Skip to content
This repository was archived by the owner on Jan 10, 2019. It is now read-only.
This repository was archived by the owner on Jan 10, 2019. It is now read-only.

did not gracefully handle feedtype migration #16

@mwhooker

Description

@mwhooker

Our application started off using thoonk.job('our_job'). Later we created our own job type, but when we called thoonk.new_job('our_job'), our application behaved unexpectedly because the job class returned was a thoonk Job. We weren't able to resolve this issue until we did a redis flushdb.

I would have expected the job class used to be a function of our access to Thoonk.feedtypes, and not whatever is stored in redis.

If you need help reproducing I can come up with a script.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    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