DiamondLightSource / DiamondLightSource/dodal

Dodal connect better output

Open
#930 1 comment 0 reactions 0 assignees View on GitHub
bug documentation enhancement good first issue python
Dominant language
Python
Stars
5
Forks
13
Avg merge
3d 2h
Merged PRs (30d)
10

Description

When I connect to a beamline and it fails, I get a lot of error messages that are difficult to parse. I'd like a better CLI DX where I can see a number of PVs not connected `in total`, errors thrown due to int-enum mismatch etc.

Moreover when I run `dodal connect [beamline] > out.txt` only the connected devices get into the buffer, and the errors arrive later and I need to manually copy and paste for debugging. I'd like an `output` flag to the `connect` CLI command that keeps the terminal silent and just pipes all of the logs into some default path with a timestamp on my OS such as `tmp/logs/dodal/[beamline]-[timestamp].txt` or maybe even in Markdown so that I can see a clear nested structure with syntax and section highlighting

also
- `-v` verbose flag for the full output
- connect 1 device mode - to faster debug a particular device connection

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.