Make sure npm package works properly

The info in npm site is not up to date. We should update it to reflect the current readme.
Also - when trying to install sharkio via npm using the command in the documentation  I got the following error:

I can add maintainers to the npm package.
Write your npm usernames below and i'll add them to the npm package.

Also you the package is not sharkio.
It's @idodav/sharkio

my npm username is oferlis

I can add maintainers to the npm package. Write your npm usernames below and i'll add them to the npm package.

this fixed the problem for me , you should change the README to match the correct npm package name


Traefik v3.0 breaks existing cert-manager integrations

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?
I was using Traefik v2 for a long time together with cert-manager inside Kubernetes.
For my usual routes, I am using the IngressRoute CRD which works perfectly fine again after I followed the migration guide.
However, all my existing cert-manager integrations and automatic certificate renewals in the whole cluster stopped working silently. The acme-solvers created by the cert-manager are default Kubernetes Ingress and they have not changed at all. I just noticed this today after a certificate could not be renewed for a very long time and gut stuck.
The Ingress they create is nothing special and as mentioned this has not changed, I have not done any other updates to the cluster than Traefik v3.0 since this problem came up.
What did you see instead?
It seems that the Ingress route is simply ignored. I tried by removing all existing IngressRoutes in the same namespace and only leaving the auto-created Ingress for a testing certificate. I tried to manually debug the whole flow and see where it gets stuck and it was for sure Traefik v3.0.
I am using the Helm Chart to deploy Traefik and providers.kubernetesIngress.enabled is set to true and is the default value in there.
The auto-created spec looks like this:
spec:
  rules:
  - host: host.example.com
    http:
      paths:
      - backend:
          service:
            name: cm-acme-http-solver-qrg6m
            port:
              number: 8089
        path: /.well-known/acme-challenge/als2om6EN1LVdx548XZESnj9DkuHh3idOaexEcaFkmI
        pathType: ImplementationSpecific

I usually have https-redirects for each host name and as soon as I added the IngressRoute again, I got back the HTTP 301 from it, even though I should have gotten the acme challenge. But as mentioned even without this redirect route I alway received a 404 page not found.
I am using a very nasty workaround everywhere now so I can at least get my certificates renewed. This is simply ignoring the auto-created Ingres resources and I manually added the following IngressRoute definitions to at least make it working again:
apiVersion: traefik.io/v1alpha1
kind: IngressRoute
metadata:
  name: https-redirect
spec:
  entryPoints:
    - web
  routes:
    - match: Host(`host.example.com`) && !PathPrefix(`/.well-known/acme-challenge/`)
      kind: Rule
      middlewares:
        - name: https-only
          namespace: traefik
      services:
        - name: some-service
          port: 3000
    - match: Host(`host.example.com`) && PathPrefix(`/.well-known/acme-challenge/`)
      kind: Rule
      services:
        - name: acme-svc-workaround
          port: 8089
---
apiVersion: v1
kind: Service
metadata:
  name: acme-svc-workaround
spec:
  selector:
    acme.cert-manager.io/http01-solver: "true"
  ports:
    - name: http
      port: 8089
      targetPort: 8089

This solution is very brittle and tedious though.
I was very lucky that the failed certificate over night was on some staging environment instead of production.
What version of Traefik are you using?
Helm Chart version:
traefik-28.0.0
App-Version:
3.0.0
What is your environment & configuration?
Custom values.yaml:
globalArguments:
  - --global.checknewversion
  - --accesslog.fields.names.StartUTC=drop

deployment:
  kind: DaemonSet
  minReadySeconds: 3

podDisruptionBudget:
  enabled: true
  maxUnavailable: 2

ingressRoute:
  dashboard:
    enabled: true

providers:
  kubernetesCRD:
    enabled: true
    allowCrossNamespace: true
    allowExternalNameServices: true
    allowEmptyServices: true

env:
  - name: TZ
    value: Europe/Berlin

logs:
  general:
    level: INFO
  access:
    enabled: true
    bufferingSize: 100
    filters:
      statuscodes: "300-599"
      minduration: 1ms
    fields:
      headers:
        defaultmode: drop
        names:
          User-Agent: keep

resources:
  requests:
    cpu: 200m
    memory: 256Mi
  limits:
    cpu: 1000m
    memory: 512Mi

service:
  enabled: true
  type: LoadBalancer
  spec:
    externalTrafficPolicy: Local

ports:
  websecure:
    asDefault: true
    http3:
      enabled: true

podAntiAffinity:
  requiredDuringSchedulingIgnoredDuringExecution:
    - labelSelector:
        matchExpressions:
          - key: app
            operator: In
            values:
              - traefik
      topologyKey: failure-domain.beta.kubernetes.io/zone

If applicable, please paste the log output in DEBUG level
No response

I have the same setup with Cert Manager and I also see this behaviour in the newly released 3.0.1, I saw it since at least 3.0.0-rc3. I see 404 in the Traefik logs on requests to /.well-known/acme-challenge/.* paths. My workaround is similar, I copy the generated rule to my IngressRoute. Fortunately I have only a handful of certificates to manage.

I don't think it's related to cert-manager at all, just to the default ingress class for kubernetes.
I just have this problem with cert-manager, because it creates the default ingress instead of the IngressRoute CRD.

Yes that's an issue with IngressRoute.
As Traefik v3 changes the API from  traefik.containo.us/v1alpha1 to traefik.io/v1alpha1. Previous IngressRoutes are ignored.
I wrote a little migration script (note: I'm considering here that the IR and the namespace name are equal)
# Create a new IR with the proper API
for irname in $(kubectl get ingressroutes.traefik.containo.us --all-namespaces -o json | jq '.items | .[] | .metadata.name' -r); do kubectl -n ${irname} get ingressroute ${irname} -oyaml  | grep -v -e "uid:" -e "resourceVersion:" -e "generation:" -e "creationTimestamp" | sed 's/.containo.us/.io/' | kubectl -n ${irname} apply -f -; done
# Delete the previous one
for irname in $(kubectl get ingressroutes.traefik.containo.us --all-namespaces -o json | jq '.items | .[] | .metadata.name' -r); do kubectl -n ${irname} delete ingressroutes.traefik.containo.us ${irname}; done

Yes that's an issue with IngressRoute.

No it's not, all the IngressRoutes work fine after the migration. It's the default Ingress class not being taken into account for the routing.

I have the same setup with Cert Manager and I also see this behaviour in the newly released 3.0.1, I saw it since at least 3.0.0-rc3. I see 404 in the Traefik logs on requests to /.well-known/acme-challenge/.* paths. My workaround is similar, I copy the generated rule to my IngressRoute. Fortunately I have only a handful of certificates to manage.

@stellirin I think the problem you are describing is related to #10672.

Hello @sebadob,
Are you still facing this issue?
On v3 we changed the supported IngressClass API Group as detailed in the migration guide.
Is your k8s cluster supporting v1 IngressClass? which k8s version are you using?
If your cluster is not supporting v1 you should see some ERROR logs.
Could you provide your logs in debug mode?

Are you still facing this issue?

Yes, I do. I just updates to Helm Chart 29.0.1 / Traefik 3.0.4.
I left one of the certificates in place which I don't need anymore just to keep track of the issue.
The example cluster is currently running K3s v1.28.7+k3s1.
The Ingress which is automatically created by cert-manager is of version networking.k8s.io/v1.
I just replaced the URL and token with an example one in the output below.
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    kubernetes.io/ingress.class: traefik
    nginx.ingress.kubernetes.io/whitelist-source-range: <IP_ADDRESS>/0,::/0
  creationTimestamp: "2024-07-01T19:02:14Z"
  generateName: cm-acme-http-solver-
  generation: 1
  labels:
    acme.cert-manager.io/http-domain: "1538328624"
    acme.cert-manager.io/http-token: "1378291422"
    acme.cert-manager.io/http01-solver: "true"
  name: cm-acme-http-solver-wbpnw
  namespace: nats
  ownerReferences:
  - apiVersion: acme.cert-manager.io/v1
    blockOwnerDeletion: true
    controller: true
    kind: Challenge
    name: my.dns.name-tls-staging-2-1854993671-323736840
    uid: e3bed558-def9-4212-8257-c6b6b3e5f454
  resourceVersion: "49310579"
  uid: ed165167-dd6d-494c-9a62-42e3c6802021
spec:
  rules:
  - host: my.dns.name
    http:
      paths:
      - backend:
          service:
            name: cm-acme-http-solver-xh2wg
            port:
              number: 8089
        path: /.well-known/acme-challenge/hyyjzsa2grDXN2U3DK42XY89gwp5NhWWQW5tS9MkcWk
        pathType: ImplementationSpecific
status:
  loadBalancer: {}

For this certificate I did not add my above workaround to the IngressRoute, which solves the issue for all other certificates.
I can see the GET to the path in the Ingress coming in where cert-manager is checking availability all the time, but Traefik simply returns a 404:
<IP_ADDRESS> - - [15/Jul/2024:11:52:45 +0200] "GET /.well-known/acme-challenge/hyyjzsa2grDXN2U3DK42XY89gwp5NhWWQW5tS9MkcWk HTTP/1.1" 404 19 "-" "cert-manager-challenges/v1.14.4 (linux/amd64) cert-manager/f5ddc412723722518f401f9ce6ec6fc950e72c04" 10 "-" "-" 0ms

I do not really like publishing debug logs here because they would contain sensitive information, but I took a look at them.
If seems that Traefik is automatically adding certificates for all domains I am using in my IngressRoutes automatically while at the same time complaining about no configured store, which makes sense because I am using cert-manager for this purpose.
Could this be intercepting the routes to /.well-known/acme-challenge/ ?
If debug logs would really help you here, I could strip all domains and change them to example ones, but I am not really sure if I might leak something else with them.

It seems that Traefik is automatical ly adding certificates for all domains I am using in my IngressRoutes while at the same time complaining about no configured store, which makes sense because I am using cert-manager for this purpose.
Could this be intercepting the routes to /.well-known/acme-challenge/ ?

Could you elaborate on this point? are you using a certresolver?

Could you elaborate on this point? are you using a certresolver?

No I am not using any certresolver, which is why these logs confused me. I am managing all my K8s internal certificates with cert-manager which is probably the de facto standard. All of this was working super nicely with Traefik v1 and v2, but v3 is either intercepting and not forwarding the requests, or is ignoring the default kubernetes Ingress route that is added automatically. I see that Traefik picks them up when I take a look at the access logs, but instead of forawrding the request to the cert-manager pods like the Ingress above defines it, it returns a 404.
As soon as I add a manual route definition to my IngressRoute which does the exact same thing as the auto-created Ingress from cert-manager, everythings works fine again. But I have to manually define this in each namespace while it was working perfectly fine with the older versions.

Hello @sebadob,
After multiple tests we reproduced the issue and found that it is a configuration issue. In your values.yaml the websecure entrypoint is marked as default with the asDefault: true option.
As explained in the documentation when an entrypoint is marked as default and a router (in this case the certmanager Ingress) does not specify an entrypoint, it will be only attached to the default entrypoints (in your case the websecure one).
Thus, the certmanager Ingress is only attached to the websecure entrypoint, but to successfully resolve the challenge it has to be attached to the web entrypoint.
To fix the issue you should remove the asDefault configuration or add the annotation traefik.ingress.kubernetes.io/router.entrypoints: web to the ingressTemplate configured in certmanager.
According to that I am closing this issue as a question.

No it does not work. I have added this annotation to the cluster issuer under ingressTemplate but still the same i can access this URL  ('http://nginx1.example.com/.well-known/acme-challenge/jeRU8h02AJe_RNTh-GU6nX8mfDd0RxS9Xpf_f_-kl2c) from the cluster node and publicly also. but still challenge is pending.
How it is working for traefik dashboard?? (all the services withing the same IngressRoute)

After multiple tests we reproduced the issue and found that it is a configuration issue. In your values.yaml the websecure entrypoint is marked as default with the asDefault: true option.

@kevinpollet oh man, thank you a lot. I totally missed that, my bad!
After removing the option, everything started working fine again.
Thanks a lot!

apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
name: letsencrypt
spec:
acme:
solvers:
- http01:
ingress:
class: traefik
ingressTemplate:
metadata:
annotations:
traefik.ingress.kubernetes.io/router.entrypoints: web
privateKeySecretRef:
  name: letsencrypt-private-key
server: https://acme-v02.api.letsencrypt.org/directory

apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
name: tls-cert
namespace: dev
spec:
commonName: traefik.example.com
dnsNames:
- traefik.example.com
- nginx1.example.com
- nginx2.example.com
issuerRef:
kind: ClusterIssuer
name: letsencrypt
secretName: tls-cert

apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
name: traefik-dashboard
namespace: dev
annotations:
kubernetes.io/ingress.class: traefik
spec:
entryPoints:
- web
- websecure
routes:
- match: Host(nginx1.example.com)
kind: Rule
services:
- name: nginx-svc
port: 80
- match: Host(`nginx2.example.com`) && PathPrefix(`/`)
  kind: Rule
  services:
    - name: second-nginx
      port: 80

- match: Host(`traefik.example.com`)
  kind: Rule
  services:
    - name: api@internal
      kind: TraefikService
  middlewares:
    - name: auth-dashboard

tls:
secretName: tls-cert

apiVersion: traefik.io/v1alpha1
kind: Middleware
metadata:
name: auth-dashboard
namespace: dev
spec:
basicAuth:
secret: traefik-auth-dashboard
apiVersion: v1
kind: Secret
metadata:
name: traefik-auth-dashboard
namespace: dev
data:
users: 111111

commonName: traefik.example.com
dnsNames:

traefik.example.com
nginx1.example.com
nginx2.example.com

@mohamaddayoub It is impossible that this could ever work, because you (most probably) don't own example.com and this domain does not have a valid route into your cluster. So this is probably your problem, because Let's Encrypt will never be able to reach your endpoints via traefik.example.com.

Actually i am using a proper DNS but i changed it here only.
the error in challenge logs: Waiting for HTTP-01 challenge propagation: failed to perform self check GET request 'http://nginx1.example.com/.well-known/acme-challenge/jeRU8h02AJe_RNTh-GU6nX8mfDd0RxS9Xpf_f_-kl2c': Get "http://nginx1.example.com//.well-known/acme-challenge/jeRU8h02AJe_RNTh-GU6nX8mfDd0RxS9Xpf_f_-kl2c": dial tcp {NODE_IP}:80: connect: connection refused

My issue is resolved, it was DNS issue inside cert-manager deployment


Add build-* make targets to static checks in Github Actions

It would also be a good idea to test how to install it on MacOS

Kinda done


npm rxjs-run v 9.2.0 is invalid, needs to be retranspiled/published

I'm not clear on how this happened, but the lib files posted to npm for rxjs-run are out of sync with the source code.  It just needs to be retranspiled and republished to npm.
To check:

Install a fresh copy of @cycle/rxjs-run
Check lib/es6/index.js and you'll see that it still refers to Observable.from which is from Rxjs 5

+1

@staltz had to republish a v8 version because of a bug and most likely forgot to rebuild after changing back to the current version

Is that why v9.2.0 was published in the first place?  Was it meant to be published as a v8 version? I couldn't see any code changes between 9.1 and 9.2 so I'm not clear on what motivated it...

Yeah, because by accident v8 was made latest

Ah got it

What is the status of this? It seems like a serious issue if the latest NPM release is broken. Is it a simple fix?

@staltz is currrently in Barcelona, and my publish rights do not work at the moment, so expect one or two days more.

now fixed with 9.3.0


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/95 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target.git

Docs Build status updates of commit a6369a8:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Archive_master_2019-09-26-09-15-54 has been deleted or has been force pushed: fatal: Couldn't find remote ref Archive_master_2019-09-26-09-15-54

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Adding "ticker" as keyword

It may help for increasing hits!
inspiration from this old library😁
https://www.npmjs.com/package/react-ticker

Good idea!


fix: added missing properties to map

Easy change to add the new properties to the Map schema and update the state checker logic

closes #121


Feature/express api

Add endpoints for fetching users in a channel, channels user is in, and messages in a channel. Also adds endpoint for inserting messages into our database.

Looks good to me, merging it in


Design and implement "Apply to jobs" system

The system shall allow users to make use of an interface and underlying API that will make it possible for them to apply to jobs through postings and to know which jobs they have already applied to.

Renaud branch was merged here: https://github.com/SenecalRenaud/equipeBoucani-soen341project2023/pull/74
Integration details and basic description are provided in this PR.
The application system has since then been altered quite a bit, please refer to most recent commits


Restore original index with PandasParallelLFApplier

Describe the solution you'd like
Using PandasParallelLFApplier includes an index sort on the original DataFrame, which can result in unexpected row order if the index is not sorted when passed in. This should be documented, or the original index order should be restored.
Discussion: https://spectrum.chat/snorkel/help/how-to-use-the-pandasparallelapplier~cf50f563-28e6-418c-93a3-337384566c13
Additional context
Related issues: #1587 #1581 #1524

+1 to this. We just spent several cycles tracking down this issue in a model that uses Snorkel.

Not sure on the exact solution you were looking for on this, but one possibility would be to add an additional default keyword arg to PandasParallelLFApplier on whether to index sort or not.
For example, at line 97 within snorkel/snorkel/labeling/apply/dask.py, dd.from_pandas() is called:
df = dd.from_pandas(df, npartitions=n_parallel)
If you want the index to remain unsorted, and prevent the problem highlighted in this issue, we can simply call dd.from_pandas() like so:
df = dd.from_pandas(df, npartitions=n_parallel, sort=False)
We might not always want this to be false however, so it could be worth letting users call PandasParallelLFApplier with sort=True / False (False by default), as they require. Just a suggestion anyway!

Not sure on the exact solution you were looking for on this, but one possibility would be to add an additional default keyword arg to PandasParallelLFApplier on whether to index sort or not.
For example, at line 97 within snorkel/snorkel/labeling/apply/dask.py, dd.from_pandas() is called:
df = dd.from_pandas(df, npartitions=n_parallel)
If you want the index to remain unsorted, and prevent the problem highlighted in this issue, we can simply call dd.from_pandas() like so:
df = dd.from_pandas(df, npartitions=n_parallel, sort=False)
We might not always want this to be false however, so it could be worth letting users call PandasParallelLFApplier with sort=True / False (False by default), as they require. Just a suggestion anyway!


How to populate the correct initialization

See previous issue
"There is no "double initialization", this is the normal behaviour: the original select element is given a new class select-mania-original (in order to hide it), and the visible select-mania element is built with the select-mania class and more styling classes like the tiny one."
The problem is this. When populating the select-box dynamic in a script upon page load the hidden first initialized class "select-mania-original" gets populated and not the "Tiny" one.
Is there a way to copy the content from the "original" to "Tiny" after population or rather to fill the right class.
The loop that I'm using does this by 'getElementById' and I think because the HTML gives the class the Element name it gets automatically copied.
Kind regards
Maurice

I feel like you're trying to insert options in the original select dynamically, and update the select-mania element accordingly, right?
After inserting options in the original select element, you can call the update method to reflect changes to the built element.
Hope it helps, if not, can you provide some code and example?

I would be happy to provide some code but this is a pieve of software which can't be found online. Can you reach out to me on a pivate line? (email)

Ok let's do this! 👌

To give some insights: Here is the webdev view which hows only the original on gets filled. Even after the update the tiny is still empty.

I just emailed you on your hotmail address ;)

And it's in your mail box! Thank you!


Update Map Commands

To be done later this week/weekend

Map for all stations on Line 1 has been made, currently not going to do the two map system and instead just use one map to showcase what stations are on Line 1
Can not finish the command now because I need to upload this to imgur and school wifi is blocking that site for some reason
(Map is not this low-quality by the way)

Closing this because this has been done


Copy files without an extension properly

When I tried to publish my Jigsaw site with Github Pages, I noticed that jigsaw build production copied the CNAME file over incorrectly from source/ with a trailing . character.

I added a check for an empty $type and returns the path without the . in the file.

👍


feat: add linux/s390x builds

This PR adds builds for linux/s390x arch (to use it on zLinux).
There is a corresponding PR open in the kyverno repo to add support there as well:
https://github.com/kyverno/kyverno/pull/3277
Signed-off-by: skuethe<EMAIL_ADDRESS>

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2104

Relevant Lines:
2244

💛  - Coveralls

@skuethe thanks for your contribution I will tag the new versions and create a new Helm Release today

I released your feature with version 2.3.0 of the Helm Chart

Thank you!


feat: allow using any 3.x chokidar dependencies

PR Checklist

[x] Addresses an existing open issue: fixes part of #5114
[x] That issue was marked as status: accepting prs
[x] Steps in CONTRIBUTING.md were taken

Overview
Compatibility with newer @types/node releases for typescript users

I also tried an npm upgrade chokidar locally and re-running tests and such. They all worked. ✔

coverage: 94.358%. remained the same
when pulling 03934abe35bc36a93c18d89609636e6a03271ef3 on simhnna:bump-chokidar
into 99601da68d59572b6aa931e9416002bcb5b3e19d on mochajs:master.

This was released in<EMAIL_ADDRESS>🚀


Better Doze

Turn Doze from a single page module into a pager module
Add support for periodic toggle without the system as force doze can permanently force the device into doze mode on some systems.

Addressed in #40


Add ext::auth email verification

This might not be worth the trouble at the moment, but I'd recommend opting your code into stricter mypy checks in pyproject.toml

@msullivan

This might not be worth the trouble at the moment, but I'd recommend opting your code into stricter mypy checks in pyproject.toml

I actually just turned them off in my editor. At the moment, due to how the body of handle_request is just a big match statement, the LSP/typechecking was just completely broken (mostly complaining about every variable being unused). I plan on doing a big refactor to split out the routing and handling, but even before we got to this point, the amount of Unknown happening due to the cython <-> python translation made almost the entire file show as errors which was obscuring actual errors/typos.
I'm definitely 100% pro-types, and I know this draft PR is currently failing CI—I'm still working on manually testing the flow. Any advice or help getting better types for things like request, db, config stuff, etc. is absolutely welcome!


pexpect.spawn should use list of arguments

pexpect.spawn should use list of arguments instead of str.format.
import pexpect

path = '/tmp/dir-without-spaces'
child = pexpect.spawn('ls {0}'.format(path))
print(child.read())
child.close()

path = '/tmp/dir with spaces'
child = pexpect.spawn('ls {0}'.format(path))
print(child.read())
child.close()

path = '/tmp/dir with spaces'
child = pexpect.spawn('ls', [path])
print(child.read())
child.close()

In [1]: run test.py
file1.txt  file2.txt

ls: cannot access '/tmp/dir': No such file or directory
ls: cannot access 'with': No such file or directory
ls: cannot access 'spaces': No such file or directory

file1.txt  file2.txt

https://github.com/kennethreitz/pipenv/blob/master/pipenv/cli.py#L626
https://github.com/kennethreitz/pipenv/blob/master/pipenv/cli.py#L667

pull requests accepted!

Resolved with (8d31698).


Typed Framework for pipelined protocols

Develop a typed framework for pipelined protocols.
The criteria for submission are:

type level description for protocols
PingPong protocol with tests

using direct (in simulation and in IO)
connect and pipelined connect (in simulation and in IO)
using a channel over data channel, bytestring channel (in simulation and in IO)
using a local pipe

codec, channels and a driver

Done in a series of PRs:

#306 - use typed-protocols in ouroboros-network
#286 - request / response mini protocol tests
#275 - fixed kind inference in PeerPipelined
#260 - moved agency proofs to Protocol class
#257 - nix expression to build typed-protocols
#209 - implement typed-protocols with pipelining


[CI] Support ppc64le arch in Travis CI

Added power support for the travis.yml file with ppc64le. This is part of the Ubuntu distribution for ppc64le. This helps us simplify testing later when distributions are re-building and re-releasing. For more info tag @gerrith3.

Our CI doesn't use Travis anymore, but uses Azure DevOps now.
We only tested on x86 machines. This will surely be a better-to-have feature, but we haven't got any chance to test it.
I will look into it. Thanks for the contribution.

@srinivas32, do you have any chance to run the code in Travis with ppc64le?

@jiasli at the moment there is no ppc64le hardware in Azure.  We do provide free access to ppc64le through OSL here: https://osuosl.org/services/powerdev/ and of course free access to ppc64le architecture in travis-ci.com for testing.  We are looking into a golang github runner, but thus far we haven't gotten very far with bootstrapping .NET/.NET core on ppc64le which is otherwise necessary to connect to other coverage services.  The best we can offer at the moment is GHA for x86/x86-64 and Travis for ppc64le, s390x, arm, macOS...

I tested with on my own repo https://github.com/jiasli/knack/commit/cd8bbf1654c8e4531b202f5062d984752aae6c38.
The result shows ppc64le arch is working correctly:
https://travis-ci.com/github/jiasli/knack/builds/207393562

@srinivas32 @gerrith3 We have disconnect Travis anymore and no plan to bring it back for now. If you want to use Travis why not fork our repo, modify it as your request, and periodically sync with upstream?

@haroldrandom We'd rather avoid permanently forking a repo here.  We'll try and reconnect when we have ppc64le connected to GHA.


Add XR Tools editor menu

This pull request adds an XR Tools menu to the editor with the following settings:

Enable OpenXR
Set Physics Layers

Note: If we agree that the grapple-layer should be supported (https://github.com/GodotVR/godot-xr-tools/pull/426) then this PR should be modified to name that layer as well.


Can't see my character after botting without customized clothing

Reproduce steps
1.Signup with Pokemon club account type
2.Botting (started at level 1 without customization clothing)
3.Open real app after level 20
Issue is cannot see my character and got white screen after select customize menu

I got it too.
There should be a way to customize character after botting.
I think there should be a feature for customizing characters.


not able to create a client when lxd is installed from snap on artful

I discovered this while trying to use mojo installed from a snap. I have a new laptop where I've installed lxd from a snap. On my other machine, where lxd is installed from a deb, I can instantiate a client fine. But on this one, instantiation fails.
» python
Python 2.7.14 (default, Sep 23 2017, 22:06:14)
[GCC 7.2.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import pylxd
>>> pylxd.Client()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/codersquid/work/mojo/trunk/vpylxd/local/lib/python2.7/site-packages/pylxd/client.py", line 232, in __init__
    raise exceptions.ClientConnectionFailed()
pylxd.exceptions.ClientConnectionFailed
>>>

If I don't have a chance to investigate this, this section is where things were failing
https://github.com/lxc/pylxd/blob/master/pylxd/client.py#L246

any idea when a new version will be released?

This has now been fixed in 2.2.5 which has now been release.


Installation issue on MacOS/OSX

I attempted to install ogre_blender_importer in to Blender 2.77 using the following Terminal commands:
$ cd ~/Library/Application\ Support/Blender/2.77/
$ mkdir scripts
$ cd scripts
$ mkdir addons
$ cd addons
$ git clone https://github.com/lamogui/ogre_blender_importer.git

When going to Blender's File > User Preferences... > Add-ons > Import-Export and ticking "Import-Export: Ogre Blender Importer" I immediately got the following Python exception trace:
Traceback (most recent call last):
 File "/Users/username/Library/Application Support/Blender/2.77/scripts/addons/ogre_blender_imports/__init__.py", line 14, in <module> from OgreMeshSerializer import *
ImportError: No module named 'OgreMeshSerializer'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
 File "OgreMeshSerializer.py", line 17, in <module>
  except ImportError as e:
ImportError: No module named 'OgreMesgSerializerImpl'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
 File "/Applications/blender.app/Contents/MacOS/..Resources/2.77/scripts/modules/addon_utils.py", line 330, in enable mod = __import__(module_name)
 File "/Users/username/Library/Application Support/Blender/2.77/scripts/addons/ogre_blender_importer/__init__py", line 21, in <module>
  srcfile="OgreMesgSerializer.py"; exec(compile(open(os.path.join(directory,srcfile)).read(), srcfile, 'exec'))
 File "OgreMeshSerializer.py", line 26, in <module>
 File "/Applications/blender.app/Contents/MacOS/../Resources/2.77/python/lib/python3.5/encodings/ascii.py", line 26, in decode
  return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xC3 in position 2110: ordinal not in range(128)

In OgreMesgSerializerImpl.py, line 52 has:
        vSemantic = self._readUShorts(stream, 1)[0]; #Utilité du vertex
When I changed it to the following the add-on was loaded successfully when ticked:
        vSemantic = self._readUShorts(stream, 1)[0]; #Vertex utility
Seems that the Python library that ships with Blender for MacOS/OSX doesn't like UTF-8 characters, or maybe the Blender team hasn't configured it correctly. :(

I don't have OSX so I can't test...
Thx for feedback if you have time to do this now, if you do a little patch (remiving the "é" by "e") please pull request it I will be happy to merge


Invalid stream header: 1668D9AA

Expected Behavior
After latest security update of windows, my machine get restarted. I reopened my android project which started showing this error on gradle build start. Same error happening while I am trying to clean & rebuild my project in android studio (version 4.0).
Current Behavior
I am constantly getting error - Cause: invalid stream header: 1668D9AA in all of my android projects on gradle build.
Context
All of my android projects stopped working on my machine.
Steps to Reproduce
I am not sure how to reproduce but this is happening in all of my existing projects. I am using windows 10 home edition, Android studio version 4.0 & gradle version 6.1.1.
Your Environment
Android studio version 4.0 & gradle version 6.1.1.
Here is the detailed log of android studio -
idea.log

This error is gone after downgrading gradle version to 5.6.4.

@snattri Can you reproduce this with a more recent version (e.g. 6.5)?

Closing for lack of answer from original reporter.


modis colormap

Description
Noticed CI was not passing due to missing value specifying color is opaque. I've made the correction, but there was an issues with my branches and needed to create new PR.
Type of change
How Has This Been Tested?
Checklist:
Please delete options that are not relevant.

[X] I have performed a self-review

Looks like a linting failure: https://github.com/microsoft/planetary-computer-apis/runs/6311112419?check_suite_focus=true#step:3:2490. I think ./scripts/format should fix that up.


pull request for e2e test at 01/18/2017 15:15:13

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add option to see index of word/operands

when using SPIR-V it is common you need to index into a certain operand or word of the instruction it would be nice have some small value over the dissambly to see that
example
  2                  1   3   4
%20 = OpAccessChain %19 %14 %18

https://github.com/KhronosGroup/SPIRV-Visualizer/commit/e0e6ed370b31c76ac6d6f87876c9bc7a1eb6724b
instead of making it in the left pane, added it to the tool tip pane which provides a much simpler solution


Base code for pulsar signals

I'm starting this PR so that we can all see the direction that we are going. This PR is not ready to merge as I don't have any tests and the doc strings are pretty sparse. So of course we still need to nail down the multiple pulsar (spatially correlated analysis) but I think this should be merged first. Take a look and let me know what you think. I will get working on some tests...

OK, I have changed things a bit to be more flexible in terms of how we select indices for parameters. Previously if we wanted to do EFAC, EQUAD per backend then I had the by_backend flag for the class factories. However, that hardcodes that behavior and we would have to define another factory to do something different.
So to try to generalize this I've started a Selection factory, similar to how we use the Function factory to give arbitrary PSDs. The goal here is to make it so that when a 'Selection' class is passed to the signal, it will initialize with the pulsar and parameter and will automatically generate the masks required to compute the signal (i.e. which indices correspond to which backend or which time-segment). This is a bit tricky if we want this to not have information about the pulsar when we define the Selection class. At the moment I've done this by requiring that the arguments to the mask function (i.e the custom function that provides the mask for the parameters) be part of the pulsar object. However for things like ECORR we want to use epoch-averaged versions of things like the flags or toas, which are currently not part of the pulsar object. We could add them but I worry that this may lead to problems down the road when we want some complicated filtering.
Here is some code for how I imagine the API looking (the ECORR does not have this yet):
# pulsar information
parfiles = 'data/B1855+09_NANOGrav_11yv0.gls.par'
timfiles = 'data/B1855+09_NANOGrav_11yv0.tim'

psr = Pulsar(parfiles, timfiles)

# white noise parameters
efac = parameter.Uniform(0.5, 5)
equad = parameter.Uniform(-10, -5)
ecorr = parameter.Uniform(-10, -5)

# selection object to use parameters "per backend"
selection = Selection(utils.get_flag_masks)

# another selection to just naively have one two EFACS for the first and second half of data
def cut_half(name, toas):
    mid = (toas.max() + toas.min()) / 2
    ind = [toas <= mid, toas > mid]
    labels = ['t1', 't2']
    return [('_'.join([name, label]), ii) for ii, label in zip(ind, labels)]

selection2 = Selection(cut_half)

# EFAC and EQUAD per backend
ef = ws.MeasurementNoise(efac=efac, selection=selection)
ef2 = ws.MeasurementNoise(efac=efac, selection=selection2)
eq = ws.EquadNoise(log10_equad=equad, selection=selection)

# still need to figure out selection for ECORR
ec = gs.EcorrBasisModel(log10_ecorr=ecorr, by_backend=True)

# red noise
pl = Function(utils.powerlaw, log10_A=parameter.Uniform(-18,-12), gamma=parameter.Uniform(1,7))
rn = gs.FourierBasisGP(spectrum=pl, components=30)

# timing model
tm = gs.TimingModel()

# combined signal
s = ef + ef2 + ec + rn + eq + tm

# initialize
pm = s(psr)

I think this is really cool but it still needs some work. @vallis, you are good at this kind of thing. Want to take a look.
BTW, this functionality does not need to be limited to white noise, we could also use this to filter the rows of the F-matrix for "system" type noise.

Ok @vallis and I have simplified the selection function even more so that any user defined selections are very minimal. EFAC, EQUAD, and ECORR can now take any kind of selection. I still have to work on the FourierBasisGP class and get selection working with that (it is a bit different because we use the Function class for the parameters and spectrum). Getting closer!

So we are going to have problems with ECORR as it is coded now because we are using dictionaries which have no fixed order, so concatenating arrays based on the keys (as in the ECORR model) will not work. I'm mainly just putting this here so we remember that this needs to get changed...

Re dicts, perhaps OrderedDict is our friend here.

I think it is all taken care of now with normal dicts. I'll know for sure when I start writing tests!

Ok with the last commit, I think things are good to go. I have removed @vallis's changes as that should go in a different PR. I have written many (we are up to 87% coverage now!) tests for the signals and I'm 99.9% certain that everything is working fine. If you can think of any other tests to add now let me know.

Ok so we aren't quite done. It is probably best to just make this PR have the full pulsar signal, including multiple pulsars. So more tests!

With the last commit we at least have some coverage of the PTA class. There are some other scenarios that we can test in this PR but I don't want to go into huge detail since some of the underlying implementation (i.e sparse matrices, generic solve methods etc) will change in other PRs.

Ok, now that the tests finally pass I think we can merge this so that we have a stable base to work from in the future.


Add procedural and latino notation

I add the latino-american.js - Latino American Rhythm Pack to simplify the composition.
And equal-procedural.js - This notation is more intuitive or logic and better to reason. It may be useful for procedural music.
And update band.js, band.min.j to 1.1.3
According issues 30:
https://github.com/meenie/band.js/issues/30

I replace notation to numbers to eliminate quotation marks.


Link not clickable

The link to this video isn't clickable [!Video https://www.youtube.com/embed/TMzHAWEQjlk]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 05b23d72-33ed-a6a1-a442-a5e5cf039f9f
Version Independent ID: 4247cf37-3667-2007-7251-46ed80f58ef5
Content: Get started with the SharePoint Online Management Shell
Content Source: sharepoint/docs-conceptual/sharepoint-online/connect-sharepoint-online.md
Service: sharepoint-powershell
GitHub Login: @pamgreen-msft
Microsoft Alias: pamgreen

submitted pull request

submitted pull request

can you link to it? thanks


fix: cwd option not overwriting per command if specified in programmatic usage

Noticed this while using this library for the first time, so sorry if I missed something. The recently added cwd option for the programmatic usage works but the override for each command doesn't, it was just silently dropped. This should fix that issue. I also noticed there were no tests that would pick up on it, so added one, although I'm not well versed on writing tests so it may need some modifications.

@gustavohenke can you please merge this? This is a hot fix.

Published in v6.0.1!


Rare and non reproducible random crashes

I've seen that sometimes it just randomly crashes and gives a seg fault.
ive seen that the draw things app also crashes sometimes like that.
it could be when other processes are taking GPU memory or something.

Hi, if you have stacktrace, that would be helpful!
Also, s4nnc is largely not thread-safe, and meant to be operated within one thread, that might / might not be relevant.

I am not able to reproduce it again.
Thanks


Update CI and docs to remove references to default admin creds

Description
Starting in 2.12.0 release, security plugin is mandating an initial admin password to be set via env variable. This PR updates the docs and CI to accommodate this change.
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

https://github.com/opensearch-project/security/issues/3624

@dhrubo-os @greaa-aws can you folks take a look here and provide any feedback? This change will be happening for 2.12.0. Thanks!

This change should have failed multiple tests as test client still has "admin" as password.
https://github.com/opensearch-project/opensearch-py-ml/blob/5c93154bcfc04d8102d4d91294af36e02e0df802/tests/__init__.py#L38
I haven't looked into it properly. But, will take a look and respond.

@dhrubo-os @greaa-aws @ylwu-amzn Can we get some reviews on this PR?

Could you please resolve the merge conflict?

Could you please resolve the merge conflict?

Done

Merging this PR will require a issue in backlog so that we take care of updating passwords in the testcases and in other required places when we migrate to Opensearch>=2.12.0

@rawwar Thanks for the call out. Could you please create an issue for py-ml too? Thanks

@rawwar Thanks for the call out. Could you please create an issue for py-ml too? Thanks

Are you asking about #371?

@greaa-aws @ylwu-amzn @b4sjoo @jngz-es @rbhavna Could we get 1 more review on this? Is there anything blocking from getting this merged? We are targeting 2.12 version release for this change.


Saving notification

Addresses #305
Saving label appears on the "Edit variation" form whenever user starts typing and disappears when everything is saved.

Nice! 👏
@lithin can you fix this one linting error and move the styles to css modules?
/home/travis/build/carteb/carte-blanche/plugins/react/frontend/components/common/SavingLabel/index.js
  10:27  error  Unexpected block statement surrounding arrow body  arrow-body-style

Awesomeeee

It's hopefully okay now :) I got confused by the RandomButton styles...

Awesome thanks!


Add support for getting signed x509 cert

The changes in this PR are targeted to address high latency when number of client requests increase exponentially. Due to high latency, we see a lot of requests being cancelled by the client but the server still processes causing the server spending a lot of time waiting for signer from the pool.
As part of this PR we ensure that if the client has cancelled the request or timeout has occurred before server makes a request to HSM to sign a certificate the request will be cancelled.
The change is made for request type getting X509 Cert

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.

Codecov Report

Merging #61 (e8dcc6c) into main (1106fb5) will increase coverage by 1.62%.
The diff coverage is 89.06%.

@@            Coverage Diff             @@
##             main      #61      +/-   ##
==========================================
+ Coverage   71.34%   72.97%   +1.62%
==========================================
  Files          19       19
  Lines         862      962     +100
==========================================
+ Hits          615      702      +87
- Misses        233      246      +13
  Partials       14       14

Impacted Files
Coverage Δ

pkcs11/signer.go
59.41% <66.66%> (ø)

api/sshuser.go
87.00% <74.00%> (-13.00%)
:arrow_down:

api/sshhost.go
100.00% <100.00%> (ø)

api/x509cert.go
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c0d8212...e8dcc6c. Read the comment docs.


Simplify module setup around gdnative::globalscope + docs

Changes:

Add load() to prelude
Rename internal module gdscript -> globalscope
Module documentation for globalscope now visible again (moved from gdnative_core::globalscope)
Smaller doc tweaks

bors try

bors r+

bors r-

bors r+


Change html structure

It's better to use nav > ul > li > a structure for navigation
https://github.com/mickzle/KPI_Chores/blob/9acdad6a150c4d9630a4508212a909e986fee84d/3rd term/WEB design and technologies/Lab1/index.html#L15

is it better now? (lines 11-21)
also, should it be uses separetely or moved as an independent part inside a li {...} css style?

MICKZLE`S PRODUCT

ABOUT

PARTICIPANTS

CONTACTS

PREVIEW:

It's ok now.

It will be much easier to change something rather go to html/css files every time

i got you, then i`ll transfer it to the css file, thanks for the help! all the best🫡


Wrong implementation in base layers

Hello, and thanks for your amazing work!
As i see you have wrong logic in baselayers.
They meant to be mutually exclusive, but as i see with the top property,
i can have two of them showing in the same time.
This is not the case although.
I ll take a look if you dont have the time to fix it, and i ll post back.
Thanks again for this awesome library

Hi kozer, you can have more than one layer at time, but only the top one will be visible. Having more than one layer active shows a "layer selector" at the top-right (by default) cornet of the map. If you want to show more information inside a layer you must use overlays.
Any contribution is welcomed, please reopen if needed


Refactor kernel sim for the experimental kernel

This WIP refactors kernel-sim for the new experimental kernel. This is based on #992 and will supercede #992.

[x] Have you provided a meaningful PR description?
[x] Have you added a test, reproducer or referred to an issue with a reproducer?
[x] Have you tested your changes locally for CPU and GPU devices?
[x] Have you made sure that new changes do not introduce compiler warnings?
[ ] If this PR is a work in progress, are you filing the PR as a draft?

@diptorupd I think it's good to go.

@chudur-budur Thank you for the PR. However, the approach in the simulator implementation does not work with the kernel_api mock SYCL classes that has been implemented in numba-dpex.
I have added kernel executors in #1326 for Range and NdRange kernels that serve the purpose of executing the pure Python mock kernels. The kernel launcher does not yet support barriers, I will perhaps add that at a later date borrowing ideas from @Hardcode84's use of the greenlet package.
I am closing this PR.


adding remove logical volume

Signed-off-by: ChrisA.Walker<EMAIL_ADDRESS>Description
Introducing removing a logical volume.
Issues Resolved
https://github.com/chef-cookbooks/lvm/issues/124
Check List

[X] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD
[X] New functionality includes testing.
[X] New functionality has been documented in the README if applicable
[X] All commits have been signed for the Developer Certificate of Origin. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

Nicely done @ChrisAWalker . Thanks!


[#1018] test(tez) RssUnorderedPartitionedKVOutputTest add close func ut

What changes were proposed in this pull request?
tez-client, RssUnorderedPartitionedKVOutputTest add close func unit test
Why are the changes needed?
tez-client, RssUnorderedPartitionedKVOutputTest add close func unit test
Fix: #1018
Does this PR introduce any user-facing change?
No.
How was this patch tested?
unit test.

Codecov Report

Merging #1034 (ecb1162) into master (ecfed5e) will increase coverage by 1.51%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #1034      +/-   ##
============================================
+ Coverage     54.10%   55.61%   +1.51%
+ Complexity     2547     2094     -453
============================================
  Files           382      310      -72
  Lines         21728    13917    -7811
  Branches       1802     1255     -547
============================================
- Hits          11755     7740    -4015
+ Misses         9269     5756    -3513
+ Partials        704      421     -283

see 77 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Correct OSConfig import paths following name change

Tested via go build and go test

/retest

/gocheck

/gobuild


DelaySign with a public key.

Background:
It is not uncommon to have a assembly signing remote server that holds the private keys and public keys distributed to the developers to be used for delay signing.
Currently if specifying /delaysign and /keyfile=mypublic.snk is used with ilrepack, it fails with an error:
System.ArgumentException: Unable to obtain public key for StrongNameKeyPair.
at System.Reflection.StrongNameKeyPair.ComputePublicKey()
at System.Reflection.StrongNameKeyPair.get_PublicKey()
at ILRepacking.Steps.SigningStep.Perform()
at ILRepacking.ILRepack.Repack()
at ILRepacking.Application.Main(String[] args)
Acceptance criteria:
Given: i have a key file with only a public key called mypublic.snk
When: i run ilrepack with /delaysign and /keyfile=mypublic.snk
Then: i get a delay signed assembly as a result.

Hi, could it be you're hitting the same issue that was mentioned in PR #146 ?
This PR hasn't been followed upon, but feel free to give it a go.
Cheers.


Make the search buffer entry display customizable

Introduce elfeed-search-print-entry-function, a var that points to a function that inserts an entry into the *elfeed-search* buffer.

(defun feed-reader/search-print (entry)
  "Print ENTRY to the buffer."

  (let* ((feed-width 16)
         (tags-width 24)

         (title (or (elfeed-meta entry :title) (elfeed-entry-title entry) ""))
         (title-faces (elfeed-search--faces (elfeed-entry-tags entry)))
         (feed (elfeed-entry-feed entry))
         (feed-title
          (when feed
            (or (elfeed-meta feed :title) (elfeed-feed-title feed))))
         (tags (mapcar #'symbol-name (elfeed-entry-tags entry)))
         (tags-str (concat "[" (mapconcat 'identity tags ",") "]"))
         (title-width (- (window-width) feed-width tags-width 4))
         (title-column (elfeed-format-column
                        title (elfeed-clamp
                               elfeed-search-title-min-width
                               title-width
                               elfeed-search-title-max-width)
                        :left))
         (tag-column (elfeed-format-column
                      tags-str (elfeed-clamp (length tags-str) tags-width tags-width)
                      :left))
         (feed-column (elfeed-format-column
                       feed-title (elfeed-clamp feed-width feed-width feed-width)
                       :left)))

    (insert (propertize feed-column 'face 'elfeed-search-feed-face) " ")
    (insert (propertize tag-column 'face 'elfeed-search-tag-face) " ")
    (insert (propertize title 'face title-faces 'kbd-help title))))

Setting elfeed-search-print-entry-function to the above nets you something like this:

Merged as 997e504. Thanks!


create primitive set mapping name clash

in the create primitive set  function below, there seems to be a possibility of mapping name clash.
e.g. If len(lib.input_tokens) == 2, the integer 0 and 1 will be used to rename ARG0 and ARG1.
Further down, if index 0 and 1  of lib.tokens have arity > 0, they will be added to the pset with addPrimitive using 0 and 1 as name as well. Thus it overwrites the previous input_tokens.
Could you confirm if this happens, or am I missing something. Thanks!
def create_primitive_set(lib):
    """Create a DEAP primitive set from a dso.libraryLibrary."""

    pset = gp.PrimitiveSet("MAIN", len(lib.input_tokens))
    rename_kwargs = {"ARG{}".format(i): i for i in range(len(lib.input_tokens))}
    for k, v in rename_kwargs.items():

        # pset.renameArguments doesn't actually rename the Primitive.
        # It just affects the pset mapping. So, rename the primitive here.
        pset.mapping[k].name = v

    pset.renameArguments(**rename_kwargs)

    for i, token in enumerate(lib.tokens):
        # Primitives MUST have arity > 0. Deap will error out otherwise.
        if token.arity > 0:
            pset.addPrimitive(None, token.arity, name=i)

.....

I agree some primitives and input tokens (i.e., terminals) will have the same DEAP name for the reason you described. But I believe that DEAP differentiates between primitives and terminals. Namely, they use separate dictionaries, so it should be okay and there should not be any actual collisions of tokens. See https://github.com/DEAP/deap/blob/master/deap/gp.py.
Pretty sure this would break all the GP code if it tokens were actually colliding :P But let me know if you see any behavior issues!

I see, I printed out pset.mapping before and after  .addPrimitive is called, seems like the Terminals and Primitives are both in the same pset.mapping and overwritten when same name is used.


Feature Request: Support ignoring applying smarter hotkeys to CJK characters

Feature Requested
For CJK characters like 这是一个有意思的插件, I may want to make bold only the following three characters: 有意思. However, the current version of the plugin would make bold the entire sentence.
Therefore, it would be great if one can neglect applying smarter hotkeys to CJK characters. Or, there can be an option in the configuration pane, where the user can choose to apply smarter hotkeys to CJK characters or not. Instead, default Obsidian hotkeys can be applied for such cases.
Relevant Screenshot
No response
Which editor are you using?

[X] New Editor
[ ] Legacy Editor

Checklist

[X] I have checked that there isn't another hotkey plugin that does what I want.
[X] The feature would be useful to more users than just me.

After scanning through the code base, the issue can become very complex, for example, it may involve mixing with bullet list.
1. 第一个要点。
2. 第二个要点。
3. 第三个要点。

by selecting
个要点。
3. 第三个要点。

What is the user's intention?
It is better to fix the numbered list bold first. like #51


[DOCFIX] adding some user docs for ACL

@aaudiber some docs for ACL, PTAL.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/156/
Test PASSed.

Merged build finished. Test PASSed.

@aaudiber merged ACL docs with Security docs, and addressed all the applicable comments.  PTAL.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/172/
Test PASSed.

@aaudiber addressed comments, PTAL. Thanks.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/177/
Test PASSed.


Added support installing without setting hostname in ingress parameters

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
[stable/weave-scope] Title of the PR starts with chart name (e.g. [stable/mychartname])

With this repository being phased out in Aug 13(?), it might make sense to start looking at weaveworks/scope#3807


Added information about splinter and requests libraries in Python

Contribution to #65
Added Information about splinter and requests

Hey @vkartik97 , Thanks for contributing to AlgoWiki.


resolve #13 : extracted russian plural forms, supplemented russian test

I've just released new version which includes this fix: https://mvnrepository.com/artifact/pl.allegro.finance/tradukisto/1.0.1


Json poc

#4861
Alignement to abapGit repo

[x] zcl_abapgit_ajson* is used by mirrored objects. To avoid confusion, please use a different prefix. thanks
 see 539964ddd6222c2e

zcl_abapgit_ajson* is used by mirrored objects. To avoid confusion, please use a different prefix. thanks

zif_abapgit_aff_chko_v1.intf.abap copy the file from https://github.com/abapGit/aff_mirror/tree/main/src, it should be okay there. Later we will setup mirroring from that repo into abapGit

we need more INTF from the AFF, no automation yet

Can't wait for Quick-Fixing this kind of findings 🙃

https://github.com/abaplint/abaplint/issues/2239 opened for the quickfix

unused types: update the config

looks like it's coming along nicely 😃.
let's keep /src/objects for the object types only. suggestion:

move zcl_abapgit_json_cnt_handler to /src/objects/json
move /src/aff to /src/objects/aff

I agree on the folder topic. But keeping in mind that it is ABAP, than from the available 30 chars there would be 23 reserved due to folder convention?
zif_abapgit_objects_aff respectively zif_abapgit_objects_json contains already 23 character.
Any suggestion on that @mbtools ? Maybe drop the objects from the object name

navigation to CHKO object seems broken?

serialization of CHKO here #32dddca61057b95a852dcd1e362e2896740924cb
It kind of works, but still need the empty line as end-of-file marker.

We would like to check whether we can remove some domain specific code for CHKO and replace it with generic code using ABAP file formats (AFF). I see the option to get rid of some dynamic code for domain owners (e.g, code in https://github.com/abapGit/abapGit/blob/0962c9aa7caed17e6f3d8d34f6df5c5a20fa69cf/src/objects/zcl_abapgit_object_chko.clas.locals_imp.abap). This domain specific code is basically available in the domain-specific implementation and is just called by the generic AFF implementation. The generic AFF implementation must be dynamic to be syntactically correct also in releases where AFF is not available.
For new object types, like CHKO, this should be fine.

serialization of CHKO here #32dddca61057b95a852dcd1e362e2896740924cb
It kind of works, but still need

Is the file zma_chko_aff.chko.xml expected?

Some housekeeping items:

[ ] Descriptions of new packages/classes/interfacees should begin with abapGit - ..., except for zcl_abapgit_object_chko where we it should be CHKO - ATC Check Object
[ ] Add minimal test case to repo https://github.com/abapGit-tests/CHKO

Sidenote: As you know CHKO isn't available in 754 (ABAP Trial 1909) which limits who will be able to test any of this. I suggest adding another object type that's available in 754 as the next step.

please remove the changes to zcl_abapgit_objects from this PR. we already merged a solution for this part with #5254

close this PR? perhaps take a local backup with some of the code


Sinusoidal vs rope pe for image tokens

Any specific reason you went with sinusoidal (sd3 style) vs rope (flux style) positional encoding for image tokens?

Answer to my own question, base model uses rope, rope + sinusoidal work well together


Add pre-validation checks to PyValidator

This change is

Codecov Report

Merging #1100 (3df0a3d) into gilad/reconnect-native-blockifier (f9174a9) will decrease coverage by 0.29%.
The diff coverage is 0.00%.

@@                          Coverage Diff                          @@
##           gilad/reconnect-native-blockifier    #1100      +/-   ##
=====================================================================
- Coverage                              67.58%   67.29%   -0.29%
=====================================================================
  Files                                     51       51
  Lines                                   6501     6529      +28
  Branches                                6501     6529      +28
=====================================================================
  Hits                                    4394     4394
- Misses                                  1723     1751      +28
  Partials                                 384      384

Files
Coverage Δ

crates/native_blockifier/src/py_validator.rs
0.00% <0.00%> (ø)

:mega: Codecov offers a browser extension for seamless coverage viewing on GitHub. Try it in Chrome or Firefox today!


[Storage] Begin migration to test proxy

Description
This PR is meant to get the process kickstarted to migrate data-plane Storage packages to the test proxy. This introduces a new Storage test class, StorageRecordedTestCase, that inherits from the AzureRecordedTestCase that's used with the test proxy. Eventually, this new class can be renamed and completely replace StorageTestCase.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.


Communicating wgpu/gfx issues upstream

We should establish a good workflow for communicating issues like this to us for investigation. The best way we can suggest is following https://github.com/gfx-rs/wgpu/wiki/Debugging-wgpu-Applications#tracing-infrastructure
Practically, that would mean:

have a way to run with "trace" feature enabled in wgpu. There is no performance cost, but there may be a compile time cost, and I know you are sensitive to that too.
have a path to the trace folder configurable by some means
once you reproduce the problem, zip the trace folder, and attach it to a bug to https://github.com/gfx-rs/wgpu
don't forget to specify the revision of wgpu used (e.g. from your lockfile) as well as platform info

This is a very good idea. Thanks!
Its worth noting that right now we're using a custom (but unmodified) wgpu crate while we wait for the next official wgpu crates.io release.

I just added support for this and added a quick doc on it: https://github.com/bevyengine/bevy/blob/master/docs/debugging.md#wgpu-tracing
We will link to that doc whenever suspected wgpu issues come up.
@karroffel  @GabLotus keep this in mind when you're triaging issues.
@kvark would you consider this closed?


addSlider2D for multi renderers

It seems that addons.addSlider2D does not consider set related renderer. I added sliderWidget.SetCurrentRenderer(plt.renderer) before EnabledOn() to make the slider2D rendered on current renderer, it worked.
However, I found the coordinateSystem of sliderRep become confused.
For example, If SetCoordinateSystemToNormalizedDisplay(), the slider2D's origine is associated renderer's origine instead of window's origine. If SetCoordinateSystemToNormalizedViewport(), the final position is totally incomprehensible.
Any ideas?

It looks like it's a VTK bug.
Apparently GetPoint2Coordinate refers to the whole set of renderers while  GetPoint1Coordinate refers to the current renderer...
As you suggested, adding the line in addons.py (line438) before EnabledOn():
sliderWidget.SetCurrentRenderer(settings.plotter_instance.renderer)
then:
from vedo import *

def slider0(widget, event):
    value = widget.GetRepresentation().GetValue()
    sphere.color(value)

def slider1(widget, event):
    value = widget.GetRepresentation().GetValue()
    cube.color(value)

vp = Plotter(N=2, axes=1)

sphere = Sphere(r=0.6)
vp.show(sphere, at=0)
vp.addSlider2D(slider0,
               -9, 9,
               value=0,
               pos=([0.1,0.1],
                    [0.4,0.1]),
               title="slider0 color number")

cube = Cube()
vp.show(cube, at=1)
vp.addSlider2D(slider1,
               -9, 9,
               value=0,
               pos=([0.1,0.1],
                    [0.4,0.1]),
               title="slider1 color number")

vp.show(interactive=1)

produces:

@marcomusy Thanks for your reply. I tested with vtk python API only, it does have strange results when using slider2D in multi renderers. In your example, both Point1 and Point2 refer to their associated renderers. You can change the viewport of the renderer to see this.
Here is my test script with vtk. I found when I construnct the second vtkSliderWidget(), The first slider will disappear..
import vtk

def sliderfunc1(widget, event):
	value = widget.GetRepresentation().GetValue()
	print('slider 1: %f'%value)

def sliderfunc2(widget, event):
	value = widget.GetRepresentation().GetValue()
	print('slider 2: %f'%value)

def sphere(r,reso):
	shape=vtk.vtkSphereSource()
	shape.SetRadius(r)
	shape.SetThetaResolution(reso)
	shape.SetPhiResolution(reso)
	shape.Update()
	mapper=vtk.vtkPolyDataMapper()
	mapper.SetInputConnection(shape.GetOutputPort())
	actor=vtk.vtkActor()
	actor.SetMapper(mapper)
	return actor

def initialRep():
	sliderRep = vtk.vtkSliderRepresentation2D()
	sliderRep.SetMinimumValue(0.)
	sliderRep.SetMaximumValue(1.)
	sliderRep.SetValue(0.5)
	sliderRep.SetSliderLength(0.015)
	sliderRep.SetSliderWidth(0.025)
	sliderRep.SetEndCapLength(0.0015)
	sliderRep.SetEndCapWidth(0.0125)
	sliderRep.SetTubeWidth(0.0075)
	sliderRep.GetPoint1Coordinate().SetCoordinateSystemToNormalizedDisplay()
	sliderRep.GetPoint2Coordinate().SetCoordinateSystemToNormalizedDisplay()
	sliderRep.GetPoint1Coordinate().SetValue(0.1, 0.1)
	sliderRep.GetPoint2Coordinate().SetValue(0.4, 0.1)
	return sliderRep

window=vtk.vtkRenderWindow()
Interactor=vtk.vtkRenderWindowInteractor()
Interactor.SetRenderWindow(window)

Render1=vtk.vtkRenderer()
Render1.SetViewport(0,0,0.5,1)
window.AddRenderer(Render1)

actor=sphere(0.6,10)
Render1.AddActor(actor)
window.Render()

sliderRep=initialRep()
sliderWidget = vtk.vtkSliderWidget()
sliderWidget.SetCurrentRenderer(Render1)
sliderWidget.SetInteractor(Interactor)
sliderWidget.SetRepresentation(sliderRep)
sliderWidget.SetAnimationModeToJump()
sliderWidget.AddObserver("InteractionEvent", sliderfunc1)
sliderWidget.EnabledOn()

Render2=vtk.vtkRenderer()
Render2.SetViewport(0.5,0,1,1)
window.AddRenderer(Render2)

actor=sphere(0.6,4)
Render2.AddActor(actor)
window.Render()

sliderRep=initialRep()
sliderWidget = vtk.vtkSliderWidget()
sliderWidget.SetCurrentRenderer(Render2)
sliderWidget.SetInteractor(Interactor)
sliderWidget.SetAnimationModeToJump()
sliderWidget.SetRepresentation(sliderRep)
sliderWidget.AddObserver("InteractionEvent", sliderfunc2)
sliderWidget.EnabledOn()

Interactor.Initialize()
window.Render()

Interactor.Start()

The error above is that you reuse sliderWidget. Rename it to sliderWidget2 and it works.
The effect of the bug is that the 0.4 value somehow refers to the coordinate system of the window in size  but shifted in the viewport (use 0.5 to see the result).

Yes, I understood. Maybe I have to report the bug for VTK.

Yes - that would be a good idea!
(btw also sliderRep should be renamed)

BTW: For python, we do not have to rename the varible. New  assignment should have no influence on the old one. I do not know why here is not.


Public API review

Here I track progress on public API review

[x] Naming consistency
[x] "Interop" suffix
[x] "Async" suffix
[x] Public members listing
[x] Expose interface
[x] Namespace/inner classes

I won't touch the current public api surface even though many public setters are here only for serialization purpose. I will wait until .NET 5 is out to make those internal


Prep for Arduino IDE Release of Cpp-Crypto

For Cpp-Crypto to be released in the Arduino IDE, the following must be done:

Create "arduino" branch.
Merge https://github.com/sleepdefic1t/cpp-crypto/tree/arduino to the "arduino" branch.
Tag/Release 0.3.0-arduino targeting the "arduino" branch (*first).
Tag/Release 0.3.0 targeting Master (*second).

@faustbrian @kristjank @supaiku0
At this time, I need an "arduino" branch.
After my PR is merged to the "arduino" branch, we can proceed with release/tagging.

https://github.com/ArkEcosystem/cpp-crypto/tree/arduino
Let me know when you made the changes needed so I tag the arduino release.

@faustbrian #67

https://github.com/ArkEcosystem/cpp-crypto/releases/tag/0.3.0-arduino


fix: Adding a 'legacy_names' var to support older v17 name schemes

Description
Adding a true/false variable like legacy_names shown here allows users to deploy the v18+ module using the older v17 style naming conventions for resources.
Motivation and Context
One of the breaking changes introduced in v18 is a change to the naming_prefixes used by almost all resources. These new naming prefixes cannot be overridden so previous "<worker_name>" resources will be destroyed and replaced by "<worker_name>-node-group" resources or the like.
Adding a legacy_names var allows small conditionals that can choose the new v18-style prefixes or the older v17-style prefixes so the v17 resources aren't destroyed/replaced just for a non-functional name change.
Breaking Changes
No breaking changes. A legacy_names var should default to false so existing deployments would be unaffected.
How Has This Been Tested?
Tested during the process of updating our own v17 cluster to v18. The variable defaulting false means it will be ignored by any implementation that doesn't actively set it to true in order to use the v17 matching names.

we have provided support for var.prefix_separator which v18.x defaults to "-", but you can set to "" to match v17.x behavior and this prevents the control plane resources from re-creating. However, we are not offering support for prior node group naming scheme or backwards compatibility. You can remove the prior node groups from Terraform state (and therefore Terraform's control) and provision new node groups. Once the new node groups are provisioned, you an cordon and drain the old node groups and finally remove once the last pods are removed

Thanks for taking the time with your comment. I'm already aware of the prefix_separator attribute though and that seems to only solve part of the upgrading problem.
Using the v18 defaults, TF plan shows many changes like this. The hyphen is an added change that forces a replacement, but so is the addition of "-cluster".
"staging2-eks" -> "staging2-eks-cluster-"

Setting an empty prefix_separator does remove the trailing hyphen, but still doesn't address the addition of "-cluster" so the name difference still forces a replacement.
Here are some excerpts from the upgrade plan (v17.24 -> v18.9) using prefix_separator = "", so you can see that the cluster itself is being replaced and not just the node group resources.
Cluster IAM Role name change forces replacement:
# module.eks.aws_iam_role.this[0] must be replaced
...
~ name_prefix           = "staging2-eks" -> "staging2-eks-cluster" # forces replacement

Cluster Security Group name change forces replacement:
# module.eks.aws_security_group.cluster[0] must be replaced
...
~ name_prefix            = "staging2-eks" -> "staging2-eks-cluster" # forces replacement

Replacing either the cluster security group or the cluster IAM role will force a replacement of the EKS cluster itself.
# module.eks.aws_eks_cluster.this[0] must be replaced
...
~ role_arn                  = "arn:aws:iam::XXXXXXXXXXXX:role/staging2-eks20210422154717366200000004" -> (known after apply) # forces replacement
...
~ vpc_config {
    ~ cluster_security_group_id = "sg-0e46ecc973ce1b40f" -> (known after apply)
    ~ security_group_ids        = [
        - "sg-0ca6cf076f4d195de",
      ] -> (known after apply) # forces replacement

Adding a legacy_names attribute like the one in this PR will allow the older naming patterns ("NAME") to be upgraded without affecting any current deploys that use the new naming patterns ("NAME-cluster-"). It seems like a small consideration to make for those of us hoping to upgrade. Since resource names are a non-functional change, why not allow us to keep our existing names/resources so we aren't forced to rebuild our clusters?

have you tried setting:
prefix_separator                   = ""
iam_role_name                      = $CLUSTER_NAME
cluster_security_group_name        = $CLUSTER_NAME
cluster_security_group_description = "EKS cluster security group."

Ref: https://github.com/terraform-aws-modules/terraform-aws-eks/issues/1744#issuecomment-1027359982

I tried that originally and just set those for another TF plan now. Originally I set those hoping to fix all of the resource renaming, but found node resources still being replaced (as you mentioned earlier). I did miss that these changes will keep the cluster resources (IAM role & security group) though, so thanks for point that out.
So the block above allows us to keep existing v17 clusters and we just need to do the node group swap you mentioned earlier.
Thanks for taking the time to clarify this!


gitkraken: fix broken interpreter after recent update

Description of changes

This hopes to fix #206240
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

I can confirm that this works as expected, now :)

Please follow the contributing guide when naming your commits.

I just tested it and it still fails. What parameters did you use for strace?

strace -f gitkraken
What do ldd $(which gitkraken) and file $(which gitkraken) say?

> ldd $(which gitkraken)
	linux-vdso.so.1 (0x00007fffe3b8c000)
	libc.so.6 => /nix/store/ayfr5l52xkqqjn3n4h9jfacgnchz1z7s-glibc-2.35-224/lib/libc.so.6 (0x00007f37be686000)
	/nix/store/ayfr5l52xkqqjn3n4h9jfacgnchz1z7s-glibc-2.35-224/lib/ld-linux-x86-64.so.2 => /nix/store/ayfr5l52xkqqjn3n4h9jfacgnchz1z7s-glibc-2.35-224/lib64/ld-linux-x86-64.so.2 (0x00007f37be891000)

> file $(which gitkraken)
/run/current-system/sw/bin/gitkraken: symbolic link to /nix/store/zkcn5hb5xf5gfkffg5yg0j4918a8cq47-gitkraken-9.0.0/bin/gitkraken

strace -f gitkraken
trace.txt

Hm, I forgot that file would not  follow symlinks by default :-D
Can you also do file -L $(which gitkraken)?

> file -L $(which gitkraken)

/run/current-system/sw/bin/gitkraken: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /nix/store/ayfr5l52xkqqjn3n4h9jfacgnchz1z7s-glibc-2.35-224/lib/ld-linux-x86-64.so.2, for GNU/Linux 3.10.0, not stripped

I think this might be a different problem than the one I fixed in this PR:
[2904161:0115/203658.856659:FATAL:gpu_data_manager_impl_private.cc(448)] GPU process isn't usable. Goodbye.
Does it display anything at all? Does gitkraken --disable-gpu work?

I think this might be a different problem than the one I fixed in this PR:
[2904161:0115/203658.856659:FATAL:gpu_data_manager_impl_private.cc(448)] GPU process isn't usable. Goodbye.
Does it display anything at all? Does gitkraken --disable-gpu work?

--disable-gpu fixes this issue. Thank you for the help.

For the impatient:
(gitkraken.overrideAttrs ({ pname, postFixup, ... }: {
  postFixup = ''
    ${postFixup}
    pushd $out/share/${pname}
    for file in chrome-sandbox chrome_crashpad_handler; do
      patchelf --set-interpreter "$(cat $NIX_CC/nix-support/dynamic-linker)" $file
    done
    popd
  '';
}))


Prepare Alpha Ids package to Beta 1

Packages impacted by this PR

@azure-tools/communication-alpha-ids

Issues associated with this PR
--
Describe the problem that is addressed by this PR
NOTE: This is a private SDK intended for internal use only. This SDK will not be officially supported
This prepares the short codes SDK for the beta 1 release.
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
--
Are there test cases added in this PR? (If not, why?)
--
Provide a list of related PRs (if any)
--
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

API change check
API changes are not detected in this pull request.


Game crashes when starting a game after update 5.01

The game crashes when you start a game after the last update 5.01. I've experienced some crashes before, but it has always been related with me minimizing the game - and therefore easily avoidable.
I've tried injecting after the game has been launched successfully, but it then also crashes the client.
Game works fine without overlay running, but thanks to your mod 60fps is now unplayable hehe.

Oh, I don't remember updating the overlay after 5.00 was released. My bad, so sorry.


Add failing loopback test

With strong-globalize fixed, there is still a remaining bug in loopback reported by @gijo-varghese.
The test is failing with the following error:
/private/var/folders/v0/cjlw1c6d2_zfqp3v0pqshd3m0000gn/T/39e4e63c55ba1/webpack:/node_modules/strong-globalize/lib/helper.js:80
    assert(validPath, '*** setRootDir: Intl dir not found under: ' + rootPath.toString());
^
AssertionError [ERR_ASSERTION]: *** setRootDir: Intl dir not found under: /private/var/folders/v0/cjlw1c6d2_zfqp3v0pqshd3m0000gn/T
    at Object.setRootDir (/private/var/folders/v0/cjlw1c6d2_zfqp3v0pqshd3m0000gn/T/39e4e63c55ba1/webpack:/node_modules/strong-globalize/lib/helper.js:80:1)
    at Function.SetRootDir (/private/var/folders/v0/cjlw1c6d2_zfqp3v0pqshd3m0000gn/T/39e4e63c55ba1/webpack:/node_modules/strong-globalize/lib/strong-globalize.js:62:1)
    at Object.<anonymous> (/private/var/folders/v0/cjlw1c6d2_zfqp3v0pqshd3m0000gn/T/39e4e63c55ba1/webpack:/node_modules/loopback/lib/globalize.js:10:1)
    at __webpack_require__ (/private/var/folders/v0/cjlw1c6d2_zfqp3v0pqshd3m0000gn/T/39e4e63c55ba1/webpack:/webpack/bootstrap:19:1)
    at Object.<anonymous> (/private/var/folders/v0/cjlw1c6d2_zfqp3v0pqshd3m0000gn/T/39e4e63c55ba1/webpack:/node_modules/loopback/lib/server-app.js:7:1)
    at __webpack_require__ (/private/var/folders/v0/cjlw1c6d2_zfqp3v0pqshd3m0000gn/T/39e4e63c55ba1/webpack:/webpack/bootstrap:19:1)
    at Object.<anonymous> (/private/var/folders/v0/cjlw1c6d2_zfqp3v0pqshd3m0000gn/T/39e4e63c55ba1/webpack:/node_modules/loopback/lib/loopback.js:12:1)
    at __webpack_require__ (/private/var/folders/v0/cjlw1c6d2_zfqp3v0pqshd3m0000gn/T/39e4e63c55ba1/webpack:/webpack/bootstrap:19:1)
    at Object.<anonymous> (/private/var/folders/v0/cjlw1c6d2_zfqp3v0pqshd3m0000gn/T/39e4e63c55ba1/webpack:/node_modules/loopback/index.js:11:1)
    at __webpack_require__ (/private/var/folders/v0/cjlw1c6d2_zfqp3v0pqshd3m0000gn/T/39e4e63c55ba1/webpack:/webpack/bootstrap:19:1)

This seems to still effectively be a bug in strong-globalize in that its dynamic algorithm is trying to load an internationalized folder we weren't able to detect.
This is a tricky one - will put some thought to it.

I've added two fixes here to get loopback to work:

There was a bug with directory asset emission stopping further assets from being emitted, which will be an important fix to get out.
I relaxed the restriction on directory asset emission to emit the nested directories and also to emit base-level package directories. The reason for this is that loopback/intl is expected to be available, but we only know from static analysis that it is accessing something in the loopback folder so we emit the whole thing.

(1) is uncontroversial.
(2) on the other hand will increase the output directory size quite a bit as it will potentially emit entire packages from node_modules. We could potentially look at ways to cut this back with various filtering heuristics (for example, hardcoding that any directory called "intl" should be emitted). But this really depends on if the added dist footprint is going to be a problem.
I'd suggest running tests for (2) to check how it affects output sizes and if that is going to be a problem or not.
If we want to wait on (2) as well, I can separate the fix from (1) in a different PR to get things moving with that in the mean time.

Codecov Report

Merging #117 into master will increase coverage by 0.38%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #117      +/-   ##
==========================================
+ Coverage   75.11%   75.49%   +0.38%
==========================================
  Files          10       10
  Lines         450      453       +3
==========================================
+ Hits          338      342       +4
+ Misses        112      111       -1

Impacted Files
Coverage Δ

src/loaders/relocate-loader.js
92.99% <100%> (+0.47%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8032a35...120a166. Read the comment docs.

I managed to put together some numbers for this from the integration tests:

analytics-node - no assets, unaffected
apollo - no assets, unaffected
auth0 - no assets, unaffected
aws-sdk - no assets, unaffected
axios - no assets, unaffected
azure-cosmos - no assets, unaffected
azure-storage - no assets, unaffected
bugsnag-js - no assets, unaffected
firebase-admin - 10,049kB -> 10,155kB
strong-globalize - 3,701kB -> 6,800kB
pdfkit - 2573kB -> 2573kB
jimp - 1068kB -> 1943kB

Looking at these numbers more closely it seems like we might actually be good to go on this one...!

This looks great. I think over-fitting is fine when FS stuff is involved, as to always prioritize that the programs work, first and foremost.


Update pleeease to 4.0.5

Due to Warning "v8::ObjectTemplate::Set() with non-primitive values is deprecated" pleeease need to be updated to work properly on current node version

This shouldnt be needed, minor ane patches are picked automatically.


chore: add react-output-target

Preflight Checklist

[x] I have read the Contributing Guidelines for this project.
[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the pull request tracker for a Pull Request (PR) that matches the one I want to submit, without success.

Issue
This PR Closes #1333
Pull request checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[ ] Build (yarn build) was run locally and any changes were pushed
[ ] Lint (yarn lint) has passed locally and any fixes were made for failures

Changes
Changes in this pull request:

add react-output-target

Browsers
I tested the build on the following browsers:

[ ] Firefox Desktop
[ ] Chrome Desktop
[ ] Edge Desktop
[ ] Safari Desktop
[ ] Chrome Mobile
[ ] Safari Mobile

Screen readers
I tested the build on the following browsers:

[ ] JAWS Firefox Desktop
[ ] JAWS Chrome Desktop
[ ] NVDA Firefox Desktop
[ ] NVDA Chrome Desktop
[ ] VoiceOver Safari Desktop
[ ] VoiceOver Chrome Desktop
[ ] VoiceOver Safari Mobile
[ ] Android Accessibility Suite Chrome Mobile

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

Does this introduce a breaking change?

[ ] Yes
[ ] No

Other information

This will be continued in #1360


Make string() and charStream() BOM-aware.

Closes #2707. Closes #2819.

Yep, this is exactly what we want. Nice change.

LGTM

LGTM!

Hmm weird string decoding problems on Java 7. Will look later.

Looks good to me too. Tested all BOMs - working correctly.
When is a release expected? ;-)

Okay so I guess I've tested everything but BOM8.
The bom you've written in the new PR was sadly not copied correctly, and has a typo.
#2994


Can't find Nethereum.JsonRpc.UnityClient.dll ...

Nethereum.JsonRpc.UnityClient.dll is missing from the packages and therefore I can't use Unity Functionality...

An update on the template is out now, let me know how it goes


[SSoC 2.0] GYM Responsive Website

Project title - GYM Website
Project Description

Showing effects of cards
Responsive for the small devices.
Creative and professional look with best attractive user interface
Adding animations
Creating a FAQ section
Adding a feedback form, etc.

Doc Domain

[x] Solidity , Html, Css , JavaScript , Web3.js / Ether.js
[] Solidity , ReactJs /NextJs , Web3.js /Ether.js
[] Solidity , Python3 , Web3.py
[] Other , feel free to mention below

Are you contributing under any open-source program ?
Yes, SSoC 2.0 program

@Vikash-8090-Yadav @shubhisingh184 sir, please assign this to me so to start working on it

@Avdhesh-Varshney assigned to you. Start working on it.


Remove extra quotes from website HSTS

Type of Change

Tool Source: Config generator

What issue does this relate to?
Fixes #195
What should this PR do?
Removes extra quotes that were present in the HSTS header for a single website.
What are the acceptance criteria?
Have two websites in the tool one with HSTS enabled and one without.
The HSTS header in the config file for the site with it enabled should not have extra single quotes around it.

cc @etam


Mistral-7B-instruct-v0.1 compatibility with main.py

Hi,
I managed to install mistral-7b-v.01 on a server and run the main.py script as recommended, and it works well. I wanted to test the model's abilities in chat completion, so I downloaded Mistral-7b-instruct-v0.1. But when running the same commands as for mistral-7b-v0.1, the main.py program does not work (see error below). More specifically the model.py script included in the mistral folder does not seem compatible with Mistral-7b-instruct-v0.1.
Do you know how to resolve this problem?
Thank you
` > python -m main interactive Mistral-7B-instruct-v0.1/
Traceback (most recent call last):
File "/home1/USERS/PSY-DEV/brunet/anaconda3/lib/python3.10/runpy.py", line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/home1/USERS/PSY-DEV/brunet/anaconda3/lib/python3.10/runpy.py", line 86, in _run_code
exec(code, run_globals)
File "/home1/USERS/PSY-DEV/brunet/llama/mistral-src/main.py", line 142, in
fire.Fire({
File "/home1/USERS/PSY-DEV/brunet/anaconda3/lib/python3.10/site-packages/fire/core.py", line 141, in Fire
component_trace = _Fire(component, args, parsed_flag_args, context, name)
File "/home1/USERS/PSY-DEV/brunet/anaconda3/lib/python3.10/site-packages/fire/core.py", line 475, in _Fire
component, remaining_args = _CallAndUpdateTrace(
File "/home1/USERS/PSY-DEV/brunet/anaconda3/lib/python3.10/site-packages/fire/core.py", line 691, in _CallAndUpdateTrace
component = fn(*varargs, **kwargs)
File "/home1/USERS/PSY-DEV/brunet/llama/mistral-src/main.py", line 106, in interactive
transformer = Transformer.from_folder(Path(model_path), max_batch_size=3)
File "/home1/USERS/PSY-DEV/brunet/llama/mistral-src/mistral/model.py", line 218, in from_folder
model_args = ModelArgs(**json.loads(f.read()))
TypeError: ModelArgs.init() got an unexpected keyword argument 'use_biases'`

Fix: Go to Mistral folder (Mistral-7B-instruct-v0.1), and change contents of "params.json" to
{"dim": 4096, "n_layers": 32, "head_dim": 128, "hidden_dim": 14336, "n_heads": 32, "n_kv_heads": 8,  "norm_eps": 1e-05, "vocab_size": 32000, "sliding_window":3}

wget https://files.mistral-7b-v0-1.mistral.ai/mistral-7B-v0.1.tar
tar -xf mistral-7B-v0.1.tar

it works well.

I am experiencing the same problem as @nvidal01 - I can get Mistral-7B-v0.1 to run and generate sensible text.  But the instruct version of the model (Mistral-7B-Instruct-v0.1) does not run, due to unexpected keywords in the params.json config file.  If I remove keywords from params.json until I stop getting TypeErrors, as @JohnTailor did, I can get Mistral-7B-Instruct-v0.1 to run.  But results are nonsensical.  It would be very helpful to have a working example of the Instruct model.

Ah sorry about that !
We'll update the examples and fix that stray param ...


send_info fails with permission problems

We have noticed that make send_info (aka dspace healthcheck) fails when run under cron.
All cronjobs are run as user tomcat7. When run manually as user tomcat7, make send_info tries to run sudo just after successfully running Log Analyser Check. Cron has the following configuration:
00 04     * * 1   tomcat7     cd /project/lindat-dspace/source/utilities/project_helpers/scripts; make send_info
I can see that the makefile includes the following under target add_cronjobs:
        (crontab -l ; echo "00 04     * * 1     cd $(BASE); sudo make send_info") | crontab -
Our repository is currently running:
 commit 563543d1dafe01c1058fd578690dfb695571acad
Is this a configuration issue, a change/update we skipped by mistake or something else?
(Thank you for your assistance.)
-jan

@kvorg sorry for taking so long to reply, somehow I missed this issue.
The issue is a line in the additional info check which calls sudo cat /proc/user_beancounters, which is very specific to our machines. Overall the whole check is outdated an will be refactored in #443.
The check used to log build time, uptime, few interesting urls, few variables and the beancounters. If you don't find these interesting you can disable the additional info check (by deleting this line) or you could remove the beancounters call in the check itself by removing these three lines


Calliope: Set brightness with parameter 0 not working

Describe the bug

The description of the block "setBrightness" says that "0 means all leds are turned off, 9 is the brightest value." However, when the brightness is set to 0, it has the same brightness as if the brightness was set to 9.

Screenshots

This program will produce the error

Device information

Type: Desktop
OS: Windows 10
Browser: Chrome

Additional context

Note that there is a similar block, which sets the brightness for a specific LED. That block will
work correctly(not display anything) when brightness is set to 0.
This program will work correctly

Needs testing whether this is the case for the real robot as well.

0 brightness works correctly on the real Calliope.

Resolved by GCI student in 4b71015.


Nuxt3 my persist sets different storage modes and fails

Are you using Nuxt?

[X] Check this box if you encountered the issue using Nuxt and the included module.

Describe the bug
"@pinia-plugin-persistedstate/nuxt": "1.2.1",
"pinia": "2.2.0",
"nuxt": "3.9.3",
"vue": "3.4.3"
Recently, my localStorage and sessionStorage settings for storage failed, which had been working fine before.They all are set to localStorage
this is my config:
persist: [
{
paths: ['ip', 'langs'],
storage: persistedState.localStorage
},
{
paths: ['dialogType'],
storage: persistedState.sessionStorage
},
{
paths: ['sortType', 'cookiePolicy'],
storage: persistedState.cookiesWithOptions({ expires: new Date(new Date().getTime() + 365 * 24 * 60 * 60 * 1000) })
}
]
Reproduction
https://stackblitz.com/edit/nuxt-starter-gsr2f4?file=store%2Fapp.ts
System Info
Win

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] The provided reproduction is a minimal reproducible of the bug.

Hi can you please try with the latest nuxt module included in the base package v4 ?
https://prazdevs.github.io/pinia-plugin-persistedstate/frameworks/nuxt.html

Hi can you please try with the latest nuxt module included in the base package v4 ?
https://prazdevs.github.io/pinia-plugin-persistedstate/frameworks/nuxt.html

thanks your reply, i solved this issues,  it may be because the latest version of pinia-plugin-persistedstate renamed the paths to pick, i fixed it and now it works.

This is probably due to cache ? I remade the docs from scratch to match v4. Sadly they are english only, this is maybe why you get 404 if you try to look for Chinese docs.
I will put a message to look for contributors willing to help translate the docs 🫡
Closing this as fixed!

This is probably due to cache ? I remade the docs from scratch to match v4. Sadly they are english only, this is maybe why you get 404 if you try to look for Chinese docs.
I will put a message to look for contributors willing to help translate the docs 🫡
Closing this as fixed!

yes, Chinese docs is 404, thank for your reply again~  but i think that issues is not due to cache,  this is because the parameter paths was renamed to pick, which caused it to fail.

Oh yes, i meant cache for the docs, not the plugin :)
It has been documented in the docs that paths is now pick because you can also exclude/omit paths in v4 🎉


Feature request: Enable automatic conversion to builtin types when parsing

Feature Request
I'd like to be able to parse JSON into types containing date and url typed properties. Potentially a way to assert/validate that automatically converts if possible would also be nice.
My concrete use case is I have a type
type LastUpdated = Partial<Record<JobType, Date>>

That tracks the last updated time for pulling the results of a batch job and I want to be able to save and load from that type directly, but currently when loading I need to manually convert like this which just introduces a bunch of extra code (and for other types where this behavior is more nested becomes much harder to maintain.
  assert<LastUpdated>(
    Object.fromEntries(
      Object.entries(JSON.parse(contents.toString()) as Record<JobType, string>).map(([key, value]) => [
        key,
        new Date(value),
      ]),
    ),
  );

It looks like https://github.com/samchon/typia/issues/372 already added some special casing for these types so maybe this support could build on top of that?

Sorry, no plan to support.


feat(UserLabel): add size property

[x] Update storybook docs
[x] Tests

Size xl has not round shape:

Thanks for contribution!


Can't disable a casein_select

I'd like to disable a select option in certain conditions. In the past I've successfully used disabled: true like this:
= casein_text_field f, f.object, :field, disabled: true

But the select doesn't seem to work.
= casein_select f, f.object, :field, {test: 1}, disabled: true

This results in a working select drop down.
Is it possible to disable a casein_select field? If so, how should I change my code to work properly?

This version of Casein is for Rails 2.x. Can you confirm you're still using this one, and not the latest? (github.com/russellquinn/casein)

Ops! Sorry, my mistake. I'll move this to the correct repo.