[omm][onboarding] Initial setup issues

[Sam-Freeman]

Howdy! Just wanted to flag a couple of difficulties (and workarounds) that I noticed when getting OMM running locally for the first time. Happy to put a fix up for some of them, just wanted to put it down as an issue (to help me remember more than anything lol)

Seeding:

• If you haven't seeded before, then the initial bank doesn't exist, and need to pass True to the storage.bank_update
• In the for loop for adding examples, currently passing a dictionary of strings for key+value when it should be SignalType for the key
  • i.e. storage.bank_add_content(bank_name, {st.get_name(): example}) needs to become storage.bank_add_content(bank_name, {st: example})

Create App:

• Not entirely sure why (haven't look into it yet), but, I had to comment out a bunch of lines around registering the blueprints the first time I created the app, afterwards, it was completely fine.

[Dcallies]

Hey @Sam-Freeman, thanks for the report! If Cinder is considering a standing deployment in your tooling, also check out #1440 to help us prioritize requests.

We definitely accept pull requests if fixes look straightforward!

For your environment, were you running these in the docker devcontainer?

Seeding issues

Is this in the flask seed helper?

Create app

I've noticed issues that sometimes crop up with the templates directory acting bizarre, which only fix themselves after a full container rebuild.

If you can get a repro, paste some of the log messages here!

[juanmrad]

I was not able to repro this after the latest fix for migration code and init of the app.

@Sam-Freeman are you able to check this is still the case if this is still an issue could you add some screenshot of errors?