-
-
Notifications
You must be signed in to change notification settings - Fork 12.9k
zsh-history-enquirer 1.3.0 (new formula) #154416
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
You will need to move this into the |
d0c5f45
to
fbb7b8f
Compare
c00f31e
to
f17b042
Compare
@p-linnane Done. |
I can take a look at the linux build failure tomorrow |
|
cc: @zthxxx, as I don’t have a Linux VM set up, or time to debug this one specific use case I don’t personally have… |
you can just use either codespace or linux action runner + tmate like what I did in here, https://github.com/chenrui333/github-action-test/blob/main/.github/workflows/brew-debug.yml#L49-L67 |
@danielbayley can you just file an upstream linux build issue report and we can do |
@chenrui333 Sure, filed here: zthxxx/zsh-history-enquirer#73.
|
It can run exactly under Linux Zsh; I also use it on all of my servers. I noticed that the CI has failed due to the unit-test. Is that the problem with the test scripts? |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
e441c54
to
c395857
Compare
Co-Authored-By: Patrick Linnane <patrick@linnane.io> Co-Authored-By: Michael Cho <michael@michaelcho.dev>
c395857
to
0f40846
Compare
Tried some things out but still failing in CI. In local Linux container, adjusting match seemed to help as arrow symbol was rendering differently. Also, when manually running with Remaining things would be CI specific settings (perhaps |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
@zthxxx Sounds like it must be. Maybe you want to look into getting it working with |
@danielbayley I'm really sorry about this. A few months ago, I have tried to solve testing on this, but I failed due to I'm not familiar with Ruby or how Homebrew tests running. 😢 Sorry for the late reply again. |
I have added unit-test for zsh plugin using expect in zthxxx/zsh-history-enquirer@00c7dfe#diff-0004d5adc0e5e69fd91c2d058cd8151332729eb9a6aefb97aff9fb2f72e1f4b1 |
@zthxxx Nice, so I have tried to make use of this new unit test instead… cc: @cho-m @chenrui333 @p-linnane |
0cb234f
to
9787c06
Compare
9787c06
to
1d18813
Compare
depends_on "zsh" | ||
end | ||
|
||
resource "zsh-widget.test" do |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It also require of files in ./tests/testing-home/*
for mock zsh testing environment, but not the single file 😢
|
||
match = "ech" | ||
io = IO.popen(widget, "r") | ||
stdout = io.expect(match, 30) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems we can't access the tty
in the CI pipeline (it's not an interactive tty and throws an error from the stty
command).
Should we try a different testing approach? Maybe we could simply check if the zsh-history-enquirer.plugin.zsh
file exists after installation,
or verify that the plugin function is loaded by .zshrc
without actually executing it. For example, we could run zsh -il -c 'where history_enquire'
and look for an exit code of 0.
HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>
, where<formula>
is the name of the formula you're submitting?brew test <formula>
, where<formula>
is the name of the formula you're submitting?brew audit --strict <formula>
(after doingHOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>
)? If this is a new formula, does it passbrew audit --new <formula>
?Reattempting #122728.