Clarify use and generation of intermediate certifiates for multicluster

Document use and automate creation of intermediate certificate by Citadel.
The README.md explains how to generate and set-up shared root of trust for multiple clusters.
It makes use of the Makefile to automate certificate creation for Citadel trust chain.
With some more customization, the Makefile could replace some shell scripts that are currently being used in various tests.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: elevran
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: frankbu
If they are not already assigned, you can assign the PR to them by writing /assign @frankbu in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

samples/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/assign @frankbu

@elevran: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
ae72576b57231c8a6837304f7650e5ef52ce816a
link
/test istio-integ-local-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@elevran: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
ae72576b57231c8a6837304f7650e5ef52ce816a
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
ae72576b57231c8a6837304f7650e5ef52ce816a
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@elevran: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
ae72576b57231c8a6837304f7650e5ef52ce816a
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
ae72576b57231c8a6837304f7650e5ef52ce816a
link
/test istio-integ-k8s-tests

prow/istio-presubmit.sh
ae72576b57231c8a6837304f7650e5ef52ce816a
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-presubmit

@elevran: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
ae72576b57231c8a6837304f7650e5ef52ce816a
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
ae72576b57231c8a6837304f7650e5ef52ce816a
link
/test istio-integ-k8s-tests

prow/istio-presubmit.sh
ae72576b57231c8a6837304f7650e5ef52ce816a
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: elevran, frankbu
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

samples/OWNERS [frankbu]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@elevran: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
ae72576b57231c8a6837304f7650e5ef52ce816a
link
/test istio-integ-k8s-tests

prow/istio-presubmit.sh
ae72576b57231c8a6837304f7650e5ef52ce816a
link
/test istio-presubmit

prow/istio-integ-local-tests.sh
ce5179cdf6f2c4b245e857f0ef8a4bcac8021304
link
/test istio-integ-local-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@elevran: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
ae72576b57231c8a6837304f7650e5ef52ce816a
link
/test istio-presubmit

prow/istio-integ-local-tests.sh
ce5179cdf6f2c4b245e857f0ef8a4bcac8021304
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
ce5179cdf6f2c4b245e857f0ef8a4bcac8021304
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@elevran: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
ce5179cdf6f2c4b245e857f0ef8a4bcac8021304
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
ce5179cdf6f2c4b245e857f0ef8a4bcac8021304
link
/test istio-integ-k8s-tests

prow/istio-presubmit.sh
ce5179cdf6f2c4b245e857f0ef8a4bcac8021304
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-presubmit
/test istio-integ-local-tests

@elevran: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
ce5179cdf6f2c4b245e857f0ef8a4bcac8021304
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
ce5179cdf6f2c4b245e857f0ef8a4bcac8021304
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@elevran: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
ce5179cdf6f2c4b245e857f0ef8a4bcac8021304
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
ce5179cdf6f2c4b245e857f0ef8a4bcac8021304
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Cannot move a file from the /root folder to desktop

### Tasks

Closing since this issue has no repro instructions.


Make "Profile" field in QED S3 config panel an optional field

Change "Profile" field in QED S3 config panel from a required field to an optional field. Omitting a profile might allow usage of user's running EC2 instance permission or user's "default" AWS profile.

Fixed in f4c71e822580214845bb973d16108062510c8fe9

Closing as complete


move changelog entry that is not in 23.4.2

In #6736 it looks like the branch should've been updated before merging, as the changelog entry were added before 23.4.2 was released.
@aaronabramov

Codecov Report

Merging #6796 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #6796   +/-   ##
=======================================
  Coverage   63.63%   63.63%
=======================================
  Files         235      235
  Lines        9017     9017
  Branches        4        3    -1
=======================================
  Hits         5738     5738
  Misses       3278     3278
  Partials        1        1

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 609f385...e2718aa. Read the comment docs.

good catch! :)


fix: US address space syntax

https://app.assembla.com/spaces/gant-ab/tickets/realtime_cardwall?ticket=12724
Chaning {{space}} to {{{space}}} syntax, otherwise   appears.

Sorry @shieldo , made changes in PHX vendor instead of this repo. Should be good now.

Great @kardi31 - thanks so much for the fix!


How to delete Expire token in DB

How to delete Expire token in DB.

This functionality hasn't been implemented yet, it will eventually be integrated in a separate package when I have the time

@lucadegasperi Currently we have no way to get expired access tokens and refresh tokens from FluentAccessToken and FluentRefreshToken. I'm trying to create my command to delete them but, i need to extend and replacement those by new implementation.
I would like to create a pull request to add new method to those FluentAdapter if you are agree with that ?

@maximebeaudoin thanks for your offer, right now this package focuses on providing an easy way to use league/oauth2-server inside laravel. All the management stuff could be done inside a separate package as I envision it.

Any updates on this?


an improvement if its possible!

@martinfekete10
First of all the new version finally works without issues and crashes! thank you so much and even more for new ui, is awesome!
may you consider a creation of more customazation like the ideas of the screenshot?

I'm actually thinking about changing seeker bar to the same design that is used in iOS so that will probably be part of the next (?) release. As of other suggestions, I'll need to think it through - on the one hand it's great to have a choice, on the other I don't want to clutter up settings too much

I'm actually thinking about changing seeker bar to the same design that is used in iOS so that will probably be part of the next (?) release. As of other suggestions, I'll need to think it through - on the one hand it's great to have a choice, on the other I don't want to clutter up settings too much

@martinfekete10
I understand the thought! But more option to make the app to our liking will be useful and totaly awesome!!!


[CosmosDB] Fix references in privateEndpointConnection.json

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

Can one of the admins verify this patch?

/azp run automation - sdk

@weidongxu-microsoft Please help merge the PR.

@soeom
Please review the CI error on BreakingChange first.
Also Martin still have the "change requested" here.

@weidongxu-microsoft
@anthony-c-martin signed off the pull request by replacing the tag to ARMSignedOff. He also confirmed that he signed off through teams.
There is no ci failures other than breaking change. This is unavoidable because the purpose of this PR is to consolidate the reference to common parameters.
Please help merge the PR.

@soeom
OK. The BreakingChange seems to be a false positive.
Martin had to change "change requested" to "approve", else technically I cannot press merge at all (github forbid it).

@akning-ms
This BreakingChange CI seems to be a false positive. It reports "removal of client parameter" but none of the change remove any client parameter. It just replaces them.
    id: '1001',
    code: 'NoVersionChange',
    message: 'The versions have not changed.',
    old: {
      ref: 'file:///home/vsts/work/1/c93b354fd9c14905bb574a8834c4d69b/specification/cosmos-db/resource-manager/Microsoft.DocumentDB/preview/2019-08-01-preview/privateLinkResources.json#',
      path: '',
      location: 'file:///home/vsts/work/1/c93b354fd9c14905bb574a8834c4d69b/specification/cosmos-db/resource-manager/Microsoft.DocumentDB/preview/2019-08-01-preview/privateLinkResources.json:1:1'
    },
    new: {
      ref: 'file:///tmp/resolved/specification/cosmos-db/resource-manager/Microsoft.DocumentDB/preview/2019-08-01-preview/privateLinkResources.json#',
      path: '',
      location: 'file:///tmp/resolved/specification/cosmos-db/resource-manager/Microsoft.DocumentDB/preview/2019-08-01-preview/privateLinkResources.json:1:1'
    },
    type: 'Info',
    docUrl: 'https://github.com/Azure/openapi-diff/tree/master/docs/rules/1001.md',
    mode: 'Update'
  },
  {
    id: '1007',
    code: 'RemovedClientParameter',
    message: "The new version is missing a client parameter that was found in the old version. Was 'apiVersionParameter' removed or renamed?",
    old: {
      ref: 'file:///home/vsts/work/1/c93b354fd9c14905bb574a8834c4d69b/specification/cosmos-db/resource-manager/Microsoft.DocumentDB/preview/2019-08-01-preview/privateLinkResources.json#/parameters',
      path: 'parameters',
      location: 'file:///home/vsts/work/1/c93b354fd9c14905bb574a8834c4d69b/specification/cosmos-db/resource-manager/Microsoft.DocumentDB/preview/2019-08-01-preview/privateLinkResources.json:174:3'
    },
    new: {
      ref: 'file:///tmp/resolved/specification/cosmos-db/resource-manager/Microsoft.DocumentDB/preview/2019-08-01-preview/privateLinkResources.json#/parameters',
      path: 'parameters',
      location: 'file:///tmp/resolved/specification/cosmos-db/resource-manager/Microsoft.DocumentDB/preview/2019-08-01-preview/privateLinkResources.json:255:3'
    },
    type: 'Error',
    docUrl: 'https://github.com/Azure/openapi-diff/tree/master/docs/rules/1007.md',
    mode: 'Removal'
  },


forward -debug to sbt

-debug is a legitimate command since 0.13.13, but it's been impossible to use it because Bash eats it. This allows log level to be set to debug level. (similar to -warn setting to warn level)
Ref https://github.com/sbt/sbt/pull/2742

Self merging this.


Added Values() and Keys() for Map and a Keys() function for Set

Hi,
i think its useful to have a Keys() function, if you just need a Set to deduplicate items. Reduces the overhead to use Scan()
I have also added Values() and Keys() for Map.

LGTM. Thanks!


Dev environment is unusable - can't fund.

Describe the bug
doing just all fails every single time on my mac.
2023-09-28T03:48:39.742974Z  INFO fund: Manually broadcasting node announcement and waiting for a few seconds...
thread 'main' panicked at 'to be able to fund: Could not verify channel is open. Please wipe and try again', crates/tests-e2e/examples/fund.rs:44:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

To Reproduce
Steps to reproduce the behavior:

Run just all
See error

Expected behavior
Funding should work, it did work for me all the time until recently.

Might be worth pointing out that this is coming from just fund.
The issue is that LND does not find/accept the node announcement of our coordinator.
@holzeis : made it work on his machine and testnet setup. Maybe he can describe his (manual) steps to get it work?

it got fixed for me with #1387 - can you try if it works for you @bonomat @holzeis ?

I'm going to close it, as I am unblocked. if anyone still experiences this on master, please feel free to re-open :-)

it got fixed for me with #1387 - can you try if it works for you @bonomat @holzeis ?

just worked for me as well 🤷♂

it started failing for me again, and after looking into it a bit, it was only due to the peer_alias not being populated 🤔 which has no impact on the ability to use the channel.

Documenting some pitfalls that will fail your faucet payment, but isn't a bug

lnd will set the flag sync_to_graph to false if the hasn't been a new block for quite some time. Mine a few new blocks or use the auto mining script to fix that issue.
lnd will quickly give up on a channel if a payment failed, ensure your are resetting the mission control, before retrying payments.

I'm closing this, as it works on my machine. If it fails for anyone else, please re-open.


Whitelisting failures in the rocm_v2 CI run

Adding a "no_rocm_v2" tag to the following tests
//tensorflow/examples/adding_an_op:fact_test
//tensorflow/examples/adding_an_op:zero_out_1_test
//tensorflow/examples/adding_an_op:zero_out_2_test
//tensorflow/examples/adding_an_op:zero_out_3_test
//tensorflow/examples/speech_commands:freeze_test
//tensorflow/examples/speech_commands:generate_streaming_test_wav_test
//tensorflow/examples/speech_commands:input_data_test
//tensorflow/examples/speech_commands:label_wav_test
//tensorflow/examples/speech_commands:models_test
//tensorflow/examples/speech_commands:train_test
//tensorflow/examples/speech_commands:wav_to_features_test
//tensorflow/examples/tutorials/mnist:fully_connected_feed_test
//tensorflow/examples/tutorials/mnist:mnist_with_summaries_test
//tensorflow/lite/experimental/microfrontend:audio_microfrontend_op_test
//tensorflow/python:contrib_test
//tensorflow/tools/compatibility:test_file_v1_12
//tensorflow/tools/compatibility:tf_upgrade_v2_test

Currently all of the above tests are failing (when run with --config=v2, i.e. in TF 2.0 mode).
This is true both in the upstream TF repo and in the ROCm fork repo.
Adding the "no_rocm_v2" tag to them should exclude them from the CI run, enabling the CI run to pass.

kicking off CI again after a slight change on the Jenkins side.
It seems that you cannot specify more the --test_tag_filters=... option more than once, if you do, the last one wins. My previous Jenkins edit was to add a new --test_tag_filters=-no_rocm_v2 option in addition to the --test_tag_filters=...,-no_rocm,... option already place. The new Jenkins edit is to instead -no_rocm_v2 to the existing --test_tag_filters=... option

jenkins: retest this please

jenkins: retest this please


Add Interest::remove

Closes #1331

Unrelated clippy failure due to single letter variable names in tests.


Stress test with probobuf format?

We want to perform stress test on a http api with pb format, but, how to send http request in protobuf format by locust(instead, jmeter supports pb format) .
Is this the same with uploading file?
`files = {
'image': open('sample.jpg', 'rb'),
}
r = requests.post('http://localhost:5000/', files=files)`

As far as I know, protobuf is just a format for serializing/deserializing structured data - with existing libraries for python - so there shouldn't be any problem using it with Locust.
Exactly how depends on how the server expects the data to get transfered. If it expects it to be transfered as a multipart file upload you would use the files keyword argument (http://docs.python-requests.org/en/master/user/quickstart/#post-a-multipart-encoded-file). However, if I would guess, I would think that it's more likely that the data were to be transfered as raw data in the POST body:
self.client.post("/some/url", data=my_protobuf_data)


flutter support arm architecture arm64 arm32

Use case

Proposal

I can port flutter it to termux android phone tablet

it will be possible to develop on an android phone and a tablet flutter

@ExtinctDrift19
Not sure if I fully understand the proposal because you didn't provide enough details. Currently Flutter supports [armeabi-v7a](https://developer.android.com/ndk/guides/abis#v7a) (ARM 32-bit), [arm64-v8a](https://developer.android.com/ndk/guides/abis#arm64-v8a) (ARM 64-bit), and [x86-64](https://developer.android.com/ndk/guides/abis#86-64)[](https://docs.flutter.dev/deployment/android#test-the-app-bundle) (x86 64-bit).
So what exactly is your proposal here ? Are you looking to have arm support for specific Android phone and tablet ?
Please elaborate.

add installation instructions for termux site flutter.dev

If I understand correctly, you are looking to have Flutter installation steps for termux.com. If so, you'll need to report this issue in flutter/website repo: https://github.com/flutter/website/issues/new?template=1_page_issue.yml&title=[PAGE ISSUE]: 'Install'&page-url=https://docs.flutter.dev/get-started/install/&page-source=https://github.com/flutter/website/tree/main/src/get-started/install/index.md
Closing from here. If you disagree or think this is incorrect, write in comments and I'll reopen it.


trainer fails to present data

Hi @karnigili! Can you help me how to reproduce this?

Hi (thanks for the super quick response)
I am so sorry, just realized that I used dicts instead of lists for the empty entities fields.
THANK YOU.

No problem :)


Individual page preview: layout is confusing for screen reader users

[ ] The tab order on the individual page preview is confusing - it starts with the top section (individual name and location info) then it goes to the buttons on the right, then to the links on the left and then to content.  It would easier to start from links on the left and then go to the content and then the buttons.
[ ] Keep the left side navigation as close as to the top left corner, so they are not missed by the magnifier.
[ ] Edit role doesn't have proper role

@sepidehshahi @greatislander I believe this was resolved by moving the top section (containing name, roles, pronouns, location, and links) to be first in the tab order, and visually move it all the way left.


query parameters in urls

koa-router's url method supports name and parameters. In addition to this, I would like to construct a URL with query parameters, e.g.,
/test?q=abc&number=123

Is it possible to use the url method for it yet? Proper escaping would be nice too.

It's already available using https://github.com/koajs/koa
Check out: https://github.com/koajs/koa/blob/9f80296fc49fa0c03db939e866215f3721fcbbc6/test/request/query.js#L23
router.get('/test', function *(next) {
    var ctx = this;

    console.log(ctx.query.q);
    // => 'abc'
    console.log(ctx.query.number);
    // => 123
});

Thanks for the reply! Do you think the same would be possible for the url method? Right now, I'm using it in the context of
this.status = 303;
this.redirect(router.url('document', doc.document) + '?revision=' + doc._id);

The latter ?revision=... part is the one that been bugging me.

It's not handled
What do you think about:
router.url('document', doc.document, {
    query: {
        revision: doc._id
    }
})

I will try to send a PR tonight

Just what I was looking for.

Hi. Are there any plans on supporting this?

@wachunei No plans that I've seen, but a PR could be opened with some work that matches what was discussed here—seems like there would be support for it.

PR sent, check #396

published at 7.3.0


Tauri v2

Windows:

Crashes when clicking the tray icon, with exit code 0xc000041d, might be similar to https://github.com/tauri-apps/tauri/issues/781 or https://github.com/tauri-apps/tauri/issues/10987
Needs exe / MSI signing

Ubuntu 22.04:

Window decorations, including the close button, don't work right in Wayland. There is a workaround by setting GDK_BACKEND=x11, seems to be a bug in Tao https://github.com/tauri-apps/tauri/issues/10686

### Tasks
- [x] Extract PR to add new Rust projects to `setup-rust` list for Windows
- [x] Correct apt-get prereqs in README files
- [x] Ensure every version has the mark for the Makefile to find it
- [ ] Pin latest Ubuntu 20.04-supporting GUI Client in docs and changelog

This has been shipped.


Vulkan error when trying to compile a pipeline using attached shader

I get the following error when trying to compile a Vulkan pipeline using the shaders stored in this zip: shader_pair.zip
Vulkan ERROR: Code 7060244 : Validation Error: [ UNASSIGNED-CoreValidation-Shader-InconsistentSpirv ] Object 0: handle = 0x55555c32f920, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0x6bbb14 | SPIR-V module not valid: The result pointer storage class and base pointer storage class in OpAccessChain do not match.
  %104 = OpAccessChain %_ptr_UniformConstant_float %792 %uint_0

Next problem is according to tizi:
Structure id 792 decorated as Block for variable in Uniform storage class must follow standard uniform buffer layout rules: member 1 at offset 4 is not aligned to 8


Revert and freeze gradle version to avoid 4.0.0 bug

Released yesterday, the gradle 4.0.0 version causes this compilation error:
```Application build has failed with an error (Could not find org.jetbrains.kotlin:kotlin-stdlib-jdk8:1.3.60-eap-25)````
Source: https://androidstudio.googleblog.com/2019/10/android-studio-40-canary-1-available.html
This pull request reverts the dependency to the last working version.
It is always a good practice to freeze dependencies to achieve reliable builds over time.

Many people are having this issue:
https://stackoverflow.com/questions/58529904/error-could-not-find-org-jetbrains-kotlinkotlin-stdlib-jdk81-3-60-eap-25-in-i
Would be great if this could be merged and released as soon as possible :)

Another pull request aims to solve this problem: #26. Although this is probably a better way to fix it.

Which ever one gets merged, please do it ASAP.

I think this is a better approach than #26.
👍

Change is good. Uses the latest stable version of gradle before 4.0.0. Please merge. Thanks

For the record:
I've sent an email to the plugin owner asking to merge this PR.

@jimbergman You can only review? Can't you merge?

I am not able to merge this. Anybody can review a pull request, but the maintainer has to do the merge. It looks like @chemerisuk hasn't made any commits to GitHub since June. ☹

Hi guys, I think better to set com.android.tools.build:gradle:3.+ because plugin used in different versions of cordova-android. Version com.android.tools.build:gradle:3.5.1 requires gradle 5.1.1+.
@homer-jay do you mind to update the PR?

Duplicates https://github.com/chemerisuk/cordova-support-google-services/pull/26

@chemerisuk thanks for your work :muscle:
Would it be possible to add someone else as a colaborator to this repo to assure the maintenance of this code?
I ask this because according to your github profile it almost seems like you died in June... :cry: so I was afraid we would loose the ability to update this package...
(Settings --> collaborators)
Thanks.


Allow CMake to generate DLL

CMake should have an option to generate the 'shared' DLL in the same way the project generator does.

For now, we'll leave it as being purely the exe, and can have open discussion(as per the new ticket) on if there's merit to breaking down into the various DLLs.


Convert a map to a list of single elements

Sometimes it makes sense to deserialize a map as a list of single items, i.e., Vec<T>.
{
	"id0": {
		"field_a": ...,
		...
	},
	"id1": {...},
	"id2": {...},
}

This could be converted to:
struct Data {
	id: IdType,
	field_a: ...,
	field_b: ...,
}

Prior art: https://crates.io/crates/serde-key-value-vec-map

A slightly different transformation is between a map and a Vec of enums like #375.
The key is the tag of the enum.
Serialize a Vec of externally tagged enums to a map with the map key being the external tag.
vec![
    EnumValue::Int(123),
    EnumValue::String("FooBar".to_string()),
    EnumValue::Int(456),
    EnumValue::String("XXX".to_string()),
    EnumValue::Unit,
    EnumValue::Tuple(1, "Middle".to_string(), false),
    EnumValue::Struct {
        a: 666,
        b: "BBB".to_string(),
        c: true,
    },
],

gets converted into this JSON
{
  "Int": 123,
  "String": "FooBar",
  "Int": 456,
  "String": "XXX",
  "Unit": null,
  "Tuple": [
    1,
    "Middle",
    false
  ],
  "Struct": {
    "a": 666,
    "b": "BBB",
    "c": true
  }
}

This got requested here: https://github.com/serde-rs/json/issues/743

There is an implementation for the first post in #555. You both indicated interest in the feature. If you still need the feature and could leave some feedback at #555, that would be very much appreciated.
@ncfavier @latk


compute sidecar for gateway when service entry is added

When service entry and gateway are added at the same time, service entry is not sent. Regression from this https://github.com/istio/istio/commit/ec1766dd7e315b2e43bb5497e008a8cd36271a9c.

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@ramaraochavali: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
4559a027f060c2bb26350181a0d777a4a9d0fcf5
link
true
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

In response to a cherrypick label: new pull request created: #35298


Couple of t2t-insights-server fixes

Fixed a couple of errors in t2t-insights-server. The configuration example in README.md, missing d3 error and json serialization error.

Hi @haukurb -- thanks for the PR!
Can you let us know what D3 error you are seeing? (image, error log, anything)
Since neither explore-view.html nor explore-view.js seem to be using D3.

@haukurb - thanks again for the PR!!! Sorry for the delays, we had to restructure some things to make this compatible internally. Many thanks again!


Change queue generation functionality

QueueID generation mechanism was changed to fix collision bug when the same data is requested.
The QueueID is now a random UUID instead of the fingerprint of the last entity sent. This way if there is a collision,
like when the end entity ends up being the same, data is still streamed to the client without errors.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

main

PR #24

PR #25   👈

This stack of pull requests is managed by Graphite.

Merge activity

Feb 18, 4:21 AM EST: @raulfrk started a stack merge that includes this pull request via Graphite.


[Release-1.25] Use version.Program not K3s in token rotate logs

Proposed Changes

Log Improvements

Types of Changes
bug fix

Verification
k3s token rotate --token <OLD_TOKEN> --new-token <NEW_TOKEN>

Testing

Linked Issues
https://github.com/rancher/rke2/issues/4891

User-Facing Change

Further Comments

CI is failing due to unrelated reasons. merging


PosixPath

Fixing a PosixPath Error in hdf5db.py

I see that a few .txt reports have been deleted. Was this intentional?


Support for storing only incremental changes for json/jsonb columns

When I enable paper_trail on a model that has a jsonb column - making updates to that column results in the entire object being stored under object_changes. For example with a model called Document that only has one jsonb column data:
d = Document.new
d.data = {a: {b: 1}}
d.save!
d.data["a"]["b"] = 2
d.save!
d.data["a"]["c"] = 1
d.save!
d.versions.last[:object_changes]["data"]
[
    [0] {
        "a" => {
            "b" => 2
        }
    },
    [1] {
        "a" => {
            "b" => 2,
            "c" => 1
        }
    }
]

I'm curious if its possible (if desirable) to only store the deltas - as with very large json/jsonb blobs the storage can become very expensive and also the object_changes don't result in easy to identify changes

I'm curious if its possible (if desirable) to only store the deltas - as with very large json/jsonb blobs the storage can become very expensive and also the object_changes don't result in easy to identify changes

Great question, Ali.  It is not currently possible. The object_changes column is populated directly from ActiveModel::Dirty#changes, which we have no control over. Does ActiveModel::Dirty provide a way to get the deltas for a jsonb attribute?

It would be good to have a Ruby method to diff the objects, but I don't think it makes sense to only store the diff in the database, as it would make restoring from the data more difficult, as well as querying it (in the case of JSONB).

The closest diffing implementation I've seen that suits the requirement is hashdiff. Restoring the data would still be done by the object value but the deltas can still be stored in object_changes in the same way as attribute changes are stored.

I agree with @alisaifee, full data in object while deltas are in object_changes.

Sean makes a good point about the difficulty of restoring from deltas. We'd have to get the entire history of that attribute and "replay" it in ruby, which would make reification expensive and complicated.  And what's the benefit? We save some disk space? Disk space is cheap :)

@jaredbeck I guess I wrongly assumed that you could reify based on the object and applying just the object_changes. But if I'm wrong about that I agree with all your points.

@jaredbeck yes, one of the benefits is indeed saving disk space (though you're right, it is cheap :P). Another benefit is to make displaying the actual changes easier (for instance if you are displaying the paper trail in a form or something.

one of the benefits is indeed saving disk space (though you're right, it is cheap :P).

Yeah, I'm not really concerned about disk space, either. Or rather, it is not a pain point that I've felt. There are other ways to save space, like limiting how many versions you keep.

Another benefit is to make displaying the actual changes easier (for instance if you are displaying the paper trail in a form or something.

That sounds worthwhile, though I'd rather improve the convenience methods that read these data, like VersionConcern#changeset rather than changing the way we write them.

You are right, I think the most important aspect is to be able to clearly communicate the actual changes. Would you be interested in a pull request / collaborating on modifying the convenience method?

Would you be interested in a pull request / collaborating on modifying the convenience method?

Yes, thank you.
Can you help me review the test coverage first? Ideally, the tests should cover all of the major data types, including timestamps with and without zone, and enums. We've had some bugs lately with enums specifically, and we could probably use more test coverage.
Then, I'd like to review the design, or at least how things are named. For example, there are two different processes that are both referred to as serialization.
Sound like a good plan?

FYI https://github.com/palkan/logidze stores only changes.

Thanks for the feedback everyone. I'm going to close this. For the reasons given above, we will not be changing how we store data.

I'd rather improve the convenience methods that read these data (like VersionConcern#changeset) rather than changing the way we write them.

I'm still open to suggestions regarding methods like changeset. Please open new issues with concrete suggestions.

FYI https://github.com/palkan/logidze stores only changes.

logidze sounds really cool, especially using triggers to write to the log. I wish I used postgres at work :(


Scroll current time into view when opened

When I open the app at 2:30pm, I probably want to see what's happening in sessions for 3pm or perhaps 2pm. It would be convenient if the appropriate time block was scrolled into view.

Thanks, we'll consider this UX for next year. Since the show is over, we're not going to change the current behavior now.


Update default parameters

This PR updates the default parameters, and nothing else. @SeaCelo @jdebacker

Hey @rickecon
Thanks for the contribution! I see you were working while presenting again, but I’m going to have to give this one a "no-go" for now. It’s important that we keep the code and documentation focused on actual data, so personal opinions are best left out of the PR.
Let’s keep the good vibes going. Appreciate the effort, and looking forward to your next PR.
Cheers!

Closed for lack of documentation on the changes to the tax code, and for the opinions on cats in the documentation.


Filter Twitter notifications

Twitter has a habit of preceding their page name with a number wrapped in parenthesis representing number of new tweets unseen.  Add universal custom filter option in OScommand before the cropping formatting.
Example:
x = "(5) Twitter - Chromium"
filter(x)
# => "Twitter - Chromium"

This way all the Twitter (and other social networks that follow the same format) can be cleanly logged.
OScommand will have initialize(**kwargs) with an optional :no_notifies parameter to trigger the formatting flag.  This can later be added to command line argument option parser once that is implemented.

Hey @omegahm ,
I'm adding customizable filters and I need to know if the following filter will work
"apple, orange".gsub(/([^,]*)[, ]{1,3}(.*)/, '\2 - \1')
# => "orange - apple"

as the same as your format code
format = ->str {
  app, window = str.split(',')
  "#{window.strip} - #{app.strip}"
}

If you could at least provide an example string of what the Mac ocascript returns I'll have something to test against or experiment with.

The osascript will return the app and window in a comma-seperated string, e.g.: "firefox, (1337) Twitter" which the formatter then flips and strips, so the above will become: "(1337) Twitter - firefox".
Shouldn't you filter on the result from the formatter? Else you'll duplicate your filtering code. The part that does [0..60] should probably be moved further out as well.

The [0..60] is the last thing the Filter class performs.  Everything is moved into a Filter class object.  I just needed a compatible gsub regexp for what you did with your returned Mac string is.

Example:
"firefox, (1337) Twitter".gsub(/([^,]*)[, ]{1,3}(.*)/, '\2 - \1').gsub(/\A ?\(\d+\) ?/, '')
 => "Twitter - firefox"

With my new Filter class I just need to pass in the two regexes as a substitutions parameter.

Yes.

It might blow up terribly if either the app name or window name contains a comma. :smirk_cat:

Haha!  Good point!  Thanks for the feature flaw ;-)

Haha!  Good point!
Just checked and the regex always splits the first comma after the app name so no problems here!

Done #7


⚠ Secret Website 3 has degraded performance

In 0f66039, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 2274 ms

Resolved: Secret Website 3 performance has improved in 1ab489c.


Node provision failing 4.7.0-0.okd-2021-06-13-090745

Describe the bug
Node provision failing with default image.

machine-config-daemon-firstboot.service - Machine Config Daemon Firstboot
Daemon Firstboot...
sed: can't read /etc/yum.repos.d/*.repo: No such file or directory
Running captured: rpm-ostree status --json
 Booted osImageURL:  (47.83.202103251640-0)
Installed Ignition binary version: 2.9.0
 failed to compare MachineConfig: error creating machineConfigDiff for comparison: parsing new Ignition config failed with error: failed to parse Ignition config: parsing Ignition config failed: unknown version.Supported spec versions: 2.2, 3.0, 3.1

Version

4.7.0-0.okd-2021-06-13-090745 deployed to GCP
How reproducible

100% reproducible
Log bundle

Please attach (or upload to the public file sharing service) must-gather archive


Migrate CI to Github actions

Travis CI is no longer running the tests, this PR replaces it by GitHub actions.

Thanks, merged.


Image does not appear

I cannot seem to get the polyfill to work. When viewed in ie8 the background image is not appearing. Any advice you can give would be appreciated.

有人解决这个问题么，我在css中也用了"-ms-behavior: url(css/backgroundsize.min.htc), behavior: url(css/backgroundsize.min.htc ，也执行了，就是页面上是没有任何图片的


Text Collection - Hamburger Menu on Text Collection

As a Bible Translator, I want hamburger menu on the text collection so that I can get my work done effectively.
Description
In PT95 the Text collection window has a menu with Edit, Modify Text collection (add or delete list of resources/projects in the list of texts) and View Menu groups
In PB this is not implemented. Zoom is implemented as part of the kebab menu.

If we will have a hamburger or another form of menu on the tabs is currently under design by the ux team. It might end up differently (e.g. a kebab or meatballs menu on the toolbar)


Experiment with parallel docker build

just testing how this behaves, may need to tune if this works

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: howardjohn
To complete the pull request process, please assign utka
You can assign the PR to them by writing /assign @utka in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

prow/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

no noticable improvement. maybe if we had bigger nodes

@howardjohn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-presubmit-tests-master
3b554be6771e7ecd73e58b620002f08691991c90
link
/test integ-mixer-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


How to support 'REGEXP' operator in laravell

i have written a simple query using "REGEXP" operator it's not working
$comments = new Comment;
$query = $comments::where('title', 'REGEXP', '8183|81600')->get();

It returns all record. It should return only 2 record. i have tested by writing Sql Query
Raw Sql query - SELECT * FROM Test where title REGEXP '8183|81600'; It is working fine.
Please find the attached image, records available in the DB.

Anyone can help about this.
Thanks

@psanjib, show the model definition please. Is the property connection mysql?


Retrieve Nutanix CAPX image only if it is in the bundle

Description of changes:
Nutanix is not added to the release bundle so retrieve it only if it's in the bundle.
This resolves issue with import-images where it fails trying to import an empty image
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/backport release-0.12

/cherry-pick release-0.12


[Suggestion] Ability to keep DialogActions and DialogTitle visible at all time

Currently dialog actions and title scroll with the content. This can confuse users when the content is long. Imagine you display Terms of Service inside a dialog. User has to scroll all the way to the bottom of text to find the confirm button. My suggestion is to introduce a sticky boolean attribute for both DialogTitle and DialogActions of a dialog to keep them always visible.

@semiadam I'm closing this issue to move the conversation to #9602.


Itunes backup is just a folder with more folders - how to open?

Hi, sorry to be a total newb but my itunes backup is just a folder with many folders inside 0-99 etc. How can I open this with the explorer?

@zrodrps Which device and iOS version do you have?

Iphone 6s 15.8.2

Additionally to all the folders, there should also be about 4 files in the backup directory.
If it is saved in the default location, the program should automatically find and show it. If the sidebar is empty, you can manually open it from the File menu by selecting the Manifest.db file in the backup directory.

Thanks I got it now. I saw those files eventually and found out I had to double click, not single, on the folders in the explorer to open up in the right pane :) Sry to disturb and thanks for replying and making the app.


kitti training is not correct

Hi,
Did you use "train.py" to train a model on SceneFlow? They share the same code.


Glint doesn’t support multiple Typescript extends

The Ember Typescript docs suggest enabling TypeScript’s strictest support by adding @tsconfig/strictest before the ember config at https://guides.emberjs.com/release/typescript/additional-resources/faq/#toc_strictness
This breaks Glint as seen in #662

unstable Glint (main) has this same problem


How to manually rotate the turntable

How to manually rotate the turntable

Hey @LiJinJinJIn,
unfortunately, I can't help without having more information about your issue. Could you please provide the code you are using and explain in detail what you are trying to achieve?


A error occurred while executing 'make build'.

###When 'make build' reaches the command 'curl -sSL https://install.python-poetry.org/ | python3 -', the command cannot be executed and does not terminate, the reason is unknown.
lx@liuxin:/mnt/d/workspace/ai_project/OpenDevin$ sudo make build
Building project...
Pulling Docker image...
Using default tag: latest
latest: Pulling from opendevin/sandbox
Digest: sha256:486e3da1d7c8ec54a2e3269071eed9b91bc75b82ca5d1ac1760d33883c39e575
Status: Image is up to date for ghcr.io/opendevin/sandbox:latest
ghcr.io/opendevin/sandbox:latest

What's Next?
  1. Sign in to your Docker account → docker login
  2. View a summary of image vulnerabilities and recommendations → docker scout quickview ghcr.io/opendevin/sandbox
Installing Python dependencies...
Retrieving Poetry metadata

What's Next?

Sign in to your Docker account → docker login

I think you might need to sign into docker. I don't normally see this when I run make build...
:~/OpenDevin$ make build
Building project...
Pulling Docker image...
Using default tag: latest
latest: Pulling from opendevin/sandbox
Digest: sha256:486e3da1d7c8ec54a2e3269071eed9b91bc75b82ca5d1ac1760d33883c39e575
Status: Image is up to date for ghcr.io/opendevin/sandbox:latest
ghcr.io/opendevin/sandbox:latest
Installing Python dependencies...
Requirement already satisfied: pipenv in /home/quimbo/miniconda3/lib/python3.11/site-packages (2023.12.1)
Requirement already satisfied: certifi in /home/quimbo/miniconda3/lib/python3.11/site-packages (from pipenv) (2024.2.2)
Requirement already satisfied: setuptools>=67 in /home/quimbo/miniconda3/lib/python3.11/site-packages (from pipenv) (68.2.2)
Requirement already satisfied: virtualenv>=20.24.2 in /home/quimbo/miniconda3/lib/python3.11/site-packages (from pipenv) (20.25.1)
Requirement already satisfied: distlib<1,>=0.3.7 in /home/quimbo/miniconda3/lib/python3.11/site-packages (from virtualenv>=20.24.2->pipenv) (0.3.8)
Requirement already satisfied: filelock<4,>=3.12.2 in /home/quimbo/miniconda3/lib/python3.11/site-packages (from virtualenv>=20.24.2->pipenv) (3.13.3)
Requirement already satisfied: platformdirs<5,>=3.9.1 in /home/quimbo/miniconda3/lib/python3.11/site-packages (from virtualenv>=20.24.2->pipenv) (3.10.0)
Installing dependencies from Pipfile.lock (90ed62)...
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
Setting up frontend environment...
Detect Node.js version...
Current Node.js version is 20.12.1, corepack is supported.
Lockfile is up to date, resolution step is skipped
Already up to date

><EMAIL_ADDRESS>prepare /home/quimbo/OpenDevin/frontend
> cd .. && husky install frontend/.husky

husky - Git hooks installed
Done in 1.3s

It shouldn't be related to Docker, as 'docker pull' has already completed. It stops at this step 'Installing Python dependencies...'

I think the problem is with curl command. I solved it by installing the latest version of curl with choco install curl. I'm now blocked at: "Building project..."
"Pulling Docker image..."
Using default tag: latest
latest: Pulling from opendevin/sandbox
Digest: sha256:486e3da1d7c8ec54a2e3269071eed9b91bc75b82ca5d1ac1760d33883c39e575
Status: Image is up to date for ghcr.io/opendevin/sandbox:latest
ghcr.io/opendevin/sandbox:latest
What's Next?

Sign in to your Docker account → docker login
View a summary of image vulnerabilities and recommendations → docker scout quickview ghcr.io/opendevin/sandbox
"Installing Python dependencies..."
Retrieving Poetry metadata

The latest version (1.8.2) is already installed.
Installing dependencies from lock file
No dependencies to install or update
Installing the current project: opendevin (0.1.0)
"Activating Poetry shell..."
"Installing pre-commit hooks..."
pre-commit installed at .git\hooks\pre-commit
"Setting up frontend environment..."
"Detect Node.js version..."
Current Node.js version is 21.7.2, corepack is supported.
-f non atteso.
make: *** [Makefile:27: build] Error 255

Installing Python dependencies...
Retrieving Poetry metadata
The latest version (1.8.2) is already installed.
make: poetry: No such file or directory
make: *** [Makefile:20: build] Error 127

Please see this comment and try setting the path.


Safer extract

If the python script fails then you generally don't want to carry on and run the remaining git commands, so instead we should exit.

Looks good to me


Two resources have incorrect post dates causing a bug in the Year Posted filter

The dataset for Green Power Projects had two installations where Date Posted was formatted MM/DD/YY instead of MM/DD/YYYY, which resulted in the Year being treated as 0016 instead of 2016. As a result, the Year Posted filter universally includes the earliest years, plus everything in between. I cannot adjust the Year Posted in Admin, so I believe this will need to be fixed by IT to resolve the issue.
The resources that need to be adjusted:
https://hub.aashe.org/browse/greenpowerproject/17426/539-kW-Rooftop-Array-Res-Rec
https://hub.aashe.org/browse/greenpowerproject/17770/22-kW-Rooftop-Array-Partners-I-Building
It's not clear why all the years after the earliest (0016) are included as options, but if you select one and apply the filter, there are zero resources. Would be good to set the filter up so that only years where resources are applied show up. This appears to be how the filters work under "Year created, published, or presented".

@rerb Do you think you could fix the date posted manually on these two? Monika and I can't change date posted through the regular admin function but I imagine it should only take you a few minutes

https://docs.google.com/spreadsheets/d/1X9YYA86om5ndzWBdDo20aUavQxgsmKvePQMtyHcPUoU/edit#gid=1783883752
See row 5, Column AQ for example of formatting issue in EDITS: Solar and Wind Green Power Projects

I updated the dates for those entries directly via the database. Still working on the year filter, looks like some more rows need attention.

The Year Posted filter looks correct on production now.
Tech note: I had to restart the web services in order for the filter to be correct.  Not sure where the content is cached for that part of the page, but I had expected it to get flushed out by now.

Looks great! The final piece for this particular ticket: Can we order the years for Year Posted and Year created, published, or presented to be consistent in terms of chronology? The former currently displays oldest first, while the latter displays earliest first.
If this is a relatively quick fix, great. But if it's particularly time-intensive, it may not be worth the trouble.
Thanks!


The "Settings" table is mostly "undefined" / "N/A" sinec February

If you click on the version number in the page header, a table comes up with the version / date / Chromium version. Since v2.1.1 in February, most (but not all) of the Chromium versions are listed as "undefined"
There's also an item at the top of the table right now that says "main - N/A - N/A"

(1) The undefined values indeed are bugs: once they are results of a not standardized release note process for Chromium version rolling (see below), and a lack of error handling on pptr.dev site. The cause is:
pptr.dev uses the following regex to parse the versions:
const match = release.releaseNotes.match(/Chromium\s+(\d+\.\d+.\d+.\d+)\s*\((r\d{6})\)/i);

(source: src/pptr/PPTRProduct.js#L102)
The format of the Chromium version rolls has changed in the release notes lately:
While the regex matches: "Chromium 86.0.4240.0 (r800071)" (v5.3.0)
But it won't match: "chromium: roll Chromium to r848005" (v7.0.0)
It was intentional back then that it sometimes work sometimes not (there is even a historical else if condition for such cases), anyway it would be correct to show N/A (not available) instead of undefined.
I will create a pull request to fix this and also raise a suggestion for the core team to include the full Chromium version in future releases (that could be in the CONTRIBUTING.md's Rolling new Chromium version section).
(2) The item on top is by purpose showing N/A. That is the documentation on the main (previously master) branch, which doesn't have an exact release date, or a specific Chromium version. That is the all-time state of the main branch.


Mentioned gh_color_mode in .md

Why:
Closes #11491

What's being changed:

Check off the following:

[ ] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

edited by maintainer to correctly link the issue

@shreya024 Thanks so much for opening a PR! I'll get this triaged for review ⚡

Okay thank you

Hi @shreya024! I'm really sorry but It looks like some crossed wires have lead to this feature already being documented. Take a look at the "Specifying the theme an image is shown to" section on the same page.
I'll have to close this (and the associated issue) but again, I'm really sorry. Your changes looked great and if it wasn't for this already being documented, I'd have been delighted to merge them! I hope you'll contribute again.


Add support for recursive calls to oe_once/pthread_once.

This change addresses one scenario I encountered when integrating the OpenSSL library into Open Enclave: I noticed my enclave hanging during the call to oe_initialize_openssl (which calls pthread_once), where the hanging never terminated. This hang was partially due to this local static lock:
static oe_spinlock_t _lock = OE_SPINLOCK_INITIALIZER;

This is an issue for OpenSSL because when invoking pthread_once to initialize OpenSSL's library, OpenSSL itself will also call pthread_once on several of its internal initialization functions. Our invocation of pthread_once will acquire the spinlock "_lock", and then when OpenSSL's pthread_once invocations attempt to acquire this lock, they will hang forever. Here is what a backtrace looks like without this change:
(gdb) run
Starting program: /home/johnkord/openenclave/build/tests/crypto/enclave/host/cryptohost ./enc/cryptoenc
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
=== begin _test_asn1_parsing()
^C
Program received signal SIGINT, Interrupt.
oe_spin_lock (spinlock=0x7ffff25a464c <oe_once._lock>) at /home/johnkord/openenclave/enclave/core/sgx/spinlock.c:43
43              while (*spinlock)
(gdb) where
#0  oe_spin_lock (spinlock=0x7ffff25a464c <oe_once._lock>) at /home/johnkord/openenclave/enclave/core/sgx/spinlock.c:43
#1  0x00007ffff228f4f0 in oe_once (once=0x7ffff25a12f4 <base>, func=0x7ffff2120a80 <ossl_init_base_ossl_>) at /home/johnkord/openenclave/enclave/core/sgx/once.c:22
#2  0x00007ffff225f846 in oe_pthread_once (once=0x7ffff25a12f4 <base>, func=0x7ffff2120a80 <ossl_init_base_ossl_>) at /home/johnkord/openenclave/enclave/core/pthread.c:97
#3  0x00007ffff20cdf76 in pthread_once (once=0x7ffff25a12f4 <base>, func=0x7ffff2120a80 <ossl_init_base_ossl_>)
    at /home/johnkord/openenclave/include/openenclave/corelibc/bits/pthread_once.h:10
#4  0x00007ffff214a986 in CRYPTO_THREAD_run_once ()
#5  0x00007ffff212059d in OPENSSL_init_crypto ()
#6  0x00007ffff209ca78 in _initialize () at /home/johnkord/openenclave/enclave/init.c:13
#7  0x00007ffff228f57f in oe_once (once=0x7ffff259f3f0 <_once>, func=0x7ffff209ca60 <_initialize>) at /home/johnkord/openenclave/enclave/core/sgx/once.c:27
#8  0x00007ffff225f846 in oe_pthread_once (once=0x7ffff259f3f0 <_once>, func=0x7ffff209ca60 <_initialize>) at /home/johnkord/openenclave/enclave/core/pthread.c:97
#9  0x00007ffff20cdf76 in pthread_once (once=0x7ffff259f3f0 <_once>, func=0x7ffff209ca60 <_initialize>) at /home/johnkord/openenclave/include/openenclave/corelibc/bits/pthread_once.h:10
#10 0x00007ffff209ca4b in oe_initialize_openssl () at /home/johnkord/openenclave/enclave/init.c:20
#11 0x00007ffff208cf67 in oe_cert_read_pem (cert=0x7ffff2de0820, pem_data=0x7ffff2590980 <_CERT>, pem_size=1351) at /home/johnkord/openenclave/enclave/cert.c:464
#12 0x00007ffff2070acf in _test_asn1_parsing () at /home/johnkord/openenclave/tests/crypto/asn1_tests.c:337
#13 0x00007ffff20708f9 in TestASN1 () at /home/johnkord/openenclave/tests/crypto/asn1_tests.c:368
#14 0x00007ffff2082cb9 in TestAll () at /home/johnkord/openenclave/tests/crypto/tests.c:9
#15 0x00007ffff206f1fd in test () at /home/johnkord/openenclave/tests/crypto/enclave/enc/enc.c:47
#16 0x00007ffff208351c in ecall_test (input_buffer=0x7ffff25e0790 "", input_buffer_size=16, output_buffer=0x7ffff25e07a0 "", output_buffer_size=16, output_bytes_written=0x7ffff2de0c78)
    at /home/johnkord/openenclave/build/tests/crypto/enclave/enc/crypto_t.c:50
#17 0x00007ffff22675cf in _handle_call_enclave_function (arg_in=140737488347080) at /home/johnkord/openenclave/enclave/core/sgx/calls.c:326
#18 0x00007ffff22661b7 in _handle_ecall (td=0x7ffff2de6000, func=2, arg_in=140737488347080, output_arg1=0x7ffff2de0fc8, output_arg2=0x7ffff2de0fc0)
    at /home/johnkord/openenclave/enclave/core/sgx/calls.c:432
#19 0x00007ffff2265b59 in __oe_handle_main (arg1=281483566645248, arg2=140737488347080, cssa=0, tcs=0x7ffff2de2000, output_arg1=0x7ffff2de0fc8, output_arg2=0x7ffff2de0fc0)
    at /home/johnkord/openenclave/enclave/core/sgx/calls.c:861
#20 0x00007ffff229765b in oe_enter () at /home/johnkord/openenclave/enclave/core/sgx/enter.S:162
#21 0x0000000000428cb1 in __morestack () at /home/johnkord/openenclave/host/sgx/linux/enter.S:95
#22 0x000000000040af37 in _do_eenter (enclave=0x67f100, tcs=0x7ffff2de2000, aep=0x428b24 <OE_AEP>, code_in=OE_CODE_ECALL, func_in=2, arg_in=140737488347080, code_out=0x7fffffffdde0,
    func_out=0x7fffffffddde, result_out=0x7fffffffdddc, arg_out=0x7fffffffddd0) at /home/johnkord/openenclave/host/sgx/calls.c:231
#23 oe_ecall (enclave=0x67f100, func=2, arg=140737488347080, arg_out_ptr=0x7fffffffdfc0) at /home/johnkord/openenclave/host/sgx/calls.c:669
#24 0x000000000040bd65 in _call_enclave_function (is_internal_call=false, enclave=0x67f100, function_id=0, input_buffer=0x68ccf0, input_buffer_size=16, output_buffer=0x68cd00,
    output_buffer_size=16, output_bytes_written=0x7fffffffe1a8) at /home/johnkord/openenclave/host/sgx/calls.c:748
#25 0x000000000040bb3a in oe_call_enclave_function (enclave=0x67f100, function_id=0, input_buffer=0x68ccf0, input_buffer_size=16, output_buffer=0x68cd00, output_buffer_size=16,
    output_bytes_written=0x7fffffffe1a8) at /home/johnkord/openenclave/host/sgx/calls.c:775
#26 0x0000000000408011 in test (enclave=0x67f100) at /home/johnkord/openenclave/build/tests/crypto/enclave/host/crypto_u.c:67
#27 0x0000000000407aec in main (argc=2, argv=0x7fffffffe3d8) at /home/johnkord/openenclave/tests/crypto/enclave/host/host.c:58

The solution to this problem was designed by @anakrish and we both pair-programmed it earlier this year. In short, this implementation uses the oe_once_t (i.e. pthread_once_t) variable as the spinlock instead of a local static spinlock, and it uses the atomic function __sync_val_compare_and_swap to handle that variable safely.
This solution seems logical to me, but I'm mostly inexperienced when it comes to low level locks like this, and I've never used pthread_once before this change. So definitely, please point out if any invalid assumptions that have been made.
Questions I have:

Is OE_ATOMIC_MEMORY_BARRIER_RELEASE in the right location? Originally, I had it inside one of the conditions, but I don't know exactly what that operation does. It seems logical that if each potential thread invokes the ACQUIRE operation, it should probably also invoke the RELEASE, but I have no idea. Double check me here, please :)
Is there any harm in using a pthread_once_t variable like this? If we can't, then I'm not really sure how to solve this problem, as we can't extend on the pthread_once_t type with oe_once_t, because OpenSSL allocates/manages the memory of their own pthread_once_t variables. I assume other third party libraries would also have the same expectations
Are there any better atomic functions to call besides this __sync_val_compare_and_swap ? Here is the reference we used when designing/implementing this: https://gcc.gnu.org/onlinedocs/gcc-7.4.0/gcc/_005f_005fsync-Builtins.html . These atomic functions are referred to as "legacy" now, so there are probably modern functions we can invoke instead.

Thanks so much, Anand. I'll incorporate your suggested changes!

bors r+

bors r+

bors r-
I'd like to wait for Anand and Akash to finish their discussion before merging this, in case they find anything that needs to change!

It needs to be decided today. If its not in it has to be out.
My impression is anands suggestions could easily be applied later.

Is there a use case where this fails?

@akash, could you resolve this this afternoon? We are trying to get a release out and I suspect we want this change to be in, rather than pushed to 0.7

bors r+


Guest can't split remote pane and causes avatar to disappear

Description
Guest can't split remote pane and causes avatar to disappear
Steps to Reproduce

Join a portal as a guest
On the shared buffer click split down.

Expected behavior:
Splitting works correct or shows an error?
Actual behavior:
Opens an empty pane.  When you close the pane and go back to the remote buffer the avatar on the right is gone.   If you switch tabs back and forth it comes back.

Reproduces how often:
100%
Versions
Atom    : 1.23.0
Electron: 1.6.15
Chrome  : 56.0.2924.87
Node    : 7.4.0

@ungb: Unless I'm misunderstanding, the split pane behavior and the disappearing avatars can be observed at the same time, but they're separate issues. I'll try to explain:

Split panes - In https://github.com/atom/teletype/pull/83, we intentionally added logic to prevent guests from splitting panes. In #83 we said:

We may revisit this decision in the future. Let's see what kind of feedback we get after the release, and we can assess the importance of split panes relative to other feature requests and the rest of the real-time collaboration roadmap.

Can I talk you into removing the avatar-related aspects from this issue? (I'll try to explain why below.) Then, we can use this issue to track guests splitting panes as an enhancement request.

Visibility of site position avatars - Currently, we only show the site position avatars when the active pane item is an editor associated with a portal. From RFC-001:

When viewing an editor associated with a portal, each participant sees the avatars for the other portal participants (just as they did prior to this RFC). As a host, when your active pane item is a local editor (i.e., an editor that you're sharing in your portal), the editor shows the avatars for the other portal participants. As a guest, when your active pane item is a remote editor (i.e., an editor that you're viewing from the host's portal), the editor shows the avatars for the other portal participants.

In the gif above, the bottom pane is focused and empty. Since the focused item is not an editor associated with a portal, the site position avatars are hidden. This behavior is not specific to split panes. If you were to focus another pane item (e.g., the settings view), that would also hide the site position avatars.
If you think we should change this behavior, would you mind opening a separate issue describing the motivation for the change?

@jasonrudolph, the thing is if you close the bottom empty pane and the only pane open is the 1 buffer and no other tabs this can lead to a confusing experience.  The tab that is focused is the shared buffer.

see below after closing the empty pane.
If you try to split pane on the tab, this no-ops and nothing happens.  This only works if you right click inside the buffer and split pane there.


Karabiner 14.13.0 installs Karabiner DriverKit VirtualHIDKeyboard 1.7.0 seems to break kmonad

I'm only just getting started with configuring kmonad so still relying on Karabiner right now.
I updated it yesterday and it forced me to restart my machine so I guess there were some low level changes.
After restarting I see the VirtualHIDKeyboard is showing 1.7.0. If I try to run kmonad I see the message connected but no keyboard inout works. I use my mouse to shutdown the iTerm running kmonad and disconnecting and reconnecting my keyboard gets it working again.
I did build against the new version of Karabiner, with this command:
 stack build --flag kmonad:dext --extra-include-dirs=c_src/mac/Karabiner-DriverKit-VirtualHIDDevice/include/pqrs/karabiner/driverkit:c_src/mac/Karabiner-DriverKit-VirtualHIDDevice/src/Client/vendor/include

I am on the very latest Apple release Sonoma 14.2 which I also upgraded yesterday but I think the Karabiner update is the more likely issue.
Running
 defaults read /Applications/.Karabiner-VirtualHIDDevice-Manager.app/Contents/Info.plist CFBundleVersion

Shows 3.1.0
No complaints, I know I shouldn't have upgraded. Just wanted to put this out there in case it helps someone else before they break their install.

This sounds like: https://github.com/kmonad/kmonad/pull/716#issuecomment-1854622531 See there for more (and a potential fix!)


JAV-88 added pojo tests

added pojo tests to verify highway endpoints only

Coverage increased (+0.2%) to 85.193% when pulling 48af3e40c8a0aec32e66b8e01b76e77cfd6c85ef on eric-lee-ltk:JAV-88_pojo_tests into 2248b887d65b607b95bee23904c807372ed5284e on ServiceComb:master.

please do a git rebase

Coverage decreased (-0.03%) to 85.193% when pulling c26ba5326547921bf0cbd4eedbf7550f13ed0cc4 on eric-lee-ltk:JAV-88_pojo_tests into ace8b8d26016a8933420cca061b7425be14caddf on ServiceComb:master.

Coverage decreased (-0.03%) to 85.193% when pulling 51dfc85a94025b8e7dd6ee77600a1ebdae33069b on eric-lee-ltk:JAV-88_pojo_tests into ace8b8d26016a8933420cca061b7425be14caddf on ServiceComb:master.


Np/new provider arden

Description
This PR adds the Arden OIDC provider .
Test plan
The following steps were taken to test the new integration:

Initially ran cargo test -p sui-swarm-config, but not all tests passed.
Reviewed the snapshot using cargo insta review and proceeded with the test process.
Re-ran cargo test -p sui-swarm-config as per the guide, and all tests passed successfully on the second run.

to test this locally, use the script attached in this pr: https://github.com/MystenLabs/sui/pull/19311

fyi @1NickPappas a test is failing so I'll rebase to main, which I think we ll resolve the failing test


ISPN-7808 Upgrade to mockito-core 2.7.21

https://issues.jboss.org/browse/ISPN-7808

Fix JpaStoreIT failures
Replace usages of deprecated mockito API
Replace any(Class) with any() or isNull() where necessary
Add a Mocks utility class to help when delegation is needed
but Mockito.spy() doesn't work

Pushed to master, thanks @danberindei


Deprecate all botframework-config exports

Fixes #2444

Pull Request Test Coverage Report for Build 171710

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.001%) to 85.014%

Totals

Change from base Build 171697:
-0.001%

Covered Lines:
15928

Relevant Lines:
17881

💛  - Coveralls


Testing Spotlight Elements to display OAS v3

Fixes https://github.com/3scale-labs/kamrad/issues/6
Testing Spotlight Elements
It comes in 2 flavors:
html
Pros:

It's easy to use, from CDN.
"Send Request" feature (buggy)

Cons:

Small community
Includes "Powered by Spotlight" backlink
Most advanced features require subscription

React (not working with React 17)
Pros:

None (package is broken)

Cons:

React package is broken, doesn't work with React 17 (see issue)

Issues found (React version):
Trying to install:
npm install @stoplight/elements@beta

It fails with error:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@stoplight/elements
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   77 more (@fortawesome/react-fontawesome, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@stoplight/mosaic-code-editor/node_modules/react-simple-code-editor
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@stoplight/mosaic-code-editor
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@stoplight/elements-core
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!       node_modules/@stoplight/elements
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /Users/damian/.npm/eresolve-report.txt for a full report.

npm ERR!      /Users/damian/.npm/_logs/2021-06-18T15_45_50_346Z-debug.log

How to test
hugo server

Go to: http://localhost:1313/posts/oas-spotlight-elements/

This example uses the Pet Store Spec, but the Send Request feature fails.
The servers in the spec are:
"servers": [
    {
      "url": "/api/v3"
    }
  ],

It replaces the server with the local server:
http://localhost:1313/api/v3

Go to: http://localhost:1313/posts/oas-spotlight-elements-2/

This example uses another spec, with servers:
"servers": [
    {
      "url": "{scheme}://developer.uspto.gov/ds-api",
      "variables": {
        "scheme": {
          "description": "The Data Set API is accessible via https and http",
          "enum": [
            "https",
            "http"
          ],
          "default": "https"
        }
      }
    }
  ],

In this case, "Send Request" doesn't fails

Related PR's:
Testing Swagger-ui
Testing Redoc

Too bad about the bug, they'll probably fix it soon. They've also told us about a workaround that is downgrading to npm 6 or using yarn.

That's how it's rendered. Is it the same for you?

@didierofrivia
I was able to use the react flavor:

Using yarn (to avoid the issue with npm)
Using webpack instead of ESBuild
We need to install several packages to satisfy all required dependencies

Check this commit.
To test:
rm -rf node_modules && yarn install

yarn start

That's how it's rendered. Is it the same for you?

That's because of a conflict with css, between spotlight and the hugo theme.
Using the "stacked" layout of spotlight works fine.

Closed in favor of https://github.com/3scale-labs/kamrad/pull/10


Scaffold, like in Android compose

Hi,
do you plan something like Scaffold in android compose?

At the moment there are no plans for application/layout components in this library.

i heavily think there should be. if/when i build a sveltejs wrapper, and mwc doesn't  have them, i'll have to make my own.


fix: fixes wrong import path

Fixes this and the fact that the Component isn't typed (props do not show up in VS Code)

Please Fix the Lint issue. Recommend use of prettier

@lohenyumnam i don't understand this linting issue. I use default prettier configuration.
export const TruncatedTextView:FC<TruncatedTextViewProps> = (props) => {

btw, this is the recommended way to type a component with props

https://github.com/typescript-cheatsheets/react#function-components
U can read about it more here.

@lohenyumnam thanks for the update! will remove RC on my codebases


user.licenseType doesn't talk about Anonymous users

user.licenseType doesn't talk about Anonymous users which is mentioned in In-Meeting getContext from Teams client library.

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

ID: 8dfa1a29-bcf4-0cc5-ae3a-b185a00fd7bc
Version Independent ID: c68181e1-151b-fc78-2671-fe9b397b702e
Content: Get context for your tab - Teams
Content Source: msteams-platform/tabs/how-to/access-teams-context.md
Service: msteams
GitHub Login: @surbhigupta
Microsoft Alias: lajanuar

@Nivedipa-MSFT - Please check and suggest the changes that needs to be updated in the documentation.

@surbhigupta12 - Could you please add the Anonymous value in below user.licenseType value.

Document link to update: https://learn.microsoft.com/en-us/microsoftteams/platform/tabs/how-to/access-teams-context?tabs=Json-v2%2Cteamsjs-v2#get-context-by-using-the-microsoft-teams-javascript-library


Collect memory usage after import. Added example on redis client integration

The following PR allows the client implementations to report memory usage metrics at the end of import stage.
It can also be used to add extra info on the post upload stage.
As an example, on the redis client, we're preserving both the full memory usage also, but all the index info that contains the breakdown of memory usage per component.

Nice addition. But it should be added for all the engines for it to make sense. But most engines don't provide RAM info out of the box so we need to extract from the Docker container.


Increase nextjs to version 12.0

Incorrect way of proposing changes, will follow CONTRIBUTING guide.

FYI – Next 12 is supported in the latest releases.


Getting JetBrains to natively support nix

Issue description
I would love for JetBrains to natively support nix. Right now, everything other than using the IDE is jarring, such as running remote-dev-server.sh for Gateway development or projector-installer to run remote-IDEs, having DataSpell be broken, and not being able to change IDEs' PATH when the shell updates
Related Issues:

JetBrains  Gateway
JetBrains Projector
JetBrains DataSpell

I have created a YouTrack issue to request for Nix integration, I would appreciate it if our community would increase the likes to allow to show JetBrains its a high-demand feature so they would not push nix to the back of the backlog.
Issue: Jetbrains YouTrack Issue

I'm all for it !

They won't. They can't even support XDG config convention while there were numerous requests over the years.


Misleading description of GetBySystemId(Guid)

"The GetBySystemId(Guid) gets the SystemId for a record" is typed, when the "GetBySystemIdMethod" uses the SystemId to get a record - this description has it the other way around
Edit:
This is related to https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-table-object#systemid
I thought the issue would be linked automatically, my bad.

Thanks for catching this, will be fixed with the next doc refresh.


Some questions and suggestions for this software

The author made an excellent software. After I tried the genome I was interested in, the accuracy of the software for centromere prediction was indeed much higher than that of the software I used before. However, there were some defects in the use of the software.

Because some genomes are large and the prediction time is long, the prediction of chromosome centromere should be carried out as a whole genome. Whether the prediction can be made separately for each chromosome every day has any influence on the result.

The output result of the software is the output path and result name specified by the software. If I have multiple genomes that want to run de at the same time, how should the software be used? Can I add a name prefix to the result for differentiation?In the era of the pan-genome, I think this is very necessary

Thank you for your great suggestions! We will consider making improvements in the next version. We will name the result files with the species name and try to improve the software's efficiency.
At 2024-08-19 11:28:40, "jwli" @.***> wrote:
The author made an excellent software. After I tried the genome I was interested in, the accuracy of the software for centromere prediction was indeed much higher than that of the software I used before. However, there were some defects in the use of the software.
Because some genomes are large and the prediction time is long, the prediction of chromosome centromere should be carried out as a whole genome. Whether the prediction can be made separately for each chromosome every day has any influence on the result.
The output result of the software is the output path and result name specified by the software. If I have multiple genomes that want to run de at the same time, how should the software be used? Can I add a name prefix to the result for differentiation?In the era of the pan-genome, I think this is very necessary
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


Enum fix

Fix for #658 including test

@dsyme Ok, I'll take a look at the suggestions a bit later in the week.

I'll merge now, since the test case is fine and the cleanup is easy later


Whenever we create a new UniTensor, provide an optional argument to initialize the name.

Now we can do this to initialize UniTensors' name:
A = cytnx.UniTensor(cytnx.ones([2,2,2]), name="A", labels=["alpha","beta","gamma"])
B = cytnx.UniTensor(cytnx.ones([2,2]), name="B", labels=["beta","delta"])
C = cytnx.UniTensor(cytnx.ones([2]), name="C", labels=["gamma"])

But when we do this
AB = cytnx.Contract(A, B)

If we want AB to have the name "AB", we need to do it separately.
I would suggest that whenever we create a new UniTensor, we provide an optional argument to initialize the name. For example
AB = cytnx.Contract(A, B, name="AB")

I think the best way is to let Unitensor.set_name() return self,
So one can do chain action like

C = contract(A,B).set_name("c")

Thanks. I think Unitensor.set_name() can do the job.


contributor docs: Clarify how to claim a mobile issue

The existing text says to post a GitHub comment "saying that you'd like to work on" the issue.  A lot of new contributors, understandably, take that literally -- they just say they'd like to work on the issue, with no further information.
In particular they don't give any evidence that they've taken the steps we prescribe in the preceding section, of figuring out what code is involved and how they'll approach the problem before they claim it. When I reply asking for that information, very often they haven't done those steps... while sometimes they have, and just hadn't put together from context that that would be a good thing to communicate.
So spell that out explicitly.  Hopefully this will elicit smoother communication from the contributors who have done that work; and for those who haven't, hopefully it'll help redirect them to go back and do it.
Also expand on the instruction not to spam.

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Looks great, let's try it!

Merged, thanks @gnprice!


[Feature Request]: Feature Selection for Machine Learning with Genetic Algorithm

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description

Data Collection: Use an existing dataset with multiple features.
Initialize Population: Create an initial population of feature subsets.
Fitness Function: Define a fitness function based on model performance (e.g., accuracy, F1 score).
Selection: Select the best feature subsets for crossover.
Crossover: Combine feature subsets to create new subsets.
Mutation: Introduce small changes to feature subsets to maintain diversity.
Evaluation: Assess the performance of the selected feature subsets on the model.

Use Case
This project uses a genetic algorithm to perform feature selection for a machine learning model. The goal is to identify the most relevant features that contribute to model performance.
Benefits
No response
Priority
High
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC contributor
[X] I want to work on this issue
[X] I'm willing to provide further clarification or assistance if needed.

@sanjay-kv pls assign it me


Error in compile when running example rat

Hi brian:
I tried to install matlabstan following the instructions on wiki  to my windows system(cmdstan 2.31.0 from cmdstanr, MatlabProcessManager and matlabstan from your project).   I also modified the code StanModel.m to make it work on windows
But I still got error message when trying to run example file rat.m
The error messages are as follows:
Error using StanModel/compile (line 906)
compile: 'cut'  is not an internal or external command, nor a runnable program
compile: or batch file
compile: 'cut'  is not an internal or external command, nor a runnable program
compile: or batch file
compile: INFO: The file could not be found in the mode provided.
compile: process_begin: CreateProcess(NULL, expr >= 8, ...) failed.
compile: mingw32-make: *** No rule to make target 'E:/MATLAB'。 Stop。
Error in StanModel/sampling (line 736)
self.compile();
Error in stan (line 138)
fit = model.sampling(p.Unmatched);
Error in rats (line 20)
fit = stan('file','rats.stan','data',rats_dat,'verbose',true);
Could you please help me to resolve this problem?
Best,
Amos

Similar problem here!


Fix issue with import aliases in grpc gateway patch

Update the gRPC gateway patch to initialize the generator at the same location as before. Update the calculation of the fully-qualified service name to match the previous algorithm.

Will discuss further w/ the team on this.

Proposed fix(es)
https://github.com/bufbuild/grpc-gateway/pull/1
https://github.com/bufbuild/plugins/pull/575


[Bug report]:

Platform
Desktop
Version
2.0.1
Description
Thu, 05 Oct 2023 17:51:59 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Thu, 05 Oct 2023 16:34:15 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Thu, 05 Oct 2023 16:32:09 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Thu, 05 Oct 2023 16:31:35 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Thu, 05 Oct 2023 16:31:12 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Thu, 05 Oct 2023 16:31:01 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Thu, 05 Oct 2023 16:30:54 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Thu, 05 Oct 2023 16:30:07 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Thu, 05 Oct 2023 16:24:30 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Thu, 05 Oct 2023 16:24:22 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Thu, 05 Oct 2023 16:24:10 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Thu, 05 Oct 2023 16:23:57 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Thu, 05 Oct 2023 16:23:41 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Thu, 05 Oct 2023 16:23:25 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 20:36:32 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 20:30:37 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 20:21:31 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 20:18:51 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 20:15:43 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 20:13:23 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 20:12:52 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 20:08:48 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 20:03:44 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 20:01:51 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 20:01:31 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 19:57:51 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 19:57:40 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 19:56:08 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 19:55:54 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 19:55:38 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 19:55:30 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 19:54:58 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 19:54:43 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 19:54:28 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 19:54:13 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 19:52:39 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 19:52:30 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 19:51:32 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 19:46:30 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 19:35:50 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 19:35:38 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 19:35:28 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 19:35:21 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 19:35:14 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 19:34:57 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 19:34:51 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 19:34:41 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 18:22:54 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 18:20:43 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 18:18:21 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 18:17:52 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 18:17:02 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 18:16:50 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 18:07:54 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 18:06:00 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 18:05:54 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 18:05:48 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 18:05:42 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 18:05:36 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 18:05:30 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 18:05:19 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 18:05:13 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 18:05:07 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 18:04:55 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 17:59:38 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 17:59:32 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 17:59:27 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 17:59:09 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 17:59:05 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 17:58:59 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 17:58:51 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 17:58:43 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 17:58:31 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 17:58:04 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 17:56:07 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 17:56:00 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 17:55:52 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 17:55:44 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 17:51:54 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 17:50:48 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 17:50:38 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 17:50:16 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 17:50:08 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 17:50:00 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 17:49:03 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 17:47:50 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 17:47:33 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 17:47:10 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 17:46:57 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 17:46:22 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Wed, 04 Oct 2023 17:46:17 GMT
wallet: nothing to consolidate: available outputs: 1, consolidation threshold: 2
Expected behaviour
...
Actual behaviour
...
Can the issue reliably be reproduced?
Yes
Steps to reproduce the issue
No response
Operating System
Mac
Diagnostics
No response
Developer Profile
No
Profile Type
Software (Stronghold)
Staking
None
Crash Status
Non-responsive
Error Messages
No response
Error Logs
No response
Duplicate declaration

[X] I have searched the issues tracker this issue and there is none

Code of Conduct

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

This is normal if you dont have enough outputs that can be consolidated you cant consolidate, you need at least 2 outputs and you have 1. You can wait until having more rewards unlocked or getting more funds to your account somehow. If you want to claim and you are getting this error, the claimable rewards are always yours to use as soon as they are unlocked, so dont worry about claiming, claiming will only consolidate them but the funds are your and available to use as soon as they are unlocked

Many thanks for your message. Since I have other accounts with more IOTa, if I transfer the low balance accounts to the larger ones, do you think I can claim the full rewards this way without disadvantages?Sincerely,Marcos Cid+41 78 733 47 @.*** 9 oct. 2023 à 13:14, Begoña Álvarez de la Cruz @.***> a écrit :
This is normal if you dont have enough outputs that can be consolidated you cant consolidate, you need at least 2 outputs and you have 1. You can wait until having more rewards unlocked or getting more funds to your account somehow. If you want to claim and you are getting this error, the claimable rewards are always yours to use as soon as they are unlocked, so dont worry about claiming, claiming will only consolidate them but the funds are your and available to use as soon as they are unlocked
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Claiming is just a consolidation so the ledger cleans up from all these small outputs that the vesting rewards created, the unlocked payouts are ready to use at any time, we just need a way to guide the user to "claim" the rewards which puts all these outputs in a single one, hence reducing the whole size of the ledger. Long story short, you dont really need to claim anything, every output that is unlocked is ready to be used from the moment is unlocked.


I couldn't open the local ibim file using simple-viewer-app.

I couldn't open the local ibim file using simple-viewer-app.
Always prompt Invalid iModelToken for RPC operation request，Can you help me.thanks.

⚠ Do not edit this section. It is required for imodeljs.github.io ➟ GitHub issue linking

LINK: Community-Resources---iModel.js-link-to-docs
TAG: imodeljs-docs-question
SOURCE: https://imodeljs.github.io/iModelJs-docs-output/learning/communityresources/

Duplicate of #52. Closing this to continue the conversation there.


[Ref][Tor] The Onion Router Implementation for Silk & Add Scheduler, ReverseLock Implementation

THIS PULL REQUEST IS ONLY FOR REFERENCE ONLY (AND FOR CODE INSPECTION) - NOT MEANT TO BE MERGED STANDALONE, INSTEAD LOOK AT PR #71
What is the purpose of this pull request (PR)?
As mentioned in the header (seriously, just read it)
Any background context to help the reviewer?
Based on https://github.com/bitcoin/bitcoin/commit/8f4e67f152a9625a1c66c20de00679286b2c187c
Was this PR tested and how?
On Ubuntu 16.04 running in VMWare Fusion on macOS Sierra
More Questions:

Does the knowledge base need an update? Yes (we need to elaborate to certain level about this)

Does this PR add or change dependencies? Yes (It adds the event library as a prerequisite)

Does this PR change or fork the blockchain? No (because it can't)

Unsure if this conflicts with @GregoryBetz work for TorControl.

It has been merged already as part of collation with #72