# Where is Pijul / Pijul Nest bug tracker?

**URL:** <https://discourse.pijul.org/t/where-is-pijul-pijul-nest-bug-tracker/246>\
**Category:** Question\
**Created:** [November 28, 2018, 9:10pm UTC](https://discourse.pijul.org/t/where-is-pijul-pijul-nest-bug-tracker/246 "2018-11-28T21:10:18Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![vi0](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/vi0/32/132_2.png) [@vi0](https://discourse.pijul.org/u/vi0)\
**Post date:** [November 28, 2018, 9:10pm UTC](https://discourse.pijul.org/t/where-is-pijul-pijul-nest-bug-tracker/246/1 "2018-11-28T21:10:18Z")

</div>

Like other open source software, I expect there to be some public issue tracker.

For example, It can be a issues in a Github repository (the code inside may be content of latest Pijul release).

Here is some list of issues I’d submitted:

- Pijul asks for SSH key’s password even if it is already in ssh agent, if trying to use invalid account on Nest;
- Attempt to clone, but not providing a value password leaves incompletely cloned repository interfering with futher clone attempts;
- Missing verbose mode that shows details of SSH connection (but not that excessively verbose like `RUST_LOG=debug`). `RUST_LOG=info` shows seemingly nothing.
- Pijul’s SSH client asks password for the next key even when the password is the same as already entered password;
- Pijul asks password for “[nest.pijul.com](http://nest.pijul.com)” in a loop without even telling that it’s incorrect password. SSH keys’ protection passwords are asked once, but reaction to valid and invalid password is also the same.
- Documentation recommends cloning Pijul from the Nest using `pijul clone me@nest.pijul.com:pijul_org/pijul` command without specifying that `me` should be replaced by your account name (unlike in Github where `git@...` stays the same).

(that’s before cloning and playing with it).

---

<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:** [November 29, 2018, 7:53am UTC](https://discourse.pijul.org/t/where-is-pijul-pijul-nest-bug-tracker/246/2 "2018-11-29T07:53:45Z")

</div>

I’m not sure I understand the question, but we wrote Pijul to be better and more automated than Git (especially on merges), so we won’t use Git or GitHub now that Pijul is starting to work.

~~The bug tracker is [https://nest.pijul.com/pijul\_org/pijul/discussions](https://nest.pijul.com/pijul_org/pijul/discussions)~~

**Edit** : it’s actually [https://nest.pijul.com/pijul/pijul/discussions](https://nest.pijul.com/pijul/pijul/discussions)

Please check that you’re using the latest version before reporting a bug, though, I believe the problems you’re talking about were fixed by thrussh-keys 0.11.9 (and `cargo install pijul --force` will fix your problem).

---

<div class="post-metadata">

**Author:** ![azzamsa](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/azzamsa/32/331_2.png) [@azzamsa](https://discourse.pijul.org/u/azzamsa)\
**Post date:** [December 3, 2020, 9:22am UTC](https://discourse.pijul.org/t/where-is-pijul-pijul-nest-bug-tracker/246/3 "2020-12-03T09:22:42Z")

</div>

I am also looking for the same thing.

I am looking for the repository of the `nest`. I can’t find in the [exploler](https://nest.pijul.com/explore), nor in the [pijul org](https://nest.pijul.com/pijul)

---

<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:** [December 3, 2020, 9:38am UTC](https://discourse.pijul.org/t/where-is-pijul-pijul-nest-bug-tracker/246/4 "2020-12-03T09:38:04Z")

</div>

There’s no repository for the Nest, it isn’t open source yet. I hope to be able to make it open source in the future.

---

<div class="post-metadata">

**Author:** ![pksunkara](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/pksunkara/32/325_2.png) [@pksunkara](https://discourse.pijul.org/u/pksunkara)\
**Post date:** [December 4, 2020, 11:50pm UTC](https://discourse.pijul.org/t/where-is-pijul-pijul-nest-bug-tracker/246/5 "2020-12-04T23:50:36Z")

</div>

You should probably keep it closed source and build a business out of it to make pijul self-sustainable.

---

<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:** [December 5, 2020, 7:18am UTC](https://discourse.pijul.org/t/where-is-pijul-pijul-nest-bug-tracker/246/6 "2020-12-05T07:18:24Z")

</div>

Actually, I would like to open it completely _and_ build a business around it! I believe it is possible, but some things need a little bit more time and validation (and more people, if possible paid and full-time).

---

<div class="post-metadata">

**Author:** ![theduke](https://avatars.discourse-cdn.com/v4/letter/t/a183cd/32.png) [@theduke](https://discourse.pijul.org/u/theduke)\
**Post date:** [December 5, 2020, 2:35pm UTC](https://discourse.pijul.org/t/where-is-pijul-pijul-nest-bug-tracker/246/7 "2020-12-05T14:35:56Z")

</div>

@pmeunier you could create an empty `pijul/nest` respository that can be used for issue tracking / feature requests until Nest is open sourced.

My first request would be sorting and filtering of discussions.