Skip to content

Queue timer fires even when api key isn't configured #46

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.

Sign up for GitHub

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

Jump to bottom
Closed
niemyjski opened this issue Apr 13, 2016 · 1 comment
Closed

Queue timer fires even when api key isn't configured #46

niemyjski opened this issue Apr 13, 2016 · 1 comment
Labels
bug

Comments

@niemyjski
Copy link
Member

I setup Exceptionless.UI to not set the api key by default but events are still enqueued (I don't want them sent and rejected). However, I started seeing this in the console.

[info] Exceptionless: Enqueuing event: 1460562831592 type=usage  exceptionless.js:1285:13
[info] Exceptionless: user identity: abc@gmail.com exceptionless.js:1285:13
[info] Exceptionless: Processing queue... exceptionless.js:1285:13
[info] Exceptionless: Invalid Api Key. The queue will not be processed. exceptionless.js:1285:13
[info] Exceptionless: Processing queue... exceptionless.js:1285:13
[info] Exceptionless: Invalid Api Key. The queue will not be processed. exceptionless.js:1285:13

It appears that we are triggering a timer to run even when configuration is invalid.
@niemyjski niemyjski added the bug label Apr 13, 2016
niemyjski added a commit that referenced this issue Feb 23, 2023
@niemyjski
Fixes #46: Queue timer fires even when api key isn't configured
6be3e09 
This will also prevent plugin startup and all timers from running.
@niemyjski
Copy link
Member Author

The client will now display the following if no api key is configured.

2023-02-23T00:57:55.106Z [warn] Exceptionless is not configured and will not process events.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Milestone
No milestone
Development

No branches or pull requests
1 participant
@niemyjski