crash_report_database_win.cc under windows systeam

set NODE_ENV=dev&&electron-forge start

√ Checking your system
√ Locating Application
√ Preparing native dependencies
√ Launching Application
Sentry Logger [Log]: Integration installed: Dedupe
Sentry Logger [Log]: Integration installed: InboundFilters
Sentry Logger [Log]: Integration installed: FunctionToString
Sentry Logger [Log]: Integration installed: ExtraErrorData
Sentry Logger [Log]: Integration installed: Console
Sentry Logger [Log]: Integration installed: Http
Sentry Logger [Log]: Integration installed: OnUnhandledRejection
Sentry Logger [Log]: Integration installed: LinkedErrors
Sentry Logger [Log]: Integration installed: OnUncaughtException
Sentry Logger [Log]: Integration installed: Electron
[256612:247972:0817/114615.340:ERROR:crash_report_database_win.cc(469)] failed to stat report
[256612:247972:0817/114615.342:ERROR:crash_report_database_win.cc(469)] failed to stat report
[256612:247972:0817/114615.342:ERROR:crash_report_database_win.cc(469)] failed to stat report
[256612:247972:0817/114615.353:ERROR:crash_report_database_win.cc(469)] failed to stat report
[256612:247972:0817/114615.354:ERROR:crash_report_database_win.cc(469)] failed to stat report
[256612:247972:0817/114615.355:ERROR:crash_report_database_win.cc(469)] failed to stat report
[256612:247972:0817/114615.355:ERROR:crash_report_database_win.cc(469)] failed to stat report
[256612:247972:0817/114615.356:ERROR:crash_report_database_win.cc(469)] failed to stat report
[256612:247972:0817/114615.356:ERROR:crash_report_database_win.cc(469)] failed to stat report
[256612:247972:0817/114615.357:ERROR:crash_report_database_win.cc(469)] failed to stat report
[256612:247972:0817/114615.357:ERROR:crash_report_database_win.cc(469)] failed to stat report
[256612:247972:0817/114615.358:ERROR:crash_report_database_win.cc(469)] failed to stat report
[256612:247972:0817/114615.358:ERROR:crash_report_database_win.cc(469)] failed to stat report
[256612:247972:0817/114615.358:ERROR:crash_report_database_win.cc(469)] failed to stat report
[256612:247972:0817/114615.359:ERROR:crash_report_database_win.cc(469)] failed to stat report
[256612:247972:0817/114615.360:ERROR:crash_report_database_win.cc(469)] failed to stat report
[256612:247972:0817/114615.360:ERROR:crash_report_database_win.cc(469)] failed to stat report
[256612:247972:0817/114615.360:ERROR:crash_report_database_win.cc(469)] failed to stat report

When I run the application with forge under Windows system, found those logs if introduce with sentry.  (Doesn't happen in Mac)
init({
// TODO: Replace with your project's DSN
dsn: 'xxxx',
debug: true,
maxValueLength: 5000,
});
Also tried with
crashReporter.start({
companyName: 'xxx',
productName: 'xxx',
ignoreSystemCrashHandler: true,
submitURL: 'xxx',
});
But no difference.  Those crash log only disappear if I remove init sentry.
These are the  main module version:
"@sentry/electron": "^1.5.2",
"async": "^3.2.0",
"cron": "^1.8.2",
"electron-log": "^4.2.4",
"electron-squirrel-startup": "^1.0.0",
"electron-store": "^6.0.0",
"electron-updater": "^4.3.4",
"glob": "^7.1.6",
"moment": "^2.27.0",
"moment-timezone": "^0.5.31",
"node-abi": "^2.18.0",
"request": "^2.88.2"
"@electron-forge/cli": "^6.0.0-beta.44",
"@electron-forge/maker-deb": "^6.0.0-beta.44",
"@electron-forge/maker-rpm": "^6.0.0-beta.44",
"@electron-forge/maker-squirrel": "^6.0.0-beta.44",
"@electron-forge/maker-zip": "^6.0.0-beta.44",
"devtron": "^1.4.0",
"electron": "^9.2.0",
"electron-builder": "^22.8.0"

same problem with electron8.3.4
"@sentry/cli": "^1.56.1",
"@sentry/electron": "^2.0.0",

I can confirm the same happens with electron 9.2.0

I'm running into this issue while running Discord, which is built with Electron. Extremely annoying and impossible to debug.

I also encountered the electron 10.1.3 developed by discord.

Same problem here with Electron 9.0.0

me too

Me too with electron 9.1.0

Me too with electron 9.1.0

I believe this issue is due to a desync between report metadata and the reports themselves. For me, in %AppData/Roaming/Electron/Crashpad I see that the metadata file gets larger when crashes happens, and a report is placed in %AppData/Roaming/Electron/Crashpad/reports. I think this is then uploaded by Sentry, but the metadata remains, so the next time it runs it will look for those missing reports and log this error when it doesn't find them.
As a local fix you can delete the metadata file.

I believe this issue is due to a desync between report metadata and the reports themselves. For me, in %AppData/Roaming/Electron/Crashpad I see that the metadata file gets larger when crashes happens, and a report is placed in %AppData/Roaming/Electron/Crashpad/reports. I think this is then uploaded by Sentry, but the metadata remains, so the next time it runs it will look for those missing reports and log this error when it doesn't find them.
As a local fix you can delete the metadata file.

@bowswung after delete metadata, it works.
Thank you!

Looks like we might need to delete the metadata file when manually uploading minidumps.


Constant-memory implementation of common threshold-varying metrics

Thanks to the developers for their great work. I (and my work) use this package heavily and will continue to do so :).
🚀 Feature
Related to #128, it would be great to also have constant-memory implementations of the ROC curve and the AUC metric. Given that this has already been implemented for precision-recall, the work is 90% done, it just needs a minor extension.
Motivation
The current implementation of AUROC consumes a lot of memory.
Pitch
I am happy to submit a PR for this (together with help from @norrishd, @ronrest, @BlakeJC94, & @ryanmseer), and would propose to do it by:

Using some logic similar to what is in BinnedPrecisionRecallCurve right now, write a more general base class that implements a "confusion matrix curve", where each of the TP, TN, FP, FN are calculated for a set of defined threshold values. An argument to the parent class could allow child classes to specify a subset of these 4 values to prevent unnecessary calculation. The base class could be called something like ConfusionMatrixCurve, StatScoresCurve, or BinnedStatScores (preferences welcome).
Simplify BinnedPrecisionRecallCurve by inheriting from this base class.
Implement a constant memory version of the ROC called BinnedROC that inherits from the base class.
Similarly, we could also add constant memory implementations of things like BinnedAUROC, and BinnedSpecificityAtFixedSensitivity.

I've implemented similar functionality in a different metrics package here, but for this implementation I would of course follow the patterns and conventions of torchmetrics as best as I could.
Alternatives

I'm currently struggling with AUROC's memory footprint, so this would honestly be amazing!

Hi @timesler,
This sounds like a great addition to torchmetrics. We are aware that some of our implementations suffer from a potential huge memory footprint, so this would be a great to have metrics that solves this.
Please feel free to send a PR :]
One small question: would it make sense to combine binned and non-binned metrics into a single metric with a parameter to change between them e.g.
class AUROC(Metric):
    def __init__(self, reduce_memory=True/False):
        self.reduce_memory = reduce_memory
        ...

    def update(self, ...):
        if self.reduce_memory:
            binned_update(...)
        else:
            current_update(...)

instead of having multiple of the same metric?

I'm beginning some exploratory work on this feature now in consultation with @timesler .

We're still working on this.

Issue will be fixed by classification refactor: see this issue https://github.com/Lightning-AI/metrics/issues/1001 and this PR https://github.com/Lightning-AI/metrics/pull/1195 for all changes
Small recap: This issue ask for constant memory implementations of common metrics like roc ect. After the refactor, metrics such as roc, auroc, precision_recall, average_precision all now supports constant memory implementations by providing the thresholds argument. If thresholds=None the standard approach is used (which is accurate but not memory constant) and if thresholds=10 (int) or thresholds=[0.1, 0.3, 0.5, 0.7] (list of floats) an binned version will be used that is less accuracy but memory constant. Example below for roc:
from torchmetrics.functional import binary_roc
import torch

preds = torch.rand(20)
target = torch.randint(0, 2, (20,))

binary_roc(preds, target, thresholds=None)  # accurate and memory intensive
# (tensor([0.0000, 0.1667, 0.3333, 0.3333, 0.3333, 0.3333, 0.5000, 0.6667, 0.6667,
#         0.6667, 0.6667, 0.8333, 0.8333, 0.8333, 1.0000, 1.0000, 1.0000, 1.0000,
#         1.0000, 1.0000, 1.0000]),
# tensor([0.0000, 0.0000, 0.0000, 0.0714, 0.1429, 0.2143, 0.2143, 0.2143, 0.2857,
#         0.3571, 0.4286, 0.4286, 0.5000, 0.5714, 0.5714, 0.6429, 0.7143, 0.7857,
#         0.8571, 0.9286, 1.0000]),
# tensor([1.0000, 0.9995, 0.8895, 0.8621, 0.8426, 0.8204, 0.8044, 0.7560, 0.7169,
#         0.7023, 0.6685, 0.6194, 0.5599, 0.5071, 0.4728, 0.4574, 0.4332, 0.2989,
#         0.2535, 0.2446, 0.2025]))
binary_roc(preds, target, thresholds=10)   # less accuracy and memory constant
# (tensor([0.0000, 0.3333, 0.5000, 0.6667, 0.8333, 1.0000, 1.0000, 1.0000, 1.0000,
#         1.0000]),
#  tensor([0.0000, 0.0000, 0.2143, 0.4286, 0.5000, 0.6429, 0.7143, 0.9286, 1.0000,
#         1.0000]),
# tensor([1.0000, 0.8889, 0.7778, 0.6667, 0.5556, 0.4444, 0.3333, 0.2222, 0.1111,
#         0.0000]))

Issue will be closed when https://github.com/Lightning-AI/metrics/pull/1195 is merged.


Log in - The Fab menu does not open automatically when log in with new account

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Navigate to https://staging.new.expensify.com/
In the email field, enter a gmail email address for a new account.
Press continue
Verify there’s a message saying that a Magic Link has been sent to the email address
Navigate to the email inbox of the account and open the validation email
Copy the link and change it to staging.
Navigate to the staging link
Verify you’re brought to the “Set a Password” page
Set a password that follows the password requirements
After setting the password, verify the user is navigated to the main screen and Fub menu is open automatically

Expected Result:
The Fab menu opens automatically when log in with new account
Actual Results:##
The Fab menu does not open automatically when log in with new account
Workaround:
Unknkown
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers): any new account
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/93399543/182617042-c26a6bf4-cd10-4b7a-9350-bfcf19a47789.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub

We are working on revamping this flow with the refactors, will revisit after those changes go out 🤔

@kbecciv Hello! Just doing some GH clean-up and wanted to see if this issue was still occurring? If so, let me know and I can continue troubleshooting from a Triage perspective. Thanks!

Sorry @tylerkaraszewski! Was in the wrong GH tab — PLEASE IGNORE!

@CortneyOfstad Issue is still reproduced in build <IP_ADDRESS>
https://user-images.githubusercontent.com/93399543/196537185-1d86a655-a569-4603-ab81-cc3f71903136.mp4

I can reproduce in staging! The weird thing is, when I searched through lots & data returned by OpenApp I saw "isFirstTimeExpensifyUser": "true" - I wonder if the problem is that there's just soooo much data coming back in that command?
cc @luacmartins I wonder if you have an idea what's going on here since you've worked a lot on OpenApp I think?

Marking Internal b/c this could definitely be related to our API side code

@Beamanator I did some quick debugging and the issue is that we no longer set the IS_LOADING_POLICY_DATA key in OpenApp, so this promise never resolves and we don't show the FAB menu. We have a PR that should fix this

I'll assign myself them and keep track of the related PR.

Aah nice thanks for the link @luacmartins 👍

@Beamanator the App PR was merged, but I noticed that Auth can return 0 or 1 instead of a bool, which makes the first part of this conditional fail. So I put up a fix here.

Given that both the linked PR that put this issue on hold is now on staging, and related, so is the PR fix mentioned immediately above, let's take this issue off hold, right?

I'm going to go ahead and do that @Beamanator and @luacmartins, and at that point we're just waiting for both PRs to hit production for this issue to close. Yeah?

@JmillsExpensify that's correct!

Awesome thank you!

Both PRs are in prod. Closing this issue, please reopen if needed!


On 'realistic' difficulty manned pods can effectively turn using SAS

The SAS selector to point in a particular direction basically works, albeit in a labored manner, for manned craft even ones that are not particularly light weight.
This definitely happens earlier in missions. I sometimes notice it going away later in missions, but it may be due to the docking-disables-your-reaction-wheels issue. https://github.com/gotmachine/MandatoryRCS/issues/7

Should be fixed in 1.6


Polish MicroProfile custom config source backed by Azure KeyVault Secrets using latest apis

Summary
The PR includes:

Rewrite using latest APIs

MicroProfile 6.0 / Config 3.0.2
Azure Java SDK 1.2.14 / azure-security-keyvault-secrets 4.6.3

Support two options for managing the lifecycle of retrieved keyvault secrets in local: Cached or non-cache
Use DefaultAzureCredential for authentication, which implements the requirement in #1
Unit tests
Restructure the project with a BOM for dependencies management
Enable dependabot version updates

Next
The followings are not included in the PR but will be included in the next one:

Sample apps (Open Liberty and Quarkus) for integration test
Add/update readme
Add javadoc
Pipeline for build and release

Signed-off-by: Jianguo Ma<EMAIL_ADDRESS>

Another benefit of my suggested topic branch naming approach is the use of these two aliases.
alias gitstat="git status > changebundle.txt"
alias gitpush="git add --all; git commit -s -n -F changebundle.txt; git push"

If your topic branch is named appropriately, then the first line of your commit log message will always be the branch name, which describes the topic, and your commit/push workflow is.
Ensure your global gitingore excludes changebundle.txt. Ensure your repo .gitignore is sufficiently powerful.

gitstat
edit changebundle.txt
gitpush

Please rework this PR to make it so the artifact serving as the parent POM is in its own maven module

@edburns Fixed in 4731b06.

@backwind1233 FYI - similar to https://github.com/quarkiverse/quarkus-azure-services/pull/142#discussion_r1275949397, I also verified that the application id az-mp-kv-secrets is displayed as part of User Agent in log when enabling Azure Java SDK logging:
{"az.sdk.message":"HTTP request","method":"GET","url":"https://mpkv071923.vault.azure.net/secrets?maxresults=REDACTED&api-version=7.4","tryCount":"1","Authorization":"REDACTED","Content-Length":"0","Content-Type":"application/json","accept-language":"REDACTED","User-Agent":"az-mp-kv-secrets azsdk-java-azure-security-keyvault-secrets/4.6.3 (17.0.7; Linux; <IP_ADDRESS>-microsoft-standard-WSL2)","contentLength":0}

Do you think we need a Separator here?
like az-mp-kv-secrets;azsdk-...

nsure your repo .gitignore is sufficiently powerful.

Hello @edburns , could you explain more about Ensure your repo .gitignore is sufficiently powerful.?
What do you mean by this, sufficiently powerful?
Isn't it enough to just add the changebundle.txt to the ignore file?

@majguo Do you think we need a Separator here? like az-mp-kv-secrets;azsdk-...

@backwind1233 We only set application id here and it's Azure Java SDK's responsibility to produce the final string for User Agent. Let's just keep it as for now, and do enhancement if required in the future when we work on BI.

Another benefit of my suggested topic branch naming approach is the use of these two aliases.
alias gitstat="git status > changebundle.txt"
alias gitpush="git add --all; git commit -s -n -F changebundle.txt; git push"

If your topic branch is named appropriately, then the first line of your commit log message will always be the branch name, which describes the topic, and your commit/push workflow is.
Ensure your global gitingore excludes changebundle.txt. Ensure your repo .gitignore is sufficiently powerful.

gitstat
edit changebundle.txt
gitpush

I created a new alias:

alias gitsnap="git add --all;git status > changebundle.txt;vim changebundle.txt;git commit -s -n -F changebundle.txt;"

and updated the gitstat="git status > changebundle.txt;vim changebundle.txt"

@backwind1233 wrote:

Hello @edburns , could you explain more about Ensure your repo .gitignore is sufficiently powerful.? What do you mean by this, sufficiently powerful?

I mean that if your personal process is as I described, the gitpush alias includes git add --all.  Therefore, you need a .gitignore that is powerful enough so that no files are accidentally swept up by the git add --all. For example, let's say you decided to convert the codebase to use NodeJS in some way. This will cause a node_modules directory to appear. Generally, one never wants to commit such folders to Git. Therefore, if you're adding NodeJS to a thing, you need to make sure the node_modules never gets added.
For completeness, the section on global ignores in the github docs is worth a re-read.


consolidate the analysis of the German copula in the complex-predicates chapter

The data suggests that the copula has to enter coherent constructions, but the LIGHT value of the copula is not defined (it cannot be since NPs and PPs are permitted as well) and the LIGHT value of the head cluster schema is not defined either. In the copula paper it was LEX+. But in the German Clause Structure book it is not defined.

JBK:

As for the rule, since the head verb (aux) requires to select a LIGHT expression, I don't think we need to say the non-head to be [LIGHT +]. As you said, it is redundant.

Stefan: For German it is needed since the copula does not select LEX+. So the schema has to decide. Maybe.


Support FIPS 140 validated crypto module(s)

Is your feature request related to a problem?
FIPS (Federal Information Processing Standards) requires that any cryptographic functions (e.g. hashing) utilize cryptographic modules validated and listed by NIST under https://csrc.nist.gov/projects/cryptographic-module-validation-program/validated-modules/search/all
What solution do you propose?

The crypto provider (https://pkg.go.dev/crypto) must offer this feature.  Working with this provider to determine what compilation/import flags (if any) are required to explicitly leverage FIPS validated modules is therefore the first step.
Depending on whether a variant build/flag of https://pkg.go.dev/crypto is required, CLI/tool vendors may support a command line flag such as --fips-mode true which engages the appropriate version of https://pkg.go.dev/crypto.  However if the providers of https://pkg.go.dev/crypto can attest that their library is fully FIPS 140 validated and can supply the https://csrc.nist.gov/projects/cryptographic-module-validation-program/validated-modules/search/all Certificate #, then no such flag is required.

What alternatives have you considered?
Utilize an OpenSSL go library that utilizes FIPS validated modules, or build OpenSSL for go using a version of OpenSSL that is FIPS validated (3.0.9 as of this writing) https://www.openssl.org/source/

Any additional context?
The following Cloud Service Providers reference the Notary Project as their recommended method for signing containers.  Any US Federal customer of these providers must therefore meet the FIPS compliance requirement described above.

https://learn.microsoft.com/en-us/azure/container-registry/container-registry-tutorial-sign-build-push
https://docs.aws.amazon.com/AmazonECR/latest/userguide/image-signing.html

Per the discussion in the meeting 3/12/2024, set the milestone to 1.3.0

@gponto could you clarify the requirement on Notary Project. Based on your description, it is not clear on what Notary Project need to do regarding FIPS support.


Consider adding the firearm proficiency optional rules

Originally in GitLab by @sharkbruhaha
There are no firearms showing in the Weapon Proficiency section:

(tagging for tracking after move to github)


Specify path to backup configuration

Include, exclude and password files should be kept out of the repository directory, rather than relying on .gitignore.
Add -c option for configuration directory and -r for repository. Both must be specified otherwise kill the script.

Not sure this is worthwhile, and given the issue has been open for over 3 years it's not bugged me enough to fix.


CIAtah version 4.0

Major version incremented due to large change in organization of many CIAtah/ciapkg functions and thus the underlying API.
All CIAtah functions have been moved to +ciapkg folder so they are part of the ciapkg package or sub-packages. The ciapkg folder has been removed.
All relevant CIAtah functions can now be called via ciapkg.api.FUNCTION_NAME, which allows for a central location to call all functions as well as allowing importing of relevant CIAtah functions into a function if want to reduce visual clutter. Full function can be found in respective +ciapkg sub-packages.
Move Turboreg to _external_programs.
Updated to handle CIAtah v4.0 switch to all functions inside ciapkg package.
This leads to current support being MATLAB 2019b or later due to function of nested packages.

Tested on MATLAB 2020a on Windows 10. Merging. Additional updates soon.


I have added one open source competition

Please check past pull requested related to this, great if you could add this to competitions.


can't use existing deployed contract address from truffle on  ganache ui ?

as per this raised issue (https://github.com/EthWorks/useDApp/issues/440)
i replaced contract address inside
    multicallAddresses: {         // "1337": contractAddress,         "1337": "0xa5D4496a792Ab98c70f09bE4d3CFABb6fbeD9aA9",     },
the issue is when I replace this contract address from useDapp's created contract address no error is there.
but when I replace this contract address with truffle deployed contract
then I am getting this error
code: -32603 data: {message: 'VM Exception while processing transaction: revert', code: -32000, data: {…}} message: "Internal JSON-RPC error."
I am new to web 3 and wanted to try out this package.
have explored ethersjs and web3js why useDapp not directly connecting with metamask ?  like ehtersjs .

Did you deploy correct multicall contract?
There are 2 versions:)


Implement Scandinavian string encoding

IFC uses ISO 8859-1.
The Swedish Wikipedia article  has some good instructions.
Example: Ytterv\X2\00E4\X0\gg should be Yttervägg

A dirty workaround is to hard code the Scandinavian characters for now... :)
myString = "Ytterv\X2\00E4\X0\gg"
myUTF8string = myString.replace("/\\X2\\00E4\\X0\\/g, "ä")


Non Websocket Example

Is there the ability to use a simple 'send file' instead of exclusively using Websockets?
Could an example be provided for that as well?

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

ID: 86146e0d-6995-048c-f0bc-bdafcdde375e
Version Independent ID: 84b5da8a-fd5e-60a5-dfc5-58070d6d1a2e
Content: C# Quickstart for Azure Cognitive Services, Microsoft Translator Speech API
Content Source: articles/cognitive-services/translator-speech/quickstarts/csharp.md
Service: cognitive-services
GitHub Login: @v-jaswel
Microsoft Alias: v-jaswel

@JonathanPalmerGD Thank you for you feedback, I have assigned the author to help here.
@v-jaswel Hi Jason, this is a doc-enhancement idea about 'Websockets', can you please check it and update the document as necessary? Thanks a lot!

@nitinme FYI

Hello @JonathanPalmerGD, I'm afraid I am not aware of any other way to send a file to the service. As it happens, I am currently having trouble getting this same quickstart to work (though it worked for me previously), and I'm about to send some questions to the Translator Speech team. I will include your question as well and let you know what I find out from them.


Missing LICENSE

This plugin doesn't have a license of any kind, so technically no one can use it.
You can choose to add one to your repo using this website.

I don't care, but if you need it...
86b08fc


Hilite issues after selecting a class grouping node with many grouped instances

Repro:

Open https://qa-connect-imodelweb.bentley.com/imodeljs/?projectId=684860b3-e9bc-47cb-82fc-c243178000fa&iModelId=c47d8e40-6890-4dfb-b390-27e5bd933c93&ChangeSetId=9f570e69ab6278e61736d15ff91383d191959b44.
Open "Search" widget.
Enter "cell" in the search, wait for search to complete.
Select the "Physical Object" class grouping node.

### Issues:
- [x] It takes a long time to hilite the grouped elements. Investigate why.
- [ ] The requests to get the grouped elements are being sent even after the class grouping node is deselected. Could we cancel that if selection changes during the process?
- [x] The class grouping node says it's grouping 42552 elements. However, the `getPagedContent` and `getPagedContentSet` requests think there are 1000341 items in the content set. Needs investigation.
- [ ] Hilite fails if the hilite set has more than 65536 items (see image below). Need to avoid this.

When loading content item for hilite set we traverse ElementOwnsChildElements relationship recursively and that results in 1000341 elements when selecting that specific class grouping node.

It takes a long time to hilite the grouped elements. Investigate why.

Performance improved with https://github.com/iTwin/imodel-native/pull/550.

Hilite fails if the hilite set has more than 65536 items (see image below). Need to avoid this.

Fixed with https://github.com/iTwin/itwinjs-core/pull/6221

The requests to get the grouped elements are being sent even after the class grouping node is deselected. Could we cancel that if selection changes during the process?

Part of the fix change is in https://github.com/iTwin/itwinjs-core/pull/6221. When that gets released, a change in @itwin/presentation-components will be needed to stop loading hilite set upon unified selection change. That feature will be included in the 5.0 major release.


Let sourcemaps be cached

This change allows source-map-support to use the default value for emptyCacheBetweenOperations (false) to improve the performance of ts-jest.
Thanks to @hermanbanken for pointing out this issue in #259

Do we need to test jest multiple times in sequence to ensure this doesn't break e.g. --watch?

Do we need to test jest multiple times in sequence to ensure this doesn't break e.g. --watch?

Sounds like a good idea. I'm not yet sure how to automate that though

I'm not sure about that either.
Just to be clear - did you pull this branch into a regular project and test it, or how did you test it?

I'm not sure about that either.

I just updated my comment above. We're already testing this.

Just to be clear - did you pull this branch into a regular project and test it, or how did you test it?

I used the project linked from #259 to test this by changing the file in the ts-jest source in node_modules

Damn, past us are smart people..!
Let's merge this baby in.


What's the use of DefaultRoute

use ES6  webpack

We call it IndexRoute in 1.0.0-rc1
See the docs for more info and examples.


Create and document workflow of making changes to the database schema

Design and document how to modify database schema, its versioning and how the database migrations are applied to live environments.

[ ] Discuss whether to use FlaskMigrations dependency to manage database migrations

We're just winging it for now by dropping the database on each deployment. Nothing could possibly go wrong.


Cannot use Custom error type in the stream

Description:
I have a custom error type as defined below, and I wanted to use that as the stream error type, but I get an error  as below.
 stream<record{}, Error> errorStream = new (resultIterator);

Compilation error:
Exception in thread "main" org.ballerinalang.compiler.BLangCompilerException: Compilation failed with 1 error(s) and 0 warning(s)
  ERROR: ballerina/sql::client.bal:92:43:: type '(ballerina/sql:DatabaseError|ballerina/sql:ApplicationError)' not allowed here; expected an 'error' or a subtype of 'error'.
        at org.ballerinalang.stdlib.utils.GenerateBalo.genBalo(GenerateBalo.java:123)
        at org.ballerinalang.stdlib.utils.GenerateBalo.main(GenerateBalo.java:77)

Definition of the custom error type:
public type DatabaseError error<DATABASE_ERROR_REASON, DatabaseErrorData>;

# Represents an error originating from application-level causes.
public type ApplicationError error<APPLICATION_ERROR_REASON, ApplicationErrorData>;

# Represents a database or application level error returned from JDBC client remote functions.
public type Error DatabaseError | ApplicationError;

Fixed with https://github.com/ballerina-platform/ballerina-lang/pull/21524 ...


Enhance Tab Arrangement Animation for a Polished User Experience

Currently, the tab arrangement animation in VSCode is functional but lacks a smooth and visually pleasing transition similar to browser tabs. This enhancement aims to introduce a more elegant and fluid animation, providing users with a refined and enjoyable experience when managing their workspace. This could include smoother transitions between tab positions and a visually appealing easing effect. Let's elevate the user interface by incorporating a touch of sophistication into the tab arrangement animation.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


fix: add fluid system collider for bullet

@4Denthusiast can you verify if this is correct. The fluid is a separate colliding objects to check against.
https://github.com/Terasology/Fluid/pull/21

This PR is superseded by https://github.com/MovingBlocks/Terasology/pull/4221, and is no longer needed.


[tool_crash] FileSystemException: Cannot create file, OS Error: The system cannot find the path specified., errno = 3

Command
flutter pub get

Steps to Reproduce

...
...
...

Logs
FileSystemException: Cannot create file, OS Error: The system cannot find the path specified.
, errno = 3
#0      _File.throwIfError (dart:io/file_impl.dart:635:7)
#1      _File.createSync (dart:io/file_impl.dart:273:5)
#2      ForwardingFile.createSync (package:file/src/forwarding/forwarding_file.dart:24:16)
#3      ForwardingFile.createSync (package:file/src/forwarding/forwarding_file.dart:24:16)
#4      _renderTemplateToFile (package:flutter_tools/src/plugins.dart:26:8)
#5      _writeAndroidPluginRegistrant (package:flutter_tools/src/plugins.dart:677:3)
#6      injectPlugins (package:flutter_tools/src/plugins.dart:1165:11)
<asynchronous suspension>
#7      FlutterProject.ensureReadyForPlatformSpecificTooling (package:flutter_tools/src/project.dart:264:11)
<asynchronous suspension>
#8      PackagesGetCommand.runCommand (package:flutter_tools/src/commands/packages.dart:152:23)
<asynchronous suspension>
#9      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:977:18)
#10     _rootRunUnary (dart:async/zone.dart:1198:47)
#11     _CustomZone.runUnary (dart:async/zone.dart:1100:19)
#12     _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
#13     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
#14     Future._propagateToListeners (dart:async/future_impl.dart:725:32)
#15     Future._completeWithValue (dart:async/future_impl.dart:529:5)
#16     Future._asyncCompleteWithValue.<anonymous closure> (dart:async/future_impl.dart:567:7)
#17     _rootRun (dart:async/zone.dart:1190:13)
#18     _CustomZone.run (dart:async/zone.dart:1093:19)
#19     _CustomZone.runGuarded (dart:async/zone.dart:997:7)
#20     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:1037:23)
#21     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)

[✓] Flutter (Channel stable, 1.22.3, on Microsoft Windows [Version 10.0.19042.928], locale en-US)
    • Flutter version 1.22.3 at C:\flutter
    • Framework revision 8874f21e79 (7 months ago), 2020-10-29 14:14:35 -0700
    • Engine revision a1440ca392
    • Dart version 2.10.3

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at C:\Users\ANABATA\AppData\Local\Android\Sdk
    • Platform android-30, build-tools 30.0.2
    • ANDROID_HOME = C:\Users\ANABATA\AppData\Local\Android\Sdk
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[✓] Android Studio (version 4.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin installed
    • Dart plugin version 193.7547
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[✓] VS Code (version 1.56.2)
    • VS Code at C:\Users\ANABATA\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.22.0

[✓] Connected device (1 available)
    • Android SDK built for x86 (mobile) • emulator-5554 • android-x86 • Android 8.0.0 (API 26) (emulator)

• No issues found!

Flutter Application Metadata
Type: app
Version: 1.0.0+1
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version: 0b8abb4724aa590dd0f429683339b1e045a1594d
Plugins
flutter_paystack-1.0.3+1
shared_preferences-0.5.6+3
shared_preferences_macos-0.0.1+6
shared_preferences_web-0.1.2+4
stripe_payment-1.0.6

me too. and also can not run to build ios app.

Flutter version 1.22.3 at C:\flutter

@ariffmma
can you run flutter upgrade -f

@ariffmma
Apart from above suggestion, this issue was fixed and may be only available on master per this comment. So run below commands and see if it resolves your issue.
flutter channel master
flutter upgrade
flutter pub get

I am going ahead and closing this as already fixed in master. If you still see the issue on latest master, write in comments and I'll reopen it.


[Archives of the Empire: Vol 1.] Cannot roll for career when Archives module is activated

Rolling for a career in the character generation process works as expected with Core Content module + any of the premium content modules, apart from Archives 1. No other modules are set up / installed when the folowing error is returned in console:
tables-wfrp4e.js:114 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'length')
at Function._inRange (tables-wfrp4e.js:114)
at Function._lookup (tables-wfrp4e.js:99)
at Function.rollTable (tables-wfrp4e.js:74)
at GeneratorWfrp4e.rollCareer (char-gen.js:206)
at Function._onCharGenButtonClick (chat-wfrp4e.js:303)
at HTMLElement.dispatch (jquery.min.js:2)
at HTMLElement.v.handle (jquery.min.js:2)From: Jagusti#3610wfrp4e: 4.2.1wfrp4e-archives1: 2.1.1wfrp4e-core: 2.1.2

I still get this on a brand new world running WFRP4e 4.3.0 on FVTT 0.8.9 and only the Core 2.2.0 and Archives 2.2.0 modules activated and initialised.

In a different environment with WFRP4e 4.3.0 on FVTT 0.8.9 and only the Core 2.2.0 module activated, I get this. If I try and run character creation when this error appears, I get the same error as above when rolling for career.

Cold this be related to changes introduced in 4.1.0? I don't remember running chargen after upgrading to 4.1.0 until recently, so not really sure when the error started appearing.

Yeah so that change would probably cause those errors, but I have no idea why you wouldn't have the updated tables. Does your career.json table define multi instead of columns?

It does define multi, right at the end after the rows. Makes no difference if I move it up the file of course. (I've added the .txt extension to the attached to post here, otherwise it's the same file as in the module.)
career.json.txt

Turns out this error only appears when selecting Default as the Subspecies for a Human to generate attributes and then selecting a career. If I choose Reiklander (or Middenlander, etc) it kicks out a career as expected.  If I select Default for another race, that also gives a career as expected.


Adjusted runLocally to throw ProcessFailedException in case of error

Q
A

Bug fix?
No

New feature?
Yes

BC breaks?
No

Deprecations?
No

Fixed tickets
N/A

Replaced the \RuntimeException in runLocally with Symfony's Symfony\Component\Process\Exception\ProcessFailedException which has more information on the command that failed (including command line and error output).
The ProcessFailedException extends the \RuntimeException so there shouldn't be a BC problem.

Cool, thanks!


Support array transition configs

Motivation:
In SCXML document order matters, so i.e.
        <transition target="pass" event="*"/>
        <transition target="fail" event="foo"/>

and
        <transition target="fail" event="foo"/>
        <transition target="pass" event="*"/>

are not equivalent. When sending foo event it has to be matched according to that document order.
TODO:

[ ] review
[x] add new tests (existing ones are passing 🎉 )
[ ] cleanup TransitionConfig type drama (at different places it's intersected with {event: TEvent["type"]} or { event?: undefined }
[x] consider caching possible candidates, right now every event is iterating through whole list each time
[x] cleanup delays-related stuff (those with TODO comments)
[ ] look into few anys used in this PR, try to fix them
[x] for object configs put * at the end

Also, a thing to consider - after some thinking it seems that we might want to special-case * when converting from object config to array definitions (latter are later processed in order) and put them at the end of those definitions. So basically when using object configs (default ones) a wildcard should never take precedence over explicit~ event type. Thoughts?

So basically when using object configs (default ones) a wildcard should never take precedence over explicit~ event type. Thoughts?

Yes - object configs should be assumed to have no order, so the safest thing to do here would be to put wildcards at the end.
For array configs, they should just maintain their position.

@davidkpiano this is nearly done on my side, the only things left to do are:

review
TS-related stuff

As to the latter - if you have any recommendations regarding TransitionConfig drama 😉 I'm all ears. With all of those mapped types and trying to satisfy strict requirements in type system it's quite cumbersome to handle some cases. Maybe something to think about in the future (although I'm not sure what can really be done, it is what it is).

This?

cleanup TransitionConfig type drama (at different places it's intersected with {event: TEvent["type"]} or { event?: undefined }

What exactly are the current typing issues right now?

Yes, this. I refer to what I have done - not something that was here before this PR.
I've left TransitionConfig roughly untouched, but actually I mostly use it in combination with object type containing event property. For object configs I make this:
https://github.com/davidkpiano/xstate/blob/dcee831a084133bcc203b49c72f5f5df3a99dfee/src/types.ts#L318-L323
because of correct event coming from config map key, so using event as part of TransitionConfig is most likely a bug.
OTOH array configs needs to specify event alongside TransitionConfig (intersection):
https://github.com/davidkpiano/xstate/blob/dcee831a084133bcc203b49c72f5f5df3a99dfee/src/types.ts#L327-L336
And the latter pattern spreads through the codebase, which is not that nice as it requires being hand-written and is surprising to see - but I couldn't figure out a good name for it. Examples:

https://github.com/davidkpiano/xstate/blob/dcee831a084133bcc203b49c72f5f5df3a99dfee/src/StateNode.ts#L126-L130
https://github.com/davidkpiano/xstate/blob/dcee831a084133bcc203b49c72f5f5df3a99dfee/src/StateNode.ts#L1902-L1904
https://github.com/davidkpiano/xstate/blob/dcee831a084133bcc203b49c72f5f5df3a99dfee/src/StateNode.ts#L1964-L1966
https://github.com/davidkpiano/xstate/blob/dcee831a084133bcc203b49c72f5f5df3a99dfee/src/StateNode.ts#L1993-L1995
https://github.com/davidkpiano/xstate/blob/dcee831a084133bcc203b49c72f5f5df3a99dfee/src/StateNode.ts#L2033-L2035

As I have gathered those examples I have also noticed right now that I've actually used different type arguments for some of those - which might indicate some inconsistency. At the same time, I'm not sure if we should even bother with typing internals so "correctly" - would be easier to just assume simple strings in place of TEvent["type"] etc. Not sure if we would lose something by doing that.
I don't know - writing generic TS with mapped types is hard 😢

Not sure if we would lose something by doing that.

I don't think we'd lose anything internally so let's make it as simple as possible.
Can we remove { event?: undefined }? I don't think it's necessary to have that restriction and it'll make typing array+map config easier.
I highly doubt someone will do this:
on: {
  SOMETHING: {
    event: 'SOMETHING_ELSE',
    target: 'foo'
  }
}

which is the only edge-case of that.

Forgive me for butting in, but have you explored alternative syntaxes than array syntax?  The document order in SCXML ensures that transitions are evaluated in the order specified; there are other ways of achieving this than changing to / adding an array syntax.  For example you could declare an order or a priority to transitions.
<transition target="pass" event="*"/>
<transition target="fail" event="foo"/>

could be written as
on: {
  '*': [
    { target: 'pass', order: 1 }
  ],
  foo: [
    { target: 'fail', order: 2 }
  ]
}

While:
<transition target="fail" event="foo"/>
<transition target="pass" event="*"/>

could be expressed as:
on: {
  '*': [
    { target: 'pass', order: 2 }
  ],
  foo: [
    { target: 'fail', order: 1 }
  ]
}

When an event occurs that could match multiple on values, the arrays would be merged, sorted by order.  I believe this could give the same "fidelity" in being able to express the document order of <transition> elements.

@mogsie Interesting approach; @Andarist this could simplify the typing complexity, especially since this is an edge-case that wouldn't normally happen in real library usage.
We should outline the real-life use cases that necessitate this (I realize it's important for SCXML) and see if a simplified API can cover it.

Forgive me for butting in

No problem, always happy to discuss alternatives.
I'm not sure however if that would be easier. First of all, it would expose order on TransitionConfig type publicly and while we always want to recommend using object orderless configs this is just a recommendation.
To make it work we would have to calculate (or just assume) some default order and sort transitions according to that - this I believe would greatly increase implementation complexity.
I also think that readability would suffer, because right now with array configs the order is implied - but rather explicit, everybody knows how ordering works inside an array. Consider this alternative though:
on: {
  '*': [
    { target: 'pass', order: 1 }
  ],
  foo: [
    { target: 'fail' }
  ]
}

Which one comes first? It imposes way more cognitive load to figure this out and this is only a very simple example. It gets more complex pretty quickly (and also imagine some of those lacking explicit order):
on: {
  '*': [
    { target: 'pass', order: 0 },
    { target: 'other', order: 4 }
  ],
  foo: [
    { target: 'x', order: 1 },
    { target: 'y', order: 3 },
  ],
  bar: [
    { target: 'a', order: 2 },
  ]
}

And while we mainly want to even support order-based transitions to satisfy SCXML semantics the readability of the conversion output is very nice to have. The example above doesn't beat top-down reading order in terms of readability, IMHO it's not even close to that.

@Andarist Can you merge master into this? I'm getting some merge conflicts.

@davidkpiano done

@davidkpiano have you had time by any chance to take a look at this?

Wondering if this should be moved to 5.0 - one thing I didn't consider is that this makes transition lookup O(n) instead of O(1) (for non-conditional cases) which affects all use-cases, even though most use-cases will not depend on order. Thoughts?

I’m caching the candidates, so it should have the same O complexity (after first run) - it would have to be a really big statechart for this to become a problem. And even if it starts to show a perf a problem we can easily rework internals to create cache while formatting transitions (which i havent done to keep code simpler) - and then it should be totally the same for both initial and subsequent runs

@davidkpiano any more thoughts on this one? would love to settle it one way or another (even if it means dropping this entirely for now - although as mentioned above I think this is truly 100% compatible with 4.x line)


Add druid_service and host_name labels to Prometheus exporter

Some labels are missing from the Prometheus exporter. They were in the Statsd exporter, such as druid_service and host_name, Which makes the result of Prometheus exporter incompatible with the stated exporter.
It would be great to have the below configs also for Prometheus.
druid.emitter.statsd.includeHost
druid.emitter.statsd.dogstatsdServiceAsTag

The prometheus extension is a community contributed extension, you're welcome to do it by yourself or you have to to wait for someone volunteer to do it.

Some labels are missing from the Prometheus exporter. They were in the Statsd exporter, such as druid_service and host_name, Which makes the result of Prometheus exporter incompatible with the stated exporter.
It would be great to have the below configs also for Prometheus.
druid.emitter.statsd.includeHost
druid.emitter.statsd.dogstatsdServiceAsTag

@amirabbas8  Is this the result you want？

Yes. Also, it would be preferable that label names be like Statsd exporter.
following is an example of a metric in our stated exporter:
druid_jvm_bufferpool_capacity{bufferpoolName="direct",druid_service="druid/router",hostname="i002.kandoo.com:8888"}

@liujianhuanzz


Nonconforming syntax in multiple markdown files

What happened?
Although some MD parsers are pretty forgiving (including GitHub's), the current markdown files in stablehlo include a variety of syntax errors that do not conform to the basic MD syntax rules. Examples include improper indentation for lists, unescaped asterisks signs (meant for bold or italic text), and missing blank lines between headings and paragraphs.
We should follow traditional MD syntax rules to ensure well-structured files that are easy to read, use an agreed-upon structure that can be tested, and that are compatible with more than one MD parser.
The simplest solution is to markdownlint and fix various syntax and style issues.
We can submit fixes for individual files, and make exceptions as appropriate because this tool allows you to disable certain rules in the linter. Then, once the files are cleaned up, we should enable a GitHub Action to run markdownlint on all new pull requests with .md files so we can avoid re-introduction of syntax errors.
Steps to reproduce your issue
No response
Version information
No response

@scottamain Thank you for looking into this! This will be a nice improvement to the state of the art. We had prior discussions about Markdown linting but haven't had the time to follow up yet.

Reopening the ticket because #793 said that it only partially fixes it.

Not sure if this lint has been run on the rfcs/ directory as well? I didn't see the Compatibility RFC in #793, and I'm doubtful that I used perfect MD syntax all the way through.
Here are all md files in the repo.

Hehe, yeah @GleasonK I didn't do the rfc files in the first CL just to keep my first PR simple. I'm sure you saw I've now cleaned those ones as well.
I think there's just two items remaining before closing this issue (in order):

Fix all lint errors in spec.md. I'm happy to do this but I don't want to cause confusing merge conflicts for others because this appears to be a fairly active document. @burmako Should we wait a little longer for this?
Enable the GitHub Action to run markdownlint on all .md file PRs.

Should we wait a little longer for this?

Spoke with Eugene, totally fine to cause merge conflicts. There is only one open PR touching spec now, which makes this a good time to make that change. That plan sounds good to me.
Got the script running locally, looks like its only spec:
$ ./build_tools/github_actions/lint_markdown.sh "**/*.md" 2>&1 | grep -v spec
<no output, all failures are in spec.md>

Given that we have a CI job now which lints markdown files, I think we can close this ticket.


Mixing Unequal Inputs [Optimal Heuristic]

Related Issues: https://github.com/nopara73/ZeroLink/issues/73, https://github.com/nopara73/ZeroLink/issues/74, https://github.com/nopara73/ZeroLink/issues/75
Related Question: https://bitcoin.stackexchange.com/questions/73431/mixing-unequal-inputs
Non-entropist Approach Measuring Anonymity: https://www.freehaven.net/anonbib/cache/entropist.pdf
Knapsack Algorithm: https://www.comsys.rwth-aachen.de/fileadmin/papers/2017/2017-maurer-trustcom-coinjoin.pdf
Intuition

Jeremy Mandelkern

As your goal appears to be the "optimization" of the average of some sort of weighted sum, the way in which your weighted terms are generated will be key. It may be possible that optimization techniques from Multivariate Calculus would be applicable, I.E. Lagrange Multipliers.

Advantages of unequal input mixing, compared to the fixed denomination mixing. I will use the following notation here:
UIM - Unequal Input Mixing
FDM - Fixed Denomination Mixing

UIM's main goal is to optimize the cost/anonymity set.
In FDM those who don't have enough money to mix, will not be able to mix. In UIM it is not an issue anymore.
In FDM peers often join together their utxos in order to reach the denomination. This exposes common ownership. There is no such an issue in UIM. Because of this, joining utxos together after the mix is not as big of a deal anymore.
In UIM mixing can be done over and over again until the desired anonymity set is reached. In FDM mixing cannot be repeated, because the mixed output of the mix will never reach the sufficient input level of the next mix (due to network fees.) In FDM if the user would decide to participate with an already mixed coin, then he would have to add another input in order to suffice the mix requirements, which exposes common ownership.

Combining Groupsend with UIM: Unequal Amount Mixing for ZeroLink using Preferred Value Series Fixed Denominations
https://gist.github.com/nothingmuch/544cdd47dd18ef8fe923b54e0d5ee141


Documentation: <STORE>

Suggestion
Document all store integrations under https://github.com/configu/configu/tree/main/packages/integrations/stores with all the necessary details that explain what each store is and how to use them.
Config stores to document:

#574
#582
#583
#584
#585
#586
#587
#588
#589
#590
#591
#592
#593
#594
#595
#596
#597
#598
#599
#636

Motivation

Introduces users to the ConfigStores.
Improves usability of the stores by providing usage examples.
Improves the completeness of the integration package.
The store integration README.md files will be converted into documentation under: https://docs.configu.com/integrations

Context

Example PR of a store doc contribution: #575

I would like to work on this!

@RS-labhub go ahead, pick an issue and request assignment ⭐

I guess this page also needs a md (it's needed tbh)

@RS-labhub, I'm not entirely sure what you mean by this page needing its own README.md. Please elaborate on which folder in the repository you're referring to.

@RS-labhub, I'm not entirely sure what you mean by this page needing its own README.md. Please elaborate on which folder in the repository you're referring to.

I meant with this folder: https://github.com/configu/configu/tree/main/packages/integrations/stores
It's better to have documentation about stores

I understand @RS-labhub, the documentation for the stores folder should be contained within https://github.com/configu/configu/blob/main/packages/integrations/README.md which is currently out of date. The relevant issue for it is #495 and there is an ongoing PR that attempts to resolve the issue. Please feel free to provide your input regarding this subject on the relevant PR(#504) or issue.

Ppl are opening PRs on assigned + less descriptive issues 👁

🌟 Hacktoberfest Success! 🌟
Thanks to our incredible contributors, all store documentation is now complete! This project couldn't have come this far without your hard work, dedication, and enthusiasm. Huge shoutout to each of you for helping make this happen!
Special thanks to:
@poorvibajpai
@Ritesh-Udgata
@mrswastik-robot
@RS-labhub
@TomerPacific
@abhirajadhikary06
Your contributions mean the world to us and the entire community. Keep up the fantastic work—looking forward to building more together! 💪✨


Update admission webhook config, remove Chart.lock, and release kong 2.28.1

What this PR does / why we need it:
See https://github.com/Kong/kubernetes-ingress-controller/pull/4733. Adds that; releases 2.28.1.
Removes Chart.lock and adds it to gitignore.
Special notes for your reviewer:
Technically we had GWAPI checks available for earlier versions also, but they never made it into the chart webhook config. I'm gating them to 2.12+ because backporting the checks isn't that crucial.
I don't think we should be including Chart.lock in our distributed chart, though unfortunately docs are kinda vague about this. https://helm.sh/docs/helm/helm_dependency_update/ and https://helm.sh/docs/helm/helm_dependency_build/ suggest the intended use of this file is so that installs from a local copy of the chart repo can be restored to their original installed version in some sort of data loss scenario.
We did not include a Chart.lock until 2.8.1 and had no issues. Chart.yaml includes its own version rules that look more appropriate for distribution (you can specify ranges rather than a pinned version+hash, though we don't actually use them for the Postgres dep).
AFAIK this got included because the helm dependency commands you use to get dependency updates always create it, and it's not obvious whether you should include it or not.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] PR is based off the current tip of the main branch.
[x] Changes are documented under the "Unreleased" header in CHANGELOG.md
[x] New or modified sections of values.yaml are documented in the README.md
[x] Commits follow the Kong commit message guidelines

I don't think we should be including Chart.lock in our distributed chart, though unfortunately docs are kinda vague about this. https://helm.sh/docs/helm/helm_dependency_update/ and https://helm.sh/docs/helm/helm_dependency_build/ suggest the intended use of this file is so that installs from a local copy of the chart repo can be restored to their original installed version in some sort of data loss scenario.

It's also for the reproducible builds. When the dependency changes you'd probably get a warning/error because the digests don't match. Not sure how much we'd like to pay attention to that though.

It's also for the reproducible builds. When the dependency changes you'd probably get a warning/error because the digests don't match. Not sure how much we'd like to pay attention to that though.

For the intended purpose of our distributables I think no--if we're declaring an allowed dependency range, we expect that the exact dependency will vary within that range. What Chart.yaml and Chart.lock express are at odds.
I think we'd have more use for ensuring that a given tag is unchanged (e.g. that the contents of ingress 3.4.5, including its allowed dependency ranges, are always the same even if someone tries to rewrite history). Helm doesn't directly provide that (Chart.lock tracks dependency hashes only, it does not hash the chart itself), but the newer OCI option for distributing charts does AFAIK.
It makes sense once you've installed a particular state and want to get back to exactly that, e.g.

Chart.yaml says dependency must be ~3
Your release pulled dependency 3.4.1 because that was the latest 3.4 available at the time.
Environment asplode and state is lost.
You want to return to exactly what you installed originally.

Chart.lock can then ensure that you get 3.4.1 still even if 3.5 has since been released, but we have no reason for unrelated new installs to get 3.4.1--we do want them to get 3.5.0.
This is somewhat moot because chart-releaser behavior effectively forces you to a specific version anyway (albeit minus hash guarantees), but ignoring that, AFAIK exact reproducible dependencies aren't something we want to enforce, e.g. here we indicate compatibility with a wide range of Postgres major versions that you may choose to pin yourself.


Adding new sources failed.

I have exported required token like is mentioned here https://github.com/packit-service/packit/blob/master/docs/update.md#tutorial.
But sync failed with traceback:
using "master" dist-git branch
syncing ./.packit.yaml
syncing ./rebase-helper.spec
INFO: Downloading file from URL https://github.com/rebase-helper/rebase-helper/archive/0.15.0/rebase-helper-0.15.0.tar.gz

    [<=>                           ]     0.00    in 00:00:00
    [<=>                           ]     8.00K   in 00:00:00
    [<=>                           ]    16.00K   in 00:00:00
    [<=>                           ]    24.00K   in 00:00:00
    [<=>                           ]    32.00K   in 00:00:00
    [<=>                           ]    40.00K   in 00:00:00
    [<=>                           ]    48.00K   in 00:00:00
    [<=>                           ]    56.00K   in 00:00:00
    [<=>                           ]    64.00K   in 00:00:00
    [<=>                           ]    72.00K   in 00:00:00
    [<=>                           ]    80.00K   in 00:00:00
    [<=>                           ]    88.00K   in 00:00:00
    [<=>                           ]    96.00K   in 00:00:00
    [<=>                           ]   104.00K   in 00:00:00
    [<=>                           ]   112.00K   in 00:00:00
    [<=>                           ]   120.00K   in 00:00:00
    [<=>                           ]   128.00K   in 00:00:00
    [<=>                           ]   136.00K   in 00:00:00
    [<=>                           ]   144.00K   in 00:00:00
    [<=>                           ]   152.00K   in 00:00:00
    [<=>                           ]   160.00K   in 00:00:00
    [<=>                           ]   168.00K   in 00:00:00
    [<=>                           ]   176.00K   in 00:00:00
    [<=>                           ]   184.00K   in 00:00:00
    [<=>                           ]   192.00K   in 00:00:00
    [<=>                           ]   200.00K   in 00:00:00
    [<=>                           ]   208.00K   in 00:00:00
    [<=>                           ]   216.00K   in 00:00:00
    [<=>                           ]   224.00K   in 00:00:00
    [<=>                           ]   232.00K   in 00:00:00
    [<=>                           ]   240.00K   in 00:00:00
    [<=>                           ]   248.00K   in 00:00:00
    [ <=>                          ]   256.00K   in 00:00:00
    [ <=>                          ]   264.00K   in 00:00:00
    [ <=>                          ]   272.00K   in 00:00:00
    [ <=>                          ]   280.00K   in 00:00:00
    [ <=>                          ]   288.00K   in 00:00:00
    [ <=>                          ]   296.00K   in 00:00:00
    [ <=>                          ]   304.00K   in 00:00:00
    [ <=>                          ]   312.00K   in 00:00:00
    [ <=>                          ]   320.00K   in 00:00:00
    [ <=>                          ]   328.00K   in 00:00:00
    [ <=>                          ]   336.00K   in 00:00:00
    [ <=>                          ]   344.00K   in 00:00:00
    [ <=>                          ]   352.00K   in 00:00:00
    [ <=>                          ]   360.00K   in 00:00:00
    [ <=>                          ]   368.00K   in 00:00:00
    [ <=>                          ]   376.00K   in 00:00:00
    [ <=>                          ]   384.00K   in 00:00:00
    [ <=>                          ]   392.00K   in 00:00:00
    [ <=>                          ]   400.00K   in 00:00:00
    [ <=>                          ]   408.00K   in 00:00:00
    [ <=>                          ]   416.00K   in 00:00:00
    [ <=>                          ]   424.00K   in 00:00:00
    [ <=>                          ]   432.00K   in 00:00:00
    [ <=>                          ]   440.00K   in 00:00:00
    [ <=>                          ]   448.00K   in 00:00:00
    [ <=>                          ]   456.00K   in 00:00:00
    [ <=>                          ]   464.00K   in 00:00:00
    [ <=>                          ]   472.00K   in 00:00:00
    [ <=>                          ]   480.00K   in 00:00:00
    [ <=>                          ]   488.00K   in 00:00:00
    [ <=>                          ]   496.00K   in 00:00:00
    [ <=>                          ]   504.00K   in 00:00:00
    [  <=>                         ]   512.00K   in 00:00:00
    [  <=>                         ]   520.00K   in 00:00:00
    [  <=>                         ]   528.00K   in 00:00:00
    [  <=>                         ]   536.00K   in 00:00:00
    [  <=>                         ]   544.00K   in 00:00:00
    [  <=>                         ]   552.00K   in 00:00:00
    [  <=>                         ]   560.00K   in 00:00:00
    [  <=>                         ]   568.00K   in 00:00:00
    [  <=>                         ]   576.00K   in 00:00:00
    [  <=>                         ]   584.00K   in 00:00:00
    [  <=>                         ]   592.00K   in 00:00:00
    [  <=>                         ]   600.00K   in 00:00:00
    [  <=>                         ]   608.00K   in 00:00:00
    [  <=>                         ]   616.00K   in 00:00:00
    [  <=>                         ]   624.00K   in 00:00:00
    [  <=>                         ]   632.00K   in 00:00:00
    [  <=>                         ]   640.00K   in 00:00:00
    [  <=>                         ]   648.00K   in 00:00:00
    [  <=>                         ]   656.00K   in 00:00:00
    [  <=>                         ]   664.00K   in 00:00:00
    [  <=>                         ]   672.00K   in 00:00:00
    [  <=>                         ]   680.00K   in 00:00:00
    [  <=>                         ]   688.00K   in 00:00:00
    [  <=>                         ]   696.00K   in 00:00:00
    [  <=>                         ]   704.00K   in 00:00:00
    [  <=>                         ]   712.00K   in 00:00:00
    [  <=>                         ]   720.00K   in 00:00:00
    [  <=>                         ]   728.00K   in 00:00:00
    [  <=>                         ]   736.00K   in 00:00:00
    [  <=>                         ]   744.00K   in 00:00:00
    [  <=>                         ]   752.00K   in 00:00:00
    [  <=>                         ]   760.00K   in 00:00:00
    [   <=>                        ]   768.00K   in 00:00:00
    [   <=>                        ]   776.00K   in 00:00:00
    [   <=>                        ]   784.00K   in 00:00:00
    [   <=>                        ]   792.00K   in 00:00:00
    [   <=>                        ]   800.00K   in 00:00:00
    [   <=>                        ]   808.00K   in 00:00:00
    [   <=>                        ]   816.00K   in 00:00:00
    [   <=>                        ]   824.00K   in 00:00:00
    [   <=>                        ]   832.00K   in 00:00:00
    [   <=>                        ]   840.00K   in 00:00:00
    [   <=>                        ]   848.00K   in 00:00:00
    [   <=>                        ]   856.00K   in 00:00:00
    [   <=>                        ]   864.00K   in 00:00:00
    [   <=>                        ]   872.00K   in 00:00:00
    [   <=>                        ]   880.00K   in 00:00:00
    [   <=>                        ]   888.00K   in 00:00:00
    [   <=>                        ]   896.00K   in 00:00:00
    [   <=>                        ]   904.00K   in 00:00:00
    [   <=>                        ]   912.00K   in 00:00:00
    [   <=>                        ]   920.00K   in 00:00:00
    [   <=>                        ]   928.00K   in 00:00:00
    [   <=>                        ]   936.00K   in 00:00:00
    [   <=>                        ]   944.00K   in 00:00:00
    [   <=>                        ]   952.00K   in 00:00:00
    [   <=>                        ]   960.00K   in 00:00:00
    [   <=>                        ]   968.00K   in 00:00:00
    [   <=>                        ]   976.00K   in 00:00:00
    [   <=>                        ]   984.00K   in 00:00:00
    [   <=>                        ]   992.00K   in 00:00:00
    [   <=>                        ]  1000.00K   in 00:00:00
    [   <=>                        ]  1008.00K   in 00:00:00
    [   <=>                        ]  1016.00K   in 00:00:00
    [    <=>                       ]     1.00M   in 00:00:00
    [    <=>                       ]     1.01M   in 00:00:00
    [    <=>                       ]     1.02M   in 00:00:00
    [    <=>                       ]     1.02M   in 00:00:00
    [    <=>                       ]     1.03M   in 00:00:00
    [    <=>                       ]     1.04M   in 00:00:00
    [    <=>                       ]     1.05M   in 00:00:00
    [    <=>                       ]     1.05M   in 00:00:00
    [    <=>                       ]     1.06M   in 00:00:00
    [    <=>                       ]     1.07M   in 00:00:00
    [    <=>                       ]     1.08M   in 00:00:00
    [    <=>                       ]     1.09M   in 00:00:00
    [    <=>                       ]     1.09M   in 00:00:00
    [    <=>                       ]     1.10M   in 00:00:00
    [    <=>                       ]     1.11M   in 00:00:00
    [    <=>                       ]     1.12M   in 00:00:00
    [    <=>                       ]     1.12M   in 00:00:00
    [    <=>                       ]     1.13M   in 00:00:00
    [    <=>                       ]     1.14M   in 00:00:00
    [    <=>                       ]     1.15M   in 00:00:00
    [    <=>                       ]     1.16M   in 00:00:00
    [    <=>                       ]     1.16M   in 00:00:00
    [    <=>                       ]     1.17M   in 00:00:00
    [    <=>                       ]     1.18M   in 00:00:00
    [    <=>                       ]     1.19M   in 00:00:00
    [    <=>                       ]     1.20M   in 00:00:00
    [    <=>                       ]     1.20M   in 00:00:00
    [    <=>                       ]     1.21M   in 00:00:00
    [    <=>                       ]     1.22M   in 00:00:00
    [    <=>                       ]     1.23M   in 00:00:00
    [    <=>                       ]     1.23M   in 00:00:00
    [    <=>                       ]     1.24M   in 00:00:00
    [     <=>                      ]     1.25M   in 00:00:00
    [     <=>                      ]     1.26M   in 00:00:00
    [     <=>                      ]     1.27M   in 00:00:00
    [     <=>                      ]     1.27M   in 00:00:00
    [     <=>                      ]     1.28M   in 00:00:00
    [     <=>                      ]     1.29M   in 00:00:00
    [     <=>                      ]     1.30M   in 00:00:00
    [     <=>                      ]     1.30M   in 00:00:00
    [     <=>                      ]     1.31M   in 00:00:00
    [     <=>                      ]     1.32M   in 00:00:00
    [     <=>                      ]     1.33M   in 00:00:00
    [     <=>                      ]     1.34M   in 00:00:00
    [     <=>                      ]     1.34M   in 00:00:00
    [     <=>                      ]     1.35M   in 00:00:00
    [     <=>                      ]     1.36M   in 00:00:00
    [     <=>                      ]     1.37M   in 00:00:00
    [     <=>                      ]     1.38M   in 00:00:00
    [     <=>                      ]     1.38M   in 00:00:00
    [     <=>                      ]     1.39M   in 00:00:00
    [     <=>                      ]     1.40M   in 00:00:00
    [     <=>                      ]     1.41M   in 00:00:00
    [     <=>                      ]     1.41M   in 00:00:00
    [     <=>                      ]     1.42M   in 00:00:00
    [     <=>                      ]     1.43M   in 00:00:00
    [     <=>                      ]     1.44M   in 00:00:00
    [     <=>                      ]     1.45M   in 00:00:00
    [     <=>                      ]     1.45M   in 00:00:00
    [     <=>                      ]     1.46M   in 00:00:00
    [     <=>                      ]     1.47M   in 00:00:00
    [     <=>                      ]     1.48M   in 00:00:00
    [     <=>                      ]     1.48M   in 00:00:00
    [     <=>                      ]     1.49M   in 00:00:00
    [      <=>                     ]     1.50M   in 00:00:00
    [      <=>                     ]     1.51M   in 00:00:00
    [      <=>                     ]     1.52M   in 00:00:00
    [      <=>                     ]     1.52M   in 00:00:00
    [      <=>                     ]     1.53M   in 00:00:00
    [      <=>                     ]     1.54M   in 00:00:00
downloaded archive: /tmp/tmppry2kb63/rebase-helper-0.15.0.tar.gz
uploading to the lookaside cache
Adding new sources failed:
Could not execute new_sources: Request is unauthorized.

Traceback (most recent call last):
  File "/usr/local/bin/packit", line 11, in <module>
    load_entry_point('packit==0.1.dev180+g0179bc3', 'console_scripts', 'packit')()
  File "/usr/local/lib64/python3.7/site-packages/click/core.py", line 764, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib64/python3.7/site-packages/click/core.py", line 717, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib64/python3.7/site-packages/click/core.py", line 1137, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib64/python3.7/site-packages/click/core.py", line 956, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib64/python3.7/site-packages/click/core.py", line 555, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib64/python3.7/site-packages/click/decorators.py", line 64, in new_func
    return ctx.invoke(f, obj, *args, **kwargs)
  File "/usr/local/lib64/python3.7/site-packages/click/core.py", line 555, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/packit/cli/update.py", line 31, in update
    api.update(dist_git_branch)
  File "/usr/local/lib/python3.7/site-packages/packit/api.py", line 96, in update
    dg.upload_to_lookaside_cache(archive)
  File "/usr/local/lib/python3.7/site-packages/packit/distgit.py", line 176, in upload_to_lookaside_cache
    f.new_sources(sources=archive_path)
  File "/usr/local/lib/python3.7/site-packages/packit/utils.py", line 85, in new_sources
    fail=fail,
  File "/usr/local/lib/python3.7/site-packages/packit/utils.py", line 54, in run_command
    raise Exception(f"{shell.args!r} failed with {error_message!r}")
Exception: ['fedpkg', 'new-sources', '/tmp/tmppry2kb63/rebase-helper-0.15.0.tar.gz'] failed with 'Adding new sources failed:'

You need to generate fedora Kerberos:
kinit<EMAIL_ADDRESS>

If ran as a service the fedora infra can provide a keytab for this

@pypingou thanks, Fesco already approved packit, so I requested the credentials: https://pagure.io/fedora-infrastructure/issue/7596
As for this issue:

The guide clearly states that you need valid Fedora kerberos ticket
The error message could be better, we can fix that


Can't disable sysctl init container

I tried the helm chart to disable sysctl init container
  initSysctl:
    enabled: false

Which still creates the init container

Hi, if you look at this line in the deployment.yaml, you'll see there is an or condition: {{- if or .Values.initSysctl.enabled .Values.elasticsearch.configureNode }}.
Can you please confirm the setting you have here in the values.yaml for elasticsearch.configureNode ?

Hi, @namloc2001!
Setting elasticsearch.configureNode to false fixes the problem.


including html snippets

Hi Team,
Looking around the docs pages and found this https://github.com/interactivethings/catalog/tree/gh-pages/docs/html-project-example -
It looks like you may be able to include things like a data visualization.
I'm not completely clear how to do this or if it's still supported?
Also for imports - could I use an html snippet by including it in a md page?
Fo instance if we have a snippet of say buttons thats straight html that is tested against - can I then include that snippet in a buttons.md documentation page?
Thanks!

Hi @jeaster12, we've removed this specimen type from Catalog core because we felt it was too specific and complex to maintain and ship per default. The extracted version lives at https://github.com/interactivethings/catalog-specimen-project, although I'm not completely sure about its status.
You can add the custom specimen like this:
<Catalog
  specimens={{project: ProjectSpecimen}}
  /*...*/
/>

I'm closing this issue, please feel free to reopen if you run into trouble.


How can I get proposal_file from my own dataset?

Hello, thanks so much for providing this fantastic frame to help us train our own instance segmentation model.
Here's my question:
I have my own 3 label dataset and coverted it into coco style, while I'm trying to use mmdetec train model listed below, I don't know how to get proposal_files it needed.
Model:
Fast R-CNN (with pre-computed proposals)
R-50-FPN
Files I don't know how to get:
proposal_file=data_root + 'proposals/rpn_r50_fpn_1x_train2017.pkl'
proposal_file=data_root + 'proposals/rpn_r50_fpn_1x_val2017.pkl',
proposal_file=data_root + 'proposals/rpn_r50_fpn_1x_val2017.pkl',
Thanks again, hope someone can help me on this.

You need to generate the proposal file with a RPN model first.

Excuse me, are you training rpn alone? I am using guaid anchor. But I don't know what the reasonable process is, whether to use ga-faster rcnn directly or try ga-rpn to generate proposal and then apply it to ga-faster rcnn, but how does proposal apply to ga-faster rcnn? I read resd me without relevant information, and hope to get your reply.

You need to generate the proposal file with a RPN model first.

Excuse me, are you training rpn alone? I am using guaid anchor. But I don't know what the reasonable process is, whether to use ga-faster rcnn directly or try ga-rpn to generate proposal and then apply it to ga-faster rcnn, but how does proposal apply to ga-faster rcnn? I read resd me without relevant information, and hope to get your reply.


placeholder text should be localized

The placeholder text ("Enter a language", "Enter a country", etc) should be localized.

Fixed in #18


Preview does not update when node is deleted

How to reproduce:
Open a new material. Add a perlin warp1 node (for example. This works with any node that changes what the output looks like). Link up that node with the albedo, wait for the preview to update, then delete the node. The preview does not change.
Add another one, connect, disconnect. This "fixes" it.
Related to #64

Indeed, thanks for reporting. That will be a last minute fix. ;)

Looks like it's fixed now...


[WIP] update dependencies, add more examples

TODO:

[x] Prepare for Google DevFest showcase (finished 3/3);

[x] Try fix abnormal evaluation scores when apply MixLoRA with Gemma models;

Problem with Gemma has been found: when MixLoRA with a large number of parameters is used on a smaller model such as 2B, it will cause overfitting.


fixed issue in homepage

Codecov Report

Merging #10 (4e00b75) into master (99e50c6) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master      #10   +/-   ##
=======================================
  Coverage   56.72%   56.72%
=======================================
  Files          35       35
  Lines         409      409
  Branches       67       67
=======================================
  Hits          232      232
  Misses        174      174
  Partials        3        3

Impacted Files
Coverage Δ

src/components/pages/Home/Home.tsx
47.72% <100.00%> (ø)

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Fix the custom path to typescriptServices.js feature

[x] All compiled assets are included (atom packages are git tags and hence the built files need to be a part of the source control)

Code run with vm.runInContext is not wrapped with the helper that sets __dirname and __filename variables so it was throwing an error. A simple require is all that's needed in this case.

Could we get a new release with this fix?


I just tried to resubmit the job at the original folder, but it fails immediately.
Thank you very much
Best
Geng

Hi Geng,
Could you share your error message?
Generally, if your previous run is successful, then the software will store the best model in the result directory and it should automatically load that model when you continue the training. However, if your previous training crashes due to an error when you run it the first time but not due to the walltime restriction, then no best model is stored and you shall remove your result directory to completely restart the training.


Communications of multiple wallets through single socket

This is the counterpart modification to the server corresponding to https://github.com/bitpay/bitcore-wallet-client/pull/89

Interesting! Thanks for the contribution. we will review it soon.

Hey, this is a much needed refactoring. I made a couple of rather small comments. Thank you for the contribution.

Hey, thanks for the comments. I'm not at the office right now, but I will make the appropriate changes tomorrow. In the mean time, let me answer some of your questions.

I agree, dict[key] = null is awkward, but to my knowledge (which is limited in this regard) JS doesn't have a set type with fast lookup. It's my understanding that checking for presence of an item in an array would be slower. Given the likely length of the sequence it would probably not matter, though. If you'd still prefer an array I have no problem changing it.
I wasn't sure what you guys used for logging. Now that you've brought up log.info(), I'll comment a few lines on the client side.

Regarding the dict[key] = null issue, I agree that it shouldn't matter in this scenario. I think we will benefit from improved readability.

Shoot. I knew I was forgetting something.

This one is waiting https://github.com/bitpay/bitcore-wallet-client/pull/89

Hi @Helios-vmg,
Although this is a great contribution, we will not be merging it unfortunately. The reason is we have been trying for some time now to migrate away from socket.io as it is causing networking issues and excessive use of resources on clients. We have been taking small steps towards a long-polling approach.
However, your contribution has shown a much better way of doing things so multiplexing notifications is now a part of the roadmap for the new architecture.
We will absolutely give you due credit and would love for you to review the associated PRs once they are posted.
Thank you very much!

Hey, no problem. Just let me know when you have the diffs you'd like me to review.


Font-display support?

Lately Google Fonts seems to support (finally) font-display option for better performance.
https://scotch.io/bar-talk/google-fonts-now-supports-font-display
Is it possible to use set it right now with this package?
If not, it could add as feature in a next release?
Got no info about it and asking. It would be awesome :)

As per Addy Osmani's tweet it already supports &display=swap.
You can add this to this loader too, however, it only works with single fonts.
Example:
{
    webfontloader: {
        google: {
            families: ['Open+Sans:300:400:600&display=swap']
        }
    },
}

However, if you pipe the fonts (['Open+Sans:300:400|Roboto:300:700']), it doesn't currently work because of Typekit being slow on upgrades. Adding &display=swap to any or both of the fonts in the array doesn't work either - at least not in my tests.
But since this webfontloader os built on top of Typekit's webfontloader, you can make a custom loader and supply the URL's yourself, like so:
{
    webfontloader: {
        custom: {
            families: [
                'Open Sans:n3,n4',
                'Roboto:n3,n7'
            ],
            urls: [
                'https://fonts.googleapis.com/css?family=Open+Sans:300,400&display=swap'
                'https://fonts.googleapis.com/css?family=Roboto:300,700&display=swap'
            ]
        }
    },
}

You can then add two or more fonts if you want. Notice the nx where x is an int, corresponding to the font-weight, and the URLs have to be in the correct order, otherwise you'll get the naming incorrect.
I don't know if @manniL or @mangerlahn wants to wait for the PR on Typekit (it's a month old as of June 2019), or if they can make some magic.
So all in all, it works, you just have to add a few more lines of code 😉

Works!!!
Thanks 👍

Thanks to @moso 	for the detailed answer.
I'd accept a PR for the README ☺

Yep! If ok also for @moso I could try to do a PR for the README in the weekend

PR done and ready to be checked.

Pr merged. Info now are in the ReadMe File. Issue closed.


Costumazation of expired cert date with gui fucntion

would we make this function ?

can you explain what you mean and how it should look like?


Nvidium is "***" and unusable in every way

Can't fabricate items that need it, or sell the supply I have

This is a result of some of the later tier ores being unlocalized.
I'll send out a patch when I have the time.


Error.captureStackTrace is not a function

In Safari I'm getting the following error:
TypeError: Error.captureStackTrace is not a function. (In 'Error.captureStackTrace(this,this.constructor)', 'Error.captureStackTrace' is undefined)

This I believe comes from the FetchError lib. Is it possible to add a conditional to catch if Error.captureStackTrace is defined?
Thanks

This module is only supposed to be used in Node.js. Browsers are not supported.

https://github.com/github/fetch


xds: respond to requests previously miscategorized as ACKs

See https://github.com/envoyproxy/envoy/issues/13009 for details
Fixes #38709 (previously 'fixed', but really the fix was a workaround)
Fixes https://github.com/istio/istio/issues/39720
Please provide a description of this PR:

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
1ba5716ada5c4621a6688be841cae222e1ace1d2
link
true
/test unit-tests_istio

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

LGTM.

@hzxuzhonghu there is some discussion in https://github.com/envoyproxy/envoy/issues/13009, doesn't seem soon


Replace update scripts with Go process

Replace the current batch and bash update scripts on OSX and Windows with a Golang process to handle the tasks. This should help improve the issues some users experiencing usually concerning permission problems.

Wouldn't this require people to have Go installed or can it be self-bundled?

@Nefari0uss Compiles down to a binary, would be bundled in with the application.

  This was a central "solution" to the problems Go Lang was solving.

@srs1978 @dustinblackman Ahh, cool! Learned something new.

Closing this in favour of http://electron.atom.io/docs/api/auto-updater/


split already_pending

Current version of already_pending:
    def already_pending(self, unit_type: Union[UpgradeId, UnitTypeId], all_units: bool=False) -> int:
        # TODO / FIXME: SCV building a structure might be counted as two units

        if isinstance(unit_type, UpgradeId):
            return self.already_pending_upgrade(unit_type)

        ability = self._game_data.units[unit_type.value].creation_ability

        amount = len(self.units(unit_type).not_ready)

        if all_units:
            amount += sum([o.ability == ability for u in self.units for o in u.orders])
        else:
            amount += sum([o.ability == ability for w in self.workers for o in w.orders])
            amount += sum([egg.orders[0].ability == ability for egg in self.units(UnitTypeId.EGG)])

        return amount

Regardless of what we're trying to find, the function will always loop over self.units, self.workers, and self.units(UnitTypeId.EGG), even when not needed. This slows down the function, which is more noticeable when it is called many times. Maybe it would be better to split it based on the requested unit type (e.g. already_pending_eggs, already_pending_units, already_pending_buildings)

I think this is solved then, feel free to reopen if there is something else.


Change request - disable default values

Hi there :)
It would be truly great if each of the properties of the Wled2 node were optional (ie checkbox next to each to enable/disable default values).
This would make certain use-cases a lot simpler and give a better user experience.
For instance - WLED is displaying an effect which was invoked via the WLED app.  I would like to turn this off via NR by simply setting state = off, so that we get the same UX as doing so via the app or the web interface- eg, simply fades to black.
Unfortunately, with current implementation, I can't do that.    And I can't set state to be the existing state, as I have no way of knowing the current state (see issue #79).
I can get the desired result by invoking the API directly, however that defeats the purpose of having this node in the first place!
Hope that's do-able - thank you!

Are there other situations where this is causing issues? Or just when setting payload to off?

Changing brightness, changing intensity, changing speed, changing any of the colours, and so on.
Thanks for looking at this so quickly!

Hey there,
having the same fault.
For example I want to change the brightness on my streamdeck to 50% and the color1 is red this flow will change also the color to white.
The json I use is literally
{"brightness":128}
would it be possible that just the brightness is changed?
Best regards :)

Hey there,
having the same fault.
For example I want to change the brightness on my streamdeck to 50% and the color1 is red this flow will change also the color to white.
The json I use is literally
{"brightness":128}
would it be possible that just the brightness is changed?
Best regards :)

For something that simple I suggest just sending the command directly to WLED with an httprequest node. You're already building JSON anyway, and the JSON for the API is really straightforward.

Okay, haven't known about this opportunity.
Now I use it. :) Thanks

Closing old issues.


Is it possible to start publishing latest releases?

Hello!
I'm very interested in using this plugin, however when I try to install via the add new plugin screen I receive this error:

I'm guessing it's because there are no published releases in this repo?
I'm happy to submit a pull request to support this, but I've got no experience with budibase plugins so any guidance would be helpful

Hi @leo-mendoza-qatalog , I see PR #2 will enable publishing and will allow you to install via github

Closing as PR #2 makes this installable 🎉


[travis] Delete garbage Docker images for real

Now that the garbage collector script has been running successfully for
a few days and we've validated its results, we can change it to actually
delete images instead of just printing which ones it would delete.
Fixes https://github.com/Microsoft/bond/issues/800

For those with access, the results of the cleanup job can be viewed in the VSTS instance.


Refactoring of ZodFormattedError type to improve tsc check time

This small refactoring of ZodFormattedError fix several  performance issues in some edge cases.
I did some benchmarks with simple case with typescript compiler option strict: false https://github.com/gydroperit/zod-test-regression

Now amount of generated types three times less than before, while  building typescript project, thus almost halves Check time

Without fix
Lines:           30507
Identifiers:     49830
Symbols:         47942
Types:           17794
Instantiations:  29270
Memory used:    77234K
I/O read:        0.00s
I/O write:       0.00s
Parse time:      0.31s
Bind time:       0.13s
Check time:      0.31s
Emit time:       0.01s
Total time:      0.75s

with this fix
Files:              72
Lines:           30508
Identifiers:     49824
Symbols:         44537
Types:            5659
Instantiations:  17489
Memory used:    70989K
I/O read:        0.00s
I/O write:       0.00s
Parse time:      0.31s
Bind time:       0.12s
Check time:      0.20s
Emit time:       0.01s
Total time:      0.63s

Second issue is maybe more  important than 15 ms of build time. On some reason VS Code on latest  version of zod has very laggy intellisense autocompletion(about 1 to 3 seconds to show autocomplete list) and slow ESLint check time in source files with zod used(About 8 seconds in my case). Even this strict option set to true.
After fix - it will run smooth like in previous version,

This problem also described in https://stackoverflow.com/questions/74881472/slow-typescript-autocompletion-in-vs-code-for-zod
https://github.com/colinhacks/zod/issues/1741
https://github.com/microsoft/TypeScript/issues/45824

Makes sense, looks good. Thanks!


Test trh issue#54

@brenzi
I have checked it on my local instance, everything is working as expected.
As Waldemar needs the changes, please take a look at it and accept.
Thanks

this PR does not what it says. I see changes with account, with video. All this is not mentioned in the OP. I can only iterate that I usually require one PR per issue

please mention all issues that are resolved with this in the description, so I at least know what to check


added moneyMaster api script

MoneyMaster is a script that will handle 'transactions' (spending money and returning exact change). Additionally, this script allows the GM to automatically split money (rounded to the nearest copper) equally among any number of party members.

CashMaster is a better version of this!


Binance streaming rate limit

Binance closes the WebSocket connection if more than one per second subscription message is sent
(even though Binance docs state that 5 messages per second are allowed)

has this been fixed elsewhere?
the mergeconflicts should be resolveable. i noticed similiar behaviour with binance streams in the past.

Hi.

You can use subscription on connect, there is no limit on it.
If I remember correctly, in reality there are 4 op/sec without error...