no traces

[waalge]

What Git revision are you using?

aiken v1.0.24-alpha+b6b57c7

What operating system are you using, and which version?

nixos

Describe what the problem is?

[2 || jes] [aik] (main**) [impure]
$aiken build && wc plutus.json
    Compiling aiken-lang/stdlib ...
  1515   3379 101620 plutus.json
[2 || jes] [aik] (main**) [impure]
$aiken build --filter-traces all && wc plutus.json
    Compiling aiken-lang/stdlib ...
  1515   3379 101620 plutus.json

What should be the expected behavior?

I've lots of traces, this should be much bigger.

[waalge]

Previously on 49bd4ba33d9fd99180cd77321ad799e19f23c6ba.

Running here:

$aiken build && wc plutus.json
 1515  3379 87116 plutus.json
[2 || jes] [aik] (main**) [impure]
$aiken build -k  && wc plutus.json
  1515   3379 127918 plutus.json

[MicroProofs]

Make sure to set both trace level and filter traces

-f, --filter-traces Filter traces to be included in the generated program(s).

• user-defined: only consider traces that you've explicitly defined (either through the 'trace' keyword of via the trace-if-false ('?') operator.
• compiler-generated: only included internal traces generated by the Aiken compiler, for example in usage of 'expect'.
• all: include both user-defined and compiler-generated traces. [optional] [default: all] [possible values: user-defined, compiler-generated, all] -t, --trace-level Choose the verbosity level of traces:
• silent: disable traces altogether
• compact: only culprit line numbers are shown on failures
• verbose: enable full verbose traces as provided by the user or the compiler

[MicroProofs]

trace-level is silent by default.

[waalge]

yeah - that works. Any point in being able to use filter-traces when on trace-level is silent?

[KtorZ]

Reopening to make sure we address that last point. We should raise a warning / meaningful error when this occurs.

[waalge]

edit : moved comment to https://github.com/aiken-lang/aiken/discussions/868