opencv stuck in multiprocess program on Mac but correctly execute on Linux

Expected behaviour
execute correctly in multiprocess
Actual behaviour
the program stuck or exit
Steps to reproduce

example code

# !/usr/bin/python3

# -*- coding: utf-8 -*-

"""
@ModuleName: why_fail
@author: GuYouda<EMAIL_ADDRESS>@date: 2021-01-05 21:23:48
@desc:
Mac
Python3
pip3 install requests
pip3 install opencv-python

"""
import requests
import multiprocessing as mp
import os

import cv2

def foo1():
    # useless code
    print("foo1 start")
    res = requests.get("http://www.baidu.com")
    print("foo1 finish")

def execute(task_queue):
    print("[{}]exec start".format(os.getpid()))
    try:
        while True:
            image = task_queue.get_nowait()
            if image is None:
                break

            # useless code
            print("[{}]resize start".format(os.getpid()))
            imgcv = cv2.resize(image, (540, 960))
            print("[{}]resize finish".format(os.getpid()))
        print("[{}]check finish".format(os.getpid()))
    except Exception as e:
        print(e)
    finally:
        print("[{}]finally".format(os.getpid()))
    print("[{}]exec finish".format(os.getpid()))

def method1():
    foo1()

    # create directory ./temp and add 5 images named 0~4.png
    image_path_list = [
        "./temp/0.png",
        "./temp/1.png",
        "./temp/2.png",
        "./temp/3.png",
        "./temp/4.png"
    ]
    task_queue = mp.Manager().Queue()
    for i in image_path_list:
        task_queue.put(cv2.imread(i))
    for i in range(4):
        task_queue.put(None)

    # execute with process pool
    pool = mp.Pool(processes=4)
    for i in range(4):
        pool.apply_async(execute, (task_queue,))
    pool.close()
    pool.join()

    print("success")

def method2():
    foo1()

    # create directory ./temp and add 5 images named 0~4.png
    image_path_list = [
        "./temp/0.png",
        "./temp/1.png",
        "./temp/2.png",
        "./temp/3.png",
        "./temp/4.png"
    ]
    task_queue = mp.Manager().Queue()
    for i in image_path_list:
        task_queue.put(cv2.imread(i))
    for i in range(4):
        task_queue.put(None)

    # execute with multiprocess
    process_list = []
    for i in range(4):
        p = mp.Process(target=execute, args=(task_queue,))
        process_list.append(p)
        p.start()

    for p in process_list:
        p.join()

    print("success")

if __name__ == '__main__':
    # line 21: res = requests.get("http://www.baidu.com")
    # line 35: imgcv = cv2.resize(image, (540, 960))
    # line 21 and 35 are both useless code, if line 21 and 35 are both executed on Mac, the program stuck
    # if delete any line of 21 and 35, the program will execute correctly
    # but on Linux, the program will execute correctly in any condition

    # execute with process pool
    method1()

    # execute with multiprocess
    # method2()

operating system
MacBook Pro (13-inch, 2019, Two Thunderbolt 3 ports)
version:10.15.7
architecture (e.g. x86)
x86
opencv-python version
<IP_ADDRESS> and <IP_ADDRESS> , maybe other version has the same problem

Issue submission checklist

[ ] This is not a generic OpenCV usage question (looking for help for coding, other usage questions, homework etc.)

[ ] I have read the README of this repository and understand that this repository provides only an automated build toolchain for OpenCV Python packages (there is no actual OpenCV code here)

[ ] The issue is related to the build scripts in this repository, to the pre-built binaries or is a feature request (such as "please enable this additional dependency")

[ ] I'm using the latest version of opencv-python

The correct place for this question is some of these forums:

https://forum.opencv.org/
https://stackoverflow.com/

This issue tracker is reserved for issues in the opencv-python build toolchain. There is no actual OpenCV code here.

The correct place for this question is some of these forums:

https://forum.opencv.org/
https://stackoverflow.com/

This issue tracker is reserved for issues in the opencv-python build toolchain. There is no actual OpenCV code here.


Uninstall Command for Intune

Hello,
I noticed on the documentation that the Uninstall command was left blank. Is there a proper way to uninstall the app on Intune?
Thanks

There is a Uninstall_tool.ps1 file. Doesn't that work?


Space in data value is currently not supported

It's a known issue that the CLI doesn't support spaces in the data value like:
kubectl tbac create secret test --data "VAR=foo bar"
bar in this case is treated as a new argument to the secret command. I have not found a way around this.
Workaround for this is to use native kubectl.

Seems to be an environmental issue since it works on macos and using the TBAC UI.

Won't fix at this point as it's an issue on some environments only and workarounds exist. Using TBAC UI or native kubectl commands.

Won't fix at this point as it's an issue on some environments only and workarounds exist. Using TBAC UI or native kubectl commands.


Close original entity stream in order to avoid connection leak

Description
Leased connections were not released when using the Apache Connector and the server returned a compressed response.
Motivation and Context
Added logging of requests/responses with the help of Logbook but found out that the apache http connections were not released back to the connection pool. Old behaviour can be verified if you remove the new try clause in RemoteResponse and run the test ClientWithApacheConnectorTest.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.

@whiskeysierra (Sorry for the mention) Any chance that you can take a look at this?

👍

Thank you for your contribution! 🎉
Sorry, that it took so long 😞


fix: translate error of old Ingress

Type of change:

[ ] Bugfix
[ ] New feature provided
[ ] Improve performance
[ ] Backport patches

What this PR does / why we need it:

Pre-submission checklist:

[ ] Did you explain what problem does this PR solve? Or what new features have been added?
[ ] Have you added corresponding test cases?
[ ] Have you modified the corresponding document?
[ ] Is this PR backward compatible? If it is not backward compatible, please discuss on the mailing list first

Codecov Report

Merging #1193 (8eb0c18) into master (3d720c0) will decrease coverage by 0.30%.
The diff coverage is 2.50%.

@@            Coverage Diff             @@
##           master    #1193      +/-   ##
==========================================
- Coverage   29.85%   29.55%   -0.31%
==========================================
  Files          81       81
  Lines       10021    10125     +104
==========================================
  Hits         2992     2992
- Misses       6705     6809     +104
  Partials      324      324

Impacted Files
Coverage Δ

pkg/ingress/apisix_route.go
0.00% <0.00%> (ø)

pkg/ingress/controller.go
0.38% <0.00%> (-0.01%)
:arrow_down:

pkg/ingress/ingress.go
6.16% <0.00%> (ø)

pkg/kube/translation/apisix_route.go
18.97% <0.00%> (-1.64%)
:arrow_down:

pkg/kube/translation/translator.go
30.10% <0.00%> (-3.23%)
:arrow_down:

pkg/kube/translation/ingress.go
49.02% <4.76%> (-11.89%)
:arrow_down:

pkg/ingress/apisix_upstream.go
0.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us.


How do I use MaterialSystem->CreateMaterial

it only takes voids and not chars?

When I made the interfaces manually, I didn't bother to fill in arguments, as it would take too much time.
You have to set the arguments manually on methods you want to use, and you can find them easily in source sdk.

ok


Merge pull request #2 from assimon/master

Merge pull request #258 from bimoe/master

update

fix bug.


Home scenario: Possible status situations

Thanks, for your app. Works as expected.
While currently working from home I'm coming to the conclusion, that the Online status (Graph API: availability) isn't as helpful to indicate my family what's "needed".
In general I see two dimensions:
a) I don't want to be distracted: (Important) presentation I'm giving, (intense) 1on1, anything that shouldn't be disturbed.
b) Avoiding awkward moments broadcasted into my call/meeting, mostly with camera and/or mic on.
So the distinction is more around the following parameters:

Being in a call / meeting?
Presenting / not presenting?
Mic on / Muted
Camera on/off

Regarding status this leads to the following states to signal:
Red flashing: really don't disturb - don't even tell me anything or ask anything
Red: In a call / meeting -- Mic / Video on -- I might be able to react
Yellow: In a call / meeting -- Mic / Video are on, be aware, but's it's ok for me to disturb
Green: Might be in a call or not -- but: Mic/video off  -- Let's talk
Off: Bulb turned off.
So in general, the Graph API: activity status might be a better indicator, combined  with the not available "Muted/Unmuted" & "Video On/Off" status. plus potentially some calendar flagging / interpretation and the unknown fact of "number of participants in the call/meeting".
For a faster implementation a kind of category selection to select a light status from the above list combined with the API-activity value might be a starter.
Just my 2c!

If you are presenting or in do not disturb, PresenceLight changes to a purplish color, here is the page that has available statuses
https://docs.microsoft.com/en-us/microsoftteams/presence-admins

If you are presenting or in do not disturb, PresenceLight changes to a purplish color, here is the page that has available statuses

Manual "Do not disturb" for me is mostly: Don't disturb me towards my online colleagues, but would be something else for my family.
In this regard: How is "Focus time" handled?

What you want is customizable control of colors. Why dont you do that manually? I only have access to the statuses available on that docs page. Anything more than that is manual

Sounds like you want to do custom colors. All I can do is change based on the statuses in that doc.

Probably my initial approach was too complicated. So let's simplify:
RED = Really dont disturb
YELLOW = Be aware - call is ongoing - camera/mic might be on
OFF = Im approachable without worries.
Based on a combination of “availability” and “activity” my suggestion would be:
IF availability = DoNotDisturb OR activity = Presenting THEN light=Red
ELSE IF activity = InACall OR activity = InAConferenceCall OR activity THEN light=Yellow
ELSE light=OFF (or Green)
This would allow to manually set within Teams the status as overwrite to "Do not disturb", all other settings would be set automatically.

Again, this is custom color configuration that does not map to Teams or Presence in general. There may be some things I can do to "control" what color gets sent based on certain scenarios, but then you need a management screen for those custom configurations. Will think on it.

I came here for this same topic. @isaacrlevin, when you say you only have access to the presence states on that page, can't you use the "app configured" value? Activity is clearly available in this example:
HTTP/1.1 200 OK

{
    "value": [
        {
            "id": "dc74d9bb-6afe-433d-8eaa-e39d80d3a647",
            "availability": "Away",
            "activity": "BeRightBack"
        }
    ]
}

@jdshkolnik that is correct, there would need to be another management screen for Activity as well as Availability, and I am unsure how that would luck. If you want to start a PR, I am more than happy to work with you on it!

Fair enough. Let me think about what I'd want to see.


how to raise error on process

I'm using jquery filepond on my project and i'm trying to raise error on process's onload
process: {
url: '/api/v1/fileuploader/upload',
method: 'POST',
timeout: 7000,
onload: function (response) {
console.log(response,this)
if (response.Code == 200) {
//on successful save
return response.Data;
} else {
//on saving failed on server/i've done validation in server
//todo raise on error sothat view so upload error..
return false;
}
},
onerror: null
guide me.

Apparently, your server responds with a 200 status code even when there's been an error. The server should return an error status, FilePond will then automatically populate the error value in the onprocessfile callback.
https://en.wikipedia.org/wiki/List_of_HTTP_status_codes

Then you'll have to set up a custom processing method, see this entry in the docs:
https://pqina.nl/filepond/docs/patterns/api/server/#advanced


Public Key Pinning (HPKP)

see:
https://scotthelme.co.uk/hpkp-toolset/

spec
Deprecated in favour of CT.


Create a slippy map "Tests Browser"

This repo contains an independent test suite that testsRoadNetwork and abstreet's RawMap. Each test case is a real world example with a lot of geographic data.
We should build a slippy map that shows the various formats of data for a test case, layering the .osm with the .geojson and linking the .dot. A simple menu would let you choose a test case to view, and highlight tests that need approving.
It could then be extended to run tests on demand, downloading .osm on the fly.

osm2lanes probably has exactly the stack that would achieve this. It would also benefit from the same tool. Maybe osm2lanes tests end up here too?

GeoJSON is built in: https://leafletjs.com/reference.html#geojson
openstreetmap/leaflet-osm has a straightforward OSM DataLayer
DOT with something like https://github.com/magjac/d3-graphviz#d3-graphviz ?

Before calling this issue done, just need to

[ ] present a list of available tests to click on, and
[ ] link from the README

Hijacking this slightly to write down some ideas I'm working on implementing. Here are some desired features of the StreetExplorer:

click a test case and see its 3 renderings / layers quickly
click a button to reimport a test case's built-in .osm. This makes a convenient dev workflow to work on transformation / importing code and use the browser for interactive debugging.
for any imported area, see a plain geometric GeoJSON view, or a more detailed rendering with the start of lane/intersection markings
import a custom area from Overpass, then save it as .osm for a new test case input
when importing a new area or reimporting an existing one, modify the transformation options. Optionally enable a debug mode, where we get back multiple copies of the StreetNetwork after each transformation step. Be able to browse forwards/backwards through the results as layers.

I'm imagining the UI state is organized around a "current loaded thing." That has a test name, or it's a freshly imported bit. There's a list of leaflet layers associated with it (so we can clean them up when we switch.) Then there are extra UI controls, depending on what's loaded. For a test case, there's a "reimport" button with options for transformation options. For a newly imported bit, there's a button to save the .osm for a new test case.

I like this direction. Can we pair-program a refactor of the JS into classes that will make this easier? I'll send a calendar invite.

I think the app is well-established at this point, and #64 links the readme to it. (Also I registered osm2streets.org pointing here)


Breakpoints not mapping correct between TS and JS files despite absolute or relative sourceMaps

VS Code Version: VS Code Insider 1.5.4
OS Version: Ubuntu 20.10 remote, OSX as local host

Steps to Reproduce:

Using bazel to build extension in typescript.
I have noted that I have correctly compiled my JS files which end up placed in a symlink path. Next to the js files is the .map files. which If I open will correctly open a symlinked ts file.
I have tried placing breakpoints in the symlinked ts file that lives at a location like

extension.js
/home/eli/.cache/bazel/_bazel_eli/6ab7f98a34b740eb8432b3beaaef9fee/execroot/trunk/bazel-out/k8-fastbuild/bin/trunk/vscode/extension.js
extension.js.map
{"version":3,"file":"extension.js","sourceRoot":"","sources":["../../../../../trunk/vscode/extension.ts"],....}

I have also tried with sourceMaps where I have set the sourceRoot in tsconfig to be an absolute path to avoid all the potential hiccups with a symlink
{"version":3,"file":"extension.js","sourceRoot":"/home/eli/GitHub/trunk/","sources":["trunk/vscode/extension.ts"],"....}

The basic hello world built with tsc directly with output directories directly below the source works without a problem. I can also attach debugger with debugger statement. I just want to be able to debug with the ts source code.

6 Launch .json looksl like this:
{
"name": "VS Code Extension Run",
"type": "extensionHost",
"request": "launch",
"runtimeExecutable": "${execPath}",
"args": [
"--extensionDevelopmentPath=${workspaceFolder}/trunk/vscode",
],
"sourceMaps": true,
"outFiles": [
"${workspaceFolder}/bazel-bin/trunk/vscode/**/*.js"
],
"trace": true
}

Package.json looks like this:
....
"main": "../../bazel-bin/trunk/vscode/extension.js",
"contributes": {
"commands": [
{
"command": "trunk.helloWorld",
"title": "Hello World"
},
{
"command": "trunk.goodbye",
"title": "Goodbye"
}
]
},

I've attached trace log
vscode-debugadapter-a94b88df.json.gz

Yes. I disabled all installed extensions except the remote extension needed for SSH

Since linked paths are resolved, I recommend setting your outFiles to point to the compiled bazel location on disk, and then also setting the sourceRoot in your tsc or tsconfig to point to the absolute path to your workspace location.
Better automatic handling may come with https://github.com/microsoft/vscode-js-debug/issues/776

@connor4312 - I have already attempted both of those changes
my outFiles are set to:
"${workspaceFolder}/bazel-bin/trunk/vscode/**/*.js" - bazel-bin is is symlink to the bazel cache out directory. All the js is compiled under trunk/vscode and should be globbed correctly
My sourceRoot was set to the absolute path "/home/eli/GitHub/trunk"
Any other debugging info I can provide to narrow down. I am happy to tweak our settings, just can't get anything that works.

"${workspaceFolder}/bazel-bin/trunk/vscode/**/*.js" - bazel-bin is is symlink to the bazel cache out directory.

The problem is that Node will automatically resolve these symlinks, so the URL for scripts that gets reported from the runtime is, in the case of the log,
file:///home/eli/.cache/bazel/_bazel_eli/6ab7f98a34b740eb8432b3beaaef9fee/execroot/trunk/bazel-out/k8-fastbuild/bin/trunk/vscode/extension.js

...instead of the path in your working directory. The debugger doesn't know these paths are equivalent--that's part of what the linked issue covers. But I think it would work if you (can know and pass) file:///home/eli/.cache/bazel/_bazel_eli/6ab7f98a34b740eb8432b3beaaef9fee/execroot/trunk/bazel-out/k8-fastbuild/bin/**/*.js in your outfiles, instead of what you do today.

Still no dice. Tried through several incarnations of that outFiles to the actual path. Still no luck.
I am happy to wait for the eventual fix here. Or I might try some resolution step to just land everything in actual paths for this use case.
If you need anyone to test a potential fix let me know. Also happy to post a sample repo with the problem although it sounds like you are well versed on the issue.
-Eli

From: Connor Peet<EMAIL_ADDRESS>Sent: Monday, February 22, 2021 9:24 AM
To: microsoft/vscode<EMAIL_ADDRESS>Cc: Eli Schleifer<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/vscode] Breakpoints not mapping correct between TS and JS files despite absolute or relative sourceMaps (#117211)
"${workspaceFolder}/bazel-bin/trunk/vscode/**/*.js" - bazel-bin is is symlink to the bazel cache out directory.
The problem is that Node will automatically resolve these symlinks, so the URL for scripts that gets reported from the runtime is, in the case of the log,
file:///home/eli/.cache/bazel/_bazel_eli/6ab7f98a34b740eb8432b3beaaef9fee/execroot/trunk/bazel-out/k8-fastbuild/bin/trunk/vscode/extension.js
...instead of the path in your working directory. The debugger doesn't know these paths are equivalent--that's part of what the linked issue covers. But I think it would work if you (can know and pass) file:///home/eli/.cache/bazel/_bazel_eli/6ab7f98a34b740eb8432b3beaaef9fee/execroot/trunk/bazel-out/k8-fastbuild/bin/**/*.js in your outfiles, instead of what you do today.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/vscode/issues/117211#issuecomment-783536362, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAJVCPWA52VLHHKPL64TAPTTAKHLVANCNFSM4YAAAUJQ.

If it's easy for you to do, a sample repo wouldn't hurt so I can make sure your use case is handled.


v1.11 Backports 2023-06-12

[ ] #25953 (@pchaigno) - :warning: minor conflicts in enableIPSec() (the function is named differently in v1.12+)

Skipped:

https://github.com/cilium/cilium/pull/26072 (@pchaigno) did not apply at all. None of the nodeID related code is present on v1.11

Once this PR is merged, you can update the PR labels via:
for pr in 25953; do contrib/backporting/set-labels.py $pr done 1.11; done

or with
make add-labels BRANCH=v1.11 ISSUES=25953

Closing in favor of https://github.com/cilium/cilium/pull/26021#issuecomment-1587332150


"application/x-czx" for ".czx" extension

Added mime type "application/x-czx" for ".czx" file extension which is used in CZIP X application

Thank you for your contribution


Some spanish translations.

Thank you for your help with the translations!  I'll have more text ready to go later today


Javairia's first turtles

:turtle:

Looks good, and I love the Turtle emoji.
You've done a good job describing your programs but will you include a brief reflection on your process as well?

@eah13 I included my reflection. Can you see it?

@jwarrich I got the reflection, but it looks like both of these trinkets are the same.  Check in your trinket account to find the board trinket - All I see are the input trinkets.  I'm going to go ahead an merge anyways.  Your partner today can open an issue for this.


Error: Cannot find module 'canvas'

I'm using version 3.0.2 of html-md and i'm getting the below error when I require html-md in my project.
npm version: 3.3.7
node version: v0.12.7
Error: Cannot find module 'canvas' from '..../node_modules/html-md/node_modules/jsdom/lib/jsdom/level2'

Unfortunately, we're quite far behind the latest version of jsdom right now. I'm considering bumping the version, however, I'm also trying to consider possible more lightweight alternatives as jsdom still feels a bit overkill.
It appears that jsdom is requiring the "canvas" module in some places even though it's not listed as dependency (optional or otherwise). I've had a quick look at the jsdom source code for v0.8.11 (the most likely version you'll have installed based on our ~0.8.6 semver range used in the dependency) and the only place I can see where it attempts to require the "canvas" module is here:
try {
  var canvas = new (require('canvas'))(0,0);
  for (var attr in element) {
    if (!canvas[attr]) {
      canvas[attr] = element[attr];
    }
  }
  return canvas;
} catch (e) {
  return element;
}

Without knowing exactly what line your error is being thrown at, I can't really help further investigate why this is happening, especially when the above code appears to wrap the require in a try/catch block, which I would have expected to prevent your error from occurring.
It's also worth noting that this should only happen if you're attempting to use html.md with HTML containing an HTML5 <canvas> element. According the the documentation for that version of jsdom:

jsdom includes support for using the canvas package to extend any <canvas> elements with the canvas API. To make this work, you need to include canvas as a dependency in your project, as a peer of jsdom. If jsdom can find the canvas package, it will use it, but if it's not present, then <canvas> elements will behave like <div>s.

I think that this would be your best course of action. I'm still not sure why you're seeing this error though and it's not gracefully ignoring the "canvas" module as documented and as the code would suggest it does.
However, be aware that depending on the "canvas" module also requires your package to have other external dependencies. Make sure that you read their wiki for complete installation instructions. This is probably why it's not a core dependency of jsdom.
I'm not convinced that a jsdom dependency bump for html.md would even fix this problem as it appears that it still does a similar check for the "canvas" module.


Remove intr and EINTR from pthread mutex

Summary
Updates pthread_sem_take and pthread_mutex_take to not take intr parameter.
The intr parameter was used for allowing the call to these functions to return EINTR (in case of we receiving a signal).
In POSIX, this should not happen, and we should continue to be locked (while trying to acquire the lock) even when we get EINTR.
So after this fix, there is now some dead code than can be removed.
Impact
The apis of the internal functions pthread_sem_take and pthread_mutex_take have been changed to not have the intr parameter. They can also never return EINTR.
Testing

thanks, ltgm.

But need to squash commits into one

@casaroli could you rebase your patch?

@casaroli could you rebase your patch?

done


Cherry pick root cert auto rotation

Please provide a description for what this PR is for.
Introduce a root cert rotator into Citadel that periodically checks root certificate expiration time and rotates expiry root certificate. Root cert rotation uses old root private key.
Support Citadel to sync root cert in local key cert bundle with root cert in istio-ca-secret, which is needed when multiple Citadels are deployed.
The following PRs are cherry-picked
https://github.com/istio/istio/pull/17330
https://github.com/istio/istio/pull/17597
https://github.com/istio/istio/pull/17550
https://github.com/istio/istio/pull/17677
https://github.com/istio/istio/pull/17865
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[x] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
https://github.com/istio/istio/issues/17059

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test istio-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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test istio-unit-tests

prow/e2e-simpleTests.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test e2e-simpleTests

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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test istio-unit-tests

prow/e2e-simpleTests.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test e2e-simpleTests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test istio-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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test istio-unit-tests

prow/e2e-simpleTests.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test e2e-simpleTests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-v1alpha3.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test istio-unit-tests

prow/e2e-simpleTests.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test e2e-simpleTests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-v1alpha3.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test istio_auth_sds_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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test istio-unit-tests

prow/e2e-simpleTests.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test e2e-simpleTests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-v1alpha3.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test istio_auth_sds_e2e

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

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test istio-unit-tests

prow/e2e-simpleTests.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test e2e-simpleTests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-v1alpha3.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test istio_auth_sds_e2e

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

prow/e2e-dashboard.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test e2e-dashboard

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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test istio-unit-tests

prow/e2e-simpleTests.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test e2e-simpleTests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-v1alpha3.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test istio_auth_sds_e2e

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

prow/e2e-dashboard.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test e2e-dashboard

prow/release-test.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test release-test

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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test istio-unit-tests

prow/e2e-simpleTests.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test e2e-simpleTests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-v1alpha3.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test istio_auth_sds_e2e

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

prow/e2e-dashboard.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test e2e-dashboard

prow/release-test.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test release-test

prow/e2e-bookInfoTests-trustdomain.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test istio-unit-tests

prow/e2e-simpleTests.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test e2e-simpleTests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-v1alpha3.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test istio_auth_sds_e2e

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

prow/e2e-dashboard.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test e2e-dashboard

prow/release-test.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test release-test

prow/e2e-bookInfoTests-trustdomain.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
link
/test e2e-bookInfoTests-trustdomain

prow/e2e-mixer-no_auth.sh
e96f4f0c65bb19bb1c8a3fa0ca9c6acfb69efc02
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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test istio-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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test istio-unit-tests

prow/e2e-bookInfoTests-v1alpha3.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test istio-unit-tests

prow/e2e-bookInfoTests-v1alpha3.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-simpleTests

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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test istio-unit-tests

prow/e2e-bookInfoTests-v1alpha3.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-simpleTests

prow/e2e_pilotv2_auth_sds.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test istio_auth_sds_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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test istio-unit-tests

prow/e2e-bookInfoTests-v1alpha3.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-simpleTests

prow/e2e_pilotv2_auth_sds.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test istio_auth_sds_e2e

prow/e2e-bookInfoTests-trustdomain.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test istio-unit-tests

prow/e2e-bookInfoTests-v1alpha3.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-simpleTests

prow/e2e_pilotv2_auth_sds.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test istio_auth_sds_e2e

prow/e2e-bookInfoTests-trustdomain.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-bookInfoTests-trustdomain

prow/istio-pilot-multicluster-e2e.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test istio-pilot-multicluster-e2e

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test istio-unit-tests

prow/e2e-bookInfoTests-v1alpha3.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-simpleTests

prow/e2e_pilotv2_auth_sds.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test istio_auth_sds_e2e

prow/e2e-bookInfoTests-trustdomain.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-bookInfoTests-trustdomain

prow/istio-pilot-multicluster-e2e.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test istio-pilot-multicluster-e2e

prow/e2e-dashboard.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-dashboard

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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test istio-unit-tests

prow/e2e-bookInfoTests-v1alpha3.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-simpleTests

prow/e2e_pilotv2_auth_sds.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test istio_auth_sds_e2e

prow/e2e-bookInfoTests-trustdomain.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-bookInfoTests-trustdomain

prow/istio-pilot-multicluster-e2e.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test istio-pilot-multicluster-e2e

prow/e2e-dashboard.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-dashboard

prow/e2e-mixer-no_auth.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test istio-unit-tests

prow/e2e-bookInfoTests-v1alpha3.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-simpleTests

prow/e2e_pilotv2_auth_sds.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test istio_auth_sds_e2e

prow/e2e-bookInfoTests-trustdomain.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-bookInfoTests-trustdomain

prow/istio-pilot-multicluster-e2e.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test istio-pilot-multicluster-e2e

prow/e2e-dashboard.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-dashboard

prow/e2e-mixer-no_auth.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-mixer-no_auth

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test istio-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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test istio-unit-tests

prow/e2e-bookInfoTests-v1alpha3.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-simpleTests

prow/e2e_pilotv2_auth_sds.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test istio_auth_sds_e2e

prow/e2e-bookInfoTests-trustdomain.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-bookInfoTests-trustdomain

prow/istio-pilot-multicluster-e2e.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test istio-pilot-multicluster-e2e

prow/e2e-dashboard.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-dashboard

prow/e2e-mixer-no_auth.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-mixer-no_auth

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/release-test.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test release-test

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.

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

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test istio_auth_sds_e2e

prow/e2e-bookInfoTests-trustdomain.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-bookInfoTests-trustdomain

prow/e2e-mixer-no_auth.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test e2e-mixer-no_auth

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
943f94ef5d2d19aa7b9bdf7cbd5594f092af53f3
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
9d3896a26c506a40eb1d9cc29452b877fbf9c1f3
link
/test istio-pilot-multicluster-e2e

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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
26a147d19863ff2a53c97699ea164d4a75c2f36c
link
/test istio-pilot-multicluster-e2e

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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
06c8d6bcf724cd080cef89b3874777d2d40d15da
link
/test istio-pilot-multicluster-e2e

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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
2e74a429a322b111c78750ad239f7eaa365bf741
link
/test istio-pilot-multicluster-e2e

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

/retest

@myidpt Please take a look. Thanks.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
2e74a429a322b111c78750ad239f7eaa365bf741
link
/test istio-pilot-multicluster-e2e

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

The pilot-multicluster-e2e test should be irrelevant to this change. I browse some recent commits to 1.1 branch and they all fail at this test with the same errors. E.g. https://github.com/istio/istio/pull/17812, https://github.com/istio/istio/pull/17816, https://github.com/istio/istio/pull/17698, https://github.com/istio/istio/pull/17070, https://github.com/istio/istio/pull/17058

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

Test name
Commit
Details
Rerun command

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

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

/retest

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

Test name
Commit
Details
Rerun command

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

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

@duderino Could you please take a look?

@myidpt @rlenglet Thanks for the review. Please take a look.
@duderino The configmap update is confirmed as an atomic operation.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
562b780556a970ace533ca41a87b5d99e23e2aa5
link
/test istio-pilot-multicluster-e2e

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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
60f724330710d0dff15d858173fc6b063668cdb1
link
/test istio-pilot-multicluster-e2e

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

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

Test name
Commit
Details
Rerun command

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

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

@duderino Could you please take a look? All review comments are addressed now. Thanks.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
3c04f735f09e1f4589304eb119c950d94d19c4d3
link
/test istio-pilot-multicluster-e2e

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


Fix flapping commit log tests due to race flush detection

cc @kobolog @xichen2020

Coverage decreased (-0.1%) to 77.842% when pulling 08e118846310e39eb1ebd6b8b403ed804fdd09dd on fix-flakey-commitlog-tests into 2b6421ab5d81b0d69dbec9a991288625fed3207b on master.


Center tab items on large screens

I feel like these tab items should center together (align-items: center, if you will), so they look natural on large screens:
Here's how it looks today, which I feel is incorrect:

Just for reference, here is the part of the md spec where they show tabs on desktop https://material.google.com/components/tabs.html#tabs-usage. Does not look like they let them stretch the whole length of the viewport on desktop.

Also, and this is interesting, i could not find any spec for bottom navigation on desktop beyond a line saying that its best to not use bottom navigation on desktop. https://material.google.com/components/bottom-navigation.html#
Bottom navigation is primarily for use on mobile. To achieve a similar effect for desktop, use side navigation.

Yea, not sure what is standard here. Looks like they left-align them but we're using the secondary/bottom nav now for MD. iOS I thought centered them, but it might stretch them, anyone test an iPad on a tabbed app?

Since i feel like an actual app is a better reference than just the standard here is the youtube app (which i feel is the standard for tabbed apps on android) on my nexus 7 in landscape.

Here's the App Store on iPad. The Podcast app is the same.

Thanks @patrickmcd!

CSS:
ion-tabbar {
    justify-content: center;
}

/* or any determined max width */
.tab-button {
    max-width: 150px;
}

Note: not tested with tab highlight


Sleek Updates

Made buttons more responsive (Play/pause button as well as playlist select buttons.) Revised earthy and lover themes according to Morpheus's suggestions. Updated images. Added border to playlist select to break up the themes a bit, made play/pause button bigger and made Player text color be assigned to spice-misc to allow more customization.

I'm not quite sure why the validate theme name check failed, any thoughts or does it not matter?

I'm not sure about the border around the playlist selection as well as the gradient, I can remove it if you'd like.

Sorry, I preferred the previous Sleek look.
Also, I personally don't like the colour schemes (there are still some elements that are not readable).
Lastly, do not create a pull request with different changes, or it will not be possible to merge it if there is something that is not suitable for the repository. For example in this case you should have opened a PR for the colour schemes and another for the UI changes.
But thanks for contributing.

In general, create pull requests for changes as much atomic as possible. It makes it easier to review them.

@morpheusthewhite Alright, will try to do so in the future


Option to add space before slash for self-closing tag

This will be in the next release. You'll need to set xmlTools.enforcePrettySelfClosingTagOnFormat to true to enable the feature.


show confetti when quiz is done

actually quite important, because the Next button when there is no question to answer anymore only shows a progress rendering but no clearer visual indication

That is, we would like that if we click Next but no unanswered question is there anymore we come to a page saying "congrats, you answered all questions". If we have a confetti animation it is even nicer


Structural Comparison Failing

Structural Comparisons in the vivado_phys_netlist_cmp flow are failing with the following error: FAIL: Unhandled properties for type GND.
Note, due to the way structural comparisons are used in the vivado_structural_error_injection flow, the compare tool will not report failures to ninja. So running a command line like python scripts/run.py vivado_phys_netlist_cmp byu/alu will appear to succeed, but checking the associated struct_cmp.log file will show the above error.

It seems the problem stemmed from comparing netlists (a,b) when a=reversed netlist and b=physical netlist, and not vice versa.   We iterate through netlist a, and don't handle certain things that show up in the reversed netlist (eg assign statements, LUTs that don't drive anything).
We used to compare (physical, reversed), but at some point it was switched.  I think the switch is causing the issues.  I'm working on PR #368 that fixes the structural compare to work even when iterating through a reversed netlist.  I'm making using of some of the netlist cleanup code I've written previously that removes assign statements and unused LUTs.


"RowChangedEvent fallback row, ignore it" when injecting CDC and Kfaka consumer network partition

What did you do?

Topo:  Upstream TiDB --CDC-- Kafka -- Consumer -- MySQL
create Kafka open protocol changefeed: /cdc  cli  changefeed  create "--server=<IP_ADDRESS>:8301" "--sink-uri=kafka://downstream-kafka.cdc-kafka-controller-tps-7508966-1-706:9092/cdc_kafka_network_partition?replication-factor=2&max-message-bytes=1048576&protocol=open-protocol" "--changefeed-id=kafka-open-protocol-task-1
Run sysbench prepare
Run sysbench workload and at the same time inject CDC owner to Kafka controller network partition.
Run kafka consumer to consumer the kafka msg to MySQL
Do data consistency check between TiDB and MySQL

What did you expect to see?
Kafka consumer should not panic, and kafka msg consumed correctly and data consistency check passed.
What did you see instead?
Consumer shoult not panic, and data consistency check passed betwen TiDB and MySQL
[writer.go:362] ["RowChangedEvent fallback row, ignore it"] [commitTs=450190641590173785] [watermark=450190655496913022] [partition=2] [row="{\"StartTs\":0,\"CommitTs\":450190641590173785,\"RowID\":0,\"PhysicalTableID\":0,

Versions of the cluster
CDC : 350a2fb4596b489af648982082e60ea5735178ff
Consumer: c70aaf2590c0efcf4c8cce58d52ed88e7c20d287

/severity major

This is caused by the message duplication, no message loss, this message can be ignored and does not affect eventual consistency.
We are going to investigate this issue further

This issue cannot be reproduced, close it. If reproduced, reopen this issue


[AIRFLOW-1337] log_format key names should be lowercase.

Dear Airflow maintainers,
follow-up to PR: #2392

JIRA
https://issues.apache.org/jira/browse/AIRFLOW-1337
Description
log_format key names should be lowercase in airflow.cfg
Tests
run_unit_test.sh (1.9.x) in local env python3.5

Codecov Report

Merging #2395 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #2395      +/-   ##
==========================================
+ Coverage   69.25%   69.26%   +<.01%
==========================================
  Files         146      146
  Lines       11231    11231
==========================================
+ Hits         7778     7779       +1
+ Misses       3453     3452       -1

Impacted Files
Coverage Δ

airflow/settings.py
88.88% <100%> (ø)
:arrow_up:

airflow/jobs.py
75.27% <0%> (+0.1%)
:arrow_up:

Continue to review full report at Codecov.

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

LGTM merged


Extension not working on PHP-FPM 7.0

I tried building the sample code from here;
http://www.php-cpp.com/documentation/functions
It does work on CLI however it doesn't work on web. According to php.ini it definitely did parsed the extension's .ini file. It also does not throw any other error than Call to undefined function.
I am running on PHP-FPM 7.0 behind nginx. PHP is from remi repo if that makes a difference.

Never mind. I added  -lmysqlpp -lmysqlclient to ld as I intended to work with mysql. But apparently that was not set up correctly.


Bug of demo.py

According to your code, the input image is in RGB format:
https://github.com/hustvl/SparseInst/blob/fd6fb385b152d232988542aae3072a8fe5d545ae/configs/Base-SparseInst.yaml#L33
and the given mean and std is also in  RGB format:
https://github.com/hustvl/SparseInst/blob/fd6fb385b152d232988542aae3072a8fe5d545ae/configs/Base-SparseInst.yaml#L4-L5
In demo.py, the image is read as RGB format:
https://github.com/hustvl/SparseInst/blob/fd6fb385b152d232988542aae3072a8fe5d545ae/demo.py#L93
and then passed to DefaultPredictor:
https://github.com/hustvl/SparseInst/blob/fd6fb385b152d232988542aae3072a8fe5d545ae/sparseinst/d2_predictor.py#L36-L49
In DefaultPredictor, the image is firstly converted into BGR format:
https://github.com/facebookresearch/detectron2/blob/96c752ce821a3340e27edd51c28a00665dd32a30/detectron2/engine/defaults.py#L309
and finally be normalized according to the given mean and std:
https://github.com/hustvl/SparseInst/blob/fd6fb385b152d232988542aae3072a8fe5d545ae/sparseinst/sparseinst.py#L61
As the  given mean and std is in RGB format and the image is in BGR format, so there remains a mismatch.

Hi @leftthomas, I'm so sorry for the late reply.
Thank you for reminding me of this problem and I'll check and fix it soon~

@wondervictor it still haven't been fixed now.

Thank you for the wonderful project. I also encountered the same problem, when will it be fixed?


Gracefully handle unconfirmed email addresses in password reset

Fixes #4548

Can we write a test that tests that UserController gracefully handles this?

Added test and logged exceptions.


resolves #24

Revised the comments per suggestions from discussion in #24
I also introduced a new --step-summary to allow using GITHUB_STEP_SUMMARY feature. The summary posted has the same content as the --thread-comments feature.
Lastly, pylint has updated their support for python 3.11, so we can now use the latest python version again in CI. I also fixed some other warnings pylint didn't like about using dict(...) instead of literal {...}.

The problem that sonar cloud is highlighting is not an easy fix. I need to use regex in that situation. To avoid using regex for that, I would need to replace it with a lot of new code. TBH, I think the warning is a false positive because the pattern is so long.

It is a single job summary. notice the name of the job is automatically used as a label.
My real point is that other steps can also add content to GITHUB_STEP_SUMMARY that will show up in the same job summary.
example: # the job name
  steps:
    - run: echo "first step" >> $GITHUB_STEP_SUMMARY
    - run: echo "second step" >> $GITHUB_STEP_SUMMARY

This will result in the following job summary:

first step
second step

I'm trying to add a unit test to cover the 1 new line about the "LGTM" comment...

I think the sonar cloud was trying to say "don't begin regex patterns with .*". But they used so many complex sentences that I had trouble understanding the problem. Its happy now, so I'm back to testing the intentional changes here 😥.

I'll release minor version bump (v1.6.0) since the step summary is a new feature.

The sonar cloud linter is getting a bit ridiculous. It's latest check on main branch failed because:

It doesn't like regex patterns that start with . tokens
Now it says the logger.basicConfig() is a possible security risk.

I can probably fix point 2, but I cannot fix point 1 without a huge rewrite.
https://github.com/cpp-linter/cpp-linter/blob/5977c76e857f79d5c350c6740fecdef00660ad27/cpp_linter/clang_tidy.py#L8
The problem with not using .+ to match a filename (and relative path) is that practically any character could be used (which is what . regex token is for).
TBH, I spent way more time trying to fix things in this PR that were not related to my intentional changes. 👎🏼


It is a mazegame in which you have to reach the coin at the end of the level. After some levels you will get the message "YOU WIN". Congrats!
How do you play your game?
Press WASD to move, J to restart.
Code
Check off the items that are true.

[x ] The game was made using the Sprig editor.
[x ] The game is placed in the in the /games directory.
[x ] The code is significantly different from all other games in the Sprig gallery (except for games labeled "demo").
[ x] The game runs without errors.
[x ] The name of the file/game contains only alphanumeric characters, -s, or _s.
[x ] The game name is not the same as the others from gallery

Image (If an image is used)

[x ] The image is in the /games/img directory.
[ ] The name of the image matches the name of your file.

Thanks for your PR!

Hey! If you want us to review please click in "Ready for review" :)

Closing this PR due to inactivity. Please let me know if you'd like this reopened.


Mailing link does not show up blue until hovered

Need some way to show it as a link without having to hover it.

fixed with css change, just committed


Support for PNG url?

Does this gem support the png printing functionality?
https://developers.google.com/chart/interactive/docs/printing
I would like to just get the URL of a chart to stick into an email.

The gem supports adding listeners now, see:

https://github.com/winston/google_visualr/blob/master/lib/google_visualr/base_chart.rb#L55
https://github.com/winston/google_visualr/blob/master/spec/google_visualr/base_chart_spec.rb

So it could be possible to have the PNG functionality. A convenience helper method can be added to the gem to make that easier too.
However you won't be able to directly use it in your email because most (all?) email clients will not allow JavaScript to run, and hence it's not possible to just use the chart functionality directly in emails.
It will be a two step process where you need to get the URLs manually before putting them in emails.
Hope this answers?

any news? if you could directly turn the chart in PNG, I could add the image to a pdf file ( with Prawn ) or other type of file that does not support javascript

I ended up using Google's deprecated image charts: https://developers.google.com/chart/image/

Ok but if I want convert the Gantt chart or Timeline chart into png?


v3: fix model fetch DecoderOnly

Small fix

Closes 404 when trying Qwen in V3 #723

Hi there 👋 v3 will use the name model instead of decoder_merged_model, as the latter is the result of a legacy conversion process which created multiple versions of the model (w/ and w/o past key value inputs). So, this change isn't needed.
If you want to override the behaviour yourself, you can use the model_file_name option when loading the model.


Is there an option to disable casino script?

No, but you can edit autopilot.js to disable it.
Why would you disable it?

I believe in some cases sleeves earn a lot more money than casino.
06.09.2022 08:26:37, David Westerink пишет:

No, but you can edit autopilot.js to disable it.
Why would you disable it?
—
Reply to this email directly, view it on GitHub
https://github.com/alainbryden/bitburner-scripts/issues/230#issuecomment-1237673320,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACDJ4FBS5WZKOECM54BUQO3V43IY3ANCNFSM6AAAAAAQE7FAII.
You are receiving this because you authored the thread.Message ID:
@.***>

This case is supposed to be handled already. Autopilot detects if in the
first minute if the BN you are earning money fast enough for casino to be
unnecessary, and skips it for that reset.
On Tue., Oct. 11, 2022, 5:21 a.m. Кирилл Фролов, @.***>
wrote:

I believe in some cases sleeves earn a lot more money than casino.
06.09.2022 08:26:37, David Westerink пишет:

No, but you can edit autopilot.js to disable it.
Why would you disable it?
—
Reply to this email directly, view it on GitHub
<
https://github.com/alainbryden/bitburner-scripts/issues/230#issuecomment-1237673320>,

or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/ACDJ4FBS5WZKOECM54BUQO3V43IY3ANCNFSM6AAAAAAQE7FAII
.
You are receiving this because you authored the thread.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/alainbryden/bitburner-scripts/issues/230#issuecomment-1274291182,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AARN33P6UHMC4Z3PVGRPEXTWCUPQZANCNFSM6AAAAAAQE7FAII
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Added an explicit option to disable the casino completely in #248


[Input] NotifyFieldChanged is called twice for all FluentInputBase derived components

Fix #1830 by adding a check to see if NotifyFieldChanged has already been called.
protected virtual async Task ChangeHandlerAsync(ChangeEventArgs e)
{
    var _notifyCalled = false; //<--👈added
    var isValid = TryParseValueFromString(e.Value?.ToString(), out TValue? result, out var validationErrorMessage);

    if (isValid)
    {
        await SetCurrentValueAsync(result ?? default);
        _notifyCalled = true; //<--👈added
    }
    else
    {
        if (FieldBound && CascadedEditContext != null)
        {
            _parsingValidationMessages ??= new ValidationMessageStore(CascadedEditContext);

            _parsingValidationMessages.Clear();
            _parsingValidationMessages.Add(FieldIdentifier, validationErrorMessage ?? "Unknown parsing error");
        }
    }
    if (FieldBound && !_notifyCalled)  //<--👈changed
    {
        CascadedEditContext?.NotifyFieldChanged(FieldIdentifier);
    }
}

@kamazheng that is a whole differnet issue and has nothing to do with this NotifyFiledChanged.
Your issue has been addressed already in #1965


Provide a root workspace

          I've juste seen you starting development.

I hope you're enjoying getting into development.
I'm pulling your branch, to read over my lunch.
I realised that my IDE couldn't analyse the code with rust-analyzer.
So I found a trick to do it.
I add a root Cargo.toml to reference the repository member project.
[workspace]

members = [
    "source/river",
]

I don't know if you're used to doing this. Just a suggestion.
Thank you for your time and your work.
I wish you a good day.
Originally posted by @lperdereau in https://github.com/memorysafety/river/issues/19#issuecomment-2036934124

@lperdereau moving this to a new issue as it is off topic for the other PR.
Thanks for the report! Yes, you'll need to launch from the source/river folder for now, we could consider adding a top level workspace to allow for this as you've mentioned. If you'd like to open this as a PR I'd accept it.

Oh yeah excuse me.
I will do the job to close this issue :+1:


campaign didn't compute

Problem
This campaign.json didn't compute. Lambda functions don't show any errors.
{"campaign_creator": "nsmith", "campaign_managers": ["nsmith"], "campaign_status": "Start", "coverage": {}, "dashboard_settings": "", "description": "Collecting Schools across Jakarta", "edited_at": "2018-10-02", "edited_by": "nsmith", "end_date": "2018-12-31", "link_to_omk": false, "map_type": "", "name": "Jakarta Schools", "participants_count_per_type": {}, "remote_projects": [], "selected_functions": {"function-1": {"function": "FeatureAttributeCompleteness", "feature": "amenity=school", "attributes": {"amenity": ["school"], "name": []}, "type": "schools"}, "function-2": {"function": "CountFeature", "feature": "amenity=school", "attributes": {"amenity": ["school"], "name": []}, "type": "schools"}, "function-3": {"function": "MapperEngagement", "feature": "amenity=school", "attributes": {"amenity": ["school"], "name": []}, "type": "schools"}}, "start_date": "2018-01-01", "thumbnail": "https://s3-us-west-2.amazonaws.com/hotosm-fieldcampaigner-data-production/campaigns/2817d40cd67844249e166f183b38ea60/thumbnail.png", "total_participants_count": 0, "types": {"type-1": {"type": "schools", "feature": "amenity=school", "tags": {"amenity: school": [], "name": []}}}, "uploader": "nsmith", "uuid": "2817d40cd67844249e166f183b38ea60", "version": 4}

Solution
Why?

My campaign is also computing after several days of creation: https://campaigns.hotosm.org/campaign/2a07007f604742fab81b8111ffd54e12

I am also having the same issue with a few campaigns:
https://campaigns.hotosm.org/campaign/f74df638bca34fffbdf4f923373f303d
https://campaigns.hotosm.org/campaign/dd7b3627dc6942dc9798ea094f8c680b

Quick update here: it looks like reason for failed campaigns from @jessbeutler and @ccamara were the geojsons. The geojson features were MultiPolygon and these were causing errors. Changing the feature type to Polygon fixes the issue.

@smit1678 do you still have those MultiPolygon geojsons?

Yes!
https://gist.github.com/smit1678/da41ebb89d13432b087da99fbe27eb22
https://gist.github.com/smit1678/34a14c973eb1274ffb47559a13c4ffd3

and to fix those campaigns, you edited the geometry type from "MultiPolygon" to "Polygon" in the geojson?

Yes, I just directly edited the geojson to change the type to Polygon and then removed the array the polygon was in.

@smit1678 what about this?

I think I will try this
I've created a campaign 15 days ago and it's still computing !!!

@Cybereric it looks like the geojson you used in that campaign is linestrings and not polygons. Can you change your file to polygons and then create a new campaign to test? I'll delete the other campaign that didn't process.

@pierrealixt Yeah I think a warning looks and works well. Will this error come up with linestrings as well?

I tried a first time to edit the geojson file by doing a "search / replace" for "linestring" to "polygon"
It did not work.
So I loaded the file in http://umap.openstreetmap.fr and there I could edit the sectors and transform them into polygons.
I downloaded the file to reload it in Map Campaigner.
The campaign is now functional >>> https://campaigns.hotosm.org/campaign/3b49da3b5ba64e899215bbdb0938333d

Closing this since the fix was pushed to limit geojson types to polygon.


[$250] IOS/Android - Workspace- Google search doesn't work in Information, Company, Personal and  Additional information pages

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Issue was found when executing PR: https://github.com/Expensify/App/pull/8826
Action Performed:

Launch the app
Log in with expensifail account
Go to Setting - Preferences
Enable Secure Staging server
Go to any Workspace
Tab connect Bank account
Tab Connect online with Plaid
Select Wells Fargo bank account
Tap user name: user_good
Tap password: pass_good
Tap Continue
Check the search address on Company, Personal and  Additional information pages

Expected Result:
Google search works in Information, Company, Personal and  Additional information pages
Actual Result:
Google search doesn't work in Information, Company, Personal and  Additional information pages
Workaround:
Unknown
Platform:

Where is this issue occurring?

iOS
Android

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation\
https://user-images.githubusercontent.com/93399543/167945161-d96c689f-17b2-4081-bdd7-67dce30e4065.mp4
https://user-images.githubusercontent.com/93399543/167945164-6ded2128-34ff-429d-a543-e58372ba63a8.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause
Slack conversation:
View all open jobs on GitHub

Is this issue still available to work on?

Can't reproduce the issue due to: https://github.com/Expensify/App/pull/8966#issuecomment-1126263948
Will look into this once that PR is merged

Able to reproduce the issue. The search seems to work fine on web.

Upwork Job

@kbecciv, how do you do step 4 (enable Secure Staging server)?

@Luke9389 I believe step 4 refers to navigating to Settings > Preferences and enabling Use Secure Staging Server:

Looks like we are using a wrong API key. Did you follow the instructions (here)[https://github.com/FaridSafi/react-native-google-places-autocomplete]?
Step 2.

Get your [Google Places API keys](https://developers.google.com/maps/documentation/places/web-service/get-api-key/) and enable "Google Places API Web Service" (NOT Android or iOS) in the console. Billing must be enabled on the account.

Step 3.

Enable "Google Maps Geocoding API" if you want to use GoogleReverseGeocoding for Current Location

Screenshot of the error attached.

@parasharrajat @MitchExpensify @Luke9389

Yeah, this is known to us. It seems like a duplicate issue cc: @Julesssss.

Can we put this on hold or something so that people don't spend time on it?

It was not supposed to be exported. We will take this down on Monday. There is nothing much an external contributor can do here. cc: @MitchExpensify

Closing as a dupe. @MitchExpensify please close out the UpWork job, thanks!

Got it, Upwork job closed @Julesssss

Thank you kindly


Chat Color Plugin - Minor Possible Bug

Type
Incorrect behavior
Operating System
Windows
OS Version
Windows
Bug description
Was changing some colors around & I noticed a minor bug. I changed the “Clan Chat channel name (transparent” to red (can be any color), whenever someone types & sends a message it is red like I chose. But, when there is an clan announcement like someone getting a item drop, pet or a level up, the Clan Chat Channel Name is the generic color it is normally. Would be great to get this fixed, but it’s not a huge issue.
Screenshots or videos

RuneLite version
Runelite Version 1.9.3 Launcher Version 2.5.0
Logs
No response

This bug also exists on opaque mode.


Improve Profile Page

Issue #589 for GCI
So far, I have setup the form. How do you want me to handle the data entered in it? Should it go to the database? If so, what's the structure?

Coverage remained the same at 82.507% when pulling 45eef74c5069527a88bd485fc952542406a7f995 on NumberC:patch-1 into 1799c45fd127f471ae67d2eb174d32315312d133 on CircuitVerse:master.

@nitin10s

Hey! Can you please attach a screenshot? Thanks.

@nitin10s Those are the options. When you click on any of those buttons, the fields will change to the fields required for a teacher or student.

Looks pretty clean to me if we judge by the aesthetics. Good work.

To refactor my fork, I will be closing this and making a new PR. The result will still be the same

Nevermind, that was meant for another PR


[ALLUXIO-3241] Fix impersonation regex

https://alluxio.atlassian.net/browse/ALLUXIO-3241

@madanadit

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/20502/
Test PASSed.

How about adit.madan? Looks like use of the delimiter period is a valid user name.
Ref:   http://manpages.ubuntu.com/manpages/bionic/en/man5/adduser.conf.5.html
VALID NAMES
adduser  and addgroup enforce conformity to IEEE Std 1003.1-2001, which allows only
the following characters to appear  in  group  and  user  names:  letters,  digits,
underscores,  periods,  at signs (@) and dashes. The name may no start with a dash.
The "$" sign is allowed at the end of usernames (to conform to samba).
          An additional check can be adjusted via the configuration parameter  NAME_REGEX  to
          enforce a local policy.

@madanadit I updated the regex (and test) to include ..

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/20503/Failed Tests: 1org.alluxio:alluxio-tests: 1alluxio.server.configuration.ConfigCheckerIntegrationTest.multiMasters
Test FAILed.

Thanks for adding period. At sign @ is the only other character that is also valid?

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/20509/Failed Tests: 1org.alluxio:alluxio-tests: 1alluxio.server.ft.MasterFailoverIntegrationTest.failoverJournalFencingTest
Test FAILed.

Jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/20513/
Test PASSed.


RFC: Standardize Intro to Programming

Problem:
Intro to Programming is different in format and approach from the other sections of OSSU.
Duration:
Aug 15, 2020
Background:
The Intro to Programming (hereafter referred to as ITP) courses were added after acceptance of this RFC. At the time, I hypothesized that giving students choice about the intro course would lower the debate about intro courses. My personal assessment is that this has been moderately successful. At the same time, this structure has come with downsides:

By giving students choice between two entry points, some students join the Gitter to ask which they should take. This has happened about a half dozen times since the adding ITP.
Some students have taken both of the ITP course options. This is not desirable, OSSU wants students to advance in the curriculum, and does not recommend taking excessive intro classes.

The two options were both Coursera specializations. Rather than link to the individual courses, there was a single link to the specialization. This led to issues:

Because individual Coursera courses can be audited, but entire specializations, students regularly ask in the Gitter about the need to pay.
Students have not been clear if the time estimates are for the whole specialization or just the first course in the specialization, as demonstrated in this issue.

One of the courses, Python for Everybody (Py4E) has a freely available course site from the course creator. OSSU now recommends students use that site.
While the two options are meant for absolute beginners, they go to very different depths. Fundamentals of Computing (FoC) takes twice as long as Py4E. In this extra time, FoC covers more material. This leads to issues:

Students are meant to take different courses following their intro, depending on which path they chose. After FoC, students should take Missing Semester. After Py4E students should take Introduction to Computer Science and Programming using Python.
It’s not clear that all of the material in FoC is appropriate for students new to programming. In a recent issue, a contributor (@spamegg1) noted that FoC goes quite deep into algorithmic complexity, which goes beyond the goals of an Introduction to Programming, or even an Introduction to Computer Science.
The advanced material in FoC is covered later in other OSSU courses.

It should be noted, there have been no complaints about either course. There have been a number of students who have praised (Py4E). When students have asked for recommendations of which course to take, there have been contributors that recommend Py4E and others that recommend (FoC).
Proposal:
To simplify the Intro to Programming section, OSSU should recommend only Python for Everybody. Doing so will address the above issues. There is no expected degradation of the curriculum, as Py4E is already a recommended course.
Alternatives:

Rather than recommending just Py4E, OSSU could recommend only FoC. This does not seem appropriate because of the questions about FoC’s depth.

Keep the curriculum as it is.

Contributors can view the proposed change here.

Very nice! Totally behind this. Awesome work as usual @waciumawanjohi

Im going to weigh in with my limited knowledge here. As an introductory course, FoC might go into a lot of depth, but I feel like the deeper topics covered in FoC are quiet simply put 'Fundamentals', which are of extreme importance to CS.
These topics might be covered later in OSSU, but I personally feel like being introduced to them early on will  help solidify them, and the redundancy will also help make them stick easier.
I propose option 2, keep the curriculum as is, yet put a note stating that it goes in depth. Some sort of warning?
Amazing write up though, and very well explaine! @waciumawanjohi

One thing that still remains unclear is the number of hours field. Is this the overall number of hours the student is expected to work (including video lectures, assignments, recommended readings, quizzes etc.)?

@krishnakumarg1984 The duration and effort should be an approximation of total time committed, including watching lectures and completing assignments. These are generally taken directly from the hosting platform; both Coursera and edX report these numbers and we simply repeat that information here.

Thank you! I am doing the python for everybody specialisation in Coursera.
I think it's certainly more than 58 hours.

https://www.coursera.org/specializations/python
Towards the bottom right of the page it says:

Approx. 8 months to complete
Suggested 3 hours/week

That would make it 3 * 4 * 8 = 96 hours total.

It's made more complicated by the fact that Py4E is on multiple platforms. I took the estimates from edX, which suggest 7 weeks for each course (there are 2) and 2-4 hours per week.
Py4E on Future Learn is similarly 6 weeks each for 2 courses, and 4 hours per week.
But perhaps the true solution is to stop trying to report effort and duration. The information is available through the platforms offering the courses. It's arguably of limited usefulness for students that are intending to take 20+ courses sequentially. The number that OSSU should be attempting to measure is how long does it take to complete the curriculum.

But perhaps the true solution is to stop trying to report effort and duration.

Yes, probably. Students can figure it out on their own from whatever platform they are using. If anyone asks, we can help them on Gitter.

There are further important considerations.
The Py4E website does not contain everything that Coursera offers. i.e. although the two platforms have a large intersection (~90-95%), they are not identical. For example, forums discussing assignments, tidbits on computing conversations with the instructor etc. (the conversations are on YouTube, but Coursera links to them directly at the end of each week for every course).
There is an even more important thing now. Coursera has been updated to integrate Py4E website in the curriculum. i.e. the click-through 'next/previous' pages to be marked complete fully mention Py4E website. Even the assignments require download of text files and example python files from the Py4E website.
Well, even the bespoke assignments autograder developed by Dr Charles at Py4E can automatically send grades to Coursera. The course website is mentioned in videos and the grading explanation is provided by Dr Charles.
I know Coursera pushes hard to make students pay, but having taken this specialisation, I think that this is the better superset.
Regarding the effort required, the 90-130 hours ballpark seem to be okay to me.
Final important thing: EdX only has course 1 and course 2 of the py4E textbook (only until chapter 11) and should not be used for providing time estimates.

Close of the Comment Period
Findings:

This RFC had very low engagement, with only 3 commenters and the proposer.
The effort/duration estimate for Py4E is currently undercounted.
Support for keeping FoC was voiced.
Support for removing FoC was voiced.

Response:

The intro courses of OSSU used to generate great amounts of debate and eat up lots of time and energy. That this is no longer the case suggests that most students and contributors are largely satisfied and unworried about the outcome of this iteration. That is a good outcome!
In supporting keeping Fundamentals of Computing there was a suggestion that FoC be preceded with a warning. This seems problematic. The section is already preceded by text explaining that FoC goes to greater depth than Py4E. But students still ask in gitter what the difference is between the courses, suggesting a warning may not be efficacious.
It seems clear that the duration estimate for Py4E should be raised.

Conclusion
The proposal will be merged in and the estimate for duration will be raised to 34 weeks.


[runtime] fix threading test deinitialization order causing a data race

We need to wait for the thread to finish before deinitializing the notification.

For more info see https://github.com/iree-org/iree/actions/runs/8788864488/job/24117319327?pr=17125#step:4:10997
 805/1388 Test  #745: iree/base/internal/threading_test ...............................................................................***Failed    1.41 sec
[==========] Running 4 tests from 2 test suites.
[----------] Global test environment set-up.
[----------] 3 tests from ThreadTest
[ RUN      ] ThreadTest.Lifetime
[       OK ] ThreadTest.Lifetime (16 ms)
[ RUN      ] ThreadTest.CreateSuspended
LLVMSymbolizer: error reading file: No such file or directory
==================
WARNING: ThreadSanitizer: data race (pid=105085)
  Write of size 1 at 0x7ffc801d42b0 by main thread:
    #0 pthread_mutex_destroy <null> (threading_test+0x278fd6)
    #1 iree_notification_deinitialize /work/runtime/src/iree/base/internal/synchronization.c:640:3 (threading_test+0x30ec22)
    #2 (anonymous namespace)::ThreadTest_CreateSuspended_Test::TestBody() /work/runtime/src/iree/base/internal/threading_test.cc:114:3 (threading_test+0x3093db)
    #3 void testing::internal::HandleSehExceptionsInMethodIfSupported<testing::Test, void>(testing::Test*, void (testing::Test::*)(), char const*) /work/third_party/googletest/googletest/src/gtest.cc:2613:10 (threading_test+0x363abf)
    #4 void testing::internal::HandleExceptionsInMethodIfSupported<testing::Test, void>(testing::Test*, void (testing::Test::*)(), char const*) /work/third_party/googletest/googletest/src/gtest.cc:2649:14 (threading_test+0x363abf)
    #5 testing::Test::Run() /work/third_party/googletest/googletest/src/gtest.cc:2688:5 (threading_test+0x339911)
    #6 testing::TestInfo::Run() /work/third_party/googletest/googletest/src/gtest.cc:2837:11 (threading_test+0x33b0a8)
    #7 testing::TestSuite::Run() /work/third_party/googletest/googletest/src/gtest.cc:3016:30 (threading_test+0x33c150)
    #8 testing::internal::UnitTestImpl::RunAllTests() /work/third_party/googletest/googletest/src/gtest.cc:5922:44 (threading_test+0x354b2a)
    #9 bool testing::internal::HandleSehExceptionsInMethodIfSupported<testing::internal::UnitTestImpl, bool>(testing::internal::UnitTestImpl*, bool (testing::internal::UnitTestImpl::*)(), char const*) /work/third_party/googletest/googletest/src/gtest.cc:2613:10 (threading_test+0x364a2f)
    #10 bool testing::internal::HandleExceptionsInMethodIfSupported<testing::internal::UnitTestImpl, bool>(testing::internal::UnitTestImpl*, bool (testing::internal::UnitTestImpl::*)(), char const*) /work/third_party/googletest/googletest/src/gtest.cc:2649:14 (threading_test+0x364a2f)
    #11 testing::UnitTest::Run() /work/third_party/googletest/googletest/src/gtest.cc:5486:10 (threading_test+0x354183)
    #12 RUN_ALL_TESTS() /work/third_party/googletest/googletest/include/gtest/gtest.h:2316:73 (threading_test+0x3124fa)
    #13 main /work/runtime/src/iree/testing/gtest_main.cc:20:13 (threading_test+0x3124fa)

  Previous atomic read of size 1 at 0x7ffc801d42b0 by thread T2:
    #0 pthread_mutex_lock <null> (threading_test+0x295a66)
    #1 iree_notification_post /work/runtime/src/iree/base/internal/synchronization.c:644:3 (threading_test+0x30ec4f)
    #2 (anonymous namespace)::ThreadTest_CreateSuspended_Test::TestBody()::$_2::operator()(void*) const /work/runtime/src/iree/base/internal/threading_test.cc:85:5 (threading_test+0x309504)
    #3 (anonymous namespace)::ThreadTest_CreateSuspended_Test::TestBody()::$_2::__invoke(void*) /work/runtime/src/iree/base/internal/threading_test.cc:81:35 (threading_test+0x309504)
    #4 iree_thread_start_routine /work/runtime/src/iree/base/internal/threading_pthreads.c:123:29 (threading_test+0x30fcf0)

  Location is stack of main thread.

  Location is global '??' at 0x7ffc801b6000 ([stack]+0x00000001e2b0)

  Thread T2 (tid=105135, running) created by main thread at:
    #0 pthread_create <null> (threading_test+0x27780b)
    #1 iree_thread_create /work/runtime/src/iree/base/internal/threading_pthreads.c:173:10 (threading_test+0x30f7cd)
    #2 (anonymous namespace)::ThreadTest_CreateSuspended_Test::TestBody() /work/runtime/src/iree/base/internal/threading_test.cc:90:3 (threading_test+0x308ef1)
    #3 void testing::internal::HandleSehExceptionsInMethodIfSupported<testing::Test, void>(testing::Test*, void (testing::Test::*)(), char const*) /work/third_party/googletest/googletest/src/gtest.cc:2613:10 (threading_test+0x363abf)
    #4 void testing::internal::HandleExceptionsInMethodIfSupported<testing::Test, void>(testing::Test*, void (testing::Test::*)(), char const*) /work/third_party/googletest/googletest/src/gtest.cc:2649:14 (threading_test+0x363abf)
    #5 testing::Test::Run() /work/third_party/googletest/googletest/src/gtest.cc:2688:5 (threading_test+0x339911)
    #6 testing::TestInfo::Run() /work/third_party/googletest/googletest/src/gtest.cc:2837:11 (threading_test+0x33b0a8)
    #7 testing::TestSuite::Run() /work/third_party/googletest/googletest/src/gtest.cc:3016:30 (threading_test+0x33c150)
    #8 testing::internal::UnitTestImpl::RunAllTests() /work/third_party/googletest/googletest/src/gtest.cc:5922:44 (threading_test+0x354b2a)
    #9 bool testing::internal::HandleSehExceptionsInMethodIfSupported<testing::internal::UnitTestImpl, bool>(testing::internal::UnitTestImpl*, bool (testing::internal::UnitTestImpl::*)(), char const*) /work/third_party/googletest/googletest/src/gtest.cc:2613:10 (threading_test+0x364a2f)
    #10 bool testing::internal::HandleExceptionsInMethodIfSupported<testing::internal::UnitTestImpl, bool>(testing::internal::UnitTestImpl*, bool (testing::internal::UnitTestImpl::*)(), char const*) /work/third_party/googletest/googletest/src/gtest.cc:2649:14 (threading_test+0x364a2f)
    #11 testing::UnitTest::Run() /work/third_party/googletest/googletest/src/gtest.cc:5486:10 (threading_test+0x354183)
    #12 RUN_ALL_TESTS() /work/third_party/googletest/googletest/include/gtest/gtest.h:2316:73 (threading_test+0x3124fa)
    #13 main /work/runtime/src/iree/testing/gtest_main.cc:20:13 (threading_test+0x3124fa)

SUMMARY: ThreadSanitizer: data race (/work/build-tsan/runtime/src/iree/base/internal/threading_test+0x278fd6) in pthread_mutex_destroy
==================


Added PTZ support, improved discovery, and refactored code and coroutines

Hi,
I have had problems with discovery (was not able to detect my camera) and coroutines (exception was not thrown in case of a failed request).
I also added PTZ support and refactored the code.
@lamba92 If you have a moment please have a look at this PR, and thanks for your efforts for adding Kotlin support!

Thank you for the PR :)
I'll have a look as soon as possible!


The error when training the graph_retriever in the HotpotQA

Thanks for your great work!
When I run the run_graph_retriever.py ( in the graph_retriever folder) to train the graph-based recurrent retriever model in the train dataset ( the files in the hotpotqa_new_selector_train_data_db_2017_10_12_fix.zip ) of HotpotQA, there is an error like it.
Traceback (most recent call last):
File "run_graph_retriever.py", line 546, in
main()
File "run_graph_retriever.py", line 264, in main
train_examples = processor.get_train_examples(graph_retriever_config)
File "/DATA/sunzhanchen/learning_to_retrieve_reasoning_paths-master/graph_retriever/utils.py", line 200, in get_train_examples
examples += self._create_examples(file_name, graph_retriever_config, "train")
File "/DATA/sunzhanchen/learning_to_retrieve_reasoning_paths-master/graph_retriever/utils.py", line 429, in _create_examples
assert t in context
AssertionError
Is there any question about the train dataset or any other question?
Thanks you again!

Hi, thank you for posting the issue!  We'd like to reproduce this error in our environment to fix it, as we haven't seen in our environment.
The error might come from this assertion error.

Hi, thank you for posting the issue!  We'd like to reproduce this error in our environment to fix it, as we haven't seen in our environment.
The error might come from this assertion error.

Thanks for your reply, and the command I used is
python run_graph_retriever.py
--task hotpot_open
--bert_model bert-base-uncased --do_lower_case
--train_file_path ./data/hotpotqa_new_selector_train_data_db_2017_10_12_fix/db=wiki_hotpotqa.db_hotpotqa_new_test_tfidf_k=50.pruning_l=100_tag_me=True.prune_after_agg=False.prune_in_article=False_use_link=True_start=
--output_dir ./train_model/retriever/
--max_para_num 50
--tfidf_limit 40
--neg_chunk 8 --train_batch_size 4 --gradient_accumulation_steps 1
--learning_rate 3e-5 --num_train_epochs 3
--use_redundant
--max_select_num 4 \
I want to train the graph-based recurrent retriever model in the HotpotQA train dataset.

Sorry for my late response. It seems that the path to train data may not be correct ./data/hotpotqa_new_selector_train_data_db_2017_10_12_fix/db=wiki_hotpotqa.db_hotpotqa_new_test_tfidf_k=50.pruning_l=100_tag_me=True.prune_after_agg=False.prune_in_article=False_use_link=True_start= but I'm not sure if it's just copying error. I have tried to run training on HotpotQA using our data and codes and I couldn't reproduce the error...
Although I'm not sure if it's the case, I got similar kinds of errors when I was running our model on our own internal data. At that time, I have mistakenly fed inputs with empty context as a TF-IDF retriever failed to return any paragraphs due to some special characters. I'm not sure if it's related to your case or not.

Hi, I encounter the same error. However, it works after I change --tfidf_limit 40 to --tfidf_limit 60. I wonder why this happens as --tfidf_limit seems only to control the number of negative samples?

Thanks, @sysu-zjw for the update! We've tested the code mostly with python 3.6, so the issue you pointed out might have caused the problem. @Frankszc, I close this issue now but please feel free to re-open.

Thanks, @sysu-zjw for the update! We've tested the code mostly with python 3.6, so the issue you pointed out might have caused the problem. @Frankszc, I close this issue now but please feel free to re-open.