pyspread: 2.2.3 -> 2.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for pyspread is: Python-oriented spreadsheet application
meta.homepage for pyspread is: https://pyspread.gitlab.io/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.3 with grep in /nix/store/s5vywmclfbzr4mm83gzi6s030wvbbj25-pyspread-2.3
found 2.3 in filename of file in /nix/store/s5vywmclfbzr4mm83gzi6s030wvbbj25-pyspread-2.3

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

pyspread

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/s5vywmclfbzr4mm83gzi6s030wvbbj25-pyspread-2.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A pyspread https://github.com/r-ryantm/nixpkgs/archive/52f210ec74e23f79e587f61c13ad7f23df7d9f6f.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/52f210ec74e23f79e587f61c13ad7f23df7d9f6f#pyspread

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/s5vywmclfbzr4mm83gzi6s030wvbbj25-pyspread-2.3
ls -la /nix/store/s5vywmclfbzr4mm83gzi6s030wvbbj25-pyspread-2.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

pyspread
pyspread.dist

Maintainer pings
cc @AndersonTorres for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@NixOS/nixpkgs-merge-bot merge


process_all.py filling up drive

The process_all.py file is creating too much data. We need to maintain the images initially in order to get a smoothed center value and to remove outliers based on the smoothed centers. Trying to optimize the amount of files that can be run at once if I delete the image data sets after each iteration (i.e., 600 files at once vs 1000 files at once). So far after 1600 images processed (first batch with 600, second batch with 1000), crashes when trying to run the last 1000 files.

Caps at 15G


Cannot run website

Expected Behavior
Everything runs nicely and I get normal hugo logs
Current Behavior
➜  hugo server                                                                                in hugo-toha.github.io on  main [!] is 📦 v0.1.0 via 🐹 v1.19.4 via 
Start building sites …
hugo v0.109.0+extended linux/amd64 BuildDate=unknown
ERROR 2023/01/15 09:25:04 js.Build failed: "/tmp/hugo_cache/modules/filecache/modules/pkg/mod/github.com/hugo-toha/toha/v4@v4.0.0-20230105191255-374b4019d89d/assets/scripts/application.js:2:7": Could not resolve "bootstrap"
ERROR 2023/01/15 09:25:04 js.Build failed: "/tmp/hugo_cache/modules/filecache/modules/pkg/mod/github.com/hugo-toha/toha/v4@v4.0.0-20230105191255-374b4019d89d/assets/scripts/application.js:3:7": Could not resolve "@fortawesome/fontawesome-free/js/all"
ERROR 2023/01/15 09:25:04 js.Build failed: "/tmp/hugo_cache/modules/filecache/modules/pkg/mod/github.com/hugo-toha/toha/v4@v4.0.0-20230105191255-374b4019d89d/assets/scripts/features/darkmode/darkreader.js:1:54": Could not resolve "darkreader"
ERROR 2023/01/15 09:25:04 js.Build failed: "/tmp/hugo_cache/modules/filecache/modules/pkg/mod/github.com/hugo-toha/toha/v4@v4.0.0-20230105191255-374b4019d89d/assets/scripts/features/syntaxhighlight/hljs.js:1:17": Could not resolve "highlight.js"
ERROR 2023/01/15 09:25:04 js.Build failed: "/tmp/hugo_cache/modules/filecache/modules/pkg/mod/github.com/hugo-toha/toha/v4@v4.0.0-20230105191255-374b4019d89d/assets/scripts/features/videoplayer/plyr.js:1:17": Could not resolve "plyr"
ERROR 2023/01/15 09:25:04 js.Build failed: "/tmp/hugo_cache/modules/filecache/modules/pkg/mod/github.com/hugo-toha/toha/v4@v4.0.0-20230105191255-374b4019d89d/assets/scripts/pages/home.js:1:21": Could not resolve "ityped"
ERROR 2023/01/15 09:25:04 js.Build failed: "/tmp/hugo_cache/modules/filecache/modules/pkg/mod/github.com/hugo-toha/toha/v4@v4.0.0-20230105191255-374b4019d89d/assets/scripts/pages/note.js:1:25": Could not resolve "imagesloaded"
ERROR 2023/01/15 09:25:04 js.Build failed: "/tmp/hugo_cache/modules/filecache/modules/pkg/mod/github.com/hugo-toha/toha/v4@v4.0.0-20230105191255-374b4019d89d/assets/scripts/pages/search.js:1:17": Could not resolve "fuse.js"
ERROR 2023/01/15 09:25:04 js.Build failed: "/tmp/hugo_cache/modules/filecache/modules/pkg/mod/github.com/hugo-toha/toha/v4@v4.0.0-20230105191255-374b4019d89d/assets/scripts/pages/search.js:2:17": Could not resolve "mark.js"
ERROR 2023/01/15 09:25:04 js.Build failed: "/tmp/hugo_cache/modules/filecache/modules/pkg/mod/github.com/hugo-toha/toha/v4@v4.0.0-20230105191255-374b4019d89d/assets/scripts/sections/projects.js:1:22": Could not resolve "filterizr"
ERROR 2023/01/15 09:25:04 js.Build failed: "/tmp/hugo_cache/modules/filecache/modules/pkg/mod/github.com/hugo-toha/toha/v4@v4.0.0-20230105191255-374b4019d89d/assets/scripts/sections/publications.js:1:22": Could not resolve "filterizr"
Error: Error building site: JSBUILD: failed to transform "scripts/application.js" (text/javascript): "/tmp/hugo_cache/modules/filecache/modules/pkg/mod/github.com/hugo-toha/toha/v4@v4.0.0-20230105191255-374b4019d89d/assets/scripts/application.js:1:7": Could not resolve "popper.js"
Built in 596 ms

Steps to Reproduce

git clone https://github.com/hugo-toha/hugo-toha.github.io.git
cd hugo-toha.github.io
hugo server

Detailed Description

hugo v0.109.0+extended linux/amd64 BuildDate=unknown
Void Linux x86_64 with Linux 6.1.4_1 on Inspiron 3521 A07
Tried it on:

my own website
the default toha website

Oh, just found #725. I think it should be clarified. Like an issue that says the website is being rewritten should be pinned or it should be added to the README. Sorry for the annoyance and sorry again if it is already clearly written somewhere. I could not see it anywhere. I apologize again for wasting your time.

Added a warning in the README. Thank you for the suggestion.

That's really bad practice to introduce new features/bugs to the main branch rather than using a development branch and then merging.

The main branch is completely runnable. Just the instructions and configurations has changed which is not documented yet. Isn't it a best practice for user to use a release instead of main branch?

That's when there's no git submodule add https://github.com/hugo-toha/toha.git themes/toha all over the place!

@arminms My apologies, if my previous comment disappointed you. I have updated the Requirements and Usage section in README.md with new instruction. Please, take a look and let me know if it does work for you.

When I try hugo mod tidy I get: Error: module "github.com/hugo-toha/toha/v4" not found.

Can you please share your repository. I am suspecting some configuration issues.

Turned out my golang and Node versions were not the minimum mentioned. Updating them solved the problem. Thanks!

Hi @salastro, I have updated the quickstart guide. You should be able to run the website from main branch.
Ref: https://toha-guides.netlify.app/posts/quickstart/#

When I follow start from scratch (i.e. not by forking hugo-toha.github.io) under Usage, everything works fine but ends up showing serif typeface (e.g. Times New Roman) rather than san-serif typeface (e.g. Arial). Do you know what could be the problem?

Look like you forgot to mount the font's from node module. Check the sample here: https://github.com/hugo-toha/hugo-toha.github.io/blob/dd88f0fb7af186f83ece20c507deac61ac324c5c/config.yaml#LL10


*: added linters

What problem does this PR solve?
Lightning lacks a linter.
What is changed and how it works?
Added several linting mechanisms (go fmt, go vet, golangci-lint, revive) shared by other projects. Currently Lightning fails the checks, and will be fixed in future PRs.
Check List
Tests

Manual test (add detailed scripts or steps below)

Run make check and got the warnings 🙃

Side effects
Related changes

/run-all-tests

PTAL @amyangfei @july2993

/run-all-tests

/run-all-tests


Typo

Changed segemnts to segments

Coverage decreased (-3.8%) to 94.318% when pulling 183aa0767ba74f48ab08f70fa2cadec4e2c3f0d2 on SandroMiguel:patch-1 into df2d5269043b69149c0c6b448bcddf050203537a on benmosher:master.

Coverage decreased (-3.8%) to 94.318% when pulling 183aa0767ba74f48ab08f70fa2cadec4e2c3f0d2 on SandroMiguel:patch-1 into df2d5269043b69149c0c6b448bcddf050203537a on benmosher:master.


pip install exits successfully on Git Bash, but wifi-password: not recognized

$ wifi-password
bash: wifi-password: command not found

Not sure why wifi-password command not recognized, I tried reloading Git Bash, but same error.
But installing through Git worked, so I'm currently using that.
output.txt
Attached is a snippet log of my terminal.
I suppose the next issue would be the command returning ERROR: SSID was not found regardless of what flags I pass through.

Hey @KevinIsMyName,
Kevin@KEVIN-AMD-PC MINGW64 ~
$ pip install wifi-password
Requirement already satisfied: wifi-password in c:\users\kevin\appdata\roaming\python\python38\site-packages (1.0.7)
Requirement already satisfied: qrcode in c:\users\kevin\appdata\roaming\python\python38\site-packages (from wifi-password) (6.1)
Requirement already satisfied: six in c:\users\kevin\appdata\local\programs\python\python38-32\lib\site-packages (from qrcode->wifi-password) (1.14.0)
Requirement already satisfied: colorama in c:\users\kevin\appdata\roaming\python\python38\site-packages (from qrcode->wifi-password) (0.4.4)

Kevin@KEVIN-AMD-PC MINGW64 ~
$ wifi-password
bash: wifi-password: command not found

The reason why this is happening is most likely because the directory which pip stores the scripts/commands that you have installed is not in your $PATH. I unfortunately don't much about Python's directory structure on Windows, so you'll have to try and Google it.

Kevin@KEVIN-AMD-PC MINGW64 ~
$ git clone https://github.com/sdushantha/wifi-password
Cloning into 'wifi-password'...
remote: Enumerating objects: 169, done.
remote: Counting objects: 100% (169/169), done.
remote: Compressing objects: 100% (119/119), done.
remote: Total 169 (delta 105), reused 79 (delta 44), pack-reused 0
Receiving objects: 100% (169/169), 14.63 MiB | 13.15 MiB/s, done.
Resolving deltas: 100% (105/105), done.

Kevin@KEVIN-AMD-PC MINGW64 ~
$ cd wifi-password

Kevin@KEVIN-AMD-PC MINGW64 ~/wifi-password (master)
$ python3 setup.py install
bash: /c/Users/Kevin/AppData/Local/Microsoft/WindowsApps/python3: Permission denied

There must be something wrong with Python3's permissions on your system since when you ran the same command but with python instead, it worked. But like I said earlier, I dont know much about how Python works on Windows.

Kevin@KEVIN-AMD-PC MINGW64 ~/wifi-password (master)
$ wifi-password
ERROR: SSID was not found

Looks like you were able to install wifi-password, that's great!
Well, I believe that the error must be occurring because you are using Git Bash. There is a chance that wifi-password thinks that you are using Linux and then is trying to execute the code for Linux systems.

Could you run the Python code below through Git Bash and let me know what the output is?
import sys
sys.platform

Kevin@KEVIN-AMD-PC MINGW64 ~
$ python
Python 3.8.2 (tags/v3.8.2:7b3ab59, Feb 25 2020, 22:45:29) [MSC v.1916 32 bit (In
tel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> sys.platform
'win32'

Yep! I was thinking of mentioning that it's probably because it's Git Bash. I wanted to compare it to a WSL2 Ubuntu-20.04 LTS, but that was another rabbithole (that I don't feel like digging because busybusybusy).
I think it might just be best to install it with Git and the setuptools if you're using a non-Linux architecture, like GitHub


Deprecated deriveKeyFromPassword: Incorrect derived key!

Trying create a keystore with asymEncrypt purpose now that deriveKeyFromPassword is deprecated and seem doesn't work or i'm on wrong way:
Old way:
lightwallet.keystore.deriveKeyFromPassword(pass, function (err, pwDerivedKey) {
   mykeystore = new lightwallet.keystore(seed, pwDerivedKey,hdPath);
   var info={curve: 'curve25519', purpose: 'asymEncrypt'};
   mykeystore.addHdDerivationPath(hdPath,pwDerivedKey,info);
   mykeystore .generateNewEncryptionKeys(pwDerivedKey, 1, hdPath);
   mykeystore.setDefaultHdDerivationPath(hdPath);
   mykeystore.passwordProvider = pass;
})

New (wrong?) way:
lightwallet.keystore.createVault({
     password: pass
   }, function (err, ks) {
          ks.keyFromPassword(pass, function (err, pwDerivedKey) {
            if (err) throw err;
            var info={curve: 'curve25519', purpose: 'asymEncrypt'};
            ks.addHdDerivationPath(hdPath,pwDerivedKey,info);
            ks.generateNewEncryptionKeys(pwDerivedKey, 1, hdPath);
            ks.setDefaultHdDerivationPath(hdPath);
            ks.passwordProvider = pass;
          });
 });

With this new code i can create the keystone but i receive "Incorrect derived key!" when try to encrypt string using lightwallet.encryption.multiEncryptString method
Could @christianlundkvist help?

similar issue for me at 'Incorrect derived key! at KeyStore.getSeed'


Enable sending a server message to the client on app start / login

When the client logs in, the server can optionally send a short message to be displayed to the user. Only for API 2.0.

Closed by #118


Regsiter pulls unprovided name & URL from bower.json

Allows calling the register command without required name and url arguments:
bower register

In this case, we attempt to pull these values from a local bower.json file, assuming the user's current working directory is that of the package being registered.
This makes it more convenient to register packages, and more familiar to users of npm publish, which has the same convention of assuming local package registration and not requiring any arguments.
In command-line mode, the usual confirmation prompt is still presented, so it shouldn't be very dangerous, at least for that use case. I deleted two failing test cases since they were tested for arguments that are no longer required immediately. I'm not sure yet how to add test cases checking what happens when the bower.json does or doesn't have the pulled properties. Added test cases for new scenarios.
I have not yet changed the messaging of the error indicating the arguments are required, nor have I yet changed the help/usage as such.
I realize the onArgsReady function has interesting indentation, but I wanted to minimize line changes to ease merge in case of other changes to the function - but I can reformat & rebase if requested.

Bower is depreacated and doesn't allow new features


Update README.md

Move the "non-ambient" section up.
Add description on when to use which.

Thank Johnny. 👍


Issue with Python code

Great plugin! It works fine with cpp files, but I encoutered problems with python code. I have set
let g:indent_blankline_debug = v:true
and didn't see any error messages.
Here is my neovim version:
NVIM v0.5.0-563-ge628a05b5
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: /usr/bin/gcc-5 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -O2 -g -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/home/travis/build/neovim/bot-ci/build/neovim/build/config -I/home/travis/build/neovim/bot-ci/build/neovim/src -I/home/travis/build/neovim/bot-ci/build/neovim/.deps/usr/include -I/usr/include -I/home/travis/build/neovim/bot-ci/build/neovim/build/src/nvim/auto -I/home/travis/build/neovim/bot-ci/build/neovim/build/include
Compiled by travis@travis-job-fcb253cc-3966-4429-bc1c-27234ed4df2e

And the minimal vimrc:
call plug#begin('~/.vim/plugged')
Plug 'Yggdroot/indentLine'
Plug 'lukas-reineke/indent-blankline.nvim'
call plug#end()

let g:indentLine_char = '│'
let g:indent_blankline_debug = v:true

I think the problem comes from the default python indent expression. After installed https://github.com/Vimjas/vim-python-pep8-indent as suggested in #11, the problem goes away. Sorry for bothering!

yea default Python indentation isn't the best. Glad its working now


Deregister linux workers

I found the switch in the onboarding.py script, and would see it as being helpful to call out the functionality to deregister Linux Hybrid runbook workers using the onboarding script.

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

ID: 556bec6a-3427-7167-b427-c3fdf9c312d5
Version Independent ID: 26702360-82ce-aa39-2eaa-c406b0796189
Content: Remove Azure Automation Hybrid Runbook Workers
Content Source: articles/automation/automation-remove-hrw.md
Service: automation
GitHub Login: @georgewallace
Microsoft Alias: gwallace

@kylecweeks Thanks for bringing this to our attention. Your feedback has been shared with the content owner for further review.

@kylecweeks Thanks for bringing this to our attention. I have on my backlog the work to get Linux Hybrid worker docs on parity with the Windows hybrid worker docs.  I plan on adding this to the removal doc though in the time being as that is a quick fix.. I will post the updated doc link when it is live.

@kylecweeks This is now live here https://docs.microsoft.com/en-us/azure/automation/automation-hybrid-runbook-worker.  Thanks for bringing this to our attention.. #please-close

@kylecweeks We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


gpt4o、4o-0513回答资讯类问题时会把会把search信息打印出来，而且提问是中文，回答是英文

版本：2.17.7
提问：最新资讯
回答：
search("latest news May 20 2024")mclick(["4", "5", "7", "15", "19"])
Here are some of the latest updates as of May 20, 2024:
International News:
A helicopter crash involving Iranian President Ebrahim Raisi has been reported. The incident occurred near the Azerbaijan border during a dam inauguration project. Investigations are ongoing to determine the cause and the extent of injuries sustained by those on board【6†source】.
In Ukraine, Russian attacks on the Kharkiv region have resulted in at least 11 fatalities. The conflict continues to escalate, impacting civilian areas and causing significant casualties【6†source】.
US Politics:
The 2024 US presidential election is heating up with debates being scheduled between President Joe Biden and former President Donald Trump. The first debate is set to take place on June 27 in Atlanta, Georgia. Additionally, RFK Jr. is actively working to secure ballot access for his campaign【7†source】.
The Supreme Court has recently cleared the way for Louisiana to implement a congressional map with two districts designed to enhance representation for Black voters. This ruling is seen as a potential boost for Democratic candidates in the upcoming elections【7†source】.
Education:
In India, the Central Board of Secondary Education (CBSE) is expected to release the results for Class 10 and 12 examinations shortly after May 20, 2024. Around 39 lakh students are awaiting these results, which will be available on several official websites such as cbseresults.nic.in and digilocker.gov.in【8†source】.
Sports:
Manchester City has clinched their fourth Premier League title, continuing their dominance in English football. Despite Arsenal's victory, Manchester City's lead in the standings secured their championship【6†source】.
The 2024 Indian Premier League (IPL) is in full swing, with live updates and scores available on the official IPL website. Fans are eagerly following the matches as the tournament progresses towards the finals【8†source】.
For more detailed updates and to follow these stories, you can visit news platforms like Al Jazeera, Politico, and Hindustan Times.

请用中文回答

显示这个search("latest news May 20 2024")mclick(["4", "5", "7", "15", "19"])是预期之内的吗

不清楚啊

额，我现在复现不出那些现象了，现在都是按官方的cut off来回答问题了，试了好几个资讯类问题都一样。您已经修复了？

是的 我修复了？
你相信么？ 我有这么厉害就好了 ^_^

现在确实没问题了，之前问它小米汽车最新情况，它肯定要search("latest news May 20 2024")mclick(["4", "5", "7", "15", "19"])之类的，现在它就按2023-10月的日期回答。还有很多类似的情况。别装了，你就是repair之神。


TypeError: Class extends value undefined is not a constructor or null

The reason for the error is that when the version of mini-css-extract-plugin is greater than 1.3.5, when speed-measure-webpack-plugin is used, the title error will be reported
webpack version: 5.27.2
webpack-cli version: 4.5.0
speed-measure-webpack-plugin version: 1.3.1
mini-css-extract-plugin version:  >1.3.5
Modify the version of mini-css-extract-plugin to 1.3.5 to solve the problem

Modify the version of mini-css-extract-plugin to 1.3.5 to solve the problem

+1 same issue

Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
Error: You forgot to add 'mini-css-extract-plugin' plugin (i.e. `{ plugins: [new MiniCssExtractPlugin()] }`), please read https://github.com/webpack-contrib/mini-css-extract-plugin#getting-started
    at Object.pitch (/Users/xxxx/node_modules/mini-css-extract-plugin/dist/loader.js:50:14)


Issue with the JVM DLL

Hello,
I am running into an issue with JVM and wanted to see if there was someone else who ran into the issue. I am trying to use straindesign in a python3.9 application. As the install instructions mentioned -- I did receive this error:
JVMNotFoundException: No JVM shared library file (libjli.dylib) found. Try setting up the JAVA_HOME environment variable.
Turns out I did not have Java JDK installed on my Macbook Pro. So I installed JDK 19. And then set the environment variable as suggested in the straindesign docs.
However, even though it is now able to locate the JVM shared library file, it is erroring saying the JVM DLL is not found.
[Errno 0] JVM DLL not found: /Library/Java/JavaVirtualMachines/jdk-19.jdk/Contents/Home/lib/libjli.dylib
I have tried installing JDK 17 as well with the same error.

Thanks @VonAlphaBisZulu I had seen this issue but thought I would ask here whether there was a more straight forward fix. Though, it does seem to have the answer in that open issue.
Essentially, If you are running an M1 chip -- even though the ARM version of JDK is made for the M1 chip -- seems there is compatibility issues with JPype /Python. Once I installed the the x86 build of JDK (my computer complained that it was suboptimal and there may be issues), I stopped getting the error.

Thank you for sharing the fix!


Donate

How can I donate i don't see a link or etc.

When you open the application and before you login with your account there's a donate option.

Thanks


Add third party lib 'Clipper2' as additional lib

Clipper
Upstream: https://sourceforge.net/projects/polyclipping/files/
Clipper2
https://github.com/AngusJohnson/Clipper2

For backwarsd compatibility with Clipper maybe its better to add Clipper2?
I can add the Clipper2 lib without removing Clipper1 (Clipper 6.4.2) as first step.
@halx99 what are you think?

Does the v2 API break v1, if not, I think just replace it is better

Yes v2  beak the v1 API.
Also v1 will no longer supported

The clipper only used at file: https://github.com/axys1/axys/blob/dev/core/2d/CCAutoPolygon.cpp#L33, so maybe we can just replace it

We can replace it later. First i want  to understand V2 and want comparing with v1.

But in PR #814  you just add clipper2, not use it in engine code

Yes. I want understand v2 first.
I want  write axys::Clipper class for direct using and test-cpp examples also.
Adding the V2 lib is the first step.

Wouldn't it be better to add the clipper V2 to a local project rather than the engine while you're testing it out? It feels a little pointless to add it to the engine if it's not actually going to be used yet.  If it works, then just replace Clipper v1 with it directly, rather than adding them side-by-side.

The clipper only used at file: https://github.com/axys1/axys/blob/dev/core/2d/CCAutoPolygon.cpp#L33, so maybe we can just replace it

@halx99 ,
I checked all SpritePolygon tests.
I removed the Clipper1 stuff and it seems its faster without using the Clipper1 lib and works also.
=> Add some checks (check size and used time with and without Clipper1 lib )
PolygonInfo AutoPolygon::generateTriangles(const Rect& rect, float epsilon, float threshold)
{

    AXLOG("PolygonInfo AutoPolygon::generateTriangles");
    Rect realRect = getRealRect(rect);
    auto p        = trace(realRect, threshold);
    AXLOG("trace: %i ", p.size());
    p             = reduce(p, realRect, epsilon);
    clock_t start = clock();
    AXLOG("reduce: %i %i", p.size(), start);
    p             = expand(p, realRect, epsilon);   // ###  check time and size of p (with and without (comment this line))
    AXLOG("expand: %i %i", p.size(), clock() - start);
    auto tri      = triangulate(p);
    calculateUV(realRect, tri.verts, tri.vertCount);
    PolygonInfo ret;
    ret.triangles = tri;
    ret.setFilename(_filename);
    ret.setRect(realRect);
    return ret;
}

My probosal:
Remove the Clippper1 lib function from AutoPolygon::generateTriangles():   p             = expand(p, realRect, epsilon);
Replace Clipper1 with Clipper2.
@halx99: What are you mean?

Do replace please.

Will add it later.
I will doing some more tests first


[IOTDB-2383] Make simplified SQL of creating timeseries and schema template more flexible

In this PR, I make simplified SQL of creating time-series and schema templates more flexible to improve fault tolerance for users.
Now, we can use SQL:
create timeseries root.sg1.d1.s1 with datatype = INT64, encoding = RLE
create timeseries root.sg1.d1.s1 with datatype = INT64 encoding = RLE
create timeseries root.sg1.d1.s1 datatype = INT64 encoding = RLE
create timeseries root.sg1.d1.s1 with INT64 encoding = RLE
create timeseries root.sg1.d1.s1 INT64 encoding = RLE   // recommend

Coverage increased (+0.04%) to 68.095% when pulling e0004d7f7780f146b57d15579d7bc72caee98c17 on liuminghui233:more_sql into 2f49925eb06055e85bc2495838783b01d6dc192b on apache:master.


Steps: tar, contextclear, contextclearall. Errs: KeyNotInContext, KeyInContextHasNoValue

KeyNotInContextError and KeyInContextHasNoValueError added. Refactor throughout to use new errs rather than KeyError.

NB: henceforth, Context throws KeyNotInContextError, not KeyError, on __ missing __

echoMe refactor to deal more sensibly with non-str types
py.step had unreachable code, removed.
new steps:

tar
contextclear
contextclearall

stepsrunner had unreachable code (steps can't re-assign context to None due to python call-by-obj param passing)
bug fixes for format strings missing f""
bug fix: complex steps exploded if didn't have the optional "in" context specified.
100% test coverage as of now

I can't see a version bump on this one.  Is that because it's not to be published as it is?

I figured 1st see what shakes out of the code review before version bumping, since it was a big one 😀 at least the version bump review will be a simple one...


Update logs-dedicated-clusters.md

To update the billing type of cluster the location property is also needed:

@yadavdilip19 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

I re-validated and it works per current description.
I don't see a need for change at this point.

@yadavdilip19 Please see the author's feedback on your proposed update. Thanks.

Update was made to article
#close

#please-close


CPR-70-data model

. Added data model classes required to process hmcts SQS messages.

Looks good, and only have a couple of suggestions:
* create an hmcts package to give :
  ...personrecord.model.hmcts.commonplatform and:
  ...personrecord.model.hmcts.libra

* remove the 'CP' prefix from the common platform classes as the package name already specifies this

* As a result of above, add the appropriate @JSON... annotation to specifiy the Pojo name

I also thought the same about the 'CP' prefix and am happy to discuss the suggestions.


Support serializing packed tables directly for the normal shuffle path

Contribute to https://github.com/NVIDIA/spark-rapids/issues/10790
This PR is trying to accelerate the normal shuffle path by partitioning and slicing tables on GPU.
The sliced table is already serializable so can be written to the Shuffle output stream directly, along with a lightweight metadata (a TableMeta) to rebuild the table on the Shuffle read side.
On the Shuffle read side, the new introduced PackedTableIterator will read the tables from the Shuffle input stream and rebuild them on GPU by leveraging the existing utils (MetaUtils, GpuCompressedColumnVector). Next, the existing GpuCoalesceBatches node is used to do the batch concatenation for the downstream operators, similar as what Rapids Shuffle does.
At least , we got about 2x speedup for a customer query on our dev cluster.
No new tests because the existing hash_aggregate_test and join_test will run into this new feature and verify its functionality.
TODO

NDS numerbs on Spark2a

Make it draft because there are still 5 unit tests failing.

WAR the failing tests by disabling the GPU serde, and filed an issue (https://github.com/NVIDIA/spark-rapids/issues/10823) to track the follow-up

build

build

build

build

It led to some perf degression in NDS runs, so disable this feature by default.

Which queries were slower? It would be great to get some feedback from you on what is different between the customer query and the NDS queries.
Also which queries got faster from NDS? That would be interesting.
I did also write internally as I'd like to see more standard configurations used for this benchmark on the next run, so we can compare apples-to-apples with our baseline.

build

Please add more context about why the test cases in #10823 are failing before merging this PR.  We'd like to understand if that issue needs to be addressed as part of this PR.

Please add more context about why the test cases in https://github.com/NVIDIA/spark-rapids/issues/10823 are failing before merging this PR. We'd like to understand if that issue needs to be addressed as part of this PR.

Done

build

Move to draft since the perf is not as good as our expectation.

@winningsix  I am going to close this since we fail to get a case that can benefit from it. And we can reopen it if we find one in the future.


How Do I figure out which vm to clone?

I have the following error when trying to create a vm from the test terraform script:

proxmox_vm_qemu.cloudinit-test: 1 error(s) occurred:

proxmox_vm_qemu.cloudinit-test: Vm 'debiantemplate' not found

proxmox_vm_qemu.prepprovision-test: 1 error(s) occurred:

proxmox_vm_qemu.prepprovision-test: Vm 'debiantemplate' not found

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.
Here is my info

Vm Name
Vm Number
Storage Location
vm type

debiantemplate
103
Local-lvm
Template

So for the 'template' name I used the vm name debiantemplate. What is the correct reference? Is I the 'disk id' of:
base-103-disk-0?
I created a cloud-init vm (works fine with cloud init from ux) named debiantemplate, converted it to a 'template'. I can hit 'clone' and system happily creates a new one. How do I figure out the correct template name?

again I will write up an answer and put in the 'docs' section.


[bug] non-optional component properties not satisfied by SLFunctionComponent<{}>

Describe the bug
Taking the docs package as example, when changing a property of the LinkableBtnProps interface to required e.g. primary:
export type LinkableBtnProps = {
  isActive?: boolean
  href?: string
  target?: string
  hoverable?: boolean
  primary: boolean // non-optional
} & HTMLAttributes<HTMLButtonElement | HTMLAnchorElement>

IDE is throwing two type errors:

First error:
Related to tsconfig.json the strictFunctionTypes option is set to true:
type StoryType = Story<typeof LinkableBtn> // typeof LinkableBtn error

Type '({ className, isActive, primary, hoverable, children, href, target, ...rest }: LinkableBtnProps) => Element' does not satisfy the constraint 'SLFunctionComponent<{}>'.
  Types of parameters '__0' and 'props' are incompatible.
    Type '{}' is not assignable to type 'LinkableBtnProps'.
      Property 'primary' is missing in type '{}' but required in type '{ isActive?: boolean | undefined; href?: string | undefined; target?: string | undefined; hoverable?: boolean | undefined; primary: boolean; }'.ts(2344)
LinkableBtn.tsx(8, 3): 'primary' is declared here.

Second error:
<Story {...context?.args} /> // Story error

Property 'primary' is missing in type '{}' but required in type '{ isActive?: boolean | undefined; href?: string | undefined; target?: string | undefined; hoverable?: boolean | undefined; primary: boolean; }'.ts(2741)
LinkableBtn.tsx(8, 3): 'primary' is declared here.

⚠ Error (TS2741)  |
Property 'primary'   is missing in type {} but required in type:
.
(parameter) Story: ({ className, isActive, primary, hoverable, children, href, target, ...rest }: LinkableBtnProps) => JSX.Element

Reproduction

Clone the repo
Run pnpm i
Change LinkableBtnProps primary property to required
Open buttons.stories.tsx and see the error

Environment

OS with version: Windows 11
Browser with version: Firefox 117.0.1
JS Runtime with version: NodeJS v20.2.0

this PR might fix this issue #75

I tested PR #75 by making react example component property in ForwardRefButton.tsx variant and in LinkableBtn.tsx primary non-optional, but the issue still persists.


Doris manager interface failed to install new Doris cluster

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
os version: oracle linux 8
doris: 2.0.2
doris-manager: 23.9.2
What's Wrong?
Guess it was when adding the crontab task, replacing the installation directory with the IP address of the webserver caused the addition of the crontab to fail
There is also this error when installing the Doris standalone version
集群部署失败，请尝试修改节点、集群配置并重新部署。 failed to add crontab for webui node <IP_ADDRESS>, stdout: , stderr: + DEPLOY_DIR=<IP_ADDRESS> + CLUSTER_NAME=cluster-478286445330437 + cat bash: line 9: <IP_ADDRESS>/.webui_cluster-478286445330437_cron.sh: No such file or directory + chmod +x <IP_ADDRESS>/.webui_cluster-478286445330437_cron.sh chmod: cannot access '<IP_ADDRESS>/.webui_cluster-478286445330437_cron.sh': No such file or directory + grep -q webui_cluster-478286445330437 + crontab -l + crontab -l + crontab - + echo '*/1 * * * * <IP_ADDRESS>/.webui_cluster-478286445330437_cron.sh' "-":1: bad minute errors in crontab file, can't install. , err: run cmd ` #!/bin/bash set -o pipefail set -x DEPLOY_DIR=""<IP_ADDRESS>"" CLUSTER_NAME=""cluster-478286445330437"" # direct overwrite cat > "${DEPLOY_DIR}/.webui_${CLUSTER_NAME}_cron.sh" << EOF #!/bin/bash WEBUI_PID_FILE="${DEPLOY_DIR}/bin/webui.pid" if [ -e "\${WEBUI_PID_FILE}" ]; then pid=\$(cat "\${WEBUI_PID_FILE}") kill -0 "\$pid" if [ \$? -eq 0 ]; then

What You Expected?
Successfully deployed Doris cluster
How to Reproduce?
No response
Anything Else?
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

add my wechat: Faith_xzc


Jameswtruher/testgapfill1

additional cmdlet tests to fill some test gaps

@JamesWTruher, I need you to push a change to re-trigger the CI system.

This fork is having trouble with permissions - I'll replicate this PR from a different fork


Set up S3 permissions scope for internal only resources

Type of Issue
Select the type of issue:

[ ] Bug report (to report a bug)
[ ] Feature request (to request an additional feature)
[x] Tracker (I am just using this as a tracker)
[ ] Refactor request
[ ] Documentation Ask

Description
One way to do this is to tag objects as internal and give IAM users permissions to access. See
https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-tagging.html
Current Behavior
craftassist/pubr bucket is set to ACL public read.
Checklist

[ ] Create internal scope
[ ] Authorize relevant IAM users
[ ] Categorize documents
[ ] Look into tagging models/dataset versions as latest and updating fetch/deploy scripts

cc @aszlam , @kavyasrinet


Authentication is not working

Hi
Only the super user can login the normal user is not able to login and throwing the error:
HTTP 400 Bad Request
Allow: POST, OPTIONS
Content-Type: application/json
Vary: Accept
{
"non_field_errors": [
"Unable to login with provided credentials."
]
}
Please have a look.

Did you add the google API credentials to settings?


Do I need to call registerPlugin(FirebaseAnalytics.class); in Capacitor V3 Version?

It seems like the call to register the plugin when using Capacitor V3 is missing from the documentation.
Maybe I'm wrong, but isn't this required in your MainActivity.java?
  public void onCreate(Bundle savedInstanceState) {
    setOrientation(this);
    super.onCreate(savedInstanceState);

    // Custom plugin registration
    registerPlugin(FirebaseAnalytics.class);
  }

Nope, this is no longer necessary. See https://capacitorjs.com/docs/updating/3-0#switch-to-automatic-android-plugin-loading


⚠ Turnos 24x7 has degraded performance

In 853309e, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 3314 ms

Resolved: Turnos 24x7 performance has improved in 86bc2ab.


Afffix functio is not ther in 4

Before opening an issue:

Search for duplicate or closed issues
Validate and lint any HTML to avoid common problems
Prepare a reduced test case for any bugs
Read the contributing guidelines

When asking general "how to" questions:

Please do not open an issue here
Instead, ask for help on StackOverflow, IRC, or Slack

When reporting a bug, include:

Operating system and version (Windows, Mac OS X, Android, iOS, Win10 Mobile)
Browser and version (Chrome, Firefox, Safari, IE, MS Edge, Opera 15+, Android Browser)
Reduced test cases and potential fixes using CodePen or JS Bin

When suggesting a feature, include:

As much detail as possible for what we should add and why it's important to Bootstrap
Relevant links to prior art, screenshots, or live demos whenever possible

We removed the affix plugin long ago. Details are in the v4 migration guide on our docs.

duplicate of #24704


Handle filename collisions in validation

Linux filesystems are case-sensitive, but Windows filesystems are not, and the SBOM validator follows the case sensitivity of whichever filesystem it runs on. As a result, if an SBOM is generated on Linux and contains files called, for example, filename and FileName, and we attempt to validate that SBOM on Windows, the validator tool sees the same filename twice with different hashes.
Currently if this happens, we add null to a dictionary of file hashes, but since we do not check for null when that dictionary is used, the user sees the message Object reference not set to an instance of an object, which doesn't give any clues about what happened.
When this happens, we should output a more meaningful error, ideally one prompting the user to make sure the validator runs on the same OS that the SBOM was generated on.

This has been merged to main and will be included in our next release


Changing the css of login page

Is your feature request related to a problem? Please describe.
No, it's a suggestion.
Describe the solution you'd like
I want to change css for this.
Are you willing to contribute to this issue? [Yes/No]
Yes
Additional context

Hi @kanisshka Could you elaborate and update the PR Description? Something like this #30
Preferrably Some answers to questions like What do you intend to make it into?
What & Which css you want to change?

Hi @kanisshka Could you elaborate and update the PR Description? Something like this #30
Preferrably Some answers to questions like What do you intend to make it into?
What & Which css you want to change?

Just like first, I want to make an 'OR' line between sign in and sign in with google.
secondly wanted to change some layout or some appearance of this page.

I don't think we need an OR rn, layout and appearance as in? Could you show an example

I don't think we need an OR rn, layout and appearance as in? Could you show an example

Like this....


libmysqlconnectorcpp: 8.4.0 -> 9.0.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/mysql-connector-c++/versions.
meta.description for libmysqlconnectorcpp is: C++ library for connecting to mysql servers
meta.homepage for libmysqlconnectorcpp is: https://dev.mysql.com/downloads/connector/cpp/
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 9.0.0 with grep in /nix/store/ajj41mpqrxv60d8wg3xw4dl33xls3xl7-libmysqlconnectorcpp-9.0.0
found 9.0.0 in filename of file in /nix/store/ajj41mpqrxv60d8wg3xw4dl33xls3xl7-libmysqlconnectorcpp-9.0.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

libmysqlconnectorcpp
mysql-workbench

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ajj41mpqrxv60d8wg3xw4dl33xls3xl7-libmysqlconnectorcpp-9.0.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libmysqlconnectorcpp https://github.com/r-ryantm/nixpkgs/archive/b63f62510f7b573a6f712ce7df5e21921cd2cdc7.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/b63f62510f7b573a6f712ce7df5e21921cd2cdc7#libmysqlconnectorcpp

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ajj41mpqrxv60d8wg3xw4dl33xls3xl7-libmysqlconnectorcpp-9.0.0
ls -la /nix/store/ajj41mpqrxv60d8wg3xw4dl33xls3xl7-libmysqlconnectorcpp-9.0.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

libmysqlconnectorcpp
mysql-workbench

Maintainer pings

Result of nixpkgs-review pr 332375 run on x86_64-darwin 1

1 package built:

libmysqlconnectorcpp


dircolors: fix enableZshIntegration with zsh.oh-my-zsh

Description
Fix #1279
Checklist

[x] Code formatted with ./format.

[x] Code tested through nix-shell --pure tests -A run.all.

[ ] Test cases updated/added. See example.

[x] Commit messages are formatted like
{component}: {description}

{long description}

See CONTRIBUTING for more information and recent commit messages for examples.

Thanks! Rebased to master in 3a80ece9fa0de388ad27503059f7856c9315d491.


36 inventory argument

Added ANSIBLE_INVENTORY to work like HERBERT_BRANCH.

@terryg just checking in, any reason not to merge this? It looks good to me

I wasn't allowed to merge at one point, and then forgot about it! I found a workaround too, which might be better. Symbolic link to an inventory file. ??


fix the evaluation

Assume label = 0 corresponds to negative label because it seems people also tend to use 0 as negative label. Without the fix, we are not counting true negatives for label=0
@hectorgon

LGTM

LGTM


Cache AllOutX volume

There is no reason to create a new volume every time we use AllOutXEnsemble.can_append etc.

This is ready for review and comment. I will leave it open for at least 24 hours, merging no earlier than Thu 18 Feb 17:00 GMT (18:00 local).

looks fine by me, what was the issue that was solved in commit https://github.com/openpathsampling/openpathsampling/pull/975/commits/4b0da5fcb6f444447a81acdec5ce0a08177f9caa ? (just interested, don't block this PR on that question)

what was the issue that was solved in commit 4b0da5f ?

Codecov complained and then didn't report coverage. Image below (since GH Actions doesn't archive logs long term).


Added specifics on EF7 (Core)

@luisgmsft,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/best-practices/retry-service-specific.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/mspnp/architecture-center, working directory: W:\wn30-s, target branch: master, target branch commit: 18316603c89093b00dbd501127e42f914b3327c9, source branch: 9c4f9dbcf81ea52d79d0d7e43ae5f930/retry-specifics-guidance/entity-framework-netcore, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/best-practices/retry-service-specific.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/best-practices/retry-service-specific.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/best-practices/retry-service-specific.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Is there a way to add events in week view?

What will be the view if events are added in week view as shown in example 1.

Same as the month view, the logic to add events does not depend on if the calendar is in month or week view.


azure/WithErrorUnlessStatusCode: fixing a panic when the response is a literal value null

Thank you for your contribution to Go-AutoRest! We will triage and review it as soon as we can.
As part of submitting, please make sure you can make the following assertions:

[x] I've tested my changes, adding unit tests if applicable.
[x] I've added Apache 2.0 Headers to the top of any new source files.

This commit fixes a panic within WithErrorUnlessStatusCode when the response returns a literal value of null:
:status: 202
cache-control: no-cache
pragma: no-cache
content-length: 4
content-type: application/json; charset=utf-8
expires: -1
location: https://management.azure.com/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/acctestRG-la-210108080034968174/providers/Microsoft.OperationalInsights/clusters/acctest-LA-210108080034968174/operationresults/00000000-0000-0000-0000-000000000000?api-version=2020-08-01
azure-asyncoperation: https://management.azure.com/subscriptions/00000000-0000-0000-0000-000000000000/providers/Microsoft.OperationalInsights/locations/westeurope/operationStatuses/00000000-0000-0000-0000-000000000000?api-version=2015-11-01-preview
x-ams-apiversion: WebAPI1.0
cachecontrol: no-cache
x-ms-request-id: 00000000-0000-0000-0000-000000000000
strict-transport-security: max-age=31536000; includeSubDomains
x-content-type-options: nosniff
server: Microsoft-IIS/10.0
server: Microsoft-IIS/10.0
x-powered-by: ASP.NET
x-powered-by: ASP.NET
x-ms-ratelimit-remaining-subscription-writes: 1199
x-ms-correlation-request-id: 00000000-0000-0000-0000-000000000000
x-ms-routing-request-id: UKWEST:20210108T103620Z:00000000-0000-0000-0000-000000000000
date: Fri, 08 Jan 2021 10:36:19 GMT
null

Where this panics when calling the nil e.ServiceError when accessing e.ServiceError.Message:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x7d1542]

goroutine 1516 [running]:
github.com/Azure/go-autorest/autorest/azure.WithErrorUnlessStatusCode.func1.1(0xc001a45170, 0x0, 0x0)
  /var/lib/teamcity/go/1.15.5/pkg/mod/github.com/!azure/go-autorest/autorest@v0.11.10/azure/azure.go:308 +0x4c2
github.com/Azure/go-autorest/autorest.ResponderFunc.Respond(0xc00130b020, 0xc001a45170, 0x203000, 0xc0013ccd48)
  /var/lib/teamcity/go/1.15.5/pkg/mod/github.com/!azure/go-autorest/autorest@v0.11.10/responder.go:41 +0x30
github.com/Azure/go-autorest/autorest.ByUnmarshallingJSON.func1.1(0xc001a45170, 0xc0013cce30, 0x7c53cd)
  /var/lib/teamcity/go/1.15.5/pkg/mod/github.com/!azure/go-autorest/autorest@v0.11.10/responder.go:180 +0x63
github.com/Azure/go-autorest/autorest.ResponderFunc.Respond(0xc00130b1d0, 0xc001a45170, 0x5ad9080, 0xc00130b1d0)
  /var/lib/teamcity/go/1.15.5/pkg/mod/github.com/!azure/go-autorest/autorest@v0.11.10/responder.go:41 +0x30
github.com/Azure/go-autorest/autorest.ByClosing.func1.1(0xc001a45170, 0x5ad9080, 0xc001556380)
  /var/lib/teamcity/go/1.15.5/pkg/mod/github.com/!azure/go-autorest/autorest@v0.11.10/responder.go:129 +0x3d
github.com/Azure/go-autorest/autorest.ResponderFunc.Respond(0xc001556380, 0xc001a45170, 0x3, 0x5ad9080)
  /var/lib/teamcity/go/1.15.5/pkg/mod/github.com/!azure/go-autorest/autorest@v0.11.10/responder.go:41 +0x30
github.com/Azure/go-autorest/autorest.Respond(0xc001a45170, 0xc0013ccf40, 0x3, 0x3, 0xc00012eb00, 0xc0013ccf50)
  /var/lib/teamcity/go/1.15.5/pkg/mod/github.com/!azure/go-autorest/autorest@v0.11.10/responder.go:78 +0x6b
github.com/Azure/azure-sdk-for-go/services/operationalinsights/mgmt/2020-08-01/operationalinsights.ClustersClient.UpdateResponder(0x5ad42c0, 0xc000e14840, 0x5ad90a0, 0xc0028f39b0, 0xc0028f3a10, 0x0, 0xdf8475800, 0xd18c2e2800, 0x3, 0x6fc23ac00, ...)
  /var/lib/teamcity/go/1.15.5/pkg/mod/github.com/!azure/azure-sdk-for-go@v49.2.0+incompatible/services/operationalinsights/mgmt/2020-08-01/operationalinsights/clusters.go:632 +0x105
github.com/Azure/azure-sdk-for-go/services/operationalinsights/mgmt/2020-08-01/operationalinsights.ClustersClient.Update(0x5ad42c0, 0xc000e14840, 0x5ad90a0, 0xc0028f39b0, 0xc0028f3a10, 0x0, 0xdf8475800, 0xd18c2e2800, 0x3, 0x6fc23ac00, ...)
  /var/lib/teamcity/go/1.15.5/pkg/mod/github.com/!azure/azure-sdk-for-go@v49.2.0+incompatible/services/operationalinsights/mgmt/2020-08-01/operationalinsights/clusters.go:591 +0x8e5

As such this commit checks to confirm if e.ServiceError is nil - then assigns an "unknown error" response with the response body if possible.
Without this change, the tests fail:
$ go test -v ./autorest/azure -run=TestWithErrorUnlessStatusCode_ -count=1
=== RUN   TestWithErrorUnlessStatusCode_NotAnAzureError
--- PASS: TestWithErrorUnlessStatusCode_NotAnAzureError (0.00s)
=== RUN   TestWithErrorUnlessStatusCode_FoundAzureErrorWithoutDetails
--- PASS: TestWithErrorUnlessStatusCode_FoundAzureErrorWithoutDetails (0.00s)
=== RUN   TestWithErrorUnlessStatusCode_FoundAzureFullError
--- PASS: TestWithErrorUnlessStatusCode_FoundAzureFullError (0.00s)
=== RUN   TestWithErrorUnlessStatusCode_LiteralNullValueInResponse
    azure_test.go:348: azure: service error is not unmarshaled properly. expected="Code=\"Unknown\" Message=\"Unknown service error\" Details=[{\"HttpResponse.Body\":\"null\"}]"
        got=<nil>
--- FAIL: TestWithErrorUnlessStatusCode_LiteralNullValueInResponse (0.00s)
=== RUN   TestWithErrorUnlessStatusCode_NoAzureError
--- PASS: TestWithErrorUnlessStatusCode_NoAzureError (0.00s)
=== RUN   TestWithErrorUnlessStatusCode_UnwrappedError
--- PASS: TestWithErrorUnlessStatusCode_UnwrappedError (0.00s)
FAIL
FAIL	github.com/Azure/go-autorest/autorest/azure	0.012s
FAIL

With this change, the tests pass:
$ go test -v ./autorest/azure -run=TestWithErrorUnlessStatusCode_ -count=1
=== RUN   TestWithErrorUnlessStatusCode_NotAnAzureError
--- PASS: TestWithErrorUnlessStatusCode_NotAnAzureError (0.00s)
=== RUN   TestWithErrorUnlessStatusCode_FoundAzureErrorWithoutDetails
--- PASS: TestWithErrorUnlessStatusCode_FoundAzureErrorWithoutDetails (0.00s)
=== RUN   TestWithErrorUnlessStatusCode_FoundAzureFullError
--- PASS: TestWithErrorUnlessStatusCode_FoundAzureFullError (0.00s)
=== RUN   TestWithErrorUnlessStatusCode_LiteralNullValueInResponse
--- PASS: TestWithErrorUnlessStatusCode_LiteralNullValueInResponse (0.00s)
=== RUN   TestWithErrorUnlessStatusCode_NoAzureError
--- PASS: TestWithErrorUnlessStatusCode_NoAzureError (0.00s)
=== RUN   TestWithErrorUnlessStatusCode_UnwrappedError
--- PASS: TestWithErrorUnlessStatusCode_UnwrappedError (0.00s)
PASS
ok  	github.com/Azure/go-autorest/autorest/azure	0.011s

Upstream API issue: https://github.com/Azure/azure-rest-api-specs/issues/12331

Upstream API issue: https://github.com/Azure/azure-rest-api-specs/issues/12331

I can't see why the tests are failing for this since I don't have permission to login to this section of Azure DevOps... 🙃

I think this is failing due to the time-of-day that particular test is being run, but I can't see the test output to confirm.

I can't see why the tests are failing for this since I don't have permission to login to this section of Azure DevOps... 🙃

I think this is failing due to the time-of-day that particular test is being run, but I can't see the test output to confirm.

This part of the UI is confusing.  From where you're at, if you click the arrow to take you back to the summary section, you need to click on the Tests "tab" (between Summary and Scans) to see the test results.
I believe you're correct.  This line is at fault.
https://github.com/Azure/go-autorest/blob/master/autorest/adal/token_test.go#L94

This part of the UI is confusing.  From where you're at, if you click the arrow to take you back to the summary section, you need to click on the Tests "tab" (between Summary and Scans) to see the test results.
I believe you're correct.  This line is at fault.
https://github.com/Azure/go-autorest/blob/master/autorest/adal/token_test.go#L94


ASM-4404 Create_nfs_export

NFS export operation fails intermittently when the export configuration is modified. This happens during the server scale-up operation from ASM
The IP Address of the newly added server is updated in the export file but due to sync issue, this error is reported by ONTAP API.
No resolution for this is suggested in the NetApp KB Articles, but based on the observation so far, removing the extra invocation as this is not solving the problem but instead leading to the failure of the ASM deployment where scale-up operation is performed

DO NOT MERGE. Still testing

@aimers1975 PR is ready to be merged.

@aimers1975 :+1:


Team 4   general mobs

Added projectiles, and currency to the mobs. Also created an atlas for all xeno images, added waves of mobs spawning.

Sorry guys, I'm in studio 1 - I think you might have mixed me up with someone else.


Loop over Hail service accounts to reduce code duplication

No functional change.

The access level to service_account list is pretty frequently accessed, you might consider refactoring this as:
access_levels = {
    'test': hail_service_account_test,
    'standard': hail_service_account_standard,
    'full': hail_service_account_full)
}

for access_level, service_account in access_levels.items():
    pass

Not super relevant for this PR, but I think a worthwhile refactor at some point.

Great Idea! I'll send a follow-up.


Add bottomSheetHeight property to countryListThemeData.

Pull request to add functionality of user to decide how tall the country list will be.

Nice...thanks...I guess it needs to be added to flutter_currency_picker which uses same code...if Daniel doesnt do it i will later do a PR too

@janar265 , i cannot see your latest message...but i guess 1/3, 2/3 size constant would be great... or something like adjustable height from few elements until a specific max height of 1/3 or 2/3 ( cause if you have 1 single or 2 elements, you expect a flexible height)

Released in v2.0.13


PDI-11089 Cannot sort preview data (NullPointerException )

It doesn't look like this commit follows the formatting requirements.

Closing pull request due to inactivity.


No more jsonpatch format for extensions ?

Hi @timgdavies
Sorry probably you guys discussed this inside some of the tickets here but probably i missed it. For OCDS 1.0 i was used to applying the extension via http://jsonpatch.com/ format, like the one here
I had integrated the json-patch library so that we can easily apply multiple json patches over the original 1.0 schema without changing/altering the json schema itself, this worked pretty well for us in 1.0. We used this for the location extension proposed by you.
We are now in the process of upgrading to 1.1 and re-assessing some of the official schema extensions. Do we have some new guidelines about applying extensions over the 1.1 schema ?

@mpostelnicu Yes - this was discussed in https://github.com/open-contracting/standard/issues/335 where the new approach uses json-merge-patch rather than json-patch  - it should be fairly easy to switch in merge-patch format instead.

great. thanks. closing!


Update setup.py

where is fontPens used in defcon?

where is fontPens used in defcon?

In the PR I opened.

the FlattenPen, I see... :thinking:
I don't know. I wish we could avoid adding a new required installation requirement (which for me, means an additional requirement to fontmake).
What about moving the import inside contourFlattenedRepresentationFactory (is that misspelled without a y?)?
So fontPens would only be required if one calls the method to correct the contour directions.
We could have an "extras_require" in the setup.py (e.g. called "pens"), so that one could do pip install defcon[pens] and get the extra requirement, in this case fontPens...

Sounds good. Will close this.


multi-network: gateways filter out endpoints for other gateways

This should prevent scenarios in multi-network where a gateway sends traffic back to another gateway. It probably won't solve the problem of having equal traffic distribution. For multiple clusters in a network that each have their own gateway.
fixes https://github.com/istio/istio/issues/26293
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

/test integ-pilot-multicluster-tests_istio

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

Test name
Commit
Details
Rerun command

lint_istio
743c24b43e940f301c68dc3f789b45ea7c69b76b
link
/test lint_istio

gencheck_istio
743c24b43e940f301c68dc3f789b45ea7c69b76b
link
/test gencheck_istio

integ-multicluster-k8s-tests_istio
743c24b43e940f301c68dc3f789b45ea7c69b76b
link
/test integ-multicluster-k8s-tests_istio

release-notes_istio
9a8310667769c9bd1435cf617ada8214e91b14e9
link
/test release-notes_istio

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

/test release-notes_istio

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

Test name
Commit
Details
Rerun command

gencheck_istio
743c24b43e940f301c68dc3f789b45ea7c69b76b
link
/test gencheck_istio

integ-multicluster-k8s-tests_istio
743c24b43e940f301c68dc3f789b45ea7c69b76b
link
/test integ-multicluster-k8s-tests_istio

release-notes_istio
9a8310667769c9bd1435cf617ada8214e91b14e9
link
/test release-notes_istio

lint_istio
9a8310667769c9bd1435cf617ada8214e91b14e9
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
743c24b43e940f301c68dc3f789b45ea7c69b76b
link
/test integ-multicluster-k8s-tests_istio

lint_istio
9a8310667769c9bd1435cf617ada8214e91b14e9
link
/test lint_istio

gencheck_istio
9a8310667769c9bd1435cf617ada8214e91b14e9
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
9a8310667769c9bd1435cf617ada8214e91b14e9
link
/test gencheck_istio

lint_istio
a9476faa35a4f398a9335e9ea93f9d6bfcc385d0
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
a9476faa35a4f398a9335e9ea93f9d6bfcc385d0
link
/test lint_istio

gencheck_istio
a9476faa35a4f398a9335e9ea93f9d6bfcc385d0
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
a9476faa35a4f398a9335e9ea93f9d6bfcc385d0
link
/test lint_istio

gencheck_istio
a9476faa35a4f398a9335e9ea93f9d6bfcc385d0
link
/test gencheck_istio

integ-pilot-k8s-tests_istio
a9476faa35a4f398a9335e9ea93f9d6bfcc385d0
link
/test integ-pilot-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
a9476faa35a4f398a9335e9ea93f9d6bfcc385d0
link
/test lint_istio

integ-pilot-k8s-tests_istio
a9476faa35a4f398a9335e9ea93f9d6bfcc385d0
link
/test integ-pilot-k8s-tests_istio

gencheck_istio
f046c5eb8b94db461fe47e2dd7fa45dd6dd88f0d
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
a9476faa35a4f398a9335e9ea93f9d6bfcc385d0
link
/test integ-pilot-k8s-tests_istio

gencheck_istio
f046c5eb8b94db461fe47e2dd7fa45dd6dd88f0d
link
/test gencheck_istio

lint_istio
f046c5eb8b94db461fe47e2dd7fa45dd6dd88f0d
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
f046c5eb8b94db461fe47e2dd7fa45dd6dd88f0d
link
/test gencheck_istio

lint_istio
f046c5eb8b94db461fe47e2dd7fa45dd6dd88f0d
link
/test lint_istio

integ-multicluster-k8s-tests_istio
f046c5eb8b94db461fe47e2dd7fa45dd6dd88f0d
link
/test integ-multicluster-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
f046c5eb8b94db461fe47e2dd7fa45dd6dd88f0d
link
/test gencheck_istio

integ-multicluster-k8s-tests_istio
f046c5eb8b94db461fe47e2dd7fa45dd6dd88f0d
link
/test integ-multicluster-k8s-tests_istio

lint_istio
48dfc558cd632f20d15cfa60c665dbe366bce3c7
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
f046c5eb8b94db461fe47e2dd7fa45dd6dd88f0d
link
/test integ-multicluster-k8s-tests_istio

lint_istio
48dfc558cd632f20d15cfa60c665dbe366bce3c7
link
/test lint_istio

gencheck_istio
48dfc558cd632f20d15cfa60c665dbe366bce3c7
link
/test gencheck_istio

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

@stevenctl: PR needs rebase.

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.

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-ipv6-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-ipv6-k8s-tests_istio

analyze-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-ipv6-k8s-tests_istio

analyze-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test analyze-tests_istio

gencheck_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-ipv6-k8s-tests_istio

analyze-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test analyze-tests_istio

gencheck_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test gencheck_istio

integ-security-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-security-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-ipv6-k8s-tests_istio

analyze-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test analyze-tests_istio

gencheck_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test gencheck_istio

integ-security-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-telemetry-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-ipv6-k8s-tests_istio

analyze-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test analyze-tests_istio

gencheck_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test gencheck_istio

integ-security-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-multicluster-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-ipv6-k8s-tests_istio

analyze-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test analyze-tests_istio

gencheck_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test gencheck_istio

integ-security-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-multicluster-k8s-tests_istio

integ-operator-controller-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-operator-controller-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-ipv6-k8s-tests_istio

analyze-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test analyze-tests_istio

gencheck_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test gencheck_istio

integ-security-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-multicluster-k8s-tests_istio

integ-operator-controller-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-operator-controller-tests_istio

release-notes_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-ipv6-k8s-tests_istio

analyze-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test analyze-tests_istio

gencheck_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test gencheck_istio

integ-security-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-multicluster-k8s-tests_istio

integ-operator-controller-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-operator-controller-tests_istio

release-notes_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test release-notes_istio

integ-distroless-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-distroless-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-ipv6-k8s-tests_istio

analyze-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test analyze-tests_istio

gencheck_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test gencheck_istio

integ-security-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-multicluster-k8s-tests_istio

integ-operator-controller-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-operator-controller-tests_istio

release-notes_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test release-notes_istio

integ-distroless-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-pilot-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-ipv6-k8s-tests_istio

analyze-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test analyze-tests_istio

gencheck_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test gencheck_istio

integ-security-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-multicluster-k8s-tests_istio

integ-operator-controller-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-operator-controller-tests_istio

release-notes_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test release-notes_istio

integ-distroless-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-pilot-k8s-tests_istio

lint_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-ipv6-k8s-tests_istio

analyze-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test analyze-tests_istio

gencheck_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test gencheck_istio

integ-security-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-multicluster-k8s-tests_istio

integ-operator-controller-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-operator-controller-tests_istio

release-notes_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test release-notes_istio

integ-distroless-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-pilot-k8s-tests_istio

lint_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test lint_istio

unit-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-ipv6-k8s-tests_istio

analyze-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test analyze-tests_istio

gencheck_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test gencheck_istio

integ-security-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-multicluster-k8s-tests_istio

integ-operator-controller-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-operator-controller-tests_istio

release-notes_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test release-notes_istio

integ-distroless-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-distroless-k8s-tests_istio

integ-pilot-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-pilot-k8s-tests_istio

lint_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test lint_istio

unit-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test unit-tests_istio

release-test_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test release-test_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-telemetry-k8s-tests_istio

integ-pilot-k8s-tests_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test integ-pilot-k8s-tests_istio

release-test_istio
2679800dde355e227c9d9bdb038a2d94d52fa67a
link
/test release-test_istio

integ-multicluster-k8s-tests_istio
fe119230944898de161f81e27b7569479f957840
link
/test integ-multicluster-k8s-tests_istio

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

What about setting ISTIO_META_REQUESTED_NETWORK_VIEW on the gateway in multi-network setups? It looks like it's meant to be used for this purpose, although it's not clear to me that it actually works..

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
4ba309d9570fffc651a3596d7520d1208cdaf1bd
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
4ba309d9570fffc651a3596d7520d1208cdaf1bd
link
/test lint_istio

gencheck_istio
6651bbaad7e0df05da8ad595414d02b10d48404d
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
4ba309d9570fffc651a3596d7520d1208cdaf1bd
link
/test lint_istio

gencheck_istio
6651bbaad7e0df05da8ad595414d02b10d48404d
link
/test gencheck_istio

integ-multicluster-k8s-tests_istio
6651bbaad7e0df05da8ad595414d02b10d48404d
link
/test integ-multicluster-k8s-tests_istio

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

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
a0a02366a5aee198239055c9e913a5c3c319694f
link
/test integ-multicluster-k8s-tests_istio

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

/retest

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

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
a0a02366a5aee198239055c9e913a5c3c319694f
link
/test integ-multicluster-k8s-tests_istio

gencheck_istio
96c53e35f70fd5e91723dd78ba898759794c2d73
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
a0a02366a5aee198239055c9e913a5c3c319694f
link
/test integ-multicluster-k8s-tests_istio

gencheck_istio
96c53e35f70fd5e91723dd78ba898759794c2d73
link
/test gencheck_istio

lint_istio
96c53e35f70fd5e91723dd78ba898759794c2d73
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
96c53e35f70fd5e91723dd78ba898759794c2d73
link
/test gencheck_istio

lint_istio
96c53e35f70fd5e91723dd78ba898759794c2d73
link
/test lint_istio

integ-multicluster-k8s-tests_istio
96c53e35f70fd5e91723dd78ba898759794c2d73
link
/test integ-multicluster-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
96c53e35f70fd5e91723dd78ba898759794c2d73
link
/test gencheck_istio

lint_istio
96c53e35f70fd5e91723dd78ba898759794c2d73
link
/test lint_istio

integ-multicluster-k8s-tests_istio
96c53e35f70fd5e91723dd78ba898759794c2d73
link
/test integ-multicluster-k8s-tests_istio

analyze-tests_istio
d11b6e60e9a9243151c74d91d432cc69b2bffba3
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
96c53e35f70fd5e91723dd78ba898759794c2d73
link
/test gencheck_istio

lint_istio
96c53e35f70fd5e91723dd78ba898759794c2d73
link
/test lint_istio

integ-multicluster-k8s-tests_istio
96c53e35f70fd5e91723dd78ba898759794c2d73
link
/test integ-multicluster-k8s-tests_istio

analyze-tests_istio
d11b6e60e9a9243151c74d91d432cc69b2bffba3
link
/test analyze-tests_istio

unit-tests_istio
d11b6e60e9a9243151c74d91d432cc69b2bffba3
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
96c53e35f70fd5e91723dd78ba898759794c2d73
link
/test gencheck_istio

integ-multicluster-k8s-tests_istio
96c53e35f70fd5e91723dd78ba898759794c2d73
link
/test integ-multicluster-k8s-tests_istio

analyze-tests_istio
d11b6e60e9a9243151c74d91d432cc69b2bffba3
link
/test analyze-tests_istio

unit-tests_istio
d11b6e60e9a9243151c74d91d432cc69b2bffba3
link
/test unit-tests_istio

lint_istio
d11b6e60e9a9243151c74d91d432cc69b2bffba3
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
96c53e35f70fd5e91723dd78ba898759794c2d73
link
/test gencheck_istio

integ-multicluster-k8s-tests_istio
96c53e35f70fd5e91723dd78ba898759794c2d73
link
/test integ-multicluster-k8s-tests_istio

analyze-tests_istio
d11b6e60e9a9243151c74d91d432cc69b2bffba3
link
/test analyze-tests_istio

unit-tests_istio
d11b6e60e9a9243151c74d91d432cc69b2bffba3
link
/test unit-tests_istio

lint_istio
d11b6e60e9a9243151c74d91d432cc69b2bffba3
link
/test lint_istio

integ-operator-controller-tests_istio
d11b6e60e9a9243151c74d91d432cc69b2bffba3
link
/test integ-operator-controller-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
96c53e35f70fd5e91723dd78ba898759794c2d73
link
/test gencheck_istio

integ-multicluster-k8s-tests_istio
96c53e35f70fd5e91723dd78ba898759794c2d73
link
/test integ-multicluster-k8s-tests_istio

analyze-tests_istio
d11b6e60e9a9243151c74d91d432cc69b2bffba3
link
/test analyze-tests_istio

unit-tests_istio
d11b6e60e9a9243151c74d91d432cc69b2bffba3
link
/test unit-tests_istio

lint_istio
d11b6e60e9a9243151c74d91d432cc69b2bffba3
link
/test lint_istio

integ-operator-controller-tests_istio
d11b6e60e9a9243151c74d91d432cc69b2bffba3
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
d11b6e60e9a9243151c74d91d432cc69b2bffba3
link
/test integ-ipv6-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
96c53e35f70fd5e91723dd78ba898759794c2d73
link
/test gencheck_istio

integ-multicluster-k8s-tests_istio
96c53e35f70fd5e91723dd78ba898759794c2d73
link
/test integ-multicluster-k8s-tests_istio

analyze-tests_istio
d11b6e60e9a9243151c74d91d432cc69b2bffba3
link
/test analyze-tests_istio

unit-tests_istio
d11b6e60e9a9243151c74d91d432cc69b2bffba3
link
/test unit-tests_istio

lint_istio
d11b6e60e9a9243151c74d91d432cc69b2bffba3
link
/test lint_istio

integ-operator-controller-tests_istio
d11b6e60e9a9243151c74d91d432cc69b2bffba3
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
d11b6e60e9a9243151c74d91d432cc69b2bffba3
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
d11b6e60e9a9243151c74d91d432cc69b2bffba3
link
/test integ-pilot-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
96c53e35f70fd5e91723dd78ba898759794c2d73
link
/test gencheck_istio

integ-multicluster-k8s-tests_istio
96c53e35f70fd5e91723dd78ba898759794c2d73
link
/test integ-multicluster-k8s-tests_istio

analyze-tests_istio
d11b6e60e9a9243151c74d91d432cc69b2bffba3
link
/test analyze-tests_istio

unit-tests_istio
d11b6e60e9a9243151c74d91d432cc69b2bffba3
link
/test unit-tests_istio

lint_istio
d11b6e60e9a9243151c74d91d432cc69b2bffba3
link
/test lint_istio

integ-operator-controller-tests_istio
d11b6e60e9a9243151c74d91d432cc69b2bffba3
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
d11b6e60e9a9243151c74d91d432cc69b2bffba3
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
d11b6e60e9a9243151c74d91d432cc69b2bffba3
link
/test integ-pilot-k8s-tests_istio

release-test_istio
d11b6e60e9a9243151c74d91d432cc69b2bffba3
link
/test release-test_istio

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

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
66a70be2af24b6636d0cd865d1d64dd71af88e0f
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
66a70be2af24b6636d0cd865d1d64dd71af88e0f
link
/test lint_istio

unit-tests_istio
66a70be2af24b6636d0cd865d1d64dd71af88e0f
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
66a70be2af24b6636d0cd865d1d64dd71af88e0f
link
/test unit-tests_istio

lint_istio
5c5ef280b87594fbb99e697cf26cf986bc68db91
link
/test lint_istio

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

This should work fine though. There's an edge case where all proxies with a cache entry for the same network view and endpoint have their network view change, the cache entries aren't evicted till the cached service is updated.


check database name when collect schemas

When collecting table schemas, we must check selectel database name to avoid conflicts with multiple cloned databases.
For example, you can create database foo, clone it to foo_dev, set the same login/password to both databases and then try to generate structs, after code generation you can see conflicts.

better gen tool: https://github.com/go-gorm/gen


PropType for element prop breaks when dealing with custom components

Problem
The element prop has a required PropType of string, which is a problem when trying to use custom components.
Specifically, the element prop is used to create the base element for the InfiniteScroll component in the following way:
React.createElement(element, props, children)

As can be seen in the createElement docs, the argument element can have several types. These include string, or any React element.
However, when element is a string, React expects that string to be an HTML tag name like div or span, and will break completely if that isn't the case. For custom components (e.g., Grid), the argument must be of type React element.
So, HTML tags will work with:
<InfiniteScroll element="div" />

But there's no good way to do a custom component.  If I try to pass the component name as a string:
<InfiniteScroll element="Grid" />

createElement will try to find a matching HTML tag and fail completely when none exists.
On the other hand, if I pass the component as an element:
<InfiniteScroll element={Grid} />

Everything will render properly, but the console will show an error for failed prop types (since Grid is not a string).
Suggested Fix
I think this is as simple as changing the PropType for element to: PropTypes.oneOfType([PropTypes.string, PropTypes.element]).
I'd be more than happy to submit a PR if this is a good idea.

Hi.
We had a similar issue & PR for changing the loader prop to node.
PropTypes.node allows for anything that can be rendered (numbers, strings, elements, array or fragment).
So feel free to submit a PR with:
element: PropTypes.node,

Thanks!

Fixed in #155

I'm having this same issue when using styled-components
declared element:
export const TableScroll = styled.div`
  display: table;
  table-layout: fixed;
  border-collapse: collapse;
  width: 100%;
  box-sizing: border-box;
  will-change: transform;
  backface-visibility: hidden;
  -webkit-overflow-scrolling: touch;
`

Infinite Scroll
<InfiniteScroll
   element={TableScroll}
   initialLoad={false}
   pageStart={1}
   loadMore={this.loadMore}
   hasMore={this.hasMore()}
   threshold={500}
   useWindow={true}
   loader={<AjaxLoader key={`page-${inventory.page}`} />}
    >

The data renders into the element, but throws the same Failed Prop Type warning and InfiniteScroll doesn't work.   Using a standard element like 'div' works fine.

Same issue here