SyntaxError: Unexpected end of JSON input when trying to publish packages

Affected Packages
All of the packages
Problem
When I try to publish my packages using pnpx changesets publish I get this error:
➜ pnpx changeset publish
🦋  info npm info @tinyhttp/app
🦋  info npm info @tinyhttp/cors
🦋  info npm info @tinyhttp/etag
🦋  info npm info @tinyhttp/logger
🦋  info npm info @tinyhttp/static
🦋  info @tinyhttp/app is being published because our local version (0.1.21) has not been published on npm
🦋  info @tinyhttp/cors is being published because our local version (0.1.20) has not been published on npm
🦋  info @tinyhttp/etag is being published because our local version (0.1.20) has not been published on npm
🦋  info @tinyhttp/logger is being published because our local version (0.1.20) has not been published on npm
🦋  info @tinyhttp/static is being published because our local version (0.1.20) has not been published on npm
🦋  info Publishing "@tinyhttp/app" at "0.1.21"
🦋  info Publishing "@tinyhttp/cors" at "0.1.20"
🦋  info Publishing "@tinyhttp/etag" at "0.1.20"
🦋  info Publishing "@tinyhttp/logger" at "0.1.20"
🦋  info Publishing "@tinyhttp/static" at "0.1.20"
🦋  error SyntaxError: Unexpected end of JSON input
🦋  error     at JSON.parse (<anonymous>)
🦋  error     at internalPublish (/home/v1rtl/Coding/tinyhttp/node_modules/.pnpm/@changesets/cli@2.9.1_@types+node@14.0.13/node_modules/@changesets/cli/dist/cli.cjs.dev.js:591:19)
🦋  error     at processTicksAndRejections (internal/process/task_queues.js:97:5)

Same happens with ./node_modules/.bin/changeset publish
I don't know what causes it because there's no clear error message.
Helpful info
reproduction repository: https://github.com/talentlessguy/tinyhttp
changesets config: https://github.com/talentlessguy/tinyhttp/blob/master/.changeset/config.json
node version: 14.4.0
pnpm version: 5.0.2
npm version: 6.14.5

I'm having the exact same issue with pnpm
The failing build is here https://github.com/remirror/remirror/pull/251/checks?check_run_id=838235175
The commit causing the issue is here: https://github.com/remirror/remirror/tree/7f4153e0b08ae709dbdd28b09d6ebd3809e9a825
Config: https://github.com/remirror/remirror/blob/7f4153e0b08ae709dbdd28b09d6ebd3809e9a825/support/root/.changeset/config.json
Prerelease config: https://github.com/remirror/remirror/blob/7f4153e0b08ae709dbdd28b09d6ebd3809e9a825/support/root/.changeset/pre.json
Node: 12
pnpm: 5.2.6
The annoying thing is that I also can't run the release command from my own machine. It just freezes at the same point with no error displayed.

Thank you both for those reports. I will make sure to investigate this asap.

In order to get the release to work I've patched the @changesets/cli package to use npm for publishing always regardless of the project. The publish now works locally.
It's possible something changed in pnpm publish in version 5. Although this is the first time I've actually used pnpm to publish so I'm not sure.

@ifiokjr you may just use pnpm to publish the bumped versions. Just run pnpm publish -r.

Ahh that's very useful to know. It looks like pnpm is using changesets as well. How do you manage tags?

@zkochan I just did my first update using pnpm publish -r --tag next and it worked like a charm. Thanks for the tip.
I also like how you're managing releases for the pnpm project. I take it you're using changesets to generate the package specific changelogs and then you're manually adding your own top level changelog and github release. This strategy makes a lot of sense and I think I'll adopt it. With 80+ packages in remirror, creating unfiltered package releases has become too noisy.

@zkochan i think I've already asked this in the past, but... do you see any difference between our publishing script and pnpm publish -r? Would it be safe to just switch to pnpm entirely for this? Is there any required pnpm version for this command? Can the same be used for single package repos?
I would still be interested in investigating why this fails though:https://github.com/atlassian/changesets/blob/81595022e27e4b94a1bc87e56eabafb9a31e8315/packages/cli/src/commands/publish/npm-utils.ts#L126-L138

@Andarist we have discussed it here: #238
To summarize:

pnpm publishes packages in topological order
it works much faster than changesets

I think, when users use pnpm, it is safe to use pnpm publish -r in both single-package cases and multi-package repositories.

We've just released a new version of @changesets/cli with some additional logs for failed JSON.parse calls - if somebody could try running a publish with this new version this would be highly helpful in debugging this problem.

@Andarist hello, I tried it once again, here's the output:
error parsing json:
🦋  error SyntaxError: Unexpected end of JSON input
🦋  error     at JSON.parse (<anonymous>)
🦋  error     at jsonParse (/home/v1rtl/Coding/tinyhttp/node_modules/.pnpm/@changesets/cli@2.9.2/node_modules/@changesets/cli/dist/cli.cjs.dev.js:480:17)
🦋  error     at internalPublish (/home/v1rtl/Coding/tinyhttp/node_modules/.pnpm/@changesets/cli@2.9.2/node_modules/@changesets/cli/dist/cli.cjs.dev.js:603:14)
🦋  error     at processTicksAndRejections (internal/process/task_queues.js:93:5)

Figured out the bug @Andarist @zkochan: there's a race condition between changesets publishing the manifests, and pnpm rewriting those manifests. That bug happens here: https://github.com/pnpm/pnpm/blob/master/packages/plugin-commands-publishing/src/publish.ts#L212-L223
I think, basically, changesets needs to throw the ball to pnpm on this one, and let it handle all the publishing.

In case that appears to be a non-sequitor, the error actually comes from the manifest being published referencing another dependency in the monorepo, whose manifest is currently missing as it undergoes the pnpm transition.

@devin-fee-ah how this can result in a JSON.parse fail later? 🤔 I understand that the manifest can not be updated properly but it seems like a potentially different problem.

I think, basically, changesets needs to throw the ball to pnpm on this one, and let it handle all the publishing.

This is probably the way to go for multiple reasons. Would you be willing to help us with this one? I probably won't have time to work on this one any time soon.

Adding additional logging to /tmp/f/mono/.pnpm/@changesets/cli<EMAIL_ADDRESS>  // extra
  console.error(stdout.toString())
  console.error(stderr.toString())

  // original: ~L701 in function internalPublish
  let json = jsonParse(stdout.toString().replace(/[^{]*/, ""));

I get:
 ERROR  Cannot resolve workspace protocol of dependency "@mono/lib-foo" because this dependency is not installed. Try running "pnpm install".

error parsing json:
🦋  error SyntaxError: Unexpected end of JSON input
🦋  error     at JSON.parse (<anonymous>)
🦋  error     at jsonParse (/tmp/f/mono/.pnpm/@changesets/cli@2.11.1/node_modules/@changesets/cli/dist/cli.cjs.dev.js:557:17)
🦋  error     at internalPublish (/tmp/f/mono/.pnpm/@changesets/cli@2.11.1/node_modules/@changesets/cli/dist/cli.cjs.dev.js:705:14)
🦋  error     at runMicrotasks (<anonymous>)
🦋  error     at processTicksAndRejections (internal/process/task_queues.js:97:5)

Now, for a different problem, I'm only getting pnpm to publish ~75% of my packages using pnpm publish (at the root). I can then manually go and publish the remaining ~12 packages.

Now, for a different problem, I'm only getting pnpm to publish ~75% of my packages using pnpm publish (at the root). I can then manually go and publish the remaining ~12 packages.

Is this caused by the mentioned problem or is it a different problem with Changesets or Pnpm itself?

That last part is independent of changesets.

Gotcha, thank you for investigating this and providing more information. This is very helpful. I think at this point it's pretty obvious what we should do but there are no time resources in the team to handle this ourselves. I can provide guidance, reviews etc for anyone who would like to help out though.

Alterrnatively, you could provide a third entrypoint –– "tag". So we'd have [version, publish and tag] allowing a user to override the publish step more easily.
The niceness of having tag as a separate entrypoint (breaking it out of publish) is that if publishing for an n'th package fails, and it's re-run... the tag for every package before the failed publish (on re-run) won't get tagged.

Could u prepare a separate issue for the tag describing the problem that it would fix? It would allow us for tracking this more easily as the proposal is separate (but related) to a problem here.

Done. https://github.com/atlassian/changesets/issues/478

I've been having a similar problem with one of my packages (not a monorepo). Here's an example of failed run: https://github.com/wikibus/Alcaeus/runs/1589751903?check_suite_focus=true
Is this the same problem? How do I resolve it?

Thanks for the report and link to the failed run - I will try to look into it but I have a lot on my plate right now so it might take a while. If you could investigate this further it could help us tremendously

@tpluscode it seems like literally npm profile has returned the same runtime error encoded in JSON a lot of times which ahs resulted in the incorrect JSON. This has happened here:
https://github.com/atlassian/changesets/blob/3c0f593a6632a4946fdaa16a06ef1add27cd6c69/packages/cli/src/commands/publish/npm-utils.ts#L61-L64
My bet is that this is actually caused by the fact that your project depends on gitbook which in turn depends (maybe indirectly) on some very old version of npm and this spawn calls to it instead of the global one that would actually return sensible results.
To fix this we'd have to figure out how to call the correct version of npm in this scenario.

Ah thank you for investigating. I have in fact started removing gitbook from the picture so I should good once its gone :)

We were just bit by this on our last publish (curiously our first publish went fine, but once we published more packages it triggered whatever causes this)

[2021-01-05T21:25:14.339Z] > changeset publish

[2021-01-05T21:25:14.339Z]

[2021-01-05T21:25:14.738Z] 🦋  info npm info @skyline/color-settings

[2021-01-05T21:25:14.738Z] 🦋  info npm info @skyline/icons

[2021-01-05T21:25:14.738Z] 🦋  info npm info @skyline/scss

[2021-01-05T21:25:14.738Z] 🦋  info npm info @skyline/tokens

[2021-01-05T21:25:14.738Z] 🦋  info npm info @skyline/vue

[2021-01-05T21:25:14.738Z] 🦋  info npm info @skyline/vuepress-theme-default

[2021-01-05T21:25:17.563Z] 🦋  info @skyline/color-settings is being published because our local version (2.0.0) has not been published on npm

[2021-01-05T21:25:17.563Z] 🦋  warn @skyline/icons is not being published because version 2.0.0 is already published on npm

[2021-01-05T21:25:17.563Z] 🦋  info @skyline/scss is being published because our local version (2.2.1) has not been published on npm

[2021-01-05T21:25:17.563Z] 🦋  info @skyline/tokens is being published because our local version (1.16.1) has not been published on npm

[2021-01-05T21:25:17.563Z] 🦋  info @skyline/vue is being published because our local version (4.3.0) has not been published on npm

[2021-01-05T21:25:17.563Z] 🦋  info @skyline/vuepress-theme-default is being published because our local version (0.4.17) has not been published on npm

[2021-01-05T21:25:17.563Z] 🦋  info Publishing "@skyline/color-settings" at "2.0.0"

[2021-01-05T21:25:17.563Z] 🦋  info Publishing "@skyline/scss" at "2.2.1"

[2021-01-05T21:25:17.563Z] 🦋  info Publishing "@skyline/tokens" at "1.16.1"

[2021-01-05T21:25:17.563Z] 🦋  info Publishing "@skyline/vue" at "4.3.0"

[2021-01-05T21:25:17.563Z] 🦋  info Publishing "@skyline/vuepress-theme-default" at "0.4.17"

[2021-01-05T21:25:21.227Z] error parsing json:

[2021-01-05T21:25:21.228Z] 🦋  error SyntaxError: Unexpected end of JSON input

[2021-01-05T21:25:21.228Z] 🦋  error     at JSON.parse (<anonymous>)

[2021-01-05T21:25:21.228Z] 🦋  error     at jsonParse (.../node_modules/.pnpm/@changesets/cli@2.12.0/node_modules/@changesets/cli/dist/cli.cjs.dev.js:557:17)

[2021-01-05T21:25:21.228Z] 🦋  error     at internalPublish (/.../node_modules/.pnpm/@changesets/cli@2.12.0/node_modules/@changesets/cli/dist/cli.cjs.dev.js:711:14)

[2021-01-05T21:25:21.228Z] 🦋  error     at processTicksAndRejections (internal/process/task_queues.js:93:5)

[2021-01-05T21:25:21.228Z]  ERROR  Command failed with exit code 1.

For more context we publish to a private Jfrog Artifactory server instead of canonical NPM

We were just bit by this on our last publish (curiously our first publish went fine, but once we published more packages it triggered whatever causes this)

[2021-01-05T21:25:14.339Z] > changeset publish

[2021-01-05T21:25:14.339Z]

[2021-01-05T21:25:14.738Z] 🦋  info npm info @skyline/color-settings

[2021-01-05T21:25:14.738Z] 🦋  info npm info @skyline/icons

[2021-01-05T21:25:14.738Z] 🦋  info npm info @skyline/scss

[2021-01-05T21:25:14.738Z] 🦋  info npm info @skyline/tokens

[2021-01-05T21:25:14.738Z] 🦋  info npm info @skyline/vue

[2021-01-05T21:25:14.738Z] 🦋  info npm info @skyline/vuepress-theme-default

[2021-01-05T21:25:17.563Z] 🦋  info @skyline/color-settings is being published because our local version (2.0.0) has not been published on npm

[2021-01-05T21:25:17.563Z] 🦋  warn @skyline/icons is not being published because version 2.0.0 is already published on npm

[2021-01-05T21:25:17.563Z] 🦋  info @skyline/scss is being published because our local version (2.2.1) has not been published on npm

[2021-01-05T21:25:17.563Z] 🦋  info @skyline/tokens is being published because our local version (1.16.1) has not been published on npm

[2021-01-05T21:25:17.563Z] 🦋  info @skyline/vue is being published because our local version (4.3.0) has not been published on npm

[2021-01-05T21:25:17.563Z] 🦋  info @skyline/vuepress-theme-default is being published because our local version (0.4.17) has not been published on npm

[2021-01-05T21:25:17.563Z] 🦋  info Publishing "@skyline/color-settings" at "2.0.0"

[2021-01-05T21:25:17.563Z] 🦋  info Publishing "@skyline/scss" at "2.2.1"

[2021-01-05T21:25:17.563Z] 🦋  info Publishing "@skyline/tokens" at "1.16.1"

[2021-01-05T21:25:17.563Z] 🦋  info Publishing "@skyline/vue" at "4.3.0"

[2021-01-05T21:25:17.563Z] 🦋  info Publishing "@skyline/vuepress-theme-default" at "0.4.17"

[2021-01-05T21:25:21.227Z] error parsing json:

[2021-01-05T21:25:21.228Z] 🦋  error SyntaxError: Unexpected end of JSON input

[2021-01-05T21:25:21.228Z] 🦋  error     at JSON.parse (<anonymous>)

[2021-01-05T21:25:21.228Z] 🦋  error     at jsonParse (.../node_modules/.pnpm/@changesets/cli@2.12.0/node_modules/@changesets/cli/dist/cli.cjs.dev.js:557:17)

[2021-01-05T21:25:21.228Z] 🦋  error     at internalPublish (/.../node_modules/.pnpm/@changesets/cli@2.12.0/node_modules/@changesets/cli/dist/cli.cjs.dev.js:711:14)

[2021-01-05T21:25:21.228Z] 🦋  error     at processTicksAndRejections (internal/process/task_queues.js:93:5)

[2021-01-05T21:25:21.228Z]  ERROR  Command failed with exit code 1.

For more context we publish to a private Jfrog Artifactory server instead of canonical NPM

It's really hard for us to repro this - given this occurs in very specific setups etc. Could you try to debug this? I would try rechecking what exact npm version is being used for publish and would also try out running publish with --dry-run. If you can't repro it locally it might be worth to patch-package changesets apply temporary changes for debugging purposes.

It's really hard for us to repro this - given this occurs in very specific setups etc. Could you try to debug this? I would try rechecking what exact npm version is being used for publish and would also try out running publish with --dry-run. If you can't repro it locally it might be worth to patch-package changesets apply temporary changes for debugging purposes.

Sorry, I should have said we're also using pnpm to publish

Sorry, I should have said we're also using pnpm to publish

Had this same issue and was able to fix it by downgrading from npm7 to latest npm@6

Running into the same issue here when executing yarn changeset publish

Node:15.4.0
npm: 7.0.15
yarn: 1.22.10

However, executing npx changeset publish worked as expected

Had this same issue and was able to fix it by downgrading from npm7 to latest npm@6

Same here, I'd say npm@7 definitely has problems with changesets.

I think that the best way to move forward would be to handle publish using the APIs rather than CLI. This would allow us for more fine-grained control over the input arguments and the result. I'm afraid that I don't have time to work on that right now - but I would be happy to review a PR implementing this.

 npx changeset publish
....
🦋  error SyntaxError: Unexpected end of JSON input
🦋  error     at JSON.parse (<anonymous>)
🦋  error     at jsonParse (/home/user/my-project/node_modules/@changesets/cli/dist/cli.cjs.dev.js:584:17)
🦋  error     at getTokenIsRequired (/home/user/my-project/node_modules/@changesets/cli/dist/cli.cjs.dev.js:632:14)
🦋  error     at processTicksAndRejections (internal/process/task_queues.js:97:5)
🦋  error     at async internalPublish (/home/user/my-project/node_modules/@changesets/cli/dist/cli.cjs.dev.js:715:8)

Got the same error. Turned out the call to npm profile get --json  around cli.cjs.dev.js:632 failed with a 401 error, but the function getTokenIsRequired didn't expect it.
npm ERR! 401 Unauthorized - GET https://registry.npmjs.org/-/npm/v1/user
{
  "error": {
    "code": "E401",
    "summary": "401 Unauthorized - GET https://registry.npmjs.org/-/npm/v1/user",
    "detail": ""
  }
}```

For my use case, I want to publish a package to a private registry on AWS, e.g., `@my-scope/my-package` and I don't have a `registry.npmjs.org` login.

I also just ran into this using the changesets github action.
error parsing json:
🦋  error SyntaxError: Unexpected end of JSON input
🦋  error     at JSON.parse (<anonymous>)
🦋  error     at jsonParse (/home/runner/work/monorepo/monorepo/node_modules/@changesets/cli/dist/cli.cjs.dev.js:584:17)
🦋  error     at internalPublish (/home/runner/work/monorepo/monorepo/node_modules/@changesets/cli/dist/cli.cjs.dev.js:738:14)
🦋  error     at processTicksAndRejections (node:internal/process/task_queues:96:5)
Error: The process '/opt/hostedtoolcache/node/16.1.0/x64/bin/npm' failed with exit code 1
    at a._setResult (/home/runner/work/_actions/changesets/action/master/dist/index.js:86:6638)
    at a.CheckComplete (/home/runner/work/_actions/changesets/action/master/dist/index.js:86:6068)
    at ChildProcess.<anonymous> (/home/runner/work/_actions/changesets/action/master/dist/index.js:86:5102)
    at ChildProcess.emit (events.js:210:5)
    at maybeClose (internal/child_process.js:1021:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
Error: The process '/opt/hostedtoolcache/node/16.1.0/x64/bin/npm' failed with exit code 1

This is a very small test repo for me to evaluate changesets in a publish setting (proof of concept) so i'm happy to send my code over if it will help. I'm using the following:
node: 16.1.0
npm: 7.11.2

@zkochan @Andarist

I think, when users use pnpm, it is safe to use pnpm publish -r in both single-package cases and multi-package repositories.

pnpm publish -r fixed the Unexpected end of JSON input error also in my case (PNPM workspace). However, this does not create git tags, as how changests should do:

It is useful to have git tags of a publish, to allow people looking for the code at that time to find them. We generate tags in git during publish, but you will need to push them back up if you want to make them available. We recomend after publish you run:
git push --follow-tags

(https://github.com/atlassian/changesets/blob/main/docs/command-line-options.md#git-tags)

with this patch
diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index f771824..1577813 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -727,7 +727,8 @@ async function internalPublish(pkgName, opts, twoFactorState) {
     npm_config_registry: getCorrectRegistry()
   };
   let {
-    stdout
+    stdout,
+    stderr,
   } = await spawn__default['default'](publishTool.name, ["publish", opts.cwd, "--json", ...publishFlags], {
     env: Object.assign({}, process.env, envOverride)
   }); // New error handling. NPM's --json option is included alongside the `prepublish and
@@ -735,7 +736,7 @@ async function internalPublish(pkgName, opts, twoFactorState) {
   // some struggles
   // Note that both pre and post publish hooks are printed before the json out, so this works.

-  let json = jsonParse(stdout.toString().replace(/[^{]*/, ""));
+  let json = jsonParse(stdout.toString().replace(/[^{]*/, "") || stderr.toString().replace(/^npm ERR.*$/gm, '').replace(/[^{]*/, ""));

   if (json.error) {
     // The first case is no 2fa provided, the second is when the 2fa is wrong (timeout or wrong words)

I got this output:

🦋  error an error occurred while publishing cem-plugin-async-function: ENEEDAUTH This command requires you to be logged in.
🦋  error You need to authorize this machine using `npm adduser`

yarn run v1.22.10
$ yarn changeset publish
$ /Users/bennyp/Developer/cem-plugins/node_modules/.bin/changeset publish
🦋  info npm info cem-plugin-async-function
🦋  info npm info cem-plugin-copy
🦋  info npm info cem-plugin-jsdoc-example
🦋  info npm info cem-plugin-module-file-extensions
🦋  info npm info cem-plugin-readonly
🦋  info npm info cem-plugin-type-descriptions-markdown
🦋  warn Received 404 for npm info "cem-plugin-async-function"
🦋  warn Received 404 for npm info "cem-plugin-module-file-extensions"
🦋  warn Received 404 for npm info "cem-plugin-copy"
🦋  warn Received 404 for npm info "cem-plugin-type-descriptions-markdown"
🦋  warn Received 404 for npm info "cem-plugin-readonly"
🦋  warn Received 404 for npm info "cem-plugin-jsdoc-example"
🦋  info cem-plugin-async-function is being published because our local version (0.0.1) has not been published on npm
🦋  info cem-plugin-copy is being published because our local version (0.0.1) has not been published on npm
🦋  info cem-plugin-jsdoc-example is being published because our local version (0.0.1) has not been published on npm
🦋  info cem-plugin-module-file-extensions is being published because our local version (0.0.1) has not been published on npm
🦋  info cem-plugin-readonly is being published because our local version (0.0.1) has not been published on npm
🦋  info cem-plugin-type-descriptions-markdown is being published because our local version (0.0.1) has not been published on npm
🦋  info Publishing "cem-plugin-async-function" at "0.0.1"
🦋  info Publishing "cem-plugin-copy" at "0.0.1"
🦋  info Publishing "cem-plugin-jsdoc-example" at "0.0.1"
🦋  info Publishing "cem-plugin-module-file-extensions" at "0.0.1"
🦋  info Publishing "cem-plugin-readonly" at "0.0.1"
🦋  info Publishing "cem-plugin-type-descriptions-markdown" at "0.0.1"
🦋  error an error occurred while publishing cem-plugin-async-function: ENEEDAUTH This command requires you to be logged in.
🦋  error You need to authorize this machine using `npm adduser`
🦋  error an error occurred while publishing cem-plugin-jsdoc-example: ENEEDAUTH This command requires you to be logged in.
🦋  error You need to authorize this machine using `npm adduser`
🦋  error an error occurred while publishing cem-plugin-copy: ENEEDAUTH This command requires you to be logged in.
🦋  error You need to authorize this machine using `npm adduser`
🦋  error an error occurred while publishing cem-plugin-module-file-extensions: ENEEDAUTH This command requires you to be logged in.
🦋  error You need to authorize this machine using `npm adduser`
🦋  error an error occurred while publishing cem-plugin-readonly: ENEEDAUTH This command requires you to be logged in.
🦋  error You need to authorize this machine using `npm adduser`
🦋  error an error occurred while publishing cem-plugin-type-descriptions-markdown: ENEEDAUTH This command requires you to be logged in.
🦋  error You need to authorize this machine using `npm adduser`
🦋  error packages failed to publish:
🦋<EMAIL_ADDRESS>🦋<EMAIL_ADDRESS>🦋<EMAIL_ADDRESS>🦋<EMAIL_ADDRESS>🦋<EMAIL_ADDRESS>🦋<EMAIL_ADDRESS>error Command failed with exit code 1.

which was a fair sight better than Unexpected end of JSON input

For anyone struggling out here:
I also tried setting up changesets for a single package repository and had the same issue as OP.
I also use the publishConfig option in my package.json:
{
  "publishConfig": {
    "access": "public",
    "directory": "dist"
  }
}

First I tried reverting from Node.js 16 to 14 (as 14 uses npm 6 instead of npm 7).
Doing so resulted in a more detailed error message:
🦋  error an error occurred while publishing @n1ru4l/graphql-public-schema-filter: ENOPACKAGEJSON ENOENT: no such file or directory, open '/home/runner/work/graphql-public-schema-filter/graphql-public-schema-filter/dist/package.json'
🦋  error npm can't find a package.json file in your current directory.
🦋  error packages failed to publish:
🦋<EMAIL_ADDRESS>error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Error: The process '/usr/local/bin/yarn' failed with exit code 1
Error: The process '/usr/local/bin/yarn' failed with exit code 1
    at a._setResult (/home/runner/work/_actions/changesets/action/master/dist/index.js:86:6638)
    at a.CheckComplete (/home/runner/work/_actions/changesets/action/master/dist/index.js:86:6068)
    at ChildProcess.<anonymous> (/home/runner/work/_actions/changesets/action/master/dist/index.js:86:5102)
    at ChildProcess.emit (events.js:210:5)
    at maybeClose (internal/child_process.js:1021:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)

Which made me realize I forgot to run my build script 🙃 .
SO I reverted back to Node.js 16 and simply added the build step.
See these two commits:
https://github.com/n1ru4l/graphql-public-schema-filter/commit/c3677b1e55792099c9add97e4b7ce8a06bc6ab40
https://github.com/n1ru4l/graphql-public-schema-filter/commit/a112aee4061bcc46f52e71cffcaba908098ee4ec

I'm still getting this issue with npm7, any new insights?
error parsing json:

🦋  error SyntaxError: Unexpected end of JSON input

🦋  error     at JSON.parse (<anonymous>)

🦋  error     at jsonParse (/home/jenkins/agent/workspace/xSite_xsite-ui_master/node_modules/@changesets/cli/dist/cli.cjs.dev.js:584:17)

🦋  error     at internalPublish (/home/jenkins/agent/workspace/xSite_xsite-ui_master/node_modules/@changesets/cli/dist/cli.cjs.dev.js:738:14)

🦋  error     at processTicksAndRejections (internal/process/task_queues.js:95:5)

The documentation recommends setting NPM_TOKEN env var in CI. This doesn't work. Set NODE_AUTH_TOKEN instead.

@bennypowers As we already discussed and found out, you actually have to set both NPM_TOKEN and NODE_AUTH_TOKEN
¯_(ツ)_/¯

I'm also seeing this. Unexpected end of JSON input
Seems like input is empty after running the pnpm command with these args
[
  'publish',
  '/x/repos/pnpm-workspaces/src/packages/package-d',
  '--json',
  '--access',
  'restricted',
  '--tag',
  'latest',
  '--no-git-checks'
]

Then the json parser breaks because the command is empty.
🦋  error SyntaxError: Unexpected end of JSON input
🦋  error     at JSON.parse (<anonymous>)
🦋  error     at jsonParse (/x/repos/pnpm-workspaces/node_modules/.pnpm/@changesets+cli@2.16.0/node_modules/@changesets/cli/dist/cli.cjs.dev.js:585

The package.json for package-d is correct...
Has anyone found a fix for this issue?

For me, I had to add the following to my package.json's:
  "publishConfig": {
    "access": "public"
  }

Answer from: https://stackoverflow.com/a/53478078

I also ran into this issue when trying to publish my pnpm monorepo with changesets. There seem to be at least two issues here:

NPM commands are being run with the --json flag. Unfortunately a regression in NPM 7 (now the default version) means that both structured and unstructured output is all muxed onto stderr. This means the stdout is an empty string which fails to be parsed as JSON.
pnpm does not support the --json flag at all. However there are various places (example) where pnpm is called and the stdout is expected to contain JSON output.

On the first issue, I don't think there's much that can be done until NPM fixes the glaring regression.
I wouldn't mind trying to patch the second issue. I think the best thing would be to special-case pnpm - i.e. listen for the exit code of the pnpm process and, upon failure, pack the entire stdout/stderr output into the error. Would appreciate some guidance though.

pnpm does not support the --json flag at all.

@rossng where did u get this info? do u know of any pnpm + other stuff combination that fails to use --json with pnpm? i was just testing it and it seems to work. pnpm simply forwards almost all arguments to the npm (and it uses npm's CLI under the hood for publishing) so in a sense this should "just work". I've tested this manually with pnpm v6 and verified the code for v3, v4, v5, and v6 - they all do roughly the same thing when it comes to this args forwarding to npm publish.

There are news? Now I have the same error...

@abdonrd I'm trying to figure out the proper solution for most of the similar publishing issues to fix this once and for all. Stay tuned

@Andarist I think you are right in the case of publishing. I had noticed that pnpm didn't support --json in the general case - that's what my comment was based on. However, I just had a quick look at the pnpm code and it does appear to forward anything in argv to npm when calling publish.
Glad to hear you are working on this - happy to help/test if needed.

I had the same issue earlier today and it happened for two reasons.
Reason One
There was a package that was set to "private": true in the package.json file. This was unintentional. I attempted to fix this mistake in a recent release by updating the package.json. The problem is that the package already had multiple CHANGELOG.md entries and as a result, changesets attempts to update the package with a PUT rather than publish with a POST request. Since the package doesn't actually exist on the registry this causes an error and npm doesn't respond with json.
Fix: Make sure there is only one entry in your changelog file before publishing a package for the first time.
Reason Two
A package I was trying to publish seemed available, but it actually causes an error response from npm when trying to publish. The naming is too similar to another package that already exists. When an error happens the npm publish command doesn't return json and the json cannot be parsed.
Fix:  Rename the package and retry.
Suggestions
I think the main problem is that changesets assumes that npm publish will always return valid json which is not the case. As a result the actual error response is hidden and all we see is an invalid json message.
https://github.com/atlassian/changesets/blob/fe8db7500f81caea9064f8bec02bcb77e0fd8fce/packages/cli/src/commands/publish/npm-utils.ts#L67
My suggestion is that this jsonParse call should be wrapped in a try catch and when failing it should log the original reponse from npm. This way it will be much easier to identify what the problem is.

Yep, already pushed out a change like this a couple of hours ago 😉 :
https://github.com/atlassian/changesets/commit/89a70f9d6702740c8b4c7903faefb8c7286bff20
Need to self-review and retest this before publishing a PR.
Thank you also for other comments - i will take a deeper look into everything you have mentioned

I've created a pull request that attempts to fix the issues mentioned here. I will setup snapshot releases for this PR soon-ish but in the meantime I would love to ask if there are any people willing to test this stuff out in their projects.

Does anyone have solutions for this lol

I managed to get the github action to work using this setup.
name: Release

on:
  push:
    branches:
      - main

concurrency: ${{ github.workflow }}-${{ github.ref }}

env:
  GITHUB_TOKEN: ${{ secrets.GH_RELEASE_TOKEN }}
  NPM_TOKEN: ${{ secrets.GH_RELEASE_TOKEN }}
  NODE_AUTH_TOKEN: ${{ secrets.GH_RELEASE_TOKEN }}

jobs:
  release:
    name: Release
    runs-on: ubuntu-latest
    steps:
      - name: Checkout Repo
        uses: actions/checkout@v3

      - name: Setup Node.js 18.x
        uses: actions/setup-node@v3
        with:
          node-version: 18.x
          cache: 'npm'
          token: ${{ secrets.GH_RELEASE_TOKEN }}
          registry-url: 'https://npm.pkg.github.com'

      - name: Install Dependencies
        run: npm ci

      - name: Create Release Pull Request or Publish to npm
        id: changesets
        uses: changesets/action@v1
        with:
          publish: npm run release


🐛[BirdNET-Pi] Species Stats not found

Description
All I get on the Species Stats is "not found", no other errors.
Reproduction steps
1. Go to 'BirdNet'
2. Click on 'Species Stats'
4. See error

Addon Logs
The in-app log shows "Not found"
There are no reference to it in the system logs.

Architecture
amd64
OS
HAos

Hi, it doesn't work for the moment with ingress ; you should access with ip:port for it to work

Also true for the web log viewer currently. Works fine hitting the port in a browser. 👍


url-pattern does treats fullstops in urls different to express.

The URL /api/v1/user/test.name/ would be captured by the expressjs route /api/v1/user/:id/ but is not captured by the url-pattern /api/v1/user/:id/.
The resulting regex should include the full stop as a valid char. \/api\/v1\/user\/([a-zA-Z0-9-_ % \.]+)\/

I guess the intention may not be to copy expresses url patterns, in that case feel free to close it, it says nowhere it does, I was just hoping for a module that did this.
Anyhow the regex I suggested breaks the major/minor version example.

yes, my intention for url-pattern is not to copy the express behaviour exactly.
i understand your requirement.
there was another issue #6 that asked for named segments to stop consuming at full stops.
that requirement and yours mutually exclude each other.
different users want different charsets to be consumed by named segments !
for that reason i made that charset, among other things, configurable to suit each users needs.
this test case configures the url-pattern compiler to exhibit the behaviour you want by adding the full stop to the set of characters consumed by named segments:
https://github.com/snd/url-pattern/blob/2c3f1aed5c4dbde9e5393d57c48e64065e5a49c8/test/url-pattern.coffee#L416
if you want to know more about modifying the compiler: https://github.com/snd/url-pattern#modifying-the-compiler
you can also change the charset for all instances of url-pattern at once:
UrlPattern.Compiler.prototype.segmentValueCharset = 'a-zA-Z0-9-_ %.;

hope i could help.

That's great really helpful. Thanks.

glad i could help!
looking at the test again i noticed that it contained an unnecessary line.
see this improved minimal test case:
https://github.com/snd/url-pattern/blob/413f16176c51c61f78c1d957a15172fa08a7a0f5/test/url-pattern.coffee#L414


I cannot see reusable item of other pages

if I create new page, I don't see the reusable block menu but only inside the page where I create them.

@skacco  did you find a solution?


Cannot select brushes anymore via left click (In Place / Edit modes)

For some reason during after version upgrades (multiple, I haven't payed attention to this for a while) I'm unable to select brushes anymore via left clicks.
Only models / gameobjects behind brushes are selected. RealtimeCSG is enabled in scene view.
This is on Unity 2019.2.0f1 and RealtimeCSG v.1557.
Not a big deal, but a little bit of a nuisance. Is there something I'm missing?

This happens in "Place" mode. In surface mode brushes are selected just fine.

Is the problem fixed if you switch between edit modes and back again?

Is the problem fixed if you switch between edit modes and back again?

Nope, it still selects objects behind brushes in place / edit mode.
Surface mode selects them correctly.
So its related to both "Place" and "Edit" modes.

The objects you're trying to select, are these brushes or some other kind of objects? if so, what kind of objects?

The objects you're trying to select, are these brushes or some other kind of objects? if so, what kind of objects?

Brushes. Behind those brushes are default objects. (Meshes, terrain etc)

So this happens on renderers behind the brushes? I'll take a look

I am unable to reproduce this issue. OP has not responded in several months, so I am going to go ahead and close it.


Module 2.2 Assignment

👋 for this assignment, if you'd like to try again, please include a screenshot of merging on the command line using git fetch and git merge.

👋 for this assignment, if you'd like to try again, please include a screenshot of merging on the command line using git fetch and git merge.
@arelia done !

@arelia hi! i don't have any news, you must be very busy. Could you look into the remaining issues ? Thank you!


softSkills section working backwards?

Expected Behavior
In the softSkills section, the color indicator should go around and stop at the defined percentage. Instead, it is now going around and leaving the remainder only.

Current Behavior
Now the color starts halfway around, goes to the percentage defined, but then ... inverts so that the only color left showing is the remainder. So if you have something at 100$, it shows nothing.

Possible Solution

Steps to Reproduce

Screenshots

Browsers Affected

[X] Chrome
[ ] Firefox
[ ] Edge
[X] Safari 11
[X] Safari 18
[ ] Safari 10
[ ] IE 11

Detailed Description

Probably some CSS issue. Try updating to latest version.

I'm on the latest version. Still happening.

@davidgs Are you still facing the issue? I see the animation is working fine on your portfolio.


Net Port health status metric

Is your feature request related to a problem? Please describe.
Feature request
Describe the solution you'd like
A possibility to collect the health status of a port which can be degraded because of the L2_reachability which was implemented in ONTAP 9.13.1
https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Native_VLAN_ports_show_degraded_after_upgrade_to_ONTAP_9.13.1
Additional context
With that we can avoid issued prio to a ONTAP upgrade or missconfiguration of a switch

That's a useful feature request, @BrendonA667.  Thanks for the suggestion.
Here are a few questions to help us add this feature:

Which dashboard should include the health status of a port? Should we add it to the Health dashboard or the Network dashboard? Do you have any preference?
It appears that the port status is available for both Ethernet and Fibre Channel ports. Would you like to see the health status for both types of ports?

Hi @Hardikl
About the dashboard I would say in the Network dashboard. Main reason it is not a direct issue for the running system.
About Ethernet and FC. Since we only have Ethernet I cannot talk for FC but for the folks who use FC it would be nice :)

Verified in 24.11 ddb97c57


tags-on-commits-list: Cannot read properties of undefined (reading 'pathname')

Description
TypeError: Cannot read properties of undefined (reading 'pathname')
    at getCommitHash (chrome-extension://hlepfoohegkhhmjieoechaddaejaokhf/assets/refined-github.js:6125:35)
    at init (chrome-extension://hlepfoohegkhhmjieoechaddaejaokhf/assets/refined-github.js:7411:134)
    at chrome-extension://hlepfoohegkhhmjieoechaddaejaokhf/assets/refined-github.js:3119:28
    at chrome-extension://hlepfoohegkhhmjieoechaddaejaokhf/assets/refined-github.js:3115:64
    at Array.map (<anonymous>)
    at chrome-extension://hlepfoohegkhhmjieoechaddaejaokhf/assets/refined-github.js:3115:45
    at runFeature (chrome-extension://hlepfoohegkhhmjieoechaddaejaokhf/assets/refined-github.js:3116:10)
    at setupPageLoad (chrome-extension://hlepfoohegkhhmjieoechaddaejaokhf/assets/refined-github.js:3131:43)
    at async chrome-extension://hlepfoohegkhhmjieoechaddaejaokhf/assets/refined-github.js:3156:11

How to replicate the issue + URL
https://github.com/kubernetes-sigs/cri-tools/commits/release-1.31
Extension version
24.8.13
Browser(s) used
Version 127.0.6533.100 (Official Build) (arm64)
Version 127.0.6533.120 (Official Build) (arm64)
Token ⚠

[X] I set a token in the options page. I understand that some features require a token to work.

Duplicate of https://github.com/refined-github/refined-github/issues/7682


Make storing a run not wait until storage is complete

With the added statelessness and the complexity of parsing a report ZIP it should be done so that this parsing does not hang one thread of the web server pool, and neither does keep a socket open. The user could time out while the server is generating the return value of massStoreRun, which could have unforeseen consequences.
Ideas:

Make the Webserver process pooled instead of thread pool. This could be a big help in alleviating for the GIL.
massStoreRun should start a direct, detached subprocess which is internal to the server host. This subprocess could independently handle the parsing and storing of the result ZIP. This way the user's connection is closed once the ZIP is dispatched, and instead of waiting for the reply in the same connection, it could be made so that the client actively pings the server to tell them when the build is successfully stored, or failed. This would require a change on the API and handling, and also to introduce a little bit of interprocess communication, or saving intermittent state data to the database (presumably into a new table which is recommended to be in the MEMORY backend).

>mfw this has been an issue since 2018 and not just 2022 like originally thought???
Okay, while not exactly matching the design that was proposed here, #3672 is a better thought-out version of this issue without the need for GIL changes, detached subprocesses, etc.


arm: create COS_PERSISTENT instead of COS_OEM

Add a cloud-init also to automatically expand the COS_PERSISTENT
partition on first boot.
Tied to #930
Still testing it
Signed-off-by: Ettore Di Giacinto<EMAIL_ADDRESS>

Cool, with this you are not loosing OEM functionality, you can still plug a USB having the OEM label with some custom cloud init data and it would be executed.
Note you are forgetting to update examples/odroid-c2/files/system/oem/01_layout.yaml

Good catch, I actually forgot to commit its deletion :sweat:

Oh wait, I did commit it, I've deleted both layout files as now cOS defaults should be good

This might need https://github.com/rancher-sandbox/cos-toolkit-docs/pull/67

seems adding rd.cos.oemlabel=COS_OEM to bootargs doesn't help. Still dropping to emergency shell  from dracut

ok, seems to boot when creating an COS_OEM (even from an .img file). So looks like entries listed in VOLUMES in layout.env, once specified are mandatory. I'll create a layout file to disable oem entirely

@davidcassany needs a re-review please as things changed slightly. It looks like the OEM partition is required if specified in VOLUMES, although would make sense to offer a way to mount certain paths 'optionally' like COS_OEM, in that case we can still support the scenarios of plugging an USB stick and load cloud config files from there.
Is there a way to override the default ? by looking at the code at a quick glance I didn't noticed, but not sure if I might have missed something

ok so after discussing with @davidcassany OEM gets mounted by default so there is no need to specify it in VOLUMES, mount will be attempted at boot even if not specified there. That means we can't rely on cOS defaults for ARM here, hence why the specific cloud-config file which overrides the layout

ok now booting works. However automatic resizing of COS_PERSISTENT it doesn't. Fails silently here with an exit 2. I'd say to merge this and create a follow-up for the partition resizing as it is out of purpose (and can be workarounded easily after image creation too).


Rename model name

Rename model name for InceptionResnetV2

It's V1 not V2. Can be confirmed by https://github.com/davidsandberg/facenet/tree/master

I thought you use InceptionResnetV2 for Facenet512d
https://github.com/davidsandberg/facenet/blob/master/src/models/inception_resnet_v2.py


Do you provide deployment guidance and images in the K8S environment?

If this doesn’t look right, choose a different type.
Do you provide deployment guidance and images in the K8S environment?
Describe your ideas

Do you provide deployment guidance and images in the K8S environment?
Solution

It should be possible. Almost all of our internal deployments are based on K8S. Due to the differences between internal and external environments, there is some workload.

when is this feature will push?


 Sundials is a different repository from OrdinaryDiffEq.jl. It's a completely different set of solvers and in fact it's a set of wrappers to the C/Fortran SUNDIALS library. As such, it won't work with Julia GPU kernels. In theory we could wrapper the CUDA N_Vector and pass pointers or something, but at this time it's not in scope for the people developing the library.

There is significant improvement in building binaries that can use the CUDA stack, which should pave the path for this if someone wants to work on it.

@abillscmu if you are still interested.
@ViralBShah is support for distributed computing with Sundials within scope?

I believe there is now a recipe for building MPI libraries in BinaryBuilder - so it is certainly possible. Should be a separate JLL whenever we decide to do it.


Consolidation of track options

Description

What was changed in this pull request?

Some options of horizontal tracks were missing in their vertical counterparts.

Why is it necessary?

Fixes #883
Checklist

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

Tests are passing. For some reason, it is not updated here.


Use env GITEA_RUNNER_REGISTRATION_TOKEN as global runner token

fix #23703
Now when Gitea start, it reads GITEA_RUNNER_REGISTRATION_TOKEN/GITEA_RUNNER_REGISTRATION_TOKEN_FILE to use that value as global runner token.
If users would like to deploy stateless Gitea/Runner instances, they could simply do this:
openssl rand -hex 24 > /some-dir/runner-token

export GITEA_RUNNER_REGISTRATION_TOKEN_FILE=/some-dir/runner-token
./gitea

export GITEA_RUNNER_REGISTRATION_TOKEN_FILE=/some-dir/runner-token
./act_runner

@lunny @Zettat123 would you like to update the document and examples?

@lunny @Zettat123 would you like to update the document and examples?

document: https://gitea.com/gitea/docs/pulls/132
example: https://gitea.com/gitea/act_runner/pulls/630


How does the L515 transmit for a distance of 20m?

Required Info

Camera Model
{ L515 }

Firmware Version
(Open RealSense Viewer --> v2.50.0)

Operating System & Version
{Win 10

Kernel Version (Linux Only)
(e.g. 4.14.13)

Platform
PC

SDK Version
{ legacy / 2.. }

Language
{C/C#/labview/nodejs/opencv/pcl/python/unity }

Segment
{Robot/Smartphone/VR/AR/others }

Issue Description
<Describe your issue / question / feature request / etc..>
We want the L515 to transmit over a distance of 20m, but it seems that the USB3.0 extension cable is not stable. Can we use a more stable method (such as network cable) for long-distance connection?

Hi @liyuan1a  Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.


Installation of the app freezes in diferent times

I downloaded the NT .exe 0.10.8 and after installing the app I always get the same problem.
When i try to open it for the first time starts downloading all the necessary and at some point the installation freezes and does not continue.
Here I leave one of those freezes:

I have tried everything I could think of to fix it:
Firewall, or antivirus problems
vc++ x86 versions
Reinstalling
As administrator
etc...
No clue why it does not work.
If anyone knows anything would be much appriciated.

As a workaround you can try manually installing the noita mod:
download the current main-branch zip https://github.com/Noita-Together/noita-together/archive/refs/heads/main.zip
from the zip, copy the two folders in 'noita_mod' to your noita installation's mods folder (for steam on windows, usually C:\program files (x86)\steam\steamapps\common\noita\mods
rename the 'core' folder to 'noita-together' and the 'nemesis' folder to 'noita-nemesis'. Delete those folders first if they already exist

Ok i did it and worked, idk why the app did not work by itself.
Thanks for the help.
Guess that my Windows 11 has some issue.

Along with the copying of the mods, passing --nt-noupdate seemed to be required to get the launcher to get past this problem.

https://github.com/Noita-Together/noita-together/issues/103 has some useful steps for resolving for now


Compile error found in "samples/snippets"

I followed the Getting started with Cloud Spanner in Java and did the following:
$ git clone https://github.com/googleapis/java-spanner.git
$ cd java-spanner/samples/snippets
$ mvn package

However, the compilation failed. Note that I did the same thing a while ago and it did work. So I guess this is caused by recent releases that include incompatible changes?
FYI, the errors are:
[INFO] -------------------------------------------------------------
[WARNING] COMPILATION WARNING :
[INFO] -------------------------------------------------------------
[WARNING] /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/TracingSample.java: /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/TracingSample.java uses or overrides a deprecated API.
[WARNING] /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/TracingSample.java: Recompile with -Xlint:deprecation for details.
[INFO] 2 warnings
[INFO] -------------------------------------------------------------
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/CreateBackupWithEncryptionKey.java:[30,43] package com.google.cloud.spanner.encryption does not exist
[ERROR] /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/RestoreBackupWithEncryptionKey.java:[26,32] cannot find symbol
  symbol:   class Restore
  location: package com.google.cloud.spanner
[ERROR] /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/RestoreBackupWithEncryptionKey.java:[30,43] package com.google.cloud.spanner.encryption does not exist
[ERROR] /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/CreateDatabaseWithEncryptionKey.java:[28,43] package com.google.cloud.spanner.encryption does not exist
[ERROR] /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/CreateBackupWithEncryptionKey.java:[72,30] cannot find symbol
  symbol:   variable EncryptionConfigs
  location: class com.example.spanner.CreateBackupWithEncryptionKey
[ERROR] /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/RestoreBackupWithEncryptionKey.java:[62,11] cannot find symbol
  symbol:   class Restore
  location: class com.example.spanner.RestoreBackupWithEncryptionKey
[ERROR] /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/RestoreBackupWithEncryptionKey.java:[63,9] cannot find symbol
  symbol:   method newRestoreBuilder(com.google.cloud.spanner.BackupId,com.google.cloud.spanner.DatabaseId)
  location: variable adminClient of type com.google.cloud.spanner.DatabaseAdminClient
[ERROR] /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/RestoreBackupWithEncryptionKey.java:[66,30] cannot find symbol
  symbol:   variable EncryptionConfigs
  location: class com.example.spanner.RestoreBackupWithEncryptionKey
[ERROR] /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/RestoreBackupWithEncryptionKey.java:[92,17] cannot find symbol
  symbol:   method getEncryptionConfig()
  location: variable database of type com.google.cloud.spanner.Database
[ERROR] /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/CreateDatabaseWithEncryptionKey.java:[60,9] cannot find symbol
  symbol:   method newDatabaseBuilder(com.google.cloud.spanner.DatabaseId)
  location: variable adminClient of type com.google.cloud.spanner.DatabaseAdminClient
[ERROR] /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/CreateDatabaseWithEncryptionKey.java:[61,30] cannot find symbol
  symbol:   variable EncryptionConfigs
  location: class com.example.spanner.CreateDatabaseWithEncryptionKey
[ERROR] /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/CreateDatabaseWithEncryptionKey.java:[64,9] method createDatabase in interface com.google.cloud.spanner.DatabaseAdminClient cannot be applied to given types;
  required: java.lang.String,java.lang.String,java.lang.Iterable<java.lang.String>
  found:    com.google.cloud.spanner.Database,java.util.List<java.lang.String>
  reason: actual and formal argument lists differ in length
[ERROR] /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/CreateDatabaseWithEncryptionKey.java:[85,26] cannot find symbol
  symbol:   method getEncryptionConfig()
  location: variable createdDatabase of type com.google.cloud.spanner.Database
[INFO] 13 errors
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4.263 s
[INFO] Finished at: 2021-04-07T11:46:56-07:00
[INFO] Final Memory: 38M/224M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project spanner-snippets: Compilation failure: Compilation failure:
[ERROR] /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/CreateBackupWithEncryptionKey.java:[30,43] package com.google.cloud.spanner.encryption does not exist
[ERROR] /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/RestoreBackupWithEncryptionKey.java:[26,32] cannot find symbol
[ERROR]   symbol:   class Restore
[ERROR]   location: package com.google.cloud.spanner
[ERROR] /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/RestoreBackupWithEncryptionKey.java:[30,43] package com.google.cloud.spanner.encryption does not exist
[ERROR] /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/CreateDatabaseWithEncryptionKey.java:[28,43] package com.google.cloud.spanner.encryption does not exist
[ERROR] /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/CreateBackupWithEncryptionKey.java:[72,30] cannot find symbol
[ERROR]   symbol:   variable EncryptionConfigs
[ERROR]   location: class com.example.spanner.CreateBackupWithEncryptionKey
[ERROR] /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/RestoreBackupWithEncryptionKey.java:[62,11] cannot find symbol
[ERROR]   symbol:   class Restore
[ERROR]   location: class com.example.spanner.RestoreBackupWithEncryptionKey
[ERROR] /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/RestoreBackupWithEncryptionKey.java:[63,9] cannot find symbol
[ERROR]   symbol:   method newRestoreBuilder(com.google.cloud.spanner.BackupId,com.google.cloud.spanner.DatabaseId)
[ERROR]   location: variable adminClient of type com.google.cloud.spanner.DatabaseAdminClient
[ERROR] /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/RestoreBackupWithEncryptionKey.java:[66,30] cannot find symbol
[ERROR]   symbol:   variable EncryptionConfigs
[ERROR]   location: class com.example.spanner.RestoreBackupWithEncryptionKey
[ERROR] /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/RestoreBackupWithEncryptionKey.java:[92,17] cannot find symbol
[ERROR]   symbol:   method getEncryptionConfig()
[ERROR]   location: variable database of type com.google.cloud.spanner.Database
[ERROR] /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/CreateDatabaseWithEncryptionKey.java:[60,9] cannot find symbol
[ERROR]   symbol:   method newDatabaseBuilder(com.google.cloud.spanner.DatabaseId)
[ERROR]   location: variable adminClient of type com.google.cloud.spanner.DatabaseAdminClient
[ERROR] /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/CreateDatabaseWithEncryptionKey.java:[61,30] cannot find symbol
[ERROR]   symbol:   variable EncryptionConfigs
[ERROR]   location: class com.example.spanner.CreateDatabaseWithEncryptionKey
[ERROR] /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/CreateDatabaseWithEncryptionKey.java:[64,9] method createDatabase in interface com.google.cloud.spanner.DatabaseAdminClient cannot be applied to given types;
[ERROR]   required: java.lang.String,java.lang.String,java.lang.Iterable<java.lang.String>
[ERROR]   found:    com.google.cloud.spanner.Database,java.util.List<java.lang.String>
[ERROR]   reason: actual and formal argument lists differ in length
[ERROR] /tmp/java-spanner/samples/snippets/src/main/java/com/example/spanner/CreateDatabaseWithEncryptionKey.java:[85,26] cannot find symbol
[ERROR]   symbol:   method getEncryptionConfig()
[ERROR]   location: variable createdDatabase of type com.google.cloud.spanner.Database
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

@skuruppu
The problem is that the samples/snippets project is using the Spanner client library version from the Google libraries bom. That is version 5.1.0. Encryption was added in version 6.x. As far as I can tell this was probably caused by the following:

The samples for Database and Backup encryption was merged a little while ago.
That PR probably used a manually set version locally during development, which meant that it wasn't noticed during development.
The CI environment currently does not execute any (integration) tests on the samples as these take too long. Instead, there are (as far as I know) tests executed only on nightly builds. I would expect those nightly builds currently also to be broken. The PR was therefore also green on CI.

I think the best thing to do here is to:

Revert #989 for now and add it back once Spanner client library 6.x is available in the BOM.
Change the build script to at least do a compile of the samples (but perhaps we should also add a couple of unit tests to the samples just to add an extra level of certainty).

The samples dependencies have been updated and should compile now in the latest release: https://github.com/googleapis/java-spanner/pull/1046


Red alert in Foundry

Describe the bug
A Foundry error appears in red color
Failed to connect to database "ActiveAuras.Active Auras Auras": Database is not open
Failed to connect to database "ActiveAuras.Active Auras Zone Actors": Database is not open
Failed to connect to database "ActiveAuras.Active Auras Macros": Database is not open
Foundry v11. 307
Active-Auras 0.7.5
To Reproduce
Just install the Active-Aura module, and go to modules section, warnings
Screenshots
If applicable, add screenshots to help explain your problem.

Environment:

Foundry v11. 307

Please can you uninstall and reinstall the module, something has gone wrong during install.

It seems that this was the error. The alert has disappeared.
Thx


Add user accounts and authentication

This needs to happen so the application can be deployed publicly.  This will need to be worked in conjunction with the HTML client application.


Feature request: before throwing OutOfRangeError, dequeue the rest samples from a queue

When using a FIFOQueue as the input for a pipeline, we often encounter the case that epoch_size % batch_size == M where M != 0. It will lead the following issue:
if we would like to evaluate our model with the entire validation dataset, we cannot test the last M samples before getting the exception OutOfRangeError if we set num_epoches to 1. Even if we set num_epoches to None to avoid OutOfRangeError, we cannot exactly get the result because of the indivisibility issue.
So what I can think of is, we need a feature like this:

if num_epoches is set to None, we need to dequeue the rest M samples from the queue before every epoch is finished. For example, a dataset's size is 10, saying they are [a,b,c,d,e,f,g,h,i,j], and batch_size is 3, the size of dequeued samples would be [a,b,c], [d,e,f], [g,h,i], [j], [a,b,c], ...;
if num_epoches is set to 1, we need to dequeue the rest M samples from the queue before throwing OutOfRangeError.For the above example, the result would be [a,b,c], [d,e,f], [g,h,i], [j], OutOfRangeError.

@mrry I'm not sure how DequeueMany and epochs are supposed to interact with FIFOQueues.  Seems to me like changing semantics like this is likely to break a lot of other people's code?

This is what FIFOQueue.dequeue_up_to(n) does. The various wrapper functions for batching have an allow_small_batch optional argument that use this op internally.

@wangchuan Does this solve your problem?

I tried allow_small_batch option, it meets part of my requirement, i.e. if num_epoches is set to an integer, the last iteration will dequeue the rest samples before throwing OutOfRangeError. However, if num_epoches is set to None, I think the results would be [a,b,c], [d,e,f], [g,h,i], [j,a,b], [c,d,e], ... instead of my expecting [a,b,c], [d,e,f], [g,h,i], [j], [a,b,c], .... Am I correct?

You're correct. The queue-based input pipelines (such as tf.train.batch() etc.) don't support any form of intermediate punctuation, so only the final batch will be smaller if the dataset size is not divisible by the batch size.
Can you explain your use case for having the intermediate smaller batch? As far as I can tell, the smaller batch isn't a reliable way of detecting the transition from one epoch to the next.

Closing this due to lack of response. I doubt we'll implement this in the current input pipeline scheme, which is currently being redesigned, but it would be great if you could still share your use case so that we can take it into account.


Fix typo in README

Hi NextLS folks,
I'm working on integrating NextLS into Zed, and along the way I tripped over a tiny typo in the NextLS README. Thought I'd fix the problem while I'm at it.
Hope y'all have a great week :)

Thank you! I forgot to update that after the extension settings were refactored.


Add documentation for AbstractWalker and Performance best practices

PR checklist

[x] Documentation update

Addresses: https://github.com/palantir/tslint/pull/2093#issuecomment-277340355
What changes did you make?
Add documentation on how to use WalkContext and AbstractWalker.
Add a section for migrating from RuleWalker.
Add a page of performance tips.
Is there anything you'd like reviewers to focus on?
I didn't know where to put this, so I just created new .md files. This needs to be integrated somewhere.
Feedback is very appreciated. Maybe the wording can use some love, because I'm not a native English speaker.

@ajafff made some changes. Sorry, I had to push directly to your branch since it wouldn't let me create a pull request.

@nchen63 thanks for the rewrite. It looks much better now. I only needed to add some minor fixes.
I also added more content to performance.md

This still needs to be integrated into the existing docs somehow / somewhere.
I don't know how that works, so I leave it up to you.


changed static file options to disable caching

what is says on the tin.

Does this apply to non-static files also, like Posts and the front page?


Transform-origin should be center

Transform origin for canvas manipulations should be the center of the image (for sane scaling), however this breaks the dragging bounds. Have to either fix the bounding function, or calculate offsets for every animationFrame to keep centered when scaling an image.
The latter might be nice only because it would leave the door open for pinch-to-zoom-context in the future (ie: zoom into the area of an image pinched, rather than just from center).

Turns out this is a large concern, because any scaled-in image will gradually drift out of the bounds as you resize the viewport. Transform center should fix this.

This depends on what we do with the crop tools in #37

Fixed in https://github.com/SimplaElements/simpla-img/releases/tag/v1.0.0


What is changed by the tare calibration of D435

Hi.
I know there are some calibrations,including tare calibration,on-chip calibration,dynamic calibration and so on.I have a D435 which  is unacceptable in get_distance.Therefore,I want to calibrate it to solve this problem.For example,I measured a box which distance is 2.0 meters，however the D435 told me the distance is 1.8 meters.
Firstly,I chose the on-chip calibration.But,the health check is told me that I don't need to calibrate. I remained to calibrate it by the "RealSense_D400 _Custom_Calib_Paper". In spite of this, there is no changes after the D435 is calibrated. It told me the distance is still 1.8 meters.
Secondly, I chose the tare calibration. And this result of D435 is almost 2.0 meters.However,I find a problem about the calibration. The properties of intrinDepthFrame,intrinColorFrame, extrinDepth2Color seemed unchanged by calibration. Therefore, I wonder what happened by  tare calibration or on-chip calibration?
Furthermore,I want to konw how to reset to factory default.Is it hard reset by intel realsense viewer?

Further information about on-chip and tare calibration can be found in the link below.
https://github.com/IntelRealSense/librealsense/issues/5838
It describes how Tare "is for correcting the accuracy. You have to point at a flat wall where you know the ground-truth distance to the center point of the image. It will then adjust the calibration parameters accordingly".
You can also calibrate the 400 Series cameras using a tool called the Dynamic Calibrator, which can provide an advanced-level calibration.  It will only calibrate the extrinsics, but this should be sufficient to correct mis-calibration problems in most cases.
https://downloadcenter.intel.com/download/29618/Intel-RealSense-D400-Series-Dynamic-Calibration-Tool
If you are a Linux user, page 14 onward of the user guide for the tool explains how to install in on Linux.
https://dev.intelrealsense.com/docs/intel-realsensetm-d400-series-calibration-tools-user-guide
The Dynamic Calibrator software includes a program called CustomRW that can be used to perform a "gold reset" of the camera to its factory configuration.  After launching CustomRW, you can initiate a gold reset by entering the command below.:
Intel.Realsense.CustomRW.exe -g

Yes.I point at a flat wall to the center point of the image.The free Dynamic Calibrator is only calibrate the extrin. I don't sure it will help me to calibrate the D435.

In 99% of cases it is sufficient to just calibrate extrinsics, as these have the most effect on the output image.   There is an OEM version of the software that can calibrate both intrinsics and extrinsics that comes with the $1500 US dollar OEM Calibration Target system sold by Intel.
https://store.intelrealsense.com/buy-intel-realsense-d400-cameras-calibration-target.html
This is aimed at customers such as engineering departments and factories though, and the free calibrator usually provides a very good re-calibration.

Thank you for your reply and for its speed. The D435 camera got a high depth quality by the  Dynamic Calibrator.
The calibrated parameters after dynamic calibrator is shown here:

However the result after the tare calibration is shown here:

As we can see,the intrintDepth and extrinDepth2Color are changed.I still don't konw what calibrated parameters are chaged by Dynamic Calibrator or Tare Calibrator separately.

Section 2.1 of the user guide for the Dynamic Calibrator software on page 12 explains which extrinsics can be altered by calibration (the free non-OEM version of the software does not calibrate intrinsics):

My understanding is that Tare is focused on improving the accuracy of the camera rather than calibrating it (which is the role of the On-Chip self calibration function).

Case closed due to no further comments received.


⚠ Jenkins Plugins Artifactory has degraded performance

In 20bf99e, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 2840 ms

Resolved: Jenkins Plugins Artifactory performance has improved in acb15d6 after 30 minutes.


icon changed

icon changed successfully by compiling the app to .exe format
added 'requirements.txt' file with all the dependencies to run and compile
NOTE: all the static files need to be copied to output folder after successful compilation .
compiled file will be present in the path
/output/main/main.exe

I can't seem to run the executable. It's in the ..\output\main.exe right? It's not running on my end. I've been thinking of refactoring the folder structure to make it easier to convert to an exe.


Compiling MDX in browser?

Is it possible to use xdm to compile MDX in the browser in order to build something like the MDX Playground?
I tried calling xdm.compile on the browser, but received a process is not defined error.

oops, the error I encountered was due to a misconfiguration of webpack on my end. 🤦


iOS 12 ---> missing current color UIView above slider?

I've noticed that on iOS12 little preview drag-UIView  is missing?

I have fixed this with .layoutIfNeeded.


Fix asset promise all not resolve

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

Codecov Report
Base: 36.61% // Head: 36.63% // Increases project coverage by +0.02% :tada:

Coverage data is based on head (c436ff6) compared to base (4c44420).
Patch coverage: 92.85% of modified lines in pull request are covered.

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

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1300      +/-   ##
==========================================
+ Coverage   36.61%   36.63%   +0.02%
==========================================
  Files         348      348
  Lines       16672    16679       +7
  Branches     2621     2623       +2
==========================================
+ Hits         6104     6111       +7
  Misses      10021    10021
  Partials      547      547

Impacted Files
Coverage Δ

packages/core/src/asset/AssetPromise.ts
86.20% <92.30%> (+1.59%)
:arrow_up:

packages/loader/src/gltf/GLTFUtil.ts
1.63% <100.00%> (+0.40%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Initial blank controller for Cognito Identity Provider

Issue #1211
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/test all

/retest

/retest

/retest


error when loading pretrained models

I downloaded the pretrained models as you said, and the file name is "net_g.pth" and "net_p.pth",
However, when I tried to load "net_g.pth" using train_DASR.yml, it shows an error as below.
Traceback (most recent call last):
File "./dasr/train.py", line 15, in
train_pipeline(root_path)
File "/nas/workspace/anse/code/pytorch/SR/DASR/basicsr/train.py", line 128, in train_pipeline
model = build_model(opt)
File "/nas/workspace/anse/code/pytorch/SR/DASR/basicsr/models/init.py", line 27, in build_model
model = MODEL_REGISTRY.get(opt['model_type'])(opt)
File "/nas/workspace/anse/code/pytorch/SR/DASR/dasr/models/DASR_model.py", line 20, in init
super(DASRModel, self).init(opt)
File "/nas/workspace/anse/code/pytorch/SR/DASR/basicsr/models/srgan_dynamic_model.py", line 41, in init
self.load_network_init_alldynamic(self.net_g, load_path, self.opt['num_networks'], self.opt['path'].get('strict_load_g', True), load_key)
File "/nas/workspace/anse/code/pytorch/SR/DASR/basicsr/models/base_model.py", line 372, in load_network_init_alldynamic
load_net = load_net[param_key]
KeyError: 'params'
I think that the pretrained model weights (similar as dictionary?) has no key 'params'.

So, I add the key 'params', and this code shows another error.

Could you tell me what the problem is?

Hi,
Thanks for your attention to our work. You can avoid the code of load_net = load_net[param_key] to load model. I will also update the function later. Thanks!

I think the code needs a pre-trained weight file as below, but I cannot get the file.

So, please give the link for that file.
Thanks.

I think the code needs a pre-trained weight file as below, but I cannot get the file.

Hi,
This is the pretrained model of MSRResNet. Please get the file from the BasicSR project. Thanks.

As you said, I used the pretrained model of MSRResNet from BasicSR project
(The link is https://drive.google.com/drive/folders/1XN4WXKJ53KQ0Cu0Yv-uCt8DZWq6uufaP)
However, when I run the code, it shows an error as below.
Traceback (most recent call last):
File "./dasr/train.py", line 15, in
train_pipeline(root_path)
File "/nas/workspace/anse/code/pytorch/SR/DASR/basicsr/train.py", line 128, in train_pipeline
model = build_model(opt)
File "/nas/workspace/anse/code/pytorch/SR/DASR/basicsr/models/init.py", line 27, in build_model
model = MODEL_REGISTRY.get(opt['model_type'])(opt)
File "/nas/workspace/anse/code/pytorch/SR/DASR/dasr/models/DASR_model.py", line 20, in init
super(DASRModel, self).init(opt)
File "/nas/workspace/anse/code/pytorch/SR/DASR/basicsr/models/srgan_dynamic_model.py", line 41, in init
self.load_network_init_alldynamic(self.net_g, load_path, self.opt['num_networks'], self.opt['path'].get('strict_load_g', True), load_key)
File "/nas/workspace/anse/code/pytorch/SR/DASR/basicsr/models/base_model.py", line 389, in load_network_init_alldynamic
net.load_state_dict(load_net_repeated, strict=strict)
File "/usr/local/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1052, in load_state_dict
self.class.name, "\n\t".join(error_msgs)))
RuntimeError: Error(s) in loading state_dict for MSRResNetDynamic:
Missing key(s) in state_dict: "conv_first.weight", "conv_first.bias", "body.0.conv1.weight", "body.0.conv1.bias", "body.0.conv2.weight", "body.0.conv2.bias", "body.1.conv1.weight", "body.1.conv1.bias", "body.1.conv2.weight", "body.1.conv2.bias", "body.2.conv1.weight", "body.2.conv1.bias", "body.2.conv2.weight", "body.2.conv2.bias", "body.3.conv1.weight", "body.3.conv1.bias", "body.3.conv2.weight", "body.3.conv2.bias", "body.4.conv1.weight", "body.4.conv1.bias", "body.4.conv2.weight", "body.4.conv2.bias", "body.5.conv1.weight", "body.5.conv1.bias", "body.5.conv2.weight", "body.5.conv2.bias", "body.6.conv1.weight", "body.6.conv1.bias", "body.6.conv2.weight", "body.6.conv2.bias", "body.7.conv1.weight", "body.7.conv1.bias", "body.7.conv2.weight", "body.7.conv2.bias", "body.8.conv1.weight", "body.8.conv1.bias", "body.8.conv2.weight", "body.8.conv2.bias", "body.9.conv1.weight", "body.9.conv1.bias", "body.9.conv2.weight", "body.9.conv2.bias", "body.10.conv1.weight", "body.10.conv1.bias", "body.10.conv2.weight", "body.10.conv2.bias", "body.11.conv1.weight", "body.11.conv1.bias", "body.11.conv2.weight", "body.11.conv2.bias", "body.12.conv1.weight", "body.12.conv1.bias", "body.12.conv2.weight", "body.12.conv2.bias", "body.13.conv1.weight", "body.13.conv1.bias", "body.13.conv2.weight", "body.13.conv2.bias", "body.14.conv1.weight", "body.14.conv1.bias", "body.14.conv2.weight", "body.14.conv2.bias", "body.15.conv1.weight", "body.15.conv1.bias", "body.15.conv2.weight", "body.15.conv2.bias", "upconv1.weight", "upconv1.bias", "upconv2.weight", "upconv2.bias", "conv_hr.weight", "conv_hr.bias", "conv_last.weight", "conv_last.bias".
Unexpected key(s) in state_dict: "params".
Maybe the weight name of MSRResNet in BasicSR is different from MSRResNetDynamic in your project.

Please show me your yml file and the command you run. Thanks. The code has been checked, and should work if you exactly follow our instructions.

when i using the net_g model they offered as pre-trained model
i change the loading model code from "self.load_network_init_alldynamic" to "self.load_network"

Here are the yml file and running code (sh file) I used.
DASR.zip

@Lvhhhh
When I used net_g model (instead of MSRResNet in BasicSR), your suggestion is helpful. Thanks!

@csjliang Here are the yml file and running code (sh file) I used. DASR.zip

Please use the attached pre-trained model. Thanks.
MSRResNet_x4_f64b16_DIV2K_1000k_B16G1_net_g_1000000.zip

@csjliang The error occurred because of my code modification. Anyway, it works well. Thanks!

Thanks.

I want to remind possible reproduce in the future that the function self.load_network_init_alldynamic is still necessary if one want to train DASR as this paper did. Since the weight value of the 'net_g.pth' is NOT the same as init_weight in MSRResNet_x4_f64b16_DIV2K_1000k_B16G1_net_g_1000000.zip provided in BasicSR. net_g.pth is used for testing only. So, one need to modify the yml file of  number_networks from 0 to 5, and then use the self.load_network_init_alldynamic function to reproduce the training process of this paper.


Port project to .NET Standard.

If you are interested, I've ported this library to .NET Standard 2.0 so it can work for both .NET Framework and .NET Core. If not, then go ahead and ignore this pull request.

Thanks for doing this. It's been on my todo list. Let me take a look and get the CI build working. Likely this will be major version change.


Update yarn cache example

Caching ~/.cache/yarn doesn't work for all scenarios, and in the case of https://github.com/actions/cache/issues/60 contained extra files not needed in the cache.
Using yarn cache dir retrieves the correct directory based on the current yarn config, see https://yarnpkg.com/lang/en/docs/cli/cache/
For the hosted runners this resolves to:

windows-latest: C:\Users\runneradmin\AppData\Local\Yarn\Cache\v6
macOS-latest: /Users/runner/Library/Caches/Yarn/v6
ubuntu-latest: /home/runner/.cache/yarn/v6

Why set the yarn cache directory instead of node_modules? If I understand correctly, it's intended for development and offline environments.

@imbsky It's not recommended to cache node_modules, as you can miss install steps, break dependencies between node versions, and cause other issues. See https://github.com/actions/cache/issues/67 for more info

Yarn recommends caching both .yarn cache and node_modules.
See the GitLab example: https://yarnpkg.com/lang/en/docs/install-ci/

@joshmgross I see.
@oscar-b I didn't know that, thanks for the useful link!

The tricky part is handling yarn workspaces, which uses multiple node_modules folders. But that should be covered by multi-folder caching I guess.

@oscar-b I think that it would be better not to require users to do that. Imagine projects like Babel and Storybook - they'd need huge scripts just for caching.

Isn't that why he is making such a proposal https://github.com/actions/cache/issues/16#issuecomment-551202039 ?

Going to stick with the yarn cache, for now, once we add multiple paths support (see #16) then we can update the example to add node_modules. With workspaces, we can't assume node_modules is the correct location (could be workspace-a/node_modules), so at the very least the yarn cache will cover all installs.


Drawing column from top to bottom

Hi, is there a way to actually draw column from top to bottom not just only for as long as there are items. What I mean by that is that if the table_view is of a size that for example fits 20 items but we only populated it with 3 the column will be drawn next to those 3 items only and the rest of the space is left empty. Perhaps pic will explain that better.

Thank you

Hi, and thanks for the report!
This would indeed be doable here.

On latest master it should work properly.

Thank you very much for your work and the reply.
Unfortunately I wasn't able to check it because after updating to the latest I'm getting:
the trait cursive::view::ViewWrapper is not implemented for cursive_table_view::TableView<Foo, BasicColumn>
I would be really grateful if somebody can help me with that issue.


feat: allow a secret to be encrypted with a custom KMS key

It's often a requirement in enterprise environments that secrets must be encrypted with a custom key, and not use the AWS default key in your environment. The reason is that destroying of the stack means all data encrypted with that key is also no longer accessible (if AWS really destroys the key).
This also means I had to fix which credentials were accepted: you can now also change the default root user of your cluster, another enterprise requirement.

with those changes my code doesnt work
import { StackContext, RDS, Bucket, Service } from "sst/constructs";
import * as ecs from "aws-cdk-lib/aws-ecs";
import * as ec2 from "aws-cdk-lib/aws-ec2";
import * as rds from "aws-cdk-lib/aws-rds";
import * as cdk from "aws-cdk-lib/core";

const MyStack = ({ stack }: StackContext) => {
  const rdsSecret = new rds.DatabaseSecret(stack, "DirectusRdsSecret", {
    username: "clusteradmin",
  });

  const database = new RDS(stack, "DirectusDatabase", {
    engine: "postgresql13.9",
    defaultDatabaseName: "directus",
    cdk: {
      cluster: {
        removalPolicy: cdk.RemovalPolicy.DESTROY,
        credentials: rds.Credentials.fromSecret(rdsSecret),
      },
    },
  });
}

Error:
Error: Only credentials managed by SecretManager are supported for the "cdk.cluster.credentials".

Trace: Error: Only credentials managed by SecretManager are supported for the "cdk.cluster.credentials".
    at RDS.validateCDKPropWhenIsClusterProps

Which is doesnt make sense cuz secrets are managed by secrets manager


[WIP](Depends on #13060) Dto collection save inventory specs for skeletal refresh

Dto collection save inventory specs for skeletal refresh

@miq-bot assign @agrare

Closing since this has been in conflict for 9 months :)


update references to master

towards #5516. With this, all references to the master branch have been updated to point to main.

could someone check whether binder still works?

could someone check whether binder still works?

It's broken, unfortunately :(

I will submit a fix later today unless someone beats me to it


Fix bindat for static array serialization

Codecov Report

Merging #13 into master will increase coverage by 0.11%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #13      +/-   ##
==========================================
+ Coverage   81.80%   81.91%   +0.11%
==========================================
  Files          17       17
  Lines        4490     4496       +6
==========================================
+ Hits         3673     3683      +10
+ Misses        817      813       -4

Impacted Files
Coverage Δ

voile/bindat.d
97.22% <100.00%> (+0.07%)
:arrow_up:

voile/sync.d
72.57% <0.00%> (+0.53%)
: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 c27f757...9c26d52. Read the comment docs.


[ButtonGroup] Fix border color when disabled and contained

Closes #16558

@ryanburr I have tried to minimize the amount of changes and of custom CSS. Let us know if the problem is still solved, it seems to be ok on my tests.

@oliviertassinari Just tested it out locally and it all looks good! Thanks for the help!

Perfect!


Fixes the issue where you can't add an item into an empty gallery

issue #25

FYI my code style formatter in Webstorm went a little crazy, if it's to much to deal with I can resubmit without the formatting.


bug: select doesn’t work on Android Tablets

When there is a select on a page, the select renders well on Android Smartphones, but when it is on Android Tablets it renders the options in blank. This problem is best described in this Stack Overflow question:
http://stackoverflow.com/questions/27025345/apache-cordova-android-5-0-select-box-option-color
I used Ionic 1, a Samsung Galaxy Tab 2 and Android 5.0

Hello, thanks for opening an issue with us! Would you be able to provide a plunker or repo that demonstrates this issue? Thanks for using Ionic!

Hello, I created this simple repo: https://github.com/mikejobrn/tablet-select.git
Like I said, it works well on smartphones but not on tablets, I mean at least on Samsung Galaxy Tab 2 (it's the only one I have to test against).
Thank you.

Hello @mikejobrn, unfortunately i cannot seem to reproduce this issue using your repo running on a Nexus 7 running Android 6.0.1. What version of Android is your Tab 2 running?

It's a Samsung Galaxy Tab 2 with a 10.1" screen running Android 5.0.2.

Hello, i just tested with a nexus 10 simulator running Android 5.0.2 and cannot seem to reproduce this issue unfortunately. Could you post a screenshot of what the issue looks like? Also could you try the app with crosswalk. Thanks!

Here is a screenshot:

I'll give a try to crosswalk and tell you what happened.

@jgw96 it worked with Crosswalk, thank you! But isn't there another way to workaround that without the Crosswalk plugin?

@mikejobrn Unfortunately I do not know of any other solution at this time. Samsung has a bad habit of modifying or not updating their webviews, which can unfortunately lead to small issues like this. Crosswalk gives you a completely stock, up to date webview, just like a nexus device has, which is why it is working with Crosswalk. Sorry i couldn't give you another solution, but i'm glad that fixed it for you. Thanks for using Ionic! As this issue has been fixed I will be closing this issue.

I understand. Thank you :)


Question: How to reverse proxy a http service?

its a node service up to port 8443
- match:
  - http:
      host:
        - "example.com"
  handle:
    - handler: proxy
    - handler: proxy
      upstreams:
        - dial: ["localhost:8443"]

this is full caddy.yml
but the 8443 port doesn't work, its a http service, but dont know how to write this config
logging:
  logs:
    default:
      level: INFO
storage:
  "module": "file_system"
  "root": "/data"
apps:
  tls:
    certificates:
      automate:
        - project-yzc.example.com
        - project-yzc-live.example.com
        - project-yzc-turn.example.com
  layer4:
    servers:
      main:
        listen: [":443"]
        routes:
          - match:
            - http:
                host:
                  - "project-yzc.example.com"
            handle:
              - handler: proxy
              - handler: proxy
                upstreams:
                  - dial: ["localhost:8443"]
          - match:
            - tls:
                sni:
                  - "project-yzc-turn.example.com"
            handle:
              - handler: tls
              - handler: proxy
                upstreams:
                  - dial: ["localhost:5349"]
          - match:
              - tls:
                  sni:
                    - "project-yzc-live.example.com"
            handle:
              - handler: tls
                connection_policies:
                  - alpn: ["http/1.1"]
              - handler: proxy
                upstreams:
                  - dial: ["localhost:7880"]

            handle:
              - handler: proxy
              - handler: proxy

You have two proxy handlers in a row, and the first one has no config. So it just straight up does nothing.

the server keep restarting after i add this
Error: loading initial config: loading new config: loading layer4 app module: provision layer4: server 'main': route 0: loading matcher modules: module name 'http': decoding module config: layer4.matchers.http: json: cannot unmarshal object into Go value of type caddyhttp.RawMatcherSets
- match:
            - http:
                host:
                  - "project-yzc.example.com"
            handle:
              - handler: proxy
                upstreams:
                  - dial: ["<IP_ADDRESS>:8443"]

i've just copied the third config, and change port it works.
thanks
logging:
  logs:
    default:
      level: INFO
storage:
  "module": "file_system"
  "root": "/data"
apps:
  tls:
    certificates:
      automate:
        - project-yzc.example.com
        - project-yzc-live.example.com
        - project-yzc-turn.example.com
  layer4:
    servers:
      main:
        listen: [":443"]
        routes:
          - match:
              - tls:
                  sni:
                    - "project-yzc.example.com"
            handle:
              - handler: tls
                connection_policies:
                  - alpn: ["http/1.1"]
              - handler: proxy
                upstreams:
                  - dial: ["localhost:8443"]
          - match:
            - tls:
                sni:
                  - "project-yzc-turn.example.com"
            handle:
              - handler: tls
              - handler: proxy
                upstreams:
                  - dial: ["localhost:5349"]
          - match:
              - tls:
                  sni:
                    - "project-yzc-live.example.com"
            handle:
              - handler: tls
                connection_policies:
                  - alpn: ["http/1.1"]
              - handler: proxy
                upstreams:
                  - dial: ["localhost:7880"]


Dict keys are not unique in the string in the database

I use jsonfield to store a blob of the following format (newlines added for readability):
{
    "213":  {
        "stringfield": "bla",
        "datafield": {"max": 3, "min": 1}
    },
    "432": {
        "stringfield": "",
        "datafield": [1,2,3]
    }
}

I change one entry at a time:
new = {"stringfield": "", "datafield": [1,2]}
model.data["432"] = new
model.save()

Sometimes, the string stored in the database is not a serialization of a dict, because the keys are not unique:
{
    "213":  {
        "stringfield": "bla",
        "datafield": {"max": 3, "min": 1}
    },
    "432": {
        "stringfield": "",
        "datafield": [1,2,3]
    },
    "432": {
        "stringfield": "",
        "datafield": [1,2]
    }
}

I have SQL logging turned on, and what I see is that Django sends
    "432": {
        "stringfield": "",
        "datafield": [1,2,3]
    },
    "432": {
        "stringfield": "",
        "datafield": [1,2]
    }

.. and that's what the server stores. Then on select, python eventually converts to dict, and chooses always the final entry, which is the first version of the stored entry. The admin shows a single entry for 432 for instance. The end result is that it seems 432 haven't changed, because the new data can never be read back.
It looks to me like jsonfield is doing something funky. This is jsonfield version 2.0.2.

Hi @hmpf. I tested this locally but was unable to recreate the issue. It's possible this was fixed in the 3.0 rewrite. Here's the sample test case I used:
class ExampleTest(TestCase):
    @override_settings(DEBUG=True)
    def test_ex(self):
        from django.db import connection
        instance = JSONNotRequiredModel.objects.create(json={
            "213":  {
                "stringfield": "bla",
                "datafield": {"max": 3, "min": 1},
            },
            "432": {
                "stringfield": "",
                "datafield": [1, 2, 3],
            }
        })

        instance.json["432"] = {"stringfield": "", "datafield": [1, 2]},
        instance.save()

        for q in connection.queries:
            print('*' * 80)
            print(q['sql'])

Which outputs:
********************************************************************************
INSERT INTO "tests_jsonnotrequiredmodel" ("json") VALUES ('{"213": {"stringfield": "bla", "datafield": {"max": 3, "min": 1}}, "432": {"stringfield": "", "datafield": [1, 2, 3]}}')
********************************************************************************
UPDATE "tests_jsonnotrequiredmodel" SET "json" = '{"213": {"stringfield": "bla", "datafield": {"max": 3, "min": 1}}, "432": [{"stringfield": "", "datafield": [1, 2]}]}' WHERE "tests_jsonnotrequiredmodel"."id" = 1

Please let me know if this is still an issue for you.


idea: Drop the support of read from tail

Nearly no one really uses read from tail, but we need to do a lot of hacks at services side. For example:

Webhdfs

https://github.com/datafuselabs/opendal/blob/034cb76bfad68a540925c91cca078d7d16dcf292/src/services/webhdfs/backend.rs#L383-L385

azblob

https://github.com/datafuselabs/opendal/blob/034cb76bfad68a540925c91cca078d7d16dcf292/src/services/azblob/backend.rs#L565-L573

I will try to do it.
I think we need to keep

Range: bytes=<range-start>-
Range: bytes=<range-start>-<range-end>

and just remove support

Range: bytes=-<suffix-length>

and just remove support

Do you mean we will return an error if users try to range_read(..xxx)?

Do you mean we will return an error if users try to range_read(..xxx)?

In BytesRange doc:

BytesRange support construct via rust native range syntax like .., 1024.., ..2048.
But it's has different semantic on RangeTo: ..<end>.
In rust, ..<end> means all items that < end, but in BytesRange, ..<end> means the
tailing part of content, a.k.a, the last <end> bytes of content.

So,  when if range.offset().is_none() && range.size().is_some(), we will think it's a suffix read.
We don't need support this semantic. I  think convert it same with 0....range better than return an error
For example:
current:  ..1024 will be converted to header range: bytes=-1024
future: - ..1024 will be converted to header range: bytes=0-1024

In our current logic, we will never send ..1024 to the underlying services. Because we always need to calculate the correctl offset and size before sending requests.
https://github.com/apache/incubator-opendal/blob/7166d873a0a1d3a502f17116777d81271532e1f5/src/layers/complete.rs#L173-L185
I think it's safe to just remove the read from tail support from services.

the correction of goal: we still support read from tail, but we don't need service to implement it directly.

Our goal isn't to remove support of read from tail. We just don't do hack to support to read from tail.
If a service can support read from tail natively, we also don't stop use read from tail.
Like:

ftp can use RETR to specify range
IPFS also can support it

So, this issue is just for removing hack to support.

We should treat this feature as a new capability.


pan: 0.144 -> 0.145

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/pan/versions.
These checks were done:

built on NixOS
/nix/store/myvdzpw4h622lqfbssrqq8iv0jlgmr3x-pan-0.145/bin/pan passed the binary check.
/nix/store/myvdzpw4h622lqfbssrqq8iv0jlgmr3x-pan-0.145/bin/.pan-wrapped passed the binary check.
2 of 2 passed binary check by having a zero exit code.
2 of 2 passed binary check by having the new version present in output.
found 0.145 with grep in /nix/store/myvdzpw4h622lqfbssrqq8iv0jlgmr3x-pan-0.145
directory tree listing: https://gist.github.com/71c7135618028b366312a29248169c8f
du listing: https://gist.github.com/ab2cc751a6e4bb701fc4e8d6836d398e

meta.description for pan is: '"A GTK+-based Usenet newsreader good at both text and binaries"'.
cc @edolstra for testing.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: pan
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: pan
Partial log (click to expand)
make[1]: Leaving directory '/build/pan-0.145/po'
glibPreFixupPhase
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/h6lmicihmnpwy86j9ii48b09f6r2dxbd-pan-0.145
shrinking /nix/store/h6lmicihmnpwy86j9ii48b09f6r2dxbd-pan-0.145/bin/.pan-wrapped
gzipping man pages under /nix/store/h6lmicihmnpwy86j9ii48b09f6r2dxbd-pan-0.145/share/man/
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/h6lmicihmnpwy86j9ii48b09f6r2dxbd-pan-0.145/bin
patching script interpreter paths in /nix/store/h6lmicihmnpwy86j9ii48b09f6r2dxbd-pan-0.145
checking for references to /build in /nix/store/h6lmicihmnpwy86j9ii48b09f6r2dxbd-pan-0.145...

Success on aarch64-linux (full log)
Attempted: pan
Partial log (click to expand)
glibPreFixupPhase
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/55877nnd158791f69in516c55lw1dk6i-pan-0.145
shrinking /nix/store/55877nnd158791f69in516c55lw1dk6i-pan-0.145/bin/.pan-wrapped
gzipping man pages under /nix/store/55877nnd158791f69in516c55lw1dk6i-pan-0.145/share/man/
strip is /nix/store/jk6j4lh9v5mvjdbdc35sj0zffhhf6s56-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/55877nnd158791f69in516c55lw1dk6i-pan-0.145/bin
patching script interpreter paths in /nix/store/55877nnd158791f69in516c55lw1dk6i-pan-0.145
checking for references to /build in /nix/store/55877nnd158791f69in516c55lw1dk6i-pan-0.145...
/nix/store/55877nnd158791f69in516c55lw1dk6i-pan-0.145


4339 admin option set import

Looks smooth! As I said before I worry someone is going to import a flippin huge option set and then try to replicate it and it will not be pretty (I think -- never tested it). But I guess we'll deal with that when it happens...


fix bug when posting too many statuses

TBC

Could you explain the bug? Do we have a JIRA issue for it?