-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Labels
Description
Sometimes when a user tries to go back to the previous dimension, a similar border condition is encountered and a server error is thrown. This is an issue with the way we are bringing the next batch of photos. This issue is hard to reproduce but occurs often.
This is the server console output:
getIndexOfDimensionID dimension_id = 24 center =23
getDimensionCounts name
obtained dimension counts from DB. Size: 490
getPreviousPhotos dimension_id:1
returnPreviousPhotosFromDimensionID dimension_id=1
/Users/damaderu/Documents/uniandes/temp/photoringSQL/node_modules/mysql/lib/protocol/Parser.js:80
throw err; // Rethrow non-MySQL errors
^
TypeError: Cannot read property 'dimension_name' of undefined
at Query._callback (/Users/damaderu/Documents/uniandes/temp/photoringSQL/server.js:124:32)
at Query.Sequence.end (/Users/damaderu/Documents/uniandes/temp/photoringSQL/node_modules/mysql/lib/protocol/sequences/Sequence.js:88:24)
at Query._handleFinalResultPacket (/Users/damaderu/Documents/uniandes/temp/photoringSQL/node_modules/mysql/lib/protocol/sequences/Query.js:139:8)
at Query.EofPacket (/Users/damaderu/Documents/uniandes/temp/photoringSQL/node_modules/mysql/lib/protocol/sequences/Query.js:123:8)
at Protocol._parsePacket (/Users/damaderu/Documents/uniandes/temp/photoringSQL/node_modules/mysql/lib/protocol/Protocol.js:279:23)
at Parser.write (/Users/damaderu/Documents/uniandes/temp/photoringSQL/node_modules/mysql/lib/protocol/Parser.js:76:12)
at Protocol.write (/Users/damaderu/Documents/uniandes/temp/photoringSQL/node_modules/mysql/lib/protocol/Protocol.js:39:16)
at Socket.<anonymous> (/Users/damaderu/Documents/uniandes/temp/photoringSQL/node_modules/mysql/lib/Connection.js:103:28)
at Socket.emit (events.js:182:13)
at addChunk (_stream_readable.js:277:12)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! photoRing@1.0.0 start: `node server.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the photoRing@1.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/damaderu/.npm/_logs/2018-09-11T15_42_00_130Z-debug.log
Reactions are currently unavailable
