Tutor devstack crashes relating to debug_toolbar

I’ve run into and reported:

These crashes are quite disruptive. Has anyone else run into these issues? Or do you all just disable debug mode for your devstacks? :slight_smile:

Also I’m curious what the process is for logging time for reporting and figuring out workarounds to these kind of devstack issues? :slight_smile:

Ticket: BB-9856 (my onboarding epic)

@samuel I don’t think I have ever run into issues like the ones described in either of those those tickets.

I thought it might be specific to some content in the demo course. But the links you shared aren’t working for me. Mostly ItemNotFoundErrors or other such.

As far the time logging goes, I don’t think there is any dedicated epic or ticket for that. It’s typically part of the ticket I am working on. Setting up a specific dev env is part of the ticket, so any issues and resolutions should go in the same ticket.

Edit: As a bit more context, I have a tutor main with the master checked out that I pulled the latest change before I tested. However, the demo course was improted maybe last week or 2 weeks before. So there is a possibility that something could have changed in the demo course since then. I didn’t mean to come across as dismissive of the errors you are seeing. I am sorry if it read that way. :slight_smile:

2 Likes

Ah yes that’s expected for most of the urls. The xblock urls are specific to the newly created xblock (after clicking “New unit”) - sorry if that wasn’t clear.

It could be specific to the demo course, good point. When I have some time, I’ll have to test again with a new course. :+1:

No not at all, don’t worry. I appreciate all the data points - if it’s just me, then maybe something’s not set up correctly for my particular devstack. :slight_smile:

@samuel I noticed this happening to me since 2 days and it has started after I updated master, let me see if this related to changes in master or probably some dependency update

2 Likes