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
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: