fix(tktrex): tktrex extension data-donation size check

[ascariandrea]

No description provided.

[vecna]

you keep it in WiP to add #382 or can I proceed with testing? thanks!

[ascariandrea]

I didn't have the chance to continue on this cause I've worked on YCAI the last days, but I can finalize it now

[ascariandrea]

@vecna ready to test 🧷

[vecna]

The extension works but seems it is sending something too much:

  parsers:description Retval is { description: '#foryourpage' } +5ms
  parsers:hashtags No hashtags for previous.nature { type: 'video', videoId: undefined, authorId: 'search' } +39ms
  parsers:numbers No numbers in previous.nature { type: 'video', videoId: undefined, authorId: 'search' } +39ms
  parsers:stitch No stitch for previous.nature { type: 'video', videoId: undefined, authorId: 'search' } +40ms
  parsers:author No hashtag for previous.nature { type: 'video', videoId: undefined, authorId: 'search' } +39ms

this is from the parser. but don't worry, I'll debug this part of the backend.

[vecna]

what I don't like is that all the messages/debug now looks from the same line:

and how I can control the verbosity of this log? because if I remove the "verbose" option, every log disappears

[vecna]

this is something that shouldn't happen:

only if there is an increment a new packet should be sent, but by debugging the background window you can see the events are duplicates

[vecna]

but beside the problems above, the patch works and the backend was ready for it:

video get accumulated by multiple of 12

[ascariandrea]

I fixed the duplicated videos in the POST /events request and debounced the mutation observer's callbacks to avoid useless run of the handlers.

To manage the log output you can use the filter bar to show only the log you want to see, or you can enable/disable then with the DEBUG variable used in yarn tk:ext watch (or yarn tk:ext build)

[vecna]

I can't understand which part of YCAI should be preserved, so I can't fix these conflicts...