ERROR in [default] \node_modules\rxjs\Observable.d.ts:10:65 Cannot find name 'Promise'

Please provide us with the following information:

OS?  Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
7
Versions. Please run ng --version. If there's nothing outputted, please run
in a Terminal: node --version and paste the result here:
1.0.0-beta.11-webpack.8
Repro steps. Was this an app that wasn't created using the CLI? What change did you
do on your code? etc.
Create a brand new app using the CLI, run ng serve
The log given by the failure. Normally this include a stack trace and some
more information.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\dom\events\hammer_gestures.d.ts:35:71
Cannot find name 'Function'.

ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\dom\events\hammer_gestures.d.ts:35:82
Cannot find name 'Function'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\collection.d.ts:1:24
Cannot find name 'MapConstructor'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\collection.d.ts:2:24
Cannot find name 'SetConstructor'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\collection.d.ts:4:26
Cannot find name 'Map'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\collection.d.ts:4:38
Cannot find name 'Map'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\collection.d.ts:7:8
Cannot find name 'Map'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\collection.d.ts:8:29
Cannot find name 'Map'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\collection.d.ts:11:42
Cannot find name 'Map'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\collection.d.ts:12:26
Cannot find name 'Map'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\collection.d.ts:14:22
Cannot find name 'Map'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\collection.d.ts:15:24
Cannot find name 'Map'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\collection.d.ts:93:28
Cannot find name 'Array'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\collection.d.ts:94:27
Cannot find name 'Array'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\collection.d.ts:94:45
Cannot find name 'Array'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\collection.d.ts:97:70
Cannot find name 'Function'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\collection.d.ts:98:54
Cannot find name 'Function'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\collection.d.ts:100:40
Cannot find name 'Set'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\collection.d.ts:101:21
Cannot find name 'Set'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\collection.d.ts:102:24
Cannot find name 'Set'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:9:19
Cannot find name 'Object'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:10:18
Cannot find name 'Array'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:11:16
Cannot find name 'Map'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:12:16
Cannot find name 'Set'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:13:10
Cannot find name 'DateConstructor'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:14:12
Cannot find name 'RegExpConstructor'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:15:17
Cannot find name 'JSON'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:19:27
Cannot find name 'Function'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:20:32
Cannot find name 'Function'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:21:31
Cannot find name 'Function'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:22:26
Cannot find name 'Array'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:23:16
Cannot find name 'Function'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:24:18
Cannot find name 'Function'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:25:17
Cannot find name 'Function'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:26:19
Cannot find name 'Function'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:27:15
Cannot find name 'Function'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:29:46
Cannot find name 'Function'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:40:25
Cannot find name 'FunctionConstructor'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:41:30
Cannot find name 'Function'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:47:9
A rest parameter must be of an array type.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:51:25
Cannot find name 'DateConstructor'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:56:51
Cannot find name 'String'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:59:54
Cannot find name 'Object'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:63:49
Cannot find name 'Date'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:67:58
Cannot find name 'Map'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:72:36
Cannot find name 'RegExp'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:77:39
Cannot find name 'RegExp'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:79:45
Cannot find name 'RegExp'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:89:46
Cannot find name 'Error'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:106:27
Cannot find name 'RegExpConstructor'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:108:21
Cannot find name 'Function'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:109:20
Cannot find name 'Function'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:109:43
Cannot find name 'Function'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:113:44
Cannot find name 'Object'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:116:35
Cannot find name 'Error'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:116:43
Cannot find name 'Object'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:117:34
Cannot find name 'Error'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:117:42
Cannot find name 'Object'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:119:29
Cannot find name 'Object'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:120:27
Cannot find name 'Object'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:123:137
Cannot find name 'Date'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:124:39
Cannot find name 'Date'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:125:35
Cannot find name 'Date'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:126:26
Cannot find name 'Date'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:127:18
Cannot find name 'Date'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:128:24
Cannot find name 'Date'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\facade\lang.d.ts:136:46
Cannot find name 'Object'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\web_workers\shared\client_message_broker.d.ts:32:64
Cannot find name 'Promise'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\web_workers\shared\client_message_broker.d.ts:40:55
Cannot find name 'Promise'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\web_workers\shared\serializer.d.ts:10:36
Cannot find name 'Object'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\web_workers\shared\service_message_broker.d.ts:27:75
Cannot find name 'Function'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\web_workers\shared\service_message_broker.d.ts:35:67
A rest parameter must be of an array type.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\web_workers\shared\service_message_broker.d.ts:35:83
Cannot find name 'Promise'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\web_workers\worker\location_providers.d.ts:21:85
Cannot find name 'Promise'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\worker_app.d.ts:6:52
Cannot find name 'Array'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\worker_app.d.ts:13:55
Cannot find name 'Array'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\worker_render.d.ts:35:52
Cannot find name 'Array'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\worker_render.d.ts:40:51
Cannot find name 'Array'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules@angular\platform-browser\src\worker_render.d.ts:44:54
Cannot find name 'Array'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules\rxjs\Observable.d.ts:10:65
Cannot find name 'Promise'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules\rxjs\Observable.d.ts:11:68
Cannot find name 'ArrayLike'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules\rxjs\Observable.d.ts:38:19
Cannot find name 'Function'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules\rxjs\Observable.d.ts:66:59
Cannot find name 'Promise'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules\rxjs\Observable.d.ts:66:69
Cannot find name 'Promise'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules\rxjs\Subject.d.ts:23:19
Cannot find name 'Function'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules\rxjs\Subscription.d.ts:4:60
Cannot find name 'Function'.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules\typescript\lib\lib.es2015.d.ts:17:0
File 'C:/Users/rakibler/Projects/efile/node_modules/typescript/lib/lib.es2015.core.d.ts' not found.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules\typescript\lib\lib.es2015.d.ts:18:0
File 'C:/Users/rakibler/Projects/efile/node_modules/typescript/lib/lib.es2015.collection.d.ts' not found.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules\typescript\lib\lib.es2015.d.ts:19:0
File 'C:/Users/rakibler/Projects/efile/node_modules/typescript/lib/lib.es2015.generator.d.ts' not found.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules\typescript\lib\lib.es2015.d.ts:20:0
File 'C:/Users/rakibler/Projects/efile/node_modules/typescript/lib/lib.es2015.iterable.d.ts' not found.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules\typescript\lib\lib.es2015.d.ts:21:0
File 'C:/Users/rakibler/Projects/efile/node_modules/typescript/lib/lib.es2015.promise.d.ts' not found.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules\typescript\lib\lib.es2015.d.ts:22:0
File 'C:/Users/rakibler/Projects/efile/node_modules/typescript/lib/lib.es2015.proxy.d.ts' not found.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules\typescript\lib\lib.es2015.d.ts:23:0
File 'C:/Users/rakibler/Projects/efile/node_modules/typescript/lib/lib.es2015.reflect.d.ts' not found.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules\typescript\lib\lib.es2015.d.ts:24:0
File 'C:/Users/rakibler/Projects/efile/node_modules/typescript/lib/lib.es2015.symbol.d.ts' not found.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules\typescript\lib\lib.es2015.d.ts:25:0
File 'C:/Users/rakibler/Projects/efile/node_modules/typescript/lib/lib.es2015.symbol.wellknown.d.ts' not found.
ERROR in [default] C:\Users\rakibler\Projects\efile\node_modules\typescript\lib\lib.es2015.d.ts:26:0
File 'C:/Users/rakibler/Projects/efile/node_modules/typescript/lib/lib.es5.d.ts' not found.

Mention any other details that might be useful.
It might be important to note that I don't have admin access, plus we have a decrypting firewall which has caused issues before.  I dunno if this is related though.

Thanks! We'll be in touch soon.

Same here

typescript upgraded to 2.0.2. lock the version to 2.0.0 should fix the problem.

tsc -v
version 2.0.2
Same here

Same errors with typescript version 1.8.10 (OSX El Capitan), node version 6.3.1 (via brew).
Upgraded to node 6.5.0, same thing.
Upgraded typescript to 2.0.0. Errors gone.
Upgraded typescript to 2.0.2. Errors back.

Have same issue did anyone manage to find a fix ?

@matpulis typings are being phased out in favor of the new @types, you can see an example here for adding new types
tsconfig.json
package.json

@traneHead can confirm, for both node 6.5 and 6.1

@traneHead in my case errors were gone after reverting typescript to 2.0.0 (i mean both global and local package) and upgrading node to 6.5.0 and npm to 3.10.6

Bug confirmed on a fresh system with latest node.js and
npm i -g typescript angular-cli@webpack
ng new

Sorry if this sounds dense, I upgraded typescript to latest (npm install -g typescript@next), but i am having trouble rolling back to 2.0.0. Are you using npm shrinkwrap?

@SeekingMonkey
npm uninstall typescript -g npm cache clean npm install<EMAIL_ADDRESS>-g
should do the trick

Same issues in new projects here.

Experiencing the same problem.
Win 7
Node 6.5.0
Npm 3.10.6
Typescript 2.0.0

Experiencing same problem.
node 6.2.2
npm 3.10.6
Rollback to typescript 2.0.0 provides a temporary fix.

I am experiencing the same problem while installing angular-cli@webpack globaly.
Unfortunately rollbacking to Typescript 2.0.0 didn't fix the problem form me.

CLI team: a couple of days ago we got a .3, .4, .5., .6, .7., .8 to quickly work through an irritating dependency problem. Now we have another one, this time with Typescript. How about shipping .9 today with an updated TS dependency? Otherwise I expect a few dups each day of this issue, and needlessly irritated users, in the meantime.

Also, regarding a comment earlier, I have experimentally confirmed that there is no need at all to discard your NPM cache ("npm cache clean") to work around this. NPM is highly capable of understanding two different versions of a package in its cache, in a sense that is its main purpose in existence.

I'm one of those users ;(

I was able to get it working but only after much fiddling. I'm using Node 6.5.0, npm 3.10.6 and TypeScript 2.0.0 (local, not global). It also seemed not to work for me until I blew away my project directory and ran ng new again. So I can confirm that configuring your libraries to those versions can work. If it doesn't work for you, maybe try creating a fresh new project to see if you can do an error-free ng build there.

I can confirm
changing
"typescript": "^2.0.0"
to
"typescript": "2.0.0"
is a valid workaround for the issue.
So is it a typescript thing or angular-cli ;)

This did not work for me. See issue 1887 for more details.

Having similar problem. See issue 1887 for more details.

I have the same problem with  angular-cli@webpack ,
I tried with typescript 1.8.0, 2.0.0, windows 7, windows 8, node 5.8, 6.5. nothing work

I was able to solve this problem with the following configuration:
Upgrade imy tools
 node --version
v6.5.0
$ npm --version
3.10.3
$ ng --version
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
angular-cli: 1.0.0-beta.11-webpack.8
node: 6.5.0
os: darwin x64

$ npm list -g
/usr/local/lib
├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>
...

├──<EMAIL_ADDRESS>
....

Changed "typescript": "^2.0.0"to "typescript": "2.0.0"in mypackages.json`
Executed the folling commands on my project root
$ rm -rf node_modules dist tmp typings
$ npm install --save-dev angular-cli@webpack

RC6 came out and has a dependency on TS 2.0.2.  Can't upgrade until the CLI supports it :(

Yep, blocked until CLI has 2.0.2 support

Seems to be an issue in awesome-typescript-loader, see https://github.com/Microsoft/TypeScript/issues/10633

I guess I found the solution, i tried it in two different machines and it worked:
Downgrade globally to Typescript 2.0.0   &   change
 "typescript": "^2.0.0"to "typescript": "2.0.0"in mypackages.json

I'm a little disappointed with the CLI. I spent the day trying to solve packages incompatibility.  I managed to install everything and now this failure. The worst that there are many people with the same problem and no solution.
$ ng --version
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
angular-cli: 1.0.0-beta.11-webpack.8
node: 6.5.0
os: linux x64

Just to guide a little on a real fix. Aggresively adding libs to the tsconfig removed the errors. Mine actually looks like this:
{
  "compilerOptions": {
    "declaration": false,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "lib": [
      "es5",
      "es6",
      "dom",
      "es2015.core",
      "es2015.collection",
      "es2015.generator",
      "es2015.iterable",
      "es2015.promise",
      "es2015.proxy",
      "es2015.reflect",
      "es2015.symbol",
      "es2015.symbol.wellknown"
    ],
    "mapRoot": "./",
    "module": "es6",
    "moduleResolution": "node",
    "outDir": "../dist/out-tsc",
    "sourceMap": true,
    "target": "es5",
    "typeRoots": [
      "../node_modules/@types"
    ]
  }
}

I realize there are a lot of moving parts, but has there ever been a thought to hold back releases of individual parts until they can release an entire ecosystem update?  In the grand scheme of things a stagger of a few days or weeks doesn't matter, but wow is it frustrating...
Just a thought - other companies (Elastic is great at this IMHO), wait to release Elasticsearch or Kibana until they are all compatible with one another.  It would be nice to see a release package that would include:
angular-cli
angular2
angular2-material
I wouldn't mind waiting another week to get RC6 or RC7 if it meant that everything just worked.

@bdinsmor but there are many people using angular2 without angular-cli, and even more using it without angular2-material
that would mean making all those people wait for something they don't care about

I understand what you are saying but if we are talking about waiting a week
to avoid 1000 GitHub issues, I would think it would be worth the wait and
forced coordination between Google teams.
On Sat, Sep 3, 2016, 8:58 AM aszechlicki<EMAIL_ADDRESS>wrote:

@bdinsmor https://github.com/bdinsmor but there are many people using
angular2 without angular-cli, and even more using it without
angular2-material
that would mean making all those people wait for something they don't care
about
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular-cli/issues/1901#issuecomment-244544976,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGse2vHo5twJwq_YOQCSAWQ2yHWuprY-ks5qmW8DgaJpZM4JwxgO
.

Hello - My understanding of a version appended with Beta it that is has been made available to the user community for usability validation and, unless something goes radically wrong - like an explosion on the test platform like SPACE-X this part week, a few usability issues might be addressed before the the final version is released, and that the final version will be 100% compatible with the Beta versions. My understanding of a version appended with RC means that it is ready for market, that the final version is around the corner, and it will be 100% with the RC versions.
The recent series of releases by Google and angular-cli suggest that we all are operating from a different perception of the meaning of these terms.
The lessons learned suggest that our friends at Google and angular-cli owe their user community a good discussion for us to develop a common understanding of the meaning of these terms, particularly in terms of their responsibilities in appending them to their releases and then, once this is in place, do a better job sticking to what has been agreed.

Upgrading to the latest CLI version should solve this issue

I don't understand whether using "^" or "~" or locking to specific version in package.json is the best practice. Spent 3 hours trying to solve the same issue today, before I found this thread.

This issue is not any longer active. Generally deps are pretty stable now. The CLI supports YARN, too!

delete "node_modules" and reinstall using
$ npm install


Allow user to manually set the offset of the arrow

I've been using this library indirectly for an Electron app (with react-joyride), and found the need to be able to move the arrow. This is because I wanted the arrow to point to something outside of the application window.
Use cases for others may be that they create a dialog and want a step to point to it from a parent window.

Hello,
The floater, including the arrow positioning, is handled by popper.js.
If you need to change its behavior, you could set a modifier function via props.
Take a look at the source


Memory leak

Few different changes in PR, all related to memory / perf issues recently:

Added S3CacheAwareStorage, this can read/write both/either binary serialised or protobuf serialised files. This implementation is temporary, we'll currently write both from WF processer but only read binary until a later date.
Update ISimpleStorageFileInfo to have async properties rather than getters to avoid async over sync potentially causing threadpool starvation issue.
Added a timeout while trying to get asyncLocker lock. Currently this will throw an exception if thread fails to enter lock but this will be altered shortly to have different impls for WF processor and public facing.
Update ArchiveStorageServiceWorkStore to use dictionary, rather than IMemoryCache for caching as this is "scope" scoped.
Added extra logging to WF processor.

deployed this branch to test and updated iiif-builder to use protobuf to confirm it's working okay.


Refactor curator dashboard views

fixed by https://github.com/ugent-library/biblio-backoffice/pull/1436


add method to compute distance matrix from numeric metadata categories

This is covered in @jairideout's skbio cookbook recipe.

This currently can't be implemented because methods/visualizers require at least one input artifact. Should be an easy fix in the framework to support this.

When it's possible for us to support this, we can promote the current _metadata_distance function to a method.

replaced by qiime2/q2-metadata#5


Getting TS error Transformer<Root, Root>' is not assignable to type 'Plugin<any[], any, any>'.

I am getting the below error however the code works fine when I compile
import { MDXRemote } from 'next-mdx-remote/rsc';
import rehypePrettyCode from 'rehype-pretty-code';

export default async function Page({ params }: any) {
  return (
    <MDXRemote
    source={`test`}
    options={{
      mdxOptions: {
        rehypePlugins: [rehypePrettyCode],
      },
    }}
  />
  );
}

This type error is because next-mdx-remote uses an old version of vfile.
The main issue in your example is:
Type 'VFileMessage' is missing the following properties from type 'VFileMessage': ancestors

vfile v6 has those properties whereas v5.3 which next-mdx-remote uses doesn't. So the issue is next-mdx-remote is using an older version of vfile dependency:
https://github.com/hashicorp/next-mdx-remote/blob/main/package.json#L17
rehype-pretty-code uses the latest version of unified which has vfile ^6 as a dependency:
https://github.com/unifiedjs/unified/blob/b69689bba52a918d87aa62f295ccffa8d9aa8ef8/package.json#L54
cc @atomiks

Seems that next-mdx-remote should update to latest unified/vfile dependencies. For now, you can ignore the type error since runtime works fine.


Native File System post

What's changed, or what was fixed?

Fugu post for Native FS

Fixes: #7717
Target Live Date: 2019-08-20

[X] This has been reviewed and approved by (NAME)
[X] I have run npm test locally and all tests pass.
[X] I have added the appropriate type-something label.
[X] I've staged the site and manually verified that my content displays correctly.

Whoops!
There were 5 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2018/11/writable-files.md - Unable to read file, was it deleted?
src/content/en/updates/2019/08/native-file-system.md#L367 - Common typo found: 'Omnibox' Should it be 'address bar'? See: https://developers.google.com/style/word-list#omnibox
src/content/en/updates/2019/08/native-file-system.md#L373 - Common typo found: 'omnibox' Should it be 'address bar'? See: https://developers.google.com/style/word-list#omnibox
src/content/en/updates/2019/08/native-file-system.md#L373 - Common typo found: 'omnibox' Should it be 'address bar'? See: https://developers.google.com/style/word-list#omnibox
src/content/en/updates/2019/08/native-file-system.md#L387 - Common typo found: 'omnibox' Should it be 'address bar'? See: https://developers.google.com/style/word-list#omnibox

Whoops!
There were 5 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2018/11/writable-files.md - Unable to read file, was it deleted?
src/content/en/updates/2019/08/native-file-system.md#L363 - Common typo found: 'Omnibox' Should it be 'address bar'? See: https://developers.google.com/style/word-list#omnibox
src/content/en/updates/2019/08/native-file-system.md#L369 - Common typo found: 'omnibox' Should it be 'address bar'? See: https://developers.google.com/style/word-list#omnibox
src/content/en/updates/2019/08/native-file-system.md#L369 - Common typo found: 'omnibox' Should it be 'address bar'? See: https://developers.google.com/style/word-list#omnibox
src/content/en/updates/2019/08/native-file-system.md#L383 - Common typo found: 'omnibox' Should it be 'address bar'? See: https://developers.google.com/style/word-list#omnibox

Whoops!
There were 5 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2018/11/writable-files.md - Unable to read file, was it deleted?
src/content/en/updates/2019/08/native-file-system.md#L363 - Common typo found: 'Omnibox' Should it be 'address bar'? See: https://developers.google.com/style/word-list#omnibox
src/content/en/updates/2019/08/native-file-system.md#L369 - Common typo found: 'omnibox' Should it be 'address bar'? See: https://developers.google.com/style/word-list#omnibox
src/content/en/updates/2019/08/native-file-system.md#L369 - Common typo found: 'omnibox' Should it be 'address bar'? See: https://developers.google.com/style/word-list#omnibox
src/content/en/updates/2019/08/native-file-system.md#L383 - Common typo found: 'omnibox' Should it be 'address bar'? See: https://developers.google.com/style/word-list#omnibox

Whoops!
There were 5 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2018/11/writable-files.md - Unable to read file, was it deleted?
src/content/en/updates/2019/08/native-file-system.md#L363 - Common typo found: 'Omnibox' Should it be 'address bar'? See: https://developers.google.com/style/word-list#omnibox
src/content/en/updates/2019/08/native-file-system.md#L369 - Common typo found: 'omnibox' Should it be 'address bar'? See: https://developers.google.com/style/word-list#omnibox
src/content/en/updates/2019/08/native-file-system.md#L369 - Common typo found: 'omnibox' Should it be 'address bar'? See: https://developers.google.com/style/word-list#omnibox
src/content/en/updates/2019/08/native-file-system.md#L383 - Common typo found: 'omnibox' Should it be 'address bar'? See: https://developers.google.com/style/word-list#omnibox

Whoops!
There were 5 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2018/11/writable-files.md - Unable to read file, was it deleted?
src/content/en/updates/2019/08/native-file-system.md#L363 - Common typo found: 'Omnibox' Should it be 'address bar'? See: https://developers.google.com/style/word-list#omnibox
src/content/en/updates/2019/08/native-file-system.md#L369 - Common typo found: 'omnibox' Should it be 'address bar'? See: https://developers.google.com/style/word-list#omnibox
src/content/en/updates/2019/08/native-file-system.md#L369 - Common typo found: 'omnibox' Should it be 'address bar'? See: https://developers.google.com/style/word-list#omnibox
src/content/en/updates/2019/08/native-file-system.md#L383 - Common typo found: 'omnibox' Should it be 'address bar'? See: https://developers.google.com/style/word-list#omnibox

:tada: This has been pushed live to https://developers.google.com/web/


Adding educat_orig

As proposed by Tom, I have added the educat_orig (as the others are educat# and educat_isced went for this instead of education_orig). I have updated:

The excel data dictionary,
The GLD Guide,
The GLD template, and
The Quality checks

The variable is placed between educat4 and educat_isced:
https://github.com/worldbank/gld/blob/6ec2eb06d33dbf7500d7bdb5448b89f2426edb26/Support/Templates/GLD_Harmonization_Template.do#L516-L534
Note that the rules (as explained in the guide, screenshot below) is that, if the matching can happen 1-1 (i.e., there is a single variable in the raw data that codes educational attainment, simply use that. If there are two or more variables that may be necessary, leave missing and make a note of it.

Let me know of any questions you may have.

Completed.

Also completed for me in #130

Completed for ZAF and IDN.


test notifications work, but alerts fail

I see this error in logs
sentry-self-hosted-worker-1 | 04:38:38 [INFO] sentry.rules: rules.fail.plugin_does_not_exist (event_id='...' plugin='sentry_telegram_py3')

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

Comparison is base (d5fdb24) 94.20% compared to head (5070c4b) 94.20%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master       #3   +/-   ##
=======================================
  Coverage   94.20%   94.20%
=======================================
  Files           2        2
  Lines          69       69
  Branches        5        5
=======================================
  Hits           65       65
  Misses          2        2
  Partials        2        2

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


Increasing Query result limit value to 5000 from 500 to reduce roundtrips to support also queries returning dozens of thousands rows with a few columns

With 500 hardcoded value its extremely unperformant having roundtrips to collect large amount of data.
As for now Dremio doesnt allow to download results for queries posted via REST API, we have to iterate multiple times having limit 500 until the end. It causes an extra time and server workload. The PR is too increase the value, and also fixes the bug if user provides a negative limit.

I hate to totally 180 on my previous comments... I still think this should be configurable, but in my rapidly changing experience with the Dremio source code, this is the type of setting that Dremio would normally expose as a "Support Key", that you would provide through the Admin screen under Support.
Dremio.conf is a pretty rigid config file, with all settings being defined in advance, support keys seem a bit more flexible.

@patricker I moved that config value to optionManager


fix performance issue in FS

FS is too slow
it should max be 50% slower than native (but in fact I think can be much better)
test in R & RW mode

@despiegk @muhamadazmy
From my quick using dd, FS is slower between 35%-45%.
Below is top10 result from  pprof
(pprof) top10
170ms of 180ms total (94.44%)
Showing top 10 nodes out of 53 (cum >= 10ms)
      flat  flat%   sum%        cum   cum%
      70ms 38.89% 38.89%      100ms 55.56%  syscall.Syscall
      20ms 11.11% 50.00%       20ms 11.11%  runtime.(*mspan).sweep.func1
      10ms  5.56% 55.56%       10ms  5.56%  runtime.(*mcentral).grow
      10ms  5.56% 61.11%       10ms  5.56%  runtime.casgstatus
      10ms  5.56% 66.67%       10ms  5.56%  runtime.getcallerpc
      10ms  5.56% 72.22%       10ms  5.56%  runtime.lock
      10ms  5.56% 77.78%       10ms  5.56%  runtime.memmove
      10ms  5.56% 83.33%       20ms 11.11%  runtime.rawstring
      10ms  5.56% 88.89%       30ms 16.67%  runtime.slicebytetostring
      10ms  5.56% 94.44%       10ms  5.56%  runtime/internal/atomic.Cas

The first two columns show the number of samples in which the function was running (as opposed to waiting for a called function to return), as a raw count and as a percentage of total samples.
So, syscall.Syscall, runtime.(*mspan).sweep.func1 , runtime.(*mcentral).grow are top three functions that take the time.
sweep is GC action, while grow is memory/heap allocation.
I guest syscall is calling file related system call.
Next step:

test using more sophisticated tools like iozone or fio
check for GC & memory related improvement

its not about iozone or fio
because that is to 1 file
that is not where the issue is
issue is when opening lots of files
e.g. when we walk over filesystem
even when files are in cache already
On Mon, Feb 29, 2016 at 10:15 AM, Iwan Budi Kusnanto <
<EMAIL_ADDRESS>wrote:

@despiegk https://github.com/despiegk @muhamadazmy
https://github.com/muhamadazmy
From my quick using dd, FS is slower between 35%-45%.
Below is top10 result from pprof
(pprof) top10
170ms of 180ms total (94.44%)
Showing top 10 nodes out of 53 (cum >= 10ms)
flat  flat%   sum%        cum   cum%
70ms 38.89% 38.89%      100ms 55.56%  syscall.Syscall
20ms 11.11% 50.00%       20ms 11.11%  runtime.(*mspan).sweep.func1
10ms  5.56% 55.56%       10ms  5.56%  runtime.(*mcentral).grow
10ms  5.56% 61.11%       10ms  5.56%  runtime.casgstatus
10ms  5.56% 66.67%       10ms  5.56%  runtime.getcallerpc
10ms  5.56% 72.22%       10ms  5.56%  runtime.lock
10ms  5.56% 77.78%       10ms  5.56%  runtime.memmove
10ms  5.56% 83.33%       20ms 11.11%  runtime.rawstring
10ms  5.56% 88.89%       30ms 16.67%  runtime.slicebytetostring
10ms  5.56% 94.44%       10ms  5.56%  runtime/internal/atomic.Cas
The first two columns show the number of samples in which the function was
running (as opposed to waiting for a called function to return), as a raw
count and as a percentage of total samples.
So, syscall.Syscall, runtime.(*mspan).sweep.func1 ,
runtime.(*mcentral).grow are top three functions that take the time.
sweep is GC action, while grow is memory/heap allocation.
I guest syscall is calling file related system call.
Next step:

test using more sophisticated tools like iozone or fio
check for GC & memory related improvement

—
Reply to this email directly or view it on GitHub
https://github.com/g8os/home/issues/3#issuecomment-190115469.

--
Kristof De Spiegeleer
+971525609014
+201206927877
+32 475405474
skype: despiegk

issue is when opening lots of files

iozone can also do multithreading test.
using iozone to do write test with 5 threads, FS is +90% slower than native.
profiling give different results
30ms 60.00% 60.00%       30ms 60.00%  syscall.Syscall
      10ms 20.00% 80.00%       10ms 20.00%  path/filepath.Clean
      10ms 20.00%   100%       10ms 20.00%  runtime.(*mcentral).grow
         0     0%   100%       50ms   100%  github.com/Jumpscale/aysfs/watcher.(*backenCleaner).Run
         0     0%   100%       40ms 80.00%  os.Lstat
         0     0%   100%       10ms 20.00%  path/filepath.Join
         0     0%   100%       50ms   100%  path/filepath.Walk
         0     0%   100%       10ms 20.00%  path/filepath.join
         0     0%   100%       50ms   100%  path/filepath.walk
         0     0%   100%       10ms 20.00%  runtime.(*mcache).refill

I am starting to check the code now
@despiegk what test tools you use? so we don't missed any check.

After more iozone tests, i found that it is slower by at least 95%.
I have tried to replace file.WriteAt  (https://github.com/g8os/fs/blob/master/rw/file.go#L183)  usage with bufio, but it didn't give any improvement.
I was thinking of optimizing write func because i thought this is where the syscall being called.
I got more detailed profiling graph from iozone & dd test,  and found that:

Cleaner goroutine was the one that dominating the profiling result
Cleaner goroutine only run for < 1 second
A bit weird, it is quite fast but dominating the result.

So, i will check it again without running the cleaner.
I attached profiling graph
from iozone

from dd

@despiegk @muhamadazmy
Please forget about my test result that stated it slower by 90-95% using iozone.
The test was using this command
iozone -t 5 -i 0 -F 1 2 3 4 5

It only writes 512kb of files.
I changed to make it write 100mb of files using this command
iozone -l 5 -u 5 -r 4k -s 100mm -F 1 2 3 4 5 -i 0

The performance is slower by around 75% now, using 5 threads.
I think i have more accurate profiling result, please see these attachments.
profile-dd-2gb.pdf
profile-iozone-100mb-without-cleaner.pdf
As you can see, most time was used by bazil, our fuse library.
I think it is worth to do these:

check bazil implementation
try another lib, maybe https://github.com/hanwen/go-fuse, it is native binding.

I was thinking idd we should try another library

Other library is an idea indeed. But I liked the fact that this one if fully written in Go. I also found the interface of hanwen/go-fuse more cumbersome than the one from bazil/fuse.
Maybe it worst looking a bit in the implementation of bazil/fuse, I remember @robvanmieghem saying that he didn't had this slow issue on Mac at all.  Means issue probably come from a linux implementation detail in the lib ??

Maybe it worst looking a bit in the implementation of bazil/fuse

OK, wiil check it.
I remember @robvanmieghem saying that he didn't had this slow issue on Mac at all

I thought g8os/fs doesn't support Mac, it failed to build for me.
~/pathgo/src/github.com/g8os/fs#go build ./...
# github.com/g8os/fs/watcher
watcher/cleaner.go:38: sys.Atim undefined (type *syscall.Stat_t has no field or method Atim)
watcher/cleaner.go:38: not enough arguments in call to time.Unix
~/pathgo/src/github.com/g8os/fs#go version
go version go1.6 darwin/amd64
~/pathgo/src/github.com/g8os/fs#

it has not to do with performance on 1 file (see my remark before)
so tools like iozone won't tell you much
we are particularly slow when we work when opening lots of small files
please write a benchmark prog for that
e.g. use the RW feature, write lots of small files
same for R feature , open all files & read them see why slow
compare with same test on native FS
k.
On Tue, Mar 1, 2016 at 10:44 AM, Iwan Budi Kusnanto <
<EMAIL_ADDRESS>wrote:

Maybe it worst looking a bit in the implementation of bazil/fuse
OK, wiil check it.
I remember @robvanmieghem saying that he didn't had this slow issue on Mac at all
I thought g8os/fs doesn't support Mac, it failed to build for me.
~/pathgo/src/github.com/g8os/fs#go build ./...
github.com/g8os/fs/watcher
watcher/cleaner.go:38 http://github.com/g8os/fs/watcherwatcher/cleaner.go:38: sys.Atim undefined (type *syscall.Stat_t has no field or method Atim)
watcher/cleaner.go:38: not enough arguments in call to time.Unix
~/pathgo/src/github.com/g8os/fs#go version
go version go1.6 darwin/amd64
~/pathgo/src/github.com/g8os/fs#
—
Reply to this email directly or view it on GitHub
https://github.com/g8os/home/issues/3#issuecomment-190575784.

--
Kristof De Spiegeleer
+971525609014
+201206927877
+32 475405474
skype: despiegk

@iwanbk it used to build on mac, I can see the build fails on a linux specific code (recent code). This part should be adopted to support mac as well, I don't have mac to test build and performance on it.

it has not to do with performance on 1 file (see my remark before)
so tools like iozone won't tell you much

I saw your remark, but iozone has multi processes option.
iozone -t 10 -r 4k -s 100mm  -i 0

With this command, it will create 10 processes, each process write to different file.
I will write the benchmark prog anyway (after checking bazel fuse & native binding), so we can see it.

profiling
i did more check on profiling result and found that after calling bazel/fuse code, it going back to call github.com/g8os/fs/rw.(*fsFileHandle).Write func.
So, it use our own Go code to write file.
bazel/fuse
I can't find any flaw in the code, i will do more check tomorrow and then check github.com/hanwen/go-fuse
testing
I did iozone test using various number of processes, here are my finding
native
number of process - write speed - read speed
1      722628     4587816
2      265395    2621656
4     45664       1361901
8     10485       3537             -> very dropped read speed
fuse
1 44516   325428
2  20608  219381
4  9958    102366
8 5077    3464                     -> very dropped read speed
From above test, read speed was very dropped in 8 processes, but it also happens in native FS. So, we still can't conclude that it has scalability issue.
But it really has speed issue.

I have checked hanwen/go-fuse lib:

From my understanding, it only has advantage of using native libfuse to dispatch file operation request to our own handler
from previous profiling graph, our own handler is where the slowness come.
their example also use file.WriteAt to write to file, same as current implementation.
@muhamadazmy CMIIW in case you also have checked hanwen/go-fuse.

So, i think it is better to improve what we have now.

test result using program from PR https://github.com/g8os/fs/pull/3
command : benchmark -nf=20,50,100 -sf=2
The command means : Write & read 2 MB of files, using 20, 50, and 100 goroutines. Each goroutine write/read to different file.
Time is total execution time
native
#files 	 write time 	 read time
20 		 3.791748675s 	 10.961196ms
50 		 9.504657191s 	 22.045919ms
100 		 19.003215961s 	 46.899218ms

Performance is quite consistent
fuse
#files 	 write time 	 read time
20 		 4.010416167s 	 87.938237ms
50 		 9.85989628s 	 282.545306ms
100 		 19.741489371s 	 5.754063046s

Performance is dropped when using 100 goroutines.(100 goroutines is a lot of files btw)
It also sometimes make the fuse crashed.

i updated test result in previous comment, it use improved benchmark program.

profiling result for above tests
profile-read-write.pdf
Focusing on read operation, majority of the times spent on bazil.org/fuse.(*ReadRequest).Respond
From my quick check, it seems that it is the code which copy/move read result from fuse to our application.
I said move because from profiling it use runtime.memmove

fixed in PR https://github.com/g8os/fs/pull/10

@rkhamis please find someone to do proper tests and make sure all newest code is used

Verfified by @ashraffouda


Add arena resolution when all entry types are the same

While working on an update to my app I noticed a delay was occurring between the time when I started physically dragging a picker widget and when the picker widget would actually start scrolling.  The picker was inside a scaffold, which builds its contents inside a ListView.  After some digging, I realized there was a competition going on between the scaffold's vertical drag gesture and the picker's vertical drag gesture.  After a certain amount of slop the gesture arena would award the winner to the picker and the picker would then jump to catch up to my finger.
I did not see an easy way to deal with this in the existing framework, so I added a resolution process to the gesture arena manager.  If all of the gesture arena entries have the same runtime type, it will make the first entry the winner.  In my case, this allows the picker to immediately win and respond to the drag gesture, which results in a much more fluid experience.  I think this logic makes sense in general, hence this PR.  I have not been able to arrive at a case where this behavior is undesirable.
Be advised that I had to update one of the tests in tap_test.dart.  The end result of that test is still the same, but the events now happen in a different order.  I do not know if this is a breaking change.

Thanks @amirh.  Is your concern primarily directed toward multi-pointer gestures, or does it encompass single-pointer gestures as well?  I can certainly see where this change might cause complications with multi-pointer gestures.  If this resolution only targeted descendants of OneSequenceGestureRecognizer, would that ease your concerns?  Or are there aspects of the state of single-pointer gestures I am missing?

Hi,
My concern is that we have no guarantee that 2 gesture recognizers with the same type are going to behave the same. Even if today we can look at the gesture recognizers in the framework and say that this is this case (I'm not sure it is, e.g you can set some fling parameters on DragGestureRecognizers) I can easily see these classes getting new configuration parameters, and we also have to consider gesture recognizers that are not part of the framework.
I do think we should look for a solution for the issue you mentioned. What do you think about filing an issue with a short code snippet that demonstrates the problem (a gesturedetector with vertical drag gesture inside a scrollable?) and we could discuss potential solutions there?
Thanks again for your contributions! would be great to improve the speed of gesture resolution.

I don't think this is the right solution, because as amir says, it's possible for different instances of the same type of gesture recognizer to be looking for different gestures.
However, I do agree that the problem you describe is a real one. Would you mind filing a bug so that we can discuss possible solutions?
I'm going to close this PR in the meantime since we don't think it's the right approach. Thanks for your contribution though!

Sorry guys, real life took a bite out of my free time.  I will file the bug now.  Thanks for entertaining the PR, even if it wasn't the right direction to go in.


describe() GUI fix

I noticed that describe() works as intended if placed after the assertion. This is because in ui/results/method.gd line 26, the following code resets the title: component.set_text(0, "%s" % title). It's still a bug in my opinion since describe() should work regardless of execution order.
I've done a search and it doesn't seem that anything changes the title of the method after it is initialized. This means that line 26 is redundant and can be removed. To be sure, I checked the blame and it seems that this line was supposed to show the total number of assertions passed for that method in https://github.com/AlexDarigan/WAT/commit/06613e7035f946914e55269de8033df74c30b58a like so: component.set_text(0, "(%s/%s) %s" % [passed, total, title]). However, it was set back to title in https://github.com/AlexDarigan/WAT/commit/35149606d564b280605b119cac79d9833e8d7f44 which should have been removed instead.
Because of this, it seems that there are plans to make this an option to be displayed in future. I can definitely see the need for number of assertions passed per test method. Therefore, instead of outright removing line 26, I refactored the code for the displaying of (total/passed) to make it more apparent, easier to maintain and extend.
Fixes #306.

Thanks!


Skins

i don't know how to put skins on the replays lol

idk if u already found out but you can just select a skin above the start button

#125 settings go skins, and start button


FIX: brain add_label views parameter with pyvista

This PR fixes the views parameter passed to the camera.
Closes part of #7143

Ci failure is related ?

I don't think so.... I restarted some CIs to have a better idea

Now the 'medial' parameter is used correctly:
https://17225-1301584-gh.circle-artifacts.com/0/dev/auto_examples/inverse/plot_time_frequency_mixed_norm_inverse.html#sphx-glr-auto-examples-inverse-plot-time-frequency-mixed-norm-inverse-py
reference:
https://mne.tools/dev/auto_examples/inverse/plot_time_frequency_mixed_norm_inverse.html

One down


Mssing file_get_contents in init.php

Hi!, I was unable to get configuration from paramaters.yml as is init.php, I had to add file_get_contents function when parsing to get it work, It could be an issue, congrats!.
$app['params'] = Symfony\Component\Yaml\Yaml::parse(file_get_contents(__DIR__.'/../config/parameters.yml'));

@EXeduardo have you run composer install first?


Adding integration tests for Digest authentication

This intends to prepare Digest implementation, to prevent regressing from the current (cURL) implementation.
Note that this requires an npm install http-auth; I'm quite uneasy on how to require it: what is the usage regarding this? Should it be included in the composer, or will it be sufficient to mention this new requirement, along Node.js, on the blog?
(the RingPHP pull request https://github.com/guzzle/RingPHP/pull/14, to include Digest auth in server.js, is not dependent on this nom install: the http-auth won't be required unless the specific Digest-requiring URI is called)

OK, back to work (after some holidays, diapers occupation, and a lot of other things…).
I like your idea. So I made a new pull request on guzzle/RingPHP (to add replying with a 501), and added a commit to the (not-yet-merged) guzzle/guzzle pull request (to catch the 501 and decide to skip the test).
Hmm… I'm quite new with github, so I did reset in my outtersg/guzzle master branch (the one requested for pull) to get rid of the travis.yml "npm install" addition, before adding the (more applicative-way) HTTP-501 handling. Tell me if this breaks the pull request.

This is great. Can you rebase against master?

Still learning git (and github)… removing non-mergeable patches (before rebasing) made GitHub close the pull request (in a non-reopenable state, as it was considered merged; a 0-commit merge, but still a merge). So followup is at https://github.com/guzzle/guzzle/pull/962


Remove options struct for the deleted "get" subcommand.

This fixes the crash that I noted in #308
cc @Tatskaari @toastwaffle

@toastwaffle I think I've done that now, thanks for taking this!

Thank you for fixing this!


Store "index" in the database rather than on the file system

Builds on #296(diff)
Previously, we had been storing partially-processed parsing entries in a file-system based "index". This set of patches replaces that logic with an analogous, database-based version. It continues to use os path separators and continues to be prefixed with an irrelevant directory path, but I've reached a good stopping point. Everything should be working without any regressions. Stepping through individual changesets is probably the best approach to reviewing.

Nice work! I had comments on restructuring some comprehensions, but they're pretty minor. Merging.


Zig Concurrent solution

cc: @jinyus

RAM: 16 GiB
CPU: Ryzen 7 5700G
$ ./run.sh zig_con
Running Zig
Zig Concurrent:

        Processing time (w/o IO): 13.061ms
        total: 4.06s memory: 4808k
        Processing time (w/o IO): 12.366ms
        total: 4.21s memory: 4916k
        Processing time (w/o IO): 13.636ms
        total: 4.33s memory: 4832k
        Processing time (w/o IO): 14.693ms
        total: 4.15s memory: 4796k
        Processing time (w/o IO): 12.836ms
        total: 4.28s memory: 4928k
        Processing time (w/o IO): 13.504ms
        total: 4.25s memory: 4916k
        Processing time (w/o IO): 14.579ms
        total: 4.22s memory: 4680k
        Processing time (w/o IO): 12.617ms
        total: 4.16s memory: 4928k
        Processing time (w/o IO): 14.209ms
        total: 4.10s memory: 4832k
        Processing time (w/o IO): 13.077ms
        total: 4.21s memory: 4928k
Checking output
Success: related_posts_zig_con.json is valid!

Thanks, it seems the results are comparable. I will merge


handling field conflict

in additional to using smart comment on the constraint
comment on constraint "beverages_distributor_id_fkey" on "beverages" is
E'@foreignFieldName distributedBeverages';
can we also support smart comment on the field level?
comment on column beverages.distributor_id is '@foreignFieldName distributedBeverages';

As a shortcut for single-key relations? That seems a reasonable idea, but what would we call the forward relation part on the same column? Maybe the smart comment should be slightly different, e.g. “relationFieldName” / “relationForeignFieldName”?

I need to add a smart comment to use "products" instead of "productsByCategoryId" in the relationship one to many. Where I should add that comment? directly in postgres?
I have two tables:
products

name
categoryId

categories

name

I am trying this:
COMMENT ON CONSTRAINT "productos_categoriaId_fkey" on productos is 'categoria' .
but not works.

You’re almost there; change the ’categoria’ to ’@foreignFieldName products’ (but watch out for the smart quotes my phone added - sorry)

Yes, I have tried that, but the response is always the same and don't works.
This is the query that I run in pg Admin.

And this is my query in Graphiql.

In the second query you’re querying productosCategorias (not productos) so I’d expect constraint named something like productos_categorias_categoryId_fkey

But there is not constraint on productosCategorias table, because the fk is on productos table.

I have restarted the server and works.
Thanks!


How to set a default value of params in a rule?

I want to set a default value of one parameter under "snakemake@params". Right now, a parameter defined under "snakemake@params" is required and its value should be entered in the config.yaml. However, default values will shorten the config.yaml a lot. Could you please help suggest how to specify a default value of a parameter? Thanks.

You could do something like this:
if 'some_param' not in config:
    config['some_param'] = 'some-default-value'

rule one:
    params:
        some_param=config['some_param']

NB: Questions like this about usage of snakemake are better asked on stackoverflow

Thanks, @dariober. Your solution works perfectly. Yes, I will ask the usage questions on StackOverflow next time. Thanks.


Fix(rules): Add 'NOT_CONTAINS' as an action

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


[ROCKETMQ-340] improve code for avoid ClassCastException.

What is the purpose of the change
improve code for avoid ClassCastException
Brief changelog
sometimes  BrokerFastFailuru#castRunnable throw ClassCastException , so fix it .
improve code for avoid ClassCastException
Verifying this change
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a JIRA issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [ROCKETMQ-XXX] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[ ] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage increased (+0.07%) to 40.025% when pulling 9f0ef6d011811fc016ec94ab3c385b90f7d94643 on fuyou001:ROCKETMQ-340 into cc0b3d091814a390107b8e733dd8a5427ff49296 on apache:develop.


github action for releasing new release and adding labels to issues

🛠 Fixes issue  #173
📇 Changes proposed
Added  two github action files

Assign labels to new issues which can be used to filter issue
Automatically releases a new release whenever there is a change in code base

✅ Check List (Mark all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[ ] This PR contains changes in the documentation
[ ] This PR contains changes in the Code of the project
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers
If anything doesn't work as expected or needs to change, please give me a heads-up.

📷 Screenshots

@ptiwari6239, any updates?

@ptiwari6239 I am closing this PR as it was in the Stale period for a pretty long time, you can raise a new one


Angular 1.3 one way and ngModelOptions

Any plans to support one way binding or ngModelOptions on filters/edit boxes? Is the best method to use custom templates?

Closing, this is not in our roadmap to do.


LineChart only updates upon resizing the window

Hi guys,
I'm doing a small demo project with this library, but I ran into some issues. I update the dataset every x amount of seconds, but the changes in dataset only get applied if I resize the window.
Here's a gist of my component: https://gist.github.com/iremlopsum/98de215354e8e01ea12d4b0c8bb6b632
the result that I'm seeing is:

plus I'm getting a weird error:
Uncaught TypeError: Cannot read property 'skip' of undefined
    at parseVisibleItems (core.interaction.js:40)
    at getIntersectItems (core.interaction.js:56)
    at indexMode (core.interaction.js:106)
    at Chart.getElementsAtEventForMode (core.controller.js:595)
    at Chart.handleEvent (core.controller.js:808)
    at Chart.eventHandler (core.controller.js:766)
    at listener (core.controller.js:701)

which only happens sometimes when I hover on the graph.
Any ideas?

I'm seeing the same issue with my bar chart

I experienced the same problem when mutating the contents within state, depending on what you want to accomplish, I solved this in one of two ways.
The first, and nicest, was to make a copy of labels and temps, ie:
let temps = this.state.temps.slice();
let labels = this.state.labels.slices()

// Mutate the copy temps / labels and set them:
this.setState({ temps, labels });

but the resulting animation was not what I wanted, as it seems chart.js behaves differently when the underlying reference to data is changed versus mutated.
The second, which forces chart.js to update wrt. its mutated state, was an ugly hack which breaks with the react model:
Grab a copy of the chart component via the ref attribute:
<Line ref={child => {this._child = child;}} data={data}/>

and when you update your data, force an update by calling it directly on chart.js:
if (this._child) this._child.chartInstance.update();


Logical NOT

Starling boolean expressions should have a ! (logical NOT) operator.  This is available internally but not exposed syntactically.
It should have the same precedence as the C operator, so check the K&R grammar for how to encode it.
Motivating example: trying to fit the Peterson array proof into my PLDI paper and half the constraints are breaking into two lines: this would be the easiest quick fix.

I can do this.
On Friday, 28 October 2016, Matt Windsor<EMAIL_ADDRESS>wrote:

Starling boolean expressions should have a ! (logical NOT) operator. This
is available internally but not exposed syntactically.
It should have the same precedence as the C operator, so check the K&R
grammar for how to encode it.
Motivating example: trying to fit the Peterson array proof into my PLDI
paper and half the constraints are breaking into two lines: this would be
the easiest quick fix.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/septract/starling-tool/issues/74, or mute the thread
https://github.com/notifications/unsubscribe-auth/AANd9rBsEczvpUnB2d483mExh0HpWORyks5q4i8hgaJpZM4Kjqmi
.

--
http://www-users.cs.york.ac.uk/~miked/

@septract thanks!

Fixed in PR #77


Introducing <Meta /> Component to help users manage meta Infos

Background
#10
What changed

Introducing  Component
Adding generation of fresh-seo.config.ts which includes meta config.

Usage
1. run init.ts script
This generates fresh-seo.config.ts from user's routes/
//fresh-seo.config.ts
import { Config } from "fresh-seo";
export default {
  routes: {
    "/": {
      title: "index",
      description: "index page",
    },
    "/about": {
      title: "about",
      description: "about page",
    },
  },
} as Config;

2. Add <Meta /> and related imports to page route components
//index.ts
import { Handlers, PageProps } from "$fresh/server.ts";
import { Head } from "$fresh/runtime.ts";
import seoConfig from "../fresh-seo.config.ts";
import { MetaProps, getMetaProps } from "fresh-seo";
import Meta from "fresh-seo/components";

interface Props {
  metaProps: MetaProps;
}

export const handler: Handlers = {
  GET(req, ctx) {
    const metaProps = getMetaProps(seoConfig, req);
    return ctx.render({ metaProps });
  },
};

 export default function Home({ data }: PageProps<Props>) {
  return (
    <>

        <Meta metaProps={data.metaProps} />

     {/* body */}

    </>
  );
}

sample project with demo
Maybe this inflicts too much user effort :thinking:
What do you think?

This really brings some hassle to the user. Seems easy enough, but we gotta do something about the boilerplate code.

@notangelmario Yeah, adding 10+ line codes to every route should be a pain!
How can we avoid this?
I can't figure out how to inject stuff into the user's DOM without forcing the user to add it explicitly during the SSR

here are a few points I think we can improve on to simplify the API a little bit (this is not exhaustive, and we will require some work to find the right API here).

For the route, it's actually pass down to the page automatically via PageProps so we could use this instead of relying on the request in the handler
In your example, getMetaProps is called in the handler but can theoretically be called in the page directly, removing the need for the handler.
Config file could be loaded automatically as we know what is the path, even though I would argue against config file and use another API for that.

If we manage to do all of this, we would boiled down the example to:
import { PageProps } from "$fresh/server";

 export default function Home({ route }: PageProps) {
  return (
    <>

        <Meta route={route} />

     {/* body */}

    </>
  );
}

Even with all those optimizations, I think we still need to:

implement the <Meta /> component in every routes
pass down the current route to the component

With all of this to consider, I'm not sure if this would be useful as is. I don't think it would actually be easier if we can't allow use to.
Maybe provide a nice <Meta /> component is already a good enough feature without the centralized config file?
From what I see, there is only 1 way to make this better and both rely on making a PR to Fresh to implement additional required API.
Either Fresh provide a useRoute hooks (à la Next) to allow our <Meta /> component to access the current route without passing it down, so we can just implement it in the _app.tsx, or we have to wait until Fresh improve on the plugin system as initially stated.

@xstevenyung
Relying on the plugin system should fit more with Fresh's concise API.
So I prefer waiting for the improvement of the plugin system's utility of the render process.
Closing as the above.


Lorenz equations don't seem to work

Via http://www.intmath.com/cg5/katex-mathjax-comparison.php?processor=MathJax

Seems related to: https://github.com/Khan/KaTeX/issues/61

\begin{aligned}
\dot{x} & = \sigma(y-x) \\
\dot{y} & = \rho x - y -xz \\
\dot{z} & = -\beta z + xy
\end{aligned}

produces the following in KaTeX (not yet deployed):

I'm going to close this a duplicate of https://github.com/Khan/KaTeX/issues/61.


FINS-10137 Document readyForIntegration events

@MarcBell-SAP

@IamTitanium32 I've merged this and made a few formatting updates. Also, I've moved it to the proper folder, event-topics/Shared/external-readyforIntegration-event.markdown.


[API-Gateway] Drop usage of prow build jobs

Description
We need to drop prow build jobs in API-Gateway Github actions. Docs:
https://github.com/kyma-project/test-infra/blob/main/cmd/image-builder/README.md#quickstart-guide
See previous tasks done for PR builds (in Notes).
Motivation
Neighbours want to drop prow in favour of azure dev ops jobs.
Contact(s): @Sawthis
ToDo [Developer]

[ ] ...

PRs

[ ] ...

AC [Reviewer | PO]

[ ] API Gateway images on main and release branch are built by neighbours provided GH Action

DoD [Developer & Reviewer]

[ ] Provide unit and integration tests.
[ ] Provide documentation.
[ ] Verify if the solution works for both open-source Kyma and SAP BTP, Kyma runtime.
[ ] If you changed the resource limits, explain why it was needed.
[ ] If the default configuration of Istio Operator has been changed, you performed a manual upgrade test to verify that the change can be rolled out correctly.
[ ] Verify that your contributions don't decrease code coverage. If they do, explain why this is the case.
[ ] Add release notes.
[ ] Fix main workflow on schedule

Attachments

11711

Follow-up Issues

...

revert main workflow cause scheduled int tests are failing


Spout not working in v1.11.1, silently stuck at "beginning to run user code"

What happened?:
Hi, guys. I've redploy v1.11.1 custom pachyderm cluster then migrate spout and pipeline which runnable on v1.10.0.
the spout daemon script and pach-spout.json are as following. I also tested kafka messaging it's work well both inside and outside container but not via cmd in pach-spout.json.
acks.py (spout daemon script)
#!/usr/bin/env python
import os
import json
import time
import tarfile
import stat
import sys
import io
from confluent_kafka import KafkaError
from confluent_kafka.avro import AvroConsumer
from confluent_kafka.avro.serializer import SerializerError

__, TOPICS, GROUP_ID = sys.argv

# Get environment variables
BOOTSTRAP_SERVERS = os.getenv('BOOTSTRAP_SERVERS', "<IP_ADDRESS>:31090,<IP_ADDRESS>:31091,<IP_ADDRESS>:31092")
SCHEMA_REGISTRY_URL = os.environ.get('SCHEMA_REGISTRY_URL', "http://<IP_ADDRESS>:30553")
POLL_INTERVAL_SECONDS = float(os.environ.get('POLL_INTERVAL_SECONDS', "1.0"))
SPOUT = os.environ.get('SPOUT', "/pfs/out")

c = AvroConsumer({
    'bootstrap.servers': BOOTSTRAP_SERVERS,
    'group.id': GROUP_ID,
    'schema.registry.url': SCHEMA_REGISTRY_URL })

c.subscribe(TOPICS.split(','))

# https://stackoverflow.com/posts/17074606/revisions
def pluck(dict, *args):
    return (dict[arg] for arg in args)

def open_pipe(path_to_file, attempts=0, timeout=2, sleep_int=5):
    if attempts < timeout :
        flags = os.O_WRONLY  # Refer to "man 2 open".
        mode = stat.S_IWUSR  # This is 0o400.
        umask = 0o777 ^ mode  # Prevents always downgrading umask to 0.
        umask_original = os.umask(umask)
        try:
            file = os.open(path_to_file, flags, mode)
            # you must open the pipe as binary to prevent line-buffering problems.
            return os.fdopen(file, "wb")
        except OSError as oe:
            print ('{0} attempt of {1}; error opening file: {2}'.format(attempts + 1, timeout, oe))
            os.umask(umask_original)
            time.sleep(sleep_int)
            return open_pipe(path_to_file, attempts + 1)
        finally:
            os.umask(umask_original)
    return None

def handle_message(mesg):
  print("inside handle_message...")
  spout = open_pipe(SPOUT)
  if spout is None:
      print ('error opening file: {}'.format(SPOUT))
      exit(-2)

  # To use a tarfile object with a named pipe, you must use the "w|" mode
  # which makes it not seekable
  print("Creating tarstream...")
  try:
      tarStream = tarfile.open(fileobj=spout,mode="w|", encoding='utf-8')
  except tarfile.TarError as te:
      print('error creating tarstream: {0}'.format(te))
      exit(-2)

  key, value = mesg.key(), mesg.value()
  projectId, userId, datasetId, sampleIds, priority = pluck(key, 'projectId', 'userId', 'datasetId', 'sampleIds', 'priority')
  datasetId =  '{}_{}'.format(userId, projectId) if datasetId is None else datasetId
  keyAsJsonStr = json.dumps(key).encode('utf-8')
  valueAsJsonStr = json.dumps(value).encode('utf-8')
  datasetAsJsonStr = json.dumps({ "datasetId": datasetId, "sampleIds": sampleIds }).encode('utf-8')

  fileNames = ['key.json', 'value.json', 'dataset.json']
  contents = [keyAsJsonStr, valueAsJsonStr, datasetAsJsonStr]

  def initTarHeader(args):
    fileName, content = args
    tarHeader = tarfile.TarInfo()
    tarHeader.size = len(content)
    tarHeader.mode = 0o600
    tarHeader.name = "{}/{}/{}".format(userId, projectId, fileName)
    return tarHeader, content

  print("Writing tarfile to spout for message {}/{}...".format(userId, projectId))
  for tarHeader, content in map(initTarHeader, zip(fileNames, contents)):
    try:
        with io.BytesIO(content) as mesgAsBytes:
            tarStream.addfile(tarinfo=tarHeader, fileobj=mesgAsBytes)
    except tarfile.TarError as te:
        print('error writing message {0} to tarstream: {1}'.format(tarHeader.name, te))
        exit(-2)

  tarStream.close()
  spout.close()

if __name__ == '__main__':
  while True:
      try:
          msg = c.poll(POLL_INTERVAL_SECONDS)
      except SerializerError as e:
          print("Message deserialization failed for {}: {}".format(msg, e))
          break

      if msg is None:
          continue

      if msg.error():
          print("AvroConsumer error: {}".format(msg.error()))
          continue

      handle_message(msg)
  c.close()

pach-spout.json

  "pipeline": {
    "name": "mtb-spout"
  },
  "spout": {
    "overwrite": true
  },
  "description": "A spout pipeline that pull messages from kafka",
  "transform": {
    "cmd": [ "./acks.py", "mtb", "!@#$" ],
    "image": "sinonkt/agnostic-confluent-kafka-spout:v0.0.12",
    "env": {
      "NUM_OF_WORKERS": "3"
    },
    "secrets" : [
        {
            "name": "confluent-kafka-conf",
            "key": "BOOTSTRAP_SERVERS",
            "env_var": "BOOTSTRAP_SERVERS"
        },
        {
            "name": "confluent-kafka-conf",
            "key": "SCHEMA_REGISTRY_URL",
            "env_var": "SCHEMA_REGISTRY_URL"
        },
        {
            "name": "confluent-kafka-conf",
            "key": "POLL_INTERVAL_SECONDS",
            "env_var": "POLL_INTERVAL_SECONDS"
        }
    ],
    "image_pull_secrets": ["hub-docker-reg-sinonkt-cred"]
  },
  "pod_spec": "{\"nodeSelector\":{\"nbt/environment\":\"production\",\"nbt/nodetype\":\"fat\",\"nbt/type\":\"compute\"}}"
}

What you expected to happen?:
Spout should work on version 1.11.1
How to reproduce it (as minimally and precisely as possible)?:
follow Spout kafka example on v1.11.1 or try my script above.
Anything else we need to know?:
Environment?:

Kubernetes version (use kubectl version): 1.16.6
Pachyderm CLI and pachd server version (use pachctl version): v1.11.1
Cloud provider (e.g. aws, azure, gke) or local deployment (e.g. minikube vs dockerized k8s): on-premise k8s, custom pachyderm deployment

Hi, thanks for the heads up. We're looking into it and will get back to you soon.

@sinonkt to clarify, you're not seeing any other log messages from your code? The last thing you see is `beginning to run user code?" It looks like there's a number of log statements in your code so that likely means that your code isn't even getting started. As far as I know we haven't seen this behavior generally, spouts seem to be able to start up and run in 1.11 for other users. A few questiosn:

if you do kubectl logs one the worker pod does that show anything different?
if it's possible to exec into the worker container it might be interesting to see if there's actually a python process running in there, that'll give us some idea of where this is breaking down

@adelelopez @jdoliner Oh, my mistakes is an incorrect kafka configuration. And actually python process is running as you guessed. now spout, got messages and keep errors on kubectl logs which cause in user space code. Thank you.
it's seem like they can handle first 3 messages before error broken pipeline which is not common in 1.10.1 that quite consistent and robust. not sure is there any changed affected to how we write stdout, pfs/out. Please point me out.
*my kafka message polling intervals is 1 seconds.
*these 4 messages is almost identical.

@sinonkt I think the broken pipe issue can be resolved by keeping the pipe open the whole time, instead of closing it after each message.

@sinonkt Any luck with this?

@adelelopez So sorry for late reply, I'ven't tried yet but thank so much for your hint. i'll come back to you with the result asap.


chore(infrastructure): update React and ReactDom to 16.4.2

PointerEvents weren't full supported until v16.4.0. Tab scroller requires pointer events so updating to latest (16.4.2).
https://github.com/facebook/react/blob/master/CHANGELOG.md#1640-may-23-2018

Codecov Report

Merging #219 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #219      +/-   ##
==========================================
- Coverage    98.8%   98.78%   -0.02%
==========================================
  Files          21       21
  Lines         834      824      -10
  Branches       78       76       -2
==========================================
- Hits          824      814      -10
  Misses         10       10

Impacted Files
Coverage Δ

packages/tab-indicator/index.js
100% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Error during upload app with Beta SDK to AppStore

We cannot transfer our for testing to pilots in TestFlight, because the validator finds the wrong value for CFBundleShortVersionString

Summary:

1 package(s) were not uploaded because they had problems:
/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/6C703A03-7FDA-4D6C-8219-A62738692D52/1196876612.itmsp - Error Messages:
ERROR ITMS-90060: "This bundle is invalid. The value for key CFBundleShortVersionString '4.14-trial1' in the Info.plist file at '${bundlePath}' must be a period-separated list of at most three non-negative integers. Please find more information about CFBundleShortVersionString at https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleshortversionstring"
2020-12-23 22:32:39.867 altool[21700:69781] *** Error: Error uploading '/Users/vagrant/deploy/DroneUpApp.ipa'.
2020-12-23 22:32:39.867 altool[21700:69781] *** Error: code -18000 (ERROR ITMS-90060: "This bundle is invalid. The value for key CFBundleShortVersionString '4.14-trial1' in the Info.plist file at '${bundlePath}' must be a period-separated list of at most three non-negative integers. Please find more information about CFBundleShortVersionString at https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleshortversionstring")
Uploading IPA failed: exit status 1

Thanks for raising this bug and our team is already working on a fix.  However there is a work-a-round that is confirmed works:
Fix the short version string in the MSDK framework

Thanks. Will wait updated version

Have been fixed and tested. Thanks


Support AWS Certificate Manager as a new provider

We would like to use External Secrets to deliver certificates directly from AWS Certificate Manager. But it looks like AWS Certificate Manager is not supported as a provider now.
Can it be supported? Or maybe there is some reason why it shouldn't be?

Of course our case is not representative but we are going to deliver only certificates signed by a private CA

hmm, i'm just wonder would the cert-manager integration work for your use-case: https://github.com/cert-manager/aws-privateca-issuer ?

Thanks for suggestion! We're considering various options.
The problem is that we've used 2 cloud providers: AWS and Yandex.Cloud. Probably some new ones will be added in the future. And we would like to use a similar approach to deliver secrets and certificates from all the clouds.
We've already delivered secrets with External Secrets and like it. I plan to prepare a PR to add support for Yandex.Cloud Certificate Manager within a couple of weeks and it seems great to have an ability to take certificates from AWS Certificate Manager too.
Anyway it's not a final decision and not very critical at the moment. We keep thinking about how to be with AWS. If we decide it's important I think we could create a PR to support AWS Certificate Manager (if that is welcome)


fix: MD033/no-inline-html

Markdownlint changed the HTML regex and now flags some new elements.
These elements don't get swallowed like the others.

By convention, we're escaping non-code-fenced < characters. We're not escaping > ... unless something changed. Let's ask Scott to take a look and confirm.

Right now, the part you undid wasn't escaping the <, it was escaping the \. I just did it at the end instead of a third stacked backtick. I agree that mostly the front angle bracket is what is escaped though.

lol ..... ooooooops! ☕ ... definitely missing a cup of ☕.

This one looks ok ...
https://docs.microsoft.com/aspnet/core/host-and-deploy/iis/#application-pool-identity
I'll check the other one next.

This looks ok, too ...
https://docs.microsoft.com/aspnet/core/mvc/views/razor#inspect-the-razor-c-class-generated-for-a-view
Which change did I make tho that you think is going to break? (and keep in mind that I still haven't had another cup of :coffee: yet :smile:).

I see :eyes: what you mean ...
1. Enter **IIS AppPool\\<app_pool_name>** in **Enter the object names to select** area. Select the
**Check Names** button. For the *DefaultAppPool* check the names using **IIS
AppPool\DefaultAppPool**. When the **Check Names** button is selected, a value of
**DefaultAppPool** is indicated in the object names area. It isn't possible to enter the app
pool name directly into the object names area. Use the **IIS AppPool\\<app_pool_name>**
format when checking for the object name.

The double is making the single backslash possible.
I'll revert that and then do the triple given that we're escaping them.

ok .... I think that will work.
Let's have that ☕ now before I break something else this morning. :smile: Thanks for your patience. Scott will let me know if anything has changed WRT our repo conventions for escapes.

New version of markdownlint is out. Most of the changes went away except for a single instance that was missing the escape


filters: apply stat pattern for network filter stat prefixes

The StatName configuration for inbound and outbound is applied to cluster stats. However network filters like TCP and Redis also set the stat prefix same as cluster name today. This PR adds the stat pattern config support to network filter stat prefixes.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@ramaraochavali: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
7034a6927087484c25753df859f688fd94b69a92
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
7034a6927087484c25753df859f688fd94b69a92
link
/test lint_istio

gencheck_istio
7034a6927087484c25753df859f688fd94b69a92
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
7034a6927087484c25753df859f688fd94b69a92
link
/test gencheck_istio

lint_istio
1ec739df3e5342afebef6df81da0e6b481d5b944
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
1ec739df3e5342afebef6df81da0e6b481d5b944
link
/test lint_istio

gencheck_istio
1ec739df3e5342afebef6df81da0e6b481d5b944
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
1ec739df3e5342afebef6df81da0e6b481d5b944
link
/test gencheck_istio

lint_istio
2fab2454a2b8527215a62dcc264dcee4fc1a748c
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
2fab2454a2b8527215a62dcc264dcee4fc1a748c
link
/test lint_istio

integ-security-k8s-tests_istio
bb43878327fa3ff2395be027febe3cca420fbc33
link
/test integ-security-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-security-k8s-tests_istio

@ramaraochavali: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-local-tests_istio
bb43878327fa3ff2395be027febe3cca420fbc33
link
/test integ-local-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-local-tests_istio

@ramaraochavali: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
271934d10bd30eeb493eb49c7a46f78da3762726
link
/test integ-mixer-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


[JENKINS-73824] Add test for deleting a Pipeline job while one of its builds is running only on a OneOffExecutor

See https://github.com/jenkinsci/jenkins/pull/9790. Once I have an incremental build of that PR I will update this PR to consume it.
Testing done

Submitter checklist

[ ] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
[ ] Ensure that the pull request title represents the desired changelog entry
[ ] Please describe what you did
[ ] Link to relevant issues in GitHub or Jira
[ ] Link to relevant pull requests, esp. upstream and downstream changes
[ ] Ensure you have provided tests - that demonstrates feature works or fixes the issue

The CodeQL autobuild doesn't like the HPI plugin override (interestingly I also get this error in Netbeans, but it works fine using Maven directly):

[2024-09-27 19:27:07] [autobuild] org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
Error: 9-27 19:27:07] [autobuild] [ERROR] Unknown packaging: hpi @ org.jenkins-ci.plugins.workflow:workflow-job:${changelist}, /home/runner/work/workflow-job-plugin/workflow-job-plugin/pom.xml, line 37, column 16

I suspect that a release of https://github.com/jenkinsci/plugin-pom/pull/1004 would help, but I have not tried to investigate the issue deeply.

https://github.com/jenkins-infra/jenkins-security-scan/pull/32 FTR

Is there any reason for this to still be in draft?

Integrated into https://github.com/jenkinsci/workflow-job-plugin/pull/470 for simplicity.


bytes: align Buffer to cachelines to avoid false sharing

bytes: align Buffer to cachelines to avoid false sharing
First of all, how relevant is the problem of false sharing for bytes.Buffer?

I signed it!


Py3

Require py3
update travis

It's fine to merge, but don't see any reason to make a release until we bump the dependencies (e.g. We'll need to bump Ansible to get full python 3 support on remote hosts)


Fixes error in node travesal description

In section 6.10.2 the behavirour of traversing nodes is described incorrectly.
It is said that the AGV has to pause on an edge potentially due to a hard blocking edge.
There is no prior reference to a hard blcoking edge, but rather hard blocking actions. Furthermore the pausing should likely take place on the node rather than the edge. Particulary because it is followed by the statement that the AGV will enter the Edge after the pause, which would not be possible if the AGV was already on said edge.
Furthermore the following figure (Figure 15) illustrates a case where an AGV stops on a node until the blocking action is finished and only then proceeds to the edge.

Thank you for the comment and the pull request! We’ll discuss this briefly with the next core team meeting.
Just a heads up, the latest published version of the recommendation is always available in the main branch. We can only make changes to future versions (currently V3.0.0). @8-prime, if you could, please update your pull request to target the development branch dev/V3.0.0.


Updating BTCPayServer to v<IP_ADDRESS>

Small update. Make one test run again, before release.

@openoms I reverted back to the old version to clear another bug first. Can you second check:

When I install TOR & then BTCPayServer the server semmes running
I get a wget response on 23000
but when calling the onion address in a TOR browser there is no answere

Couldn't reproduce this. Updated the scripts and uninstalled Tor. Installed BTCPay v<IP_ADDRESS> together and after Tor too, the Hidden Service became available after a couple of seconds of returning to the main menu.

Could not reproduce this problem. I have synced and modified the latest script uninstalled Tor and reinstalled Tor + BTCPay together and then one-by-one too.
Don't see a reason in the changelog which could cause this.
v<IP_ADDRESS> working fine:

OK it looks like its something with my TOR desktop browser - BTCPAY Server is showing up on my mobile TOR browser. So we are good here.

New major BTCPay release <IP_ADDRESS> with Payjoin support (requires an other hot wallet, not tested on the blitz yet):
https://docs.btcpayserver.org/features/payjoin
https://twitter.com/BtcpayServer/status/1250853659618967553
Will test and update here.
Their LND support is still partially broken, unfortunately only works properly with LND 0.8.2 for now.
https://github.com/rootzoll/raspiblitz/issues/1104

Installation looking good on 1.5RC1 with:
https://github.com/btcpayserver/btcpayserver/releases/tag/v<IP_ADDRESS>
and
https://github.com/dgarage/NBXplorer/releases/tag/v2.1.24

Managed to generate a hot wallet and the payjoin link is available to be paid with another BTCPay wallet as described in: https://docs.btcpayserver.org/features/payjoin

OK is merged - looking for final testing on v1.5 RC2 (coming as soon as lnd 0.10.0 is out).

Test look good .. closing for v1.5 RC2 release.

https://github.com/btcpayserver/btcpayserver/releases/tag/v<IP_ADDRESS>

Merged update. TODO: One final install test.

https://github.com/rootzoll/raspiblitz/commit/05d6e644fcb9bfa54a3d82f5656054f022ac72b0


Reason syntax

@glennsl how do you want to do this? Inline before/after the ocaml snippets? Another doc page? Interactive web page?

Ideally it would be interactive (and with runnable examples!), but that'd take a bit of work (though it also gives lots of other benefits too of course). Inline would be a bit heavy and difficult to maintain I think, but a separate page shouldn't be too hard to automate.

if you're happy to have a small express server behind it, I can whip something up that serves those snippets with a toggle pretty easily (done it before)

For the toggle, couldn't we just translate them and inline them as text in the code?

depends on how you'd like to store them. if we want to ship them in the bundle, or as a bunch of files, then yes. if you want to ship them async from the server and have a smaller faster bundle, then no. I guess once you go interactive, then definitely :smile: but before then, you can just store them as .re and .ml and toggle a component that fetches the right one from the server. too complex?

or do you mean run a jsoo compiled bucklescript and literally translate them?

Some prepublish script that uses your local refmt and goes through snippets. This way the page's serverless. Though it's kinda tempting to dog food bs-express =P
Related: https://github.com/facebook/reason/pull/960

ooh, cool PR. At the point that we have the interpreter it's definitely less of an issue. Should we maybe sync up with @jaredly on updating the bucklescript jsoo version and wrapping it with a reason-react component that can render an example and a snippet? I'm happy to take a shot at prototyping something like that.

In terms of ease of maintenance, a script that reads the markdown and replaces the contents of each ```ml ``` block with the output of refmt and writes out the reason version of the document would be pretty straightforward to write and would not require a server. Sound reasonable?

Absolutely! You want to take a shot at it @zploskey ?

Sure, I'll take a shot at it over the weekend.

Would love to see this updated for Rescript 🥲

This is still very relevant for Melange, the spiritual successor to BuckleScript, I think. And there's enough differences in rescript libraries, idioms and just what's plain possible with the new syntax that it's probably best to make it a fork. If anyone's asking for my permission to do that, you certainly have it :slightly_smiling_face:


fuse example on top of new flist

use low level fuse impl on top of flist

https://pypi.python.org/pypi/llfuse/

create a filesystem which

exposes files from a chosen plist (use the metadata interface on plist)
allow read/write
files are written to ardb using https://github.com/nimscale/stor
for RW support while opening put on temp dir & only upload when file close or after certain period

in branch 8.2.0_flist_fuse

the implementation is very bad.
all is in mem as copy of capnp
this is not usable

@despiegk I thought it's an example to validate the usage of the metadata layer hence that was my main focus to validate the metadata layer usability.