text:
Usage with webpack

Hi guys, it seems that there are many libs missing when I try to use the library as my console is litteraly shouting at me:
ERROR in ./~/request/lib/cookies.js
Module not found: Error: Cannot resolve module 'tough-cookie' in E:\Projets\pkmn-go\node_modules\request\lib
resolve module tough-cookie in E:\Projets\pkmn-go\node_modules\request\lib
  looking for modules in E:\Projets\pkmn-go\node_modules
    resolve 'file' tough-cookie in E:\Projets\pkmn-go\node_modules
      resolve file
        E:\Projets\pkmn-go\node_modules\tough-cookie doesn't exist
        E:\Projets\pkmn-go\node_modules\tough-cookie.js doesn't exist
        E:\Projets\pkmn-go\node_modules\tough-cookie.jsx doesn't exist
    E:\Projets\pkmn-go\node_modules\tough-cookie doesn't exist (module as directory)
[E:\Projets\pkmn-go\node_modules\tough-cookie]
[E:\Projets\pkmn-go\node_modules\tough-cookie.js]
[E:\Projets\pkmn-go\node_modules\tough-cookie.jsx]
[E:\Projets\pkmn-go\node_modules\tough-cookie]
 @ ./~/request/lib/cookies.js 3:12-35
ERROR in ./~/mime-db/db.json
Module parse failed: E:\Projets\pkmn-go\node_modules\mime-db\db.json Unexpected token (2:40)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (2:40)
    at Parser.pp$4.raise (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:2221:15)
    at Parser.pp.unexpected (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:603:10)
    at Parser.pp.semicolon (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:581:61)
    at Parser.pp$1.parseExpressionStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:966:10)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:730:24)
    at Parser.pp$1.parseBlock (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:981:25)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:709:33)
    at Parser.pp$1.parseTopLevel (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:638:25)
    at Parser.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:516:17)
    at Object.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:3098:39)
 @ ./~/mime-db/index.js 11:17-37
ERROR in ./~/request/request.js
Module not found: Error: Cannot resolve module 'forever-agent' in E:\Projets\pkmn-go\node_modules\request
resolve module forever-agent in E:\Projets\pkmn-go\node_modules\request
  looking for modules in E:\Projets\pkmn-go\node_modules
    resolve 'file' forever-agent in E:\Projets\pkmn-go\node_modules
      resolve file
        E:\Projets\pkmn-go\node_modules\forever-agent doesn't exist
        E:\Projets\pkmn-go\node_modules\forever-agent.js doesn't exist
        E:\Projets\pkmn-go\node_modules\forever-agent.jsx doesn't exist
    E:\Projets\pkmn-go\node_modules\forever-agent doesn't exist (module as directory)
[E:\Projets\pkmn-go\node_modules\forever-agent]
[E:\Projets\pkmn-go\node_modules\forever-agent.js]
[E:\Projets\pkmn-go\node_modules\forever-agent.jsx]
[E:\Projets\pkmn-go\node_modules\forever-agent]
 @ ./~/request/request.js 17:19-43
ERROR in ./~/request/lib/har.js
Module not found: Error: Cannot resolve module 'fs' in E:\Projets\pkmn-go\node_modules\request\lib
resolve module fs in E:\Projets\pkmn-go\node_modules\request\lib
  looking for modules in E:\Projets\pkmn-go\node_modules
    resolve 'file' fs in E:\Projets\pkmn-go\node_modules
      resolve file
        E:\Projets\pkmn-go\node_modules\fs doesn't exist
        E:\Projets\pkmn-go\node_modules\fs.js doesn't exist
        E:\Projets\pkmn-go\node_modules\fs.jsx doesn't exist
    E:\Projets\pkmn-go\node_modules\fs doesn't exist (module as directory)
[E:\Projets\pkmn-go\node_modules\fs]
[E:\Projets\pkmn-go\node_modules\fs.js]
[E:\Projets\pkmn-go\node_modules\fs.jsx]
[E:\Projets\pkmn-go\node_modules\fs]
 @ ./~/request/lib/har.js 3:9-22
ERROR in ./~/har-validator/lib/schemas/cache.json
Module parse failed: E:\Projets\pkmn-go\node_modules\har-validator\lib\schemas\cache.json Unexpected token (2:14)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (2:14)
    at Parser.pp$4.raise (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:2221:15)
    at Parser.pp.unexpected (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:603:10)
    at Parser.pp.semicolon (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:581:61)
    at Parser.pp$1.parseExpressionStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:966:10)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:730:24)
    at Parser.pp$1.parseBlock (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:981:25)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:709:33)
    at Parser.pp$1.parseTopLevel (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:638:25)
    at Parser.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:516:17)
    at Object.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:3098:39)
 @ ./~/har-validator/lib/schemas/index.js 4:9-32
ERROR in ./~/har-validator/lib/schemas/cacheEntry.json
Module parse failed: E:\Projets\pkmn-go\node_modules\har-validator\lib\schemas\cacheEntry.json Unexpected token (2:9)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (2:9)
    at Parser.pp$4.raise (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:2221:15)
    at Parser.pp.unexpected (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:603:10)
    at Parser.pp.semicolon (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:581:61)
    at Parser.pp$1.parseExpressionStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:966:10)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:730:24)
    at Parser.pp$1.parseBlock (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:981:25)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:709:33)
    at Parser.pp$1.parseTopLevel (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:638:25)
    at Parser.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:516:17)
    at Object.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:3098:39)
 @ ./~/har-validator/lib/schemas/index.js 5:14-42
ERROR in ./~/har-validator/lib/schemas/content.json
Module parse failed: E:\Projets\pkmn-go\node_modules\har-validator\lib\schemas\content.json Unexpected token (2:8)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (2:8)
    at Parser.pp$4.raise (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:2221:15)
    at Parser.pp.unexpected (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:603:10)
    at Parser.pp.semicolon (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:581:61)
    at Parser.pp$1.parseExpressionStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:966:10)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:730:24)
    at Parser.pp$1.parseBlock (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:981:25)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:709:33)
    at Parser.pp$1.parseTopLevel (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:638:25)
    at Parser.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:516:17)
    at Object.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:3098:39)
 @ ./~/har-validator/lib/schemas/index.js 6:11-36
ERROR in ./~/har-validator/lib/schemas/cookie.json
Module parse failed: E:\Projets\pkmn-go\node_modules\har-validator\lib\schemas\cookie.json Unexpected token (2:8)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (2:8)
    at Parser.pp$4.raise (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:2221:15)
    at Parser.pp.unexpected (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:603:10)
    at Parser.pp.semicolon (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:581:61)
    at Parser.pp$1.parseExpressionStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:966:10)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:730:24)
    at Parser.pp$1.parseBlock (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:981:25)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:709:33)
    at Parser.pp$1.parseTopLevel (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:638:25)
    at Parser.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:516:17)
    at Object.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:3098:39)
 @ ./~/har-validator/lib/schemas/index.js 7:10-34
ERROR in ./~/har-validator/lib/schemas/creator.json
Module parse failed: E:\Projets\pkmn-go\node_modules\har-validator\lib\schemas\creator.json Unexpected token (2:8)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (2:8)
    at Parser.pp$4.raise (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:2221:15)
    at Parser.pp.unexpected (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:603:10)
    at Parser.pp.semicolon (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:581:61)
    at Parser.pp$1.parseExpressionStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:966:10)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:730:24)
    at Parser.pp$1.parseBlock (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:981:25)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:709:33)
    at Parser.pp$1.parseTopLevel (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:638:25)
    at Parser.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:516:17)
    at Object.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:3098:39)
 @ ./~/har-validator/lib/schemas/index.js 8:11-36
ERROR in ./~/har-validator/lib/schemas/entry.json
Module parse failed: E:\Projets\pkmn-go\node_modules\har-validator\lib\schemas\entry.json Unexpected token (2:8)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (2:8)
    at Parser.pp$4.raise (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:2221:15)
    at Parser.pp.unexpected (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:603:10)
    at Parser.pp.semicolon (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:581:61)
    at Parser.pp$1.parseExpressionStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:966:10)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:730:24)
    at Parser.pp$1.parseBlock (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:981:25)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:709:33)
    at Parser.pp$1.parseTopLevel (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:638:25)
    at Parser.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:516:17)
    at Object.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:3098:39)
 @ ./~/har-validator/lib/schemas/index.js 9:9-32
ERROR in ./~/har-validator/lib/schemas/har.json
Module parse failed: E:\Projets\pkmn-go\node_modules\har-validator\lib\schemas\har.json Unexpected token (2:8)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (2:8)
    at Parser.pp$4.raise (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:2221:15)
    at Parser.pp.unexpected (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:603:10)
    at Parser.pp.semicolon (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:581:61)
    at Parser.pp$1.parseExpressionStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:966:10)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:730:24)
    at Parser.pp$1.parseBlock (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:981:25)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:709:33)
    at Parser.pp$1.parseTopLevel (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:638:25)
    at Parser.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:516:17)
    at Object.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:3098:39)
 @ ./~/har-validator/lib/schemas/index.js 10:7-28
ERROR in ./~/har-validator/lib/schemas/log.json
Module parse failed: E:\Projets\pkmn-go\node_modules\har-validator\lib\schemas\log.json Unexpected token (2:8)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (2:8)
    at Parser.pp$4.raise (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:2221:15)
    at Parser.pp.unexpected (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:603:10)
    at Parser.pp.semicolon (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:581:61)
    at Parser.pp$1.parseExpressionStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:966:10)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:730:24)
    at Parser.pp$1.parseBlock (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:981:25)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:709:33)
    at Parser.pp$1.parseTopLevel (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:638:25)
    at Parser.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:516:17)
    at Object.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:3098:39)
 @ ./~/har-validator/lib/schemas/index.js 11:7-28
ERROR in ./~/har-validator/lib/schemas/page.json
Module parse failed: E:\Projets\pkmn-go\node_modules\har-validator\lib\schemas\page.json Unexpected token (2:8)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (2:8)
    at Parser.pp$4.raise (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:2221:15)
    at Parser.pp.unexpected (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:603:10)
    at Parser.pp.semicolon (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:581:61)
    at Parser.pp$1.parseExpressionStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:966:10)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:730:24)
    at Parser.pp$1.parseBlock (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:981:25)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:709:33)
    at Parser.pp$1.parseTopLevel (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:638:25)
    at Parser.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:516:17)
    at Object.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:3098:39)
 @ ./~/har-validator/lib/schemas/index.js 12:8-30
ERROR in ./~/har-validator/lib/schemas/pageTimings.json
Module parse failed: E:\Projets\pkmn-go\node_modules\har-validator\lib\schemas\pageTimings.json Unexpected token (2:8)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (2:8)
    at Parser.pp$4.raise (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:2221:15)
    at Parser.pp.unexpected (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:603:10)
    at Parser.pp.semicolon (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:581:61)
    at Parser.pp$1.parseExpressionStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:966:10)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:730:24)
    at Parser.pp$1.parseBlock (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:981:25)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:709:33)
    at Parser.pp$1.parseTopLevel (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:638:25)
    at Parser.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:516:17)
    at Object.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:3098:39)
 @ ./~/har-validator/lib/schemas/index.js 13:15-44
ERROR in ./~/har-validator/lib/schemas/postData.json
Module parse failed: E:\Projets\pkmn-go\node_modules\har-validator\lib\schemas\postData.json Unexpected token (2:8)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (2:8)
    at Parser.pp$4.raise (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:2221:15)
    at Parser.pp.unexpected (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:603:10)
    at Parser.pp.semicolon (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:581:61)
    at Parser.pp$1.parseExpressionStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:966:10)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:730:24)
    at Parser.pp$1.parseBlock (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:981:25)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:709:33)
    at Parser.pp$1.parseTopLevel (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:638:25)
    at Parser.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:516:17)
    at Object.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:3098:39)
 @ ./~/har-validator/lib/schemas/index.js 14:12-38
ERROR in ./~/har-validator/lib/schemas/record.json
Module parse failed: E:\Projets\pkmn-go\node_modules\har-validator\lib\schemas\record.json Unexpected token (2:8)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (2:8)
    at Parser.pp$4.raise (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:2221:15)
    at Parser.pp.unexpected (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:603:10)
    at Parser.pp.semicolon (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:581:61)
    at Parser.pp$1.parseExpressionStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:966:10)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:730:24)
    at Parser.pp$1.parseBlock (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:981:25)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:709:33)
    at Parser.pp$1.parseTopLevel (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:638:25)
    at Parser.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:516:17)
    at Object.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:3098:39)
 @ ./~/har-validator/lib/schemas/index.js 15:10-34
ERROR in ./~/har-validator/lib/schemas/request.json
Module parse failed: E:\Projets\pkmn-go\node_modules\har-validator\lib\schemas\request.json Unexpected token (2:8)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (2:8)
    at Parser.pp$4.raise (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:2221:15)
    at Parser.pp.unexpected (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:603:10)
    at Parser.pp.semicolon (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:581:61)
    at Parser.pp$1.parseExpressionStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:966:10)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:730:24)
    at Parser.pp$1.parseBlock (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:981:25)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:709:33)
    at Parser.pp$1.parseTopLevel (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:638:25)
    at Parser.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:516:17)
    at Object.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:3098:39)
 @ ./~/har-validator/lib/schemas/index.js 16:11-36
ERROR in ./~/har-validator/lib/schemas/response.json
Module parse failed: E:\Projets\pkmn-go\node_modules\har-validator\lib\schemas\response.json Unexpected token (2:8)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (2:8)
    at Parser.pp$4.raise (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:2221:15)
    at Parser.pp.unexpected (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:603:10)
    at Parser.pp.semicolon (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:581:61)
    at Parser.pp$1.parseExpressionStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:966:10)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:730:24)
    at Parser.pp$1.parseBlock (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:981:25)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:709:33)
    at Parser.pp$1.parseTopLevel (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:638:25)
    at Parser.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:516:17)
    at Object.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:3098:39)
 @ ./~/har-validator/lib/schemas/index.js 17:12-38
ERROR in ./~/har-validator/lib/schemas/timings.json
Module parse failed: E:\Projets\pkmn-go\node_modules\har-validator\lib\schemas\timings.json Unexpected token (2:12)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (2:12)
    at Parser.pp$4.raise (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:2221:15)
    at Parser.pp.unexpected (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:603:10)
    at Parser.pp.semicolon (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:581:61)
    at Parser.pp$1.parseExpressionStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:966:10)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:730:24)
    at Parser.pp$1.parseBlock (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:981:25)
    at Parser.pp$1.parseStatement (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:709:33)
    at Parser.pp$1.parseTopLevel (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:638:25)
    at Parser.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:516:17)
    at Object.parse (E:\Projets\pkmn-go\node_modules\acorn\dist\acorn.js:3098:39)
 @ ./~/har-validator/lib/schemas/index.js 18:11-36
ERROR in ./~/tunnel-agent/index.js
Module not found: Error: Cannot resolve module 'net' in E:\Projets\pkmn-go\node_modules\tunnel-agent
resolve module net in E:\Projets\pkmn-go\node_modules\tunnel-agent
  looking for modules in E:\Projets\pkmn-go\node_modules
    resolve 'file' net in E:\Projets\pkmn-go\node_modules
      resolve file
        E:\Projets\pkmn-go\node_modules\net doesn't exist
        E:\Projets\pkmn-go\node_modules\net.js doesn't exist
        E:\Projets\pkmn-go\node_modules\net.jsx doesn't exist
    E:\Projets\pkmn-go\node_modules\net doesn't exist (module as directory)
[E:\Projets\pkmn-go\node_modules\net]
[E:\Projets\pkmn-go\node_modules\net.js]
[E:\Projets\pkmn-go\node_modules\net.jsx]
[E:\Projets\pkmn-go\node_modules\net]
 @ ./~/tunnel-agent/index.js 3:10-24
ERROR in ./~/tunnel-agent/index.js
Module not found: Error: Cannot resolve module 'tls' in E:\Projets\pkmn-go\node_modules\tunnel-agent
resolve module tls in E:\Projets\pkmn-go\node_modules\tunnel-agent
  looking for modules in E:\Projets\pkmn-go\node_modules
    resolve 'file' tls in E:\Projets\pkmn-go\node_modules
      resolve file
        E:\Projets\pkmn-go\node_modules\tls doesn't exist
        E:\Projets\pkmn-go\node_modules\tls.js doesn't exist
        E:\Projets\pkmn-go\node_modules\tls.jsx doesn't exist
    E:\Projets\pkmn-go\node_modules\tls doesn't exist (module as directory)
[E:\Projets\pkmn-go\node_modules\tls]
[E:\Projets\pkmn-go\node_modules\tls.js]
[E:\Projets\pkmn-go\node_modules\tls.jsx]
[E:\Projets\pkmn-go\node_modules\tls]
 @ ./~/tunnel-agent/index.js 4:10-24

Sorry for the huge copy-pasta. Any ideas ?

In order to use pogobuf with webpack, just put this in webpack.config.js:
  node: {
    fs: "empty",
    tls: "empty",
    net: "empty"
  }

I also had to add json-loader to compile properly.

I added the entry @mbeaudru mentioned but more missing modules popped up afterwards:
These dependencies were not found:

* jodid25519 in ./~/sshpk/lib/private-key.js, ./~/sshpk/lib/dhe.js
* jsbn in ./~/sshpk/lib/dhe.js
* ecc-jsbn in ./~/sshpk/lib/dhe.js
* bcrypt-pbkdf in ./~/sshpk/lib/formats/ssh-private.js
* ecc-jsbn/lib/ec in ./~/sshpk/lib/dhe.js

I tried adding them to @mbeaudru's node object but they are still popping up.
Does json-loader resolve these dependencies?

Dumb question, but did you try to install sshpk ?

authors: mbeaudru travisfisher

repo: cyraxx/pogobuf


text:
Support New TSS (Thread Specific Storage) API of Python 3.7

TLS (Thread Local Storage) API will be deprecated as https://github.com/python/cpython/blob/731e18901484c75b60167a06a0ba0719a6d4827d/Include/pythread.h#L81-L92 and TSS (Thread Specific Storage) API is newly added as https://github.com/python/cpython/blob/731e18901484c75b60167a06a0ba0719a6d4827d/Include/pythread.h#L98-L142.
see also https://www.python.org/dev/peps/pep-0539/
pythread.pxd does not support it yet https://github.com/cython/cython/blob/31752522d88f03642fb9c17474135cb16d2fe474/Cython/Includes/cpython/pythread.pxd.

Pull request welcome.
This probably also means that we should update the TLS usage inside of Cython itself, specifically in the FastGil code in ModuleSetupCode.c.

Is there a way to use preprocessors like #if PY_VERSION_HEX >= 0x03070000 in pythread.pxd?

You don't have to. Just declare them there. Users will have to take care that they are only used when available.
That being said, it's probably possible to backport the API to older CPython versions by defining Py_tss_t as a simple struct containing an int as native key, and then using that as key value in the old TLS C-API. There is already lots of compatibility code in ModuleSetupCode.c, so it shouldn't hurt much to add it there.

fixed via https://github.com/cython/cython/pull/1939

source: gharchive/issue

authors: scoder sonots

repo: cython/cython

license_type: permissive

license_source: bigquery


text:
Plugin 'Cython.Coverage.Plugin' did not provide a file reporter

Ran into the following issue (snippet below) with this relatively simple (in it's current stage a stub) library.
$ coverage report -m
Plugin 'Cython.Coverage.Plugin' did not provide a file reporter for '/home/travis/build/jakirkham/cybuffer/src/cybuffer.pyx'.
The command "coverage report -m" exited with 1.

Using Python 3.7.0, Cython 0.29, Coverage 4.5.2, and pytest 3.10.1. Also saw this on Python 2.7 and Python 3.5-3.7 with other dependencies at the same version. More details available in the build logs.

Was missing this line.
This fixes the failure, but does not report any coverage for the Cython file. Will save the latter discussion for another issue.
coverage run --append --source . setup.py build_ext --inplace

ref: https://travis-ci.com/jakirkham/cybuffer/jobs/158609206#L903


text:
How can I generate an AST?

Hi,
How can I generate an abstract syntax tree from some Cython code?
Also, is there a way to generate code directly from that AST, instead of running Cython.Build.cythonize and internally generating another AST?
I need to get a lot of information on a module, such as weather it's C or C++, what it imports, what the docstring is, and other things.
Thanks

You probably want to insert something into the pipeline at an early stage just after parsing?

Sounds good, but how do I do that? Is there an example somewhere?

Look at the TreeFragment class. It builds its own partial pipeline. Also look at the PrintTree class in Pipeline.py.
Closing this since it's not a bug/issue in Cython.

authors: Keithcat1 da-woods scoder


text:
[BUG] Compiled function can't be used with sicpy ode.

Describe the bug
Functions compiled with cython 3.0.0 cannot be used with the fortran solvers from scipy through the ode interface.
It seems the fortran don't detect the right number of argument.
It used to work with cython 0.29.X.
Could be related to #1232.
Code to reproduce the behaviour:
%%cython

def f(t, x):
    return x

import scipy.integrate
ode = scipy.integrate.ode(f)
ode.set_integrator('lsoda')
ode.set_initial_value([1], 0)
ode.integrate(1)

Output (truncated):
TypeError: f() takes exactly 2 positional arguments (1 given)

Expected behaviour
I expected to be able to use compiled functions with ode.
OS
Linux
Python version
3.10.0
Cython version
3.0.0
Additional context
No response

I'd try setting the compiler detective @cython.binding(False). It'd still be worth investigating but that might be a workaround

Thank you, it worked.

Any idea why this happens? Numpy is seeing an opposite problem with bindings and this signature. It fails on 0.29.36 and works on 3.0.0:
def poisson(self, lam=1.0, size=None):
    ...

xref numpy/numpy#24429

Any idea why this happens?

I had a brief go at trying to debug it but didn't get to far. My suspicion is that it's an issue with how f2py wraps callables, but I think I'd need to compile everything with debug flags to find out. I think we've also seen similar issues with PyQt and signals/slots.

Numpy is seeing an opposite problem with bindings and this signature. It fails on 0.29.36 and works on 3.0.0:
def poisson(self, lam=1.0, size=None):
    ...

xref numpy/numpy#24429

I don't think that's directly related to this. One of the key advantages with the binding feature is it exposes things like __defaults__ for better introspection, so it completely makes sense that you'd get better signature information with it.
binding isn't a new Cython 3 feature - it's just on by default in Cython 3. So potentially you could turn it on universally and get better introspection with 0.29.x.

Maybe I should open a separate issue. The problem is that when we turned bindings on universally, the error in introspection appeared in 0.29.36

authors: Ericgig da-woods mattip


text:
Feature/svg legend

General information
Associated issues: #76
Checklist
Author:

[ ] One or more reviewers have been assigned.
[ ] Automated tests have been included in this pull request, if possible, for the new feature(s) or bug fix.
[ ] The associated GitHub issues are included (above).
[ ] Notes have been included (below).

Reviewers:

[ ] All automated checks are passing (green check next to latest commit).
[ ] At least one reviewer has signed off on the pull request.  Reviewers have two business days to review the pull request, after which the author may merge in the pull request unilaterally.

Notes
This PR makes the following changes...

Replaces the cy.js based legend with a new legend using SVG.
The legend can be exported as an SVG image file. (This action still has to be added to the share menu, but I did test it and it works).
Moves the legend to the bottom-right. The legend overlays the network but is quite small so it shouldn't obscure too much. The legend can be collapsed down to a floating action button.

https://user-images.githubusercontent.com/5350528/228658676-015e26f3-92a3-445a-983f-ddc52869d7c2.mov

This looks nice
I've only yet looked at the video so far, but here are some ideas that could improve some areas of the legend:
(1) The blue colour of the legend button, when it's collapsed, makes it look like it's not the legend anymore.  It just feels a bit weird.  It might be better if it's the same white colour as the legend's ordinary background.  Another idea would be to colour the button with the same gradient as the legend entry.  That gives a nice signifier that you'll get information about the colours when you click the collapsed button.
(2) It's useful to see the legend up front, when the user first gets to the results page.  Once you start interacting with the network, you probably would often collapse the legend.   You've seen it already and it takes up space more noticeably, for instance, when you zoom in.  A simple small improvement would be to automatically collapse the legend once you start interacting with the network, like if you zoom or pan.  You only need to see it once, after all.
(3) I'm not sure the 'Legend' title is strictly necessary.  Figures in papers don't often use a 'Legend' title.  That could save a little bit of space.

I don't want to use the same color as the nodes for the button color,
because I think it will make the button look like a node. I think it needs
to have a distinct color from the network. Either black like the
panels/toolbars for consistency, or white like the network background. I'll
try both and see how it looks.
I agree that it should be expanded initially.
I'm ok to remove the "Legend" title.
Thanks!
Mike.
On Thu, Mar 30, 2023 at 9:40 AM Max Franz @.***> wrote:

This looks nice
I've only yet looked at the video so far, but here are some ideas that
could improve some areas of the legend:
(1) The blue colour of the legend button, when it's collapsed, makes it
look like it's not the legend anymore. It just feels a bit weird. It might
be better if it's the same white colour as the legend's ordinary
background. Another idea would be to colour the button with the same
gradient as the legend entry. That gives a nice signifier that you'll get
information about the colours when you click the collapsed button.
(2) It's useful to see the legend up front, when the user first gets to
the results page. Once you start interacting with the network, you probably
would often collapse the legend. You've seen it already and it takes up
space more noticeably, for instance, when you zoom in. A simple small
improvement would be to automatically collapse the legend once you start
interacting with the network, like if you zoom or pan. You only need to see
it once, after all.
(3) I'm not sure the 'Legend' title is strictly necessary. Figures in
papers don't often use a 'Legend' title. That could save a little bit of
space.
—
Reply to this email directly, view it on GitHub
https://github.com/cytoscape/enrichment-map-webapp/pull/91#issuecomment-1490325378,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABI2JAG7VLSL3MBOTITVJGLW6WENFANCNFSM6AAAAAAWML6B7E
.
You are receiving this because you authored the thread.Message ID:
@.***>

I don't want to use the same color as the nodes for the button color,
because I think it will make the button look like a node.

Good point

Screenshots with a white button and background (actually its slightly grey).

Here is with a dark color...

Here is without the "Legend" title...  the empty space looks kind of weird IMO.

I like the light-grey background a little bit more (less intrusive on the network canvas, looks more like a legend and not another panel), but I prefer the dark round button (easier to find and differentiate from nodes).
Yes, it's weird without the "Legend" title.

Either colour is an improvement over blue.
To clarify:  The title, 'Enrichment (NES)', should go up at the very top, beside the chevron, if we're looking to save space.  It doesn't need to be so far down if the NES is the only thing in the legend.

I'm going with the light-grey.
Moving "Expression (NES)" up next to the button requires the popup to be wider.

Another option is to move "Expression" to the top and keep "NES" on the color scale...

Personally I think it was fine with "Legend" at the top.

After thinking more about it: "Legend" tells the user what this little panel does. Without it, the user may wonder whether this may have another funcion: Is this another chart? Can I interact with it? Etc.

Why don’t we go with the simplest thing for now, which is to go with Mike’s ‘Legend’ title?  What we have now is much better than what we had before.
I’ll log the further enhancement ideas (e.g. auto-collapse) so that we have them at hand.  If we run into issues re. legends or space in future, then we’ll already have some potential solutions to draw on.

source: gharchive/pull-request

authors: chrtannus maxkfranz mikekucera

repo: cytoscape/enrichment-map-webapp

license: MIT

license_source: github-api


text:
Win Support

Seeing nothing that prevents this from getting merged.
Post-Merge

Tracking issue for fopen64 implementation!

@steffengy I've just got an email from this thread asking if I've reviewed this PR and cznic/cc#96 but I cannot see the message here. Anyway, yes, this PR is already merged and I've reviewed cznic/cc#96 18 hours ago, according to Github. Since then it's ready to be merged.

Okay I'll merge it to then. The mail is over from https://github.com/cznic/ccir/pull/2 .
Just asking because I did get comments but no LGTM from you :)

Just asking because I did get comments but no LGTM from you :)

Right, sorry. Will try to do better next time ;-)

authors: cznic steffengy

repo: cznic/virtual


text:
Merge annsk.alignment

I tried to merge this extension to Transformer but i can't. Can you do it pls?

Why would you want to merge another extension when you can just install it separately?

Well, I just want to keep the amount of extension i have to install to a minimum and less settings i have to find. Additionally, the "Align to Cursor" kinda broken.

You can create your own extension pack to better help manage your own installs.  I did that for myself as an example - https://marketplace.visualstudio.com/items?itemName=dakara.dakara-editor-core-pack
The Align To Cursor aligns only text to the right side of the cursor to the position of the cursor where there is a gap of empty space.  It doesn't parse the text and try to figure out the syntactic character separators.

authors: d-akara duckimann

repo: d-akara/vscode-extension-transformer


text:
The service code is a bit redundant

These API services really ought to be a class so that the near identical code between them for basic CRUD could be abstracted and cut back on redundancies

That might be all well and good for fetch 1 and delete, but the fetch many, create, and update functions are fairly unique between different services, and so are some fetch 1 and delete functions if there's a parent, such as DELETE categories/:categoryId/subcategories/:id. If 70% of the functions on average have to be overridden in child classes then the benefits aren't sufficient to justify the effort.
Alternatively we could, in fetch many for example, technically pass an object (or null) to generate the query string as needed and where applicable, but that shifts the onus of knowing what keys are valid from the service onto the calling component

repo: d-hayman/Warehome


text:
[bug] Reviews created on Windows store file paths incompatible with Linux

Reviews created on Windows store file paths incompatible with WSL2
Description
When the code reviews created in Windows are opened on the Windows subsystem for Linux (Ubuntu), a double-click on a review item results in a error "Cannot not open file: '/home/user/repo/\app\path\file.ext': File does not exist"
Yes, the error message contains double negation, but this is a secondary issue.
Reproduction

Open VS Code on Windows and make some code review comments on separate files. Commit the code review file.
Open VS Code and access files on WSL2 (Ubuntu was used) and click on any of the code review comments.
Observe the error

Error message

Cannot not open file: '/home/user/repo/\app\path\file.ext': File does not exist

🌍 Your Environment
VS Code on Windows 10 for creating code review items.
VS Code on Windows 11 accessing files on WSL for viewing code review items.
Workaround
Replacing backslashes with slashes in the code review CSV file allows to open the files on VS Code.

Temporary, you can open the csv on VS Code and switch the "End of line Sequence" of the file by clicking on the LF / CRLF:

Mac: should be "LF"
Windows: should be "CRLF"

Thanks for your comment.
Unfortunately I won't find time within the next weeks or even month to investigate this further.
Also, I can't really test it as I am working with a mac.
Long story short: I would be happy to receive a pull request for review. 🙂

authors: Jakartoine d-koppenhagen haybatov

repo: d-koppenhagen/vscode-code-review


text:
🛑 Staging Homologation API is down

In 89877af, Staging Homologation API ($STAGING_HOMOLOGATION_API) was down:

HTTP code: 503
Response time: 867 ms

Resolved: Staging Homologation API is back up in 065bdeb.


text:
[Feature Request- Factory Automation] Auto-buy rubber if short.

The Factory Automation script should attempt to purchase Rubber if it's short.

Buying from the shop is out of scope for the factory script. (It's nearly impossible to do, and can't be done as efficiently because AI can't right-click.)

Yah, I noticed this when trying to make that script myself.. kinda annoying, hopefully the revamp will solve things.

The easiest automatic way to buy rubber is with an auto clicker script, but it's slow. With the infinite rubber skill, you can just right-click 10 times and get plenty of rubber to tide you over for a while.


text:
能否忽略子目录下的文件夹

比如我想忽略所有目录下名为“pycache”的文件夹而不只是根目录下的
按现在的方式的话只能扫描完在设置中一个个添加这些文件夹，然后重新扫描一遍

我觉得你可以先删除，扫描完之后再加入进去呢~

其实就是不支持写正则表达式吧

设置偏好后，为啥不生效？

比如设置忽略的文件后，不生效

比如我想忽略所有目录下名为“pycache”的文件夹而不只是根目录下的 按现在的方式的话只能扫描完在设置中一个个添加这些文件夹，然后重新扫描一遍

你好，我基于该软件二次开发出了 Annotree：一款生成带注释的目录树工具 ✨✨✨ | 帮助你高效地编写技术文档，大家有目录树需求的，欢迎来看看！详情见: #79


text:
Add basic array methods for iterables.

What do you think about adding the equivalents of basic array methods (array.filter, array.sort, etc.), but for iterables? Yes, these are all roughly equivalent to converting to an array with Array.from first, but I think it’s convenient (and hopefully faster) to have dedicated methods.
For example:
const set = new Set([1, 2, 3]);
every(set, d => d > 0); // true

Another possibility to consider is whether we want to try to preserve the input type rather than always returning an Array. I think we could do that for typed arrays, Set, and Map, if we wanted. But I worry that it might be a little confusing.
Also, we should note in the documentation that these methods behave slightly different than the array methods with respect to sparse arrays: because the basic array methods skip missing entries, but array iterators yield undefined values.

I've often been wanting to type (iterator).filter(…) as a chained method. I like the fact that the verb comes after the noun/subject. filter(iterator, …) is not as good, but I suppose it's only a question of subclassing Set or Map? Would d3.group use an "extended" Map?

I’d prefer to use the standards than to create new classes to avoid needing to convert to or from.
The proposed pipeline operator will let you use standard functions with nice chaining syntax. There’s even a partial application proposal but you can also wrap with an arrow function.

Added tests; this should be ready for review.
I thought more about type preservation but I like the conceptual simplicity of always returning an array. You can use array.filter or array.map if you want to preserve typed array, or pass to new Set or new Map for collections.

I also thought about lodash _.matches and _.property style shorthand, but I feel that now that JavaScript supports arrow functions,
filter(objects, matches({a: 4}))
map(objects, property("a.b"))

is just a more cryptic form of
filter(objects, o => o.a === 4)
map(objects, o => o.a.b)

And especially with things like optional chaining now in the language there’s no reason to create a string-based alternative to native syntax.

authors: Fil mbostock

license: isc


text:
Rollup and color methods from scale are unnecessarily being included

Hi,
I'm using Rollup to create a d3 bundle. I'm only importing the following modules:
export {
  scaleUtc,
  scaleTime,
  scaleLinear,
  scaleBand,
  scalePoint
} from "d3-scale";
export * from "d3-quadtree";

What I'm seeing is that the color related methods from d3-scale are included in my bundle: all the category files, cubehelix, rainbow, and viridis, and then of course, their dependencies. These still get included even when I reduce my scale imports to just one of the above modules. Deleting the export statements from index.js does prevent them from being imported, which serves to confirm that they are coming from d3-scale and not elsewhere. This is bugging me because, without these, I could eliminate d3-color from my bundle and save a fair amount of space.
What I'm wondering is if it is possible to stop these unnecessary color methods from being imported? I've not been able to track down exactly where they are being imported from and whether this is intentional that they always get included or a bug. If they are being brought in via some circular dependency, perhaps it is possible to change the imports and resolve this?

Sorry, but this is a Rollup issue, not a D3 issue. Rollup has made a lot of improvements recently to its tree-shaking algorithm, but it seems like it’s still not smart enough to tree-shake all the dead code here.
You can help Rollup (at the cost of making your code slightly more brittle to version upgrades) by importing the file that defaults scaleLinear (and the other scales) directly rather than using the default entry. For example, this produces a 76KB bundle:
export {
  scaleLinear
} from "d3-scale";

But this produces a 40KB bundle:
export {
  default as scaleLinear
} from "d3-scale/src/linear";

It’s possible to rewrite the D3 code to make it easier for Rollup to determine that it has no side-effects, and therefore tree-shake more effectively, but I’m not going to rewrite the code solely for the benefit of Rollup’s tree-shaking algorithm. (If an unrelated improvement has the side-effect of making it easier for Rollup, that’d be welcome, however.)
I expect Rollup will continue to get better but you’ll probably need to use workarounds like the above if you want smaller bundles.

Sweet, that certainly does what I need for now. Thanks!

authors: mbostock nonmetalhail


text:
possible to use the UI on existing vpn server installation ?

i see that the project comes with its own docker image which i assume contains also the ovpn server part. but it is possible to use it on an existing environment that runs outside docker? and if so, should those 2 environments share the same filesystems or can the 2 run on separate machines (ie. gui on server 1 and ovpn legacy env on server 2 ) ?
cheers

Hi @dberardo-com,
Yes it is possible. You could clone repo, then go into ~/build/ directory and run ./standalone-install.sh script for standalone build and installation.
The issue #26  has installation steps and logs.
Please be aware that standalone installation is currently supports supported Debian linux only.
Post installation and UI start you have to go into "Configuration > OpenVPN UI" and set "OpenVPN ConfigPath" and "Easy-RSA ConfigPath" options accordingly.

Note that UI, at the moment takes server.conf and client.conf from /etc/openvpn/config subdirectory, so you have to copy files there and adjust server start config accordingly.
In version 1 I'll update UI to take config just from the /etc/openvpn dir.

As for the different servers - this may work with OpenVPN server configuration and EasyRSA pki dir mounted over NFS to the server where OpenVPN UI is running. However, it was never tested. If you would test, please let me know results.

There are several minor issues, I discovered, when installing this on my standalone vpn server. If I remember right, this where

location of server.conf and client conf - solved this using links
required scripts in location /opt/scripts - solved using links
required openvpn-ui location at /opt/openvpn-ui - solved using links
scripts in "scripts" directory to i.e. restart openvpn only rely on docker - edited them ti restart service
maybe more, don't remember, fixed several issues on the fly

but - cool project and really useful! Thanks d3vilh!

Hi @thomas2108 thank you for the reporting.
I'll keep the issue open until documentation update in main branch.

I am also interested in this. I already have a working OpenVPN server with multiple users. I need a user interface to manage them properly.

I already have a working OpenVPN server with multiple users.
Hi @jav-12 do you mean different server instances running on the same server?
If so, you could run different OpenVPN-Ui instances as well for every server instance you have.
All you need is to change ports and paths in openvpn-ui/conf/app.conf accordingly.

Yes. I want to use the GUI on the server already used for the VPN.

If you have Docker env available on the server, you could run just openvpn-ui container as Dockerfile or Docker-compose with volumes: setup towards your server and easyrsa configuration files.
Alternatively is to build ui with ./standalone-install.sh script.
It will build binaries for your arch and distro version, then you can use those binaries to run as a service or as application without any issue.
For both cases it is better to use some test environment before applying the solution on Prod environment.

If you have Docker env available on the server, you could run just openvpn-ui container as Dockerfile or Docker-compose with volumes: setup towards your server and easyrsa configuration files.
Alternatively is to build ui with ./standalone-install.sh script. It will build binaries for your arch and distro version, then you can use those binaries to run as a service or as application without any issue.
For both cases it is better to use some test environment before applying the solution on Prod environment.

hello, im also trying to install just the web UI. I have installed OpenVPN with PiVPN with default settings. Where and how should I set up the volumes exactly?

hello, im also trying to install just the web UI. I have installed OpenVPN with PiVPN with default settings. Where and how should I set up the volumes exactly?

Hi @null-p01ntr ,
You have to follow the standalone installation guide . Be precise with username and password vars.
Then just login and modify openvpnUI parameters to set where your openvpn server config dir is and easyrsa home directory.
I don't use PiVPN and Rspberry-Gateway  is neat even on PiZero boards.


text:
Replace neotree with treemacs

https://github.com/Alexander-Miller/treemacs

Done


text:
CMakeLists.txt : target_compile_features no longer work as expected

target_compile_features(vaca PUBLIC cxx_std_14) will no longer work as you expected. When you wrote this line C++14 was the latest, but now it's C++17 or even C++20. For example, the GCC 12.2.0 compiler of MSYS2 MINGW64 targets C++17 by default. Since C++17 is greater than C++14 and cxx_std_14 means at least C++14 so -std=c++14 will not be added and it will default to C++17. There will be warning about the register keyword is not allowed on C++17.
https://cmake.org/cmake/help/latest/command/target_compile_features.html
The solution as the document said is explicitly forcing C++14 with:
set(CMAKE_CXX_STANDARD_REQUIRED ON)
set(CMAKE_CXX_STANDARD 14)

The target_compile_features line could be removed.

Actually I'm used to CMAKE_CXX_STANDARD  and CMAKE_CXX_STANDARD_REQUIRED in other of my libraries (clip) but I'm not sure why I used target_compile_features() here.
Anyway removing the usage of the old register keyword fixed some issues related to this.

authors: dacap iahung

repo: dacap/vaca

license: mit


text:
Make into a better library

Convert the existing code into a friendly library.

Change the current code to use the simpler version as well.

This issue is a bit vague.  I will close it and create specific issues for work to be done.


text:
Provide the transformation as a helper function?

Hello,
One question, will it be possible to provide the transform of markdown to bbcode as a helper function? That way we can use only the code of the transform and not need the full component if not needed?
Thanks,
Jaume.

By pasting the MarkdownLabel control:
var mdlabel = get_tree().get_root().get_child(0).get_node("MarkdownLabel")

Alternatively, without pasting the control:
var mdlabel = preload("res://addons/markdownlabel/markdownlabel.gd").new()

This way, you can access the MarkdownLabel class.
It seems that you can convert a markdown string to a BBCode string by calling the mdlabel._convert_markdown method.
Thanks to the GDScript language specification.

Closing this since direct conversion is not the purpose of this addon. It can be easily achieved by instancing the class as explained in the previous comment though :)

authors: Dracks daenvil uniras

repo: daenvil/MarkdownLabel


text:
.settings in wrong help

Command .settings is in the help of mpd not in the help of internals. (im devel-Branch)

Fixed with https://github.com/dafoxia/mumble-ruby-pluginbot/commit/146c35006ea61142ae00891b43c5bf834c6c70db

Did you add it somewhere else in the help?

It was already in .internals...
.settings in mpd was probably a leftover from earlier development.

Oh okay.

authors: Natenom tu-maurice

repo: dafoxia/mumble-ruby-pluginbot


text:
Office 365 Regex credit card

Hi,
I tried following command.
Invoke-SelfSearch -Remote -ExchHostname outlook.office365.com -Regex '.*3[47][0-9]{13}.*|.*(?:5[15][0-9]{2}|222[1-9]|22[3-9][0-9]|2[3-6][09]{2}|27[01][0-9]|2720)[0-9]{12}.*|.*4[0-9]{12}(?:[09]{3}).*' -CheckAttachments -MailsPerUser 1000
But it Returns nothing. Any idea? There are a lot of mails with credit Cards in my Mailbox.
It seems that it does not working. In my PowerShell It tries to connect and then Exit
[] Trying Exchange version Exchange2010
[] Using EWS URL https://outlook.office365.com/EWS/Exchange.asmx

Hey man, I won't be able to troubleshoot this until next week but the first thing I would mention is that the regex is looking for VISA, MasterCard, and American Express numbers. So if the cards in your mailbox aren't one of those then it won't find it. Also, are the card numbers in the body of the email or in the attachments. I see you are using the -CheckAttachments option.

Hi,
thanks for your response. The regex is not the problem. I sent myself an email with subject "Password" and also with "Password" in the Body and just tried the default settings. But I think that the Connection to EWS is not working or the session is just closing because after
[] Using EWS URL https://outlook.office365.com/EWS/Exchange.asmx
Nothing happens... In your Blogpost there is a screenshot with "Now searching..." But I never see something I like that...

Oh that is an odd issue. I would also assume that the connection isn't working to EWS... At that point in the script it should actually be trying to bind to the Inbox. I will check it out next week and see if I can replicate the issue.

Any updates?

I just tested it and it seems to be working for me. I used the following command to search for 'password' against an O365 account and it found my test email with the term password in the body.

PS C:\> Invoke-SelfSearch -ExchHostname outlook.office365.com -Terms "*password*" -Remote -Mailbox r@testdomainonO365.com

[*] Trying Exchange version Exchange2010

cmdlet Get-Credential at command pipeline position 1
Supply values for the following parameters:
Credential
[*] Using EWS URL https://outlook.office365.com/EWS/Exchange.asmx
[***] Found folder: Inbox
[*] Now searching mailbox: r@testdomainonO365.com for the terms *password*.

Sender                                      ReceivedBy                             Subject          Body
------                                        ------                                       ------             ------
beau@blackhillsinfosec.com   r@testdomainonO365.com    Test Email   This message has a password in it...

If authentication was failing for you I believe you would see at least an error stating the request failed so it's probably not that. What version of PowerShell are you running and what OS? Also, can you try logging directly in to EWS with a browser at https://outlook.office365.com/EWS/Exchange.asmx? You should see the Service page after logging in there if it was successful.

Ah, I think i found the problem. I use a system with german language and german office 365. If iuse use the -folder all parameter it works. Seems it does not work because of the default folder "inbox".

authors: Wipsly dafthack

repo: dafthack/MailSniper


text:
Continued enhancements for x/.../sam package

PR here https://github.com/dagger/dagger/pull/2435/

[ ] tests
[ ] ???

cc @munichbughunter

Any progress on this issues?

Not at the moment. But there will be adjustments so that the package also works via TCP connection.

authors: TomChv jpadams munichbughunter

repo: dagger/dagger


text:
Basic namespacing in API

Overview
In the new cloak core API, cache volumes are associated with a key provided by the client. Buildkit does not provide a facility for namespacing these keys, so by default every client that looks up the cache volume foo on the same engine, will use the same cache volume. This is not practical, and will probably lead to ad-hoc namespacing solutions. It would be better for Dagger itself to handle namespacing. But how?
As explained by @vito (see original discussion below), the answer is probably namespacing by something roughly equivalent to a "project". This issue is to discuss whether this feature is actually needed, and if so how to design it.
Original discussion
As discussed in https://github.com/dagger/dagger/issues/3287#issuecomment-1276822308_ :

I agree that we'll need scoping really soon if not on day 1. I wonder if it's closer to "project" than "user" though. I may be using the same machine/user to work on multiple projects that all use Dagger and it'd be awkward if they collided with one another.

You are right. I see two possible paths here:

We introduce the smallest possible concept of namespace, just enough for have basic scoping, and improve later.
We defer namespacing entirely. We take the leap of faith that we can introduce it later and not break the UX (similar to extensions).

I'm leaning towards option 1. Mostly because it seems really hard to ship a UX with global scoping, then change it to support namespacing that can support something like a project. I could be wrong though.
Note: I think @vito 's use of "project" is roughly equivalent to @sipsma 's use of "session" in this discussion, is this accurate?

In some cases you might want to share caches across projects though, for example it should be safe to share one big Go build/module cache.

This part I'm OK with deferring to later. I think if we have a good project scoping primitive, we can find a way to add this feature later.

Also one thing worth clarifying: we're aiming to prevent cache collisions just from a usability perspective, not a security perspective, right? So it should be OK to let the user provide the scope key. Multiple untrusted tenants on the same Buildkit is never a safe thing to do anyway.

IMO we need a UX primitive that works in a single-tenant and multi-tenant context. Totally agree that we don't want to actually make a buildkit instance multi-tenant (at least not with untrusted tenants) but we might want to implement multi-tenancy at a higher level (with cloud etc). So if the UX has a hook for that, it would be ideal.

"Session" and the use of "project" here are related but not entirely the same.
Session is an already existing concept today. It's how buildkit scopes certain resources (localdirs, gateway containers, among others). Sessions have a random ID (they also have a name you can set, but that's different than the ID) and are tied to a single client connection. Once that connection is closed, the session is gone.

Confusingly some resources associated with it are freed (gateway containers) but others have more complicated stories (local dirs)

Project as it's used here (and as I understand it, correct me if wrong) would be more persistent than a session because it would be scoping cache dirs. If you use a cache dir, disconnect and then reconnect, it should be possible for the cache dir to still exist (as contrasted with e.g. gateway containers where they are gone when the session ends).
The direction I've been leaning more and more towards for a while is that the session concept we get from Buildkit is really hard to work with and often not what we want. What we really want is more like the "project" concept above where resources are less ephemeral. You should be able to let a service keep running even if you disconnect.

I actually asked Buildkit maintainers about whether they'd want this specifically a few months ago, they said no.

The vague, incomplete idea that's been knocking around my head is that we maybe should invent our own "dagger session" concept which encompasses not only services and local dirs (like Buildkit sessions) but probably also the loaded schema. Can add cache dirs to that too. Dagger sessions would have some degree of persistence.
If we wanted to call "dagger session" a project instead that'd make sense to me in isolation, we just need to sort of the conflicts with the existing concept called project. The two concepts have overlap in that they may both be associated with a schema, but in other ways they are not really the same. I'd actually be in favor of calling the "persistent-session thing" a "project" and the "config for an extension" (i.e. what's currently called "project") something else.

In order to avoid confusion with existing definitions of "session" and "project", for the purpose of this discussion I propose using the more neutral and functional "namespace". Analogy is eg. to kubernetes namespaces, and perhaps docker context?
Doesn't have to be the actual name we use, it just seems useful to have our own name for now, to avoid interference.

kubernetes namespaces

containerd has namespaces too, which could be especially relevant to us if we decide to use the containerd worker

I see two possible paths here:

We introduce the smallest possible concept of namespace, just enough for have basic scoping, and improve later.
We defer namespacing entirely. We take the leap of faith that we can introduce it later and not break the UX (similar to extensions).

Update: we have gone with option 2 (defer namespace entirely). Now we are facing an urgent need to introduce namespacing, in order to implement persistence of cache volumes in Dagger Cloud.
I am resurrecting this thread to make sure we avoid breaking the UX.

@shykes What is the connection between namespaces and cache volume syncing? I can imagine updating the cache volume API to support settings that would impact the cloud's sync of them, but I don't see yet the connection point with namespacing, which has more to do with multitenancy in my mind.

@shykes What is the connection between namespaces and cache volume syncing? I can imagine updating the cache volume API to support settings that would impact the cloud's sync of them, but I don't see yet the connection point with namespacing, which has more to do with multitenancy in my mind.

The connection is that when creating a cache volume in your code, you need to give it a name; that name is chosen with an assumption that cache volumes are namespaced. How namespacing works exactly, will impact when my cache volume is reused, and when it's not.
My understanding is that, in the current implementation of Dagger Cloud, cache volume names are global to the entire Cloud organization. So if I run 5 unrelated pipelines, all with a cache volume named "npm", they will be synced as a single volume. This is leading to a) stopgaps where eg. @jpadams is writing code with globally unique cache volume names such as customer_name_2, and b) cloud team is designing a cloud-specific way to namespace cache volumes.
Instead of designing a cloud-specific way to namespace cache volumes, I would like us to design namespacing platform-wide, then implement it in Cloud.

So if I run 5 unrelated pipelines, all with a cache volume named "npm", they will be synced as a single volume. This is leading to a) stopgaps where eg. @jpadams is writing code with globally unique cache volume names such as customer_name_2,

I'm still missing how "cache volumes are shared" leads to us needing to namespace by customer_name_*. They just seem completely unrelated still. @jpadams can you help fill in the gaps here?
To be clear, I'm not saying we don't want some type of namespacing ever (namespacing by npm version could be a nice feature to have for this specific case), it just feels independent of cloud synchronization.

b) cloud team is designing a cloud-specific way to namespace cache volumes.

@marcosnils can you clarify this point? I understand that in the backend we store layers+cache-mounts under org-specific prefixes, but that's a 100% totally internal implementation detail that users need zero awareness of. Where else does namespacing come into play that it impacts users?

I'm still missing how "cache volumes are shared" leads to us needing to namespace by customer_name_*.

Sorry that was confusing on my part. I’m conflating cross-org global namespacing (unrelated and very temporary cloud issue) with org-wide namespacing, which would require volume names more like teamfoo_projectbar_npm.

Sorry that was confusing on my part. I’m conflating cross-org global namespacing (unrelated and very temporary cloud issue) with org-wide namespacing, which would require volume names more like teamfoo_projectbar_npm.

Oh okay, so we're thinking about when users want to split up their org into separate "sub-orgs" (teams, etc.) and then have independent synchronization of cache mounts?
If so, makes much more sense and I can see the conceptual connection. In terms of the implementation, I believe it still is orthogonal to cloud synchronization right now, but that could change in the future.
Reason being that cloud sync currently works with the low-level name of the cache mount in buildkit, which would be one or two layers of abstraction below namespacing dagger applies. So it shouldn't need any awareness of namespacing, it just syncs based on whatever the namespace "compiles" to in terms of the low-level cache mount name.
One hypothetical situation where a connection point arises is if we want some sort of "tiered" caching that reflects org structures. So if you are in OrgFoo and on TeamBar, which is a part of OrgFoo, then maybe you want to be able to say something like: "give me the npm cache for TeamBar, but if there isn't any then check to see if there's any in OrgFoo".
I would have previously assumed that was a feature a ways off in terms of needing, but maybe not?
Either way, agree it's worth more thought if we are starting down the "org hierarchy" path already. We should also consider whether layer caches would be impacted by this too though (mostly in terms of storage, pruning, pricing, etc.).

Oh okay, so we're thinking about when users want to split up their org into separate "sub-orgs" (teams, etc.) and then have independent synchronization of cache mounts?

One way to describe the problem: when I write code describing my pipeline logic (which includes creating and naming my cache volumes). I shouldn't have to know everything else that runs, or will run in the future, in the same Dagger Cloud org as my pipeline. But if Dagger Cloud considers cache volume names to be global to the org, then that's effectively what I have to do.

cloud sync currently works with the low-level name of the cache mount in buildkit, which would be one or two layers of abstraction below namespacing dagger applies. So it shouldn't need any awareness of namespacing, it just syncs based on whatever the namespace "compiles" to in terms of the low-level cache mount name.

What is an example of such a low-level volume ID, and what other inputs go into "compiling" it? I still feel like when developing my pipeline logic, I need to know how my cache volumes will be namespaced - "don't worry about it" doesn't help me decide how to name my volume.

One way to describe the problem: when I write code describing my pipeline logic (which includes creating and naming my cache volumes). I shouldn't have to know everything else that runs, or will run in the future, in the same Dagger Cloud org as my pipeline. But if Dagger Cloud considers cache volume names to be global to the org, then that's effectively what I have to do.

Agree that's a problem, though I think the solution to that in particular is either (or both) of the following:

There's an API for registering and querying the cache volumes your org uses
Cache volumes can be defined in a Zenith env and vendored out to users in your org from there

But I don't think this has to do with namespacing. Even if you could namespace, you'd still have the same problem of needing to know what exists in your namespace.
Maybe we have different definitions of what namespacing means? From the original description of this issue, I thought it was just a way of scoping the same name under different "contexts" (aka namespaces) for the purposes of isolation and multitenancy, which I think only comes into play here if we want tiered caches from org->team that I mentioned in my previous comment.

What is an example of such a low-level volume ID, and what other inputs go into "compiling" it? I still feel like when developing my pipeline logic, I need to know how my cache volumes will be namespaced - "don't worry about it" doesn't help me decide how to name my volume.

Right now (with no namespacing), the name is a just a hash of the cache volume id, which currently only contains the name the user provided. With namespacing, presumably the namespace hierarchy would also be mixed in to the hash.
I agree that none of that helps you decide what to name your volume, the point was that magicache doesn't need to care about this, it just syncs what it's told to sync. It would only need awareness of namespacing if we want tiered caching, otherwise it's just an opaque ID of a cache volume to sync.

Cache volumes can be defined in a Zenith env and vendored out to users in your org from there

I didn't understand this part, what does "vendored out to users in your org" mean?

I didn't understand this part, what does "vendored out to users in your org" mean?

I'm imagining a top-hat for an org creating their org's standalone environment and including CacheVolume types as part of that environment's API. The low-level plumbing for this would be easy to support, but this doesn't clearly fit into any of the existing entrypoint types (commands, artifacts, shells, etc.), so I suppose we could consider adding a Caches entrypoint type?
The DX would be that when users in that org need to use a cache volume, they just import their org's environment and then can choose cache volumes from it. So if top-hat wants their support pip_cache and gradle_cache, the user would use them in their pipelines either like:

Type-unsafe version: client.Environment().Load("my-org").Cache("pip_cache")
Codegen version: client.MyOrg().PipCache()

Either one of those above would be returning a CacheVolume type, so it would just plug into the rest of the APIs seamlessly. You could also imagine APIs for querying what caches exist, etc.
The overall idea is that Zenith gives orgs a way of cataloguing cache volumes for end-users, which solves the problem of "when I write code describing my pipeline logic (which includes creating and naming my cache volumes). I shouldn't have to know everything else that runs, or will run in the future, in the same Dagger Cloud org as my pipeline." You know what to use because your org's environment tells you what is available to use.
There's actually a bunch more interesting features we could layer on top of something like this, but I'll try to not derail the conversation too much yet :-)

Type-unsafe version: client.Environment().Load("my-org").Cache("pip_cache")
Codegen version: client.MyOrg().PipCache()

Either one of those above would be returning a CacheVolume type, so it would just plug into the rest of the APIs seamlessly. You could also imagine APIs for querying what caches exist, etc.

There's actually a bunch more interesting features we could layer on top of something like this, but I'll try to not derail the conversation too much yet :-)

OK that's pretty cool - perhaps even mindblowing ;) This gives me a glimpse of a deeper integration with Dagger Cloud, where devs can take advantage of its features programmatically. Which I love.
BUT it also scares me a little bit, wouldn't this cause cloud-specific, and org-specific details to leak all over the place into otherwise perfectly portable code?
I feel like we could have the best of both worlds, if we could make this similar to the dynamic secrets API: 1) fully programmatic; but also 2) traces a path to keeping the code portable in the future, with "secret providers".
I feel like your idea for cache volumes isn't quite there, but perhaps it could be?

@shykes Sorry I just remembered this whole thread and realized I never got back

BUT it also scares me a little bit, wouldn't this cause cloud-specific, and org-specific details to leak all over the place into otherwise perfectly portable code?

I'd argue that "cloud-specific, and org-specific details" are not something to be avoided. We absolutely 100% want portable, re-usable environments, but ultimately end-users need to take those environments and use them to their precise needs, and it's great if that's just code too. I guess the analogies would be:

There's lots of re-usable/generic libraries out there for every language, but you still ultimately have to actually import and use those for your specific use case. All of that, both the libraries and the end users code, get committed/published somewhere
There's plenty of shared utils and abstractions in various IaC frameworks, but it's still beneficial to actually publish the code for your specific infra somewhere too that uses those utils.

I feel like we could have the best of both worlds, if we could make this similar to the dynamic secrets API: 1) fully programmatic; but also 2) traces a path to keeping the code portable in the future, with "secret providers".

I can't totally imagine what this would look like in a way that's different than just having the ability to import a cache mount definition that's defined in an external environment, might need clarification on what you are imagining for something like this.

@marcosnils @aluzzardi can you provide additional context on the current status of this?

@sagikazarmark in your case I think you are running into 3 distinct (but related) consequences of lack of namespacing :

Global Go cache. All your invocations of go share the same Go cache because they use the same cache volume name. This is actually OK (I think) because Go supports sharing the same cache across projects.

Concurrent access. In the default sharing configuration, cache volumes allow concurrent writers. So if you invoke go multiple times concurrently, they will hit the same cache volume at the same time. This is also OK (I think) because Go also supports concurrent writers to its global cache.

Last run wins. You are seeing some runs overwrite the result of other runs. I think this is an artifact of Dagger Cloud’s distributed caching implementation. At the moment cache volumes are shared between all engines connected to the same Dagger Cloud organization. The Dagger Cloud organization is a global namespace for cache volumes. Synchronization is done by uploading a snapshot of the entire volume. The last upload wins. There is no merge mechanism at the moment.

In summary: the core namespacing problem is not specific to Dagger Cloud, but it can manifest itself in more visible ways when using Dagger Cloud with cache volumes, and that is what you are encountering.

@shykes makes sense, I'll try that, thanks.
TBH, I'm not that comfortable with bundling all CI steps into a single run though.
For one, I don't get the same feedback on GH right now with checks if I do that.
Also, in some projects it's just not possible to scale the runner vertically (eg. OSS projects), so splitting CI runs is often for performance reasons (I don't have the numbers to back that up though...yet).

@shykes makes sense, I'll try that, thanks.
TBH, I'm not that comfortable with bundling all CI steps into a single run though.
For one, I don't get the same feedback on GH right now with checks if I do that.
Also, in some projects it's just not possible to scale the runner vertically (eg. OSS projects), so splitting CI runs is often for performance reasons (I don't have the numbers to back that up though...yet).

I completely understand. To be clear I only suggested this as a stopgap to alleviate the immediate pain. I absolutely agree that you shouldn’t have to combine runs in order to get the cache volume sharing semantics you expect.

I am deprecating this issue in favor of #7211 , which is more up-to-date and more narrowly focused on cache volumes.

authors: mircubed sagikazarmark shykes sipsma


text:
docs: Add Node.js SDK docs

This commit contains the documentation for the Node.js SDK.
Closes #3640

@aluzzardi should we add a linter for the typescript code snippets?

not sure if we can fix this, but it looks like a line spacing issue here? It isn't a dealbreaker for getting the docs out though.

not sure if we can fix this, but it looks like a line spacing issue here? It isn't a dealbreaker for getting the docs out though.

I think this might be related to our theme CSS. Not sure who knows about this though - maybe @jpadams can comment?

authors: mircubed vikram-dagger


text:
Fix a name clash

The latest sequence exports a fromList method. Use
a qualified import to skirt the clash.
Fixes #52.

Looks good to me. If the tests pass, I say merge it.

I think the tests got stuck so I restarted them.

Weird. The MacOS one seemed to take forever. shrug.

authors: dagit treeowl

repo: dagit/logict-sequence


text:
How to create an action of my C# program function?

Hi there,
I am trying to use the Task Scheduler Managed Wrapper to schedule runing one of my C# function. Is that possible to do? and how? The example shows how to schedule an exe as the following:
            td.Actions.Add(new ExecAction("notepad.exe", "c:\\test.log", null));

But can I schedule to run one of my functions in the same C# program?
Thanks
Feng
Originally posted: 2013-11-06T10:25:23

You can either create an executable that accepts parameters as a means to call your method or you can create a COM Handler using my template (https://taskscheduler.codeplex.com/releases/view/29938) as an independent DLL assembly that contains your method and then use the COMHandlerAction to invoke it from the task.
Originally posted: 2013-11-06T17:50:51

repo: dahall/TaskScheduler


text:
Read-only ShellItemPropertyStore throws System.Runtime.InteropServices.COMException - GPS_BESTEFFORT flag resolves issue

Describe the bug and how to reproduce
Sometimes, attempting to retrieve a property from a ShellItem will result in a System.Runtime.InteropServices.COMException.
(Using ShellItem.Properties.GetValueOrDefault)
I've noticed this happening with .exe files most often (e.g., reading the items in a WinPython or Adobe Acrobat Reader install directory), though it's not consistent and I haven't been able to find the common thread between them.
No current configuration of ShellItemPropertyStore seems to resolve the issue. However, creating a read-only PropertyStore with the GPS_BESTEFFORT flag (instead of the current GPS_DEFAULT) does work.
What code is involved
https://github.com/dahall/Vanara/blob/master/Windows.Shell.Common/ShellProperties/ShellItemPropertyStore.cs
For comparison, the following code results in a COMException* when tested against certain files (for instance, AdobeGenuineSlimInstaller.exe from an Acrobat Reader DC installation):
    public static IDictionary<string, string> GetProperties1(string path)
    {
        var result = new Dictionary<string, string>();

        using var item = new ShellItem(path);
        using var propertyDescriptions = item.GetPropertyDescriptionList();
        foreach (var description in propertyDescriptions.Where(description => item.Properties.ContainsKey(description.PropertyKey)))
        {
            var key = description.CanonicalName;
            var value = item.Properties.GetValueOrDefault(description.PropertyKey)?.ToString();
            if (!string.IsNullOrEmpty(value))
            {
                result.Add(key, value);
            }
        }

        return result;
    }

Whereas this does not:
    public static IDictionary<string, string> GetProperties2(string path)
    {
        var result = new Dictionary<string, string>();

        using var item = new ShellItem(path);
        using var propertyDescriptions = item.GetPropertyDescriptionList();

        var propertyStore = ((IShellItem2)item.IShellItem).GetPropertyStore(GETPROPERTYSTOREFLAGS.GPS_BESTEFFORT, typeof(IPropertyStore).GUID);

        foreach (var description in propertyDescriptions)
        {
            var key = description.CanonicalName;

            using var pv = new PROPVARIANT();
            propertyStore.GetValue(description.PropertyKey, pv);
            var value = description.FormatForDisplay(pv, PROPDESC_FORMAT_FLAGS.PDFF_DEFAULT);

            if (key != null && !string.IsNullOrEmpty(value))
            {
                result.Add(key, value);
            }
        }

        Marshal.ReleaseComObject(propertyStore);

        return result;
    }

*The specific exception is:
System.Runtime.InteropServices.COMException : The specified resource type cannot be found in the image file. (0x80070715)
Stack Trace:
     at Vanara.PInvoke.Shell32.IShellItem2.GetPropertyStore(GETPROPERTYSTOREFLAGS flags, Guid& riid)
     at Vanara.Windows.Shell.ShellItemPropertyStore.GetIPropertyStore()
     at Vanara.Windows.Shell.ReadOnlyPropertyStore.Run[T](Func`2 action)
     at Vanara.Windows.Shell.ReadOnlyPropertyStore.get_Keys()
     at Vanara.Windows.Shell.ReadOnlyPropertyStore.ContainsKey(PROPERTYKEY key)

Expected behavior
The intention of this code was to replace a PowerShell script which performed ShellFolder.GetDetailsOf calls.
GetDetailsOf would consistently succeed, where ShellItem.Properties would throw an exception.
I would prefer ShellItemPropertyStore to safely retrieve properties, or at least provide a means of setting the GPS_BESTEFFORT flag without also setting ReadOnly to false.

Since you have this running, would you mind testing the following?
using var item = new ShellItem(path);
using var propertyDescriptions = item.GetPropertyDescriptionList();
propertyDescriptions.ReadOnly = false;
foreach (var description in ...

I'm assuming you mean:
        using var item = new ShellItem(path);
        using var propertyDescriptions = item.GetPropertyDescriptionList();
        item.Properties.ReadOnly = false;
        foreach (var description in ...

Since there's no ReadOnly property on PropertyDescriptionList*.
This throws:
System.Runtime.InteropServices.COMException : Access Denied. (0x80030005 (STG_E_ACCESSDENIED))
Stack Trace:
     at Vanara.PInvoke.Shell32.IShellItem2.GetPropertyStore(GETPROPERTYSTOREFLAGS flags, Guid& riid)
     at Vanara.Windows.Shell.ShellItemPropertyStore.GetIPropertyStore()
     at Vanara.Windows.Shell.ReadOnlyPropertyStore.Run[T](Func`2 action)
     at Vanara.Windows.Shell.ReadOnlyPropertyStore.get_Keys()
     at Vanara.Windows.Shell.ReadOnlyPropertyStore.ContainsKey(PROPERTYKEY key)

For that same file.
*(That's on me, really. Sorry for the slightly wonky example using keys from PropertyDescriptionList to access the ShellItemPropertyStore - I was working backwards from some other attempts at resolving the issue when I wrote that example.)
Some other things I've tried:

The property filter lists in PROPERTYKEY.System.PropList. None worked.
Putting a try-catch block around each Get to see if specific keys were triggering the issue (this is where the roundabout PropertyDescriptionList solution came from). But it seems to be all-or-nothing for this specific issue.

I made a change to ShellItemPropertyStore so it defaults to GPS_BESTEFFORT instead of GPS_DEFAULT and it now works with your first example w/o exceptions.

authors: dahall matthijsr

repo: dahall/Vanara


text:
Loading first page of a PDF file

Hi,
Thank you for this great tool !
I want to load only the first page of pdf files. I found that for a file named "myfile.pdf" it's possible to use filename='myfile.pdf[0]', but I don't know how to deal with binary blobs.
Best regards

Use the format= kwarg to trick the constructor.
with Image(blob=my_binary_blob, format="PDF[0]") as img:
    assert len(img) == 1
    # ... do work ...

Works like a charm. Thank you !

authors: emcconville yoch

repo: dahlia/wand


text:
Ignore specified characters when sorting

Is your feature request related to a problem? Please describe.
Hi, I found another case in my workspace that is a violation of what I wanted from #4.
import { ActivityGroup, ACTIVITY_CHART_TOTAL_DAYS, RootDashboardPageProvider } from "./";

It's supposed to look like this:
import { ACTIVITY_CHART_TOTAL_DAYS, ActivityGroup, RootDashboardPageProvider } from "./";

I'm guessing that it's the underscore that's causing the problem here because my sortRules is:
"sortRules": {
    "names": ["Aa"]
}

Describe the solution you'd like
It's probably worth it to allow the user to specify what characters, strings or regular expressions should be ignored when determining how to sort imports.
Describe alternatives you've considered
Are there any alternatives? If so, I'd like to know what they are.
Additional context

@JordanLongstaff thanks for your feedback!
Maybe you should set the rule as ["_", "Aa"].
I don't think we should ignore any chars because it causes more issues, e.g. what's the order of a_b and ab?

Well, your suggestion fixed my issue, so I think I can drop this.

Well, your suggestion fixed the issue, so I think I can drop this. Thanks!

authors: JordanLongstaff daidodo

repo: daidodo/tsimportsorter


text:
Fix bug in wrapping long queries

This addresses #208

Merged by hand as https://github.com/dalibo/pg_activity/commit/e44cab8ba14b3bb664ae1133f8c915e1027fcb01; many thanks for working on this!

authors: dlax plockaby

license: PostgreSQL


text:
Let's depend on rake 11

Let's update rake dependency to 11 version to prevent conflicts with other gems depending on latest rake.

Thank you for your support!

authors: damianFC vadimr

repo: damianFC/alexa-rubykit


text:
what file formats supported?

Hi
what file formats are supported?
Can the source image have multiple pixel art drawings or only 1 to extract?
I have attached an image (JPG) and when I run it, I get this error:

Traceback (most recent call last):
  File "F:\VISUAL STUDIO PROJECT\PIXEL ART\video\Pixel Art Extractor\pixel_art_extractor.py", line 420, in <module>
    main()
  File "F:\VISUAL STUDIO PROJECT\PIXEL ART\video\Pixel Art Extractor\pixel_art_extractor.py", line 39, in main
    pixel_image = crop_image(pixel_image)
  File "F:\VISUAL STUDIO PROJECT\PIXEL ART\video\Pixel Art Extractor\pixel_art_extractor.py", line 154, in crop_image
    pixel_image_crop[y_pos, x_pos] = image[y_pos +
IndexError: index 200 is out of bounds for axis 0 with size 200

@pixelart-girl the only image type that is currently supported is PNG.

@pixelart-girl

Can the source image have multiple pixel art drawings or only 1 to extract?
At the moment its only programmed to extract an icon away from its background. In the image you've given, I predict you may get some success, but it might make the top left cloud transparent, based on how I have programmed the background detections. I'd be interested to see what it does.

I could also probably add support for JPGs quite easily

FUCKYOU MOTHERFUCKER

SUCK MY MOTHERFUCKING CLIT

authors: dan-giddins pixelart-girl

repo: dan-giddins/pixel-art-extractor


text:
How to implement on web with React

Hi, this package looks awesome. I would love to implement something similar on a hover event on a React component for the web. Any tips on the translation? This is not super relevant to the project so feel free to close if you don't have an answer. Thanks!

Try using react-native-web. I've tested this on web and it works.

authors: gnestor tgoldenberg

repo: dancormier/react-native-swipeout


text:
V11 Update & Possible Themes Support

This is the obligatory new FoundryVTT Version dropped, please update issue.
The module seems to essentially still work, but the structure of the main page has changed a bit, so the css names do not match up anymore, should be a quick fix, most users can probably even implement themselves in the css file, but some default changes would be nice.
Finally, foundry now has themes for the setup. I havent verified if they interact with the module much yet, but they do change something on the login screen, so I imagine there is some crossover. No idea if themes will be editable or changeable with modules later on, but for now that doesnt seem to be the case. But maybe the css wizards of this module can still work with this a bit.

Hey, thanks for opening this issue. Yup it's absolutely on my radar to update the module for v11, and hopefully also directly integrate with the new themes support. I can't promise when yet, but should hopefully happen within the next few weeks and sooner rather than later, because as you said, it should be an easy adjustment!

While you're at it, it would be great if we can override the logo at the top of the login screen

As it turns out, Foundry currently doesn't have support for modules to include setup or login themes, and apparently also removed the ability for core translation modules to load CSS on the login page. So for now, the module is dead on v11, manual installation is the only way.
That being said, I have added a new CSS file to repository that includes an adjusted stylesheet to restore this project's functionality on v11. Note that since Foundry changed quite a lot of its default styling on the login page, the results look a little bit different than in previous versions, but I thought it would be counterintuitive to undo the (imo positive) changes that the VTT already includes in its core.
I'll leave this issue open for visibility and hope that eventually I will be able to wrap this CSS into a module again, but it looks like it won't be possible until at least v12.

does the login page theme need to be set to minimal while using the new CSS file? Does it matter which login page theme is selected?

Needs to be left at default, setting it to Minimal will break the logos.


text:
2.1.0版本lite分片任务执行时，任务重复执行

总共4个分片，但是每次0这个分片总是在4个分片执行完后，多了个线程把0这个分片又重新执行了一次 ，也就是每次一个轮训就要有一个分片被多执行一次，每次重复执行的那次的线程名称明显可以看出可其他的不太一致（当failover设置为true时存在此问题，failover为false是没有此问题）
下面是任务输出的信息：
[ob-myTestJob7-3] com.boot.job.MyJob    : ==========开始执行定时任务ShardingContext(jobName=myTestJob7, taskId=myTestJob7@-@0,1,2,3@-@READY@-@10.10.8.221@-@8eff493d-92e4-4415-a437-b4b38ceca74b, shardingTotalCount=4, jobParameter=ss, shardingItem=2, shardingParameter=C)
[ob-myTestJob7-2] com.boot.job.MyJob    : ========开始执行定时任务ShardingContext(jobName=myTestJob7, taskId=myTestJob7@-@0,1,2,3@-@READY@-@10.10.8.221@-@8eff493d-92e4-4415-a437-b4b38ceca74b, shardingTotalCount=4, jobParameter=ss, shardingItem=1, shardingParameter=B)
[ob-myTestJob7-4] com.boot.job.MyJob    : ========开始执行定时任务ShardingContext(jobName=myTestJob7, taskId=myTestJob7@-@0,1,2,3@-@READY@-@10.10.8.221@-@8eff493d-92e4-4415-a437-b4b38ceca74b, shardingTotalCount=4, jobParameter=ss, shardingItem=3, shardingParameter=D)
[ob-myTestJob7-1] com.boot.job.MyJob    : =========开始执行定时任务ShardingContext(jobName=myTestJob7, taskId=myTestJob7@-@0,1,2,3@-@READY@-@10.10.8.221@-@8eff493d-92e4-4415-a437-b4b38ceca74b, shardingTotalCount=4, jobParameter=ss, shardingItem=0, shardingParameter=A)
[stJob7_Worker-1] com.boot.job.MyJob    : =========开始执行定时任务ShardingContext(jobName=myTestJob7, taskId=myTestJob7@-@0@-@READY@-@10.10.8.221@-@8eff493d-92e4-4415-a437-b4b38ceca74b, shardingTotalCount=4, jobParameter=ss, shardingItem=0, shardingParameter=A)
[ob-myTestJob7-5] com.boot.job.MyJob    : ==========开始执行定时任务ShardingContext(jobName=myTestJob7, taskId=myTestJob7@-@0,1,2,3@-@READY@-@10.10.8.221@-@8eff493d-92e4-4415-a437-b4b38ceca74b, shardingTotalCount=4, jobParameter=ss, shardingItem=0, shardingParameter=A)
[ob-myTestJob7-7] com.boot.job.MyJob    : =========开始执行定时任务ShardingContext(jobName=myTestJob7, taskId=myTestJob7@-@0,1,2,3@-@READY@-@10.10.8.221@-@8eff493d-92e4-4415-a437-b4b38ceca74b, shardingTotalCount=4, jobParameter=ss, shardingItem=2, shardingParameter=C)
[ob-myTestJob7-6] com.boot.job.MyJob     : ==========开始执行定时任务ShardingContext(jobName=myTestJob7, taskId=myTestJob7@-@0,1,2,3@-@READY@-@10.10.8.221@-@8eff493d-92e4-4415-a437-b4b38ceca74b, shardingTotalCount=4, jobParameter=ss, shardingItem=1, shardingParameter=B)
[ob-myTestJob7-8] com.boot.job.MyJob    : ========开始执行定时任务ShardingContext(jobName=myTestJob7, taskId=myTestJob7@-@0,1,2,3@-@READY@-@10.10.8.221@-@8eff493d-92e4-4415-a437-b4b38ceca74b, shardingTotalCount=4, jobParameter=ss, shardingItem=3, shardingParameter=D)
[stJob7_Worker-1] com.boot.job.MyJob   : =========开始执行定时任务ShardingContext(jobName=myTestJob7, taskId=myTestJob7@-@0@-@READY@-@10.10.8.221@-@8eff493d-92e4-4415-a437-b4b38ceca74b, shardingTotalCount=4, jobParameter=ss, shardingItem=0, shardingParameter=A)

请确认一下是不是作业服务器时钟不一致导致的

时钟是一致的，刚才又让朋友试了下，也是同样的的问题，我是在springboot中使用的，而且把线程名称打印出来，明显感觉不太一样的

请提供任务执行代码，配置以及运行环境说明

光看描述感觉就像是正常的failover的功能，请确定一下分片0是否有执行失败的情况

用提供的例子执行也是这个问题， 就是用的
elastic-job-example-lite-springboot这个例子，只不过把SimpleJobConfig中的getLiteJobConfiguration方法中将failover设置为ｔｒｕｅ，然后去掉了和数据库的交互，直接让simplejob任务sleep(100),就出现了上述问题

好的，我已经重现，感谢发现问题

authors: pioneersli terrymanu

repo: dangdangdotcom/elastic-job


text:
Make it Clear That This Module is for AngularJS

... and not just Angular which stands for Angular 2+

Is this module for AngularJS and Angular, or just for AngularJs?

authors: netlander rangfu

repo: danialfarid/ng-file-upload


text:
Added touchend for touch devices instead of click, and fix FastClick issue on Chrome for ios

This removes the 300ms delay for mobile devices, and fixes an issue with FastClick for chrome on iOS. On Chrome for iOS, if FastClick is being used, the click event will not fire. I ran a build (noticed that other contributors were not) because I wasn't sure if this was done automatically.

You may want to rebase this

+1, @taylorcode can you rebase this?

Fixed in version 3.3.0 I had to do manual change since the files had changed quiet a bit since you submitted pull request.

authors: danialfarid prdolmos recurrence taylorcode


text:
🛑 Ramen Katsu is down

In c315aa3, Ramen Katsu (https://systemalpha.net/ramenkatsu) was down:

HTTP code: 504
Response time: 10292 ms

Resolved: Ramen Katsu is back up in 6b1ab1d after 12 minutes.

repo: danichrisd/up


text:
🛑 Ramen Katsu is down

In 92e4265, Ramen Katsu (https://systemalpha.net/ramenkatsu) was down:

HTTP code: 403
Response time: 914 ms

Resolved: Ramen Katsu is back up in bc55a80 after 11 minutes.


text:
Clicking the IPIMS home button when a user is not logged leads to an error

Cause: user variable is not loaded, which means link to user home is invalid.
recommended fix to to handle the case in the respective controller, by redirecting to login page

Fixed. this. not the best. but it works. Genstats branch. UserController


text:
Infinite FlowListView

Is there a way to create an infinite FlowListView?
How would I do that with ViewModel and XAML?

I got it:
https://github.com/daniel-luberda/DLToolkit.Forms.Controls/issues/53

#53


text:
Scaladoc lists

I'm using lists in Scaladoc:
      /** Documentation
        *
        *  - item 1
        *  - item 2
        */

Note the two spaces between * and - item 1, which are necessary to make it a list.  My problem is that scalariform reduces these two spaces to one, thus destroying the list structure.
Is there a way to deal with that?

No news on this?  It continues to mess up my code between sbt and IntelliJ IDEA.  Is there a way to turn off scalariform entirely for scaladoc comments?

It looks like its possible to modify the code to not strip out extra leading whitespace.
There's a few things that can be done:

Special case when the first character is the start of a scaladoc list to not strip leading whitespace
Add a new preference to allow no formatting of comments
Change the behavior in general to not strip out leading whitespace
Adding another preference to enable or disable trimming of whitespace in comments

The first option seems to be the "smartest", although there seem to be other reasons why someone might want to disable commenting on comments, so that might be useful to implement regardless. Not stripping out whitespace might be OK too, will need to think about this some more what the best solution is.

This issue was moved to scala-ide/scalariform#168

authors: charpov daniel-trinh sschaef

repo: daniel-trinh/scalariform


text:
引入报错 Component is not found in path "custom-wrapper"

引入报错 Component is not found in path "custom-wrapper"
@tarojs/taro: "3.5.0-beta.7"

经过测试是支持 "@tarojs/taro": "3.5.1" 的，建议升级正式版本尝试下

authors: daniel-zd tdida


text:
Locale support

Our project currently only supports one language, but upon integrating your pod, now it claims to support a myriad: Italian, Japanese, Korean, Portuguese, Spanish, and Traditional Chinese. I'm glad it has this capability, but I think you would agree that your pod shouldn't dictate what languages our app supports. :)
The solution appears to be thus, from a similar example with a Git project Appirater:

Afaik, this is only because Appirater adds all those localization bundles in the root of your app’s bundle. It should not do that. It should have a namespaced resource bundle that contains them and adjust the code accordingly.

As it is now, you can’t even have your own localizations without merging them with those of Appirater, which is bad.

https://github.com/CocoaPods/CocoaPods/issues/1301#issuecomment-22926515
Any help with this would be greatly appreciated!

It added support to all these languages? I can help with the Portuguese. @aaronhedquist

authors: Viniciuscarvalho aaronhedquist

repo: danielebogo/DBPrivacyHelper


text:
[BUG] In Cyrillic version CS GO, I have question marks in skinchanger

E.g.

You have to adjust Unicode ranges for GUI fonts to cover Cyrillic characters.

fixed, thx

Input doesn't work anyway at least for me

repo: danielkrupinski/Osiris