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
When producing the broadcast file after running forge script, some arguments were improperly set. Given their unicode aspect, I'm assuming this is styling/formatting related. I've pasted the file's content below. Please note the arguments, more specifically "500000000000 \u001b[2;49;39m[5e11]\u001b[0m", and "250000000000 \u001b[2;49;39m[2.5e11]\u001b[0m",, where the original args were simply "500000000000" and "250000000000" - this happened for all deployed contracts from this script, specifically for this field
While not a huge issue, kind of a pain since I run scripts that consume this json and depend on the correct values.
Component
Forge
Have you ensured that all of these are up to date?
What version of Foundry are you on?
forge 0.2.0 (08a629a 2023-06-03T00:14:26.563741000Z)
What command(s) is the bug in?
forge script
Operating System
macOS (Apple Silicon)
Describe the bug
When producing the
broadcast
file after runningforge script
, some arguments were improperly set. Given their unicode aspect, I'm assuming this is styling/formatting related. I've pasted the file's content below. Please note thearguments
, more specifically"500000000000 \u001b[2;49;39m[5e11]\u001b[0m",
and"250000000000 \u001b[2;49;39m[2.5e11]\u001b[0m",
, where the original args were simply"500000000000"
and"250000000000"
- this happened for all deployed contracts from this script, specifically for this fieldWhile not a huge issue, kind of a pain since I run scripts that consume this json and depend on the correct values.
The text was updated successfully, but these errors were encountered: