- User Since
- Aug 22 2009, 11:37 AM (477 w, 3 d)
Sun, Oct 14
Wed, Oct 10
Tue, Sep 25
Thu, Sep 20
Wed, Sep 19
Tue, Sep 18
Mon, Sep 17
Sep 16 2018
Sep 15 2018
Issue temporarily solved in rPSf8d992400e0172104b3fc687e245d9eedac7bbd9.
Sep 14 2018
Sep 13 2018
Could you describe the bug that motivated this fix?
Currently the fix seems to break attachment rendering everywhere :)
Sep 9 2018
All fixed in 9dba25e9a9e4394d987e931a028cb170aff42758, except for the last concern. We actually display the sample id in the table, so the user can actually see which sample we are talking about in the error. I agree that embedding the error message in the sample row would be nicer, so I create a [new task for it](T56730), which also references this concern.
Sep 8 2018
Sep 6 2018
Sep 5 2018
Sep 4 2018
Sep 3 2018
Sounds good. We should discuss how to handle node_type properties overrides (for example predefined values, or allowed values).
Probably this makes "migrations" easier, and reduces complexity when validating nodes so it's really exciting!
Awesome! I add a comment here, to be discussed tomorrow.
Could you outline the reasoning behind storing the watch progress in the user document instead of in the node docs?
I think that storing such info in the node docs would allow for simpler/faster queries both when fetching an individual video and when fetching a series.
Aug 28 2018
The data is accessible via https://opendata.blender.org/raw-data/.