Skip to content
This repository has been archived by the owner on Apr 24, 2020. It is now read-only.

Fix of k8s shorter segment #693

Merged
merged 1 commit into from
Dec 14, 2017
Merged

Fix of k8s shorter segment #693

merged 1 commit into from
Dec 14, 2017

Conversation

djetelina
Copy link
Contributor

My latest PR #676 seemed to have been incompatible with #661 - I did my PR on top of master instead of next. This one is done on top of next and should fix the current not so great state of next (prints nothing). Sorry!

My latest PR #676 seemed to have been incompatible with #661 - I did my PR on top of master instead of next. This one is done on top of next and should fix the current not so great state of next (prints nothing). Sorry!
@bhilburn
Copy link
Member

Thanks for the fix, @iScrE4m! I'm actually surprised that #676 passed unit testing with that breakage. We clearly have a gap in test coverage that we need to fix.

Thanks again for the PRs, and for fixing this issue! Much appreciated =)

@bhilburn bhilburn merged commit 40b500c into Powerlevel9k:next Dec 14, 2017
@bhilburn
Copy link
Member

Oh, wait, I understand what happened. The tests were fine on master, but when I re-targeted your branch target it didn't re-build against next, so I never saw the failure.

Good lesson learned, there.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants