cannot create snippet from stdin
no open bug for this
https://gitlab.com/gitlab-org/cli/-/issues/?sort=created_date&state=opened&search=snippet&label_name%5B%5D=bug&first_page_size=20
### Checklist
<!-- Please test the latest versions, that will remove the possibility that you see a bug that is fixed in a newer version. -->
See below for versions.
- [x] I'm using the latest version of the extension (Run `glab --version`)
- Extension version: glab 1.86.0 (1ef884a6)
- [x] Operating system and version: Ubuntu 24.04.4 LTS
- [x] Gitlab.com or self-managed instance? gitlab.com
- [x] I have performed `glab auth status` to check for authentication issues
- [x] Run the command in debug mode (like `DEBUG=true glab mr list`) and attach any useful output
### Summary
<!-- Summarize the bug encountered concisely -->
unable to create gist^H^H^H^Hsnippet from stdin
### Environment
- OS: Ubuntu 24.04.4 LTS
- SHELL: fish 3.7.0
- TERM: ghostty 1.2.3
- GLAB: glab 1.86.0 (1ef884a6)
<!--
Please include any other information that you believe might be relevant
in debugging. For example, you may include a shell framework like oh-my-zsh
or other customizations like editing the prompt (PS1, PS2, and others).
-->
Other:
## Steps to reproduce
### What is the current _bug_ behavior?
Using example from docs:
https://docs.gitlab.com/cli/snippet/create/
> set DEBUG true echo "package main" | glab snippet new --title "Title of the snippet" --filename "main.go"
```
[git remote -v]
[git remote -v]
ERROR
Stdin required if no 'path' is provided.
```
<!-- What actually happens -->
### What is the expected _correct_ behavior?
create snippet
<!-- What you should see instead -->
### Relevant logs and/or screenshots
<!--- Paste the activity log from your command line -->
see above
> begin; set -lx DEBUG true; echo 'test' | glab snippet create --title 'test'; end
```
[git remote -v]
ERROR
If 'path' is not provided, 'filename' and stdin are required.
```
### Possible fixes
<!-- If you can, link to the line of code that might be responsible for the problem -->
presumably in how it checks whether bytes were received from stdin
issue