You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've searched other issues and no duplicate issues were found.
I'm convinced that this is not my fault but a bug.
Description
An environment variable name tier4_simulator_launch_param_pathis defined HERE.
And the name is used in HERE. You can see the config directory is conflicting.
When I tried to use fault injection in the scenario simulator, I could not use the fault injection because of duplicate "config" directories.
Expected behavior
I can use Fault Injection in the scenario simulator.
Actual behavior
I cannot use Fault Injection in the scenario simulator.
Steps to reproduce
Run scenario simulator.
Publish a something fault injection.
Versions
No response
Possible causes
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
@Yukio247
Thank you for reporting, and sorry for my mistake. I did not test this modification on scenario simulator since it was a simple change.
I opened a PR to fix this issue: autowarefoundation#2281, which eventually will be merged into tier4/main branch in this repos.
Checklist
Description
An environment variable name
tier4_simulator_launch_param_path
is defined HERE.And the name is used in HERE. You can see the
config
directory is conflicting.When I tried to use fault injection in the scenario simulator, I could not use the fault injection because of duplicate "config" directories.
Expected behavior
I can use Fault Injection in the scenario simulator.
Actual behavior
I cannot use Fault Injection in the scenario simulator.
Steps to reproduce
Versions
No response
Possible causes
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: