Non of the code runs in chapter 11 (Can't set headers after they are sent)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- coffeescript, express, node.js
- Domain
- backend
Research direction
Start by running one of the chapter 11 examples with the listed CoffeeScript, Express, and Node versions, then trace the reported failure into src/controllers/responders/responder.js. Compare the other chapter 11 examples to determine whether they reach the same responder path; done means the chapter examples run without the reported headers error.
Written by the indexing model from the issue text.
Description
If you try running any code in chapter 11 you get the same error "Can't set headers after they are sent"
Express 3.0.0beta7
CoffeeScript version 1.3.3
Node v0.8.2
http.js:644
throw new Error('Can't set headers after they are sent.');
^
Error: Can't set headers after they are sent.
at ServerResponse.OutgoingMessage.setHeader (http.js:644:11)
at ServerResponse.res.setHeader (/Users/work/todo/node_modules/express/node_modules/connect/lib/patch.js:62:20)
at ServerResponse.res.header (/Users/work/todo/node_modules/express/lib/response.js:280:8)
at ServerResponse.res.json (/Users/work/todo/node_modules/express/lib/response.js:135:8)
at Create.global.Responder.Responder.complete (/Users/work/todo/src/controllers/responders/responder.js:27:25)
at Promise.__bind (/Users/work/todo/src/controllers/responders/responder.js:3:63)
at Promise.addBack (/Users/work/todo/node_modules/mongoose/lib/promise.js:120:8)
at Promise.EventEmitter.emit (events.js:88:17)
at Promise.emit (/Users/work/todo/node_modules/mongoose/lib/promise.js:59:38)
at Promise.complete (/Users/work/todo/node_modules/mongoose/lib/promise.js:70:20)
- Dominant language
- CoffeeScript
- Stars
- 62
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from markbates/Programming-In-CoffeeScript
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
Difficulty 1/5 Under an hour Newbie friendliness 45/100
markbates/Programming-In-CoffeeScript#3 · 1 comment ·
-
chpt 10 Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
markbates/Programming-In-CoffeeScript#2 · 2 comments ·
All issues in markbates/Programming-In-CoffeeScript
Similar issues
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100