Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flowcept parsing issue #150

Open
tskluzac opened this issue Feb 27, 2024 · 2 comments
Open

Flowcept parsing issue #150

tskluzac opened this issue Feb 27, 2024 · 2 comments
Assignees

Comments

@tskluzac
Copy link
Collaborator

When Flowcept receives a MONITOR or TERMINATOR activity type, it receives the following Error written to the log from the message handler:

'str' object has no attribute 'agent_id'

We will need to pack agent_id into other message types.

@tskluzac tskluzac self-assigned this Feb 27, 2024
@renan-souza
Copy link
Collaborator

Or we can change this class https://github.com/ORNL/flowcept/blob/main/flowcept/flowceptor/adapters/zambeze/zambeze_dataclasses.py#L11
to make it optional. If we remove the @DataClass decorator from this class, all fields would be optional.

Whichever you think would make more sense for Zambeze.

I can make this change or feel free to create branch in flowcept repo and change this.

@renan-souza
Copy link
Collaborator

By the way, if you pull to the newest version of flowcept, you'll see that we can now observe multiple queues defined in the settings.yaml file.

https://github.com/ORNL/flowcept/blob/main/resources/sample_settings.yaml#L73

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants