Store Meshes in Postgres

[fm3]

URL of deployed dev instance (used for testing):

• https://savemesh.webknossos.xyz

@philippotto on this branch I added the new routes

POST          /api/meshes         //create
PUT           /api/meshes/:id     //update 
DELETE        /api/meshes/:id     //delete
GET           /api/meshes/:id     
PUT           /api/meshes/:id/data
GET           /api/meshes/:id/data

the data is separate from the metadata.
metadata post and put (topmost) expect a json like

{
	"annotationId": "5bc717c52601006501a87696",
	"position": [0, 0, 0],
	"description": "aMeshDescription"
}

and return a json with meshInfo.
the annotation info request contains a new field "meshes", listing the associated meshes. (the mesh metadata GET will probably not be used by the frontend)

the data requests expect/deliver raw binary data. They will fail if the metadata is not created first.

@philippotto is this how you imagined it? Please ask questions or suggest changes :)

Do you want to implement the front-end part on this branch? (Or assign someone else, of course)

Steps to test:

Issues:

• fixes Store Meshes in Postgres #3289

---

• Updated changelog
• Updated migration guide if applicable
• Updated documentation if applicable
• [ ] Needs datastore update after deployment
• Ready for review

[philippotto]

@fm3 I added the front-end part and think this is ready to review. I made some small changes to the back-end which you might want to double check.

Do you want to pull the master in and merge the back-end conflict? If you commit the frontend conflicts, I can resolve them then.

[fm3]

@philippotto that’s great, thanks!
I merged master, there are still open conflicts in app/assets/javascripts/oxalis/store.js and app/assets/javascripts/oxalis/view/layouting/default_layout_configs.js

[daniel-wer]

Very clean implementation 👍 I like that you focused on UX and made this an easily usable feature :)

[daniel-wer]

The feature itself works really well :) There are still some things I noticed during manual testing:

• Initially the meshes tab is not displayed, only after reset layout, it turns up. What is the strategy for layout migrations?
• Switching to Flight/Oblique is broken, somehow all layout panes are displayed and no data is rendered.
• React Warning in the Console: Warning: React does not recognize the 'faIcon' prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase 'faicon' instead. If you accidentally passed it from a parent component, remove it from the DOM element.
• It takes pretty long to add the stl to the scene and render it for the first time (>20s for my test unicorn). I'm not sure whether that is the same for the amira segmentation files or whether we can do anything to improve that. I did a performance measurement and the time was mostly spent in threejs.

Unicorn_20160524.zip

• Maybe change the mouse cursor to indicate that the edit and delete icons are clickable (cursor: pointer).

[daniel-wer]

I just tested again, arbitrary/flight mode works as expected, was probably related to the missing layout config version bump. :)