On selecting a soundset, nothing happens.

All soundsets are shown but when I select one, it come back to --no soundsets--
Steps to reporoduce

Go to Music
Select soundsets dropdown menu
Click on one of them

Result: soundsets come back to --no soundsets--

go to folder in the toolbar to select a macro
Macro list is open

Result: no sounds are available
Configuration
MacOS Monterey 12.3.1 on MacBook Air M1
Google Chrome Version 101.0.4951.64 (Build officiel) (arm64)
FoundryVTT: V9 build 269
Syrin-control: 0.3.0
Server is install on my local machine
Screenshots

Logs
Reload Foundry, the
FoundryVTT-SyrinControl.log

I think this is a duplicate of #35

I think this is a duplicate of #35

Indeed.

I am going to close this one in favor of #35 so if you have any questions regarding to this please don't hesitate and write a mail to me or just comment under #35.


Accessible Page Titles

Hidden page titles that are digestible to screenreaders:
Front page: has a title already
Form page: First, verify your identity and tell us why you need a new appointment.
Calendar page: Now, use the calendar to tell us when you're available.
Review page: has a title already
Confirmation page: has a title already

Great to see this! Thanks, Zak!


fix hashes for wrong mainnet range

superseded by https://github.com/ledgerwatch/erigon-snapshot/pull/206


Lockscreen: disabling previous / next controls

First of all thanks for a very nice plugin @ghenry22
Question: is there a way to disable the previous / next controls on the lock screen?
In my case I'm playing one long piece of media -- and there is no previous or next media.
I tried using
hasPrev: false,
hasNext: false
But these will disable the controls in the notifications area (not on the lock screen).
Thanks

@currim want to check with you if you managed to resolve the problem or if it was fixed in the latest version?

@currim want to check with you if you managed to resolve the problem or if it was fixed in the latest version?

@ghenry22  - i ended up using it for multiple "tracks", so it wasn't a requirement for me.  I know your time is limited so I didn't want to trouble you for the feature if it wasn't "affecting" me.
Thank you for checking!

@ghenry22 hey man this is still an issue for me on Samsung s9 running Android 10

Still an issue  for me as well. im using it for a music screaming app so prev/next have no function for a live stream.


Is this integration still working?

Is this integration still working? If it is, I am getting this in my log "'id' not in your device list". Can someone help me. Thank you.

Please make sure the device id is correct.  That's the issue ultimately.
On Fri, Jan 14, 2022, 4:13 PM wnaylor @.***> wrote:

Is this integration still working? If it is, I am getting this in my log
"'id' not in your device list". Can someone help me. Thank you.
—
Reply to this email directly, view it on GitHub
https://github.com/Madj42/ryobi_gdo3/issues/4, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE34CSJCIPXMVDKXEWJOA3TUWCN2LANCNFSM5L73ZTIQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Closing.


Bug in strongly_connected_components

Ref: https://github.com/JuliaGraphs/LightGraphs.jl/issues/71
Graphs.jl has the same issue.

I think I fixed it in LightGraphs. Will submit a PR for examination here shortly.


Set description based on OSM query

if there is no Wikidata link, it would be nice to query OSM and automatically fetch a description that would look like "bar in San Diego", or something of the sort.

As a reminder and for those unaware of it, while you could definitely generate an element description from it, OpenStreetMap’s IDs aren’t meant for long term storage.


Rhino 8 support

I've just been testing out Rhino 8 and I was wondering if anyone has looked at implementing Heron in that package? Some of my other GH install's have come across automatically (Kangaroo) but Heron didn't seem to.

I haven't been testing Heron against Rhino 8 because it's not stable on the Windows side of my MBP 2015. What kind issues or errors are you seeing?  Are you on a Mac or PC?

I am trying to install Heron 4.2 for Rhino 8 but am not able to. @headart did you make any progress?

@andcoder321 are you trying to install via the package manager?  I've fixed a graphics setting on my machine which was previously causing Rhino 8 to crash and can confirm I'm able to run Heron in Rhino 8.  I haven't tested all the components yet, so let me know if there are specific ones that don't work.

I was not (!), was trying to install manually. I'm still new to Rhino.
Package manager worked, and is a big help! Let me try to import this .las
and I'll let you know.
Thanks!!
On Thu, Mar 14, 2024 at 6:37 PM Brian Washburn @.***>
wrote:

@andcoder321 https://github.com/andcoder321 are you trying to install
via the package manager? I've fixed a graphics setting on my machine which
was previously causing Rhino 8 to crash and can confirm I'm able to run
Heron in Rhino 8. I haven't tested all the components yet, so let me know
if there are specific ones that don't work.
image.png (view on web)
https://github.com/blueherongis/Heron/assets/13613796/5dd27e69-a0d9-4eb0-8d19-df36721998d3
—
Reply to this email directly, view it on GitHub
https://github.com/blueherongis/Heron/issues/55#issuecomment-1998922294,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A7VAS75PLXY3IADJEX3SPFLYYJ3HFAVCNFSM6AAAAABBJRFMYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJYHEZDEMRZGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi @ncatunda,
Are you able to post an example file for testing?


Remove perl from fish key bindings.

Perl was used to remove the trailing newline character, but fzf already
has --print0 to use null character as terminators, and fish read -z is
expecting null character as terminators. There is no reason to depend on
perl if --print0 is passed to fzf invocation.

Good point, merged, thanks!


__spreadArrays - this is undefined

Bug Report
I recently came across a Rollup build issue for vue-property-decorator:
(!) this has been rewritten to undefined
https://rollupjs.org/guide/en/#error-this-is-undefined
node_modules/vue-property-decordator/index.js
1: var __spreadArrays = (this && this.__spreadArrays) || function () {
                         ^
2: for (var s = 0, i = 0, il = arguments.length; i < il; i++) s += arguments[i].length;
3: for (var r = Array(s), k = 0, i = 0; i < il; i++)
...and 1 other occurrence

Investigating I found the same issue for the browser-detect package: https://github.com/DamonOehlman/detect-browser/issues/162
Looking a little closer, the root issue appears to be coming from Typescript; specifically the __spreadArrays helper which was added here: commit/375487ec602c7cc8b4dd9e3991ad6145d8bbe21f.
This var is meant to replace the spread operator, but after it has defined itself, it should be reused.
Because this is undefined it always re-defines itself.
🔎 Search Terms

Rollup "this has been rewritten to undefined"
__spreadArrays
"this is undefined"

🕗 Version & Regression Information
Relevant commit is here made on 12 Jun 2019
⏯ Playground Link
The issue is pure JavaScript (this is undefined), and depends on other tools (like Rollup) catching the issue on packages built with Typescript. Not sure how to add that to a playground.
💻 Code

// src/compiler/factory.ts
export const spreadArraysHelper: UnscopedEmitHelper = {
        name: "typescript:spreadArrays",
        scoped: false,
        text: `
            var __spreadArrays = (this && this.__spreadArrays) || function () {
                for (var s = 0, i = 0, il = arguments.length; i < il; i++) s += arguments[i].length;
                for (var r = Array(s), k = 0, i = 0; i < il; i++)
                    for (var a = arguments[i], j = 0, jl = a.length; j < jl; j++, k++)
                        r[k] = a[j];
                return r;
            };`
    };

// tests/baselines/reference/argumentExpressionContextualTyping.js
// tests/baselines/reference/arrayLiteralExpressionContextualTyping.js
// tests/baselines/reference/arrayLiteralSpread.js
// tests/baselines/reference/arrayLiterals2ES5.js
// tests/baselines/reference/arrayLiterals3.js
// Lots and lots more from [the relevant commit](https://github.com/microsoft/TypeScript/commit/375487ec602c7cc8b4dd9e3991ad6145d8bbe21f)
var __spreadArrays = (this && this.__spreadArrays) || function () {
    for (var s = 0, i = 0, il = arguments.length; i < il; i++) s += arguments[i].length;
    for (var r = Array(s), k = 0, i = 0; i < il; i++)
        for (var a = arguments[i], j = 0, jl = a.length; j < jl; j++, k++)
            r[k] = a[j];
    return r;
};

🙁 Actual behavior
When a spread operator ... is used and transformed to __spreadArrays() the code above is added to the top of the file. There is a warning that the this in this && this.__spreadArrays is undefined.
Considering that, I imagine that this function is broken because it will always re-define __spreadArrays with the function
🙂 Expected behavior

Not re-defining __spreadArrays every call
No undefined error

I believe this could be fixed by modifying the first line added to either:
var __spreadArrays = (__spreadArrays !== undefined) || function () {

or
var __spreadArrays = (window.__spreadArrays) || function () {

var __spreadArrays = (window.__spreadArrays) || function () {

window may be undefined as well. This could would lead to a ReferenceError.
It sounds more like an issue with Rollup to me.

window may be undefined as well. This could would lead to a ReferenceError.
Quite possibly - certainly if it's not a browser that uses this.

It sounds more like an issue with Rollup to me.
I believe that if you insert this at the top of a JavaScript file it will be undefined - Rollup is just pointing that out.
Outside of the annoying warning, (this && this.__spreadArrays) || function () {...} will always run function () {...} because this is always undefined. So at the very least I think it may be worthwhile removing (this && this.__spreadArrays) ||

I believe that if you insert this at the top of a JavaScript file it will be undefined

I'm not sure that is true. I couldn't find a case where this would be undefined. It's even defined directly in a NodeJS session.

My mistake. In a browser it appears this at the root is window. So I imagine it's an IDE issue as this at the top of a file is always undefined (as context is not considered). Could global.__spreadArrays replace (this && this.__spreadArrays)? It should be window in a browser and whatever the equivalent is for other platforms (and so always defined)?
I'll raise this with rollup too.

I'm not sure that is true. I couldn't find a case where this would be undefined.

In the top level of an ES module, this is undefined.  For proof, paste the following code into the console of any modern web browser:
(s => { s.textContent = "console.log('this is:' + this)", s.type = "module", document.body.appendChild(s) })(document.createElement("script"))

So typescript's emit doesn't quite make sense when you ask it to transpile down spread but leave everything as modules.

The helper works this way so that you can shim it with an earlier script in a global context.
There's nothing per se wrong with it; Rollup's complaint would be valid if a human wrote this code, but since we use the same helper in all contexts for consistency, it's being overzealous. Rollup should have some way to configure this warning so that it doesn't trigger on this particular snippet.

This issue can be easily solved in rollup by correctly adding any external dependencies as external dependencies in the rollup.config.js (https://rollupjs.org/guide/en/#warning-treating-module-as-external-dependency.
By doing so, rollup skips these ES module checks.
Thanks for everyone's input on this.


ARTEMIS-1224 - change the journal file size to nearest multiple

https://issues.apache.org/jira/browse/ARTEMIS-1224

I could not find if there is check whether journal-file-size is higher or equal to alignment (disc sector size) as it's theoretically minimum value. This is really low risk, just commenting it here whether it's worth to check it. Based on the code, it might happen that journal-file-size is set to 0 if journal-file-size is < (alignment/2)

@mnovak1  I don't think that's an issue:
the min size is not really an issue. min journal size is 1K (because of headers and stuff).. if someone sets 1024 where the align is 4K, it will be adjusted... 1K would be an error:
https://github.com/apache/activemq-artemis/blob/028df470309471842ca3cd9729533c4912107a84/artemis-journal/src/main/java/org/apache/activemq/artemis/core/journal/impl/JournalBase.java#L33-L35


[SPARK-29011][BUILD] Update netty-all from 4.1.30-Final to 4.1.39-Final.

What changes were proposed in this pull request?
Upgrade netty-all to latest in the 4.1.x line which is 4.1.39-Final.
Why are the changes needed?
Currency of dependencies.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Existing unit-tests against 2.4 branch.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Test build #4859 has started for PR 25732 at commit 47aaa52.

Test build #4859 has finished for PR 25732 at commit 47aaa52.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged to 2.4


Is it possible to use without an app and for direct email tunneling?

I am trying to send/recieve email from an outlook account via a gmail account. Can this be used here to get past the 2fa issue. I wanted to do what is described in the solution of this forum question, but is no longer able to be done now that 2fa is required.
What I have done is:

Configure config with outlook client id/secret (create app in azure active directory admin center to generate these)
run server
tried to add as alias from gmail

Issues I have come across:

Wont allow localhost/<IP_ADDRESS> as SMTP server
Ports are drop down of values: 25; 465; 587 -- so i cant set to 1587

Yes - there are several other issues discussing this setup. You'll need to run your own publicly accessible server to do this, however, as Gmail cannot connect to your local host unless it is publicly reachable.

Yes - there are several other issues discussing this setup. You'll need to run your own publicly accessible server to do this, however, as Gmail cannot connect to your local host unless it is publicly reachable.

If I setup a public server running the proxy, can i overwrite port 587 of the machine or will that cause issues?

Yes - you can run the proxy on any port you like. The defaults are chosen simply to avoid having to use sudo in a normal environment.


Update some more benchmarks to use correct evaluation context (PLT-9713) [fourth attempt]

This updates the BLS12-381 and Marlowe benchmarks to use the more precise evaluation strategy introduced in https://github.com/IntersectMBO/plutus/pull/5867.
Trying again without all of the benchmarking noise.

/benchmark validation

/benchmark validation

/benchmark validation

/benchmark validation

/benchmark validation

/benchmark validation

/benchmark nofib

/benchmark marlowe

/benchmark lists

/benchmark validation

/benchmark validation

This seems to work OK now, so I'm going to merge it.  See issue #5906 though.


How to run ghidra disassembler from commandline?

Hi,
I am wondering whether it is possible to run ghidra disassembler from linux command line?  I need to disassemble many files and wondering whether it is possible to use ghidra disassembler for the project.
Thanks,
Rong

I have a similar requirement and will have a look at what "Chunfang Li" did here:
https://github.com/NationalSecurityAgency/ghidra/issues/1334
I have 900 different binaries so I am using IDA as it can be all done in the command line and finds the asm more thoroughly, can be scripted and left to run overnight (they take quite a while to analyse so sitting at at GUI is not applicable).  Ghidra would be my preference going forward.

Use the analyzeHeadless option found in the support directory. I have used it to do analysis on 100's of binaries at once using a script to pull out the information I need and it worked great. My case was using it to pull out information from shared library files.
You can view the .html file in the support folder, but an example command would look like
analyzeHeadless ghidra/Projects Project/folder -scriptPath /user/scripts -preScript yourscript.java -process -recursive

Like @james-tate said, support/analyzeHeadless is what you are looking for.  And like @DarrylC03 said, #1334 is a great reference, especially if you need to output the disassembly to text files.


caffe('get_init_key')   Undefined function 'caffe' for input arguments of type 'char'.

i installed caffe, and clone the rcnn,  and i also run the startup.m  rcnn_build.m with no error ,but when i try to run key = caffe('get_init_key'), i got the following message.

caffe('get_init_key')
Undefined function 'caffe' for input arguments of type 'char'.

I can use matcaffe like caffe.set_mode_gpu(), but I can't use caffe('set_mode_gpu').
anybody can give me the appropriate solution for the problem
Please help.

Were you able to get answers to your question? I am hitting the same issue and not sure what the solution is.

@jainanshul  yeah. Using the caffe of current version may be a leading cause of errors. U can try the following version of caffe: https://github.com/BVLC/caffe/archive/v0.999.tar.gz

Thanks, I got it working withe v0.999 version.

I cannot compile make matcaffe for 0.999 it kept printing linker error from libcaffe.a

I solve it by link the caffe_.mexa64 which is build by make matcaffe to the folder rcnn/bin by below command:
$ ln -s $CAFFE_ROOT/matlab/caffe/private/caffe_.mexa64 $RCNN_ROOT/bin/caffe.mexa64

After make a symlink like this, caffe is found by matlab, but my caffe('get_init_key') get an random key id such as 2.6446e+09, and it is not equal to -2 which is referred in readme file, I don't know why T^T . Now I'm downing pre-trained model and try to run demo of rcnn.
Hope I can help you ^_^

@WideLee   HI ,did you  successfully  run demo of rcnn? I meet  the same question. thanks!


Add a patch to fix CVE-2023-49083

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[x] Ready to merge

Summary

What does the PR accomplish, why was it needed?

This PR adds a patch to fix CVE-2023-49083
Calling load_pem_pkcs7_certificates or load_der_pkcs7_certificates could lead to a NULL-pointer dereference and segfault. Exploitation of this vulnerability poses a serious risk of Denial of Service (DoS) for any application attempting to deserialize a PKCS7 blob/certificate.

Change Log

This is the upstream PR in pyca/cryptography that fixes the issue
There was a comment (regarding raising an exception) that was addressed later on in this PR
The patch has the changes from both of these PRs

Does this affect the toolchain?

NO
Associated issues

Links to CVEs

https://nvd.nist.gov/vuln/detail/CVE-2023-49083

Test Methodology

Buddy Build - Pass

In the GitHub advisory, there is a reproducer for this issue. Used this reproducer to test the patch. Results are below.

Using python3-cryptography-3.3.2-5, we see the seg fault:

Using the updated python3-cryptography-3.3.2-6, we see the ValueError exception being thrown:

Closing. It looks like this has been now patched with #7135.


Upgrades mongo driver and uuid format

Can we release this as a snapshot release, so I can investigate if this fixes our current UUID issues?
Also I guess it must become a major release, as not fully backwards compatible. Roundtrips work but the encoded DBObject might look a bit different with the uuid being already in a binary format.
Due to deprecation of the default JAVA_LEGACY as uuid representation for BSON we have to manually do that otherwise the mongo db client might insert the correct uuid format (if configured), but functions like equals, toJson and toString will fail on BasicDBObjects.

@yannick-cw do we still new this PR?

No thanks!


Add more columns to demographics export.

Description

Enable "creation time" for applications.

in doing this, discovered that the logic around draft applications got deleted at some point, re-enabled it.

Enable TI group name
obfuscated email of submitter
stop obfuscating empty values for non-applicant columns - no PII being leaked there.
unrelated, but also stop logging so much auth stuff.  it's not useful and it means the logs might contain PII depending on what the auth server sends back, and that might lead to a mess later on.

Checklist

[ ] Created tests which fail without the change (if possible)
[ ] Extended the README / documentation, if necessary

Issue(s)

I think the browser tests should cover it.


upgrading from 4.1.1 to 6.0.0

Hi, @jhnns.
I was wondering if you could help with some sass-loader related troubleshooting. I've got errors from three different modules and I've isolated the cause for all the errors to upgrading sass-loader from 4.1.1 to 6.0.0. These errors are all from https://github.com/Judahmeek/bootstrap-loader/tree/update-dependencies/examples/basic and any assistance you (or others) can provide contributes directly towards bootstrap-loader's compatibility with sass-loader.
Module 1:
ERROR in ./~/extract-text-webpack-plugin/loader.js?{"omit":1,"remove":true}!./~/style-loader!./~/css-loader!./~/resolve-url-loader!./~/sass-loader/lib/loader.js?sourceMap!./~/bootstrap-loader/lib/bootstrap.styles.loader.js?{"bootstrapVersion":3,"preBootstrapCustomizations":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/app/styles/bootstrap/pre-customizations.scss","bootstrapCustomizations":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/app/styles/bootstrap/customizations.scss","appStyles":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/app/styles/app.scss","useCustomIconFontPath":false,"extractStyles":true,"styleLoaders":["style-loader","css-loader","sass-loader"],"styles":["mixins","normalize","print","glyphicons","scaffolding","type","code","grid","tables","forms","buttons","component-animations","dropdowns","button-groups","input-groups","navs","navbar","breadcrumbs","pagination","pager","labels","badges","jumbotron","thumbnails","alerts","progress-bars","media","list-group","panels","wells","responsive-embed","close","modals","tooltip","popovers","carousel","utilities","responsive-utilities"],"scripts":["transition","alert","button","carousel","collapse","dropdown","modal","tooltip","popover","scrollspy","tab","affix"],"configFilePath":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/.bootstraprc-3-example","bootstrapPath":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/~/bootstrap-sass","bootstrapRelPath":"../bootstrap-sass"}!./~/bootstrap-loader/no-op.js
Module build failed: Error
    at factoryCallback (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/webpack/lib/Compilation.js:259:39)
    at /Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/webpack/lib/NormalModuleFactory.js:234:19
    at onDoneResolving (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/webpack/lib/NormalModuleFactory.js:59:20)
    at /Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/webpack/lib/NormalModuleFactory.js:126:20
    at /Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/async/dist/async.js:3694:9
    at /Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/async/dist/async.js:356:16
    at iteratorCallback (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/async/dist/async.js:934:13)
    at /Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/async/dist/async.js:840:16
    at /Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/async/dist/async.js:3691:13
    at apply (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/async/dist/async.js:21:25)
    at /Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/async/dist/async.js:56:12
    at /Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/webpack/lib/NormalModuleFactory.js:121:22
    at onResolved (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/enhanced-resolve/lib/Resolver.js:70:11)
    at loggingCallbackWrapper (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/enhanced-resolve/lib/createInnerCallback.js:31:19)
    at afterInnerCallback (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/enhanced-resolve/lib/Resolver.js:138:10)
    at loggingCallbackWrapper (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/enhanced-resolve/lib/createInnerCallback.js:31:19)
    at Resolver.applyPluginsAsyncSeriesBailResult1 (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/tapable/lib/Tapable.js:181:46)
    at innerCallback (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/enhanced-resolve/lib/Resolver.js:125:19)
    at loggingCallbackWrapper (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/enhanced-resolve/lib/createInnerCallback.js:31:19)
    at /Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/tapable/lib/Tapable.js:283:15
    at /Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/enhanced-resolve/lib/UnsafeCachePlugin.js:38:4
    at loggingCallbackWrapper (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/enhanced-resolve/lib/createInnerCallback.js:31:19)
    at afterInnerCallback (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/enhanced-resolve/lib/Resolver.js:138:10)
    at loggingCallbackWrapper (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/enhanced-resolve/lib/createInnerCallback.js:31:19)
    at Resolver.applyPluginsAsyncSeriesBailResult1 (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/tapable/lib/Tapable.js:181:46)
    at innerCallback (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/enhanced-resolve/lib/Resolver.js:125:19)
    at loggingCallbackWrapper (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/enhanced-resolve/lib/createInnerCallback.js:31:19)
    at /Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/tapable/lib/Tapable.js:283:15
    at innerCallback (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/enhanced-resolve/lib/Resolver.js:123:11)
    at loggingCallbackWrapper (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/enhanced-resolve/lib/createInnerCallback.js:31:19)
 @ ./~/bootstrap-loader/lib/bootstrap.loader.js?extractStyles&configFilePath=/Users/judahmeek/Apps/bootstrap-loader/examples/basic/.bootstraprc-3-example!./~/bootstrap-loader/no-op.js 1:21-1696
 @ multi font-awesome-loader bootstrap-loader/lib/bootstrap.loader?extractStyles&configFilePath=/Users/judahmeek/Apps/bootstrap-loader/examples/basic/.bootstraprc-3-example!bootstrap-loader/no-op.js tether ./app/scripts/app

ERROR in ./~/extract-text-webpack-plugin/loader.js?{"omit":1,"remove":true}!./~/style-loader!./~/css-loader!./~/resolve-url-loader!./~/sass-loader/lib/loader.js?sourceMap!./~/bootstrap-loader/lib/bootstrap.styles.loader.js?{"bootstrapVersion":3,"preBootstrapCustomizations":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/app/styles/bootstrap/pre-customizations.scss","bootstrapCustomizations":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/app/styles/bootstrap/customizations.scss","appStyles":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/app/styles/app.scss","useCustomIconFontPath":false,"extractStyles":true,"styleLoaders":["style-loader","css-loader","sass-loader"],"styles":["mixins","normalize","print","glyphicons","scaffolding","type","code","grid","tables","forms","buttons","component-animations","dropdowns","button-groups","input-groups","navs","navbar","breadcrumbs","pagination","pager","labels","badges","jumbotron","thumbnails","alerts","progress-bars","media","list-group","panels","wells","responsive-embed","close","modals","tooltip","popovers","carousel","utilities","responsive-utilities"],"scripts":["transition","alert","button","carousel","collapse","dropdown","modal","tooltip","popover","scrollspy","tab","affix"],"configFilePath":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/.bootstraprc-3-example","bootstrapPath":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/~/bootstrap-sass","bootstrapRelPath":"../bootstrap-sass"}!./~/bootstrap-loader/no-op.js
Module build failed: Error
    at factoryCallback (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/webpack/lib/Compilation.js:259:39)
    at /Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/webpack/lib/NormalModuleFactory.js:234:19
    at onDoneResolving (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/webpack/lib/NormalModuleFactory.js:59:20)
    at /Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/webpack/lib/NormalModuleFactory.js:126:20
    at /Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/async/dist/async.js:3694:9
    at /Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/async/dist/async.js:356:16
    at iteratorCallback (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/async/dist/async.js:934:13)
    at /Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/async/dist/async.js:840:16
    at /Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/async/dist/async.js:3691:13
    at apply (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/async/dist/async.js:21:25)
    at /Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/async/dist/async.js:56:12
    at /Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/webpack/lib/NormalModuleFactory.js:121:22
    at onResolved (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/enhanced-resolve/lib/Resolver.js:70:11)
    at loggingCallbackWrapper (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/enhanced-resolve/lib/createInnerCallback.js:31:19)
    at afterInnerCallback (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/enhanced-resolve/lib/Resolver.js:138:10)
    at loggingCallbackWrapper (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/enhanced-resolve/lib/createInnerCallback.js:31:19)
    at Resolver.applyPluginsAsyncSeriesBailResult1 (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/tapable/lib/Tapable.js:181:46)
    at innerCallback (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/enhanced-resolve/lib/Resolver.js:125:19)
    at loggingCallbackWrapper (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/enhanced-resolve/lib/createInnerCallback.js:31:19)
    at /Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/tapable/lib/Tapable.js:283:15
    at /Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/enhanced-resolve/lib/UnsafeCachePlugin.js:38:4
    at loggingCallbackWrapper (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/enhanced-resolve/lib/createInnerCallback.js:31:19)
    at afterInnerCallback (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/enhanced-resolve/lib/Resolver.js:138:10)
    at loggingCallbackWrapper (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/enhanced-resolve/lib/createInnerCallback.js:31:19)
    at Resolver.applyPluginsAsyncSeriesBailResult1 (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/tapable/lib/Tapable.js:181:46)
    at innerCallback (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/enhanced-resolve/lib/Resolver.js:125:19)
    at loggingCallbackWrapper (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/enhanced-resolve/lib/createInnerCallback.js:31:19)
    at /Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/tapable/lib/Tapable.js:283:15
    at innerCallback (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/enhanced-resolve/lib/Resolver.js:123:11)
    at loggingCallbackWrapper (/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/enhanced-resolve/lib/createInnerCallback.js:31:19)

ERROR in /Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/extract-text-webpack-plugin/loader.js?{"omit":1,"remove":true}!/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/style-loader/index.js!/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/css-loader/index.js!/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/resolve-url-loader/index.js!/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/sass-loader/lib/loader.js?sourceMap!/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/bootstrap-loader/lib/bootstrap.styles.loader.js?{"bootstrapVersion":3,"preBootstrapCustomizations":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/app/styles/bootstrap/pre-customizations.scss","bootstrapCustomizations":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/app/styles/bootstrap/customizations.scss","appStyles":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/app/styles/app.scss","useCustomIconFontPath":false,"extractStyles":true,"styleLoaders":["style-loader","css-loader","sass-loader"],"styles":["mixins","normalize","print","glyphicons","scaffolding","type","code","grid","tables","forms","buttons","component-animations","dropdowns","button-groups","input-groups","navs","navbar","breadcrumbs","pagination","pager","labels","badges","jumbotron","thumbnails","alerts","progress-bars","media","list-group","panels","wells","responsive-embed","close","modals","tooltip","popovers","carousel","utilities","responsive-utilities"],"scripts":["transition","alert","button","carousel","collapse","dropdown","modal","tooltip","popover","scrollspy","tab","affix"],"configFilePath":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/.bootstraprc-3-example","bootstrapPath":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/bootstrap-sass","bootstrapRelPath":"../bootstrap-sass"}!/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/bootstrap-loader/no-op.js doesn't export content

Module 2:
WARNING in ./~/css-loader!./~/resolve-url-loader!./~/sass-loader/lib/loader.js?sourceMap!./~/bootstrap-loader/lib/bootstrap.styles.loader.js?{"bootstrapVersion":3,"preBootstrapCustomizations":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/app/styles/bootstrap/pre-customizations.scss","bootstrapCustomizations":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/app/styles/bootstrap/customizations.scss","appStyles":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/app/styles/app.scss","useCustomIconFontPath":false,"extractStyles":true,"styleLoaders":["style-loader","css-loader","sass-loader"],"styles":["mixins","normalize","print","glyphicons","scaffolding","type","code","grid","tables","forms","buttons","component-animations","dropdowns","button-groups","input-groups","navs","navbar","breadcrumbs","pagination","pager","labels","badges","jumbotron","thumbnails","alerts","progress-bars","media","list-group","panels","wells","responsive-embed","close","modals","tooltip","popovers","carousel","utilities","responsive-utilities"],"scripts":["transition","alert","button","carousel","collapse","dropdown","modal","tooltip","popover","scrollspy","tab","affix"],"configFilePath":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/.bootstraprc-3-example","bootstrapPath":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/~/bootstrap-sass","bootstrapRelPath":"../bootstrap-sass"}!./~/bootstrap-loader/no-op.js
      resolve-url-loader cannot operate: source-map error
      ENOENT: no such file or directory, scandir '/Users/judahmeek/Apps/bootstrap-loader/examples/basic/public/assets'

    ERROR in ./~/css-loader!./~/resolve-url-loader!./~/sass-loader/lib/loader.js?sourceMap!./~/bootstrap-loader/lib/bootstrap.styles.loader.js?{"bootstrapVersion":3,"preBootstrapCustomizations":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/app/styles/bootstrap/pre-customizations.scss","bootstrapCustomizations":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/app/styles/bootstrap/customizations.scss","appStyles":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/app/styles/app.scss","useCustomIconFontPath":false,"extractStyles":true,"styleLoaders":["style-loader","css-loader","sass-loader"],"styles":["mixins","normalize","print","glyphicons","scaffolding","type","code","grid","tables","forms","buttons","component-animations","dropdowns","button-groups","input-groups","navs","navbar","breadcrumbs","pagination","pager","labels","badges","jumbotron","thumbnails","alerts","progress-bars","media","list-group","panels","wells","responsive-embed","close","modals","tooltip","popovers","carousel","utilities","responsive-utilities"],"scripts":["transition","alert","button","carousel","collapse","dropdown","modal","tooltip","popover","scrollspy","tab","affix"],"configFilePath":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/.bootstraprc-3-example","bootstrapPath":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/~/bootstrap-sass","bootstrapRelPath":"../bootstrap-sass"}!./~/bootstrap-loader/no-op.js
    Module not found: Error: Can't resolve '../fonts/OpenSans-Light.ttf' in '/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/bootstrap-loader'
     @ ./~/css-loader!./~/resolve-url-loader!./~/sass-loader/lib/loader.js?sourceMap!./~/bootstrap-loader/lib/bootstrap.styles.loader.js?{"bootstrapVersion":3,"preBootstrapCustomizations":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/app/styles/bootstrap/pre-customizations.scss","bootstrapCustomizations":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/app/styles/bootstrap/customizations.scss","appStyles":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/app/styles/app.scss","useCustomIconFontPath":false,"extractStyles":true,"styleLoaders":["style-loader","css-loader","sass-loader"],"styles":["mixins","normalize","print","glyphicons","scaffolding","type","code","grid","tables","forms","buttons","component-animations","dropdowns","button-groups","input-groups","navs","navbar","breadcrumbs","pagination","pager","labels","badges","jumbotron","thumbnails","alerts","progress-bars","media","list-group","panels","wells","responsive-embed","close","modals","tooltip","popovers","carousel","utilities","responsive-utilities"],"scripts":["transition","alert","button","carousel","collapse","dropdown","modal","tooltip","popover","scrollspy","tab","affix"],"configFilePath":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/.bootstraprc-3-example","bootstrapPath":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/~/bootstrap-sass","bootstrapRelPath":"../bootstrap-sass"}!./~/bootstrap-loader/no-op.js 6:110-148

Module 3:
WARNING in ./~/css-loader!./~/resolve-url-loader!./~/sass-loader/lib/loader.js?sourceMap!./~/bootstrap-loader/lib/bootstrap.styles.loader.js?{"bootstrapVersion":3,"preBootstrapCustomizations":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/app/styles/bootstrap/pre-customizations.scss","bootstrapCustomizations":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/app/styles/bootstrap/customizations.scss","appStyles":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/app/styles/app.scss","useCustomIconFontPath":false,"extractStyles":true,"styleLoaders":["style-loader","css-loader","sass-loader"],"styles":["mixins","normalize","print","glyphicons","scaffolding","type","code","grid","tables","forms","buttons","component-animations","dropdowns","button-groups","input-groups","navs","navbar","breadcrumbs","pagination","pager","labels","badges","jumbotron","thumbnails","alerts","progress-bars","media","list-group","panels","wells","responsive-embed","close","modals","tooltip","popovers","carousel","utilities","responsive-utilities"],"scripts":["transition","alert","button","carousel","collapse","dropdown","modal","tooltip","popover","scrollspy","tab","affix"],"configFilePath":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/.bootstraprc-3-example","bootstrapPath":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/~/bootstrap-sass","bootstrapRelPath":"../bootstrap-sass"}!./~/bootstrap-loader/no-op.js
      resolve-url-loader cannot operate: source-map error
      ENOENT: no such file or directory, scandir '/Users/judahmeek/Apps/bootstrap-loader/examples/basic/public/assets'

    ERROR in ./~/css-loader!./~/resolve-url-loader!./~/sass-loader/lib/loader.js?sourceMap!./~/bootstrap-loader/lib/bootstrap.styles.loader.js?{"bootstrapVersion":3,"preBootstrapCustomizations":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/app/styles/bootstrap/pre-customizations.scss","bootstrapCustomizations":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/app/styles/bootstrap/customizations.scss","appStyles":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/app/styles/app.scss","useCustomIconFontPath":false,"extractStyles":true,"styleLoaders":["style-loader","css-loader","sass-loader"],"styles":["mixins","normalize","print","glyphicons","scaffolding","type","code","grid","tables","forms","buttons","component-animations","dropdowns","button-groups","input-groups","navs","navbar","breadcrumbs","pagination","pager","labels","badges","jumbotron","thumbnails","alerts","progress-bars","media","list-group","panels","wells","responsive-embed","close","modals","tooltip","popovers","carousel","utilities","responsive-utilities"],"scripts":["transition","alert","button","carousel","collapse","dropdown","modal","tooltip","popover","scrollspy","tab","affix"],"configFilePath":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/.bootstraprc-3-example","bootstrapPath":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/~/bootstrap-sass","bootstrapRelPath":"../bootstrap-sass"}!./~/bootstrap-loader/no-op.js
    Module not found: Error: Can't resolve '../fonts/OpenSans-Light.ttf' in '/Users/judahmeek/Apps/bootstrap-loader/examples/basic/node_modules/bootstrap-loader'
     @ ./~/css-loader!./~/resolve-url-loader!./~/sass-loader/lib/loader.js?sourceMap!./~/bootstrap-loader/lib/bootstrap.styles.loader.js?{"bootstrapVersion":3,"preBootstrapCustomizations":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/app/styles/bootstrap/pre-customizations.scss","bootstrapCustomizations":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/app/styles/bootstrap/customizations.scss","appStyles":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/app/styles/app.scss","useCustomIconFontPath":false,"extractStyles":true,"styleLoaders":["style-loader","css-loader","sass-loader"],"styles":["mixins","normalize","print","glyphicons","scaffolding","type","code","grid","tables","forms","buttons","component-animations","dropdowns","button-groups","input-groups","navs","navbar","breadcrumbs","pagination","pager","labels","badges","jumbotron","thumbnails","alerts","progress-bars","media","list-group","panels","wells","responsive-embed","close","modals","tooltip","popovers","carousel","utilities","responsive-utilities"],"scripts":["transition","alert","button","carousel","collapse","dropdown","modal","tooltip","popover","scrollspy","tab","affix"],"configFilePath":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/.bootstraprc-3-example","bootstrapPath":"/Users/judahmeek/Apps/bootstrap-loader/examples/basic/~/bootstrap-sass","bootstrapRelPath":"../bootstrap-sass"}!./~/bootstrap-loader/no-op.js 6:110-148

Completely and utterly solved by https://github.com/bholloway/resolve-url-loader/pull/45. I'm rather blown away.  :)


feat(icons)!: update SparkIcon type definition and values

⚠ Breaking changes

The new SparkIcon is now a sealed class:
public sealed class SparkIcon {
    public data class<EMAIL_ADDRESS>val drawableId: Int) :
SparkIcon()
    public data class Vector(val imageVector: ImageVector) : SparkIcon()
}

Most resources have changed either by name and/or by content.
This will now take spark-tokens as the only source of truth
Icons are now exposed as property extensions of the SparkIcons object, and they no longer have a category hierarchy.
Example:
public val SparkIcons.Accessories: SparkIcon get() =
SparkIcon.DrawableRes(R.drawable.spark_icons_accessories)

UpNavigationIcon now correctly uses the default icon size for the "back arrow" instead of 16.dp.

spark-icons-kt.main.kts
This PR also adds a new spark-icons-kt.main.kts Kotlin script that will be responsible to expose all spark-icons/src/main/res/drawable as Kotlin API.
It will be run automatically by the pr-icon-updates.yml workflow.
Usage:
./scripts/spark-icons-kt/spark-icons-kt.main.kts \
    --input="spark-icons/src/main/res/drawable" \
    --output="spark-icons/src/main/kotlin/com/adevinta/spark/icons/SparkIcons.kt" \
    --copyright="scripts/spark-icons-kt/COPYRIGHT.kt"

References

#403
#393

@spark-ui-bot paparazzi golden images


Storage elasticsearch health check

These changes intend to add health checks to elasticsearch storage plugin.

Update elasticsearch client 6.x and 7.x to the latest version, which tries to fix some underlying connection issues.

Upgrading client is hard, let's leave them alone.

Add HealthChecker to combinate between provider and storage service client. The HealthChecker opts to "sync" strategy which means it doesn't set up an async scheduler to check backend server periodically. That is because our persistence timer will touch the storage server every 3 seconds(the default value), so we can leverage it as a health checking trigger.
Some users report issues like https://github.com/elastic/elasticsearch/issues/39946, in this PR, I fix this issue by recreating a new RestClient once catching the IllegalStateExecption indicate the collection pool is closed under the hood.

I only update the elasticsearch 6 in the current commit. After getting enough feedbacks to polish the implementation, I will update elasticsearch 7 accordingly.

@wu-sheng I enclose the gauge value into a new metric class, HealthCheckMetrics, so other developers don't have to set the value directly.
But when I try to move the initialization of the client to the start phase, some other module, for instance, CoreModule, complains they can't find the service provided by Storage modules. It seems we must keep the registration of storage service in the prepare phase. So I add a new DeletegatedHealthChecker as a final field of client classes, it can receive the HealthChecker created by Telemetry module, that's available in the start phase.


Allow additional custom tests in the generator

For some exercises it makes sense to add some language specific test cases additional to what is listed in the problem spec test cases.
Here an example where this would be helpful: https://github.com/exercism/go/issues/1451
Let's discuss ideas how to adjust the generator to incorporate additional test cases. The restriction should be that the new cases adhere to the format of the existing ones (e.g. no new properties are introduced).

What about having a canonical-data.append.json in the .meta directory for the exercise?

@andrerfcsantos Great idea! That shouldn't be hard and the generator is in that directory already anyway.
So the task here is to change the generator so that it checks whether .meta/canonical-data.append.json is present for the exercise. If it it is, the content should be combined with the content of the usual canonical-data.json file.
General information about the generator can be found here: https://github.com/exercism/go#generating-test-cases

@eklatzer Not sure whether you mean you want to include this in #2279 but if yes, it would be better if this would be separate PR. Otherwise if the added code for this feature has issues that blocks the other PR for now reason. And the more things are in one PR, the harder it is to review.

I will wait for #2279 to be merged and then I will do it

Note for future: we could use the feature of this issue in the exercise reverse-string as there is currently the following additional test case:
// mutiByteCases adds UTF-8 multi-byte case,
// since the canonical-data.json (generator data source for cases_test.go)
// doesn't have any such cases.
var multiByteCases = []reverseTestCase{
	{
		description: "a multi-byte test case",
		input:       "Hello, 世界",
		expected:    "界世 ,olleH",
	},
}

Same for roman-numerals (will also need adjustment in the generator):
invalidRomanNumeralTests := []romanNumeralTest{
		{description: "0 is out of range", input: 0},
		{description: "-1 is out of range", input: -1},
		{description: "3001 is out of range", input: 3001},
	}

Same for two-bucket:
var errorTestCases = []bucketTestCase{
	{
		"Invalid first bucket size",
		0, 5, 5, "one", "one", 1, 0, true,
	},
	{
		"Invalid second bucket size",
		3, 0, 3, "one", "one", 1, 0, true,
	},
	{
		"Invalid goal amount",
		1, 1, 0, "one", "one", 0, 1, true,
	},
	{
		"Invalid start bucket name",
		3, 5, 1, "three", "one", 4, 5, true,
	},
}

@eklatzer Please don't start on this yet. I think we need to discuss again what is the best approach here. I am not sure anymore the extra json file helps us much compared to what was done in those examples you found. I will leave some more thoughts on this later.

Sorry for putting this on hold, here my thoughts on the matter.
When I originally wrote this issue, I did not know we already had a "solution" for adding custom tests. Comparing the existing solution of appending test cases to the generated test cases list to the idea in this issue to have a separate json file, it feels to me the existing way might be better. The idea with the json file only works if the format in the json file fits exactly to the format in the problem spec canonical file. So someone who wants to add a test case needs to go there and figure out this format. In contrast, with the existing solution, the person just needs to look at the existing cases file and then write the item that should be appended in plain Go.
@eklatzer WDYT?
So my tendency would be to not add any feature to the generator and instead document this existing system in the readme (a link to an example would probably already go a long way here). In any case, I would like to keep this issue open to track the missing documentation.

I completely agree, do you want me to add the docs?


Toyota: use FW query for DSU detection

Did you run something on a few thousand segments to see if the DSU always responds nicely? If it wouldn't respond it would still fingerprint, so you wouldn't directly notice this.

Checked all the Toyota routes from the last week and this matches the old behavior for 15824 / 16163. Most of the mismatches don't get any FW at all, not just the DSU. We can hold off on merging this cleanup until we look into firmware fingerprinting reliability.

Noticed some people don't plug in the comma power v2, or they do have it plugged in but have some sort of connection issue. They likely wouldn't know if their car works using fp1.0 anyway :/

How will this work with S-DSU? Will it still work as it did before?

Doesn't affect SDSU.

We don't have access to the fingerprint source in get_params so changed it to just check the length of the firmware array to check if the comma power was plugged in.


✨ Update community link

I suppose you leave "slackCommunity" not to cause further complex changes?

I just removed, because it don't used anymore, the new link is in "start_page.md" just for empty datasets page.


[Site] fix font-smoothing

Description
font-smoothing is not valid. There are only webkit and mozilla font smoothing.

Fixed in Fomantic-UI by https://github.com/fomantic/Fomantic-UI/pull/563


adding registration.php

registration.php was missing, without it You are not able to install this module. Hope this helps

You are right, thanks ! I forgot to add it on this sample plugin after the october update !

You are right, thanks ! I forgot to add it on this sample plugin after the october update !

 :)


[CI:DOCS] Bump master version

Bump master to v2.1.0-dev now that v2.0.0 is released.
Update release notes and readme on master as well.

LGTM

LGTM

/lgtm
/hold
will let @mheon cancel the hold

/hold cancel


Creation of pre-training dataset

Hi, this work is fascinating
Can you provide the source code that is used to create the datasets pertaining to the MolTC?

Gibbs free energy pre-training data processing source code: (https://github.com/MangoKiller/MolTC/blob/main/pretrain_data.py), the corresponding data file is: https://huggingface.co/chang04/ddi/blob/main/data/solve_data/pre_train_data.txt

Thanks for you reply. I want to create my own dataset like gibs free energy
dataset you have created.. could you please share how you curated that
dataset...
On Fri, 23 Aug 2024, 19:55 JunfengFang, @.***> wrote:

Gibbs free energy pre-training data processing source code: (
https://github.com/MangoKiller/MolTC/blob/main/pretrain_data.py), the
corresponding data file is:
https://huggingface.co/chang04/ddi/blob/main/data/solve_data/pre_train_data.txt
—
Reply to this email directly, view it on GitHub
https://github.com/MangoKiller/MolTC/issues/3#issuecomment-2307205524,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQ7MTCU4V467D674LS6KLGTZS5A4NAVCNFSM6AAAAABMSUIA3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBXGIYDKNJSGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

We did not do much processing on the pre-training dataset because its format is consistent with that of the downstream tasks. This is the reference paper of our pre-training dataset: "Transfer learning for solvation free energies: From quantum chemistry to experiments". I don't know if it can solve your question.

I have another query, can you please clarify how you saved the Lora model?


Fused about QSL

I am fused about QSL,  I have noticed there is explaination about QSL in README:   For performance runs, the LoadGen will select queries uniformly at random (with replacement) from a test set. The minimum size of the performance test set for each benchmark is listed as 'QSL Size' in the table above.
Here is my question:

QSL is short for what?  it is Query Sample Length ??
What QSL effect?  Latency or throughoutput ?, How QSL effect performance ?
The relationship between QSL and Dataset sample counts

you can learn more about QSL in the loadgen source code at:
https://github.com/mlcommons/inference/blob/master/loadgen/loadgen.cc#L1542

you can learn more about QSL in the loadgen source code at:
https://github.com/mlcommons/inference/blob/master/loadgen/loadgen.cc#L1542

please re-open if needed

please re-open if needed


[1570] Rename QTS related things to more general Award term

Context

https://trello.com/c/DTbBTUfK/1601-rename-qts-to-award-code-only

Changes proposed in this pull request
EYTS is awarded under similar terms as QTS but with different params. Unfortunately we've labelled everything to QTS. Following that route means we'd create duplicate classes doing very similar things. This PR refactors naming to a more general "Award" term.
The changes are only at the code level, not user facing. Users will still see the everything as the app currently is.
Guidance to review
I have already done a regression test locally but will need to do the same on QA to make sure everything still works as expected.

 Rename QTS to Award (code only)

Does the export needs to correlate?

Does the export needs to correlate?

Fixed


eslint-index

I have created an ESLint utility module inspired by eslint-find-rules that I thought you might find useful.
The module is called eslint-index and you can read the full documentation on npm.
eslint-index provides a great deal of functionality including:

List all available rules declared by ESLint and any plugins you have included
Colour code rules depending on their status:

omitted (not declared anywhere in you ESLint config file)
0|off (declared, but set to 0|off)
1|warn
2|error

Display links to the rule documentation page next to each rule
Filter/reject rules by their status and/or their group

status is as described above (omitted|off|warn|error)
group is eslint for the core ESLint rules or the name of any of your plugins like react|import|flowtype

Format the output as a number or a table to get an overview of your rule settings
Rules that have been marked as deprecated are removed from all outputs
All of the above filters and formatting can be combined, for example:

filter omitted and off rules, output them as a list and display the rule doc links alongside
filter eslint rules and display the rule setting counters in a table

I wrote this plugin to aid the development of my own ESLint config settings and found it incredibly useful for keeping track of everything. I hope you find this module useful and please do let me know if you have any ideas on how to improve it.

We're adopting eslint-index in this PR.  @wagerfield, thanks for letting us know about this!

@GoodForOneFare thanks for taking a look at eslint-index, though the link to the PR you posted above doesn't resolve.
I had a look back over the recently merged PR's and none of them introduce eslint-index? I also had a look at the latest state of your package.json and can't see it added there either—you are still using eslint-find-rules—which is obviously totally fine—I just wanted to make you aware that eslint-index hasn't been added.
I would happily open a PR for you if that would be helpful?

@wagerfield there was a typo in the PR link.  Here's a working version: https://github.com/Shopify/eslint-plugin-shopify/pull/4.


CLI Test command should recognize block tags + plugins

Describe the bug
I am using the "Random Number" plugin in the Insomnia Designer. This tag is used in a few places in my unit test execution. When running the tests through the Insomnia Designer all my tests pass without a problem, but when I use the CLI to run the tests, I get a "Error: unknown block tag: randomnumber".
I am making use of the git sync feature and are running the cli tests from within the repo folder on my local machine. I also installed the plugin in this folder using npm i insomnia-plugin-randomnumber.
My test payload is as follow:
{
  "name": "User Name",
  "age": "{% randomnumber 10, 99, 0, 0 %}"
}

To Reproduce
Steps to reproduce the behavior:

In Insomnia designer -> Application -> Preferences - Plugins, install the "insomnia-plugin-randomnumber" package
In the "DEBUG" tab of the insomnia designer, create a new request that makes use of this plugin
In the "TEST" tab of the insomnia designer, create a simple "Returns 200" test
Using the inso CLI, run the newly created test and you will get the error:

Error: unknown block tag: randomnumber
      at C:\Users\{USERNAME}\AppData\Roaming\npm\node_modules\insomnia-inso\node_modules\insomnia-send-request\dist\index.js:6343:26
      at C:\Users\{USERNAME}\AppData\Roaming\npm\node_modules\insomnia-inso\node_modules\nunjucks\src\environment.js:39:5
      at RawTask.call (C:\Users\{USERNAME}\AppData\Roaming\npm\node_modules\insomnia-inso\node_modules\asap\asap.js:40:19)
      at flush (C:\Users\{USERNAME}\AppData\Roaming\npm\node_modules\insomnia-inso\node_modules\asap\raw.js:50:29)
      at processTicksAndRejections (internal/process/task_queues.js:76:11)

Expected behavior
When using insomnia plugins, the CLI should be able to utilise them in unit tests
Screenshots

Desktop (please complete the following information):

OS: Windows 10 Pro V1809 (Build: 17763.1339)
Installation Method: npm
CLI Version: 2.2.20
Node Version: 12.14.1

Thanks @Ruan20795, this is a valid use case and should be supported. This initial stage of the CLI does not play with plugins, so I've marked this as a feature request instead of a bug. We need to give some thought towards how to communicate plugin information through to the CLI. 👍

We are debating re-writing all automation to use inso, but we make heavy use of jwtCreate and have seen the error described here. Is this officially on the roadmap or is it still up in the air? Thanks!

@coladarci I'll put it as a future item on the roadmap for now, we do want it, it's definitely something we want to look at after our spaces functionality.

Any feedback on this?

Hi @Ruan20795, unfortunately not yet, as above it will likely come after the Spaces functionality.


Attribute basename of StaticRouter work a little strange

Version
"react-router": "^4.3.1"
"react-router-dom": "^4.3.1"
Test Case
https://codesandbox.io/s/n50pvx92v4
Steps to reproduce
Just open the Codesandbox case, inspect any Link component's <a> tag, check the href attribute.
Expected Behavior
when I use the basename as / on StaticRouter, just normally be the /, /topics, etc;
Actual Behavior
now, i got the // //topics;

https://github.com/ReactTraining/react-router/blob/017f692af74f5797c65d86265c063bc0ea829e13/packages/react-router/modules/StaticRouter.js#L16-L19
Problem is that "location.pathname" defaults to "/". Hence we get "//".

If your website's pages exist at the root, you do not need a basename. The basename represents a non-root segment at the beginning of the pathname component of a URL, a forward slash followed by the segment string (e.g. /base).

I use the BrowserRouter before, that's component set '/' as basename attributes is work, I mistakenly think that this is the expected behavior of your design. 😅
@pshrmn thanks for your reply.

@fimars the StaticRouter is a bit weird because it uses a fake history object. A real history ensures a basename has the correct format, which turns the basename / into an empty string.


Example app does not reflect what is hosted at https://srdjan.github.io/react-multistep/

How do I hide/show previous button based on step number?

can you show some screenshots?
If I understand the issue, once this story is complete:
https://github.com/srdjan/react-multistep/issues/110
it will be possible to "hide/show previous button based on step number"


Horizontal scroll bar doesn't work when using workspace setting

The horizontal scroll bar in Split view mode does not show up when turning off the editor.wordWrap on workspace setting.

After testing I was unable to repro this, will get a few other confirmations prior to closing.
Workspace settings will override user settings.


Missing code in the guide

In the "Components" part of the guide, at "Making a Carousel Component", the example code misses the definition of the Carousel type.
It reads:
type Carousel slide

Although it should be
type Carousel slide
    = Carousel (Internals slide)

I am pretty sure this is done on purpose since the code snippet only shows exposed values and signatures -- not the whole code.

I see your point, and I agree: something showing clearly the code is not complete would be less confusing.

Fair enough, I added a note above the code example to avoid confusion:


Bump release for sharp 0.33.3 dependency

4.0.0 release has a sharp dependency  of 0.32.6
https://github.com/donmccurdy/ndarray-pixels/blob/v4.0.0/package.json#L42
"dependencies": {
		"@types/ndarray": "^1.0.11",
		"ndarray": "^1.0.19",
		"ndarray-ops": "^1.2.2",
		"sharp": "^0.32.6"
	},

Sharp 0.33.0 had fix for deno support: https://github.com/denoland/deno/issues/20071#issuecomment-1836135194
Also, latest @gltf-transform/cli release also uses sharp 0.33.3
https://github.com/donmccurdy/glTF-Transform/blob/v4.0.0/packages/cli/package.json#L58
This should hopefully fix a bug when using npm:@gltf-transform/functions in deno.

Hi @FloridaKing! Thanks, I've just published v4.1 with an updated Sharp dependency.


Default PPR

Let's make the PPR default 1.0 actually. I think the users will benefit more from seeing that included data included with the images they are likely to use than to be confused by portions of their images missing.

Double checking that this is the Q minimum threshold?

Yes


Add Appveyor support

Add Appveyor support.
Add appveyor.yml.
Closes #15.

Coverage remained the same at 0.667% when pulling 2a361228a60821fafcdbefa1946f3202e2b4c577 on chore-add-appveyor-support into fc91adef0f5bcd42ed50089cfc279d5951a6d896 on master.

Coverage remained the same at 0.667% when pulling 8cad7d74bdb7f7469b654b4c490823c02d0d3a20 on chore-add-appveyor-support into fc91adef0f5bcd42ed50089cfc279d5951a6d896 on master.

Coverage remained the same at 0.667% when pulling 93cb57b86f7c243fe59a62c8cee14bdb3239c225 on chore-add-appveyor-support into fc91adef0f5bcd42ed50089cfc279d5951a6d896 on master.

Coverage remained the same at 0.667% when pulling c2ea37c675c879f14847ec893d2491560dd656cc on chore-add-appveyor-support into fc91adef0f5bcd42ed50089cfc279d5951a6d896 on master.

Coverage remained the same at 0.667% when pulling e5af3c100347f0d6d9202447a852ff53e724c8e6 on chore-add-appveyor-support into 4bd0be2d14dd6f649c3d9fd3a17ca9856abb2908 on master.

Coverage remained the same at 0.667% when pulling 1373026d7224285746a84b870b8968f5adb0af20 on chore-add-appveyor-support into 4bd0be2d14dd6f649c3d9fd3a17ca9856abb2908 on master.

Coverage remained the same at 0.667% when pulling e8e3b574db4b4aa26c09f1f7e214d1502d0eaefa on chore-add-appveyor-support into 4bd0be2d14dd6f649c3d9fd3a17ca9856abb2908 on master.

Coverage remained the same at 0.667% when pulling e4b194b9d7eb9b63d7b01b4776e3ba717a921af0 on chore-add-appveyor-support into 4bd0be2d14dd6f649c3d9fd3a17ca9856abb2908 on master.

Coverage remained the same at 0.667% when pulling d6038e9d30dd1de09386f46047b966faeb81fae7 on chore-add-appveyor-support into 4bd0be2d14dd6f649c3d9fd3a17ca9856abb2908 on master.


Quering variants on ranges returns 500 error on huge ranges

Describe the bug
There is an endpoint for quering for variants on specific position range.
E.x.
 https://reev.cubi.bihealth.org/internal/proxy/annonars/annos/range?genome_release=<>&chromosome=<>&start=<>&stop=<>

To Reproduce
Steps to reproduce the behavior:

Go to https://reev.cubi.bihealth.org/internal/proxy/annonars/annos/range?genome_release=grch37&chromosome=16&start=688105&stop=68869440
Or to https://reev.cubi.bihealth.org/internal/proxy/annonars/annos/range?genome_release=grch37&chromosome=10&start=89624226&stop=89725229
500 error will be returned

Expected behavior
A proper 400-series error should be returned without server crash
Screenshots
N/A
Additional context
N/A

Will be addressed by #502. In particular, your first query goes from/to
   688105
68869440

So it will query 68Gbp (!)
Your second one goes over 100kbp, still
89 624 226
89 725 229


[Bug]:

What happened?
I tried to use whisper large model v2 and v3 but both gives this message I have put
Steps to reproduce
1- I tried to remove the model and redownload
2- I tried to do the magic install and then reset when it didn't work'
3- actually the medium model works but when I change the gpu to 1 instead of 0 to use the nividia the app shutsdown
What OS are you seeing the problem on?
Window
Relevant log output
failed to open model

Caused by:
    Failed to create a new whisper context.

Location:
    core\src\transcribe.rs:37:65

https://github.com/thewh1teagle/vibe/issues/370


Issues with  config.container

Hi there,
I'm having issues with ng-scrollreveal, please see attached image of the issue
Using chrome dev tools with the view responsive (or just changing the browser window size), if I play around with the dimensions (height of the view/browser) it works, but  when I scroll, it does not work.

My dependencies and code:
@angular: ^4.0.0
"ng-scrollreveal": "^2.0.2",
app.component.ts
@NgModule({
  declarations: [

  ],
  imports: [
    NgsRevealModule.forRoot()
  ],
  providers: [],
  bootstrap: [AppComponent]
})
export class AppModule { }

app.component.html

..

..

..

..

..

..

Item 1

Item 2

Item 3

Item 4

Item 5 (will not be animated)

THANKS !

OK so I changed the title of the issue, it does animate and if angular 4 would be the issues, it would break or not animate or something else.. . .. I think my problem lies with setting the correct container settings.. . .
Some code on the AppComponent

export class AppComponent implements AfterViewInit {
  constructor(private config: NgsRevealConfig) {
    // customize default values of ng-scrollreveal directives used by this component tree
    //config.duration = 5000;

    config.easing = 'cubic-bezier(0.645, 0.045, 0.355, 1)';

    //config.container = document.querySelector('.xxx')

    console.log('config.container', this.config.container);
    console.log("document.querySelector('.html')", document.querySelector('html'));
    console.log('window.document.documentElement', window.document.documentElement);
    this.config.container = window.document.documentElement;

  }

duration and easing do work but, while trying to set the container ...
According to the config d.ts, container is of type HTMLElement
export declare class NgsRevealConfig {

    container?: HTMLElement;

According to the scrollreveal documentation on the default config settings (https://github.com/jlmakes/scrollreveal#2-configuration)
Doing this on the constructor of AppComponent
this.config.container = document.querySelector('xxx');
this.config.container = '.xxx'

Give mes a type error since Element is not assignable to container?: HTMLElement;

Hi @edoardoVD
Good catch about the type of container...
Even more complicated enough, it seems that the actual type returned by document.querySelector(selector) depends on the passed selector:
See here, a extract of lib.dom.d.ts file

Anyway, I will relax the type of container into : container?: Element|string  ,as it seems possible to set it to the selector as string as well.

thanks for looking intos this,
any idea how can I get it to work ?
Still no luck with my project : (

Just published v2.0.3,
Could you update your deps, then yarn upgrade (or rm -rf node_modules/ && npm install)?
Feel free to re-open if still having issues, and it look at it in more details.
Cheers,

@tinesoft , thanks for the super fast update on the package
So here's the current status:
Updated ngscrollreveal to 2.0.3
I'm not tempering in anyway with the configuration settings of scrollreveal
Still not working
Things to know:
I'm using a router outlet
this is how my page structure is

html
-- body
---  ng-component
----   div #testClass
-----    div item
-----   div item
-----   div item
my home.component.html has:
..
..
..
..
..
..

Hi @edoardoVD ,
I haven't looked closely enough yesterday (was getting late :) )
But the problem here, is that you have the  [ngsReveal] on each single item you want to animate
div class="item" [ngsReveal]="{ reset: true}" >..
div class="item" [ngsReveal]="{ reset: true}" >..
div class="item" [ngsReveal]="{ reset: true}" >..
div class="item" [ngsReveal]="{ reset: true}" >..
div class="item" [ngsReveal]="{ reset: true}" >..
div class="item" [ngsReveal]="{ reset: true}" >..

AND that those items are already in the viewport (i.e visible), so nothing happens, unless you resize the viewport.
 Element|string)


Added Feature_Engineering

Related Issue
Feature Engineering

[x] GSSOC'2024 Participant
[x] Contributor

Closes: #731
Describe the changes you've made
I have added Feature_Engineering.ipynb in the repository.
Type of change
What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[x] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly whereever it was hard to understand.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have added tests that prove my fix is effective or that my feature works.
[x] Any dependent changes have been merged and published in downstream modules.

Please consider adding a ReadMe.md file and creating a directory is recommended.

@invigorzz313 I created a separate branch and created a PR. Readme.md file is added. Please approve. Consider adding label tag to the Issue


Hive distributed parallel processing

Changelog category :

New Feature
resolve #220

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
...
Documentation entry for user-facing changes

[ ] Documentation is written (mandatory for new features)

Any performance data?


Error [ERR_MODULE_NOT_FOUND]

Describe the bug
in this case, import three/examples/jsm/controls/OrbitControls, vite build will find the ${path}/package.json, but it only export .js, I think that if we don't find ${path}/package.json, we can choose to find index.js or index.ts as another plan.
import { OrbitControls } from 'three/examples/jsm/controls/OrbitControls'

Reproduction
import { OrbitControls } from 'three/examples/jsm/controls/OrbitControls'
System Info
build

Used Package Manager
pnpm
Logs
import * as THREE from 'three'
import { OrbitControls } from 'three/examples/jsm/controls/OrbitControls'
import { GLTFLoader } from 'three/examples/jsm/loaders/GLTFLoader'
then
build
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I use vite-ssg to build the threejs project that has this error, then it's successful that I try to pure vite to build. The error may be caused by vite-ssg.  so temporarily turn off this issue


[bug] If pint is not installed, suggest user restarts ulauncher after install

Describe the bug
The message reminding the user to install pint does not also suggest that the user restarts ulauncher to get around the error, but it is necessary (at least is was for me).
To Reproduce
Steps to reproduce the behavior:

Install extension but do not install pint
Open ulauncher and type =
Notice a message saying something like "Install pint by running pip install pint"
Install pint by running pip install pint.
Open ulauncher and type =

Expected behavior
I expect newly installed pint to be recognized, since I followed the directions.
What happened instead

Got the same message saying "Install pint by running pip install pint"
Start fiddling with it to get it to work, which starts with restarting ulauncher process.
Notice that there is no more error message about pint

Logs
Sorry I don't have logs, please let me know if you actually need them for this.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information)

OS: [e.g. Ubuntu Linux 20.04 ]

Linux: If you don't know the version, these commands may help: cat /etc/os-release lsb_release -a hostnamectl

~ % uname --all
Linux m 6.0.12-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 08 Dec 2022 11:03:38 +0000 x86_64 GNU/Linux
~ % cat /etc/os-release
NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://bugs.archlinux.org/"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo
~ % lsb_release -a
LSB Version:    n/a
Distributor ID: Arch
Description:    Arch Linux
Release:        rolling
Codename:       n/a
~ % hostnamectl
Static hostname: m
Icon name: computer-laptop
Chassis: laptop 💻Machine ID: ac2d7008d3874e7292bcc4dfcb25d7d7
Boot ID: 17c682032a2147a88df688bb7d6b5fd7
Operating System: Arch Linux
Kernel: Linux 6.0.12-arch1-1
Architecture: x86-64
Hardware Vendor: Dell Inc.
Hardware Model: XPS 13 9300
Firmware Version: 1.15.0

Additional context
Add any other context about the problem here.

I'm seeing the same on Manjaro KDE. But although Python says the requirement is already satisfied, restarting ULauncher just shows the same message needing pint installed.

I'm seeing the same on Linux Mint 21.3 Cinnamon. Python requirements are installed like so:
$ pip install Pint simpleeval parsedatetime pytz
Defaulting to user installation because normal site-packages is not writeable
Requirement already satisfied: Pint in ./.local/lib/python3.10/site-packages (0.23)
Requirement already satisfied: simpleeval in ./.local/lib/python3.10/site-packages (0.9.13)
Requirement already satisfied: parsedatetime in ./.local/lib/python3.10/site-packages (2.6)
Requirement already satisfied: pytz in /usr/lib/python3/dist-packages (2022.1)
Requirement already satisfied: typing-extensions in /usr/lib/python3/dist-packages (from Pint) (<IP_ADDRESS>)

Re-launching Ulauncher doesn't help at all.

I've met this same problem on my Ubuntu 22.04.4 LTS
Everything looks like packet is yet installed but it somehow fails.
What i discovered is if I just run python interactive console i can import pint with no problem.
Finally what I discovered is that i had two installs of pint - one from pip install and one from apt.
I deleted pint that was from apt (as it was quite old and couldn't handle import Self from typing_extensions) and reinstalled or upgraded the one from pip.
And I now can use this plugin flawlessly.

How did you install the plugin?
Depending on your system and python version pip may refer to pip for python2 and pip for python 3. You may have installed pint for the wrong python version.
To make sure you use the proper one try using python3 -m pip install pint.
Let me know if this helps.

Didn't help.
/usr/bin/python3 -m pip install pint
Defaulting to user installation because normal site-packages is not writeable
Requirement already satisfied: pint in ./.local/lib/python3.10/site-packages (0.23)
Requirement already satisfied: typing-extensions in /usr/lib/python3/dist-packages (from pint) (<IP_ADDRESS>)

yeah i cant get it to work no matter what on linux mint too

Requirement already satisfied: pint in /usr/local/lib/python3.10/dist-packages (0.23)
Requirement already satisfied: typing-extensions in ./.local/lib/python3.10/site-packages (from pint) (4.11.0)

same as the guys above, wont detect pint at all

Not working on Mint... halp!

Could this be due to Ulauncher using a different Python version than your system? Did you install it via Flatpak or another way other than the .deb file?
I don't have Mint, but it looks like the Ulauncher you run possibly runs via a different Python interpreter that does not have Pint installed.

Ulauncher 5.15.7 system package for Ulauncher

Update: seems to have been fixed i ran ulauncher in dev and verbose debugging mode, turns out i needed to run the following command - pip install py_expression_eval

@runew0lf I have installed Mint on a VirtualBox machine and I have tried some things to figure out what is the problem.
So on a first note when I run
python3
import pint

I get the following error:

I am not sure how this issue came to be. It looks like it is an issue others face, as well as other projects. I updated the typing-extensions like this:
python3 -m pip install --upgrade typing-extensions

This allows pint to be imported, but it is still not working on Ulauncher. I then removed it and upgraded the system package (generally not recommended)
sudo python3 -m pip install --upgrade typing-extensions

I can still import it if I run Python3 from the terminal, but Ulauncher refuses to cooperate.
I will need some time to dig into what is happening here because Ulauncher probably messes up with the sys /usr/bin/launcher. If, in the meantime, you have any idea we can go forward with this, feel free to comment.

Linux Mint 21.3 Cinnamon
Ulauncher 5.15.7
Python 3.10.12
Same issue. No matter where or how pint is installed.


Added missing dependency pycurl

Adds the missing py-curl dependency for the Alpine image.
Closes https://github.com/DataDog/docker-dd-agent/issues/166

closing as explained on #166
Thanks for the contrib


FineTuning Model

First of all, great job on the project! I was wondering if there were any implemented functionality to finetune this model? Basically introducing another dataset to train on top of the already trained model.
Thanks in advance.

Hi, I am trying to train the model on my own dataset.
After training is complete, there is no colourisation happening whatsoever. Is anyone able to train this model well and would give me some insight? Such as amount of epochs, loss and dataset size?
Cheers!

Hi Dear friend,
If you use CPU test, not GPU, you will get gray result. Just set gpu_ids = "-1" in base_options.py. Do you test on CPU ? @steven0704


[Bug] Sankey breaks when there is a loop or a cycle

Version
5.4.3
Link to Minimal Reproduction
https://echarts.apache.org/examples/en/editor.html?c=sankey-itemstyle
Steps to Reproduce
go to https://echarts.apache.org/examples/en/editor.html?c=sankey-itemstyle
change data set so that one of the data items loops back to the first entry and the sankey breaks
Current Behavior
the sankey does not load
Expected Behavior
the sankey load and where the data loops back my expectation is there is a line that shows the flow going back to a previous node
Environment
- OS: mac
- Browser: chrome
- Framework: i'm just using the website https://echarts.apache.org/examples/en/editor.html?c=sankey-itemstyle

Any additional comments?
No response

Not a bug, it throws an error: Uncaught Error: Sankey is a DAG, the original data has cycle!. Sankys cannot contain cycles. Maybe a graph is more suitable for you are trying to achieve.

@MatthiasMert why can sankeys not contain cycles?
if visualizing money flow which is a good case, if you want the inflows and outflow so to be separate.


Can't connect to NBT anymore: "Crypto Operation Failed"

Hi there, since a few day, I can't connect the trader to NBT anymore.
I added a socket.on('connect_error', (e) => .... hook to see what's going on.
this is the error i got back:
NBT auto trader running.
Connection error Error: xhr poll error
    at XHR.Transport.onError (/home/joe/projects/trader/node-binance-trader/node_modules/engine.io-client/lib/transport.js:68:13)
    at Request.<anonymous> (/home/joe/projects/trader/node-binance-trader/node_modules/engine.io-client/lib/transports/polling-xhr.js:132:10)
    at Request.Emitter.emit (/home/joe/projects/trader/node-binance-trader/node_modules/component-emitter/index.js:145:20)
    at Request.onError (/home/joe/projects/trader/node-binance-trader/node_modules/engine.io-client/lib/transports/polling-xhr.js:314:8)
    at Timeout._onTimeout (/home/joe/projects/trader/node-binance-trader/node_modules/engine.io-client/lib/transports/polling-xhr.js:274:12)
    at listOnTimeout (node:internal/timers:556:17)
    at processTimers (node:internal/timers:499:7) {
  type: 'TransportError',
  description: Error: Unable to load PFX certificate
      at Object.createSecureContext (node:_tls_common:334:17)
      at Object.connect (node:_tls_wrap:1602:48)
      at Agent.createConnection (node:https:137:22)
      at Agent.createSocket (node:_http_agent:334:26)
      at Agent.addRequest (node:_http_agent:285:10)
      at new ClientRequest (node:_http_client:322:16)
      at Object.request (node:https:333:10)
      at Object.<anonymous> (/home/joe/projects/trader/node-binance-trader/node_modules/agent-base/patch-core.js:25:22)
      at /home/joe/projects/trader/node-binance-trader/node_modules/socks-proxy-agent/node_modules/agent-base/patch-core.js:23:20
      at XMLHttpRequest.send (/home/joe/projects/trader/node-binance-trader/node_modules/xmlhttprequest-ssl/lib/XMLHttpRequest.js:495:17) {
    code: 'ERR_CRYPTO_OPERATION_FAILED'
  }
}

Maybe the ssl cert elapsed or something?

Maybe the ssl cert elapsed or something?

I can connect on my Arch Linux, but not on my Debian buster 🤔

I can connect on my Arch Linux, but not on my Debian buster 🤔

Which Node / npm version are you using and what's your OS?

Which Node / npm version are you using and what's your OS?

This problem occurred to me when using Node 15. I'm now using Node 14 and the issue no longer persists.
Btw, I'm using Docker.

This problem occurred to me when using Node 15. I'm now using Node 14 and the issue no longer persists.
Btw, I'm using Docker.

Thanks, I also figured while working on your other request, that it works on my other machine. Both are arch though and I thought running with Node 14. Have to double check

Thanks, I also figured while working on your other request, that it works on my other machine. Both are arch though and I thought running with Node 14. Have to double check

I'm now using Node 14 and the issue no longer persists.

Yes, that did it!

I'm now using Node 14 and the issue no longer persists.

Yes, that did it!


Kover report tasks not cacheable

When running a simple project twice with build cache enabled, we can see that the Kover report task is skipped:

which leads to no report being generated nor taken from a cache.
The way I would expect it working would be:

First run stores the report into the build cache
Second run does not skip the report task, just takes the report from the cache

Thanks for the report!
Since the binary report file is not currently added to the output of the test task, if the test has the FROM-CACHE status, the binary report file is not restored and report generation is skipped.

I quickly checked it locally, you already have attached an extension to the test tasks so now it's just a matter of adding proper input/output annotations on KoverTaskExtension. Also in CoverageArgumentProvider don't forget also to define @Nested val taskExtension: KoverTaskExtension. You can take a look at the built-in jacoco plugin for a concrete example.

Fixed in 0.4.3


This looks delightful! [emscripten]

I love your README. At the risk of possibly polluting the aesthetic purity of your repo, I wanted to ask: would this be impossible to bring to browser via emscripten?
I should probably just try, and I know it’s not your purview necessarily, but just thought I’d ask in case you knew. Sorry I’m not an emscripten expert but I do love this Ui and your philosophy of how it should work, and I think it would be cool to be able to put it in a webpage.

This is excellent news @buserror, about your friend. Ah the internet, always working in secret in the background, always getting stuff done!
I totally get he is probably way too busy to bother putting it in a proper repo and that's completely fine. Just good to know it's done and works! And looking forward to if he does push it out! Thank you kindly for your reply.


Check Goobi's working storage and clear it out

In looking at our AWS bills, it may be that we have way too much stuff stored in Goobi's working storage.
I have suspected that since the migration our image cleanup steps may not be working correctly to clean this stuff up so that's why I've labeled it a bug.
Searching "stepinwork:Image removal" gives me 1100+ items that are in progress on this step and have been for months, for example.
Can we check and see what's in our working storage? How much stuff is in there?
Can we make sure the image removal steps are already working?
And we'll need to clear out anything that's finished beyond the DDS API call and has been for more than 90 days, as that's the usual time we'd save the working images.
Alex Chan is a good one to ask about this while I'm away.

I'll move this back in TODO
We should also check "stepopen:Image removal" and others

I've done some clearing out of Goobi's working storage this week. I removed ~10TB of ALTO files and JP2 images which I could match to content in the storage service (and thus was definitely redundant). For more details, see the individual tickets (https://github.com/wellcomecollection/platform/issues/5399, https://github.com/wellcomecollection/platform/issues/5404).
The next step to reducing costs is #423, which is quick and easy.
If somebody wanted to clean this up further, here's where I'd start:

Look at the JPEG images which appeared alongside JP2s. I found lots of processes that had both JPEG and JP2 images, but only the JP2 images were uploaded to the storage service. Because I couldn't match the JPEG images to the storage service, I didn't delete them on this pass, but they can probably be safely removed.
I'd do something like:

Get all the JPEG files in a given process ID prefix
Work out what the equivalent JP2 files would have been
If all of the equivalent JP2 files were deleted (see attached list for convenience), delete the JPEGs. Otherwise, do nothing.

Look at ALTO files which weren't a perfect match. I found some ALTO files which have a file with the same name in the storage service, but the version in Goobi working storage is much bigger. It looks like the ones in working storage are from ABBYY, whereas the ones in the storage service have been through Goobi. Something like:

Get all the ALTO files in a given process ID prefix
Look for objects with the same filenames in the storage service
If all of the ALTO files have an object with the same filename, delete the ALTOs. Otherwise, do nothing.

Look at gzip/zip bundles. This is an opportunity to make a cheap cleanup – some information is duplicated in compressed/uncompressed form, e.g. https://console.aws.amazon.com/s3/buckets/wellcomedigitalworkflow-workflow-data?region=eu-west-1&showversions=false&prefix=101377%2Fimages%2Fsource%2F

You can probably delete:

the uncompressed XML file – if it's equivalent to what's in the gzip
the compressed ZIP of JP2 files – if we deleted all the uncompressed JP2s already, see list below

Delete any objects whose filename starts with a '.', e.g. .DS_Store. There's a few thousand of them hanging around in the bucket. Enough to be worth deleting if you're already clearing up the bucket, but not worth tackling on their own.

deleted_jp2_keys.txt.gz

I did another pass of deletions last week, which has had a big effect on the size of the bucket:
3,513,501 objects deleted, total 6.9 TB, saving $80.5285 per month ($966.34 per year)

This was backfilling deletions that are applied to new Goobi processes, but haven’t been applied to stuff from 2021 and earlier:

Do we have a folder full of JP2s that are all in the storage service? Duplicates, bin.
Do we have a folder full of JPEGs that have similarly-named JP2s in the storage service? Duplicates, bin.
Do we have a folder with both a compressed and uncompressed copy of the JP2s or OCR data? Duplicates, bin.
Do we still have the jpylzer validation results? No long-term value, bin.


Prometheus exportere cant' find  port

Hi, I've enable prometheus plugin on a 2 node microk8s cluster and 2 pods are not running:
# kubectl get -n monitoring pods
NAME                                   READY   STATUS    RESTARTS   AGE
prometheus-k8s-0                       2/2     Running   0          174m
alertmanager-main-0                    2/2     Running   0          174m
node-exporter-bsk5d                    0/2     Pending   0          75m
node-exporter-vxtm7                    0/2     Pending   0          75m
prometheus-adapter-69b8496df6-xpwft    1/1     Running   1          175m
grafana-6b8df57c5b-67md6               1/1     Running   1          175m
prometheus-operator-7649c7454f-677tc   2/2     Running   2          175m
kube-state-metrics-78dc55b74b-xqpcg    3/3     Running   4          175m

kubectl describe shows event that complains:
kubectl describe -n monitoring pods node-exporter-bsk5d
...
Events:
  Type     Reason            Age   From               Message
  ----     ------            ----  ----               -------
  Warning  FailedScheduling  62m   default-scheduler  0/2 nodes are available: 1 node(s) didn't have free ports for the requested pod ports, 1 node(s) didn't match Pod's node affinity/selector.

Why should a port not be available?
I guess the 2 pods are on different nodes, but are not yet assigned to a node.
inspection-report-20210923_165259.tar.gz

The node exporter uses hostPort and hostNetwork 9100.
If your nodes already uses that port, then it will not be able to bind to that.

That was it. I had Traefik's metric listening on that port (installed via helm). Sorry for the noise.
May I just suggest you add the port number in the message, that would have been easier to spot.

The prometheus addon is taken from the upstream kube-prometheus.  I don't think microk8s can do anything with the messages.
Plus the error is detected by kubelet before starting the pod.


25 euro difference in refund manager for some orders

Some orders have a 25 euro difference between total order amount and refundable amount:

The data comes from the Mollie API, however I'm curious why this happens? :)

mollie allows to refund 25 EUR on top of the total amount for some payment methods...this can be used if a merchant wants to say "sorry" for instance :)
so that is just how it is with the Mollie API
here is the page to the api refs, where the totalAmount has a description on this
https://docs.mollie.com/reference/v2/refunds-api/create-payment-refund
i hope this helps :)

Thanks. Makes sense now :)


Support running Spring integration tests in instrumentation process

Description
Fixes #2357, #2220

Use TestContextManager when running tests
Make ValueConstructionPhase handle exceptions using standard mechanism of handling exceptions in ExecutionPhases
Make SpringUtExecutionInstrumentation only transform user sources

How to test
Manual tests
Generate integration tests for spring-boot-testing-main, spring-pet-clinic, and other Spring projects.
Self-check list

[x] I've set the proper labels for my PR (at least, for category and component).
[x] PR title and description are clear and intelligible.
[x] I've added enough comments to my code, particularly in hard-to-understand areas.
[ ] The functionality I've repaired, changed or added is covered with automated tests.
[x] Manual tests have been provided optionally.
[x] The documentation for the functionality I've been working on is up-to-date.

LGTM, requested some optional naming improvements personally.


[Bug] Can not enable Context Isolation

What did I do
~Using the template provided in this repository, I wanted to enable contextIsolation to seperate Main and Preload contexes.
I also, disabled the nodeIntegration.
Here's the code i've changed.~
False positive, I can not reproduce this problem on the provided template.
  win = new BrowserWindow({
    title: 'Main window',
    webPreferences: {
      preload: splash,
      contextIsolation: true,
    },
  })

note that nodeIntegration is disabled by default.
What happened
I got this error.
Uncaught ReferenceError: require is not defined
    at promises.js:2:11

which I assume that the vite-plugin-electron package is not handling this configuration and nodejs code is being leaked into browser context.
Expected
There should be no error when enabling contextIsolation.
Environment

OS: Ubuntu 22
electron-vue-vite  v2.0.0

@stalkercn 没人逼着你用，我这个项目太烂，不和你胃口

@caoxiemeihao 大佬那现在这个问题还是没法解决嘛没法开启嘛？我按照官网的文档操作也报这个错

大佬那现在这个问题还是没法解决嘛没法开启嘛？我按照官网的文档操作也报这个错
这不很简单的东西吗？你没发现是提 issue 的人自己关的 issue?


feat: support forking Ethereum testnets

What I did
Allows forking other Ethereum networks
Required this PR: https://github.com/ApeWorX/ape/pull/691
How I did it

Register the Fork provider for other Fork networks in Ethereum
Inject POA middleware if needed
Add tests for fork provider

How to verify it
You should now be able to fork rinkeby!
Example config:

ethereum:
  default_network: rinkeby-fork
  rinkeby:
    default_provider: alchemy
  rinkeby_fork:
    default_provider: hardhat

  mainnet:
    default_provider: alchemy

hardhat:
  fork:
    ethereum:
      rinkeby:
        upstream_provider: alchemy

      mainnet:
        upstream_provider: alchemy

Checklist

[ ] Passes all linting checks (pre-commit and CI jobs)
[ ] New test cases have been added and are passing
[ ] Documentation has been updated
[ ] PR title follows Conventional Commit standard (will be automatically included in the changelog)

Build failing because of the bug that is fixed by this PR https://github.com/ApeWorX/ape-hardhat/pull/59 which won't fully work until the next Ape is released

After this merges, I can open a PR that address a test