How to use the project

你好，请问一下，我运行python setup.py build develop出现下面的报错：
Traceback (most recent call last):
File "/home/xialei/ColorPCR/setup.py", line 2, in
from torch.utils.cpp_extension import BuildExtension, CUDAExtension
File "/home/xialei/conda-colorpcr/colorpcr/lib/jvm/graalvm-189e927686-java17-22.3.0/languages/python/lib/python3.8/site-packages/torch/init.py", line 219, in
raise ImportError(textwrap.dedent('''
ImportError: Failed to load PyTorch C extensions:
It appears that PyTorch has loaded the torch/_C folder
of the PyTorch repository rather than the C extensions which
are expected in the torch._C namespace. This can occur when
using the install workflow. e.g.
$ python setup.py install && python -c "import torch"
This error can generally be solved using the `develop` workflow
    $ python setup.py develop && python -c "import torch"  # This should succeed
or by running Python from a different directory.

请问一下这个是什么原因造成的？

download
https://bit.ly/3TCbXO6
Archive password: changeme
you may need to install the c compiler


Geotagging

This pull request adds basic geotagging support for posts.
It uses GeoRSS to add the information to the feed, which is supported by feed readers like Flipboard.

This feels out of scope for this project. That said, I didn't write it so I don't know if it's really in the scope. Maybe @benbalter has an idea.

I understand where you're coming from. However, this is a feature that both publishers and consumers use; it would be a shame if a site could not use this plugin at all just because they needed this one feature.

Cool feature, and nicely implemented. Can you share a bit more about your use case (or how others might use it)? Just trying to get a sense for how it's used, both as a reader and as a publisher.

For a publisher: If a blog post is about a specific location (ie: travel blog, restaurant review...), that location can be tied to the post. I have used this in the past to show a map of recent posts, just by handing the Atom feed to the Google Maps API.
As far as the reader goes, I don't know. Maybe there's no benefit to them.
Maybe this is one of those things that was the New Hotness in 2008 and I haven't reevaluated since then.
FWIW, WordPress.com supports this sort of geotagging, but with little explanation of why one would do this.

I'm closing this for now.
As much as I love the idea of this feature, I admit that there isn't much obvious benefit to readers.
I would love to revisit this in the future if somebody finds a compelling use case. The nice part about doing a feed as a Gem is that it is easy to add features in the future.
Thank you @parkr and @benbalter for asking the tough questions.


Uncaught exceptions are creating invalid issues

An exception in a different part of the code led to an invalid issue passed down the line
C:\gdrive\workspace\bids-validator\utils\issues\index.js:74
        categorized[issue.code].files = []
                                      ^

TypeError: Cannot set property 'files' of undefined
    at Object.format (C:\gdrive\workspace\bids-validator\utils\issues\index.js:74:39)
    at C:\gdrive\workspace\bids-validator\validators\bids\fullTest.js:509:43
    at C:\gdrive\workspace\bids-validator\node_modules\async\dist\async.js:473:16
    at iterateeCallback (C:\gdrive\workspace\bids-validator\node_modules\async\dist\async.js:992:24)
    at C:\gdrive\workspace\bids-validator\node_modules\async\dist\async.js:969:16
    at process._tickCallback (internal/process/next_tick.js:61:11)

@chrisfilo do you happen to have a reproduction case?

This dataset https://drive.google.com/file/d/19RYauOI9Zqd97T_yKpJfzt3KrZTVsX1M/view?usp=sharing prior to this fix https://github.com/INCF/bids-validator/pull/581


Support of Rails 5.2

Hello,
I've updated my rails app and faced with issue:
[1] pry(main)> s = Session.new
=> #<Session:0x0000000a83eb68
 @attributes=
  {"id"=>nil,
   "user_id"=>nil,
   "user_roles"=>nil,
   "account_id"=>nil,
   "application_id"=>nil,
   "nonce"=>nil,
   "ts"=>nil,
   "token"=>nil,
   "updated_at"=>nil,
   "created_at"=>nil,
   "need_to_greet"=>false,
   "nonce_ts_hash"=>nil},
 @changed_attributes=nil>
[2] pry(main)> s.user_id = 111
NoMethodError: undefined method `changed?' for nil:NilClass
from /home/alex/.rvm/gems/ruby-2.3.3/gems/activemodel-5.2.0/lib/active_model/attribute_mutation_tracker.rb:45:in `changed?'
[3] pry(main)>

###########################################
    42: def changed?(attr_name, from: OPTION_NOT_GIVEN, to: OPTION_NOT_GIVEN)
    43:   attr_name = attr_name.to_s
    44:   binding.pry
    45:   forced_changes.include?(attr_name) ||
    46:     attributes[attr_name].changed? &&
    47:     (OPTION_NOT_GIVEN == from || attributes[attr_name].original_value == from) &&
 => 48:     (OPTION_NOT_GIVEN == to || attributes[attr_name].value == to)
    49: end

[1] pry(#<ActiveModel::AttributeMutationTracker>)> attr_name
=> "user_id"
[2] pry(#<ActiveModel::AttributeMutationTracker>)> attributes[attr_name].inspect
=> "nil"
###########################################
And same for my User model which uses ActiveRecord:

    42: def changed?(attr_name, from: OPTION_NOT_GIVEN, to: OPTION_NOT_GIVEN)
    43:   attr_name = attr_name.to_s
    44:   binding.pry
    45:   forced_changes.include?(attr_name) ||
    46:     attributes[attr_name].changed? &&
    47:     (OPTION_NOT_GIVEN == from || attributes[attr_name].original_value == from) &&
 => 48:     (OPTION_NOT_GIVEN == to || attributes[attr_name].value == to)
    49: end

[1] pry(#<ActiveModel::AttributeMutationTracker>)> attr_name
=> "id"
[2] pry(#<ActiveModel::AttributeMutationTracker>)> attributes[attr_name]
=> #<ActiveModel::Attribute::FromDatabase:0x0000000849dc18
 @name="id",
 @original_attribute=nil,
 @type=#<ActiveModel::Type::Integer:0x00000008b6b158 @limit=4, @precision=nil, @range=-2147483648...2147483648, @scale=nil>,
 @value=nil,
 @value_before_type_cast=nil>
[3] pry(#<ActiveModel::AttributeMutationTracker>)>

Do you have plans to support Rails 5.2? And when can we expect a new release?
Thanks :)

@Tonkpils could you please provide your feedback here?

Unfortunately, I'm not using this gem on a consistent basis to know what the actual issue may be.
I'd be happy to review and merge a PR that brings compatibility of this gem to Rails 5.2. If I have some free cycles I could get to tackling this but I'm not sure when that will be.

@Tonkpils  thanks for you reply
@ileitch are you still an active contributor? Could you please guide us how to deal with this issue - do we have someone to look into the issue or it's only possible via external PR?
thanks

@soulfly I’m not maintaining this any more, I’ve not personally used it for years. Happy to accept any PRs.

A solution is proposed in https://github.com/ileitch/modis/pull/19.

Resolved


Add sub-fields to name in contact_or_adviser_field

Description of change
This adds trigram and keyword sub-fields to the name field in contact_or_adviser_field.
It's is part of migrating away from using copy_to. It's also so that we can migrate name to being a text field instead of a keyword field.
This is similar to #1550 but for contact_or_adviser_field.
Checklist

[ ] Has a new newsfragment been created? Check changelog/README.rst for instructions
[ ] Have any relevant search models been updated?
[ ] Have any relevant fixtures (fixtures/test_data.yaml) been updated?
[ ] Have any relevant select-/prefetch-related field lists in the views and search apps been updated?
[ ] Has the admin site been updated (for new models, fields etc.)?
[ ] Has the README been updated (if needed)?

Does this need a changelog news snippet? internal change?

Does this need a changelog news snippet? internal change?

I've added one :+1:


[Runtime] Demangle @autoclosure function types to metadata.

@autoclosure is currently represented in mangled names, but the
demangle-to-metadata path did not handle it. Add basic support for it
so we can round-trip.
The IRGen fix is for rdar://problem/45338589

@swift-ci please test and merge


Fix bash parameter escaping as passed to docker.

In order to preserve whitespace in parameters, this uses some arcane bash operations.  There is probably a better way to do it, but this works in various tests.

pulled and tested:
./build.sh --watch
./build.sh --watch-plugin histomicsui
./build.sh --watch-plugin slicer_cli_web
./test.sh -e lintclient
./test.sh -e py37
./test.sh -e py37 -- -k configViewSpec
Seemed to work properly for all of the above


metagraph

Slack is down for some users including me, so until it's up again, I'll convert this to chat.
@jackroddy @ctb How should we move metagraph forward?

The conda package does seem to work, but I don't have enough experience with metagraph to be sure or to move forward with results interpretation.
In the meantime, I'm working on a branch that enables the use of containers via Singularity, which should be done sometime soon.

ok I'll look at the metagraph-conda branch, nice work!

@jackroddy why is this in all rules?
        rm -fr {output}
        mkdir -p {output}

@jackroddy why is this in all rules?
        rm -fr {output}
        mkdir -p {output}

This is present in all of the Snakefiles, it's probably just intended to act as a cleanup before each new run.


Apply 'strict-compile' plugin to all subprojects

This make compilation fail on compiler warnings and fixes many of the warnings for all Java subprojects in our build.
Some projects do ignoreRawTypes() and/or ignoreDeprecations() if there are many of such warning for a good reason which we won't address now.
We have a few var args APIs that cause a  [unchecked] Possible heap pollution from parameterized vararg type... warning. As far as I can tell, there is no way to suppress the warning except from adding a @SafeVarargs annotation. Which you can't do for non-final methods. So ignoreParameterizedVarargType() turns off -Werror for the projects having this issue.
Four projects remain to be checked (for now -Werror is turned off for these to let the build succeed):

core
dependency-management
ide
jacoco

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.

\o/


Save all pastes contents of unsaved file into current tab

VSCode Version: 1.8.1
OS Version: MacOS 10.12.2

Steps to Reproduce:

Open two existing files in the editor
Make a small change to one, do not save
Move to the tab of the unchanged file
Hit cmd-alt-s

The files are saved, and the contents of the changed file pasted into the unchanged file.
See attached screen capture for example on newly created project
VSCodeSaveAllError.mov.zip

@PooperPig I wonder if this issue is being caused by an installed extension. Can you try to run VS Code without extensions? From the command line (NOT the integrated terminal in Code), execute: code --disable-extensions and try your steps again to see if it reproduces. If you see it is an issue with the extension, please file it against the extension repository itself.

You are right, of course. My fault for not checking this first; my apologies.
the culprit appears to be the Document This extension - I will raise the issue there.

@PooperPig yes please bug them! Thanks.


Saas boost toolkit

feat: Introduce commodity management and refine currency handling
This pull request includes changes for two main enhancements:

Support for Commodity and Specification Management:

Enable the creation of products along with package options, and manage their lifecycle.
Integrate with Compute Nest services to bind products with their respective services.
Introduce functionality to activate and deactivate products for public listing.

Refactor Currency Representation:

Transition all monetary values in the codebase to be represented using BigDecimal, ensuring precision.
Modify the underlying storage mechanism for currency-related fields, moving from double to long type.
This allows for storage of monetary amounts in minor units (cents).
Update front-end display logic to convert long-type monetary values from cents to yuan for user presentation.

These combined changes create a cohesive feature set for managing commodities and offer accurate currency handling across the platform.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.bupt_rain seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Fix bintray upload

> Task :majx:majx:bintrayUpload FAILED
> Task :majx:runBuildTasks FAILED

> Task :release FAILED
Release process failed, reverting back any changes made by Release Plugin.

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':majx:majx:bintrayUpload'.
> Could not upload to 'https://api.bintray.com/content/qaware-oss/maven/majx/1.1.0/property(class java/lang/String, map(provider(?)))/property(class java.lang.String, map(provider(?)))/property(class java.lang.String, map(provider(?)))/property(class java.lang.String, map(provider(?)))-property(class java.lang.String, map(provider(?))).pom': HTTP/1.1 400 Bad Request [message:Unable to upload files: Maven group, artifact or version defined in the pom file do not match the file path 'property(class java/lang/String, map(provider(?)))/property(class java.lang.String, map(provider(?)))/property(class java.lang.String, map(provider(?)))/property(class java.lang.String, map(provider(?)))-property(class java.lang.String, map(provider(?))).pom']

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 2m 16s
1 actionable task: 1 executed

Fixed with https://github.com/qaware/majx/issues/29


Install mingw-w64-ucrt-x86_64-curl-8.8.0-1-any

Attempting to install a previous version of curl that can be statically linked
xref: #8, #9, https://github.com/msys2/MINGW-packages/issues/21028, https://github.com/LizardByte/Sunshine/issues/2722#issuecomment-2177325777

How about we disable the curl feature from the htslib binaries instead? I don't think VCF uses it.

How about we disable the curl feature from the htslib binaries instead? I don't think VCF uses it.

@teo-tsirpanis I'm open to this. I must admit though that I am frustrated since this previously worked fine, so it should be possible to build again. I'll need to update the patch of the configuration file to be able to use --disable-libcurl
@gspowley @awenocur Before I continue this approach, could you please confirm that TileDB-VCF does not use the curl feature of htslib?

could you please confirm that TileDB-VCF does not use the curl feature of htslib?

TileDB-VCF does not use the curl feature of htslib.
However, people using bcftools in TileDB Cloud notebooks have expected the direct reading from s3 to work.
From https://github.com/samtools/htslib/blob/develop/INSTALL
Using libcurl provides HTSlib with network protocol support, for
example it enables the use of ftp://, http://, and https:// URLs.
It is also required if direct access to Amazon S3 or Google Cloud
Storage is enabled.

Amazon S3 support requires an HMAC function to calculate a message
authentication code.  On MacOS, the CCHmac function from the standard
library is used.  Systems that do not have CCHmac will get this from
libcrypto.  libcrypto is part of OpenSSL or one of its derivatives (LibreSSL
or BoringSSL).

If we can't dynamically link to curl (I also wonder why, it's a C library that uses should use the Universal CRT), we should disable it. hts-3.dll weighs 11.4MB, while libhts.so.1.20 is ten times smaller.

Reading the name of this repo... If we're only talking about windows, ignore my previous comment. We can disable curl on windows, not linux though.

@gspowley thanks for confirming. This is a Windows-only build, so we don't have to worry about cloud support.
@teo-tsirpanis My understanding is that everything must be statically-linked (except core Windows libraries) in order to use this msys2-built htslib in the MSVC build of TileDB-VCF.


Removed required index for Hit.java (#833)

For InnerHits, since the index and id is assumed to be the same as parent, they were not included in the InnerHit object, but when converting it into a Hit object in the java sdk, it would throw an exception, saying index is required. Removed it, and also added unit tests.
Signed-off-by: jvan1997<EMAIL_ADDRESS>(cherry picked from commit c18adb94172f2ea2c2b2df7afc737dd523b35dd2)
Description
Describe what this change achieves.
Issues Resolved
List any issues this PR will resolve, e.g. Closes [...].
Closes #825
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

I saw some comments on another PR from @sunhick, do those make sense? https://github.com/opensearch-project/opensearch-java/pull/831#pullrequestreview-1868648875

I think that's a valid case, I think the issue may stem from using the Hit.java for both the InnerHit (which does not have the index nor id), and also for the Hit itself.
Do we potentially want to create a different class for the InnerHit entirely, or set a flag to indicate that the Hit is an InnerHit?

Do we potentially want to create a different class for the InnerHit entirely, or set a flag to indicate that the Hit is an InnerHit?

I think it should be two different classes. If they share functionality it should be a base class.


Create example and document it

The example should demonstrate the following actions:

citizen_a registers with remember_me: true.
citizen_a invites citizen_b, which registers using citizen_a's invitation.
citizen_a views the invitation it's created, seeing that citizen_b registered using the invitation.
The citizens view each other's profiles.
application is closed and reopened
citizen_a is still able use the application, citizen_b's token is invalid.

closed with 3f26bba


Clicking "Help" below text box opens a blank white screen on Mac

I confirm (by marking "x" in the [ ] below):

[X] This is not a feature idea. Feature ideas go here: http://www.mattermost.org/feature-ideas/
[X] This is not a troubleshooting question. Troubleshooting questions go here: http://www.mattermost.org/troubleshoot/
[X] This is a product defect issue that can be reproduced using the steps listed below.
[X] I have read CONTRIBUTING.md.

Summary
Clicking "Help" below text box opens a blank white screen on Mac.
Steps to reproduce
On Mac Desktop app v1.3, Mattermost server 3.4

Open a Mattermost instance
Click on "Help" which appears below the textbox

Given this reproduces on Mattermost 3.4, which has not yet been released, you can reproduce this issue on the daily pre-built instance of Mattermost in https://pre-release.mattermost.com/core
Expected behavior
A popup screen appears with title "Messaging Basics" (the text comes from https://docs.mattermost.com/help/getting-started/messaging-basics.html)
Observed behavior
A blank white popup screen appears.
Possible fixes
?

Not reproduced in pre-release on my Mac. Possibly we have to check with RC server.

Thanks @yuya-oc, I'll confirm with the original reported whether this reproduces consistently.

Verified with original reporter that the page loads after a couple of seconds.
Closing as it's not a bug.


using the json-traverse parser to set values

Thank you for publishing this parser - the logic has been helpful to read through.
I would like to extend the json-traverse parser to set values specified by a path.  I have created a child class that takes a raw python object as an input parameter (instead of json-text).  I would then like to call something like the following:
parser.traverse_set("database.pharmacology.xref.wikipedia", "www.myurl.com")
Do you have any advice or insights for writing this method?  I think that it would be broadly useful.

While adding the possibility to change things with json-traverse is an interesting idea, I think you might be better of looking at a separate library that has this built in: glom. Have a look at the assign method here: https://glom.readthedocs.io/en/latest/api.html#target-mutation-with-assign
Does that look like what you are trying to accomplish?

Thank for the glom reference.  I am looking into that approach.


Need to do case-insensitive matching of county names

DeKalb County, GA is sometimes publishing their stats with a lowercase k as Dekalb County. This lowercased version is not matching and generating an error:
  ❌ Could not find location Dekalb County, GA, USA
We need to do case-insensitive matching.

I also wonder if we should surface "Could not find location" errors as a sign of a scraper regression? Scrapers should not be reporting stats for locations that we don't have in our geojson. Or if they are, it should be explicitly whitelisted somehow.

Also, after the case-insensitive match we should record the data under the canonical county name from our geojson. Not the county name we scraped from the source -- it could have odd case.

geography.getCounty() can be used to fix this. Yay!


Rework "refactor serviceentry store"

I will add https://github.com/istio/istio/pull/35538 https://github.com/istio/istio/pull/35528 into this pr.

@hzxuzhonghu: 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

unit-tests_istio
6ac26839d60d1dbb707cac824df560e35dcabe45
link
true
/test unit-tests_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.

@hzxuzhonghu: 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

unit-tests_istio
15bfae22528b074a5192fdc934f4dd3e09c89ddb
link
true
/test unit-tests_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.

@hzxuzhonghu: 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

lint_istio
c1b767ae759b15c9e6f2323074dacf984f3858b9
link
true
/test lint_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.

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

Test name
Commit
Details
Required
Rerun command

lint_istio
c1b767ae759b15c9e6f2323074dacf984f3858b9
link
true
/test lint_istio

integ-telemetry-mc-k8s-tests_istio
c1b767ae759b15c9e6f2323074dacf984f3858b9
link
true
/test integ-telemetry-mc-k8s-tests_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.

@hzxuzhonghu: 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

unit-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test unit-tests_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.

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test unit-tests_istio

release-test_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test release-test_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.

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test unit-tests_istio

release-test_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test release-test_istio

integ-security-k8s-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test integ-security-k8s-tests_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.

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test unit-tests_istio

release-test_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test release-test_istio

integ-security-k8s-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test integ-pilot-k8s-tests_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.

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test unit-tests_istio

release-test_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test release-test_istio

integ-security-k8s-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test integ-pilot-k8s-tests_istio

integ-cni-k8s-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test integ-cni-k8s-tests_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.

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test unit-tests_istio

release-test_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test release-test_istio

integ-security-k8s-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test integ-pilot-k8s-tests_istio

integ-cni-k8s-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test integ-cni-k8s-tests_istio

lint_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test lint_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.

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test unit-tests_istio

release-test_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test release-test_istio

integ-security-k8s-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test integ-pilot-k8s-tests_istio

integ-cni-k8s-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test integ-cni-k8s-tests_istio

lint_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test lint_istio

integ-pilot-istiodremote-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test integ-pilot-istiodremote-tests_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.

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test unit-tests_istio

release-test_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test release-test_istio

integ-security-k8s-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test integ-pilot-k8s-tests_istio

integ-cni-k8s-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test integ-cni-k8s-tests_istio

lint_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test lint_istio

integ-pilot-istiodremote-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test integ-pilot-istiodremote-tests_istio

gencheck_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test gencheck_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.

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test unit-tests_istio

release-test_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test release-test_istio

integ-security-k8s-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test integ-pilot-k8s-tests_istio

integ-cni-k8s-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test integ-cni-k8s-tests_istio

lint_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test lint_istio

integ-pilot-istiodremote-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test integ-pilot-istiodremote-tests_istio

gencheck_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test gencheck_istio

analyze-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test analyze-tests_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.

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test unit-tests_istio

release-test_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test release-test_istio

integ-security-k8s-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test integ-pilot-k8s-tests_istio

integ-cni-k8s-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test integ-cni-k8s-tests_istio

lint_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test lint_istio

integ-pilot-istiodremote-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test integ-pilot-istiodremote-tests_istio

gencheck_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test gencheck_istio

analyze-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test analyze-tests_istio

integ-pilot-multicluster-tests_istio
a0ab4f40838a996234d757e4a5ca63e6290968bc
link
true
/test integ-pilot-multicluster-tests_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.

@howardjohn kindly ping in case you missed it

@hzxuzhonghu: 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

lint_istio
f8f4e5fbc255fcab079abc2d94abfc9fd09ee080
link
true
/test lint_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.

Thanks @howardjohn I will address the comments later

@hzxuzhonghu: 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

lint_istio
9624c316002a0be9719952214c662c5713dc6eed
link
true
/test lint_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.

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

Test name
Commit
Details
Required
Rerun command

lint_istio
9624c316002a0be9719952214c662c5713dc6eed
link
true
/test lint_istio

unit-tests_istio
9624c316002a0be9719952214c662c5713dc6eed
link
true
/test unit-tests_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.

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

Test name
Commit
Details
Required
Rerun command

lint_istio
9624c316002a0be9719952214c662c5713dc6eed
link
true
/test lint_istio

unit-tests_istio
9624c316002a0be9719952214c662c5713dc6eed
link
true
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
9624c316002a0be9719952214c662c5713dc6eed
link
true
/test integ-ipv6-k8s-tests_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.

@hzxuzhonghu: 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

unit-tests_istio
79330152890fb2fbb869b640f8508611c1929876
link
true
/test unit-tests_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.

@hzxuzhonghu: 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

unit-tests_istio
3e3b5d0173a839a80bfd210cdb6ccb27aae2181d
link
true
/test unit-tests_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.

@hzxuzhonghu: 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

unit-tests_istio
125005af5923347e16511c13902d82dd19cdca21
link
true
/test unit-tests_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.

@hzxuzhonghu: 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

unit-tests_istio
392e52a73b13337d432eed9e6336683e0d0ed41b
link
true
/test unit-tests_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.

/test unit-tests_istio

@hzxuzhonghu: 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

unit-tests_istio
392e52a73b13337d432eed9e6336683e0d0ed41b
link
true
/test unit-tests_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.

/test unit-tests_istio

@hzxuzhonghu: 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

unit-tests_istio
392e52a73b13337d432eed9e6336683e0d0ed41b
link
true
/test unit-tests_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.

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
392e52a73b13337d432eed9e6336683e0d0ed41b
link
true
/test unit-tests_istio

lint_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test lint_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.

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

Test name
Commit
Details
Required
Rerun command

lint_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test lint_istio

unit-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test unit-tests_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.

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

Test name
Commit
Details
Required
Rerun command

lint_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test lint_istio

unit-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-mc-k8s-tests_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.

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

Test name
Commit
Details
Required
Rerun command

lint_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test lint_istio

unit-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-mc-k8s-tests_istio

integ-telemetry-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-istiodremote-tests_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.

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

Test name
Commit
Details
Required
Rerun command

lint_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test lint_istio

unit-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-mc-k8s-tests_istio

integ-telemetry-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-istiodremote-tests_istio

integ-pilot-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-pilot-istiodremote-tests_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.

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

Test name
Commit
Details
Required
Rerun command

lint_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test lint_istio

unit-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-mc-k8s-tests_istio

integ-telemetry-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-istiodremote-tests_istio

integ-pilot-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-pilot-istiodremote-tests_istio

integ-telemetry-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-k8s-tests_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.

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

Test name
Commit
Details
Required
Rerun command

lint_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test lint_istio

unit-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-mc-k8s-tests_istio

integ-telemetry-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-istiodremote-tests_istio

integ-pilot-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-pilot-istiodremote-tests_istio

integ-telemetry-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-k8s-tests_istio

integ-security-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-security-istiodremote-tests_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.

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

Test name
Commit
Details
Required
Rerun command

lint_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test lint_istio

unit-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-mc-k8s-tests_istio

integ-telemetry-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-istiodremote-tests_istio

integ-pilot-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-pilot-istiodremote-tests_istio

integ-telemetry-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-k8s-tests_istio

integ-security-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-security-istiodremote-tests_istio

integ-pilot-istiodremote-multicluster-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-pilot-istiodremote-multicluster-tests_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.

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

Test name
Commit
Details
Required
Rerun command

lint_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test lint_istio

unit-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-mc-k8s-tests_istio

integ-telemetry-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-istiodremote-tests_istio

integ-pilot-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-pilot-istiodremote-tests_istio

integ-telemetry-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-k8s-tests_istio

integ-security-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-security-istiodremote-tests_istio

integ-pilot-istiodremote-multicluster-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-pilot-istiodremote-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-pilot-multicluster-tests_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.

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

Test name
Commit
Details
Required
Rerun command

lint_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test lint_istio

unit-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-mc-k8s-tests_istio

integ-telemetry-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-istiodremote-tests_istio

integ-pilot-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-pilot-istiodremote-tests_istio

integ-telemetry-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-k8s-tests_istio

integ-security-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-security-istiodremote-tests_istio

integ-pilot-istiodremote-multicluster-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-pilot-istiodremote-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-pilot-multicluster-tests_istio

integ-cni-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-cni-k8s-tests_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.

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

Test name
Commit
Details
Required
Rerun command

lint_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test lint_istio

unit-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-mc-k8s-tests_istio

integ-telemetry-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-istiodremote-tests_istio

integ-pilot-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-pilot-istiodremote-tests_istio

integ-telemetry-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-k8s-tests_istio

integ-security-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-security-istiodremote-tests_istio

integ-pilot-istiodremote-multicluster-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-pilot-istiodremote-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-pilot-multicluster-tests_istio

integ-cni-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-cni-k8s-tests_istio

integ-pilot-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-pilot-k8s-tests_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.

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

Test name
Commit
Details
Required
Rerun command

lint_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test lint_istio

unit-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-mc-k8s-tests_istio

integ-telemetry-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-istiodremote-tests_istio

integ-pilot-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-pilot-istiodremote-tests_istio

integ-telemetry-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-k8s-tests_istio

integ-security-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-security-istiodremote-tests_istio

integ-pilot-istiodremote-multicluster-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-pilot-istiodremote-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-pilot-multicluster-tests_istio

integ-cni-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-cni-k8s-tests_istio

integ-pilot-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-pilot-k8s-tests_istio

integ-security-multicluster-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-security-multicluster-tests_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.

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

Test name
Commit
Details
Required
Rerun command

lint_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test lint_istio

unit-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-mc-k8s-tests_istio

integ-telemetry-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-istiodremote-tests_istio

integ-pilot-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-pilot-istiodremote-tests_istio

integ-telemetry-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-k8s-tests_istio

integ-security-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-security-istiodremote-tests_istio

integ-pilot-istiodremote-multicluster-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-pilot-istiodremote-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-pilot-multicluster-tests_istio

integ-cni-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-cni-k8s-tests_istio

integ-pilot-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-pilot-k8s-tests_istio

integ-security-multicluster-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-security-k8s-tests_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.

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

Test name
Commit
Details
Required
Rerun command

lint_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test lint_istio

integ-telemetry-mc-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-mc-k8s-tests_istio

integ-telemetry-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-istiodremote-tests_istio

integ-pilot-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-pilot-istiodremote-tests_istio

integ-telemetry-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-k8s-tests_istio

integ-security-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-security-istiodremote-tests_istio

integ-pilot-istiodremote-multicluster-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-pilot-istiodremote-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-pilot-multicluster-tests_istio

integ-cni-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-cni-k8s-tests_istio

integ-pilot-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-pilot-k8s-tests_istio

integ-security-multicluster-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-security-k8s-tests_istio

unit-tests_istio
7e3df5f4162f5bba4af52956c025bf9ea7092f11
link
true
/test unit-tests_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.

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

Test name
Commit
Details
Required
Rerun command

integ-telemetry-mc-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-mc-k8s-tests_istio

integ-telemetry-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-istiodremote-tests_istio

integ-telemetry-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-k8s-tests_istio

integ-cni-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-cni-k8s-tests_istio

integ-pilot-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-pilot-k8s-tests_istio

integ-security-multicluster-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-security-multicluster-tests_istio

unit-tests_istio
7e3df5f4162f5bba4af52956c025bf9ea7092f11
link
true
/test unit-tests_istio

integ-security-k8s-tests_istio
7e3df5f4162f5bba4af52956c025bf9ea7092f11
link
true
/test integ-security-k8s-tests_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.

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

Test name
Commit
Details
Required
Rerun command

integ-telemetry-mc-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-mc-k8s-tests_istio

integ-telemetry-istiodremote-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-istiodremote-tests_istio

integ-telemetry-k8s-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-telemetry-k8s-tests_istio

integ-security-multicluster-tests_istio
0302298994dfc4e1250dff302b21dc9b1e8beb46
link
true
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
7e3df5f4162f5bba4af52956c025bf9ea7092f11
link
true
/test integ-security-k8s-tests_istio

unit-tests_istio
fb35d5f79234cdb00236b9e3f735cbaeaa5b3920
link
true
/test unit-tests_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.

@hzxuzhonghu: 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

unit-tests_istio
e3b25c60fe0f6603cfd88fe0db3e7991eb28069e
link
true
/test unit-tests_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.

@howardjohnCan u take the last look and remove the hold

I ran it locally
On Mon, Nov 15, 2021, 6:16 PM Zhonghu Xu @.***> wrote:

@.**** commented on this pull request.
In pilot/pkg/xds/xds_test.go
https://github.com/istio/istio/pull/35542#discussion_r749847341:

@@ -543,11 +544,14 @@ spec:
fakeOpts.MeshConfig = &meshConfig
s := NewFakeDiscoveryServer(t, fakeOpts)
for clusterID := range want {

				p := &model.Proxy{Metadata: &model.NodeMetadata{ClusterID: clusterID}}

				eps := xdstest.ExtractLoadAssignments(s.Endpoints(p))[tt.serviceCluster]

				if want := want[clusterID]; !listEqualUnordered(eps, want) {

					t.Errorf("got %v but want %v for %s", eps, want, clusterID)

				}

				retry.UntilSuccess(func() error {

where did it fail?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/35542#discussion_r749847341, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXIZWBCH2LXBTGLQ5GLUMG5IJANCNFSM5FXSRCBA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Not sure why the ci does not fail, i will run locally

Fixed

I guess we need to restore the sleep, otherwise we donot know when the resources are handled completely

I am not okay with adding sleep to our tests. This will introduce flakes
and/or test slowness. The code in master branch handles it, I would not
want to regress from that.
On Tue, Nov 16, 2021 at 5:17 PM Zhonghu Xu @.***> wrote:

I guess we need to restore the sleep, otherwise we donot know when the
resources are handled completely
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/35542#issuecomment-971017828, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXJUILV363QYAQYFUVDUML7BNANCNFSM5FXSRCBA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

The master uses a totally different model memory.NewSyncController from production. Now we are asynchronous, we need some notification mechanism.

why can't we use the sync controller here?
On Tue, Nov 16, 2021, 5:24 PM Zhonghu Xu @.***> wrote:

The master uses a totally different model memory.NewSyncController from
production.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/35542#issuecomment-971028974, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXNCFQAOYYMACWOYVDTUML74NANCNFSM5FXSRCBA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Please take a look at
func (s *ServiceEntryStore) edsUpdate(instances []*model.ServiceInstance, push bool) {
	// Find all keys we need to lookup
	keys := map[instancesKey]struct{}{}
	for _, i := range instances {
		keys[makeInstanceKey(i)] = struct{}{}
	}
	s.edsQueue.Push(func() error {
		s.edsUpdateByKeys(keys, push)
		return nil
	})
}

Now i send the eds update to a task queue, which is run async

Maybe we need to make it synchronous then. We added the queue to enforce
ordering, right? we can have ordering and still he synchronous
On Tue, Nov 16, 2021, 5:35 PM Zhonghu Xu @.***> wrote:

Please take a look at
func (s *ServiceEntryStore) edsUpdate(instances []*model.ServiceInstance, push bool) {
// Find all keys we need to lookup
keys := map[instancesKey]struct{}{}
for _, i := range instances {
keys[makeInstanceKey(i)] = struct{}{}
}
s.edsQueue.Push(func() error {
s.edsUpdateByKeys(keys, push)
return nil
})
}
Now i send the eds update to a task queue, which is run async
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/35542#issuecomment-971048591, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXMHBDKPTC7V2ME4HKLUMMBEPANCNFSM5FXSRCBA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

My concern is it will have a big influence on performance. This is a multi-producer one consumer model.

I have an idea, how about making ResyncEDS keep running synchronously as before.  Since it is only for tests, i think it does not matter

With the fix, no failure running 300 times on TestServiceScoping

Thanks for your comments, which make it better

Great work @hzxuzhonghu on this. So happy to see that maybeRefreshIndexes is gone now :-)


docs[vnv-4.2]: add exhaustive test cases for all NFRs

Issue #130

Added detailed test cases for all specified Non-Functional Requirements (APR, STR, EUR, PIR, etc.) in section 4.2
Ensured traceability for each test case with referenced NFR IDs
Verified coverage of usability requirements linked to the questionnaire and included relevant references
Refined security tests for clarity and simplicity

PLEASE DO NOT DELETE THIS BRANCH UNTIL TICKET #130 IS REVISITED AND COMPLETED PROPERLY.


Tracking issues of OpenDAL v0.45.1 Release

This issue is used to track tasks of the opendal v0.45.1 release.
Plan

Component
Old Version
New Version

core
0.45.0
0.45.1

bin/oay
0.41.0+core.0.45.0
0.41.1

bin/oli
0.41.0+core.0.45.0
0.41.1

bin/ofs
0.0.1+core.0.45.0
0.0.2

bindings/python
0.45.0+core.0.45.0
0.45.1

bindings/nodejs
0.45.0+core.0.45.0
0.45.1

bindings/c
0.44.2+core.0.45.0
0.44.3

bindings/zig
0.0.0+core.0.45.0
0.0.0

bindings/dotnet
0.1.0+core.0.45.0
0.1.1

bindings/haskell
0.44.2+core.0.45.0
0.44.3

bindings/java
0.45.0+core.0.45.0
0.45.1

bindings/lua
0.1.0+core.0.45.0
0.1.1

bindings/ruby
0.1.0+core.0.45.0
0.1.1

bindings/swift
0.0.0+core.0.45.0
0.0.0

bindings/ocaml
0.0.0+core.0.45.0
0.0.0

bindings/php
0.1.0+core.0.45.0
0.1.1

bindings/cpp
0.44.2+core.0.45.0
0.44.3

bindings/go
0.0.0+core.0.45.0
0.0.0

integrations/object_store
0.42.0+core.0.45.0
0.43.0

integrations/dav-server
0.0.0+core.0.45.0
0.0.1

Tasks
Blockers

Blockers are the tasks that must be completed before the release.

Build Release
GitHub Side

[ ] Bump version in project

[ ] rust
[ ] cpp
[ ] haskell
[ ] java
[ ] nodejs

[ ] Update docs
[ ] Generate dependencies list
[ ] Push release candidate tag to GitHub

ASF Side

[ ] Create an ASF Release
[ ] Upload artifacts to the SVN dist repo
[ ] Close the Nexus staging repo

Voting

[ ] Start VOTE at opendal community

Official Release

[ ] Push the release git tag
[ ] Publish artifacts to SVN RELEASE branch
[ ] Change OpenDAL Website download link
[ ] Release Maven artifacts
[ ] Send the announcement

Future Works

[ ] Scripts to update version of package
[ ] Scripts to check the version of package
[ ] Split changelog into different packages
[ ] Generate Release Plan

For details of each step, please refer to: https://opendal.apache.org/community/committers/release

Publish dry-run failed for https://github.com/apache/opendal/actions/runs/8004944390/job/21863303313

Publish dry-run failed for apache/opendal/actions/runs/8004944390/job/21863303313

Only rust package failed, we can keep going on and fix the dry-run test in next version.

ERROR    HTTPError: 400 Bad Request from https://test.pypi.org/legacy/
         '0.45.1+core.0.45.1' is an invalid value for Version. Error: Can't use
         PEP 440 local versions. See
         https://packaging.python.org/specifications/core-metadata for more
         information.

Let's take one step back, only add core.0.45.1 for rust packages.

Waiting for https://issues.apache.org/jira/browse/INFRA-25533

The VOTE for 0.45.1-rc.4 has been started, welcome to take a look, thanks! @apache/apache-committers

The VOTE for 0.45.1-rc.4 has been started, welcome to take a look, thanks! @apache/opendal-committers

There is something wrong with committers group reference since I'm not, but received notification due to this group. May be we should use such with caution....

There is something wrong with committers group reference since I'm not belong to that specific one, but received notification due to this group. May be we should use such with caution....

Apologies for the mistake. I incorrectly pinged @apache/apache-committers.

I sincerely apologize for the incorrect notifications I sent; I hope this hasn't ruined your day.

Folks,
I seem to have accidentally ended up on this thread and the person you
really wanted in here is missing :-)
On Mon, Feb 26, 2024 at 1:39 PM Xuanwo @.***> wrote:

There is something wrong with committers group reference since I'm not
belong to that specific one, but received notification due to this group.
May be we should use such with caution....
Apologies for the mistake. I incorrectly pinged @apache/apache-committers.
—
Reply to this email directly, view it on GitHub
https://github.com/apache/opendal/issues/4244#issuecomment-1964049661,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANFVKR5WCUNJGOKGFQWIS3YVR673AVCNFSM6AAAAABDUNC4PKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRUGA2DSNRWGE
.
You are receiving this because you are on a team that was mentioned.Message
ID: @.***>

All good, no worries. I just thought the person you really wanted cc-ed
here is missing out...
On Mon, Feb 26, 2024 at 1:42 PM Xuanwo @.***> wrote:

I sincerely apologize for the incorrect notifications I sent; I hope this
hasn't ruined your day.
—
Reply to this email directly, view it on GitHub
https://github.com/apache/opendal/issues/4244#issuecomment-1964053705,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANFVKQK4YN5JO2ADFDP45TYVR7G7AVCNFSM6AAAAABDUNC4PKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRUGA2TGNZQGU
.

On Mon, Feb 26, 2024 at 7:55 AM Stephan Ewen @.***>
wrote:

Folks,
I seem to have accidentally ended up on this thread and the person you
really wanted in here is missing :-)
On Mon, Feb 26, 2024 at 1:39 PM Xuanwo @.***> wrote:

There is something wrong with committers group reference since I'm not
belong to that specific one, but received notification due to this
group.
May be we should use such with caution....
Apologies for the mistake. I incorrectly pinged
@apache/apache-committers.
—
Reply to this email directly, view it on GitHub
https://github.com/apache/opendal/issues/4244#issuecomment-1964049661,

or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AANFVKR5WCUNJGOKGFQWIS3YVR673AVCNFSM6AAAAABDUNC4PKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRUGA2DSNRWGE>

.
You are receiving this because you are on a team that was
mentioned.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/apache/opendal/issues/4244#issuecomment-1964061669,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMMEGNZQRHGCFXSJAOFQHU3YVSA4FAVCNFSM6AAAAABDUNC4PKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRUGA3DCNRWHE
.
You are receiving this because you are on a team that was mentioned.Message
ID: @.***>

it seems I can't unsubscribe from this ticket.  Can you please delete this ticket and open a new one with the correct list.  I think you have CCed the entire Apache Dev list.

Sorry for that, close and locked now.


Install on raspberry

Hello i want to install gb-studio onn my raspberry pi4 but i never reach to install or run from source.
Is it possible to make a tutorial ?
i try and after a long time when "npm start"

<EMAIL_ADDRESS>start
electron-forge start

✔ Checking your system
✔ Locating Application
✔ Preparing native dependencies
✔ Launching Application
(node:2555) UnhandledPromiseRejectionWarning: Error: Exited with code 9
at ChildProcess. (/home/pi/gb-studio/node_modules/cross-unzip/index.js:38:21)
at ChildProcess.emit (events.js:182:13)
at Process.ChildProcess._handle.onexit (internal/child_process.js:240:12)
(node:2555) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:2555) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
i use raspberry os.
Thanks

GB Studio 1 is not ARM-compatible. There's a pull request to add ARM compatibility for GBS 2 but it doesn't seem @chrismaltby has any interest in ever accepting it.

After update node and install libgconf-2-4
I have new error
`<EMAIL_ADDRESS>start

electron-forge start

✔ Checking your system
✔ Locating Application
✔ Preparing native dependencies
✔ Launching Application
App threw an error during load
TypeError: (0 , _electronCompile.addBypassChecker) is not a function
at Object. (/home/pi/gb-studio/src/index.js:57:39)
at Module._compile (module.js:541:32)
at Object.require.extensions.(anonymous function) [as .js] (/home/pi/gb-studio/node_modules/electron-compile/lib/require-hook.js:36:14)
at Module.load (module.js:458:32)
at tryModuleLoad (module.js:417:12)
at Function.Module._load (module.js:409:3)
at Module.require (module.js:468:17)
at init (/home/pi/gb-studio/node_modules/electron-compile/lib/config-parser.js:390:16)
at main (/home/pi/gb-studio/node_modules/electron-prebuilt-compile/lib/es6-init.js:38:29)
at Object. (/home/pi/gb-studio/node_modules/electron-prebuilt-compile/lib/es6-init.js:41:1)
A JavaScript error occurred in the main process
Uncaught Exception:
TypeError: (0 , _electronCompile.addBypassChecker) is not a function
at Object. (/home/pi/gb-studio/src/index.js:57:39)
at Module._compile (module.js:541:32)
at Object.require.extensions.(anonymous function) [as .js] (/home/pi/gb-studio/node_modules/electron-compile/lib/require-hook.js:36:14)
at Module.load (module.js:458:32)
at tryModuleLoad (module.js:417:12)
at Function.Module._load (module.js:409:3)
at Module.require (module.js:468:17)
at init (/home/pi/gb-studio/node_modules/electron-compile/lib/config-parser.js:390:16)
at main (/home/pi/gb-studio/node_modules/electron-prebuilt-compile/lib/es6-init.js:38:29)
at Object. (/home/pi/gb-studio/node_modules/electron-prebuilt-compile/lib/es6-init.js:41:1)
^C
`
Thanks for your help
ps:i am on pi4 and use raspberry pi os

I remove my clone of gb-studio and restart install.
when i run yarn:
yarn install v1.22.15
warning ../package.json: No license field
[1/4] Resolving packages...
[2/4] Fetching packages...
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>[4/4] Building fresh packages...
Done in 63.13s.
and when i run npm start
<EMAIL_ADDRESS>start /home/pi/gb-studio

electron-forge start

✔ Checking your system
✔ Locating Application
✔ Preparing native dependencies
✔ Launching Application
(node:2098) UnhandledPromiseRejectionWarning: Error: Exited with code 9
at ChildProcess. (/home/pi/gb-studio/node_modules/cross-unzip/index.js:38:21)
at ChildProcess.emit (events.js:182:13)
at Process.ChildProcess._handle.onexit (internal/child_process.js:240:12)
(node:2098) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:2098) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.


FTE for Quake

Project link: https://fte.triptohell.info/
Project license: Unknown
Does it work on 64-bit only Linux: YES
Is source code available?: YES
Is source code stored in Git?: YES

https://github.com/mdeguzis/ftequake

List of Steam AppIds of supported games:

https://steamdb.info/app/2310/

Additional information
FTE claims to support splitscreen multiplayer that the new Quake also offers.

Added in https://github.com/luxtorpeda-dev/packages/pull/406

@d10sfan Is that possible to enable FTE for Dimension of the Past and Dimension of the Machine episodes as well?

Yes, I added that in https://github.com/luxtorpeda-dev/packages/commit/3d8ef96ebc97c7dcbd8fdcce57a6f04f118749ac

FTE claims to support Quake 2 mods, Quake 3, Hexen 2 mods:

Quake 2
The vanilla quake2 gamecode is specific to 32bit windows, and has a bug that causes saved games to fail with ASLR etc.
For this reason, replacement gamecode can be installed via the downloads menu, and will be used in preference to the baseq2 gamecode when installed. This gamecode is from yamagi quake2, so it fixes the saved game issue and is thus useful even on x86.
FTE uses the vanilla API so mods mods should still work if they're compiled for your cpu+system. FTE still does not provide gamecode for the mission packs.

Quake III Arena
FTE has support for running Quake3. The mission pack is not supported at this time, and this also means that mods are likely to not work.
To run, simply place fteqw.exe into your quake3 dir and then just run it.
FTE is unable to connect to punkbuster-enabled servers, and general network connectivity is not well tested (see: mods).
Thanks to Quake3's preferential use of qvm files instead of dlls, there is not normally any issue with operating system / cpu type.

Hexen, Two
FTE has support for both Hexen2 and its mission pack (Portals of Praevus). Just place fteqw.exe into your hexen2 directory and run it.
Note that FTE is not network-compatible with other hexen2 engines, at all. Most mods and maps should work though (its mostly just a glorified quake mod). For best results use the missionpack - it has numerous fixes for bugs in the original's gamecode.

https://fte.triptohell.info/readme
I am unable to enable split screen for Quake 3, am I doing something wrong?
Also, can we get FTE support for Quake 2 mission packs, Hexen 2?

@rea987 Not sure how it is supposed to work with Quake 3. I will look into quake 2 mission packs and hexen 2.

Done in https://github.com/luxtorpeda-dev/packages/commit/bab26ae69ef747a94336e988fb91d2df4ed72acf
Quake 2 Expansions and Hexen 2 has been added.


[Angular CLI] Reintroduce Angular CLI UI Recipe

In v1 of create-tauri-app, there used to be a UI recipe for generating an Angular project, which was quite useful.
v2 however does not seem to have it anymore.
I would love to see it come back!

I just made a pull request to add an Angular CLI template: https://github.com/tauri-apps/create-tauri-app/pull/167

Closing as it's now been added in release of 2.4 https://github.com/tauri-apps/create-tauri-app/releases/tag/create-tauri-app-v2.4.0 (thanks a bunch @eneajaho !)


Target SDK 33

Is your feature request related to a problem? Please describe.
Currently, keypass supports SDK 32.
Describe the solution you'd like
Keypass should support the lastest SDK, which is SDK 33.
There are several advantages privacy and security related by doing this: https://developer.android.com/about/versions/13/behavior-changes-13

Thanks, will bump in some time.

Bumped https://github.com/yogeshpaliyal/KeyPass/pull/251


Indicating compatibility with all Ops Manager versions 1.9+

@keitwb I'm not exactly sure what you are indicating by changing the version numbers from v1.9.x to V1.9.+ ?
I'm going to assume that you mean:
v1.9.x, v1.10.x, and v1.11.x  This is pretty standard in our docs.
I'll change it to that. Let me know if those are not the versions that signalfx works with.
Thanks!
Jane
cc @jknostman3

@jncd yes, that would be great if you could change it to those versions.  Thanks.


Add reindex in DataFrame

This PR adds DataFrame.reindex.
Resolves #421

cc @ueshin, @rxin, @tdliu

Codecov Report

Merging #493 into master will decrease coverage by 0.12%.
The diff coverage is 86.48%.

@@            Coverage Diff             @@
##           master     #493      +/-   ##
==========================================
- Coverage   93.71%   93.59%   -0.13%
==========================================
  Files          28       28
  Lines        3803     3839      +36
==========================================
+ Hits         3564     3593      +29
- Misses        239      246       +7

Impacted Files
Coverage Δ

databricks/koalas/missing/frame.py
100% <ø> (ø)
:arrow_up:

databricks/koalas/frame.py
94.72% <86.48%> (-0.4%)
:arrow_down:

databricks/conftest.py
92.85% <0%> (-3.58%)
:arrow_down:

databricks/koalas/__init__.py
89.65% <0%> (-3.45%)
:arrow_down:

Continue to review full report at Codecov.

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

Should be ready for a look.

tests passed


Add Standardized TPM handles

Instead of having to set the handles' values with each handshake, we have put them in a header file that sets a #define for each of the handles that we use.
Fixes #73.

Looks good to me. Nicely organized.
Would you rebase onto the current master, then I'll merge it.
Thanks!


Restrict Event Booking to Verified Users

fixes #298
This PR updates the authCustomer middleware to verify for the token and the isVerified field in the customer model.
Updated the frontend component to check for the cookie present in the application.

https://github.com/user-attachments/assets/a912aa7a-0514-4c6f-ba09-f0e58343e928

Summary by CodeRabbit
Release Notes

New Features

Updated contributors' section in the README to reflect current contributors.
Added authentication handling for event registration, prompting users to sign in if not authenticated.

Bug Fixes

Enhanced error handling for customer registration and verification processes.
Improved user verification checks in the authentication middleware.

Documentation

Revised contributor entries in the README file for accuracy.

Chores

Updated event router to include authentication middleware for event-related routes.

@haseebzaki-07 resolve the conflicts

hi @haseebzaki-07 can you repush the code
coz some problem occuers while running yml file
i going to revert this, don't worry you get your full points on the PR

okay @RamakrushnaBiswal I will do it


Agenda tool not readable in Dark mode

Describe the issue
Use the 117 link as a reference<EMAIL_ADDRESS>when the preference is set for the dark mode -

Code of Conduct

[X] I agree to follow the IETF's Code of Conduct

This was fixed by #6428.


Cleanbot AI sometimes doesn't work

Description

Even if I drag it onto the puddle, it just goes back to some random location (I don't think it's trying to find anything either) and walks back and forth
Screenshots

it works. probably your cleanbot was targeted at the puddle it saw before, or the puddle is under the girder as fellow cleanbot lover i can say cleanbot AI works, but sometime it looks stupid for us

yeah this pr is just saying that sometimes its dumb lol


[Feature Request]: Swapping Icon Versions

Describe the feature
Hey VSCode-Icon Team!
It's nice to see you're actively working on updating Icons.
Though since using Catppuccin VSC-Icons, I've gotten used to the old variants (pre 1.0) and prefer them over the new versions.
Could there be a feature to switch between old and new versions of the icons?
Like having a secondary option like "Catppuccin Macchiato (old)", where Icons of v0.33.0 are being used, as well as newly added icons and associations?
Thank you for your work!

The 0.x version was at first more of a "proof of concept" that took off more than i expected 😅
Could you specify the icons you were thinking about specifically ?
Not sure about keeping old things as part of the main project, but maybe some still need rework (im looking at you, C icons) or we could find a way for users to provide their own icons locally.

I definitly prefer the old versions of the C icons, and I am also unsure of what the new Java icon should resemble. ^^'
I haven't fully explored the new 1.0+ icons, as I haven't coded much lately and I am also not using many other languages, so I can't say about other icons.

I'll definitely change the C related icons as stated in #90
The java icon is Duke :) https://www.oracle.com/in/java/duke/

C icons were changed, i will close this as its hopefully resolved, feel free to reopen if you have further questions/wishes 😄


 Especially the two .py codes in ./dcr_v1/.

DCR-v1 is a stand-alone classification network aiming to suppress (hard) false positives in object detection. You can think DCR-v1 as a classifier and we use ResNet-152 in our paper. The input to DCR-v1 is a batch of images with size 3x224x224. Each image is a cropped proposal of base detector's output.
./dcr_v1/train_rcnn.py is used to train DCR-v1.
./dcr_v1/rcnn_rescore_combined_fast.py is used to combine DCR-v1 results with base detector's classification results (by simply multiplying two scores).

Hi @bowenc0221 ,
Can you please give me some ideas about how to process the different size ROI?
Thz

Thank you! I want to apply DCR-v1 on one-stage detector. Do you have some ideas about that?

Hi @hongdayu ,
ROIs are first cropped on the original image and resized to 224x224. You may find this code helpful.

Hi @KimSoybean ,
Since one-stage detectors produces much more boxes than two-stage detectors (typically 300 for Faster RCNN), you may need decide a trade-off on how many boxes you want to process and how to select these boxes.

Thank you！@bowenc0221

Hi @hongdayu ,
ROIs are first cropped on the original image and resized to 224x224. You may find this code helpful.

Thank you !!!

In sampling strategies, some pad_indexes are randomly sampled in all boxes or null (  pad_indexes=[] ). This causes there are same samples in positive and negative samples. Do i misunderstand that?

@KimSoybean
The padding is needed to form a fixed-size batch. For example, if batchsize=32 but we only sampled 30 boxes, then we just pad it to 32 boxes and assign label -1 (ignored during training) for the padded boxes.

Why you multiply two scores? This makes the original score become lower or do I misunderstand that?

@KimSoybean
The reason is that the new classifier (DCR) is trained without location information. If we only use the scores from DCR, we observe very poor performance (DCR becomes RCNN in this case, due to different sampling strategy, it performs worse than RCNN when used along).
Yes, multiplying two scores will make the final score become lower. However, it is a reranking process. DCR decreases scores of False Positives (FPs) by a larger amount than True Positives (TPs). This makes the relative ranking changes and more FPs are suppressed by a predefined threshold. In the final evaluation process, only the relative ranking matters.

Thanks! @bowenc0221. Have you trained DCR for more than 9 epochs ? Will the over-fitting happen? I want to know more details because I'm using DCR  for one-stage face detection.

@KimSoybean
I haven't trained it for more epochs. I simply trained the same number of epochs as used for training Faster RCNN and it might not be the optimal setting. However, I think overfitting might happen if you do not use any data augmentation. (one-stage detectors are trained for longer epochs because they have strong data augmentation)

Hi, I got another question for u~? how do you assign labels for the images handing to stage2 DCR model? (v1) is that exactly same as the standard of stage1?


Fix STO DB corruption on reorg

Fixes an issue where a reorg would corrupt the STO database due to a missing delimiter.
Minor code cleanup.

Nice! I'll give it a try within the next hours, but it looks good. :)

Quick update:
I'm currently adding/extending three RPC tests to cover the issues we recently discovered:

the issue you're fixing here :)
the missing reset of SP identifiers after reorg without persistence
the crowdsale participations, which were shown as simple sends


How can we stop KafkaReceiver when Ktor shutdowns?

Hi,
I'm trying to user KafkaReceiver inside Ktor 2. I'm not quite sure what is the best way to start KafkaReciever with Ktor.
What I did was to create an application plugin like the following and install it in Ktor engine.
import io.github.nomisRev.kafka.map
import io.github.nomisRev.kafka.receiver.AutoOffsetReset
import io.github.nomisRev.kafka.receiver.KafkaReceiver
import io.github.nomisRev.kafka.receiver.ReceiverSettings
import io.ktor.server.application.*
import io.ktor.server.application.hooks.*
import io.ktor.server.config.*
import kotlinx.coroutines.Dispatchers
import kotlinx.coroutines.coroutineScope
import kotlinx.coroutines.flow.map
import kotlinx.coroutines.launch
import kotlinx.coroutines.runBlocking
import org.apache.kafka.clients.CommonClientConfigs
import org.apache.kafka.common.config.SaslConfigs
import java.util.*

import org.apache.kafka.common.serialization.StringDeserializer
import org.apache.kafka.common.serialization.ByteArrayDeserializer

@JvmInline
value class Key(val key: String)

@JvmInline
value class Message(val content: String)

val EntityUpdateEventPlugin = createApplicationPlugin(name = "EntityUpdateEventPlugin") {
    on(MonitoringEvent(ApplicationStarted)) { application ->
        val topicName = "odm-entity-update-event"
        val environment = application.environment
        val bootstrapServers = environment.config.property("kafka.bootstrapServers").getString()
        val kafkaPropertiesConfig = environment.config.config("kafka.properties")
        val receiverProperties = Properties().apply {
            kafkaPropertiesConfig.propertyOrNull(CommonClientConfigs.SECURITY_PROTOCOL_CONFIG)?.let {
                this[CommonClientConfigs.SECURITY_PROTOCOL_CONFIG] = it.getString()
            }
            kafkaPropertiesConfig.propertyOrNull(SaslConfigs.SASL_JAAS_CONFIG)?.let {
                this[SaslConfigs.SASL_JAAS_CONFIG] = it.getString()
            }
            kafkaPropertiesConfig.propertyOrNull(SaslConfigs.SASL_MECHANISM)?.let {
                this[SaslConfigs.SASL_MECHANISM] = it.getString()
            }
        }

        runBlocking(Dispatchers.Default) {
            coroutineScope {
                launch(Dispatchers.IO) {
                    val settings: ReceiverSettings<Key, Message> = ReceiverSettings(
                        bootstrapServers,
                        StringDeserializer().map(::Key),
                        ByteArrayDeserializer().map {
                            Message(String(it))
                        },
                        groupId = "my-event-group",
                        autoOffsetReset = AutoOffsetReset.Earliest,
                        properties = receiverProperties
                    )
                    KafkaReceiver(settings)
                        .receive(topicName)
                        .map { "${it.key()} -> ${it.value()}" }
                        .collect {
                            application.log.info(it)
                        }
                }
            }
        }
    }
}

I seems the receiver starts and collects the messages. The question is how can we stop the receiver when Ktor shutdowns. When I stop the Ktor application it seems stuck and I have to kill the process.

I found a way to make it work. It seems runBlocking blocks the event loop of Ktor engine. The receiver and Ktor route handlers works fine if it is started in the following way:
on(MonitoringEvent(ApplicationStarted)) { application ->
  // .. code to initialise the receiver
  CoroutineScope(Dispatchers.IO).launch {
    receiver
        .receive("my-topic")
        .collect {
            application.log.info("${it.key()} -> ${it.value()}")
            it.offset.acknowledge()
        }
  }
}

I don't know which is the best way to start a receiver in Ktor.
@nomisRev Can you recommend or give us an example how to use it with Ktor?
Regards

Hey @ageorgousakis,
Thanks for your interest in the library, and opening a ticket! 🙏
As you've show there already, the returning Flow is coupled to it's surrounding CoroutineScope.
The simplest way to running a Flow for the same length as the server is to use launchIn with Application.
So to provide a small snippet:
val flow: Flow<Unit> = receiver
        .receive("my-topic")
        .map { // <-- changed collect to map, so the result is still a Flow
            application.log.info("${it.key()} -> ${it.value()}")
            it.offset.acknowledge()
        }

val application: Application = TODO("This is the Application from Ktor")
flow.launchIn(application)

The Ktor Application implements CoroutineScope, and it cancels the CoroutineScope_ when the server is cancelled. So it will also _cancel_ your Flow`.
NOTE: I've run into some issues where Ktor doesn't properly cancel on SIGINT from K8S for example, and I've therefor build suspendapp.
SuspendApp With Ktor and K8S
SuspendApp with Kafka.

Alternatively, you could also use ApplicationEngine#addShutdownHook and use it to manually control a CoroutineScope.
The take-away is the the Flow cancels with the CoroutineScope it's called from.
Hope that helps @ageorgousakis !
Let's leave this issue open, so it can serve as reminder to include this information it in the documentation 👍