Ray Chen
Ray Chen
I noticed that the `Proxy-Authorization` header was being inserted as a value in the `Authorization: ..` header when using `RequestAuth.Proxy(..)`. 1) Using `requests.RequestAuth.Proxy`: ```scala @ val reqProxy = requests.RequestAuth.Proxy("username", "password")...
Reproduction: ```php >>> use PHPHtmlParser\Dom; >>> $dom = new Dom; >>> $dom->loadFromUrl("https://casper.com/gifts/?clickid=T02U6OVQYxyLUbdwUx0Mo36dUkB1HNWwiSMnwQ0"); ``` Throws: ``` PHP Warning: mb_eregi_replace(): mbregex search failure in php_mbereg_replace_exec(): retry-limit-in-match over in /paquettg/php-html-parser/src/PHPHtmlParser/Dom/Cleaner.php on line 81...
I can't reproduce this reliably, but go to https://docs.railway.app/reference/cli-api and click around anchor links and you'll land on a different section than intended after a few clicks. This seems related...
On https://docs.railway.app/troubleshoot/fixing-common-errors: The top-level examples (everything under `Node / Express`) should be underneath the "Solution" section. I'm worried we're nesting too much here, perhaps splitting this out to a separate...
The search modal currently looks bare. Going to collab w/ @jitachi on this in the coming weeks. Related to #248, might want a dedicated page we can mount as a...
https://docs.railway.app/search?q=foobar should bring users to search results for `foobar`.
We're doing `process.env.foo ?? ""` and checking for non-empty strings everywhere that uses the env var. We should centralize this into a config module and perform all the checks upfront...
The way we're importing stuff is scattered: there are relative references (`import foo from '../../'`), paths-based references (`import foo from @/..`), and const/default exports are not super clear. It'd be...
1. Have `strict=true` in tsconfig 2. Build project 3. Receive error: ``` ./node_modules/typeid-ts/src/lib/basics.ts:6:5 Type error: Variable 'uuidv7' implicitly has type 'any' in some locations where its type cannot be determined....
https://platform.openai.com/docs/guides/chat/introduction Currently, all prompts are sent as `role=user`. The endpoint supports `(system, user, assistant)` as roles. I skipped this in the current version because it doesn't appear to be valuable...