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.

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

Can't see a new user #2249

Closed
rlevit opened this issue Jun 3, 2022 · 16 comments
Closed

Can't see a new user #2249

rlevit opened this issue Jun 3, 2022 · 16 comments
Labels
bug Something isn't working

Comments

@rlevit
Copy link

rlevit commented Jun 3, 2022

Describe the bug
In the newly deployed locally Dispatch app, where the dispatch-local image was built from Dockerfile pulled today, I created a new organization named Amplify with a user ([email protected]) who is an admin of the default org. I logged out and changed URL to http://localhost:8000/amplify/auth/register and registered with a new user [email protected]. I ran docker exec -it dispatch-web-1 bash -c 'dispatch user update --role Owner --organization Amplify [email protected]' command and got User successfully updated response.

When I log in to Dispatch as [email protected] and go to Members I see my user but don't see the test user. If I switch to Amplify org I don't see any users. If I log in to Amplify org with the test user I don't see that user in Members at all. I see the same thing in the API calls - the test user is not showing up regardless which user auth bearer token I use (rlevit or test). With Dispatch running from the image created by the install.sh I was able to see all users in the API and UI.

Expected behavior
All users appear and the Members section.

Screenshots
Screen Shot 2022-06-03 at 12 15 43 PM

Screen Shot 2022-06-03 at 1 43 54 PM

Screen Shot 2022-06-03 at 1 45 33 PM

Screen Shot 2022-06-03 at 1 48 57 PM

Screen Shot 2022-06-03 at 1 52 11 PM

@mvilanova
Copy link
Contributor

@rlevit thanks for the report. I'll see if I can repro and circle back probably not until next week. Sorry for the inconvenience this is causing.

@github-actions
Copy link
Contributor

github-actions bot commented Jul 4, 2022

This issue is stale, because it has been open for 30 days with no activity. Remove the stale label or comment, or this will be closed in 5 days.

@github-actions github-actions bot added the Stale label Jul 4, 2022
@mvilanova mvilanova removed the Stale label Jul 7, 2022
@mvilanova
Copy link
Contributor

@rlevit #2336 should've fixed this issue. Let me know if that's not the case.

@mvilanova mvilanova added the bug Something isn't working label Jul 7, 2022
@rlevit
Copy link
Author

rlevit commented Jul 13, 2022

@mvilanova I redeployed Dispatch from the latest master and now can see all users registered to a non-default org. Thank you for fixing this.

@rlevit
Copy link
Author

rlevit commented Jul 13, 2022

@mvilanova, oh, sorry, I have to take the previous message back.

After the login I switched to Amplify org and went to "Settings->Members" and I saw all the user I didn't see before. But I didn't realized that I still was in the "Default" org. So now looks like the org switcher is not working because no matter how many times I click on the arrows sign next to the desired org it won't switch to it. To actually switch to Amplify org I had to replace "default" with "amplify" in the URL and now can't go back to the "default" org using the org switcher. Sorry about confusion. I can make a screen recording to demonstrate the issue.

@mvilanova
Copy link
Contributor

Known issue. Working on a fix.

@rlevit
Copy link
Author

rlevit commented Jul 13, 2022

Great, thank you. Also, after switching to the Amplify org I couldn't see users registered to that org, meaning the issue persists.

@github-actions
Copy link
Contributor

This issue is stale, because it has been open for 30 days with no activity. Remove the stale label or comment, or this will be closed in 5 days.

@github-actions github-actions bot added the Stale label Aug 13, 2022
@mvilanova mvilanova removed the Stale label Aug 13, 2022
@mvilanova
Copy link
Contributor

I haven't forgotten about this one. I should be able to resume work on it soon.

@github-actions
Copy link
Contributor

This issue is stale, because it has been open for 30 days with no activity. Remove the stale label or comment, or this will be closed in 5 days.

@github-actions github-actions bot added the Stale label Sep 13, 2022
@github-actions
Copy link
Contributor

This issue was closed, because it has been stalled for 5 days with no activity.

@mvilanova mvilanova reopened this Sep 19, 2022
@mvilanova mvilanova removed the Stale label Sep 19, 2022
@vijal-patel
Copy link

@mvilanova. are you looking for contributors? If so, I'd like to work on this issue

@mvilanova
Copy link
Contributor

@vijal-patel sure, go ahead. Thanks!

@vijal-patel
Copy link

@rlevit I'm not able to replicate the missing user issue. Can you provide the exact steps you used?
I've tried:

  • running everything with docker (did not use install.sh)
  • running dispatch with python only

I see @mvilanova is already working on the organization switch issue #2599

@github-actions
Copy link
Contributor

This issue is stale, because it has been open for 30 days with no activity. Remove the stale label or comment, or this will be closed in 5 days.

@github-actions github-actions bot added the Stale label Nov 22, 2022
@github-actions
Copy link
Contributor

This issue was closed, because it has been stalled for 5 days with no activity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants