text:
Buzzfeed sso/fix default allowed email domains

Is this a new chart
No
What this PR does / why we need it:
Currently the chart sets the env var DEFAULT_ALLOWED_EMAIL_DOMAINS to emailDomain by default. This is fine if you want to just whitelist a domain. However, when you set allowed_groups in upstream, the default is still present as it has enabled the domains backend. This isn't quite right. It should be set to an empty string, as per this issue https://github.com/buzzfeed/sso/pull/280#issuecomment-584088825.
This change is a bit messy as noted in the values file, but it maintains backwards capability with the previous chart.
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

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

Thanks for the change! It looks good to me, just some small comments regarding the documentation and maybe we can figure out if that alternative go templating pattern for the invalid string is feasible in this case 👍

Thanks for the review @darioblanco ! I am struggling to make this backwards compatible, terse and readable at the same time!

/assign @komljen

/ok-to-test
/lgtm

agreed its a bit clunky, but there's prior art in how the persistence stuff works, so I say go for it

/ok-to-test

authors: darioblanco lachie83 paulczar willejs


text:
[stable/anchore-engine] use capabilities in order to support older in…

…gress api
What this PR does / why we need it:
Make it compatible with older clusters.
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

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

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

This change is

/assign @btodhunter

/lgtm

source: gharchive/pull-request

authors: Btodhunter davidkarlsen

repo: helm/charts

license_type: permissive

license_source: github-api


text:
[incubator/kubeless] Update deprecated Deployment APIs to supported versions

Signed-off-by: Viktor Radnai viktor.radnai@gmail.com

Is this a new chart: No

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

What this PR does / why we need it:
Updates deprecated Kubernetes API usage for Deployment resources: extensions/v1beta1 and apps/v1beta1 replaced with apps/v1. This allows the chart to work on Kubernetes 1.16 or newer.
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

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

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

/assign @tompizmor

@prydonius @tompizmor @sameersbn @carrodher could one of you please look at this? Should be a reasonably trivial change which would only remove compatibility with old K8s versions.

Hi @prydonius @tompizmor @sameersbn @carrodher could one of you please look at this?

Hi @prydonius @tompizmor @sameersbn @carrodher could one of you please look at this? It has now gone stale. Any issues preventing it from getting merged?


text:
[stable/factorio] deprecating chart

Is this a new chart

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

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

fixes #

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

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

https://github.com/helm/charts/issues/24310

authors: mattfarina scottrigby


text:
deprecated PodDisruptionBudget apiversion

@hickeyma  according to your comment, i re-opened a new pull request, please review.

@hickeyma pls review

@mehmetyazicioglu Do you mins rebasing as there are conflicts?

authors: hickeyma mehmetyazicioglu

repo: helm/helm-mapkubeapis


text:
Error: fork/exec /root/.local/share/helm/plugins/helm-push/bin/helm-cm-push: no such file or directory

I have installed push
helm plugin install https://github.com/chartmuseum/helm-push
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /root/.kube/config
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /root/.kube/config
Error: plugin already exists

But my push failed,my chart repository is ChartMuseum
helm cm-push mychart-0.1.0.tgz zqhtest
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /root/.kube/config
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /root/.kube/config
Error: fork/exec /root/.local/share/helm/plugins/helm-push/bin/helm-cm-push: no such file or directory

Output of helm version:
3.9.3
Output of kubectl version:
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
腾讯云

Please file an issue with the plugin maintainer at chartmuseum/helm-push

source: gharchive/issue

authors: ZhangSetSail joejulian

repo: helm/helm


text:
finer grained --wait for ressources to be considered ok

Output of helm version:
version.BuildInfo{Version:"v3.11.1", GitCommit:"293b50c65d4d56187cd4e2f390f0ada46b4c4737", GitTreeState:"clean", GoVersion:"go1.18.10"}

Hello there!
I actually use helm with a lot of crds, and all of them are not that well designed, the current wait argument is not enough to ensure that what you released is actually released correctly, you'll have to make some custom checks with the kube apis, like checking a specific status field to be here, another resource to be created (operator pattern I see you here), etc...
So I was thinkin, why can't helm have at least one of the following solutions?

"--wait-for-ressource-attribute" command line option, where you can check anything you want to be here like
"status.whatever=whatever" (and add multiple of them)
helm annotations to add to your ressources to ensure the current ressource should be considered ok or not, like the following:  annotations:
        helm.sh/resource-check-spec.someattribute: "meh"    # check if spec.someattribute equal "meh"
        helm.sh/resource-check-status.somelist.value: "meh"  # check if one or all the values are equal to "meh"
        ...

ability to check if another resource status is ok before trying to continue with one of the following solution:

with the annotations thing above  + a new annotation like "helm.sh/weight": "5", without the hook thing here, be able to put a weight on any ressources
like with the annations thing above, but only for this purpose, with a specific annotation like:    "wait-for-resource-mynamespace.resourcename": "" # Check if the ressource default status is ok (if there's the annotations things mentionned before, it should be default + custom checks)
    "wait-for-resource-mynamespace.anotherresourcename.spec.someattribute": "meh"  # check it the anotherressource.spec.someattribute is equal to meh before putting this ressource

This would be great to have this feature in helm, for at least 3 reasons:

the helm engine can then use this to have a generic way to handle any ressources lifecycles, whatever it is, making it simpler to implement new helm default ressources checks
the custom ressources would have a way to handle their statuses in a standard way without having to put some jobs to handle the ressource lifecycle for no reason
this would be of great benefit for any tools like argocd, flux, terraform-helm-provider, it would let the helm chart handle the lifecycle of its ressources in a defined way, so you would not be bothered by having to implement custom configurations/checks inside this tools, your helm chart defines the way it should behave, and when it's deployed or not when you're waiting for it to be released.

Hope that's something in the scope of helm, because I'm currently using terraform + argocd right now, and it can be hard to handle stuff like operators, deploying a simple crd can be a hurdle from my point of view, and it would be easier with this feature
Just for information, vault is using annotations for secret injection in pods as an example, so I do think it's doable at some point

Looks fairly well thought out. If you can contribute this feature, please start by writing a helm improvement proposal (hip).
Thanks!

Thanks you for your quick réponse, I'll take some time to write the whole Idea correctly, I think it can be of great use for the helm community, as it would provide more mature/granular ressources state management on release

authors: Diliz joejulian


text:
Cannot connect to tiller using helm v2.9.0: Error: Get http://localhost:8080/api/v1/namespaces/kube-system/configmaps?labelSelector=OWNER%!D(MISSING)TILLER: dial tcp [::1]:8080: connect: connection refused

I have a fresh 1.9.6 Azure AKS cluster (one node). Ran a helm init --upgrade --force-upgrade against it to get it to 2.9.0, admittedly without checking whether there was a tiller on it before. I have set KUBECONFIG to the configuration file of this cluster, and made sure I can connect to it. Everything works, but helm does not, or better helm version works, but apparently nothing else.
I have tried this with helm 2.9.0 (on macOS) and 2.8.2 (on Linux/in Docker), and both behave the same; so this may or may not be an issue with AKS, or with helm, or possibly both. The error messages come from tiller, so that's why I file an issue here:
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.3", GitCommit:"d2835416544f298c919e2ead3be3d0864b52323b", GitTreeState:"clean", BuildDate:"2018-02-09T21:51:54Z", GoVersion:"go1.9.4", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.6", GitCommit:"9f8ebd171479bec0ada837d7ee641dec2f8c6dd1", GitTreeState:"clean", BuildDate:"2018-03-21T15:13:31Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

$ helm version
Client: &version.Version{SemVer:"v2.9.0", GitCommit:"f6025bb9ee7daf9fee0026541c90a6f557a3e0bc", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.0", GitCommit:"f6025bb9ee7daf9fee0026541c90a6f557a3e0bc", GitTreeState:"clean"}

$ helm ls
Error: Get http://localhost:8080/api/v1/namespaces/kube-system/configmaps?labelSelector=OWNER%!D(MISSING)TILLER: dial tcp [::1]:8080: connect: connection refused

Checking logs:
$ kubectl logs -n kube-system tiller-deploy-f7bd48bf-tfk8p
[main] 2018/04/27 14:26:58 Starting Tiller v2.9.0 (tls=false)
[main] 2018/04/27 14:26:58 GRPC listening on :44134
[main] 2018/04/27 14:26:58 Probes listening on :44135
[main] 2018/04/27 14:26:58 Storage driver is ConfigMap
[main] 2018/04/27 14:26:58 Max history per release is 0
[storage] 2018/04/27 14:27:36 listing all releases with filter
[storage/driver] 2018/04/27 14:27:36 list: failed to list: Get http://localhost:8080/api/v1/namespaces/kube-system/configmaps?labelSelector=OWNER%3DTILLER: dial tcp [::1]:8080: connect: connection refused

And the env vars:
$ kubectl exec -n kube-system tiller-deploy-f7bd48bf-tfk8p -- env
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOSTNAME=tiller-deploy-f7bd48bf-tfk8p
TILLER_NAMESPACE=kube-system
TILLER_HISTORY_MAX=0
KUBERNETES_DASHBOARD_SERVICE_HOST=10.0.88.104
KUBERNETES_DASHBOARD_SERVICE_PORT=80
KUBERNETES_DASHBOARD_PORT=tcp://10.0.88.104:80
KUBE_DNS_PORT_53_UDP_ADDR=10.0.0.10
KUBERNETES_SERVICE_PORT_HTTPS=443
HEAPSTER_SERVICE_HOST=10.0.52.123
HEAPSTER_PORT_80_TCP_ADDR=10.0.52.123
KUBE_DNS_PORT=udp://10.0.0.10:53
KUBE_DNS_PORT_53_TCP=tcp://10.0.0.10:53
TILLER_DEPLOY_PORT_44134_TCP=tcp://10.0.239.195:44134
KUBE_DNS_SERVICE_PORT=53
KUBE_DNS_PORT_53_UDP=udp://10.0.0.10:53
KUBERNETES_DASHBOARD_PORT_80_TCP_ADDR=10.0.88.104
KUBERNETES_SERVICE_PORT=443
HEAPSTER_SERVICE_PORT=80
HEAPSTER_PORT_80_TCP_PORT=80
KUBE_DNS_SERVICE_HOST=10.0.0.10
KUBE_DNS_PORT_53_TCP_PROTO=tcp
TILLER_DEPLOY_PORT_44134_TCP_ADDR=10.0.239.195
TILLER_DEPLOY_PORT_44134_TCP_PORT=44134
KUBERNETES_PORT_443_TCP=tcp://10.0.0.1:443
HEAPSTER_PORT_80_TCP_PROTO=tcp
KUBE_DNS_SERVICE_PORT_DNS=53
KUBE_DNS_PORT_53_UDP_PORT=53
KUBE_DNS_PORT_53_TCP_ADDR=10.0.0.10
TILLER_DEPLOY_PORT_44134_TCP_PROTO=tcp
KUBERNETES_PORT_443_TCP_PROTO=tcp
KUBERNETES_PORT_443_TCP_PORT=443
HEAPSTER_PORT=tcp://10.0.52.123:80
HEAPSTER_PORT_80_TCP=tcp://10.0.52.123:80
KUBE_DNS_PORT_53_TCP_PORT=53
KUBERNETES_DASHBOARD_PORT_80_TCP=tcp://10.0.88.104:80
KUBERNETES_DASHBOARD_PORT_80_TCP_PORT=80
TILLER_DEPLOY_PORT=tcp://10.0.239.195:44134
TILLER_DEPLOY_SERVICE_PORT_TILLER=44134
KUBERNETES_SERVICE_HOST=10.0.0.1
KUBE_DNS_SERVICE_PORT_DNS_TCP=53
KUBERNETES_DASHBOARD_PORT_80_TCP_PROTO=tcp
TILLER_DEPLOY_SERVICE_PORT=44134
KUBERNETES_PORT=tcp://10.0.0.1:443
KUBERNETES_PORT_443_TCP_ADDR=10.0.0.1
KUBE_DNS_PORT_53_UDP_PROTO=udp
TILLER_DEPLOY_SERVICE_HOST=10.0.239.195
HOME=/tmp

Ideas? This felt like a very vanilla use case.

According to the code, if no service account is provided in helm init then it does not auto-mount the service account token. https://github.com/kubernetes/helm/blob/4d519a741dd43f8f0c175228dee9e9df951a7c5c/cmd/helm/installer/install.go#L179
Can you try again with v2.8.2 and see if that works as described? https://github.com/kubernetes/helm/pull/3784 was a recent 2.9 feature so it could be a regression.

We're running into this same issue as well on a kops launched kubernetes (1.9.7) cluster on AWS , but it was working fine with helm 2.8.2

another workaround for the time being:
helm init --service-account default

If you would be so kind as to test #3990, that would be appreciated. Seems like there was a regression in 2.9.

alternative PR: #3991

If you would be so kind as to test #3990, that would be appreciated. Seems like there was a regression in 2.9.

I will try to do that, but I haven't yet built helm myself, so I can't promise it will work out directly - or are there binaries somewhere?

@DonMartin76 because the patch has been merged into master you can test following the "From Canary" section in the docs. :)

the issue can be fixed just by exec
kubectl -n kube-system patch deployment tiller-deploy -p '{"spec": {"template": {"spec": {"automountServiceAccountToken": true}}}}'

It's also been fixed in 2.9.1. :)

error: failed to create serviceaccount: Post "http://localhost:8080/api/v1/namespaces/kube-system/serviceaccounts?fieldManager=kubectl-create": dial tcp 127.0.0.1:8080: connect: connection refused

authors: Chili-Man DonMartin76 bacongobbler gdville huangyuqi


text:
rendered manifests contain a resource that already exists

i have a chart, which will delete secret "xxx" that already exists in k8s , and deploy my own secret "xxx" to k8s, using helm hook  "helm.sh/hook": "pre-install".  it worked in helm2 ,bu get error in helm3 .
is it by design, or there is something I missed?

Hi @ruanjianxuetu. I transferred this issue to helm/helm. Please file bug reports over there in the future. helm/community is for discussions around high-level org things like mailing lists, governance, communication, meetings, etc.
When opening a ticket, we also ask that you provide an example which can be used to reproduce the issue on our end. Please provide an example. Thanks.

At first glance however, yes this does look to be by design. If your chart is attempting to install a resource that already exists in the cluster, Helm will not "commandeer" that resource, and instead returns an error.

thanks for your reply.
here is the situation I met. the pre-existing secret is the configfile of alertmanager, which is maintained by our paas team. I need to customize the config without manual intervention.  If the pre-install hook can not work under this situation, do you have any suggestion what I can do

Sounds like you're looking for a tool that provides configuration management. The tooling and use cases are different than a package manager. Something like terraform might be helpful here. Helm is meant to be used as a tool to package your software and deploy it to Kubernetes. It is not intended for use to manage resources managed by another "package" or maintained by another piece of software.

authors: bacongobbler ruanjianxuetu


text:
Fix SIGSEGV when storage driver returns nil error (#3625)

This addresses #3625 where tiller segfaults in uniqName -- the check for an existing name assumes that the storage driver's Get function always returns a valid error type, but for example the cfgmaps driver (default) often returns a nil

A note on testing ... this is a hard one to test for; the only existing test that might trigger this is https://github.com/helm/helm/blob/b4b693c3168421c8cd7165e2fb5eb2233adefa6a/pkg/tiller/release_server_test.go#L357 and that would only trigger the issue if moniker chose the name happy-panda; with the current version of moniker having 243 animals and 390 descriptors, that's a 1 in 94,770 chance (0.001%) of triggering the bug during testing.
I could update this PR with a bigger rewrite that allows the use of something that satisfies the moniker interface in order to increase the test coverage, if that's considered worthwhile.

PR updated to add a test which, based on the original code causes a segfault and confirms that the fix is valid

hey! looks like the commit history is mangled. Mind taking a look into fixing that?

Yeah, whoops ... sorry. Fixing that now

authors: bacongobbler nonspecialist


text:
Cleanup Specta integration

Changes:

Don't depend on tauri-specta, specta is enough and means this crate is compatible with any Specta compatible library (rspc, taurpc, Tauri Specta)
cfg attribute on module not export. This is so when the Specta feature isn't enabled the crate doesn't try and import Specta.
Remove pub use specta_derives::*. Implementations don't need to be publically exposed to work.
Import rest of crate into specta_derives module so it can refer to the crates types.

Thank you and sorry for the slow review time!
I will resume development on this project very soon.


text:
Having problems getting python-decouple to work on AWS.

not sure how to fix this problem:
https://stackoverflow.com/questions/60733143/how-to-get-python-decouple-to-work-on-a-live-server

python-decouple seems to work well when the project is run locally, but when pulled to my AWS Ubuntu server and ran, I get "decouple.UndefinedValueError: SECRET_KEY not found. Declare it as envvar or define a default value."

The problem is that (1) you don't have your server environment variables set and (2) you don't have a .env to work as a fallback.
It seems you're not using the library correctly.

I decided to use the AWS parameters instead But thank you for your quick reply.

repo: henriquebastos/python-decouple

license: mit

license_source: bigquery


text:
add import key option to UI

This is a possible, straightforward approach to add existing private keys as discussed in #54 #34 and #7
There are other potential approaches though which may be incompatible with this one but there seemed to be some interest in it so I decided to submit this as a PR. Up to you to decide what to do with it ;)
You might want to test it some more first, but it should just add and save the keys in exactly the same way as when they're generated.

Thanks so much Greg! Can you add screenshots to this PR?

Sure, I'm away from my dev machine now but I'll upload some tonight :)

Uploaded two screenshots and a linux and mac build here. Don't mind the description and date there, that's just because I edited an existing release instead of making a new one :)

The code looks good, but I fear the additions to the UI will be too confusing. I will make some designs when I get a chance and merge it with your code. How does that sound?

Sounds good to me. And I think you're right about the UI, there's definitely a better way to do this.

Working on testing this locally!

This view could do with some improving

Is there any blockers on this or is it still being worked on?

This could be merged, I'd just like if the UI problem that I mentioned was fixed.

I actually agree that it could be implemented in a better-looking way, especially considering this app looks so nice as it is. I'm really not a designer though, not sure if I can come up with a better look..

I'm not either, but we could have a flow of initial screen when user has no key
Options to generate key or import key, and then goes to a specific UI for each.

How about something a little more like this? It's missing some polish and animation jazz but you're right I like the splash screen much better too, compared to switching the buttons over.

Oops, I was playing with a mobile app yesterday and must have accidentally closed this, my bad.

Any word on this?

authors: Tasemu casesandberg frankcash greg-js henryboldi

repo: henryboldi/felony


text:
cubied doesn't reap zombies

Hi Sebastien,
When trying to use cubied to manage a container used for running a batch system worker node, I find that I get a huge number of zombie processes.  This seems to be because cubied, as PID 1, isn't  reaping orphaned processes.  It's a bit of a problem for a long-running container.
Best,
Peter

it is, indeed, an issue.
are the orphaned processes originating from the "master" command or from the extra "daemon-like" commands?

They're at least originating from the initial processes (those described in the cubie.d configuration files).  For example, I start Condor daemons (running condor_master) and after every job I have lingering condor_starter and sh processes.  I'm not sure whether they result from the "final" processes.

I believe I fixed it (aplogies it took so long)
feel free to re-open if you disagree :)
(I am in the process of updating the hepsw/docks containers)

authors: ponyisi sbinet

repo: hepsw/cubie


text:
Update 03-deployment.yaml

Updated environment variable to be the correct variable name.
Fixes #59
Signed-off-by: Nicholas Lane nicholas@heptio.com

@soggiest could you sign the commit? Thanks!

authors: soggiest stevesloka

repo: heptiolabs/gangway


text:
Improve UI of sign up page

Describe the feature
Improving Sign up page with adding several effects to look the UI better.
Add ScreenShots
Add hover effects to the labels and will add separate header to make the UI look impressive.
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'24 contributor
[X] I want to work on this issue

I agree to follow this project's Code of Conduct
I'm a GSSoC'24 contributor
Assign this issue to me

I agree to follow this project's Code of Conduct
I'm a GSSoC'24 contributor
I want to work on this issue
Please assign this issue to me

repo: hereisSwapnil/ExamTime

license: MIT


text:
docker-compose fails installing jdk

Hi,
docker-compose is failing loading the JDK 7u80 with the following error. Is there any simple solution?
$$:~/docker_open5gs$ docker-compose up
Building fhoss
Step 1/13 : FROM ubuntu:focal
---> 14be0685b768
Step 2/13 : ENV DEBIAN_FRONTEND=noninteractive
---> Using cache
---> 35e29103bb15
Step 3/13 : RUN apt-get update &&       apt-get -y install git vim wget subversion mysql-server
---> Using cache
---> f49138fb442e
Step 4/13 : RUN mkdir -p  /usr/lib/jvm/ &&      cd / && wget https://files-cdn.liferay.com/mirrors/download.oracle.com/otn-pub/java/jdk/7u80-b15/jdk-7u80-linux-x64.tar.gz &&   tar -zxf /jdk-7u80-linux-x64.tar.gz -C /usr/lib/jvm/ &&      update-alternatives --install /usr/bin/java java /usr/lib/jvm/jdk1.7.0_80/bin/java 100 &&       update-alternatives --install /usr/bin/javac javac /usr/lib/jvm/jdk1.7.0_80/bin/javac 100
---> Running in b3fc57b68979
--2023-07-31 16:02:03--  https://files-cdn.liferay.com/mirrors/download.oracle.com/otn-pub/java/jdk/7u80-b15/jdk-7u80-linux-x64.tar.gz
Resolving files-cdn.liferay.com (files-cdn.liferay.com)... 104.18.29.95, 104.18.28.95, 2606:4700::6812:1c5f, ...
Connecting to files-cdn.liferay.com (files-cdn.liferay.com)|104.18.29.95|:443... connected.
HTTP request sent, awaiting response... 500 Internal Server Error
2023-07-31 16:02:04 ERROR 500: Internal Server Error.
ERROR: Service 'fhoss' failed to build: The command '/bin/sh -c mkdir -p  /usr/lib/jvm/ &&      cd / && wget https://files-cdn.liferay.com/mirrors/download.oracle.com/otn-pub/java/jdk/7u80-b15/jdk-7u80-linux-x64.tar.gz &&        tar -zxf /jdk-7u80-linux-x64.tar.gz -C /usr/lib/jvm/ &&         update-alternatives --install /usr/bin/java java /usr/lib/jvm/jdk1.7.0_80/bin/java 100 &&       update-alternatives --install /usr/bin/javac javac /usr/lib/jvm/jdk1.7.0_80/bin/javac 100' returned a non-zero code: 8
Thank you,
Ravi

Is there any simple solution?

I would suggest to use open5gs_hss_cx branch for now until the above issue is resolved

All instance of FhoSS has now been removed from this repo and moved to pyHSS so this should not be an issue anymore. Please re-open the issue with pcaps and logs if you still face issue.

Thank you.

authors: herlesupreeth psravikiran


text:
Use current rust toolchain

Closes https://github.com/hermitcore/runh/issues/66.

bors r+

repo: hermitcore/runh


text:
Fix JSON payload handling for requests with payload

The Heroku API client actually handles encoding of the body for us, so
when we were passing the unparsed input string directly, that was
being sent as a JSON string containing the full JSON payload. That
is, instead of sending the bytes
{ "foo": "bar" }
we were sending the bytes
"{\"foo\": \"bar\" }"
and while technically this is valid JSON, it is not what the user
intended nor what the endpoint expects.
Instead, we parse the input and pass the resulting object to the
request, letting the client handle re-encoding for us.

thanks!

Thanks! I was caught by this one too 👍

authors: dmcinnes rwz uhoh-itsmaciek

repo: heroku/heroku-api-plugin


text:
Deprecated or unsupported version of go (go1.6.3)

remote:  !!    Deprecated or unsupported version of go (go1.6.3)
remote:  !!    See https://devcenter.heroku.com/articles/go-support#go-versions for supported version information.

Sorry about that. Should be fixed in 91c7eeae6c4e89ea08be0c11b42580594b1f5153

repo: heroku/heroku-buildpack-go


text:
🛑 Software Center - Test 1 is down

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

HTTP code: 0
Response time: 0 ms

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

repo: herrphon/upptime


text:
🛑 Auth-Bridge - Test 1 is down

In 9dd74be, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

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


text:
🛑 Auth-Bridge - Test 1 is down

In 9da1d08, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

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


text:
🛑 Software Center - Test 1 is down

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

HTTP code: 0
Response time: 0 ms

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


text:
🛑 Auth-Bridge - Test 1 is down

In 8ab5f9e, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

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


text:
🛑 Software Center - Test 1 is down

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

HTTP code: 0
Response time: 0 ms

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


text:
🛑 Auth-Bridge - Test 1 is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in 8003922 after 29 minutes.


text:
🛑 Auth-Bridge - Test 1 is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in b450984 after 41 minutes.


text:
🛑 Software Center - Test 1 is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in fb07b05 after 18 minutes.


text:
🛑 Software Center - Test 1 is down

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

HTTP code: 0
Response time: 0 ms

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


text:
🛑 Auth-Bridge - Test 1 is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in b0cb5cf after 40 minutes.


text:
🛑 Auth-Bridge - Test 1 is down

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

HTTP code: 0
Response time: 0 ms

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


text:
🛑 Software Center - Test 1 is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in d109fbf after 26 minutes.


text:
🛑 Auth-Bridge - Test 1 is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in 263ae86 after 22 minutes.


text:
🛑 Software Center - Test 1 is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 1bff302 after 34 minutes.


text:
🛑 Auth-Bridge - Test 1 is down

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

HTTP code: 0
Response time: 0 ms

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


text:
🛑 Auth-Bridge - Test 1 is down

In 23347d2, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

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


text:
🛑 Auth-Bridge - Test 1 is down

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

HTTP code: 0
Response time: 0 ms

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


text:
🛑 Software Center - Test 1 is down

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

HTTP code: 0
Response time: 0 ms

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


text:
Pinch to Zoom

Add Pinch to Zoom on Pictures shown

See Release 2.1.4

repo: hertleinj/image-killer


text:
optimize: add example

What type of PR is this?
optimize

What this PR does / why we need it (English/Chinese):
add example for keyauth

Which issue(s) this PR fixes:

#3

LGTM

repo: hertz-contrib/keyauth


text:
🛑 HedgeDoc is down

In dc5b358, HedgeDoc ($HEDGEDOC_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: HedgeDoc is back up in 3ba107f after 1 hour, 48 minutes.


text:
Default values in schema should make parameters optional

Description
When an openapi-specification has parameters with default values it should generate those as optional.
Generated from json below
export type $OpenApiTs = {
 '/api/v1/reports/': {
   get: {
     req: {
       limit: number;
       offset: number;
     };
     res: {
       /**
        * Success
        */
       200: any;
     };
   };
 };
};

Expected
export type $OpenApiTs = {
  '/api/v1/reports/': {
    get: {
      req: {
        limit?: number;
        offset?: number;
      };
      res: {
        /**
         * Success
         */
        200: any;
      };
    };
  };
};

OpenAPI specification (optional)
{
  "openapi": "3.0.1",
  "info": {
    "version": "1.0"
  },
  "paths": {
    "/api/v1/reports/": {
      "get": {
        "parameters": [
          {
            "name": "limit",
            "in": "query",
            "required": true,
            "schema": {
              "type": "integer",
              "format": "int32",
              "default": 50
            }
          },
          {
            "name": "offset",
            "in": "query",
            "required": true,
            "schema": {
              "type": "integer",
              "format": "int32",
              "default": 0
            }
          }
        ],
        "responses": {
          "200": {
            "description": "Success"
          }
        }
      }
    }
  }
}

Configuration
openapi-ts -i ./openapispec.json -o src/openapi-generated --name BffClient --postfixServices Api --schemas false
System information (optional)
No response

@karmats i believe this was removed because the default value is something the server should be setting if one is not provided. Cc @mrlubos as this change was made by him.

Yeah. @karmats can you explain why would a client need to set default value? Default means if no value is provided, that's what will be used by the server. In other words, whether client provides default value or not, it has no impact on the server

Thanks for the fast replies!
I want it so I don't need to type parameters that will use the default anyway. Is it possible to modify the typescript interfaces somehow and make parameters with a default value optional?

@karmats those fields should be optional. Are they showing as required? Can you provide generate model related to that endpoint?

Not currently as we removed it, but I want to poke at that statement. Why do you need to type parameters with default values? The implication is they're optional, so it's fine if you omit them

You are correct, setting them has no effect! I have updated the title and description to better reflect my problem

@karmats thanks. I will take a look into fixing this.

It's because you're using required @karmats. OpenAPI spec defines parameters with required as required, and setting default value on them has no effect. If a value isn't required, don't set the field. If it is, it doesn't need a default. Those two are mutually exclusive

It's because you're using required @karmats. OpenAPI spec defines parameters with required as required, and setting default value on them has no effect. If a value isn't required, don't set the field. If it is, it doesn't need a default. Those two are mutually exclusive

That makes sense :)
I will close this issue, but do you have any suggestion for my use case:
I have a header-parameter that is required for every request and will always have the same value. I guess an interceptor/middleware can be used for this, but is it possible to change the generated typescript request to make that parameter optional (since it is set in the middleware)?

@karmats I'd say make the header optional in OpenAPI spec and handle validation on your end. I don't really know an API where headers would be required. Even if you need Authorization headers because every endpoint is protected, those aren't required in the spec. Same with x-* headers that might be required depending on resource configuration. Dealing with this logic through TypeScript would be a nightmare, if it's even possible, since your interceptor might have conditional logic and not always set the header.

@karmats I am going to close this issue. If you run into any other issues or have a feature you think it useful, please create a new issue!

@karmats I'd say make the header optional in OpenAPI spec and handle validation on your end. I don't really know an API where headers would be required. Even if you need Authorization headers because every endpoint is protected, those aren't required in the spec. Same with x-* headers that might be required depending on resource configuration. Dealing with this logic through TypeScript would be a nightmare, if it's even possible, since your interceptor might have conditional logic and not always set the header.

We use Duende Identityserver and their BFF-framework for our backend. They recommend setting a custom header for every request to protect against CSRF-attacks. Our options are to either not set this header, which makes our application less secure, or to include the header for every endpoint-request.
Since we've used openapi-typescript-codegen before which set the default parameter values for every request and made those parameters optional, this was never an issue for us. That project is, as you know, deprecated and replaced by this one and we now have to set this X-CSRF-header for all our requests, which wasn't something I wished to do.
Your points are valid, but even the Swagger UI (that I see as an interface for an API-call) prefills the request parameters with the default values even if the server sets them.
Anyway, thanks for your time and comments regarding this!

@karmats is it a complete blocker for you or is any of what we discussed a viable workaround?

My point is only about requiring this header which complicates things. I am not clear how making it optional in types and then sending it via interceptor would produce a different outcome – the end result should still be the same, no?

I get your points @mrlubos and they sure are valid.
The end result (requests sent with the required header) would be the same, but I wouldn't have to type it for every endpoint-request with a request interceptor.
I can't set the header as optional since the framework does that for us, and thereby out of our control. Even if we could I'm not sure that we would, because that would mean we accept requests without the header and that makes our applications more insecure.
This is not a blocker for us. It sure would be helpful but setting the parameter for all the requests is something we can live with.

@karmats That's good to hear. So it sounds like TypeScript is a bigger problem here than any security concepts. I'd need to see your application, but you should be able to create a wrapper around all your endpoints and use that instead of the generated services. All it would do is pass arguments forward and add that required header. Note that this might not be possible today, but that approach should satisfy everyone – your API, TypeScript, and our package architecture. You should be able to do this once we have the client packages out!

Sounds good! Looking forward to it 🥳

Guys, I have a schema like this:
`
type: object
properties:
huntingSkill:
type: string
description: The measured skill for hunting
default: lazy
enum:
- clueless
- lazy
- adventurous
- aggressive
required:

nothing
`

Why the typescript generates the huntingSkill as required?
Note: I'm using the typescypt client and, I should not be forced to add the value of huntingSkill, as the behaviour that I wan't is that if omited, then server side it sets the lazy as default.
Best regards,
Filipe

Hey @filipeandre, are you sure this is the right repository for the issue? 🧐

authors: filipeandre jordanshatford karmats mrlubos

repo: hey-api/openapi-ts


text:
Added Image Background Selector

needs fix look into it please

Has conflicts

Has conflicts

i made the pr weeks ago, have you updated your env?
I'll update the branch though

I have updated the env files and added it in .gitignore, you can fork the project again and copy paste the logic code

@heycalebszn check it out

Merges try it out and see if it works as expected

authors: ImArnoldDCODES heycalebszn

repo: heycalebszn/bannerly


text:
Review TeamCreation.jsx and TeamInvitationsWidget.jsx

Files to Review
TeamCreation.jsx
TeamInvitationsWidget.jsx
Checklists
Architecture
Design
JS
React
Testing
Due Date
Monday, October 9, 9:00 AM
For more information
The review process is documented at: http://courses.ics.hawaii.edu/ics414f23/morea/review/reading-idpm-review.html

TeamCreation.jsx
DE-03: L60, 76, 81, 124, 132, 136, 139, 144
JS-04: L51
JS-05: L151-153
TeamInvitationsWidget.jsx
JS-05: L63, 75, 78, 90, 93, 105, 108, 120, 123, 151-154
RE-06: 180-194 define constants in withTracker()
RE-09
RE-10

TeamCreation.jsx
JS-04 & RE-09: L29
JS-05: L151,152,153
JS-06: L60, 76, 81, 124, 132, 136, 139, 144
#TeamInvitationsWidget.jsx
JS-04 & RE-09: L51
JS-05: L75, 90, 105, 120

outcome
TeamCreation.jsx

remove logs
lodash
bootstrap instead of semantic ui
use function component

useRef

use checkbox instead of radio
use useTracker instead of withTracker
add a test

TeamInvitationsWidget.jsx

remove unused variables

lodash

bootstrap

function component

useTracker

add collection subscriptions and return a field like "ready"

test

getSomething functions could use a filter instead of

const data = [];
...js
return data;

TeamCreation.jsx
DE-05: L60, L76, L108, L124, L139, L144
JS-04 L84 & L92
JS-05: L151-153
TeamInvitationsWidget.jsx
RE-09
JS-05: L75, L90, L105, L120

authors: Rubegen km584 rhlai winstonco


text:
[ 功能建议 ] 建议在平台上加入mongodb查询模块

目前环境mongodb的应用还是很普及的，运用也非常多，希望可以在sql查询模块中 加入mongodb的查询支持。谢谢。

感谢你的建议，这是我们的开发者指南 https://github.com/hhyo/Archery/wiki/开发者指南 ，接入新数据库类型是比较简单的，只需要按文档做出对应的调整即可。
如果有兴趣可以直接对照修改提出pull request， 只要单元测试全过，覆盖率达标，没有大的逻辑问题就会接受。

按照开发者文档加入了mongo模块,用2周前的老版本可以使用. 这两天更新了新版本后,sql查询--在线查询不显示mongo数据库,是什么情况?

新版本中 /opt/archery/sql/templates/sqlquery.html 中的
{% for instance in instances %}
{% if instance.db_type == 'mongo' %}
{{ instance.instance_name }}
{% endif %}
{% endfor %}

没地方加了.

新版本中 /opt/archery/sql/templates/sqlquery.html 中的
{% for instance in instances %}
{% if instance.db_type == 'mongo' %}
{{ instance.instance_name }}
{% endif %}
{% endfor %}
没地方加了.

sqlquery.html#L27追加
<optgroup id="optgroup-mongodb" label="MongoDB"></optgroup>

sqlquery.html#L871追加
$("#optgroup-mongodb").empty();

sqlquery.html#L884追加
else if (result[i]['db_type'] === 'mongodb') {
                                $("#optgroup-mongodb").append(instance);
                            }

感谢,已解决.

@jackielulu17325 方便的话提个pr吧

@LeoQuote 刚实现了在线查询功能,还没怎么测试,代码写的不好,等过两天测测再给提交上来吧..

@jackielulu17325 好的，期待

已合并至master , 请等待下次 release 更新后即可使用.

repo: hhyo/Archery


text:
HHH-12968 (5.3)

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

Closing PR because it was created to merge to wrong branch.

repo: hibernate/hibernate-orm


text:
Improve ListresultConsumer duplication check method performance

just an attempt to address the potential perf issue mentioned in the https://github.com/hibernate/hibernate-orm/pull/4924 discussion.

my concern is the impact of the new IdentityHashMap for small/medium results where the original solution had not real perf issues

my concern is the impact of the new IdentityHashMap for small/medium results where the original solution had not real perf issues

We could try to allocate the IdentityHashMap only when exceeding a certain row count threshold, but not sure if that makes things a lot better.
I think, if we pass through a maxResults estimate into org.hibernate.sql.results.spi.ResultsConsumer#consume, we could reduce the possible negative effects to only HQL/Criteria queries that select entities where we have no good estimate. In the end, I think we simply need guidance from the user. The user should be able to provide a hint that says "don't deduplicate", in which case we can avoid the IdentityHashMap.

IMO conceptually we'd need a https://en.wikipedia.org/wiki/Bloom_filter
Not keen to add a dependency though - could we check how close we get approximating it via an identity hashmap ?

IMO conceptually we'd need a https://en.wikipedia.org/wiki/Bloom_filter
Not keen to add a dependency though - could we check how close we get approximating it via an identity hashmap ?

Yeah, either add a dependency or implement/integrate this ourselves in hibernate-core. It's not trivial to implement this, but I think it would be worth it to add a custom implementation. Standard Bloom filters AFAIU need a fixed size, but since we keep the data around, we could grow the bit set on-demand similar to what a hash table does, but use a lot less memory (64 times memory savings i.e. for 1M elements we'd use ~2KB instead of ~1MB). Growing a bit set also consumes a lot less memory, though rehashing is still necessary.

authors: Sanne beikov dreab8


text:
HSEARCH-4204 Expose the Elasticsearch index names in the metamodel API

https://hibernate.atlassian.net/browse/HSEARCH-4204

Feel free to merge when they are solved. And don't forget to apply the same changes to the backport :)

repo: hibernate/hibernate-search


text:
🛑 kiwifarms.hk is down

In 588e5b0, kiwifarms.hk (https://kiwifarms.hk) was down:

HTTP code: 0
Response time: 0 ms

Resolved: kiwifarms.hk is back up in 7923f57 after 4 minutes.

repo: hickoryhouse/kf


text:
🛑 kiwifarms.st is down

In d213939, kiwifarms.st (https://kiwifarms.st) was down:

HTTP code: 500
Response time: 1238 ms

Resolved: kiwifarms.st is back up in b855f53 after 5 minutes.


text:
🛑 kiwifarms.pl is down

In 6a3e2ae, kiwifarms.pl (https://kiwifarms.pl) was down:

HTTP code: 502
Response time: 1157 ms

Resolved: kiwifarms.pl is back up in 99ee736 after 24 days, 23 hours, 38 minutes.


text:
Idea/request: Syslog compatibility

First, thanks for this awesome library!
In a similar manner as the file logging functionality, it would be really useful to have an optional syslog "logger" which sends all log messages in Syslog format over UDP.

Thanks for the suggestion. The syslog format, especially the log format that requires timestamps, is not the same on all platforms, so it would be difficult for the library to support it on all platforms.
Having them create it themselves in a custom format would be better.

Thanks for getting back on this topic. I was under the impression that the syslog format was standardized according to https://datatracker.ietf.org/doc/html/rfc5424 but I might very well be naive here.
Regardless, would you care to elaborate on your last sentenser with regards to a custom format. Do you mean there is already a preferred way of extending DebugLog with another custom logging format/transport?

Yes, please refer https://github.com/hideakitai/DebugLog?tab=readme-ov-file#log-preamble-control

Ah, yes, thanks. That makes perfect sense for the formatting part. But I am still unsure about how to use a custom transport (or sink if you will) for all log messages. Right now, I believe there are two implementations, to a serial port and to a file. How would I go about pushing the log messages over UDP instead/also?

You can attach any Stream* class to output. But I should rename/add LOG_ATTCH_STREAM().
    LOG_ATTACH_SERIAL(&Serial2);
    LOG_ATTACH_SERIAL(&your_udp_client);
    LOG_ATTACH_SERIAL(&your_tcp_client);

added
LOG_ATTACH_STREAM(your_udp_client);

Oh, that makes sense now that I see your examples, awesome! And, yes, the additional "overload" introduced in 0.8.4 makes it a lot clearer 👍
Feel free to close this issue and thanks for your quick and helpful response!

repo: hideakitai/DebugLog


text:
🛑 NGINX is down

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

HTTP code: 0
Response time: 0 ms

Resolved: NGINX is back up in 8ec6d20.


text:
Finger Paint App

Add fingerPaint App code and resources.
This current version still needs to be updated to work outside of the hifi repo.
In order for the fingerPaint App to run successfully, there's a dependency with engine code that is currently under a merge with hifi:master  PR.

Engine side PR has been merged. We know there is an issue with the sphere not always rezzing when changing hands but would like to merge this anyway and apply a bugfix for the QA fail on https://github.com/highfidelity/hifi/pull/10702

I feel this is a PASS as the issues seen are minor and IMO not blockers.
Used this link to test along with five other users.
https://rawgit.com/CraftsmanMG/hifi-content/0fbfdb9689479263f97c387bc009a6c6196922ad/Marketplace/fingerPaint/fingerPaint.js
All features were tested and seemed to work fine for all users. We had a large group working together. We even tried co-ordinating our strokes to closely follow the leader and this worked really well. Everyone  enjoyed using finger paint.
Everyone would be happier with a larger number of undos.
Had a request for a hifi logo brush.
We could identify each other's work when declaring what we would draw.
Avatar scaling with hand controllers is blocked when finger paint is active.
Undo: Occasionally when undoing a delete operation the user can see the restored stroke but others do not see it. We had this occur with three observers.
Hue Animation: Occasionally strokes do not animate. The failed strokes are observed by all.
Mouse mode: Does not always work despite reloading scripts.
Continous line: And possibly any line fails when the avatar is moving at speed.
Brushes: Brush masks are slow to load (User perception) Seems to take a couple of seconds.
Deleting: Sometimes with very long and undulating strokes it can be difficult to find a spot on the line which will trigger the delete.
There are a few minor gripes.
It is easy to unintentionally place a stroke when grabbing the tablet. Ie. you can draw when moving the tablet with the dominant hand.
Sometimes random polyline vert positions are created if the stroke intersects the tablet.
Performance:
User experience even with large numbers of strokes in view ( hundreds ) is good with no one reporting noticeable frame rate reductions.
There is no obvious way to delete ( apart from undo ) when painting in desktop mode.
There would probably ( almost certainly ) be issues with attempting to select large numbers of the strokes in the ent list but that is not due to this PR.
Tie a ribbon round this and send it on it's way.
Any previous feedback I've given regarding the quality of the strokes and other features still applies.

Closing as these changes are encompassed in #132 with the required structure for app certification

authors: CraftsmanMG Nex-Pro misslivirose themelissabrown

repo: highfidelity/hifi-content


text:
Updated styling

I added CSS and changed the HTML accordingly to make the popup look like the LTTStore.com website.
The extension is now also available in light and dark theme depending on the theme of the browser.

I didn't want to change the icon you made, but in the popup I used a newly created icon which fits more with the style of LTTStore.com. We could perhaps update the extension icon to this one too, but i'll leave that up too @highfly117 .

Looks much better and you Extension Icon is much better to

I'll make another PR to update the icon in the browser too then.


text:
Hello

Hello

/chatgpt hello

license: ISC


text:
Update the genbank fetcher  to read raw data

Description

What was changed in this pull request?

Add the text loader in the genbank data fetcher so that the genbank file doesn't have to be specified as a url

Why is it necessary?

If the data is already loaded by an external application it may not be accessible at a URL

Fixes #___
Checklist

[ ] Set proper GitHub labels (e.g. v1.6+, ignore if you don't know)
[x] Unit tests added or updated
[x] Documentation added or updated
[ ] Example(s) added or updated
[ ] Update schema.json if there are changes to the viewconf JSON structure format
[ ] Screenshot for visual changes (e.g. new tracks or UI changes)
[x] Updated CHANGELOG.md

What kind of escaping is expected for this to work? If I open a .gbff file and just copy the contents into the text property, it does not work. If I use the formatted text from GenbankFetcherTests, it works.

Yeah, Genbank is a very picky format. You have to make sure all  of the newlines are in  place. I loaded the Genbank elsewhere and set it as part of the viewconf programmatically.

authors: alexander-veit pkerpedjiev

repo: higlass/higlass


text:
Win10系统内使用Umi-OCR v2.1版本报错

CPU
Intel Core（TM）2 Duo CPU
Umi-OCR version 程序版本
2.1.0
Windows version 系统版本
win10
OCR plugins Used 使用的OCR插件
PaddleOCR
Reproduction steps 复现步骤
国产VDI虚拟云桌面登入后，v2.1.0解压桌面使用Umi-OCR，提示报错。
在使用截图功能后，步入自动识别文字时PaddleOCR-json.exe弹出错误窗口，“应用程序无法正常启动（0xc0000142）”。随后，Umi-OCR同样报错。
具体详见图片。Citrix虚拟桌面Workspace平台未测试。
Problem screenshots or related files (optional) 问题截图或相关文件（可选）

明显是该云环境缺乏AVX指令集。换用Rapid版本即可。

明显是该云环境缺乏AVX指令集。换用Rapid版本即可。

感谢指导 换用后Rapid版本后可正常使用

repo: hiroi-sora/Umi-OCR


text:
fix: pointer ignored, performance improvements

This PR is updating the config format:

    [storage]
    working_dir = "/hirosystems/ordhook/data"

    # The Http Api allows you to register / deregister
    # dynamically predicates.
    # Disable by default.
    #
    [http_api]
    http_port = 20456

    [network]
    mode = "mainnet"
    bitcoind_zmq_url = "tcp://0.0.0.0:18543"
    bitcoind_rpc_url = "http://0.0.0.0:8332"
    bitcoind_rpc_username = "xxx"
    bitcoind_rpc_password = "xxx"

    [snapshot]
    download_url = "https://archive.hiro.so/mainnet/ordhook/mainnet-ordhook-sqlite-latest"

    [resources]
    ulimit = 3096
    cpu_core_available = 12
    memory_available = 32
    bitcoind_rpc_threads = 4
    bitcoind_rpc_timeout = 15
    expected_observers_count = 1

Sorry to be difficult but now it just cant build this anymore. cargo ordhook-intall gives a bunch of errors like
relocation R_X86_64_32 against `.rodata.str1.8' can not be used when making a PIE object; recompile with -fPIC

The above seems to be due to the tcmalloc thing. Rolling back to the typo fixing commit solves it.

Any progress ?

@0xbitfly yep, we're almost there!

authors: 0xbitfly GuutBoy lgalabru

repo: hirosystems/ordhook


text:
Unable to determine chainID from node. [critical issue in 3.18.0]

it works in 3.17.2 but failed to work in 3.18.0. Please see above screenshot.
This affects all our test users. our API end point is:
https://stacks-node-api.testnet.alexlab.co
By using 3.17.2 downloaded from github release, the network can be added fine with same content.

@fbwoolf thoughts on whether / how the recent network refactor may have affected this?

@fbwoolf thoughts on whether / how the recent network refactor may have affected this?

Yep, most likely from those changes. I did test this before releasing, so let me look at it today.

Ended up not being my changes but a double // path:

Fix will be in the new wallet release today.

Hi @markmhx @fbwoolf thank you for releasing this fix as part of 3.18.1.
I see that Chrome web store still carries 3.18.0. Would you know when this will be updated to 3.18.1?

It's hard to say exactly how long it'll take for Google to approve for the Chrome Web Store, but we've submitted and usually it's quite fast (within 24 hours).

I see it's now updated to 3.18.1. Thank you!

I see it's now updated to 3.18.1. Thank you!

authors: caoer fbwoolf fiftyeightandeight goodsanai markmhx

repo: hirosystems/stacks-wallet-web


text:
Update README.md

Updated the contributors section in Readme

Hey @Glorycs29 , wonderful job
your commit message should be in this form :- :  and everything should be in small letters
refer:- https://github.com/hitesh22rana/OptySys/blob/main/CONTRIBUTION.md
can you update it?

okay I'll Update it

PR should be raised with this message :- docs: add contributors section


text:
AttributeError: type object 'PPODecorators' has no attribute 'empty_cuda_cache'. Did you mean: 'empty_device_cache'?

deepspeed zero3 单机双A10*24G微调chatglm3-6b，
ds_config.json
{     "bf16": {         "enabled": false     },     "fp16": {         "enabled": "auto",         "loss_scale": 0,         "loss_scale_window": 1000,         "initial_scale_power": 16,         "hysteresis": 2,         "min_loss_scale": 1     },     "optimizer": {         "type": "AdamW",         "params": {             "lr": "auto",             "betas": "auto",             "eps": "auto",             "weight_decay": "auto"         }     },     "scheduler": {         "type": "WarmupDecayLR",         "params": {             "last_batch_iteration": -1,             "total_num_steps": "auto",             "warmup_min_lr": "auto",             "warmup_max_lr": "auto",             "warmup_num_steps": "auto"         }     },     "zero_optimization": {         "stage": 3,         "offload_optimizer": {             "device": "cpu",             "pin_memory": true         },         "offload_param": {             "device": "cpu",             "pin_memory": true         },         "overlap_comm": true,         "contiguous_gradients": true,         "sub_group_size": 1e9,         "reduce_bucket_size": "auto",         "stage3_prefetch_bucket_size": "auto",         "stage3_param_persistence_threshold": "auto",         "stage3_max_live_parameters": 2e9,         "stage3_max_reuse_distance": 2e9,         "stage3_gather_16bit_weights_on_model_save": true     },     "gradient_accumulation_steps": "auto",     "gradient_clipping": "auto",     "steps_per_print": 2000,     "train_batch_size": "auto",     "train_micro_batch_size_per_gpu": "auto",     "wall_clock_breakdown": false }
ds_train.sh
deepspeed --num_gpus 2 src/train_bash.py \     --deepspeed ds_config.json \     --stage sft \     --model_name_or_path /home/projects/model/chatglm3-6b \     --do_train \     --dataset train \     --template chatglm3 \     --finetuning_type lora \     --lora_target query_key_value \     --output_dir checkpoint/chatglm3_lora \     --overwrite_cache \     --cutoff_len 5000 \     --per_device_train_batch_size 1 \     --lr_scheduler_type cosine \     --logging_steps 130 \     --save_steps 5000 \     --learning_rate 1e-4 \     --num_train_epochs 1 \     --plot_loss \     --fp16
提示这个错误：
Traceback (most recent call last):
File "/home/dotouch/work/projects/LLaMA-Factory/src/train_bash.py", line 1, in
from llmtuner import run_exp
File "/home/dotouch/work/projects/LLaMA-Factory/src/llmtuner/init.py", line 3, in
from llmtuner.api import create_app
File "/home/dotouch/work/projects/LLaMA-Factory/src/llmtuner/api/init.py", line 1, in
from llmtuner.api.app import create_app
File "/home/dotouch/work/projects/LLaMA-Factory/src/llmtuner/api/app.py", line 11, in
from llmtuner.chat import ChatModel
File "/home/dotouch/work/projects/LLaMA-Factory/src/llmtuner/chat/init.py", line 1, in
from llmtuner.chat.stream_chat import ChatModel
File "/home/dotouch/work/projects/LLaMA-Factory/src/llmtuner/chat/stream_chat.py", line 8, in
from llmtuner.tuner.core import get_infer_args, load_model_and_tokenizer
File "/home/dotouch/work/projects/LLaMA-Factory/src/llmtuner/tuner/init.py", line 1, in
from llmtuner.tuner.tune import export_model, run_exp
File "/home/dotouch/work/projects/LLaMA-Factory/src/llmtuner/tuner/tune.py", line 9, in
from llmtuner.tuner.ppo import run_ppo
File "/home/dotouch/work/projects/LLaMA-Factory/src/llmtuner/tuner/ppo/init.py", line 1, in
from llmtuner.tuner.ppo.workflow import run_ppo
File "/home/dotouch/work/projects/LLaMA-Factory/src/llmtuner/tuner/ppo/workflow.py", line 14, in
from llmtuner.tuner.ppo.trainer import CustomPPOTrainer
File "/home/dotouch/work/projects/LLaMA-Factory/src/llmtuner/tuner/ppo/trainer.py", line 28, in
class CustomPPOTrainer(PPOTrainer, Trainer):
File "/home/dotouch/work/projects/LLaMA-Factory/src/llmtuner/tuner/ppo/trainer.py", line 230, in CustomPPOTrainer
@PPODecorators.empty_cuda_cache()
AttributeError: type object 'PPODecorators' has no attribute 'empty_cuda_cache'. Did you mean: 'empty_device_cache'?

use trl==0.7.2

repo: hiyouga/LLaMA-Factory


text:
🛑 Griffo is down

In fb232d6, Griffo (https://www.griffo.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Griffo is back up in b1d9fc1 after 8 minutes.

repo: hjstrauss/MonitorMySites


text:
🛑 LM Bogen WSV is down

In 64bedef, LM Bogen WSV (https://www.lmbogenwsv.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: LM Bogen WSV is back up in 6dae4d5 after 13 minutes.


text:
🛑 Reime ohne Sinn und Verstand is down

In 51d3973, Reime ohne Sinn und Verstand (https://www.reimeohnesinnundverstand.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Reime ohne Sinn und Verstand is back up in 981003d after 13 minutes.


text:
🛑 Griffo is down

In c3c8613, Griffo (https://www.griffo.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Griffo is back up in 63f0ba9 after 8 minutes.


text:
🛑 HJStrauss is down

In 1a59fd5, HJStrauss (https://www.hjstrauss.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: HJStrauss is back up in ebb8337 after 9 minutes.


text:
🛑 Reime ohne Sinn und Verstand is down

In 23f4b79, Reime ohne Sinn und Verstand (https://www.reimeohnesinnundverstand.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Reime ohne Sinn und Verstand is back up in b31a0f2 after 8 minutes.


text:
🛑 Reime ohne Sinn und Verstand is down

In 29d373f, Reime ohne Sinn und Verstand (https://www.reimeohnesinnundverstand.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Reime ohne Sinn und Verstand is back up in 7b42227 after 8 minutes.


text:
Added JSON_PRESERVE_ZERO_FRACTION

Hi, man.
I've added JSON_PRESERVE_ZERO_FRACTION flag to all json_encode() occurrences of your code, because defaul json_encode() behaviour would remove zero fraction.
The purpose is: in case you want to validate a float number against pattern \d+.\d+, currently numbers with \d+.[0]+ (only zeroes as decimal part) are converted to \d+, making validation fail.
I'm aware that 1.0 and 1 are perfectly the same thing and that OpenAPI's number type matches both. Anyway specific cases where you want to enforce a non-empty decimal part currently cannot validate properly.
Let me know if it sounds as a reasonable thought or if you need an example.
Thanks in advance, as usual!

http://moneyphp.org/en/stable/ ?

Well, no, actually the need I'm reporting is not a matter of value, rather of format: if you want to force an API to use float numbers with decimal part always expressed (both 1.1 and 1.0), currently you can't, because 1.0 is converted to 1. As value, they're of course identical, but if make the format compulsory, they're different: the former is right, the latter is wrong.

authors: francescozanoni shadowhand


text:
Missing comma in configuration file readme example

Hello!
I copy-pasted the code https://github.com/hkupty/iron.nvim#how-to-configure here into my local config and it wouldn't work. Found that there is a comma missing:
    repl_definition = {
      sh = {
        command = {"zsh"}
      }
    } -- <=== HERE (line 14)
    repl_open_cmd = require('iron.view').curry.bottom(40),
    -- how the REPL window will be opened, the default is opening
}

Thanks for the awesome plugin.

Hi @EMPAT94 ,
Thanks for the issue! I'll fix it as soon as possible!
Glad you like it!
Best regards,
Henry


text:
Some doubts about the details

Thanks for the work DynamicRCNN, I have read the paper "Dynamic R-CNN: Towards High Quality Object Detection via Dynamic Training", for dynamic Dynamic SmoothL1 Loss, when calculating the regression errors , the source code is
https://github.com/hkzhang95/DynamicRCNN/blob/de62c3a4c3c131da9679dbda689d37edbdaaa5a1/models/zhanghongkai/dynamic_rcnn/coco/dynamic_rcnn_r50_fpn_1x/network.py#L166
           raw_regression_targets = cat(
                [proposal.get_field("regression_targets") for proposal in
                 raw_proposals], dim=0
            ).abs()[:, :2].mean(dim=1)

            rcnn_error_new = torch.kthvalue(raw_regression_targets.cpu(), min(
                cfg.MODEL.DYNAMIC_RCNN.KE * cfg.SOLVER.IMS_PER_GPU,
                raw_regression_targets.size(0)))[0].item()

But I have some doubts:
First, why does it use the mean offsets x and y instead of using the mean offsets of x ,y, w ,h to calculate the regression errors?  What's more, in the paper DynamicRCNN, it mentioned use regression error to update beta, but when I read the source code, it just uses the ground truth of offsets, it seems unreasonable.
Second, the hyper-parameter  MODEL.DYNAMIC_RCNN.KE choose the number 8 10 15, Are there some reasons? Does it relate to the anchor number or some other parameters?
@hkzhang95

Thanks for your question. Sorry for the late reply since I was a little busy these days.

Using the mean offsets of x&y is just one simple choice. From Figure 2 in the paper, the distribution of w&h are also similar, so we just use x&y for simplicity.
The definition of regression error is the offset from the candidate box to the target ground truth box. So I have no idea where is the problem.
KE can be viewed as a percentage ratio of the positives. For example, if KI=75, selecting KE=15 means we record the regression error of the positive sample at 20%. So choosing KE as 8 &10 means the percentage ratio is around 10%/13%.

I hope this can solve your problem.

Thanks for your question. Sorry for the late reply since I was a little busy these days.

Using the mean offsets of x&y is just one simple choice. From Figure 2 in the paper, the distribution of w&h are also similar, so we just use x&y for simplicity.
The definition of regression error is the offset from the candidate box to the target ground truth box. So I have no idea where is the problem.
KE can be viewed as a percentage ratio of the positives. For example, if KI=75, selecting KE=15 means we record the regression error of the positive sample at 20%. So choosing KE as 8 &10 means the percentage ratio is around 10%/13%.

I hope this can solve your problem.

Thanks for your reply. But I am still puzzled about the definition of regression error. In the paper DynamicRCNN, in Fig.4 the paper analyzes the relationship between regression error and gradient , the abscissa is regression error which denotes the x  in SmoothL1, but the implement of SmoothL1 in
https://github.com/hkzhang95/DynamicRCNN/blob/de62c3a4c3c131da9679dbda689d37edbdaaa5a1/dynamic_rcnn/det_opr/loss.py#L15
For my understanding, we compute the abs of the distance of input and target . So for the abscissa regression error, it should be the error of predict offset and target offset instead of the offset from the candidate box to the target ground truth box.
Otherwise, if we use the offset from the candidate box to the target ground truth box as regression error, it won't be changed actually, it always a fixed number because the offset from the candidate box to the target ground truth box don't change for the same image, it would be always related to the offset of targets, not related to the predicted offsets. The dynamic beta won't be really dynamic, it just the offset of targets with settled value before. So, in training process, it just changes the image combination of the different batch to get different beta.

Sorry for the wrong comment. Actually, I have noticed the misleading words and changed the expression from regression error to regression label in Figure 2. However, I forgot to change some other similar expressions in the paper, I will fix this bug in the next version.
Just for clarification (we use regression label to update beta):

regression error is the error between the predicted offset and the target offset
regression label is the target offset (termed as regression target in some papers), which can reflect the localization accuracy

Moreover, if we use the offset from the candidate box to the target ground truth box to update beta, it is also dynamic since in the second stage the candidate box is the proposal which is not fixed.


text:
如何开发 chameleon ?

https://github.com/hlerenow/chameleon/blob/master/DEV_README.md
中使用 yarn，但是项目中存在 pnpm-lock.yml 使用 pnpm 之后 lerna 似乎无法正确执行 lerna bootstrap
目前 lerna 新版本已经切换成 nx, 有考虑使用 nx 么？

文档写错了，已更新，目前用的 lerna-lit（不包含 nx功能） ，就是为了更干净些，没有负责的外部依赖，lerna 只是用来 发包，不做其他的处理。

cd ./ pnpm i pnpm run build cd package/engine pnpm ru nstart

还需要 lerna link 么？

不需要link ，按照上面全部使用pnpm命令，不要使用lerna

在提交的时候遇到
➜ git commit
✔ Preparing lint-staged...
✔ Hiding unstaged changes to partially staged files...
❯ Running tasks for staged files...
  ❯ package.json — 7 files
    ❯ packages/*/src/**/*.{js,jsx,ts,tsx} — 3 files
      ✖ eslint --fix --quiet [ENOENT]
    ❯ packages/*/src/**/* — 3 files
      ✖ prettier --write --ignore-unknown [KILLED]
↓ Skipped because of errors from tasks. [SKIPPED]
↓ Skipped because of errors from tasks. [SKIPPED]
✔ Reverting to original state because of errors...
✔ Cleaning up temporary files...

✖ eslint --fix --quiet failed without output (ENOENT).

✖ prettier --write --ignore-unknown failed without output (KILLED).
husky - pre-commit hook exited with code 1 (error)

的错误，暂时没找到方法，我尝试 pnpm prettier 或者 pnpm eslint 是存在的，不知道 lint-staged 是通过 pnpm 调度 eslint 和 prettier 还是通过全局，我全局上是不存在这两个工具的。

全局安装这两个工具后正常，

提交在根目录下使用 pnpm run cz，不要使用 git commit

authors: StringKe hlerenow

repo: hlerenow/chameleon


text:
[Blog Pages] Autoblock Sidebar

The sidebar has the same content for all blog pages in the same geosite (confirm with the customer)
This means that authors should not have to add it to every page. Instead it should be autoblocked on each page with the blog page template, using a fragment.
https://www.aem.live/developer/block-collection/fragment
https://www.aem.live/developer/markup-sections-blocks#auto-blocking

In https://github.com/hlxsites/servicenow/pull/58 I've added autoblocking/fragments for blog pages (articles)
Do we also need to autoblock these page types?

Category Page: https://www.servicenow.com/blogs/category/company-news.html
Topic Page: https://www.servicenow.com/blogs/topics/ai-and-automation.html
Author Page: https://www.servicenow.com/blogs/author/will-carlson.html
Year Page: https://www.servicenow.com/blogs/2023.html

Do we also need to autoblock these page types?

Good question, I asked the customer the same in https://adobe-dx-support.slack.com/archives/C05LRE7PRQ8/p1698154206957709?thread_ts=1697658221.518879&cid=C05LRE7PRQ8 . For now I can't say that I understand 100%

I would not block merging the current PR on it, so we can present it to the customer and get their feedback, based on that they might tell us: Yes, I like it like this, I want it on all other pages, or no, I want it differently on those pages.

authors: andreituicu florentin

repo: hlxsites/servicenow


text:
CIV-7026 Fix vary judgement label issue

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/CIV-7026
Change description
Fix vary judgement label issue
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

repo: hmcts/civil-general-apps-ccd-definition


text:
am-image 怎么得到image的ref ？

父组件中使用，报错
this.$refs['image'].save((result) => {
if (result.success) {
this.$notice.toast({ message: '已保存至本地' })
} else {
this.$notice.toast({ message: '保存失败！请稍后再试试~' })
}
});

暂时可以使用
this.$refs.image.image.save
使用，迟点我把image组件的方法加一下。

ok

repo: hminghe/weex-amui


text:
Etd 26

Changes for etd-26

etd-26 changes

repo: hmrc/customs-update-eori-admin-frontend


text:
[ETFE-377] Add Controller, View, Connector for MovementList

Associated PRs:

https://github.com/hmrc/emcs-tfe/pull/6

Closing as #14 supersedes this and contains fixes for QA

repo: hmrc/emcs-tfe-frontend


text:
PPTP-1648: Added page

hookup the change link and added more test
Description of Work carried through
Brief description of what/why/how.
Check list

[X] ./precheck was executed (Integration/Component/Unit tests)
[X] sbt scalafmt test:scalafmt was executed
[ ] Required Environment Config has been amended/added - N/A
[ ] Links to dependencies have been included (BE/FE work) - N/A
[X] User Acceptance Tests (UAT) were run locally and have passed.
[ ] No Accessibility errors/warnings reported by Wave -N/A

Yes, the migrate file is to do with the scaffolding. I just changed a little to allow to accept a parameter to allow to create route using snake case format. As default this create routes using Camel Case format.

Yes, the migrate file is to do with the scaffolding. I just changed a little to allow to accept a parameter to allow to create route using snake case format. As default this create routes using Camel Case format.

Actually I reverted the migrate.sh changes, as this should not gone in this PR. This should go inn a separate changes by itself so it can be discussed if it worth it doing.


text:
remove sonatype publishing dependencies to decouple building form publis...

...hing

I don't think sbt-sonatype from the builds at this point

authors: charleskubicek duncancrawford

repo: hmrc/play-breadcrumb


text:
Select cells in rectangular region

in spatial or tsne

fixed by #41

repo: hms-dbmi/vitessce


text:
feat: post comment to a blog

I added the post comment to blog endpoint to the route of the project at /api/v1/blogs/{blog_id}/comments. The endpoint accepts the post method.
Description
This endpoint adds comments to a blog post. The user must be authenticated and the content of the comment cannot be null or empty.
Related Issue (Link to issue ticket)
The issue for this pull request can be found here.
Motivation and Context
This endpoint adds comments to blog posts, helping authors get feedback on the thoughts of their users. The request blog_id must be of a blog which exists in the database. Any other id get a 404 error.
How Has This Been Tested?
The endpoint has been tested. The unit tests are in the file /tests/v1/blogs/test_add_comment.py.

[x] Data is added appropriately to the database.
[x] Appropriate response and status code is returned.
[x] Users must be authenticated.
[x] Non existing blog_id will throw a 404 error.
[x] Empty comment content will throw a 422 error.

The test can be run by: PYTHONPATH=. pytest /tests/v1/blogs/test_add_comment.py.
Affected areas of the code

I added a comment.py file to the route, service and schema folders. The files outline the model for my response data and logic for the endpoint respectively.
I added a test file at /tests/v1/blog/test_add_comment.py.

Screenshots (if appropriate - Postman, etc):
Success Response

No content in request body

Unauthenticated user response

Types of changes

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the readme accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

Fix merge conflict

It has been fixed @joboy-dev

Fix merge conflict

Do not merge


text:
General error during semantic analysis: Unsupported class file major version 61

HI!
Trying to use library within android project, which is setuped for supporting android 12 and java 11.
But When I'm trying to build an app - got every time this issue ->>>
`* What went wrong:
A problem occurred evaluating project ':react-native-drop-shadow'.

Plugin with id 'maven' not found.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
==============================================================================

2: Task failed with an exception.

What went wrong:
A problem occurred configuring project ':react-native-drop-shadow'.

compileSdkVersion is not specified. Please add it to build.gradle

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
==============================================================================

Get more help at https://help.gradle.org`

resolve 0.0.3


text:
macOS: Not running, needs update

Hi, I can't run this on macOS because Apple cannot check for malicious software. Any updates on when this will be solved?

macOS version: 14.4

Did you run it for the first time by doubleclicking it? Right click and choose "Open". Then normally you can still start it up.

Oh yeah lol that solves it. Thanks!


text:
where is module abc

@hobincar  Hi , I am sorry to disturb you again. This week I want to use inceptionv4 net to extract features from the datasets. When I run this project, I find the "from abc import ABC" this sentence from the config.py in the project, but I cannot find where the abc module defination is.  Please help me.

Hi @maoao686868, The module abc is the built-in module in python language. The docs is saying that it is added in version 3.4, and I guess you are using an older version of python.

@hobincar I am sorry. Yes, I forget to change the python version since these codes are based on python 3.6.8 virtual environment, and the code for "Reconstruction for video captioning" is based on the python2.7.12 virtual environment.


text:
ResultPage: Not responsive

Describe the bug
The resultpage itself is not responsive. User which want to interact with the webpage via tablet or phone, won't be able to deal with the given offers.
To Reproduce
Feed the homepage's searchbar with some input and route to the resultpage. Press F12 to open the developer tools and change the layout to responsive.
Expected behavior
The resultpage should be displayed responsive to get a good user experience.
Screenshots
Smartphone (please complete the following information):

Device: [e.g. iPhone6/7]

Partially fixed by https://github.com/hochschule-darmstadt/einander-helfen/commit/72460e8fb7e0ac260c3767f3885712f12399f3d4
I used css grids to fix the layout: https://github.com/hochschule-darmstadt/einander-helfen/blob/72460e8fb7e0ac260c3767f3885712f12399f3d4/app/src/views/ResultPage.vue#L273-L304
But the search bar is still not mobile usable

@sgrobarek did you have a look at this issue and what was already done,  before you pushed and merged?
In your layout changes the map and post details are at the bottom of the page:

If there are less posts a huge empty space is being shown:

@sgrobarek did you have a look at this issue and what was already done, before you pushed and merged?
@jschurse sry, saw that after my work was done. hope everything is okay :S

Implemented and merged

authors: andresesam jschurse sgrobarek

repo: hochschule-darmstadt/einander-helfen


text:
Minor refactoring to fix warning and some clippy lints

Fixes unrestricted recursion in peppi-arrow
Uses shorthand struct initialization where it makes sense
Automatic clippy lint fixing

Rebased and separated the commits

Added commit that fixes the indexing error I identified in #16

repo: hohav/peppi


text:
502 Bad Gateway nginx/1.18.0 (Ubuntu)

After clicking up the sing button and select the workspace, I get this error:
502 Bad Gateway
nginx/1.18.0 (Ubuntu)

Also getting this issue

Yep, me too. The code is still in the URL, but pasting that code and then trying to continue it just hangs on "Loading..."

I am having the same issue here. So I tried the same steps as @AMGMNPLK , and I had the same results: the modal window of the login freezes :

I get the same issue. When I paste the code in to sign in, it loads indefinitely and the condole provides this error:

Same issue here "502 Bad Gateway". As for now, I think I'll just keep ClickUp open in a tab in Obsidian with the Open Gate plugin . At at least I do not have to do back and forth even if it is not the ideal solution

Same issue.

@CCampanini  @MilesRomney
Do you still receive the error?
Looks like an issue with the server.
P.S. Sorry for late response for some reason I wasn't getting any notification about issues and comments

Hey, @hokim-m!  Thanks for getting back to us!  Currently, I no longer get the bad gateway issue, but I now get this error:

Let me know if there's anything else you'd like me to send you.  Looking at the console, I am not sure what would be helpful.

@Redster1 fixed, please update plugin

Heyo! It works!

authors: AMGMNPLK Amina-Delali CCampanini MilesRomney Redster1 Zafarzz hokim-m looqingGood rolanddutoit

repo: hokim-m/click-up-x-obsidian


text:
Add select mechanism

Added some neat functionalities for selection of a specific option.
Can be tested with:
rl.on('data', (line) => {
  sendMessage(line)
  const hardcodedOptions = ['abcdfe', 'efghij', 'klmnop', 'qrstuv', 'wxyzab', 'cdefgh', 'ijklmn', 'opqrst', 'uvwxyz', 'abcdef']
  if (line === 'options') {
    rl.showOptions(hardcodedOptions)
    return
  }
  rl.prompt()
})
rl.prompt()

rl.on('optionSelected', (selectedOption) => {
  console.log(`Selected option: ${selectedOption}`)
})

Thank you for the suggestion! This is outside the scope of the module, however, and would be best implemented as a separate module.

Could you set up a repo and i will do a pull request? Maybe call it something like bare-cli-helpers?

Community modules are more than welcome so feel free to create and publish such a module yourself! There's no need for us to gatekeep it.

@kasperisager https://github.com/dabuchera/bare-select-prompts

authors: dabuchera kasperisager

repo: holepunchto/bare-readline


text:
Add getAndWatch

Two behaviours were somewhat unexpected, both related to truncates:
In the 'getAndWatch truncate flow' test, I think we're hitting a race condition on await this.bee.get(this.key), where a truncate is triggered ~at the same time as the get. This results in a SNAPSHOT_NOT_AVAILABLE error.
This one is solved by catching that particular error and early-returning, because we know it was triggered by a truncate, so _onAppend will run again anyway. But if it is indeed a race condition, I think it should be solved elsewhere in the code.
In the 'getAndWatch chaos' test, there's still a TODO, because I had to add an await eventFlush() to avoid a crash, and I don't think it should be necessary. It might be a similar scenario to the error above, but I'm not sure. The error is
`/home/hans/holepunch/hyperbee/node_modules/random-access-memory/index.js:86
      return req.callback(new Error('Could not satisfy length'), null)
                          ^

Error: Could not satisfy length
    at RAM._read (/home/hans/holepunch/hyperbee/node_modules/random-access-memory/index.js:86:27)
    at Request._run (/home/hans/holepunch/hyperbee/node_modules/random-access-storage/index.js:258:42)
    at RAM.run (/home/hans/holepunch/hyperbee/node_modules/random-access-storage/index.js:153:14)
    at RAM.read (/home/hans/holepunch/hyperbee/node_modules/random-access-storage/index.js:60:10)
    at /home/hans/holepunch/hyperbee/node_modules/hypercore/lib/merkle-tree.js:1120:13
    at new Promise (<anonymous>)
    at getStoredNode (/home/hans/holepunch/hyperbee/node_modules/hypercore/lib/merkle-tree.js:1119:10)
    at MerkleTree.get (/home/hans/holepunch/hyperbee/node_modules/hypercore/lib/merkle-tree.js:433:12)
    at MerkleTree.byteOffset (/home/hans/holepunch/hyperbee/node_modules/hypercore/lib/merkle-tree.js:763:33)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

2.10.0

authors: HDegroote mafintosh

repo: holepunchto/hyperbee


text:
Add options to blobs.clear method

Depends on https://github.com/holepunchto/hypercore/pull/373

2.3.0

authors: LuKks mafintosh

repo: holepunchto/hyperblobs


text:
status of scikit-optimize

May I kindly ask what exactly is the status of scikit-optimize?
It looks confusing:

GitHub archived and seemingly defunct
this repository and you, @holgern, committed to maintaining

If you are continuing maintenance, why not in the original repo?
I'd also be available to help, although I'd like to understand the current situation better.

Hi @fkiraly ,
I was a maintainer for scikit-optimize in 2021 and during this time I was added to the pypi-repository as maintainer.
Then my work was moving away from classification and others had taken my maintenance role, until they stopped being active.
Then the owner of scikit-optimize decided to archive scikit-optimize, as no one was doing something. This was the moment when I was again aware of the scikit-optimize project.
I was willing to do the maintaince again and I asked the project owner to allow me to do this. They did not response.
As I'm still maintainer of the pypi-repo. I decided to move the code to this new location and I worked through all open PR and integrated them into the codebase.
I'm would be more than happy to contribute to the original git location, but I do not have access.
Hope this helps to understand the situation better.

Ah, I see. That makes sense, summarizing so I just understand:

you were a maintainer back some years ago and drifted off the project but never officially left
other maintainers decided to close down the project but did not contact all other maintainers (2023-2024)
they archived it in Feb 2024 on their own initiative, and that's when you heard of it again being closed down
you thought, you'd be happy to take a more active role to prevent the project from closing and keep it maintained
you contacted the maintainers about this, and also proved that you were willing and able to continue maintaining the project by handling the PR and variou supdates (March 2024) but they did not respond since then

Is the above a correct summary of the project's current history?
If so, I could offer to help out as well, at sktime we are maintaining multiple sklearn-like packages under a streamlined maintenance framework, so one more would be only a fractional addition to the workload, compared to maintaining packages separately. After a bit of upfront refactor of release pipelines and package structure (non-breaking), things should be easier.
What do you think?

?

Yes, that is a correct summary.
It seems that adding scikit-optimize to sktime would be a good thing. So I generally agree with integrating scikit-optimize into the sktime organization (assuming I would still be a maintainer and would be able to release new versions of scikit-optimize).

authors: fkiraly holgern

repo: holgern/scikit-optimize


text:
IE11 - Reorder XHR timeout and enforce async to avoid InvalidStateError

I'm seeing strange behaviour in our staging environment in IE11, whereby when we go to flush the transport buffer we get an InvalidStateError - the internet suggests it's sometime to do with the ordering of the commands (https://github.com/stephanebachelier/superapi/issues/5) and looking at how superagent is implemented, they avoid synchronous requests entirely, so I'm following in their footsteps.

Looks fabulous 👍

repo: holidayextras/barometer


text:
Explainability metrics

explainability metrics
feature importance plots
tutorials

Also, for lime, am I right in thinking that the contrast metrics are not included here?
Is it "replaced" with the importance spread for features? I guess for each feature, you get their range and calculate the entropy of the ranks compared to if it was the same rank in each sample, which give you some sort of contrast metric?
Do we have demos of the effectiveness of these metrics? i.e. what are expected "good" values? Or can we only figure that out by comparing to a benchmark explainable model?

repo: holistic-ai/holisticai


text:
Update pins on some examples

This PR updates some of the dependencies in the nyc_taxi and glaciers examples.
New issue: it appears the .parq file in the nyc_taxi examples is no longer being read correctly by fastparquet.

New issue: it appears the .parq file in the nyc_taxi examples is no longer being read correctly by fastparquet.

This is a problem I also got in https://github.com/holoviz-topics/examples/pull/369. The last comment was:

Ok so I ended up with keeping pyarrow as the engine but adding this before the imports:
import dask

dask.config.set({"dataframe.convert-string": False})
dask.config.set({"dataframe.query-planning": False})

Since HoloViews does that too in its test suite, meaning that there's isn't yet "official" support for these two features (query planner and pyarrow string): https://github.com/holoviz/holoviews/blob/6b0121d5a3685989fca58a1687961523a5fd575c/holoviews/tests/conftest.py#L61-L62

However, since then, HoloViews no longer sets dask.config.set({"dataframe.query-planning": False}) (it still has dask.config.set({"dataframe.convert-string": False})).
https://github.com/holoviz/holoviews/blob/e5f7aede7a58902677eb995b8fd67c54ae9ae3ab/holoviews/tests/conftest.py#L55-L60
My suggestions:

Try with engine='pyarrow' and see whether the notebook runs fine. Don't set any of the dask.config options yet, maybe it works without them.
If it doesn't work, start with dask.config.set({"dataframe.convert-string": False}).

Note that in the past, pyarrow and fastparquet had very different performance from each other in certain workloads, so ideally you'd at least qualitatively compare the old pinned version with the new version, and make sure that performance has not significantly degraded.

Try with engine='pyarrow' and see whether the notebook runs fine. Don't set any of the dask.config options yet, maybe it works without them.
If it doesn't work, start with dask.config.set({"dataframe.convert-string": False}).

I have tried each of the suggestions individually and all together but it still didn't work. It still shows the same Traceback error. Here's the full Traceback:
Full traceback

---------------------------------------------------------------------------
OSError                                   Traceback (most recent call last)
File <timed exec>:2

File ~/Documents/development/holoviz-topics-examples/nyc_taxi/envs/default/lib/python3.11/site-packages/dask/base.py:348, in DaskMethodsMixin.persist(self, **kwargs)
    309 def persist(self, **kwargs):
    310     """Persist this dask collection into memory
    311
    312     This turns a lazy Dask collection into a Dask collection with the same
   (...)
    346     dask.persist
    347     """
--> 348     (result,) = persist(self, traverse=False, **kwargs)
    349     return result

File ~/Documents/development/holoviz-topics-examples/nyc_taxi/envs/default/lib/python3.11/site-packages/dask/base.py:998, in persist(traverse, optimize_graph, scheduler, *args, **kwargs)
    995     postpersists.append((rebuild, a_keys, state))
    997 with shorten_traceback():
--> 998     results = schedule(dsk, keys, **kwargs)
   1000 d = dict(zip(keys, results))
   1001 results2 = [r({k: d[k] for k in ks}, *s) for r, ks, s in postpersists]

File ~/Documents/development/holoviz-topics-examples/nyc_taxi/envs/default/lib/python3.11/site-packages/dask/dataframe/io/parquet/core.py:97, in ParquetFunctionWrapper.__call__(self, part)
     94 if not isinstance(part, list):
     95     part = [part]
---> 97 return read_parquet_part(
     98     self.fs,
     99     self.engine,
    100     self.meta,
    101     [
    102         # Temporary workaround for HLG serialization bug
    103         # (see: https://github.com/dask/dask/issues/8581)
    104         (p.data["piece"], p.data.get("kwargs", {}))
    105         if hasattr(p, "data")
    106         else (p["piece"], p.get("kwargs", {}))
    107         for p in part
    108     ],
    109     self.columns,
    110     self.index,
    111     self.common_kwargs,
    112 )

File ~/Documents/development/holoviz-topics-examples/nyc_taxi/envs/default/lib/python3.11/site-packages/dask/dataframe/io/parquet/core.py:645, in read_parquet_part(fs, engine, meta, part, columns, index, kwargs)
    642 if len(part) == 1 or part[0][1] or not check_multi_support(engine):
    643     # Part kwargs expected
    644     func = engine.read_partition
--> 645     dfs = [
    646         func(
    647             fs,
    648             rg,
    649             columns.copy(),
    650             index,
    651             **toolz.merge(kwargs, kw),
    652         )
    653         for (rg, kw) in part
    654     ]
    655     df = concat(dfs, axis=0) if len(dfs) > 1 else dfs[0]
    656 else:
    657     # No part specific kwargs, let engine read
    658     # list of parts at once

File ~/Documents/development/holoviz-topics-examples/nyc_taxi/envs/default/lib/python3.11/site-packages/dask/dataframe/io/parquet/core.py:646, in <listcomp>(.0)
    642 if len(part) == 1 or part[0][1] or not check_multi_support(engine):
    643     # Part kwargs expected
    644     func = engine.read_partition
    645     dfs = [
--> 646         func(
    647             fs,
    648             rg,
    649             columns.copy(),
    650             index,
    651             **toolz.merge(kwargs, kw),
    652         )
    653         for (rg, kw) in part
    654     ]
    655     df = concat(dfs, axis=0) if len(dfs) > 1 else dfs[0]
    656 else:
    657     # No part specific kwargs, let engine read
    658     # list of parts at once

File ~/Documents/development/holoviz-topics-examples/nyc_taxi/envs/default/lib/python3.11/site-packages/dask/dataframe/io/parquet/arrow.py:641, in ArrowDatasetEngine.read_partition(cls, fs, pieces, columns, index, dtype_backend, categories, partitions, filters, schema, **kwargs)
    638     row_group = [row_group]
    640 # Read in arrow table and convert to pandas
--> 641 arrow_table = cls._read_table(
    642     path_or_frag,
    643     fs,
    644     row_group,
    645     columns,
    646     schema,
    647     filters,
    648     partitions,
    649     partition_keys,
    650     **kwargs,
    651 )
    652 if multi_read:
    653     tables.append(arrow_table)

File ~/Documents/development/holoviz-topics-examples/nyc_taxi/envs/default/lib/python3.11/site-packages/dask/dataframe/io/parquet/arrow.py:1774, in ArrowDatasetEngine._read_table(cls, path_or_frag, fs, row_groups, columns, schema, filters, partitions, partition_keys, **kwargs)
   1767     arrow_table = frag.to_table(
   1768         use_threads=False,
   1769         schema=schema,
   1770         columns=cols,
   1771         filter=_filters_to_expression(filters) if filters else None,
   1772     )
   1773 else:
-> 1774     arrow_table = _read_table_from_path(
   1775         path_or_frag,
   1776         fs,
   1777         row_groups,
   1778         columns,
   1779         schema,
   1780         filters,
   1781         **kwargs,
   1782     )
   1784 # For pyarrow.dataset api, if we did not read directly from
   1785 # fragments, we need to add the partitioned columns here.
   1786 if partitions and isinstance(partitions, list):

File ~/Documents/development/holoviz-topics-examples/nyc_taxi/envs/default/lib/python3.11/site-packages/dask/dataframe/io/parquet/arrow.py:271, in _read_table_from_path(path, fs, row_groups, columns, schema, filters, **kwargs)
    264     return pq.ParquetFile(fil, **pre_buffer).read(
    265         columns=columns,
    266         use_threads=False,
    267         use_pandas_metadata=True,
    268         **read_kwargs,
    269     )
    270 else:
--> 271     return pq.ParquetFile(fil, **pre_buffer).read_row_groups(
    272         row_groups,
    273         columns=columns,
    274         use_threads=False,
    275         use_pandas_metadata=True,
    276         **read_kwargs,
    277     )

File ~/Documents/development/holoviz-topics-examples/nyc_taxi/envs/default/lib/python3.11/site-packages/pyarrow/parquet/core.py:537, in ParquetFile.read_row_groups(self, row_groups, columns, use_threads, use_pandas_metadata)
    495 """
    496 Read a multiple row groups from a Parquet file.
    497
   (...)
    533 animal: [["Flamingo","Parrot","Dog",...,"Brittle stars","Centipede"]]
    534 """
    535 column_indices = self._get_column_indices(
    536     columns, use_pandas_metadata=use_pandas_metadata)
--> 537 return self.reader.read_row_groups(row_groups,
    538                                    column_indices=column_indices,
    539                                    use_threads=use_threads)

File ~/Documents/development/holoviz-topics-examples/nyc_taxi/envs/default/lib/python3.11/site-packages/pyarrow/_parquet.pyx:1418, in pyarrow._parquet.ParquetReader.read_row_groups()

File ~/Documents/development/holoviz-topics-examples/nyc_taxi/envs/default/lib/python3.11/site-packages/pyarrow/error.pxi:91, in pyarrow.lib.check_status()

OSError: RLE encoding only supports BOOLEAN

OK thanks for the report. It looks like the file cannot be read with pyarrow. We'll have to read it with fastparquet (for that dask-expr will have to be disabled), and save it again using pyarrow.

OK thanks for the report. It looks like the file cannot be read with pyarrow. We'll have to read it with fastparquet (for that dask-expr will have to be disabled), and save it again using pyarrow.

Can you guide me on how I can do this?

Suggesting Needed to avoid a warning emitted when datashader internally imports dask.dataframe import.

OK. I'll make it clearer.

This PR need to be rebased on top of main. Will do that soon...

authors: Azaya89 jbednar maximlt

repo: holoviz-topics/examples


text:
Psychic

Summary

This PR adds possibility to add documents via psychic.
Fixes #73
Screenshots

Checklist

[x] My code follows the code style of this project and passes make format.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] My change has adequate unit test coverage.

@jasonwcfan Thanks for this contribution! Will be merged tomorrow!

repo: homanp/superagent


text:
Add support for ValueDecodeFailure

Handles bad matter devices that have cluster attributes with the wrong values and are turned into ValueDecodeFailure types by the chip library.
Resolves https://github.com/home-assistant-libs/python-matter-server/issues/187
Hue Bridge is an example of a device in this case an ExtendedColorLight with attributes that can't be parsed by the chip controller

Marking as draft pending https://github.com/orgs/home-assistant-libs/projects/1?pane=issue&itemId=16855348

I have seen this one too while working on the bridge support, its pretty common.
For now I've filtered out the ones I saw but we need to fix this both upstream and in the parser logic at some point.

authors: ArturoGuerra balloob marcelveldt


text:
How do you change the color of the entity on a light panel?

BTW this is awesome! I don't see a way to change the font properties of the entity name on a light panel. Also, is there a way to change the name of a panel, instead of using the entity name?

Hey @mlittle408 ! I Really appreciate it! I'm going to add this feature soon.

repo: home-assistant-react/dashboard