Error: Could not find 'winrm'

I am getting after trying to execute a command in rundeck.
SYS INFO:
CentOS release 6.8 (Final)
Rundeck 2.7.3-1
rvm 1.29.1 (latest)
ruby-2.4.0 [ x86_64 ]
winrm (1.8.1)
winrm-fs (0.4.3)
/var/lib/rundeck/libext/rd-winrm-plugin-1.5.1.zip
ERROR:
/usr/local/rvm/rubies/ruby-2.4.0/lib/ruby/site_ruby/2.4.0/rubygems/dependency.rb:308:in to_specs': Could not find 'winrm' (= 1.8.1) among 18 total gem(s) (Gem::MissingSpecError) Checked in 'GEM_PATH=/.gem/ruby/2.4.0:/usr/local/rvm/rubies/ruby-2.4.0/lib/ruby/gems/2.4.0', execute gem envfor more information 	from /usr/local/rvm/rubies/ruby-2.4.0/lib/ruby/site_ruby/2.4.0/rubygems/dependency.rb:320:into_spec'
from /usr/local/rvm/rubies/ruby-2.4.0/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_gem.rb:65:in gem' 	from /var/lib/rundeck/libext/cache/rd-winrm-plugin-1.5.1/winrmexe.rb:2:in '
Failed: NonZeroResultCode: [WinRMexe] Result code: 1
Execution failed: 2 in project Test: [Workflow result: , step failures: {1=Dispatch failed on 1 nodes: [sarkistest: NonZeroResultCode: [WinRMexe] Result code: 1]}, Node failures: {sarkistest=[NonZeroResultCode: [WinRMexe] Result code: 1]}, status: failed]
gem env output
RubyGems Environment:

RUBYGEMS VERSION: 2.6.11
RUBY VERSION: 2.4.0 (2016-12-24 patchlevel 0) [x86_64-linux]
INSTALLATION DIRECTORY: /usr/local/rvm/gems/ruby-2.4.0
USER INSTALLATION DIRECTORY: /root/.gem/ruby/2.4.0
RUBY EXECUTABLE: /usr/local/rvm/rubies/ruby-2.4.0/bin/ruby
EXECUTABLE DIRECTORY: /usr/local/rvm/gems/ruby-2.4.0/bin
SPEC CACHE DIRECTORY: /root/.gem/specs
SYSTEM CONFIGURATION DIRECTORY: /usr/local/rvm/rubies/ruby-2.4.0/etc
RUBYGEMS PLATFORMS:

ruby
x86_64-linux

GEM PATHS:

/usr/local/rvm/gems/ruby-2.4.0
/usr/local/rvm/gems/ruby-2.4.0@global

GEM CONFIGURATION:

:update_sources => true
:verbose => true
:backtrace => false
:bulk_threshold => 1000

REMOTE SOURCES:

https://rubygems.org/

SHELL PATH:

/usr/local/rvm/gems/ruby-2.4.0/bin
/usr/local/rvm/gems/ruby-2.4.0@global/bin
/usr/local/rvm/rubies/ruby-2.4.0/bin
/usr/local/rvm/gems/ruby-2.4.0/bin
/usr/local/rvm/gems/ruby-2.4.0@global/bin
/usr/local/rvm/rubies/ruby-2.4.0/bin
/usr/local/sbin
/usr/local/bin
/sbin
/bin
/usr/sbin
/usr/bin
/usr/local/rvm/bin
/root/bin

Sorry, I don't know how much help I can be since we aren't activly using this plugin at the moment.
I suspect it might be a problem with ruby 2.4.0. Perhaps try and older version of ruby?

Unfortunately the older version of Ruby did not help

Ended up using https://github.com/rundeck-plugins/rundeck-winrm-plugin/releases/tag/v1.3.3
Thanks @spuder for your hlep!


Hello, I would like to collaborate on your project as a translator to Spanish which is my native language

How would that work ?

My intention is to translate the doc to spanish so it gets the atention of spanish speaking people, I'll make a new file of the translation and you'll merge the doc if you're happy with the results. let me know if you're interested. cheers!

@1stmetro


Dev

Implemented the BabyIAXO geometry, consisting on the detector chamber, copper pipe and lead shielding. This can be used to test a fairly complex and real use case.
I Also added the default value for deltaphi in the GdmlCone class, which I assume was not added before by mistake.

👍


Suggestion(s)

Hello,
I learned about your MicroBeast Computer Kit from Hacker News. From the few images I saw it looks great.
I wanted to make a suggestion - add a few tutorial videos to your website (or ask someone that is passionate about 8-bit computers to do it for you) e.g. how to build the kit, how to write a small program, build it and run it on the device, remote development from a more powerful machine. People will be more inclined to buy it if they see the computer in action.
(As a point of comparison, check how many videos are on YouTube about something like Agon Light 2 or RC2014. It could really help people decide if they want to buy and play with your device).
Best wishes,
Paul

Thanks - I would love to create some videos, but so far haven't had a moment spare to even begin.


[Debug View] strange timestamps

While working with git.exe and keeping the Debug View plugin Always on Top, I saw this strange time-stamp reported; the last (the other times are correct):

AFAICS, the time-stamp comes from entry->Time in plugins-extra/DbgViewPlugin/dialog.c. I'd suspect the date is bogus too. Not sure it's the fault of some system .DLL or ProcessHacker.

The DebugView plugin has weird issues sometimes... You should post the bug in the plugins-extra repro:
https://github.com/processhacker/plugins-extra/issues/53


Add the studio field

Inspired by the edX Zoom XBlock.

@OmarIthawi cool effort on this. Have comments though and the build is failing

Thanks @johnbaldwin, I've addressed your notes. I think now tests will pass. Please let me know if you have additional notes.

Looks like Travis is still failing. I tried to run tox locally but am getting the error

Please worry about tests failing as long as Travis catches them. I think it's more valuable to focus on the other part of the code reviews.

py36-django111 create: /Users/jbaldwin/work/appsembler/repos/course-access-groups/.tox/py36-django111
ERROR: InterpreterNotFound: python3.6
py36-django20 create: /Users/jbaldwin/work/appsembler/repos/course-access-groups/.tox/py36-django20
ERROR: InterpreterNotFound: python3.6

I have Python 3.6.10 installed with Pyenv. Do I need a different version of 3.6?

Yes. I think tox doesn't know about the pyenv pythons and it looks only for system-wide installations such as:
$ whereis python
python: /usr/bin/python2.7-dbg-config /usr/bin/python /usr/bin/python3.6 /usr/bin/python3.6m-config /usr/bin/python3.6m /usr/bin/python2.7-dbg /usr/bin/python3.6-config /usr/bin/python2.7-config /usr/bin/python2.7 /usr/lib/python3.6 /usr/lib/python3.8 /usr/lib/python3.7 /usr/lib/python2.7 /etc/python /etc/python3.6 /etc/python2.7 /usr/local/lib/python3.6 /usr/local/lib/python2.7 /usr/include/python3.6 /usr/include/python2.7_d /usr/include/python3.6m /usr/include/python2.7 /usr/share/python /opt/az/bin/python3.6 /opt/az/bin/python3.6m-config /opt/az/bin/python3.6m /opt/az/bin/python3.6-config /usr/share/man/man1/python.1.gz

Thanks Omar. I'll have to work on my local python environment to get tox to pass with Python 3.6. Meanwhile, LGTM, Approved!

Thanks John and Maxi!


⚠ ClamAV has degraded performance

In 5bcb4dc, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 78 ms

Resolved: ClamAV performance has improved in 915aa62 after 24 minutes.


Question, why is this an IOC Container

To be a dependency injection framework, it usually means inject an instance of class into another, but from readme, there seems to be no such action?

This is just a simple method to manage dependent providers, it is on the developer to find a proper way handling how to inject those providers into something like React components.
For example, we use React Context API for this purpose:
ReactDOM.render(
  <EntrancesContext.Provider value={entrances}>
    <App />
  </EntrancesContext.Provider>,
  document.getElementById('app'),
);

const App = () => {
  const {messageService} = useContext(EntrancesContext);

  // ...
};

I'm too young too simple to understand these...My university didn't teach me this.


Temporary users

Create temporary users that can access the server for a period of time

Duplicate of #581


Incremental PushContext initilization

Based on @rshriram's pr #16076, to implement incremental push context init.  Basically it is to make use of the old push context as much as possible. For example,  if a service updated, only reinitialize its related configs, services and sidecarscopes.
It is to improve the performance and scalability of the control plane.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

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

Test name
Commit
Details
Rerun command

lint_istio
39d86512d4d0b246a5fb115a5a171302850bf973
link
/test lint

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 them all:

Test name
Commit
Details
Rerun command

lint_istio
39d86512d4d0b246a5fb115a5a171302850bf973
link
/test lint

unit-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test unit-tests

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test unit-tests

e2e-mixer-no_auth_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test e2e-mixer-no_auth

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 them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test unit-tests

e2e-mixer-no_auth_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test e2e-mixer-no_auth

pilot-e2e-envoyv2-v1alpha3_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test pilot-e2e-envoyv2-v1alpha3

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 them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test unit-tests

e2e-mixer-no_auth_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test e2e-mixer-no_auth

pilot-e2e-envoyv2-v1alpha3_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test pilot-e2e-envoyv2-v1alpha3

integ-pilot-k8s-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test integ-pilot-k8s-tests

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test unit-tests

e2e-mixer-no_auth_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test e2e-mixer-no_auth

pilot-e2e-envoyv2-v1alpha3_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test pilot-e2e-envoyv2-v1alpha3

integ-pilot-k8s-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test integ-pilot-k8s-tests

e2e-bookInfoTests-envoyv2-v1alpha3_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

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 them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test unit-tests

e2e-mixer-no_auth_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test e2e-mixer-no_auth

pilot-e2e-envoyv2-v1alpha3_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test pilot-e2e-envoyv2-v1alpha3

integ-pilot-k8s-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test integ-pilot-k8s-tests

e2e-bookInfoTests-envoyv2-v1alpha3_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test e2e-bookInfoTests-trustdomain

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 them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test unit-tests

e2e-mixer-no_auth_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test e2e-mixer-no_auth

pilot-e2e-envoyv2-v1alpha3_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test pilot-e2e-envoyv2-v1alpha3

integ-pilot-k8s-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test integ-pilot-k8s-tests

e2e-bookInfoTests-envoyv2-v1alpha3_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test e2e-bookInfoTests-trustdomain

integ-mixer-k8s-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test integ-mixer-k8s-tests

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test unit-tests

e2e-mixer-no_auth_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test e2e-mixer-no_auth

pilot-e2e-envoyv2-v1alpha3_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test pilot-e2e-envoyv2-v1alpha3

integ-pilot-k8s-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test integ-pilot-k8s-tests

e2e-bookInfoTests-envoyv2-v1alpha3_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test e2e-bookInfoTests-trustdomain

integ-mixer-k8s-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test integ-mixer-k8s-tests

integ-security-k8s-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test integ-security-k8s-tests

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test unit-tests

e2e-mixer-no_auth_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test e2e-mixer-no_auth

pilot-e2e-envoyv2-v1alpha3_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test pilot-e2e-envoyv2-v1alpha3

integ-pilot-k8s-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test integ-pilot-k8s-tests

e2e-bookInfoTests-envoyv2-v1alpha3_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test e2e-bookInfoTests-trustdomain

integ-mixer-k8s-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test integ-mixer-k8s-tests

integ-security-k8s-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test integ-security-k8s-tests

pilot-multicluster-e2e_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test pilot-multicluster-e2e

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

did you do any perf testing if this?

no, i do not have the env as you did before with a great visualization.

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

Test name
Commit
Details
Rerun command

pilot-e2e-envoyv2-v1alpha3_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test pilot-e2e-envoyv2-v1alpha3

integ-pilot-k8s-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test integ-pilot-k8s-tests

e2e-bookInfoTests-envoyv2-v1alpha3_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test e2e-bookInfoTests-trustdomain

integ-mixer-k8s-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test integ-mixer-k8s-tests

integ-security-k8s-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test integ-security-k8s-tests

pilot-multicluster-e2e_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test pilot-multicluster-e2e

e2e-mixer-no_auth_istio
e0ee60daa7a14db4e3c1c140830759c0146546e7
link
/test e2e-mixer-no_auth

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 them all:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test integ-pilot-k8s-tests

e2e-bookInfoTests-envoyv2-v1alpha3_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test e2e-bookInfoTests-trustdomain

integ-mixer-k8s-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test integ-mixer-k8s-tests

integ-security-k8s-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test integ-security-k8s-tests

pilot-multicluster-e2e_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test pilot-multicluster-e2e

e2e-mixer-no_auth_istio
e0ee60daa7a14db4e3c1c140830759c0146546e7
link
/test e2e-mixer-no_auth

pilot-e2e-envoyv2-v1alpha3_istio
e0ee60daa7a14db4e3c1c140830759c0146546e7
link
/test pilot-e2e-envoyv2-v1alpha3

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 them all:

Test name
Commit
Details
Rerun command

e2e-bookInfoTests-envoyv2-v1alpha3_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test e2e-bookInfoTests-trustdomain

integ-mixer-k8s-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test integ-mixer-k8s-tests

integ-security-k8s-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test integ-security-k8s-tests

pilot-multicluster-e2e_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test pilot-multicluster-e2e

e2e-mixer-no_auth_istio
e0ee60daa7a14db4e3c1c140830759c0146546e7
link
/test e2e-mixer-no_auth

pilot-e2e-envoyv2-v1alpha3_istio
e0ee60daa7a14db4e3c1c140830759c0146546e7
link
/test pilot-e2e-envoyv2-v1alpha3

integ-pilot-k8s-tests_istio
e0ee60daa7a14db4e3c1c140830759c0146546e7
link
/test integ-pilot-k8s-tests

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

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

Test name
Commit
Details
Rerun command

e2e-bookInfoTests-trustdomain_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test e2e-bookInfoTests-trustdomain

integ-mixer-k8s-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test integ-mixer-k8s-tests

integ-security-k8s-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test integ-security-k8s-tests

pilot-multicluster-e2e_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test pilot-multicluster-e2e

e2e-mixer-no_auth_istio
e0ee60daa7a14db4e3c1c140830759c0146546e7
link
/test e2e-mixer-no_auth

pilot-e2e-envoyv2-v1alpha3_istio
e0ee60daa7a14db4e3c1c140830759c0146546e7
link
/test pilot-e2e-envoyv2-v1alpha3

integ-pilot-k8s-tests_istio
e0ee60daa7a14db4e3c1c140830759c0146546e7
link
/test integ-pilot-k8s-tests

e2e-bookInfoTests-envoyv2-v1alpha3_istio
e0ee60daa7a14db4e3c1c140830759c0146546e7
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

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 them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test integ-mixer-k8s-tests

integ-security-k8s-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test integ-security-k8s-tests

pilot-multicluster-e2e_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test pilot-multicluster-e2e

e2e-mixer-no_auth_istio
e0ee60daa7a14db4e3c1c140830759c0146546e7
link
/test e2e-mixer-no_auth

pilot-e2e-envoyv2-v1alpha3_istio
e0ee60daa7a14db4e3c1c140830759c0146546e7
link
/test pilot-e2e-envoyv2-v1alpha3

integ-pilot-k8s-tests_istio
e0ee60daa7a14db4e3c1c140830759c0146546e7
link
/test integ-pilot-k8s-tests

e2e-bookInfoTests-envoyv2-v1alpha3_istio
e0ee60daa7a14db4e3c1c140830759c0146546e7
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
e0ee60daa7a14db4e3c1c140830759c0146546e7
link
/test e2e-bookInfoTests-trustdomain

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 them all:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test integ-security-k8s-tests

pilot-multicluster-e2e_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test pilot-multicluster-e2e

e2e-mixer-no_auth_istio
e0ee60daa7a14db4e3c1c140830759c0146546e7
link
/test e2e-mixer-no_auth

pilot-e2e-envoyv2-v1alpha3_istio
e0ee60daa7a14db4e3c1c140830759c0146546e7
link
/test pilot-e2e-envoyv2-v1alpha3

integ-pilot-k8s-tests_istio
e0ee60daa7a14db4e3c1c140830759c0146546e7
link
/test integ-pilot-k8s-tests

e2e-bookInfoTests-envoyv2-v1alpha3_istio
e0ee60daa7a14db4e3c1c140830759c0146546e7
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
e0ee60daa7a14db4e3c1c140830759c0146546e7
link
/test e2e-bookInfoTests-trustdomain

integ-mixer-k8s-tests_istio
e0ee60daa7a14db4e3c1c140830759c0146546e7
link
/test integ-mixer-k8s-tests

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
8e1a48de747517219ee110da004cb975d1544d9c
link
/test integ-security-k8s-tests

e2e-mixer-no_auth_istio
e0ee60daa7a14db4e3c1c140830759c0146546e7
link
/test e2e-mixer-no_auth

pilot-e2e-envoyv2-v1alpha3_istio
e0ee60daa7a14db4e3c1c140830759c0146546e7
link
/test pilot-e2e-envoyv2-v1alpha3

integ-pilot-k8s-tests_istio
e0ee60daa7a14db4e3c1c140830759c0146546e7
link
/test integ-pilot-k8s-tests

e2e-bookInfoTests-envoyv2-v1alpha3_istio
e0ee60daa7a14db4e3c1c140830759c0146546e7
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
e0ee60daa7a14db4e3c1c140830759c0146546e7
link
/test e2e-bookInfoTests-trustdomain

integ-mixer-k8s-tests_istio
e0ee60daa7a14db4e3c1c140830759c0146546e7
link
/test integ-mixer-k8s-tests

pilot-multicluster-e2e_istio
e0ee60daa7a14db4e3c1c140830759c0146546e7
link
/test pilot-multicluster-e2e

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

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

Test name
Commit
Details
Rerun command

e2e-mixer-no_auth_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test e2e-mixer-no_auth

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 them all:

Test name
Commit
Details
Rerun command

e2e-mixer-no_auth_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test e2e-mixer-no_auth

pilot-e2e-envoyv2-v1alpha3_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test pilot-e2e-envoyv2-v1alpha3

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 them all:

Test name
Commit
Details
Rerun command

e2e-mixer-no_auth_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test e2e-mixer-no_auth

pilot-e2e-envoyv2-v1alpha3_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test pilot-e2e-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test e2e-bookInfoTests-trustdomain

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 them all:

Test name
Commit
Details
Rerun command

e2e-mixer-no_auth_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test e2e-mixer-no_auth

pilot-e2e-envoyv2-v1alpha3_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test pilot-e2e-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test e2e-bookInfoTests-trustdomain

integ-pilot-k8s-tests_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test integ-pilot-k8s-tests

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

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

Test name
Commit
Details
Rerun command

e2e-mixer-no_auth_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test e2e-mixer-no_auth

pilot-e2e-envoyv2-v1alpha3_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test pilot-e2e-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test e2e-bookInfoTests-trustdomain

integ-pilot-k8s-tests_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test integ-pilot-k8s-tests

e2e-bookInfoTests-envoyv2-v1alpha3_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

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 them all:

Test name
Commit
Details
Rerun command

e2e-mixer-no_auth_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test e2e-mixer-no_auth

pilot-e2e-envoyv2-v1alpha3_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test pilot-e2e-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test e2e-bookInfoTests-trustdomain

integ-pilot-k8s-tests_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test integ-pilot-k8s-tests

e2e-bookInfoTests-envoyv2-v1alpha3_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

integ-mixer-k8s-tests_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test integ-mixer-k8s-tests

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

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

Test name
Commit
Details
Rerun command

e2e-mixer-no_auth_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test e2e-mixer-no_auth

pilot-e2e-envoyv2-v1alpha3_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test pilot-e2e-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test e2e-bookInfoTests-trustdomain

integ-pilot-k8s-tests_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test integ-pilot-k8s-tests

e2e-bookInfoTests-envoyv2-v1alpha3_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

integ-mixer-k8s-tests_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test integ-mixer-k8s-tests

pilot-multicluster-e2e_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test pilot-multicluster-e2e

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

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

Test name
Commit
Details
Rerun command

pilot-e2e-envoyv2-v1alpha3_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test pilot-e2e-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test e2e-bookInfoTests-trustdomain

integ-pilot-k8s-tests_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test integ-pilot-k8s-tests

e2e-bookInfoTests-envoyv2-v1alpha3_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

integ-mixer-k8s-tests_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test integ-mixer-k8s-tests

pilot-multicluster-e2e_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test pilot-multicluster-e2e

e2e-mixer-no_auth_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test e2e-mixer-no_auth

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 them all:

Test name
Commit
Details
Rerun command

e2e-bookInfoTests-trustdomain_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test e2e-bookInfoTests-trustdomain

integ-pilot-k8s-tests_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test integ-pilot-k8s-tests

e2e-bookInfoTests-envoyv2-v1alpha3_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

integ-mixer-k8s-tests_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test integ-mixer-k8s-tests

pilot-multicluster-e2e_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test pilot-multicluster-e2e

e2e-mixer-no_auth_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test e2e-mixer-no_auth

pilot-e2e-envoyv2-v1alpha3_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test pilot-e2e-envoyv2-v1alpha3

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 them all:

Test name
Commit
Details
Rerun command

e2e-bookInfoTests-trustdomain_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test e2e-bookInfoTests-trustdomain

integ-pilot-k8s-tests_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test integ-pilot-k8s-tests

integ-mixer-k8s-tests_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test integ-mixer-k8s-tests

pilot-multicluster-e2e_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test pilot-multicluster-e2e

e2e-mixer-no_auth_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test e2e-mixer-no_auth

pilot-e2e-envoyv2-v1alpha3_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test pilot-e2e-envoyv2-v1alpha3

e2e-bookInfoTests-envoyv2-v1alpha3_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

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 them all:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test integ-pilot-k8s-tests

integ-mixer-k8s-tests_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test integ-mixer-k8s-tests

pilot-multicluster-e2e_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test pilot-multicluster-e2e

e2e-mixer-no_auth_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test e2e-mixer-no_auth

pilot-e2e-envoyv2-v1alpha3_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test pilot-e2e-envoyv2-v1alpha3

e2e-bookInfoTests-envoyv2-v1alpha3_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test e2e-bookInfoTests-trustdomain

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 them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test integ-mixer-k8s-tests

pilot-multicluster-e2e_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test pilot-multicluster-e2e

e2e-mixer-no_auth_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test e2e-mixer-no_auth

pilot-e2e-envoyv2-v1alpha3_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test pilot-e2e-envoyv2-v1alpha3

e2e-bookInfoTests-envoyv2-v1alpha3_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test e2e-bookInfoTests-trustdomain

integ-pilot-k8s-tests_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test integ-pilot-k8s-tests

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

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

Test name
Commit
Details
Rerun command

pilot-multicluster-e2e_istio
77dc10495fab8ae25e3a9ce41c8339a7150d2e78
link
/test pilot-multicluster-e2e

e2e-mixer-no_auth_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test e2e-mixer-no_auth

pilot-e2e-envoyv2-v1alpha3_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test pilot-e2e-envoyv2-v1alpha3

e2e-bookInfoTests-envoyv2-v1alpha3_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test e2e-bookInfoTests-trustdomain

integ-pilot-k8s-tests_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test integ-pilot-k8s-tests

integ-mixer-k8s-tests_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test integ-mixer-k8s-tests

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

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

Test name
Commit
Details
Rerun command

e2e-mixer-no_auth_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test e2e-mixer-no_auth

pilot-e2e-envoyv2-v1alpha3_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test pilot-e2e-envoyv2-v1alpha3

e2e-bookInfoTests-envoyv2-v1alpha3_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test e2e-bookInfoTests-trustdomain

integ-pilot-k8s-tests_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test integ-pilot-k8s-tests

integ-mixer-k8s-tests_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test integ-mixer-k8s-tests

pilot-multicluster-e2e_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test pilot-multicluster-e2e

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

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

Test name
Commit
Details
Rerun command

e2e-mixer-no_auth_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test e2e-mixer-no_auth

pilot-e2e-envoyv2-v1alpha3_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test pilot-e2e-envoyv2-v1alpha3

e2e-bookInfoTests-envoyv2-v1alpha3_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

e2e-bookInfoTests-trustdomain_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test e2e-bookInfoTests-trustdomain

integ-pilot-k8s-tests_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test integ-pilot-k8s-tests

integ-mixer-k8s-tests_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test integ-mixer-k8s-tests

pilot-multicluster-e2e_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test pilot-multicluster-e2e

unit-tests_istio
0bb7b15f2058e7a8cd9dde847cf0e97e32aca201
link
/test unit-tests

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

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

Test name
Commit
Details
Rerun command

pilot-multicluster-e2e_istio
156c38d0be35b60da73142ef8cbb8600bed4a693
link
/test pilot-multicluster-e2e

unit-tests_istio
0bb7b15f2058e7a8cd9dde847cf0e97e32aca201
link
/test unit-tests

integ-mixer-k8s-tests_istio
0bb7b15f2058e7a8cd9dde847cf0e97e32aca201
link
/test integ-mixer-k8s-tests

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

/retest

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

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
0bb7b15f2058e7a8cd9dde847cf0e97e32aca201
link
/test integ-mixer-k8s-tests

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

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

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
0bb7b15f2058e7a8cd9dde847cf0e97e32aca201
link
/test integ-mixer-k8s-tests

gencheck_istio
9f016a36f530c7a464d7b2deee2c788422792037
link
/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 them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
0bb7b15f2058e7a8cd9dde847cf0e97e32aca201
link
/test integ-mixer-k8s-tests

gencheck_istio
9f016a36f530c7a464d7b2deee2c788422792037
link
/test gencheck_istio

integ-new-install-k8s-tests_istio
9f016a36f530c7a464d7b2deee2c788422792037
link
/test integ-new-install-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.

/test gencheck_istio


Enable Token Price History without History Module

Issue:
Currently token price history is only enabled if history module is enabled.
There will be networks that don't require history and I would like to retrieve their token price history in order to display a 7 day chart.
Implementation:
Separate Token Price History from history. Log the price once a day (seriously once a day should be enough)

@ryuash currently there's only storing price in history module, can we say we just remove history module and store the price history every 30 secs as usual?

Every 30 seconds is a bit extreme for ui's use-case.
I just want the price once a day but I would have to search through 2880 rows for each day. 2880 * 7 just to get 7 days of price history.
I don't mind logging them all back in to token_price table but i believe x has already switched to token_price_history

I think we can add it to the pricefeed module to query the price once a day and store it inside new daily_token_price_history table. This way we keep history module optional to enable for users.

Can we default this to hourly instead?
Both BD and X does not need it every 30 seconds - 2 minutes and just logging once per hour is more than enough. I've confirmed with @calvinkei
Implementation

Add a frequency config specifically for tokens that defaults to every hour
Enable this by default in token module or create a token_history module
Keep the data in token_price_history table

I don't see any usecase for such high frequency as we are not coin gecko and I don't see the point of creating a new table as it's still considered history.


Improve error messages when v1 and v2 namespaces are mixed accidentally

Initial Checks

[X] I have searched Google & GitHub for similar requests and couldn't find anything
[X] I have read and followed the docs and still think this feature is missing

Description
Pydantic ships both v1 and v2 namespaces, but does not support intermixing the namespaces. Unfortunately, intermixing may happen frequently as many libraries use Pydantic under the hood and either user or library code may be using .v1 or the .v2 namespace.
Generally, the error messages are incomprehensible when the namespaces are mixed: https://github.com/langchain-ai/langchain/discussions/24405#discussioncomment-10222989
Here's one simple reproduction with pydantic 2.9.2
from pydantic import BaseModel
from pydantic.v1 import BaseModel as BM1

class Foo(BM1):
    x: int

class Bar(BaseModel):
    foo: Foo

Bar(
    foo=Foo(
        x=5
    )
)

Error trace:
  File "/home/eugene/src/sandbox/pydantic/example/f4.py", line 12, in <module>
    Bar(
  File "/home/eugene/.pyenv/versions/core_3_11_4/lib/python3.11/site-packages/pydantic/main.py", line 212, in __init__
    validated_self = self.__pydantic_validator__.validate_python(data, self_instance=self)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: BaseModel.validate() takes 2 positional arguments but 3 were given

Apologies if this was already handled in pydantic 2.10
Affected Components

[ ] Compatibility between releases
[ ] Data validation/parsing
[ ] Data serialization - .model_dump() and .model_dump_json()
[ ] JSON Schema
[ ] Dataclasses
[ ] Model Config
[ ] Field Types - adding or changing a particular data type
[ ] Function validation decorator
[ ] Generic Models
[ ] Other Model behaviour - model_construct(), pickling, private attributes, ORM mode
[ ] Plugins and integration with other tools - mypy, FastAPI, python-devtools, Hypothesis, VS Code, PyCharm, etc.

@eyurtsev,
Thanks for the request. We've improved these on main and the improvements will soon be released in v2.10.0b1.
Here's the new behavior:
from pydantic import BaseModel
from pydantic.v1 import BaseModel as BM1

class Foo(BM1):
    x: int

class Bar(BaseModel):
    foo: Foo

Bar(
    foo=Foo(
        x=5
    )
)
"""
/Users/programming/pydantic_work/pydantic/pydantic/_internal/_generate_schema.py:771: UserWarning: Mixing V1 models and V2 models (or constructs, like `TypeAdapter`) is not supported. Please upgrade `Foo` to V2.
"""

Going to mark this as resolved for now. Feel free to test against main and let us know if you're still having any issues 👍


Rebalance mod following v1.2 StS changes

Slay The Spire is being updated and that means relics being shuffled around in rarity (plus Fire Breathing got a rework!). So, all my relics probably will need some buff/nerfing, and possibly the Weakest cards too.
Initial list of changes: https://www.reddit.com/r/slaythespire/comments/d21tcj/compilation_of_beta_changes_992019/

? Buff Weakest Fighting Style: Weakest Block add 1 extra Block;
? Buff Wrestler's Cloak: throwing the Cloak gives 8 Temp HP instead of 5;

Given recent changes, there will be a LOT of buffing...

Stuff to consider (got from the Beta patch notes):
1 - Sacred Bark relic makes all Potions I made need a (what if double effect).
2 - Buff Cattail, since some Boss relics are now Common/Uncommon/Shop. (even if I wouldn't get that relic, it's not my style)
3 - "Manual and auto line break mode for card descriptions enabled for JPN/ZHS languages." <- Use this to fix stuff of the beta.
4 - Make Potions to appear once certain relics are with the player, as an Easter Egg?
4.1 - Make Elixir appear rarely as an extra potion if the player has Rainbow Paint.
4.2 - Make Rainbow Potion for the Rainbow Relic: choose one of 5 cards of any good color. It costs 0 this turn.
4.3 - Make "Distilled Nothing" potion: the next card you would use does nothing instead. Can't be discarded.
5 - Given the power of new Potions, BUFF all the relics of this mod.
6 - Make an uncommon event for those Potions, them being one of two prizes. (The Architect/Potion maker/I don't know who competition event?) (Pick one option, be hurt by the other option)
7 - Add greying out when the relic effect has been triggered.
8 - Change flask shape of the three potions.


Eagle cleaning

Put back the data directory management.
Adapt it to EAGLE dataset
Put back the images in the datasets

Note that to import the dataset one should now to:
from sfh.datasets import  tng100, eagle

Les datasets sont générés sans problème.


Read Function Doesn't throw Error When Adapter Is Uunplugged

Linux Amd64 When Serial Adaptor is unplugged no error is received to signify device is unavailable.
Only way to tell if device is detached is with the Write function.

I have the same issue... could fix this?

Me too!


Import button not prominent enough

I went back and deleted the resource and started again.  This time I used a small image
(worked)
and clicked Save after checking the "Column headings" box (which wasn't obvious to
me as
something I had to do before).  When I finished mapping my concepts, I selected Done
rather than
Save but was unsure what to expect with the two buttons.  I then went to view the resource
and
found I still had a core record count of zero.  I therefore re-edited the mapping and
selected Save
but saw no difference in what was shown.  It was then that I found the Upload link.
 It was unclear
exactly what Upload would mean (would it upload data directly to GBIF central?), but
I clicked it.
After that I saw what I expected.

Perhaps inline documentation will be needed soon?

Original issue reported on code.google.com by timrobertson100 on 2009-04-01 07:04:33

This issue related to IPT version 1, and was reopened accidentally while migrating issues from Google Code. Closing.


missing render of search skill

The UI doesnt have the proper render when is a search skill

There are multiple levels of the sample application that increase in both power and complexity. This app is purposely kept simple so it is easy to understand the code without too much complexity.
https://github.com/watson-developer-cloud/assistant-intermediate


Reorganize documentation to be more friendly to newbies

The documentation is in a big pile right now and I think it could benefit from being broken up into multiple pages. I was thinking something like below, with the first level being pages and the second level being sections.

About Oak

What is Oak?
Publications and Credibility

Getting Oriented

The Goal of Oak
Screencasts and Feature List

Getting Setup

Prerequisites
Using Chocolatey

Getting Oak

Bootstrapped solution
Git download
Nuget

Getting Started

Running Oak
Rake Commands
Interactive tutorial

Growl

Sample Apps
Going Beyond
Troubleshooting

Configuring SQL Express
Error: The Type or namespace 'Ajax' does not exist

I also think it'd be good to flesh out the readme just a little bit more, even if that means a little redundancy.
I'm definitely open to feedback on this.

I'd like to start with the readme's that might be a good idea. The homepage has become a "big really bad list" (and not in a good way).

So are we talking bulk up the readme enough for the essentials or are we talking about having multiple .md files for documentation? If it's the latter, I'm not 100% sure how traditional projects handle that. As in, where do we want to keep those files?

I was thinking multiple. One readme per sample app and on at the top? May a readme in every project folder so people understand what it's there for?

Ah, that works. I'll start on the pull request next week. Once I've got something going we can take a look.

That's awesome man. Thank you :-)


Possible avenues for further optimization

Not really an issue but this seemed the best place to record what I have found while optimizing voxblox over the last two weeks.
Overall, currently the fast and simple integrators are badly memory bound. While there are a hundred little tweaks/hacks to make them use less CPU, they won't go any faster without reading or writing less data (or vectorizing the reads/writes). The merged integrator does not currently seem to suffer from this same limitation.
Below is a list of possible ways to speed things up and my findings from running some quick tests. Listed roughly in order of viability.

Switch to floats as the FloatingPoint
The fast integrator is badly memory bound, and so while this makes no difference for the merged integrator, for 5cm voxels the fast integrator speeds up by over 30%.

Use fast-math
Initially this put nans in voxel distances, this was fixed by checking if weights were near zero before dividing by them.
Same quick tests gave very small improvement maybe 1-5% faster. This will mostly be coming from the std::floor instruction in transforming coordinates to indexes. Without fast-math floor needs to handle nans and infs in a correct manner that makes it surprisingly expensive.

Switch the underlying hash-map
Looked at a large range of ones on the Internet. I tested them by having them store voxel indexes for 15 seconds and found the per scan time. This was a quite quick test, so don't take these numbers as perfect.

Just looping through all the points without actually casting any rays: 6 ms
Our current std::unordered_map 159 ms
libcuckoo (https://github.com/efficient/libcuckoo)
A concurrent hash map implementation. Note that each thread uses 100% of its core in this test
running in 1 thread: 187 ms
running in 2 threads: 147 ms
running in 4 threads: 114 ms
running in 8 threads: 100 ms
running in 4 threads, and mixing up the order the threads get the indexes: 87 ms
google dense_hash_map (https://github.com/sparsehash/sparsehash)
Well known, but also very memory heavy can take over 4x more than std::unordered_map. Also needs a null hash
run time: 76 ms
flat_hash_map (https://github.com/skarupke/flat_hash_map)
Written by some random guy on a blog, fastest in the test but c++14 only
run time: 73 ms
hopscotch-map (https://github.com/Tessil/hopscotch-map)
Drop in replacement for std::unordered_map that also lets you reuse the hash
run time: 78 ms
junction (https://github.com/preshing/junction/tree/master/junction)
Another concurrent hash_map, claims to be much faster than libcuckoo I could not get it to compile with our code.
boost and intel also have some hashmaps, but every chart and benchmark I saw put them much slow than those listed above.
From the tests I like hopscotch-map as it is almost as fast as the others, is header only, pretty good on ram and has no special conditions.
On testing on our actual situation it seems it could give somewhere between a 5 to 10% performance boost, maybe more if we use its hash lookup options.

Using more experimental compiler flags
Tried profile guided optimization and all these flags -march=native -fassociative-math -fno-signed-zeros -freciprocal-math -frename-registers -funroll-loops -fopenmp -D_GLIBCXX_PARALLEL
Speed gain was less than 1% if any.

using Eigens experimental AlignedVector3 (basicly a wrapper round a vector4) wherever we use indexes.
In some quick tests made things slightly slower, guess this will be due to it making memory bandwidth issues worse.

I had another look at this today and the difference -ofast and hopscotch-map makes is extremely minor on the current setup. Closing issue as most suggestions in it have been done or aren't worth it.


Performance testing problem

Hi
i bulid a version base on dragonboat-example/helloworld,   Dragonboat can just sustain writes at 14 w/s when payload is 16 bytes each.
1.389829122s 6.949 micros/op, 143902.58 op/s, 0.000000 err/rate
It is quite different from that in the document（Dragonboat can sustain writes at 1.25 million per second when payload is 16 bytes each, Can you provide your pressure test program or give some suggestions to me ？
rc := config.Config{
	// ClusterID and NodeID of the raft node
	NodeID:    uint64(*nodeID),
	ClusterID: exampleClusterID,
	// In this example, we assume the end-to-end round trip time (RTT) between
	// NodeHost instances (on different machines, VMs or containers) are 200
	// millisecond, it is set in the RTTMillisecond field of the
	// config.NodeHostConfig instance below.
	// ElectionRTT is set to 10 in this example, it determines that the node
	// should start an election if there is no heartbeat from the leader for
	// 10 * RTT time intervals.
	ElectionRTT: 10,
	// HeartbeatRTT is set to 1 in this example, it determines that when the
	// node is a leader, it should broadcast heartbeat messages to its followers
	// every such 1 * RTT time interval.
	HeartbeatRTT: 1,
	CheckQuorum:  true,
	// SnapshotEntries determines how often should we take a snapshot of the
	// replicated state machine, it is set to 10 her which means a snapshot
	// will be captured for every 10 applied proposals (writes).
	// In your real world application, it should be set to much higher values
	// You need to determine a suitable value based on how much space you are
	// willing use on Raft Logs, how fast can you capture a snapshot of your
	// replicated state machine, how often such snapshot is going to be used
	// etc.
	SnapshotEntries: 6000000,
	// Once a snapshot is captured and saved, how many Raft entries already
	// covered by the new snapshot should be kept. This is useful when some
	// followers are just a little bit left behind, with such overhead Raft
	// entries, the leaders can send them regular entries rather than the full
	// snapshot image.
	CompactionOverhead: 1000000,
}

@enefuture
Please note that -

you should be using the same hardware & benchmark program (which is never released) when reproducing the claimed benchmark.
dragonboat's provided example program is not for benchmarking purposes, I believe the code & docs contain such explanations.

for the extremely low throughput you are seeing, please check what is your disk's fsync performance. Note that home grade NVME SSDs are known to be slow, all MacBook Pro laptops tested so far also come with SSDs with slow fsync performance.

@lni I experience the same with the ondisk example. Only 6 comitted sync proposes per second are possible on my new Macbook Pro.  Any hints how to tune it or how to run the benchmarks shown in the graphs?
Thanks!

@SebastianM any chance you can run the same program on a different machine, say on a linux machine with ssd?

@lni I ran it on two linux machines now:

A small 512 MB Ram Droplet on DigitalOcean with an SSD
My desktop machine with an AMD Ryzen 7 3700X (16) @ 3.600GHz and a fast Samsung NVMe SSD and Arch Linux

On the DigitalOcean VM I got at best 700 sync proposes per second. After a few minutes, one node chrashed with a panic:
panic: lastApplied not moving forward

goroutine 187 [running]:
main.(*DiskKV).Update(0xc0007a9ce0, 0xc0001568c0, 0x1, 0x1, 0x0, 0x0, 0x0, 0x0, 0x0)
	/Users/Sebastian.Holstein/_personal_projects/dragonboat-example/ondisk/diskkv.go:402 +0x53e
github.com/lni/dragonboat/v3/internal/rsm.(*OnDiskStateMachine).Update(0xc000156880, 0xc0001568c0, 0x1, 0x1, 0xc001adccc0, 0x3a, 0x40, 0x0, 0x0)
	/Users/Sebastian.Holstein/go/pkg/mod/github.com/lni/dragonboat/v3@v3.3.1/internal/rsm/adapter.go:295 +0x5b

On my linux desktop machine I achieved only ~400 per second, which I didn't expected compared to an $5 VM.
Here's the modified code of the main.go. The rest of the example code is the same. Am I doing anything wrong here?:
// Copyright 2017,2018 Lei Ni (nilei81@gmail.com).
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
//     http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.

/*
ondisk is an example program for dragonboat's on disk state machine.
*/
package main

import (
	"context"
	"encoding/json"
	"flag"
	"fmt"
	"log"
	"math/rand"
	"os"
	"os/signal"
	"path/filepath"
	"runtime"
	"strconv"
	"sync/atomic"
	"syscall"
	"time"

	"github.com/lni/dragonboat/v3"
	"github.com/lni/dragonboat/v3/config"
	"github.com/lni/dragonboat/v3/logger"
	"github.com/lni/goutils/syncutil"
)

type RequestType uint64

const (
	exampleClusterID uint64 = 128
)

const (
	PUT RequestType = iota
	GET
)

var (
	// initial nodes count is fixed to three, their addresses are also fixed
	addresses = []string{
		"localhost:63001",
		"localhost:63002",
		"localhost:63003",
	}
)

func printUsage() {
	fmt.Fprintf(os.Stdout, "Usage - \n")
	fmt.Fprintf(os.Stdout, "put key value\n")
	fmt.Fprintf(os.Stdout, "get key\n")
}

var rps uint64
var rpsErr uint64

func main() {
	nodeID := flag.Int("nodeid", 1, "NodeID to use")
	addr := flag.String("addr", "", "Nodehost address")
	join := flag.Bool("join", false, "Joining a new node")
	flag.Parse()
	if len(*addr) == 0 && *nodeID != 1 && *nodeID != 2 && *nodeID != 3 {
		fmt.Fprintf(os.Stderr, "node id must be 1, 2 or 3 when address is not specified\n")
		os.Exit(1)
	}
	// https://github.com/golang/go/issues/17393
	if runtime.GOOS == "darwin" {
		signal.Ignore(syscall.Signal(0xd))
	}
	initialMembers := make(map[uint64]string)
	if !*join {
		for idx, v := range addresses {
			initialMembers[uint64(idx+1)] = v
		}
	}
	var nodeAddr string
	if len(*addr) != 0 {
		nodeAddr = *addr
	} else {
		nodeAddr = initialMembers[uint64(*nodeID)]
	}
	fmt.Fprintf(os.Stdout, "node address: %s\n", nodeAddr)
	logger.GetLogger("raft").SetLevel(logger.ERROR)
	logger.GetLogger("rsm").SetLevel(logger.ERROR)
	logger.GetLogger("transport").SetLevel(logger.ERROR)
	logger.GetLogger("grpc").SetLevel(logger.ERROR)
	logger.GetLogger("dragonboat").SetLevel(logger.ERROR)
	rc := config.Config{
		NodeID:             uint64(*nodeID),
		ClusterID:          exampleClusterID,
		ElectionRTT:        10,
		HeartbeatRTT:       1,
		CheckQuorum:        true,
		SnapshotEntries:    10000,
		CompactionOverhead: 5,
	}
	datadir := filepath.Join(
		"example-data",
		"helloworld-data",
		fmt.Sprintf("node%d", *nodeID))
	nhc := config.NodeHostConfig{
		WALDir:         datadir,
		NodeHostDir:    datadir,
		RTTMillisecond: 10,
		RaftAddress:    nodeAddr,
	}
	nh, err := dragonboat.NewNodeHost(nhc)
	if err != nil {
		panic(err)
	}
	if err := nh.StartOnDiskCluster(initialMembers, *join, NewDiskKV, rc); err != nil {
		fmt.Fprintf(os.Stderr, "failed to add cluster, %v\n", err)
		os.Exit(1)
	}
	raftStopper := syncutil.NewStopper()
	consoleStopper := syncutil.NewStopper()
	consoleStopper.RunWorker(func() {
		for {
			log.Println("RPS", rps, "errors", rpsErr)
			atomic.SwapUint64(&rps, 0)
			atomic.SwapUint64(&rpsErr, 0)
			time.Sleep(time.Second)
		}
	})
	printUsage()
	raftStopper.RunWorker(func() {
		time.Sleep(time.Second * 10)
		log.Println("Start")
		cs := nh.GetNoOPSession(exampleClusterID)
		ctx := context.Background()
		for i := 0; i < 5; i++ {
			go func() {
				for {
					ctx, cancel := context.WithTimeout(ctx, time.Second*3)
					data := strconv.Itoa(int(rand.Uint64()))
					kv := &KVData{
						Key: data,
						Val: data,
					}
					b, _ := json.Marshal(kv)
					_, err = nh.SyncPropose(ctx, cs, b)
					cancel()
					if err == nil {

						atomic.AddUint64(&rps, 1)
					} else {

						atomic.AddUint64(&rpsErr, 1)
					}
				}
			}()

		}
		select {}
	})
	raftStopper.Wait()
}

@SebastianM I'd willing to bet that your SAMSUNG nvme SSD is a consumer grade one. fsync performance of such consumer grade SSDs are in general terrible. Please see some test results below.
https://www.percona.com/blog/2018/02/08/fsync-performance-storage-devices/
I will look into that panic issue, it seems to be from the example code.

Note that Pebble (the default LogDB implementation) is particularly slow on MacOS (darwin) OS. To be precise the fsync operation is terribly slow.

Hello, I built up on an existing benchmark and deployed it to an AWS r5dn.large instance. The log is configured to be in-memory. Three raft nodes are deployed. I also disabled snapshotting and log compaction.
From my testings, the reads generally were around 70% slower than etcd. The writes even take more than twice as long as etcd or hashicorp.
@lni Do you see any flaws in the way the key-value store is implemented? You find the code under: https://github.com/alexanderstephan/raft-bench/tree/master/dragonboat
I will provide some graphs with more details soon.

@alexanderstephan It appears that your benchmarks are making local reads in etcd and linearlizable reads in dragonboat.
Using ReadLocalNode rather than SyncRead in the dragonboat benchmark would be a more fair comparison for reads.
https://pkg.go.dev/github.com/lni/dragonboat/v4#NodeHost.ReadLocalNode
As for writes, your etcd raft node is configured to make asynchronous writes. You push a value to a channel without waiting for confirmation that the proposal was committed or applied.
Your dragonboat node, on the other hand, is configured to make synchronous writes. SyncPropose will not return until the proposed entry has been committed and applied.

These two examples are operating at different levels of durability and consistency. Your etcd raft configuration does not guarantee that proposals are accepted, nor that they have been applied. Proposals may be lost and values that do get written are not guaranteed to be available on subsequent reads since reads are local and writes only guarantee that the proposals have been committed and will eventually be applied. Your dragonboat example, in contrast, provides both of these guarantees and is truly linearizable. As such, it's not surprising that their performance differs.
Relaxing durability and consistency is a pretty easy way to improve performance. Dragonboat has methods to help build systems with lower consistency requirements (ie. ReadLocalNode, NotifyCommit

@kevburnsjr Thanks so much, that must explain it! I actually have implemented mechanisms to await proposals and retry logic for etcd in another project, but completely forgot about it here... Hashicorp was even faster than etcd, but as it turns out it is also configured to be async.
I will extend the benchmarks based on your suggestions. I am really curious about the changes in the result.
Btw, are you aware of any other direct performance comparison between etcd, hashicorp and dragonboat or this something new? I was a bit puzzled that I have not found anything in this regard.

Thanks @kevburnsjr for the detailed insight above.
With etcd (last checked maybe 12 months ago), it comes with a reasonably efficient log storage implementation designed for a small number of raft shards. It becomes pretty much unusable when you increase the shard count to say hundreds or a couple thousand as each of them will require its own log storage file that must be be fsynced for each write. You end up with hundreds of slow fsync calls when you make a proposal to each of those shards. On comparison, a small fixed & configurable number of fsyncs (up to 16 by default) will be called in dragonboat when writing to thousands of shards.
It also lacks facilities to efficiently handle large number of concurrent requests from large number of clients.
All these are related to the pipelining and batching features in dragonboat, as explained by @kevburnsjr above. In my opinion, it is a pretty essential feature to have, as you can't expect most users to build their own execution pipeline or internal batching for logging.
Note that this is not aimed to argue which one is better, just want to let people know the difference.


DeviceManager.DeviceByID can't find device until enumerate is called

Looking through the core source I realize this is expected.
The other bindings (at least what I looked at) do not provide a method similar to this, most involve instantiating DeviceManager in a function and or finding a shared one and then simply returning a device. Similar to the frida.GetDeviceById in this module.
So in this case DeviceManager.DeviceByID should either enumerate the devices or at the very at least in the doc string express that before calling DeviceByID that the deviceManager must first enumerate the devices.
I'd be happy to provide a PR for either direction.
Cheers!

Hey, I want to keep the Frida.GetDeviceById so that the user has the options to either follow the usual route(get device manager, enumerate devices and select the device) or they can grab it right away (doing the work in the background).
Based on all of this, I would much rather keep it the way it is right now, and you are right, doc string should be updated to let the user know.


Email Server Validation

Would you be able to provide more documentation on email notifier configuration? I am not receiving any emails and have no idea what properties are required and if there are any issues being logged.
Thanks,

Same here. I'm setting the options, but no emails are coming through.
var errorMailOptions = _configuration.GetSection("errorMailOptions").Get();
services.AddElmah(options =>
{
options.ApplicationName = "Web API";
options.ConnectionString = configuration.GetSection("ConnectionStrings")"SomeConnection"];
options.Notifiers.Add(new ErrorMailNotifier("Email", errorMailOptions));
});


Documentation: update docs for podmaster removal

cc @aaronlevy @robszumski @joshix
Podmaster was removed in #355 because of the new --leader-elect flag. I updated the docs to reflect this.

LGTM, but I'd wait on @robszumski or @joshix to okay the doc changes

Merged the two update sections since everything is basically updated in the same fashion. PTAL.

One small change, but looks good

@robszumski PTAL

LGTM


Live demo not working

Tried using the live demo with username "demo" and password "demo1234" but I get message saying "No connection to backend server, try again in a few minutes. 8:42:21 PM"

Updated demo refresh script to match current configuration.
Note: Changes to the .env or to the .yml are not automatically updated and will probably break the refresh script.
Script is set to run ever two hrs. Will close after 24hr with no issue.

I am still not able to open the demo site.
https://demo2.librephotos.com/login
No connection to backend server, try again in a few minutes.
10:23:24 PM (CST)

@david-pekrul Did you configure your .env file? What CPU do you use? Can you post the log by starting just with docker-compose up?

I am still not able to open the demo site.
https://demo2.librephotos.com/login
No connection to backend server, try again in a few minutes.
10:23:24 PM (CST)

I am also having similar problems when I try and deploy this to my home server.
I'm wondering if this problem is related to the DB errors on setup?
#257 (comment)

I had a similar problem when deploying the other day and ended up needing to add a couple of items for the postgres container in addition to those provided in the example compose YAML:
POSTGRES_USER
POSTGRES_PASSWORD
POSTGRES_DB

Yay, added logging to the crontab, and it was having issues taking down the server. An update to the script has been made and should run in the next two hrs.

Logs indicate refresh script is running correctly. Issue Closed.

demo currentyl down same error

@JochenMehlich I was able to log into both demo servers. https://demo2.librephotos.com and https://demo1.librephotos.com
Can you verify you are not able to access either.

Im getting same error with the Demo. no access to backend.
I also tried to deploy it locally (NOT Docker, Debian local install) and I get the same problem.


MSBuild fails for PlatformTarget.x86

I have a solution with multiple .net projects and multiple Silverlight projects. I was using Cake 0.5.0 till now with MSBuild task as follows:
var buildSettings = new MSBuildSettings()
                .SetConfiguration(configuration)
                .UseToolVersion(MSBuildToolVersion.NET40)
                .SetPlatformTarget(PlatformTarget.x86)
                .WithProperty("OutputPath", outputPath);
        solutionFiles.ForEach(solutionFile =>
            MSBuild(solutionFile, buildSettings));

This would work perfectly, but now I upgraded Cake to 0.6.4.
After the upgrade I get the error "Debug|x86" is invalid."
I changed the PlatformTarget to PlatformTaget.MSIL (any CPU). Now, all .net projects would build but Silverlight projects would fail with "The Silverlight 4 SDK is not installed."
@patriksvensson suggested me to use build settings as so
var buildSettings = new MSBuildSettings()
                .SetConfiguration(configuration)
                .UseToolVersion(MSBuildToolVersion.NET40)
                .SetPlatformTarget(PlatformTarget.MSIL)
                .SetMSBuildPlatform(MSBuildPlatform.x86)
                .WithProperty("OutputPath", outputPath);

With the above settings all projects build successfully.

@kopparam This is not a problem with Cake but a missing build configuration (Debug|x86) that hasn't been specified in your csproj/vbproj file. Silverlight also needs to be built using x86 version of MSBuild (which is not used by default in Cake on a x64 machine).
To build with x86 configuration you would need to add this to your project file:
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|x86' ">
  <!-- Configuration here -->
</PropertyGroup>

You can also add the configuration in the "Configuration Manager" in Visual Studio (which also will set sensible defaults).


MSP files "Num peaks" always reporting 174 peaks

Hello,
The peptides in the prediction files from the web server always report Num peaks: 174 even when most of them are shorter. For example, this is the beginning of my downloade msp file.
examplePrositLib.txt
174 peaks are reported in my other downloaded file as well. Is this a mistake?

Hello,
it was an issue on our side it got fixed now, resubmit the jobs and it would work correctly now.

Thank you, it works as a csv


Address error within eval_plots.py when running on outputs that don't have data covering all benchmark types

Steps to reproduce:

create or use a set of FIM outputs that only cover some of the benchmark data sources (e.g. one BLE HUC)
run synthesize_test_cases.py
run eval_plots.py or eval_plots_stackedbar.py

Error message below:
Traceback (most recent call last):
File "//foss_fim/tools/eval_plots.py", line 1037, in
eval_plots(metrics_csv=m, workspace=w, versions=v, stats=s, spatial=sp, fim_1_ms=f, site_barplots=i)
File "//foss_fim/tools/eval_plots.py", line 729, in eval_plots
barplot(
File "//foss_fim/tools/eval_plots.py", line 328, in barplot
axes = sns.barplot(
File "/usr/local/lib/python3.10/dist-packages/seaborn/categorical.py", line 2755, in barplot
plotter = _BarPlotter(x, y, hue, data, order, hue_order,
File "/usr/local/lib/python3.10/dist-packages/seaborn/categorical.py", line 1532, in init
self.establish_colors(color, palette, saturation)
File "/usr/local/lib/python3.10/dist-packages/seaborn/categorical.py", line 707, in establish_colors
lum = min(light_vals) * .6
ValueError: min() arg is an empty sequence

This is a duplicate of 1362, but we will close that one and put those notes into this card, keeping this card open:

Eval plots is erroring out with a ValueError of "min() arg is an empty sequence.
The following AHPS sites are considered "BAD_SITES":  baki3, cart2, eagi1, efdn7, erwn6, grfi2, kcdm7, ksdm7, levk1, lkcm7, loun7, lrlm7, mcri2, mtao1, roun6, rwdn4, vcni3
The following query is used to filter AHPS:  not flow.isnull() & masked_perc<97 & not nws_lid in @BAD_SITES
Traceback (most recent call last):
  File "//foss_fim/tools/eval_plots.py", line 1036, in <module>
    eval_plots(metrics_csv=m, workspace=w, versions=v, stats=s, spatial=sp, fim_1_ms=f, site_barplots=i)
  File "//foss_fim/tools/eval_plots.py", line 728, in eval_plots
    barplot(
  File "//foss_fim/tools/eval_plots.py", line 327, in barplot
    axes = sns.barplot(
  File "/usr/local/lib/python3.10/dist-packages/seaborn/categorical.py", line 2755, in barplot
    plotter = _BarPlotter(x, y, hue, data, order, hue_order,
  File "/usr/local/lib/python3.10/dist-packages/seaborn/categorical.py", line 1532, in __init__
    self.establish_colors(color, palette, saturation)
  File "/usr/local/lib/python3.10/dist-packages/seaborn/categorical.py", line 707, in establish_colors
    lum = min(light_vals) * .6
ValueError: min() arg is an empty sequence

root@421deec6b5a0:/# ^C
It has been seen against against a couple of different pipeline tests including a huc set of "07080103 07080208 12040101 12040103 12090301". Between the combination of those HUCs, they cover all five of the different test_case types.

07080103 (ras2fim, ifc)
07080208 (ras2fim, usgs)
12040101 (nws, ble)
12040103 (ble, nws, usgs)
12090301 (ble, ifc, nws, and usgs)

Matt:
I ran fim_pipeline, synth, and eval_plots on the same set of HUCs ("07080103 07080208 12040101 12040103 12090301") on my EC2 using the dev image but didn't get the error. I'll try on prod3.

Unable to replicate this particular error. It may have been resolved with an update to seaborn. We'll keep an eye out for it and reopen this issue if it happens again.


Adding approach0.xyz in the HSTS preload list for (albeit small) faster loading time

Without HSTS or HSTS being preloaded a user would need to first connect to the website to retrieve the key then to connect again, something that wont happen if the HSTS header is preloaded. Right now there is a problem to get it added in the HSTS Preload list (which is included in all major browsers, from Chromium to Firefox)
https://securityheaders.io/?q=approach0.xyz&followRedirects=on
https://hstspreload.org/?domain=approach0.xyz
Error 1: No HSTS header is present on the response.
The website doesn't have HSTS to begin with :]
Error 2: Too many redirects: There are more than 3 redirects starting from http://approach0.xyz.
Error 3: Insecure redirect: http://approach0.xyz redirects to an insecure page on redirect #2: http://approach0.xyz/search
Error 4: Insecure redirect https://approach0.xyz redirects to an insecure page: http://approach0.xyz/search
Even solving these other redirect errors will result in faster speeds.

@builtfordevelopers-hstermail-c Thank you for bringing up this issue!
I have removed the redundant redirection. Now visiting http://approach0.xyz goes through only https://approach0.xyz/ and then https://approach0.xyz/search/. (I can argue these 3 steps are reasonable)
Although I doubt the necessity to use HSTS for a site like Approach0 no matter for security reason or efficiency consideration (Appraoch0 is just a search engine, and the current number of users are not significant). I have added a short term (currently only has max-age=1314000) HSTS header to Approach0 (check it on hstspreload again). Because Approach0 is using free HTTPS certificate service (let's encript), long HSTS age will completely block users from accessing our site when I fail to response very quickly when the HTTPS certificate gets expired (which may be relatively frequent for a free service). After all, Approach0.xyz is meant to be a demo site, I do not expect over-tuned or unnecessary efficiency optimization (e.g. adding domain to HSTS preload list and make approach0.xyz a https site forever) in a very near future.
ref: https://www.nginx.com/blog/http-strict-transport-security-hsts-and-nginx

@t-k- Thanks for these improvements!
Did you use Certbot to implement the Let's Encrypt cert? It does the job of automatic renewals of the certificate by default. If not you can try to setup a cron job that will renew the certificate each 90 days.

@builtfordevelopers-hstermail-c No, I am using a simple script to manually setup let's encrypt service each time I need. I think I will take some time to simply write a cron job to automatically run my script in the future. Thank you for recommending a nice tool to me!


Fix comment parsing

Fix comment parsing, in css doesn't allow line comments, i.e.
// Foo

is invalid comments.
Will be great to merge after https://github.com/swc-project/swc/pull/2398

@kdy1 hm, before we generate ast for // test, now we don't do it, so if somebody rely on // comment parsing, it will be broken now, so I decided that it would be major change... Anyway I can change

@kdy1 Ready fro review, if we merge this and https://github.com/swc-project/swc/pull/2415, I will send a couple more fixes :star:

@kdy1 Done :star:


Trying to use the noscript plugin, like this:

      <picture class="img-block">
            <source media='(min-width: 641px)' srcset="
            http://ex.com/file.jpg.jpg?w=600&format=jpg&quality=80 3x,
            http://ex.com/file.jpg.jpg?w=600&format=jpg&quality=70 2x,
            http://ex.com/file.jpg.jpg?w=450&format=jpg&quality=70 1.5x,
            http://ex.com/file.jpg.jpg?w=300&format=jpg&quality=87 1x" />
        ...

      </picture>

The code of the  contents would sometimes be processed with HTML-symbols encoded:

  <picture class="imb-block">
      <source media='(min-width: 641px)' srcset="
      http://ex.com/file.jpg.jpg?w=600&amp;format=jpg&amp;quality=80 3x,
      http://ex.com/file.jpg.jpg?w=600&amp;format=jpg&amp;quality=70 2x,
      http://ex.com/file.jpg.jpg?w=450&amp;format=jpg&amp;quality=70 1.5x,
      http://ex.com/file.jpg.jpg?w=300&amp;format=jpg&amp;quality=87 1x" />
    ...
    <img class="ContentAside-img"
     src="http://ex.com/file.jpg.jpg?w=300&amp;format=jpg&amp;quality=87"
     alt="something"
     data-responsive-img>
  </picture>

This doesn't happen on each page load. Sometimes the images would load normally on the very same page they failed the last time; and then fail again.
I could reproduce it in the latest Safari 12, also in older chromes (64, 47).
Is that a bug in webkit/blink, and can it be mitigated in the code of the lib? Or maybe you could give me some leads to what other JS software could be causing this?

I would need a test case to reproduce this problem.


 It's really a small and good model,I want to retrain it in my business,very thanks

I used to train this model using https://github.com/justadudewhohacks/tfjs-tiny-yolov2. But I nowadays train models on colab instead of in the browser.

Hi, @justadudewhohacks , right now we are have a project to detect emotion , we plen to train with our own sample images too, would you share abit about "colab" you mention above ?
anyway we also check this link https://github.com/justadudewhohacks/tfjs-tiny-yolov2 to start learn how to train it


EOL while scanning string literal

Hi
I created the conda env and activated it, then tried a dry run:
snakemake --configfile config.yaml -n

This produces an error:
SyntaxError in line 10 of 16S-dada2/Snakefile:
EOL while scanning string literal

Not sure what's going on, is this a Python version?
$ which python
/home/ubuntu/miniconda3/envs/dada2_env/bin/python
$ python --version
Python 3.6.13

Thank you for noticing. It's fixed on the master branch. you can simply run git pull I think


missing dependencies error

looks awesome! i'm hitting some dependency when i try to run

If i run the main scene with CMD + B. Here's what I see.

sorry for breaking this into a couple comments 😅
i get the error alert below if i try to open main.tscn, level1.tscn, and level2.tscn

When I run the main scene (screenshot on previous comment), I see these errors in the Debugger console.
E 0:00:00:0847   open: res://kits/mesh_lib3.tres:1 - Parse Error: Saved with newer format version
  <C++ Source>   scene/resources/resource_format_text.cpp:1055 @ open()

E 0:00:00:0847   _load: Failed loading resource: res://kits/mesh_lib3.tres. Make sure resources have been imported by opening the project in the editor at least once.
  <C++ Error>    Condition "found" is true. Returning: Ref<Resource>()
  <C++ Source>   core/io/resource_loader.cpp:275 @ _load()

E 0:00:00:0866   _parse_ext_resource: res://scenes/level2/level2.tscn:42 - Parse Error: [ext_resource] referenced non-existent resource at: res://kits/mesh_lib3.tres
  <C++ Source>   scene/resources/resource_format_text.cpp:163 @ _parse_ext_resource()

i'm on Godot 4.2.2

+1 on this issue

--- GDScript language server started on port 6005 ---   scene/resources/resource_format_text.cpp:448 - res://characters/PlayerEntity.tscn:5 - ext_resource, invalid UID: uid://cnt1c1t4mbygw - using text path instead: res://ui/game_data_store.tres   scene/resources/resource_format_text.cpp:1055 - res://kits/mesh_lib3.tres:1 - Parse Error: Saved with newer format version   Failed loading resource: res://kits/mesh_lib3.tres. Make sure resources have been imported by opening the project in the editor at least once.   scene/resources/resource_format_text.cpp:284 - res://scenes/level2/level2.tscn:42 - Parse Error:    Failed loading resource: res://scenes/level2/level2.tscn. Make sure resources have been imported by opening the project in the editor at least once.   scene/resources/resource_format_text.cpp:448 - res://ui/ControllerMenu.tscn:3 - ext_resource, invalid UID: uid://b5kvl5o6ywpt1 - using text path instead: res://ui/game_data_store.tres   scene/resources/resource_format_text.cpp:284 - res://scenes/main.tscn:18 - Parse Error:    Failed loading resource: res://scenes/main.tscn. Make sure resources have been imported by opening the project in the editor at least once.   editor/editor_data.cpp:626 - Index p_idx = 1 is out of bounds (edited_scene.size() = 1).   scene/resources/resource_format_text.cpp:1584 - res://kits/meshlib_space_ground.tres:1 - Parse Error: Saved with newer format version   scene/resources/resource_format_text.cpp:1584 - res://kits/mesh_lib3.tres:1 - Parse Error: Saved with newer format version

the relevant line seems to be this one:
res://kits/mesh_lib3.tres:1 - Parse Error: Saved with newer format version

I am working with Godot 4.3dev6 (living on the edge!). Can you give it a try?

Confirmed, it works with 4.3dev6 not 4.2.2


Add extra fields based on label and env for gelf/fluentd log drivers

Fix #15816
This adds container env and labels to log context, and use the data in gelf and fluentd log driver to expose more logging data.
Usage:

gelf: --log-opt gelf-labels=label1,label2 --log-opt gelf-env=env1,env2
fluentd: --log-opt fluentd-labels=label1,label2 --log-opt fluentd-env=env1,env2

The above instructions add label1, label2, env1, env2 key-value pair to log.
cc @LK4D4 @tagomoris @mariussturm

I think any changes here would need to depend on #15384

@dqminh extra fields in a GELF message have to start with a _. In the current PR you can pick any name, right?

@mariussturm ah yes, i forgot about that specification ( seems like the log servers still happily accepts it though ). I think user can pick names, but we can force that the fields we sent is prefixed with _. wdyt ?

Yes, I would force the prefix. Thanks!

LGTM :+1:

Another thing, since the fluentd-labels/env and the gelf-labels/env behave in the same way, there is no need for different option names. I think it's more important to point out that the label/env options hook into the Docker metadata system. Maybe a generic name like --log-opt append-labels would be clearer for the user?

@mariussturm however not all log drivers can support this though. I think journald can with the same changes, but json file and syslog cannot. Not sure if we can apply a global log opt here.

It's the same with gelf-tag and fluentd-tag option, both will be deprecated in favour of tag: https://github.com/docker/docker/pull/15384

@mariussturm tag can be applied universally though, this is not applicable to syslog / json-file afaik.

@mariussturm added support for _ prefix in additional field names.

Obligatory ping @mariussturm @cpuguy83 :smile:
Not sure which order we want to merge this vs #15384 . IMO this is much more simpler and useful than #15384 for ingesters want to consume structured log with injected metadata ( i.e. not applicable to syslog )

The GELF part LGTM. But as I said parameter name feels inconsistent to me. Especially when you combine it with the tag option: --log-opt tag vs. --log-opt gelf-labels
As a user: why one with protocol prefix and the other without?
But this is something @calavera or @cpuguy83 has to decide.

I'd say that if an option is used by more than one driver, it should not have a prefix. I agree with @mariussturm that it feels inconsistent. I think this should be --log-opt labels= and --log-opt env=.

Hmm i dont mind changing it. I jus think that it can be confusing when not all drivers can support this, for example syslog and json-file, also journald but that can be fixed.
Do you think that is only a doc issue now ?

@dqminh maybe it would be even easier to add these options to all drivers rather than just two of them :smile_cat:

@calavera we can probably extend json-file, but syslog is problematic though unless we want RFC5424. Feels like that a big change.

@dqminh let's go with json-file only then. We can always iterate on syslog if we need to.

I added this PR to the 1.9 milestone. I think it would be a nice feature to have in systems like Amazon ECS #15153.
@dqminh feel free to reach me if you need help with this.

@dqminh is there any progress on this?

@calavera not yet. I'm planning to work on this later today.

awesome, thank you! :metal:

@calavera updated to labels/env log options and add it to journald and json-file too.

Is there a way we can have tests and documentation for this? I just found an issue that would have been quickly detected with some unit tests.

@calavera fixed and added some tests last week ( sorry forgot to ping :( )
This doesnt have any documentation yet, but I dont have much cycle on this for this week, so feel free to take over if you want. Otherwise let me know and i will try to find some time for it.

code LGTM, but I'm not going to be able to carry it in, because I'm going to be offline for a couple of weeks.

Except from the small comments, code LGTM too.
@calavera I can carry it, but wondering if the commits should be squashed or not ?

Yes, @dqminh Do you have time to squash commits before someone carries?

Squashed and rebased.

Moving to docs review, thanks @dqminh!

@dqminh I don't see any docs yet; can you add a description of the new options to
https://github.com/docker/docker/blob/master/docs/reference/logging/overview.md, also, IIUC, env and label can now be used in --log-opt tag, so they need to be added to the table, and here; https://github.com/docker/docker/blob/master/docs/reference/logging/log_tags.md

@dqminh if you get this done by today we can try and get it in 1.9 before code freeze

@jfrazelle @dqminh I'm gonna carry it for the docs ; to make sure it makes it :wink:.

thanks @vdemeester

closing because https://github.com/docker/docker/pull/16961 is updated thanks @dqminh


Is repo still maintained?

Hello, very interesting Node Powershell integration.
May I ask, is there any plan continuing the development?
I see participations and pull requests are not processed.
Thank you for your response.

Adding my comment here, would like to see this repo maintained too. Maybe hand it over to someone else to maintain if you don't have time, @rannn505 ?

Try this:
https://github.com/obaydmerz/powerjs

Looks interesting, I might have to check it out


Check indentation completely

I suggest to implement all-catching check of indentation. The current rules regarding indentation ([W1007] uneven-indent and [E1008] bad-indent) allow me to indent very sloppily. 😄 It could work roughly like this:

One level of indentation is either one tab or 4 spaces (this "4" would be default, but configurable)
Names of keywords and test cases in definition are not indented. Their bodies are indented by 1 level.
In FOR-cycles and IF-branches, stuff is indented one more level than "FOR" or "IF"
Continuation line has the same indentation as the line which the continuation line "extends".
Lines containing only comments are indented either like the preceding, or the following non-empty line.
(Is there any other case influencing indentation?)

I do not know whether Robocop is ready for such a rule, but it is able to work with indentation even now, so I hope so...

I am sorry I create many issues today, but I am carefully going through our code standard and thinking how Robocop could help us to observe it. 😄

I've spent quite a lot of time with indents in Robocop and the reason why it isn't so strict is because how flexible Robot Framework is. Some people prefer different ways of aligning (ie align to columns, or extra align for particular statements). It makes it harder to catch actual issues. That's why current uneven indent rule does not check if we're matching fixed indent but only if all indents are the same in given block (test, keyword, for or if).
But I have an idea: we could add parametr strict (default False). In strict mode we could check for indents in the way you described. And it's actually easier to implement than non strict mode. What do you think?

I am sorry I create many issues today, but I am carefully going through our code standard and thinking how Robocop could help us to observe it. 😄

Don't be sorry, we really apprecieate all new ideas or issues how so we can improve Robocop further ;)

I've spent quite a lot of time with indents in Robocop and the reason why it isn't so strict is because how flexible Robot Framework is. Some people prefer different ways of aligning (ie align to columns, or extra align for particular statements). It makes it harder to catch actual issues. That's why current uneven indent rule does not check if we're matching fixed indent but only if all indents are the same in given block (test, keyword, for or if).
But I have an idea: we could add parametr strict (default False). In strict mode we could check for indents in the way you described. And it's actually easier to implement than non strict mode. What do you think?

@bhirsz I totally support this idea.

I suggest to implement all-catching check of indentation. The current rules regarding indentation ([W1007] uneven-indent and [E1008] bad-indent) allow me to indent very sloppily. 😄 It could work roughly like this:

One level of indentation is either one tab or 4 spaces (this "4" would be default, but configurable)
Names of keywords and test cases in definition are not indented. Their bodies are indented by 1 level.
In FOR-cycles and IF-branches, stuff is indented one more level than "FOR" or "IF"
Continuation line has the same indentation as the line which the continuation line "extends".
Lines containing only comments are indented either like the preceding, or the following non-empty line.
(Is there any other case influencing indentation?)

I do not know whether Robocop is ready for such a rule, but it is able to work with indentation even now, so I hope so...

@MoreFamed  At least one thing is missing here... What would be the indentation for the first token after continuation line? It can be either next 4 spaces or... something else.

Hi, thanks for you attitude and ideas! To be clear: by word "indentation", I mean just amount of whitespace at the beginning of a line, not whitespace between tokens. (The latter could hardly be checked because of the reason @bhirsz mentions, if I caught the mention about "aligning to columns" well.)
@mnojek, I am not sure I understand your question. If you ask about space between "..." and the next thing on the line: I do not know. :) I consider this question to be similar to question of spaces between two tokens and I think this is beyond the scope of indentation rules. I can imagine this
    [Documentation]  Some description
    ...              which is very long

and this too:
    [Documentation]
    ...  Some description
    ...  which is very long

I would rather check just the whitespaces before "...".

@MoreFamed  You're right, these are 2 different things and I mixed them up.

I have starting working on this. There is one issue to be resolved - we have two rules for indentation, uneven-indent and bad-indent. If we would add new "strict" parameter we would need to add it to both rules and then somehow make it work with current logic (since it's "embedded" in current fuzzy indent match logic).
However I'm thinking about leaving only one rule. Just by the description of the rules it may not be clear why there are two rules:
uneven-indent:
       Reported when line does not follow indent from the current block.
        Example of rule violation::

            Keyword With Over Indented Setting
                [Documentation]  this is doc
                 [Arguments]  ${arg}  # over-indented
                   No Operation  # over-indented
                Pass
                No Operation
                Fail

bad-indent:
        Expecting indent. Example of rule violation::

             FOR  ${elem}  IN  ${list}
            Log  stuff  # content of FOR blocks should use bigger indentation than FOR header
             END

It made sense to create two rules before because sometimes the indentation is just uneven (hence rule with the warning) and sometimes it is wrong and causes syntax issues (hence rule with the error). But now we have feature of allowing dynamic severity of the rule - so we can use one rule and change severity depending on our needs. For example use bad-indent rule with default severity Warning and optional parameter strict.
Such change will require deprecation warning - but it will not be breaking change (thanks to deprecation warnings) so the next version will be still minor.
@mnojek WDYT?

Now I see that the issue is from 17.09.2021 so I have exactly two days before anniversay :D

Actually, the anniversary is today (from the first release)! 😄
Happy birthday, Robocop! 👮🏻♂
So you mean that this one new rule will trigger warning when it will be something like old uneven-indent and it will raise error when it is something like old bad-indent?

🥳
Yes. It it still not perfect (the idea that severity can change) but it will be easier to understand by users rather than two existing rules.

I agree, let's do it. These 2 rules were confusing anyway.


Error importing an npm module

Currently creating an android app. I am simply trying to import the spotify-web-api-node module.
One line so far in my index.android.js to do this:
import SpotifyWebApi from 'spotify-web-api-node';
When I go to load the JS into my emulator I get the follow error:
602/603Error while persisting cache: SyntaxError /path/to/the/project/node_modules/restler/lib/multipartform.js: Invalid number (112:35)
I am using a mac, this occurs for android (have not tried ios yet).
react-native -v =  react-native-cli: 0.1.10 react-native: 0.21.0

@facebook-github-bot stack-overflow