Reduce noise in Debug impl of RuntimeVariableList

[jimmygchen]

Issue Addressed

The default debug output of these types contains a lot of unnecessary noise making it hard to read.

This PR removes the type and extra fields from debug output to make logs easier to read.

len could be potentially useful in some cases, but this gives us flexibility to only log it separately if we need it.

Related PR in ssz_types:

• Reduce noise in Debug impl of VariableList and FixedVector ssz_types#57

RuntimeVariableList

Before

Before:

RuntimeVariableList { vec: [42, 42, 42, 42], max_len: 4 }

After:

[42, 42, 42, 42]

RuntimeFixedVector

Before

RuntimeFixedVector { vec: [42, 42, 42, 42], len: 4 }

After

[42, 42, 42, 42]

[mergify]

Some required checks have failed. Could you please take a look @jimmygchen? 🙏

[michaelsproul]

The max_len doesn't seem as nasty as the typenum we were logging in ssz_types, but happy to remove it anyway.

I guess having it could sometimes be useful for debugging config issues? Similar to what Pawan suggested on the ssz_types PR:

• sigp/ssz_types#57 (comment)

[jimmygchen]

The max_len doesn't seem as nasty as the typenum we were logging in ssz_types, but happy to remove it anyway.

I guess having it could sometimes be useful for debugging config issues? Similar to what Pawan suggested on the ssz_types PR:

• sigp/ssz_types#57 (comment)

Yep I can implement something like

[42, 42, 42, 42] (max_len=4)
[42, 42, 42, 42] (len=4)

[mergify]

Some required checks have failed. Could you please take a look @jimmygchen? 🙏

[michaelsproul]

Looks nice

[mergify]

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

• ☑️ test-suite-success

You can check the last failing draft PR here: #8019.

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[michaelsproul]

@mergify requeue

[mergify]

requeue

✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically