v1.0.26 thread 'main' panicked at /home/runner/work/goose/goose/.hermit/rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/slice.rs:522:50:
New version, returns the following error:
Goose is running! Enter your instructions, or try asking what goose can do.
thread 'main' panicked at /home/runner/work/goose/goose/.hermit/rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/slice.rs:522:50:
capacity overflow
Happens on linux, even if I'm not running any extensions, etc. Pretty much any session I run.
Here's my setup
~/projects/pipedb $ uname -a
Linux galaxy 6.13.12-061312-generic #202504200842 SMP PREEMPT_DYNAMIC Sun Apr 20 11:07:04 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
~/projects/pipedb $ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 24.04.2 LTS
Release: 24.04
Codename: noble
~/projects/pipedb $ goose --version
1.0.26
Also, this happens with Claude Sonnet 4
~/projects/pipedb $ goose session
starting session | provider: anthropic model: claude-sonnet-4-20250514
logging to /home/tom/.local/share/goose/sessions/20250609_155946.jsonl
working directory: /home/tom/projects/pipedb
Goose is running! Enter your instructions, or try asking what goose can do.
Context: ○○○○○○○○○○ 0% (0/32000 tokens)
Not sure if the 32,000 tokens thing is a clue - the sonnet model is much larger than that!
yeah, we are releasing a new version to resolve
can you try the new version? https://github.com/block/goose/releases/tag/v1.0.27
Sadly I still hit this
─── text_editor | developer ──────────────────────────
path: ~/projects/pipedb/web/web/static/css/map-controls.css
command: view
◐ Measuring semantic distance... 2025-06-10T01:21:05.543026Z ERROR goose::agents::agent: Error: Rate limit exceeded: Some(Object {"error": Object {"message": String("This request would exceed the rate limit for your organization (360ff382-7b7b-48d8-8fea-d665f29d9992) of 80,000 input tokens per minute. For details, refer to: https://docs.anthropic.com/en/api/rate-limits. You can see the response headers for current usage. Please reduce the prompt length or the maximum tokens requested, or try again later. You may also contact sales at https://www.anthropic.com/contact-sales to discuss your options for a rate limit increase."), "type": String("rate_limit_error")}, "type": String("error")})
at crates/goose/src/agents/agent.rs:747
Ran into this error: Rate limit exceeded: Some(Object {"error": Object {"message": String("This request would exceed the rate limit for your organization (360ff382-7b7b-48d8-8fea-d665f29d9992) of 80,000 input tokens per minute. For details, refer to: https://docs.anthropic.com/en/api/rate-limits. You can see the response headers for current usage. Please reduce the prompt length or the maximum tokens requested, or try again later. You may also contact sales at https://www.anthropic.com/contact-sales to discuss your options for a rate limit increase."), "type": String("rate_limit_error")}, "type": String("error")}).
Please retry if you think this is a transient or recoverable error.
thread 'main' panicked at /home/runner/work/goose/goose/.hermit/rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/slice.rs:522:50:
capacity overflow
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
But also a non-rate limit job hit this error
─── text_editor | developer ──────────────────────────
path: ~/projects/pipedb/web/web/static/js/core-map.js
command: str_replace
new_str: ...
old_str: ...
Perfect! Now I've made the following changes to fix the vertical overflow issue:
## Summary of Changes
### 1. **Reduced Default Segment Count**
- Changed `totalSegments` from `20` to `5` in all the legend methods
- This means for step-based mode, instead of 10 segments between each color pair, you'll get 5 segments between each pair
- If you have 4 color entries, it will create 4×5 + 1 = **21 segments** instead of 4×20 + 1 = **81 segments**
### 2. **Made Legend Height Dynamic**
- Replaced fixed `height: 350px` with `max-height: 300px` and `min-height: 80px`
- Added `height` to the transition property for smooth resizing
- The legend will now size itself based on content but stay within reasonable bounds
### 3. **Improved Responsiveness**
- The legend will now automatically fit the content without exceeding the max-height
- If you need more segments, you can always override by passing `totalSegments` explicitly
The changes should resolve the vertical overflow issue while maintaining the new step-based and value-based functionality you added. The legend will now be more compact by default but still provide good visual representation of your color gradients.
thread 'main' panicked at /home/runner/work/goose/goose/.hermit/rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/slice.rs:522:50:
capacity overflow
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
proof of version
~/projects/pipedb $ goose --version
1.0.27
and here's the model
~/projects/pipedb $ goose session
starting session | provider: anthropic model: claude-sonnet-4-20250514
logging to /home/tom/.local/share/goose/sessions/20250609_202133.jsonl
working directory: /home/tom/projects/pipedb
Goose is running! Enter your instructions, or try asking what goose can do.
Context: ○○○○○○○○○○ 0% (0/32000 tokens)
I get the same issue while using AWS Bedrock as a provider for both Amazon Nova Pro and Claude Sonnet 4. Those both have higher than 32k token windows as well, if that helps. Also on 1.0.27
Same problem with Github Copilot and model claude-sonnet-4
do you see the same error before 1.0.26? may I know how to reproduce it?
I get the error pretty much all the time. Repro: 1) Use Bedrock model provider, 2) enable computer controller and developer extensions, 3) do anything. I put some files in a folder and asked it to navigate to them and read a particular file. It seems to happen when the context is getting more full
do you see the same error before 1.0.26? may I know how to reproduce it?
Same error with 1.0.26.
Provider: openrouter anthropic/claude-sonnet-4 (with copilot agent doesn't work with tools) Extensions: computercontroller and developer Prompt: Help me search for high-definition album cover images of the last 10 years Grammy Award winners.
Context: ○○○○○○○○○○ 0% (0/32000 tokens)
thread 'main' panicked at /home/runner/work/goose/goose/.hermit/rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/slice.rs:522:50:
capacity overflow
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Sorry if this isn’t the right thread, but I’m seeing the same capacity overflow panic in Goose version 1.0.27.
starting session | provider: aws\_bedrock model: us.anthropic.claude-sonnet-4-20250514-v1:0
logging to /Users/<username>/.local/share/goose/sessions/20250611\_125203.jsonl
working directory: /Users/<username>
Goose is running! Enter your instructions, or try asking what goose can do.
Context: ○○○○○○○○○○ 0% (0/32000 tokens)
( O)> how many r's are in the word strawberry
Goose responds:
To count the number of 'r's in the word "strawberry", I'll examine each letter:
**s-t-r-a-w-b-e-r-r-y**
Looking at each position:
* s: not an 'r'
* t: not an 'r'
* r: **this is an 'r'** (1st r)
* a: not an 'r'
* w: not an 'r'
* b: not an 'r'
* e: not an 'r'
* r: **this is an 'r'** (2nd r)
* r: **this is an 'r'** (3rd r)
* y: not an 'r'
There are **3 r's** in the word "strawberry".
Then it crashes with:
thread 'main' panicked at /rustc/17067e9ac6d7ecb70e50f92c1944e545188d2359/library/alloc/src/slice.rs:522:50:
capacity overflow
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
🖥️ Platform Info
ProductName: macOS ProductVersion: 15.5 BuildVersion: 24F74
Let me know if there’s anything I can do to help debug this!
Hi,
Just want to add to the above issue. I am getting the following error message. When running with 1.0.27 version on MacOS
starting session | provider: aws_bedrock model: us.amazon.nova-premier-v1:0
logging to /Users/ldodda/.local/share/goose/sessions/20250611_143521.jsonl
Goose is running! Enter your instructions, or try asking what goose can do.
Context: ○○○○○○○○○○ 0% (0/32000 tokens)
thread 'main' panicked at /rustc/17067e9ac6d7ecb70e50f92c1944e545188d2359/library/alloc/src/slice.rs:522:50:
capacity overflow
stack backtrace:
0: 0x10526aa50 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h92dda645f072dcaf
1: 0x10528eb90 - core::fmt::write::hbc92919d8e8f9a96
2: 0x105265dc8 - std::io::Write::write_fmt::hcee3b5dc9ab531be
3: 0x10526a904 - std::sys::backtrace::BacktraceLock::print::h0f497abce563e5d2
4: 0x10526bb68 - std::panicking::default_hook::{{closure}}::h62595143a6c21f05
5: 0x10526b9b8 - std::panicking::default_hook::hd800536ed1df5085
6: 0x10526c648 - std::panicking::rust_panic_with_hook::h1882a30575fbb763
7: 0x10526c274 - std::panicking::begin_panic_handler::{{closure}}::h39275ef3005e6337
8: 0x10526af00 - std::sys::backtrace::__rust_end_short_backtrace::h6ede323c05a76849
9: 0x10526bf1c - __rustc[95feac21a9532783]::rust_begin_unwind
10: 0x10539e608 - core::panicking::panic_fmt::h529fda7ea817ba4f
11: 0x10539e5e8 - core::option::expect_failed::h5266eebf69f4aa13
12: 0x100a61e04 - alloc::slice::<impl [T]>::repeat::h464d6d682778678c
13: 0x100b725d8 - goose_cli::session::output::display_context_usage::hf97b6d7ba7b65378
14: 0x10073f894 - goose_cli::session::Session::interactive::{{closure}}::h4ca7e3265aabaec4
15: 0x100733968 - goose_cli::cli::cli::{{closure}}::h0da26108afd60977
16: 0x10072c650 - tokio::runtime::park::CachedParkThread::block_on::h3d427a26ba978502
17: 0x1008966d8 - tokio::runtime::context::runtime::enter_runtime::h6ddf3bbf09356ec8
18: 0x100838900 - goose::main::h47873e044d39ad44
19: 0x1008ee87c - std::sys::backtrace::__rust_begin_short_backtrace::hc37a8bf368feec56
20: 0x1009ca0e4 - std::rt::lang_start::{{closure}}::h544e8dd43282c96d
21: 0x10525c54c - std::rt::lang_start_internal::hdff9e551ec0db2ea
22: 0x100838b70 - _main
looks like caused by https://github.com/block/goose/pull/2315, looking into it
We have the fix in the new version, can you try to verify that? https://github.com/block/goose/releases/tag/v1.0.28
Thanks
Fixed! Thank you!!!