profile
viewpoint
Stephan Renatus srenatus Chef Software Inc. Berlin, Europe

dexidp/dex 4978

OpenID Connect Identity (OIDC) and OAuth 2.0 Provider with Pluggable Connectors

fugue/fregot 134

Fugue Rego Toolkit

chef-cookbooks/audit 56

Audit Cookbook for Chef Compliance

chef-boneyard/delivery-cluster 20

DEPRECATED: Deployment cookbook for standing up Delivery clusters using chef-provisioning.

chef/kitchen-zone 0

Test Kitchen Driver for Solaris Zones

srenatus/aeson 0

A fast Haskell JSON library

srenatus/angular-oauth2-oidc 0

Support for OAuth 2 and OpenId Connect (OIDC) in Angular.

srenatus/apache2 0

Development repository for the apache2 cookbook

srenatus/aptly 0

Installs and Configured aptly (aptly.info)

PullRequestReviewEvent

push eventsrenatus/auth0

Stephan Renatus

commit sha ebf3ba84d2567b8dc377768f3eca429f96672a01

internal/client: simplify funs passed to rehttp.NewTransport I believe them to be equivalent... :) Signed-off-by: Stephan Renatus <srenatus@chef.io>

view details

push time in 14 hours

PR opened go-auth0/auth0

internal/client: simplify funs passed to rehttp.NewTransport

I believe them to be equivalent... :)

+3 -8

0 comment

1 changed file

pr created time in 15 hours

create barnchsrenatus/auth0

branch : sr/nitpick-rehttp-setup

created branch time in 15 hours

PullRequestReviewEvent
CommitCommentEvent
CommitCommentEvent

pull request commentgo-auth0/auth0

management: add WithContext method

Heya. I've been having limited access to a keyboard yesterday, so I'd like to describe my use case some more now:

Imagine there's some HTTP handler code, "LIST auth thingies", and that code ends up calling mgmt.Client.List(), where mgmt is an instance of management.Management shared among the different handlers. When the requesting party goes away, I'd like the list request to be cancelled. I can imagine some ways of making this happen:

  1. Instantiate a separate instance of management.Management in every handler, use management.New(..., management.WithContext(ctx)).
  2. Share the instance, use mgmt.WithContext(ctx).Client.List().
  3. Alter every method, allowing us to do mgmt.Client.List(ctx)

(1.) comes with the disadvantage that ever call to New() ends up retrieving a new access token using the client creds flow, work that wouldn't be necessary. I'd think that (3.) is the cleanest way to do it, but also the most effort. So, (2.) seems like a decent compromise. What do you think?

(There's more alternatives, to explore, I suppose. If New() would take in a token source, we would perhaps be able to avoid the token business, and still have an instance per handler invocation.... 🤔)

srenatus

comment created time in 18 hours

Pull request review commentopen-policy-agent/opa

Treat built-in function errors as false/undefined instead of halting evaluation

 var builtin = [...]commandDesc{ 	{"profile", []string{}, "toggle profiler and turns off trace"}, 	{"types", []string{}, "toggle type information"}, 	{"unknown", []string{"[ref-1 [ref-2 [...]]]"}, "toggle partial evaluation mode"},+	{"strict-builtin-errors", []string{}, "treat built-in function errors as fatal"},

[nit] Shouldn't this say "toggle", too?

Also, is there a way to retrieve the current setting? (Might not be needed if we don't have that on any of the other toggling commands...)

tsandall

comment created time in 19 hours

Pull request review commentopen-policy-agent/opa

Treat built-in function errors as false/undefined instead of halting evaluation

 func TestEvalWithBundleDuplicateFileNames(t *testing.T) { 	}) } +func TestEvalWithStrictBuiltinErrors(t *testing.T) {+	params := newEvalCommandParams()+	params.strictBuiltinErrors = true++	var buf bytes.Buffer+	_, err := eval([]string{"1/0"}, params, &buf)+	if err == nil {+		t.Fatal("expected error")+	}++	params.strictBuiltinErrors = false+	buf.Reset()++	_, err = eval([]string{"1/0"}, params, &buf)+	if err != nil {+		t.Fatal("unexpected error:", err)+	}

Could we add what it actually returns with params.strictBuiltinErrors set to false? (Can we assert "undefined" here?)

tsandall

comment created time in 19 hours

Pull request review commentopen-policy-agent/opa

Treat built-in function errors as false/undefined instead of halting evaluation

 func TestEvalWithInterQueryCache(t *testing.T) { 	} } +func TestStrictBuiltinErrors(t *testing.T) {+	_, err := New(Query("1/0"), StrictBuiltinErrors(true)).Eval(context.Background())+	if err == nil || err.Error() != "1/0: eval_builtin_error: div: divide by zero" {

Unrelated: an error refactoring could be useful -- allowing the caller to differentiate stuff like this based on types, not strings.

tsandall

comment created time in 19 hours

Pull request review commentopen-policy-agent/opa

Treat built-in function errors as false/undefined instead of halting evaluation

 project adheres to [Semantic Versioning](http://semver.org/).  ### Backwards Compatibility -* Renamed `timer_rego_builtin_http.send_ns` to `timer_rego_builtin_http_send_ns` to avoid issues with periods in metric keys.+* The `timer_rego_builtin_http.send_ns` metric has been renamed to `timer_rego_builtin_http_send_ns` to avoid issues with periods in metric keys.+* Built-in function error handling has been changed to treat errors as false/undefined. See the note below.++### Built-in Function Error Handling++Previously, built-in function errors would cause policy evaluation to halt immediately. Going forward, by default, built-in function errors no longer halt evaluation. Instead, expressions are treated as false/undefined if any of the invoked built-in functions return errors.++This change resolves a common issue people face when passing unsanitized input values to built-in functions. For example, prior to this change the expression `io.jwt.decode("GARBAGE")` would halt evaluation of the entire policy because the string is not a valid encoding of a JSON Web Token (JWT). If the expression was `io.jwt.decode(input.token)` and the user passed an invalid string value for `input.token` the same error would occur. With this change, the same expression is simply undefined, i.e., there is no result. This means policies can use negation to test for invalid values:++```rego+error["invalid JWT supplied as input"] {+  not io.jwt.decode(input.token)+}+```++If you require the old behaviour, enable "strict" built-in errors on the query:++| Caller | Example |+| --- | --- |+| HTTP | `POST /v1/data/example/allow?strict-builtin-errors` |+| Go (Library) | `rego.New(rego.Query("data.example.allow"), rego.StrictBuiltinErrors(true))` |+| CLI | `opa eval --strict-builtin-errors 'data.example.allow'` |+

❓ Anything to say about WASM here? Perhaps not because there, the builtin situation is different...?

tsandall

comment created time in 19 hours

PullRequestReviewEvent
PullRequestReviewEvent

pull request commentgo-auth0/auth0

management: add WithContext method

I'd like to pass a different context in for each request. The existing means would have me call new for every call, wouldn't they?

On Wed, 23 Sep 2020, 09:56 Alex Kalyvitis, notifications@github.com wrote:

Hi! I may be mistaken, but wouldn't that acquire a new token for every call to new? I think I'd rather avoid that...

Why would you need to make multiple calls to New?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/go-auth0/auth0/pull/142#issuecomment-697199494, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGUR3VIJGIRVEF2IL5444LSHGSZBANCNFSM4RVQDIIQ .

srenatus

comment created time in 2 days

pull request commentgo-auth0/auth0

management: add WithContext method

Hi!

I may be mistaken, but wouldn't that acquire a new token for every call to new? I think I'd rather avoid that...

On Wed, 23 Sep 2020, 09:44 Alex Kalyvitis, notifications@github.com wrote:

Hi @srenatus https://github.com/srenatus, isn't management.WithContext() https://github.com/go-auth0/auth0/blob/master/management/management.go#L278-L284 sufficient for your use case? You can use it as an argument to management.New(...).

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/go-auth0/auth0/pull/142#issuecomment-697194104, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGUR3TTKYB4ZOZ5BO7MUB3SHGROHANCNFSM4RVQDIIQ .

srenatus

comment created time in 2 days

issue commentchef/automate

hide sign in as local user button

This line decides if dex "knows" local users or not: https://github.com/chef/automate/blob/afbd5604c7d5966b24e0676f3df6e55c11c232f0/components/automate-dex/habitat/templates/config.yml#L6

susanev

comment created time in 2 days

issue commentchef/automate

hide sign in as local user button

well it would be gone. there's dragons here, but you could still change the config to re-enable local users.

susanev

comment created time in 2 days

issue commentchef/automate

hide sign in as local user button

I believe we could disable local users in dex completely. That would make the button disappear, too.

susanev

comment created time in 2 days

PullRequestReviewEvent

pull request commentgo-auth0/auth0

Add an option to use custom base http.Client.

🤔 This is a good improvement, it's a shame to let it go to waste. Anyone listening? Anything I can do to help with this?

rene00

comment created time in 3 days

CommitCommentEvent
CommitCommentEvent
CommitCommentEvent
CommitCommentEvent
CommitCommentEvent
CommitCommentEvent
CommitCommentEvent
CommitCommentEvent

push eventsrenatus/auth0

Stephan Renatus

commit sha 1c6e0c314c261afae030c03c1feee82886c54f84

management: add WithContext method This tries to introduce the ability to provide a context, while keeping the API surface intact, and not changing every single method signature. It is modelled slightly after how gorp had done the same thing three years ago: https://github.com/go-gorp/gorp/pull/352 Signed-off-by: Stephan Renatus <srenatus@chef.io>

view details

push time in 3 days

PR opened go-auth0/auth0

management: add WithContext method

This tries to introduce the ability to provide a context, while keeping the API surface intact, and not changing every single method signature.

It is modelled slightly after how gorp had done the same thing three years ago: https://github.com/go-gorp/gorp/pull/352

+53 -2

0 comment

2 changed files

pr created time in 3 days

push eventsrenatus/auth0

Stephan Renatus

commit sha 23790916a85d7a72f87b39e9d715bf6924218aeb

management: add WithContext method This tries to introduce the ability to provide a context, while keeping the API surface intact, and not changing every single method signature. It is modelled slightly after how gorp had done the same thing three years ago: https://github.com/go-gorp/gorp/pull/352 Signed-off-by: Stephan Renatus <srenatus@chef.io>

view details

push time in 3 days

PullRequestReviewEvent

create barnchsrenatus/auth0

branch : sr/rough-in-a-context-argument

created branch time in 3 days

fork srenatus/auth0

Go SDK for the Auth0 platform

fork in 3 days

startedlehins/massiv

started time in 3 days

issue commentopen-policy-agent/opa

Support gRPC body in OPA Istio plugin

If it's possible to implement inside of server handler as opposed to a built-in function, I think that would be preferable since that way the policy would not be tightly coupled to the wire format [...]

Yup, that's a good point.

I have wondered in the past whether we could make this work in OPA itself. For example, if bundles could be extended to include the descriptors then in theory it could unmarshal protobuf messages before running eval. This would require some upfront design work.

Would you imagine this like providing support for another content-type (like application/protobuf), where the provided set of descriptors would allow the handler to translate the input before passing it on into eval? We'd need some way to convey the message type then... 🤔 (In gRPC, that's done via a header, see PROTOCOL-HTTP2.md)

ledor473

comment created time in 4 days

PullRequestReviewEvent
PullRequestReviewEvent

PR opened returntocorp/semgrep

docs/pattern-features.md: fix golang snippet

I'm not 100% certain that this was the original intention behind the code snippet, but it seems probable to me. The code that was there previously wasn't valid.

+1 -1

0 comment

1 changed file

pr created time in 4 days

create barnchsrenatus/semgrep

branch : sr/docs/pattern-features/go-var-example

created branch time in 4 days

fork srenatus/semgrep

Lightweight static analysis for many languages. Find bug variants with patterns that look like source code.

https://semgrep.dev

fork in 4 days

create barnchsrenatus/oso

branch : sr/python-test

created branch time in 4 days

fork srenatus/oso

oso is an open source policy engine for authorization that’s embedded in your application

https://docs.osohq.com

fork in 4 days

starteddgryski/semgrep-go

started time in 5 days

issue commentopen-policy-agent/opa

Upgrade gorilla/mux to at least 1.7.4

updating the http router, gorilla/mux, to at least v1.7.4 as they describe some performance improvements we think might help.

I'm curious about these. 😃 Looking at the release notes, they've improved the performance of the code path for parsing url query parameters (https://github.com/gorilla/mux/pull/544). (💭Do you use these a lot in your setup?) The other perf improvement seems to be https://github.com/gorilla/mux/pull/516... no idea if that could be really impactful. But of course, ho harm in updating.

loudmouth

comment created time in 5 days

push eventsrenatus/pbcat

Stephan Renatus

commit sha feed84bf4d0d74915037ad41d1fd10c5a9479b39

example: initial commit Signed-off-by: Stephan Renatus <srenatus@chef.io>

view details

push time in 5 days

create barnchsrenatus/pbcat

branch : master

created branch time in 5 days

created repositorysrenatus/pbcat

created time in 5 days

startedpnnferreira/grpcopa

started time in 5 days

issue commentopen-policy-agent/opa

Support gRPC body in OPA Istio plugin

I could imagine two ways for proceeding here, extending the envoy plugin with some specific functionality, or creating a pb.unmarshal builtin via a plugin. The latter would be generic, and could be used from the envoy plugin, too. I believe it's necessary to make it a plugin, as it'll bring a few dependencies, and requires its own configuration for passing in a proto_descriptor_bin or proto_descriptor_file in the same way the envoy grpc-json transcoder does it. The unmarshal method would take in an object that contains the binary message payload to unmarshal, and either the message type, or the service method the message was provided as an argument to.

The envoy plugin, when using that new builtin, could either call it when trying to provide the parsed body, or leave it to the author of the policy to make use of that builtin, by providing the raw request payload, suitably encoded.

Just thinking aloud here for purpose of discussion, while I'd like to see this resolved, it'll be weeks before I'd get to pick it up. WDYT?

ledor473

comment created time in 12 days

startedphantomics/april

started time in 13 days

issue commentopen-policy-agent/opa

Support gRPC body in OPA Istio plugin

I'm afraid the grpc json transcoder works the other way: incoming json requests are turned into grpc calls.

Envoy also has a http1.1-grpc bridge, but that one translates incoming grpc calls into http2 calls with protobuf payloads.

So, I don't think there's anything close at hand to solve this. However, we could perhaps have a plugin for OPA that allows you to configure the relevant protosets, and that could be used to make the payloads available in the right place.

On Wed, 9 Sep 2020, 18:09 PF2000, notifications@github.com wrote:

Hi, Is there any way to use the transcoder https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/grpc_json_transcoder_filter to parse the body to JSON and forward it to OPA as "application/json" ?

The structure would be something like this:

(...) - filters: - name: envoy.http_connection_manager (...) http_filters: - name: envoy.grpc_json_transcoder (...) - name: envoy.ext_authz (...)

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/open-policy-agent/opa/issues/1931#issuecomment-689663595, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGUR3ROJVWUE7N3MZECOYTSE6SEPANCNFSM4JSY77SA .

ledor473

comment created time in 15 days

PullRequestReviewEvent

Pull request review commentchef/chef-server

Upgrade to OTP 22

 fields_for_insert(#oc_chef_cookbook_artifact{}) ->     erlang:error(not_supported).  %% @doc Checks if a cookbook artifact with the given `AuthzId' exists--spec exists_by_authz_id(AuthzId :: object_id()) -> boolean | {error, _Why}.+-spec exists_by_authz_id(AuthzId :: object_id()) -> boolean() | {error, _Why}.

heh

stevendanna

comment created time in 21 days

Pull request review commentchef/chef-server

Upgrade to OTP 22

 acl_checks() ->     fun check_admins_group_removal_from_grant_ace/5   ]. --spec check_admins_group_removal_from_grant_ace(binary(),binary(), atom(),binary(),tuple())-      -> false | {true, attempted_admin_group_removal_grant_ace}.++-spec check_admins_group_removal_from_grant_ace(binary(), binary(), atom(), binary(), tuple())+      -> error | false | {true, attempted_admin_group_removal_grant_ace}.

Hmm it's been a while, so I don't see where the error comes from? Is that a default if it's no_match or something...?

stevendanna

comment created time in 21 days

Pull request review commentchef/chef-server

Upgrade to OTP 22

 fetch_cookbook_id(DbContext, Name, OrgId) ->             AuthzId     end. --spec fetch(chef_type(), binary(), id()) -> list() | {error, term()}.+-spec fetch(chef_type(), binary(), id()) -> ejson_term() | {error, term()} | forbidden. fetch(Type, OrgId, AuthzId) ->     fetch(Type, OrgId, AuthzId, undefined). 

👇 Should fetch/4 have a spec, too? (It's exported)

stevendanna

comment created time in 21 days

Pull request review commentchef/chef-server

Upgrade to OTP 22

 check_file(OrgId, AwsConfig, Bucket, Checksum) ->                      error_logger:error_msg("Checking presence of file (checksum: ~p) for org ~p from bucket ~p (key: ~p) failed because the file was not found~n",                                             [Checksum, OrgId, Bucket, Key]),                      {missing, Checksum};+                 %% TODO(ssd) 2020-09-03: should likely remove this case when we move to erlcloud+                 error:{aws_error, {socket_error,retry_later}} ->+                     error_logger:error_msg("Checking presence of file (checksum: ~p) for org ~p from bucket ~p (key: ~p) returned retry_later (retries left: ~p)~n",+                                            [Checksum, OrgId, Bucket, Key, AttemptsLeft - 1]),+                     check_file(OrgId, AwsConfig, Bucket, Checksum, AttemptsLeft -1);

[nit] This is a tiny nit, but AttemptsLeft - 1 reads better than AttemptsLeft -1, doesn't it? 🤔

stevendanna

comment created time in 21 days

PullRequestReviewEvent
PullRequestReviewEvent

issue commentenvoyproxy/envoy

Support 404 NotFound with gRPC-JSON transcoder when an unknown url comes in

I've been looking into ways to allow changing the behaviour here. @lych77's approach seems like a good one.

To make this more explicit, what do you think about the grpc_json transcoder setting some dynamic metadata key based on whether it has or has not matched? The configuration could then have a local reply if they key isn't present (or has the wrong value) as desired.

Alternatively, we could have a configurable in transcoder.proto to allow stating the desired local reply if the gRPC method lookup fails. (I think the other approach is more lightweight, but I've not verified if dynamic metadata and local replies can be used like that, beside reading the docs.)

longkai

comment created time in 21 days

Pull request review commentchef/automate

[Auth-4301] Add permission check for CreateRule

 const ( )  func (p *pg) CreateRule(ctx context.Context, rule *storage.Rule) (*storage.Rule, error) {++	projectsFilter, err := projectsListFromContext(ctx)+	if err != nil {+		return nil, err+	}+	found := len(projectsFilter) == 0 // empty means all projects allowed+	if !found {+		for _, proj := range projectsFilter {+			if proj == rule.ProjectID {+				found = true+			}+		}

[nit] This could use stringutils. SliceContains:

		found = stringutils.SliceContains(projectsFilter, rule.ProjectID)
msorens

comment created time in 21 days

Pull request review commentchef/automate

[Auth-4301] Add permission check for CreateRule

 const ( )  func (p *pg) CreateRule(ctx context.Context, rule *storage.Rule) (*storage.Rule, error) {++	projectsFilter, err := projectsListFromContext(ctx)+	if err != nil {+		return nil, err+	}+	found := len(projectsFilter) == 0 // empty means all projects allowed+	if !found {+		for _, proj := range projectsFilter {+			if proj == rule.ProjectID {+				found = true+			}+		}+	}+	if !found {+		return nil, fmt.Errorf("project with ID %q not found", rule.ProjectID)+	}

Re: previous nit, instead of overwriting found, I'd suggest

	if !found && !stringutils.SliceContains(projectsFilter, rule.ProjectID) {
		return nil, fmt.Errorf("project with ID %q not found", rule.ProjectID)
	}
msorens

comment created time in 21 days

Pull request review commentchef/automate

[Auth-4301] Add permission check for CreateRule

 const ( )  func (p *pg) CreateRule(ctx context.Context, rule *storage.Rule) (*storage.Rule, error) {++	projectsFilter, err := projectsListFromContext(ctx)+	if err != nil {+		return nil, err+	}+	found := len(projectsFilter) == 0 // empty means all projects allowed+	if !found {+		for _, proj := range projectsFilter {+			if proj == rule.ProjectID {+				found = true+			}+		}+	}+	if !found {+		return nil, fmt.Errorf("project with ID %q not found", rule.ProjectID)+	}

🤔 maybe there's a better name than found, here, too? allProjectsAllowed := len(...) == 0 maybe?

msorens

comment created time in 21 days

Pull request review commentchef/automate

[Auth-4301] Add permission check for CreateRule

 const ( )  func (p *pg) CreateRule(ctx context.Context, rule *storage.Rule) (*storage.Rule, error) {++	projectsFilter, err := projectsListFromContext(ctx)+	if err != nil {+		return nil, err+	}+	found := len(projectsFilter) == 0 // empty means all projects allowed+	if !found {+		for _, proj := range projectsFilter {+			if proj == rule.ProjectID {+				found = true+			}+		}+	}+	if !found {+		return nil, fmt.Errorf("project with ID %q not found", rule.ProjectID)+	}+ 	ctx, cancel := context.WithCancel(ctx) 	defer cancel()

[nit] This block should be the first thing happening in this function, I think.

msorens

comment created time in 21 days

PullRequestReviewEvent
PullRequestReviewEvent

startedenvoyproxy/xds-relay

started time in 21 days

pull request commentchef/automate

Make external API a separate module

Updating dependencies no longer provides an easy way to review what is changing in those dependencies.

Yeah, it's still in the go.{sum,mod} files, but you won't see the code right away.

I agree with your pros and cons there, thanks for summing this up. :)

danielsdeleo

comment created time in 22 days

Pull request review commentchef/automate

Make external API a separate module

 paths = [   "vendor/github.com/grpc-ecosystem/grpc-gateway/*",   "vendor/github.com/grpc-ecosystem/grpc-opentracing/*",   "vendor/github.com/hashicorp/hcl/*",+  "vendor/github.com/josharian/intern/*",

🤔 I wonder how this got dragged in

danielsdeleo

comment created time in 22 days

PullRequestReviewEvent

pull request commentchef/automate

Make external API a separate module

@stevendanna you're suggesting that we stop vendoring, and rely completely on go modules instead? It has worked fine for the other project, I'd say. 👍

danielsdeleo

comment created time in 22 days

PullRequestReviewEvent

startedekzhang/crepe

started time in 22 days

PullRequestReviewEvent

delete branch srenatus/envoy

delete branch : sr/bazelisk-from-homebrew-core

delete time in 24 days

pull request commentenvoyproxy/envoy

macos/homebrew: bazelisk is in homebrew-core now

I can't see a change from my second commit... I'm unsure if the CI run has happened a second time... there shouldn't be no output at all from bazel version. 😕

srenatus

comment created time in 24 days

push eventsrenatus/envoy

Stephan Renatus

commit sha 44e3a901162ac02884c48560f46f605bcafa7de1

squash me: add `bazel version` Signed-off-by: Stephan Renatus <srenatus@chef.io>

view details

push time in 24 days

pull request commentenvoyproxy/envoy

macos/homebrew: bazelisk is in homebrew-core now

Running the call locally for comparison, I get this:

$ brew link --overwrite bazelisk
Warning: Already linked: /usr/local/Cellar/bazelisk/1.6.1
To relink:
  brew unlink bazelisk && brew link bazelisk

So, the link has succeeded, I suppose; since it was already the case. I've pushed a commit including bazel version. ⏳

srenatus

comment created time in 24 days

pull request commentenvoyproxy/envoy

macos/homebrew: bazelisk is in homebrew-core now

@lizan thanks for reviewing this! I'll add a line, and look into fixing the warning... 😃

srenatus

comment created time in 24 days

pull request commentenvoyproxy/envoy

macos/homebrew: bazelisk is in homebrew-core now

https://dev.azure.com/cncf/envoy/_build/results?buildId=50072&view=logs&j=a5e52b91-c83f-5429-4a68-c246fc63a4f7&t=7d499b5d-1d92-5096-7919-3c7f8065da78 looks like osx is happy

srenatus

comment created time in 24 days

PR opened envoyproxy/envoy

macos/homebrew: bazelisk is in homebrew-core now

See https://formulae.brew.sh/formula/bazelisk and https://github.com/bazelbuild/homebrew-tap/pull/98


This should have been a trivial README change. I've also changed the other occurance of bazelbuild/tap/bazelisk, so let's see what CI thinks about that.

+5 -6

0 comment

2 changed files

pr created time in 24 days

create barnchsrenatus/envoy

branch : sr/bazelisk-from-homebrew-core

created branch time in 24 days

fork srenatus/envoy

Cloud-native high-performance edge/middle/service proxy

https://www.envoyproxy.io

fork in 24 days

PullRequestReviewEvent

issue commentsolo-io/gloo

Redirect to a different page when OPA reject a call

https://github.com/solo-io/gloo/issues/3201 would allow something like this, I think.

djannot

comment created time in 25 days

PullRequestReviewEvent

startedenvoyproxy/go-control-plane

started time in a month

PullRequestReviewEvent
PullRequestReviewEvent

pull request commentchef/automate

Remove proto dep external->interservice

Was that not resolved with https://github.com/dexidp/dex/pull/1750? I haven't kept close track, but I thought so... 🤔

danielsdeleo

comment created time in a month

PullRequestReviewEvent
PullRequestReviewEvent

pull request commentPlasmaLang/plasma

src/pz.link.m: fix typo "too modules" -> "two ..." (also in tests)

#288 looks alright to me and I agree with it for this small change. Thanks for clarifying!

srenatus

comment created time in a month

PR opened PlasmaLang/plasma

src/pz.link.m: fix typo "too modules" -> "two ..." (also in tests)

Trivial fix, doesn't warrant adding a line added to AUTHORS, I'd think. What do you think?

+2 -2

0 comment

2 changed files

pr created time in a month

create barnchsrenatus/plasma

branch : sr/typo/two-modules

created branch time in a month

fork srenatus/plasma

Plasma Programming Language

fork in a month

startedPlasmaLang/plasma

started time in a month

startedPaulBone/protobuf-mercury

started time in a month

startedMercury-Language/mercury

started time in a month

more