Two surprises in browser crashes
neugierig.org
neugierig.org
Was the change CSS specific or was it domain specific?
The call chain from the renderer can be surprisingly deep.
What is your favorite tool for this?
I feel like years ago it was New Relic, Raygun, Sentry, etc... but it feels like we never hear about these tools or companies any more on HN. Is this not a sexy topic any more?
If it wasn't for the GitHub pack, I would have never known about something like this. Maybe you are right, and it isn't a unique enough topic now :(
I disable javascript by default, some sites become non-functional, then I enable 1st party js, and something see these 3rd party js and got curious on it when I see it being used from multiple sites.
You can also quickly see which tech are used by the site you're browsing with the wappalyzer addon
That being said, New Relic has served us fairly well. Especially if you put in the grunt work for distributed tracing between the client and your servers.
They have a generous free tier and are open source so that’s a plus too
Report-uri is the tool. Warning you are going to get a lot of reports because your stuff is broken a lot. You just don't see it.
Basically more than likely your code/infrastructure is doing something wrong. These linter style tools many times will find whole classes of bugs smeared across your whole code base.
One poor soul I worked with once decided 'hey no errors are being caught anywhere'. He then proceeded to add logging to everything where something would fail. "dude you are about to get 1000 bugs back from the QA group and they will blame you even though it is the 3 guys who left 2 years ago that did it". He nearly lost his job because he did not prime them for it. QA was rightly mad because they went from 'everything seems to work' to error alerts everywhere and no testing can be completed.
I've built shopping cart forms before, which get every single browser imaginable. Keenly aware of the number of oddball edge case errors that happen.
Don't be evil (:
If these settings can't be turned off then I'd definitely assume the feature flag reporting and the CSP reporting are used for tracking on some platforms, on which AdNauseam would then have merit.
EDIT: CSP reports are blocked by uBlock Origin by default but it appears there are no browser settings to control this behaviour. I expected Chrome to screw users over like this, but I'm disappointed in Firefox that there's no "advanced privacy options" screen where I can control this behaviour.
export function wrapInErrorHandler<Func extends (...args: any[]) => any>(func: Func): (...args: InferArguments<Func>) => InferReturn<Func> {
return function (...args: InferArguments<Func>) {
try {
return func.apply(null, args);
} catch (err: any) {
if (err instanceof LoggedError) {
throw err;
}
post({ your- error - object});
throw new LoggedError(err);
}
};
}