Skip to content
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

New field detection problem in GitLab Rest Handler. #114

Open
WGC575 opened this issue Jan 28, 2024 · 1 comment
Open

New field detection problem in GitLab Rest Handler. #114

WGC575 opened this issue Jan 28, 2024 · 1 comment
Assignees

Comments

@WGC575
Copy link
Collaborator

WGC575 commented Jan 28, 2024

In GitLabRestHandler.java, when a new field (in the REST API) is detected, the previous reaction is to throw an exception and break the execution. But most of the time, we don't care what is added to the field set since we don't fetch new information for processing RecovAr. Thus, the workaround now is to skip the defaults rather than throwing out exceptions for any field that enters the "default" part for case switch.

@WGC575 WGC575 self-assigned this Jan 28, 2024
WGC575 added a commit that referenced this issue Jan 28, 2024
…xception that breaks the execution of RecovAr. #114
@WGC575
Copy link
Collaborator Author

WGC575 commented Jan 28, 2024

The issue is temporary resolved with 177bc11. Further fixes needed to report new fields. The reason is that although we don't need this information for execution, but we still need it for extending ARCADE and RecovAr.

WGC575 added a commit that referenced this issue Jan 30, 2024
…ted GitLabRestHandler.java to disregard new fields to match #114. #112
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant