-
-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
intermittent error? #532
Comments
your command probably encounters an error and Just make sure that export const render = ({output}) => {
if (output == null) return null;
...
} or check whether there is an error and then display it. That way you might be able to figure out what the issue is: export const render = ({output, error}) => {
if (error != null) return <div>{JSON.stringify(error)}</div>;
....
} |
Thanks! I'll give that a try and report back. |
your output must be empty in some cases, so maybe best to combine both approaches: export const render = ({output, error}) => {
if (error != null) return <div>{JSON.stringify(error)}</div>;
if (!output) return null;
....
} |
That did the trick! Thank you. BTW, switched to Sequoia today, and Übersicht hasn't skipped a beat. |
This is probably my bad coding, but I’m seeing an odd intermittent (but frequent enough to be annoying) error with Übersicht…
Multiple times a day, I get an error panel on my desktop, but if I refresh Übersicht it disappears only to reappear randomly-ish later, and then tends to stay around until I do a manual refresh.
At first I thought it might be the a problem with the shell command being run, having some sort of race condition, but I’ve verified that this still happens without the shell command, so that means there’s either a silly bug in my code, or my code is triggering something within Übersicht. My money’s on the former, so can anyone see where the problem is? The intermittent nature of it has me stumped ¯\_(ツ)_/¯
I almost forgot to add, I have the widget on multiple monitors, and sometimes the error only appears on one monitor, sometimes on both.
The text was updated successfully, but these errors were encountered: