Install scripts/perf to share/clBLAS on non WIN32 systems

Python scripts should not get installed to /usr/bin. Same as for clFFT https://github.com/clMathLibraries/clFFT/pull/52.

In my linux system (OpenSuse) that I tested, the python files were installed to ${BUILD_DIR}/package/bin directory. "client", which the python scripts will call, resides in the same directory. The architecture of the "package" also includes "lib64", which contains library binary files, "include" with header files and "samples". I am wondering why the pythons scripts were installed into /usr/bin instead.

Actually, this change is similar to https://github.com/clMathLibraries/clFFT/commit/37b1f443e516f0a87c4a728cac8291148bb31b72. See the discussion in https://github.com/clMathLibraries/clFFT/pull/50.
Following your description, it seems that you just compile the package, but didn't installed it. For Gentoo Linux, the change is definitely, necessary. I recently created an clBLAS ebuild for the gentoo science overlay, where the patch already get's applied. Anyway, we always like to see patches getting upstream. Therefore this pull request :)

I did install the package. But it seems there was a recent pull request #71 that by default will make the install destination a system directory on linux system, which I have mixed feelings about. Setting the top level install destination (CMAKE_INSTALL_PREFIX) from cmake, to a destination of your choice will install all the binaries and scripts there. I wonder if that would be okay with you.

I just build clBLAS based on the develop branch and also checked the commits of https://github.com/clMathLibraries/clBLAS/pull/71. Still binaries get installed to /usr/bin
   usr/bin/clBLAS-client
   usr/bin/testPerfWrapper
   usr/lib64/libclBLAS.so.2.3.0
   usr/bin/clBLAS-tune
   usr/bin/make-ktest
   usr/bin/example_sgemv
   usr/bin/example_sgemm
   usr/bin/example_ssymv
   usr/bin/example_ssyrk
   usr/bin/example_ssyr2k
   usr/bin/example_strmm
   usr/bin/example_strsm
   usr/bin/example_strmv
  [..]

That is extremely nasty on Linux systems. The examples shoudn't get installed to /usr/bin, but instead to /usr/share/clBLAS and that is exactly what is suggested with this pull request .

I just build clBLAS from the develop branch.
-- Installing: /var/tmp/portage/sci-libs/clblas-9999/image/usr/bin/clBLAS-client
-- Installing: /var/tmp/portage/sci-libs/clblas-9999/image/usr/bin/testPerfWrapper
-- Installing: /var/tmp/portage/sci-libs/clblas-9999/image/usr/bin/measurePerformance.py
-- Installing: /var/tmp/portage/sci-libs/clblas-9999/image/usr/bin/plotPerformance.py
-- Installing: /var/tmp/portage/sci-libs/clblas-9999/image/usr/bin/blasPerformanceTesting.py
-- Installing: /var/tmp/portage/sci-libs/clblas-9999/image/usr/bin/errorHandler.py
 [..]

The install path /var/tmp/portage/sci-libs/clblas-9999/image/ get's stripped on Gentoo systems in the next step, thus the Python scripts geht installed to /usr/bin.
I also checked pull request #71, this doesn't affect the install location of the python scripts.

Hi. It sounds like all the binaries were installed correctly to the install path but the python scripts are still installed to /usr/bin, as well as clBLAS-client?

This is only a snipped, not all binaries (examples) get installed to the correct location ( as mentioned in #75 ).
Anyway, clBLAS-client get's installed to /usr/bin which is correct, but the python scripts still shouldn't be installed to /usr/bin.

How should we proceed here? I would really like to drop the patches from the clblas ebuild.


Kick animation update

Follow up to PR #3

Improved integration of the Kick
Fixed a Bug where the Animation Runtime Controller is not reloaded properly after respawning
Small Correction to README.md

Forgot to rebase my fork toa void conflicts, sorry


Explosion effect not showing

I'm playing on the latest version available for Quilt 1.19.2, and none of the effects are showing. I've checked the configuration settings and I have everything enabled :(

While I can't guarantee support for Quilt, as it is not the platform Explosive Enhancement is designed for, I did do a quick test myself and it worked fine.

What other mods are you using?
Do you have the right Explosive Enhancement version?
Are the vanilla particles showing?

hi, thanks for checking this issue out! I’ve tried using the mod without any other mod installed except for YetAnotherConfigLib, Mod menu, and the API for Quilt, all of which are the latest available version for Fabric/Quilt 1.19.2, so this probably isn’t an incompatibility issue. The version of this mod I’m using is 1.2.0 for Fabric 1.19.2 released on 25 July, downloaded from Modrinth. I do, however, have my particles set to “minimal” could that be the cause of the issue?

I do, however, have my particles set to “minimal”

Thanks for pointing that out. I believe that is the issue. Could you try turning your particles to "All" and see what happens?

I do, however, have my particles set to “minimal”

Thanks for pointing that out. I believe that is the issue. Could you try turning your particles to "All" and see what happens?

I've just tried this and it works! It works on Quilt, and with 'decreased' particle settings too :D so it seems that particles do not show at all with the 'minimal' setting. Thanks for the help! I'll close this issue now

Glad you figured it out! Hopefully you can have some fun with my mod!


Fixed a bug on the CURL creation related to multipart

Pull Request Test Coverage Report for Build 462

15 of 16 (93.75%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.01%) to 94.416%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

bddrest/documentary/curl.py
11
12
91.67%

Totals

Change from base Build 449:
-0.01%

Covered Lines:
1674

Relevant Lines:
1773

💛  - Coveralls


WhisperKit CLI cleanup

Before taking on https://github.com/argmaxinc/WhisperKit/issues/36 I decided to do a little cleanup in the CLI

moved command line arguments to a separate WhisperKitArguments struct
extracted a separate transcribe subcommand
changed executable name to whisper-kit

so rn in order to run the transcribe command the user has to type swift run whisper-kit transcribe
It's going to be convenient if we're going to add more subcommands in future (e.g. swift run whisper-kit translate)

Good thinking in general with the cleanup, however this will break quite a bit of our benchmark/eval code as is, because it calls this function from python as a shell command, and would require updating all of that as well. If this is a blocker for the homebrew PR then we should discuss further, otherwise it would be ideal to keep the interfaces the same.

Sounds fair. I could potentially add a PR in https://github.com/argmaxinc/whisperkittools repo to accommodate for these changes but I understand the concern. I reverted the renaming part, please take a 2nd look @ZachNagengast


Fix PT-9148

Don't know why there is a +1 - deleting it solves the exception when selection the 31th of a month.

1. Why is this change necessary?
Sovles exception
2. What does this change do, exactly?
Does not add +1
3. Describe each step to reproduce the issue or behaviour.
Go to affilate marketing, select a range of 01.03.2018 to 31.07.2018, and clock on Download - you will get an expcetion with an invalid date (2018-08-32)
4. Please link to the relevant issues (if any).
https://issues.shopware.com/issues/PT-9148
5. Which documentation changes (if any) need to be made because of this PR?
No.
6. Checklist

[ ] I have written tests and verified that they fail without my change
[ ] I have squashed any insignificant commits
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[ ] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-24400
Please use this issue to track the state of your pull request.

Thanks for your Contribution! :blue_heart:


Fix call with widget outside cart or product page not works

Questions
Answers

Description?
fix using {widget name='ps_crossselling' hook='displayShoppingCart'} not work  with ps_crossselling v2.0.1 Prestashop <IP_ADDRESS>

Type?
improvement

BC breaks?
no

Deprecations?
no

Fixed ticket?
-

How to test?
read below.

Fix, If you call widget with tag in smarty, eg:
in [theme]/templates/checkout/cart.tpl
{widget name='ps_crossselling' hook='displayShoppingCart'}

Hi @mkdgs can you please follow the PR template https://github.com/PrestaShop/ps_crossselling/blob/dev/.github/PULL_REQUEST_TEMPLATE.md it contains important informations we need to be able to be able to review your PR. Especially the "How to test" part

Hi @matks, it's done

Hello, it seems this PR is now stale.
I close this PR, following our review guidelines "Pull Requests may be closed after 30 days of inactivity".
If however you are still interested in it, please ping us 😉  we can reopen.
Thank you for your contribution.


Upgrade Gemfile dependencies

What: Upgrade Gemfile dependencies
Why: By upgrading Rails to the latest version, we will need to upgrade the gems we use.
Notes
We will probably need to make code changes. If when upgrading these dependencies we need to make a big code change, let's create a new ticket for it.

Qx


No sections in hs_invertiblity_example (Shock Non Invertiblity)

@jstac here is the issue. Thanks

@AnjuJoon I've fixed this and pushed to master.


Add case of checking timekeeping after multiple reboot

Thanks Jing, the test case does seem relevant in what it does.
For the implementation I find it too be a little bit more long and prone to errors between distros.
What I would recommend is to design it around the setupscripts/Test50TimesReboot.ps1 script.
That one triggers the reboot operations from the host side, so it's distro agnostic.
Plus that the code is already there and can be merely only modified as to run maybe even as a setup or pretest script, then have the actual time sync check script.
Thank you!

Thanks your advice, Chris, I didn't notice this script . It is so convenient to use exist script I just need to modify xml to add this case.

Close this PR to add case with exist script, Thank Chris


Add rachartier/tiny-code-action.nvim

Repo URL:
https://github.com/rachartier/tiny-code-action.nvim
Checklist:

[x] The plugin is specifically built for Neovim, or if it's a colorscheme, it supports treesitter syntax.
[x] The lines end with a .. This is to conform to awesome-list linting and requirements.
[x] The title of the pull request is Add/Update/Remove `username/repo`  (notice the backticks around `username/repo`) when adding a new plugin.
[x] The description doesn't mention that it's a Neovim plugin, it's obvious from the rest of the document. No mentions of the word plugin unless it's related to something else. No .. for Neovim.
[x] The description doesn't contain emojis.
[x] Neovim is spelled as Neovim (not nvim, NeoVim or neovim), Vim is spelled as Vim (capitalized), Lua is spelled as Lua (capitalized), Tree-sitter is spelled as Tree-sitter.
[x] Acronyms should be fully capitalized, for example LSP, TS, YAML, etc.

Thanks for the PR!


Create in-app Bitcoin announcement banner or similar

@markmhx Trying to understand where this would take place. Should we show it to all new and existing users?

I'm thinking we could squeeze in banner right below the "Next steps" section (if not hidden already) and above the rest of the home screen for all users, new and existing, that says something like:

Hiro Wallet now supports Ordinal inscriptions and Bitcoin transactions! Create your first inscription

It could have some light visual treatment that connotes both Bitcoin and Ordinals, and the link could go to a new FAQ that highlights how to use Gamma for inscribing with the wallet. cc @314159265359879

An Enable Bitcoin button with https://confettijs.org 🤔

https://confettijs.org/ could be nice for the moment of transaction broadcasting as well, either alongside implementation of the new "post submission" transaction screen or ahead of it as well as we take the user to the activity area so they have a sense that it was accomplished

https://www.figma.com/file/OSQocEEJnfcMkniEl8u3U8/%231483---Initial-Bitcoin-support?node-id=1266%3A66268&t=EXKw9FjLtTgJvDeF-4


Image Slider

Replace the current image slider with something better and it should be responsive too.
Don't change the text and image*.

You can change images iff you get a better one in place of them

means new animation or something else

I can do this please assign me.

you

means new animation or something else

YOU can change the  Slider completely as per your wish share the SS too before PR

Sir Where i have to send the SS or the video Recording of the Slider

here only

you can do better for text .... like instead of white bg use some transparent blur-bg or something .......

I Have Changed the Design As per Requirement And Also Added the Hover Effect as show in 2nd Pic.
Anything Else i Can Do?

remove the hover effect , rest ok

I removed the hover Effect👍


How can we use property iteration for setting field 'Delegation' in subnet using ARM template

I am not able to set 'delegation' field in subnet using the copy iteration of property in the ARM template for VNET creation.
COPY BLOCK:
            "copy": [
                {
                    "name": "subnets",
                    "count": "[length(parameters('subnets'))]",
                    "input": {
                        "name": "[parameters('subnets')[copyIndex('subnets')].name]",
                        "properties": {
                            "addressPrefix": "[parameters('subnets')[copyIndex('subnets')].addressPrefix]",
                            "networkSecurityGroup": "[if(empty(parameters('subnets')[copyIndex('subnets')].networkSecurityGroupName), json('null'), json(concat('{\"id\": \"', resourceId('Microsoft.Network/networkSecurityGroups', parameters('subnets')[copyIndex('subnets')].networkSecurityGroupName), '\"}')))]",
                            "routeTable": "[if(empty(parameters('subnets')[copyIndex('subnets')].routeTableName), json('null'), json(concat('{\"id\": \"', resourceId('Microsoft.Network/routeTables', parameters('subnets')[copyIndex('subnets')].routeTableName), '\"}')))]",
                            "serviceEndpoints": "[if(empty(parameters('subnets')[copyIndex('subnets')].serviceEndpoints), json('null'), parameters('subnets')[copyIndex('subnets')].serviceEndpoints)]",
                            "delegations": "[if(empty(parameters('subnets')[copyIndex('subnets')].delegations), json('null'),parameters('subnets')[copyIndex('subnets')].delegations)]"

                        }
                    }
                }
            ]
        },

PARAMETER:
   "subnets": {
        "value": [

             {
                "name": "test-subnet-003",
                "addressPrefix": "<IP_ADDRESS>/24",
                "networkSecurityGroupName": "",
                "routeTableName": "",
                "serviceEndpoints": [
                ],
                "delegations": [
                    {
                        "name":  "NetAppDel",
                        "properties": {
                            "serviceName": "Microsoft.Netapp/volumes"
                        }
                    }
                ]
            }
        ]
    },

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

ID: c01dc5ae-fd95-0d3a-bc60-5f6dbd9372b2
Version Independent ID: bf6b4d40-08ba-7655-0547-8db6070c58f4
Content: Define multiple instances of a property - Azure Resource Manager
Content Source: articles/azure-resource-manager/templates/copy-properties.md
Service: azure-resource-manager
Sub-service: templates
GitHub Login: @mumian
Microsoft Alias: jgao

@ManmohitSingh10 Hope you have self resolved and hence closed the issue. Thanks for the update.

Sorry, closed by mistake, the issue is still open.

@ManmohitSingh10 Okay. We will review and provide an appropriate update ASAP.

@ManmohitSingh10 - what type of error are you seeing?

@tfitzmac -
"code": "InvalidTemplate",
"message": "Unable to process template language expressions for resource 'The language expression property 'properties' has an invalid array index.'",

@ManmohitSingh10 Did you provide the 'type' of parameter named 'subnets' as 'string' instead of 'array' in the deploy json template file ? I believe this is one classic example template that we can compare with your requirement.
Tagging @tfitzmac for visibility, to provide insights and help on this. Thanks.

I have fixed the issue. There was an issue with the value of the parameter - 'subnets' that I was passing. Thanks for the assistance.

@mpsingh10  Can you please highlight the correct code, as I'm also facing the same issue for service endpoints


Add missing files in 2014-04-01 for go sdk

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-python

Automation for azure-sdk-for-go

@jaredmoo  please help review this PR. Thanks.

This pr is submitted due to the current sql/2014-04-01 lack of some functions comparing to the swagger. Therefore I changed the tag in readme.go.md from package-2014-04 to package-pure-2014-04 to cover more swagger files for go SDK.

Can one of the admins verify this patch?

Hi @yaohaizh I have reverted the changes in input-files section of readme.md file. Now the only change is readme.go.md, which will only affect go SDK.


API partial redesign. Command execution helpers.

Change list
API partial redesign:

OpenQA.Selenium.Appium.Android.Interfaces.ISendsKeyEvents was marked obsolete.
Appium.Interfaces.ISendsKeyEvents was added. It is implemented by AndroidDriver and WindowsDriver.
OpenQA.Selenium.Appium.iOS.Interfaces.IIOSHidesKeyboard  was marked obsolete.
OpenQA.Selenium.Appium.Interfaces.IHidesKeyboardWithKeyName was added. It extends OpenQA.Selenium.Appium.Interfaces.IHidesKeyboard and it is implemented by IOSDriver and WindowsDriver.
OpenQA.Selenium.Appium.Android.Interfaces.IHasSettings was added. It is implemented by AndroidDriver. Also the OpenQA.Selenium.Appium.Android.Enims.AutomatorSetting was provided.
OpenQA.Selenium.Appium.iOS.Interfaces.IPerformsTouchID was added. It is implemented by IOSDriver.
almost all interfaces extend the OpenQA.Selenium.Appium.Interfaces.IExecuteMethod

Command execution helpers:

OpenQA.Selenium.Appium.AppiumCommandExecutionHelper was added.
OpenQA.Selenium.Appium.Android.AndroidCommandExecutionHelper was added.
OpenQA.Selenium.Appium.iOS.IOSCommandExecutionHelper was added.
These classes consist of static methods which accept IExecuteMethod as one of parameters.

Types of changes

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

##Details
This is the preparation to the making AppiumDriver the non-abstract class. Also some functions which were supposed to be Android-specific/iOS-specific are used by Windows automation. So it is needed to be used across few platforms.

@jlipps @Astro03 @yodurr could you review it?

LGTM too.

Ok. I'm merging.


Unable to search

Moving the pinned location works fine. However when I attempt to search for an address it gives me an undefined error when trying to access lat. All relevant versions should be at their latest since this is a brand new project.

having the same issue, any update on this?

looks like this fork might have the solution: https://github.com/aadgrant/sanity-plugin-leaflet-input/commit/53df165093df7a3a3dc6b572ee94bdd83cb3b4aa
Why no update on this recently? Is this project abandoned?

The issue with the inability to search seems to come from a required input method. The browser console gives the below warning when trying to use the search field.
The input component for type "geopoint" is missing a required ".focus()" method
The link below provides some guidelines for a fix to the issue.

The issue with the inability to search seems to come from a required input method. The browser console gives the below warning when trying to use the search field.
The input component for type "geopoint" is missing a required ".focus()" method
The link above provides some guidelines for a fix to the issue.

The link where? I dont see a link with guidance on how to fix. Can you please provide a link if you have found a workaround?

My bad I skipped the link before posting. Here, please:
https://www.sanity.io/help/input-component-missing-required-method
https://www.sanity.io/docs/custom-input-widgets
https://res.cloudinary.com/calebyeboah/image/upload/v1654194192/Error_-_required_focus_method_fqdyzl.png
Currently, I do not get the error message in some instances when I choose from a list of suggested locations provided to me by OpenStreetMap after I type in my search term in the search box. However, the above warning seems to persist in the console.


Multi-stage cluster addons: Patching clusteraddon objects seems to cause issues

/kind bug
What steps did you take and what happened:
Sometimes when testing it happens that an upgrade flow is triggered right after the create flow. This apparently has something to do with the "ready: true" not being patched correctly. At least in the next reconcile loop it is not there anymore. Or is this cached in the next reconcile loop? The conditions are up to date.
What did you expect to happen:
This should be patched correctly and we should not trigger upgrade flows if not necessary.

We have tracked this down. And don't understand it at all. I have asked in Slack whether someone else has an idea. We patch the ClusterAddon object at the end and set the boolean "ready" on true. We also set a condition "HelmChartApplied". Then we fetch the object again and the condition is there, but the boolean is on false.
This leads to the controller thinking it is in the middle of an ongoing process and triggers a second upgrade flow, after the create flow is done. In practice, this won't harm as long as the ClusterStack is constructed well. We have actually realized this through a wrongly constructed ClusterStack where the upgrade process triggered after the create process failed.
We lack an idea of how this can happen, and it is no problem in practice. It will just do two rounds of applying the same objects. Therefore, we will leave this as is now. Hopefully, we'll find out why this happens eventually.


Hedge Position

Does any body has any Idea if I can keep Hedge position from the both sides (long & short) running rather than humminbot keeping only of the sides running after one of the sides is closed. Currently when HBOT places orders on each side, and one side is  closed with profit it keeps the other side running and not placing any orders from closed orders position running. I want to keep each side running no matter what the market direction is.

Handing custom requests like this is why we created the Community Bounties process. See this post for more info: https://blog.hummingbot.org/introducing-community-bounties/


Can't update spreadsheet sections

I get this error whenever trying to edit a spreadsheet, with any operation and section:
This document does not support updates with the given location type and section_id.
so section_id param is unused in edit_document for spreadsheets.
RIP

I have the same problem.


locking?

not sure if it's an issue, but I've noticed locking in the lookup method:
func lookup(lang, cat string, fallback bool) string {
	samplesLock.Lock()
	s := _lookup(lang, cat, fallback)
	samplesLock.Unlock()
	return s
}

does it mean it's kind of a synchronous access? If so, is there any chance to provide non-locking implementation? As for the parallel world it sounds like a bad idea.

The sample data gets cached in a map, and maps are not safe for concurrent access in Go. We need to coordinate access, and a mutex is probably the appropriate solution.
However, we should be using a RWMutex so that once it is cached then readers can access it concurrently. Commit #9d352d2 does that.
Thanks for the report!

thanks for incredible response time!


Ambiguous phrasing

I would argue that this sentence is ambiguous: "Linker errors occur when the same name has two different definitions in different translation units." and would rephrase it to be "Linker errors occur when the same name is defined in different translation units."
Because "two different definitions" to me implies that if a symbol is defined twice in the same exact way, it's only one definition that would be acceptable. But we all know that according to the C standard, this is not acceptable and violates the ODR. This case (one symbol redefined the same way in multiple translation units) is also one of the more common and confusing cases because that's what happens when a symbol is defined in a header file and included in multiple other files.

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

ID: 04d22551-f6be-bbd0-98e6-805b8875c07e
Version Independent ID: c94795a2-814b-0c05-d2df-5ba3bc0425c7
Content: Translation units and linkage (C++)
Content Source: docs/cpp/program-and-linkage-cpp.md
Product: visual-cpp
Technology: cpp-language
GitHub Login: @corob-msft
Microsoft Alias: corob

@Thomas-PM
Thanks for the report. An update with a fix is available now.


Off by two error in bullet/mine shooting cooldowns

The ship's fire time is set to 1/10 seconds, and the mine deploy time is set to 1 second. The game runs at 30 FPS, so we would expect that we can fire bullets once every 3 timesteps, and lay mines once every 30. However in reality, we can only shoot once every 5 timesteps and lay a mine once every 32 timesteps. This off-by-two error is caused by the way we're checking whether the cooldown has hit 0.
On the timestep the cooldown "hits zero", it actually hits 1.3877787807814457e-17 in the case of firing bullets, which isn't below 0. We then spend a timestep decrementing this to a negative number, and another timestep setting that to 0, which costs an extra 2 timesteps than expected.
I propose we fix this for clarity, but just in case this breaks people's controllers, we can change the firing rate to 1/6 seconds, so the firing is still once every 5 frames. But the mine cooldown can be changed from 32 to 30 frames.
We can also add in the can_deploy_mine in the boolean that's passed to the player, so they know whether they can lay a mine again

Was fixed in #50


Tabular doesn't work with Meteor Partitioner

It seems that Tabular doesn't work with Meteor Partitioner (https://github.com/mizzao/meteor-partitioner). As soon as a collection is partitioned, Tabular refuses to display any data. Even a custom publication won't help.
Is it possible to get Tabular to work with partitioned collections?

Same problem here.

I haven't used this, but it seems like it would work. Somebody will need to post a link to an app that reproduces the issue.

I am using Tabular to display partitioned data and don't have an issue.  I did make some tweaks to the partitioner package to support some other things I'm doing, but it's not immediately obvious to me that any of those would have 'fixed' Tabular.


subnet e2e fails occasionally

• [FAILED] [8.089 seconds]
[CNI:Kube-OVN] [group:subnet]
/home/runner/work/kube-ovn/kube-ovn/test/e2e/framework/framework.go:139
  [It] should support subnet AvailableIPRange and UsingIPRange is correct when restart deployment [Conformance]
  /home/runner/work/kube-ovn/kube-ovn/test/e2e/kube-ovn/subnet/subnet.go:727

  Begin Captured StdOut/StdErr Output >>
    delete deployment deployment-8733 failed with err <nil>
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    [BeforeEach] [CNI:Kube-OVN] [group:subnet]
      set up framework | framework.go:178
    STEP: Creating a kubernetes client 02/28/23 06:53:59.865
    Feb 28 06:53:59.865: INFO: >>> kubeConfig: /home/runner/.kube/config
    STEP: Building a namespace api object, basename subnet 02/28/23 06:53:59.866
    STEP: Waiting for a default service account to be provisioned in namespace 02/28/23 06:53:59.893
    STEP: Waiting for kube-root-ca.crt to be provisioned in namespace 02/28/23 06:53:59.896
    [BeforeEach] [CNI:Kube-OVN] [group:subnet]
      /home/runner/work/kube-ovn/kube-ovn/test/e2e/framework/framework.go:58
    STEP: Setting kubernetes context 02/28/23 06:53:59.898
    STEP: Creating a Kube-OVN client 02/28/23 06:53:59.898
    Feb 28 06:53:59.898: INFO: >>> kubeConfig: /home/runner/.kube/config
    [BeforeEach] [CNI:Kube-OVN] [group:subnet]
      /home/runner/work/kube-ovn/kube-ovn/test/e2e/kube-ovn/subnet/subnet.go:43
    [It] should support subnet AvailableIPRange and UsingIPRange is correct when restart deployment [Conformance]
      /home/runner/work/kube-ovn/kube-ovn/test/e2e/kube-ovn/subnet/subnet.go:727
    STEP: Creating subnet subnet-7759 02/28/23 06:53:59.899
    Feb 28 06:53:59.904: INFO: Waiting up to 2m0s for subnet subnet-7759 condition Ready to be true
    Feb 28 06:53:59.907: INFO: Couldn't find condition Ready on subnet subnet-7759
    Feb 28 06:54:01.919: INFO: deployment status: v1.DeploymentStatus{ObservedGeneration:0, Replicas:0, UpdatedReplicas:0, ReadyReplicas:0, AvailableReplicas:0, UnavailableReplicas:0, Conditions:[]v1.DeploymentCondition(nil), CollisionCount:(*int32)(nil)}
    Feb 28 06:54:03.922: INFO: deployment status: v1.DeploymentStatus{ObservedGeneration:1, Replicas:5, UpdatedReplicas:5, ReadyReplicas:0, AvailableReplicas:0, UnavailableReplicas:5, Conditions:[]v1.DeploymentCondition{v1.DeploymentCondition{Type:"Available", Status:"False", LastUpdateTime:time.Date(2023, time.February, 28, 6, 54, 1, 0, time.Local), LastTransitionTime:time.Date(2023, time.February, 28, 6, 54, 1, 0, time.Local), Reason:"MinimumReplicasUnavailable", Message:"Deployment does not have minimum availability."}, v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:time.Date(2023, time.February, 28, 6, 54, 2, 0, time.Local), LastTransitionTime:time.Date(2023, time.February, 28, 6, 54, 1, 0, time.Local), Reason:"ReplicaSetUpdated", Message:"ReplicaSet \"deployment-8733-77bb6f7494\" is progressing."}}, CollisionCount:(*int32)(nil)}
    Feb 28 06:54:05.9[26](https://github.com/zhangzujian/kube-ovn/actions/runs/4290297851/jobs/7474222179#step:17:27): FAIL: Expected
        <string>:
    to equal
        <string>: <IP_ADDRESS>-<IP_ADDRESS>

    Full Stack Trace
    github.com/kubeovn/kube-ovn/test/e2e/kube-ovn/subnet.glob..func1.13.1({0x0, 0x0}, {0xc00065dea0, 0x19}, {0xc000992dd0, 0xb}, {0xc000992d80, 0xd}, 0x5)
    	/home/runner/work/kube-ovn/kube-ovn/test/e2e/kube-ovn/subnet/subnet.go:755 +0x305
    github.com/kubeovn/kube-ovn/test/e2e/kube-ovn/subnet.glob..func1.13()
    	/home/runner/work/kube-ovn/kube-ovn/test/e2e/kube-ovn/subnet/subnet.go:761 +0x943
    github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0xa84a5e, 0xc000970780})
    	/home/runner/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.4.0/internal/node.go:449 +0x1b
    github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func2()
    	/home/runner/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.4.0/internal/suite.go:750 +0x98
    created by github.com/onsi/ginkgo/v2/internal.(*Suite).runNode
    	/home/runner/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.4.0/internal/suite.go:738 +0xe3d
    [AfterEach] [CNI:Kube-OVN] [group:subnet]
      /home/runner/work/kube-ovn/kube-ovn/test/e2e/kube-ovn/subnet/subnet.go:72
    STEP: Deleting deployment  02/[28](https://github.com/zhangzujian/kube-ovn/actions/runs/4290297851/jobs/7474222179#step:17:29)/23 06:54:05.926
    STEP: Deleting pods  02/28/23 06:54:05.9[29](https://github.com/zhangzujian/kube-ovn/actions/runs/4290297851/jobs/7474222179#step:17:30)
    STEP: Deleting subnet subnet-7759 02/28/23 06:54:05.929
    Feb 28 06:54:05.9[34](https://github.com/zhangzujian/kube-ovn/actions/runs/4290297851/jobs/7474222179#step:17:35): INFO: Waiting for subnet subnet-7759 to disappear
    Feb 28 06:54:05.947: INFO: Subnet subnet-7759 still exists
    Feb 28 06:54:07.948: INFO: Waiting for subnet subnet-7759 to disappear
    Feb 28 06:54:07.951: INFO: Subnet subnet-7759 no longer exists
    [DeferCleanup (Each)] [CNI:Kube-OVN] [group:subnet]
      dump namespaces | framework.go:196
    STEP: dump namespace information after failure 02/28/23 06:54:07.951
    [DeferCleanup (Each)] [CNI:Kube-OVN] [group:subnet]
      tear down framework | framework.go:193
    STEP: Destroying namespace "subnet-2582" for this suite. 02/28/23 06:54:07.9[51](https://github.com/zhangzujian/kube-ovn/actions/runs/4290297851/jobs/7474222179#step:17:52)
  << End Captured GinkgoWriter Output

  Feb 28 06:[54](https://github.com/zhangzujian/kube-ovn/actions/runs/4290297851/jobs/7474222179#step:17:55):05.926: Expected
      <string>:
  to equal
      <string>: <IP_ADDRESS>-<IP_ADDRESS>
  In [It] at: /home/runner/work/kube-ovn/kube-ovn/test/e2e/kube-ovn/subnet/subnet.go:7[55](https://github.com/zhangzujian/kube-ovn/actions/runs/4290297851/jobs/7474222179#step:17:56)

• [FAILED] [425.256 seconds]
[CNI:Kube-OVN] [group:underlay]
/home/runner/work/kube-ovn/kube-ovn/test/e2e/framework/framework.go:143
  [It] should support underlay to overlay subnet interconnection  [Conformance]
  /home/runner/work/kube-ovn/kube-ovn/test/e2e/kube-ovn/underlay/underlay.go:438

  Begin Captured GinkgoWriter Output >>
    [BeforeEach] [CNI:Kube-OVN] [group:underlay]
      set up framework | framework.go:178
    STEP: Creating a kubernetes client 03/01/23 08:04:26.542
    Mar  1 08:04:26.542: INFO: >>> kubeConfig: /home/runner/.kube/config
    STEP: Building a namespace api object, basename underlay 03/01/23 08:04:26.543
    STEP: Waiting for a default service account to be provisioned in namespace 03/01/23 08:04:26.563
    STEP: Waiting for kube-root-ca.crt to be provisioned in namespace 03/01/23 08:04:26.567
    [BeforeEach] [CNI:Kube-OVN] [group:underlay]
      /home/runner/work/kube-ovn/kube-ovn/test/e2e/framework/framework.go:58
    STEP: Setting kubernetes context 03/01/23 08:04:26.57
    [BeforeEach] [CNI:Kube-OVN] [group:underlay]
      /home/runner/work/kube-ovn/kube-ovn/test/e2e/kube-ovn/underlay/underlay.go:66
    STEP: Getting kind nodes 03/01/23 08:04:26.57
    STEP: Connecting nodes to the docker network 03/01/23 08:04:26.572
    STEP: Getting node links that belong to the docker network 03/01/23 08:04:27.07
    Mar  1 08:04:27.072: INFO: Executing command "ip -d -j address show" in container 5b68e665248b8b8473e3b5508effa679bcb6b9b0ae1d6f41426b50585cf4a820
    Mar  1 08:04:27.202: INFO: stdout: [{"ifindex":1,"ifname":"lo","flags":["LOOPBACK","UP","LOWER_UP"],"mtu":65536,"qdisc":"noqueue","operstate":"UNKNOWN","group":"default","txqlen":1000,"link_type":"loopback","address":"00:00:00:00:00:00","broadcast":"00:00:00:00:00:00","promiscuity":0,"min_mtu":0,"max_mtu":0,"num_tx_queues":1,"num_rx_queues":1,"gso_max_size":65536,"gso_max_segs":65535,"addr_info":[{"family":"inet","local":"<IP_ADDRESS>","prefixlen":8,"scope":"host","label":"lo","valid_life_time":4294967295,"preferred_life_time":4294967295},{"family":"inet6","local":"::1","prefixlen":128,"scope":"host","valid_life_time":4294967295,"preferred_life_time":4294967295}]},{"ifindex":2,"ifname":"kube-ipvs0","flags":["BROADCAST","NOARP"],"mtu":1500,"qdisc":"noop","operstate":"DOWN","group":"default","link_type":"ether","address":"c6:e5:55:46:89:5f","broadcast":"ff:ff:ff:ff:ff:ff","promiscuity":0,"min_mtu":0,"max_mtu":0,"linkinfo":{"info_kind":"dummy"},"num_tx_queues":1,"num_rx_queues":1,"gso_max_size":65536,"gso_max_segs":65535,"addr_info":[{"family":"inet6","local":"fd00:10:96::bd57","prefixlen":128,"scope":"global","valid_life_time":4294967295,"preferred_life_time":4294967295},{"family":"inet6","local":"fd00:10:96::e647","prefixlen":128,"scope":"global","valid_life_time":4294967295,"preferred_life_time":4294967295},{"family":"inet6","local":"fd00:10:96::6e3","prefixlen":128,"scope":"global","valid_life_time":4294967295,"preferred_life_time":4294967295},{"family":"inet6","local":"fd00:10:96::46e","prefixlen":128,"scope":"global","valid_life_time":4294967295,"preferred_life_time":4294967295},{"family":"inet6","local":"fd00:10:96::13a6","prefixlen":128,"scope":"global","valid_life_time":4294967295,"preferred_life_time":4294967295},{"family":"inet6","local":"fd00:10:96::9c47","prefixlen":128,"scope":"global","valid_life_time":4294967295,"preferred_life_time":4294967295},{"family":"inet6","local":"fd00:10:96::89c","prefixlen":128,"scope":"global","valid_life_time":4294967295,"preferred_life_time":4294967295},{"family":"inet6","local":"fd00:10:96::a","prefixlen":128,"scope":"global","valid_life_time":4294967295,"preferred_life_time":4294967295},{"family":"inet6","local":"fd00:10:96::1","prefixlen":128,"scope":"global","valid_life_time":4294967295,"preferred_life_time":4294967295}]},{"ifindex":3,"ifname":"ovs-system","flags":["BROADCAST","MULTICAST"],"mtu":1500,"qdisc":"noop","operstate":"DOWN","group":"default","txqlen":1000,"link_type":"ether","address":"b2:e2:3f:cf:1e:ce","broadcast":"ff:ff:ff:ff:ff:ff","promiscuity":1,"min_mtu":68,"max_mtu":65535,"linkinfo":{"info_kind":"openvswitch"},"num_tx_queues":1,"num_rx_queues":1,"gso_max_size":65536,"gso_max_segs":65535,"addr_info":[]},{"ifindex":4,"ifname":"br-int","flags":["BROADCAST","MULTICAST"],"mtu":1380,"qdisc":"noop","operstate":"DOWN","group":"default","txqlen":1000,"link_type":"ether","address":"2a:5f:42:3a:f8:f8","broadcast":"ff:ff:ff:ff:ff:ff","promiscuity":1,"min_mtu":68,"max_mtu":65535,"linkinfo":{"info_kind":"openvswitch"},"num_tx_queues":1,"num_rx_queues":1,"gso_max_size":65536,"gso_max_segs":65535,"addr_info":[]},{"ifindex":5,"ifname":"genev_sys_6081","flags":["BROADCAST","MULTICAST","UP","LOWER_UP"],"mtu":65000,"qdisc":"noqueue","master":"ovs-system","operstate":"UNKNOWN","group":"default","txqlen":1000,"link_type":"ether","address":"de:97:70:9b:6d:83","broadcast":"ff:ff:ff:ff:ff:ff","promiscuity":1,"min_mtu":68,"max_mtu":65465,"linkinfo":{"info_kind":"geneve","info_data":{"external":true,"id":0,"ttl":0,"df":"unset","port":6081,"udp_zero_csum6_rx":true},"info_slave_kind":"openvswitch"},"num_tx_queues":1,"num_rx_queues":1,"gso_max_size":65536,"gso_max_segs":65535,"addr_info":[{"family":"inet6","local":"fe80::dc97:70ff:fe9b:6d83","prefixlen":64,"scope":"link","valid_life_time":4294967295,"preferred_life_time":4294967295}]},{"ifindex":6,"ifname":"mirror0","flags":["BROADCAST","MULTICAST","UP","LOWER_UP"],"mtu":1380,"qdisc":"noqueue","operstate":"UNKNOWN","group":"default","txqlen":1000,"link_type":"ether","address":"66:fa:b4:7b:60:b0","broadcast":"ff:ff:ff:ff:ff:ff","promiscuity":1,"min_mtu":68,"max_mtu":65535,"linkinfo":{"info_kind":"openvswitch"},"num_tx_queues":1,"num_rx_queues":1,"gso_max_size":65536,"gso_max_segs":65535,"addr_info":[{"family":"inet6","local":"fe80::64fa:b4ff:fe7b:60b0","prefixlen":64,"scope":"link","valid_life_time":4294967295,"preferred_life_time":4294967295}]},{"ifindex":7,"link_index":8,"ifname":"eth0","flags":["BROADCAST","MULTICAST","UP","LOWER_UP"],"mtu":1500,"qdisc":"noqueue","operstate":"UP","group":"default","link_type":"ether","address":"02:42:ac:12:00:03","broadcast":"ff:ff:ff:ff:ff:ff","link_netnsid":0,"promiscuity":0,"min_mtu":68,"max_mtu":65535,"linkinfo":{"info_kind":"veth"},"num_tx_queues":2,"num_rx_queues":2,"gso_max_size":65536,"gso_max_segs":65535,"addr_info":[{"family":"inet","local":"<IP_ADDRESS>","prefixlen":16,"broadcast":"<IP_ADDRESS>","scope":"global","label":"eth0","valid_life_time":4294967295,"preferred_life_time":4294967295},{"family":"inet6","local":"fc00:f853:ccd:e793::3","prefixlen":64,"scope":"global","nodad":true,"valid_life_time":4294967295,"preferred_life_time":4294967295},{"family":"inet6","local":"fe80::42:acff:fe12:3","prefixlen":64,"scope":"link","valid_life_time":4294967295,"preferred_life_time":4294967295}]},{"ifindex":8,"ifname":"ovn0","flags":["BROADCAST","MULTICAST","UP","LOWER_UP"],"mtu":1380,"qdisc":"noqueue","operstate":"UNKNOWN","group":"default","txqlen":1000,"link_type":"ether","address":"00:00:00:23:b0:85","broadcast":"ff:ff:ff:ff:ff:ff","promiscuity":1,"min_mtu":68,"max_mtu":65535,"linkinfo":{"info_kind":"openvswitch"},"num_tx_queues":1,"num_rx_queues":1,"gso_max_size":65536,"gso_max_segs":65535,"addr_info":[{"family":"inet6","local":"fd00:100:64::3","prefixlen":64,"scope":"global","valid_life_time":4294967295,"preferred_life_time":4294967295},{"family":"inet6","local":"fe80::200:ff:fe23:b085","prefixlen":64,"scope":"link","valid_life_time":4294967295,"preferred_life_time":4294967295}]},{"ifindex":12,"link_index":11,"ifname":"281af2aa6a64_h","flags":["BROADCAST","MULTICAST","UP","LOWER_UP"],"mtu":1380,"qdisc":"noqueue","master":"ovs-system","operstate":"UP","group":"default","txqlen":1000,"link_type":"ether","address":"02:e9:55:33:1c:7c","broadcast":"ff:ff:ff:ff:ff:ff","link_netnsid":2,"promiscuity":1,"min_mtu":68,"max_mtu":65535,"linkinfo":{"info_kind":"veth","info_slave_kind":"openvswitch"},"num_tx_queues":2,"num_rx_queues":2,"gso_max_size":65536,"gso_max_segs":65535,"addr_info":[{"family":"inet6","local":"fe80::e9:55ff:fe33:1c7c","prefixlen":64,"scope":"link","valid_life_time":4294967295,"preferred_life_time":4294967295}]},{"ifindex":14,"link_index":13,"ifname":"83b14b6f3a5a_h","flags":["BROADCAST","MULTICAST","UP","LOWER_UP"],"mtu":1380,"qdisc":"noqueue","master":"ovs-system","operstate":"UP","group":"default","txqlen":1000,"link_type":"ether","address":"9a:d2:ec:26:e4:db","broadcast":"ff:ff:ff:ff:ff:ff","link_netnsid":3,"promiscuity":1,"min_mtu":68,"max_mtu":65535,"linkinfo":{"info_kind":"veth","info_slave_kind":"openvswitch"},"num_tx_queues":2,"num_rx_queues":2,"gso_max_size":65536,"gso_max_segs":65535,"addr_info":[{"family":"inet6","local":"fe80::98d2:ecff:fe26:e4db","prefixlen":64,"scope":"link","valid_life_time":4294967295,"preferred_life_time":4294967295}]},{"ifindex":16,"link_index":15,"ifname":"ca4c76eab877_h","flags":["BROADCAST","MULTICAST","UP","LOWER_UP"],"mtu":1380,"qdisc":"noqueue","master":"ovs-system","operstate":"UP","group":"default","txqlen":1000,"link_type":"ether","address":"82:e5:fc:a9:de:dd","broadcast":"ff:ff:ff:ff:ff:ff","link_netnsid":1,"promiscuity":1,"min_mtu":68,"max_mtu":65535,"linkinfo":{"info_kind":"veth","info_slave_kind":"openvswitch"},"num_tx_queues":2,"num_rx_queues":2,"gso_max_size":65536,"gso_max_segs":65535,"addr_info":[{"family":"inet6","local":"fe80::80e5:fcff:fea9:dedd","prefixlen":64,"scope":"link","valid_life_time":4294967295,"preferred_life_time":4294967295}]},{"ifindex":18,"link_index":19,"ifname":"eth3","flags":["BROADCAST","MULTICAST","UP","LOWER_UP"],"mtu":1500,"qdisc":"noqueue","operstate":"UP","group":"default","link_type":"ether","address":"02:42:ac:13:00:02","broadcast":"ff:ff:ff:ff:ff:ff","link_netnsid":0,"promiscuity":0,"min_mtu":68,"max_mtu":65535,"linkinfo":{"info_kind":"veth"},"num_tx_queues":2,"num_rx_queues":2,"gso_max_size":65536,"gso_max_segs":65535,"addr_info":[{"family":"inet","local":"<IP_ADDRESS>","prefixlen":16,"broadcast":"<IP_ADDRESS>","scope":"global","label":"eth3","valid_life_time":4294967295,"preferred_life_time":4294967295},{"family":"inet6","local":"fc00:adb1:b29b:608d::2","prefixlen":64,"scope":"global","nodad":true,"valid_life_time":4294967295,"preferred_life_time":4294967295},{"family":"inet6","local":"fe80::42:acff:fe13:2","prefixlen":64,"scope":"link","tentative":true,"valid_life_time":4294967295,"preferred_life_time":4294967295}]}]

    Mar  1 08:04:27.202: INFO: stderr:
    Mar  1 08:04:27.203: INFO: Executing command "ip -d -j route show" in container 5b68e665248b8b8473e3b5508effa679bcb6b9b0ae1d6f41426b50585cf4a820
    Mar  1 08:04:27.300: INFO: stdout: [{"type":"unicast","dst":"default","gateway":"<IP_ADDRESS>","dev":"eth0","protocol":"boot","scope":"global","flags":[]},{"type":"unicast","dst":"<IP_ADDRESS>/16","dev":"eth0","protocol":"kernel","scope":"link","prefsrc":"<IP_ADDRESS>","flags":[]},{"type":"unicast","dst":"<IP_ADDRESS>/16","dev":"eth3","protocol":"kernel","scope":"link","prefsrc":"<IP_ADDRESS>","flags":[]}]

    Mar  1 08:04:27.300: INFO: stderr:
    Mar  1 08:04:27.300: INFO: Executing command "ip -d -j -6 route show" in container 5b68e665248b8b8473e3b5508effa679bcb6b9b0ae1d6f41426b50585cf4a820
    Mar  1 08:04:27.417: INFO: stdout: [{"type":"unicast","dst":"fc00:adb1:b29b:608d::/64","dev":"eth3","protocol":"kernel","scope":"global","metric":256,"flags":[],"pref":"medium"},{"type":"unicast","dst":"fc00:f853:ccd:e793::/64","dev":"eth0","protocol":"kernel","scope":"global","metric":256,"flags":[],"pref":"medium"},{"type":"unicast","dst":"fd00:10:16::/64","gateway":"fd00:100:64::1","dev":"ovn0","protocol":"boot","scope":"global","prefsrc":"fc00:f853:ccd:e793::3","metric":1024,"flags":[],"pref":"medium"},{"type":"unicast","dst":"fd00:100:64::/64","dev":"ovn0","protocol":"kernel","scope":"global","metric":256,"flags":[],"pref":"medium"},{"type":"unicast","dst":"fe80::/64","dev":"eth0","protocol":"kernel","scope":"global","metric":256,"flags":[],"pref":"medium"},{"type":"unicast","dst":"fe80::/64","dev":"genev_sys_6081","protocol":"kernel","scope":"global","metric":256,"flags":[],"pref":"medium"},{"type":"unicast","dst":"fe80::/64","dev":"mirror0","protocol":"kernel","scope":"global","metric":256,"flags":[],"pref":"medium"},{"type":"unicast","dst":"fe80::/64","dev":"ovn0","protocol":"kernel","scope":"global","metric":256,"flags":[],"pref":"medium"},{"type":"unicast","dst":"fe80::/64","dev":"281af2aa6a64_h","protocol":"kernel","scope":"global","metric":256,"flags":[],"pref":"medium"},{"type":"unicast","dst":"fe80::/64","dev":"83b14b6f3a5a_h","protocol":"kernel","scope":"global","metric":256,"flags":[],"pref":"medium"},{"type":"unicast","dst":"fe80::/64","dev":"ca4c76eab877_h","protocol":"kernel","scope":"global","metric":256,"flags":[],"pref":"medium"},{"type":"unicast","dst":"fe80::/64","dev":"eth3","protocol":"kernel","scope":"global","metric":256,"flags":[],"pref":"medium"},{"type":"unicast","dst":"default","gateway":"fc00:f853:ccd:e793::1","dev":"eth0","protocol":"boot","scope":"global","metric":1024,"flags":[],"pref":"medium"}]

    Mar  1 08:04:27.417: INFO: stderr:
    Mar  1 08:04:27.417: INFO: Executing command "ip -d -j address show" in container ca81da5e5f711f0fe5ee792cfb1a7c7f2c651bf0692ad141919ea7e7dcafefc6
    Mar  1 08:04:27.497: INFO: stdout: [{"ifindex":1,"ifname":"lo","flags":["LOOPBACK","UP","LOWER_UP"],"mtu":65536,"qdisc":"noqueue","operstate":"UNKNOWN","group":"default","txqlen":1000,"link_type":"loopback","address":"00:00:00:00:00:00","broadcast":"00:00:00:00:00:00","promiscuity":0,"min_mtu":0,"max_mtu":0,"num_tx_queues":1,"num_rx_queues":1,"gso_max_size":65536,"gso_max_segs":65535,"addr_info":[{"family":"inet","local":"<IP_ADDRESS>","prefixlen":8,"scope":"host","label":"lo","valid_life_time":4294967295,"preferred_life_time":4294967295},{"family":"inet6","local":"::1","prefixlen":128,"scope":"host","valid_life_time":4294967295,"preferred_life_time":4294967295}]},{"ifindex":2,"ifname":"kube-ipvs0","flags":["BROADCAST","NOARP"],"mtu":1500,"qdisc":"noop","operstate":"DOWN","group":"default","link_type":"ether","address":"c6:f3:b9:01:b2:6e","broadcast":"ff:ff:ff:ff:ff:ff","promiscuity":0,"min_mtu":0,"max_mtu":0,"linkinfo":{"info_kind":"dummy"},"num_tx_queues":1,"num_rx_queues":1,"gso_max_size":65536,"gso_max_segs":65535,"addr_info":[{"family":"inet6","local":"fd00:10:96::bd57","prefixlen":128,"scope":"global","valid_life_time":4294967295,"preferred_life_time":4294967295},{"family":"inet6","local":"fd00:10:96::e647","prefixlen":128,"scope":"global","valid_life_time":4294967295,"preferred_life_time":4294967295},{"family":"inet6","local":"fd00:10:96::6e3","prefixlen":128,"scope":"global","valid_life_time":4294967295,"preferred_life_time":4294967295},{"family":"inet6","local":"fd00:10:96::46e","prefixlen":128,"scope":"global","valid_life_time":4294967295,"preferred_life_time":4294967295},{"family":"inet6","local":"fd00:10:96::13a6","prefixlen":128,"scope":"global","valid_life_time":4294967295,"preferred_life_time":4294967295},{"family":"inet6","local":"fd00:10:96::9c47","prefixlen":128,"scope":"global","valid_life_time":4294967295,"preferred_life_time":4294967295},{"family":"inet6","local":"fd00:10:96::89c","prefixlen":128,"scope":"global","valid_life_time":4294967295,"preferred_life_time":4294967295},{"family":"inet6","local":"fd00:10:96::1","prefixlen":128,"scope":"global","valid_life_time":4294967295,"preferred_life_time":4294967295},{"family":"inet6","local":"fd00:10:96::a","prefixlen":128,"scope":"global","valid_life_time":4294967295,"preferred_life_time":4294967295}]},{"ifindex":3,"ifname":"ovs-system","flags":["BROADCAST","MULTICAST"],"mtu":1500,"qdisc":"noop","operstate":"DOWN","group":"default","txqlen":1000,"link_type":"ether","address":"a6:1c:c7:81:e1:52","broadcast":"ff:ff:ff:ff:ff:ff","promiscuity":1,"min_mtu":68,"max_mtu":65535,"linkinfo":{"info_kind":"openvswitch"},"num_tx_queues":1,"num_rx_queues":1,"gso_max_size":65536,"gso_max_segs":65535,"addr_info":[]},{"ifindex":4,"ifname":"br-int","flags":["BROADCAST","MULTICAST"],"mtu":1380,"qdisc":"noop","operstate":"DOWN","group":"default","txqlen":1000,"link_type":"ether","address":"be:0c:25:d8:e4:9c","broadcast":"ff:ff:ff:ff:ff:ff","promiscuity":1,"min_mtu":68,"max_mtu":65535,"linkinfo":{"info_kind":"openvswitch"},"num_tx_queues":1,"num_rx_queues":1,"gso_max_size":65536,"gso_max_segs":65535,"addr_info":[]},{"ifindex":5,"link_index":6,"ifname":"eth0","flags":["BROADCAST","MULTICAST","UP","LOWER_UP"],"mtu":1500,"qdisc":"noqueue","operstate":"UP","group":"default","link_type":"ether","address":"02:42:ac:12:00:02","broadcast":"ff:ff:ff:ff:ff:ff","link_netnsid":0,"promiscuity":0,"min_mtu":68,"max_mtu":65535,"linkinfo":{"info_kind":"veth"},"num_tx_queues":2,"num_rx_queues":2,"gso_max_size":65536,"gso_max_segs":65535,"addr_info":[{"family":"inet","local":"<IP_ADDRESS>","prefixlen":16,"broadcast":"<IP_ADDRESS>","scope":"global","label":"eth0","valid_life_time":4294967295,"preferred_life_time":4294967295},{"family":"inet6","local":"fc00:f853:ccd:e793::2","prefixlen":64,"scope":"global","nodad":true,"valid_life_time":4294967295,"preferred_life_time":4294967295},{"family":"inet6","local":"fe80::42:acff:fe12:2","prefixlen":64,"scope":"link","valid_life_time":4294967295,"preferred_life_time":4294967295}]},{"ifindex":6,"ifname":"mirror0","flags":["BROADCAST","MULTICAST","UP","LOWER_UP"],"mtu":1380,"qdisc":"noqueue","operstate":"UNKNOWN","group":"default","txqlen":1000,"link_type":"ether","address":"a2:91:00:eb:a3:a7","broadcast":"ff:ff:ff:ff:ff:ff","promiscuity":1,"min_mtu":68,"max_mtu":65535,"linkinfo":{"info_kind":"openvswitch"},"num_tx_queues":1,"num_rx_queues":1,"gso_max_size":65536,"gso_max_segs":65535,"addr_info":[{"family":"inet6","local":"fe80::a091:ff:feeb:a3a7","prefixlen":64,"scope":"link","valid_life_time":4294967295,"preferred_life_time":4294967295}]},{"ifindex":7,"ifname":"genev_sys_6081","flags":["BROADCAST","MULTICAST","UP","LOWER_UP"],"mtu":65000,"qdisc":"noqueue","master":"ovs-system","operstate":"UNKNOWN","group":"default","txqlen":1000,"link_type":"ether","address":"7a:98:c6:f9:eb:8b","broadcast":"ff:ff:ff:ff:ff:ff","promiscuity":1,"min_mtu":68,"max_mtu":65465,"linkinfo":{"info_kind":"geneve","info_data":{"external":true,"id":0,"ttl":0,"df":"unset","port":6081,"udp_zero_csum6_rx":true},"info_slave_kind":"openvswitch"},"num_tx_queues":1,"num_rx_queues":1,"gso_max_size":65536,"gso_max_segs":65535,"addr_info":[{"family":"inet6","local":"fe80::7898:c6ff:fef9:eb8b","prefixlen":64,"scope":"link","valid_life_time":4294967295,"preferred_life_time":4294967295}]},{"ifindex":8,"ifname":"ovn0","flags":["BROADCAST","MULTICAST","UP","LOWER_UP"],"mtu":1380,"qdisc":"noqueue","operstate":"UNKNOWN","group":"default","txqlen":1000,"link_type":"ether","address":"00:00:00:25:1f:92","broadcast":"ff:ff:ff:ff:ff:ff","promiscuity":1,"min_mtu":68,"max_mtu":65535,"linkinfo":{"info_kind":"openvswitch"},"num_tx_queues":1,"num_rx_queues":1,"gso_max_size":65536,"gso_max_segs":65535,"addr_info":[{"family":"inet6","local":"fd00:100:64::2","prefixlen":64,"scope":"global","valid_life_time":4294967295,"preferred_life_time":4294967295},{"family":"inet6","local":"fe80::200:ff:fe25:1f92","prefixlen":64,"scope":"link","valid_life_time":4294967295,"preferred_life_time":4294967295}]},{"ifindex":16,"link_index":15,"ifname":"c7cb1ab258c2_h","flags":["BROADCAST","MULTICAST","UP","LOWER_UP"],"mtu":1380,"qdisc":"noqueue","master":"ovs-system","operstate":"UP","group":"default","txqlen":1000,"link_type":"ether","address":"ba:65:05:c3:84:8b","broadcast":"ff:ff:ff:ff:ff:ff","link_netnsid":2,"promiscuity":1,"min_mtu":68,"max_mtu":65535,"linkinfo":{"info_kind":"veth","info_slave_kind":"openvswitch"},"num_tx_queues":2,"num_rx_queues":2,"gso_max_size":65536,"gso_max_segs":65535,"addr_info":[{"family":"inet6","local":"fe80::b865:5ff:fec3:848b","prefixlen":64,"scope":"link","valid_life_time":4294967295,"preferred_life_time":4294967295}]},{"ifindex":20,"link_index":21,"ifname":"eth3","flags":["BROADCAST","MULTICAST","UP","LOWER_UP"],"mtu":1500,"qdisc":"noqueue","operstate":"UP","group":"default","link_type":"ether","address":"02:42:ac:13:00:03","broadcast":"ff:ff:ff:ff:ff:ff","link_netnsid":0,"promiscuity":0,"min_mtu":68,"max_mtu":65535,"linkinfo":{"info_kind":"veth"},"num_tx_queues":2,"num_rx_queues":2,"gso_max_size":65536,"gso_max_segs":65535,"addr_info":[{"family":"inet","local":"<IP_ADDRESS>","prefixlen":16,"broadcast":"<IP_ADDRESS>","scope":"global","label":"eth3","valid_life_time":4294967295,"preferred_life_time":4294967295},{"family":"inet6","local":"fc00:adb1:b29b:608d::3","prefixlen":64,"scope":"global","nodad":true,"valid_life_time":4294967295,"preferred_life_time":4294967295},{"family":"inet6","local":"fe80::42:acff:fe13:3","prefixlen":64,"scope":"link","tentative":true,"valid_life_time":4294967295,"preferred_life_time":4294967295}]}]

    Mar  1 08:04:27.497: INFO: stderr:
    Mar  1 08:04:27.498: INFO: Executing command "ip -d -j route show" in container ca81da5e5f711f0fe5ee792cfb1a7c7f2c651bf0692ad141919ea7e7dcafefc6
    Mar  1 08:04:27.556: INFO: stdout: [{"type":"unicast","dst":"default","gateway":"<IP_ADDRESS>","dev":"eth0","protocol":"boot","scope":"global","flags":[]},{"type":"unicast","dst":"<IP_ADDRESS>/16","dev":"eth0","protocol":"kernel","scope":"link","prefsrc":"<IP_ADDRESS>","flags":[]},{"type":"unicast","dst":"<IP_ADDRESS>/16","dev":"eth3","protocol":"kernel","scope":"link","prefsrc":"<IP_ADDRESS>","flags":[]}]

    Mar  1 08:04:27.556: INFO: stderr:
    Mar  1 08:04:27.556: INFO: Executing command "ip -d -j -6 route show" in container ca81da5e5f711f0fe5ee792cfb1a7c7f2c651bf0692ad141919ea7e7dcafefc6
    Mar  1 08:04:27.616: INFO: stdout: [{"type":"unicast","dst":"fc00:adb1:b29b:608d::/64","dev":"eth3","protocol":"kernel","scope":"global","metric":256,"flags":[],"pref":"medium"},{"type":"unicast","dst":"fc00:f853:ccd:e793::/64","dev":"eth0","protocol":"kernel","scope":"global","metric":256,"flags":[],"pref":"medium"},{"type":"unicast","dst":"fd00:10:16::/64","gateway":"fd00:100:64::1","dev":"ovn0","protocol":"boot","scope":"global","prefsrc":"fc00:f853:ccd:e793::2","metric":1024,"flags":[],"pref":"medium"},{"type":"unicast","dst":"fd00:100:64::/64","dev":"ovn0","protocol":"kernel","scope":"global","metric":256,"flags":[],"pref":"medium"},{"type":"unicast","dst":"fe80::/64","dev":"eth0","protocol":"kernel","scope":"global","metric":256,"flags":[],"pref":"medium"},{"type":"unicast","dst":"fe80::/64","dev":"mirror0","protocol":"kernel","scope":"global","metric":256,"flags":[],"pref":"medium"},{"type":"unicast","dst":"fe80::/64","dev":"genev_sys_6081","protocol":"kernel","scope":"global","metric":256,"flags":[],"pref":"medium"},{"type":"unicast","dst":"fe80::/64","dev":"ovn0","protocol":"kernel","scope":"global","metric":256,"flags":[],"pref":"medium"},{"type":"unicast","dst":"fe80::/64","dev":"c7cb1ab258c2_h","protocol":"kernel","scope":"global","metric":256,"flags":[],"pref":"medium"},{"type":"unicast","dst":"fe80::/64","dev":"eth3","protocol":"kernel","scope":"global","metric":256,"flags":[],"pref":"medium"},{"type":"unicast","dst":"default","gateway":"fc00:f853:ccd:e793::1","dev":"eth0","protocol":"boot","scope":"global","metric":1024,"flags":[],"pref":"medium"}]

    Mar  1 08:04:27.616: INFO: stderr:
    [It] should support underlay to overlay subnet interconnection  [Conformance]
      /home/runner/work/kube-ovn/kube-ovn/test/e2e/kube-ovn/underlay/underlay.go:438
    STEP: Creating provider network 03/01/23 08:04:27.616
    STEP: Getting docker network kube-ovn-vlan 03/01/23 08:04:41.69
    STEP: Creating vlan vlan-12908 03/01/23 08:04:41.692
    STEP: Creating underlay subnet subnet-15715 03/01/23 08:04:41.707
    Mar  1 08:04:41.710: INFO: Waiting up to 2m0s for subnet subnet-15715 condition Ready to be true
    Mar  1 08:04:41.731: INFO: Couldn't find condition Ready on subnet subnet-15715
    STEP: Creating underlay subnet pod 03/01/23 08:04:43.738
    Mar  1 08:04:43.744: INFO: Waiting up to 5m0s for pod "pod-14919" in namespace "underlay-4966" to be "running and ready"
    Mar  1 08:04:43.753: INFO: Pod "pod-14919": Phase="Pending", Reason="", readiness=false. Elapsed: 9.119118ms
    Mar  1 08:04:43.753: INFO: The phase of Pod pod-14919 is Pending, waiting for it to be Running (with Ready = true)
    Mar  1 08:04:45.758: INFO: Pod "pod-14919": Phase="Pending", Reason="", readiness=false. Elapsed: 2.014028252s
    Mar  1 08:04:45.758: INFO: The phase of Pod pod-14919 is Pending, waiting for it to be Running (with Ready = true)
    Mar  1 08:04:47.758: INFO: Pod "pod-14919": Phase="Pending", Reason="", readiness=false. Elapsed: 4.014082531s
    Mar  1 08:04:47.758: INFO: The phase of Pod pod-14919 is Pending, waiting for it to be Running (with Ready = true)
    Mar  1 08:09:43.757: INFO: Pod "pod-14919": Phase="Pending", Reason="", readiness=false. Elapsed: 5m0.013165713s
    Mar  1 08:09:43.757: INFO: The phase of Pod pod-14919 is Pending, waiting for it to be Running (with Ready = true)
    Mar  1 08:09:43.759: INFO: Pod "pod-14919": Phase="Pending", Reason="", readiness=false. Elapsed: 5m0.015273223s
    Mar  1 08:09:43.759: INFO: The phase of Pod pod-14919 is Pending, waiting for it to be Running (with Ready = true)
    Mar  1 08:09:43.760: INFO: Unexpected error:
        <*pod.timeoutError | 0xc0013f1e90>: {
            msg: "timed out while waiting for pod underlay-4966/pod-14919 to be running and ready",
            observedObjects: [
                <*v1.Pod | 0xc000ea4d80>{
                    TypeMeta: {Kind: "", APIVersion: ""},
                    ObjectMeta: {
                        Name: "pod-14919",
                        GenerateName: "",
                        Namespace: "underlay-4966",
                        SelfLink: "",
                        UID: "16e2aeee-cb39-4128-b203-b697c2961cba",
                        ResourceVersion: "3954",
                        Generation: 0,
                        CreationTimestamp: {
                            Time: {
                                wall: 0,
                                ext:<PHONE_NUMBER>3,
                                loc: {
                                    name: "Local",
                                    zone: [
                                        {name: "UTC", offset: 0, isDST: false},
                                    ],
                                    tx: [
                                        {
                                            when: -9223372036854775808,
                                            index: 0,
                                            isstd: false,
                                            isutc: false,
                                        },
                                    ],
                                    extend: "UTC0",
                                    cacheStart:<PHONE_NUMBER>854775807,
                                    cacheEnd:<PHONE_NUMBER>854775807,
                                    cacheZone: {name: "UTC", offset: 0, isDST: false},
                                },
                            },
                        },
                        DeletionTimestamp: nil,
                        DeletionGracePeriodSeconds: nil,
                        Labels: nil,
                        Annotations: {
                            "ovn.kubernetes.io/cidr": "fc00:adb1:b29b:608d::/64",
                            "ovn.kubernetes.io/ip_address": "fc00:adb1:b29b:608d::5",
                            "ovn.kubernetes.io/logical_router": "ovn-cluster",
                            "ovn.kubernetes.io/mac_address": "00:00:00:47:55:47",
                            "ovn.kubernetes.io/allocated": "true",
                            "ovn.kubernetes.io/gateway": "fc00:adb1:b29b:608d::1",
                            "ovn.kubernetes.io/logical_switch": "subnet-15715",
                            "ovn.kubernetes.io/pod_nic_type": "veth-pair",
                            "ovn.kubernetes.io/routed": "true",
                        },
                        OwnerReferences: nil,
                        Finalizers: nil,
                        ManagedFields: [
                            {
                                Manager: "kube-ovn-controller",
                                Operation: "Update",
                                APIVersion: "v1",
                                Time: {
                                    Time: {
                                        wall: 0,
                                        ext:<PHONE_NUMBER>3,
                                        loc: {
                                            name: "Local",
                                            zone: [...],
                                            tx: [...],
                                            extend: "UTC0",
                                            cacheStart:<PHONE_NUMBER>854775807,
                                            cacheEnd:<PHONE_NUMBER>854775807,
                                            cacheZone: {name: ..., offset: ..., isDST: ...},
                                        },
                                    },
                                },
                                FieldsType: "FieldsV1",
                                FieldsV1: {
                                    Raw: "{\"f:metadata\":{\"f:annotations\":{\"f:ovn.kubernetes.io/allocated\":{},\"f:ovn.kubernetes.io/cidr\":{},\"f:ovn.kubernetes.io/gateway\":{},\"f:ovn.kubernetes.io/ip_address\":{},\"f:ovn.kubernetes.io/logical_router\":{},\"f:ovn.kubernetes.io/mac_address\":{},\"f:ovn.kubernetes.io/pod_nic_type\":{},\"f:ovn.kubernetes.io/routed\":{}}}}",
                                },
                                Subresource: "",
                            },
                            {
                                Manager: "kube-ovn.test",
                                Operation: "Update",
                                APIVersion: "v1",
                                Time: {
                                    Time: {
                                        wall: 0,
                                        ext:<PHONE_NUMBER>3,
                                        loc: {
                                            name: "Local",
                                            zone: [...],
                                            tx: [...],
                                            extend: "UTC0",
                                            cacheStart:<PHONE_NUMBER>854775807,
                                            cacheEnd:<PHONE_NUMBER>854775807,
                                            cacheZone: {name: ..., offset: ..., isDST: ...},
                                        },
                                    },
                                },
                                FieldsType: "FieldsV1",
                                FieldsV1: {
                                    Raw: "{\"f:metadata\":{\"f:annotations\":{\".\":{},\"f:ovn.kubernetes.io/logical_switch\":{}}},\"f:spec\":{\"f:containers\":{\"k:{\\\"name\\\":\\\"container\\\"}\":{\".\":{},\"f:args\":{},\"f:image\":{},\"f:imagePullPolicy\":{},\"f:name\":{},\"f:resources\":{},\"f:terminationMessagePath\":{},\"f:terminationMessagePolicy\":{}}},\"f:dnsPolicy\":{},\"f:enableServiceLinks\":{},\"f:restartPolicy\":{},\"f:schedulerName\":{},\"f:securityContext\":{},\"f:terminationGracePeriodSeconds\":{}}}",
                                },
                                Subresource: "",
                            },
                            {
                                Manager: "kubelet",
                                Operation: "Update",
                                APIVersion: "v1",
                                Time: {
                                    Time: {
                                        wall: 0,
                                        ext:<PHONE_NUMBER>3,
                                        loc: {
                                            name: "Local",
                                            zone: [...],
                                            tx: [...],
                                            extend: "UTC0",
                                            cacheStart:<PHONE_NUMBER>854775807,
                                            cacheEnd:<PHONE_NUMBER>854775807,
                                            cacheZone: {name: ..., offset: ..., isDST: ...},
                                        },
                                    },
                                },
                                FieldsType: "FieldsV1",
                                FieldsV1: {
                                    Raw: "{\"f:status\":{\"f:conditions\":{\"k:{\\\"type\\\":\\\"ContainersReady\\\"}\":{\".\":{},\"f:lastProbeTime\":{},\"f:lastTransitionTime\":{},\"f:message\":{},\"f:reason\":{},\"f:status\":{},\"f:type\":{}},\"k:{\\\"type\\\":\\\"Initialized\\\"}\":{\".\":{},\"f:lastProbeTime\":{},\"f:lastTransitionTime\":{},\"f:status\":{},\"f:type\":{}},\"k:{\\\"type\\\":\\\"Ready\\\"}\":{\".\":{},\"f:lastProbeTime\":{},\"f:lastTransitionTime\":{},\"f:message\":{},\"f:reason\":{},\"f:status\":{},\"f:type\":{}}},\"f:containerStatuses\":{},\"f:hostIP\":{},\"f:startTime\":{}}}",
                                },
                                Subresource: "status",
                            },
                        ],
                    },
                    Spec: {
                        Volumes: [
                            {
                                Name: "kube-api-access-lr2gf",
                                VolumeSource: {
                                    HostPath: nil,
                                    EmptyDir: nil,
                                    GCEPersistentDisk: nil,
                                    AWSElasticBlockStore: nil,
                   ...

    Gomega truncated this representation as it exceeds 'format.MaxLength'.
    Consider having the object provide a custom 'GomegaStringer' representation
    or adjust the parameters in Gomega's 'format' package.

    Learn more here: https://onsi.github.io/gomega/#adjusting-output

    Mar  1 08:09:43.760: FAIL: timed out while waiting for pod underlay-4966/pod-14919 to be running and ready

    Full Stack Trace
    k8s.io/kubernetes/test/e2e/framework/pod.(*PodClient).CreateSync(0xc000e12cf0, 0xc0016a6000?)
    	/home/runner/go/pkg/mod/k8s.io/kubernetes@v1.26.2/test/e2e/framework/pod/pod_client.go:107 +0x94
    github.com/kubeovn/kube-ovn/test/e2e/kube-ovn/underlay.glob..func1.7()
    	/home/runner/work/kube-ovn/kube-ovn/test/e2e/kube-ovn/underlay/underlay.go:495 +0x10a5
    github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x0, 0x0})
    	/home/runner/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.4.0/internal/node.go:449 +0x1b
    github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func2()
    	/home/runner/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.4.0/internal/suite.go:750 +0x98
    created by github.com/onsi/ginkgo/v2/internal.(*Suite).runNode
    	/home/runner/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.4.0/internal/suite.go:738 +0xe3d
    [AfterEach] [CNI:Kube-OVN] [group:underlay]
      /home/runner/work/kube-ovn/kube-ovn/test/e2e/kube-ovn/underlay/underlay.go:260
    STEP: Deleting pod pod-17487 03/01/23 08:09:43.761
    Mar  1 08:09:43.764: INFO: Waiting for pod pod-17487 to disappear
    Mar  1 08:09:43.766: INFO: Pod pod-17487 no longer exists
    STEP: Deleting underlay pod pod-14919 03/01/23 08:09:43.766
    Mar  1 08:09:43.773: INFO: Waiting for pod pod-14919 to disappear
    Mar  1 08:09:43.775: INFO: Pod pod-14919 still exists
    Mar  1 08:11:31.777: INFO: Waiting for pod pod-14919 to disappear
    Mar  1 08:11:31.782: INFO: Pod pod-14919 no longer exists
    STEP: Deleting overlay pod  03/01/23 08:11:31.782
    Mar  1 08:11:31.782: FAIL: Failed to delete pod "": resource name may not be empty

    Full Stack Trace
    k8s.io/kubernetes/test/e2e/framework/pod.(*PodClient).DeleteSync(0xc000e12cf0, {0x0, 0x0}, {{{0x0, 0x0}, {0x0, 0x0}}, 0x0, 0x0, 0x0, ...}, ...)
    	/home/runner/go/pkg/mod/k8s.io/kubernetes@v1.26.2/test/e2e/framework/pod/pod_client.go:183 +0x195
    github.com/kubeovn/kube-ovn/test/e2e/framework.(*PodClient).DeleteSync(...)
    	/home/runner/work/kube-ovn/kube-ovn/test/e2e/framework/pod.go:25
    github.com/kubeovn/kube-ovn/test/e2e/kube-ovn/underlay.glob..func1.2()
    	/home/runner/work/kube-ovn/kube-ovn/test/e2e/kube-ovn/underlay/underlay.go:275 +0x2c5
    github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0xa84ece, 0xc0008bbc80})
    	/home/runner/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.4.0/internal/node.go:449 +0x1b
    github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func2()
    	/home/runner/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.4.0/internal/suite.go:750 +0x98
    created by github.com/onsi/ginkgo/v2/internal.(*Suite).runNode
    	/home/runner/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.4.0/internal/suite.go:738 +0xe3d
    [DeferCleanup (Each)] [CNI:Kube-OVN] [group:underlay]
      dump namespaces | framework.go:196
    STEP: dump namespace information after failure 03/01/23 08:11:31.783
    [DeferCleanup (Each)] [CNI:Kube-OVN] [group:underlay]
      tear down framework | framework.go:193
    STEP: Destroying namespace "underlay-4966" for this suite. 03/01/23 08:11:31.783
  << End Captured GinkgoWriter Output

  Mar  1 08:09:43.760: timed out while waiting for pod underlay-4966/pod-1[491](https://github.com/kubeovn/kube-ovn/actions/runs/4301158673/jobs/7498268970#step:15:492)9 to be running and ready
  In [It] at: /home/runner/go/pkg/mod/k8s.io/kubernetes@v1.26.2/test/e2e/framework/pod/pod_client.go:107

  There were additional failures detected after the initial failure.  Here's a summary - for full details run Ginkgo in verbose mode:
    [FAILED] in [AfterEach] at /home/runner/go/pkg/mod/k8s.io/kubernetes@v1.26.2/test/e2e/framework/pod/pod_client.go:183
    [PANICKED] in [DeferCleanup (Each)] at /opt/hostedtoolcache/go/1.20.1/x64/src/runtime/panic.go:260

第一个问题可以加等待再看看，像是创建pod后 subnet的字段还没来得及同步。
第二个问题这个还没进入测试就是创建了一个underlay subnet，再创建一个pod发现ping gateway不通，导致pod没起来，可能是环境有问题，看会不会复现。


nixos/base16-schemes unstable-2022-12-16 -> unstable-2023-05-02

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@apfelkuchen6 how would i combine the commits?

@TotalChaos05: Search for "git squash" on the web, you will find different solutions among which:

either use git reset to delete all your commits but keep your changes and then make 1 commit
or use git rebase interactively and ask git to "squash" commits

I can do it for you if you don't want to.

@DamienCassou did that work?

@TotalChaos05: everything went well, good job. The only remaining problem is the missing colon : after the package name in the commit message. See https://nixos.org/manual/nixpkgs/stable/#submitting-changes-making-patches.

sorry about all that :')

Result of nixpkgs-review pr 238995 run on x86_64-linux 1

1 package built:

base16-schemes

@TotalChaos05: There is nothing to be sorry about. Thank you for your work. Your next PR will be much easier to get merged! :-)


Added logging to end of Job._scheduled_next_run() method

Relating to issue #228.

Coverage remained the same at 100.0% when pulling d14bb83a5907855dbc28dca7caa90112e286e724 on inkychris:issue-228-scheduled-next-run-logging into cd890d055b9dbd6dcbc697f2eda397e2e47a1d77 on dbader:master.


Refactor pointer handling

Big changes to memory management
This is the first step towards a safer memory management: stuff allocated by Rust are returned wrapped into a particular kind of object, so that it can later (with some other updates that will follow) be dropped by Rust.
No more pointer-of-pointer getting dereferenced and assigned.
At the moment everything is returned in a slice because otherwise there would be issues with non-typed structs. Hopefully with some extra mind-twisting macros we can remove the rgb_as_ptr C macro and directly return ptrs.

Next up is a safe mechanism to free Rust-allocated memory and then we should be ready to merge.
I tried doing something with C macros but I found out that typeof() is expanded after macros are substituted (obviously, I forgot about that), so one generic rgb_free() macro seems unfeasible at the moment.
It's more likely going to be something along the lines of rgb_free(ptr, type) and the macro will try to check that ptr is actually a type* before calling a specific Rust function to free that pointer.
More updates tonight!


Revert "Rename DefaultTextStyle constructor to explicit (#3920)"

This reverts commit 55f9145ef4fb7a7f4b4738740d5848ff745ae076.
Turns out that this commit breaks apps that use the material library,
because of the _errorTextStyle DefaultTextStyle which has inherit:true.
Just setting it to false doesn't work, unfortunately, because then you
hit some sort of issue with merging that text style with others that
have inherit:true.
TBR=@abarth to clear the tree

LGTM


Removing stopPropagation

Hello, I'm using the slider inside a sweetalert2 modal and have a problem with users trying to slide to the min or max value and accidentally closing the modal.
Clicking and sliding to min/max value with the mouse going outside the modal then releasing the click will close the modal because of click event on background overlay.
Removing stopPropagation fixes the issue because sweetalert2/boostrap knows if the background overlay click was intended or not based on mousedown/mouseup.
Made some tests with stopPropagation removed and seems to work correctly. Will a pull request with this change be merged?
https://css-tricks.com/dangers-stopping-event-propagation/
Expected behaviour
The mousedown events should propagate upwards.
Actual behaviour
The mousedown events don't propagate because stopPropagation is called.

In ionic, there is an event attached to swipe left/right to show/hide side menu. Removing event.stopPropagation() on start causes opening of side menu when the slider is dragged to right. There can be many different cases or framework which has an event attached to swipe especially for mobile application, I am not sure removing event.stopPropagation() from the library was a good idea because now every developer who uses this library for mobile apps will have to write onStart option to ensure event.stopPropagation(); to prevent side menu from opening.
To solve this I have added an option for slider configuration.
options: {                 onStart: function () {                     event.stopPropagation();                 }, }

Hey @stripathix you could solve this with the following options:
onStart: function () {
    $ionicSideMenuDelegate.canDragContent(false);
},
onEnd: function () {
    $ionicSideMenuDelegate.canDragContent(true);
}

Take a look at this example: http://jsfiddle.net/313p8bag/15/

Since 6.4.4 the slider behavior went bad for my application: instead of only dragging the slider it also started dragging the whole block wich was draggable with angular ui sortable, however for now I just set bower to keep 6.4.3 so I am able to keep using this... Imo This (and 6.4.4) with removing the stoppropagation, is a breaking change

@ValentinH  @andreeib I do use that configuration to stop Ionic canDrag when slider drag starts, but I would say that performance is not that smooth as it used to be. Many a time I can see that due to slider drag menu does open. This happens when quicky strat drag/stop drag then starts drag of the slider.
The performance with stopPropogation was really smooth.

OK I will rollback this then.

Best solution is to make this an optional option paramter I think. Something like DisableStopPropogation, then it should be default like it was before 6.4.3 so people can override it, if they have other needs. (Just a suggestion)

Yes definitely agreed. To be quick, I just reverted the commit that had removed the stopPropagation.
@andreeib , if you still need this, could you resubmit your PR and add the option mentionned by @MaximCrabbe ?

6.5.1 fixes your issues @MaximCrabbe @stripathix

@ValentinH Thanks :-)


Any tries to kill the so created process will leave the child process running. See the following snippet:
// This file is 'runner.dart'
import 'dart:io';

void main(List<String> args) async {
  bool killed = false;
  ProcessSignal.sigterm.watch().listen((event) {
    print('[$pid] SIGTERM received.');
    killed = true;
  });

  if (args.firstOrNull == '--child') {
    int iter = 0;

    while (!killed) {
      print("[$pid] Child iteration: $iter");
      await Future.delayed(Duration(seconds: 1));
      iter++;
    }
    return;
  }

  print("[$pid] Starting child...");
  var p = await Process.start('dart', ['run', 'runner.dart', '--child']);
  p.stdout.pipe(stdout);
  p.stderr.pipe(stderr);
  print("[$pid] Started ${p.pid}.");

  await Future.delayed(Duration(seconds: 5));

  print("[$pid] Killing child...");
  p.kill();
  // These have the same outcome:
  // Process.killPid(p.pid);
  // Process.runSync('kill', ['${p.pid}']);
  print("[$pid] Killed.");
}

The output of running `dart run runner.dart' outputs:
[67301] Starting child...
[67301] Started 67302.
[67316] Child iteration: 0
[67316] Child iteration: 1
[67316] Child iteration: 2
[67316] Child iteration: 3
[67316] Child iteration: 4
[67301] Killing child...
[67301] Killed.
[67316] Child iteration: 5
[67316] Child iteration: 6
[67316] Child iteration: 7
[67316] Child iteration: 8
[67316] Child iteration: 9

where the child iterations continue forever (until manually killed).
Expected output would look like:
[67301] Starting child...
[67301] Started 67302.
[67316] Child iteration: 0
[67316] Child iteration: 1
[67316] Child iteration: 2
[67316] Child iteration: 3
[67316] Child iteration: 4
[67301] Killing child...
[67316] SIGTERM received
[67301] Killed.

It seems like the dart run command does not properly send through termination signals to its target process.

I have a feeling this isn't a problem specific to dart run, just how processes spawned via dart:io are handled. @schultek what platform are you running on? Would you mind providing the output of dart info?

cc @brianquinlan and @a-siva who probably have the most context on this behavior these days.

@bkonyi, I don't believe this is the same issue that we were discussing last week. The change to use external processes for the 'run' command has not landed yet.

@schultek what platform are you running on? Would you mind providing the output of dart info?

General info

Dart 3.3.1 (stable) (Wed Mar 6 13:09:19 2024 +0000) on "macos_arm64"
on macos / Version 14.1 (Build 23B74)
locale is de-DE

Process info

Memory
CPU
Elapsed time
Command line

5653 MB
0.0%
18:50:36
dart language-server --client-id=IntelliJ-IDEA --client-version=IU-232.10203.10 --protocol=analyzer

42 MB
0.0%
19:50:19
dart run runner.dart

42 MB
0.0%
19:50:18
dart run runner.dart --child

42 MB
0.0%
19:46:52
dart run runner.dart --child

42 MB
0.0%
19:45:13
dart run runner.dart --child

64 MB
0.0%
02-20:32:32
flutter_tools.snapshot daemon

I have a feeling this isn't a problem specific to dart run, just how processes spawned via dart:io are handled

I think it does. When I compile the programm to an executable and change the line to
- var p = await Process.start('dart', ['run', 'runner.dart', '--child']);
+ var p = await Process.start('./runner', ['--child']);

then it behaves as expected:
[82927] Starting child...
[82927] Started 82928.
[82928] Child iteration: 0
[82928] Child iteration: 1
[82928] Child iteration: 2
[82928] Child iteration: 3
[82928] Child iteration: 4
[82927] Killing child...
[82927] Killed.
[82928] SIGTERM received.

I tried the example provided above on main branch of Dart
(Dart SDK version: 3.4.0-edge.db1b6018caed19d10d81774278e6515162237dd9 (main) (Fri Mar 15 18:09:29 2024 +0000) on "macos_x64")
and I get the following output
asiva-macbookpro1:sdk asiva$ xcodebuild/ReleaseX64/dart-sdk/bin/dart /tmp/runner1.dart parent
[86893] Starting child...
[86893] Started 86906.
[86906] Child iteration: 0
[86906] Child iteration: 1
[86906] Child iteration: 2
[86906] Child iteration: 3
[86906] Child iteration: 4
[86893] Killing child...
[86893] Killed.
[86906] SIGTERM received.

The two process (parent and child) do not die as we have the watch signal watch method still watching for signals (both parent and child).
I changed the signal handler as follows
ProcessSignal.sigterm.watch().listen((event) {
    print('[$pid] SIGTERM received.');
    killed = true;
    exit(0);
  });

and the child process dies.
We don't have a way of explicitly cancelling the signal watching.
Re writing the code as follows makes it work
import 'dart:io';

void main(List<String> args) async {
  bool killed = false;

  if (args.firstOrNull == '--child') {
    int iter = 0;
    ProcessSignal.sigterm.watch().listen((event) {
      print('[$pid] SIGTERM received.');
      killed = true;
      exit(0);
    });

    while (!killed) {
      print("[$pid] Child iteration: $iter");
      await Future.delayed(Duration(seconds: 1));
      iter++;
    }
    return;
  }

  print("[$pid] Starting child...");
  var p = await Process.start(Platform.executable, ['run', '/tmp/runner1.dart', '--child']);
  p.stdout.pipe(stdout);
  p.stderr.pipe(stderr);
  print("[$pid] Started ${p.pid}.");

  await Future.delayed(Duration(seconds: 5));

  print("[$pid] Killing child...");
  p.kill();
  // These have the same outcome:
  // Process.killPid(p.pid);
  // Process.runSync('kill', ['${p.pid}']);
  print("[$pid] Killed.");
}

@schultek I tried your example on the latest version of Dart and it appears to work, I made a slight modification to your code to cancel the subscription, see below
import 'dart:async';
import 'dart:io';

late StreamSubscription subscription;

main(List<String> args) async {
  bool killed = false;
  subscription = ProcessSignal.sigterm.watch().listen((event) {
    print('[$pid] SIGTERM received.');
    killed = true;
    print('[$pid] set killed to $killed');
    subscription.cancel();
  });

  if (args.first == '--child') {
    int iter = 0;

    while (!killed) {
      print("[$pid] Child iteration: $iter");
      await Future.delayed(Duration(seconds: 1));
      iter++;
    }
    return;
  }

  print("[$pid] Starting child...");
  var p = await Process.start(Platform.executable, ['run', '/usr/local/google/home/asiva/tmp/runner.dart
', '--child']);
  p.stdout.pipe(stdout);
  p.stderr.pipe(stderr);
  print("[$pid] Started ${p.pid}.");

  await Future.delayed(Duration(seconds: 5));

  print("[$pid] Killing child...");
  p.kill();
  print("[$pid] Killed.");
  subscription.cancel();
}

and it works as expected
[2176902] Starting child...
[2176902] Started 2176913.
[2176922] Child iteration: 0
[2176922] Child iteration: 1
[2176922] Child iteration: 2
[2176922] Child iteration: 3
[2176922] Child iteration: 4
[2176902] Killing child...
[2176902] Killed.
sigterm watcher called

Closing issue, if you think there is still an issue please reopen.


Pokemon Go 0.31.0 location doesn't work

On cellular data: "GPS signal not found"
On Wifi: With location disabled, game loads but "GPS signal not found". App crashes when location turned on in phone settings.
Previous versions of Pokemon Go worked fine but now the update is enforced.

Same issue for me with latest stable and unstable releases with CyanogenMod 13 (Android 6.0.1) on a Redmi Note 3 Pro Prime (Kenzo) phone.

could it be that the version 0.31.0 does in general only work with GPS turned on?
have you tried that version on a phone with real google play services?

I forgot to say that v0.31.0 also crashes with "GPS only" activated. No only with "High accuracy" mode.

Are you on 0.2.4 or 0.2.4-3? See #159

^yes... Updating to latest preview release worked. Thanks and sorry, this was a duplicate of #159
(I didn't realise that the latest versions weren't in Fdroid while https://microg.org was also down)

Oops... Fixed by updating to latest preview. Latest versions should be in Fdroid for more visibility.
IMO you can close this issue.


HTML head title attribute not set correctly

FlowRouter does not set the title correctly (stays when navigating between pages).

Iron router can be used instead

@pmuens Is this still an open bug?  Looking at it now, it seems to be working.

Yes. Seems to be working. I'll close it for now. Thanks!


demo: Saturn:[ Looping Animation, live config] (Meshes)

Simple common animations like gears spinning, the fountain demo etc.
The specific one I want to recreate is: https://codepen.io/Yakudoo/pen/qbyga

as its not thousands I'm not sure we need to instance it or exactly how to play that out, I'll start with octo shapes or something.

[ ] Span
[ ] Persist
[ ] Animate
[ ] Respond to controls
[ ] size variance
[ ] color variance

Nice to have:

[ ] Shadows
[ ] Collisions (even fake)
[ ] User interaction

Link is 404 unfortunately

Link is 404 unfortunately

Link updated to personal fork: https://codepen.io/dennissmolek-the-selector/pen/oNEPXQr
Prob. a bad copy paste on my part.
The original creator: Karim Maaloul has a ton of amazing examples,

Hi, what is the actionable outcome of this issue?


clean up and standardize cwd/root behavior (incl. JS API)

Problem
When using the JS API (e.g. import { startDevServer } from 'snowpack';), the cwd option doesn‘t get passed through to the rest of snowpack, which poses a problem in a larger project. Consider the following scenario:
├── client/
│   ├── snowpack.config.js
│   └── src/
└── server/

Say a Snowpack project lives in client/, and inside snowpack.config.js, all the mounted folders point relatively within client/. Everything works fine when you‘re in that folder.
But if you import 'snowpack' inside server/, Snowpack can‘t find anything because it tries to resolve server/src/ which doesn‘t exist.
Proposed Solution
Fix the cwd option to all the Node API functions, like so:
startDevServer({
  cwd: __dirname
})

Currently, there is a cwd parameter, however, it doesn‘t get passed to the rest of the application. All the top-level methods should accept the cwd command, and this should override process.cwd() when it’s set:

snowpack.startDevServer()
snowpack.getUrlForFile()

When not set, it should fall back to its current value, process.cwd().

If alright, I'd like to take up and work on this issue!

@thescripted Sure! Please take a swing at it 🙂

@thescripted Drew and I were just talking about this, and I think we want to tackle this as a larger "what is the root in a Snowpack project?" Currently it is the process.cwd(), but for programatic usage (including our own testing needs) we want to turn this into a larger "root"/"resolveFrom" concept that sets the root of your project AND defaults to where your closest snowpack.config.js file lives.
We'd still love the help so if you're still interested in tackling, please let us know and we can provide guidance! The original post is still a part of this work (honor the "cwd" value in the JS API, and then rename it to "root" later). But otherwise, no worries if feels too big to bite off now.

I'm very interested in this, but I am stretched thin between my commitment to other work and my lack of knowledge in this space (and why I haven't updated much in this issue). This might be too big for me at the moment.
If, down the road, this or related issue gets broken down into multiple PRs I believe I could help out. Would also still love to find ways to contribute in general as well!

np, appreciate the offer to help! We're looking to get this out as a breaking change in v3, so @drwpow or @matthewp may be tackling sooner

@FredKSchott  Would love to give it a shot if this is still open!

Here's what I accomplished so far:
https://github.com/februarycat/snowpack/tree/Replace-process-cwd-with-configurable-root-option
I'm not 100% sure it's complete as I didn't have much time today to test it all. When I have some free time I'll check if I can replace the rest of the cwd instances in the code.
I'll be waiting to hear your thoughts on whether this is a good start for the refactor!

Awesome! I may actually be taking over this initiative instead of @drwpow or @matthewp, in which case I'd love to help you with your PR! I'll take a look later today and can provide feedback.
Can you create a draft PR of your branch? It will be easier for me to check out and leave feedback that way

Yep, here's the draft:
https://github.com/snowpackjs/snowpack/pull/1928

Oops, apparently Vercel is deploying everything on my account T_T. I'll take care of it tomorrow

Thanks for the PR @februarycat! I'm going to mark this issue as done now that #1928 is done.
There's still some work to do to resolve relative paths from the location of the loaded file itself, but not directly related to the new root config.


Is that path correct?

If I have read this correctly, then in the example about merging props file from the parent directory, should this line: <Import Project="$([MSBuild]::GetPathOfFileAbove('Directory.Build.props', '$(MSBuildThisFileDirectory)../'))" /> be changed to this: <Import Project="$([MSBuild]::GetPathOfFileAbove('Directory.Build.props', '$(MSBuildThisFileDirectory)'))" />

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

ID: d410ebeb-3841-a0a9-efb4-185823add4dc
Version Independent ID: 7e397179-4ccc-054c-8137-5e8f2430d794
Content: Customize your build | Microsoft Docs
Content Source: docs/msbuild/customize-your-build.md
Service: unspecified
GitHub Login: @Mikejo5000
Microsoft Alias: mikejo

@rainersigwald Rainer, can you verify this before I change it? Thanks.

I think it's correct as it currently is.
In this scenario, you have something like
S:\WORK\DBPROPSDEMO_ROOT
│   Directory.Build.props
│
└───folder
    └───subfolder
            Class1.cs
            Directory.Build.props
            subfolder.csproj

Without the .., you get a warning:
s:\work\DBPropsDemo_Root\folder\subfolder\Directory.Build.props(2,1): warning MSB4011: "s:\work\DBPropsDemo_Root\folder\subfolder\Directory.Build.props" cannot be imported again. It was already imported at "C:\Program Files (x86)\Microsoft Visual Studio\Preview\EntInt\MSBuild\15.0\Microsoft.Common.props (36,3)". This is most likely a build authoring error. This subsequent import will be ignored. [s:\work\DBPropsDemo_Root\folder\subfolder\subfolder.csproj]

That's because GetPathOfFileAbove is somewhat confusingly named. It starts its search in the argument directory and then looks upward. Since there is a Directory.Build.props file in the current directory (it's the current file!) it just finds that again.
If you want subfolder/Directory.Build.props to import root/Directory.Build.props, it must start its search (at least) one folder up.
Does that make sense @dazinator?

Ah I see. Yes the name of the method had me confused as to exactly what it was doing, but the explaination makes sense :-)

So its more of a: FindFileInDirectoryOrDirectoryAbove :-)

Indeed. I claim innocence on the naming since we were going for consistency with an existing name added before any of us was on the team 😇


"Association property name 'social_profiles' clashes with field of same name of table 'users'. You should explicitly specify the 'propertyName' option" when a new user logs in

Hi, ADmad.
I'm getting these errors when a new user logs in:
Warning (512): Association property name "social_profiles" clashes with field of same name of table "users". You should explicitly specify the "propertyName" option. [CORE/src/ORM/Association.php, line 721]

Warning (2): Cannot modify header information - headers already sent by (output started at /home/keoma/Projetos/simples/vendor/cakephp/cakephp/src/Error/Debugger.php:822) [CORE/src/Network/Session.php, line 564]

Warning (2): session_regenerate_id() [function.session-regenerate-id]: Cannot regenerate session id - headers already sent [CORE/src/Network/Session.php, line 568]

Warning (512): Unable to emit headers. Headers sent in file=/home/keoma/Projetos/simples/vendor/cakephp/cakephp/src/Error/Debugger.php line=822 [CORE/src/Http/ResponseEmitter.php, line 48]

Warning (2): Cannot modify header information - headers already sent by (output started at /home/keoma/Projetos/simples/vendor/cakephp/cakephp/src/Error/Debugger.php:822) [CORE/src/Http/ResponseEmitter.php, line 148]

Warning (2): Cannot modify header information - headers already sent by (output started at /home/keoma/Projetos/simples/vendor/cakephp/cakephp/src/Error/Debugger.php:822) [CORE/src/Http/ResponseEmitter.php, line 181]

Warning (2): Cannot modify header information - headers already sent by (output started at /home/keoma/Projetos/simples/vendor/cakephp/cakephp/src/Error/Debugger.php:822) [CORE/src/Http/ResponseEmitter.php, line 181]

Despite that, the user is saved on database. Logging in with previous saved users works fine. I did exactly like the readme says.
That is my UsersTable.php:
class UsersTable extends Table
{

    /**
     * Initialize method
     *
     * @param array $config The configuration for the Table.
     * @return void
     */
    public function initialize(array $config)
    {
        parent::initialize($config);

        $this->setTable('users');
        $this->setDisplayField('id');
        $this->setPrimaryKey('id');

        /*$this->hasMany('SocialProfiles', [
            'foreignKey' => 'user_id'
        ]);*/
        $this->hasMany('ADmad/HybridAuth.SocialProfiles');

        \Cake\Event\EventManager::instance()->on('HybridAuth.newUser', [$this, 'createUser']);
    }

    /**
     * Default validation rules.
     *
     * @param \Cake\Validation\Validator $validator Validator instance.
     * @return \Cake\Validation\Validator
     */
    public function validationDefault(Validator $validator)
    {
        $validator
            ->integer('id')
            ->allowEmpty('id', 'create');

        $validator
            ->email('email')
            ->requirePresence('email', 'create')
            ->notEmpty('email')
            ->add('email', 'unique', ['rule' => 'validateUnique', 'provider' => 'table']);

        $validator
            ->allowEmpty('social_profiles');

        return $validator;
    }

    /**
     * Returns a rules checker object that will be used for validating
     * application integrity.
     *
     * @param \Cake\ORM\RulesChecker $rules The rules object to be modified.
     * @return \Cake\ORM\RulesChecker
     */
    public function buildRules(RulesChecker $rules)
    {
        $rules->add($rules->isUnique(['email']));

        return $rules;
    }

    public function createUser(\Cake\Event\Event $event)
    {
        // Entity representing record in social_profiles table
        $profile = $event->data()['profile'];

        // Make sure here that all the required fields are actually present

        $user = $this->newEntity(['email' => $profile->email]);
        $user = $this->save($user);

        if (!$user) {
            throw new \RuntimeException('Unable to save new user');
        }

        return $user;
    }
}

Thank you.

I created the column "social_profiles" on my users table. I misinterpreted the readme. Please ignore it.