Skip to content

Bug: Frontend changing values before displaying to the user #593

Description

@jwarner112

Encountered this just now, and it's interesting. I assume it's common enough a use case to justify mentioning here.

So, the use case: we're queueing batches of jobs to perform operations on individual pg table rows. I often use the "args" in the UI to link back and check on those rows. And in this case, the only arg we pass is the row's ID, a BIGINT.

But I kept seeing IDs that don't match up in the database. I notice they all end in 00.

I use the job's ID to go back and check the arguments, and sure enough. From the river_job.args for that job:

{"id": 1970670598291982290}

But from the UX:

{"id": 1970670598291982300}

So something in the frontend stack is rounding these enormous numbers.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions