Rob,
I recently changed how we handle categorization of linkTo events. In the past the categorization projection just handled resolved events, so it could not see your
‘pelanguage-’
streams.
However, it now receives unresolved events too and additionally categorizes events by links referring them.
So, if linkTos were processed several days ago it may be an issue.
Please let me know, if reprocessing helped.
-yuriy
Can you give me an exact sample?
I’m not using the .NET API to save events to the store, I was using the JS code I stole from somewhere else in the project - did I forget something?
These messages are coming from the HTTP interface. Probably when you are browsing streams with the streams UI.
However, the fact that it cannot de-serialize JSON with Newtonsoft parser means either invalid JSOn or something wrong with parsing.
Let’s check if projections get these events.
I suppose it is posting events via http. Does it submit correct content-type? application/json?
Projections since several days ago do not attempt to deserialize events that are not marked as json.
Yes
https://github.com/robashton/githubinfograph/blob/master/src/es.js
You’ll recognise the code
The JSON itself is coming almost directly from Github, although I do a
JSON.parse
and then a
JSON.stringify
So it’s valid JSON - the only thing left there is “is it all being set up correctly”
Is this going to be at all related to the category stuff? (Given that all the other projections are working fine)
It can only be related to how we categorize events. fromCategory(‘a’) is almost identical to fromStream(’$ce-a’).
Do you see right events if you browse $ce-CATEGORYNAME stream?
yes, I do
I’m confused though, I appear to have some artifacts left over from the last test - is there something else I have to delete other than the data directory?
clear browser cache. all the responses that hold immutable data expire in a month.
What do I need to start github import here?
git clone https://github.com/robashton/githubinfograph
npm install
create a config.js with
{
“auth”: "?client_id=MY_CLIENT_ID&client_secret=MY_CLIENT_SECRET
}
Client_id and client_secret can be gotten from Github on https://github.com/settings/applications/new (callback URL is irrelevant)
(Obviously you need nodeJS)
will try
ok, for the beginning I see these de-serialization errors. starting with debugger.
I’m glad you’ve pulled this down - either you can tell me what I’m doing wrong or see what is going wrong, I’ve pushed my event store posts back to the 25th onwards so we’ve still got loads of time 
Rob
I traced JSON truncation back to es.js. I’ll clear my DB and try your projection.
OK, I see the same problem as you get. Let me find out why event categorization does not build pushlanguage category.
phew at least one of my things isn’t clearly my fault
I was too lazy to write exhaustive unit test for this
Fixing…