Question: Remove existing wallet and create new one

Background
Let's say someone lost access to their lnd wallet (asking for a friend :wink:) and now he wants to create a new wallet?
Just calling lncli create returns an error, as expected:
[lncli] unable to generate seed: rpc error: code = Unknown desc = wallet already exists
What would be the best way of removing the old wallet and creating a new one? Just delete all macraroon files?
By the way. The error is thrown at the end of the create-wallet process. It would be nice if lncli create would return an error instantly and not ask for all the passwords and ciphers first!
Your environment

lnd version 0.4.1-beta commit=9017d18f14d9cb07256dfa9c2927cb6d6431dbeb
Linux bitcoin-full-node-with-lightning 4.4.0-121-generic
Bitcoin Core Daemon version v<IP_ADDRESS>-g4b4d7eb255

Thanks for the Help!

What would be the best way of removing the old wallet and creating a new one? Just delete all macraroon files?

Just delete all your old state, then start over again.

Thanks the quick answer!

Just delete all your old state, then start over again.

My question is what is the "old state". Is it all macaroon files? Some configs? For me and also for documentation purposes it would be nice to know what information is stored where.

My question is what is the "old state". Is it all macaroon files? Some configs? For me and also for documentation purposes it would be nice to know what information is stored where.

Old state is everything in the lnd application directory. The location depends on you OS, for example will be in ~/.lnd for linux.

Is there a more surgical way to do this? Would I be able to delete just enough to prompt a new "Create or unlock wallet prompt" and not botch the lnd service.  I'm trying NOT to delete everything as that would cause a new rescan of the entire blockchain.

I removed everything in the ~/.lnd directory and still got this error:

[lncli] unable to generate seed: rpc error: code = Unknown desc = wallet already exists

I deleted ~/.lnd/data, it works.

i dont consider  "I deleted ~/.lnd/data, it works." a solution since it changes identity_pubkey (and all connected setups).
Rbeef comment "Just delete all your old state, then start over again." is also insufficient.
Do better, provide solution, please reopen.

I did
rm ~/.lnd/data/chain/bitcoin/mainnet/wallet.db

I will leave this here in case it helps someone else.
I was able to prompt creating a new wallet (resolve "[lncli] unable to generate seed: rpc error: code = Unknown desc = wallet already exists" without having to even shut down the lnd) by simply renaming "\Lnd\data\chain\litecoin\mainnet\wallet.dat" to a different filename.


builtins: add parse and to_char_with_style variants for date types

PR: https://github.com/cockroachdb/cockroach/pull/68351
From release notes:

Implemented the parse_time and parse_timetz builtins, which parses a TIME or TIMETZ with immutable volatility. [#68351][#68351]

We probably don't need to document this built-in explicitly (it's included from the generated docs).


move echo action to util package

I claim that's where it belongs.

Hi Stephen, can we do this as part of the "openwhisk-catalog" move? See issue #2 👍
https://github.com/openwhisk/openwhisk-catalog/issues/2
in the new openwhisk-catalog repo.
We can create that issue there or I can amend #2 to include  echo.js.

@houshengbo Please be aware of this as part of issue #2 for the catalog move.

done.


BloomRPC - A Nice and Simple GUI Client for gRPC Services

Hi there,
I'm excited to add BloomRPC to the awesome-grpc collection.
This is yet another gRPC GUI client which focuses on simplicity of use and real-life developer experience for exploring and debugging gRPC services.
It supports all gRPC types of calls including streamings
We've been developing BloomRPC internally and we are now glad to share to the open source.

I signed it!


Error opening file with mode 'r': 'dict/english.txt': No such file or directory (File::NotFoundError) on Crystal 1.5.0

Please check following backtrace, thank you.
  from /usr/share/crystal/src/crystal/system/unix/file.cr:11:7 in 'open'
  from /usr/share/crystal/src/file.cr:120:5 in 'new'
  from /usr/share/crystal/src/file.cr:656:5 in 'read'
  from /usr/share/crystal/src/file.cr:670:3 in 'read'
  from lib/bip39/src/util.cr:27:5 in 'word_list'
  from lib/bip39/src/bip39.cr:164:7 in 'to_words'
  from src/project_root.cr:37:1 in '->'
  from lib/kemal/src/kemal/route.cr:12:26 in '->'
  from lib/kemal/src/kemal/route_handler.cr:49:39 in 'process_request'
  from lib/kemal/src/kemal/route_handler.cr:17:7 in 'call'
  from /usr/share/crystal/src/http/server/handler.cr:28:7 in 'call_next'
  from lib/kemal/src/kemal/websocket_handler.cr:13:14 in 'call'
  from /usr/share/crystal/src/http/server/handler.cr:28:7 in 'call_next'
  from lib/kemal/src/kemal/filter_handler.cr:21:7 in 'call'
  from /usr/share/crystal/src/http/server/handler.cr:28:7 in 'call_next'
  from lib/kemal/src/kemal/static_file_handler.cr:75:9 in 'call'
  from /usr/share/crystal/src/http/server/handler.cr:28:7 in 'call_next'
  from lib/kemal/src/kemal/exception_handler.cr:8:7 in 'call'
  from /usr/share/crystal/src/http/server/handler.cr:28:7 in 'call_next'
  from lib/kemal/src/kemal/log_handler.cr:8:37 in 'call'
  from /usr/share/crystal/src/http/server/handler.cr:28:7 in 'call_next'
  from lib/kemal/src/kemal/init_handler.cr:12:7 in 'call'
  from /usr/share/crystal/src/http/server/request_processor.cr:51:11 in 'process'
  from /usr/share/crystal/src/http/server.cr:515:5 in 'handle_client'
  from /usr/share/crystal/src/http/server.cr:468:13 in '->'
  from /usr/share/crystal/src/fiber.cr:146:11 in 'run'
  from /usr/share/crystal/src/fiber.cr:98:34 in '->'

I create a PR #9 for fix this, thank you.


setup.cfg isn't packaging Python library files

One can see this by extracting the tarball after python -m build or by running pip install . -vvv | grep adding. Only the dist-info stuff is added.
There is something in the setup.cfg file, but after playing with the packages = find: or other options I can't make much progress, and the setuptools user guide isn't much help.
@tngTUDOR Any ideas?

I think this is related to:
https://github.com/brightway-lca/cookiecutter-brightwaylib/blob/main/{{cookiecutter.project_name}}/setup.cfg#L48

this should have been fixed with:
https://github.com/brightway-lca/cookiecutter-brightwaylib/commit/85b6d642cd92c49fe3539e139010779e48016abd

does your setup.cfg specify "root" project folder as the place to find packages?
  45   │ zip_safe = False
  46   │ packages = find_namespace:
  47   │ include_package_data = True
  48   │ package_dir =
  49 ~ │     = .

and:
  63   │ [options.packages.find]
  64   │ where = .
  65   │ exclude =
  66   │     tests


Unable to run suite with chromedriver in ubuntu

QAF Version

Note: only the latest version is supported

Steps To Reproduce
using following configurations
1. ChromeDriver 2.36.540471
2. qaf 2.1.13
3. java 1.8
Expected behavior
I am able to run UI test suites in mac , however not able to run on ubuntu/debian linux systems.
Actual behavior
Getting the following exception after running mvn test
[UiDriverFactory] - Driver: chromeDriver
Starting ChromeDriver 2.36.540471 (9c759b81a907e70363c6312294d30b6ccccc2752) on port 12609
Only local connections are allowed.
Unable to create driver instance in 1st attempt with retry timeout of 0 seconds. You can check/set value of 'driver.init.retry.timeout' appropriately to set retry timeout on driver initialization failure.Unable to Create Driver Instance for chrome: unknown error: cannot find Chrome binary
(Driver info: chromedriver=2.36.540471 (9c759b81a907e70363c6312294d30b6ccccc2752),platform=Linux 4.4.0-1052-aws x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 96 milliseconds
Build info: version: '2.53.0', revision: '35ae25b1534ae328c771e0856c93e187490ca824', time: '2016-03-15 10:43:46'
Is the issue reproducible on runner?

[x ] QAS
[x ] Maven
[  ] Gradle
[  ] Ant
[  ] Eclipse

Test case sample

Please, share the test case (as small as possible) which shows the issue

[UiDriverFactory] - Driver: chromeDriver
Starting ChromeDriver 2.36.540471 (9c759b81a907e70363c6312294d30b6ccccc2752) on port 12609
Only local connections are allowed.
Unable to create driver instance in 1st attempt with retry timeout of 0 seconds. You can check/set value of 'driver.init.retry.timeout' appropriately to set retry timeout on driver initialization failure.Unable to Create Driver Instance for chrome: unknown error: cannot find Chrome binary
(Driver info: chromedriver=2.36.540471 (9c759b81a907e70363c6312294d30b6ccccc2752),platform=Linux 4.4.0-1052-aws x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 96 milliseconds
Build info: version: '2.53.0', revision: '35ae25b1534ae328c771e0856c93e187490ca824', time: '2016-03-15 10:43:46'

Issue is more related to driver configuration.
As exception reads Unable to Create Driver Instance for chrome: unknown error: cannot find Chrome binary, which is from chrome driver! May be it's not finding the chrome binary and you can try by providing chrome binary location using capability as per closed chrome driver issue #950.
chrome.additional.capabilities={"chromeOptions": {"binary": "D:/Program Files/Chrome/chrome.exe"}}

Make sure you have correct value for webdriver.chrome.driver and the chromedriver is compatible with the version of chrome.
qaf users group is right place to post such issues.

Thanks cjayswal, Binary issue has been resolved, however i am getting different issue and posting in qaf users group. Many thanks , Really appreciate your help here.

Will you please share resolution and close the issue?

following setting helped me to resolve binary issue:
chrome.additional.capabilities={"chromeOptions":{"binary": "/home/ubuntu/software/chromedriver"}}


chore: simplified metapackage types

Here is what I was talking about. Much less code and IMO easier to manage.

Codecov Report

:exclamation: No coverage uploaded for pull request base (node@2efd447). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             node       #2   +/-   ##
=======================================
  Coverage        ?   92.33%
=======================================
  Files           ?        7
  Lines           ?      261
  Branches        ?       32
=======================================
  Hits            ?      241
  Misses          ?       20
  Partials        ?        0


Tagging first time contributors

It would be helpful if the bot could help to identify new contributors to Node core by automatically tagging new PRs with a "New Contributor" label (if the user has never landed a commit in core) or "Recently New Contributor" label (if the user has only recently landed their first commit). This would make it easier to identify, welcome and recognize new contributors.

I really like this idea! Do we want the bot to create a friendly comment as well?

That would be good but I'd want to make sure collaborators are encouraged
to post their own welcome messages also.
On Friday, August 5, 2016, Phillip Johnsen<EMAIL_ADDRESS>wrote:

I really like this idea! Do we want the bot to create a friendly comment
as well?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nodejs-github-bot/github-bot/issues/56#issuecomment-237833925,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAa2eUrSbzpvfgP2ktREX6snWbAmV4jqks5qcyc7gaJpZM4JZrLb
.

@jasnell has the need for this changed in some sense, now that GitHub does this? As seen in https://github.com/nodejs/node/pull/12727:

Good question! I still think it's helpful but also better if the welcome message comes from a real person. I think we can close this!

Alright, closing this then. Sorry for letting this rot forever...


You can still use rocket punch and meteor strike while hacked by Sombra

When I was playing with some friends I was hacked and I could still use my rocket punch and my ult but I couldn’t use slam or uppercut.

PR #291 will fix this.


python38Packages.click-help-colors: 0.9 -> 0.9.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python38Packages.click-help-colors is: "Colorization of help messages in Click"
meta.homepage for python38Packages.click-help-colors is: "https://github.com/r-m-n/click-help-colors"
meta.changelog for python38Packages.click-help-colors is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.9.1 with grep in /nix/store/4njl5r06d545fb1nxka5rk2x7ynbha6y-python3.8-click-help-colors-0.9.1

found 0.9.1 in filename of file in /nix/store/4njl5r06d545fb1nxka5rk2x7ynbha6y-python3.8-click-help-colors-0.9.1

directory tree listing: https://gist.github.com/a1724a38d358dd635f95dd8af1235008

du listing: https://gist.github.com/a0c4d58ccd07128c5c1fc5160a287751

Rebuild report (if merged into master) (click to expand)

16 total rebuild path(s)

4 package rebuild(s)

4 x86_64-linux rebuild(s)
4 i686-linux rebuild(s)
4 x86_64-darwin rebuild(s)
4 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
python38Packages.click-help-colors
python38Packages.gradient
python39Packages.click-help-colors
python39Packages.gradient

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/4njl5r06d545fb1nxka5rk2x7ynbha6y-python3.8-click-help-colors-0.9.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python38Packages.click-help-colors https://github.com/r-ryantm/nixpkgs/archive/d3d60a082a7d803ed1e2dc0f3156fb72b837be7a.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4njl5r06d545fb1nxka5rk2x7ynbha6y-python3.8-click-help-colors-0.9.1
ls -la /nix/store/4njl5r06d545fb1nxka5rk2x7ynbha6y-python3.8-click-help-colors-0.9.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @freezeboy for testing.

Result of nixpkgs-review pr 133797 at d3d60a08 run on x86_64-linux 1

2 packages failed to build:

python38Packages.gradient
python39Packages.gradient

2 packages built successfully:

python38Packages.click-help-colors
python39Packages.click-help-colors

1 suggestion:

warning: no-python-tests
Test runner could not discover any test cases: ‘Ran 0 tests in 0.000s’
Near pkgs/development/python-modules/click-help-colors/default.nix:23:0:
   |
23 |     description = "Colorization of help messages in Click";
   | ^

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.


[SPARK-46424][PYTHON][SQL] Support Python metrics in Python Data Source

What changes were proposed in this pull request?
This PR proposes to support Python metrics in Python Data Source so the metrics are reported same as other Python execution and API.
Why are the changes needed?
Same metics (https://github.com/apache/spark/pull/33559) should be shown in Python Data Source reading. This is last missing part compared to other Python execution and API.
Does this PR introduce any user-facing change?
Python Data Source has not been released yet, so no end-user facing change.
It shows some new metrics in UI.
Example:
from pyspark.sql.datasource import DataSource, DataSourceReader, InputPartition

class TestDataSourceReader(DataSourceReader):
    def __init__(self, options):
        self.options = options
    def partitions(self):
        return [InputPartition(i) for i in range(3)]
    def read(self, partition):
        yield partition.value, str(partition.value)

class TestDataSource(DataSource):
    @classmethod
    def name(cls):
        return "test"
    def schema(self):
        return "x INT, y STRING"
    def reader(self, schema) -> "DataSourceReader":
        return TestDataSourceReader(self.options)

spark.dataSource.register(TestDataSource)
sql("CREATE TABLE tblA USING test")
sql("SELECT * from tblA").show()

This is same as other Python nodes, UDFs, etc.
How was this patch tested?
Unittests were added, and manually tested via UI.
Was this patch authored or co-authored using generative AI tooling?
No.

cc @cloud-fan and @allisonwang-db
cc @viirya too who actually added this IIRC :-).

Merged to master

Made a PR to clean up.


Add sourceMap to babelConfig options

Just a simple addition to add sourcemaps when the output is ES2015.

Thanks @sevenninety! Will test this and get back soon.


[ACR] add IE browser issue to FAQ

// @sajayantony

@ankurkhemani : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ankurkhemani : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Require Node 16 or greater

This package wasn't explicit about which version of Node.js it required. In other words, it didn't set the "engines" field in package.json.
This changes that. I chose Node 16 because that is the latest supported version.
Setting the engine won't stop anyone from installing the library on old Node—it just gives a warning and may not work for them.
Nobody asked me to do this, so feel free to reject or ask for changes. (I'm doing this because it will make it easier to update the better-sqlite3 dependency, which is on an old version that's giving me trouble.)

Looks good, thanks @EvanHahn ! Merging in.

Thanks! I opened #25 as a followup.


feat: add loeffel-io/ls-lint

loeffel-io/ls-lint: An extremely fast directory and filename linter - Bring some structure to your project filesystem
$ aqua g -i loeffel-io/ls-lint

How to confirm if this package works well
Reviewers aren't necessarily familiar with this package, so please describe how to confirm if this package works well.
Please confirm if this package works well yourself as much as possible.
Command and output
$ ls-lint --help
Usage of ls-lint-darwin-arm64:
  -config string
        ls-lint config file path (default ".ls-lint.yml")
  -debug
        write debug informations to stdout
  -version
        prints version information for ls-lint
  -warn
        write lint errors to stdout instead of stderr (exit 0)
  -workdir string
        change working directory before executing the given subcommand (default ".")

see. https://ls-lint.org/

Thank you always!

v4.12.0 is out 🎉
https://github.com/aquaproj/aqua-registry/releases/tag/v4.12.0


Replace unmaintained actions-rs actions

Specific Demand
actions-rs/toolchain and the rest of the actions-rs org have been unmaintained for over two years. See this Reddit thread for more info. I'm also tagging the issue of shame. We should update the pipelines to use a different approach for installing Rust toolchains.
Implement Suggestion
One that keeps coming up in the forums as a good replacement is dtolnay/rust-toolchain. I've successfully integrated this in my personal project and in my PR #1358 for the new CLI release pipeline. I think this is a good move for the other pipelines in this project to avoid any vulnerabilities or disruptions (such as the eventual set-output deprecation).

Closed by #1366

Just for laughs take a look at https://github.com/DioxusLabs/dioxus/pull/1099.
So the issue described here was already fixed in #1099 on June 19th, but both actions-rs/toolchain and actions-rs/cargo were re-introduced in #1222 on July 20th, a month later. PR #1222 was also merged by its creator without review, so you might possibly want to put some checks in place to avoid that in the future. Otherwise you might see yourselves in the position where you need to address this very issue again.
(And then there is #1077 which also uses / re-introduced the unmaintained actions-rs stuff, but since the issue was created before #1099 and was only merged after #1099 one cannot really blame its creator. It's just an unfortunate chain of events. Had it been merged before #1099, then #1099 would have picked that up.)


Request for External function

Can we get the following functions as External at 2018 W1 CU6.
Function                                            | Object Type  -   Name
ValidatePurchaserOnPurchHeader   | Table            -   Purchase   Header
CheckIfPrivacyBlocked                      | Table            -   Contact
ValidateSalesPersonOnSalesHeader | Table            -   Sales Header
ReservEntryExist                                | Codeunit      -   Purch.   Line-Reserve

Thank you for your request! We have exposed the functions in the upcoming major release. We will be backporting the change to the current Business Central offering as well, but will not be backporting the change to NAV2018, seeing that NAV2018 is an on-premise release which you can modify yourself. Please refer to the following blog post for our branching and release strategy, if you are interested: https://blogs.msdn.microsoft.com/nav/2018/05/03/al-developer-previews-multiple-releases-and-github/. If the fix has to be backported to NAV2018, please follow the instructions in the blog post for backporting.


New list comprehensions lesson

RFC @pragmaticivan, @pjhampton — Please DO NOT MERGE, need to figure out the order of this lesson in the basics section.

@pjhampton I set this lesson to number 13.  Any other feedback?

I am going to merge this but I do plan to come back and expand on the subject a bit more.


Recurate hybertson2011

Comment on line 204.

@sgebel  the necessary changes have been made.

@sgebel necessary changes have been made.

@sgebel  Discussion closed.


SyntaxError: Unexpected end of JSON input

I see this in developer tools in one window. I haven't been using the extension in this window. I see it every time I reload the window. It's a multiroot workspace if that helps.
 ERR Unexpected end of JSON input: SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at Object.t.fromPRUri (/Users/roblou/.vscode-insiders/extensions/github.vscode-pull-request-github-insiders-0.345.0/media/extension.js:1:53851)
    at t.FileTypeDecorationProvider.provideDecoration (/Users/roblou/.vscode-insiders/extensions/github.vscode-pull-request-github-insiders-0.345.0/media/extension.js:8:6595)
    at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:529:104
    at Array.map (<anonymous>)
    at e.$provideDecorations (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:528:972)
    at t._doInvokeHandler (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:658:837)
    at t._invokeHandler (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:658:509)
    at t._receiveRequest (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:657:60)
    at t._receiveOneMessage (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:656:59)
    at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:653:895
    at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:130:793
    at e.fire (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:133:218)
    at a (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:186:147)
    at Socket.n._socketDataListener (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:186:368)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at addChunk (_stream_readable.js:263:12)
    at readableAddChunk (_stream_readable.js:250:11)
    at Socket.Readable.push (_stream_readable.js:208:10)
    at Pipe.onread (net.js:594:20)

This is happening again, same error

@roblourens are you using Nightly build?

Yes

@roblourens the nightly build is broken due to vsce on Nodejs 10.14 https://github.com/Microsoft/vscode-vsce/pull/314 , already fixed and published a new release, which contains the fix I mentioned above.


Bug in getState and getStateV2

Describe the bug
I was attempting to resolve ticket #5409 and the epoch state transitions but cannot pull the historical state.  I believe the system is timing out when attempting to recreate the state through state transition.
Attempted to pull state via slot and 0x prefixed hex stateRoot but was unable to pull the data.  The named states head, finalized etc work fine but older states to not get returned.
Expected behavior
curl -H "Accept: application/octet-stream" https://lodestar-mainnet.chainsafe.io/eth/v2/debug/beacon/states/6123583 -o state_mainnet_6123583.ssz should output the state to disk in SSZ format.
Steps to Reproduce
run: curl -H "Accept: application/octet-stream" https://lodestar-mainnet.chainsafe.io/eth/v2/debug/beacon/states/6123583 -o state_mainnet_6123583.ssz
returns: 504
run: curl -H "Accept: application/octet-stream" https://lodestar-mainnet.chainsafe.io/eth/v2/debug/beacon/states/0xadd30839a0a9bb6705edf4b0ee08b160af85ecc4e7ffc7ec0198575e339397f0 -o state_mainnet_6123583.ssz
returns: 404 or 504 depending on the root used
Screenshots

Desktop (please complete the following information):

OS: osx and linux
Version: current
Branch: several, found on stable and unstable.  Not sure which others
Commit hash: HEAD

Found the error that is actually getting thrown:
https://github.com/ChainSafe/lodestar/blob/229b77baa26ee100cd644ce0494d6c217dd681c1/packages/state-transition/src/util/seed.ts#L52
error: Req req-7 getState error  Validator indices must not be empty

It's really weird to see this error error: Req req-7 getState error  Validator indices must not be empty, since all states have some active validators.

Here is a copy of the full stack trace and a screenshot.  Was running for almost 13 min and then threw the error.  Had super high cpu till it crashed so wondering if it was a single state transition that was bad to cause it but still trying to sort through that.
May-01 22:03:31.340[rest]            error: Req req-8 getState error  Validator indices must not be empty
Error: Validator indices must not be empty
    at computeProposerIndex (file:///Users/matthewkeil/Documents/dev/chainsafe/lodestar/packages/state-transition/src/util/seed.ts:52:11)
    at computeProposers (file:///Users/matthewkeil/Documents/dev/chainsafe/lodestar/packages/state-transition/src/util/seed.ts:31:7)
    at EpochContext.afterProcessEpoch (file:///Users/matthewkeil/Documents/dev/chainsafe/lodestar/packages/state-transition/src/cache/epochContext.ts:468:22)
    at processSlotsWithTransientCache (file:///Users/matthewkeil/Documents/dev/chainsafe/lodestar/packages/state-transition/src/stateTransition.ts:174:26)
    at processSlots (file:///Users/matthewkeil/Documents/dev/chainsafe/lodestar/packages/state-transition/src/stateTransition.ts:136:15)
    at getFinalizedState (file:///Users/matthewkeil/Documents/dev/chainsafe/lodestar/packages/beacon-node/src/api/impl/beacon/state/utils.ts:267:13)
    at stateBySlot (file:///Users/matthewkeil/Documents/dev/chainsafe/lodestar/packages/beacon-node/src/api/impl/beacon/state/utils.ts:199:20)
    at resolveStateId (file:///Users/matthewkeil/Documents/dev/chainsafe/lodestar/packages/beacon-node/src/api/impl/beacon/state/utils.ts:42:40)
    at Object.getState (file:///Users/matthewkeil/Documents/dev/chainsafe/lodestar/packages/beacon-node/src/api/impl/debug/index.ts:44:23)
    at Object.handler (file:///Users/matthewkeil/Documents/dev/chainsafe/lodestar/packages/api/src/beacon/server/debug.ts:23:26)

You should dump to disk the state that this code path claims has no active validators to take a deeper look after the fact

slot that threw in processSlots: 17056
state buffer length passed in: 6729301
Captured via:
 curl http://<IP_ADDRESS>:9596/eth/v2/debug/beacon/states/6123583  -H "Accept: application/octet-stream" -o state_mainnet_6123583.ssz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100    84    0    84    0     0      0      0 --:--:--  0:12:58 --:--:--    21

  let stateBeforeError!: CachedBeaconStateAllForks;
  let slotBeforeError = slot;
  try {
    // due to skip slots, may need to process empty slots to reach the requested slot
    if (state.slot < slot) {
      stateBeforeError = state.clone();
      slotBeforeError = state.slot;
      state = processSlots(state, slot);
    }
  } catch (err) {
    const filepath = path.resolve(path.dirname(fileURLToPath(import.meta.url)), `state_mainnet_${slot}.ssz`);
    const serialized = stateBeforeError.serialize();
    console.log(`state buffer length: ${serialized.length}\nslot passed into processSlots: ${slotBeforeError}\n`);
  }

Serialized state that was saved in ssz format.
state_mainnet_before_error.ssz.zip

@matthewkeil I'm not able to deserialize the downloaded state, could you give it a try?
Error: Offset out of bounds<PHONE_NUMBER> > 6729301
      at readVariableOffsets (/Users/tuyennguyen/Projects/lodestar/node_modules/@chainsafe/ssz/src/type/container.ts:451:13)

maybe you could try stateBeforeError.commit() before stateBeforeError.serialize()

I was successful pulling the historical state from a full-sync Lodestar node.  Perhaps we can throw an error if not in the correct mode.  We could determine if the call will fail so it fails quickly and with a better error. @dapplion what are your thoughts?  Would it be better to look at state or just the config?

Let's archive this issue for now and revisit latter

Leaving a breadcrumb here.  When the db attempts to pull the nearest state to regen from it eventually attempts to pull and the repo returns null when it does not find it cached here

I think #6033 will tackle this

superseded by #5846


[Bug] enable-torch-compile error

Checklist

[x] 1. I have searched related issues but cannot get the expected help.
[x] 2. The bug has not been fixed in the latest version.
[x] 3. Please note that if the bug-related issue you submitted lacks corresponding environment info and a minimal reproducible demo, it will be challenging for us to reproduce and resolve the issue, reducing the likelihood of receiving feedback.
[x] 4. If the issue you raised is not a bug but a question, please raise a discussion at https://github.com/sgl-project/sglang/discussions/new/choose Otherwise, it will be closed.
[x] 5. Please use English, otherwise it will be closed.

Describe the bug
Starting the server with  --enable-torch-compile flag fails with this error:
Traceback (most recent call last):
  File "/usr/lib/python3.10/multiprocessing/process.py", line 314, in _bootstrap
    self.run()
  File "/usr/lib/python3.10/multiprocessing/process.py", line 108, in run
    self._target(*self._args, **self._kwargs)
  File "/home/ubuntu/testfs/sglang-venv/lib/python3.10/site-packages/sglang/srt/managers/tp_worker.py", line 781, in run_tp_server
    model_server = ModelTpServer(
  File "/home/ubuntu/testfs/sglang-venv/lib/python3.10/site-packages/sglang/srt/managers/tp_worker.py", line 99, in __init__
    self.model_runner = ModelRunner(
  File "/home/ubuntu/testfs/sglang-venv/lib/python3.10/site-packages/sglang/srt/model_executor/model_runner.py", line 140, in __init__
    self.init_cuda_graphs()
  File "/home/ubuntu/testfs/sglang-venv/lib/python3.10/site-packages/sglang/srt/model_executor/model_runner.py", line 373, in init_cuda_graphs
    raise Exception(
Exception: Capture cuda graph failed: backend='inductor' raised:
RuntimeError: "_local_scalar_dense_cuda" not implemented for 'Float8_e4m3fn'

While executing %empty : [num_users=1] = call_function[target=torch.ops.aten.empty.memory_format](args = ([1, 8192],), kwargs = {dtype: torch.float8_e4m3fn, device: cuda:1, pin_memory: False})
Original traceback:
  File "/home/ubuntu/testfs/sglang-venv/lib/python3.10/site-packages/sglang/srt/models/llama2.py", line 165, in forward
    qkv, _ = self.qkv_proj(hidden_states)
  File "/home/ubuntu/testfs/sglang-venv/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1562, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/ubuntu/testfs/sglang-venv/lib/python3.10/site-packages/vllm/model_executor/layers/linear.py", line 334, in forward
    output_parallel = self.quant_method.apply(self, input_, bias)
  File "/home/ubuntu/testfs/sglang-venv/lib/python3.10/site-packages/vllm/model_executor/layers/quantization/fp8.py", line 231, in apply
    return apply_fp8_linear(
  File "/home/ubuntu/testfs/sglang-venv/lib/python3.10/site-packages/vllm/model_executor/layers/quantization/utils/w8a8_utils.py", line 119, in apply_fp8_linear
    qinput, x_scale = ops.scaled_fp8_quant(
  File "/home/ubuntu/testfs/sglang-venv/lib/python3.10/site-packages/vllm/_custom_ops.py", line 32, in wrapper
    return fn(*args, **kwargs)
  File "/home/ubuntu/testfs/sglang-venv/lib/python3.10/site-packages/vllm/_custom_ops.py", line 348, in scaled_fp8_quant
    output = torch.empty(shape, device=input.device, dtype=torch.float8_e4m3fn)

Reproduction
CUDA_VISIBLE_DEVICES=2,3 python -m sglang.launch_server --model-path NousResearch/Meta-Llama-3.1-70B-Instruct --port 30003 --tp 2 --mem-fraction-static 0.93 --quantization fp8  --host <IP_ADDRESS> --context-length 2560  --max-num-reqs 15 --chunked-prefill-size 8192 --enable-torch-compile
Environment
Python: 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]
CUDA available: True
GPU 0,1,2,3,4,5,6,7: NVIDIA H100 80GB HBM3
GPU 0,1,2,3,4,5,6,7 Compute Capability: 9.0
CUDA_HOME: /usr
NVCC: Cuda compilation tools, release 12.2, V12.2.140
CUDA Driver Version: 535.129.03
PyTorch: 2.4.0+cu121
sglang: 0.2.13
flashinfer: 0.1.5+cu121torch2.4
triton: 3.0.0
transformers: 4.44.2
requests: 2.32.3
tqdm: 4.66.5
numpy: 1.26.4
aiohttp: 3.10.5
fastapi: 0.112.1
hf_transfer: 0.1.8
huggingface_hub: 0.24.6
interegular: 0.3.3
packaging: 24.1
PIL: 10.4.0
psutil: 6.0.0
pydantic: 2.8.2
uvicorn: 0.30.6
uvloop: 0.20.0
zmq: 26.2.0
vllm: 0.5.4
multipart: 0.0.9
openai: 1.42.0
anthropic: 0.34.1
NVIDIA Topology:
        GPU0    GPU1    GPU2    GPU3    GPU4    GPU5    GPU6    GPU7    NIC0    CPU Affinity    NUMA Affinity   GPU NUMA ID
GPU0     X      NV18    NV18    NV18    NV18    NV18    NV18    NV18    SYS     0-103   0               N/A
GPU1    NV18     X      NV18    NV18    NV18    NV18    NV18    NV18    SYS     0-103   0               N/A
GPU2    NV18    NV18     X      NV18    NV18    NV18    NV18    NV18    SYS     0-103   0               N/A
GPU3    NV18    NV18    NV18     X      NV18    NV18    NV18    NV18    SYS     0-103   0               N/A
GPU4    NV18    NV18    NV18    NV18     X      NV18    NV18    NV18    SYS     104-207 1               N/A
GPU5    NV18    NV18    NV18    NV18    NV18     X      NV18    NV18    SYS     104-207 1               N/A
GPU6    NV18    NV18    NV18    NV18    NV18    NV18     X      NV18    SYS     104-207 1               N/A
GPU7    NV18    NV18    NV18    NV18    NV18    NV18    NV18     X      SYS     104-207 1               N/A
NIC0    SYS     SYS     SYS     SYS     SYS     SYS     SYS     SYS      X

Legend:

  X    = Self
  SYS  = Connection traversing PCIe as well as the SMP interconnect between NUMA nodes (e.g., QPI/UPI)
  NODE = Connection traversing PCIe as well as the interconnect between PCIe Host Bridges within a NUMA node
  PHB  = Connection traversing PCIe as well as a PCIe Host Bridge (typically the CPU)
  PXB  = Connection traversing multiple PCIe bridges (without traversing the PCIe Host Bridge)
  PIX  = Connection traversing at most a single PCIe bridge
  NV#  = Connection traversing a bonded set of # NVLinks

NIC Legend:

  NIC0: mlx5_0

ulimit soft: 4096

@siddhatiwari Hey. Thanks for pointing this out. We've noticed this issue and will fix ASAP.
But I want to point out that torch compile right now only works for small models that can be served on only on GPU, like llama3.1-8b. For llama3.1 70b, even if you can compile it, the model would be slightly slower. (For 8b model it will be quicker of cause).
So please turn down compile for you 70b model. And we  will try to fix this bug.

torch.compile now only works for fp16, so your fp8 command will fail


[Question] Build not triggered when additional commits arrive in Pull Request

Hi. I've set up pipeline with PR resource in its simplest form. It checks BitBucket repo every 2 minutes.  When new PR arrives, Concourse build is triggered as expected and completes successfully.
Some time later I push additional commits to existing PR and expect it to trigger build again, but it does not happen.
Question: is it possible to trigger build again for newer commits? Thanks.

A few questions:

When you enter the resource history on the web UI for this resource, do you see the input, outputs and metadata of the commit, which should trigger the build?
Have you set up the version: every and trigger: true in the pipeline for that resource? Like that:

  - get: pull-request
    trigger: true
    version: every

We are using that resource in couple of our pipelines and it generally works.

Hmm. Starting from today it works as expected. Seems that source of the problem with PR was on Bitbucket.org side:
https://community.atlassian.com/t5/Bitbucket-articles/Extinguishing-our-performance-fires-and-rebuilding-for-the/ba-p/1679820#M1048
Thank you @mkocus.


RegExp named capture groups don't get transpiled

TypeScript Version:
3.7.2 (3.7.4 and nightly (3.8.0) as well)
Search Terms:
Named capture groups
Named capturing groups
Regex
ES2018.RegExp
Expected behavior:
The named capture group in the regex gets transpiled to the correct target (es5 in our case). Something like what @babel/plugin-transform-named-capturing-groups-regex does?
Actual behavior:
The named capture group ends up in the compiled code while only Chrome currently supports this.
Related Issues:
https://github.com/microsoft/TypeScript/issues/31241
Code
const regex = /^(?<name>[A-Za-z]+)/;
const match = regex.exec('MatchThis-NotThis');
console.log(match);

Live Playground
Here
Additional information
I'm not 100% sure if this is something that TypeScript actually should be doing so if that's not the case I'd like to get some details on how to properly transpile this.

We don't currently inspect RegEx bodies to see if they're compatible with the current target, since this is the first (?) new syntax in a long time.


Merge missing translations

This is the last batch of "language related changes" from me for now.
Note that before this gets merged, the dummy Norwegian translation needs to be disabled in config.toml.
It's easier to get a grasp of this PR by looking at the content tree for the Norwegian translation:
content/no
├── _common-resources
│   └── index.md
├── _index.html
├── blog
│   ├── _index.md
│   └── _posts
│       └── 2018-09-06-2018-steering-committee-election-cycle-kicks-off.md
├── case-studies
│   ├── _index.md
│   └── adform
│       └── index.html
└── docs
    ├── _index.md
    ├── contribute
    │   └── _index.md
    ├── home
    │   └── _index.md
    ├── reference
    │   ├── _index.md
    │   └── glossary
    │       ├── container.md
    │       └── index.md
    ├── setup
    │   ├── _index.md
    │   └── pick-right-solution.md
    └── tutorials
        └── kubernetes-basics
            └── _index.md

In summary, this is what's needed for a new language:

The section content files (see "_index*", esp. note the home page) with its menu definitions.
A translation of the language bundle in /i18n
A language configuration in config.toml

In that language configuration, you can specify an ordered list of one or more languages to fill inn missing translations from. In this PR, no has this set to language_alternatives = ["en"].
This language merging has an effect in

Blog. The last blog entry from language_alternatives will be shown on front page if not translated. Also, the archive is merged.
Docs browser
Docs left tree nav
Glossary page, glossary tooltip
Case studies

Links to "foreign language" is marked with its language and opens up in a new window.
There is certainly more to be done in this area (the glossary page contains some untranslated text, and the user journey is only available in English, to mention some examples. But think now at least it makes sense to let other languages in.)
This PR updates Hugo to 0.48. That is built with Go 1.11, which makes the relevant template constructs much simpler.
/cc @zacharysarah @chenopis

There seems to be a logical flaw in the blog archive ... I will fix that tomorrow.

Re. my comment above: I found a bug in Hugo that needs to be resolved for this PR to work 100%. I will get that into a planned released for Monday.

I have bumped the Hugo versions to 0.49 in this PR, which has fixed the "language merge" issue on the blog archive.
/cc @zacharysarah

@bep 👋 Thanks for your work here. Some questions:

Note that before this gets merged, the dummy Norwegian translation needs to be disabled in config.toml

To disable the dummy translation, is it sufficient to remove this block from config.toml:
[languages.no]
title = "Kubernetes"
description = "Production-Grade Container Orchestration"
languageName ="Norsk"
weight = 3
contentDir = "content/no"
# A list of language codes to look for untranslated content, ordered from left to right.
language_alternatives = ["en"]

...or must we also remove file content: i18n/no.toml, content/no/?
I can't think of a good reason to keep the dummy files ☝ after this PR merges, but am curious as to whether they must be removed entirely for Hugo to be happy or can simply be disabled in config.toml.

@zacharysarah No, it's easier than that, see my comment in config.toml:
# This is currently used for testing.
# disableLanguages = ["no"]

The above can also be set as an OS environment variable (I will dig up the syntax if you need it), and its main motivation is to use when you're in the process of translating a new language.

@bep

No, it's easier than that, see my comment in config.toml:

Cool! :sparkles: From the OP:

Note that before this gets merged, the dummy Norwegian translation needs to be disabled in config.toml.

I  disabled the dummy translation in a separate commit. It works in the preview, so let's go ahead and merge.
/cc @lucperkins 👋 You may have to resolve merge conflicts in #10373 and #10381 due to changes in Makefile.

/lgtm
/approve


PLACEHOLDER - CONVERT APP TO USE SWAGGER / FLASK-RESTX

This is a reminder issue to create individual stories for migrating various parts of the core application to Swagger / Flask-RESTX format as described in lecture on 7/27. This can be closed directly after the new stories are created.

Covered by #49, #69-74.


Improve the transfer tutorial

At the moment, the transfer tutorial is the best place for seeing how atomkraft works.
However, it should be updated with respect to recent changes (e.g., not downloading model checkers directly, but through atomkraft etc.).
Overall goal is to have it as a simple tutorial in which everything is done through atomkraft..

Related issues:

https://github.com/informalsystems/modelator/issues/241

It's possible to disable the Copy button on GitHub: https://github.com/squidfunk/mkdocs-material/issues/2418

I see the copy button as a feature. Not sure that it makes sense to disable a user-feature for the sake our e2e tests.
Would it make sense to generate a duplicate file? (Then we are certain there will be no divergence.)


Investigate ConnectorSink's use of Pony runtime backpressure

During work on PR #3013, I encountered a couple of test runs where ConnectorSink's use of the Pony runtime's Backpressure mechanism caused a deadlock.  The problem should be investigated thoroughly and, if repeatable, fixed.

The specific case is when a ConnectorSink TCP connection is closed by the connector process (via intentional close or via process crash).

NOTE: PR #3042 removes use of Pony runtime backpressure entirely but does not add a replacement backpressure mechanism.

I'll put add a commit to PR #3042 which fixes this particular problem ... but also should not be used as a general technique for solving this kind of deadlock problem.


Increase package extension names char limit to 30

Previously, the package extension names' char limit was set to 20 which flagged com.azure.resourcemanager.kubernetesconfiguration.models. After discussing with @JonathanGiles, relaxing this limit to 30 chars instead.

CI pipelines completed successfully, overriding check enforcer
https://dev.azure.com/azure-sdk/public/_build/results?buildId=780955&view=results

/check-enforcer override


Update to use eth_utils.toolz indirection for imports

What is wrong?
This library currently specifies cytoolz as a hard dependency.  This makes pypy support more difficult.
How can it be fixed?

Remove cytoolz from the direct dependencies.
Update the eth-utils requirement to be >=1.3.0,<2
Update all imports that come from cytoolz to instead come from eth_utils.toolz

I am on it!

@pipermerriam , as I have not seen any progress on this issue, I have worked on this and fixed this. Please review #76 for merging.

Also eth-utils 1.3.0 is in beta phase, and have added the same name in the setup.


I am trying to do RandomizedSearchCV on ABOD, but surprisingly it does not run?

Here is my code:
from pyod.models.abod import ABOD
param_grid = {'neighbours': list(range(1, 5,1)),
'contamination': np.linspace(0.01, 0.05, 5)}
skf = StratifiedKFold(n_splits=10)
folds = list(skf.split(X.toarray(), y_true))
clf = ABOD()
scoring = make_scorer(precision_score)
search = RandomizedSearchCV(estimator=clf, param_distributions=param_grid, scoring=scoring, cv=folds)
search.fit(X.toarray(), y_true)
y_pred= search.predict(X.toarray())
print('Best parameters:%0.10f' % search.best_params_["contamination"], 'Precision score: %0.3f' % precision_score(y_true, y_pred),
'Recall score: %0.3f' % recall_score(y_true, y_pred))
Best parameters:0.0100000000 Precision score: 0.000 Recall score: 0.000

The result makes sense to me. Just want to bring up some other points to consider:

ABOD is an unsupervised learning method. If you could do parameter search, you do have the ground truth (labels y) of the training data. If that is the case, what about treating it as a supervised problem with skewed class (data imbalance)? I guess if you simply run your data with an XGBOOST classifier, the result may be better than unsupervised approaches, e.g. ABOD.

You could verify if the percentage of the outliers in your data is closer to 0.05 than 0.01 and 1. If that is true, I think the result is ok.

Not sure about the version of Pyod you are using. You may want to update to the latest version since it is updated everyday (it is not in production stage yet), which can be done "pip install --upgrade pyod"

Let me know if you have other questions:)
Yue

I am only considering extremely imbalanced datasets
MinorityClassSize / MajorityClassSize < 0.20


Installer code still uses tabs for indentation

We should use 4 spaces as per PSR.
@brendo Can I do it directly into integration or should I send a PR ?

You can fix this directly, it's low risk :)

Ok, but after my work on the installer is pulled in, to avoid conflicts :)

In progress...

Confirming that only line feeds were added: https://github.com/DeuxHuitHuit/symphony-2/commit/f7d607f00630ff3cb08f4902fe2cfab33267f852?w=0

Same for this one: https://github.com/DeuxHuitHuit/symphony-2/commit/eca1f41c95bc4a74af4e4f319ca879fc4a0cac8e?w=0
Done.


Feature Request - Allow to run locally

I managed to make it run on Tomcat as a WAR file with some playing with maven profiles, but it's not exactly the same as the ApiGatewayRequestContext is not available in an offline / local war deployment. It will be nice if there was a built in way to run the app locally as a Spring application with similar RequestContext behavior as in a lambda deployment.

@eranation I'm wondering if we should do some research on how to run applications written with this library using the new sam-local: https://github.com/awslabs/aws-sam-local - what do you think?

For the Spring Boot project I easily made a new submodule with a simple class and a dependency to my lambda module. The class looks like:
@EnableAutoConfiguration
@ComponentScan("com.xxx.xxx.xxx.xxx")
public class XXXAppplication {

    public static void main(String[] args) {
        SpringApplication.run(XXXAppplication.class, args);
    }

}

I also added a dependency to spring boot so I can run it from the main in a tomcat:
  <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-web</artifactId>
            <version>1.5.6.RELEASE</version>
        </dependency>

It works just fine.

All 3 supported frameworks can be started locally with an embedded container, this allows you to test your application. To emulate API Gateway and Lambda's behavior you are definitely better off using the aws-sam-local project. The sample applications included in this repo have a basic SAM template you can just re-use.
I'm closing this issue for now.


Update libxml_ruby version

As per https://github.com/xml4r/libxml-ruby/issues/49, older versions of libxml_ruby struggle with libxml2-2.9.0.
I have updated to the latest version of libxml_ruby - all specs pass.

@voxxit, when do you release the current master v0.3.5 to rubygems? :)


Add tests for template literal with backslashes

with regard to #429, the bug in res_printer has been addressed at some point I guess?

Thanks for this.


Where is ocrd_training?

IIUC the repos docs and ocr-d.github.io where integrated here.
Then I don't understand why there's no reference to https://github.com/OCR-D/ocr-d.github.io/blob/master/docs/ocrd-training.md anywhere on the website.
And is this issue in the right repo?

I guess this issue is dublicating https://github.com/OCR-D/ocrd-website/issues/101? So we can close this one @bertsky ?

I wouldn't strictly call it a duplicate. But yes, if the intention is to re-introduce the training notes, which #101 depends on, we can close here I guess.


when Access is deleted, return and not process next logic.

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
when Access is deleted, return and not process next logic.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?

NONE

@yanggangtony nice finding, thanks


Add option to hide group name in window title

In v0.3, the group name is displayed in the window title. While it is a sensible addition, it breaks the window recognition of some password managers (eg. KeePassXC window associations).
A way to fix this would be to add an option to hide the group name in the window title.

I will add an option for it


Premium stroage support

Since Premium Storage doesn't support page, Is it possible to use packer-azure with Premium Storage  VMs?
Thanks.

Sorry for the late response, I"m just returning...
I haven't tried this scenario, but packer-azure does not operate at a level where it makes this distinction.  All of the APIs it operates with don't care (to my knowledge).  Do you a gist of the Packer config that you can share so I can validate it.

You are correct. It's working. Closing the issue.


Code refactoring and simplification

Two functions, GetAllRawContainers and GetSummary, both started by building an URL. For both functions, the step of building that URL was semantically equivalent although their code was slightly different (which I found confusing).
I factored-out that common functionality into  two functions, getScheme and getUrl, and now GetAllRawContainers and GetSummary just call getUrl

This change is

/ok-to-test
please squash the fixup down into the original commit.  Otherwise looks good.

@DirectXMan12 rebased and switched to using host.String() as you said. Good catch, thanks!

Anything else we need to wrap this up?

/lgtm
Thanks @atzannes for your contribution.

it's my pleasure


fix: bump edge-runtime to 1.58.3

What kind of change does this PR introduce?
Bump edge-runtime to 1.58.3
Changes
1.58.3 (2024-09-10)
Bug Fixes

improve stability (#406) (50eb636)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>9
Details

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.03%) to 60.017%

Files with Coverage Reduction
New Missed Lines
%

internal/storage/rm/rm.go
2
89.53%

Totals

Change from base Build<PHONE_NUMBER>6:
0.03%

Covered Lines:
6363

Relevant Lines:
10602

💛  - Coveralls


Fixed syntax error in PHP < 5.4

Raised an "unexpected T_OBJECT_OPERATOR" syntax error in PHP < 5.4

Thanks, is included in the next release


crashed by

please describe your problem.

Are you in a terminal? If so, this would be expected because ctrl-s is a terminal control character to stop character output. Try pressing ctrl-q.

I never understood why Vim doesn't use the terminal ioctls to disable ctrl-s/ctrl-q handling like it does for ctrl-c and ctrl-backslash.

ctrl-s / ctrl-q is set by the terminal.  It's not Vim specific.  If you don't want them, disable them in the terminal.  This probably works:  stty -ixon


[LogicApps Integration Account] : Examples included for integration account Api's

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] Validation errors from the Linter extension for VS Code have all been fixed for this spec. (Note: for large, previously checked in specs, there will likely be many errors shown. Please contact our team so we can set a timeframe for fixing these errors if your PR is not going to address them).
[x] The spec follows the patterns described in the Swagger good patterns document unless the service API makes this impossible.

@amar any clue what the schema validator is complaining about? (https://travis-ci.org/Azure/azure-rest-api-specs/jobs/208444863) it says "is an invalid JSON" for every example although it looks pretty valid to me - or is it a schema error?

@olydis - I am pulling the changes and trying to repro locally on my box. Will get back to you shortly.

After making some quick fixes for resourceGroupName in the example, I ran the model validator locally and found the following issue:
Azure swagger model validation using x-ms-examples and examples in spec
error: Found errors in validating the response with statusCode "200" for x-ms-example "Get IntegrationAccount callback URL" in operation "Integration
Accounts_GetCallbackUrl".:

{ code: 'RESPONSE_VALIDATION_ERROR',
  message: 'Found errors in validating the response with statusCode "200" for x-ms-example "Get IntegrationAccount callback URL" in operation "Integr
ationAccounts_GetCallbackUrl".',
  innerErrors:
   [ { code: 'INVALID_RESPONSE_BODY',
       errors:
        [ { code: 'OBJECT_ADDITIONAL_PROPERTIES',
            params: [ [ 'queries', 'basePath' ] ],
            message: 'Additional properties not allowed: queries,basePath',
            path: [],
            description: 'The callback url.' } ],
       message: 'Invalid body: Additional properties not allowed: queries,basePath',
       path: [] } ] }
{ AssertionError: swagger "/Users/amarz/sdk/azure-rest-api-specs/arm-logic/2016-06-01/swagger/logic.json" contains model validation errors.
    at /Users/amarz/sdk/azure-rest-api-specs/test/model.js:21:14
  name: 'AssertionError',
  actual: false,
  expected: true,
  operator: '==',
  message: 'swagger "/Users/amarz/sdk/azure-rest-api-specs/arm-logic/2016-06-01/swagger/logic.json" contains model validation errors.',
  generatedMessage: false }
    1) /Users/amarz/sdk/azure-rest-api-specs/arm-logic/2016-06-01/swagger/logic.json should have valid examples.

No modification for NodeJS

No modification for Python


Introduce 'create-archive.download'

Add a new download key to create-archive. From a functional point of it should be similar to sources: download the source-archive(s) from the URL(s) provided and save them to path.
To be implemented after #1641.
This change is needed to support customizing source-git update-dist-git (see packit/research#150).

Hello all,
as part of a backlog cleanup, we are closing source-git-related issues because it is not our priority anymore and if we were to change the priorities, the whole source-git project would need to be revisited nevertheless.
A more detailed description of why have come up with this can be found at https://packit.dev/source-git/status (most of this is still relevant), TLDR is that we can provide more benefits in other areas.
What now:

The service part is currently being decommissioned for no real use. (It even was offline for a couple of weeks because of a certificate issue and no one realised.)
The CLI is still there, but the Packit team won't work on these tasks. We are happy to help and accept any external contribution.
If you find something really, really important and can't do it yourself, let us know. We might still find a way but we would need to be really sure that our time spent on this is worth the benefit.

Our current priorities are visible on our board (revisited quarterly) and are based on user benefit and demand. (=> You can influence that..;)
František


SL Review - Communication with senior leaders before the review process starts

The scope of this story has changed, now only ADMs need to fill the form. Also see #15, might be a duplicate.
Notes from UX Sessions-

Time/deadlines need to be communicated
Encourage people to consult people who have worked closely with the senior leader or to have a conversation with the senior leader
Ensuring eligible senior leaders know about the process so that they don't feel excluded.
Making it clear that this is an iterative improvement over the previous process & we are still working on resolving the issues with previous SL review initiatives.

Action items -

We need to decide where this communication will sit.

Do we need a page on Careers & MyHR website
Do we need to include it in the emails sent
OR is the "about the review process" section in the form enough

We need to start drafting the copy

We want to ensure the following in all communications around the senior leader review process -

We want to be transparent about the review process. Those who will go through the review process & even those who are not eligible yet to go through review process should clearly understand the process.

We also want to be transparent about how this data will be used. Will i get an advantage in being considered for an ADM role? Is this just to get comprehensive feedback from my supervisor & other ADMs? Is this just to get targeted learning development programs?

We want to ensure senior leaders understand the value of going through the review process.
However, we also want to ensure they understand that this is a completely voluntary process. It is not necessary to go through the review process to apply for an ADM/DM position at a later stage.
We also want to ensure both senior leaders & supervisors understand the timelines before which they need to complete the form, have the conversation and sign off

To achieve this the following ideas have been proposed -

A landing page before the SLR form is accessed
An FAQ page
A popup/banner message the lets people know if they are ineligible to go through the review process.
The email they receive with the link to the landing page

Action items -

We need to decide which of these ideas we will implement for MVP
We need to start drafting the copy

The communications plan and tactics are not in scope for the PSA/TES scrum team, although this work is important when considering the user/audience experience and how/where they will access the form.
Communication planning will be initiated and managed by the SL team (and supported by PIE - Andrea Gillis (corporate) and or Lauren Grindler (PSA). The plan will help the SL team determine communications objectives and outline the recommended tactics and key messages.
The Careers and MyHR content team will also support development of any content development that is needed for the Careers & MyHR website as a tactic within the communications plan. This work can begin asap and should complement the communications plan.
Recommendation to SL to get in touch with PIE/Comms as soon as possible.

One of the considerations and decisions to be made is to have all content related to senior leaders in a TEAMS channel and the link to the form and all relevant content will be available there. - @JodiLittle

Eddie is looking into what is the best option - MS Teams or Compass. Pros/Cons/Recommendation. Decision to come

Eddie is working on the design of the MS Teams Channel for ADMs to access the form and supporting information. Targeting Oct 4 to be ready for UX testing of form


Fixing task annotations for actions

flyby: simplify hello_world_distributed

Fixes #4652

@khuck could you please check whether this fixes the issue for you?

testing it now...

@khuck could you please check whether this fixes the issue for you?

Yes, works great!  Thanks!

Looks like I have some labeling issues in APEX, but the profiling is working...


Putting the display task into second core on ESP

Hi 2dom,
Instead of messing around with the interupts in handling the display, would it not be an idea to put the display handling in core 0 of the ESP32 as task ?
This is then always securing the refreshrate and will not have to do with any other handling of code. How to do this efficiently and if it will work is something I can not judge at the moment but it would be a good use of the second core in the ESP32 module, don't you think ?

I tried this before not with much success. Feel free to try and send a pull request if you get it to word :)

I've had good success with the opposite, run PxMatrix on the regular Arduino core and run some other stuff (i2c and maths calculations for the falling sand project) on core 0. I will share my code the next time I'm on my PC


Ask for code help

Thank you for your article and code, which gave me a lot of help. I encountered difficulties during the experiment. I would like to ask if you can share with me the code to reproduce the previous defense method in the paper experiment, because my code I have limited abilities and can't do it myself, if you can help me, I will be very grateful！！

Hi @LongJinhe-coder, thank you for reaching out and I'm glad to hear that our article and code have been helpful to your research.
Regarding your request for reproducing previous defense methods mentioned in our paper, I encourage you to refer to the original authors' GitHub repositories or the algorithms detailed in their papers. Best of luck with your experiments.


chore: add move asset files to a dedicated submodule

This should help us to keep a clean repo in the long term
Scope

[x] Repository

Type of change

[x] Chore

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 74.91%. Comparing base (4e2d52d) to head (a7325e8).

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #125      +/-   ##
==========================================
- Coverage   74.96%   74.91%   -0.05%
==========================================
  Files          32       32
  Lines        3627     3632       +5
==========================================
+ Hits         2719     2721       +2
- Misses        908      911       +3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Closing this as @cedricchevalier19 suggested that there might be smarter way to do this. We can also look into github LFS when we'll deal with larger meshes (i.e. benchmarking instead of debugging).


Error with CanonicalAlgorithm implementation

CanonicalizationAlgorithms  = {
        "http://www.w3.org/2001/10/xml-exc-c14n#": ExclusiveCanonicalization,
        "http://www.w3.org/2001/10/xml-exc-c14n#WithComments": ExclusiveCanonicalizationWithComments,
        "http://www.w3.org/2000/09/xmldsig#enveloped-signature": EnvelopedSignature
    };

All algorithms have got process function, but with different result types
EnvelopedSignature.process(node: Node, options?): Node;
ExclusiveCanonicalization.process(node: Node, options?): string;
ExclusiveCanonicalizationWithComments.process(node: Node, options?): string;

It can be a problem with createSignature function
https://github.com/yaronn/xml-crypto/blob/master/lib/signed-xml.js#L701-L704
because signatureAlgorithm.getSignature needs signedInfo: string | Buffer

You are right that this is confusing and bad coding. I don't expect this to be a problem in practice since an EnvelopedSignature does not make sense as a canonicalization algorithm for the signature. But we should definitely get rid of this when we have a chance.

The same error with
var canonizedSignedInfo = canAlgorithm.process(node);
var signatureAlgorithm = this.findSignatureAlgorithm(this.signatureAlgorithm);
this.signatureValue = signatureAlgorithm.getSignature(canonizedSignedInfo, this.signingKey);

process - can return Node
getSignature - 1 param must be string

We ended up fixing this in our implementation derived from this great package :  https://www.npmjs.com/package/xadesjs

Any pointers on how to fix this?
I do not have understanding of what the node is, but I would like to make the return type string for process method of the enveloped algorithm as I have immediate need for the same.
Otherwise are their any known mature implementations which do the same?

@avckp can you share the code that consumes xml-crypto? I want to understand the sequence of algorithms.

@yaronn I need to generate the signature in the following format
<Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
	<SignedInfo>
		<CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315" />
		<SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1" />
		<Reference URI="">
			<Transforms>
				<Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature" />
			</Transforms>
			<DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
			<DigestValue>2QvzuMcZU/D6Nbk3lmUaxupnzG8=</DigestValue>
		</Reference>
	</SignedInfo>
	<SignatureValue>R5TfpMgiKT7...</SignatureValue>
	<KeyInfo>
		<X509Data>
			<X509SubjectName>....</X509SubjectName>
	<X509Certificate>.....</X509Certificate>
		</X509Data>
	</KeyInfo>
</Signature>

My code looks like
 var sig = new SignedXml();
      sig.addReference("//*[local-name(.)='Hmac']");
      sig.signingKey = fs.readFileSync("certs/keyfile.key.pem");
      sig.keyInfoProvider = new MyKeyInfo();
      sig.canonicalizationAlgorithm = "http://www.w3.org/2000/09/xmldsig#enveloped-signature";
      sig.computeSignature(xml);

Signing with this algorithm was failing (as enveloped-signature returns node in place of string), I modified the SignedXml.prototype.createSignature to use
706  this.signatureValue = signatureAlgorithm.getSignature(**canonizedSignedInfo.toString()**, this.signingKey)
While it gives me output, I am not sure what I am doing here.
Am I supposed to convert the node to string inside the transform.process itself?
Also my output has
<CanonicalizationMethod Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>
and
<Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
I am expecting it to be
<Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature" />

I think you mixed the algorithms you need. The right place to add the enveloped transformation is here:
  sig.addReference("//*[local-name(.)='Hmac']", ["http://www.w3.org/2000/09/xmldsig#enveloped-signature"]);

As for the canonicalization algorithm (http://www.w3.org/TR/2001/REC-xml-c14n-20010315), that algorithm is not supported yet. The documentation explains how to add algorithms if you want but it is sometimes time consuming. It is not always true, so not sure I would recommend it for produciton use, but I think in many cases that algorithm is the same as exclusive canonicalization so for testing you could try to do this:
SignedXml.CanonicalizationAlgorithms['http://www.w3.org/TR/2001/REC-xml-c14n-20010315'] = SignedXml.ExclusiveCanonicalization;
sig.canonicalizationAlgorithm = "http://www.w3.org/TR/2001/REC-xml-c14n-20010315";

@yaronn  I added as you recommended but I got the following error:
Possibly unhandled Error: canonicalization algorithm 'http://www.w3.org/TR/2001/REC-xml-c14n-20010315' is not supported
at SignedXml.findCanonicalizationAlgorithm (/Users/FraGoTe/Documents/Projects/xxx/node_modules/xml-crypto/lib/signed-xml.js:292:14)

I did :
 SignedXml.CanonicalizationAlgorithms['http://www.w3.org/TR/2001/REC-xml-c14n-20010315'] = SignedXml.CanonicalizationAlgorithms['http://www.w3.org/2001/10/xml-exc-c14n#'];

    sig.canonicalizationAlgorithm = 'http://www.w3.org/TR/2001/REC-xml-c14n-20010315';

But i got the same <ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>

@FraGoTe make sure the first line you pasted is called before the second one. You can also try to hard code that algorithm here just to test https://github.com/yaronn/xml-crypto/blob/master/lib/signed-xml.js#L225

Could anyone run it for that algorithm?
sig.canonicalizationAlgorithm = 'http://www.w3.org/TR/2001/REC-xml-c14n-20010315';
Any tips how to apply this?

Fixed in #116


Add Shubham Chaudhari to contributors.md

Hi Brad,
Thanks for creating this space. I have added my name and area of interest accordingly.
Thank you!

Also fixing a typo in your readme.
Thank you!


[Usabilla] Search feedback

Search query: https://www.nuget.org/packages?q=boost_python36-vc142
Comment:   Results that do not contain the keywords I'm searching for

Using spaces instead of underscores and dashes yields better results: https://www.nuget.org/packages?q=boost+python+vc142
The "banana split" improvement doesn't help here because the desired results don't match all the tokens boost, python, 36, vc, and 142. We should compare the tokens generated by the Azure Search analyzer for the boost_python36-vc142 and boost python36 vc142 queries.

This is fixed with the camel-split enhancement (https://github.com/NuGet/NuGet.Jobs/pull/925).

Well


add a new parameter for maven: -Duse.local.thrift.compiler (false by default)

Now downloading a thrift compiler using maven-exec-plugin is too slow for Unix (40MB size).
If someone has installed thrift-compiler by apt install thrift-compiler=0.9.1-2.1 (which is far faster...), there is no need to download the thrift compiler again.
So, I add a new parameter, ${use.local.thrift.compiler} to skip the downloading process.
By default, it is false, which means maven will download the correct compiler and use it. So everything runs well as normal.

Is it necessary to add this parameter?
If we ask user to set use.local.thrift.compiler = true and configure thrift path manually, this will lead to many unforeseen mistakes because of unknown operations from user. In my opinion, 40MB size is not very large and only need to downloaded once. Also, we will provide a docker image with all dependencies installed in the future.

Is it necessary to add this parameter?
If we ask user to set use.local.thrift.compiler = true and configure thrift path manually, this will lead to many unforeseen mistakes because of unknown operations from user. In my opinion, 40MB size is not very large and only need to downloaded once. Also, we will provide a docker image with all dependencies installed in the future.

Downloading it will takes more than 20 minutes....
Normally, users do not need to use this parameter. But if they want to do like this, we give them an option.
As the comments say: if true, you must set the thrift compiler into your PATH, and make sure the version is ${thrift.version}

Are you sure it takes 20 minutes to download thrift-compiler rather than other maven dependencies? If network is poor, it also requires lots of time to download maven dependencies

Are you sure it takes 20 minutes to download thrift-compiler rather than other maven dependencies? If network is poor, it also requires lots of time to download maven dependencies

At least in China the speed is poor, you can have a try by  checkout the branch enable_docker_image, and run docker build -t test:v1 .
But in other countries, it is fine. On travis, the Ubuntu image only takes several minutes.

I find another method which do not need to modify the pom.xml... I will try it.

This method is not friendly for users, I will close this PR and remove the branch.


Cyrillic character sent by game instead of Latin character

[Master HamsterKombat Bot][INFO] 2024-08-27 02:03:55 [Account 10] Best upgrade is Сoindesk with profit 193 and price 159.84k, Level: 14
--- Logging error ---
Traceback (most recent call last):
  File "C:\Program Files\Python312\Lib\logging\__init__.py", line 1163, in emit
    stream.write(msg + self.terminator)
  File "C:\Program Files\Python312\Lib\encodings\cp1252.py", line 19, in encode
    return codecs.charmap_encode(input,self.errors,encoding_table)[0]
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
UnicodeEncodeError: 'charmap' codec can't encode character '\u0421' in position 85: character maps to <undefined>
Call stack:
  File "C:\Users\FARM\Downloads\Hamster Kombat\MasterHamsterKombatBot-main-7\main.py", line 1554, in <module>
    main()
  File "C:\Users\FARM\Downloads\Hamster Kombat\MasterHamsterKombatBot-main-7\main.py", line 1548, in main
    asyncio.run(RunAccounts())
  File "C:\Users\FARM\Downloads\Hamster Kombat\MasterHamsterKombatBot-main-7\main.py", line 1515, in RunAccounts
    account.Start()
  File "C:\Users\FARM\Downloads\Hamster Kombat\MasterHamsterKombatBot-main-7\main.py", line 1409, in Start
    if not self.BuyBestCard():
  File "C:\Users\FARM\Downloads\Hamster Kombat\MasterHamsterKombatBot-main-7\main.py", line 718, in BuyBestCard
    log.info(
Message: '[Account 10] Best upgrade is Сoindesk with profit 193 and price 159.84k, Level: 14'
Arguments: ()
[Master HamsterKombat Bot][INFO] 2024-08-27 02:03:55 [Account 10] Attempting to buy the best card...

I know this is because of the updates in https://github.com/masterking32/MasterHamsterKombatBot/pull/238 which have been fixed by adding kwargs['encoding'] = 'utf-8' but it might be useful to know.

We don't have any support for PRs, Just Merged PRs can be checked.


Changing text color

Hi, first of all, thank you for this. I cannot change the text's color neither title's color. It is weird because I'm able to change the image's style.
textStyle: styles.title (doesn't work)
imageStyle: styles.image (works)

Thank you in advance!
Luis

Hi @luisbajana
Thanks for the bug report. Could you post your render-method and also the styles-object you're referring to?

Sure,
My styles-object:
const styles = StyleSheet.create({
container: {
flex: 1
},
welcome: {
fontSize: 20,
textAlign: 'center',
margin: 10,
fontFamily: "Comfortaa-Bold"
},
title: {
fontSize: 12
},
instructions: {
textAlign: 'center',
color: '#333333',
marginBottom: 5,
},
image: {
width: 200,
height: 200,
}
});
My render method:

And the slides-object, please. Sorry.

I've just tested on the example project and everything seems to be working on my end. Have you tried changing the color in the title-style? Also note that you've only included the textStyle-property in the first slide.

Hey Jacob, thank you for your answers. I don't know what's going on, I think I tried everything, and still doesn't work :/

Styles

const styles = {
container: {
flex: 1
},
titleSlide: {
color: 'black',
fontSize: 32
},
textSlide: {
color: 'black',
fontSize: 22
},
instructions: {
textAlign: 'center',
color: '#333333',
marginBottom: 5,
},
image: {
width: 200,
height: 200,
}
}

Slides object

const slides = [
{
key: 'key4',
title: 'Title 4',
text: 'Text 4',
image: require("./components/common/img/conexion.png"),
imageStyle: styles.image,
backgroundColor: '#136AC7',
textStyle: styles.textSlide,
titleStyle: styles.titleSlide
},
{
key: 'key3',
title: 'Title 3',
text: 'Text 3',
image: require("./components/common/img/seguro.png"),
imageStyle: styles.image,
backgroundColor: '#FFAD17',
textStyle: styles.textSlide,
titleStyle: styles.titleSlide
},
{
key: 'key2',
title: 'Title 2',
text: 'Example text 2',
image: require("./components/common/img/expertos.png"),
imageStyle: styles.image,
backgroundColor: '#B62599',
textStyle: styles.textSlide,
titleStyle: styles.titleSlide
},
{
key: 'key1',
title: 'Title 1',
text: 'Example text 1',
image: require("./components/common/img/music.png"),
imageStyle: styles.image,
backgroundColor: '#0EA30B',
textStyle: styles.textSlide,
titleStyle: styles.titleSlide
}
];

I'm returning this in the render method:

return(
<AppIntroSlider
slides={slides}
onDone={ ()=> { this.setState({ tour: false }) } }
nextLabel={"Siguiente"}
doneLabel={"Listo"}
/>)

My package JSON looks like this:
"react-native-app-intro-slider": "^0.2.2",
"react": "16.0.0-beta.5",
"react-native": "0.49.3",
"react-native-app-intro-slider": "^0.2.2",

Thank you for your time.

@luisbajana Still not working?

Closing for inactivity. Feel free to reopen, @luisbajana.

any updated answer?


Adding a global button click delay?

Most of the Buttons in my app perform actions that cause the Button to disappear (dismiss some information, change modes, etc). So when I tap a Button with my touch pad, the mouseDown and click events happen so close together that I never get to see any of the Ripple animation. It's actually a little disconcerting.
Any tips on how I might add a global delay for click events on Buttons?
I thought I'd sub-class or fork Button, but react-toolbox uses Button a lot internally as well (in Navigation, in particular), so that wouldn't get all the buttons.
I thought of patching Button, but I don't know how I'd make that configurable, because I'm sure most people want buttons that react immediately.

This sounds great mterestmgw

Hi @alltom In my opinion the best option is handle the delay in the callback of onClick, but if you think is better create a property like delay we are open to any proposal.
best,
javi

Thanks, good suggestions. It looks like I'll have to manually decorate every affected button no matter which strategy I choose, so I may as well go the non-invasive route and wrap my onClick callbacks with a delay.

I think it's ok to add a delay prop to delay the onClick callback if you need it.
Wouldn't that be a solution @alltom ?


LegacyVersion has been removed from packaging.version

docs_versions_menu version: latest (0.5.0+dev)
Python version: 3.10
Operating System: linux

Description
LegacyVersion was removed. Trying to use it raises an error:
Extension error:
Could not import extension docs_versions_menu (exception: cannot import name 'LegacyVersion' from 'packaging.version' (/[...]/site-packages/packaging/version.py))
ERROR: InvocationError for command /[...]/bin/sphinx-build -M html . _build (exited with code 2)

What I Did
https://github.com/awoimbee/docs_versions_menu/commit/d6063fd0ccf26bfce6a9fcf07c9251863d16ec3a

The packaging library removed LegacyVersion in their release 22.0.
I'm going to pin packaging < 22.0 until I can work around this.


componentWillReceiveProps has been renamed

hi, I get the following waring:
componentWillReceiveProps has bee renamed, and is not recommended fo use.

I get it too!

I fix seems to have been merged : https://github.com/jeanregisser/react-native-slider/issues/169


Fixes CSS issues. Moves Spotify details to bottom panel.

@lefoy
Hopefully resolves #14.
Also moves Spotify details from status bar to bottom panel. Prefer this to atomify in status bar? Reasoning is that on smaller screens / with a lot of packages populating the status bar Spotify details are not seen.

My two cents are that it's better on the status bar...


Don't Merge! PR real time test for webhook case

Docs Build status updates of commit 20a92cb:
:clock10: Pending: waiting for processors (21 builds ahead of you)
:warning: Docs Build is busy, currently there are 21 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 20a92cb:
:clock10: Full build: the average full build time is 7 min(s) 28 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit 20a92cb:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/testing.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Grow to fit & shrink to fit worker imbalances

As part of the learning process for working on #1722 and #1619 was studying how grow to fit's allocation of stateful steps to workers is currently done.  I discovered that the algorithm used by PartitionRebalancer.step_count_to_send() creates some very odd imbalances, especially as the ratio of partitions to workers approaches one.
See https://gist.github.com/slfritchie/1f9afb3c0636da9ae102c768947dff04 for the partition assignments as a simulated cluster incrementally grows from 1 to 12 workers (or 16 workers).
Part of this work should include adding more unit tests around PartitionRebalancer to capture these cases.

The contents of the above gist are dated, but the bug is still around, and I'm running into it with larger autoscale tests, so here is a new gist that applies to the current bug I'm seeing against the current rebalancing algorithm
https://gist.github.com/nisanharamati/073ca2ec4cb29f7df29604d6aa2a1773
cc @jtfmumm this is the same error I'm running into with the autoscale tests, with the exact same worker partition counts:
Cluster status query response:
external_sender$ ./external_sender -t cluster-status-query -e <IP_ADDRESS>:20003 -j
{"processing_messages":true,"worker_names":["initializer","worker1","worker2","worker3","worker4","worker5","worker6","worker9","worker8","worker7","worker10","worker11","worker12","worker15","worker14","worker13","worker19","worker18","worker16","worker17","worker20","worker21","worker22","worker23","worker26","worker27","worker24","worker25","worker31","worker33","worker29","worker30","worker32","worker28","worker35","worker34","worker40","worker37","worker39","worker36","worker38"],"worker_count":41}

Partition count query response:
external_sender$ ./external_sender -t partition-count-query -e <IP_ADDRESS>:20003 -j
{"state_partitions":{"letter-state":{"worker24":21,"worker35":21,"worker28":21,"worker21":21,"worker17":17,"worker23":21,"worker32":21,"worker8":17,"worker20":17,"worker12":17,"worker7":17,"worker3":17,"worker4":17,"worker34":21,"worker18":17,"worker16":17,"worker36":5,"worker22":21,"worker11":17,"worker5":17,"worker25":21,"worker10":17,"worker13":17,"worker26":21,"worker33":21,"worker1":17,"initializer":17,"worker31":21,"worker14":17,"worker27":21,"worker29":21,"worker15":17,"worker9":17,"worker19":17,"worker2":17,"worker30":21,"worker6":17}},"stateless_partitions":{}}


How to call a Detail Activity

How to Call a CustumerDetail, for update and delete?
override fun onBindViewHolder(baseHolder: RecyclerView.ViewHolder, basePosition: Int) {
super.onBindViewHolder(baseHolder, basePosition)
val position = baseHolder.adapterPosition
when (getItemViewType(basePosition)) {
VIEW_TYPE_ITEM -> {
val holder = baseHolder as CustomerViewHolder
val item = items[position] as Customer
val binding = holder.binding
binding.customer = item
if (!binding.root.hasOnClickListeners()) {
binding.root.setOnClickListener {
// val clickedPosition = holder.adapterPosition
// val clickedItem = items[clickedPosition] as Customer
}
}
}
}
}

Hello @blfernandez
There is no Customer Detail Activity in Sample app.
You can surely add one, by passing the customer object (POJO) to new CutsomerDetailActivity / CustomerDetailFragment and display customer details

Ready


Change C:\Python35\python.exe to C:\Python34\python.exe in installation doc

I believe there's a typo in the installation doc for setting up the virtual environment on Windows.
As it is right now, it is going to use Python 3.5 to set up the environment instead of Python 3.4
Throughout the docs, it says that VOC won’t build on Python3.5+ and that a separate Python 3.4+ installation is required, so I am pretty sure this is just a typo.

Ah I see, is it only up to Python 3.5 for now? Or is Python 3.6 supported as well?

We run CI on 3.4, 3.4 and 3.6, so all three should be OK.


Use Ruby 2.3.0

@schneems Are you testing something on 2.2.4? Should we upgrade to 2.3 now?

I did use 2.2.4 for some testing. I'm done now. Thanks!

:+1:


Parameters for ROS stereo_img_proc

What parameters should I use for ROS stereo_img_proc? When I use the command outlined in the readme, I just get a few splotches and it doesn't detect a person in front of the cameras like shown in the demo.

Try stereo camera calibration described as:
http://wiki.ros.org/camera_calibration/Tutorials/StereoCalibration
I didn't tune the stereo matching parameter for the demo, but you may need to tune stereo parameter as:
http://wiki.ros.org/stereo_image_proc/Tutorials/ChoosingGoodStereoParameters

ah, yeah I realized I had forgotten to calibrate. I need to find a good area for calibration and get the proper grid.
I tried it in a lab, but there wasn't enough space. It's a little better, but still not fully there.

Seems to work well now, the camera still has issues, but positive its not this software causing it.

Thanks for reporting! @kfechter