my game rewrite isnt working properly on penguinmod

Expected Behavior
menus and text should be normal and clones should be 24
Actual Behavior
clones are 6 and text and buttons are missing
Steps to Reproduce
open my sb3 in penguinmod
Operating System and Browser
Windows 11, Microsoft Edge

epic scratch import failure :yawning_face:

also my bro why does it need reiterating that we cant see what your save file is

so should I pass the sb3 (pls dont send it anywhere)

https://files.catbox.moe/b87vzf.sb3 ahhhhh

I figured out the problem, the extendable blocks extension isnt working right on penguinmod for some reason cuz I was using switch and case from that

great that you found the issue, but why where you using an external switch case block when pm has one built in?

its cuz its from when the game was in turbowarp lol

skibidi gyatt is rizzler ohio!

how did you know what goes on in my head every night

how did you know what goes on in my head every night

looky guess


Missing shell output in Kubernetes based environment

Jenkins and plugins versions report

Environment

Jenkins: 2.346.1
OS: Linux - 5.4.196-108.356.amzn2.x86_64
---
Parameterized-Remote-Trigger:<IP_ADDRESS>
ace-editor:1.1
ansicolor:1.0.1
antisamy-markup-formatter:2.7
anything-goes-formatter:1.0
apache-httpcomponents-client-4-api:4.5.13-1.0
authentication-tokens:1.4
badge:1.9.1
basic-branch-build-strategies:1.3.2
blueocean:1.25.5
blueocean-autofavorite:1.2.5
blueocean-bitbucket-pipeline:1.25.5
blueocean-commons:1.25.5
blueocean-config:1.25.5
blueocean-core-js:1.25.5
blueocean-dashboard:1.25.5
blueocean-display-url:2.4.1
blueocean-events:1.25.5
blueocean-git-pipeline:1.25.5
blueocean-github-pipeline:1.25.5
blueocean-i18n:1.25.5
blueocean-jwt:1.25.5
blueocean-personalization:1.25.5
blueocean-pipeline-api-impl:1.25.5
blueocean-pipeline-editor:1.25.5
blueocean-pipeline-scm-api:1.25.5
blueocean-rest:1.25.5
blueocean-rest-impl:1.25.5
blueocean-web:1.25.5
bootstrap5-api:5.1.3-7
bouncycastle-api:2.26
branch-api:2.1046.v0ca_37783ecc5
caffeine-api:2.9.3-65.v6a_47d0f4d1fe
checks-api:1.7.4
cloudbees-bitbucket-branch-source:773.v4b_9b_005b_562b_
cloudbees-disk-usage-simple:0.10
cloudbees-folder:6.729.v2b_9d1a_74d673
command-launcher:1.2
commons-lang3-api:<IP_ADDRESS>
commons-text-api:1.9-9.v39a_53e2e0343
configuration-as-code:1466.v2d4119502006
copyartifact:1.46.4
credentials:1139.veb_9579fca_33b_
credentials-binding:523.vd859a_4b_122e6
display-url-api:2.3.6
docker-commons:1.19
docker-workflow:1.29
dtkit-api:3.0.1
durable-task:496.va67c6f9eefa7
echarts-api:5.3.3-1
email-ext:2.89
extended-read-permission:3.2
favorite:2.4.1
font-awesome-api:6.1.1-1
git:4.11.3
git-client:3.11.0
github:1.34.4
github-api:1.303-400.v35c2d8258028
github-branch-source:1656.v77eddb_b_e95df
groovy-postbuild:2.5
handlebars:3.0.8
handy-uri-templates-2-api:2.1.8-22.v77d5b_75e6953
hashicorp-vault-plugin:351.vdb_f83a_1c6a_9d
htmlpublisher:1.30
http_request:1.15
jackson2-api:2.13.3-285.vc03c0256d517
javax-activation-api:1.2.0-3
javax-mail-api:1.6.2-6
jaxb:2.3.6-1
jdk-tool:1.0
jenkins-design-language:1.25.5
jjwt-api:0.11.5-77.v646c772fddb_0
job-dsl:1.80
jobConfigHistory:1155.v28a_46a_cc06a_5
jquery-detached:1.2.1
jquery3-api:3.6.0-4
jsch:<IP_ADDRESS>
junit:1119.1121.vc43d0fc45561
kubernetes:3651.v908e7db_10d06
kubernetes-cli:1.10.3
kubernetes-client-api:5.12.2-193.v26a_6078f65a_9
kubernetes-credentials:0.9.0
ldap:2.10
locale:180.v207501dff9b_a_
lockable-resources:2.15
mailer:414.vcc4c33714601
matrix-auth:2.6.11
matrix-project:772.v494f19991984
metrics:<IP_ADDRESS>
momentjs:1.1.1
monitoring:1.91.0
okhttp-api:4.9.3-105.vb96869f8ac3a
opentelemetry:2.9.0-rc1
permissive-script-security:0.7
pipeline-build-step:2.18
pipeline-graph-analysis:195.v5812d95a_a_2f9
pipeline-groovy-lib:593.va_a_fc25d520e9
pipeline-input-step:449.v77f0e8b_845c4
pipeline-milestone-step:101.vd572fef9d926
pipeline-model-api:2.2097.v33db_b_de764b_e
pipeline-model-definition:2.2097.v33db_b_de764b_e
pipeline-model-extensions:2.2097.v33db_b_de764b_e
pipeline-rest-api:2.24
pipeline-stage-step:293.v200037eefcd5
pipeline-stage-tags-metadata:2.2097.v33db_b_de764b_e
pipeline-stage-view:2.24
pipeline-utility-steps:2.13.0
plain-credentials:1.8
plugin-util-api:2.17.0
popper2-api:2.11.5-2
prometheus:2.0.10
pubsub-light:1.16
robot:3.2.0
role-strategy:3.2.0
scm-api:608.vfa_f971c5a_a_e9
script-security:1175.v4b_d517d6db_f0
simple-theme-plugin:103.va_161d09c38c7
snakeyaml-api:1.30.2-76.vc104f7ce9870
sse-gateway:1.25
ssh-agent:295.v9ca_a_1c7cc3a_a_
ssh-credentials:291.v8211e4f8efb_c
ssh-slaves:1.821.vd834f8a_c390e
sshd:3.0.3
structs:318.va_f3ccb_729b_71
timestamper:1.18
token-macro:293.v283932a_0a_b_49
trilead-api:1.57.v6e90e07157e1
variant:1.4
windows-slaves:1.8.1
workflow-aggregator:590.v6a_d052e5a_a_b_5
workflow-api:1188.v0016b_4f29881
workflow-basic-steps:969.vc4ec3e4854b_f
workflow-cps:2746.v0da_83a_332669
workflow-durable-task-step:1174.v73a_9a_17edce0
workflow-job:1203.v7b_7023424efe
workflow-multibranch:716.vc692a_e52371b_
workflow-scm-step:400.v6b_89a_1317c9a_
workflow-step-api:625.vd896b_f445a_f8
workflow-support:833.va_1c71061486b_
xunit:3.1.0

What Operating System are you using (both controller, and any agents involved in the problem)?
Linux, Kubernetes on AWS
Reproduction steps

Configure a K8S connection via the Kubernetes Plugin settings
Configure OpenTelemetry plugin for Store pipeline logs In Elastic and visualize logs both in Elastic and through Jenkins
Launch a simple command

podTemplate {
    node(POD_LABEL) {
        sh('ls -la')
    }
}

Expected Results
The output of the ls -la should be visible:
+ ls -la
total 0
drwxr-xr-x 2 jenkins jenkins  6 Jul 12 18:47 .
drwxr-xr-x 4 jenkins jenkins 34 Jul 12 18:47 ..

Actual Results
Output of shell is not visible inside the log
Anything else?
Log combination with native instance & Kubernetes based.
Build-In Node
node() {
    sh('ls -la')
}

Don't store pipeline logs in Elastic 🆗

Running on [Jenkins](***) in /var/jenkins_home/workspace/test
+ ls -la
total 8
drwxrwsr-x 2 jenkins jenkins 4096 Jul  5 16:52 .
drwxrwsr-x 5 jenkins jenkins 4096 Jul  5 16:52 ..
Finished: SUCCESS

Store pipeline logs In Elastic and visualize logs both in Elastic and through Jenkins 🆗

[Pipeline] Start of Pipeline
[Pipeline] node
Running on Jenkins in /var/jenkins_home/workspace/test
[Pipeline] {
[Pipeline] sh
+ ls -la
total 8
drwxrwsr-x 2 jenkins jenkins 4096 Jul  5 16:52 .
drwxrwsr-x 5 jenkins jenkins 4096 Jul  5 16:52 ..
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: SUCCESS

Kubernetes based
podTemplate {
    node(POD_LABEL) {
        sh('ls -la')
    }
}

Don't store pipeline logs in Elastic 🆗

Created Pod: cmo-prod.vni-pmt-ci vni-pmt-ci/test-50-btvzh-v5q6d-slpx4
Agent [test-50-btvzh-v5q6d-slpx4](***) is provisioned from template test_50-btvzh-v5q6d
Running on [test-50-btvzh-v5q6d-slpx4](***) in /home/jenkins/agent/ws/test
+ ls -la
total 0
drwxr-xr-x 2 jenkins jenkins  6 Jul 12 18:47 .
drwxr-xr-x 4 jenkins jenkins 34 Jul 12 18:47 ..
Finished: SUCCESS

Store pipeline logs In Elastic and visualize logs both in Elastic and through Jenkins 🔥

[Pipeline] Start of Pipeline
[Pipeline] podTemplate
[Pipeline] {
[Pipeline] node
Created Pod: cmo-prod.vni-pmt-ci vni-pmt-ci/test-49-j06nk-1t4ft-0dphk
Agent test-49-j06nk-1t4ft-0dphk is provisioned from template test_49-j06nk-1t4ft
Running on test-49-j06nk-1t4ft-0dphk in /home/jenkins/agent/ws/test
[Pipeline] {
[Pipeline] sh
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // podTemplate
[Pipeline] End of Pipeline
Finished: SUCCESS

The log seems to never reached Elastic - also with the Store pipeline logs In Elastic and visualize logs exclusively in Elastic option the sh output is not visible.
[Pipeline] Start of Pipeline
[Pipeline] podTemplate
[Pipeline] {
[Pipeline] node
Created Pod: cmo-prod.vni-pmt-ci vni-pmt-ci/test-49-j06nk-1t4ft-0dphk
Agent test-49-j06nk-1t4ft-0dphk is provisioned from template test_49-j06nk-1t4ft
Running on test-49-j06nk-1t4ft-0dphk in /home/jenkins/agent/ws/test
[Pipeline] {
[Pipeline] sh
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // podTemplate
[Pipeline] End of Pipeline
Finished: SUCCESS

Thanks @timmjd for the detailed report.
@jglick are you aware of such a limitation of JEP 210? A limitation where the shell console of the Jenkins Kubernetes Plugin would not be routed to the h.m.BuildListener provided by the o.j.p.w.log.LogStorage?
@kuisathaverat  @v1v can we test on our environment?

Good catch @kuisathaverat , you rock!
@timmjd can you verify the OTLP endpoint you configured in the Jenkins OpenTelemetry plugin configuration are also valid from the Kubernetes build agents?

Damn, that was the missing thing.
Our job runs inside a separate namespace of the cluster - and I only used the local DNS http://default-elasticsearch-ccif-ot-collector:4317 instead of the global one http://default-elasticsearch-ccif-ot-collector.vni-pmt.svc.cluster.local:4317.
I finally exposed the OTLP endpoint via a nginx based ingress - should now work for OnPrem and in cluster.
During debugging, I also found the error inside the JNLP agent:
SEVERE: Failed to export logs. The request could not be executed. Full error message: default-elasticsearch-ccif-ot-collector: Name or service not known
Not sure if possible, but sending this information to the server would have make it more obvious.

are you aware of such a limitation of JEP 210

#304 IIUC? :eyes:

sending this information to the server would have make it more obvious

The kubernetes plugin does not stream agent log messages (like stderr from java -jar agent.jar) to the build log. Would probably be helpful to do so. It did stream K8s events pertaining to the pod to the build log, but this was removed in https://github.com/jenkinsci/kubernetes-plugin/pull/1192. CC @Vlatombe


Feature: Object store configuration

SDK
Python
Description
I am occasionally running into issues like this when indexing:
File "/app/lance/python/python/lance/dataset.py", line 1075, in create_index
    self._ds.create_index(column, index_type, name, replace, kwargs
OSError: LanceError(IO): Generic S3 error: Error after 0 retries in 34.07378292s, max_retries:10, retry_timeout:180s, source:error sending request for url (https://<s3 path...>/data/01685d89-40c6-46a3-bdb9-fdafffd2d53c.lance): operation timed out, /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/core/src/convert/mod.rs:716:9

I think what I'd want is the ability to specify a custom RetryConfig to configure retry timeouts. Happy to pick this up for the Python SDK (along with plumbing any lance changes), but might need some guidance on where to start.

There are some environment variables that can be set. I think TIMEOUT is what you want to set. It defaults to 30s. This can be formatted like 45s or 45000ms. So you can set something like TIMEOUT=1m if you want a full 60s timeout.
LanceDB relies on the object-store Rust crate to provide connections to S3. The environment variables that can be set correspond with each of the variables here: https://docs.rs/object_store/latest/object_store/enum.ClientConfigKey.html
The environment variable names are the capitalized versions of these string here:
https://docs.rs/object_store/latest/src/object_store/client/mod.rs.html#145-158
The duration format for the timeouts is based on the humantime crate function parse_duration here: https://docs.rs/humantime/latest/humantime/fn.parse_duration.html

Ah, thank you! On further inspection, I don't think this is actually an issue with retries:
 Error after 0 retries in 34.07378292s, max_retries:10, retry_timeout:180s,

Note that this is failing after 0 retries and isn't actually exhausting the backoff/retry configuration parameters.
Another one I ran into today:
OSError: LanceError(IO): LanceError(IO): Execution error: LanceError(IO): Generic S3 error: Error after 0 retries in 54.169075124s, max_retries:10, retry_timeout:900s, source:error sending request for url (https://<s3 url>/0057d8ce-c5a4-40fe-8e73-dc44f341bc73.lance): operation timed out, /app/lance/rust/lance-core/src/io/object_reader.rs:62:12, /app/lance/rust/lance/src/dataset/scanner.rs:1286:31, /app/lance/rust/lance/src/index/vector/ivf/builder.rs:157:27

I think this second issue might be related to this size call:
https://github.com/lancedb/lance/blob/d6772d9125923c11f36d7500e374a7db66d9be2d/rust/lance-core/src/io/object_reader.rs#L60-L63
Is it possible that this size call needs to be wrapped in retries similar to what we're doing for get_range below?


Compact Mode Organizing

Is your feature request related to a problem? Please describe:

Going off of Issue #560, is there anyway that you can add option for sequence number. so they can be displayed in a different order? Similar to my mock up drawing.

Describe the solution you'd like:

I would like to be able to change the sequence of the widgets on the compact mode so that I can have them show up high or lower in the sequence.
Describe alternatives you've considered:

Being about to move the widgets and then lock them on compact mode.
Additional context:

None

If you're feeling adventurous you can edit the  mobileOrder in ~/.homebridge/.uix-dashboard.json.

@oznu i will try it out.

@oznu tried changing the order and assigned 1 through 9 and the mobile order never stuck. restarted homebridge and it kept the HomebridgeStatusWidgetComponent at the top.
[{"x":5,"y":0,"component":"HomebridgeStatusWidgetComponent","cols":9,"rows":4,"mobileOrder":10,"hidePort":false},{"x":17,"y":0,"component":"WeatherWidgetComponent","cols":3,"rows":4,"mobileOrder":20,"hideOnMobile":false,"location":{"id":5690366,"name":"Mandan","country":"US","coord":{"lat":46.8264,"lon":-100.8897}}},{"x":14,"y":0,"component":"ClockWidgetComponent","cols":3,"rows":4,"mobileOrder":23,"hideOnMobile":true,"timeFormat":"h:mm a","dateFormat":"EEEE, MMMM d, y"},{"x":14,"y":7,"component":"AccessoriesWidgetComponent","cols":6,"rows":12,"mobileOrder":9,"hideOnMobile":false,"accessoryOrder":["393605692a804216f2b3481bdf243dd6cfd56a4ebcab7f9adee51236a6f9bd70","f60b98562ffbd26037772fceca3ab6d94a8b83df30900145c051b91d6e57b13a","6453d3df850fdc2df879f061c4528f94752a77874c149d9a72f2bf1965fbb631","996f2b29878f0713408dfc2620b09f4516aebb69603be0e18cb411b93dd47132","a21b1227268effa70539b3d25f5b4ed92753c87908c5fa1e6aed43a122ec01e2","09d3dccf04324f200907517d90af82d4476d8dc111ab565346400283441b1ac8","39725b728dd4e1c55d5706bc47cbdddb088a0a53ac7b67c5056052ba354f7293"]},{"x":5,"y":4,"component":"CpuWidgetComponent","cols":5,"rows":3,"mobileOrder":40},{"x":10,"y":4,"component":"MemoryWidgetComponent","cols":5,"rows":3,"mobileOrder":50},{"x":15,"y":4,"component":"UptimeWidgetComponent","cols":5,"rows":3,"mobileOrder":60,"hideOnMobile":false},{"x":0,"y":9,"component":"SystemInfoWidgetComponent","cols":5,"rows":10,"mobileOrder":70,"hideOnMobile":true},{"x":0,"y":0,"component":"HapQrcodeWidgetComponent","cols":5,"rows":9,"mobileOrder":100,"hideOnMobile":true},{"x":5,"y":7,"component":"HomebridgeLogsWidgetComponent","cols":9,"rows":12,"mobileOrder":1000,"hideOnMobile":true,"fontWeight":"400","fontSize":15}]

I had it set from 1 to 9 and that didn't stick.


community: add Needle retriever and document loader integration

[x] PR title: "community: add Needle retriever and document loader integration"

Where "package" is whichever of langchain, community, core, etc. is being modified. Use "docs: ..."  for CI changes.
Example: "community: add foobar LLM"

[x] PR message: Delete this entire checklist and replace with

Description: This PR adds a new integration for Needle, which includes:

NeedleRetriever: A retriever for fetching documents from Needle collections.
NeedleLoader: A document loader for managing and loading documents into Needle collections.
Example notebooks demonstrating usage have been added in:

docs/docs/integrations/retrievers/needle.ipynb
docs/docs/integrations/document_loaders/needle.ipynb.

Dependencies: The needle-python package is required as an external dependency for accessing Needle's API. It has been added to the extended testing dependencies list.
Twitter handle: Feel free to mention me if this PR gets announced: needlexai.

[x] Add tests and docs: If you're adding a new integration, please include

Unit tests have been added for both NeedleRetriever and NeedleLoader in libs/community/tests/unit_tests. These tests mock API calls to avoid relying on network access.
Example notebooks have been added to docs/docs/integrations/, showcasing both retriever and loader functionality.

[x] Lint and test: Run make format, make lint, and make test from the root of the package(s) you've modified. See contribution guidelines for more: https://python.langchain.com/docs/contributing/

make format: Passed
make lint: Passed
make test: Passed (requires needle-python to be installed locally; this package is not added to LangChain dependencies).

Additional guidelines:

[x] Optional dependencies are imported only within functions.
[x] No dependencies have been added to pyproject.toml files except for those required for unit tests.
[x] The PR does not touch more than one package.
[x] Changes are fully backwards compatible.
[x] Community additions are not re-imported into LangChain core.

If no one reviews your PR within a few days, please @-mention one of baskaryan, efriis, eyurtsev, ccurme, vbarda, hwchase17.

@efriis

@efriis should be ok, Vercel deployment fails due to
Error: Docs markdown link couldn't be resolved: (MIGRATION.md) in source file "/vercel/path0/docs/docs/langserve.md" for version current

I guess that is a FP? Should be all good with the PR.

Hi Langchain team, @efriis  👋 This is Onur from Needle. We are waiting on this review for more than 2 months. There was another PR previously which we had to close and open this one since the review flow changed.
Could you finalize reviewing this PR? Obviously we want to avoid same scenario happening again. Thanks for your efforts!

hey sorry for the delay! would you be interested in integrating like this instead? then you don't have to deal with the "needs support" status for the integration, and docs PRs are much easier for us to review.
Please take a look at the CI failures as well (looks like it's on the docs build, which would apply regardless of format of the integration!)
https://python.langchain.com/docs/contributing/how_to/integrations/

actually merging in master to rebuild the docs - @JANHMS ' comment was addressed earlier, so it may fix itself

Thank @efriis it did solve the issue by itself.
I need this to be a community integration for another integration I am making, where it depends on the fact that I am integrated in the langchain_community package.
Are we ready to merge?

hey sorry for the delay! would you be interested in integrating like this instead? then you don't have to deal with the "needs support" status for the integration, and docs PRs are much easier for us to review.
Please take a look at the CI failures as well (looks like it's on the docs build, which would apply regardless of format of the integration!)

Hey @efriis sorry to bump again, but we actually need this asap and are waiting for a long time. It blocks us on another side. Please let's go ahead and merge so we have it available as the community package.

@efriis

@eyurtsev @efriis

@eyurtsev Hi Eugene - sorry about chasing, but it's ready to be merged from our side. Can you take a look? We understand you guys are busy these days, we appreciate the effort! 🙏


[FLINK-11336][zk] Delete ZNodes when ZooKeeperHaServices#closeAndCleanupAllData

What is the purpose of the change
When calling ZooKeeperHaServices#closeAndCleanupAllData we should delete the
HA_CLUSTER_ID znode which is owned by the respective ZooKeeperHaServices.
Moreover, the method tries to go up the chain of parent znodes and tries to
delete all empty parent nodes. This should clean up otherwisely orphaned
parent znodes.
Verifying this change

Added ZooKeeperHaServicesTest

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

#closeAndCleanupAllData should only be called by the ClusterEntrypoint which transitions the executed ExecutionGraph into a globally terminal state. This should only be possible for the current leader. If the leader changes after the ExecutionGraph has reached a globally terminal state, then the new leader should not start the execution. At the moment, this is not guaranteed to not happen.

Thanks for the explanation!

Thanks for the review @TisonKun and @azagrebin. Merging this PR.

@flinkbot approve all

@flinkbot attention @tillrohrmann


🏷 Feature Request Type
UI Feature
🔖 Feature description
Please add:
Register an account using Full Name and Email and Password..
Login to an account using Email and Password.
Logout from an account.
✔ Solution
Adding Register, Login, Logout
❓ Alternatives
Integrating Google Sign-In into the web app
📝 Additional Context
No response
👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar feature request

Duplicate. User management in general is #128.


Calling Ensure.NotEmptyGuid() is throwing an argument exception with improper value in ParamName

When using Ensrue.NotEmptyGuid(), when an empty guid is being tested/found, the thrown ArgumentException does not have a valid ParamName.

From my understanding, ParamName should only have the name of the parameter (streamBatchId, in this instance).

This is occurring in v0.9.2 in Nuget.


Yaku.all is overridden by yaku/utils/all on yaku.brower.full.min.js version

Reproduction:
<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <title></title>
</head>
<body>
  <script src="path/to/yaku.browser.full.min.js"></script>
  <script>
    console.log(Yaku.all);
  </script>
</body>
</html>

Yaku.all expect is Promise.all but actually is yaku.util.all
https://github.com/ysmood/yaku/blob/master/src/browser.full.js#L8

Actually, I'd like to remove file browser.full.js. Nowadays, people are more comfort with webpack and require.

What do you think?

I just needed a simple Promise polyfill, I OK with it. Thanks anyway :)


[SCB-326] Using the EventManager directly

…google EventBus because it is good enough
Signed-off-by: zhengyangyong<EMAIL_ADDRESS>Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[x] Each commit in the pull request should have a meaningful subject line and body.
[x] Format the pull request title like [SCB-XXX] Fixes bug in ApproximateQuantiles, where you replace SCB-XXX with the appropriate JIRA issue.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Run mvn clean install to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Remove custom EventBus an replace with Already Exists EventManager with google EventBus because it is good enough

Coverage decreased (-0.04%) to 87.28% when pulling 498ec860a6c806ff75d84d72866306bfc4d80d4b on zhengyangyong:SCB-326 into 769dc9dd52f3c003f763ddaacd5d601a37ed273e on apache:master.

need test
do not merge now.

test result is here in comment : https://issues.apache.org/jira/projects/SCB/issues/SCB-326


[bat] Batch File Syntax highlighting not working on variables or comments.

After upgrading to version 0.10.1 Syntax highlighting within windows .bat files has become reduced.
Previous versions would syntax highlight variables (%VARIABLENAME%) and comments(REM-COMMENT TEXT" now these both appear as normal text:

We use the text mate grammar from https://github.com/sublimehq/Packages

I patched the grammar with a fix for these in pending PR #1678

fixed by #1678


ofActionPayload helper is provided

Sometimes it is useful to take access to payload of action in rxjs operator. I have added small halper to reduce boilerplate code a little bit.

thankyou! @sgrishchenko


A proc that returns a string seems to be seen as a int in python

I've been impressed by this library. It seems to greatly simplify the interface between nim and python.
Unfortunately, I've been having problems with def procs that return strings.
So, to provide a simplified example, a bindings.nim:
import unicode

import genny

import txtdb

proc joe(): string =
    result = "hello"

exportProcs:
  joe

writeFiles("bindings/generated", "txtdb")
include generated/internal

Examining the internal file:
proc txtdb_joe*(): cstring {.raises: [], cdecl, exportc, dynlib.} =
  joe().cstring

And yet, if I call it from python:
test = dll.txtdb_joe().decode("utf8")

I get:
Traceback (most recent call last):
  File "/home/johnd/Projects/pytxtdb/tests/test_load.py", line 16, in <module>
    result = person_table.create(person_c)
  File "/home/johnd/Projects/pytxtdb/src/txtdb.py", line 40, in create
    test = dll.txtdb_joe().decode("utf8")
AttributeError: 'int' object has no attribute 'decode'

Details:
Running on Pop_OS!, an ubuntu variant. So, using libtxtdb.so.
Nim is version 1.4.8.
Python is
Python 3.9.5 (default, May 11 2021, 08:20:37)
[GCC 10.3.0] on linux

genny version is genny  [0.1.0]
Thanks for any help you can provide!

Interesting issue. Thanks very much for trying genny and for reporting this issue along with great information so we can reproduce it. Will reply back here with an update soon.

Ok this took a bit longer than I expected to get back to but I do have an update. I am not able to reproduce the issue, but I do know we haven't really documented well how to set things up so there could be many issues along the way. Some things:
nim c -f -d:release --app:lib --gc:arc --tlsEmulation:off --out:txtdb bindings.nim or something like this should be the compile command.
From here, the generated python file does need a tweak to work without the pip set up (which is too much for a simple test). An example file would be:
from ctypes import *
import os, sys

dir = os.path.dirname(os.path.abspath(__file__))
if sys.platform == "win32":
  libName = "txtdb.dll"
elif sys.platform == "darwin":
  libName = "libtxtdb.dylib"
else:
  libName = "libtxtdb.so"
dll = cdll.LoadLibrary(os.path.join(dir, libName))

class txtdbError(Exception):
    pass

def joe():
    result = dll.txtdb_joe().decode("utf8")
    return result

dll.txtdb_joe.argtypes = []
dll.txtdb_joe.restype = c_char_p

test = dll.txtdb_joe().decode("utf8")

print(test)

Notice that I added the print at the bottom, and changed the dir = at the top to work with file paths. It expects the dll / so to be in the same directory as the python file, and the same directory you are running the python script.
For me, then python txtdb.py prints hello as expected.
I hope this helps and thanks for giving genny a try. As you've noticed, it is pretty cool but also quite new and rough. We'll work through it though as we put more time in on genny.

Closing this just for housekeeping. Please re-open if there is an update.


'progress' is not working and I can't find reason.

Hi guys, I want to use playerjs for my project. But I'm not good at js and jquery. So I'm learning while testing some codes. For my project, I interested in 'progress' event which notice me how many buffered.
I wrote this code and didn't work at all.
player.on('progress', function(){   console.log(percent); });
How can I correct this?

use the timeupdate event instead.

Has timeupevent property about buffering?
I thought timeupevent have only about played time.

The progress event is very poorly supported across providers. It's not an event we focus on.


[Java] AsyncMethodCallback should be typed in generated AsyncIface

The parametrization brings the existing actual parametrization with
client call implementation objects to the fore and so this change
also fixes that parametrization to be a simple parametrization over
the return type as is done in the server-side AsyncProcessor code.
NB: This is a breaking change in both generated code and the client
libs.

NB: This is a straw-man at this point that picks up the work started in #500 by @mreve and whose merits is being discussed here: http://markmail.org/message/k77l6helvkh4igrv
Please do not merge pending results of that discussion - this is a breaking change for async client users.


AAD B2C deployment plan

Documentation about AAD B2C deployment plan based on a workgroup.

@Freenity - please take a look at this contribution. Since it's a new article, it will need to be moved to the private repo 'azure-docs-pr' to take advantage of the validation and staging tools available there.
thanks.


Removed app-only permissions notice from "purview" commands. Closes #5026

Removed app-only permissions notice from "purview" commands. Closes #5026

Thank you @nanddeepn!
I think you might have forgotten something. In the code, we also perform an authentication check.

Yes, correct @milanholemans, those need to be removed as well. Plus you need to clean up the test files as well, @nanddeepn...


Option to move or hide this section

Describe your suggested feature

i suggest to add an option to hide or move(somewhere else, but not there) this section (screenshot) since i really don't use it and prefer just  the 3 sections there, sources, extensions and migrate; nothing else.
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extensions repository.
[X] I have updated the app to version 1.8.1.
[X] I will fill out all of the requested information in this form.

Im going to deny this since its too much work and it was recently improved so more people can find uses for it

can you keep it open just i case someone wants to add this feature?


Member deprovisioning when deprovisioning a group

Member deprovisioning when deprovisioning a group
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 271dc426-fb47-7441-d627-ec11f8c7a6ea
Version Independent ID: 4cb8bfc8-4748-e501-425a-e4c2da0f5f5a
Content: Tutorial - Develop a SCIM endpoint for user provisioning to apps from Azure Active Directory - Microsoft Entra
Content Source: articles/active-directory/app-provisioning/use-scim-to-provision-users-and-groups.md
Service: active-directory
Sub-service: app-provisioning
GitHub Login: @kenwith
Microsoft Alias: kenwith

Azure documentation issue guidance
Thanks for opening an issue in the Azure technical documentation repository.
We use GitHub issues as the primary channel for customer and community feedback about the Azure documentation.
Creating an issue
We prefer that you create documentation feedback issues using the Feedback link on the published article - the feedback control on the doc page creates an issue that contains all the article details so you can focus on the feedback part.
You can also create a feedback issue here in the repo. If you do this, please make sure your issue lists:

[ ] The relevant Azure service or technology.
[ ] A link to the published documentation article that you have feedback about.
[ ] Clear, specific feedback that the author can act on.

Pull requests and article contributions
If you know the change that is needed in an article, we encourage you to submit the changes directly using a pull request. If the change is large, or if you want to contribute an entire article, follow these guidelines:

[ ] Don't surprise us with a big pull request or a pull request with a new article! Submit an issue that describes the details of the proposed large change or new article.
[ ] Include the service or technology area.

We'll route the issue to the appropriate content team for review and discussion.
Tech support and product feedback
If you would like to contact Microsoft about other things, such as product feedback or tech support, please review these guidelines:

If you need technical support using Azure, the paid and free support options are described here: https://azure.microsoft.com/support/options/.

Each article in the Azure technical documentation contains a product feedback button - it's best to submit product feedback directly from a relevant article. Otherwise, you can submit product feedback for most Azure products in the following product feedback forum: https://feedback.azure.com/d365community/forum/79b1327d-d925-ec11-b6e6-000d3a4f06a4.

If I deprovision a group, no users are removed (via patch /group/{id}). Shouldn't all users be removed from the group before the group is deprovisioned? The documentation is unclear in this regard (see here) but it seems that a query (nr 4 in the diagram) is made and then a 'remove member' call (nr 5) is made. I can't find any sign of this call in the logs. Can you please clarify?

@harald-quist-stratsys
Thanks for your feedback! We will investigate and update as appropriate.

No updates on this @kenwith?

Moved to work item in backlog. #please-close


Links that open a new tab open in default browser

Links that are supposed to open a new tab open a new tab in a (desktop) browser instead of opening in a new tab in GameBarBrowser

Fixed in https://github.com/dynamiquel/GameBarBrowser/tree/webview2.


Align female / transgender male inclusion criteria with data elements spreadsheet

Make any necessary updates to TopLevelScreeningLibrary.cql based upon the recent discussions between L2/L3 teams around defining female and transgender male.

Open branch gender-identity: https://github.com/ccsm-cds-tools/ccsm-cds-with-tests/tree/gender-identity

This is addressed in https://github.com/ccsm-cds-tools/ccsm-cds-with-tests/pull/41


Calling codes on a .plist

Sorry it took me that long to correct the previous pull request.

Merged 👍


Contiv network support

Contiv network plugin has good policy support, and multicast support, which is important for video streaming use case. Can we make it become another deployment option? https://github.com/contiv/netplugin

cc @PeterLamar

I can add this to the backlog https://www.pivotaltracker.com/n/projects/1461754 and contiv is on our roadmap. Have you used its multicast support with docker?

FYI: As far as i know they are supporting k8s already. Also they are planning to contribute netplugin support upstream into kubernetes/contib/ansible (ref https://github.com/contiv/netplugin/issues/237)

Multicast can work in inter-container use case. Vipin is helping me making external multicast work. Should have good news soon.


⚠ ClamAV has degraded performance

In 4631800, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 73 ms

Resolved: ClamAV performance has improved in e0f026f.


Auto rollback for addColumn with foreign key contraints fails

Environment
Liquibase Version:
3.8
Liquibase Integration & Version: <Pick one: CLI, maven, gradle, spring boot, servlet, etc.>
maven integration
Database Vendor & Version:
Sybase/SQL Anywhere 11
Operating System Type & Version:
Win10
Description
When I write a "addColumn" changeset with a constraint tag adding a foreign key, the foreign key is not droped during the auto roll back and prevent the rollback
Steps To Reproduce
Run this changeset with an appropriate table and column, and try to rollback
`
<preConditions onFail="MARK_RAN">

   <not>

       <columnExists schemaName="schema" tableName="table" columnName="col" />

    </not>

</preConditions>

<addColumn schemaName="schema" tableName="table">

    <column name="col" type="int">

        <constraints referencedTableName="other_table" referencedColumnNames="id" foreignKeyName="fk_table_othertable"/>

    </column>

</addColumn>

`
Actual Behavior
Auto rollback doesn't take the constraint into accound and column cannot be removed because of it.
Expected/Desired Behavior
A drop constraint before the drop column.

Hi @pierregui67 Thanks for writing up this issue.  We will add it to the list of issues that we are processing.

Hi! This is indeed a bug for liquibase 4.17.0. I tried looking at this behavior in other databases, and liquibase execute a DROP COLUMN sql, in other databases, this is enough to drop the constraints, but i looks like this is  not enough to drop the constraints in Sybase. Adding this to the queue of bugs to fix. Thanks for submitting this issue!


function.json file is missing for C#

I created a simple function in Visual Studio Code and I can deploy to Azure without problem. However, I want to update the binding from "GET and POST" to "GET" only. I cannot do this via the portal because the app and function are in READ ONLY mode if I deploy my app via Visual Studio Code. Then, I am thinking I may be able to modify the function.json in my Visual Studio Code and deploy it. However, I cannot find this file. What can i do?

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

ID: 04c9d43d-5bd2-87c6-2ccf-0c65ef193760
Version Independent ID: 6bf46ebc-481f-e4ef-b269-99bf99434601
Content: Create your first function in Azure using Visual Studio Code
Content Source: articles/azure-functions/functions-create-first-function-vs-code.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@bcube Checking in to see if the above post helped answer your question.

@bcube Since we have not heard back from you we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Cider implementation for for enhanced enums

See https://github.com/dart-lang/sdk/issues/47849 for the main tracking issue.

FYI, the flag has been flipped so these can be used without a flag internally now.

@keertip can you confirm this is done?


autosave files

Issue Type: Bug
sql operation studio  resets my auto save setting, I had it OFF. There were two events
first I installed latest update, second my Windows got restarted at night while
sos was opened. I am not sure which  of these events triggered auto save even though I had it off for over a month and it was always asking if I want to save. Lost some queries that I did not intend to save.
This option should stay unchanged after updates or if closed by Windows.
SQL Operations Studio version: sqlops 0.30.6 (df7e3ec7d52a82febee5b597a1019cabf021b883, 2018-06-19T21:45:43.589Z)
OS version: Windows_NT x64 6.1.7601

System Info

Item
Value

CPUs
Intel(R) Xeon(R) CPU E5-2623 v4 @ 2.60GHz (8 x 2594)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: disabled_softwarevideo_decode: enabledvideo_encode: enabledvpx_decode: unavailable_softwarewebgl: enabledwebgl2: enabled

Memory (System)
15.89GB (7.61GB free)

Process Argv
D:\3partyPrograms\micrsosft\sqlops\SQL Operations Studio\sqlops.exe

Screen Reader
no

VM
0%

Extensions: none

Thanks for reporting this @tekken22. Can you clarify if you're referring to the "files.autoSave" setting or some other setting? If so, do you know what value it got changed to? Or did it just not respect the setting the one time either when it updated or when Windows restarted?


Remove DotNetCliToolReference for Microsoft.VisualStudio.Web.CodeGeneration.Tools

Scaffolding is now generating a global tool and the package Microsoft.VisualStudio.Web.CodeGeneration.Tools is no longer being generated.
cc @seancpeters @mlorbetske  @vijayrkn

@prafullbhosale Could you rebase and ensure Appveyor or Travis pass?

Appveyor and Travis are being super flaky. @prafullbhosale Can you generate some templates with your change and do a basic "dotnet run" sanity check?

Will this fix the issue with preview2 stack:

error NU1102: Unable to find package Microsoft.VisualStudio.Web.CodeGeneration.Tools with version (>= 2.1.0-preview2-30131)

Closing as this will be done as part of https://github.com/aspnet/templating/pull/370


action, reducer, effects in different files?

Hi, thanks for the wonderful work. I love redux pattern very much, but normally in global store redux pattern we used to divide the files. So something like, flights.reducer.ts, flights.action.ts and flights.effects.ts and somehow wire them up all together. So, is it possible we can separate reducer functions, actions list and side effects in their own separate file for a particular signalStore? Otherwise I think, there will be a lot of code inside signalStore() as the project grows with more and more state slices. Thanks in advance, once again great work team :)

Hi @audhit, we had plans for withRedux to extend it but it turned out that NgRx itself is now working no an eventing extension which would supersede this.
I cannot promise anything, maybe we provide actions which can be dispatched globally, or we wait for the release of the events extension.


Webhook API changes and UI Implementation

On the API side this adds a summary method to obtain the summaries of all the webhooks with the size of their queue.
On the UI side this implements the UI for the webhooks page in React.
It also makes many (though not all) of the shared react components easier to reuse:

propTypes were added to many react components
Messy code was cleaned up
Non-custom sorting was implemented in tables (but you still have to provide your own sort function). Note that elements will not jump around even if there are more than ten.
Vex now works with React.

Things that could be improved (but may not be necessary for now):

There is a bit of messy code. Places where I could have used shared react components but didn't, or put methods into React that maybe should have been part of the model
Vex + React is a bit of a hack, and implementation could be improved by making the Vex components reusable.

Note that this PR (including its title and top comment) has been updated to include the UI implementation.

Two bugs:

First, I managed to create a webhook with a space in the URI and now I can't delete it
Second, it isn't sending the user creating the webhook.
I'll address these tomorrow.

Those two bugs are now fixed.
Having the ID in a path param turned out to be problematic because certain browsers and proxies will encode and decode the URL the wrong number of times, so the old API methods that used path params were deprecated. A new set of API methods was added that does exactly the same things as the old ones, except using query params instead of path params - since proxies and browsers leave query params alone.

Looks good @Calvinp , going to merge so we can work more on the PRs that build off these components


add sanette as user of ocaml-ci

Thanks for your interest @sanette to start building with OCaml-CI:

Add the app to your account, selecting Install at https://github.com/apps/ocaml-ci
Select only the repositories you want tested - if you select All Repositories we won't build anything!

Please let me know if you run into any issues.

thanks; Is there anything more I should do to have something happen? I couldn't find this in the docs

@tmcgilchrist maybe you need to make deploy-stack too?

I have done it as docker container inspect showed an outdated user list.

it's working now, thanks

Thanks for fixing the deploy @mtelvers


Progressive Web App (PWA)

To get a more "app-like" feeling a PWA would be great.

Agreed! I'll have a look at this.


libadwaita chapters are missing in the book since awhile.

@Hofer-Julian after returning to the book for reference I noticed that libadwaita related chapters has disappeared and new inactive chapters in Contents were added.
I wonder is a bug or missing content hasn't been ported to news structure yet?

Also, "Resource" chapter has no content, just a Title.

Previous version of the book is back ATM. It seems like it was already fixed.

@Hofer-Julian Shouldn't we close this issue since the problem has been resolved?

Sure

I think we should stop publishing the book on releases as it usually might require fixes or updates after the release is done.

I think we should stop publishing the book on releases as it usually might require fixes or updates after the release is done.

We already stopped doing that on main IIRC. The older point releases sill mess us up though.


Create Draft of Air Transport Figures

While we are working on obtaining the necessary data, we should start preparing the corresponding visualizations.
I suggest we use geopandas, rather than https://scitools.org.uk/cartopy/docs/latest/ since it is better documented - and should offer all features we need.
For now, assume that we have data on ~20 airports in Europe and all flights between them.
Our figure should now show:

All flights between these airports (great circle only)
The number of flights (frequency)

You can use my lecture figures as templates for using geopandas: map_corsia_euets and route_ban_france.
Here are two ideas we could adapt (image #1 source, image #2 source):

@michaelweinold I started working on the map for Europe! It looks quite okay so far. I've included the 20 biggest airports on the map, but I'm having trouble finding data for the connections between them. Do you have any ideas where I can find this information?

Right now, just make up some sample data.

I think we could maybe get the data from here: https://ec.europa.eu/eurostat/web/transport/data/database

I still have to adjust the code with comments and some adjustment that it follows all rules... sorry that I already committed


Parent folder is being littered

The Prebuild (or rather FetchDependencies.py) script places the fetched dependencies in the parent folder of the RGA source directory.
Go to ~/dev/radeon_gpu_analyzer/Build/, run ./Prebuild.sh -> Dependencies are placed in ~/dev/Common/ - A library should never litter parent directories unless specifically being instructed to do so.
Even if this is a wontfix there should at least be a note in the documentation.

Hi @robinchrist,
This has been resolved with the update prebuild functionality. The dependencies are fetched into subfolders.


My steinels give "[Node 059] Error during node interview: Node 59 does not support the Command Class Version! (ZW0302). Results in no entities and strange behaviour.

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
YES, BUT a Home Assistant developer has told me to come here
Is your problem within ZWaveJS2MQTT?
NO, my problem is NOT within ZWaveJS2MQTT
Checklist

[X] I have checked the troubleshooting section and my problem is not described there.

[X] I have read the changelog and my problem was not mentioned there.

Describe the bug
The problem
So , I have a strange phenomenon going on, and I'm not shure it's a bug or PEBCAK.
hassio on nuc, 2021.12.7
zwave_js addon: 0.1.51

Bump Z-Wave JS to 8.9.2
Bump Z-Wave JS Server to 1.14.0

USB stick: https://devices.zwave-js.io/?jumpTo=0x0271:0x0001:0x1a73:0.0
History;

Updated to zwave-js addon 0.1.49 and beyond
got an error (Results in no entities being added to HA)

[Node 059] Error during node interview: Node 59 does not support the Command Class Version! (ZW0302)

after heal / reinterview, changing openzwave_js versions , ... I excluded the device for testing
EXISTING, prefectly working steinel IS140- 2 ( https://devices.zwave-js.io/?jumpTo=0x0271:0x0002:0x1a72:0.0 ) Got removed
I'm not able to read any of these two sensors, I'm afraid to try to exclude / include something else as a test.

Device information
https://devices.zwave-js.io/?jumpTo=0x0271:0x0002:0x1a72:0.0
and
https://devices.zwave-js.io/?jumpTo=0x0271:0x0001:0x1a73:0.0
How are you using node-zwave-js?

[ ] zwavejs2mqtt Docker image (latest)
[ ] zwavejs2mqtt Docker image (dev)
[ ] zwavejs2mqtt Docker manually built (please specify branches)
[ ] ioBroker.zwave2 adapter (please specify version)
[X] HomeAssistant zwave_js integration  (please specify version)
[ ] pkg
[ ] node-red-contrib-zwave-js (please specify version, double click node to find out)
[ ] Manually built from GitHub (please specify branch)
[ ] Other (please describe)

Which branches or versions?
zwave_js addon: 0.1.51

Bump Z-Wave JS to 8.9.2
Bump Z-Wave JS Server to 1.14.0

Did you change anything?
yes (please describe)
If yes, what did you change?
Updated to latest available brach
Did this work before?
Yes (please describe)
If yes, where did it work?
Device got added correctly in previous branch ( +/- 2 yrs ago)
Attach Driver Logfile
Initial symptoms previous version
2021-11-29T18:02:05.002Z CNTRLR « [Node 059] ping successful
2021-11-29T18:02:05.003Z CNTRLR » [Node 059] querying node info...
2021-11-29T18:02:05.084Z CNTRLR « [Node 059] node info received
                                  supported CCs:
                                  · Z-Wave Plus Info
                                  · Firmware Update Meta Data
                                  · Version
                                  · Manufacturer Specific
                                  · Multi Channel
                                  · Device Reset Locally
                                  · Configuration
                                  · Powerlevel
                                  · Node Naming and Location
                                  · Notification
                                  · Association
                                  · Multi Channel Association
                                  · Association Group Information
                                  · Multilevel Sensor
                                  · Binary Switch
                                  · All Switch
                                  controlled CCs:
2021-11-29T18:02:05.102Z CNTRLR   [Node 059] Interview stage completed: NodeInfo
2021-11-29T18:02:05.104Z CNTRLR   [Node 059] Interviewing Manufacturer Specific...
2021-11-29T18:02:05.104Z CNTRLR » [Node 059] querying manufacturer information...
2021-11-29T18:02:05.190Z CNTRLR « [Node 059] Received updated node info
2021-11-29T18:02:05.208Z CNTRLR « [Node 059] received response for manufacturer information:
                                    manufacturer: STEINEL GmbH (0x0271)
                                    product type: 0x02
                                    product id:   0x1a72
2021-11-29T18:02:05.209Z CNTRLR   [Node 059] Interviewing Version...
2021-11-29T18:02:05.209Z CNTRLR » [Node 059]   querying the CC version for Version...
2021-11-29T18:02:05.404Z CNTRLR   [Node 059]   does NOT support CC Version (0x86)
2021-11-29T18:02:05.404Z CNTRLR » [Node 059] querying node versions...
2021-11-29T18:02:05.404Z CNTRLR   [Node 059] Error during node interview: Node 59 does not support the Command C
                                  lass Version! (ZW0302)
2021-11-29T18:02:05.404Z CNTRLR » [Node 059] Assigning SUC return route...
2021-11-29T18:02:10.032Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.

Additional information
2021-11-29T19:34:06.229Z CNTRLR   [Node 059] Beginning interview - last completed stage: None
2021-11-29T19:34:06.229Z CNTRLR   [Node 059] new node, doing a full interview...
2021-11-29T19:34:06.230Z CNTRLR » [Node 059] querying protocol info...
2021-11-29T19:34:06.232Z SERIAL » 0x010400413b81                                                       (6 bytes)
2021-11-29T19:34:06.232Z DRIVER » [REQ] [GetNodeProtocolInfo]
                                    payload: 0x3b
2021-11-29T19:34:06.233Z SERIAL « [ACK]                                                                   (0x06)
2021-11-29T19:34:06.234Z SERIAL « 0x01090141d39c01040701fa                                            (11 bytes)
2021-11-29T19:34:06.235Z SERIAL » [ACK]                                                                   (0x06)
2021-11-29T19:34:06.235Z DRIVER « [RES] [GetNodeProtocolInfo]
                                    payload: 0xd39c01040701
2021-11-29T19:34:06.236Z CNTRLR « [Node 059] received response for protocol info:
                                  basic device class:    Routing Slave
                                  generic device class:  Notification Sensor
                                  specific device class: Notification Sensor
                                  node type:             Routing End Node
                                  is always listening:   true
                                  is frequent listening: false
                                  can route messages:    true
                                  supports security:     false
                                  supports beaming:      true
                                  maximum data rate:     100000 kbps
                                  protocol version:      3
2021-11-29T19:34:06.237Z CNTRLR   [Node 059] Interview stage completed: ProtocolInfo
2021-11-29T19:34:06.237Z CNTRLR » [Node 059] querying node info...
2021-11-29T19:34:06.239Z SERIAL » 0x010400603ba0                                                       (6 bytes)
2021-11-29T19:34:06.239Z DRIVER » [Node 059] [REQ] [RequestNodeInfo]
                                    payload: 0x3b
2021-11-29T19:34:06.240Z SERIAL « [ACK]                                                                   (0x06)
2021-11-29T19:34:06.246Z SERIAL « 0x01040160019b                                                       (6 bytes)
2021-11-29T19:34:06.247Z SERIAL » [ACK]                                                                   (0x06)
2021-11-29T19:34:06.249Z DRIVER « [RES] [RequestNodeInfo]
                                    payload: 0x01
2021-11-29T19:34:06.653Z SERIAL « 0x01190049843b130407015e7a8672605a70737771858e593125278f            (27 bytes)
2021-11-29T19:34:06.654Z SERIAL » [ACK]                                                                   (0x06)
2021-11-29T19:34:06.655Z DRIVER « [Node 059] [REQ] [ApplicationUpdateRequest]
                                    payload: 0x3b130407015e7a8672605a70737771858e59312527
2021-11-29T19:34:06.657Z CNTRLR « [Node 059] node info received
                                  supported CCs:
                                  · Z-Wave Plus Info
                                  · Firmware Update Meta Data
                                  · Version
                                  · Manufacturer Specific
                                  · Multi Channel
                                  · Device Reset Locally
                                  · Configuration
                                  · Powerlevel
                                  · Node Naming and Location
                                  · Notification
                                  · Association
                                  · Multi Channel Association
                                  · Association Group Information
                                  · Multilevel Sensor
                                  · Binary Switch
                                  · All Switch
                                  controlled CCs:
2021-11-29T19:34:06.683Z CNTRLR   [Node 059] Interview stage completed: NodeInfo
2021-11-29T19:34:06.683Z CNTRLR   [Node 059] Interviewing Manufacturer Specific...
2021-11-29T19:34:06.684Z CNTRLR » [Node 059] querying manufacturer information...
2021-11-29T19:34:06.688Z SERIAL » 0x010900133b027204253fb0                                            (11 bytes)
2021-11-29T19:34:06.689Z DRIVER » [Node 059] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      63
                                  └─[ManufacturerSpecificCCGet]
2021-11-29T19:34:06.690Z SERIAL « [ACK]                                                                   (0x06)
2021-11-29T19:34:06.697Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2021-11-29T19:34:06.698Z SERIAL » [ACK]                                                                   (0x06)
2021-11-29T19:34:06.698Z DRIVER « [RES] [SendData]
                                    was sent: true
2021-11-29T19:34:07.013Z SERIAL « 0x011800133f00001f02cf7f7f7f7f010103050f00000101000010              (26 bytes)
2021-11-29T19:34:07.014Z SERIAL » [ACK]                                                                   (0x06)
2021-11-29T19:34:07.015Z DRIVER « [REQ] [SendData]
                                    callback id:     63
                                    transmit status: OK
2021-11-29T19:34:07.163Z SERIAL « 0x01100004003b087205027100021a72cf0079                              (18 bytes)
2021-11-29T19:34:07.165Z CNTRLR   [Node 059] [+] [Manufacturer Specific] manufacturerId: 625        [Endpoint 0]
2021-11-29T19:34:07.166Z CNTRLR   [Node 059] [+] [Manufacturer Specific] productType: 2             [Endpoint 0]
2021-11-29T19:34:07.166Z CNTRLR   [Node 059] [+] [Manufacturer Specific] productId: 6770            [Endpoint 0]
2021-11-29T19:34:07.167Z SERIAL » [ACK]                                                                   (0x06)
2021-11-29T19:34:07.168Z DRIVER « [Node 059] [REQ] [ApplicationCommand]
                                  └─[ManufacturerSpecificCCReport]
                                      manufacturer id: 0x0271
                                      product type:    0x02
                                      product id:      0x1a72
2021-11-29T19:34:07.169Z CNTRLR « [Node 059] received response for manufacturer information:
                                    manufacturer: STEINEL GmbH (0x0271)
                                    product type: 0x02
                                    product id:   0x1a72
2021-11-29T19:34:07.170Z CNTRLR   [Node 059] [+] [Manufacturer Specific] interviewComple [Endpoint 0] [internal]
                                  te: true
2021-11-29T19:34:07.179Z CNTRLR   [Node 059] Interviewing Version...
2021-11-29T19:34:07.180Z CNTRLR » [Node 059]   querying the CC version for Version...
2021-11-29T19:34:07.182Z SERIAL » 0x010a00133b038613862540a8                                          (12 bytes)
2021-11-29T19:34:07.182Z DRIVER » [Node 059] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      64
                                  └─[VersionCCCommandClassGet]
                                      CC: Version
2021-11-29T19:34:07.184Z SERIAL « [ACK]                                                                   (0x06)
2021-11-29T19:34:07.190Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2021-11-29T19:34:07.191Z SERIAL » [ACK]                                                                   (0x06)
2021-11-29T19:34:07.191Z DRIVER « [RES] [SendData]
                                    was sent: true
2021-11-29T19:34:07.526Z SERIAL « 0x011800134000002202cf7f7f7f7f010103050f00000101000052              (26 bytes)
2021-11-29T19:34:07.527Z SERIAL » [ACK]                                                                   (0x06)
2021-11-29T19:34:07.528Z DRIVER « [REQ] [SendData]
                                    callback id:     64
                                    transmit status: OK
2021-11-29T19:34:07.635Z SERIAL « 0x010c0004003b0486148600cf0013                                      (14 bytes)
2021-11-29T19:34:07.636Z SERIAL » [ACK]                                                                   (0x06)
2021-11-29T19:34:07.637Z DRIVER « [Node 059] [REQ] [ApplicationCommand]
                                  └─[VersionCCCommandClassReport]
                                      CC:      Version
                                      version: 0
2021-11-29T19:34:07.640Z CNTRLR   [Node 059]   does NOT support CC Version (0x86)
2021-11-29T19:34:07.640Z CNTRLR » [Node 059] querying node versions...
2021-11-29T19:34:07.641Z CNTRLR   [Node 059] Error during node interview: Node 59 does not support the Command C
                                  lass Version! (ZW0302)
2021-11-29T19:34:34.784Z SERIAL « 0x0112000400080a32022132000000000000c3000b                          (20 bytes)

Additional information; current version of the addon
2021-12-31T14:23:25.527Z CNTRLR   [Node 062] The node is alive.
2021-12-31T14:23:25.529Z CNTRLR « [Node 062] ping successful
2021-12-31T14:23:25.557Z CNTRLR   [Node 062] Interviewing Z-Wave Plus Info...
2021-12-31T14:23:25.557Z CNTRLR » [Node 062] querying Z-Wave+ information...
2021-12-31T14:23:25.734Z CNTRLR « [Node 062] received response for Z-Wave+ information:
                                  Z-Wave+ version: 1
                                  role type:       AlwaysOnSlave
                                  node type:       Node
                                  installer icon:  0x0c07
                                  user icon:       0x0c07
2021-12-31T14:23:25.767Z CNTRLR   [Node 062] Interviewing Multi Channel...
2021-12-31T14:23:25.767Z CNTRLR » [Node 062] Querying endpoint count for CommandClass Binary Switch...
2021-12-31T14:23:25.768Z CNTRLR   [Node 062] Error during node interview: Node #62 does not support the command
                                  GetV1! (ZW0302)
2021-12-31T14:23:25.768Z CNTRLR » [Node 062] Assigning SUC return route...

Please include a full driver log of the interview on loglevel debug, not only snippets or lower loglevels.


Link external files into HTML-example area?

The documentation of HTML inside a comment of a SCSS-file is the key to many problems. Many modules are huge HTML-constructs and can be the combination of other modules. E.g. a caroussell of teasers. If the teaser changes the developer has to know, in which files this teaser is used, too.
I would prefer to link to files inside the html-example-area. In these files there would be the HTML, needed to be displayed. We would have with this solution only a singlue point of failure, regarding the working code, not multiple points.
Would this idea be possible with hologram?
Would you consider developing it?

I think this could be done as a custom markdown tag somehow. Personally, I'm not interested in developing but I'd be open to reviewing pull requests for it.


Image of auto-fill imported book doesn’t update after refining search

I was lazy, and only searched for "Elder Race". That gave me some paranormal romance book with Series: Elder Races (maybe a title match should have precedence? Anyway, different issue :D), so I chose "Discard". I added Author: Adrian Tchaikovsky and it found the proper book. But the image stayed as the paranormal romance cover, and I needed to manually import the correct one.

Ok, I'll have a look at it.

Should be fixed in v 0.30.0


move current content of help pages into the wiki

Empty the bridge docs afterwards.
Missing docs:

[ ] About Aurelia (but I guess that would be the same anyway)
[ ] About materialize
[ ] Bridge developers notes

The bridge developers notes should be created in sync with @rborosak as everything that is "target bridge independent" (across all bridges) should be in the skeleton bridge as well.
Both tutorial categories should be completely Materialize bridge specific Note that each tutorial comes with the finished code repository https://github.com/aurelia-ui-toolkits/skeleton-navigation-kendo and https://github.com/aurelia-ui-toolkits/skeleton-plugin-kendo

KendoUI has some specific features in bridge developers notes (generation of bindables), which I find interesting. I thought it would be a good idea to document some Materialize specific thigs there, too.
Of course that doesn't stop us from having synced contents.

It is very rewarding to see that you are not limiting your interest in Materialize bridge only as it was always my desire that we all know as much about what other team members to as possible.
The concept of using any available metadata from the bridge target toolkit is one of the key property of our bridge implementations, so we should always seek to find a reliable way to do this (see this and this as examples)


Allow for notifications to go to a specific team member

Should a build fail currently it posts a message to the channel for the whole team to see. However if the branch being tested is a branch that is specific to a developer then it would be good to @Tag the developer. With many developers it becomes difficult to filter the notifications that need to be looked at.

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

ID: 1cddc0ae-93af-297c-2e71-334143ebee1e
Version Independent ID: cb76e516-8471-c3e1-45f4-0a20a223f32a
Content: Microsoft Teams with Azure DevOps Services and Team Foundation Server
Content Source: docs/service-hooks/services/teams.md
Product: devops
GitHub Login: @elbatk
Microsoft Alias: elbatk

Hi @greengumby , I'm adding @roofers to see if this is possible. If it is, I can add it to the docs, if not, you may want to just post it to the Azure DevOps Developer Community as a request.

@greengumby - This is great feedback. Currently, we don't have the ability to @ mention someone in a hook. I recommend that you follow up on the developer community that @elbatk linked to above. It will help us better track these requests.


Update API docs

Notes:

tags query parameter will be removed
partition_by_field should not be documented for now

partition_by_field looks like it's still missing in docs

Actually, this is voluntary because this part of the code is not stable.
Do you have a use case where thispartition_by_field is useful for you?


Final release notes for 1.7.0

Fills in remaining release notes (PR and issue lists will be updated separately as those are a living thing...).
Could everyone please have a look and fill in whatever I've missed. Apologies in advance for anything that I have missed. In particular, @hkaiser could you add a note on the collectives changes (and anything else that you think is relevant)? @Jedi18, @srinivasyadav18 could you have a look to see if I've missed some algorithms that you've adapted?

@Jedi18, @srinivasyadav18 did you have anything to add? @Jedi18 I'll still update the list of adapted algorithms depending on how many your PRs we merge before the release.

Thanks! No, don't have anything to add.

Thank you. No, I do not have anything to add.


Child record mutations should navigate back to parent upon completion

Is your feature request related to a problem? Please describe.
When adding or editing records from a page another record is embedded in, you have to press back twice (once to get to the edit form and another to get back to the initial page) in order to arrive at the initial page you were coming from. This is a UX nightmare for edit heavy applications.
Describe the solution you'd like
Edit and insert operations should remember where they were initiated from and renavigate to the initiating page upon completion.
Additional context
See video for example (image doing this 100's of times per day)
https://user-images.githubusercontent.com/19151369/193868890-aa04ad99-dd44-48fd-84bd-f432ffea81ef.mp4
Add any other context or screenshots about the feature request here.

Hey, thank you for raising this issue. We have general navigation improvements in the pipeline (for 2023.3), which includes this problem you're experiencing.

Is there anyway I can contribute to this to help it make an earlier release?


fillColor, StrokeColor, opacity, StrokeWidth of Rectangle tag don't work

Describe the bug
I tried to change the value of parameters fillColor, opacity, strokeColor, strokeWidth, canRotate of Rectangle tag but nothing works.
To Reproduce
Steps to reproduce the behavior:

Go to polygon tag playground
Change fillColor to #29b924
Compare with fillColor default, nothing changes.

Expected behavior
The Rectangle tab should change behavior whenever we change its value of parameter.
Screenshots
fillColor by default

fillColor = "#52c825"

fillColor = "#9d34a4"

Thank you for your vigilance! The playground version doesn't look like the latest one. But it seems that parameters fillColor, opacity, strokeColor, strokeWidth  haven't worked for a while.
We're already working on that.

The fix is in master branch and will be release in 1.4.1.


TSC Meeting - 2021-08-30

Content

Meetings are held every other week on Mondays at 10:00 EST (US east coast).
You can check your local time: https://www.timeanddate.com/time/map/.
Discussion group: https://lists.openmainframeproject.org/g/ambitus-discussion
All meetings are listed on the Open Mainframe Project calendar at https://lists.openmainframeproject.org/calendar, subject to the mailing lists you are subscribed to.
Conference Call Details
Join Zoom Meeting (you must be logged on to Zoom)
https://zoom.us/j/706416074 (ID: 706416074)
Meeting ID: 706 416 074
One tap mobile
+16465588656,,706416074# US (New York)
+16699006833,,706416074# US (San Jose)
Dial by your location
+1<PHONE_NUMBER> US (New York)
+1<PHONE_NUMBER> US (San Jose)
855 880 1246 US Toll-free
877 369 0926 US Toll-free
+1<PHONE_NUMBER> Canada
855 703 8985 Canada Toll-free
Meeting ID: 706 416 074
Find your local number: https://zoom.us/u/acBVrM6HWR
Recording Information
To be added...
Attendance
[ ] Charles Korpics
[ ] Dieter Wellerdiek
[ ] Giancarlo Frix
[ ] Joe Bostian
[ ] Joe Devlin
[ ] Michael Colavita
[ ] Peter Fandel
[ ] Tatiana Balaburkina
[ ] Yoel Ben-Avraham
[ ] Zach Burns
[ ] John Mertic
Agenda

Kobotoolbox port
Tensorflow serving
Open Mainframe Summit is coming:  https://events.linuxfoundation.org/open-mainframe-summit/

Minutes


kubeadm/create-cluster: add warning about admin.conf

note: this is targetting dev-1.21 since the command kubeadm kubeconfig user is being promoted in 1.21.
Add warning that the file must not be shared as it has super powers
that cannot be revoked.
xref https://github.com/kubernetes/kubeadm/issues/2414
/sig cluster-lifecycle

/lgtm

/assign


Toggle Minimap won't work

Issue Type: Bug
Menu/View/Toggle Minimap doesn't make any difference. Minimap won't go away.
VS Code version: Code 1.25.1 (1dfc5e557209371715f655691b1235b6b26a06be, 2018-07-11T15:43:53.668Z)
OS version: Windows_NT x64 10.0.16299

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-4310U CPU @ 2.00GHz (4 x 2594)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: disabled_softwarevideo_decode: enabledvideo_encode: enabledvpx_decode: unavailable_softwarewebgl: enabledwebgl2: enabled

Memory (System)
15.68GB (8.70GB free)

Process Argv
C:\Program Files\Microsoft VS Code\Code.exe C:\Users\fvogliotti\Desktop\bluewater.sh

Screen Reader
no

VM
0%

Extensions (7)

Extension
Author (truncated)
Version

xml
Dot
2.3.1

gitlens
eam
8.5.1

java
red
0.28.0

vscode-java-debug
vsc
0.10.0

vscode-java-pack
vsc
0.3.0

vscode-java-test
vsc
0.7.1

vscode-maven
vsc
0.9.2

@frvo Can you please check your User Settings, Workspace Settings and Folder Settings for editor.minimap ?

I'm sorry I omited one thing: this happens when I switched to the new interface custom in Window settings:
File/Preferences/Settings/Window/Title Bar Style -> switched to "custom"
When in "Native" mode, no problems whatsoever.

@frvo sorry for the bad experience. This issue should be resolved in the latest insiders. Would you be able to verify?

In fact I tested Insider version and yes, it works perfectly. Thank you!!

@frvo thanks for verifying


Some pop up menus are not displayed correctly (unreadable)

Some right click pop up menus (i.e. History, Notifications menu, Download, etc...) are not correctly displayed. They have a blank background and this results in getting an unreadable text, because we are assuming text is displayed in Nord Polar Dark.
If we knew the name of those classes it would be way easier

for now i've just changed menu pop ups characters colours from white to black into the history sidebar and bookmarks sidebar but this is only a temporary fix

Some right click pop up menus (i.e. History, Notifications menu, Download, etc...) are not correctly displayed. They have a blank background and this results in getting an unreadable text, because we are assuming text is displayed in Nord Polar Dark.
If we knew the name of those classes it would be way easier

It's in beta

I also have a fork and it is in beta too lol

Some right click pop up menus (i.e. History, Notifications menu, Download, etc...) are not correctly displayed. They have a blank background and this results in getting an unreadable text, because we are assuming text is displayed in Nord Polar Dark.

If we knew the name of those classes it would be way easier

It's in beta

Did you realize that i am the author of this repo and issue did you?

Some right click pop up menus (i.e. History, Notifications menu, Download, etc...) are not correctly displayed. They have a blank background and this results in getting an unreadable text, because we are assuming text is displayed in Nord Polar Dark.

If we knew the name of those classes it would be way easier

It's in beta

Did you realize that i am the author of this repo and issue did you?

Wait I didn't see that 😅
Sorry?

Some right click pop up menus (i.e. History, Notifications menu, Download, etc...) are not correctly displayed. They have a blank background and this results in getting an unreadable text, because we are assuming text is displayed in Nord Polar Dark.

If we knew the name of those classes it would be way easier

It's in beta

Did you realize that i am the author of this repo and issue did you?

Wait I didn't see that 😅
Sorry?

That's fine, no worries ✌

We can consider this closed (even if not totally) with the latest push


When a task of a pipeline run timeout , the finally tasklist will not be implemented?

As the title told, when I use the feature "finally" keyword as the documents expound  with the Tekton version 0.25.0.
I write the pipelinerun yaml  as follows.
apiVersion: tekton.dev/v1beta1
kind: PipelineRun
metadata:
generateName: pipelinerun-
spec:
pipelineSpec:
tasks:
- name: task1
taskRef:
name: task1
finally:
- name: clean-task
taskRef:
name: clean-task
I found that the finally task  "clean-task"  does not execute, when the task1 run exceed  the time limits of tekton.
The main requirement of my usage is that I want to do some clean task  at the end of the pipelinerun  even if some task is out of time limit.
I want to figure out how to  resolve this scene or I can access my purpose  with some other substitution.
THANKS

Hi @NEUerYZY, this section of the Tekton docs may be helpful. It looks like you aren't specifying any timeouts in your pipelinerun, so the global timeout of 60 mins applies. You can set a timeout for your pipeline and reserve some of it for finally tasks, as shown in the docs, or you can choose to set 0 (for no timeout) for your pipelinerun.

/kind bug

We may need to update the documentations to make it clear

@lbernick Thank you for your  reply ,I tried the solution as the doc illustrated and it works

@jerop That's great ,Thank you very much

We should also consider changing the default timeout behavior to reserve some time for finally tasks.

We should also consider changing the default timeout behavior to reserve some time for finally tasks.

@lbernick Has this feature been implemented? Finally tasks should always be run even if the main pipeline has timeout.


vz: warn ignored YAML fields

Warnings should be printed for ignored YAML propertries: https://github.com/containerd/nerdctl/blob/c1a4159035b77a4a739a503b98139a17ac3440b8/pkg/composer/serviceparser/serviceparser.go#L38
Can be another PR though

Originally posted by @AkihiroSuda in https://github.com/lima-vm/lima/pull/1147#discussion_r1016138374

I will work on this next


Comparison with SWC/jest

Clear and concise description of the problem
in comparisons page, I would like to see a comparison with https://www.npmjs.com/package/@swc/jest
Suggested solution
compare a set of tests with https://www.npmjs.com/package/@swc/jest
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Would like to know, if/how is it possible to use vitest with TypeScript support while using SWC for compiling a project.
Currently, I'm using jest and @swc/jest for testing my Node.js fastify API REST application but there are many issues with jest and vitest is really looking great and modern! Actually, jest is stopping my project to use ESM modules imports "type": "module" in my package.json.
vitest seems to solve this issue (and of course with many other great improvements).
Is it possible/recommended to use vitest without vite and not for frontend but for backend code?
How can I use SWC for compiling my project, but still configure vitest for testing, and is it viable/good to do so?
Thanks for your replies! :smile:

You can use Vite plugins to compile your project, like this: https://github.com/wight554/vitest-nestjs-testing/commit/9e4d1e5f6c4b723b972aa470aed2ef3d3986476e (haven't tested it)

I don't think this comparison is needed in documentation because you can also use SWC transformer in Vitest, so comparing Vitest and Jest is enough.


Unable to make client.quit() async

Issue
Unable to make client.quit() async
I would like to make client.quit into quitAsync (just like client.get can).
I have tried the following two methods. Neither of them wait for the promise to resolve or reject!
let client = redis.createClient(options);

// Method 1
client._quit = promisify(client.quit).bind(client);

// Method 2
        client._quit = () => {
            return new Promise((resolve, reject) => {
                client.quit((err, d) => {
                    if (!err) {
                       console.log("1");
                        return resolve(d)
                    } else {
                        return reject(err)
                    }
                });
                // if (!result) {
                //     return reject(new Error("client/connection does not exist"))
                // }
            });
        };

// some where else
await conn._quit();
console.log("2");

Using method-2 Expected
"1" gets printed before "2"
Using method-2  Actual
"2" gets printed on the console before "1" ! how and why?
Environment

Node.js Version: 14.2.0
Redis Version: 5.0.6
Platform: Win 10

Correct me if im wrong, but the example  you wrote uses top level await, and that is not supported by node js 14.2.0
try invoking it with a IIFE
(async () => {
await conn._quit();
})()

@donjo9 the await is not at the top level. My example above is just for illustration.

https://github.com/donjo9/redis-async-test
I made a small test

node --version v14.2.0
looks like it works

I will revisit this, just preoccupied with something else at the moment; thanks.

Hi @mannharleen, the await works but I think in your case it might be due node version (I am using v14.15.3).
import dotenv from "dotenv";
dotenv.config();
import { createClient } from "redis";

try {
    const RedisClient = await new Promise((resolve, reject) => {
        try {
            const redis = createClient({
                host: process.env.REDIS_HOST,
                port: process.env.REDIS_PORT,
                password: process.env.REDIS_PASS,
            });
            resolve(redis);
        } catch (err) {
            reject(err);
        }
    });
    console.log("1");
    const res = await new Promise((resolve, reject) => {
        RedisClient.quit((err, res) => {
            if (err) reject(err);
            else {
                console.log("Inside the quit()");
                resolve(res);
            }
        });
    });
    console.log(res);
    console.log("2");
} catch (err) {
    console.log(err);
}

Output:
1
Inside the quit()
OK
2


Not sure it really works...

The text is "Sie warten am Straßenrand und wollen gehen. Im toten Winkel (freier hinterer Bereich) befindet sich niemand. Was möchten Sie tun…"
Here is the code for it:
TextWrapAutoSize(
  Text(
    appTest!.activeQuestion.question.text,
    style: const TextStyle(
      // fontSize: 20,
      fontFamily: 'Helvetica',
    ),
    // maxLines: 3,
  ),
  minFontSize: 1,
  maxFontSize: 20,
),

It is inside a SizedBox with height 86.
SizedBox itself is under LayoutBuilder.

I don't think the text is minimized to size 1. It looks around size 10. Actually with size 20 it reaches "Was" ( "möchten Sie tun…" is clipped ). So size 16-18 should have been ok for this.
It skips to next line after the "." I checked the data and there's no line break character or anything. Why does it start a new paragraph?
It should be max 3 lines. But if this would have worked I think there's no need to write it down. That's why it's commented.

Just tested it again.. I don't understand what's wrong. Here is the text viewed in Notepad++:

again in app it shows like this ( I also toggled debug ):

I also added replaceAll to see if there's a LF somewhere and it doesn't detect it.
I did change your code to use "Helvetica" and your program ran correctly again.

I added the Padding 8,8 to your app also to simulate the same conditions.
Only difference is innerbox, which calculates to 366 for my app, and 368 for your example app. I don't know what's the cause of that difference ( there's no border or anything in my app ).

"auto_size_text" did work. Thanks for trying to help. I don't really understand what went wrong. The only difference was I read the text from the Firebase.


sql: improve database schema handling

Motivation
Currently, the database schema is always built by running a series of migrations, even on a fresh database. There's no place in the source code to look for the full database schema in a single place. If schema drift happens for whatever reason (running dev version, a bug in a coded migration, etc.), it may go undetected causing issues at some later point in time.
Another problem is that state.sql and local.sql databases aren't being handled in a consistent manner, with sql.Open / sql.InMemory being used for the state database with its associated migrations, and localsql.Open / localsql.InMemory being derived from them. This has some unpleasant consequences, most importantly that it is hard to implement coded migrations as they'll have to be referred explicitly from node/node.go and possibly in other places.
syncv2 will require some coded migration(s) for storing synctrees in the database, and ahead of these changes, it would be nice to have this kind of refactoring done in go-spacemesh.
Description
When a new database is created, use schema script instead of running all the migrations. Also, check that there's no schema drift by diffing database schema against the schema script after running migrations.
Use consistent package/folder structure for local.sql and state.sql databases:

sql/statesql and sql/localsql handle the state db and the local db, respectively, with Schema, InMemory and Open functions provided. Coded migrations can be added to these packages, too
sql/statesql/schema/schema.sql and sql/statesql/schema/schema.sql contain current database schemas
sql/statesql/schema/migrations/*.sql and sql/statesql/schema/migrations/*.sql contain database migrations

When a new database is created, the schema snapshot from schema.sql is used to initialize it. If the database already exists, its version is checked and if it's old, the migrations are run. In both cases, the schema is retrieved from the database afterwards and diffed against the schema snapshot, logging warnings about any detected differences (schema drift).
Fixes #6026.
Test Plan
Verify on testnet and mainnet nodes
TODO

[X] Explain motivation or link existing issue(s)
[x] Test changes and document test plan
[x] Update changelog as needed

Updated the PR according to https://github.com/spacemeshos/go-spacemesh/issues/6026#issuecomment-2159063376
Additional changes made:

worked around circular dependencies in coded migrations by making sql.Database an interface with an internal implementation and introducing derived interfaces sql.StateDatabase and sql.LocalDatabase. This way, sql/statesql and sql/localsql packages are only imported by tests in most other packages and not the non-test code, and thus using most go-spacemesh packages in migrations located under sql/statesql and sql/localsql will not cause circular dependencies
moved database schema handling docs from README.md to CONTRIBUTING.md
fixed printing the error which caused the node startup to fail twice, so that docs can be prettier and still reflect the current codebase

It might make sense to move the new section in CONTRIBUTING.md to CODING.md after #6045 is merged

Moved db schema docs to CODING.md

bors merge

bors merge

bors merge

ok it seems like the problem is this PR 😕

Tried to run the systests locally, didn't observe the problem so far.
There was k8s resource-related issue with systests yesterday, so will retry one more time

bors merge

The only test that is failing, namely TestPartition_50_50 passes in my env and likely will pass in the CI env if run in isolation. There appears to be a timing-dependent problem in systests (interaction between parallel tests) that this change somehow triggers, trying to look into that

bors merge

bors merge

bors try

bors merge

bors merge

bors try

bors merge

windows unittest flake

bors merge

bors merge

Temporarily disabled malfeasance_double_marry_test.go via a build tag (circular dependency problem), will need to fix it before merging

bors try

Last bors try failed due to a flake in a unittest on Windows.
The systests have passed: https://github.com/spacemeshos/go-spacemesh/actions/runs/10368810152/job/28703211607
Doing another run to ensure stability.

bors try

bors try

@fasmat @acud @poszu pls recheck this PR after the latest changes that were needed to resolve the conflicts

Took me a bit but I made it through all changes, there is also still this comment by @poszu that is open: https://github.com/spacemeshos/go-spacemesh/pull/6003#discussion_r1654745181

Took me a bit but I made it through all changes, there is also still this comment by @poszu that is open: #6003 (comment)

Also fixed

CI rerun due:
hare_test.go:653: eligibility can't be sent, waited: 10s, stacktraces:

Likely unrelated

bors merge


ISPN-14788 Allow to retrieve cache entry metadata version using the REST API

https://issues.redhat.com/browse/ISPN-14788

@wburns and @pruivo thanks for the review, I applied the suggestions

Merged, thanks


Minor refactoring, fixes, and cleanup

Coverage increased (+3.0%) to 78.227% when pulling 212e9ffb994ead300c88e3196fe7d117acc370b5 on michakraus:master into b10cfd78794aadd40f98164498e2cb6dbcd43c37 on DDMGNI:master.


MarkerClusterer flashing/acting weird?

I tried wrapping my existing array of Marker objects in a MarkerClusterer and I'm seeing the following odd behavior (the marker clusters flash and disappear occasionally, but sometimes they just show up normally):

Is this a known issue? Any clue what's going on?

I personally don't use MarkerCluster a lot but this seems very weird. One question, do you render your <GoogleMap> in a controlled way or uncontrolled way?

Controlled. (I specify zoom and center props rather than defaults)

Does it matter if the <Marker /> instances are in an array as children of <MarkerClusterer /> instead of "naked" children? (I thought they were essentially the same)
What about if the <Makrer />s have child <InfoWindow /> instances?
let elements = [];
for (let item of iterator) {
  if (item === null) continue;
  const id = item.id;
  const position = item.position;
  elements.push(
    <Marker
      {...props}
      key={id}
      ref={`marker_${id}`}
      position={position}
    >
      { info ?
        <InfoWindow
          {...props}
          key={`${info.ref}_info`}
          owner={info.ref}
          content={info.name} />
      : null }
    </Marker>
  );
}

<MarkerClusterer>{ elements }</MarkerClusterer>

I think it should be children of <MarkerCluster />. I'm suspecting this line of code:
https://github.com/tomchentw/react-google-maps/blob/master/src/addons/addonsCreators/MarkerClustererCreator.js#L96

Also seeing this.
This is also the behavior on their demos it seems: https://googlemaps.github.io/js-marker-clusterer/examples/simple_example.html
And our implementation is using timers it seems: https://github.com/mikesaidani/marker-clusterer-plus/search?utf8=✓&q=setTimeout

@vvo I'm not seeing the problematic behavior on the demo site you linked...
@farrrr Any ideas on this?

@idolize may you give me a reproducible example for me? I think that will help me to trace.

I try to modified example to below. and everything is fine. InfoWindow works fine with MarkerClusterer
import {default as React, Component} from 'react';
import {default as fetch} from 'isomorphic-fetch';

import {GoogleMap, Marker, InfoWindow } from 'react-google-maps';
import {default as MarkerClusterer} from 'react-google-maps/lib/addons/MarkerClusterer';

export default class MarkerClustererExample extends Component {
  state = {
    markers: [],
  }

  componentDidMount() {
    fetch('https://gist.githubusercontent.com/farrrr/dfda7dd7fccfec5474d3/raw/758852bbc1979f6c4522ab4e92d1c92cba8fb0dc/data.json')
      .then(res => res.json())
      .then(data => {
        this.setState({ markers: data.photos });
      });
  }

  render() {
    const { markers } = this.state;

    return (
      <GoogleMap
        containerProps={{
          ...this.props,
          style: {
            height: '100%',
          },
        }}
        defaultZoom={ 3 }
        defaultCenter={{ lat: 25.0391667, lng: 121.525 }}>
          <MarkerClusterer
           averageCenter={ true }
           enableRetinaIcons={ true }
           gridSize={ 60 }>
           { markers.map(marker => (
             <Marker
               position={{ lat: marker.latitude, lng: marker.longitude }}
               key={ marker.photo_id }>
               <InfoWindow
                 key={ `${marker.photo_id}_info` }
                 content={ marker.photo_title } />
             </Marker>
           )) }
       </MarkerClusterer>
      </GoogleMap>
    );
  }
}

I've been doing some testing by removing chunks from my code and it seems to be related to using a controlled <GoogleMap> (where I set the new center and zoom props with a handler from onBoundsChanged).
When I remove this code (delete the onBoundsChanged) and just use the uncontrolled <GoogleMap> it works as expected. I will try to make a fiddle or sample repo.

Try this:
import {default as React, Component} from 'react';
import {default as fetch} from 'isomorphic-fetch';

import {GoogleMap, Marker, InfoWindow } from 'react-google-maps';
import {default as MarkerClusterer} from 'react-google-maps/lib/addons/MarkerClusterer';

export default class MarkerClustererExample extends Component {
  state = {
    markers: [],
    zoom: 3,
    lat: 25.0391667,
    lng: 121.525
  }

  componentDidMount() {
    fetch('https://gist.githubusercontent.com/farrrr/dfda7dd7fccfec5474d3/raw/758852bbc1979f6c4522ab4e92d1c92cba8fb0dc/data.json')
      .then(res => res.json())
      .then(data => {
        this.setState({ markers: data.photos });
      });
  }

  handleBoundsChanged = () => {
    if (!this.map) {
      // Wait for map to load
      return;
    }
    const center = this.map.getCenter();
    const zoom = this.map.getZoom();
    const stateCenter = new google.maps.LatLng(this.state.lat, this.state.lng);

    // Notice: Check equality here, or it will fire event infinitely
    if (zoom !== this.state.zoom || !center.equals(stateCenter)) {
      const lat = center.lat();
      const lng = center.lng();
      this.setState({ lat, lng, zoom });
    }
  }

  render() {
    const { markers, zoom, lat, lng } = this.state;

    return (
      <GoogleMap
        ref={ map => this.map = map }
        containerProps={{
          ...this.props,
          style: {
            height: '100%',
          },
        }}
        onBoundsChanged={ this.handleBoundsChanged }
        zoom={ zoom }
        center={ ({ lat, lng }) }>
          <MarkerClusterer
           averageCenter={ true }
           enableRetinaIcons={ true }
           gridSize={ 60 }>
           { markers.map(marker => (
             <Marker
               position={{ lat: marker.latitude, lng: marker.longitude }}
               key={ marker.photo_id }>
               <InfoWindow
                 key={ `${marker.photo_id}_info` }
                 content={ marker.photo_title } />
             </Marker>
           )) }
       </MarkerClusterer>
      </GoogleMap>
    );
  }
}

@idolize You need disable InfoWindow autoPan, because InfoWindow will autoPan by default.and it will change center always when it show.
<InfoWindow
                 options={{ disableAutoPan: true }}
                 key={ `${marker.photo_id}_info` }
                 content={ marker.photo_title } />

and everything will be fine.

@farrrr I just tried that and it did not fix the problem. In fact, I think the <InfoWindow>s were a red herring, because I can still reproduce the issue in a controlled <GoogleMap> component without any <InfoWindow>s.

@idolize I will build an online example for u when I back home.

@idolize I made an example here: https://farrrr.github.io/react-google-maps/#basics/marker-clusterer

I suggest change zoom / center to defaultZoom / defaultCenter, because when u move map, it will trigger
handleBoundsChanged serval times, so it made map always repaint. You still can use zoom / center props, but it will be laggy.

@farrrr I just feel some laggy for your example provided. Will adding _.debounce to handleBoundsChanged help?

@tomchentw yep, you are right, I update the example :)

I see the exact same problem. My Map is controlled as well, and after a 2nd render the MarkerClusterer disappears. I noticed that when I then pan the map it will trigger an google maps 'idle' event which in turn triggers a redraw() on the clusterer and it appears again.

Ok, I think I found the problem. Because the zoom property is controlled, the map will generate a zoom_changed when redrawn, but it never generates the idle event. So the viewport is reset, but it is never redrawn.

Ok, I think I found the problem. Because the zoom property is controlled, the map will generate a zoom_changed when redrawn, but it never generates the idle event. So the viewport is reset, but it is never redrawn.

@hmeerlo @lauffenp do you think that this need to be fixed in react-google-maps?

@tomchentw I think it should be fixed, but I have no idea if it is an easy fix. I reverted to the uncontrolled zoom property which was good enough for me.

We're going to look into this shortly.
We're also looking for maintainers. Involve in #266 to help strengthen our community!

I will check it this week...

Has anyone gotten this to work with a controlled map?

Hey, I got this working.
The trouble is indeed with the controlled zoom. react-google-maps sends a map.setZoom(props.zoom) at every render, even when map.getZoom() === props.zoom.
I fixed the situation by doing this:

Changed to an uncontrolled zoom.

            <GoogleMap ref={this.mapRendered}
                       zoom={zoom}
                       center={center} .../

to
            <GoogleMap ref={this.mapRendered}
                       defaultZoom={zoom}
                       center={center} ... /

Store a reference to map in this.mapRendered
In componentWillReceiveProps (nextProps) do this:

    if (map && map.getZoom() !== nextProps.zoom) {
      map.setZoom(nextProps.zoom)
    }

And it works.

@mariusandra Awesome! Can you make a PR to handle this directly in the library so developers won't have to worry about doing this themselves if they use a controlled component?

Oh @mariusandra you made my day! Thank you very much. It works like a charm. Willing to see a PR linked to this issue so other devs won't be digging around any longer.

Would love to see an ultimate solution to get rid of this controlled/uncontrolled hell……

@idolize Hi, does your info window also works for the clustered markers, i m trying to do the same but it works only for one marker not for clustered markers. Please help me if you have any idea how can i show info windows for the clustered markers as well.

Just to let you know 6.0.0 is released on npm beta tag now. We also have a new demo page. Feel free to try it:
https://tomchentw.github.io/react-google-maps/

I had this issue when using fitBounds using refs on the <GoogleMap /> component. It's fine if I wrap fitBounds in Ramda's once so that we only fit to bounds once — which does it make sense. After that it's perfectly fine.
const fitBounds = once((map, bounds) => map.fitBounds(bounds));

// ...

<GoogleMap ref={map => map && fitBounds(map, bounds)} />