@schedutron @srv-twry Can you guys confirm fossasia/open-event-server#5043
I want to know if it's just me
Are you hosting it somewhere else ?
What do you mean?
Check the stacktrace in your issue.
It is making a call to this URL
:neutral_face:
yes, and the url is responding
Okay, so are you hosting it or is it the new deployment hosted by @maxlorenz ?
oh it's mine
ignore it
What I basically want is the stacktrace. It doesn't matter whether one/two or everyone else gets the error. It shouldn't error out for anyone.
If you have access to the stacktrace of the server, please add it on the issue.
ah you mean on the server
What I basically want is the stacktrace. It doesn't matter when one/two or everyone else gets the error. It shouldn't error out for anyone.
Which should've logged in the server, right?
wait a sec den
Also go to the networks tab in the browser and add the payload of the request in the issue as well.
It's not necessary, it just says that because the reply was 500, then it errors as well
but let me get you the server stack
okay
there you go
Have you updated the db ?
python manage.py db upgrade ??
is there a way to check that
Just run it again. It won't cause any issues if you run again.
Or you can do
python manage.py db show to see the current head. It should be 163f9fc56815.
Hmm would it be a bad idea if manage.py runserver also updated the database
000b9376b87b (head)
After db upgrade
oh wait I think I forgot to do something
Getting this error while upgrading
qlalchemy.exc.ProgrammingError: (psycopg2.ProgrammingError) column "mail_status" cannot be cast automatically to type boolean
HINT: You might need to specify "USING mail_status::boolean".
[SQL: 'ALTER TABLE message_settings ALTER COLUMN mail_status TYPE BOOLEAN ']
Now getting this
sqlalchemy.exc.ProgrammingError: (psycopg2.ProgrammingError) column message_settings.sent_at does not exist
LINE 1: ...l_status AS message_settings_user_control_status, message_se...
^
when running runserver, hmm
Your server is not updated then. That PR was merged yesterday I guess.
yeah I merged that yesterday from @bhaveshAn
mail_status used to be 1/0 before
well it seems I can't even get it to work now lol
Getting this
v2-server_1 | Creating Event Topics...
v2-server_1 | Creating Event Types...
v2-server_1 | Creating Event Locations...
v2-server_1 | Creating admin message settings...
v2-server_1 | Traceback (most recent call last):
v2-server_1 | File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1182, in _execute_context
v2-server_1 | context)
v2-server_1 | File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 470, in do_execute
v2-server_1 | cursor.execute(statement, parameters)
v2-server_1 | psycopg2.ProgrammingError: column message_settings.sent_at does not exist
v2-server_1 | LINE 1: ...l_status AS message_settings_user_control_status, message_se...
v2-server_1 | ^
v2-server_1 |getting this
@maxlorenz does your docker server work for you?
it stopped working since recently because of this
Guys similar to what we do in the orga app, I have added an
open-for-all label in the server repository. These issues haven't been claimed by anyone and can be taken by someone who is short in issues to work on. https://github.com/fossasia/open-event-server/issues?q=is%3Aissue+is%3Aopen+label%3Aopen-for-all
Please review fossasia/open-event-server#5036
I'm getting the same error that @Kreijstal was getting:
sqlalchemy.exc.ProgrammingError: (psycopg2.ProgrammingError) column "mail_status" cannot be cast automatically to type boolean
HINT: You might need to specify "USING mail_status::boolean".
[SQL: 'ALTER TABLE message_settings ALTER COLUMN mail_status TYPE BOOLEAN ']I guess we need to add the USING mail_status::boolean flag to the current migration file, i.e., 163f9fc56815_.py
I'm testing travis
python create_db.py is broken
you cannot longer install open-event
but travis didn't output any error!
WEIRD travis worked
but my build keeps failing
what is going on
there's something weird going on
@Kreijstal please pull the changes and check now
fixed it
It was nothing to do with open-event
:/