# Have I hit a nest limit?

**URL:** <https://discourse.pijul.org/t/have-i-hit-a-nest-limit/263>\
**Category:** Question\
**Created:** [January 15, 2019, 8:21am UTC](https://discourse.pijul.org/t/have-i-hit-a-nest-limit/263 "2019-01-15T08:21:39Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rohan](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/rohan/32/99_2.png) [@Rohan](https://discourse.pijul.org/u/Rohan)\
**Post date:** [January 15, 2019, 8:21am UTC](https://discourse.pijul.org/t/have-i-hit-a-nest-limit/263/1 "2019-01-15T08:21:39Z")

</div>

While trying to push the large repo which has been giving me conflict issue to the nest I’ve got into a state where no additional patches are pushed. Instead a long response like this is displayed in the console. These are patch IDs. There is no stack trace.

```auto
TaBPfsw8nxZ5jBNrZTx6gicMvqgz1s3vxR4N5Lo5ga9b:2139
6Q8v8E6KSuLMGKh5rwbVDXLvadf7epuNWy9TpgSB6dhdefzHRfA6xqC7G4KkCNcfwS4kfnYboziJGm6o4x3p3XPz:2140
99ENSgEvagC8B3ypNehGCuadHLKxvznzJ5XuAQmfD5WAi6hAxUUtZdxrfjjx5p2bRjNBBkPMH5ryzvocwTGZKUdT:2141

```

---

<div class="post-metadata">

**Author:** ![pmeunier](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/pmeunier/32/4_2.png) [@pmeunier](https://discourse.pijul.org/u/pmeunier)\
**Post date:** [February 23, 2019, 11:16pm UTC](https://discourse.pijul.org/t/have-i-hit-a-nest-limit/263/2 "2019-02-23T23:16:23Z")

</div>

Sorry for the late answer, there are no hard limits in the Nest currently. I’d have to investigate the situation closer to understand what happened. We had a performance bug recently while listing files touched by a patch, but this is supposed to be fixed.

If you still have the problem, I’m totally willing to investigate it, you can send me a tarball at [pe@pijul.org](mailto:pe@pijul.org).

---

<div class="post-metadata">

**Author:** ![Rohan](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/rohan/32/99_2.png) [@Rohan](https://discourse.pijul.org/u/Rohan)\
**Post date:** [July 4, 2019, 10:26am UTC](https://discourse.pijul.org/t/have-i-hit-a-nest-limit/263/3 "2019-07-04T10:26:31Z")

</div>

I’ve dug into the issue and it looks like there’s some buffer handling issues in pijul push itself as increasing the window\_size and maximum\_packet\_size in thrussh avoids this issue. Working out where the packet is being dropped has exceeded my Rust-fu.

That repo I sent you for the cyclic repo corruption will trigger this

---

<div class="post-metadata">

**Author:** ![Rohan](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/rohan/32/99_2.png) [@Rohan](https://discourse.pijul.org/u/Rohan)\
**Post date:** [July 4, 2019, 10:38am UTC](https://discourse.pijul.org/t/have-i-hit-a-nest-limit/263/4 "2019-07-04T10:38:29Z")

</div>

Note that patches are pushed successfully - the issue is around determining which haven’t been pushed yet