If a use case utilizes instance identifiers (see Instance Names in Process List), then different RUN_ID values are logged.
Expected Behavior
The same run ID should be used in all logs for a given METplus run.
Environment
Describe your runtime environment: Any
To Reproduce
Describe the steps to reproduce the behavior:
1. Copy METplus/parm/use_cases/met_tool_wrapper/Example/Example.conf to another directory2. Modify the config to change the process list and add an instance header:
Change:
PROCESS_LIST = Example
to:
PROCESS_LIST = Example, Example(my_instance)
[my_instance]
[config]
[ ] Submit a pull request to merge into main_\.
Pull request: bugfix <Issue Number> main_<Version> <Description>
[ ] Define the pull request metadata, as permissions allow.
Select: Reviewer(s) and Development issue
Select: Milestone as the next bugfix version
Select: Coordinated METplus-X.Y Support project for support of the current coordinated release
[ ] Iterate until the reviewer(s) accept and merge your changes.
[ ] Delete your fork or branch.
[ ] Complete the steps above to fix the bug on the develop branch.
Branch name: bugfix_<Issue Number>_develop_<Description>
Pull request: bugfix <Issue Number> develop <Description>
Select: Reviewer(s) and Development issue
Select: Milestone as the next official version
Select: METplus-Wrappers-X.Y.Z Development project for development toward the next official release
Describe the Problem
If a use case utilizes instance identifiers (see Instance Names in Process List), then different RUN_ID values are logged.
Expected Behavior
The same run ID should be used in all logs for a given METplus run.
Environment
Describe your runtime environment: Any
To Reproduce
Describe the steps to reproduce the behavior: 1. Copy METplus/parm/use_cases/met_tool_wrapper/Example/Example.conf to another directory 2. Modify the config to change the process list and add an instance header:
Change:
to:
3. Run use case and review ID values in the logs:
Relevant Deadlines
List relevant project deadlines here or state NONE.
Funding Source
Define the source of funding and account keys here or state NONE.
Define the Metadata
Assignee
Labels
Milestone and Projects
Define Related Issue(s)
Consider the impact to the other METplus components.
Bugfix Checklist
See the METplus Workflow for details.
[ ] Complete the issue definition above, including the Time Estimate and Funding Source.
[ ] Fork this repository or create a branch of main_\ .
Branch name:
bugfix_<Issue Number>_main_<Version>_<Description>
[ ] Fix the bug and test your changes.
[ ] Add/update log messages for easier debugging.
[ ] Add/update unit tests.
[ ] Add/update documentation.
[ ] Add any new Python packages to the METplus Components Python Requirements table.
[ ] Push local changes to GitHub.
[ ] Submit a pull request to merge into main_\ .
Pull request:
bugfix <Issue Number> main_<Version> <Description>
[ ] Define the pull request metadata, as permissions allow. Select: Reviewer(s) and Development issue Select: Milestone as the next bugfix version Select: Coordinated METplus-X.Y Support project for support of the current coordinated release
[ ] Iterate until the reviewer(s) accept and merge your changes.
[ ] Delete your fork or branch.
[ ] Complete the steps above to fix the bug on the develop branch. Branch name:
bugfix_<Issue Number>_develop_<Description>
Pull request:bugfix <Issue Number> develop <Description>
Select: Reviewer(s) and Development issue Select: Milestone as the next official version Select: METplus-Wrappers-X.Y.Z Development project for development toward the next official release[ ] Close this issue.