deno fmt panic #30980
Description
I upgraded to the latest Deno and ran deno fmt on my codebase. I can reproduce it consistently, but I am not sure what file is causing it. I don't know if it's the same as #30276 (--use-tabs does not help in my case)
============================================================
Deno has panicked. This is a bug in Deno. Please report this
at https://github.com/denoland/deno/issues/new.
If you can reliably reproduce this panic, include the
reproduction steps and re-run with the RUST_BACKTRACE=1 env
var set and include the backtrace in your report.
Platform: linux x86_64
Version: 2.5.4
Args: ["/home/alex/.asdf/installs/deno/2.5.4/bin/deno", "fmt"]
View stack trace at:
https://panic.deno.com/v2.5.4/x86_64-unknown-linux-gnu/iyjpyGoytypEgmtypEgltypEgjtypEg9xypEo926nGy_x6nGov--pGw2k6nG8uyguG44rguGgps7qEgmq7qEg7p7qEg9jlBqr0pCA
thread 'tokio-runtime-worker' panicked at /home/admin/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/dprint-core-0.67.4/src/formatting/writer.rs:98:9:
For some reason finish_indent was called without a corresponding start_indent.
stack backtrace:
0: 0x64cd73008e32 - <unknown>
1: 0x64cd730072e3 - <unknown>
2: 0x64cd7300706f - <unknown>
3: 0x64cd73008c93 - <unknown>
4: 0x64cd7300830e - <unknown>
5: 0x64cd75461bff - <unknown>
6: 0x64cd73006cde - <unknown>
7: 0x64cd73006ac5 - <unknown>
8: 0x64cd73006a59 - <unknown>
9: 0x64cd73006a4c - <unknown>
10: 0x64cd730073ef - <unknown>
11: 0x64cd74f2917f - <unknown>
12: 0x64cd74f277ca - <unknown>
13: 0x64cd75038fb7 - <unknown>
14: 0x64cd74f2668e - <unknown>
15: 0x64cd7523f53f - <unknown>
16: 0x64cd7523e966 - <unknown>
17: 0x64cd730aaa3b - <unknown>
18: 0x64cd730aa5ba - <unknown>
19: 0x64cd730aa3df - <unknown>
20: 0x7fe7daa94ac3 - start_thread
at ./nptl/pthread_create.c:442:8
21: 0x7fe7dab268c0 - __GI___clone3
at ./misc/../sysdeps/unix/sysv/linux/x86_64/clone3.S:81:0
22: 0x0 - <unknown>