New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[studio] db error during content-type updates #1742

Closed
jdrossl opened this Issue Jan 4, 2018 · 3 comments

Comments

@jdrossl
Member

jdrossl commented Jan 4, 2018

Actual behavior

After a content-type is changed (add a new form section & a control) when the Save button is clicked an error is returned.

screen shot 2018-01-03 at 1 45 27 pm

Steps to reproduce the problem

There is no way to reproduce manually, it appears completely random during execution of the test-suite

Log/stack trace (use https://gist.github.com)

https://gist.github.com/jdrossl/02030600df2fbc24e5101c335255bc6d

@sumerjabri sumerjabri added this to the Crafter CMS v3.1.0 milestone Jan 8, 2018

@sumerjabri sumerjabri added this to Backlog in Crafter CMS v3.0.x via automation Aug 15, 2018

@sumerjabri sumerjabri removed this from Backlog in Crafter CMS v3.0.x Aug 15, 2018

@sumerjabri sumerjabri added this to Backlog in Crafter CMS v3.1.x via automation Aug 15, 2018

@sumerjabri

This comment has been minimized.

Show comment
Hide comment
@sumerjabri

sumerjabri Aug 15, 2018

Member

This should be fixed now. We made changes to protect against the race-condition that causes this. Please validate.

Member

sumerjabri commented Aug 15, 2018

This should be fixed now. We made changes to protect against the race-condition that causes this. Please validate.

@sumerjabri sumerjabri changed the title from [studio] db error during content-type edition to [studio] db error during content-type updates Aug 15, 2018

@jdrossl jdrossl moved this from Backlog to Test & Validate in Crafter CMS v3.1.x Aug 20, 2018

@jdrossl

This comment has been minimized.

Show comment
Hide comment
@jdrossl

jdrossl Aug 20, 2018

Member

I ran the test suite in the 3.1 branch and the error didn't happen, but since it was completely random I don't know if we can be sure.

Member

jdrossl commented Aug 20, 2018

I ran the test suite in the 3.1 branch and the error didn't happen, but since it was completely random I don't know if we can be sure.

@jdrossl jdrossl assigned sumerjabri and unassigned jdrossl Aug 20, 2018

@sumerjabri

This comment has been minimized.

Show comment
Hide comment
@sumerjabri

sumerjabri Aug 21, 2018

Member

The underlying issue should be fixed, and this is no longer reproducible. Closing.

Member

sumerjabri commented Aug 21, 2018

The underlying issue should be fixed, and this is no longer reproducible. Closing.

@sumerjabri sumerjabri closed this Aug 21, 2018

Crafter CMS v3.1.x automation moved this from Test & Validate to Completed Aug 21, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment