Webpack CSS build issue on Windows

Hi Team
I am having trouble taking the build of the whole project. As per instruction, Only JDK 8 needs to be installed. I did and run the build. I am getting an error. Can you share me version details of all dependency like node js, grade, java version or etc.?
Stacktrace:
C:\Users\nihal\Projects\sagan-master>gradlew :sagan-site:bootRun

Task :sagan-client:npm_install
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\watchpack-chokidar2\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

audited 919 packages in 17.95s
39 packages are looking for funding
run npm fund for details
found 1 low severity vulnerability
run npm audit fix to fix them, or npm audit for details

Task :sagan-client:npm_run_build

sagan@ build C:\Users\nihal\Projects\sagan-master\sagan-client
webpack

Hash: a68c0c20c60443109963
Version: webpack 4.43.0
Time: 26184ms
Built at: 2020-05-25 11:23:37 p.m.
21 assets
Entrypoint main = css/main.css js/main.js
Entrypoint guide = css/guide.css js/guide.js
Entrypoint project = css/project.css js/project.js
Entrypoint team = css/team.css js/team.js
Entrypoint profile = css/profile.css js/profile.js
Entrypoint blog = css/blog.css js/blog.js
Entrypoint admin = css/admin.css js/admin.js
Entrypoint theme = js/theme.js
Entrypoint run_prettify = js/run_prettify.js
[16] ./src/app/main.js 10 KiB {3} [built]
[19] ./src/css/main.css 1.61 KiB {3} [built] [failed] [1 error]
[20] ./src/css/dark.scss 39 bytes {3} [built]
[21] ./src/app/guide.js 1.14 KiB {2} [built]
[34] ./src/css/guide.css 39 bytes {2} [built]
[35] ./src/app/project.js 1.75 KiB {5} [built]
[36] ./src/css/project.css 39 bytes {5} [built]
[37] ./src/app/team.js 3.96 KiB {7} [built]
[38] ./src/css/team.css 39 bytes {7} [built]
[39] ./src/app/profile.js 3.66 KiB {4} [built]
[40] ./src/css/profile.css 39 bytes {4} [built]
[41] ./src/app/blog.js 24 bytes {1} [built]
[43] ./src/app/admin.js 880 bytes {0} [built]
[49] ./src/app/theme.js 296 bytes {8} [built]
[50] ./src/app/run_prettify.js 18 KiB {6} [built]
+ 46 hidden modules
WARNING in configuration
The 'mode' option has not been set, webpack will fallback to 'production' for this value. Set 'mode' option to 'development' or 'production' to enable defaults for each environment.
You can also set it to 'none' to disable any default behavior. Learn more: https://webpack.js.org/configuration/mode/
ERROR in ./src/css/main.css
Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
ModuleParseError: Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
at handleParseError (C:\Users\nihal\Projects\sagan-master\sagan-client\node_modules\webpack\lib\NormalModule.js:469:19)
at C:\Users\nihal\Projects\sagan-master\sagan-client\node_modules\webpack\lib\NormalModule.js:503:5
at C:\Users\nihal\Projects\sagan-master\sagan-client\node_modules\webpack\lib\NormalModule.js:358:12
at C:\Users\nihal\Projects\sagan-master\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:373:3
at iterateNormalLoaders (C:\Users\nihal\Projects\sagan-master\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:214:10)
at Array. (C:\Users\nihal\Projects\sagan-master\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:205:4)
at Storage.finished (C:\Users\nihal\Projects\sagan-master\sagan-client\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:55:16)
at C:\Users\nihal\Projects\sagan-master\sagan-client\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:91:9
at C:\Users\nihal\Projects\sagan-master\sagan-client\node_modules\graceful-fs\graceful-fs.js:123:16
at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
@ ./src/app/main.js 7:0-24
ERROR in<EMAIL_ADDRESS>Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
ModuleParseError: Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
at handleParseError (C:\Users\nihal\Projects\sagan-master\sagan-client\node_modules\webpack\lib\NormalModule.js:469:19)
at C:\Users\nihal\Projects\sagan-master\sagan-client\node_modules\webpack\lib\NormalModule.js:503:5
at C:\Users\nihal\Projects\sagan-master\sagan-client\node_modules\webpack\lib\NormalModule.js:358:12
at C:\Users\nihal\Projects\sagan-master\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:373:3
at iterateNormalLoaders (C:\Users\nihal\Projects\sagan-master\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:214:10)
at Array. (C:\Users\nihal\Projects\sagan-master\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:205:4)
at Storage.finished (C:\Users\nihal\Projects\sagan-master\sagan-client\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:55:16)
at C:\Users\nihal\Projects\sagan-master\sagan-client\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:91:9
at C:\Users\nihal\Projects\sagan-master\sagan-client\node_modules\graceful-fs\graceful-fs.js:123:16
at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
@ ./src/app/main.js 4:0-50
Child mini-css-extract-plugin<EMAIL_ADDRESS>1 asset
Entrypoint mini-css-extract-plugin = *
2 modules
Child mini-css-extract-plugin<EMAIL_ADDRESS>1 asset
Entrypoint mini-css-extract-plugin = *
18 modules
ERROR in<EMAIL_ADDRESS>1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
<EMAIL_ADDRESS><EMAIL_ADDRESS>7:36-76

ERROR in<EMAIL_ADDRESS>1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
<EMAIL_ADDRESS><EMAIL_ADDRESS>12:36-77

ERROR in<EMAIL_ADDRESS>1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
<EMAIL_ADDRESS><EMAIL_ADDRESS>17:37-76

ERROR in<EMAIL_ADDRESS>1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
<EMAIL_ADDRESS><EMAIL_ADDRESS>6:36-77

ERROR in<EMAIL_ADDRESS>1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
<EMAIL_ADDRESS><EMAIL_ADDRESS>5:36-78

ERROR in<EMAIL_ADDRESS>1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
<EMAIL_ADDRESS><EMAIL_ADDRESS>11:36-78

ERROR in<EMAIL_ADDRESS>1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
<EMAIL_ADDRESS><EMAIL_ADDRESS>10:36-79

ERROR in<EMAIL_ADDRESS>1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
<EMAIL_ADDRESS><EMAIL_ADDRESS>16:37-77

ERROR in<EMAIL_ADDRESS>1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
<EMAIL_ADDRESS><EMAIL_ADDRESS>15:37-78

ERROR in<EMAIL_ADDRESS>1:0
Module parse failed: Unexpected character '∩┐╜' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
<EMAIL_ADDRESS><EMAIL_ADDRESS>4:36-76

ERROR in<EMAIL_ADDRESS>1:0
Module parse failed: Unexpected character '∩┐╜' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
<EMAIL_ADDRESS><EMAIL_ADDRESS>14:37-76

ERROR in<EMAIL_ADDRESS>1:1
Module parse failed: Unexpected character '∩┐╜' (1:1)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
<EMAIL_ADDRESS><EMAIL_ADDRESS>9:36-77

ERROR in<EMAIL_ADDRESS>1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!--
| Font Awesome Free 5.13.0 by @fontawesome - https://fontawesome.com
<EMAIL_ADDRESS><EMAIL_ADDRESS>13:36-77

ERROR in<EMAIL_ADDRESS>1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!--
| Font Awesome Free 5.13.0 by @fontawesome - https://fontawesome.com
<EMAIL_ADDRESS><EMAIL_ADDRESS>8:36-76

ERROR in<EMAIL_ADDRESS>1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!--
| Font Awesome Free 5.13.0 by @fontawesome - https://fontawesome.com
<EMAIL_ADDRESS><EMAIL_ADDRESS>18:37-76

Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!node_modules/bulma/css/bulma.css:
1 asset
Entrypoint mini-css-extract-plugin = *
2 modules
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!node_modules/jquery-datetimepicker/jquery.datetimepicker.css:
1 asset
Entrypoint mini-css-extract-plugin = *
2 modules
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!node_modules/sass-loader/dist/cjs.js!src/css/dark.scss:
1 asset
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js!./node_modules/sass-loader/dist/cjs.js!./src/css/dark.scss 9.77 KiB {0} [built]
+ 1 hidden module
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!src/css/admin.css:
1 asset
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js!./src/css/admin.css 2.61 KiB {0} [built]
+ 1 hidden module
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!src/css/blog.css:
1 asset
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js!./src/css/blog.css 4.62 KiB {0} [built]
+ 1 hidden module
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!src/css/guide.css:
1 asset
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js!./src/css/guide.css 3.69 KiB {0} [built]
+ 1 hidden module
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!src/css/main.css:
1 asset
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js!./src/css/main.css 98.6 KiB {0} [built]
[3] ./src/fonts/metropolis-regular-webfont.woff2 284 bytes {0} [built] [failed] [1 error]
[4] ./src/fonts/metropolis-regular-webfont.woff 284 bytes {0} [built] [failed] [1 error]
[5] ./src/fonts/metropolis-bold-webfont.woff2 284 bytes {0} [built] [failed] [1 error]
[6] ./src/fonts/metropolis-bold-webfont.woff 284 bytes {0} [built] [failed] [1 error]
[7] ./src/fonts/metropolis-extrabold-webfont.woff2 284 bytes {0} [built] [failed] [1 error]
[8] ./src/fonts/metropolis-extrabold-webfont.woff 284 bytes {0} [built] [failed] [1 error]
[9] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.eot 271 bytes {0} [built] [failed] [1 error]
[10] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.woff2 284 bytes {0} [built] [failed] [1 error]
[11] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.woff 284 bytes {0} [built] [failed] [1 error]
[12] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.ttf 284 bytes {0} [built] [failed] [1 error]
[13] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.svg 424 bytes {0} [built] [failed] [1 error]
[14] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.eot 281 bytes {0} [built] [failed] [1 error]
[15] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.woff2 284 bytes {0} [built] [failed] [1 error]
[16] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.woff 284 bytes {0} [built] [failed] [1 error]
+ 24 hidden modules
ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 13:36-107

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-600.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 23:37-104

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 18:37-107

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-700.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 28:37-104

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-regular.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 33:37-106

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-700.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 38:37-102

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-600.eot 1:2
Module parse failed: Unexpected character ' ' (1:2)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 20:37-104

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-regular.eot 1:2
Module parse failed: Unexpected character ' ' (1:2)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 30:37-106

ERROR in ./src/fonts/metropolis-regular-webfont.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 5:36-87

ERROR in ./src/fonts/metropolis-regular-webfont.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 4:36-88

ERROR in ./src/fonts/metropolis-bold-webfont.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 7:36-84

ERROR in ./src/fonts/metropolis-bold-webfont.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 6:36-85

ERROR in ./src/fonts/metropolis-extrabold-webfont.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 8:36-90

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 11:36-109

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 12:36-108

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 16:37-109

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 17:37-108

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-600.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 22:37-105

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-600.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 21:37-106

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-700.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 26:37-106

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-700.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 27:37-105

ERROR in ./src/fonts/metropolis-extrabold-webfont.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 9:36-89

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-regular.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 31:37-108

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-regular.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 32:37-107

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-700.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 37:37-103

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-700.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 36:37-104

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-700.eot 1:0
Module parse failed: Unexpected character '' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 35:37-102

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.eot 1:0
Module parse failed: Unexpected character '∩┐╜' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 15:37-107

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-700.eot 1:0
Module parse failed: Unexpected character '∩┐╜' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 25:37-104

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.eot 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 10:36-107

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 14:37-108

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 19:37-107

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-600.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 24:37-104

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-regular.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 34:37-106

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-700.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 29:37-104

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-700.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 39:37-102

Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!src/css/profile.css:
1 asset
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js!./src/css/profile.css 3.83 KiB {0} [built]
+ 1 hidden module
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!src/css/project.css:
1 asset
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js!./src/css/project.css 10.8 KiB {0} [built]
+ 1 hidden module
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!src/css/team.css:
1 asset
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js!./src/css/team.css 1.9 KiB {0} [built]
+ 1 hidden module
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! sagan@ build: webpack
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the sagan@ build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      C:\Users\nihal\AppData\Roaming\npm-cache_logs\2020-05-26T03_23_37_727Z-debug.log

Task :sagan-client:npm_run_build FAILED

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':sagan-client:npm_run_build'.

Process 'command 'C:\Users\nihal\Projects\sagan-master\sagan-client.gradle\npm\npm-v6.14.4\npm.cmd'' finished with non-zero exit value 2

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.3/userguide/command_line_interface.html#sec:command_line_warnings
BUILD FAILED in 1m 28s
5 actionable tasks: 2 executed, 3 up-to-date
My System Configuration:
C:\Users\nihal\Projects\sagan-master>java -version
java version "1.8.0_251"
Java(TM) SE Runtime Environment (build 1.8.0_251-b08)
Java HotSpot(TM) 64-Bit Server VM (build 25.251-b08, mixed mode)
C:\Users\nihal\Projects\sagan-master>npm -v
6.13.4
C:\Users\nihal\Projects\sagan-master>node -ver
node: bad option: -ver
C:\Users\nihal\Projects\sagan-master>node -v
v8.17.0
C:\Users\nihal\Projects\sagan-master>gradle -version

Gradle 6.4.1
Build time:   2020-05-15 19:43:40 UTC
Revision:     1a04183c502614b5c80e33d603074e0b4a2777c5
Kotlin:       1.3.71
Groovy:       2.5.10
Ant:          Apache Ant(TM) version 1.10.7 compiled on September 1 2019
JVM:          1.8.0_251 (Oracle Corporation 25.251-b08)
OS:           Windows 10 10.0 amd64

Met the same problem, after google search, someone mentioned it was related to font loading.
Tried add the following, and it can pass build, but not sure if this is the right way.
sagan\sagan-client\webpack.config.js
        {
            test: /\.(woff2|woff|eot|ttf|svg)$/,
            loader: 'file-loader',
            options: {
                name: 'fonts/[name].[ext]',
            },
        },

Thanks @colinzuo. Your suggestion got me past the error. I will watch this error for official word.

I'm not sure this is the right way to address this issue.
Our current CI is working properly and the build is also working properly on several machines. The snippet suggested by @colinzuo is quite similar to what we've got already, only the pattern changes and includes all svg files, which can also be images and this not located under fonts. This might cause problems when loading images in production.
We've had similar problems when trying to fix that in #973 and #963

i have same problem and i was not able to find any solution on web. anything i tried was not working.
i tried also with node version 12.19.0 and also some older one around version 10 i think.
i tried this week it on 3 different PCs. same problem every time.
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! sagan@ build: `webpack`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the sagan@ build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      C:\Users\stse\AppData\Roaming\npm-cache\_logs\2020-10-16T09_55_12_656Z-debug.log

> Task :sagan-client:npm_run_build FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':sagan-client:npm_run_build'.
> Process 'command 'C:\Dev\Kody\sagan\sagan-client\.gradle\npm\npm-v6.14.4\npm.cmd'' finished with non-zero exit value 2

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.3/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 2m 30s
5 actionable tasks: 5 executed

C:\Dev\Kody\sagan>java -version
java version "1.8.0_261"
Java(TM) SE Runtime Environment (build 1.8.0_261-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.261-b12, mixed mode)

C:\Dev\Kody\sagan>node -v
v14.14.0

C:\Dev\Kody\sagan>gradle -version

------------------------------------------------------------
Gradle 6.6.1
------------------------------------------------------------

Build time:   2020-08-25 16:29:12 UTC
Revision:     f2d1fb54a951d8b11d25748e4711bec8d128d7e3

Kotlin:       1.3.72
Groovy:       2.5.12
Ant:          Apache Ant(TM) version 1.10.8 compiled on May 10 2020
JVM:          1.8.0_261 (Oracle Corporation 25.261-b12)
OS:           Windows 10 10.0 amd64

Hi @bclozel/@colinzuo  ,
May i know how to run the project in Windows. I am Sorry I am not clear with the explanation given in project Wiki.
Since ./gradlew build is throwing error how do i proceed.
https://github.com/spring-io/sagan/wiki/Run-the-site-locally
Steps
Run the site locally from your IDE
Create a new run configuration with the class sagan.SiteApplication. It might help to run ./gradlew build from the top level directory first, in case your IDE doesn't know how to build all the dependencies. In IntelliJ you also might need to configure the launcher to run within the module working directory (i.e. from sagan-site).
Then use this run configuration to start the site!
Note: Sagan is using Spring Boot's developer tools features, such as LiveReload.

HI @simrin051
As replied when you reached out directly to by email, this is the very problem that we're trying to address here: we haven't found a way so far to fix this problem for contributors using Windows without breaking the production service.
There has been proposals here to fix the issue on Windows but unfortunately they're breaking the build on Linux and MacOS.

@bclozel
If i am not wrong it is like i cannot contribute to this project correct?

This comment shows how to make the build pass on windows.

@bclozel
Thanks build was successful.
I get the below error when i ran   ./gradlew :sagan-site:bootRun
Caused by: org.h2.jdbc.JdbcSQLSyntaxErrorException: Syntax error in SQL statement "ALTER TABLE PROJECT_SAMPLE MODIFY[*] TITLE VARCHAR(255) NOT NULL"; expected ".,
ADD, SET, RENAME, DROP, ALTER"; SQL statement:
ALTER TABLE project_sample MODIFY title VARCHAR(255) NOT NULL [42001-200]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:453) ~[h2-1.4.200.jar:1.4.200]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:429) ~[h2-1.4.200.jar:1.4.200]
at org.h2.message.DbException.getSyntaxError(DbException.java:243) ~[h2-1.4.200.jar:1.4.200]
at org.h2.command.Parser.getSyntaxError(Parser.java:1053) ~[h2-1.4.200.jar:1.4.200]
at org.h2.command.Parser.parseAlterTable(Parser.java:7705) ~[h2-1.4.200.jar:1.4.200]
at org.h2.command.Parser.parseAlter(Parser.java:6983) ~[h2-1.4.200.jar:1.4.200]
at org.h2.command.Parser.parsePrepared(Parser.java:887) ~[h2-1.4.200.jar:1.4.200]
at org.h2.command.Parser.parse(Parser.java:843) ~[h2-1.4.200.jar:1.4.200]
at org.h2.command.Parser.parse(Parser.java:819) ~[h2-1.4.200.jar:1.4.200]
at org.h2.command.Parser.prepareCommand(Parser.java:738) ~[h2-1.4.200.jar:1.4.200]
at org.h2.engine.Session.prepareLocal(Session.java:657) ~[h2-1.4.200.jar:1.4.200]
at org.h2.engine.Session.prepareCommand(Session.java:595) ~[h2-1.4.200.jar:1.4.200]
at org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1235) ~[h2-1.4.200.jar:1.4.200]
at org.h2.jdbc.JdbcStatement.executeInternal(JdbcStatement.java:212) ~[h2-1.4.200.jar:1.4.200]
at org.h2.jdbc.JdbcStatement.execute(JdbcStatement.java:201) ~[h2-1.4.200.jar:1.4.200]
at com.zaxxer.hikari.pool.ProxyStatement.execute(ProxyStatement.java:94) ~[HikariCP-4.0.3.jar:na]
at com.zaxxer.hikari.pool.HikariProxyStatement.execute(HikariProxyStatement.java) ~[HikariCP-4.0.3.jar:na]
at org.flywaydb.core.internal.jdbc.JdbcTemplate.executeStatement(JdbcTemplate.java:241) ~[flyway-core-7.7.3.jar:na]
at org.flywaydb.core.internal.sqlscript.ParsedSqlStatement.execute(ParsedSqlStatement.java:111) ~[flyway-core-7.7.3.jar:na]
at org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor.executeStatement(DefaultSqlScriptExecutor.java:206) ~[flyway-core-7.7.3.jar:na]
... 51 common frames omitted

Task :sagan-site:bootRun FAILED

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':sagan-site:bootRun'.

Process 'command 'C:\Program Files\Java\jdk-11.0.12\bin\java.exe'' finished with non-zero exit value 1

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 2m 54s
11 actionable tasks: 4 executed, 7 up-to-date
PS C:\Users\user\Spring_Workspace\sagan>

@simrin051 you need to run siteApplication with spring profile = standalone either through command line or through IDE.
In IntelliJ:

Or If you run through CMD:
SPRING_PROFILES_ACTIVE=standalone ./gradlew :sagan-site:bootRun

ok Thanks


Plugin handling

Maybe my plugin understanding is not perfect.
But i guess
SimpleWebServer.java@325
should check plugin.canServeUri, otherwise it will call plugin based on mimeType which is not exactly what i would expect...

https://github.com/NanoHttpd/nanohttpd/blob/master/webserver/src/main/java/fi/iki/elonen/SimpleWebServer.java#L414 seems to be correct now. Should this be closed?

not completely there was a second check nessesary


Rename impl/sql -> impl/mysql

More accurate package path.
The implementation is mysql specific, not generic sql.

KT is very explicitly v0.2-alpha
On Fri, Mar 27, 2020 at 10:30 AM Martin Hutchinson<EMAIL_ADDRESS>wrote:

@mhutchinson approved this pull request.
If you're not worried about impact on clients (semver deja vu) then LGTM
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/google/keytransparency/pull/1508#pullrequestreview-382739585,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABQOTXC6TOA7DXCQS2OPBDRJR54BANCNFSM4LU4SARQ
.


bug: apply fail to apply to correct files - create a new file instaed

IDE Information
PyCharm 2024.2.4 (Professional Edition)
Build #PY-242.23726.102, built on October 22, 2024
Licensed to **** / ****
You have a perpetual fallback license for this version.
Subscription is active until October 17, 2025.
Runtime version: 21.0.4+13-b509.26 amd64 (JCEF 122.1.9)
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Toolkit: sun.awt.X11.XToolkit
Linux 6.8.0-40-generic
GC: G1 Young Generation, G1 Concurrent GC, G1 Old Generation
Memory: 2560M
Cores: 4
Registry:
vcs.log.index.enable=true
ide.experimental.ui=true
i18n.locale=
python.debug.low.impact.monitoring.api=False
Non-Bundled Plugins:
com.berzanmikaili.intellij.monokai_pro (2.0.2c)
MultiHighlight (3.2.0)
org.intellij.plugins.hcl (242.23339.11)
com.ultrahob.zerolength.plugin (0.95)
org.jetbrains.action-tracker (0.3.3)
com.intellij.ideolog (242.23726.110)
com.tylerthrailkill.intellij.solarized (3.0.0)
org.jeto.taskfocus (1.2)
com.arcticicestudio.nord.jetbrains (0.13.0)
GrepConsole (13.1.0-IJ2023.3)
com.insyncwithfoo.pyrightls (1.1.0)
uk.co.ben-gibson.remote.repository.mapper (4.5.2)
com.sourcegraph.jetbrains (7.3.2)
Activity Tracker (0.1.13 beta)
Current Desktop: ubuntu:GNOME
Bug Description
My project have this structure:
scripts/
src/
src/scripts/

When I work with files inside src/scripts/ apply create a new file in scripts/ instead of modifying the file inside `src/scripts/. This happens even when I only include the single file as context.
Additional context
No response

Probably same as https://community.sourcegraph.com/t/cody-generates-new-files-when-i-click-apply-instead-of-applying-the-changes-to-the-correct-file/1125


Support recreating unmergeable PRs in GitLab

GitLab doesn't support low-level git API like GitHub, so currently we mark every PR as canRebase=false. But it would perhaps be desirable to close existing PR and create a replacement, instead of leaving the existing one as conflicted.
Cc @guumaster

Depends on your GitLab version, ut turns out that Gitlab EE has the feature, but its not exposed through the API.

In that case I guess we can't use it though? BTW I have been testing against the public gitlab.com myself

The public GitLab.com site is their Enterprise Edition.
For what it's worth, I would lean on the side of not using any specific EE features as there are a lot of non-profits out there using GitLab Community Edition, and they too may benefit from renovate.

With npm5 out and package-locks being a default feature this issue has become a whole lot more relevant.
So far my workflow to handle this manually has been to nuke the conflicting branch and re-run renovate to generate a new branch and continue using the same PR. This is not perfect however as we lose an updated description and title in the case of newer versions of deps being added during this process. If we can overcome that drawback the branch nuking may be a viable solution though.
What do you guys think?

we lose an updated description and title in the case of newer versions of deps being added during this process.

Could you give an example of this so I understand?

It would be a bit challenging to stage the scenario myself. But the steps to reproduce this naturally would be:

Having a fairly stale PR waiting in the queue that has a merge conflict (Usually due to package-lock now)
Deleting the source branch (Without deleting the PR)
Running renovate, which will detect the out-of-date dep and go ahead and make the branch again.
The PR is now live again, and if there just so happened to be a newer version of the dep than the PR reflected renovate would have committed to that version, but the title and description of the PR will not reflect this, only the latest commit message will.

@Autre31415 Are you saying that in GitLab you can delete a branch and it does not automatically delete/close the MR?
If so then this behaviour differs from GitHub but that would be a good thing and help me solve the problem.

That is correct, and that has been my manual solution to dealing with this problem, with the only drawback being that the title and description will not update if the dependency has a newer version when the branch is remade.

That's quite possibly the trick we need then.
So:

We have a conflicting branch/MR
We delete the branch. "Zombie" MR stays open!?
We recreate the branch, based off of master - no conflicts
GitLab "reconnects" the zombie MR with its recreated branch?
Renovate needs to detect the MR and update its title/description

The strange thing is that (5) is meant to be the way things work already. If you're sure it's not - or was it just theoretical - then hopefully it can be fixed. FYI: renovate will check the MR title and description on every iteration and update it if the old one is outdated.

I can confirm through my own use of renovate that 2 and 4 are the case, with 5 being the only problem. I've been dealing with this problem since npm5 dropped and package-lock created merge conflicts galore.

Thanks for the info. I think it can be fixed and the end result will hopefully be as elegant as the existing GitHub rebasing.

I'm looking into this now. I think an easy way to reproduce such a challenge in an empty repo is:

Install a version of dependency 2 versions old (e.g<EMAIL_ADDRESS>Run renovate (will create 2 MRs, one for each major version)
Merge the 3.x branch
The 4.x will now be in conflict

Confirming how it looks to me when I delete the branch:

Nearly done. You get a bit of "noise" in the "Discussion" area but otherwise it's quite elegant:

@Autre31415 please try renovate version 8.38.0 and let me know how it goes. It should automatically delete and recreate any branches that have got into unmergeable state (e.g. due to package-lock.json.
BTW in case you have "related" packages causing this problem (e.g. eslint and friends), consider having a package "group" to put them all into the same branch and avoid the merge/rebase/merge/rebase cycle when multiple are released at similar times.

🎉 🎉 🎉 🎉 🎉 🎉
I just tried it out and am happy to report that our merge conflicts are being handled properly now, and with updated descriptions. Awesome work!

Great news! Thanks for tip re: how GitLab let's you delete branches without automatically closing the MR - that was the whole reason why I couldn't do the same thing on GitHub and assumed the same for GitLab.

Also wanted to chime in and say what an awesome enhancement!
The extra discussion updates are a minor matter given the enormous benefit.


Yaml file needs ports declaration

It would be kind to explain more in your issue, but no, the docker-compose.browsersync.yaml does not need or want a ports stanza. If it had one, you could only run one project on a system. Instead, it has an expose (which exposes inside docker's world) and HTTP_EXPOSE/HTTPS_EXPOSE, which expose it via ddev-router (which handles it per-hostname)
https://github.com/drud/ddev-browsersync/blob/1743545298d5c48397eb9d88e801e053f2df7a24/docker-compose.browsersync.yaml#L6-L10

How could I set a different port? (instead of 3000)

Currently this is not fully changeable: https://github.com/drud/ddev-browsersync/blob/main/commands/web/browsersync#L9

The follow steps show how to replace the port from 3000 to 8080
In .ddev/browser-sync.js:

Remove // #ddev-generated
Set the port number.

module.exports = {
    port: 8080,

In .ddev/docker-compose.browsersync.yaml

Remove // #ddev-generated
replace 4 instances of the port

```yml
expose:
  - '8080'
environment:
  - HTTP_EXPOSE=${DDEV_ROUTER_HTTP_PORT}:80,${DDEV_MAILHOG_PORT}:8025,3001:8080
  - HTTPS_EXPOSE=${DDEV_ROUTER_HTTPS_PORT}:80,${DDEV_MAILHOG_HTTPS_PORT}:8025,8080:8080
```

In ~/.ddev/commands/web/browsersync:

Remove // #ddev-generated
replace 1 instances of the port

echo "Proxying browsersync on ${DDEV_PRIMARY_URL}:8080"

Your welcome to submit a PR if you want to extract it into a variable. 😄

Closing as "answered"


Telescope Window name

Hi there,
Would you consider renaming the default Telescope window name to 'Bookmarks'' or similar, from 'Select from List: Default'?

This will help with :

Being able to tell this plugin apart when lots of telescope plugins are mapped to different key combinations.
Consistency with other plugins that read for e.g., File Browser, Live Grep, etc in that field that state their purpose, as there is nothing indicating that it refers to the Bookmarks.

Thanks heaps for considering this, it would be a massive help!

Yeah, of course we can do it.
But I still want the hint about which list I'm choosing from, which format should be better?
Bookmarks: [Default]

The impl has been pushed, sorry for the late~


Outdated script

The script for converting users from per-user to Conditional Access based MFA is written using the MSOnline module which I can't seem to install any longer as it is being deprecated. It would be great to have this script updated to use the new Azure AD v2 module.

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

ID: f132318f-8670-fd0d-2524-01305ccff2a1
Version Independent ID: 0849b4a9-ff14-1d61-47f2-a2daecf3cde9
Content: Deployment considerations for Azure Multi-Factor Authentication
Content Source: articles/active-directory/authentication/howto-mfa-getstarted.md
Service: active-directory
Sub-service: authentication
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

@dtblodgett
Thanks for your feedback! I have assigned this issue to the author who will investigate and update as appropriate.

Thanks for the feedback, @dtblodgett
I believe @BarbaraSelden was looking to work on some updates to this deployment guide, so it may be able to roll in to that. Our specific per-user doc is also using the MSOnline module, unfortunately - https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-mfa-userstates#convert-users-from-per-user-mfa-to-conditional-access-based-mfa
#assign:BarbaraSelden

Thank you. I have reached out to get help in updating this script
Thank you!
-bmws
Barbara Winter Selden
Identity Knowledge Mangement
206-601-4223
From: Iain Foulds<EMAIL_ADDRESS>Sent: Tuesday, July 7, 2020 11:13 AM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Barbara Winter Selden<EMAIL_ADDRESS>Assign<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Outdated script (#58576)
Thanks for the feedback, @dtblodgetthttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdtblodgett&data=02|01|Barbara.Selden%40microsoft.com|54d83cdfb6d74765126708d822a16450|72f988bf86f141af91ab2d7cd011db47|1|0|637297423851004124&sdata=ASVI40OSjgioVPf%2BzyN%2FHJ5vUgXCU5gQNudZVzOZQ9U%3D&reserved=0
I believe @BarbaraSeldenhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FBarbaraSelden&data=02|01|Barbara.Selden%40microsoft.com|54d83cdfb6d74765126708d822a16450|72f988bf86f141af91ab2d7cd011db47|1|0|637297423851014112&sdata=2FekRNkqPlG%2ByqdxA6X144VGUnhIszhtYbHxW2MSO9E%3D&reserved=0 was looking to work on some updates to this deployment guide, so it may be able to roll in to that. Our specific per-user doc is also using the MSOnline module, unfortunately - https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-mfa-userstates#convert-users-from-per-user-mfa-to-conditional-access-based-mfahttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fauthentication%2Fhowto-mfa-userstates%23convert-users-from-per-user-mfa-to-conditional-access-based-mfa&data=02|01|Barbara.Selden%40microsoft.com|54d83cdfb6d74765126708d822a16450|72f988bf86f141af91ab2d7cd011db47|1|0|637297423851014112&sdata=YWxnG0fDgqcHAvKg5xxKqHxBTCKxGGTYPt2d5P6Mfks%3D&reserved=0
#assign:BarbaraSelden
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F58576%23issuecomment-655035635&data=02|01|Barbara.Selden%40microsoft.com|54d83cdfb6d74765126708d822a16450|72f988bf86f141af91ab2d7cd011db47|1|0|637297423851024105&sdata=pMvx%2FDwOhtBwGmAJtF68%2BV7ZJrGQAUaTuc0rliSCRu8%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAG4WUUSTNEGRY26LTNXI7RLR2NQS7ANCNFSM4OS64AIA&data=02|01|Barbara.Selden%40microsoft.com|54d83cdfb6d74765126708d822a16450|72f988bf86f141af91ab2d7cd011db47|1|0|637297423851024105&sdata=wJ8hBy5PjBrLlx8dLWKsJs4KfeYf6ufu5TYTM3A9OV0%3D&reserved=0.

BarbaraSelden is already assigned.

#assign @mmcla

#assign:@Justinha


Transition in FAQ page and responsive

Related Issue
Fixes:  #2424
Description
Added animation and transition effect on FAQ page and improved UI.
Made the section responsive for all screen also
Type of PR

[ ] Bug fix
[X] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
https://github.com/anuragverma108/SwapReads/assets/168854094/39d716cf-a5ae-49c6-8e5f-b40fbcccf043
https://github.com/anuragverma108/SwapReads/assets/168854094/04b31d65-9a41-499c-a0e4-9622570773ee
Checklist:

[X]  I have made this change from my own.
[X]  My code follows the style guidelines of this project.
[X]  I have performed a self-review of my own code.
[X]  I have commented my code, particularly in hard-to-understand areas.
[X] My changes generate no new warnings.
[X]  I have tested the changes thoroughly before submitting this pull request.
[X] I have provided relevant issue numbers and screenshots after making the changes.

This branch has conflicts that must be resolved


Search Highlighting

The search highlighting is not working since one of the last commits.
On the search results page, search terms should highlight in yellow after a search. This in configured via inline JS.

Accordion title was changed from  to .
JS file changed accordingly by JS


Update settings.tsx

Added lemmy.wtf

Hi @LizardWizardGB and thanks for the PR!
I am trying to keep the list of instances short for now, so I am listing only the most popular ones. I'm determining "popularity" by the number of links we have in our database.
If you want to configure a Home Instance that's not in the list, you can use the "custom" option at the bottom of the instances dropdown and enter your URL - in your case that would be lemmy.wtf/c/.


Enabling the time portion of the datetime string to be on the left hand side

Enabling the time portion of the datetime string to be on the left hand side as per issue #777

Thank you for this contribution.  Would you be able to issue this pull request to the dev branch?

Hi Trent - have done so - one other thing the changes I have made don't affect in any way the alt fields at this stage because my project didn't need that functionality but it shouldn't be hard


VS Code window is not maximized when restored from minimized

Does this issue occur when all extensions are disabled?: Yes

VS Code Version:
Version: 1.58.2
Commit: c3f126316369cd610563c75b1b1725e0679adfb3
Date: 2021-07-14T22:30:16.440Z
Electron: 12.0.13
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.13.7-arch1-1

OS Version: Arch Linux

Steps to Reproduce:

Open a text file with VS Code (from desktop, file manager, terminal...)
Maximize VS Code if not maximized already
Minimize VS Code
Open the same or another file

Actual results:

VS Code window is NOT maximized

Expected results:

VS Code window is maximized

Details:

If the bug is not reproducible, try to first resize VS Code window to a small size (e.g. 800x600) then continue from step 2.
I was able to reproduce this bug on Xfce and Gnome (Xorg and Wayland), but not on Windows.
I don't think this is a duplicate of #114632, could be related though
Setting window.titleBarStyle to custom or native makes no difference

https://user-images.githubusercontent.com/599565/129616718-1b364927-6ddc-4484-bb2c-c3f6a9fe3a0b.mp4

Might be OS dependent or Electron specific. All we do when opening the file again is to focus the window, this seems to take away the window state.

@bpasero you're right, I was able to reproduce this bug with electron-quick-start, I just had to add single window behavior based on this snippet.
Now I'm going to investigate electron and ping back if I find something interesting.

Thanks a lot for reporting this to Electron!


Make sure copy-item works with single quotes, changed workfolder to env:systemdrive/temp instead of C:/temp

Changed a few minor things

Escaped the Enable path with single quotes, problems are caused if the path has special characters like {}
Use env:systemdrive/temp to store logging instead of C:/temp, not all machines will have one
Additional error checking when sending data to report server, will now err if not enough permissions

LGTM, but I would change the path to this notation with a backslash character:
$workfolder = "$env:SystemDrive\temp"


Performance

What are the expected nodes per second on a iPhone 14 Pro? With 6 cores I reach little more than 100k nodes/second. With 1 core around 30k nps. Is it possible to improve this?
After deactivating the Neural Network evaluation the nps improved significantly to around 800k nps at 6 cores. This opens up another question: Is the NN evaluation better regarding quality, so that a sacrifice in nps is justified?
I checked out the SmallFish app, unfortunately it does not show nps but it seems to be much faster in reaching a depth of 18-20. Of course given that this number is accurate.

I would offer my help, but I have don't know anything about C++ and how to combine it with Swift. I really hope you can work it out, because your package is really nice and working with it is easy.

Performance has been improved in f4aafb615b34392a5b1fb32ed5a51dc40e92a9a0.


Make Meteor-Files compatible with meteor-desktop (#881)

Meteor Community package meteor-desktop allows to build desktop apps with Meteor & Electron. As far as Meteor is concerned, it works like the Cordova integration, which it piggy-backs. The only needed change is that Meteor.isCordova is replaced by Meteor.isDesktop.
We have been used Meteor-Files & meteor-cookies in a meteor-desktop project, with the proposed code change, for a while without issue.

Thanks for the merge


flutter build macos-framework can't build embeddable frameworks

There should be an option to create a framework that works with the embedder api.
When using flutter build macos-framework the resulting Flutter framework is missing the symbols required to use it with the embedder API.  Without these symbols the project cannot be loaded via the embedder api.
Seen results
$ flutter build macos-framework
...
$ nm build/macos/framework/Release/FlutterMacOS.xcframework/macos-arm64_x86_64/FlutterMacOS.framework/FlutterMacOS | grep FlutterEngineRun
$

Expected results
$ flutter build macos-framework
...
$ nm build/macos/framework/Release/FlutterMacOS.xcframework/macos-arm64_x86_64/FlutterMacOS.framework/FlutterMacOS | grep FlutterEngineRun
000000000096c220 T _FlutterEngineRun
$

cc @cbracken @jmagman

I don't think this is specific to flutter build macos-framework but to FlutterMacOS.framework in release mode.
The symbols are embedded in the Debug framework (DEBUG_INFORMATION_FORMAT=dwarf), but in Release it should be a separate dSYM (DEBUG_INFORMATION_FORMAT=dwarf-with-dsym).  But right now we don't ship the framework dSYM in the SDKs, you have to download them separately. On iOS those instructions are at https://github.com/flutter/flutter/wiki/Crashes#ios, there don't seem to be the same instructions for macOS, but it's the same, example at https://storage.cloud.google.com/flutter_infra_release/flutter/cf69289fbda1a4890d2f2d650a49403884db2992/darwin-x64-release/FlutterMacOS.dSYM.zip.
Ideally we would ship the dSYMs in the SDK and copy them to the right spot for Xcode etc. to find.  iOS feature request at https://github.com/flutter/flutter/issues/79790, I don't see a macOS version.

Without these symbols the project cannot be loaded via the embedder api.

What does that mean, exactly?

Note those symbols are present in Debug, just in Release they are (correctly) stripped in expectation that there will be a dSYM file (which doesn't exist but should).
$ nm build/macos/framework/Debug/FlutterMacOS.xcframework/macos-arm64_x86_64/FlutterMacOS.framework/FlutterMacOS  | grep FlutterEngineRun
0000000000972a00 t _FlutterEngineRun
00000000009743c0 t _FlutterEngineRunInitialized
000000000097b0f0 t _FlutterEngineRunTask
000000000097c4c0 t _FlutterEngineRunsAOTCompiledDartCode

Sorry, it's not clear.  So there are 2 different types of the engine builds: Flutter.framework and FlutterEmbedder.framework.  The Flutter.framework will have the symbols for things like the FlutterViewController.  But if you are creating your own embedder those unnecessary, so there is the FlutterEmbedder.framework which has all the symbols from embedder.h visible.
Why have 2 different frameworks?  An optimization that makes the sizes of the frameworks smaller.
The feature request is that we should have a flag in the tool that will export a built flutter project that is intended to be used with the embedder.h interface.  The output should look something like this:
$ ls
FlutterEmbedder.xcframework
embedder.h
App.xcframework

Currently, the tool just assumes you are using the standard embedder and people writing their own embedders need to go off and build the engine themselves.

@gaaclarke per https://github.com/flutter/flutter/wiki/Custom-Flutter-Engine-Embedders I see flutter/<uuid>/darwin-x64/FlutterEmbedder.framework.zip, but darwin-x64 is the debug directory.  Where are profile and release uploaded to?

This should be blocked on https://github.com/flutter/flutter/issues/111827, the FlutterEmbedder.framework needs to support arm to run natively on M1 Macs


Ledger - BOLOS app messages

@TriPhan96
Can we remove from messages reference to "BOLOS" app. Most Ledger users don't know what it is.
For example message:
"Please open Symbol BOLOS app on your Ledger device" should be changed to "Please open Symbol app on your Ledger device"

Fixed.


Add support for preserving source message timestamp

This feature allows Brooklin to make use of Kafka message's source timestamp when sending the
event to destination cluster. If the mirrored topic is configured with message.timestamp.type
set to CreateTime, the intent is to have the timestamp supplied by the application. This feature
will help achieving this intention.

@celiakung @ahmedahamid could you please review this PR?

@sanjay24 Will do.

thanks @ahmedahamid @somandal

What is the expected timeline for to review this change @ahmedahamid, @somandal? It would be a very useful feature.

Will look into it by end of next week. @mateuszmrozewski

@celiakung could you please check & approve the changes? Thanks

There is still some more work required on this. I'll get back with my discovery and changes

@ahmedahamid @celiakung @somandal KafkaMirrorMakerConnectorTask was translating the records to pass the source event's timestamp only when its timestamp type was "LogAppendTime". Do you know why was it done?
I've updated the PR to pass the correct timestamp when the feature is enabled.

@ahmedahamid could we get moving on the review? Also, when is the next Brooklin release planned?

@ahmedahamid Pinging you to get this reviewed and move ahead on this!


add & remove multiple locks at once per group

Suggested by @obreitwi

closed because duplicate with #611


package upkeep

[x] Update the package to the latest Dart SDK.
[x] updated tests.
[x] I have added the toJson method.

@dustin-graham Hi bud! thanks for your work! When you have a moment, could you please take a look at the pull request? I’d love to hear your thoughts and see if any adjustments are needed before we merge. Thank you!


fix(pictogram-array): use markdown utility

Related Ticket(s)
Addresses #826
Description
Adds new markdown-to-html utility to copy of the pictogram array pattern

Changelog
Changed

Changed copy of pictogram array pattern to use markdown converter utility

Personally I feel like we need to open the flood gate for all markdown, and allow adopters like Drupal to handle the limitations they need. With that said I left a change to align with expectations from the web simplification team, and the functional specs.

Agreed. All options should be turned on, and for this pattern in particular you are manually setting bold to false.

Personally I feel like we need to open the flood gate for all markdown, and allow adopters like Drupal to handle the limitations they need. With that said I left a change to align with expectations from the web simplification team, and the functional specs.

Agreed. All options should be turned on, and for this pattern in particular you are manually setting bold to false.

That's what I had previously, should I just roll back to have it allow all or are you suggesting something else? would it make sense to pass in a flag to the component of accepted styles?

Agreed. All options should be turned on, and for this pattern in particular you are manually setting bold to false.

Just for clarity on my "flood gate" comment above... I was more so referring to even all patterns allowing the use of all markdown features within these rich text copy areas. That way everything is consistent and easier to maintain, and so then adopters like drupal would control what kind of markdown they would like to pass into it by limiting or stripping before rendering. That's my personal opinion at the moment though.


Feature/share trip

This feature enables the possibility to share a trip via the 'Android Easy Share' action in an easily readable text-format.
Feedback on the output-format is welcome. (RouteDetailActivity -> Line 389...)

Issue with sharing trip if walking is involved.
Linked issue: https://github.com/Team-Eight/sthlm-commuter/issues/8#issue-317657732

Resolved #8 as of commit https://github.com/Team-Eight/sthlm-commuter/commit/8c291247bf11ff7ddc427c4fed1b3e79265c7ae6 , refactoring still needed.


Use scale independent PDF completion icons

This commit addresses two issues from older Sergey Mudrik Changed "icons for completion menu to HiDPI version" from PR #12:

The HiDPI icons changed style, from rounded rects to white squares, which are far less readable
New HiDPI icons also look like crap on non-retina screens, as effectively these are downscaled from higher resolution

This commit brings PDF scale independent icons which look sharp on both Retina and lo-res displays, also bringing back old colorful style. All of them were hand-crafted by me.
New PDF icons on lo-res screen

And on Retina

Previous "HiDPI" icons on lo-res screen from PR #12

These look fantastic. Thank you!


integration test overhaul

Issue #, if available:
Description of changes:
Problem
The current CFN template snapshot testing strategy has a very low signal to noise ratio. The diffs are often just asset hash changes or other noise that bloats PRs and reviewers (aka myself) tend to just skip over the template changes because they usually don't have anything useful in them.
Furthermore, the tests themselves are not very valuable anymore. They were implemented before we had a proper e2e suite as a sanity check against some classes of regressions. However, now we have a proper e2e suite that provides stronger assertions than simply checking CDK synth.
Solution
The "in memory" integration test suite has been overhauled to use the CDK assertions library to check for specific template conditions rather than a full snapshot test. Specifically, the assertions are checking that the expected category stacks are being created and that stateful resources in those stacks have stable logical IDs. This seems like a good low-cost sanity check to provide confidence that categories are working together. Tests around individual feature configuration is already happening at the unit test level so we don't need those kinds of assertions at this level. Full e2e tests happen separately in the e2e suite.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Nice! I hope it fix the Health_Check for #754

Tested it out locally, and yes it appears to work with the latest version of tsx


Performance of large LOB application

I would like to use Blazor in LOB (Line of Business) application. Nontrivial LOB applications often have screens with a lot of fields (sometimes 200 or more). It is often necessary to switch between different modules (for example orders, customers, products, etc). User can be in edit mode in orders module and he have to switch to customers module to change for example customer's address. Then he wants to come back to orders module and continue his work. There are a lot of state in each module: values of ordinary fields, calculated fields, information about fields available for editing (some of them are not available because user is not authorized or there are some other business rules). I haven't used Angular but I have read somewhere that it may have performance problems if there are a lot fields on the screen (visible or hidden). This is somehow related to binding and change detection algorithm.
Is Blazor designed for the above use case? Is change detection algorithm fast enough? Can we create and destroy components fast enough?

Yes, we are conscious of the need to support very large UI hierarchies.
Blazor performs diffs on a per-component level, which gives you a lot of flexibility to structure your app in a way that changes are individually cheap even when a huge number of other UI elements are also present. I’ve no doubt it’s easily possible to create artificial slowdown scenarios deliberately, but the expectation is that for realistic UI structures it should be possible to maintain excellent responsiveness given some consideration to how the diffing and DOM updates work.
If you end up building something that has perf issues, we’d love to know more, because making sure things scale well to big apps is one of our key concerns.


Yarn start doesn't work

D:\Repos\budget-tracking>yarn start yarn run v1.22.5 error Command "start" not found. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Hi, welcome to the project!
Sorry, the README.md file is outdated, we are working on it in #177.
To run this project you need to first run yarn to install the dependencies, and then run yarn serve to run the app.
For the next time you get to a JavaScript/TypeScript project, you will know that you can look at a file called package.json and see what commands (scripts) exist:
https://github.com/brafdlog/budget-tracking/blob/c5a719c78af7c44c5cd340a1634da842497d1bf8/package.json#L11-L23
Please try to run, and for any other question, you can open another issue, or if you are not sure it is an issue or just a help request, you can open a new discussion

Hi, welcome to the project!
Sorry, the README.md file is outdated, we are working on it in #177.
To run this project you need to first run yarn to install the dependencies, and then run yarn serve to run the app.
For the next time you get to a JavaScript/TypeScript project, you will know that you can look at a file called package.json and see what commands (scripts) exist:
https://github.com/brafdlog/budget-tracking/blob/c5a719c78af7c44c5cd340a1634da842497d1bf8/package.json#L11-L23
Please try to run, and for any other question, you can open another issue, or if you are not sure it is an issue or just a help request, you can open a new discussion


Update int_classif_universe.ado

hi @gronert-m ,
please check it, I made the changes you requested.
Best,

Thanks for this @alexandraqn !


Insert mode <tab> cause wrong input.

open new empty c file, nvim main.c
go to insert mode, type <tab>

you will see pumvisible() ? "\" : "" be inserted.

I thought this was fixed in #4?  Do you know what plugin that originates from?

@tweekmonster
I just check the verbose, it should be clang2, sorry, I think I am using old version of deoplete-clang2. I just test the latest version, it works well for me, sorry for invalid issue.
:Verbose imap <tab>

i  <Tab>       *@<SNR>176_select_placeholder("i", 1)
	Last set from ~/.cache/vimfiles/.cache/init.vim/.dein/autoload/clang2.vim
i  <Tab>         SpaceVim#mapping#tab()
	Last set from ~/SpaceVim/SpaceVim/autoload/SpaceVim/default.vim

@wsdjeg Oh okay.  No problem!  I thought it was another issue with \ in double quotes.  Good to know it's working :D


When creating a new target record the 'harvester type' in the profile tab defaults to H1 not H3

When creating a new target record the 'harvester type' in the profile tab defaults to H1 not H3. The base profile points correctly to the default Standard Profile.
However when I change H1 to H3 manually the base profile suddenly incorrectly points to the Fast/aggressive profile (the first profile in the list) instead of the default Standard profile.

No longer a bug, unclear when it was resolved


W-11690081 Mule sdk callout fix

Writer's Quality Checklist
Before merging your PR, did you:

[ ] Run spell checker
[ ] Run link checker to check for broken xrefs
[ ] Check for orphan files
[ ] Perform a local build and do a final visual check of your content, including checking for:

Broken images
Dead links
Correct rendering of partials if they are used in your content
Formatting issues, such as:

Misnumbered ordered lists (steps) or incorrectly nested unordered lists
Messed up tables
Proper indentation
Correct header levels

[ ] Receive final review and signoff from:

Technical SME
Product Manager
Editor or peer reviewer
Reporter, if this content is in response to a reported issue (internal or external feedback)

[ ] If applicable, verify that the software actually got released

soooo quick :D thank you!


add mmesh_name feature to multi-matpsecies object

-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 2785
Status: New
Project: VisIt
Tracker: Feature
Priority: Normal
Subject: add mmesh_name feature to multi-matpsecies object
Assigned to: -
Category: -
Target version: -
Author: Mark Miller
Start: 03/15/2017
Due date:
% Done: 0%
Estimated time:
Created: 03/15/2017 08:41 pm
Updated:
Likelihood:
Severity:
Found in version:
Impact: 3 - Medium
Expected Use: 3 - Occasional
OS: All
Support Group: Any
Description:
Comments:

This is a Silo ticket @markcmiller86 .

I've added to silo-issues repo


v0.1.6

What was added

#7 Added support for lists of nested models
Bumped version to v0.1.6

Bump version to v0.1.6


License request

Would it be possible to have a license attributed to this of some sort?
Thanks

If you don't know which license to choose,
I would recommend the MIT-license.

Wow, I'm pretty surprised, that someone is interested in this. License has been added.


Can't create discussion

Everytime I try to create a new discussion the text-editor keeps loading as seen below. It didn't do this before and I don't know why it keeps loading. Please help. I also keep getting "$(...).spectrum is not a function" even though I've installed spectrum through NPM.

Yeah me too. Same problem. I think it's because it's not updated to the latest version of Laravel yet.

If I in Chrome Devtools change the ID 'new_discussion' to something else to corrupt the css/js connected it does work (kind of). I think the loader is just bugged. Anyone any idea how to fix it?

Hey everyone, I believe this is a race condition due to jquery being loaded in app.js and this package trying to synchronously add the spectrum plugin to jquery.
The horrible kludge I am using is to just synchronously load app.js by removing the "defer" attribute from <script src="{{ asset('js/app.js') }}" defer></script> in resources/views/layouts/app.blade.php. (thanks to https://github.com/thedevdojo/chatter/issues/226#issuecomment-438640209)

If you're having issues with the creating new discussions check out
👇
https://github.com/thedevdojo/chatter/issues/244#issuecomment-488680638


Misuse of PBKDF2

NightOS uses a secure algorithm to store passwords, PBKDF2.
However, the salt used isn't very secure : the username.
It could lead to a rainbow table attack because of builtins accounts.
The use of a secure salt (a random string that would be stored alongside the password) could resolve this issue.

I use PBKDF2 with the username as salt just to solve problems when two users have the same password...

(After a long discussion by SMS) OK I will correct that to make impossible attacks using rainbow tables


input of function compute_spin_loss

In the line 87 of the .py file, why opponent_logits_syn is passed into the compute_spin_loss twice? Should it be the missing opponent_logits_gt that is not defined?

You're absolutely right, the opponent_logits_gt term was missing. The implementation in this repo was quickly put together and I didn't get to test it as I'm waiting on compute.
Fixed in ce23eb5


ISPN-15018 temporary remove programmatic mapping of entities docs

needs backport to 14
https://issues.redhat.com/browse/ISPN-15018
Temporary removal of content that is not supported.

Thanks @dvagnero


fix dtls multi-thread crash issue

Description
fix dtls multi-thread crash issue:
refer to:
https://linux.die.net/man/3/crypto_set_locking_callback
http://curl.haxx.se/libcurl/c/opensslthreadlock.html
http://curl.haxx.se/libcurl/c/threaded-ssl.html

Sample code to reproduce the crash bug, it similar with the constructor of DtlsTransport.cpp (erizo/src/erizo/DtlsTransport.cpp)
#include "dtls/DtlsSocket.h"
#include <thread>

const int thread_num = 100;

void func() {
  boost::scoped_ptr<dtls::DtlsSocketContext> dtlsRtp;
  dtlsRtp.reset(new dtls::DtlsSocketContext());
  dtlsRtp->createClient();
}

int main()
{
  dtls::DtlsSocketContext::Init();
  std::thread th[thread_num];
  for (int i = 0; i < 100; i++ ) {
    for (int j = 0; j < thread_num; j++) {
      th[j] = std::thread(func);
    }
    for (int j = 0; j < thread_num; j++) {
      th[j].join();
    }
  }

  return 0;
}

the coredump backtrace looks like:
#0  0x0000000001af7c68 in rsa_pub_cmp ()
#1  0x0000000001a77d81 in X509_check_private_key ()
#2  0x00000000019fb793 in SSL_CTX_use_PrivateKey ()
#3  0x0000000000c0a06a in dtls::DtlsSocketContext::DtlsSocketContext (this=0x7fccccffe000) at /opt/download/licode/erizo/src/erizo/dtls/DtlsClient.cpp

This PR use Linux pthread_mutex_* APIs.
if can be build with c++11 , I think it will be better to use std::mutex, looks like:

Another example code from ffmpeg:
https://github.com/FFmpeg/FFmpeg/blob/master/libavformat/tls_openssl.c

@yuanchao0310 I submitted a proposal with changes for this PR, including a unit test: https://github.com/yuanchao0310/licode/pull/1

@yuanchao0310 I submitted a proposal with changes for this PR, including a unit test: yuanchao0310#1

Merged. Please review again.


Hi, Do you want to submit your script into this library collection, or if you need help with the script, better post into unity forums:  https://forum.unity3d.com/forums/scripting.12/

yes I want to help but you can sumit if you want because this script can move  but it was not my expect

Then its better to post in unity forums first, so can solve the problem there.
(You can then later submit the script here too for others to use)


gh-398: consistent plotting for notebooks

Closes #398. Adds a .matplotlibrc to stabilise the production of plots. For more detail on the config file, look at https://matplotlib.org/stable/users/explain/customizing.html#the-matplotlibrc-file. I haven't used a stylesheet (plt.style.use), as (except for classic) they don't define the resolution etc. https://github.com/matplotlib/matplotlib/tree/main/lib/matplotlib/mpl-data/stylelib.
I did run the notebooks, but they must be using these current values.

@ntessore I've added matplotlibrc symlink to both folders instead

Thanks @paddyroddy, I think this is a nice and clean solution!

I did run the notebooks, but they must be using these current values.

This surprised me, so I had a look. I guess you used our noxfile ... where we forgot to add the --inplace flag to the jupyter execute so that the execution actually changes the notebooks! At the moment, the notebooks run, but their outputs aren't stored anywhere (and our examples' HTML artefacts therefore never change). That's on me, I should have picked up on it in #367.

No, I ran them manually and verified it worked by changing the top level .matplotlibrc


Add support for vim plugin and prerequisite information

Completed in https://github.com/cdevoogd/tilde/commit/289b273cdf16cbdb6d7cf1cc77c24b17496772c4

Completed in https://github.com/cdevoogd/tilde/commit/289b273cdf16cbdb6d7cf1cc77c24b17496772c4


image pull policy updated

Signed-off-by: kumarabd<EMAIL_ADDRESS>Description
Manifests updated with imagePullPolicy: Always
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Codecov Report

Merging #3389 (1d98bfa) into master (05cda78) will decrease coverage by 0.78%.
The diff coverage is 0.28%.

@@            Coverage Diff            @@
##           master   #3389      +/-   ##
=========================================
- Coverage    7.02%   6.24%   -0.79%
=========================================
  Files          23      35      +12
  Lines        1409    2754    +1345
=========================================
+ Hits           99     172      +73
- Misses       1303    2560    +1257
- Partials        7      22      +15

Flag
Coverage Δ

integrationtests
?

unittests
6.24% <0.28%> (-0.79%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

mesheryctl/internal/cli/root/config/config.go
1.11% <0.00%> (-1.12%)
:arrow_down:

mesheryctl/internal/cli/root/perf/perf.go
50.00% <ø> (ø)

mesheryctl/internal/cli/root/system/check.go
1.94% <0.00%> (ø)

mesheryctl/internal/cli/root/system/restart.go
2.50% <0.00%> (-0.54%)
:arrow_down:

mesheryctl/internal/cli/root/system/start.go
1.50% <0.00%> (-0.04%)
:arrow_down:

mesheryctl/internal/cli/root/system/status.go
0.00% <0.00%> (ø)

mesheryctl/internal/cli/root/system/stop.go
1.08% <0.00%> (-0.07%)
:arrow_down:

mesheryctl/pkg/utils/auth.go
0.00% <0.00%> (ø)

mesheryctl/pkg/utils/error.go
0.00% <0.00%> (ø)

mesheryctl/pkg/utils/formatter.go
0.00% <0.00%> (ø)

... and 17 more

Continue to review full report at Codecov.

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


Update covalent docs to be able to toggle between different major @covalent versions (EX: v1.x.x vs v2.x.x docs)

Premise: Developer was trying to get started with<EMAIL_ADDRESS>because their customer did not want to use<EMAIL_ADDRESS>because it was still in beta and was having trouble getting setup because the docs were not version proofed.
Associated with Pavel Ermakov (developer) reported having issues getting started with<EMAIL_ADDRESS>stable, which supports<EMAIL_ADDRESS>in the Covalent slack channel. The current docs/instructions to setup covalent are "more" targeted towards how to setup<EMAIL_ADDRESS>which support<EMAIL_ADDRESS>but<EMAIL_ADDRESS>is not yet stable (beta-2). The Covalent docs say to install the latest @angular/cli in the docs (this gives the developer the latest version of angular that is support by the cli in this case it was<EMAIL_ADDRESS>but when using<EMAIL_ADDRESS>docs/instructions should actually say use<EMAIL_ADDRESS>which support<EMAIL_ADDRESS>We need to look at having different version of Covalent docs (Angular and Angular material do this by having a dropdown to select which version of the docs you want to see) so developers don't have these versioning issues when just trying to get started.
Start of slack convo with Pavel Ermakov about the issue: https://teradata.slack.com/archives/C17U55B4K/p1528581353000014

Dup of https://github.com/Teradata/covalent/issues/1593


Rythmbox pause button disabled with radio streams

After upgrading from Ubuntu 22.04 (Gnome 42.9) to Ubuntu 24.04 (Gnome 46), the pause button stopped working for radio streams in Rythmbox. The pause button is disabled (greyed out) in the bar and in the window popping out when I click.
I tried to check if the problem could be in Rythmbox itself (upgraded from 3.4.4 to 3.4.7), but I see that in its interface for radio streams there's always a stop button (no pause button).
So I guess that in the previous version (v20) the pause button was acting like a stop, while currently (v2.0.1) this is not true anymore.
This is very unfortunate, because is forcing me to open Rythmbox each time to stop the stream, defeating the purpose of having controls in the menu bar.

I tested it and VLC and rythmbox both add the STOP button when Play/Pause is disabled in MPRIS.
This is not a bug that the Pause button is disabled IMHO.
The feature of having a STOP button when Play/Pause is disabled could be an option.

Just to add some context, the default Gnome menu (the one popping up when you click on the clock) shows the proper Pause button for the same case (Rythmbox playing a stream radio)

They do not use the MPRIS interface to show this notification I assume. In MPRIS pause is disabled for streams.


WebGL extensions

Is there any way how I can get WebGL extensions from glow context?
I see an Extensions struct, but it private and used only for internal purposes.
https://github.com/grovesNL/glow/blob/96cc2d4f5691b8ccf20f5cbd92ad25ed920c72cd/src/web_sys.rs#L20-L55

Ok, now I see why the Extensions struct is private :smile: Based on WebGL docs, almost all WebGL extensions are part of WebGL 2.


React Native Build Successfully But not running the app

React Native Build Successfully but not doing anything just stuck on it

Is the app accessible on the android emulator itself?

@AlanFoster yes it is it was running fine before I upgrade the react native

got it solved by reinstalling node.js


Not seeing multiple outputs of versioned spec

This is the versioning sample unchanged.
Playground Link

I'm reproing this without playground too. I got openapi.v1.json and openapi.v2.json before merging main and now I get a single openapi.yaml. cc @timotheeguerin

Yes, it does seem introduced by #1496. You can see it in the sample regen output too:


Avoid LINQ Count method

PR Summary

Refactor code to avoid LINQ Count method.

Full refactor of DoesCurrentRunspaceIncludeCoreHelpCmdlet method

Refactor method parameters to a type that implements ICollection<T> (for the Count property)

IEnumerable<TypeMemberData> -> Dictionary<string, TypeMemberData>.ValueCollection
IEnumerable<PropertySetData> -> List<PropertySetData>

I choose not to use a ICollection<T> type because the enumerator may result in a heap allocation.

PR Context
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[NA] Experimental feature(s) needed

[NA] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[NA] Documentation needed

[NA] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[NA] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[NA] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

@xtqqczze Is it still draft?

@rjmholt Can you review the changes since your last review?


Remove self update mechanism

Every time we update an annotation property we update the source. We should move the responsibility of updating to the end developer to allow to change multiple properties performantly. For example changing the icon, text and location of a symbol will result in 3 updates while these can be consolidated into one.  API wise this will result in making our annotations classes into POJO classes and exposing an AnnotationManager#update method to perform the actual update of the underlying source.

Happening in #700


Add API to look up users by federated ID.

In general we don't add APIs to this SDK that are not already present in the Node.js SDK.
@bojeil-google WDYT?

Hey @hiranya911, I plan to review the Node.js implementation these 2 weeks. It's in my backlog. I think @rsgowman's plan was to launch multiple languages together (including the Java implementation).

Sounds good. I'll assign to @rsgowman for now. Do we have an API proposal for this?

Yeah, link is at: https://docs.google.com/document/d/1OfN5XH6cYJ7y3AnNsocftQSrbMiMaLlPlkWWWsOpDQg/
The proposal is approved.

That only has the bulk get and delete API as far as I can tell. I don't see getUserByFederatedId() in there.

This is somewhat related to the bulk get, but is slightly different. The API doc for this feature is here: http://doc/1ikY2GoQZrwHNJ5mBa---t2o9R-MdjA4np4uW9SJ9dTg. It isn't approved yet (and thus we can't land this, but we don't want to delay starting on it while waiting for the API approval... especially this time of year.)

Oh I didn't know that. I don't understand why this is being implemented before the other then. Definitely let's hold on this.

We'll work on the Node implementation then. Sorry, I didn't know starting with the Node implementation was a must. I started with the Java implementation as the Node implementation was going to be tangled with bulk add/delete changes that are sent for review.

Note I won't have time to review this PR. I will only have time to review the Node.js implementation. That should be the case going forward. @rsgowman and @hiranya911 reviews should be sufficient.


How to maintain bluetooth connection on page navigation/refresh/rerender?

Thanks for maintaining awesome library
I have a questions about maintaining BLE connection when rerendering the page.
Currently we're doing all of our ble-plx stuff within a single page and testing with iOS
  const scanAndConnect = async () => {
    const connectionStatus = await manager.isDeviceConnected(ARDUINODEVICEID);
    if (!connectionStatus) {
      await manager.startDeviceScan(
        [SERVICEUUID],
        null,
        async (error, device) => {
          if (error) {
            throw error;
          }
          if (device.name === "Arduino") {
            setCurrentDevice(device);
            await manager.stopDeviceScan();
            await manager.connectToDevice(device.id, { autoConnect: true });
            await device.discoverAllServicesAndCharacteristics();
            const services = await device.services();
            const characteristics = await manager.characteristicsForDevice(
              ARDUINODEVICEID,
              SERVICEUUID
            );
            const singleCharacteristic = characteristics[0];
            singleCharacteristic
              .monitor(async (error, char) => {
                count++;
                setSensorData(`${count}`);
              })
          }
        }
      );
    } else {
      console.log("DEVICE ALREADY CONNECTED");
    }
  };

Right now we're just doing a count to isolate the issue. But every time we receive data from our arduino, we update the state of count.
The first time
setSensorData(`${count}`);
is called, our connection with the BLE device drops.
Is this because we're inside our page and it should take place at the app level or is there something else we need to do to maintain device connection when rerendering our pages/navigation etc.?
Thanks!

If you need to monitor a characteristic across, it might make sense for you to handle the connection and monitoring in a service (for example) instead of doing it on the page.
I'm not sure if that's your problem, but doing it on a service will guarantee that you don't drop any important variable or state when closing a page.

Can you show how do you handle BleManager instance? I highly recommend to separate BLE from the UI.

Thanks both, separating BLE from UI solved the issue for us!

@jackbridger  can you please elaborate on how you separated BLE from UI? was this done via a background service worker? https://github.com/devfd/react-native-workers

@jackbridger  Hello Jack, i have the same issue, can you please give an example of how did you separate BLE from UI please ? on android it works perfectly without the separation, on iOS everything works but only on the same interface.

@MedRaid I found out how. You need to have the code that manages the BLE connection in a background worker. Here is an example using Saga https://github.com/Cierpliwy/SensorTag/blob/master/src/Saga.js


Update outdated deps, but not the breaking ones

@chriskacerguis   maybe we want to designate this as a regular action to occur at the beginning of each sprint? (unless there a specific need arises necessary)

@miq-bot add_lable  euwe/no, technical debt

@miq-bot add_label  euwe/no, technical debt

@AllenBW agree, great idea!


[top/chip/syn] Remove AST_BYPASS_CLK define in ASIC target

In the meantime, AST has been updated so that it compiles properly on our end when passed through DC synthesis and AscentLint, without having to define the AST_BYPASS_CLK macro.
Hence, the AST_BYPASS_CLK macro does not have to be defined anymore for these targets (that was a workaround to get things going).
See also #9468 and #9548 for context.
Closes #9468 and #9548.

LGTM


issue about advert records from get Timeline data

Hi @liamcottle ,
When I call function getTimelineFeed(), I receive a advert media record in my data. It's from Instagram, not from my following or favourite. So I want remove that record.
How do I know what record is advert? Your code can't do it now.
I see that the advert record will have this fields in response data:
ad_action=webclick
ad_header_style=0
ad_link_type=0
dr_ad_type=1
So I think you may want to add a function to determine the advert account for example: isAdvert();
from Instagram\API\Response\Model\FeedItem Class.
Thanks!

Could you proxy the request and post the JSON as a gist. I don't receive ads in my responses, probably due to where I'm based location wise, so can't check this from my side.

Please see the request and response from attach files.
you can search for "dr_ad_type" field from response text. That's what I mean above
request.txt
response.txt


Added jiggle physics, support for native Package Manager support.

I did the following changes:

Added some default HDRP assets so that the unity project is a bit more usable.
Moved everything into a single ModelReplacementSDK folder. Editor, and Plugin folders are no longer "special" in this version of unity. Instead we use assembly definitions to restrict code to only exist in editor.
Added a package.json, and root level Bunya.ModelReplacementAPI assembly definition (required by the package manager).
Added JigglePhysics to the ModelReplacementAPI assembly directly.
Added a root-level Makefile with a single command to show how to update the package.
Added instructions to the README on how to install the package. (This won't actually work until the Makefile, or the command within it, is ran.)

I haven't tested my changes exactly, as I want to make sure you're comfortable with the direction it's going before I put more work in. Let me know what you think!

I'm always glad when people more knowledgeable than me pitch in. Thanks for settings things up so well.

Pressed the wrong button.


Bold is too bold

Specifically

Form field labels
Create user dropdown
Buttons

Originally created by Tom Smyth at 2018-05-15 09:54, migrated from redmine-#8430

Version set to 6.0

By Tom Smyth at 2018-06-08 12:04

Status changed from New to Closed

By Tom Smyth at 2018-07-02 01:03


Uncaught (in promise) TypeError: Cannot read property 'transaction' of undefined

I followed the documentation and I got this error in the console when I tried to run my index.html file.
I'm missing something?
Looking at the code, the error is related to IndexDB I think:
function getObjectStore(dbName) {
    var mode = arguments.length <= 1 || arguments[1] === undefined ? 'readwrite' : arguments[1];

    var db = dbs[dbName],
        tx = db.transaction(dbName, mode);
    return tx.objectStore(dbName);
}

Commit 52ffb4ebdac1d20b87132cc4122d4a4a138f9e96 fixes it.
Thanks for reporting.


MRG: modify n simultaneous downloads; update buildutils

This PR integrates the changes to BuildUtils (MultiSelection details, minor changes to BuildCollection filtering + writing) that arose from integration into branchwater. It also makes the number of simultaneous downloads tunable, since I was having trouble when using the 3 default permits with large eukaryotic genomes.
It also handles changes associated with zipfile handling from https://github.com/sourmash-bio/sourmash/pull/3431 arising from updating sourmash core to 0.18.0
ref #134

ok @ctb this one is ready for review!