Skip to content
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.

Sign up for GitHub

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

Jump to bottom

App crashes when loading workspace (tried 2) #5

Open
keenmaster486 opened this issue Feb 12, 2020 · 4 comments
Open

App crashes when loading workspace (tried 2) #5

keenmaster486 opened this issue Feb 12, 2020 · 4 comments

Comments

@keenmaster486
Copy link

I tried this app on 2 different workspaces. One has a lot of channels and users. The second one has hardly any (maybe like 10). The app crashes with a general protection fault when trying to access either one of them (while trying to load the user list).

This is happening on 3 systems: my main Linux PC with WINE, my Windows XP VM, and my IBM Thinkpad 755C running Windows 3.1 (i.e. a real machine that this app definitely should work on).

Without the proxy it gracefully fails to load the users and does not crash, so I don't think it is my system configuration.
@yeokm1
Copy link
Owner

yeokm1 commented Feb 12, 2020 •
edited
Loading

I'll need more information if it's ok with you to provide.

  1. How does your Thinkpad 755C connect to the network? Also what is the network configuration and its system specifications? I understand you mentioned that the app can hit the proxy so this should not be an issue. But it could be useful for me.

  2. Since you mentioned a crash while loading the users list, can you run this command and send me the result? Replace your fields as necessary. Replace the IP with your proxy IP.

curl -H "Host: slack.com" -H "Authorization: Bearer xoxp-821448956678-818775000324-818797461140-4d175b4e14b948d630f195e51478bb0e" -X GET "http://127.0.0.1:80/api/users.list"

  1. Send me a copy of your w31slack.ini. You can remove the token if that is a sensitive issue.

The best solution of all if possible is to create a dummy user account for me and pass me a token to your workspace so I can simulate the problem directly on my end. You can revoke it after I'm done.

@keenmaster486
Copy link
Author

keenmaster486 commented Feb 13, 2020 via email

@yeokm1
Copy link
Owner

yeokm1 commented Feb 16, 2020

@keenmaster486 Thanks for the info. Let me look into it once my schedule clears up.

yeokm1 added a commit that referenced this issue Feb 27, 2020
@yeokm1
Add extra test case based on this issue #5
efc2f4e
@yeokm1
Copy link
Owner

yeokm1 commented Feb 27, 2020 •
edited
Loading

@keenmaster486 I have adopted your json as an additional test case in this commit. My code can parse the 24 users correctly with no crash. So it is unlikely the json parsing is at fault.

I propose to let me try it on your Slack workspace to replicate and debug what the problem is. If you are comfortable, can you create a temporary account for me and pass me the token privately.

efc2f4e

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@yeokm1 @keenmaster486