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

TOO_MANY_REDIRECTS on report issue #1677

Conversation

maturbet
Copy link
Contributor

@dregad
Copy link
Member

dregad commented Jun 2, 2020

Thanks for your contribution.

I have tested your PR, and it fixes the problem without introducing any regression (as far as I can tell).

That being said, in terms of data integrity I don't think the users' default_project setting should contain an invalid project value, which can happen when a user is removed from the project, or when the project is deleted.

Maybe we should enforce resetting the default project to ALL_PROJECTS in such case, what do you think ?

@dregad
Copy link
Member

dregad commented Jun 2, 2020

As a side note, for future contributions

  • Commits should actually describe what you changed and why, Fixes #xxxx is not sufficient.
  • When submitting PR's, you should always rebase your feature branch onto mantisbt/mantisbt master (or master-x.xx for a patch release) -- unless it's a very complex, long-running branch that would be too difficult or complex to rebase, in which case merge commits are acceptable.

Unless you're using it for your own purposes, I also recommend to keep your master branch aligned with and identical to ours (i.e. git fetch upstream && git reset --hard upstream/master) instead of merging (like you did at c142c21). Then you can simply run git pull upstream to keep it in sync.

@maturbet
Copy link
Contributor Author

maturbet commented Jun 3, 2020

Maybe we should enforce resetting the default project to ALL_PROJECTS in such case, what do you think ?

This is indeed a feature I had considered but didn't feel like coding myself.

As a side note, for future contributions [...]

I will try to improve myself, I'm not a developer nor a GIT regular. Thanks for your recommendations.

@dregad
Copy link
Member

dregad commented Jun 3, 2020

This is indeed a feature I had considered but didn't feel like coding myself.

I'll take care of it.

I'm not a developer nor a GIT regular

Feel free to ask if you need help or advice.

@maturbet
Copy link
Contributor Author

maturbet commented Jun 3, 2020

Because an administrator can cause this bug, I designed this feature to prevent the selection of a default project, inaccessible to a user.

@maturbet
Copy link
Contributor Author

maturbet commented Jun 3, 2020

Feel free to ask if you need help or advice.

Is it better ? b8bb06338c
git pull upstream master
git push

@dregad dregad force-pushed the maturbet-fixredirectionloop branch from f1fcbf1 to 3753e20 Compare June 4, 2020 16:21
@dregad
Copy link
Member

dregad commented Aug 9, 2020

So I finally managed to finish testing this 😌
Thanks for your contribution.

I reworded the commit, merged in b162f8f

@dregad dregad closed this Aug 9, 2020
@dregad
Copy link
Member

dregad commented Aug 9, 2020

That being said, in terms of data integrity I don't think the users' default_project setting should contain an invalid project value, which can happen when a user is removed from the project, or when the project is deleted.

This is tracked in https://mantisbt.org/bugs/view.php?id=27144, fix is in #1691

@maturbet maturbet deleted the maturbet-fixredirectionloop branch August 10, 2020 06:56
Copy link

@tomasreyes tomasreyes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@maturbet maturbet restored the maturbet-fixredirectionloop branch August 12, 2020 07:15
@maturbet maturbet deleted the maturbet-fixredirectionloop branch August 12, 2020 07:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants