fix penumbra-specific timestamp reads in ibc module

Describe your changes
fix penumbra-specific timestamp reads in ibc module by using HostInterface instead.

Ics20WithdrawalWithHandler was created analogously to IbcRelayWithHandler, which attaches a HostInterface to be used in check_and_execute to get the current block timestamp
the rpc method client_state was also updated to use HostInterface

Issue ticket number and link
closes #4812
Checklist before requesting a review

[x] If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason:

the timestamp reads are unchanged for penumbra, as the PenumbraHost is used, which calls the same methods as before

wasm crate seems to build fine with this alternate patch. what's the difference here?
diff --git a/packages/wasm/crate/Cargo.toml b/packages/wasm/crate/Cargo.toml
index c78cd16f7..a58548b8e 100644
--- a/packages/wasm/crate/Cargo.toml
+++ b/packages/wasm/crate/Cargo.toml
@@ -14,21 +14,21 @@ default = ["console_error_panic_hook"]
 mock-database = []

 [dependencies]
-penumbra-auction = { git = "https://github.com/penumbra-zone/penumbra.git", tag = "v0.80.0", package = "penumbra-auction", default-features = false }
-penumbra-asset = { git = "https://github.com/penumbra-zone/penumbra.git", tag = "v0.80.0", package = "penumbra-asset" }
-penumbra-compact-block = { git = "https://github.com/penumbra-zone/penumbra.git", tag = "v0.80.0", package = "penumbra-compact-block", default-features = false }
-penumbra-dex = { git = "https://github.com/penumbra-zone/penumbra.git", tag = "v0.80.0", package = "penumbra-dex", default-features = false }
-penumbra-fee = { git = "https://github.com/penumbra-zone/penumbra.git", tag = "v0.80.0", package = "penumbra-fee", default-features = false }
-penumbra-governance = { git = "https://github.com/penumbra-zone/penumbra.git", tag = "v0.80.0", package = "penumbra-governance", default-features = false }
-penumbra-keys = { git = "https://github.com/penumbra-zone/penumbra.git", tag = "v0.80.0", package = "penumbra-keys" }
-penumbra-num = { git = "https://github.com/penumbra-zone/penumbra.git", tag = "v0.80.0", package = "penumbra-num" }
-penumbra-proof-params = { git = "https://github.com/penumbra-zone/penumbra.git", tag = "v0.80.0", package = "penumbra-proof-params", default-features = false }
-penumbra-proto = { git = "https://github.com/penumbra-zone/penumbra.git", tag = "v0.80.0", package = "penumbra-proto", default-features = false }
-penumbra-sct = { git = "https://github.com/penumbra-zone/penumbra.git", tag = "v0.80.0", package = "penumbra-sct", default-features = false }
-penumbra-shielded-pool = { git = "https://github.com/penumbra-zone/penumbra.git", tag = "v0.80.0", package = "penumbra-shielded-pool", default-features = false }
-penumbra-stake = { git = "https://github.com/penumbra-zone/penumbra.git", tag = "v0.80.0", package = "penumbra-stake", default-features = false }
-penumbra-tct = { git = "https://github.com/penumbra-zone/penumbra.git", tag = "v0.80.0", package = "penumbra-tct" }
-penumbra-transaction = { git = "https://github.com/penumbra-zone/penumbra.git", tag = "v0.80.0", package = "penumbra-transaction", default-features = false }
+penumbra-auction = { git = "https://github.com/penumbra-zone/penumbra.git", branch = "noot/host-interface-fix", package = "penumbra-auction", default-features = false }
+penumbra-asset = { git = "https://github.com/penumbra-zone/penumbra.git", branch = "noot/host-interface-fix", package = "penumbra-asset" }
+penumbra-compact-block = { git = "https://github.com/penumbra-zone/penumbra.git", branch = "noot/host-interface-fix", package = "penumbra-compact-block", default-features = false }
+penumbra-dex = { git = "https://github.com/penumbra-zone/penumbra.git", branch = "noot/host-interface-fix", package = "penumbra-dex", default-features = false }
+penumbra-fee = { git = "https://github.com/penumbra-zone/penumbra.git", branch = "noot/host-interface-fix", package = "penumbra-fee", default-features = false }
+penumbra-governance = { git = "https://github.com/penumbra-zone/penumbra.git", branch = "noot/host-interface-fix", package = "penumbra-governance", default-features = false }
+penumbra-keys = { git = "https://github.com/penumbra-zone/penumbra.git", branch = "noot/host-interface-fix", package = "penumbra-keys" }
+penumbra-num = { git = "https://github.com/penumbra-zone/penumbra.git", branch = "noot/host-interface-fix", package = "penumbra-num" }
+penumbra-proof-params = { git = "https://github.com/penumbra-zone/penumbra.git", branch = "noot/host-interface-fix", package = "penumbra-proof-params", default-features = false }
+penumbra-proto = { git = "https://github.com/penumbra-zone/penumbra.git", branch = "noot/host-interface-fix", package = "penumbra-proto", default-features = false }
+penumbra-sct = { git = "https://github.com/penumbra-zone/penumbra.git", branch = "noot/host-interface-fix", package = "penumbra-sct", default-features = false }
+penumbra-shielded-pool = { git = "https://github.com/penumbra-zone/penumbra.git", branch = "noot/host-interface-fix", package = "penumbra-shielded-pool", default-features = false }
+penumbra-stake = { git = "https://github.com/penumbra-zone/penumbra.git", branch = "noot/host-interface-fix", package = "penumbra-stake", default-features = false }
+penumbra-tct = { git = "https://github.com/penumbra-zone/penumbra.git", branch = "noot/host-interface-fix", package = "penumbra-tct" }
+penumbra-transaction = { git = "https://github.com/penumbra-zone/penumbra.git", branch = "noot/host-interface-fix", package = "penumbra-transaction", default-features = false }

 anyhow = "1.0.86"
 ark-ff = { version = "0.4.2", features = ["std"] }

notably wasm doesn't depend on the ibc crate at all, lol. maybe that is the difference

Excellent, thanks for the assist, @turbocrime! I'm not sure why my toml patch gave inaccurate results, but I agree with your solution, and appreciate the manual testing via local builds. My concerns are address, I'm happy to merge.

@noot for now, please use a git dep against the latest commit on main: 87adc8d6b15f6081c1adf169daed4ca8873bd9f6. We'll likely have a v0.80.3 tag up in a week or two.


Add support for different trinity root dirs

What was wrong?
This is a spin off and a continuation of the discussion that started in https://github.com/ethereum/py-evm/pull/1566#discussion_r241366836
Now that we have support for the trinity-beacon  command, we still need to sort out how we would like to handle all the files that Trinity saves to discs. Today, that looks roughly like this:
/home/cburgdorf/.local/share/trinity
├── mainnet
│   ├── chain
│   │   ├── full
│   │   │   └── db files
│   │   └── light
│   │       └── db files
│   ├── logs
│   │   ├── trinity.log
│   │   ├── ...
│   │   └── trinity.log.7
│   └── nodekey
└── ropsten
    ├── chain
    │   ├── full
    │   │   └── db files
    │   └── light
    │       └── db files
    ├── logs
    │   └── trinity.log
    │   ├── ...
    │   └── trinity.log.7
    └── nodekey

For the beacon node, I guess we need a different nodekey, we want to keep logs separate and we need different directories for beacon and shard dbs.
My preferred solution, would be to treat the beacon node as an entirely different program and hence maintain an entirely separate root directory which would then roughly look like this.
/home/cburgdorf/.local/share/trinity-beacon   <-- notice the different root path
├── mainnet
│   ├── chain
│   │   ├── full
|   |   |     ├── beacon
│   │   │     |     └── db files
|   |   |     ├── shard-1
│   │   │     |     └── db files
|   |   |     └── shard-n
│   │   │           └── db files
│   │   ├── light
|   |   |     ├── beacon
│   │   │     |     └── db files
|   |   |     ├── shard-1
│   │   │     |     └── db files
|   |   |     └── shard-n
│   │   │           └── db files
│   ├── logs
│   │   ├── trinity.log
│   │   ├── ...
│   │   └── trinity.log.7
│   └── nodekey
└── some_future_testnet
     ├── chain
     │   ├── full
     |    |     ├── beacon
     │    │     |     └── db files
     |    |     ├── shard-1
     │    │     |     └── db files
     |    |     └── shard-n
     │    │           └── db files
     │    ├── light
     |    |     ├── beacon
     │    │     |     └── db files
     |    |     ├── shard-1
     │    │     |     └── db files
     |    |     └── shard-n
     │    │           └── db files
     ├── logs
     │   └── trinity.log
     │   ├── ...
     │   └── trinity.log.7
     └── nodekey

The alternative to that would be to figure out a new layout that places the beacon node files side by side inside the existing trinity root directory.
However, that would most likely also mean that existing data directories need to be migrated.
I personally think the cleanest thing to do is to treat the beacon node as an entirely different program which we already do by exposing it via a separate trinity-beacon command and providing a separate bootstrapping with different plugins etc.
How was it fixed?
This implements the proposed solution by slightly changing our utils to allow setting using different root directories.
Cute Animal Picture

On alternative is that maybe trinity becomes the all-in-one command for running both the beacon and mainnet. What we currently call trinity moves to trinity-eth1 or something. Then implicitly trinity runs both trinity-beacon and trinity-eth1. So maybe the directory structure is something like trinity/beacon-mainnet/... and trinity/eth1-mainnet/....

Yes, we could introduce this sub-client level but it's also a strong breaking change which means either:

everyone needs to resync
we tell people how to move their files to handle the change
we auto-migrate existing directories

I'd be in favor to go down the simpler path and just treat the beacon node (and potentially the validator client, too) as entirely different programs with different root paths. In fact, maybe long term what we know today as trinity the client will just become a library with different clients being built on top of this (maybe similar to parity substrate even though I don't know anything beyond the marketing info about it)

Eh, we could go down the "it's an alpha suck-it-up" route, which we've decided before on this same basic issue.
Or we could name the eth1 mainnet as mainnet, and then it is backwards compatible with the current system.

Sure we can. But I would ask: what for? I think I just favor the idea of treating these as different applications. More flexibility, better separation of concerns, better isolation, less complexity. I guess I just don't see a strong argument why we should try treat this as one application or even make trinity the all-in-one command. What's with the linux philosophy of things? :)

@cburgdorf it should be trivial for us to write a quick plugin to do the migration for people so I'm :+1: on breaking change approach.  alpha is alpha...  We can also document the manual approach as well and really highlight the change in the release notes.

I guess I just don't see a strong argument why we should try treat this as one application or even make trinity the all-in-one command.

AIUI the beacon chain will have ultimately have checkpoints that allow you to sync mainnet from the middle of the chain. From a user's point of view, they probably don't want to start the mainnet and the beacon chain and then wire them together, just to get that benefit. So the concept of what trinity is to the end user might reasonably expand to include several "internal" applications that we wire together for them.

I'm :-1: on a whole new directory.  I think 1) beacon chain is going to be linked to main chain because it will provide finality for main chain so they aren't completely separate and 2) I like the proposal to have trinity implicitly run the full everything (beacon + main + whatever-shards).   and 3) separating them doesn't feel right since sharing a nodekey across all of these should be fine and there are likely other resources that are acceptable to be shared/colocated.

beacon chain is going to be linked to main chain because it will provide finality for main chain so they aren't completely separate

Ok, but I would argue that this kind of connection should rely on API access and not on both chains sharing the same application directory. Or put another way, I guess it should be totally reasonable for a trinity beacon node to receive any Ethereum 1 related information from a geth node.
All things considered I'm :-1: on mixing the application directories but I'm :+1: on democracy and if both of you prefer going down that route, so be it.
Let's dream up the application directory layout you'd like to have. How about this one. That one could even be backwards compatible by just having adding a chain-beacon directory next to the existing chain?
/home/cburgdorf/.local/share/trinity
├── mainnet                       <-- one mainnet directory, but different chain directories
│   ├── chain
│   │   ├── full
|   |   |     └── db files
│   │   └── light
|   |         └── db files
│   ├── chain-beacon
│   │   ├── full
|   |   |     ├── beacon
│   │   │     |     └── db files
|   |   |     ├── shard-1
│   │   │     |     └── db files
|   |   |     └── shard-n
│   │   │           └── db files
│   │   └── light
|   |         ├── beacon
│   │         |     └── db files
|   |         ├── shard-1
│   │         |     └── db files
|   |         └── shard-n
│   │               └── db files
│   ├── logs                      <-- one log directory per network but different file names
│   │   ├── trinity.log
│   │   ├── trinity-beacon.log
│   │   ├── ...
│   │   ├── trinity.log.7
│   │   └── trinity-beacon.log.7
│   └── nodekey
|
└── ropsten
    ├── chain
    │   ├── full
    |   |     └── db files
    │   └── light
    |         └── db files
    ├── chain-beacon
    │   ├── full
    |   |     ├── beacon
    │   │     |     └── db files
    |   |     ├── shard-1
    │   │     |     └── db files
    |   |     └── shard-n
    │   │           └── db files
    │   └── light
    |         ├── beacon
    │         |     └── db files
    |         ├── shard-1
    │         |     └── db files
    |         └── shard-n
    │               └── db files
    ├── logs
    │   ├── trinity.log
    │   ├── trinity-beacon.log
    │   ├── ...
    │   ├── trinity.log.7
    │   └── trinity-beacon.log.7
    └── nodekey

Ok, let me challenge this with one last line of thought before I give up.
Where do you see the ETH 2.0 / Serenity validator client fit in to this?
I've been telling @djrtwo and @hwwhww that my preference would be to build the validator client on top of Trinity because there is a lot of nice infrastructure to reuse (mostly plugin / event bus / multiprocessing architecture)
I know that @djrtwo wants the validator as separate as possible and I agree to that and made the point that the validator client would be a different piece of software from the perspective of the operation system (different command, different process(es) etc). It would be able to connect to any kind of different but compatible software by prysmatic, lighthouse, nimbus, <you name it>.
Now if you are saying that you also want to put the validator client into the same app directory as well, then clearly the line gets blurred. From the perspective of the operating system a clearly distinct program should absolutely use its own application directory.
If you are saying that the validator client should use its own application directory but the beacon node should share the application directory with the Ethereum 1 node then I would argue that this makes things even worse (consistency etc).
And on

I think 1) beacon chain is going to be linked to main chain because it will provide finality for main chain so they aren't completely separate

Most of the other ETH 2.0 clients that are currently being build do not even have an existing ETH 1.0 sister project that they could share the application directory with. I think any kind of connection between the ETH 2.0 and the ETH 1.0 client should rely on clear API boundaries and not on a shared application directory.
To visualize how I see the future vision of Trinity, actually think parts of the code base can be treated as a library with just different clients being build on top of it.
trinity-library
├── eth 1 cient   <- own command, process(es) and application directory
│
├── beacon client  <- own command, process(es) and application directory
│
└── validator client  <- own command, process(es) and application directory

I like that unix philosophy more than the all-in-one vision. It is easy enough to build a thin all-in-one wrapper atop, it is difficult to go the opposite direction and tear apart things that have been mangled together.
Sorry to be so stubborn about it but I feel that there's little benefit from sharing one application directory and I just want to make sure we think this through.

I don't have a strong opinion on the validator stuff yet but I'm inclined to have it live elsewhere from the main trinity directory.
I see your arguments on separating eth1 and eth2 but I'm not convinced at-this-time.  If you feel strongly, lets open an issue to re-visit this in a few months, but for now, I'm still somewhat strongly :-1: on separating them.

@pipermerriam alright. I'll come up with a different PR to address this then. In the process of creating #1627 I just noticed that the above proposed layout still won't work under that model though because we currently track pidfiles in trinity/<network>/<process>.pid. So right now the trinity and the trinity-beacon command would overwrite each others pidfiles (e.g. both would create a database.pid or a discovery-plugin.pid etc.) To me this is yet another signal that we are really attempting to mix concerns here but it feels like beating a dead horse at this point.
The TrinityConfig could be made aware of an app_prefix which would then be used for logfiles and pidfiles to have both the eth1 and the beacon files live side by side. Or would you suggest something else?

So right now the trinity and the trinity-beacon command would overwrite each others pidfiles (e.g. both would create a database.pid or a discovery-plugin.pid etc.) To me this is yet another signal that we are really attempting to mix concerns here but it feels like beating a dead horse at this point.

Here's how I'm thinking about it, so that the services are separate, but still under the trinity umbrella:

right now, trinity runs a single core service: the eth1 mainnet
sometime in the future trinity will run several core services: eth1 mainnet, beacon chain, etc

In that future, hard-core developers will be able to download and run the services for eth1 mainnet or beacon chain separately, to mix and match them with other services as desired. When run independently, they might default to something like ~/.local/eth1-mainnet, ~/.local/eth-beacon.
End users can always download and run trinity, which is meant to do all the coordination for them in a single local setup. When the services are run together, orchestrated by trinity, they are run in an combined data directory. trinity sets up the configuration for each service so that they are run in something like ~/.local/trinity/eth1-mainnet and ~/.local/trinity/eth-beacon. trinity also configures each service to talk to each other, across whatever ports or IPC files are necessary for the standard API communication.

@pipermerriam I think that we should create subdirectories for pidfiles and ipc files and then make the TrinityConfig aware of an app_identifier which e.g. could be beacon for the beacon node and then arrive at the following layout (assuming that the app_identifier for the eth1 node is "").
/home/cburgdorf/.local/share/trinity
├── mainnet                       <-- one mainnet directory, but sub directories
│   ├── chain
│   │   ├── full
|   |   |     └── db files
│   │   └── light
|   |         └── db files
│   ├── chain-beacon
│   │   ├── full
|   |   |     ├── beacon
│   │   │     |     └── db files
|   |   |     ├── shard-1
│   │   │     |     └── db files
|   |   |     └── shard-n
│   │   │           └── db files
│   │   └── light
|   |         ├── beacon
│   │         |     └── db files
|   |         ├── shard-1
│   │         |     └── db files
|   |         └── shard-n
│   │               └── db files
│   ├── logs
│   │   ├── trinity.log
│   │   ├── ...
│   │   ├── trinity.log.7
│   ├── logs-beacon
│   │   └── trinity.log
│   │   ├── ...
│   │   └── trinity.log.7
│   ├── ipc
│   │   ├── db.ipc
│   │   └── ...
│   ├── ipc-beacon
│   │   ├── db.ipc
│   │   └── ...
│   ├── pid
│   │   ├── database.pid
│   │   └── ...
│   ├── pid-beacon
│   │   ├── database.pid
│   │   └── ...
│   └── nodekey
|
└── ropsten
    ├── chain
    │   ├── full
    |   |     └── db files
    │   └── light
    |         └── db files
    ├── chain-beacon
    │   ├── full
    |   |     ├── beacon
    │   │     |     └── db files
    |   |     ├── shard-1
    │   │     |     └── db files
    |   |     └── shard-n
    │   │           └── db files
    │   └── light
    |         ├── beacon
    │         |     └── db files
    |         ├── shard-1
    │         |     └── db files
    |         └── shard-n
    │               └── db files
    ├── logs
    │   ├── trinity.log
    │   ├── ...
    │   ├── trinity.log.7
    ├── logs-beacon
    │   └── trinity.log
    │   ├── ...
    │   └── trinity.log.7
    ├── ipc
    │   ├── db.ipc
    │   └── ...
    ├── ipc-beacon
    │   ├── db.ipc
    │   └── ...
    ├── pid
    │   ├── database.pid
    │   └── ...
    ├── pid-beacon
    │   ├── database.pid
    │   └── ...
    └── nodekey

Because we don't want to bleed the multi app support into various parts of the application like the fix-unclean-shutdown plugin that currently globs all pidfiles in the data directory.
https://github.com/ethereum/py-evm/blob/629a4e47adb232f5143aa390a581f270e078b7bf/trinity/plugins/builtin/fix_unclean_shutdown/plugin.py#L38
So, with the proposed layout this would become:
pidfiles = tuple(trinity_config.pidfiles.glob('*.pid'))

And then trinity.pidfiles would just resolve to
<trinity_root_dir>/<data-dir>/<pidfiles-{app-identifier}>.
Or put another way, every directory data-dir is suffixed with the app-identifer and everything that is not already in a directory (currently ipc and pidfiles) moves into a directory. Does that make sense to you?


Optional dependencies are not installed

Hi! The package @napi-rs/snappy-darwin-x64 is not derived after the installation of the latest snappy. What may be the reason? Can not load bindings also appears until the latter is installed.
$ npm -v
7.11.2

Did you install with --ignore-optional flag?

Tested on my macOS 11.5, Node.js @16.7.0<EMAIL_ADDRESS>everything is fine.

The flag drops installation of optional packages, though my problem is the opposite. They are not installed at all, but I need them to be installed. Ok, I will try the newest version of npm, maybe there is a bug there.

Same issue here, we develop on macs, run in docker, the latest version is not pulling in the correct packages even when I omit --ignore-optional

@sugarandmagic Yes you can not omit --ignore-optional flag if you install dependencies in macOS and run your app in Linux(Docker). It's by design.


Hong kong translations

Our translator wasn't able to fully translate the rate limit message so I've used Google Translate for that one.

Thanks for the PR! I'll release this in the next version.

This was released in version 2.0.0

Awesome, thanks!


feat: Build Swift 5.5, 5.6 on one linux for CI

Issue #

Description of changes

New/existing dependencies impact assessment, if applicable

Conventional Commits

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

Closing.  If this work is performed in the future, it will be part of a more complete, holistically planned overhaul of CI.


Support PDF.js legacy build

PDF.js build uses moderen JavaScript and Browsers APIs.
To support older browser versions, PDF.js has a legacy build that includes pollyfils for newer APIs.
For example, when running pdfrx in Chome Version 109.0.5414.120 (Official Build) Windows 7 (same for Firefox)
I get an error:
NoSuchMethodError: method not found: 'withResolvers' (Promise.withResolvers is not a function)

Basically, we can use different version of pdf.js by setting PdfJsConfiguration.configuration before actual use (e.g. on the top of main function) of pdfrx.

@espresso3389 Thanks for that.


New Shader reload method and fix for a reload bug

This time I did two commits in the case you only want to have the fix.
I can't see how to create a pull request for a single commit. Cherry picking is up to you.

Thanks!
Attention: I renamed both reload functions and gave the older one a gl::Result as return value as well. See 3f9c38c53cc35c3fb3d6dcf8e499268b68d31a4c.
Due to commit c4a6cc4fbef14a69978b7f77f07912aa65064239 we should not have problems with your dispatch method in gl::ShaderObject anymore.
(Actually I do not know if could have avoided that extra merge commit anyways)


see which properties can be made public

due to proper typing we coul open the visibility of a lot of properties -> make them public.
see also: https://github.com/CycloneDX/cyclonedx-php-library/discussions/128

rejected for now.
the getter/setter stuff has the benefit that it enables chaining.
so this will not be implomented via V2


Please Can I Join This Organisation? 🥺🙏"

Name:
Your name here...
Why do you want to join this organization?
Explain here...
Pull request with your contribution
Replace this with a link to the pull-request with your contributions.
If you have not created a pull-request yet, please follow these instructions first.

I wan to become a member of this organization.


Issue with Executing SQL Commands with Semicolons in Init-SQL-Commands for Flight SQL Server

The option --init-sql-commands of flight_sql_server uses semicolon (';') as a delimiter to segregate the SQL command, which is then run on the server. If a SQL command, such as a connection string containing a semicolon, is used, it would be divided into distinct commands at each semicolon. This results in an incorrect operation, as a single command is erroneously divided into multiple commands.
CREATE SECRET (
    TYPE AZURE,
    CONNECTION_STRING 'DefaultEndpointsProtocol=https;AccountName=***;AccountKey=*******==;EndpointSuffix=***'
)

Proposed solution
In order to escape the semicolons in the connection string, they could be substituted with a unique character sequence (like "_semicolon_"). Subsequently, in the RUN_INIT_COMMANDS macro, this sequence can be reverted to a semicolon prior to the execution of the command.
Here is how macro could be altered:
#define RUN_INIT_COMMANDS(serverType, init_sql_commands) \
    do { \
        if (init_sql_commands != "") { \
            std::vector<std::string> tokens; \
            boost::split(tokens, init_sql_commands, boost::is_any_of(";")); \
            for (std::string &init_sql_command: tokens) { \
                if (init_sql_command.empty()) continue; \
                boost::replace_all(init_sql_command, "_semicolon_", ";"); \
                std::cout << "Running Init SQL command: " << std::endl << init_sql_command << ";" << std::endl; \
                ARROW_RETURN_NOT_OK(serverType->ExecuteSql(init_sql_command)); \
            } \
        } \
    } while (false)

And this is how the semicolons in the SQL command can be escaped:
CREATE SECRET (
    TYPE AZURE,
    CONNECTION_STRING 'DefaultEndpointsProtocol=https_semicolon_AccountName=***_semicolon_AccountKey=*******==_semicolon_EndpointSuffix=***'
)

@rohitprg - what are your thoughts about us allowing escaping the semi-colon with a \ character?  Thanks for your help.

what are your thoughts about us allowing escaping the semi-colon with a \ character?

Allowing the escaping of the semicolon with a backslash () character is a good idea, particularly because it is a common way to handle such situations.

hey @rohitprg - could you kindly see if your issue was truly resolved by the latest release: v1.3.1 ?  Thanks.

hey @rohitprg - could you kindly see if your issue was truly resolved by the latest release: v1.3.1 ? Thanks.

Please note - the fix was to NOT delimit on semi-colons which are contained within single quotes.  There is no need to escape the semi-colon(s)...

@prmoore77 -  I have verified the fix and it's functioning properly now. Thanks for the prompt fix.
It appears that in the modified code, semicolons within single quotes are not treated as command separators.


Update/dependencies

Updates
librespot
/workspaces/librespot/Cargo.toml
dependency  current  upgrade
sysinfo     0.31.4   0.33.0
thiserror   1.0.69   2.0.7

librespot-audio
/workspaces/librespot/audio/Cargo.toml
dependency  current  upgrade
thiserror   1.0.69   2.0.7

librespot-core
/workspaces/librespot/core/Cargo.toml
dependency  current  upgrade
governor    0.6.3    0.8.0
quick-xml   0.36.2   0.37.1
sysinfo     0.31.4   0.33.0
thiserror   1.0.69   2.0.7

librespot-oauth
/workspaces/librespot/oauth/Cargo.toml
dependency  current  upgrade
thiserror   1.0.69   2.0.7

librespot-connect
/workspaces/librespot/connect/Cargo.toml
dependency  current  upgrade
thiserror   1.0.69   2.0.7

librespot-playback
/workspaces/librespot/playback/Cargo.toml
dependency  current  upgrade
rodio       0.19.0   0.20.1
thiserror   1.0.69   2.0.7
zerocopy    0.7.35   0.8.13

librespot-metadata
/workspaces/librespot/metadata/Cargo.toml
dependency  current  upgrade
thiserror   1.0.69   2.0.7

librespot-discovery
/workspaces/librespot/discovery/Cargo.toml
dependency  current  upgrade
thiserror   1.0.69   2.0.7

I did not update jack and zbus as both require MSRV 1.80.0

👌


NPM is forcing me to commit changes otherwise I can't do releases, so…

… I have to check this code in even though the feature is not ready yet. I really dislike the git/npm workflow. It doesn't seem to have the flexibility that I want in a SCM.

This is a non-controversial change that actually doesn't do anything because I'm just adding testpages for things that are currently under-development. I wouldn't even be checking these in, except that npm won't allow me not-to.

@kdillon We talked about this a little bit, but for future reference: once you made this branch, you could go back to master (git checkout master) and then run the release script. You could then switch back to this branch (git checkout enforce_that_syn_honors_passed_offsets), merge or rebase with master (git merge master or git rebase master), and then continue working from there.


Add TMT proteomics template - retry automation

Same as PR#48 but trying to get the updated workflows to run the data model conversion.

Looking at a test TMT assay metadata template, there is an issue where there's a column called tissue even though that's not specified in the template dependencies: https://docs.google.com/spreadsheets/d/1Zgmc3EY1z7PJ65ecOhDrqgEO57LUpLEbfLCBMVZVHzc/edit?gid=0#gid=0.
The issue appears to be that tissue is a valid value of the attribute specimenType, leaving us with a circular graph. I'm going to leave this for now so we can merge the template. Some options to deal with it in the future:

rename the valid value to something like "tissue specimen", if there are no portal facets depending on that as annotation
set up a component-based validation rule so the tissue column is NOT required in the TMT assay manifest and tell people to ignore it
?


[Feature]: Implement PR Title Checker workflow for Conventional Commit Prefixes

Is your feature request related to a problem? Please describe.
Description:
The project would benefit from a PR title checker that ensures conformity to conventional commit prefixes. Currently, the following prefixes are considered valid:

build:
chore:
docs:
feat:
fix:
perf:
refactor:
revert:
style:
test:

Problem:
Enforcing consistent and descriptive PR titles following conventional commit prefixes helps maintain clarity and organization in the project's version history.
Describe the solution you'd like
Implement a PR title checker that validates each PR title against the specified conventional commit prefixes. This will ensure that PR titles adhere to the established guidelines.
To-Do:

[ ] Develop the PR title checker script to verify titles against the defined prefixes.
[ ] Integrate the checker into the project's CI/CD pipeline.
[ ] Define error messages or warnings for non-compliant PR titles.

Are you interested in contributing?

[X] I'd like to work on this issue

Code of Conduct

[X] I have used the search function to check if an issue already exists
[X] I agree to follow this project's Code of Conduct
[X] I am IWOC 24 contributor

Go for it


[Feature] Add detailed indicator information to the table

Search before asking

[X] I searched in the issues and found nothing similar.

Motivation
Add detailed indicator information to the table

Table storage size
Total table files
DDL last update time
Data last update time
Partition storage size
Number of partition files

Solution
No response
Anything else?
No response
Are you willing to submit a PR?

[X] I'm willing to submit a PR!

This is something in scan.


About the combination of ADAM and CODA-Prompt

Hello, I appreciate your work very much, but now I have encountered some problems in the learning process. Aper can be fine-tuned using the VPT method, so can Aper be combined with CODA-Prompt to use CODA-Prompt to fine-tune the pre-trained model in the first stage?
Looking forward to your reply

Hi, CODA-Prompt is not a tuning technique, and its core idea is also VPT. Please check the paper for more details.


Fixed humidifier typo

FYI, fixing this typo may break other projects that depend on this library.

Thanks for the PR! Breaking things is OK for now as it's a bit until this library reaches 1.0.0 and should be API-stable.


Add a DEB repository for tenv

Is your feature request related to a problem? Please describe.
By using a DEB repo, Debian/Ubuntu users can benefit from auto-update like any other package. It's simpler and easier for day-to-day operations.
Describe the solution you'd like
Create a PPA repo for tenv, and for every build, add the new version there.
Describe alternatives you've considered
N/A.
Additional context
N/A.

Good idea. I'm still working on snap in scope of https://github.com/tofuutils/tenv/issues/53, maybe deb should be before it.

Created PPA (https://launchpad.net/tenv), will add publish to it soon.

Created a basic pipeline: https://github.com/tofuutils/tenv/commit/ea91aee5020e2e39f55661559cff654719a67fec
will check how it will works

example: https://github.com/diogenes1oliveira/hashicorp-ppa/tree/master

example 2:https://github.com/mfinelli/ppa

@kvendingoldo Any progress on this?

@samuel-phan working on it. Doesn't snap work for u?

Thanks.
On Linux Mint, snap is not installed by default, so I don't use it. I'm always a bit reluctant to use tools in a sandbox, because it might block some features that needs bindings with other parts on the OS libs (eg custom under development TF providers).

Ok. I will try to deliver deb repo this week


Change partner image to certsuite-sample-workload

Creates a new image certsuite-sample-workload and also pushes the old partner image as well.

https://github.com/redhat-best-practices-for-k8s/certsuite/pull/2321


Fix eslint warnings

Describe the bug
Frontend code has eslint warnings

To Reproduce
Steps to reproduce the behavior:

After cloning the repository
Install packages npm i
Start the server npm start
Observe eslint warnings in the log

Expected behavior
All eslint warnings must be fixed

Hey! I think I can work on this.
Would you be willing to assign it to me under GSSoc'21?

Sure @A-HK, please go ahead :)

Hey @chetan-rns , does this log look fine to you?

If it does, let me know if I should make a PR !

Hey @chetan-rns @avinashkranjan , made a PR for the same. Please check if everything is satisfactory whenever you're free!


minor LDAP fixes

usermanager: disable username and descr field for ldap users
usermanager: hide password field for ldap users
import ldap user: fixed a bug on Active Directory where the name attribute isn't handled correctly
import ldap user: sort entries by name
import ldap user: add scrollbars on IE, Firefox & Opera
auth servers: move bind credentials up on the screen

@chrisch1974 great stuff, thank you!!


Error on windows with python 3.7.3

Hi,
i'm trying to run your module on windows with python 3.7.3 but i always get that error :
File "C:\Users\dk6166\AppData\Local\Programs\Python\Python37-32\lib\subprocess.py", line 1178, in _execute_child startupinfo)
FileNotFoundError: [WinError 2] The system cannot find the file specified
this is my code :

Can you help me (i renamed my wifi interface by 'wifi')
thank you

I dont believe wifi is the correct interface for windows, but these are See here. Need to determine how to modify this method, since it still calls iwlist  which is linux specific

Hi @Olimelan , as @dkowalsky7 stated, this will not work for Windows. If you found a workaround or modification, please open a PR! I'd love to see this become available for OS outside of Ubuntu.


Unabstracted variables in indices of inductive types in mutual block

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Check that your issue is not already filed.
Reduce the issue to a minimal, self-contained, reproducible test case. Avoid dependencies to mathlib4 or std4.

Description
In certain cases, when elaborating inductive types, Lean fails to abstract some loose free variables in the signature of inductive types (more particularly on indices) in a mutual block, leading to an error.
Context
Discovered initially here. The issue can be avoided by using variable
Steps to Reproduce
mutual

inductive R (F: α → α → Prop) (a : α) : α → Prop where
| ind : ∀ (f: Nat → α) b, (∀ n, And₂ F a b f n) → R F a b

inductive And₂ (F: α → α → Prop) (a : α) : α → (Nat → α) → Nat → Prop where
  | mk (b : α) (f : Nat → α) (n : Nat): R F a (f n) → F (f n) b → And₂ F a b f n

end

Expected behavior: No error
Actual behavior: Error (kernel) declaration has free variables 'And₂'
Versions
4.5.0
Web Browser
Additional Information
The signature type of And₂ here is: {α : Sort u_1} → (α → α → Prop) → α → _uniq.21 → (Nat → _uniq.21) → Nat → Prop.
The issue can be circumvented by using variable, the following code works:
variable {α : Type _}

mutual

inductive R (F: α → α → Prop) (a : α) : α → Prop where
  | base : R F a a
  | ind : ∀ (f: Nat → α) b, (∀ n, And₂ F a b f n) → R F a b

inductive And₂ (F: α → α → Prop) (a : α) : α → (Nat → α) → Nat → Prop where
  | mk (b : α) (f : Nat → α) (n : Nat): R F a (f n) → F (f n) b → And₂ F a b f n

end

Impact
Add :+1: to issues you consider important. If others are impacted by this issue, please ask them to add :+1: to it.

Further minimization:
mutual
inductive A (α : Type) : α → Type where

inductive B (α : Type) : α → Type where
end
/-unknown free variable '_uniq.7'-/

I believe I found another instance of this problem that still reproduces in 4.8.0-rc1 (and the web compiler, as of writing):
structure Salg (n: Nat) where
  D: Type

mutual
inductive Ins (salg: Salg n) : salg.D → Prop
inductive Out (salg: Salg n) : salg.D → Prop
end

The error I'm getting is (kernel) declaration has free variables 'Out'.

I'll take a look, thanks for reporting.

It appears the that issue comes from unification/metavariables. When the term is elaborated, there is still an mvar that needs to be elaborated (the n argument of Salg in salg.D. I'm guessing the metavar is resolved before that step, but is not correctly instantiated at that point. Because of this, the instantiation done here doesn't replace the expected free variables, since they do not appear in the term before the instantiation.
At first glance, it seems like replacing
        let type  := r.type |>.abstract r.params |>.instantiateRev params

with
        let type ← instantiateMVars r.type
        let type  := type |>.abstract r.params |>.instantiateRev params

Seems to resolve the issue, but I am anything but skilled when it comes to working with unification, and fear this might have some unexpected consequences. A second opinion would be greatly appreciated.


Inform client of invalid events

Is there a way to respond to the client when the socket emits an event that isn't picked up by an event listener? That way you can inform the client rather than them just having a timeout. For example:
Server:
socket.on('test', (data, respond) => {
    respond(null, 'success');
});
socket.on('unansweredMessage', (respond) => {
    respond(new Error('Unknown event request.'));
});

Client:
socket.emit('test2', {}, (err) => {
    console.log(err); // ERROR: Unknown event request.
});

No there is not a way to inform a client if it is not received by server. Timeout is the only thing you can do to check if request is received and acknowledged corresponding ack is received or not.

That's unfortunate. Thanks for the response anyway.

@FallingSnow do you mean a default catch-all event (so the server receives an event which has no matching listeners attached)?
If so, it's not supported at the moment but feel free to share more details about your use case and why you think it might be useful and we can consider it.

I intend to write a websocket api for a service I'm developing. The ability to notify clients when they have made an unknown request would not only help with my development but also developers that will use that api in the future.
My primary use case is for requests for events that require authentication. For security reasons I don't attach certain event listeners to a socket until it has been authenticated. If there was an api to catch unhandled events I could compare the event against my list of handlers for authorized events and notify clients that they need to authenticate before calling this event or that this event doesn't exist at all.
Lastly I think it would add a better user experience. A timeout error suggests that any number of errors could have occurred between the client and the server (when I think timeout I think connection loss personally). With a catch-all you can provide the client with a more specific error.
Rant over. Thanks.


EXEC SQL WHENEVER are compilation directives (not statement) : not concerned by unreachable code

Development environment used

Editor Platform

[x] Visual Studio Code
[ ] CodeReady Workspaces
[ ] Eclipse Che
[ ] Standlone Theia

Platform Version: VS Code 1.46.1 / ZOE 1.0.0
Operating System: Windows 10 1607
Java Version: 1.8
Logs attached: no

Problem Description
Extract from https://github.com/IBM/zopeneditor-about/issues/18#issuecomment-643372231
In some cases the "EXEC SQL WHENEVER" directives can be considered as not reachable, but as they are not instructions, they are compilation directives, they should not appear as non-reachable code.

This bug was fixed in version 4.3.0, thank you for your patience while we worked on a fix.


Get enum strings where available

Add fetchLatestMetadata=true to all requests.

Parse the resulting metadata looking for enum options in PB and JSON responses.

Add enum_options member to ArchiveData. Populate an enum_strings array for enum string of each value, if available.

Add enum_string member to ArchiveEvent.

Please could you have a go with it and see if presentation of the information is useful?

I forgot to mention: thank you for this change, this is a significant improvement.

This all seems to work well now. So let's consider the API:

enum_options for the dict
enum_strings for the string values
empty strings if you ask for strings when it's not an enum

Cothread doesn't do anything for you except add enums (a list of strings) if you request FORMAT_CTRL. So this is fine in comparison. My only question is that last bullet point, I'm not sure how user-friendly it would prove. How would you determine if your data was an enum or not?

This all seems to work well now. So let's consider the API:
* `enum_options` for the dict

* `enum_strings` for the string values

* empty strings if you ask for strings when it's not an enum

Cothread doesn't do anything for you except add enums (a list of strings) if you request FORMAT_CTRL. So this is fine in comparison. My only question is that last bullet point, I'm not sure how user-friendly it would prove. How would you determine if your data was an enum or not?

Some alternatives:

Following Cothread, only try to get the enum values if requested - i.e. add an argument to get_values / get_event_at which causes the fetchLatestMetadata to be appended. But following this through would then probably want a subclass of ArchiveData with the enum members so that they are only present if requested.
Return None from enum_strings if enum_options is empty
Raise an exception like NotAnEnum instead of returning empty strings (seems a bit mean)
add a member giving the data type or perhaps true/false for "this is an enum"

Return None from enum_strings if enum_options is empty

This is my favourite.

I tired that out. It was easier to implement than expected. I also added has_enum_strings as a property since I have to do the check anyway.

Looks good to me.

OK, thanks. I'll do some rebasing and review the docs, then merge.


Clarification on "clear" instead of "uncheck" or "unselect"

This page currently states to use "clear" instead of "uncheck" "unselect": https://docs.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/u/uncheck-unmark-unselect
Can someone clarify why "clear" is the preferred term for unselecting check boxes? If "select" is okay, then why not "unselect": https://docs.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/c/check-check-box-check-mark

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

ID: 7909593b-721f-41a7-dab7-7231373fdd7d
Version Independent ID: d08babbe-edfc-ad4d-3714-badfa750bc96
Content: uncheck, unmark, unselect - Microsoft Style Guide
Content Source: styleguide/a-z-word-list-term-collections/u/uncheck-unmark-unselect.md
Product: non-product-specific
GitHub Login: @pallep
Microsoft Alias: pallep

I believe 'clear' is a better word to use than 'select' with 'un' in front of it.
I know what I describe above may sound nuts, but hear me out.
To people who don't speak English as a second language, using different words to mean opposites, in a Boolean fashion, can be confusing. I prefer to use 'clear' from an accessibility perspective: Learning disorders like dyslexia hinder some people from reading words, which is why I personally prefer to keep 'clear' and 'select'.
Just my two cents on this, @densha.


Rename go module to github.com/nooncall/owls/go

LGTM

nit: 可能会造成makefile里的命令失效

Oops~ I fixed these paths in Makefile and yaml configs.


Is there a standalone version?

For using outside firefox/browsers in general, like a CLI or maybe IDE extensions (brackets, atom, vscode).
If not, any guidelines for me to do so?

Hi Bernardo,
Sorry there’s no standalone or integration version. The way web development has changed over the last decade, I don’t think there’s really much call for tools like this anymore, when there are things like Node modules that can do a similar job within an integrated environment. And this is the main reason why I haven’t really kept the extension updated.
If you want to convert or cherry-pick the code for your own purposes, please be my guest.
cheers
James

On 21 Nov 2017, at 18:01, Bernardo A. Dal Corno<EMAIL_ADDRESS>wrote:
For using outside firefox/browsers in general, like a CLI or maybe IDE extensions (brackets, atom, vscode).
If not, any guidelines for me to do so?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/brothercake/dustmeselectors/issues/1, or mute the thread https://github.com/notifications/unsubscribe-auth/ACJOwVRlLX9irSdfS8s9HCgxehns13Sjks5s4w_tgaJpZM4QmQZP.

Thanks for the reply James!
I've kept digging and you're right, now there is a module in npm for that, it's purify-css. So no job needed here.
Thanks anyway! Cheers


feat: enable write variable width data in 2.1

This PR adds a Compute_Stat trait to DataBlock, to separate the statistics computation and statistics inquiry.
This PR also modifies do_flush and encode_miniblock in PrimitiveStructuralEncoder to enable write variable width data in 2.1(PrimitiveStructuralEncoder)

Codecov Report
Attention: Patch coverage is 86.55914% with 25 lines in your changes missing coverage. Please review.

Project coverage is 77.16%. Comparing base (b7663fb) to head (f987ee7).
Report is 1 commits behind head on main.

Files with missing lines
Patch %
Lines

rust/lance-encoding/src/statistics.rs
84.13%
22 Missing and 1 partial :warning:

.../lance-encoding/src/encodings/logical/primitive.rs
94.87%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3090      +/-   ##
==========================================
- Coverage   77.34%   77.16%   -0.18%
==========================================
  Files         240      240
  Lines       79432    79732     +300
  Branches    79432    79732     +300
==========================================
+ Hits        61433    61522      +89
- Misses      14830    15034     +204
- Partials     3169     3176       +7

Flag
Coverage Δ

unittests
77.16% <86.55%> (-0.18%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Disable scale for grid when scalingObjects: true

I have following config
view: {
        panEnabled: true,
        zoomEnabled: true,
        scalingObjects: true,
        fit: true,
        layoutHandler: new GridLayout({ grid: 20 }),
        grid: {
            visible: true,
        },
    },

And <g class="v-background-viewport"... scaling along with other objects with grid on background

When i turn scalingObjects option to false everything back to normal, but my task is scale nodes and edges on zoom and leave background grid fullscreen.

Hi @justfry,
Thank you very much for your report.
Fixed grid scaling when scalingObjects: true is specified.
Please check it out v0.3.7.

@dash14 Oh my god it works! Thank you!


update .../pods/index.md

change "clean" to "cleaning"

This change is

I think the existing sentence is correct and does not require any changes.

“clean” is a verb, while "cleaning" is a noun. That's why I want to change it.

I still think the existing wording is correct. The full sentence is essentially: "Pod is exposed as a primitive in order to facilitate clean composition of Kubelet-level functionality with cluster-level functionality".

“clean” is a verb, while "cleaning" is a noun. That's why I want to change it.

In this particular case "clean" is an adjective and "composition" is the noun (clean is describing the composition).

You are right. I close it. Thank you.


Dojo list does not scroll

The dojo list loads for a while and then it does not scroll to India:
https://zen.coderdojo.com/?list=true#India
I would like, once the list is successfully loaded, that it scrolls down to India.

It seems that the anchor is applied upon click, but not taken into consideration while loading the page.
Definitely a bug, thanks @niccokunzmann :+1:


A batch of updates to get to xgboost 2.0.3

builds with xgboost v2.0.3
expose cuda support as a feature
some additional OS X (openmp) compatibility for homebrew
move upstream to dmlc/xgboost
fix cargo dependencies for git submodules
update cargo dependencies
update DMatrix uri loading format for 2.0 compat
fix cargo clippy lints

static lifetimes are no longer required

fix dmatrix slicing out of bounds segfault
cargo fmt (rustfmt.toml to minimize changes where possible)

Needs detailed review:

From csr does not pass tests, but from csc is easier for me to reason about:

https://github.com/davechallis/rust-xgboost/compare/master...postgresml:rust-xgboost:master#diff-5395154ef0eed4cb8417ab3dfac078a8e79d26947d6967aa0800ad0460d81b1aR67

@montanalow Thanks for this, looks good on quick read through! I'll spend a bit of time reviewing in detail shortly (just dealing with a bit of a backlog after xmas...).

Code changes mostly look good I think.
I'm having some trouble building xgboost-sys after the changes though, so still investigating that. I get the errors:
error[E0412]: cannot find type `_Tp` in this scope
   --> /Users/dsc/src/rust-xgboost/xgboost-sys/target/debug/build/xgboost-sys-95c0101c1ac52cb0/out/bindings.rs:452:27
    |
452 |     pub static std_value: _Tp;
    |                           ^^^ not found in this scope

For more information about this error, try `rustc --explain E0412`.
error: could not compile `xgboost-sys` (lib) due to previous error

I'll carry on trying to find the cause though, possible I'm using an outdated llvm install.

This one took me a bit, but I think it's fixed by https://github.com/davechallis/rust-xgboost/pull/21/commits/0307a92960290bbe74b69cdeff2dd9090201f346


EUMETSAT cloud mask product

Apparently Eumesat Cloud Mask product has an hour's delay. How do you work around that delay in your workflow?
Thank you very much!

We have found that the other images are also a bit delayed, can be an hour. What latency have you found for the other images?
We solve this in the ML side of things. When training the model we only give the model satellite data that is 1 hour before the initialisation time. We've also added a bit of drop out, incase its slightly more or less than 1 hour
Does this make sense?

High Rate SEVIRI has a latency of 15 minutes and Cloud Mask about one hour.
Your procedure makes complete sense.
Thank you.


Add diff and trapz(y, x) functions

Looks good!

I think we should change the dx parameter to trapz to be double instead of value_type ... it's a bit nonsensical there (also I checked and numpy seems to always convert the result to double so it should be fine).


create logs in temp directory

Creating logs in installation dependent directory __file__/../.. may cause problems due to missing write permissions. Using pywsdp library in QGIS plugin on Windows leads to error message below:
Unable to create C:\Users\logs

This draft PR creates logs in temporary directory instead of installation dependent path.
Tasks before merging:

[x] user should have possibility to defined own log directory (as constructor's argument / method / or env variable)

@lindakladivova Any progress?

@lindakladivova Any progress?

I think that this PR already fixes the issue in the way that it creates the default log directory in the Temporary directory.
There is actually the @log_adresar.setter but the problem was that for some reason Sphinx only read the documentation for the @property method, not the @property.setter one at all (please see https://stackoverflow.com/questions/71713284/types-of-setter-arguments-not-showing-in-sphinx-documentation).
I have added the logger info message to the setter and extended the documentation.

Btw WSDP test services are in maintenance till the 28th so pytest fails (https://www.cuzk.cz/Aplikace-DP-do-KN/Aplikace-DP-do-KN/Archiv-DP.aspx).

@lindakladivova I tested PR in Python 3.11. There is a warning which should be nice to avoid before merging:
warning:/usr/lib/python3.11/tempfile.py:1034: ResourceWarning: Implicitly cleaning up
              _warnings.warn(warn_message, ResourceWarning)

             traceback: File "/home/martin/git/ctu-geoforall-lab/qgis-vfk-plugin/../qgis-vfk-plugin/mainApp.py", line 259, in runDownloadingPosidents
              ctios = CtiOS([
              File "/home/martin/git/ctu-geoforall-lab/qgis-vfk-plugin/../qgis-vfk-plugin/pywsdp/modules/CtiOS/__init__.py", line 50, in __init__
              super().__init__(creds, trial=trial)
              File "/home/martin/git/ctu-geoforall-lab/qgis-vfk-plugin/../qgis-vfk-plugin/pywsdp/base/__init__.py", line 42, in __init__
              self._log_adresar = self._set_default_log_dir()
              File "/home/martin/git/ctu-geoforall-lab/qgis-vfk-plugin/../qgis-vfk-plugin/pywsdp/base/__init__.py", line 105, in _set_default_log_dir
              log_dir = tempfile.TemporaryDirectory().name
              File "/usr/lib/python3.11/weakref.py", line 590, in __call__
              return info.func(*info.args, **(info.kwargs or {}))
              File "/usr/lib/python3.11/tempfile.py", line 1034, in _cleanup
              _warnings.warn(warn_message, ResourceWarning)

Probably the best way how to avoid this is not to use tempfile.TemporaryDirectory in case we do not want to delete the dir after the process is completed. I have changed the way how the log_dir is created. It takes the temp directory and inside it, it creates a new directory based on the service name (e.g. ctiOS). So, in our case the resulting path to log file will be e.g. /tmp/ctiOS/17_58_51_09_08_2023.log .

@lindakladivova I tested PR and it's ready to be merged. Please create release-2.2 branch and release 2.2.0.


Better match Cocoa semantics for API

Current dependencies on/for this PR:

main

PR #6   👈

This stack of pull requests is managed by Graphite.


[c2][encoder] Pass down parameter of max B frames

Pass parameter of max B frames to onevpl.

Improper Commit Message
Tracked on not found in commit message,
make sure Tracked-On: Jira-ticket  is present.


[salesforce] Provide as a salesforce app

tracked by https://ag-grid.atlassian.net/browse/AG-98

Hi,
Thank you for raising this issue for us, at this moment we are reviewing how we process Feature Requests/questions that come through from GitHub.
As I am sure you are aware, we offer two products:
ag-Grid - this is entirely free to use in line with our MIT license
ag-Grid Enterprise - our commercial version which funds the development of both versions.
We currently have a very full pipeline of work which can be viewed here: https://www.ag-grid.com/ag-grid-pipeline/
This will be our priority for the coming months and as a result, we don’t have capacity to take feature requests/questions from GitHub, but you might find that yours has already been raised in our pipeline.
We will do a periodic review of GitHub issues for any bugs raised and these can also be tracked on our pipeline page.
Thanks for your understanding.
ag-Grid Team.

Hi @makinggoodsoftware ,

@sagarpomal did you find any useful library or solution for grids/datatables in lwc?

@sjurgis  No, we could not find any other solution related to datatable in lwc with features that ag-grid has. We tried our best to make ag-grid work in lwc by contacting ag-grid and also working with Salesforce. Based on our discussion, ag-grid has to make a lot of breaking changes, and they can't take this on priority because of low volume on Salesforce.
We ended up using ag-grid with Lightning Container based on our use case and features we wanted and validated our approach with Salesforce based on current limitations.
We could have tried to modify the lwc datatable; however, it is yet to be made open source under lwc base components due to its complexity.

@sagarpomal yes I've got same message from lwc team - too much deps on internal API's and components to open source just yet.
I've tried ag-gird, handsontable, anygrids so far and none of them work.

@sjurgis Yes, many of the feature rich third party libraries are not working.


Twig 3.0 support

Hello,
Thanks for your bundle, great work !
Twig have a new version and change it's way to deal with extensions:

Is it possible to change your src\Twig\HashidsExtension.php by this to make it works ? :
<?php

declare(strict_types = 1);

namespace Roukmoute\HashidsBundle\Twig;

use Roukmoute\HashidsBundle\Hashids;
use Twig\Extension\AbstractExtension;
use Twig\TwigFilter;

class HashidsExtension extends AbstractExtension
{
    /**
     * @var Hashids
     */
    private $hashids;

    public function __construct(Hashids $hashids)
    {
        $this->hashids = $hashids;
    }

    public function getFilters(): array
    {
        return [
            new TwigFilter('hashids_encode', [$this, 'encode']),
            new TwigFilter('hashids_decode', [$this, 'decode']),
        ];
    }

    public function encode($number): string
    {
        return $this->hashids->encode($number);
    }

    public function decode($hash): array
    {
        return $this->hashids->decode($hash);
    }
}

(regarding to https://symfony.com/doc/4.0/templating/twig_extension.html it's supported from SF4.0 so it's should be fine for everyone)
Thanks in advance :)

Hey thanks for your support.
You are right, I will fix that quickly or do not hesitate to create a P.R. of course!


feat: Implement trace_transaction

Provides transaction processing of type trace for the specified transaction. Use this API to improve smart contract performance by analyzing its internal transactions and execution steps. You can use this information to identify bottlenecks and optimize the contract for better performance.
Parameters :
transaction hash: [Required] The transaction hash
Returns :
A list of traces in the order called by the transaction.
Request :
curl https://mainnet.infura.io/v3/YOUR-API-KEY \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc": "2.0", "method": "trace_transaction","params": ["0x4c253746668dca6ac3f7b9bc18248b558a95b5fc881d140872c2dff984d344a7"],"id": 1}'

Response :
{
    "jsonrpc": "2.0",
    "result": [
      {
        "action": {
          "callType": "call",
          "from": "0xfe3b557e8fb62b89f4916b721be55ceb828dbd73",
          "gas": "0xffad82",
          "input": "0x0000000000000000000000000000000000000999",
          "to": "0x0020000000000000000000000000000000000000",
          "value": "0x0"
        },
        "blockHash": "0x71512d31e18f828cef069a87bc2c7514a8ca334f9ee72625efdf5cc2d43768dd",
        "blockNumber": 6,
        "result": {
          "gasUsed": "0x7536",
          "output": "0x"
        },
        "subtraces": 1,
        "traceAddress": [],
        "transactionHash": "0x91eeabc671e2dd2b1c8ddebb46ba59e8cb3e7d189f80bcc868a9787728c6e59e",
        "transactionPosition": 0,
        "type": "call"
      },
}

DO NOT FORGET TO UPDATE methodsStatus.md (set this method as finished)
/rosettanet/docs/methodsStatus.md
methodsStatus.md

.

@Boreas09 Is this open?

The method trace_transaction is not available in Infura.


Implement static support for the null check operator.

See this section of the feature spec.

Landed in https://dart-review.googlesource.com/c/sdk/+/118380

Inference handled in https://dart-review.googlesource.com/c/sdk/+/130705

We still need to figure out whether the type context should be nullable (like for lhs of ??).

@johnniwinther I think we may take the following comment for the answer: https://github.com/dart-lang/sdk/issues/39694#issuecomment-562673214.

Following https://github.com/dart-lang/sdk/issues/39694#issuecomment-562673214 the proposed fix is to make the context nullable: https://dart-review.googlesource.com/c/sdk/+/134330


feat: add martech plugin to connect to analytics and target

This PR adds integration with Target, Launch & ACDL via the martech library. It also moves the Analytics instrumentation to the martech library, and creates a more generic loader to combine the GTM and WebSDK logic and isolate it from the main scripts.js file.
At a high level:

lib-analytics.js is renamed to lib-martech-loaded.js

inline scripts are changed to direct execution to avoid HTML parsing
consent is updated to v2 API
conversion, GTM, alloy and click trackings are all moved to the martech loader
launch and analytics envs will be mapped as follows:

*.petwatch.com => prod
*.live / *.page urls => stage
everything else => dev

a new trackAnalyticsEvent method is exported to specifically track events in Analytics instead of GTM
updates alloy.js to v2.21.1

Adobe martech library is add as plugins/martech
head.html gets new preload/preconnect links for resources immediately imported, so we don't have to wait for scripts.js to be parsed.

Test URLs:

Before: https://main--24petwatch--hlxsites.hlx.live/
After: https://martech-lib--24petwatch--hlxsites.hlx.live/

@fe-lix- @ekremney @bohnertchris Since I did quite some heavy lib-analytics.js refactoring for this, if you know the various analytics events they were tracking before, could you perform a quick sanity check to make sure we didn't lose anything along the way?

@ramboz it has been almost 1 year since the custom analytics events were implemented for this project. I am afraid I cannot recall all the details. The most important events were tracked by GA4 via trackGTMEvent


incorrect singular values from svdl?

SVDL returns radically different answers than SVD for the case generated by the test case, below. assuming that the two algorithms are equivalent.
using IterativeSolvers
M = zeros(110,22);
M[:,1] = ones(110); M[:,2] = repeat(1:11,outer=10);
offset = 0; indx = 1:11;
for i = 3:2:21
	M[offset+indx,i] = ones(11);
	M[offset+indx,i+1] = indx;
	offset += 11;
end
svd(M)[2]
svdl(M)[1]
svdl(M,22)[1]
svdl(sparse(M),22)[1]

The algorithms aren't equivalent. svd isn't iterative and is more stable than svdl. I think svdl doesn't work well with many repeated singular values. I cannot really judge whether the method is unstable or has a bug.


Added ShuffleWithinSegments

Shuffling tokens within segments.

The token sequence is split into segments of the same label; for each segment, a decision is made randomly: to shuffle it or not.
In case of a positive decision, the tokens within each segment are shuffled.

The source: https://arxiv.org/abs/2010.11683

SuspectingParaphraser doesn't pass the tests. What should I do about it.

Hi @Erlemar
I was assigned as one of your reviewers.
Thanks for this contribution!
I this that this transformation is very useful and clear.
Here's my general review:
Correctness: All checks have failed, please fix this by looking at other PRs
Interface: I think you have chosen the correct interface(s).
Applicable Tasks & Keywords: I think you have chosen the relevant task. Please add keywords as explained here
Specificity: The change is general.
Novelty: This transformation is not yet implemented in NL-Augmenter.
Adding New Libraries: No new libraries appear to be added, and there is no requirements.txt file.
Description: The README is clear and explains what the transformation is aiming to do.
Data and code source: References clearly indicated in README
Test Cases: 6 test cases have been added.
Evaluating Robustness: No robustness evaluation has been performed.
Languages other than English: Yes, but it is required as input a TAG sequence

Hello @marco-digio
Thank you for your review!
Correctness:
The problem is that tests for my transformation (ShuffleWithinSegments) pass successfully, tests fail for a different transformation (SuspectingParaphraser). I'm not sure what should I do about it.
Applicable Tasks & Keywords: I have added the keywords, but I'm not sure that I have selected all of them correctly. Here is my reasoning:
"lexical" - the transformation substitutes different words.
"word-order" -  the order of the words is changed.
"rule-based" - the transformation uses heuristics.
"unnaturally-written", "unnatural-sounding" - I'm not sure about these keywords: this transformation randomly shuffles words within separate entities, as a result, the order of the words could be unnatural. This perturbed order could sound unnatural too. This is why I chose both these keywords.
"possible-meaning-preserving" - due to the changed word order, the meaning of the sentence could change.
"high-precision" - the transformation generates what it intends to generate.
"low-coverage" - the transformation works only for TAG sequences.
"low-generations" - The transformation generates few outputs for a single input.
Evaluating Robustness: I have added the results of the evaluation check.

I have pushed the changes from https://github.com/GEM-benchmark/NL-Augmenter/pull/288 now the tests should pass.

Hi @samsontmr @marco-digio the tests have passsed successfully.

Thanks @Erlemar for the hard work and everyone for their comments.


connect to azure sql

Does anyone know the correct way to configure azure sql connection? I've spent a long time trying to find any examples of this and many variations of:
mssql: {
client: 'mssql',
connection: {
host: Env.get('DB_HOST', 'localhost'),
port: Env.get('DB_PORT', ''),
user: Env.get('DB_USER', 'root'),
password: Env.get('DB_PASSWORD', ''),
database: Env.get('DB_DATABASE', 'adonis')
},
options: {
port: Env.get('DB_PORT', '1433'),
database : Env.get('DB_DATABASE', 'adonis'),
encrypt: Env.get('DB_ENCRYPT', true),
//debug: Env.get('DEBUG', true)
},
debug: Env.get('DEBUG', true)
}
trying to run the migrations as a test of connectivity.. It's a new project, mssql 4.1.0 is installed and Adonis 4.0.28. The error I get is:
Users-MacBook-Pro-2:apiprojectadon4 mmarino$ adonis migration:run
[ { sql: 'select object_id from sys.tables where object_id = object_id(?)',
output: [Function: output],
bindings: [ '[adonis_schema]' ] } ]
TypeError: (connection.tx_ || connection).request is not a function
at /Users/mmarino/development/apiprojectAdon4/node_modules/knex/lib/dialects/mssql/index.js:213:48
at Client_MSSQL._query (/Users/mmarino/development/apiprojectAdon4/node_modules/knex/lib/dialects/mssql/index.js:208:12)
at Client_MSSQL.query (/Users/mmarino/development/apiprojectAdon4/node_modules/knex/lib/client.js:211:17)
at Runner. (/Users/mmarino/development/apiprojectAdon4/node_modules/knex/lib/runner.js:149:36)
From previous event:
at Runner.queryArray (/Users/mmarino/development/apiprojectAdon4/node_modules/knex/lib/runner.js:199:40)
at /Users/mmarino/development/apiprojectAdon4/node_modules/knex/lib/runner.js:59:23
at runCallback (timers.js:789:20)
at tryOnImmediate (timers.js:751:5)
From previous event:
at Runner.run (/Users/mmarino/development/apiprojectAdon4/node_modules/knex/lib/runner.js:47:31)
at SchemaBuilder.Target.then (/Users/mmarino/development/apiprojectAdon4/node_modules/knex/lib/interface.js:35:43)
at process._tickCallback (internal/process/next_tick.js:188:7)
at Function.Module.runMain (module.js:678:11)
at startup (bootstrap_node.js:187:16)
at bootstrap_node.js:608:3

How about trying this config? https://github.com/tgriesser/knex/issues/1480#issuecomment-231009712

that's what i was looking at when I created the config in database.js of adonis. I even bypassed the .env file and entered this in directly. Nothing seems to work..

Can u connect to the DB without using Adonis or knex? Let's say connecting it from command line?

yes, I was using sails with sequelize earlier that also uses mssql driver. I've gotten a bit farther, I'm getting:
Knex:warning - Connection Error: ConnectionError: Server requires encryption, set 'encrypt' config option to true.
Knex:warning - Connection Error: ConnectionError: Server requires encryption, set 'encrypt' config option to true.
I've set this in multiple places to try to find out exactly where it's expecting this. in sequalize, I had to add an options section to my model in order to get it to work along with the connection config..

I finally got it to work. Don't know why it wouldn't work earlier..
mssql: {
    client: 'mssql',
    connection: {
      host: Env.get('DB_HOST', 'localhost'), // azure database
      user: Env.get('DB_USER', 'root'), // azure user
      password: Env.get('DB_PASSWORD', ''), //azure password
      database: Env.get('DB_DATABASE', 'adonis'), //azure database
      options: {
        encrypt: Env.get('DB_ENCRYPT', true)   // use this for Azure database encryption
      }
    }
  }


Docs/so-133/dfd

moved DFD to main readme

This is cool! Couple of suggestions:

Remove date from image
Change v1.0.0 to the prism major or minor version? Otherwise kind of confusing. E.g. v3. Or remove version altogether
Add a link below it for somebody to edit it? E.g. if there is an inconsistency now or in the future that somebody notices, how are they going to put in a PR to update it?

Orr not lol. At least add a link somewhere so that folks can edit that diagram? Re-creating it would be a bummer.

Orr not lol. At least add a link somewhere so that folks can edit that diagram? Re-creating it would be a bummer.

:D I think Phil didn't notice your comments, I created another PR with the link to original


[BEAM-4073] Expand ExecutableGraph, and add a Portable Representation

This change adds additional methods required to execute a Pipeline to
ExecutableGraph, a Portable implementation of the interface, and expands
the implementation of QueryablePipeline to be able to fulfill that interface.

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand:

[ ] What the pull request does
[ ] Why it does it
[ ] How it does it
[ ] Why this approach

[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Run ./gradlew build to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @huygaa11


怎么删除知识库

做测试只能新建知识库，重新测试只能重建知识库。旧知识库怎么删除

没找到对应功能，knext语句也没找到对应功能

Thank you for your feedback. We will support the deletion of the knowledge base in the next version

Since dozerdb (a community version of Neo4j) does not deleting graph databases. We can not implement the knowledge base deletion feature for the moment.

做测试只能新建知识库，重新测试只能重建知识库。旧知识库怎么删除
 没找到对应功能，knext语句也没找到对应功能

knowledge base deletion has been supported in kag v0.5.1 : https://github.com/OpenSPG/KAG/releases/tag/v0.5.1


FIX issue #35873 ps_imageslider.php

Questions
Answers

Description?
Test if DOMElement exist before create sortable list

Type?
bug fix

BC breaks?
no

Deprecations?
no

Fixed ticket?
Fixes https://github.com/PrestaShop/PrestaShop/issues/35873

Sponsor company

How to test?
Indicate how to verify that this change works as expected.

Can't be tested because blocked by https://github.com/PrestaShop/PrestaShop/issues/35704


fix: maven cache in ci.yml

Summary
SUMMARY_GOES_HERE
Full changelog

[Implement ...]
[Add related tests]
...

Issues resolved
Fix #XXX

Codecov Report

Merging #26 (724f1a6) into master (5695378) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #26   +/-   ##
=========================================
  Coverage     69.95%   69.95%
  Complexity      128      128
=========================================
  Files            13       13
  Lines           416      416
  Branches          1        1
=========================================
  Hits            291      291
  Misses          113      113
  Partials         12       12

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


select2 is not a function

I keep getting this error so how can i fix it

This appears to be more of a usage question than a bug report or common feature request.  As we continue to keep the Select2 issue tracker geared towards these two areas, bug reports and common feature requests, we are redirecting usage questions to other communities such as the mailing list, IRC, or Stack Overflow.


[BEAM-22] Give root transforms step names

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[x] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[x] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[x] Replace "<Jira issue #>" in the title with the actual Jira issue
number, if there is one.
[x] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

Fix a bug where steps would only be given step names if they were a
non-root node.
Use the ConsumerTrackingPipelineVisitor in the
InProcessEvaluationContext test to handle runner-expanded transforms

R: @bjchambers

LGTM


Deletes all sites if no argument specified for 'passgo remove'.

This is a pretty simple but nice feature that I think could come to use. It might not be used very often, or at all by some users - but if you need the functionality to delete all your sites it would be extremely tedious without this feature.
It's pretty simple. If passing passgo remove without any arguments the user will get a confirmation prompt and then all sites will be deleted.

This is very "foot shoot", the type of software I'm very against writing.


dapr.io/app-health-check-path description is not correct for version 1.11

Describe the issue
The Reference->Arguments and Annotations page needs to be updated for changes made in the latest 1.11 release for the "dapr.io/app-health-check-path" description in the table.
It looks like the default value for the argument was changed from "/health" to "/healthz" between versions 1.10 and 1.11.
URL of the docs
https://docs.dapr.io/reference/arguments-annotations-overview/
Expected content
The last line of the description should state:  "Default is /healthz."
Screenshots

@xendren would you like to submit a PR that fixes this?


time-picker  component enhancements

This function solves the problem (这个功能解决的问题)
component enhancements
Expected API (期望的 API)
Any time range can be selected

Yes, I also think it's a complicated process, but I've consulted various UI libraries, and the multiple features of dates make it more popular

Yes, I also think it's a complicated process, but I've consulted various UI libraries, and the multiple features of dates make it more popular

I know, we will do it after features with higher priority is implemented.


No search results showing up

Search results are not showing up. It worked fine a few days back.

Seems like it works again now.

Looks like Twitch might've had a service disruption. Thanks for the report!


Added ihsaan.glitch.me

This PR is:

[x] Adding a new domain
[ ] Updating existing domain size
[ ] Changing domain name
[ ] Removing existing domain from list
[ ] Website code changes (512kb.club site)
[ ] Other not listed

[x] I used the uncompressed size of the site
[x] I have included a link to the GTMetrix report
[x] The domain is in the correct alphabetical order
[x] This site is not a ultra lightweight site
[x] The following information is filled identical to the data file

I confirm that I have read the FAQ section, particularly the two red items around minimal pages and inappropriate content and I attest that this site is neither of these things.

[x] Check to confirm

- domain: ihsaan.glitch.me
  url: https://ihsaan.glitch.me/
  size: 121
  last_checked: 2022-03-15

GTMetrix Report: https://gtmetrix.com/reports/ihsaan.glitch.me/FRFbeM34/

Thanks!


issue with embed base64 image into jinja2 template

Hello Mikael,
Thank you for making red-mail, it's great helper.
Describe the bug
It seems it's not possible to embed base64 image into jinja2 template. Image is always attached to the email instead being embedded.
To Reproduce
Code:
    # picture is passed from python PIL from another function as arg
    # picture = base64.b64encode(buff.getvalue())
    # this way, I avoid saving and reading picture from disk, so base64 is super useful.

    tp_decoded = base64.b64decode(picture)
    red_email.send(
        subject="The Subject",
<EMAIL_ADDRESS>        html_template="email/reset.html",
        body_images={
            "myimage": tp_decoded,
        },
    )

Template file:

Hello,

    {{ myimage }}

End result is attached image instead of embedded:

Expected behavior
Expecting that this would work the same way, as when no template is being used like in this example:
    tp_decoded = base64.b64decode(picture)
    red_email.send(
        subject="The Subject",
<EMAIL_ADDRESS>        html="""

Hello,

Auth code is valid for 30 minutes

            {{ myimage }}
            """,
        body_images={
            "myimage": tp_decoded,
        },
    )

Without template, image is embedded correctly:

Email provider:

Email service: Gmail, Protonmail
Application to view the email: Web Gmail, Web Protonmail

Environment (please complete the following information if relevant):

OS: Linux
Python version [3.10.5]
Red Mail version [0.4.0]

Why encode and decode again? You should be able to just embed the bytes
if you can pass around the PIL.Image object instead, you should be able to embed that as well
I may have misunderstood you problem, if these dont work please clarify the original type of the image object that is passed to these lines of code


How do I use shared libraries on Linux

vcpkg is creating static libraries in manifest mode. Ideally I would like to use shared libraries. Is there a way to force that?

https://github.com/microsoft/vcpkg/discussions/19127

You can add a new triplet file x64-linux-dynamic.cmake in VCPKG_ROOT/triplets and write the following code:
set(VCPKG_TARGET_ARCHITECTURE x64)
set(VCPKG_CRT_LINKAGE dynamic)
set(VCPKG_LIBRARY_LINKAGE dynamic)

set(VCPKG_CMAKE_SYSTEM_NAME Linux)

Then use --triplet=x64-linux-dynamic in the install command.

We hope your question was answered to your satisfaction; if it wasn't, you can reopen with more info.


Add flag --cpu-profile to enable pprof

To collect CPU profile information added a flag --cpu-profile which is a path to file where this collected information will be dumped.
This flag is valid only in debug mode or when --debug flag is applied.
Fixes #464

ping @runcom

LGTM

LGTM


Build failure: python311Packages.bitsandbytes

Steps To Reproduce
Steps to reproduce the behavior:
NIXPKGS_ALLOW_UNFREE=1 nix-shell -p 'python311Packages.bitsandbytes'

Build log
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "<string>", line 1, in <lambda>
  File "/nix/store/6b1fqdwb3g56j5pazv8zkx9qd0mv3wiz-python3-3.11.9/lib/python3.11/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1204, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1176, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1147, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 690, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 940, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/nix/store/j7613gwnhflnc6hyvxr6lvnd3x48bc5m-python3.11-bitsandbytes-0.42.0/lib/python3.11/site-packages/bitsandbytes/__init__.py", line 16, in <module>
    from .nn import modules
  File "/nix/store/j7613gwnhflnc6hyvxr6lvnd3x48bc5m-python3.11-bitsandbytes-0.42.0/lib/python3.11/site-packages/bitsandbytes/nn/__init__.py", line 6, in <module>
    from .triton_based_modules import SwitchBackLinear, SwitchBackLinearGlobal, SwitchBackLinearVectorwise, StandardLinear
  File "/nix/store/j7613gwnhflnc6hyvxr6lvnd3x48bc5m-python3.11-bitsandbytes-0.42.0/lib/python3.11/site-packages/bitsandbytes/nn/triton_based_modules.py", line 8, in <module>
    from bitsandbytes.triton.dequantize_rowwise import dequantize_rowwise
  File "/nix/store/j7613gwnhflnc6hyvxr6lvnd3x48bc5m-python3.11-bitsandbytes-0.42.0/lib/python3.11/site-packages/bitsandbytes/triton/dequantize_rowwise.py", line 10, in <module>
    import triton
  File "/nix/store/0ggxhg7260p9d1fgdq4bsg97xgd4rmc7-python3.11-triton-2.1.0/lib/python3.11/site-packages/triton/__init__.py", line 8, in <module>
    from .runtime import (
  File "/nix/store/0ggxhg7260p9d1fgdq4bsg97xgd4rmc7-python3.11-triton-2.1.0/lib/python3.11/site-packages/triton/runtime/__init__.py", line 1, in <module>
    from .autotuner import (Autotuner, Config, Heuristics, OutOfResources, autotune,
  File "/nix/store/0ggxhg7260p9d1fgdq4bsg97xgd4rmc7-python3.11-triton-2.1.0/lib/python3.11/site-packages/triton/runtime/autotuner.py", line 8, in <module>
    from .jit import KernelInterface
  File "/nix/store/0ggxhg7260p9d1fgdq4bsg97xgd4rmc7-python3.11-triton-2.1.0/lib/python3.11/site-packages/triton/runtime/jit.py", line 14, in <module>
    from ..common.backend import get_backend, path_to_ptxas
  File "/nix/store/0ggxhg7260p9d1fgdq4bsg97xgd4rmc7-python3.11-triton-2.1.0/lib/python3.11/site-packages/triton/common/__init__.py", line 1, in <module>
    from .build import _build, cuda_include_dir, libcuda_dirs
ImportError: cannot import name '_build' from 'triton.common.build' (/nix/store/0ggxhg7260p9d1fgdq4bsg97xgd4rmc7-python3.11-triton-2.1.0/lib/python3.11/site-packages/triton/common/build.py)
error: builder for '/nix/store/f1k1z6j56s0qf2pal5k7bycf7ybvyifs-python3.11-bitsandbytes-0.42.0.drv' failed with exit code 1;
       last 10 log lines:
       >     from .runtime import (
       >   File "/nix/store/0ggxhg7260p9d1fgdq4bsg97xgd4rmc7-python3.11-triton-2.1.0/lib/python3.11/site-packages/triton/runtime/__init__.py", line 1, in <module>
       >     from .autotuner import (Autotuner, Config, Heuristics, OutOfResources, autotune,
       >   File "/nix/store/0ggxhg7260p9d1fgdq4bsg97xgd4rmc7-python3.11-triton-2.1.0/lib/python3.11/site-packages/triton/runtime/autotuner.py", line 8, in <module>
       >     from .jit import KernelInterface
       >   File "/nix/store/0ggxhg7260p9d1fgdq4bsg97xgd4rmc7-python3.11-triton-2.1.0/lib/python3.11/site-packages/triton/runtime/jit.py", line 14, in <module>
       >     from ..common.backend import get_backend, path_to_ptxas
       >   File "/nix/store/0ggxhg7260p9d1fgdq4bsg97xgd4rmc7-python3.11-triton-2.1.0/lib/python3.11/site-packages/triton/common/__init__.py", line 1, in <module>
       >     from .build import _build, cuda_include_dir, libcuda_dirs
       > ImportError: cannot import name '_build' from 'triton.common.build' (/nix/store/0ggxhg7260p9d1fgdq4bsg97xgd4rmc7-python3.11-triton-2.1.0/lib/python3.11/site-packages/triton/common/build.py)
       For full logs, run 'nix log /nix/store/f1k1z6j56s0qf2pal5k7bycf7ybvyifs-python3.11-bitsandbytes-0.42.0.drv'.

Additional context
Commit fe220a6 seems likely to have broken the build for bitsandbytes.
Notify maintainers
@bcdarwin @samuela @SomeoneSerge
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.0-101-generic, Ubuntu, 22.04.3 LTS (Jammy Jellyfish), nobuild`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - nixpkgs: `/mnt/data/home/HammillC/.nix-defexpr/channels/nixpkgs`

Add a :+1: reaction to issues you find important.

I suspect the above output is related to 530d5769d57e88bde975c5fefb9ecfcddba89742
that commit modifies or creates the triton.common.build module referenced above. I'm rebuilding setting the _build to None and cuda_include_dir to [] to see if having dummy definitions solves the problem. Unfortunately it's slow going as it requires a full pytorch rebuild to see if it repaired bitsandbytes.

the trivial fix proposed above appears to resolve the build. Not sure if this would have ramifications elsewhere in the tree. Happy to PR the change if others want to help kick the tires @samuela @SomeoneSerge @bcdarwin

Oh!!! https://github.com/NixOS/nixpkgs/commit/530d5769d57e88bde975c5fefb9ecfcddba89742#diff-12d5872269fe05b4b44d02433ddaf5804f72b72ccda1c3b488d50684ba3cf889R94 was mean to be a >> not >... how on earth did this even pass the tests 🙈

@cfhammill a PR would be very welcome

@SomeoneSerge looks like your original idea should also work, and be less broken in mysterious ways, I can do a quick PR.


installing from source documentation is outdated

https://stack-of-tasks.github.io/pinocchio/download.html
There are a few issues I've stumbled upon:

Optional dependencies are not optional rather mandatory because I could not get cmake .. -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr/local to pass.
Eigenpy 2.6 is hard to install on Ubuntu because you cannot just install it with apt-get rather you must first download it from sources here and then install it with cmake. Because of that I think that the install procedure should be added to pinnochio documentation.

I think also that the repo needs GH Actions which would build pinocchio from sources so one can look into build steps to reproduce build from sources.

Do you want to use the Python bindings? Otherwise, you can add to the cmake command line -DBUILD_PYTHON_INTERFACE=OFF to deactivate the building of the Python interface.

I'm closing the issue as there is no answer from the original author.

Hi @jcarpent
I don't know if this is the current behaviour. However, I think it should not compile the Python bindings if eigenpy (and perhaps boost Python) is not detected.
You might also print a message that the python bindings are not going to be generated as it was not detected those dependencies.

I think that the problem still persist and closing it will not solve it. I have no intentions to contribute.

I think that the problem still persist and closing it will not solve it. I have no intentions to contribute.

Have you been able to install Pinocchio finally @IvanVnucec?

I think that the problem still persist and closing it will not solve it. I have no intentions to contribute.

Have you been able to install Pinocchio finally @IvanVnucec?

Yes I did but with a lot of fiddling around.
It was really a brute-force approach. Fortunately for me, I have a little bit of experience with programming and building/installing other dependencies was successful, but not easy.
If someone who is novice in programming tries to install Pinocchio from source, I'm afraid one will not succeed.


python311Packages.google-cloud-pubsub: 2.17.1 -> 2.18.0

Changelog: https://github.com/googleapis/python-pubsub/blob/v2.18.0/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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 243418 run on x86_64-linux 1

10 packages built:

home-assistant-component-tests.google_pubsub
home-assistant-component-tests.nest
python310Packages.google-cloud-pubsub
python310Packages.google-cloud-pubsub.dist
python310Packages.google-nest-sdm
python310Packages.google-nest-sdm.dist
python311Packages.google-cloud-pubsub
python311Packages.google-cloud-pubsub.dist
python311Packages.google-nest-sdm
python311Packages.google-nest-sdm.dist


Matching by request schema and calculate files directories

Allow imposter's matching by request schema
Dynamic responses based on regex endpoint or request schema
Calculate files directory(body and schema) based on imposters path
Update REAMDE.md with resolved features and new future features

Codecov Report

Merging #12 into master will increase coverage by 1.08%.
The diff coverage is 95.23%.

@@            Coverage Diff             @@
##           master      #12      +/-   ##
==========================================
+ Coverage   92.07%   93.16%   +1.08%
==========================================
  Files           3        5       +2
  Lines         101      117      +16
==========================================
+ Hits           93      109      +16
  Misses          5        5
  Partials        3        3

Impacted Files
Coverage Δ

imposter.go
100% <100%> (ø)

handler.go
91.66% <100%> (+0.11%)
:arrow_up:

server.go
100% <100%> (ø)
:arrow_up:

route_matchers.go
93.75% <93.75%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3d30ee6...bc924cd. Read the comment docs.


French develp version status broken

Description
The version status badge in the bottom left of the desktop UI of Jellyseer is broken in french.
In weblate, the english string is Overseer Develop which is translated to  Développement d'Overseer. This works because in french de  is replaced by d' when followed by a vowel.
In the case of Jellyseer, the string is Développemeent d'Jellyseer which should be Développemeent de Jellyseer.
I'm not sure how this should be handled.
Version
fd460df2439df154307d089ebb8206688f1b7b26
Steps to Reproduce

Install the right version
Set locale to french
Go to Jellyseer's home page

Screenshots

Logs
No response
Platform
desktop
Device
MSI Delta 15
Operating System
Manjaro Linux Gnome Unstable
Browser
Firefox
Additional Context
No response
Code of Conduct

[X] I agree to follow Overseerr's Code of Conduct

You'll need to correct in this line.
You can open a PR request and I'll accept c:

:tada: This issue has been resolved in version 1.5.0 :tada:
The release is available on:

v1.5.0
GitHub release

Your semantic-release bot :package::rocket:


Worker should be web in Procfile

So, I was developing a simple Telegram bot with Webhooks and your repo came in handy, I appreciate that. But I kept getting "h14" error, despite following all the steps in README. So basically Heroku refused to assign dyno to my process, I tried both heroku ps:scale worker=1 and changing it manually from dashboard. Logs looked like this:

Luckily, I found this post, which explained everything. After changing worker to web in my Procfile, bot finally started receiving requests, like this:

As you can see, it has nothing to do with the bot itself, because in both cases the app was launched successfully (look at "my comment" in logs).
I am not entirely sure this wasn't my fault, but it looks like it would be a good idea to at least mention web worker type in README.

Yes, I will add that. Thanks


XIVY-13261 Improve responsive-toolbar / add arrow-icon / add emptyDetail

I added the following improvements:

Add EmptyDetail-Component from UI-Components
Add Chevron to Components-Popup
Add responsiveness to Components-Popup (if not enough space only show "All Components")

I have one problem at the moment that I don't quiet know how to solve. If you resize and have a popover open and then it disappears (do to the width), the popover remains open because the ToolbarContainer component is only set to display: none and is not completely removed from the DOM (see end of the GIF). Unfortunately, I don't know how to listen to this resize event and close the popover accordingly. Do you have any ideas? If this is not possible, I assume that I can't simply work with the ToolbarContainer component and will probably have to use ref or window.innerWidth to remove the component directly.

I have one problem at the moment that I don't quiet know how to solve. If you resize and have a popover open and then it disappears (do to the width), the popover remains open because the ToolbarContainer component is only set to display: none and is not completely removed from the DOM (see end of the GIF). Unfortunately, I don't know how to listen to this resize event and close the popover accordingly. Do you have any ideas? If this is not possible, I assume that I can't simply work with the ToolbarContainer component and will probably have to use ref or window.innerWidth to remove the component directly.

have you checked the popover docs? e.g. tried out the hideOnDetached flag? https://www.radix-ui.com/primitives/docs/components/popover

Thanks, hideWhenDetached did the trick, great 🙌


Cross-schema Oracle patch

Ability to query across schemas with the Oracle connector

@bkief Thank you for your contribution!

This PR should've been merged into master (I've just fixed that).


Lack of some sources

I would like to modify a bit my local copy of ag-grid sources and rebuild it. I downloaded sources but when I try to recompile them with gulp, it tells me:
bower_components\ag-grid\src\ts\main.ts(5,1): error TS6053: File '(path)/bower_components/ag-grid/typings/tsd.ts' not found.
bower_components\ag-grid\src\ts\main.ts(12,16): error TS2304: Cannot find name 'exports'.
bower_components\ag-grid\src\ts\main.ts(13,20): error TS2304: Cannot find name 'module'.
bower_components\ag-grid\src\ts\main.ts(13,46): error TS2304: Cannot find name 'module'.
bower_components\ag-grid\src\ts\main.ts(14,13): error TS2304: Cannot find name 'exports'.
bower_components\ag-grid\src\ts\main.ts(14,23): error TS2304: Cannot find name 'module'.
bower_components\ag-grid\src\ts\main.ts(16,9): error TS2304: Cannot find name 'exports'.
[12:17:18] TypeScript: 7 semantic errors
[12:17:18] TypeScript: emit succeeded (with errors)
[12:17:21] Finished 'agGrid' after 8.75 s

I didn't find those sources on git. Could you publish them here or tell me were is my fault?
BTW: ag-grid is great!

it's a race condition in the gulp file. just run the gulp build a second time, it should solve it. basically i wasn't aware that gulp dependencies get executed in parallel.

After rebuilding those errors didn't appear again. Thanks!


Make the Contributing.md hacktoberfest ready

Make the Contributing.md hacktoberfest ready
🔲  Fix internal links to headings
🔲  Clean up language

Hey, Olavea/Maintainer of this repo,
I can fix the external links and can make minimal contributing guidelines for HackatoberFest 2023.
Kindly assign this to me.

Hey,
@GyanPrakashRaj
How do you feel about doing this job for the other plugin?
We want the CONTRIBUTING.md to look like this and if you can also add  contributing guidelines for HackatoberFest 2023. That would be great.
The issue is here
https://github.com/cloudinary-devs/gatsby-transformer-cloudinary/issues/244

Sorry I'm replying late
May I continue working on HacktoberFest contribution markdown file ?