These are chat archives for fossasia/open-event-server

8th
Jul 2018
Kreijstal
@Kreijstal
Jul 08 2018 05:51 UTC
@schedutron @srv-twry Can you guys confirm fossasia/open-event-server#5043
I want to know if it's just me
Saurav Tiwary
@srv-twry
Jul 08 2018 05:52 UTC

http://domis.sytes.net:10002

Are you hosting it somewhere else ?

Kreijstal
@Kreijstal
Jul 08 2018 05:53 UTC
What do you mean?
Saurav Tiwary
@srv-twry
Jul 08 2018 05:53 UTC
Check the stacktrace in your issue.
It is making a call to this URL
:neutral_face:
Kreijstal
@Kreijstal
Jul 08 2018 05:53 UTC
yes, and the url is responding
Saurav Tiwary
@srv-twry
Jul 08 2018 05:54 UTC
Okay, so are you hosting it or is it the new deployment hosted by @maxlorenz ?
Kreijstal
@Kreijstal
Jul 08 2018 05:54 UTC
oh it's mine
ignore it
Saurav Tiwary
@srv-twry
Jul 08 2018 05:55 UTC
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.
Kreijstal
@Kreijstal
Jul 08 2018 05:55 UTC
ah you mean on the server
Saurabh Chaturvedi
@schedutron
Jul 08 2018 05:56 UTC

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?

Kreijstal
@Kreijstal
Jul 08 2018 05:56 UTC
wait a sec den
Saurav Tiwary
@srv-twry
Jul 08 2018 05:56 UTC
Also go to the networks tab in the browser and add the payload of the request in the issue as well.
Kreijstal
@Kreijstal
Jul 08 2018 05:57 UTC
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
Saurav Tiwary
@srv-twry
Jul 08 2018 06:01 UTC
Have you updated the db ?
python manage.py db upgrade ??
Kreijstal
@Kreijstal
Jul 08 2018 06:05 UTC
is there a way to check that
Saurav Tiwary
@srv-twry
Jul 08 2018 06:05 UTC
Just run it again. It won't cause any issues if you run again.
Saurabh Chaturvedi
@schedutron
Jul 08 2018 06:06 UTC
Or you can do python manage.py db show to see the current head. It should be 163f9fc56815.
Kreijstal
@Kreijstal
Jul 08 2018 06:13 UTC
Hmm would it be a bad idea if manage.py runserver also updated the database
Kreijstal
@Kreijstal
Jul 08 2018 06:22 UTC
000b9376b87b (head)
After db upgrade
oh wait I think I forgot to do something
Kreijstal
@Kreijstal
Jul 08 2018 06:35 UTC
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 ']
Kreijstal
@Kreijstal
Jul 08 2018 07:06 UTC
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
Saurav Tiwary
@srv-twry
Jul 08 2018 07:25 UTC
Your server is not updated then. That PR was merged yesterday I guess.
Max Lorenz
@maxlorenz
Jul 08 2018 08:15 UTC
yeah I merged that yesterday from @bhaveshAn
mail_status used to be 1/0 before
Kreijstal
@Kreijstal
Jul 08 2018 08:30 UTC
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

Kreijstal
@Kreijstal
Jul 08 2018 08:38 UTC
@maxlorenz does your docker server work for you?
it stopped working since recently because of this
Saurav Tiwary
@srv-twry
Jul 08 2018 08:53 UTC
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
Saurabh Chaturvedi
@schedutron
Jul 08 2018 09:10 UTC
Please review fossasia/open-event-server#5036
Saurabh Chaturvedi
@schedutron
Jul 08 2018 12:46 UTC

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

Kreijstal
@Kreijstal
Jul 08 2018 12:58 UTC
I'm testing travis
python create_db.py is broken
you cannot longer install open-event
but travis didn't output any error!
Kreijstal
@Kreijstal
Jul 08 2018 13:20 UTC
WEIRD travis worked
but my build keeps failing
what is going on
Kreijstal
@Kreijstal
Jul 08 2018 14:23 UTC
there's something weird going on
Bhavesh Anand
@bhaveshAn
Jul 08 2018 14:50 UTC
@Kreijstal please pull the changes and check now
Kreijstal
@Kreijstal
Jul 08 2018 18:11 UTC
fixed it
It was nothing to do with open-event
:/