Jest failing with "Call retries were exceeded", using --runInBand works-around issue

🐛 Bug Report
I've got 2 test files. In the test, a WebAssembly object gets instantiated. This instantiation seems to stall for some reason when running the test in CI. Locally running jest passes the tests fine.
In CI they fail with this error:
  ● Test suite failed to run

    Call retries were exceeded

      at ChildProcessWorker.initialize (../node_modules/jest-worker/build/workers/ChildProcessWorker.js:193:21)

When -i is used however, they pass as well in CI.
Jest: 24.8.0
Node: 10.15.0
Local env: macOS, 10.14.6 (18G84))
CI env: CircleCI, Docker Linux 6a7bd3b63625 4.15.0-1035-aws #37-Ubuntu SMP Mon Mar 18 16:15:14 UTC 2019 x86_64 GNU/Linux
To Reproduce
I don't have a concise repro repo at this moment.
Expected behavior
I expect the tests to pass as well when not run in band.
Link to repl or repo (highly encouraged)
Don't have it at this moment.
Run npx envinfo --preset jest
Paste the results here:
CI:
npx: installed 1 in 1.719s

  System:
    OS: Linux 4.15 Debian GNU/Linux 9 (stretch) 9 (stretch)
    CPU: (36) x64 Intel(R) Xeon(R) Platinum 8124M CPU @ 3.00GHz
  Binaries:
    Node: 10.15.0 - ~/.nodenv/versions/10.15.0/bin/node
    Yarn: 1.17.3 - /usr/bin/yarn
    npm: 6.4.1 - ~/.nodenv/versions/10.15.0/bin/npm

Local:
Environment:
  OS:  macOS 10.14.6
  Node:  10.15.0
  Yarn:  1.17.3
  npm:  6.4.1
  Watchman:  Not Found
  Xcode:  Xcode 10.3 Build version 10G8
  Android Studio:  3.1 AI-173.4819257

do you use jest-worker? Please provide more information about your use of it if available. or say more about the file that runs your test.

do you use jest-worker?

Not that I’m aware of? I do see it as a dependency in my yarn.lock file.
But I didn’t add any configuration in the jest.config.js for it.
I will try to create a minimal repro example when I find some time.

Ok, do you provide a reproduce code?

I will try to create a minimal repro example when I find some time.

Any lucky on this? I am having the same issue after upgrading to node v13.

I observed that the issue occurs with node v13.2.0, but not with v13.1.0. Looks like the issue with only the latest node version.

@antony2025 same here. After upgrading to node v13.2.0 my test suite which has many async test statements started to fail. Funny thing is that if I delete a few async tests from the test suite it works again.

Same for me I have the same issue w/ Node 10.17.0

I just faced the same issue in CI and was able to reproduce it in local by switching to the latest version of node. As suggested, only by downgrading fixes it for me, using -i didn't.

I have observed the same issue on Node 13.2.0 (where updating node is the only change since it was previously working reliably; package-lock.json has not changed, and I have tried before and after clearing out and rebuilding node_modules).
For me, running with --runInBand results in 8266 Segmentation fault: 11 at the same point where it otherwise fails with Call retries were exceeded at ChildProcessWorker.initialize. I am running on macOS 10.14.6 and installed node via Homebrew. After the crash it notes that it reached 33 passing test suites with 106 total tests. The codebase contains 34 test suites and 122 total tests (I don't know if these numbers are similar for other people hitting the issue?). I have many async tests in the rest of the code but the suite which hits this error contains only synchronous tests.
Since it's segfaulting, I suspect this is a bug in Node itself (seemingly a regression since this was an issue before), but I have no idea where to begin looking!

Appears this issue has been reported upstream: nodejs/node#30730

Hey guys! I was having this issue on CI only (CircleCI). So I changed the following value on CI config file and the issue has gone:
Before
version: 2
jobs:
  build:
    docker:
      - image: circleci/node:latest-browsers

Then
version: 2
jobs:
  build:
    docker:
      - image: circleci/node:12-browsers

Error:
Test suite failed to run Call retries were exceeded at ChildProcessWorker.initialize (node_modules/jest-worker/build/workers/ChildProcessWorker.js:193:21)
Confirmed fix:
Upgrade from nodejs 13.2.0 to 13.3.0
Environment
I had this error with
Windows 10
nodejs 13.2.0
Yarn 1.19.2
Package.json
"dependencies": {
    "@testing-library/jest-dom": "^4.2.4",
    "@testing-library/react": "^9.3.2",
    "@testing-library/user-event": "^7.1.2",
    "react": "^16.12.0",
    "react-dom": "^16.12.0",
    "react-redux": "^7.1.3",
    "react-scripts": "3.3.0",
    "redux": "^4.0.4"
  },
"devDependencies": {
    "@storybook/addon-actions": "^5.3.0-beta.16",
    "@storybook/addon-docs": "^5.3.0-beta.16",
    "@storybook/addon-knobs": "^5.3.0-beta.16",
    "@storybook/addon-links": "^5.3.0-beta.16",
    "@storybook/addon-storyshots": "^5.3.0-beta.16",
    "@storybook/addons": "^5.3.0-beta.16",
    "@storybook/preset-create-react-app": "^1.3.2",
    "@storybook/react": "^5.3.0-beta.16",
    "babel-loader": "^8.0.6",
    "react-test-renderer": "^16.12.0"
  }

Storybook initStoryshots from '@storybook/addon-storyshots'
When following the tutorial in https://www.learnstorybook.com/intro-to-storybook/react/en/simple-component/
The code below is where the error occured.
// src/storybook.test.js
import initStoryshots from '@storybook/addon-storyshots';
initStoryshots();

What helped me was upgrading the runner machine to a one with more memory.

@mvasin how much memory has your machine now?

same with node 10.19.0, ubuntu 20.04

adding --runInBand, worked for me. I don't know why and I don't care as long as i see greens :green_circle: :see_no_evil:

any solution on this?

@davidje13  thanks for the info, will check right now I'm update to node v13.3.0 still having and issue call still having an issue Call retries were exceeded

I don't know if it helps anyone, but I was getting this error when running in a docker container on macOS, and I fixed it by increasing the memory available in Docker Desktop for Mac preferences.

It is a bit embarassing for us node devs that 2 cpu and 4gb ram cannot run unit tests properly :disappointed:

Well don't feel quite so bad, the default was 2gb ram and increasing to 4gb prevented this error 🙂

Just spotted this in the docs:

For environments with variable CPUs available, you can use percentage based configuration: --maxWorkers=50%

We're going to use this for a while and see whether this issue still happens.

This now produces actual errors and fails the test suite on Nodejs 15, where unhandled promise errors are treated as exceptions.

This now produces actual errors and fails the test suite on Nodejs 15, where unhandled promise errors are treated as exceptions.

You save my time 👍

I'm seeing this on Node 10 as well!

I'm also seeing this on Node 14, specifically 14.15.1. Running with --runInBand fails with a SIGSEGV.

Seeing this on 12.18.4/13.1.0

also seeing this on node 12.18.4

seeing this on node 14.15.0

seeing this on node 14.15.0

Still an issue using 14.14.0

Still an issue using 14.14.0

have same issue  jest.useFakeTimers(); solve the problem, just add it after your imports .

have same issue  jest.useFakeTimers(); solve the problem, just add it after your imports .

Still has an issue on NodeJS 15.5.1

Having the same issue, using workers

Having the same issue, using workers

@lamhieu-vk
Anyone can easily reproduce this bug locally. Here's how:

yarn add -D segfault-handler
write this test:

var SegfaultHandler = require('segfault-handler');

describe("segfault", () => {
  it("should segfault", () => {
    SegfaultHandler.causeSegfault();
  });
})

write at least 1 other test
yarn jest (or whatever your test command is)

Output:
 PASS  src/utils/mergeIndexDTs.test.js
 PASS  src/utils/getIndexEntries.test.js
 PASS  src/drivers/translationDriverTests.test.js
NodeSegfaultHandlerNative: about to dereference NULL (will cause a SIGSEGV)
NodeSegfaultHandlerNative: about to dereference NULL (will cause a SIGSEGV)
NodeSegfaultHandlerNative: about to dereference NULL (will cause a SIGSEGV)
 FAIL  src/drivers/segfault.test.js
  ● Test suite failed to run

    Call retries were exceeded

      at ChildProcessWorker.initialize (../../node_modules/jest-worker/build/workers/ChildProcessWorker.js:193:21)

Test Suites: 1 failed, 10 passed, 11 total
Tests:       60 passed, 60 total
Snapshots:   36 passed, 36 total
Time:        8.243 s

The bug in jest is that it does NOT display "your test caused a segfault in node."
This is a combination of 2 bugs. The more serious one is SOMETHING IN YOUR TEST CAUSES A SEGFAULT :). But Jest should still tell us that the process segfaulted.
Fortunately, I can tell you that ChildProcess does report the SIGSEGV in its internals because I stepped through a jest test with the chrome debugger to make sure, so it's just a question of Jest noticing this in ChildProcessWorker.initialize() when retrying, and reporting "the test caused a segmentation fault in node, likely due to a serious bug in an internal module you are using." or some such language

@lamhieu-vk
Anyone can easily reproduce this bug locally. Here's how:

yarn add -D segfault-handler
write this test:

var SegfaultHandler = require('segfault-handler');

describe("segfault", () => {
  it("should segfault", () => {
    SegfaultHandler.causeSegfault();
  });
})

write at least 1 other test
yarn jest (or whatever your test command is)

Output:
 PASS  src/utils/mergeIndexDTs.test.js
 PASS  src/utils/getIndexEntries.test.js
 PASS  src/drivers/translationDriverTests.test.js
NodeSegfaultHandlerNative: about to dereference NULL (will cause a SIGSEGV)
NodeSegfaultHandlerNative: about to dereference NULL (will cause a SIGSEGV)
NodeSegfaultHandlerNative: about to dereference NULL (will cause a SIGSEGV)
 FAIL  src/drivers/segfault.test.js
  ● Test suite failed to run

    Call retries were exceeded

      at ChildProcessWorker.initialize (../../node_modules/jest-worker/build/workers/ChildProcessWorker.js:193:21)

Test Suites: 1 failed, 10 passed, 11 total
Tests:       60 passed, 60 total
Snapshots:   36 passed, 36 total
Time:        8.243 s

The bug in jest is that it does NOT display "your test caused a segfault in node."
This is a combination of 2 bugs. The more serious one is SOMETHING IN YOUR TEST CAUSES A SEGFAULT :). But Jest should still tell us that the process segfaulted.
Fortunately, I can tell you that ChildProcess does report the SIGSEGV in its internals because I stepped through a jest test with the chrome debugger to make sure, so it's just a question of Jest noticing this in ChildProcessWorker.initialize() when retrying, and reporting "the test caused a segmentation fault in node, likely due to a serious bug in an internal module you are using." or some such language

[SOLVED]
just use: jest.useFakeTimers()

Running the tests at CircleCI, I found that if I just run jest, the error that normally appears is: "Call retries were exceeded".
But if I execute jest --coverage the first error that appears is "ENOMEM: not enough memory, read" and then the error above appears.

To solve the problem I am now using jest --maxWorkers=4 and jest --coverage --maxWorkers=4.

I'm facing this issue too, any update?

I updated my node version from 12.18 to 15.8 and that solved the problem for me.

This also seems to happen on our CI with 62G memory & 8 cores.

For us this actually happened due to uncaught promise rejection. The error message was pretty far from actionable :D So there is apparently far more reasons for this error to occur than just OOM.

"react": "^17.0.1"
"enzyme": "^3.11.0"
"jest-enzyme": "^7.1.2"
"@wojtekmaj/enzyme-adapter-react-17": "^0.4.1"
With any node version, still happening

fixed by setting the maximum of the jest workers to 2

Any updates on this one ? I am having the same issue.

@FahmyChaabane if You know which file is causing the error, try wrapping the tests into try catch (in an async function) and, see what kind of errors you get and try to fix those. That might help.

I've added 2 flags to my react-scripts test and removed some Lazy loadings when it's on test stage

cross-env NODE_ENV=test react-scripts test --unhandled-rejections=warn --runInBand

And then in the code, im checking if it's in test stage env. Example:
  let ReactPlayer;
  if (global.__TEST__) ReactPlayer = require('react-player').default;
  else ReactPlayer = require('react-player/lazy').default;

My jest.setup.js
 global.__TEST__ = true;

Hope it helps someone.

Still having this issue. No workaround helped.

[SOLVED]
just use: jest.useFakeTimers()

For me this is not working properly! It just masks the problem because even if the assertion is wrong the test passes!

In my case, this bug occurred only when a specific combination of props was passed to my component. I went through code commenting out different parts related to these props and found that if I remove (or mock out) my Dropzone sub-component then the problem goes away. To everyone experiencing this issue, try commenting out parts of your component to find your culprit.

Maybe it helps someone, but for me the problem was, that I had process.env.NAME in the code and the same env variable was defined on my Mac, but not on the CI-Machine. This way all my tests were green, but on CI red.

Same issue node 16.0, also ERR_UNHANDLED_REJECTION

I get this error as well, I don't even know what jest-worker is, but I see it in package-lock.json. I don't know which module is implementing this, is there a way to just disable it completely?

For us this actually happened due to uncaught promise rejection. The error message was pretty far from actionable :D So there is apparently far more reasons for this error to occur than just OOM.

This was the case for us, too. I suspect if anyone else out there is seeing test suites fail to run with the "Call retries were exceeded" message after upgrading to Node 15 and above, you might want to hunt down and fix any unhanded promise rejections in your codebase.
I created a small reproducing repo in case it helps anyone on the Jest team: https://github.com/scitech/call-retries-repro
I think the issue here is, Jest will spawn some number of workers which will each attempt to fork a process. If a worker's process dies it forks another one, but after 3 tries it will stop running tests, and subsequent test suites will fail with the rather obscure error message "Call retries were exceeded". So it's not specifically related to unhandled promise rejections or memory issues (as in the OP) -- the failure could be due to a worker encountering 3 Node exceptions of any kind.
Given that unhandled promise rejections are pretty common in application code, I wonder if there isn't a more informative way to presenting this information to the Jest user so they can track down the issue. Forgive the unsolicited suggestions but here are some ideas:

Changing the error message text. "Call retries exceeded" is pretty opaque, maybe to something like "Jest worker process exited 3 times due to Node process exceptions, exceeding retry limit."
If a child process worker exceeds the retry limit, can it bail early, rather than run all the tests marking each as failed? It's harder to find the original source of the problem as is.
Can the exit handler of the ChildProcessWorker collect the Node process exception messages and report them back out after exceeding the retry limit?

For me it happened with lazy imports...just repurposed them into normal imports and it worked.

I think I had the same error:

Failed to construct transformer: { Error: Call retries were exceeded
at ChildProcessWorker.initialize (/Users/developer/Documents/dev/docomondo/app/node_modules/jest-worker/build/workers/ChildProcessWorker.js:193:21)
at ChildProcessWorker._onExit (/Users/developer/Documents/dev/docomondo/app/node_modules/jest-worker/build/workers/ChildProcessWorker.js:274:12)
at ChildProcess.emit (events.js:198:13)
at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12) type: 'WorkerError' }

I updated node from v10.19.0 to v14.17.0 and it works now

I have the same issue , but locally it works fine the tests passes however in CI it give me this error too !

Solved with: jest -w 1
https://github.com/zcorky/moment/issues/26

I faced the same error when I was using node version 16.3. Changing the version from 16.3 to 12.6.3 resolved this issue.

I think I had the same error:

Failed to construct transformer: { Error: Call retries were exceeded
at ChildProcessWorker.initialize (/Users/developer/Documents/dev/docomondo/app/node_modules/jest-worker/build/workers/ChildProcessWorker.js:193:21)
at ChildProcessWorker._onExit (/Users/developer/Documents/dev/docomondo/app/node_modules/jest-worker/build/workers/ChildProcessWorker.js:274:12)
at ChildProcess.emit (events.js:198:13)
at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12) type: 'WorkerError' }

I updated node from v10.19.0 to v14.17.0 and it works now

This worked for me

Meet the same issue when upgrade node from 12.13 to 16, any update on this?
"jest": "^25.5.4",
"react": "^16.14.0",
"node": "16"
Test suite failed to run

    Call retries were exceeded

      at ChildProcessWorker.initialize (node_modules/jest-worker/build/workers/ChildProcessWorker.js:191:21)
      at ChildProcess.emit (node:events:394:28)
      at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12)

@jiaoqiqi I'm also still seeing this issue. However, I've been able to mitigate this by pinning node to 16.8.
Hopefully there is a longer term fix soon.

I'm experiencing this issue on GitLab CI on a k8s cluster after I set the CPU limit of the runner pod to 5 cores (while the cluster has 40 in total).
I guess the Node.js told jest-runner that the system has 40 cores so jest-runner requested for according number of child processes, then the CPU limit caused the child process request to fail.

@jiaoqiqi I'm also still seeing this issue on node 16.9. However, I've been able to mitigate this by pinning node to 16.8.
Hopefully there is a longer term fix soon.

I'm having this issue on 16.8.0
I have a feeling that the node version is a red herring and the problem is getting fixed after upgrades/downgrades because something else changes as a side effect.

For me the issue came when i used spyon on a api.
initialy I was using
spyOn(dataService, 'getData').and.returnValue({
paydown: 0,
depAmount: null
});
Then it worked when I changed the code to callfake
spyOn(dataService, 'getData').and.callFake(() => Promise.resolve({
paydown: 0,
depAmount: null
}));

I am seeing a similar issue with node v16.10.0. In my case, however, I am running locally and --runInBand causes the test to throw:
node:internal/process/promises:246
          triggerUncaughtException(err, true /* fromPromise */);
          ^

[UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "Error: For security reasons, `window.crypto` is required to run `auth0-spa-js`.".] {
  code: 'ERR_UNHANDLED_REJECTION'
}

Reverting back to node 12.20.1 resolves the issue but it seems like more than just a node version problem.

I've run into this issue when updating a codebase from Node12 -> Node16 and in my digging I've found that in the bits that are now failing all seem to have the following in common when I run with a debugger attached.
[DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Which would indicate to me that now the behaviour it was relying on, unhandled promise rejections continue, now cause a termination in Node, which Jest is detecting, running the test an additional 3 times before declaring it as dead and marks it as a failed test suite.
What is interesting is that in Node12 those tests pass even when unhandled promise rejection is being fired as long as it's not actually impacting any of the bits that are being tested:
  it.only('calls navigate function to existing booking error page ', async () => {
    const response = responseBuilder('AS');
    await renderComponent('AS');
    waitFor(() => expect(props.navigate).toHaveBeenCalledWith('EXISTING_BOOKING_ERROR', response));
  });

Jest 27.2.3
Node 12.18.2 - All tests work as expected
Node 16.13.0 - Tests that contain an Unhandled promise rejection fail, even if it's not in the tests critical path

Having the same problem
jest: 26.6.3
node: 15.5.1
node:internal/process/promises:227
          triggerUncaughtException(err, true /* fromPromise */);

Call retries were exceeded

      at ChildProcessWorker.initialize (node_modules/jest-worker/build/workers/ChildProcessWorker.js:193:21)

Same issue here

jamesRaybould's description matches the problem I have as well. Worked in node 14.17.16, fails in 16.13.0.

In my case we're missing an await before wairFor from @testing-library/react
- waitFor(() => {

+ await waitFor(() => {
      expect(screen.getByTestId('my-button')).toBeInTheDocument();

If we run with node 16, it does not complain at all. Node 14 yells Call retries were exceeded without any implicit error message and it's very difficult to spot the bug.

Same Problem here:
 FAIL  __tests__/homepage.test.tsx
  ● Test suite failed to run

    Jest worker encountered 4 child process exceptions, exceeding retry limit

      at ChildProcessWorker.initialize (node_modules/jest-worker/build/workers/ChildProcessWorker.js:185:21)

Node version: v16.13.0
Does anyone got a fix?

From my understanding of the problem I think the best fix for this is probably to fix the problem at source, in my case it's a combination of us not mocking out dependencies properly and a couple of places where we don't actually handle the a promise rejection (at all). So fixing those will get us to a place where it all works as expected.
I'm not sure that there is a fix that can go in Jest other than to maybe better highlight where the unhandledPromiseRejection is being thrown.

I had the same problem with a VueJS app, with nodejs v16.13.0 and jest 25.5.4 so a bit older version of Jest.
node:internal/process/promises:246
          triggerUncaughtException(err, true /* fromPromise */);
          ^

and Call retries were exceeded
"Fixed" it with the following changed. I prefer the former syntax than the latter.
    components: {
      VueApexCharts: () => import('vue-apexcharts')
    }

to
    import VueApexCharts from 'vue-apexcharts'
...
    components: {
      VueApexCharts
    }

In my case we're missing an await before wairFor from @testing-library/react
- waitFor(() => {

+ await waitFor(() => {
      expect(screen.getByTestId('my-button')).toBeInTheDocument();

If we run with node 16, it does not complain at all. Node 14 yells Call retries were exceeded without any implicit error message and it's very difficult to spot the bug.

Do not know why but this worked like charm.

For those having issues running on node 16, I found this link helpful,
https://stackoverflow.com/questions/68368577/react-tests-unhandledpromiserejection
Essentially you need to ensure that any custom async functions being called from your tests need to implement a try/catch.

We ran into this issue when upgrading from Node 14 to Node 16.  It appears that Node 15 introduced a breaking change to promise rejection handling, as @jamesRaybould indicated earlier.  I found https://developer.ibm.com/blogs/nodejs-15-release-blog/ to be a helpful writeup of the change.
We saw the errors disappear after passing the --unhandled-rejections=warn flag to node when running tests, which likely confirms this diagnosis.
Passing that flag may work as a short term workaround.

My problem was that a testing-library test was longer than the 5 seconds timeout of a test. There are multiples waitFor in it as it represent an E2E test.
In order to fix it, I simply needed to up the timeout of the test to an higher value:
it('should do a mega long process`, () => {
  renderComponent();

  // all the process

  expect(true).toBeTruthy()
}, 60 * 1000) // one minute to be sure it does not timeout again

Hope it helps some of you!

My problem was that a testing-library test was longer than the 5 seconds timeout of a test. There are multiples waitFor in it as it represent an E2E test.

@arivestNexapp Another option is you can configure it globally, so you don't have to manually increase timeout for each test.
import { configure } from '@testing-library/dom';

configure({
  asyncUtilTimeout: 2500,
});

Reference: https://testing-library.com/docs/dom-testing-library/api-configuration#asyncutiltimeout

In my case we're missing an await before wairFor from @testing-library/react
- waitFor(() => {

+ await waitFor(() => {
      expect(screen.getByTestId('my-button')).toBeInTheDocument();

If we run with node 16, it does not complain at all. Node 14 yells Call retries were exceeded without any implicit error message and it's very difficult to spot the bug.

Do not know why but this worked like charm.

In my case, I was not awaiting a findByText. Switching to getByText fixed the issue for me.

Hi, for me this error was related to M1 processor. Run tests on a terminal with rosetta enabled and got it working.

It makes sense that a try/catch block solves the issue because it's a way of catching rejections. Essentially all Promises in tests should catch or handle reject.

For those having issues running on node 16, I found this link helpful, https://stackoverflow.com/questions/68368577/react-tests-unhandledpromiserejection
Essentially you need to ensure that any custom async functions being called from your tests need to implement a try/catch.

It makes sense that a try/catch block solves the issue because it's a way of catching rejections. Essentially all Promises in tests should catch or handle reject.

mostly, If you met such type of problem you need to take an attention to asynchrous test, perhaps problem related with this

For me, my problem was with not mocking a dependency exhaustively when some components in the dependency were being used in the component I was testing. For instance
import { A, B } from "dependency";

MyComponent => ({condition}) => {
  if (condition)
    return <A />
  else
    return <B />
}

in my test
jest.mock("dependency", () => ({
   A: (props) => Something
}))

it("shows something", () => {
   <MyComponent condition={false} />
})

This would throw this error until I fully mocked the dependency like this (to ensure B is not undefined in the mock):
jest.mock("dependency", () => ({
   ...jest.requireActual("dependency"),
   A: (props) => Something
}))

While my component also had some async work, that was never the problem.
Try to check if you have some things that are undefined possibly due to mocking.

全体起立！
在 setupTests.js 或者出现问题的单元测试文件添加下面的代码，完美解决！！！
process.on('unhandledRejection', (reason) => {});


Send UDP ASSOCIATE command, DST.ADDR and DST.PORT should use zeros.

Describe actual behavior
When request the udp association command, the dst.addr and dst.port is set the destination address and the destination port.
What is your expected behavior
If the client is not in possesion of the information at the time of the UDP ASSOCIATE, the client MUST use a port number and address of all zeros. Come from the describe of UDP ASSOCIATE in rfc-1928
Specifications like the version of the project, operating system, or hardware
Steps to reproduce the problem
package main

import (
	"fmt"

	"github.com/txthinking/socks5"
)

func main() {
	server := "xxx"
	username := "xxx"
	password := "xxx"
	tcpTimeout := 10
	udpTimeout := 60

	client, err := socks5.NewClient(server, username, password, tcpTimeout, udpTimeout)
	if err != nil {
		return
	}

	network := "udp"
	addr := "xxx"
	conn, _ := client.Dial(network, addr)
	_, err = conn.Write([]byte("hello"))
	if err != nil {
		return
	}
	udpResp := make([]byte, 1024)

	_, err = conn.Read(udpResp)
	if err != nil {
		fmt.Println("Error receiving UDP data:", err)
		return
	}
	fmt.Println(udpResp)
}

Section 7:
The UDP relay server *MUST* acquire from the SOCKS server the expected    IP address of the client that will send datagrams to the BND.PORT    given in the reply to UDP ASSOCIATE.  It *MUST* drop any datagrams    arriving from any source IP address other than the one recorded for    the particular association. (C)
Section 6:
The server *MAY*    use this information to limit access to the association(B)
Section 6:
If the client *is not* in possesion of the information at the time of the UDP ASSOCIATE, the client MUST use a port number and address of all zeros. (A)
Actually, ABC are a bit contradictory. Yes, we can ignore B because it is MAY, but can't ignore C with MUST.
Back to discuss A:

E: If there is NAT in the network between the client and the server, then it is is not

in this case, how about C MUST? like this way but this is not mentioned in the standard RFC?

F: If there is no NAT in the network between the client and the server, then it is is

prepare the address, C will not be controversial.

We only need to add a variable to the client for caller to decide whether it is under NAT, and then whether to prepare the address that expects to use to send UDP. such as:
type Client struct{
    NoNAT bool
}

if (!NoNAT) then E;
if (NoNAT) then F;


Swarm mode: service definition lacks custom DNS settings

When creating a container one can specify custom DNS settings: https://godoc.org/github.com/docker/engine-api/types/container#HostConfig - specifically DNS, DNSOptions and DNSSearch
There is no equivalent in the https://godoc.org/github.com/docker/engine-api/types/swarm#ServiceSpec

Added a PR #27567 to have DNS related configs in service specification.


Add command to run project locally

 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.

@indusankar89 could you please merge? :-)

@maxstreifeneder  Thanks for the fix. :)


Permission for non-admins

Hi,
a user with "Moderator" permisssion on our wagtail site is reporting they can't see the "News" button in the wagtail admin menu. How could I grant permission to add and edit news articles to "Moderators" or "Editors"?
Thanks a lot in advance!
Jojo

There should be add, edit delete permission on the group settings, I think from memory it's called something like "News items". Try giving permissions to those groups


Fix link in About section of this project

Move www.phlex.fun/rails/ to www.phlex.fun

Done. thanks!


Update page columns to accept date format as an option

Closing as @jamestalton is working on a solution to have date format picked up and applied globally from the user settings dialog.


WIP: reviewing and fixing some pending issues related to the name table rules

As discussed in issue #1974 and based on feedback from @mjlagattuta at https://github.com/google/fonts/issues/1618#issuecomment-425992197

There's more to do here. But there's not reason to keep this pending here. I will soon open a new pull request to deal with the rest.


⚠ Bofrost.be has degraded performance

In 66f8b48, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2090 ms

Resolved: Bofrost.be performance has improved in d26e86a.


Fix Typo

Several typo/link fix under docs and apis.

Codecov Report

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

@@          Coverage Diff           @@
##           master   #1384   +/-   ##
======================================
  Coverage    3.74%   3.74%
======================================
  Files          35      35
  Lines       18637   18637
======================================
  Hits          698     698
  Misses      17812   17812
  Partials      127     127

Impacted Files
Coverage Δ

apis/voyager/v1beta1/annotations.go
29.79% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


dm client adds in the namespace twice on requests to the remote.

Does not occur everytime, so it may be quite hard to reproduce.
priya@Priyas-MBP:~/dotmesh/ops/backup$ dm dot show brtknr/moby_counter
Dot brtknr/moby_counter:
Master branch ID: e907d5f3-548d-4c92-6bdc-a03a6fae81e8
Commits: 0
Dot size: - (all clean)
Branches:
Response '{"jsonrpc":"2.0","error":{"code":-32000,"message":"No such filesystem named 'brtknr/brtknr/moby_counter'","data":null},"id":2775422040480279449}
' yields error No such filesystem named 'brtknr/brtknr/moby_counter'

For some context, I was running the backup script which uses the dm client just before trying to do dm dot show brtknr/moby_counter above.


Repo sync for protected CLA branch

The pull request is created from master637533470827659264 to master to fix git push error for protected CLA branch

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


[FEATURE]: Assistant logo is not static

Describe the feature
While scrolling the website your assistant logo in not being static it moves up with the scrolling of the website. So it should be static during scrolling of the website for make the better user experience.
Add ScreenShots

Record

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

@arghadipmanna101  Please assign this issue to me i want to work on this issue. #GSSoc'24

@arghadipmanna101 Please look and merge the PR.

i want to work on this issue under gssoc'24 Contributor; please assign me this issue. I will asap after being assigned.


"use of @import when modules are disabled error"

I've just updated pods for my project and now i'm having "use of @import when modules are disabled error" because of FastttCamera.h:
@import UIKit;

BUT, modules are switched ON for my project and pods:

Any idea how to fix this?

Aaah. It's way to early for a sunday ... I was importing FastttCamera from an Objective-C++ controller, which caused the issue. Moving everything to a new controller worked like a charm!


disable safe_browsing throttles

fix https://github.com/brave/browser-laptop/issues/11716

++ pls do new builds with this


Unable to copy / paste cell data from query Results table

Azure Data Studio Version: v1.32.0
OS Version: Win10

Steps to Reproduce:

Run a query
Try to copy a value from a single cell in the result set (select cell and hit CTRL+C)
Try to paste value into query pane (or anywhere) using CTRL+V
Result is that value was never copied to the clipboard

Does this issue occur when all extensions are disabled?: Yes/No
Yes (I disabled all extensions)

If you right click and select the "Copy" action does that also not work?

If you right click and select the "Copy" action does that also not work?

It does not work; I don't even get a context menu when I right click.

Do you get a context menu elsewhere in the app - like in the main editor pane or on the tree views to the side?
Could you also try downloading the insiders version of ADS and seeing if you get the same thing there?

I do get a context menu in both the query pane and the connections pane.
I will try the insiders version next...

Same issue in the freshly installed Insiders build: no context menu and CTRL+C doesn't copy cell value to my clipboard.

@alanrenmsft Any ideas here? I've never seen any reports of this kind of issue happening and am not sure what could be causing some events not to be handled correctly...

Console.log from dev tools console tab:
console.log

Zipped application log folder:
20210820T125621.zip

Oh wow, thank you for finding that out @JordanMarr! Sorry about the issues you had, glad you were able to resolve it.


summer 2015 update on site

I know you don't want to put a pdf on the front page, but it'd be nice to link to the Summer 2015 update somewhere. We can talk about that later if you like, to see how best to put it on there, and also sending the pdf of the file, too.

Link to file https://www.dropbox.com/s/o17tioicgpkoihq/OpenAQUpdate_Summer2015.pdf?dl=0


Character in cell boundary not read

If a character in a text in a table cell is close to the boundary then it is nor read by Cell.getText(). Kindly let me know if any way we can read entire text in a cell with tabula java api.
In attached pic text 'No SS Number' in the cell is read as 'o SS Number'.

Hi @paponcc, the problem is that the characters overlap the ruling line, which is confusing Tabula. You could try "Stream" mode, but that might cause other problems for you.


protect load balancer from variable cpu clock

Original author: Jim Phillips (@jcphill)
Original issue: https://charm.cs.illinois.edu/redmine/issues/641

When running netlrts-smp on Linux with two processes on a single node for GPU-accelerated NAMD, the OS sees some cores (generally those associated with one process or the other) as less busy and slows the cpu clock, which exaggerates the load imbalance and results in even worse overload of the other process following load balancing.  Setting the cpu frequency scaling governors to "performance" makes the issue go away, but we need to understand why the OS isn't reading the CPUs as fully loaded or find a way for the load balancer to cope with time-varying cpu speeds.

Original author: Jim Phillips (@jcphill)
Original date: 2014-12-31 17:05:49

The OS was reading the CPU as not loaded due to frequent calls to CmiMachineProgressImpl() in NAMD entry methods.  These calls were taking a lot of time waiting on something in the machine layer.  When the CmiMachineProgressImpl() calls are removed the OS keeps the cores at full or near-full speed.  It is possible that it is a bug for user code to call CmiMachineProgressImpl() in non-smp builds, or at least is shouldn't serve any purpose when there is a communication thread. These calls were originally added to ensure that high-priority incoming messages were received promptly.

Original author: Jim Phillips (@jcphill)
Original date: 2015-01-16 02:50:37

That should be "It is possible that it is a bug for user code to call CmiMachineProgressImpl() in smp builds".  In any case, I assume this is related to the issue of the comm thread holding the comm lock while sending and receiving messages rather than only when manipulating queues.

Original author: Harshitha Menon
Original date: 2015-08-17 19:14:40

Is this bug related to https://charm.cs.illinois.edu/redmine/issues/642? If so, does that fix eliminate this problem?

Original author: Jim Phillips (@jcphill)
Original date: 2015-08-19 01:42:56

I assume that fixes the problem.  I also eliminated the CmiMachineProgressImpl() calls in NAMD for smp builds.

Original date: 2017-02-01 17:42:45

It looks like this was fixed a while ago in the following two commits:
~~https://charm.cs.illinois.edu/gerrit/#/c/577/~~ https://github.com/UIUC-PPL/charm/commit/64fb65c3ea86e714f1a3549a13dad7662ecee274
~~https://charm.cs.illinois.edu/gerrit/#/c/638/~~ https://github.com/UIUC-PPL/charm/commit/81f00d788030abd2a5df0e6d95057df41f658ed3
Anything left to do on this issue?

Original date: 2018-03-28 01:21:40

Please close this issue if it is done


Changed python dependency to ^3.7.1

This avoids the following dependency conflict when installing it with poetry in a newly created project.

LGTM! ☺


Can I use Python 3?

Since the model is in container, I'm assuming that I should be able to use Python 3.
But if I can't, could you please explain why? Thank you.

At this moment, we don't support python 3 with our official image, but we are planning to. There's a lot on our plate at the moment, but this is one of the things we know is important to add.
In the meantime, if you absolutely need to use python 3, you can build your own image by following the instructions in this repository, with small modifications to the dockerfiles.

Thank you! I've tried following the instruction for building image, but I'm stuck since I'm new to Docker. Please see issue #43


WhatsApp Web Images

If I try to add an image from whatsapp web download. It comes to an error in the pdf. Is there any solution?

If you're downloading the image from the whatsapp url itself instead of a local file or a file from the same origin, the canvas could be tainted as a result. Allowing anonymous cors could solve this issue


caravan mpw9 PnR

First PnR iteration of caravan using the new hierarchy (flattened core + padframe)
Standalone physical verification, STA, and SDF simulations are yet to be done

Multiple iterations for PnR have been done and I think the current physical views for caravan are good now.
The following issues have been addressed:
https://github.com/efabless/caravel/issues/417
https://github.com/efabless/caravel/issues/120
https://github.com/efabless/caravel/issues/415
https://github.com/efabless/caravel/issues/416
https://github.com/efabless/caravel/issues/148
https://github.com/efabless/caravel/issues/185
https://github.com/efabless/caravel/issues/351
https://github.com/efabless/caravel/issues/369
https://github.com/efabless/caravel/issues/412
@passant5 @marwaneltoukhy @M0stafaRady please add your review.


Locks up to homebridge with these errors

[6/6/2019, 9:55:18 PM] [Denon to Blu-ray] TypeError: Cannot read property 'cmd' of undefined
at doRequest.then.resp (/homebridge/node_modules/homebridge-denon-quickselect/index.js:59:27)
at process._tickCallback (internal/process/next_tick.js:68:7)
[6/6/2019, 9:55:18 PM] [Denon to TV-Music] TypeError: Cannot read property 'cmd' of undefined
at doRequest.then.resp (/homebridge/node_modules/homebridge-denon-quickselect/index.js:59:27)
at process._tickCallback (internal/process/next_tick.js:68:7)
[6/6/2019, 9:55:18 PM] [Denon to Game] TypeError: Cannot read property 'cmd' of undefined
at doRequest.then.resp (/homebridge/node_modules/homebridge-denon-quickselect/index.js:59:27)
at process._tickCallback (internal/process/next_tick.js:68:7)
[6/6/2019, 9:55:18 PM] [Denon to TV-Movie] TypeError: Cannot read property 'cmd' of undefined
at doRequest.then.resp (/homebridge/node_modules/homebridge-denon-quickselect/index.js:59:27)
at process._tickCallback (internal/process/next_tick.js:68:7)

Unsolved. Closing to keep things clean.


Update The Plugin

Hi,
can you remove the campaign option, since this is no longer part of the Amazon Affiliate Service.
Aswell could you offer a Setting to change the Affiliate Tag in the YOURLS Menu, would highly appreciate that.

Hey @mrlufus – these changes sound very reasonable, but I'm not actively maintaining this anymore. Feel free to open a PR for this, would happily review it!


Allow longest prefix match

(This is used to request new product features, please visit https://discuss.istio.io for questions on using Istio)
Describe the feature request
Currently First matched prefix in virtual services is used for a given host, It will be good if we can have a feature that allows longest path match.
Ex: say for host foo.bar,  we have two paths /anything and /anything/football
any request like /anything/football* should match the rule for path /anything/football
and request like /anything*, which doesn't match /anything/football* should match the rule /anything
This should happen irrespective of the order in which the rules were created.
Describe alternatives you've considered
Affected product area (please put an X in all that apply)
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Additional context

To add some more context -- this is mostly useful for VirtualServices that are merged. If they aren't merged you can just do it yourself easily

I would recommend using https://gateway-api.sigs.k8s.io/api-types/httproute/ where this is already how it works.


Abizern/remove roboto

This closes #192

Thanks @Abizern! I'll check this out later this afternoon

Looks good, thanks @Abizern


NICE-170 latest from nice & homepage

https://nicedigital.atlassian.net/browse/NICE-170
Note: this PR contains a lot of semi-complete boilerplate for other homepage components

All looking good. Just a few comments, nothing major. Mainly me asking questions, not raising issues.
Noticed a few snapshots around NewsGrid and HomepageLatestNews that need updating, but can probably leave this for a separate PR?

Ta - snapshots updated


Update key events

The key controls didn't work for me, so I moved them from canvas to window instead.
Thanks for a very nice description of this interesting Voxel Space technique 👍

Looks like I have done it already today. Thanks for the patch anyway.


bash: default to 5

Motivation for this change
This is just a test to see if defaulting to bash 5 and removing old bash 4.4 works properly.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg eval

I've checked the error on my local, here is what I found out
local input=/nix/store/c9w69kl4caarcs2j84hck0icrdj9jqr6-fix-darwin-dylib-names.sh
++ local output=/nix/store/wiqpq8fwh190c9msc8iq68ai6cszca88-hook/nix-support/setup-hook
++ shift 2
++ '[' '!' -f /nix/store/c9w69kl4caarcs2j84hck0icrdj9jqr6-fix-darwin-dylib-names.sh ']'
++ local content
++ consumeEntire content
++ IFS=
++ read -r -N 0 content
++ echo 'consumeEntire(): ERROR: Input null bytes, won'\''t process'
consumeEntire(): ERROR: Input null bytes, won't process
++ return 1

the file
❯ cat /nix/store/c9w69kl4caarcs2j84hck0icrdj9jqr6-fix-darwin-dylib-names.sh
# On macOS, binaries refer to dynamic library dependencies using
# either relative paths (e.g. "libicudata.dylib", searched relative to
# $DYLD_LIBRARY_PATH) or absolute paths
# (e.g. "/nix/store/.../lib/libicudata.dylib").  In Nix, the latter is
# preferred since it allows programs to just work.  When linking
# against a library (e.g. "-licudata"), the linker uses the install
# name embedded in the dylib (which can be shown using "otool -D").
# Most packages create dylibs with absolute install names, but some do
# not.  This setup hook fixes dylibs by setting their install names to
# their absolute path (using "install_name_tool -id").  It also
# rewrites references in other dylibs to absolute paths.

fixupOutputHooks+=('fixDarwinDylibNamesIn $prefix')

fixDarwinDylibNames() {
    local flags=()
    local old_id

    for fn in "$@"; do
        flags+=(-change "$(basename "$fn")" "$fn")
    done

    for fn in "$@"; do
        if [ -L "$fn" ]; then continue; fi
        echo "$fn: fixing dylib"
        int_out=$(@targetPrefix@install_name_tool -id "$fn" "${flags[@]}" "$fn" 2>&1)
        result=$?
        if [ "$result" -ne 0 ] &&
            ! grep "shared library stub file and can't be changed" <<< "$out"
        then
            echo "$int_out" >&2
            exit "$result"
        fi
    done
}

fixDarwinDylibNamesIn() {
    local dir="$1"
    fixDarwinDylibNames $(find "$dir" -name "*.dylib")
}

I've found 2 previous attempt and one person suggested a solution
https://github.com/NixOS/nixpkgs/pull/108101
second attempt is older and just like mine so far
https://github.com/NixOS/nixpkgs/pull/53687
I'm trying the fix documented in the first link. In bash 5 the behavior of read -N 0 has changed and that was not documented anywhere. I'm testing this on local, I will push the commit after.

The next two errors are test errors while building nix.
running test tests/user-envs.sh... [FAIL]
    + '[' -z '' ']'
    + clearStore
    + echo 'clearing store...'
    clearing store...
    + chmod -R +w /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/store
    + rm -rf /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/store
    + mkdir /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/store
    + rm -rf /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/var/nix
    + mkdir /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/var/nix
    + nix-store --init
    + clearProfiles
    + profiles=/private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/var/nix/profiles
    + rm -rf /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/var/nix/profiles
    + clearProfiles
    + profiles=/private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/var/nix/profiles
    + rm -rf /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/var/nix/profiles
    ++ nix-env -p /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/var/nix/profiles/test -q '*'
    ++ wc -l
    + test 0 -eq 0
    + mkdir -p /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/test-home
    + nix-env --switch-profile /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/var/nix/profiles/test
    ++ nix-env -f ./user-envs.nix -qa '*'
    ++ wc -l
    + test 6 -eq 6
    ++ nix-env -f ./user-envs.nix -qa --out-path --no-name '*'
    ++ grep foo-1.0
    + outPath10=/private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/store/4rchg0azqmx526arwhv8a7b3817q1c3x-foo-1.0
    ++ nix-env -f ./user-envs.nix -qa --drv-path --no-name '*'
    ++ grep foo-1.0
    + drvPath10=/private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/store/sq8ikm091c6jldai40sdp4ax420mab5f-foo-1.0.drv
    + '[' -n /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/store/4rchg0azqmx526arwhv8a7b3817q1c3x-foo-1.0 -a -n /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/store/sq8ikm091c6jldai40sdp4ax420mab5f-foo-1.0.drv ']'
    + nix-env -f ./user-envs.nix -qa '*' --description
    + grep -q silly
    + rm -rf /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/test-home/.nix-defexpr
    ++ pwd
    + ln -s /private/tmp/nix-build-nix-2.3.14.drv-0/nix-2.3.14/tests/user-envs.nix /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/test-home/.nix-defexpr
    + nix-env -qa '*' --description
    + grep -q silly
    + nix-env -qa '*' --system
    + grep -q x86_64-darwin
    + nix-env -i foo-1.0
    installing 'foo-1.0'
    these derivations will be built:
      /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/store/sq8ikm091c6jldai40sdp4ax420mab5f-foo-1.0.drv
    building '/private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/store/sq8ikm091c6jldai40sdp4ax420mab5f-foo-1.0.drv'...
    error: unexpected EOF reading a line

running test tests/fetchurl.sh... [FAIL]
    + clearStore
    + echo 'clearing store...'
    clearing store...
    + chmod -R +w /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/store
    + rm -rf /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/store
    + mkdir /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/store
    + rm -rf /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/var/nix
    + mkdir /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/var/nix
    + nix-store --init
    + clearProfiles
    + profiles=/private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/var/nix/profiles
    + rm -rf /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/var/nix/profiles
    ++ nix-hash --flat --type sha256 ./fetchurl.sh
    + hash=9b1d81c5333e8c25296214cbf642e479131b8437f69d6e50cde80029a9e55e84
    +++ pwd
    ++ nix-build '<nix/fetchurl.nix>' --argstr url file:///private/tmp/nix-build-nix-2.3.14.drv-0/nix-2.3.14/tests/fetchurl.sh --argstr sha256 9b1d81c5333e8c25296214cbf642e479131b8437f69d6e50cde80029a9e55e84 --no-out-link --hashed-mirrors ''
    these derivations will be built:
      /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/store/jcmp6jplgqc3vdwj1pp3nxs5fj7gvqdk-fetchurl.sh.drv
    building '/private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/store/jcmp6jplgqc3vdwj1pp3nxs5fj7gvqdk-fetchurl.sh.drv'...
    + outPath=/private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/store/zr0g75mi67dazv4hby9lgj8jk14avh2v-fetchurl.sh
    + cmp /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/store/zr0g75mi67dazv4hby9lgj8jk14avh2v-fetchurl.sh fetchurl.sh
    + clearStore
    + echo 'clearing store...'
    clearing store...
    + chmod -R +w /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/store
    + rm -rf /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/store
    + mkdir /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/store
    + rm -rf /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/var/nix
    + mkdir /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/var/nix
    + nix-store --init
    + clearProfiles
    + profiles=/private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/var/nix/profiles
    + rm -rf /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/var/nix/profiles
    ++ nix hash-file --type sha512 --base64 ./fetchurl.sh
    + hash=aKjXWoXYIDfLkn4MV1P6FR/rkiXOqps6A4J3cWCYc1G3mgtTbIK5/YY7wXuExg/ltSf8JHlD25wCyovEU6ZI9Q==
    +++ pwd
    ++ nix-build '<nix/fetchurl.nix>' --argstr url file:///private/tmp/nix-build-nix-2.3.14.drv-0/nix-2.3.14/tests/fetchurl.sh --argstr sha512 aKjXWoXYIDfLkn4MV1P6FR/rkiXOqps6A4J3cWCYc1G3mgtTbIK5/YY7wXuExg/ltSf8JHlD25wCyovEU6ZI9Q== --no-out-link --hashed-mirrors ''
    these derivations will be built:
      /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/store/v4wknf7v874g819pr9vc20rw5inywb31-fetchurl.sh.drv
    building '/private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/store/v4wknf7v874g819pr9vc20rw5inywb31-fetchurl.sh.drv'...
    + outPath=/private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/store/qjwwfb7nq62w30pzmiijnl0289jfhnf7-fetchurl.sh
    + cmp /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/store/qjwwfb7nq62w30pzmiijnl0289jfhnf7-fetchurl.sh fetchurl.sh
    + clearStore
    + echo 'clearing store...'
    clearing store...
    + chmod -R +w /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/store
    + rm -rf /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/store
    + mkdir /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/store
    + rm -rf /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/var/nix
    + mkdir /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/var/nix
    + nix-store --init
    + clearProfiles
    + profiles=/private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/var/nix/profiles
    + rm -rf /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/var/nix/profiles
    ++ nix hash-file ./fetchurl.sh
    + hash=sha256-mx2BxTM+jCUpYhTL9kLkeRMbhDf2nW5QzegAKanlXoQ=
    + [[ sha256-mx2BxTM+jCUpYhTL9kLkeRMbhDf2nW5QzegAKanlXoQ= =~ ^sha256- ]]
    +++ pwd
    ++ nix-build '<nix/fetchurl.nix>' --argstr url file:///private/tmp/nix-build-nix-2.3.14.drv-0/nix-2.3.14/tests/fetchurl.sh --argstr hash sha256-mx2BxTM+jCUpYhTL9kLkeRMbhDf2nW5QzegAKanlXoQ= --no-out-link --hashed-mirrors ''
    these derivations will be built:
      /private/tmp/nix-build-nix-2.3.14.drv-0/nix-test/store/iwjcbsicdy9zbzr3mli6109c1lzf5zsv-fetchurl.sh.drv
    error: unexpected EOF reading a line
    + outPath=

it only took 19h on my machine to build.

@vcunat when you have a moment, could we try a hydra rebuild, I would like to make sure this does not break stuff.
I understand you are busy, no worries if this takes time.

Recreated the PR leaving bash_4 around
https://github.com/NixOS/nixpkgs/pull/133495
Sorry about messing up the branch and notifying half of the world.


Unable to save while editing a page on phone

If you edit or create a page and interact with the "textare" where you create the content for the page, the upper menu to save, preview, delete etc will disappear. With that, you are unable to save the page.
It isn't happening instantly. If you write a bit it will dissapear. Sometimes it stays but most of the time it won't.
Workaround: Press on any link which which will redirect you to an other page within the same tab. Press no and the upper menu will appear again.
EDIT:
The menu will vanish if you copy/paste something.

It seems it's is browser specific.
Most of the time a Chromium browser does have the bug but some don't. Firefox is weird in this regard.
I guess it has something to do with the webkit or the way how the menu is displayed on phones. Probably the media-screen has something to do with it.

Can confirm on multiple android phones and browsers. Editing pages via the phone is unreliable


set_sql_header and config.sql_header don't do anything.

When attempting to add a SQL header, nothing is generated. (for reference: https://docs.getdbt.com/reference/resource-configs/sql_header )
{{ config(materialized='table') }}

{% call set_sql_header(config) %}
declare @temp float = 1.345;
{%- endcall %}

select * from MyTable where MyColumn = @temp

this also doesn't work:
{{
    config(
        materialized='table',
        sql_header="""
declare @temp float = 1.345;
""")
}}

select * from MyTable where MyColumn = @temp

The compiled SQL looks like:
select * from MyTable where MyColumn = @temp

Related dbt create statements.
https://github.com/dbt-labs/dbt-adapters/blob/706b7beaaa231da415d3dfbcdc5fb5b4d60a63c2/dbt/include/global_project/macros/relations/view/create.sql#L16
https://github.com/dbt-labs/dbt-adapters/blob/706b7beaaa231da415d3dfbcdc5fb5b4d60a63c2/dbt/include/global_project/macros/relations/table/create.sql#L22
I don't have time today, but i'll take a look next week at it.

So i'm not sure exactly what the way forward will be here.
How this was implemented is a bit of a block here with respect to table creation.
Basically its:

create table is called with some sql logic
create a temporary view to hold your model logic
insert into a table from the temporary view
drop the temporary view

The issue is that the model might have a declare and a argument to that variable @myvar, but SQL Server does not like it when its passed along to the create view statement.
Essentially it expects that the view creation doesn't have any declares and it's the first statement, which is not the case.
If I properly understand the reasoning here it is because dbt is a collection of .sql files, it proxies them into views to allow those to be inserted into a table, primarily because nested CTEs are not supported which would be the case any time someone creates a .sql file with a WITH ... AS statement .
As an example the file xyz.sql passes through this structure.
-- xyz.sql
{{
    config(
        materialized='table',
        sql_header="declare @myvar INT = 2;"
    )
}}
SELECT @myvar FROM {{ source('my', 'source')

into
-- this is where the @var will break

DECLARE @myvar INT = 2;
CREATE VIEW dbo.xyz_temporary AS
SELECT @myvar FROM my.source

into
DECLARE @myvar INT = 2;
SELECT * INTO dbo.xyz FROM dbo.xyz_temporary

then finally
DROP VIEW IF EXISTS dbo.xyz_temporary

You cannot ignore the @myvar either in this case, as the create view will break too.
Its a bit of a catch in that the way a table is created from a .sql file means you need to create a temporary view to prevent it failing on CTEs, but that in turn breaks the ability to have a sql_header since it breaks the create view logic.
There is an underlying problem here around the create logic being proxied through a view. So if that could be solved to allow the creation of tables, without needing a view, then this in turn would probably work for tables. I cannot see it working properly for views in any case though.

Adding one more thought; i'm not sure you could even change the create table logic to fix this.
The behaviour of writing sql files that are compiled into your table makes it agnostic about whether its a view or a table, which means, at least on sql server, something that is written as...
-- my_cte_model.sql
WITH my_cte AS (
   SELECT @myvar as var_col
)
SELECT * FROM my_cte

still needs to pass through some sort of a create table type statement, be it SELECT * INTO or a CREATE TABLE then INSERT INTO. Problem again hinging on the sql statement is written to be closed as SELECT * FROM my_cte which doesn't really pass cleanly into how dbt processes it.
DECLARE @myvar INT = 1;

CREATE TABLE my_cte_model (
   var_col INT -- this is also needing to be defined somehow when going down the create table road.
)

INSERT INTO my_cte_model (var_col)
SELECT var_col FROM (
    WITH my_cte AS (
       SELECT @myvar as var_col
    )
    SELECT * FROM my_cte
)

Otherwise its
DECLARE @myvar INT = 1;
SELECT * INTO my_cte_model FROM (
    WITH my_cte AS (
       SELECT @myvar as var_col
    )
    SELECT * FROM my_cte
) cte_proxy

which breaks due to nested CTEs.

One work around would be to store that as its own model and join to that using a ref potentially. Certainly not as clean, but one potential option


chore(deps): update common-dev-assets digest to 8d8a949

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
60681d1 -> 8d8a949

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 6.4.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Fix gridMinimumScale behaviour

Issue: When isGridVisible={false}, the grid reappeared unexpectedly during canvas interactions like panning or zooming.
Fix: Ensured that the grid remains hidden when isGridVisible={false}, regardless of canvas interactions such as panning or zooming. That was caused when GridMinimumScale was introduced. Fixed that behaviour as well.

@hunkim98 have a look please

Will approve! Thanks!


Added the ability to send a body of an arbitrary mime type with the response of an Upgrade request

Description
The HTTP/2 upgrade factory needs to send binary data in the response to an upgrade request. The existing API doesn't support that. The new API adds the ability to the ConnectionUpgradeFactory.upgrade function to return an optional Data (the body's contents) and an optional String (the body's mime type). A protocol extension was written to avoid breaking existing APIs.
Motivation and Context
Needed for HTTP/2 support
How Has This Been Tested?
Ran unit tests on macOS and Linux.
Checklist:

[ ] I have submitted a CLA form
[ ] If applicable, I have updated the documentation accordingly.
[ ] If applicable, I have added tests to cover my changes.

Codecov Report

Merging #190 into master will decrease coverage by 1.21%.
The diff coverage is 92.3%.

@@            Coverage Diff             @@
##           master     #190      +/-   ##
==========================================
- Coverage   76.16%   74.95%   -1.22%
==========================================
  Files          29       30       +1
  Lines        4024     4032       +8
==========================================
- Hits         3065     3022      -43
- Misses        959     1010      +51

Flag
Coverage Δ

#CHTTPParser
62.66% <ø> (ø)
:arrow_up:

#KituraNet
74.95% <92.3%> (-1.22%)
:arrow_down:

Impacted Files
Coverage Δ

Sources/KituraNet/ConnectionUpgradeFactory.swift
100% <100%> (ø)

Sources/KituraNet/ConnectionUpgrader.swift
75.43% <85.71%> (-0.93%)
:arrow_down:

Sources/KituraNet/IncomingSocketHandler.swift
53.08% <0%> (-23.7%)
:arrow_down:

Continue to review full report at Codecov.

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


add FURU to otr

New Listing: FURU

Identity Name: FURU
Authbase: d9ab24ed15a7846cc3d9e004aa5cb976860f13dac1ead05784ee4f4622af96ea

Evidence Linking Authbase to Identity

Select one:

[x] Direct evidence: a chain-resolved registry at the authhead provides substantially equivalent metadata for this authbase. The Authhead TXID is provided below:
[ ] Indirect evidence: the identity is burned or provably locked within a covenant, so the authbase can safely be linked using indirect evidence. Details and two or more corroborating, third party-archived URLs of reputable sources vouching for this association are provided below:

Authhead TXID: 7c54400ebe360902acaaf7696fe0c0eee4f6dc5843425fbf335154bbf2445f5a
Evidence Linking Identity to Authbase

Archived URL(s):

Evidence Linking Authbase to Categories

Select one:

[x] Token category is equal to the authbase for all Identity Snapshots.
[ ] Evidence is provided for differing category values below:

Substantiation of Other Claims

Select one:

[x] The submission (esp. the description) includes no claims requiring substantiation.
[ ] The claims in this submission can be corroborated with the following evidence:

The Furu token description reads:

FURU tokens are the official free-play tokens for the BCH Guru predictions platform.

The FURU tokenId is displayed on nfts.bch.guru in the FAQ sections under 'security'.
Checklist

[x] I have reviewed the OpenTokenRegistry inclusion criteria, and this listing can be included in the registry.
[x] The listing completes all required fields:

name

[x] Objective, authoritative, and neutral tone
[x] No longer than 20 characters; exceptions may be allowed for existing legal names (please provide evidence above including the jurisdiction(s) in which the legal name is established).

description

[x] Objective, authoritative, and neutral tone
[x] Descriptions is appropriate for use in user interfaces without a disclaimer by unaffiliated, neutral, third parties (wallets, block explorers, exchanges, etc.); no exclamations, calls to action, or disputable statements.
[x] All claims are substantiated above.

token information (if applicable)

[x] Token category is defined.
[x] If fungible tokens exist for the category, decimals is defined.
symbol

[x] Globally-unique base symbol, including among assets not listed in OpenTokenRegistry.
[x] Valid symbol (regular expression: /^[A-Z0-9]+[-A-Z0-9]*$/)
[x] Appropriate minimum length (For new, primarily-fungible base symbols: minimum of 4 characters; non-fungible base symbols: minimum of 6 characters; see Symbol Length Recommendations)
[x] No longer than 13 characters for base symbols
[x] No longer than 26 characters for full symbols

uris.icon

[x] Uses IPFS with a v1 CID
[x] Either SVG format OR 400px by 400px AVIF, WebP, or PNG

uris.web

[x] Domain name is owned by the issuing project or organization
[x] Either HTTPS protocol OR ongoing activity demonstrated via optional URI identifiers (described in Substantiation of Other Claims)

[x] Includes relevant historical information in previous snapshots OR this token has never been rebranded, redenominated, or reissued
[x] All static data (images, animations, videos, binary files, etc.) uses IPFS with v1 CIDs to ensure file integrity (e.g. ipfs://ba...).

Reviewed, looks great! Thanks for the submission @bchguru, and thanks @georgedonnelly for the first review 🚀


changelog

as a beginner-friendly cryptography library, having a changelog that explains the reason behind any significant change in the architecture of the code is really helpful for a newcomer

I like this. One way to do this that is easy is to ship releases of the library and follow semver. This was all the PRs and then put into a change-log automatically. Not sure if it's the best but could be a nice path forward.


How UE4 implements the bystander view of HoloLens 2？

Can UE4 also realize the third-person perspective of HoloLens 2?

you can do it on your own. basicly two steps:
1 space axis alignment by image tracking(QR code etc.) or azure spatial anchor, as this rep does.
2 sync operations by network


Registration page designed Closes #24

[https://github.com/gauravsingh1281/Rentalog-Rent-Management-Web-App-For-Landlords/issues/24](Closes #24)

Hi @gauravsingh1281 ,
I have submitted a pull request for the registration branch. I have made the following changes:

designed the registration page

I have tested the code and it is working as expected. I would appreciate it if you could take a look at my pull request and provide feedback.
Thanks,
@kcsaiganesh

Thank you for your contribution @kcsaiganesh 😇


Add text decoration to Typography

This PR add the textDecoration property to Typography to allow underline a text.

👉 It refers to the issue https://github.com/okp4/ui/issues/485

:tada: This PR is included in version 1.14.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


upgrade to recent upstream master

I'm currently upgrading to substrate master
work started on branch brenzi-upstream-sync
code adapted. stuck at
error: duplicate lang item in crate `sr_tee_io`: `panic_impl`.
  |
  = note: first defined in crate `sr_io`.

error: duplicate lang item in crate `sr_tee_io`: `oom`.
  |
  = note: first defined in crate `sr_io`.

caused by: https://github.com/paritytech/substrate/issues/3271

Supports now : https://github.com/paritytech/substrate/commit/f17d023bbe179f15678ac9989f471c9b18917e17


Add support for CHERI-enabled DMA

Add Support for CHERI-enabled DMA
Description
This pull request is a request for comments on how CHERI-enabled DMA could be implemented. This is related to https://github.com/CTSRD-CHERI/RISC-V_Galois_demo/pull/1
The permissions granted to the DMA engine are not final and should be tightened later.
When tightening the permissions it might make more sense to have two separate sets of capabilities for accessing buffers - one set with R/W permissions for software to use, and one with only R (for TX buffers) or only W (for RX buffers) for the DMA engine to use.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

The permissions granted here are indeed excessive. I used the execute permission in hardware as a way to disable checks for debugging purposes, and that's why I've given everything execute permissions for now. I'll reduce the permissions and add the ifdefs.
I think the cast to u32 might also need to be put back in when not compiling for CHERI-aware DMA.
I'll have a look and test.


font seems a bit clipped

0.2.0-beta
I like everything else you've done, but the "connected" string looks like it's clipped across the top (the top of the t and ns).
Either that or it's a weird font and I don't like it ;)
Sorry to be picky

It's the font being the font 😅
I wanted a font that was tall and bold for the connection states, the 't' is a little bit odd, so I'll look into alternatives.

Changed font in https://github.com/seanmtracey/GlowOrb-Emulator/commit/597598d163e7612fc4b0009ab597357568fc725b.


Wrong complexity class

I was just looking for references on parser core implementation, and I happened to find this repo. I thought it worth pointing out that this implementation has n squared complexity (on the number of tokens) where it should be linear. This is the result of using shift and unshift to manipulate the tokens array instead of push and pop. Shift is, of course, an O(n) operation on an array as every existing value must move to a new index.

Hello,
Things are probably less clear cut in Javascript/v8 than what you mention in your issue.
Cf for example this discussion regarding list operations in perl where it explains why common scenarios are O(1)

The consequence of this implementation is that all of perl's primitive list operators (insertion, fetching, determining array size, push, pop, shift, unshift, etc.) perform in O(1) time.

There are probably similar optimizations in Javascript/v8.
Did you write benchmarks highlighting the "n squared complexity" of the token-stream module or comparing the complexity of the Javascript/v8 implementation of push, pop, shift, unshift ?

I've never heard anyone claim that JS shift/unshift are O(1). I did in fact do some research to verify before I opened this ticket. V8 optimizes by copying the entire array into new memory instead of moving every element, but it's still not the right complexity class. See: https://stackoverflow.com/questions/44031591/performance-of-array-push-vs-array-unshift.

Here's more data for you: https://jsperf.com/array-push-vs-unshift. No graph, but it confirms that v8 also does not implement an O(1) opt.

Interesting it seems like it could be interesting to investigate. Be sure that I was not judging you in my message and I am sorry if my tone sounded dubious. it is just that sometimes v8 auto-optimisations go a long way and I am surprised that unshift gets a so bad performance compared to what perl seem to be doing.
I did not participate in the token-stream module did you read the code and does it seem easy to you to "reverse" the implementation (using push vs unshift) or would it need more work ?

I just opened the code I did not realize it is a very small module beeing mainly a wrapper around the shift/unshift functions.
Maybe it is easy to swap things and test it all with pug-parser. It could indeed make a performance improvement if the O(n) complexity is heavily hit during the parsing that would be a great discovery !

Yeah that's kind of the curse of JS -- perf isn't explicit and it's hard to keep track of which optimizations are where and whether they can be relied on.
Looking at the code the weirdest bit is that an external array is mutated. Using this class may have side effects. If you copy the array then you could just reverse it in the constructor, swap all the access logic around, and you'd be fine. I thought you might even be able to replace array mutation with simple indexing, but then the defer method wouldn't work.

Since mutation of the passed array is surprising and not documented, I'd consider changing that behavior a semver-patch bugfix.

I think that this module is mainly used as a wrapper around the array adding a sort of parsing oriented syntaxic sugar so dependent modules are probably aware and ok with the mutation that occurs.
I found this jsperf - https://jsperf.com/ilogico-reverse-and-pop-vs-shift - that seems to show that "reverse + pop" is nearly equivalent to shift (the manual reverse + pop is 2x better than shift though)
I think it needs experimentation to see if this would make a big difference of not for pugjs and if/where the reverse should be taking place. The tokens here are coming from pug-lexer that uses push to build up the array of tokens so it seems that the reverse will need to take place at some point if pop/push should be used in the parser instead of shift/unshift.
Or there are maybe modules like https://www.npmjs.com/package/fast-list but then that might cause a problem with lookahead(index) that would degrade its perf.

@conartist6 Thanks for reporting this. You're totally right that this is probably causing significantly worse perf in pug than it should be. I wrote this a long time ago and have had to resolve issues just like this on other libraries I maintain (e.g. throat's heavily optimised queue implementation). I think the best option here will be to just track the index in the Array without actually removing values. Since the tokens array is usually short-lived, that should be pretty efficient.


Add clarification for naming convention for date types

Source: https://github.com/octoenergy/styleguide/blob/master/python.md#model-field-naming-conventions

Thank you!


fix(resolver): recover panic during resolve

Proposed Changes

add panic handling for the resolve process

I submit this contribution under the Apache-2.0 license.

Maybe good to add logging that allows users to see on which file the analysis choked if any parsing issues remain. That will make troubleshooting a lot easier for future parsing-related issues. As can be seen in #6513, the stacktrace did not provide any helpful information on which file the analysis broke. Would make future troubleshooting a lot more efficient.

@p3pijn , you right! we will add your idea into our future implementations! thanks for your input!


[Question]: gnet client works not as expected even tho i did it according to the api ref

Connecting with a web server, however when the connection is opened i write http request data payload, send it. But get no response back..
What is wrong?
package main

import (
	"fmt"
	"log"
	"net"

	"github.com/panjf2000/gnet/v2"
)

type EventHandler struct {
	gnet.BuiltinEventEngine
	eng gnet.Engine
}

func (es *EventHandler) OnBoot(eng gnet.Engine) gnet.Action {
	fmt.Println("boot")
	es.eng = eng
	return gnet.None
}

func (e *EventHandler) OnOpen(c gnet.Conn) (out []byte, action gnet.Action) {
	fmt.Println("onopen")
	out = []byte("GET / HTTP/1.1\r\nHost: pix4.dev\r\n\r\n")
	return out, gnet.None
}

func (e *EventHandler) OnTraffic(c gnet.Conn) (action gnet.Action) {
	fmt.Println("traffic")
	rd, err := c.Next(-1)
	if err != nil {
		log.Fatal(err)
	}
	fmt.Println(string(rd), 1)
	return gnet.None
}

func (e *EventHandler) OnClose(c gnet.Conn, err error) (action gnet.Action) {
	fmt.Println(err)
	return gnet.None
}

func main() {
	client, err := gnet.NewClient(&EventHandler{}, gnet.WithMulticore(true))
	if err != nil {
		log.Fatal(err)
	}

	if err := client.Start(); err != nil {
		log.Fatal(err)
	}

	_, err = client.Dial("tcp", "<IP_ADDRESS>:80")
	if err != nil {
		log.Fatal(err)
	}

}

Too few information, use bug report template to create a new issue.


mocha test runner failing

Hi, I'm trying out the latest test feature on alm, and the console is reporting
MOCHA STDERR:   ...\node_modules\alm\src\server\workers\tested\runners\mochaInstrumenter.ts:9
import * as common from "./instrumenterCommon";
^^^^^^
SyntaxError: Unexpected token import
    at Object.exports.runInThisContext (vm.js:76:16)

Error was reproduced on OS X as well as Windows 10, running Node 6.x.
$ npm list -g alm
`--<EMAIL_ADDRESS>$ typescript --init
$ typings init
$ typings install --global mocha
$ cat alm.json
{
  "tests": {
    "include": [
       "./tests/*.ts"
    ]
  }
}
$ cat tests/sample.ts
/// <reference path="../typings/index.d.ts" />

describe('simple test', () => {
  it('adds 2 + 2', () => {
    throw 'bad stuff'
  })
})

worked for me for some reason :

Verified. Deployed version has this bug :

Figuring out why :rose:

I'm new to alm, but happy to help out if you point to me where to start looking.

I'm new to alm, but happy to help out if you point to me where to start looking.

I'll fix it. Things I've ruled out : node_modules folder doesn't fix it (basically copied my local copy to replace the npm installed copy and it still results in an error). Still since you asked :rose:
How testing works
First be familiar with how workers work : https://basarat.gitbooks.io/alm/content/contributing/async.html
Next its just this worker : https://github.com/alm-tools/alm/blob/master/src/server/workers/tested/testedWorker.ts
Which just calls mochaRunner : https://github.com/alm-tools/alm/blob/aa86da0eaa8afddda2b895b512ee3eaa2194ac29/src/server/workers/tested/testedWorker.ts#L173
Which just executes this command to run mocha : https://github.com/alm-tools/alm/blob/aa86da0eaa8afddda2b895b512ee3eaa2194ac29/src/server/workers/tested/runners/mochaRunner.ts#L37-L99
Based on the error it feels like ts-node isn't running (it should compile away the import * before handing it over to mocha :rose:

Thanks. Documenting this for someone like myself in the future - able to reproduce error executing
$ C:/Users/Chui/AppData/Roaming/npm/node_modules/alm/node_modules/mocha/bin/_mocha \
  --require C:/Users/Chui/AppData/Roaming/npm/node_modules/alm/node_modules/ts-node/register  \
  --require C:/Users/Chui/AppData/Roaming/npm/node_modules/alm/src/server/workers/tested/runners/mochaInstrumenter.ts \
  --reporter json --full-trace tests/sample.ts

@teyc thanks for the fix 🎉 🎈 ! What a great day to wake up to :heart:
Released with 2.0.4 :rose:


Netty SecureRandom issue

Hi,
It is netty 4.0.18, and pushy is 0.3 with jdk <IP_ADDRESS> x64 on centos 6.
The tomcat 7.0.53 catalina.out turns out:
Apr 23, 2014 2:19:01 PM io.netty.util.internal.logging.Slf4JLogger warn
WARNING: Failed to generate a seed from SecureRandom within 3 seconds. Not enough entrophy?
By checking this:
http://netty.io/5.0/xref/io/netty/util/internal/ThreadLocalRandom.html
I think it is thread related issue.
Any helps?

I'm using netty-4.0.25-final, but it appeared the WARNNIG unfortunately.
I don't know what is the name of machine running app, but the result of its uname -a is HP-UX nateifsd B.11.11 U 9000/800<PHONE_NUMBER> unlimited-user license.
And java version is
java version "<IP_ADDRESS>"
Java(TM) SE Runtime Environment (build <IP_ADDRESS>-jinteg_01_dec_2011_03_39-b00)
Java HotSpot(TM) Server VM (build 20.3-b02-jre<IP_ADDRESS>-rc1b1 PA2.0 (aCC_AP), mixed mode)

How can I avoid this warning?

I saw the issue again.
2015-09-15 21:03:28,470 WARN [io.netty.util.internal.ThreadLocalRandom] 136 - Failed to generate a seed from SecureRandom within 3 seconds. Not enough entrophy?
The application is running under ARM cpu.
agent@agentpi:~/agent$ uname -a
Linux agentpi 3.18.11-v7+ #781 SMP PREEMPT Tue Apr 21 18:07:59 BST 2015 armv7l GNU/Linux
java -version
java version "1.8.0"
Java(TM) SE Runtime Environment (build 1.8.0-b132)
Java HotSpot(TM) Client VM (build 25.0-b70, mixed mode)
Netty version:
#Generated by netty-parent/pom.xml
#Thu, 12 Jun 2014 16:35:31 +0200
netty-transport-rxtx.version=4.0.20.Final
netty-transport-rxtx.buildDate=2014-06-12 16:35:31 +0200
netty-transport-rxtx.commitDate=2014-06-12 16:14:48 +0200
netty-transport-rxtx.shortCommitHash=1709113
netty-transport-rxtx.longCommitHash=1709113a1f27be021e890d07c4d94576e2e7710c
netty-transport-rxtx.repoStatus=clean
#Generated by netty-parent/pom.xml
#Thu, 12 Jun 2014 16:28:52 +0200
netty-common.version=4.0.20.Final
netty-common.buildDate=2014-06-12 16:28:52 +0200
netty-common.commitDate=2014-06-12 16:14:48 +0200
netty-common.shortCommitHash=1709113
netty-common.longCommitHash=1709113a1f27be021e890d07c4d94576e2e7710c
netty-common.repoStatus=clean
#Generated by netty-parent/pom.xml
#Thu, 12 Jun 2014 16:30:14 +0200
netty-buffer.version=4.0.20.Final
netty-buffer.buildDate=2014-06-12 16:30:14 +0200
netty-buffer.commitDate=2014-06-12 16:14:48 +0200
netty-buffer.shortCommitHash=1709113
netty-buffer.longCommitHash=1709113a1f27be021e890d07c4d94576e2e7710c
netty-buffer.repoStatus=clean
#Generated by netty-parent/pom.xml
#Thu, 12 Jun 2014 16:31:11 +0200
netty-transport.version=4.0.20.Final
netty-transport.buildDate=2014-06-12 16:31:11 +0200
netty-transport.commitDate=2014-06-12 16:14:48 +0200
netty-transport.shortCommitHash=1709113
netty-transport.longCommitHash=1709113a1f27be021e890d07c4d94576e2e7710c
netty-transport.repoStatus=clean
#Generated by netty-parent/pom.xml
#Thu, 12 Jun 2014 16:35:03 +0200
netty-codec-socks.version=4.0.20.Final
netty-codec-socks.buildDate=2014-06-12 16:35:03 +0200
netty-codec-socks.commitDate=2014-06-12 16:14:48 +0200
netty-codec-socks.shortCommitHash=1709113
netty-codec-socks.longCommitHash=1709113a1f27be021e890d07c4d94576e2e7710c
netty-codec-socks.repoStatus=clean
#Generated by netty-parent/pom.xml
#Thu, 12 Jun 2014 16:33:27 +0200
netty-handler.version=4.0.20.Final
netty-handler.buildDate=2014-06-12 16:33:27 +0200
netty-handler.commitDate=2014-06-12 16:14:48 +0200
netty-handler.shortCommitHash=1709113
netty-handler.longCommitHash=1709113a1f27be021e890d07c4d94576e2e7710c
netty-handler.repoStatus=clean
#Generated by netty-parent/pom.xml
#Thu, 12 Jun 2014 16:32:48 +0200
netty-codec.version=4.0.20.Final
netty-codec.buildDate=2014-06-12 16:32:48 +0200
netty-codec.commitDate=2014-06-12 16:14:48 +0200
netty-codec.shortCommitHash=1709113
netty-codec.longCommitHash=1709113a1f27be021e890d07c4d94576e2e7710c
netty-codec.repoStatus=clean
#Generated by netty-parent/pom.xml
#Thu, 12 Jun 2014 16:33:59 +0200
netty-codec-http.version=4.0.20.Final
netty-codec-http.buildDate=2014-06-12 16:33:59 +0200
netty-codec-http.commitDate=2014-06-12 16:14:48 +0200
netty-codec-http.shortCommitHash=1709113
netty-codec-http.longCommitHash=1709113a1f27be021e890d07c4d94576e2e7710c
netty-codec-http.repoStatus=clean
#Generated by netty-parent/pom.xml
#Thu, 12 Jun 2014 16:36:13 +0200
netty-transport-udt.version=4.0.20.Final
netty-transport-udt.buildDate=2014-06-12 16:36:13 +0200
netty-transport-udt.commitDate=2014-06-12 16:14:48 +0200
netty-transport-udt.shortCommitHash=1709113
netty-transport-udt.longCommitHash=1709113a1f27be021e890d07c4d94576e2e7710c
netty-transport-udt.repoStatus=clean
#Generated by netty-parent/pom.xml
#Thu, 12 Jun 2014 16:35:49 +0200
netty-transport-sctp.version=4.0.20.Final
netty-transport-sctp.buildDate=2014-06-12 16:35:49 +0200
netty-transport-sctp.commitDate=2014-06-12 16:14:48 +0200
netty-transport-sctp.shortCommitHash=1709113
netty-transport-sctp.longCommitHash=1709113a1f27be021e890d07c4d94576e2e7710c
netty-transport-sctp.repoStatus=clean

Firewall blocking the ports causes the issue in redhat. Cleared up by adding ports to the intended interface in firewalld.
firewall-cmd --zone=public --add-port=52489/tcp
Just thought I'd respond with how I fixed it on my system.

http://stackoverflow.com/questions/28173570/conditions-for-lack-of-entophy-in-threadlocalrandom
cat /proc/sys/kernel/random/entropy_avail
391
Normally,It is large number,when the issue happens, it is small,just 29 .

http://askubuntu.com/questions/99144/how-can-i-permantly-increase-the-entropy-avail-level
sudo apt-get install haveged -y
It works for me now. really great.


Adjust message handlers' access levels

Recently, the conventions on which access level to use for certain handler methods have been changed.
In this PR we update those access levels.

@armiol, PTAL.

@armiol, PTAL again.
Also, could you please turn off the automatic review dismiss for this repository?


register v0.1.0

@JuliaRegistrator register branch=release/v0.1

Registration pull request created: JuliaRegistries/General/61754
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" a370100700d46182f13e89519acb446cfbb163af
git push origin v0.1.0


[UX] Indicate there are more icons at bottom on mobile

When accessing isaiah on mobile devices, there are a few icons at the bottom of the screen.
I did not realize there are more than 4 icons there at beginning, and learnt there are more icons by accident.
I think it would be a better to have an indicator or something in the docker at the bottom of the screen to tell user (especially the first time user) there are more icons. It would help first time user.

I found this at very bottom of README
https://github.com/will-moss/isaiah?tab=readme-ov-file#a-feature-that-works-on-desktop-is-missing-from-the-mobile-user-interface

Hi,
Thanks a lot for opening that issue (along with all the others!) and for providing those details.
I have just published a new release that should address the issue mentioned here.
From now on, when using a mobile device, a popup message will be shown on first launch, indicating that more buttons are available in the menu, and it's scrollable too.
I hope it works better for everyone now, as that issue was also mentioned earlier by another user.

Thank you for the update. And thank you for making it work on both desktop and mobile devices. Sorry that I have not tried the new version.
I was thinking that a" ..." Or humberger menu may be better than sliding left and right solution on mobile. I don't do front end code so I am not sure how difficult it is. Just some random thoughts.
Here is how it looks like on the GitHub mobile web interface:

Hi again!
Thanks to you, and no need to be sorry.
I've just released a new version, that now uses a hamburger menu on mobile.
I'd definitely agree that it "feels" better now, but I let you judge for yourself!

Looks good. Thanks


French version of the Kubernetes ingress documentation

The ingress link --> "Support services exposed with ingress" in https://github.com/goharbor/harbor-operator/blob/master/README.md#ingress-controller-types leads to the French doc, is this intended?

thanks for reporting this typo.


Errors resolving hostname when trying to play response

Flavor
MicroWakeWord
Checklist

[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of currently previous issues..
[X] I am able to consult debug logging for my ESPHome instance.

Describe the issue
When I say the wakeword, (hey nabu), the speaker's lights respond, and home assistant performs the command. However, I do not hear a response. there are errors in the log that indicate a failure to resolve the hostname of my home assistant.
[18:14:58][D][esp-idf:000]: E (683339) esp-tls: couldn't get hostname for :hass.klopnet.com: getaddrinfo() returns 202, addrinfo=0x0
Reproduction steps

Use a wakeword and command
observe the correct response
observe no reply message is uttered
Find errors in log along with text of what the reply should have been
...

Debug logs
[18:14:51][D][light:036]: 'top_led' Setting:
[18:14:51][D][light:051]:   Brightness: 70%
[18:14:51][D][light:059]:   Red: 0%, Green: 20%, Blue: 100%
[18:14:51][D][light:109]:   Effect: 'processing'
[18:14:51][D][voice_assistant:439]: State changed from STOPPING_MICROPHONE to AWAITING_RESPONSE
[18:14:51][D][voice_assistant:563]: Event Type: 4
[18:14:51][D][voice_assistant:591]: Speech recognised as: "Turn off the lights."
[18:14:51][D][voice_assistant:563]: Event Type: 5
[18:14:51][D][voice_assistant:596]: Intent started
[18:14:51][D][voice_assistant:563]: Event Type: 6
[18:14:51][D][voice_assistant:563]: Event Type: 7
[18:14:51][D][voice_assistant:619]: Response: "Turned off the lights"
[18:14:51][D][voice_assistant:563]: Event Type: 8
[18:14:51][D][voice_assistant:639]: Response URL: "https://hass.klopnet.com/api/tts_proxy/85d43b448ab715eae17c0361864a34ff749eb14a_en-gb_29e3de9935_cloud.mp3"
[18:14:51][D][voice_assistant:439]: State changed from AWAITING_RESPONSE to STREAMING_RESPONSE
[18:14:51][D][voice_assistant:445]: Desired state set to STREAMING_RESPONSE
[18:14:51][D][media_player:059]: 'Onju Voice Satellite 548058' - Setting
[18:14:51][D][media_player:066]:   Media URL: https://hass.klopnet.com/api/tts_proxy/85d43b448ab715eae17c0361864a34ff749eb14a_en-gb_29e3de9935_cloud.mp3
[18:14:51][D][adf_media_player:030]: Got control call in state 1
[18:14:51][D][esp_adf_pipeline:050]: Starting request, current state STOPPED
[18:14:51][D][esp_adf_pipeline:302]: State changed from STOPPED to PREPARING
[18:14:51][I][adf_media_player:135]: got new pipeline state: 1
[18:14:51][D][adf_i2s_out:127]: Set final i2s settings: 16000
[18:14:51][D][esp_audio_processors:079]: New settings: SRC: rate: 16000, ch: 2 DST: rate: 16000, ch: 2
[18:14:51][D][light:036]: 'top_led' Setting:
[18:14:51][D][light:059]:   Red: 20%, Green: 100%, Blue: 0%
[18:14:51][D][light:109]:   Effect: 'speaking'
[18:14:51][D][voice_assistant:563]: Event Type: 2
[18:14:51][D][voice_assistant:653]: Assist Pipeline ended
[18:14:51][D][esp-idf:000]: I (676331) AUDIO_ELEMENT: [http] AEL_MSG_CMD_RESUME,state:1

[18:14:51][D][esp-idf:000]: I (676333) AUDIO_ELEMENT: [decoder] AEL_MSG_CMD_RESUME,state:1

[18:14:51][D][esp_aud:000]:
ERROR Fatal error: protocol.data_received() call failed.
protocol: <aioesphomeapi._frame_helper.noise.APINoiseFrameHelper object at 0x7f902fe377f0>
transport: <_SelectorSocketTransport fd=6 read=polling write=<idle, bufsize=0>>
Traceback (most recent call last):
  File "/usr/lib/python3.11/asyncio/selector_events.py", line 1009, in _read_ready__data_received
    self._protocol.data_received(data)
  File "aioesphomeapi/_frame_helper/noise.py", line 136, in aioesphomeapi._frame_helper.noise.APINoiseFrameHelper.data_received
  File "aioesphomeapi/_frame_helper/noise.py", line 163, in aioesphomeapi._frame_helper.noise.APINoiseFrameHelper.data_received
  File "aioesphomeapi/_frame_helper/noise.py", line 319, in aioesphomeapi._frame_helper.noise.APINoiseFrameHelper._handle_frame
  File "/usr/local/lib/python3.11/dist-packages/noise/state.py", line 74, in decrypt_with_ad
    plaintext = self.cipher.decrypt(self.k, self.n, ad, ciphertext)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/noise/backends/default/ciphers.py", line 13, in decrypt
    return self.cipher.decrypt(nonce=self.format_nonce(n), data=ciphertext, associated_data=ad)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "src/chacha20poly1305_reuseable/__init__.py", line 127, in chacha20poly1305_reuseable.ChaCha20Poly1305Reusable.decrypt
  File "src/chacha20poly1305_reuseable/__init__.py", line 147, in chacha20poly1305_reuseable.ChaCha20Poly1305Reusable.decrypt
  File "src/chacha20poly1305_reuseable/__init__.py", line 263, in chacha20poly1305_reuseable._decrypt_with_fixed_nonce_len
  File "src/chacha20poly1305_reuseable/__init__.py", line 273, in chacha20poly1305_reuseable._decrypt_data
cryptography.exceptions.InvalidTag
WARNING onju-voice-548058 @ <IP_ADDRESS>: Connection error occurred: onju-voice-548058 @ <IP_ADDRESS>: Invalid encryption key: received_name=onju-voice-548058
INFO Processing unexpected disconnect from ESPHome API for onju-voice-548058 @ <IP_ADDRESS>
WARNING Disconnected from API
INFO Successfully connected to onju-voice-548058 @ <IP_ADDRESS> in 0.004s
INFO Successful handshake with onju-voice-548058 @ <IP_ADDRESS> in 0.055s
[18:14:58][D][esp-idf:000]: E (683339) esp-tls: couldn't get hostname for :hass.klopnet.com: getaddrinfo() returns 202, addrinfo=0x0

[18:14:58][D][esp-idf:000]: E (683343) esp-tls: Failed to open new connection

[18:14:58][D][esp-idf:000]: E (683348) TRANSPORT_BASE: Failed to open a new connection

[18:14:58][D][esp-idf:000]: E (683352) HTTP_CLIENT: Connection failed, sock < 0

[18:14:58][D][esp-idf:000]: E (683356) HTTP_STREAM: Failed to open http stream

[18:14:58][D][esp-idf:000]: E (683359) AUDIO_ELEMENT: [http] AEL_STATUS_ERROR_OPEN,28674

[18:14:58][D][esp-idf:000]: W (683363) AUDIO_ELEMENT: [http] audio_element_on_cmd_error,7

[18:14:58][D][esp-idf:000]: W (683368) AUDIO_ELEMENT: IN-[decoder] AEL_IO_ABORT

[18:14:58][D][esp-idf:000]: E (683371) MP3_DECODER: failed to read audio data (line 117)

[18:14:58][D][esp-idf:000]: W (683375) AUDIO_ELEMENT: [decoder] AEL_IO_ABORT, -3

[18:14:58][D][esp-idf:000]: I (683380) MP3_DECODER: Closed

[18:15:01][I][esp_adf_pipeline:185]: Pipeline preparation timeout!
[18:15:01][D][esp-idf:000]: W (686307) AUDIO_PIPELINE: Without stop, st:1

[18:15:01][D][esp_adf_pipeline:302]: State changed from PREPARING to STOPPING
[18:15:01][I][adf_media_player:135]: got new pipeline state: 4
[18:15:01][D][esp_adf_pipeline:302]: State changed from STOPPING to STOPPED
[18:15:01][I][adf_media_player:135]: got new pipeline state: 5

I suspect the issue is the colon receding the hostname


XML import treated as modal

In my code I'm streaming a response from a web service into an XML port and then importing it through the XML port.
The import part of the XML port is treated as modal, so if I want to use my code in a write transaction I need to add a commit before calling XMLPort.Import(). I have never seen a page open when I run this code and in the documentation I can't find anything about why this should be treated as a modal behavior.
So my question is this. Does the import procedure of XML ports really need to be treated as modal or is there some case which I'm not aware of which can cause a suspension of the code execution?

Hi @dennisfrostlander,
Took some time to recall the issue.
I'm using AL 0.16.26913 and BC 12.3.23590.23828-US.
This has happened in one or more occasions. The one I was able to reproduce was a subscriber to an OnRecModify. When I modify the record in a page and the XMLPort.Import from the subscriber hits I get the following error:

Do you mean OnModifyRecord?
I tried the following sample, does not repro on the latest version.
Could you please provide the minimal repro which causes the error in your scenario?
pageextension 50100 CustomerListExt extends "Customer Card"
{
    trigger OnModifyRecord(): Boolean
    var
        x: XmlPort MyXmlport;
        f: File;
        os: OutStream;
        is: InStream;
        rec: Record Customer;
    begin
        //f.Create('c:\temp\xmlport.xml');
        //f.CreateOutStream(os);
        //Xmlport.Export(Xmlport::MyXmlport, os);

        f.Open('c:\temp\xmlport.xml');
        f.CreateInStream(is);
        Xmlport.Import(Xmlport::MyXmlport, is);
        Message('imported xml port');
    end;
}

xmlport 50100 MyXmlport
{
    schema
    {
        textelement(CustomerElement)
        {
            tableelement(Customer; Customer)
            {
                fieldattribute(CustomerName; Customer.Name)
                {
                }
            }
        }
    }
}


Door lock status

Hello,
Having an issue with Siri knowing and being able to control door locks. I can go through the Home app and control fine. However, when using Siri, it replies that it "didn't hear back." This has been the case on 10.2b3, b2 and b1.  Other switches and devices seem to be controlled with Siri fine.
I'm using 0.4.9 of homebridge, and also I am using the homebridge-smartthings plugin.

Might not be a homebridge issue. I sometimes get the "didn't hear back" response from Siri with my Schlage Sense locks, which are HomeKit compatible and therefore do not require homebridge. For me, it appears that Siri succeeds in locking or unlocking the door, but the lock does not report back its status in time (I think I read somewhere that Siri will wait a maximum of 10 seconds for a response).