Update to @types

Contains most of the changes in the types branch of @demurgos. Differences:

@demurgos' branch contained both typings and @types, which caused conflicts. I removed typings, since that was not needed any more.
@types are not used in the tests any more. TypeScript would automatically pick up these files, which broke several tests in @demurgos' branch.

Hi,
I was able to install and successfully run all the tests from your branch without any error.
Unfortunately, looks like it created conflicts with my dependant project (your definitions for Node were leaking and caused a conflict with my own). I'm taking a look at it, I'll try to set up a minimal repo demonstrating my problem.

It might be necessary to mark @types/node as a devDependency. Then consumers should install the types for node themselves, but they probably already need to do that. The definition will then never conflict with any other installation.

Here is a demo project using gulp-typescript to generate other gulp tasks.
Before running the following commands, I checked-out your branch types, ran npm install, npm test (no error) and npm link so I'll be able to test it with my own project.
$ git clone https://github.com/demurgos/gulp-ts-types.git
$ cd gulp-ts-types
$ npm install && typings install
$ tsc
node_modules/gulp-typescript/release/main.d.ts(1,1): error TS6053: File '/home/demurgos/projects/test/gulp-ts-types/node_modules/gulp-typescript/typings/tsd.d.ts' not found.

(this is the error we're trying to solve)
Now, I link it with the branch types of gulp-typescript:
$ npm link gulp-typescript
/home/demurgos/projects/test/gulp-ts-types/node_modules/gulp-typescript -> /usr/lib/node_modules/gulp-typescript -> /home/demurgos/projects/others/gulp-typescript
$ tsc
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(102,6): error TS2300: Duplicate identifier 'BufferEncoding'.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(547,9): error TS2502: 'BuffType' is referenced directly or indirectly in its own type annotation.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(548,9): error TS2502: 'SlowBuffType' is referenced directly or indirectly in its own type annotation.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(549,26): error TS2300: Duplicate identifier 'Buffer'.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(549,50): error TS2300: Duplicate identifier 'SlowBuffer'.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(570,18): error TS2300: Duplicate identifier 'EventEmitter'.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(611,22): error TS2320: Interface 'Server' cannot simultaneously extend types 'Server' and 'EventEmitter'.
  Named property 'addListener' of types 'Server' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(611,22): error TS2320: Interface 'Server' cannot simultaneously extend types 'Server' and 'EventEmitter'.
  Named property 'emit' of types 'Server' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(611,22): error TS2320: Interface 'Server' cannot simultaneously extend types 'Server' and 'EventEmitter'.
  Named property 'on' of types 'Server' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(611,22): error TS2320: Interface 'Server' cannot simultaneously extend types 'Server' and 'EventEmitter'.
  Named property 'once' of types 'Server' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(611,22): error TS2320: Interface 'Server' cannot simultaneously extend types 'Server' and 'EventEmitter'.
  Named property 'prependListener' of types 'Server' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(611,22): error TS2320: Interface 'Server' cannot simultaneously extend types 'Server' and 'EventEmitter'.
  Named property 'prependOnceListener' of types 'Server' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(611,22): error TS2320: Interface 'Server' cannot simultaneously extend types 'Server' and 'EventEmitter'.
  Named property 'removeListener' of types 'Server' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(623,22): error TS2320: Interface 'ServerResponse' cannot simultaneously extend types 'Writable' and 'EventEmitter'.
  Named property 'addListener' of types 'Writable' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(623,22): error TS2320: Interface 'ServerResponse' cannot simultaneously extend types 'Writable' and 'EventEmitter'.
  Named property 'emit' of types 'Writable' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(623,22): error TS2320: Interface 'ServerResponse' cannot simultaneously extend types 'Writable' and 'EventEmitter'.
  Named property 'on' of types 'Writable' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(623,22): error TS2320: Interface 'ServerResponse' cannot simultaneously extend types 'Writable' and 'EventEmitter'.
  Named property 'once' of types 'Writable' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(623,22): error TS2320: Interface 'ServerResponse' cannot simultaneously extend types 'Writable' and 'EventEmitter'.
  Named property 'prependListener' of types 'Writable' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(623,22): error TS2320: Interface 'ServerResponse' cannot simultaneously extend types 'Writable' and 'EventEmitter'.
  Named property 'prependOnceListener' of types 'Writable' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(623,22): error TS2320: Interface 'ServerResponse' cannot simultaneously extend types 'Writable' and 'EventEmitter'.
  Named property 'removeListener' of types 'Writable' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(653,22): error TS2320: Interface 'ClientRequest' cannot simultaneously extend types 'Writable' and 'EventEmitter'.
  Named property 'addListener' of types 'Writable' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(653,22): error TS2320: Interface 'ClientRequest' cannot simultaneously extend types 'Writable' and 'EventEmitter'.
  Named property 'emit' of types 'Writable' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(653,22): error TS2320: Interface 'ClientRequest' cannot simultaneously extend types 'Writable' and 'EventEmitter'.
  Named property 'on' of types 'Writable' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(653,22): error TS2320: Interface 'ClientRequest' cannot simultaneously extend types 'Writable' and 'EventEmitter'.
  Named property 'once' of types 'Writable' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(653,22): error TS2320: Interface 'ClientRequest' cannot simultaneously extend types 'Writable' and 'EventEmitter'.
  Named property 'prependListener' of types 'Writable' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(653,22): error TS2320: Interface 'ClientRequest' cannot simultaneously extend types 'Writable' and 'EventEmitter'.
  Named property 'prependOnceListener' of types 'Writable' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(653,22): error TS2320: Interface 'ClientRequest' cannot simultaneously extend types 'Writable' and 'EventEmitter'.
  Named property 'removeListener' of types 'Writable' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(679,22): error TS2320: Interface 'IncomingMessage' cannot simultaneously extend types 'Readable' and 'EventEmitter'.
  Named property 'addListener' of types 'Readable' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(679,22): error TS2320: Interface 'IncomingMessage' cannot simultaneously extend types 'Readable' and 'EventEmitter'.
  Named property 'emit' of types 'Readable' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(679,22): error TS2320: Interface 'IncomingMessage' cannot simultaneously extend types 'Readable' and 'EventEmitter'.
  Named property 'on' of types 'Readable' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(679,22): error TS2320: Interface 'IncomingMessage' cannot simultaneously extend types 'Readable' and 'EventEmitter'.
  Named property 'once' of types 'Readable' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(679,22): error TS2320: Interface 'IncomingMessage' cannot simultaneously extend types 'Readable' and 'EventEmitter'.
  Named property 'prependListener' of types 'Readable' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(679,22): error TS2320: Interface 'IncomingMessage' cannot simultaneously extend types 'Readable' and 'EventEmitter'.
  Named property 'prependOnceListener' of types 'Readable' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(679,22): error TS2320: Interface 'IncomingMessage' cannot simultaneously extend types 'Readable' and 'EventEmitter'.
  Named property 'removeListener' of types 'Readable' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(733,18): error TS2300: Duplicate identifier 'Agent'.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(791,18): error TS2300: Duplicate identifier 'Worker'.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(1342,22): error TS2320: Interface 'REPLServer' cannot simultaneously extend types 'Interface' and 'ReadLine'.
  Named property 'pause' of types 'Interface' and 'ReadLine' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(1342,22): error TS2320: Interface 'REPLServer' cannot simultaneously extend types 'Interface' and 'ReadLine'.
  Named property 'resume' of types 'Interface' and 'ReadLine' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(1377,17): error TS2300: Duplicate identifier 'CompleterResult'.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(1414,18): error TS2300: Duplicate identifier 'Script'.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(3004,22): error TS2420: Class 'Readable' incorrectly implements interface 'ReadableStream'.
  Types of property 'pause' are incompatible.
    Type '() => Readable' is not assignable to type '{ (): ReadableStream; (): void; }'.
      Type 'Readable' is not assignable to type 'ReadableStream'.
        Property 'isPaused' is missing in type 'Readable'.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(3170,22): error TS2420: Class 'Duplex' incorrectly implements interface 'ReadWriteStream'.
  Types of property 'pause' are incompatible.
    Type '() => Duplex' is not assignable to type '() => ReadWriteStream'.
      Type 'Duplex' is not assignable to type 'ReadWriteStream'.
        Property 'isPaused' is missing in type 'Duplex'.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(3191,22): error TS2420: Class 'Transform' incorrectly implements interface 'ReadWriteStream'.
  Types of property 'pause' are incompatible.
    Type '() => Transform' is not assignable to type '() => ReadWriteStream'.
      Type 'Transform' is not assignable to type 'ReadWriteStream'.
        Property 'isPaused' is missing in type 'Transform'.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(3216,5): error TS2309: An export assignment cannot be used in a module with other exported elements.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(3299,5): error TS2300: Duplicate identifier 'export='.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(3321,18): error TS2300: Duplicate identifier 'Domain'.
typings/globals/node/index.d.ts(176,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'cache' must be of type 'any', but here has type '{ [filename: string]: NodeModule; }'.
typings/globals/node/index.d.ts(177,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'extensions' must be of type 'any', but here has type 'NodeExtensions'.
typings/globals/node/index.d.ts(202,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'parent' must be of type 'any', but here has type 'NodeModule'.
typings/globals/node/index.d.ts(205,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'children' must be of type 'any[]', but here has type 'NodeModule[]'.
typings/globals/node/index.d.ts(238,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'Console' must be of type '{ new (stdout: WritableStream, stderr?: WritableStream): Console; prototype: Console; }', but here has type 'new (stdout: WritableStream) => Console'.
typings/globals/node/index.d.ts(244,6): error TS2300: Duplicate identifier 'BufferEncoding'.
typings/globals/node/index.d.ts(252,13): error TS2403: Subsequent variable declarations must have the same type.  Variable 'Buffer' must be of type '{ new (str: string, encoding?: string): Buffer; new (size: number): Buffer; new (array: Uint8Arra...', but here has type '{ new (str: string, encoding?: string): Buffer; new (size: number): Buffer; new (array: Uint8Arra...'.
typings/globals/node/index.d.ts(386,5): error TS2403: Subsequent variable declarations must have the same type.  Variable 'errno' must be of type 'string', but here has type 'number'.
typings/globals/node/index.d.ts(469,5): error TS2403: Subsequent variable declarations must have the same type.  Variable 'env' must be of type 'any', but here has type '{ [key: string]: string; PATH: string; }'.
typings/globals/node/index.d.ts(474,5): error TS2687: All declarations of 'exitCode' must have identical modifiers.
typings/globals/node/index.d.ts(482,5): error TS2403: Subsequent variable declarations must have the same type.  Variable 'versions' must be of type 'ProcessVersions', but here has type '{ http_parser: string; node: string; v8: string; ares: string; uv: string; zlib: string; openssl:...'.
typings/globals/node/index.d.ts(673,24): error TS2300: Duplicate identifier 'Buffer'.
typings/globals/node/index.d.ts(673,48): error TS2300: Duplicate identifier 'SlowBuffer'.
typings/globals/node/index.d.ts(694,16): error TS2300: Duplicate identifier 'EventEmitter'.
typings/globals/node/index.d.ts(694,16): error TS2420: Class 'EventEmitter' incorrectly implements interface 'NodeJS.EventEmitter'.
  Property 'prependListener' is missing in type 'EventEmitter'.
typings/globals/node/index.d.ts(730,5): error TS2403: Subsequent variable declarations must have the same type.  Variable 'port' must be of type 'number', but here has type 'string | number'.
typings/globals/node/index.d.ts(735,5): error TS2403: Subsequent variable declarations must have the same type.  Variable 'headers' must be of type '{ [key: string]: any; }', but here has type 'OutgoingHeaders'.
typings/globals/node/index.d.ts(804,5): error TS2403: Subsequent variable declarations must have the same type.  Variable 'headers' must be of type 'any', but here has type 'IncomingHeaders'.
typings/globals/node/index.d.ts(806,5): error TS2403: Subsequent variable declarations must have the same type.  Variable 'trailers' must be of type 'any', but here has type 'IncomingHeaders'.
typings/globals/node/index.d.ts(807,5): error TS2403: Subsequent variable declarations must have the same type.  Variable 'rawTrailers' must be of type 'any', but here has type 'string[]'.
typings/globals/node/index.d.ts(848,16): error TS2300: Duplicate identifier 'Agent'.
typings/globals/node/index.d.ts(890,5): error TS2403: Subsequent variable declarations must have the same type.  Variable 'addressType' must be of type 'number | "udp4" | "udp6"', but here has type 'string'.
typings/globals/node/index.d.ts(893,16): error TS2300: Duplicate identifier 'Worker'.
typings/globals/node/index.d.ts(1066,5): error TS2403: Subsequent variable declarations must have the same type.  Variable 'SNICallback' must be of type '(servername: string, cb: (err: Error, ctx: SecureContext) => any) => any', but here has type '(servername: string) => any'.
typings/globals/node/index.d.ts(1070,5): error TS2403: Subsequent variable declarations must have the same type.  Variable 'pfx' must be of type 'any', but here has type 'string | Buffer'.
typings/globals/node/index.d.ts(1071,5): error TS2403: Subsequent variable declarations must have the same type.  Variable 'key' must be of type 'any', but here has type 'string | Buffer'.
typings/globals/node/index.d.ts(1073,5): error TS2403: Subsequent variable declarations must have the same type.  Variable 'cert' must be of type 'any', but here has type 'string | Buffer'.
typings/globals/node/index.d.ts(1074,5): error TS2403: Subsequent variable declarations must have the same type.  Variable 'ca' must be of type 'any', but here has type 'string | Buffer | (string | Buffer)[]'.
typings/globals/node/index.d.ts(1175,20): error TS2300: Duplicate identifier 'CompleterResult'.
typings/globals/node/index.d.ts(1222,16): error TS2300: Duplicate identifier 'Script'.
typings/globals/node/index.d.ts(2011,14): error TS2403: Subsequent variable declarations must have the same type.  Variable 'StringDecoder' must be of type 'new (encoding?: string) => NodeStringDecoder', but here has type 'new (encoding: string) => NodeStringDecoder'.
typings/globals/node/index.d.ts(2026,5): error TS2403: Subsequent variable declarations must have the same type.  Variable 'port' must be of type 'number', but here has type 'string | number'.
typings/globals/node/index.d.ts(2027,5): error TS2403: Subsequent variable declarations must have the same type.  Variable 'pfx' must be of type 'string | Buffer[]', but here has type 'string | Buffer'.
typings/globals/node/index.d.ts(2028,5): error TS2403: Subsequent variable declarations must have the same type.  Variable 'key' must be of type 'string | any[] | string[] | Buffer', but here has type 'string | Buffer'.
typings/globals/node/index.d.ts(2030,5): error TS2403: Subsequent variable declarations must have the same type.  Variable 'cert' must be of type 'string | string[] | Buffer | Buffer[]', but here has type 'string | Buffer'.
typings/globals/node/index.d.ts(2031,5): error TS2403: Subsequent variable declarations must have the same type.  Variable 'ca' must be of type 'string | string[] | Buffer | Buffer[]', but here has type 'string | Buffer | (string | Buffer)[]'.
typings/globals/node/index.d.ts(2034,5): error TS2403: Subsequent variable declarations must have the same type.  Variable 'honorCipherOrder' must be of type 'boolean', but here has type 'any'.
typings/globals/node/index.d.ts(2037,5): error TS2403: Subsequent variable declarations must have the same type.  Variable 'NPNProtocols' must be of type 'string[] | Buffer', but here has type '(string | Buffer)[]'.
typings/globals/node/index.d.ts(2038,5): error TS2403: Subsequent variable declarations must have the same type.  Variable 'SNICallback' must be of type '(servername: string, cb: (err: Error, ctx: SecureContext) => any) => any', but here has type '(servername: string) => any'.
typings/globals/node/index.d.ts(2043,5): error TS2403: Subsequent variable declarations must have the same type.  Variable 'port' must be of type 'number', but here has type 'string | number'.
typings/globals/node/index.d.ts(2046,5): error TS2403: Subsequent variable declarations must have the same type.  Variable 'key' must be of type 'string | string[] | Buffer | Buffer[]', but here has type 'string | Buffer'.
typings/globals/node/index.d.ts(2048,5): error TS2403: Subsequent variable declarations must have the same type.  Variable 'cert' must be of type 'string | string[] | Buffer | Buffer[]', but here has type 'string | Buffer'.
typings/globals/node/index.d.ts(2091,5): error TS2403: Subsequent variable declarations must have the same type.  Variable 'key' must be of type 'string | Buffer', but here has type 'string | string[] | Buffer | { pem: string; passphrase: string; }[]'.
typings/globals/node/index.d.ts(2196,5): error TS2403: Subsequent variable declarations must have the same type.  Variable 'padding' must be of type 'number', but here has type 'any'.
typings/globals/node/index.d.ts(2201,5): error TS2403: Subsequent variable declarations must have the same type.  Variable 'padding' must be of type 'number', but here has type 'any'.
typings/globals/node/index.d.ts(2220,16): error TS2420: Class 'Readable' incorrectly implements interface 'ReadableStream'.
  Types of property 'pause' are incompatible.
    Type '() => void' is not assignable to type '{ (): ReadableStream; (): void; }'.
      Type 'void' is not assignable to type 'ReadableStream'.
typings/globals/node/index.d.ts(2258,16): error TS2420: Class 'Duplex' incorrectly implements interface 'ReadWriteStream'.
  Types of property 'pause' are incompatible.
    Type '() => void' is not assignable to type '() => ReadWriteStream'.
      Type 'void' is not assignable to type 'ReadWriteStream'.
typings/globals/node/index.d.ts(2272,16): error TS2420: Class 'Transform' incorrectly implements interface 'ReadWriteStream'.
  Types of property 'pause' are incompatible.
    Type '() => void' is not assignable to type '() => ReadWriteStream'.
      Type 'void' is not assignable to type 'ReadWriteStream'.
typings/globals/node/index.d.ts(2366,3): error TS2300: Duplicate identifier 'export='.
typings/globals/node/index.d.ts(2388,16): error TS2300: Duplicate identifier 'Domain'.

As you can see, your internal definitions are leaking and conflicting with my owns. This is pretty bad: this means that it might collide not only with my local definitions but also with the definitions of my other dependencies! I am currently using typings to get my dependencies, but for completeness I also checked with tsd (see the branch tsd):
$ tsc
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(102,6): error TS2300: Duplicate identifier 'BufferEncoding'.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(263,18): error TS2300: Duplicate identifier 'EventEmitter'.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(547,9): error TS2502: 'BuffType' is referenced directly or indirectly in its own type annotation.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(548,9): error TS2502: 'SlowBuffType' is referenced directly or indirectly in its own type annotation.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(549,26): error TS2300: Duplicate identifier 'Buffer'.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(549,50): error TS2300: Duplicate identifier 'SlowBuffer'.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(570,18): error TS2300: Duplicate identifier 'EventEmitter'.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(733,18): error TS2300: Duplicate identifier 'Agent'.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(791,18): error TS2300: Duplicate identifier 'Worker'.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(1377,17): error TS2300: Duplicate identifier 'CompleterResult'.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(1414,18): error TS2300: Duplicate identifier 'Script'.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(1796,22): error TS2320: Interface 'Server' cannot simultaneously extend types 'Socket' and 'EventEmitter'.
  Named property 'removeListener' of types 'Socket' and 'EventEmitter' are not identical.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(2320,18): error TS2451: Cannot redeclare block-scoped variable 'constants'.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(2550,18): error TS2300: Duplicate identifier 'TLSSocket'.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(2861,10): error TS2300: Duplicate identifier 'Utf8AsciiLatin1Encoding'.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(2862,10): error TS2300: Duplicate identifier 'HexBase64Latin1Encoding'.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(2863,10): error TS2300: Duplicate identifier 'Utf8AsciiBinaryEncoding'.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(2864,10): error TS2300: Duplicate identifier 'HexBase64BinaryEncoding'.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(2865,10): error TS2300: Duplicate identifier 'ECDHKeyFormat'.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(3216,5): error TS2300: Duplicate identifier 'export='.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(3299,5): error TS2300: Duplicate identifier 'export='.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(3321,18): error TS2300: Duplicate identifier 'Domain'.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(3613,5): error TS2300: Duplicate identifier 'export='.
../../others/gulp-typescript/node_modules/@types/node/index.d.ts(3639,5): error TS2300: Duplicate identifier 'export='.
typings/node/node.d.ts(87,6): error TS2300: Duplicate identifier 'BufferEncoding'.
typings/node/node.d.ts(243,18): error TS2300: Duplicate identifier 'EventEmitter'.
typings/node/node.d.ts(530,26): error TS2300: Duplicate identifier 'Buffer'.
typings/node/node.d.ts(530,50): error TS2300: Duplicate identifier 'SlowBuffer'.
typings/node/node.d.ts(551,18): error TS2300: Duplicate identifier 'EventEmitter'.
typings/node/node.d.ts(714,18): error TS2300: Duplicate identifier 'Agent'.
typings/node/node.d.ts(772,18): error TS2300: Duplicate identifier 'Worker'.
typings/node/node.d.ts(1358,22): error TS2300: Duplicate identifier 'CompleterResult'.
typings/node/node.d.ts(1398,18): error TS2300: Duplicate identifier 'Script'.
typings/node/node.d.ts(2291,22): error TS2451: Cannot redeclare block-scoped variable 'constants'.
typings/node/node.d.ts(2646,18): error TS2300: Duplicate identifier 'TLSSocket'.
typings/node/node.d.ts(3020,10): error TS2300: Duplicate identifier 'Utf8AsciiLatin1Encoding'.
typings/node/node.d.ts(3021,10): error TS2300: Duplicate identifier 'HexBase64Latin1Encoding'.
typings/node/node.d.ts(3022,10): error TS2300: Duplicate identifier 'Utf8AsciiBinaryEncoding'.
typings/node/node.d.ts(3023,10): error TS2300: Duplicate identifier 'HexBase64BinaryEncoding'.
typings/node/node.d.ts(3024,10): error TS2300: Duplicate identifier 'ECDHKeyFormat'.
typings/node/node.d.ts(3375,5): error TS2300: Duplicate identifier 'export='.
typings/node/node.d.ts(3458,5): error TS2300: Duplicate identifier 'export='.
typings/node/node.d.ts(3480,18): error TS2300: Duplicate identifier 'Domain'.
typings/node/node.d.ts(3772,5): error TS2300: Duplicate identifier 'export='.
typings/node/node.d.ts(3798,5): error TS2300: Duplicate identifier 'export='.

I also tried with @types (see the branch types) and it worked. I'm still confused about it: we both used the exact same file in @types: what would happen when Node 7.x is released and I update my definitions before you do. Will my definitions conflict with yours internal ones ?
Finally, I know that @types is out now, but I'm not sure that a dependency should dictate the definition manager to use (or at least not right now when @types is only a few weeks old). As I told you in the related issue, you can use whatever definition manager you want, but for the moment I'd prefer to keep typings for my top project for various reasons so it would be fine if using your library did not break it. :s
I may also have made a mistake in my configuration so it may be possible to make it work with tsd or typings while your packages uses @types, in this case, could you please check what should be changed ?

It might be necessary to mark @types/node as a devDependency. Then consumers should install the types for node themselves, but they probably already need to do that. The definition will then never conflict with any other installation.

This may solve the issue: it seems that this is what Angular is using.

I'm pretty sure that making Node a devDependency will solve all issues. The other type definitions will never conflict with any other version of the package, since these can be installed multiple times without problems. However, that's not the case for Node since these types are declared like declare module "fs" { .. } (I guess they are called 'global' definitions), and they will pollute the global namespace. So a consumer of gulp-typescript would then only need to install the types for Node manually, all other types will be loaded automatically.

I think that you are right. I asked how @types/node should be install (dependency or devDependency) on the types-publisher repo (https://github.com/Microsoft/types-publisher/issues/173), we should get an answer soon.

I was looking for a source confirming that the way to go is to use devDependencies, I think that I got it: Typescript itself is adding it as a devDependency.

Hi!
I got an answer:

My thought is dependencies since you're written as a library with dependents. For any users using Typings with TypeScript 1.8 and below, they shouldn't be affected, but as you noted, 2.0+ users may run into problems (at which point the solution is trivial - just remove node from their typings.json - but still annoying).

So keep it in dependencies, and I'll update my build to use @type/node and typings for the rest.
I think that this means that you can merge the current branch.

Once you have accepted this PR, could you publish your package to npm ?

Yes, will create a new release then. Though I'm still afraid that this would break a lot of users, so replied to Microsoft/types-publisher#81, asking about possible conflicts.


Tensorflow Keras Conv3D op support

Hello,
We've been testing the conversion of a Tensorflow Keras model with a custom layer and some 3D convolution and 3D Average Pooling layers to ONNX using the master branch version of keras2onnx, but the following warnings are shown:
WARN: No corresponding ONNX op matches the tf.op node Umonna_Unit_LST_LSTCam/conv3d_8/Conv3D of type Conv3D
      The generated ONNX model needs run with the custom op supports.
WARN: No corresponding ONNX op matches the tf.op node Umonna_Unit_LST_LSTCam/average_pooling3d_3/AvgPool3D of type AvgPool3D
      The generated ONNX model needs run with the custom op supports.

Will Tensorflow Conv3D and AvgPool3D ops be supported anytime soon? Or maybe, is there any workaround to this problem?
Thanks!

+1

I am afraid that Conv3D and AvgPool3D ops are not supported in near future. It seems to me that onnx Conv op is designed for 1D or 2D, not for 3D.

After reading the operator schemas documentaton, I get the impression that ONNX supports n-dimensional convs:

Input data tensor from previous layer; has size (N x C x H x W), where N is the batch size, C is the number of channels, and H and W are the height and width. Note that this is for the 2D image. Otherwise the size is (N x C x D1 x D2 ... x Dn).

I would also appreciate Conv3D and AvgPool3D support.

After reading the operator schemas documentaton, I get the impression that ONNX supports n-dimensional convs:

Input data tensor from previous layer; has size (N x C x H x W), where N is the batch size, C is the number of channels, and H and W are the height and width. Note that this is for the 2D image. Otherwise the size is (N x C x D1 x D2 ... x Dn).

I would also appreciate Conv3D and AvgPool3D support.

in an effort to not appear insane: there was a comment, which indicated that ONNX does only support 1D and 2D operations. Lesson learned, use the reply function ...

Just checked in Conv3D support, please pull latest keras2onnx master and try.
Not sure if I have time do AvgPool3D soon, can you write model using keras layer?

Keras-onnx now converts a model with conv3d and avgpooling3d successfully. The results appear to be correct.
@jiafatom thank you very much!


Color-stop as list

I was trying to write a linear-gradient mixin that will take the first color stop and set it as the background color. However SASS recognizes my list as a set of color-stops so I can't access the first element with the nth function:
$colorStopsList: (#fff 20%, #f6f6f6 50%, #eee 50%, #f4f4f4 100%);
$colorStop: nth($colorStops, 1): //Type-of: compass::sassextensions::functions::gradientsupport::colorstop
//$colorStop: #fff 20%
background-color: type-of(nth($colorStop, 1)); //Returns #fff 20%, where #fff was expected

I don't know if this is a Compass issue or a Sass issue...

Just wanted to make sure it didn't fall through the cracks.


clientv3: use grpc codes to translate raw grpc errors

I was debugging unexpected ErrClientConnClosing error from gRPC in txn write fail tests. Would this affect that code path?

Yes, but it's still triggering the failure according to semaphore. I was hoping the tighter error handling in the client would fix the problem.

Yeah this approach looks good. LGTM.
Defer to @xiang90
Thanks!

@heyitsanthony Do we know the root cause of https://github.com/coreos/etcd/issues/6238?

lgtm

Got CI passing. I think this now fixes #6238 PTAL /cc @gyuho

LGTM. Thanks!


HttpUrlCondition extracted

SonarQube analysis reported 2 issues

 2 info

Watch the comments in this conversation to review them.
1 extra issue
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 PathQueryCondition.kt#L7: Line detected that is longer than the defined maximum line length in the code style.


Split atlas_reader.create_output function into multiple funcs

The create_output() function is rather sizeable and aims to do multiple things, including running the cluster analyses, generating the output CSV file, and creating the cluster map images; it would be great to split it up a bit to improve modularity and ease testing and readability! In my mind those could be three functions (at least!), something like:

gen_cluster_df(), which does most of the work (wrapping the first part of the function)
save_table(), which outputs the CSV file (and maybe other table formats, like LaTeX, as desired)
save_cluster_images(), which outputs the cluster map images (allowing more control over image formatting!)

I'm happy to discuss the best mechanism for doing this, but would love to see it chopped up a bit before proceeding too far.

Perfect! Yes, save_table and save_cluster_images should be clearly separated from the main function.


Bug 3451383

Consolidated changes into this pull request: https://github.com/OfficeDev/Office-Addin-Scripts/pull/150


Commands that intentended to be in multiple line, were shown in a single line

Because of using > (quote) instead of   (code), multi-line commands were shown in a single line that may confuse some people.

Good change, thank you!


Mysql grants delete old grants when adding an extra grant

Hello!

Vote on this issue by adding a 👍 reaction
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already)

Issue details
When adding a grant with pulumi-mysql like this:
mysql.Grant(f"mysql-grant-{username}",
        database="*",
        user=username,
        host="%",
        privileges=[
            "SELECT",
            "INSERT",
            "UPDATE",
            "DELETE",
            "CREATE",
            "ALTER",
            "INDEX",
            "REFERENCES",
            "PROCESS"
        ],
        opts=pulumi.ResourceOptions(provider=mysql_provider, parent=user)
    )

and adding an extra privilege later all the priviliges set before the update will be removed.
Steps to reproduce

create a privilege set see above.
add another privilege to the list.

pulumi output:
pulumi:pulumi:Stack: (same)
    [urn=urn:pulumi:prod::accounting::pulumi:pulumi:Stack::accounting-prod]
    > pulumi:pulumi:StackReference: (read)
        [id=buckaroo/prod-v1/prod]
        [urn=urn:pulumi:prod::accounting::pulumi:pulumi:StackReference::buckaroo/prod-v1/prod]
        name: "buckaroo/prod-v1/prod"
        ++mysql:index/grant:Grant: (create-replacement)
            [id=iam_admin@%:*]
            [urn=urn:pulumi:prod::accounting::mysql:index/user:User$mysql:index/grant:Grant::mysql-grant-iam_admin]
            [provider=urn:pulumi:prod::accounting::pulumi:providers:mysql::accounting-prod-rds-root-provider::9efc35f9-e93e-4cf7-8d8b-c53456753faa]
          ~ privileges: [
                [0]: <null>
                [1]: <null>
                [2]: <null>
                [3]: <null>
                [4]: <null>
                [5]: <null>
                [6]: <null>
                [7]: <null>
              + [8]: "PROCESS"
            ]
        +-mysql:index/grant:Grant: (replace)
            [id=iam_admin@%:*]
            [urn=urn:pulumi:prod::accounting::mysql:index/user:User$mysql:index/grant:Grant::mysql-grant-iam_admin]
            [provider=urn:pulumi:prod::accounting::pulumi:providers:mysql::accounting-prod-rds-root-provider::9efc35f9-e93e-4cf7-8d8b-c53456753faa]
          ~ privileges: [
                [0]: <null>
                [1]: <null>
                [2]: <null>
                [3]: <null>
                [4]: <null>
                [5]: <null>
                [6]: <null>
                [7]: <null>
              + [8]: "PROCESS"
            ]
        --outputs:--

Expected: A privilege added but initial privileges intact
Actual: old priviliges removed, new privilige added.

@stack72 While not directly related to the bug described above, I wonder if it would make sense to have this provider track https://github.com/winebarrel/terraform-provider-mysql instead? It's continuing to be updated (vs. the current upstream which is in archive mode) and has added functionality such as https://github.com/winebarrel/terraform-provider-mysql/pull/20 to support updating grants vs. having to replace them.

👍
Currently we have to work around this by using a opts=ResourceOptions(replace_on_changes=["privileges"]), but i have to hope this is not intended.

This issue has been fixed and does not reproduce with latest provider and pulumi binaries.


Release v1.0.3 on the Chrome WebStore

Currently on the Chrome WebStore has version 1.0.2 but in GitHub there is 1.0.3 that will open links in a new window, can this be update on the Chrome WebStore?
Thanks,

Version: 1.1 in chrome webstore. Issue could be closed.

We should also tag releases for easy diffing.
It would be great.

Closing in favor of #18


DNS Change detail notices

Changes in this pull request:

Add configurable notices to the DNS Change detail page based on the DNS Change status. The notices are intended to give users additional context about the state of their DNS Change.
Config key is "dnsChangeNotices" and requires a list. The list can be empty or contain objects with the attributes: "status", "text", "alertType", "href" (optional), "hrefText" (optional).
status is matched against our current list of valid batch change statuses: Cancelled, Complete, Failed, PartialFailure, PendingProcessing, PendingReview, Rejected, Scheduled. If the given status doesn't match we set the status to "Unknown". This determines which notice appears on which DNS Change.
alertType is matched against a list of valid Bootstrap 3 alert types: info, success, danger, warning. If the given alertType doesn't match we set the alertType to "info". This sets the styling of the notice.
If included, the "href" and "hrefText" will appear after the given "text" value in the notice message.

Documentation Note: will include documentation updates in this PR, but will wait for feedback to confirm the configuration.
Screenshots of the different style notices based on "alertType":
info alertType:

success alertType:

warning alertType:

danger alertType:

updated this PR description to include screenshots of the different notice styles based on the given alertTtype in the config.


IterableDataset strange deadlock

Describe the bug
import datasets
import torch.utils.data

num_shards = 1024

def gen(shards):
    for shard in shards:
        if shard < 25:
            yield {"shard": shard}

def main():
    dataset = datasets.IterableDataset.from_generator(
        gen,
        gen_kwargs={"shards": list(range(num_shards))},
    )
    dataset = dataset.shuffle(buffer_size=1)
    dataset = datasets.interleave_datasets(
        [dataset, dataset], probabilities=[1, 0], stopping_strategy="all_exhausted"
    )
    dataset = dataset.shuffle(buffer_size=1)

    dataloader = torch.utils.data.DataLoader(
        dataset,
        batch_size=8,
        num_workers=8,
    )

    for i, batch in enumerate(dataloader):
        print(batch)
        if i >= 10:
            break
    print()

if __name__ == "__main__":
    for _ in range(100):
        main()

Steps to reproduce the bug
Running the script above, at some point it will freeze.

Changing num_shards from 1024 to 25 avoids the issue
Commenting out the final shuffle avoids the issue
Commenting out the interleave_datasets call avoids the issue

As an aside, if you comment out just the final shuffle, the output from interleave_datasets is not shuffled at all even though there's the shuffle before it. So something about that shuffle config is not being propagated to interleave_datasets.
Expected behavior
The script should not freeze.
Environment info

datasets version: 3.0.0
Platform: macOS-14.6.1-arm64-arm-64bit
Python version: 3.12.5
huggingface_hub version: 0.24.7
PyArrow version: 17.0.0
Pandas version: 2.2.2
fsspec version: 2024.6.1

I observed this with 2.21.0 initially, then tried upgrading to 3.0.0 and could still repro.

Yes interleave_datasets seems to have an issue with shuffling, could you open a new issue on this ?
Then regarding the deadlock, it has to do with interleave_dataset with probabilities=[1, 0] with workers that may contain an empty dataset in first position (it can be empty since you distribute 1024 shard to 8 workers, so they may not have an example that satisfies you condition if shard < 25).

Opened https://github.com/huggingface/datasets/issues/7156
Can the deadlock be fixed somehow? The point of IterableDataset is so we don't need to preload the entire dataset, which loses some meaning if we need to see how many examples are in the dataset in order to set shards correctly.

And it is kinda strange that Commenting out the final shuffle avoids the issue since if the infinite loop is inside interleave_datasets you'd expect that to happen regardless of the additional shuffle call?

well the second dataset passed to interleave_datasets is never exhausted, since it's never sampled. But we could also state that the stream of examples from the second dataset is empty if it has probability 0, so I opened https://github.com/huggingface/datasets/pull/7157 to fix the infinite loop issue by ignoring datasets with probability 0, let me know what you think !

Thanks for taking a look!
I think you're right that this is ultimately an issue that the user opts into by specifying a dataset with probability 0, because the user is basically saying "I want to force this interleave_datasets call to run forever" and yet one of the workers can end up having only empty shards to mix...
That said it's probably not a good idea to randomly change the behavior of interleave_datasets with probability 0, I can't be the only one that uses it to repeat many different datasets (since there is no datasets.repeat() function). https://xkcd.com/1172/
I think just the knowledge that filtering out probability 0 datasets fixes the deadlock is good enough for me. I can filter it out on my side and add a restart loop around the dataloader instead.
Thanks again for investigating.

Ok I see ! We can also add .repeat() as well


The AIML40 data uploaded by the script is corrupt

After uploading the dataset for demo2 using the workaround detailed in #59, the data that is uploaded appears to be corrupt:

Thank you for bringing this issue up, the manual procedure for uploading Excel file will take care of the correct format. I will close the issue once the updated readme is on the portal..

I have merged the pull request with the updates and corrections - thank you @shwars for your hard work here and making the content better for everyone


Reset input field after ajax complete

Sorry for my English!
Hi, I have a problem. I initialize plugin after page load. Open modal window, type some text in field with emoji, than I pick emoji and send it to the server. If response code 200, I want to reset all the fields. If I type this
$('#some_form').trigger('reset')
this will work for every input exept emojione.
So I going to do next thing
var emojioneAreas = $(".em").emojioneArea(); emojioneAreas.data("emojioneArea").setText('');
And field is reset but, the content of this field don't present in new FormData object. So tell me pleas, how can I send date via ajax, reset all inputs in form, and fill the form again, without any pain.

emojioneAreas.data("emojioneArea").setText(''); should reset your input,
I don't know how works your form, but probably you should create new FormData() after emojioneAreas.data("emojioneArea").setText('');

emojioneAreas.data("emojioneArea").setText(''); should reset your input,
I don't know how works your form, but probably you should create new FormData() after emojioneAreas.data("emojioneArea").setText('');

I bind submit event and my FormData created every time submit event is triggered.
So firstly I create new FormData and send it via ajax. If ajax response 200, I am going to emojioneAreas.data("emojioneArea").setText(''); and this $('#some_form').trigger('reset')
after all this steps done form is reset and it's looks like everything ok, but when I fill the form again, new FormData object  don't have input with .em class, which is initialized by emojioneArea.

Why not just append the emojiOneAreas to your FormData manually using formData.append?

Why not just append the emojiOneAreas to your FormData manually using formData.append?

I think about it, and probably I will go this way. But it's would be cool to have cleaner way to fill formdata object


Formula for Blisk returning 404

$ brew cask install blisk
==> Downloading https://bliskcloudstorage.blob.core.windows.net/mac-installers/BliskInstaller_0.61.2743.166.dmg

curl: (22) The requested URL returned error: 404 The specified blob does not exist.
Error: Download failed on Cask 'blisk' with message: Download failed: https://bliskcloudstorage.blob.core.windows.net/mac-installers/BliskInstaller_0.61.2743.166.dmg
The incomplete download is cached at /Users/ivan/Library/Caches/Homebrew/Cask/blisk--0.61.2743.166.dmg.incomplete

I made sure I have the latest Cask and brew doctor isn't throwing any warnings.

#26124


Implement Cluster Scoped Kyma CRD for Runtime SKRs

Fixes https://github.com/kyma-project/lifecycle-manager/issues/184

/hold

Closing as per https://github.com/kyma-project/lifecycle-manager/issues/184#issuecomment-1258162382


State the default user a container process runs

This patch adds information about the default user/group a process runs on Linux.
Signed-off-by: Amit Saha<EMAIL_ADDRESS>

SGTM, but the commit is not signed (try git commit -s --amend .)
Also, as a nit on the commit message, the subject line more appropriately be "config.md: args is an array of strings"

Thanks @vbatts , done.

On Sun, May 01, 2016 at 02:17:13AM -0700, Amit Saha wrote:

This patch adds information about the default user/group a process
runs on Linux.

I'm not sure this default is a good idea.  For example, a config that
does not create a new user namespace may want the process to run as
the current user/group instead of as root.  I think it's better to
follow unshare(1) and require folks who want a process to run as root
to specify that explicitly in their config.
$ unshare --user id
uid=65534(nobody) gid=65534(nobody) groups=65534(nobody)
$ unshare --user --map-root-user id
uid=0(root) gid=0(root) groups=0(root),65534(nobody)
Wording for that approach would be something like (also pulling in
#412):

uid (int, required) specifies the user ID in the container
namespace.  If unset, the runtime will not attempt to manipulate
the user ID (e.g. not calling setuid(2) or similar).

@wking But that is what is the default now, isn't it?

On Sun, May 01, 2016 at 03:21:16PM -0700, Amit Saha wrote:

@wking But that is what is the default now, isn't it?

It's not in the spec, so the current default is “undefined” ;).
Bundle authors who expect this behavior may get it with runC (I'm not
sure), but may see different behavior on other runtimes (e.g. ccon-oci
will not call setuid 1).  If we want to make the “default to root”
behavior explicit, I'd rather see that also land with motivation
explaining why it's a better approach than “do nothing by default”
2.
 Subject: Exposing platform defaults
 Date: Thu, 14 Jan 2016 15:36:26 -0800
 Message-ID<EMAIL_ADDRESS>

I think the current text that makes it required is best. Implied behavior that goes straight to the highest privledge level isn't super helpful.

Because we have uid/gid required in the spec we do not need to talk about what the default is.  We made it required so we don't have to specify defaults for this.

PR #425


Position from preferred resolution gets overwritten when the current resolution changes.

Ideally it should remember the position of each resolution used, however going to any other resolution will shift the UI elements into undesired positions and result in having to manually move them again.  For the time being I've decided to disable this plugin since my resolution switches based on the display in use.

Is there any plugin that you know that handles this in a satisfactory way?

Is there any plugin that you know that handles this in a satisfactory way?

I couldn't say since I don't use very many plugins nor do I develop any, but I'd be surprised if there wasn't a way to do so.  Maybe asking in the Dalamud community specifically could yield a potential fix.

#7, when done, will allow you to set different profiles for different resolutions

Sounds like a good solution. Hopefully this can be adopted by other UI plugins.

I actually did it in a different way. If you grab the testing version you can try it out


Proposal for last_val() for Vectors

Hi,
you have for Vec's the methods last() and last_mut() but if you want to get the value itself you have to use pop() and it breaks the semantic. I would propose to introduce last_val() that could be a simple alias to pop() since a moved value cannot exist two times, so it has to be deleted from the list. But last_val() would confuse fewer users searching for something that returns the last value instead of a reference.

In pretty much all languages, “extracting the last value of a container” is called pop. I don’t see the basis of the statement that users would be less confused with your suggestion.

This is one of those changes that realistically would have had to happen more than 5 years ago to be worth it.  Even assuming (without taking a position on it) that last_val is a slightly better name than pop, that's not worth the churn to switch a common method nor worth the added confusion of two methods that do the same thing.
The description of pop in the docs says

Removes the last element from a vector and returns it
so hopefully this is still sufficiently discoverable for anyone looking to perform this operation.

When I just looked at the issue title, I was expecting this to be a moving projection from Vec<T> to T instead of &mut Vec<T> to T. The name last_val itself is alone confusing enough.


HUM-620 add algorithm to scheme in metadata

This will make sense if we ever have multiple algorithms.
It will require any existing data to be deleted.

I get this with this patch:
cory@saio:~$ hummingbird nectar -v -A http://<IP_ADDRESS>:8080/auth/v1.0 -U test:tester -K testing get hec/foo
X-Trans-Id: "151a087afa60d853"
unexpected EOF

LGTM, and it even seems to work! 👍


Consider extending algorithms and cipher specs in MslConstants

Similar to how the authentication and keyx schemes can be extended by the MSL configuration layer, doing the same for the compression and crypto enums currently held in MslConstants will probably also be useful.
MslUtils would need to allow compression algorithms to be installed as well (maybe similar to Base64). Perhaps a compression class should be created explicitly to support compression implementations instead of continuing to mix it into MslUtils.

Base64 was done on a global static level. It would be preferred to have compression algorithms configurable via an object instead of an static, something along the lines of MslContext (an object we provide to MSL).

The approach I've used is to use injection (e.g. MslContext) when there is context that needs to be carried for the operation, whereas standalone instances are global statics like Base64 and many other language library APIs, or like logging solutions.
I think compression would fall into the category of a standalone instance that could be used anywhere independent of context. Do you have an example of how Base64 would have benefited from being pulled off of MslContext? Doing so would also require passing MslContext into even more functions than it currently is provided to.


Multiple error messages are displayed for same error, if multiple tabs & panel are open

[ x] I am on the 2.0.0-canary.11 Hyper.app 2.0.0-canary.11
[x ] I have searched the issues of this repo and believe that this is not a duplicate

OS version and name:
Hyper.app version: 2.0.0-canary.11
Link of a Gist with the contents of your .hyper.js: https://gist.github.com/livey0u/88e670d9ad3734e6aa57825416179247
Relevant information from devtools (CMD+ALT+I on macOS, CTRL+SHIFT+I elsewhere): https://gist.github.com/livey0u/85e1c8bbfde32f54dc7f310727f7c08e
The issue is reproducible in vanilla Hyper.app: Not sure

Issue
There was some issue(see the 2nd gist file). Because of that, an error is displayed at the beginning(ie: when there is only one tab). After launching a few tabs & panels, if a plugin is installed or the configuration is reloaded, the same error is displayed number of tabs & panels times. I think, the same is true for notifications also.

Your issue is due to a bad plugin (ie. hyper-autoprofile), developped by a bad bad developper (ie. me) 😛.
Can you try to add a autoProfile: {} in your hyper config file?
Do you mind to open an issue in plugin repository: https://github.com/chabou/hyper-autoprofile

@livey0u: Fixed in hyper-autoprofile v1.0.1.
Thank you for your feedback 🙏


In Row while using baseline alignment Some of children painted outside the bounds

When using CrossAxisAlignment.baseline in Row widget, it seems only children with text painted inside Row boundaries.

Code to reproduce:
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: "App",
      theme: ThemeData(
        textSelectionHandleColor: Colors.red,
      ),
      home: Test1(),
    );
  }
}

class Test1 extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            Row(
              crossAxisAlignment: CrossAxisAlignment.baseline,
              textBaseline: TextBaseline.ideographic,
              children: <Widget>[
                Container(
                  child: Text("Hello World"),
                  height: 40.0,
                  color: Colors.green,
                ),
                Container(
                  width: 60.0,
                  height: 60.0,
                  color: Colors.blue,
                ),
              ],
            ),
            Container(
              height: 40.0,
              color: Color.fromARGB(120, 255, 0, 0),
            ),
          ],
        ),
      ),
    );
  }
}

Flutter doctor:
[√] Flutter (Channel stable, v1.5.4-hotfix.2, on Microsoft Windows [Version 10.0.17134.858], locale en-IN)
    • Flutter version 1.5.4-hotfix.2 at D:\Installed\FlutterSDK
    • Framework revision 7a4c33425d (8 weeks ago), 2019-04-29 11:05:24 -0700
    • Engine revision 52c7a1e849
    • Dart version 2.3.0 (build 2.3.0-dev.0.5 a1668566e5)

[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at C:\Users\Flower\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)
    • All Android licenses accepted.

[√] Android Studio (version 3.4)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 36.1.1
    • Dart plugin version 183.6270
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

[√] Connected device (1 available)
    • Android SDK built for x86 • emulator-5554 • android-x86 • Android 9 (API 28) (emulator)

• No issues found!

testing the code below with the latest master
code
import 'package:flutter/foundation.dart';
import 'package:flutter/material.dart';

void main() => runApp(
      const MyApp(
        key: Key('app'),
      ),
    );

class MyApp extends StatelessWidget {
  const MyApp({Key key}) : super(key: key);
  @override
  Widget build(BuildContext context) => MaterialApp(
        home: const MyHomePage(
          key: Key('home'),
        ),
      );
}

class MyHomePage extends StatelessWidget {
  const MyHomePage({Key key}) : super(key: key);

  @override
  Widget build(BuildContext context) => Material(
        child: Center(
          child: Column(
            mainAxisAlignment: MainAxisAlignment.center,
            children: <Widget>[
              Row(
                crossAxisAlignment: CrossAxisAlignment.baseline,
                textBaseline: TextBaseline.ideographic,
                children: <Widget>[
                  Container(
                    child: const Text('Hello World'),
                    height: 40.0,
                    color: Colors.green,
                  ),
                  Container(
                    width: 60.0,
                    height: 60.0,
                    color: Colors.blue,
                  ),
                ],
              ),
              Container(
                height: 40.0,
                color: const Color.fromARGB(120, 255, 0, 0),
              ),
            ],
          ),
        ),
      );
}

screenshot

doctor
[✓] Flutter (Channel master, 1.21.0-6.0.pre.129, on Mac OS X 10.15.5 19F101, locale en-GB)
    • Flutter version 1.21.0-6.0.pre.129 at /Users/nevercode/development/flutter_master
    • Framework revision 30aef0a3b9 (14 hours ago), 2020-07-30 14:20:21 -0700
    • Engine revision a9910e409c
    • Dart version 2.10.0 (build 2.10.0-1.0.dev 24c7666def)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/nevercode/Library/Android/sdk
    • Platform android-29, build-tools 29.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.5, Build version 11E608c
    • CocoaPods version 1.9.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.12.2

[✓] Connected device (4 available)
    • Pixel 3a (mobile) • 965AY0WP5C • android-arm64  • Android 10 (API 29)
    • macOS (desktop)   • macos      • darwin-x64     • Mac OS X 10.15.5 19F101
    • Web Server (web)  • web-server • web-javascript • Flutter Tools
    • Chrome (web)      • chrome     • web-javascript • Google Chrome 84.0.4147.105

• No issues found!

the issue seems to be solved, I feel safe to close this issue,
if you disagree please write in the comments and I will reopen it.
Thank you


Fix empty selectors list in deprecation cop view

This fixes https://github.com/atom/deprecation-cop/issues/47. As far as I can tell, the problem here was that the variable deprecations from the outer loop was used in the inner loop, and was getting overwritten. This problem was introduced here -- previously the outer loop didn't use a deprecations variable, it just re-fetched the deprecations in every iteration of the loop. Really sorry for not catching this before.
This PR fixes the problem by changing the variable's name in the inner loop so that there's no conflict. We could also use the same approach as before. This just seemed a bit cleaner.
Before:

After (correctly lists deprecations in styles.less):

cc @kevinsawicki for :eyes:

:+1:


Log errors captured in integrations with SentryLogger

This is just a very quick PR for discussion.
:scroll: Description

add logger name parameter
log errors from Zone, Isolate and Flutter integrations

:bulb: Motivation and Context
Fixes https://github.com/getsentry/sentry-dart/issues/640
:green_heart: How did you test it?
:pencil: Checklist

[x] I reviewed submitted code
[ ] I added tests to verify changes
[ ] I updated the docs if needed
[ ] All tests passing
[ ] No breaking changes

:crystal_ball: Next steps

Codecov Report

Merging #641 (849ae73) into main (9599a50) will increase coverage by 1.77%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #641      +/-   ##
==========================================
+ Coverage   90.28%   92.05%   +1.77%
==========================================
  Files          93        8      -85
  Lines        3035      277    -2758
==========================================
- Hits         2740      255    -2485
+ Misses        295       22     -273

Impacted Files
Coverage Δ

dart/lib/src/default_integrations.dart

dart/lib/src/diagnostic_logger.dart

dart/lib/src/isolate_error_integration.dart

dart/lib/src/sentry_options.dart

...art/lib/src/environment/environment_variables.dart

dart/lib/src/noop_client.dart

dart/lib/src/utils.dart

dart/lib/src/platform_checker.dart

dart/lib/src/protocol/debug_image.dart

...event_processor/deduplication_event_processor.dart

... and 75 more

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 9599a50...849ae73. Read the comment docs.

The sentry_flutter builds seem to be failing because they don't use the correct dart dependency.

@kuhnroyal CI fails ->

ERROR: ../lib/src/default_integrations.dart:77:11: Error: No named parameter with the name 'logger'.
ERROR:           logger: 'sentry.flutterError',

@kuhnroyal add changelog entry and its good to go, thanks for doing this


Bug/forms 209-conditions persist

Description
bug report:

If I create a condition from Edit Conditions > add an inset text component > set the condition to the one I just created and save > go back into the component, the conditions field is blank (the condition doesn't apply to Preview either)

change options.conditions to options.condition
add types

Acceptance criteria
Given I have a page with an inset text component and conditions available to select
When I select a condition and click save
Then after re-opening the page, I can see my selected condition
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce
the testing if necessary.
Before PR's can be merged they will need to be tested by QA and approved where
applicable. To flag the change to QA assign @XGovFormBuilder/qa as one of the reviewers.

[x] manual

Checklist:

[x] My changes do not introduce any new linting errors
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation and versioning
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have rebased onto master and there are no code conflicts
[x] I have checked deployments are working in all environments
[x] I have updated the architecture diagrams as per Contribute.md

Fixed verified locally


Investigate & add update mode cross-connectors

We should investigate how and where we can bring the update functionality on receive that we currently only have in Revit (I believe).
See: https://speckle.community/t/speckle-should-be-able-to-update-existing-objects-in-the-dwg-file/3424/2

An update receive mode has been added for rhino, autocad, and civil3d!

Update:

[x] Revit
[x] Rhino
[x] Autocad
[x] Civil 3D
[ ] Structural connectors ? @Reynold-Chan

This seems to be closed - though we should document how this was implemented across each connector and how well round-tripping works for cross connector workflows


add russian language

add russian language

@diksset  It is not a right way to use whole upstream as a pull request source, it contains too much modifications. Would you please make a separate pull request that only contains the language resource ?

Closed by #65


Not able to group multiple players

What version of Music Assistant has the issue?
2.2.2
What version of the Home Assistant Integration have you got installed?
2024.8.1
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

[X] Yes

The problem
When I try to group multiple HEOS Speakers (2+), which are integrated through the Home Assistant plugin, I only get a group of two. If I select a third one the other one gets kicked out of the group. It doesn't throw any errors in the log.

Using the grouping feature of the devices that are imported through Airplay works fine. In the HEOS App you can see, that grouping the Airplay devices doesn't actually create a room but plays synced streams on each devices.
How to reproduce

Integrate the speakers through Home Assistant Media Player Plugin
Try to group more than two speakers

Music Providers
Not working:

Home Assistant Media Player

Working:

AirPlay

Player Providers
Not working:

Spotify
Soundcloud

Full log output
home-assistant_mass_2024-08-23T22-58-48.571Z.log
Additional information
No response
What version of Home Assistant Core are your running
2024.8.2
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Alternative

Why do you want to group HA media players if you can group the Airplay ones?

For me Airplay has a way bigger delay and some random sound dropouts from time to time.

We will be more interested in that than trying to fix a universal group of HA players but this will get looked at eventually

For me Airplay has a way bigger delay and some random sound dropouts from time to time.

Airplay has a bit of delay at stream-start (1.5 to 2 seconds) but should then be buttery smooth.
Do you still have those dropouts in the last release ?
As for the grouping of the HEOS speakers, what happens if the stream is already playing and you group them in Home Assistant ? Does that work ?

Airplay has a bit of delay at stream-start (1.5 to 2 seconds) but should then be buttery smooth.
Do you still have those dropouts in the last release ?

Yes in a 3 minute song i have like 3 to 5  one second dropouts. Sometimes it's worse.

As for the grouping of the HEOS speakers, what happens if the stream is already playing and you group them in Home Assistant ? Does that work ?

If the music plays on one speaker and I use an automation to group them: yes that works. The players get grouped correctly and the music plays without stopping.

Yes in a 3 minute song i have like 3 to 5 one second dropouts. Sometimes it's worse.

Sounds like buffer issue - Airplay sends lossless PCM or ALAC by default so its a bit demanding on bandwidth, while sending audio to HEOS with HA will send mp3 compressed audio by default. Did you leave compression on in the Airplay settings ?

If the music plays on one speaker and I use an automation to group them: yes that works. The players get grouped correctly and the music continues without stopping.

OK, thanks. I'll review the implementation between MA and HA then

Thanks for your time and effort!
Sounds like buffer issue - Airplay sends lossless PCM or ALAC by default so its a bit demanding on bandwidth, while sending audio to HEOS with HA will send mp3 compressed audio by default. Did you leave compression on in the Airplay settings ?
I'm not sure whre to do that. Is it a MA setting or inside the heos app?

In the MA settings for the player

@timbeckss please provide some further information regarding the effect of changing the compression setting

Having some airplay dropout issues and found this.

Did you leave compression on in the Airplay settings ?

Is this question also suggesting that dropouts are less likely if compression is enabled or disabled? What is the suggested setting?

If the dropouts are due to network congestion then compression ON should help

Upcoming changes in the beta server will see groups completely rewritten. Hopefully this will fix this issue.

I will try it as soon it is released. Thanks for your efforts!

Beta 30 has been released. Confirm this hass been fixed

Sadly I still have the same results I described in my initial post. Grouping with an automation works fine nevertheless. Im going to do a full factory reset with all speakers to rule out any problems with heos.

Upcoming changes in the beta server will see groups completely rewritten. Hopefully this will fix this issue.

That only applies for grouping within any of the native providers. This issue report is about grouping players from the HA provider, and more specifically HEOS players.

I have removed the ability to sync players from MA using HA players, it was too much of a hot mess due to the generic approach.
You just need to use HA players to do the grouping or ofcourse use any of the native MA providers.


isSelected

Hey! I like your Tag Controller, but sadly there is an error on Swift 2.0:
RRTagCollectionViewCell.swift:15:9: Getter for 'isSelected' with Objective-C selector 'isSelected' conflicts with getter for 'selected' from superclass 'UICollectionViewCell' with the same Objective-C selector.
Do you see how I can fix it?
Thanks.

After convert the code with last swift syntaxe, just change isSelected for setSelected ( or whatever ) in all the files and the app will run..


Bugfix/exoplayer not muting

Replaced the commented out mute code with code that mutes

This is in regard to this issue:
https://github.com/nstudio/nativescript-plugins/issues/11

Thanks for the PR.

Released with 5.0.6


fixes duplicate keys in normalizedColumnNameMap

The generated code duplicates keys in the normalized column name map array in certain cases where two variants of how to specify a column accidentally create the exact same spelling.
For example the spelling of a single word column name is the same when using camelcase or snake_case. PHP ignorhes this but many tools flag this as a potential error, hence this fix.
Marked draft as I have to figure out the unit tests

I rebased it to the current master. Anything else I need to do? Do we need to resolve the discussions?

Hey @hsegnitz,
Everything is great, all that's left to do is wait. The maintainers seem to have limited time to spend on this project, so it usually takes a while until you see progress. This can be discouraging, and as a fellow contributer, I should have warned you about it. Sorry!
In my experience, it does not mean they don't appreciate all your work.
I submitted another PR last week, and I think it blew their capacities. Now I am holding back, not to get in the way of a new contributor. I had hoped, that running the tests would have been approved by now, but what can you do, it takes as long as it takes.
Anyway, again, sorry for not mentioning it earlier.
Best,
Moritz


[IMPROVEMENT] Update uninstallation info to include the 'Deleting Confirmation Flag'  in chart

Is your improvement request related to a feature? Please describe (👍 if you like this request)
Update the uninstallation instructions in the chart with the 'Deleting Confirmation Flag' information.

After verified the PR-2304 and PR-2305 , we could find out the uninstallation instructions in the chart with the 'Deleting Confirmation Flag' information.


[UI] Extra Tracks

If I run this simple tracing example:
void track0() {
    TRACE_EVENT("Stream", "Slice0::0");
    std::cout << "timing stuff.." << std::endl;
}

I get this rendering in the UI:

The main track is duplicated and there is an extra empty track for the process.  If I define a custom track, the duplicate track goes away, but there is still an empty track for the process.
void track0() {
    TRACE_EVENT("Stream", "Slice0::0");
    std::cout << "timing stuff.." << std::endl;
}

I've tagged this as a UI issue because I've tried using custom data sources to mimic the output from above with custom data sources and things became more wonky.  I was able to make a custom embedding of tracks within processes, but all slices then appeared as the same color.  For now I just listed minimal examples, which I believe are supported.

Can you please link a trace which is demonstrating this behavior? This is likely a trace processor or SDK bug: it's unlikely the UI is creating tracks which are not in the data model.

Thanks for the quick response!
Github only supports certain file extensions, so I added .txt to the end of the binary file name before uploading here.
simple_trace0.perfetto-trace.txt
I am opening this file at https://ui.perfetto.dev/.
I also converted the file to something human readable with
./traceconv text simple_trace0.perfetto-trace simple_trace0.txt
simple_trace0.txt
From that human readable version, it looks to me like there is one track defined for the thread and one for the process (to make the drop down category in the GUI).  As a side note, is this the best way to debug?  I am creating a binary from C++ code, converting to a human readable format, and then going back to the C++ code to make changes.  Is there a way to edit a human readable file and then display it?
Anyway, I think this can be viewed as two issues, which may or may not be related.

The GUI displays duplicate tracks from the above trace.  I was a bit loose with my terminology, but it seems to me this is an issue with something post-SDK, like the trace processor.
An empty process track is displayed.  There is a track descriptor which defines the process in the trace, so maybe this is intended trace processor/GUI behavior for the given trace.  If that is the case, I suppose this would be an SDK issue.  What should the trace packets look like to group multiple tracks under a process without displaying an empty track?

There are two threads in the thread table.  One of them is swapper, which seems to have been added automatically.  Is this an ftrace thing?

Another issue which may actually be a UI issue can be seen with the trace I attached above.
When collapsed, the process shows what seems to be a sum of the active threads at that time.  It seems to be summing two things which are offset by 10.2ns and the whole thing does not align with the thread(s) inside.  I'll try to align the screenshots here so you can see what I mean:

I created some traces where the two threads also appear misaligned (even through they show the exact same slices).  I can post those, but I figured I should stick with the one trace in this issue.

Sorry I would love to look at this but swamped with other stuff ATM.
If you just want to convert a textproto trace to protobuf to load in UI, have a look at the script tools/serialize_test_data.py. You'll need a full checkout and build of Perfetto to use it though.
If you have a minimal repro, then I will come back and look a bit further.

Ack thanks for the clarification. I'll try and look at this when I have some spare time.

Thanks Lalit!  One more piece of very relevant info:  I just noticed the duplicate Thread view was only happening in one browser and found that it is linked to the "Tracks V2" option in the GUI (which was set in one browser).  I disabled that and it only shows one thread now.  There is still a default empty process  and the process graph is misaligned, but I think those issues are less significant.

Maybe this might deserve a separate ticket, but the 'default empty process' is also affecting me, too.  One possible usecase is for tracing applications with only counters (e.g., monitoring internal stats of a given application, while the traces are not interesting).  The empty tracks are not going to be a showstopper, but it gets annoying once we have a large number of processes.  I can create a ticket and a minimal repro if it seems worthy.


CommanderPi installs but doesn't run on RaspberryPi OS using a RaspberryPi 4 64bit

Hello,
I just found this program and I installed it but nothing seems to work when trying to get it to run. I have a Raspberry Pi 4 8GB 64bit system and I currently run Raspberry Pi OS. I get the following error :
pi@pi-desktop:~/Desktop $ /home/pi/CommanderPi/src/start.sh
No protocol specified
No protocol specified
Traceback (most recent call last):
File "/home/pi/CommanderPi/src/main.py", line 22, in
main()
File "/home/pi/CommanderPi/src/main.py", line 18, in main
start = g.Window()
File "/home/pi/CommanderPi/src/gui.py", line 567, in init
master = tk.Tk()
File "/usr/lib/python3.7/tkinter/init.py", line 2023, in init
self.tk = _tkinter.create(screenName, baseName, className, interactive, wantobjects, useTk, sync, use)
_tkinter.TclError: couldn't connect to display ":0"
Any ideas or help in getting this running please.
I also get this error when installing it as well:
Traceback (most recent call last):
File "c_desktop.py", line 20, in
f = open(d_dir, "w+")
FileNotFoundError: [Errno 2] No such file or directory: '/root/Desktop/commanderpi.desktop'
chmod: cannot access '/root/Desktop/commanderpi.desktop': No such file or directory

You installed is as root, you must install it without sudo.

You installed it as root, you must install it without sudo.

Thanks, I restarted my Pi and then it ran no problem.