Skip to content

Here's what's popular on GitHub today...

The Julia Language logo

Popular topic

Julia is a high-level, high-performance dynamic programming language for numerical computing.
{Future} Stack 2022

Upcoming event recommended by GitHub

Jun
1

{Future} Stack 2022

June 01, 2022 - June 04, 2022 • Las Vegas, NV

It’s the ultimate software engineering conference.Get deep into what your peers are doing.

App recommended by GitHub

Stale

Automatically close stale Issues and Pull Requests that tend to accumulate during a project.

How it works

After a period of inactivity, a label will be applied to mark an issue as stale, and optionally post a comment to notify contributors that the Issue or Pull Request will be closed.

If the Issue or Pull Request is updated, or anyone comments, then the stale label is removed.

If no more activity occurs, the Issue or Pull Request will be automatically closed with an optional comment.

Trending repository

conradludgate
conradludgate commented Apr 26, 2022

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

good first issue

Trending repository

smartcontracts
smartcontracts commented Apr 29, 2022

Another simple task for ya. We have this function called setProxyTarget:

https://github.com/ethereum-optimism/optimism/blob/8ac47db2f7397ff545a674d20281a13dfba90d86/packages/contracts/test/helpers/resolver/address-manager.ts#L6-L17

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

C-maintenance good first issue M-contracts

Trending repository

marlon-tucker
marlon-tucker commented Mar 16, 2022

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

good first issue Triaged
keda

Trending repository

zroubalik
zroubalik commented Apr 13, 2022

Proposal

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

help wanted good first issue feature-request