Quarkus 3: Update openapi version

Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[ ] You have read the contributors guide
[ ] Your code is properly formatted according to this configuration
[ ] Pull Request title is properly formatted: KOGITO-XYZ Subject
[ ] Pull Request title contains the target branch if not targeting main: [0.9.x] KOGITO-XYZ Subject
[ ] Pull Request contains link to the JIRA issue
[ ] Pull Request contains link to any dependent or related Pull Request
[ ] Pull Request contains description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket

How to replicate CI configuration locally?

Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.
build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.

How to retest this PR or trigger a specific build:

for pull request checks
Please add comment: Jenkins retest this

for a specific pull request check
Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] tests

for quarkus branch checks
Run checks against Quarkus current used branch
Please add comment: Jenkins run quarkus-branch

for a quarkus branch specific check
Run checks against Quarkus current used branch
Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] quarkus-branch

for quarkus main checks
Run checks against Quarkus main branch
Please add comment: Jenkins run quarkus-main

for a specific quarkus main check
Run checks against Quarkus main branch
Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] quarkus-main

for quarkus lts checks
Run checks against Quarkus lts branch
Please add comment: Jenkins run quarkus-lts

for a specific quarkus lts check
Run checks against Quarkus lts branch
Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] quarkus-lts

for native checks
Run native checks
Please add comment: Jenkins run native

for a specific native check
Run native checks
Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] native

for native lts checks
Run native checks against quarkus lts branch
Please add comment: Jenkins run native-lts

for a specific native lts check
Run native checks against quarkus lts branch
Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] native-lts

How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-7.67.x to backport the original PR to the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

Quarkus-3 PR check is failing ... what to do ?

The Quarkus 3 check is applying patches from the `.ci/environments/quarkus-3/patches`.
The first patch, called 0001_before_sh.patch, is generated from Openrewrite .ci/environments/quarkus-3/quarkus3.yml recipe. The patch is created to speed up the check. But it may be that some changes in the PR broke this patch.
No panic, there is an easy way to regenerate it. You just need to comment on the PR:
jenkins rewrite quarkus-3

and it should, after some minutes (~20/30min) apply a commit on the PR with the patch regenerated.
Other patches were generated manually. If any of it fails, you will need to manually update it... and push your changes.

jenkins rewrite quarkus-3

(quarkus-3) - kogito-runtimes job #54 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer
export BUILD_MVN_OPTS_CURRENT=-T 1C
build-chain build cross_pr -f 'https://raw.githubusercontent.com/kiegroup/kogito-pipelines/main/.ci/pull-request-config.yaml' -o 'bc' -p kiegroup/kogito-runtimes -u https://github.com/kiegroup/kogito-runtimes/pull/3193 --skipParallelCheckout
NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution

Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest.quarkus-3/job/kogito-runtimes.quarkus-3.kogito-runtimes/54/display/redirect
Test results:

PASSED: 3361
FAILED: 7

Those are the test failures:

org.kie.kogito.integrationtests.springboot.OASTest.testOASisValid
Expecting empty but was: ["Unable to read location `http://localhost:44239/v3/api-docs`"]

org.kie.kogito.integrationtests.springboot.OASTest.testOASisSwaggerUICompatible
Expecting empty but was: ["Unable to read location `http://localhost:44239/v3/api-docs`"]

org.kie.kogito.integrationtests.springboot.PMMLRegressionTest.testEvaluateLinRegResult
1 expectation failed.Expected status code <200> but was <404>.

org.kie.kogito.integrationtests.springboot.PMMLTreeTest.testEvaluateSampleMineResult
1 expectation failed.Expected status code <200> but was <404>.

org.kie.kogito.integrationtests.springboot.PingPongMessageTest.testPingPongBetweenProcessInstances
Assertion condition defined as a org.kie.kogito.integrationtests.springboot.PingPongMessageTest 1 expectation failed.Expected status code <200> but was <404>. within 10 seconds.

org.kie.kogito.integrationtests.springboot.ProcessSvgAddonTest.testGetSvgProcessInstances
javax/servlet/DispatcherType

org.kie.kogito.integrationtests.springboot.ProcessSvgAddonTest.testInvalidSvgProcessInstances
Could not initialize class com.github.tomakehurst.wiremock.jetty9.JettyHttpServerFactory

(tests) - kogito-apps job #3058 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer
export BUILD_MVN_OPTS_CURRENT=
build-chain build cross_pr -f 'https://raw.githubusercontent.com/kiegroup/kogito-pipelines/main/.ci/pull-request-config.yaml' -o 'bc' -p kiegroup/kogito-apps -u https://github.com/kiegroup/kogito-runtimes/pull/3193 --skipParallelCheckout
NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution

Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-runtimes.tests.downstream.kogito-apps/3058/display/redirect
Test results:

PASSED: 2764
FAILED: 1

Those are the test failures:

org.kie.kogito.index.oracle.ProcessDataIndexOracleKafkaIT.testProcessInstanceEvents
java.lang.IllegalStateException: Unable to determine the status of the running process. See the above logs for details


SPOI-5837: Malhar: Set filterStream variable to transient

@PramodSSImmaneni  please review and pull this change.

Pull request and commit messages to reference Malhar JIRA.

@tushargosavi can you please review and pull the changes.


Q? CSP transform without cov

I'm trying to do a dimensionality reduction with CSP, but want to keep the time sample to then perform a search light eg.
make_pipeline(
    CSP(2),  # find spatial filters where covariance is most predictive
    Windower(size=50, step=50),  # chunk into time slices
    SearchLight(make_pipeline(Covariances(), TangentSpace(), Logistic()))  # for each slice decode from cov

Would it make sense? If so, is it possible to implement it with pyRiemann?
Thanks!

Hum, i would suggest to use the MNE CSP (but i'm not sure it can return raw spatially filtered signal).
otherwise, would suggest to put the CSP just after the Covariance, and flip the switch log=False so it can return spatially filtered covariance instead of just the log-variance.
i would like to avoid modifying the CSP api

Ok, thanks


gh-1364 - added default score resolver

This will allow other score resolver implementations to access the default values for nested operations

Codecov Report

Merging #1478 into develop will decrease coverage by 0.65%.
The diff coverage is 83.33%.

@@              Coverage Diff              @@
##             develop    #1478      +/-   ##
=============================================
- Coverage      66.58%   65.93%   -0.66%
  Complexity      1744     1744
=============================================
  Files            721      655      -66
  Lines          23627    20752    -2875
  Branches        2984     2464     -520
=============================================
- Hits           15733    13682    -2051
+ Misses          6686     6054     -632
+ Partials        1208     1016     -192

Impacted Files
Coverage Δ
Complexity Δ

...gaffer/store/operation/resolver/ScoreResolver.java
100% <100%> (ø)
0 <0> (?)

.../operation/handler/ScoreOperationChainHandler.java
80.59% <100%> (+0.07%)
0 <0> (ø)
:arrow_down:

...store/operation/resolver/DefaultScoreResolver.java
76.47% <76.47%> (ø)
0 <0> (?)

.../src/main/java/uk/gov/gchq/gaffer/graph/Graph.java
57.38% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...ion/addelements/impl/AggregateAndSortTempData.java

...e/serialisation/impl/IntegerParquetSerialiser.java

...tore/serialisation/impl/LongParquetSerialiser.java

...sation/impl/TypeSubTypeValueParquetSerialiser.java

.../addelements/impl/rdd/AggregateGafferElements.java

.../addelements/impl/GenerateIndexForColumnGroup.java

... and 67 more

Continue to review full report at Codecov.

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


[BUG][CAPR] rancher-provisioning-capi-patch-sa job failing due to lack of exclusion from PSA enforcement

Rancher Server Setup

Rancher version: v2.7-head 787c056
Installation option (Docker install/Helm Chart): Helm

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc):

Information about the Cluster

Kubernetes version: v1.26.7+rke2r1
Cluster Type (Local/Downstream):

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider):
AWS node driver

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)

If custom, define the set of permissions: Admin

Describe the bug

Downstream cluster is unable to provision and cluster is stuck at waiting for viable init node. I don't see the machines getting created on the AWS portal and the latest log message is Creating server [fleet-default/auto-aws-kkswl-pool0-01d54a4c-4kr6x] of kind (Amazonec2Machine) for machine auto-aws-kkswl-pool0-74f9b78f74xcl6q9-fjnch in infrastructure provider
To Reproduce

Provision RKE2 AWS node driver cluster

Result
Cluster gets stuck while provisioning with the status waiting for viable init node
Expected Result

Cluster is able to provision successfully
Screenshots

This is not resolved for us.
We looked into our automation and nothing looks out of the ordinary.  Here's what we know:

this only fails for rke1 local clusters (rke2 on the same 1.26.7 k8s version deploys just fine)
if you manually set the rancher-provisioning-capi-patch-sa 's namespace to enforce:psa:privileged and the cattle-fleet-local-system to enforce:psa:privileged , both rancher-provisioning-capi-patch-sa job and the fleet-agent job are successful
without doing this, the cluster never resolves and is basically unusable

tested versions:
(Tim): v2.7.7-rc4
Caleb: v2.7-head and v2.8-head

I would suspect that the issue here is that changes that were made to introduce the new CAPI chart may not have been coordinated with changes to FeatureAppNS list, which should track all feature chart / system namespaces to exclude PSA enforcements from them.
cattle-fleet-local-system and cattle-provisioning-capi-system (the CAPI Provisioning Namespace that is set as the chart's release namespace do not appear to be in this list, so the fix should simply be to add those namespaces to the list.

using these namspaces in the pod security configuration, I was able to resolve the issue for fleet. It appears that cattle-provisioning-capi-system is missing from this list though.

/forwardport v2.8.0

Test Environment:
Rancher version: v2.7-head 1d25044
Rancher cluster type: HA
Docker version: 20.10
Downstream cluster type: RKE2 node driver cluster

Testing:
Tested this issue with the following steps:

Provision RKE2 AWS node driver cluster

Result
The job no longer fails but the cluster still isn't able to come up.

@Oats87 Should I close this ticket now that the job isn't faililng and open a different issue? The cluster went to delete after about 5 minutes and is now just stuck in deleting

My bad @Oats87 this was an issue with our jenkins job which was fixed here https://github.com/rancher/rancher/pull/42743
Closing this issue as fixed.


[neuralnet] Bug fix for graph usage

Bug fix patch to use constant iterators for the graph.
Signed-off-by: Parichay Kapoor<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #1299. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnstreamer.mooo.com/.


[Feature Request]: socks5h supports.

Describe the feature / enhancement and how it would improve things
werner@X10DAi:~/Public/repo/github.com/acheong08/ChatGPT-to-API.git$ http_proxy=socks5h://<IP_ADDRESS>:18890 SERVER_PORT=18080 ./freechatgpt
[GIN-debug] [WARNING] Creating an Engine instance with the Logger and Recovery middleware already attached.

[GIN-debug] [WARNING] Running in "debug" mode. Switch to "release" mode in production.
 - using env:	export GIN_MODE=release
 - using code:	gin.SetMode(gin.ReleaseMode)

[GIN-debug] GET    /ping                     --> main.main.func1 (4 handlers)
[GIN-debug] PATCH  /admin/password           --> main.passwordHandler (5 handlers)
[GIN-debug] PATCH  /admin/tokens             --> main.tokensHandler (5 handlers)
[GIN-debug] PATCH  /admin/puid               --> main.puidHandler (5 handlers)
[GIN-debug] PATCH  /admin/openai             --> main.openaiHandler (5 handlers)
[GIN-debug] OPTIONS /v1/chat/completions      --> main.optionsHandler (4 handlers)
[GIN-debug] POST   /v1/chat/completions      --> main.nightmare (5 handlers)
[GIN-debug] GET    /v1/engines               --> main.engines_handler (5 handlers)
[GIN-debug] GET    /v1/models                --> main.engines_handler (5 handlers)
2023/08/02 14:26:28 17121 <IP_ADDRESS>:18080
[GIN] 2023/08/02 - 14:26:41 | 500 |  791.445879ms |       <IP_ADDRESS> | POST     "/v1/chat/completions"

werner@X10DAi:~/Public/repo/github.com/acheong08/ChatGPT-to-API.git$ curl -v http://<IP_ADDRESS>:18080/v1/chat/completions -d '{"messages": [{"role": "user", "content": "Say this is a test!"}],"stream": true}'
*   Trying <IP_ADDRESS>:18080...
* Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 18080 (#0)
> POST /v1/chat/completions HTTP/1.1
> Host: <IP_ADDRESS>:18080
> User-Agent: curl/7.81.0
> Accept: */*
> Content-Length: 81
> Content-Type: application/x-www-form-urlencoded
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 500 Internal Server Error
< Access-Control-Allow-Headers: *
< Access-Control-Allow-Methods: *
< Access-Control-Allow-Origin: *
< Content-Type: application/json; charset=utf-8
< Date: Wed, 02 Aug 2023 06:26:41 GMT
< Content-Length: 33
<
* Connection #0 to host <IP_ADDRESS> left intact
{"error":"error sending request"}

Describe how your proposal will work, with code and/or pseudo-code
This is because tls-client does not support socks5h currently.
See https://github.com/acheong08/ChatGPT-to-API/issues/104#issuecomment-1661532075 for the related comment.

Just leaving this as a reference here for now: https://github.com/golang/go/issues/13454


PDI-5204 - Renaming a file in Kettle's repository explorer does not set comments in the commit

These changes are connected with pull request (https://github.com/pentaho/pdi-ee-plugin/pull/86) to pdi-ee-plugin.

closing since the pdi-ee one was also closed.


dont run tiny_dset workflow when markdown files are changed

don't run tiny_dset test when changing, for example, documentation, which doesn't affect the dataset prep/loading

Awesome! Thanks Jeff!


Added parallax effect for cupertino fullscreenDialog

Description
Added the slideTransition for the parallax effect when a route was pushed as fullscreenDialog.
Related Issues
Fixes #20073
Tests
Added test that check that the parallax effect is working and is not used if a fullscreen routes is push over.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[ x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x ] I signed the CLA.
[x ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ x] I updated/added relevant documentation (doc comments with ///).
[x ] All existing and new tests are passing.
[x ] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x ] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x ] No, no existing tests failed, so this is not a breaking change.

@xster I updated the names of the test, added that both fullscreen dialog and non fullscreen dialog cases are tested and updated the comments such that they reflect which animations are affected by the linearTransition boolean.
Turns out that the comment on CupertinoPageTransition said that only the primary animation would be affected but that was not true so also updated that one.

Someone complained about the breakage: https://stackoverflow.com/questions/61075440/after-latest-flutter-upgrade-project-is-not-building
While I understand that this isn't strictly considered breaking according to the breaking change policy, in this case it's clearly from a complete lack of testing.  A @required named parameter was changed; anyone using CupertinoFullscreenDialogTransition cannot avoid being broken.  This should fall under:

In cases where we can imagine reasonable scenarios where developers would be affected negatively, by courtesy, once the change has landed, engineers are encouraged to announce the changes by sending an e-mail to flutter-announce and listing it on our Changelog wiki page (such that they will be included in our release notes)

It looks like we broke the extended_images pub package https://github.com/fluttercandies/extended_image/blob/f65ce8f5dd37b3d54d14422adf31e40a98c435f0/lib/src/gesture/extended_image_slide_page_route.dart#L331.
@Kavantix would you like to create an announcement message and send it to flutter-announce? I'll help you approve the group message. See https://github.com/flutter/website/blob/master/src/docs/release/breaking-changes/template.md for a message template.
I'll add this change to the changelog.

Sure I’ll do that.
Shouldn’t the changelog also reflect that two other required parameters where added @xster?


Globally turn off the draw.io link from the Sidebar from all spaces

"It is cluttering the UI."
https://community.atlassian.com/t5/Confluence-questions/Remove-draw-io-from-sidebar/qaq-p/1449226

Unfortunately, this isn't technically possible.

We use draw.io in some spaces, but not others. It's not used in our public facing space, so when the user clicks it, it always shows empty.
 They sit, in context, on each page, which suffices for us.

If this is Done, then how does one remove the link from the menu in a space?


Fix the selection box does not move when the mouse is moved out

Fix the selection box does not move when the mouse is moved out. For example, if you select a DOM node and switch to another software through Alt+Tab, the selected box will be fixed

Add display font size attribute

@GrayLinTouchWorld Sorry for the long wait, I am picking up again this project lately. Thank you very much for your contribution!


FATAL: The configured certfile is not found

Problem/Motivation

Pi-hole can't be started. I would like to use it again :)

Expected behavior

Expected Pi-hole to start, it doesn't.

Actual behavior

Fails at "FATAL: The configured certfile is not found" and exits.

Steps to reproduce

I was running v2.0.1 without any issues. Updated to v2.0.2 and was unable to start Pi-hole. Updating to v2.0.3 didn't change this, neither did v2.0.4.

Log output:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] 01-resolver-resolv: applying...
[fix-attrs.d] 01-resolver-resolv: exited 0.
[fix-attrs.d] 01-sudo: applying...
[fix-attrs.d] 01-sudo: exited 0.
[fix-attrs.d] 02-nginx: applying...
[fix-attrs.d] 02-nginx: exited 0.
[fix-attrs.d] 03-pihole: applying...
[fix-attrs.d] 03-pihole: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing...
-----------------------------------------------------------
 Hass.io Add-on: Pi-hole v2.0.4
 Network-wide ad blocking using your Hass.io instance
 From: Community Hass.io Add-ons
 By: Franck Nijhof<EMAIL_ADDRESS>-----------------------------------------------------------
 armhf / HassOS 1.9 / HA 0.76.2 / SU 127 / stable
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing...
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-requirements.sh: executing...
INFO: Password is NOT in the Have I Been Pwned database! Nice!
FATAL: The configured certfile is not found
[cont-init.d] 10-requirements.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing...
-----------------------------------------------------------
                Oops! Something went wrong.

 We are so sorry, but something went terribly wrong when
 starting or running this add-on.

 Be sure to check the log above, line by line, for hints.
-----------------------------------------------------------
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.

The error is pretty clear, you linked a certfile while it's not there.
Check your add-on config, especially ssl:, which is now true by default.

Makes no sense that the add-on fails after an update, unless it has altered the config.

@SirJMD It changed defaults, if you were on the old default, Hass.io (not the add-on) changes it, even on existing installations. This is IMHO a failure with Hassio. Feel free to create an issue there, since this is out of scope and out of control for the add-on.
To cope with this change, it was made in a major release of the add-on, as major version can contain backward breaking changes (as per documentation of the add-on).


Update App.css

That the file where i have added a height=50px in name-folder class .By doing this it will make the contributors page look better.

Looks good to me 👍

Thank u
Btw you have done a great job
Keep going
On Sun, Oct 3, 2021, 18:06 GAURAV SINHA @.***> wrote:

Merged #26 https://github.com/gauravsinhaweb/EduSmart/pull/26 into main.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/gauravsinhaweb/EduSmart/pull/26#event-5399704866, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ATN4OEPWR2QPUV2PFYSZNILUFBE5RANCNFSM5FHQ2I7A
.


encode_packed produces wrong output

Version
2.0.0
Platform
Darwin (mac os) M1 apple cpu
Description
the abi.encode_packed function does not produce the output described in the Solidity spec.
A negative i16 -1 seems to be interpreted by ethers-rs as a uint256.
types: [ "int16", "uint48" ]
values: [ "-1", "12" ]
ethers-js: "0xffff00000000000c"
ethers-rs: "0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff0c"

Another example where the packages disagree:
types: [ "uint256", "uint256" ]
values: [ "8", "16" ]
ethers-js: "0x00000000000000000000000000000000000000000000000000000000000000080000000000000000000000000000000000000000000000000000000000000010"
ethers-rs: "0x0810"

Please see #2225 and the docs of the function.

Please see #2225 and the docs of the function.

Thanks. I just reviewed these. It sounds like people are not concerned that the ethers-rs implementation differs from the Solidity implementation, because the limitations of the ethers-rs implementation are known (e.g. can't distinguish between uint sizes). Is that an accurate summary?

Yeah, the biggest limitation is that we are delegating most of the ABI encoding functionality to an external crate (ethabi), which is fine until we want to add new functionality to it, like encode_packed, which requires a different API.. I think this is a goal for 3.0 tho


Please add a build file for Apple M1

Hi there
Apparently, a lot of packages including the tf-agents library are dependant on this library. It would be great if you could add a build for Apple's M1 macs.
Thank you so much for your time and affords

I'd deeply appreciate if you did this too!

Would love this as well

I was able to install dm-tree on a M1 by installing directly from github using pip. (But make sure you have cmake installed)
pip install cmake
pip install git+git://github.com/deepmind/tree.git

Hope this helps 😁


TestCreateCatalog fail when DEFAULT_RUNTIME_VERSION=3.6.0-SNAPSHOT

What happened?
--- FAIL: TestCreateCatalog (4.12s)
catalog_test.go:115:
Error Trace:    /home/claudio/alphaworks/projects/camel-k/pkg/controller/integrationplatform/catalog_test.go:115
Error:          Not equal:
expected: "Ready"
actual  : "Error"

Diff:
--- Expected
+++ Actual
@@ -1,2 +1,2 @@
-(v1.IntegrationPlatformPhase) (len=5) "Ready"
+(v1.IntegrationPlatformPhase) (len=5) "Error"

Test:           TestCreateCatalog
catalog_test.go:116:
Error Trace:    /home/claudio/alphaworks/projects/camel-k/pkg/controller/integrationplatform/catalog_test.go:116
Error:          Not equal:
expected: "True"
actual  : "False"

Diff:
--- Expected
+++ Actual
@@ -1,2 +1,2 @@
-(v1.ConditionStatus) (len=4) "True"
+(v1.ConditionStatus) (len=5) "False"

Test:           TestCreateCatalog
catalog_test.go:122:
Error Trace:    /home/claudio/alphaworks/projects/camel-k/pkg/controller/integrationplatform/catalog_test.go:122
Error:          Should NOT be empty, but was []
Test:           TestCreateCatalog
FAIL

Steps to reproduce
make DEFAULT_RUNTIME_VERSION=3.6.0-SNAPSHOT test
Relevant log output
No response
Camel K version
No response

I think this is fixed.


Dependencies causing issues DCM action

Describe the bug
Apparently, the DCM action cannot pull dependencies due to mocktail's dependencies being behind DCM's. I find these kinds of errors quite difficult to read, so I'm hoping someone here can confirm that this is indeed the issue (I filed an issue with DCM, it's been a week with nothing).
To Reproduce
This only happens when I run the DCM action on my PR, which is difficult to replicate unless you fork my repo and run a dummy PR on it to match what I currently have up. I'm reluctant to advise going through that process, but that's the best way I can think of to reproduce.
Expected behavior
N/A
Screenshots

Logs
Already linked above.

Paste the output of running flutter doctor -v here.
N/A since the issue is with a GitHub action. DCM works fine as part of my project itself.

Additional context
N/A other than it is worth noting I've tried several times to pin specific versions of dependencies that are noted in the action log, with no success. But again, I've always found such errors difficult to decipher properly. I'm really just going off the summary of the log, which reads  So, because macos_ui depends on both dart_code_metrics ^5.5.1 and mocktail ^0.3.0, version solving failed. 🤷

Hey @GroovinChip 👋
I can take a closer look shortly but my immediate thought is your GitHub workflow is using an older version of Flutter. Can you confirm that your PR checks are running using the latest stable version of Flutter? Thanks!

Hi @felangel! I can confirm that my workflow is using the latest stable version of Flutter - see here.

Resolved! I was using an older version of the action. Embarrassing!!

Resolved! I was using an older version of the action. Embarrassing!!
Glad you figured it out! 🎉


User documentation for Pascal VOC format

Summary
Added user documentation for Pascal VOC format https://github.com/openvinotoolkit/datumaro/issues/224
How to test

Checklist

[ ] I submit my changes into the develop branch
[ ] I have added description of my changes into CHANGELOG
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues)

License

[ ] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[ ] I have updated the license header for each file (see an example below)

# Copyright (C) 2020 Intel Corporation
#
# SPDX-License-Identifier: MIT

Please, update the changelog, and merge.


Feature request: customise the bahaviour for parameter array

Hello,
currently if I use an array for a parameter Alamofire URL method encodes it with square bracket like:
&foo[]=bar&foo[]=bar2

I understand the meaning and it is also specified that:
Since there is no published specification for how to encode collection types, the convention of appending `[]` to the key for array values (`foo[]=1&foo[]=2`), and appending the key surrounded by square brackets for nested dictionary values (`foo[bar]=baz`)

However, even some modern servers that uses RestEasy with JAX-RS accept this format for arrays:
&foo=bar&foo=bar2

For this reason, I'd like to propose to have the ability to customise this behaviour with an option in order to support both cases.
It's a simple change that I can help doing and I think it will add flexibility to the library and will avoid the usage of the Custom method for this simple case.
What do you think?
Thanks,
Dem

+1. Exactly the issue I'm dealing with currently. I'm pretty sure this would be pretty straightforward to implement.

I'm going to go ahead and close this issue out. Please see my comments in #966. Cheers. 🍻

Needless to say I don't agree that it's not commonly used, maybe in your experience it's not but I'm using a commonly used modern java framework so it's not that unusual. Also, beside the pull proposal from DavidRoman, it can be implemented in a backward compatible way (default config is like it is now, and you can change if you want) and you will support both commonly used use cases.
Obviously you (the team) decide what you want to do, but saying "it's not commonly used" is not an acceptable answer in my opinion.
Same thing for multiple encoding methods in a single request (https://github.com/Alamofire/Alamofire/issues/374): you (the team) say it's not common but again it's not common for you, it's a very common pattern that happens regularly and it feels like Alamofire doesn't support basic patterns out of the box.
Cheers,
Dem

Just to be clear, at no point did I claim that the PR was declined because "it's not commonly used". I declined it for other reasons which were very cleared documented. Additionally, I think you are assuming a bit too much here. At no point have we claimed we'll never support this feature. It's actually in our Trello backlog and has been for a while. I think I could have done a better job explaining that in my previous comment to avoid confusion...my bad there.
We completely understand there's a need for such a feature and want to support feature requests the best we possibly can. With that said, we have a very large community that we always need to consider when adding complexity into our APIs. This is definitely one of those features that we need to be careful how we introduce.
Please be patient because there are many features here we are actively supporting. If you feel that you would like to see this feature added sooner than we will be able to, then by all means submit a complete, well thought out pull request. We'll be more than happy to consider it. But please understand that it is certainly in the community's best interest for us to decline PRs once in a while that aren't up to our standards or designed in a way that we deem suitable.

Thank you for "New Parameter Encoding Protocol". It is the great benefit
Now how to use it? How to convert code from  @DavdRoman answer?


[App Engine] Wordpress Standard Environment - Functionality to use CloudSQL 2nd gen

When running the WordPress code generation, It does not let you populate the CloudSQL connection name with the region. I have created a fork with a rough implantation of this feature.
Would there be an interest to add the functionality to choose between using 1st or 2nd generation CloudSQL instance?
Current example behavior:
:/cloudsql/{{project_id}}:{{db_instance}}

Expected example behavior:
:/cloudsql/{{project_id}}:{{db_region}}:{{db_instance}}

@1MichaelOHara Yes! Please submit a PR with your changes and we will definitely look at merging. I think this would be great functionality.


Add a php cs file

Proposal for a cs file see #1 and #2
We all have our habits, way of doing thing, etc... IMO having a common style for code is necessary, however choice of rules should not take forever. Then i want to propose the following workflow for choosing coding rules :

Every contributor can propose a rule in a new issue / pull request
Every contributor should do a vote about the rule: +1 / 0 (don't give a fuck) / -1
After 1 week on the proposed rule, vote are counted, and if it's win by majority (50% + 1), rule is added / removed to the cs file

(A contributor in this case is someone who belongs to the organisation)
This is mainly to avoid useless debate for something which is highly subjective.
This cs file include all psr1 and psr2 rules as the base coding style.
If workflow is agreed by everyone, i will propose some other rules.

i agree we should have a common code style and find your proposal fine.
i would be happy to stick with the symfony CS and not create exceptions
for whitespace (more to avoid discussion than because of a strong opinion)
+1 for the short array syntax (its what we do already) and the ordered
use statements.
what about using the styleci service? the upshot is that this can be
integrated into the pull requests here on github, and their service can
even provide a patch / do a pull request against the branch with the cs
fixes that can be done automatically.

+1 from me for both the workflow and the proposal.
I was also thinking about styleci, but I am not as impressed now as I was when I found it. What can Style CI do that Scrutinizer doesn't? Also, it seems creating CIs is the hype nowadays.
https://houndci.com/
That said, if you think it worth and gives us something more than Scrutinizer, then I would happily set it up. For example I am not sure if Scrutinizer breaks the build or automatically opens a PR.

styleci is convenient because we would not need to change the travis
build at all, its a completely separate integration and only about cs.
scrutinizer is about coverage and such afaik, less about cs.

Ok, convinced me.

+1 for the short array syntax (its what we do already) and the ordered
use statements.

Sorry @dbu i have remove those rules / proposal and also the symfony one, as i don't want to introduce new rules here (2 different purposes) and just want to agree on a operation workflow for the moment.
(I will add these in another issue)

Cool, let's go ahead then.

Hello !
Do you plan to add the php-cs-fixer dependency to composer or do you think it's better to require a global installation on developer computer ?

I think it is better kept out of the composer dependencies.

Do you plan to add the php-cs-fixer dependency to composer or do you
think it's better to require a global installation on developer computer ?

the idea is to commit it in each of the repositories. there would even
be a script that we could adapt to sync the files that must be the same
into all our repos:
https://github.com/dantleech/cmf-utils/blob/master/scripts/sync_styleci


Fix issue #1576

Pull Request Type
What kind of change does this PR introduce?
[ * ] Solved an issue/task
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:
What is the current behavior?
Footer is not present.
Issue Number: #1576
What is the new behavior?
A footer with a copyright notice has been added.

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out our forkcommitmerge.io website repository. The repository contain real issues that you can help to resolve or create some of your own if you see any bugs or want to add new features to the site, etc. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!


Windows 10 - 64bit installation error

2017-09-27 00:20:29> Program: Starting Squirrel Updater: --install .
2017-09-27 00:20:29> Program: Starting install, writing to C:\Users\AnimeUser.DESKTOP-8IJDHDB\AppData\Local\SquirrelTemp
2017-09-27 00:20:30> Program: About to install to: C:\Users\AnimeUser.DESKTOP-8IJDHDB\AppData\Local\atom
2017-09-27 00:20:30> CheckForUpdateImpl: Couldn't write out staging user ID, this user probably shouldn't get beta anything: System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\AnimeUser.DESKTOP-8IJDHDB\AppData\Local\atom\packages.betaId'.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.StreamWriter.CreateFile(String path, Boolean append, Boolean checkHost)
at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize, Boolean checkHost)
at System.IO.File.InternalWriteAllText(String path, String contents, Encoding encoding, Boolean checkHost)
at System.IO.File.WriteAllText(String path, String contents, Encoding encoding)
at Squirrel.UpdateManager.CheckForUpdateImpl.getOrCreateStagedUserId()
2017-09-27 00:20:30> CheckForUpdateImpl: Failed to load local releases, starting from scratch: System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\AnimeUser.DESKTOP-8IJDHDB\AppData\Local\atom\packages\RELEASES'.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
at Squirrel.Utility.LoadLocalReleases(String localReleaseFile)
at Squirrel.UpdateManager.CheckForUpdateImpl.d__2.MoveNext()
2017-09-27 00:20:30> CheckForUpdateImpl: Reading RELEASES file from C:\Users\AnimeUser.DESKTOP-8IJDHDB\AppData\Local\SquirrelTemp
2017-09-27 00:20:30> CheckForUpdateImpl: First run or local directory is corrupt, starting from scratch
2017-09-27 00:20:32> ApplyReleasesImpl: Writing files to app directory: C:\Users\AnimeUser.DESKTOP-8IJDHDB\AppData\Local\atom\app-1.20.1
2017-09-27 00:20:41> LogHost: Rigging execution stub for atom_ExecutionStub.exe to C:\Users\AnimeUser.DESKTOP-8IJDHDB\AppData\Local\atom\atom.exe
2017-09-27 00:21:16> IEnableLogger: Failed to install package to app dir: System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
at System.IO.Directory.InternalCreateDirectory(String fullPath, String path, Object dirSecurityObj, Boolean checkHost)
at System.IO.Directory.InternalCreateDirectoryHelper(String path, Boolean checkHost)
at System.IO.Directory.CreateDirectory(String path)
at Squirrel.ReleasePackage.<>c__DisplayClass15_0.b__0()
at System.Threading.Tasks.Task.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Squirrel.UpdateManager.ApplyReleasesImpl.<>c__DisplayClass7_0.<b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Squirrel.Utility.d__431.MoveNext() 2017-09-27 00:21:16> Unhandled exception: System.AggregateException: One or more errors occurred. ---> System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.    at System.IO.Directory.InternalCreateDirectory(String fullPath, String path, Object dirSecurityObj, Boolean checkHost)    at System.IO.Directory.InternalCreateDirectoryHelper(String path, Boolean checkHost)    at System.IO.Directory.CreateDirectory(String path)    at Squirrel.ReleasePackage.<>c__DisplayClass15_0.<ExtractZipForInstall>b__0()    at System.Threading.Tasks.Task.InnerInvoke()    at System.Threading.Tasks.Task.Execute() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Squirrel.UpdateManager.ApplyReleasesImpl.<>c__DisplayClass7_0.<<installPackageToAppDir>b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Squirrel.Utility.<LogIfThrows>d__431.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at Squirrel.UpdateManager.ApplyReleasesImpl.d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Squirrel.UpdateManager.d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at Squirrel.Update.Program.d__4.MoveNext()
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at System.Threading.Tasks.Task.Wait()
at Squirrel.Update.Program.executeCommandLine(String[] args)
at Squirrel.Update.Program.main(String[] args)
---> (Inner Exception #0) System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
at System.IO.Directory.InternalCreateDirectory(String fullPath, String path, Object dirSecurityObj, Boolean checkHost)
at System.IO.Directory.InternalCreateDirectoryHelper(String path, Boolean checkHost)
at System.IO.Directory.CreateDirectory(String path)
at Squirrel.ReleasePackage.<>c__DisplayClass15_0.b__0()
at System.Threading.Tasks.Task.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Squirrel.UpdateManager.ApplyReleasesImpl.<>c__DisplayClass7_0.<b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Squirrel.Utility.d__43`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at Squirrel.UpdateManager.ApplyReleasesImpl.d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Squirrel.UpdateManager.d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at Squirrel.Update.Program.d__4.MoveNext()<---

Duplicate of https://github.com/atom/atom/issues/5109. Please see the workaround linked in the FAQ that I've directed you to.


Twitter OAuth Callback Issue

When I am using the API, for the Twitter, it is working absolutely fine but after the twitter auth process it showing the browser for few seconds (showing the callback url not found) and then it is automatically closing and working as it should. But it looks rather odd to show this to my ionic app users.
FYI: I m using callback url as "http://localhost/callback" in my ionic app.
I have seen the same issue in you issue list, but not sure what's elegant way for twiiter oauth.
Appreciate your co-operation.

For providers that don't offer implicit grants (Twitter), you'll need to override the redirect URL to one that actually exists remotely if you want to get rid of the screen.
Best,


Correction for raw affiliation Centre Genie Industriel—IMT Mines Albi, 81000 Grenoble, France; Physical Internet Center, Supply Chain & Logistics Institute, Atlanta, GA 30332, USA; School of Industrial and Systems Engineering, Georgia Institute of Technology, Atlanta, GA 30332, USA

Correction needed for raw affiliation Centre Genie Industriel—IMT Mines Albi, 81000 Grenoble, France; Physical Internet Center, Supply Chain & Logistics Institute, Atlanta, GA 30332, USA; School of Industrial and Systems Engineering, Georgia Institute of Technology, Atlanta, GA 30332, USA
raw_affiliation_name: Centre Genie Industriel—IMT Mines Albi, 81000 Grenoble, France; Physical Internet Center, Supply Chain & Logistics Institute, Atlanta, GA 30332, USA; School of Industrial and Systems Engineering, Georgia Institute of Technology, Atlanta, GA 30332, USA
new_rors: 01zkghx44;01xn7cv95;00bq8vv83
previous_rors: 01zkghx44;01xn7cv95;0455wwj08;00bq8vv83
works_examples: W4387132532
contact: b48287552bcef6a154e65563d441e20a:8341f371bc2e501adb79be33 @ centralesupelec.fr

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


update minimal advanced IAM policy template

It seems that the basic serverless configuration needs to be updated since the serverless framework is using API Gateway v2, bucket encryption, and some other things.
I updated it using the gist provided by serverless.com, while removing the advanced features (dynamodb, iot, kinesis, sns, and states). I also followed the same order to simplify future updates.

Thank you! Appreciate the PR.


Search All might look cleaner in a single table

Peforming a search all <search term> potentially produces output of multiple tables of varying column widths.
It might be nicer to default to all results in a single table with an exta column or header row to identify the channel.
Perhaps a --no-group or similar option to provide separate tables as now.
Some related ideas:

rich Tables can have their own headers: table_options so we could perhaps utilise that rather than outputting a seperate piece of text for the header
If we like the combined table idea, would it make sense to have a new CombinedSearch class with its own show_matches method, as the combined table might have an extra colunm for channel (tip/youtube etc) or additional header row to demark channels. If we like the --no-group idea then under that scenario the CombinedSearch class could just iterate the the default show_matches for each class

@greywidget so we got a combined table, do you still want to do --no-group? I am happy with how things are now (1.0.0) - thanks!

OK, after a bit of a play, I think it messes the code too much for something we don't currently have a requirement for. I'm happy to leave it as it is for now - I think there are better gains to be had elsewhere.

OK thanks for confirming.


Add zip_map adaptor

Addresses, #172: The element type of flux::cartesian_product, cartesian_power and adjacent is a tuple of the element type(s) of the underlying sequences. These three adaptors also provide  *_map versions, which take an n-ary function and call it directly with the underlying  elements. This is to avoid forming a tuple and then immediately destructuring it, as would happen in a subsequent call to map(unpack(func)).
This commit adds the *_map version for the zip adaptor.

So first of all, please accept my apologies @isaacy2012 for letting this PR languish for months. I'm afraid I was pretty busy at the time you originally submitted it so I intended to review it later, and then I somehow I never got back to looking at it. I feel very bad!
The good news is that this PR looks great! I've just got a couple of small comments but otherwise this looks awesome.
If you've moved on in the intervening time and don't feel like coming back to this then I quite understand :). I'll be happy to do a final polish if you're busy with other things.
Thanks, and apologies again

Hi @tcbrindle, no worries at all, I'll address those changes this weekend :)

Thanks @isaacy2012!


[FEATURE] Implement Keyboard Shortcut to Delete Drawing on Screen

Feature Description
I have worked with similar drawing sites, and when I draw something and I want to delete / erase something, I have the habit of selecting it by mouse and delete / erase it using 'DELETE' button on my keyboard. This feature would be helpful for many people.
*Solution
When someone wants to delete / erase the drawing, they can simply select it using mouse and press delete button on keyboard.
I would like to work on this issue under GSSoC '24, request you to assign this task to me :)

Hi @yashmandi  thanks for opening an issue.
This is already implemented in the code , the problem right now is , it has been breaked by a PR , we are right now trying to resolve it . If you can resolve it , here is the PR that breaked it , i have also commented down in the PR itself. #41


gh: prefix doesn't work anymore

Cookiecutter version: 1.5.1
Template project url: gh:*
Python version: 2.7.13
Operating System: Linux

Description:
cookiecutter does not honor prefixes anymore.
What I've run:
Simply testing the example from the README doesn't work as expected:
$ cookiecutter gh:audreyr/cookiecutter-pypackage
A valid repository for "gh:audreyr/cookiecutter-pypackage" could not be found in the following locations:
gh:audreyr/cookiecutter-pypackage
/home/me/.cookiecutters/gh:audreyr/cookiecutter-pypackage

The same commands using the full repository path works as expected:
$ cookiecutter https://github.com/audreyr/cookiecutter-pypackage

Hi @noirbizarre! 👋
Thank you for pointing this out. I noticed this too and have done some work to address this, but don't have the time wrap up my PR at the moment.
You probably have abbreviations in your ~/.cookiecutterrc, right? The current implementation overwrites config keys, which means it discards the default values if you have any abbreviations in your user config.

Hey @noirbizarre, can you please review and/or try out #967?

Yes, you're right, I had abbreviations in my ~/.cookiecutterrc.
I reviewed your PR :+1:


problems with shapes using the same properties

Considre the following shapes:
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX xsd: <http://www.w3.org/2001/XMLSchema#>
PREFIX ex: <https://example.org/#>

<#Foo> {
  rdfs:label xsd:string
    // rdfs:comment "The label of this foo" ;
}

<#Bar> {
  a [ ex:Bar]
    // rdfs:comment "Instances of Bar have a unique Foo" ;
  ex:foo @<#Foo>
    // rdfs:comment "The unique Foo of this Bar" ;
}

<#Baz> {
  a [ ex:Baz]
    // rdfs:comment "Instances of Baz may have multiple Foos" ;
  ex:foo @<#Foo> +
    // rdfs:comment "The Foos of this Bar" ;
}

When I try to use this SHEX file with LDO, I fail to access the foo property in instances of Bar.
The cause seems to be the fact that the same property ex:foo is used also in the Baz shape, but with a different cardinality.
If I remove the ex:foo property from shape <#Baz>, or if I use the same cardinality in both shapes, the problem disappears. But I would like to be able to use the same property in different shapes with different cardinalities.

I created a minimal example manifesting this bug:
https://github.com/pchampin/ldo_issue_58
The last commit "works", but that was achieve by altering the SHEX file (commenting out the "overloaded" property),
but this is not a satisfying solution in the long term.


At what point does the program stop running

I'm running this code and it's working great! But I noticed that epoch has 1024 and I've run 110 of them now, each taking about a minute, will the program stop early?

1

do you solve this problem now?

do you solve this problem now?
I am running the experiment with the default settings (lr=0.002, n_labeled=250), and the accuracy keeps improving for the epochs above 200.


terraform-docs should not fail if complex types contain 'description' keyword

Fix description key inside type
This PR fixes a when a key named description is inside the type block of a variable section:
variable "ingress_cidr_blocks" {
  description = "Bzzzzz"
  type = list(
    object({
      description = string
      cidr_blocks = string
      from_port   = number
      to_port     = number
      protocol    = string
    })
  )

  default = [
    {
      description = "SG"
      cidr_blocks = "<IP_ADDRESS>/32"
      from_port   = 22
      to_port     = 22
      protocol    = "tcp"
    },
  ]
}

Refs: https://github.com/antonbabenko/pre-commit-terraform/issues/65
Refs: https://github.com/antonbabenko/pre-commit-terraform/issues/64
Refs: https://github.com/antonbabenko/pre-commit-terraform/pull/73
Refs: https://github.com/cloudposse/build-harness/issues/170
Refs: https://github.com/cytopia/docker-terraform-docs/pull/23

Integration tests
Test for this can be found here: https://github.com/cytopia/docker-terraform-docs/blob/master/tests/0.12/main.tf#L60
Reliability
I tried to fix this to the best of my knowledge and currently available test cases. Please do test this before merging on existing files.

@cytopia thanks, will close this one then


Unpublic elements getting rendered

Elements that are not public getting rendered in the preview and even after flushing the page cache.

Only on pages with cells.


SVG thumbnails for "Gallery" category

🚀 Feature
A default thumbnail is being used currently for a code block.
For the "Gallery" category, SVG thubmnails that represents the code block preview in an abstract manner (like a skeleton template) would help a user to get an intuition about the template in a glance in the sidebar itself
Have you spent some time to check if this issue has been raised before?
Yes
Have you read the Contributing Guidelines?
Yes
Pitch
This would enhance the user experience by providing a quick abstract preview of the code block in the sidebar that would reduce the time required to find the desired template. The thumbnail can be designed using any designing tool like Figma, Adobe XD etc.

I'll take this one

@erinknight242 Please take a look at this.

@VaibhavSaini19 may I have this one?

@erinknight242 you can work on the issues one by one. Please let me know which one you would like to be assigned for now, so that others can take up the other issues. When you are done with one, and other issues have not been assigned to someone else yet, we can assign that to you

@erinknight242 you can work on the issues one by one. Please let me know which one you would like to be assigned for now, so that others can take up the other issues. When you are done with one, and other issues have not been assigned to someone else yet, we can assign that to you

+1 on that @VaibhavSaini19. Assigning loads of issues to a single assignee might not be the wisest thing to do here.

Thanks @VaibhavSaini19, I understand. I am ready to work on these images now. If you wait to assign me the next one until the previous PR is merged, it will take multiple days to close them all out where I can just knock them out right now if they are marked for me. Feel free to assign as you prefer.

Cool, I'll assign you the next as soon as you are done with this one

Thanks @VaibhavSaini19, I understand. I am ready to work on these images now. If you wait to assign me the next one until the previous PR is merged, it will take multiple days to close them all out where I can just knock them out right now if they are marked for me. Of course as it's your project, feel free to assign as you prefer.

I understand that you mean well for the project @erinknight242 and we appreciate it. :smile: But we would want to give equal opportunity to everyone looking for candidate issues on hacktoberfest. Once you are done with one issue, we would certainly assign you with another.


bug: better handling of folds

Did you check the docs?

[X] I have read all the flash.nvim docs

Is your feature request related to a problem? Please describe.
currently matches inside folds are labeled
Describe the solution you'd like
need to think this through :)
Describe alternatives you've considered
not really
Additional context
No response

Could this be an option? Jumping to folds is quite useful sometimes

Whats the use-case? Using incremental mode?

No, just navigation. Sometimes I wanna jump to a fold and open it because the code I must read/modify is folded

It doesn't seem to be possible to set extmarks on the folded line.
With something like nvim-ufo, you will see the markers

@MariaSolOs I mean you can jump to the summary shown on the fold for a word in that fold.
Still need to make it so that a folded line also gets a label (one) when the text inside the fold matches the pattern.

Added proper support for folds.
The fold line will now show the label of the first match inside a fold. See example below:

The fold line will now show the label of the first match inside a fold.

Why limit the label to the first match? Not asking you to change this BTW, I'm just curious :)

Since you can't see the targets you are jumping to, I don't think it makes sense to show all the labels for items in the folds?

@folke What I had in mind is that say I'm jumping to the following line with se:
> fn folded_method () {

I thought something like this would happen (adding the labels to both occurrences of e):
> fn foldad_mxthod () {

Oh you mean on the foldtext? That's not how it currently works. It's also not straightforward to map actual cursor positions to a position inside the foldtext.
The feature I did add is say you have a multiline fold and the pattern matches something in line 3 of your fold, then you'd still be able to jump to that

That makes sense, thanks for explaining!


Tokota Duplication

https://gyazo.com/fc6826c8964e631e0b182d61fcef0fa3
https://gyazo.com/fa3873307fda92dc9f1496859b6530c2
Issue with pulling tokotas off the google sheet- tokotas are only listed once. I am using the fancy HP tracker. None of the names will load properly.

As of yesterday's update, tokota name duplication should be fixed. The patch is live on the website.
Some more technical details on the cause of the issue below, for the record:
This bug stemmed from an issue with how the code was searching and sorting tokotas. The sort algorithm was sorting case-insensitively but the search algorithm was searching case-sensitively, so the sort algorithm was putting some names in places the search algorithm didn't expect. This threw off the sorting of the entire list and made it impossible for the search algorithm to find many of the names.
If the search can't find a name in the list when it's reading the csv file, it assumes there is no tokota with that name yet and adds a new name to the list, which caused incorrectly sorted names to be duplicated several times. And if it can't find a name while generating a journal, it ends up trying to read from a section of the tokota list that doesn't exist, resulting in that "cannot read property of undefined" error.
Now that both the search and the sort operate case-sensitively, this issue should be gone.


handle negative numbers and small floats

PROBLEM
CWL converts all numbers smaller than 1e-5 to a string, even if the default is given as a number (0.00001)
- id: annotation_prokka_evalue
 type: float?
 default: 0.00001
 inputBinding:
 prefix: --annotation_prokka_evalue

gives this error:
ERROR: Validation of pipeline parameters failed!
* --annotation_prokka_evalue: expected type: Number, found: String (1e-05)

It does not happen for floats >0.0001, though. Also, negative numbers in the default are passed as a string.
SOLUTION
Define these numbers as strings in the .cwl file, e.g.:
type: string?
default: '0.000001'

TASK
The defaults taken from the nextflow_schema.json have either to be checked if they are <0.0001 and if so, written to the .cwl file as string? OR all input taken from the .json has to be written as a string? in the .cwl.

@louperelo Is that with cwltool or a different CWL engine?

It is with cwltool.
I try to call the pipeline with cwltool pipeline.cwl runs.yml
There is a longer conversation on DataPlant Teams about the two issues I am having at the moment.

Does type: double? behave differently?

No, it unfortunately behaves the same as with type: float?.

This is a cwltool bug; we will fix it and add a new conformance test! https://github.com/common-workflow-language/cwltool/issues/1831

Great news! Thank you @mr-c!

A new release of cwltool is out, with the fix: https://github.com/common-workflow-language/cwltool/releases/tag/3.1.20230424211314 a.k.a. https://pypi.org/project/cwltool/3.1.20230424211314/


add "std-unwrap" feature to defer to std's unwrap in unwrap_throw

In our release binaries .unwrap() gives a useful error:
Error: panicked at crates/lang/src/count.rs:22:64:
called `Option::unwrap()` on a `None` value

Whereas .unwrap_throw() does not:
Error: `unwrap_throw` failed

error.stack
Error: `unwrap_throw` failed
wasm_bindgen::throw_str::h52b6facbb28affa2@[wasm code]
<futures_util::stream::stream::for_each::ForEach<St,Fut,F> as core::future::future::Future>::poll::h63f690969fd636cf@[wasm code]
tokio::runtime::task::raw::poll::h14ea459da51d02f6@[wasm code]
concurrency_utils::try_future::try_::{{closure}}::hef4fe39654304a7f@[wasm code]
<dyn core::ops::function::FnMut<()>+Output = R as wasm_bindgen::closure::WasmClosure>::describe::invoke::h4114b59fa0fc4be3@[wasm code]
A@https://tably.com/xxx:1:1125947
_dyn_core__ops__function__FnMut_____Output___R_as_wasm_bindgen__closure__WasmClosure___describe__invoke__h4114b59fa0fc4be3@https://tably.com/xxx:1:1128611
x@https://tably.com/xxx:1:1179277
__wbg_try_b1e23a7f21a743ba@https://tably.com/xxx:1:1128574
<futures_util::future::maybe_done::MaybeDone<Fut> as core::future::future::Future>::poll::h685a6becb168fdad@[wasm code]
<concurrency_utils::task::DropFuture<F> as core::future::future::Future>::poll::h0af0a15d821db4ce@[wasm code]
wasm_bindgen_futures::queue::Queue::new::{{closure}}::h46010d614ba0d67e@[wasm code]
<dyn core::ops::function::FnMut<(A,)>+Output = R as wasm_bindgen::closure::WasmClosure>::describe::invoke::h018270bf1cf615d6@[wasm code]
E@https://tably.com/xxx:1:1126097
s@https://tably.com/xxx:1:1125704

Currently, enabling debug_assertions is the only way to have .unwrap_throw() print the call site:
https://github.com/rustwasm/wasm-bindgen/blob/78463a2fd7ade4a975b2c4a28b508732173cd0a6/src/lib.rs#L1330-L1344
Gating on debug_assertions was intended to avoid increasing code size in release mode. Unfortunately though it makes debugging panics in release binaries significantly harder, given many fundamental libs including wasm-bindgen-futures, yew and leptos use .unwrap_throw().
This PR adds a feature "std-unwrap" to make fn unwrap_throw and fn expect_throw defer to fn unwrap and fn expect respectively. This allows applications to trade off a potentially negligible increase in code size for useful panic messages. Some measurements from our production application:

call site in panic message
Wasm bin compressed size
% increase

debug_assertions = false
no
4,237,448
-

debug_assertions = true
yes
4,269,427
0.75%

debug_assertions = false, features = ["std-unwrap"]
yes
4,239,307
0.04%

I'm not in favor of adding a crate feature for this kind of adjustment.
However, it would be great if you could dig into why this was guarded behind cfg(debug_assertions) in the first place, then we could just remove the guard.

The original motivation in #1219 for these traits was to create variants with "a smaller code size footprint than the normal Option::unwrap and Option::expect methods".
Printing the call site was added in #2995. That PR initially unconditionally printed the call site but that was objected to on code size grounds. A compromise was suggested:

I think it would be really useful if unwrap_throw displayed filename and line numbers in debug mode (but not release mode).

and this was implemented by gating on cfg(debug_assertions).
I understand the motivation but debug_assertions is orthogonal to "give useful panic messages". In a production application we need useful panic messages but would rather not take the unpredictable performance and code size hit of enabling debug_assertions. As there's no way around this we're using and maintaining this fork.
I understand the reticence to adding a crate feature so if you have any alternative suggestions please do say.

The original motivation in #1219 for these traits was to create variants with "a smaller code size footprint than the normal Option::unwrap and Option::expect methods".
Printing the call site was added in #2995. That PR initially unconditionally printed the call site but that was objected to on code size grounds. A compromise was suggested:

I think it would be really useful if unwrap_throw displayed filename and line numbers in debug mode (but not release mode).

and this was implemented by gating on cfg(debug_assertions).

Thank you for the research!

I understand the reticence to adding a crate feature so if you have any alternative suggestions please do say.

I would recommend you to explore generating source maps as this would significantly improve your debugging experience in many ways. Let me know if you have any trouble with it.
If that doesn't really work for you, I think the alternative to a crate feature would be something like cfg(wasm_bindgen_unwrap_throw_debug), which I think would be acceptable for wasm-bindgen.

Source maps would help debugging on our machines right? It's specifically crashes that occur on user machines where we need this. For crashes on our machines Chrome's DWARF extension gives us a pretty decent debugging experience.

Source maps work on user machines as well, they also work on all current browsers without the need for any extension.
If you don't want to expose any debug information to users, you may want to take a look at Wasm coredumps.

Source maps work on user machines as well, they also work on all current browsers without the need for any extension.

Is there any documentation that they give Wasm stack traces line numbers? I only found the opposite.

If you don't want to expose any debug information to users, you may want to take a look at Wasm coredumps.

I didn't think this was implemented in any browsers yet?

Source maps work on user machines as well, they also work on all current browsers without the need for any extension.

Is there any documentation that they give Wasm stack traces line numbers? I only found the opposite.

I'm not sure where to find any documentation on this, but source maps do include line numbers and from personal testing I can say that it looks like native stacktraces.

If you don't want to expose any debug information to users, you may want to take a look at Wasm coredumps.

I didn't think this was implemented in any browsers yet?

I'm not aware of any actual proposal that needs implementing, these are just tool conventions. If you follow the links on this page you will even find a live demo to try it out yourself.

Thanks for the pushback @daxpedda! I looked into this a little more and decided this approach doesn't sufficiently mitigate the unsoundness we've seen the effects of. As Alex said, Wasm-bindgen also offers the ability to throw a JS exception at any point from within wasm which is basically unsound and can't be used properly anyway. Instead we're strengthening our poisoning until #3687 is implemented. I'll go ahead and close this.

I'm not sure where to find any documentation on this, but source maps do include line numbers and from personal testing I can say that it looks just like native stacktraces.

I'm not seeing source maps affecting Error().stack for Wasm frames, unless I'm doing something wrong. Perhaps you're referring to the debugger's call stack, which is was I was referring to as workable on our but not on user machines.

I'm not aware of any actual proposal that needs implementing, these are just tool conventions. If you follow the links on this page you will even find a live demo to try it out yourself.

Thanks for making me aware of it but it's sadly not workable. It's not implemented by browsers yet and so requires a sketchy polyfill wasm-coredump-rewriter to "rewrite[s] [the] Wasm module and inject the core dump runtime functionality in the binary" per Cloudflare which will break the debuggability we already have from DWARF debuginfo.

I'm not sure where to find any documentation on this, but source maps do include line numbers and from personal testing I can say that it looks just like native stacktraces.

I'm not seeing source maps affecting Error().stack for Wasm frames, unless I'm doing something wrong. Perhaps you're referring to the debugger's call stack, which is was I was referring to as workable on our but not on user machines.

I just tested it with Error.stack and it works for me. Maybe something went wrong in your source map generation, I've used wasm2map, maybe that works for you as well.

I'm not aware of any actual proposal that needs implementing, these are just tool conventions. If you follow the links on this page you will even find a live demo to try it out yourself.

Thanks for making me aware of it but it's sadly not workable. It's not implemented by browsers yet and so requires a sketchy polyfill wasm-coredump-rewriter to "rewrite[s] [the] Wasm module and inject the core dump runtime functionality in the binary" per Cloudflare which will break the debuggability we already have from DWARF debuginfo.

The Cloudflare blog post you linked has a decent overview how to work with it. Breaking the DWARF debuginfo would defeat the purpose of a core dump, so it actually still works.
Wasm post-processing isn't ideal, but it is the status quo right now, wasm-bindgen itself is a Wasm post-processor, so hopefully that shouldn't be a blocker by principle.

Sorry for the delayed response!


Github Actions to build binaries and deploy to releases page

FB rapidly changes so will be good to keep it fresh

Perhaps better to have a way to auto-update the app?

Yanone says:

Also, instead of implementing an auto-update feature, maybe just have the app check with the fontbakery repo for the existence of a newer version. If the app is indeed built automatically alongside fontbakery, one just needs to compare the version of the bundled fontbakery module with the online one.

I figure maybe having the app run pip (as a library) on launch to test if there is an upgrade available, upgrade its internal copy of qfontbakery, and restart.

Well, I've added code to prompt the user to update things, but it seems like we're onto a loser here for MacOS.

py2app comes with its own stripped-down version of site.py (which is required by pip) which doesn't include a USER_BASE variable. pip tries to import USER_BASE and crashes.
We can't put updated fontbakery libraries into the app into the app itself, because that will break the code signing.
So at the very least we need a custom py2app with a sensible USER_BASE which copies the logic from the stock Python _getuserbase and finds the user home directory, then fiddle with sys.path early in the process to look for updated code in the user home directory.

I don't know if I've fixed auto-updates. However, I have sorted out Continuous Deployment, which is the point of this issue.


SPARK-5841 [CORE] [HOTFIX] Memory leak in DiskBlockManager

Avoid call to remove shutdown hook being called from shutdown hook
CC @pwendell @JoshRosen @MattWhelan

Test build #27627 has started for   PR 4648 at commit 51548db.

This patch merges cleanly.

Test build #27627 has finished for   PR 4648 at commit 51548db.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/27627/
Test PASSed.

LGTM.  Thanks for taking care of this.


update github action docker buildx action to v2

This solves random build/push issues.
See: https://github.com/docker/build-push-action/issues/761#issuecomment-1406261692

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer (optional):

Cool! Seems this is now working.
Thanks for the follow-up @BlaineEXE.


Make "Google Maps Polling Locations" WeVoteID into a link

that takes you to the "One Polling Location" page

👍


nextTick doesn't always ensure the element is already in the DOM

Some directives can only work on elements that are already in the DOM, such as autofocus:
Vue.directive('autofocus', {
    bind() {
        Vue.nextTick(() => this.el.focus())
    }
});

However, the page component is compiled right away but it's only inserted into the DOM when it's mounted after the data and activate hooks are done. This results in nextTick running before the element is in the DOM, resulting in the element never getting focus.
Since nextTick obviously doesn't ensure that the element is in the DOM, what can be used instead?

nextTick is intended to be used right after you modified some reactive data.
For your use case, it seems more appropriate to do this:
bind () {
  this.vm.$once('hook:attached', () => this.el.focus())
}


Revert "When doing data binding over a list attribute, return an empt…

…y list or"
This reverts commit 9cf3566409ab957139fd6cff2d9b3ea850dab7d1.

This is a test to see if TC run tests and returns green status, don't worry about it.

LGTM


Restore compatibility with GHC-7 / old Cabal environments.

Some of the changes done lately make the project compile only with GHC-8, and only when there are no obsolete package-versions installed in the Cabal environment.
Here I adress these issues so IHaskell will also install on an old GHC-7.10 setup.

Thanks for this PR! Dropping 7.10 compatibility is intentional as per https://github.com/gibiansky/IHaskell/pull/716#issuecomment-300482782 and the README. I was actually planning to remove more of the <8.0 stuff because it complicates the codebase and makes adding support for future GHCs harder.
Can you tell me why you want 7.10 support in master when you can use the GHC7 tag?

Well, actually I didn't realise there's a GHC-7 tag... where does the README actually tell me about it?
The reason I want to stay in master is of course to easily keep up-to-date. Rather than switching to a legacy branch, I'd switch the compiler – I'm not overly concerned with long backwards compatibility, but I'm also not a fan of Stack's “everything in realtime” approach. GHC-7.10 isn't, like, Fortran 95 gfortran or something, it's no big deal to keep compatibility with it...

It's true that 7.10 is not that old, but I'm already running into issues with #735 because the GHC API has noticeably changed between 8.0 and 8.2. I don't see the benefit of keeping backwards compatibility when no new features have been added since the GHC7 tag (other than GHC 8 support). I can update the README to mention the tag, would that be sufficient resolution?

Ok, just the lack of support should then also be reflected in the Cabal dependencies. #748


CHORE add unittest test function  ConvertMapToValueForCreate

Adds unit tests for ConvertMapToValuesForCreate function in GORM, ensuring correct value conversion from maps to database columns for CREATE operations.

This test and the original visit_map_test.go can be moved to helper_test.go

This test and the original visit_map_test.go can be moved to helper_test.go

@a631807682 Hi
The function loadOrStoreVisitMap in the callbacks package is a private function. This means that it can only be accessed and used by code within the same package.
If you move the unit test for this function from visite_map_test.go to helper_test.go, the unit test will no longer be able to access the function because it will be in a different package.
do you want to move only convert_map_test.go first

Sorry, I didn't make it clear, I meant move to callbacks/helper_test.go .

This test and the original visit_map_test.go can be moved to helper_test.go

@a631807682 Hi
The function loadOrStoreVisitMap in the callbacks package is a private function. This means that it can only be accessed and used by code within the same package.
If you move the unit test for this function from visite_map_test.go to helper_test.go, the unit test will no longer be able to access the function because it will be in a different package.
do you want to move only convert_map_test.go first

Sorry, I didn't make it clear, I meant move to callbacks/helper_test.go .

@a631807682
Hi. i already move the test cases located in the files convert_map_test.go and visit_map_test.go into the file helper_test.go.


Provide easy way to setup cookie to response

Currently there is no easy way to add http.Cookie to response https://github.com/http-wasm/http-wasm-guest-tinygo/blob/main/handler/api/api.go#L135
of course it can be done through w.Header().Add("Set-Cookie", "a=b"). However, it would be nice to have helper function which does this out of the box (including parameters like Expires, Secure, HttpOnly). Example from go source https://cs.opensource.google/go/go/+/refs/tags/go1.21.3:src/net/http/cookie.go;l=169

actually I found pretty easy way:
	cook := &http.Cookie{
		Name:     "bar",
		Value:    "foo",
		Path:     "/",
		HttpOnly: true,
		Secure:   true,
		Domain:   req.Host,
		MaxAge:   3600 * 12,
	}
	resp.Headers().Add("Set-Cookie", cook.String())


Receiving only one HEX Code

i uploaded the code to UNO and i m getting only one hex code.
i tried Engine RPM code and i m getting RPM Values.
197,00,00,0000BE0002000000
197,00,00,0000BE0003000000
197,00,00,0000BE0004000000
197,00,00,0000BE0005000000
197,00,00,0000BE0006000000
197,00,00,0000BE0007000000
197,00,00,0000BE0008000000
197,00,00,0000BE0009000000

This is weird. Can you send some screenshot of the RPM and PID reader examples sketch output?

This is weird. Can you send some screenshot of the RPM and PID reader examples sketch output?

Sorry i forget to update. My manufacture is using PIN 8 & 9 for CAN BUS Reading. But i cant read windows up and down but i can able to see the data changes when doors are opened. Im keep on digging .


default_map uses internal names to override default values of options

click default_map uses internal names to set(override) default values
Problem
--from, internal name from_internal I cannot override default using {"from":"newvalue"}, I have to use {"from_internal": "new value"}
In my use case, the user would be overwriting the values, so it would make sense to use option names instead of internal names. Is there any workaround for this?
Example snippet
From docs
import click

CONTEXT_SETTINGS = dict(
    default_map={'runserver': {'port': 5000}}
)

@click.group(context_settings=CONTEXT_SETTINGS)
def cli():
    pass

@cli.command()
@click.option('--port', 'port_internal_name', default=8000)
def runserver(port_internal_name):
    click.echo(f"Serving on http://<IP_ADDRESS>:{port_internal_name}/")

if __name__ == '__main__':
    cli()

This doesn't override the default, for --port option
$ python test.py runserver
Serving on http://<IP_ADDRESS>:8000/

Environment:

Python version: 3.9.6
Click version: 8.0.1

An option only has one name. In this case, you named the option port_internal_name, so that's the name that Click knows to look for. An option can have multiple flags, and by default uses the name of a flag as the name of the option, but Click doesn't consider each possible flag when looking at default_map or allow_from_autoenv.

Thanks for response,
What I did, is I changed all internal names to either be the same name as the option or have the suffix _, like from_. And then I took dict from user input and added repetitive values with suffix _.
Ex:
{"from": "value"}
# turns to
{"from": "value", "from_":  "value"}

It's hacky but that's the best way I found.


Memory and performance regressions after the merge of the core typechecker branch

Sucessful build from last Friday (11/11), in the morning: https://everest-ci.paris.inria.fr/build/4139
[VERIFY] Test.Vectors.Chacha20Poly1305.fst, 1:44.01

Successful build from last Friday (11/11), later in the day: https://everest-ci.paris.inria.fr/build/4181
[VERIFY] Test.Vectors.Chacha20Poly1305.fst, 44:32.08

We are also starting to notice out-of-memory errors on the HACL build that weren't there before. A recent build OOM'd on that file above, and on my machine I see 4.8GB used for Test.Vectors.Chacha20Poly1305. As a point of comparison, when @mtzguido ran his most recent memory usage analysis, in https://github.com/FStarLang/FStar/pull/2734#issuecomment-1285586701, that file wasn't even one of the "top" 25 files for memory usage, meaning that its memory usage was below 1.6GB. So it looks like memory usage tripled for that file, and verification time exploded too.
CCing @karthikbhargavan, @R1kM and @polubelova as the HACL maintainers.

Thanks for reporting ... taking a look. It doesn't seem like that files uses tactics at all, so it's a bit surprising.

The perf regression turns out to not be related to the core checker at all.
There was a change to the way the normalizer was memoizing the reduction of the scrutinee in pattern matches that impacts performance severely in this example. Reverting that one change to the normalizer makes this example go through again in a minute or so.
Working on a patch ...

Thanks. Should Everest regressions include time and memory measurements? Guido had a nice proposal for measuring that (and post-processing the result) in #2734, which leads me to think at least the top 10 files for memory / time could be reported as part of a build.

hi @msprotz, that PR #2759 fixed the perf regression on this file. Closing this issue for now. Do re-open if you find any other perf regressions.
I agree that it would be useful to report time & memory measurements as part of CI. Maybe you can open an issue requesting that on project-everest/everest?


Make slide names "prosperity/welvaart" in households and "demand growth/groei van de vraag" consistent

The slide names: "prosperity/welvaart" in households and "demand growth/groei van de vraag" in buildings are inconsistent and IMO incorrect (demand does not always grow...). Proposal:

English: development of demand
Dutch: vraagontwikkeling

@DorinevanderVlies we picked this up in https://github.com/quintel/etmodel/pull/3939 right? Can we close this?


Cluster in Error state when attempting recover from s3 backup scenario

What kind of request is this:
bug
Steps to reproduce:
    - This test create 1 custom cluster with s3 backups enabled
        - 1 ControlPlane/worker node
        - 2 worker nodes
        - 3 etcd nodes
    - Creates an Ingress pointing to a workload
    - Snapshots the cluster and checks the backup is in S3
    - Stops the etcd nodes in ec2
    - Waits for the cluster to go into unavailable state.              *****
    - Removes all 3 etcd nodes.                                        *****
    - Creates 3 new etcd nodes and waits until the cluster             *****
      asks to restore from backup.
    - Restores from S3 backup
    - Cluster is validated after it gets in Active state.
    - Checks the Ingress created before the backup is functional after restore.

In the above scenario master-head usually fails between Waits for the cluster to go into unavailable state and Creates 3 new etcd nodes and waits until the cluster asks to restore from backup. (Lines with *****)
Result:

Other details that may be helpful:
This scenario works in v2.4.6 exact same same HA setup and custom downstream cluster.
Environment information

Rancher version: master-head (09/01/2020) c428bc9
Installation option: HA k8s

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Custom
Machine type (cloud/VM/metal) and specifications (CPU/memory): AWS t3a.medium
Kubernetes version (use kubectl version): `v1.18.6-rancher1-2

@izaac
Could you test this again on master-head?
I tried this multiple times with both HA and single node, following the steps: I am not able to reproduce the issue.
rancher: master-9addfe297070f85eb3020d0e54571adaa438ccec-head.

create custom cluster with 3 etcd nodes, 1 control and 1 worker with s3 enabled backup
create a workload and ingress
take a snapshot
stop 3 etcd nodes
wait for cluster to be in error state, saying it’s unhealthy
delete nodes from nodes page
register 3 new etcd nodes
cluster complains about stop provisioning, restore from backup
restored from backup
cluster stays in the last red error state, but cluster provisioning starts in logs
it goes through after a while and recovers
workload and ingress are present and functional

Rancher version: master-head (09/21/2020) 517b29c7cdaa58c76190340813de37c1c7c46fca
After stopping the etcd nodes the test waits polling the API for the Unavailable state but in 2.5 this state is now Error.
Adding new nodes manually and restoring from S3 backup we get the cluster back to Active as expected.


Accomplish requisite work to close out PR #11431.

Describe problem solved by the proposed pull request
This PR simplifies the diff in PR #11431, although it might produce a few merge conflicts for @catch-twenty-two to resolve (apologies).  The changes proposed in this PR include alphabetizing #includes and stubbing out method declarations.
This PR is aimed at advancing/closing out PR #11431.
Additional context
See PR #11431.

@mcsauder Can you just pull the entirety of #11431 into here so that we can merge the complete feature in one go?

@mcsauder I'd suggest that you request review from someone appropriate, otherwise I'm not sure how this should proceed.

Hi @bkueng , would you mind helping me with a review to close out this PR and 11431?  Thank you for your trained eye in review, I appreciate it.

If this doesn't break anything, let's just add it and deal with any repercussions after we discover an issue!

@dagar, this is pretty low risk, any concerns I can address?

Intermingled with this PR is #12309... The two are attempting to utilize the same functionality from different viewpoints... I am appreciative for input from anyone who wrote this code and understands it!

Intermingled with this PR is #12309... The two are attempting to utilize the same functionality from different viewpoints... I am appreciative for input from anyone who wrote this code and understands it!

Hi @mcsauder thanks for continuing to work on this. This code only runs in the PX4 simulator, the other issue seems to be on the actual hardware. So this code is never active when the firmware is loaded on an actual hardware and executed  Does that make sense?

Hi @mcsauder thanks for continuing to work on this. This code only runs in the PX4 simulator, the other issue seems to be on the actual hardware. So this code is never active when the firmware is loaded on an actual hardware platform and executed. Does that make sense?

Thanks @catch-twenty-two , I perhaps wasn't all that clear in my reference above.  I think that the intent of this PR is actually at odds with what kind of data this message is meant to carry.  It looks to me  that we should be loading an ACSII music string instead of the struct that is being proposed in this PR and was originally submitted.  I think we need to revisit this PR in that light and am closing this work for now since we lack functionality on the simulator side to receive as well.

Ah got it.  In that respect a lot more work would need to be done on the
sim side, since it was basically just playing a tone for a specified time
and not interpreting a string of characters. I was trying to get it to
mimic a bare bones buzzer as closely as possible to reflect exactly how the
px4 stack would have played it. I guess a message long would have made more
sense, when I get some time I will reopen this with the necessary changes.
On Thu, Oct 24, 2019 at 11:06 AM Mark Sauder<EMAIL_ADDRESS>wrote:

Hi @mcsauder https://github.com/mcsauder thanks for continuing to work
on this. This code only runs in the PX4 simulator, the other issue
seems to be on the actual hardware. So this code is never active when the
firmware is loaded on an actual hardware platform and executed. Does that
make sense?
Thanks @catch-twenty-two https://github.com/catch-twenty-two , I
perhaps wasn't all that clear in my reference above. I think that the
intent of this PR is actually at odds with what kind of data this message
is meant to carry. It looks to me that we should be loading an ACSII music
string instead of the struct that is being proposed in this PR and was
originally submitted. I think we need to revisit this PR in that light and
am closing this work for now since we lack functionality on the simulator
side to receive as well.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/PX4/Firmware/pull/12507?email_source=notifications&email_token=ABRHPO6QLP4J3B5VVNYGEHLQQHPZRA5CNFSM4IEWLOQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECF5PKI#issuecomment-546035625,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABRHPO6QBA7MA4G2SQVP733QQHPZRANCNFSM4IEWLOQQ
.

--
Jimmy Johnson
Field Application Engineer
Phone: (253) 242-3689
Seattle, Wa
www.auterion.com


[Blog]Doris monitoring metrics description

Doris monitoring metrics description
Proposed changes
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce to Doris?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)
[ ] Code refactor (Modify the code structure, format the code, etc...)
[ ] Optimization. Including functional usability improvements and performance improvements.
[ ] Dependency. Such as changes related to third-party components.
[ ] Other.

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[ ] I have created an issue on (Fix #ISSUE) and described the bug/feature there in detail
[ ] Compiling and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If these changes need document changes, I have updated the document
[ ] Any dependent changes have been merged

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

There will be more and more pictures saving in code repo, which is not suitable for a code repository.
I am thinking about moving docs/ to https://github.com/apache/incubator-doris-website.
But I am very sure about it.

There will be more and more pictures saving in code repo, which is not suitable for a code repository. I am thinking about moving docs/ to https://github.com/apache/incubator-doris-website.
But I am very sure about it.

OK


Is ~/.config/powermanagementprofilesrc skipped intentionally

Hi there,
Thanks again for writing this module. I'm now crafting my KDE configuration and nocited that run2nix doesn't include powermanagementprofilesrc (the one that controls power settings). Is this intentional?

Yes, it's intentional.  My reasoning is that this file is going to be very specific to the current machine.
The rc2nix tool really needs a command line option to include files that it doesn't include by default.  In that case, this issue is related to #12.

Got'ya. You mean something beyond -a (i.e. a default list)

Thanks again for your support.


Fix workspaceLocation for saveSourcecastData

Recorded sourcecast entry should be ready for preview after saving into database.
Broken due to extraction of sourcereel/sourcecast reducers from workspace reducer.

Pull Request Test Coverage Report for Build 2427

0 of 2 (0.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.03%) to 35.0%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/containers/sourcecast/SourcereelContainer.ts
0
1
0.0%

src/reducers/sourcecast.ts
0
1
0.0%

Totals

Change from base Build 2426:
-0.03%

Covered Lines:
2173

Relevant Lines:
5509

💛  - Coveralls


KnobEventHandler motion event handling broken when using log scale

If you set a knob to use a logarithmic scale, manipulating the knob value by clicking and dragging the mouse on the knob does not work correctly: The value remains on the minimum value or something very close to it. Changing the value using the mouse wheel works correctly.
Can be reproduced with the CairoUI example by inserting the following lines in the constructor:
fKnob->setRange(1.0f, 100.0f);
fKnob->setUsingLogScale(true);

thanks for the report.
it is likely a regression from the recent changes to fix integer behaviour

I just ran into this and it looks like this commit got rid of some calls to invlogscale().
Adding a matching call to invlogscale()  just above this seems to have fixed it, though I'm not familiar enough with the code to be confident that it's the Right Thing to do:
https://github.com/DISTRHO/DPF/blob/f5815166356e85a5fe244f6024c2e401f04b10fa/dgl/src/EventHandlers.cpp#L446-L450