Error: Uncaught (in promise): TypeError: Gy(…).storage is not a function when using ng build --prod

🐞 Bug report
Command (mark with an x)

[x] build

Is this a regression?

 Yes, the previous version in which this bug was not present was: Yes, but I am not sure exactly what was updated since I had made several changes.  I just started this project from scratch in May, so nothing was very old.
Description
I am getting this error  Error: Uncaught (in promise): TypeError: Gy(...).storage is not a function but ONLY when I build and deploy my Angular project using ng build --prod. When I deploy using ng build or when I run ng serve, I do not get the error and everything works as expected.
Additionally, the error only happens when I try to route to one specific component within my app.
Further, I have discovered that when I change the "target" property under "compilerOptions" in my tsconfig.json file from es2018 to es2015 to es5 or back and forth, it changes the error slightly instead of Gy, it may say Xy, or qy.
Based on suggestions found in some slightly similar issues, I have tried the following:
-Updating all my npm packages
-Upgrading my Angular CLI as per this post: https://stackoverflow.com/a/43931987/10415078
-Running ng update (everything seems to be in order)
🔬 Minimal Reproduction
I am not sure what exactly is causing the error, but I only get it when I navigate to this specific component, and only when I've run ng build --prod.
Here are my imports for that component, but nothing really changed within this component from the time it worked to the time it didn't.
import { Component, OnInit } from '@angular/core';
import { GENERAL_REF } from '../../dbReferences';
import { DatabaseService } from 'src/app/services/database.service';
import { ProductApiService } from '../../services/product-api.service';
import { StorageService } from '../../services/storage.service';
import { Router, ActivatedRoute } from '@angular/router';
import { List } from '../../models/List';
import { User } from '../../models/User';
import { ListView } from '../../models/ListView';
import { NgbModal, ModalDismissReasons } from '@ng-bootstrap/ng-bootstrap';

My tsconfig.json file:
{
  "compileOnSave": false,
  "compilerOptions": {
    "baseUrl": "./",
    "outDir": "./dist/out-tsc",
    "sourceMap": true,
    "declaration": false,
    "downlevelIteration": true,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "module": "esnext",
    "moduleResolution": "node",
    "importHelpers": true,
    "target": "es2015",
    "typeRoots": [
      "node_modules/@types", "./typings.d.ts"
    ],
    "lib": [
      "es2018",
      "dom"
    ]
  }
}

My
🔥 Exception or Error
Error: Uncaught (in promise): TypeError: qy(...).storage is not a function
TypeError: qy(...).storage is not a function
    at VM239 main-es2015.062cd6f3017dd905f396.js:1
    at a.invoke (VM237 polyfills-es2015.4d31cca2afc45cfd85b5.js:1)
    at t.run (VM237 polyfills-es2015.4d31cca2afc45cfd85b5.js:1)
    at ar.runOutsideAngular (VM239 main-es2015.062cd6f3017dd905f396.js:1)
    at new <anonymous> (VM239 main-es2015.062cd6f3017dd905f396.js:1)
    at VM239 main-es2015.062cd6f3017dd905f396.js:1
    at xi (VM239 main-es2015.062cd6f3017dd905f396.js:1)
    at Pi (VM239 main-es2015.062cd6f3017dd905f396.js:1)
    at VM239 main-es2015.062cd6f3017dd905f396.js:1
    at xi (VM239 main-es2015.062cd6f3017dd905f396.js:1)
    at P (VM237 polyfills-es2015.4d31cca2afc45cfd85b5.js:1)
    at P (VM237 polyfills-es2015.4d31cca2afc45cfd85b5.js:1)
    at VM237 polyfills-es2015.4d31cca2afc45cfd85b5.js:1
    at a.invokeTask (VM237 polyfills-es2015.4d31cca2afc45cfd85b5.js:1)
    at Object.onInvokeTask (VM239 main-es2015.062cd6f3017dd905f396.js:1)
    at a.invokeTask (VM237 polyfills-es2015.4d31cca2afc45cfd85b5.js:1)
    at t.runTask (VM237 polyfills-es2015.4d31cca2afc45cfd85b5.js:1)
    at _ (VM237 polyfills-es2015.4d31cca2afc45cfd85b5.js:1)
    at c.invokeTask [as invoke] (VM237 polyfills-es2015.4d31cca2afc45cfd85b5.js:1)
    at y (VM237 polyfills-es2015.4d31cca2afc45cfd85b5.js:1)

🌍 Your Environment

Angular CLI: 8.1.2
Node: 10.16.0
OS: win32 x64
Angular: 8.1.2
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.801.2
@angular-devkit/build-angular     0.801.2
@angular-devkit/build-optimizer   0.801.2
@angular-devkit/build-webpack     0.801.2
@angular-devkit/core              8.1.2
@angular-devkit/schematics        8.1.2
@angular/fire                     5.2.1
@angular/http                     7.2.15
@ngtools/webpack                  8.1.2
@schematics/angular               8.1.2
@schematics/update                0.801.2
rxjs                              6.5.2
typescript                        3.4.5
webpack                           4.35.2

##Anything Else Relevant?
I am using Firebase and running the app on Chrome browser.
Also, I noticed in my angular.json file that I am getting an error for "$schema"<EMAIL_ADDRESS>that says File not found, even though that file definitely exists - I am not sure if this error has always been there or not, but everything runs fine if only I build with ng build or run ng serve.

Hi, can you try updating the angular cli and build angular to next and see if the problem persists?
If the problem persists after updating, can you setup a minimal repro please?
You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.

Can you please provide me with the correct steps to do that? I have already followed the steps below with no change:
npm uninstall -g angular-cli
npm cache clean or npm cache verify #(if npm > 5)
npm install -g @angular/cli@latest
rm -rf node_modules
npm uninstall --save-dev angular-cli
npm install --save-dev @angular/cli@latest
npm install

The below command should be enough.
npm install @angular/cli@next @angular-devkit/build-angular@next --save-dev

@alan-agius4  thank you for providing the command and sorry for taking so long to get back to you!
After running that, I showed that I had
    "@angular-devkit/build-angular": "^0.802.0-next.1",
    "@angular/cli": "^8.2.0-next.1",

When I ran ng build --prod after that, I got the following errors.  These only showed after signing into Firebase Auth and trying to make a request to Firestore.
main-es2015.2d833ea15afb58d17bef.js:1 [2019-07-24T21:52:37.331Z]  @firebase/firestore: Firestore (6.3.1): INTERNAL UNHANDLED ERROR:  TypeError: Cannot read property 'serializer' of undefined
    at https://presently.us/main-es2015.2d833ea15afb58d17bef.js:1:148837
    at t.watch (https://presently.us/main-es2015.2d833ea15afb58d17bef.js:1:148908)
    at e.sendWatchRequest (https://presently.us/main-es2015.2d833ea15afb58d17bef.js:1:174979)
    at https://presently.us/main-es2015.2d833ea15afb58d17bef.js:1:175848
    at A (https://presently.us/main-es2015.2d833ea15afb58d17bef.js:1:2753)
    at e.<anonymous> (https://presently.us/main-es2015.2d833ea15afb58d17bef.js:1:175811)
    at https://presently.us/main-es2015.2d833ea15afb58d17bef.js:1:333628
    at Object.next (https://presently.us/main-es2015.2d833ea15afb58d17bef.js:1:333733)
    at https://presently.us/main-es2015.2d833ea15afb58d17bef.js:1:332671
    at new e (https://presently.us/polyfills-es2015.0237501fdf2cd123afaf.js:1:13013)
u @ main-es2015.2d833ea15afb58d17bef.js:1
polyfills-es2015.0237501fdf2cd123afaf.js:1 Unhandled Promise rejection: Cannot read property 'serializer' of undefined ; Zone: <root> ; Task: Promise.then ; Value: TypeError: Cannot read property 'serializer' of undefined
    at main-es2015.2d833ea15afb58d17bef.js:1
    at t.watch (main-es2015.2d833ea15afb58d17bef.js:1)
    at e.sendWatchRequest (main-es2015.2d833ea15afb58d17bef.js:1)
    at main-es2015.2d833ea15afb58d17bef.js:1
    at A (main-es2015.2d833ea15afb58d17bef.js:1)
    at e.<anonymous> (main-es2015.2d833ea15afb58d17bef.js:1)
    at main-es2015.2d833ea15afb58d17bef.js:1
    at Object.next (main-es2015.2d833ea15afb58d17bef.js:1)
    at main-es2015.2d833ea15afb58d17bef.js:1
    at new e (polyfills-es2015.0237501fdf2cd123afaf.js:1) TypeError: Cannot read property 'serializer' of undefined
    at https://presently.us/main-es2015.2d833ea15afb58d17bef.js:1:148837
    at t.watch (https://presently.us/main-es2015.2d833ea15afb58d17bef.js:1:148908)
    at e.sendWatchRequest (https://presently.us/main-es2015.2d833ea15afb58d17bef.js:1:174979)
    at https://presently.us/main-es2015.2d833ea15afb58d17bef.js:1:175848
    at A (https://presently.us/main-es2015.2d833ea15afb58d17bef.js:1:2753)
    at e.<anonymous> (https://presently.us/main-es2015.2d833ea15afb58d17bef.js:1:175811)
    at https://presently.us/main-es2015.2d833ea15afb58d17bef.js:1:333628
    at Object.next (https://presently.us/main-es2015.2d833ea15afb58d17bef.js:1:333733)
    at https://presently.us/main-es2015.2d833ea15afb58d17bef.js:1:332671
    at new e (https://presently.us/polyfills-es2015.0237501fdf2cd123afaf.js:1:13013)
n.onUnhandledError @ polyfills-es2015.0237501fdf2cd123afaf.js:1
polyfills-es2015.0237501fdf2cd123afaf.js:1 Uncaught TypeError: Cannot read property 'serializer' of undefined
    at main-es2015.2d833ea15afb58d17bef.js:1
    at t.watch (main-es2015.2d833ea15afb58d17bef.js:1)
    at e.sendWatchRequest (main-es2015.2d833ea15afb58d17bef.js:1)
    at main-es2015.2d833ea15afb58d17bef.js:1
    at A (main-es2015.2d833ea15afb58d17bef.js:1)
    at e.<anonymous> (main-es2015.2d833ea15afb58d17bef.js:1)
    at main-es2015.2d833ea15afb58d17bef.js:1
    at Object.next (main-es2015.2d833ea15afb58d17bef.js:1)
    at main-es2015.2d833ea15afb58d17bef.js:1
    at new e (polyfills-es2015.0237501fdf2cd123afaf.js:1)
main-es2015.2d833ea15afb58d17bef.js:1 [2019-07-24T21:52:47.281Z]  @firebase/firestore: Firestore (6.3.1): FIRESTORE (6.3.1) INTERNAL ASSERTION FAILED: AsyncQueue is already failed: TypeError: Cannot read property 'serializer' of undefined
    at https://presently.us/main-es2015.2d833ea15afb58d17bef.js:1:148837
    at t.watch (https://presently.us/main-es2015.2d833ea15afb58d17bef.js:1:148908)
    at e.sendWatchRequest (https://presently.us/main-es2015.2d833ea15afb58d17bef.js:1:174979)
    at https://presently.us/main-es2015.2d833ea15afb58d17bef.js:1:175848
    at A (https://presently.us/main-es2015.2d833ea15afb58d17bef.js:1:2753)
    at e.<anonymous> (https://presently.us/main-es2015.2d833ea15afb58d17bef.js:1:175811)
    at https://presently.us/main-es2015.2d833ea15afb58d17bef.js:1:333628
    at Object.next (https://presently.us/main-es2015.2d833ea15afb58d17bef.js:1:333733)
    at https://presently.us/main-es2015.2d833ea15afb58d17bef.js:1:332671
    at new e (https://presently.us/polyfills-es2015.0237501fdf2cd123afaf.js:1:13013)
u @ main-es2015.2d833ea15afb58d17bef.js:1
e.error @ main-es2015.2d833ea15afb58d17bef.js:1
m @ main-es2015.2d833ea15afb58d17bef.js:1
v @ main-es2015.2d833ea15afb58d17bef.js:1
e.verifyNotFailed @ main-es2015.2d833ea15afb58d17bef.js:1
e.enqueue @ main-es2015.2d833ea15afb58d17bef.js:1
e.enqueueAndForget @ main-es2015.2d833ea15afb58d17bef.js:1
e.handleDelayElapsed @ main-es2015.2d833ea15afb58d17bef.js:1
(anonymous) @ main-es2015.2d833ea15afb58d17bef.js:1
invokeTask @ polyfills-es2015.0237501fdf2cd123afaf.js:1
runTask @ polyfills-es2015.0237501fdf2cd123afaf.js:1
invokeTask @ polyfills-es2015.0237501fdf2cd123afaf.js:1
invoke @ polyfills-es2015.0237501fdf2cd123afaf.js:1
n.args.<computed> @ polyfills-es2015.0237501fdf2cd123afaf.js:1
polyfills-es2015.0237501fdf2cd123afaf.js:1 Uncaught Error: FIRESTORE (6.3.1) INTERNAL ASSERTION FAILED: AsyncQueue is already failed: TypeError: Cannot read property 'serializer' of undefined
    at main-es2015.2d833ea15afb58d17bef.js:1
    at t.watch (main-es2015.2d833ea15afb58d17bef.js:1)
    at e.sendWatchRequest (main-es2015.2d833ea15afb58d17bef.js:1)
    at main-es2015.2d833ea15afb58d17bef.js:1
    at A (main-es2015.2d833ea15afb58d17bef.js:1)
    at e.<anonymous> (main-es2015.2d833ea15afb58d17bef.js:1)
    at main-es2015.2d833ea15afb58d17bef.js:1
    at Object.next (main-es2015.2d833ea15afb58d17bef.js:1)
    at main-es2015.2d833ea15afb58d17bef.js:1
    at new e (polyfills-es2015.0237501fdf2cd123afaf.js:1)
    at v (main-es2015.2d833ea15afb58d17bef.js:1)
    at e.verifyNotFailed (main-es2015.2d833ea15afb58d17bef.js:1)
    at e.enqueue (main-es2015.2d833ea15afb58d17bef.js:1)
    at e.enqueueAndForget (main-es2015.2d833ea15afb58d17bef.js:1)
    at e.handleDelayElapsed (main-es2015.2d833ea15afb58d17bef.js:1)
    at main-es2015.2d833ea15afb58d17bef.js:1
    at a.invokeTask (polyfills-es2015.0237501fdf2cd123afaf.js:1)
    at t.runTask (polyfills-es2015.0237501fdf2cd123afaf.js:1)
    at invokeTask (polyfills-es2015.0237501fdf2cd123afaf.js:1)
    at invoke (polyfills-es2015.0237501fdf2cd123afaf.js:1)
v @ main-es2015.2d833ea15afb58d17bef.js:1
e.verifyNotFailed @ main-es2015.2d833ea15afb58d17bef.js:1
e.enqueue @ main-es2015.2d833ea15afb58d17bef.js:1
e.enqueueAndForget @ main-es2015.2d833ea15afb58d17bef.js:1
e.handleDelayElapsed @ main-es2015.2d833ea15afb58d17bef.js:1
(anonymous) @ main-es2015.2d833ea15afb58d17bef.js:1
invokeTask @ polyfills-es2015.0237501fdf2cd123afaf.js:1
runTask @ polyfills-es2015.0237501fdf2cd123afaf.js:1
invokeTask @ polyfills-es2015.0237501fdf2cd123afaf.js:1
invoke @ polyfills-es2015.0237501fdf2cd123afaf.js:1
n.args.<computed> @ polyfills-es2015.0237501fdf2cd123afaf.js:1

The first 3 showed immediately, and the last 2 showed up a few seconds later.
This also happened when I rebuilt with ng build (no --prod), but I got NO errors when I ran with ng serve
After that happened, I went ahead and updated the following packages, just to see if it helped, but nothing changed.
"firebase": "^6.3.1",
"firebase-admin": "^8.3.0",
"firebase-functions": "^3.2.0",
"firebase-tools": "^7.2.0",

So, I ran npm i @angular/cli@latest @angular-devkit/build-angular@latest --save-dev to put my angular cli back to where it was before, which is:
    "@angular-devkit/build-angular": "^0.801.2",
    "@angular/cli": "^8.1.2",

And now I am just back to the original error, happening on the same page and only with ng build --prod.
Does that give you any additional insight or are you still needing a repro?
Thanks!

Hi @formster-biz, it would be best to provide a reproduction so that we can look at the a bit more.
Thanks

Hi @formster-biz, I am thinking that your issue might be the same root cause of https://github.com/angular/angular-cli/issues/15145 can you check if setting "@angular-devkit/build-angular": "0.801.0", works?
Thanks

@alan-agius4 unfortunately, I am getting the same main error, although some of the details are a little different.
First I ran npm i<EMAIL_ADDRESS>and now my angular version is:
Angular CLI: 8.1.2
Node: 10.16.0
OS: win32 x64
Angular: 8.1.2
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.801.2
@angular-devkit/build-angular     0.801.0
@angular-devkit/build-optimizer   0.801.0
@angular-devkit/build-webpack     0.801.0
@angular-devkit/core              8.1.2
@angular-devkit/schematics        8.1.2
@angular/fire                     5.2.1
@angular/http                     7.2.15
@ngtools/webpack                  8.1.0
@schematics/angular               8.1.2
@schematics/update                0.801.2
rxjs                              6.5.2
typescript                        3.4.5
webpack                           4.35.2

Then I ran ng build--prod and here's the error I got once I navigated to the problem page:
ERROR Error: Uncaught (in promise): TypeError: qy(...).storage is not a function
TypeError: qy(...).storage is not a function
    at main-es2015.4f3e1680e51ec4004c64.js:1
    at a.invoke (polyfills-es2015.6ea0b72173d453e298a9.js:1)
    at t.run (polyfills-es2015.6ea0b72173d453e298a9.js:1)
    at ar.runOutsideAngular (main-es2015.4f3e1680e51ec4004c64.js:1)
    at new <anonymous> (main-es2015.4f3e1680e51ec4004c64.js:1)
    at main-es2015.4f3e1680e51ec4004c64.js:1
    at xi (main-es2015.4f3e1680e51ec4004c64.js:1)
    at Pi (main-es2015.4f3e1680e51ec4004c64.js:1)
    at main-es2015.4f3e1680e51ec4004c64.js:1
    at xi (main-es2015.4f3e1680e51ec4004c64.js:1)
    at P (polyfills-es2015.6ea0b72173d453e298a9.js:1)
    at P (polyfills-es2015.6ea0b72173d453e298a9.js:1)
    at polyfills-es2015.6ea0b72173d453e298a9.js:1
    at a.invokeTask (polyfills-es2015.6ea0b72173d453e298a9.js:1)
    at Object.onInvokeTask (main-es2015.4f3e1680e51ec4004c64.js:1)
    at a.invokeTask (polyfills-es2015.6ea0b72173d453e298a9.js:1)
    at t.runTask (polyfills-es2015.6ea0b72173d453e298a9.js:1)
    at _ (polyfills-es2015.6ea0b72173d453e298a9.js:1)
    at c.invokeTask [as invoke] (polyfills-es2015.6ea0b72173d453e298a9.js:1)
    at y (polyfills-es2015.6ea0b72173d453e298a9.js:1)

Should I try to update some of those other devkit packages before creating a repro?
Thanks!

It may be totally unrelated (this is all so far over my head ): ) , but I wanted to mention since it seems really weird that this error only occurs when i route to one specific component in my app - literally every other one works.  This component has almost all the same imports as the others, but there is one that is used here that isn't used anywhere else in my app.  This component imports/utilizes my storage.service.ts service, which in turn uses import { AngularFireStorage, AngularFireUploadTask } from '@angular/fire/storage';
The error occurs immediately before the component even has a chance to start ngOnInit, and this service is not even called automatically in ngOnInit, it is only called as needed depending on user input - so maybe it's not related...?
Anyway, I just thought it may be worth mentioning, since my error obviously says something about a .storage function.

@alan-agius4 I just commented out everything related to the storage.service.ts service that I mentioned in the previous comment from my item.component.ts component (the one that throws the error when I route to it, and rebuilt with ng build --prod and ran with no errors!!

Hi @formster-biz, in that case a reproduction is definitely need to see what's going on.
Thanks.

Good morning, @alan-agius4 I created the repro app, but I can't add Firebase to it, since the console is still having issues this morning, and I don't think the error would re-occur without it.  Would it be helpful if I went ahead and added it to Github as is for now, or should I just wait?  Sorry, I'm just anxious to get this problem resolved :/

Hi, @alan-agius4
Ok, I got the reproduction uploaded to the following repository: https://github.com/formster-biz/repro
You can also see the error at https://repro-b32d1.firebaseapp.com/ which was built with ng build --prod - it's almost exactly the same but the function letters have changed slightly again:
ERROR Error: Uncaught (in promise): TypeError: Gd(...).storage is not a function
TypeError: Gd(...).storage is not a function
    at main-es2015.ff59a6302a369d00305c.js:1
    at a.invoke (polyfills-es2015.4d31cca2afc45cfd85b5.js:1)
    at t.run (polyfills-es2015.4d31cca2afc45cfd85b5.js:1)
    at no.runOutsideAngular (main-es2015.ff59a6302a369d00305c.js:1)
    at new <anonymous> (main-es2015.ff59a6302a369d00305c.js:1)
    at main-es2015.ff59a6302a369d00305c.js:1
    at kr (main-es2015.ff59a6302a369d00305c.js:1)
    at xr (main-es2015.ff59a6302a369d00305c.js:1)
    at main-es2015.ff59a6302a369d00305c.js:1
    at kr (main-es2015.ff59a6302a369d00305c.js:1)
    at P (polyfills-es2015.4d31cca2afc45cfd85b5.js:1)
    at P (polyfills-es2015.4d31cca2afc45cfd85b5.js:1)
    at polyfills-es2015.4d31cca2afc45cfd85b5.js:1
    at a.invokeTask (polyfills-es2015.4d31cca2afc45cfd85b5.js:1)
    at Object.onInvokeTask (main-es2015.ff59a6302a369d00305c.js:1)
    at a.invokeTask (polyfills-es2015.4d31cca2afc45cfd85b5.js:1)
    at t.runTask (polyfills-es2015.4d31cca2afc45cfd85b5.js:1)
    at _ (polyfills-es2015.4d31cca2afc45cfd85b5.js:1)
    at c.invokeTask [as invoke] (polyfills-es2015.4d31cca2afc45cfd85b5.js:1)
    at y (polyfills-es2015.4d31cca2afc45cfd85b5.js:1)

It works fine when run with ng serve and ng build
Thank you so much for taking the time to look into this!  Let me know if you need any further info.

Good morning, @alan-agius4
I just wanted to check in and see if there was any progress on this yet?  I've not done a repo before, so wanted to make sure everything was submitted correctly.  Thanks!

@formster-biz, the reproduction is great. Unfortunately I didn't have time to take a look at the problem.

@alan-agius4 can you please let me know when I should expect an update on this?

I can repro by:

git clone https://github.com/formster-biz/repro && cd repro
npm install
ng serve --prod
opening http://localhost:4200 and clicking on click for Item Component
the error below appears on the chrome devtools console:

core.js:9110 ERROR Error: Uncaught (in promise): TypeError: _firebaseAppFactory(...).storage is not a function
TypeError: _firebaseAppFactory(...).storage is not a function
    at storage.js:22
    at ZoneDelegate.invoke (zone-evergreen.js:359)
    at Zone.run (zone-evergreen.js:124)
    at NgZone.runOutsideAngular (core.js:34127)
    at new storage_AngularFireStorage (storage.js:20)
    at core.js:26482
    at _createProviderInstance (core.js:26436)
    at resolveNgModuleDep (core.js:26383)
    at core.js:26471
    at _createProviderInstance (core.js:26436)
    at resolvePromise (zone-evergreen.js:797)
    at resolvePromise (zone-evergreen.js:754)
    at zone-evergreen.js:858
    at ZoneDelegate.invokeTask (zone-evergreen.js:391)
    at Object.onInvokeTask (core.js:34182)
    at ZoneDelegate.invokeTask (zone-evergreen.js:390)
    at Zone.runTask (zone-evergreen.js:168)
    at drainMicroTaskQueue (zone-evergreen.js:559)
    at ZoneTask.invokeTask [as invoke] (zone-evergreen.js:469)
    at invokeTask (zone-evergreen.js:1603)

Btw this was a great repro, well done!
I tried to updating to<EMAIL_ADDRESS>and<EMAIL_ADDRESS>to see if the problem was still there, and it was. I also tried ng serve --prod --build-optimizer false to see if it's a Build Optimizer bug (these things often are), but I still saw the error.
There's a similar issue report in https://github.com/angular/angularfire2/issues/1978, but no details there.
I went to check the docs (https://github.com/angular/angularfire2/blob/master/docs/storage/storage.md) to see if there was some config item missing and saw that AngularFireStorageModule needs to be imported. I added it to src/app/app.module.ts and the problem was gone.
I think this was just a matter of a unhelpful error message from @angular/fire (cc @davideast).


Add lint rule for spec.matchLabels on Deployment

Resources like Deployment, ReplicaSet, and DaemonSet should, as a best practice, declare selector.matchLabels rules in their pod template:
https://kubernetes.io/docs/concepts/tools/kubectl/object-management-using-declarative-config/#defining-controller-selectors-and-podtemplate-labels
Doing so prevents a number of odd-ball cases where pods are not appropriately updated.
We should write a linting rule to catch this case.

This could be a nice stretch goal feature for 2.4 if we are able to finish the other work.

related: #2694

/remove-lifecycle rotten


replace json with gson library

add to pom.xml:
  <!-- https://mvnrepository.com/artifact/com.google.code.gson/gson -->
  <dependency>
      <groupId>com.google.code.gson</groupId>
      <artifactId>gson</artifactId>
      <version>2.8.9</version>
  </dependency>

and remove json dep

@rultor hello

@rultor hello

@l3r8yj Hi there! I understand a few simple commands: "merge", "deploy", etc. This page explains them briefly. Any questions or bug reports are welcome. Have fun :)


103|| Binary Tree Zigzag Level Order Traversal || CPP

solution for 103. Binary Tree Zigzag Level Order Traversal
Create code for the problem 103. Binary Tree Zigzag Level Order Traversal
Type of Issue -
Please add/delete options that are not relevant.

[x] Adding New Code
[] Improving Code
[] Improving Documentation
[] Bug Fix

Programming Language
Please add/delete options that are not relevant.

[] Python
[x] C++
[] Java
[] SQL

Self Check

Ask for issue assignment and wait to get assigned to it before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Discord server ✉ - https://discord.gg/CXksGdn
Happy Coding,

I have already made the pull request. Please take a look through it.


Mockchain delegation certificates

This extends the mockchain's Transaction type with a vector of Certificates, which are signed messages for registering/deregistering a stake key, registering/retiring a stake pool, and delegating from a stake key to a stake pool. They're in Transaction to ensure UTxO-based protection against replays and to allow fees/deposits if needed.
Handling of these messages to update the ledger/leadership will be a subsequent PR.

Updated: Blocks now have a list of Messages, which are an enum of SignedTransaction and the various delegation-related certificate types.


fix: prefix has random bit now

Description
pr-test.go has been updated so that the prefixes contain a random bit to avoid clashing.
Release required?

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

@toddgiguere what approach do you suggest here?

The main issue was that you cannot use "prefix" variable as part of a string that is passed into the DefaultWithVars function call, because the value of the prefix at that point is the static value without the random suffix. So the idea is that you have to let DefaultWithVars complete, then the options.Prefix value will be the static + random value that you want.
What I had suggested was to call DefaultWithVars to let the default variable map be set up, and prefix generated, then to add variables to the map after, using the new value for prefix.
This could be done a couple ways:

get the current map from Default call and add some new variables to it, and replace merged map back into options (which is what is being done here with the "copy-add-replace" logic)
add to the map from Default directly by using golang map key-value syntax, like options.TerraformVars["new_var"] = "new-value" (would need a line for each new input merged in)

Either way, the idea is you need to take the default map and "merge" in some new variables, since we cannot supply them at DefaultWithVars time.

Also in case you were wondering what maps.Copy(dest, src) was doing:
Copy copies all key/value pairs in src adding them to dst. When a key in src is already present in dst, the value in dst will be overwritten by the value associated with the key in src.

So what is done above is taking the original input vars map generated from DefaultWithVars (the dest) and merging into it the second set of input vars created after prefix was set (the src).

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


Feed wide read-only tokens

It seems to me that issuing read-only tokens on a feed specific basis is laborious and unnecessary. Currently, generating read-only tokens is a method of the feed object. Consider this example in python:
feed = client.feed('user', user.id)
return feed.get_read_only_token()

Now, shouldn't any user be able to read any users personal stream? So why the feed specific read-only token or even the need for a token at all? Would it not be simpler to avoid the need to create a token for each user feed?
return get_read_only_token('user')

so i think that is partially supported, @tbarbugli will know more

creating tokens with read access for all feeds is not exposed by a public method and it's not the default behavior, we'll probably add a few helper functions in the future for that.
In the meantime this should works for your use-case:
var streamSigner = require('getstream/src/lib/signing');
var apiSecret = '...';
streamSigner.JWTScopeToken(apiSecret, 'feed', 'read', {'feedId': '*'});

@tbarbugli Thanks for the solution

Sorry, to reopen this issue. I know I should have checked your solution worked before closing it @tbarbugli.
Anyway, it seems the token is not valid without specifying the feed ID:
streamSigner.JWTScopeToken(apiSecret, 'feed', 'read', {'feedId': '*'}); # 403 error

streamSigner.JWTScopeToken(apiSecret, 'feed', 'read', {'feedId': 'user2'}); # 200, okay

looking into that
On Thu, Mar 10, 2016 at 2:55 PM, Jacob Windsor<EMAIL_ADDRESS>wrote:

Sorry, to reopen this issue. I know I should have checked your solution
worked before closing it @tbarbugli https://github.com/tbarbugli.
Anyway, it seems the token is not valid without specifying the feed ID:
streamSigner.JWTScopeToken(apiSecret, 'feed', 'read', {'feedId': '*'}); # 403 error
streamSigner.JWTScopeToken(apiSecret, 'feed', 'read', {'feedId': 'user2'}); # 200, okay
—
Reply to this email directly or view it on GitHub
https://github.com/GetStream/stream-js/issues/79#issuecomment-194851967.


Make changing an element template a two-step action (unlink & choose new template)

Is your feature request related to a problem? Please describe.
Currently when working with element templates on service tasks, the Modeler User can switch freely between element templates using a dropdown. As soon as a template is selected, the values it specifies are directly applied to the respective fields.
This leads to the problem that other values, which the Modeler User has already set, are overwritten (potentially without the user noticing)
Describe the solution you'd like
This is a first solution-light to the problem. The goal of this solution is to make the application of an element template (and its value) a conscious decision for the user. Specification is yet to be clarified
Option A

[ ] As soon as a template was applied (by clicking on one element template from the dropdown), the dropdown is disabled
[ ] In order to re-enable the drop-down, the currently applied template needs to be "unlinked" by clicking a respective button. Unlinking would include a potential deletion of the specified parameters of that template so to not clutter the parameters (to be confirmed)

Option B

[ ] When selecting a new template, a confirmation dialog stating the consequences (overwrite of existing values) requiring an "Okay" by the user

Option C

[ ] we offer two things: either we keep all properties or we remove all properties (maybe except the element ID) regardless whether they were set by the template
[ ] When switching from one template to another, removing all properties seems to be a good default
[ ] When unlinking a template, then both options seems valid and we might offer them to the user

Future solution
Forward looking, the user shall retrieve more information about the impact of applying an element template by e.g., showing a dialog window which states all consequences of the application of that template (e.g., which fields are overwritten)
Additional context
Other issue relating to improvement of element template application: #1355

We have to answer two questions:

what happens when applying an element template?
what happens when removing/changing an element template?

In my opinion, solution A would not solve the problem. Data will still be overwritten. The only little benefit I see is that the 2-step action may help the user to understand that after removing a template its data remains (seeing some artifacts in the general tab afterwards).
I would like to suggest that we answer the two questions mentioned above by defining an automatism or by providing options to the user. A two-step solution would then not be necessary.
Option B may be the most simple solution but it would also not require a two-step-action.

Unlinking would include a potential deletion of the specified parameters of that template so to not clutter the parameters

this would require a major change in how element templates work today and might not be feasible for the first iteration.

When selecting a new template, a confirmation dialog stating the consequences (overwrite of existing values) requiring an "Okay" by the user

This would happen every time a user selects from the worker catalog, and would lead to a situation where less technical people would be faced with technical details that they cannot understand. Therefore, I'm not sure if option B would be a good way to go. I could imagine option B as an alternative in case the user wants to see this, but not the default.

Alternative:

we offer two things: either we keep all properties or we remove all properties (maybe except the element ID) regardless whether they were set by the template

When switching from one template to another, removing all properties seems to be a good default
When unlinking a template, then both options seems valid and we might offer them to the user
to be defined: how does this relate to initially applying an element template and what happens to properties that already existed before.

Will be closed by #1889


refactor(relative_tonalities): remove class

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 11 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+2.7%) to 41.156%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/src/tonality/key_signature.dart
0
11
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
2.7%

Covered Lines:
121

Relevant Lines:
294

💛  - Coveralls


Announcement: roadmap for fluent-ffmpeg v3

Hey there,
I'm planning to do a bunch of maintenance on this package and publish a version 3 in the coming weeks, hopefully before 2024.
The codebase is now pretty old and it is long overdue for some refactors.
Here is a rough outline of what version 3 will include.

Better CI (well, at least working CI) and package releases using Github Actions
API cleanup
Code refactors to move fluent-ffmpeg to more modern javascript
TS types at least, maybe plain Typescript
Promise-based API
Dropping some parts of the lib that no longer really make sense now (flvtool stuff, presets)

This will most likely introduce incompatibilities with code using version 2. As a consequence when v3 is released I will probably close all existing pull requests (some of them will be merged first, when they make sense).
The project is still lacking long-term maintainers and workforce to triage and answer issues. There have been some proposals in #755 but unfortunately they came at times where I was not really involved on the project nor watching answers, so if some of you reading this feel up to the task, drop a comment there.

Amazing! Thanks a lot 💪

Great, we need this repo to live long.  I am willing to contribute let me know if i can pick something. I am using this library in one of my projects. I hope many people still use it.

It's a really helpful tool to handle ffmpeg. I hope it will get the maintenance it deserves.

Is this still in plans?

hello, thanks for your work on it ? It is possible to provide v3 as beta tagged in npmjs ? At least, we can already work on it without rebuilding on our side.
but anyway thanks !

There will be an alpha as soon as it is usable

What is the status of plans to add types? I'd love to help with any TypeScript questions but I'm not familiar with this library yet. I want to be and TypeScript would help a lot.

Looks like they're on DefinitelyTyped https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/fluent-ffmpeg


droopy: remove macpath to migrate to py3.8

Motivation for this change
Fix proposed by upstream, but no patch is proposed:
https://github.com/stackp/Droopy/issues/27
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Could you open a PR upstream with the patch instead, and fetch the commit in your fork with fetchpatch ?

Could you open a PR upstream with the patch instead, and fetch the commit in your fork with fetchpatch ?

That was done and now the patch is fetched. Sometimes GitHub doesn't notify commenters on PRs when the OP (force) pushes a commit


Backspace bring the cursor to the beginning of the line

If I press the backspace from an indented text, the text positioned to the beginning of left.

This is already fixed by changing grammar in https://github.com/ballerinalang/plugin-intellij/commit/29760b3fc3f45355835c94bc3352bba993a65cc0.


changing packages in create

replaced catchall python package on line 61 with 3 individual packages. Original breaks Fedora Rawhide, proposed change

Coverage remained the same at 64.489% when pulling 16d1b2fd0b6396c78766a802aaf7af332ffb5a85 on gwencasey96:master into b0f2e6308dedbbf450ec55578fcb4467c3272306 on OPAE:master.

Closing this, as CI is hung (fork). See #2656 instead.


DM-20267: Add required README.txt to /datasets/refcats/htm

While creating the reference catalog readme file, I realized we could use more guidance about how to manage the contents of this file.

I've expanded the readme template and updated the descriptions of what goes where. Please have another look.
Built version: https://developer.lsst.io/v/DM-20267/services/datasets.html#reference-catalogs

The "responsibility" link is broken.


[PE-D][Tester C] Invalid deadline error message does not match actual error

Expected error message: The deadline should not be before the current date and time
Actual error message: Deadline should be in valid DateTime format: MMM dd yyyy HHmm
I believe that the format of my deadline is correct as shown in the screenshot above and that the error message is misleading.

Labels: type.FunctionalityBug severity.Medium
original: jinyang628/ped#6

Closes w #172


feat: emit slashing events

Motivation
Add proposer_slashing and attester_slashing to SSE
Description
Make sure new events introduced by https://github.com/ethereum/beacon-APIs/pull/376 are now emitted and made available via SSE.
Closes #6209

:tada: This PR is included in v1.16.0 :tada:


Query About Training SAVANA with CLR Data for Improved Results

Hello SAVANA Team,
I am currently using SAVANA for somatic structural variant calling with CLR (Continuous Long Read) data. However, we are not achieving the desired accuracy in our results. I understand that SAVANA allows for the training of a custom model using labeled VCF files.
My question is: Given the unique characteristics of CLR data, would it be a viable approach to train a new model with our CLR data to potentially improve the accuracy of SV calling? Are there any specific considerations or recommendations for this process when using CLR data?
Any insights or suggestions you could provide would be greatly appreciated.
Thank you for your time and assistance.

Hi there! Many apologies for my late response - I was working on a new release of SAVANA which should improve default performance on CLR data. However, if you still are seeing performance issues on CLR in v1.2.0, I would indeed recommend training a custom model. Besides the description of how to do this in the README, you can also refer to our preprint on details of how we generated our ONT training set. Happy to help troubleshoot if you run into issues training and using a custom model with CLR data.
All the best,
Hillary


Where did openapi.yaml come from?

Hi Jonathan,
How did you generate the openapi.yaml from the original api.yaml file that you got from Okta? I see that you did it in this commit: 775319f618be12d84b8c93cff1ac7b84bc462cf1
I'd like to update the openapi.yaml file to the newest version of the Okta api. I'd be happy to do a pull request back to you to help out. By the way, this is where I found the most up-to-date api.yaml file for Okta:
It appears that the npm module: https://www.npmjs.com/package/@okta/openapi has a<EMAIL_ADDRESS>file, but it references swagger, not openapi v3.0.0. Wonder if you found your spec in a different place, since it is also at https://github.com/okta/okta-sdk-java/blob/master/src/swagger/api.yaml, but which is a little bit older than the npm one.
Thanks!

Solution: I see that one can use https://mermade.org.uk/openapi-converter to convert from a swagger 2.0 spec (that Okta uses) to the newer OpenApi 3.0.0 spec.
New problem:
However, okra can't build the newest Okta version (1.11.2) of the spec:
error: failed to run custom build command for `okra v0.2.0 (/Users/greg/src/okra)`

Caused by:
  process didn't exit successfully: `/Users/greg/src/okra/target/debug/build/okra-48c008a156381622/build-script-build` (exit code: 101)
--- stderr
[/Users/greg/.cargo/registry/src/github.com-1ecc6299db9ec823/openapi-codegen-0.1.0/src/lib.rs:139] any_schema = AnySchema {
    schema_data: SchemaData {
        nullable: false,
        read_only: false,
        write_only: false,
        deprecated: false,
        external_docs: None,
        example: None,
        title: None,
        description: None,
    },
    pattern: None,
    multiple_of: None,
    exclusive_minimum: None,
    exclusive_maximum: None,
    minimum: None,
    maximum: None,
    properties: {},
    required: [],
    additional_properties: false,
    min_propeties: None,
    max_properties: None,
    items: None,
    min_items: None,
    max_items: None,
    unique_items: None,
    format: None,
}
thread 'main' panicked at 'not yet implemented', /Users/greg/.cargo/registry/src/github.com-1ecc6299db9ec823/openapi-codegen-0.1.0/src/lib.rs:140:21


run command: argument parsing is fuzzy

I want to invoke an inline shell script inside the container but unfortunately shell's options are being eaten by buildah:
$ sudo buildah run python-working-container /bin/sh -c 'ls /'
Incorrect Usage: flag provided but not defined: -c

NAME:
   buildah run - Run a command inside of the container

USAGE:
   buildah run [command options] CONTAINER-NAME-OR-ID COMMAND [ARGS [...]]

DESCRIPTION:
   Runs a specified command using the container's root filesystem as a root
   filesystem, using configuration settings inherited from the container's
   image or as specified using previous calls to the config command

OPTIONS:
   --runtime path            path to an alternate runtime (default: "runc")
   --runtime-flag value      add global flags for the container runtime
   --volume value, -v value  bind mount a host location into the container while running the command

ERRO[0000] flag provided but not defined: -c

$ sudo buildah run python-working-container /bin/sh "-c 'ls /'"
Incorrect Usage: flag provided but not defined: -c 'ls /'

...

$ sudo buildah run python-working-container /bin/sh -- -c 'ls /'
/bin/sh: 0: Can't open -c

$ sudo buildah run python-working-container /bin/sh '-c "ls /"'
Incorrect Usage: flag provided but not defined: -c "ls /"

...

@nalind just suggested over IRC to do
sudo buildah run -- python-working-container /bin/sh -c 'ls /'

which works just fine! Thank you!


Read timed out after 10 seconds

We are using a Zend Cache folder inside of the deployment folder. The files are created by user "apache" with permissions 700 (no rwx for group or others). Zend Server which is using user "zend" would not be able to remove old deployments completely because of this remaining temp folder. This seems to be related to the pretty consistent error message of ZS client after exactly 10 seconds. Zend Server (8.5.3) still continues with the deployment, but ZS client stops with a read time out:
======================================================================
The application has thrown an exception!
Zend\Http\Client\Adapter\Exception\TimeoutException
Read timed out after 10 seconds

We will fix the permission issue for Zend Cache, but ZS client should react differently. We are using --safe, --wait and --http="timeout=120"

@plmsprd Can you send  me [slavey (at) zend.com ]  sample zpk so that I can reproduce the issue?  Also logs from Zend Server will be helpful.


Layout needs improvements

Make order of the sites to be case insensitive (so "bB" would be at top, not at the bottom).
"Quick search:"  string looks out off place, maybe move it above the sites.
Make "Batch transfer" button a bit smaller, more near the size of the site names.
Move "Covert to thumbnails" button in a new row below Douban stuff.
Make all white buttons to look more like a button, maybe some color and style would help.

Here how it look on ptp initially and after both middle buttons pressed:

What you think about dual language (check if script at my fork works for you)?

@Purfview 1 will be fixed.
2 do you mean the Quick Search string is too long?
3 change to a text button maybe look great.
4. move button to a new row may waste more space.Make the button more smaller may be a good choice
5. Dose the color of the button make you confused？🤔 The button style is from UI component Element.
6. Many thanks for your translation. Looks perfect.
Your way is more efficiency. I'm considering create sth like laguage config json though. It can reduce more conditional judgment.

Convert  tags to .

I meant to make it more ergonomic, like "Transfer to", to be on the same line with the site names.

Or maybe change "Working.../Success!" messages to colors of the button like "Yellow/Green". Jumping buttons around is not a good design in general. :)

Not confusing, just buttons look bland, maybe some more visible border would help.

Separate config module would be the best approach, but I doubt that anyone will want to translate it to more languages.

Got it. I'll fix them all in next version(maybe 1.2.7😝)
6. English is enough

7. That rotating config button consumes so much cpu/gpu for some reason. If  I apply my Darkmode script on top of it then it starts to consume a whole core.  :astonished:

8.Rotating svg button sometimes doesn't work, like it doesn't register clicks.
On my fork I tried a png image and it solved the click problem, but cpu/gpu consumption is same, looks like that css animation eats a lot of cpu/gpu cycles on some styles.
(Need to find some good gif creation program.)

@Purfview Have you tested the cpu consumption is exactly caused by the rotate icon?I checked yesterday,didn't reproduce this issue.

Yes, and I found info on internet that those css animations are cpu/gpu hungry, nothing can be done about them.
First I noticed unusual high speed on GPU fan, bit by bit I found that if you disable rotation on icon then GPU fan gets quiet, then I disabled hardware acceleration in browser and then CPU usage jumped up when I enabled rotation animation.

@Purfview Maybe I should just remove the animation.The only purpose of the animation is drawing some attention in case of that users don't know where is setting panel.

I like animated icon and yes it directs users where settings are.
Gif animation would solve cpu/gpu usage problem, but I couldn't find good gif on internet, need to DIY with some soft.

@Purfview I'll try it out.

Found that Photoshop has function to create animated gifs. I created one but problem is that small gifs(64x64) have visible artifacts which looks bad on a dark background. :anguished:
I think good solution would be an option in settings to turn off animation.
Check if png icon in my fork look good to you, I can PR it to solve randomly not registering mouse clicks on the svg icon.

No, it's caused by css "animation".


Add ITComputeTest test for resource name

For testing https://github.com/googleapis/google-cloud-java/issues/4416.
~This test won't pass until artman is updated with https://github.com/googleapis/gapic-generator/pull/2529 and the clients are refreshed.~ Edit: blockers are gone

How do i format the code?

I think its mvn com.coveo:fmt-maven-plugin:2.8:format

@igorbernstein2 No luck, the tool returns success without changing any files.

@kolea2 Is there anything else I can do to fix the formatting on the diff?

Hey @andreamlin! I locally ran 'mvn com.coveo:fmt-maven-plugin:format' on your branch and it reformatted the file for me - looks like there are some unused imports and it reformatted a comment. Let me know if you need help getting it to work or I can try to push my changes as well.

@kolea2  Thanks for the fix! Would you mind reviewing?

Fixed up comments. PTAL


Added localized warning ignore for GCC 9.x and above

for returning a local initializer_list object:
In file included from /home/aditya/projects/ginkgo/core/test/utils.hpp:49,
                 from /home/aditya/projects/ginkgo/core/test/matrix/identity.cpp:43:
/home/aditya/projects/ginkgo/core/test/utils/assertions.hpp: In instantiation of ‘std::initializer_list<std::initializer_list<_Tp> > gko::test::assertions::detail::l(std::initializer_list<std::initializer_list<_Tp> >) [with T = double]’:
/home/aditya/projects/ginkgo/core/test/matrix/identity.cpp:125:5:   required from ‘void {anonymous}::Identity_AppliesToMultipleVectors_Test<gtest_TypeParam_>::TestBody() [with gtest_TypeParam_ = std::complex<float>]’
/home/aditya/projects/ginkgo/core/test/matrix/identity.cpp:113:1:   required from here
/home/aditya/projects/ginkgo/core/test/utils/assertions.hpp:694:12: warning: returning local initializer_list variable ‘list’ does not extend the lifetime of the underlying array [-Winit-list-lifetime]
  694 |     return list;
      |            ^~~~
/home/aditya/projects/ginkgo/core/test/utils/assertions.hpp:692:53: note: declared here
  692 |     std::initializer_list<std::initializer_list<T>> list)
      |     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~
/home/aditya/projects/ginkgo/core/test/utils/assertions.hpp: In instantiation of ‘T gko::test::assertions::detail::plain_ptr(T) [with T = std::initializer_list<std::initializer_list<double> >]’:
/home/aditya/projects/ginkgo/core/test/matrix/identity.cpp:125:5:   required from ‘void {anonymous}::Identity_AppliesToMultipleVectors_Test<gtest_TypeParam_>::TestBody() [with gtest_TypeParam_ = std::complex<float>]’
/home/aditya/projects/ginkgo/core/test/matrix/identity.cpp:113:1:   required from here
/home/aditya/projects/ginkgo/core/test/utils/assertions.hpp:724:12: warning: returning local initializer_list variable ‘ptr’ does not extend the lifetime of the underlying array [-Winit-list-lifetime]
  724 |     return ptr;
      |            ^~~
/home/aditya/projects/ginkgo/core/test/utils/assertions.hpp:722:15: note: declared here
  722 | T plain_ptr(T ptr)

I think this warning is spurious, since the underlying data we are returning is never created locally in the l functions. The pragmas help keep build output clean, and help for people using (Spac)Emacs to jump to errors. Thoughts?

You make a good point in terms of making the build output less noisy - this is definitely something we should tackle!
I remember a while ago trying to fix the underlying issue, but I would need to take a look at the details again. Maybe passing by reference might be a first step.

I think we discussed this some time back, as much as possible we would like to avoid ignoring warnings because in case there is a legitimate warning in the future, this may get ignored.

Observations: GCC 9 gives this warning (and maybe GCC 10, not sure). nvcc with GCC 8, Clang 10 and Clang 12 do not.
@pratikvn I understand your concern; I don't really want to remove warnings either. But it's also easier to miss useful warnings when you have to sift through a number of false positives. Besides, the warning is only removed for those three specific functions (two ls and one plain_ptr). So if we can determine that the warning does not apply to these functions, maybe we should remove the warning just for them.
@upsj I'm wondering if these functions obey the standard. Going over cppreference, I'm not completely sure, though I would guess they're fine.

I tried out a fix for the underlying issue, which you can see in https://github.com/ginkgo-project/ginkgo/pull/663/commits/4e67674c011ca53cb6cfee8222e55e06c5c20b20. I believe this should not lead to any lifetime issues, since we only use plain_ptr and l on temporary initializer lists that live as long as the surrounding full-expression.

Great, thanks! I was thinking of trying const references too, based on the warning message, but abandoned the idea because I don't entirely get the point of these functions and didn't want to risk it. If you're sure references are fine, maybe we can reject and close this PR. If I make the exact changes you made, I guess it should merge smoothly when I pull from you later.

The l functions are there exclusively to help with template argument deduction: In templated tests, we need a way to transparently specify the ValueType which the initializer_lists should use. plain_ptr is used to uniformly use smart pointers, plain pointers and initializer lists in GKO_ASSERT_MTX_NEAR


[ja] Translated content/ja/blog/_posts/2024-08-12-feature-gates_client-go.md

[ja] Translated content/ja/blog/_posts/2024-08-12-feature-gates_client-go.md
Description
Translate
content/en/blog/_posts/2024-08-12-feature-gates_client-go.md
into Japanese
content/ja/blog/_posts/2024-08-12-feature-gates_client-go.md
Issue
Closes: #47473
Robot
/area localization
/language ja

/assign nasa9084
for approval


Register shutdown function to clear event loop

This repeatedly registers shutdown functions which run the event loop until a function does not discover any additional enabled and referenced callbacks in the event loop. The first invocation of the shutdown function always registers another invocation so that any shutdown functions registered during script execution are executed before the second invocation.
There are edge cases where a shutdown function registering another shutdown function which then adds callbacks to the event loop may not be executed, but I consider those cases highly unlikely. I think this will cover every practical use case to avoid unexecuted events on script termination.
Testing shutdown functions in unit tests is difficult, so I added an example which demonstrates the new shutdown behavior.

Something like
EventLoop::unreference(EventLoop::onSignal(SIGINT, function () { throw new SignalException(); }));
getStdin()->read();

will cause a hang here, unless we getStdin()->unreference() in onShutdown (this is how I do it in MadelineProto).

While the issue of unreference watchers is generalized, a CTRL-C while reading from STDIN is an especially nasty case for CLI applications, and an extremely common one too.

I'm not sure whether we want to happen this unconditionally. I mean, the application may be in an unexpected state upon shutdown being called, especially when the cause is a fatal error or uncaught exception.
I feel like this should be configurable.
Also, how is a server application going to even actually abort on error?

... Is it possible to just check whether the cause of stop is an error? And if yes, don't run the event loop automatically.

Well that pretty much spoils this idea. I forgot thrown exceptions would still trigger a shutdown function. Back to the drawing board I suppose. I'm not sure there's a good way to solve this problem outside of recommending applications use EventLoop::run() instead of relying on suspending {main}.

@trowski Shouldn't just a simple check for error_get_last()["type"] == E_ERROR (and the other few fatal type errors like E_CORE_ERROR) and such be enough?

+1 @bwoebi Yep I share the concerns.
There are two main usecases for this:

Partially synchronous (fpm) applications using amphp libraries: since running the event loop will mainly just finish flusing data to sockets, thus the behavior in this PR is very much desired.
I am using using precisely the behavior of this PR @ work (type 1 partially synchronous application).

Fully async applications using EventLoop::run(): running the event loop on shutdown is still needed for the reasons in 1, but it becomes problematic with many independent background fibers each doing async work (and continuing to do so when the event loop is restarted)
MadelineProto is a type 2 application, and re-starts the event loop on shutdown only to do some cleanup, and save state, without actually running EventLoop::run(): https://github.com/danog/MadelineProto/blob/v8/src/Shutdown.php#L59.

In both cases, there is a risk of working with partially corrupted state in case of exceptions, but the benefits of finishing any pending work overweigh the risk (and personally I never encountered issues with this).


[Snyk] Security upgrade @backstage/errors from 0.0.0-use.local to 0.1.1

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):

packages/repo-tools/package.json

Note for zero-installs users
If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Regular Expression Denial of Service (ReDoS) SNYK-JS-PATHTOREGEXP-7925106
  67

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Regular Expression Denial of Service (ReDoS)

🎉 Snyk hasn't found any issues so far.
✅ code/snyk check is completed. No issues were found. (View Details)


Glob Inclusion Issue

Hello dear:
I have met a question when I use the global Inclusion  in my project like this :
[
    {
        "include" : "*.json"
    }
]

but there exists a problem
[main] ERROR Illegal char <*> at index 0: *.json

I try to escape the regular with \*, but it does work. I do not know how to deal with it , please give me  some advice,thank you!!!

Glob inclusion is provided in 0.12.0, please check your Moco version. On the other hand,  it is used for global configuration which is used with "-g" option.

Thank you for your answer!
I hava checked my moco, My Moco version is  0.12.0, and this is my start command :

this is my global configuration file:

Thank you for your answer!
I hava checked my moco, My Moco version is 0.12.0, and this is my start command :

this is my global configuration file:

@dreamhead
I have found that it's related with platform. In Windows, it can't be built successfully. In Mac, everything is OK.

@waitshang Thank you for your reminder.


Create ParseFileWithPlantUmlTask.groovy

In one of my project, I needed the ability to parse a few files individually via plant uml. Here is a task that you could add to your plugin to make it easer.
I use it this way :
task createOverviewWithPlantUmlTask(type: ParseFileWithPlantUmlTask) {
  sources = [project.file('overview.html')]
  destDir = project.file("$buildDir/javadoc/")
}

:+1: for identifying a required feature: I have filed it as a new feature request for the records.


How to use font which is stored in another project as Resource ?

I'd like to store my fonts in a library where everything is stored as Resource and could be used on Android or iOS.
Can you show how to do that ? How to reference a font from another project ?
I think it will add a lot of value in the documentation.
Thanks

Hi @Nk54
Are you talking about Xamarin.Forms?


Comment on video

Hi Peaches!
Just watched your presentation. Good job!
One thing that I'm curious about now: You mentioned that most woylie sightings were in the spring, in the early analysis in the report. But when you analysed the tourism data you also noticed that the holiday tourists were highest in Q3, which is spring. However, you didn't make the connection between your early finding and the tourism pattern. Why not?

Hi Dianne,
Thankyou so much for taking the time to review our presentation and apologies to have missed your opened issue.
With respect to your question, while you correctly pointed out that the tourism pattern and the Woylie sightings appear to be highest during the spring season, however, we were concerned whether we should state that as a result of the following:

The location of interest (Narrabri regions) has only been a home to the Woylies very recently in the year of 2022 (majorly due to conservation efforts where these endangered animals were translocated from WA to NSW). Hence, there was a sudden spike in the number of sightings within that region but for a very short period of time.

For the Narrabri regions, the holiday tourists in the year of interest was only for Quarter 3. However, going by just the data of one year, we felt it might not be appropriate to comment whether there is indeed a correlation between the number of tourists and the Woylie sightings.

Figure 17 illustrates the trend line graph of Woylie Sightings in Narrabri Surrounds as well as the holiday tourists in the region for the year of 2022. While there were Woylie sightings in this region during quarter 3, there were infact a lot more sightings in quarter 4 aswell but there were no tourists recorded in the region in that period.

The reasons above allowed us to conclude that there is a requirement of further analysis and data to ascertain the tourism pattern and any consequent correlation with the Woylie sightings.


"go: error loading module requirements" in sircleci jobs

Expected Behavior
All go modules correctly downloaded
Current Behavior
Tests fail with error
go: error loading module requirements
Failure Information (for bugs)
Workflows with error:
https://circleci.com/gh/networkservicemesh/networkservicemesh/63817
https://circleci.com/gh/networkservicemesh/networkservicemesh/63675
Context
Try to use scripts/go-mod-download.sh before running go scripts

From here:

go mod vendor - resets the main module's vendor directory to include all packages needed to build and test all of the module's packages based on the state of the go.mod files and Go source code.
By default, go commands like go build ignore the vendor directory when in module mode.
The -mod=vendor flag (e.g., go build -mod=vendor) instructs the go commands to use the main module's top-level vendor directory to satisfy dependencies. The go commands in this mode therefore ignore the dependency descriptions in go.mod and assume that the vendor directory holds the correct copies of dependencies. Note that only the main module's top-level vendor directory is used; vendor directories in other locations are still ignored.

I suppose it is a very useful mechanism for us. @haiodo @edwarnicke @nickolaev what do you think?

we could use partial vendoring for utilities like linter. Its possible with using godep or govendor.
What do you think?

It's a cloud native world - design for failure :)
I don't like (1) as it implies adding vendored code in our tree, let's avoid that. (2) is probably my favourite, as it is very often a network/service flakiness that leads to these issues.  Maintaining a docker image as proposed in (3) might be an additional burden to carry with the project, but is a generally good idea.
(4) the linter has both a docker image and a pre-compiled binary, why not use those? E.g. downlaod the binary unarchive it and put it in the $PATH so make can find it.


Oath2 authentication issue with dev mode

Bug description
I have an Oauth2 credential set up with Google and am trying to integrate it with my local wundergraph environment.

I have a self-signed certificate for local https
I have HOST rewrites set up on my device to redirect the domains to the correct IPs

When I start the WG application with wunderctl up and try the login flow, I get an error from the Google Oauth2 screen:

Access blocked: This app’s request is invalid
Error 400: redirect_uri_mismatch
You can't sign in to this app because it doesn't comply with Google's OAuth 2.0 policy.
If you're the app developer, register the redirect URI in the Google Cloud Console.
Request details: redirect_uri=http://api.my-local-url.com/auth/cookie/callback/google

Even though I have the wundergraph.config.ts setup as https, it sends me to http instead:
  ...
  authorizedRedirectUriRegexes: ["https://api.my-local-url.com/*"]
  ...

I've also verified that I have the Authorized redirect URIs in Google Credentials set up correctly as:
https://api.my-local-url.com/auth/cookie/callback/google

If I simply change wunderctl up to wunderctl start, then the authentication flow works.
How to reproduce

Generate a local self-signed certificate
Set up a demo UI and wundergraph backend with HTTPS
Add hosts file rewrites to point an example dev.domain.com to the UI and api.domain.com to wundergraph
Set up a Google Oauth2 credential flow with the correct redirects
Run wunderctl up and watch the workflow fail
Run wunderctl start and watch the workflow succeed

Expected behavior
Wundergraph should not rewrite the redirect_uri as http when it is provided as https in the config.
WunderGraph information
wundergraph.config.ts:
import {
    EnvironmentVariable,
    authProviders,
    configureWunderGraphApplication,
    introspect,
    templates
} from "@wundergraph/sdk"
import operations from "./wundergraph.operations"
import server from "./wundergraph.server"

const spaceX = introspect.graphql({
    apiNamespace: "spacex",
    url: "https://spacex-api.fly.dev/graphql/"
})

const hasura_user = introspect.graphql({
    apiNamespace: "user",
    url: new EnvironmentVariable("HASURA_GRAPHQL_HTTP_URL"),
    introspection: {
        pollingIntervalSeconds: 30
    },
    headers: (builder) => {
        builder.addStaticHeader("x-hasura-admin-secret", new EnvironmentVariable("HASURA_GRAPHQL_ADMIN_SECRET"))
        builder.addStaticHeader("x-hasura-role", "user")
        return builder
    }
})

const hasura_admin = introspect.graphql({
    apiNamespace: "admin",
    url: new EnvironmentVariable("HASURA_GRAPHQL_HTTP_URL"),
    introspection: {
        pollingIntervalSeconds: 30
    },
    headers: (builder) => {
        builder.addStaticHeader("x-hasura-admin-secret", new EnvironmentVariable("HASURA_GRAPHQL_ADMIN_SECRET"))
        builder.addStaticHeader("x-hasura-role", "admin")
        return builder
    }
})

// configureWunderGraph emits the configuration
configureWunderGraphApplication({
    apis: [hasura_user, spaceX, hasura_admin],
    server,
    operations: operations!,
    generate: {
        codeGenerators: [
            {
                templates: [
                    // use all the typescript react templates to generate a client
                    ...templates.typescript.all,
                    templates.typescript.operations,
                    templates.typescript.linkBuilder
                ]
            },
            {
                templates: [templates.typescript.client],
                path: "../../packages/generated-wundergraph"
            }
        ]
    },
    cors: {
        allowedOrigins: ["https://et2-dev.com/"] // process.env.NODE_ENV === "production" ? ["https://*"] : ["http://*"]
    },
    authentication: {
        cookieBased: {
            providers: [
                authProviders.google({
                    id: "google", // unique id for this provider
                    clientId: new EnvironmentVariable("GOOGLE_CLIENT_ID"),
                    clientSecret: new EnvironmentVariable("GOOGLE_CLIENT_SECRET")
                })
            ],
            secureCookieHashKey: new EnvironmentVariable("WG_SECURE_COOKIE_HASH_KEY"),
            secureCookieBlockKey: new EnvironmentVariable("WG_SECURE_COOKIE_BLOCK_KEY"),
            csrfTokenSecret: new EnvironmentVariable("WG_CSRF_TOKEN_SECRET"),
            authorizedRedirectUriRegexes: ["https://my-local-url.com/*", "https://api.my-local-url.com/*"]
        }
    },
    security: {
        enableGraphQLEndpoint: process.env.NODE_ENV !== "production"
    }
})

Environment & setup

OS: Windows 11 / Ubuntu 20 WSL2
Database: PostgreSQL 15
Node.js version: v18.16.0

WunderCtl Version
Version: 0.154.0
Commit: 761d46c51cdb92da6fce745777bf4bf89e6c9bfe
Date: 2023-05-26T17:40:27Z
BuiltBy: ci

On the cmd wunderctl up (or start) can you try setting the flag --disable-force-https-redirects?

Hi @jensneuse, when I tried to add that flag it had this error:

Error: unknown flag: --disable-force-https-redirects

I see, you're right. When using "start", we actually enforce https redirects, but allow you to disable it.
When using up, we default to http and you currently cannot change it:
https://github.com/wundergraph/wundergraph/blob/main/pkg/authentication/oidc.go#L173
I'll create a ticket internally. I think it would be best if we give the user more flexibility in configuring this per auth provider. WDYT?

Cool, that sounds like a good idea. Thanks for the quick response!

Still open.


Add a pipeline data source

This adds a data source for fetching the properties of a single pipeline. The pipeline is specified using a slug, available in the
pipeline URL on buildkite.com.
This could be particularly useful for folks who want to lookup the webhook URL and set it on a GitHub repo (using the  GitHub terraform provider).
Closes #93

still to come: tests

The CI build is green, and I've manually run the acceptance tests to confirm they're also green:
$ BUILDKITE_ORGANIZATION=foo BUILDKITE_API_TOKEN=bar TF_ACC=1 go test -v ./...
?       github.com/buildkite/terraform-provider-buildkite       [no test files]
=== RUN   TestAccDataPipeline_read
--- PASS: TestAccDataPipeline_read (6.00s)
=== RUN   TestProvider
--- PASS: TestProvider (0.00s)
=== RUN   TestProvider_impl
--- PASS: TestProvider_impl (0.00s)
=== RUN   TestAccAgentToken_add_remove
--- PASS: TestAccAgentToken_add_remove (2.37s)
=== RUN   TestAccAgentToken_update
--- PASS: TestAccAgentToken_update (5.57s)
=== RUN   TestAccAgentToken_import
--- PASS: TestAccAgentToken_import (2.82s)
=== RUN   TestAccPipeline_add_remove
--- PASS: TestAccPipeline_add_remove (3.08s)
=== RUN   TestAccPipeline_add_remove_complex
--- PASS: TestAccPipeline_add_remove_complex (3.10s)
=== RUN   TestAccPipeline_update
--- PASS: TestAccPipeline_update (5.60s)
=== RUN   TestAccPipeline_import
--- PASS: TestAccPipeline_import (3.73s)
PASS
ok      github.com/buildkite/terraform-provider-buildkite/buildkite     32.284s


Changes to ClosureAstTransformer to fuse JS emitting and printing

Moving back to draft due to: https://github.com/scala-js/scala-js/pull/4917#issuecomment-1873311523

This is not necessary given the current state of #4917. However, I'll leave this PR open until the review is done.


initial support for external components is working

Missed a number of renames from "default" to "global". Fixed them all.
Good work :-)  !!


feat: Show active file name when saving to current file

Screenshots

Long file name

Closes
#3650

Notes:

I'd not make it into an input at all since that suggests editability. I'm not technically against making it editable, but would leave that for later as we'd need to figure out how it should behave — rename the file (if possible)? Save to a new file handle?

The shape props menu should account for the fileHandle and not overflow the footer:

I've changed it more to look like the UI from #3381
Fixed it by changing the max height of shape props menu depending on whether active file name is shown

I'd tweet it alongside https://github.com/excalidraw/excalidraw/pull/3717 once merged

shipping 🎉


Armature modifier applies last pose when "apply modifiers" is active

As noted in https://github.com/KhronosGroup/glTF-Blender-Exporter/pull/166#issuecomment-395833769, when exporting a model with an armature, the last pose before exporting will be applied.
This is pretty problematic, as it deforms all animations (unless the armature was in a rest pose anyway).
The FBX exporter addresses this problem by saving all armature states before the export, then setting all the armature states to REST, exporting the mesh with applied modifiers, then restoring the previous states.
This can be worked around by making sure that an action with the rest pose is on top in the NLA and the only strip contributing. But it can cause a lot of pain and confusion when setting up an initial workflow. It certainly took me a while to figure it out the first time!
(Actually I found this problem in another Blender exporter, a better COLLADA exporter for the Godot game engine, here the PR that fixed the problem: https://github.com/godotengine/collada-exporter/pull/65. I noticed this exporter has the same problem, so the PR in the other project might be helpful as a reference, as well as the standard FBX exporter in Blender).

It looks like the FBX exporter just skips Armature modifiers, when "Apply Modifiers" is selected... do you know if that would be an acceptable fix here?

/cc https://github.com/KhronosGroup/glTF-Blender-Exporter/issues/142.

Fixed in new repo (https://github.com/KhronosGroup/glTF-Blender-IO/), we no longer apply the Armature modifier when this option is enabled.


Restoring/removing bg keeps the same size

Description (what's changed?)
Restoring/removing bg keeps the same size.
Testing instructions

Generate an image. Shrink it. Remove bg. Image will have the same size
Restore bg. Image will still have the same size.

Task linked: CU-86ay5qk67 Restore Bg should be keep size as original


Can't be read / closed with TalkBack

[x ] I have verified the issue exists on the latest version
[ x] I am able to reproduce it

Version used:
1.13.0
Android version:
9
The announcement can't be read via TalkBack. Even worse: it can't be closed via TalkBack too! (it can, but only with the back button and since there is no indication what's going on, a blind person has no idea they should do this). This means that this library basically renders the app unusable for blind people.
The easiest fix would be to simply not show anything when touch navigation is enabled:
fun Context.isTouchExplorationEnabled(): Boolean {
    // can be null during unit tests
    val am = getSystemService(ACCESSIBILITY_SERVICE) as AccessibilityManager?
    return am?.isTouchExplorationEnabled ?: false
}

Actually making it work would be a very nice option. With it, you'd have to set the contentDescription to View and allow closing it by clicking on it when touch exploration is enabled.

it would be amazing if the content of the feature can be read from talkback, I tried right now and it's a frustrating experience, imagine from blind people.

Are there any updates on this issue? I would like to add that the missing content description also generates a warning in Google's pre-launch report that I'm not able to solve.


Not all profiles have view counts.

Description
I was looking at the popular profile pages and saw mine there, I went to check the view count on the profile and it wasn't there, so I checked Eddie's and Pradumna's and they have it. There is other profiles on popular that don't have view counts.
Screenshots

Additional information
No response

It is off by default, you can enable it with "displayStatsPublic": true,, see the official example here in the docs...
https://github.com/EddieHubCommunity/LinkFree#-to-add-your-profile

Ok, I'll close this issue now :) XD

no worries, thank you for asking and closing 👍


IONIC 3 - Can't install native push

Ionic version:  (check one with "x")
[ X ] 3.x
I'm submitting a ...  (check one with "x")
[X] bug report
Current behavior:
When trying to install native push, I get the following:
      ionic cordova plugin add phonegap-plugin-push

cordova plugin add phonegap-plugin-push --save
✖ Running command - failed!
[ERROR] Cordova encountered an error.
You may get more insight by running the Cordova command above directly.
[ERROR] An error occurred while running cordova plugin add phonegap-plugin-push --save (exit code 1):
Installing "phonegap-plugin-push" for android
Plugin doesn't support this project's cordova version. cordova: 6.3.0, failed version requirement: >=6.4.0
Skipping 'phonegap-plugin-push' for android
Plugin "phonegap-plugin-push" already installed on browser.
Installing "phonegap-plugin-push" for ios
Plugin doesn't support this project's cordova version. cordova: 6.3.0, failed version requirement: >=6.4.0
Skipping 'phonegap-plugin-push' for ios
Saved plugin info for "phonegap-plugin-push" to config.xml
Error: Cannot find plugin.xml for plugin "com.googlemaps.ios". Please try adding it again.

Expected behavior:
It should install with no issues
Steps to reproduce:
Try simply to create a new project, then try to install native push and you'll fall in the same error.
Other information:
I've tried to uninstall both cordova and ionic and install it from scratch, then created a new project, but I got the same issue by the end.
I am guess that I need to update cordovan-cli to 6.5.0 or higher, I've done everything and it didn't work, after a new fresh ionic installation I got cordova 6.3.0
Ionic info:
global packages:

    @ionic/cli-utils : 1.4.0
    Cordova CLI      : 6.3.0
    Ionic CLI        : 3.4.0

local packages:

    @ionic/app-scripts              : 1.3.8
    @ionic/cli-plugin-cordova       : 1.4.0
    @ionic/cli-plugin-ionic-angular : 1.3.1
    Cordova Platforms               : android 5.2.2 browser 4.1.0 ios 4.2.1
    Ionic Framework                 : ionic-angular 3.5.0

System:

    Node       : v6.10.3
    OS         : macOS Sierra
    Xcode      : Xcode 8.3.3 Build version 8E3004b
    ios-deploy : 1.8.6
    ios-sim    : 5.0.8
    npm        : 3.10.10

As it says, it requires 6.4.0 or higher, no way around it. Try npm install -g cordova@latest or your preferred version if you have any

@AmitMY of course I've tried that already, it seems to be installed; however, when running an ionic info it shows 6.3.0

cordova -v output?

@AmitMY as I told you before that was 7.0.1 on ionic info it's still 6.3.0

This issue was moved to ionic-team/ionic-native#1756


Simon IO 100 Roller Blind is not working as Roller Blind.

Version
Build/Run method:
[X] Docker
[ ] Git Clone + yarn install + yarn run build + yarn start
[ ] Pkg
Z-Wave JS UI version: 8.16.6
Z-Wave JS version: 10.20.0
Describe the bug
After add a new device (a Simon IO 100 Roller Blind) is not detecting as a roller blind because in Home Assistant section it says this:

Here is all log since I have enabled import and since enabled log
debug.log
zwavejs_2023-05-15.log

If I'm not mistaken, this is a problem with MQTT discovery and not the driver.


Broken link in docs/4.x/navigation-views/#transitioner

Link to https://reactnavigation.org/docs/4.x/navigation-views/transitioner.md is currently a 404

Hey @jay-jlm
where did you find the reference for this link?

The link is in the issue titie ☝

The reference is in the Navigation views page in the Transitioner section

thanks! fixed in here https://github.com/react-navigation/react-navigation.github.io/commit/21c7d6aa6744657d2b92242e5c39ef61df220c32
for more info: https://reactnavigation.org/docs/4.x/upgrading-from-3.x/#removal-of-transitioner


Disallow all using robots.txt until on TDL

As long as we're on a subdomain, let's add a robots.txt file to prevent any SEO collisions with carbondesignsystem.com. To do so, in the web-app public folder, a robots.txt with:
User-agent: *
Disallow: /

We'll have another issue for updating this when on the TLD.

Hey team! Please add your planning poker estimate with ZenHub @alisonjoseph @andreancardona @francinelucca @jdharvey-ibm


Value Error and Invalid Checksum error nmea_serial

Ubuntu 18.04
ros melodic
Garmin 18x
Serial -> usb connection
I'm trying to run
rosrun nmea_navsat_driver nmea_serial_driver _port:=/dev/ttyUSB0 _baud:=4800

and the first error I get is:
Received a sentence with an invalid checksum. Sentence was: '1225,N,08835.9985,W,000.0,000.0,200420,003.4,W*79'

The follow up and the rest of the errors publishing are:
Value error, likely due to missing fields in the NMEA message. Error was: invalid literal for int() with base 10: ''. Please report this issue at github.com/ros-drivers/nmea_navsat_driver, including a bag file with the NMEA sentences that caused it.

I'd also like to add that using gtkterm with baud at 4800 and device set to /dev/ttyUSB0
$GPGSV,3,2,10,16,70,168,38,22,22,207,35,26,64,068,33,27,11,154,18*7A
$GPGSV,3,3,10,29,11,036,27,31,32,073,30*77
$GPRMC,132734,A,4401.1226,N,08835.9993,W,000.0,000.0,200420,003.4,W*7F
$GPGGA,132734,4401.1226,N,08835.9993,W,2,10,0.8,240.3,M,-34.1,M,,*7E
$GPGSA,A,3,03,04,09,14,16,22,26,27,29,31,,,1.5,0.8,1.2*39
$GPGSV,3,1,10,03,37,229,21,04,60,306,29,09,25,309,23,14,15,128,31*76
$GPGSV,3,2,10,16,70,168,38,22,22,207,35,26,64,068,34,27,11,154,18*7D
$GPGSV,3,3,10,29,11,036,27,31,32,073,30*77

After some investigation it looks like it's not parsing the utc-time values correctly?
$GPRMC,150225,A,4401.1254,N,08836.0000,W,000.0,000.0,200420,003.4,W*72
fix_valid:True
latitude:44.0187566667
latitude_direction:N
longitude:88.6
longitude_direction:W
speed:0.0
true_course:0.0
[WARN] [1587394945.612839]: Value error, likely due to missing fields in the NMEA messages. Error was: invalid literal for int() with base 10: ''
$GPGGA,150225,4401.1254,N,08836.0000,W,2,07,1.1,252.9,M,-34.1,M,,*74
fix_type:2
latitude:44.0187566667
latitude_direction:N
longitude:88.6
longitude_direction:W
altitude:252.9
mean_sea_level:-34.1
hdop:1.1
num_satellites:7
[WARN] [1587394945.755028]: Value error, likely due to missing fields in the NMEA messages. Error was: invalid literal for int() with base 10: ''

Found work around for GPGGA by removing nanoseconds in parser.py and returning unix_secs only.
Also work around for GPRMC is commenting out the
if sentence type rmc change to utc_time.
Then setting in the parse map RMC -> ("utc_time", convert_time, 1),


Remote content hash is always null when using Minio

Overview
When using Exfilac with a Minio server, unnecessary upload detection always fails because the remote content has is always null, even when the asset already exists on the remote and has not changed.
Details
Minio stores metadata header names capitalized, i.e. as X-Amz-Meta-Exfilac-Sha256. In contrast, I think AWS S3 stores these header names lowercased. As such, accessing the metadata from a Minio server returns a Map<string, string> containing {"Exfilac-Sha256": "..."} rather than the expected {"exfilac-sha256": "..."}.
I think the easiest resolution would be to wrap response.metadata() in a case-insensitive map, as I cannot configure Minio to return lowercased header names.

That's strange. I use minio locally as my main storage and I'm not seeing the same problem.
It would be easy to add a workaround for this, but I'd like to track down the actual underlying problem.
Is there something sitting between you and minio like a reverse proxy, perhaps? I use nginx for TLS termination between my device and minio. I wonder if, by doing that, I'm inadvertently working around this problem and haven't seen it. :thinking:

I'm using caddy v2 for TLS termination. Since minio is working in your setup, I'll do some investigation with my setup and get back to you.

Turns out caddy uppercases HTTP headers, rather than minio storing headers as capitalized. I set up nginx and caddy in front of a test minio instance, and wrote a header named x-amz-meta-sha256 through the nginx endpoint. While I didn't test this, I'd wager that caddy would rewrite headers to be capitalized when issuing a PUT through the caddy endpoint.
# 8881 is caddy
$ curl -IHEAD http://localhost:8881/hello/pasted.png
...
X-Amz-Meta-Sha256: asdf

# 8882 is nginx
$ curl -IHEAD http://localhost:8882/hello/pasted.png
x-amz-meta-sha256: asdf

I would have assumed that the AWS S3 SDKs would use case-insensitive maps for HTTP headers (or at least normalize), but I suppose that is not the case.

Thanks for tracking it down.
I agree that the app should work regardless of the header case. I'll add something in to ensure that it's not sensitive to case. :hourglass:


[Event Request] page 6510 "Item Tracking Lines" - OnBeforeTestTempSpecificationExists

We would like to add a new event OnBeforeTestTempSpecificationExists in the following procedure:
procedure TestTempSpecificationExists() Exists: Boolean
var
    TrackingSpecification: Record "Tracking Specification";
begin
    //A200F0000.Event.ns
    if not TrackingExists() then
        exit(false);
    //A200F0000.Event.ne
    TrackingSpecification.Copy(Rec);
    Rec.SetCurrentKey("Lot No.", "Serial No.");
    Rec.SetRange("Serial No.", Rec."Serial No.");
    if Rec."Serial No." = '' then
        Rec.SetNonSerialTrackingFilterFromSpec(Rec);
    OnBeforeTestTempSpecificationExists(Rec); //A200F0000.Event.n

    Rec.SetFilter("Entry No.", '<>%1', Rec."Entry No.");
    Rec.SetRange("Buffer Status", 0);

    OnTestTempSpecificationExistsOnAfterSetFilters(Rec);
    Exists := not Rec.IsEmpty();
    Rec.Copy(TrackingSpecification);
    if Exists and CurrentPageIsOpen then
        if Rec."Serial No." = '' then
            Message(Text011, Rec."Serial No.", Rec."Lot No.", Rec."Package No.")
        else
            Message(Text012, Rec."Serial No.");
end;

Event Signature:
[IntegrationEvent(false, false)]
local procedure OnBeforeTestTempSpecificationExists(var TrackingSpecification: Record "Tracking Specification")
begin
    //A200F0000.Event
end;

We already have event OnTestTempSpecificationExistsOnAfterSetFilters(Rec), why you cannot use this one?

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


@Loadbalanced "WebClient" does not have spring-retry LoadBalancer support just like "RestTemplate.

Question?
@Loadbalanced "WebClient" does not have spring-retry LoadBalancer support just like "RestTemplate.
ReactiveLoadBalancerAutoConfiguration does not have any implementation of Spring RetryTemplate just like LoadBalancerAutoConfiguration.
Can you please help to understand if this feature is missed or do we have any other approach to handle LB retry for WebClient?
If there is a different way to handle Spring RetryTemplate with @LoadBalanced WebClient; then please let me know?
And,
If this feature is a miss; then please confirm the same and also what would be the plan to include this?
Thanks!!

Project Reactor has retry functionality built in

Thanks @spencergibb for a quick reply. so you are suggesting to implement retry feature of Reactor framework with @Loadbalanced WebClient and not using Spring RetryTemplate.
And,
because Project Reactor has retry functionality, Spring RetryTemplate is not implemented with WebClient LB.
Correct??

Spring retry hasn't been updated to be reactive, so yes, that is what I'm suggesting

Thanks!!
I have additional questions on this:

Is there any plan to implement Project Reactor retry feature with @Loadbalanced WebClient?
As @Loadbalanced is Ribbon based; so do we have any plan to have retry feature available with @LoadBalancerClient (which is recommended as Ribbon is in maintenance mode) for reactive starter?

The retry features are not based on ribbon, but spring retry. We don't currently have plans for configurations driven retry for webclient when retry is built in to the Reactor api.

Thanks for all these details.

@spencergibb With the reactor built-in Mono.retry() feature, I believe that the LoadBalancerExchangeFilterFunction does not get re-applied on retries. That means that it keeps retrying with the same host, which isn't great since the host might be having issues, while other hosts might be just fine.
If my understanding is correct, I suggest reopening the ticket and implementing a higher level reactive retry feature that does go through LoadBalancerExchangeFilterFunction on each try.

What I'm observing is that the WebClient code goes through the filters synchronously and then delegates the HTTP connections asnychronously. So if you re-subscribe via retry(), you're not going back through the filters.


KeyParameter should be private or should use other namespace

Hi,
Love the library, it's saved me a lot of hassle with deflate calls. However, https://github.com/adamhathcock/sharpcompress/blob/master/src/SharpCompress/Crypto/KeyParameter.cs definitely needs to either have a different namespace or be private as it interferes with including actual BouncyCastle crypto libraries.

That was fast. Is there an ETA for next release? Guessing I should just reference by source for now.

I'll probably do it some time today as I've got a few things ready

Awesome, thanks!


Add support for free space threshold setting

Would this feature support mergerfs combined storage? I having an issue with media_cleaner.py trying to find the folder ( which im assuming is the mount point for the mergerfs folder?
2024-09-30 03:47:08 - INFO :: deleterr.py :: deleterr : Running version rfsbraz/deleterr:0.0.19
2024-09-30 03:47:08 - INFO :: deleterr.py :: deleterr : Log level set to INFO
2024-09-30 03:47:08 - INFO :: deleterr.py :: deleterr : Processing sonarr instance: 'sonarr'
2024-09-30 03:47:09 - ERROR :: media_cleaner.py :: deleterr : Could not find folder '/media/storage' in server instance. Skipping library 'TV Shows'
2024-09-30 03:47:09 - INFO :: deleterr.py :: deleterr : Freed 0.00 B of space by deleting shows
2024-09-30 03:47:09 - INFO :: deleterr.py :: deleterr : Processing radarr instance: 'Radarr'
2024-09-30 03:47:09 - ERROR :: media_cleaner.py :: deleterr : Could not find folder '/media/storage' in server instance. Skipping library 'Movies'
2024-09-30 03:47:09 - INFO :: deleterr.py :: deleterr : Freed 0.00 B of space by deleting movies


[SourceKit] Fix typo in SwiftDocSupport.cpp

extention -> extension

@swift-ci please test and merge


fix worker thread pool exhaustion bug

Fixed a bug where the supervisor can hang waiting for a thread from the worker thread pool which never becomes available. Also add a timeout for async operations as a safety for these kind of issues, and fix the unit test which should have caught this issue but was broken.

Tests failed to due checkstyle issue in #3567, @jon-wei could you take a look at that?

👍


Discussion of JGF metadata included

Right now, I am doing the following structure (for nodes)
spack root
  package --> name@version
  contains -- [lib] --> <library>
  contains -- [lib] --> <library>
  contains -- [bin] --> <binary>

And then the idea is that the edges are between packages and the libs and binaries - that seems like the level of what a user would look for. I've packaged additional metadata about a package with the node under "attributes" - a similar custom subsection to "paths." But even with a "small" spack install, it's huge. See: https://gist.github.com/vsoch/af1c57b558a476d1bb67fd78b284677e.
We likely want to discuss this structure and possibly trim away what is not needed to solve the immediate problem.  It could also be the case we aren't interested in every package of a spack install, but it's hard to say how to make that decision.

Easy idea for making this smaller - only represent one way of the edge (so one of "contains" or "in" but not both).


Docker

https://access.redhat.com/articles/1320623
manage yum repo
To avoid overloading /dev/mapper/sysvg-root, follow instructions in Use the Device Mapper storage driver.

Read iSolution tickets
Potentially reinstall Docker under /local

docker/overlay2 can sometimes get too big (see here). To completely refresh docker to a clean state:

stop the docker engine (systemctl stop docker);
delete the entire directory (not just the overlay2 folder) with rm -rf /local/scratch/software/docker/*
restart docker (systemctl start docker).


CompiledDataBinder: "Body of catch must have the same type as body of try" exception

Not too sure what to do with this one (not a big user of expressions)..

This console app reproduces it with 1.3.5, 0.2.12, and .net 7
        static bool HandleError(DataValidationContext validationContext)
        {
            return true;
        }

        public class X{
            public string UniqueIdentifier { get; set; }
            public DateTime RecordDate { get; set; }
            public decimal? Data1 { get; set; }
        }

        public static void Main(string[] args)
        {
            var csvStr = @"Z, Y, ID, X, W, V, A1, A2
""A"", ""B"", ""C"", ""D"", ""E"", 01/01/2000, 12.345, 67.890"u8;
            var schema = "ID>UniqueIdentifier:string,V>RecordDate:DateTime{dd/MM/yyyy},A1>Data1:decimal?";

            var opts = new CsvDataReaderOptions { Schema = new CsvSchema(Sylvan.Data.Schema.Parse(schema)), HasHeaders = true };
            using var csv = CsvDataReader.Create(new StreamReader(new MemoryStream(csvStr.ToArray())), opts).ValidateSchema(HandleError);

            var binderOpts = new DataBinderOptions() { BindingMode = DataBindingMode.Any };
            var l = csv.GetRecords<X>(binderOpts).ToList(); //boom
    }

ps; as noted I'd no idea what to do with it, but implementing BingAI's recommendation did at least stop it from throwing.. No idea if it's right or not

var catchExpr = Expression.Catch(exParam, Expression.Block(Expression.Throw(Expression.New(exCtor!, idxVar, exParam)), Expression.Default(typeof(void))));

Pumelling a couple of AIs eventualy got to the suggestion to change the code to:
var catchExpr = Expression.Catch(
			exParam,
			Expression.Block(
				Expression.Throw(Expression.New(exCtor!, idxVar, exParam)),
				Expression.NewArrayInit(typeof(object)) // Return an empty array of objects
			)
		);

which seems to stop the exception throwing, but no idea if it's right..

Sounds like you got it figured out?
The original issue is that there was nothing getting bound, because the headers had a space prefixed, which probably should have produced a binding error. Your code uses BindingMode.Any, which currently allows zero properties to be bound. Technically, it might make sense to allow a completely uninitialized T to be returned, since Any includes none, but I think in reality it would always mask a mistake of the user.
Would it have been more obvious if an UnboundMemberException had been thrown originally?

Yeah, I've resolved to start off with bindingmode All in future, and then swap it to Any.. Even when I was debugging Sylvan's code today, I'm looking at a vis of the physicalColumns var and pulling my hair out wondering "why are there 54 entities here and every single one of them has no name at all.. infact, no anything at all - all the properties are the default values?" - it was so easy to miss the leading space in the data vs the schema
"Any" probably should have a special case for when nothing matches, and perhaps raise an error if a schema mentions a property that doesn't exist - while we can't reasonably control whether a column is or isn't in a CSV from one file to the next, the compiled code nominating A>B could raise an error if B doesn't exist as a proeprty in a compiled class.. MissingMemberException?

Actually, thinking on it some more, I think my requirement to use Any is a consequence of not having available the mode that I really, actually want to use..
All notionally means "All columns in file related to All properties in model" but I have columns I don't want to use and for some files I have properties I cannot set (no data for them) but it doesn't matter for those props. I can't use AllColumns or AllProps either for the same reason; sometimes a file will have both unbound cols and result in unassigned props
.. and thus my only choice is to use Any, which doesn't check anything
Really, I'd like the schema, if I've used one, to be the driver for an All operation; if I've put columns in the schema that don't exist in the file, or i've mentioned props in the schema that don't exist in the class, then I should get an error so I can correct the code
In other words where we now have All/AllX driven by the file/class, have a different mode/setting where it's driven by the schema - do an All, but pretend that columns/props not mentioned in the schema don't exist

The data binder can use the DataMemberAttribute to allow mapping names that don't match the property. That attribute has an IsRequired member, but I don't currently look at it. I think it would make sense to enforce the binder binds all IsRequired properties regardless of BindingMode.

I've made two changes.

the binder must bind at least one property regardless of binding mode or an UnboundMemberException will be thrown.
the binder now honors the DataMemberAttribute.IsRequired property, such that any properties with that flag must be bound, or an UnboundMemberException will be thrown.

These changes are included in this pre-release package:
https://www.nuget.org/packages/Sylvan.Data/0.2.13-b0001
I'll release a 0.2.13 final release at some point in the near future.