Named export 'consola' not found

Environment
Nuxi 3.4.0

Operating System: Darwin
Node Version:     v19.8.1
Nuxt Version:     3.4.0
Nitro Version:    2.3.3
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      runtimeConfig, modules, imports, app, vite, sitemap, tailwindcss, googleFonts, i18n, content
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction

yarn nuxi upgrade --force
yarn dev
visit http://localhost:3000

Describe the bug

:warning: Request Error 500: Named export 'consola' not found.

[nuxt] [request error] [unhandled] [500] Named export 'consola' not found.

The requested module 'consola' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from 'consola';
const { consola } = pkg;

 at ModuleJob._instantiate (node:internal/modules/esm/module_job:123:21)
  at async ModuleJob.run (node:internal/modules/esm/module_job:189:5)

Additional context
No response
Logs
No response

Experiencing the same issue after upgrading to 3.4

This issue is likely caused by other dependencies hoisting consola v2 to the top level.
For now, you can likely work around it by adding pnpm/npm overrides or yarn resolutions.
cc: @pi0

Same here, here is an output of pnpm why consola
devDependencies:
@nuxt/devtools 0.3.2
├─┬ @nuxt/devtools-kit 0.3.2
│ ├─┬ @nuxt/kit 3.4.0
│ │ └── consola 3.0.1
│ └─┬ nuxt 3.4.0 peer
│   ├─┬ @nuxt/kit 3.4.0
│   │ └── consola 3.0.1
│   ├─┬ @nuxt/telemetry 2.2.0
│   │ ├─┬ @nuxt/kit 3.4.0
│   │ │ └── consola 3.0.1
│   │ └── consola 3.0.1
│   ├─┬ @nuxt/vite-builder 3.4.0
│   │ └─┬ @nuxt/kit 3.4.0
│   │   └── consola 3.0.1
│   └─┬ nitropack 2.3.3
│     └── consola 3.0.1
├─┬ @nuxt/devtools-wizard 0.3.2
│ └── consola 2.15.3
├─┬ @nuxt/kit 3.4.0
│ └── consola 3.0.1
├── consola 2.15.3
└─┬ nuxt 3.4.0 peer
  ├─┬ @nuxt/kit 3.4.0
  │ └── consola 3.0.1
  ├─┬ @nuxt/telemetry 2.2.0
  │ ├─┬ @nuxt/kit 3.4.0
  │ │ └── consola 3.0.1
  │ └── consola 3.0.1
  ├─┬ @nuxt/vite-builder 3.4.0
  │ └─┬ @nuxt/kit 3.4.0
  │   └── consola 3.0.1
  └─┬ nitropack 2.3.3
    └── consola 3.0.1
@nuxt/image-edge 1.0.0-28008586.381b906
├─┬ @nuxt/kit 3.4.0
│ └── consola 3.0.1
├── consola 2.15.3
└─┬ ipx 1.0.0
  └── consola 2.15.3
@pinia/nuxt 0.4.8
└─┬ @nuxt/kit 3.4.0
  └── consola 3.0.1
@vite-pwa/nuxt 0.0.7
└─┬ @nuxt/kit 3.4.0 peer
  └── consola 3.0.1
consola 3.0.1
nuxt 3.4.0
├─┬ @nuxt/kit 3.4.0
│ └── consola 3.0.1
├─┬ @nuxt/telemetry 2.2.0
│ ├─┬ @nuxt/kit 3.4.0
│ │ └── consola 3.0.1
│ └── consola 3.0.1
├─┬ @nuxt/vite-builder 3.4.0
│ └─┬ @nuxt/kit 3.4.0
│   └── consola 3.0.1
└─┬ nitropack 2.3.3
  └── consola 3.0.1
pinceau 0.18.8
├── consola 2.15.3
├─┬ style-dictionary-esm 1.3.7
│ └── consola 2.15.3
└─┬ unbuild 1.2.0
  └── consola 2.15.3

Can be fixed by adding this into package.json
  "pnpm": {
    "overrides": {
      "consola": "3.0.1"
    }
  }

Workaround seems to be working.
yarn add -D consola installs in my case "consola": "^3.0.1",
Result: error no longer present

I also experience the issue, and yes the "workaround" works npm install<EMAIL_ADDRESS>However, a fresh nuxt install works, so it must be one of the modules we have installed.

Hi, I'm having the same issue after upgrading to Nuxt 3.4.0. yarn add -D consola also resolves the issue for me. Below is the output of yarn why consola before and after adding the dependency.

Before
yarn why v1.22.19
[1/4] 🤔  Why do we have the module "consola"...?
[2/4] 🚚  Initialising dependency graph...
[3/4] 🔍  Finding dependency...
[4/4] 🚡  Calculating file sizes...
=> Found<EMAIL_ADDRESS>info Has been hoisted to "consola"
info Reasons this module exists
   - Hoisted from "@nuxt#devtools#consola"
   - Hoisted from "@nuxt#image-edge#consola"
   - Hoisted from "@nuxt#devtools#@nuxt#devtools-wizard#consola"
   - Hoisted from "@nuxt#image-edge#ipx#consola"
info Disk size without dependencies: "220KB"
info Disk size with unique dependencies: "220KB"
info Disk size with transitive dependencies: "220KB"
info Number of shared dependencies: 0
=> Found "<EMAIL_ADDRESS>info This module exists because "nuxt#@nuxt#kit" depends on it.
info Disk size without dependencies: "264KB"
info Disk size with unique dependencies: "264KB"
info Disk size with transitive dependencies: "264KB"
info Number of shared dependencies: 0
=> Found "<EMAIL_ADDRESS>info This module exists because "nuxt#@nuxt#telemetry" depends on it.
info Disk size without dependencies: "264KB"
info Disk size with unique dependencies: "264KB"
info Disk size with transitive dependencies: "264KB"
info Number of shared dependencies: 0
=> Found<EMAIL_ADDRESS>info This module exists because "nuxt#nitropack" depends on it.
info Disk size without dependencies: "264KB"
info Disk size with unique dependencies: "264KB"
info Disk size with transitive dependencies: "264KB"
info Number of shared dependencies: 0
✨  Done in 0.21s.

After
yarn why consola
yarn why v1.22.19
[1/4] 🤔  Why do we have the module "consola"...?
[2/4] 🚚  Initialising dependency graph...
[3/4] 🔍  Finding dependency...
[4/4] 🚡  Calculating file sizes...
=> Found<EMAIL_ADDRESS>info Has been hoisted to "consola"
info Reasons this module exists
   - Specified in "devDependencies"
   - Hoisted from "nuxt#@nuxt#kit#consola"
   - Hoisted from "nuxt#@nuxt#telemetry#consola"
   - Hoisted from "nuxt#nitropack#consola"
info Disk size without dependencies: "264KB"
info Disk size with unique dependencies: "264KB"
info Disk size with transitive dependencies: "264KB"
info Number of shared dependencies: 0
=> Found "<EMAIL_ADDRESS>info This module exists because "@nuxt#devtools" depends on it.
info Disk size without dependencies: "220KB"
info Disk size with unique dependencies: "220KB"
info Disk size with transitive dependencies: "220KB"
info Number of shared dependencies: 0
=> Found "<EMAIL_ADDRESS>info This module exists because "@nuxt#image-edge" depends on it.
info Disk size without dependencies: "220KB"
info Disk size with unique dependencies: "220KB"
info Disk size with transitive dependencies: "220KB"
info Number of shared dependencies: 0
=> Found "<EMAIL_ADDRESS>info This module exists because "@nuxt#devtools#@nuxt#devtools-wizard" depends on it.
info Disk size without dependencies: "220KB"
info Disk size with unique dependencies: "220KB"
info Disk size with transitive dependencies: "220KB"
info Number of shared dependencies: 0
=> Found<EMAIL_ADDRESS>info This module exists because "@nuxt#image-edge#ipx" depends on it.
info Disk size without dependencies: "220KB"
info Disk size with unique dependencies: "220KB"
info Disk size with transitive dependencies: "220KB"
info Number of shared dependencies: 0
✨  Done in 0.21s.

Noticing this when I add nuxt-icon to my current list of modules:
  modules: [
    '@nuxt/content',
    '@nuxtjs/color-mode',
    '@nuxtjs/tailwindcss'
  ],

Removing the module using yarn remove allows everything to work correctly.

started

I'm on 3.4. I have a couple apps at 3.3 I can try updating.

Same here, overrides does not helps

I experienced the same problem. In my case, running nuxi upgrade --force resolved the issue.
I hope this works.

I have the same issue

Same issue

Operating System: Linux
Node Version:     v18.15.0
Nuxt Version:     3.4.0
Nitro Version:    2.3.3
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      srcDir, modules, vite, i18n, nitro, schemaOrg, telemetry, algolia, head, auth, viewport, css, build, runtimeConfig
Runtime Modules<EMAIL_ADDRESS>genesis-design-system/nuxt<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

This also happens to me on 3.3.1 if i delete my node_modules and lockfile and reinstall. Fixed by the workaround

For those using @nuxtjs/tailwindcss you need to wait for them to update they package because they are still in nuxt/kit 3.3.3 instead of nuxtkit 3.4
I'm using pnpm workspace so for me adding consola in my root package solve the issue

On v3.4.1 and this fixed it for me

Can be fixed by adding this into package.json if using pnpm
  "pnpm": {
    "overrides": {
      "consola": "3.0.1"
    }
  }

Fix with in package.json:
  "peerDependencies": {
    "consola": "3.0.1"
  },

I experienced the same problem. In my case, running nuxi upgrade --force resolved the issue.
I hope this works.

It works this way. I did not use the --force option when I updated it the first time, then I ran the upgrade command using the --force option and it worked flawlessly.

nuxi upgrade --force option is not for me since it will delete node_modules, lock file, and reinstall all my deps, it's too risky for a big project, I will be waiting for the update from the other deps to upgrade consola before upgrading nuxt

With npm and node >= 18 this happens in case you run
npm update nuxt instead of  npm update nuxt --legacy-peer-deps
to fix it, run npm i --legacy-peer-deps

Same here

Hi. I apologize for any issues you are encountering with this upgrade. If you are using nuxt as a dependency in your project:

Use npx nuxi upgrade --force to upgrade the lock file. Check if the issue is solved.
Use pnpm why, npm-why or yarn why and check list of dependencies that are still using consola@2. Please consider reporting them here so we can track and ask them to upgrade. If hoisted (top level) consola version in results is still v2, add a resolutions field to your project's package.json and renew lockfile or install:

{
  "resolutions": {
    "consola": "^3.0.0"
  }
}

If you are a library or module author:

Check if you are directly having consola as a dependency, if you have it, upgrade to v3 and change import consola to import { consola }
Followup steps above to find out about the possible sub-dependency issues
Use resolutions, to fix your local development branch and followup with sub-dependency issues here to be resolved. Advice your users to use above steps in the meanwhile.

Hi. I apologize for any issues you are encountering with this upgrade.
If you are using nuxt as a dependency in your project:
1. Use `npx nuxi upgrade --force` to upgrade the lock file. Check if the issue is solved.

2. Use [pnpm why](https://pnpm.io/cli/why), [npm-why](https://www.npmjs.com/package/npm-why) or [yarn why](https://classic.yarnpkg.com/lang/en/docs/cli/why/) and check list of dependencies that are still using `consola@2`. Please consider reporting them here so we can track and ask them to upgrade. If hoisted (top level) consola version in results is still v2, add a `resolutions` field to your project's `package.json` and renew lockfile or install:

{
  "resolutions": {
    "consola": "^3.0.0"
  }
}

If you are a library or module author:
1. Check if you are directly having `consola` as a `dependency`, if you have it, upgrade to `v3` and change `import consola` to `import { consola }`

2. Followup steps above to find out about the possible sub-dependency issues

3. Use `resolutions`, to fix your **local development** branch and followup with sub-dependency issues here to be resolved. Advice your users to use above steps in the meanwhile.

In my proyect:

nuxt-icon ><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>

@sdsoldi Thanks for reporting. nuxt-config-schema is fixed you can try again by recreating lockfile.

@pi0 Fixed! Thanks!!!

I literally get this in a new project:
$ npx nuxt init ui
$ cd ui
$ npm install
$ npm run dev
Nuxi 3.4.2                                                                                8:33:11 PM
Nuxt 3.4.2 with Nitro 2.3.3                                                                                8:33:11 PM
                                                                                8:33:12 PM
  > Local:    http://localhost:3000/
  > Network:  http://<IP_ADDRESS>:3000/
  > Network:  http://<IP_ADDRESS>:3000/
  > Network:  http://<IP_ADDRESS>:3000/
  > Network:  http://<IP_ADDRESS>:3000/
  > Network:  http://<IP_ADDRESS>:3000/

ℹ Vite client warmed up in 761ms                                                                                8:33:13 PM
✔ Nitro built in 388 ms                                                                                nitro 8:33:13 PM
[8:33:21 PM] [nuxt] [request error] [unhandled] [500] Named export 'consola' not found. The requested module 'consola' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from 'consola';
const { consola } = pkg;

  at ModuleJob._instantiate (node:internal/modules/esm/module_job:123:21)
  at async ModuleJob.run (node:internal/modules/esm/module_job:189:5)
[8:33:21 PM] [nuxt] [request error] [unhandled] [500] Named export 'consola' not found. The requested module 'consola' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from 'consola';
const { consola } = pkg;

  at ModuleJob._instantiate (node:internal/modules/esm/module_job:123:21)
  at async ModuleJob.run (node:internal/modules/esm/module_job:189:5)
npm run dev  4,93s user 0,28s system 28% cpu 18,018 total

$ node --version
v19.8.1
$ npm -version
8.19.2

@alko89 Would you check if you have a node_modules folder in a parent directory?

@danielroe yep, its a monorepo project, parrent package.json
{
  "name": "task",
  "version": "1.0.0",
  "description": "",
  "authors": {
    "name": "",
    "email": ""
  },
  "license": "MIT",
  "workspaces": [
    "api",
    "ui"
  ]
}

Hi I faced the same issue
and this is the result of

$ npx npm-why consola

Who required consola:

@nuxt/devtools ><EMAIL_ADDRESS>@nuxt/image-edge > ipx ><EMAIL_ADDRESS>

I have the same issue but adding a resolutions field is working fine.
pnpm why consola returns:

dependencies:
@nuxtjs/sanity 1.6.0
└─┬ @nuxt/kit 3.1.0
└── consola 2.15.3

app > @nuxt/devtools ><EMAIL_ADDRESS>

Another two libaries using consola 2.X.X
npx npm-why consola

  Who required consola:

  studio-terabyte-website-nuxt-3 > @funken-studio/sitemap-nuxt-3 ><EMAIL_ADDRESS>  studio-terabyte-website-nuxt-3 > @nuxt/image-edge > ipx ><EMAIL_ADDRESS>
Adding consola to resolutions has fixed the issue

I'm using nuxt only few months and I got multiple problems not only for updating from 2 to 3 but every single release you something to broke! I'm frustrated. Please think about it, your product used by many people. Maybe invest in unit tests more?

Hi this issue just happened. These are the libraries who are using consola 2.X.X:
npx npm-why consola

  Who required consola:

  @nestjs/core > @nuxtjs/opencollective ><EMAIL_ADDRESS>
Adding consola to resolutions didn't fix the issue, either in the nuxt app package.json or the root package.json

Solved for me when upgrading to nuxt's latest version and removing nuxtImage module.

Upstream

what can i do with this: Error cannot start nuxt :cannot read properties of undefined (reading 'hook')
-nuxtbootstarpvue
-installmodule
-async initNuxt/load/_main/Object.invoke

@AliNaraghiA You are using a module that isn't compatible with Nuxt 3.

I fail to understand how to fix this, but npx nuxi init my-app will result with this consola error...

Hi. I apologize for any issues you are encountering with this upgrade.
If you are using nuxt as a dependency in your project:

Use npx nuxi upgrade --force to upgrade the lock file. Check if the issue is solved.
Use pnpm why, npm-why or yarn why and check list of dependencies that are still using consola@2. Please consider reporting them here so we can track and ask them to upgrade. If hoisted (top level) consola version in results is still v2, add a resolutions field to your project's package.json and renew lockfile or install:

{
  "resolutions": {
    "consola": "^3.0.0"
  }
}

If you are a library or module author:

Check if you are directly having consola as a dependency, if you have it, upgrade to v3 and change import consola to import { consola }
Followup steps above to find out about the possible sub-dependency issues
Use resolutions, to fix your local development branch and followup with sub-dependency issues here to be resolved. Advice your users to use above steps in the meanwhile.

I have a monorepo project that consists of nuxt for the frontend and strapi for the backend. I tried to fix it with the "resolutions" key in nuxts package.json but it didn't work.
Those are the deps that still using console v2:

@strapi/strapi > @strapi/admin > webpackbar ><EMAIL_ADDRESS>strapi-plugin-io > @strapi/strapi > @strapi/admin > webpackbar ><EMAIL_ADDRESS>

@hermanndettmann You may need to use overrides or pnpm.overrides depending on your package manager.

Thanks @danielroe for your reply! I tried overrides because I'm using just plain ol' npm but unfortunately it didn't help. I added the following to my package.json:
"overrides": {
     "consola": "^3.0.0"
},

Thanks @danielroe for your reply! I tried overrides because I'm using just plain ol' npm but unfortunately it didn't help. I added the following to my package.json:
"overrides": {
     "consola": "^3.0.0"
},

Just for the record: I got it working finally. I just put the overrides into the wrong place. My monorepo is structured like this:
nuxt/
- package.json
strapi/
- package.json
package.json

I first put the overrides into nuxt/package.json but that didn't work. What made it work was putting it into the roots package.json.
I hope that helps some other desperate node tinkerer like me. :-)


allow-hide-as-option-in-param

allow params to be hidden by specifying help=True rather than the name starting with an underscore

closes #32


WIP - Removed rule to test only PostgresSQL

enables testing during CI build of wrong credentials for non-PostgresSQL DB's to verify if the exception still exists or not for #511

@blafond I've changed this to a Draft PR.
Also, you can test this on your personal GitHub repository changing the condition here (if needed): https://github.com/hibernate/hibernate-reactive/blob/master/.github/workflows/build.yml#L4

Looks like MySQL DB test worked fine, but DB2 failed. Ran locally and the exception didn't contain BogusBogus
The exception was:
io.vertx.db2client.DB2Exception: Invalid credentials, verify the user and password values supplied are correct
So do we need to customize the test(s) to check to DB type? since the message from PgException won't be the same as DB2Exception?

sorry.. looks like MySQL errored too in the CI test

That was the whole point of the issue :-)
Could you checked why it has failed?
It's better if you enable this test only for Postgres and MySQL, so that error on Db2 won't appear

thanks @blafond


AARCH64 Broken Relocations

The following relocations are broken:
R_AARCH64_PREL64 (generates unimplemented warning)
R_AARCH64_ADD_ABS_LO12_NC (bad relocation information applied)
R_AARCH64_CALL26 (bad relocation information applied)
R_AARCH64_JUMP26 (bad relocation information applied)

Fixed in 3.2.3857-dev.


KY040 not changing volume

Hi,
I am trying to use the often used setup with the KY040 as Volume control and the Hifiberry Miniamp as amplifier. Unfortunately I cannot get the knob to make the sound go up/down.
The KY040 itself seems to be working - I put a logging handler temporarily to the rotary_encoder.py, that streams to stdout and I get the expected notifications.
Is there any config, that I still need to set and overlooked?
I'd really appreciate some hint. Thanks!
I am using an RPi Zero W, Headless Raspberry-Pi OS, RPi-Jukebox Image from about 4 weeks ago.
This is my gpio_settings.ini
[DEFAULT]
enabled : True

[VolumeControl]
enabled : True
Type : RotaryEncoder
Pin1 : 5
Pin2 : 6
timeBase: 0.2
functioncall1 : functionCallVolU
functioncall2 : functionCallVolD

[PlayPause]
enabled : True
Type : Button
pin : 27
hold_time : 0.3
functioncall : functionCallPlayerPause
pull_up_down : pull_up

[NextSong]
enabled : True
type : Button
pin : 22
hold_time : 0.3
functioncall : functionCallPlayerNext

[PrevSong]
enabled : True
type : Button
pin : 23
hold_time : 0.3
functioncall : functionCallPlayerPrev

PS: If this is not the right place for this question, I am sorry. Please point me into the right direction in that case. Thanks.

Ok, probably the wrong place here... I put a new thread in discussions for that. Sorry to bother...


fix(grammar): Fix syntax highlighting for Kernel.` method in Ruby grammar

Motivation
Closes #1470
The issue was that syntax highlighting breaks when using the Kernel.\`  method in Ruby code. The grammar was incorrectly treating the backtick in this context as the start of an interpolated string literal, leading to incorrect tokenization and highlighting.
Implementation
To address this, the Ruby grammar was updated to properly distinguish between backtick string literals and the Kernel.`  method calls. Specifically, the begin pattern for backticks was modified to include a negative lookbehind (?<!\\.), ensuring that only standalone backticks are treated as string delimiters.

(?<!…) — Negative Lookbehind. Matches if the provided pattern would not match the preceding characters, but does not advance the current position. The pattern must have a fixed length (unbounded quantifiers are not permitted).

ref. https://rbuckton.github.io/regexp-features/engines/oniguruma.html
Additionally, I added new test cases to cover both standard backtick strings and Kernel.\`  method calls. These tests verify that the grammar correctly tokenizes each scenario, ensuring that backtick strings are recognized as interpolated strings, while Kernel.\`  methods are handled without string interpretation.
Automated Tests
Unit tests were added as part of this change to ensure that both scenarios (standard backtick strings and Kernel.\` method calls) are correctly handled by the grammar.
Manual Tests
Before

After

I have signed the CLA!


Increase Illuminate/Support to 5.0.*

Adding the Illuminate/support to 5.0.* to ensure it works with Laravel 5

Tried it, It gave problems further down the line.
https://github.com/wtfzdotnet/tmdb-package/pull/4

Like What issue was it giving?

I don't remember :( did you get it working?


JAVA-2480: Upgrade Jackson to 2.10.0

Pushed a small fix for the databind property and confirmed that the OSGi tests pass.


Requests to external_concrete5/ throw 500 error

Make a request to /ccm/system/authentication/oauth2/external_concrete5/<something> and you'll get the following error:

exceptions.EMERGENCY: Exception Occurred: /var/www/public/concrete/src/Http/Middleware/FrameOptionsMiddleware.php:41 Call to a member function has() on null (0)  ["[object] (Error(code: 0): Call to a member function has() on null at /var/www/public/concrete/src/Http/Middleware/FrameOptionsMiddleware.php:41)"] []

I remember this but I can't reproduce this - I believe this has since been fixed.


Label context support

Describe the Feature
Hi, would it make sense to update this module to support label context?
Are you guys planning to update all of your modules to support context using some kind of automation?
If you don't, I can prepare a PR where I introduce the context to this module. See aws-s3-bucket context PR as a reference.

@adys
Thanks, yes we are working on adding context to all our modules (and some other new features).
We have many modules, so yes your help would be welcome and appreciated.
PRs are always welcome.
If you want to take a stub at this, please run the following commands in the root of the repo:
make init
make github/init
cd test/src/
go mod init github.com/cloudposse/$(cd ../../ && basename `pwd`)
go mod tidy
git rm Gopkg.*
git add go.*
cp ../../../terraform-null-label/test/src/Makefile

We need to add context.tf to the module and to the examples/complete.
This also will update the Terratest to use go modules (if that was not updated yet).
Thank you

@aknysh I just noticed this module depends on aws-dynamodb-autoscaler module which doesn't support the context either.
I've created PR to add context to the dependency module first. Once it gets merged, I'll update this one as well.

@aknysh any chance someone can take a look at PR so I can finish this one as well? Thank you.

Closed by #72


SharedSerializeMapError does not implement Send/Sync, making it difficult to use

In general Errors should strive to implement Send/Sync when possible so that passing them across threads down to e.g. main thread is reasonably straightforward.
Usually the errors fail to implement these traits when they have as a payload some type which doesn't need to be there all that badly. I'm not sure if that's the case with SharedSerializeMapError, but it contains a pointer which makes it !Send/!Sync.
Are users inspecting this error expected to do something pointery with the contained pointer, or is it there entirely for ability to inspect the address etc? If its the latter, maybe it would make sense to replace it with an usize?

This is an oversight, the provided pointer is intended to be used purely for debugging purposes. Changing it to a usize is technically an API change, so I think that manually implementing Send and Sync for SharedSerializeMapError is the best path forward. Switching to a usize and removing the manual implementations would be good cleanup for the next breaking release.

Fixed by 1601793a9cb34088ca03299eb0281e647f072e78. This will be released in rkyv 0.7.30 which should be in the next few hours if everything goes smoothly.

Hm, AllocScratchError seems to be sharing mostly the same issue, though I'm again not entirely sure if the pointers therein are expected to be used as pointers by the users or not.

Same thing, all of those error types are meant to be purely for debugging purposes. I would be very shocked if people wanted to try to manually fix up a byte buffer. I’ll get that one sorted too.

This should be cleaned up by 317599f2e9cbe37ef219b8b44a96bfbc804fb620. The only remaining exception is SharedDeserializeMap, which can't be Send/Sync per #174. Not sure if there's actually a way to fix this, but if you have any ideas you're welcome to chime in on that issue.
I'll get these changes tested and shipped for 0.7.31, which should (hopefully) be sometime later today.


refactor(frontend): generalize Info banner component

Motivation
Since we are going to reuse it even for ETH/ERC20 tokens, we generalize the usage if the Info component.
Changes

Move infoBox to lib/components/info.
Create component InfoBanner that just accepts key as prop and manage the show/hide features (this part was already in Info component, and it was just separated).
Adapt Info component.

Tests
No changes in local replica.

Maybe InfoWrapper?

Why not, or InfoBoxWrapper.

Done


Agility rooftop course laps per hour inconsistencies

Describe the bug
Laps per hour is inconsistent to the true laps per hour see screenshot for example
Expected behavior
Doing my example of 1 hour of laps on agility course for example 1 hour doing 64 laps. Should yield a 64 laps per hour estimate
Screenshots

The agility plugin estimates laps per hour from the 10 previous lap completions. The discrepancy would be from slowing down slightly for the last 10 laps of the hour.
I'm not sure this counts as a bug, but the behaviour could be communicated to the player.

10 laps seems like a very small amount considering it's cheap to increase that number and prevent people from thinking the estimation is as wrong as it is sometimes.


move to ASGI

move the deployment to ASGI to integrate the ws and wsgi servers in order to facilitate the "Flash" implementation.

this cascaded into a new implementation of the ws handler as the ASGI standard imposes some constraints on structure


Mismatch between crates.io and this repo: version and deps

Hello,
Thank you for creating this work.  It's proving to be quite handy for making and applying patches!
While experimenting, I noticed that the version of bidiff listed on crates.io is set to 1.0.0.
Meanwhile, this repo's Cargo.toml shows a version of 0.1.0.
What's more, there is a slight mismatch in the dependencies, as well: rayon, log, and proptest (dev dep) have slightly higher versions.
Would it be possible to merge the outstanding changes from the crates.io artifact  into this repository's master branch?

A case of having forgotten to push. fixed!

Very much appreciated!
Happy holidays and Happy New Year 🎄 🌟


[Backport] Velocity 931 update secure classlist

depends on #22

@wglasshusain  @cesarhernandezgt  will this patch be available sometime soon?  would like to use in our product.

@wglasshusain @cesarhernandezgt will this patched version be available sometime soon? would like to use in our product.

You have not responded to the change requests.

@wglasshusain @cesarhernandezgt will this patched version be available sometime soon? would like to use in our product.

You have not responded to the change requests.

hi @michael-o  I believe your change request was to the PR creator (cesar?)

@wglasshusain @cesarhernandezgt will this patched version be available sometime soon? would like to use in our product.

You have not responded to the change requests.

hi @michael-o I believe your change request was to the PR creator (cesar?)

True, though you can fork and update the patch.

Closing this PR, as it has been updated elsewhere.


An exclusion scenario that should be added to "Find My Mouse"（“查找我的鼠标”中应添加的一种排除情况）

Description of the new feature / enhancement
应添加一个可选项：当鼠标被按下时，不会激活“查找我的鼠标”
An optional option should be added: "Find My Mouse" will not be activated when the mouse is pressed down
Scenario when this would be used?
如果加入这个功能的话，我会保持开启
If this feature is added, I will keep it on
Supporting information
需要在屏幕上快速来回拖动一些元素时，如窗口、文件，仍然会激活“查找我的鼠标”。通常来说，需要晃动来查找鼠标时，人们并不会按下鼠标；一般来说按下鼠标快速晃动的时候都是刻意的。
When you need to quickly drag some elements back and forth on the screen, such as windows and files, "Find My Mouse" will still be activated. Generally speaking, when it is necessary to shake the mouse to search, people do not press the mouse. And when pressing the mouse and at the same time quickly shaking it, it is most likely deliberately.

/dup #18529


Update Authors in ‘utopia-php/pay’

please consider this for hacktoberfest 2022

@christyjacob4 would you please merge this when you get a chance?

THANK YOU! All changes merged 🥳
Please reach out to me on our Discord server if you would like to claim your Appwrite swags! As a way of saying thank you, we would also love to invite you to join the Appwrite organization on GitHub. Please share your GitHub username with us on Discord.
You can accept the invite by visiting https://github.com/orgs/appwrite/invitation. By joining our team, you will officially be an Appwrite maintainer on GitHub.
You can change your membership visibility settings, so your new Appwrite team membership badge will show up on your personal GitHub profile.
Please feel free to look for more PRs you might be interested in helping with on our long list of Hacktoberfest friendly issues and help make Appwrite better :)


remove MPL packages

follow up: https://github.com/envoyproxy/gateway/pull/4157
cc @shahar-h

+------------------------------+------+-----------+---------+---------+--------+
| OSV URL                      | CVSS | ECOSYSTEM | PACKAGE | VERSION | SOURCE |
+------------------------------+------+-----------+---------+---------+--------+
| https://osv.dev/GO-2024-3105 |      | Go        | stdlib  | 1.22.5  | go.mod |
| https://osv.dev/GO-2024-[31](https://github.com/envoyproxy/gateway/actions/runs/10747767939/job/29810620873?pr=4161#step:4:32)06 |      | Go        | stdlib  | 1.22.5  | go.mod |
| https://osv.dev/GO-2024-3107 |      | Go        | stdlib  | 1.22.5  | go.mod |
+------------------------------+------+-----------+---------+---------+--------+

will fix it in separated one.


tools/c7n_guardian - guard duty handle pre-invitation target accounts in a disabled state

fixes #2344

not clear this is needed, closing for now.


Polish Translation Update 2

pl_pl.json
At the moment of making that PR im on the phone,so im dropping the .json file that i downloaded from my fork]
Proposed Changes
-added translation for partial dl wolf
-added translation for the new advancement

im sorry if i messed something up

ok, actually writing something in "Proposed Changes" is optional

understood,i just got used to do that


Add :status field with color as a default

I love the dev config, only I want it to have a timestamp as well.
I know that if i copy the dev config manually, I can simply add :date[iso], but then I lose the awesome colors of the response codes.
Can you either add another default format which is the dev config with a timestamp or can you simply make a :status field that by default has color? e.g. :colored-status

You can see how the dev format is defined in the source code of morgan:
morgan.format('dev', function developmentFormatLine (tokens, req, res) {
  // get the status code if response written
  var status = headersSent(res)
    ? res.statusCode
    : undefined

  // get status color
  var color = status >= 500 ? 31 // red
    : status >= 400 ? 33 // yellow
    : status >= 300 ? 36 // cyan
    : status >= 200 ? 32 // green
    : 0 // no color

  // get colored function
  var fn = developmentFormatLine[color]

  if (!fn) {
    // compile
    fn = developmentFormatLine[color] = compile('\x1b[0m:method :url \x1b[' +
      color + 'm:status \x1b[0m:response-time ms - :res[content-length]\x1b[0m')
  }

  return fn(tokens, req, res)
})

All that is needed is to get the status code and decide a color accordingly.

Yea, you can always make your own format that replicates the colors or if you would like you can always make a pull request to add it here :+1:

@dougwilson Got a start on it, but struggling with failing unit tests on colored string assertions. Could use help if you've got time https://github.com/expressjs/morgan/pull/175

Hi @toymachiner62 I guess I misunderstood your request. I was under the assumption you were going to make a new token called :colored-status so you can use colored status in custom formats. The :status token cannot have colors because the formats using them must be color-less as these are written to logs and read by existing ecosystem log parsing software (which is why we offer out-of-the-box support for things like "Apache" style logs as this is what existing parsing software expects). Including the color control characters into the log files will break the parsing software.

@dougwilson what about #174 with a new token?


      /Users/user/.npm/_logs/2020-05-15T12_44_24_633Z-debug.log
husky > pre-commit hook failed (add --no-verify to bypass)

In the above example I used https://github.com/typicode/husky#readme, but I assume any other pre-commit hook will work.

I'm on it.

Added a basic implementation for bypassing failed git hooks (using --no-verify flag). Also added this rule for 3 commands which can fail due to a hook, namely am, commit and, push.
Can @dekelb or someone else please test this, and see if it works as intended.
Thank you.

Seems like it doesn't work (sorry it took some time to test it).
➜  REPO git:(feature/rows-dnd) ✗ git commit demo/demo.js -m "working example"
husky > pre-commit (node v13.11.0)
....
....
✖ 5 problems (5 errors, 0 warnings)

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>eslint: `eslint src/** -c ./configs/.eslintrc`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>eslint script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/{me}/.npm/_logs/2020-06-02T22_51_40_019Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>lint: `npm run eslint && npm run tsc`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>lint script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!       Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>eslint script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/{me}/.npm/_logs/2020-06-02T22_51_48_141Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>lint: `npm run eslint && npm run tsc`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>lint script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!       The response from a pre-commit hook may take way too long to produce useful output. Hence, this rule has to be output-independent. But then, it should have a lower priority, which would throw it to the back of the queue of suggestions.

Agreed @scorphus, these hooks can take a long time to execute.
I'll try to complete the PR asap. I'm a little busy right now.

@scorphus I think this was resolved with #1097 and should be closed.

Thanks for contributing, @divykj <3


Introduce SkipList Dump() and Load() method

Hi,
It would be helpful if we can have Dump() and Load() method in skiplist. It would help serialize/deserialize a skiplist to a disk.

That's a reasonable explanation. For my purpose, I am using strings as both key and values and implemented serializer / deserializer locally.
Thank you!


[network]: missing reference of trusted root certificate in Backend http settings in Application Gateway

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
For Application Gateway resource, CLI allows to create root-cert sub resource using
az network application-gateway root-cert create
Additionally, this resource needs to be referenced in the backendHttpSettings sub-resource (same as auth-certs (Authentication Certificates)) which can't be done with options provided.
az network application-gateway http-settings create -h

Command
    az network application-gateway http-settings create : Create HTTP settings.

Arguments
    --gateway-name      [Required] : Name of the application gateway.
    --name -n           [Required] : The name of the backed HTTP settings.
    --port              [Required] : The port number.
    --resource-group -g [Required] : Name of resource group. You can configure the default group
                                     using `az configure --defaults group=<name>`.
    --affinity-cookie-name         : Name used for the affinity cookie.
    --auth-certs                   : Space-separated list of authentication certificates (names or
                                     IDs) to associate with the HTTP settings.
    --connection-draining-timeout  : The time in seconds after a backend server is removed during
                                     which on open connection remains active. Range: 0 (disabled) to
                                     3600.
    --cookie-based-affinity        : Enable or disable cookie-based affinity.  Allowed values:
                                     Disabled, Enabled.
    --enable-probe                 : Whether the probe is enabled.  Allowed values: false, true.
    --host-name                    : Host header sent to the backend servers.
    --host-name-from-backend-pool  : Use host name of the backend server as the host header.
                                     Allowed values: false, true.
    --no-wait                      : Do not wait for the long-running operation to finish.
    --path                         : Path that will prefix all HTTP requests.
    --probe                        : Name or ID of the probe to associate with the HTTP settings.
    --protocol                     : The HTTP settings protocol.  Allowed values: Http, Https.
                                     Default: http.
    --timeout                      : Request timeout in seconds.

To Reproduce
N/A
Expected behavior
Add --root-certs flag to the following command (similar in working to auth-certs flag)
az network application-gateway http-settings create --root-certs
Environment summary
Installation Method: N/A
az --version
azure-cli                         2.0.66
network                            2.5.1

Additional context
Issues tracking root-cert feature:
https://github.com/Azure/azure-cli/issues/7528
https://github.com/Azure/azure-cli/issues/8244

This is arising from a customer issue. Let's keep this on priority.

This property can currently be updated using the --set argument in az network application-gateway http-settings update. Example:
az network application-gateway http-settings update -g demo2019 --gateway-name WAF1 -n setting2 --host-name "xyz.com" --set trustedRootCertificates='[{"id": "/subscriptions/a932c0e6-b5cb-4e68-b23d-5064372c8a3c/resourceGroups/demo2019/providers/Microsoft.Network/applicationGateways/WAF1/trustedRootCertificates/cert2"}]'

@akshaysngupta Hello, from which api version supports trusted_root_certificates in the application gateway ?


add poster at the top of the message

as discussed in #246 I've moved the author/reply author information to the top of the panels.
Resulting layout:

@driesvints I've implemented your requested changes and extracted the tags and avatar into seperate blade files. pls review again

I pushed a commit with some small changes. I re-added the avatar for the thread author in the end because it looked weird without it. Sorry about that.
Thanks for your work on this! Looks much better :)

Omg, thanks to everyone, really is so much more useful now #gamechanger


Dynamically setting Modals visibility crashing iOS Simulator whilst debugging

Description
I have a Modal within my React Native app which has it's visible prop set via a state property. When using iOS Simulator with Debug JS Remotely and trying to toggle the visibility, iOS Simulator crashes. When disabling debugging, the application works as expected.
Here is the error that I am receiving in my console
Exception 'shadowView (for ID 22) not found' was thrown while invoking replaceExistingNonRootView on target UIManager with params (
    22,
    36
)

Downgrading to React Native 0.41.0 seems to rectify the aforementioned problem. However, when trying clicking Shake Gesture on iOS Simulator, it crashes. To reproduce this, simply stop the Package Manager, change 0.42.0 to 0.41.0 in package.json, run a yarn install and once finished, react-native run-ios.
Reproduction
You can find the error at https://github.com/hannigand/modal (within index.ios.js) - Simply clone to repository and do a yarn install, subsequently run react-native run-ios. Once iOS Simulator has opened, click on Hardware in the Toolbar and then Shake Gesture. Once the iOS menu opens, click Debug JS Remotely and press the Toggle Modal button.
Additional Information

React Native version: 0.42.0
Platform: iOS
Operating System: Mac OSX
Dev tools: XCode 8.2.1, Chrome 56, Chrome Developer Tools,

#12768


Hotfix/type

Jira issue link: link

check applicable boxes

[ ] I have made tests to match the user stories
[ ] This code does not require tests that match user stories

Coverage remained the same at 57.258% when pulling 9ae21fe884cc383c29b53ea4cfe923bc7a985202 on hotfix/type into 52c708e7872ec56fbabf0ab31ebd5d93ae68b7be on develop.


[xy-chart] Add xy-chart package

This PR adds the xy-chart package for re-usable + composable + themeable charts with x/y-axes. It leverages vx for low-level components 💯 . Check out the examples to look at the API.

next steps:

[ ] address any feedback from @hshoff @andyfangdz
[ ] merge this + publish the first version
[ ] refactor @andyfangdz's PR, let me know if you want me to have a go at this or if you want to, happy either way :)
[ ] add more series so we can use it in DLS: stacked / grouped bar, etc.
[ ] refactor repo to use jest instead of mocha -> add some tests 🎉

note: proper axis display here depends on this vx PR
cc @elibrumbaugh

This is really amazing! I think it's safe to close my original PR and implement charts based on xy-chart 😄.
The only concern I have right now is for smoothing curve in the LineSeries plot. D3's default curve functions (curveBasis, etc.) are for controlling curve, rather than representing the local estimate value for the data. What this means is that all of the curve functions in D3, when applied for curve smoothing, will try too hard to make sure the curve go through each of the points and skews the data in the process (a comparison can be seen here). These methods will make visually appealing curves, but the curves don't represent any meaningful value.
As can be seen in this discussion of Mike Bostock in d3-shape(https://github.com/d3/d3-shape/issues/43), some other method should be used for the purpose of line smoothing (local regression, median filter, etc.). Part of my PR addresses this problem by bringing in the Local Regression kernel from science.js. You can see from my example here that the smoothed curve doesn't try to go through any of the points, but instead tries to minify the sum of squared error from each point to the curve.
What I'm concerned about this feature is whether this feature is too niche to be included the package. I feel like smoothing curves is a common feature, yet most people use the wrong method (e.g., curveBasis), so it makes sense to include it in the package and as a feature to market. What do you think?
Otherwise, LGTM!

@andyfangdz as discussed on slack I went ahead and merged this and completely agree that something like a RegressionSeries would be really useful here 🙌


Can we have platformAndArch string in error log?

What are you trying to achieve?
I mean this string: https://github.com/lovell/sharp/blob/master/lib/sharp.js#L3
If its have error here it's possible platformAndArch to be different from sharp-XXX.node in /build/Release/ but I dont know what is platformAndArch output
try {
  module.exports = require(`../build/Release/sharp-${platformAndArch}.node`);
} catch (err) {

This line miss me:
} catch (err) {
  help.push('current platformAndArch: ' + platformAndArch);
  throw new Error(help.join('\n'));
}

The value should implicitly appear as part of the err.message already, e.g. if I delete the build directory and attempt to require('sharp') I see the following on Linux x64:
Error:
Something went wrong installing the "sharp" module

Cannot find module '../build/Release/sharp-linux-x64.node'
Require stack:
...

Is there a scenario where this isn't happening?
I'm happy to make this value explicit too, but want to make sure I understand the underlying problem first as there could be additional things we can output to help.

I have packaged Electron App (with asar) and this error on Linux platform only (on Mac and Windows I dont have errors):
Tagspaces WS: /opt/TagSpaces/resources/app.asar/node_modules/sharp/lib/sharp.js:30
Tagspaces WS:   throw new Error(help.join('\n'));
Tagspaces WS:   ^
Tagspaces WS: Error:
Tagspaces WS: Something went wrong installing the "sharp" module
Tagspaces WS: libvips-cpp.so.42: cannot open shared object file: No such file or directory
Tagspaces WS: Possible solutions:
Tagspaces WS: - Install with the --verbose flag and look for errors: "npm install --ignore-scripts=false --verbose sharp"
Tagspaces WS: - Install for the current runtime: "npm install --platform=linux --arch=x64 sharp"
Tagspaces WS: - Consult the installation documentation: https://sharp.pixelplumbing.com/install
Tagspaces WS:     at Object.<anonymous> (/opt/TagSpaces/resources/app.asar/node_modules/sharp/lib/sharp.js:30:9)
Tagspaces WS:     at Module._compile (node:internal/modules/cjs/loader:1110:14)
Tagspaces WS:     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1140:10)
Tagspaces WS:     at Module.load (node:internal/modules/cjs/loader:982:32)
Tagspaces WS:     at Module._load (node:internal/modules/cjs/loader:823:12)
Tagspaces WS:     at Function.c._load (node:electron/js2c/asar_bundle:5:13331)
Tagspaces WS:     at Module.require (node:internal/modules/cjs/loader:1006:19)
Tagspaces WS:     at require (node:internal/modules/cjs/helpers:93:18)
Tagspaces WS:     at Object.<anonymous> (/opt/TagSpaces/resources/app.asar/node_modules/sharp/lib/constructor.js:8:1)
Tagspaces WS:     at Module._compile (node:internal/modules/cjs/loader:1110:14)

It appears that sharp-linux-x64.node is installed correctlly in asar archive

maybe platformAndArch variable is different from linux-x64 ??

I found my issue: https://github.com/lovell/sharp/issues/2582
stanimir@debian:~/structmedia/tagspaces$ ldd node_modules/sharp/build/Release/sharp-linux-x64.node
        linux-vdso.so.1 (0x00007fff3bfed000)
        libvips-cpp.so.42 => /home/stanimir/structmedia/tagspaces/node_modules/sharp/build/Release/../.././vendor/8.11.3/linux-x64/lib/libvips-cpp.so.42 (0x00007f781ab89000)
        libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f781a807000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f781a503000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f781a2ec000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f781a0cf000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f7819d30000)
        libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007f7819b19000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f7819915000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f781bf42000)

@lovell what about to change this line:
 const help = ['', 'Something went wrong installing the "sharp" module for platform:' + platformAndArch, '', err.message, '', 'Possible solutions:'];

Added via commit https://github.com/lovell/sharp/commit/96992845ed25b74ab6ee1b82a9a1b443b86f6931 - this will be in v0.30.0

v0.30.0 now available with this feature.


Can't update fields of an already updoaded media using the S3 adapter

Link to reproduction
No response
Payload Version
3.0.0-beta.56
Node Version
20.12.2
Next.js Version
15.0.0-rc.0
Describe the Bug
Whenever I want to update a field (e.g. Alt field), I get a 500 error when I try to submit the form.
Here is the log from the console

Reproduction Steps
Install Payload v3.0.0-beta.56 with the default Media Collection
Install @payloadcms/storage-s3 v3.0.0-beta.56
Set up S3 storage (I tried both on minIO and AWS S3 and I get the same behavior)
Upload a first Media
Update the Alt field and submit the form
Adapters and Plugins
@payloadcms/db-postgres v3.0.0-beta.56
@payloadcms/storage-s3 v3.0.0-beta.56

Any news on this one ? Is there anything I can help you with @PatrikKozak ?

Hey @fofoy - we'll get right on this!

Hi @fofoy - I did some testing on my end and was not able to reproduce the above issue.
It may have something to do with your S3 storage setup - do you have a reverse proxy setup?
Is this purely local?
Just want to get some additional information before I can dig deeper into this - thank you!

Hi @PatrikKozak I have the same issue in local (using a dockerized MinIO instance) and on my staging environment using an AWS S3 bucket so it doesn't seem to be a setup issue.

@fofoy Thanks for the info - hmm unfortunately there isn't enough here to fully understand what could be causing this issue.
A couple things though, could you try and log out some of the info in that function where the error is coming from (in your node_modules) - this may be able to give us some more information
Also, could you update your payload packages versions to latest (just in case) - I'd like to get to the bottom of this but just will need more info to continue

@PatrikKozak Thanks, I had the time to update my project to latest beta version 91 and the problem remains, I'll dig further to see where it's going wrong and I'll let you know.

Hi @PatrikKozak here is the result of logging the Promise getExternalFile on line 41 of generateFileData.js file:
Promise {
  <pending>,
  [Symbol(async_id_symbol)]: 652801,
  [Symbol(trigger_async_id_symbol)]: 652790,
  [Symbol(kResourceStore)]: {
    url: {
      pathname: '/api/media/c26034b9-71ab-4e88-8ff1-2dfc5a980261',
      search: '?depth=0&fallback-locale=null'
    },
    headers: [Getter],
    cookies: [Getter],
    mutableCookies: [Getter],
    draftMode: [Getter],
    reactLoadableManifest: {},
    assetPrefix: '',
    afterContext: undefined,
    isHmrRefresh: undefined,
    serverComponentsHmrCache: undefined
  },
  [Symbol(kResourceStore)]: {
    isStaticGeneration: false,
    page: '/(payload)/api/[...slug]/route',
    fallbackRouteParams: null,
    route: '/api/[...slug]',
    incrementalCache: IncrementalCache {
      locks: Map(0) {},
      unlocks: Map(0) {},
      hasCustomCacheHandler: false,
      dev: true,
      disableForTestmode: false,
      minimalMode: false,
      requestHeaders: [Object],
      requestProtocol: 'https',
      allowedRevalidateHeaderKeys: undefined,
      prerenderManifest: [Object],
      revalidateTimings: [SharedRevalidateTimings],
      fetchCacheKeyPrefix: '',
      cacheHandler: [FileSystemCache]
    },
    isRevalidate: false,
    isPrerendering: undefined,
    fetchCache: undefined,
    isOnDemandRevalidate: undefined,
    isDraftMode: undefined,
    requestEndedState: undefined,
    revalidate: 0,
    tags: [
      '_N_T_/layout',
      '_N_T_/(payload)/layout',
      '_N_T_/(payload)/api/layout',
      '_N_T_/(payload)/api/[...slug]/layout',
      '_N_T_/(payload)/api/[...slug]/route',
      '_N_T_/api/media/c26034b9-71ab-4e88-8ff1-2dfc5a980261'
    ],
    nextFetchId: 2
  },
  [Symbol(kResourceStore)]: undefined,
  [Symbol(kResourceStore)]: undefined,
  [Symbol(kResourceStore)]: undefined,
  [Symbol(kResourceStore)]: { isAppRoute: true, isAction: false }
}

and here is the actual error when trying to fetch the file :
TypeError: fetch failed
     at node:internal/deps/undici/undici:12618:11
     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
     at async getExternalFile (webpack-internal:///(rsc)/../node_modules/.pnpm/payload@3.0.0-beta.108_graphql@16.9.0_monaco-editor<EMAIL_ADDRESS> a48-202_bgnc5eiwwsaz2mukappcno4s3m/node_modules/payload/dist/uploads/getExternalFile.js:18:21) {
   cause: Error: connect ECONNREFUSED <IP_ADDRESS>:443
       at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1605:16)
       at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
     errno: -111,
     code: 'ECONNREFUSED',
     syscall: 'connect',
     address: '<IP_ADDRESS>',
     port: 443
   }
 }
  ⨯ unhandledRejection: TypeError: fetch failed
     at node:internal/deps/undici/undici:12618:11
     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
     at async getExternalFile (webpack-internal:///(rsc)/../node_modules/.pnpm/payload@3.0.0-beta.108_graphql@16.9.0_monaco-editor<EMAIL_ADDRESS> a48-202_bgnc5eiwwsaz2mukappcno4s3m/node_modules/payload/dist/uploads/getExternalFile.js:18:21) {
   cause: Error: connect ECONNREFUSED <IP_ADDRESS>:443
       at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1605:16)
       at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
     errno: -111,
     code: 'ECONNREFUSED',
     syscall: 'connect',
     address: '<IP_ADDRESS>',
     port: 443
   }
 }
  ⨯ unhandledRejection: TypeError: fetch failed
     at node:internal/deps/undici/undici:12618:11
     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
     at async getExternalFile (webpack-internal:///(rsc)/../node_modules/.pnpm/payload@3.0.0-beta.108_graphql@16.9.0_monaco-editor<EMAIL_ADDRESS> a48-202_bgnc5eiwwsaz2mukappcno4s3m/node_modules/payload/dist/uploads/getExternalFile.js:18:21) {
   cause: Error: connect ECONNREFUSED <IP_ADDRESS>:443
       at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1605:16)
       at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
     errno: -111,
     code: 'ECONNREFUSED',
     syscall: 'connect',
     address: '<IP_ADDRESS>',
     port: 443
   }
 }

So it seems like it's something to do with the network. I'm running everything in Docker with several containers for the postgres db, the S3 instance (minIO) and the payload admin but it also does the same on our dev cluster (kubernetes) with an AWS S3 instance connected to it.

Hi @PatrikKozak and @fofoy
I'm having the same problem as well. I can't edit any fields of an already uploaded file, and I got the same error as described above.
We also run our environments in kubernetes and we use Google cloud storage for storing files. I have however noticed that when I'm running payload locally (and still using google cloud storage for storing files) it works. When I'm running payload in docker I get the same error we got in our kubernetes environments.
@fofoy Have you found any temporary workaround for this problem?

Hi @nickejoha, I didn't have the time to dig any further than this yet as I need to make progress on my current project but that's definitely something that needs to be sorted, I'll try to invest more time in a bit.

I also attempted to recreate this issue, but I was unable to. I'm not sure there's much more we can do on our end to troubleshoot this.
If you have any more info or a way to consistently reproduce that would be helpful.

Hi @denolfe, I updated to the latest version of beta v122 and the same problem remains, let me know if I can help you in any way to help you debug this.

I think we have found the issue here and we have implemented a workaround.
In short, the problem in our case seems to be connected our firewall in Google cloud plattform and locally that we use a different external port in our docker build.
The problem here seems to be is that when we edit a field of media file that has been uploaded already, payload tries to fetch the file but the fetch fails. The problem in our case was that when payload tries to fetch the file, it uses the external url which works fine when used from a frontend client or when running a docker config that doesn't alter the ports, but because the request is executed from the container itself the url is invalid. In our local docker config the external url is localhost:3077, but inside the container the app runs on port 3000. So when we access file from outside the container localhost:3077 is valid, but when trying to fetch the same file from inside the container the url is invalid because the application runs on port 3000. The problem in our Google cloud plattform was due the same fact that the external url isn't valid from inside the cluster.
So with that figured out we implemented a bit of a hack as a workaround. By temporarily changing the files url to a valid url (from the containers perspective) with a hook, and the error is gone and editing the file works :)
import { CollectionBeforeOperationHook, CollectionBeforeReadHook } from 'payload'

const fixMediaUrl = (req: any) => {
  if (req.data?.url) {
    const prefix = process.env.CMS_INTERNAL_URL || ''
    if (req.data.url.startsWith('/')) {
      req.data.url = prefix + req.data.url
    }
    if (req.data?.sizes) {
      for (const key in req.data.sizes) {
        if (req.data.sizes[key].url?.startsWith('/')) {
          req.data.sizes[key].url = prefix + req.data.sizes[key].url
        }
      }
    }
  }
}

export const fixMediaUrlOperation: CollectionBeforeOperationHook = async ({ req }) =>
  fixMediaUrl(req)

export const fixMediaUrlRead: CollectionBeforeReadHook = async ({ req }) => fixMediaUrl(req)


Heroic Knuckle Bones (Keepsake) counts as Old Grudge (Hades Boon)

You can do it Jow!!

Fixed in current release! Thank you for reporting it 🤩


Always "Cheking..."

it never shows the channels live on archlinux-gnome, just shows "checking..." all the time
I cloned the git and made a sudo ./setup.sh.

Hey, can you show me the output?

Here it is, and the icon takes some time to appear, like 3 minutes.

This is because you are using python3.4, but indicator is written for python2.7. I have plans to make it available for both versions, but I don't know when exactly.
If you're willing to implement by yourself, pull requests are always welcome :)

Well... I'm not even a beginner in Python so I can't, but I solved my problem:
I searched for the arch wiki and it says: Any program requiring Python 2 needs to point to /usr/bin/python2, instead of /usr/bin/python, which points to Python 3.
So, I changed that, you just have to change the line to "#!/usr/bin/python2" and it will use the 2 version (I have both them installed).
and it worked perfectly :)
thank you for the answer, sorry for the bad english.

Awesome, glad to hear everything is working for you!


Update README.rst

Corrected the command names

Thanks for the contribution! this is a read-only mirror. please read the contribution guide.


[Identity] Expose MsaPassthrough as an option

This PR exposes the WindowsBrokerOptions.MsaPassthrough option of MSAL to two credential option types of Azure.Identity.BrokeredAuthentication libraries so that it can support MSA account.
Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

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


Fix inconsistent redirects for policies

In New World Publishing, applications send content to the publishing-api, which forwards it to the content-store and also registers routes for the document with the router-api.
However, in the past apps have sent routes directly to router-api. This has happened frequently when setting up redirects.
It means we have a bunch of routes in the router for which either no content items exist, or for which the content item doesn't match the content item.
The rake task added in the first commit is used to find a subset of the last case. It finds policies with format "placeholder" in the content-store that are actually redirects. The outputted information is used to bring the database up-to-date by turning the content items into proper redirect content items.
I've extracted the InconsistentRedirectFinder to enable us to re-use the code to fix other inconsistent redirects. The rake data_hygiene:inconstent_policy_redirects task is temporary and will be removed once we've fixed them.
The motive to fix the policies now is that they have duplicate content_ids and we need to fix that for tagging.
Trello: https://trello.com/c/fhz6hWaA/367-fix-duplicate-content-id-for-policies

Since I've also added https://github.com/alphagov/content-store/commit/afe84fa60f6404dded1331bac9be8a2d5e3e529d, I've updated PR title + description.

This makes more sense - thanks.


idea plugin and custom configuration bug

Hi,
When defining a custom configuration for integration tests:
configurations {
    integrationTestImplementation {
        extendsFrom testImplementation
        canBeResolved = true
    }
}

I get the following exception when refreshing the project in intellij:
> Resolving dependency configuration 'integrationTestImplementation' is not allowed as it is defined as 'canBeResolved=false'.
  Instead, a resolvable ('canBeResolved=true') dependency configuration that extends 'integrationTestImplementation' should be resolved.

After debugging I noticed the idea task fails.
Expected Behavior
The idea task should not fail as canBeResolved=true
Current Behavior
The idea task failed.
Context
I found a solution: I moved the configuration block in the build.gradle file next to the idea configuration block and it fixed the issue.
Steps to Reproduce
Example project: https://github.com/rozza/gradleIdeaConfigurations
Run ./gradlew idea to reproduce the issue.  Move the custom configuration block next to the idea block and re run and it succeeds.
Your Environment
Build scan URL: https://scans.gradle.com/s/guslvqrxidqxc

I think I have an explanation.
The example build script defines two things:

a custom integrationTest source set

sourceSets {
    integrationTest {
        ...
    }
}

configuration for a integrationTestImplementation configuration scope

configurations {
    integrationTestImplementation {
        ...
    }
}

Without defining the custom source set, the latter snippet would create a new configuration scope. However, the Java Gradle plugin also creates an integrationTestImplementation configuration for each source set, which is not configurable (hence the canBeResolved=false error message).
You can fix the issue in two ways:

(recommended) add the resolvable runtime classpath configuration to the idea module: idea.module.scopes.TEST.plus += [ configurations.integrationTestRuntimeClasspath ] and delete integrationTestImplementation {... } from the configurations block
rename your custom dependency scope (e.g. myIntegrationTestImplementation)


[INTERNAL] Align jsdoc publish with UI5

Align lib/processors/jsdoc/lib/ui5/template/publish.cjs with OpenUI5

coverage: 94.523%. remained the same
when pulling 800f903c533744a931a020e0d8739ff9b7641f56 on align-jsdoc
into b4a6f7275abdeffaa2735b4cd7c87fe8222a7bd6 on main.


Concierge configuration

Add visual indicators to comments on PRs, and update signature to indicate where configurations are stored.
@mramato

@ggetz, thanks for the pull request! Maintainers, we have a signed CLA from @ggetz, so you can review this at any time.
I noticed that CHANGES.md has not been updated. If this change updates the public API in any way, fixes a bug, or makes any non-trivial update, please add a bullet point to CHANGES.md and comment on this pull request so we know it was updated. For more info, see the Pull Request Guidelines.

I am a bot who helps you make Cesium awesome! Thanks again.

Thanks.

Forgot something.  Can you open a separate PR to ignore the .concierge directory in .npmignore and also make sure it's not in the generated zip file.  Thanks.


All raster pairwise tests

[x] sgVerify1

[x] sgVerify2

[x]  sgVerify3

[x]  sgVerify4

[x]  sgVerify5

[x]  sgVerify6

[x]  sgVerify7

[x] sgVerify8

[x] sgVerify9

[x] sgVerify10

[x] sgVerify11

[ ] sgVerify12

[ ] sgVerify13

[x] sgVerify14

[x] sgVerify15

sgVerify12 is basically the same as 15, but 12 uses resistances shortcut with will be done once #5 is done

sgVerify13 has input in a different format (INI file). In the domain #25


Extensions: Make GetFullPathOfMember method public

Description

GetFullPathOfMember under ExpressionExtensions is currently internal, meaning it cannot be used for custom IFormComponent implementations. This is a very niche usage but I am working on an adaptation of TinyMCE.Blazor and need the component to implement IFormComponent as well as use fluent validation. At present, I must copy this entire extension method in order to use it in my project. The other utilities are public, so I don't think there is a good reason for this one to be internal.
How Has This Been Tested?

Not applicable
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[x] I've added relevant tests.

@henon Can you peek at this? It's really simple. :)


Serve the website using Nginx

https://ember-cli.com/user-guide/#deployments

http://iamstef.net/ember-app-kit/guides/deployment.html
Has a section on deploying ember apps via nginx.

nginx is really simple, lightweight, and flexible.

It may be worth highlighting why you feel niginx is needed. While I also agree niginx is a nice, simple, web server, ember is built on nodejs which it's self can be a flexible web server.
What is to be gained from using niginx that node and ember don't provide out of the box or with some minor tweaks?

The super douper light weight Ember web server isn't designed for production environments (which is effectively what Egee.io is). Niginx offers a couple things such as DDOS protection and redirection for error codes.

Yeah egee weren't you having issues with Ember just crashing out of nowhere?

I'm not sure what @GhostSquad57 is smoking but I've never had ember abruptly crash out on me.

 THANKS ghostsquad57

Egee:

How do I do this

Me:

Move the root of the server to nginx's root defined in default and run nginx

Egee:

Oh, it works

Issue closed


Change location of bootargs.conf

Use the same location as grub.conf, /etc/elemental.
The grub config is backwards compatible and tries to source from /etc/cos/bootargs.conf as well.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 72.56%. Comparing base (3028919) to head (0a55eb9).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2013   +/-   ##
=======================================
  Coverage   72.56%   72.56%
=======================================
  Files          76       76
  Lines        8907     8907
=======================================
  Hits         6463     6463
  Misses       1910     1910
  Partials      534      534

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


socket close event?

its absolutely necessary.

Yes, not to be polluting (weighing) the server or client with unnecessary socket connections

e.g server down or restart.


Fixes bower json file issue

Fixes issue with bower json file error

duplicate of #23 , thanks for the help 👍

Hi @srk289
This is fixed in version v2.1.3.
Thanks again for your help.


Fix memory leaks

Hey, I noticed that there were still some unresolved memory issues after this thread: #89
In particular:

GameMaps dynamically allocate a large number of Cells in every constructor call, but never free the Cells, resulting in a memory leak.
Agents allocate Cities, and Cities allocate CityTiles, but Agents are the ones who clean up everything, which makes the ownership a little confusing. This might also cause a memory leak if you re-use the Agent class multiple times (e.g. in a custom benchmarker tool) and forget to call resetPlayerStates at the end.

I verified 1. in valgrind. A simple solution to the problem would just be to store objects by value on the stack, rather an dynamically allocating them. Now if for some reason you really want dynamic allocation, then we could instead use the RAII pattern, e.g. with a unique_ptr, but that doesn't sound like it would be an improvement.
I just eyeballed problem 2., but I think this refactor makes sense. A simple solution is to clearly define who owns which blocks of memory, and denote ownership by using value member variables. In this PR, I've arranged it so that Cities own CityTiles (and are responsible for their cleanup), and Players own Cities (and are responsible for their cleanup). That way, when you call players[team].cities.clear(); you guarantee you have cleaned up all the Citytiles as well.
Let me know if you have any feedback. If you're trying to reduce code churn in main.cpp, I can refactor City::citytiles a little bit so that it will still store pointers and require no code changes to main.cpp.

This looks great! Thanks for the fixes, our c++ kit was always poorly written / not really checked much.
Also seems like API hasn't changed either so that's good!

Glad to help!


training fails when using bfloat16

Description
I cannot train a transformer_base model using bfloat   type for both activation and weights using GPU  (GTX 1080Ti).
From the error I got
ValueError: Tensor conversion requested dtype bfloat16 for Tensor with dtype float32: 'Tensor("transformer/parallel_0_5/transformer/symbol_modality_8374_512/shared/ExpandDims:0", shape=(?, ?, 1, 1), dtype=float32, device=/device:GPU:0)'

It seems that in some part there is (at least) one wrong/missing cast.
Commands for replicability and full log are below.
Is this a bug in Tensor2Tensor? or in TensorFlow?
Is it actually impossible to use bfloat16 on gpu?
Or is there any error I am making?
Environment information
OS: Ubuntu 16.04

$ pip freeze | grep tensor
tensor2tensor==1.6.3
tensorboard==1.8.0
tensorflow-gpu==1.8.0

$ python -V
Python 2.7.12

For bugs: reproduction and error logs
# Steps to reproduce:
t2t-datagen --data_dir t2t_data/datagen --tmp_dir ./t2t_data/tmp --problem translate_enfr_wmt_small8k --hparams activation_dtype=bfloat16,weight_dtype=bfloat16

t2t-trainer --data_dir t2t_data/datagen --tmp_dir ./t2t_data/tmp --problem translate_enfr_wmt_small8k --model transformer --hparams_set transformer_base --output_dir ./t2t_data/model --local_eval_frequency=500 --train_steps=1000 --worker_gpu=1 --hparams batch_size=3072,activation_dtype=bfloat16,weight_dtype=bfloat16

nothing change if I do not use "--hparams activation_dtype=bfloat16,weight_dtype=bfloat16"   in data generation.
# Error logs:
/usr/local/lib/python2.7/dist-packages/h5py/__init__.py:36: FutureWarning: Conversion of the second argument of issubdtype from `float` to `np.floating` is deprecated. In future, it will be treated as `np.float64 == np.dtype(float).type`.
  from ._conv import register_converters as _register_converters
INFO:tensorflow:Overriding hparams in transformer_base with batch_size=3072,activation_dtype=bfloat16,weight_dtype=bfloat16,optimizer=Adafactor
WARNING:tensorflow:From /home/nicola/.local/lib/python2.7/site-packages/tensor2tensor/utils/trainer_lib.py:151: __init__ (from tensorflow.contrib.learn.python.learn.estimators.run_config) is deprecated and will be removed in a future version.
Instructions for updating:
When switching to tf.estimator.Estimator, use tf.estimator.RunConfig instead.
INFO:tensorflow:schedule=continuous_train_and_eval
INFO:tensorflow:worker_gpu=1
INFO:tensorflow:sync=False
WARNING:tensorflow:Schedule=continuous_train_and_eval. Assuming that training is running on a single machine.
INFO:tensorflow:datashard_devices: ['gpu:0']
INFO:tensorflow:caching_devices: None
INFO:tensorflow:ps_devices: ['gpu:0']
INFO:tensorflow:Using config: {'_save_checkpoints_secs': None, '_keep_checkpoint_max': 20, '_task_type': None, '_cluster_spec': <tensorflow.python.training.server_lib.ClusterSpec object at 0x7f76c00c0990>, '_keep_checkpoint_every_n_hours': 10000, '_session_config': gpu_options {
  per_process_gpu_memory_fraction: 0.95
}
allow_soft_placement: true
graph_options {
  optimizer_options {
  }
}
, 'use_tpu': False, '_tf_random_seed': None, '_num_worker_replicas': 0, '_task_id': 0, 't2t_device_info': {'num_async_replicas': 1}, '_evaluation_master': '', '_log_step_count_steps': 100, '_num_ps_replicas': 0, '_train_distribute': None, '_is_chief': True, '_tf_config': gpu_options {
  per_process_gpu_memory_fraction: 1.0
}
, '_save_checkpoints_steps': 500, '_environment': 'local', '_master': '', '_model_dir': './neural_model', 'data_parallelism': <tensor2tensor.utils.expert_utils.Parallelism object at 0x7f76c9da2d10>, '_save_summary_steps': 100}
WARNING:tensorflow:Estimator's model_fn (<function wrapping_model_fn at 0x7f76c003d938>) includes params argument, but params are not passed to Estimator.
WARNING:tensorflow:ValidationMonitor only works with --schedule=train_and_evaluate
WARNING:tensorflow:From /home/nicola/.local/lib/python2.7/site-packages/tensor2tensor/utils/trainer_lib.py:338: __init__ (from tensorflow.contrib.learn.python.learn.experiment) is deprecated and will be removed in a future version.
Instructions for updating:
Please switch to tf.estimator.train_and_evaluate. You will also have to convert to a tf.estimator.Estimator.
WARNING:tensorflow:continuous_train_and_eval (from tensorflow.contrib.learn.python.learn.experiment) is experimental and may change or be removed at any time, and without warning.
INFO:tensorflow:Training model for 500 steps
INFO:tensorflow:Reading data files from t2t_data/datagen/translate_enfr_wmt_small8k-train*
INFO:tensorflow:partition: 0 num_data_files: 100
INFO:tensorflow:Calling model_fn.
INFO:tensorflow:Setting T2TModel mode to 'train'
INFO:tensorflow:Using variable initializer: uniform_unit_scaling
INFO:tensorflow:Transforming feature 'inputs' with symbol_modality_8374_512.bottom
Traceback (most recent call last):
  File "/home/nicola/.local/bin/t2t-trainer", line 32, in <module>
    tf.app.run()
  File "/home/nicola/.local/lib/python2.7/site-packages/tensorflow/python/platform/app.py", line 126, in run
    _sys.exit(main(argv))
  File "/home/nicola/.local/bin/t2t-trainer", line 28, in main
    t2t_trainer.main(argv)
  File "/home/nicola/.local/lib/python2.7/site-packages/tensor2tensor/bin/t2t_trainer.py", line 353, in main
    execute_schedule(exp)
  File "/home/nicola/.local/lib/python2.7/site-packages/tensor2tensor/bin/t2t_trainer.py", line 302, in execute_schedule
    getattr(exp, FLAGS.schedule)()
  File "/home/nicola/.local/lib/python2.7/site-packages/tensorflow/contrib/framework/python/framework/experimental.py", line 64, in new_func
    return func(*args, **kwargs)
  File "/home/nicola/.local/lib/python2.7/site-packages/tensorflow/contrib/learn/python/learn/experiment.py", line 773, in continuous_train_and_eval
    saving_listeners=self._saving_listeners)
  File "/home/nicola/.local/lib/python2.7/site-packages/tensorflow/contrib/learn/python/learn/experiment.py", line 876, in _call_train
    saving_listeners=saving_listeners)
  File "/home/nicola/.local/lib/python2.7/site-packages/tensorflow/python/estimator/estimator.py", line 363, in train
    loss = self._train_model(input_fn, hooks, saving_listeners)
  File "/home/nicola/.local/lib/python2.7/site-packages/tensorflow/python/estimator/estimator.py", line 843, in _train_model
    return self._train_model_default(input_fn, hooks, saving_listeners)
  File "/home/nicola/.local/lib/python2.7/site-packages/tensorflow/python/estimator/estimator.py", line 856, in _train_model_default
    features, labels, model_fn_lib.ModeKeys.TRAIN, self.config)
  File "/home/nicola/.local/lib/python2.7/site-packages/tensorflow/python/estimator/estimator.py", line 831, in _call_model_fn
    model_fn_results = self._model_fn(features=features, **kwargs)
  File "/home/nicola/.local/lib/python2.7/site-packages/tensor2tensor/utils/t2t_model.py", line 922, in wrapping_model_fn
    use_tpu=use_tpu)
  File "/home/nicola/.local/lib/python2.7/site-packages/tensor2tensor/utils/t2t_model.py", line 972, in estimator_model_fn
    logits, losses_dict = model(features)  # pylint: disable=not-callable
  File "/home/nicola/.local/lib/python2.7/site-packages/tensorflow/python/layers/base.py", line 717, in __call__
    outputs = self.call(inputs, *args, **kwargs)
  File "/home/nicola/.local/lib/python2.7/site-packages/tensor2tensor/utils/t2t_model.py", line 154, in call
    sharded_logits, losses = self.model_fn_sharded(sharded_features)
  File "/home/nicola/.local/lib/python2.7/site-packages/tensor2tensor/utils/t2t_model.py", line 209, in model_fn_sharded
    sharded_logits, sharded_losses = dp(self.model_fn, datashard_to_features)
  File "/home/nicola/.local/lib/python2.7/site-packages/tensor2tensor/utils/expert_utils.py", line 230, in __call__
    outputs.append(fns[i](*my_args[i], **my_kwargs[i]))
  File "/home/nicola/.local/lib/python2.7/site-packages/tensor2tensor/utils/t2t_model.py", line 233, in model_fn
    transformed_features = self.bottom(features)
  File "/home/nicola/.local/lib/python2.7/site-packages/tensor2tensor/utils/t2t_model.py", line 275, in bottom
    transformed_features[key] = input_modality.bottom(features[key])
  File "/home/nicola/.local/lib/python2.7/site-packages/tensor2tensor/layers/modalities.py", line 121, in bottom
    return self.bottom_simple(x, "shared", reuse=None)
  File "/home/nicola/.local/lib/python2.7/site-packages/tensor2tensor/layers/modalities.py", line 115, in bottom_simple
    ret *= tf.expand_dims(tf.to_float(tf.not_equal(x, 0)), -1)
  File "/home/nicola/.local/lib/python2.7/site-packages/tensorflow/python/ops/math_ops.py", line 970, in binary_op_wrapper
    y = ops.convert_to_tensor(y, dtype=x.dtype.base_dtype, name="y")
  File "/home/nicola/.local/lib/python2.7/site-packages/tensorflow/python/framework/ops.py", line 1014, in convert_to_tensor
    as_ref=False)
  File "/home/nicola/.local/lib/python2.7/site-packages/tensorflow/python/framework/ops.py", line 1104, in internal_convert_to_tensor
    ret = conversion_func(value, dtype=dtype, name=name, as_ref=as_ref)
  File "/home/nicola/.local/lib/python2.7/site-packages/tensorflow/python/framework/ops.py", line 947, in _TensorTensorConversionFunction
    (dtype.name, t.dtype.name, str(t)))
ValueError: Tensor conversion requested dtype bfloat16 for Tensor with dtype float32: 'Tensor("transformer/parallel_0_5/transformer/symbol_modality_8374_512/shared/ExpandDims:0", shape=(?, ?, 1, 1), dtype=float32, device=/device:GPU:0)'

bfloat16 is only TPU, not GPU.

Is there any reason why 'bfloat16' is not available for GPU?
Is there any other way to use half_precision with GPU?


[P4] Include local weather in memory

Similar to feature request #325 , but weather

Not planend for now.


Investigate the order of support for AM code

This issue is imported from pivotal - Originaly created at Oct 23, 2019 by bstrooband
Should additional care be taken for AM because support of PHP5.6 is dropped?
Because we don't know what is used it's hard to make a educated decision.

Test common ones, fix problematic ones when we encounter a problem? (Thijs Kinkhorst - Oct 23, 2019)

The tests currently used are the ones below, which seem to address common AM's:
https://github.com/OpenConext/OpenConext-engineblock/blob/master/src/OpenConext/EngineBlockFunctionalTestingBundle/Features/AttributeManipulation.feature
https://github.com/OpenConext/OpenConext-engineblock/blob/master/src/OpenConext/EngineBlockFunctionalTestingBundle/Features/AttributeManipulationException.feature
So I won't do anything further with this. If you'll encounter some problematic ones yourself which you'll like to have tested please file an issue so we could add them to the tests. (bstrooband - Oct 23, 2019)


[Bug] Changing between entities doesn't reset rule field values when category type is used

Steps to reproduce within demo

Create entity categories
Add Fields to categories, populate their values, the fields must use category
When using entity mode inspect the field values for a category field, they should appear correctly
Change from one entity to another

Result:

Inspect the values again, the values are taken from the previous entity field's options
Inspect JSON: rule's entity has changed but the field has remained from the previous

Related PR
#78

Hi!
I need this fix, what can I do?
Thanks

Yeah, I am facing the same issue. how can i get through this ?


product options don't show up correctly

After configuring product options, they don't appear correctly. No radio buttons or check boxes.
Also no way to add pricing for the options on a base product.

also after editing a product with options and you add a new option to the existing ones only the new option gets added and rest are deleted.

both check boxes or radios don't save the values on add to cart.

Was this fixed?

I can't replicate with very little information. Works fine for me.

All values from radios, and select inputs don't save correctly. And if you have a select input and you unchecked it it throws an undefined error.

I'm running the latest version on Github and cannot reproduce this error. Can you please specify the exact steps? I've tried adding options of all types and get no errors.

When a product is added to the cart all radio and select input values are wrong drop down are good
Sent from my iPhone

On Feb 9, 2019, at 2:49 AM, Mark Moffat<EMAIL_ADDRESS>wrote:
I'm running the latest version on Github and cannot reproduce this error. Can you please specify the exact steps? I've tried adding options of all types and get no errors.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

By the way this is awesome finally an express cart been waiting for something like this for a while.

add something to the cart with radios or select inputs

cool  thank you sir


Latest release missing bin file

The release on npm with version 0.4.1 doesn't seem to have been built properly (there's not out/ directory).

:+1:


--sync-keep option not working for local transfers

For local backups on another filesystem I'd like to use the --sync-target and --sync-keep options. However, on the receiving filesystem the snapshots pile up and there is never a clean up. With --sync-keep 7 I would expect to see 7 or less snapshots only. The clean up on the sending side is working well.
/usr/local/bin/snapbtrex.py \
--target-backups 1 --keep-backups 1 --keep-only-latest \
--snap / --path /mnt/btrfs/xps_system/snapshots/root/ \
--sync-target /mnt/btrfs/sa190919/backup/system/root/ --sync-keep 7 \
-v
Verbose output:
Local  > snapshotting path=/ to newdir=/mnt/btrfs/xps_system/snapshots/root/20190929-213433
EXEC  >-> sudo btrfs subvolume snapshot -r / /mnt/btrfs/xps_system/snapshots/root/20190929-213433
OUTPUT > Create a readonly snapshot of '/' in '/mnt/btrfs/xps_system/snapshots/root/20190929-213433'

Local  > sync filesystem '/mnt/btrfs/xps_system/snapshots/root/'
EXEC  >-> sudo btrfs filesystem sync /mnt/btrfs/xps_system/snapshots/root/
Local  > done sync filesystem '/mnt/btrfs/xps_system/snapshots/root/'
Local  > done snapshotting
Local  > Sync: last possible parent = 20190929-213303
Local  > transfer: parent=20190929-213303 snap=20190929-213433
Local  > send snapshot from 20190929-213433 with parent 20190929-213303 to path=/mnt/btrfs/sa190919/backup/system/root/
EXEC  >-> sudo btrfs send -v -p /mnt/btrfs/xps_system/snapshots/root/20190929-213303 /mnt/btrfs/xps_system/snapshots/root/20190929-213433 | pv -brtf |  sudo btrfs receive -v /mnt/btrfs/sa190919/backup/system/root/
OUTPUT > At snapshot 20190929-213433

STDERR > At subvol /mnt/btrfs/xps_system/snapshots/root/20190929-213433
receiving snapshot 20190929-213433 uuid=4c3e1037-d4fb-c547-834e-ba6de5b5d389, ctransid=289810 parent_uuid=eef97a2c-5cf6-6f4a-a291-c16119cbd8b4, parent_ctransid=289805
BTRFS_IOC_SEND returned 0
joining genl thread
BTRFS_IOC_SET_RECEIVED_SUBVOL uuid=4c3e1037-d4fb-c547-834e-ba6de5b5d389, stransid=289810
4,50MiB 0:00:00 [ 130MiB/s]

Local  > Parameters for cleandir: keep_backups=1, target_freespace=None, target_backups=1, max_age=None, keep_latest=True
Local  > will delete backup: '20190929-213433'
Local  > remove snapshot '20190929-213303'
EXEC  >-> sudo btrfs subvolume delete /mnt/btrfs/xps_system/snapshots/root/20190929-213303
OUTPUT > Delete subvolume (no-commit): '/mnt/btrfs/xps_system/snapshots/root/20190929-213303'

Local  > done remove snapshot '20190929-213303'
Local  > Reached number of backups to keep: 1

I am not sure if the output to STDERR indicates an error: except for this issue everything works fine. Or maybe the problem is that --sync-keep is stored the same as for --remote-keep but gets evaluated only for remote transfers (which would be my guess for why this happens).

STDERR does not mean, there is an error! its just btrfs-send that is printing the Output to Stderr.

and Yes it is an Error.

Works. Thank you! :-)


[NTR] hepatic fibrosis (disease)

cc @idazucchi (original request: https://github.com/HumanCellAtlas/ontology/issues/96)
Dear Mondo editors,
The Human Cell Atlas would like to request a disease term please, to represent fibrotic liver disease as needed for this paper. We're aware that there is a term for 'Hepatic fibrosis' in HP, but the HCA schema cannot accommodate phenotype terms at present, and the paper specifically refers to "human fibrotic liver disease" and "fibrotic diseases" (as well as liver fibrosis). I realize we're in a grey zone here, but there are precedents of disease terms in Mondo like 'breast fibrosis', 'endomyocardial fibrosis' etc. so I'm wondering if you'd agree to creating this one too, possibly with a link to HP:0001395 'Hepatic fibrosis'. It could be named 'hepatic fibrosis (disease)' to distinguish it from the phenotype term, or 'fibrotic liver disease':
Preferred term label:
hepatic fibrosis (disease)
or
fibrotic liver disease
Synonyms
fibrotic liver disease
or
hepatic fibrosis (disease);
liver fibrosis (disease)
Definition (free text, please give PubMed ID, if applicable, in format PMID:#######)
A liver disease characterized by the presence of excessive fibrous connective tissue in the liver.
PMID:31722201 (the same paper HCA is wrangling, above)
Parent term (use OLS, or your favorite ontology browser)
MONDO:0005154 liver disease
Children terms (if applicable) Should any existing terms that should be moved underneath this new proposed term?
Not really, but MONDO:0018840 'isolated congenital hepatic fibrosis' ("A congenital disorder usually inherited in an autosomal recessive pattern. It affects the hepatobiliary system and the kidneys. It is characterized by liver fibrosis, portal hypertension, and renal cysts. [ NCIT:C97071 ]") might be linked to HP:0001395 'Hepatic fibrosis'.
Your nano-attribution (ORCID)
http://orcid.org/0000-0002-4900-7575 (Ida's)
http://orcid.org/0000-0002-2825-0621 (mine)
Thank you,
Paola and Ida

sure thing @paolaroncaglia
Note to self, this should probably be a child:
MONDO_0018840 'isolated congenital hepatic fibrosis'

Thanks @nicolevasilevsky , you're faster than light! :-)


Support for #[cfg] on #[monotonic]

I would like to feature-gate the monotonic type to only have it in some builds and not others. I tried the following but it doesn't work:
    #[cfg(feature = "log")]
    #[monotonic(binds = SysTick, default = true)]
    type MonoSysTick = Systick<100>;

Then in init I have:
        (
            Shared { ... },
            Local { ... },
            #[cfg(not(feature = "log"))]
            init::Monotonics(),
            #[cfg(feature = "log")]
            init::Monotonics(systick),
        )

Here's what I get when building without the feature (it works with the feature):
error[E0412]: cannot find type `MonoSysTick` in module `super::super`
  --> src/main.rs:51:10
   |
51 |     type MonoSysTick = Systick<100>;
   |          ^^^^^^^^^^^ not found in `super::super`

error[E0412]: cannot find type `Systick` in this scope
  --> src/main.rs:51:24
   |
51 |     type MonoSysTick = Systick<100>;
   |                        ^^^^^^^ not found in this scope

error[E0061]: this struct takes 1 argument but 0 arguments were supplied
   --> src/main.rs:117:13
    |
117 |             init::Monotonics(),
    |             ^^^^^^^^^^^^^^^^-- an argument is missing
    |

Is this something that might eventually get support for?

Scope goes beyond Monotonic. Also applies to Shared and Local. I also would like this.

Hi,
The cfg support in RTIC 1 is broken and on the path of wont-fix.
This is case is already supported in (under development) RTIC 2, so o think

As an experiment to see what can be done for RTIC 1 I've created #691
The obvious limitation, as shown in examples/cfg-monotonic, is that rtic-syntax does not know what is cfg-ed out, and thus "correctly" refuses code that uses the same type, or same interrupt. Might work for other cases, here I hope for your help to see how your usecases might be supported :)
From the example, showing the rtic-syntax errors
    // A monotonic timer to enable scheduling in RTIC
    #[cfg(feature = "killmono")]
    #[monotonic(binds = SysTick, default = true)]
    type MyMono = Systick<100>; // 100 Hz / 10 ms granularity

    // Not allowed by current rtic-syntax:
    // error: `#[monotonic(...)]` on a specific type must appear at most once
    //   --> examples/cfg-monotonic.rs:23:10
    //    |
    // 23 |     type MyMono = Systick<100>; // 100 Hz / 10 ms granularity
    //    |          ^^^^^^
    // #[monotonic(binds = SysTick, default = true)]
    // type MyMono = Systick<100>; // 100 Hz / 10 ms granularity

    // Not allowed by current rtic-syntax:
    // error: this interrupt is already bound
    //   --> examples/cfg-monotonic.rs:31:25
    //    |
    // 31 |     #[monotonic(binds = SysTick, default = true)]
    //    |                         ^^^^^^^
    // #[monotonic(binds = SysTick, default = true)]
    // type MyMono2 = DwtSystick<100>; // 100 Hz / 10 ms granularity

here I hope for your help to see how your usecases might be supported

As original author of this issue, my usecase doesn't exist anymore (I moved out of RTIC for different reasons). But for reference, my original usecase was: Use monotonic for defmt::timestamp! and thus only use it when logging is enabled. The cfg would have been something like #[cfg(feature = "defmt")]. And in the init task I would call defmt::timestamp! on monotonics::now(), gated by feature = "defmt".