feat(segmenter): add user dict to JiebaSegmenter

This PR adds a new option to the JiebaSegmenter by exposing an existing feature in the Jieba library:
Allow the user to extend the default dict by a custom dict of their choice. The dict needs to be specified as a path in the user_dict_file parameter. The format of the dict is specified in the Jieba repository
This feature was requested in this issue, which did not specify exactly which features to expose.
Potentially one could also expose the functionality to modify the existing dict. That seemed a bit too cumbersome for the user to me though.
The custom dict feature assumes that the dictionary file is accessible locally. If that requirement is too inconvenient, one could also try to get it via HTTP or so.
All changes are covered with unit tests.

I have read the CLA Document and I hereby sign the CLA

Cool! Thank you @jacobowitz


DelegatorBot doesn't handle reply messages until timeout isn't finished

Hello!
I have a delegator bot:
bot = telepot.aio.DelegatorBot(TOKEN, [
    pave_event_space()(
        per_from_id(), create_open, ITLHandler, timeout=10),
])

ITLHandler innerhit from telepot.aio.helper.ChatHandler
Here is a problem:
"on_chat_message" in my ITLHandler doesn't catch message if this message is a reply for previous bot's message, timeout doesn't finished and this message in a group. After timeout finished, and on__idle method completed i reply to the same bot's message and ITLHandler handle it! At the same time - "get_from_telegram_server()" in telepot.aio.Bot.message_loop() recieve both of this message and everything is good in private chat's.
Is it problem on my code?

Update: doesn't matter it's reply or not. In groups messages handles only after timeout is expired (except first message ofc).

Sorry, I don't quite understand your question. But there is one thing you seem to be doing wrong. If you use per_from_id(), then your handler should be a subclass of UserHandler. If you really want to use ChatHandler, then you should use per_chat_id() in front.
per_*() functions have to be paired correctly with *Handler. They have to be on the same page, so to speak.
bot = telepot.aio.DelegatorBot(TOKEN, [
    pave_event_space()(
        per_from_id(), create_open, UserHandlerSubclass, timeout=10),

    pave_event_space()(
        per_chat_id(), create_open, ChatHandlerSubclass, timeout=10),
])

Simply put, ChatHandler looks at messages with a certain chat id. If you want to perform a conversation in a private chat or group chat, you should use a ChatHandler.
UserHandler looks at messages with a certain from id. If you want to handle actions originating from one user (including his chat messages, inline query, etc), you should use a UserHandler.

Thanks a lot! It's work fine now. Issue can be closed.


pull request for e2e test at 01/27/2017 13:56:17

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Changes to objectclass table

swap objectclass id of Building and BuildingPart (also for Tunnel and Bridge)
Remove entries for CityObjectRelation and Role - they go into property not feature
Remove entry for ImplicitGeometry because it's stored in its own table not in feature
Add entry for TransportationComplex

Agree, CityObjectRelation is just an association class and should be handled as a complex attribute mapped into the property table. Also, it has no ADE hooks and hence doesn't need to be linked with the objectclass table.

I also agree, CityObjectRelation is just an association class and should be handled as a complex attribute mapped into the property table.

Add entry for TransportationComplex

TransportationComplex does not have a new successor class in CityGML 3.0. Most proper successor candidate class can be "AbstractTransportationSpace".

You are right, @muratkendir. I removed it from the list.

Updated with 4386fe8


Change candidate resolution logic to allow assemblies depending on shared framework.

This is required due to how AspNet Core is included via a framework reference now. In order to properly evaluate transitive projects that target AspNet Core 3.0 we'd need some level of information that they targeted a framework reference. This happens to be a missing feature in the sdk/nuget. Also, given that all of ASP.NET is now included via a framework reference the act of finding candidate assemblies to reduce the amount of assembly loads doesn't matter as much since we went from 100s of potential assemblies to only what the application currently targets.
Fixed a test issue where calling into BasicApi tests resulted in the attempted loading of EFCore.Design. Problem is EFCore.Design wasn't a dependency of our functional test project because of PrivateAssets="true" and therefore, when we tried to find candidate assemblies we read in the BasicApiTest.deps.json but operated on the functional tests.deps.json. I could have added the EFCore.Design package to the functional test project to fix this but given that the package wasn't being used choose to remove it instead.
Removed Mvc.Analyzers from AspNetCore.Mvc because it's no longer brought in via the shared framework. This was needed because with the new approach with always loading all dll's in an applications graph we'd attempt to load Mvc.Analyzers at which point we'd explode saying we couldn't load Roslyn (it's not available at runtime anymore).
Updated tests to reflect new expectations in regards to application part type loading.

Addresses #4332

Still need to benchmark the impact this has on startup performance with @sebastienros

When benchmarking this we ran into an issue where the benchmark app was using a super old school (project.json) invalidly packaged netstandard1.5 package and then barfed (Sigil). This really makes me think we need to try-catch around our resolution logic. @rynowak I know you had some super serious concerns about doing that though. Could you share those?
In the meanwhile, going to work on running a benchmark on one of the test apps that doesn't use Sigil.

So the results make me want to cry 😢

Description
RPS
CPU (%)
Memory (MB)
Avg. Latency (ms)
Startup (ms)
First Request (ms)
Latency (ms)

baseline
14,207
86
365
20.8
849
172.9
1.3

After Change
14,774
88
441
19
1056 (+24%)
608.7 (+352%)
1.4

--server http://asp-perf-win:5001 --client http://asp-perf-load:5002 `
>> --database MySql --jobs https://raw.githubusercontent.com/aspnet/AspNetCore/master/src/Mvc/benchmarkapps/BasicViews/benchmarks.json -n BasicViews.GetTagHelpers --no-warmup --duration 1 --self-contained -i 5 -x 1 --outputFile "C:\Users\nimullen\Documents\GitHub\AspNetCore\src\Mvc\src\Microsoft.AspNetCore.Mvc.Core\bin\Release\netcoreapp3.0\Microsoft.AspNetCore.Mvc.Core.dll"

Abandoning this. The perf results are too scary. Working with partner teams to get the right information into the deps file.


Copy builder constructor properties.  Fixes #102

Builder instances should copy the constructor properties argument instead of assigning it directly.  This prevents an error if multiple instances later set the same property.

Codecov Report

Merging #104 (5a606ae) into main (21b0b7d) will increase coverage by 0.03%.
The diff coverage is 99.79%.

@@            Coverage Diff             @@
##             main     #104      +/-   ##
==========================================
+ Coverage   99.81%   99.84%   +0.03%
==========================================
  Files          76       87      +11
  Lines        1060     1284     +224
  Branches       52      117      +65
==========================================
+ Hits         1058     1282     +224
- Misses          0        2       +2
+ Partials        2        0       -2

Impacted Files
Coverage Δ

src/internal/base/composition-object-base.ts
100.00% <ø> (ø)

src/internal/constants/button-styles.ts
100.00% <ø> (ø)

src/internal/constants/dispatch-on-types.ts
100.00% <ø> (ø)

src/internal/constants/element-types.ts
100.00% <ø> (ø)

src/internal/constants/file-types.ts
100.00% <ø> (ø)

src/internal/constants/object-types.ts
100.00% <ø> (ø)

src/internal/constants/response-types.ts
100.00% <ø> (ø)

src/internal/constants/surface-types.ts
100.00% <ø> (ø)

src/internal/exception/error.ts
100.00% <ø> (ø)

src/internal/helpers/apply-mixins.ts
100.00% <ø> (ø)

... and 80 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


feat: notify on ban revoke

Sends a discord notification when an admin revokes any ban.
Also, from now on, discord channels are identified by name, not by ID.

Codecov Report

Merging #73 into master will decrease coverage by 0.26%.
The diff coverage is 34.37%.

@@            Coverage Diff             @@
##           master      #73      +/-   ##
==========================================
- Coverage   87.81%   87.55%   -0.27%
==========================================
  Files          86       86
  Lines        2971     2988      +17
  Branches      128      130       +2
==========================================
+ Hits         2609     2616       +7
- Misses        324      334      +10
  Partials       38       38

Impacted Files
Coverage Δ

.../discord/services/discord-notifications.service.ts
28.84% <0%> (-6.87%)
:arrow_down:

src/environment/environment.ts
13.04% <0%> (ø)
:arrow_up:

src/players/services/player-bans.service.spec.ts
98.66% <100%> (+0.11%)
:arrow_up:

src/players/services/player-bans.service.ts
88.88% <100%> (+0.31%)
:arrow_up:

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 be7edc7...c911fe5. Read the comment docs.


Consider updating to Redux 1.0 RC

Redux 1.0 RC is out with breaking changes. No further API changes are expected in 1.0 so it may be a good time to port the example to 1.0 RC (in a branch). We will release 1.0 when the docs are ready.
You can find the comprehensive list of the changes in 1.0 RC against 1.0 alpha in the Redux 1.0 RC release notes. If you haven't ported to alpha yet, you'll need to apply changes from 0.12 to alpha first.
Thank you!
Please make sure to report any issues so we can release a stable 1.0.

I've been following those threads and trying to decide when to pull the trigger. Thanks for the heads-up. I'm on it!


Prevent network disruption on adding a new VPC tier for redundant VRs

Description
This PR fixes https://github.com/apache/cloudstack/issues/8108
As of now, on adding a new network tier to a VPC, results in a small network disruption because of keepalived's config reload on both the VRs. This patch fixes this by doing operations in this order:

Stop keepalived on all the backup VRs. This prevents the backup VR from becoming master when keepalived on the PRIMARY VR is getting reloaded.
Update the config and reload on all primary VRs.
Update the config and restart on all backup VRs.

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

How did you try to break this feature and the system with this change?

@blueorangutan package

@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✖ el7 ✖ el8 ✖ el9 ✖ debian ✖ suse15. SL-JID 9935

@blueorangutan package

@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el7 ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 9936

@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

@blueorangutan package

@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

@blueorangutan package

@weizhouapache a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el7 ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 9957

@blueorangutan test

@vishesh92 a [SL] Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

[SF] Trillian test result (tid-10454)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 43308 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr9251-t10454-kvm-centos7.zip
Smoke tests completed. 130 look OK, 1 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_02_trigger_shutdown
Failure
341.63
test_safe_shutdown.py

@blueorangutan package

@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el7 ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 9974

@blueorangutan test

@DaanHoogland a [SL] Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

[SF] Trillian test result (tid-10466)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 42653 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr9251-t10466-kvm-centos7.zip
Smoke tests completed. 130 look OK, 1 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_02_trigger_shutdown
Failure
341.72
test_safe_shutdown.py

tested in a lab env:

started a redundant VPC
created a tier
deployed a vm
started a ping to the outside
added a tier
no packets being dropped.


I can join twice

Joined twice with new picks and the results were weird. Please fix.

Should be resolved in the app refactor which now uses a SQLite backend: 6c6ccc8be5d28a553d679c91eb3199bf275a232e


[cocoon] Issue with Commit Link and Copy to Clipboard Functionality in Cocoon dashboard

Screen capture
https://github.com/flutter/flutter/assets/11145366/725a3b04-56b4-4149-a75e-723cf94e689c
Description
I encountered an issue in the Cocoon dashboard where the expected behavior of the commit link and copy to clipboard icon is not functioning as intended. Here's a breakdown of the problem:
Commit Link Issue
When I attempt to open the commit link within Cocoon, there is no response or action. Clicking the commit link does not lead to the expected destination, and it appears to be non-functional.
Copy to Clipboard Icon Issue
Instead of copying the commit hash to my clipboard as expected, clicking the copy to clipboard icon results in the launch of another browser window. This new window navigates to the GitHub issue page, rather than copying the commit hash.
System specs
Machine: 2021 M1 Macbook Pro
OS: Ventura 13.5
Browser: Chrome Version 115.0.5790.170 (Official Build) (arm64)
Validation steps:

Click author avatar
Click the commit link (nothing happens)
Click the copy icon (link is opened)

Expected Behavior

The commit link should lead to the corresponding commit page.
Clicking the copy to clipboard icon should copy the commit hash to the clipboard without opening a new browser window.

@zanderso which chrome version are you using? Is this issue here exactly the same as yours: https://github.com/flutter/flutter/issues/132134?
Both links/copy work for me with chrome version 116.0.5845.82 (Official Build) (arm64)

Just updated to Version 116.0.5845.96 (Official Build) (arm64) and the issue is still present.

Can confirm this is still present, and super annoying when trying to get at a PR that has broken the tree.

(Added fyi-web just in case Clipboard management is broken (?))

this issue may be related?

https://github.com/flutter/flutter/issues/138833

The dashboard is using a bespoke implementation of a link called Hyperlink. The dashboard also enables semantics. However, I don't see any mention of Semantics in the implementation of Hyperlink. I think the framework is trying to do its best to make semantics work, but it's failing due to no guidance from the widget itself. I see the label and the tap handler of the hyperlink merged into the parent card semantic node, which seems wrong.
Consider using the Link widget from package:url_launcher. Alternatively, use the Semantics widget to provide proper semantics for the Hyperlink. The Link widget can be used for inspiration.

Great find! I'll try to clean-up the Hyperlinks when I get around to this!


Can I target a Dom or a String instead of a URL?

I'm forced to use casperjs for logging in and render the JS of the site I'm scraping. That means I already have the Dom. How can I pass it to scrape-it directly?

@sscarduzio Of course, if you have some HTML  as a string or cheerio object, you can pass it to the scrapeHTML method.

Great news, thanks I will try :)

@sscarduzio  Did you succeed it?


feat: Out of the box React Query ESLint plugin when using tRPC

Is your feature request related to a problem? Please describe.
Not really a problem.
Describe the solution you'd like to see
The official ESLint plugin seems promising. I'm not sure why it isn't already included. If there is a reason I would like to know it.
Describe alternate solutions

Additional information
No response

Sound promising, but does it work with tRPC?

Sounds promising, but does it work with tRPC?

That's a good question. I tried to make it error but I failed. I think a tRPC expert could answer this.

I dont see any value using it along with trpc.

exhaustive deps - trpc sets keys for you so this rule is irrelevant
prefer-object-syntax - also irrelevant since there is only a single valid syntax when using trpc
stable-query-client - the initialized code handles this


docker plugin enable cannot find the plugin's socket

Create a volume using docker plugin but no socket found

I created a sshfs volume plugin flowing the docker official doc developing a plugin
Create a volume

docker volume create -d sshfs --name sshvolume -o sshcmd=<IP_ADDRESS>:/remote -o password=password

Got an error

Error response from daemon: create sshvolume: Post http://%2Frun%2Fdocker%2Fplugins%2F8f7b8f931b38a4ef53d0e4f8d738e26e8f10ef8bd26c8244f4b8dcc7276b685f%2Fsshfs.sock/VolumeDriver.Create: dial unix /run/docker/plugins/8f7b8f931b38a4ef53d0e4f8d738e26e8f10ef8bd26c8244f4b8dcc7276b685f/sshfs.sock: connect: no such file or directory

Directory /run/docker/plugins/8f7b8f931b38a4ef53d0e4f8d738e26e8f10ef8bd26c8244f4b8dcc7276b685f is empty.
sshfs plugin config.json
{
        "description": "sshFS plugin for Docker",
            "documentation": "https://docs.docker.com/engine/extend/plugins/",
                "entrypoint": ["/docker-volume-sshfs"],
                "network": {
                               "type": "host"
                },
                "interface" : {
                               "types": ["docker.volumedriver/1.0"],
                                          "socket": "sshfs.sock"
                },
                "linux": {
                            "capabilities": ["CAP_SYS_ADMIN"]
                }
}

Output of docker version:
Client:
 Version:      1.13.1
 API version:  1.26
 Go version:   go1.7.5
 Git commit:   092cba3
 Built:        Wed Feb  8 06:38:28 2017
 OS/Arch:      linux/amd64

Server:
 Version:      1.13.1
 API version:  1.26 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   092cba3
 Built:        Wed Feb  8 06:38:28 2017
 OS/Arch:      linux/amd64
 Experimental: false

Output of docker info:
Containers: 4
 Running: 4
 Paused: 0
 Stopped: 0
Images: 44
Server Version: 1.13.1
Storage Driver: overlay
 Backing Filesystem: xfs
 Supports d_type: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: flocker local
 Network: bridge contiv/v2plugin:latest host macvlan null overlay
Swarm: active
 NodeID: n2tuxvoib9yaz2uqj193u5kkd
 Is Manager: true
 ClusterID: 41ypi3l8xmpyah3p55zm0tiz0
 Managers: 1
 Nodes: 3
 Orchestration:
  Task History Retention Limit: 5
 Raft:
  Snapshot Interval: 10000
  Number of Old Snapshots to Retain: 0
  Heartbeat Tick: 1
  Election Tick: 3
 Dispatcher:
  Heartbeat Period: 5 seconds
 CA Configuration:
  Expiry Duration: 3 months
 Node Address: <IP_ADDRESS>
 Manager Addresses:
  <IP_ADDRESS>:2377
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: aa8187dbd3b7ad67d8e5e3a15115d3eef43a7ed1
runc version: 9df8b306d01f59d3a8029be411de015b7304dd8f
init version: 949e6fa
Security Options:
 seccomp
  Profile: default
Kernel Version: 3.10.0-514.6.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 40
Total Memory: 125.6 GiB
Name: sz-pg-oam-docker-test-001.tendcloud.com
ID: E3EW:5GDB:KB2E:JANJ:2HCQ:TROP:W3H5:ENQA:23FH:RJ5T:UX5T:O7M2
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
 sz-pg-oam-docker-hub-001.tendcloud.com
 <IP_ADDRESS>/8
Live Restore Enabled: false

Physical machine

/cc @vieux @anusha-ragunathan ptal

docker plugin enable will find the plugin's socket at
client, err := plugins.NewClientWithTimeout("unix://"+sockAddr, nil, c.timeoutInSecs)

Should the socket created when I create a plugin manually? However how the plugin know its ID before I enable it?

The plugin should create the socket under /var/run/docker. It's clearly doc-ed in https://github.com/docker/docker/blob/master/docs/extend/index.md#developing-a-plugin
Note: The /run/docker/plugins directory is mandatory inside of the plugin's filesystem for docker to communicate with the plugin.
The plugin ID is created during create/install and enable happens after that.

Closing the issue, since this is a question more than an issue and the question has been answered.

@anusha-ragunathan I have read the doc and developing the plugin as the instructions but no socket appear in /run/docker/plugin directory.

@rootsongjc : Are you creating a socket like so? https://github.com/vieux/docker-volume-sshfs/blob/b051239b05a9880fbb32742e2ed2c24e3ec998f0/main.go#L268

Hi @anusha-ragunathan
I met the same issue.
`const socketAddress = "/run/docker/plugins/zmq.sock"
var logLevels = map[string]logrus.Level{
"debug": logrus.DebugLevel,
"info":  logrus.InfoLevel,
"warn":  logrus.WarnLevel,
"error": logrus.ErrorLevel,
}
func main() {
levelVal := os.Getenv("LOG_LEVEL")
if levelVal == "" {
levelVal = "info"
}
if level, exists := logLevels[levelVal]; exists {
logrus.SetLevel(level)
} else {
fmt.Fprintln(os.Stderr, "invalid log level: ", levelVal)
os.Exit(1)
}
    h := sdk.NewHandler(`{"Implements": ["LoggingDriver"]}`)
    zmgloggerr.Handlers(&h, zmgloggerr.NewDriver())
    if err := h.ServeUnix(socketAddress, 0); err != nil {
            panic(err)
    }

when I try to enable the plugin. I got the folloing output:root@max-VirtualBox:/run/docker/plugins# docker plugin enable zmq_002
Error response from daemon: dial unix /run/docker/plugins/7148073f6d0c859d597e90df1d2e59bf7f493f26700cb40ae9a3bc9c3f487c1f/zmq.sock: connect: no such file or directory
root@max-VirtualBox:/run/docker/plugins# ls
root@max-VirtualBox:/run/docker/plugins#
`
it seems there is no zmq.sock.
BTW: I am trying to create a log plugin

my machine:
root@max-VirtualBox:/run/docker/plugins# docker info
Containers: 5
 Running: 0
 Paused: 0
 Stopped: 5
Images: 8
Server Version: 17.06.0-ce
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 27
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: cfb82a876ecc11b5ca0977d1733adbe58599088a
runc version: 2d41c047c83e09a6d61d464906feb2a2f3c52aa4
init version: 949e6fa
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.10.0-28-generic
Operating System: Ubuntu 17.04
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 990MiB
Name: max-VirtualBox
ID: YBHV:5TA4:EM7Y:HXSM:ZLSC:HDGO:ML2W:BNPV:JEBT:ZOPL:HTDD:ZE3H
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false

WARNING: No swap limit support
root@max-VirtualBox:/run/docker/plugins# docker --version
Docker version 17.06.0-ce, build 02c1d87

The socket is created by the plugin and once the plugin has started to run does it need to first create the socket before performing any other task as part of its startup?
It seems like that's expected (as part of plugin install), manager_linux.go:pluginPostStart() does a net.Dial() on what it knows should be the plugin socket. But its not guaranteed that the plugin has as yet created the socket after it was started. Is there a reason why its expected that the plugin must create the socket early enough so this check passes?

Hi @anusha-ragunathan and @savagecm,
I think I found the reason why it's not working.
Even if you follow the documentation https://github.com/moby/moby/blob/17.03.x/docs/extend/index.md#developing-a-plugin
It cannot work because the plugin is running inside a container so the daemon won't be able to find your socket unless you bind it (mount in the config.json).

The plugin should create the socket under /var/run/docker. It's clearly doc-ed in

@anusha-ragunathan , imho, it is not as clear, because one may think that the interface.socket must be created under / (root) inside the container.
For example, provided config.json has:
    "interface": {
        "socket": "plugin.sock",

Once a user tries enabling the plugin, the user gets the following error:
Error response from daemon: dial unix /run/docker/plugins/1a3f916a1f6c5efa68cf78627cd8e353c7aae2910437d74f6f7f2d27fb54735c/plugin.sock: connect: no such file or directory

Is it reasonable to assume that Docker tries looking for the socket file inside the container?

This may be helpful to someone - if you debug your brand new plugin, and you see such errors (connect: no such file or directory, or connection refused) - check for obsolete .sock plugin files and restart docker, otherwise it won't find your .sock file new location.

i have the same problem:
[root@cephnode1 ~]# docker plugin install rexray/ebs EBS_ACCESSKEY=access_key EBS_SECRETKEY=secret_key
Plugin "rexray/ebs" is requesting the following privileges:

network: [host]
mount: [/dev]
allow-all-devices: [true]
capabilities: [CAP_SYS_ADMIN]
Do you grant the above permissions? [y/N] y
latest: Pulling from rexray/ebs
d726edfb6c8d: Download complete
Digest: sha256:b5b0680b6dd53a4c61bac21942738a69edfe3d6a6516acc13045d257889c9213
Status: Downloaded newer image for rexray/ebs:latest
Error response from daemon: dial unix /run/docker/plugins/432f4b002c54601215fbcc719efb8bae4e5a9c8a9c172e4a8709414ebb42cf23/rexray.sock: connect: no such file or directory

Having the same issue https://github.com/fentas/docker-volume-davfs/issues/3
Does anyone know how to ensure that sock is created before docker is looking for it?

@fentas
Did you figure out what's wrong?
Having the same issue

@eleaner did you find anything about the issue?

@eleaner nope never figured it out. Sometimes it works sometimes it doesn't.. :/ :man_shrugging:

Same problem here. Totally fresh VM and Docker install. Simply trying to install an AuthZ plugin from Docker Hub:
$ printf('y') | docker plugin install openpolicyagent/opa-docker-authz-v2:0.6
Plugin "openpolicyagent/opa-docker-authz-v2:0.6" is requesting the following privileges:
 - mount: [/etc/docker]
Do you grant the above permissions? [y/N] y
0.6: Pulling from openpolicyagent/opa-docker-authz-v2
19ad1cb286ca: Download complete
Digest: sha256:5f32ec04f92a53434a94a5db10279f3d513b00d213e7878fee46a6e1b632701a
Status: Downloaded newer image for openpolicyagent/opa-docker-authz-v2:0.6
Error response from daemon: dial unix /run/docker/plugins/277fc1ca43069a4c20ff20b975ad1df580f6f9364b51f191cb8f28b4969dc77b/opa-docker-authz.sock: connect: no such file or directory

In case it's relevant: I am running Docker locally, with the server requiring TLS. I have the client and CA certificates appropriately placed, so I am running docker without using sudo. I have moved the Docker Root Dir to a separate partition. I am also enforcing userns-remaping for user management, with strict file permissions locally. I suspect one of these settings may be the root cause. Here are my Docker details:

 /etc/docker/daemon.json

$ cat /etc/docker/daemon.json
{
  "icc": false,
  "userns-remap": "default",
  "log-driver": "syslog",
  "live-restore": true,
  "userland-proxy": false,
  "no-new-privileges": true,
"storage-driver": "overlay2",
"storage-opts": [],
"data-root": "/docker",
"tls": true,
"tlsverify": true,
"tlscacert": "/certs/docker/ca.pem",
"tlscert": "/certs/docker/server-cert.pem",
"tlskey": "/certs/docker/server-key.pem"
}

 Docker Info

$ docker info
Client:
 Debug Mode: false
Server:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 1
Server Version: 19.03.8
Storage Driver: overlay2
Backing Filesystem:
Supports d_type: true
Native Overlay Diff: true
Logging Driver: syslog
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 7ad184331fa3e55e52b890ea95e65ba581ae3429
runc version: dc9208a3303feef5b3839f4323d9beb36df0a9dd
init version: fec3683
Security Options:
apparmor
seccomp
Profile: default
userns
Kernel Version: 4.19.0-8-cloud-amd64
Operating System: Debian GNU/Linux 10 (buster)
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 3.857GiB
Docker Root Dir: /docker/165536.165536
Debug Mode: false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
<IP_ADDRESS>/8
Live Restore Enabled: true
WARNING: No swap limit support

 Docker Version

$ docker version
Client: Docker Engine - Community
 Version:           19.03.8
 API version:       1.40
 Go version:        go1.12.17
 Git commit:        afacb8b7f0
 Built:             Wed Mar 11 01:25:56 2020
 OS/Arch:           linux/amd64
 Experimental:      false
Server: Docker Engine - Community
Engine:
Version:          19.03.8
API version:      1.40 (minimum version 1.12)
Go version:       go1.12.17
Git commit:       afacb8b7f0
Built:            Wed Mar 11 01:24:28 2020
OS/Arch:          linux/amd64
Experimental:     false
containerd:
Version:          1.2.13
GitCommit:        7ad184331fa3e55e52b890ea95e65ba581ae3429
runc:
Version:          1.0.0-rc10
GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
docker-init:
Version:          0.18.0
GitCommit:        fec3683


ffmpeg version compatibility

Hey, awesome project and i've been waiting for something like this for the past 5 years :D
I am running ffmpeg (and shared libraries) at 4.2.4, and I have some build issues

Build log
root@6dee3e1d8ada:~/app# make
g++ -Iimgui -Iimgui/backends -Iimnodes -g -Wall -Wformat `pkg-config --with-path=/usr/local/lib/pkgconfig --cflags glfw3` `pkg-config --with-path=/usr/local/lib/pkgconfig --cflags libavutil` `pkg-config --with-path=/usr/local/lib/pkgconfig --cflags libavcodec` `pkg-config --with-path=/usr/local/lib/pkgconfig --cflags libavformat` `pkg-config --with-path=/usr/local/lib/pkgconfig --cflags libswresample` `pkg-config --with-path=/usr/local/lib/pkgconfig --cflags libswscale` `pkg-config --with-path=/usr/local/lib/pkgconfig --cflags libavfilter` -c -o main.o main.cpp
/bin/sh: 1: pkg-config: not found
/bin/sh: 1: pkg-config: not found
/bin/sh: 1: pkg-config: not found
/bin/sh: 1: pkg-config: not found
/bin/sh: 1: pkg-config: not found
/bin/sh: 1: pkg-config: not found
/bin/sh: 1: pkg-config: not found
main.cpp: In function 'bool is_simple_filter(const AVFilter*)':
main.cpp:502:9: error: 'avfilter_filter_pad_count' was not declared in this scope; did you mean 'avfilter_pad_count'?
  502 |     if (avfilter_filter_pad_count(filter, 0) == 1 &&
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~
      |         avfilter_pad_count
main.cpp: In function 'bool is_source_filter(const AVFilter*)':
main.cpp:530:10: error: 'avfilter_filter_pad_count' was not declared in this scope; did you mean 'avfilter_pad_count'?
  530 |     if ((avfilter_filter_pad_count(filter, 0)  > 0  ||  (filter->flags & AVFILTER_FLAG_DYNAMIC_INPUTS)) ||
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~
      |          avfilter_pad_count
main.cpp: In function 'bool is_sink_filter(const AVFilter*)':
main.cpp:540:10: error: 'avfilter_filter_pad_count' was not declared in this scope; did you mean 'avfilter_pad_count'?
  540 |     if ((avfilter_filter_pad_count(filter, 0)  > 0  ||  (filter->flags & AVFILTER_FLAG_DYNAMIC_INPUTS)) &&
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~
      |          avfilter_pad_count
main.cpp: In function 'bool is_source_audio_filter(const AVFilter*)':
main.cpp:551:34: error: 'avfilter_filter_pad_count' was not declared in this scope; did you mean 'avfilter_pad_count'?
  551 |         for (unsigned i = 0; i < avfilter_filter_pad_count(filter, 1); i++) {
      |                                  ^~~~~~~~~~~~~~~~~~~~~~~~~
      |                                  avfilter_pad_count
main.cpp: In function 'bool is_source_video_filter(const AVFilter*)':
main.cpp:565:34: error: 'avfilter_filter_pad_count' was not declared in this scope; did you mean 'avfilter_pad_count'?
  565 |         for (unsigned i = 0; i < avfilter_filter_pad_count(filter, 1); i++) {
      |                                  ^~~~~~~~~~~~~~~~~~~~~~~~~
      |                                  avfilter_pad_count
main.cpp: In function 'bool is_sink_audio_filter(const AVFilter*)':
main.cpp:579:34: error: 'avfilter_filter_pad_count' was not declared in this scope; did you mean 'avfilter_pad_count'?
  579 |         for (unsigned i = 0; i < avfilter_filter_pad_count(filter, 0); i++) {
      |                                  ^~~~~~~~~~~~~~~~~~~~~~~~~
      |                                  avfilter_pad_count
main.cpp: In function 'bool is_sink_video_filter(const AVFilter*)':
main.cpp:593:34: error: 'avfilter_filter_pad_count' was not declared in this scope; did you mean 'avfilter_pad_count'?
  593 |         for (unsigned i = 0; i < avfilter_filter_pad_count(filter, 0); i++) {
      |                                  ^~~~~~~~~~~~~~~~~~~~~~~~~
      |                                  avfilter_pad_count
main.cpp: In function 'void draw_node_options(FilterNode*)':
main.cpp:911:18: error: 'AV_OPT_TYPE_CHLAYOUT' was not declared in this scope; did you mean 'AV_OPT_TYPE_COLOR'?
  911 |             case AV_OPT_TYPE_CHLAYOUT:
      |                  ^~~~~~~~~~~~~~~~~~~~
      |                  AV_OPT_TYPE_COLOR
main.cpp: In function 'void show_commands(bool*)':
main.cpp:1268:48: error: 'AV_OPT_FLAG_RUNTIME_PARAM' was not declared in this scope; did you mean 'AV_OPT_FLAG_SUBTITLE_PARAM'?
 1268 |                             if (!(opt->flags & AV_OPT_FLAG_RUNTIME_PARAM))
      |                                                ^~~~~~~~~~~~~~~~~~~~~~~~~
      |                                                AV_OPT_FLAG_SUBTITLE_PARAM
make: *** [Makefile:61: main.o] Error 1

Is this compatible only with ffmpeg 5+?

Developed on ffmpeg master. But I think it will compile with FFmpeg 5.0 too (master FFmpeg have some source filters fixes for setting frame_rate of outlinks, so if you can, pick that one instead of 5.0). Anything older than 5.0 is not supported.

mentioned ffmpeg version in readme.md file.


[UI/UX][BLE] Integrate BLE with new homepage

done in https://github.com/covid19risk/covidwatch-android/pull/76


Breakpoints starting with a number aren't working (2xl, etc)

Description
When I use 2xl breakpoint, I expect my styles to render, but instead my 2xl breakpoint styles are never rendered
https://stackblitz.com/edit/stackblitz-starters-3siapy?file=pages%2Findex.js
Link to Reproduction
https://stackblitz.com/edit/stackblitz-starters-3siapy?file=pages%2Findex.js
Steps to reproduce

Add styles to a break point starting with a number (2xl, 3xl, etc)
Can be within a style attribute or breakpoint attribute

className={css({
  bg: {
    '2xl': 'orange.500',
  },
})}
// or
className={css({
  '2xl: {
    bg: 'orange.500',
  },
})}

Styles never render at specified breakpoint, although you can see them generated in your CSS

@media screen and (min-width: 1536px) {
    .\2xl\:bg_orange\.500 {
      background: var(--colors-orange-500)
    }
}

JS Framework
React
Panda CSS Version
0.4.0
Browser
Brave Version 1.52.126 Chromium: 114.0.5735.133 (Official Build) (arm64)
Operating System

[X] macOS
[ ] Windows
[ ] Linux

Additional Information
For what its worth, I checked out how Tailwind handles this and it prefixes a 3 to the style name. Not sure why, though.
@media (min-width: 1536px) {
  .\32xl\:bg-orange-400 {
    --tw-bg-opacity: 1;
    background-color: rgb(251 146 60 / var(--tw-bg-opacity));
  }
}

After some cursory reading, it looks like .\32 is used because 32 is the unicode position of 2. Today I learned.
However, I don't know what tooling is used to generate their (or Panda's) classNames, otherwise, I'd happily open a PR!

https://www.w3.org/International/questions/qa-escapes#css_identifiers
https://mathiasbynens.be/notes/css-escapes#css

Thanks for such a detailed breakdown. TIL
I've gone ahead to update the escape function. I'll release an update shortly.

Ah, ha. I was actually digging into this myself. But I'll post what Ive been working on in case its useful


Peer review - Repository

Your repo looks very clean, you already had the project live on heroku and have updated everything according to your concept. You have described the API and dependencies that you use very well.
These are the only things missing from your repo:

The data life cycle
Real-time events explained

Your readme is looking good (as expected), good job on already being up to date. This will save you a lot of time in the coming weeks 🚀

To Do:

[ ] Data lifecycle diagram
[ ] Explain real-time events

This issue has been added to my issue summary. Thanks again!


feat: Add initialize lifecycle method

TL;DR- ESM for a widget can now export an initialize function along size the render. This function is executed when the widget front end first loads and can be used to setup event handlers / state to share across views created in render.
export function initialize({ model }) {
  model.on("change:value", () => console.log(model.get("value")));
}
export function render({ model, el }) {
  model.on("change:value", () => el.innerText = model.get("value"))
}

Towards:

#266
#388

Motivation
In the MVC framework used by Jupyter Widgets, right now anywidget treats Python as the sole "source of truth" for defining the model and only supports rendering views of that model in JS (view render). We don't currently have an API to initialize some initial front-end model listeners/state (or allow for a DOM-less use of anywidget).
Surveying existing Jupyter Widgets in the wild, it seems this type of model initialization is often defined in the WidgetModel.initialize method.  This PR introduces a new export which maybe be implemented for an anywidget front-end module: initialize. Initialize has the same signature as render, except only model is provided in the context.
The semantic difference is that initialize is executed once per model (regardless of whether anything is displayed) and render is executed once per view. As we iron out this feature, the setup export is prefixed with unstable_, so to try this out you'll need to define a unstable_initialize function.
Examples
Example 1: Model-level "logger" for state changes
Here, initialize adds an event listener to console.log any time value changes, and then each view adds their own event listener for updating the text node in the DOM. If the console.log were to be setup per-view, then the console would print "Value is X" for every view. Adding the handler in unstable_initialize ensures this logic is only handled once per instance.
import anywidget
import traitlets

class Widget(anywidget.AnyWidget):
    _esm = """
    export async function unstable_initialize({ model }) {
        model.on("change:value", () => {
            console.log(`Value is ${model.get("value")}!`);
        });
    }
    export function render({ model, el }) {
        el.innerText = `Value is ${model.get("value")}!`;
        model.on("change:value", () => {
            el.innerText = `Value is ${model.get("value")}!`;
        })
    }
    """
    value = traitlets.Int(0).tag(sync=True)

widget = Widget()
widget

widget

widget.value = 10 # logs once to the browser console and updates both DOM views

Example 2: DOM-less widget
import anywidget
import traitlets

class Widget(anywidget.AnyWidget):
    _view_name = traitlets.Any(None).tag(sync=True) # TODO: nicer way to do this?
    _esm = """
    export async function unstable_initialize({ model }) {
        model.on("change:value", () => {
            console.log(`Value is ${model.get("value")}!`);
        });
    }
    """
    value = traitlets.Int(0).tag(sync=True)

widget = Widget()
widget.value = 1 # logs in the browser console
widget # displays a plain/text repr
# Widget()

I'm thinking I will likely get rid of keeping the model._unstable_context. The same effect can be accomplished within the module itself with a separate variable:
const value_history = [];

export async function _unstable_setup({ model }) {
	model.on("change:value", () => {
		value_history.push(model.get("value"));
	});
}
export function render({ model, el }) {
	let button = document.createElement("button");
	button.innerHTML = `Log history`;
	button.addEventListener("click", () => {
		console.log(`the count history is ${value_history}`);
	});
	el.appendChild(button);
}

I have renamed this method from setup to initialize to mirror the method it represents in traditional Jupyter Widgets (WidgetModel.initialize), much like how render reflects DOMWidgetModel.render.

On my first review this was the only comment I had :)

setup to initialize to mirror the method it represents in traditional Jupyter Widgets

Awesome work @manzt !

Just wanted to report here that I've been experimenting with this PR and it is working great so far!

That's great to hear!
I’m curious about what you think of allowing (encouraging?) global (module-level state) being shared between the instantiate and render hooks. We can do this because we re-load the ESM for each widget instance, so each instance is its own isolated module.
An alternative would be to have a function (like Rollup/Vite plugins) which can create some initial isolated state.
export default function () {
  let foo;
  return {
    instantiate({ model }) {
      foo = "bar";
    },
    render({ model, el }) {
      console.log(foo);
    },
  }
}

Although I like the named exports, I think this would give us more flexibility going forward to change how the ESM is loaded by the anywidget "runtime".

Hmm I like the isolated state option but I'm afraid I'm not familiar enough with the front-end JS ecosystem to have a proper opinion.
How this approach vs. global module-level state would work with the multiple widgets per ESM workaround described in https://github.com/manzt/anywidget/discussions/382#discussioncomment-7647610?

I suppose you could delegate the widget from initialize in the default export:
function tableWidget() { /* ... */ }

function chartWidget() { /* ... */ }

const widgetRegistry = { tableWidget, chartWidget };

export default function () {
  let widget;
  return {
    initialize({ model }) {
      const createWidget = widgetRegistry[model.get("component")];
      widget = createWidget();
      return widget.initialize({ model });
    },
    render({ model, el }) {
      return widget.render({ model, el });
    }
  }
}

I prefer the simplicity of the named render and initialize functions (especially for users who are unfamiliar to JS, they may get tripped up by the need to define a function that exports an object; there are many curly brackets to keep track of). I would imagine that users will copy/paste the boilerplate from the README/docs and modify since it may be tricky to remember.
I am not sure I see the benefit of defining shared state within vs. outside of the function - does it have to do with HMR?
Would this not work?
function tableWidget() { /* ... */ }

function chartWidget() { /* ... */ }

const widgetRegistry = { tableWidget, chartWidget };

let widget;

export function initialize({ model }) {
  const createWidget = widgetRegistry[model.get("component")];
  widget = createWidget();
  return widget.initialize({ model });
}
export function render({ model, el }) {
  return widget.render({ model, el });
}

I would not be opposed to the default function export way if there are benefits. It would probably be confusing to support both options (named function exports and default function that returns an object), so if the default function export way provides benefits I would go all-in on that mechanism rather than supporting both.

Thanks for the feedback everyone! I plan to merge this week, just need to write up some release notes, documentation, and consider how to deprecate the render API.

I am not sure I see the benefit of defining shared state within vs. outside of the function - does it have to do with HMR?

Currently there isn't really a clear benefit to either choice. However, the function would be a future design consideration, which I think would allow us to avoid potential future breaking changes.
For example, the anywidget "runtime" currently imports a fresh, isolated module per widget instance (i.e., Python class instantiation). This means that things like importing dependencies is duplicated each time a widget in instantiated.
Having the shared state within the function would allow us experiment with changing the runtime, and avoid breaking changes for end users. For example, we could execute this top-level logic once per widget defintion, meaning that the ESM could define local state that could be shared across all instances.
With top-level await, this could include additional setup/logic that might be useful:
(This code is not real and doesn't work)
import * as d3 from "https://esm.sh/d3";

const globalSharedData = await fetch('https://jsonplaceholder.typicode.com/todos/1').then(res => res.json());
const globalSharedState = {};

export default function () {
  const localState = {};
  return {
    instantiate({ model }) {},
    render({ model, el }) {},
}

Thanks for all the feedback here! I have updated the PR description and implementation. Will merge and then move to updating the documentation for the preferred API.

Want to ping some of the existing widget implementations with anticipated deprecation notice
cc: @domoritz @juba @jonmmease

[!WARNING]
This PR adds a deprecation notice for existing named render exports (i.e., all existing widget implementations). I'm not sure we will deprecate in the future, but migrating away from this would allow us more flexibility in loading widget ESM in the future. Migration:
Remove
export function render({ model, el }) { ... }
^^^^^^

Use
function render({ model, el }) { ... }
         ^^^^^^
export default { render }
                 ^^^^^^

Thanks for the ping. I'll update mosaic.

Hello, Just to confirm, what is the least minimal version where this change is not breaking existing code?
In other words: if I migrate right now my widgets to this newer API, what is the least version I can claim to support (assuming I only use this feature, for simplicity) ?
Thank you in advance!

what is the least minimal version where this change is not breaking existing code?

Great question!
The API is of 0.9.0. You can pin anywidget>=0.9.0 in your pyproject.toml etc.

The API is of 0.9.0. You can pin anywidget>=0.9.0 in your pyproject.toml etc.

@manzt If possible, it'd be nice to include this in the deprecation warning :)


Add previewUrl to assets in Frontify

📦 Published PR as canary version: Canary Versions

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>

:rocket: PR was released in<EMAIL_ADDRESS>:rocket:


chore(deps): update dependency winston to v3.4.0

This PR contains the following updates:

Package
Type
Update
Change

winston
dependencies
minor
3.3.3 -> 3.4.0

Release Notes

winstonjs/winston
v3.4.0
Compare Source
Yesterday's release was done with a higher sense of urgency than usual
due to vandalism in the colors package.
This release:

ties up a loose end by including [#1973] to go with [#1824]
adds a missing http property in NpmConfigSetColors [#2004] (thanks @SimDaSong)
fixes a minor issue in the build/release process [#2014]
pins the version of the testing framework to avoid an issue with a test incorrectly failing [#2017]

The biggest change in this release, motivating the feature-level update, is
[#2006] Make winston more ESM friendly, thanks to @miguelcobain.
Thanks also to @DABH, @wbt, and @fearphage for contributions and reviews!
v3.3.4
Compare Source
Compared to v3.3.3, this version fixes some issues and includes some updates to project infrastructure,
such as replacing Travis with Github CI and dependabot configuration.
There have also been several relatively minor improvements to documentation, and incorporation of some updated dependencies.
Dependency updates include a critical bug fix [#2008] in response to self-vandalism by the author of a dependency.

[#1964] Added documentation for how to use a new externally maintained Seq transport.
[#1712] Add default metadata when calling log with string level and message.
[#1824] Unbind event listeners on close
[#1961] Handle undefined rejections
[#1878] Correct boolean evaluation of empty-string value for eol option
[#1977] Improved consistency of object parameters for better test reliability

Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box.

This PR has been generated by Renovate Bot.

Renovate Ignore Notification
As this PR has been closed unmerged, Renovate will now ignore this update (3.4.0). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.
If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.


macOS: Dead key breaks text editing

Happens with current master. Can be reproduced on US keyboard by pressing [alt + `] and then a. It does output correct character (à), but after that text selection is no longer possible, and after moving caret new character are always appended to the beginning of text.

cc @cbracken

The issue seems to be that composition is never finished. The only method called after composition finishes is - (void)insertText: replacementRange: which commits the composition, but doesn't end it.

Closing in favor of https://github.com/flutter/flutter/issues/77544.


Support JWT auth

Some partners require utilizing JWT with their applications, so being able to supply it within jsonrpc-client would be great.
This is the expected post call via curl:
curl -vvvv --location --request POST 'https://near-mainnet.dev.api.pagoda.co/rpc/v1/' \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer eyJhbGciOiJSUNiJ9.eyJzdWIiOiIxY3ODkwIZSI6ImFkbWluIiwiaXNzIjoiYWRtaW4taXNzdWVyIiwiYWRtaW4iOnRydWUsImlhdCI6MTUxNjIzOTAyMn0.TZXtM_-6jBInZTXK53Mei3eSXR15FXAFilV_CjnW7VxvaMsR-G587d0UUNAggVIH-M5T6UuiPBtj2uQnaila__OZcnmXis4qjlxb1CGir1V1xwaOBSfLZSsczqObhw4wf_84ShfZib3rO2b8hUOozA2tgTjKG4VB8ZWbEtC56CELpSHULKf8rvnNtYVibrfGAiT5B5HaIky_c-odc3HmcTkT8jCV1dqncJgUYidLe2G6beb4WfU-3H0FmNhAiUGJSmhCsocP2Dt7xIITFdBX4RJMpXEy' \
  --data-raw '{"jsonrpc": "2.0", "id":"dontcare","method":"status","params":[] }'

but would be nice to have an interface around it like ApiKey

@miraclx does this sound simple enough to add?

It's already possible to do this externally. Either by implementing HeaderEntry (see this example in Prevalidated).
.. or by calling
client.header(
    ("Authorization", "Bearer eyJhbGciOiJSUNiJ9...")
)?;

But yeah, I see certainly see value in exporting a consistent interface that helps with this.
Perhaps something on the order of:
client.header(
    ApiKey::new("83e534d5-adf8-4ff3-..."), // x-api-key: 83e534d5-adf8-4ff3-...
);
client.header(
    Authorization::bearer("eyJhbGciOiJSUNiJ9..."), // Authorization: Bearer eyJhbGciOiJSUNiJ9...
);

Unsure if we should support more than the bearer scheme here, or perhaps we can leave it generic for the users to specify both the scheme and value. Even reqwest only provides helpers for the bearer and basic schemes.
But as a rule of thumb, it's always easier to introduce what's missing than deprecating / straight-up removing features.

But as a rule of thumb, it's always easier to introduce what's missing than deprecating / straight-up removing features.

yeah I can understand that, but don't think bearer is something going away in the future, since it's pretty standard. I do think that header(("Authorization", "Bearer eyJhbGciOiJSUNiJ9...")) isn't too intuitive especially since you have to put a space between Bearer and the token. So your snippet with Authorization::bearer looks more clean to deal with this case, but I'll leave this up to you whether you want to add, since the basic functionality is already there

yeah I can understand that, but don't think bearer is something going away in the future, since it's pretty standard.

yeah, bearer is fine. I was contemplating whether to add the rest of the valid schemes. But for now, I'll settle on starting with bearer and if the need arises for the rest, we can add them incrementally, rather than adding them now and receiving little to no usage. But at least for now, I think bearer holds the greatest value.

gotcha, yeah let's just have bearer and add further when there's a need


⚠ Pihole-KA has degraded performance

In 4576ea3, Pihole-KA ($URL_PIHOLE_MERZ_NIMBUS) experienced degraded performance:

HTTP code: 200
Response time: 10359 ms

Resolved: Pihole-KA performance has improved in 78e1d7a.


Bump up cirq requirements to protobuf 4.x

Bump up to dependencies to protobuf 4.x
Rebuild proto-derived sources to reflect protobuf 4.x
Update expected textproto for protobuf 4.x
fix new mypy complaints about proto-derived types

Fixes #5929

This fix has a slight downside that any other packages using both cirq and protobuf would need to upgrade to protobuf 4.x.
I feel that that transition would need to happen at some point anyway.
Do we want to add CI check for successful pip-compile?

@tanujkhattar , @mpharrigan - can you PTAL?

I don't know anything about the backwards-compatibility implications of the changes to the generated pb2.py files, but LGTM

I have skimmed through the Python notes in https://github.com/protocolbuffers/protobuf/blob/main/CHANGES.txt and could not see Python API changes likely to impact us.  As for the serialized content, that should be backwards compatible.  I had to update the expected textproto for a test in 4aa01461ce5551299b89a950f9009fd09b5d0826, but all changes were in the output order or in dropping the decimal point for integer floats, e.g., 0.0 --> 0.

cc @maffoo - in case there might be some serious implications for updating protobuf in pyle.  We would like to continue installing cirq and pyle in the same virtual environment, so if one bumps up the protobuf requirement, it affects the other  as well.

Usually protobuf updates are fairly easy in pyle, but I'm guessing 3->4 will cause more headaches than usual. Probably just gonna have to try it out though, and see if anything breaks. One possible issue would be if other dependencies want protobuf 3 (e.g. something like tensorflow).

I think TFQ is probably at the highest risk of breaking with this change. See https://github.com/tensorflow/quantum/blob/master/requirements.txt
@MichaelBroughton Do you have thoughts on if / how this might break TFQ ?

Thank you all for the feedback.  The gentler solution seems to be to pin the grpcio-status dependency so it stays compatible with protobuf 3.x and makes pip-compile happy.  Please see #5953.
I am converting this to a draft in case it would help with protobuf 3.x -> 4.x transition sometime in the future.

Superseded by #6191


FormDescription will not empty String into code

Hi, I encountered a bug while using the form builder. The code is written in such a way that if there is no description, the FormDescription component will not be rendered in the code part... but the moment that someone can write a just space... is not calculated.
To tell the truth, these are the topics on which we can say that if he missed and made space, it is his fault. But it's better to have all the cases covered.

Expected way:

users input is " " in description input?
Not render FormDescription component

Incorrect way:

users input is " " in description input?
It's rendering with " ", like: <FormDescription> </FormDescription>

Thank you for noticing the gap and producing a quality solution.


Release v0.8.1

Release Checklist

[ ] OWNERS must LGTM the release proposal.
At least two for minor or major releases. At least one for a patch release.
[ ] Verify that the changelog in this issue and the CHANGELOG folder is up-to-date

[ ] Use https://github.com/kubernetes/release/tree/master/cmd/release-notes to gather notes.
Example: release-notes --org kubernetes-sigs --repo kueue --branch release-0.3 --start-sha 4a0ebe7a3c5f2775cdf5fc7d60c23225660f8702 --end-sha a51cf138afe65677f5f5c97f8f8b1bc4887f73d2 --dependencies=false --required-author=""

[ ] For major or minor releases (v$MAJ.$MIN.0), create a new release branch.

[ ] An OWNER creates a vanilla release branch with
git branch release-$MAJ.$MIN main
[ ] An OWNER pushes the new release branch with
git push release-$MAJ.$MIN

[ ] Update the release branch:

[ ] Update RELEASE_BRANCH and RELEASE_VERSION in Makefile and run make prepare-release-branch
[ ] Update the CHANGELOG
[ ] Submit a pull request with the changes:

[ ] An OWNER prepares a draft release

[ ] Write the change log into the draft release.
[ ] Run
make artifacts IMAGE_REGISTRY=registry.k8s.io/kueue GIT_TAG=$VERSION
to generate the artifacts and upload the files in the artifacts folder
to the draft release.

[ ] An OWNER creates a signed tag running
git tag -s $VERSION
and inserts the changelog into the tag description.
To perform this step, you need a PGP key registered on github.
[ ] An OWNER pushes the tag with
git push $VERSION

Triggers prow to build and publish a staging container image
us-central1-docker.pkg.dev/k8s-staging-images/kueue/kueue:$VERSION

[ ] Submit a PR against k8s.io,
updating registry.k8s.io/images/k8s-staging-kueue/images.yaml to
promote the container images
to production:
[ ] Wait for the PR to be merged and verify that the image registry.k8s.io/kueue/kueue:$VERSION is available.
[ ] Publish the draft release prepared at the GitHub releases page.
Link:
[ ] Run the openvex action to generate openvex data. The action will add the file to the release artifacts.
[ ] Run the SBOM action to generate the SBOM and add it to the release.
[ ] For major or minor releases, merge the main branch into the website branch to publish the updated documentation.
[ ] Send an announcement email to<EMAIL_ADDRESS>and<EMAIL_ADDRESS>with the subject [ANNOUNCE] kueue $VERSION is released.
[ ] Update the below files with respective values in main branch :

Latest version in README.md
Latest version in cmd/experimental/kjobctl/docs/installation.md
Release notes in the CHANGELOG
version in site/hugo.toml
appVersion in charts/kueue/Chart.yaml
SECURITY-INSIGHTS.yaml values by running make update-security-insights GIT_TAG=$VERSION

[ ] For a major or minor release, prepare the repo for the next version:

[ ] Create an unannotated devel tag in the
main branch, on the first commit that gets merged after the release
branch has been created (presumably the README update commit above), and, push the tag:
DEVEL=v0.$(($MAJ+1)).0-devel; git tag $DEVEL main && git push $DEVEL
This ensures that the devel builds on the main branch will have a meaningful version number.
[ ] Create a milestone for the next minor release and update prow to set it automatically for new PRs:

[ ] Create the presubmits jobs for the next patch release:

Changelog
Changes since `v0.8.0`:

### Feature

- Add gauge metric admission_cycle_preemption_skips that reports the number of Workloads in a ClusterQueue
  that got preemptions candidates, but had to be skipped in the last cycle. (#2942, @alculquicondor)
- Publish images via artifact registry (#2832, @alculquicondor)

### Bug or Regression

- CLI: Support `-` and `.` in the resource flavor name on `create cq` (#2706, @trasc)
- Detect and enable support for job CRDs installed after Kueue starts. (#2991, @ChristianZaccaria)
- Fix over-admission after deleting resources from borrowing ClusterQueue. (#2879, @mbobrovskyi)
- Fix support for kuberay 1.2.x (#2983, @mbobrovskyi)
- Helm: Fix a bug for "unclosed action error". (#2688, @mbobrovskyi)
- Prevent infinite preemption loop when PrioritySortingWithinCohort=false
  is used together with borrowWithinCohort. (#2831, @mimowo)
- Support for helm charts in the us-central1-docker.pkg.dev/k8s-staging-images/charts repository (#2834, @IrvingMg)
- Update Flavor selection logic to prefer Flavors which allow reclamation of lent nominal quota, over Flavors which require preempting workloads within the ClusterQueue. This matches the behavior in the single Flavor case. (#2829, @gabesaba)

Replace @k8s-infra-cherrypick-robot for the original authors.
Other than that, LGTM

+1
Remaining TODO: https://github.com/kubernetes-sigs/kueue/pull/2574

@tenzen-y @alculquicondor I have updated the release notes after https://github.com/kubernetes-sigs/kueue/pull/2574 got merged, PTAL

LGTM

LGTM


Implement ansible molecule to run Unit tests

AVD Unit test
This section provides a list of AVD scenario executed during Continuous Integration to validate AVD integration.
Ansible molecule
Molecule provides support for testing with multiple instances, operating systems and distributions, virtualization providers, test frameworks and testing scenarios. Molecule encourages an approach that results in consistently developed roles that are well-written, easily understood and maintained.
Scenario
Current molecule implementation provides following scenario:

AVD-L3LS-EBGP
AVD-L3LS-EBGP-JSON
AVD-L3LS-ISIS

Manual execution
To manually run molecule testing, follow commands:
# Install development requirements
$ pip install -r development/requirements-dev.txt

# Move to AVD collection
$ ansible-avd/ansible_collections/arista/avd

# Run molecule for a given test
$ molecule test -s <scenario-name>

# Run molecule for all test
$ molecule test --all

Continuous Integration
These scenario are all included in github actions and executed on push and pull_request when a file under roles and/or molecule is updated.
name: Ansible Molecule
on:
  push:
  pull_request:
    paths:
      - 'ansible_collections/arista/avd/roles/**'
      - 'ansible_collections/arista/avd/molecules/**'
      - 'requirements.txt'
jobs:
  molecule:
    runs-on: ubuntu-latest
    env:
      PY_COLORS: 1 # allows molecule colors to be passed to GitHub Actions
      ANSIBLE_FORCE_COLOR: 1 # allows ansible colors to be passed to GitHub Actions
    strategy:
      fail-fast: true
      matrix:
        avd_scenario:
          - avd-l3ls-ebgp
          - avd-l3ls-ebgp-json
          - avd-l3ls-isis
    steps:
      - name: Checkout repository
        uses: actions/checkout@v2

      - name: Run molecule action
        uses: inetsix/molecule-collection-actions@master
        with:
          molecule_parentdir: 'ansible_collections/arista/avd'
          molecule_command: 'test'
          molecule_args: '-s ${{ matrix.avd_scenario }}'
          pip_file: 'requirements.txt'

When PR will be validated, we will be able to remove testing folder and playbook_validation.yml from CI as it will be replaced by molecule approach

[x] Add scenario for eos_cli_config_gen in molecule
[x] Export artifacts from any scenario when CI runs

After review and before merge, molecule action should be set to pull_request only

Molecule is pruning all generated files meaning that artifacts do not have generated files.
Pruning extra files from scenario ephemeral directory


Can't Play/Pause in other apps when the extension is active

When I press my media key button it don't pause my music apps because the extension have a priority and is anoying.

Hi @Tom60chat. Sorry to say that but key bindings is managed by OS and it's impossible to bind keys to more than one app in the same time. Priority gets the application which has registered bindings later. There is no any bindings management into the extension - all is done by Chrome. So, what you're asking is impossible to resolve.


Syntax Error on Relax NG Exercise 2

I'm getting a general syntax error on my xml document after I associate my schema. I feel like it's a pretty obvious problem, but I've just been staring at it for a while and I think I need a pair of fresh eyes to help point out the issue.

@natalyamyers Sorry I missed seeing your post! I can't see the source of the error here: the schema looks right to me, although in your rule for the <sent> element, I would move the n attribute outside of mixed{}. That won't cause a syntax error, though...
If you haven't solved this already, what's the text of the error message you're seeing?

@ebeshero no text error, just giving me the syntax error with no information on it

@natalyamyers I can't tell what's wrong from the screen capture. I'd need to see the files. But try saving both the schema and the XML file, and then, with your cursor in the XML file, click the red checkmark button in oXygen to refresh the schema validation. Does that take care of it?


feat(CategoryTheory/ChosenFiniteProducts): Type u has chosen finite products

Introduce CategoryTheory/ChosenFiniteProducts/Types.lean and prove that the category of types has chosen finite products given by the product of types.

The rationale behind adding this is that along with the results in CategoryTheory/ChosenFiniteProduct/FunctorCategory, given two presheaves X Y : C ⥤ Type, it should become easier to work with bifunctors of the form (c, d) => X(x) × Y(y).

Closing as this instance is already provided in CategoryTheory/Monoidal/Types/Basic.lean


Multiselect fields not working on Gall Admin page

Edit: The color, walls, cells, alignment, and shape fields should be multiselect fields like Texture is currently; they are all (with the exception maybe of walls and cells but still best to just change those too unless there's a good reason not to?) traits that can take more than one value.
Original: This is not a priority for me at the moment, but the color, walls, cells, alignment, and shape fields in the admin Add Gallformers page are not working at the moment. They only let you select one option, and there's no way to add more after you've done that. Texture, Location, and Host are working fine though.

Those fields are not designed to be multiselect, only texture and location currently support that.

Oh okay, changed to reflect that. Was there a reason you did it that way in the first place?

I do not remember at this point. I am guessing I decided it did not make sense to assign multiples of those.

As part of the bug fix for #83 I am going to go ahead and make this change as well. Might take a bit longer as a result. To be clear I am going to make:

Walls
Cells
Alignment
Color
Shape

all multi-select.
Abundance, which is a property of a species (not just gall so it is also present on hosts) will NOT be multiselect.

Given that I am already in the same code it may make sense for me to tackle the detachable issue as well. #40
CC/ @ahiatt14

Hey - quick question here. Did a search and figured this was as good a place as any to ask...
The Location(s) filter on ID Galls. I can tell by the (s) at the end that this is intended to be multi-select, but I'm wondering if it should be. As one of the two key options for filtering galls, this seems like the easiest place to make a mistake. I didn't realize it was multi-select when I was playing around. I was trying to see what I could get to come up for Q. berberidifolia. I was going through each of the areas I recognized as having known galls associated with them and realized that each time I was selecting a location it was adding to the filter. If I were looking for a stem gall but also had previously selected petiole and had not cleared it, would it be looking for a gall that would be set up as both occurring on the stem and the petiole or either on the stem or the petiole (show galls for both options)? If I'm a beginner trying to figure out what a gall is, what would be the value of the multi-select in this field?
If it's looking for something that would occur on BOTH I have selected, this may be problematic in the same ways we were concerned season may be problematic. If it would look for galls with either of them associated, it could be a huge bonus. For example, if the location of a leaf gall was difficult to distinguish based on size/cluster/whatever, I could select all the leaf options and in the process catch the one I'm looking for. One that comes to mind is the Two-Horned Gall ( Dryocosmus dubiosus) where you can find them along the leaf midrib as well as the leaf veins. Sometimes multiple galls on the same leaf in both locations.
This gall isn't yet in the database and I was thinking about using it as my first entry so I can play around with it.


Load new MPU-9255

Hi Richard,
I have added the definitions for a IvenSense MPU-9255 IMU.
The only difference I can see was the location address changed from the MPU-9250 (0x71) to MPU-9255 (0x73).
Hope it helps someone.

Problem is that I can't test it and even RTIMULib2 really isn't supported any more as I have moved on to other things.

I could put an entry on my blog pointing to your implementation for those interested in the MPU-9255. Would that be useful?

Hi Richard,
I guess a entry in your blog, would be good. I understand you would not be able to test (can't have every piece of kit which comes on to the market).
Your RTIMULib does seem to get used (mentioned) in lots of places, a good piece of useful work.
Thanks

Your RTIMULib does seem to get used (mentioned) in lots of places, a good piece of useful work.

+1


A Error about "from tensorflow.examples.tutorials.mnist import input_data"

Please go to Stack Overflow for help and support:
https://stackoverflow.com/questions/tagged/tensorflow
If you open a GitHub issue, here is our policy:

It must be a bug, a feature request, or a significant problem with documentation (for small docs fixes please send a PR instead).
The form below must be filled out.
It shouldn't be a TensorBoard issue. Those go here.

Here's why we have that policy: TensorFlow developers respond to issues. We want to focus on work that benefits the whole community, e.g., fixing bugs and adding features. Support only helps individuals. GitHub also notifies thousands of people when issues are filed. We want them to see you communicating an interesting problem, rather than being redirected to Stack Overflow.

System information

**Have I written custom code:YES ,I have
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):windows10 64 bit
Mobile device  if the issue happens on mobile device:no ,it's not work on Mobile device
TensorFlow installed from (source or binary):installed from command
TensorFlow version (use command below):tensorflow 1.10.0
Python version:python3.6.5
Bazel version (if compiling from source):no,it's not compiling from source
GCC/Compiler version (if compiling from source):no,it's not compiling from source
CUDA/cuDNN version:CUDA9.0/cuDNN7.1
GPU model and memory:GTX1080/8192
Exact command to reproduce:command

Describe the problem
Describe the problem clearly here. Be sure to convey here why it's a bug in TensorFlow or a feature request.
In python, I type:
from tensorflow.examples.tutorials.mnist import input_data
it got error as follows:
NotFoundError                             Traceback (most recent call last)
 in ()
----> 1 from tensorflow.examples.tutorials.mnist import input_data
2 import tensorflow as tf
3 mnist = input_data.read_data_sets('MNIST_data', one_hot=True)
D:\software\anaconda\envs\tensorflow-gpu\lib\site-packages\tensorflow\examples\tutorials\mnist_init_.py in ()
19 from future import print_function
20
---> 21 from tensorflow.examples.tutorials.mnist import input_data
22 from tensorflow.examples.tutorials.mnist import mnist
D:\software\anaconda\envs\tensorflow-gpu\lib\site-packages\tensorflow\examples\tutorials\mnist\input_data.py in ()
28 from six.moves import xrange  # pylint: disable=redefined-builtin
29 import tensorflow as tf
---> 30 from tensorflow.contrib.learn.python.learn.datasets.mnist import read_data_sets
31 # pylint: enable=unused-import
D:\software\anaconda\envs\tensorflow-gpu\lib\site-packages\tensorflow\contrib_init_.py in ()
35 from tensorflow.contrib import crf
36 from tensorflow.contrib import cudnn_rnn
---> 37 from tensorflow.contrib import data
38 from tensorflow.contrib import deprecated
39 from tensorflow.contrib import distribute
D:\software\anaconda\envs\tensorflow-gpu\lib\site-packages\tensorflow\contrib\data_init_.py in ()
76 from tensorflow.contrib.data.python.ops.counter import Counter
77 from tensorflow.contrib.data.python.ops.enumerate_ops import enumerate_dataset
---> 78 from tensorflow.contrib.data.python.ops.error_ops import ignore_errors
79 from tensorflow.contrib.data.python.ops.get_single_element import get_single_element
80 from tensorflow.contrib.data.python.ops.grouping import bucket_by_sequence_length
D:\software\anaconda\envs\tensorflow-gpu\lib\site-packages\tensorflow\contrib\data\python\ops\error_ops.py in ()
18 from future import print_function
19
---> 20 from tensorflow.contrib.data.python.ops import contrib_op_loader  # pylint: disable=unused-import
21 from tensorflow.contrib.data.python.ops import gen_dataset_ops
22 from tensorflow.python.data.ops import dataset_ops
D:\software\anaconda\envs\tensorflow-gpu\lib\site-packages\tensorflow\contrib\data\python\ops\contrib_op_loader.py in ()
22
23 _dataset_ops = loader.load_op_library(
---> 24     resource_loader.get_path_to_datafile("../../_dataset_ops.so"))
D:\software\anaconda\envs\tensorflow-gpu\lib\site-packages\tensorflow\contrib\util\loader.py in load_op_library(path)
54       return None
55   path = resource_loader.get_path_to_datafile(path)
---> 56   ret = load_library.load_op_library(path)
57   assert ret, 'Could not load %s' % path
58   return ret
D:\software\anaconda\envs\tensorflow-gpu\lib\site-packages\tensorflow\python\framework\load_library.py in load_op_library(library_filename)
54     RuntimeError: when unable to load the library or get the python wrappers.
55   """
---> 56   lib_handle = py_tf.TF_LoadLibrary(library_filename)
57
58   op_list_str = py_tf.TF_GetOpList(lib_handle)
NotFoundError: D:\software\anaconda\envs\tensorflow-gpu\lib\site-packages\tensorflow\contrib\data\python\ops...._dataset_ops.so not found
and It also pops up a window saying:
The procedure entry point ?addcleanup@arenaimpl@internal@protobuf@google@@QEAAXPEAXP6AX0@Z@Z could not be located in the dynamic link library _pywarp_tensorflow_internal.pyd
what should I do to solve it?by the way ,I Use it OK in tensorflow 1.5.have it changed in tensorflow?where  can I find guid about it?
please help ! thank you very much in advance!
Source code / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached. Try to provide a reproducible test case that is the bare minimum necessary to generate the problem.

@noticeable Hi, thanks for  your post. Can you delete the file _dataset_ops.so from the below path and try it again. Thank you!
NotFoundError: D:\software\anaconda\envs\tensorflow-gpu\lib\site-packages\tensorflow\contrib\data\python\ops...._dataset_ops.so not found

@noticeable Have you tried as mentioned above ?

Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!

its having version issue.
install this and your problem would be solved
pip install tensorflow==1.14


Nice work !!! When will the entire dataset available and the corresponding code with it? Is it already to use?

Thank you for your interest in our dataset. You can download a preliminary version here: https://drive.google.com/file/d/1ctMoU8PcBSUQtJWuLIPhomhEsh3Pg0bf/view
To load the dataset you can use our API as described here: https://github.com/jutanke/hik/blob/main/documentation/api.md
We are still ironing out some issues with the API which should be finalized for NeurIPS23, so ~Dec 10th 2023.


The request to create a scratch org failed with error code: C-1033. at checkScratchOrgInfoForErrors (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/core/lib/org/scratchOrgErrorCodes.js:76:15) at async pollForScratchOrgInfo (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/core/lib/org/scratchOrgInfoApi.js:304:16) at async scratchOrgCreate (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/core/lib/org/scratchOrgCreate.js:165:17) at async Create.createScratchOrg (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/plugin-org/lib/commands/force/org/create.js:151:68) at async Create._run (/usr/local/lib/node_modules/sfdx-cli/node_modules/@oclif/core/lib/command.js:107:22) at async Config.runCommand (/usr/local/lib/node_modules/sfdx-cli/node_modules/@oclif/core/lib/config/config.js:296:25)

Summary
The request to create a scratch org failed with error code: C-1033. at checkScratchOrgInfoForErrors (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/core/lib/org/scratchOrgErrorCodes.js:76:15) at async pollForScratchOrgInfo (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/core/lib/org/scratchOrgInfoApi.js:304:16) at async scratchOrgCreate (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/core/lib/org/scratchOrgCreate.js:165:17) at async Create.createScratchOrg (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/plugin-org/lib/commands/force/org/create.js:151:68) at async Create._run (/usr/local/lib/node_modules/sfdx-cli/node_modules/@oclif/core/lib/command.js:107:22) at async Config.runCommand (/usr/local/lib/node_modules/sfdx-cli/node_modules/@oclif/core/lib/config/config.js:296:25)
Steps To Reproduce:

Using a valid 2GP project, try to create a scratch org

Expected result
I expect a scratch org to be created successfully
Actual result
It fails with an error
The request to create a scratch org failed with error code: C-1033. at checkScratchOrgInfoForErrors (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/core/lib/org/scratchOrgErrorCodes.js:76:15) at async pollForScratchOrgInfo (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/core/lib/org/scratchOrgInfoApi.js:304:16) at async scratchOrgCreate (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/core/lib/org/scratchOrgCreate.js:165:17) at async Create.createScratchOrg (/usr/local/lib/node_modules/sfdx-cli/node_modules/@salesforce/plugin-org/lib/commands/force/org/create.js:151:68) at async Create._run (/usr/local/lib/node_modules/sfdx-cli/node_modules/@oclif/core/lib/command.js:107:22) at async Config.runCommand (/usr/local/lib/node_modules/sfdx-cli/node_modules/@oclif/core/lib/config/config.js:296:25)
System Information

Which shell/terminal are you using? (e.g. bash, zsh, powershell 5, powershell 7, cmd.exe, etc.)
Github actions bash or zsh.

Version of SFDX CLI is: sfdx-cli/7.187.1 linux-x64 node-v16.19.0
Additional information

{
"orgName": "Package Development",
"edition": "Developer",
"features": [],
"settings": {
"apexSettings": {
"enableGaplessTestAutoNum": true, "enableDisableParallelApexTesting": true
},
"quoteSettings": {
"enableQuote": true
},
"lightningExperienceSettings": {
"enableS1DesktopEnabled": true
},
"nameSettings": {
"enableNameSuffix": false
},
"mobileSettings": {
"enableS1EncryptedStoragePref2": false
}
}
}

      - name: "Create scratch org"
        id: create
        run: |
          echo $(sfdx force:org:create -f src/unpackaged/config/project-scratch-def.json -a scratch-org -s -d 1 --json) > create.json
          v=$(cat create.json | jq '.status' -r)
          if [[ $v != 0 ]]
          then
              echo "Create scratch org failed"
              n=$(cat create.json | jq '.name' -r)
              s=$(cat create.json | jq '.stack' -r)
              echo "Error message: $n $s"
              m="Org creation failed with error $n $s"
              echo "success=false" >> $GITHUB_OUTPUT
              mx=$(echo $m | tr '\n' ' ')
              echo "result=$mx" >> $GITHUB_OUTPUT
          else
              echo "success=true" >> $GITHUB_OUTPUT
          fi

Did you check your DevHub instance against this list?
https://trailblazer.salesforce.com/issues_view?id=a1p4V000003BIYGQA4
https://status.salesforce.com/incidents/10793

Did you check your DevHub instance against this list?
https://trailblazer.salesforce.com/issues_view?id=a1p4V000003BIYGQA4
https://status.salesforce.com/incidents/10793

Thanks David.
Ok, two devhubs are located on NA208 and NA156 so both of them are affected by that issue. Probably I should try to switch to my personal devhub then

what a heck is going on? when I tried to switch to my European-based devhub, I started receiving the following errors:

I use English locale and English language. How come the scratch org is created with Russian language?

closing because the linked KI closed.


Unable to download Migrated objects from destination buckets

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

kind bug

/kind feature

What happened:
After migrating object from source bucket to destination bucket, user will not be able to download objects from destination buckets
What you expected to happen:
User should be able to download objects from destination buckets.
How to reproduce it (as minimally and precisely as possible):

Install Gelato project with development branch
Create backends and create 2 buckets (i.e. source and destination)
Upload objects to Source bucket
Migrate objects ( Objects got migrated successfully and can be downloaded from cloud console)
Try to download objects using OpenSDS dashboard or API [FAILED]

Anything else we need to know?:
Environment:

Gelato(release/branch) version: development (Elba release)
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

S3-API logs

S3 service logs

TiDB data

Probable reason: ACL properties of Migrated objects is not getting updated

This is fixed by #966 , Thanks


Question about speech to text quotas

Hi, I have already read the docs about quotas for speech to text. They say 900 requests per minute and I see that in my google patform account. But I am getting
RESOURCE_EXHAUSTED: Quota exceeded for quota metric 'Requests' and limit 'Requests per minute'

before processing 450 small audios and much before 1min, sometimes at the beggining. I tried to throttle to 15 requests per second, same result.
And while long audios are being processed, they still use a quota slot? Or just the instant when they are sent is used when computing requests per minute or per second?

Or the quota actually is 60s/900 = 0.0667s between each request?


Homogenise section, component, form and translation naming throughout

This looks like a huge PR, although it is just renaming things and a couple of small tweaks. The main objective is to rename the form sections so they are consistent and easily recognisable. These are the new names:

referrer_details

referrer_organisation

teacher_personal_details

teacher_contact_details

teacher_role

allegation_details

allegation_previous

allegation_evidence

Things renamed

View Components
Controllers
Forms
Sections
Views
Routes (the url slugs have been left the same in case that interferes with analytics)
Translations
Specs

Other changes

Shorten summary row path from for example teacher_role_duties to just duties reduces repetition
Section slugs are now generated dynamically rather than explicitly


Cannot connect to any server with mod installed on client

When I was trying to connect to my server, I got this error and disconnected:
io.netty.handler.codec.DecoderException: net.minecraft.class_148: Loading NBT data
I have to uninstall this mod in order to join servers.

Issue was related to QuickStack's sister mod: ItemFavorites. See 2Retr0/ItemFavorites#5 for more details.


fix: explicitely check if data-hover validates to false

Reference: https://github.com/zurb/foundation-sites/issues/10685

Todo: strict check for more attributes.

So check better for strict true or any type of string?

So check better for strict true or any type of string?

I don't know what solution to choose.
So I wonder, do we need to:

consider all non-false values as positivesif (this.options.hover !== false) ...

ignore invalid properties (and use defaults instead)const validOptions = filterOptions({  }, Dropdown.defaults, this.$element.data(), options);
this.options = filterOptions({ hover: Boolean, ... }, Dropdown.defaults, this.$element.data(), options);

ignore invalid properties, but transform to true for Boolean
(same code as above)

Did some changes to cover empty attr values and boolean true.

It's not only about this component. It's about how the whole framework should deal with Boolean/Empty attributes. We cannot make a manual check in each component for true || ''.

Right. Another approach should be better (the internal plugin system).
Where and how could we implement this in the best way?

@colin-marshall what do you think?

The simplest would be to use a small utility like
// foundation.util.core.js
function boolAttr(value) {
  return value === true || (typeof value === 'string' && !value.length);
}

// foundation.dropdown.js
if (boolAttr(this.option.hover)) ...

But it would be a bit dirty.
An other solution is (like given in a previous comment) a filter when initializing options. But it would be the part of a way bigger architecture change to efficiently control typing (typescript would not be a bad idea btw).

Should we plan this for v7 or how do we proceed with this PR?

I think it's not too much work to go with a little helpers in all components like:
    _init() {
        this.options = $.extend({}, Dropdown.defaults, this.$element.data(), options);
        this.options.hover = boolAttr(this.options.hover, 'hover');
    }

Or
    _init() {
        this.options = $.extend({}, Dropdown.defaults, this.$element.data(), options);
        this.options = parseBooleanAttributes(this.options, ['hover', ...]);
    }

What should we choose? @colin-marshall @kball @Owlbertz @brettsmason

@DanielRuf Personally I would go for the 3rd solution.
I can expect this to be true:
<div data-dropdown data-hover>...<div>

But not this:
Foundation.Dropdown.defaults.hover = '';

@ncoden I guess you may know best how the helper should look and work like. Do you want to and can you take care of this?

I'll take care of this, probably Saturday.

I guess we have to rebase here. On which branch should I rebase?

develop. But still, it's not a priority (v6.6.0).


how to edit csproj

Fixes #1498
/cc @Rick-Anderson @BillWagner

Added the link in the See also section, even though I think most people will be coming from that topic anyway since VS links to that from the migrate dialog window. Would have to look at the data.