s3: resolve bucket ARN in replication config references

Description of your changes
The replication destination bucket should resolve to an ARN, not a bucket name.
Fixes #745
I have:

[x] Read and followed Crossplane's contribution process.
[x] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested
With blood, sweat and tears. Fixed three other issues first.
This is a "minimal" configuration (excluding role and policy):
---
apiVersion: s3.aws.crossplane.io/v1beta1
kind: Bucket
metadata:
  annotations:
    crossplane.io/external-name: repl-src.2021-06-07
  name: repl-src
spec:
  deletionPolicy: Delete
  forProvider:
    acl: private
    locationConstraint: eu-north-1
    paymentConfiguration:
      payer: BucketOwner
    serverSideEncryptionConfiguration:
      rules:
      - applyServerSideEncryptionByDefault:
          sseAlgorithm: AES256
    versioningConfiguration:
      status: Enabled
    replicationConfiguration:
      role: arn:aws:iam::...:role/s3-replication-test # assumable by s3 svc, I just tested with an s3 admin role
      rules:
      - destination:
          storageClass: STANDARD
          bucketRef:
            name: repl-dest
        deleteMarkerReplication:
          status: Disabled
        priority: 0
        id: rule-1
        status: Enabled
---
apiVersion: s3.aws.crossplane.io/v1beta1
kind: Bucket
metadata:
  annotations:
    crossplane.io/external-name: repl-dest.2021-06-07
  name: repl-dest
spec:
  deletionPolicy: Delete
  forProvider:
    acl: private
    locationConstraint: eu-north-1
    paymentConfiguration:
      payer: BucketOwner
    serverSideEncryptionConfiguration:
      rules:
      - applyServerSideEncryptionByDefault:
          sseAlgorithm: AES256
    versioningConfiguration:
      status: Enabled

Question: Do you prefer the function returning a function for BucketARN?

/size S

Thanks for testing and reviewing this and the other PRs! I think you need a filter, or the filter PR, but I'm not certain.
I can check on monday.

cannot create or update: cannot put Bucket replication: InvalidRequest: Versioning must be 'Enabled' on the bucket to apply a replication configuration

sigh - apparently we need to re-order those calls
Also, I'm back to malformed policy unless i specify a filter, I don't understand why, because the SDK version is the same as before. Added filter to the example.


dropwizard-util still imports old jackson-annotations version

After the bump to jackson 2.8.9 in dropwizard 1.1.2, whenever i run mvn dependency:tree, I still get jackson-annotations with version 2.8.0.
Is this supposed to be?
(cut) Output from mvn dependency:tree:
[INFO] com.myapp:jar:1.0.0-SNAPSHOT
[INFO] +- io.dropwizard:dropwizard-core:jar:1.1.2:compile
[INFO] |  +- io.dropwizard:dropwizard-util:jar:1.1.2:compile
[INFO] |  |  +- com.fasterxml.jackson.core:jackson-annotations:jar:**2.8.0**:compile
[INFO] |  |  +- com.google.guava:guava:jar:21.0:compile
[INFO] |  |  +- com.google.code.findbugs:jsr305:jar:3.0.1:compile
[INFO] |  |  \- joda-time:joda-time:jar:2.9.7:compile
[INFO] |  +- io.dropwizard:dropwizard-jackson:jar:1.1.2:compile
[INFO] |  |  +- com.fasterxml.jackson.core:jackson-core:jar:2.8.9:compile
[INFO] |  |  +- com.fasterxml.jackson.core:jackson-databind:jar:2.8.9:compile
[INFO] |  |  +- com.fasterxml.jackson.datatype:jackson-datatype-guava:jar:2.8.9:compile
[INFO] |  |  +- com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.8.9:compile
[INFO] |  |  +- com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.8.9:compile
[INFO] |  |  +- com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.8.9:compile
[INFO] |  |  +- com.fasterxml.jackson.module:jackson-module-afterburner:jar:2.8.9:compile
[INFO] |  |  +- com.fasterxml.jackson.datatype:jackson-datatype-joda:jar:**2.8.9**:compile
[INFO] |  |  \- ch.qos.logback:logback-classic:jar:1.2.1:compile

Why is not the version specified in the dependency management used for dropiwzard-util as well?
The reason I'm asking is because Owasp dependency check is giving me a bit of trouble for jackson-annotations - 2.8.0  (namely CVE-2016-3720). I guess newer versions still have that, but just curious of why the old version gets used

@izrobin CVE-2016-3720 was a problem in jackson-dataformat-xml, not in jackson-annotations, so the OWASP dependency check is wrong about this one.
As for the version of jackson-annotations, it's simply the version declared in the official jackson-bom: https://github.com/FasterXML/jackson-bom/blob/jackson-bom-2.8.9/pom.xml#L25

Well do'h confusing me... Sorry! And thanks!


Ensure addresses instance variable is array

If left as null, the validation throws a warning that null is not countable. Alternative, the conditions there can be changed to check for array and then count it.

Thanks!


DeDoDe

Would it be possible to train the lightglue matcher with the DeDoDe feature extractor + descriptor? not sure if this makes sense to try or not

Hi, Kornia has a model of LightGlue trained for DeDoDeV1 (both B and G) https://github.com/kornia/kornia/blob/main/kornia/feature/lightglue.py


The email HTML templates added #6146

Description
The email HTML templates has been added to the notifications service.
The built-in templates can be replaced  with custom.
Related Issue

Fixes <issue_link>

Motivation and Context

How Has This Been Tested?

test environment: local
tested manually via inbucket

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Technical debt
[ ] Tests only (no source changes)

Checklist:

[x] Code changes
[ ] Unit tests added
[ ] Acceptance tests added
[ ] Documentation ticket raised:

@2403905 this needs an update in README.md in section Email Notification Templates.

@micbar Do we need to have the multiple html templates for each kind of message or it can be a single one?
After we move the content to the transifex the templates became very similar.

Note that the blank line 23 in readme.md (between the list items) could be removed. I cant make a suggestable commit...

Issue!
While documenting this in the admin docs, I identified the following:
The link: email/templates


Crashing At Startup

The Most Important Information Is Here:
Log:
latest.log
And It Has The Latest Version Of Chattriggers

CTJS hasn't been tested with Quilt yet. As of right now it only works with Fabric 1.19.4 and 1.20.1 (and possibly 1.20.2)


Update Dockerfile

Hi @youaredev123 Why do you want to change the dockerfile?

Sorry for that.
@wahyd4  it was my issue.


Upgrading dependencies to newer versions

New lodash version also fixes security vulnerabilities.

@RobinBuschmann Please can you merge this
It would be of great help


China network issue: Run 'source scripts/activate.sh' failed, failed to access 'chrome-infra-packages.appspot.com'

Problem
I cloned the matter repo, ready the submodules, then run 'source scripts/activate.sh', but always got error:
OSError: [Errno 101] Network is unreachable, After analyisis, I found that I can nor access 'chrome-infra-packages.appspot.com', anyone can reproduce this or meet this issue before.
Env:
Commit:
commit 203b25d94211952e52b2bcd991218151dd0c9777 (HEAD -> master, origin/master, origin/HEAD)
Author: Song GUO<EMAIL_ADDRESS>Date:   Thu Aug 5 15:11:33 2021 +0800
[cloudbuild] Add compress flag to compress built artifacts (#8781)

I checked that it seems the address 'chrome-infra-packages.appspot.com' can not work for China network. Anyone can help?

I double checked this again, finally get a proxy from NXP IT to fix this.
This may bring a trouble for Chinese customer, if we can have a default proxy in the code for China network, it will be great.
Comments?

FQ吧，老兄

@andy31415 ?

Put CIPD client in tools so that users can easily get it in their PATH.
CIPD_HOST = 'chrome-infra-packages.appspot.com'
源码中的 这个地址确实对中国用户很不友好........  要么找代理  要么翻墙...  否则没办法构建.......


feat: add containerd field to container runtime configuration

Description

Related Issue

Motivation and Context

Screenshots (if appropriate)

@yxxhero @hyy0322


Rust wrappers

Ⅰ. Describe what this PR did

增加 cluster_wrapper
优化 http_call 增加回调判断标识
增加 request_wrapper
增加 demo

Ⅱ. Does this pull request fix one issue?

#1297
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

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

Project coverage is 44.24%. Comparing base (ef31e09) to head (73b3f56).
Report is 126 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1367      +/-   ##
==========================================
+ Coverage   35.91%   44.24%   +8.33%
==========================================
  Files          69       76       +7
  Lines       11576     9895    -1681
==========================================
+ Hits         4157     4378     +221
+ Misses       7104     5183    -1921
- Partials      315      334      +19

see 91 files with indirect coverage changes


BUG? flake8 fails locally but succeeds on travis

I was happy to read in https://mne-tools.github.io/stable/contributing.htm that I can run make flake from the root to detect flake8 violations, instead of letting a Travis build run for 30 minutes before failing.
However I get lots of errors locally (lots of D400 First line should end with a period, D205 1 blank line required between summary line and description) while the Travis build succeeds.
It's a problem for me because it makes it difficult to check for non-tolerated pep8 violations locally.
Am I missing something?

Did you pip install what is the version? Sometimes flake8 updates and we have to either fix the changes or add them to the ignore list in setup.cfg (depending on difficulty and group preference).

I had a pip installation indeed, I removed flake8 with pip and reinstalled it via conda, but it still failed.
Inspecting with conda list gave me:
mathurin@mathurin-HP-EliteBook-840-G3:~/workspace/mne-python$ conda list flake8
# packages in environment at /home/mathurin/anaconda3:
#
# Name                    Version                   Build  Channel
flake8                    3.5.0                    py35_0    conda-forge
flake8-docstrings         1.0.3                     <pip>
flake8-polyfill           1.0.1                     <pip>

and removing the last 2 packages (with pip uninstall) makes it work. Not sure why.

Flake8 must have optional components. We use pydocstyle currently for
docstring checks. You could make flake8 check the same set if you want.


[MM-51025]: Fix post reminder submenu header theme issue and minor issue with dot menu shortcuts

Summary
fix post reminder submenu header theme issue
Ticket Link
Fixes https://mattermost.atlassian.net/browse/MM-51025
Related Pull Requests
NA
Screenshots

before
after

Release Note
* fix post reminder submenu header theme issue

/e2e-test

Successfully triggered E2E testing!
GitLab pipeline | Test dashboard

You don't have permissions to trigger this command.
It's only available for organization members.


fix S3 checksum calculation

While working against AWS, I realised moto was returning different checksum after copying an object and recalculating its checksum. It seems the calculation was bit wrong, as it was using hexdigest instead of the binary digest when passing the hash to the base64 encoding.
I've tried to add a test to cover all checksum calculation by using a checksum recalculation property of CopyObject.
Also fixed CopyObject behaviour, when copying a key that has a Checksum, if not asked to be recalculated, it will also copy it to the destination key. This has been verified with AWS (same with the values, so we can check that the recalculation works properly, even when not provided by boto in the first request like in test_copy_key_boto3_with_both_sha256_checksum).

Hey @bentsku, the linter has been fixed now - if you merge in the latest master, the build should pass again


iptables: Create CILIUM_TRANSIENT_FORWARD for IPv6

Commit 317a671 ("iptables: Populate CILIUM_FORWARD chain for IPv6") fixed the agent to add IPv6 counterparts to the Cilium IPv4 rules in CILIUM_FORWARD. The same method is however used to install rules in CILIUM_FORWARD and CILIUM_TRANSIENT_FORWARD. The IPv6 chain for CILIUM_TRANSIENT_FORWARD doesn't exist, resulting in the following error message:
level=error msg="Command execution failed" cmd="[ip6tables -w 5 -A CILIUM_TRANSIENT_FORWARD -o cilium_host -m comment --comment cilium (transient): any->cluster on cilium_host forward accept -j ACCEPT]" error="exit status 1" subsys=iptables
level=warning msg="ip6tables: No chain/target/match by that name." subsys=iptables
level=warning msg="failed to install transient iptables rules" error="cannot install forward chain rules to CILIUM_TRANSIENT_FORWARD: exit status 1" subsys=datapath-loader

This pull request fixes it by skipping the installation of IPv6 rules in CILIUM_TRANSIENT_FORWARD. If we want those rules, more work is required.
Fixes: https://github.com/cilium/cilium/pull/14675

test-me-please

test-me-please

test-netnext

Cilium-Ginkgo-GKE failed with known-flake https://github.com/cilium/cilium/issues/14996. K8s-1.13-Kernel-netnext failed with known flake https://github.com/cilium/cilium/issues/12511. Other jobs are green and the team review is covered. Marking as ready to merge.


Add paramiko dependency (made optional in Ansible 2.8+)

Closes https://github.com/ansible/molecule/issues/2070.
See https://github.com/ansible/ansible/blob/stable-2.8/changelogs/CHANGELOG-v2.8.rst.
See https://www.paramiko.org/installing.html.
As far as I can tell, in the traceback of #2070, it's because we choose to use the Testinfra paramiko back-end. Maybe we can investigate that choice later on. Testinfra doesn't manage these connection back-ends for us and Ansible use to give us this dependency on previous versions transitively.
Questions:

Will this conflict with Ansible < 2.8 dependencies?

I guess that is probably the right approach, even if paramiko seems to be not very well maintained anymore, being full of deprecation warnings. I guess that is the reason why recently https://github.com/ploxiln/paramiko-ng appeared as an alternative for those not willing to wait forever for a new release.

Yeah, I think it works for Molecule now. Any further comments anyone?
This fixes a critical bug which I'd like to get out of the way ASAP.

because molecule can also be used without paramiko in some cases but I will workflow it.

Yes, we need to investigate on which execution path paramiko is required in combination with testinfra and then see if we can make it an extra. Perhaps we can default to a different back-end: https://testinfra.readthedocs.io/en/latest/backends.html


ManualTestApp, ScrollView buttons don't work, Android/Native

The buttons on the ScrollView page don't do anything.
Android/Native

Assumed part of the linked issue.


DeletionPolicy common property does not seem to work for EIPAssosciation

I've been trying out humidifier by converting one of our existing CFNs to use it, as such I know that the JSON version of the CFN I have works correctly.
I was expecting this code
stack.add('AssociateEIP', Humidifier::EC2::EIPAssociation.new(
    deletion_policy: 'Retain',
    allocation_id: Humidifier::Ref.new('EIPAllocationId'),
    instance_id: Humidifier::Ref.new('Server'),
))

to generate:
               "AssociateEIP": {
			"Type": "AWS::EC2::EIPAssociation",
			"DeletionPolicy": "Retain",
			"Properties": {
				"AllocationId": { "Ref": "EIPAllocationId" },
				"InstanceId": { "Ref": "Server" }
			}
		}

As described by: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-deletionpolicy.html
Instead I get an error::
C:/tools/ruby-2.2.4-i386-mingw32/lib/ruby/gems/2.2.0/gems/humidifier-0.1.2/lib/humidifier/resource.rb:94:in `validate_property': Attempting to set invalid property for Humidifier::EC2::EIPAssociation: deletion_policy (ArgumentError)
	from C:/tools/ruby-2.2.4-i386-mingw32/lib/ruby/gems/2.2.0/gems/humidifier-0.1.2/lib/humidifier/resource.rb:50:in `update_property'
	from C:/tools/ruby-2.2.4-i386-mingw32/lib/ruby/gems/2.2.0/gems/humidifier-0.1.2/lib/humidifier/resource.rb:44:in `block in update'
	from C:/tools/ruby-2.2.4-i386-mingw32/lib/ruby/gems/2.2.0/gems/humidifier-0.1.2/lib/humidifier/resource.rb:44:in `each'
	from C:/tools/ruby-2.2.4-i386-mingw32/lib/ruby/gems/2.2.0/gems/humidifier-0.1.2/lib/humidifier/resource.rb:44:in `update'
	from C:/tools/ruby-2.2.4-i386-mingw32/lib/ruby/gems/2.2.0/gems/humidifier-0.1.2/lib/humidifier/resource.rb:14:in `initialize'

I also tried to following, but .add only takes 2 parameters.
stack.add('AssociateEIP', Humidifier::EC2::EIPAssociation.new(
    allocation_id: Humidifier::Ref.new('EIPAllocationId'),
    instance_id: Humidifier::Ref.new('Server'),
    ),
   deletion_policy: 'Retain',
)

Hi @MartinSGill,
Yeah we went back and forth on this when we were designing Humidifier. We figured it was actually confusing to put top-level attributes along with properties. Maybe that was wrong, but for now the way you would do this would be:
eip_association = Humidifier::EC2::EIPAssociation.new(
  allocation_id: Humidifier::Ref.new('EIPAllocationId'),
  instance_id: Humidifier::Ref.new('Server'),
)
eip_association.deletion_policy = 'Retain'
stack.add('AssociateEIP', eip_association)

or
stack.add('AssociateEIP', Humidifier::EC2::EIPAssociation.new(
  allocation_id: Humidifier::Ref.new('EIPAllocationId'),
  instance_id: Humidifier::Ref.new('Server'),
))
stack.resources['AssociateEIP'].deletion_policy = 'Retain'

I'm partial to the first approach since stack.resources feels like you're reaching into internals.

Ok, that helps, and thanks @kddeisz for the quick response.
Given knowledge of the actual JSON structure, would not a third parameter, a hash, on the add method remove the need for that extra assignment? Like my 2nd attempt above, just for the common parameters?
stack.add('AssociateEIP', Humidifier::EC2::EIPAssociation.new(
    allocation_id: Humidifier::Ref.new('EIPAllocationId'),
    instance_id: Humidifier::Ref.new('Server'),
    ),
   deletion_policy: 'Retain',
)

Yeah that seems to make sense. I've opened a PR with that suggestion implemented. I'll get some review on it and if other people like it I'll cut a new gem at the beginning of next week.

@MartinSGill Version 0.2.0 has this functionality, just pushed it up


[Feature Request]: Specify Egress IP/NAT

Description
Hello,
I am looking for a way to have a predictable IP for outgoing requests made from Pods (to whitelist them in the firewall of an exernal API). This is especially an issue for us, when using Cluster Auto-Scaling, as new Nodes are continously creating and destroyed (resulting in the use of various IPs).
In general this should be able to be solved using ""egress IPs"or NAT-as-a-Service" (see https://stackoverflow.com/questions/41133755/static-outgoing-ip-in-kubernete).
Is there a way to implement this using this project?

@zypriafl You are lucky, we are going to merge this very feature soon! https://github.com/kube-hetzner/terraform-hcloud-kube-hetzner/pull/611


Add kathleen config

The sombrero example runs fine. The conquest one doesn't , so probably the spack environment needs tweaking, but the conquest benchmark is itself under development, so I don't want to delay merging this system because of it. Discuss.

Yeah I wouldn't worry too much if a benchmark in a draft PR (#227) doesn't run properly. However, it seemed like there was an issue with openmpi?

Can you do a last review and merge if happy with it, @tkoskela and @giordano ? Both intel-mpi and OpenMPI work with the current versions in the spack.yaml.


Xamarin.iOS Unified support

This should be identical to the MonoTouch projects but they link against a different set of core libraries and should go into the lib\Xamarin.iOS NuGet folder.

Rx 2.3 will be shipped in the coming weeks, at which point one of the builds will be targeted to portable-net45+netcore45+wpa81+wp8+MonoAndroid1+MonoTouch1, which should support Xamarin.iOS.


Tab characters fail the parse, cryptically

The error message presented when a source file contains a tab character \t is a bit cryptic:
Error in examples/repro.ic:
Encountered unprintable character with integral value '9' encountered in source.

Ideally, tabs would be treated like regular whitespace. Barring that, we should have a better error message that (a) points to the location in the source, and (b) attempts to display the unprintable character in a more human-friendly way (ala man ascii).
Finally, the same error is output for every instance of a tab character in the source, which can be pretty overwhelming for a large file.

Parsing tab characters as normal whitespace seems more than reasonable. Feel free to spelunk in frontend/lex/lex.cc, probably starting looking at NextToken.
If not, I'll get to this in a few weeks.


Mixed string array encoding prototype

Coverage increased (+0.005%) to 98.58% when pulling 752fa6baa2d908a67fd2b565034a5c5bc95c6b8c on mixed-string-array-encoding into 8c91a254beba14fa491652bdd8b6c00e935779d0 on master.


Truncation should reset a table's id column

Per issue #66, this patch brings consistency to the Truncation strategy, in terms of the state that a table's id column is left in after a cleaning. With this change, any db's table id columns should be reset to 0 after truncation. This is the default behavior of TRUNCATE for Oracle, IBM, MSSQL, and MySQL. This commit merely mimics that behavior for SQLite and Postgres.
I don't know enough about the NoSQL dbs to guess if or how this should apply to them.

I agree that the IDs should be reset.. I'll have to work on the other adapters and strategies to make sure this is consistent.  I've merged in this change for SQLite, thanks!


Failed to call 'OTAUpdate'

zigbee2mqtt add-on version (if edge, please report commit hash):
Operating environment (HassOS, Virtual Machine, Device/platform running Hass.io):

Raspberry Pi 3 Model B+
Description of problem:
After publishing topic zigbee2mqtt/bridge/ota_update/update with payload sensor.0xccccccfffe2fb7b9 zigbee2mqtt addon log shows the following:
zigbee2mqtt:error 2020-03-17 13:06:55: Failed to call 'OTAUpdate' 'onMQTTMessage' (AssertionError [ERR_ASSERTION]: Device not found or not a device     at OTAUpdate.onMQTTMessage (/zigbee2mqtt-1.11.0/lib/extension/otaUpdate.js:64:9)     at Controller.callExtensionMethod (/zigbee2mqtt-1.11.0/lib/controller.js:329:44)     at runMicrotasks (<anonymous>)     at processTicksAndRejections (internal/process/task_queues.js:94:5))
Your entire configuration from the frontend (with sensitive fields redacted):
data_path: /share/zigbee2mqtt
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  server: 'xxx'
  user: xxx
  password: 'xxx'
serial:
  port: /dev/ttyACM0
  disable_led: true
advanced:
  pan_id: 6754
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blacklist: []
ban: []
whitelist: []
queue: {}
socat:
  enabled: false
  master: 'pty,raw,echo=0,link=/dev/ttyZ2M,mode=777'
  slave: 'tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5'
  restartdelay: 1
  initialdelay: 1
  options: '-d -d'
  log: false
zigbee_shepherd_devices: true

Your logs from Hass.io

Based on experience: drop the "sensor:"  The payload should only include the 0x....


[Sandbox] SpinKube

Application contact emails
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Project Summary
SpinKube is an open source platform for efficiently running (containerless) Spin-based WebAssembly (Wasm) applications on Kubernetes.
Project Description
SpinKube is a Kubernetes-based platform for running serverless Wasm without a container. It achieves this by combining a few technologies: A containerd-shim-spin that can directly run Spin applications from OCI Artifacts without a Container, A runtime-class-manager (formerly KWasm)  operator that manages the lifecycle of WebAssembly runtimes on Kubernetes Hosts, and the  Spin Operator which manages the configuration and lifecycle of Spin applications.
This combination provides excellent developer and operator experience when running Wasm on Kubernetes.
SpinKube provides many benefits over container-based serverless compute:

Change management - with container based deployments, patching system dependencies (such as OpenSSL) needs to happen in every image independently, which can become difficult to manage over time. With SpinKube many of these dependencies are node-local, and the runtime-class-manager provides a kubernetes-native api for patching those on running systems, without application downtime.
Rightsizing workloads - managing access to shared resources like CPU and memory correctly is difficult, which often leads to over-provisioning resources (over introducing downtime) resulting in low utilization of host resources. With SpinKube, applications consume near-zero resources at idle, and per-request resource isolation reduces the need for broad-strokes resource limits, allowing you to reduce overprovisioning of resources.
Size - containers are often bigger than needed, and often include extraneous system dependencies by default which are not required to run the application. Spin applications contain only the compiled application and its assets - and does not need per-architecture artifacts, this results in much smaller distribution units and can drastically improve scaling performance.

Org repo URL (provide if all repos under the org are in scope of the application)
https://github.com/spinkube
Project repo URL in scope of application
N/A
Additional repos in scope of the application
No response
Website URL
https://spinkube.dev
Roadmap
https://github.com/orgs/spinkube/projects/5/views/7
Roadmap context
The SpinKube Project aims to integrate WebAssembly applications seamlessly into the Kubernetes and the broader CNCF Landscape. To achieve those goals there are up-and-downstream enhancements to make across Observability, Kubernetes Node management, and scaling systems. Although not yet fully realized in the GitHub Project, the roadmap includes bringing automatic OpenTelemetry instrumentation to Wasm applications and having runtime-class-manager handle the lifecycle of installing and upgrading complex runtimes on Kubernetes nodes.
We believe in the future of WebAssembly as the next wave of efficient Serverless compute.
Contributing Guide
https://www.spinkube.dev/docs/spin-operator/contributing
Code of Conduct (CoC)
https://github.com/spinkube/governance/blob/main/CODE_OF_CONDUCT.md
Adopters
No response
Contributing or Sponsoring Org
Fermyon Technologies, Microsoft, Liquid Reply, SUSE
Maintainers file
https://github.com/spinkube/governance/issues/13
IP Policy

[X] If the project is accepted, I agree the project will follow the CNCF IP Policy

Trademark and accounts

[X] If the project is accepted, I agree to donate all project trademarks and accounts to the CNCF

Why CNCF?
The CNCF hosts a vibrant and diverse community of developers and organizations. The CNCF is able to provide a shared governance model and neutral home for the project, allowing for collaboration among various vendors and end-users, fostering the creation of a solution that delivers collective benefits to all stakeholders within the ecosystem.
Benefit to the Landscape
To expand the range of serverless platform options in the CNCF ecosystem and bring the benefits of Wasm to the Kubernetes community. Many end-users are looking for options that allow them to give their developers a serverless solution that is cost-efficient while offering excellent performance. SpinKube offers a seamless way to do this by leveraging the power of Wasm and deeply integrating it into various layers of Kubernetes for integration with the whole ecosystem.
Cloud Native 'Fit'
Landscape: Serverless
TAGs: TAG Runtime + TAG App Delivery
TAG Runtime is a natural fit for much of SpinKube, especially as the home of WG-WASM. We already integrate deeply with ContainerD through runwasi, and aim to work alongside other common runtimes too. These discussions present an opportunity to enhance the Kubernetes ecosystem, especially for lightweight environments with WebAssembly runtimes.
TAG App Delivery is also relevant to SpinKube - Our primary distribution mechanism for Wasm artifacts are OCI Artifacts, which ties into the work of wg-artifacts.
Cloud Native 'Integration'
SpinKube unites Wasm applications and Kubernetes in a way that is natural to developers who use Kubernetes today - by running applications as deployments and creating regular Kubernetes Service’s. This means you can benefit from your existing Service Meshes, O11y Pipeline’s, CI+CD, and scaling solutions while also benefiting from the portability and efficiency of WebAssembly.
SpinKube is also built on the shoulders of giants - including OCI Artifacts, runwasi in the containerd project, Kubebuilder, and OpenTelemetry.
Cloud Native Overlap
The WasmEdge, wasmCloud, knative, and krustlet projects in the CNCF ecosystem have some overlapping objectives with SpinKube. The SpinKube Project aims to integrate WebAssembly applications seamlessly into the Kubernetes and the broader CNCF Landscape.
The CNCF WasmEdge, SpinKube, and WasmCloud each use a different Wasm runtime, wasmEdge, Spin, and wasmCloud, respectively. While each of them have a differing developer experience for building applications, they each have some level of support for running their applications on Kubernetes.
According to the wasmCloud documentation, "wasmCloud is compatible with, but not dependent on, Kubernetes". With wasmCloud, Pods in a cluster are the wasmCloud "hosts" and contain N Wasm applications.
On the other hand, SpinKube was designed and built for running WebAssembly on Kubernetes - and there is a 1:1 relationship between Pods and Wasm applications. This is due to SpinKube leveraging the containerd/runwasi project to natively execute Wasm applications. Since all Wasm apps are represented as Pods, you can easily use existing tooling such as Cilium, Istio, HPA, KEDA, and Dapr with SpinKube.
WasmEdge is a runtime for embedded functions, microservices, udf, smart contracts, and IoT devices. The WasmEdge Runtime is excellent for packaging inside your software, but is more akin to WasmTime (the runtime used by Spin) than it is to Spin itself. Spin is hyper-focused on event driven serverless applications (that respond to events from HTTP requests/Queue messages/...), and SpinKube relies on that developer experience and programming model as we continue to integrate into the Cloud Native Ecosystem.
Both projects leverage runwasi to run on Kubernetes, and as such SpinKube’s runtime-class-manager not only simplifies configuring the Spin shim but can also manage the WasmEdge shim if that runtime better suits your needs, or you would like to use both.
SpinKube fits in a similar domain as serverless projects in the Cloud Native ecosystem. Like Knative, SpinKube is targeted at engineers who build serverless platforms and want a Kubernetes native experience. The defining distinction is that SpinKube applications are Wasm applications, giving them a greater level of isolation (as every request is fully isolated), fast start-up times, and simplified management of system dependencies.
Krustlet is another project in the CNCF space that runs Wasm on Kubernetes; however, it is no longer maintained - the team that developed it did go on to develop runwasi however.
Similar projects
Knative, wasmCloud, wasmEdge, krustlet
Landscape
Not yet
Business Product or Service to Project separation
N/A.
Project presentations
SpinKube Tutorial - https://www.youtube.com/watch?v=TTXAUSicj04
Project champions
No response
Additional information
No response

Congrats 🎉

I am a big +1 to this proposal. However, I believe it is significant that the namesake project at the core of SpinKube, Spin, is itself not a CNCF project. My main concern regarding this is that if there was a change of licensing for Spin, then the SpinKube collection of projects could be at risk.

This proposal is really interesting (the demos at kubecon were great), but I do find some of the statements above confusing and potentially misleading.
This opening statement describing the cloud native overlap:

The CNCF WasmEdge, SpinKube, and WasmCloud each use a different Wasm runtime, wasmEdge, Spin, and wasmCloud, respectively.

explicitly clashes with this statement in the paragraph immediately following it:

WasmEdge [...] is more akin to WasmTime (the runtime used by Spin) than it is to Spin itself.

Is Spin itself a runtime that SpinKube depends on (as suggested by the first statement), or does it use Wasmtime (as suggested by the second)?
As far as I'm aware neither Spin or wasmCloud are runtimes. According to Spin's own readme, it is a framework which uses Wasmtime, and according to this blog post,  wasmCloud also uses Wasmtime (it does not use 'wasmCloud'). If both wasmCloud and Spin use Wasmtime for their runtimes, what is the purpose of that opening statement?
I'm also not sure why this text refers to WasmEdge as 'CNCF WasmEdge' and wasmCloud as simply wasmCloud, given that they are both CNCF sandbox projects and I've generally seen wasmCloud referred to CNCF wasmCloud elsewhere.
Lastly, Taylor Thomas, one of the original developers of Krustlet that the above text refers to, recently wrote a blog post on this subject which I feel is a relevant read.

I'm also not sure why this text refers to WasmEdge as 'CNCF WasmEdge' and wasmCloud as simply wasmCloud, given that they are both CNCF sandbox projects and I've generally seen wasmCloud referred to CNCF wasmCloud elsewhere.

@boomskats that is entirely unintentional - in the place we do that I'll update it for wasmCloud too

Is Spin itself a runtime that SpinKube depends on (as suggested by the first statement), or does it use Wasmtime (as suggested by the second)?

WRT "runtime" - I'm going to try and do some wordsmithing to find a better word, but originally they (Spin and wasmCloud) were referred to as "runtimes" because from an end-user perspective they somewhat are in this context. I'm on holiday until Tuesday so that'll take a bit longer to change.

It seems a little odd to have an operator and accompanying in a foundation for a base project not in a foundation which is also reliant on a venture backed startup. Ie. It’s unclear why spin is not part of this. Given the zeitgeist and heightened sensitivity to companies changing project licenses to non oss, it seems like a non starter unless the project is also in a foundation. else cncf as a community runs the risk of being foundation laundered on accessories for a core that could end up in the same place, re non oss.
Re other foundation homes for spin, Byte code alliance projects are typically lower level runtime/spec oriented versus orchestration here. Splitting coherency for contributor organizations across foundations doesn’t seem like a good rationale either. Spin is devex and orchestration, and cncf already holds numerous projects to the goals and targeted towards wasm.
It’s not clear what benefit it has to users or community on the split but the risks to the same seem high unless spin is part of the same proposal to move to a foundation.

@devigned

I believe it is significant that the namesake project at the core of SpinKube, Spin, is itself not a CNCF project. My main concern regarding this is that if there was a change of licensing for Spin, then the SpinKube collection of projects could be at risk.

I understand that concern and it's one we're currently taking very seriously (sorry for the delay, I was on vacation post KubeCon and wanted to have some internal discussions before posting a response).
We're just as committed to keeping Spin open as we have been from the beginning with the Open Source Promise. We're currently working on defining how best to ensure that Spin will remain open for everyone.

We're just as committed to keeping Spin open as we have been from the beginning with the Open Source Promise.

I praise the Fermyon team for pledging to keep Spin open sourced in a good faith commitment and the fact that the team has a track record of building open source tools and platforms. However, we must consider the possibility of an acquisition scenario that a new ownership may change the open-source license to the closed-source model. This scenario isn't unheard of.  I am interested in hearing considerations on how to ensure that Spin will remain open in enforceable frameworks.

@angellk I believe @jsturtevant and @thomastaylor312 will be leading a discussion about Wasm OCI Artifacts in the TAG-Runtime Wasm-WG in the upcoming meeting on Tuesday April 16th at 5:00 pm CET/ 8:00 am PST meeting notes / working group details.
For a preview, I believe this doc, Wasm OCI Artifacts in containerd, tells the gist of the story.
We pursued this in https://github.com/containerd/runwasi/pull/147 so that we could fulfill the promise of Wasm workloads being architecture and OS agnostic in Kubernetes. Previous to this work, one would need to build an OCI image for a given platform / arch (linux/arm, windows/amd64, ...) etc. To target multiple, you'd have to bake multi arch images. That is not Wasm. We believed that K8s Wasm workloads should be free to run on any node in your cluster with a single artifact.
IMHO, it's one of the coolest features of the containerd Wasm shims!

Thanks @devigned - please reach out to the TAG App Delivery Artifacts Working Group to make sure they are invited / involved then since they are specifically called out in the application.

For those that are interested outside of the context of this issue, we now have an upstream tracking issue in Spin for governance definition and are making good progress in figuring out the path forwards. Thanks for your patience 💖 : https://github.com/fermyon/spin/issues/2449

Thanks @devigned - please reach out to the TAG App Delivery Artifacts Working Group to make sure they are invited / involved then since they are specifically called out in the application.

As a follow up, @devigned did an overview of the work at the last meeting on Tuesday April 12th https://docs.google.com/document/d/1E7iKPOuyA1jxPe8vDG8aPd8jtnCEbpDpCifXDvDCnA0/edit#heading=h.uylsvgzqikm

@rchincha @sabre1041 Does TAG App Delivery Artifacts WG have notes/recommendation from the meeting mentioned?

@rchincha @sabre1041 Does TAG App Delivery Artifacts WG have notes/recommendation from the meeting mentioned?

Recording from the meeting which provided a brief overview and how OCI artifacts are being used
https://www.youtube.com/watch?v=NHW5UigLXso

We're just as committed to keeping Spin open as we have been from the beginning with the Open Source Promise.

I praise the Fermyon team for pledging to keep Spin open sourced in a good faith commitment and the fact that the team has a track record of building open source tools and platforms. However, we must consider the possibility of an acquisition scenario that a new ownership may change the open-source license to the closed-source model. This scenario isn't unheard of. I am interested in hearing considerations on how to ensure that Spin will remain open in enforceable frameworks.

@endocrimes any response?

@endocrimes poke!

@endocrimes given zero movement on a foundation for spin core in the last quarter or two, the question must be asked, why the wrapper without the core in cncf? else splitting foundations is negative value for end users, and having a wrapper without a core in a foundation is the same. to be blunt, foundations aren't for laundering projects by startups, they are for fostering community around projects, imho.

@endocrimes poke!

We've actually been making some pretty meaningful progress - with Spin now having a defined governance model (https://github.com/fermyon/spin/pull/2593), as a very important step in the process of defining its future. We'll have more to share soon as that process settles in.

All - we appreciate community members support and exploration in surfacing items for technical consideration as part of sandbox applications, it allows the TOC to have a more comprehensive perspective on each projects' potential. However, in keeping with the Technical Leadership principles, we want to remind everyone to be welcoming and curious in their comments, provide feedback with courtesy, and foster respectful resolution.  Embodying the technical leadership principles as you comment on these applications directly contributes to sustaining the open, community-oriented nature of CNCF.
We've initiated an update to the Sandbox Application README to capture this guidance for anyone commenting on applications (as well as providing more information to projects on what to expect).

Review from TAG-Runtime available here.
Thank you.

Spin has now also been submitted for separate consideration as a Sandbox project - It's taken a little while and a lot of discussions to find the right path for the health of the project, and a lot of work on cementing governance 😅.
The projects are being submitted separately as they have different design goals and aspirations, even though there is some overlap between the Shim projects in SpinKube and Spin itself. I strongly feel that is the best path for both of the projects futures over a subproject-like dynamic.

Hello, q. wouldn't it make sense to donate Spin first and then just do SpinKube as an add-on to Spin? Thanks.

Moving this project application to Waiting until Spin is up for review so they can be considered and reviewed at the same time.

Apologies for the delay, but for completeness here are the recommendations following the discussion.
@endocrimes the submission was reviewed by the CNCF TOC on August 13th. The following clarifications are requested:

Would SpinKube consider supporting other WASM applications (WASMEdge, WASMCloud, ...), especially if Spin is not part of the application?
Would Spin be considered to be included in this application?

The second item was answered by @endocrimes above already.

Would SpinKube consider supporting other WASM applications (WASMEdge, WASMCloud, ...), especially if Spin is not part of the application?

We haven’t talked about this scenario in detail, but the design of the operator, runtime class manager, and the shim (the three major components of SpinKube) allow eventually supporting other execution environments.
More specifically, the operator has the concept of the “executor”, which can select the specific implementation of an executor which can control both the scheduling configuration for Kubernetes (https://github.com/spinkube/spin-operator/blob/main/api/v1alpha1/spinappexecutor_types.go), but also the actual execution of a Wasm component.
Similarly, the runtime class manager project already tracks a milestone for being able to configure all shims that KWasm can install (https://github.com/spinkube/runtime-class-manager/milestone/2)
In the near term, we are prioritizing being able to run more generic HTTP applications with SpinKube (this is also in line with the Spin roadmap, which aims to allow targeting runtimes other than the Spin runtime itself — https://github.com/fermyon/spin/blob/main/ROADMAP.md), and focusing on the operational experience for configuring and running them.
If others are interested in contributing and maintaining capabilities for SpinKube to support other Wasm applications, this is something the project can support, and we would definitely be open if it helps SpinKube users!


Removing props params from functional component

It is causing confusion with initialState defined on top, and expecting Counter component to have prop with same name.

As pointed out, this is expected. Thank you for the PR!


fix(EG-680): minor updates to support NF integration

This PR fixes:

S3Urls in the samplesheet for the uploaded files
Sets the samplesheet S3Url for the input property
Adds some missing imports for FE pages
Renders the edited settings in Step 3. in the Step 4. summary page (to update to Nick's Figma designs still)
Filters the Pipeline's sections for any that contain all hidden settings since it is not to be edited/visible in Step 3 and Step 4.

NOTE: There is still a bug with the manual editing of the input samplesheet text field in Step 3. This only gets updated and displayed properly in Step 4 after going back to Step 3, and then Step 4 again. It seems to be a storage update issue.

Renders the edited settings in Step 3. in the Step 4. summary page (to update to Nick's Figma designs still)

The styling is a bit rough here but if you're comfortable merging as-is with a view to update to the hi-fi designs soon then it's all good.

Filters the Pipeline's sections for any that contain all hidden settings since it is not to be edited/visible in Step 3 and Step 4.

This fix is already in main (although a different implementation, see: https://github.com/twobulls/easy-genomics/pull/311/files).

Thanks everyone for the review. I'll update this branch with the latest main changes.
@simondib , yeah I think I'm comfortable with the roughness of the summary of the settings for now.
We can improve it to match the Figma design in a follow up ticket.


READY: Webinars one more time now from the top

@faktorsmak @nayrudin @Delightend @johndorn Redoing the webinars icon.

:+1:


Remove password from user edit field, add validate password to user

PR to remove password field from edit user

Add validate_password? method to user
Add if validate_password? to password length validation
Remove password field from edit form
Remove password field from edit form spec
All feedback and suggestions welcome!
https://trello.com/c/33Dh5bWw/
Thanks for taking a look!

Merging now, thank you for your feedback @elle


Users pagination

Summary

Added new endpoint GET /users/pagination
Implemented getUsersPaginated in /users/controller.ts
Populated test cases for getUsersPaginated
Tested getUsersPaginated using Postman to double-check check function's correctness

Testing
Testing using Jest

Run yarn backend
Run yarn test

Testing using Postman

Starting a GET request in the form of "http://localhost:8000/users/paginations?limit=&after="
SEND and we should see the correct number of users and the correct users displayed

lgtm :)

LGTM!


Add .highligh_area() method

I believe a .highlight_area() method should be added with a start and end line index given as arguments. @rdbende Are you ok with this? The issue is the only way to currently do this is to move around the insert a ton and then use .highlight()  but it would be so much cleaner and nicer to use .highlight_area(). You might ask: "why?". Sometimes when you make a ton of inserts really fast in a method it forgets to actually highlight the area so it would be good to either:
A). Have a patch fixing the bug
or
B). Just allowing a certain area to be re-highlighted (may help fix the docstring issue)

For an example of the bug open DIP_dev and, by opening with a python file, comment out multiple lines at once and notice the first comment gets highlighted but the other #'s just become black (I can provide an image and example).


Expand the new filter search functionallity

Description
Love the addition of the new filter system. But would still like some extra filters to make my life easier to find series (mainly animes and next season animes). Very selfish request.
The filter I'm suggestion already exist when viewing different series in Jellyseerr, but I don't now how integrated they are in the system to make it searchable. My hope is it's nearly a "plug and play" for you, and not something complicated to make a reality.
Desired Behavior
New filters:

Series Type; So you can select anime (is anime the only type?)
Production Country; Sort out content from different countries
Status; Lookup future content to add with "In Production" or "Returning Series"
Next Air Date;

Additional Context
https://i.imgur.com/cjnjHcl.png
https://i.imgur.com/54Jw3SX.png
https://i.imgur.com/8a6PiUo.png
https://i.imgur.com/MjBh6tC.png
Code of Conduct

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

Do you mean like this?

anime as keyword could work
My goal with the suggestion is to get this list in Jellyseerr
https://anichart.net/Spring-2023
As they begin to air in april, it does complicate the search. For example if I put next air date in april, some still doesn't show up as they don't have a next airdate yet or yet very little information.
What they have is "Series Type: Anime" (and keyword, so thanks for that), production country and status (Production or returning series).
But when I think about it, it's impossible as even more future anime will show up in the list that is impossible to sort out.


Play Event: Investigate why secondsToLoad can report extremely high

Within the play tracking, the secondsToLoad has been reported to be very high. It is possible that the video is being loaded and not played for a long time. Maybe the user paused before first frame?
Example graph;

merged & releasing 0.0.6 to npm

accuracy improved, but I'm still getting cases where the numbers are sky-high. will need to keep looking around at specific cases when this happens... maybe it'll help me find and reproduce


raft: introduce/fix test_node_with_smaller_term_can_complete_election

contirbute to https://github.com/pingcap/raft-rs/issues/21

Rest LGTM

PTAL @BusyJay


Add bazzite logo

Bazzite is a custom image based on Fedora Silverblue and Universal Blue made to be a replacement for SteamOS on the Steam Deck.
The logo would want to look something the logos in the directory in the ublue-os/bazzite repo

logo.txt is the neofetch ascii art
logo.svg is what you want the logo to look like

I created a logo, this is what it looks like:

The progress can be found at #39. Let me know what you think :)

@nicknamenamenick @noahdotpy added in 2.9.0 :)

@nicknamenamenick @noahdotpy added in 2.9.0 :)

Thanks!


Update how-to-query-container.md

Delete repeated word "queries".

Learn Build status updates of commit 630c967:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/cosmos-db/nosql/how-to-query-container.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

#sign-off


Add BaseView docs

Complete BaseView docs

Thanks a lot for this PR and for #251, it's more beautiful with the expose wrapper <3

Thank you for the contribution 👍 This is all based on your work.


Error in the training

i have this error when i train my data : !python3 train.py --data 'data.yaml' --batch 16 --epoch 160 --model yolo_nas_m
The console stream is logged into /root/sg_logs/console.log
[2023-09-17 23:38:27] INFO - crash_tips_setup.py - Crash tips is enabled.
Train epoch 0:   0% 0/314 [00:02<?, ?it/s]
terminate called after throwing an instance of 'c10::CUDAError'
what():  CUDA error: device-side assert triggered
CUDA kernel errors might be asynchronously reported at some other API call,so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.
Exception raised from createEvent at ../aten/src/ATen/cuda/CUDAEvent.h:174 (most recent call first):
frame #0: c10::Error::Error(c10::SourceLocation, std::string) + 0x42 (0x7ba77803c7d2 in /usr/local/lib/python3.10/dist-packages/torch/lib/libc10.so)
frame #1:  + 0x267df7a (0x7ba7cb47df7a in /usr/local/lib/python3.10/dist-packages/torch/lib/libtorch_cuda_cpp.so)
frame #2:  + 0x300728 (0x7ba82df00728 in /usr/local/lib/python3.10/dist-packages/torch/lib/libtorch_python.so)
frame #3: c10::TensorImpl::release_resources() + 0x175 (0x7ba778025005 in /usr/local/lib/python3.10/dist-packages/torch/lib/libc10.so)
frame #4:  + 0x1ee619 (0x7ba82ddee619 in /usr/local/lib/python3.10/dist-packages/torch/lib/libtorch_python.so)
frame #5:  + 0x4d9ff8 (0x7ba82e0d9ff8 in /usr/local/lib/python3.10/dist-packages/torch/lib/libtorch_python.so)
frame #6: THPVariable_subclass_dealloc(_object*) + 0x292 (0x7ba82e0da2f2 in /usr/local/lib/python3.10/dist-packages/torch/lib/libtorch_python.so)

frame #24:  + 0x29d90 (0x7ba83071ad90 in /lib/x86_64-linux-gnu/libc.so.6)
frame #25: __libc_start_main + 0x80 (0x7ba83071ae40 in /lib/x86_64-linux-gnu/libc.so.6)

I thinking you are running on google colab.
Try with this: https://colab.research.google.com/drive/1VGX8FVCviclmxUu1v-DHV0lK0u74suIX?usp=sharing
I think it will solve your problem.
Please let me know your feedback.

Hi , i run it with collab but the problem is not solve

Hi @oussaifi-majdi ,
Did you give absolute path on data.yaml?
Still you are facing the issue, Can you share the data with me, If you don't have any issue.
So that I can check its the issue the data or other things.

Hi @oussaifi-majdi ,
I think issue was resolved.
So I am closing thins issue. If you have any issues.
Please re-open this issue.
Thank you.


Sumo Logic Syslog Processor

Add Syslog Processor to keep backward compatibility with current solutions
Sumo Logic Syslog Processor
Supported pipeline types: logs
The Sumo Logic Syslog processor can be used to create attribute with facility name
basing on facility code. Default facility name is syslog.
Configuration

Field
Default
Description

facility_attr
facility
The attribute name in which a facility name is going to be written

Examples
Following table shows example facility names which are extracted from log line

log
facility

<13> Example log
user-level messages

<334> Another example log
syslog

Plain text log
syslog

Configuration Example
processors:
  sumologic_syslog:
    facility_attr: testAttrName

@pmm-sumo We can iterate in that direction, but I don't have a general idea how this should work

@pmm-sumo We can iterate in that direction, but I don't have a general idea how this should work

By moving the mapping to config keys. E.g.
 attrtibute: facility_id
 mapped_attribute: facility_name
 mapping:
   0: "kernel_messages"
   1: "user-level messages"
   ...

This case is not so simple, because I need to extract value for mapping, divide it by 8 and this is my base for mapping.
Anyway, mapping processor is a good idea and it's possible that we will need it anyway :sweat_smile: :+1:

I need to extract value for mapping, divide it by 8 and this is my base for mapping.

On the other hand, the mapping keys could be multiplied by 8, I guess? :)

On the other hand, the mapping keys could be multiplied by 8, I guess? :)

It could, but it would look like pretty ugly :cold_sweat:
 mapping:
   0: "kernel_messages"
   1: "kernel_messages"
   2: "kernel_messages"
   3: "kernel_messages"
   4: "kernel_messages"
   5: "kernel_messages"
   6: "kernel_messages"
   7: "kernel_messages"


Update modules without re-instantiating the editor?

Question: Do I have to create a new Quill instance to update modules? Or is there a way to update them directly, something like:
const quill = new Quill(editorContainer, {
  modules, // <- this can change
  theme: "snow",
 });

// later on
quill.options.modules = updatedModules. // doesn't work, obviously

Context: I need to override some default keyboard bindings, and I do it through the config as suggested. When a binding needs to be updated (eg, user can change it in settings), it looks like I need to create a new Quill instance with updated config. This creates an extra hustle of saving/re-applying existing user input and selection.

One approach would be updating quill.keyboard.options directly so in binding handlers, you could read the options dynamically

One approach would be updating quill.keyboard.options directly so in binding handlers, you could read the options dynamically

Typescript would not be happy about it. There's probably  a reason for this property to be protected:
Property 'options' is protected and only accessible within class 'Module<T>' and its subclasses

I opened #4237 which seems like a separate bug to me. I wouldn't hit it, if I didn't have to re-create the editor. But it's still a bug on its own.

I'm facing the same problem, and I think I have a solution for that: https://github.com/slab/quill/discussions/4397
Happy to create a PR and make the Quill editor reconfigurable

hide/show different modules according to different condition is very common.


Argument order for ClientAPI send_XXX methods

What was wrong?
The NetworkAPI uses the following pattern for it's send methods.
def method(node_id: NodeID, endpoint: Endpoint, ...)

The ClientAPI is reversed
def method(endpoint: Endpoint, node_id: NodeID)

This is confusing.
How can it be fixed?
Change all of the methods that take both node_id and endpoint to take them in that order, with node_id first.

This was cleaned up in #113


Is there any way to generate swagger-ui endpoints?

Hi, neat project!
I just want to see if there is some way to generate the Swagger UI HTML/CSS/JS artifacts that need to be served up in order to get Swagger UI running?

Hey Alex, thanks!
I know others at Twilio spent some time getting that working in-house, but it never made it to OSS.
The mission statement of this project is to ensure it's as easy as possible to follow your specification in a type-safe and idiomatic way, while exposing the underlying routing infrastructure for whatever framework you're using. The latter being a great launching off point for integrating with other stuff (the output of a dedicated swagger-ui plugin, existing routing infrastructure that hasn't been converted to guardrail yet, etc)
I'm not opposed to it, I just don't know what that would look like.

Thanks Devon. I did a bit more digging. I think it might be better to keep this out of guardrail. There are a few scala/swagger-ui integrations  floating around, but I actually think something like this might be simpler..
Expose the openapi yaml through the server, something like:

val appRoutes: Route = PetResource.routes(...)
val docsRoutes: Route = path("openapi.yaml") {
    getFromResource("petstore.yaml", ContentType(MediaType.customWithFixedCharset("text", "vnd.yaml", `UTF-8`)))
  }
 Await.result(Http().newServerAt("<IP_ADDRESS>", 8080).bindFlow(appRoutes ~ docsRoutes), Duration.Inf)

Then just run the swagger-ui docker container and point it at the https://<my service>/openapi.yaml URL.
Spinning up an official docker container is a lot easier than messing with the various language-specific swagger-ui server implementations.
So, maybe the only thing that would be useful to implement in guardrail is the ability to copy the openapi yaml spec into src_managed. That would make it easier to serve the openapi spec from a dockerized akka-http server. Otherwise, we'd have to either remember to copy it into the container, or mount it, or would have to keep it in src/main/resources.

That's not out the realm of possibility, it would go well alongside the different kinds we support, to go alongside client, server, and models. Probably spec, though that's available for bikeshedding.
One possible benefit is that by round-tripping through the OpenAPI parser, I presume it would inline all cross-file references and omit unexpected or unusable fields. External file references was an issue we dealt with when trying to do swagger-ui, iirc.


Cannot run this project on iOS 13.3.1

The error shows:
dyld: Library not loaded: @rpath/ARCL.framework/ARCL
  Referenced from: /private/var/containers/Bundle/Application/0CA54520-ADFF-4615-834E-044598FC39FC/ARKit+CoreLocation.app/ARKit+CoreLocation
  Reason: no suitable image found.  Did find:
	/private/var/containers/Bundle/Application/0CA54520-ADFF-4615-834E-044598FC39FC/ARKit+CoreLocation.app/Frameworks/ARCL.framework/ARCL: code signature invalid for '/private/var/containers/Bundle/Application/0CA54520-ADFF-4615-834E-044598FC39FC/ARKit+CoreLocation.app/Frameworks/ARCL.framework/ARCL'

I looks the same as https://stackoverflow.com/questions/60096258/library-not-loaded-rpath-fblpromises-framework-fblpromises-ios-13-3-1/60211703#60211703. But I'd tried all the workarounds and related method. Neither of them works for me.

I am using free developer account by the way...

Got the solution from here: https://arcl-dev.slack.com/archives/C6DNBB46L/p1582464756001800


Point to submodules with https instead of ssh

Should fix https://github.com/kittykatattack/hexi/issues/16
Also, it looks like github pages clones recursively when publishing.

This should also help this guy:
https://github.com/kittykatattack/hexi/issues/17

pls merge

Thank so much for this!!!


useFetch not deduplicating requests that return an error like 404, 401 etc.

Environment

Operating System: Linux
Node Version:     v22.4.1
Nuxt Version:     3.12.4
CLI Version:      3.12.0
Nitro Version:    2.9.7
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      compatibilityDate, devtools
Runtime Modules:  -
Build Modules:    -

Reproduction
I've setup a repository with the minimal code here:
https://github.com/Jannick94/nuxt-usefetch-dedupe/blob/main/app.vue
If StackBlitz is easier, I could also create a reproduction there but I thought it was easier to test in a 'real browser'.
Describe the bug
I'm currently refactoring my code to correctly use the useFetch composable (according to the amazing video: https://www.youtube.com/watch?v=njsGVmcWviY). I discovered that performing a request to something like an profile/user API endpoint doesn't seem to correctly dedupe the request when this endpoint returns a erroneous status code like 404/401 etc.
In the reproduction's app.vue file I set up two tests, when using useFetch the correct way I see the api request in the browser networks tab. When I perform the request using useFetch the wrong way, I dont see the request in the network tab, as expected because it runs on the server and dedupes the response to the client.
Whenever the request doesn't return a erroneous status code, it does get deduped correctly. I tried setting various useFetch/fetch options like retry/retryStatusCodes but none seem to produce my expected result.
Thanks!
Additional context
No response
Logs
No response

i don't get what is it execute,
the descructuring of useFetch should be like this no?
const { data, status, error, refresh, clear } = await useFetch('yourURL')

As far as I know, execute and refresh do the same and are just aliases of eachother.
https://nuxt.com/docs/api/composables/use-fetch#return-values

Let me try to explain the issue a bit more clear:
When I have the following code directly in a script setup context:
const { data: user, execute: executeFetchUser } = useFetch('https://reqres.in/api/users/23', {
    immediate: false,
});

async function fetchUser() {
    await executeFetchUser();

    console.log('do some extra stuff after fetching user');
}

await fetchUser();

The browser console shows the following when reloading the page:

It seems the request is done twice because it returns an erroneous status code. When the request is succesful (for instance, changing the id in the url from 23 to 1), I do get the expected result.

Now when I do the request like this, and I know this is the wrong way to use useFetch, but that's how I stumbled upon this issue:
async function fetchUser() {
    const { data: user } = await useFetch('https://reqres.in/api/users/23');

    console.log('do some extra stuff after fetching user');
}

await fetchUser();

The browser console show this, it seems the request is then only done on the server, as I would have expected

Adding a manual key to the request doesn't change the resulting behavior unfortunately.

In client side, call execute, it will refetch.
https://github.com/nuxt/nuxt/blob/b161fb2c6471e7150c6e19deed3ae6f160a405c8/packages/nuxt/src/app/composables/asyncData.ts#L266
If only await useFetch, in server side fetch error, in client side, it will not refetch, it will return error.
https://github.com/nuxt/nuxt/blob/b161fb2c6471e7150c6e19deed3ae6f160a405c8/packages/nuxt/src/app/composables/asyncData.ts#L365

Fetch will automatically retry if it receives an error. You can configure this by setting retry to false (or the number of retries you want) or by configuring retryStatusCodes (if you want to customise which codes will trigger a retry).


plugins append all instance variables to response...

This seems like a good idea at first, but we just built a plugin that has a vocabulary as an instance variable - you can imagine how big the response is!
Two ideas:

provide a different mechanism for populating the 'analysis' part of the response
provide guidelines on where/how to store instance/class variables in the docs

For now, can you recommend how we should proceed?
Thx

Just make your variables private. For instance:
    def activate(self, *args, **kwargs):
        self._classifier = 5

ok, variables prefixed with an underscore are ignored? Thanks (:
We should mention that in the docs (and mention that class variables are added to http responses).

@drevicko will do. Thanks for reporting this!


Create a REST API to update a product

Create a REST API to update a product in the shopcart
The new product should have the same product_id and user_id

Approved

Thanks for reviewing. Please review the previous PR requests, too. There is an order to merge them from bottom to top.


Couldn't able to read header and footer section of doc and docx

If it's supported ? Documentation links plese. If not, is there any plans of supporting it ?

I am facing the same issue with the textract. this issue is still there. Please share any idea how to support to read the doc/docx file header and footer content.

The idea behind textract is no muss, no fuss. As such, you can get the main body text from multiple file formats with the same function, i.e. textract.process(). This being said, I can understand the need to provide acces to headers, footers for doc(x) files or the subject from an email.
How would you propose to add this functionality, while keeping the entire process straightforward? I you have any ideas, please share them or make a pull resuest and I'll happily review them.
Sent with GitHawk


Expand automount

Respectfully requesting that automount is expanded with options/flags to enable or disable automount for specific drives by guid, or possibly even by port. This would enable a much higher degree of safety when keeping drives with other filesystems, such as ext* or btrfs, plugged in as permanent fixtures of our hardware. This would help dual-booting scenarios. However, my use case is that of portable systems, such as vm's and Puppy Linux, being kept on a usb drive. My intention is to keep it plugged into my fastest usb port (usb 3.1, part of the rear io) for quick access at all times, while I can always remove it if I have to move my workflow to another station. Every time Windows boots or I insert the drive, Windows inspects the drive and asks if I want to format the drive; each time this happens there is a risk of wiping my drive by user error, and technically even a risk of Windows corrupting the drive in the event of some grave failure. I hope you'll consider this and that the implementation is relatively straightforward.

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

ID: f0a74de9-f1e4-5155-1f15-a032791a2794
Version Independent ID: 37116043-c59b-78ad-fef4-038ff4141940
Content: automount
Content Source: WindowsServerDocs/administration/windows-commands/automount.md
Product: windows-server
Technology: windows-commands
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

@chadsters88 Thank you for your product feedback. It has been forwarded to the engineering team.


Class goals

My Goals for the GitHub

[ ] Creating a New repository

[ ] Opening a  new Pull request
@yudibakshi I have made this, so you could bring

Hello

I am now looking at the issue. I am on it.


fix: refactor azureMonitor credentials

Now in azureMonitor you have to either provide both of the clientId and clientSecret together or non of them.  closes redkubes/unassigned-issues#194

I do not understand why this story is closed. Was there only one place where schema was not strict enough ?

Indeed good question. I am reopening this, but also in the light of new solution which is preferred. I propose to use:
https://stackoverflow.com/a/44399387/6144728


fingers-key without prefix?

Hello!
I Love tmux-fingers!!! But would like to get even quicker access to them!
For some common actions in tmux like switching panes I use non prefixed shortcuts (ex alt-j for jumping to lower pane).
Can I get tmux-fingers to run using alt-f?
After a grep in the tmux-fingers source code I tried adding this to my .tmux.conf:
bind-key -n M-f run-shell -b "~/.tmux/plugins/tmux-fingers/bin/tmux-fingers send-input fzf"

But I get .tmux/plugins/tmux-fingers/bin/tmux-fingers send-input fzf returned 1

Hi!
There is an undocumented workaround which is to prepend "-n" to the @fingers-key option. Like this:
set -g @fingers-key "-n M-f"

This might stop working in a feature release though, as I'm trying to figure out a way to allow more customizable key bindings in general.

Perfect! Thank you @Morantron. Works like a charm. No problem with dropping support in the future. I will notice when alt-f stops working :-)


Caused by: com.spotify.docker.client.DockerException: Get https://registry-1.docker.io/v1/repositories/library/java/tags/8: dial tcp <IP_ADDRESS>:443: i/o timeout  at com.spotify.docker.client.AnsiProgressHandler.progress(AnsiProgressHa

Expected behavior
Java Image should get downloaded
Jenkin Image get downloaded.
Actual behavior
Error
TTP code is 500 which indicates error: server error - Get https://registry-1.docker.io/v2/library/jenkins/manifests/latest: Get https://auth.docker.io/token?account=synbaas&scope=repository%3Alibrary%2Fjenkins%3Apull&service=registry.docker.io: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Information about the Issue
No image is getting downloading from docker hub, neither from docker hub through kitematic nor from through DockerFile.
Steps to reproduce the behavior

Login to kitematic
try to download any image
It will result to above error.

Timeout usually means that your connection to the server was lost. I would re-try on a solid network connection.

I guess some maintenance activity was going on aws side as it was failing with below error & <IP_ADDRESS> IP belonging to 52.3.178 - amazonaws.com.
Failed to execute goal com.spotify:docker-maven-plugin:0.2.3:build (defa
ult-cli) on project eureka: Exception caught: Get https://registry-1.docker.io/v1/repositories/library/java/tags/8: dial tcp <IP_ADDRESS>:443: i/o timeout ->
For more details please refer link,
https://forums.docker.com/t/pulling-docker-images-i-o-timeout/740/13


'deinit' is not calling ever. Serious Bug

Controllers keeps in memory stack, not deinit. Its big issue. Please check and release new version.

Hey! Any updates on this issue? Having same trouble here!

Hey, @subinspathilettu ! How are you doing man? Any news on this issue? I've tested it a couple days ago and it's still in place.

Super, its working.


neovimRequireCheckHook: Fix dependency list

Description of changes
Fix neovimRequireCheckHook for plugins that have more than two dependencies.
The error looks like this and is due to missing comma between the dependencies listed on command line:
Error detected while processing pre-vimrc command line:
E518: Unknown option: /nix/store/vk7s8q1m0f0vl2ilcyv06vyna33qnzk0-vimplugin-lua5.1-plenary.nvim-scm-1-unstable-2024-05-20

This was discovered while packaging vimPlugins.avante-nvim in https://github.com/NixOS/nixpkgs/pull/339921 and https://github.com/NixOS/nixpkgs/pull/341927.
There was already one plugin that uses neovimRequireCheckHook and has more than two dependencies (vimPlugins.image-nvim).
Not sure why that one didn't trigger the failure.
Update: Investigated - turns out it somehow passed only one dependency to neovimRequireCheckHook.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I hope these mass rebuilds are not a problem... nixpkgs-review would be nice

I hope these mass rebuilds are not a problem...

This is why we targeted staging.

nixpkgs-review would be nice

Unfortunately it is a mess to run it on staging.
I don't know if there is another solution apart from rebasing the branch on master and running nixpkgs-review from there.

I don't know if there is another solution apart from rebasing the branch on master and running nixpkgs-review from there.

this is the way. Few plugins depend on neovimRequireCheckHook so if those build you should be good. No need for a full nixpkgs-review

This is why we targeted staging.

Oh, sorry, missed that


Regex upgrade!

Made the "vm" after "ty" optional
Added support for permutations of thanks.
Here are some examples of abbreviations that are now accepted:
thanks
thank
thnx
thanx
thx

Use spaces for aligning the comments at the ends of the line, not tabs.


Fix export mesh lib break due to imported gltf has a redundant Node3D

Fixes #81850
The code is a little messy this way, but imho it's better to change the mesh lib export code than change the gltf import code. I would appreciate any feedback or alternative suggestions.

@aaronfranke does this interfere with any of your changes?

Long-term, I would like to adjust the mesh library import code so that it no longer needs a MeshInstance3D node. Instead, it should be able to just grab the mesh resources imported from the glTF file. That way it does not depend on the glTF file having any particular node structure, and can even work when the glTF file has no nodes.
Short-term, I don't have any objections to this ad-hoc fix.

Instead, it should be able to just grab the mesh resources imported from the glTF file.

Do we need a proposal for this ？

@jsjtxietian I would do this as part of https://github.com/godotengine/godot-proposals/issues/7494, allowing MeshLibrary as one of the available resources. However this rework is significant so it must wait for Godot 4.3 at the earliest. I think this PR is fine to merge for Godot 4.2 as an ad-hoc fix for now.

Short-term, I don't have any objections to this ad-hoc fix.

I assume we'll need compatibility code for this?

Is there a case where this change can cause compatibility breakage? My understanding is this PR allows one extra case where an object wouldn't have been considered legal for a mesh library.
But I do agree with the assessment that ideally all meshes in the glTF document will be used regardless of node structure.

Superseded by #87923.


Hello World reports an error while running

Hi,
I used pip install diffdrr and wanted to run the Hello world code, but it reported an error in line 26:
()
didn't match because some of the keywords were incorrect: dim

(int dim, bool keepdim)
(name dim, bool keepdim)
please help me solve this problem, thanks!

usually that’s a torch version issue
can you make sure you’re on the latest version of torch?
On Nov 19, 2024 at 07:15 -0500, asjeff @.***>, wrote:
Hi,
I used pip install diffdrr and wanted to run the Hello world code, but it reported an error in line 26:
()
didn't match because some of the keywords were incorrect: dim

(int dim, bool keepdim)
(name dim, bool keepdim)
please help me solve this problem, thanks!

—
Reply to this email directly, view it on GitHubhttps://github.com/eigenvivek/DiffDRR/issues/345, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHDA5PGSPWZ3LAD2B4HT67L2BMTWVAVCNFSM6AAAAABSB5LL5GVHI2DSMVQWIX3LMV43ASLTON2WKOZSGY3TCOJRGE2TSNI.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

thanks！I will check it

hi,
I'm using pytorch 2.1.2, i want to know only 2.5.1 can use the diffdrr 0.4.4？

not sure about all the version compatabilities, but i’m pretty sure pytorch 2.2+ works
On Nov 19, 2024 at 09:20 -0500, asjeff @.***>, wrote:
hi,
I'm using pytorch 2.1.2, i want to know only 2.5.1 can use the diffdrr 0.4.4？
—
Reply to this email directly, view it on GitHubhttps://github.com/eigenvivek/DiffDRR/issues/345#issuecomment-2485849637, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHDA5PC26WXXP4MYGXMZKVT2BNCKBAVCNFSM6AAAAABSB5LL5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBVHA2DSNRTG4.
You are receiving this because you commented.Message ID: @.***>

closing for now, feel free to reopen if you're still facing issues


repvgg_model_convert function should't have the "x", please confirm it

o = deploy_model(x)
this "x" should't have.

Please illustrate question with which line in which file.  Thank you.

mobileone.py
359 line

mobileone.py 359 line

just set arg "input" as None, you don't need it.


Promise combinators

Feature:
Add promise combinators and durable promise combinators (Could be the same) to the sdk.
List of combinators

all:

input: iterable of invocations
output: promise of a list of the fulfillment values
throws: if any of the promises throw

race:

input: iterable of invocations
output: promise with the eventual state of the first invocation that finishes

any:

input: iterable of invocations
output: fulfills when any of the input's invocations fullfils

all settled:

input: iterable of invocations
output: promise of a list with the outcome of each of the input's invocations.

https://github.com/resonatehq/resonate-sdk-py/issues/45


return pod qos in advance

If the pod's Qos has a value, return the QoS value early. For pods evicted within the descheduler, they are typically already scheduled onto nodes, and in most cases, the QoS value is already present on the pod's status. Therefore, it is unnecessary to start the determination process from scratch.

/ok-to-test

/lgtm
/assign @ingvagabund

/approve


Edit and expand SOAP template comments

See https://outsystemsrd.atlassian.net/browse/TK-10028 for more information.

@jonathanalgar , I checked the zip file, but I don't know about a couple of lines in the Reference. cs under CalculatorWebServiceSoapClient, Are they being interpreted as comments or code?

/// The endpoint to configure
/// The client credentials

@jonathanalgar , I checked the zip file, but I don't know about a couple of lines in the Reference. cs under CalculatorWebServiceSoapClient, Are they being interpreted as comments or code?

/// The endpoint to configure
/// The client credentials

Comments. You can learn about how param tags can be used in XML C# comments here, for example. But I didn't edit the reference.cs file in any case—it is automatically generated.
From the perspective of zip the important question is if the reference.cs is the same as the original: I believe it is, but please double-check.

@jonathanalgar , I checked the zip file, but I don't know about a couple of lines in the Reference. cs under CalculatorWebServiceSoapClient, Are they being interpreted as comments or code?

/// The endpoint to configure
/// The client credentials

Comments. You can learn about how param tags can be used in XML C# comments here, for example. But I didn't edit the reference.cs file in any case—it is automatically generated.
From the perspective of zip the important question is if the reference.cs is the same as the original: I believe it is, but please double-check.

I did check.  They are comments.

Approved by @OSmvicente on Slack 🚀


updated minKubeVersion as 1.19 in operator csv #47503

https://github.ibm.com/IBMPrivateCloud/roadmap/issues/47503

/lgtm


Add support for markdown "checkboxes"

When submitting an issue here on github, I am able to make lists with "checkboxes" which can be checked/unchecked.
For example, using:
- [ ] an example issue
- [x] a completed issue

will output:

[ ] an example issue
[x] a completed issue

Can a similar feature be added (without the fancy rendering)?
Where one can insert a "checkbox" using a keyboard shortcut, and then check/uncheck it using another?

Example screenshot:

I've had this on my personal list as well! I like it a lot but haven't looked into it yet as it's changing text content. If it's doable in a non-hacky way, I'll try and add it.

Any suggestions for the keyboard shortcut(s)?

Maybe something like cmd + . or cmd + /?

I like the idea of spacebar to toggle, that keeps it consistent with html checkboxes. however that should only work when you are between [ ]. Would you expect cmd+. to work wherever you are on a line?

Just pushed this to the checkbox-support branch. if you press ctrl + /, it will add an empty checkbox to the beginning of the current line (prepended by any whitespace you already have, so indented lists work) . pressing ctrl + / again will toggle the checkbox to checked and unchecked.

What this doesn't do is append the checkbox after any "list" items such as * or -, it will instead add the checkbox before the list item but after any whitespace at the beginning of the line. To me this looks better (and it's less code to write and maintain, so double win). Let me know what you think @evolutionxbox!

I really like this. I'm going to checkout that branch later today and have a play around. Personally I think you've got a good approach.

Just pushed support for interaction with selections too: select multiple lines and press ctrl + / and it will add/toggle checkboxes on all of them.

I'm using FromScratch as my to-do scratchpad (it feels like a much nicer macOS Stickies), and I'm really looking forward to this in stable. 👍
Supporting  list-style checkboxes may be useful for those who want Markdown in the end, but I think I can live without them.

What are list-style checkboxes?

The GitHub flavored Markdown syntax of:
- [ ] one
- [ ] two
    - [ ] three
- [x] four
- [ ] five

...which they render as so:

[ ] one
[ ] two

[ ] three

[x] four
[ ] five

Ah, yes. We're not going to render checkboxes as html, they will remain plain text. IMO the dash is superfluous:
[ ] one
[ ] two
    [ ] two point one
[ ] three

Reads just as well, right? See my comment here for rationale: https://github.com/Kilian/fromscratch/issues/36#issuecomment-258973814

@Kilian yeah I agree with you. The checkboxes do not need to render.

Yes, it reads fine, but isn't great for copy/pasting into Markdown files.
And just to be clear, I don't think FromScratch should render them as HTML — I'd just personally prefer - [ ] one over [ ] one.
That said, it's perfectly fine for FromScratch not to bother with that, as it's not a Markdown editor (and doesn't want to be one). If I end up needing something like this, processing text is easy enough to script.

Just merged this back to master, will be in 1.3.0!


Missing casting from LiveEvent

https://github.com/hadilq/LiveEvent/blob/027ac57d093c9b8f9fddeb3ef8517de2b8b65534/lib/src/main/java/com/hadilq/liveevent/LiveEvent.kt#L44
Shouldn't this line be
if (observer is ObserverWrapper && observers.remove(observer)) {
Got lint error here

Thanks @SamYStudiO for your suggestion.
I am running ./gradlew check to see the lint report in lint-results.html file, but there's no such error! What is the version of gradle you are using?
However, I don't get why lint should give an error on this! If observer is not an instance of ObserverWrapper then it would not get removed, because observers could not hold it in the first place! Can you explain a possible flaw there? Thanks!

Thanks @SamYStudiO I am updating the versions, so probably see the lint error soon :D
Also I'll fix it anyway and publish an update today, if everything goes well.


Deploying of sample JavaScript Function throws this error

Repro steps:

Action: azureFunctions.deploy
Error type: 403
Error Message: Failed with code "403".
Version: 0.20.2
OS: win32
Product: Visual Studio Code
Product Version: 1.42.1
Language: en

Call Stack
extension.bundle.js:218:502569extension.bundle.js:218:502569
s extension.bundle.js:218:111756
s extension.bundle.js:164:25792
extension.bundle.js:164:27036extension.bundle.js:164:27036
o extension.bundle.js:164:674848
extension.bundle.js:164:24705extension.bundle.js:164:24705
$._callback extension.bundle.js:1:635041
$.t._callback.t.callback.t.callback extension.bundle.js:194:5590
$.emit events.js:200:13
$.<anonymous> extension.bundle.js:194:18450
$.emit events.js:205:15
IncomingMessage.<anonymous> extension.bundle.js:194:17282
Object.onceWrapper events.js:288:20
IncomingMessage.emit events.js:205:15
endReadableNT _stream_readable.js:1154:12
processTicksAndRejections task_queues.js:84:9

As a workaround please try the "Advanced" option when creating a function app. Your subscription likely doesn't have permissions for something. Closing as duplicate of https://github.com/microsoft/vscode-azurefunctions/issues/1583


Duplicate palettes

Issues

#63

Changes

Add button to duplicate palette inside list view

:tada: This PR is included in version 1.3.0-staging.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Wrong values in the cloud events

Hey, I was working w/ the cloud variables but scratchattach returns me values that either were not set for minutes or don't even appear in my Cloud Monitor (ignore the "Changed" lines):

What cloud events were you using? (scratch3.CloudEvents or scratch3.WsCloudEvents)

scratchattach's cloud events receive data from the clouddata API. According to Scratch's clouddata API, the variable Request was set to the values<PHONE_NUMBER>15, 1119 and 14: https://clouddata.scratch.mit.edu/logs?projectid=877118077&limit=30&offset=0

Are you sure the project id in your code is correct? The clouddata API should not differ from the cloudmonitor


vite-typescript template conflict with "allowImportingTsExtensions":true

Pre-flight checklist

[X] I have read the contribution documentation for this project.
[X] I agree to follow the code of conduct that this project uses.
[X] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Electron Forge version
7.2.0
Electron version
v29.0.0
Operating system
Win10 x64 Pro 22H2 19045.3208
Last known working Electron Forge version
7.2.0
Expected behavior
✔ Checking your system
✔ Locating application
✔ Loading configuration
✔ Preparing native dependencies
✔ Running generateAssets hook
......
Actual behavior
✔ Checking your system
✔ Locating application
✖ Loading configuration
› Unable to use specified module loaders for ".ts".
◼ Preparing native dependencies
◼ Running generateAssets hook
An unhandled rejection has occurred inside Forge:
Error: Unable to use specified module loaders for ".ts".
at Object.exports.prepare (C:\Users\XLin0mu\AppData\Roaming\npm\node_modules@electron-forge\cli\node_modules\rechoir\index.js:58:11)
at exports.default (C:\Users\XLin0mu\AppData\Roaming\npm\node_modules@electron-forge\cli\node_modules@electron-forge\core\src\util\forge-config.ts:117:17)
at async Task.task (C:\Users\XLin0mu\AppData\Roaming\npm\node_modules@electron-forge\cli\node_modules@electron-forge\core\src\api\start.ts:63:29)
at async Task.run (C:\Users\XLin0mu\AppData\Roaming\npm\node_modules@electron-forge\cli\node_modules\listr2\dist\index.cjs:978:11)
at async C:\Users\XLin0mu\AppData\Roaming\npm\node_modules@electron-forge\cli\node_modules\p-map\index.js:57:22
Steps to reproduce

Execute command npm init electron-app@latest DLR_SA -- --template=vite-typescript.
Add this item to tsconfig.json:

{
"compilerOptions": {
//...
"allowImportingTsExtensions": true,
"noEmit": true,
//whether add "noEmit" at here won't make any different.
//...
}

Run forge start script. npm run start or electron-forge start, givensame error message exclude the path.

Additional information
Full tsconfig.json file (which one make error):
{
  "compilerOptions": {
    "target": "ESNext",
    "module": "commonjs",
    "allowJs": true,
    "skipLibCheck": true,
    "esModuleInterop": true,
    "noImplicitAny": true,
    "sourceMap": true,
    "baseUrl": ".",
    "outDir": "dist",
    "moduleResolution": "node",
    "resolveJsonModule": true,

    "noEmit": true,
    "allowImportingTsExtensions": true,
  },
  "include": ["src"]
}

Want to share my experience with this error here;
I was running into the same error Error: Unable to use specified module loaders for ".ts". but I was not using the configuration above. What ended up being the cause was that I had removed ts-node from my package,json. When I put ts-node back the error was resolved and the app started as expected.

The CJS build of Vite's Node API is deprecated. See https://vitejs.dev/guide/troubleshooting.html#vite-cjs-node-api-deprecated for more details.

I get that when I run npm run package 😀 (although unrelated??) it shares my sentiment

@jpmckown do you use ts-node in the start script, in vite config or somewhere?

@jpmckown do you use ts-node in the start script, in vite config or somewhere?

It's been a while but as I recall, ts-node is a dependency for Electron itself. So, the short answer is no, I think. Just leave the scripts as-is when generated by the forge.

Thanks, it worked.
ts-node should be added as optional peer dependency of Electron.


tests: samples/boards/stm32/power_mgmt/serial_wakeup failed on mec15xxevb_assy6853

The daily twister tester will run samples/boards/stm32/power_mgmt/serial_wakeup on mec15xxevb_assy6853 and got a failure
Please also mention any information which could help others to understand
the problem you're facing:

What target platform are you using? -> mec15xxevb_assy6853

What have you tried to diagnose or workaround this issue?
Check the readme.rst in the test folder, and found this test case seems to be dedicated to stm32. Regarding to mec15xxevb_assy6853 has its own power_mgmt test case, this case should add "platform_alow: stm32" in the sample.yaml.

Is this a regression? If yes, have you been able to "git bisect" it to a
specific commit?

Not a regression. It looks like a small bug in the commit f5378424f7f492a8ae0d173a015bc1186fcc7127.

To Reproduce
Steps to reproduce the behavior:
twister --hardware-map $HOME/mec1.file --device-testing -T samples/boards/stm32/power_mgmt/serial_wakeup/ -vv
Expected behavior
The test should be skipped
Impact
1 test case fail in daily test
Logs and console output
DEBUG   - DEVICE: *** Booting Zephyr OS build zephyr-v3.1.0-3848-g02b23f3733e0  ***
DEBUG   - DEVICE: Device ready
DEBUG   - DEVICE: Device is not wakeup capable

Environment (please complete the following information):

OS: (e.g. Linux, MacOS, Windows): Ubuntu 20.04
Toolchain (e.g Zephyr SDK, ...) 0.14.1
Commit SHA or Version used :02b23f3733e0e052775a7480ff1e7f6f7971f4e6

@erwango Is this test case for STM32 only?
commit f5378424f7f492a8ae0d173a015bc1186fcc7127
Author: Erwan Gouriou<EMAIL_ADDRESS>Date:   Tue Jun 28 16:54:49 2022 +0200

    samples: boards: stm32: Add a serial wakeup sample

    Add a sample to demonstrate use of (LP)U(S)ART with wakeup capability
    This sample is provided with 2 configurations
    - nucleo_wb55rg: Basic configuration that could be exercised in CI
    - stm32l562e_dk: "Full feature" configuration that require some set up
    configuration (be able to display console from lpuart) and allows to
    achieve lowest power consumption.

    Signed-off-by: Erwan Gouriou<EMAIL_ADDRESS>

This is also seen on nucleo_wl55jc and b_u585i_iot02a and others (stm32L5, stm32L4, stm32G0 boards)


Fixed compilation errors on Linux, fixed progression message and added --help flag

Flushing the progression message fixed the program not displaying it in a Linux terminal.
Added `--help`` flag for easier use (current version only print the message when there's no argument given to the program).
Added includes where it was needed and change the cases in the switch, both to compile flawlessly (and no more error) with clang-15 and gcc-13.


chore: Add Dependabot integration for automated dependency updates

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
Adds Dependabot integration to provide automated dependency updates.
Which issue(s) this PR fixes:

Requirements:

[x] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 47.046%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
223

Relevant Lines:
474

💛  - Coveralls


Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)

I am building a CNN+RNN model for speech recognition. But it seems a lot problems with MXNet's rnn API?
I followed the rnn example and trained my network finally after someone's help.
But when it comes to the predict step, some issues occur:
Here are my codes:
x = mx.io.NDArrayIter(data=Pxxs_arr, label=None, batch_size=10, shuffle=False, last_batch_handle='pad')
pred = self.model.predict(x)
hint: Pxx.shape = (10, 1, x, y)
(batch_size, chnnel, w, h)
Then:
Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)
Since My codes is work pretty well in my single cnn network experienments:
pred = self.model.predict(Pxx)
hint: Pxx is a numpy array with shape(1, 1, x, y)
So, what's the true skills of MXNet's RNN API?
here are my codes of the symbol(CNN + RNN):
`data = mx.symbol.Variable('data')
rnn_h_init = mx.sym.SwapAxis(mx.sym.Variable('LSTM_init_h'),
dim1=0, dim2=1)
rnn_c_init = mx.sym.SwapAxis(mx.sym.Variable('LSTM_init_c'),
dim1=0, dim2=1)
rnn_params = mx.sym.Variable('LSTM_bias')
print_infer_shape(data)
conv1 = mx.symbol.Convolution(data=data, kernel=(3, 5), num_filter=64, stride=(1, 4))
bn1 = mx.symbol.BatchNorm(data=conv1, fix_gamma=False, momentum=0.9, eps=1e-5)
relu1 = mx.symbol.Activation(data=bn1, act_type="relu")
pool1 = mx.symbol.Pooling(data=relu1, pool_type="max",
kernel=(2, 2), stride=(2, 2))
print_infer_shape(pool1)
conv2 = mx.symbol.Convolution(data=pool1, kernel=(3, 3), num_filter=128, stride=(1, 2))
bn2 = mx.symbol.BatchNorm(data=conv2, fix_gamma=False, momentum=0.9, eps=1e-5)
relu2 = mx.symbol.Activation(data=bn2, act_type="relu")
pool2 = mx.symbol.Pooling(data=relu2, pool_type="max",
kernel=(2, 2), stride=(2, 2))
print_infer_shape(pool2)
conv3 = mx.symbol.Convolution(data=pool2, kernel=(3, 3), num_filter=256, stride=(1, 2))
bn3 = mx.symbol.BatchNorm(data=conv3, fix_gamma=False, momentum=0.9, eps=1e-5)
relu3 = mx.symbol.Activation(data=bn3, act_type="relu")
pool3 = mx.symbol.Pooling(data=relu3, pool_type="max",
kernel=(1, 2), stride=(1, 2))
print_infer_shape(pool3)
conv4 = mx.symbol.Convolution(data=pool3, kernel=(2, 2), num_filter=512, stride=(1, 1))
bn4 = mx.symbol.BatchNorm(data=conv4, fix_gamma=False, momentum=0.9, eps=1e-5)
relu4 = mx.symbol.Activation(data=bn4, act_type="relu")
print_infer_shape(relu4)
reshape1 = mx.symbol.Reshape(data=relu4, shape=(10, 512, -1))
swapaxis1 = mx.symbol.SwapAxis(data=reshape1, dim1=0, dim2=1)
swapaxis2 = mx.symbol.SwapAxis(data=swapaxis1, dim1=0, dim2=2)
bilstm = mx.symbol.RNN(data=swapaxis2, bidirectional=False, num_layers=3, mode='lstm',
state_size=128, state_outputs=False, state=rnn_h_init,
state_cell=rnn_c_init, parameters=rnn_params)
print_infer_shape(bilstm)
swapaxis3 = mx.symbol.SwapAxis(data=bilstm, dim1=0, dim2=1)
print_infer_shape(swapaxis3)
mean_state = mx.symbol.sum(data=swapaxis3, axis=1) / 177.
print_infer_shape(mean_state)
fc1 = mx.symbol.FullyConnected(data=mean_state, num_hidden=num_classes)
neonscript_withrnn = mx.symbol.SoftmaxOutput(data=fc1, label=label, name='softmax')`

This issue is closed due to lack of activity in the last 90 days. Feel free to reopen if this is still an active issue. Thanks!


Select which tab to hide it's title

added tabKeyToHideLabel string that should include the tabs names to hide in one string, and check for their existence using tabKeyToHideLabel.includes(route.key)

This change is

Hi @Xdabier, is this PR meant for my fork repo of react-navigation-tab? or the main react-navigation-tab repo?

hi @xkawi sorry for the mistake, I was actually pulling to my fork, and somehow ended up pulling to yours I guess it happened because I've mistaken my name with yours somehow.. I'm sorry again.