Added Ticket Auction

Ticket Auction problem in CPP language

Have you read the Contributing Guidelines on Pull Requests?
Yes, I have gone through the Guidelines.
Description
Concert Tickets Auction
There are n concert tickets available, each with a certain price. Then, m customers arrive, one after another.
Each customer announces the maximum price he or she is willing to pay for a ticket, and after this, they will get a ticket with the nearest possible price such that it does not exceed the maximum price.
Checklist

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

Related Issues or Pull Requests
closes #2418

@HarshCasper
resolved the changes suggested 💯

@HarshCasper I've no idea why the DeepSource: Java (beta) is failing...
" DeepSource can’t analyze this repository yet, unfortunately. Please check back later! "        :/


test-serve(main): not-preserve-symlinks test on Windows fails

Describe the bug
it seems there is something broken on Windows running test-serve script on main branch (Windows 10 PRO machine: I enable dev mode):

Reproduction
just clone main on a Window 10 machine and run the test-serve script
System Info
npx envinfo --system --npmPackages '{vite,@vitejs/*}' --binaries --browsers

  System:
    OS: Windows 10 10.0.19044
    CPU: (16) x64 Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz
    Memory: 41.21 GB / 63.95 GB
  Binaries:
    Node: 16.13.0 - C:\Program Files\nodejs\node.EXE
    npm: 8.1.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 102.0.5005.62
    Edge: Spartan (44.19041.1266.0), Chromium (101.0.1210.53)
    Internet Explorer: 11.0.19041.1566

Used Package Manager
pnpm
Logs
F:\work\projects\quini\GitHub\vite-esm-ssr-build>pnpm run test-serve

> vite-monorepo@ test-serve F:\work\projects\quini\GitHub\vite-esm-ssr-build
> vitest run -c vitest.config.e2e.ts

 RUN  v0.12.9 F:/work/projects/quini/GitHub/vite-esm-ssr-build

···-···-···-···--··--··············-····································································-········-···----······················-··························································-------··
····-···················---------····························--··x··································--------·································-····--····--···············································-·········
·······--······--······················--···················--············--·--··---

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Tests 1 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

 FAIL  playground/preserve-symlinks/__tests__/preserve-symlinks.spec.ts > not-preserve-symlinks
AssertionError: expected '' to be 'hello vite' // Object.is equality
 ❯ playground/preserve-symlinks/__tests__/preserve-symlinks.spec.ts:10:42
      8|
      9| test('not-preserve-symlinks', async () => {
     10|   expect(await page.textContent('#root')).toBe('hello vite')
       |                                          ^
     11| })
     12|

  - Expected   "hello vite"
  + Received   ""

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯

Test Files  1 failed | 52 passed | 11 skipped (64)
     Tests  1 failed | 442 passed | 63 skipped (506)
      Time  20.58s (in thread 158.60s, 12.98%)

 ELIFECYCLE  Command failed with exit code 1.

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Tested also skiping that test, it is ok, only fails not-preserve-symlinks.

It didn't reproduce. Maybe this one? https://github.com/vitejs/vite/blob/main/CONTRIBUTING.md#:~:text=Also you may want to set git core.symlinks to true to solve issues with symlinks in git.

Ok, I need to add that entry...

@sapphi-red
using git clone -c core.symlinks=true https://github.com/vitejs/vite.git the test now is ok, but then I get this another one:
F:\work\projects\quini\GitHub\vite-esm-ssr-symlinks\vite>git config core.symlinks
true

the error now is on playground/worker/__tests__/es/es-worker.spec.ts:

 FAIL  playground/worker/__tests__/es/es-worker.spec.ts > build > inlined code generation
Error: ENOENT: no such file or directory, scandir 'F:\work\projects\quini\GitHub\vite-esm-ssr-symlinks\vite\playground-temp\worker\dist\es\assets'
 ❯ Object.readdirSync ../../../../../../../node:fs:1390:3
 ❯ playground/worker/__tests__/es/es-worker.spec.ts:68:21
     66|   test('inlined code generation', async () => {
     67|     const assetsDir = path.resolve(testDir, 'dist/es/assets')
     68|     const files = fs.readdirSync(assetsDir)
       |                     ^
     69|     expect(files.length).toBe(27)
     70|     const index = files.find((f) => f.includes('main-module'))

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: {
  "code": "ENOENT",
  "errno": -4058,
  "path": "F:\\work\\projects\\quini\\GitHub\\vite-esm-ssr-symlinks\\vite\\playground-temp\\worker\\dist\\es\\assets",
  "syscall": "scandir",
}
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯

Test Files  1 failed | 57 passed | 3 skipped (64)
     Tests  1 failed | 425 passed | 47 skipped (487)
      Time  22.65s (in thread 203.07s, 11.15%)

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Errors ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

Vitest caught 1 unhandled error during the test run. This might cause false positive tests.
Please, resolve all the errors to make sure your tests are not affected.

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Error ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Error: Errors occurred while running tests. For more information, see serialized error.
 ❯ Object.runTests ../../../../../../../file:/F:/work/projects/quini/GitHub/vite-esm-ssr-symlinks/vite/node_modules/.pnpm/vitest@0.12.9/node_modules/vitest/dist/chunk-vite-node-externalize.42b0363f.js:8250:15
 ❯ processTicksAndRejections ../../../../../../../node:internal/process/task_queues:96:5
 ❯ async ../../../../../../../file:/F:/work/projects/quini/GitHub/vite-esm-ssr-symlinks/vite/node_modules/.pnpm/vitest@0.12.9/node_modules/vitest/dist/chunk-vite-node-externalize.42b0363f.js:10439:9
 ❯ async Vitest.runFiles ../../../../../../../file:/F:/work/projects/quini/GitHub/vite-esm-ssr-symlinks/vite/node_modules/.pnpm/vitest@0.12.9/node_modules/vitest/dist/chunk-vite-node-externalize.42b0363f.js:1044
9:12
 ❯ async Vitest.start ../../../../../../../file:/F:/work/projects/quini/GitHub/vite-esm-ssr-symlinks/vite/node_modules/.pnpm/vitest@0.12.9/node_modules/vitest/dist/chunk-vite-node-externalize.42b0363f.js:10376:5
 ❯ async startVitest ../../../../../../../file:/F:/work/projects/quini/GitHub/vite-esm-ssr-symlinks/vite/node_modules/.pnpm/vitest@0.12.9/node_modules/vitest/dist/chunk-vite-node-externalize.42b0363f.js:11112:5
 ❯ async start ../../../../../../../file:/F:/work/projects/quini/GitHub/vite-esm-ssr-symlinks/vite/node_modules/.pnpm/vitest@0.12.9/node_modules/vitest/dist/cli.js:665:9
 ❯ async CAC.run ../../../../../../../file:/F:/work/projects/quini/GitHub/vite-esm-ssr-symlinks/vite/node_modules/.pnpm/vitest@0.12.9/node_modules/vitest/dist/cli.js:661:3

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: {
  "errors": [
    [Error: ENOENT: no such file or directory, open 'F:\work\projects\quini\GitHub\vite-esm-ssr-symlinks\vite\playground-temp\css\dist\assets\index.40015985.js'],
    [Error: ENOENT: no such file or directory, open 'F:\work\projects\quini\GitHub\vite-esm-ssr-symlinks\vite\playground-temp\worker\dist\iife\index.html'],
    [Error: ENOENT: no such file or directory, open 'F:\work\projects\quini\GitHub\vite-esm-ssr-symlinks\vite\playground-temp\worker\dist\iife-sourcemap\index.html'],
  ],
}
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
 ELIFECYCLE  Command failed with exit code 1.
ERROR: "test-build" exited with 1.
 ELIFECYCLE  Test failed. See above for more details.

@userquin That fail is flaky. Would you try running the test several times? or apply https://github.com/vitejs/vite/pull/8049/commits/0b054fcb7f12f175ca29005dbed0e852cad240f4 which will reduce flaky fails.

@sapphi-red
closing, 0b054fc fix it, now test passing...
FYI: on my laptop (Windows 10 PRO) I need to change process.exit() on scripts/patchCJS.ts with process.exit(0), it seems plugin-legacy cannot be built: https://github.com/vitejs/vite/pull/8348#issuecomment-1140270143


deploy fails with python2.7 with updated pip and upgraded awsebcli

Description
Suddenly deploy fails due to inability to import JSONDecodeError in ebcli/core/fileoperations.py", line 32. Previously the deployment script worked fine, but right now there are probably some unexpected updates in dependencies.
Steps to reproduce
Start a docker image node:14 (as per documentation). In this instance run few updates as following:
For python version 2.7:
apt-get update -y
curl https://bootstrap.pypa.io/pip/2.7/get-pip.py -o get-pip.py
python get-pip.py
pip --version
pip install --upgrade pip setuptools
pip install awsebcli -q --upgrade
eb deploy production

For python version 3.5:
apt-get update -y
apt-get install -y python3-dev python3-pip
update-alternatives --install /usr/bin/python python /usr/bin/python2.7 1
update-alternatives --install /usr/bin/python python /usr/bin/python3.5 2
update-alternatives --list python
python --version
pip3 --version
pip3 install awsebcli -q --upgrade
eb deploy production

Observed result

Please provide command output with --debug flag set.

NOTE: the --debug flag does not produce any difference.
For python version 2.7:
$ eb deploy production
Traceback (most recent call last):
  File "/usr/local/bin/eb", line 5, in <module>
    from ebcli.core.ebcore import main
  File "/usr/local/lib/python2.7/dist-packages/ebcli/core/ebcore.py", line 19, in <module>
    from ebcli.core import ebglobals, base, hooks
  File "/usr/local/lib/python2.7/dist-packages/ebcli/core/hooks.py", line 20, in <module>
    from ebcli.core import fileoperations
  File "/usr/local/lib/python2.7/dist-packages/ebcli/core/fileoperations.py", line 32, in <module>
    from json import load, JSONDecodeError
ImportError: cannot import name JSONDecodeError

For python3:
$ pip3 install awsebcli -q --upgrade
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-0rv71d9c/awsebcli/

Expected result
Normal deploy as before
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
.elasticbeanstalk config contains:
default_platform: Docker 18.06.1-ce

Until this is fixed one solutions is to use previous version:
pip install awsebcli==3.19.4 --upgrade
Also haven't tried myself, but devs from another project had the same problem with python 3.7, they solved the issue by using different python image:
image: nikolaik/python-nodejs:latest

@blackisnotcool  do you know if there's an open PR for the awsebcli patch already which I can follow?

@o1dnik Doesn't look like there is.

Indeed version 3.20.0 did not work for me. I tried with version 3.19.4 yet there was another issue. For some reason downgrading the version did not help.
But what I can recommend is to use the official awsebcli setup script (documentation link and the official repository here).

After investigating about this, the bug was first introduced in https://github.com/aws/aws-elastic-beanstalk-cli/commit/6275d6970364be3c15f0fe3f72d06f4242277fe6, indeed included in release 3.20.0. That commit is the first one to add from json import JSONDecodeError, which is only valid since Python 3.5.
To maintain compatibility with Python versions < 3.5, considering JSONDecodeError is a subclass of ValueError, these usages should be converted to:
try:
    from json import JSONDecodeError
except ImportError:
    JSONDecodeError = ValueError

@o1dnik thanks for reporting this issue. As you can see from the error message, this error happens because JSONDecodeError can not be imported. The fact is that JSONDecodeError is not supported in python 2.7(see this https://cpython-test-docs.readthedocs.io/en/latest/library/json.html#exceptions) and we no longer supports Python 2.7
Therefore I suggest that you use python 3.5 if you use new version (3.20.0) of our cli, or if you still want to use python 2.7 then use old version of cli. I recommend use virtual environment to manage different Python versions and different package versions.


ModelBinder Issue on Mono

Hi,
I have a ViewModel with ObjectId property, It's a specific Struct from the MongoDB driver.
public class EntityViewModel
{
      public ObjectId Id { get; set; }
}

I send the ViewModel to the server in json and receive it in the controller with the FromBody attribute.
public IActionResult AddEntity([FromBody] EntityViewModel model) { ... }

This work perfectly on Windows.
But on Linux (I use the beta3 docker image) the server return this error.

An unhandled exception occurred while processing the request.

InvalidProgramException: Invalid IL code in (wrapper delegate-invoke) <Module>:invoke_callvirt_DateTime_ObjectId& (MongoDB.Bson.ObjectId&): IL_004d: castclass 0x00000007

Microsoft.AspNet.Mvc.PropertyHelper.CallPropertyGetterByReference[ObjectId,DateTime] (Microsoft.AspNet.Mvc.ByRefFunc2 getter, System.Object target) [0x00000] in \<filename unknown> Microsoft.AspNet.Mvc.PropertyHelper.GetValue (System.Object instance) [0x00000] in \<filename unknown> Microsoft.AspNet.Mvc.ModelBinding.AssociatedMetadataProvider1+<>c__DisplayClass9_0[Microsoft.AspNet.Mvc.ModelBinding.CachedDataAnnotationsModelMetadata].b__0 () [0x00000] in <filename unknown>
Microsoft.AspNet.Mvc.ModelBinding.ModelMetadata.get_Model () [0x00000] in <filename unknown>

I found this issue closed recently on mono, is this related ?

@sornaks Please confirm this issue has been fixed in Mono and then close as appropriate.

Yes this was fixed in Mono (https://github.com/mono/mono/commit/c73363cee456b32c726ef7a0c4d504f1d07eaad2). You will have to build mono from source to get this change. (Mono issue - https://bugzilla.xamarin.com/show_bug.cgi?id=25717)


Add missing example entry (pbr_textures)

examples/3d/pbr_textures.rs was missing in both Cargo.toml and in the examples
README.md.

noticed it as well, wanted to add it)

The pbr_textures and load_gltf examples were merged because the only difference was the rotating light. It looks like cart just forgot to remove the pbr_textures file. See commit https://github.com/bevyengine/bevy/pull/1632/commits/00b03a7f09fa43cbb12102a60033dab14482762d .

@pkupper oh ok didn't know about that!
I did an overwrite of this branch to instead remove the leftover pbr_textures.rs.

bors r+


Different time every day

Hello,
Can someone please guide me as to how I can use notifee to generate local notifications every day but for a different time. I'm trying to implement a prayer alert feature. The prayer times are different every day.
My current implementation is:
Create trigger notification for a single day:
prayer 1 => 5am
prayer 2 => 10am
prayer 3 => 5pm
prayer 4 => 10pm
next day
prayer 1 => 5:10am
prayer 2 => 10:05am
prayer 3 => 5:20pm
prayer 4 => 10:11pm
As per the docs, I cannot pass a date to the parameters, is there any workaround available that I can use?
Any guidance here is highly appreciated, much thanks.

Hi, thanks for the question. You can pass a timestamp to createTriggerNotification which can be calculated by the standard Javascript Date API or using something like moment.js. For example, if you need an alert tomorrow at 10:11pm:
await notifee.createTriggerNotification(notification, {
    const date = new Date(Date.now());
    date.setDay(date.getDate() + 1);
    date.setHours(22);
    date.setMinutes(11);

    // OR
    const date = new Date('2021-11-04T22:11:00')

    // Create a time-based trigger
    const trigger: TimestampTrigger = {
      type: TriggerType.TIMESTAMP,
      timestamp: date.getTime(), // fire at 10:11pm
    };

    // Create a trigger notification
    await notifee.createTriggerNotification(
     notification,
      trigger,
    );
  }

})

We have a similar example in our docs https://notifee.app/react-native/docs/triggers#creating-a-trigger-notification. Hope this helps.

Thank you for your reply.
How can I schedule a notification for 2021-11-10 for 5pm?
I see that the timestamp parameter takes in only date.getTime() but no date
// Create a time-based trigger
const trigger: TimestampTrigger = {
  type: TriggerType.TIMESTAMP,
  **timestamp: date.getTime(), // fire at 10:11pm**
};

No problem, happy to help! The getTime() method converts the date object into a numeric value that represents both the date and time.
If you see the code snippet in the example posted above, I've shown two different ways on how to create the timestamp:

in multiple lines

const date = new Date(Date.now());
date.setDay(date.getDate() + 1);
date.setHours(22);
date.setMinutes(11);

in one line:
const date = new Date('2021-11-04T22:11:00')

Then you convert the date into a timestamp as you mentioned date.getTime() which as it states in the official docs:
 Returns the numeric value of the specified date as the number of milliseconds since January 1, 1970, 00:00:00 UTC. (Negative values are returned for prior times.)


Creating an Data processor

You need to create a Java application that will:

receive metadata about saved artifacts through a message broker.
save metadata to a NoSQL database.
send information about successful/failed saving back to the message broker.

Done


Add postgres based SearchEngine

This PR adds a postgres based search engine. This search engine might be the default for most instances as it doesn't require and additional service (like elastic search), scales well, provides good results and is pretty easy to setup. If you are already using postgres, no configuration is required.
We already running this in production and gained some experience with it. Therefore the schema already evolved a bit to avoid to high write loads. We started with rewriting the whole table every time content is indexed, but now it's smarter and only writes updated documents to the index.
I decided to name it search-backend-module-pg even though it would also be possible to write implementations for MySQL and SqLite. However the schema will be completely different for these databases. Maybe someone is interested in contributing them in the future. For now one can fallback to the Lunr implementation when using SqLite locally.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

@Fox32 awesome work!

@iamEAP I moved the docs to the microsite and wired the page up in the navigation

Not super familiar with the knex/postgres world but rest of it looks 🔥
Thanks for this contribution @Fox32 🚀

Not super familiar with the knex/postgres world but rest of it looks 🔥

I guess @freben is an expert here. Would be open for some feedback, not need to rush merging it.


In the search bar, if we enter a barcode with spaces, no product will be found

Hi everyone,
Here is an issue that users may encounter if they input a barcode with spaces: no product will be found.
The fix is, as usual, really simple: remove all spaces if there are only digits on the app.
But shouldn't this fix also be applied to the API?

So, should we fix this on mobile for now or create an issue on the dart package?  @g123k

So, should we fix this on mobile for now or create an issue on the dart package? @g123k

We can have fixes on multiple sides:

On the Dart package, ensure to remove all spaces (don't forget about weird spaces, not only " " )
On the app, edit isAValidBarcode method
On the server, a fix for the API

Fixed in the app by #5019.


Integrate Firebase

Since we're moving to Firebase, we need to import Firebase's dependency.

[x] Add Firebase dependency and configuration
[ ] Find a way to integrate this with redux actions

@jpmarques66 https://www.robinwieruch.de/react-firebase-redux-tutorial might shed light on this.


Code in ModelForm

Hello,
Is it possible to have editable code form?
Use case: building a SQL query form that would be prepopulated from a URL, similar to this.

Hi @liquidcarbon,
Seems like a great feature request. Marking as such. PRs welcome!

Ended up building with gradio, sorry 🙃 https://huggingface.co/spaces/liquidcarbon/duckdb-fastapi-gradio


Move Socket Outside

Describe the bug
I think we should move all socket.io code outside of index.js in the backend because there is a bunch of socket.io events happening in index.js.
To Reproduce
Expected result
We can create an object of the socket in the socket.js file which we store in Utils folder So I think it's easy to understand index.js code and also code will be refactored in proper structure
Actual result
Screenshots
Are you willing to contribute to this issue? Yes
Desktop (please complete the following information):

OS: Windows 10
Browser Chrome
Version 89.0.4389.114

Smartphone (please complete the following information):
Additional context

Your point seems realistic. @nishant23122000 this will help us in extending the socket in the future @kothariji

@Vishv07  Yes

Hi @nishant23122000 , First of all, thank you so much for taking out the time to work on this issue.
Definitely 🙌, Please go forward to work on this issue.


Added New Pull Request project structure and style guide to CONTRIBUTING.md

🛠 Fixes Issue
Closes #96

👨💻 Changes proposed

Added explanation of the project structure to CONTRIBUTING.md
Created a style_guide.md which contains style guide information from the figma board.

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers

📷 Screenshots

@t-bello7 please let me know if there is anything else i'm missing.

@Osilaja78 This is looking cool. Its well written and structured.
##Things to add

That tailwind is the accepted CSS framework used.
A reference to the  tailwind.config.cjs file which handles most of the style guides. So developers don't have to create their own style configuration.
Emphasis on developers checking molecules and atoms if a components has already been built before building from scratch.
There is a template folder in the src folder to handle things like layouts; the dashboard is later going to be refactored to have a dashboard layout.

Done @t-bello7 . Everything has been added.


Listbox Item Groups

I've noticed the listbox does not have a groupstyle member. Is there any way to group a list in Avalonia?

the DataGrid allows this https://github.com/AvaloniaUI/DataGrid
https://github.com/AvaloniaUI/Avalonia/pull/2109

DataGrid is an overkill for my purpose but I'll check it out, thanks for pointing


Laggy linting

Type: Bug
Shows me error while I have already changed the piece of code. Very slow with the performance. Found that this extension is problematic by using vscode extension bisect.
Extension version: 2024.13.2024082201
VS Code version: Code 1.92.2 (fee1edb8d6d72a0ddff41e5f71a671c23ed924b9, 2024-08-14T17:29:30.058Z)
OS version: Linux x64 6.8.0-060800-generic
Modes:

System Info

Item
Value

CPUs
AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx (8 x 2774)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_offwebnn: disabled_off

Load (avg)
6, 5, 4

Memory (System)
15.43GB (9.16GB free)

Process Argv
. --crash-reporter-id 2de9ee3f-1b65-45f4-8b80-cc7f3fda0086

Screen Reader
no

VM
0%

DESKTOP_SESSION
cinnamon

XDG_CURRENT_DESKTOP
X-Cinnamon

XDG_SESSION_DESKTOP
cinnamon

XDG_SESSION_TYPE
x11

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonnoceb:30805159
asynctok:30898717
pythonregdiag2:30936856
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
accentitlementst:30995554
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
g316j359:31013175
pythoncenvpt:31062603
a69g1124:31058053
dvdeprecation:31068756
dwnewjupytercf:31046870
2f103344:31071589
impr_priority:31102340
refactort:31108082
pythonrstrctxt:31112756
flightc:31119335
wkspc-onlycs-t:31111718
wkspc-ranged-c:31123312
fje88620:31121564

@Tuhin-thinks Can you elaborate on what you mean by error. Is it syntax errors or linting errors for a specific linter? Please provide a screen shot of the error. Python extension itself does not do linting of python code, linting occurs from various tools. So having the screenshot of the error will be helpful.

I can take a screen recording of few seconds for better clarity.

I think I have the same or similar issue. Don't want to raise a new ticket if its a duplicate.
My python project I am using
I am using

VS Code version 1.93.0
Python version v2024.14.0
pylint version v2023.10.1
mypy type checker version v2024.0.0
Pylance version v2024.9.1

I have autosave on in my VSCode, not sure if it is a contributing factor or not.
But I what I observe is: I am typing my code, the linter and mypy randomly report partially written bits of code are correctly wrong (I don't mind this I have auto save on). But I can type fast. I finish writing the code, then spot more errors and fix them.
And I see very slow (every few seconds) the linter updates what it shows, to select different bits of wrong code. I can sit with my completed code and wait minutes while for it to animate its review on my code until it finally finishes. This is terrible.
It is like each change queues up a new check (without replacing the last one) and so has to slowly work its way through them all.
My work around to this is to regularly restart pylint and mypy servers using the command on F1. It would good if the linter was faster. But mostly it should always do the most recent request per file and drop the rest of the requests. I only care about the state now.
Snippet from Pylint output (I think this might show it):
2024-09-12 12:52:32.938 [info] [Trace - 12:52:32 PM] Received notification 'textDocument/publishDiagnostics'.
2024-09-12 12:52:32.940 [info] [Trace - 12:52:32 PM] Received response 'textDocument/codeAction - (234)' in 43783ms.
2024-09-12 12:52:32.941 [info] [Trace - 12:52:32 PM] Received response 'textDocument/codeAction - (235)' in 38260ms.
2024-09-12 12:52:32.942 [info] [Trace - 12:52:32 PM] Received response 'textDocument/codeAction - (236)' in 36310ms.
2024-09-12 12:52:32.943 [info] [Trace - 12:52:32 PM] Received response 'textDocument/codeAction - (237)' in 34503ms.
2024-09-12 12:52:32.944 [info] [Trace - 12:52:32 PM] Received response 'textDocument/codeAction - (238)' in 33343ms.
2024-09-12 12:52:32.944 [info] [Trace - 12:52:32 PM] Received response 'textDocument/codeAction - (239)' in 32398ms.
2024-09-12 12:52:32.946 [info] [Trace - 12:52:32 PM] Received response 'textDocument/codeAction - (240)' in 31872ms.
2024-09-12 12:52:32.947 [info] [Trace - 12:52:32 PM] Received response 'textDocument/codeAction - (241)' in 27643ms.
2024-09-12 12:52:32.948 [info] [Trace - 12:52:32 PM] Received response 'textDocument/codeAction - (242)' in 26585ms.
2024-09-12 12:52:32.949 [info] [Trace - 12:52:32 PM] Received response 'textDocument/codeAction - (243)' in 25559ms.
2024-09-12 12:52:32.950 [info] [Trace - 12:52:32 PM] Received response 'textDocument/codeAction - (244)' in 25160ms.
2024-09-12 12:52:32.951 [info] [Trace - 12:52:32 PM] Received response 'textDocument/codeAction - (245)' in 16936ms.
2024-09-12 12:52:32.952 [info] [Trace - 12:52:32 PM] Received response 'textDocument/codeAction - (246)' in 11936ms.
2024-09-12 12:52:32.953 [info] [Trace - 12:52:32 PM] Received response 'textDocument/codeAction - (247)' in 10653ms.
2024-09-12 12:52:32.954 [info] [Trace - 12:52:32 PM] Received response 'textDocument/codeAction - (248)' in 10302ms.
2024-09-12 12:52:32.955 [info] [Trace - 12:52:32 PM] Received response 'textDocument/codeAction - (249)' in 6460ms.
2024-09-12 12:52:32.955 [info] [Trace - 12:52:32 PM] Received response 'textDocument/codeAction - (250)' in 4108ms.
2024-09-12 12:52:32.956 [info] [Trace - 12:52:32 PM] Received response 'textDocument/codeAction - (251)' in 1586ms.
2024-09-12 12:52:33.209 [info] [Trace - 12:52:33 PM] Sending request 'textDocument/codeAction - (252)'.
2024-09-12 12:52:33.210 [info] [Trace - 12:52:33 PM] Received response 'textDocument/codeAction - (252)' in 1ms.
2024-09-12 12:55:49.921 [info] [Trace - 12:55:49 PM] Sending request 'textDocument/codeAction - (253)'.
2024-09-12 12:55:49.923 [info] [Trace - 12:55:49 PM] Received response 'textDocument/codeAction - (253)' in 2ms.

Thanks
Kris

@KrisTC There are some limitations to how this works with autosave, the code for this is here :
https://github.com/microsoft/vscode-pylint/blob/96409b97d1f7aac1dbdb1b8ec9886288a15a0519/bundled/tool/lsp_server.py#L100-L131
I am open to take any PRs on this. The limitations exist due to how quickly we can perform linting with pylint, may be a good debounce mechanism would work.
An alternative option, that works much better and faster is ruff, with the Ruff extension. Ruff works in a different way, and designed to handle continuous linting.


Target_VNET_RG is missing in parameters

Script which was used for Recovery Vault based migration had an option to specify Resource Group name for VNET so it can be in a different RG compared to where VM are migrated to. New version of the script is missing this parameter which forces migrated VMs to be collocated with VNET in the same RG

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

ID: 1fd4faae-ca8a-99cb-8799-a7a54590c291
Version Independent ID: e9dde0d4-b0d0-78c5-8818-5ebc840bf58b
Content: Automate agentless VMware migrations in Azure Migrate - Azure Migrate
Content Source: articles/migrate/how-to-automate-migration.md
Service: azure-migrate
GitHub Login: @rahulg1190
Microsoft Alias: rahugup

@artisticcheese Thanks for the feedback! We are taking a look into this and will get back to you soon.

@artisticcheese Thanks for the feedback! We are taking a look into this and will get back to you soon.

Duplicate of #https://github.com/MicrosoftDocs/azure-docs/issues/68937#issuecomment-760630331

Duplicate of #https://github.com/MicrosoftDocs/azure-docs/issues/68937#issuecomment-760630331

I verified that current code will fail if there are more then 1 VNET with same name. Not only that but code get all VNETs in all regions with that name so it may even fail if VNET is in wrong region with only 1 VNET in place.
 $Target_VNet = Get-AzVirtualNetwork -Name $targetVnetName
        if (-not $Target_VNet) {
            $processor.Logger.LogError("VNET could not be retrieved for: '$($targetVnetName)'")
            $reportItem.AdditionalInformation = "VNET could not be retrieved for: '$($targetVnetName)'"
            return
        }
        else {
            $params.Add("TargetNetworkId", $Target_VNet.Id)
        }

I verified that current code will fail if there are more then 1 VNET with same name. Not only that but code get all VNETs in all regions with that name so it may even fail if VNET is in wrong region with only 1 VNET in place.
 $Target_VNet = Get-AzVirtualNetwork -Name $targetVnetName
        if (-not $Target_VNet) {
            $processor.Logger.LogError("VNET could not be retrieved for: '$($targetVnetName)'")
            $reportItem.AdditionalInformation = "VNET could not be retrieved for: '$($targetVnetName)'"
            return
        }
        else {
            $params.Add("TargetNetworkId", $Target_VNet.Id)
        }

Will track this as an enhancement item. Thank you for checking and pointing this out @artisticcheese.

Will track this as an enhancement item. Thank you for checking and pointing this out @artisticcheese.


AppArmor Engine Policy complain-only & improve ruleset

To prevent breakages for users and to assess the
impact of the engine policy for users (especially those
on less common graph drivers), mark the policy as
complain-only until we are comfortable removing this
tag.
Implements the policies for the remaining binaries
called by the Docker engine and eliminates the
giant whitelisted 'all files' permission in favor
of granular whitelisting and child-specific policies.
Signed-off-by: Eric Windisch<EMAIL_ADDRESS>

This should unbreak Ubuntu/Debian packages. /cc @duglin @jhowardmsft @runcom

/cc @jfrazelle @icecrime - this should eliminate potential breakages people may still be having in 1.8rc1. It seems prudent to put the new AppArmor policy into a complain-only (i.e info) mode while we make sure it works for everyone.

@ewindisch - Hmmm. I just tried compiling this branch (this time using a 1.7.1 daemon), and then re-compiling again, but with the previously built daemon running. Unfortunately I'm seeing the same symptoms as before still (as in won't compile).

NM, rebased off master and re-verified. Can now compile using the latest daemon. LGTM, solved my issues.

As per [this comment on #14985] (https://github.com/docker/docker/issues/14985#issuecomment-125396849) I have leveraged the changes in this apparmor.d entry. Now, however, I am unable to successfully invoke docker stop.

LGTM

I think we should just warn for now then next release we can error out, otherwise its super scary for users of just the static binary

@jfrazelle this PR was making the apparmor engine policy soft, such that there would be no hard errors. To help defuse the confusion, I've combined my PRs into #15099

Thanks @ewindisch. I'm going to close this PR in favor of #15099.


Providing arbitrary options for sources

Hello, I noticed that although the olHelpers provides a simple interface for building sources with the createSource function, the list of parameters we can provide is limited to those supported by the function.
For now if I need to provide some parameters to OpenLayers which are not supported by the directive, I can create a PR and that's fine as it does not happen too often. But I wonder if we could find a way to provide arbitrary options for sources.
Maybe a specific "raw" case could do the trick by providing a object like :
{
    type: 'raw',
    source: new ol.source.XYZ(...)
}

What do you think ?

Sure, can you elaborate bit more on this?

+1
The goal is to use every parameters defined by OL3 without restriction. If we choose to use this type, we know we are at the bleeding edge of the directive :
This kind of code could be in the switch/case which define the oSource in the olHelper :
case 'raw': {
                if (!source.rawSource) {
                    $log.error('[AngularJS - Openlayers] - Raw layer need to have an OL3 source defined at source.rawSource');
                }

                osmSource = source.rawSource;

Do you think there is other side effect by doing that ?

Interesting.

Do you think there is other side effect by doing that ?

No, not really. It's an edge case where the developer might want to go native with ol3 constructs, which I think is fine. In the general case you could still benefit from the simpler object configuration syntax the directive currently offers.
Could you submit a PR for that?

After investigation, it seems ol object are too complexe for the $scope.$watch function.
When angular try to do a comparison between two OpenLayer Source object, the browser reach it's maximum call stack size (from here : https://github.com/tombatossals/angular-openlayers-directive/blob/master/src/directives/layer.js#L61 )
So, as an alternative, and only for native type of OpenLayer (ImageWMS, TileWMS, WMTS, OSM, BingMaps, MapQuest, TileJSON, TileVector, TileTMS, TileImage, KML, XYZ), we should find a way to let the developper give angular-openlayer-directive the parameter of the constructor.
For example :
if (source.rawParameters) {
  return new ol.layer.[source.type](source.rawParameters);
}

switch(source.type):
case ...
...

If you have a better idea, I'll be glad to hear it :smile:


refactor(molecules): SfCallToAction

Related issue
https://github.com/DivanteLtd/storefront-ui/issues/805
Scope of work
refactor of Call to action molecule to adjust to new design and update of font variables,
sf-banner-light was modifier removed
Screenshots of designs

Checklist

[x] No commented blocks of code left
[x] Run tests and docs
[x] Self code-reviewed

If applicable:

[x] I followed composition rules for my component
[x] I tested the component in most common device sizes (can be tested in Storybook from viewport addon in top menu)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


When a trigger is called, and the after/before callback has an exception, the state is still transitioned

I have two states, game_begin and game_end, and i'm missing the implementation of def do_stuff():
>>> x.state
'game_begin'
>>> x.my_trigger()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python3.5/dist-packages/transitions-0.5.1-py3.5.egg/transitions/core.py", line 282, in trigger
  File "/usr/local/lib/python3.5/dist-packages/transitions-0.5.1-py3.5.egg/transitions/core.py", line 831, in _process
  File "/usr/local/lib/python3.5/dist-packages/transitions-0.5.1-py3.5.egg/transitions/core.py", line 312, in _trigger
  File "/usr/local/lib/python3.5/dist-packages/transitions-0.5.1-py3.5.egg/transitions/core.py", line 201, in execute
  File "/usr/local/lib/python3.5/dist-packages/transitions-0.5.1-py3.5.egg/transitions/core.py", line 809, in _callback
AttributeError: 'GameState' object has no attribute 'do_stuff'

>>> x.state
'game_complete'

If an exception occurs before the transition (in prepare, before), it is halted. In case there is a raise after the transition has been conducted (in after, finalize), there is no rollback but the execution of further after callback is halted. If the error occurs in after callbacks, finalize callbacks will be executed though. This is expected behaviour so far.
from transitions import Machine

m = Machine(states=['A', 'B', 'C'], initial='A', before_state_change='do_stuff')

print(m.state)  # >>> A
try:
    m.to_B()
except AttributeError:
    pass
print(m.state)  # >>> A

m = Machine(states=['A', 'B', 'C'], initial='A', after_state_change='do_stuff')

try:
    m.to_B()
except AttributeError:
    pass
print(m.state)  # >>> B

Hi @dgtlmoon,
do you still have issues with the way the library handles exceptions during state transitions? Feel free to leave some feedback/suggestions.

closing this due to inactivity. Feel free to reopen the issue if it still persist.

Hi there, I was just looking for information on which cases does a 'rollback' occur on state transition when any of the callback raises an exception. Would it be possible to add this information to the main documentation?
Thank you!

Would it be possible to add this information to the main documentation?

sure thing! I added the passage right after the execution order.

cool, thank you!


stop_times - CALL_AND_RETRY_2 Allocation failed

Processing downloads/gtfs/stop_times.txt
FATAL ERROR: CALL_AND_RETRY_2 Allocation failed - process out of memory
Abandon (core dumped)

(database = postgres & stop_times.txt = 1.3 GB)

What GTFS are you testing with?

<EMAIL_ADDRESS>(network.txt = agency.txt)
Do you want my model ? Or perhaps a zip of my fork with data.zip (by your yahoo mail)  ?

Well, that's got to be the largest GTFS I've ever seen.  ;)
I think I know why the error is happening and have an idea of how to fix it.
As for all the other files in your feed, I'm trying to maintain compatibility with only the GTFS spec.  You're always able to create a fork of this library and customize for your custom GTFS.

OK thank you :)
I avoided the problem by upgrading node 0.10.* to 0.12.7 (very soon 4.0^^) with the flag --max-old-space-size=30720 (I have 32GB)
If it can help you, the code consumes around 29GB on my stop_times.txt and database postgis is near 4GB.
Perhaps the callbacks ?
http://stackoverflow.com/questions/29880741/request-makes-process-out-of-memory-when-downloading-big-media-files

I'm pretty sure it's from the bulk inserter function getting all rows queued up while it synchronously inserts 1000 rows at a time.

I ended up creating a whole new helper library to solve this one:  https://github.com/djstroky/db-streamer
Regarding that particular feed, there were some other problem:

agency.txt is missing
there were duplicate records of service_id and date in calendar_dates.txt.  It doesn't make sense to have both include and exclude in there.  So I tried to fix that file and maybe caused the final problem.
There was a missing service_id reference in the trips.txt table.

Because of all that I didn't get to test loading in the stop_times.txt table, but nonetheless, this fix should solve the original issue.


Webapp seem broken ?

Using the example of scikit-hep/hist
https://scientific-python.github.io/repo-review/?repo=scikit-hep%2Fhist&branch=main
I get
Traceback (most recent call last):
  File "/lib/python311.zip/_pyodide/_base.py", line 468, in eval_code
    .run(globals, locals)
     ^^^^^^^^^^^^^^^^^^^^
  File "/lib/python311.zip/_pyodide/_base.py", line 310, in run
    coroutine = eval(self.code, globals, locals)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "", line 5, in
  File "", line 7, in __init__
  File "/lib/python3.11/site-packages/repo_review/ghpath.py", line 59, in __post_init__
    val: io.StringIO = self.open_url(url)
                       ^^^^^^^^^^^^^^^^^^
  File "/lib/python3.11/site-packages/repo_review/ghpath.py", line 53, in open_url
    with urllib.request.urlopen(url) as response:
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/lib/python311.zip/urllib/request.py", line 216, in urlopen
    return opener.open(url, data, timeout)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/lib/python311.zip/urllib/request.py", line 519, in open
    response = self._open(req, data)
               ^^^^^^^^^^^^^^^^^^^^^
  File "/lib/python311.zip/urllib/request.py", line 541, in _open
    return self._call_chain(self.handle_open, 'unknown',
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/lib/python311.zip/urllib/request.py", line 496, in _call_chain
    result = func(*args)
             ^^^^^^^^^^^
  File "/lib/python311.zip/urllib/request.py", line 1419, in unknown_open
    raise URLError('unknown url type: %s' % type)
urllib.error.URLError:

Edit: works from the CLI, so unsure.

Same is happening here: https://scientific-python.github.io/repo-review/?repo=scikit-hep%2Fhist&branch=main - not sure what changed, but it's not picking up the injection of open_url. The next version modifies this a bit, but that's not out yet, so no idea why it's broken yet.

Actually, I understand why the local demo is broken - it expects the unreleased version of repo-review. Ahh, your link is the unreleased version too! That's why. I thought you were pointing at the dev guide. Probably should just make a release, then.

0.11 is out which fixes this.

Ah, sorry ! thanks for the quick fix !


Main PR for 2022-2023

integration pr for 2022-2023

LGTM. Left 1 minor comment (not even sure if that's your code or if it's library code lol). Didn't look in too much detail but trusting feedback from feature/autonomy PR was addressed properly.

fixed! will merge then.

LGTM. Left 1 minor comment (not even sure if that's your code or if it's library code lol). Didn't look in too much detail but trusting feedback from feature/autonomy PR was addressed properly.

for clarity, these were the ones not addressed in this PR (non-blocking):
higher priority fixes
https://github.com/PurdueLunabotics/purdue_lunabotics/pull/43#discussion_r1451099217
nits + docs updates
https://github.com/PurdueLunabotics/purdue_lunabotics/pull/43#discussion_r1421110396
https://github.com/PurdueLunabotics/purdue_lunabotics/pull/43#discussion_r1264551454
https://github.com/PurdueLunabotics/purdue_lunabotics/pull/43#discussion_r1264551573
https://github.com/PurdueLunabotics/purdue_lunabotics/pull/43#discussion_r1451519852
https://github.com/PurdueLunabotics/purdue_lunabotics/pull/43#discussion_r1264553342

blocked by https://github.com/PurdueLunabotics/purdue_lunabotics/pull/55. once that's tested in sim and real, can merge this.


Implement PLATFORM_RELATIONSHIPS, fixes #9

#9

This implements PLATFORM_RELATIONSHIPS with local DDEV-based values.

mariadb/mysql/postgres
elasticsearch
redis
memcached

This can be tested with
ddev get https://github.com/rfay/ddev-platformsh/tarball/20221024_platform_relationships

TODO:

[x] The scripts to generate relationships should go into a gitignored directory.

Works OOTB on<EMAIL_ADDRESS>

This is great!
However, I wonder why you removed the platform.yaml provider.

DDEV automatically provides platform.yaml (and has for several months). It's the version that was originally developed for the add-on. And ddev start overwrites it anyway with DDEV's own version.


Support query the global transaction in unexpect status

Why you need it?
Is your feature request related to a problem? Please describe in details
After modify the TC as springboot project, We are supposed to add some openapi.
the current issue is to require someone to support query the global transaction in unexpect status
If you want to support it, please comment "Please assign it to me" is this issue.
完成SpringBoot改造之后，需要提供一些对外的接口，查询查询非正常状态的全局事务信息。
如果你有兴趣支持这个问题的话, 请在下方留言 Please assign it to me
How it could be?
A clear and concise description of what you want to happen. You can explain more about input of the feature, and output of it.
Other related information
Add any other context or screenshots about the feature request here.

Please assign it to me @caohdgege


Pure Cool Link - becomes unavailable sporadically

Hi,
thanks again for making the integration happen. I have 6 Dyson fans connected to this integration, but there is one machine that acts differently then the rest. 2 of my machines are Pure Cool Link machines, but one of them, often becomes unavailable, and sometimes comes back to report to HA. The other Pure Cool Link is rock solid (like the other fans) and stay online all the time. I've often had to delete the one fan, and re-add it again, only to become unavailable again, at some point. Its 10 ft away from my internet access point, so I don't think its related to WiFi connectivity but who knows.
Any idea why this particular machine mis-behaves and becomes unavailable? I've added this machine both way (Via the Wifi credentials AND the manual credentials). When its unavailable in HA I can still access the machine using the Dyson app.
Here's an example of the temperature history, and you can see how often it becomes unavailable to available (but sometimes it just stays unavailable until I delete and readd).

Having same issue with Pure Hot+Cool the last few days. Has been working perfectly up until now - any ideas on what the cause is are welcome (maybe something changed recently on Dyson's end?). And thanks a ton for this integration - really love it!
tip: restarting home assistant does reconnect the dyson - but that's not something you want to repeat very often

I have the same issue. Dyson Pure Hot+Cool becomes unavailable after a while and I haven't found any way to make it work again unless I delete and reconfigure the integration...

Ditto - Hot & Cool unavailable, has been pretty stable until a week or so again (I think)

I recently changed my router and the connection to my Dyson fans have been almost perfect.
In about a month with my new router there was one fan that became unavailable and I unplugged it and plugged it back in and it became instantly available in HA.
I suspect the connection issues I was experiencing was related to how my old router was handling too many devices on my home wifi, 84 to be exact.

I have the same problem with my Dyson Purifier Cool Formaldehyde (TP09) that the integration suddenly becomes unavailable.
My experience:

I tried to restart Home Assistant which did not work.
Then I logged of from the Dyson Link mobile app.
After restarting again, the Dyson integration worked again.

With the "Unknown Error Occurred" issue (https://github.com/shenxn/ha-dyson/issues/99) we learned that you have to log out from the mobile app in order to register your Dyson Cloud in Home Assistant.
Conclusion: Could it be that Dyson allows only one connection / device at the same time? As soon as you have connected with home assistant and your Dyson Link mobile app at the same time, one connection (probably not Dyson Link) will fail.
Do you agree? Can anyone confirm?


Auto login

If the user has not logged out of the manager and navigates to a different page, reloads the page or browser, the manager will attempt to log in to the address saved in localStorage.
A few other things that had to be done for this to work smoothly:

LogoutManager function created to reset the reducer to initial state, run the start method, then redirect to the homepage
A link to logout was added to the header navigation
Moved the location of localStorage.setItem() to after login is successful. This does not remove the input from the popup window in case the user types in their address wrong.

Closes #65

In an effort to rebase this branch, I made a mistake and it looks like I removed the commits.


1.5.1 changes to Util.formatNum break many features

var line = L.polyline([[0,-7.993322e-10],[10,20],[20,30]]);
L.geoJson(line.toGeoJSON());//errors on NaN
L.Util.formatNum(-7.993322e-10); //Returns NaN

Please publish a patch to revert of this commit.
https://github.com/Leaflet/Leaflet/pull/6670
Environment

Leaflet version: 1.5.1
Browser (with version):
OS/Platform (with version):

Hi @desean1625
I'm going to publish a patch later this week.
Sorry for the delay!

Released in 1.6.0


doc: Wifx gateways update

Summary

Add Wifx L1 (Closes #1043) (very similar to LORIX One as it's the same software)
Add 'wifx' prefix to LORIX One folder
Update LORIX One images and textes for latest software version

Checklist

[x] Scope: The referenced issue is addressed, there are no unrelated changes.
[x] Run Locally: Verified that the docs build using make server, posted screenshots, verified external links. Test with HUGO_PARAMS_SEARCH_ENABLED=true if style changes will affect the search bar.
[x] New Features Marked: Documentation for new features is marked using the new-in-version shortcode, according to the guidelines in CONTRIBUTING.
[x] Style Guidelines: Documentation obeys style guidelines in CONTRIBUTING.
[x] Commits: Commit messages follow guidelines in CONTRIBUTING, there are no fixup commits left.

Hey @mullerch, the PR looks great (which is why I approved) except one thing - we did docs reorganization in the meantime, so you can notice that for example lorix-one folder isn't anymore in /gateways/lorix-one but in gateways/models/lorix-one. Your PR is based on the old version of master branch, so this introduces a lot of conflicts and broken references, which is why the docs build is failing. Can you please do a rebase on the current master branch and fix conflicts? I tried, but I cannot push commits on your upstream.


Add option to try out different index choices

Summary

The framework currently produces IndexScan and IndexOnlyScan hints without specifying an index name. The optimizer may choose some index, but that is necessarily the best one to choose.
Since trying out every possible index on the table will increase the search space and the time it takes to run the whole model, it would be good if we have an option for enabling this mode as well as limiting it based on complexity of the query, e.g.: the number of tables <= 3, etc.
The IndexScan/IndexOnlyScan hints without the index name should also tried out in addition to the index specific ones to let the optimizer consider use of different indexes for computing different min/max values, etc.

Examples
Example 1
(This is included in the taqo-issues model attached to #2.)
For the query: select c2 from t10000w where c2 = 10, the optimizer chose the index t10000w_c2_c1 on t10000w (c2 asc, c1 asc), however, there is a smaller index: t10000w_c2 on t10000w (c2 asc), which would be cheaper for the query that doesn't need c1 at all.
When the option is specified, try: IndexScan(t10000w t10000w_c2_c1), IndexScan(t10000w t10000w_c2), IndexOnlyScan(t10000w t10000w_c2_c1) and IndexOnlyScan(t10000w t10000w_c2)
Instead of (or in addition to): IndexScan(t10000w) and IndexOnlyScan(t10000w) for this query. We may need to limit the number of tables in the query, e.g.: only for a single table query, etc., too.
{
    "tag": "",
    "query": "select c2 from t10000w where c2 = 10",
    "query_hash": "91a59d5ce30012088f45c690503b6707",
    "tables": null,
    "optimizer_tips": null,
    "explain_hints": "IndexScan(t10000w)",
    "execution_plan": {"full_str": "Index Scan using t10000w_c2_c1 on t10000w  (cost=0.00..4.49 rows=4 width=4)\n  Index Cond: (c2 = 10)"},
    "execution_time_ms": 0.56376953125,
    "result_cardinality": 4,
    "result_hash": "6add84506c86a658bc85038f91e35ce7",
    "parameters": [],
    "optimizations": null,
    "execution_plan_heatmap": null
},
{
    "tag": "",
    "query": "select c2 from t10000w where c2 = 10",
    "query_hash": "91a59d5ce30012088f45c690503b6707",
    "tables": null,
    "optimizer_tips": null,
    "explain_hints": "IndexOnlyScan(t10000w)",
    "execution_plan": {"full_str": "Index Only Scan using t10000w_c2_c1 on t10000w  (cost=0.00..4.45 rows=4 width=4)\n  Index Cond: (c2 = 10)"},
    "execution_time_ms": 0.525830078125,
    "result_cardinality": 4,
    "result_hash": "6add84506c86a658bc85038f91e35ce7",
    "parameters": [],
    "optimizations": null,
    "execution_plan_heatmap": null
},

Example 2

https://github.com/yugabyte/yugabyte-db/issues/17720

Example 3

An index-specific hint would disable min/max optimization and causes the optimizer to choose Seq Scan.

yugabyte=# explain select min(c1), min(c2), min(c3) from t100;
                          QUERY PLAN
--------------------------------------------------------------
 Finalize Aggregate  (cost=10.75..10.76 rows=1 width=12)
   ->  Seq Scan on t100  (cost=0.00..10.00 rows=100 width=12)
         Partial Aggregate: true
(3 rows)

yugabyte=# explain /*+ IndexOnlyScan(t100) */select min(c1), min(c2), min(c3) from t100;
                                            QUERY PLAN
--------------------------------------------------------------------------------------------------
 Result  (cost=12.33..12.34 rows=1 width=12)
   InitPlan 1 (returns $0)
     ->  Limit  (cost=0.00..4.11 rows=1 width=4)
           ->  Index Scan using t100_pkey on t100  (cost=0.00..4.11 rows=1 width=4)
                 Index Cond: (c1 IS NOT NULL)
   InitPlan 2 (returns $1)
     ->  Limit  (cost=0.00..4.11 rows=1 width=4)
           ->  Index Only Scan using t100_c2_c4v on t100 t100_1  (cost=0.00..4.11 rows=1 width=4)
                 Index Cond: (c2 IS NOT NULL)
   InitPlan 3 (returns $2)
     ->  Limit  (cost=0.00..4.11 rows=1 width=4)
           ->  Index Only Scan using t100_c3 on t100 t100_2  (cost=0.00..4.11 rows=1 width=4)
                 Index Cond: (c3 IS NOT NULL)
(13 rows)

yugabyte=# explain /*+ IndexOnlyScan(t100 t100_c3) */select min(c1), min(c2), min(c3) from t100;
                                     QUERY PLAN
------------------------------------------------------------------------------------
 Aggregate  (cost=10000000010.75..10000000010.76 rows=1 width=12)
   ->  YB Seq Scan on t100  (cost=10000000000.00..10000000010.00 rows=100 width=12)
(2 rows)

A new config parameter, all-index-check was added to allow exploration of different indexes (371732b3ed375481e8e8a2e15fa6b1412276cc17).


Document workaround for LualineNotices and empty windows

Lualine warns about config issues during startup, but the recommended
:LualineNotices only spawns an empty window.
The empty window is related to loading the colorscheme after calling
lualine setup. Load lualine after the colorscheme:

#632

This is not what I meant also miss leading as other things can cause the same issue too . I think I have an idea to fix it will try that later.
TODO(shadman) Make only last call to setup trigger LualineaNotice message to trigger by differing message  showing to couple of seconds after nvim startup.


Use system default shell (future-proofing for macOS 10.15)

Starting with macOS 10.15, zsh will be the default system shell and bash will be deprecated.. This proposed change makes it so that the example configuration uses the system default shell, which is /bin/bash on 10.13 and 10.14 and /bin/zsh on 10.15. This works because /bin/sh is symlinked to the respective shells.

Added this a long with some other changes to the sample config. Thanks for the suggestion.


Bump minimum tx relay to 5000 sat / KB

In light of this post:
https://www.reddit.com/r/Bitcoin/comments/3oecqm/psa_to_address_mempool_flooding_bitcoin_core/
We should bump the min amount possible in the tx fee slider to 5000 sat / KB)
The code has been written so that any amount lower than that (currently minimum is 1000 sat / KB) will get lifted.

The minimum tx fee slider value is now 5000 sat/ KB.
Also this rate is used as the minimum in any send.
Awaiting review and closing

Verified working.
I've released a new version of BRIT Core (0.4.0) since it's unlikely there is anything else that will need to change there.
Closing.


Remove the color enum

This PR removes the color type enum as described in #72. I do not know if this has any side effects tough, everything compiles fine on my end, tests and examples compile and run as well. The only difference i noticed is in the readme_examples/readme_manipulation example part. The latter two colors arent the same but im not sure why.

Okay, the example now has the correct color and I've updated the Readme 👌

Nice! This is the best kind of pull request, where added/removed counter goes negative! My final request is that you mention "fixes #72" or "closes #72" in your PR description. That will go into the merge commit and automatically close the issue. :slightly_smiling_face:

Thanks!
bors: r+


workflow not work

when i config workflow = [('train', 2),('val',1)], train crash by this
assert len(data_loaders) == len(workflow)
because  len(data_loaders) always 1

hi ,@hellock,
you say " In detection tasks we implement mAP evaluation during training to serve as validation, so the val phase is unnecessary." where is it,in the tools/train.py I haven't found.

@alexwq100 Look here


#6 Debian & #7 Ubuntu Scrapers

What it does:

Gets the job done.

Things remaining:

Add test cases.
Remove boilerplate.

@kartiksibal the current data structure for the returned CVEs is not easily usable, instead of the current 3 lists of strings, we should return a single list of CVEs dictionaries.
Instead of:
(
    ['CVE-2016-5416', 'CVE-2012-6655'],
    ['389-ds-base', 'accountsservice'],
    ['not yet assigned', 'not yet assigned'],
)

Return:
[
    {
        'cve_id': 'CVE-2016-5416',
        'package_name': '389-ds-base',
        'vulnerability_status': 'not yet assigned',
    },
    {
        'cve_id': 'CVE-2012-6655',
        'package_name': 'accountsservice',
        'vulnerability_status': 'not yet assigned',
    },
]

It will be much easier to use that data structure to then create model instances (save the data in the DB).


Pyarrow_bindings

Adding type caster for pyarrow bindings

Dear @maximiliank,
while I appreciate the significant effort that must have gone into this, I don't think this a component that needs to be part of nanobind (of which I try to keep the core as small as possible). My suggestion would be that you set up a separate repository. The nanobind documentation could then link to this repository and include a sort of directory of repositories with additional type casters.
Best,
WEnzel

Dear @wjakob
thank you for your suggestion. I created a separate repository https://github.com/maximiliank/nanobind_pyarrow
Best,
Max

I added a commit referencing your repository from the documentation just now.


⚠ Bofrost.be has degraded performance

In 5508fd3, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2370 ms

Resolved: Bofrost.be performance has improved in 8e4ac98 after 42 minutes.


az keyvault key download failing on ubuntu

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az keyvault key show
Errors:
No module named 'azure.keyvault.v7_0'
Traceback (most recent call last):
python3/dist-packages/knack/cli.py, ln 206, in invoke
    cmd_result = self.invocation.execute(args)
cli/core/commands/__init__.py, ln 528, in execute
    self.commands_loader.load_arguments(command)
azure/cli/core/__init__.py, ln 299, in load_arguments
    self.command_table[command].load_arguments()  # this loads the arguments via reflection
cli/core/commands/__init__.py, ln 291, in load_arguments
    super(AzCliCommand, self).load_arguments()
...
<frozen importlib._bootstrap>, ln 961, in _find_and_load_unlocked
<frozen importlib._bootstrap>, ln 219, in _call_with_frames_removed
<frozen importlib._bootstrap>, ln 1014, in _gcd_import
<frozen importlib._bootstrap>, ln 991, in _find_and_load
<frozen importlib._bootstrap>, ln 973, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'azure.keyvault.v7_0'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az keyvault key show

Expected Behavior
Environment Summary
Linux-5.4.0-29-generic-x86_64-with-glibc2.29
Python 3.8.2
Shell: bash

azure-cli 2.0.81 *

Extensions:
azure-devops 0.17.0

Additional Context

hi @bim-msft could you pls have a look?thanks

@ashwarn Hi, could you upgrade your CLI to the latest version? I cannot reproduce this issue using https://shell.azure.com/
You may also try pip install azure-keyvault==1.1.0 to fix it.

Sure, I will do that and let you know.
On Fri, May 15, 2020, 4:15 PM Bin Ma<EMAIL_ADDRESS>wrote:

@ashwarn https://github.com/ashwarn Hi, could you upgrade your CLI to
the latest version? I cannot reproduce this issue using
https://shell.azure.com/
You may also try pip install azure-keyvault==1.1.0 to fix it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-cli/issues/13457#issuecomment-629050065,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD44QSGTV7GCOYBLXCFF5ODRRTMXBANCNFSM4M62L6YA
.

@ashwarn Hi, we are going to close the issue due to long time inactivity. If you have anything unresolved, just feel free to reopen this and I will continue to follow up this.

Please see https://github.com/Azure/azure-cli/issues/19640#issuecomment-1148202854


Publish to npm

Can you publish this to npm?

@mathiasbynens Any chance of revisiting this decision? Times have changed. npm is not just for node modules anymore.

Never has been, but certainly not now :-)

@feross as it seems that won't be happening for a while, would you mind pulling version 2.1.0 into your fork? Thanks! :+1:

@Qantas94Heavy Done, 2.1.0 is published!


error to install typescript

error to install typescript

This is not the right place to log issues with installing TypeScript. Please read the error message for instructions on what to do.


parameter

Describe the Change You Would Like
A clear and concise description of what you would like changed.
looks need to mention explicitly the case of the task parameter must be lowercase

@tdtheautomator Thanks for opening this issue. We have an existing issue to document task parameter constraints (https://github.com/puppetlabs/bolt/issues/2240) so I'm going to close this as a duplicate.


Responsive Navigation Header

I think there are a few item to address in Issue #3
It can probably be broken down in 4 chunks:

Header bar collapses to a hamburger menu
Cards collapse to 2 columns and then 1 column (or just skip from 3 to 1)
Filterbar changes orientation on smaller screens? (stacked filters) or maybe only search
Rework the cop detail pane to slide out and fit on smaller screens.

This PR addresses item number 1 by making the navigation header responsive and swaps the links for a hamburger menu on smaller screens.
I'm not very familiar with styled-components and it looked to me like it was already opening us up to a lot of duplication of components and styles. I am pretty familiar with https://material-ui.com, their Grid system works pretty well and they have great documentation. I went ahead and set it up for the project and added a simple theme with some base colors.
Ill wait to get some feedback before merging this since it could have a lasting impact on the direction of the front end tool set.

Yes - this should definitely be broken down into 4 chunks. I'll rewrite the original issue to reflect the first chunk (Navigation Header).
Imho styled-components are reusable, but we need to go the extra mile to re-use them, organize them and avoid de-duplicate them: its strength in flexibility turns into a weakness for distributed teams
I'm in favor of using the approach suggested in this PR:

use material-ui for base components (its a very well supported library)
use the useStyle hooks to customize components to our styles (awesome it has this feature, which also makes it similar to styled-components anyways)

Material-ui even comes with its own version of styled components if we could not find the right component in their existing API. https://material-ui.com/guides/interoperability/#styled-components. Though in practice using their base components is usually the way to go.

I found 3 small css issues and 1 component issue that this PR introduces, nothing major and expected as the Material-UI library is introduced and tweaked:
CSS issues:

Container max-size:
PR view:

Original view:

I think this might have something to do with some container wrapper that was removed. It might be the introduction of the Material-UI Theme Provider or removing <div className="app-body" align="center">
.app-body {
  display: flex;
  flex-flow: column;
  height: 100%;
}

Container max-size (part 2):
PR view:

Original view:

This container max-size issue seems to also spillover into the About component

Related to (2) - theres a white gap introduced between the Header Navigation component and About component, this might just be padding in useStyles.

Component issue:

On mobile menu clicking "About" does not trigger About component. I think this is also somewhat a larger discussion on refactoring the About component in general (it could technically just be a new page on  instead introducing the complexities of a reveal

Thanks for the feedback @JohnCLo . I'll update tonight

My pixel pushing eyes are getting tired! I think I have the about page fixed up, along with the header bar spacing for the items.
I had to make a few tweaks to the filter bar and cop list to get them back to center.

Looks like main component overflows on top of the map component, might be a css position issue:

Other than that its looking really good!

@JohnCLo It was getting too cumbersome to do these piece meal and since no one had taken up the other issues yet I included more changes in this PR.
The site should be fully responsive now.
The cop detail pane has been updated to use a drawer and resized to fit on mobile.
The about page is responsive.
The filter bar will change to a single column of filters on smaller screens.
The cop card list will change from 3 to 2 to 1 cards in a row.
There are more small tweaks we can make. Let me know if you see anything still glaring that I missed.

Unfortunate it not working well in Chrome. Something about the svg map is no longer creating a content box to hold its space.
I'm also having difficulty on my machine using Chrome (hogs memory and wont load pages) so its hard to me to debug at the moment.
@sherryxiao1988 or @harmanbains  Could either of you take a look and see if you can get the map working in chrome again?

@kgstew great stuff - sorry was offline the past few days for work stuff. But overall looks really good and sets up a strong foundation moving forward. I'll have some time tomorrow to look into the svg map, if not swap it with a newer component. Thanks!

Resolves #3 #5 #6


Add new account error

Azure Data Studio Version: 1.2.4
The following error message appears when signing in to Azure account :

Error adding linked account
Error: self signed certificate in certificate chain
Steps to Reproduce:
I get this error when adding a new account. It immediately displays. It may have a lot to do with the corporate firewall. Do we need to import a "safe" certificate to ADS in order to get outside?

@wfsharon  Thanks for reporting the problem.  We're currently investigating this bug with issues https://github.com/Microsoft/azuredatastudio/issues/545 and https://github.com/Microsoft/azuredatastudio/issues/3298.  I'll close this as a duplicate.

I'm still getting this error in ADS

Same here .. even on V1.3.9. Other threads are pointing to a very-well known node.js issue of reading its own fixed list of certificates rather then the cert store (I'm amazed they can still get away with it). Face it, most developers (and potential ADS users) sit behind corporate firewalls.

so I'm confused why they have this issue as marked as closed, when it's simply not fixed.  I'm just trying to play around with ADS and come up to speed with it, and it's not even working.  very frustrating


Wrong recipient, payload audience != requiredAudience

Been trying to figure out what is wrong in my code since Tut does not follow newest changes in UI. Now i am running into Issue Below pleases suggest workaround. Also Which Client ID should i Use since doc not in Sync.
This error seems to occur after "Privacy Policy MSG" is displayed
Error: Wrong recipient, payload audience != requiredAudience
    at OAuth2Client.verifySignedJwtWithCerts (/srv/node_modules/google-auth-library/build/src/auth/oauth2client.js:696:23)
    at OAuth2Client.<anonymous> (/srv/node_modules/google-auth-library/build/src/auth/oauth2client.js:514:38)
    at step (/srv/node_modules/google-auth-library/build/src/auth/oauth2client.js:57:23)
    at Object.next (/srv/node_modules/google-auth-library/build/src/auth/oauth2client.js:38:53)
    at fulfilled (/srv/node_modules/google-auth-library/build/src/auth/oauth2client.js:29:58)
    at <anonymous>
    at process._tickDomainCallback (internal/process/next_tick.js:229:7)

Same issue here

Found any solution ?

The problem here is the client_id that is being used to create an OAuth2Client and the client_id being used as the audience in the verifyIdToken is not the same. The client_id for the audience should be the client_id that was used in your frontend application to get the id_token.


Docs update

Updated the docs about installing contentful/laravel instead of contentful-bundle.

Sorry @jevets, overlooked this PR. Merged now :)


Localizable.strings localized only for a single language generated incorrectly

If there is a file like Localizable.strings localized only for a single language (one folder en.lproj):

xcodegen doesn't pick this up correctly. After generating the xcode project, the file is not localized and thus not picked up at runtime:

If I add a second language just as a placeholder, it is picked up correctly:

Same question


Fetch just files modified since last fetch

To avoid having to pull everything, it would be useful to be able to fetch just metadata that is likely to have changed since the last time files was run.
https://developers.google.com/drive/api/v3/search-files says:
modifiedTime > '2012-06-04T12:00:00' // default time zone is UTC

I can do this in SQL:
select max(modifiedTime) from files

Which currently returns 2022-02-18T00:00:16.995Z.

So I could do something like this:
google-drive-to-sqlite files files.db --since

Which would look up the current max modifiedTime and ask for everything since then.
(Duplicating the --since option from twitter-to-sqlite.)

Other naming options:

--sync
--incremental
--since-last
--since

I actually quite like --since-last - it's more obvious than just --since.
Also, running --since-last won't capture the fact that files have been deleted, --sync might misleadingly imply that.

I ran a quick test to see if the modifiedTime for a folder was updated when a file was uploaded to that folder, but sadly it was not:
% google-drive-to-sqlite files --folder '1dbccBzomcvEUGdnoj8-9QG1yHxS0R-_j' --nl | jq '{name:.name, t:.modifiedTime}'
{
  "name": "two",
  "t": "2022-02-19T04:22:38.714Z"
}
{
  "name": "one",
  "t": "2022-02-19T04:22:33.581Z"
}
% google-drive-to-sqlite files --folder '1dbccBzomcvEUGdnoj8-9QG1yHxS0R-_j' --nl | jq '{name:.name, t:.modifiedTime}'
{
  "name": "two",
  "t": "2022-02-19T04:22:38.714Z"
}
{
  "name": "one",
  "t": "2022-02-19T04:22:33.581Z"
}
{
  "name": "california_warn_raw.csv",
  "t": "2020-11-11T18:10:31.000Z"
}

I'm worried that this option just won't work correctly at all with the --folder X option, which is where I most want to use it!
Probably need to disallow --since if you try to combine it with --folder to avoid confusion.


Change on home text message

Thanks. I'll apply the comma separately, because that makes sense, but I'm going to decline the "split-string" part -- determining the correct first name or names for a person of indeterminate nationality is not a solved problem in computer science, so the username is much less likely to cause annoyance. :-)


Rename symbol replaces default keyword for  defaut export of anonymous function

TypeScript Version:  3.3.0-dev.20190124

Search Terms:
rename, rename symbol, default, export, anonymous default export
Code
a.ts
import log from './b';

log('test'); // use Rename Symbol on `log` here with `test`

b.ts
export default function(a: string) {
    console.log(a);
};

Expected behavior:
When I use Rename symbol in VS Code on log function call - log  should be replaced with test only in src/a.ts
VS Code uses TypeScript version from local node_modules. When I install typescript@latest (3.2.4) it works as supposed.
Actual behavior:
default is replaced with test in src/b.ts
export test function(a: string) {
    console.log(a);
};

Same for export default class {}; and export default () => {}
I don't see any error in TS Server logs.
Playground Link: Doesn't work for multiple files
Related Issues: #11308

After recent tests with latest stable and nightly versions of TS and VS Code I'm unable to reproduce this issue.


PUSH: error: error while sending push TypeError: type.startsWith is not a function

Environment Setup
Parse server: 2.2.7
Steps to reproduce
Installed parse server and tried to send push notification and error was shown in the logs
Logs/Trace
error: error while sending push TypeError: type.startsWith is not a function     at mongoFieldToParseSchemaField (/parse/node_modules/parse-server/lib/Adapters/Storage/Mongo/MongoSchemaCollection.js:32:12)     at /parse/node_modules/parse-server/lib/Adapters/Storage/Mongo/MongoSchemaCollection.js:65:22     at Array.reduce (native)     at mongoSchemaFieldsToParseSchemaFields (/parse/node_modules/parse-server/lib/Adapters/Storage/Mongo/MongoSchemaCollection.js:64:29)     at mongoSchemaToParseSchema (/parse/node_modules/parse-server/lib/Adapters/Storage/Mongo/MongoSchemaCollection.js:91:13)     at Array.map (native)     at /parse/node_modules/parse-server/lib/Adapters/Storage/Mongo/MongoSchemaCollection.js:183:24     at run (/parse/node_modules/babel-polyfill/node_modules/core-js/modules/es6.promise.js:89:22)     at /parse/node_modules/babel-polyfill/node_modules/core-js/modules/es6.promise.js:102:28     at flush (/parse/node_modules/babel-polyfill/node_modules/core-js/modules/_microtask.js:18:9)

Can you include more details about how you sent the push, what the payload looks like, etc?

I sent the push using postman. To this URL:
http://<IP_ADDRESS>:1337/parse/push
Here is the Payload:
In my mongodb collection, I have added a field for username and I am making the query based on username. I am also sending ReportID and Category as data in my push message.
{
"where": {
"username": "RegeShark"
},
"data": {
"alert": "Your Report #A1434367039545 changed status to resolved",
"sound": "default",
"reportid": "#B1450429923842",
"category": "FIRST_CATEGORY"
}
}

Closing due to lack of activity, please update to latest parse-server version and reopen if the issue persist.
Don't forget to include your current:

node version
npm version
parse-server version
any relevant logs (VERBOSE=1 will enable verbose logging)


Fixed null safety issue for transform scale

Hi @DarkKnight1005, thanks for the PR,
Could you provide detail of the issue?

"Error: The argument type 'double?' can't be assigned to the parameter type 'double' because 'double?' is nullable and 'double' isn't.
scale: _scale,"


Update dev-1.29 branch to sync with main

Fix a merge conflict provoked by PR #42823

/approve
given the time constraints. A second approval would be nice.

/approve

Oops. https://github.com/kubernetes/website/pull/44286#event-11201373628 fixes a stylesheet needed for the v1.29 metrics.


Update PHP 8.2 Runtime

I checked all PHP8.2 extensions and it seems like only php8.2-pocv is still missing, therefor I uncommented all other extensions which are available.
This can be tested with the following repository:
git clone git@github.com:Jubeki/laravel-sail-test-php82.git
cd laravel-sail-test-php82
cp .env.example .env
composer install --ignore-platform-reqs
sail up -d
sail composer update
sail artisan key:generate
sail php --version
open http://<IP_ADDRESS>

<3


Problem with mocks in tests with Object

Hello, I have some strange behavior in tests: when I mock class which is inherited from Object I can't call to some(I realy don't know whats the difference) functions - it just return NULL without any errors:
$tmpMock = $this->getMock(\yii\base\Object::class);

var_dump($tmpMock->hasProperty('tmp'));
exit;

Result is:

And same behavior for private and nonexistent function: I can call to it without any errors and it will return NULL.
$tmpMock = $this->getMock(\yii\base\Object::class);

var_dump($tmpMock->someFnc());
exit;

Result the same.
When I mock class, which isn't inherited from Object, I get an error(Pricelist is not extends from Object):
$tmpMock = $this->getMock(Pricelist::class);

var_dump($tmpMock->someFnc());
exit;

Result is:

And I have no problem to call existing functions of this class.
Im use Yii 2.0.7, yii2-codeception 2.0.4, codeception 2.1.2 (same on the 2.1.6) and php7.

@klimov-paul, it's not a question, it's a bug, I can't test code, can't mock functions.

Do you know waht exactly  $this->getMock() does?

@klimov-paul, I need mock function, like isCanCalculated so it will return true, then I try to call public function calculate and it just return NULL and doesn't execute code.

So, you do NOT know.
Lets take another try: how does getMock() method works.
Really, once you will get question answered - you can resolve your problem.
So?

I can tell for sure, this does not relates to Yii - it relates to 'PHPUnit Mock Framework' usage.
You have made quite a common mistake with your code.
But one you'll give enough attention to the description of the getMock() method and its arguments - you can get things right.

@klimov-paul, thanks.


Reduce cache time for tarballs to 1 minute

This serves the original purpose of preventing the tarball creation on every task while still providing timely updates.

👍


Enable run button faster after switching language

After switching programming language, it takes way too long before the run button gets enabled.

Only happens with switching to Python, so apparently some setup needs to be done first?

Correct, the initialization of the Python worker takes a while as it loads in the standard library and runs some initial code. I don't think our use case involves switching languages often, and the loading time of the worker is only a few seconds. Since users still need to write their code anyway, this doesn't seem to be a real issue?


Backport pick_first fix to v1.19.x

The original fix (#18598) is modified to fit into v1.19.x.
I have verified that the test fails before the fix and passes after the fix.

@srini100 Please merge this patch, thanks!

@lidizheng, this will require a new RC since pick first is default policy.

Distribution Tests Linux (standalone subset): https://github.com/grpc/grpc/issues/18548

I think we need a patch release for v1.19.
It's not in v1.20.x yet. Backporting it via https://github.com/grpc/grpc/pull/18629.


Docker swarm doc updates - 1

Model docs,structure it similar to K8s deployment

have one standard deployment,put custom deployment in notes
have pre-populated, placeholders in configs
remove 'dev' way of deploying - rm config-dev.json, image in custom
stack
update the 3.5 image with production one

Need to add resource values of zookeeper swarm in  git.

First part of swarm docs updates, which has changes in :

infrastructure
mon-stack
nginx
databroker
rs

Remaining will be done in next PR.


Fix settings overlay for narrow screens.

First commit is to show the right section correctly when increasing screen width.
Second commit is to always show the left section only when opening overlays in narrow screens.

Fixes:  https://chat.zulip.org/#narrow/stream/9-issues/topic/settings.20overlay.20on.20small.20screen.20sizes

Screenshots and screen captures:

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

The current behavior for narrow screens is -

On opening the overlay, we always show the left panel list. Previously it showed the right section, that too with both "Profile" and "Account and privacy" sections shown one below the other, when the overlay was closed when a right section was opened.
On increasing the screen width, the right section becomes visible as per the url, which is set as the first section or the last opened section.
Behavior on manually chaning the url hash is same. There are two cases here -

Initially only left panel shown is shown - if the url is changed from #settings/profile to #organization/organization-profile, then only the left panel is shown with organization settings panel list. But if the url is changed from #settings/profile to #settings/account-and-privacy, then the "Account and privacy" right section is opened. This is same as previous behavior.
Initially a section is opened on right side - if the url is changed from #settings/profile to #organization/organization-profile, "Organization profile" section is opened on right side. Previously, this change did nothing. But I guess the current behavior is also fine. For other case, i.e. changing from #settings/profile to #settings/account-and-privacy, the behavior is same as above which means "Account and privacy" section will be opened on right side, and this is same as previous behavior.

I have explained the current behavior in this PR above, but might be better to test it manually to get a clear idea.

Hm, so playing with this PR:

Make the screen narrow.
Open your user card.
Click "Edit your profile".

The result is that the http://localhost:9991/#settings/profile URL is opened, but the left-side panel is shown. I think it would be better to open just the Profile panel in that situation, if it's not too tricky to arrange.
So long as we don't have things that look totally busted, I'm primarily concerned about what happens in states that are reachable from the UI, without manual URL editing.

Everything else felt reasonable to me.

@timabbott over to you. I haven't re-tested with the latest change.

Merged, thanks @sahil839!


Transition project to modern Jetpack Compose

Thanks for stopping by to let us know something could be better!

PLEASE READ
If you have a support contract with Google, please create an issue in the support console. This will ensure a timely response.
Discover additional support services for the Google Maps Platform, including developer communities, technical guidance, and expert support at the Google Maps Platform support resources page.
If your bug or feature request is not related to this particular library, please visit the Google Maps Platform issue trackers.
Check for answers on StackOverflow with the google-maps tag.

Is your feature request related to a problem? Please describe.
Your build gradle is the old style of gradle. This shows that the project is using old Jetpack Compose. It would be great if this project/example is migrated to latest Jetpack Compose (to the date of writing this) and migrate your gradle to the newer version.
It is frustrating trying to adapt your code to latest version of Jetpack Compose as one has to deal with deprecated composables.

If you would like to upvote the priority of this issue, please comment below or react on the original post above with :+1: so we can see what is popular when we triage.
@alghe-global Thank you for opening this issue. 🙏
Please check out these other resources that might help you get to a resolution in the meantime:

Check the issue tracker - bugs and feature requests for Google Maps Platform APIs and SDKs
Open a support case - Get 1:1 support in Cloud Console.
Discord - chat with other developers
StackOverflow - use the google-maps tag

This is an automated message, feel free to ignore.

Not the most well-written bug ticket I have ever seen but I like the spirit of it!


GL_SCISSOR_TEST doesn't work in iOS.

Created default app using LibGDX version 1.6.0
Compiled with RoboVM 1.5
@Override
public void render ()
{
	Gdx.gl.glClearColor(1, 0, 0, 1);
	Gdx.gl.glClear(GL20.GL_COLOR_BUFFER_BIT);

	batch.begin();
    Gdx.gl20.glEnable(GL20.GL_SCISSOR_TEST);
	batch.draw(img, 0, 0);
    Gdx.gl20.glDisable(GL20.GL_SCISSOR_TEST);
	batch.end();
}

https://github.com/libgdx/libgdx/blob/master/CONTRIBUTING.md#using-the-issue-tracker

I performed a search with no result. This is a valid issue.

Please read the link, that isn't a self contained test, and 'doesn't work' is not a helpful description of an issue.

This is not an issue with libgdx, this is an issue with your code. The code you provided clearly shows that you haven't verified that this is a libgdx issue. Try the forum or IRC first. Please don't use the issue tracker for personal support requests.

I compiled with default app and only added those lines.

@voidstarfire could you please make a github repo with a minimal self-contained test case? If this is indeed a bug, I'd be glad to know of it, yet I don't have any Mac at hand ATM to verify.

I found the solution for iOS devices.
batch.begin()

causes glScissor to be reset on iOS devices to 0,0,0,0.
Calling
Gdx.gl.glScissor(0,0, Gdx.graphics.getWidth(), Gdx.graphics.getHeight());

at the start of the render loop seems to fix this, only needed for iOS devices.
The only thing I added to a default LibGDX 1.6.4 project with RoboVM 1.5 was:
@Override
public void render ()
{
    Gdx.gl.glClearColor(1, 0, 0, 1);
    Gdx.gl.glClear(GL20.GL_COLOR_BUFFER_BIT);

    batch.begin();
    Gdx.gl20.glEnable(GL20.GL_SCISSOR_TEST);
    batch.draw(img, 0, 0);
    Gdx.gl20.glDisable(GL20.GL_SCISSOR_TEST);
    batch.end();
}

Self contained test case:
https://github.com/voidstarfire/GL-Scissor-Example

Ah, so the issue you were reporting is that if you enable scissors but don't define the scissor box, that the scissor box is undefined. Please be aware that there is no way we could get that from your issue description of 14 words, nor from the limited code you included (which just enables scissors and then disables it again, without ever using it).

Yup. It's just as xoppa pointed out - since OpenGL is a state machine, you generally shoudn't assume anything about any particular state until you set it yourself - same goes with scissoring. IMO you should provide e.g. Gdx.gl.glScissor(0,0, Gdx.graphics.getWidth(), Gdx.graphics.getHeight()); (or any other initial scissor values) on every platform before even using the scissor test. The fact it did work on platforms other than iOS means you got lucky; still, relying on UB is hardly a good thing.

Ah yes sorry about the breif intro I was incrediblly intoxicated at the time. At least people who come across this bug or not will find a solution :-)


httpclient.processor: additional variable(s) on SpEL context to evaluate reply

Please expose the  original message in evaluation context while evaluating the final replay inhttpclient.processor, so the replyExpression could be written like this :
{
'name':#message.payload.someExpression,
'val': body.anotherExpression
}

Thanks

This looks like a new feature request.
Since all the SCSt applications have been severed to their own repositories, consider to move the issue to the appropriate place https://github.com/spring-cloud-stream-app-starters/httpclient/issues.
And, please, share more info what is the purpose of the feature.
Thanks

And, please, share more info what is the purpose of the feature.
Well, with the current implementation I can only transform message against response body, the original message payload is not accessible in replyExpression.
The purpose of the feature is  to expose original message payload in evaluation context and provide capability to include some values from original message to transformed message.

OK. But I said you already: this is already a wrong place to ask such a new feature.
Plus keep in mind that nowhere in Spring Integration we have something like replyExpression.
The standard behavior is to return the reply as is and let the further component to deal with its transformation. It isn't the tarter service gateway responsibility to modify reply. That doesn't look like loosely coupling and microservices architecture.
Therefore you should just place the requestMessage into headers before httpclient and use it afterwards in the transformer.
OTOH that isn't good idea to expose it as a SpEL variable because we would have to create EvaluattionContext for each message to send. That is some performance impact for most cases when we don't need requestMessage for reply evaluation. Therefore I'd recommend to do such a logic only in your custom httpclient, but not as an out-of-the-box requirement. Anyway that's why they are called starters: you pick up the one as is and modify for your business. That is the best middle ground to avoid unexpected misbehavior in other places.
Does it make sense for you?

Sounds reasonable...
I can't find the example how to customize the standard starter, I would appreciate  if you point me to some sample.
Thanks
Alexander

Looks like this should help you somehow: http://docs.spring.io/spring-cloud-stream-app-starters/docs/1.0.4.RELEASE/reference/html/_introduction.html#_patching_pre_built_applications

Yeah,  I saw this, but it doesn't show how to customize the processor...

Eh... Agreed. That is embarrassing without copy/paste of that code :smile:
Consider the Aggregation approach for your solution.
So, you can have a header-enricher processor before httpclient, then httpclient, and transformer afterwards to consult the reply as a payload and headers for request message.
Hope that helps

@artembilan, I've tried  what you'd suggested, but got MessageHeaders is immutable :

This is how I tried to  enrich headers with transformer starter:
transformer.expression=null == headers.put('myHeader','myValue')?payload:payload
Please advise
Thanks

@jvmlet ,
Eh... I agree that there is no out-of-the-box header-enricher-processor. Maybe just because there was no request before?..
You can achieve that withe the custom processor configuration for your Aggregation:
@EnableBinding(Processor.class)
public class HeaderEnricherConfiguration {

        @Bean
	public IntegrationFlow headerEnricherFlow() {
                return IntegrationFlows.from(Processor.INPUT)
					.enrichHeaders(e -> e.headerFunction("requestMessage", m -> m))
					.channel(Processor.OUTPUT)
					.get();
	}

}

Right, this isn't flexible, but we really talk here about your custom solution. So, such a hard code should fix your current requirements.
Regarding mutability of MessageHeaders. Right, that is a fact. You can't modify headers directly you have to crate a new Message using MessageBuilder. Maybe something like this:
transformer.expression=T(org.springframework.integration.support.MessageBuilder).fromMessage(#root).setHeader('requestMessage',#root).build()

Thanks, the above transformer.expression does the trick.


test statefulsets in our CI

Right now we test headless service, but its not a stateful set. This may have implications on DNS, at the very least

not stale
On Wed, Apr 21, 2021 at 10:05 PM Istio Policy Bot @.***>
wrote:

🧭 This issue or pull request has been automatically marked as stale
because it has not had activity from an Istio team member since 2021-01-21.
It will be closed on 2021-05-06 unless an Istio team member takes action.
Please see this wiki page
https://github.com/istio/istio/wiki/Issue-and-Pull-Request-Lifecycle-Manager
for more information. Thank you for your contributions.
Created by the issue and PR lifecycle manager.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/30283#issuecomment-824540986, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXLAHDCNLCTOAHIGV5TTJ6VCRANCNFSM4WNNO7BA
.


Add a reusable workflow for integration-test

replaced by https://github.com/nervosnetwork/godwoken-tests/pull/65