Bug: Workspace dropdown in Add to workspace modal it too big

[nickytonline]

The workspace dropdown in the Add to workspace modal it too big. The arrow is in the middle of the dropdown.

[github-actions[bot]]

Thanks for the issue, our team will look into it as soon as possible! If you would like to work on this issue, please wait for us to decide if it's ready. The issue will be ready to work on once we remove the "needs triage" label.

To claim an issue that does not have the "needs triage" label, please leave a comment that says ".take". If you have any questions, please comment on this issue.

For full info on how to contribute, please check out our contributors guide.

[ryandotfurrer]

.take

[ryandotfurrer]

I am looking to login on my branch so I can see the changes I'm making to the dropdown, however, I am getting a 404 upon running npm run dev. Any ideas how I can fix this so I can see what I am working on?

The same thing occurs when I try to go to /home

[nickytonline]

Hmm not sure what’s up. We don’t have a /login route.

Can you run git clean -dfx to remove any files that aren't in git and then run npm install. There are no environment variables to set. We have environment variables configured for dev. From there running npm run dev and going to http://localhost:3000 should load up the site.

and to log in just click on the connect with GitHub button at the top right of the site.

[ryandotfurrer]

Thanks, @nickytonline! I forgot this is a known issue from working on Gridiron Survivor (GIS). Any time I spin up another Next.JS app it tries to use the redirect in GIS's next.config, which redirects to /login. I imagine this has something to do with caching but none of us know the solution.

I didn't think about this yesterday but was going crazy as I did not see a /login route.

Either way, I've got this running now. Thanks for teaching me about git clean -dfx too.

[nickytonline]

Thanks, @nickytonline! I forgot this is a known issue from working on Gridiron Survivor (GIS). Any time I spin up another Next.JS app it tries to use the redirect in GIS's next.config, which redirects to /login. I imagine this has something to do with caching but none of us know the solution.

I didn't think about this yesterday but was going crazy as I did not see a /login route.

Either way, I've got this running now. Thanks for teaching me about git clean -dfx too.

You probably have a ServiceWorker in GridIron survivor causing the issue. Just clearing all application data in dev tools fixes it or unregistering the service worker.

[ryandotfurrer]

Thanks, @nickytonline! I forgot this is a known issue from working on Gridiron Survivor (GIS). Any time I spin up another Next.JS app it tries to use the redirect in GIS's next.config, which redirects to /login. I imagine this has something to do with caching but none of us know the solution. I didn't think about this yesterday but was going crazy as I did not see a /login route. Either way, I've got this running now. Thanks for teaching me about git clean -dfx too.

You probably have a ServiceWorker in GridIron survivor causing the issue. Just clearing all application data in dev tools fixes it or unregistering the service worker.

Thanks for this man, I'll have a look! You may have solved our headache 😅

[open-sauced[bot]]

:tada: This issue has been resolved in version 2.62.0-beta.3 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket:

[open-sauced[bot]]

:tada: This issue has been resolved in version 2.62.0 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket: