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
{{ message }}
Repository navigation
Exceptions should never be propagated as a generic Java Error #275
This tends to cause processes to crash as no-one catches this type of error. From what I can tell, it looks like we are re-boxing the GitlabAPIexception with a java.lang.Error.
java.lang.Error: org.gitlab.api.GitlabAPIException: {"message":"403 Forbidden"}
at org.gitlab.api.http.GitlabHTTPRequestor$1.fetch(GitlabHTTPRequestor.java:263)
at org.gitlab.api.http.GitlabHTTPRequestor$1.hasNext(GitlabHTTPRequestor.java:217)
at org.gitlab.api.http.GitlabHTTPRequestor.getAll(GitlabHTTPRequestor.java:185)
at org.gitlab.api.GitlabAPI.getRepositoryTree(GitlabAPI.java:1563)
On Dec 22, 2017, at 1:20 PM, Tim Olshansky ***@***.***> wrote:
@jpitz you make a very good point. Would you be ok to submit a PR for this change?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
Activity
mjpitz commentedon Dec 18, 2017
Looking at the code really quick, I see this double try catch causing the issue:
timols commentedon Dec 22, 2017
@jpitz you make a very good point. Would you be ok to submit a PR for this change?
mjpitz commentedon Dec 22, 2017
mjpitz commentedon Jan 5, 2018
@timols : feel free to assign to me if possible. I should have something up today.
mjpitz commentedon Jan 5, 2018
Pull request here: #281
gh-275: Propagate exceptions as a RuntimeException instead of java.la…
jaredhodge commentedon Oct 4, 2018
@timols ; how about spinning a new version of the library and propagating it out maven central so people can take advantage of this fix?
jaredhodge commentedon Oct 16, 2018
I see 4.1.0 out there now. Thanks @timols!