perhaps not without write access on the associated repo. I see a restart job button in the top-right there ^
I don't have that button. :(
clicking the buttons then heh
might could see if travis has any concept of retry attempts?
Maybe, but I think retires only make sense in part of the pre-job setup steps (i.e. Vault download, pip installs). Manual retries are probably fine for right now.
@llamasoft: Also, since you're here now :), I'm thinking it might be easiest to go ahead and cut a new release version before merging hvac/hvac#533 and do that over the next day or two
#533 has the potential to disrupt folks' usages in potentially unexpected way, so it may make sense to cut a patch release with your recent additions (along with some of the other low-impact PRs from the community) and then do a minor version bump for #533 to help indicate the chance we're introducing breaking changes
also, as a metapoint, I've been incredibly pleased to see you tackle some long lingering issues with aplomb and if you have in interest in helping maintain this module let me know! i.e., if you're interested in having write access and helping review other folks' PRs, etc.
Alright! “conference heck” is now over… im back! went to 5 conferences in 2 months and a few other travels in between. feels like ive been gone for a while!
my god @llamasoft you have been crushing it lol thanks for the contributions and thoughtful explanations