Add theme as a locator predicate

Enable using theme as a search predicate in locator

@caalador the tests seem to be failing. Could you investigate please?

Helps to actually check against the values also.


Help needed: built dependencies fail in Azure Function deployment from AzureDevOps

My team has created an Azure function and successfully deployed it using VS Code.
However, we want to set it up to build and deploy through Azure DevOps, in order to take advantage of the many benefits offered.
Unfortunately, no matter how we set up the build and deploy process(es) in Azure DevOps, we run into issues with compiled dependencies not working correctly.
Our dependencies include azure-storage-blob, azure-storage-filelake, and psycopg2, both of which seem to need some building during install.
We created the azure-pipelines.yml just like it's recommended for python3.7.
We also set up a Release pipeline with the Azure Functions 1.* task.
(We've also tries deploying directly from the Build pipeline)
But every time we try something new, we still get errors whenever we trigger the function. In this case, the run fails when trying to import azure-storage

Traceback:

Result: Failure Exception: ModuleNotFoundError: No module named '_cffi_backend'. Troubleshooting Guide: https://aka.ms/functions-modulenotfound Stack:
File "/azure-functions-host/workers/python/3.8/LINUX/X64/azure_functions_worker/dispatcher.py", line 262, in _handle__function_load_request func = loader.load_function(
File "/azure-functions-host/workers/python/3.8/LINUX/X64/azure_functions_worker/utils/wrappers.py", line 34, in call raise extend_exception_message(e, message)
File "/azure-functions-host/workers/python/3.8/LINUX/X64/azure_functions_worker/utils/wrappers.py", line 32, in call return func(*args, **kwargs)
File "/azure-functions-host/workers/python/3.8/LINUX/X64/azure_functions_worker/loader.py", line 76, in load_function mod = importlib.import_module(fullmodname)
File "/usr/local/lib/python3.8/importlib/init.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level)
File "/home/site/wwwroot/GTreasurySaver/init.py", line 6, in  from .adls import ADLSStorageService
File "/home/site/wwwroot/GTreasurySaver/adls.py", line 3, in  from azure.storage.filedatalake import DataLakeServiceClient
File "/home/site/wwwroot/.python_packages/lib/site-packages/azure/storage/filedatalake/init.py", line 7, in  from ._download import StorageStreamDownloader
File "/home/site/wwwroot/.python_packages/lib/site-packages/azure/storage/filedatalake/_download.py", line 7, in  from ._models import
FileProperties
File "/home/site/wwwroot/.python_packages/lib/site-packages/azure/storage/filedatalake/_models.py", line 11, in  from azure.storage.blob import LeaseProperties as BlobLeaseProperties
File "/home/site/wwwroot/.python_packages/lib/site-packages/azure/storage/blob/init.py", line 11, in  from ._blob_client import BlobClient
File "/home/site/wwwroot/.python_packages/lib/site-packages/azure/storage/blob/_blob_client.py", line 24, in  from ._shared.encryption import generate_blob_encryption_data
File "/home/site/wwwroot/.python_packages/lib/site-packages/azure/storage/blob/_shared/encryption.py", line 19, in  from cryptography.hazmat.primitives.padding import PKCS7
File "/home/site/wwwroot/.python_packages/lib/site-packages/cryptography/hazmat/primitives/padding.py", line 13, in  from cryptography.hazmat.bindings._padding import lib

We see the dependencies being built and installed in the build pipeline, and they're there when we download the artifact. But it seems it's not built for the Azure Function environment, or we need to have a flag set for the Function environment to build the dependencies afresh.
I'm sure something like this exists, but we haven't been able to find it yet. After all, as I said at the beginning, we can deploy it by using VS Code.
I'd love some help figureing out how to get it to work through DevOps.
Investigative information
Please provide the following:

Timestamp:
Function App name: mna-nonprod-innov-gtreasury
Function name(s) (as appropriate): GTreasurySaver
Core Tools version:

Contents of the requirements.txt file:
#
# This file is autogenerated by pip-compile
# To update, run:
#
#    pip-compile requirements.in
#
attrs==19.3.0             # via environ-config
azure-core==1.6.0         # via azure-storage-blob, azure-storage-file-datalake
azure-functions==1.2.1    # via -r requirements.in
azure-storage-blob==12.3.1  # via -r requirements.in, azure-storage-file-datalake
azure-storage-file-datalake==12.0.1  # via -r requirements.in
certifi==2<IP_ADDRESS>       # via msrest, requests
cffi==1.14.0              # via cryptography
chardet==3.0.4            # via requests
cryptography==2.9.2       # via azure-storage-blob
environ-config==20.1.0    # via -r requirements.in
idna==2.9                 # via requests
isodate==0.6.0            # via msrest
msrest==0.6.14            # via azure-storage-blob, azure-storage-file-datalake
oauthlib==3.1.0           # via requests-oauthlib
psycopg2==2.8.5           # via -r requirements.in
pycparser==2.20           # via cffi
requests-oauthlib==1.3.0  # via msrest
requests==2.23.0          # via -r requirements.in, azure-core, msrest, requests-oauthlib
six==1.15.0               # via azure-core, cryptography, isodate
sqlalchemy==1.3.17        # via -r requirements.in
urllib3==1.25.9           # via requests
wheel==0.34.2             # via -r requirements.in

I could really use some help.

Hi @Chris-May, thanks for your email.
Seems like your function app is running on Python 3.8, could you confirm if the pipeline is using Python 3.8 instead of Python 3.7?

Hey @Hazhzeng! Thank you so much for taking time to look into this.
The pipeline was using 3.7, but I just changed it, and got the same error.

@Hazhzeng @Chris-May is this issue still open? It looks very similar to my own issue https://github.com/Azure/azure-functions-python-worker/issues/827 and this other new issue that was logged https://github.com/Azure/azure-functions-python-worker/issues/831.
Did you find a workaround @Chris-May ?

Hi @Chris-May , Can we know if this is still persisting, we apologize for not following up frequently.

Closing due to lack of activity. Please open a new issue if there are further questions over this.


Error while loading fmu

While trying to load an fmu get the following error
ERROR: UndefVarError: fmi3ProvidesDirectionalDerivatives not defined
Stacktrace:
 [1] fmi3Load(pathToFMU::String; unpackPath::Nothing)
   @ FMIImport ~/.julia/packages/FMIImport/jYeff/src/FMI3_ext.jl:161
 [2] fmi3Load(pathToFMU::String)
   @ FMIImport ~/.julia/packages/FMIImport/jYeff/src/FMI3_ext.jl:20
 [3] top-level scope
   @ REPL[2]:1

It seems a typo here

Dear @Sov-trotter ,
thanks for the issue. We are currently working on refactoring the FMI3-Code to match the new FMI.jl topology (in fact, there are much more issues than just that typo). I hope that we can provide an update next week at the latest.
Regards!

Sure. I have been experimenting around abit and can conclude the same. Do let me know when you're open for any PR's. Thanks


fix: converting circular structure to json

Closes #643

@moltar

Wouldn't 429 be caught here?
https://github.com/ScaleLeap/amazon-advertising-api-sdk/pull/679/files#diff-b3d62e5c74806d2b785aa734d35d46400ad94a64d80846b0a16dd2ee8fea3436R84-R86

Yeah. It would be caught there if there is code in body response.

But why would 429 fall through to InvalidProgramStateError?
I thought we had a special error class for 429 errors?

In this case, InvalidProgramStateError will be through if request has http status is 429 and there isn't code.
We had a special error class for 429 errors too and processed in apiErrorFactory
Should we only focus on http status for error checking?

@moltar

Wouldn't 429 be caught here?
https://github.com/ScaleLeap/amazon-advertising-api-sdk/pull/679/files#diff-b3d62e5c74806d2b785aa734d35d46400ad94a64d80846b0a16dd2ee8fea3436R84-R86

Yeah. It would be caught there if there is code in body response.

But why would 429 fall through to InvalidProgramStateError?
I thought we had a special error class for 429 errors?

In this case, InvalidProgramStateError will be through if request has http status is 429 and there isn't code.
We had a special error class for 429 errors too and processed in apiErrorFactory
Should we only focus on http status for error checking?

Ok, so does that mean then that the API returns 429 without a body?

Ok, so does that mean then that the API returns 429 without a body?

Ok, so does that mean then that the API returns 429 without a body?

Not sure. I couldn't reproduce them in live API.
From the docs, they still mention about code in body.
But as my understand from our source code, it will only throw if there isn't code attribute in body?

Ok, so does that mean then that the API returns 429 without a body?

Not sure. I couldn't reproduce them in live API.
From the docs, they still mention about code in body.
But as my understand from our source code, it will only throw if there isn't code attribute in body?

it will only throw if there isn't code attribute in body?

That's right. And the 429 error should have code.

it will only throw if there isn't code attribute in body?

That's right. And the 429 error should have code.

That's right. And the 429 error should have code.

So we still check both http status and code in body?

That's right. And the 429 error should have code.

So we still check both http status and code in body?

That's right. And the 429 error should have code.

So we still check both http status and code in body?

That's right. And the 429 error should have code.

So we still check both http status and code in body?

I think the issue might be that the API is returning a string, instead of the object. So I added a bunch of defenses against that.

I think the issue might be that the API is returning a string, instead of the object. So I added a bunch of defenses against that.

@moltar: Should we rebase and merge this PR to fix "Converting circular structure" error before we receive response from ownagedj in #643 ?
We still keep issue open.

@moltar: Should we rebase and merge this PR to fix "Converting circular structure" error before we receive response from ownagedj in #643 ?
We still keep issue open.

Yeah, let's merge.

Yeah, let's merge.

I think I lost some coverage with my refactors. Please see the detailed report, it says which lines. Could you please fix that? Thanks.

I think I lost some coverage with my refactors. Please see the detailed report, it says which lines. Could you please fix that? Thanks.

I think I lost some coverage with my refactors. Please see the detailed report, it says which lines. Could you please fix that? Thanks.

I got it and will resolve in next PR. Thanks.

I think I lost some coverage with my refactors. Please see the detailed report, it says which lines. Could you please fix that? Thanks.

I got it and will resolve in next PR. Thanks.


diff: exit with correct status

#[path = "../diff_util/constants.rs"]
mod constants;

Using the constants file directly eliminates the unused code warnings.


LLM app fixes

Updated the apps that use local LLM models. Planning on showcasing them as examples for the EvaDB assignment if students don't want to spend on OpenAI API keys.

@Chitti-Ankith Can you also remove the youtube-channel app to a separate repo?

@Chitti-Ankith Can you also remove the youtube-channel app to a separate repo?

Moved the app to https://github.com/Chitti-Ankith/YouTube-Channel-QA

Is the answer in a good quality based on the context? The prompt seems to be a bit general and short.

Yes I tested it. In fact with the previous prompt, the LLM sometimes failed to output any answer.


JupyterLab 4 classifier is missing

https://github.com/jupyter-server/jupyter-scheduler/blob/14c44518f9d48eb40eb6c20e063c275c84358698/pyproject.toml#L15-L19

Good point, thank you


Preview Map broken

When changing sources, a preview image would be generated, but this seems to be broken for some time. What's up with that?
Either fix or remove.

Also regarding the website, when does the coverage map at https://batch.openaddresses.io/data update?


delete empty files in the integration tests folder

These empty files were necessary in Go 1.7, but are obsolete now.

Apparently this is not true. It's still needed in Go 1.8, but obsolete for 1.9.
So we need to keep those empty files around until dropping support for 1.8.

Yes. I tried that during my PR but it broke travis.

Codecov Report

Merging #804 into master will decrease coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #804      +/-   ##
==========================================
- Coverage   91.65%   91.61%   -0.05%
==========================================
  Files          82       81       -1
  Lines        5870     5861       -9
==========================================
- Hits         5380     5369      -11
- Misses        304      306       +2
  Partials      186      186

Impacted Files
Coverage Δ

server.go
90.82% <0%> (-0.72%)
:arrow_down:

client.go
90.59% <0%> (-0.22%)
:arrow_down:

handshake/crypto_setup_server.go
87.83% <0%> (-0.09%)
:arrow_down:

session.go
89.58% <0%> (-0.07%)
:arrow_down:

ackhandler/retransmittable.go
100% <0%> (ø)
:arrow_up:

internal/wire/stop_waiting_frame.go

internal/wire/ack_frame.go

internal/wire/ping_frame.go

internal/protocol/version.go

internal/wire/goaway_frame.go

... and 31 more

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 e7d1d22...7dd32b4. Read the comment docs.

@lucas-clemente: This can be merged now. Please approve.


Destructuring into an empty object vs an object with existing properties yields different results

🔎 Search Terms
"destructuring", "record"
🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ.

⏯ Playground Link
https://www.typescriptlang.org/play/?ts=5.6.3#code/MYewdgzgLgBATgU1HAJgdQJZQBYGUpwZgDmEAXDAEpIioA80hJANDI0cQHwwC8MA3gF8A3AChRCAB4AHWrFCRYiZOizYAcgFcAtgCMEcclRr12LGGB3643Pv1EwYUggEMACnBDSDUAJ4UABmYHGAA6cOVaVRx8JlJgkSA
💻 Code
This raises a type error:
const recordWithStrings: Record<string, string> = {};

export const recordWithNumbers: Record<string, number> = {
  ...recordWithStrings,
};

and this doesn't:
const recordWithStrings: Record<string, string> = {};

export const recordWithNumbers: Record<string, number> = {
  extraProperty: 0,
  ...recordWithStrings,
};

Is there a sound reason for that?
🙁 Actual behavior
The 2nd example doesn't raise a type error.
🙂 Expected behavior
The 2nd example should raise a type error.
Additional information about the issue
No response

Maybe related to #27144?

The reported code is almost an exact copy of what was reported in this comment https://github.com/microsoft/TypeScript/issues/27273#issuecomment-1114703301 and here https://github.com/microsoft/TypeScript/issues/56431 . The last experiment to fix this was worked on here https://github.com/microsoft/TypeScript/pull/56441


Configuring a Read-Only LDAP User Store doc issues

Description:
Existing documentation is an an outdated one where the sample properties are given assuming that an identity server with embedded LDAP is executed.
This need to be changed adhering to the updated documentation of IS, because embedded LDAP support is discontinued from IS 5.11 onwards

Update [2024-11-02]
Created PR for master branch : https://github.com/wso2/docs-apim/pull/8650


MixedRealityInputSimulationProfile serialization problem

Describe the bug
The DefaultMixedRealityInputSimulationProfile is part of the the simulation data provider in the MRKT input profile. But at the same time it's AMSDEF is Editor and UWP only, causing a deserialization problem on all other platforms.
Since it's the only service (I think) that's only being used in Editor and the fact that it also compiles for UWP makes me believe that either this could very well be just compiled for all platforms and we're done with it, or the profile needs to be extracted out, which I tried and stopped after the 3rd file.
To reproduce
Steps to reproduce the behavior:

Build MRKT with SimulationProfile for e.g. Standalone.

Expected behavior
no serialization problem
Your Setup (please complete the following information)

Unity Version 2018.4.6f1
MRTK Version mrtk_development

Target Platform (please complete the following information)

Standalone

Closing as duplicate of https://github.com/microsoft/MixedRealityToolkit-Unity/issues/3971, I believe


🐛reuse kubectl found in path

In my M1 env, I'd like to reuse the kubectl; otherwise you cannot download a darwin/arm64 kubectl binary:
w/o this PR, the following command won't work in M1:
KWOK_KUBE_VERSION=v1.20.15 kwokctl create cluster --runtime binary --kube-scheduler-binary<EMAIL_ADDRESS>--kube-controller-manager-binary<EMAIL_ADDRESS>--kube-apiserver-binary<EMAIL_ADDRESS>--kwok-controller-binary /usr/local/bin/kwok --etcd-binary /opt/homebrew/bin/etcd --name 120-binary

/kind bug

/retest

Ooops seems to have triggered another bug, I've fixed it, #44 merge first and then rebase this RP

Do we need to provide a way to disable kubectl in the path? Otherwise it will prompt

WARNING: version difference between client (1.24) and server (1.22) exceeds the supported minor version skew of +/-1

Do we need to provide a way to disable kubectl in the path? Otherwise it will prompt

It doesn't bother me as kubectl version skew is more robust than the skew among other core components.

/retest

/lgtm


Feat(web, web-react, web-twig): Attachment image object fit #DS-1005

Description

Added new prop objectFit to web-react and web-twig packages.
Same for web as data attribute: data-spirit-object-fit
Accepts cover (as default) and contain

Issue reference
FileUploader: Změna formátu náhledu

coverage: 69.436% (-27.0%) from 96.46% when pulling bef5068ac1d095b5de1d7461ec4f962c179b145e on feat/DS-1005-fileuploader-attach-obj-fit into 0cb30d586a846f513a18892072a41b994475d7c2 on main.


Verbose mode

Hello :)
Thanks for your amazing project, it's awesome :)
We tried to selfhost the project in a Kubernetes cluster, it works but we randomly have the error:
{ status: "error", code: 404, message: "The hostname of the origin is unresolvable (DNS) or blocked by policy." }
If we refresh the link url in a new target, after one or two refreshs it works
The docker don't log anything, I don't know what to do to debug it, how can I have verbose errors/logs ?
Have a great day,
Maxime

Sounds like the IPv6 interface is not properly configured, see #206 for more information. If using Docker, you can try to switch to host networking by passing --network host to the command line.
If that doesn't work, you could enable debugging in the nginx module by commenting this out.
https://github.com/weserv/images/blob/dffb6b496bb8c62e306ff5b5698d651265f711af/third_party/nginx/CMakeLists.txt#L8 (I can't recommend turning that on in production because these debug logs are quite verbose)
This also allows you to pass &debug=1, &debug=2, etc. within the URL.
https://github.com/weserv/images/blob/c071d29998461d5a1d5d249699c20f23c6dabe62/src/nginx/module.h#L126-L133

Thanks for the answer, it solved my issue 🥰


chore(deps): update all non-major

This PR contains the following updates:

Package
Type
Update
Change

@playwright/test (source)
devDependencies
minor
1.28.0 -> 1.37.0

axum
dependencies
patch
0.6.4 -> 0.6.20

cockroachdb/cockroach

patch
v23.1.4 -> v23.1.8

http
dependencies
patch
0.2.8 -> 0.2.9

tokio (source)
dependencies
minor
1.29 -> 1.31

tokio (source)
dependencies
minor
1.25 -> 1.31

Release Notes

Microsoft/playwright (@playwright/test)
v1.37.0
Compare Source
✨ New tool to merge reports
If you run tests on multiple shards, you can now merge all reports in a single HTML report (or any other report)
using the new merge-reports CLI tool.
Using merge-reports tool requires the following steps:

Adding a new "blob" reporter to the config when running on CI:
export default defineConfig({
  testDir: './tests',
  reporter: process.env.CI ? 'blob' : 'html',
});

The "blob" reporter will produce ".zip" files that contain all the information
about the test run.

Copying all "blob" reports in a single shared location and running npx playwright merge-reports:
npx playwright merge-reports --reporter html ./all-blob-reports

Read more in our documentation.
📚 Debian 12 Bookworm Support
Playwright now supports Debian 12 Bookworm on both x86_64 and arm64 for Chromium, Firefox and WebKit.
Let us know if you encounter any issues!
Linux support looks like this:

Ubuntu 20.04
Ubuntu 22.04
Debian 11
Debian 12

Chromium
✅
✅
✅
✅

WebKit
✅
✅
✅
✅

Firefox
✅
✅
✅
✅

🌈 UI Mode Updates

UI Mode now respects project dependencies. You can control which dependencies to respect by checking/unchecking them in a projects list.
Console logs from the test are now displayed in the Console tab.

Browser Versions

Chromium 116.0.5845.82
Mozilla Firefox 115.0
WebKit 17.0

This version was also tested against the following stable channels:

Google Chrome 115
Microsoft Edge 115

v1.36.2: 1.36.2
Compare Source
Highlights
https://github.com/microsoft/playwright/issues/24316 - [REGRESSION] Character classes are not working in globs in 1.36
Browser Versions

Chromium 115.0.5790.75
Mozilla Firefox 115.0
WebKit 17.0

This version was also tested against the following stable channels:

Google Chrome 114
Microsoft Edge 114

v1.36.1
Compare Source
Highlights
https://github.com/microsoft/playwright/issues/24184 - [REGRESSION]: Snapshot name contains some random string after test name when tests are run in container
Browser Versions

Chromium 115.0.5790.75
Mozilla Firefox 115.0
WebKit 17.0

This version was also tested against the following stable channels:

Google Chrome 114
Microsoft Edge 114

v1.36.0
Compare Source
Highlights
🏝 Summer maintenance release.
Browser Versions

Chromium 115.0.5790.75
Mozilla Firefox 115.0
WebKit 17.0

This version was also tested against the following stable channels:

Google Chrome 114
Microsoft Edge 114

v1.35.1
Compare Source
Highlights
https://github.com/microsoft/playwright/issues/23622 - [Docs] Provide a description how to correctly use expect.configure with poll parameterhttps://github.com/microsoft/playwright/issues/236666 - [BUG] Live Trace does not work with Codespacehttps://github.com/microsoft/playwright/issues/2369393 - [BUG] attachment steps are not hidden inside expect.toHaveScreenshot()
Browser Versions

Chromium 115.0.5790.13
Mozilla Firefox 113.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 114
Microsoft Edge 114

v1.35.0
Compare Source
Highlights

UI mode is now available in VSCode Playwright extension via a new "Show trace viewer" button:

UI mode and trace viewer mark network requests handled with page.route() and browserContext.route() handlers, as well as those issued via the API testing:

New option maskColor for methods page.screenshot(), locator.screenshot(), expect(page).toHaveScreenshot() and expect(locator).toHaveScreenshot() to change default masking color:
await page.goto('https://playwright.dev');
await expect(page).toHaveScreenshot({
  mask: [page.locator('img')],
  maskColor: '#00FF00', // green
});

New uninstall CLI command to uninstall browser binaries:
$ npx playwright uninstall # remove browsers installed by this installation
$ npx playwright uninstall --all # remove all ever-install Playwright browsers

Both UI mode and trace viewer now could be opened in a browser tab:
$ npx playwright test --ui-port 0 # open UI mode in a tab on a random port
$ npx playwright show-trace --port 0 # open trace viewer in tab on a random port

⚠ Breaking changes

playwright-core binary got renamed from playwright to playwright-core. So if you use playwright-core CLI, make sure to update the name:
$ npx playwright-core install # the new way to install browsers when using playwright-core

This change does not affect @playwright/test and playwright package users.

Browser Versions

Chromium 115.0.5790.13
Mozilla Firefox 113.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 114
Microsoft Edge 114

v1.34.3
Compare Source
Highlights
https://github.com/microsoft/playwright/issues/23228 - [BUG] Getting "Please install @playwright/test package..." after upgrading from 1.34.0 to 1.34.1
Browser Versions

Chromium 114.0.5735.26
Mozilla Firefox 113.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 113
Microsoft Edge 113

v1.34.2
Compare Source
Highlights
https://github.com/microsoft/playwright/issues/23225 - [BUG] VSCode Extension broken with Playwright 1.34.1
Browser Versions

Chromium 114.0.5735.26
Mozilla Firefox 113.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 113
Microsoft Edge 113

v1.34.1
Compare Source
Highlights
https://github.com/microsoft/playwright/issues/23186 - [BUG] Container image for v1.34.0 missing library for webkithttps://github.com/microsoft/playwright/issues/232066 - [BUG] Unable to install supported browsers for v1.34.0 from playwright-corhttps://github.com/microsoft/playwright/issues/2320707 - [BUG] importing ES Module JSX component is broken since 1.34
Browser Versions

Chromium 114.0.5735.26
Mozilla Firefox 113.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 113
Microsoft Edge 113

v1.34.0
Compare Source
Highlights

UI Mode now shows steps, fixtures and attachments:

New property testProject.teardown to specify a project that needs to run after this
and all dependent projects have finished. Teardown is useful to cleanup any resources acquired by this project.
A common pattern would be a setup dependency with a corresponding teardown:
// playwright.config.ts
import { defineConfig } from '@playwright/test';

export default defineConfig({
  projects: [
    {
      name: 'setup',
      testMatch: /global.setup\.ts/,
      teardown: 'teardown',
    },
    {
      name: 'teardown',
      testMatch: /global.teardown\.ts/,
    },
    {
      name: 'chromium',
      use: devices['Desktop Chrome'],
      dependencies: ['setup'],
    },
    {
      name: 'firefox',
      use: devices['Desktop Firefox'],
      dependencies: ['setup'],
    },
    {
      name: 'webkit',
      use: devices['Desktop Safari'],
      dependencies: ['setup'],
    },
  ],
});

New method expect.configure to create pre-configured expect instance with its own defaults such as timeout and soft.
const slowExpect = expect.configure({ timeout: 10000 });
await slowExpect(locator).toHaveText('Submit');

// Always do soft assertions.
const softExpect = expect.configure({ soft: true });

New options stderr and stdout  in testConfig.webServer to configure output handling:
// playwright.config.ts
import { defineConfig } from '@playwright/test';

export default defineConfig({
  // Run your local dev server before starting the tests
  webServer: {
    command: 'npm run start',
    url: 'http://<IP_ADDRESS>:3000',
    reuseExistingServer: !process.env.CI,
    stdout: 'pipe',
    stderr: 'pipe',
  },
});

New locator.and() to create a locator that matches both locators.
const button = page.getByRole('button').and(page.getByTitle('Subscribe'));

New events browserContext.on('console') and browserContext.on('dialog') to subscribe to any dialogs
and console messages from any page from the given browser context. Use the new methods consoleMessage.page()
and dialog.page() to pin-point event source.

⚠ Breaking changes

npx playwright test no longer works if you install both playwright and @playwright/test. There's no need
to install both, since you can always import browser automation APIs from @playwright/test directly:
// automation.ts
import { chromium, firefox, webkit } from '@playwright/test';
/* ... */

Node.js 14 is no longer supported since it reached its end-of-life on April 30, 2023.

Browser Versions

Chromium 114.0.5735.26
Mozilla Firefox 113.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 113
Microsoft Edge 113

v1.33.0
Compare Source
Locators Update

Use [locator.or()][locator.or()] to create a locator that matches either of the two locators.
Consider a scenario where   you'd like to click on a "New email" button, but sometimes a security settings dialog shows up instead.
In this case, you can wait for either a "New email" button, or a dialog and act accordingly:
const newEmail = page.getByRole('button', { name: 'New' });
const dialog = page.getByText('Confirm security settings');
await expect(newEmail.or(dialog)).toBeVisible();
if (await dialog.isVisible())
  await page.getByRole('button', { name: 'Dismiss' }).click();
await newEmail.click();

Use new options hasNot and hasNotText in [locator.filter()][locator.filter()]
to find elements that do not match certain conditions.
const rowLocator = page.locator('tr');
await rowLocator
    .filter({ hasNotText: 'text in column 1' })
    .filter({ hasNot: page.getByRole('button', { name: 'column 2 button' }) })
    .screenshot();

Use new web-first assertion [locatorAssertions.toBeAttached()][locatorAssertions.toBeAttached()] to ensure that the element
is present in the page's DOM. Do not confuse with the [locatorAssertions.toBeVisible()][locatorAssertions.toBeVisible()] that ensures that
element is both attached & visible.

New APIs

[locator.or()][locator.or()]
New option hasNot in [locator.filter()][locator.filter()]
New option hasNotText in [locator.filter()][locator.filter()]
[locatorAssertions.toBeAttached()][locatorAssertions.toBeAttached()]
New option timeout in [route.fetch()][route.fetch()]
[reporter.onExit()][reporter.onExit()]

⚠ Breaking change

The mcr.microsoft.com/playwright:v1.33.0 now serves a Playwright image based on Ubuntu Jammy.
To use the focal-based image, please use mcr.microsoft.com/playwright:v1.33.0-focal instead.

Browser Versions

Chromium 113.0.5672.53
Mozilla Firefox 112.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 112
Microsoft Edge 112

v1.32.3
Compare Source
Highlights
https://github.com/microsoft/playwright/issues/22144 - [BUG] WebServer only starting after timeouthttps://github.com/microsoft/playwright/pull/221911 - chore: allow reusing browser between the testshttps://github.com/microsoft/playwright/issues/222155 - [BUG] Tests failing in toPass often marked as passed
Browser Versions

Chromium 112.0.5615.29
Mozilla Firefox 111.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 111
Microsoft Edge 111

v1.32.2
Compare Source
Highlights
https://github.com/microsoft/playwright/issues/21993 - [BUG] Browser crash when using Playwright VSC extension and trace-viewer enabled in confighttps://github.com/microsoft/playwright/issues/220033 - [Feature] Make Vue component mount props less restrictivhttps://github.com/microsoft/playwright/issues/2208989 - [REGRESSION]: Tests failing with "Error: tracing.stopChunk"
Browser Versions

Chromium 112.0.5615.29
Mozilla Firefox 111.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 111
Microsoft Edge 111

v1.32.1
Compare Source
Highlights
https://github.com/microsoft/playwright/issues/21832 - [BUG] Trace is not opening on specific broken locatorhttps://github.com/microsoft/playwright/issues/218977 - [BUG] --ui fails to open with error reading mainFrame from an undefined this._pahttps://github.com/microsoft/playwright/issues/21918918 - [BUG]: UI mode, skipped tests not being fohttps://github.com/microsoft/playwright/issues/219411941 - [BUG] UI mode does not show webServer startup erhttps://github.com/microsoft/playwright/issues/2195321953 - [BUG] Parameterized tests are not displayed in the UI mode
Browser Versions

Chromium 112.0.5615.29
Mozilla Firefox 111.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 111
Microsoft Edge 111

v1.32.0
Compare Source
📣 Introducing UI Mode (preview)

Playwright v1.32 updates
New UI Mode lets you explore, run and debug tests. Comes with a built-in watch mode.

Engage with a new flag --ui:
npx playwright test --ui

New APIs

New options option: updateMode and option: updateContent in page.routeFromHAR() and browserContext.routeFromHAR().
Chaining existing locator objects, see locator docs for details.
New property TestInfo.testId.
New option name in method Tracing.startChunk().

⚠ Breaking change in component tests
Note: component tests only, does not affect end-to-end tests.

@playwright/experimental-ct-react now supports React 18 only.
If you're running component tests with React 16 or 17, please replace
@playwright/experimental-ct-react with @playwright/experimental-ct-react17.

Browser Versions

Chromium 112.0.5615.29
Mozilla Firefox 111.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 111
Microsoft Edge 111

v1.31.2
Compare Source
Highlights
https://github.com/microsoft/playwright/issues/20784 - [BUG] ECONNREFUSED on GitHub Actions with Node 18https://github.com/microsoft/playwright/issues/211455 - [REGRESSION]: firefox-1378 times out on await page.reload() when URL contains a #hashttps://github.com/microsoft/playwright/issues/2122626 - [BUG] Playwright seems to get stuck when using shard option and last test is skipphttps://github.com/microsoft/playwright/issues/21227227 - Using the webServer config with a Vite dev servehttps://github.com/microsoft/playwright/issues/21312312 - throw if defineConfig is not used for component testing
Browser Versions

Chromium 111.0.5563.19
Mozilla Firefox 109.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 110
Microsoft Edge 110

v1.31.1
Compare Source
Highlights
https://github.com/microsoft/playwright/issues/21093 - [Regression v1.31] Headless Windows shows cascading cmd windowshttps://github.com/microsoft/playwright/pull/211066 - fix(loader): experimentalLoader with node@18
Browser Versions

Chromium 111.0.5563.19
Mozilla Firefox 109.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 110
Microsoft Edge 110

v1.31.0
Compare Source
New APIs

New property TestProject.dependencies to configure dependencies between projects.
Using dependencies allows global setup to produce traces and other artifacts,
see the setup steps in the test report and more.
// playwright.config.ts
import { defineConfig } from '@playwright/test';

export default defineConfig({
  projects: [
    {
      name: 'setup',
      testMatch: /global.setup\.ts/,
    },
    {
      name: 'chromium',
      use: devices['Desktop Chrome'],
      dependencies: ['setup'],
    },
    {
      name: 'firefox',
      use: devices['Desktop Firefox'],
      dependencies: ['setup'],
    },
    {
      name: 'webkit',
      use: devices['Desktop Safari'],
      dependencies: ['setup'],
    },
  ],
});

New assertion expect(locator).toBeInViewport() ensures that locator points to an element that intersects viewport, according to the intersection observer API.
const button = page.getByRole('button');

// Make sure at least some part of element intersects viewport.
await expect(button).toBeInViewport();

// Make sure element is fully outside of viewport.
await expect(button).not.toBeInViewport();

// Make sure that at least half of the element intersects viewport.
await expect(button).toBeInViewport({ ratio: 0.5 });

Miscellaneous

DOM snapshots in trace viewer can be now opened in a separate window.
New method defineConfig to be used in playwright.config.
New option maxRedirects for method Route.fetch.
Playwright now supports Debian 11 arm64.
Official docker images now include Node 18 instead of Node 16.

⚠ Breaking change in component tests
Note: component tests only, does not affect end-to-end tests.
playwright-ct.config configuration file for component testing now requires calling defineConfig.
// Before

import { type PlaywrightTestConfig, devices } from '@playwright/experimental-ct-react';
const config: PlaywrightTestConfig = {
  // ... config goes here ...
};
export default config;

Replace config variable definition with defineConfig call:
// After

import { defineConfig, devices } from '@playwright/experimental-ct-react';
export default defineConfig({
  // ... config goes here ...
});

Browser Versions

Chromium 111.0.5563.19
Mozilla Firefox 109.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 110
Microsoft Edge 110

v1.30.0
Compare Source
🎉 Happy New Year 🎉
Maintenance release with bugfixes and new browsers only. We are baking some nice features for v1.31.
Browser Versions

Chromium 110.0.5481.38
Mozilla Firefox 108.0.2
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 109
Microsoft Edge 109

v1.29.2
Compare Source
Highlights
https://github.com/microsoft/playwright/issues/19661 - [BUG] 1.29.1 browserserver + page.goto = net::ERR_SOCKS_CONNECTION_FAILED
Browser Versions

Chromium 109.0.5414.46
Mozilla Firefox 107.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 108
Microsoft Edge 108

v1.29.1
Compare Source
Highlights
https://github.com/microsoft/playwright/issues/18928 - [BUG] Electron firstWindow times out after upgrading to 1.28.0https://github.com/microsoft/playwright/issues/192466 - [BUG] Electron firstWindow times out after upgrading to 1.28.https://github.com/microsoft/playwright/issues/1941212 - [REGRESSION]: 1.28 does not work with electron-serve anymorhttps://github.com/microsoft/playwright/issues/19540540 - [BUG] electron.app.getAppPath() returns the path one level higher if you run electron pointing to the directhttps://github.com/microsoft/playwright/issues/195489548 - [REGRESSION]: Ubuntu 18 LTS not supported anymore
Browser Versions

Chromium 109.0.5414.46
Mozilla Firefox 107.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 108
Microsoft Edge 108

v1.29.0
Compare Source
New APIs

New method route.fetch() and new option json for route.fulfill():
await page.route('**/api/settings', async route => {
  // Fetch original settings.
  const response = await route.fetch();

  // Force settings theme to a predefined value.
  const json = await response.json();
  json.theme = 'Solorized';

  // Fulfill with modified data.
  await route.fulfill({ json });
});

New method locator.all() to iterate over all matching elements:
// Check all checkboxes!
const checkboxes = page.getByRole('checkbox');
for (const checkbox of await checkboxes.all())
  await checkbox.check();

Locator.selectOption matches now by value or label:
<select multiple>
  <option value="red">Red

  <option value="green">Green

  <option value="blue">Blue

</select>

await element.selectOption('Red');

Retry blocks of code until all assertions pass:
await expect(async () => {
  const response = await page.request.get('https://api.example.com');
  await expect(response).toBeOK();
}).toPass();

Read more in our documentation.

Automatically capture full page screenshot on test failure:
// playwright.config.ts
import type { PlaywrightTestConfig } from '@playwright/test';

const config: PlaywrightTestConfig = {
  use: {
    screenshot: {
      mode: 'only-on-failure',
      fullPage: true,
    }
  }
};

export default config;

Miscellaneous

Playwright Test now respects jsconfig.json.
New options args and proxy for androidDevice.launchBrowser().
Option postData in method route.continue() now supports serializable values.
Ubuntu 18.04 is not supported anymore

Browser Versions

Chromium 109.0.5414.46
Mozilla Firefox 107.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 108
Microsoft Edge 108

v1.28.1
Compare Source
Highlights
This patch release includes the following bug fixes:
https://github.com/microsoft/playwright/issues/18928 - [BUG] Electron firstWindow times out after upgrading to 1.28.0https://github.com/microsoft/playwright/issues/189200 - [BUG] [expanded=false] in role selector returns elements without aria-expanded attribuhttps://github.com/microsoft/playwright/issues/18865865 - [BUG] regression in killing web server process in 1.28.0
Browser Versions

Chromium 108.0.5359.29
Mozilla Firefox 106.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 107
Microsoft Edge 107

tokio-rs/axum (axum)
v0.6.20: axum - v0.6.20
Compare Source

added: WebSocketUpgrade::write_buffer_size and WebSocketUpgrade::max_write_buffer_size
changed: Deprecate WebSocketUpgrade::max_send_queue
change: Update tokio-tungstenite to 0.20
added: Implement Handler for T: IntoResponse (#2140)

v0.6.19: axum - v0.6.19
Compare Source

added: Add axum::extract::Query::try_from_uri (#2058)
added: Implement IntoResponse for Box<str> and Box<[u8]> (#2035)
fixed: Fix bugs around merging routers with nested fallbacks (#2096)
fixed: Fix .source() of composite rejections (#2030)
fixed: Allow unreachable code in #[debug_handler] (#2014)
change: Update tokio-tungstenite to 0.19 (#2021)
change: axum's MSRV is now 1.63 (#2021)

v0.6.18: axum - v0.6.18
Compare Source

fixed: Don't remove the Sec-WebSocket-Key header in WebSocketUpgrade (#1972)

v0.6.17: axum - v0.6.17
Compare Source

fixed: Fix fallbacks causing a panic on CONNECT requests (#1958)

v0.6.16: axum - v0.6.16
Compare Source

fixed: Don't allow extracting MatchedPath in fallbacks (#1934)
fixed: Fix panic if Router with something nested at / was used as a fallback (#1934)
added: Document that Router::new().fallback(...) isn't optimal (#1940)

v0.6.15: axum - v0.6.15
Compare Source

fixed: Removed additional leftover debug messages (#1927)

v0.6.14: axum - v0.6.14
Compare Source

fixed: Removed leftover "path_router hit" debug message (#1925)

v0.6.13: axum - v0.6.13
Compare Source

added: Log rejections from built-in extractors with the
axum::rejection=trace target (#1890)
fixed: Fixed performance regression with Router::nest introduced in
0.6.0. nest now flattens the routes which performs better (#1711)
fixed: Extracting MatchedPath in nested handlers now gives the full
matched path, including the nested path (#1711)
added: Implement Deref and DerefMut for built-in extractors (#1922)

v0.6.12: axum - v0.6.12
Compare Source

added: Implement IntoResponse for MultipartError (#1861)
fixed: More clearly document what wildcards matches (#1873)

v0.6.11: axum - v0.6.11
Compare Source

fixed: Don't require S: Debug for impl Debug for Router<S> (#1836)
fixed: Clone state a bit less when handling requests (#1837)
fixed: Unpin itoa dependency (#1815)

v0.6.10: axum - v0.6.10
Compare Source

fixed: Add #[must_use] attributes to types that do nothing unless used (#1809)
fixed: Gracefully handle missing headers in the TypedHeader extractor (#1810)
fixed: Fix routing issues when loading a Router via a dynamic library (#1806)

v0.6.9: axum - v0.6.9
Compare Source

changed: Update to tower-http 0.4. axum is still compatible with tower-http 0.3 (#1783)

v0.6.8: axum - v0.6.8
Compare Source

fixed: Fix Allow missing from routers with middleware (#1773)
added: Add KeepAlive::event for customizing the event sent for SSE keep alive (#1729)

v0.6.7: axum - v0.6.7
Compare Source

added: Add FormRejection::FailedToDeserializeFormBody which is returned
if the request body couldn't be deserialized into the target type, as opposed
to FailedToDeserializeForm which is only for query parameters (#1683)
added: Add MockConnectInfo for setting ConnectInfo during tests (#1767)

v0.6.6: axum - v0.6.6
Compare Source

fixed: Enable passing MethodRouter to Router::fallback (#1730)

v0.6.5: axum - v0.6.5
Compare Source

fixed: Fix #[debug_handler] sometimes giving wrong borrow related suggestions (#1710)
Document gotchas related to using impl IntoResponse as the return type from handler functions (#1736)

hyperium/http (http)
v0.2.9
Compare Source

Add HeaderName constants for cache-status and cdn-cache-control.
Implement Hash for PathAndQuery.
Re-export HeaderName at crate root.

tokio-rs/tokio (tokio)
v1.31.0: Tokio v1.31.0
Compare Source
Fixed

io: delegate WriteHalf::poll_write_vectored (#5914)

Unstable

rt(unstable): fix memory leak in unstable next-gen scheduler prototype (#5911)
rt: expose mean task poll time metric (#5927)

v1.30.0: Tokio v1.30.0
Compare Source
1.30.0 (August 9, 2023)
This release bumps the MSRV of Tokio to 1.63. (#5887)
Changed

tokio: reduce LLVM code generation (#5859)
io: support --cfg mio_unsupported_force_poll_poll flag (#5881)
sync: make const_new methods always available (#5885)
sync: avoid false sharing in mpsc channel (#5829)
rt: pop at least one task from inject queue (#5908)

Added

sync: add broadcast::Sender::new (#5824)
net: implement UCred for espidf (#5868)
fs: add File::options() (#5869)
time: implement extra reset variants for Interval (#5878)
process: add {ChildStd*}::into_owned_{fd, handle} (#5899)

Removed

tokio: removed unused tokio_* cfgs (#5890)
remove build script to speed up compilation (#5887)

Documented

sync: mention lagging in docs for broadcast::send (#5820)
runtime: expand on sharing runtime docs (#5858)
io: use vec in example for AsyncReadExt::read_exact (#5863)
time: mark Sleep as !Unpin in docs (#5916)
process: fix raw_arg not showing up in docs (#5865)

Unstable

rt: add runtime ID (#5864)
rt: initial implementation of new threaded runtime (#5823)

v1.29.1: Tokio v1.29.1
Compare Source
Fixed

rt: fix nesting two block_in_place with a block_on between (#5837)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 0.2.4 :tada:
The release is available on:

GitHub release
v0.2.4

Your semantic-release bot :package::rocket:


Support passing custom webpack config directly to generateWebpackConfig

Notice: A feature request describes a suggested improvement. If you have a debugging or troubleshooting question, please open a discussion on the Discussions Tab. Otherwise, remove this line and fill out the following sections.
Desired behavior:
'use strict';

const { generateWebpackConfig } = require('shakapacker');
const Dotenv = require('dotenv-webpack');

const customConfig = {
  plugins: [new Dotenv()],
  module: {
    rules: [
      // ...
    ]
  }
};

// See the shakacode/shakapacker README and docs directory for advice on customizing your webpackConfig.

module.exports = generateWebpackConfig(customConfig);

Actual behavior:
'use strict';

const { generateWebpackConfig, merge } = require('shakapacker');
const Dotenv = require('dotenv-webpack');

const customConfig = {
  plugins: [new Dotenv()],
  module: {
    rules: [
      // ...
    ]
  }
};

// See the shakacode/shakapacker README and docs directory for advice on customizing your webpackConfig.

module.exports = merge(generateWebpackConfig(), customConfig);

It feels like a pretty simple win given that generateWebpackConfig is just doing webpackMerge.merge anyway, and this feels like it's in the name too right?
If someone needs to do more advance stuff, they can still use merge directly themselves.
Setup environment:

Ruby version: 3.1.0
Rails version: 7.0.0
Shakapacker version: 7.0.2

@justin808 You also wanted such a function to get a config object as an optional parameter. Is this proposal the same as what you had in mind?

@G-Rath this is a great idea so long as the argument is optional and the current functionality is preserved. Or you can say that the default param is an empty object. Please submit and PR and I'll approve,.


Less strict dependencies

All Trusted-AI libraries should have roughly the same version requirements.
As it is, they are incompatible with each other and you can't run them in the same environment if you have a strict dependency checker.
For that matter, a library should not lock to a specific version number, but should offer a range that still works.
https://github.com/Trusted-AI/adversarial-robustness-toolbox/blob/925b6957870f8b689e24cac482f8b1c2afcc69d3/setup.py#L11-L13
The latest version of scikit-learn (0.23.2) is not even supported as a WML deployment.
i.e.

 "scipy>=1.4.1",
 "scikit-learn>=0.20.3",

Hi @illeatmyhat,
Thank you very much for the suggestion, which makes sense. We'll investigate how much we can relax the constraints for the upcoming release of ART 1.4. For most dependencies we don't have any strict requirements, but there are reasons for restrictions on scipy and scikit-learn.
ART is now a project of the Linux Foundation for AI and has therefore to be compatible with multiple deployment environments.


rm unneccessary import

_ "istio.io/istio/galley/pkg/metadata" not needed by pilot.

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

Needs approval from an approver in each of these files:

pilot/OWNERS

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
b429abc5cef2ab189a7c06d47edb4979f79b604f
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.

/approve

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

Needs approval from an approver in each of these files:

pilot/OWNERS [hzxuzhonghu]

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

/test istio-unit-tests

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

Test name
Commit
Details
Rerun command

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

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

/test e2e-bookInfoTests-envoyv2-v1alpha3


[Service Bus] Add isServiceBusMessage checks to all methods that take messages

This PR ensures we have input validation in all apis that take messages as input.
Resolves #9487

/azp run js - servicebus - tests

/azp run js - servicebus - tests


FCC (regular and Beta) marked as unsafe at public library

Issue Description

I am at the public library and, when I tried to access FCC, regular and beta, I got the same warning (see screenshot).
Browser Information

Browser Name, Version: Chrome Version 63.0.3239.132 (Official Build) (32-bit)
Operating System: Windows 7 Pro
Mobile, Desktop, or Tablet: desktop

Screenshot

We use CloudFlare as a CDN in front of our servers. As for the certs, I think they are provided by LetsEncrypt.
@BerkeleyTrue do you think this is due something at our end? I can not think of anything that would be causing this.

Looks like our certificate should be good: https://www.ssllabs.com/ssltest/analyze.html?d=freecodecamp.org

It also says it should run fine on your version of Chrome (as it does for me).
@ReveurGAM Can you check if https://www.opensourceforgood.org/ gives you the same error? It should be running on the same certificate, so if it works fine, this may be a cache issue.

I don't think this is on our end. We use industry standard certs provided by cloudflare.

@systimotic Hi, when I get back to the West Allis Library (Wisconsin), I will try to check.  I don't have this problem anywhere else, which is what makes it odd, but I thought I should report it because I don't want library users to be discouraged from using FCC.

@ReveurGAM Please try running in incognito mode. I'm 100% sure it'll work ;).

Next time I'm there, but I wouldn't be surprised if they disabled private browsing, given how locked down the computers are...

@ReveurGAM Ya. So, try clearing all the browsing data (Including cache) and visit the site again.

Ok, guys, I've made a special trip to the library. :)
First, please note this happens on the children's section's computers.  This does NOT occur on the adult computers so, if you're not interested in having kids study on FCC, you might as well close this.  It's probably the filtering from ContentProtect (www.contentwatch.com) and/or SAM (security account manager), so I guess you'd have to contact the respective owners to see if you can be exempted from blocking.
ContentProtect:

You can see the SAM icon in the bottom right corner.

@systimotic Same result on that website.

@vkWeb I tried Incognito.  Since I was already logged in to BFCC, I didn't get the warning.  However, the website still behaves incorrectly, which seems to support my belief that the filters are causing this.
I cleared the browser (which was almost empty) and refreshed my screen, which netted me the warning again, and the website still doesn't behave correctly.  Also, right-click is sometimes disabled. When I opened the dev tools, I got this on that error:

Here's the dev tools, inspecting the empty editor, map opened:

And focused on the preview:

Inspecting the dysfunctional editor, map closed:

And, the preview pane, map closed:

I hope this helps.  It's time to get home to my kids. :)

BTW, after logging out of BFCC, I used Incognito to see if I'd get the error; I didn't.

This is due to the protection software, being used at library. Unfortunately that is beyond the scope of this project.
Will have to close.


Blinking and focus reset with react-table and withPortal for DateRangePicker

react-dates version
<EMAIL_ADDRESS>Describe the bug
Using react-table and withPortal causes blinking and a focus reset when setting the startDate for DateRangePicker.
Source code (including props configuration)
I am having trouble using react-dates as a filter inside react-table and I don't think all the issues are due to react-table. In my local code, I can't even open the calendar without using withPortal but I am unable to reproduce that problem in a codesandbox. If anybody has an idea there, let me know.
In this code sandbox (inside react-table, with withPortal), you can see that trying to set the startDate does not advance the focus to endDate. If you log the changes, you can see that it does switch to endDate but immediately resets back to startDate.
In this code sandbox, I have gotten ride of the react-table and everything works just fine.
I thought, OK, it must only be down to react-table but if you remove withPortal from the first sandbox, the focus change works correctly.
Desktop (please complete the following information):

OS: Windows 10
Browser: Chrome
Version 79.0.3945.130

Additional context
I'm sorry if this is purely because of react-table but since I can eliminate the issue even with react-table (although, only in the code sandbox and not in my own code) by removing withPortal, I still think there might be a bug somewhere with withPortal.
I don't think this is related to #1523 or #1709, because of the focus problem, which is not seen in those bugs.
Also, does anybody know why the minDate is today, even though I have specified a minDate...

Another thing I discovered, in case anybody is interested, is that if you use appendToBody instead of withPortal, DateRangePicker will still work but you will be able to type into the input fields. 👍


NanoHTTPD session.parseBody(files); timeout

Hello
i want to send a file from a smartphone "A" with ion to a smartphone "B" with nanoHttpd
in the smartphone B i try to get the byte of the JPEG image and write it to a file
If i use this function :  session.parseBody(files);
I have a timeout error => Read timed out
another solution is to get the byte like this but the image isn't readable
Integer contentLength = Integer.parseInt(session.getHeaders().get( "content-length" ));
byte[] buf = new byte[contentLength];
Log.d(TAG,"RequestBody: " + new String(buf));
this is my code to send the file from the smartphone A :
Ion.with(mContext)
.load(...)
.setMultipartParameter("id_file", id_file)
.setMultipartFile("image", "image/jpeg", file_data)

ok i changed the the timeout in the start server function
server.start(10000000);
but now i have this error ;
BAD REQUEST: Content type is multipart/form-data but contains less than two boundary strings


use size as pixel for width/height instead a multiplicator

size should be used for determining the size of the produced SVG instead of being a multiplier
as i understand the documentation it should work like my implementation:

size (png and svg only) — size of one module in pixels. Default 5 for png and undefined for svg.

Any updates on this ?

i fixed it within my commit. so feel free to use my fork


Add logging to phoenix module

Current coverage is 86.06% (diff: 88.57%)

Merging #38 into master will decrease coverage by 0.55%

@@             master        #38   diff @@
==========================================
  Files            13          9     -4
  Lines           157        122    -35
  Methods         150        113    -37
  Messages          0          0
  Branches          4          6     +2
==========================================
- Hits            136        105    -31
+ Misses           21         17     -4
  Partials          0          0

Powered by Codecov. Last update 83491fb...25c9737


What is the general purpose of a loop?

What is the general purpose of a loop?
A. Loops read and recreate code automatically.
B. Loops automatically iterate a block of code based on conditions.
C. All loops help the computer make decisions automatically.
D. Loops iterate through arrays to find elements.

I chose B. Loops automatically iterate a block of code based on conditions.


No position function outwards facing

Could we add an outwards facing position function to blot? Currently there is nothing that does this to my knowledge, and the position is already stored in the class. This should only take a few lines of code.
I believe the function below could be added to virtual-gallery/drawing-functions/Turtle.js to implement this functionality.
pos() {
    return this.location
  }

I believe it should be added to astro/src/lib/drawingToolkit
/turtle.ts, not the virtual gallery one

This is a great idea though! I was hoping to have it a couple of times while working on my art.

also i think t.end sort of does this?

@BrightTheBackpack that's a little confusing. Should this be an alias of that function or does it do something else?

If it a method returned this.location from the turtles internals that should be better, because it would work if the turtle had not path. (I believe t.end only works when a path has been made)


FIX-#4907: Implement radd for Series and DataFrame

Signed-off-by: Karthik Velayutham<EMAIL_ADDRESS>
What do these changes do?
This PR implements a proper implementation for radd which is needed for string concatenation on DataFrames and Series objects.

[x] commit message follows format outlined here
[x] passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] signed commit with git commit -s
[x] Resolves #4907
[x] tests added and passing
[x] module layout described at docs/development/architecture.rst is up-to-date
[x] added (Issue Number: PR title (PR Number)) and github username to release notes for next major release

can we add tests that do the following:

@RehanSD I agree adding column to string is good to test (though we should double check whether we are testing this already).
I don't think we should test for the second case. That is basically testing order of operations in Python, on top of the string + dataframe and dataframe + string test cases. We should trust that Python uses __radd__ and __add__ appropriately.

can we add tests that do the following:

@RehanSD I agree adding column to string is good to test (though we should double check whether we are testing this already).
I don't think we should test for the second case. That is basically testing order of operations in Python, on top of the string + dataframe and dataframe + string test cases. We should trust that Python uses __radd__ and __add__ appropriately.

Sgtm - let's just add the first test then!

@RehanSD yes, that sounds like a good idea. I had tested this before on my own for sanity but didn't add it because I felt like this was a case that would be covered normally.


Widgets app refactor

This is to reland what was reverted in https://github.com/flutter/flutter/pull/22249
Previous version of this caused a runtime failure in AOT mode.  Filed https://github.com/dart-lang/sdk/issues/34572 to track that.
I'm not entirely sure why this change works when the other didn't, but it works in AOT mode now.

LGTM


s.login() suddenly doesn't work due to base64 problem?

All of a sudden, my script utilizing Snapy is outputting the following error.

Traceback (most recent call last):
File "<stdin>", line 1, in
File "build/bdist.macosx-10.11-intel/egg/snapy/init.py", line 175, in login
File "build/bdist.macosx-10.11-intel/egg/snapy/API.py", line 37, in getSnapchatAttestation
File "/usr/local/Cellar/python/2.7.10_2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/base64.py", line 76, in b64decode
raise TypeError(msg)
TypeError: Incorrect padding

Could something have changed with the APIs utilized by Casper or Snapy?

The Casper API is currently down and being worked on. Look up the page
"Casper App" on Facebook for more news and updates.


Fetch updated translations

As per https://groups.google.com/forum/#!topic/wagtail/i7rsyHO3qmU

Done in #1045


Gstreamer VAAPI Patch Support for Gstreamer 1.18

Hi,
Will there be any patches for gstreamer-vaapi on gstreamer 1.18+ in order to support VAAPI preprocessor backend?
FYI, we are upgrading to gstreamer 1.18.2 due to the availability of vaapioverlay.
Thanks,
Vincent

Hi @vt911001,
Just clarify, are you asking DL Streamer update for GST 1.18+ or just GST VAAPI?
If you just ask gst vaapi, you should go to following project:
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi
DL Streamer support 1.16.2, so if you are asking about updating DL Streamer, I can help.
Mark

Hi Mark,
I was referring to the install guide for dlstreamer in order to enable VAAPI preprocessor backend.
To enable VA-API preprocessing of inference elements gstreamer-vaapi-patch must be installed.
https://github.com/openvinotoolkit/dlstreamer_gst/blob/master/patches/gstreamer-vaapi/README.md
The patch is only working on 1.16.2 and I would like to ask if there is similar patch available for 1.18.2?
This is because I would like to leverage the vaapi-surface-sharing preprocessor backend.
Thanks,
Vincent

Hi, Vincent!
It seems to me that this patch should work on 1.18.2 because we are using it on gstreamer 1.18.4. Try to apply it. If it does not work, come back and we`ll try to help you.
Thanks,
Denis

Hi @vt911001,
Does our replay solved your problem?
If yes, I will close this issue.
Mark

Hi Mark and Denis,
I have tried to apply the patch onto Gstreamer 1.18.2 and I got the following outputs:
Patch:
https://raw.githubusercontent.com/opencv/gst-video-analytics/master/patches/gstreamer-vaapi/video-format-mapping.patch
Outputs:
patch -p1  < ../video-format-mapping.patch
patching file gst-libs/gst/vaapi/gstvaapidisplay.c
Reversed (or previously applied) patch detected!  Assume -R? [n] n
Apply anyway? [n] y
Hunk #1 succeeded at 709 with fuzz 2 (offset 34 lines).
Hunk #2 FAILED at 911.
1 out of 2 hunks FAILED -- saving rejects to file gst-libs/gst/vaapi/gstvaapidisplay.c.rej
patching file gst-libs/gst/vaapi/video-format.c
Hunk #1 FAILED at 33.
Hunk #2 succeeded at 185 with fuzz 2 (offset 90 lines).
Hunk #3 FAILED at 112.
Hunk #4 FAILED at 124.
Hunk #5 FAILED at 165.
Hunk #6 FAILED at 181.
Hunk #7 FAILED at 198.
Hunk #8 FAILED at 223.
Hunk #9 FAILED at 245.
Hunk #10 FAILED at 263.
Hunk #11 FAILED at 280.
Hunk #12 succeeded at 679 with fuzz 2 (offset 340 lines).
10 out of 12 hunks FAILED -- saving rejects to file gst-libs/gst/vaapi/video-format.c.rej
patching file gst-libs/gst/vaapi/video-format.h
Hunk #1 succeeded at 76 with fuzz 2 (offset 17 lines).

Thus, I am not sure whether it is compatible or not?
FYI, the other patch of https://raw.githubusercontent.com/opencv/gst-video-analytics/master/patches/gstreamer-vaapi/vasurface_qdata.patch works fine.
Thanks,
Vincent

@mliu2020 @denissmolyakov
Good day, can I know is there any update on this.
Is the file well patched to move on?
Thanks,
Vincent

Hi @vt911001,
Sorry for the late response.
Yes, I have confirmed the one patch you have applied successful should get you going. You should be able to move on with only one patch.
Let me know if you have any issues with one patch.
Mark

Hi @mliu2020 ,
Thanks for your reply, I will get back to you once I try it out.
Thanks,
Vincent

@vt911001 ,
Do you have any results on this? Let me know if you need help on this, I can help you to confirm.
Mark

@mliu2020 ,
Sorry for the late reply, It is working.
Thanks,
Vincent

Great! Thanks so much.
Mark


IBDesignable error

I got this error failed to render and update auto layout no suitable image found after installing via cocoa pods

This is a bug in CocoaPods it seems, it can be fixed with the workarounds mentioned in this issue or by downgrading to a previous CocoaPods version.


Update Composer dependencies (2019-11-21-00-09)

Visual regression test passed!
View the visual regression test report


Implement Disco queries against other entities

In order to learn what the server or a different user supports, I had to expand the support of XEP-0030 a bit.
EDIT: It seems that this PR breaks the PubSub functionality. I am working on a fix.

Could you please resolve conflicts?

Could you please resolve conflicts?

@mattn: Have you progressed on it?

Thanks


Adding the directed interval

Aside from the implementation/code structure issues, is there a fundamental reason to have a separate DIM type? I understand that there are lots of good engineering reasons to keep the undirected and directed ones apart, but I wonder whether theoretically the undirected ones can be viewed as a particular mode of use.

Closing this PR for now --- but maybe we can revisit this sometime, now that we have a more powerful directed cofibration solver.


Fix broken link

Broken when included from e.g., https://btcguide.github.io/known-issues/hardware/trezor

Thanks @real-or-random! Unfortunately, this link is also broken as it has a trailing slash. I'm happy to make that change, but didn't want to steal your git commit cred if you'd like to edit this PR?

oops, should be fixed.

Thanks @real-or-random!


Some static assets (vendor js and css) returning 504 on RKE HA external LB initial set up and UI not rendering

Rancher versions:
rancher/server or rancher/rancher: v2.03
Infrastructure Stack versions:
kubernetes (if applicable):
ubuntu@rancher2-01:~$ ./rke_linux-amd64 --version
rke version v0.1.8-rc5

Docker version: (docker version,docker info preferred)
ubuntu@rancher2-01:~$ docker info
Containers: 33
 Running: 18
 Paused: 0
 Stopped: 15
Images: 13
Server Version: 17.03.2-ce
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 4ab9917febca54791c5f071a9d1f404867857fcc
runc version: 54296cf40ad8143b62dbcaa1d90e520a2136ddfe
init version: 949e6fa
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.4.0-1057-aws
Operating System: Ubuntu 16.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 15.22 GiB
Name: rancher2-01.zymergen.net
ID: GA6J:4RCU:AEQK:YGWJ:TIQQ:PB7P:P6IO:BQJZ:Y4NO:HDVI:6I2L:3WII
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false

WARNING: No swap limit support

Operating system and kernel: (cat /etc/os-release, uname -r preferred)
ubuntu@rancher2-01:~$ uname -r
4.4.0-1057-aws

Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
aws, m5xlarge
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
HA Rancher external Load Balancer ALB with certs signed by recognized CA
Following docs at https://rancher.com/docs/rancher/v2.x/en/installation/ha-server-install-external-lb/
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Steps to Reproduce:
Followed the steps to set up the HA external LB. Only deviations are that I used a cname for the DNS to point at the ALB DNS instead of an A record, and we're using an internal LB only accessible in our vpc/vpn.
From everything I can see RKE came up fine and I can use kubectl and the generated kube_config_rancher-cluster.yml to get resources in the nginx-ingress and cattle-system namespaces.
ubuntu@rancher2-01:~$ kubectl --kubeconfig kube_config_rancher-cluster.yml get services -n cattle-system
NAME             TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)   AGE
cattle-service   ClusterIP   <IP_ADDRESS>   <none>        80/TCP    26m

ubuntu@rancher2-01:~$ kubectl --kubeconfig kube_config_rancher-cluster.yml get deployments -n cattle-system
NAME      DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
cattle    1         1         1            1           27m

ubuntu@rancher2-01:~$ kubectl --kubeconfig kube_config_rancher-cluster.yml get pods -n cattle-system
NAME                      READY     STATUS    RESTARTS   AGE
cattle-6879b88dfb-h6vbr   1/1       Running   0          27m

ubuntu@rancher2-01:~$ kubectl --kubeconfig kube_config_rancher-cluster.yml get ingress -n cattle-system
NAME                  HOSTS                   ADDRESS            PORTS     AGE
cattle-ingress-http   rancher2.zymergen.net   rancher2-01.z...   80        26m

Attaching the log from kubectl --kubeconfig kube_config_rancher-cluster.yml logs -l app=cattle -n cattle-system
cattle.log
Results:
Initial Rancher UI does not render in browser
/assets/vendor.css, /assets/vendor-ed805d466babe1ea344647cc847cc81b.js, and /assets/images/logos/favicon.ico all are timing out with a 504 when I first try and go to the Rancher UI. The main index.html and /assets/ui-11743155b847aedd04ac46dd41fa36c3.js appear to load fine.

I extracted the service, ingress, and deployment yaml, so that I could apply with changed configs and played with some of the nginx annotations. Tried some of the following settings:
metadata:
  namespace: cattle-system
  name: cattle-ingress-http
  annotations:
    nginx.ingress.kubernetes.io/proxy-connect-timeout: "60"
    kubernetes.io/ingress.class: nginx
    nginx.ingress.kubernetes.io/proxy-body-size: 500m
    ingress.kubernetes.io/proxy-body-size: 500m
    nginx.ingress.kubernetes.io/proxy-read-timeout: "1800"   # Max time in seconds for ws to remain shell window open
    nginx.ingress.kubernetes.io/proxy-send-timeout: "1800"   # Max time in seconds for ws to remain shell window open
    nginx.ingress.kubernetes.io/ssl-redirect: "false"        # Disable redirect to ssl

I shelled into the rancher container to check that the vendor assets are there and everything seems to be there:
root@cattle-6879b88dfb-h6vbr:/usr/share/rancher/ui/assets# ls -la
total 21848
drwxr-xr-x 5  501 staff     4096 Jun 23 03:54 .
drwxr-xr-x 6 root root      4096 Jun 23 03:54 ..
drwxr-xr-x 2  501 staff     4096 Jun 23 03:54 fonts
drwxr-xr-x 5  501 staff     4096 Jun 23 03:54 images
drwxr-xr-x 3  501 staff     4096 Jun 23 03:54 intl
-rw-r--r-- 1  501 staff      735 Jun 21 23:44 node-asset-manifest.js
-rw-r--r-- 1  501 staff  1223995 Jun 21 23:44 ui-11743155b847aedd04ac46dd41fa36c3.js
-rw-r--r-- 1  501 staff  2350220 Jun 21 23:44 ui-5753cf60829082a37d0e3290d9725684.map
-rw-r--r-- 1  501 staff   192576 Jun 21 23:44 ui-dark.css
-rw-r--r-- 1  501 staff   192760 Jun 21 23:44 ui-dark.rtl.css
-rw-r--r-- 1  501 staff   191441 Jun 21 23:44 ui-light.css
-rw-r--r-- 1  501 staff   191625 Jun 21 23:44 ui-light.rtl.css
-rw-r--r-- 1  501 staff        0 Jun 21 23:44 ui.css
-rw-r--r-- 1  501 staff        0 Jun 21 23:44 ui.rtl.css
-rw-r--r-- 1  501 staff 13658017 Jun 21 23:44 vendor-e79461cdb9093a0aaebb4b59adf1efc6.map
-rw-r--r-- 1  501 staff  4243266 Jun 21 23:44 vendor-ed805d466babe1ea344647cc847cc81b.js
-rw-r--r-- 1  501 staff    44030 Jun 21 23:44 vendor.css
-rw-r--r-- 1  501 staff    44049 Jun 21 23:44 vendor.rtl.css

Additional output:
ubuntu@rancher2-01:~$ kubectl --kubeconfig kube_config_rancher-cluster.yml get pods --all-namespaces
NAMESPACE       NAME                                      READY     STATUS      RESTARTS   AGE
cattle-system   cattle-6879b88dfb-h6vbr                   1/1       Running     0          4d
ingress-nginx   default-http-backend-564b9b6c5b-5vdc4     1/1       Running     0          4d
ingress-nginx   nginx-ingress-controller-hqzj2            1/1       Running     0          4d
ingress-nginx   nginx-ingress-controller-rmzlg            1/1       Running     0          4d
ingress-nginx   nginx-ingress-controller-zf5zv            1/1       Running     0          4d
kube-system     canal-7dw6h                               3/3       Running     0          4d
kube-system     canal-jvsjt                               3/3       Running     0          4d
kube-system     canal-k9m6t                               3/3       Running     0          4d
kube-system     kube-dns-5ccb66df65-knmq8                 3/3       Running     0          4d
kube-system     kube-dns-autoscaler-6c4b786f5-97djt       1/1       Running     0          4d
kube-system     rke-ingress-controller-deploy-job-t94bb   0/1       Completed   0          4d
kube-system     rke-kubedns-addon-deploy-job-w6v75        0/1       Completed   0          4d
kube-system     rke-network-plugin-deploy-job-ldc2j       0/1       Completed   0          4d
kube-system     rke-user-addon-deploy-job-zwzcz           0/1       Completed   0          4d

Thanks to @superseb in the Rancher slack channel he suggested I remove all nodes except the one running cattle from the lb and now the UI renders.

Once again from the slack superseb suggested using this gist to double check the network: https://gist.github.com/superseb/974039a3e84e899088d99b84c3fad6ef. I adapted to my 3 nodes cluster and there does appear to be a network problem:
ubuntu@rancher2-01:~$ ./pod-test.sh
daemonset.apps "alpine" created
Waiting for rollout to finish: 0 of 3 updated pods are available...
Waiting for rollout to finish: 1 of 3 updated pods are available...
Waiting for rollout to finish: 2 of 3 updated pods are available...
daemon set "alpine" successfully rolled out
=> Start
command terminated with exit code 1
rancher2-03.zymergen.net cannot reach rancher2-01.zymergen.net
command terminated with exit code 1
rancher2-03.zymergen.net cannot reach rancher2-02.zymergen.net
command terminated with exit code 1
rancher2-01.zymergen.net cannot reach rancher2-03.zymergen.net
command terminated with exit code 1
rancher2-01.zymergen.net cannot reach rancher2-02.zymergen.net
command terminated with exit code 1
rancher2-02.zymergen.net cannot reach rancher2-03.zymergen.net
command terminated with exit code 1
rancher2-02.zymergen.net cannot reach rancher2-01.zymergen.net
=> End

I`m use rancherOS in vsphere and get same result.
./k8s-kubectl-pod-network-test.sh
daemonset.apps "alpine" created
Waiting for rollout to finish: 0 of 6 updated pods are available...
Waiting for rollout to finish: 2 of 6 updated pods are available...
Waiting for rollout to finish: 2 of 6 updated pods are available...
Waiting for rollout to finish: 3 of 6 updated pods are available...
daemon set "alpine" successfully rolled out
=> Start
command terminated with exit code 1
k8s-ld2-worker-3 cannot reach k8s-ld2-worker-2
command terminated with exit code 1
k8s-ld2-worker-1 cannot reach k8s-ld2-worker-2
command terminated with exit code 1
k8s-ld2-worker-6 cannot reach k8s-ld2-worker-2
command terminated with exit code 1
k8s-ld2-worker-2 cannot reach k8s-ld2-worker-3
command terminated with exit code 1
k8s-ld2-worker-2 cannot reach k8s-ld2-worker-1
command terminated with exit code 1
k8s-ld2-worker-2 cannot reach k8s-ld2-worker-6
=> End


sawtooth-validator-default  sawtooth-validator-default

When I use Docker for a Single Sawtooth Node. Follow the steps in website.
In Step 3: Start the Sawtooth Docker Environment:
The problem is below:
sawtooth-settings-tp-default          | INFO  | sawtooth_sdk::proces | Message: cf7742d809ff457fba0fc06eedc907e2
sawtooth-settings-tp-default          | INFO  | sawtooth_sdk::proces | sending PingResponse
sawtooth-validator-default            | [2023-10-31 03:09:49.534 DEBUG    interconnect] No response from 713cce62a68f7672e0ade9a65366537d1387fc01b6fea726893ab30449d76b92f62d207742a703762d9f866d9ea45e97c57061195fea078e28e9241ec2ff5e69 in 10.007903337478638 seconds - beginning heartbeat pings.
sawtooth-validator-default            | [2023-10-31 03:09:49.535 DEBUG    interconnect] No response from 02744ab3a5235fe142c08ed48ae078e1f91ff11615f09dda419b8b5759e7c449008a4f670648583d6259e7361d9c9a25db4f68a4e2f011bc74da3bb7ab8252ae in 10.007768869400024 seconds - beginning heartbeat pings.
sawtooth-validator-default            | [2023-10-31 03:09:49.536 DEBUG    interconnect] No response from 010132a6c832702654c52751072ccdf2fd5379befa1f245fcbe4cb25083689bd100e37f7905c56d709308f96c46067a16a0a66f6d094d5fda79505cead42c302 in 10.006694316864014 seconds - beginning heartbeat pings.
sawtooth-intkey-tp-python-default     | [2023-10-31 03:09:49.536 DEBUG    core] received message of type: PING_REQUEST
sawtooth-xo-tp-python-default         | [2023-10-31 03:09:49.537 DEBUG    core] received message of type: PING_REQUEST
sawtooth-settings-tp-default          | INFO  | sawtooth_sdk::proces | Message: c084d9c80c744fa79534ee9c2a5407c0
sawtooth-settings-tp-default          | INFO  | sawtooth_sdk::proces | sending PingResponse
sawtooth-validator-default            | [2023-10-31 03:09:59.540 DEBUG    interconnect] No response from 713cce62a68f7672e0ade9a65366537d1387fc01b6fea726893ab30449d76b92f62d207742a703762d9f866d9ea45e97c57061195fea078e28e9241ec2ff5e69 in 10.001838684082031 seconds - beginning heartbeat pings.
sawtooth-validator-default            | [2023-10-31 03:09:59.541 DEBUG    interconnect] No response from 02744ab3a5235fe142c08ed48ae078e1f91ff11615f09dda419b8b5759e7c449008a4f670648583d6259e7361d9c9a25db4f68a4e2f011bc74da3bb7ab8252ae in 10.00159239768982 seconds - beginning heartbeat pings.
sawtooth-validator-default            | [2023-10-31 03:09:59.541 DEBUG    interconnect] No response from 010132a6c832702654c52751072ccdf2fd5379befa1f245fcbe4cb25083689bd100e37f7905c56d709308f96c46067a16a0a66f6d094d5fda79505cead42c302 in 10.00166654586792 seconds - beginning heartbeat pings
So, is there any problem with the step before or proxy?

The heartbeat pings message is not an issue. That debug log is just letting
you know that heartbeat pings are being sent to keep the connections alive.
If the network is underload, the heartbeat messages are not required.
On Mon, Oct 30, 2023 at 10:02 PM liuchao11 @.***> wrote:

When I use Docker for a Single Sawtooth Node. Follow the steps in website
https://sawtooth.hyperledger.org/docs/1.2/app_developers_guide/installing_sawtooth.html
.
In Step 3: Start the Sawtooth Docker Environment:
The problem is below:
sawtooth-settings-tp-default | INFO | sawtooth_sdk::proces | Message:
bd8dccc6b99d4ad5855651160adf261d
sawtooth-settings-tp-default | INFO | sawtooth_sdk::proces | sending
PingResponse
sawtooth-validator-default | [2023-10-31 02:54:41.614 DEBUG interconnect]
No response from
c1f3eeaed030584111afa187be97c36f01b3d07cc1d57739ecba003794daf62086b12c5ce1ae6832651e3b563751f589cdc4a12ff5d9893de1e82c547696119f
in 10.008634567260742 seconds - beginning heartbeat pings.
So, is there any problem with the step before or proxy?
—
Reply to this email directly, view it on GitHub
https://github.com/hyperledger/sawtooth-core/issues/2467, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEK7EPXYNRYE7RELULTQIT3YCBS2XAVCNFSM6AAAAAA6W7SSXGVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE3DSNJUGQ3TGOA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

@agunde406 Thank you! There is another problem in the step Creating a Sawtooth Test Network.
When I download sawtooth-default-pbft.yaml, then run the step one by one.  As I start the Sawtooth network, sawtooth-validator-default-0 container is not running. The wrong code is as below:
sawtooth-validator-default-0    | Generated config-genesis.batch
sawtooth-validator-default-0    | sawtooth.consensus.pbft.members=["0366aac61c18ff2e044e9ce1775fb865b38eb5eee98b78c00287ed37c189dc57f5","02e64eee2926effd634c65ceecf85f46c417ff0e15e8515a863b60c7fb36a59ff0","037b362e1575065e682719712d28eeeef291685726684e435c20de84e68277ab1a","02eb8d8c5d0f6064665f32bdb41fcd1ba216e1c7d85d26d0a460e5d9b088cfc1f4","03c95b24131139e7d82a151214e05d7f1262467fcb30104462ccd23e85b56c1d94"]
sawtooth-validator-default-0    | usage: sawset proposal create [-h] [-k KEY]
sawtooth-validator-default-0    |                               [-o OUTPUT | --url URL | --sabre-output SABRE_OUTPUT]
sawtooth-validator-default-0    |                               setting [setting ...]
sawtooth-validator-default-0    | sawset proposal create: error: the following arguments are required: setting
sawtooth-validator-default-0    | bash: line 22: -k: command not found
sawtooth-validator-default-0    | bash: line 23: sawtooth.consensus.algorithm.name=pbft: command not found
sawtooth-validator-default-0    | bash: line 24: sawtooth.consensus.algorithm.version=1.0: command not found
sawtooth-validator-default-0    | bash: line 25: sawtooth.consensus.pbft.members=["0366aac61c18ff2e044e9ce1775fb865b38eb5eee98b78c00287ed37c189dc57f5","02e64eee2926effd634c65ceecf85f46c417ff0e15e8515a863b60c7fb36a59ff0","037b362e1575065e682719712d28eeeef291685726684e435c20de84e68277ab1a","02eb8d8c5d0f6064665f32bdb41fcd1ba216e1c7d85d26d0a460e5d9b088cfc1f4","03c95b24131139e7d82a151214e05d7f1262467fcb30104462ccd23e85b56c1d94"]: command not found
sawtooth-validator-default-0    | bash: line 26: sawtooth.publisher.max_batches_per_block=1200: command not found
sawtooth-validator-default-0    | bash: line 27: -o: command not found
sawtooth-validator-default-0    | bash: line 36: --endpoint: command not found
sawtooth-validator-default-0    | bash: line 37: --bind: command not found
sawtooth-validator-default-0    | bash: line 38: --bind: command not found
sawtooth-validator-default-0    | bash: line 39: --bind: command not found
sawtooth-validator-default-0    | bash: line 40: --scheduler: command not found
sawtooth-validator-default-0    | bash: line 41: --peering: command not found
sawtooth-validator-default-0    | bash: line 42: --maximum-peer-connectivity: command not found


Error: package ‘LandsatLinkr’ was installed before R 4.0.0: please re-install it

As suggested on the Guide page, I used all the three commands in sequence to install the package. However, it looks like the SDMTools package is not installed. On Googling I found that the SDMTools package is no longer available on CRAN. I found an alternative solution here. Now, SDMTools installation is complete--I checked the installation by calling the library. Installing LandsatLinkr says package ‘LandsatLinkr’ successfuly unpacked and MD5 sums checked, but when I call LandsatLink, it says:
Error: package or namespace load failed for ‘LandsatLinkr’: package ‘LandsatLinkr’ was installed before R 4.0.0: please re-install it

To fix this, I tried the solution given here, but it doesn't work. I uninstalled all packages and re-installed them, manual version of the same solution, but no luck so far.
My specs from a fresh R session:

Am I doing something fundamentally wrong?

@PratyushTripathy thanks for your interest in LandsatLinkr. Unfortunately, the package is quite stale and will likely not work without updates to dependencies and code. My apologies for not having a message as such on the README. I've just added one:
⚠ This repository is no longer in development and is not supported ⚠
You'll likely find that unmaintained dependencies and versioning conflicts make
this package unusable.
Progress is (slowly) being made on ee-LandsatLinkr,
which offers similar MSS-to-successor harmonization procedures using Google Earth Engine.
Unfortunately, I can no longer offer help on this package.
Best regards,
Justin


API Port flags compiler generated code in portable class libraries

Hi, I'm trying out API Port on one of my project and noticed that it was flagging some compiler generated code. A simple repro:

Create a new Portable Class Library (I did C#, .NET Framework 4.6, Windows Universal 10.0).
Add a new Resource File (.resx).
Build.
Run API Port.

It flags the compiler generated ResourceManager property as a portability issue. Is this is a problem?

This is a known issue #113.
As a tangential aside, the C# backing to *.resx is generated by an external tool (ie. resgen.exe) and not the C# compiler.

@conniey this doesn't seem the same as #113 - there, TypeInfo is showing up due to it being derived and thus showing up as being on Type. This is an issue involving generated methods/types. These are usually annotated with some sort of attribute - maybe we could add a way to filter those out?

An example: https://github.com/Microsoft/dotnet-apiport/blob/master/src/Microsoft.Fx.Portability/Resources/LocalizedStrings.Designer.cs
The type has [global::System.Runtime.CompilerServices.CompilerGeneratedAttribute()] which we may be able to filter out - not sure how much work that would be in the metadata reader.

Ahh, I see what you're saying now.. Hmm that may be a little work due to how we calculate the docIds in MetadataReader.

Look at this feature when IOperation is available.

Rerun the resgen tool supporting .NET standard should fix the issue.


[cross-filtering] emitting timestamp filter break the dashboard

Clicking on timestamp on table chart to emit filter break the dashboard
Expected results
Should be able to filter by that timestamp i clicked on
Actual results
Dashboard error
Screenshots
https://user-images.githubusercontent.com/52086618/128303039-30890b2a-843e-4acc-8dfe-3239f0ca4f7a.mp4
How to reproduce the bug

Go to '...'
Click on '....'
Scroll down to '....'
See error

Environment
cross-filtering flag, native filter flag, UX_BETA flag, d&d flag on

This has been fixed by https://github.com/apache-superset/superset-ui/pull/1281, closing


Mail catching smtp timeout when running in background

Hi Guys,
I have a very strange issue but I do not how I could debug it any further.
1, if I run mailcatcher in the foreground -f -v
a, web interface works perfectly
b, smtp receives emails flawlessly
2, if I run it in the backgroud
a, web interface works
b, smtp interface does not respond.
Dec 22 12:34:24 sendemail[10247]: ERROR => Timeout while reading from localhost:2525 There was no response after 60 seconds.
If I want to telnet into it I CAN!
It is not a port issue as I run the test on the same computer and when it is in foreground mode it works.
I do not see any error logs anywhere. is there a way to enable some debug mode so that I can see why the smtp timeouts ?
Any idea what can be wrong ?
my ruby version is -> ruby 1.9.3p547 (2014-05-14 revision 45962) [x86_64-linux]
my mailcatcher version is mailcatcher (0.5.12)
My local gems:
*** LOCAL GEMS ***
activesupport (3.2.19)
bigdecimal (1.1.0)
builder (3.2.2)
bundler (1.5.3)
chef (11.16.4)
chef-zero (2.2)
coderay (1.1.0)
daemons (1.1.9)
diff-lcs (1.2.5)
docile (1.1.5)
erubis (2.7.0)
eventmachine (1.0.4)
ffi (1.9.5)
ffi-yajl (1.1.0)
haml (4.0.6)
hashie (2.1.2)
highline (1.6.21)
i18n (0.6.11)
io-console (0.3)
ipaddress (0.8.0)
json (1.8.1, 1.5.5)
libyajl2 (1.0.1)
mail (2.6.3)
mailcatcher (0.5.12)
method_source (0.8.2)
mime-types (1.25.1)
minitest (2.5.1)
mixlib-authentication (1.3.0)
mixlib-cli (1.5.0)
mixlib-config (2.1.0)
mixlib-log (1.6.0)
mixlib-shellout (1.6.0)
multi_json (1.10.1)
mysql (2.9.1)
net-ssh (2.9.1)
net-ssh-gateway (1.2.0)
net-ssh-multi (1.2.0)
ohai (7.4.0)
plist (3.1.0)
pry (0.10.1)
rack (1.5.2)
rack-protection (1.5.3)
rake (10.1.1, <IP_ADDRESS>)
rdoc (3.9.5)
rest-client (1.6.7)
rspec (2.14.1)
rspec-core (2.14.8)
rspec-expectations (2.14.5)
rspec-mocks (2.14.6)
rspec_junit_formatter (0.1.6)
ruby-shadow (2.3.4)
simplecov (0.9.1)
simplecov-html (0.8.0)
sinatra (1.4.5)
skinny (0.2.3)
slop (3.6.0)
sqlite3 (1.3.10)
systemu (2.6.4)
thin (1.5.1)
tilt (1.4.1)
wmi-lite (1.0.0)

Exactly the same problem, and workaround.

Just got the same issue, and seems like it somehow depends on Ruby version.
The mailcatcher as a daemon doesn't work on Ruby 2.1.5p273, and everything works perfectly fine on Ruby 2.1.3p242.
I haven't changed anything on the project except Ruby version. The daemon stopped working after upgrade to Ruby 2.1.5.

+1, I encountered this when upgrading from Rails 4.1.x to Rails 4.2. I traced it down to: net/smtp
Right before it sends the email
# byebug break point
b /usr/local/lib/ruby/2.1.0/net/smtp.rb:555
c

Net Smtp id file (/usr/local/lib/ruby/2.1.0/net/smtp.rb:555)
# $Id: smtp.rb 45111 2014-02-22 05:39:58Z naruse $
Actual code
def do_start(helo_domain, user, secret, authtype)
  raise IOError, 'SMTP session already started' if @started
  if user or secret
    check_auth_method(authtype || DEFAULT_AUTH_TYPE)
    check_auth_args user, secret
  end
  s = Timeout.timeout(@open_timeout, Net::OpenTimeout) do
    tcp_socket(@address, @port)
  end
  logging "Connection opened: #{@address}:#{@port}"
  @socket = new_internet_message_io(tls? ? tlsconnect(s) : s)
  check_response critical { recv_response() }  # <--- recv_response() doesn't get anything; ERGO; time out.

I think the error comes from EventMachine, since mailcatcher appears to rely on it for the majority of the Server IO issues.

Forcing the mailcatcher to use
gem 'eventmachine', '1.0.3'
fixes the problem

I solved the problem for myself by installing eventmachine 1.0.3
 gem install eventmachine -v 1.0.3
 gem uninstall eventmachine -v 1.0.4

and then restarting mailcatcher.

@danlo that worked for me too! :+1:

@danlo +1, also fixed for me

Thanks @danlo, that does the trick!

:+1: @danlo

:+1: @danlo

:+1: @danlo

I am getting the same problem on osx 10.10.1, rails 4.2, and ruby 2.2.0.  I tried @danlo's fix but that tossed another huge error for me:
➜  ~  gem install eventmachine -v 1.0.3
Building native extensions.  This could take a while...
ERROR:  Error installing eventmachine:
	ERROR: Failed to build gem native extension.

    /Users/chrishough/.rbenv/versions/2.2.0/bin/ruby -r ./siteconf20150107-6357-13us0t8.rb extconf.rb
checking for rb_trap_immediate in ruby.h,rubysig.h... no
checking for rb_thread_blocking_region()... no
checking for inotify_init() in sys/inotify.h... no
checking for __NR_inotify_init in sys/syscall.h... no
checking for writev() in sys/uio.h... yes
checking for rb_wait_for_single_fd()... yes
checking for rb_enable_interrupt()... no
checking for rb_time_new()... yes
checking for sys/event.h... yes
checking for sys/queue.h... yes
creating Makefile

make "DESTDIR=" clean

make "DESTDIR="
compiling binder.cpp
compiling cmain.cpp
compiling ed.cpp
compiling em.cpp
em.cpp:827:9: error: use of undeclared identifier 'rb_thread_select'; did you mean 'rb_thread_fd_select'?
        return EmSelect (maxsocket+1, &fdreads, &fdwrites, &fderrors, &tv);
               ^~~~~~~~
               rb_thread_fd_select
./em.h:25:20: note: expanded from macro 'EmSelect'
  #define EmSelect rb_thread_select
                   ^
/Users/chrishough/.rbenv/versions/2.2.0/include/ruby-2.2.0/ruby/intern.h:454:5: note: 'rb_thread_fd_select' declared here
int rb_thread_fd_select(int, rb_fdset_t *, rb_fdset_t *, rb_fdset_t *, struct timeval *);
    ^
em.cpp:827:32: error: cannot initialize a parameter of type 'rb_fdset_t *' with an rvalue of type 'fd_set *'
        return EmSelect (maxsocket+1, &fdreads, &fdwrites, &fderrors, &tv);
                                      ^~~~~~~~
/Users/chrishough/.rbenv/versions/2.2.0/include/ruby-2.2.0/ruby/intern.h:454:42: note: passing argument to parameter here
int rb_thread_fd_select(int, rb_fdset_t *, rb_fdset_t *, rb_fdset_t *, struct timeval *);
                                         ^
em.cpp:946:6: error: use of undeclared identifier 'rb_thread_select'; did you mean 'rb_thread_fd_select'?
                                        EmSelect (0, NULL, NULL, NULL, &tv);
                                        ^~~~~~~~
                                        rb_thread_fd_select
./em.h:25:20: note: expanded from macro 'EmSelect'
  #define EmSelect rb_thread_select
                   ^
/Users/chrishough/.rbenv/versions/2.2.0/include/ruby-2.2.0/ruby/intern.h:454:5: note: 'rb_thread_fd_select' declared here
int rb_thread_fd_select(int, rb_fdset_t *, rb_fdset_t *, rb_fdset_t *, struct timeval *);
    ^
3 errors generated.
make: *** [em.o] Error 1

make failed, exit code 2

Gem files will remain installed in /Users/chrishough/.rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/eventmachine-1.0.3 for inspection.
Results logged to /Users/chrishough/.rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/extensions/x86_64-darwin-14/2.2.0-static/eventmachine-1.0.3/gem_make.out

:+1: @danlo

Thank you for this, hours of reading articles where it just all about port 1080 and no one cares about 1025. This helped save my sanity. @danlo

:+1:  @danlo, thanks!

Nice solution @danlo ! Thanks!

Seems to be a bug in the latest version of EventMachine, sadly. -.-
The reason it doesn't daemonise until after the eventmachine loop is running is so that port failures can be reported to the user.
I'll see what's going on upstream in eventmachine. But honestly eventmachine has become a major pain. May see if there's a feasible alternative, maybe even going back to the standard library with a custom select loop.

@danlo, Thank you soo much!

@danlo, Thank you!!!

@sj26 Someone mentioned on another thread; but could we have a new release of the existing code, but just forcing event machine at 1.0.3?

Just tested this myself, when mailcatcher -v 0.5.12 is running with eventmachine -v 1.0.4 the timeout happens.
Note: mailcatcher -v 0.5.12 does not install eventmachine -v 1.0.4, something else in your project is what is causing the 1.0.4 version to be installed. So this can also be fixed by forcing your project to install 1.0.3 and then uninstalling the 1.0.4 version.

I issued a pull request as a temporary fix that forces the version of eventmachine to be less than 1.0.4. If that is not used, eventmachine will default install 1.0.4 which will cause the timeout issue

This does seem to be an eventmachine regression.
Please try mailcatcher 0.6.0pre1 (gem install mailcatcher --pre) which restricts eventmachine to != 1.0.4.

@chrishough eventmachine 1.0.3 is not compatible with ruby 2.2, so you need to use ruby 2.1 or older.

I have the same issue. Running as mailcatcher -f works for me too.

@matthewbarram please try mailcatcher 0.6.0pre1 (gem install mailcatcher --pre).

@sj26 Just came to report this exact bug. Brought in the 0.0.0pre1, as you suggested, and I can now run it fine without --foreground - thank you :+1:

This has been worked around in 0.6.0, please upgrade with gem install mailcatcher.
The root cause of this has also been lodged as an issue upstream:
https://github.com/eventmachine/eventmachine/issues/569

Ah, I see:
eventmachine (1.0.5)

They must have released a new version which has broken my fix. I'll look into it again.

:+1:

mailcatcher 0.6.1 is out which works with eventmachine up to 1.0.5, and restricts future upgrades.

@sj26 downloading now and will report back, many thanks for monitoring this, great response.

@sj26 It works! Thanks again for your timely update.

@danlo :+1:

not sure if this is still open, but I am running into this problem where mailcatcher has stopped working. Nothing that I know of has changed (other than switching between a lot of branches) and I can't find any error messages showing where something might be breaking. right now in development I can see the emails being sent in the logs, but they're not popping up in mailcatcher. here's my set up

Rails 4.2.6
ruby 2.2.2p95
mailcatcher 0.6.4

I have tried @danlo tip and it didn't work (ended with a result similar to @chrishough) and tried running with mailcatcher -f -v and installing gem install mailcatcher --pre and still am not getting it to work. are there any other workarounds?

I'm having the same problems as @jmnewman.
Using
ruby 2.3.0p0 (with rvm)
mailcatcher 0.6.4
eventmachine <IP_ADDRESS>


Logo doesn't appear after uploaded.

When I uploaded logo and click on Submit. The logo doesn't appear but the flash message show "The site has been updated."

+1

Fixed!