We started getting this error message in our SonarCloudAnalyze task in Azure Dev Ops.
##[error]ERROR: [baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
It does not seem to cause the activity to fail, but it does show as an error on the Azure Pipeline Run. We rebuilt our containers earlier today so it seems like it could potentially be related to the version of node. This repo is primarily ASP.NET Core and Blazor WASM. Please advise. Thank you.
Thanks for reporting this. We are looking into it, but as we have some high priority items on our plate this might take a bit of time before we can solve it, if you confirm this is not blocking at the moment.
Hi, we are seeing and having the same issue on our environment. Would be nice if this can be fixed soon, as it is throwing Errors instead of Warnings. If it can be a warning instead of an Error, that would already help a lot.
As far as we can see we are not reporting the error, so we cannot influence the level, unfortunately.
I am deeply sorry about the inconvenience. Let us know if that becomes a blocker, but, as I said, we have some high priority work at the moment, so unless it is preventing users from working, I’m afraid it has to take a back seat. We will tackle it as soon as we can and reshuffle priorities if need be.
Hi @denis.troller , thanks for responding swiftly. It is not a blocker as if we cannot work, but it is quite annoying that our build server returns only two errors, being:
So each time we think we need to solve something, but its this one. Over time this will lower our thresholds for errors and makes us respond less faster to actual issues.
Thanks for the quick reply. I can confirm as @zaat did that this is not a blocker, just an annoyance at the moment. Looking forward to a fix when you all get some time. Thanks again.
I noticed that when I asked about when this issue will be fixed, I checked JIRA and saw that it has not yet been assigned to anyone for resolution. When can we expect this issue to be resolved?
