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
Not finished the backup #1
Comments
Just tried this and ran into the same issue. Maybe something to do with the transcript data for the specific day? |
I just got this, and it has to do with campfire throttling the data pull, from the last archive file pulled down...
Sounds like setting User-Agent header in the request will solve the issue. |
This just gets you to the next level of throttling:
|
Getting something similar. /usr/local/lib/node_modules/campfire-archive/lib/CampfireArchiver.js:245 |
Same for me. |
Same problem here |
This avoids the following issue: jbt#1
After put the token via web, I have a error:
Fetching 2013-6-14 for room 559196 from campfire
Fetching 2013-6-15 for room 559196 from campfire
Fetching 2013-6-16 for room 559196 from campfire
Fetching 2013-6-17 for room 559196 from campfire
/opt/boxen/nodenv/versions/v0.10.13/lib/node_modules/campfire-archive/lib/CampfireArchiver.js:245
transcript.messages.forEach(this.processTranscriptMessage.bind(this));
^
TypeError: Cannot call method 'forEach' of undefined
at CampfireArchiver.processTranscript (/opt/boxen/nodenv/versions/v0.10.13/lib/node_modules/campfire-archive/lib/CampfireArchiver.js:245:23)
at null. (/opt/boxen/nodenv/versions/v0.10.13/lib/node_modules/campfire-archive/lib/CampfireArchiver.js:238:12)
at /opt/boxen/nodenv/versions/v0.10.13/lib/node_modules/campfire-archive/lib/CampfireArchiver.js:209:13
at Object.oncomplete (fs.js:107:15)
This is it a bug?
The text was updated successfully, but these errors were encountered: