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 create promise #261

Closed
bsoule opened this issue Aug 28, 2018 · 4 comments
Closed

can't create promise #261

bsoule opened this issue Aug 28, 2018 · 4 comments
Labels
BUG MEN Mendoza = need to resolve before accepting more beta users UVI User-Visible Improvement zap (closed as) fixed

Comments

@bsoule
Copy link
Contributor

bsoule commented Aug 28, 2018

wrote this promise down in slack some hours ago, and when i clicked on it just now got this really weird behavior and it won't create the promise. the page is "creating your promise..." and the status bar thingie keeps filling and then dropping, and the promise is never created and if I try to go to that address again it still barfs in the same way.

i successfully created another promise the same way just minutes earlier.

I have a screen capture of the bug, along with the js console output. maybe i'll upload that to slack.

@bsoule
Copy link
Contributor Author

bsoule commented Aug 28, 2018

/create-test-promise-2154 successfully creates a promise, but
/review-gmail-auth-PR-test still fails in the same manner as /review-gmail-auth-PR

could the bot-detection code have labelled me a bot because Slack tried to autofetch/prefetch those URLs after I initially typed them, but then no one clicked on them until hours later?

@dreeves dreeves added MEN Mendoza = need to resolve before accepting more beta users BUG UVI User-Visible Improvement labels Aug 28, 2018
@dreeves
Copy link
Contributor

dreeves commented Aug 28, 2018

ha, i figured it out. capital letters! we redirect to canonicalize the URL or something.

i'm actually in favor of solving this by doing no canonicalizing whatsoever. the urtext is exactly what the user typed -- completely case-sensitive and not trying to clean up any extra underscores or anything like that.

@dreeves
Copy link
Contributor

dreeves commented Aug 28, 2018

Case-insensitivity is the default with the Express router but there's a setting to turn it off. One of these:

app.set('case sensitive routing', true)
router = express.Router({ caseSensitive: true })

I've also heard someone say you need to use regex-based routing instead of string-based routing to make case-sensitivity work. I doubt that's true but there may be other reasons to prefer regex-based routing anyway.

@chrisbutler
Copy link
Member

@dreeves setting that case-insensitivity wouldn't work for our case... and trust me, it's worth lowercasing the urls, if we didn't you'd be filing an issue for it

you really want regex routing, eh? lol

@dreeves dreeves added the zap (closed as) fixed label Oct 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BUG MEN Mendoza = need to resolve before accepting more beta users UVI User-Visible Improvement zap (closed as) fixed
Projects
None yet
Development

No branches or pull requests

3 participants