In Privacy settings, Hide mail Client still refers to K9 User Agent

Checklist

[X] I have used the search function to see if someone else has already submitted the same bug report.
[X] I will describe the problem with as much detail as possible.

App
Thunderbird for Android
App version
8.0
Where did you get the app from?
None
Android version
unknown
Device model
No response
Steps to reproduce
user report at https://support.mozilla.org/en-US/questions/1472738
Expected behavior
"Thunderbird for Android"
Actual behavior
"K9"
Logs
No response

@kewisch which is the missing expected behavior addressed here, when Hide mail client is checked ?

When  I send mail, receiver will not be able to see my mail client in his/her mail header?
I as as user won't see any mail client info in any of my received mails?

Asking this because 1 is working in my case (Thunderbird debug version : 10.0-SNAPSHOT) so is it no 2? or is no1 ? In-case it's no 1, please provide steps to re-produce, so I can re-produce and fix it.
Please let me know. Thank you!

I think no functionality is affected, but with en_GB localization it is still displaying K-9 in the UI for the user agent setting, see https://github.com/thunderbird/thunderbird-android/blob/8668fabd5cff6cbbe630de653e490be3219ad39f/legacy/ui/legacy/src/main/res/values-en-rGB/strings.xml#L599
It looks like there are also some other languages where this is still the case.

This has been changed in weblate 5 moths ago: https://hosted.weblate.org/translate/tb-android/app-strings/en/?checksum=e586b5d3bfa510df , but for some reason the strings.xml is not yet updated...

I think no functionality is affected, but with en_GB localization it is still displaying K-9 in the UI for the user agent setting, see
thunderbird-android/legacy/ui/legacy/src/main/res/values-en-rGB/strings.xml
Line 599 in 8668fab
Remove K-9 User-Agent from mail headers
It looks like there are also some other languages where this is still the case.

I marked translations for this string that included "K-9" as "needs editing" on Weblate just now.

This has been changed in weblate 5 moths ago: https://hosted.weblate.org/translate/tb-android/app-strings/en/?checksum=e586b5d3bfa510df , but for some reason the strings.xml is not yet updated...

We use American English as our source language. The identifier for that is "en" on Weblate. "en_GB" is the British English translation that hasn't been updated on Weblate (until I removed the translation just now because it should be identical to the source string).

Closing this issue because there's no code that needs changing.


Automatically Synchronize time

Description
It seems that if use the automatically synchronize time is enabled feature, it maxes out the processor usage,  my average usage is around 40% jumps to 97 odd...
Reproduction Steps

Configure device
Go to options
Select Automatically synchronize time
Save
Reload

Expected behavior
I assume this is not normal and shouldn't use this much processing power :)
If applicable, add error logs.
Happy to send a screenshot of system performance before and after
Device Firmware
C225 by TP-Link Firmware: 1.0.24 Build 230731 Rel.42636n
Using stream component
No
Does camera work via official integrations?
Yes
Camera has all attributes filled out in developer tools
Yes
HASS Environment
Docker with the integration
Search for similar issues
Yes
Additional information
Happy to supply any more information if needed.

Does this happen after restart as well? Provide debug logs and screenshots please as it does not happen to me so I cannot replicate it.

Hi @JurajNyiri
Thanks for the reply
See attached screenshot as requested.

Not sure if related but the logs have the below spamming , nothing else seems out of place. i'm going to try a few more combinations and see if i can get more information
2023-10-17 19:58:43.243 DEBUG (MainThread) [custom_components.tapo_control] [initOnvifEvents] Got device information.
2023-10-17 19:58:43.249 DEBUG (MainThread) [custom_components.tapo_control] setupOnvif - entry
2023-10-17 19:58:43.249 DEBUG (MainThread) [custom_components.tapo_control] Setting up onvif...
2023-10-17 19:58:43.249 DEBUG (MainThread) [custom_components.tapo_control] setupEvents - entry
2023-10-17 19:58:43.249 DEBUG (MainThread) [custom_components.tapo_control] Detected base_url schema: http
2023-10-17 19:58:43.250 DEBUG (MainThread) [custom_components.tapo_control] Detected base_url schema: http
2023-10-17 19:58:43.250 DEBUG (MainThread) [custom_components.tapo_control] Using HTTPS: False
2023-10-17 19:58:43.250 DEBUG (MainThread) [custom_components.tapo_control] Webhook enabled: False
2023-10-17 19:58:43.250 DEBUG (MainThread) [custom_components.tapo_control] Using Webhooks: False
2023-10-17 19:58:43.250 DEBUG (MainThread) [custom_components.tapo_control] Setting up events...
2023-10-17 19:58:43.250 DEBUG (MainThread) [custom_components.tapo_control] WSPullPointSupport: True
2023-10-17 19:58:43.384 DEBUG (MainThread) [custom_components.tapo_control] Events started.
2023-10-17 19:58:43.385 DEBUG (MainThread) [custom_components.tapo_control] Creating binary sensor entity.
2023-10-17 19:58:43.385 DEBUG (MainThread) [custom_components.tapo_control] Binary sensor creation for motion has been forwarded to component.
2023-10-17 19:58:59.175 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:58:59.826 DEBUG (MainThread) [custom_components.tapo_control] mediaSync
2023-10-17 19:59:01.097 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.098 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.098 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.098 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.098 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.099 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.099 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.099 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.099 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.099 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.099 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.099 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.100 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.100 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.100 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.101 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.101 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.101 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.101 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.101 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.101 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.101 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.102 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.102 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.102 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.102 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.102 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.102 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.102 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.102 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.103 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.103 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.123 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.123 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.123 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.123 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.124 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.124 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.124 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.124 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.124 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.124 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.124 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.124 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.125 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.125 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.125 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.125 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.125 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.125 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:01.125 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:03.422 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.
2023-10-17 19:59:03.423 DEBUG (MainThread) [custom_components.tapo_control] Debouncer call ignored as shutdown has been requested.

Closing due to inactivity.


API+basic buttons

basic access to api and also button and search bar on html

nice work tosin!!!


Request to add the files of demos of samjs website to repository

Hi, @yzg1025 @yzg1025, I am building an application to use SAM and I came across your package. It is really useful and has been of great help.
Since documentation is not available for your module can you please upload the code for your website demo page either in this repository or a new repository.
That would be much appreciated thank you.

https://github.com/antvis/SAMJS/tree/main/docs the demos


[tool_crash] SocketException: Send failed, OS Error: No route to host, errno = 65

Command
flutter run --machine --start-paused -d 00008110-00165C980122801E --devtools-server-address http://<IP_ADDRESS>:9100/ --target /Users/amirdora/Documents/Experimental/ai_calorie_tracker/lib/main.dart

Steps to Reproduce

...
...
...

Logs
SocketException: Send failed, OS Error: No route to host, errno = 65
#0      _NativeSocket.send (dart:io-patch/socket_patch.dart:1275:34)
#1      _RawDatagramSocket.send (dart:io-patch/socket_patch.dart:2590:15)
#2      MDnsClient.lookup (package:multicast_dns/multicast_dns.dart:219:22)
#3      MDnsVmServiceDiscovery._pollingVmService (package:flutter_tools/src/mdns_discovery.dart:236:36)
<asynchronous suspension>
#4      MDnsVmServiceDiscovery.firstMatchingVmService (package:flutter_tools/src/mdns_discovery.dart:189:56)
<asynchronous suspension>
#5      MDnsVmServiceDiscovery.getVMServiceUriForLaunch (package:flutter_tools/src/mdns_discovery.dart:452:50)
<asynchronous suspension>
#6      Future.any.onValue (dart:async/future.dart:614:5)
<asynchronous suspension>

[✓] Flutter (Channel stable, 3.27.1, on macOS 15.2 24C101 darwin-arm64, locale en-US)
    • Flutter version 3.27.1 on channel stable at /Users/amirdora/development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 17025dd882 (9 days ago), 2024-12-17 03:23:09 +0900
    • Engine revision cb4b5fff73
    • Dart version 3.6.0
    • DevTools version 2.40.2

[!] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
    • Android SDK at /Users/amirdora/Library/Android/sdk
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/to/macos-android-setup for more details.

[✓] Xcode - develop for iOS and macOS (Xcode 16.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 16C5032a
    • CocoaPods version 1.16.2

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

[✓] Android Studio (version 2024.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 21.0.3+-79915917-b509.11)

[✓] VS Code (version 1.96.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.102.0

[✓] Connected device (4 available)
    • iPhone-Amir (mobile)            • 00008110-00165C980122801E • ios            • iOS 18.1.1 22B91
    • macOS (desktop)                 • macos                     • darwin-arm64   • macOS 15.2 24C101 darwin-arm64
    • Mac Designed for iPad (desktop) • mac-designed-for-ipad     • darwin         • macOS 15.2 24C101 darwin-arm64
    • Chrome (web)                    • chrome                    • web-javascript • Google Chrome 131.0.6778.205

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

Flutter Application Metadata
Type: app
Version: 1.0.3+3
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version: 17025dd88227cd9532c33fa78f5250d548d87e9a
Plugins
file_selector_linux-0.9.3+2
file_selector_macos-0.9.4+2
file_selector_windows-0.9.3+3
flutter_plugin_android_lifecycle-2.0.24
image_picker-1.1.2
image_picker_android-0.8.12+19
image_picker_for_web-3.0.6
image_picker_ios-0.8.12+1
image_picker_linux-0.2.1+1
image_picker_macos-0.2.1+1
image_picker_windows-0.2.1+1
path_provider_linux-2.2.1
path_provider_windows-2.3.0
shared_preferences-2.3.4
shared_preferences_android-2.4.0
shared_preferences_foundation-2.5.4
shared_preferences_linux-2.4.1
shared_preferences_web-2.4.2
shared_preferences_windows-2.4.1

Closing this as a duplicate of https://github.com/flutter/flutter/issues/150131


Possible Error with TypeLiteralNode validation?

When using TypeGuards.isTypeLiteralNode the kinds that are being verified are different from the value actually passed.
TypeGuards.isTypeLiteralNode is checking against TypeLiteral which is kind 164 but the TypeLiteralNode kind is 174.
This may also affect TypeGuards.isTypeNode but not sure.
Or am I looking at it incorrectly?

Hey @kjpou1, LiteralType is 174 and TypeLiteral is 164. Very easy to mix them up! :) (Maybe I am mixing them up right now and not realizing...)
Here's the definition from the compiler for TypeLiteralNode and LiteralTypeNode:
export interface TypeLiteralNode extends TypeNode, Declaration {
    kind: SyntaxKind.TypeLiteral; // 164
    members: NodeArray<TypeElement>;
}

export interface LiteralTypeNode extends TypeNode {
    kind: SyntaxKind.LiteralType; // 174
    literal: BooleanLiteral | LiteralExpression | PrefixUnaryExpression;
}

Perhaps you mean to use TypeGuards.isLiteralTypeNode(...)?

@dsherret yes it looks like that was it !!!  Thanks for pointing that out.


Add EthereumChainID, TokenContract fields to burn/lock messages

This PR updates the initial burn and lock tendermint messages with 2 additional fields: EthereumChainID and TokenContract. The tests and README have been updated to reflect these changes.
Why have these fields been added?

TokenContract is required for the subsequent contract interaction initiated by validators running the Cosmos relayer. Once integrated, this will unblock https://github.com/cosmos/peggy/pull/77.
EthereumChainID is not currently required, but added so that going forward users can use the Bridge in a way that would handle two clashing tokens from different Ethereum chains.

you mean EthereumChainID :)

you mean EthereumChainID :)

I do indeed. Updated the PR title/description to match the code.

Besides for first comment on 'stake', looks good.
Also to note: This is related to https://github.com/cosmos/peggy/issues/69, which is a bigger issue around discussion Token metadata (like contract address, symbol and name duplication, etc) in the Cosmos SDK. If that were supported, we would want to use some kinda token metadata abstraction instead of a solution like this, but that can be looked into in future.


Deco's ladder changes

When ladders added in Deco are turned into items, they all become oak ladders.

Issues with deco should be posted to deco's repo: https://github.com/BTW-Community/Deco-Addon-2


Animate Dot That Appears On When ChartTooltip is Activated.

Is there a way to just animate the tooltip points that show on hover in the line chart? I want them to blink. Would also work if I am able to animate the last point of the chart because I am feeding data into the chart every second.
It would be a big help.
Thanks!

Something like that?

@kurkle, Thanks for taking an interest. I want just the dots to blink. I don't want to animate the lines and it should be an infinite animation.

https://codepen.io/kurkle/pen/WNwJvxv?editors=0110
https://www.chartjs.org/docs/master/configuration/animations

Thanks, @kurkle. That was really helpful


when to support read_sql？

postgres_scanner(pgscan) can query pg table directly, but only support table,
not like pandas,
df=pd.read_sql('select * from a join b on ...')

can pgscan support this?

This is already supported - see #128


fix(Designer): Changed test connection request to not run through batch api

Main Changes
Adjusted our connection test request function to not run the request through batch.
During my investigation, running some connector test requests through batch would fail specifically when going through the batch api, with no other changes in the request.
We have a catch over in the portal httpClient where if a request has any explicit headers set, it will not go through batch, so I've just added a dummy header for now.
Fixes https://github.com/Azure/LogicAppsUX/issues/3781

Can we just go ahead and remove batch API all together for now? It’s not batching by default anyway.

Can we just go ahead and remove batch API all together for now? It’s not batching by default anyway.

I'm fine with that as well, I can go ahead and make that change over in Portal


Enhancement: Enable static_lambda fixer

This PR

[x] enables the static_lambda fixer
[x] runs php-cs-fixer

💁♂ For reference, see https://github.com/FriendsOfPHP/PHP-CS-Fixer/tree/v2.15.1#usage:

static_lambda
Lambdas not (indirect) referencing $this must be declared static.
Risky rule: risky when using ->bindTo on lambdas without referencing to $this.

@localheinz This PR needs a rebase and/or rerun of php-cs-fixer against latest master :-)

@smoench
Rebased!

Thank you, @localheinz!

Thank you, @smoench!


Fix #399: url validation should fail when valid URL is only a substring

Fixes:
https://github.com/mikeerickson/validatorjs/issues/399

@zjmhungry thank you for the PR. I am going to reject this specific PR ONLY because I have already modified this rule to address another reported issue and will assure your issue is resolved as well before releasing final version in the coming days as I am preparing a bigger release for later this week.

Closed as part of our future release

@mikeerickson okay that sounds good. Thanks for the efforts!


fix merge conflicts in 'option to avoid computing possibly unused svd matrix'

The PR https://github.com/scipy/scipy/pull/4147 had merge conflicts with recent changes in the abstract linear operator interface, so I've manually resolved these in this PR.  The logic and tests should be the same as in the original PR.

Can you change the commits so that @nicolamontecchio is listed as the author (of the first one at least)? I think git commit --amend --author=X will do that.

@larsmans sorry I tried
$ git commit --amend --author=nicolamontecchio  156d2ce
but I got the output
fatal: No existing author found with 'nicolamontecchio'
I've searched this output on google and I'm not sure what is an acceptable way to deal with it.  Do you have any other suggestions, keeping in mind that I'm not a git pro?

Git requires an email address in the author name. If you don't know it,
using --author="nicolamontecchio nicolamontecchio@localhost" is
probably ok.

Looks like I screwed that up.

fwiw I used
$ git commit --amend --author="nicolamontecchio <nicolamontecchio@localhost>" -c 156d2ce
Then when I tried to push to this branch, git complained, so I added the -f flag.

@argriffing I tried my git-fu with https://github.com/ev-br/scipy/compare/pr/4147?expand=1
Does it look right? [I'm not sure in either my git-fu or my understanding of this code]

@ev-br Yes that looks good.  I guess you've made the changes from dot to matmat to resolve the conflict, and haven't messed with the style.  The git-fu of that PR is much better so if you add it as a new PR I'll close this one.

https://github.com/scipy/scipy/pull/4504
FWIW, what I did was
$ git fetch upstream
$ git checkout pr/4147   # this relies on some git magic I got from @rgommers
$ git rebase upstream/master   # the fun is here

This keeps the commit author, but yeah, I wonder what's the recommended way of doing three-way merge with git (I typically do git difftool, but I'm sure there is some better incantation)

this relies on some git magic I got from @rgommers

Thanks, I googled for 'git checkout pr` and found https://gist.github.com/piscisaureus/3342247 but I'm hesitant to use a non-vanilla git config until I'm more comfortable with git.

I think something along the lines of git remote add <their scipy fork> their_fork and git checkout their_fork/<their_branch> could work

git remote add argriffing https://github.com/argriffing/scipy.git
git fetch argriffing
git checkout argriffing/montecchio-partial-svd

is the "standard" way to grab someone else's stuff.

What about a PR like https://github.com/scipy/scipy/pull/3303 which does not use a separate branch and which conflicts with the scipy master branch?  I'd like to try to merge that, after (possibly temporarily) removing the axis-specific stuff and after fixing its brokenness with respect to complex-valued matrices.

master is not a special branch, the name is just a convention, so it works like the others.
You'd need to use git rebase upstream/master to resolve the merge conflict:
git remote add perryism https://github.com/perryism/scipy.git
git fetch perryism
git checkout -b pr-3303-fix perryism/master
git remote add upstream https://github.com/scipy/scipy.git
git fetch upstream
git rebase upstream/master
# 1.
# edit files with merge conflicts, see the message it prints and `git status`
# replace the parts between the <<< >>> markers with something sensible
git add scipy/sparse/data.py scipy/sparse/tests/test_base.py # mark conflicts resolved
git rebase --continue
# go to 1. until rebase is finished

Thanks, I'll try this.  It won't throw away the original authorship information or other meta-data that reviewers might want?

Rebase will leave the author as is, but will make you the "committer" because you last touched the commits.


Pool with lanes contains space (and elements in that area) that are not in lane

Describe the Bug
See attached diagram, is that standard conform? Even more, how to get rid of the "not in lane"-space of the pool?
Steps to Reproduce
Sorry, only got the failing diagram.
Expected Behavior
There should be no space in a pool that is not part of a lane (as long is there is at least one lane).
laneOrNoLane.bpmn.txt

See attached diagram, is that standard conform?

I guess. Lanes have no strictly defined semantics.

There should be no space in a pool that is not part of a lane (as long is there is at least one lane).

If you're able to create this diagram with the Camunda Modeler it is a bug. In that case we'd need concrete steps to reproduce this issue

Even more, how to get rid of the "not in lane"-space of the pool?

Simply resize the middle lane to take up all the space. Then you'll be able to split it up again.

See attached diagram, is that standard conform?

I guess. Lanes have no strictly defined semantics.

There should be no space in a pool that is not part of a lane (as long is there is at least one lane).

If you're able to create this diagram with the Camunda Modeler it is a bug. In that case we'd need concrete steps to reproduce this issue

Even more, how to get rid of the "not in lane"-space of the pool?

Simply resize the middle lane to take up all the space. Then you'll be able to split it up again.

See attached diagram, is that standard conform?

I guess, lanes don't really have strict semantics.

Even more, how to get  rid of the "not in lane"-space of the pool?

Resize the second lane to take all open space. Split it afterwards into two to restore the old behavior.


Add SpaceX Exploration Expansion HD by LazTek from Kerbal Stuff

This pull request was automatically generated by Kerbal Stuff on behalf of Lazarus, to add SpaceX Exploration Expansion HD by LazTek to CKAN.
Please direct questions about this pull request to Lazarus.

Closing in favour of https://github.com/KSP-CKAN/NetKAN/pull/589


scripts: mask systemd-networkd-wait-online.service

Every time when docker.service runs, it waits for 120 seconds doing nothing, until systemd-networkd-wait-online.service times out. As a result, kubeadm is being blocked until docker server became available: a huge delay for every nspawn container, although network is already online and reachable.
Let's just mask systemd-networkd-wait-online.service, to allow docker.service to run without being blocked.
Fixes https://github.com/kinvolk/kube-spawn/issues/75

Also added a line to set password for non-root user "core".

I'll merge it as it's simple but necessary bugfixes.


Enter- Key does not insert

First of all i have to say thank you  for this marvellous tool.
I currently try to create an Controll- Addin, where the current version of the editor is part of Windows- form that allows to use a JavScript as control.
I got this working until the point, where i press the Enter-key (Numpad or Normal) in the textarea.
I would expect, that pressing Enter inserts a new Line in the text, but nothing happens.
Because i do not have a JavaScript console available, i inserted some different logging.
Until now I found out that the Enter-Key fires a KeyDown- event with expected!? values and that pressing CTRL+M creates the NewLine as expected.
What am i able to do, to find out where the problem occurs?
I also have to say that i am not a JavaScript- native,😥 so i would need perhaps some more explanation.

Please tell me more detail.
I do not understand well. 😢

As i wrote above, i have a windows form that includes your editor as javacript crontol-addin.
SunEditor is initialized by the attached script. When the form is shown as in the picture, all works fine except the ENTER-key. When i use Suneditor in a WEB-page, ENTER inserts a , but not here, where only Ctrl+M or Shift+ENTER insert a !?
So as i don't think that is a real bug in the editor, i need a hint where to grab some information why ENTER is not working.
Script_js.txt

https://github.com/JiHong88/SunEditor/blob/master/src/lib/core.js#L6763
The operation when entering the Enter key (key code 13) is performed here.
PS:
"lang(In nodejs)": "de"
This is not a real option.
you don't have to


Desync since keyframe boost

According to git bisect:
00b17caca4d690b9caaf35b52b843ce5d82b49f1 is the first bad commit
commit 00b17caca4d690b9caaf35b52b843ce5d82b49f1
Author: Frank Bossen<EMAIL_ADDRESS>Date:   Wed Sep 5 19:26:21 2018 -0400

    Boost quantizer on key frames

I'm getting a desync:
~/rav1e$ SEQ=/derf-media/subset1/Air_Force_Academy_Chapel,_Colorado_Springs,_CO_04090u_original.y4m ./build.sh
   Compiling rav1e v0.1.0 (file:///home/tmatth/rav1e)
warning: redundant linker flag specified for library `m`

warning: redundant linker flag specified for library `pthread`

    Finished release [optimized] target(s) in 8.99s
     Running `target/release/rav1e /derf-media/subset1/Air_Force_Academy_Chapel,_Colorado_Springs,_CO_04090u_original.y4m -o enc_file.ivf -s 3 -r rec_file.y4m`
Frame 0 - Key frame
/dev/fd/63 /dev/fd/62 differ: byte 987560, line 2

Depends on the input file as well as the value of q_boost, e.g. 14 instead of 15 doesn't desync on Air Force.

This might be related to initial CDF selection.

This doesn't seem to be a quantizer boost issue. Also getting a mismatch with c1b5dceda9ca8e95eead581c41b9a77d31748e7c (previous commit) when using --quantizer=85

Looks more like an issue from interaction between the deblocking filter, CDEF, and odd frame sizes (in the example the frame width is 858 = 107*8+2. When switching off either deblocking or CDEF there is no mismatch

@fbossen yeah that makes sense, the boost commit just exposed the issue.

Moved to #554


[demo] fill from query string

this would let you share whatever you're translating with a single link
ie https://bullg.it/blah-code/?lang=blah&to=encrypt&q=test+123+👌
or something similar.
Useful would be to add a button or a field which shows the current url in the page itself

Good idea. Man. You’re on :fire:


Understand aa-common-service repo and create a google doc with understandings and questions

[ ] Created the google document
[ ] Understood the document
[ ] Added the key points into document
[ ] Mentioned questions

https://docs.google.com/document/d/1WPk3Y2W_Vii6FwLhDjhmv0m0M9Tg15QTllzfDXyzEiE/edit

https://docs.google.com/document/d/1WPk3Y2W_Vii6FwLhDjhmv0m0M9Tg15QTllzfDXyzEiE/edit


[17.06] Backport cgroup namespace support

This replaces #6 to have cgroup namespace support in 17.06.
First 5 commits are aux build and CI fixes, as it looks like CI was utterly broken. While CI it useful, it's not absolutely required here and can be split out to a separate PR.
 Due to code changes were there many hunks not applied or, worse, applied with the wrong context (especially in nsexec.c), so most of the code changes were applied manually.

Rebased to current 17.06 tip

@andrewhsu @crosbymichael PTAL

LGTM


Update README for permanent install

Also update flake.nix a bit to only support Linux (Macs are supported natively anyway).

Lgtm, thanks!


Specifying Dynamic Class Does not Render icons

I have:
<script setup lang="ts">
const iconClass = `i-symbol:${props.icon}`
</script>

Then in template:
<i :class="[iconClass]" text-10 />
Icons do not render. Sometimes one of them does (of a group of 5) which is strange. Also if I render the icons with hardcoded names first either on the same page or some other page, they do  display  (probably using a cached icon)
Vue 3
Vitesse template with updated deps ("unocss": "^0.32.13")

https://github.com/unocss/unocss#safelist


[WIP]Adding testcases for all commentcommand parsers

Pull Request Test Coverage Report for Build 1014

15 of 15 (100.0%)  changed or added relevant lines in 6 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+3.5%) to 85.419%

Files with Coverage Reduction
New Missed Lines
%

src/main/java/seedu/address/logic/commands/AddCommentCommand.java
1
38.46%

Totals

Change from base Build 1011:
3.5%

Covered Lines:
2150

Relevant Lines:
2517

💛  - Coveralls


Disable/Enable Scaffolder NEXT STEP Button

Hi,
Is it possible to control enabling/disabling the NEXT STEP Button in Scaffolder Page based on user inputs to the fields?

Not sure if this is supported out of the box in rjsf - do you mean that you want to control this based on schema validity of the current page's data, or something else?
Either way I think this might mean needing some implementation work if it were to become supported. Is this something you might be interested in looking into?

Opening this one again 🙏🏼
is this possible in 2024?
We have a step with a custom UI component, while fetching data (loading) we should not allow the user to proceed to next step.
is it possible to control it?


No error is returned from lightpush if a peer is full

This is a feature or change request
Problem
I ran into a problem that I had a peer that had a full disk and lightPush.send returned no error, but the data returned from store.queryGenerator was empty.
More specifically there were no errors in SendResult, and the peer was in recipients.
Proposed Solutions
It would be better to return either REMOTE_PEER_FAULT or REMOTE_PEER_REJECTED if the peer is full and cannot store data. I haven't checked the code, but most likely this issue affects not only js-waku but also nwaku (and possibly go-waku as well).
Notes

js-waku version: "@waku/sdk": "^0.0.20"
Environment (browser software and version, system software and version): Firefox & Chromium on Linux
Nodes connected to: nwaku 0.21.1

Is the full disk on nwaku side or nodejs side?

On the nwaku side.

@waku-org/nwaku-developers happy if I transfer the issue over?
@agazso do you have logs for nwaku? waht DB did you use ? SQlite or PostgreSQL:?

@agazso do you have logs for nwaku? waht DB did you use ? SQlite or PostgreSQL:?

Not sure if I still have the logs. The DB is Sqlite.

Transferring issue to nwaku repo.

Closing in favor of https://github.com/waku-org/nwaku/issues/2335


Fix ruff action

Updates ruff action to maintained version, see #92  as currently used one is not maintained anymore.
Maybe fixes the broken dependency on most current ruff, #92.

version 1 is still not compatible with ruff 5. Version 2 might be.


Release version 2.3.0

This is a component issue for 2.3.0.
Coming from opensearch-build#2447. Please follow the following checklist.
Please refer to the DATES in that post.
How to use this issue

This Component Release Issue
This issue captures the state of the OpenSearch release, on component/plugin level; its assignee is responsible for driving the release. Please contact them or @mention them on this issue for help.
Any release related work can be linked to this issue or added as comments to create visiblity into the release status.
Release Steps
There are several steps to the release process; these steps are completed as the whole component release and components that are behind present risk to the release. The component owner resolves the tasks in this issue and communicate with the overall release owner to make sure each component are moving along as expected.
Steps have completion dates for coordinating efforts between the components of a release; components can start as soon as they are ready far in advance of a future release. The most current set of dates is on the overall release issue linked at the top of this issue.
The Overall Release Issue
Linked at the top of this issue, the overall release issue captures the state of the entire OpenSearch release including references to this issue, the release owner which is the assignee is responsible for communicating the release status broadly.  Please contact them or @mention them on that issue for help.
What should I do if my plugin isn't making any changes?
If including changes in this release, increment the version on 2.x branch to 2.3.0 for Min/Core, and <IP_ADDRESS> for components. Otherwise, keep the version number unchanged for both.

Preparation

[ ] Assign this issue to a release owner.
[ ] Finalize scope and feature set and update the Public Roadmap.
[ ] All the tasks in this issue have been reviewed by the release owner.
[ ] Create, update, triage and label all features and issues targeted for this release with v2.3.0.

CI/CD

[ ] All code changes for 2.3.0 are complete.
[ ] Ensure working and passing CI.
[ ] Check that this repo is included in the distribution manifest.

Pre-Release

[ ] Update to the 2.3 release branch in the distribution manifest.
[ ] Increment the version on the parent branch to the next development iteration.
[ ] Gather, review and publish release notes following the rules and back port it to the release branch.git-release-notes may be used to generate release notes from your commit history.
[ ] Confirm that all changes for 2.3.0 have been merged.
[ ] Add this repo to the manifest for the next developer iteration.

Release Testing

[ ] Find/fix bugs using latest tarball and docker image provided in parent release issue and update the release notes if necessary.
[ ] Code Complete: Test within the distribution, ensuring integration, backwards compatibility, and performance tests pass.
[ ] Sanity Testing: Sanity testing and fixing of critical issues found.
[ ] File issues for all intermittent test failures.

Release

[ ] Complete documentation.
[ ] Verify all issued labeled for this release are closed or labelled for the next release.

Post Release

[ ] Prepare for an eventual security fix development iteration by incrementing the version on the release branch to the next eventual patch version.
[ ] Add this repo to the manifest of the next eventual security patch version.
[ ] Suggest improvements to this template.
[ ] Conduct a retrospective, and publish its results.

Hi @penghuo ,
The release notes are missing for this component in 2.3 branch.
You can see the checklist here https://github.com/opensearch-project/opensearch-build/issues/2447#issuecomment-1242457653

I see issue #743 tagged with v2.3.0. Can you close or update the tag accordingly?
Thanks!

@penghuo @anirudha  I am closing this issue since we released 2.3.0 already but I would request you to keep this issue up to date during release and close it on time going forward. Make sure to add any retrospective learning on this issue as well.


Move native modules into single directory

The native modules are in the root of Iris but they aren't contained within a folder.
fs-mod may not be the only native module, so it would be preferred to have a folder containing all native modules for easier access.
For example, this is what the directory could look like
native-modules/fs-mod
native-modules/fs-utils
native-modules/util

Note that rust-analyzer is a bit finicky with workspace paths.
If everything resides in the root, your Cargo.toml will have this
[workspace]
members = ["./"]

For now, put all the native modules in the root of Iris so rust-analyzer won't have detection issues.


docker-compose up throws errors and app doesn't start

This looks similar to #153 . But the logs aren't exactly the same.
Here's the log :
Creating mailforgood_redis_1
Creating mailforgood_postgres_1
Creating mailforgood_app_1
Attaching to mailforgood_redis_1, mailforgood_postgres_1, mailforgood_app_1
redis_1     | 1:C 16 Jul 04:06:35.911 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
postgres_1  | The files belonging to this database system will be owned by user "postgres".
postgres_1  | This user must also own the server process.
postgres_1  |
postgres_1  | The database cluster will be initialized with locale "en_US.utf8".
postgres_1  | The default database encoding has accordingly been set to "UTF8".
postgres_1  | The default text search configuration will be set to "english".
redis_1     |                 _._
redis_1     |            _.-``__ ''-._
redis_1     |       _.-``    `.  `_.  ''-._           Redis 3.2.9 (00000000/0) 64 bit
redis_1     |   .-`` .-```.  ```\/    _.,_ ''-._
redis_1     |  (    '      ,       .-`  | `,    )     Running in standalone mode
redis_1     |  |`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379
redis_1     |  |    `-._   `._    /     _.-'    |     PID: 1
redis_1     |   `-._    `-._  `-./  _.-'    _.-'
postgres_1  |
redis_1     |  |`-._`-._    `-.__.-'    _.-'_.-'|
redis_1     |  |    `-._`-._        _.-'_.-'    |           http://redis.io
postgres_1  | Data page checksums are disabled.
postgres_1  |
postgres_1  | fixing permissions on existing directory /var/lib/postgresql/data ... ok
redis_1     |   `-._    `-._`-.__.-'_.-'    _.-'
redis_1     |  |`-._`-._    `-.__.-'    _.-'_.-'|
redis_1     |  |    `-._`-._        _.-'_.-'    |
redis_1     |   `-._    `-._`-.__.-'_.-'    _.-'
redis_1     |       `-._    `-.__.-'    _.-'
redis_1     |           `-._        _.-'
postgres_1  | creating subdirectories ... ok
redis_1     |               `-.__.-'
redis_1     |
redis_1     | 1:M 16 Jul 04:06:35.912 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
redis_1     | 1:M 16 Jul 04:06:35.912 # Server started, Redis version 3.2.9
postgres_1  | selecting default max_connections ... 100
redis_1     | 1:M 16 Jul 04:06:35.912 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis_1     | 1:M 16 Jul 04:06:35.912 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
redis_1     | 1:M 16 Jul 04:06:35.912 * The server is now ready to accept connections on port 6379
postgres_1  | selecting default shared_buffers ... 128MB
postgres_1  | selecting dynamic shared memory implementation ... posix
postgres_1  | creating configuration files ... ok
postgres_1  | running bootstrap script ... ok
app_1       | npm info it worked if it ends with ok
app_1       | npm info using<EMAIL_ADDRESS>app_1       | npm info using<EMAIL_ADDRESS>app_1       | npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>app_1       | npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>app_1       |
app_1       | ><EMAIL_ADDRESS>start /usr/src/app
app_1       | > NODE_ENV=production ./node_modules/pm2/bin/pm2 start server/index.js --node-args=server/feedback-consumer/consumer.js --no-daemon
app_1       |
app_1       |
app_1       |                         -------------
app_1       |
app_1       | __/\\\\\\\\\\\\\____/\\\\____________/\\\\____/\\\\\\\\\_____
app_1       |  _\/\\\/////////\\\_\/\\\\\\________/\\\\\\__/\\\///////\\\___
app_1       |   _\/\\\_______\/\\\_\/\\\//\\\____/\\\//\\\_\///______\//\\\__
app_1       |    _\/\\\\\\\\\\\\\/__\/\\\\///\\\/\\\/_\/\\\___________/\\\/___
app_1       |     _\/\\\/////////____\/\\\__\///\\\/___\/\\\________/\\\//_____
app_1       |      _\/\\\_____________\/\\\____\///_____\/\\\_____/\\\//________
app_1       |       _\/\\\_____________\/\\\_____________\/\\\___/\\\/___________
app_1       |        _\/\\\_____________\/\\\_____________\/\\\__/\\\\\\\\\\\\\\\_
app_1       |         _\///______________\///______________\///__\///////////////__
app_1       |
app_1       |
app_1       |          Welcome to most Advanced Process Manager for Node.js
app_1       |
app_1       |                           Monitoring
app_1       |                         $ pm2 monitor
app_1       |
app_1       |                       Start PM2 at boot
app_1       |                         $ pm2 startup
app_1       |
app_1       |                      Increase Performance
app_1       |                     $ pm2 start api.js -i 4
app_1       |
app_1       |                         -------------
app_1       |
app_1       | pm2 launched in no-daemon mode (you can add DEBUG="*" env variable to get more messages)
postgres_1  | performing post-bootstrap initialization ... ok
app_1       | 2017-07-16 04:06:38: Launching in no daemon mode
app_1       | 2017-07-16 04:06:38: [PM2] Starting /usr/src/app/server/index.js in fork_mode (1 instance)
app_1       | 2017-07-16 04:06:38: Starting execution sequence in -fork mode- for app name:index id:0
app_1       | 2017-07-16 04:06:38: App name:index id:0 online
app_1       | 2017-07-16 04:06:39: [PM2] Done.
app_1       | 2017-07-16 04:06:39: ┌──────────┬────┬──────┬─────┬────────┬─────────┬────────┬─────┬───────────┬──────────┐
app_1       | │ App name │ id │ mode │ pid │ status │ restart │ uptime │ cpu │ mem       │ watching │
app_1       | ├──────────┼────┼──────┼─────┼────────┼─────────┼────────┼─────┼───────────┼──────────┤
app_1       | │ index    │ 0  │ fork │ 27  │ online │ 0       │ 0s     │ 5%  │ 25.2 MB   │ disabled │
app_1       | └──────────┴────┴──────┴─────┴────────┴─────────┴────────┴─────┴───────────┴──────────┘
app_1       | 2017-07-16 04:06:39:  Use `pm2 show <id|name>` to get more details about an app
app_1       | 2017-07-16 04:06:39: [--no-daemon] Continue to stream logs
app_1       | 2017-07-16 04:06:39: [--no-daemon] Exit on target PM2 exit pid=17
app_1       | 2017-07-16 04:06:39: [STREAMING] Now streaming realtime logs for [all] processes
postgres_1  | syncing data to disk ...
postgres_1  | WARNING: enabling "trust" authentication for local connections
postgres_1  | You can change this by editing pg_hba.conf or using the option -A, or
postgres_1  | --auth-local and --auth-host, the next time you run initdb.
postgres_1  | ok
postgres_1  |
postgres_1  | Success. You can now start the database server using:
postgres_1  |
postgres_1  |     pg_ctl -D /var/lib/postgresql/data -l logfile start
postgres_1  |
postgres_1  | ****************************************************
postgres_1  | WARNING: No password has been set for the database.
postgres_1  |          This will allow anyone with access to the
postgres_1  |          Postgres port to access your database. In
postgres_1  |          Docker's default configuration, this is
postgres_1  |          effectively any other container on the same
postgres_1  |          system.
postgres_1  |
postgres_1  |          Use "-e POSTGRES_PASSWORD=password" to set
postgres_1  |          it in "docker run".
postgres_1  | ****************************************************
postgres_1  | waiting for server to start....LOG:  could not bind IPv6 socket: Cannot assign requested address
postgres_1  | HINT:  Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
app_1       | 04:06:39 0|index    | Feedback consumer started: watching for feedback messages (bounces, complaints, etc) from SQS
app_1       | 04:06:39 0|index    | Unhandled rejection SequelizeBaseError: connect ECONNREFUSED <IP_ADDRESS>:5432
app_1       | 04:06:39 0|index    |     at /usr/src/app/node_modules/sequelize/lib/dialects/postgres/connection-manager.js:98:20
app_1       | 04:06:39 0|index    |     at Client.<anonymous> (/usr/src/app/node_modules/pg/lib/client.js:203:5)
app_1       | 04:06:39 0|index    |     at emitOne (events.js:96:13)
app_1       | 04:06:39 0|index    |     at Connection.emit (events.js:191:7)
app_1       | 04:06:39 0|index    |     at Socket.<anonymous> (/usr/src/app/node_modules/pg/lib/connection.js:86:10)
app_1       | 04:06:39 0|index    |     at emitOne (events.js:96:13)
app_1       | 04:06:39 0|index    |     at Socket.emit (events.js:191:7)
app_1       | 04:06:39 0|index    |     at emitErrorNT (net.js:1279:8)
app_1       | 04:06:39 0|index    |     at _combinedTickCallback (internal/process/next_tick.js:80:11)
app_1       | 04:06:39 0|index    |     at process._tickDomainCallback (internal/process/next_tick.js:128:9)
postgres_1  | LOG:  database system was shut down at 2017-07-16 04:06:38 UTC
postgres_1  | LOG:  MultiXact member wraparound protections are now enabled
postgres_1  | LOG:  database system is ready to accept connections
postgres_1  | LOG:  autovacuum launcher started
postgres_1  |  done
postgres_1  | server started
postgres_1  | ALTER ROLE
postgres_1  |
postgres_1  |
postgres_1  | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
postgres_1  |
postgres_1  | LOG:  received fast shutdown request
postgres_1  | LOG:  aborting any active transactions
postgres_1  | waiting for server to shut down...LOG:  autovacuum launcher shutting down
postgres_1  | .LOG:  shutting down
postgres_1  | LOG:  database system is shut down
postgres_1  |  done
postgres_1  | server stopped
postgres_1  |
postgres_1  | PostgreSQL init process complete; ready for start up.
postgres_1  |
postgres_1  | LOG:  database system was shut down at 2017-07-16 04:06:41 UTC
postgres_1  | LOG:  MultiXact member wraparound protections are now enabled
postgres_1  | LOG:  database system is ready to accept connections
postgres_1  | LOG:  autovacuum launcher started

And the app doesn't start, as in, I am not able to http://<IP_ADDRESS>:8080

Looking into this, seems the project at Docker Hub is not updating https://hub.docker.com/r/freecodecamp/mail-for-good/.

@AndrewGHC Oh


specialization

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 36 (5.56%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-4.09%) to 72.598%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

writer.go
1
17
5.88%

reader.go
1
19
5.26%

Totals

Change from base Build<PHONE_NUMBER>:
-4.09%

Covered Lines:
408

Relevant Lines:
562

💛  - Coveralls


Add style classes for border and text decoration

Prerequisites

[X] I have searched for duplicate or closed feature requests
[X] I have read the contributing guidelines

Proposal
"smarty" style classes: '.double' '.dotted' '.dashed'.
if style class added to element with class .text-decoration-underline or .text-decoration-line-through, then change text-decoration-style, else, border-style.
or "utility":
Border style classes (change border-style): '.border-double' '.border-dotted' '.border-dashed'
Text decoration style classes (change text-decoration-style): '.text-decoration-double' '.text-decoration-dotted' '.text-decoration-dashed'.
Motivation and context
We already have have utilities for border and decoration of text, but can't change decoration/border style by that's utilities

I would like to work on this issue.

@amankumar11 What you mean? Sending PR adding something like this:
    "border-style": (
      property: border-style,
      class: border,
      values: double dotted dashed
    ),
    "text-decoration-style": (
      property: text-decoration-style,
      class: text-decoration,
      values: double dotted dashed
    ),

to scss/_utilities.scss?

Yes

We'll pass on this for now as the Utility API exists for this very reason.

@mdo

"smarty" style classes: '.double' '.dotted' '.dashed'.
if style class added to element with class .text-decoration-underline or .text-decoration-line-through, then change text-decoration-style, else, border-style.


Add Basque language translation

Basque XLIFF language files added, and config.yml updated.

Great! Thanks Asier for contributing a new translation for this project!
Eskerrik asko


Show notification for ie and edge separately as they have different version

How to show notifications for ie and edge separately as they have different versions
is beta version is the latest version this plugin consider?

Ok. I will implement the option to treat them differently soon.
No. We consider the latest stable version (EdegeHTML 15)

I'd definitely use and love this too.  Our platform supports only IE11 and the latest version 2 versions of Edge, being able to notify on this separately from IE11 would be helpful.

This works now, see:
http://browser-update.org/blog/18_notify_outdated_ie_and_edge_separately/
I've been busy with a complete rewrite of the site so it took me some time.

Great thanks
On Tue, May 8, 2018, 8:29 PM josselex<EMAIL_ADDRESS>wrote:

This works now, see:
http://browser-update.org/blog/18_notify_outdated_ie_and_edge_separately/
I've been busy with a complete rewrite of the site so it took me some time.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/browser-update/browser-update/issues/367#issuecomment-387432382,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Af8avhKIqeZPxzBkS63DFhjIDyZXrm-iks5twbLYgaJpZM4QW1Wr
.

Fantastic, thank you!!


youtube_dl.utils.RegexNotFoundError: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure

$ youtube-dl --proxy="socks5://<IP_ADDRESS>:7890" --verbose 'https://youtu.be/qodoWBn58-s'
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--proxy=socks5://<IP_ADDRESS>:7890', '--verbose', 'https://youtu.be/qodoWBn58-s']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2021.12.17
[debug] Python version 3.10.10 (CPython) - macOS-13.3-x86_64-i386-64bit
[debug] exe versions: ffmpeg 5.1.2, ffprobe 5.1.2, rtmpdump 2.4
[debug] Proxy map: {'http': 'socks5://<IP_ADDRESS>:7890', 'https': 'socks5://<IP_ADDRESS>:7890'}
[youtube] qodoWBn58-s: Downloading webpage
ERROR: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/usr/local/Cellar/youtube-dl/2021.12.17/libexec/lib/python3.10/site-packages/youtube_dl/YoutubeDL.py", line 815, in wrapper
    return func(self, *args, **kwargs)
  File "/usr/local/Cellar/youtube-dl/2021.12.17/libexec/lib/python3.10/site-packages/youtube_dl/YoutubeDL.py", line 836, in __extract_info
    ie_result = ie.extract(url)
  File "/usr/local/Cellar/youtube-dl/2021.12.17/libexec/lib/python3.10/site-packages/youtube_dl/extractor/common.py", line 534, in extract
    ie_result = self._real_extract(url)
  File "/usr/local/Cellar/youtube-dl/2021.12.17/libexec/lib/python3.10/site-packages/youtube_dl/extractor/youtube.py", line 1794, in _real_extract
    'uploader_id': self._search_regex(r'/(?:channel|user)/([^/?&#]+)', owner_profile_url, 'uploader id') if owner_profile_url else None,
  File "/usr/local/Cellar/youtube-dl/2021.12.17/libexec/lib/python3.10/site-packages/youtube_dl/extractor/common.py", line 1012, in _search_regex
    raise RegexNotFoundError('Unable to extract %s' % _name)
youtube_dl.utils.RegexNotFoundError: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

#30839 !


HealthCheckRequest should have a flag for specifying calling server

We want to have an optional field to identify which server is calling service's health check. This is useful for multi-client services :D

Can you use a metadata header?


Need: bacalhau approve --list

List all nodes that are awaiting approving

We could (should) do this as a filter on list.  See https://github.com/bacalhau-project/bacalhau/issues/3683


Dependency injection and tests in the new framework

Changes proposed ✍
What

🤖 Generated by Copilot at f9840b2
This pull request improves the integration with Discourse forums, adds a new feature to install dependencies from the command line, updates some service dependencies and scripts, and simplifies the Dockerfile for the script executor service.

🤖 Generated by Copilot at f9840b2

We're building the script executor, me hearties, yo ho
We're cloning and installing the crowd.dev repo
We're adding new features and fixing bugs, me lads and lasses, yo ho
We're running the trigger-webhook script on the count of three

Why
How

🤖 Generated by Copilot at f9840b2

Add script to trigger webhook for testing purposes to backend/package.json (link)
Add conditions to check if user is defined before proceeding with Discourse integration operations in discourseIntegrationService.ts (link, link, link)
Modify return type, encode url parameter and handle 404 error response in getUser.ts (link, link, link)
Add function to install backend and services libraries dependencies and handle install-backend-libs argument in scripts/cli (link, link)
Replace content of Dockerfile.script_executor with simplified Dockerfile using node:16-alpine base image and installing necessary packages and libraries (link)
Add command-line-args and command-line-usage dependencies and name properties to ../../libs dependencies in integration_stream_worker/package.json and package-lock.json (link, link, link, link, link, link, link, link, link, link, link, link)
Remove dev properties, add new dependencies and avoid duplication of dependencies in integration_stream_worker/package-lock.json (link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link)

Checklist ✅

[x] Label appropriately with Feature, Improvement, or Bug.
[ ] ~Add screehshots to the PR description for relevant FE changes~
[x] New backend functionality has been unit-tested.
[ ] ~API documentation has been updated (if necessary) (see docs on API documentation).~
[x] Quality standards are met.

I'll put the comment here to start a discussion.
Thanks for all this effort Uroš, I have a couple issues though:

I'm still not sure how to review the PR, there are so many changes
It would've been much easier to review it if the changes were split into several reasonable commits, each having a specific purpose with an explanation (i.e. Remove build step from libs, Add basic IOC setup, Migrate all classes to the IOC framework)
It seems like there are still two separate things: no build step for libraries, and ioc. Can we split the PR even further?
Skeptical a bit about ioc. I think it adds too much complexity, and we're getting too close to java. I'm afraid instead of creating features we'll be creating interfaces and binding implementation to them.

I'll put the comment here to start a discussion.
Thanks for all this effort Uroš, I have a couple issues though:

I'm still not sure how to review the PR, there are so many changes
It would've been much easier to review it if the changes were split into several reasonable commits, each having a specific purpose with an explanation (i.e. Remove build step from libs, Add basic IOC setup, Migrate all classes to the IOC framework)
It seems like there are still two separate things: no build step for libraries, and ioc. Can we split the PR even further?
Skeptical a bit about ioc. I think it adds too much complexity, and we're getting too close to java. I'm afraid instead of creating features we'll be creating interfaces and binding implementation to them.

I'll split the PR into two - DI and no lib building.
As for your 4th point:

I think that DI will help with testing and scripting:

we will be able to inject custom script classes instead of predefined service classes like sqs emitters for example
as for the complexity - library code is getting more complex and with the plan to use library and service code in other applications this will help with that - user will be able to more easily initialize the library code and have it ready wherever we need it
I would argue on the contrary - it decreases complexity for the developer:

he doesn't need to know the initialization steps for the library components
he doesn't need to refactor multiple files if he want's to get a certain component into his constructor
inversify offers explicit bindings/mappings unlike some DI systems - I also dislike Java/Spring style DI but this one I like because it's not just wiring things seemingly like magic - it's explicit

argument that we are too close to Java doesn't really hold IMO - Java has been an enterprise solution used for decated before NodeJS came knocking - it's one of the most stable languages/ecosystems there are - if you are implying Java with Spring as DI then yes I can relate - I dislike that a lot as well :)

@sausage-todd - PR for no lib building


serialization and custom hyperparam tests for datasets

PR to add

tests for serialization/deserialization of BeepDataset class
tests for dataset generation from processed_cycler_run objects with custom hyperparam sets. For instance, RPTdQdVFeatures can be generated for the different rpt cycles in the same dataset.

@BruisVanVlijmen2020 : this is just the unit-test to ensure dataset generation from processed cycler run works as expected, even when we generate objects of the same featurizer with different  hyperparam combinations. I will, however, use your suggestion for the dataset i generate on the beep-stage instance for building/training EP models


⚠ Badges API Endpoint has degraded performance

In 0a8bb1f, Badges API Endpoint (https://badges.roblox.com/v1/badges/2124548403) experienced degraded performance:

HTTP code: 200
Response time: 5326 ms

Resolved: Badges API Endpoint performance has improved in 94b378b.


Release 1.0.6

@MatthewCaseres  Think we're ready for releasing v1.0.6 to pypi soon, capturing all the latest changes.

[ ] I'm adding a template/example generator 'make_example' which can set up a few examples for users. (I'm going to use them for demos/getting started)
[ ] I've added you as an author in pyproject.toml - please set email if you want it :)

Anything else to add?

I'd like to close out #9 and start using proper release notes but I can't upload to pypi so it seems like you'll have to do that one?
Another note is that we are not abiding by the rules of semantic versioning. If you had not released v1.0.0 then we would not be breaking the rules. And we still might ship more breaking changes (unless we are certain we won't) so it is a funny spot to be in from perspective of semver https://semver.org/

I've still to read (and understand) the automated building, I've got hatch set up which does it all on my own machine for now.
SemVer: Agree - I wasn't aware of semantic versioning when I first released.  I think we're pretty safe to go for it as 1.0.6 and then run semver on that going forward:

not many people using the library yet (I suspect just me & you)
breaking changes aren't really breaking, e.g. I've got a Warning on do_run, and .ToDataFrame() isn't removed yet in favour of .df property.
can caveat in readme.

API wise, it feels like I've got what I want in heavylight.Model, we probably need to look at consistency between that and the optimised versions though.  heavylight.Table still needs a bit of thinking on API - for now I'm leaving it as opinionated on having metadata encoded in the column names (|int, etc.)
(I could yank the current versions from pypi, and put in at 0.2.0 but it might cause other problems.)

I've put in PR but tests fail for 3.8, 3.9 due to path: str|pathlib.Path not being recognised.  I'll probably just drop the type hints here for now.  Need to sleep now, so probably easier to merge and then fix in main.

No rush lets wait on merging for another day, type signatures in user facing functions is usually nice. gives me some time to review

I went ahead and merged it after writing a test and changing some code style but not the substance

Thank you!  Would yo9u like to add your email address to pyproject.toml (https://github.com/lewisfogden/heavylight/blob/main/pyproject.toml) and then I'll publish to pypi?

its changed

Fab - we're live with 1.0.6:  https://pypi.org/project/heavylight/1.0.6/ (Just running post-live checks now using a new colab environment)

All good!


Sak 30767

So what it looks like the problem here is, if the user has more than one submission (somehow?!?) and they don't have permission for one of them, it's not going to be able to return it. I'm not 100% sure how this can happen but we are seeing it happen on occasion. I moved the check for if the user is allowed up into the while loop and added a lot more debugging.


Oauth and grant permission for Kaoto

Automatically grant permissions for creating resources (kamelets,kamelet-bindings) according openshift logged user.

not more in scope


Compilation error on llama 7 B with batch size 8

When trying to compile llama 7B with:

batch_size: 8,
n_positions: 2048,
tp_degree: 24,
auto_cast_type: f16.

Hi dacorvo - we have been able to reproduce your issue and are working on a solution.  The model compiled successfully; the issue is with loading the model onto the device for execution.

Same issue with Zephyr: https://huggingface.co/aws-neuron/optimum-neuron-cache/discussions/3

Now closed.


Account creation is broken

So when you run the bash command and it brings you to the account creation, it skips the username and goes to the password, so then you cant login at all.
its the command from your website that doesnt work, but the command on github works.

Make sure you have type the right command.
If the command is accurate. Have to fix it ASAP (Since is me wrote that script)


snapshots: find max value currently used

The MAX() statement consistently returns snap9 when it should actualy return
snap10 or greater.
Signed-off-by: Christian Brauner<EMAIL_ADDRESS>

@stgraber, feel free to come up with a smarter way; not a db wizard.

I'm going to poke at sqlite a bit to see what can be done. The fix isn't right either because it won't necessarily return the last entry (it's an unsorted query) and even if it did, nothing tells you that the snapshots were created in order.

Why does it need to be sorted? The loop running after will look through all returned entries and find the biggest int, no?

Hmm, indeed, I didn't see the loop. Looks good.

Will this fix be released for Ubuntu 16.04 or do I have to add the PPA?

It will be in the next LXD 2.0.x point release (2.0.10) which will be pushed to Ubuntu 16.04.

Thanks @stgraber :+1:


Optimize Entities::reserve_entity to reduce memory and atomics

TL;DR: this cuts in half the number of atomic ops per
Entities::reserve_entity and also cuts in half the memory
overhead related to Entity freelisting and allocation.
Entities maintained two tables: reserved and free, each
with one slot for every possible Entity. This way every entity could
be freelisted or reserved without needing more memory. Combined,
these tables took 2*meta.len() slots.
The key observation is that any entity can only be in one table or the
other, but not both, so we actually only need meta.size() slots total,
i.e. half the memory. One way to take advantage of this would be to
have the freelist grow "up" from the bottom of a Vec, and reserved
grow "down" from the top of the same Vec, because we know they
can't meet in the middle.  But there is a better way.
This change combines free and reserved into unused, cutting the
memory in half, and also lays them out like this:
------------------------------------------
| freelist | reserved | <room to expand> |
------------------------------------------
           ^          ^
  freelist_cursor   reserved_cursor

When reserve_entity wants to move something from the freelist
to the reserved list, it simply atomically decrements freelist_cursor,
the boundary between the two, without moving any array entries.
This avoids the previous atomic operation to update reserved.
reserved_cursor no longer needs to be atomic because it is only
modified by &mut methods.
This approach does make alloc() and free() slightly more complicated.
alloc() has to update reserved_cursor to match freelist_cursor
(just a single store). This works if you can't have unflushed data
when you alloc, which is my understanding.
If free tries to push an item and there are reserved values, it
needs to move the first reserved value to the end of the reserved
range to make room for the larger freelist. I don't know if this can
happen -- is it actually legal to free into an unflushed Entities?
If not, then we don't need some of this code.
This change also has a few other tweaks:

When grow() copies values into the freelist, put them "before"
the old freelist values (if any), so they get popped last. This way
we are more likely to hand out lower IDs, only allocating higher IDs
when we really need them.

Added some unit tests.

I wasn't completely clear on the reserved_len (etc.) code and its
requirements (what is legal while iterating with those?), so I took my
best guess how to update it.

I do love optimizations :)
Given that this touches hecs code, it might also be a good idea to submit a PR to the hecs repo so they can get these optimizations too. @Ralith is this something you're interested in? It would be nice to get your feedback on this too given that you wrote entities.rs.

Another idea: if it's not legal to free() while unflushed stuff exists (unclear to me), the pending atomic could be deleted, as well as the free_cursor CAS. Instead, just use simpler code that unconditionally decrements free_cursor, and the more negative it goes, the more pending values there are.

Another thing that becomes possible by not moving freelist values around is that it's easy to add a reserve_entities method that returns N entities at once. It would return an iterator that contains both a slice pointing into the Entities freelist, and a numeric range of "pending" IDs consumed if the freelist ran out. Combined with removing the  pending atomic by letting free_cursor (now AtomicI64) go negative, that means that it would only take a single atomic subtract to reserve any number of IDs, and allocate no memory.

These changes (subject to detailed review) would be very welcome in hecs!

is it actually legal to free into an unflushed Entities?

I'm not certain what you mean by "into" here. free is not currently supported on reserved, unflushed entities, but may in principle be called prior to flush on real entities. At least in upstream hecs, we only ever call free immediately after flush (in World::despawn), so I'd be perfectly happy to strengthen that requirement to "must only be called with no pending (i.e. unflushed) entities" if it's useful.

Thanks @Ralith, that's the strengthened requirement I was interested in. I'll put together a PR for hecs and we can talk more about it there.

I will submit something upstream, so withdrawing this PR.

Cool cool. If/when this gets merged there, feel free to open up another pr here.

Upstream PR is https://github.com/Ralith/hecs/pull/86

@cart @Ralith please let me know if there is a specific ECS benchmark you'd like me to make faster.

The first thing that comes to my mind perfwise is the inlining improvements that were made in bevy which haven't yet been upstreamed. Help getting that synced back up would be great!

Yeah I think the inlining and "Entity as query" improvements are clear / relatively easy things to upstream. Sorry @Ralith for not driving those upstream myself yet. @mjhostet you are definitely welcome to do that if you want.


VS intellisense with doc comments from file attribute?

Is there any way to get docs included with the file attribute way to show up as "intellisense"in VS 2017/2019, as it does when the comments are directly in the code file? For example as a tooltip when hovering a member at the point of use. It does not work for me when the doc is in a referenced xml file.

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

ID: 39152ded-70ce-012d-ffc3-a8b1a78f3308
Version Independent ID: 809078f6-169a-0ffe-5f33-d5a359aeefc5
Content: Documenting your code with XML comments
Content Source: docs/csharp/codedoc.md
Product: dotnet-csharp
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

That's a nice idea @deap82
The very brief answer is that you'd have to build the XML file from the project to get the included text in the XML output. Then, if that file is delivered with the assembly, it gets displayed.
We should add a tutorial that covers ow to build this and consume it.
@gewarren Would this be something that should be covered in the VS docs, or is it better in the C# docs?

@BillWagner It sounds like perhaps it makes more sense in the VS docs. I'll assign this to myself.

Thanks @gewarren.
can you mention me when you create the doc? I'll link to it from the pertinent docs in the C# Guide for better visibility.

@billwagner But what about a multi project solution where one of the projects has these included files and other projects in the solution uses it? Will that also work?
My use case is not an assembly being distributed to others.

@deap82 I don't know the answer right now. @gewarren and I will investigate.

@BillWagner Could you transfer this issue (use "Transfer issue" on right hand side) to MicrosoftDocs/visualstudio-docs? I don't seem to have permissions to transfer it.

@gewarren I can’t. I just looked and “transfer issue” doesn’t support transferring from one org (dotnet) to another (MicrosoftDocs)
We’ll have to do the old close and reopen. Do you want me to use Zendesk to do that?

@billwagner - That would be great; thanks!

Crud. That's not supported either.  😞

I think the only way is to manually move it between orgs, unfortunately.

@jillre This work should be done in the VS docs. I'm not sure if you want to track it with this issue or create a new issue in the VS repo.

@gewarren Where can I find the updated docs? Will that also solve my concern in comment from March 5th; https://github.com/dotnet/docs/issues/10633#issuecomment-469544447 ?

@gewarren Where can I find the updated docs? Will that also solve my concern in comment from March 5th; #10633 (comment) ?

Sorry for the confusion; by "should be done" I meant "should happen". That is, it hasn't happened yet...

Closing this issue since it's being tracked in the Visual Studio docs repo now. @deap82 You might want to subscribe to notifications on that issue.

@gewarren, I don't understand how to find that issue. Could you please provide a link?

@deap82 here's the issue in the visualstudio-docs repo: https://github.com/MicrosoftDocs/visualstudio-docs/issues/4279


feat(sqlcheck): add sql affect rows support for ob oracle

What type of PR is this?
type-feature

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Additional documentation e.g., usage docs, etc.:

When we cannot judge the affected rows, we have another rule Unable2JudgeAffectedRows for this situation. You may need to adapt the Unable2JudgeAffectedRowsFactory

ok

Doc of SQL affected rows: https://yuque.antfin-inc.com/obodc/mkh69g/tm1huyba6gg4usl1

Doc of SQL affected rows: https://yuque.antfin-inc.com/obodc/mkh69g/tm1huyba6gg4usl1


Card Mechanics

Cards should have the mechanics used as an enum.
A separate document listing mechanics should also be produced.
Most are straight forward, except 'Veteran X' which has a dynamic value
Here is the code to generate a translations file (coffeescript):
_ = require 'lodash'
fs = require 'fs'

locales =
  'de-DE': 'de-DE'
  'en-US': 'en-US'
  'es-ES': 'es-es'
  'es-MX': 'es-mx'
  'fr-FR': 'fr-fr'
  'it-IT': 'it-it'
  'ja-JP': 'jp-jp'
  'pl-PL': 'pl-PL'
  'pt-BR': 'pt-br'
  'ru-RU': 'ru-RU'
  'zh-CN': 'zh-cn'
  'zh-TW': 'zh-tw'

parseFile = (file) ->
  res = {}
  _.map file.split('\n'), (line) ->
    if /"keyword_/.test line
      l = line.split ';'
      if l.length isnt 3
        throw new Error 'line has semicolon'
      keyword = line.match /keyword_\w+/
      translation = l[2].replace(/["\r]/g, '') # leave bold tag
        .replace(/<#[^>]+>/g, '').replace(/<\/color>/g, '') # <#0000></color>
      res[keyword] = translation.trim()
  return res

tooltipFiles = _.mapValues locales, (locale) ->
  fs.readFileSync __dirname + "/tooltips_#{locale}.csv", 'utf8'

englishKeyToKeyword = {}
translations = {}

_.map tooltipFiles['en-US'].split('\n'), (line) ->
  if /"keyword_/.test line
    keyword = line.match(/keyword_\w+/)[0]
    english_key = line.match(/[A-Z][\w\s]+:/)[0]
    if english_key is 'Veteran X:'
      english_key = 'Veteran'
    englishKeyToKeyword[english_key] = keyword

_.map tooltipFiles, (file, locale) ->
  f = parseFile file
  translations[locale] = _.mapValues englishKeyToKeyword, (keyword) ->
    f[keyword]

console.log JSON.stringify translations

Cards now have their keywords listed in the keywords field.
Now we need the localised definitions of those keywords. This will probably be exported as a separate JSON.

The keyword definitions are actually stored in each locales tooltips_-.csv file
e.g. en-US:
"tooltips";"keyword_ambush";"<#BDBDBD>Ambush:</color> Play face down and only turn over when certain conditions are met. While face down, adds no Power to its side's total and is immune to all abilities unless stated otherwise."
"tooltips";"keyword_armor";"<#BDBDBD>Armor:</color> Absorbs a given amount of Damage dealt to a Unit."
"tooltips";"keyword_banish";"<#BDBDBD>Banish:</color> Remove the card from the game."
"tooltips";"keyword_banish_in_graveyard";"<#BDBDBD>Doomed:</color> Units: Remove from the game when moved from the Board to the Graveyard.\nSpecial Cards: Remove from the game after triggering the card's ability."
"tooltips";"keyword_bond";"<#BDBDBD>Bond:</color> Trigger this ability each time another copy of this Unit is played on the same side."
"tooltips";"keyword_boost";"<#BDBDBD>Boost:</color> Increase a Unit's current Power."
"tooltips";"keyword_boosted";"<#BDBDBD>Boosted:</color> A Boosted Unit's current Power is more than its base Power."
"tooltips";"keyword_brave";"<#BDBDBD>Brave:</color> Trigger this ability if your opponent is winning the current Round (calculated after placing this Unit and any Units it Spawns)."
"tooltips";"keyword_clone";"<#BDBDBD>Clone:</color> An exact copy of a card, with the same current Power and abilities."
"tooltips";"keyword_consume";"<#BDBDBD>Consume:</color> Move a card to the Graveyard (or remove it from the game, if it's already in the Graveyard), then Boost the Consuming Unit by its Power."
"tooltips";"keyword_counter";"<#BDBDBD>Counter:</color> Reduce the Counter whenever the given condition is met. Reset the Counter when the Unit leaves the Board."
"tooltips";"keyword_craven";"<#BDBDBD>Craven:</color> Trigger this ability if your opponent is losing the current Round."
"tooltips";"keyword_crew";"<#BDBDBD>Crewmen X:</color> When a Unit with a 'Fresh Crew' ability is played adjacent to this Unit, trigger that ability X times."
"tooltips";"keyword_crewed";"<#BDBDBD>Fresh Crew:</color> Trigger this ability when this Unit is played adjacent to a Unit with a 'Crewmen' ability."
"tooltips";"keyword_damage";"<#BDBDBD>Damage:</color> Decrease a Unit's current Power."
"tooltips";"keyword_damaged";"<#BDBDBD>Damaged:</color> A Damaged Unit's current Power is less than its base Power."
"tooltips";"keyword_deadlock";"<#BDBDBD>Clash:</color> Trigger this ability only if neither player has passed."
"tooltips";"keyword_deathwish";"<#BDBDBD>Deathwish:</color> Trigger this ability when the card is moved to the Graveyard."
"tooltips";"keyword_demote";"<#BDBDBD>Demote:</color> Convert a Gold card to Silver (or Bronze, if Bronze was the card's original color)."
"tooltips";"keyword_deploy";"<#BDBDBD>Deploy:</color> Trigger this ability when the card is placed on the Board."
"tooltips";"keyword_destroy";"<#BDBDBD>Destroy:</color> Move the card to the Graveyard."
"tooltips";"keyword_discard";"<#BDBDBD>Discard:</color> Move the card to the Graveyard from the Hand or Deck."
"tooltips";"keyword_doomed";"<#BDBDBD>Doomed:</color> Units: Remove from the game when sent to the Graveyard.\nSpecial Cards: Remove from the game after triggering the card's ability."
"tooltips";"keyword_drain";"<#BDBDBD>Drain:</color> Damage a Unit and Boost the Draining Unit by the specified amount."
"tooltips";"keyword_draw";"<#BDBDBD>Draw:</color> Move the top card or cards from your Deck to your Hand."
"tooltips";"keyword_enemy";"<#BDBDBD>Enemy:</color> A Unit on your opponent's side of the Board."
"tooltips";"keyword_friendly";"<#BDBDBD>Ally:</color> A Unit on your side of the Board."
"tooltips";"keyword_gamble";"<#BDBDBD>Gamble:</color> Guess whether a random Bronze or Silver Unit from your opponent's Deck is Higher or Lower than 5. The consequences of winning or losing your Gamble are written on the card."
"tooltips";"keyword_gold";"<#BDBDBD>Gold:</color> Card abilities do not affect or take into account Gold cards unless otherwise stated. You can, however, draw Gold cards from your deck if no color restrictions are specified."
"tooltips";"keyword_heal";"<#BDBDBD>Heal:</color> Restore a Damaged Unit to its base Power."
"tooltips";"keyword_highest";"<#BDBDBD>Highest:</color> The highest Power. If the ability targets only one Unit, ties are resolved randomly."
"tooltips";"keyword_leadership";"<#BDBDBD>Leadership:</color> Trigger this ability when either Leader card is played (but before the Leader's ability is resolved)."
"tooltips";"keyword_lock";"<#BDBDBD>Lock:</color> Disables a card's abilities. Disables and turns over Ambushes. Prevents a Unit from counting towards a Trio."
"tooltips";"keyword_lowest";"<#BDBDBD>Lowest:</color> The lowest Power. If the ability targets only one Unit, ties are resolved randomly."
"tooltips";"keyword_mulligan";"<#BDBDBD>Mulligan:</color> Exchange a certain number of cards in your Hand for cards from your Deck. Golds can be drawn and exchanged (unless stated otherwise)."
"tooltips";"keyword_muster";"<#BDBDBD>Summon:</color> Play the specified card(s) from your Deck."
"tooltips";"keyword_non_decoyable";"<#BDBDBD>Stubborn:</color> This card cannot return to the Hand."
"tooltips";"keyword_order";"<#BDBDBD>Orders:</color> Trigger this ability when your Leader card is played (but before its ability is resolved)."
"tooltips";"keyword_overstrain";"<#BDBDBD>Effort:</color> Perform the specified action for every card targeted by the preceding ability."
"tooltips";"keyword_pair";"<#BDBDBD>Pair:</color> Trigger this ability when 2 copies of this card are present on the Board."
"tooltips";"keyword_promote";"<#BDBDBD>Promote:</color> Convert the card to Gold until the Round ends."
"tooltips";"keyword_regress";"<#BDBDBD>Regress:</color> Return the card to its original state."
"tooltips";"keyword_regressing";"<#BDBDBD>Regressing:</color> When this Unit is removed from the Board, its base Power is returned to the value it has in the Collection."
"tooltips";"keyword_reset";"<#BDBDBD>Reset:</color> Reset the Unit to its base Power."
"tooltips";"keyword_resilient";"<#BDBDBD>Resilient:</color> A Resilient Unit remains on the Board at the end of the Round."
"tooltips";"keyword_resistant";"<#BDBDBD>Resistant:</color> A Resistant Unit is not affected by the specified Weather effect."
"tooltips";"keyword_resurrect";"<#BDBDBD>Resurrect:</color> Play a card from your Graveyard, or, if specified, from your opponent's Graveyard."
"tooltips";"keyword_retaliation";"<#BDBDBD>Retaliation:</color> Trigger this ability whenever this Unit is Damaged but not sent to the Graveyard."
"tooltips";"keyword_reveal";"<#BDBDBD>Reveal:</color> Turn a card in the Hand over, exposing it to both players."
"tooltips";"keyword_revealed";"<#BDBDBD>Revealed:</color> A card in the Hand that has been turned over, exposing it to both players."
"tooltips";"keyword_round_end";"<#BDBDBD>Round End:</color> Trigger this ability when the Round ends."
"tooltips";"keyword_shield";"<#BDBDBD>Shield:</color> Protects a Unit from the next Power-reducing effect."
"tooltips";"keyword_solitary";"<#BDBDBD>Solitary:</color> Trigger this ability if there is only 1 copy of this card on the Board."
"tooltips";"keyword_spawn";"<#BDBDBD>Spawn:</color> Add the card to the game and immediately play it."
"tooltips";"keyword_spring";"<#BDBDBD>Spring:</color> Turn over a face down Ambush card and trigger its ability."
"tooltips";"keyword_spying";"<#BDBDBD>Spying:</color> A Unit is Spying when it is on the opposite side of the Board from the player who played it."
"tooltips";"keyword_strengthen";"<#BDBDBD>Strengthen:</color> Increase a Unit's base Power."
"tooltips";"keyword_stubborn";"<#BDBDBD>Stubborn:</color> This card cannot return to the Hand."
"tooltips";"keyword_timer";"<#BDBDBD>Timer:</color> Reduce the Timer by 1 every turn while this Unit is on the Board. Trigger the ability when it reaches 0 (at the start or end of the turn). Reset the Timer when the Unit leaves the Board."
"tooltips";"keyword_transform";"<#BDBDBD>Transform:</color> Convert into a different card."
"tooltips";"keyword_trio";"<#BDBDBD>Trio:</color> Exactly 3 Unlocked copies of a Unit on a row."
"tooltips";"keyword_turn_end";"<#BDBDBD>Turn End:</color> Trigger this ability at the end of your turn."
"tooltips";"keyword_turn_start";"<#BDBDBD>Turn Start:</color> Trigger this ability at the start of your turn."
"tooltips";"keyword_veteran";"<#BDBDBD>Veteran X:</color> At the start of Rounds 2 and 3, Strengthen this Unit by X if it is in your Hand, Deck or Graveyard."
"tooltips";"keyword_weaken";"<#BDBDBD>Weaken:</color> Decrease a Unit's base Power."

This info is now localised and included in the keywords.json output.


The join is not actually used.

https://github.com/evmar/webtreemap/blob/5dbfbff2619004ffeb38cd3230ee8bcf3f97a96c/src/tree.ts#L68-L82
The join function is not used though.
I think it's possible to modify the line 78. However the id property mismatch the join function type.
Maybe you can give me a hint.
Thanks.

I agree that the join function isn't used. It looks like that can be deleted just fine.
diff --git a/src/tree.ts b/src/tree.ts
index 8d78894..e313c89 100644
--- a/src/tree.ts
+++ b/src/tree.ts
@@ -65,13 +65,10 @@ export function treeify(data: Array<[string, number]>): Node {
  * @param join If given, a function that joins the names of the parent and
  * child.
  */
-export function flatten(
-  n: Node,
-  join = (parent: string, child: string) => `${parent}/${child}`
-) {
+export function flatten(n: Node) {
   if (n.children) {
     for (const c of n.children) {
-      flatten(c, join);
+      flatten(c);
     }
     if (n.children.length === 1) {
       const child = n.children[0];

I'm not sure what you're saying about the id property though.

As far as I concered, the purpose of flatten is to flatten nodes that have only one child, which means a child node hoist.
So the new id of the parent should have something to do with the child.id. And here comes the join function to do the job.
However, the id is optional, as commented, in the type Node.   The TS compiler yells when make change like the following.