smartcontractkit / smartcontractkit/chainlink
[NODE] 404 Page not found when a bridge is created with capital letters on its name
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.2k
- Forks
- 2k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 202
Description
Description
When a bridge is created and capital letters are used to name it (OpenWeatherMap was my case) bridge creation apparently succeeds but then the bridge is not usable (when creating jobs a "not all bridges exist" error comes up) and clicking on it in the list shown in the bridges tab I get a 404 Page not found page.
Basic Information
[replace this line with basic information about the issue you are experiencing, including but not limited to all relevant logs and any other relevant information, such as if you are using a Docker container to run the node, job specification, oracle contract address, transaction IDs, etc.]
- Network: Sepolia
- Operating System: Windows 10, WSL
- Commit: Chainlink Node 2.0.0 at commit [0970c819be6bb2b6714644c6d44509ddeffc2a24]
- Hosting Provider: Docker, self-hosted
- Startup Command: Followed docs "Running a node"
Steps to Reproduce
Simply create a bridge and give it a name with capital letters
Additional Information
Using all lower case letters solved the issue after having tried for two whole days anything else that came to mind (even deleting the node completely and starting over), so the issue is well established. Bridge creation should fail and warn the user to not use caps. Also, the docs even say that the bridge's names are case insensitive, which make it seem like caps are not a problem
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing bridge creation with a capitalized name on Chainlink Node 2.0.0 using the documented Docker startup, then inspect the bridge-creation, Bridges-tab, and job-validation paths. Done means capitalized names work consistently, or creation rejects them with a clear warning, matching the case-insensitive documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- backend, blockchain, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100