Skip to content
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

Updates to Entity values are not persisted #39

Open
fatbatman opened this issue Jul 3, 2017 · 6 comments
Open

Updates to Entity values are not persisted #39

fatbatman opened this issue Jul 3, 2017 · 6 comments

Comments

@fatbatman
Copy link

fatbatman commented Jul 3, 2017

After doing a git clone
lein repl
(run)

The Todo list shows but updates to entities fail with;

image

@fatbatman
Copy link
Author

fatbatman commented Jul 3, 2017

Which seems to be due to the way the logging is configured?

image

@metasoarous
Copy link
Owner

I don't think it has anything to do with the way logging is called. That's just the odd way exceptions bubble up in JS with try catch. I think... I could be wrong. Do you have any thoughts on this @bamarco?

@fatbatman
Copy link
Author

Does anyone happen to remember the last time this working on any DatSys branch/release?
It was working in an old Cayalysis branch I'd prefer not to go that far back.

fatbatman pushed a commit to fatbatman/datsync that referenced this issue Jul 13, 2017
@fatbatman
Copy link
Author

Somewhere in the call stack a nil gets added to the server-event giving it a length of 3 and so failing the validation.
I couldn't see where that was happening so it's possible it's some kind of clojurescript wierdness
Anyway, this fixes it fatbatman/datsync@ed549dd

@bamarco
Copy link
Collaborator

bamarco commented Jul 13, 2017

@metasoarous This seems like it might be somewhere in the datview code that is confused about sente events vs datsync events, maybe?

@metasoarous
Copy link
Owner

@fatbatman - good find! Thanks for tracking that down! The situation is that I needed to send transaction metadata at some point, and so I added a third entry to the vector. I had it working at some point, but something else must have changed that made that break. I wasn't totally satisfied with the hack I baked in anyway though. It might be better to use a separate event name in that case, something like [:send-tx-with-metadata [tx-forms metadata]].

@bamarco - It's possible that's why this started breaking.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants