profile
viewpoint

adriancole/airline 2

Java annotation-based framework for parsing Git like command line structures

adriancole/armeria 1

Asynchronous RPC/REST library built on top of Java 8, Netty, HTTP/2, Thrift and gRPC

adriancole/clj-zipkin 1

Adds zipkin tracing instrumentation for Clojure applications

adriancole/- 0

Because I can

adriancole/adaptive-alerting 0

Anomaly detection for streaming time series, featuring automated model selection.

adriancole/adriancole.github.com 0

test repo for github pages

adriancole/arquillian-container-undertow 0

Arquillian Deployable Container for Undertow

created repositoryJakeWharton/dockerfile-shebang

Treat your Dockerfiles as self-contained, editable scripts

created time in 4 hours

push eventsmoketurner/dropwizard-zipkin

Justin Plock

commit sha 6b34d65e7ad148d9b8dccc7e026f9f7d163832bb

[maven-release-plugin] prepare for next development iteration

view details

push time in 7 hours

created tagsmoketurner/dropwizard-zipkin

tagv2.0.16-1

Dropwizard Zipkin Bundle

created time in 7 hours

push eventsmoketurner/dropwizard-zipkin

Justin Plock

commit sha 2570e8444cf2ab72c6bf49cd4448955e7d67ff57

[maven-release-plugin] prepare release v2.0.16-1

view details

push time in 7 hours

push eventsmoketurner/dropwizard-zipkin

Justin Plock

commit sha f97a0f80cb0f2022f66b689ab741c5988d904a07

Formatting updates

view details

push time in 7 hours

push eventsmoketurner/dropwizard-zipkin

Justin Plock

commit sha d88fe3160d7c6f45374344f676bd73e41593b620

Update to Dropwizard 2.0.16

view details

push time in 7 hours

issue openedhypertrace/hypertrace

Fix ENV variable issue for snyk on forked branch PR by non-member

Use Case

When PR is raised from forked branch by non-member circleci couldn't find ENV variables and throws error like below. Screenshot 2020-11-30 at 8 53 43 PM

According to Aaron, The repo has to be set up to pass secrets to forked PRs, but there are security implications to that so we deferred it.

Proposal

This a big think when it comes to contribution from non-members and we should address it asap. I found a FAQ around this in circleci support which are as below:

  • https://support.circleci.com/hc/en-us/articles/360008097173-Why-aren-t-pull-requests-triggering-jobs-on-my-organization-

we will need to investigate more and explore options if circleci is not able to this.

created time in 10 hours

issue openedhypertrace/hypertrace

Optimise release process and versioning for helm charts

<!-- Welcome to the Hypertrace repo!

  • Please be respectful and considerate of others when commenting on issues.
  • Please search for existing issues in order to make sure we don't have duplicate bugs/feature requests.
  • If you have a question please ask it on our Slack chat https://join.slack.com/t/hypertrace/shared_invite/zt-hgjlblic-Tq2_N4sHJj4RMqx5nirS9w instead of creating an issue.
  • Please provide as much information as possible so we all understand the issue. -->

Use Case

  • As a part of bigger initiative of having proper semantic versioning based releases on manual release, we need to have internal versions for helm charts on each merge similar to 1.0.0-main.10bd522c which will help us trigger helm CD on each merge.
  • This will help in testing intermediate releases.

Proposal

We can explore something like this: https://insights.project-a.com/using-github-actions-to-deploy-to-kubernetes-122c653c0b09 to cut releases and CD based on github action.

created time in 11 hours

delete branch hypertrace/hypertrace-ingester

delete branch : fix_snyk

delete time in 11 hours

delete branch hypertrace/hypertrace-ingester

delete branch : update-one-by-one

delete time in 11 hours

delete branch hypertrace/hypertrace-ingester

delete branch : merge

delete time in 11 hours

delete branch hypertrace/hypertrace-ingester

delete branch : update-submodules-adds-logging-config

delete time in 11 hours

delete branch hypertrace/hypertrace-ingester

delete branch : init-commit

delete time in 11 hours

delete branch hypertrace/hypertrace-ingester

delete branch : unit-test

delete time in 11 hours

PR closed hypertrace/hypertrace-ingester

Reviewers
chore: add a unit test for conditional and string equals projections

Tests specifically for returning "null" string.

+77 -3

4 comments

2 changed files

tim-mwangi

pr closed time in 11 hours

pull request commenthypertrace/hypertrace-ingester

chore: add a unit test for conditional and string equals projections

@aaron-steinfeld is this still necessary?

I don't think so - I added general tests for the null case in both the attribute and ingester relevant areas.

Ok. Will close it out.

tim-mwangi

comment created time in 11 hours

pull request commenthypertrace/hypertrace-ingester

chore: add a unit test for conditional and string equals projections

@aaron-steinfeld is this still necessary?

I don't think so - I added general tests for the null case in both the attribute and ingester relevant areas.

tim-mwangi

comment created time in 11 hours

pull request commenthypertrace/hypertrace-ingester

chore: add a unit test for conditional and string equals projections

@aaron-steinfeld is this still necessary?

tim-mwangi

comment created time in 11 hours

push eventhypertrace/hypertrace-ingester

Rishabh

commit sha 53d1520246da3d138b1d9cd8db3a09e0da448f7c

Add otel constants for container & k8s (#78) * Add otel constants for container & k8s

view details

push time in 11 hours

delete branch hypertrace/hypertrace-ingester

delete branch : add-resource-constants

delete time in 11 hours

delete branch talsma-ict/context-propagation

delete branch : dependabot/maven/io.dropwizard.metrics-metrics-core-4.1.16

delete time in 12 hours

push eventtalsma-ict/context-propagation

dependabot-preview[bot]

commit sha 47f8089810d519b1a0b944555a9637c64b421e8b

Bump metrics-core from 4.1.15 to 4.1.16 (#195) Bumps [metrics-core](https://github.com/dropwizard/metrics) from 4.1.15 to 4.1.16. - [Release notes](https://github.com/dropwizard/metrics/releases) - [Commits](https://github.com/dropwizard/metrics/compare/v4.1.15...v4.1.16) Signed-off-by: dependabot-preview[bot] <support@dependabot.com> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>

view details

push time in 12 hours

PR merged talsma-ict/context-propagation

Bump metrics-core from 4.1.15 to 4.1.16 dependencies

Bumps metrics-core from 4.1.15 to 4.1.16. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dropwizard/metrics/releases">metrics-core's releases</a>.</em></p> <blockquote> <h2>v4.1.16</h2> <h2>Improvements</h2> <ul> <li>Allow configuration of the maximum length of names sent to collectd (<a href="https://github-redirect.dependabot.com/dropwizard/metrics/issues/1702">#1702</a>)</li> <li>Enforce frequency limits in CPU profile servlet (<a href="https://github-redirect.dependabot.com/dropwizard/metrics/issues/1710">#1710</a>)</li> </ul> <h2>Dependency updates</h2> <ul> <li>Bump jetty9.version from 9.4.34.v20201102 to 9.4.35.v20201120 (<a href="https://github-redirect.dependabot.com/dropwizard/metrics/issues/1712">#1712</a>)</li> <li>Bump mockito-core from 3.6.0 to 3.6.28 (<a href="https://github-redirect.dependabot.com/dropwizard/metrics/issues/1713">#1713</a>)</li> <li>Bump actions/stale from v3.0.13 to v3.0.14 (<a href="https://github-redirect.dependabot.com/dropwizard/metrics/issues/1711">#1711</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dropwizard/metrics/commit/56b97479b95ad94f2b6a5738003c474af304215e"><code>56b9747</code></a> [maven-release-plugin] prepare release v4.1.16</li> <li><a href="https://github.com/dropwizard/metrics/commit/1121d67982b9793cb424d33f3a91a84ac416244e"><code>1121d67</code></a> Allow configuration of the maxlength of names sent to collectd (<a href="https://github-redirect.dependabot.com/dropwizard/metrics/issues/1702">#1702</a>)</li> <li><a href="https://github.com/dropwizard/metrics/commit/45ae47b8d683477916a33a0ad6fe4e9a3d3a4190"><code>45ae47b</code></a> Bump mockito-core from 3.6.0 to 3.6.28 (<a href="https://github-redirect.dependabot.com/dropwizard/metrics/issues/1713">#1713</a>)</li> <li><a href="https://github.com/dropwizard/metrics/commit/054dbb861a5058a8388c68d9d93ab32bf62063a3"><code>054dbb8</code></a> Bump jetty9.version from 9.4.34.v20201102 to 9.4.35.v20201120 (<a href="https://github-redirect.dependabot.com/dropwizard/metrics/issues/1712">#1712</a>)</li> <li><a href="https://github.com/dropwizard/metrics/commit/34d47a6d88afb657e05843c7842fce0bd61bc757"><code>34d47a6</code></a> Bump actions/stale from v3.0.13 to v3.0.14 (<a href="https://github-redirect.dependabot.com/dropwizard/metrics/issues/1711">#1711</a>)</li> <li><a href="https://github.com/dropwizard/metrics/commit/42681ef4a45c3b7eb9be49d536ffd79a2e1b6583"><code>42681ef</code></a> Enforce frequency limits in CPU profile servlet (<a href="https://github-redirect.dependabot.com/dropwizard/metrics/issues/1710">#1710</a>)</li> <li><a href="https://github.com/dropwizard/metrics/commit/6a552b3aa4c788241cd25dd4d6a0a81fd54e9010"><code>6a552b3</code></a> [maven-release-plugin] prepare for next development iteration</li> <li>See full diff in <a href="https://github.com/dropwizard/metrics/compare/v4.1.15...v4.1.16">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

</details>

+1 -1

1 comment

1 changed file

dependabot-preview[bot]

pr closed time in 12 hours

issue closedhypertrace/hypertrace

Easy way to test locally built docker images with helm setup

As a contributor or someone who likes to tinker around people might build local images with changes and they should be able to test those images with helm setup using test tag.

For example, As @ravisingal pointed out we support tagOverride for pinot. so, if I want to test pinot image I built locally which will be something like this hypertrace/pinot:test I just need to add two lines in values.yaml like below:

pinot:
  image:
    repository: "hypertrace/pinot"
    tagOverride: "test"
    ....

Can we have similar way to test images using tagOverride for all the services?

closed time in 13 hours

JBAhire

issue commenthypertrace/hypertrace

Easy way to test locally built docker images with helm setup

Closing this as there's tagOverride in all services which are part of helm deployment now.

JBAhire

comment created time in 13 hours

delete branch hypertrace/hypertrace-ingester

delete branch : tagoverride-for-helm

delete time in 13 hours

push eventhypertrace/hypertrace-ingester

Jayesh Bapu Ahire

commit sha 1dd5841ee6da568d5df9cf7adcae5a18fc68d686

allows tagOverride for helm charts (#75) * allows tagOverride for helm charts * cleanup

view details

push time in 13 hours

PR merged hypertrace/hypertrace-ingester

Reviewers
allows tagOverride for helm charts

Description

addresses https://github.com/hypertrace/hypertrace/issues/55 based on: https://github.com/hypertrace/pinot/pull/18

Testing

Tested with personal EKS cluster deployment by adding following lines in values.yaml for hypertrace deployment.

Works as expected.

Checklist:

  • [x] My changes generate no new warnings
  • [na] I have added tests that prove my fix is effective or that my feature works
  • [x] Any dependent changes have been merged and published in downstream modules
+65 -16

1 comment

26 changed files

JBAhire

pr closed time in 13 hours

more