Open Cynical-Optimist opened 4 years ago
In GitLab by [Gitlab user @tristanvb] on Sep 20, 2018, 11:12
Yes this is a bug.
Some clarifications:
bst build --track-all
), then it will be shown as ????????
So the above clearly appears to be a bug.
In GitLab by [Gitlab user @Qinusty] on Sep 20, 2018, 14:45
This is due to the message being produced by a source (The workspaced element main:5G.bst-0
) and message.task_id
is unset.
See original issue on GitLab In GitLab by [Gitlab user @Qinusty] on Sep 20, 2018, 10:57
Summary
During
bst workspace open
, various messages do not contain the associated elements cache key.Steps to reproduce
Open a workspace, observe output.
What is the current bug behavior?
Messages are produced without any cache key
What is the expected correct behavior?
All messages associated with the operation triggered for the element should contain its cache key.
Relevant logs and/or screenshots
Other relevant information