rubyforgood / rubyforgood/Flaredown
upgrading either rack or puma broke prod cors so I reverted, make the upgrade not do that
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 50
- Forks
- 21
- Avg merge
- 6d 12h
- Merged PRs (30d)
- 16
Description
This issue has no description.
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
No files, tests, or entry points are identified, and the issue body is empty. Start by reviewing the Rack and Puma upgrade history and the production CORS configuration, then reproduce the reported production breakage. Done means the upgrade no longer breaks production CORS and the relevant behavior is covered by a verification step.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100