Create a pages/_error.js page

Follow along with next's custom error handling and create a pages/_error.js page that surfaces errors in a good contextual way.

Opened PR 74

I am going to go ahead and remove the [WIP] label from this PR. It should use the new error handling and I can make a follow up PR to render something better than it is currently rendering.


Implementation proposal

Hi,
is there a possibility to use uptonight in Home Assistant OS, so without Docker container?
Thanks

UpTonight uses astropy which cannot be used asynchronously which would be required for a HomeAssistant integration.


Fixed a small typo "t hegroup"

Changed "t hegroup" to "the group".

@curtand please sign-off on this when you get a chance. Thanks.

@tostca Thank you so much for your contribution!!

#sign-off


[Feature Request] One way sync ( flag not to delete files on destination)

Not sure if this has ever been asked before but I love how rclone integrates with Amazon drive and encryption makes it even better the only thing I'm missing is I would like to sync some folder e.g. once new files appear rerun the command and upload the new files but not to delete if a file has been deleted on the source.
E.g.
I've got dir A on my local machine with the following files:
example1
example2
Now I add
example3
Run the sync and the file is uploaded now I want the ability to remove example1 and if I rerun the sync command I want to keep the file on the remote location.
Maybe I'm missing something and this is already possible? Also I could not find if existing files are skipped via copy?
My test tell me copy option should do confirmation would be awesome!
Thanks

Yes, use the copy verb and it will do what you want - copy never deletes anything on the destination.
You can test first with --dry-run to see exactly what it does.

Hello nbittmann,
Unless I missed something, what you want is already accomplished by using the command "rclone copy" instead of "rclone sync".
Cheers,
Durval.

Hello nbittmann,
Unless I missed something, what you want is already accomplished by using the command "rclone copy" instead of "rclone sync".
Cheers,
Durval.


Problems running nvitop on Windows after installation

Runtime Environment

Operating system and version: Windows 11 Pro version 21H2 (OS Build 22000.65)
Terminal emulator and version: Windows PowerShell 5.1.22000.65
Python version: 3.9.6
NVML/CUDA version: NVIDIA-SMI 471.21       Driver Version: 471.21       CUDA Version: 11.4
nvitop version/commit: <IP_ADDRESS>
python-ml-py version: 11.450.51
Locale: ENG

Current Behavior
1 - After installing nvitop as instructed you cannot launch nvitop by running "nvitop" command in Windows Command Prompt or Windows PowerShell. Current solution is to use "python -m nvitop" command to run.
2 - Running nvitop using "python -m nvitop" produces error "ModuleNotFoundError: No module named '_curses'". Solution is to install windows-curses using "pip3 install windows-curses"
Expected Behavior
1 - nvitop command should be executable directly from Windows Command Prompt or Windows PowerShell after installation.
2 - pip should install all necessary packages needed for Windows such as "windows-curses" package.
Context
Unless you are experienced with Python this could be difficult for an average user.
Possible Solutions
1 - Use "python -m nvitop" to run nvitop or add to PATH
2 - Install "windows-curses" pip package after installation of nvitop
Steps to reproduce

Install nvitop on Windows and try to run using "nvitop" command.
After installation run nvitop with "python -m nvitop" command.

Thanks for the feedback!
For the first issue:

nvitop command should be executable directly from Windows Command Prompt or Windows PowerShell after installation.

The Python executable (in PYTHONHOMEDIR) and the scripts installed by pip (in PYTHONHOMEDIR/Scripts) are in the different directory, You should add both Python home and its script directory to your shell PATH. (If you are using conda or virtualenv, these entries will be added to your PATH at activation).

For the second issue:

pip should install all necessary packages needed for Windows such as "windows-curses" package.

I tested and packed nvitop on my Linux machine, and the sys.platform was Linux when I build the wheel. When you installing nvitop on Windows from PyPI, pip will use the wheel file instead of running the setup.py which will determine sys.platform at runtime. I will repack the wheel file to PyPI later.

I have uploaded the repacked version of nvitop (fixed by b669fa39b161e7d482221ccee696d8dd82ed8910) to the PyPI index, you can try:
pip3 uninstall windows-curses
pip3 install nvitop==<IP_ADDRESS>

It should install windows-curses automatically.

Thanks for the feedback from @WMRamadan! Please feel free to reopen this issue if you have any other question.


Add ability to sort by Date Added

Hello,
Been using this for a long time, and always wanted an ability to sort files based on when they were added into AriaNg. Its very useful to see the files that were added just recently, so you know whether you have actually added them, or not. Most download managers allow this by default.
I understand aria2 doesn't expose this information.... but i was hoping you could add some code that would save the data separately as part of your own package.
Thank you for you time,
TheVillageIdiot

The aria2 does not expose added date of tasks via rpc. So, AriaNg cannot support sorting by this method. But, if you don't change the order of tasks manually, the default order is sorted by added date.


code coverage badge

Update output step in GitHub workflow
Add rendered output example to ReadMe.md
Add Codecov integration to GitHub actions

Not bad 🚀

Nice, should work fine 🤘


Black bar under navigation bar when adding view on scroll

when i add a subview , when the navigation bar is scrolled up, it adds a black background under navigation bar, i dont know why it happens like that, please help if anyone is aware about the issue.

Hey @pareekkhushboo77
can you share the detail steps to reproduce this issue?

@andreamazz , i solved this issue, it was my autolayout issue, the origin of my table view was below navigation bar, i just made the origin over navigation bar i.e. top of the screen and it solved my problem.
Thanks for your instant response. :)

Check another solution here: https://github.com/andreamazz/AMScrollingNavbar/issues/210#issuecomment-1491277964


Specifying timeout(s)

I may be mistaken but I didn't find any options to specify a timeout.
It seems to me that 2 types of timeouts could be implemented.

Stopping the job after x amount of time. This could be achieved in a run statement, but having an argument like "job-timeout" or such could be useful.

Terminating the ec2 instance after x amount of time. To reduce the risk of paying for an unused EC2 instance if any edge case, where that could happen, was to happen. Self terminating the ec2 instance might be a way to implement this behavior. An argument "ec2-timeout" might then be appropriate.

I was going to ask about the same thing, another mechanism to consider is https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/UsingAlarmActions.html#AddingTerminateActions
Perhaps during the start-runner we can use some of the AWS API to setup an alarm that will terminate the instance after some time.

Stopping the job after x amount of time

Which job?

Hi !
The first bullet point actually refers to github actions job timeout and is thus already implemented :+1:
Only the one for terminating the ec2 may be useful to add !


ecash (XEC) reject blocks with bad-cb-minerfund error

Discussed in https://github.com/oliverw/miningcore/discussions/1541

Originally posted by btclinux December  8, 2022
Hi! I see in coins.json for ecash https://github.com/oliverw/miningcore/blob/master/src/Miningcore/coins.json#L908
"hasMinerFund": true
All blocks rejected with:
ERROR: ConnectTip: ConnectBlock<PHONE_NUMBER>000000097c03ca368bc4efbc271a1ba308877befdf69d62cdb3a5c failed, bad-cb-minerfund

Should I add something special in pool config?
ecash node config:
rpcuser=rpcuser
rpcpassword=rpcpassword
prune=550
deprecatedrpc=accounts
usecashaddr=0
zmqpubhashblock=tcp://<IP_ADDRESS>:15101
```</div>

probably, it would give some idea
https://bitcoinabc.org/doc/dev/validation_8cpp_source.html

Hi! I think I found a problem.
If using 'usecashaddr=1' and 'ecash=0' in node config we get minerfund address bitcoincash:prfhcnyqnl5cgrnmlfmms675w93ld7mvvq5zsvycff which we can see here https://github.com/Bitcoin-ABC/bitcoin-abc/blob/47a114b9882b15e62e53d2c9ad90ce96808ea30d/src/minerfund.cpp#L40
But pool not starting due base58 check
[2023-01-19 10:17:51.9798] [E] [ecash] Error during UpdateJob System.FormatException: Invalid base58 data
   at NBitcoin.DataEncoders.Base58Encoder.DecodeData(String encoded)
   at NBitcoin.DataEncoders.Base58CheckEncoder.DecodeData(String encoded)
   at Miningcore.Blockchain.Bitcoin.BitcoinUtils.AddressToDestination(String address, Network expectedNetwork) in /home/pool/miningcore-test/src/Miningcore/Blockchain/Bitcoin/BitcoinUtils.cs:line 20
   at Miningcore.Blockchain.Bitcoin.BitcoinJob.CreateMinerFundOutputs(Transaction tx, Money reward) in /home/pool/miningcore-test/src/Miningcore/Blockchain/Bitcoin/BitcoinJob.cs:line 534
   at Miningcore.Blockchain.Bitcoin.BitcoinJob.CreateOutputTransaction() in /home/pool/miningcore-test/src/Miningcore/Blockchain/Bitcoin/BitcoinJob.cs:line 250
   at Miningcore.Blockchain.Bitcoin.BitcoinJob.BuildCoinbase() in /home/pool/miningcore-test/src/Miningcore/Blockchain/Bitcoin/BitcoinJob.cs:line 91
   at Miningcore.Blockchain.Bitcoin.BitcoinJob.Init(BlockTemplate blockTemplate, String jobId, PoolConfig pc, BitcoinPoolConfigExtra extraPoolConfig, ClusterConfig cc, IMasterClock clock, IDestination poolAddressDestination, Network network, Boolean isPoS, Double shareMultiplier, IHashAlgorithm coinbaseHasher, IHashAlgorithm headerHasher, IHashAlgorithm blockHasher) in /home/pool/miningcore-test/src/Miningcore/Blockchain/Bitcoin/BitcoinJob.cs:line 639
   at Miningcore.Blockchain.Bitcoin.BitcoinJobManager.UpdateJob(CancellationToken ct, Boolean forceUpdate, String via, String json)    at NBitcoin.DataEncoders.Base58Encoder.DecodeData(String encoded)
   at NBitcoin.DataEncoders.Base58CheckEncoder.DecodeData(String encoded)
   at Miningcore.Blockchain.Bitcoin.BitcoinUtils.AddressToDestination(String address, Network expectedNetwork) in /home/pool/miningcore-test/src/Miningcore/Blockchain/Bitcoin/BitcoinUtils.cs:line 20
   at Miningcore.Blockchain.Bitcoin.BitcoinJob.CreateMinerFundOutputs(Transaction tx, Money reward) in /home/pool/miningcore-test/src/Miningcore/Blockchain/Bitcoin/BitcoinJob.cs:line 534
   at Miningcore.Blockchain.Bitcoin.BitcoinJob.CreateOutputTransaction() in /home/pool/miningcore-test/src/Miningcore/Blockchain/Bitcoin/BitcoinJob.cs:line 250
   at Miningcore.Blockchain.Bitcoin.BitcoinJob.BuildCoinbase() in /home/pool/miningcore-test/src/Miningcore/Blockchain/Bitcoin/BitcoinJob.cs:line 91
   at Miningcore.Blockchain.Bitcoin.BitcoinJob.Init(BlockTemplate blockTemplate, String jobId, PoolConfig pc, BitcoinPoolConfigExtra extraPoolConfig, ClusterConfig cc, IMasterClock clock, IDestination poolAddressDestination, Network network, Boolean isPoS, Double shareMultiplier, IHashAlgorithm coinbaseHasher, IHashAlgorithm headerHasher, IHashAlgorithm blockHasher) in /home/pool/miningcore-test/src/Miningcore/Blockchain/Bitcoin/BitcoinJob.cs:line 639
   at Miningcore.Blockchain.Bitcoin.BitcoinJobManager.UpdateJob(CancellationToken ct, Boolean forceUpdate, String via, String json)

If using 'usecashaddr=0' in node config we get minerfund address 3LyFQTKbPwXtgrsGpMbbEECY7ViBeFbonU in block template which is not presented in ABC source code.
Any suggestions?

Hi! I think I found a problem. If using 'usecashaddr=1' and 'ecash=0' in node config we get minerfund address bitcoincash:prfhcnyqnl5cgrnmlfmms675w93ld7mvvq5zsvycff which we can see here https://github.com/Bitcoin-ABC/bitcoin-abc/blob/47a114b9882b15e62e53d2c9ad90ce96808ea30d/src/minerfund.cpp#L40 But pool not starting due base58 check
[2023-01-19 10:17:51.9798] [E] [ecash] Error during UpdateJob System.FormatException: Invalid base58 data
   at NBitcoin.DataEncoders.Base58Encoder.DecodeData(String encoded)
   at NBitcoin.DataEncoders.Base58CheckEncoder.DecodeData(String encoded)
   at Miningcore.Blockchain.Bitcoin.BitcoinUtils.AddressToDestination(String address, Network expectedNetwork) in /home/pool/miningcore-test/src/Miningcore/Blockchain/Bitcoin/BitcoinUtils.cs:line 20
   at Miningcore.Blockchain.Bitcoin.BitcoinJob.CreateMinerFundOutputs(Transaction tx, Money reward) in /home/pool/miningcore-test/src/Miningcore/Blockchain/Bitcoin/BitcoinJob.cs:line 534
   at Miningcore.Blockchain.Bitcoin.BitcoinJob.CreateOutputTransaction() in /home/pool/miningcore-test/src/Miningcore/Blockchain/Bitcoin/BitcoinJob.cs:line 250
   at Miningcore.Blockchain.Bitcoin.BitcoinJob.BuildCoinbase() in /home/pool/miningcore-test/src/Miningcore/Blockchain/Bitcoin/BitcoinJob.cs:line 91
   at Miningcore.Blockchain.Bitcoin.BitcoinJob.Init(BlockTemplate blockTemplate, String jobId, PoolConfig pc, BitcoinPoolConfigExtra extraPoolConfig, ClusterConfig cc, IMasterClock clock, IDestination poolAddressDestination, Network network, Boolean isPoS, Double shareMultiplier, IHashAlgorithm coinbaseHasher, IHashAlgorithm headerHasher, IHashAlgorithm blockHasher) in /home/pool/miningcore-test/src/Miningcore/Blockchain/Bitcoin/BitcoinJob.cs:line 639
   at Miningcore.Blockchain.Bitcoin.BitcoinJobManager.UpdateJob(CancellationToken ct, Boolean forceUpdate, String via, String json)    at NBitcoin.DataEncoders.Base58Encoder.DecodeData(String encoded)
   at NBitcoin.DataEncoders.Base58CheckEncoder.DecodeData(String encoded)
   at Miningcore.Blockchain.Bitcoin.BitcoinUtils.AddressToDestination(String address, Network expectedNetwork) in /home/pool/miningcore-test/src/Miningcore/Blockchain/Bitcoin/BitcoinUtils.cs:line 20
   at Miningcore.Blockchain.Bitcoin.BitcoinJob.CreateMinerFundOutputs(Transaction tx, Money reward) in /home/pool/miningcore-test/src/Miningcore/Blockchain/Bitcoin/BitcoinJob.cs:line 534
   at Miningcore.Blockchain.Bitcoin.BitcoinJob.CreateOutputTransaction() in /home/pool/miningcore-test/src/Miningcore/Blockchain/Bitcoin/BitcoinJob.cs:line 250
   at Miningcore.Blockchain.Bitcoin.BitcoinJob.BuildCoinbase() in /home/pool/miningcore-test/src/Miningcore/Blockchain/Bitcoin/BitcoinJob.cs:line 91
   at Miningcore.Blockchain.Bitcoin.BitcoinJob.Init(BlockTemplate blockTemplate, String jobId, PoolConfig pc, BitcoinPoolConfigExtra extraPoolConfig, ClusterConfig cc, IMasterClock clock, IDestination poolAddressDestination, Network network, Boolean isPoS, Double shareMultiplier, IHashAlgorithm coinbaseHasher, IHashAlgorithm headerHasher, IHashAlgorithm blockHasher) in /home/pool/miningcore-test/src/Miningcore/Blockchain/Bitcoin/BitcoinJob.cs:line 639
   at Miningcore.Blockchain.Bitcoin.BitcoinJobManager.UpdateJob(CancellationToken ct, Boolean forceUpdate, String via, String json)

If using 'usecashaddr=0' in node config we get minerfund address 3LyFQTKbPwXtgrsGpMbbEECY7ViBeFbonU in block template which is not presented in ABC source code. Any suggestions?

Very interesting. Working on it.

Adding "addressType": "bcash" to the pool config should allow you to use the bech32 cash address.

Adding "addressType": "bcash" to the pool config should allow you to use the bech32 cash address.

I did, and got "Error during UpdateJob System.FormatException: Invalid base58 data"

Currently NBitcoin does not seem to like the minerfund address. Even if you add ecash support to nbitcoin the minerfund address seems to still fail to decode correctly.

Currently NBitcoin does not seem to like the minerfund address. Even if you add ecash support to nbitcoin the minerfund address seems to still fail to decode correctly.

Minerfund have a bitcoincash: format, not ecash:

You have it working with bitcoincash: instead of ecash:  and the minderfund is set and decoded correctly?


Celestia Bridge crashes with to many open files

Celestia Node version
Semantic version: v0.12.1 Commit: b7b6350f8921d4454b8a38c8485d74f908fb6a61 Build Date: Sun Dec 17 05:14:17 PM CET 2023 System version: amd64/linux Golang version: go1.21.2
OS
DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS"
Install tools
Running local binary
Others
No response
Steps to reproduce it
Run bridge node for validator. Then run into error after running since mainnet. Has only occued once, but has done so on mainnet node
Error is
131 225 62 201 255 255 255 255 255 255 255 255] right:[] inf:false size:0}] thisSize:0 dropPrefixes:[]} error: While opening directory: /home/celestia/.celestia-bridge/inverted_index/. error: open /home/celestia/.celestia-bridge/inverted_index/: too many open files
keeps repeating itself, higher cpu usage. Restart fixes
Expected result
no error and just run
Actual result
error
Relevant log output
131 225 62 201 255 255 255 255 255 255 255 255] right:[] inf:false size:0}] thisSize:0 dropPrefixes:[]} error: While opening directory: /home/celestia/.celestia-bridge/inverted_index/. error: open /home/celestia/.celestia-bridge/inverted_index/: too many open files

Notes
Error on mainnet node for validator Staking4All

bridge-mainnet.txt

@mindstyle85 @rooiie did you get around this, assume via increasing the max open files with ulimit?


Formatting not working at all!

For me, the formatting won't work at all! This is the output at the beginning of every java file. Am I doing something wrong?
/*
 * #%L
 * [...]
 * %%
 * Copyright (C) 2015 [...]
 * %%
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 * #L%
 */

Configuration:
            <!-- License plugin -->
            <plugin>
                <groupId>org.codehaus.mojo</groupId>
                <artifactId>license-maven-plugin</artifactId>
                <version>1.8</version>
                <configuration>
                    <roots>
                        <root>src/main/java</root>
                        <root>src/test</root>
                    </roots>
                    <licenseName>apache_v2</licenseName>
                    <inceptionYear>2015</inceptionYear>
                    <projectName>${project.name}</projectName>
                    <properties>
                        <owner>[...]</owner>
                        <email>[...]</email>
                    </properties>
                    <excludes>
                        <exclude>**/README</exclude>
                        <exclude>src/test/resources/**</exclude>
                        <exclude>src/main/resources/**</exclude>
                    </excludes>
                </configuration>
                <executions>
                    <execution>
                        <id>first</id>
                        <goals>
                            <goal>update-file-header</goal>
                        </goals>
                        <phase>process-sources</phase>
                    </execution>
                </executions>
            </plugin>

You ate using an outdated version. Please see the website / doc.
<groupId>org.codehaus.mojo</groupId>
<artifactId>license-maven-plugin</artifactId>
<version>1.8</version>


Latest cleanup is broken

[x] are reporting a bug others will be able to reproduce and not asking a question. If you're not sure or want to ask a question do so on our Discourse: https://discourse.brew.sh
[x] ran a brew command and reproduced the problem with multiple formulae? If it's a problem with a single, official formula (not cask) please file this issue at Homebrew/homebrew-core: https://github.com/Homebrew/homebrew-core/issues/new/choose. If it's a brew cask problem please file this issue at https://github.com/Homebrew/homebrew-cask/issues/new/choose. If it's a tap (e.g. Homebrew/homebrew-php) problem please file this issue at the tap.
[x] ran brew update and can still reproduce the problem?
[x] ran brew doctor, fixed all issues and can still reproduce the problem?
[x] ran brew config and brew doctor and included their output with your issue?

Sometime within the last 24 hours, cleanup -n is now (a) listing stuff twice, and (b) listing stuff that (i) it didn't use to list and (ii) should not be cleaned up.
For instance, in the output below you can see the duplication.  Also,  every single thing listed there is both installed and current.  (Some of it is from my own custom tap but e.g., jpeg is not.
$ brew cleanup -n
Would remove: /stuff/brache/browser--7 (419B)
Would remove: /stuff/brache/jpeg--9c.high_sierra.bottle.tar.gz (297.6KB)
Would remove: /stuff/brache/jpeg--9c.tar.gz (1004.1KB)
Would remove: /stuff/brache/jq--1.5.d2.tar.xz (3.6MB)
Would remove: /stuff/brache/lynx--2.8.9rel1.tar.xz (3.5MB)
Would remove: /stuff/brache/screenresolution--1.6i.txz (34KB)
Would remove: /stuff/brache/browser--7 (419B)
Would remove: /stuff/brache/jpeg--9c.high_sierra.bottle.tar.gz (297.6KB)
Would remove: /stuff/brache/jpeg--9c.tar.gz (1004.1KB)
Would remove: /stuff/brache/jq--1.5.d2.tar.xz (3.6MB)
Would remove: /stuff/brache/lynx--2.8.9rel1.tar.xz (3.5MB)
Would remove: /stuff/brache/screenresolution--1.6i.txz (34KB)

None of that was listed yesterday.
$ brew config
HOMEBREW_VERSION: 1.7.1-204-g8e703e3
ORIGIN: https://github.com/Homebrew/brew
HEAD: 8e703e30ba53f8089686b0fc90f87803b4fd5d90
Last commit: 6 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: b450b805d3fe4ca94310b31e2583c1a497cf7fa8
Core tap last commit: 2 hours ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_REPOSITORY: /usr/local/hb
HOMEBREW_CACHE: /stuff/brache
HOMEBREW_TEMP: /Users/chdiza/.tmp/tmpdir
HOMEBREW_BUILD_FROM_SOURCE: 1
HOMEBREW_DEV_CMD_RUN: 1
HOMEBREW_LOGS: /Users/chdiza/Library/Homebrew
HOMEBREW_NO_ANALYTICS: 1
HOMEBREW_NO_AUTO_UPDATE: 1
HOMEBREW_NO_EMOJI: 1
HOMEBREW_NO_GITHUB_API: 1
CPU: quad-core 64-bit ivybridge
Homebrew Ruby: 2.3.7 => /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/bin/ruby
Clang: 9.1 build 902
Git: 2.18.0 => /usr/local/bin/git
Curl: 7.54.0 => /usr/bin/curl
Java: N/A
macOS: 10.13.6-x86_64
CLT: <IP_ADDRESS>.1.1528165917
Xcode: 9.4.1
XQuartz: N/A

$ brew doctor
Your system is ready to brew.

The bad commit is 78658e430259bc030389668d6f
Author: Markus Reiter<EMAIL_ADDRESS>Date:   Wed Aug 8 22:23:55 2018 +0200

    Add cask cleanup and per-formula cache cleanup.

Evidently some new regex is messed up.

Is this why I'm getting error when I run update?
Error: Unknown command: clean

@nwhitmont, please open a separate issue for that.


Don't use unwrap

Enabled +#![deny(clippy::unwrap_used, clippy::expect_used, clippy::panic)]
(but also allow-unwrap-in-tests = true because it's too strict for tests)
This means that unwrap, expect and panic are not allowed in the project, unless the programmer states #[allow(clippy::unwrap_used)], preferably with a comment explaining why the unwrap/expect could never panic.
Removed all instances of unwrap which had better alternatives, but left some that were reasonable.
This should stop recert from causing panics (unfortunately dependencies might still panic)
Also removed references to anyhow::Error from return values, as this is unnecessarily verbose and can be inferred implicitly. It's constantly being added by the rust_analyzer's extract_function code action, and I forget to remove it.

/retest

/retest

/test e2e-aws-ovn-single-node-recert-parallel

/override ?

/override pull-ci-rh-ecosystem-edge-recert-main-e2e-aws-ovn-single-node-recert-serial


Introduced the possibility to implement a client-side table

See issue #6

I'm sorry I didn't get a chance to properly provide feedback on this yet. It's a pretty invasive feature and I'll have to properly think through whether the approach taken is the best for future extensions.

For my intents is very useful this feature.
For the moment I'm using my fork for production environments.
I hope to see a feature that introduces a feature like this in the next releases.
I'd like to provide my contribution to this project.

Closing due to inactivity, it seems there's not much demand for this feature.

Ok @curry684 , someone has forked my fork to use this feature.
I hope that you keep in mind for the future.
Thanks
G.

Of course :)


test: add code coverage support

Signed-off-by: Ramkumar Chinchani<EMAIL_ADDRESS>
What type of PR is this?

Which issue does this PR fix:
What does this PR do / Why do we need it:
If an issue # is not available please add repro steps and logs showing the issue:
Testing done on this change:

Automation added to e2e:

Will this break upgrades or downgrades?
Does this PR introduce any user-facing change?:

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

stacker subcommand: [/home/runner/work/stacker/stacker/stacker --internal-userns --debug internal-go copy docker://centos:latest oci:/home/runner/work/stacker/stacker/test/centos:latest copy docker://centos:latest oci:/home/runner/work/stacker/stacker/test/centos:latest copy docker://centos:latest oci:/home/runner/work/stacker/stacker/test/centos:latest]
error: wrong number of args

need to work out a way to remove these repeated args for the internal invocation.

2023-02-03T01:38:33.6924887Z GOCOVERDIR=. go build -tags "exclude_graphdriver_btrfs exclude_graphdriver_devicemapper containers_image_openpgp osusergo netgo " -ldflags "-X main.version=b9cbdb6efc7a274b0574764594a3f864b18a2951 -X main.lxc_version=5.0.0~git2209-g5a7b9ce67 " -o stacker-dynamic ./cmd/stacker
2023-02-03T01:48:48.9973555Z GOCOVERDIR=. go build -cover -covermode=atomic -coverpkg="./..." -tags "exclude_graphdriver_btrfs exclude_graphdriver_devicemapper containers_image_openpgp osusergo netgo static_build testrunmain" -ldflags "-X main.version=b9cbdb6efc7a274b0574764594a3f864b18a2951 -X main.lxc_version=727adc05220e9b8b594c5bc2124bef5b2e0abe7a -extldflags '-static'" -o stacker ./cmd/stacker

https://pkgs.alpinelinux.org/package/edge/community/x86/go
^ best to wait for alpine to release its go 1.20 pkg

Codecov Report

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

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@          Coverage Diff           @@
##             main    #347   +/-   ##
======================================
  Coverage        ?   6.60%
======================================
  Files           ?      58
  Lines           ?    6294
  Branches        ?       0
======================================
  Hits            ?     416
  Misses          ?    5816
  Partials        ?      62

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Closing in favor of PR #550


\transn breaks vertical spacing inside of a square root

As shown below, when you put a decimal number into a square root, wrapped in \transn, it displays incorrectly. E.g.: \sqrt{\transn{0.04}}
https://codepen.io/barillax/pen/BvVQBX

I wonder if the fix for this might be similar to https://github.com/OmarIthawi/arabic-mathjax/pull/16 ?
EDIT: this also happens for \transt{}{} inside of a square root, i.e.: %% \sqrt{{\transt{speed}{السرعة}}} %%

After looking at #16, I inspected the DOM and found that if I added the .mar class to the surrounding element, it fixed the display. See image below illustrating what I mean:

The top square root in the above image renders incorrectly, while the bottom one displays properly thanks to the CSS giving it border-width: 0.45 em 0;

@barillax this PR https://github.com/OmarIthawi/arabic-mathjax/pull/20 should solve your issue. Please wait for it to be merged and pushed to npm
CC: @OmarIthawi

Thank you @shadinaif !


[semver:major] Use localstack-main as default container name

Update orb commands
Bump example version
Update changelog

SEMVER Update Type:

[x] Major
[ ] Minor
[ ] Patch

Description:

Update the name of the container to localstack-main.
Motivation:

Hyphens are not allowed in domain names. Docker container names are sometimes used as URLs, and some tools (e.g. boto3) refuse to connect to localstack_main.
For more details, see the corresponding LocalStack change: https://github.com/localstack/localstack/pull/9469
Checklist:

[x] Usage Example version numbers have been updated.
[x] Changelog has been updated.

The changes are small and would work fine once the LocalStack CLI v3.0 is released. However, we could just add a minor release which falls back to the old container name (see comments). This way we could just move forward and merge / release it :) What do you say? We can also try to time this release specifically and do a major bump...

I think this is a safer idea. Thanks for pointing out the backwards-compatible implementation. I'll work on making a minor release.


docs(ce/getting-started) typo in secure-services section

change mock to mocking in admin api calls

@malhotraamit236 Sorry for the confusion, but the initial path is correct: mocking is the name and /mock is the path, as set earlier in the getting started guide: https://docs.konghq.com/getting-started-guide/latest/expose-services/#add-a-route

@malhotraamit236 Sorry for the confusion, but the initial path is correct: mocking is the name and /mock is the path, as set earlier in the getting started guide: https://docs.konghq.com/getting-started-guide/latest/expose-services/#add-a-route

@lena-larionova I was referring to http :8001/routes/mock/plugins name=key-auth in https://docs.konghq.com/getting-started-guide/latest/secure-services/
I tried to add plugin to a path and got:
HTTP/1.1 404 Not Found
Access-Control-Allow-Origin: *
Connection: keep-alive
Content-Length: 23
Content-Type: application/json; charset=utf-8
Date: Mon, 04 May 2020 17:54:45 GMT
Server: kong/2.0.4
X-Kong-Admin-Latency: 1

{
    "message": "Not found"
}

But if I do http :8001/routes/mocking/plugins name=key-auth it is successful.

But if I do http :8001/routes/mocking/plugins name=key-auth it is successful.

Hmm, I just tested it, and you are right. This is an odd/confusing design choice. Thanks for double-checking!


how to train net  by adding Semantic segmentation branch ?

thanks your amazing works
i have add Semantic segmentation branch in net, and want to  finetune in this weight(nuScenes_3Ddetection_e140.pth ) Want more output of semantic segmentation in the network but i don not how to definition my dataset in your dataset factory and don not know how to train Semantic segmentation branch? (frozen others output, only train Semantic segmentation branch ?)

Thank you for your interest. I would say you need to expect many code changes. I haven't worked on Semantic segmentation so I am not able to give more specific suggestions.


When should ThreadPoolBuilder be used?

It would be nice if the documentation added information as to when one should use the ThreadPoolBuilder.  So far, it seems like the only use is if you want to have a non-default number of threads, stack size, or handlers.
However, should a custom thread pool be built if we are going to repeatedly use par_iter? (or is the global initialization only done once?)  As an example, is the following any better than the equivalent code without a pool?
let pool = rayon::ThreadPoolBuilder::new().build().unwrap();
let mut err = 1e10;
for err > 1e-5 {
    pool.install(|| {
        err = vec.par_iter_mut(|v| some_expensive_function(v)).min().unwrap();
    })
}

That's a reasonable confusion, so we can certainly update the docs. I'll try to clarify here first.
The global thread pool remains for the life of the process. It can be manually initialized and configured with ThreadPoolBuilder::build_global() if you like, otherwise it will implicitly start with default settings on first use. A global "use" would be any rayon invocation that's not explicitly installed in some other ThreadPool first.
You would use separate ThreadPool instances if you need more control over the life of the threads, like build_scoped(), or if you want to segregate parallel tasks for any reason. For instance, you might want to create a pool with higher scheduling priority for latency-sensitive tasks, and leave other tasks in the global pool. Rayon doesn't have any priority of its own, especially since there's no means of preemption, but you can let the OS handle that at the thread level.

However, should a custom thread pool be built if we are going to repeatedly use par_iter? (or is the global initialization only done once?)

The global initialization is only done once, so you don't need a custom pool for repeated use.


Don't lose cutpoints when extending the timeline

If a recording is cut and is not long enough the previously set cutpoints should persist.
The Operator could already have spend a lot of time looking for the inpoint before noticing that the recording is not long enough. Currently the inpoint would be lost and the operator has to set it again.

This is difficult to achieve with current architecture, since the tracker application has no access to the info in the fuse mount.
Possible solution: set a property on the ticket that tells the mount worker to save and restore the cutmarks before unmount/after mount.

Wouldn't we also enable easy remounts when always restoring cut marks when they exist?

Looking at the mounts: yes. Looking at the ticket states: no. The ticket needs to be reset to recorded and then the previous state information is lost.

then the previous state information is lost
Why do we need the previous state? It should be safe to always restore if the properties exist, shouldn't it?

In the use case "restore mounts": if it was already cut, then it should end up in finalized without manual interaction and maybe without going through finalizing.
While in the use case of extending, it of course should end up in prepared (this happens right now and is ok).

Okay, we probably need a separate solution to trigger remounts (ideally without leaving finalized). But cut marks could always be restored.

Agree, therefore I already created https://github.com/crs-tools/crs-scripts/issues/4 and came to the conclusion that there should be no problem when always restoring cutmarks.
For documentation: there is a script that can manually restore mounts from all tickets in finalized:
https://github.com/crs-tools/crs-scripts/blob/master/scripts/restore-fuse-mounts.pl but of course there is no web UI for that.


Hdist block voting

@barakshani @zalmen this is without the abstain we can add it in a different pr

Please add unit tests to all new logic and refactored logic.


Some models do not apply vae when upscaling

Hi, First of all, great work!
My model has no problem with normal generate, but only when upscaling.
Realistic Vision , XXMix_9realistic, etc. also succeed when upscaling.
test-L10-C16-W384-H512-T768-T1152.json

Can it be resolved? thanks.

I don't know why, but there is a checkpoint where the color fades when used in animatediff.


[core] Make prettier run programmatically

[x] I have followed (at least) the PR section of the contributing guide.

Continuation of #13571
Not sure where the scripts should live, looking to receive guidance :)

@eps1lon Well done with the review! It's even better than what the React team did :). @joshwooding 👌


Bug: Time synchronization still in winter time

Describe the bug
The time synchronization option sets the date, but the time is 1h late since summer time (end of march)
To Reproduce
Mark the option "Automatically synchronise time", wait for summer time (DST?), check data printed on the video stream.
Expected behavior
Camera time and system time should be the same.
For example, system time is now 21:10, while cameras show 20:10. During winter time both were in sync.
Log
n/a
Camera (please complete the following information):

Device Model: C100, C200
FW: n/a

Using stream component
no
Camera works through onvif component OR different cameras work in general
yes
Camera has all attributes filled out properly in developer tools
yes
HASS Environment
Home Assistant OS
Additional context
Add any other context about the problem here.

Tapo cameras use UTC timezones which don't have daylight saving.
What is interesting, is that half of my cameras show a correct time and the other half don't.
The timezone in the app is set to UTC-1 in all the cameras.
However, the half which correctly displays time reports timezone as 'UTC-01:00DST-02:00,M3.5.0/02:00:00,M10.5.0/03:00:00' and the other half with incorrect time just 'UTC-01:00'.
All of them have the same time synchronized.
In all the cases its following:
{
    'DateTimeType': 'NTP',
    'DaylightSavings': True,
    'TimeZone': {
        'TZ': 'see above'
    },
    'UTCDateTime': {
        'Time': {
            'Hour': 22,
            'Minute': 11,
            'Second': 18
        },
        'Date': {
            'Year': 2021,
            'Month': 5,
            'Day': 6
        }
    },
    'LocalDateTime': {
        'Time': {
            'Hour': 0,
            'Minute': 11,
            'Second': 18
        },
        'Date': {
            'Year': 2021,
            'Month': 5,
            'Day': 7
        }
    },
    'Extension': None,
    '_attr_1': None
}

Integration is setting UTC time, camera has to then apply your correct timezone AND daylight saving settings.
Not sure currently how to fix this, but it must be some setting hidden in the app. Try to have a look around?

Fixed in 3.3.2.


Implementation constraint queries

Each aras should be assigned, if they cannot do it, they can call it out of scope and we can assign them later.

Workflow query A.1 - write a query with a TRAPI constraint with a chemical that must be FDA approved. Along the way ARAs and ARS will then know what to do.  Currently none of the ARAs are implementing constraints. The idea is to have the ARAs implement the constraint. There is a backup plan that this constraint can be implemented with workflow runner and then ARAs don't have to worry about it. But before the backup plan is implemented, ARAs need to evaluate and determine if implementing the constraint is out of scope for them. @vgardner-renci, assign all ARAs to this issue so they can make a decision.

BTE is planning on implementing constraint filtering, tracked in https://github.com/biothings/BioThings_Explorer_TRAPI/issues/174

ARAX is planning to have this constraint implemented by Aug. 20 - being tracked in https://github.com/RTXteam/RTX/issues/1599

Will triage by August 12, 2021.  We have some limited constraint capabilities already.  I need to investigate what else we'd need to add.

In the mini hackathon repo, there is a folder with code EFGR advanced.

This is in-scope for ranking-agent.  Being tracked: https://github.com/ranking-agent/strider/issues/233

the example TRAPI query with the constraint is here: https://github.com/NCATSTranslator/minihackathons/blob/main/2021-12_demo/workflowA/EGFR_advanced.json

Improving Agent and Explanatory Agent folks, can you comment on this issue @brettasmi @jenndoug @suihuang-ISB @Rosinaweber

ARAX has implemented handling of the biolink:highest_FDA_approval_status constraint (as defined in A.9_EGFR_advanced.json) - an example of a query using it is here: https://arax.ncats.io/?r=19693
Has there been a discussion about what possible values other than "regular approval" this constraint might have? We have other drug status information like "experimental drug" or "investigational drug" that could be constrained on as well, but are not sure if a standard way of creating constraints for such info has been settled on.

Strider being deployed Sep 9 should implement this.

On our to-dos and will be implemented by relay.


follow the profile spec more closely

addresses the issues discussed in #15

Current coverage is 99.22% (diff: 100%)

Merging #16 into master will decrease coverage by 0.02%

@@             master        #16   diff @@
==========================================
  Files             9          9
  Lines           403        389    -14
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits            400        386    -14
  Misses            3          3
  Partials          0          0

Powered by Codecov. Last update 55ee3de...8122411


AmazingFeature - Added essential mouseover handling to the OK button.

As stated in the short description, here are some essential changes to the OK button. I feel like I'm back in Junior High again!

Jokes, we love it! 👏


plans for another release?

I'm keen to use the ability to drop the nom dependency that was merged in #17 but isn't on crates.io yet.
This library is fairly large when compiled to Webassembly (over 1MB) and any ability to trim it down would be helpful.
Keep up the great work!

@joshrule wanna try your new crates.io privileges to make this available?

Another suggestion would be to move all the string parsing into a proc macro (assuming that we're only interested in parsing static strings).  That way the parsing happens at compile time (no runtime overhead) and nom effectively becomes a dev dependency.

My personal use cases tend to require parsing at runtime, so I think adding the feature is probably the next step.
@lucasem - happy to handle this, but it may be a few days due to some major preexisting commitments this weekend.

Okay - this has now been resolved by #24!


editing ?

Wonderful and fast editor !!! Is a joy to use...
Does this supporting editing a markdown file ?
The buffer golang file seems to indicate that there is some lower level functionality for this, but maybe its not exposed to the Text Editor ?

Wonderful and fast editor !!! Is a joy to use...

Thank you, although it is still very much a work-in-progress haha.

Does this supporting editing a markdown file ?

Sorry, I don't understand the question. If you provide a file path to the program (for example mdedit file.md), you should be able to edit the markdown content of file.md, correct?

Yes i know its very alpha / beta, etc :) I am just playing around with the it as its such a nice example of what gioui can do.
Yes parsing a file as an argument works fine.
But I  can not edit the markdown. The same is true for all files i open with it. There is no caret. Its completely read only.
I am in mac btw. Maybe your on windows or linux and are not aware that editing does not work ?

Yikes... no I didn't know that, I'm only using linux. Just to be clear, you're saying when you open a file, for example by running mdedit file.md, there is no white rectangle in the top left corner of the file content, such as the below screenshot?

I also have the white rectangle. However, i cant edit because no mouse or keyboard events work to allow editing the file. The panel is totally dead.
The preview panel ( on the right) works great. Scrolls etc.

Ah, ok: the editor is meant to be similar to vim. I say "vi-like" in the readme. So that rectangle is the caret.
Vim (stands for Vi-IMproved) is a text editor with different "modes." Two of the most often used modes are Normal mode and Insert mode.
By default, mdedit starts in Normal mode which is useful for navigating around the text. Check out this Vim cheatsheet, specifically the "Cursor movement" section for how to use Normal mode.
To start editing check out the next section titled "Insert mode - inserting/appending text." (A common way is by just typing i if you wanted to quickly try it without reading the cheatsheet).

Ah . all makes sense now.
I can confirm that inserts work on mac. SO no bug - just user training :)

Haha yes, and I can probably be clearer about this in the readme, so thank you for the issue! :sunglasses:

ah its cool - thats code - never ever finished...
I did find your code for checking the key binding events. It is so nicely done.
I started to make a markdown file to document all the currently implemented key bindings, but could not because i do not understand how to use VIM and so cant document the same in mdedit. Not enough  semantic understanding on my side..
If you happen to get time to add these to the README with some sort of explanation it would be really cool.   I really want to use this as my IDE , and yes i know its beta beta...  Please let me know if you do make the markdown doc, otherwise i will try again later when i have more time.


pdm: 2.10.0 -> 2.10.1; fix #265883

Description of changes
Changelog: https://github.com/pdm-project/pdm/releases/tag/2.10.1
fixes #265883

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 266016 run on x86_64-linux 1

2 packages built:

pdm
pdm.dist

Fix for #265883 works.


CAMEL-19852 - Camel-platform-http-vertx: Always use normalized path f…

…rom context
Description

Target

[x] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[ ] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[x] I checked that each commit in the pull request has a meaningful subject line and body.

[x] I have run mvn clean install -DskipTests locally and I have committed all auto-generated changes

/component-tests camel-platform-http-vertx

The error is not related to the PR. Will fix with https://issues.apache.org/jira/browse/CAMEL-19853


Issues of running MXNET cu-80 with RTX2080, Nvidia-driver-410, CUDA-8.0, 9.0, 9.2

Description
Loading MXNET mtcnn model very slow with CUDA8.0.
With CUDA 9.0 or CUDA 9.2, fail to load MXNET forward convolution algorithm, or after processing the forward convolution algorithm, the system would show error if I want to give further instructions, such as print mxnet.ndarray or asNumpy
Environment info (Required)
Ubuntu 16.04
Nvidia-driver410
GrForce RTX 2080
CUDA 8.0, CUDA 9.0, CUDA 9.2
mxnet cu-80, mxnet cu-90, mxnet-cu92
cudnn v6.0 for CUDA 8.0, cudnn v7.0 for CUDA 9.0, CUDA 9.2
I installed Nvidia-driver-410 first,
Package used (Python/R/Scala/Julia):
python 2.7

Compiler (gcc/clang/mingw/visual studio):
visual studio code

## Error Message:
(Paste the complete error message, including stack trace.)
Segmentation fault: 11
mxnet.base.MXNetError: [20:11:38] src/operator/nn/./cudnn/cudnn_convolution-inl.h:870: Failed to find any forward convolution algorithm.

## What have you tried to solve it?

1. We tried to configure the environment in multiple ways, including install Nvida-410, then install CUDA from .run file, selected not to install the suggested driver version, tried 3 different CUDA versions.

Same with me

Support for Turing GPUs (eg 2080) was added in CUDA 10 (https://devblogs.nvidia.com/cuda-10-features-revealed/). CUDA 9 won't allow you to use Turing GPUs. Also relevant: #12877

It shouldn't crash if you use Turing, it should just use a possibly less than ideal PTX version.    This could be related to a recently fixed bug.  Can you see if you can reproduce the issue in version 1.3.1 (which should be released very soon).

@KellenSunderland: are you sure about this? Both PyTorch and TensorFlow have a lot of issues open about this (eg this), and articles written about it (eg this "The major issue being CUDA-9 is not aware of the latest GeForce RTX 2080 and its architecture hence when you run a program with TF as backend it shows segmentation fault."). I don't think it merely has non-ideal PTX.

I also encountered the same error one month ago after the forward pass. However, I reinstall the mxnet today and it works fine for me. I also test that mxnet-cuda100 also works now.
My System setup:
ubuntu 18.04
cuda 9.2, cuda 9.1, cuda 10.0 installed
cudnn v7.3.1 for linux
GPU: RTX 2080
CPU is AMD Ryzen 2600
RAM: 16GB

@sbodenstein I'm pretty sure.  I can test on my machine to trust-but-verify :-).
@tianweiy: that's really interesting that a reinstall fixed your issue.  I wonder if people running into this issue could delete their ~/.nv folder and see if it magically starts working.  What I'm wondering is did people upgrade their card on the same machine?  If so I could see a cubin for the wrong hardware being cached in ~/.nv .  More or less a wild guess, but this could cause issues.

I am upgrading on a new machine so that I don't think the cache is the problem. I also upgrade the cudnn library which may help to fix the problem.

The issue doesn't seem to be related to C++ Frontend API, hence removing the C++ label.

@mxnet-label-bot update [Question, CUDA]


Create docs/sdg directory

Create a directory for sdg-focused design docs to live. Move the
original proposal for the new repository into the new directory as
well.
Signed-off-by: Russell Bryant<EMAIL_ADDRESS>

Thanks for the quick reviews! This is a trivial change, so I'm going to go ahead and merge.


Pagination using the Tire REST DSL

We need to paginate some queries that require the REST DSL, but have not found a way to do so.
The REST DSL queries are implemented like:
https://github.com/karmi/tire/wiki/Using-elasticsearch-query-DSL-directly-(or%3A-doing-queries-not-supported-by-the-DSL)
We tried to paginate by applying the methodology described in the Tire unit tests:
https://github.com/karmi/tire/blob/master/test/integration/active_record_searchable_test.rb#L83
However, this does not seem to work with a query hash (e.g ':query => {"match_all" => {}}') and as far as I know translating the query hash to a query string is not feasible for advanced queries that use geo, facets, filters etc.
Any advice on how to paginate a  REST DSL query is greatly appreciated.
Best,
Andy

Hi, if you use the "raw" API by sending hashes over the wire, than you have to mix the size and from values into the hash, as describe in the ES docs.
Ping me again if you encounter any problems...

Thank you for the quick response. After looking at the Tire unit tests I see that it now supports geo filters, so I rewrote my queries in the native DSL like e.g:
 recommended_events = Event.search do |search|
    search.query do |query|
        query.boolean do
            must { range :start_time, {:to => DateTime.now} }
        end
    end
    search.sort { by :start_time, 'asc' }
    search.filter :geo_distance, :distance => "12km", :location => {"lat" =>37.7749295, "lon" => -122.4194155}
    search.from 3
    search.size 3
 end

I have two questions with regards to this:
-  I need a mechanism to show number of 'pages' for pagination. How do I determine the total number of search results?
-  Does 'from' refer to the index in the search results after sorting?

I found the answer to the first question by looking at your code:
https://github.com/karmi/tire/blob/master/lib/tire/results/pagination.rb
The total number of elements is fortunately returned by the 'total' variable.
With regards to the second question it heuristically seems like the sorted results from the parameter @from@ offset in the result is returned. However, please let me know if you can confirm this as the intended semantics when an index is spread over many shards.


Adds cppcheck, closes #33

Re: Arduino code - yes! I'm focused on all the GUI infra currently - will refocus on arduino once we're in a good place here

Re: Local tasks - in my unit testing work I've been building out a nice little CLI for running common tasks. Coming soon!


"The Angular Compiler requires TypeScript" after fresh npm i and ng serve

Issue type
I'm submitting a ...  (check one with "x")

[x] bug report
[ ] feature request
[ ] question about the decisions made in the repository

Issue description
Exception after ng serve
C:\Data\Projects\Personalprojekt\ngx-admin-fork\node_modules\@angular\compiler-cli\src\typescript_support.js:65
            throw new Error("The Angular Compiler requires TypeScript >=" + minVersion + " and <" + maxVersion + " but " + version + " was found instead.");
            ^

Error: The Angular Compiler requires TypeScript >=4.2.3 and <4.4.0 but 4.4.4 was found instead.
    at checkVersion (C:\Data\Projects\Personalprojekt\ngx-admin-fork\node_modules\@angular\compiler-cli\src\typescript_support.js:65:19)
    at Object.verifySupportedTypeScriptVersion (C:\Data\Projects\Personalprojekt\ngx-admin-fork\node_modules\@angular\compiler-cli\src\typescript_support.js:70:9)
    at new NgtscProgram (C:\Data\Projects\Personalprojekt\ngx-admin-fork\node_modules\@angular\compiler-cli\src\ngtsc\program.js:47:38)
    at AngularWebpackPlugin.updateAotProgram (C:\Data\Projects\Personalprojekt\ngx-admin-fork\node_modules\@ngtools\webpack\src\ivy\plugin.js:311:32)
    at C:\Data\Projects\Personalprojekt\ngx-admin-fork\node_modules\@ngtools\webpack\src\ivy\plugin.js:188:24
    at Hook.eval [as call] (eval at create (C:\Data\Projects\Personalprojekt\ngx-admin-fork\node_modules\tapable\lib\HookCodeFactory.js:19:10), <anonymous>:24:1)
    at Hook.CALL_DELEGATE [as _call] (C:\Data\Projects\Personalprojekt\ngx-admin-fork\node_modules\tapable\lib\Hook.js:14:14)
    at Compiler.newCompilation (C:\Data\Projects\Personalprojekt\ngx-admin-fork\node_modules\webpack\lib\Compiler.js:1043:30)
    at C:\Data\Projects\Personalprojekt\ngx-admin-fork\node_modules\webpack\lib\Compiler.js:1088:29
    at Hook.eval [as callAsync] (eval at create (C:\Data\Projects\Personalprojekt\ngx-admin-fork\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:22:1)

Current behavior:
Exception appears.
Expected behavior:
No exception should appear
Steps to reproduce:
rm -r node_modules
rm package-lock.json
npm i --legacy-peer-deps
ng serve
Other information:
The error appears because angular cli currently only supports 4.2. or 4.3. but not 4.4.

Is there a way to avoid this exception? I dont seem to be able to get passed it after deleting the node_modules and package-lock.json.

Check out my pull request :)
https://github.com/akveo/ngx-admin/pull/5894/files
Does that help? I have created two more pull requests that adress similar problems, but unfortunately these don't get attention by the maintainers...

Nope sadly it didnt help. Im wondering what is the case here because I tried on a new angular project and everything seems fine there.

So i somehow got to go around this by using an old node modules folder. I noticed that in the version that was resulting in this exception, @angular-devkit/builder-angular was having version 13.x.x, while @angular-devkit/core and @angular-devkit/schematics were having version 12.x.x.
But after using replacing the node_modules folder with an old one, all version are consistent (photo above) and i can serve the application again.
Could you please check if this is also the case for you when this exception appears?

How i fixed this exception:

do a fresh clone of the repository
rm package-lock.json
rm -r node_modules
Change package.json to "typescript": "~4.2.3||~4.3.0"
npm i
ng serve
=> Now the exception is not present any more

Can you confirm that the exception is away after repeating my steps?
Although now there is a new exception that i fixed with that pull request: https://github.com/akveo/ngx-admin/pull/5896/files
After you fix this there is a new issue with ng2-ckeditor that i also already addressed with https://github.com/akveo/ngx-admin/pull/5898/files
=> After applying all three pull requests you should get it working

Thanks @MaaxGr  ,,, Your PRs should get merged asap, these are very helpful.. these are life-saver.

@vaibhavkumar-sf Any Idea how to get the attention of the maintainers? :D

@KostyaDanovsky @nnixaa @Tibing @yggg @denStrigo @hryb @lexzhukov @lugovsky @maksim-karatkevich @elupanov @katebatura  .. can anyone please give attention to this solution? It worked like a charm : https://github.com/akveo/ngx-admin/issues/5893#issuecomment-1114004416

Thanks 👍

Sorry guys. We do not actively maintain project. Hope it will change in 2022 Q4.

@elupanov Thanks for your reply and merging PRs, & it is the best open-source theme available right now in Angular, so, it is widely used, & Nebular components are also Awesome, so it's fine not to add new features actively here, but issues like these were blocking users in installing this, so these must be checked atleast weekly :)  Also, add in the readme that "It will NOT work in Node-16" . It is working fine in NODE-14.18.2 , because  node-sass version used in package.json is 4.14, which WILL NOT SUPPORT Node 15 & 16 (screenshot attached)

@vaibhavkumar-sf thanks for the hint
I've added installation notes with required NodeJS version


Use variables for z-index

Our z-index rules are mostly set with raw values, and we're starting to see collisions between them - especially extensions like widgets. This issue requires all z-index rules across the repo to be driven by a set of variables to ensure against unexpected visibility issues for non-static positioned elements.

Hello, I'd like to work on this.

@Manish-Giri could have sworn we talked about this, maybe in Slack? Anyway, yes, please do!

https://github.com/Android0868/torch.github.io.git


Idea to improve readability of explanations of date-range searches

⚠ Please check that this feature request hasn't been suggested before.

[X] I searched previous Ideas in Discussions didn't find any similar feature requests.
[X] I searched previous Issues didn't find any similar feature requests.

🔖 Feature description
Currently, the explanation of date-range searches looks like this:
starts 2023-01-01 2023-02-02 =>
  start date is between 2023-01-01 (Sunday 1st January 2023) and 2023-02-02 (Thursday 2nd February 2023) inclusive OR no start date

It's OK, but would be a bit more readable if the two dates were vertically aligned.
If there are several date range filters in a boolean combination, it gets still harder to read.
( starts 2023-01-01 2023-02-02 ) OR ( scheduled 2023-01-01 2023-02-02 ) OR ( due 2023-01-01 2023-02-02 ) OR ( done 2023-01-01 2023-02-02 ) OR ( due 2023-01-01 2023-02-02 ) OR ( happens 2023-01-01 2023-02-02 ) =>
  OR (At least one of):
    start date is between 2023-01-01 (Sunday 1st January 2023) and 2023-02-02 (Thursday 2nd February 2023) inclusive OR no start date
    scheduled date is between 2023-01-01 (Sunday 1st January 2023) and 2023-02-02 (Thursday 2nd February 2023) inclusive
    due date is between 2023-01-01 (Sunday 1st January 2023) and 2023-02-02 (Thursday 2nd February 2023) inclusive
    done date is between 2023-01-01 (Sunday 1st January 2023) and 2023-02-02 (Thursday 2nd February 2023) inclusive
    due date is between 2023-01-01 (Sunday 1st January 2023) and 2023-02-02 (Thursday 2nd February 2023) inclusive
    due, start or scheduled date is between 2023-01-01 (Sunday 1st January 2023) and 2023-02-02 (Thursday 2nd February 2023) inclusive

✔ Solution
I'm thinking that this layout would be a lot more readable for the first example above:
starts 2023-01-01 2023-02-02 =>
  start date is between:
    2023-01-01 (Sunday 1st January 2023) and
    2023-02-02 (Thursday 2nd February 2023) inclusive
    OR no start date

And for the second:
( starts 2023-01-01 2023-02-02 ) OR ( scheduled 2023-01-01 2023-02-02 ) OR ( due 2023-01-01 2023-02-02 ) OR ( done 2023-01-01 2023-02-02 ) OR ( due 2023-01-01 2023-02-02 ) OR ( happens 2023-01-01 2023-02-02 ) =>
  OR (At least one of):
    start date is between:
      2023-01-01 (Sunday 1st January 2023) and
      2023-02-02 (Thursday 2nd February 2023) inclusive
      OR no start date
    scheduled date is between:
      2023-01-01 (Sunday 1st January 2023) and
      2023-02-02 (Thursday 2nd February 2023) inclusive
    due date is between:
      2023-01-01 (Sunday 1st January 2023) and
      2023-02-02 (Thursday 2nd February 2023) inclusive
    done date is between:
      2023-01-01 (Sunday 1st January 2023) and
      2023-02-02 (Thursday 2nd February 2023) inclusive
    due date is between:
      2023-01-01 (Sunday 1st January 2023) and
      2023-02-02 (Thursday 2nd February 2023) inclusive
    due, start or scheduled date is between:
      2023-01-01 (Sunday 1st January 2023) and
      2023-02-02 (Thursday 2nd February 2023) inclusive

❓ Alternatives
No response
📝 Additional Context
No response

Fixed by #1836

Just to confirm that the new output from my example above is now:
( starts 2023-01-01 2023-02-02 ) OR ( scheduled 2023-01-01 2023-02-02 ) OR ( due 2023-01-01 2023-02-02 ) OR ( done 2023-01-01 2023-02-02 ) OR ( due 2023-01-01 2023-02-02 ) OR ( happens 2023-01-01 2023-02-02 ) =>
  OR (At least one of):
    start date is between:
      2023-01-01 (Sunday 1st January 2023) and
      2023-02-02 (Thursday 2nd February 2023) inclusive
      OR no start date
    scheduled date is between:
      2023-01-01 (Sunday 1st January 2023) and
      2023-02-02 (Thursday 2nd February 2023) inclusive
    due date is between:
      2023-01-01 (Sunday 1st January 2023) and
      2023-02-02 (Thursday 2nd February 2023) inclusive
    done date is between:
      2023-01-01 (Sunday 1st January 2023) and
      2023-02-02 (Thursday 2nd February 2023) inclusive
    due date is between:
      2023-01-01 (Sunday 1st January 2023) and
      2023-02-02 (Thursday 2nd February 2023) inclusive
    due, start or scheduled date is between:
      2023-01-01 (Sunday 1st January 2023) and
      2023-02-02 (Thursday 2nd February 2023) inclusive

Absolutely brilliant, @ilandikov!! ❤ 😆 🎉

All the credits should go to my mentor ;)


Build Failing for Commit 2b6cac25823af011ff3bc7628bc9b06e483c5a08

Platform Information
$ node -v
v16.19.1
$ uname -a
Linux ******-********** <IP_ADDRESS>-microsoft-standard-WSL2 #1 SMP Fri Jan 27 02:56:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Failed Unit Test: pathological tests hangs on crc hash
 1) Pathological sequences speed
       Cmark
         verify original source crc:

      AssertionError [ERR_ASSERTION]: CRC or cmark pathological tests hanged. Verify and update pathological.json
      actual expected

      68c7c28fe0d4a34367f27dcbceec9fedda7a30ea2886aea813e50c2764ecc40f

      at Context.<anonymous> (test/pathological.js:53:14)
      at processTicksAndRejections (node:internal/process/task_queues:96:5)

The full build log can be found here

Fixed in master


'sage' requirement?

When running some of the attack modes I get a "Can't load (...) because sage is not installed"
F.instance: "Can't load ecm because sage is not installed".
Is there a missing requirement in requirements.txt?

Some modules like "ecm" require sage binary on the system.
look at https://doc.sagemath.org/html/en/installation/binary.html for instructions.


Use a parallel sort to order txs while speculating

A small follow-up to https://github.com/AleoHQ/snarkVM/pull/2421 and the replacement of https://github.com/AleoHQ/snarkVM/pull/2424. The changes are:

a cfg_sort_unstable_by macro for parallel sorting using a closure is introduced (note: the unstable part only means that equal elements may be reordered, and transaction IDs are never equal)
the aforementioned macro is used to sort transactions when speculating
the parallel iteration for the collection is removed, as it is slower than single-threaded iteration (since Transaction::id is basically free)
instead of enumerating and collecting indices, IndexSet::get_index_of is used

Is the assumption that sort_unstable is safe because the IDs are supposed to be unique?

The unstable sort is safe, it only may reorder equal elements.
However, I realized that due to lookups, caching the key would be more meaningful here; I added a macro for sorting by cached key and adjusted this PR to use it.
I kept the macro for unstable sorting, as it may be useful in the future, for applications where they key extraction function is cheap.


Feature: mark current selected tab

Feature

[X] I have read the comment above and have completed each step
[X] I have filled in each heading below

Is your feature request related to a problem? Please describe
there is no visual feedback of what is the selected sticker pack in the tab icons.
Describe the solution you'd like
usually the tab would be underlined, so I recommend to underline the selected tab.

I took a look at this and honestly can't work out how to do this easily, if you have any ideas then you can open a merge request or drop a reply and I'd be happy to include it as I agree that it would be a good QOL feature


tail: don't optimize beyond fetch_size

If the tail limit exceeds the fetch size, then we don't get points
in the right order. Rather than add a bunch of complexity to keep
optimizing this edge case, let's just not optimize it.
@VladVega

Just in case you didn't see my threaded +1 above, then +1.


feature: android notification data pass

Description
This PR is a cherry-pick of https://github.com/phonegap/phonegap-plugin-push/pull/2369
Full description can be seen in the above PR and the associated original ticket: https://github.com/phonegap/phonegap-plugin-push/issues/2364
Related Issue
closes #30
Motivation and Context
Ticket Request
How Has This Been Tested?

n/a

Screenshots (if appropriate):

n/a

Types of changes
From Original PR

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:
From Original PR

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Additional Changes
I updated the original PR's Android src code to follow new syntax.

I have not perform a manual test and will try and take a look into how to test this PR.
Also from reading the PR markdown and also the original ticket, it says:

my suspicion is that in seeing the notification part of the payload the OS will take over to display the notification in the notification shade. It will ignore the icon and sound properties set in the init method. Such are the constraints we are faced with when we want to enable folks to set this from JS code.

and

By using the notification object in your payload, in all cases, all custom notification features provided by this plugin are unavailable.

I suspect this is acceptable?

I suspect this is the acceptable use case?

I do believe so. Users of the original plugin were advised to put everything in the data section of the payload. This PR adds functionality and allows to use both data and notification sections.


endPoint cannot be changed after initial execute

When the endPoint gets changed after the plugin has already been executed, it will generate an invalid request.
As a quick fix I commented out the following condition in OperationHelper.prototype.getSignatureHelper:
if (typeof(this.signatureHelper) === 'undefined')

I believe I am having this problem as well. Did you discover this because the endPoint should be webservices.amazon.com rather than ecs.amazonaws.com? http://docs.aws.amazon.com/AWSECommerceService/latest/DG/AnatomyOfaRESTRequest.html#EndpointsandWebServices
Might be a good idea to change the default as well unless there is some other reason to use ecs.amazonaws.com...

fyi- I just noticed this issue, looked at the code and think it will affect me too. I've forked and may send a pr shortly.

Please see the discussion on @trentmillar's PR if you are interested.

Link to said PR: https://github.com/dmcquay/node-apac/pull/58

Closing this due to lack of interest. Please feel free to reopen.


Update showcases.js

Showcase addition

Name: Cardania
Description: Cardania is a scifi fantasy metaverse gaming ecosystem project being built on the Cardano blockchain. Welcome to the most rad destination in the metaverse.
Link:  https://www.cardania.com
Source: <link_to_source_code>
Tags:

game
nft

ooo that is a problem.  I'm sorry about that, let me fix that

Updated!

@jonathanfishbein1 looks good, but is this live or a preview? It doesn't look like anything can be done.

The development is iterative but already has network connectivity - We most recently ran a very popular NFT sale utilizing our website for the front end and NFT Maker Pro for the backend. Delegators are also able to stake to SUMN directly from the site. Users will see a lot more game interaction in the coming months which we're very excited for.

Thank you for your contribution and for building on Cardano. This PR has been open for quite a while and I would like to give you a little feedback. Projects need 3 reviewer approvals and it seems the project didn't get enough "traction" among the reviewers.
Please note that showcase projects need to provide a unique value from existing showcase items - which is especially difficult with many tokens and FT/NFT or FT/NFT platforms. Feel free to join the discussion here: #243 (or in case you prefer to discuss this not in GitHub please join https://discord.gg/Exe6XmqKDx)
Suggestion: you can add your project to https://github.com/input-output-hk/essential-cardano


📃:

🔴 Title: Drum Kit - Fun Beginner-Friendly Project
🔴 Tech stack:

HTML
CSS
JavaScript

🔴 Objective:
To create an interactive drum kit web app where pressing specific keys on the keyboard triggers corresponding drum sounds.
🔴 Summary:
This project is designed to be beginner-friendly, focusing on basic DOM manipulation and event handling in JavaScript. Users press keys (e.g., 'W', 'A', 'S', 'D', 'J', 'K', 'L') to hear different drum sounds, providing an engaging way to learn web development while creating a fun and functional app. It also teaches the use of CSS for styling and enhancing the visual appeal of the project.
📸 Screenshots:

✅ Details to Include When Taking the Issue:
Name: [Your Name]
Participant Role: Hacktoberfest , gssoc , gssoc-ext

Happy Contributing! 🚀
Wishing you all the best on your open source journey. Enjoy! 😎

Feel free to customize it further!

The project already exist, Do not be demotivated and raise a new issue.


Release

:tada: This PR is included in version 0.126.0 :tada:
The release is available on:

v0.126.0
v0.126.0
GitHub release

Your semantic-release bot :package::rocket:


Explanation of Directory Structure

Hello,
I am using drywall for user management for a health-care project. But I am confused with the directory structure. Specifically I want to know the difference between "/public/layouts" and "/layouts", again "/public/views" and "/views".

This is how i see it
public/views is client side , like the javascript on a page form
views/ is server side, like the javascript handling the login and db updates
same goes for the layouts ..some work is done server side including default css ,footers, headers for the site and some work is done client side like how the page will be rendered with client data.

Thanks for opening an issue @davik. I think @scottmont said it well. Let us know if you have more questions.

Thank you very much!!


A* Path Finding Algorithm

Hey Rachel! I finally got my username and email set so I can do these pulls and commits and whatnot lol. Git Hub is still very new to me, so if I messed up the commit, pull and merge process please let me know so I can correct anything on my end.
As for the codes, I linked the websites that I found as a comment. I'm still getting to understand them myself, but I think A* Draft 2 is a better fit for us. The way I understand how we could make the code fit the floor plan we choose is If we look at it as it's some made-up place in a video game and go from there, at least that's how I'm understanding hehe.
These are just samples that I found on the web, so they aren't tweaked for our project yet. I want to know if this would be a good first step to take.
See you later today!
Tega

This is good information to keep, but I'm not going to merge this PR since we are not using these files in the actual project. Refer back to this PR for future reference!


discode does not work on runner

Some commands like see and discode does not work properly on the runner. see works fine for colon-defined functions but fails for built-in operators (after printing something like Code +):
in file included from *OS command line*:-1
tests.4th:4: No such file or directory
see >>>+<<<
Backtrace:
$7F4CA0458C40 throw
$0
$7F4CA0472298 slurp-fid
$7F4CA0472558 gdb-addr-sep-char
$A
$7F4CA046D6A8 discode
$7F4CA046E060 seecode
$7F4CA046E5F0 xt-see
$55C57843C1C8
$7F4CA046E848 name-see

Which is related to how discode would fail:
in file included from *OS command line*:-1
tests.4th:4: No such file or directory
' + 8 >>>discode<<<
Backtrace:
$7F0FBE510C40 throw
$0
$7F0FBE52A298 slurp-fid
$7F0FBE52A558 gdb-addr-sep-char
$A

(I think there are a few more commands that don't work but I forgot which)
It's not Undefined word, so GForth recognizes discode, but failed due to some other reasons.
But according to official documentation at least, shouldn't discode fall back to dump if no disassembler is available? dump works fine on the runner though. Did something pretend there are disassemblers and only fail when actually trying to call them (due to something like file permission)?

See https://stackoverflow.com/questions/44014281/dissassembly-of-forth-code-words-with-see and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655550
Looks like a workaround is to set ptrace_scope to 0 (or run as root), but I'm not doing that for security reasons.
Maybe newer versions of gforth doesn't have this issue, but 0.7.3 is the latest stable and I don't really want to use unstable releases that requires us to build from source.

There's actually a preview 0.7.9 in the make since 2020, so don't hold your breath. I'm closing this issue for now. When a new version becomes available we will request a new version of gforth on CW.


Link to resource does not work

This week is getting longer ---- the link to Microsoft Teams UI Kit (Figma) is running and error and cannot load.

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

ID: 8c700ab9-9512-a9e4-a1a5-4c615925cf0d
Version Independent ID: fd80ea24-e549-0918-4dd3-47bd46e34cad
Content: Designing task modules - Teams
Content Source: msteams-platform/task-modules-and-cards/task-modules/design-teams-task-modules.md
Service: msteams
GitHub Login: @heath-hamilton
Microsoft Alias: lajanuar

We checked by clicking on this link

and its getting redirected properly as shown below:

Thank you Prasad-MSFT


'Failed to resolve directive' error

Hi. Another plugin is not working. https://github.com/JALBAA/vue-lazyload-img
import Vue from 'vue'
import Lazyload from 'vue-lazyload-img'

Vue.use(Lazyload, {
  fade: true,
  speed: 20,
  time: 300
})

     <img v-lazyload="'https://test.jpeg'"/>

Empty img tag is rendered. In devtools console error:
Failed to resolve directive: lazyload

Tried as plugin, tried import on page. The same error.

Solved, bug with vue-lazyload-img


xfsprogs: replace glibc-2.27 patch w/upstream variant

This version also works w/musl :)
https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/patch/?id=8041435de7ed028a27ecca64302945ad455c69a6
cc @shlevy

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

Maybe just upgrade the package instead?

Optimistically moving ahead, just wanted to make sure you saw :).  Hopefully uncontroversial since we're using upstream fix :).

(I suspect that fix didn't exist when you were working on this, hehe)

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: xfsprogs
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: xfsprogs
Partial log (click to expand)
shrinking /nix/store/n645c3nkbaqbcwscdwajwjz6bhsingw1-xfsprogs-4.14.0/lib/libxlog.so.0.0.0
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/n645c3nkbaqbcwscdwajwjz6bhsingw1-xfsprogs-4.14.0/lib
patching script interpreter paths in /nix/store/n645c3nkbaqbcwscdwajwjz6bhsingw1-xfsprogs-4.14.0
checking for references to /tmp/nix-build-xfsprogs-4.14.0.drv-0 in /nix/store/n645c3nkbaqbcwscdwajwjz6bhsingw1-xfsprogs-4.14.0...
shrinking RPATHs of ELF executables and libraries in /nix/store/v39s40qxxia6wcrj9n8gapag1lll7bjw-xfsprogs-4.14.0-doc
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/v39s40qxxia6wcrj9n8gapag1lll7bjw-xfsprogs-4.14.0-doc
checking for references to /tmp/nix-build-xfsprogs-4.14.0.drv-0 in /nix/store/v39s40qxxia6wcrj9n8gapag1lll7bjw-xfsprogs-4.14.0-doc...
/nix/store/wy4z3a0pln196777q00brv4bnzicbisj-xfsprogs-4.14.0-bin

Success on aarch64-linux (full log)
Attempted: xfsprogs
Partial log (click to expand)
shrinking /nix/store/0l9hhrida7vwh704606iv8zl6a34n1dc-xfsprogs-4.14.0/lib/libxfs.so.0.0.0
strip is /nix/store/j7d4mr0ikv974ig7yzhknpsq288js4bs-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/0l9hhrida7vwh704606iv8zl6a34n1dc-xfsprogs-4.14.0/lib
patching script interpreter paths in /nix/store/0l9hhrida7vwh704606iv8zl6a34n1dc-xfsprogs-4.14.0
checking for references to /build in /nix/store/0l9hhrida7vwh704606iv8zl6a34n1dc-xfsprogs-4.14.0...
shrinking RPATHs of ELF executables and libraries in /nix/store/sq08600cna79p4cwmab2fzl6bfj0xj5f-xfsprogs-4.14.0-doc
strip is /nix/store/j7d4mr0ikv974ig7yzhknpsq288js4bs-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/sq08600cna79p4cwmab2fzl6bfj0xj5f-xfsprogs-4.14.0-doc
checking for references to /build in /nix/store/sq08600cna79p4cwmab2fzl6bfj0xj5f-xfsprogs-4.14.0-doc...
/nix/store/w4hiynajhwk287nrx9f1f7xpw2wv2wsh-xfsprogs-4.14.0-bin

Maybe just upgrade the package instead?

I tried that first but had problems making it work (4.15.1) regardless of libc.  Note there are newer gentoo patches to use but even so.
Here's about where I left that effort, if anyone wants to revisit it in the future: https://github.com/dtzWill/nixpkgs/releases/tag/xfsprogs-4.15.1-wip
It fails trying to--I guess-- find Makefile rules for LDFLAGS-esque things like -lrt or -lunistring.  Not sure what's going on there.
While visiting this I'll note other folks seem to build with DEBUG=-NDEBUG which we may wish to do as well, but I was only going to explore that after the update worked.... :).

:ship: Yeah, this wasn't upstream when I looked for it.

Ok, thanks for the work on the upgrade, I will continue on that some day. For some reason xfsprogs always needs some patches to actually compile... it's like linking dynamically to stuff in 2018 is rocket science or something...


GoDoc corrupted output

The godoc for this package show a bunch of go comments (beginning with //) in the argument list for the Reporter() method.

Duplicate of golang/go#32532


Better action files secret handling

Current: lakeFS users wanting to use secrets in their Airflow/Web hooks, must place them as plaintext in the action file. Although the action files path can be restricted, it creates a coupling between managing action files and access to secrets to be used by them.
Desired: Secrets are not used directly in action files, but stored safely in lakeFS (or any other 3rd party) and referenced from there.

I don't see secrets being used in files in any other way than Github is doing today. Basically having a special syntax to reference the secret (like {{ secrets.MY_SECRET }} ). However there are several ways to store and handle these secrets.
Possible ways to go here:

lakeFS to handle the secrets by exposing CRUD API for secrets and storing those encrypted in the DB. It might limit us when moving away from postgres. Also users might be reluctant to trust us with their secrets.
lakeFS to integrate with cloud secret storages like AWS Secret Manager, GCS Secret Manager or even Kubernetes Secrets. This will require us to support many new integrations with the different solutions, similarly to what we have with the block adapters.
Support just env vars. lakeFS will parse the contents of the action files and will read the secrets from env vars. Every known solution has a mechanism in place to inject secrets as env vars.

Voting for 3: I don't think it's in the scope of our product to manage secrets. Like you said, it's pretty common to put secrets in environment variables. We can do this and wait for the feedback.

Agree with @johnnyaug on this - there are existing solutions (as listed in option 2) that are more suitable for secret storage. if we do 3 we allow users to integrate those solution using standard ways.


add cleos set contract/code/abi --clear

Provide a way to remove contract from shell scripts or command line..
When using --clear, it will remove contract/abi/code.
for example:
cleos set code eosio.token --clear
Setting Code...
executed transaction: a34a611311f40f96560d836a3b3f6533bf48e2a9122859aa551b6af1ddc1b1fa  96 bytes  6853 us
#         eosio <= eosio::setcode               {"account":"eosio.token","vmtype":0,"vmversion":0,"code":""}

cleos set abi eosio.token --clear
Setting ABI...
executed transaction: 0eb4ac374163fc12484e491ef839965af3d4e2b4830d3c549bfff11a9baccb23  96 bytes  5633 us
#         eosio <= eosio::setabi                {"account":"eosio.token","abi":""}

cleos set contract  eosio.token --clear
Publishing contract...
executed transaction: e6747258e63153ef271f66032123ad444562d161987d4ed924fc6154fd404952  104 bytes  5210 us
#         eosio <= eosio::setcode               {"account":"eosio.token","vmtype":0,"vmversion":0,"code":""}
#         eosio <= eosio::setabi                {"account":"eosio.token","abi":""}

I am getting ERROR: ExtrasError: [--clear]" after running cleos set contract aromaticbeer ./build/contracts/eosio.token --clear

@johnworthley  Are you use new cleos replace /usr/local/bin/cleos?

I found the problem. eosio/eos-dev:v1.3.0 is not updated after investigating eos/programs/cleos/main.cpp in the dev docker. Please verify

No I use docker pull eosio/eos-dev
On Thu, Sep 20, 2018 at 9:12 AM fires<EMAIL_ADDRESS>wrote:

@johnworthley https://github.com/johnworthley Are you use new cleos
replace /usr/local/bin/cleos?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/EOSIO/eos/pull/5442#issuecomment-423177153, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ARg9qnMy71uf4nYNU5JOmVwJw2oq6C-aks5uc5QqgaJpZM4WNpnb
.


🐛 BUG: In Vectorize filter by metadata keys not working.

Which Cloudflare product(s) does this pertain to?
Workers for Platforms, Workers Runtime
What version(s) of the tool(s) are you using?
3.15.0
What version of Node are you using?
v18.17.1.
What operating system are you using?
Mac and Linux
Describe the Bug
I am using Vectorize for indexing and querying vectors  but it works only query by vectors. But attribute filter is a common for most use-case we should be able to filter by one or more metadata keys and apply query vectors. Thats not working.  I cant see any documentation to do the same. Whats the syntax I checked CLIs , JS and API docs none of them seem to show.
In this case query by vectors (on values) and filter by price or description.
{
    id: "97913813",
    values: [0.16, 1.2, 3.8],
    metadata: { "description": "DSLR camera", "price": 13.99$ },
  },

I am sure this feature is included as it is a 1st class feature for DBs, So I assume this to be a omission in the documentation by mistake ?
let queryVector = [54.8, 5.5, 3.1];
let matches = await env.YOUR_INDEX.query(queryVector, { topK: 1, returnValues: true, returnMetadata: true })

Please provide a link to a minimal reproduction
No response
Please provide any relevant error logs
No response

Transferring this to workerd since it's a feature request for the Vectorize JS API cc @vy-ton

@PrithivirajDamodaran You can add a filter property when calling query(), see example here

@vy-ton linked example no longer shows how to use filters. Can't find any such example.


Fix typos

Hi, and thanks for these! My only issue is that the files in the winamp folders aren't mine and should not be changed.
If you resubmit the PR without those files I'll pull it in. Thanks!

Done :)

Thanks! Funny, we all know how to spell variants now!  :grin: