text:
octo-sts

Have you seen https://github.com/octo-sts/app/ ?
The number of people that have independently invented this solution is pretty surprising:

Apr 2022 - https://github.com/github/actions-oidc-gateway-example (first time I'd seen this!)
Jul 2022 - https://github.com/thepwagner/github-token-factory-oidc
Apr 2023 - https://github.com/helaili/github-oidc-auth-app
Jan 2024 - https://github.com/octo-sts/app

I'm sure there are more!
Sharing as you might find inspiration in any of these projects.
I'm not affiliated with Chainguard,  I abandoned my invention of this wheel when OctoSTS went open source: https://www.chainguard.dev/unchained/open-sourcing-octo-sts

Thanks!
I wasn't aware of your implementation but definitely saw the Chainguard one and you rightfully guessed that there are others 😄. I know one where they cleverly check the PR that modifies the configuration file so that no one can provide access they don't personally own already 😉 @atkinchris

Nice to see octo-sts went open source. I remember looking at this before we built our own, internal-only version with the specific feature set we needed.
For our version, we're very aware that the GitHub App is risk given it's superset of permissions. We onboard new repositories using PRs - which include a status check to limit privilege escalation. This uses the repos.getCollaboratorPermissionLevel API to check the permissions of the PR author against the repositories that they're either onboarding or editing - and rejects PRs which would grant permissions that the author does not have.

authors: atkinchris helaili thepwagner

repo: helaili/github-oidc-auth-app


text:
[TASK] Add symfony/console ^4.0 as allowed dependency (#7)

Resolves: #7

Closed as my changes was in tomasnorre/ter-client master, so could update the review without a amend commit.

source: gharchive/pull-request

repo: helhum/ter-client

license: MIT

license_type: permissive

license_source: github-api


text:
2.x: MP quickstart fails to build native-image: Main entry point class not found

Environment Details

Helidon Version: 2.6.6-SNAPSHOT
Helidon MP
JDK version:
java 11.0.11 2021-04-20 LTS
GraalVM 21.3.0 Java 11 CE (Java Version 11.0.13+7-jvmci-21.3-b05)

Problem Description
If you build quickstart-mp that is generated from the Helidon archetype the native image build fails:
[INFO] [quickstart-mp:86840]    classlist:   2,607.45 ms,  1.19 GB
[WARNING] Error: Main entry point class 'me.jdipol.mp.quickstart' not found.
[WARNING] com.oracle.svm.core.util.UserError$UserException: Main entry point class 'me.jdipol.mp.quickstart' not found.
[WARNING] 	at com.oracle.svm.core.util.UserError.abort(UserError.java:73)
[WARNING] 	at com.oracle.svm.hosted.NativeImageGeneratorRunner.buildImage(NativeImageGeneratorRunner.java:346)
[WARNING] 	at com.oracle.svm.hosted.NativeImageGeneratorRunner.build(NativeImageGeneratorRunner.java:569)
[WARNING] 	at com.oracle.svm.hosted.NativeImageGeneratorRunner.main(NativeImageGeneratorRunner.java:122)
[WARNING] 	at com.oracle.svm.hosted.NativeImageGeneratorRunner$JDK9Plus.main(NativeImageGeneratorRunner.java:599)
[INFO] [quickstart-mp:86840]      [total]:   2,655.11 ms,  1.19 GB
[WARNING] Error: Image build request failed with exit status 1

This is working with Helidon 2.6.5
Steps to reproduce
Build the archetype in the helidon-2.x branch and run:
helidon init --reset --reset --url file:///path/to/helidon-2.x-repo/archetypes/catalog/target/cli-data
# Select MP, quickstart and accept other defaults
mvn clean install -DskipTests -Pnative-image

Note: to run the helidon CLI this way you'll want the change in PR #8463

This might be related to #8332

fixed by https://github.com/helidon-io/helidon/pull/8465

source: gharchive/issue

authors: barchetta tvallin

repo: helidon-io/helidon


text:
Replace all references to master with main

Or at least, attempt to

lgtm, nice job @jamiew, merging

repo: helium/HIP


text:
[Removal]: Great Carrot Cuckoo

Hotspot Name
Great Carrot Cuckoo
Hotspot b58 Address
112ErjrvfFH1sPW6iRacAVURBzXa32u66iitjRwhCS1PuNsRXuTM
Discord Handle
hotspot-owner#9184
Hotspot Manufacturer
panther
Removal Reason
Dear helium team, I bought 4 machines from the second-hand market at a high price on January 4th, but I didn’t know that these 4 machines had already been marked in the blacklist. At that time, I just learned about helium, and I became the unfortunate one.  Victims of , please help me remove from the blacklist, thank you very much!
Modifications
No
Extra forwarders
No
Extra antennas
No
Additional Information
Dear helium team, I bought 4 machines from the second-hand market at a high price on January 4th, but I didn’t know that these 4 machines had already been marked in the blacklist. At that time, I just learned about helium, and I became the unfortunate one.  Victims of , please help me remove from the blacklist, thank you very much!

so the seller cheated you, you should file complain against him since you used legit platform.

so the seller cheated you, you should file complain against him since you used legit platform.
Thank you very much for your reply!  As you know, the complaint is useless, the seller won't refund the money, the seller has been unreachable, I think if the team could have taken steps earlier, a few months ago, to ban those cheaters and limit the crooks from transferring his machines, we  There won't be so many victims, thanks again for your reply!

We have taken into account this removal request in the next iteration of the denylist. It may take some time before it's processed. This is an automated comment due to the volume of addition and removal requests. A future tool is in the works to provide more insight into the analysis approach made by the Helium team and community members that maintain this list.

authors: Noah5623 abhay hntrax

repo: helium/denylist


text:
Crash on H

Hi,
I have the issue that the script just crashes when I go for H.
It runs on admin and worked before but now when it comes to scanning it crashes right before it scans the mainboard.
I also tried it with Win Defender off, but didnt help.
Any ideas?

My guess is that you have an Intel CPU and that the CPU microcode scanning function crashes. On some motherboards (I know of at the latest one Gigabyte motherboard) that it crashes on. If it's not even showing the motherboard info, then you likely have corruption in your Windows install. If that is the case, run this:
sc config winmgmt start= disabled net stop winmgmt Winmgmt /salvagerepository %windir%\System32\wbem Winmgmt /resetrepository %windir%\System32\wbem sc config winmgmt start= auto
Otherwise, If you want, I can work with you and attempt to get a permanent fix for the community. If not, copy and paste into your favorite text editor that has line numbers, then delete lines 1085 and 1087 and then paste it into your Admin PowerShell/Terminal console

Hello, I'm having a similar issue but its crashing after displaying motherboard info. here is what I see when it happens

This should be resolved #97


text:
#258 - Add field length feedback to campaign form

Fixes: #258
Changes campaign creation fields from  'Max 800 characters' to dynamic '70/800'.
Additionally, the Learn More URL <textarea> is checked for validity.
While working on this, I noticed the description at the top of the create page says the following:

Optionally, you can add a link for them to learn more about the topic.

However, the Submit validation expects a Learn More URL. I may need to open another issue to address this.

We may want to incorporate something like ngMessages to alert the user when the field they've entered is not valid: https://docs.angularjs.org/api/ngMessages/directive/ngMessages

repo: helloGov/webapp


text:
Sugar: support percentages

Support using a % sign next to numbers such as 6% or 1.5% which would simply interpret the number a number[n+2]. From a parsing standpoint, we need to require the % to be right next to the number to avoid confusion with 6 % 4 for instance.

We should also consider having a percentage type
type percentage[n] number[n] constrained_by {
  return 0 <= percentage && percentage <= 1
}

Implemented in #75!

authors: pascallouisperez workmajj

repo: helloeave/worksheets


text:
Remove chancez as owner/maintainer to etcd-operator/nginx-ingress

I don't use either of these charts anymore and don't keep up with the
upstream projects since I don't use them any longer. Removing myself as
there are other maintainers.

What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ ] DCO signed
[ ] Chart Version bumped
[ ] Variables are documented in the README.md

@chancez you need to sign the DCO and bump the chart version of the nginx

Huh, I guess that's true with CI. I guess I need to update the DCO with my redhat email.

@chancez you need to sign the DCO and bump the chart version of both. sad that are you leaving :(

@cpanato should be ready

/assign @prydonius

/assign @lachie83

/lgtm

authors: chancez cpanato unguiculus

repo: helm/charts


text:
[stable/prometheus-operator] Update deps for grafana v6

What this PR does / why we need it:
This patch bumps the Grafana subchart version to v2.2.* (appVersion v6.0.*).
Grafana v6 includes support for Loki which is a simple, scalable logging solution :)
There's also a new Explore panel which allows you to work on your queries.
https://github.com/grafana/grafana/releases/tag/v6.0.0
Special notes for your reviewers:
@gianrubio @vsliouniaev
There are a few chart features that have been added in the past few commits on stable/grafana.
https://github.com/helm/charts/commits/master/stable/grafana
I've reviewed them, and they look non-consequential.
( Even the chart major version bump just updated the image tag. )
I've deployed this setup to an existing GKE cluster, and it's working well.
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/lgtm

authors: cpanato stealthybox


text:
New chart submission [stable/codedx]

Signed-off-by: Tyler Camp tylermatthewcamp@gmail.com

What this PR does / why we need it: Installtion chart for Code Dx
Special notes for your reviewer:
Some things of note:

We use a template for resource labels, since there are many resource that have many of the same labels. I haven't seen this used in other charts but also haven't seen anything explicitly discouraging this. (Template here and sample usage here)
We've got many separate secrets that could probably be combined into a single secret in some cases. I'll take a second look at this if it's brought up as a concern.
There is a PNG diagram of the deployed resources in the repository. This can be removed and hosted elsewhere if necessary.
Many of the "lines added" are from documentation files, sample files, and application-specific template files ("codedx.props")

This chart originally developed in: https://github.com/codedx/codedx-kubernetes (which has the full commit history)
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

@viglesiasce @prydonius Can we get myself and @ssalas added as collaborators on this repo and get an estimate on when we can expect review/feedback for this chart? We understand there are a lot of pull requests and this is a relatively large one. Thanks for your time.

hey @tylercamp
Have you considered hosting this chart and adding it to helm hub?
https://github.com/helm/hub/blob/master/Repositories.md

@maorfr Thanks for your reply, we've considered it but would be more convenient for end-users if it was available in the official Stable repo. We'd also appreciate the review in general, if possible. We understand if it's unlikely for this to get a review or possible acceptance.

hey @tylercamp, thanks for your reply!
i completely understand your view. having said that, the way forward is helm hub, and not this charts repository. see this for more information.
you are welcome to keep this PR open and hopefully get a review!
at the same time, i would further explore the helm hub option, as these are getting merged in faster and you will get some community traction :)

authors: maorfr tylercamp


text:
[stable/traefik] Make dashboard ingress optional

This PR allows for the optional creation of the Traefik dashboard ingress rule (set to true by default to preserve existing functionality). In some environments it may not be desirable to create the ingress rule, and instead rely on other methods (such as Kubectl port-forward) in order to access the dashboard application.

fixes #15684

@krancour @emilevauge @dtomcej @ldez

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/assign @ldez

/assign @krancour

/assign @dtomcej

Awesome. Came here looking for a solution and found this!
Looking forward to it being available! Thanks @adhodgson1

/assign @dtomcej

:-(
On Thu, 3 Oct 2019 at 11:39, stale[bot] notifications@github.com wrote:

This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Any
further update will cause the issue/pull request to no longer be considered
stale. Thank you for your contributions.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/helm/charts/pull/15686?email_source=notifications&email_token=AA42IJWOARLGYX6DHXN7GR3QMXDX7A5CNFSM4IE3LWRKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAHYZQQ#issuecomment-537889986,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA42IJUJXQMAMIUJ35XRLDTQMXDX7ANCNFSM4IE3LWRA
.

/ok-to-test

/test pull-charts-e2e

authors: adhodgson1 chelnak ldez zanhsieh


text:
stable/airflow Added support for airflow session affinity

Signed-off-by: Stijn De Haes stijndehaes@gmail.com

Is this a new chart

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

What this PR does / why we need it:
It adds support for session affinity. When doing a rolling upgrade with baked in dags. Dags appear and disappear because the image is changed. The session affinity can fix this if properly configured.
Which issue this PR fixes

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

@gsemet Can I ask your review for this PR.

/lgtm

Not sure to understand why this does not work ?

During a rolling upgrade we have 2 versions of the airflow image running: one with the old version of the dags and one with the new version. Maybe in the second version we have an extra dag. If you refresh the page you hit on of the two airflow web servers. One that has on dag less and this looks funky.

Ah, wrong PR, this one is ok, I was questioning actually on the other one !

Ah, wrong PR, this one is ok, I was questioning actually on the other one !

That makes more sense :)

authors: gsemet stijndehaes


text:
[stable/cluster-overprovisioner] add pod security context

Is this a new chart
No
What this PR does / why we need it:
Adds ability to configure the podSecurityContext.  Will allow running this chart under a more restrictive PSP.
Which issue this PR fixes
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @mmingorance-dh

/lgtm

authors: mmingorance-dh pwillie


text:
Error: INSTALLATION FAILED: failed to download "oci://myrepo.azurecr.io/charts/haveged" at version "0.1.1"

Output of helm version:
version.BuildInfo{Version:"v3.7.0", GitCommit:"eeac83883cb4014fe60267ec6373570374ce770b", GitTreeState:"clean", GoVersion:"go1.16.8"}

Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.11", GitCommit:"c6a2f08fc4378c5381dd948d9ad9d1080e3e6b33", GitTreeState:"clean", BuildDate:"2021-05-12T12:27:07Z", GoVersion:"go1.15.12", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.13", GitCommit:"cdb117ffa2e5de1593521791bbfe53b43dfa68c7", GitTreeState:"clean", BuildDate:"2021-08-31T00:01:35Z", GoVersion:"go1.15.14", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.): AKS
Here are the commands I've run
> export HELM_EXPERIMENTAL_OCI=1

> helm registry login myrepo.azurecr.io --username XXXX --password XXX
Login Succeeded

> helm push haveged-0.1.1.tgz oci://myrepo.azurecr.io/charts
Pushed: myrepo.azurecr.io/charts/haveged:0.1.1
Digest: sha256:1234567900000...

> helm install haveged oci://myrepo.azurecr.io/charts/haveged --version 0.1.1
Error: INSTALLATION FAILED: failed to download "oci://myrepo.azurecr.io/charts/haveged" at version "0.1.1"

Could you run helm install with the --debug so we can have more information? Thanks :)

401 Unauthorized but other commands work.
> export HELM_EXPERIMENTAL_OCI=1
> helm registry login myrepo.azurecr.io --username XXXXXXXXX --password XXXXXXXXXX
WARNING: Using --password via the CLI is insecure. Use --password-stdin.
Login Succeeded

helm pull & helm list work
> helm pull oci://myrepo.azurecr.io/charts/haveged --version 0.1.1
Pulled: myrepo.azurecr.io/charts/haveged:0.1.1
Digest: sha256:xxxxxxxxxxxxxxxx

> helm list
NAME    NAMESPACE       REVISION        UPDATED STATUS  CHART   APP VERSION

> helm install haveged oci://myrepo.azurecr.io/charts/haveged --version 0.1.1 --debug
install.go:178: [debug] Original chart version: "0.1.1"
Error: INSTALLATION FAILED: failed to authorize: failed to fetch anonymous token: unexpected status: 401 Unauthorized
helm.go:88: [debug] unexpected status: 401 Unauthorized
github.com/containerd/containerd/remotes/docker/auth.FetchToken
        github.com/containerd/containerd@v1.5.4/remotes/docker/auth/fetch.go:187
github.com/containerd/containerd/remotes/docker.(*authHandler).doBearerAuth
        github.com/containerd/containerd@v1.5.4/remotes/docker/authorizer.go:304
github.com/containerd/containerd/remotes/docker.(*authHandler).authorize
        github.com/containerd/containerd@v1.5.4/remotes/docker/authorizer.go:228
github.com/containerd/containerd/remotes/docker.(*dockerAuthorizer).Authorize
        github.com/containerd/containerd@v1.5.4/remotes/docker/authorizer.go:112
github.com/containerd/containerd/remotes/docker.(*request).authorize
        github.com/containerd/containerd@v1.5.4/remotes/docker/resolver.go:475
github.com/containerd/containerd/remotes/docker.(*request).do
        github.com/containerd/containerd@v1.5.4/remotes/docker/resolver.go:539
github.com/containerd/containerd/remotes/docker.(*request).doWithRetries
        github.com/containerd/containerd@v1.5.4/remotes/docker/resolver.go:551
github.com/containerd/containerd/remotes/docker.(*request).doWithRetries
        github.com/containerd/containerd@v1.5.4/remotes/docker/resolver.go:564
github.com/containerd/containerd/remotes/docker.(*dockerResolver).Resolve
        github.com/containerd/containerd@v1.5.4/remotes/docker/resolver.go:280
oras.land/oras-go/pkg/oras.Pull
        oras.land/oras-go@v0.4.0/pkg/oras/pull.go:45
helm.sh/helm/v3/internal/experimental/registry.(*Client).Pull
        helm.sh/helm/v3/internal/experimental/registry/client.go:235
helm.sh/helm/v3/pkg/getter.(*OCIGetter).get
        helm.sh/helm/v3/pkg/getter/ocigetter.go:57
helm.sh/helm/v3/pkg/getter.(*OCIGetter).Get
        helm.sh/helm/v3/pkg/getter/ocigetter.go:36
helm.sh/helm/v3/pkg/downloader.(*ChartDownloader).DownloadTo
        helm.sh/helm/v3/pkg/downloader/chart_downloader.go:99
helm.sh/helm/v3/pkg/action.(*ChartPathOptions).LocateChart
        helm.sh/helm/v3/pkg/action/install.go:753
main.runInstall
        helm.sh/helm/v3/cmd/helm/install.go:194
main.newInstallCmd.func2
        helm.sh/helm/v3/cmd/helm/install.go:125
github.com/spf13/cobra.(*Command).execute
        github.com/spf13/cobra@v1.2.1/command.go:856
github.com/spf13/cobra.(*Command).ExecuteC
        github.com/spf13/cobra@v1.2.1/command.go:974
github.com/spf13/cobra.(*Command).Execute
        github.com/spf13/cobra@v1.2.1/command.go:902
main.main
        helm.sh/helm/v3/cmd/helm/helm.go:87
runtime.main
        runtime/proc.go:225
runtime.goexit
        runtime/asm_amd64.s:1371
failed to fetch anonymous token
github.com/containerd/containerd/remotes/docker.(*authHandler).doBearerAuth
        github.com/containerd/containerd@v1.5.4/remotes/docker/authorizer.go:306
github.com/containerd/containerd/remotes/docker.(*authHandler).authorize
        github.com/containerd/containerd@v1.5.4/remotes/docker/authorizer.go:228
github.com/containerd/containerd/remotes/docker.(*dockerAuthorizer).Authorize
        github.com/containerd/containerd@v1.5.4/remotes/docker/authorizer.go:112
github.com/containerd/containerd/remotes/docker.(*request).authorize
        github.com/containerd/containerd@v1.5.4/remotes/docker/resolver.go:475
github.com/containerd/containerd/remotes/docker.(*request).do
        github.com/containerd/containerd@v1.5.4/remotes/docker/resolver.go:539
github.com/containerd/containerd/remotes/docker.(*request).doWithRetries
        github.com/containerd/containerd@v1.5.4/remotes/docker/resolver.go:551
github.com/containerd/containerd/remotes/docker.(*request).doWithRetries
        github.com/containerd/containerd@v1.5.4/remotes/docker/resolver.go:564
github.com/containerd/containerd/remotes/docker.(*dockerResolver).Resolve
        github.com/containerd/containerd@v1.5.4/remotes/docker/resolver.go:280
oras.land/oras-go/pkg/oras.Pull
        oras.land/oras-go@v0.4.0/pkg/oras/pull.go:45
helm.sh/helm/v3/internal/experimental/registry.(*Client).Pull
        helm.sh/helm/v3/internal/experimental/registry/client.go:235
helm.sh/helm/v3/pkg/getter.(*OCIGetter).get
        helm.sh/helm/v3/pkg/getter/ocigetter.go:57
helm.sh/helm/v3/pkg/getter.(*OCIGetter).Get
        helm.sh/helm/v3/pkg/getter/ocigetter.go:36
helm.sh/helm/v3/pkg/downloader.(*ChartDownloader).DownloadTo
        helm.sh/helm/v3/pkg/downloader/chart_downloader.go:99
helm.sh/helm/v3/pkg/action.(*ChartPathOptions).LocateChart
        helm.sh/helm/v3/pkg/action/install.go:753
main.runInstall
        helm.sh/helm/v3/cmd/helm/install.go:194
main.newInstallCmd.func2
        helm.sh/helm/v3/cmd/helm/install.go:125
github.com/spf13/cobra.(*Command).execute
        github.com/spf13/cobra@v1.2.1/command.go:856
github.com/spf13/cobra.(*Command).ExecuteC
        github.com/spf13/cobra@v1.2.1/command.go:974
github.com/spf13/cobra.(*Command).Execute
        github.com/spf13/cobra@v1.2.1/command.go:902
main.main
        helm.sh/helm/v3/cmd/helm/helm.go:87
runtime.main
        runtime/proc.go:225
runtime.goexit
        runtime/asm_amd64.s:1371
failed to authorize
github.com/containerd/containerd/remotes/docker.(*request).do
        github.com/containerd/containerd@v1.5.4/remotes/docker/resolver.go:540
github.com/containerd/containerd/remotes/docker.(*request).doWithRetries
        github.com/containerd/containerd@v1.5.4/remotes/docker/resolver.go:551
github.com/containerd/containerd/remotes/docker.(*request).doWithRetries
        github.com/containerd/containerd@v1.5.4/remotes/docker/resolver.go:564
github.com/containerd/containerd/remotes/docker.(*dockerResolver).Resolve
        github.com/containerd/containerd@v1.5.4/remotes/docker/resolver.go:280
oras.land/oras-go/pkg/oras.Pull
        oras.land/oras-go@v0.4.0/pkg/oras/pull.go:45
helm.sh/helm/v3/internal/experimental/registry.(*Client).Pull
        helm.sh/helm/v3/internal/experimental/registry/client.go:235
helm.sh/helm/v3/pkg/getter.(*OCIGetter).get
        helm.sh/helm/v3/pkg/getter/ocigetter.go:57
helm.sh/helm/v3/pkg/getter.(*OCIGetter).Get
        helm.sh/helm/v3/pkg/getter/ocigetter.go:36
helm.sh/helm/v3/pkg/downloader.(*ChartDownloader).DownloadTo
        helm.sh/helm/v3/pkg/downloader/chart_downloader.go:99
helm.sh/helm/v3/pkg/action.(*ChartPathOptions).LocateChart
        helm.sh/helm/v3/pkg/action/install.go:753
main.runInstall
        helm.sh/helm/v3/cmd/helm/install.go:194
main.newInstallCmd.func2
        helm.sh/helm/v3/cmd/helm/install.go:125
github.com/spf13/cobra.(*Command).execute
        github.com/spf13/cobra@v1.2.1/command.go:856
github.com/spf13/cobra.(*Command).ExecuteC
        github.com/spf13/cobra@v1.2.1/command.go:974
github.com/spf13/cobra.(*Command).Execute
        github.com/spf13/cobra@v1.2.1/command.go:902
main.main
        helm.sh/helm/v3/cmd/helm/helm.go:87
runtime.main
        runtime/proc.go:225
runtime.goexit
        runtime/asm_amd64.s:1371
INSTALLATION FAILED
main.newInstallCmd.func2
        helm.sh/helm/v3/cmd/helm/install.go:127
github.com/spf13/cobra.(*Command).execute
        github.com/spf13/cobra@v1.2.1/command.go:856
github.com/spf13/cobra.(*Command).ExecuteC
        github.com/spf13/cobra@v1.2.1/command.go:974
github.com/spf13/cobra.(*Command).Execute
        github.com/spf13/cobra@v1.2.1/command.go:902
main.main
        helm.sh/helm/v3/cmd/helm/helm.go:87
runtime.main
        runtime/proc.go:225
runtime.goexit
        runtime/asm_amd64.s:1371

Hello it seems that this is the same problem as in the https://github.com/helm/helm/issues/10122

Having the same isssue. What's super weird is it seems to be working on windows, but not on linux. Using 3.7.1 on both platforms.  On linux helm pull oc://.... did work. As a workaround, if you combine helm pull --untar --untardir {dest} and helm install name {dest}, it ends up working.

Thanks @marek-marusic-loepfe. Closing as a duplicate.

In my case, I don't think overriding the env var fix Works, it's already what I'm doing. This or the other bug should be reopened.

authors: bacongobbler dkirrane marek-marusic-loepfe scabana zonggen

repo: helm/helm


text:
ValuesYaml is mutated at case of Linting

I guess there is a bug when I create a client with Linting option and call client.InstallChart providing ValuesYaml (some code fragments have been omitted for brevity):
opt := &helmclient.KubeConfClientOptions{
    Options: &helmclient.Options{
	Linting: true
    },
}
client, err := helmclient.NewClientFromKubeConf(opt)
spec := &helmclient.ChartSpec{
    ValuesYaml: valuesYaml,
}
release, err := client.InstallChart(ctx, spec, opt)

The bug is located at the following section https://github.com/helm/helm/blob/v3.11.2/pkg/lint/rules/values.go#L74,L75:
coalescedValues := chartutil.CoalesceTables(make(map[string]interface{}, len(overrides)), overrides)
coalescedValues = chartutil.CoalesceTables(coalescedValues, values)

It sometimes mutates input argument - overrides (the second line at the code snippet) what leads to mutation of ValuesYaml derived argument and at least wrong (additional rows) USER-SUPPLIED VALUES output when I eventually call helm get all release-name:
expected output:
image:
  repository: v0

actual:
image:
  repository: v0
  tag: v2
  pullPolicy: v3

Provided default values.yaml from the chart:
image:
  repository: v1
  tag: v2
  pullPolicy: v3

values.yaml from ValuesYaml:
image:
  repository: v0

This looks right to me. When you pass values, they're merged with the values.yaml in the chart.

@joejulian Yes, it is right to merge this values. But there is USER-SUPPLIED VALUES and COMPUTED VALUES (merged) to understand where each value came from and at this case value.yaml values leak to user supplied section.

Hey @joejulian I would like to contribute to this issue


text:
Error: INSTALLATION FAILED: repo bitnami not found

when I install mysql with my own yaml, I encountered a strange problem. The result of repo list shows that bitnami repo is already in my ubuntu 24.04, but I cannot install mysql
helm repo list
NAME   	URL
bitnami	https://charts.bitnami.com/bitnami

sudo helm install my-db -f values.yaml bitnami/mysql
Error: INSTALLATION FAILED: repo bitnami not found

I can also find the bitnami/mysql
helm search repo bitnami/mysql
NAME         	CHART VERSION	APP VERSION	DESCRIPTION
bitnami/mysql	11.1.16      	8.4.2      	MySQL is a fast, reliable, scalable, and easy t...

Output of helm version:
version.BuildInfo{Version:"v3.16.1", GitCommit:"5a5449dc42be07001fd5771d56429132984ab3ab", GitTreeState:"clean", GoVersion:"go1.22.7"}
Output of kubectl version:
Client Version: v1.30.4+k3s1
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.30.4+k3s1
Cloud Provider/Platform (AKS, GKE, Minikube etc.): k3s
thanks for your reply~

It's because you used sudo

It's because you used sudo
Thank you for your comment. The first time I executed the command without sudo, I received a 'permission denied' error. After your comment, I modified the permissions of the 'k3s.yaml' file, and it works!


text:
Windows; Helm 2.9.0, Error: no available release name found

Output of helm version:
Client: &version.Version{SemVer:"v2.9.0", GitCommit:"f6025bb9ee7daf9fee0026541c90a6f557a3e0bc", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.0", GitCommit:"f6025bb9ee7daf9fee0026541c90a6f557a3e0bc", GitTreeState:"clean"}
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.2", GitCommit:"5fa2db2bd46ac79e5e00a4e6ed24191080aa463b", GitTreeState:"clean", BuildDate:"2018-01-18T10:09:24Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"9+", GitVersion:"v1.9.6-gke.1", GitCommit:"cb151369f60073317da686a6ce7de36abe2bda8d", GitTreeState:"clean", BuildDate:"2018-04-07T22:06:59Z", GoVersion:"go1.9.3b4", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
GKE Kubernetes  1.9.6-gke.1 : 8 vm cluster with each vm having 1 core and custom 6.5 GB ram.
I also ran the below commands to make sure tiller is working properly:
kubectl create serviceaccount --namespace kube-system tiller
kubectl create clusterrolebinding tiller-cluster-rule --clusterrole=cluster-admin --serviceaccount=kube-system:tiller
kubectl patch deploy --namespace kube-system tiller-deploy -p "{"spec":{"template":{"spec":{"serviceAccount":"tiller"}}}}"
While helm 2.8.2 on gke with k8s version: 1.8.8-gke.0 is working properly after running those commands.

Same issue on macOS (kubespray, vagrant).

Can you test and see if this was fixed in 2.9.1? We addressed a similar bug in that release.

Closing due to inactivity. Please open a new ticket against Helm 3 if this issue persists. Thanks!

authors: bacongobbler petermetz prateekrastogi


text:
Containers never get past pending

Output of helm version:
Client: &version.Version{SemVer:"v2.10.0", GitCommit:"9ad53aac42165a5fadc6c87be0dea6b115f93090", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.10.0", GitCommit:"9ad53aac42165a5fadc6c87be0dea6b115f93090", GitTreeState:"clean"}

Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.3", GitCommit:"a4529464e4629c21224b3d52edfe0ea91b072862", GitTreeState:"clean", BuildDate:"2018-09-10T11:44:21Z", GoVersion:"go1.11", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.3", GitCommit:"2bba0127d85d5a46ab4b778548be28623b32d0b0", GitTreeState:"clean", BuildDate:"2018-05-28T20:13:43Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.):
aws - EKS
I have my kube cluster up and running with https://eksctl.io
I can do regular kubectl -f commands without an issue.
When I try to do helm charts, my pods stay in Pending status forever.
Steps:
helm init
helm repo update
helm install stable/mysql

Several minutes later
kubectl get pods
NAME                                         READY     STATUS    RESTARTS   AGE
loitering-chinchilla-mysql-74ff8d654-9j96k   0/1       Pending   0          9m

kubectl logs loitering-chinchilla-mysql-74ff8d654-9j96k
# no output/empty

I have tried both m5 and m4 type instances in AWS for the nodes.

What's the output of helm describe po loitering-chinchilla-mysql-74ff8d654-9j96k?

kubectl describe po bulging-orangutan-mysql-5796c85d8c-7khd5
Name:           bulging-orangutan-mysql-5796c85d8c-7khd5
Namespace:      default
Node:           <none>
Labels:         app=bulging-orangutan-mysql
                pod-template-hash=1352741847
Annotations:    <none>
Status:         Pending
IP:
Controlled By:  ReplicaSet/bulging-orangutan-mysql-5796c85d8c
Init Containers:
  remove-lost-found:
    Image:      busybox:1.25.0
    Port:       <none>
    Host Port:  <none>
    Command:
      rm
      -fr
      /var/lib/mysql/lost+found
    Environment:  <none>
    Mounts:
      /var/lib/mysql from data (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-r6n4c (ro)
Containers:
  bulging-orangutan-mysql:
    Image:      mysql:5.7.14
    Port:       3306/TCP
    Host Port:  0/TCP
    Requests:
      cpu:      100m
      memory:   256Mi
    Liveness:   exec [sh -c mysqladmin ping -u root -p${MYSQL_ROOT_PASSWORD}] delay=30s timeout=5s period=10s #success=1 #failure=3
    Readiness:  exec [sh -c mysqladmin ping -u root -p${MYSQL_ROOT_PASSWORD}] delay=5s timeout=1s period=10s #success=1 #failure=3
    Environment:
      MYSQL_ROOT_PASSWORD:  <set to the key 'mysql-root-password' in secret 'bulging-orangutan-mysql'>  Optional: false
      MYSQL_PASSWORD:       <set to the key 'mysql-password' in secret 'bulging-orangutan-mysql'>       Optional: false
      MYSQL_USER:
      MYSQL_DATABASE:
    Mounts:
      /var/lib/mysql from data (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-r6n4c (ro)
Conditions:
  Type           Status
  PodScheduled   False
Volumes:
  data:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  bulging-orangutan-mysql
    ReadOnly:   false
  default-token-r6n4c:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-r6n4c
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason            Age                From               Message
  ----     ------            ----               ----               -------
  Warning  FailedScheduling  4m (x37 over 15m)  default-scheduler  pod has unbound PersistentVolumeClaims (repeated 2 times)

I'm going to close this ticket due to inactivity, but please re-open if this still needs to be addressed. Thanks!

The issue seems to be arising from not setting the Persistent volume properties. Warning  FailedScheduling  4m (x37 over 15m)  default-scheduler  pod has unbound PersistentVolumeClaims (repeated 2 times)
I did try deploying with persistent volume, still hitting into same issue.
helm install sample-devdb bitnami/mysql -n sample-namespace --set persistence.storageClass=<storage-class-name>
Logs are empty:
kubectl logs   pod/sample-devdb-mysql-0 -n sample-namespace mysql
Can you please conclude/close this thread with some useful steps.

I was hitting similar issue as discussed in below thread.
https://github.com/bitnami/charts/issues/7433
Cross-posting if anybody hits into same issue.

authors: bacongobbler kylesloan sandeepV2


text:
Helm 3 unable to reach cluster

Output of helm version:
version.BuildInfo{Version:"v3.0.0", GitCommit:"e29ce2a54e96cd02ccfce88bee4f58bb6e2a28b6", GitTreeState:"clean", GoVersion:"go1.13.4"}
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.1", GitCommit:"4485c6f18cee9a5d3c3b4e523bd27972b1b53892", GitTreeState:"clean", BuildDate:"2019-07-18T09:18:22Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
AWS kops cluster
I am trying to install a helm chart that is publically available and when doing do I get an error Error: Kubernetes cluster unreachable which is preventing me from installing said chart.
Chart I am trying to install: https://hub.helm.sh/charts/architectminds/aws-ecr-credential
Steps to reproduce:
Install Helm 3 using install script
helm repo add architectminds https://architectminds.github.io/helm-charts/
helm repo update
helm install  aws-ecr-credential architectminds/aws-ecr-credential --set targetNamespace=development --set-string aws.account=<account ID> --set aws.region=us-east-1 --set aws.accessKeyId=base64== --set aws.secretAccessKey=base64==  --dry-run

Error message: Error: Kubernetes cluster unreachable
Same error message is produced when appling directly without dry run.

Can you run kubectl cluster-info?  Can it reach the cluster?

I'm having the same issue here. It doesn't seem to be looking at my current context.

You can see that helm doesn't reach the cluster until I explicitly provide the config file that contains my current context.
If it helps, I have multiple files within the ~/.kube directory and my $KUBECONFIG contains all of them (i.e. /path/to/first.conf:/path/to/second.conf:/path/to/third.conf).

After install helm on ubuntu i was also experiencing this issue.
I just reran
kubectl config set-context <context>

And it worked

@particledecay @FredM @kevupton
From Organizing Cluster Access Using kubeconfig Files:
"By default, kubectl looks for a file named config in the $HOME/.kube directory. You can specify other kubeconfig files by setting the KUBECONFIG environment variable or by setting the --kubeconfig flag."
Helm works pretty much the same as kubectl wrt cluster access.
When you have multiple kubeconfig files specified in $KUBECONFIG, then the first file is used by default. You therefore need to set the context if you want to use another file instead. With kubectl, you can use command: kubectl config use-context.
Alternatively, you can also use tools like kubectx for this: https://github.com/ahmetb/kubectx. Or use --kube-context flag when running the Helm command.
Organizing Cluster Access Using kubeconfig Files provide details on the cluster access.

@pageanengineer Is this still an issue for you or can this issue be closed?

authors: hickeyma kevupton marckhouzam pageanengineer particledecay


text:
Enabling hide secrets on install and upgrade dry run

This change adds a new flag to the install and upgrade commands in the Helm client and properties to the install and upgrade action. The new flag is --hide-secret and can only be used with the --dry-run flag.
The --dry-run flag is designed to send all chart rendered manifests to stdout so that they can be inspected.
When the --hide-secret flag is used they are absent from the output. This is because the output is checked for openapi validation and to ensure it is valid yaml. While openapi validation can be skipped, yaml validation is not easily skipped. So, secrets are removed from the output.

What this PR does / why we need it: #7275
Special notes for your reviewer: N/A
If applicable:

[x] this PR contains documentation
[x] this PR contains unit tests
[x] this PR has been tested for backwards compatibility

Is it possible to add the same option for the non-dry-run modes? IIRC, the secret values are still shown when you install/upgrade (which I expect, but it would be convenient to hide that information in output; currently if you want to watch your helm upgrade in CI, but don't want secrets in logs, you basically have to invent a weird program that will read a file or pipe unbuffered and filter out the secret values while still outputting all the other lines in real time)

hi, updating docs:
https://github.com/helm/helm-www/pull/1608

authors: aviadshimoni mattfarina peterwwillis


text:
DropdownV2: Resolve item render updates

DropdownV2: Resolve item render updates

This update resolves the issue for DropdownV2 where new items being passed
may (or may not) re-render correctly.
The issue was Dropdown.Container, which handles the diff'ing + state
updating process from external props.
The nextState that was building was being clobbered over as it trickles
down the conditional logic tree.

Unrelated, I fixed the AnimatedGroup test so that it stops spitting out
errors during the test run.
Resolves: https://github.com/helpscout/hsds-react/issues/474

Pull Request Test Coverage Report for Build 1615

7 of 7 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 1614:
0.0%

Covered Lines:
6203

Relevant Lines:
6203

💛  - Coveralls

authors: ItsJonQ coveralls

repo: helpscout/hsds-react


text:
ActionSelect: Fix resize and refocus interactions

ActionSelect: Fix resize and refocus interactions
This update fixes the resizing and refocus interactions when an item
is selected from the Dropdown.
A special focus util has been added to ensure the scroll position doesn't
jump on focus.
The resizing mechanism in ActionSelect has been optimized to only fire during
a new selection, rather than on children change.
Checkbox improvements
Ensure Checkbox/Radio aren't display block, by default

Pull Request Test Coverage Report for Build 2182

16 of 16 (100.0%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 2181:
0.0%

Covered Lines:
10792

Relevant Lines:
10792

💛  - Coveralls


text:
HSDS-77 Fix Truncate component to show tooltip when truncated on splitter'

JIRA: https://helpscout.atlassian.net/browse/HSDS-77
Problem

When using <Truncate /> with a splitter prop so you can truncate email addresses, the tooltip feature isn't working. It should show the non-truncated email address on hover.

If you have an email address like g@example.com, with the splitter prop set, it renders out as g @example.com. This is because the first span has a min-width of 21px, which is wider than a character.

Solution
Tooltip feature:
The <Tooltip /> component will wrap around the truncated content if a) the showTooltipOnTruncate prop is true and b) this.state.isTruncated is true. The latter makes sure that we only show the Tooltip if the content has been truncated.
For content that isn't using a splitter, one parent <span> wraps around the content, and we can easily compare the length of the content to the width of the span and see if it overflows using this.contentNode.offsetWidth > this.node.offsetWidth. However, content that IS being truncated based of the presence of the splitter has a different HTML structure and the width of the two spans containing the pre- and post- splitter content is very nested.
This PR gains access to those nested spans to compare their combined width to that of their container in order to accurately update this.state.isTruncated and allow the <Tooltip /> to wrap the truncated text.
Spacing issue
A solution to the spacing problem has already been implemented by Juan Pablo in this PR and has been reimplemented here.
Testing
I've updated the Truncated => Tooltips story to include an email address.

[ ] There should be no tooltip if the email is not truncated.
[ ] There should be a tooltip if the email is truncated
https://share.getcloudapp.com/o0ux4wQR

I've updated the Truncated => default story to include an email address with a one character user name.

[ ] There should be no space between the username and the @ sign, e.g. a@domain.com.

Whoops, need to fix a test.

Pull Request Test Coverage Report for Build 2653

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 2646:
0.0%

Covered Lines:
21

Relevant Lines:
21

💛  - Coveralls

@knicklabs I tested the (accidental) 2.65.2 release on the branch for HSAPP-89 and saw that the spacing issue is gone and tooltips work. I wasn't able to find the spacing issue in the Customer Management work on sometestco, but maybe I was looking in the wrong spot?


text:
Don't index project index pages with querystring.

This adds a canonical meta tag to all pages, where the url is the same as the page. We can override the canonical_url, as we do here with Project listings, where we strip out the query string.
e.g. https://helpwithcovid.com/projects?skills=Analytics,Biology gets indexed only as https://helpwithcovid.com/projects
Fixes #170

@sradu @jamiew actually, maybe I should just apply the canonical_url to the Projects page, instead of all pages? Not sure if there are unintended side effects for the latter.

It's a recommended best practice for all pages so I think it should be fine
Thanks for the patch!
On Wed, Apr 15, 2020 at 8:50 PM Tieg Zaharia notifications@github.com
wrote:

@sradu https://github.com/sradu @jamiew https://github.com/jamiew
actually, maybe I should just apply the canonical_url to the Projects page,
instead of all pages? Not sure if there are unintended side effects for the
latter.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/helpwithcovid/covid-volunteers/pull/171#issuecomment-614351420,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAAO3ZOHIQAQ6HDUDJ5BA3RMZI6TANCNFSM4MJAHKDQ
.

--
@jamiew https://twitter.com/jamiew | https://jamiedubs.com
https://www.jamiedubs.com/

authors: jamiew tiegz

repo: helpwithcovid/covid-volunteers


text:
Feat/localization

Localization Improvements: Implemented the PyBabel system to automate the translation process of marked strings, substantially improving our app's multilingual capabilities.
It includes setting up 'en' locale and updating 'sv' translations.
Phrase Feature Addition: Introduced a feature in 'phrase' with default value and replacement variable. Also implemented handling of default language.
Main Module Enhancement: An important unit 'set_language' introduced in the main module.
Test Additions: Passing tests were added.
Following are the steps to manage the Babel system with .po and .mo files:
PyBabel is a part of Babel library, which is a Python package that provides tools for internationalizing and localizing Python applications. To install the Babel package, see below.
poetry add babel
1 - .po File Generation: The Babel library provides a command pybabel extract -F babel.cfg -o messages.pot, which crawls through the source code and creates a .pot file with all marked strings.
2 - Translation Catalog Creation: After the .po file is derived from .pot template, a translation catalog for a language is created via pybabel init -i locale/messages.pot -d locale -l <language-code> where  is the code for the intended language like 'en' for English.
3 - .po File Update: The translation strings get filled in this file. Any updates to the original strings need the .po file to be updated, by running pybabel update -i locale/messages.pot -d locale -l <language-code> --ignore-obsolete -N
4 - .mo File Compilation: The .po file is compiled to a binary .mo file before deployment. Use the command pybabel compile -d locale -l <language-code>
Remember, .po files are human-readable and editable. These are the files to which translators add their translations. The .mo file is machine-readable and is the format used by the system to display translations in the application. Please refer to Python Babel documentation for more detailed instructions.

Failing tests when running Pytest:
1. Switch to branch `feat/localization`.

2. Launched Pytest with args `fai-backend/tests --no-header --no-summary -q`.

Error log:
    def translate(self, key: str) -> str:
        if not self.translation:
>           raise ValueError('Language not set. Call set_language() before calling translate()')
E           ValueError: Language not set. Call set_language() before calling translate()

../fai_backend/phrase.py:27: ValueError

Fixed!

repo: helsingborg-stad/F-AI


text:
Added sequence field parsing

hi, I have added parsing of the field "update_seq" to StreamingViewResult. Can you merge this update and deploy new version? Or should I do it myself and work with the local repository

worth bearing in mind that this will break against CouchDB 2.0 / Cloudant / BigCouch where update_seq is non-numeric. To be compatible, treat update_seq as a json object (maybe something similar to https://github.com/helun/Ektorp/pull/240).

authors: Zajs willholley

repo: helun/Ektorp

license_source: bigquery


text:
Loop

Hi, how can I do loop for gallery?
Thanks for nice script :)

Hi Anatoliy, just want to make sure I understand.
By loop, do you mean clicking next on the last picture gives you the first picture?

Yes, I mean it.

Updated to 2.1.3 which includes this feature.

Thank you very much.

repo: henrygd/bigpicture

license: mit


text:
🛑 hentaiOS Forum is down

In 38cf024, hentaiOS Forum (https://forum.helluvaos.com) was down:

HTTP code: 403
Response time: 613 ms

Resolved: hentaiOS Forum is back up in 55d98cd after 11 minutes.


text:
🛑 hentaiOS Blog is down

In b1c0b27, hentaiOS Blog (https://blog.hentaios.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: hentaiOS Blog is back up in 9aeb55f after 5 minutes.


text:
🛑 hentaiOS Wiki is down

In 45ce94a, hentaiOS Wiki (https://wiki.newcentrix.helluvaos.com) was down:

HTTP code: 403
Response time: 669 ms

Resolved: hentaiOS Wiki is back up in b9f02f3.


text:
Add verb-noun command aliases

Signed-off-by: Andy Goldstein andy.goldstein@gmail.com

@skriss updated, ptal

LGTM.

authors: ncdc skriss

repo: heptio/ark


text:
Use a struct for GetStatus to be consistent

What this PR does / why we need it:
Increases consistency of our method signatures for the interface.
Which issue(s) this PR fixes
Fixes #337
Special notes for your reviewer:
Release note:
The GetStatus method on the pkg/Interface (and SonobuoyClient type) will now take a struct which wraps the namespaces to increase in consistency and future extensibility.

Small PR to just get the item off of our backlog. Merging.

repo: heptio/sonobuoy


text:
重启出现问题

enforcer, err := casbin.NewEnforcer(path, false)
assignment mismatch: 2 variables but casbin.NewEnforcer returns 1 values
请问如何解决

你看看是不是修改了 casbin相关的文件


text:
HARP-11233: Store the clipping states in the ring vertices

This change modifies clipPolygon to store the state of the clipping
in the vertices. Also, this change modifies the clipping planes
to ensure that vertices on the edge are not marked as "clipped".

@robertoraggi , reviewing, I just want to try something locally.

@robertoraggi , reviewing, I just want to try something locally.

authors: nzjony robertoraggi


text:
Make pci-ids optional

Depends on https://github.com/hermitcore/libhermit-rs/pull/419.
Closes https://github.com/hermitcore/rusty-hermit/pull/104.

bors r=stlankes

repo: hermitcore/rusty-hermit


text:
Did anyone get the Heroku Preview-Apps to run with the deployHeroku of sbt?

2018-07-05T15:00:44.844322+00:00 heroku[web.1]: Starting process with command `target/universal/stage/bin/myapp -Dhttp.port=${PORT} -DTT_BOOTSTRAP_MODULE=WebModule -Dconfig.resource=${CONF} -J-javaagent:target/universal/stage/lib/com.newrelic.agent.java.newrelic-agent-3.46.0.jar -J-Dnewrelic.config.file=target/universal/stage/conf/newrelic.yml -Dnewrelic.environment=${NEW_RELIC_ENV}`
2018-07-05T15:00:46.764685+00:00 heroku[web.1]: Process exited with status 127
2018-07-05T15:00:46.777562+00:00 heroku[web.1]: State changed from starting to crashed
2018-07-05T15:00:46.779611+00:00 heroku[web.1]: State changed from crashed to starting
2018-07-05T15:00:46.707622+00:00 app[web.1]: Setting JAVA_TOOL_OPTIONS defaults based on dyno size. Custom settings will override them.
2018-07-05T15:00:46.707743+00:00 app[web.1]: bash: target/universal/stage/bin/myapp: No such file or directory

Help absolutely appreciated :-)

Is myapp the name of your project? I think sbt will generate the target/universal/stage/bin/ scripts with whatever name is in your build.sbt, like:
name := """myapp"""

I have this:
name := "MyApp"
could it be upper/lowercase?

@olmaga i don't know. can you try it lowercase. Also, run sbt stage and list the contents of the target/universal/stage/bin/ to see what the actual file name is.

Oh, Preview Apps probably won't work when using sbt-heroku because the deployment mechanism is quite different. With sbt-heroku, you are deploying pre-compiled artifacts. But Preview Apps pull down your source code and run the Scala buildpack. You can definitely make these work together, but you'll need to ensure your app works with git push heroku master too.

Thx for explaining. We'll go towards this direction then!

authors: jkutner olmaga

repo: heroku/sbt-heroku


text:
🛑 Software Center - Test 1 is down

In 84fe5e3, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in ed405e9.

repo: herrphon/upptime


text:
🛑 Software Center - Test 1 is down

In a6e3f46, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in d5a516c.


text:
🛑 Auth-Bridge - Test 1 is down

In 839133a, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in b9b50ab.


text:
🛑 Software Center - Test 1 is down

In c200803, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 3408c6f.


text:
🛑 Software Center - Test 1 is down

In 28de19d, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 7373e63.


text:
🛑 Auth-Bridge - Test 1 is down

In 210959d, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in 06bb4ed.


text:
🛑 Software Center - Test 1 is down

In 205f733, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 456f62a.


text:
🛑 Software Center - Test 1 is down

In 22c43f7, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in a71adc9 after 45 minutes.


text:
🛑 Auth-Bridge - Test 1 is down

In 7986bbd, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in ad8e307 after 16 minutes.


text:
🛑 Software Center - Test 1 is down

In 717a94b, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 4c7a3e7.


text:
🛑 Auth-Bridge - Test 1 is down

In 54993e5, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in c7d2a64 after 10 minutes.


text:
🛑 Software Center - Test 1 is down

In 8935aaf, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 8b658b4 after 1 hour, 3 minutes.


text:
🛑 Software Center - Test 1 is down

In 4f85dfd, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in af5d6fa after 10 minutes.


text:
🛑 Auth-Bridge - Test 1 is down

In 028f874, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in 7fb6a3e after 23 minutes.


text:
🛑 Software Center - Test 1 is down

In 61dce66, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 766a5f6 after 12 minutes.


text:
🛑 Software Center - Test 1 is down

In 7b2e51a, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 5488b22 after 20 minutes.


text:
🛑 Software Center - Test 1 is down

In 7a14731, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 40c29e9.


text:
🛑 Software Center - Test 1 is down

In e751e2f, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in fc5f1ff after 19 minutes.


text:
🛑 Software Center - Test 1 is down

In 26f6cd3, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 2c929a9.


text:
🛑 Software Center - Test 1 is down

In 4e5f930, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 3f96ebd after 21 minutes.


text:
🛑 Auth-Bridge - Test 1 is down

In 03733dd, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in c9d77ca.


text:
🛑 Auth-Bridge - Test 1 is down

In 4fad621, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in d3ffbfc.


text:
🛑 Software Center - Test 1 is down

In a9c359d, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 0db049b.


text:
The jak2stat5 example fails with mrgsolve

I took the model at https://github.com/hetalang/qsp-benchmark/tree/master/jak2stat5/src, compiled it and tried to run it with mrgsolve. Unfortunately, I get an error.
I was able to run the simple example model from readme via mrgsolve, so it presumably isn't just an installation issue.
The error I get is:
> nameless_model <- mrgsolve::mread(model = 'nameless', file = 'model.cpp')
Building nameless ... error.

---:: stderr ::---------------------------------------------
In file included from nameless-mread-source.cpp:3:
nameless-mread-header.h:25:10: error: expected unqualified-id before 'default'
   double default;
          ^~~~~~~

7:1: error: case label not within a switch statement
 default = 1.0;
 ^~~~~~~
7:8: error: expected ':' before '=' token
 default = 1.0;
        ^~
        :
7:9: error: expected primary-expression before '=' token
 default = 1.0;
         ^

14:37: error: expected primary-expression before 'default'
 EpoRJAK2_amt__0 = (init_EpoRJAK2) * default;
                                     ^~~~~~~
15:24: error: expected primary-expression before 'default'
 SOCS3_amt__0 = (0.0) * default;
                        ^~~~~~~
16:28: error: expected primary-expression before 'default'
 EpoRpJAK2_amt__0 = (0.0) * default;
                            ^~~~~~~
17:26: error: expected primary-expression before 'default'
 SHP1Act_amt__0 = (0.0) * default;
                          ^~~~~~~
18:31: error: expected primary-expression before 'default'
 EpoRJAK2_CIS_amt__0 = (0.0) * default;
                               ^~~~~~~
19:30: error: expected primary-expression before 'default'
 p1EpoRpJAK2_amt__0 = (0.0) * default;
                              ^~~~~~~
20:30: error: expected primary-expression before 'default'
 p2EpoRpJAK2_amt__0 = (0.0) * default;
                              ^~~~~~~
21:31: error: expected primary-expression before 'default'
 p12EpoRpJAK2_amt__0 = (0.0) * default;
                               ^~~~~~~
22:29: error: expected primary-expression before 'default'
 SHP1_amt__0 = (init_SHP1) * default;
                             ^~~~~~~
24:22: error: expected primary-expression before 'default'
 CIS_amt__0 = (0.0) * default;
                      ^~~~~~~
In file included from nameless-mread-source.cpp:3:

nameless-mread-header.h:89:35: error: expected primary-expression before 'default'
 #define EpoRJAK2 (EpoRJAK2_amt_ / default)
                                   ^~~~~~~
44:13: note: in expansion of macro 'EpoRJAK2'
 v1 = (Epo * EpoRJAK2 * JAK2ActEpo) / (SOCS3 * (SOCS3Inh / SOCS3Eqc) + 1.0);
             ^~~~~~~~
nameless-mread-header.h:89:35: error: expected ')' before 'default'
 #define EpoRJAK2 (EpoRJAK2_amt_ / default)
                  ~                ^~~~~~~
44:13: note: in expansion of macro 'EpoRJAK2'
 v1 = (Epo * EpoRJAK2 * JAK2ActEpo) / (SOCS3 * (SOCS3Inh / SOCS3Eqc) + 1.0);
             ^~~~~~~~
44:75: error: expected ')' before ';' token
 v1 = (Epo * EpoRJAK2 * JAK2ActEpo) / (SOCS3 * (SOCS3Inh / SOCS3Eqc) + 1.0);
      ~                                                                    ^
                                                                           )
In file included from nameless-mread-source.cpp:3:
nameless-mread-header.h:90:37: error: expected primary-expression before 'default'
 #define EpoRpJAK2 (EpoRpJAK2_amt_ / default)
                                     ^~~~~~~
45:6: note: in expansion of macro 'EpoRpJAK2'
 v2 = EpoRpJAK2 * (JAK2EpoRDeaSHP1 / init_SHP1) * SHP1Act;
      ^~~~~~~~~
nameless-mread-header.h:90:37: error: expected ')' before 'default'
 #define EpoRpJAK2 (EpoRpJAK2_amt_ / default)
                   ~                 ^~~~~~~
45:6: note: in expansion of macro 'EpoRpJAK2'
 v2 = EpoRpJAK2 * (JAK2EpoRDeaSHP1 / init_SHP1) * SHP1Act;
      ^~~~~~~~~
nameless-mread-header.h:90:37: error: expected primary-expression before 'default'
 #define EpoRpJAK2 (EpoRpJAK2_amt_ / default)
                                     ^~~~~~~
46:7: note: in expansion of macro 'EpoRpJAK2'
 v3 = (EpoRpJAK2 * EpoRActJAK2) / (SOCS3 * (SOCS3Inh / SOCS3Eqc) + 1.0);
       ^~~~~~~~~
nameless-mread-header.h:90:37: error: expected ')' before 'default'
 #define EpoRpJAK2 (EpoRpJAK2_amt_ / default)
                   ~                 ^~~~~~~
46:7: note: in expansion of macro 'EpoRpJAK2'
 v3 = (EpoRpJAK2 * EpoRActJAK2) / (SOCS3 * (SOCS3Inh / SOCS3Eqc) + 1.0);
       ^~~~~~~~~
46:71: error: expected ')' before ';' token
 v3 = (EpoRpJAK2 * EpoRActJAK2) / (SOCS3 * (SOCS3Inh / SOCS3Eqc) + 1.0);
      ~                                                                ^
                                                                       )
In file included from nameless-mread-source.cpp:3:
nameless-mread-header.h:90:37: error: expected primary-expression before 'default'
 #define EpoRpJAK2 (EpoRpJAK2_amt_ / default)
                                     ^~~~~~~
47:13: note: in expansion of macro 'EpoRpJAK2'
 v4 = (3.0 * EpoRpJAK2 * EpoRActJAK2) / ((EpoRCISInh * EpoRJAK2_CIS + 1.0) * (SOCS3 * (SOCS3Inh / SOCS3Eqc) + 1.0));
             ^~~~~~~~~
nameless-mread-header.h:90:37: error: expected ')' before 'default'
 #define EpoRpJAK2 (EpoRpJAK2_amt_ / default)
                   ~                 ^~~~~~~
47:13: note: in expansion of macro 'EpoRpJAK2'
 v4 = (3.0 * EpoRpJAK2 * EpoRActJAK2) / ((EpoRCISInh * EpoRJAK2_CIS + 1.0) * (SOCS3 * (SOCS3Inh / SOCS3Eqc) + 1.0));
             ^~~~~~~~~
47:115: error: expected ')' before ';' token
 v4 = (3.0 * EpoRpJAK2 * EpoRActJAK2) / ((EpoRCISInh * EpoRJAK2_CIS + 1.0) * (SOCS3 * (SOCS3Inh / SOCS3Eqc) + 1.0));
      ~                                                                                ^
                                                                                )
In file included from nameless-mread-source.cpp:3:
nameless-mread-header.h:91:41: error: expected primary-expression before 'default'
 #define p1EpoRpJAK2 (p1EpoRpJAK2_amt_ / default)
                                         ^~~~~~~
48:27: note: in expansion of macro 'p1EpoRpJAK2'
 v5 = (3.0 * EpoRActJAK2 * p1EpoRpJAK2) / ((EpoRCISInh * EpoRJAK2_CIS + 1.0) * (SOCS3 * (SOCS3Inh / SOCS3Eqc) + 1.0));
                           ^~~~~~~~~~~
nameless-mread-header.h:91:41: error: expected ')' before 'default'
 #define p1EpoRpJAK2 (p1EpoRpJAK2_amt_ / default)
                     ~                   ^~~~~~~
48:27: note: in expansion of macro 'p1EpoRpJAK2'
 v5 = (3.0 * EpoRActJAK2 * p1EpoRpJAK2) / ((EpoRCISInh * EpoRJAK2_CIS + 1.0) * (SOCS3 * (SOCS3Inh / SOCS3Eqc) + 1.0));
                           ^~~~~~~~~~~
48:117: error: expected ')' before ';' token
 v5 = (3.0 * EpoRActJAK2 * p1EpoRpJAK2) / ((EpoRCISInh * EpoRJAK2_CIS + 1.0) * (SOCS3 * (SOCS3Inh / SOCS3Eqc) + 1.0));
      ~                                                                                ^
                                                                                )
In file included from nameless-mread-source.cpp:3:
nameless-mread-header.h:92:41: error: expected primary-expression before 'default'
 #define p2EpoRpJAK2 (p2EpoRpJAK2_amt_ / default)
                                         ^~~~~~~
49:21: note: in expansion of macro 'p2EpoRpJAK2'
 v6 = (EpoRActJAK2 * p2EpoRpJAK2) / (SOCS3 * (SOCS3Inh / SOCS3Eqc) + 1.0);
                     ^~~~~~~~~~~
nameless-mread-header.h:92:41: error: expected ')' before 'default'
 #define p2EpoRpJAK2 (p2EpoRpJAK2_amt_ / default)
                     ~                   ^~~~~~~
49:21: note: in expansion of macro 'p2EpoRpJAK2'
 v6 = (EpoRActJAK2 * p2EpoRpJAK2) / (SOCS3 * (SOCS3Inh / SOCS3Eqc) + 1.0);
                     ^~~~~~~~~~~
49:73: error: expected ')' before ';' token
 v6 = (EpoRActJAK2 * p2EpoRpJAK2) / (SOCS3 * (SOCS3Inh / SOCS3Eqc) + 1.0);
      ~                                                                  ^
                                                                         )
In file included from nameless-mread-source.cpp:3:
nameless-mread-header.h:96:33: error: expected primary-expression before 'default'
 #define SHP1Act (SHP1Act_amt_ / default)
                                 ^~~~~~~
50:38: note: in expansion of macro 'SHP1Act'
 v7 = (JAK2EpoRDeaSHP1 / init_SHP1) * SHP1Act * p1EpoRpJAK2;
                                      ^~~~~~~
nameless-mread-header.h:96:33: error: expected ')' before 'default'
 #define SHP1Act (SHP1Act_amt_ / default)
                 ~               ^~~~~~~
50:38: note: in expansion of macro 'SHP1Act'
 v7 = (JAK2EpoRDeaSHP1 / init_SHP1) * SHP1Act * p1EpoRpJAK2;
                                      ^~~~~~~
nameless-mread-header.h:96:33: error: expected primary-expression before 'default'
 #define SHP1Act (SHP1Act_amt_ / default)
                                 ^~~~~~~
51:38: note: in expansion of macro 'SHP1Act'
 v8 = (JAK2EpoRDeaSHP1 / init_SHP1) * SHP1Act * p2EpoRpJAK2;
                                      ^~~~~~~
nameless-mread-header.h:96:33: error: expected ')' before 'default'
 #define SHP1Act (SHP1Act_amt_ / default)
                 ~               ^~~~~~~
51:38: note: in expansion of macro 'SHP1Act'
 v8 = (JAK2EpoRDeaSHP1 / init_SHP1) * SHP1Act * p2EpoRpJAK2;
                                      ^~~~~~~
nameless-mread-header.h:96:33: error: expected primary-expression before 'default'
 #define SHP1Act (SHP1Act_amt_ / default)
                                 ^~~~~~~
52:38: note: in expansion of macro 'SHP1Act'
 v9 = (JAK2EpoRDeaSHP1 / init_SHP1) * SHP1Act * p12EpoRpJAK2;
                                      ^~~~~~~
nameless-mread-header.h:96:33: error: expected ')' before 'default'
 #define SHP1Act (SHP1Act_amt_ / default)
                 ~               ^~~~~~~
52:38: note: in expansion of macro 'SHP1Act'
 v9 = (JAK2EpoRDeaSHP1 / init_SHP1) * SHP1Act * p12EpoRpJAK2;
                                      ^~~~~~~
nameless-mread-header.h:94:43: error: expected primary-expression before 'default'
 #define EpoRJAK2_CIS (EpoRJAK2_CIS_amt_ / default)
                                           ^~~~~~~
53:7: note: in expansion of macro 'EpoRJAK2_CIS'
 v10 = EpoRJAK2_CIS * (EpoRCISRemove / init_EpoRJAK2) * (p12EpoRpJAK2 + p1EpoRpJAK2);
       ^~~~~~~~~~~~
nameless-mread-header.h:94:43: error: expected ')' before 'default'
 #define EpoRJAK2_CIS (EpoRJAK2_CIS_amt_ / default)
                      ~                    ^~~~~~~
53:7: note: in expansion of macro 'EpoRJAK2_CIS'
 v10 = EpoRJAK2_CIS * (EpoRCISRemove / init_EpoRJAK2) * (p12EpoRpJAK2 + p1EpoRpJAK2);
       ^~~~~~~~~~~~
nameless-mread-header.h:95:27: error: expected primary-expression before 'default'
 #define SHP1 (SHP1_amt_ / default)
                           ^~~~~~~
54:7: note: in expansion of macro 'SHP1'
 v11 = SHP1 * (SHP1ActEpoR / init_EpoRJAK2) * (EpoRpJAK2 + p12EpoRpJAK2 + p1EpoRpJAK2 + p2EpoRpJAK2);
       ^~~~
nameless-mread-header.h:95:27: error: expected ')' before 'default'
 #define SHP1 (SHP1_amt_ / default)
              ~            ^~~~~~~
54:7: note: in expansion of macro 'SHP1'
 v11 = SHP1 * (SHP1ActEpoR / init_EpoRJAK2) * (EpoRpJAK2 + p12EpoRpJAK2 + p1EpoRpJAK2 + p2EpoRpJAK2);
       ^~~~
nameless-mread-header.h:96:33: error: expected primary-expression before 'default'
 #define SHP1Act (SHP1Act_amt_ / default)
                                 ^~~~~~~
55:17: note: in expansion of macro 'SHP1Act'
 v12 = SHP1Dea * SHP1Act;
                 ^~~~~~~
nameless-mread-header.h:96:33: error: expected ')' before 'default'
 #define SHP1Act (SHP1Act_amt_ / default)
                 ~               ^~~~~~~
55:17: note: in expansion of macro 'SHP1Act'
 v12 = SHP1Dea * SHP1Act;
                 ^~~~~~~
nameless-mread-header.h:90:37: error: expected primary-expression before 'default'
 #define EpoRpJAK2 (EpoRpJAK2_amt_ / default)
                                     ^~~~~~~
56:50: note: in expansion of macro 'EpoRpJAK2'
 v13 = (STAT5 * (STAT5ActJAK2 / init_EpoRJAK2) * (EpoRpJAK2 + p12EpoRpJAK2 + p1EpoRpJAK2 + p2EpoRpJAK2)) / (SOCS3 * (SOCS3Inh / SOCS3Eqc) + 1.0) * cyt;
                                                  ^~~~~~~~~
nameless-mread-header.h:90:37: error: expected ')' before 'default'
 #define EpoRpJAK2 (EpoRpJAK2_amt_ / default)
                   ~                 ^~~~~~~
56:50: note: in expansion of macro 'EpoRpJAK2'
 v13 = (STAT5 * (STAT5ActJAK2 / init_EpoRJAK2) * (EpoRpJAK2 + p12EpoRpJAK2 + p1EpoRpJAK2 + p2EpoRpJAK2)) / (SOCS3 * (SOCS3Inh / SOCS3Eqc) + 1.0) * cyt;
                                                  ^~~~~~~~~
56:150: error: expected ')' before ';' token
 v13 = (STAT5 * (STAT5ActJAK2 / init_EpoRJAK2) * (EpoRpJAK2 + p12EpoRpJAK2 + p1EpoRpJAK2 + p2EpoRpJAK2)) / (SOCS3 * (SOCS3Inh / SOCS3Eqc) + 1.0) * cyt;
                                                 ~                                                                                ^
                                                                                )
56:150: error: expected ')' before ';' token
 v13 = (STAT5 * (STAT5ActJAK2 / init_EpoRJAK2) * (EpoRpJAK2 + p12EpoRpJAK2 + p1EpoRpJAK2 + p2EpoRpJAK2)) / (SOCS3 * (SOCS3Inh / SOCS3Eqc) + 1.0) * cyt;
       ~                                                                                ^
                                                                                )
In file included from nameless-mread-source.cpp:3:
nameless-mread-header.h:93:43: error: expected primary-expression before 'default'
 #define p12EpoRpJAK2 (p12EpoRpJAK2_amt_ / default)
                                           ^~~~~~~
57:64: note: in expansion of macro 'p12EpoRpJAK2'
 v14 = (STAT5 * (STAT5ActEpoR / pow(init_EpoRJAK2, 2.0)) * pow((p12EpoRpJAK2 + p1EpoRpJAK2), 2.0)) / ((CIS * (CISInh / CISEqc) + 1.0) * (SOCS3 * (SOCS3Inh / SOCS3Eqc) + 1.0)) * cyt;
                                                                ^~~~~~~~~~~~
nameless-mread-header.h:93:43: error: expected ')' before 'default'
 #define p12EpoRpJAK2 (p12EpoRpJAK2_amt_ / default)
                      ~                    ^~~~~~~
57:64: note: in expansion of macro 'p12EpoRpJAK2'
 v14 = (STAT5 * (STAT5ActEpoR / pow(init_EpoRJAK2, 2.0)) * pow((p12EpoRpJAK2 + p1EpoRpJAK2), 2.0)) / ((CIS * (CISInh / CISEqc) + 1.0) * (SOCS3 * (SOCS3Inh / SOCS3Eqc) + 1.0)) * cyt;
                                                                ^~~~~~~~~~~~
57:180: error: expected ')' before ';' token
 v14 = (STAT5 * (STAT5ActEpoR / pow(init_EpoRJAK2, 2.0)) * pow((p12EpoRpJAK2 + p1EpoRpJAK2), 2.0)) / ((CIS * (CISInh / CISEqc) + 1.0) * (SOCS3 * (SOCS3Inh / SOCS3Eqc) + 1.0)) * cyt;
                                                               ~                                                                                ^
                                                                                )
57:180: error: expected ')' before ';' token
 v14 = (STAT5 * (STAT5ActEpoR / pow(init_EpoRJAK2, 2.0)) * pow((p12EpoRpJAK2 + p1EpoRpJAK2), 2.0)) / ((CIS * (CISInh / CISEqc) + 1.0) * (SOCS3 * (SOCS3Inh / SOCS3Eqc) + 1.0)) * cyt;
       ~                                                                                ^
                                                                                )
In file included from nameless-mread-source.cpp:3:
nameless-mread-header.h:106:25: error: expected primary-expression before 'default'
 #define CIS (CIS_amt_ / default)
                         ^~~~~~~
68:7: note: in expansion of macro 'CIS'
 v25 = CIS * CISTurn;
       ^~~
nameless-mread-header.h:106:25: error: expected ')' before 'default'
 #define CIS (CIS_amt_ / default)
             ~           ^~~~~~~
68:7: note: in expansion of macro 'CIS'
 v25 = CIS * CISTurn;
       ^~~
nameless-mread-header.h:113:29: error: expected primary-expression before 'default'
 #define SOCS3 (SOCS3_amt_ / default)
                             ^~~~~~~
78:7: note: in expansion of macro 'SOCS3'
 v35 = SOCS3 * SOCS3Turn;
       ^~~~~
nameless-mread-header.h:113:29: error: expected ')' before 'default'
 #define SOCS3 (SOCS3_amt_ / default)
               ~             ^~~~~~~
78:7: note: in expansion of macro 'SOCS3'
 v35 = SOCS3 * SOCS3Turn;
       ^~~~~
nameless-mread-header.h:90:37: error: expected primary-expression before 'default'
 #define EpoRpJAK2 (EpoRpJAK2_amt_ / default)
                                     ^~~~~~~
81:64: note: in expansion of macro 'EpoRpJAK2'
 pJAK2_au = log10(offset_pJAK2_long + 2.0 * scale_pJAK2_long * (EpoRpJAK2 + p12EpoRpJAK2 + p1EpoRpJAK2 + p2EpoRpJAK2) / init_EpoRJAK2);
                                                                ^~~~~~~~~
nameless-mread-header.h:90:37: error: expected ')' before 'default'
 #define EpoRpJAK2 (EpoRpJAK2_amt_ / default)
                   ~                 ^~~~~~~
81:64: note: in expansion of macro 'EpoRpJAK2'
 pJAK2_au = log10(offset_pJAK2_long + 2.0 * scale_pJAK2_long * (EpoRpJAK2 + p12EpoRpJAK2 + p1EpoRpJAK2 + p2EpoRpJAK2) / init_EpoRJAK2);
                                                                ^~~~~~~~~
81:134: error: expected ')' before ';' token
 pJAK2_au = log10(offset_pJAK2_long + 2.0 * scale_pJAK2_long * (EpoRpJAK2 + p12EpoRpJAK2 + p1EpoRpJAK2 + p2EpoRpJAK2) / init_EpoRJAK2);
                                                               ~                                                                      ^
                                                                                )
In file included from nameless-mread-source.cpp:3:
nameless-mread-header.h:93:43: error: expected primary-expression before 'default'
 #define p12EpoRpJAK2 (p12EpoRpJAK2_amt_ / default)
                                           ^~~~~~~
82:65: note: in expansion of macro 'p12EpoRpJAK2'
 pEpoR_au = log10(offset_pEpoR_long + 16.0 * scale_pEpoR_long * (p12EpoRpJAK2 + p1EpoRpJAK2 + p2EpoRpJAK2) / init_EpoRJAK2);
                                                                 ^~~~~~~~~~~~
nameless-mread-header.h:93:43: error: expected ')' before 'default'
 #define p12EpoRpJAK2 (p12EpoRpJAK2_amt_ / default)
                      ~                    ^~~~~~~
82:65: note: in expansion of macro 'p12EpoRpJAK2'
 pEpoR_au = log10(offset_pEpoR_long + 16.0 * scale_pEpoR_long * (p12EpoRpJAK2 + p1EpoRpJAK2 + p2EpoRpJAK2) / init_EpoRJAK2);
                                                                 ^~~~~~~~~~~~
82:123: error: expected ')' before ';' token
 pEpoR_au = log10(offset_pEpoR_long + 16.0 * scale_pEpoR_long * (p12EpoRpJAK2 + p1EpoRpJAK2 + p2EpoRpJAK2) / init_EpoRJAK2);
                                                                ~                                                          ^
                                                                                )
In file included from nameless-mread-source.cpp:3:
nameless-mread-header.h:106:25: error: expected primary-expression before 'default'
 #define CIS (CIS_amt_ / default)
                         ^~~~~~~
83:34: note: in expansion of macro 'CIS'
 CIS_au = log10(offset_CIS_long + CIS * scale_CIS_long / CISEqc);
                                  ^~~
nameless-mread-header.h:106:25: error: expected ')' before 'default'
 #define CIS (CIS_amt_ / default)
             ~           ^~~~~~~
83:34: note: in expansion of macro 'CIS'
 CIS_au = log10(offset_CIS_long + CIS * scale_CIS_long / CISEqc);
                                  ^~~
nameless-mread-header.h:113:29: error: expected primary-expression before 'default'
 #define SOCS3 (SOCS3_amt_ / default)
                             ^~~~~~~
84:43: note: in expansion of macro 'SOCS3'
 SOCS3_au = log10(offset_SOCS3_long + fabs(SOCS3) * scale_SOCS3_long / SOCS3Eqc);
                                           ^~~~~
nameless-mread-header.h:113:29: error: expected ')' before 'default'
 #define SOCS3 (SOCS3_amt_ / default)
               ~             ^~~~~~~
84:43: note: in expansion of macro 'SOCS3'
 SOCS3_au = log10(offset_SOCS3_long + fabs(SOCS3) * scale_SOCS3_long / SOCS3Eqc);
                                           ^~~~~
nameless-mread-header.h:95:27: error: expected primary-expression before 'default'
 #define SHP1 (SHP1_amt_ / default)
                           ^~~~~~~
88:18: note: in expansion of macro 'SHP1'
 SHP1_abs = log10(SHP1 + SHP1Act);
                  ^~~~
nameless-mread-header.h:95:27: error: expected ')' before 'default'
 #define SHP1 (SHP1_amt_ / default)
              ~            ^~~~~~~
88:18: note: in expansion of macro 'SHP1'
 SHP1_abs = log10(SHP1 + SHP1Act);
                  ^~~~
nameless-mread-header.h:106:25: error: expected primary-expression before 'default'
 #define CIS (CIS_amt_ / default)
                         ^~~~~~~
89:22: note: in expansion of macro 'CIS'
 CIS_abs = log10(fabs(CIS));
                      ^~~
nameless-mread-header.h:106:25: error: expected ')' before 'default'
 #define CIS (CIS_amt_ / default)
             ~           ^~~~~~~
89:22: note: in expansion of macro 'CIS'
 CIS_abs = log10(fabs(CIS));
                      ^~~
nameless-mread-header.h:113:29: error: expected primary-expression before 'default'
 #define SOCS3 (SOCS3_amt_ / default)
                             ^~~~~~~
90:24: note: in expansion of macro 'SOCS3'
 SOCS3_abs = log10(fabs(SOCS3));
                        ^~~~~
nameless-mread-header.h:113:29: error: expected ')' before 'default'
 #define SOCS3 (SOCS3_amt_ / default)
               ~             ^~~~~~~
90:24: note: in expansion of macro 'SOCS3'
 SOCS3_abs = log10(fabs(SOCS3));
                        ^~~~~
nameless-mread-header.h:95:27: error: expected primary-expression before 'default'
 #define SHP1 (SHP1_amt_ / default)
                           ^~~~~~~
98:39: note: in expansion of macro 'SHP1'
 tSHP1_au = log10(scale_SHP1_shp1oe * (SHP1 + SHP1Act) / init_SHP1);
                                       ^~~~
nameless-mread-header.h:95:27: error: expected ')' before 'default'
 #define SHP1 (SHP1_amt_ / default)
              ~            ^~~~~~~
98:39: note: in expansion of macro 'SHP1'
 tSHP1_au = log10(scale_SHP1_shp1oe * (SHP1 + SHP1Act) / init_SHP1);
                                       ^~~~
98:67: error: expected ')' before ';' token
 tSHP1_au = log10(scale_SHP1_shp1oe * (SHP1 + SHP1Act) / init_SHP1);
                                      ~                            ^
                                                                   )
In file included from nameless-mread-source.cpp:3:
nameless-mread-header.h:106:25: error: expected primary-expression before 'default'
 #define CIS (CIS_amt_ / default)
                         ^~~~~~~
99:17: note: in expansion of macro 'CIS'
 CIS_au1 = log10(CIS * scale1_CIS_dr90 / CISEqc);
                 ^~~
nameless-mread-header.h:106:25: error: expected ')' before 'default'
 #define CIS (CIS_amt_ / default)
             ~           ^~~~~~~
99:17: note: in expansion of macro 'CIS'
 CIS_au1 = log10(CIS * scale1_CIS_dr90 / CISEqc);
                 ^~~
nameless-mread-header.h:106:25: error: expected primary-expression before 'default'
 #define CIS (CIS_amt_ / default)
                         ^~~~~~~
100:17: note: in expansion of macro 'CIS'
 CIS_au2 = log10(CIS * scale2_CIS_dr90 / CISEqc);
                 ^~~
nameless-mread-header.h:106:25: error: expected ')' before 'default'
 #define CIS (CIS_amt_ / default)
             ~           ^~~~~~~
100:17: note: in expansion of macro 'CIS'
 CIS_au2 = log10(CIS * scale2_CIS_dr90 / CISEqc);
                 ^~~
make: *** [C:/PROGRA~1/R/R-41~1.0/etc/x64/Makeconf:245: nameless-mread-source.o] Error 1
------------------------------------------------------------
Error: the model build step failed.

Hi @martinmodrak ,
Thank you for your feedback. I have the same issue.
The model included a compartment with "default" id.
This is a reserved word in mrgsolve, as I understand.
I've updated the repository with jak2stat5 model changing "default" => "def".
Now everything is fine. Compilation and simulations are OK.
Pull the latest commit from hetalang/qsp-benchmark and recompile the model.
This is a workaround. But the unexpected issues with reserved words are still a problem.
We need a better solution.

Wouldn't a systematic solution be that the XXExport classes expose a list of keywords and the compiler checks the model against this list. It could then either:

Raise an error/warning when an id conflicts with the keywords, or
Automatically rename all ids to avoid the conflict (e.g. by adding underscorses or something)

(I don't insist on this being done for the review, it just seems like a relatively cheap but useful solution)

@martinmodrak, agree, this would be good.
As a fast temporal solution, I've added "default" into a general keyword list.
Now the usage of such id throws an error. A user should change the id of such a component by himself.
But I still doubt if it's the best solution.

It seems that each "export" type should have its own stop list. We need time to collect and analyze them all.
We should also think of automatic renaming rules.

So I guess we suggest a better solution later.

authors: martinmodrak metelkin

repo: hetalang/heta-compiler


text:
fix-typo

fix a typo in README file

done


text:
Error: Could not resolve './fi/hg/core/RequestServer'

[!] Error: Could not resolve './fi/hg/core/RequestServer' from src/main.ts
Error: Could not resolve './fi/hg/core/RequestServer' from src/main.ts
    at error (/Users/jhh/tmp/foo-backend/node_modules/rollup/dist/shared/rollup.js:198:30)
    at ModuleLoader.handleResolveId (/Users/jhh/tmp/foo-backend/node_modules/rollup/dist/shared/rollup.js:22287:24)
    at /Users/jhh/tmp/foo-backend/node_modules/rollup/dist/shared/rollup.js:22250:26

Root cause for this problem is that we've moved some node specific code to fi.hg.node . I will add it there and fix imports.

repo: heusalagroup/create-backend


text:
PHP Warning: "resource" is not a supported builtin type and will be interpreted as a class name.

PHP Warning:  "resource" is not a supported builtin type and will be interpreted as a class name. Write "\hexydec\css\resource" or import the class with "use" to suppress this warning in /var/www/html/vendor/hexydec/cssdoc/src/cssdoc/cssdoc.php on line 84
Looks like PHP 8 does not support resource anymore. Change to mixed can fix.

44a193e might fixed this but you need update at https://github.com/hexydec/htmldoc too.

Made a PR #5

Not sure, but I think you need create a new tag to update at htmldoc.

I have updated the dependencies in HTMLDoc and released a new version, plese update to 1.2.1.

authors: hexydec insign

repo: hexydec/cssdoc


text:
Failed windows 10 pro x64

Turla Driver Loader v1.1.4 started
(c) 2016 - 2019 TDL Project
Supported x64 OS : 7 and above
Ldr: Windows v10.0 build 17763
SCM: Vulnerable driver load failure
I did everything right and I get this, I have already checked all the driver and have no running to lock it.

Likely it is your environment caused.

18 days no reply, closed.

I am having the same issue

So with the new windows 10 we can't use this anymore? I am still on windows 7 but dreading the future :(

If you expected this to work forever it is obviosly your problem.

authors: DonoDayZ MeisterJaan hfiref0x quetzalsly


text:
Auto-generating the kernel.json file breaks starting the kernel

The https://github.com/hhu-stups/prolog-jupyter-kernel/commit/ad3f209a6ca478c635d3a048bcfa93280933fe4e change breaks the Prolog kernel for me. Same when I back-ported it to the Logtalk kernel. I get:
/opt/local/bin/python3.10: No module named prolog_kernel
[I 2022-12-02 15:27:23.886 ServerApp] AsyncIOLoopKernelRestarter: restarting kernel (1/5), new random ports
/opt/local/bin/python3.10: No module named prolog_kernel
[I 2022-12-02 15:27:26.903 ServerApp] AsyncIOLoopKernelRestarter: restarting kernel (2/5), new random ports
/opt/local/bin/python3.10: No module named prolog_kernel
[I 2022-12-02 15:27:29.921 ServerApp] AsyncIOLoopKernelRestarter: restarting kernel (3/5), new random ports
/opt/local/bin/python3.10: No module named prolog_kernel
[I 2022-12-02 15:27:32.938 ServerApp] AsyncIOLoopKernelRestarter: restarting kernel (4/5), new random ports
/opt/local/bin/python3.10: No module named prolog_kernel
[I 2022-12-02 15:27:35.955 ServerApp] AsyncIOLoopKernelRestarter: restarting kernel (5/5), new random ports
/opt/local/bin/python3.10: No module named prolog_kernel
...

This after uninstalling the previous version of the kernel and installing the new one:
$ pip3 uninstall prolog_kernel
$ pip3 install -e .
$ python3 -m prolog_kernel.install

I'm running:

macOS 12.6.1
Python 3.10.8
jupyter_core 4.10.0
jupyterlab 3.5.0
notebook  6.4.8

My guess would be that you have mismatched Python installations in your PATH, i. e. the pip3 command comes from a different Python installation than the python3 command. It's recommended to always use python3 -m pip (change the python3 part as needed) so that you know for sure that pip is operating on the Python installation that you expect.
So in this case I'd recommend:
$ pip3 uninstall prolog_kernel
$ pip3 uninstall prolog_kernel
$ python3 -m pip uninstall prolog_kernel
$ python3 -m pip uninstall prolog_kernel
$ python3 -m pip install -e .
$ python3 -m prolog_kernel.install

Sometimes you need to run pip uninstall more than once, if you have the package installed in multiple locations used by the same Python environment (e. g. user-local and system-wide).

Thanks for the quick reply. That sequence of shell commands solved the problem for both kernels (although, interestingly, only a single installation for each kernel was found by the uninstall commands).

I also just pushed a few changes for better feedback when installing the kernel (5b2f5af) and a better default install location (2ac5ace). These should help with debugging the issue.

Thanks. I applied those changes to the Logtalk kernel (https://github.com/LogtalkDotOrg/logtalk-jupyter-kernel/commit/1c968deabaace9d15c8a2ed1b7c6f17915d2c52d).

authors: dgelessus pmoura

repo: hhu-stups/prolog-jupyter-kernel


text:
[ bug ]V1.7.0 实例管理-会话管理页面导出的会话列表SQL语句不完整

重现步骤

期待结果和实际结果
期待结果：
SQL语句完整
实际结果:
SQL语句不完整
截图

版本信息
应用版本/分支：1.7.0
部署方式：Docker

@hhyo 大神，这个BUG已经修复了吗？

对，可以查看fix的commit记录，导出时先选择显示完整INFO

多谢大神，辛苦了！
发自我的iPhone
------------------ 原始邮件 ------------------
发件人: 小圈圈 <notifications@github.com>
发送时间: 2019年10月20日 10:16
收件人: hhyo/Archery <Archery@noreply.github.com>
抄送: yuandajn578 <12173670@qq.com>, Author <author@noreply.github.com>
主题: 回复：[hhyo/Archery] [ bug ]V1.7.0 实例管理-会话管理页面导出的会话列表SQL语句不完整 (#479)

repo: hhyo/Archery


text:
[ 功能建议 ] 能否在归档功能上根据不同工单配置不同归档时间

目前遇到的问题/使用障碍
由于业务需求，需要在不同的时间点进行归档，目前归档只能统一配置一个时间调用，使用不友好
希望如何解决/实现它
在申请归档页面提供归档时间选项，针对每个工单提供归档时间选择。
其他信息
如果有其他类似的产品功能或者图片信息，可在此提交

两种实现方案

每个归档任务配置一个schedule
原有schedule支持传入配置id，可以此建多个schedule调度

欢迎感兴趣的同学提交PR

authors: falcondance hhyo


text:
Add PluckConfig

Add Config for adding customizations to the project like supporting tabs to select single/multiple images.
Eg. Single + Multiple Image Selection.

Fixed in the new release

repo: hi-manshu/Pluck


text:
Investigate how to use an EBS disk and if we need it

At the moment we have started an image that create an EBS disk where we save the jenkins workspace (this part is not scripted).
The EBS disk is created new everytime a machine is started but what we need is to use an image that doesn't create an EBS disk and attach one that already exists.
Maybe we don't need an EBS disk at all if we use a different image.
We need to investagat possible solution and update the script to apply them

outdated: moved to use Ansible now, and tracking issues on JIRA.

authors: DavideD Sanne


text:
HHH-11071 : Add UtcTimestampType

This is the pull request with the patch to add a new type that can be used in place of TimestampType by an explicit @org.hibernate.annotations.Type( type = "org.hibernate.type.UtcTimestampType" ) annotation (so existing behaviour is not affected by merging this patch). The new type explicitly uses the UTC timezone instead of the (system/JVM/…) default one when no explicit time zone is given, and is unchanged otherwise — in fact, the type descriptor class is generated by running sed(1) on the TimestampTypeDescriptor class, and the UtcTimestampType class itself is a trivial subclass of TimestampType merely changing the SQL descriptor after calling its parent’s constructor.
From a Hibernate user’s point of view, this functionality is required to be able to reliably store and retrieve data from/to SQL “TIMESTAMP WITHOUT TIME ZONE” fields; it may also positively affect “TIMESTAMP WITH TIME ZONE”, although I personally have only tested¹ the former. The only alternative to this is to store timestamps as SQL “BIGINT”, which is semantically wrong.
This ability appears to be a frequently asked-for thing (according to a WWW and StackOverflow research), and many people are willing to use a Hibernate-specific feature (with all the portability problems this involves) just to get it.
As for the patch itself, feedback is welcome; while I program since 1988, Java™ is new to me.
① “Tested” here means, added the equivalent of these classes in an internal project in that project’s namespace, added all those @Type annotations, and watched happily as the service finally gave out correct data. Also, ran “bash gradlew hibernate-core:test”. I did not test with the patched Hibernate build in the internal project, as the latter is still using version 5.1.0.Final (any chance getting this accepted into the 5.1 branch for an eventual 5.1.1 release, by the way?). We don’t wish to carry this in our application forever, due to the maintenance cost (as the descriptor has to be copied from Hibernate’s core code in each version), and because my employer ⮡ tarent is an Open Source company, and because this way we finally have an official type everyone can use instead of creating their own (or, worse, manipulating the JVM timezone, in those cases that helps).

https://hibernate.atlassian.net/browse/HHH-11071

Instead of adding a new type, I think we should consider adding parameterized support for the default Timestamp descriptor. But even then, we'd have to specify the timezone for every type mapping. Most of the time, we want to store timestamps with the same timezone in the DB, instead of mixing different timestamp types, right? For this reason, maybe we need a configuration property as the default timezone.

I think we will address this issue along with a fix for HHH-10399

authors: mirabilos vladmihalcea

repo: hibernate/hibernate-orm


text:
HHH-9641 Publish JavaDoc JARs

HHH-9641 is an old ticket and isn't assigned to anyone, but the required changes didn't seem too hard so I gave it a shot. I tested my changes with a ./gradlew clean assemble publishToMavenLocal (which, before my changes only created the binary and source JARs). I'd be glad to do any more required testing and make any other changes necessary.

Looks good. I wonder if there is anything we should change.

I started a discussion on the mailing list and will attach it here. Basically, this was intended and that's why we have aggregated Java Docs.
However, since this is already tested and it works, we might integrate this change as well. I'm waiting to see if there's anyone against it.

If you can resolve the conflicts I will integrate this next week.

I hope to do 5.3.0.Beta1 this week.  No rush, but if you want it in there...

I've updated the branch based on the latest in the upstream master.
I just realized something that should really have been obvious when I made the changes: the same all-encompassing JavaDoc JAR is being created for each of the sub-projects. Although this serves the need for a JavaDoc JAR, it seems wrong to include JavaDoc for classes that are not part of a given artifact and it seems wrong to publish such a large JAR for each sub-project.
I could do one of the following:

decline the PR (since the team doesn't really use the JavaDoc JARs)
see what it takes to get a more correct JavaDoc JAR for each sub-project without upsetting the existing build and then update the PR

Let me know which option you'd prefer.

To publish module-specific JavaDoc jars, obviously those JavaDoc should be
module-specific :)
On Tue, Dec 19, 2017 at 9:30 AM george thomas notifications@github.com
wrote:

I've updated the branch based on the latest in the upstream master.
I just realized something that should really have been obvious when I made
the changes: the same all-encompassing JavaDoc JAR is being created for
each of the sub-projects. Although this serves the need for a JavaDoc JAR,
it seems wrong to include JavaDoc for classes that are not part of a
given artifact and it seems wrong to publish such a large JAR for each
sub-project.
I could do one of the following:

decline the PR (since the team doesn't really use the JavaDoc JARs)
see what it takes to get a more correct JavaDoc JAR for each
sub-project without upsetting the existing build and then update the PR

Let me know which option you'd prefer.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/hibernate/hibernate-orm/pull/2078#issuecomment-352792735,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOUE8QFIMNVYaEGJVCAQVejVCdq8xQIks5tB9aJgaJpZM4Q1rW_
.

Thanks for not choosing to decline it outright :) Let me see what I can do to get some module-specific JavaDoc JARs.

Have you checked the Gradle documentation?  Generating javadoc jar is pretty straight-forward.

@sebersole, my changes initially reused what the build in this project already does for JavaDoc. I do plan to use the standard javdoc task from Gradle (I'll likely duplicate some of the configuration from aggregateJavadocs in documentation/documentation.gradle). I just haven't been able to get back to this over the last few days :)

There really should not be much to do for this - I'm not sure what you want to "duplicate".
Anyway, as we are also looking to move to Bintray for publishing release artifacts and syncing to Central we will need to start publishing javadocs as well since Central requires it.  We had previously gotten around that, but we will no longer be able to.  So I'll likely just do this

The duplication should only be in the configuration for the JavaDoc.

I implemented this myself : https://github.com/hibernate/hibernate-orm/pull/2097

Cool, @sebersole. I was just about to push a working alternative.

authors: sebersole smoothreggae vladmihalcea


text:
Check compatibility with Vert.x 4.5

See https://vertx.io/blog/whats-new-in-vert-x-4-5/

The build on CI fails for JDK 22 because of this issue: https://github.com/eclipse-vertx/vertx-sql-client/issues/1379

repo: hibernate/hibernate-reactive


text:
HV-1536

https://hibernate.atlassian.net/browse/HV-1536

@gsmet Reworded the comment as per your request.

Amended and merged! Thanks.

authors: gsmet gunnarmorling

repo: hibernate/hibernate-validator


text:
BUG: cannot import mtw because of "from ot import"

(mtw-env) ➜  mtw git:(master) ✗ python
Python 3.7.1 | packaged by conda-forge | (default, Nov 13 2018, 18:33:04)
[GCC 7.3.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from mtw import MTW
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/mathurin/workspace/mtw/mtw/__init__.py", line 1, in <module>
    from .mtw import MTW
  File "/home/mathurin/workspace/mtw/mtw/mtw.py", line 2, in <module>
    from .solver import solver
  File "/home/mathurin/workspace/mtw/mtw/solver.py", line 10, in <module>
    from .otfunctions import (barycenterkl, barycenterkl_img, barycenterkl_log,
  File "/home/mathurin/workspace/mtw/mtw/otfunctions.py", line 6, in <module>
    from ot import emd2
ModuleNotFoundError: No module named 'ot'

@hichamjanati

What is ot supposed to be ?

That's the pot package https://pot.readthedocs.io/en/stable/
This dependency should be removed actually

authors: hichamjanati mathurinm

repo: hichamjanati/mtw


text:
🛑 Kiwi Farms Forum is down

In 443971f, Kiwi Farms Forum (https://kiwifarms.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Kiwi Farms Forum is back up in 80239a6 after 5 minutes.

repo: hickoryhouse/kf


text:
🛑 Mad at the Internet is down

In 6343de7, Mad at the Internet (https://madattheinternet.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Mad at the Internet is back up in 841e2d6 after 10 minutes.


text:
🛑 NGINX is down

In d80d899, NGINX (https://web.sshcdn.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NGINX is back up in 1b5a78d.