burn icon indicating copy to clipboard operation
burn copied to clipboard

To see the logs and panic need to compile release version.

Open oiwn opened this issue 6 months ago • 0 comments

Describe the bug I'm trying to train the model. There is inconsistency between debug and release version or I'm doing it wrong. If I run it like cargo run -- model train I do not see any logs if something causing application to fail. To see the logs I have to do some kind of dirty hack, compile as release version (and painc="abort"). In this case I can see what's going on:

2024-07-25T01:57:26.754083Z  INFO wgpu_core::instance: Adapter Metal AdapterInfo { name: "Apple M1 Pro", vendor: 0, device: 0, device_type: IntegratedGpu, driver: "", driver_info: "", backend: Metal }
thread 'main' panicked at /Users/username/.cargo/registry/src/index.crates.io-6f17d22bba15001f/burn-tensor-0.13.2/src/tensor/api/float.rs:181:9:
                                                                                                                                                                  === Tensor Operation Error ===
           Operation: 'Matmul'
                                Reason:
                                           1. The inner dimension of matmul should be the same, but got 12 and 8. Lhs shape [128, 12], rhs shape [8, 128].

                                                                                                                                                           stack backtrace:
                                                                                                                                                                           note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
                                                                           fish: Job 1, 'RUST_BACKTRACE=1 ./app model …' terminated by signal SIGABRT (Abort)

I use latest version of Burn framework: 0.13 with ["wgpu", "train"]

To Reproduce Write an burn app which will compile but cause panic. Run with cargo run and run compiled into release mode app with panic = "abort".

Expected behavior I would like to see panics in debug version also.

Desktop (please complete the following information):

  • OS: iOS
  • Browser: safari
  • Version: Sonoma 14.5

As far as I understand it can be that TUI switching into the Alternate Screen and logs go there.

oiwn avatar Jul 25 '24 01:07 oiwn