-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Revert #1674 - failing tests #1722
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
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1722 +/- ##
==========================================
+ Coverage 85.31% 85.77% +0.45%
==========================================
Files 29 29
Lines 2002 2017 +15
==========================================
+ Hits 1708 1730 +22
+ Misses 186 181 -5
+ Partials 108 106 -2
Continue to review full report at Codecov.
|
#1674 seems to cause problems that are detected with #1671 . Maybe #1674 is correct ... who knows f72eaa4#diff-996f64128c7fffe6cc8254ea4e1ac3c5693956f86ab5c8952e525083cf14ca27L26 NB: #1671 is also strange. Line 503 in ea31edb
|
@aldas Maybe I'm missing something but, Why you reverted #1671? The issue is related to #1674, in particular the first call to g.Any() |
BTW, thanks for the advice on squashing commits 👍 |
its easy - I did not understand why it would do it twice - always twice. it looked more like a quick fix - not a real solution. what if it already ended with slash? |
Additional note: The behaviour of treating a It might make sense to take a deeper look into the topic first, which should be done in a new PR based as replacement for #1671 Currently I'm in favour of only reverting #1674 and opening a new PR to discuss better alternatives for #1671. Comments welcome. |
If the prefix already end with a slash, the slash at the end is required. |
anyway i'm not saying it must be reverted. I assumed everyone guilty - both PRs seemed to pass tests before both of them were merged so - revert everything, make master to ok again and check later. As far as I can remember trailing slash is a thing in Nginx and/or Apache location configuration directive. So you would add location sometimes as |
We will revert both and see what to do with the old PRs. |
reverts #1674
reverts #1671
NB: in future please use squash commits when merging - it is cleaner for history and reverting merged PRs is easier