You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I like this plugin a lot. Unfortunately I have been encountering an issue since I installed it and was hoping someone here might be able to point me in the right direction towards fixing it.
The problem is that, sporadically, I will get a "EOF\n" error popup. It happens every few minutes and seems to occur more when there is a build in progress but not exclusively during one.
My build setup is simple, and I only have one branch displayed.
I am not too familiar with Java, but looking at the source I am not sure that this is an issue specifically with this plugin - I just don't know how to diagnose the issue.
I have tried disabling the JUnit progress output setting, periodic repository scans, and some other settings to no avail.
My Jenkins log doesn't show anything that jumps out at me, I am not sure why it is saying there is no rate limiting as I have that enabled but I don't think it is related to this issue.
May 08, 2022 1:03:01 PM INFO jenkins.branch.MultiBranchProject$BranchIndexing run
TestProject #20220508.130300 branch indexing action completed: SUCCESS in 1.3 sec
May 08, 2022 1:08:00 PM INFO org.jenkinsci.plugins.github_branch_source.ApiRateLimitChecker$RateLimitCheckerAdapter checkRateLimit
LocalChecker for rate limit was not set for this thread. Configured using system settings with API URL 'https://api.github.com'.
May 08, 2022 1:08:01 PM INFO jenkins.branch.MultiBranchProject$BranchIndexing run
TestProject #20220508.130800 branch indexing action completed: SUCCESS in 1.2 sec
May 08, 2022 1:08:40 PM INFO org.jenkinsci.plugins.github.webhook.subscriber.DefaultPushGHEventSubscriber onEvent
Received PushEvent for https://github.com/Eshnek/TestProject from <some ip> → <some ip> → <some ip> ⇒ https://smee.io:8080/github-webhook/
May 08, 2022 1:08:55 PM INFO org.jenkinsci.plugins.github_branch_source.ApiRateLimitChecker$RateLimitCheckerAdapter checkRateLimit
LocalChecker for rate limit was not set for this thread. Configured using system settings with API URL 'https://api.github.com'.
May 08, 2022 1:09:04 PM INFO org.jenkinsci.plugins.github_branch_source.ApiRateLimitChecker$RateLimitCheckerAdapter checkRateLimit
LocalChecker for rate limit was not set for this thread. Configured using system settings with API URL 'https://api.github.com'.
I have also tried using a custom logger with the log setting to ALL, I did not see anything out of the ordinary.
Ultimately I can hide the popup modal / refresh the page, but this is far from ideal (Similar to #602)
Since reloading always fixes the issue, is there any reason the plugin could not instead continue to function after receiving this error?
The text was updated successfully, but these errors were encountered:
Hello!
I like this plugin a lot. Unfortunately I have been encountering an issue since I installed it and was hoping someone here might be able to point me in the right direction towards fixing it.
The problem is that, sporadically, I will get a
"EOF\n"
error popup. It happens every few minutes and seems to occur more when there is a build in progress but not exclusively during one.My build setup is simple, and I only have one branch displayed.
I am not too familiar with Java, but looking at the source I am not sure that this is an issue specifically with this plugin - I just don't know how to diagnose the issue.
I have tried disabling the JUnit progress output setting, periodic repository scans, and some other settings to no avail.
My Jenkins log doesn't show anything that jumps out at me, I am not sure why it is saying there is no rate limiting as I have that enabled but I don't think it is related to this issue.
I have also tried using a custom logger with the log setting to
ALL
, I did not see anything out of the ordinary.Ultimately I can hide the popup modal / refresh the page, but this is far from ideal (Similar to #602)
Since reloading always fixes the issue, is there any reason the plugin could not instead continue to function after receiving this error?
The text was updated successfully, but these errors were encountered: