Should-be perfect match has non-zero score

Describe the bug
When searching for a keyword in a list of objects, the search works and finds matches. However, the should-be perfect matches return a non-zero score like 2.220446049250313e-16. This should be 0 as it is a perfect match, but due to not being exactly 0, it continues the search.
The Minimal Production below gives this as its result:
0: {item: {…}, refIndex: 0, matches: Array(1), score: 2.220446049250313e-16}
1: {item: {…}, refIndex: 1, matches: Array(1), score: 0.2}
2: {item: {…}, refIndex: 2, matches: Array(1), score: 0.2}
3: {item: {…}, refIndex: 3, matches: Array(1), score: 0.2}
4: {item: {…}, refIndex: 4, matches: Array(1), score: 0.2}

Version
6.4.1
Is this a regression?
Yes, the previous version in which this bug was not present was: 3.6.1
(Im using it in another project, there it works fine)
🔬Minimal Reproduction
  const items = [
    {
      value : 'test1',
    },
    {
      value : 'test2',
    },
    {
      value : 'test3',
    },
    {
      value : 'test4',
    },
    {
      value : 'test5',
    },
  ];

  const fuse = new Fuse(items, {
    ignoreLocation : true,
    includeMatches : true,
    includeScore   : true,
    keys           : ['value'],
  });

  console.log(fuse.search('test1'));

Seeing this too, perfect matches are scoring above 1.4

The score value is 2.220446049250313e-16 for example or aka 0.0000000000000002
So a work around would be to iterate over the results and force it to 2 decimal spaces (or more as needed)
fuse.search('test2').forEach((it) => it.score = Number(it.score.toFixed(2)));

fuse.search('test2').forEach((it) => it.score = Number(it.score.toFixed(2)));

I've used that workaround too, although I would recommend using Math.round((score * 100) / 100) as its much slower to use toFixed() and then casting to `Number. Especially if there are thousands of records, it would slow it down significantly.

Bump


 Thank you for creating such a wonderful module! I have an issue. I run a call of cthulhu game and there are some big scenes that I use as maps (for example a map of old Boston). However, I can't zoom out fully out of those maps. I will include the boston map here (I use 1562x2175рх JPEG one). Could you please take a look at it?
I am running v11 315. This also happens with D&D 5e 3.1.2

Have you configured the Zoom/Pan Options settings to increase the minimum and maximum zoom overrides?

Try decreasing the Minimum further (and tell me which numbers they both are at).

Hey, thanks for the suggesion!  I had it at 0,3333333333333333, but set it to 0.1 and it is now enough. Thank you, that fixes it for me

I admit I made the same mistake too, more than once 🗡
I should probably improve those descriptions.


Non-Zero Return Code for failures

At present the utility will always return a zero return code regardless of whether errors were thrown or not. This results in a successful pipeline run on CI systems running a sync job despite errors being thrown.
Ideally failures and exceptions should result in a non-zero return code.

The utility already returned exit code 1 if there was a major error, for example when the utility is unable to connect to the source system. Potentially transient errors, for example if an error occurs while processing a single vulnerability, are logged but the utility continues processing other vulnerabilities. The next release of the utility will now return exit code 2 on such potentially transient errors.

https://github.com/fortify-ps/FortifyBugTrackerUtility/releases/tag/4.3


Feature request: export api interfaces

It might be good if all api responses be exported, so i can cache them in my application and do not call kick api, specially noticed they are not exported on getCurrentUser.
I'm familiar to do PR if you wan't to.

Absolutely agree, I was just too lazy to setup the exports originally. I committed some changes last night to assist with this.
I have setup barrel files and I'm just exporting everything currently. I'm not that familiar with setting up exports for a library so I'm not sure is there is a better way to achieve this. I'll just need to publish to npm if it looks good, I can do so after work today, looking at about ~12 hours away, unless I get time this morning.

Ok, thanks.
And thanks for your library, i found it pretty useful for myself.

Found some time this morning, published v1.0.1-8 to NPM.


Clarify installation instructions

This pull request aims to solve R2Northstar/Northstar/#2 by giving more detail on the install location.
It's worth mentioning I wasn't able to find anything on opening a game's local files in Origin, so that part has been removed. Please do correct this if I'm wrong.

Awesome, thanks <3


Support for Nextcloud

For the people who want to use cloud like storage without the privacy issues of a public cloud, could support be added for clouds like nextcloud.

You don't need KeeAnywhere to access a .kdbx file stored on Nextcloud, the storage is accessible with HTTPS. Just open them the file with "open url". The URL should look like this:
https://1234.example.com/remote.php/webdav/example.kdbx

@craige1 What @Discostu36 writes is correct. So closing this request.

Added clarification to the FAQ-Section of the Homepage:
https://keeanywhere.de/use/faq

It would still be nice to have webDAV support because KeePass does not support Database-Caching (as far as I know) but keeanywhere does.


(HC-94) Unpin the hocon gem version

Prior to this commit, the version of the hocon gem for this module
was pinned to 0.9.3. There have been several new releases since then,
but since the version is pinned in the Gemfile the module is still
using an old release of the gem.
The version was originally pinned to avoid breaking the vsphere
and azure modules, but both modules now require hocon version 1.0.0+
so it is no longer neccesary for the module to continue using an
older version.

Oops this is failing in Travis, looks like there may be some work to be done around beaker versions. I'll take a look

~> 1.2.0 will pin to anything 1.2.x; using ~> 1.2 will pin to anything 1.x
with x > 2; I usually recomment the latter for less churn, if you only want
to test against latest.
On 27 October 2016 at 15:22, Chris Price<EMAIL_ADDRESS>wrote:

@cprice404 commented on this pull request.
In Gemfile https://github.com/puppetlabs/puppetlabs-hocon/pull/40:

@@ -27,6 +27,6 @@ else
gem 'puppet', :require => false
end

-gem 'hocon', '~> 0.9.3',       :require => false
We should have pretty much full control over the ruby hocon gem/API, and
we have been following semver pretty carefully.
My vote would probably be to just go with ~>1.2.0 and not worry about
multiple versions until we have a concrete use case. But if it's
easy/desirable to introduce the matrix now, that's fine too. I would love
to have 1.2.0 covered in tests (it should be released any minute now -
@jpinsonault https://github.com/jpinsonault has just been working on
the kinks on a CI release job for it).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/puppetlabs/puppetlabs-hocon/pull/40, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AABsQLGCJVbkPuC6Fx2aplhJ2lRwCNBdks5q4LO9gaJpZM4Kf8Mm
.

Alright, thanks for the input everyone! This now has been dealt with in PR #42 which added puppetlabs-hocon to modulesync. Since it's now modulesync'd, it will get periodic updates to things like gem versions and configurations so hopefully this should minimizes issues in the future.
There was no 1.2 version of the hocon gem yet, so I pinned it to ~> 1.1. We can update it when the new version is out.


Test cleanup per code review

Description
Per comments in #3216, I went ahead an updated this test a well to be consistent.

LGTM


Reposense config.json

Everyone update their author name accordingly.

Pull Request Test Coverage Report for Build 128

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

Totals

Change from base Build 123:
0.0%

Covered Lines:
1988

Relevant Lines:
2412

💛  - Coveralls


ImageUpdateAutomation enhancements with v1beta2 API

Similar to other Flux controllers, image-automation-controller is undergoing refactoring. The refactor includes overall code organization changes and design enhancements. This issue discusses the enhancements and API changes.
Update ResultV2
In order to address https://github.com/fluxcd/image-automation-controller/issues/437 (inclusion of previous and new value in the update result), the update Result data structure needs to be changed. The current structure is based on file -> objects -> images. This only accounts for updates that involve the full image (name+tag) updates. Partial image updates (name or tag) are not recorded in the result. In order to provide complete details about what was updated, we need to record the complete change regardless of image reference.
A new ResultV2 can be introduced to capture all the kinds of updates and the previous value with the structure file -> objects -> changes. A change constitutes the old value, the new value and the setter responsible for the update. This can be used to construct commit messages like the following with old and new values:
Automation: default/test-update-auto

- File: foo-deployment.yaml
  - Object: Deployment/default/foo
    Changes:
    - 2.2.2 -> 5.0.3

- File: podinfo-deployment.yaml
  - Object: Deployment/default/infopod
    Changes:
    - v1.0 -> 5.0.3
  - Object: Deployment/default/podinfo
    Changes:
    - ghcr.io/stefanprodan/podinfo:4.0.6 -> ghcr.io/stefanprodan/podinfo:5.0.3
    - bar -> ghcr.io/stefanprodan/podinfo
    - 4.0.6 -> 5.0.3

In order to keep the current commit templates working as before, TemplateData will be extended by introducing the new field for file change based data.
type TemplateData struct {
        AutomationObject types.NamespacedName
        Updated          update.Result
        Changed          update.ResultV2
}

The new result will be an opt-in feature.
See https://github.com/fluxcd/image-automation-controller/pull/642 for the implementation.
ImagePolicy selector support
Currently, all the ImagePolicies present in a namespace are considered when performing an update. Based on a lot of user feedback, policy selectors will be introduced will allow selecting image policies based on their labels via .spec.policySelector field in ImageUpdateAutomation. An implementation of this exists in https://github.com/fluxcd/image-automation-controller/pull/619. Along with this, the selected image policies will also be recorded in the status of ImageUpdateAutomation object with their latest images. This will help evaluate and reason about the result of an update, enhancing troubleshooting experience.
apiVersion: image.fluxcd.io/v1beta2
kind: ImageUpdateAutomation
metadata:
  name: update-app
spec:
  policySelector:
    matchLabels:
      app.kubernetes.io/component: foo
      app.kubernetes.io/instance: bar
  ...
status:
  observedPolicies:
  - name: policyA
    latestImage: foo/bar1:v1.0
  - name: policyB
    latestImage: foo/bar2:v1.5
  ...

short-circuit reconciliations
When nothing has changed (git repository commits and the image policies latest images), the reconciliations can be returned early, avoiding full reconciliations. If the latest images of the ImagePolicies have not changed and the remote git repository has no new commit, the full reconciliation operation can be skipped. This will require recording the ImagePolicies and their latest images observed in the last reconciliation, which is described above. And also recording the last observed commit in the git repository. We use similar technique in source-controller to avoid rebuilding the artifact if there's no new commit in the git repository. These can be stored in the status of the ImageUpdateAutomation, .status.observedPolicies and .status.observedLastCommit.
During a reconciliation, git repository can be checked for new commit and the image policies can be checked for new latest images before performing the full reconciliation.
TODO:

[ ] Introduce ResultV2
[ ] Introduce policy selector and observed policies
[ ] short-circuit reconciliations with observed last commit and observed image policies

If the update includes a digest, it'll be recorded just as a string.

Awesome, so we are all covered here.

it would be better to store the image policy result in ImageUpdateAutomation status in the format defined ImageRef

Yes let's do this!


Espresso SDK (poc)

Open points:

Environment variable handling needs to be adapted to Android best practices
Builder classes where appropriate (VisualClient, VisualCheckOptions, BuildAttributes etc.)
Use default Android http client instead of Apache's

A lot of the code here looks similar-ish to the Java client. Can none of that be imported and used here as a dependency somehow?

A lot of the code here looks similar-ish to the Java client. Can none of that be imported and used here as a dependency somehow?

@omacranger That would be super convenient however it brings also some problems that complicates the implementation. Importing Java client brings transitive dependencies that are not compatible with Android environment, considering the target Android API (apache httpclient, graphql-java etc.). Those dependencies need to be excluded explicitly and need to be maintained for the future versions of java client if new ones show up. Also, since we are using the same package and class names for certain classes that need reimplementation (mainly VisualAPI and GraphQLClient), class/method loading problems arise in runtime. Instead of trying to fix those problems, I'd rather keep the implementations fully separate.


Implement migration class for migrating from 8.0.0 to 8.1.0

https://github.com/microbiomedata/nmdc-schema/releases/tag/v8.1.0 was released a few weeks ago.
There is no corresponding migration class in https://github.com/microbiomedata/nmdc-schema/blob/main/nmdc_schema/migration_recursion.py
This ticket represents the task of implementing one (it may be a noop).
CC: @turbomam , @pkalita-lbl, @Shalsh23

@turbomam already implemented the migration class (my bad—I didn't check before opening this ticket):
https://github.com/microbiomedata/nmdc-schema/blob/382c7081a2f1db302da3a0ea6fbaac6f0dedfc78/nmdc_schema/migration_recursion.py#L269-L283
I'll just update the class name to reflect the target schema version, then open a PR.
- Migrator_from_8_0_0_to_research_study_study_category
+ Migrator_from_8_0_0_to_8_1_0


Uncaught Exception: badCredentials

I'm trying to use the api (thank you) and I'm always getting an uncaught exception.
const degiro = new DeGiro.default.create({
username: args[0],
pwd: args[1],
oneTimePassword: args[2]
})
const accountData = await degiro.login()
I've verified the arguments multiple times. Is there something I'm doing wrong?
Output with debug on:
node:internal/process/esm_loader:34       internalBinding('errors').triggerUncaughtException(                                 ^ badCredentials (Use node --trace-uncaught ...` to show where the exception was thrown)
Node.js v21.2.0
Making request to https://trader.degiro.nl/login/secure/login with options:
{
"method": "POST",
"body": "{"isPassCodeReset":false,"isRedirectToMobile":false,"password":"XXXXX","username":"XXXXX","oneTimePassword":"XXXXX","queryParams":{"reason":"session_expired"}}",
"headers": {
"Content-Type": "application/json"
},
"credentials": "include",
"referer": "https://trader.degiro.nl/trader/"
}
Sending OTP`

I don't know exactly what error I currently have when passing arguments, but it worked when passing them manually.


deisctl start platform takes very long time to complete

As per the installation instructions, I ran deisctl start platform to start deis on a set of vagrant machines. For me, the command takes around 20 minutes to complete. I thought this might just be the first time due to downloading dependencies but it seemed to take even longer the next time.

thats normal builde is huge / the cloudinit has a preseed command which helps to speed stuff up .. run that on every node .. and you see a huge speed improvement

When the units are started, they have to pull the image which can take some time. Builder has some images that it depends upon, so it needs to pull those during boot in order to accept pushes for the first time. As @PierreKircher mentioned there is a pre-seed script that you can run on each host, but again it will take some time to complete.
We are continuing to make the images as small as possible (we've probably hit the limit by now). Short of shipping our own CoreOS images with the components pre-seeded on each host (#1153) there's not much else we can do at this point. If you have any ideas we are always welcome for input!

If you have any ideas we are always welcome for input!

If that's just as long as it takes that's fine. I was just concerned that I might have had something mis-configured which caused it to take longer than it should. One thing I'm still not clear on though is how much of this you have to redo when you restart the host machine. Would the preseed help in a vagrant setting?

One thing I'm still not clear on though is how much of this you have to redo when you restart the host machine.

Since the host will leave the cluster, it will begin by re-scheduling the units to other hosts. You shouldn't have to re-do anything.

Would the preseed help in a vagrant setting?

I guess that depends on how fast your internet is at your office and if you're willing to pull every component on every host.

Let's add something to the documentation and / or deisctl start platform itself that makes it more clear that this is a time-consuming operation.

I'm looking into running the Docker image building in parallel during builder's boot. Are there any known issues with trying to do that?

As long as the builder isn't accepting git pushes at that time, that should be fine. Obviously the builder needs these images to be available to run the build process for non-Dockerfile builds.

There isn't much really to be done about the startup time overall, especially now that Deis is required to serialize all the docker pull operations on a host. I'm closing this, but see #3568.


Urls use absolute paths, should use relative ones

I have this project deployed at http://.....com/test/
The project doesn't work because the links use absolute paths, not relative ones (It tries pulling files, say "angular.js", from http://...com/angular.js instead of http://.....com/test/angular.js)
I got it to "work" by modifing this line in the gulpfile.js
arguments[0] = filepath.replace('/' + PATH.dest[env].all, '') + v;
with
arguments[0] = filepath.replace('/' + PATH.dest[env].all, './') + v; (Notice the "./")
It created some weird but tolerable side effects, but after updating the project to master, those lines were changed and the fix no longer works!
Any ideas on how to fix this?

Thanks for pointing this out! I'll take a look at this issue today

Everytime you refresh the page now, it adds an extra "/" to the url. So after 5 refreshes, the url looks like this:
http://.....com/test//////


[SPARK-26316][BRANCH-2.4] Revert hash join metrics in spark 21052 that causes performance degradation

What changes were proposed in this pull request?
revert spark 21052 in spark 2.4 because of the discussion in PR23269
How was this patch tested?
N/A

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

ok to test

Can you fix the PR title to [SPARK-26316][BRANCH-2.4] Revert hash join metrics in spark 21052 that causes performance degradation?

@HyukjinKwon ok. Fixed.

Test build #100128 has started for PR 23318 at commit ca4ae0e.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/6112/
Test PASSed.

Test build #100128 has finished for PR 23318 at commit ca4ae0e.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #100134 has started for PR 23318 at commit 45e16a9.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/6118/
Test PASSed.

Test build #100134 has finished for PR 23318 at commit 45e16a9.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Retest this please.

Test build #100166 has started for PR 23318 at commit 45e16a9.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/6145/
Test PASSed.

Test build #100166 has finished for PR 23318 at commit 45e16a9.

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

Merged build finished. Test PASSed.

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

cc @viirya


Technical Spike: IPFS Integration

The application has to be integrated with IPFS. For this reason, we can try to implement a simple integration with IPFS.
HOW IPFS WORKS
decentralized file storage on Polkadot
Research
There are already solutions that have integrated Substrate with IPFS such as:

https://rs-ipfs.github.io/offchain-ipfs-manual/building-an-offchain-ipfs-app.html
https://wiki.crust.network/docs/en/build101  (Polkadot is using CRUST for its IPFS storage) https://github.com/crustio/crust-demo/tree/main/store-file

[ ] Evaluate best option for IPFS integration
[ ] Create a small technical spike: Store the Vision document in IPFS and store the actual hash

Budget: $40

Documentation on IPFS: https://github.com/ipfs-shipyard/ipfs-primer

We have IPFS node running in a docker container.
For instance you can get its peers: curl -X POST http://<IP_ADDRESS>:5001/api/v0/swarm/peers
We will integrate IPFS-HTTP-JS_CLIENT library into our front-end.
When posting data to our node, we will only post the cid HASH information, so the node doesn't need to be tightly coupled to IPFS. We only might have to check for a valid Hash.


Add array detection in getHeaderValue function

Warning can appear otherwise...

:+1:

:+1:
Must increment fix digit in version number


refactor: Remove not needed condition

Form data can't be None at this point

Codecov Report

Merging #936 (4668737) into master (f510a39) will decrease coverage by 0.04%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #936      +/-   ##
==========================================
- Coverage   99.66%   99.61%   -0.05%
==========================================
  Files          66       66
  Lines        4457     4455       -2
  Branches      733      732       -1
==========================================
- Hits         4442     4438       -4
- Misses          5        6       +1
- Partials       10       11       +1

Flag
Coverage Δ

unittests
99.61% <100.00%> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/schemathesis/models.py
99.53% <100.00%> (+0.46%)
:arrow_up:

src/schemathesis/extra/pytest_plugin.py
97.64% <0.00%> (-2.36%)
:arrow_down:

src/schemathesis/cli/callbacks.py
98.19% <0.00%> (-1.81%)
:arrow_down:

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 f510a39...4668737. Read the comment docs.


stderr is not displayed

If a command outputs something to stderr, it's not visible in the build log, for example:
time sleep 1

As a workaround:
time sleep 1 2>&1

seems to be fixed now


Incorrect method parameter color for Java

How it looks in IntelliJ:

How it looks in GitHub:

Thank you for reaching out @napsterv  but I am also trying to keep better contrast so it is easily / nicely visible to devs.
So, not sure what actually looks on GitHub is good, feel free to reopen issue or comment out if you want to say something via comment.


RequireJS in the title is misleading.

RequireJS in the title is misleading ( confused with RequireJS ). It should be just require.ensure

👍


sync with upstream

Description

Motivation and context

How has this been tested?

Screenshots (if appropriate):
Types of changes

✅ Maintenance (change which doesn't modify functionality, but provides dependency updates or tooling improvements)
✅ Bug fix (non-breaking change which fixes an issue)
✅ New feature (non-breaking change which adds functionality)
✅ Refactor (non-breaking change which doesn't change functionality)
✅ Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

✅ My code follows the code style of this project. [REQUIRED]
✅ All new and existing tests passed. [REQUIRED]
✅ My change requires a change to the documentation and I have updated it accordingly.
✅ I have added tests to cover my changes.

Closed this PR in favor of https://github.com/rifflearning/jitsi-meet/pull/132


[camera] Add macOS support

Since laptops commonly have cameras built in, this would be potentially useful.
~Blocked on #30717~

Any idea when this will be implemented?

I was looking for an indication as to when this would be prioritized. Is this on the roadmap yet?

No; see https://github.com/flutter/flutter/wiki/Issue-hygiene#when-will-my-bug-be-fixed

If the issue is labeled P5 or P6, we are not currently expecting to ever work on it

Since it was labeled P5 it seems that it won’t be worked on. Is there a different plan for desktop cameras?

I'm so need it. Please 🙏

This should have been implemented with flutter 3.0 since that release marked the stable support of desktops

Am I to assume that there is no way I can access a macbook's web cam and microphone in my Flutter app?

Platform channels are available on macOS, so you access arbitrary native code on macOS just as you can on other platforms. This issue is about the camera plugin, not what is generally possible with respect to camera access.

I have a Flutter app that uses Agora video calling and it works perfectly fine on the iPad. But my employer needs a macOs app and for the life of me I cant find any way to access Macbook's web cam or microphone. Am I to assume that there is no way I can access a macbook's web cam and microphone in my Flutter app?

have you found any solution for this? i am also struggling to request permissions from flutter macos.

me, too, Macos won't allow the camera access, any idea? can someone help? it is a flag issue.

Any update for Camera package rather than working with Platform Channels?

any update?

https://github.com/stuartmorgan/packages/tree/macos-camera has some initial exploration; it compiles now, but doesn't actually work yet (the preview is blank, and taking a picture results in an NSError, so there are likely capture configuration issues).

I would also love to see MacOS support for the camera plugin.
The use of cameras is common across devices. In addition, it would also speed up development targetting ios/android/etc. by being able to run this functionality directly for the macos platform.


Question regarding robot experiments

Hi @arsalan-mousavian, and thanks for making the code public!
I have a simple question regarding the robot experiments (as shown in the videos). I am trying to use some of the grasps generated by this approach to grasp some simple objects off a table with our Franka arm, and I' m wondering how you guys implemented the finger movement in the grasp evaluation you have shown. According to my experience, the Franka library only exposes a grasp command (which tends to squish soft objects). In your videos, however, the force applied during the grasp does not seem to be very large (e.g. it does not squish the boxes or the mustard bottle). Did you guys develop a custom force controller for the fingers, or did you just use whatever comes with libfranka and franka_ros?
Thanks in advance!

Hi @fbottarel, we don't have any force controller but would really like to have one. So if you develop force controller for franka please share it publicly. I think it's going to be very useful.
At the time, we prompted the user for entering the force before moving the robot. for boxes we used 40N and for Mustard we used 70N. These days we just set the force to 70N for all the objects. It's not a perfect solution but it's better than asking the user to enter the amount of force.

Thank you @arsalan-mousavian for the swift response. Unfortunately, the libfranka API does not allow for direct control of the gripper fingers in terms of force/torque, there are only "non-realtime" commands very similar to how ROS actions work. For this specific purpose, in the lab I'm working at we are looking forward to switch out the Franka hand for a gripper that allows for that sort of thing.
On a side note: is a 40N/70N sufficient to grab boxes without squishing them? It seems quite large to me!


[RFC]: Store Org's all Pull Requests in Real Dev Squad Backend Database and Webhook Integration

[RFC]: Store Org's all Pull Requests in Real Dev Squad Backend Database and Webhook Integration
Feature Name: Store Org's all Pull Requests in Real Dev Squad Backend Database and Webhook Integration
Summary
This RFC proposes a solution to store all pull requests from the Real Dev Squad organization in the Real Dev Squad backend database. It also suggests integrating a webhook to receive real-time updates from GitHub and keep the backend database synchronized.
Motivation
The purpose of this RFC is to outline a solution for storing Real Dev Squad's GitHub pull requests in the Real Dev Squad backend database. By integrating a webhook, the backend database can be updated in real-time, ensuring data consistency and providing a streamlined workflow.
Detailed design
1. Introduction
This RFC proposes storing the GitHub pull requests of the Real Dev Squad organization in the Real Dev Squad backend database. It also suggests using a webhook to retrieve the latest data from GitHub and keep the backend database updated in real-time.
2. Background
Real Dev Squad uses GitHub for source code management and collaboration. The Real Dev Squad backend database serves as a central repository for various organization data. To streamline workflows and maintain data consistency, it is essential to synchronize pull request information from GitHub into the backend database.
3. Objectives
The objectives of this RFC are as follows:

Store pull request data in the backend database: Extract relevant information from GitHub pull requests and store it in the backend database.
Real-time updates: Implement a webhook to receive notifications from GitHub for pull request creation, updates, and closures, enabling real-time updates in the backend database.
Data integrity: Ensure stored pull request data is accurate, up-to-date, and consistent with corresponding pull requests in GitHub.

4. Proposed Solution
4.1. Database Schema
Design an appropriate database schema to store pull request data in the backend database. The schema should include fields such as pull request ID, title, description, author, creation timestamp, last update timestamp, status (open/closed), and other relevant information.
4.2. API Endpoint
Create an API endpoint in the Real Dev Squad backend to handle incoming requests for storing pull request data. The endpoint should process received data and persist it in the backend database.
4.3. Webhook Integration
Integrate a webhook mechanism with GitHub to receive event notifications related to pull requests. Configure the webhook to send notifications to the designated endpoint in the backend whenever a pull request is created, updated, or closed.
4.4. Event Processing
Upon receiving a webhook notification, the backend should authenticate the request, extract relevant data associated with the pull request, and process it. The processed data should be stored or used to update the corresponding record in the backend database.
4.5. Error Handling
Implement appropriate error handling mechanisms to address cases where webhook notifications fail to be processed or stored in the backend database. This may include logging, error notifications, and retry mechanisms to maintain data consistency.
5. Security Considerations
Ensure the API endpoint and webhook integration are secured using appropriate authentication mechanisms (e.g., OAuth or API keys) to prevent unauthorized access and data tampering.
6. Future Enhancements
In the future, consider additional features to enhance the pull request integration, such as implementing a two-way synchronization to update pull request status in GitHub when modified in the backend database.
Drawbacks
Drawbacks of the proposed design are:

Additional configuration and maintenance requirements for the webhook integration.
The need for additional security measures to protect the API endpoint from unauthorized access and data tampering.
Potential requirement for additional resources to implement and maintain the solution.

Unresolved questions

[ ] Name of the API endpoint to be created in the backend. For example - /pull-requests.
[ ] GitHub API endpoint to be used for retrieving pull request data.
[ ] Database schema for storing pull request data in the backend database.
[ ] How will the API endpoint process incoming requests and store pull request data in the backend database?
[ ] How will the API endpoint handle errors and ensure data consistency?
[ ] How will the webhook be configured to receive notifications from GitHub?
[ ] How will the backend authenticate webhook requests?
[ ] How will the backend process webhook notifications and store pull request data in the backend database?
[ ] What security measures will be implemented to protect the API endpoint from unauthorized access and data tampering?
[ ] Does API have GET, POST, PUT, DELETE methods?

Conclusion
This RFC proposes storing Real Dev Squad's GitHub pull requests in the Real Dev Squad backend database through webhook integration. The solution allows for real-time updates and ensures data consistency. Additional configuration and maintenance efforts may be required for the webhook integration and API endpoint. Security measures must be implemented to protect against unauthorized access and data tampering. Alternatives considered include periodic data storage using scheduled jobs, which do not provide real-time updates.

[
  {
    "url": "https://api.github.com/repos/Real-Dev-Squad/website-status/pulls/576",
    "id":<PHONE_NUMBER>,
    "node_id": "PR_kwDOEQJXR85Q9A8T",
    "html_url": "https://github.com/Real-Dev-Squad/website-status/pull/576",
    "diff_url": "https://github.com/Real-Dev-Squad/website-status/pull/576.diff",
    "patch_url": "https://github.com/Real-Dev-Squad/website-status/pull/576.patch",
    "issue_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/issues/576",
    "number": 576,
    "state": "closed",
    "locked": false,
    "title": "Create pull_request_template.md",
    "user": {
      "login": "bhtibrewal",
      "id": 42600164,
      "node_id": "MDQ6VXNlcjQyNjAwMTY0",
      "avatar_url": "https://avatars.githubusercontent.com/u/42600164?v=4",
      "gravatar_id": "",
      "url": "https://api.github.com/users/bhtibrewal",
      "html_url": "https://github.com/bhtibrewal",
      "followers_url": "https://api.github.com/users/bhtibrewal/followers",
      "following_url": "https://api.github.com/users/bhtibrewal/following{/other_user}",
      "gists_url": "https://api.github.com/users/bhtibrewal/gists{/gist_id}",
      "starred_url": "https://api.github.com/users/bhtibrewal/starred{/owner}{/repo}",
      "subscriptions_url": "https://api.github.com/users/bhtibrewal/subscriptions",
      "organizations_url": "https://api.github.com/users/bhtibrewal/orgs",
      "repos_url": "https://api.github.com/users/bhtibrewal/repos",
      "events_url": "https://api.github.com/users/bhtibrewal/events{/privacy}",
      "received_events_url": "https://api.github.com/users/bhtibrewal/received_events",
      "type": "User",
      "site_admin": false
    },
    "body": "Issue: #577\r\nadded a template to standardize PRs",
    "created_at": "2023-05-21T10:13:57Z",
    "updated_at": "2023-05-25T16:44:26Z",
    "closed_at": "2023-05-25T16:44:25Z",
    "merged_at": "2023-05-25T16:44:25Z",
    "merge_commit_sha": "4dad25f6558e00cccb12e140b2bb70620095f890",
    "assignee": {
      // Same as user
    },
    "assignees": [
      // Same as user but in array
    ],
    "requested_reviewers": [],
    "requested_teams": [],
    "labels": [],
    "milestone": null,
    "draft": false,
    "commits_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/pulls/576/commits",
    "review_comments_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/pulls/576/comments",
    "review_comment_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/pulls/comments{/number}",
    "comments_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/issues/576/comments",
    "statuses_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/statuses/087cf71ba3b38237a3e5217a9ab3816a871f3849",
    "head": {
      "label": "Real-Dev-Squad:make-pull_request_template",
      "ref": "make-pull_request_template",
      "sha": "087cf71ba3b38237a3e5217a9ab3816a871f3849",
      "user": {
        // Same as user
      },
      "repo": {
        "id": 285366087,
        "node_id": "MDEwOlJlcG9zaXRvcnkyODUzNjYwODc=",
        "name": "website-status",
        "full_name": "Real-Dev-Squad/website-status",
        "private": false,
        "owner": {
          // Same as user
        },
        "html_url": "https://github.com/Real-Dev-Squad/website-status",
        "description": "Shows a roadmap of the ongoing projects being done",
        "fork": false,
        "url": "https://api.github.com/repos/Real-Dev-Squad/website-status",
        "forks_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/forks",
        "keys_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/keys{/key_id}",
        "collaborators_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/collaborators{/collaborator}",
        "teams_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/teams",
        "hooks_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/hooks",
        "issue_events_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/issues/events{/number}",
        "events_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/events",
        "assignees_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/assignees{/user}",
        "branches_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/branches{/branch}",
        "tags_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/tags",
        "blobs_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/git/blobs{/sha}",
        "git_tags_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/git/tags{/sha}",
        "git_refs_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/git/refs{/sha}",
        "trees_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/git/trees{/sha}",
        "statuses_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/statuses/{sha}",
        "languages_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/languages",
        "stargazers_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/stargazers",
        "contributors_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/contributors",
        "subscribers_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/subscribers",
        "subscription_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/subscription",
        "commits_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/commits{/sha}",
        "git_commits_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/git/commits{/sha}",
        "comments_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/comments{/number}",
        "issue_comment_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/issues/comments{/number}",
        "contents_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/contents/{+path}",
        "compare_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/compare/{base}...{head}",
        "merges_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/merges",
        "archive_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/{archive_format}{/ref}",
        "downloads_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/downloads",
        "issues_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/issues{/number}",
        "pulls_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/pulls{/number}",
        "milestones_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/milestones{/number}",
        "notifications_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/notifications{?since,all,participating}",
        "labels_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/labels{/name}",
        "releases_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/releases{/id}",
        "deployments_url": "https://api.github.com/repos/Real-Dev-Squad/website-status/deployments",
        "created_at": "2020-08-05T17:58:40Z",
        "updated_at": "2023-05-08T10:34:54Z",
        "pushed_at": "2023-05-25T17:21:30Z",
        "git_url": "git://github.com/Real-Dev-Squad/website-status.git",
        "ssh_url": "git@github.com:Real-Dev-Squad/website-status.git",
        "clone_url": "https://github.com/Real-Dev-Squad/website-status.git",
        "svn_url": "https://github.com/Real-Dev-Squad/website-status",
        "homepage": "https://status.realdevsquad.com/",
        "size": 5138,
        "stargazers_count": 15,
        "watchers_count": 15,
        "language": "TypeScript",
        "has_issues": true,
        "has_projects": true,
        "has_downloads": true,
        "has_wiki": true,
        "has_pages": false,
        "has_discussions": false,
        "forks_count": 108,
        "mirror_url": null,
        "archived": false,
        "disabled": false,
        "open_issues_count": 137,
        "license": {
          "key": "mit",
          "name": "MIT License",
          "spdx_id": "MIT",
          "url": "https://api.github.com/licenses/mit",
          "node_id": "MDc6TGljZW5zZTEz"
        },
        "allow_forking": true,
        "is_template": false,
        "web_commit_signoff_required": false,
        "topics": ["hacktoberfest", "react", "typescript"],
        "visibility": "public",
        "forks": 108,
        "open_issues": 137,
        "watchers": 15,
        "default_branch": "develop"
      }
    },
    "base": {
      // Same as above head object
    },
    "_links": {
      "self": {
        "href": "https://api.github.com/repos/Real-Dev-Squad/website-status/pulls/576"
      },
      "html": {
        "href": "https://github.com/Real-Dev-Squad/website-status/pull/576"
      },
      "issue": {
        "href": "https://api.github.com/repos/Real-Dev-Squad/website-status/issues/576"
      },
      "comments": {
        "href": "https://api.github.com/repos/Real-Dev-Squad/website-status/issues/576/comments"
      },
      "review_comments": {
        "href": "https://api.github.com/repos/Real-Dev-Squad/website-status/pulls/576/comments"
      },
      "review_comment": {
        "href": "https://api.github.com/repos/Real-Dev-Squad/website-status/pulls/comments{/number}"
      },
      "commits": {
        "href": "https://api.github.com/repos/Real-Dev-Squad/website-status/pulls/576/commits"
      },
      "statuses": {
        "href": "https://api.github.com/repos/Real-Dev-Squad/website-status/statuses/087cf71ba3b38237a3e5217a9ab3816a871f3849"
      }
    },
    "author_association": "CONTRIBUTOR",
    "auto_merge": null,
    "active_lock_reason": null
  }
]

Field which are required in the PR

[x] url - URL of the PR in the browser
[ ] id - ID of the PR it is unique for every PR
[ ] node_id - Node ID of the PR it is unique for every PR
[x] html_url - URL of the PR in the browser
[ ] diff_url - Used to get the diff of the PR
[ ] patch_url - Used to get the patch of the PR
[x] issue_url - URL of the issue in the browser
[x] number - Number of the PR it is unique for every PR
[x] state - State of the PR like open or closed
[ ] locked - If the PR is locked or not
[x] title - Title of the PR

PR user

[x] login - Username of the user
[x] id - ID of the user it is unique for every user
[ ] node_id - Node ID of the user it is unique for every user
[x] avatar_url - URL of the user's avatar
[ ] gravatar_id - Gravatar ID of the user
[x] url - URL of the user(API)
[x] html_url - URL of the user in the browser
[ ] followers_url - URL of the user's followers(API)
[ ] following_url - URL of the user's following(API)
[ ] gists_url - URL of the user's gists(API)
[ ] starred_url - URL of the user's starred gists(API)
[ ] subscriptions_url - URL of the user's subscriptions(API)
[ ] organizations_url - URL of the user's organizations(API)
[ ] repos_url - URL of the user's repos(API)
[ ] events_url - URL of the user's events(API)
[ ] received_events_url - URL of the user's received events(API)
[ ] type - Type of the user like User or Organization
[ ] site_admin - If the user is site admin or not

Continue to PR

[x] body - Body of the PR
[x] created_at - Date and time when the PR was created
[x] updated_at - Date and time when the PR was updated
[x] closed_at - Date and time when the PR was closed
[x] merged_at - Date and time when the PR was merged
[ ] merge_commit_sha - SHA of the merge commit

PR Assignee
Same as PR user
PR Assignees - Array
Same as PR Assignee but in array
Continue to PR

[ ] requested_reviewers - Array of the requested reviewers
[ ] requested_teams - Array of the requested teams
[x] labels - Array of the labels
[ ] milestone - Milestone of the PR
[x] draft - If the PR is draft or not
[ ] commits_url - URL of the commits(API)
[ ] review_comments_url - URL of the review comments(API)
[ ] review_comment_url - URL of the review comment(API)
[ ] comments_url - URL of the comments(API)
[ ] statuses_url - URL of the statuses(API)

PR Head

[x] label - Label of the head
[x] ref - Ref of the head
[ ] sha - SHA of the head
[ ] USER - User of the head

PR Head User
Same as PR user
PR Head Repo

[ ] id - ID of the head repo it is unique for every head repo
[ ] node_id - Node ID of the head repo it is unique for every head repo
[x] name - Name of the head repo
[x] full_name - Full name of the head repo
[x] private - If the head repo is private or not

PR Head Repo Owner
Same as PR user and PR head user
Continue to PR Head Repo

[x] html_url - URL of the head repo in the browser
[x] description - Description of the head repo
[ ] fork - If the head repo is fork or not
[ ] url - URL of the head repo(API)
[ ] forks_url - URL of the head repo's forks(API)
[ ] keys_url - URL of the head repo's keys(API)
[ ] collaborators_url - URL of the head repo's collaborators(API)
[ ] teams_url - URL of the head repo's teams(API)
[ ] hooks_url - URL of the head repo's hooks(API)
[ ] issue_events_url - URL of the head repo's issue events(API)
[ ] events_url - URL of the head repo's events(API)
[ ] assignees_url - URL of the head repo's assignees(API)
[ ] branches_url - URL of the head repo's branches(API)
[ ] tags_url - URL of the head repo's tags(API)
[ ] blobs_url - URL of the head repo's blobs(API)
[ ] git_tags_url - URL of the head repo's git tags(API)
[ ] git_refs_url - URL of the head repo's git refs(API)
[ ] trees_url - URL of the head repo's trees(API)
[ ] statuses_url - URL of the head repo's statuses(API)
[ ] languages_url - URL of the head repo's languages(API)
[ ] stargazers_url - URL of the head repo's stargazers(API)
[ ] contributors_url - URL of the head repo's contributors(API)
[ ] subscribers_url - URL of the head repo's subscribers(API)
[ ] subscription_url - URL of the head repo's subscription(API)
[ ] commits_url - URL of the head repo's commits(API)
[ ] git_commits_url - URL of the head repo's git commits(API)
[ ] comments_url - URL of the head repo's comments(API)
[ ] issue_comment_url - URL of the head repo's issue comment(API)
[ ] contents_url - URL of the head repo's contents(API)
[ ] compare_url - URL of the head repo's compare(API)
[ ] merges_url - URL of the head repo's merges(API)
[ ] archive_url - URL of the head repo's archive(API)
[ ] downloads_url - URL of the head repo's downloads(API)
[ ] issues_url - URL of the head repo's issues(API)
[ ] pulls_url - URL of the head repo's pulls(API)
[ ] milestones_url - URL of the head repo's milestones(API)
[ ] notifications_url - URL of the head repo's notifications(API)
[ ] labels_url - URL of the head repo's labels(API)
[ ] releases_url - URL of the head repo's releases(API)
[ ] deployments_url - URL of the head repo's deployments(API)
[ ] created_at - Created at of the head repo
[ ] updated_at - Updated at of the head repo
[ ] pushed_at - Pushed at of the head repo
[ ] git_url - Git URL of the head repo
[ ] ssh_url - SSH URL of the head repo
[ ] clone_url - Clone URL of the head repo
[ ] svn_url - SVN URL of the head repo
[ ] homepage - Homepage of the head repo
[ ] size - Size of the head repo
[ ] stargazers_count - Stargazers count of the head repo
[ ] watchers_count - Watchers count of the head repo
[ ] language - Language of the head repo
[ ] has_issues - If the head repo has issues or not
[ ] has_projects - If the head repo has projects or not
[ ] has_downloads - If the head repo has downloads or not
[ ] has_wiki - If the head repo has wiki or not
[ ] has_pages - If the head repo has pages or not
[ ] has_discussions - If the head repo has discussions or not
[ ] forks_count - Forks count of the head repo
[ ] mirror_url - Mirror URL of the head repo
[ ] archived - If the head repo is archived or not
[ ] disabled - If the head repo is disabled or not
[ ] open_issues_count - Open issues count of the head repo

PR Head Repo Owner License

[ ] key - Key of the head repo owner license
[ ] name - Name of the head repo owner license
[ ] spdx_id - SPDX ID of the head repo owner license
[ ] url - URL of the head repo owner license
[ ] node_id - Node ID of the head repo owner license

Continue to PR Head Repo

[ ] allow_forking - If the head repo is allowed to fork or not
[ ] is_template - If the head repo is template or not
[ ] topics - Topics of the head repo - Array
[ ] visibility - Visibility of the head repo
[ ] forks - Forks of the head repo
[ ] open_issues - Open issues of the head repo
[ ] watchers - Watchers of the head repo
[ ] default_branch - Default branch of the head repo

PR base
Same as PR head
PR _links

[ ] self - Self of the PR
[ ] html - HTML of the PR
[ ] issue - Issue of the PR
[ ] comments - Comments of the PR
[ ] review_comments - Review comments of the PR
[ ] review_comment - Review comment of the PR
[ ] commits - Commits of the PR
[ ] statuses - Statuses of the PR

Continue to PR

[ ] author_association - Author association of the PR
[ ] auto_merge - Auto merge of the PR
[ ] active_lock_reason - Active lock reason of the PR

Please mention the reason why we want to move all the pr data to rds
remember once @harshith-venkatesh told us that we can set up rules for naming PRs and based on that we can filter it out.


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-sandbox/networking-wg-leads
/assign knative-sandbox/networking-wg-leads
Produced by: knative-sandbox/knobots/actions/update-deps
Details:
bumping knative.dev/networking 27525df...e8b2eb9:
  > e8b2eb9 Update community files (# 629)
  > 9ba6cf4 Update actions (# 627)
  > e2b9815 Support TLS server for each test image (# 609)
  > 6f27842 upgrade to latest dependencies (# 626)
bumping knative.dev/pkg fe26417...2fdd5f2:
  > 2fdd5f2 Update actions (# 2449)
  > 76a28b0 set git user name/email prior to merging upstream (# 2448)

/lgtm
/approve

/retest

/retest
/lgtm


crypto-square: Remove test of intermediate functions

So, I was just looking at the canonical test data for crypto-square and I think it was the first time I saw test data for an exercise that also tested the intermediate steps of the problem like normalization or concatenation of segments.
Shouldn't those intermediate tests be removed, as it was agreed on in: https://github.com/exercism/discussions/issues/41
They originated from this PR: #250

Link to canonical-data.json

Indeed, the Haskell track discussed in https://github.com/exercism/xhaskell/issues/259 and decided not to test intermediate functions, diverging from x-common in https://github.com/exercism/xhaskell/pull/391.
Not saying that all have to take the exact approach the Haskell track took or that any other track should agree with the exact same reasons, but if this data helps make the decision, we are glad to provide it.

Since crypto-square's introduction into the Go track at https://github.com/exercism/xgo/pull/68 the Go track has never tested the intermediate functions. So if x-common goes this route, xgo would become closer to x-common.

https://github.com/exercism/problem-specifications/pull/922 was merged, so I think we can close out this issue.


Support for run_time fields

Need support for dynamically computed fields and should be able to perform aggregations over them.
script_fields wouldn't be of help as we can't perform further operations like aggregations or sorting on the scripted fields.
Elasticsearch has rolled out support for this type of use-cases, by a feature called run_time fields.
Would like to know how to solve such use cases in OpenSearch or would like to know if there is a plan to support run_time fields in OpenSearch.

AFAIK there's nobody working on this, but it's a good feature!


Add docs for SwitchPresenter

Fixes #409
Docs for Toolkit PR https://github.com/windows-toolkit/WindowsCommunityToolkit/pull/3379 and https://github.com/windows-toolkit/WindowsCommunityToolkit/pull/3789 where SwitchPresenter as added.
What changes to the docs does this PR provide?
Adds control doc for SwitchPresenter
PR Checklist
Please check if your PR fulfills the following requirements:

[x] Correctly picked the right branch to base the change off (master for new features, live for typos/improvements)
[x] For new pages, used the provided template
[x] For new features, added an entry in the Table of Contents
[ ] Ran against a spell and grammar checker
[ ] Contains NO breaking changes

Other information

Docs Build status updates of commit adfa8d4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/controls/SwitchPresenter.md
:white_check_mark:Succeeded
View

docs/toc.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 2a990b9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/controls/SwitchPresenter.md
:white_check_mark:Succeeded
View

docs/toc.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 59f60c5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/controls/SwitchPresenter.md
:white_check_mark:Succeeded
View

docs/toc.md
:white_check_mark:Succeeded
View

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


Why can't separate their args, just more one space?

model       = app.Command("model", "Post a message to a channel.")
modelName   = model.Arg("name", "Table name.").Required().String()
modelSchema = model.Arg("schema", "table key-value schema").Required().Strings()

. model w w w
command name: model [w], [[w w]]
. model  w w w
command name: model [], [[w w w]]

Two command just more one space, why can't separate their args?

Can you post a full code snippet to reproduce? And what OS are you on?

var (
	Debug = false

	app         = kingpin.New("chandra", "A command-line Chandra application.")
	interactive = app.Flag("interactive", "Interactive mode.").Short('i').Bool()
	// env         = app.Flag("env", "Command run env.").Default(ENV_DEVE).String()

	debugSwitch = app.Command("debug", "Debug mode switch in console mode.")

	server     = app.Command("server", "Register a new user.")
	serverIP   = server.Arg("host", "Server address.").Default("<IP_ADDRESS>").IP()
	serverPORT = server.Arg("port", "Server port.").Default("8095").Int()

	model       = app.Command("model", "Post a message to a channel.")
	modelName   = model.Arg("name", "Table name.").Required().String()
	modelSchema = model.Arg("schema", "table key-value schema").Required().Strings()

	list     = app.Command("list", "List all models.")
	listArgs = list.Arg("components", "Components").Default("all").String()

	quit = app.Command("quit", "Quit this console.")
)

func WriteOut(s string, ars ...interface{}) {
	if len(ars) > 0 {
		fmt.Printf(s, ars)
	} else {
		fmt.Print(s)
	}
}

func console_command(command []string) {
	ji, ok := app.Parse(command)
	Logger("Command Error: %v\n", ok)

	if ok != nil {
		WriteOut("%v\n", ok)
	}
	switch ji {
	case model.FullCommand():
		WriteOut("command name: model %s", *modelName)
		WriteOut(", %s \n", *modelSchema)
		run_model_command(*modelName, *modelSchema)
...

My OS is windows 10 x64.

I tried on centos. Same out.

Maybe I added console function. I will check my code again.
Thanks.

Okay. I can't replicate the issue. I get:
[alec@cavern:~/development/urbancompass]go run t.go model w w
w [w]
[alec@cavern:~/development/urbancompass]go run t.go model w w w
w [w w]
[alec@cavern:~/development/urbancompass]go run t.go model w w w w
w [w w w]


Remove flaky marker on some tests.

They've been mostly green since https://github.com/flutter/flutter/pull/17812


Breaks when using with Astro V2

While upgrading to Astro V2 I encountered the following issue:
09:43:53 [astro] Unable to load astro.config.ts

 error   __vite_ssr_import_2__.default is not a function
  File:
    /node_modules/vite/dist/node/chunks/dep-5e7f419b.js:52224:9
  Code:
    52223 |         const initModule = new AsyncFunction(`global`, ssrModuleExportsKey, ssrImportMetaKey, ssrImportKey, ssrDynamicImportKey, ssrExportAllKey, '"use strict";' + result.code + `\n//# sourceURL=${mod.url}`);
    > 52224 |         await initModule(context.global, ssrModule, ssrImportMeta, ssrImport, ssrDynamicImport, ssrExportAll);
            |         ^
      52225 |     }
      52226 |     catch (e) {
      52227 |         mod.ssrError = e;
  Stacktrace:
TypeError: __vite_ssr_import_2__.default is not a function
    at eval (/astro.config.ts:17:34)
    at async instantiateModule (file:///node_modules/vite/dist/node/chunks/dep-5e7f419b.js:52224:9)

while I disable the astro-sanity config Astro can read the astro.config.ts file just fine.

Seems that downgrading to astro-sanity v1.0.0 also fixes it, so it seems your work on v1.1.2 is not compatible with Astro V2.

I'm not currently experiencing any issues using Astro 2.0.4 on both the static and SSR demos. Can you please provide more info about your environment? (where it's deployed, are you using SSR, static, etc)
Thank you!

I'm going to close this issue but please feel to reach out here or in our Discord if you still are having issues.  Thanks!

From what I know about Vite config files and Astro config files you can't use import.meta.env in the config because the meta environment is running in the source code and not config file. I could be wrong about that though. I can add some documentation around using .env files in the config file if that might help?

@kkga Are you putting this code in your src folder or your astro.config.mjs file? It shouldn't work in the config file because import.meta.env doesn't work there at all to my knowledge.

You're right, it's in the src/, not in the astro config.

Sorry for the late response, but it seems to work now. I've cleared my node_modules and ran yarn again and it worked with the latest version 👍🏼.
One thing though: I'm using typescript in my Astro project, and naturally I have astro.config.ts instead of .mjs. I'm getting the following TypeScript warning when declaring the astro-sanity integration:
Type 'AstroIntegration' is not assignable to type 'false | AstroIntegration | (false | AstroIntegration)[]'.
  Type 'import("/Users/REDACTED_PATH/node_modules/astro-sanity/node_modules/astro/dist/@types/astro").AstroIntegration' is not assignable to type 'import("/Users/REDACTED_PATH/node_modules/astro/dist/@types/astro").AstroIntegration'.
    The types of 'hooks['astro:config:setup']' are incompatible between these types.
      Type '(options: { config: import("/Users/REDACTED_PATH/node_modules/astro-sanity/node_modules/astro/dist/@types/astro").AstroConfig; command: "dev" | "build" | "preview"; ... 5 more ...; injectRoute: (injectRoute: import("/Users/REDACTED_PATH/node_modules/astro-sanit...' is not assignable to type '(options: { config: import("/Users/REDACTED_PATH/node_modules/astro/dist/@types/astro").AstroConfig; command: "dev" | "build" | "preview"; isRestart: boolean; ... 4 more ...; injectRoute: (injectRoute<EMAIL_ADDRESS>        Types of parameters 'options' and 'options' are incompatible.
          Type '{ config: import("/Users/REDACTED_PATH/node_modules/astro/dist/@types/astro").AstroConfig; command: "dev" | "build" | "preview"; isRestart: boolean; ... 4 more ...; injectRoute: (injectRoute: import("/Users/REDACTED_PATH/node_modules/astro/dist/@types/astro").I...' is not assignable to type '{ config: import("/Users/REDACTED_PATH/node_modules/astro-sanity/node_modules/astro/dist/@types/astro").AstroConfig; command: "dev" | "build" | "preview"; ... 5 more ...; injectRoute: (injectRoute: import("/Users/REDACTED_PATH/node_modules/astro-sanity/node_mod...'.
            Types of property 'config' are incompatible.
              Property 'style' is missing in type 'import("/Users/REDACTED_PATH/node_modules/astro/dist/@types/astro").AstroConfig' but required in type 'import("/Users/REDACTED_PATH/node_modules/astro-sanity/node_modules/astro/dist/@types/astro").AstroConfig'.ts(2322)
schema.d.ts(201, 5): 'style' is declared here.

My configuration looks like this:
import { defineConfig } from 'astro/config';
import sitemap from '@astrojs/sitemap';
import sanity from 'astro-sanity';
import compress from 'astro-compress';

export default defineConfig({
	site: 'REDACTED',
	integrations: [
		sitemap(),
		sanity({
			projectId: 'REDACTED',
			dataset: 'production',
			apiVersion: '2022-03-23',
			useCdn: false,
		}),
		compress(),
	],
});


Research for compute backend-as-a-service from App Center

With App Center, our aim is to make the development of your app 10x easier. Beyond the services that exist in App Center to enable DevOps capabilities we’ve also introduced services such as Push, Auth, and Data to help you more easily add capabilities to your app itself. As we continue to look for ways to bring more value to the service and help people take advantage of the cloud, another scenario deals with the addition of backend cloud compute. This could do things like handle events and process data generated by the app. Imagine if you could create and integrate a few serverless functions to process data generated by your app and stored in App Center Data, or intercept a push notification and do some special processing, without leaving the App Center portal.
This month we’re starting the research within this problem space and what a solution could potentially become for offering compute through App Center. We’re asking for your help now to better understand how you’re thinking about developing apps that tap into the power of compute in the cloud.
If you are considering the use of cloud compute for your app or have an app already leveraging cloud compute, we're interested in learning more. Submit this survey to help us understand more about your situation with compute. Thanks for any help you can provide here and any contributions you’ve made to discussions in this repo. It really does help us work toward a better experience for the community.

I think it is crucial to have this capability. In the current implementation of Data service, all logic has to be in the mobile app. This approach might be sufficient for small/simple applications but it is not suitable for more complex application.

@jiberan We'd like to understand your scenarios and use cases in detail. Would you be willing to hop on a call with us in the coming days? Please let me know and I'd send a meeting invite accordingly. Thank you!

@elamalani sorry for the late response. Sure, but I'm out of office until 10/10. It is ok to have call after that?

@jiberan Please send me an email at emalani at microsoft dot com and we can talk after 10/10. Thanks.

The research into MBaaS related to compute has concluded for now. As more research opportunities open up, watch for them in this repository and iteration plans.

The research into MBaaS related to compute has concluded for now. As more research opportunities open up, watch for them in this repository and iteration plans.


Fix hierarchical output

Getting log output that looks like this:
[DBUG] [08] ...|next#277: mark: U+FFFD '�', start: 0, index: 6, line: 2
[INFO] [14] ...|emit#199: itemParagraph: "break." l.start: 0 (1) l.index: 6 (7) line: 2

[INFO] [03] ...|...|...|...|parse#346: Parser got token: &parse.item{ID:1, Type:4, Text:"A paragraph with a line", Line:1, StartPosition:1, Length:23}

[DBUG] [15] ...|...|...|...|...|paragraph#819: START
[DBUG] [13] lexParagraph#669: END
[DBUG] [06] lexStart#486: START
[DBUG] [06] lexStart#511: isEndOfLine == true
[DBUG] [06] lexStart#525: Found end of last line
[INFO] [14] ...|emit#199: itemEOF: "" l.start: 6 (7) l.index: 6 (7) line: 2
[DBUG] [06] lexStart#535: END
[DBUG] [05] run#183: End
[DBUG] [15] ...|...|...|...|...|paragraph#843: END
[DBUG] [04] ...|...|...|...|...|peek#424: Using &parse.item{ID:3, Type:0, Text:"", Line:2, StartPosition:7, Length:0}
[DBUG] [03] ...|...|...|...|parse#385: END
[DBUG] [01] ...|...|...|Parse#331: END

One possible way to fix this is to only increase by 1 level over the last output if the output jumps more than two levels.
Another way would be to experiment with a git log --graph type view...

Heirarchical output might will be removed as it dosen't really make a difference. It is also very broken.


502 Bad Gate Way issues

Link to sample
https://learn.microsoft.com/zh-cn/rest/api/aks/managed-clusters/abort-latest-operation?tabs=HTTP
Library name and version
azure-mgmt-containerservice 26.0.0
Language of the Sample

[ ] C#/.NET
[ ] Java
[ ] JavaScript/TypedScript
[X] Python
[ ] Golang
[ ] Other - Please specify in Issue details field

Sample Issue Type

[ ] Sample not working
[ ] Sample missing
[x] Do not understand sample

Issue details
Hi team,
Why it is report me 502 Bad GateWay error, while I use agent pool and manager cluster begin_abort_latest_operation method? When I request using the rest API, when it is an update, the error code reported to me for the first request. If I request again, he will report me that the current status is' cancel 'and' operation not allowed '.
Python SDK request code:

client.managed_clusters.begin_abort_latest_operation(resource_group_name=self.resource_group,
resource_name=self.cluster_name)

client.agent_pools.begin_abort_latest_operation(self.resource_group, self.cluster_name, nodepool_name)

API request details:
POST: /subscriptions/af8a838e-eb6b-4a7a-974e-36128b1ea4b7/resourceGroups/cqfybg6fef-sapsecxco2-d7/providers/Microsoft.ContainerService/managedclusters/cqfybg6fef-sapsecxco2-d7-kub/abort?api-version=2023-07-01
POST: /subscriptions/af8a838e-eb6b-4a7a-974e-36128b1ea4b7/resourceGroups/cqfybg6fef-sapsecxco2-d7/providers/Microsoft.ContainerService/managedClusters/cqfybg6fef-sapsecxco2-d7-kub/agentPools/shrvsbzqv9/abort?api-version=2021-09-01
BR
Marvin,Wen
Expected behavior
No response
Actual behavior
No response
Reproduction Steps
No response
Environment
No response

Hi, @MarvinWenS
If you got the response Cancel operation is not allowed when the ProvisioningState is Canceled, it means that the last long operation was successfully aborted. Your first request was processed by the service, but the client didn't receive the response correctly, so it came to 502 Bad GateWay error.
Usually the response would be in 204 status with no content returned. Please retry the method and if this error code keeping reported, please give us feedback and provide more details on the reproduction steps.


Dataset.repeat(0)

URL(s) with the issue:.
https://www.tensorflow.org/api_docs/python/tf/data/Dataset#repeat
Description of issue (what needs to be changed):.
I am coming from here: https://github.com/tensorflow/tensorflow/issues/56215.
Here's how to get a dataset (from Image classification from scratch).
curl -O https://download.microsoft.com/download/3/E/1/3E1C3F21-ECDB-4869-8368-6DEBA77B919F/kagglecatsanddogs_5340.zip
unzip kagglecatsanddogs_5340.zip

Then run this:
import tensorflow as tf

train_ds = tf.keras.preprocessing.image_dataset_from_directory("PetImages")

flag = False
for images, labels in train_ds.repeat(0):
    flag = True
assert flag  # Fails

We can see that .repeat(0) will not enter the for loop.
In my opinion, the expected behavior for .repeat(0) would be to move through the Dataset once and then StopIteration, because we are repeating the dataset zero times.  However, .repeat(0) results in a zero-length iterable.
I think this should be documented: that if you want to move through the dataset once, don't use .repeat(0) instead use .repeat(1).

@jamesbraza Could you please have a look at this gist and confirm the issue?
Thank you!

Yeah that's correct, thank you for converting @sushreebarsa 👍
The assertion's failure means we never entered the loop.  I think it'd be useful to document this

I do see that.  In my opinion I think a slight clarification (e.g. an example) to the docs would be useful.
Current count arg description:

(Optional.) A tf.int64 scalar tf.Tensor, representing the number of times the dataset should be repeated. The default behavior (if count is None or -1) is for the dataset be repeated indefinitely.

Here is what I would like to see:

(Optional.) A tf.int64 scalar tf.Tensor, representing the number of times the dataset should be repeated. The default behavior (if count is None or -1) is for the dataset be repeated indefinitely.  If count is 0, the output dataset will be empty.

What do you think?

@jamesbraza Thank you for the response.

Repeats this dataset so each original value is seen count times.

The above line describes the same in the document. If you really think this is necessary please create a PR. Thanks!


How to compare stdout with a Vec?

I want compare command stdout with my tested app's stdout like this:
    let output = Command::new("uname").output().unwrap();
    let stdout = output.stdout;
    new_cmd!()
        .assert()
        .success()
        .stdout(stdout)    // this will give an error
        .stderr("");

I can't find a simple API from predicates. Can you suggest a proper way to handle this?

So if we go to the docs, .stdout() takes a IntoOutputPredicate.  There is an implementation that takes a &'static [u8].
A Vec<u8> can be derefed as a &[u8] but the lifetime is a problem (possibly a bug?).
But you can use it for inspiration.
So in theory, you could do something like
use predicates::prelude::*;

    let output = Command::new("uname").output().unwrap();
    let stdout = output.stdout;
    new_cmd!()
        .assert()
        .success()
        .stdout(predicate::eq(&stdout as &[u8]))
        .stderr("");

And I created https://github.com/assert-rs/assert_cmd/issues/51


optimisticLock bug

It appears that optimistic locking has a bug. When I implement everything according to documentation and attempt to read 'version' right after save(), such as to send it back to my user through ajax, the new 'version' is not updated.
$order->version equals 0

However, when I access 'version' through getOldAttribute('version') the code works as expected.
try {
    if($order->save(false)) {
        return ['data' => array('validated'), 'tag' => array($order->tag), 'version' => array($order->getOldAttribute('version'))];`
    else
        return ['data' => array('error'), 'reason' => array('Server error while saving order.')];
}
catch(StaleObjectException $e) {
    return ['data' => array('error'), 'reason' => array('The order has been modified. Please, look up this order again.')];
}

So, another words, immediately after updating an existing record (within the same request):
$order->version = 0;

but
$order->getOldAttribute('version') = 1;

I am expecting this to be in reverse.

Looking into the source code, looks like 'version' is added to and incremented in $values[] array and copied into $_oldAttributes, but is not copied into $_attributes?
protected function updateInternal($attributes = null)
{
    if (!$this->beforeSave(false)) {
        return false;
    }
    $values = $this->getDirtyAttributes($attributes);
    if (empty($values)) {
        $this->afterSave(false, $values);
        return 0;
    }
    $condition = $this->getOldPrimaryKey(true);
    $lock = $this->optimisticLock();
    if ($lock !== null) {
        $values[$lock] = $this->$lock + 1;
        $condition[$lock] = $this->$lock;
    }
    // We do not check the return value of updateAll() because it's possible
    // that the UPDATE statement doesn't change anything and thus returns 0.
    $rows = $this->updateAll($values, $condition);

    if ($lock !== null && !$rows) {
        throw new StaleObjectException('The object being updated is outdated.');
    }

    $changedAttributes = [];
    foreach ($values as $name => $value) {
        $changedAttributes[$name] = isset($this->_oldAttributes[$name]) ? $this->_oldAttributes[$name] : null;
        $this->_oldAttributes[$name] = $value;
    }
    $this->afterSave(false, $changedAttributes);

    return $rows;
}

Issue resolved by commit 51a442d

I looked at the fix and without testing it, it seems that the fixed code will now produce the same result for
 $order->version will be 1 and
 $order->getOldAttribute('version') will also be 1 instead of 0

This is expected: as version value has been just updated, so it is not 'dirty'.

OK. Cool. Thanks!


Contribution guidelines could be more clear

update text to use more direct language
update instruction for yarn *:check (yarn check seems to be more correct)
use shorter sentences where possible

@hammer Specific Changes:
Contributing
Before making a change please discuss the change you wish to make with the owners of this repository. Discuss changes via issue issue or any other method.
Our code style
There is an eslint, prettier and python config that ensures a consistent code style. We also recommend auto-save and format on save configured for VS Code. To check for style errors, run $ yarn check. Code style will also be checked when you push using a git hook. Make sure it’s passing before sending a pull request.
Branching guidelines
We don't have a strict rule for branch name guidelines. You should try to name your branch using kebab-case with the name of the feature/issue your are working on (eg: adopt-jotai). You can also prefix your branch name with the issue number if you are creating the branch from issues in GitHub.
Pull Request Process
Please try to keep your pull request focused, in scope, and avoid including unrelated commits.
We adopted the Squash and merge convention to give a nice, clean, linear history on main which makes it easier to bisect and track changes.
Thank you for contributing!

Closed by #433


Remove validator subcommands.

Signed-off-by: Byron Gravenorst<EMAIL_ADDRESS>Pull Request Description
Remove validator subcommands.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Exception: cannot share data context between Swing events

I'm submitting a ...

[ x ] bug report
[ ] feature request
[ ] puppy => You're not submitting a puppy. I already have one and he's adorable

What is the current behavior?
When Opening Webstorm got the following excpetion:
java.lang.Throwable: cannot share data context between Swing events; initial event count = 569842; current event count = 572763
at com.intellij.openapi.diagnostic.Logger.error(Logger.java:161)
at com.intellij.ide.impl.DataManagerImpl$MyDataContext.getData(DataManagerImpl.java:327)
at com.intellij.openapi.actionSystem.DataContext.getData(DataContext.java:42)
at com.intellij.openapi.actionSystem.AnActionEvent.getData(AnActionEvent.java:192)
at com.intellij.openapi.actionSystem.AnActionEvent.getProject(AnActionEvent.java:151)
at gitflow.actions.StartFeatureAction.actionPerformed(StartFeatureAction.java:36)
at com.intellij.openapi.actionSystem.ex.ActionUtil.lambda$performActionDumbAware$5(ActionUtil.java:273)
at com.intellij.util.SlowOperations.lambda$allowSlowOperations$0(SlowOperations.java:77)
at com.intellij.util.SlowOperations.allowSlowOperations(SlowOperations.java:64)
at com.intellij.util.SlowOperations.allowSlowOperations(SlowOperations.java:76)
at com.intellij.openapi.actionSystem.ex.ActionUtil.performActionDumbAware(ActionUtil.java:273)
at com.intellij.openapi.keymap.impl.IdeKeyEventDispatcher$1.performAction(IdeKeyEventDispatcher.java:616)
at com.intellij.openapi.keymap.impl.IdeKeyEventDispatcher.lambda$processAction$3(IdeKeyEventDispatcher.java:676)
at com.intellij.openapi.application.TransactionGuardImpl.performUserActivity(TransactionGuardImpl.java:95)
at com.intellij.openapi.keymap.impl.IdeKeyEventDispatcher.processAction(IdeKeyEventDispatcher.java:675)
at com.intellij.openapi.keymap.impl.IdeKeyEventDispatcher.processAction(IdeKeyEventDispatcher.java:626)
at com.intellij.openapi.keymap.impl.IdeKeyEventDispatcher.processActionOrWaitSecondStroke(IdeKeyEventDispatcher.java:486)
at com.intellij.openapi.keymap.impl.IdeKeyEventDispatcher.inInitState(IdeKeyEventDispatcher.java:481)
at com.intellij.openapi.keymap.impl.IdeKeyEventDispatcher.dispatchKeyEvent(IdeKeyEventDispatcher.java:232)
at com.intellij.ide.IdeEventQueue.dispatchKeyEvent(IdeEventQueue.java:889)
at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.java:833)
at com.intellij.ide.IdeEventQueue.lambda$dispatchEvent$8(IdeEventQueue.java:449)
at com.intellij.openapi.progress.impl.CoreProgressManager.computePrioritized(CoreProgressManager.java:808)
at com.intellij.ide.IdeEventQueue.lambda$dispatchEvent$9(IdeEventQueue.java:448)
at com.intellij.openapi.application.impl.ApplicationImpl.runIntendedWriteActionOnCurrentThread(ApplicationImpl.java:781)
at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:502)
at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)

Is this a bug? Sorry about that. If so give me explicit details how to reproduce:

Open IntelliJ

What is the expected behavior?
No Exception bubble should appear in webstorm

What is the motivation / use case for changing the behavior?

Please tell me about your environment:

Gitflow4idea version: 0.7.6

Gitflow version: 1.12.3 (AVH Edition)

IntelliJ Help -> about > click copy icon and paste here. Should look like this:

  Webstorm 2021.1.3

Thanks for the report.
Does this happen for every project? Specific projects?
If so are any of those public? I need to be able to repro for a fix

Hi @OpherV - thanks for taking the time to write back.
Probably happens on my specific project - I cannot share the project publicly but If thats ok I will share it privately with you so you'll be able to reproduce it.
Is that ok? how would you suggest to share it?
Thanks for this awesome plugin!

Let's try with a zip of the project? Hit me at<EMAIL_ADDRESS>:)

@OpherV  Awesome!
Sent you an email.
Appreciate your support!

I can't seem to reproduce this at all even with your project. It might be an OS thing.
I assume you're running this on a mac? Can you tell me which specific version?

Also, please test if this still happens with the new 0.7.7 version

MacOS Big Sur 11.4.
Seems to be solved 0.7.7.
Thanks for checking - Appreciate the support!


[libssh] add static build support for MinGW subsystem

Describe the pull request

What does your PR fix?
Static build failure on MinGW subsystem.

Using set_property instead of set_target_properties, retains -DLIBSSH_STATIC option in COMPILE_FLAGS property, that is a must for static build, according to https://api.libssh.org/stable/libssh_linking.html.
cmake -E create_symlink command is available only on UNIX, according to https://cmake.org/cmake/help/v3.4/manual/cmake.1.html#unix-specific-command-line-tools

Which triplets are supported/not supported?

Yes

If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

Have you submitted this patch upstream?

yes, already merged.


initial draft of operator-testing-tool proposal for openshift-4.3

Description of the change:
this is the proposal draft document for the operator-testing-tool, for openshift-4.3
Motivation for the change:
not a breaking change or code fix, just the proposal for a new feature.

Make sure to run the markdown checker, /hack/ci/marker --root=doc
./hack/ci/marker --root=doc
Found broken reference (  ->  ) at doc/proposals/openshift-4.3/operator-testing-tool.md:27
Found broken reference (  ->  ) at doc/proposals/openshift-4.3/operator-testing-tool.md:28
Found broken reference (  ->  ) at doc/proposals/openshift-4.3/operator-testing-tool.md:29
Found broken reference (  ->  ) at doc/proposals/openshift-4.3/operator-testing-tool.md:30
Found broken reference (  ->  ) at doc/proposals/openshift-4.3/operator-testing-tool.md:31
Found broken reference (openshift/docs -> openshift/docs) at doc/proposals/openshift-4.3/operator-testing-tool.md:31
Found broken reference (maturity levels -> maturity levels) at doc/proposals/openshift-4.3/operator-testing-tool.md:170
Found broken reference (maturity-levels -> maturity-levels) at doc/proposals/openshift-4.3/operator-testing-tool.md:170
Found broken reference (optional -> optional) at doc/proposals/openshift-4.3/operator-testing-tool.md:234
make: *** [test/markdown] Error 1

Actually we might have to fix the marker checker to handle the proposal format

/test marker


removed redundant consts from constexpr variables

read
"When can I / should I use both, const and constexpr together?"


Big Sur close prompt looks scary

See screenshot, Big Sur dims the whole window when showing an alert and it looks like VSCode is locked up or frozen when everything is working fine.
Not sure if this is an Electron thing or not... but there you go

/duplicate


Update dependencies

Sorry for the noise here, accidentally opened a PR here instead of in our fork.


Text2d visibility fix

Objective
Text drawn with Text2d isn't visible in main.
fixes #9676
Solution
Add an ExtractedSpriteBatches resource that allows the extraction of sprites in batches that all share the same entity for visibility checks.
In extract_text2d_sprite extract to ExtractedSpriteBatches rather than ExtractedSprites.
This is a bit of a hack but it's harmless and minimal.
My first attempt had three buffers:

Set of all Text2d entities with their  Entity, Transform, and a range into buffer 2.
Vec of ExtractedGlyphSections. Each ExtractedGlyphSection has a handle for the font's atlas texture, color, and a range of indices into buffer 3.
Vec of ExtractedGlyphs. Each ExtractedGlyph has a position (relative to the transform) and a Rect containing coords of the glyph in the font's atlas texture.

I struggled to get it to work though. It was almost there but there were some weird texturing issues I couldn't work out even after spending half a day on it:

---
I still don't understand Bevy's rendering internals very well, so it could be anything.
Anyway, I decided to switch approach. This PR is deliberately as simple as I could make it. It fixes Text2d rendering and shouldn't introduce any new problems or have any significant performance costs. The implementations of ExtractedSpriteBatches and extract_text2d_sprites aren't super efficient, but naive benchmarks suggest this Text2d is faster than 0.11.2's Text2d by about 5-10% (probably entirely due to the improvements in bevy_sprites).
cargo run --profile stress-test --features trace_tracy --example many_sprites

(yellow is this PR, red is main)
The main drawback is that ExtractedSpriteBatches is exposed as public, I'd rather have kept it private as it's not really suitable for much else except text rendering.

Changelog

Added ExtractedSpriteBatches.
Modified queue_sprites and prepare_sprites so they also add the sprites from ExtractedSpriteBatches.
extract_text2d_sprite extracts to ExtractedSpriteBatches instead of ExtractedSprites.

I'm assuming that this needs a major rework after #9685 and #9903?

I prefer #10100  if it fixes the same problem.

Closing due to merging #10100 If that PR doesn’t address the problem, you’re welcome to come shout at me. 💜


Add equipment content

What does this PR do?
=>Add equipment content
Screenshots?

@nerdlet lets not duplicate components like this, for a later update.


broken with rxjs 5.0.0-beta.5

New with rxjs 5.0.0-beta.5, Subjects have been moved directly under the /src folder:
https://github.com/ReactiveX/rxjs/commit/30c4ef339d8ed7381e9353018891aa0362cb5d0a
@ngrx/store imports would need to be adjusted, and the rxjs peerDependency version should be upped to ^5.0.0-beta.5.
In the meantime the fix for client applications is to specify beta.4 in package.json, i.e. "rxjs": "5.0.0-beta.4"

👍

Just saw same thing today when updating dependencies on an Ionic2 hybrid app. I reverted back to rxjs beta.2. I find ngrx a pleasure to work with and appreciate everyone's efforts very much.

thanks for this - we're working through some issues in ng core wrt some changes in beta4 and 5 and typescript 1.8+ - i'll merge this as soon as they're resolved 👍

This was fixed some time ago.

Thanks all. Working well today with ngrx/store 1.5.0 & rxjs 5.0.0-beta.6. Cheers!


No option to pass Git credentials

Hi there,
I'm trying to set up a build action with a T3 topology. Therefore "west update" of the action-zephyr-setup needs credentials to checkout other repositories, but there is no way to pass credentials to the "west update" call in action-zephyr-setup.
Is there a way to work around this problem?
Regards
Sebastian

Hey hi, not sure I fully understand the issue but can you add an extra step to setup git before the action runs?
Something like
      - name: Environment Setup
        run: |
          git config --global user.email<EMAIL_ADDRESS>          git config --global user.name "Zephyr Bot"

Shouldn't be needed unless you are doing a rebase or some other operations though. Feel free to link to an example or a log or something if you can.

Hi @fabiobaltieri, that is actually what I meant. However, I solved this a little bit different:
git config --global credential.helper store
echo "https://x-access-token:${{ secrets.PAT<EMAIL_ADDRESS>>> ~/.git-credentials

Shouldn't be needed unless you are doing a rebase or some other operations though. Feel free to link to an example or a log or something if you can.

For further explanation, especially because I missed that important information, it is also necessary if private repositories need to be checked out by west init. Or am I missing something?
However, now I have a different issue:
-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: /home/runner/work/repo_name/repo_name/gateway
-- CMake version: 3.29.6
-- Found Python3: /opt/hostedtoolcache/Python/3.11.9/x64/bin/python (found suitable version "3.11.9", minimum required is "3.8") found components: Interpreter
-- Cache files will be written to: /home/runner/.cache/zephyr
-- Zephyr version: 3.7.0-rc2 (/home/runner/work/repo_name/repo_name/zephyr)
-- Found west (found suitable version "1.2.0", minimum required is "0.14.0")
-- Board: esp32s3_devkitc, qualifiers: esp32s3/procpu
-- ZEPHYR_TOOLCHAIN_VARIANT not set, trying to locate Zephyr SDK
-- Found host-tools: zephyr 0.16.8 (/home/runner/work/repo_name/repo_name/zephyr-sdk)
-- Found toolchain: zephyr 0.16.8 (/home/runner/work/repo_name/repo_name/zephyr-sdk)
-- Found Dtc: /home/runner/work/repo_name/repo_name/zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/dtc (Required is at least version "1.4.6")
-- Found BOARD.dts: /home/runner/work/repo_name/repo_name/zephyr/boards/espressif/esp[32](https://github.com/organisation/repo_name/actions/runs/9855561738/job/27210667040?pr=6#step:9:33)s3_devkitc/esp32s3_devkitc_procpu.dts
-- Generated zephyr.dts: /home/runner/work/repo_name/repo_name/build/zephyr/zephyr.dts
-- Generated devicetree_generated.h: /home/runner/work/repo_name/repo_name/build/zephyr/include/generated/zephyr/devicetree_generated.h
-- Including generated dts.cmake file: /home/runner/work/repo_name/repo_name/build/zephyr/dts.cmake
CMake Error at /home/runner/work/repo_name/repo_name/zephyr/cmake/modules/dts.cmake:383 (message):
  command failed with return code: no such file or directory
Call Stack (most recent call first):
  /home/runner/work/repo_name/repo_name/zephyr/cmake/modules/zephyr_default.cmake:132 (include)
  /home/runner/work/repo_name/repo_name/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
-- Configuring incomplete, errors occurred!
  /home/runner/work/repo_name/repo_name/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  CMakeLists.txt:4 (find_package)

FATAL ERROR: command exited with status 1: /usr/local/bin/cmake -DWEST_PYTHON=/opt/hostedtoolcache/Python/3.11.9/x64/bin/python -B/home/runner/work/repo_name/repo_name/build -GNinja -DBOARD=esp32s3_devkitc/esp32s3/procpu -S/home/runner/work/repo_name/repo_name/app
Error: Process completed with exit code 1.

I changed the actual names of my private repos. It looks strange, that the repo name is used twice /repo_name/repo_name/ during the build. Especially because it is different from what has been configured in the action.yml.
Did you ever tested the action with a T3 topology?
Greetings
Sebastian

Never mind, the second issue was caused by the GitHub cache of the runner. After deleting it, everything worked.


Windows App Crashing when opening reports

Windows app crashing when reports selected.
Case/491921 (includes desktop logs)

Seems to be issue with default browser not being properly set. Here is a possible fallback solution.

User reported that resetting the default browser fixed the issue.


Cop request: private delegates

Is your feature request related to a problem? Please describe.
When using #delegate, ActiveSupport creates a new method on the class, but this method does not respect the visibility scope of said class.
For example:
class Foo
  def initialize(bar)
    @bar = bar
  end

  attr_reader :bar

  private

  delegate :baz, to: :bar
end

The generated method #baz will not be private. The #delegate method does, however, provide an option to create a private method like so:
delegate :baz, to: :bar, private: true

Describe the solution you'd like
I would like a cop that detects calls to #delegate that:

Are in a private scope.
Does not pass the private: true option.

Sidenote: The private option was added in Rails 6:
https://blog.bigbinary.com/2019/06/10/rails-6-adds-private-option-to-delegate-method.html

I've had the same desire and would like to build this feature!
is it okay if I go ahead and start working on it following the contribution guidelines? or is there any other protocol to follow up on?

@ABaldwinHunter go ahead! See https://github.com/rubocop/rubocop-rails/blob/master/CONTRIBUTING.md

I started working on this. But what to do (in terms of auto-correction) when private option is passed, but there is mismatch in the scope? E.g.
class A
  private

  delegate :bar, to: :foo, private: false

class B
  public

  delegate :bar, to: :foo, private: true

Should we instead of changing the private option, move the node? Or register an offense with a different message (than in the missing private option) and do not attempt to auto-correct?


cp problem

hi, I face a problem while I compile the newest version project.
cp: cannot copy a directory, '/home/chaowyc/tensorflow_cc/tensorflow_cc/build/tensorflow/tensorflow/co
ntrib/makefile/gen/protobuf', into itself, './tensorflow/contrib/makefile/gen/protobuf/protobuf'

the whole context is showed in the picture below:

I tried the last second commit version, but failed too

I read the issue the other one posted who faced the same problem before, and the solution you provided in that issue by adding -DCMAKE_INSTALL_PREFIX is doesn't work for me, and at the same time I face a new problem before the cp.

so, is there any relation between the two problem?

Hi, the solution will probably work for you as well, but you have to remove the tensorflow_cc/build folder first. Also consider removing ~/.cache to clean up the previous builds.

hi, I think I find the key point why this cp error appears after reading the your whole project and many times building.
At first, I found the error always showed after tensorflow build process was finished. That means our tensorflow is successful built and then next step will do some cp operations, At that time I didn't know why there should have cp operation because I only typed make command without make install, as you can see the make install command will cause some files movement and use cp is make sense.
So, I began read your cmake files. After long time reading, I found some clues in cmake directory. In the TensorflowShared.cmake file, there are some command execute sequences, the last two commands are to build tensorflow and do some copy links by executing bash files respectively. That is what I want find as I described above, the error shows after tensorflow is successful built.
Then read the copy-links bash file. According to my understanding, the main function of the bash file is find symbolic links under the directory which is specified by argument, then remove these symbolic links by unlink them and copy the content from the realpath to there, it seems something wrong when copying . Actually it is, when I comment the do copy-links bash file command, which means there is no copy process after building tensorflow, the cp problem is disappear.
Then, I execute the commands inside the copy-links.sh manually, I get the same cp error, and the error only happened when process this path:
"./tensorflow/contrib/makefile/gen/protobuf/protobuf"

after testing this path, I find this symbolic links actully is a circle.
when list the content in this path (./tensorflow/contrib/makefile/gen/protobuf/protobuf), shows below
lib, bin, include, protobuf

then cd to the protobuf dir and list(./tensorflow/contrib/makefile/gen/protobuf/protobuf/protobuf), shows same content as below. you can do these processes several times, you will find the content is NEVER changed.
So this circle will lead the source and destination is same when do the copy command to protobuf dir !!!.
AND, fortunately it's also means that we do not need do the copy command to this dir beacause it's content not changed, it's SAME one.
I finally got this, and modify your copy-links.sh file, now it's look likes below:
#!/bin/sh
set -e
skip="./tensorflow/contrib/makefile/gen/protobuf/protobuf"
for f in $(find "$1" -type l); do
    if test $f = $skip
        then
            continue
    fi
    realf="$(realpath $f)"
    unlink "$f"
    cp -r "$realf" "$f"
done

it's look likes simple and force, but it really works for me, faceplam.
I still have some question, I don't understand why you clean up the symbolic links. I browse the commit history find that it's no need delete these links before.
And, when I compile the tensorflow by bazel, there is no symbolic links generated, so why there is some when compile tf through your project.
Anyway, thank for you project, I can get my hand on building the tf by cmake, and I also learn a lot by read your code. Hope my issue will help you find the truly solution for this problem.

Hi,
The reason for "delinking" is that some of the files in the compiled library are actually only links to the ~/.cache/bazel. After removing ~/.cache, the installation would stop working. Can you please try to remove both tensorflow_cc/build and ~/.cache, and rebuild the project with -DCMAKE_INSTALL_PREFIX=/usr/local?

Closing for inactivity, please reopen if you continue to encounter this issue.

Hi, the issue should be fixed in the latest master.