"Lock file" error on "Step 10/19" on make patch images

Hi.
After running make patch images, on "Step 10/19", an error appears:
Step 10/19 : RUN npm ci --prod
 ---> Running in 950bdcb000bc
npm WARN config production Use `--omit=dev` instead.
npm ERR! code EUSAGE
npm ERR!
npm ERR! `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing.
npm ERR!
npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR!
npm ERR! Clean install a project
npm ERR!
npm ERR! Usage:
npm ERR! npm ci
npm ERR!
npm ERR! Options:
npm ERR! [-S|--save|--no-save|--save-prod|--save-dev|--save-optional|--save-peer|--save-bundle]
npm ERR! [-E|--save-exact] [-g|--global] [--global-style] [--legacy-bundling]
npm ERR! [--omit <dev|optional|peer> [--omit <dev|optional|peer> ...]]
npm ERR! [--strict-peer-deps] [--no-package-lock] [--foreground-scripts]
npm ERR! [--ignore-scripts] [--no-audit] [--no-bin-links] [--no-fund] [--dry-run]
npm ERR! [-w|--workspace <workspace-name> [-w|--workspace <workspace-name> ...]]
npm ERR! [-ws|--workspaces] [--include-workspace-root] [--install-links]
npm ERR!
npm ERR! aliases: clean-install, ic, install-clean, isntall-clean
npm ERR!
npm ERR! Run "npm help ci" for more info

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2023-07-27T21_27_03_382Z-debug-0.log
The command '/bin/sh -c npm ci --prod' returned a non-zero code: 1

More of the output

# you can edit excalidraw.env.production to change endpoints
cp excalidraw.env.production excalidraw/.env.production
cp excalidraw.dockerignore excalidraw/.dockerignore
Sending build context to Docker daemon    6.9MB
Step 1/10 : FROM node:14-alpine AS build
 ---> 0dac3dc27b1a
Step 2/10 : WORKDIR /opt/node_app
 ---> Using cache
 ---> 25b5736578cd
Step 3/10 : COPY package.json yarn.lock ./
 ---> Using cache
 ---> 4b552c2173c8
Step 4/10 : RUN yarn --ignore-optional --network-timeout 600000
 ---> Using cache
 ---> 229c9e84bb97
Step 5/10 : ARG NODE_ENV=production
 ---> Using cache
 ---> 6888937c6459
Step 6/10 : COPY . .
 ---> Using cache
 ---> 2b48cefe3a5e
Step 7/10 : RUN yarn build:app:docker
 ---> Using cache
 ---> 9e6b5d2a64e4
Step 8/10 : FROM nginx:1.21-alpine
 ---> b1c3acb28882
Step 9/10 : COPY --from=build /opt/node_app/build /usr/share/nginx/html
 ---> Using cache
 ---> 7fbdc91daeb1
Step 10/10 : HEALTHCHECK CMD wget -q -O /dev/null http://localhost || exit 1
 ---> Using cache
 ---> e2322dc297d6
[Warning] One or more build-args [COMMIT] were not consumed
Successfully built e2322dc297d6
Successfully tagged excalidraw:v0.1.0-6c3da92
Sending build context to Docker daemon    298kB
Step 1/9 : FROM node:12-alpine
 ---> bb6d28039b8c
Step 2/9 : WORKDIR /excalidraw-room
 ---> Using cache
 ---> 32e137a17b7c
Step 3/9 : COPY package.json yarn.lock ./
 ---> Using cache
 ---> 11aad932c141
Step 4/9 : RUN yarn
 ---> Using cache
 ---> 27c3841c4608
Step 5/9 : COPY tsconfig.json ./
 ---> Using cache
 ---> 9497a88b95bb
Step 6/9 : COPY src ./src
 ---> Using cache
 ---> dc51d8e9565d
Step 7/9 : RUN yarn build
 ---> Using cache
 ---> 460c002d1b5a
Step 8/9 : EXPOSE 80
 ---> Using cache
 ---> 426ec4a215fe
Step 9/9 : CMD ["yarn", "start"]
 ---> Using cache
 ---> 4aa3c3d44036
[Warning] One or more build-args [COMMIT] were not consumed
Successfully built 4aa3c3d44036
Successfully tagged excalidraw-room:v0.1.0-6c3da92
Sending build context to Docker daemon  822.3kB
Step 1/19 : FROM node:16-alpine as builder
 ---> d22e42cbfdbb
Step 2/19 : RUN apk add --update python3 make g++
 ---> Using cache
 ---> 5f1f7db154b3
Step 3/19 : RUN npm install -g eslint
 ---> Using cache
 ---> 6ca5fe7af870
Step 4/19 : RUN npm install -g @nestjs/cli
 ---> Using cache
 ---> fb9ec2c7bb45
Step 5/19 : WORKDIR /app
 ---> Using cache
 ---> 5258004fa2a5
Step 6/19 : COPY package.json .
 ---> Using cache
 ---> d987d0c6c618
Step 7/19 : COPY package-lock.json .
 ---> Using cache
 ---> b562279862ee
Step 8/19 : RUN npm install
 ---> Using cache
 ---> 0d81d5692ac7
Step 9/19 : COPY . .
 ---> Using cache
 ---> 5a7e4ead41b3
Step 10/19 : RUN npm ci --prod
 ---> Running in 950bdcb000bc
npm WARN config production Use `--omit=dev` instead.
npm ERR! code EUSAGE
npm ERR!
npm ERR! `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing.
npm ERR!
npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR!
npm ERR! Clean install a project
npm ERR!
npm ERR! Usage:
npm ERR! npm ci
npm ERR!
npm ERR! Options:
npm ERR! [-S|--save|--no-save|--save-prod|--save-dev|--save-optional|--save-peer|--save-bundle]
npm ERR! [-E|--save-exact] [-g|--global] [--global-style] [--legacy-bundling]
npm ERR! [--omit <dev|optional|peer> [--omit <dev|optional|peer> ...]]
npm ERR! [--strict-peer-deps] [--no-package-lock] [--foreground-scripts]
npm ERR! [--ignore-scripts] [--no-audit] [--no-bin-links] [--no-fund] [--dry-run]
npm ERR! [-w|--workspace <workspace-name> [-w|--workspace <workspace-name> ...]]
npm ERR! [-ws|--workspaces] [--include-workspace-root] [--install-links]
npm ERR!
npm ERR! aliases: clean-install, ic, install-clean, isntall-clean
npm ERR!
npm ERR! Run "npm help ci" for more info

npm ERR!
What could I try doing to resolve the issue?

Please try these commands, and find out which one cause problem.
make images TARGETS=excalidraw
make images TARGETS=excalidraw-room
make images TARGETS=excalidraw-storage-backend

Fixed.

Please try these commands, and find out which one cause problem.
make images TARGETS=excalidraw
make images TARGETS=excalidraw-room
make images TARGETS=excalidraw-storage-backend

update: I found make images TARGETS=excalidraw-storage-backend produce the error, I'm working on it.

Hi. Sorry I didn't answer before.

Fixed by #19 .

I confirm that the issue seems resolved. Thank You very much for Your help and all! I managed to have the instance up and running. :tada:


[[clients]] shouldn't require name=s

The whole infrastructure around them involves referring to them by name, but it probably makes sense to just automatically generate name values at conf load time if a name isn't provided.

https://github.com/oxy-secure/oxy/commit/ca0ec9a0f1d0bc2477f0627199afe59da70bf8fa


Add exclude query for list and reset-batch command

What changed?
Add exclude query for list command

Why?
ElasticSearch doesn't allow join operation, so this exclude query will do it
https://github.com/uber/cadence/issues/4671

How did you test it?
Tested in my prod env

Potential risks
None

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 83060ab5-d52c-4a24-987d-3f1aab1b1b14

10 of 69 (14.49%)  changed or added relevant lines in 2 files are covered.
43 unchanged lines in 7 files lost coverage.
Overall coverage decreased (-0.02%) to 57.021%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

tools/cli/workflowCommands.go
5
64
7.81%

Files with Coverage Reduction
New Missed Lines
%

common/task/fifoTaskScheduler.go
2
87.63%

common/task/weightedRoundRobinTaskScheduler.go
2
89.12%

service/history/execution/mutable_state_builder.go
2
69.66%

common/cache/lru.go
3
90.73%

service/history/task/fetcher.go
4
86.15%

common/persistence/nosql/nosqlplugin/cassandra/tasks.go
14
72.8%

common/persistence/nosql/nosqlTaskStore.go
16
58.37%

Totals

Change from base Build 9ae87487-02a4-45b5-a201-7b9139583b00:
-0.02%

Covered Lines:
82926

Relevant Lines:
145431

💛  - Coveralls


NEXT-8603 Don't load multiple bundles from plugins

1. Why is this change necessary?
In theory any plugin can load additional bundles but when someone else already adds this bundle the plugin can't be activated.
2. What does this change do, exactly?
The plugin loader keeps track of every bundle name it emits and prevents from emitting a bundle twice.
3. Describe each step to reproduce the issue or behaviour.

Have two plugins serving at least one same additional bundle that both share
Plugin activation not possible due to duplicate bundle loading within symfony

4. Please link to the relevant issues (if any).
https://issues.shopware.com/issues/NEXT-8603
#858
5. Checklist

[x] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hello! :) Would you mind giving us some more information on how to test this PR? Is there any behaviour change affecting the user?

@leichteckig this is an improvement for plugin developers who would like to ship additional bundles/composer packages.
so maybe @JoshuaBehrens could provide two example plugins and if they are both installed and Shopware still works normally, everything should be ok

@leichteckig and @mitelg I provided two a test case that is not working because it fails in loading my new plugin and bundle fixtures. Maybe someone can help me out there.

I rechecked running it locally again and my plugin gets loaded locally without any further changes. How can we find out what is missing here?

I rechecked running it locally again and my plugin gets loaded locally without any further changes. How can we find out what is missing here?

This PR should be good to go, after https://github.com/shopware/platform/pull/896#pullrequestreview-411695831 is resolved.

Change is pushed

Thanks for contributing!

Nice :shipit: 🎉
You're welcome 💜


Split core library from gradle plugin

What is this pull request for? Why do you create this pull request?
Fixes #102, also pretty much prerequisite for #155, alternative to #104
What is changed?
All the core stuff is now separated from the gradle plugin. I tried to maintain compatibility.

I haven't really tested for compatibility yet and so I just hope that everything still works as intended, it seems good though.
The publishing is probably broken too (non existent for core).

I also fixed some warnings, updated the code style to the new standard code style and some other minor stuff that just popped up.

And I removed some files from git that don't belong there (all auto generated idea files)

I also moved some new gradle stuff to .kts because it's just better at checking, completion and everything's kotlin anyways.

Also the whole thing is more like a starting point. There's probably a lot to optimize and modularize afterwards.

@cromefire
Looks good. let me see the detail :+1:

@cromefire
Excuse me, how could I execute test?
./gradlew test simply?

Yeah I think so, it's been some time but I don't think I actually changed much of the functionality, other than to split it into 2 projects.

I merged your branch to feature/split and executed the test as:
kenjiotsuka2@KenjinoMacBook-puro ~/project/harmonica
 % ./gradlew :core:test

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.5/userguide/command_line_interface.html#sec:command_line_warnings

BUILD SUCCESSFUL in 811ms
3 actionable tasks: 3 up-to-date

but in my understanding, there are more tests. 🤔

Fixed, gradle was missing the junit platform mode

Let me just port the other gradle script too, so it's unified

It's all kts now, have to check the core publishing though, but probably not today.

@cromefire
Thank you, but how can I test?

@cromefire
Sorry it looks working!

@cromefire
thanks! merged,

@ashokgelal
I merged this and split the core parts

The one thing left to look out for is if the publishing of the core library to your upstream maven repo is properly working, but think you still use the deprecated jCenter, so that might need an overhaul anyway.


Document that per-schedule configuration can also be set using schedules env key in meltano.yml

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2031
Originally created by @DouweM on 2020-05-15 16:25:05

View 4 previous comments from the original issue on GitLab


crash on DEFINE AXIS with T range missing

Reported by Ansley B Manke on 22 Mar 2005 21:45 UTC
DEFINE AXIS /t0="1-jan-1861"/units=months/t myt
*** NOTE: /UNIT=MONTHS is ambiguous ... using 1/12 of 365.2425 days
STOP Illegal calendar in tm_secs_to_date() statement executed
The /T=lo:hi:del is missing -- this should issue an error and continue.  See
xeq_define, calls to RESET_SECS_FROM_BC.  variables start, end, and prev_cal_id
are set to unspecified_val8 and unspecified_int4, in which case we should just
skip the calls to RESET_SECS_FROM_BC.
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1203

Comment by<EMAIL_ADDRESS>on 23 Mar 2005 19:09 UTC
fixed in xeq_define.F


How to combine LetsEncrypt existing certificate with "-existing-webserver"?

mox, when run with the flag -existing-webserver, will generate this config:
# public > TLS >

KeyCerts:
        -

                # Certificate including intermediate CA certificates, in PEM format.
                CertFile: path/to/correo.domain123-chain.crt.pem

                # Private key for certificate, in PEM format. PKCS8 is recommended, but PKCS1 and
                # EC private keys are recognized as well.
                KeyFile: path/to/correo.domain123.key.pem
        -

                # Certificate including intermediate CA certificates, in PEM format.
                CertFile: path/to/mta-sts.domain123-chain.crt.pem

                # Private key for certificate, in PEM format. PKCS8 is recommended, but PKCS1 and
                # EC private keys are recognized as well.
                KeyFile: path/to/mta-sts.domain123.key.pem
        -

                # Certificate including intermediate CA certificates, in PEM format.
                CertFile: path/to/autoconfig.domain123-chain.crt.pem

                # Private key for certificate, in PEM format. PKCS8 is recommended, but PKCS1 and
                # EC private keys are recognized as well.
                KeyFile: path/to/autoconfig.domain123.key.pem

And these existing LetsEncrypt ones:
$ sudo ls -al /etc/letsencrypt/live/domain123.com
total 12
drwxr-xr-x 2 root root 4096 Nov  6 07:26 .
drwx------ 6 root root 4096 Nov  6 07:26 ..
lrwxrwxrwx 1 root root   36 Nov  6 07:26 cert.pem -> ../../archive/domain123.com/cert1.pem
lrwxrwxrwx 1 root root   37 Nov  6 07:26 chain.pem -> ../../archive/domain123.com/chain1.pem
lrwxrwxrwx 1 root root   41 Nov  6 07:26 fullchain.pem -> ../../archive/domain123.com/fullchain1.pem
lrwxrwxrwx 1 root root   39 Nov  6 07:26 privkey.pem -> ../../archive/domain123.com/privkey1.pem
-rw-r--r-- 1 root root  692 Nov  6 07:26 README

Which of these should I add into the mox.conf? There're 4 pairs in mox.conf. Should I remove 3 of them leaving 1?
And for the 1 left, which 2 out of the 4 in  /etc/letsencrypt/live/domain123.com should I use in mox.conf?
For instance, in nginx config  I'll use the fullchain and privkey one. But mox requires a chain one which is different already.

If you don't want to use MTA-STS and autoconfig, you could disable MTA-STS for each domain (in domains.conf) and disable autoconfig (in mox.conf), and remove the key/cert pair in mox.conf for them. MTA-STS makes SMTP delivery with STARTTLS required, so I would try to keep that enabled. Autoconfig is useful for some email clients, making it easier to set up a new account. I would at least try to keep MTA-STS enabled.
Without MTA-STS and autoconfig, I think that should leave only 1 pair, for the hostname itself (if you have a 4th pair, for what domain is it?). KeyFile should point to privkey.pem. I'm pretty sure CertFile should point to chain.pem. It's likely fullchain.pem includes the root certificate, but there's no point sending that to TLS clients: Either they already have it and trust it, or they don't have it and won't trust it even if you send it.
Keep in mind the certificate should be for the hostname where mox is running (e.g. mail.yourdomain.example), not for your domain directly (so not for yourdomain.example). With a certificate for the domain, TLS certificate verification will fail during SMTP STARTTLS due to hostname mismatch.
Mox also includes a webserver. It can serve static files and serve as reverse proxy. It's easily configurable (through config file and web admin that updates the config file). It does transparent and cached compression. And it will automatically fetch TLS certificates for new domains you add, through let's encrypt. So it could be worth trying to use it. It has made my life simpler (I used to run nginx too).
Keep in mind that mox does not currently automatically refresh certificates from disk. So you should probably configure some kind of hook in the tool that fetches certificates (certbot?) that restarts mox after a certificate refresh.

Mox also includes a webserver. It can serve static files and serve as reverse proxy. It's easily configurable (through config file and web admin that updates the config file). It does transparent and cached compression. And it will automatically fetch TLS certificates for new domains you add, through let's encrypt. So it could be worth trying to use it. It has made my life simpler (I used to run nginx too).

You suggest that I switch to the websever of mox for multiple websites that I run on the same machine and for which I know use nginx?

You suggest that I switch to the websever of mox for multiple websites that I run on the same machine and for which I now use nginx?

Yes. (:
If it is an option of course. And that depends on whether you're using features of nginx that mox doesn't support. I've implemented everything I needed, but some more functionality could be added. Though mox is not going to be as configurable as nginx.

The question is also which file-certificate of Letscrypt to use for MTA-STS and Autoconfig.

I think I don't understand the question. Your directory listing is for domain123.com. For MTA-STS I would expect a directory mta-sts.domain123.com with the same set of files as the listing earlier. And for autoconfig a directory autoconfig.domain123.com. For your mail host I would expect something like .domain123.com, not domain123.com. Because each email domain needs 3 certificates, it can get annoying to handle it with a separate tool (certbot). That's why I switched to mox also for my HTTPS TLS needs.

Didn't work. Worked with cert1 and fullchain1

What was in those files? I would expect cert1 to be a single certificate, without intermediates. And chain1 to contain cert1 + 1 or more intermediates. And fullchain1 to be cert1 + intermediates + root. If using just cert1 seems to work, that may be because your devices happen to already know about the intermediates from other TLS connections. But not all devices may already know those intermediates, and some may see TLS connectivity issues. So I think you should load the intermediates.


prepare_proxy: do not redirect inbound traffic to Envoy

Disable redirecting all pod inbound traffic to Istio's Envoy sidecar proxy.
Traffic is already filtered by Cilium when used in conjunction with Istio.

@rlenglet: Adding do-not-merge/release-note-label-needed because the release note process has not been followed.

One of the following labels is required "release-note", "release-note-action-required", or "release-note-none".
Please see: https://github.com/kubernetes/community/blob/master/contributors/devel/pull-requests.md#write-release-notes-if-needed.
Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Hi @rlenglet. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


How to change weights ordering of saved keras model

Hey
Is it possible to train a model with theano dim ordering, save weights and then run it with tensorflow dim ordering?
Thanks!

Found this looks promising I'm going to try it

OK I tried the method using convert_kernel as the link suggested.  I did the following:
1.I ran it when dim was for theano i.e th
2. loaded the model from th file
3.I saved it for tf convert_kernel(original_w, dim_ordering="tf")
4.I change keras dim to tf
5. I tried to load the converted model again and got dim problem
It seems that it is not enough to change the following layers  ['Convolution1D', 'Convolution2D', 'Convolution3D', 'AtrousConvolution2D']:
The error I get is:

ValueError: Cannot feed value of shape (1024, 256, 1, 1) for Tensor u'Placeholder_156:0', which has shape '(1, 1, 256, 1024)'

The is fully connected to fully connected. What am I missing while converting th to tf ?
Thanks!

@oak-tree You can use my script weight_conversion_theano.py (https://github.com/titu1994/Keras-Classification-Models) to convert your model trained in theano with th dim ordering to :

Tensorflow with tf dim ordering (this is what you want)
Tensorflow with th dim ordering (delete later)
Theano with tf dim ordering (delete later)

Follow the instructions in the script and edit it wherever it mentions.

@titu1994 thanks i'll check it out. Can you explain to me why there is a need to shuffle the fc layers if there are more than 1 layer?

I found another issue. I have a complex model. Some kind of graph model. Iterating over model.layers only gets the basic node of graph` and does not show all graph layers.

@oak-tree The script works for all types of models, it only needs the model to be built so as to handle tf and th dim ordering.
Use a script to build the models, once with th dim ordering and another with tf dim ordering. Then just execute the script. It handles graph (functional api) models.


ALLOW PROGRAMMERS TO CHANGE IDENTITY DEFAULT PAGES

Let's face it, this issue is never getting resolved, because @Microsoft only cares about making money off of programmer's misery.

I have spent 15 hours hammering away at this issue, and I'm done.


javax.imageio.IIOException: Illegal band size

Description
Derivans fails to read image due limited access, i.e. missing permissions.
Actual
The tool encounters the resource, but keeps on moving to the next stage.
There it reports finally  (App:45) java.io.FileNotFoundException: /var/lib/tomcat9/kitodo-hotfolder/work_361768028/IMAGE_80/00000020.jpg (No such file or directory)
Expected
The Tool should fail fast and report properly the image's identification.
Instead just logging an error like 2023-04-24 08:32:18 [ERROR] (ImageDerivateerJPG:47) render /var/lib/tomcat9/kitodo-hotfolder/work_361768028/IMAGE_FOOTER/00000020.jpg: Can't read input file! it should throw an exception.

It looks like it's not a problem regarding permissions but with somewhat broken and not processable image data

The actual reason is: 2023-04-26 08:16:35 [ERROR][ForkJoinPool-1-worker-7](ImageDerivateerJPG:48) processing error /home/hartwig/ulb-exporter/exporter-work-dir/361768028/MAX/00000020.tif:Illegal band size: should be 0 < size <= 8
Common Image IO is not capable to write JPEG images with depth beyond 8bit, but in this case the input images has 16bit per channel.

noted in README


Enhancement: Improve Test cases Maintainability and Remove Magic Numbers on test/exclude_times_test.test.js, test/filter_times_test.test.js and test/include_times_test.test.js

Description
This issue is to propose an enhancement to the project by improving the maintainability of certain test cases and removing magic numbers from the test cases which will be helpful for the developers to easily understand the codebase.
Motivation and Benefits

Enhancing test case maintainability will lead to more readable and understandable code.
Removing magic numbers will make the code more robust and easier to maintain

Related Files/Code

test/exclude_times_test.test.js
test/filter_times_test.test.js
test/include_times_test.test.js

Sounds good

Hi @martijnrusschen ,
I created this issue based on the review comments I got on one of my previous PRs (https://github.com/Hacker0x01/react-datepicker/pull/4319#discussion_r1359640157).  Can you assign this issue to me? I'll update the test cases for the mentioned files

@martijnrusschen, Thank you for assigning this refactor ticket to me.  I created a PR for this - https://github.com/Hacker0x01/react-datepicker/pull/4335.  Kindly review it and let me know if any changes required.


Change Reportname of merged version from ZABAPGIT_FULL to ZABAPGIT_STANDALONE

closes #3829

thanks, lets try merging it 😄

looks like it worked https://raw.githubusercontent.com/abapGit/build/master/zabapgit.abap

yea 👍


make a copyright file.

Please make a copyright file with an adequate license, perhaps GPL 3 or 2  so it can be fit for distribution purposes.

I added one thank you :)


Expose _isMockObject as utility

Do you mind having a function "isMockObject" that tests the property _isMockObject within the object?
I often come across this in a project where there is a transition from vanilla vitest to extend vitest (this project):
// https://github.com/eratio08/vitest-mock-extended/blob/31ea7aaebab51fc2f418ba210db6ca153166a1c3/src/Mock.ts#L160
const isMockObject = <T extends object>(objt: T): objt is MockProxy<T> =>
  '_isMockObject' in objt;

const mockHttpService = (
  httpService: HttpService | MockProxy<HttpService>,
  customResponse: Partial<AxiosResponse | AxiosError>,
) => {
  const mockedResponse: AxiosResponse = {
    ...mock<AxiosResponse>(),
    ...customResponse,
  };

  if (isMockObject(httpService)) {
    httpService.get.mockReturnValueOnce(of(mockedResponse));
    httpService.post.mockReturnValueOnce(of(mockedResponse));
    httpService.delete.mockReturnValueOnce(of(mockedResponse));
    return;
  }

  vi.spyOn(httpService, 'get').mockReturnValueOnce(of(mockedResponse));
  vi.spyOn(httpService, 'post').mockReturnValueOnce(of(mockedResponse));
  vi.spyOn(httpService, 'delete').mockReturnValueOnce(of(mockedResponse));
};

It's small and useful.
I could create a PR that does just this:
const isMockObject = <T extends object>(objt: T): objt is MockProxy<T> =>
  '_isMockObject' in objt;

If it makes sense and you want it.

@RickStanley feel free to create a pr with tests. I will gladly approve it


Robyn allocator doesn't accept vector format of the date_range

Project Robyn
Describe issue
Robyn allocator doesn't accept vector format of the date_range.
AllocatorCollect <- robyn_allocator(
  InputCollect = InputCollect,
  OutputCollect = OutputCollect,
  select_model = select_model,
  date_range = date_range
  total_budget = total_budget, # Total budget for date_range period simulation
  channel_constr_low = channel_constr_low,
  channel_constr_up = channel_constr_up,
  channel_constr_multiplier = channel_constr_multiplier, # Customise bound extension for wider insights
  scenario = scenario,
  export = export
)

The above code works fine if
date_range <- "last_91"
However, it produces an error if
date_range <- c("2023-01-01", "2023-04-01"),

Running budget allocator for model ID 2_285_1 ...
Date Window: 2023-01-01:2023-04-01 (91 days)
Error in if (date_range == "all") { : the condition has length > 1
Calls: main -> optimize -> robyn_allocator -> which_usecase
In addition: There were 20 warnings (use warnings() to see them)
Execution halted

Provide reproducible example
Environment & Robyn version
Make sure you're using the latest Robyn version before you post an issue.

Check and share Robyn version: packageVersion("Robyn")
‘3.10.3’
R version (Please, check and share: sessionInfo() or R.version$version.string)
4.3.1 (2023-06-16)

Closing this issue as an update to the Robyn version solved the problelm


Update issue templates

Coverage remained the same at 43.384% when pulling def601ae1f92f471bf2d15d5581dbc5352bd2ef2 on leonwanghui-patch-1 into 2da153fe858293bd009c8b76b7653a5301c58346 on development.

Close it for now


ORM not set correctly in config/initializers/devise.rb when using Mongoid and ActiveRecord

I am using both ActiveRecord and mongoid. My User model is using ActiveRecord but when mongoid is being used, "rake db:migrate" becomes confused and assumes User is a Mongoid document and results in the following error:
$> rake db:migrate
rake aborted!
undefined method `devise' for User(Table doesn't exist):Class
Tasks: TOP => db:migrate => environment
(See full trace by running task with --trace)
A workaround when running "rake db:migrate" is to manually change the config/initializers/devise.rb file by changing:
require 'devise/orm/mongoid'
to:
require 'devise/orm/active_record'
However, I shouldn't have to manually do this. If I generate the User model using:

rails g active_record:devise User

Then devise should automatically generate the config/initializers/devise.rb with the correct settings for the ORM.
I am using Ruby 1.9.2p290, Rails 3.1.0, Mongoid 2.3, bson_ext 1.4, and Devise 1.5.3.
Best,
Mike

If you are using Devise with User and User is ActiveRecord, the line on config/initializers/devise.rb must be:
require 'devise/orm/active_record'
Devise is not assuming that it is mongoid the default, mongoid is the one configuring Rails to say it is the default. You shuold probable set config.generators.orm = :active_record if you want to use Active Record most of the cases.

Hi Jose,
My point is that "rails generate" allows one to revert back to ActiveRecord--even though Mongoid is the default--by using the command

rails g active_record:devise ModelName

Is it possible to do this for "rake db:migrate" without having to manually change config/initializers/devise.rb or the config.generators.orm setting? If not, then it becomes rather kludgy if one wants to use multiple ORMs.
Mike

From: Jos Valim<EMAIL_ADDRESS>To: mykoweb<EMAIL_ADDRESS>Sent: Tuesday, January 24, 2012 12:14 AM
Subject: Re: [devise] ORM not set correctly in config/initializers/devise.rb when using Mongoid and ActiveRecord (#1595)
If you are using Devise with User and User is ActiveRecord, the line on config/initializers/devise.rb must be:
require 'devise/orm/active_record'
Devise is not assuming that it is mongoid the default, mongoid is the one configuring Rails to say it is the default. You shuold probable set config.generators.orm = :active_record if you want to use Active Record most of the cases.

Reply to this email directly or view it on GitHub:
https://github.com/plataformatec/devise/issues/1595#issuecomment-3628906

No, you need to explicitly load Devise for them ORMs you are using, otherwise you will keep running into failures.

Not sure if I follow you. What I'm asking for is a way to dynamically configure devise depending on which ORM I am using.
If I am only using one ORM, then devise works fine as is. If I am using multiple ORMs (in my case Mongoid and ActiveRecord), then the Issue that I filed is requesting that there be a way to dynamically tell Devise which ORM I am using for a particular model.
How does that sound?

From: Jos Valim<EMAIL_ADDRESS>To: mykoweb<EMAIL_ADDRESS>Sent: Tuesday, January 24, 2012 12:50 AM
Subject: Re: [devise] ORM not set correctly in config/initializers/devise.rb when using Mongoid and ActiveRecord (#1595)
No, you need to explicitly load Devise for them ORMs you are using, otherwise you will keep running into failures.

Reply to this email directly or view it on GitHub:
https://github.com/plataformatec/devise/issues/1595#issuecomment-3629281

There isn't a way to dynamically do it.  If you are using Devise with both ActiveRecord and
Mongoid, you need to require BOTH in your config/initializers/devise.rb.

Okay, thanks, Jos. I was hoping there would be a way to do it dynamically. I have a workaround that I can live with.
I will also close this issue if you haven't already done so.
Best,
Mike

From: Jos Valim<EMAIL_ADDRESS>To: mykoweb<EMAIL_ADDRESS>Sent: Tuesday, January 24, 2012 1:20 AM
Subject: Re: [devise] ORM not set correctly in config/initializers/devise.rb when using Mongoid and ActiveRecord (#1595)
There isn't a way to dynamically do it.  If you are using Devise with both ActiveRecord and
Mongoid, you need to require BOTH in your config/initializers/devise.rb.

Reply to this email directly or view it on GitHub:
https://github.com/plataformatec/devise/issues/1595#issuecomment-3629574


Not everything i've disabled is being removed

Hi!
I've just installed the rich-text editor and have the following options:
Bold, Underline, Italic, Ordered list, bullet, and a link.
Unfortunatly I'm still able to paste in all sorts of H's elements and colored text. The clear formatting button works to remove it. But I thought it wouldn't be pasted in in the first place.
Alternatively, if I can let the clear formatting trigger on the on-change action this issue would be solved as well :)
We're running the latest mendix project.

Dear Jan,
Thank you for reporting this. At the moment the sanitize option will remove all tags that are not allowed.
https://github.com/mendixlabs/rich-text/blob/11c1815f228a1181618f5e28bf76faab9f990d78/src/components/RichText.ts#L119
We see this as a feature request, and will discuss the possibility with the product owner.
Cheers, Andries


feat: Add support for Android devices with 16 KB page size

Hello,
I'm working on a Capacitor project which uses capacitor-community-sqlite-6.0.2. Using an Android 15 emulator(API Level 35), which supports 16 KB page size(a new Android 15 feature described here), my app keeps crashing with a segmentation fault error.
After investigating the issue, I discovered that the culprit was
implementation 'net.zetetic:android-database-sqlcipher:4.5.3'

inside  the android/build.gradle file.
Checking the android-database-sqlcipher repository, I discovered that it has been deprecated and its long-term relacement is here. I also discovered that version 4.6.1(as described in this issue already supports Android 15 devices with 16 KB page size.
Could you please change the following line inside the android/build.gradle file from
implementation 'net.zetetic:android-database-sqlcipher:4.5.3'

to
implementation "net.zetetic:sqlcipher-android:4.6.1@aar"

Thank you in advance!

Would you be willing to create a PR?

Hey, @robingenz, sure, I'll work on it and link it.
Thanks

Hi!
I submitted a PR to do this upgrade: https://github.com/capacitor-community/sqlite/pull/607


Weird Rendering Order

Bevy version
0.13.1
General information
AdapterInfo { name: "NVIDIA GeForce GTX 1070 Ti", vendor: 4318, device: 7042, device_type: DiscreteGpu, driver: "NVIDIA", driver_info: "536.23", backend: Vulkan }
What I try to achieve
I have made a chunk that has cubes that use "global lattice voxels"
The problem
The ordering is wrong or some weird bug that I can't understand probably how the normals are implied. sometimes the texture Image is transparent and some time is not.
Here I changed the normals to be wrong to see the difference
https://github.com/bevyengine/bevy/assets/69791771/784bf730-81df-44ef-b93c-7f02375f50bc
when done "currently" (all normals looking up) (it should be seen from both sides )
https://github.com/bevyengine/bevy/assets/69791771/1da71e16-fb6c-44d4-885b-cc4553cd4213
Additional information
Some normals are not current for viewing easily when I create StandardMaterial I use the double-sided to be true and cull_mode to None which enables rendering both ways
let material = StandardMaterial{
      base_color_texture : Some(image),
      double_sided: true,
      cull_mode: None,
      alpha_mode: AlphaMode::Blend,
      ..default()
  };

Excuse me, is this issue scheduled to be fixed? @alice-i-cecile


Unallocated runes to first non OP_RETURN

Magic Eden is using the pointer way of to send Runes. Perhaps we can add that to tryDecodeRunestone ?

Here is an example transaction: https://mempool.space/tx/626c21452e512476da878a23958bf05ac7374efd9bec4a90a4f267f2f6d598ee
Where based on Magic Eden, there is a transfer of 4200 RSIC.

tryDecodeRunestone is decoding what is actually found in the encoded runestone, so it makes sense for this method to not return anything.

@jeasonstudio This is a great way to bootstrap ord's Rust SOT implementation into Javascript! However, the indexer in this repo actually uses different reorg logic, so its not a full copy-paste reimplementation.


Put formatter setting in language override, otherwise it can be overridden by a language-scoped user setting.

Also add git.branchProtection

Also removed the pwa- prefixes in launch.json to fix warnings, there will be no behavior change

Codecov Report

Merging #11098 (daff77f) into main (70dc27d) will increase coverage by 0%.
The diff coverage is n/a.

:exclamation: Current head daff77f differs from pull request most recent head da196ed. Consider uploading reports for the commit da196ed to get more accurate results

@@          Coverage Diff           @@
##            main   #11098   +/-   ##
======================================
  Coverage     63%      63%
======================================
  Files        482      482
  Lines      33865    33865
  Branches    5526     5526
======================================
+ Hits       21411    21417    +6
+ Misses     10403    10395    -8
- Partials    2051     2053    +2

Impacted Files
Coverage Δ

src/notebooks/outputs/tracebackFormatter.ts
93% <0%> (-7%)
:arrow_down:

src/platform/common/cancellation.ts
62% <0%> (-6%)
:arrow_down:

src/kernels/jupyter/remoteKernelFinder.ts
88% <0%> (-4%)
:arrow_down:

src/kernels/kernelFinder.base.ts
82% <0%> (-3%)
:arrow_down:

src/kernels/installer/productInstaller.node.ts
78% <0%> (-2%)
:arrow_down:

src/kernels/kernelProvider.base.ts
95% <0%> (-1%)
:arrow_down:

src/platform/msrCrypto/msrCrypto.js
16% <0%> (+<1%)
:arrow_up:

src/kernels/common/baseJupyterSession.ts
80% <0%> (+<1%)
:arrow_up:

src/standalone/api/kernelApi.ts
73% <0%> (+1%)
:arrow_up:

src/kernels/kernelDependencyService.node.ts
85% <0%> (+1%)
:arrow_up:

... and 3 more


Tomm/wrap up

Sign in route
Updated comments

Codecov Report

Merging #60 (81311cb) into dev (d66411c) will decrease coverage by 2.30%.
The diff coverage is 40.00%.

@@            Coverage Diff             @@
##              dev      #60      +/-   ##
==========================================
- Coverage   53.55%   51.24%   -2.31%
==========================================
  Files           8        9       +1
  Lines         183      201      +18
  Branches       23       24       +1
==========================================
+ Hits           98      103       +5
- Misses         78       90      +12
- Partials        7        8       +1

Impacted Files
Coverage Δ

src/middleware/bearer.js
15.38% <ø> (ø)

src/models/user.js
34.37% <0.00%> (ø)

src/routes/user.js
23.33% <33.33%> (+1.51%)
:arrow_up:

src/routes/public.js
86.04% <66.66%> (ø)

src/middleware/basic.js
23.07% <0.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 d66411c...81311cb. Read the comment docs.


Update Composer dependencies (2021-04-11-00-06)

Visual regression test passed!
View the visual regression test report


Update aws-java-sdk-kinesis, ... to 1.11.789

Updates

com.amazonaws:aws-java-sdk-kinesis
com.amazonaws:aws-java-sdk-s3
com.amazonaws:aws-java-sdk-sqs

from 1.11.772 to 1.11.789.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.amazonaws" } ]

labels: library-update, semver-patch

Codecov Report

Merging #332 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #332   +/-   ##
=======================================
  Coverage   46.76%   46.76%
=======================================
  Files          24       24
  Lines         278      278
=======================================
  Hits          130      130
  Misses        148      148

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 b3ca628...d3d2698. Read the comment docs.


Readme examples import pysnmplib

readme example:
from pysnmplib.hlapi import *

wrong name:
>>> from pysnmplib.hlapi import *
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ModuleNotFoundError: No module named 'pysnmplib'

right name:
>>> import pysnmp
>>> pysnmp.__file__
'/home/videoteam/snmp/lib/python3.9/site-packages/pysnmp/__init__.py'

:tada: This issue has been resolved in version 5.0.20-beta.1 :tada:
The release is available on:

v5.0.20-beta.1
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 5.0.20 :tada:
The release is available on:

v5.0.20
GitHub release

Your semantic-release bot :package::rocket:


infer dimensions in capacity

This is no longer necessary now that we have a dimension-independent builder.


ENH: Supports rotating file log

CI failed in https://github.com/xorbitsai/inference/actions/runs/6701736452/job/18213287938?pr=590

CI failed in https://github.com/xorbitsai/inference/actions/runs/6701736452/job/18213287938?pr=590

Fix

https://github.com/xorbitsai/inference/actions/runs/6718151781/job/18284482047?pr=590 failed on linux.


Dense Fog - Advisory

https://www.msn.com/en-us/weather/maps/severeweather?lat=39.1&lon=-94.579&ocid=ansmsnweather&bingFeature=Alert&

Not seeing this myself, for repro steps is being in Kansas City required?


LinkedIn Browser Bug

I've noticed that when broadcasting an Eddystone-URL for some linkedIn profiles when using a url shortner like bit.ly or goo.gl, the title, description and favicon are not being populated in some Physical Web browsers like Chrome and PhyWeb. I'm trying to figure out why this is but it appears that this is something that's occuring a little bit differently depending on the mobile OS and the browser. Looked a little further and thought it could be occuring in PWMetadataRequest.m somewhere but then happened upon this stack overflow post (https://stackoverflow.com/questions/32450569/linkedin-isnt-letting-me-google-users-anymore-sentinel-org-block#) talking about the problems with the sentinal org tool they are using.  Has anyone else noticed this or have any ideas about fixing this?

Can you produce a sample URL which you have on a beacon?
Then I can give you a curl command which uses our Physical Web Service (PWS) to resolve the url into metadata.  All the PW clients use a PWS to actually get page metadata so the errors shouldn't be client specific.
If LinkedIn is doing something specific to block google-bot from crawling its pages, this could explain the issue.

Can the source code be loaded to my google app engine? @mmocny

@Jerren34 you can find a sample PWS hosted right in this project.
It is written using python GAE, which you can run yourself locally or publish to your GAE account.
The Physical Web standalone apps use a version of this sample PWS hosted by us on GAE, but the Physical Web feature of Chrome uses a different PWS backend.

I'm trying to upload it on app ego e right now but I'm having trouble. Do
you mind helping me? Can get it to load and don't know what I'm doing wrong
On Thursday, January 14, 2016, Michal Mocny<EMAIL_ADDRESS>wrote:

@Jerren34 https://github.com/Jerren34 you can find a sample PWS
https://github.com/google/physical-web/tree/master/web-service hosted
right in this project.
It is written using python GAE, which you can run yourself locally or
publish to your GAE account.
The Physical Web standalone apps use a version of this sample PWS hosted
by us on GAE, but the Physical Web feature of Chrome uses a different PWS
backend.
—
Reply to this email directly or view it on GitHub
https://github.com/google/physical-web/issues/580#issuecomment-171865479
.

--
BT3 Viral Marketing
Jerren Harrison
CEO, Founder
313 704 3444

I have a Google appspot account I'm using now. I have downloaded app engine
launcher, python 2.7, and app whine SDK but I can't get it up running. Mind
helping me?
On Thursday, January 14, 2016, Jerren Harrison<EMAIL_ADDRESS>wrote:

I'm trying to upload it on app ego e right now but I'm having trouble. Do
you mind helping me? Can get it to load and don't know what I'm doing wrong
On Thursday, January 14, 2016, Michal Mocny<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:

@Jerren34 https://github.com/Jerren34 you can find a sample PWS
https://github.com/google/physical-web/tree/master/web-service hosted
right in this project.
It is written using python GAE, which you can run yourself locally or
publish to your GAE account.
The Physical Web standalone apps use a version of this sample PWS hosted
by us on GAE, but the Physical Web feature of Chrome uses a different PWS
backend.
—
Reply to this email directly or view it on GitHub
https://github.com/google/physical-web/issues/580#issuecomment-171865479
.

--
BT3 Viral Marketing
Jerren Harrison
CEO, Founder
313 704 3444

--
BT3 Viral Marketing
Jerren Harrison
CEO, Founder
313 704 3444

@mmocny sure, this is a shortened linkedin profile page goo.gl/v6QFk9 . As you can see through the Physical Web app, it doesn't render the metadata like other broadcasted, shortened site urls. For iOS PhyWeb is showing the correct url but not pulling any metadata
 . Android doesn't even show the link in the list of Physical Web beacons and Chrome enabled on iOS today screen is doing the same thing where it's not rendering any of the data.

@rochforp Have you seen examples of this with anything other than LinkedIn?

That particular landing page for goo.gl/v6QFk9 does not have the required meta data...
On the landing page, there is no meta data for description.
<meta name="description" content="....
Without that you won't get the main thing, description, displayed.
It does the have the other tag needed.. ...
But it is buried in boocoo other meta data and scripts; the scraper is stuck it seems.
Observations:
PW list on iOS shows shortened URL, yet sometimes shows LANDING URL. Don't know why.
PW list on Android shows LANDING URL normally, but on this one only shortened URL with loading...
Seems stuck.
It seems the LinkedIn site isn't optimized for PW queries, yet.

@tolson2000 How would that differ from a bot coming along? Could we implement the same methods?
If LinkedIn is not optimized for a title/description/favicon PW query, we should probably augment the PW to include older query methods. I would suspect that LinkedIn is not unique.

@kahjav So far it's been isolated to just linkedin but I'm concerned that it's possibly indicative of a problem that might exist on other sites as well.

First, just a quick aside: Chrome for Android will only show results which link to https pages.  It looks like your short url does redirect to https://www.linkedin.com/in/tlytle so this should be fine.  Chrome for iOS still supports non-https but we will be making a switch soon.  The Physical Web app will likely continue to show all results.
Second, some of our clients will show the raw URL if we fail to fetch page metadata.  The intention was that local-intranet-only or local-development-machine-only URLs, which our PWS could not fetch, should still be available.  However, our direction these days is to just filter these results out and we will add some "advanced" views where you will be able to see all results.  This is less developer friendly but more user friendly.  This may explain why iOS Physical Web app shows just the green link, while other clients show nothing.
Finally, the root of the problem appears to be that the PWS is not resolving your url:
$ curl -k -s -H "Content-Type: application/json" -d '{"objects":[{"url":"http://goo.gl/v6QFk9"}]}' http://url-caster.appspot.com/resolve-scan | python -m json.tool
{
    "metadata": []
}

I will attempt to debug and resolve this issue.  Thank you for raising it!

This may not be the only bug, but it appears that LinkedIn returns a different page depending on the requesting user agent.  The page being served to PWS right now may be an empty page with only inline javascript and no semantic page information at all.
$ curl -L http://goo.gl/v6QFk9
<html><head>
<script type="text/javascript">
window.onload = function() {
  // Parse the tracking code from cookies.
  var trk = "sentinel_org_block";
  var cookies = document.cookie.split("; ");
  for (var i = 0; i < cookies.length; ++i) {
    if ((cookies[i].indexOf("trkCode=") == 0) && (cookies[i].length > 8)) {
      trk = cookies[i].substring(8);
    }
  }

  // Get the protocol for the redirect url.
  var protocol = "http:";
  if (window.location.protocol == "https:") {
    protocol = "https:";
  } else {
    // If "sl" cookie is set, redirect to https.
    for (var i = 0; i < cookies.length; ++i) {
      if ((cookies[i].indexOf("sl=") == 0) && (cookies[i].length > 3)) {
        window.location.href = "https:" + window.location.href.substring(window.location.protocol.length);
        return;
      }
    }
  }

  // Get the new domain. For touch.www.linkedin.com or tablet.www.linkedin.com
  // we strip "touch." and "tablet.". For international domains such as
  // fr.linkedin.com, we convert it to www.linkedin.com
  var domain = location.host;
  if (domain.substr(0, 6) == "touch.") {
    domain = domain.substr(6);
  } else if (domain.substr(0, 7) == "tablet.") {
    domain = domain.substr(7);
  } else if (domain.charAt(2) == ".") {
    domain = "www" + domain.substr(2);
  }

  // D8E90337EA is the tracking code proposed by Harsh, representing guest request redirected
  // to login.
  window.location.href = protocol + "//" + domain + "/uas/login?trk=" + trk + "&session_redirect=" +
      encodeURIComponent(protocol + "//" + domain +
      window.location.href.substr(window.location.href.search(window.location.host) +
                                  window.location.host.length));
}
</script>
</head></html>

Our current PWS does not evaluate JavaScript.  We do not run the page through a headless browser.
However, once I change the User-Agent header I get the real data:
$ curl -L -H "Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8" -H "user-agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.48 Safari/537.36" https://www.linkedin.com/in/tlytle
<...Lots of HTML...>

We already set a custom user agent, but I will see about adjusting it slightly.

FYI: Our current User Agent

@mmocny When does/will Chrome check for https? Would non-https URL shorteners still be able to be utilized if the destination is https?

@kahjav The PW is specifically looking for the "description" for a page. Places like LinkedIn, Facebook, don't bother making a "description" for a 'users' info page. In the case of Facebook when they are hit by a bot their server will substitute a generic description for bots for their users. Affectively just saying JoeBlow is on Facebook.  Join now to connect. Kind of useless for a PW concept. Companies like realtors don't always have a "description" field for their employee pages. And for bots will substitute maybe something again like JobBlow is a realtor for ...
If you want a page for your resume you need to make one specifically with the needed tags and meta data fields to work with PW.
Probably what we need to do is ask LinkedIn them to provide a meaningful "description" meta data.
Here's my test page. It's a shortend URL with http which redirects to a https on another server.
Here again, though, on my iPOD is shows the shortened URL and on Android is shows the
landing page URL.
http://io.ivt.com/to9

@kahjav Coincidentally I just got this question!  Yes, at the moment you can use http redirector to link to https destination.  The https requirement is only on the final URL, and it is to protect the user (so compromised network cannot replace the page contents, effectively having Chrome send users to the wrong destination).  Since the redirect loop is done on PWS we are less concerned about compromised networks.

Yeah, I don't know if I agree with having to have the landing page be https:
That isn't always possible. Will you be allowing self-signed certs?

Alright, it looks like we are failing to resolve LinkedIn because they are explicitly blocking crawling: HTTP/1.1 999 Request denied.  I haven't nor intend to pursue ways to circumvent this.

@tolson2000 We don't currently do much certificate verification, but if you send a user to such a page the browser will likely put up a big red flag, so is unlikely to be a good idea outside of local testing.  And for local testing we hope to make it easier to just show all results.
To be clear: the https requirement is not a big change to physical web or the Eddystone-URL BLE frame format.  It is only a policy decision by the developers of Chrome browser for its integration of the Physical Web feature, and meant to safeguard its users.


Loosen upper bounds on distributed-process-X packages

I'm trying to build this project with the latest version of distributed-process (0.7.3) and currently need to increase the upper-bounds of several packages that this package depends on, and the bounds of some packages they depend on.
The dependency bounds I'm interested in changing are:
- distributed-process <0.7 to  <=0.7.3
- ansi-terminal <0.7 to <=<IP_ADDRESS>
- time <1.7 to <=<IP_ADDRESS>
- network-transport ==0.4 to ==0.5.2
- network-transport-tcp <0.6 to <=0.6

The only two of these that seem to affect extra-deps (distributed-process-X packages) directly are time and distributed-process, which obviously also have some dependency constraints that would need reconciling.
Would you be open to me submitting sweeping PRs that made these bounds changes across all the relevant distribute-process-X packages:
- distributed-process-extras-0.3.2
- distributed-process-async-0.2.4
- distributed-process-systest-0.1.1

as well as this one, distributed-process-supervisor?
I'm really interested in using this package, and will for the mean time use allow-newer: true with stack so that I can build this library in a codebase that uses distributed-process-0.7.3, but would love to get these upper bounds fixed upstream and depend on these repos directly, without the use of allow-newer. Thanks!

You should not ask about permission to send PR! PR for dependency loosening  are welcome. And will be merged and new version and(or) revision  will be released.

Hi all.
@tdietert how things are going? Do you need help with this PR ? :)
Similar problem exists with client-server package.

I didn't end up having the time as the abstraction I'm building on top of distributed-process-supervisor ended up taking up all my time (and the project built just fine with allow-newer: true in the stack.yaml file as a temporary fix.
My coworker @Acentelles may submit these PRs next week as I am out of the office for the next two weeks.

resolved with PR #11
@portnov you should be able to build both libs now with distributed-process-0.7.4 :heart:


Generate NetworkCloud/sdk-2022-12-12-preview

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

/azp run prepare-pipelines

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.NetworkCloud


InputSimulationProfile should support pad controller 2nd joystick by default

Overview
Currently, when launching a demo with a pad controller in the editor, we can't control cameras
Expected Behavior
by default for the DefaultMixedRealityInputSimulationProfile LookHorizontal and LookVertical should be mapped in respectively 4th Axis and 5th Axis (Invert) in the Input project settings.
If the MRTK can change Input Settings by adding those 2 mappings, it would be great.
Actual Behavior
LookHorizontal and LookVertical are defined in the DefaultMixedRealityInputSimulationProfile but not in the Input Project Settings.
Workaround (for those that want it to work as expected)

Edit > Project Settings... > Input
Add 2 Axes

LookHorizontal mapped to Joystick Axis, 4th axis
LookVertical mapped to Invert, Joystick Axis, 5th axis

Steps to reproduce
Launch a demo scene, try moving the camera view with a controller right joystick
camera view does not change, needs to use mouse right click + move mouse
(left joystick for moves works fine)
Unity Editor Version
2018.3.11f1
Mixed Reality Toolkit Release Version
v2.0.0-RC1

Hello,
@gilbdev is it possible to get more information on this pad controller? Is it a specific physical device?

Oh, sorry, i thought i had it specified ...
It's a standard official xboxone controller.

The DefaultMixedRealityInputSimulationProfile should be updated to properly utilize InputActions instead of hard coded axis strings

The DefaultMixedRealityInputSimulationProfile should be updated to properly utilize InputActions instead of hard coded axis strings

I've been looking at input actions and it using them for controlling camera and hand simulation in the editor does not seem feasible:

We would need to add a lot of new actions to the input actions profile:

Camera rotation: 2
Camera movement: 2
Toggle hands: 2 (left/right)
Control hands: 2
Rotate hands: 3

The input sim service is an editor-only data provider. The actions profile is a core profile that would have to include the actions nevertheless.
With each action added the risk of breaking changes increases due to the way action IDs are just indices in the profile. This should be improved in any case, but it makes me want to stay away from input actions in the meantime.
Using input actions means the service would have to become or create a InputSystemGlobalListener

I'd rather keep the input sim service as-is until the input actions system can be reworked somewhat.

That's the whole point of the input actions is to facilitate this sort of thing.
If you're having to add a ton of additional actions it might be beneficial to understand the kinds of data you're trying to convey to the system. Do you really need that many? Should some of that logic be better organized to be closer to the data that it needs? Maybe creating a new data type / axis constraint to convey the hand data?

Using input actions means the service would have to become or create a InputSystemGlobalListener

And what's wrong with that? If that's a problem, why aren't you just sending the messages directly to the game object?

The input sim service is an editor-only data provider. The actions profile is a core profile that would have to include the actions nevertheless.

I don't understand the problem here. Might need more clarification.

With each action added the risk of breaking changes increases due to the way action IDs are just indices in the profile. This should be improved in any case, but it makes me want to stay away from input actions in the meantime.

That's unrelated to the task at hand, but I agree, maybe that could be improved upon. index id was chosen for performance reasons.  One thing to note is that the input action profiles are one of the few profiles we didn't intend to be able to be changed at runtime for that specific reason.
It's the controller mapping that should be swappable and really where the magic happens in relation to what you're trying to accomplish.

I've pushed a fix for the original issue of gamepad joystick axes for camera rotation.
I'd like to leave the question of using InputActions for input simulation for another time.


cv2.IMREAD_IGNORE_ORIENTATION not available in cv2 3.1.0

My run is failing at line 360 in io.py because cv2 version 3.1.0 does not appear to have a IMREAD_IGNORE_ORIENTATION attribute.  I am on Ubuntu 14.04 if that helps.

is it possible for you to update to opencv 3.2?
they added that feature on that version.
we could add a patch for 3.1, but that would only work for orientation: 1

I upgraded to 3.2, and it works fine now.  For reference, I am using Python 2.7.12 |Anaconda 4.2.0 (64-bit).  The standard "conda install opencv" is at 3.1.0, but using
$conda install -c menpo opencv3
worked well.


Datepicker format output

Currently you have the ability to format the date value shown Datepicker component using a custom function. However the value returned by the component to the model is always the same date object. It would be nice to have the ability to format the output as well.

Was about to post the same thing!

@defiant I'm sorry, i don't understand. Custom function format a date object to a string and v-model accepts Date object.
So you could use the same function to format v-model, no ?

@jtommy Maybe you could do that but I was saying it would be more convenient if we passed a custom format string (or function) we could use it directly when we submit the form

@defiant No custom format string because we want an easy and light component that helps to manage date but it haven't to cover all features like other specific library.
When you submit form if you do it by ajax call you can format Date object as you want otherwise will be submit input value (that depends on format function prop).
I think i don't understand your request yet.

There are cases when you submit the whole form without using model, or cases when you use Formdata. I was trying to say it would be easier if we could specify the output format as an option

Most of the time you are dealing with stuff that comes from some api, which usually transports data as a JSON object. In JSON, there is no native Date type.
In my case, JSON contains ISO8601 strings like 2015-10-31T00:00:00.000Z.
To make it seamlessly work with the datepicker, it should also consume ISO-strings.

Yes, but at the moment we don't want cover all patterns but it's the developer to do it (you can use moment library) because we want keep Datepicker simple and without dependency.

Yes, but at the moment we don't want cover all patterns but it's the developer to do it (you can use moment library) because we want keep Datepicker simple and without dependencies.
I see.

Formatting the date for display: I agree, you can set up a global config in your main.js like this:
Vue.use(Buefy, {
  // ... global Buefy config stuff ...
  defaultDateFormatter: filters.dateFormat,
  defaultDateParser: date => {
    const m = moment(date)
    return m.isValid() ? m.toDate() : null
  }
})

OK.
But if we want to support common use cases like parsing an ISO8601 string, then only these adjustments need to be done in src/components/datepicker/Datepicker.vue:
        // ...
        props: {
            value: [Date, String],
            // ...
        },
        watch: {
            dateSelected (value) {
                const currentDate = !value ? new Date() : value
                // Here:
                this.$emit('input', value.toISOString())
                // ...
            },
            value (value) {
                // And here:
                this.dateSelected = new Date(value)
                // ...
            }
        },

What do you think?

We removed String value support because Date object it's to easy to manage.
About your example, i don't know because the v-model could be Date or String but when date is changed or selected emit a string value. It's quite strange.

@jtommy You are right - this is a bit confusing, but works OK in my case.
Ideally I would need only a good tool that automatically converts all fields in my json-response to Date-Objects.

@alqu A great library is moment.js.
You can format (date to string) and parse (string to date) as you want.

@jtommy Thanks for setting up the jsfiddle. I know, it is easily doable.
Looking closer at my app, there are some cases where I directly use the date object via v-model, and others that uses the plain ISO strings, coming directly from a server response.
I guess I have to ask in the VueJS community about best practices where to apply the data transformation. Probably not in a component.
Thanks!


Improve the website

add search for characters
add highscore list
add guilds
add serverstatus (the dashboard)
add game guide

full support for mobile

create a new theme

[ ] investigate vulcanization

fix an issue where the elevation shadow is increased when hovering contained elements.

https://github.com/codingchili/chili-game-ext/issues/3


Missing Texts

Internationalizations for both 🇩🇪 and 🇬🇧 required!
All internationalization Strings are found in core/i18n/de.txt and core/i18n/en.txt
Currently empty or sparce fields regard:

FAQ/help texts  (...Help...=...)
Replies for accepted/denied protocols (uploadReply[1->9]=...)

If a Field is filled with content please change for both languages.
How to
Each line contains the complete content String. Valid String are written in HTML.
Hence a Linebreak is <br>

Replies for accepted/denied protocols (uploadReply[1->9]=...) is enhanced in 264d73552c4857f11d61cc62e2e9455e43a09d6f and 45b84948a910c2d54b20ddd5e081ae5c5e39f964.

No one has complained about any misleading or not verbose enough texts. Closing this now. If anyone wants to make improvements in the core/i18n/de.txt and core/i18n/en.txt localization files, please do so.


Adds js to update the favicon

@kewisch Could you take a look at this please?

@petesfrench Just checking, is this meant to be a stopgap until you reroute the images via nginx? While visually this will work for people viewing the page, I'm not sure it will work with search engine results.

Closing as the nginx PR will be merged asap


Added Personal Portfolio Website Folder in Basics of Web Dev under SWOC3 contribution(#869)

Have you read the Contributing Guidelines ?
(Write your answer here.)
Description
(Write your answer here.)
Fixes #869

Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[ ] I've edited the README.md and link to my code.

Related Issues or Pull Requests

I have deleted that AI file

I have deleted that AI file

It is still there .

Kindly, check it now!
If still it does, then let me know

I have added the readme file

Kindly see now


Update base image tag in Prow jobs

This PR updates the base image tag in all the prowjobs with the tag of the most recently built builder-base image.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: vivek-koppuru
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [vivek-koppuru]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: vivek-koppuru
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [vivek-koppuru]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@vivek-koppuru: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

prowjobs-lint-presubmit
9f9615c03738dedff72b9091bafbefc335a40cb4
link
/test prowjobs-lint-presubmit

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vivek-koppuru: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

prowjobs-lint-presubmit
9f9615c03738dedff72b9091bafbefc335a40cb4
link
/test prowjobs-lint-presubmit

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vivek-koppuru: Updated the job-config configmap in namespace default at cluster default using the following files:

key amazon-eks-pod-identity-webhook-postsubmits.yaml using file jobs/aws/eks-distro-build-tooling/amazon-eks-pod-identity-webhook-postsubmits.yaml
key amazon-eks-pod-identity-webhook-presubmits.yaml using file jobs/aws/eks-distro-build-tooling/amazon-eks-pod-identity-webhook-presubmits.yaml
key athens-postsubmits.yaml using file jobs/aws/eks-distro-build-tooling/athens-postsubmits.yaml
key athens-presubmits.yaml using file jobs/aws/eks-distro-build-tooling/athens-presubmits.yaml
key eks-distro-base-periodics.yaml using file jobs/aws/eks-distro-build-tooling/eks-distro-base-periodics.yaml
key eks-distro-base-postsubmits.yaml using file jobs/aws/eks-distro-build-tooling/eks-distro-base-postsubmits.yaml
key eks-distro-base-presubmits.yaml using file jobs/aws/eks-distro-build-tooling/eks-distro-base-presubmits.yaml
key github-exporter-postsubmits.yaml using file jobs/aws/eks-distro-build-tooling/github-exporter-postsubmits.yaml
key github-exporter-presubmits.yaml using file jobs/aws/eks-distro-build-tooling/github-exporter-presubmits.yaml
key helm-chart-postsubmits.yaml using file jobs/aws/eks-distro-build-tooling/helm-chart-postsubmits.yaml
key helm-chart-presubmits.yaml using file jobs/aws/eks-distro-build-tooling/helm-chart-presubmits.yaml
key prometheus-alertmanager-postsubmits.yaml using file jobs/aws/eks-distro-build-tooling/prometheus-alertmanager-postsubmits.yaml
key prometheus-alertmanager-presubmits.yaml using file jobs/aws/eks-distro-build-tooling/prometheus-alertmanager-presubmits.yaml
key prometheus-helm-chart-postsubmits.yaml using file jobs/aws/eks-distro-build-tooling/prometheus-helm-chart-postsubmits.yaml
key prometheus-helm-chart-presubmits.yaml using file jobs/aws/eks-distro-build-tooling/prometheus-helm-chart-presubmits.yaml
key prometheus-postsubmit.yaml using file jobs/aws/eks-distro-build-tooling/prometheus-postsubmit.yaml
key prometheus-presubmits.yaml using file jobs/aws/eks-distro-build-tooling/prometheus-presubmits.yaml
key release-tooling-presubmits.yaml using file jobs/aws/eks-distro-build-tooling/release-tooling-presubmits.yaml
key prowjobs-lint-presubmits.yaml using file jobs/aws/eks-distro-prow-jobs/prowjobs-lint-presubmits.yaml
key aws-iam-authenticator-postsubmits.yaml using file jobs/aws/eks-distro/aws-iam-authenticator-postsubmits.yaml
key aws-iam-authenticator-presubmits.yaml using file jobs/aws/eks-distro/aws-iam-authenticator-presubmits.yaml
key cni-postsubmits.yaml using file jobs/aws/eks-distro/cni-postsubmits.yaml
key cni-presubmits.yaml using file jobs/aws/eks-distro/cni-presubmits.yaml
key coredns-postsubmits.yaml using file jobs/aws/eks-distro/coredns-postsubmits.yaml
key coredns-presubmits.yaml using file jobs/aws/eks-distro/coredns-presubmits.yaml
key docs-postsubmit.yaml using file jobs/aws/eks-distro/docs-postsubmit.yaml
key docs-presubmit.yaml using file jobs/aws/eks-distro/docs-presubmit.yaml
key etcd-postsubmits.yaml using file jobs/aws/eks-distro/etcd-postsubmits.yaml
key etcd-presubmits.yaml using file jobs/aws/eks-distro/etcd-presubmits.yaml
key external-attacher-postsubmits.yaml using file jobs/aws/eks-distro/external-attacher-postsubmits.yaml
key external-attacher-presubmits.yaml using file jobs/aws/eks-distro/external-attacher-presubmits.yaml
key external-provisioner-postsubmits.yaml using file jobs/aws/eks-distro/external-provisioner-postsubmits.yaml
key external-provisioner-presubmits.yaml using file jobs/aws/eks-distro/external-provisioner-presubmits.yaml
key external-resizer-postsubmits.yaml using file jobs/aws/eks-distro/external-resizer-postsubmits.yaml
key external-resizer-presubmits.yaml using file jobs/aws/eks-distro/external-resizer-presubmits.yaml
key external-snapshotter-postsubmits.yaml using file jobs/aws/eks-distro/external-snapshotter-postsubmits.yaml
key external-snapshotter-presubmits.yaml using file jobs/aws/eks-distro/external-snapshotter-presubmits.yaml
key kubernetes-1-18-postsubmits.yaml using file jobs/aws/eks-distro/kubernetes-1-18-postsubmits.yaml
key kubernetes-1-18-presubmits.yaml using file jobs/aws/eks-distro/kubernetes-1-18-presubmits.yaml
key kubernetes-release-postsubmits.yaml using file jobs/aws/eks-distro/kubernetes-release-postsubmits.yaml
key kubernetes-release-presubmits.yaml using file jobs/aws/eks-distro/kubernetes-release-presubmits.yaml
key livenessprobe-postsubmits.yaml using file jobs/aws/eks-distro/livenessprobe-postsubmits.yaml
key livenessprobe-presubmits.yaml using file jobs/aws/eks-distro/livenessprobe-presubmits.yaml
key main-presubmits.yaml using file jobs/aws/eks-distro/main-presubmits.yaml
key metrics-server-postsubmits.yaml using file jobs/aws/eks-distro/metrics-server-postsubmits.yaml
key metrics-server-presubmits.yaml using file jobs/aws/eks-distro/metrics-server-presubmits.yaml
key node-driver-registrar-postsubmits.yaml using file jobs/aws/eks-distro/node-driver-registrar-postsubmits.yaml
key node-driver-registrar-presubmits.yaml using file jobs/aws/eks-distro/node-driver-registrar-presubmits.yaml

In response to this:

This PR updates the base image tag in all the prowjobs with the tag of the most recently built builder-base image.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@vivek-koppuru: Updated the job-config configmap in namespace default at cluster default using the following files:

key amazon-eks-pod-identity-webhook-postsubmits.yaml using file jobs/aws/eks-distro-build-tooling/amazon-eks-pod-identity-webhook-postsubmits.yaml
key amazon-eks-pod-identity-webhook-presubmits.yaml using file jobs/aws/eks-distro-build-tooling/amazon-eks-pod-identity-webhook-presubmits.yaml
key athens-postsubmits.yaml using file jobs/aws/eks-distro-build-tooling/athens-postsubmits.yaml
key athens-presubmits.yaml using file jobs/aws/eks-distro-build-tooling/athens-presubmits.yaml
key eks-distro-base-periodics.yaml using file jobs/aws/eks-distro-build-tooling/eks-distro-base-periodics.yaml
key eks-distro-base-postsubmits.yaml using file jobs/aws/eks-distro-build-tooling/eks-distro-base-postsubmits.yaml
key eks-distro-base-presubmits.yaml using file jobs/aws/eks-distro-build-tooling/eks-distro-base-presubmits.yaml
key github-exporter-postsubmits.yaml using file jobs/aws/eks-distro-build-tooling/github-exporter-postsubmits.yaml
key github-exporter-presubmits.yaml using file jobs/aws/eks-distro-build-tooling/github-exporter-presubmits.yaml
key helm-chart-postsubmits.yaml using file jobs/aws/eks-distro-build-tooling/helm-chart-postsubmits.yaml
key helm-chart-presubmits.yaml using file jobs/aws/eks-distro-build-tooling/helm-chart-presubmits.yaml
key prometheus-alertmanager-postsubmits.yaml using file jobs/aws/eks-distro-build-tooling/prometheus-alertmanager-postsubmits.yaml
key prometheus-alertmanager-presubmits.yaml using file jobs/aws/eks-distro-build-tooling/prometheus-alertmanager-presubmits.yaml
key prometheus-helm-chart-postsubmits.yaml using file jobs/aws/eks-distro-build-tooling/prometheus-helm-chart-postsubmits.yaml
key prometheus-helm-chart-presubmits.yaml using file jobs/aws/eks-distro-build-tooling/prometheus-helm-chart-presubmits.yaml
key prometheus-postsubmit.yaml using file jobs/aws/eks-distro-build-tooling/prometheus-postsubmit.yaml
key prometheus-presubmits.yaml using file jobs/aws/eks-distro-build-tooling/prometheus-presubmits.yaml
key release-tooling-presubmits.yaml using file jobs/aws/eks-distro-build-tooling/release-tooling-presubmits.yaml
key prowjobs-lint-presubmits.yaml using file jobs/aws/eks-distro-prow-jobs/prowjobs-lint-presubmits.yaml
key aws-iam-authenticator-postsubmits.yaml using file jobs/aws/eks-distro/aws-iam-authenticator-postsubmits.yaml
key aws-iam-authenticator-presubmits.yaml using file jobs/aws/eks-distro/aws-iam-authenticator-presubmits.yaml
key cni-postsubmits.yaml using file jobs/aws/eks-distro/cni-postsubmits.yaml
key cni-presubmits.yaml using file jobs/aws/eks-distro/cni-presubmits.yaml
key coredns-postsubmits.yaml using file jobs/aws/eks-distro/coredns-postsubmits.yaml
key coredns-presubmits.yaml using file jobs/aws/eks-distro/coredns-presubmits.yaml
key docs-postsubmit.yaml using file jobs/aws/eks-distro/docs-postsubmit.yaml
key docs-presubmit.yaml using file jobs/aws/eks-distro/docs-presubmit.yaml
key etcd-postsubmits.yaml using file jobs/aws/eks-distro/etcd-postsubmits.yaml
key etcd-presubmits.yaml using file jobs/aws/eks-distro/etcd-presubmits.yaml
key external-attacher-postsubmits.yaml using file jobs/aws/eks-distro/external-attacher-postsubmits.yaml
key external-attacher-presubmits.yaml using file jobs/aws/eks-distro/external-attacher-presubmits.yaml
key external-provisioner-postsubmits.yaml using file jobs/aws/eks-distro/external-provisioner-postsubmits.yaml
key external-provisioner-presubmits.yaml using file jobs/aws/eks-distro/external-provisioner-presubmits.yaml
key external-resizer-postsubmits.yaml using file jobs/aws/eks-distro/external-resizer-postsubmits.yaml
key external-resizer-presubmits.yaml using file jobs/aws/eks-distro/external-resizer-presubmits.yaml
key external-snapshotter-postsubmits.yaml using file jobs/aws/eks-distro/external-snapshotter-postsubmits.yaml
key external-snapshotter-presubmits.yaml using file jobs/aws/eks-distro/external-snapshotter-presubmits.yaml
key kubernetes-1-18-postsubmits.yaml using file jobs/aws/eks-distro/kubernetes-1-18-postsubmits.yaml
key kubernetes-1-18-presubmits.yaml using file jobs/aws/eks-distro/kubernetes-1-18-presubmits.yaml
key kubernetes-release-postsubmits.yaml using file jobs/aws/eks-distro/kubernetes-release-postsubmits.yaml
key kubernetes-release-presubmits.yaml using file jobs/aws/eks-distro/kubernetes-release-presubmits.yaml
key livenessprobe-postsubmits.yaml using file jobs/aws/eks-distro/livenessprobe-postsubmits.yaml
key livenessprobe-presubmits.yaml using file jobs/aws/eks-distro/livenessprobe-presubmits.yaml
key main-presubmits.yaml using file jobs/aws/eks-distro/main-presubmits.yaml
key metrics-server-postsubmits.yaml using file jobs/aws/eks-distro/metrics-server-postsubmits.yaml
key metrics-server-presubmits.yaml using file jobs/aws/eks-distro/metrics-server-presubmits.yaml
key node-driver-registrar-postsubmits.yaml using file jobs/aws/eks-distro/node-driver-registrar-postsubmits.yaml
key node-driver-registrar-presubmits.yaml using file jobs/aws/eks-distro/node-driver-registrar-presubmits.yaml

In response to this:

This PR updates the base image tag in all the prowjobs with the tag of the most recently built builder-base image.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Supplied content type is not allowed. Content-Type: application/json is required ?

When I call http://localhost:1633/stamps/100/17, it returns "Supplied content type is not allowed. Content-Type: application/json is required" ", so I called "postman" and returned "{
"jsonrpc": "2.0",
"error": {
"code": -32700,
"message": "Parse error"
},
"id": null
}"
I don't know what is going on

@twodogegg can you disclose the bee version you're running? BTW, In 1.0 the stamps API was moved into the debug API, see: https://github.com/ethersphere/bee/blob/master/openapi/SwarmDebug.yaml#L780

I believe this is related to Bee itself, while bee-js is JS client library, so I am moving it to Bee repo.


[1.16] Block breaker crash client and server

My server is crashed after i place the block breaker from your mod and now my server don´t start anymore.I testit it in a singleplayer world  and the same thing happen there too.
Forge version:  36.0.13
Industrial Foregoing version: industrial-foregoing-1.16.5-<IP_ADDRESS>-2b762d7.jar
Titanium version: titanium-1.16.5-<IP_ADDRESS>.jar
Pastebin: https://pastebin.com/BNJje2kt

Report it to Effortless Building, they are sending a packet to a fake player.


Editable list view fixes (order of choices & relations bug)

Fixes #1019 by putting inline editable choices in a list instead of a dict.
Fixes a bug caused by #1009 that added an extra blank field to inline editable fields (only on relations) when allow_blank was enabled.
Fixed issue with unicode strings in options breaking x-editable.

@pawl Beautiful... Really nice to have the fields display in the right order.
Big thanks!
Hope you have a relaxing weekend, you deserved it.


Rationalize the use of initial slashes in endpoints

In some places in our Javalin code we have endpoints with initial slashes (e.g., /about), and in other places we don't (e.g., api/users). We should figure out if this matters (I don't think it does) and pick one and use it consistently.

All the examples in the Javalin handler documentations have leading slashes, so we should follow suit.


can_put_xmp doesn't say why

I have been trying for the better part of a day to try and add a XMP file to a PDF/A file but every time I try xmpfile.can_put_xmp(xmp) it returns false. I have no idea why it won't allow me to write it. Is there a way to determine why it is failing easily? I attached the files I am using (had to rename the xmp file as github wouldn't allow me to upload it).
The code I am running:
#!/usr/bin/env python3

from libxmp import XMPFiles

xmpfile = XMPFiles( file_path="output1.pdf", open_forupdate=True )
xmpdata = XMPFiles( file_path="004004.modified.xmp" )
xmp = xmpdata.get_xmp()

if xmpfile.can_put_xmp(xmp):
  xmpfile.put_xmp(xmp)
  xmpfile.close_file()
else:
  print("can't put new xmp metadata!")

[output1.pdf](https://github.com/python-xmp-toolkit/python-xmp-toolkit/files/114456/output1.pdf)
[004004.modified.xmp.txt](https://github.com/python-xmp-toolkit/python-xmp-toolkit/files/114460/004004.modified.xmp.txt)

Hey John, sorry for the late answer, which is that you can't use the exempi
library to inject XMP into a PDF that does not already have an XMP packet.
Some background on the issue here, https://forums.adobe.com/thread/708717 .
On Tue, Feb 2, 2016 at 1:37 PM, John Scancella<EMAIL_ADDRESS>wrote:

I have been trying for the better part of a day to try and add a XMP file
to a PDF/A file but every time I try xmpfile.can_put_xmp(xmp) it returns
false. I have no idea why it won't allow me to write it. Is there a way to
determine why it is failing easily? I attached the files I am using (had to
rename the xmp file as github wouldn't allow me to upload it).
The code I am running:
#!/usr/bin/env python3
from libxmp import XMPFiles
xmpfile = XMPFiles( file_path="output1.pdf", open_forupdate=True )
xmpdata = XMPFiles( file_path="004004.modified.xmp" )
xmp = xmpdata.get_xmp()
if xmpfile.can_put_xmp(xmp):
xmpfile.put_xmp(xmp)
xmpfile.close_file()
else:
print("can't put new xmp metadata!")
output1.pdf
004004.modified.xmp.txt
—
Reply to this email directly or view it on GitHub
https://github.com/python-xmp-toolkit/python-xmp-toolkit/issues/47.

--
John Evans

@quintusdias but I am not trying to inject XMP into a PDF that does not already have an XMP packet. I am trying to MERGE a XMP file into a PDF that already has XMP.

So after debugging the exempi library, it appears that in the case of PDF, not only does an XMP packet have to exist, but the packet that you want to merge back in has to be smaller than the pre-existing packet?  Line 1199 of exempi-2.2.2/source/XMPCore/XMPMeta-Serialize.cpp is where that check occurs and where your case fails (which is in the Adobe SDK being wrapped by exempi).  By manually increasing the padding at the bottom of the XMP packet in the PDF file, it can be made to work, but that's obviously not a great solution.
It's unfortunate, but about the only thing I can think to do is to somehow get a better diagnostic.

@quintusdias Ok that makes sense. If I wanted to do the "not great solution" of manually increasing the padding at the bottom, how would I go about doing that?

The way I did it was to put blank space between the final </x:xmpmeta>  and  .  The XMP specification refers to this as the "padding" and recommends that it be 2-4 KB, seemingly for this very purpose.   If you end up having to go to lengths like that, you might as well bypass the python xml toolkit entirely and manually excise the old XMP and stitch in the new.

Yeah that is what I was afraid of. Ok, then can I change this issue so that the underlaying exempi code error messages come back instead of just a boolean for can put?
For example, the exempi code you referenced above, could xmp-toolkit supply an optional error message Can't fit into specified packet size ?

Also I submitted a bug report to exempi for this underlying issue
https://bugs.freedesktop.org/show_bug.cgi?id=94065

Given Adobe answer is https://forums.adobe.com/message/3096497#3096497
"This is because the toolkit does not have a smart file handler for PDF files but just uses dump packet scanning when interacting with XMP in that file format.
The PDF library should be able to inject XMP into PDF files."
It is unlikely to get fixed quick. Another case where they didn't want to disrupt their business (selling the PDF library).
see https://forums.adobe.com/message/3099970#3099970
"the request for a smart PDF handler exists for a long time already but so far demand was unfortunately never high enough that it would make it to the top of the priority list."
What I would recommend for your case would be to special case PDF and use a PDF writing library to write the XMP packet to PDF.

(I'm the maintainer of Exempi, BTW)

But it seems that Exempi is missing some APIs for a better control on the packet serialization and size that the SDK has. I could roll a 2.3 release with these. (you'd need to update the python bindings too).

Hey Hubert, pleased to make acquaintance with you.
A 2.3 release would be great, but I agree that making a special case for PDF might work best for now.

@quintusdias looks like 2.3 was released with the fix https://bugs.freedesktop.org/show_bug.cgi?id=94065


feat(bedrock): introduce amazon titan models as another option for Bedrock

This pull request (PR) aims to introduce "Amazon Titan Foundation Models" as another option for the Bedrock feature. The Bedrock option in this library is currently limited to "Anthropic Claude Family of Large Language Models."
This change aims to make the API request function more flexible, allowing for the integration of additional Bedrock options that may have different API requests.
Here's a comparison of how the API request is for both Bedrock options based on their respective AWS documentation:

Amazon Titan text models

request body
{
    "inputText": string,
    "textGenerationConfig": {
        "temperature": float,
        "topP": float,
        "maxTokenCount": int,
        "stopSequences": [string]
    }
}

response body
{
    'inputTextTokenCount': int,
    'results': [{
        'tokenCount': int,
        'outputText': '\n<response>\n',
        'completionReason': string
    }]
}

Anthropic Claude models

request body
{
    "prompt": "\n\nHuman:<prompt>\n\nAssistant:",
    "temperature": float,
    "top_p": float,
    "top_k": int,
    "max_tokens_to_sample": int,
    "stop_sequences": ["\n\nHuman:"]
}

response body

In sum, below is a table comparing the API requests for both Bedrock options:
see table summary...

Bedrock option
API request
API response

Amazon Titan Foundation Models

Anthropic Claude Family of Large Language Models

To test the API requests for both Bedrock options, you can use the following commands:

for "Amazon Titan Foundation Models", use the following command:

 (AWS_ACCESS_KEY_ID="xxxxx" AWS_SECRET_ACCESS_KEY="xxxxx" \
    node ./dist/src/main.js eval \
    --config examples/amazon-bedrock/promptfooconfig.titan-text.yaml --no-cache)

for "Anthropic Claude Family of Large Language Models", use the following command:

 (AWS_ACCESS_KEY_ID="xxxxx" AWS_SECRET_ACCESS_KEY="xxxxx" \
     node ./dist/src/main.js eval \
     --config examples/amazon-bedrock/promptfooconfig.claude.yaml --no-cache)

With this change, we're making it possible to utilize different Bedrock options with varying API requests, giving users more flexibility and choice.
Let me know if you have any questions or feedback.

Thanks @igorlima for this excellent change!


Add create master on latest revision api

@slohia-adobe can you please review it?

@slohia-adobe Could you please review this


Move grades-rest from gb1 to gradebookng

@ern where should this relocated REST endpoint live?

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 30

Complexity increasing per file
==============================
- gradebookng/grades-rest/src/main/java/org/sakaiproject/gradebook/entity/Student.java  1
- gradebookng/grades-rest/src/main/java/org/sakaiproject/gradebook/entity/Category.java  1
- gradebookng/grades-rest/src/main/java/org/sakaiproject/gradebook/entity/GradesEntityProvider.java  24
- gradebookng/grades-rest/src/main/java/org/sakaiproject/gradebook/entity/User.java  10
- gradebookng/grades-rest/src/main/java/org/sakaiproject/gradebook/logic/ExternalLogic.java  60
- gradebookng/grades-rest/src/main/java/org/sakaiproject/gradebook/entity/GradebookItemScore.java  15
- gradebookng/grades-rest/src/main/java/org/sakaiproject/gradebook/entity/SparseGradebookItem.java  4
- gradebookng/grades-rest/src/main/java/org/sakaiproject/gradebook/entity/Course.java  7
- gradebookng/grades-rest/src/main/java/org/sakaiproject/gradebook/entity/GradebookItem.java  10
- gradebookng/grades-rest/src/main/java/org/sakaiproject/gradebook/entity/Gradebook.java  7

See the complete overview on Codacy

Few things these classes could be lombok's reducing their size dramatically and it provides safer implementations of equals and hashcodes.
Instead of creating a duplicate gradebook endpoint probably should add these to the existing one to reduce confusion.


feat(CategoryTheory): sheaf categories are cartesian closed

... under some assumptions on the target category.
We apply this to conclude that condensed sets and light condensed sets are cartesian closed.
Co-authored-by: Sina Hazratpour @sinhp
Co-authored-by: Jon Eugster @joneugster
This is adapted from work done at the Copenhagen masterclass on formalisation of condensed mathematics in 2023.

Thanks!
bors merge


fix: Add initial support for long comments in headers of WordPress theme style.css files.

This change allows for longer comments in themes header:
• URLs longer than 80 characters
• Descriptions longer than 80 characters
• Tags longer than 80 characters
Fixes #150.

Note: This requires the upcoming stylelint v8 and tests will fail against 7.x branches


Missing a function for TLS and a minor fix

Hi,
I wanted to migrate from peerjs-server to peerjs-go/server, and I found some minor problems with the server.

The first difficulty that I encountered was the missing TLS option and for that reason, I created StartTLS method.
The second issue was with the websocket path, where the Go's peerjs client and the older JS client were trying to call GET wss://<website>/<path>/peerjs, but the Go's server was creating a handler for wss://<website>/<path>/<key>. However, I don't know whether the second issue is a bug or a feature on how the peerjs protocol will work now on.

I fixed them for my side project, and I hope you like my improvements.

Great addition, thanks 🙏