search

ShelbyTV / shelby_gt

Rails API services for Shelby GT
2 stars 0 forks source link

Frames referencing conversations that don't exist #101

Closed iceberg901 closed 12 years ago

iceberg901 commented 12 years ago

Examples:

On Roll 4fccc6e4b415cc7f2100092d:

Frame 4feddc55b415cc0fcf0001f5 references conversation_id 4feddc55b415cc0fcf0001f3 Frame 4fec5dfbb415cc5e8f000b9c references conversastion_id 4fec5dfbb415cc5e8f000b9a

On Roll 4fdf3d27b415cc69340008f8

Frame 4fedbfacb415cc641b0009f3 references conversation_id 4feddc55b415cc0fcf0001f3

Those conversation ids do not exist. This causes big problems for the front end as all conversation creation occurs on the backend as a side effect of other RESTful operations, so once the front end receives a frame with a bad conversation it has no way to recover.

@hubdaba Both of these frames were created by you last week, so I can't help asking if this could be bookmarklet/extension related?

spinosa commented 12 years ago

@hubdaba It's really important that we understand how this happened. Since you've been working on bookmarklet, and both of these are in your account, that really narrows down the possible ways this could have happened. (Not necessarily your fault)

Please investigate and hypothesize how these could have come about.

iceberg901 commented 12 years ago

@hubdaba I've updated the initial issue to take note of the fact that I've found this problem on another roll. The problematic frame, again, has your name on it and was created last week while you were working on bookmarklet/extension. Please look into the points where you are hitting the API and see what could be causing this.

spinosa commented 12 years ago

closing as this hasn't been seen since, and it seems quite possible that this was caused by dev on the bookmarklet