ng update @angular/core fails

Versions
Angular CLI: 6.0.0
Node: 8.9.1
OS: win32 x64
Angular: 5.2.10
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.6.0
@angular-devkit/core         0.6.0
@angular-devkit/schematics   0.6.0
@angular/cli                 6.0.0
@schematics/angular          0.6.0
@schematics/update           0.6.0
rxjs                         5.5.10
typescript                   2.6.2

Repro steps

Follow steps at https://update.angular.io/
ng update @angular/core

Observed behavior
Package "@angular/compiler-cli" has an incompatible peer dependency to "typescript" (requires ">=2.7.2 <2.8", would install "2.6.2")
Invalid range: ">=4.3.0"

Desired behavior
I would expect this to work properly.
Mention any other details that might be useful (optional)
I tried to manually update the compiler-cli and run the update function again and got this:
$ ng update @angular/core
Invalid range: ">=4.3.0"

@markgoho-EDT, the ng update itself doesn't do anything else as showing the packages that have to be updated:
ng update
    We analyzed your package.json, there are some packages to update:

      Name                               Version                  Command to update
     --------------------------------------------------------------------------------
      @angular/core                      5.0.5 -> 6.0.0           ng update @angular/core
      @angular/material                  5.2.0 -> 6.0.0           ng update @angular/material
      rxjs                               5.5.2 -> 6.1.0           ng update rxjs

    There might be additional packages that are outdated.
    Or run ng update --all to try to update all at the same time.

Doing ng update --all isn't doing its job either:
ng update --all
                  Package "karma-jasmine-html-reporter" has a missing peer dependency of "jasmine" @ "^3.0.0".
                  Package "@angular/compiler-cli" has an incompatible peer dependency to "typescript" (requires ">=2.7.2 <2.8", would install "2.8.3")
                  Package "@auth0/angular-jwt" has an incompatible peer dependency to "@angular/common" (requires "^4.4.6||^5.0.0", would install "6.0.0")
                  Package "ng2-pdf-viewer" has a missing peer dependency of "pdfjs-dist" @ "2.0.489".
Invalid range: ">=6.0.0-rc.0"

I updated the cli first with ng update @angular/cli. Running ng update @angular/core after that gives me the error Invalid range: ">=4.3.0||>5.0.0".

So, the Invalid range: ... doesn't say much. It could at least state from which package.json (aka from which node module this is coming from)

I tried to run ng update @angular/core and my terminal shows this:
[[24;154R                                                                                Invalid range: ">=2.3.0 <3.0.0||>=4.0.0"

Same here. I tried to different version of Typescript (2.4, 2.6, 2.7, 2.8) and i get differents "Invalid range" error :

same for me, just did
npm install<EMAIL_ADDRESS>npm install<EMAIL_ADDRESS>...
for all @angular/... package and it was ok

@IterationCorp - this doesn't update your configuration files then, which means your karma, tslint and angular config won't get updated at all.

Same here,
$ ng update --all
                  Package "angular2-moment" has an incompatible peer dependency to "@angular/core" (requires ">=2.0.0 <6.0.0", would install "6.0.0")
                  Package "countup.js-angular2" has an incompatible peer dependency to "ts-node" (requires "~3.2.0", would install "6.0.2").
                  Package "bootstrap" has a missing peer dependency of "popper.js" @ "^1.14.3".
                  Package "ng2-dnd" has an incompatible peer dependency to "@angular/core" (requires "^4.0.0 || ^5.0.0", would install "6.0.0")
Invalid range: ">=4.0.1||>5.0.0||<=6.0.0"

try ng update --all --force but even ng update  seems still in beta step or out of scope

Same: Invalid range: ">=5.0.0"

Same here:   Invalid range  ">2.4.2"

I had the same issue. Upgraded my angular packages manually yarn add @angular/$PACKAGE, run ng update @angular/core again.

Workaround:

Update manually the angular packages to 6.0.0
ng update rxjs
ng update angular/core
ng update angular/material
if ng update installs typescript 2.8.3 you have to install typescript version 2.7.2. angular compiler doesn;t work with 2.8.3

This should have been checked before angular 6.0.0 was released. Now I have to downgrade everything.

I had to uninstall the following to make "ng update @angular/core" successful. The good ting is the "ng update @angular/core" automatically installs the latest compatible @ngrx.
npm uninstall @ngrx/db --save
npm uninstall @ngrx/core --save
npm uninstall @ngrx/effects --save
npm uninstall @ngrx/router-store --save
npm uninstall @ngrx/store --save
npm uninstall angularfire2 --save
npm uninstall @angular/flex-layout --save

My workaround:
remove @angular/compiler-cli from package.json
run ng update @angular/core
npm i --save-dev @angular/compiler-cli@latest
seems to work :D

I was experiencing the same problem reported by @markgoho-EDT, with some changes I was able to fix it, bellow you can see my steps, maybe it will help someone else.
The error message:
Package "@angular/compiler-cli" has an incompatible peer dependency to "typescript" (requires ">=2.7.2 <2.8", would install "2.6.2")
I was following along the steps from the https://update.angular.io page, but the above error poped when I was trying to run the ng update @angular/core bit.
What I have installed so far:

Angular CLI (local and global): 6.0.0
Typescript: 2.8.3

My steps:
$ ng update
  Name                               Version                  Command to update
 --------------------------------------------------------------------------------
  @angular/core                      5.2.10 -> 6.0.0          ng update @angular/core
  rxjs                               5.5.10 -> 6.1.0          ng update rxjs

There might be additional packages that are outdated.
Or run ng update --all to try to update all at the same time.

$ ng update --all
Package "karma-jasmine-html-reporter" has a missing peer dependency of "jasmine" @ "^3.0.0".
Package "@angular/platform-browser-dynamic" has a missing peer dependency of "@angular/compiler" @ "6.0.0".

$ ng update @angular/core
Package not installed: "@angular/compiler". Skipping.

$ ng update @angular/compiler
Package not installed: "@angular/compiler". Skipping.

$ npm install @angular/compiler -> the compiler was installed, but the version was 5.2.0
+<EMAIL_ADDRESS>removed 7 packages and updated 1 package in 11.763s

$ ng update core -> worked fine, no messages this time
Then, just to be sure, run $ ng update again, and got:
We analyzed your package.json and everything seems to be in order. Good work!

This is what I've done, worked for me, maybe will work for someone else. I think the key step was installing the @angular/compiler again, to force its update.
Note: I've just started this project, so no big changes for me, my dev env was almost pristine.

These steps haven't helped me clear the error, and when I try ng build --prod --base-href / i get the following:
92% chunk asset optimization UglifyJSPluginUnhandled rejection TypeError: Cannot read property 'sections' of null
    at new SourceMapConsumer (/Users/dev/Projects/ChiangsNinja/node_modules/uglifyjs-webpack-plugin/node_modules/source-map/lib/source-map-consumer.js:20:20)
    at UglifyJsPlugin.buildError (/Users/dev/Projects/ChiangsNinja/node_modules/uglifyjs-webpack-plugin/dist/index.js:116:23)
    at /Users/dev/Projects/ChiangsNinja/node_modules/uglifyjs-webpack-plugin/dist/index.js:275:45
    at Array.forEach (<anonymous>)
    at /Users/dev/Projects/ChiangsNinja/node_modules/uglifyjs-webpack-plugin/dist/index.js:259:19
    at step (/Users/dev/Projects/ChiangsNinja/node_modules/uglifyjs-webpack-plugin/dist/uglify/index.js:90:11)
    at done (/Users/dev/Projects/ChiangsNinja/node_modules/uglifyjs-webpack-plugin/dist/uglify/index.js:99:22)
    at tryCatcher (/Users/dev/Projects/ChiangsNinja/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/Users/dev/Projects/ChiangsNinja/node_modules/bluebird/js/release/promise.js:512:31)
    at Promise._settlePromise (/Users/dev/Projects/ChiangsNinja/node_modules/bluebird/js/release/promise.js:569:18)
    at Promise._settlePromise0 (/Users/dev/Projects/ChiangsNinja/node_modules/bluebird/js/release/promise.js:614:10)
    at Promise._settlePromises (/Users/dev/Projects/ChiangsNinja/node_modules/bluebird/js/release/promise.js:693:18)
    at Promise._fulfill (/Users/dev/Projects/ChiangsNinja/node_modules/bluebird/js/release/promise.js:638:18)
    at Promise._resolveCallback (/Users/dev/Projects/ChiangsNinja/node_modules/bluebird/js/release/promise.js:432:57)
    at Promise._settlePromiseFromHandler (/Users/dev/Projects/ChiangsNinja/node_modules/bluebird/js/release/promise.js:524:17)
    at Promise._settlePromise (/Users/dev/Projects/ChiangsNinja/node_modules/bluebird/js/release/promise.js:569:18)

I also had that issue: ng update @angular/core says "Invalid range: ">=2.1.0"
Things, that did not help so far:

updating everything manually to the latest version
updating rxjs manually
updating typescript to 2.7.2 and then to 2.8.3
trying to ng update --all
npm install<EMAIL_ADDRESS>until that point, ng -v showed my Angular version is 5.2. but...

What finally worked:

npm install<EMAIL_ADDRESS>

This is how I make it work.
My Environment:
Angular CLI Global : 6.0.0, Local: 1.7.4, Angular: 5.2

Note:  To enable ng Update you need to install Angular CLI 6.0 first
npm install -g @angular/cli or npm install @angular/cli

ng update  //update Angular Package core/common/complier... to 6.0.0

ng update @angular/cli    //change angular-cli.json to angular.json

optional if you have angular-material 5.4.2, ngx-translate 9.1.1, ng-bootstrap/ng-bootstrap 1.1.1:

ng update @angular/material  //upgrade to 6.0.1

npm install<EMAIL_ADDRESS>--save   //upgrade ngX translate to 10.0.1 for Angular 6

5 npm install --save<EMAIL_ADDRESS>//for ng-bootstrap
If you use Observable and get the error:
ERROR in node_modules/rxjs/Observable.d.ts(1,15): error TS2307: Cannot find module 'rxjs-compat/Observable'. node_modules/rxjs/observable/of.d.ts(1,15): error TS2307: Cannot find module 'rxjs-compat/observable/of'.
Change: import { Observable } from "rxjs/Observable"; import { of } from 'rxjs/observable/of';
To
import { Observable, of } from "rxjs";

I finally got mine to work by doing the following:
Step 1: Run ng ls --depth=1 to see if there is more than one version of webpack.
Step 2: If so, then npm uninstall webpack
Step 3: delete all of the other webpack- related folders in your node_modules directory. It is unnecessary to delete the entire node_modules directory.
Step 4: Run npm install @angular-devkit . @angular-devkit contains its own copy of webpack.
Step 5: Ensure that your webpack dependencies are met. You shouldn't see any errors in your console related to webpack not being installed.

@bluefire2121 Did you mean npm ls --depth=1 ?

I also got: Package "@angular/compiler-cli" has an incompatible peer dependency to "typescript" (requires ">=2.7.2 <2.8", would install "2.6.2")
I just fixed this by running npm install<EMAIL_ADDRESS>immediately after seeing the error.
I did subsequently get a heck of a lot of warnings and things that look like errors during the angualr/material update though it claimed to complete successfully.

In regards to the Invalid range: xxx errors, I've taken a quick peek at the @angular-devkit/schematics repo to see where the error was thrown and what was actually happening.
The error is thrown at https://github.com/angular/devkit/blob/master/packages/schematics/update/update/index.ts#L41
If I look at the surrounding function, seems that it's expecting semver versioned packages only, and no logical (by the lack of a better term?) versioning.
I would try to debug it further, but can't seem to locate the compiled files in my project to tinker with it.

@Bjeaurn yes 👍  Thank you. Updated.

It appears to be important to initially leave the local @angular/cli version at 1.7.4 (or whatever) and not 6.0.0. This is actually what the "npm install @angular/cli" in the update instructions does do, but  it gives a warning that the local one is at an older version, causing me to first try setting it at 6.0.0 like the global one before continuing, which lead to the range errors.  Starting over again from previous state pulled from version control,  I had luck by just ignoring that warning, and was able to get through the install as described at update.angular.io.

Thanks @scharris

Yeah, @scharris  and @manuelescamilla , that method causes this problem: https://github.com/angular/angular-cli/issues/10664

Downgrading to 2.7.2. breaks a lot of @angular imports with no apparent reason. Using 2.8.3, the imports work but the compiler fails and nothing is usable. Waiting for a fix, I don't know what to do. I already tried to uninstall the whole node_modules folder and start from scratch and the behaviour is the same. I tried verifying my package configuration through npm-check and everything is ok.

When i downgrade to typescript 2.7.2 and use angular/cli 6.0.0 then i have many errors with rxjs/Subscription and rxjs/Observable.
My rxjs version is 6.1.0

@bbuehrer, are you using the new import points for rxjs 6? They are changed (much simplified) so that could just be a legit compile error until imports are adjusted or the rxjs-compat package is added.

ok i added the rxjs-compat package and it worked

how can I find out if a new typescript version is compatible with angular/cli?

I installed typescript 2.7.2 as soon as I got that error, and then proceeded ok.
npm install<EMAIL_ADDRESS>

None of the mentioned solutions helped me because even though I had installed typescript 2.7.2, I had typescript ^2.8.3 in devDependecies. When I changed it to 2.7.2 everything worked correctly.

Am I the only one that is facing the imports issue downgrading to 2.7.2.? What am I doing wrong? I checked my node_modules, tyescript is 2.7.2 as expected, but none of the imports of classes of angular work anymore.
Anyway, should I expect a fix about this problem or it's gonna take a long time?

@isametal88 did you try to delete node_modules nad package-lock,json and run npm install again?

I had to manually add the 6.0.0 to all angular components and 2.7.2 to typescript. then it worked.

@lakerko Yes, I did.

@isametal88 is your global tsc taking over?
tsc -v

I wasn't able to run that command, I tried with this one (it seems to do a similar thing)
npm list -g typescript
[..]
+--<EMAIL_ADDRESS>| --<EMAIL_ADDRESS>|   --<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| --<EMAIL_ADDRESS>--<EMAIL_ADDRESS>--<EMAIL_ADDRESS>   --<EMAIL_ADDRESS>I doubled-check the typescript folder in node_modules and it is 2.7.2.

tsc -v
message TS6029: Version 1.5.3

That version is way too old. Explains why your imports etc aren’t working. Your situation seems unrelated to the reported issue.

Still getting these errors.  Manually upgraded to Angular 6 with RxJS at 6.1.0 and Typescript 2.7.2
node_modules/rxjs/Observable.d.ts(1,15): error TS2307: Cannot find module 'rxjs-compat/Observable'.
node_modules/rxjs/Subject.d.ts(1,15): error TS2307: Cannot find module 'rxjs-compat/Subject'.
node_modules/rxjs/Subscription.d.ts(1,15): error TS2307: Cannot find module 'rxjs-compat/Subscription'.

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

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.6.0
@angular-devkit/build-angular     0.6.0
@angular-devkit/build-optimizer   0.6.0
@angular-devkit/core              0.6.0
@angular-devkit/schematics        0.6.0
@angular/cdk                      6.0.1
@angular/flex-layout              6.0.0-beta.15
@angular/material                 6.0.1
@ngtools/webpack                  6.0.0
@schematics/angular               0.6.0
@schematics/update                0.6.0
rxjs                              6.1.0
typescript                        2.7.2
webpack                           4.6.0

same here what is the official recommended way forward here?
not giving much confidence in the hyped ng update.

Ran into the "Invalid range" error also, just trying to use ng update @angular/cli to update to 6.0.1, something I think should have been easy. Nope. Ended up doing an npm update to get 6.0.1, but still doing ng update @angular/core (because ng update said it needed to), I'm seeing
Invalid range: ">2.4.2"

No idea what is triggering this - it's pretty much a standard CLI app.

Similar issues here. I just started a new Angular 6.0.0 project from CLI 6.0.0 a week ago.
I could update angular-cli to version 6.0.1 but doing
ng update @angular/core shows me
Invalid range: ">=5.0.0"
I have<EMAIL_ADDRESS>and<EMAIL_ADDRESS>installed
Anybody facing the same issue trying to update angular/core from 6.0.0 -> 6.0.1 ?

@ray-kay
I had a clean install of 6.0.0.
When running ng update --all to try update to the 6.0.1, here is the error I have:
Package "karma-jasmine-html-reporter" has a missing peer dependency of "jasmine" @ ">=3".
Package "@angular/compiler-cli" has an incompatible peer dependency to "typescript" (requires ">=2.7.2 <2.8", would install "2.8.3").
Package "@angular/compiler-cli" has an incompatible peer dependency to "typescript" (requires ">=2.7.2 <2.8", would install "2.8.3")
Incompatible peer dependencies found. See above.

My package.json contains "typescript": "2.7.2" in devDependencies. That makes no sens to me.

@ddahan I had the same issue before I think.
Could solve by just update the locale angular cli on its own:
ng update @angular/cli
Hope this will help with your issue. After that try:
ng update @angular/core and it  should say:
Invalid range: ">=5.0.0"

I just run
npm update instead ng update and it updated Angular's packages to 6.0.1 without any issues.
Maybe an issue in the cli ng update dependency detection?

Except, for me anyway, when I initially updated to 6.0, the package.json items were set like
“@angular/common”: “6.0.0”
Locking it to that version. Npm update would not update anything.

Sorry for beeing so negative and off topic, but what's the point for Google to provide a new ng update command supposed to ease things if we need 58 comments in a an issue and 6 steps, to go from 6.0.0 to 6.0.1 in the end?
I gave up, I will update this later when tools will be less cumbersome to use.

The main problem seems to be with ng update --all not doing its job properly.
Following @Rumsha001 's approach seems to work well.
Just don't forget the @s:

ng update @angular/core
ng update @angular/material

I also needed to ng update @angular/cli

What I was doing:

Follow "Before updating guide" from https://update.angular.io/
Then set typescript package version to 2.7.2 (yarn upgrade<EMAIL_ADDRESS>yarn add global @angular/cli
ng update @angular/cli
yarn add @angular/cli
then continue following the guide
??????
profit

I tried following the steps @Rumsha001  laid out but was still having "Invalid range" failures at the ng update @angular/core step. Then I changed step 1 to use version '6.0.2' and finally things worked. No guarantees this was the magic touch though ... I tried many things tonight, in various orders, etc.
Overall, very frustrating, I've gotta say ...

I know this is "closed" with a "fix" in place, but trying to ng update to 6.0.2 produces the same "invalid range" error. ng update is more of a problem that it's solving at the moment.

same problem with 6.0.2 what is going on.
`WARNING in<EMAIL_ADDRESS>5354:15-36 Critical dependency: the request of a dependency is an expression
WARNING in<EMAIL_ADDRESS>5370:15-102 Critical dependency: the request of a dependency is an expression`

It certainly looks like ng update needs more work.
But people complaining here should have been around when Angular (2) was still in alpha. It was pretty hairy back then with breaking changes every couple of days sometimes.
That experience taught me it was worth sticking with Angular. It just gets better all the time. Sure a new feature like ng update might not work for everyone straight out of the box but I think we can all rest assured the engineers at Google will be working on it until they get it pretty well right.
Also remember updating from v5 to v6 is going to be a pretty huge task to accomplish with a single tool. After we have updated to v6, I'm sure the update process for future versions will be a whole lot better.

@chriscurnow well. for me to update the angular from 5 to 6 I only needed this thread, ng-update guide and one day)

I couldn't use ng update @angular/core to upgrade to 6.0.2. Then @angular/cli 6.0.3 has been released. After updating to @angular/cli 6.0.3 all ng update command worked well!

I'm also confused.
In my package.json I have "typescript": "^2.7.2".
When I run tsc -v I get 'tsc' is not recognized as an internal or external command, operable program or batch file, so it is not installed globally.
When I run ng -v I get
⋮
Angular CLI: 6.0.3
Node: 8.9.1
OS: win32 x64
Angular: 6.0.2
... animations, cdk, common, compiler, compiler-cli, core, forms
... http, material, platform-browser, platform-browser-dynamic
... platform-server, router
⋮
@angular-devkit/architect    0.6.3
@angular-devkit/core         0.6.3
@angular-devkit/schematics   0.6.3
@angular/cli                 6.0.3
@ngtools/webpack             6.0.3
@schematics/angular          0.6.3
@schematics/update           0.6.3
rxjs                         6.1.0
typescript                   2.8.3
webpack                      4.8.3
When I run webpack, I get ERROR in The Angular Compiler requires TypeScript >=2.7.2 and <2.8.0 but 2.8.3 was found instead.
Where is this 2.8.3 TypeScript version installed? I didn't install it, but it looks like Angluar CLI installed it, and now Angular Compiler breaks because it's installed, and I can't run webpack as a result...
How do I remove this 2.8.3 TypeScript version (that I didn't install), so I can webpack my project?

@tolvaly How do you "1. Manually update the angular packages to 6.0"?
I tried "ng update<EMAIL_ADDRESS>but (after waiting 10 minutes) I get the same error.

@tolvaly How do you "1. Manually update the angular packages to 6.0"?
I tried "ng update<EMAIL_ADDRESS>but (after waiting 10 minutes) I get the same error.

"Manually" means that you should update packages using "npm install" instead of "ng update", like this:
npm install<EMAIL_ADDRESS>--save
npm install<EMAIL_ADDRESS>--save
etc...

@alberthendriks
How do you "1. Manually update the angular packages to 6.0"?
I tried "ng update<EMAIL_ADDRESS>but (after waiting 10 minutes) I get the same error.

Meanwhile I found out why updating doesn't work with ng update. It's because of 3rd-party libraries witch depends on angular.
You have to find out witch of them is breaking your update, and you have to update them manually to the latest version witch support angular and rxjs 6. You have to analyse your package.json, check each dependency under "dependencies". This is also a good opportunity to throw out old libraries witch aren't  used or maintained anymore!
Couple of example libraries that broke my update were:

@ angular/flex-layout; Currently latest version: 6.0.0-beta.15
ng2-signalr;  Currently latest version: 6.0.0
@ ngx-translate/core;  Currently latest version: 10.0.2
ngx-moment; Currently latest version: 2.0.0

Until today all of them released a new version supporting angular6, and today I managed to update my packages to angular 6.0.5 running ng update @angular/cli without any issue. I was using angular/cli version 6.0.3
And responding to your question, under manual update I mean, you have to change the version numbers in package.json manually and run npm install to update the outdated packages.

As for many others - after upgrading to angular 6 package.json held fixed "6.0.0" version. Manually switching it to "^6.0.0" and executing npm install @angular/{core,forms,...,router} succesfully updates packages

Running below should help to update your dependencies to latest version.
npm i -g npm-check-updates
ncu -u
npm install

I had a typescript version missmatch like many people (requires ">=2.7.2 <2.8", would install "2.8.3").
My package.json contained typescript 2.7.2 but my package-lock.json contained typescript 2.9...
I remove this entry from package-lock.json and i run npm install<EMAIL_ADDRESS>I also needed to install angular-devkit/build-angular  as dev dependency npm install --save-dev @angular-devkit/build-angular
This solved my problem.

So far I stuck with this:
 npm list typescript
<EMAIL_ADDRESS>/www/liverecord/client
├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   └──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   └──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
Looks like<EMAIL_ADDRESS>screws everything.

I could have faced incompatible peer dependency issues when i ran the command ng update @angular/core to update the core library of the existing angular project.
Issues
Package "@angular/cdk" has an incompatible peer dependency to "@angular/common" (requires ">=5.0.0-rc.0 <6.0.0||>=4.0.0 <5.0.0", would install "6.0.0").
Package "codelyzer" has an incompatible peer dependency to "@angular/core" (requires ">=5.0.0-rc.0 <6.0.0||>=2.3.1 <3.0.0||>=4.0.0-beta <5.0.0", would install "6.0.0").
Package "codelyzer" has an incompatible peer dependency to "@angular/compiler" (requires ">=5.0.0-rc.0 <6.0.0||>=2.3.1 <3.0.0||>=4.0.0-beta <5.0.0", would install "6.0.0").
in second time i used the following command to update the core library
ng update --next but still there an issue.
issue had fix when i use the following command with --force flag,
ng update @angular/core --next --force
now, my project library has been updated from version 4 to 6. Well done :)
"dependencies": {
"@angular/animations": "^6.0.0",
"@angular/cdk": "^2.0.0-beta.8",
"@angular/common": "^6.0.0",
"@angular/compiler": "^6.0.0",
"@angular/core": "^6.0.0",
"@angular/forms": "^6.0.0",
"@angular/http": "^6.0.0",
"@angular/material": "^2.0.0-beta.8",
"@angular/platform-browser": "^6.0.0",
"@angular/platform-browser-dynamic": "^6.0.0",
"@angular/router": "^6.0.0",
"core-js": "^2.4.1",
"rxjs": "^6.2.0",
"zone.js": "^0.8.26",
"rxjs-compat": "^6.0.0-rc.0"
},
Good Luck !!!

I  have facing incompatible peer dependency issues when i ran the command ng update @angular/core to update the core library of the existing angular project.
Package "angulartics2" has an incompatible peer dependency to "@angular/router" (requires ">=7.0.0-rc.0 <8.0.0||>=4.4.0 <=6.0.0", would install "6.0.5").
Package "codelyzer" has an incompatible peer dependency to "@angular/compiler" (requires ">=5.0.0-rc.0 <6.0.0||>=2.3.1 <3.0.0||>=4.0.0-beta <5.0.0", would install "6.0.5").
can some one help on this

From the message it seems that both of those libraries are specifically disallowing the 6.x.x version range.
I'm not personally using these, but from what I can see:
For angulartics2 it looks like they moved to support Angular 6.x when they released version 6 of the package: https://github.com/angulartics/angulartics2/releases/tag/v6.0.0
For codelyzer it seems they should be supporting Angular 6.x starting with 4.2.1: https://github.com/mgechev/codelyzer/commit/3112b38607f56002106b9039619693193a134eac

I have the same issue with it.

ng update @angular/core

Package "ngx-bootstrap" has an incompatible peer dependency to "@angular/forms" (requires ">=7.0.0-rc.0 <8.0.0||6.0.1", would install "6.0.7").
Incompatible peer dependencies found. See above.
  I'm trying an ng update from 6.0.2 to 6.2.4, and I've chased through several missing packages that were apparently added in between those two versions.  I started with @angular-devkit/build-angular, but then also hit clean-css, compression and dom-converter.  I got stuck on the last two, because attempting to install either one states that the other one is missing.  ng update is a big fat fail for me.  There should be something to detect missing packages between versions, and install those as part of the ng update process.  Otherwise, it's faster to create a project from scratch and manually copy everything over.

npm install<EMAIL_ADDRESS>then ng update @angular/core worked for me
Good luck guys

For future reference. I got frustrated trying so many "solutions" with no avail so I decided to just run the following command.
$ ng update --all --force
It was a wild gamble and took a while to update but now everything is working and my project is up-to-date.

ng update --all --force worked for me also.
@kobusbeets I can't say it was a "wild gamble" though, not with a version control system.


@type {import('file').Type} not supported, while typescript says it is the official way

Search Terms
typescript import type
Problem
Currently typedoc errors for {import('file').Type} with:
[Error [TypeLexerSyntaxError]: Expected "!", "#", ".", ".<", "<", "=", "?", "[]", "|", "~", [ \t\r\n ], [a-zA-Z0-9_$] or end of input but "(" found.:
import('./index.js').CustomType
     ^]

while typescript offically says that it is the right way to import types
Typescript 4.8 Changelog Example Code
Suggested Solution
Implement import() capability

Tested on typedoc 0.23.13

That error isn't coming from TypeDoc - are you sure TypeDoc is using the version of TS you think it is? Try running with --version

That error isn't coming from TypeDoc - are you sure TypeDoc is using the version of TS you think it is? Try running with --version

TypeDoc 0.23.13
Using TypeScript 4.8.2 from ./node_modules/typescript/lib

Seems to be working correctly for me, I'll need a reproduction.
https://github.com/TypeStrong/typedoc-repros/runs/8169270507?check_suite_focus=true - run says failure but you can see by the logs that it did complete type checking and conversion.

Seems to be working correctly for me, I'll need a reproduction.

the project and branch are public at https://github.com/hasezoey/mongoose/tree/typedocRepro (not minimal though simple to show the changes / install)
instructions:

clone and enter the repository
run npm install
run npm run docs:generate observe the error

The file that has the type is lib/index.js (almost at the end of the file) and the import is in lib/schema.js (at the end of the file)

skipErrorChecking:true

I do not investigate projects which have this turned on as mentioned in the bug report template. The compiler api isn't consistent if errors are present and this option is off.

I do not investigate projects which have this turned on as mentioned in the bug report template. The compiler api isn't consistent if errors are present and this option is off.

sorry it seems i have ignored template comments out of habit, thanks for telling instead of just closing
thanks for pointing this out, though sadly i would not be able to use typedoc in that project without that option, because otherwise typescript would give out way too many errors (even with strict: false) and some of them would not even be fixable with the current conventions the projects has (or backwards breaking)
also, vscode uses the same typescript but does not error and the types still work, is there anything i can do in typedoc to do the same?

Looked slightly more closely at what you're doing and... it doesn't make sense to me. Mongoose defines its types in types/index.d.ts, so you should be running on that instead of on the source code in lib. I checked out master, made the following changes, and ran npx typedoc types/index.d.ts --out docs2, which gave me output.
diff --git a/package.json b/package.json
index 391c2e7..3f998d4 100644
--- a/package.json
+++ b/package.json
@@ -62,6 +62,7 @@
     "stream-browserify": "3.0.0",
     "ts-benchmark": "^1.1.10",
     "tsd": "0.20.0",
+    "typedoc": "^0.23.14",
     "typescript": "4.7.4",
     "uuid": "8.3.2",
     "webpack": "5.74.0"
diff --git a/tsconfig.json b/tsconfig.json
index 10f087f..47c3481 100644
--- a/tsconfig.json
+++ b/tsconfig.json
@@ -5,5 +5,6 @@
     "paths": {
       "mongoose" : ["./types/index.d.ts"]
     }
-  }
+  },
+  "exclude": ["test"]
 }

Looked slightly more closely at what you're doing and... it doesn't make sense to me. Mongoose defines its types in types/index.d.ts,

that is correct, though i was looking for a replacement for dox and though i could use typedoc (especially because it would allow referencing types from other files1) while the code is still in only-js form. i was looking for a replacement because other jsdoc parsers seem to not be updated anymore and are outdated (dependency wise) and the only "similar" package i could think of was typedoc, so i wanted to try that
see:

website.js (the script that starts generating the static files for the documentation and calls api.js)
api.js (the script that generates documentation based on the source-code)

note: i was not using typedoc's built-in html-generation, because i wanted to keep the style the same as before (only replace which package looked through the code)
1: we currently also use intellisense to make the js code easier to use (inside the package itself while developing), and typedoc (being reliant on typescript) would bring it in line with what intellisense would be capable of while also having the documentation work (like not ignoring typedef and being able to use stuff like import)

diff --git a/tsconfig.json b/tsconfig.json
index 10f087f..d6835eb 100644
--- a/tsconfig.json
+++ b/tsconfig.json
@@ -2,8 +2,10 @@
   "compilerOptions": {
     "strict": true,
     "strictNullChecks": true,
+    "allowJs": true,
     "paths": {
       "mongoose" : ["./types/index.d.ts"]
     }
-  }
+  },
+  "include": ["lib"]
 }

I made the following changes, which let npx tsc --project tsconfig.json --noEmit compile without errors. With these changes, npx typedoc --tsconfig tsconfig.json --json out.json worked as expected.
If npx tsc --noEmit exits with no errors, TypeDoc should also be able to parse as expected.


platform.is('ios') return false in ios simulator?

Ionic version:  (check one with "x")
[ ] 1.x (For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[x ] 3.x
I'm submitting a ...  (check one with "x")
[ ] bug report
[ x] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
platform.is('ios') return false in ios simulator
Related code:
this.platform.is('ios')

Hello! Thanks for using Ionic. Does this only happen on the simulator or on an actual device too? Also, is it using the iOS styles or the material design styles on the app running on the sim?

@jgw96  I used iOS styles and only happen on the simulator

Hello @longdw , are you loading cordova in your app? Do you see any warnings in the console about cordova taking to long to init?

@jgw96  It's my fault, I init the platform with new Platform(), when I init it in construstor(private platform Platform), it comes ok. thank you.

I would like to ask Ionic Team on why new-ing up platform doesn't work and only works when injected?


Figure out why guardian picks the wrong permissions model (does not detect subclasses of User/GroupObjectPermissionAbstract)

The assign_perm utility from guardian.utils assigns permissions in the generic guardian permissions model, instead of using our custom permission models.
The guardian class detection thing appears to fail around here https://github.com/django-guardian/django-guardian/blob/4784cfa91516944dfa113f56399c1b4c59a780c5/guardian/utils.py#L207 where is_generic() detects the object_id field and falls back to using guardians generic permissions model.
Create a minimal reproducer and open an issue in django-guardian

This was not a guardian issue after all, it was caused by using the wrong base model for our non-generic real-fk permission models. We used UserObjectPermissionAbstract when we should have used UserObjectPermissionBase


Parse Json Logs?

Hey folks,
I have a nodejs backend producing json logs with pino. But when I check the logs in grafana using the loki datasource, the json is split on multiple lines.
Tried a lot of different combinations of the json stage, but could make it work:
This is my last attempt
stage.json {          expressions = {           output="log"}       }
When I check the pod logs, I see this json, and I wanted the req piece to be whole on the grafana entry
req: {
      "id": 503,
      "method": "GET",
      "url": "/api/v3/home-feed?currentDateTime=06-09-2024-13&includeVideos=1&limit=35&teamId=CAN&trendingLimit=3",
      "query": {
        "currentDateTime": "06-09-2024-13",
        "includeVideos": "1",
        "limit": "35",
        "teamId": "CAN",
        "trendingLimit": "3"
      },
      "params": {},
      "headers": {
        "x-forwarded-for": "<IP_ADDRESS>",
        "x-forwarded-proto": "https",
        "x-forwarded-port": "443",
        "host": "api.mysite.com",
        "devicetype": "ios",
        "buildnumber": "3.02",
        "teamid": "CAN",
        "accept": "*/*",
        "authsource": "ios",
        "accept-language": "en-US;q=1.0",
        "includevideos": "true",

      "remoteAddress": "::ffff:<IP_ADDRESS>",
      "remotePort": 36070
    }

@tcborg can you provide a complete raw log line from the pod logs?

@bentonam
This is pretty much it
[11-06-2024 02:57:50] INFO (1): request completed
    req: {
      "id": 19256,
      "method": "GET",
      "url": "/api/v3/feed-by-id?contentType=video&currentDateTime=06-10-2024-22&feedId=zO3KRoos",
      "query": {
        "contentType": "video",
        "currentDateTime": "06-10-2024-22",
        "feedId": "zO3KRoos"
      },
      "params": {},
      "headers": {
        "x-forwarded-for": "<IP_ADDRESS>",
        "x-forwarded-proto": "https",
        "x-forwarded-port": "443",
        "host": "api.mysite.com",
        "x-amzn-trace-id": "Root=1-6667bd2e-53f0a50e72c3454803129de6",
        "devicetype": "ios",
        "buildnumber": "3.02",
        "authorization": "[Redacted]",
        "accept": "*/*",
        "authsource": "ios",
        "userid": "HpqsEKs2uvV7RFt395zpJHCTqH62",
        "contenttype": "video",
        "accept-language": "en-US;q=1.0",
        "accept-encoding": "br;q=1.0, gzip;q=0.9, deflate;q=0.8",
        "anonymoususerid": "e2b4rBuiVUauna6mURDPqT",
        "user-agent": "iOS",
        "feedid": "zO3KRoos",
        "cookie": "_tracking_consent=%7B%22v%22%3A%222.1%22%2C%22reg%22%3A%22CCPA%22%2C%22con%22%3A%7B%22CMP%22%3A%7B%22m%22%3A%220%22%2C%22s%22%3A%22%22%2C%22p%22%3A%220%22%2C%22a%22%3A%220%22%7D%7D%2C%22region%22%3A%22USVA%22%7D"
      },
      "remoteAddress": "::ffff:<IP_ADDRESS>",
      "remotePort": 63618
    }
    res: {
      "statusCode": 200,
      "headers": {
        "x-powered-by": "Express",
        "access-control-allow-origin": "*",
        "content-type": "application/json; charset=utf-8",
        "content-length": "1541",
        "etag": "W/\"605-4irVFR88+TK3HnJKbrREhgDSyLU\"",
        "cache-control": "max-age=300"
      }
    }
    responseTime: 6

@tcborg I'm not that familiar with pino, but according to their documentation https://github.com/pinojs/pino/blob/main/docs/pretty.md pino uses NDJSON (new-line delimited JSON).  You posted what I believe to be pretty-json, which spans multiple new lines.   Typically new lines should be avoided in production logs if at all possible.  As it leads to unnecessarily complex log parsing.  However Alloy/Promtail supports multiline, you have to provide a firstline selector.
If my understanding is correct you want to:

Only have the json body written to the loki
There is still other useful information written to the log i.e. timestamp, level,  message, responseTime
The timestamp of the log is reset to the extracted value instead of the collection time
level is used as a label
message and responseTime values are extracted and set as structured metadata, this way they are still part of the log but not part of the log line and are not good candidates
The log line is reset to be just the req json with all new lines removed.

Here is an example promtail configuration file, the reason I'm using promtail is you can read from stdin:
Promtail Config:
---
clients:
  - url: https://loki.example.com/loki/api/v1/push
    basic_auth:
      username: test
      password: test

scrape_configs:
  - job_name: pino
    static_configs:
      - targets:
          - localhost
        labels:
          __path__: pino.log
    pipeline_stages:
      # strip ascii color codes
      - decolorize:
      # RE2 regular expression, if matched will start a new multiline block.
      - multiline:
          firstline: '^\[\d{2}-\d{2}-\d{4} \d{2}:\d{2}:\d{2}\]\s+\w+(?: \(\d+\))?:'
          max_wait_time: 3s
      # assign a default log-level of unknown
      - static_labels:
          level: unknown
      # extract the timestamp, level, req and responseTime
      - regex:
          expression: '\[(?P<timestamp>\d{2}-\d{2}-\d{4} \d{2}:\d{2}:\d{2})\] (?P<level>\w+)(?: \(\d+\))?:\s+(?P<message>(?:\n|.)+)req:\n*\s*(?P<json_log>(?:.|\n)+)\n*\s*(?P<responseTime>responseTime:\s+\d+)\n*$'
      # set the extracted level to be a label
      - labels:
          level:
      # set the message and responseTime as structured metadata
      - structured_metadata:
          message:
          responseTime:
      # set the metadata timestamp to be that of the extracted timestamp from the log line
      - timestamp:
          source: timestamp
          format: "02-01-2006 15:04:05"
      # remove all new lines and whitespace from the req
      - replace:
          expression: '(\n\s+)'
          source: json_log
          replace: ''
      # reset the log line to be that of just the json object
      - output:
          source: json_log

Command:
cat pino.log | promtail -stdin -config.expand-env -config.file promtail.yaml -dry-run

Output:

Example Input:
[11-06-2024 02:57:50] INFO (1): request completed
    req: {
      "id": 19256,
      "method": "GET",
      "url": "/api/v3/feed-by-id?contentType=video&currentDateTime=06-10-2024-22&feedId=zO3KRoos",
      "query": {
        "contentType": "video",
        "currentDateTime": "06-10-2024-22",
        "feedId": "zO3KRoos"
      },
      "params": {},
      "headers": {
        "x-forwarded-for": "<IP_ADDRESS>",
        "x-forwarded-proto": "https",
        "x-forwarded-port": "443",
        "host": "api.mysite.com",
        "x-amzn-trace-id": "Root=1-6667bd2e-53f0a50e72c3454803129de6",
        "devicetype": "ios",
        "buildnumber": "3.02",
        "authorization": "[Redacted]",
        "accept": "*/*",
        "authsource": "ios",
        "userid": "HpqsEKs2uvV7RFt395zpJHCTqH62",
        "contenttype": "video",
        "accept-language": "en-US;q=1.0",
        "accept-encoding": "br;q=1.0, gzip;q=0.9, deflate;q=0.8",
        "anonymoususerid": "e2b4rBuiVUauna6mURDPqT",
        "user-agent": "iOS",
        "feedid": "zO3KRoos",
        "cookie": "<redacted>"
      },
      "remoteAddress": "::ffff:<IP_ADDRESS>",
      "remotePort": 63618
    }
    res: {
      "statusCode": 200,
      "headers": {
        "x-powered-by": "Express",
        "access-control-allow-origin": "*",
        "content-type": "application/json; charset=utf-8",
        "content-length": "1541",
        "etag": "W/\"605-4irVFR88+TK3HnJKbrREhgDSyLU\"",
        "cache-control": "max-age=300"
      }
    }
    responseTime: 6

Example Promtail Output
{"id": 19256,"method": "GET","url": "/api/v3/feed-by-id?contentType=video&currentDateTime=06-10-2024-22&feedId=zO3KRoos","query": {"contentType": "video","currentDateTime": "06-10-2024-22","feedId": "zO3KRoos"},"params": {},"headers": {"x-forwarded-for": "<IP_ADDRESS>","x-forwarded-proto": "https","x-forwarded-port": "443","host": "api.mysite.com","x-amzn-trace-id": "Root=1-6667bd2e-53f0a50e72c3454803129de6","devicetype": "ios","buildnumber": "3.02","authorization": "[Redacted]","accept": "*/*","authsource": "ios","userid": "HpqsEKs2uvV7RFt395zpJHCTqH62","contenttype": "video","accept-language": "en-US;q=1.0","accept-encoding": "br;q=1.0, gzip;q=0.9, deflate;q=0.8","anonymoususerid": "e2b4rBuiVUauna6mURDPqT","user-agent": "iOS","feedid": "zO3KRoos","cookie": "<redacted>"},"remoteAddress": "::ffff:<IP_ADDRESS>","remotePort": 63618}res: {"statusCode": 200,"headers": {"x-powered-by": "Express","access-control-allow-origin": "*","content-type": "application/json; charset=utf-8","content-length": "1541","etag": "W/\"605-4irVFR88+TK3HnJKbrREhgDSyLU\"","cache-control": "max-age=300"}}

As you can see this works when accounting for multiline log messages.  Now promtail will not help you with the k8s-monitoring helm chart as it is not supported, Alloy is used.  Alloy provides a conversion command, if we convert the promtail file to alloy, the steps needed will be provided for you.
Alloy Convert:
alloy convert --output pino.alloy --source-format promtail promtail.yaml

local.file_match "pino" {
	path_targets = [{
		__address__ = "localhost",
		__path__    = "pino.log",
	}]
}

loki.process "pino" {
	forward_to = [loki.write.default.receiver]

	stage.decolorize { }

	stage.multiline {
		firstline = "^\\[\\d{2}-\\d{2}-\\d{4} \\d{2}:\\d{2}:\\d{2}\\]\\s+\\w+(?: \\(\\d+\\))?:"
		max_lines = 0
	}

	stage.static_labels {
		values = {
			level = "unknown",
		}
	}

	stage.regex {
		expression = "\\[(?P<timestamp>\\d{2}-\\d{2}-\\d{4} \\d{2}:\\d{2}:\\d{2})\\] (?P<level>\\w+)(?: \\(\\d+\\))?:\\s+(?P<message>(?:\\n|.)+)req:\\n*\\s*(?P<json_log>(?:.|\\n)+)\\n*\\s*(?P<responseTime>responseTime:\\s+\\d+)\\n*$"
	}

	stage.labels {
		values = {
			level = null,
		}
	}

	stage.structured_metadata {
		values = {
			message      = null,
			responseTime = null,
		}
	}

	stage.timestamp {
		source = "timestamp"
		format = "02-01-2006 15:04:05"
	}

	stage.replace {
		expression = "(\\n\\s+)"
		source     = "json_log"
	}

	stage.output {
		source = "json_log"
	}
}

loki.source.file "pino" {
	targets               = local.file_match.pino.targets
	forward_to            = [loki.process.pino.receiver]
	legacy_positions_file = "/var/log/positions.yaml"
}

loki.write "default" {
	endpoint {
		url = "https://loki.example.com/loki/api/v1/push"

		basic_auth {
			username = "test"
			password = "test"
		}
	}
	external_labels = {}
}

I hope this is helpful for you and helps to solve your issues.
Download Files: pino-example.zip

This has been answered, so closing.


Pragmatically add metadata within cucumber?

Using cucumber 4 (seems no reason why that wouldnt work like 3?), so I have a post cucumber script to translate json to html.
I'm a bit stuck trying to get my environment variables (browser name, app version etc.) into the cucumber json file DURING cucumber execution.
I don't think cucumber offers an attach, or any way to just fiddle yourself with the testcase to get the metadata in the json?
Do I have to create my own formatter - forked from the json formatter?
An example, documentation or formatter would really help me.

Hi @lenntt
I'm not working with plain CucumberJS, so I don't know how to do that. If you figured it out I'd really like to know and if you want you can add a PR to update the docs.
I'm going to close it for now because this isn't a question / issue related to this module. It's still open for discussion.


When maximising a window, the accent colour is shown for a few frames

Explain the bug
When a window is maximised, the new area is shown in the user's accent colour for a few frames.
To reproduce

Drag a window to the top or press the maximise button
100% reproducible

Expected behavior
The window to immediately resize or use the themed colour so as not to flash.
Screenshots
https://user-images.githubusercontent.com/13716824/116496832-d4e45e00-a89d-11eb-8e9e-b51aca8198eb.mp4
System Information

OS Version:
Device name	DESKTOP-ECO40Q0
Processor	AMD Ryzen 5 1600X Six-Core Processor              3.60 GHz
Installed RAM	16.0 GB
Device ID	BB110B17-97DB-4DCD-A197-CE7E1F37C395
Product ID	00330-80000-00000-AA101
System type	64-bit operating system, x64-based processor
Pen and touch	No pen or touch input is available for this display

App version: <IP_ADDRESS>

This appears to be a framework bug with CoreWindow, can you open an issue for this  in the Feedback Hub as it's not specific to Files?

Would there be any way to change it to use the background colour, not the accent?

Unfortunately changing the background isn't something that's supported.


Update docs for multiple entry points

Aligns the documentation for multiple entry points with the changes introduced in 0.31.0 (https://github.com/denoland/dnt/pull/221).

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


Develop

@cmaneu , I don't understand the problem you mentioned the other day on conflict and erasing github history... What are the commit in origin/master that would not be in origin/develop ?
++

@bertrandlalo There are multiple files in master that are not in develop, including:

azure-static-web-apps-zealous-glacier-020fd5403.yml in .github/workflows
the api folder

I've double checked, and there is indeed a common commit between develop and master. So, I'll go ahead and merge this PR.
If it's a complete mess, I'll revert the merge commit :)


Add SOAP to REST editing capability and chunking

Fixed with https://github.com/wso2/carbon-apimgt/pull/7818


micro:bit Windows 10 App - Serial connection unreliable

Haven't found an explicit way to reproduce this one, but when testing a simple application like the one below, which sends serial data when a button is pressed, I am not always able to trigger the "Show Data Device" option to appear (or it appears and disappears quickly):

https://makecode.microbit.org/_ULC19tiaH2WJ

It also looks like sometimes the application loses the serial connection and is unable to reconnect.
If I disconnect the micro:bit, close MakeCode, connect the micro:bit and then open MakeCode then is all back to normal. Most of the time is enough to close MakeCode and open it again and it works again.
I am more likely to encounter this problem if I do the following (although it doesn't always happen):

Open Makecode
Press the button a couple of times for the serial button to appear
Go to the "Show Data  Device" view
Press the button a bunch of time, see the "hello world" message counter go up
Stop pressing the button, maybe even switch to a different app for a few seconds
Press the button again, nothing happens
Go to the blocks/code view and the "Show Data Device" button doesn't appear anymore
In extreme occasions the app might even crash and close

At this point I can open any other serial terminal program (like tera term or putty), connect to the micro:bit com port, and the button does send the serial messages without any issues.

I would like to request that the serial workflow in the app is twofold. While I really like the option of clicking the simulator button and getting a visual of the data I also like the immediacy of seeing the terminal window displayed on the main page such as previous versions.

Perhaps on the main page you can have the small terminal with an additional show simulator button placed alongside.
Also I still wish there was a way for you all to reinstate the stream to cloud function. It seams like while I know there were issues using it with the chrome extension, running it in the windows app should work.

@machinehistories would you kindly create a new issue to track this feature request? I will use this issue to track the serial connection issues
@microbit-carlos we are about to check in a fix that should increase stability of the serial connection. However, please note that the data from the device is only sent to the editor when enough content has been received.
In your example, that means it will take multiple button presses before the "Show data Device" button shows up. It's also why sometimes it appears as though a button press is not incrementing the console counter - you'll need to click it multiple times before the buffer fills up and gets dumped into the editor, which can then process the info accordingly. @pelikhan @cait1inhennessy maybe we could improve that area? I.e. periodically dump the buffer even if it's not full?
Also, out of curiosity, does unplugging / replugging the device not fix any serial issues you're having? Do you really need to fully close the app and relaunch it before things go back to normal?

Now that 994aed5938341a0e9d372055d3588ede4c17913a has been merged, our next micro:bit release should see increased reliability for the HID and serial connections in the Windows app.
However, as I noted above, due to the way our editor pulls data from the device, multiple button presses will still be required in your example for the messages to show up in the data view.


Shoot under player

When my player model crouch, my bullet has drawing under me.
But it visual. In GOTV demo all good.

Same here.

Same here.
Most probably, same issue here: danielkrupinski/Osiris#3271

Im sure, what is the same!


Update to CircuitState Annotations

I will be reworking in the next couple of days how CircuitState Annotations will be passed.
Currently, the API is to only return the new annotations. This is extremely confusing, because a transformation that does nothing would naturally pass the input CircuitState without modifying it.
This causes all annotations to be duplicated, because we assume all the annotations contained in CircuitState are new, and add them to the existing annotations we saved before calling the transform.
The new proposal is to assume that the annotations that get passed by a transform are all of the annotations. If an annotation is not passed on, it is assumed to be deleted.
I will add a deleted field to all annotations, and this will be marked if a transform failed to pass it along. This should enable passes to error if they see their annotation get deleted (and they weren't expecting it to be).
This is just a PSA for people who are writing transforms, including @shunshou, @colinschmidt, @donggyukim, @jackkoenig, @chick.
I will try to update all transforms that I know about to the new API.

Fixed by #464


[Definition Request]: Olympus Dao

Context
A follower on Twitter recommended adding Olympus Dao to the knowledge base
Term
olympus dao
Definition
TBD
List of category options
DAO (i.e. Developer Dao, Friends with Benefits, etc...)
Additional Information
No response

They probably describe it best themselves: https://docs.olympusdao.finance/main/
More info here: https://www.coingecko.com/buzz/what-is-olympusdao-and-how-does-it-work

original protocol that is forked a looot (unofficial site: https://ohmforks.com/)

@JordyPouw did you want to have a go at this issue 👀 ?  It's totally fine to say no too, it's all good

I don't think I'm the best person to write out a clear definition for this. I'll keep it open for others to write, hopefully those links give them a good start.

I don't think I'm the best person to write out a clear definition for this. I'll keep it open for others to write, hopefully those links give them a good start.

Yeah no problem man, thank you for the links!


#9 "fix" broke kv_a

When I run the kvec example in the header:
kvec_t(int) array;
kv_init(array);
kv_push(int, array, 10); // append
kv_a(int, array, 20) = 5; // dynamic
kv_destroy(array);

The line on kv_a gives me error: lvalue required as left operand of assignment. However, when I revert the change done in issue #9, removing one level of parens, it works perfectly.

Yes this is still broken on gcc.


Consider using a faster inmemory store for the indexes

Currently the DashMap implementation works fine, but I guess the dataset could grow a lot.
Investigate using https://github.com/salsa-rs/salsa (thank you Pascal)

Closing as premature optimization, I think the map is fine until someone reports an issue proving it's not.


Cannot install from git url in v1.1.8

why not just store them on githun or gitlab?

@egoist

Self-hosted GitLab repo.
An app with multiple templates, like Razzle.


new ground_segmentation filter

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I've agreed with the maintainers that I can plan this task.

Description
There are many ground points in the output of the current ground filter. I have tried the algorithm accepted by RA-L with IROS'22 option named "TRAVEL: Traversable Ground and Above-Ground Object Segmentation using Graph Representation for 3D LiDAR Scans". The proposed algorithm is sensible and works better in accuracy and processing time than the scan_ground_filter. Due to the fact that this project is licensed with GPL-3.0, I am rewriting the code, making it more performant, and also adapting to Autoware stack by adding pointcloud_preprocessor, etc.
There is an comparison video of two algorithms :
https://youtu.be/VkzRjY9xLdk
Purpose
To give more precise output by the obstacle_segmentation/ground_filter with lowering the processing_time_ms.
Possible approaches
Adding the travel_ground_filter among the other filters as an option
Definition of done

Rewriting the code to license it with Apache-2.0
Adapt to Autoware stack and add some features like pointcloud_preprocessor
Adjust the launch files by including the new method

Looks grate! I'm actually implementing patchwork++ and I want to update it combining with TRAVEL. Therefore if you get any progress let's discuss about it!
https://github.com/ktro2828/autoware.universe/tree/feat/patchworkpp

Thanks for your interest, excellent work!
I actually progressed quite much, I have written the implementation in the format of current ground filters, so I am working under the ground segmentation package rather than a distinct package because I am planning it to be an optional ground filter.
https://github.com/yusufy1ld1z/autoware.universe/tree/travel_ground_filter/perception/ground_segmentation
I will not be able to work on this project next week. I am waiting for your thoughts and future improvements with curiosity. After that, we can work together!

Hello again, apologies for a long break. I have not changed anything since the last update because I thought I already finished the project when I opened this issue. I think @ktro2828 has done a well job but I could not find the package of him after the last updates in the Autoware. If you still interested in my job I am ready to make updates you desire. Initially I adopted my project as an option to ground filters already in the perception ground segmentation stack and I am still agree with that. What are your further thoughts about the project, I am looking forward to open a PR !

@ktro2828 Do you have any idea about this?


LCD backlight controller

Related: https://github.com/lvgl/lvgl_esp32_drivers/pull/74
Changes in this PR:

enable brightness control from menuconfig
carve-out backlight control from TFT drivers
support for multiple displays
support for (future) runtime configuration

TODOs:

[x] Carve out backlight control
[x] Adapt existing display drivers
[x] Update Kconfig
[x] Compile with all existing drivers
[x] Compile with IDF v 4.2 and below

Thanks :)

LGTM, can we add something about this in the README?

can we add something about this in the README?

Sure, will do

@C47D Readme updated.
Give me a thumb up and I'll merge it.
(I'd like to have me first merge as 'Collaborator', lol)

It's all yours @tore-espressif , great job! 🥳


feat: TCP redirect mode

Add back TCP redirection mode because some users don't know how to use TPROXY and/or don't have a kernel with TPROXY support. Code is ported from Hysteria 1 with minor changes.
Example:
iptables -t nat -A OUTPUT -p tcp -d <IP_ADDRESS> -j REDIRECT --to-ports 3500
Closes https://github.com/apernet/hysteria/issues/659
Note to self: requires doc changes.

I am so grateful for your quick and helpful response， so impressed, and so thankful, for your generosity in sharing your work with us.


chore: prepare v0.2

https://github.com/keymanapp/shared-sites/blob/67ecd659838b4b3c5039659f6106a68b91c2c777/_common/KeymanSentry.php#L11
Do we want this to become .localhost?

Do we want this to become .localhost?

Yep, but let's work on that kind of thing as a separate PR to avoid conflating the changes.


Branch 2

Current dependencies on/for this PR:

main

PR #3

PR #4   👈

This comment was auto-generated by Graphite.


Add legacy govspeak class alongside gem govspeak

What

Adds the govspeak class alongside the gem-c-govspeak class - this makes sure that the govspeak has the same output as gem-c-govspeak for minimal additional CSS.
Why

There are many many many places where the older govspeak class is used on elements that wrap around content, rather than gem-c-govspeak. This class comes as part of the content from the content store (eg in details.body in the cabinet office content.
Adding the legacy class as a fix is easier and safer that changing the myriad of places where this is added - around 7K places across alphagov).
This is not the ideal fix - that would be to change Whitehall et al to output <div class="gem-c-govspeak"> -  this will do for now, and will help ensure that there are no unstyled elements whilst this change occurs.
Visual Changes

None.

Whilst I appreciate the comment "Legacy class name" it doesn't describe to me why it needs to be there. Could we expand on that in the comment, mentioning that it's sometimes contained in content items?

Good point - I've added a (hopefully) better comment explaining why it's unfortunately needed.


Use "not in" operator

https://github.com/InformaticsGenomicMedicine/DraftCoreDataModel/blob/79450932a44ee677816f9c02e6f5660ea03e5ec1/src/core_variant.py#L94C6-L94C6
Please change if not value in set to if value not in set. The first will work, but it is more pythonic to use the not in operator as documented here.  Please change the linked conditional statement and then search the code for any others that need to be updated as well.

Changed syntax to "if value not in ..". Not going to highlight ever change but these changes were made in core_variant.py module that is currently in the issue-dev-sb branch.

Reviewed with @rrfreimuth.


Replace deprecated set-output command

As described in #38 , the set-output command used in the main.yml workflow file, and in the index.js action is being deprecated. This PR addresses both of those issues, and we are successfully using the updated version from my fork in our project, and the warnings about the deprecated command are gone.
Resolves #38.

@jfkriz Thanks for the contribution!


FINERACT-1913-Initializing-db-connection-pool-at-startup

Description
Changes to initialize database connection pool at startup for tenants.
Describe the changes made and why they were made.
Ignore if these details are present on the associated Apache Fineract JIRA ticket.
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!

[ ] Write the commit message as per https://github.com/apache/fineract/#pull-requests

[ ] Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.

[ ] Create/update unit or integration tests for verifying the changes made.

[ ] Follow coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions.

[ ] Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes

[ ] Submission is not a "code dump".  (Large changes can be made "in repository" via a branch.  Ask on the developer mailing list for guidance, if required.)

FYI our guidelines for code reviews are at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide.

@ruchiD it is failing on spotbugs check


problem in handling empty dataframes

I'm loading and preprocessing a legitimate dataframe, using a long function, with calls to pymongo and mysql (will try spending the time to make a minimal example if issue is unclear).
I have this line:
df2 = pd.concat([v for v in some_cache_df.values()]) if some_cache_df else pd.DataFrame()
It raises an IndexError in line 45 of /dovpanda/core.py, where there's a call to cols = {df.shape[1] for df in objs}

closed

could not reproduce.
whaat pandas version?
is some_cache_df.values() a pymongo object?

No, is is a dict of dataframes.


Feature Request: Allow the change of volume data values alone without recomputing mesh data

When committing a volume, OSPRay does some calculations which can be quite expensive. I am assuming these are related to acceleration structures pertaining to the mesh. We have a common use case of changing the data values of a mesh without changing the mesh itself. Committing the volume after making this change results in rerunning the expensive calculations. Is there any way this can be avoided?

Note this issue may be particularly relevant for unstructured grids. As a specific use case it takes about 2 minutes for the first rendering of a ~150M tetrahedra cell mesh on a 18-core 2.3-GHz Intel Xeon 6140 (Skylake) processor. But subsequent renderings are on the order of a second. Presumably the initial cost is for computing acceleration structures that may only need to change when a new mesh is loaded?

Understood, this is a very reasonable request, we like to have that as well (already on the wish list) :-). We started on the infrastructure to facilitate such more fine-granular, smarter updates. However, still some pieces missing, so will take some time.


Blackhole route for service CIDR can prevent host from accessing service cluster IPs

Expected Behavior
A host-networked pod, or some other process running directly on a Kubernetes host, should be able to connect to a Kubernetes service using that service's cluster IP.
Current Behavior
Connection to the service cluster IP fails.
(But please note, this is only from the host; connection from normal pods is fine.)
Explanation
In https://github.com/projectcalico/confd/pull/322, we recently arranged to program a blackhole route into the Linux kernel routing table, for the Kubernetes service CIDR.  The motivation for this was to break accidental routing loops, when we are also advertising service IPs to the Calico nodes' default gateway.
Unfortunately we think this blackhole route may prevent connection to a service IP from the host.  For example, this arose in the older issue at #2457 , when a similar blackhole route was being programmed by accident.  #2457 was focussed on suppressing the blackhole route and does not describe the detailed cause of the connection problem, but we think it is to do with Linux source IP selection.  Linux needs to choose a source IP for the connection from the host, and to do that it looks up the destination IP - which is the cluster IP - in the routing table.  The routing table says "blackhole", so the connection fails at that point.  (If Linux source IP selection happened after the service IP DNAT, there would be no problem, but unfortunately it happens earlier than that.)
Net, we need to revisit this, confirm the detailed explanation for why host connections fail, and update the kernel programming so as to prevent routing loops while still allowing a host to connect to a service IP.

Fixed here: https://github.com/projectcalico/calico/pull/3755

@caseydavenport The linked pull request seems to be unrelated to this issue. Does that fix apply to this issue?

perhaps, he meant this https://github.com/projectcalico/confd/pull/337 which reverted the original confd change. v3.15.1 releasenotes mentions the reverted fix.

Uhh, yeah I'm not sure why I linked that! Must have grabbed the wrong tab.
The fix was indeed the revert that @ravilr linked to.


Camel 16099: throttler EIP - throttle on concurrent requests

Updated the Throttler to use the number of concurrent requests as the throttling measure instead of the number of requests per period.
Now uses Semaphore to bound the rate with the bound of the semaphore set using the throttle rate. Semaphore 'fair' setting set to ensure fifo behaviour.
Maintains asyc resubmission when config allows with processes being submitted for immediate execution to the executor.
Some tests removed that were based on testing the number of requests per period.

Can you add a note in the 4.3 upgrade guide about this change as end users may need to migrate

There are some throttling unit test failures on CI after 2 build attempts. Not sure if its a bit flaky with this change ?

Let me update the guide and take a look at those failing tests.

@jono-morris in the migration guide, it would be good to add a before vs after example how to migrate the throttle EIP

Added a note to the migration guide  https://github.com/apache/camel/pull/12200

Thank you all for the hard work improving Apache Camel!
I have a question about this change that I would like to ask.
With this new change, how are we going to set the rate limit (10 req/sec) as specified by some API endpoints?
The new throttle EIP design doesn't seem to be practical since most APIs aren't designed with a rate limit of "max concurrent requests"?

Thank you all for the hard work improving Apache Camel!
I have a question about this change that I would like to ask.
With this new change, how are we going to set the rate limit (10 req/sec) as specified by some API endpoints?
The new throttle EIP design doesn't seem to be practical since most APIs aren't designed with a rate limit of "max concurrent requests"?

I think we, somehow, missed this valid question. I was looking at one of the emails on our user list and someone raised the very same question.
@jono-morris, I think, maybe, we should complement the migration guide with this information or a guidance for some scenarios (such as - what to do when there is a need to rate limit it when the time slot is greater than 1000msec and other use cases).

Thank you all for the hard work improving Apache Camel!
I have a question about this change that I would like to ask.
With this new change, how are we going to set the rate limit (10 req/sec) as specified by some API endpoints?
The new throttle EIP design doesn't seem to be practical since most APIs aren't designed with a rate limit of "max concurrent requests"?

I think we, somehow, missed this valid question. I was looking at one of the emails on our user list and someone raised the very same question.
@jono-morris, I think, maybe, we should complement the migration guide with this information or a guidance for some scenarios (such as - what to do when there is a need to rate limit it when the time slot is greater than 1000msec and other use cases).

There were other questions about throttling and about the removal of timeoutPeriodmillis.. I think we should not remove that option.

Thank you all for the hard work improving Apache Camel!
I have a question about this change that I would like to ask.
With this new change, how are we going to set the rate limit (10 req/sec) as specified by some API endpoints?
The new throttle EIP design doesn't seem to be practical since most APIs aren't designed with a rate limit of "max concurrent requests"?

I think we, somehow, missed this valid question. I was looking at one of the emails on our user list and someone raised the very same question.
@jono-morris, I think, maybe, we should complement the migration guide with this information or a guidance for some scenarios (such as - what to do when there is a need to rate limit it when the time slot is greater than 1000msec and other use cases).

There were other questions about throttling and about the removal of timeoutPeriodmillis.. I think we should not remove that option.

Firstly, sorry about the delay in responding.  I've taken away some learnings.
About this change.
Previously the Throttler employed a fixed window algorithm, allowing a fixed number of calls in a particular period, e.g. 2 requests per minute.  This is susceptible to bursts in requests. For example, if the limit is set at 1000 requests/hour, all 1000 requests might be made in the first minute of the window.
With this in mind the algorithm was shifted to more of a leaky bucket implementation using a semaphore with a fixed number of permits.  Callers try to acquire a permit, blocking if necessary when all available permits have been acquired.  When a caller completes processing the permit it holds is released.  This approach limits the number of concurrent requests, there is no notion of rate.
Let's discuss and find the best way forward.

@pai911 See https://issues.apache.org/jira/browse/CAMEL-20355

@pai911 See https://issues.apache.org/jira/browse/CAMEL-20355

Thank you so much!


Support auto-generated API docs

I use sphinx-apidoc to auto-generate API documentation for my project. Right now I have to commit these auto-generated files to my repository so that RTD can build them into HTML docs. It'd be cool if RTD could run sphinx-apidoc for me, since it's easy to forget to regen API docs and commit them to my repo after making changes to my code.

fwiw I'd also be happy if RTD just allowed me to specify my own build process, so it wouldn't to specifically hardcode support for sphinx-apidoc. Though that may also be difficult to allow in a secure way.

I'm also trying to use sphinx-apidoc for my documentation.  I use a tox -e docs to generate my docs

+1 on this... I'm sure, even documenting it in the release procedure, that I'll forget to generate the apidocs and commit them...

We are currently developing a new build system. And I assume we could integrate this in there somehow. However it's not there yet, so I assume we won't have a fix for this in the next couple of weeks, but more in the terms of months.

+1
Adding this support would be incredible and would significantly reduce the friction associated with keeping documentation current. If sphinx-apidoc was supported in readthedocs, a developer wouldn't even need the sphinx toolchain installed locally if they didn't want; their only responsibility would be to keep docstrings up to date.

+1

:+1:

+1

+1

FYI, you can work around this by adding something like the following to your project's conf.py file:
def run_apidoc(_):
    modules = ['a_list_of',
               'python_module_directories',
               'in_your_project']
    for module in modules:
        cur_dir = os.path.abspath(os.path.dirname(__file__))
        output_path = os.path.join(cur_dir, module, 'doc')
        cmd_path = 'sphinx-apidoc'
        if hasattr(sys, 'real_prefix'):  # Check to see if we are in a virtualenv
            # If we are, assemble the path manually
            cmd_path = os.path.abspath(os.path.join(sys.prefix, 'bin', 'sphinx-apidoc'))
        subprocess.check_call([cmd_path, '-e', '-o', output_path, module, '--force'])

def setup(app):
    app.connect('builder-inited', run_apidoc)

This will run sphinx-apidoc during the builder-inited sphinx core event. It should work on readthedocs as well as locally, enabling you to autogenerate your api docs without having to store the output in your git repo. You can even cross reference your manual documentation with these API references.

Another solution which doesn't involve directly calling a subprocess is to use the following in conf.py:
from sphinx.apidoc import main()
main(['-e', '-o', ...])

instead of
subprocess.check_call([cmd_path, '-e', '-o', output_path, module, '--force'])
This solved one of the issues I had was with long path names which are restricted on readthedocs.

@alyjak @Maxyme Thanks. And this works for me.
def run_apidoc(_):
    from sphinx.apidoc import main
    import os
    import sys
    sys.path.append(os.path.join(os.path.dirname(__file__), '..'))
    cur_dir = os.path.abspath(os.path.dirname(__file__))
    module = '.'
    output_path = os.path.join(cur_dir, 'source')
    # main(['-e', '-o', output_path, module, '--force'])

def setup(app):
    app.connect('builder-inited', run_apidoc)

@BowenFu
Thank you! For your code to work, however, you would need to uncomment the main line. Not least of all, I found this incompatible with the directory structure I commonly see, where the .rst source files are all placed in the documentation directory (where config.py is also located). What worked for me was:
def run_apidoc(_):
	from sphinx.apidoc import main
	import os
	import sys
	sys.path.append(os.path.join(os.path.dirname(__file__), '..'))
	cur_dir = os.path.abspath(os.path.dirname(__file__))
	module = os.path.join(cur_dir,"..","labbookdb")
	main(['-e', '-o', cur_dir, module, '--force'])

def setup(app):
	app.connect('builder-inited', run_apidoc)

Two comments on @TheChymera 's code, which mostly works great and which I'm now using:

You'll need to replace labbookdb with the name of your module
Because option parsing starts with the second item in the list, -e doesn't get honored; if you want a separate page per module, you'll need to prepend None to the list passed to main.

Otherwise, a fine solution to the problem of automating API doc updates. Thanks!!

I'm not sure if this is a feature that we'll implement directly into RTD. Having the above solution in our docs would be a great step though! We have similar content under docs/guides.
If we implemented this anywhere, I think we could implement this in our YAML config.

Since last version, the behavior is the same as local doc build, as expected. So, I removed the workaround made in March.
Thanks for the fix.

@Guts that means you just add the extension and it works as expected? Can we close this issue then?

@bpteague When prepending a None since the first argument is removed, the None needs to be an argument before the list. That is, the line of @TheChymera code should be:
main(None, ['-e', '-o', cur_dir, module, '--force'])

Also, maybe you wan to use https://github.com/rtfd/sphinx-autoapi

@Guts that means you just add the extension and it works as expected? Can we close this issue then?

Yes. I removed the workaround and it works. To close the issue, Maybe we should wait for the author feedback? cc @radix

Also, maybe you wan to use https://github.com/rtfd/sphinx-autoapi

I've not really tested https://github.com/rtfd/sphinx-autoapi because it says Python 2 only (Python (2 only -- Epydoc doesn't support Python 3)) and I've not much time to give it a try and understand another Sphinx extension (I'm not a doc expert so it would requires me to really dive into).

Thanks for reporting back, I will close this in a couple of days if the original author doesn't respond or anyone else is having this issue :)

yeah, go ahead and close it if you have a resolution, I am not going to have a chance to verify it soon. Thanks very much!

Ok, I'm closing, please let us know if you have the problem again or if the solution works for you too

I've been using @TheChymera fix with great success until now, but I have to comment it when I want to build the  docs locally.
Does the @Guts update mean I can drop this fix, add extensions = ['autoapi.extension'] in my conf.py, and it will run both locally and on RTD?

Does the @Guts update mean I can drop this fix, add extensions = ['autoapi.extension'] in my conf.py, and it will run both locally and on RTD?

I think so, if you require to execute code conditionally you can see https://docs.readthedocs.io/en/latest/faq.html#how-do-i-change-behavior-for-read-the-docs

Does the @Guts update mean I can drop this fix, add extensions = ['autoapi.extension'] in my conf.py, and it will run both locally and on RTD?

That's what it means. At least, this is what I did: a workaround to handle local/RTD build envs, then removing it with the RTD update.

Sphinx 1.6 to 1.7 broke some things that the aforementioned workaround relied on. A Sphinx 1.6 and 1.7+ compatible version is included below.
def run_apidoc(_):
    ignore_paths = [
        ...
    ]

    argv = [
        "-f",
        "-T",
        "-e",
        "-M",
        "-o", ".",
        ".."
    ] + ignore_paths

    try:
        # Sphinx 1.7+
        from sphinx.ext import apidoc
        apidoc.main(argv)
    except ImportError:
        # Sphinx 1.6 (and earlier)
        from sphinx import apidoc
        argv.insert(0, apidoc.__file__)
        apidoc.main(argv)

def setup(app):
    app.connect('builder-inited', run_apidoc)

Looks like there is some work going on upstream to add autogeneration of API docs to Sphinx.
xref: https://github.com/sphinx-doc/sphinx/pull/4101

Looks like there is some work going on upstream to add autogeneration of API docs to Sphinx.
xref: sphinx-doc/sphinx#4101

This also supported out-of-tree using the sphinxcontrib.apidoc extension. This is used extensively in the OpenStack community and works quite well for our purposes.

With Sphinx 3.1.1 I needed to import
from sphinx.ext.apidoc import main
instead of
from sphinx.apidoc import main


How to enable Flaky Test Management

Interesting article and something which I am keen to implement as we currently have several flaky tests. However, in all of my VSTS projects settings, I do not see an option for Project Settings -> Pipelines -> Test Management.
Is this something which needs to be manually enabled?

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

ID: a8dfb3bf-8cce-7ad8-b2c6-40d6c2b9d441
Version Independent ID: 53e2d39d-6808-70d5-9c26-bc4c5bb109e3
Content: Flaky test management - Azure Pipelines
Content Source: docs/pipelines/test/flaky-test-management.md
Product: devops
Technology: devops-cicd
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

This is a new feature so my guess is that they are still rolling it out across organizations.
https://docs.microsoft.com/en-us/azure/devops/release-notes/2019/sprint-155-update#in-product-support-for-flaky-test-management
I'm also excited for this because our team suffers from flaky tests (we've been calling them "non-determinate" tests).

I am waiting for this too.  However, this update is from July 22.  It is now Aug 6.  Does the roll out take this long?

@LyndseyPaxton, @ahaleiii , @gregpakes - The rollout was complete on July 31st. I've reached out to the PM who authored this article for more information. Will update you as soon as I get a response.

We hit some deployment blocker and thus isn't not enabled. Hoping to complete the rollout in next 2-3 days. Sorry for the delay.

Sorry reopening the issue, I closed it in err. I will close it when the deployment is complete for all customers.

Hi @divais,
Any update on the deployment?
Thanks

Ping. I thought I saw the settings light up in my account at some point, but they aren't there now. Any updates?

Flaky feature is not enabled on all accounts. Do reach us if you face any issues.

Why closed?

I closed it as the key concern was feature unavailability. Are you seeing issues? Do you prefer reopening?

Well - It's still not enabled in my account....  So if you close, I'm just going to open another asking why it's not enabled in my account....

@gregpakes deleted your comment in err, trying to remove the emoji. Is it possible to share your account name.

publicly? privately?

can you please send the details to devops_tools @ microsoft.com

I received a bounce saying:

The group xxxx only accepts messages from people in its organization or on its allowed senders list, and your email address isn't on the list.

Done

I did receive your email and responded back. Based on your system we see that flaky feature is enabled for your account.

Hi @divais
I just checked one of my projects in Azure DevOps, and the menu item is still not there.
Are you able to check if it is enabled for my account please?
Thanks
LP

Okay, I do see it in
Project Settings -> Test management
Thanks for your help. Feel free to close the ticket.
Cheers
LP

All looks good.

Flaky settings are available in Project setting under Test management. Sample below with default settings.

Hi @divais, I sent an email to<EMAIL_ADDRESS>Could you help enable Flaky Test Management for us? Thanks

@zhongyi-zhang It is now enabled. could you please try and let us know.


Final PR in the series. This PR:

split actions.rs into many sub-files
fix capitalisation in some menu item
split the release check list in small checks

Full series:

https://github.com/rerun-io/rerun/pull/5392
https://github.com/rerun-io/rerun/pull/5397
https://github.com/rerun-io/rerun/pull/5407
https://github.com/rerun-io/rerun/pull/5411
https://github.com/rerun-io/rerun/pull/5422
https://github.com/rerun-io/rerun/pull/5433
https://github.com/rerun-io/rerun/pull/5456

Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested the web demo (if applicable):

Using newly built examples: app.rerun.io
Using examples from latest main build: app.rerun.io
Using full set of examples from nightly build: app.rerun.io

[x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
[x] If applicable, add a new check to the release checklist!

PR Build Summary
Docs preview
Examples preview
Recent benchmark results
Wasm size tracking

that's still a loot of manual checks there, but at least more atomic 👍

Agreed. Hopefully, most of that can be automated with the test harness :)


Add Combine docs to the Readme

Basically add a readme section, similar to our Rx and Reactive sections but using the new publishers.

Unfortunately have to close this one as we are removing Combine support for now.

Now that combine is back in 15.0.0-alpha.1, this issue should probably be reopened?

@philipbel yes good catch! though we have added some docs in #2024 and #2066, there might be still some work to look at all the docs and make sure we provide at least most of the things we provide for Rx/RAS docs


SystemAccount token account metadata

Presently, a the cli displays the token accounts associated with system account with the following columns:
 +----------------------------------------------+----------------------------------------------+-----------------+-----------+
 |                Token Account                 |                    Token                     |     Balance     | Standard  |
 +----------------------------------------------+----------------------------------------------+-----------------+-----------+

In particular, the Token column only shows the Mint. It may be nice to either replace the mint with the metadata symbol, e.g. USDC, or add another column that displays the symbol (blank if N/A).
When then account subcommand receives a token account, there is code that does this lookup. So, we can copy paste it from there and modify as needed.

addressed by #10


Doc build broken

Seems to be a version conflict from sphinx and one extension

Builds are going now, and docs for latest version passed, closed by #10807


Adding write access parameter to Events endpoint and Series endpoint

There have to be the possibility to pass a write access parameter to the Events endpoint and the Series Endpoint.
If passed, the Events endpoint and the Series Endpoint should only response results with permission "write access".
Environment Information

opencast 8.3

Ticket is related to :
https://github.com/opencast/opencast/pull/1063
and
https://github.com/opencast/opencast/pull/209
Implementation
EventsEndpoint.java

Adding the parameter "onlyWithWriteAccess" to the Events Endpoint getEvents(...)
when parameter is passed as true we are querying with Permissions.Action.WRITE

Attribut
isRequired = false
description = "Whether only to get the events to which we have write access."
type = Type.BOOLEAN

additional function deserializeMetadataList for deserialize and mapping the catalogs json to a list

further :
SeriesEndpoint.java

Adding the parameter "onlyWithWriteAccess" to the Series Endpoint getSeriesList(...)
when parameter is passed as true we are querying with Permissions.Action.WRITE

Merge Request in Progress...
I think you will categorize as feature?
So request should go into develop or should i offer the request to 8.3 / 8.x?
Greetz
Otti

/cib

This, to me, sounds like a minor feature.  @KatrinIhler, @mliradelc thoughts?

What endpoints are we talking about here? If it's the api, this would probably also require a new api version.
Either way, yeah, I think that's a feature and should go into develop.

Hi.
Yes, these are influencing the endpoints of the external api.
I already created the pull request locally, but i need a branch with the reference number to commit.
Can you please tell me how to do it, then you can have look at the request.
THX a lot

@otti-ssystems if you have the code, follow along at https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork.  File it against opencast/opencast's develop branch.

@gregorydlogan thank you. Thats what i was looking for

@gregorydlogan Oopsie, I fixed my comment now :P

@LukasKalbertodt I don't have a strong opinion right now either, maybe bring this up at the next technical meeting?

We (including @rrolf) discussed this internally and decided against backporting this to 8.x. Adding a new parameter to the external API would require a new API version which is not something we want to do in minor version bumps.
So this issue can be closed and the Studio PR/feature has to wait till 9.x.

This is not only relevant for Studio! Why not leave it open for 9.x?

Ups, missed #1548 🤦♂


last-digit test, L1D/LDT?

A test using only the last digit may be useful if only few digits are presented, and the second last may be skewed.
I only saw a last-two digits test.

Sorry for the delay in replying.
Hum... interesting... well, the implementation followed the tests that were known and researched, but htat might be a nice idea.

Beber, B., & Scacco, A. (2012). What the Numbers Say: A Digit-Based Test for Election Fraud. Political Analysis, 20(2), 211-234. https://doi.org/10.1093/pan/mps003

Thanks. I´ll look into it.


Unify JSON parsing & caching

Now the JSON outline view and the ARM template intellisense parse JSON documents on their own. This duplicated effort should be eliminated.

Performance seems okay at the moment.


18997: Vue 3 Upgrade - Completing Party

Issue #: /bcgov/entity#18997
Description of changes:

Upgrade the Completing Party Shared Component to Vue3
Used the Base-Address Vue 3 component upgrade as a template; excessive imports here that may need to be cut to reduce the bloat.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the business-filings-ui license (Apache 2.0).

Current output in Storybook:

From the Vue 2 version (below) I am unable to currently display the address:

May be due to the excessive Address files and importing the AddressIF incorrectly. Currently working on this and reducing some bloat in the supporting files.

Re:

If you can't resolve this with a rebase, just revert the files and remind me to do a lerna bootstrap --hoist when I next publish these components.

By the way, lerna bootstrap --hoist is deprecated in the latest version of Lerna. One of us will have to research what the new way to update component dependencies is.

Karim, please verify and close off the other conversations. Nice work so far!

Karim, please verify and close off the other conversations. Nice work so far!

Thanks! I verified all conversations. Please let me know if there are any other comments or if I can proceed with merging.


Consider using TypeCache for better performance than assembly scanning

Looks like a cool project. I like how third-party projects can opt-in to it.
I noticed that you scan through all the assemblies, but I couldn't determine how often that happens. Every domain reload? Every enter play? If scanning assemblies happens on play or reload, I strongly suggest taking a look at TypeCache. I used a project that consumed 5 seconds scanning through assemblies. When I switched it to use TypeCache, it took 50 milliseconds.
This change would probably require using an attribute rather than method name.

Wow! Thanks for bringing this up. I wasn't aware of TypeCache and it sounds interesting (and a lot more simple). I'll try to implement it as soon as I can.

Implemented the suggestion. Will keep the PR up for another few hours before merging it with the main branch.


RFC: Suspense option per-query

Summary
Currently suspense is an all-or-nothing thing enabled or disabled on the client for every useQuery. I'd like to see the option to overwrite the global setting on a per-call basis of useQuery.
Proposed Solution
Add a suspense option to UseQueryArgs and use that over the global setting if present.

This is already possible by leveraging the context.suspense option on useQuery https://formidable.com/open-source/urql/docs/api/core/#operationcontext

Oh. Thanks. Sorry for missing that in the documentation.


An issue

Plugin org.apache.maven.plugins:maven-clean-plugin:2.4.1 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-clean-plugin:jar:2.4.1: Could not transfer artifact org.apache.maven.plugins:maven-clean-plugin:pom:2.4.1 from/to central (http://repo.maven.apache.org/maven2): Connection to http://repo.maven.apache.org refused: Connection timed out: connect -> [Help 1]
To see the full stack trace of the errors, re-run Maven with the -e switch.
Re-run Maven using the -X switch to enable full debug logging.
For more information about the errors and possible solutions, please read the following articles:
[Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException

Is this an issue when your compiling the plugin to use or getting the dependencies to develop it?

compiling

@CaptainElliott The message is copied from the maven build log. It seems he cannot connect to the maven central repository, rather than an issue with the plugin itself.

@twizmwazin how can i solve this?

@ElFlambMC Your getting this error because you can't connection the repository. There are several reasons for this, most likely a firewall or anti-virus plugin which is blocking it. Try disabling these and see if that corrects your issue. Don't forget to re-enable it afterwards.

if not, test to compile on anther computer....


Improvement/add-extensions-with-babel-register

Using babel-register for register new extensions in babel config.

I think better put all extensions in the @babel/register, right ?
This looks good

I think better put all extensions in the @babel/register, right ?
This looks good

It does not work '-'

It does not work '-'

I don't think this works

I don't think this works


Access to Build Id via environment variables

AppCenter can set the build number to an auto-incrementing number but we cannot customize the format of the version. For example, we can not set the build number as 1.0.{BuildId}
AppCenter exposes several environment variables but we do not have access to Build Id as an environment variable.
Either give us a way to set build number format or expose Build Id as an environment variable so that we can set format using custom build script.

Hi @Giorgi, if I'm not mistaken APPCENTER_BUILD_ID is available as an environment variable.
For a full list of supported variables please go to  Build Environment variables.
Also, take a look at VS App Center Custom Build Scripts for Production Apps by @jamesmontemagno for how you could use it in your custom build scripts.
Send your feedback afterwards.


Add mnemonic-indexes parameter to README

Is there a way to retrieve the address used before signing?

There could be, using cast wallet address, but it would require to interact twice with the HW or console, which is cumbersome. The only way would be to have it implemented in cast directly


add font-face guide copied from aphrodite

Pull Request Test Coverage Report for Build 156

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 154:
0.0%

Covered Lines:
51

Relevant Lines:
51

💛  - Coveralls


Allow jumps to time out

Might be a little obscure, but I binded my jumps to <tab> and <s-tab> and find myself accidently jumping to places from snippets I expande minutes ago when I actually meant to indent.
Is it possible to configure some sort of timer to make luasnip.jump fail if it has been to long since the last time I jumped/expanded a snippet?

Have you tried setting region_check_events? That should pretty much fix it.
I'm not opposed to implementing a timer-based solution for this, but finding the right timeout sounds pretty hard (we would make it configurable ofc), so I can see it as also being annoying, although less than jumping back into a exited snippet

You might even do this quick and dirty via the config. With cmp I've got something like
      ["<Tab>"] = cmp.mapping(function(fallback)
        if luasnip.expand_or_jumpable() then
          luasnip.expand_or_jump()
        else
          fallback()
        end

in my config. Simply using a local variable (declared outside the cmp.mapping function) last_jump_time and checking on <Tab> if this os.time - last_jump_time > threshold should do the trick (of course you'll need to do this only on luasnip.jumpable() and reset the timer on luasnip.expandable()).
Note: This is still missing to "abort" the snippet (didn't find the luasnip function right now)

EDIT: exit_out_of_region() might be the thing. But after reading on this and region_check_events I as well would encourage you to look into this at first (uses logic/cursor position instead of a timeout which sounds more convenient as a timer might be too unflexible)
EDIT2: But I have to admit, region_check_events doesn't quite work (maybe a misunderstanding on what the region is) as I expected it (and the only doc I can find is in the README.md)

With region_check_events = "CursorMoved", in ls.config.set_config

Ah, try CursorMovedI, it's a different event for movement in INSERT

Thanks! region_check_events covers most of my use cases
although I would still like a timeout feature, this is good enough for my workflow


Add read APIs that enforce aligned memory for SSE

Applications that are using SIMD to accelerate decoding the Arrow data encoding into native data structures (e.g. SIMD popcount for counting nulls in a chunk of a bitmask) should have a well-documented set of APIs to use to ensure that any data buffered in memory is 16-byte (or 32-byte for AVX) aligned. Not required for this moment but keep in the back of our mind

with #219 i think we've done as much as we need to do. it seems anecdotally that SSE/AVX on unaligned memory only has 5-10% worse performance nowadays on modern CPUs