Support Helm charts from OCI registries

The language in the Helm docs about registries suggests that the plan is support using OCI (https://helm.sh/docs/topics/registries/). This feature still experimental in Helm, but it looks like the plan is to graduate it in a release soon: https://github.com/helm/helm/pull/7613, https://github.com/helm/community/pull/136.

Yes it would be a really great feature. OCI is the future for Helm chart, and Harbor already support replication to external registries like Azure Container Registry.

The OCIGetter was made available in Helm v3.5.0 but has not been extensively documented yet.

The OCIGetter was made available in Helm v3.5.0 but has not been extensively documented yet.

The OCIGetter was made available in Helm v3.5.0 but has not been extensively documented yet.
Update: no chances of integration yet, as the registry.Client required to pull it all off (🥁) is still in helm/internal.

Isn't it enough to just use OCIGetter which wraps the client you mention?

No, it is not as we do not have access to the RegistryClient that is injected using the options. We are therefore unable to construct the OCIGetter properly.

I have browsed for few days searching a solution to have my Charts stored in a private GitLab container registry (OCI compliant registry) and be finally able to pull those charts from the usual Helm command.
I have found the code from two small projects that looks appealing:

https://github.com/alauda/oci-chartrepo
https://github.com/hangyan/chart-registry

The goal is to build a classic Chart registry from the content of the OCI registry using the following endpoints:

/index.yaml     # Get the OCI data from --storage-registry-repo, then transform them into standard chart repository data structures.
/charts/:name   # Download a chart artifact

Do you think that such solution can be the good direction to avoid rewriting a specific module to handle OCI registries?

Is there any timeline available on when this might become available? We are also using Azure Container registry and MSFT is suggesting to use OCI3, which on the Helm side is considered experimental.
Now that we did the migration we also wanted to look into GitOps/Flux, however, its a major blocker now that I cannot pull the charts from the registry, as OCI3 is not supported.

See: https://github.com/helm/helm/issues/9188#issuecomment-811278873

@alxy It is also possible to push tar.gz files of Helm chart to an ACR. We currently push both the OCI and the tar.gz, for now we only use the tar.gz with Flux but when OCI is available when can just switch without the need to push all charts again.

@rchrd Thanks for the tip, we have also considered the hybrid approach, but it makes the build and deploy pipelines a lot more complex (as the helm commands to run are quite different). Will need to think about it... Especially since the deploy part is then potentially anyway handled by flux, it might be worth it.

I have browsed for few days searching a solution to have my Charts stored in a private GitLab container registry (OCI compliant registry) and be finally able to pull those charts from the usual Helm command.
I have found the code from two small projects that looks appealing:
* https://github.com/alauda/oci-chartrepo

* https://github.com/hangyan/chart-registry

The goal is to build a classic Chart registry from the content of the OCI registry using the following endpoints:
* **/index.yaml**     # Get the OCI data from --storage-registry-repo, then transform them into standard chart repository data structures.

* **/charts/:name**   # Download a chart artifact

Do you think that such solution can be the good direction to avoid rewriting a specific module to handle OCI registries?

@alxy Have you though about a proxy/mirror/endpoint that can translate your OCI registry in a classic Chart registry ?
Have a look at the projects in the quote, they can help you to think about a different solution

@Jimmy-Newtron I think in that case I'd rather use the approach that @rchrd suggested. At least the ACR (which is a managed cloud resource) supports both methods (in parallel), and I'd prefer that over setting up my custom repository and adding even more tooling to the already complex process and toolchain.

I'm using chartmuseum for now and pushing helm charts parallel to it to gcr.io.
Hopefully we can get rid of chartmuseum soon :)

It would be great if OCR registries are supported in FluxCD.

@hiddeco May I ask if this is a technical thing that this cannot be added to flux, or something political, as in you are not using features considered as experimental by Helm?
The reason I am asking is that I have found this PR for argo-cd which seems to implement exactly the functionality we are looking for here...

ArgoCD uses cmd.Exec under the hood, this controller integrates the go pkg helm.sh/helm/v3/pkg. As mentioned above, OCIGetter is partially internal and can not be constructed properly without internals.
We are also blocked by this (we in particular want to use AWS ECR). Would it be an option to copy the necessary parts from helms internal/  pkg? kustomize-controller does that too to support sops. I'm not saying that this is the best solution, but it has been quite some time and i would prefer the trade-off as it can be cleaned-up later.

Major changes in the OCI implementation in Helm 3.7.0:
https://github.com/helm/helm/releases/tag/v3.7.0

With all OCI related APIs still being internal, nothing has changed for us. But the fact that things are moving is promising :-).

With Helm 3.8.0 released and OCI being out of experimental, this is now ready to be worked on. It will require a bit of design tinkering to work well in combination with #450, @souleb is currently investigating our options, and is hoping to share more on this later in the week.

@hiddeco @souleb we're integrating with FluxCD Toolkit and OCI support is really important feature. I'm keen to help, please let me know if anything I can start with.

We are working on a design doc. Would be nice to have feedbacks.

@souleb @hiddeco I've left some comments on the design doc. Basically, my angle is from modeling the OCI Source CRD on Registry rather than Repository, which, I feel, makes it easier to reason that a single generic OCI source can produce different types of Artifact (of different config.mediaType), helm chart, kustomize bundle, etc.
By the way, I found hackmd not really friendly in terms of commenting, there's a maximum number of character for each comment that forced me to break my comments into chunks, and also I couldn't edit any comment once submitted.
Is it ok to migrate to a Google Doc or something?

apiVersion: source.toolkit.fluxcd.io/v1beta1
kind: OCIRegistry
metadata:
  name: my-local-registry
  namespace: flux-system
spec:
  interval: 10m
  url: localhost:5000
  auth:
    secretRef:
      name: regcred

apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  name: my-chart
spec:
  interval: 5m
  chart:
    spec:
      chart: my-chart
      version: '4.0.x'
      sourceRef:
        kind: OCIRegistry
        name: my-local-registry
        namespace: flux-system
      interval: 1m

helm-controller creates the following
apiVersion: source.toolkit.fluxcd.io/v1beta1
kind: OCIArtifact
metadata:
  name: my-chart
  namespace: flux-system
spec:
  baseName: my-chart
  #one of
  tag: '4.0.x'
  digest: "sha256:0be7ec9fb7b962b46d81e4bb74fdcdb7089d965d3baca9f85d64948b05b402ff"
  sourceRef:
    kind: OCIRegistry
    name: my-local-registry
  interval: 5m

source-controller use GET /v2/my-chart/tags/list Registry API to determine the desired tag, then it pulls the manifest via GET /v2/my-chart/manifests/<desired tag>, now we know the config.mediaType, from this point on, source-controller can have mediaType-specific handler to process the config and the binary blob layers (helm OCI getter from Helm project being one of them).
In the case of using OCI for kustomize bundle, if the bundle is pushed to the same registry, we don't need to define another instance of OCIRegistry, we can add a new field bundle to the kustomizationSpec:
apiVersion: kustomize.toolkit.fluxcd.io/v1beta2
kind: Kustomization
metadata:
  name: my-kustomization
spec:
  interval: 5m
  bundle:
    name: my-kustomization
    #oneof
    tag: "1.0.x"
    digest: "sha256:44136fa355b3678a1146ad16f7e8649e94fb4fc21fe77e8310c060f61caaff8a"
  path: "./deploy/webapp/"
  prune: true
  sourceRef:
    kind: OCIRegistry
    name: my-local-registry
    namespace: flux-system
  wait: true
  timeout: 2m

the kustomize-controller then create a very similar OCIArtifact:
apiVersion: source.toolkit.fluxcd.io/v1beta1
kind: OCIArtifact
metadata:
  name: my-kustomization
  namespace: flux-system
spec:
  baseName: my-kustomization
  #one of
  tag: '1.0.x'
  sourceRef:
    kind: OCIRegistry
    name: my-local-registry
  interval: 5m

@simingweng what about putting this in the alternative design section?

I'm not for introducing two types for Helm and Kustomize to source-controller API. I would very much prefer to reuse the OCIRepository type in both kustomize-controller and helm-controller APIs sourceRef. The  OCIRepository implementation is here: https://github.com/fluxcd/source-controller/pull/450

Isn't the OCIRegistry part a simple rename from OCIRepository -> OCIRegistry? Which might be a better name indeed.

Isn't the OCIRegistry part a simple rename from OCIRepository -> OCIRegistry? Which might be a better name indeed.

Not exactly. The difference is that an OCIRepository would point to a concrete repository like registry.gitlab.com/makkes/repo whereas the idea of a OCIRegistry is more generic.
With an OCIRepository you would have to create one such resource per Helm chart.
With an OCIRegistry you would create one resource for as many Helm charts or other actual resources you'd like to consume from the registry.
That's how I understand both suggestions. Please correct me if I'm wrong @souleb or  @simingweng.

@makkes yes, that's where I came from. The fundamental reason that makes me want to try model it at Registry level is that in current HelmRelease API, we offer HelmRelease.chart.version to filter desired versions of chart, and at the same time, in the suggested OCIRepository, it seems we also want to offer the same thing via ref or filterTag, etc.
Do we want to allocate this "version selection" semantics in a single resource, rather than overlap in both the "source" resource and the "consuming" resource? I know it sounds too much like a refactoring of existing API, which may not be the goal of this OCI support effort. Then, we just need to educate the user clearly which field takes priority when both the OCIRepositry and HelmRelease carries version selection intentions.

@simingweng what about putting this in the alternative design section?

Yes, I can.

@simingweng We have updated the doc. Please review it.

Any progress on this?

Hi flux firends! I am actively working to complete PR #450. I am updating the OCIRepository reconciler implementation to match the new standard used in other reconcilers within this project.
Additionally, I propose to add  "CertSecretRef" to OCIRepository spec as suggested in PR #450. The "CertSecretRef" will be optional and can have a name of a secret that contains certificate data. It will be used for connecting to the registry. I find this useful for registry that has certificates issued by a Private CA (non-public Cetificate Authorties)

@rashedkvm please hold off the implementation, we need to decide on how the API will look.
Everyone please add your feedback on the Flux OCI support for Helm, once the RFC is approved we can move forward with the implementation.

RFC-0002 is now marked as implementable, thanks everyone for your feedback. The implementation can be tracked in https://github.com/fluxcd/source-controller/issues/669


v1.9 backports 2021-01-06

#14388 -- test: Add missing gomega Eventually intervals (@jrajahalme)
#14021 -- helm: 'bpf.ctTcpMax' and 'bpf.ctAnyMax' need to be strings, not integers (@mvisonneau)
#14346 -- pkg/logging: Init klog with flag set name (@fafucoder)
#14412 -- test: Test policy enforcement through tunnels (@pchaigno)
#14413 -- helm: fix TLS cert server name for cluster names containing dots (@kaworu)
#14416 -- helm: fix TLS cert server name for cluster names containing dots with certgen (@kaworu)
#14420 -- test: Fix microk8s deployment hurdles (@joestringer)
#14434 -- docs: Update linux distribution compatibility (@joestringer)
#13888 -- docs: add info about tailcalls in bpf subprograms (@mfijalko)
#14449 -- install/kubernetes: set the right option for expectAzureVnet (@aanm)
#14447 -- bpf: Fix misaligned access in bpf_xdp with prefilter and IPv6 (@pchaigno)
#14464 -- test: Un-Quarantine K8sUpdates on GKE (@gandro)
#14241 -- Update policy-creation.rst (@gecube)
#14473 -- Fixing Hubble ServiceMonitor k8s-app label (@guilhermef)
#14271 -- Istio: Update to 1.6.14 (@jrajahalme)

Notes: Slight conflict inside test suite, where v1.9 tree has the Istio tests quarantined, and master seemingly doesn't. Kept it as quarantined.

#14508 -- Add missing requireIPv6PodCIDR setting (@NeilW)
#14513 -- vendor: Update vishvananda/netlink (@pchaigno)
#14517 -- docs: Add cgroups kernel config requirements (@joestringer)

Once this PR is merged, you can update the PR labels via:
$ for pr in 14388 14021 14346 14412 14413 14416 14420 14434 13888 14449 14447 14464 14241 14473 14271 14508 14513 14517; do contrib/backporting/set-labels.py $pr done 1.9; done

test-backport-1.9

test-backport-1.9

retest-gke

retest-gke

retest-gke

retest-gke

retest-gke

retest-gke

retest-gke

retest-gke

retest-gke

retest-gke

retest-gke

retest-gke

@gandro Looks like the GKE test is finally running, but it failed with the same error that Paul linked: https://jenkins.cilium.io/job/Cilium-PR-K8s-GKE/3906/testReport/Suite-k8s-1/16/K8sUpdates_Tests_upgrade_and_downgrade_from_a_Cilium_stable_image_to_master/

@gandro Looks like the GKE test is finally running, but it failed with the same error that Paul linked: https://jenkins.cilium.io/job/Cilium-PR-K8s-GKE/3906/testReport/Suite-k8s-1/16/K8sUpdates_Tests_upgrade_and_downgrade_from_a_Cilium_stable_image_to_master/

@gandro Looks like the GKE test is finally running, but it failed with the same error that Paul linked: https://jenkins.cilium.io/job/Cilium-PR-K8s-GKE/3906/testReport/Suite-k8s-1/16/K8sUpdates_Tests_upgrade_and_downgrade_from_a_Cilium_stable_image_to_master/

I guess this needs further investigation. Feel free to my commit from the PR to get this merged.

@gandro Looks like the GKE test is finally running, but it failed with the same error that Paul linked: https://jenkins.cilium.io/job/Cilium-PR-K8s-GKE/3906/testReport/Suite-k8s-1/16/K8sUpdates_Tests_upgrade_and_downgrade_from_a_Cilium_stable_image_to_master/

I guess this needs further investigation. Feel free to my commit from the PR to get this merged.

test-backport-1.9

test-backport-1.9


Description: Unexpected error - Crash on Launch

Not sure if it is related to the other issue, but here is my crash report.
@BunnyCinnamon
crash-2021-07-19_11.51.16-client.txt

I found the reason for my issue and fixed it.  I had an outdated mod.


Add spec for custom matchers and some extra chainables

Update RSpec matchers with extra chains and add some tests (but exclude rspec.rb)

Coverage remained the same at 100.0% when pulling 435df9dfeaa4698e408a3359621a9e04fc11c5f8 on feature/rspec-matchers into 791656e3888b2098830fcc880a9df62249a8b5f9 on breaking/v0.4.0.

@egreer @ncallaway at least one of you should take a look here

This addresses #11

Seems fine outside of the small comments.


Error message when verifying message consumer pact

I'm trying to create an example for message contracts along the lines of the examples  in the pact-js repo.
The consumer test is successful, but pact-node does not write the Pact file. The console shows this error message:
 ERROR: "pact-message update" was called with arguments ["{\"description\":\"a hero", "created message\",\"contents\":{\"id\":{\"contents\":42,\"json_class\":\"Pact::SomethingLike\"},\"name\":{\"contents\":\"Superman\",\"json_class\":\"Pact::SomethingLike\"},\"superpower\":{\"contents\":\"flying\",\"json_class\":\"Pact::SomethingLike\"},\"universe\":{\"data\":{\"generate\":\"DC\",\"matcher\":{\"json_class\":\"Regexp\",\"o\":0,\"s\":\"^(DC|Marvel)$\"}},\"json_class\":\"Pact::Term\"}},\"metadata\":{\"content-type\":\"application/json\"}}"]
    Usage: "pact-message update MESSAGE_JSON --consumer=CONSUMER --pact-dir=PACT_DIR --provider=PROVIDER"

I have pushed the code to github here. The problem can be reproduced by calling npm run test:consumer.
Do you have an idea what's wrong with my example?
The example from the pact-js repo runs fine on my machine (at least after adding a missing done()). But I don't see the difference between both examples.

This is (finally) fixed in v10.11.2. Sorry it took so long!


Update ABOUT.md

Closing to clean up the PRs, this seems quite out of date. Feel free to reopen if I'm wrong!


Customize 3scale-gateway

Hi. I want to customize 3scale-gateway for my own Purpose. Specifically I want to add some field in header of HTTP request from 3scale-gateway to next module (gateway and my app deployed in Knative System). Can you show me how can I do that?
Thanks so much!.

You can try ko apply -Rf config/core/ to rebuild your knative components.


node v4 support dropped?

I am getting typeError: this is not a typed array
at Object.<anonymous> (.../node_modules/tar/lib/parse.js:33:27)
It looks like Buffer.from is a node v6 feature and on Feb 22 there was a commit to go from new buffer to Buffer.from, dropping all support before v6: https://github.com/npm/node-tar/commits/master/lib/parse.js
Is this intended?  I had a dependency thats used by many other modules where it did tar: ^4, so if this was intended I would think it should be a major version change as its a breaking change.

It looks like const Buffer = require('./buffer.js') needs to be added to parse.js in order to give Buffer backwards compability. All other files that are touched in https://github.com/npm/node-tar/commit/4513e3bbb887b1be77db3146de4ecbc4bfac4747#diff-9f97a9c36fbbfb0d19068d6fae3bb84e are suspect and would need to make sure they work in node v4


OS X 10.6?

Yea... so umm i got the bootloader to work... imma try to get to the desktop... (lol ik this won't work)
I chose 10.6 because it is the first version with Intel CPU support, and it is 32-bit, and is the most lightweight.

@copy do you think there would be a way to add a second CD drive, like i said, this is just the bootloader, its fine if you can't get 2 CD drives, i can just combine the bootloader with the OS X iso.

If you have anything that works in qemu (i386) I might have a look at it.

alright

UPDATE: I figured out that OS X 10.6 CAN run in qemu(i386), but...... imma have to install linux to do it 🤦, but im still gonna do it, ill update soon.

UPDATE: I figured out that OS X 10.6 CAN run in qemu(i386), but...... imma have to install linux to do it 🤦(because WSL is annoying and slow with QEMU, so ubuntu would be WAY easier for me at least), but im still gonna do it cuz why not, ill update soon.

I was gonna do it in VirtualBox but after reading some issues, i realized that if you create it in VBox, it most likely won't work in V86.

UPDATE: I figured out that OS X 10.6 CAN run in qemu(i386), but...... imma have to install linux to do it 🤦(because WSL is annoying and slow with QEMU, so ubuntu would be WAY easier for me at least), but im still gonna do it cuz why not, ill update soon.

I was gonna do it in VirtualBox but after reading some issues, i realized that if you create it in VBox, it most likely won't work in V86.

If you have a USB drive, install Slax on it. Then it'll work.


"stat: illegal option -- c"

hi! this happens to me on current osx, installed by fisherman:
stat: illegal option -- c
usage: stat [-FlLnqrsx] [-f format] [-t timefmt] [file ...]
(standard_in) 2: parse error
test: Missing argument at index 2

This is a known issue — macOS comes with a BSD-like version of stat which does not support the -c option. Please see the OSX section in the readme: https://github.com/MaxMilton/pure#osx-compatibility.


Update AUTHORS and bump version

Update to AUTHORS and bump version to 1.3.0

@clintonb @rlucioni

:+1:

:+1:


OpenSource :  1.2 What Is a Distributed Version Control System (DVCS)?

Description :

What Is a Distributed Version Control System (DVCS)?
The Evolution of Distributed Version Control Systems.
Limitations of the DVCS Model.
Why Companies Switch to Centralized Version Control Systems?

Note :

Changes should be made inside the Open_Source/ directory & Opensource branch.
Issue only for GWOC'21 contributors.
Issue will be assigned on a first come first serve basis, 1 Issue  ==  1 PR.

Must Follow : Contributing Guidelines & Code of Conduct before start Contributing.
Happy Contributing 🙌

Can I work on this issue?

@Dhruv-194  Sure, I'll assign this to you !!
Happy Documenting 🙌

sir can I work on this issue?

sir can I work on this issue?

@Akshat-2002-coder  Hey thanks for asking , Actually this issue is already been assigned to contributor so can you look other plenty of open issues,  thanks✌

@Dhruv-194  Any updates on this ?

sir can I work on this issue?

@Akshat-2002-coder Hey thanks for asking , Actually this issue is already been assigned to contributor so can you look other plenty of open issues, thanks

There are no issues open.

sir can I work on this issue?

@Akshat-2002-coder Hey thanks for asking , Actually this issue is already been assigned to contributor so can you look other plenty of open issues, thanks

There are no issues open.

Hey @siddhi-244  👋, You can create a new issue that you want to work under open_source_domain

sir can I work on this issue?

@Akshat-2002-coder Hey thanks for asking , Actually this issue is already been assigned to contributor so can you look other plenty of open issues, thanks

There are no issues open.

Hey @siddhi-244 👋, You can create a new issue that you want to work under open_source_domain

Where is the road map?? And I have opened a new issue there is no reply for that.

@Dhruv-194 Any updates on this ?

I will complete this issue by today itself. Thank you for reminding :)

@Dhruv-194  Updates??

Hey @Aryamanz29 I was working on this issue. And I am having two problems with it.

I cannot a find a lot of detailed information for the evolution of DVCS. So can we add any other topic in place of it.
The second one is for companies switching to CVCS. Are you sure that companies are switching to CVCS? Because wherever I go, I read that most of the companies have started to use DVCS instead of CVCS. So is there a mistake in the heading?

Hey @Aryamanz29 I was working on this issue. And I am having two problems with it.

I cannot a find a lot of detailed information for the evolution of DVCS. So can we add any other topic in place of it.
The second one is for companies switching to CVCS. Are you sure that companies are switching to CVCS? Because wherever I go, I read that most of the companies have started to use DVCS instead of CVCS. So is there a mistake in the heading?

We need to add content about DVCS, So we can't change that right now
Yes there is a typo it should be DVCS

@Dhruv-194  I have changed issue description, Please look into this
Here is ref for you : https://www.slideshare.net/caniszczyk/evolution-of-version-control-in-open-source

@Dhruv-194  Try to complete this issue today
Thanks

Okay Thank you @Aryamanz29


feature: add range functionality to fix_time in Task

added range functionality to fix_time
adjusted times order in the signals and fix the tests
wrapped together functions for tuples
added tests for fix_time as a range

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#68  👈
#65
#64
#63
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @gcroci2 and the rest of your teammates on  Graphite

I realize that in the currently planned experiments these are not needed, but I can easily imagine a future application where they are. Is there any reason not to include the option already?

We should ask how realistic it is that a user might need them, from the experiments point of view. Otherwise, I would avoid implementing them until someone requests the specific feature. Imo, stim_time is something you want to have fixed and not random. fix_intensity is not even much used as a constant value, from what I understood, so no need of adding code lines and tests for something it will be barely used even in its basic form. stim_intensity is the only one I think it could be useful because we are basically using it as a range already (e.g., [0.8, 0.9, 1.0]), but then the con is that in cases in which you are interested in very low values and very high values (e.g., [0.2, 0.25, 0.3, 0.35, 0.9, 0.95]), you don't have a way to set this with a range, because also random numbers in between will be chosen.
So to conclude, I'd stick to what we have now, without implementing additional ranges. If you're not convinced I'd ask to the others first which ones make more sense :)

I approved this PR because I think at this point it's fine either with or without my suggestions above, your call.

I realize that in the currently planned experiments these are not needed, but I can easily imagine a future application where they are. Is there any reason not to include the option already?

We should ask how realistic it is that a user might need them, from the experiments point of view. Otherwise, I would avoid implementing them until someone requests the specific feature. Imo, stim_time is something you want to have fixed and not random. fix_intensity is not even much used as a constant value, from what I understood, so no need of adding code lines and tests for something it will be barely used even in its basic form. stim_intensity is the only one I think it could be useful because we are basically using it as a range already (e.g., [0.8, 0.9, 1.0]), but then the con is that in cases in which you are interested in very low values and very high values (e.g., [0.2, 0.25, 0.3, 0.35, 0.9, 0.95]), you don't have a way to set this with a range, because also random numbers in between will be chosen.
So to conclude, I'd stick to what we have now, without implementing additional ranges. If you're not convinced I'd ask to the others first which ones make more sense :)

I think that to make the code flexible to whatever a user wants to do (that is not ridiculous), I don't see why not to add the options. Given that you've now written a functions to do implement the random ranges and checks that the inputs are as expected, it doesn't add much code to apply it to other parameters as well. Your call though on how to proceed.
I do definitely agree with the point you make about high and low values. I guess strictly speaking this could also be true for other parameters, but much less likely. Formally speaking a user could also prefer to draw from a different distribution than uniform. I think both these points could be implemented without too much problems, but neither of these are within the scope right now.

I realize that in the currently planned experiments these are not needed, but I can easily imagine a future application where they are. Is there any reason not to include the option already?

We should ask how realistic it is that a user might need them, from the experiments point of view. Otherwise, I would avoid implementing them until someone requests the specific feature. Imo, stim_time is something you want to have fixed and not random. fix_intensity is not even much used as a constant value, from what I understood, so no need of adding code lines and tests for something it will be barely used even in its basic form. stim_intensity is the only one I think it could be useful because we are basically using it as a range already (e.g., [0.8, 0.9, 1.0]), but then the con is that in cases in which you are interested in very low values and very high values (e.g., [0.2, 0.25, 0.3, 0.35, 0.9, 0.95]), you don't have a way to set this with a range, because also random numbers in between will be chosen.
So to conclude, I'd stick to what we have now, without implementing additional ranges. If you're not convinced I'd ask to the others first which ones make more sense :)

I think that to make the code flexible to whatever a user wants to do (that is not ridiculous), I don't see why not to add the options. Given that you've now written a functions to do implement the random ranges and checks that the inputs are as expected, it doesn't add much code to apply it to other parameters as well. Your call though on how to proceed.

I think we need to balance a bit between developing the most flexible framework, the best practices, and what is needed for the experiments. It is true that the project is at its beginning, but I'd try to be selective about how to spend time on the code-base from the beginning. For extending the ranges thing, atm I think there are more possibilities that the functionality would be not used or would need edits to be used than the contrary, so I'd avoid doing that unless explicitly requested. Same for a different distribution than uniform, which would be a very nice feature actually. If it will be requested, should be fast enough to be implemented anyway.


Test

test

Test 3

Test 4

Test 30
“It’s tough,” says Porsche Penske Motorsport driver Nick Tandy, before clarifying that it’s much tougher for the crew than the drivers. “For our crew, we raced at Laguna for a weekend. The next week, we tested at Watkins Glen for two days. The next week, we went to Detroit to race. The next week, we came [to Le Mans] to test, then we race at Le Mans and then we go straight to the Six Hours of the Glen. So it’s at least a six-, seven-week run where the cars have been running on track, the crew have been obviously working on the cars traveling back and forwards all over the states and to Europe and back.”

Test 31 “It’s tough,” says Porsche Penske Motorsport driver Nick Tandy, before clarifying that it’s much tougher for the crew than the drivers. “For our crew, we raced at Laguna for a weekend. The next week, we tested at Watkins Glen for two days. The next week, we went to Detroit to race. The next week, we came [to Le Mans] to test, then we race at Le Mans and then we go straight to the Six Hours of the Glen. So it’s at least a six-, seven-week run where the cars have been running on track, the crew have been obviously working on the cars traveling back and forwards all over the states and to Europe and back.”

Test 32 “It’s tough,” says Porsche Penske Motorsport driver Nick Tandy, before clarifying that it’s much tougher for the crew than the drivers. “For our crew, we raced at Laguna for a weekend. The next week, we tested at Watkins Glen for two days. The next week, we went to Detroit to race. The next week, we came [to Le Mans] to test, then we race at Le Mans and then we go straight to the Six Hours of the Glen. So it’s at least a six-, seven-week run where the cars have been running on track, the crew have been obviously working on the cars traveling back and forwards all over the states and to Europe and back.”


Update azure-cni-overlay.md

removed limitation in regions not support ARM64, since it's present today. This is not relevant anymore. ARM64 is now supported in all regions in Overlay.

#sign-off


e.startsWith is not a function

My contact has recently reset his keys.
I saw the notice of that in our chat and, after clicking Jump to new conversation nothing was happening (or it looked like so), so I clicked again a couple of times and then this error appeared at the top of the Keybase client window.
TypeError: e.startsWith is not a function at Object.m [as isPendingConversationIDKey] (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:1:205342) at d (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:6:82435) at d.next (<anonymous>) at n (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:6:162150) at s (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:6:167747) at k (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:6:163838) at x (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:6:164445) at y (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:6:163393) at file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:6:165943 at Array.forEach (native)

Still happens with the new version 1.33, FYI

Thanks @Heliosmaster; we've gotten similar complaints in a post-reset state. We're going to put some effort in the coming weeks against fixing the experience after reset, which is quite rough.
Cc: @keybase/react-hackers


LLVM ERROR: Cannot select issue when compiling LLVM module on s390x architecture

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 20.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: N/A
TensorFlow installed from (source or binary): source
TensorFlow version (use command below): 2.3.1
Python version: 3.8.5
Bazel version (if compiling from source): 3.1.0
GCC/Compiler version (if compiling from source): Ubuntu 9.3.0-17ubuntu1~20.04
CUDA/cuDNN version: N/A
GPU model and memory: N/A

Describe the current behavior
When running the test case //tensorflow/python/keras/optimizer_v2:adam_test on s390x machine, please see below for the full error stack. Apparently, it is an issue within the compiler code and the same issue is causing a lot of other test cases failures under //tensorflow/compiler/... test suite.
I investigated the issue a little bit, and I noticed that the error is thrown when executing this line https://github.com/tensorflow/tensorflow/blob/fcc4b966f1265f466e82617020af93670141b009/tensorflow/compiler/xla/service/cpu/simple_orc_jit.cc#L178, i.e., when compiling the LLVM IR code into machine code. Since LLVM is supporting s390x architecture (as "SystemZ") and I manually merged the commit to include it into build target, it should be able to execute the compilation without any issue. Since the error message does not have much readable info about the error, I am kind of stuck in figuring out the cause of the issue. If anyone who is familiar with LLVM could help with debugging this issue, I will really appreciate it, thanks.
Describe the expected behavior
The compilation should work, and the test case should pass.
Other info / logs
adam_test.log

In TensorFlow 2.5.0 the same issue still persists. Hi @r4nt, do you have any insights on this?

The root cause has been found and tracking through: https://bugs.llvm.org/show_bug.cgi?id=51030


Setup operator-ci for release branch of caikit-tgis-serving

PR : https://github.com/openshift/release/pull/41254


Experiment with improving fixture tokens handling

/azp run

Looks like something is still flaky? CooperativeCancellation_WhenTestCleanupTimeoutExpiresAndUserChecksToken_StepThrows is currently failing on MacOS release.

@Youssef1313 I have done multiple rerun and it seems this is no longer flaky (or that the level of flakiness dropped enough)


Expand the register file functionality to support variable bit width

Context:
Expanding the register file functionality to support variable bit width.
Changes:

Modified config.yml for rf to support different widths (8, 16, 32, 64, 128, 256)
word_width is no longer hard coded in reg_data.py
the method synthesis in dffram.py now takes two more parameters to be able to pass the correct parameter for model.v
changed the parameter RWIDTH to WSIZE for the sake of consistency in model.v for rf.

Could you look at adding non-multiple of 8 widths in the future too? 9 bits, 18 bits, 4 bits and 6 bits can all be useful if things like ECC or other status bits are needed.

@mithro We'll investigate.


HOT-FIX: Fix broken links

Found several broken links in the docs, mostly in streams-concepts
For testing, I ran kafka-site locally with these changes.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@guozhangwang, @mjsax, @vvcephei for review
\cc @joel-hamill @JimGalasyn  for reviews as well

Is there any new content added here?

@joel-hamill yes, the sections added are KStream, KTable, and GlobalKTable as the links were there but not the content.  But this info already exists in CP.

Fixed some additional links, should be all of them now.

@guozhangwang made changes per comments.
@joel-hamill mind taking another look? I've tested locally, but another quick pass wouldn't hurt.

Thank you @bbejeck !!


Update any remaining  headers to be  in order that linking works properly

We need to update any outstanding Level 1 headers to be Level 2 headers as Docusaurus does not support h1 anchors.
See also: Slack thread

Hey, @jtravee is this issue resolved?

Hey, @jtravee is this issue resolved?

Hi @akshat5302, no we have not yet done this; we are in the middle of restructuring our docs after the initial rollout. Once we've completed this, we will be implementing these changes (next few weeks projected).


Terminal parsing

Is it possible to parse a piece of the terminal (last line for instance) to determine which account to load? And is it possible to chat the password directly from 1pw into the terminal?
For instance I sometimes SSH into a remote server and want to do a git pull one of my private Github repos. I would like to:
me@myserver:~/folder$ git pull
Username for 'https://github.com':
And then hit cmd-\ and then have it show my Github web entry. Then when I choose it that it first enters the username and then the password, preferably depending on what the terminal asks.
Maybe in the beginning this could simply be depending on a few chat script like fields inside the different accounts. For instance by setting 'match_login' as 'git pull',  'match_user' as' Username for 'https://github.com':', etc.. Then it could chat with the terminal directly after I hit cmd-\ and choose the account that I want to use?

@lrozema So sorry I didn't respond sooner! That's something I've wanted to experiment with but haven't had time to as of late. I will definitely see if we can do something here.

This could probably be handled by allowing a username to be specified on the command line when starting the co-process.  iTerm triggers could then be used instead of a keypress to start the coprocess.  The coprocess could then send the DEFAULT_HOSTNAME string, but with the username included.  The triggers can pass in data that is gathered from a regular expression.

That's exactly what I do and it works well. The change I made to make this possible is here: https://github.com/lrosenstein/sudolikeaboss/commit/fb36f082e88e5f6910940be51dce0d6c15ee5d33

Not bad.  What I've wanted to do is to have the option of specifying a user and host, if a user is specified, use:
sudolikeaboss://@local
and if user and host is specified use:
sudolikeaboss://@
Then, hopefully be able to configure a trigger that grabs the username and possibly hostname from the sudo command.  I could then configure the sudo prompt to include username and hostname on all my hosts.  The regular expression could then send just the username if I'm on a kerberos/ad connected server, or the username and hostname if not.


[Doc Improvement][Doc Modernization Update MPN ID][3948380]

Updating for MPN ID's updated name

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/teams-faq.md
89
82
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/teams-faq.md
89
82
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/teams-faq.md
89
82
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/prepare/manage-third-party-apps-license.md
89
19
link
:white_check_mark:

msteams-platform/teams-faq.md
89
82
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/prepare/manage-third-party-apps-license.md
90
18
link
:white_check_mark:

msteams-platform/teams-faq.md
89
84
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/prepare/manage-third-party-apps-license.md
90
18
link
:white_check_mark:

msteams-platform/get-started/glossary.md
89
98
link
:white_check_mark:

msteams-platform/teams-faq.md
89
84
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/prepare/manage-third-party-apps-license.md
90
18
link
:white_check_mark:

msteams-platform/get-started/glossary.md
89
98
link
:white_check_mark:

msteams-platform/teams-faq.md
89
84
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/manage-your-apps-in-developer-portal.md
90
20
link
:white_check_mark:

msteams-platform/concepts/deploy-and-publish/appsource/prepare/manage-third-party-apps-license.md
90
18
link
:white_check_mark:

msteams-platform/concepts/deploy-and-publish/appsource/prepare/teams-store-validation-guidelines.md
91
131
link
:white_check_mark:

msteams-platform/get-started/glossary.md
89
98
link
:white_check_mark:

msteams-platform/includes/tabs/node-js-yeoman-prereq.md
85
15
link
:white_check_mark:

msteams-platform/m365-apps/publish.md
95
9
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema-dev-preview.md
84
126
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema.md
86
109
link
:white_check_mark:

msteams-platform/tabs/how-to/create-channel-group-tab.md
92
64
link
:white_check_mark:

msteams-platform/tabs/how-to/create-personal-tab.md
93
56
link
:white_check_mark:

msteams-platform/teams-faq.md
89
84
link
:white_check_mark:

msteams-platform/toolkit/publish-your-teams-apps-using-developer-portal.md
96
2
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/manage-your-apps-in-developer-portal.md
90
20
link
:white_check_mark:

msteams-platform/concepts/deploy-and-publish/appsource/prepare/manage-third-party-apps-license.md
90
18
link
:white_check_mark:

msteams-platform/concepts/deploy-and-publish/appsource/prepare/teams-store-validation-guidelines.md
91
131
link
:white_check_mark:

msteams-platform/get-started/glossary.md
89
98
link
:white_check_mark:

msteams-platform/includes/tabs/node-js-yeoman-prereq.md
85
15
link
:white_check_mark:

msteams-platform/m365-apps/publish.md
95
9
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema-dev-preview.md
84
126
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema.md
86
109
link
:white_check_mark:

msteams-platform/tabs/how-to/create-channel-group-tab.md
92
64
link
:white_check_mark:

msteams-platform/tabs/how-to/create-personal-tab.md
93
56
link
:white_check_mark:

msteams-platform/teams-faq.md
89
84
link
:white_check_mark:

msteams-platform/toolkit/publish-your-teams-apps-using-developer-portal.md
96
2
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/manage-your-apps-in-developer-portal.md
90
20
link
:white_check_mark:

msteams-platform/concepts/deploy-and-publish/appsource/prepare/manage-third-party-apps-license.md
90
18
link
:white_check_mark:

msteams-platform/concepts/deploy-and-publish/appsource/prepare/teams-store-validation-guidelines.md
91
131
link
:white_check_mark:

msteams-platform/get-started/glossary.md
89
98
link
:white_check_mark:

msteams-platform/includes/tabs/node-js-yeoman-prereq.md
85
15
link
:white_check_mark:

msteams-platform/m365-apps/publish.md
95
9
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema-dev-preview.md
84
126
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema.md
86
109
link
:white_check_mark:

msteams-platform/tabs/how-to/create-channel-group-tab.md
92
64
link
:white_check_mark:

msteams-platform/tabs/how-to/create-personal-tab.md
93
56
link
:white_check_mark:

msteams-platform/teams-faq.md
89
84
link
:white_check_mark:

msteams-platform/toolkit/publish-your-teams-apps-using-developer-portal.md
96
2
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/manage-your-apps-in-developer-portal.md
90
20
link
:white_check_mark:

msteams-platform/concepts/deploy-and-publish/appsource/prepare/manage-third-party-apps-license.md
90
18
link
:white_check_mark:

msteams-platform/concepts/deploy-and-publish/appsource/prepare/teams-store-validation-guidelines.md
91
131
link
:white_check_mark:

msteams-platform/get-started/glossary.md
89
98
link
:white_check_mark:

msteams-platform/includes/tabs/node-js-yeoman-prereq.md
85
15
link
:white_check_mark:

msteams-platform/m365-apps/publish.md
95
9
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema-dev-preview.md
84
126
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema.md
86
109
link
:white_check_mark:

msteams-platform/tabs/how-to/create-channel-group-tab.md
92
64
link
:white_check_mark:

msteams-platform/tabs/how-to/create-personal-tab.md
93
56
link
:white_check_mark:

msteams-platform/teams-faq.md
89
84
link
:white_check_mark:

msteams-platform/toolkit/publish-your-teams-apps-using-developer-portal.md
96
2
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.


Better CMake support

This is an answer to this warning.
For my needs it's enough to just remove the warning and add the module. I'm not sure what else could be needed?
Maybe a check for JUCE like in melatonin_inspector would be nice?

Thanks for this. Yeah, this was just like... "I can't deal with this, drawing a line here for now!" — a check for JUCE would be nice!

Makes sense! Added the check now :)

Thanks for this!
That macos-latest is being intermittent on main as well, so I'll merge anyway. I'm sort of confused why the runs are being cancelled, but I might look into removing the benchmark stuff from the CI runs, they take much longer.

The job running on runner GitHub Actions 3 has exceeded the maximum execution time of 10 minutes.

Ok, wow.... this is new....


Validate settings

These conditions will all result in an error, would be nice to validate them on startup and provide descriptive error messages:

Missing workingDirectory
No storagePath or s3Bucket
Non-numeric value for maxUploadSize
Invalid fonts array
Missing fonts files
Non-string redisHost

Could also provide warnings about:

Improperly formatted themes
Themes missing required options

Missing AWS credentials are already handled by a headBucket() test on startup.

Merged to master.


 This lets users hanging around without able to automatically download bean-test anymore.
There is already a start with 9cb29eb to publish the artifact on Github Packages but it's not finished.
Possible Solution
Please provide the existing artifact info.novatec:bean-test:0.2.Final on a publicly available repository like Maven Central (howto: https://dzone.com/articles/how-to-publish-artifacts-to-maven-central).
Workarounds for users
Summary possible workaround (partly under investigation).
1. Deploy to Maven Central as fork
Looks straightforward, but probably only Novatec can do this for the original artifact due to Maven Central checking ownership over the groupId. So it would be needed to fork, rewrite the groupId and then deploy to Maven Central.
2. Use Github Packages
Was started with 9cb29eb (thanks for that), can also be done with a self-maintained fork. But a downside is that Github Packages requires token authentication also for public repos (doc here: https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry). Setting secrets in every users settings.xml might not be ideal.
A workaround would be to write credentials into the pom.xml
<repository>
   <id>BeanTest</id>
   <name>BeanTest Repository</name>
<EMAIL_ADDRESS>   <!-- Contains access token to download from Github Packages (and only for that use case) -->
</repository>

Update: The approach with username:accesstoken is prevented by Github (actually, a good sign that hardcoded credentials don't work on Gihub :-) ): A recent scan found a valid GitHub Personal Access Token linked to your GitHub account in commit at ...
3. Provide bean-test with system scope
Upload the existing jar into a maven project and link it with
			<dependency>
				<groupId>info.novatec</groupId>
				<artifactId>bean-test</artifactId>
				<version>0.2.Final_Local</version>
				<scope>system</scope>
				<systemPath>${project.basedir}/../sormas-base/dependencies/bean-test-0.2.Final.jar</systemPath>
				<!-- Changed scope "test" to "system" as workaround for currently no publicly available maven artifact -->
			</dependency>

			<!-- Dependencies of bean-test that are missing without the POM -->
			<dependency>
				<groupId>org.jboss.weld.se</groupId>
				<artifactId>weld-se</artifactId>
				<version>2.1.2.Final</version>
				<scope>test</scope>
			</dependency>
			<dependency>
				<groupId>org.apache.deltaspike.core</groupId>
				<artifactId>deltaspike-core-impl</artifactId>
				<version>1.2.1</version>
				<scope>test</scope>
			</dependency>
			<dependency>
				<groupId>org.apache.deltaspike.cdictrl</groupId>
				<artifactId>deltaspike-cdictrl-weld</artifactId>
				<version>1.2.1</version>
				<scope>test</scope>
			</dependency>

Problem with this approach: Changing the scope lets transitive dependencies like deltaspike or weld not be part of the Classpath because there is no POM linked to lookup dependencies. I documented dependencies that I needed to add, but in depends on the use case.
Doc: https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#system-dependencies

Hi @carlosbarragan,
thanks for you quick try, I saw it and we followed up on it. We made the approach with Github Packages running, see https://github.com/hzi-braunschweig/BeanTest/commit/8f0cb575fd38afef81677c5fa9d59bf6680523de to publish version 0.2.0.Final . But the inconvenience with mandatory credentials is too annoying, and hardcoding the login to basically all public Github Packages repositories is probably a bit too extreme.
My current approach is to deliver a workaround for my project, but I would really appreciate a publicly hosted artifact under the original maven coordinates.

We now went with the system scope approach as workaround.

We are still evaluating whether we publish it to maven or we follow the approach of using GitHub as a maven Repository: https://www.baeldung.com/maven-repo-github
I also noticed some dependencies are really old and have vulnerabilities so it would be a good idea to update them. I also think that JDK 11 as baseline would be appropriate. However, I don't know if Java 11 and the dependencies update could affect your project because of version conflicts etc.

The idea to use the Github repo tree as Maven Repository looks as an option (if it works but looks like it), but still less straight forward than Maven Central.
I think updating to JDK 8 is probably a must if one would go into the topic updating dependencies. If JDK 11 is mandatory on the update path than it may be. But it would probably be helpful to publish a version compatible to 0.2.Final and keep dependency updates indipendent for a follow-up version.

The "problem" with Maven Central is that it takes longer because of the requirements that need to be fulfilled. Besides, I don't know if they would easily accept an artefact that contains old dependencies with vulnerabilities 🤔


Support time dependent concentration BCs for Delwaq

As we now only support a single (first) timestep for the Delwaq input.

Duplicate of #1484


fixed link to test src

what

Fixed the typo for the link to test/src'

why

So that the link in the readme points to the appropriate page

references

N/A

@johncblandii

Thanks @david-hankinson. Could you make the change in README.yaml (as stated in the top of the README file) ?
** DO NOT EDIT THIS FILE
  **
  ** This file was automatically generated by the `cloudposse/build-harness`.
  ** 1) Make all changes to `README.yaml`
  ** 2) Run `make init` (you only need to do this once)
  ** 3) Run`make readme` to rebuild this file.
  **
  ** (We maintain HUNDREDS of open source projects. This is how we maintain our sanity.)
  **

thanks for the info, I believe i've made the appropriate changes now

Hey could this be merged into main?

@johncblandii


Editable installs with src in 3.5.0

Thanks for flit, and congrats on 3.5.0!
Using a src/<module>/__init__.py layout, I am, however, seeing some odd behavior with editable installs on flit(-core) 3.5.0:
flint install --symlink --deps=none
Symlinking src/jupyterlite -> ~/envs/default/lib/python3.9/site-packages/src/jupyterlite  I-flit.install
Traceback (most recent call last):
  File "~/envs/default/lib/python3.9/runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "~/envs/default/lib/python3.9/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "~/envs/default/lib/python3.9/site-packages/flit/__main__.py", line 5, in <module>
    main()
  File "~/envs/default/lib/python3.9/site-packages/flit/__init__.py", line 200, in main
    Installer.from_ini_path(args.ini_file, user=args.user, python=python,
  File "~/envs/default/lib/python3.9/site-packages/flit/install.py", line 416, in install
    self.install_directly()
  File "~/envs/default/lib/python3.9/site-packages/flit/install.py", line 312, in install_directly
    os.symlink(src.resolve(), dst)
FileNotFoundError: [Errno 2] No such file or directory: '~/jupyterlite/py/jupyterlite/src/jupyterlite' -> '~/envs/default/lib/python3.9/site-packages/src/jupyterlite'

presumably failing because site-packages/src does not exist

flit install --pth-file --deps=none
Adding .pth file ~/envs/default/lib/python3.9/site-packages/jupyterlite.pth for src  I-flit.install
Writing script to ~/envs/default/bin/jupyter-lite  I-flit.install

just exhibits no module named jupyterlite when importing, running CLI, etc.

Meanwhile... reverting to flit 3.4.0 does not have this issue:
Symlinking src/jupyterlite -> ~/envs/default/lib/python3.9/site-packages/jupyterlite  I-flit.install
Writing script to ~/envs/default/bin/jupyter-lite  I-flit.install

Adding .pth file ~/envs/default/lib/python3.9/site-packages/jupyterlite.pth for ~/jupyterlite/py/jupyterlite/src  I-flit.install
Writing script to ~/envs/default/bin/jupyter-lite  I-flit.install

Sorry about that. It will be the changes in #468 that broke it.

#472 should fix this.

Fantastic turn-around, thanks!

Hooray?

I hope so: 3.5.1 is out now and should fix this. Feel free to open a new issue, or comment here, if there are still problems.

Sounds great, and thanks again. My CI will be testing it out as soon as https://github.com/conda-forge/flit-feedstock/pull/32 lands! It's great to see src under test, going forward.

(actually, will be testing the PyPI version before that, locally)


Release 0.5.1

@rultor release it; the tag is 0.5.1.

@rultor release it; the tag is 0.5.1.

@rafamizes OK, I will release it now. Please check the progress here

@rultor release it; the tag is 0.5.1.

@rafamizes Done! FYI, the full log is here (took me 1min)


Schedule of Dataset Releasing

Hi @jwyang , do you have a schedule to release the dataset? Thanks for your great project!

Thanks for your interest! We will release the dataset tomorrow!
On Tue, Nov 7, 2023 at 1:18 AM Zi-Yuan Hu @.***> wrote:

Hi @jwyang https://github.com/jwyang , do you have a schedule to
release the dataset? Thanks for your great project!
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/SoM/issues/4 or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA5WXZ5HCBSLGIP6FUIJH7LYDH4ETBFKMF2HI4TJMJ2XIZLTSOBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJLJONZXKZNENZQW2ZNLORUHEZLBMRPXI6LQMWBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTLDTOVRGUZLDORPXI6LQMWSUS43TOVS2M5DPOBUWG44SQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKJXGA2TINJZGY2DTAVEOR4XAZNFNFZXG5LFUV3GC3DVMWVDCOJYGA4DSMRZGY4KO5DSNFTWOZLSUZRXEZLBORSQ
.
You are receiving this email because you were mentioned.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub
.

Got it. Thanks for your quick reply!

Hi, @HenryHZY,
thanks again for your interest. Please find the first version of our SoM-Bench here:
https://github.com/microsoft/SoM/tree/main/benchmark
Please note that we still working on the compilation of the ground-truth annotations for COCO, ADE20K and the automatic evaluation code now that GPT-4V API has been released. For now, you can try flickr30k and refcocog first.
thanks!

Hi @jwyang
Thanks for the detailed update of the datasets and task prompts!
I have tested some of the examples in the paper previously and found that GPT-4V+SoM didn't work particularly well. But it did get better with the addition of some prompts about "numberic ID".
And I just find that Benchmark Readme also provides a "language prompt" for a specific task, which is reasonable and important for SoM prompting.
Thanks again. I think we can close this issue now:)


Properly encode content-disposition header

Provide a narrative description of what you are trying to accomplish:

[x] Are you fixing a bug?

[x] Detail how the bug is invoked currently.
[x] Detail the original, incorrect behavior.
[x] Detail the new, expected behavior.
[x] Base your feature on the master branch, and submit against that branch.
[ ] Add a regression test that demonstrates the bug, and proves the fix.
[x] Add a CHANGELOG.md entry for the fix.

Always use ASCII for the content-disposition header. When using UTF-8 encoding, this results in a header being set as Content-Disposition: =?utf-8?Q?inline?= which is not interpreted properly by Thunderbird nor Microsoft Exchange / Outlook. This pull request forces encoding for this header to always be ASCII, so that the header reads Content-Disposition: inline and is correctly interpreted by email clients.
Fixes: https://github.com/magento/magento2/issues/25076

This repository has been closed and moved to laminas/laminas-mail; a new issue has been opened at https://github.com/laminas/laminas-mail/issues/2.

This repository has been moved to laminas/laminas-mail. If you feel that this patch is still relevant, please re-open against that repository, and reference this issue. To re-open, we suggest the following workflow:

Squash all commits in your branch (git rebase -i origin/{branch})
Make a note of all changed files (`git diff --name-only origin/{branch}...HEAD
Run the laminas/laminas-migration tool on the code.
Clone laminas/laminas-mail to another directory.
Copy the files from the second bullet point to the clone of laminas/laminas-mail.
In your clone of laminas/laminas-mail, commit the files, push to your fork, and open the new PR.
We will be providing tooling via laminas/laminas-migration soon to help  automate the process.


Hack crashes after inject

Code is not modified. The game does not crash.
Build: VS 2017 Community
Windows SDK: 10.0.17763.0
OS: Windows 10 x64
CSGO: <IP_ADDRESS>, non-steam
An exception was thrown at the address 0x00F67267 (Osiris.dll) in csgo.exe: 0xC0000005: read access violation at 0x00000000.

CSGO: <IP_ADDRESS>, non-steam
The cheat working only on steam version


yet again trying to send me bcc to binance to transfer to another crypto and it goes unconfirmed again.

Not sure why its going unconfirmed, i sent this over 8 hours ago and still has not reached my binance account.

 Trusted Key has chosen not support Bitcoin Cash.  They are the 3rd party that operates 2fa.  Please see #41 to move your coins out of the 2fa wallet and into a normal wallet.


Provide option to enable only specific cloud provider

It would be nice to have the option to disable other cloud providers than Azure.
Context
We are currently seeing error logs in our aad-pod-identity pods in AKS, which are caused by requests from the datadog agent:
E0119 10:12:13.871629       1 server.go:518] metadata header is not specified, req.method=GET reg.path=/latest/meta-data/hostname req.remote=<IP_ADDRESS>
E0119 10:12:13.872182       1 server.go:518] metadata header is not specified, req.method=GET reg.path=/latest/meta-data/instance-id req.remote=<IP_ADDRESS>
E0119 10:12:14.187564       1 server.go:518] metadata header is not specified, req.method=GET reg.path=/computeMetadata/v1/instance/hostname req.remote=<IP_ADDRESS>
E0119 10:12:14.188108       1 server.go:518] metadata header is not specified, req.method=GET reg.path=/computeMetadata/v1/instance/name req.remote=<IP_ADDRESS>
E0119 10:12:14.194333       1 server.go:518] metadata header is not specified, req.method=GET reg.path=/computeMetadata/v1/ req.remote=<IP_ADDRESS>
E0119 10:12:14.228989       1 server.go:518] metadata header is not specified, req.method=GET reg.path=/computeMetadata/v1/instance/network-interfaces/ req.remote=<IP_ADDRESS>
E0119 10:12:14.229483       1 server.go:518] metadata header is not specified, req.method=GET reg.path=/latest/meta-data/network/interfaces/macs req.remote=<IP_ADDRESS>

As far as I can see these requests are only useful in an AWS or GCE environment, so it would be nice to be able to disable those unnecessary checks.
Steps to reproduce the issue:

Run datadog agent in AKS
Deploy aad-pod-identity in same AKS
add-pod-identity will log the errors shown above

Related issue: https://github.com/Azure/aad-pod-identity/issues/1239

I landed on your issue semi-randomly.
Wouldn't it be possible to use configure this behaviour using the cloud_provider_metadata configuration options for the agent? (datadog.yaml configuration)
## @param cloud_provider_metadata - list of strings -  optional - default: ["aws", "gcp", "azure", "alibaba", "oracle", "ibm"]
## @env DD_CLOUD_PROVIDER_METADATA - space separated list of strings - optional - default: aws gcp azure alibaba oracle ibm
## This option restricts which cloud provider endpoint will be used by the
## agent to retrieve metadata. By default the agent will try # AWS, GCP, Azure
## and alibaba providers. Some cloud provider are not enabled by default to not
## trigger security alert when querying unknown IP (for example, when enabling
## Tencent on AWS).
## Setting an empty list will disable querying any cloud metadata endpoints
## (falling back on system metadata). Disabling metadata for the cloud provider in which an Agent runs may result in
## duplicated hosts in your Datadog account and missing Autodiscovery features
##
## Possible values are:
## "aws"     AWS EC2, ECS/Fargate
## "gcp"     Google Cloud Provider
## "azure"   Azure
## "alibaba" Alibaba
## "tencent" Tencent
## "oracle"  Oracle Cloud
## "ibm"     IBM Cloud
#
# cloud_provider_metadata:
#   - "aws"
#   - "gcp"
#   - "azure"
#   - "alibaba"
#   - "oracle"
#   - "ibm"

@AlexandreArpinMotion thank you! This solved the issue :slightly_smiling_face:


add adjustment for time zone offset

This adds a really primitive adjustment for time zones. The user can simply set the value for tz_offset to the hours difference to UTC and it will do a really simple calculation. This isn't real time zone support, but it lets a new user at least see this demo in their current time zone.

Thank you!


Add distance check for offensive units from APC & Player in rbdnew09

Once there are no PILOTED offensive units in the area, the APC will start to move

do NOT check for guntowers, this would break the common strategy of destroying power while leaving gun tower intact

Not sure the best way to do this, the issue with not checking guntowers is that the APC will run into them once all the american units have been taken out. Checking if either both guntowers or both power plants have been taken out might be a good solution?

I think that would be wise.

My suggestion: Don't bother with giving the APC the order to move to the Recycler, make it clear in objectives that the player needs to order it themselves.


java.lang.NullPointerException: Attempt to invoke interface method 'java.util.Iterator java.lang.Iterable.iterator()' on a null object reference

It is a bug report.
"react": "16.8.6",
"react-native": "0.58.5",
 react-native-maps: 0.23.0

It is happening in Android native side. Application crashed in a class named  AirMapPolyline.java
at com.google.android.gms.maps.model.PolylineOptions.addAll(Unknown Source)
It happenned when I want to draw a polyline. It works in Ios, however it does not work in android
Is there any solution ?

I got the same issue, is there a fix for this? Thanks

I also have this issue.

For anyone that comes across this issue it is not a bug.
The error is thrown whenever a Polyline or Polygon is given passed undefined to the coordinates prop.
Use something like .filter() to remove any undefined items before trying to render them and the error will be eliminated.

i got the same issue

I'm getting this same issue even without and undefined elements in the coordinates array.


Feature request: Lightning Callback

It would be a nice addition to have a nlptest callback that will trigger a nlptest run at the end of an epoch (or at the end of training) and generate a report and metrics.
This could probably be done within the PyTorch Lightning or directly within nlptest.


Make it easier for libraries to add IMemberTranslator implementations

Libraries currently have to jump through a lot of hoops to add additional IMemberTranslator and IMethodCallTranslator implementations.
We should consider doing something similar to IConventionSetBuilder which allows multiple registrations that get aggregated together.

Fixed by #13115


thrust-related compile error when trying to install torch

I want to install torch on a server maintained by our IT department. The server runs Debian 8 (jessie), so I told IT to install the dependencies, as listed in install-deps:
apt-get update
apt-get install -y build-essential curl \
	 cmake libreadline-dev git-core libqt4-dev libjpeg-dev \
	 libpng-dev ncurses-dev imagemagick libzmq3-dev gfortran \
	 unzip gnuplot gnuplot-x11 ipython
apt-get install -y libgraphicsmagick1-dev libfftw3-dev sox libsox-dev

Then, I ran ./install.sh, which fails at some point with:
THCStorage.cu(11): error: class "thrust::detail::execute_with_allocator<THCThrustAllocator, thrust::system::cuda::detail::execution_policy>" has no member "on"

More context:
-- Installing: /home/user/mine/torch/install/lib/luarocks/rocks/optim/1.0.5-0/lua/optim/README.md
Updating manifest for /home/user/mine/torch/install/lib/luarocks/rocks
optim 1.0.5-0 is now built and installed in /home/user/mine/torch/install/ (license: BSD)

Found CUDA on your machine. Installing CUDA packages
Warning: unmatched variable LUALIB

jopts=$(getconf _NPROCESSORS_CONF)

echo "Building on $jopts cores"
cmake -E make_directory build && cd build && cmake .. -DLUALIB= -DCMAKE_CXX_FLAGS=${CMAKE_CXX_FLAGS} -DCMAKE_BUILD_TYPE=Release -DCMAKE_PREFIX_PATH="/home/user/mine/torch/install/bin/.." -DCMAKE_INSTALL_PREFIX="/home/user/mine/torch/install/lib/luarocks/rocks/cutorch/scm-1" && make -j$jopts install

Building on 24 cores
-- The C compiler identification is GNU 4.9.2
-- The CXX compiler identification is GNU 4.9.2
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Found Torch7 in /home/user/mine/torch/install
-- Found CUDA: /usr (found suitable version "7.5", minimum required is "6.5")
-- Removing -DNDEBUG from compile flags
-- TH_LIBRARIES: TH
-- MAGMA not found. Compiling without MAGMA support
-- Autodetected CUDA architecture(s): 5.2 5.2 5.2 5.2 5.2 5.2 5.2
-- got cuda version 7.5
-- Found CUDA with FP16 support, compiling with torch.CudaHalfTensor
-- CUDA_NVCC_FLAGS: -gencode;arch=compute_52,code=sm_52;-DCUDA_HAS_FP16=1
-- THC_SO_VERSION: 0
-- Configuring done
-- Generating done
-- Build files have been written to: /home/user/mine/torch/extra/cutorch/build
[  1%] [  3%] [  3%] [  9%] [  7%] [  9%] [  9%] [  9%] [ 10%] [ 12%] [ 12%] [ 13%] [ 14%] [ 15%] [ 18%] [ 18%] [ 19%] [ 21%] [ 21%] [ 22%] [ 23%] [ 25%] Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir//./THC_generated_THCHalf.cu.o
[ 26%] Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir//./THC_generated_THCBlas.cu.o
[ 27%] Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir//./THC_generated_THCStorageCopy.cu.o
Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir//./THC_generated_THCTensorCopy.cu.o
Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir//./THC_generated_THCTensor.cu.o
Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir//./THC_generated_THCStorage.cu.o
Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir//./THC_generated_THCReduceApplyUtils.cu.o
Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir//./THC_generated_THCTensorMathPairwise.cu.o
Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir//./THC_generated_THCTensorMathMagma.cu.o
Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir//./THC_generated_THCSleep.cu.o
Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir//./THC_generated_THCSortUtils.cu.o
Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir//./THC_generated_THCTensorMath2.cu.o
Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir//./THC_generated_THCTensorMathBlas.cu.o
Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir//./THC_generated_THCTensorMath.cu.o
Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir//./THC_generated_THCTensorMathScan.cu.o
Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir//./THC_generated_THCTensorConv.cu.o
Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir//./THC_generated_THCTensorScatterGather.cu.o
Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir//./THC_generated_THCTensorMathReduce.cu.o
Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir//./THC_generated_THCTensorTypeUtils.cu.o
Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir//./THC_generated_THCTensorMode.cu.o
Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir//./THC_generated_THCTensorIndex.cu.o
Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir//./THC_generated_THCTensorSort.cu.o
Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir//./THC_generated_THCTensorRandom.cu.o
Building NVCC (Device) object lib/THC/CMakeFiles/THC.dir//./THC_generated_THCTensorTopK.cu.o
/home/user/mine/torch/extra/cutorch/lib/THC/generic/THCStorage.cu(11): error: class "thrust::detail::execute_with_allocator<THCThrustAllocator, thrust::system::cuda::detail::execution_policy>" has no member "on"

/home/user/mine/torch/extra/cutorch/lib/THC/generic/THCStorage.cu(9): error: no instance of overloaded function "thrust::fill" matches the argument list
            argument types are: (<error-type>, thrust::device_ptr<unsigned char>, thrust::device_ptr<unsigned char>, unsigned char)

/home/user/mine/torch/extra/cutorch/lib/THC/generic/THCStorage.cu(11): error: class "thrust::detail::execute_with_allocator<THCThrustAllocator, thrust::system::cuda::detail::execution_policy>" has no member "on"

/home/user/mine/torch/extra/cutorch/lib/THC/generic/THCStorage.cu(9): error: no instance of overloaded function "thrust::fill" matches the argument list
            argument types are: (<error-type>, thrust::device_ptr<char>, thrust::device_ptr<char>, char)

/home/user/mine/torch/extra/cutorch/lib/THC/generic/THCStorage.cu(11): error: class "thrust::detail::execute_with_allocator<THCThrustAllocator, thrust::system::cuda::detail::execution_policy>" has no member "on"

/home/user/mine/torch/extra/cutorch/lib/THC/generic/THCStorage.cu(9): error: no instance of overloaded function "thrust::fill" matches the argument list
            argument types are: (<error-type>, thrust::device_ptr<short>, thrust::device_ptr<short>, short)

/home/user/mine/torch/extra/cutorch/lib/THC/generic/THCStorage.cu(11): error: class "thrust::detail::execute_with_allocator<THCThrustAllocator, thrust::system::cuda::detail::execution_policy>" has no member "on"

/home/user/mine/torch/extra/cutorch/lib/THC/generic/THCStorage.cu(9): error: no instance of overloaded function "thrust::fill" matches the argument list
            argument types are: (<error-type>, thrust::device_ptr<int>, thrust::device_ptr<int>, int)

/home/user/mine/torch/extra/cutorch/lib/THC/generic/THCStorage.cu(11): error: class "thrust::detail::execute_with_allocator<THCThrustAllocator, thrust::system::cuda::detail::execution_policy>" has no member "on"

/home/user/mine/torch/extra/cutorch/lib/THC/generic/THCStorage.cu(9): error: no instance of overloaded function "thrust::fill" matches the argument list
            argument types are: (<error-type>, thrust::device_ptr<long>, thrust::device_ptr<long>, long)

/home/user/mine/torch/extra/cutorch/lib/THC/generic/THCStorage.cu(11): error: class "thrust::detail::execute_with_allocator<THCThrustAllocator, thrust::system::cuda::detail::execution_policy>" has no member "on"

/home/user/mine/torch/extra/cutorch/lib/THC/generic/THCStorage.cu(9): error: no instance of overloaded function "thrust::fill" matches the argument list
            argument types are: (<error-type>, thrust::device_ptr<half>, thrust::device_ptr<half>, half)

/home/user/mine/torch/extra/cutorch/lib/THC/generic/THCStorage.cu(11): error: class "thrust::detail::execute_with_allocator<THCThrustAllocator, thrust::system::cuda::detail::execution_policy>" has no member "on"

/home/user/mine/torch/extra/cutorch/lib/THC/generic/THCStorage.cu(9): error: no instance of overloaded function "thrust::fill" matches the argument list
            argument types are: (<error-type>, thrust::device_ptr<float>, thrust::device_ptr<float>, float)

/home/user/mine/torch/extra/cutorch/lib/THC/generic/THCStorage.cu(11): error: class "thrust::detail::execute_with_allocator<THCThrustAllocator, thrust::system::cuda::detail::execution_policy>" has no member "on"

/home/user/mine/torch/extra/cutorch/lib/THC/generic/THCStorage.cu(9): error: no instance of overloaded function "thrust::fill" matches the argument list
            argument types are: (<error-type>, thrust::device_ptr<double>, thrust::device_ptr<double>, double)

/home/user/mine/torch/extra/cutorch/lib/THC/THCHalf.cu(18): error: class "thrust::detail::execute_with_allocator<THCThrustAllocator, thrust::system::cuda::detail::execution_policy>" has no member "on"

/home/user/mine/torch/extra/cutorch/lib/THC/THCHalf.cu(16): error: no instance of overloaded function "thrust::transform" matches the argument list
            argument types are: (<error-type>, float *, float *, half *, __float2halfOp)

/home/user/mine/torch/extra/cutorch/lib/THC/THCHalf.cu(29): error: class "thrust::detail::execute_with_allocator<THCThrustAllocator, thrust::system::cuda::detail::execution_policy>" has no member "on"

/home/user/mine/torch/extra/cutorch/lib/THC/THCHalf.cu(27): error: no instance of overloaded function "thrust::transform" matches the argument list
            argument types are: (<error-type>, half *, half *, float *, __half2floatOp)

4 errors detected in the compilation of "/var/tmp/tmpxft_00005328_00000000-7_THCHalf.cpp1.ii".
16 errors detected in the compilation of "/var/tmp/tmpxft_0000530c_00000000-7_THCStorage.cpp1.ii".
CMake Error at THC_generated_THCHalf.cu.o.cmake:267 (message):
  Error generating file
  /home/user/mine/torch/extra/cutorch/build/lib/THC/CMakeFiles/THC.dir//./THC_generated_THCHalf.cu.o

lib/THC/CMakeFiles/THC.dir/build.make:623: recipe for target 'lib/THC/CMakeFiles/THC.dir/./THC_generated_THCHalf.cu.o' failed
make[2]: *** [lib/THC/CMakeFiles/THC.dir/./THC_generated_THCHalf.cu.o] Error 1
make[2]: *** Waiting for unfinished jobs....
CMake Error at THC_generated_THCStorage.cu.o.cmake:267 (message):
  Error generating file
  /home/user/mine/torch/extra/cutorch/build/lib/THC/CMakeFiles/THC.dir//./THC_generated_THCStorage.cu.o

lib/THC/CMakeFiles/THC.dir/build.make:79: recipe for target 'lib/THC/CMakeFiles/THC.dir/./THC_generated_THCStorage.cu.o' failed
make[2]: *** [lib/THC/CMakeFiles/THC.dir/./THC_generated_THCStorage.cu.o] Error 1
/home/user/mine/torch/extra/cutorch/lib/THC/generic/THCTensorMath.cu(315): error: class "thrust::detail::execute_with_allocator<THCThrustAllocator, thrust::system::cuda::detail::execution_policy>" has no member "on"

There are many more errors like that.
I can't figure out what is wrong, since Debian 8 is supported by the install scripts. I have to say though, /usr/include/thrust/execution_policy.h (official package here) looks somewhat different from the current upstream version.
In any case, it doesn't seem like I can install torch on Debian 8 at this time.
Some more info:
mine@rattle:~/torch$ cat /etc/*release* | head -n 1
PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
mine@rattle:~/torch$ dpkg-query -l | grep -Ei "libthrust|cuda" | awk '{print $2,$3}'
libcuda1:amd64 367.57-2
libcudart7.5:amd64 7.5.18-4
libcudnn5 5.1.3-1+cuda7.5
libcudnn5-dev 5.1.3-1+cuda7.5
libcudnn5-doc 5.1.3-1+cuda7.5
libnvcuvid1:amd64 367.57-2
libnvrtc7.5:amd64 7.5.18-4
libthrust-dev 1.7.0-2
nvidia-cuda-dev 7.5.18-4
nvidia-cuda-doc 8.0.44-3
nvidia-cuda-mps 361.45.18-2
nvidia-cuda-toolkit 7.5.18-4
nvidia-profiler 7.5.18-4

You are using pre release version of CUDA 8. Please install the latest version.
@soumith do you think it is best if we can detect this in the CMake file instead of having to repeatedly answer this question ?

You are using pre release version of CUDA 8.

How can I determine this? Please excuse my ignorance, but I am under the impression that this server has some version of CUDA 7 installed:
mine@rattle:~/torch$ nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2015 NVIDIA Corporation
Built on Tue_Aug_11_14:27:32_CDT_2015
Cuda compilation tools, release 7.5, V7.5.17

That's what the official jessie-backports repo provides:
https://packages.debian.org/jessie-backports/nvidia-cuda-toolkit
See also the list at the end of my original report. So, the server is running "official" debian 8 (backport) packages, which I thought torch supports. I don't think there are offical CUDA 8 packages for Debian 8.

@cshapeshifter ok I misread your error message. There's been a bunch of similar issues with people using a pre-release version of CUDA 8.
But you are using CUDA 7.5 which should work fine, so something else is wrong. Let me check it out further.

@cshapeshifter can you run grep THRUST_VERSION /usr/include/thrust/version.h ?

Certainly:
mine@rattle:~$ grep THRUST_VERSION /usr/include/thrust/version.h
//  THRUST_VERSION % 100 is the sub-minor version
//  THRUST_VERSION / 100 % 1000 is the minor version
//  THRUST_VERSION / 100000 is the major version
/*! \def THRUST_VERSION
 *  \brief The preprocessor macro \p THRUST_VERSION encodes the version
 *         <tt>THRUST_VERSION % 100</tt> is the sub-minor version.
 *         <tt>THRUST_VERSION / 100 % 1000</tt> is the minor version.
 *         <tt>THRUST_VERSION / 100000</tt> is the major version.
#define THRUST_VERSION 100700
#define THRUST_MAJOR_VERSION     (THRUST_VERSION / 100000)
#define THRUST_MINOR_VERSION     (THRUST_VERSION / 100 % 1000)
#define THRUST_SUBMINOR_VERSION  (THRUST_VERSION % 100)

also:
mine@rattle:~$ dpkg-query -S /usr/include/thrust/version.h
libthrust-dev: /usr/include/thrust/version.h

mine@rattle:~$ dpkg -l libthrust-dev | grep ii
ii  libthrust-dev  1.7.0-2      all          Thrust - Parallel Algorithms Library

The package (1.7.0-2): https://packages.debian.org/jessie/libthrust-dev
There's also https://packages.debian.org/jessie-backports/libthrust-dev - I could ask IT to install this newer version (1.8.1-1) instead.

@cshapeshifter That looks like the issue. I think thrust 1.7  is tied to an older version of the CUDA toolkit.  I think 1.8.1 came with CUDA 7.0 but it should work for this particular problem. There may be other compilation bugs that can pop up. Thrust 1.8.2 is the version shipped alongside CUDA 7.5 but it doesn't look like Debian packages that version.

@pavanky  May I ask that is there some easy way?

@D-X-Y you can download cuda and install it to a local path. You don't need sudo privs for that.

Installing libthrust-dev 1.8.1 solves the problem. Feel free to close the issue. I suppose the installer could check for this but I guess an enhancement request should be opened for that if necessary.


clean code

This PR fixes nothing
Use repeat builtin function to repeat some strings
The support for the String.repeat method is:

Captured from CanIUse - JavaScript built-in: String: repeat

Should I add a polyfill?

@alexdima I don't know why it failed and I don't have a Mac to reproduce it, what do you suggest I do?

Thank you, but we don't accept such refactorings PRs due to the risk of the refactoring breaking something and the change not being strictly necessary.


Improve encoding of SMT labels

Discussed with Nik and Assem a way to better encode SMT labels.

This is long done by Nik. Closing.


Pickle error when saving Atom objects

Describe the bug
Pickle step fails when pickling list of atoms. Returns this traceback:
Traceback (most recent call last):
File "/Users/roger/Git/nmr-ase/src/temp.py", line 18, in
pickle.dump(atom_list, f)
RuntimeError: Pickling of "rdkit.Chem.rdchem.Atom" instances is not enabled (http://www.boost.org/libs/python/doc/v2/pickle.html)
To Reproduce
from rdkit import Chem
import pickle

compound_smiles = "CCCCO"
mol = Chem.MolFromSmiles(compound_smiles)
atom_list = []

for atom in mol.GetAtoms():
    atom_list.append(atom)

with open("../data/atoms.pickle", "wb") as f:
    pickle.dump(atom_list, f)

Expected behavior
I expect to save a pickle file containing all atoms.
Screenshots
N/A
Configuration (please complete the following information):

RDKit version: 2022.03.5
OS: [e.g. Ubuntu 20.04]: MacOS Ventura 13.4
Python version (if relevant): 3.10.13
Are you using conda? Yes
If you are using conda, which channel did you install the rdkit from? conda-forge (conda install -c conda-forge rdkit)
If you are not using conda: how did you install the RDKit? N/A

Additional context
None

Atoms simply cannot be pickled by themselves.  You need to pickle the molecule that contains them.  This is why you see the error:
RuntimeError: Pickling of "rdkit.Chem.rdchem.Atom" instances is not enabled

This is a bit non-pythonic but the underlying code is not python so this is as designed.
Working example:
from rdkit import Chem
import pickle

compound_smiles = "CCCCO"
mol = Chem.MolFromSmiles(compound_smiles)
with open("../data/atoms.pickle", "wb") as f:
    pickle.dump(mol, f)

OK thanks for the clarification


Breakdown menu in antimatter list also coming generated events

Hi,
So i assigned the event page type to a test page named "Presentation". Now, with menu, I see this page and all the coming events (which I would like to avoid). Is it a bug ? How can I fifter out the generated events from my menu ?
What I have when I'm on the "Presentation page":

What I have when I click on an event (ie link to given event, http://localhost:8080/le-club/presentation/evt:73b402 and the original content is still as 1st result)):

If I'm on a non event content, rendering is:

Something like this is generally theme specific. I'll add an option in the admin blueprint that hides this from menus automatically but that can be disabled if someone wants it in a menu for some reason.

Hi @kalebheitzman,
Thanks for the reply ; as I just start with Grav, could you tell me what kind of filter I could use to exclude the generated events (not the initial one) from the menu ? A link to the doc should be sufficient

Hi @kalebheitzman,
Thanks for the reply ; as I just start with Grav, could you tell me what kind of filter I could use to exclude the generated events (not the initial one) from the menu ? A link to the doc and the key on which I should filter should be sufficient.
Thanks !

There isn't currently a way to exclude generated events. I'll have to code something for this behavior.

Ok,thanks ! Let me know once I can test it.

Hi @kalebheitzman
I want to display latest events on my home page and I still have the issue. How could I fix the issue or have a workaround ?
Why don't you have the issue when using a collection like for the events or agenda page but when using page.find() we have the issue ?
Thanks,
Nicolas

@nsteinmetz i think this has something to do with the way Im generating events. Instead of polluting the pages collection I'm storing events in a array where each event is duplicated x number of times with corrected dates etc. I'm doing some heavy development with this plugin at the moment and I'll see if I can look into as I go.

I've done some heavy development on the plugin the last couple of months. The way events are processed is completely different now. This may or may not be an issue anymore. I'm going to close the issue, but if it does end up happening again, just open a new issue. Using page functions like .find() and .eval() should work just fine now. Check the templates to see code in use.


Fixed sorting of chart widgets with one dimension active

Fixed the highcharts widget to sort the series data frame to force the x-axis dimension to always be ordered

Coverage increased (+0.006%) to 90.129% when pulling bed38a3234ff9b7f20f950e7d3ba71b54c9188fd on fix_sorting_of_single_dimension_charts into fbfa98fb0a478193e8fee86b22a6f1b97eabb9b4 on master.


show current XTZ balance next to amount when making a proposal

Show XTZ (or FA2) in proposal divided by the total balance of the DAO. Currently one has to go back and check the DAO's current balance when specifying an amount


feat(jsx-one-expression-per-line): add spaceMode option (#241)

Description
Adds the spaceMode option to jsx-one-expression-per-line which uses the HTML   entity instead of JSX {' '}

Linked Issues
#241
Additional context

[!important]
This PR is not ready and requires assistance

There are a few issues:

I wasn't able to generate the types.d.ts file (I couldn't figure out how)
The test is only replacing the text for the first offending source and not the second offending source. I'm not sure why
There's an issue with how this rule parses sources. If you look at the test I added, the first literal has a space preceding the embedded div. When this rule runs, it treats the preceding space as part of the first literal (which doesn't get targeted because it's not a violation) and thus ignores it. For proper fixing, the rule would have to replace that space with   and then add a newline, however, there's no way for me to do that and simply adding   and then a newline creates two spaces. I'm not sure how to resolve this issue

In fact, this is an issue with the rule itself even without these changes as the fix keeps that space and then adds a newline with {' '} as well. (Which, again, is two spaces)

To answer your questions:

You can run npm run update on the project root
That's how rules works, only one change is applied at one time. You could have some basic test for one occurrence (and check the error messages), and then create a new set of tests like https://github.com/eslint-stylistic/eslint-stylistic/blob/59070ae45258046e88bb4bcc36cbd74f86eec9bf/packages/eslint-plugin-plus/rules/indent-binary-ops/indent-binary-ops.test.ts#L31-L55 to test the final result.

@exoRift Are you on windows? I met this error: https://github.com/privatenumber/tsx/issues/345 and I had to use WSL to develop


Use parent() to get  itemView parent on itemFilter, fixes #412

This was done to fix #412. I added a test case that failed before this fix.

Thanks for the fix!


kaggle.json not downloading on windows.

I am trying to download the kaggle.json but as soon as I clicked on Create new API Token, only the green notification is showing and nothing else happened.
I am using windows 10 and chrome browser to download the file in the browser.

If somebody else is going through this on google chrome/mozilla Just do this:
inspect(ctrl+shift+I)>Network and try to check the latest generated after you click on the API button on kaggle website.
the code is looking like this:
{"username":"Your username","key":"2f4997fa1d8e4f56ad8eb7659aaf1c31"}
Paste it in a text and then change the extension from .txt to .json.


服务重启无法注册上，pulsar-manager上无法查看namespaces

pulsar 2.8.0 15:20:16.831 [pulsar-io-4-4] INFO  org.apache.pulsar.broker.lookup.TopicLookupBase - Failed to lookup null for topic persistent://base/message/delay_notify_service_pulsar_topic-partition-6 with error Namespace bundle base/message/0x2aaaaaaa_0x3fffffff is being unloaded
导致在pulsar-manager上无法查看namespaces,所有消费者无法订阅到topic 上，重启broker后就能正常显示，

@sqtce Just want to confirm some details from the last community meeting

the issue happens both on 2.7 and 2.8
list the namespace that can't show the given namespace but when you try to create the namespace again, shows the namespace already exists.
After restarts the broker, the namespaces appears when listing the namespaces
After restarts the broker, the consumer subscribed to the topic successfully.

1，我用的是2.8.0版本
2，当时是通过pulsar-manager去查看namepaces，发现我创建的namepaces不见了，尝试创建同名的namespaces时，提示说namespaces存在
3，重新启动broker后，在pulsar-manager看又能正确显示namespaces名字
4，重新启动broker后，消费者成功订阅topic

The issue had no activity for 30 days, mark with Stale label.

Close as stale. The development of pulsar-manager has been permanently moved to https://github.com/apache/pulsar-manager


refactor: consistent header name case

Description

consistent header name case

Checklist:

[x] Securely signed commits
[] Component(s) with PHPDoc blocks, only if necessary or adds value
[] Unit testing, with >80% coverage
[x] User guide updated
[x] Conforms to style guide

@MGatner Thank you for the review!


Fix links

It seems to be incorrectly changed by 7efe138

@yoichinak : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@mtillman @curtand Could you take a look at this pull request in the public repo?
Thanks.

#sign-off

Thanks @yoichinak and @mtillman

Yes, Thanks @yoichinak for catching this. Sorry I missed it when you originally posted it.