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
Library version: fma-connectors 0.0.1 Describe the bug:
When creating a federated model through the API service, we set the allow_aggregation attribute. This attribute is not properly set in the database using the connectors setter function for allow_aggregation. The fix lives in the serializers.py file on line 69.
To Reproduce:
Standup API service and try to set the allow aggregation attribute on the web form.
Expected behavior:
No matter what the attribute is set to the allow aggregation attribute will be set to "false". Even if an update patch is done from the web page the change will not propagate to the database entry
Additional context:
Proposed fix:
change logic on lines 69-74 in serializers.py to account for the instance.scheduler not existing when deploying remotely
The text was updated successfully, but these errors were encountered:
General Information:
Describe the bug:
When creating a federated model through the API service, we set the allow_aggregation attribute. This attribute is not properly set in the database using the connectors setter function for allow_aggregation. The fix lives in the serializers.py file on line 69.
To Reproduce:
Standup API service and try to set the allow aggregation attribute on the web form.
Expected behavior:
No matter what the attribute is set to the allow aggregation attribute will be set to "false". Even if an update patch is done from the web page the change will not propagate to the database entry
Additional context:
Proposed fix:
change logic on lines 69-74 in serializers.py to account for the
instance.scheduler
not existing when deploying remotelyThe text was updated successfully, but these errors were encountered: