Trending repository
-
Updated
Apr 27, 2022 - Python
Enter your username and annotate some of the “towers” to share your GitHub story in 3D, VR, and IRL.
October 30, 2022 - November 02, 2022 • Raleigh, NC
Google Cloud Build lets you create fast, consistent, reliable builds across all languages. Automatically build containers or non-container artifacts on commits to your GitHub repository. Get complete control over defining custom workflows for building, testing, and deploying across multiple environments such as VMs, serverless, Kubernetes, or Firebase.
We support two flows when registering:
Upfront (arguments):
atuin register -u "..." -e "..." -p "..."Partial (prompt):
atuin register -u "..." -e "..."
Please enter password: ...I think we should probably suggest the latter (it's uncommon to paste passwords into the command itself)
There's also the issue that the password prompt does not enable any proper p
Another simple task for ya. We have this function called setProxyTarget:
It's only used in the contract tests. However, it's not necessary and we can remove it. Goal of this issue is to first remove the function, and then replace all
as title
I'm in the process of converting our WCF security model over to CoreWCF and have hit a wall because CustomUserNameSecurityTokenAuthenticator has been marked as internal.
I'm unable to work around it by inheriting from a class further up the chain because the UserNameSecurityToken is also marked as internal, and that is the token type which will get created.
Is there a reason why these ar
As disscuseed on kedacore/keda#2765 (comment), we should unify the functions for Status & Conditions handling. Referencing controller related stuff here is suboptimal.
There are two locations with similar functions:
https://github.com/kedacore/keda/blob/9f0ee58fc6839d74636e1ec6883fe21d82617ea3/controllers/keda/util/status.go#L30-L63
https://g
Gitpod is an open-source developer platform automating the provisioning of ready-to-code developer environments..
With Gitpod your team can instantly start coding with fresh, ephemeral and fully-compiled dev environments for each new task - no matter if you are building a new feature, want to fix a bug or do a code review.
Sounds like GitHub Codespaces? https://www.gitpod.io/gitpod-vs-codespaces/
So that we don't need to cast every time in the program.