VM dynamic scaling option granularity

Description
This PR introduces new granularity levels to configure VM dynamic scalability. Previously VM is configured to be dynamically scalable based on the template and global setting. Now we bringing this option to configure at service offering and VM level also.
VM can dynamically scale only when all flags are ON at VM level, template, service offering and global setting. If any of the flags is set to false then VM cannot be scalable. This result will be persisted in DB for each VM and will be honoured for that VM till it is updated.
We are introducing 'dynamicscalingallowed' parameter with permitted values of true or false for deployVM API and createServiceOffering API.
Following are the API parameter changes:
createServiceOffering API:
dynamicscalingenabled: an optional parameter of type Boolean with default value “true”.
deployVirtualMachine API:
dynamicscalingenabled: an optional parameter of type Boolean with default value “true”.
Following are the UI changes:
Service offering creation has ON/OFF switch for dynamic scaling enabled with default value true.

Deploy VM wizard has ON/OFF switch for dynamic scaling enabled with default value true in Advanced Mode section.

Added a documentation PR to support these changes
https://github.com/apache/cloudstack-documentation/pull/186

Types of changes

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

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[x] Major
[ ] Minor

Bug Severity

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

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

Following are the test cases that I've covered as part of my testing on VMware environment.
VM Creation:

Created VM with Small service offering with all Flags ON
- VM1 (scalable)
Created VM with Small service offering which is not dynamic, with Dynamic Scaling Enabled true on VM
- VM2 (not scalable)
Created VM with Small service offering, with Dynamic Scaling Enabled false on VM
- VM3 (not scalable)
Created VM with Small service offering which is not dynamic, with Dynamic Scaling Enabled false on VM
- VM4 (not scalable)
Created VM with Small service offering with all dynamic flags ON except template
-  VM5 (not scalable)

VM Update:

Stop VM1 => set Dynamic Scaling Enabled to false => Update VM
- VM is updated to Dynamic Scaling Enabled value false
Stop VM2 or VM3 or VM4 or VM5 => set Dynamic Scaling Enabled to true => Update VM
- VM update operation fails because VM cannot be scaled with any of the template/service offering/global setting dynamic scaling enabled flag with false

VM dynamic Scaling:
While trying to scale VM from UI, it will only list service offering that are suitable to scale and also offering with "Dynamic Scaling Enabled" value same as old service offering.

Create Big Service Offering with Dynamic Scaling Enabled true
- SO1
Create Big Service Offering with Dynamic Scaling Enabled false
- SO2
Scale VM1 (scalable) to Service Offering SO1
- Successful
Scale VM1 (scalable) to Service Offering SO2
- Operation failed because, VM1 Service Offering is marked Dynamic Scaling Enabled but not on SO2

@blueorangutan package

@harikrishna-patnala a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos7 ✔centos8 ✔debian. JID-2641

@blueorangutan ui

@rhtyd a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/4643 (JID-3830)

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/4643 (JID-3831)

@blueorangutan package

@harikrishna-patnala a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos7 ✔centos8 ✔debian. JID-2648

@blueorangutan test matrix

@harikrishna-patnala a Trillian-Jenkins matrix job (centos7 mgmt + xs71, centos7 mgmt + vmware65, centos7 mgmt + kvmcentos7) has been kicked to run smoke tests

Trillian test result (tid-3491)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 33095 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr4643-t3491-kvm-centos7.zip
Smoke tests completed. 86 look OK, 0 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

Trillian test result (tid-3490)
Environment: xenserver-71 (x2), Advanced Networking with Mgmt server 7
Total time taken: 33415 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr4643-t3490-xenserver-71.zip
Intermittent failure detected: /marvin/tests/smoke/test_scale_vm.py
Smoke tests completed. 85 look OK, 1 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_01_scale_vm
Failure
11.62
test_scale_vm.py

Trillian test result (tid-3492)
Environment: vmware-65u2 (x2), Advanced Networking with Mgmt server 7
Total time taken: 39835 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr4643-t3492-vmware-65u2.zip
Intermittent failure detected: /marvin/tests/smoke/test_kubernetes_clusters.py
Intermittent failure detected: /marvin/tests/smoke/test_service_offerings.py
Intermittent failure detected: /marvin/tests/smoke/test_vm_snapshots.py
Smoke tests completed. 84 look OK, 2 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_03_deploy_and_upgrade_kubernetes_cluster
Failure
778.21
test_kubernetes_clusters.py

test_change_service_offering_for_vm_with_snapshots
Error
140.93
test_vm_snapshots.py

These failed test cases are commonly seen on all PRs, not related to this PR changes.
test_01_scale_vm on XenServer is failing with License error

@blueorangutan ui

@sureshanaparti @Pearl1594 @nvazquez I've addressed your comments and updated the code as per the suggestions. Please review.

@blueorangutan package

@harikrishna-patnala a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos7 ✔centos8 ✔debian. JID-2657

@blueorangutan package

@harikrishna-patnala a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos7 ✔centos8 ✔debian. JID-2659

@blueorangutan test matrix

@harikrishna-patnala a Trillian-Jenkins matrix job (centos7 mgmt + xs71, centos7 mgmt + vmware65, centos7 mgmt + kvmcentos7) has been kicked to run smoke tests

Trillian test result (tid-3513)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 32281 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr4643-t3513-kvm-centos7.zip
Smoke tests completed. 86 look OK, 0 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

Trillian test result (tid-3512)
Environment: xenserver-71 (x2), Advanced Networking with Mgmt server 7
Total time taken: 33403 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr4643-t3512-xenserver-71.zip
Intermittent failure detected: /marvin/tests/smoke/test_reset_vm_on_reboot.py
Intermittent failure detected: /marvin/tests/smoke/test_scale_vm.py
Intermittent failure detected: /marvin/tests/smoke/test_vpc_vpn.py
Smoke tests completed. 84 look OK, 2 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_01_scale_vm
Failure
9.31
test_scale_vm.py

test_01_vpc_site2site_vpn
Failure
272.17
test_vpc_vpn.py

Trillian test result (tid-3514)
Environment: vmware-65u2 (x2), Advanced Networking with Mgmt server 7
Total time taken: 38210 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr4643-t3514-vmware-65u2.zip
Intermittent failure detected: /marvin/tests/smoke/test_kubernetes_clusters.py
Smoke tests completed. 85 look OK, 1 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_03_deploy_and_upgrade_kubernetes_cluster
Failure
801.70
test_kubernetes_clusters.py

@harikrishna-patnala code LGTM, just check and confirm on the test failures above.

Thanks @sureshanaparti.
Test failures are not related this PR changes and are common on all other PRs.
test_01_scale_vm on XenServer is failing with License issues. So I've manually ran it on my setup to check the actual result and it passed.

@blueorangutan package

@harikrishna-patnala a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos7 ✔centos8 ✔debian. JID-2670

@blueorangutan package

@harikrishna-patnala a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos7 ✔centos8 ✔debian. JID-2678

Packaging result: :heavy_multiplication_x: centos7 :heavy_multiplication_x: centos8 :heavy_multiplication_x: debian. SL-JID 188

@harikrishna-patnala can you address the conflicts, please?

@harikrishna-patnala can you address the conflicts, please?

Resolved conflicts.

@blueorangutan package

@harikrishna-patnala a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: :heavy_multiplication_x: centos7 :heavy_multiplication_x: centos8 :heavy_check_mark: debian. SL-JID 199

@blueorangutan package

@harikrishna-patnala a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: centos7 :heavy_check_mark: centos8 :heavy_check_mark: debian. SL-JID 203

Trillian Build Failed (tid-221)

Trillian Build Failed (tid-222)

Trillian test result (tid-231)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 35496 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr4643-t231-kvm-centos7.zip
Intermittent failure detected: /marvin/tests/smoke/test_vm_life_cycle.py
Smoke tests completed. 85 look OK, 1 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_01_migrate_VM_and_root_volume
Error
78.45
test_vm_life_cycle.py

test_02_migrate_VM_with_two_data_disks
Error
51.14
test_vm_life_cycle.py

Trillian Build Failed (tid-449)

Trillian Build Failed (tid-450)

@blueorangutan package

@harikrishna-patnala a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: centos7 :heavy_check_mark: centos8 :heavy_check_mark: debian. SL-JID 496

@blueorangutan package

@harikrishna-patnala a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: centos7 :heavy_check_mark: centos8 :heavy_check_mark: debian. SL-JID 77

@blueorangutan test matrix

@DaanHoogland a Trillian-Jenkins matrix job (centos7 mgmt + xs71, centos7 mgmt + vmware65, centos7 mgmt + kvmcentos7) has been kicked to run smoke tests

Trillian test result (tid-736)
Environment: xenserver-71 (x2), Advanced Networking with Mgmt server 7
Total time taken: 41906 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr4643-t736-xenserver-71.zip
Intermittent failure detected: /marvin/tests/smoke/test_privategw_acl.py
Intermittent failure detected: /marvin/tests/smoke/test_templates.py
Smoke tests completed. 87 look OK, 1 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_09_list_templates_download_details
Failure
0.04
test_templates.py

Trillian test result (tid-737)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 49630 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr4643-t737-kvm-centos7.zip
Intermittent failure detected: /marvin/tests/smoke/test_kubernetes_clusters.py
Intermittent failure detected: /marvin/tests/smoke/test_network.py
Intermittent failure detected: /marvin/tests/smoke/test_service_offerings.py
Smoke tests completed. 86 look OK, 2 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_reboot_router
Failure
445.76
test_network.py

test_01_invalid_upgrade_kubernetes_cluster
Failure
3613.38
test_kubernetes_clusters.py

test_02_deploy_and_upgrade_kubernetes_cluster
Failure
3613.45
test_kubernetes_clusters.py

test_03_deploy_and_scale_kubernetes_cluster
Failure
0.05
test_kubernetes_clusters.py

test_04_basic_lifecycle_kubernetes_cluster
Failure
0.05
test_kubernetes_clusters.py

test_05_delete_kubernetes_cluster
Failure
0.05
test_kubernetes_clusters.py

test_07_deploy_kubernetes_ha_cluster
Failure
0.05
test_kubernetes_clusters.py

test_08_deploy_and_upgrade_kubernetes_ha_cluster
Failure
0.05
test_kubernetes_clusters.py

test_09_delete_kubernetes_ha_cluster
Failure
0.05
test_kubernetes_clusters.py

ContextSuite context=TestKubernetesCluster>:teardown
Error
98.92
test_kubernetes_clusters.py

@blueorangutan package

@harikrishna-patnala a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: centos7 :heavy_check_mark: centos8 :heavy_check_mark: debian.  LGTM

@blueorangutan test centos7 vmware-67u3

@DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + vmware-67u3) has been kicked to run smoke tests

@blueorangutan test centos7 kvm-centos7

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

the scaling tests in Travis are due to the template not being marked scalable in the test env. This error seems relted but is happening on other PRs as well so I don't consider it a blocker for this PR.

Trillian test result (tid-762)
Environment: vmware-67u3 (x2), Advanced Networking with Mgmt server 7
Total time taken: 36813 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr4643-t762-vmware-67u3.zip
Intermittent failure detected: /marvin/tests/smoke/test_router_dhcphosts.py
Smoke tests completed. 88 look OK, 0 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

Trillian test result (tid-763)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 72997 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr4643-t763-kvm-centos7.zip
Intermittent failure detected: /marvin/tests/smoke/test_kubernetes_clusters.py
Intermittent failure detected: /marvin/tests/smoke/test_privategw_acl.py
Intermittent failure detected: /marvin/tests/smoke/test_reset_vm_on_reboot.py
Intermittent failure detected: /marvin/tests/smoke/test_resource_accounting.py
Intermittent failure detected: /marvin/tests/smoke/test_router_dhcphosts.py
Intermittent failure detected: /marvin/tests/smoke/test_router_dns.py
Intermittent failure detected: /marvin/tests/smoke/test_router_dnsservice.py
Intermittent failure detected: /marvin/tests/smoke/test_routers_iptables_default_policy.py
Intermittent failure detected: /marvin/tests/smoke/test_routers_network_ops.py
Intermittent failure detected: /marvin/tests/smoke/test_routers.py
Intermittent failure detected: /marvin/tests/smoke/test_service_offerings.py
Intermittent failure detected: /marvin/tests/smoke/test_snapshots.py
Intermittent failure detected: /marvin/tests/smoke/test_vm_snapshots.py
Intermittent failure detected: /marvin/tests/smoke/test_vpc_redundant.py
Smoke tests completed. 76 look OK, 12 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_03_vpc_privategw_restart_vpc_cleanup
Failure
370.64
test_privategw_acl.py

ContextSuite context=TestResetVmOnReboot>:setup
Error
0.00
test_reset_vm_on_reboot.py

ContextSuite context=TestRAMCPUResourceAccounting>:setup
Error
0.00
test_resource_accounting.py

ContextSuite context=TestRouterDHCPHosts>:setup
Error
0.00
test_router_dhcphosts.py

ContextSuite context=TestRouterDHCPOpts>:setup
Error
0.00
test_router_dhcphosts.py

ContextSuite context=TestRouterDns>:setup
Error
0.00
test_router_dns.py

ContextSuite context=TestRouterDnsService>:setup
Error
0.00
test_router_dnsservice.py

ContextSuite context=TestRouterIpTablesPolicies>:setup
Error
0.00
test_routers_iptables_default_policy.py

ContextSuite context=TestVPCIpTablesPolicies>:setup
Error
0.00
test_routers_iptables_default_policy.py

ContextSuite context=TestIsolatedNetworks>:setup
Error
0.00
test_routers_network_ops.py

ContextSuite context=TestRedundantIsolateNetworks>:setup
Error
0.00
test_routers_network_ops.py

ContextSuite context=TestRouterServices>:setup
Error
0.00
test_routers.py

ContextSuite context=TestCpuCapServiceOfferings>:setup
Error
0.00
test_service_offerings.py

ContextSuite context=TestServiceOfferings>:setup
Error
0.12
test_service_offerings.py

ContextSuite context=TestSnapshotRootDisk>:setup
Error
0.00
test_snapshots.py

test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers
Failure
399.75
test_vpc_redundant.py

test_05_rvpc_multi_tiers
Failure
505.79
test_vpc_redundant.py

There is a test failure in the simulator environment, I've fixed it in the last commit. All checks for good now.

Packaging result: :heavy_check_mark: centos7 :heavy_check_mark: centos8 :heavy_check_mark: debian. SL-JID 108

@blueorangutan test matrix

Trillian Build Failed (tid-773)

@blueorangutan package

@harikrishna-patnala a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: centos7 :heavy_check_mark: centos8 :heavy_check_mark: debian.


Template import precedence

Currently OntClassMatcher has only 2 priority levels for templates: templates from the main sitemap have higher priority than those from the imported ontologies. The import tree/hierarchy is not taken into account. The mechanism should probably be more like the XSLT import precendence:
http://www.w3.org/TR/xslt20/#dt-import-precedence

This issue probably also involves some kind of default template rules, such as those in the GP vocabulary. Here's the equivalent in XSLT: http://www.w3.org/TR/xslt20/#built-in-rule


Restrict api.newspring.cc to be closed to public traffic

This should be only accessible by the applications in the same vpc

keeping this alive for the beta app but its really easy to do with rancher


Logo is too big

Can you make a logo smaller. 43Kb for a logo is a little bit to much.
For the readme you can still use a bigger picture.

Resized the logo to 128px x 128px and (8kb)


Disable send message button while waiting for bot to response

Hi,
I'm looking for solution to disable send message button while waiting for bot to response.
Because when user type multiple messages, bot will now reply it multiple times that might add confusion to user.
For example:
User: Hi
User: I have an issue with my computer
User: I cannot logged in properly
User: I'm using surface pro 6 with windows 10 OS
In this case, bot will reply it multiple times:
Bot: Hi, how can I help you? (replying to user's first message)
Bot: Do you mean "issue with laptop", "issue with surface"? (replying to user's second message)
Bot: Hi, I can help you with that. What is your device type? (replying to user's third message)
Bot: Sorry, I don't understand that. (replying to user's fourth message)
It will add lots of confusion to user because the answer that bot provided are different for every single message from the user.
Thanks

@aldvintumbelaka, what channel is this for? It sounds like Web Chat, but can you clarify? Whether a button is enabled / disabled is a feature of the hosting site and not of the bot.

@aldvintumbelaka, what channel is this for? It sounds like Web Chat, but can you clarify? Whether a button is enabled / disabled is a feature of the hosting site and not of the bot.

@stevkan it will be for microsoft teams

@stevkan it will be for microsoft teams

@aldvintumbelaka, disabling a button that is specific to the Teams UI falls outside the functionality of the BotFramework. You will need to communicate with the Teams development team to determine if this is even possible, or to suggest as a feature request. Their community forum can be located at Teams UserVoice.

@aldvintumbelaka, disabling a button that is specific to the Teams UI falls outside the functionality of the BotFramework. You will need to communicate with the Teams development team to determine if this is even possible, or to suggest as a feature request. Their community forum can be located at Teams UserVoice.


STAR-233 Update to new apache/cassandra-dtest trunk as of 20210301 by merging

This PR shows all of the changes to be merged in from OSS trunk as of 20210301.
DO NOT MERGE THIS PR.
There are no DS only commits, so the PR by rebasing has no changes from trunk as there is nothing to rebase.
fast-ci run: https://jenkins-stargazer.build.dsinternal.org/job/ds-cassandra-build-fast-ci/24/

LGTM


server: Some redis queue refactorings

Motivation
Preparation for omniqueue integration, in particular solves the problem discussed here.
Solution
Refactor redis queue implementation to not take TaskQueueDelivery parameter in ack, nack methods, instead only taking references to the fields it is interested in, specifically excluding the acker field (such that it can be borrowed mutably when calling one of these methods).
Additionally, I improved one of the methods to use implicit named format arguments.

Unsure whether the test failure is related. Couldn't run tests locally, #1186 is related but not the full solution (I also got a timeout from the webhooks server after that); but also there's a clearly-unrelated CI failure there so maybe this is also flakiness? Any ideas appreciated, though at first I'll also try re-running CI for this.


Do you have a plan to add networking to the API?

Describe the feature
Excuse me, do you have plans to add networking capabilities for ChatGPT API?
like this: https://github.com/tobiasbueschel/search-gpt

No plan at the moment; it's a really cool feature, but I think it's out of scope for now. You can always implement the search / networking logic on top of the chatgpt package.
Thanks! 🙏


Add websockets support

screenshot from wireshark for websockets integration spec where client server perform ping pong.

Closing this in favor of #158


[TW#15842] Preferences Library getString problem

Reading a string from Preferences library through getString(char *, char *, size_t nmax) without giving third argument causes it to fail. I am using latest esp32 Preferences lib which I downloaded yesterday.
Thanks
Shashank

Maybe you meant to post this in the Arduino repo? Those arguments do not have default values, so you need to provide them all.

Closing as not IDF related.


Add baker with empty URL fails

Bug Description
Add baker with empty URL fails.
Steps to Reproduce
Add baker, leave URL empty.
Expected Result
This should be possible.
Actual Result
Transaction fails
Versions

Software Version: 3.0.0(47)
OS: iOS

Fixed in build 48

Verified in 3.0.0(48)


Fix #1293 Add customizable TOC title class

This appears to be an implementation of the feature requested in #1293. What happens here depends on what decision is made there.

Given the decision made in #1293, I will not be accepting this as-is. However, I am not opposed to including the new config option to allow the user to define the class assigned to the title. After all, we already allow various other classes to be set by the user. Might as well include this one too.
If this is updated (with all checks passing), then I would be happy to accept it. If no action is taken, it will likely be closed.

I'll try to work on that in may because tomorrow I'm leaving to go to PyCon US.

The tests will need to all be passing before we can accept this. Also, the release notes and the documentation need to be updated appropriately.

The tests will need to all be passing before we can accept this. Also, the release notes and the documentation need to be updated appropriately.

@waylan I fixed test failures and updated the documentation


Allow STM input for Python interface

PR motivation:
CLI supports a common input format for each WER type.
The python code uses the WER specific input type (i.e. the natural input format for each WER type, e.g. for cpWER it is one transcript for each speaker without timing information, while tcpWER expect words or short segments with timing information).
It is not that easy to get the input format with the first try correct (Especially ORC, MIMI and tcp).
Now: With the STM interface, each WER has a high level interface and STM is well defined.

Took some time to find it.

On https://github.com/nryant/dscore I found channel (1-indexed) that turn is on; should always be 1. (Currently, the best argument to select a default, because it is the only argument)
From the RWTH I saw an STM file and there was the default 1.
In ESPnet I saw some rttm files and they have as default 1.

While that is not a strong argument, it is at least an argument to select one over another.

They are accessible via, e.g., meeteval.wer.wer.cp.cp_word_error_rate_stm. But not directly under meeteval.wer. I'll add the import there


Not supported cleanup

This PR makes graph and geometry functions that will not be supported by our driver throw a ReferenceError with a relevant error message. Code from index.d.ts in this modules was also deleted to cause TypeScript to throw compilation error if someone wants to use those functions. Datastax tests for graph and geometry methods were deleted.

I can see that tests are failing, which makes sense because we deleted the tested functions. Two things:

Let's take a look at https://github.com/scylladb-zpp-2024-javascript-driver/scylladb-javascript-driver/actions/runs/11462837301/job/31895202380?pr=34 and verify that what we is what would like the user to see.
Let's disable (delete) the tests related to the functionality removed in this PR, because we want the CI to pass for this PR and subsequent ones. After that, that's the point of having CI: its failures should be meaningful, signalling that's something's wrong with the PR.

Remember to update this readme:
https://github.com/scylladb-zpp-2024-javascript-driver/scylladb-javascript-driver/blob/c42672cd2856672dfe003ed9a6bd59f9f5eb4c79/README.md?plain=1#L64-L73

Remember to rebase onto main ;)
Also maybe consider to move all files to some compatibility catalog (what Kuba suggested today)?
Do you want to squash whole PR, or to edit the history of this PR?


Configure the duration of each screen

Hi, first of all thank you for your screen saver, it is much appreciated :)
Here is one feature request, event if I do not know the feasability
Some screens are very short, i would like to know if it can be configurable to loop them
Describe the solution you'd like
In the configuration menu, maybe add an input which takes an integer as second
The related screen will then loop this amount of second
Feel free to close this issue if it is not doable :)
Cheers!

Hello @noniagriconomie and welcome here! Glad you enjoyed 😄
Configuring seconds isn't very doable because most of them have different lengths. That's why that option is called "number of loops" -  it ignores how long the animation is, it just loops in N times.
What could be an animation would be selecting how much loops each animation does individually but I'm afraid that would be would make the panel look like a mess. I'm closing this for now, but maybe we can revisit this in the future.


Removing multiple spaces using regex not working in Python

API
Python
Description
The common regex to match an arbitrary number of spaces is \s+. When using the Python API in Kùzu, this doesn't seem to work. I'm unsure if this is due to passing the regular expression from Python into the C++ layer, or if the functionality isn't implemented at the C++ level.
Here's what I'm trying to do. I have this JSON file persons.json:
[
  {
    "name": "Xavier Williams",
    "date_of_birth": "1989-06-28",
    "residence": {
      "address": "901  Oak    Lane",
      "city": "San Francisco",
      "state": "CA",
      "zip_code": "94122"
    }
  }
]

I want to generate a unique string primary key that's a concatenation of all the address fields, that I can then use for relationship creation downstream.
During this process, I want to remove all whitespaces, and as seen in the raw data example above, there's an arbitrary number of white space characters in the string 901  Oak    Lane.
I'm doing this right now:
LOAD FROM 'persons.json'
WITH DISTINCT residence AS r
RETURN
    concat(
        regexp_replace(lower(r.address), '\s+', ''),
        regexp_replace(lower(r.city), '\s+, ''),
        regexp_replace(lower(r.state), '\s+', ''),
        r.zip_code
    ) AS id,
    r.address,
    r.city,
    r.state,
    r.zip_code

And I get this error:
/Users/prrao/code/ingest_kuzu.py:73: SyntaxWarning: invalid escape sequence '\s'
  conn.execute("""
Traceback (most recent call last):
  File "/Users/prrao/code/ingest_kuzu.py", line 73, in <module>
    conn.execute("""
  File "/Users/prrao/code/.venv/lib/python3.12/site-packages/kuzu/connection.py", line 130, in execute
    _query_result = self._connection.query(query)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
RuntimeError: Parser exception: Invalid input <concat(
                regexp_replace(lower(r.address), '>: expected rule oC_ProjectionItem (line: 7, offset: 49)
"                regexp_replace(lower(r.address), '\s+', ''),"

If I were to run the same regexp replacement in pure Python, it would work as intended.
>>> import re
>>> original_string = "901  Oak    Lane"
>>> cleaned_string = re.sub(r'\s+', '', original_string).strip().lower()
>>> cleaned_string
'901oaklane'

@mewim Do you think it's because we need to parse the regex pattern as a raw string in Python before sending to C++?

This issue can be closed once we implement the "global" option to the regexp_replace function as per #4331.
This is how it's looks in DuckDB (all spaces are removed):
D select regexp_replace('901  Oak    Lane', '\s', '', 'g');
┌───────────────────────────────────────────────────┐
│ regexp_replace('901  Oak    Lane', '\s', '', 'g') │
│                      varchar                      │
├───────────────────────────────────────────────────┤
│ 901OakLane                                        │
└───────────────────────────────────────────────────┘

Done in #4375


Salvaged semver work

:broken_heart: Test failed - status-travis

@Eh2406 no worries, it was worth trying to do.

@bors: r=Eh2406 1606ab3a7

:hourglass: Testing commit 1606ab3a79384c330f3d0f52184ec0fd4055a0fc with merge e593efc9cb987aa218e89dfca1aa915ccab77e88...

:sunny: Test successful - status-appveyor, status-travis
Approved by: Eh2406
Pushing e593efc9cb987aa218e89dfca1aa915ccab77e88 to master...


add from_slice trait to ease arrow2 migration

Which issue does this PR close?
Closes #.
Rationale for this change
Per #1556 - this trait is added to ease migration to arrow2:

PrimitiveArray::from vec can be replaced with PrimitiveArray::from_slice with a slice

What changes are included in this PR?

Are there any user-facing changes?

Thank you @Jimexist


New Configure Options

Change compartment color
Change compartment visibility
Change reaction centroid visibility

Change default effect?

Checkbox for remove text halo


Feature Request

Hello,
First of all, thank you for the sample project. I will use it in my own project. I think it would be good to add additional features to be more useful to people who will use it in the future.
Useful features;

It can be effective that it supports image formats like "Png","Jpg" besides Svg format.
Adding space between rows and columns can improve the quality of the view.
The area can be adjusted to be scrollable left and right.

On no2. I think you just set the seat state to SeatState.empty, it works.

How to limit seat that clicked for example I buy 2 ticket and after I select 2 seat I can't select others unless I deselect my seat?

@zidniryi I think you need to direct this. You should not allow a new election if your access to selected seats is more than 2 currently selected seats.

I think you need to direct this. You should not allow a new election if your access to selected seats is more than 2 currently selected seats.

How? cause there is no props like MaxLimit and where should I implement this??

Because every version of book_my_seat depends on flutter_svg ^1.0.2 and blubrain depends on flutter_svg ^2.0.5, book_my_seat is forbidden.
So, because blubrain depends on book_my_seat any, version solving failed.
can you update it to the latest version of svg

Hello,
First of all, thank you for the sample project. I will use it in my own project. I think it would be good to add additional features to be more useful to people who will use it in the future.
Useful features;

It can be effective that it supports image formats like "Png","Jpg" besides Svg format.
Adding space between rows and columns can improve the quality of the view.
The area can be adjusted to be scrollable left and right.

The spacing between the rows and columns is really important. My seatwidgets seem packed together, and I'm left with no option than to strip the code and implement some margin between the widgets


Allow raw sending of form fields?

Hi, First of all, sorry if this isn't the right place to ask this question, please close it/move it elsewhere if this is irrelevant here.
I m trying to replace traditional curl calls to a prestashop server (using this provided library ) with artax async calls.
GET requests are ok but i m having trouble when posting XML. With Artax i do the following :
$body = new FormBody();
$body->addField('',$rawxml);

The problem seems to be that the server does not accept the encoded XML string:

String could not be parsed as XML

even if the content-type IS x-www-form-urlencoded when using the prestashop server standard library, it only accepts it as raw.
As a test, i tried to change getFormEncodedBodyString() in FormBody.php
`    private function getFormEncodedBodyString(): string {
$fields = [];
    foreach ($this->fields as $fieldArr) {
        list($name, $value) = $fieldArr;
        $fields[$name][] = $value;
    }

    foreach ($fields as $key => $value) {
        $fields[$key] = isset($value[1]) ? $value : $value[0];
    }
      return implode("&",$fields);
    //return \http_build_query($fields);
}`

That simple change made the 3rd party API accept the request.
So i know, it is not an Artax issue, but do you think allowing raw sending of form fields via an option is something that could make sense in some cases or not?

You need to set the body directly, it's not supposed to be a form, i.e. $request->setBody($rawXml);.

Works like a charm, Thanks a lot!


Add Vasudev Jaiswal

Add my profile data
Resolve #641

I've linked the issue #641 in the pr description thus it will automatically gets closed on pr merge.

Problem Resolved 😊
Thanks @Panquesito7


Parallelisation

Hi,
Was wondering - for each element in the batch, does the current algorithm automatically parallelise? I have an RTX3090 (with 24 GiB) and I run out of memory instantly for a sequence anything longer than 512 samples.
I was wondering if CUDA is trying to parallelise across each sequence in the batch automatically - if so, I think it's be good to run them in series if there isn't enough memory, seeing as they should be independent. It seems DTW inherently has high memory use, and I'd rather have the loss take longer than be limited in my sequence length if this is the case and that's possible.
Cheers

Hello @stellarpower ,
if you are running into memory issues, I would recommend to reduce the batch size until your data fits into GPU memory.
With a batch of one and a length of 512 (i.e. [1, 512]), you do not run into this issue, right?

I think I don't, although if the sequences in the batch are independent, is it possible to do it in such a way that they don't all consume the resources if there's room to loop through one by one (or several at a time) instead? I.e. if I have a batch size of 16, and there's memory to compute 8 at a time, can we do two iterations and then just sum the result?
I think the problem I hit after that, which was more of a concern, was running out of resources for longer sequences - the overall GPU memory was fine, but, I assume the thread limit or memory for the kernel was exhausted, with a batch size of 1.

I would rather have the host making sure that they make calls with adapted batched size.

Afraid I'm not sure what you mean by adapted batch size; does Torch change the batch size dynamically at times? I have not seen this in Tensorflow.
But this is what I was wondering, is there a motivating reason for handling all the sequences in the batch in the kernel? I would've thought if the kernel just handles one, then the framework would be able to handle sensible decisions about how to parallelise them and queue up in pipelines, freeing it from being an issue. I haven't been able to stress-test the Keras one yet, but I am hoping that as I handle each sequence separately, given Tensorflow works on the atomic unit of "Ops", it will be smart enough to queue everything up in a way that prevents memory exhaustion when it knows it can parallelise. At the top level I have a map over the sequences in the batch, so it seems reasonably hopeful that will be the case.
Are longer sequences limited by the CUDA kernel/thread memory limits mentioned in Maghoumi's version? Or just by total available memory? For particular my network, a sequence length of 512 will be quite limiting, so I may still look into writing a kernel in C++ if it learns but needs further optimisations.

Unless that is the case, I'll close this issue?

Feel free, I don't know if you want to enable the Q&A feature on the repository, as was more of a question right now than a request, and this could be moved over there. I think a limited batch length could be an issue for my project, but as I'm mostly using Tensorflow then I don't have as much a reason myself to need it for the meantime.
BTW whilst I am here, do you think it would be possible to add a quick example of obtaining the full gradients to the readme? I am getting a difficult bug where my implementation is differing from yours and the other Torch versions in the gradients, but only when gamma != 1.0. The intermediate matrices are all within numerical precision, so I'm not sure if I am using the gradient tape properly. This is what I have, I am looking at the tests right now to see if it looks the same:
lossesPerSequenceGraph = sdtw(y_true, y_pred)

lossesPerSequence = lossesPerSequenceGraph.detach().numpy()

# Have to call sum before running the backwards pass.
lossesPerSequenceGraph.sum().backward()

# We only want the gradient on y_pred; y_true is constant and thus doesn't affect them.
torchGradients = y_pred.grad

Thanks

Edit: Looks like I have to call y_pred.grad.zero_() explicitly after calculating for each value of gamma; then the numbers match between the two implementations, so I had it right in the Keras version all along. That was a very annoying loss of a day :rofl:

Am I also missing something on the memory use?
Let's say I have data of (16, 512, 1). For each sequence, with float32 that's then:

just over 1M for the loss matrix in the forward pass
same for the distance matrix
same for the alignment matrix

So if we do everything at the same time that's to the order of megabytes per batch, and yet I'm able to exhaust the 24G of memory on my 3090 by increasing either the batch size or the sequence length. So presumably I've missed something in this model of what the algorithm is doing (?)


[Gigasecond] Implementation

Ping @ErikSchierboom as I think this is valid -- prove passes all the tests locally. :D
I know @kytrinyx made some changes to the documentation since and if doesn't gel then I'm happy to rework it.
It would be great if draft PRs could still run so we can still check them for validity.

Thanks for reopening @m-dango ! :D
Is this perhaps failing because the new rakudo-star version 2023.02 is pending? ( The compile now requires a newer version of perl or perl subs enabled. )

@habere-et-dispertire Yes, unfortunately there was a dependency for prove6 missing when the last version of Rakudo Star was built. I'm looking into now bumping the docker image to the new version of Rakudo Star.

Great -- looks like the new docker image has arrived. Thanks @m-dango 🍡 !
How do we restart the checks here ?

Great -- looks like the new docker image has arrived. Thanks @m-dango dango ! How do we restart the checks here ?

I restarted the checks.

I don't know too much about MacOS but it seems an older version of Rakudo Star is being installed than what the latest available is? (2022.12 instead of 2023.02).

I'd like to help. Let me know if I can look into anything. 👍
FWIW, after compiling and installing Rakudo Star on my macOS system, prove6 seems okay:
$ prove6 --version

prove6 0.0.12 with TAP::Harness 0.3.5 on rakudo (2023.02)

Any update ?
Thanks everyone !
:D

Workflows failing due to reasons unrelated to these changes. One of them is addressed here: https://github.com/exercism/raku/pull/600

Does 2023-04 (just out) perhaps address the remaining issues ?  prove6 appears still available, at least on macOS:
~/rakudo/bin $ prove6 --version
prove6 0.0.12 with TAP::Harness 0.3.5 on rakudo (2023.04)

Thanks ❣


grpc connection errors

The client needs to get status of the cluster periodically (every second). And it got this error:
2016/03/02 17:49:00 Failed to dial <IP_ADDRESS>:1278: grpc: the client connection is closing; please retry.
2016/03/02 17:49:01 grpc: Conn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp <IP_ADDRESS>:1278: connect: cannot assign requested address"; Reconnecting to "<IP_ADDRESS>:1278"
2016/03/02 17:49:01 grpc: Conn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp <IP_ADDRESS>:1278: connect: cannot assign requested address"; Reconnecting to "<IP_ADDRESS>:1278"
2016/03/02 17:49:02 grpc: Conn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp <IP_ADDRESS>:1278: connect: cannot assign requested address"; Reconnecting to "<IP_ADDRESS>:1278"
2016/03/02 17:49:02 grpc: Conn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp <IP_ADDRESS>:1278: connect: cannot assign requested address"; Reconnecting to "<IP_ADDRESS>:1278"
2016/03/02 17:49:03 grpc: Conn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp <IP_ADDRESS>:1278: connect: cannot assign requested address"; Reconnecting to "<IP_ADDRESS>:1278"
2016/03/02 17:49:04 grpc: Conn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp <IP_ADDRESS>:1278: connect: cannot assign requested address"; Reconnecting to "<IP_ADDRESS>:1278"
2016/03/02 17:49:05 grpc: Conn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp <IP_ADDRESS>:1278: connect: cannot assign requested address"; Reconnecting to "<IP_ADDRESS>:1278"
2016/03/02 17:49:05 Failed to dial <IP_ADDRESS>:1278: grpc: timed out trying to connect; please retry.
2016/03/02 17:49:08 grpc: Conn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp <IP_ADDRESS>:1278: connect: cannot assign requested address"; Reconnecting to "<IP_ADDRESS>:1278"
2016/03/02 17:49:08 grpc: Conn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp <IP_ADDRESS>:1278: connect: cannot assign requested address"; Reconnecting to "<IP_ADDRESS>:1278"
2016/03/02 17:49:10 grpc: Conn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp <IP_ADDRESS>:1278: connect: cannot assign requested address"; Reconnecting to "<IP_ADDRESS>:1278"
2016/03/02 17:49:10 grpc: Conn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp <IP_ADDRESS>:1278: connect: cannot assign requested address"; Reconnecting to "<IP_ADDRESS>:1278"
2016/03/02 17:49:12 grpc: Conn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp <IP_ADDRESS>:1278: connect: cannot assign requested address"; Reconnecting to "<IP_ADDRESS>:1278"
2016/03/02 17:49:12 grpc: Conn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp <IP_ADDRESS>:1278: connect: cannot assign requested address"; Reconnecting to "<IP_ADDRESS>:1278"
2016/03/02 17:49:13 grpc: Conn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp <IP_ADDRESS>:1278: connect: cannot assign requested address"; Reconnecting to "<IP_ADDRESS>:1278"

The status function is hitting etcd too fast with 1 second timeout. Will improve cache and failover tonight.
Because of this, the public cluster thinks two of the nodes are down every other call.

Turns out grpc connections are leaking. Closing via https://github.com/coreos/etcd-play/pull/28.


Add TextMeshPro support

Hi, thanks for the contribution. However I think that these changes do not need to be included in the base library because:

TMP requires a separate package. If the user does not have this package, then the text will not work and the missing script error will be shown in the UniMob.TMPText prefab.
UniMobText and UniMobButton widgets are used only in examples to simplify the code or in fast prototypes (they are not extensible enough for real projects). In these cases it doesn't matter which text is used, Text or TextMeshPro.

If you really need integration with the text mesh pro, you can create a separate repository with text meth pro related code and link it to the main library with asmref.


feature/task_email_comment_author

Add comment author to task comment email #253

I updated the MailChimp templates to include this merge var. Pushing to STG to test out.


Fail to run vulkan tests on Android: Required Vulkan function vkEnumerateInstanceVersion not available

Followed instructions in https://google.github.io/iree/GetStarted/AndroidCMake
After working around the issue of vkCreateInstance, I hit another error:
...
I ../iree/tools/vm_util.cc:305] Creating driver and device for 'vulkan'...
E ../iree/base/api_util.h:29] UNAVAILABLE: Required Vulkan function vkEnumerateInstanceVersion not available

Instruction to repro
$ ctest -V -R iree/test/e2e/xla_ops:check_vulkan-spirv_vulkan_add.mlir_on_android_device

what version of vulkan do you have? vkEnumerateInstanceVersion is 1.1 (our min version)

Hanhan, is your test phone running Android 10? Vulkan 1.1 should be mandated by Android 10...

Also you can use https://play.google.com/store/apps/details?id=de.saschawillems.vulkancapsviewer to get detailed information regarding Vulkan implementation on your phone.

Ah, it's running Android 9, I haven't upgraded my Samsung S10. Let me upgrade it, and test again.

Yes, please update to whatever newest stable version you can. :)

Also you can use https://play.google.com/store/apps/details?id=de.saschawillems.vulkancapsviewer to get detailed information regarding Vulkan implementation on your phone.

Good to know this, it's useful!

Cool, it's working!
I think it would be good if we add this information to the doc or common issue, eg, we recommend users to upgrade Android to 10 or later version which usually support vulkan 1.1?

Great! I think there are a few test fails on Vulkan at the moment. I haven't looked into them closely. Could you create an issue to track them? After fixing them, we can then set up buildbots to guard against regressions.

I think it would be good if we add this information to the doc or common issue, eg, we recommend users to upgrade Android to 10 or later version which usually support vulkan 1.1?

Android 10 requirement is already mentioned in the doc (https://google.github.io/iree/GetStarted/AndroidCMake#vulkan-hal-backend). But please feel free to send a pull request to add a new common issue for this! :)

Oh, I missed it, it's good to keep it this way. :)
Sure, I'll run the tests on Android and create issues for failing tests.


Clarify why relocating bstats is not necessarry for bstats-sponge

Can you please clarify why I do not have to relocate the bstats package when using Sponge?
What happens if someone else shades a different bstats version to the same classpath?
org.bstats.sponge

To be honest, I don't know.
Most of the code for the Sponge Metrics class was rewritten my @mbax in https://github.com/Bastian/bStats-Metrics/pull/38.
My current guess would be, that Sponge has a different class loader per plugin and thus it doesn't matter.
Maybe @mbax can elaborate the reasoning behind it a little bit better.

Thank you for your reply!
Yes, this would be interesting.

While it's probably technically still not necessary, the new Sponge Metrics classes (2.x.x) now require relocation again.


Controller fails to reconcile the pull secret

Expected Behavior
Expected the pull secret to get updated
Current Behavior
controller log:
2023-07-12T07:03:42Z	ERROR	Reconciler error	{"controller": "clusterrelocation", "controllerGroup": "rhsyseng.github.io", "controllerKind": "ClusterRelocation", "ClusterRelocation": {"name":"cluster"}, "namespace": "", "name": "cluster", "reconcileID": "4939a489-c204-45e9-afe4-6f5444ffe9ae", "error": "Secret \"pull-secret\" is invalid: type: Invalid value: \"Opaque\": field is immutable"}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:329
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:274
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:235

Possible Solution
The issue happens because the type of secret I created was Opaque instead of  kubernetes.io/dockerconfigjson
The relocation operator should either validate it and report it in the status or handle it.
Steps to Reproduce (for bugs)

Here is the secret I used:

apiVersion: v1
data:
  .dockerconfigjson: {REDACTED}
kind: Secret
metadata:
  creationTimestamp: "2023-07-12T06:38:42Z"
  managedFields:
  - apiVersion: v1
    fieldsType: FieldsV1
    fieldsV1:
      f:data:
        .: {}
        f:.dockerconfigjson: {}
      f:type: {}
    manager: kubectl-create
    operation: Update
    time: "2023-07-12T06:38:42Z"
  - apiVersion: v1
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:ownerReferences:
          .: {}
          k:{"uid":"18feb399-8a8d-43a4-98aa-79ad14bdc7ce"}: {}
    manager: manager
    operation: Update
    time: "2023-07-12T06:58:14Z"
  name: new-pull-secret
  namespace: relocation
  ownerReferences:
  - apiVersion: rhsyseng.github.io/v1beta1
    kind: ClusterRelocation
    name: cluster
    uid: 18feb399-8a8d-43a4-98aa-79ad14bdc7ce
  resourceVersion: "428077"
  uid: c303a693-84b7-4186-b2cb-0840522a395d
type: Opaque

Apply a clusterrelocation CR that reference the above secret

Regression

Your Environment

Version used (cluster-relocation-operator): installed it from subscription
Environment name and version 4.13.0

Thanks, I've created a PR to address this: https://github.com/RHsyseng/cluster-relocation-operator/pull/79
I think it's best to validate that the secrets are the correct type, rather than try to mutate them, since ensuring the correct type enables further validation (the pull secret must be type kubernetes.io/dockerconfigjson, which ensures that the secret contains a .dockerconfigjson key).


Update scala-library, scala-reflect to 2.12.14

Updates

org.scala-lang:scala-library
org.scala-lang:scala-reflect

from 2.12.11 to 2.12.14.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang" } ]

labels: library-update, semver-patch

Superseded by #724.


max-width of sap.m.MenuButton

OpenUI5 version: All since MenuButton exists
Tested browsers (OK/FAIL) on Windows 10:
FAIL: FF, IE, Edge, Chrome, Opera
OK: -
URL (minimal example if possible): https://embed.plnkr.co/zXYqbL/
Steps to reproduce the problem:

Visit the provided example page

What is the expected result?
Width of the MenuButton is applied (or auto if no width is given):

What happens instead?
MenuButton has max-width: 12rem.

Any other information?
Not sure if it's a bug or just not documented.

Hi @boghyon,
Thank you for mentioning this issue.
This is the expected behavior of the sap.m.MenuButton, however, this indeed is not documented anywhere thus we have created internal incident:<PHONE_NUMBER>.
Best Regards,
Hristo

Hi @boghyon,
The documentation was updated and this will be available in the of the library.
Best Regards,
Hristo

Documentation fixed with https://github.com/SAP/openui5/commit/baabc9d1f061835bfd67199731a5cf9ff3756b63

... now reverted in this new change https://github.com/SAP/openui5/commit/88b563d35a84cf3cbd13b8114fabec7a53f7281f together with the removal of max-width: 12rem;. Now the sap.m.MenuButton can expand up to 100% width.


Added books+articles from Discord text discussion for 2023-07-24 recording

These are (nearly all) the links shared by folks in the Discord channel that didn't necessarily come up in the voice channel. I sorted them into sidebar-books and sidebar-links bits, which each should be in chronological order.
There are also a few images and such I didn't include. :)

Thanks for this! A huge help!


Node v4.1.2 Memory Leak

Since updating to Node v4.1.2 to address CVE-2015-7384 a memory leak has crept in:

Any more information?  What methods cause the leak?  Is it possible that node itself is causing the leak?

A fresh rebuild of dependencies (rm -r node_modules && npm install) seems to have stabilised it a bit, not getting much info from my debuggers yet.
Sockets, session, pubsub & frontend are all turned off, and Methods are all
Model.find({...}).exec(function(data) { res.send(data); });

so it's a bit harder to figure out when a big find() hangs around for a while.
Agreed that it's probably node / dependency causing it, but am struggling to find anyone else seeing this.

Tentatively closing as not a waterline issue - cannot yet replicate from a clean fresh install.
One hour of 20 concurrent connections, followed by 30mins of idle of calling this:
memoryCheck: function(req, res) {
    SomeTable.findOne({
        name: 'databaseCheck'
    }).exec(function(err, data) {
        if (err) {
            res.send('Server Error', 500);
            return;
        }

        // there should be an entry called 'databaseCheck'
        if (_.size(data)) {
            // all good
            res.send('Up!', 200);
        } else {
            res.send('ERROR!', 500);
        }
    });
}

looks pretty darn good. Gets pretty big before some of the larger GCs, but sails/waterline is not the cause of my leak! :)

Good news!  Thanks much for following up!

For future reference, there's more information and tips on diagnosing memory leaks in Node apps, and on reproducing+reporting suspected memory leaks in Sails here: https://github.com/balderdashy/sails/issues/3782#issuecomment-238679052

(@wulfsolter @devinivy I realize both you guys are aware of that stuff, I'm just going through and funneling all of these hanging issues to one place so it's easy for folks to find the step-by-step instructions from search engines)


Add CD

On tags, distributions should be built for Linux and Mac (and Windows if it's easy but I have less of an idea about that). Use this blog post as inspiration. It doesn't ship the binary, but I can look into GitHub artifacts for that.

There's a cd.yml script that runs on pushed tags, but it has a few things wrong:

[ ] in both macos and linux, it tries to create a release that might already exist (depending on which goes faster -- in practice the linux build is always faster)
[ ] the location of the build isn't captured correctly -- i think I'm trying to upload a symlink, which the release creater script doesn't really like


Loop Detection Question

I had a question on the feature characteristic: loop.
I have a function that does contain a loop but the characteristic appears to not be recognized.
In sample 1d8fd13c890060464019c0f07b928b1a (Located in the capa-testfiles repo) at offset: 0x401920.
The function graph contains the following blocks:

I wrote a dummy rule to see if I could trigger on the behaviour of a loop
rule:
  meta:
    name: loop
    namespace: loop
    scope: function
  features:
    - and:
      - characteristic: loop

The only result that I'm getting back is @ 0x402360 and not 0x401920
loop
namespace  loop
scope      function
function @ 0x402360
  and:
    characteristic: loop @ 0x402360

Any help or guidance would be appreciated.

If it helps another example of this is in the RC4 section 0x4015F0 of the malware mentioned above 1d8fd13c890060464019c0f07b928b1a
Removing the match: contain loop condition from the encrypt-data-using-rc4-prga.yml rule will cause the rule correctly ID the function.  (Shown below)
encrypt data using RC4 PRGA
namespace  data-manipulation/encryption/rc4
scope      function
matches    0x4015F0

A screenshot of the function, showing a loop:

Looks like this is a bug caused by some unexpected behavior in Vivisect.
Vivisect does not set any branch flags for the jmp instructions @ 0x401617 and 0x401699:
('0x401617', jmp 0x00401622)
('BR_COND', False)
('BR_FALL', False)
('BR_TABLE', False)
('BR_PROC', False)
('BR_ARCH', False)
('BR_DEREF', False)

('0x40161f', mov dword [ebp - 16],edx)
('BR_COND', False)
('BR_FALL', True)
('BR_TABLE', False)
('BR_PROC', False)
('BR_ARCH', False)
('BR_DEREF', False)

('0x401628', jnc 0x0040169e)
('BR_COND', True)
('BR_FALL', True)
('BR_TABLE', False)
('BR_PROC', False)
('BR_ARCH', False)
('BR_DEREF', False)

('0x401628', jnc 0x0040169e)
('BR_COND', True)
('BR_FALL', False)
('BR_TABLE', False)
('BR_PROC', False)
('BR_ARCH', False)
('BR_DEREF', False)

('0x401699', jmp 0x00401619)
('BR_COND', False)
('BR_FALL', False)
('BR_TABLE', False)
('BR_PROC', False)
('BR_ARCH', False)
('BR_DEREF', False)

This causes the following check to ignore the branches @ 0x401617 and 0x401699 causing the loop detection to fail:
https://github.com/fireeye/capa/blob/583f3f74ecfb6f3b430ba05408b5cb2f2a5c4b3b/capa/features/extractors/viv/function.py#L81
@mr-tz or @williballenthin you guys are more familiar with vivisect. Any thoughts on why Vivisect might not be setting the branch flags for these instructions?

here are the intended meanings of the branch flags:
# Branch flags (flags returned by the getBranches() method on an opcode)
BR_PROC  = 1<<0  # The branch target is a procedure (call <foo>)
BR_COND  = 1<<1  # The branch target is conditional (jz <foo>)
BR_DEREF = 1<<2  # the branch target is *dereferenced* into PC (call [0x41414141])
BR_TABLE = 1<<3  # The branch target is the base of a pointer array of jmp/call slots
BR_FALL  = 1<<4  # The branch is a "fall through" to the next instruction
BR_ARCH  = 1<<5  # The branch *switches opcode formats*. ( ARCH_FOO in high bits )

https://github.com/vivisect/vivisect/blob/402e944e0b1d7ff07ab702c8651a7c1723b24023/envi/__init__.py#L60-L66
given this, i think the behavior of not setting a branch flag is probably correct. i think capa needs to check for the mnemonic jmp in the extraction code?

@williballenthin I think you're correct. I updated my comment after taking another look. Can capa simply check for the branch flags it doesn't want to record specifically BR_PROC, BR_DEREF, and BR_ARCH?

fixed in #192.


Case-sensitive Package Names

NPM's rules for package.json includes not using capital letters.  A lot of MEAN setup (mean-cli, examples) uses camelCasing or something similar.  We need to investigate this further.
It does seem that the Package walk to find mean packages will break if the name in package.json is not the same (case-sensitive) as the module name new Module('myName')

https://docs.npmjs.com/files/package.json

Good catch


Visuallizer throws error in visible_actions branch

Running the visuallizer throws the error
  File "visuallizer_rllib.py", line 263, in <module>
    visualizer_rllib(args)
  File "visuallizer_rllib.py", line 170, in visualizer_rllib
    info={'all_agents_actions': last_actions})
  File "/home/gds38/multi8/lib/python3.6/site-packages/ray/rllib/agents/agent.py", line 410, in compute_action
    episode=episode)
  File "/home/gds38/multi8/lib/python3.6/site-packages/ray/rllib/evaluation/policy_graph.py", line 121, in compute_single_action
    episodes=episodes)
  File "/home/gds38/multi8/lib/python3.6/site-packages/ray/rllib/evaluation/tf_policy_graph.py", line 182, in compute_actions
    prev_reward_batch, episodes=episodes[0])
  File "/home/gds38/multi8/lib/python3.6/site-packages/ray/rllib/agents/a3c/a3c_policy_graph_causal.py", line 281, in _build_compute_actions
    [e.prev_action for e in episodes[self.agent_id]]))
KeyError: 'agent-0'

I have attached a sample log file to help with replication.
log_file.zip

Hi @gregSchwartz18, giving it a try now. I'll get back to you shortly.

Hi @gregSchwartz18, any chance you can submit a PR with your branch? That way I can resolve code incompatibilities faster.


Convert Routes to use Constants

Existing
private readonly Dictionary<string, string> _routes = new Dictionary<string, string>
{
    ["parameters"] = "/parameters",

}

Suggested
Add to Constants.cs or Add new File Routes.cs
    public static class Routes
    {
        public const string Parameters = "/parameters";
        public static class Auth
        {
            public const string Token = "/session/token";
            public const string RefreshToken = "/session/refresh_token";
        }

    }

When using we can use
Post(Routes.Auth.Token, reqParams)

Thanks for the suggestion. But this will be quite a significant change. Will consider this for the next major version. I will keep the issue open.

Thanks for the suggestion. But this will be quite a significant change. Will consider this for the next major version. I will keep the issue open.

Can I contribute to this or any suggestions via pull requests?

I actually have the patch ready. But just not merged yet. Since this is changing code related to all APIs, it will have to be tested as a whole and that is time consuming. That is why I'm delaying it till a major version or a refactor.

I am asking in general, can outsiders contribute to Zerodha repos?

Yeah sure. Just keep in mind, if it is a large patch then make sure to create an issue with your suggestion and seek maintainers opinion.


Add mkalioby as maintainer

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

noarch: python recipes are recommended to have a lower bound on the python version. This recommendation will become a requirement in the future.

@conda-forge-admin, please rerender

I agree to be a maintainer

Thank you @mkalioby. The conda-forge package uses the package from pip. Updating the conda-forge feedstock is as simple as incrementing the version and updating the SHA (which you can get from the PyPI page for the package) in the recipe.yml. This should be done through a pull request from a fork of this repo. See: https://conda-forge.org/docs/maintainer/updating_pkgs.html
Let me know if you need my assistance updating the conda package in the future.


Issues with initial calculations with top-* in Vue onMounted method

I have an issue with vue 3 and the top-start option
  const { x, y } = await computePosition(referenceElement, tooltipEl, {
        placement: "top-start",
        strategy: "fixed",
      });
      Object.assign(tooltipEl.style, {
        left: `${x + 20}px`,
        top: `${y - 1 * TOOLTIP_DISTANCE_PX}px`,
      });
      tooltipEl.classList.add("arrow_down");
      tooltipEl.classList.remove("arrow_left");

the issue is wrapped in a Vue3 onMounted(() => { and on the first render, the top-start (also just top) is way off, however on the next scroll or resize, the position is correct. However  placement: "right-end", works fine first time and continues to work.

Is the value of {referenceEl|tooltipEl}.getBoundingClientRect() correct before you call computePosition()? This type of thing is never an issue with the function but rather a timing problem where the reference/floating element is not on the DOM (to be measured) when you call it.

If I wait 100ms, the problems disappear but terrible for the user exp. In the onMounted and with a debugger in it, the Vue UI doesn't look complete at all, missing background and stuff, its just confusing cause the right-end works perfect even with the missing background stuff. Will get back to you soon.

Could you try to call it from a requestAnimationFrame maybe?

Closing as it's a timing problem with the framework rather than this lib, however, adding docs on this would be useful I think


cannot decode TOML integer into struct field bootstrap.BottlerocketKubernetes.ImageGCHighThresholdPercent of type *string

Description
Observed Behavior:
Karpenter doesn't respsect the fact that the following settings are supposed to be integers or strings:
    image-gc-high-threshold-percent = 75
    image-gc-low-threshold-percent = 45

Message: creating instance, getting launch template configs, getting launch templates, creating launch template, invalid UserData toml: cannot decode TOML integer into struct field bootstrap.BottlerocketKubernetes.ImageGCHighThresholdPercent of type *string

Expected Behavior:
Per the Bottlerocket docs, this can be a String or an Integer, so Karpenter should respect that.

Can you confirm if you are setting these values through the Karpenter EC2NodeClass kubeletConfig or through the TOML in the userData? My assumption is TOML in your userData, but confirming.

Via the user data..


Regarding the docs: should we add an explicit text banner to mention / clear up differences to the existing jwt-auth?

Now that https://laravel-jwt-auth.readthedocs.io/ is up, it might be confusing what this is related to https://jwt-auth.readthedocs.io/
Would it make sense to add an paragraph right on the first page to describe the difference? Maybe this would be a good place to also link to https://github.com/PHP-Open-Source-Saver/jwt-auth#migrating-from-tymondesignsjwt-auth (FWIW, I prefer having the migration part in the readme, because this makes it super quick available on github and also on the composer page)

Yeah, looks great! I think adding this information to the homepage of documentation is the way. Anyway, it looks very empty now 😄

Yes, we should keep this section in the documentation because most of the users (to not say 100% hahahahha) came from the old package, so let's keep it.

Shouldn't we move it to discussions?


[Bug] There is no option to select GPT-4 model.

When looking for the GPT-4 option in the model listing, there is no GPT-4 option, there are only GPT-3.5 options.
Even tried to add as custom model, app refuses to use GPT-4.

Deployment
https://app.nextchat.dev/ -v2.10.1
Mozilla Firefox.

@Yidadaa Sir, please can you help me with this issue?

Seems that they set DISABLE_GPT4? I'm not sure.
https://github.com/ChatGPTNextWeb/ChatGPT-Next-Web/blob/9eaf492d5b72d252c9dcaa55d5d99dab87bf19e0/README.md?plain=1#L209-L213

I have added the DISABLE_GPT4 environment variable, and GPT-4 has been disabled

I have added the DISABLE_GPT4 environment variable, and GPT-4 has been disabled

I understand, do you mean that from now on it will not be possible to use gpt-4 in the webpage app.nextchat.dev?

Any schedules when gpt4 can be reopened? I think this is a serious issue because most people are using gpt4 now.

Any schedules when gpt4 can be reopened? I think this is a serious issue because most people are using gpt4 now.gpt4何时可以重新开放？我认为这是一个严重的问题，因为现在大多数人都在使用gpt4。

go to here 👉 https://a.nextapi.fun/

Yeah, this really makes the app for many people unusable, including me :(

Any schedules when gpt4 can be reopened? I think this is a serious issue because most people are using gpt4 now.gpt4何时可以重新开放？我认为这是一个严重的问题，因为现在大多数人都在使用gpt4。

go to here 👉 https://a.nextapi.fun/

Hey thanks. Do you mind sharing from where is this link from and who hosts it?

Any schedules when gpt4 can be reopened? I think this is a serious issue because most people are using gpt4 now.gpt4何时可以重新开放？我认为这是一个严重的问题，因为现在大多数人都在使用gpt4。

go to here 👉 https://a.nextapi.fun/

Hey thanks. Do you mind sharing from where is this link from and who hosts it? (I wanna know if I can trust it)嘿，谢谢。你介意分享一下这个链接是从哪里来的，由谁托管的吗？（我想知道我是否可以信任它）

@Yidadaa


[FLINK-22815][checkpointing][bp-1.12] Disable unaligned checkpoints for broadcast partitioning

This is a backport of parts of #16019 and #15294
Broadcast partitioning can not work with unaligned checkpointing. There are no guarantees that records are consumed at the same rate in all channels. This can result in some tasks applying state changes corresponding to a certain broadcasted event while others don't.
In turn upon restore, it may lead to an inconsistent state. This is especially harmful to the most common pattern for using a broadcast pattern where only a single operator checkpoints its state and that state is copied over to all other operators on restore.

This is a similar work to #16066


fix poorly formatted README.md section

Description of changes:
The original content appears to be based on https://aws.amazon.com/blogs/aws/new-for-aws-lambda-container-image-support/
Unfortunately when it was copied, the entrypoint script was collapsed down to a single line and part of it was lost. A handful of other improvements are also included.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@mgrandis Thanks for the review. I've updated the PR.


Extending Sprokets

I would like to hook into sprokets building process to run a script after sprokets has been called to run but before sprokets runs. Is there a way to do this?
If there is a blatantly obvious way to do this I apologize, I fully admit I could have dug deeper than just reading the project home page before asking.
Sincerely,
jBeasley

It seems I can hook in through here: bundle exec rake assets:precompile
Please comment if there are other options.


Custom Telegram API Endpoint

Describe the feature request
Allow telegram.endpoint setting.
Why do you personally want this feature to be implemented?
In some countries, api.telegram.org is blocked, we have to use a custom endpoint (with proxy configured, or self-deployed telegram-bot-api server).
How long have you been using this project?
~1year
Additional information
No response

Fair enough! I would however prefer to have it be alerting.telegram.api-url instead of alerting.telegram.endpoint to avoid confusion. The default value would be https://api.telegram.org/.
Relevant code:
https://github.com/TwiN/gatus/blob/3f961a740874849b06adf5a778521b70dcaeb6c9/alerting/provider/telegram/telegram.go#L31


bundling failed: Error: Unable to resolve module ../Components/AccessibilityInfo/AccessibilityInfo from node_modules/react-native/Libraries/react-native/react-native-implementation.js:

While running the app in bundler it fails with the following message in the terminal
warning: the transform cache was reset.
Loading dependency graph, done.
To reload the app press "r"
To open developer menu press "d"
error: bundling failed: Error: Unable to resolve module ../Components/AccessibilityInfo/AccessibilityInfo from node_modules/react-native/Libraries/react-native/react-native-implementation.js:
None of these files exist:

node_modules/react-native/Libraries/Components/AccessibilityInfo/AccessibilityInfo(.native|.macos.js|.native.js|.js|.macos.json|.native.json|.json|.macos.ts|.native.ts|.ts|.macos.tsx|.native.tsx|.tsx)
node_modules/react-native/Libraries/Components/AccessibilityInfo/AccessibilityInfo/index(.native|.macos.js|.native.js|.js|.macos.json|.native.json|.json|.macos.ts|.native.ts|.ts|.macos.tsx|.native.tsx|.tsx)
at ModuleResolver.resolveDependency (/Users/dev/Desktop/Sangeeth/mytakeaway2.0/Myt-Mac/MYT_MacOS/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:163:15)
at ResolutionRequest.resolveDependency (/Users/dev/Desktop/Sangeeth/mytakeaway2.0/Myt-Mac/MYT_MacOS/node_modules/metro/src/node-haste/DependencyGraph/ResolutionRequest.js:52:18)
at DependencyGraph.resolveDependency (/Users/dev/Desktop/Sangeeth/mytakeaway2.0/Myt-Mac/MYT_MacOS/node_modules/metro/src/node-haste/DependencyGraph.js:282:16)
at Object.resolve (/Users/dev/Desktop/Sangeeth/mytakeaway2.0/Myt-Mac/MYT_MacOS/node_modules/metro/src/lib/transformHelpers.js:267:42)
at dependencies.map.result (/Users/dev/Desktop/Sangeeth/mytakeaway2.0/Myt-Mac/MYT_MacOS/node_modules/metro/src/DeltaBundler/traverseDependencies.js:426:31)
at Array.map ()
at resolveDependencies (/Users/dev/Desktop/Sangeeth/mytakeaway2.0/Myt-Mac/MYT_MacOS/node_modules/metro/src/DeltaBundler/traverseDependencies.js:423:18)
at /Users/dev/Desktop/Sangeeth/mytakeaway2.0/Myt-Mac/MYT_MacOS/node_modules/metro/src/DeltaBundler/traverseDependencies.js:275:33
at Generator.next ()
at asyncGeneratorStep (/Users/dev/Desktop/Sangeeth/mytakeaway2.0/Myt-Mac/MYT_MacOS/node_modules/metro/src/DeltaBundler/traverseDependencies.js:87:24)
BUNDLE  [macos, dev] ./index.js ░░░░░░░░░░░░░░░░ 3.1% (9/77), failed.

I fixed this by removing .ios.js extension with .js in files inside react-native/libraries/components
For example, I changed AccessibilityInfo.ios.js --> AccessibilityInfo.js
Likewise, there are so many files which need these changes like Checkbox, DatePicker, Alert, Settings, etc

The above error indicates that your metro config is not correct.  It should never be loaded files from react-native when bundling for macos -- it should get all the files from react-native-macos.
Are you on 0.62? And using at least version 4.9 of @react-native-community/cli?

For 0.61 you'd need a seperate metro config for macos, like react-native-netinfo does:
https://github.com/react-native-community/react-native-netinfo/blob/master/metro.config.macos.js

what is causing this issue and how do i fix this ?

Close running Metro and run react-native run-macos again. It'll solve the problem. No need to change or rename any file

When bundling for macos, metro should be told to redirect any react-native import to react-native-macos.
In 0.61 you have to do this manually by changing your config when bundling for macos.  (The config wont work for other platforms)
  resolver: {
    extraNodeModules: {
      'react-native': path.resolve(__dirname, 'node_modules/react-native-macos')
    },
  },
  serializer: {
    getModulesRunBeforeMainModule: () => [
      require.resolve(
        path.resolve(__dirname, 'node_modules/react-native-macos/Libraries/Core/InitializeCore')),
      ]
  },
  transformer: {
    assetRegistryPath: path.resolve(__dirname, 'node_modules/react-native-macos/Libraries/Image/AssetRegistry'),
  },

For 0.62, so long as you are using<EMAIL_ADDRESS>or greater, then the cli should automatically set this up for you.
See https://github.com/react-native-community/cli/pull/1115 for details of the metro change that allowed this config to happen automatically.

@acoates-ms I just started a brand new project and this issue happens to me. I was using 0.63 first, but now I changed to 0.62.

I was mistaken in my above comment about this happening automatically currently.  There was a change that I thought we'd made in react-native-macos that never happened.  If I work out what #587 needs, then it would work without a custom metro config.  Otherwise, you can run the snipped in my comment above to configure metro correctly for macos.

@acoates-ms Also, it seems that if you run yarn ios first and then yarn macos (or npx), it will fail cause react-native start from iOS won't include MacOS stuff. Now, if you run macos first, it will launch the modified Metro and work properly, including the ios build.

Can you try this again with react-native-macos 0.62.11.

It works but not with the command from the react-native-docs (npx react-native run-macos)
Instead it works when we start the metro server and app separately as -

yarn start:macos
npx react-native run-macos

@acoates-ms @HeyImChris FYI I ran into this again today, where I had run "yarn ios" from fluent-ui-react-native tester app, and then was trying to run "yarn macos" to have both testers up, but ran into this error. I don't know where documentation for react-native-macos is going, but if this issue can't be fixed, then we should mention it as a known issue in documentation (i.e. if you're running both ios and mac, make sure to run macos first). Let me know if you have any questions.

I ran into this again today, was able to get past the error with the code above,  but am now getting a "No bundle URL present" error. Any ideas?

I'm getting the same error from a clean install of everything:
error: Error: Unable to resolve module ./Libraries/Components/AccessibilityInfo/AccessibilityInfo from /Users/thertzelle/Local_Development/JQuakeMobile/node_modules/react-native/index.js:

None of these files exist:
  * node_modules/react-native/Libraries/Components/AccessibilityInfo/AccessibilityInfo(.native|.macos.js|.native.js|.js|.macos.json|.native.json|.json|.macos.ts|.native.ts|.ts|.macos.tsx|.native.tsx|.tsx)
  * node_modules/react-native/Libraries/Components/AccessibilityInfo/AccessibilityInfo/index(.native|.macos.js|.native.js|.js|.macos.json|.native.json|.json|.macos.ts|.native.ts|.ts|.macos.tsx|.native.tsx|.tsx)

I re-installed my entire environment again, and followed setting up react native and then setting up react native macos, and this is the error I get.

Same here. I'm using an M1 MacBook air and same issue. I tried everything mentioned above.

Any update?


Use dict overrides

Proposed changes
Use the new feature introduced in https://github.com/valory-xyz/open-aea/pull/284 for dict overrides.
This basically reverts some commits which had introduced a hacky workaround in #1189 to overcome the missing feature.
Fixes
n/a
Types of changes
What types of changes does your code introduce? (A breaking change is a fix or feature that would cause existing functionality and APIs to not work as expected.)
Put an x in the box that applies

[ ] Non-breaking fix (non-breaking change which fixes an issue)
[ ] Breaking fix (breaking change which fixes an issue)
[ ] Non-breaking feature (non-breaking change which adds functionality)
[ ] Breaking feature (breaking change which adds functionality)
[x] Refactor (non-breaking change which changes implementation)
[ ] Messy (mixture of the above - requires explanation!)

Checklist
Put an x in the boxes that apply.

[x] I have read the CONTRIBUTING doc
[x] I am making a pull request against the main branch (left side). Also you should start your branch off our main.
[x] Lint and unit tests pass locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have locally run services that could be impacted and they do not present failures derived from my changes

Further comments
n/a

Still getting:
Error: Attribute `models.params.args.pair_ids` is not allowed to be updated!


config.hooks only accepts module name/path?

https://github.com/metaskills/mocha-phantomjs/blob/master/lib/mocha-phantomjs.coffee#L185
It seems awfully restrictive that config.hooks only supports a module name or path. I'd like to request this be updated to check the type of the value passed. If it's an object it should pass that along, rather than try to require on an object.

That's the only way it can work. the hooks object needs to have functions hanging off of it, and the config is the JSON serialized object from the command line - JSON doesn't support functions.

@nathanboktae why so close-happy on tickets? You didn't give any time for discussion at all. Come on now.
Considering:
      .pipe(mocha({
        phantomjs: {
          webSecurityEnabled: false,
          localToRemoteUrlAccessEnabled: true,
          ignoreSslErrors: true,
          hooks: 'mocha-phantomjs-istanbul'
        }
      }))

There's no fundamental difference between:
config.hooks = require(module)

which exports an object with the afterEnd method, and
config.hooks = { afterEnd: function(runner) { } }

mocha-phantomjs runs in phantomjs, not node. Also you're giving example code from something not mocha-phantomjs but I'm guessing some wrapper around it for a node.js build system like grunt or gulp. config is hydrated by code running in phantomjs from JSON passed in the command line.


Add a watch feature

In this feature, the cli would continuously poll the api in certain customizable intervals to fetch new posts and append them to the feed.

I don't quite understand what you mean by this ! As every event is already fetched directly from the api.


[FLINK-26613][streaming] Allow setting operator uid hashes for predefined sink operators

What is the purpose of the change
Since the topology has changes between Flink 1.14 and 1.15 it might
happen that stateful upgrades are not possible if no pior operator uids
were set. With this commit, users can set operator uid hashes for the
respective operators.
Brief change log

Add a parameter to DataStream#sinkTo to pass operator uid hashes`
Set the operator uid hashes for Writer, Committer, GlobalCommitter during SinkTransformation translation

Verifying this change
Added a test to verify the respective sink operators have the uid hash set.
Does this pull request potentially affect one of the following parts:

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

Documentation

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

Thanks @fapaul for the fix! I'll have a look~

Very thanks @fapaul for the fix! LGTM.
For another point, should we also unify the uid format compared to the 1.13? In all the versions, the writer always have the same uid with the sink transformation, thus there should be no problem. But for the other two operators:

For the committer operator, <= 1.13 it is set to Sink Committer: <sink uid> (https://github.com/apache/flink/blob/98c20ced2d5e514a967feedbc51c1570c22c91be/flink-streaming-java/src/main/java/org/apache/flink/streaming/runtime/translators/SinkTransformationTranslator.java#L247) and on 1.15 it is set to Sink <sink uid> Committer (https://github.com/apache/flink/blob/a0d31c5e0914d8e759917a72ca7b667d3db2f1d2/flink-streaming-java/src/main/java/org/apache/flink/streaming/runtime/translators/SinkTransformationTranslator.java#L334)
For the global committer, it seems the 1.13 and 1.14 already have different format. But currently the usage of global committer is rare, thus I think we may keep it the same with 1.14 and then we do not to do any change.

Thus as a whole, perhaps we change the uid format of committer back to Sink Committer: <sink uid>?

For another point, should we also unify the uid format compared to the 1.13? In all the versions, the writer always have the same uid with the sink transformation, thus there should be no problem. But for the other two operators:

For the committer operator, <= 1.13 it is set to Sink Committer: <sink uid> (https://github.com/apache/flink/blob/98c20ced2d5e514a967feedbc51c1570c22c91be/flink-streaming-java/src/main/java/org/apache/flink/streaming/runtime/translators/SinkTransformationTranslator.java#L247
) and on 1.15 it is set to Sink <sink uid> Committer (https://github.com/apache/flink/blob/a0d31c5e0914d8e759917a72ca7b667d3db2f1d2/flink-streaming-java/src/main/java/org/apache/flink/streaming/runtime/translators/SinkTransformationTranslator.java#L334
)
For the global committer, it seems the 1.13 and 1.14 already have different format. But currently the usage of global committer is rare, thus I think we may keep it the same with 1.14 and then we do not to do any change.

Thus as a whole, perhaps we change the uid format of committer back to Sink Committer: <sink uid>?

Good catch, I think you are right we can make the life of our users a bit easier since there is not committer with 1.14, we can switch to using the uid pattern from 1.13 for the committer.

@gaoyunhaii I added a separate commit 739af0 to address the committer operator uid problem for upgrades from 1.13 to 1.14.


Refactor of location layers to support tracking and navigation

I started with a refactoring of the location layer. I want to support users to:

track his location (and later store/share that track)
be navigated to a specific location
location updates should be active all the time

But I'm having issues with the last one: when the user starts using this app, the location should be turned on and show a location marker on the map. This location doesn't have to run in [back/fore]ground (no notification needed). Also if the application is closed, the location should be turned off. But when the user starts navigation/tracking it should use foreground location. Similar to how (for example) Locus maps work. In the future, I would also enable users to turn this off completely.
For this I tried using navigator.geolocation.watchPosition but for some reason, it's not working as it should. I think it's using a location provider from WIFI or LTE (I'm not sure) but not GPS (there is no android icon shown). I'm not sure if this is again a problem with my phone or if there is another way to achieve this. Did you ever experience anything similar? Do you have any idea how to solve this?

There's no way to force GPS location with navigator.geolocation, however, you can specify options with Geolocation.watchPosition() or Geolocation.getCurrentPosition(), specifically you're interested in using the enableHighAccuracy: true option.
https://developer.mozilla.org/en-US/docs/Web/API/Geolocation/getCurrentPosition
https://developer.mozilla.org/en-US/docs/Web/API/Geolocation/watchPosition
In a cordova environment using a plugin, you can specify the GPS_PROVIDER option for LocationManager.

🤦 I was using it (enableHighAccuracy: true) here, but forgot to add it in location-store
I think that's it ...

@jeancaffou this is getting big, so I will stop now :) comments much appreciated.

Just checked, since this was pretty straightforward in Vue2/Vuex, but with Pinia and Vue3, you can set up reactive store properties with storeToRefs(). Here is an example: https://stackoverflow.com/a/72530962

The reason for those was to have component specific logic there. But probably I didn't think it through enough. It looks like I could move this into watcher, didn't think about it before. Will look into this.

@jeancaffou moved a few things around. I think the components are now much cleaner. Didn't even need to use storeToRef in most places.

Looks good 👍


Cache the weather update date

We want to cache the date along with the weather update
since this is used to display "Last updated at".
Without this it will always say it was last updated at the current time
and when the real update comes in it won't change
but the new weather will.

This looks good to merge.


Archive project and update update readme to reflect project merge

To prevent confusion for people with old forks of this project, it should have the README updated indicating the merge with the main project and should then be ARCHIVED.

Completed. Will leave the project in place for a bit in case of unforeseen problems.


Fault Handling OS Coredump Callback Feature

This provides mynewt-core users the ability to set up their own coredump callbacks by toggling a syscfg and using the provided interface void os_coredump_cb(void *tf);

Follow on from https://github.com/apache/mynewt-core/pull/2686

@andrzej-kaczmarek are you cool with the changes?


No upcoming arrivals for all requests

Hi,
great widget and simple idea that can work for almost all cases.
I'm trying to get it to work - having two urls at the same server and trying to find departures, but no matter which route+direction+stop I choose, i get: No upcoming arrivals
How to debug it? Console says 200 OK for all answers, and provides a response with a long alphanumeric value.
All requests seem to go to tripupdates url with suffix ?cacheBust=1629829331976 etc.
Please advise how to proceed.

Can you share with me your config.json file so I can see the data sources you are using?

@brendannee hi, thanks for responding. shared the config over through slack as the url's used are beta


Private preview API accidentally published as GE sample query

Describe the bug
GE has accidentally published the Search grounding API, even though the API isn't available beyond private preview (see screenshot below).
To Reproduce
Steps to reproduce the behavior:

Go to https://developer.microsoft.com/en-us/graph/graph-explorer
Search "grounding"
Click on POST (beta) search grounding
See error

Expected behavior
A private preview API should not have a GE sample query published publicly.
Screenshots

Desktop (please complete the following information):

OS: Windows
Browser: Microsoft Edge

Need to do:

Have this private preview sample query removed from GE.
Can you tell me more about the process of how a sample query is added onto GE? Please describe this process in detail, as I'd like to understand what the gap was that allowed this to happen.

This has been fixed at source here: https://github.com/microsoftgraph/microsoft-graph-devx-content/pull/534


Remove duplicated attributes for Xenium and CosMX

Closes #403

Integrity checks now pass. OK to merge once JSON-LD generation has completed

Ah... of course the duplicates in the CSV would have been eliminated by Schematic so no JSON-LD changes to commit


More robust timing tests

The primary objective of this PR is to fix the issue we have with test_suite_timing and the TIMING selftest on the CI, which sometimes fail due to heavy load. I also fixed some minor bugs in the timing module.
This PR introduces new timing tests that test the functions in the timing module mostly independently. The old self-test is still present in the code but will not be executed by the test suite, like other self-tests that we judge to be too time-consuming. CI still runs it once through programs/test/selftest.
Compared with the self-tests:

The new tests are more modular and print some detailed information when they fail.
I don't test mbedtls_set_alarm with delays of more than 1 second, which makes the test run for about 2s instead of 8s.
The timing self-test is more tolerant and shorter.

There are some test ideas I discarded in https://github.com/gilles-peskine-arm/mbedtls/tree/IOTSSL-1798-development-1 . The present PR is https://github.com/gilles-peskine-arm/mbedtls/tree/IOTSSL-1798-development-2 with a few minor fixes and a cleaned up history.
Incidental changes in this PR:

Fix read from an uninitialized integer object in mbedtls_timing_get_timer on Windows (internal ref: IOTSSL-1822)
Improved documentation of the timing API.
Fix mbedtls_set_alarm(0) on Unix/POSIX.
In the selftest program, support running a subset of the tests with command line arguments.

I've tested several iterations of this PR on my machine and on CI. The CI failures haven't completely gone so far, but they're markedly less frequent.
Partial backport for 2.1: #1223 (bug fixes, self test robustness, selftest command line parsing)
Partial backport for 1.3: #1224 (bug fixes, self test robustness)
Internal ref: IOTSSL-1798

CI has now passed twice (I rebased a couple of times).

This PR is critical as CI often fails in timing tests.

Running it in Oulu CI as that is most time skewed.

Timing test fails on Oulu CI https://jenkins-internal.mbed.com/job/mbedtls-pr/314/execution/node/206/log/

The CI has run several times, but due to a Jenkins issue it picked old revisions of this PR. Manual run on the latest version (https://github.com/ARMmbed/mbedtls/pull/1136/commits/ca5f6e2290735f63804ff58c4f01070c502db148): https://jenkins-internal.mbed.com/job/mbedtls-commit-tests/47/

I uploaded a fix for a mistake that Clang pointed out.

New bug fix: the code of mbedtls_timing_get_timer was originally using an uninitialized integer variable on Windows when calling it to initialize a timer, and I introduced a similar bug on Unix. I've now changed it to not read any part of the timer object when resetting.
This bug is harmless on basically all real-world environments since the worst it could do was to cause an integer overflow in an expression whose value was not specified. Nonetheless, it could cause a crash if someone compiled a Windows or Unix application with signed integer overflow checks enabled.

CI release job: https://jenkins-internal.mbed.com/job/mbedtls-release/51/
CI commit job: https://jenkins-internal.mbed.com/job/mbedtls-commit-tests/49/

CI commit job: https://jenkins-internal.mbed.com/job/mbedtls-commit-tests/52/
CI release job: https://jenkins-internal.mbed.com/job/mbedtls-release/60/

I've further relaxed the self-test. CI commit job: https://jenkins-internal.mbed.com/job/mbedtls-commit-tests/55/

PR job https://jenkins-internal.mbed.com/job/mbedtls-pr/525/ failed only the self-test on FreeBSD (1 out of 2). Commit job https://jenkins-internal.mbed.com/job/mbedtls-commit-tests/55/ passed the self-test on FreeBSD both times (and failed in the other timing issue, in compat.sh, but that's unrelated with this PR).

I'd like to advocate two things: (1) that we merge this now rather than later. Even if it's not perfect, it's an improvement over the current state of things, so I'd rather have an improvement now, and a further improvement later, that maybe something perfect some distant time in the future. (2) I think we should skip the timing selftest function in the CI until further notice (eg until the CI machines get less loaded): as discussed, the timing functions are loosely coupled with the rest of the library and the implementations we provide are likely to be replaced with other (user-provided) implementations in production code, so the looser tests introduced by this PR should be enough.

@mpg Agreed about merging ASAP. I've been fixing some build failures under various compiler warning settings, but according to CI this has converged. Even if it isn't perfect, it's already a major improvement.
For dropping the timing self-test, what's your proposed approach? New option to selftest?

For dropping the timing selftest, I was thinking we could just stop running programs/tests/selftest as all the other selftests are already included in their corresponding test suite.

Also, regarding backports, I'd like to suggest skipping the backport to 1.3 as it's only going to see one more release before being end-of-lifed, so I don't see the point in backporting improvements to tests to that branch.

Following our discussion, I'm going to rebase this PR to clean up the history (no reversal in the changes to mbedtls_timing_get_timer, less waffling in the evolution of the tests).

Rebased with a cleaner history. The old history is at https://github.com/gilles-peskine-arm/mbedtls/tree/IOTSSL-1798-development-2

I've reviewed the diff between the previous version of this branch (in my local copy) and the rebased version, and I'm satisfied nothing nasty happened during the rebase.

I triggered a daytime run of the CI job that tends to fail: https://jenkins-internal.mbed.com/job/mbedtls-commit-tests/56/ . All the timing tests passed, there were failures only in compat.sh which is a known issue (also due to CI slowness) that wasn't fixed when this PR was forked.

retest

retest


Shouldn't taskIcon.png be icon.png?

My custom icon didn't show up in the build task until I renamed it to icon.png in the task's folder, and made it 32x32 pixels.

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

ID: 83f7acc5-1222-7216-571b-913fa63298e4
Version Independent ID: 15b2e074-4a8d-9ac8-8aa8-56a0c11be534
Content: Custom build/release task reference
Content Source: docs/extend/develop/build-task-schema.md
Service: unspecified
GitHub Login: @erickson-doug
Microsoft Alias: elbatk

Confused me as well, works when renaming the taskIcon.png to icon.png :)

Finally getting around to fixing this, thanks for the heads up @nadcraker and @niofire !


Code-viewer and annotation bugfixes

Bugs:

caching the submission file id in localStorage meant that a pdf or image file from a previous student was being displayed when changing between student submissions in the results page.
the annotationPanel component stores the current overall comment as both a prop and in the component state. This state was not being updated after the initial render which meant that a previously saved overall comment was never visible.

Fixes:

only cache the file name in localStorage and update the getFirstFile function to find either the first visible file or the first file with the cached filename.
add a componentDidUpdate method to the annotationPanel that makes sure the state updates to reflect the props when the props change (ie. when new data is sent from the server).

@mishaschwartz looks good to me, please feel free to merge & send patch.