snowplow / snowplow/snowplow-javascript-tracker
Very rare issue with invalid null in change form event's value property
Open
Nobody has claimed this yet.
category:help_wanted
priority:low
status:needs_triage
type:defect
- Dominant language
- TypeScript
- Stars
- 590
- Forks
- 232
- Avg merge
- 2h 22m
- Merged PRs (30d)
- 3
Description
userid | 101
slice | 0
tbl | 108333
starttime | Fri Sep 02 2016 01:40:54 GMT+0000 (UTC)
session | 31472
query | 1722582
filename | s3://xxx/shredded/good/run=2016-09-02-01-00-30/com.snowplowanalytics.snowplow/change_form/jsonschema/1-0-0/part-00000-00012.gzip
line_number | 490
colname | value
type | varchar
col_length | 2048
position | 246
raw_line | com.snowplowanalytics.snowplow|change_form|jsonschema|1-0-0|25a24d60-9fef-4e32-8354-2a9fb15bdd99|2016-09-01 21:27:43.000|events|["events","change_form"]|events|new_review|review[description]|TEXTAREA|
raw_field_value | ..
err_code | 1218
err_reason | Invalid null byte - field longer than 1 byte
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names no files, tests, or entry points. Begin by locating the change_form event value handling and tracing how an invalid null byte could enter the value field, then reproduce the reported case; done means the cause is understood and the invalid event value is handled without the reported load error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- analytics, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100