`jhack tail` produces lots of "not found in history... simulating one" lines with Juju 4
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start with the jhack tail entry point and jhack/utils/tail_charms/core/processor.py, then reproduce the reported output with Juju 4. The issue does not yet provide reproduction steps or tests; done means the spurious “not found in history... simulating one” lines no longer appear during affected event tailing.
Written by the indexing model from the issue text.
Description
Bug Description
Listening for events...ERROR:jhack./home/ubuntu/.local/share/uv/tools/jhack/lib/python3.11/site-packages/jhack/utils/tail_charms/core/processor.py:mysql-k8s/0:mysql_pebble_ready not found in history... simulating one.
ERROR:jhack./home/ubuntu/.local/share/uv/tools/jhack/lib/python3.11/site-packages/jhack/utils/tail_charms/core/processor.py:mysql-k8s/1:mysql_pebble_ready not found in history... simulating one.
ERROR:jhack./home/ubuntu/.local/share/uv/tools/jhack/lib/python3.11/site-packages/jhack/utils/tail_charms/core/processor.py:mysql-k8s/2:mysql_pebble_ready not found in history... simulating one.
ERROR:jhack./home/ubuntu/.local/share/uv/tools/jhack/lib/python3.11/site-packages/jhack/utils/tail_charms/core/processor.py:mysql-k8s/0:config_changed not found in history... simulating one.
ERROR:jhack./home/ubuntu/.local/share/uv/tools/jhack/lib/python3.11/site-packages/jhack/utils/tail_charms/core/processor.py:mysql-k8s/2:config_changed not found in history... simulating one.
To Reproduce
(TBC)
Environment
juju info v0.1
┌──────────────┬───────────────────────────────────────────────────────────────┐
│ jhack │ 0.4.4.0.24 │
│ python │ 3.11.14 (/home/ubuntu/.local/share/uv/tools/jhack/bin/python) │
│ juju-* snaps │ juju │ 4.0.0 - 33191 (4.0/stable) │
│ microk8s │ Not Installed. │
│ lxd │ 5.21.4 LTS │
│ multipass │ Not Installed. │
│ multipassd │ Not Installed. │
│ os │ Ubuntu 24.04.3 LTS │
│ kernel │ Linux 6.8.0-88-generic x86_64 │
└──────────────┴───────────────────────────────────────────────────────────────┘
Relevant log output
(See above)
Additional context
No response
- Dominant language
- Python
- Stars
- 60
- Forks
- 31
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from canonical/jhack
-
canonical/jhack#234 · 2 comments · 1 reaction · 2 assignees ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100