[atc_profile_storage] Profile not saved about augmented-traffic-control HOT 6 CLOSED

I tested this pretty thoroughly before I created #15. Are you doing anything peculiar? Like not entering either of the rates, or the name, for instance.

from augmented-traffic-control.

I used the config from PR #21 . I did try a name with a space first, and then without a space.

from augmented-traffic-control.

I played around with this and it appears to be working as designed.

However, after some thought, I decided that the workflow for profiles was very non-intuitive. Some of the widgets were storing background state that did not reflect the actual fields if users updated them after the state was originally accessed.

I reworked the workflow to be much more intuitive in #23.

The UI presents the name field from the get-go and doesn't display the profile list if it's not available. In addition, I removed all the widget state that was previously causing confusion.

If #23 still does not fix the issue, could you show me exactly what you're doing to cause this issue?

from augmented-traffic-control.

I did not do anything special that should have prevented it from working as expected. The work flow was something alike:

• set some shaping values
• click on add profile
• enter profile name
• saved profile

After this, the list would still be empty. Reloading the page would not help. I am pretty sure I did run the Django migration script ... so the dB should have been there.

Will check again later to see if I did anything stupid. But if I did something stupid, an error message should have been thrown to me and not be discarded silently.

from augmented-traffic-control.

The only other thing I can think of is you have to run atcui-setup as the atc user, otherwise the atc user can read from it (i.e. will start successfully) but cannot write to it. This would cause the issues you mentioned.

The old workflow had some error messages for common errors, but they were fairly simple and there were likely other ways of causing issues without hitting those cases. The simplified workflow in #23 should be much more robust.

from augmented-traffic-control.

ok, confirmed that /var/django/atc_ui/db.sqlite3 was owned by root. I had run the atcui-setup as root .... so the script should be modified to run the manage.py script with the right credentials which basically means the whole script altogether should be ran as the user than is used to run the UI.

I will capture that in another task.

from augmented-traffic-control.