in your git comments, I wanted some clarity: better use of Jinja2 block structure within the same file? or (separate .css, .html, .js files.
Yes, better use of jinja2. I also thing Bootstrap can be better utilized being the code for tabs and other mechanics you coded is already being loaded.
Working on the bootstrap stuff. it'll get rid of a lot of custom functionality i made
is the new tool live to use on the prod sanic site?
{agent_name}/{year}/{month}/{day}/{hour}-{minute}-{second} {phone}.mp3
https://python-dependency-injector.ets-labs.org/
Can I have a person I know has been having issues come in so we can see if your fix worked on the DB permissions 404 thing? I want to do a workshop with about 6 people, someone asked me again this morning about it.
I want to at least get that one small fix pushed
My PR changes the entire structure. 10k+lines changed. Dustin is reviewing it, but it will take a while. As for that fix, I can have a deeper look.
Can you describe the problem as you see it? I know we have spoken about it, but a textual description here would have something for me to review any time I try to consider the issue.
yea i just want to push a single branch to fix that one single thing. it seems to be a DB permissions issue on the routes and some people get the 404. Others not. I already went through netowrks logs, GCP logs, etc. It traced it down to that one line.
I want to have someone come in that was having an issue and log in and try it in here with your fix before we push it
Ah, you should be able to pull my branch that is up there and run the prod locally so that you can log them into an incognito window. I will likely not be in today and working from home, as I am currently at the doctors for my wife, and at 1 I have an echo cardiogram. If you would like me to do it, set up a quick meeting tomorrow morning around stand up.
Ah we'll sort it out tomorrow. I am absolutely convinced it is something in the permissions in the database for the routes
I am currently writing integration tests which require actual database communication so if these issues arise in the future, we can diagnose quicker.
Yeah this is very specificly tied to permission in the db regarding routes
well talk tomorrow -- take care of yourself