Thanks to visit codestin.com
Credit goes to github.com

Skip to content

queue name can be anything while group_rate name is an atom #21

@benoitc

Description

@benoitc

I was trying to setup 2 queue sharing the same group_name but failed with a case_clause error while trying to use a tuple as a group_rate name. Creating the group name with a tuple is OK, but then passing this name when setting a queue fails with a case_clause error. AFaik the group name should match an atom there:

https://github.com/uwiger/jobs/blob/master/src/jobs_server.erl#L488

I'm not sure what should be fixed there. Either fixing the code above by not matching a specific type for the name. Or fixing jobs:add_group_rate/2 and raise a badarg error if the name is anything but atom.

Thoughts?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions