-
Notifications
You must be signed in to change notification settings - Fork 33
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
Logs cut leading zeroes of addresses #67
Comments
@janhesters this is actually not framework, but rather Cadence itself :) And I absolutely love that log spy! ❤️ |
@MaxStalker If I understand the issue you linked correctly, this was fixed on November 4th? So I was wondering, why is this still in the emulator? Am I misreading something? |
@janhesters Oh... I thought that maybe CLI is still using old Cadence version, but it's on @SupunS or @turbolent can you check why the issue still there? |
I assume it is because even though this was fixed on master, the |
Problem
Logs cut leading zeroes of addresses.
(Related to #65 (comment)).
Steps to Reproduce
flow.json
:Transaction (in
cadence/transactions/log-signers.cdc
):Test:
This test fails and claims the second argument is
false
. The address ofAlice
is0x01cf0e2f2f715450
. But the output ofconsole.log(transactionLogs)
is:If you look closely, you'll see that it says
0x1cf0e2f2f715450
, so its missing the zero after thex
:0x01cf0e2f2f715450
.Acceptance Criteria
Logging no longer cuts leading zeroes of addresses.
Context
A test that does assertions on logs inside of transactions.
The text was updated successfully, but these errors were encountered: