chore: rename start to dev

🔗 Linked issue
❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
Rename the start script to dev. The dev command is named dev in every others projects.
📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Nop since start is a classic angular script


Disk name not changed in the Mount Point input

mounts": [
{
"name": "AAAAAAAAAA",
"mountPoint": "/mnt/92fa6bf4",
"size":<PHONE_NUMBER>0,
"state": "ok",
"message": ""
TC665
Weblets: v1.4.3-qa3
https://play.qa.grid.tf/#/
Portal: https://portal.qa.grid.tf/

If I remember correctly the functionality was updated not to update the disk name after all, so in this case the test case can be removed from the test suit


Perform unreferenced file cleanup for any operation failure and mute flaky test

Description
As of now, we cleanup unreferenced files whenever last write is performed by merge and it caused disk to get full and shard to fail. Incase some other operation performs the last write and caused disk to get 100% full and a merge is ongoing, merge will just get aborted and no cleanup will be performed. Since when closing the shard it is the other operation causing disk full and not segment merge.
In order to fix this we need to cleanup unreferenced files when any operation failed due to disk full.
Related Issues
https://github.com/opensearch-project/OpenSearch/issues/12054
Check List

[x] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
[x] Commits are signed per the DCO using --signoff
[x] Commit changes are listed out in CHANGELOG.md file (See: Changelog)
[x] Public documentation issue/PR created

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@RS146BIJAY  : are you still working on this change ?


Frontend/feature/image upload

I've added functionality for updating the user profile picture in the UserForm
I've added a component that handles taking an image file input (ImageInput)
And added a component for showing a circular avatar image (AvatarInput)
I've added a service function to upload images to the backend
Waiting for #704 to be merged

Aapeli agrees that it would be better that the url is part of the response from the backend rather than the way I've done it currently

What do you mean by this?

Also the upload is not saved to the profile currently, it needs to be added to the UpdateProfileReq request in service/user.ts

Also the upload is not saved to the profile currently, it needs to be added to the UpdateProfileReq request in service/user.ts
I've added the avatarKey and avatarUrl to the request values but it still does not seem to work

@aapeliv
The updateUser request gives an error when it includes the avatarKey
And some of the uploaded images gives "Internal Server Error" when I request them after upload

The updateUser request gives an error when it includes the avatarKey

Fixed the typo

And some of the uploaded images gives "Internal Server Error" when I request them after upload

Fixed that one too, in #709.
Sorry, this has been incredibly buggy...

Currently upload works, but changing the profile without changing the image causes an unknown backend error. I suspect there is no check for avatarKey existing but having a blank value @aapeliv .

@MichaelGuldborg  It's disappeared from the profile edit page - did it get lost in the merge?

Also this is crashing with Error: There is already a source with this ID, which I suspect your Map fix will fix this?

To test locally you need to run media server docker container, but it's only in the production docker-compose file atm

How's this, will do some tests if it's ok

Also tests for negative cases? i.e. what happens if an invalid file is given, and when the file reader throws an error

@darrenvong as far as I can tell, there's no way to check for valid images. However the server does and I added error handling.

If the server will throw an error, couldn't we simulate this since those are already mocked? What happens if handleConfirm throws from the mutateAsync call?


CI: Travis / Circle CI setup

Setup Travis/Circle CI automation

build using existing gradle setup ( pretty easy )
run tests using gradle test on project slatekit.tests
only have to remove some tests since they rely on the database

Travis set up here: https://travis-ci.org/code-helix/slatekit


Offer finalization incorrectly requires to use the Buyer's wallet

Steps to reproduce:

As buyer using Wallet B, buy a product using crypto
As merchant using Wallet A, accept the offer on the shop's admin Orders page
As merchant using Wallet A, try to accept the offer on the shop's admin Orders page
=> The UI rejects it with error: "Incorrect account. Please set account to "

Done now


python311Packages.flask-security-too: 5.4.2 -> 5.4.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.flask-security-too is: Simple security for Flask apps (fork)
meta.homepage for python311Packages.flask-security-too is: https://github.com/Flask-Middleware/flask-security
meta.changelog for python311Packages.flask-security-too is: https://github.com/Flask-Middleware/flask-security/blob/5.4.3/CHANGES.rst
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.4.3 with grep in /nix/store/681f277cif2aga6iy4ikaay24252wbv8-python3.11-flask-security-too-5.4.3
found 5.4.3 in filename of file in /nix/store/681f277cif2aga6iy4ikaay24252wbv8-python3.11-flask-security-too-5.4.3

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
pgadmin4
pgadmin4-desktopmode
python311Packages.flask-security-too

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/681f277cif2aga6iy4ikaay24252wbv8-python3.11-flask-security-too-5.4.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/b64f0eaee61a056f156e70e3f2601bfb4a2b0d0a#python311Packages.flask-security-too

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/681f277cif2aga6iy4ikaay24252wbv8-python3.11-flask-security-too-5.4.3
ls -la /nix/store/681f277cif2aga6iy4ikaay24252wbv8-python3.11-flask-security-too-5.4.3/bin

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

6 packages built:

pgadmin4
pgadmin4-desktopmode
pgadmin4-desktopmode.dist
pgadmin4.dist
python311Packages.flask-security-too
python311Packages.flask-security-too.dist

Maintainer pings
cc @gador for testing.

@ofborg eval


Expected identifier, got 'LParen'solc

Hi I'm currently editing my SmartContract.sol from the scaffold-eth project.
By editing, I get the error "Expected identifier, got 'LParen'solc"
I think it is a noob question, but I'm grateful for every help I get.

I would just ignore that. Same thing happens to me, I think it is a VS Code thing with the linter.

I would just ignore that. Same thing happens to me, I think it is a VS Code thing with the linter.


Can't build release APK

I'm following the instructions from the official react native website, but can't get pass the $ ./gradlew assembleRelease step. I fixed some errors but now I get the following when running the command with --info :
> Task :react-native-braintree-xplat:verifyReleaseResources FAILED
Putting task artifact state for task ':react-native-braintree-xplat:verifyReleaseResources' into context took 0.0 secs.
Up-to-date check for task ':react-native-braintree-xplat:verifyReleaseResources' took 0.0 secs. It is not up-to-date because:
  Task has failed previously.
All input files are considered out-of-date for incremental task ':react-native-braintree-xplat:verifyReleaseResources'.
Unable do incremental execution: full task run
QueuedCruncher is using /Users/miguel/Library/Android/sdk/build-tools/27.0.3/aapt

Shutdown finished in 0ms

:react-native-braintree-xplat:verifyReleaseResources (Thread[Task worker for ':' Thread 3,5,main]) completed. Took 0.7 secs.
:react-native-svg:platformAttrExtractor (Thread[Task worker for ':',5,main]) completed. Took 10.698 secs.
:react-native-vector-icons:platformAttrExtractor (Thread[Daemon worker Thread 23,5,main]) completed. Took 10.461 secs.

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-braintree-xplat:verifyReleaseResources'.
> com.android.ide.common.process.ProcessException: Failed to execute aapt

* Try:
Run with --stacktrace option to get the stack trace. Run with --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 5m 19s
173 actionable tasks: 152 executed, 21 up-to-date

If I run the app directly on debug by executing react-native run-android works fine.

@miguelglz I'm having the similar problem. Did you manage to resolve this?
Only when trying to compile release build then I have this problem, nothing wrong when I am making debug build.

@miguelglz hi thanks for the reply. In case others may encounter the similar problem, I'll just leave my solution here.
What I did was to change the build.gradle of the library in the node_modules to use one version older than the latest braintree sdk. Probably the latest sdk is not compatible with the version of react native that I'm using (0.46.4).


Enhance generated code for structures with properties, support ICloneable in .NET standard

support ICloneable with NET_STANDARD, it is not required anymore to comment out
updates for generated code with complex types with variables.
The existing implementation did not track the timestamps of the properties and subscriptions did not work.
For sample implementation using this update see PR: https://github.com/OPCFoundation/UA-.NETStandard/pull/2008

moved to OPCF-Members


remove stale entries from rules.json

I'd like to remove a few things from our generated json descriptions of lint rules (https://github.com/dart-lang/linter/blob/gh-pages/lints/machine/rules.json).
Specifically, I'd like to remove:

"maturity" (now state)
"sinceLinter" (see: https://github.com/dart-lang/sdk/issues/59174)

@parlough, @devoncarew: do you have any idea who (if anyone) is using this file?
(I feel like I put this together for @csells a while back but can't recall how it's use has evolved...)

no tools I know of use either of those two field, @pq

Hi - this issue just got re-pinged due to the repo transfer (https://github.com/dart-lang/linter/issues/5127).


[1pt] Create basic structure for Rockets - Setup

Create a route and a view component. Use <NavLink /> for the page navigation links and style active class to indicate which section/page the user is currently on (underline active navigation link).
Create a directory for all Redux state slice files.

Link to the PR: https://github.com/SaveryIV/Space-X-Project/pull/29


QSCAN: add test

Imitate the Redis SCAN test  and try to add QSCAN test
Related https://github.com/antirez/disque/issues/59 :-)

Excellent! I'l merge monday.

Add IMPORTRATE option test and merge with the former changes into a new commit. :-)

That's pretty cool! Thanks. I think it's better if we match queue names instead of number of queues matching, but it's trivial to change.

p.s. removing the COUNT option test since there is no such guarantee of returning at least 5 elements. It's like Redis SCAN COUNT option.


[LIVY-610] optimization for windows environment build.

What changes were proposed in this pull request?
we can remove requireOS restriction for windows building, and add execute permission for bin/livy-server.
https://issues.apache.org/jira/browse/LIVY-610
How was this patch tested?
tested manually.

Codecov Report

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

@@             Coverage Diff             @@
##             master    #184      +/-   ##
===========================================
- Coverage     68.65%   68.4%   -0.25%
+ Complexity      905     902       -3
===========================================
  Files           100     100
  Lines          5666    5666
  Branches        850     850
===========================================
- Hits           3890    3876      -14
- Misses         1224    1232       +8
- Partials        552     558       +6

Impacted Files
Coverage Δ
Complexity Δ

...cala/org/apache/livy/scalaapi/ScalaJobHandle.scala
52.94% <0%> (-2.95%)
7% <0%> (ø)

.../scala/org/apache/livy/sessions/SessionState.scala
58.33% <0%> (-2.78%)
2% <0%> (ø)

...ain/java/org/apache/livy/rsc/driver/RSCDriver.java
76.69% <0%> (-2.55%)
39% <0%> (-3%)

...ain/scala/org/apache/livy/utils/SparkYarnApp.scala
71.12% <0%> (-2.12%)
33% <0%> (ø)

...c/src/main/java/org/apache/livy/rsc/RSCClient.java
73.91% <0%> (-1.25%)
20% <0%> (ø)

...main/scala/org/apache/livy/server/LivyServer.scala
35.46% <0%> (-0.5%)
11% <0%> (ø)

Continue to review full report at Codecov.

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

Codecov Report

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

@@             Coverage Diff             @@
##             master    #184      +/-   ##
===========================================
- Coverage     68.65%   68.4%   -0.25%
+ Complexity      905     902       -3
===========================================
  Files           100     100
  Lines          5666    5666
  Branches        850     850
===========================================
- Hits           3890    3876      -14
- Misses         1224    1232       +8
- Partials        552     558       +6

Impacted Files
Coverage Δ
Complexity Δ

...cala/org/apache/livy/scalaapi/ScalaJobHandle.scala
52.94% <0%> (-2.95%)
7% <0%> (ø)

.../scala/org/apache/livy/sessions/SessionState.scala
58.33% <0%> (-2.78%)
2% <0%> (ø)

...ain/java/org/apache/livy/rsc/driver/RSCDriver.java
76.69% <0%> (-2.55%)
39% <0%> (-3%)

...ain/scala/org/apache/livy/utils/SparkYarnApp.scala
71.12% <0%> (-2.12%)
33% <0%> (ø)

...c/src/main/java/org/apache/livy/rsc/RSCClient.java
73.91% <0%> (-1.25%)
20% <0%> (ø)

...main/scala/org/apache/livy/server/LivyServer.scala
35.46% <0%> (-0.5%)
11% <0%> (ø)

Continue to review full report at Codecov.

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

Is above the only fix for window compiling?

This patch is available for windows compiling and package, like "mvn clean -DskipTests -Pthriftserver package".  But unit tests and verify could not pass because of spark-submit command.

Another question, will the modification here change the behavior of *nix build?

This patch applies to unix build without any loss, and built package works fine by test .

I'm OK with the current fix. But this is still a half-way fix for Windows build support. @dockerzhang would you please create follow-up jiras to track the left issues.

Merging to master branch.

LIVY-611 is created to track the left issues.


Add monad syntax

I'm still feeling a little guilty about tramping over begin in this context, but it doesn't serve much other purpose given the context system so not too worried.
👍


Unable to delete relic snaphsots  using Get-RubrikUnmanagedObject for specific snappables.

Current Behavior:
PS C:\> Get-RubrikUnmanagedObject -Type "MssqlDatabase" | Where-Object -FilterScript { $_.unmanagedStatus -eq 'Relic' } | Remove-RubrikUnmanagedObject -Verbose
VERBOSE: Validate the Rubrik token exists
VERBOSE: Found a Rubrik token for authentication
VERBOSE: Gather API Data for Remove-RubrikUnmanagedObject
VERBOSE: Selected 1.0 API Data for Remove-RubrikUnmanagedObject
VERBOSE: Load API data for
VERBOSE: Description: Bulk delete all unmanaged snapshots for the objects specified by objectId/objectType pairings.
VERBOSE: Build the URI
VERBOSE: URI = https://<IP_ADDRESS>/api/internal/unmanaged_object/snapshot/bulk_delete
VERBOSE: Build the query parameters for
VERBOSE: Query = Found limit flag
VERBOSE: URI = https://<IP_ADDRESS>/api/internal/unmanaged_object/snapshot/bulk_delete?limit=9999
VERBOSE: List of set parameters: [Verbose, True] [Type, MssqlDatabase] [id,
MssqlDatabase:::0a9be6da-847b-4578-b3a6-1360a78ffa9d]
VERBOSE: Build the body parameters
VERBOSE: Adding objectDefinitions...
VERBOSE: Body = {
    "objectDefinitions":  [
                              {
                                  "objectId":  "MssqlDatabase:::0a9be6da-847b-4578-b3a6-1360a78ffa9d",
                                  "objectType":  "MssqlDatabase"
                              }
                          ]
}
VERBOSE: Submitting the request
VERBOSE: POST https://<IP_ADDRESS>/api/internal/unmanaged_object/snapshot/bulk_delete?limit=9999 with -1-byte payload
VERBOSE: received 0-byte response of content type
VERBOSE: Received HTTP Status 204
VERBOSE: Formatting return value
VERBOSE: Filter the results
VERBOSE: Build the URI
VERBOSE: URI = https://<IP_ADDRESS>/api/internal/unmanaged_object/snapshot/bulk_delete
VERBOSE: Build the query parameters for
VERBOSE: Query = Found limit flag
VERBOSE: URI = https://<IP_ADDRESS>/api/internal/unmanaged_object/snapshot/bulk_delete?limit=9999
VERBOSE: List of set parameters: [Verbose, True] [Type, MssqlDatabase] [id,
MssqlDatabase:::4a07300e-745c-4d72-ab35-0703fc71681f]
VERBOSE: Build the body parameters
VERBOSE: Adding objectDefinitions...
VERBOSE: Body = {
    "objectDefinitions":  [
                              {
                                  "objectId":  "MssqlDatabase:::4a07300e-745c-4d72-ab35-0703fc71681f",
                                  "objectType":  "MssqlDatabase"
                              }
                          ]
}
VERBOSE: Submitting the request
VERBOSE: POST https://<IP_ADDRESS>/api/internal/unmanaged_object/snapshot/bulk_delete?limit=9999 with -1-byte payload
VERBOSE: received 0-byte response of content type
VERBOSE: Received HTTP Status 204
VERBOSE: Formatting return value
VERBOSE: Filter the results
VERBOSE: Build the URI
VERBOSE: URI = https://<IP_ADDRESS>/api/internal/unmanaged_object/snapshot/bulk_delete
VERBOSE: Build the query parameters for
VERBOSE: Query = Found limit flag
VERBOSE: URI = https://<IP_ADDRESS>/api/internal/unmanaged_object/snapshot/bulk_delete?limit=9999
VERBOSE: List of set parameters: [Verbose, True] [Type, MssqlDatabase] [id,
MssqlDatabase:::d05adace-fc13-49e9-b9a0-de2b6f4bae5b]
VERBOSE: Build the body parameters
VERBOSE: Adding objectDefinitions...
VERBOSE: Body = {
    "objectDefinitions":  [
                              {
                                  "objectId":  "MssqlDatabase:::d05adace-fc13-49e9-b9a0-de2b6f4bae5b",
                                  "objectType":  "MssqlDatabase"
                              }
                          ]
}
VERBOSE: Submitting the request
VERBOSE: POST https://<IP_ADDRESS>/api/internal/unmanaged_object/snapshot/bulk_delete?limit=9999 with -1-byte payload
VERBOSE: received 0-byte response of content type
VERBOSE: Received HTTP Status 204
VERBOSE: Formatting return value
VERBOSE: Filter the results

Expected Behavior:
Need to delete the Relic snapshot for a specific swappable
Steps to Reproduce:
Get-RubrikUnmanagedObject -Type "MssqlDatabase" | Where-Object -FilterScript { $_.unmanagedStatus -eq 'Relic' } | Remove-RubrikUnmanagedObject
Context:
Failure Logs
VERBOSE: Submitting the request
VERBOSE: POST https://<IP_ADDRESS>/api/internal/unmanaged_object/snapshot/bulk_delete?limit=9999 with -1-byte payload
VERBOSE: received 0-byte response of content type
VERBOSE: Received HTTP Status 204
VERBOSE: Formatting return value
VERBOSE: Filter the results
VERBOSE: Build the URI
VERBOSE: URI = https://<IP_ADDRESS>/api/internal/unmanaged_object/snapshot/bulk_delete
VERBOSE: Build the query parameters for
VERBOSE: Query = Found limit flag
VERBOSE: URI = https://<IP_ADDRESS>/api/internal/unmanaged_object/snapshot/bulk_delete?limit=9999
VERBOSE: List of set parameters: [Verbose, True] [Type, MssqlDatabase] [id,
MssqlDatabase:::4a07300e-745c-4d72-ab35-0703fc71681f]
VERBOSE: Build the body parameters
VERBOSE: Adding objectDefinitions...
VERBOSE: Body = {
    "objectDefinitions":  [
                              {
                                  "objectId":  "MssqlDatabase:::4a07300e-745c-4d72-ab35-0703fc71681f",
                                  "objectType":  "MssqlDatabase"
                              }
                          ]
}
VERBOSE: Submitting the request
VERBOSE: POST https://<IP_ADDRESS>/api/internal/unmanaged_object/snapshot/bulk_delete?limit=9999 with -1-byte payload
VERBOSE: received 0-byte response of content type
VERBOSE: Received HTTP Status 204
VERBOSE: Formatting return value
VERBOSE: Filter the results
VERBOSE: Build the URI
VERBOSE: URI = https://<IP_ADDRESS>/api/internal/unmanaged_object/snapshot/bulk_delete
VERBOSE: Build the query parameters for
VERBOSE: Query = Found limit flag
VERBOSE: URI = https://<IP_ADDRESS>/api/internal/unmanaged_object/snapshot/bulk_delete?limit=9999
VERBOSE: List of set parameters: [Verbose, True] [Type, MssqlDatabase] [id,
MssqlDatabase:::d05adace-fc13-49e9-b9a0-de2b6f4bae5b]
VERBOSE: Build the body parameters
VERBOSE: Adding objectDefinitions...
VERBOSE: Body = {
    "objectDefinitions":  [
                              {
                                  "objectId":  "MssqlDatabase:::d05adace-fc13-49e9-b9a0-de2b6f4bae5b",
                                  "objectType":  "MssqlDatabase"
                              }
                          ]
}
VERBOSE: Submitting the request
VERBOSE: POST https://<IP_ADDRESS>/api/internal/unmanaged_object/snapshot/bulk_delete?limit=9999 with -1-byte payload
VERBOSE: received 0-byte response of content type
VERBOSE: Received HTTP Status 204
VERBOSE: Formatting return value
VERBOSE: Filter the results

Thanks for reporting this bug, we will take a look at how we can resolve this

Hello @ravs968,
I've taken a look at trying to replicate your results, but I am unable to replicate your results. Do you get similar results when attempting to remove these unmanagedobjects through the GUI?

Closing issue as no further information was provided. If you would like to reopen this please comment here.


kaleido --> python-kaleido in config.yaml

https://pypi.org/project/kaleido/

https://github.com/conda-incubator/grayskull/issues/168#issuecomment-1141484616

Thanks for your contribution again! :)


Enable Cleaner and Pruner cronJobs for cache

When cache is enabled, we might need to build two additional cronJobs to enable cache-cleaner and cache-pruner.
This patch extends the ability of the current cronJob definition to run different commands and schedules, according to the CronJobType passed as argument.

tempest job looks good: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openstack-k8s-operators_glance-operator/330/pull-ci-openstack-k8s-operators-glance-operator-main-glance-operator-build-deploy-tempest/1709474557351432192/artifacts/glance-operator-build-deploy-tempest/openstack-k8s-operators-gather/artifacts/must-gather/quay-io-openstack-k8s-operators-openstack-must-gather-sha256-923bc944999f722935616f4e3fa620f5a1b037c8cef824258f2bad11f0a178e4/namespaces/openstack/cronjobs/glance-cron.yaml

/test glance-operator-build-deploy-kuttl


AUTHORIZATION

How do i redirect user to put in their pin ??
sorry your little documentation is not really clear abeg

Hi @GoodnessEzeokafor
To achieve this, kindly check below;
if (response.meta.authorization.mode === 'pin')
if this is true, you can render a page to collect Users PIN and add the following to the initial payload.
authorization = {
                "mode": "pin",
                "fields": [
                    "pin"
                ],
                "pin": 3310 // Users PIN
            }

Then call charge again with the added params to the payload
const reCallCharge = await flw.Charge.card(payload2)
Then you can proceed to validate  by calling validate.
const callValidate = await flw.Charge.validate({
                "otp": "12345" //Users OTP,
                "flw_ref": reCallCharge.data.flw_ref
            })

Kindy check here to see how card transaction works.
Once again, thank you for the documentation feedback.
The team will review it

Thanks
would also love to know when is you guys flutterwave expert programme


Issuer - Support to configure database

Implemented as part of https://github.com/trustbloc/edge-sandbox/pull/417.


Add nunomaduro/termwind console sink

For beautiful formatting on the console, it would be nice to choose another sink for the console logger. This would involve:

installing nunomaduro/termwind
creating a new class in the console module
implement the Sink contract
log using termwind in the log method

Working on this issue showed that it is not really preferable to integrate a completely different logging solution. The current codebase is too tightly integrated with the existing solution. This can be pursued once the dependency are more loosely coupled.
The result of working on this ticket will still be merged via #25, but without nunomaduro/termwind.


Azure - GitHub Action for deploying OCP Cluster

Description
Automated deployment of OCP Cluster in Azure upon any code changes in the ARM Template or deployment script.
Potential Solutions
Implement GitHub Action workflow file for automated deployment of OCP Cluster in Azure.
Additional Context
Test the deployment of OCP Cluster with the workflow file.

@ivandov PR https://github.com/IBM/zmodstack-deploy/pull/8 has been raised for this issue.

PR has been merged to dev branch.
Executed GitHub Action successfully - https://github.com/IBM/zmodstack-deploy/actions/runs/5516199515.
Closing the issue.


3.2 Big Ideas, Period 1

Team Member : Sonika Dhenuva Konda, Katherine Chen, Sanya Kapoor, Aditi Bandaru
Period 1, Mr Brown
Description: This is the Team Teach for 3.2 Big Ideas - Data Abstraction

Accepted, you can pull and test.  But, you should consider generic nature of this link and that we have 5 periods, many topics Big Idea 1 through 5,  and many sections in Big Idea 3.
http://<IP_ADDRESS>:4100/portfolio_2025/csp/big-idea/home

Also, file names of IPYNB need some correction to work across all the students participating.
It would be nice to get you integrated with menu for entire class.


[feat]: choose your own base color

Feature description
When initialising shadcn-ui on a project already setup with my own styles in the tailwind config, I want that the base colour that shadcn-ui uses to be one of my existing ones, not one from the set of colours given by the repo itself.
Affected component/components
No response
Additional Context
Whenever I add a component, I have to go through and update all of the styles that exist (that's the point, but a little less work OOTB would be nice)
Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues and PRs

It would also be nice to ask for more than just the base color, like primary, secondary and maybe tertiary colors.

Hmm, I suppose this is already possible thanks to being able to create a custom schema; albeit this would still be a nice addition to the default one.

i agree


A  question about  search.py

Hi ,  man  I  want to  excute  seach.py  in  cifar 10  ,   I  notice  that   fa_reduced_cifar10 is   the  result  you  got  ,  but    in   wresnet40x2_cifar10_b512.yaml,  there  alreayd  exist  a  key  aug: fa_reduced_cifar10  ,      should I  delete  it   and   type  with  nothing ?

@heartInsert You are right. You need to add "--aug default" parameter when you run search.py file.

Ok, I  get  it .


The specified procedure could not be found.

After running the command: accelerate launch train_tuneavideo.py --config="configs/road-scenarios.yaml" on my own data
It shows this error:
Traceback (most recent call last):
File "c:\Users\INP_Rohit.conda\envs\phn\lib\runpy.py", line 196, in run_module_as_main
return run_code(code, main_globals, None,
File "c:\Users\INP_Rohit.conda\envs\phn\lib\runpy.py", line 86, in run_code
exec(code, run_globals)
File "C:\Users\INP_Rohit.conda\envs\phn\Scripts\accelerate.exe_main.py", line 4, in
File "c:\Users\INP_Rohit.conda\envs\phn\lib\site-packages\accelerate_init.py", line 3, in
from .accelerator import Accelerator
File "c:\Users\INP_Rohit.conda\envs\phn\lib\site-packages\accelerate\accelerator.py", line 32, in
import torch
File "c:\Users\INP_Rohit.conda\envs\phn\lib\site-packages\torch_init.py", line 129, in
raise err
OSError: [WinError 127] The specified procedure could not be found. Error loading "c:\Users\INP_Rohit.conda\envs\phn\lib\site-packages\torch\lib\c10_cuda.dll" or one of its dependencies.

the above error was clearecd after reinsatlling cuda again using torch
But a new error arrived when i run the command again:
The following values were not passed to accelerate launch and had defaults used instead:
--num_processes was set to a value of 1
--num_machines was set to a value of 1
--mixed_precision was set to a value of 'no'
--dynamo_backend was set to a value of 'no'
To avoid this warning pass in values for each of the problematic parameters or run accelerate config.
03/29/2024 11:28:57 - INFO - main - Distributed environment: NO
Num processes: 1
Process index: 0
Local process index: 0
Device: cuda
Mixed precision type: fp16
Traceback (most recent call last):
File "c:\Users\INP_Rohit.conda\envs\phn\lib\site-packages\diffusers\configuration_utils.py", line 326, in load_config
config_file = hf_hub_download(
File "c:\Users\INP_Rohit.conda\envs\phn\lib\site-packages\huggingface_hub\utils_validators.py", line 110, in _inner_fn
validate_repo_id(arg_value)
File "c:\Users\INP_Rohit.conda\envs\phn\lib\site-packages\huggingface_hub\utils_validators.py", line 158, in validate_repo_id
raise HFValidationError(
huggingface_hub.utils._validators.HFValidationError: Repo id must be in the form 'repo_name' or 'namespace/repo_name': './checkpoints/stable-diffusion-v1-4'. Use repo_type argument if needed.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\INP_Rohit\Documents\ImageGeneration\Tune-A-Video\train_tuneavideo.py", line 367, in
main(**OmegaConf.load(args.config))
File "C:\Users\INP_Rohit\Documents\ImageGeneration\Tune-A-Video\train_tuneavideo.py", line 105, in main
noise_scheduler = DDPMScheduler.from_pretrained(pretrained_model_path, subfolder="scheduler")
File "c:\Users\INP_Rohit.conda\envs\phn\lib\site-packages\diffusers\schedulers\scheduling_utils.py", line 118, in from_pretrained
config, kwargs = cls.load_config(
File "c:\Users\INP_Rohit.conda\envs\phn\lib\site-packages\diffusers\configuration_utils.py", line 363, in load_config
raise EnvironmentError(
OSError: We couldn't connect to 'https://huggingface.co' to load this model, couldn't find it in the cached files and it looks like ./checkpoints/stable-diffusion-v1-4 is not the path to a directory containing a scheduler_config.json file.
Checkout your internet connection or see how to run the library in offline mode at 'https://huggingface.co/docs/diffusers/installation#offline-mode'.
Traceback (most recent call last):
File "c:\Users\INP_Rohit.conda\envs\phn\lib\runpy.py", line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File "c:\Users\INP_Rohit.conda\envs\phn\lib\runpy.py", line 86, in run_code
exec(code, run_globals)
File "C:\Users\INP_Rohit.conda\envs\phn\Scripts\accelerate.exe_main.py", line 7, in
File "c:\Users\INP_Rohit.conda\envs\phn\lib\site-packages\accelerate\commands\accelerate_cli.py", line 47, in main
args.func(args)
File "c:\Users\INP_Rohit.conda\envs\phn\lib\site-packages\accelerate\commands\launch.py", line 1023, in launch_command
simple_launcher(args)
File "c:\Users\INP_Rohit.conda\envs\phn\lib\site-packages\accelerate\commands\launch.py", line 643, in simple_launcher
raise subprocess.CalledProcessError(returncode=process.returncode, cmd=cmd)
subprocess.CalledProcessError: Command '['c:\Users\INP_Rohit\.conda\envs\phn\python.exe', 'train_tuneavideo.py', '--config=configs/road-scenarios.yaml']' returned non-zero exit status 1.

@23Rj20 same for me, did you solve it?


[BOT PR] to update dependencies of istio

This PR will be merged automatically once checks are successful.
none

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

Needs approval from an approver in each of these files:

OWNERS

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

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
e1ae409d6c39728f3b38362493c2a6415831a32c
link
/test istio-integ-k8s-tests

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

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
e1ae409d6c39728f3b38362493c2a6415831a32c
link
/test istio-integ-k8s-tests

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

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


Bad Credentials Issue is back

Exception in thread "main" xyz.gianlu.librespot.core.Session$SpotifyAuthenticationException: BadCredentials
Anyone else having this issue?

Same issue yeah, wonder how i keep having issues but the t4ils api stays on

I actually think his version on  t4ils api isn't the old insights. I think his is a modified version...  because his only shows 5 cities. It looks like he was porting it over from the last time the other endpoints stopped working.
I need to find an alternative to get the 50 cities. 5 is so much worse :(

Cities? What cities are we talking about? I thought this was used for playcounts i have no idea what cities mean

The artistinsights endpoint that we used in the past had the artists top 50 cities.   I cant access that insights endpoint anymore at all due to Bad Auth

Ohh like that, i was only focused on the playcount endpoints my bad

Same issue here. Launched a new debian VM at Google Cloud, installed Java, Git and Maven and then cloned and build the java jar.
idmon@spotify-api:~/sp-playcount-librespot$ java -jar ./core/target/librespot-core-jar-with-dependencies.jar '###########' '############' 2023-11-14 19:38:22,195 INFO  ApResolver:66 - Loaded aps into pool: {accesspoint=[ap-guc3.spotify.com:4070, ap-guc3.spotify.com:443, ap-guc3.spotify.com:80, ap-gew4.spotify.com:4070, ap-gue1.spotify.com:443, ap-gae2.spotify.com:80], dealer=[guc3-dealer.spotify.com:443, gew4-dealer.spotify.com:443, gue1-dealer.spotify.com:443, gae2-dealer.spotify.com:443], spclient=[guc3-spclient.spotify.com:443, gew4-spclient.spotify.com:443, gue1-spclient.spotify.com:443, gae2-spclient.spotify.com:443]} 2023-11-14 19:38:22,284 INFO  Session:94 - Created new session! {deviceId: c70f928698cc099e39bddfd469f7de38e3b805db, ap: ap-guc3.spotify.com:4070}  2023-11-14 19:38:22,805 INFO  Session:223 - Connected successfully! Exception in thread "main" xyz.gianlu.librespot.core.Session$SpotifyAuthenticationException: BadCredentials         at xyz.gianlu.librespot.core.Session.authenticatePartial(Session.java:311)         at xyz.gianlu.librespot.core.Session.authenticate(Session.java:231)         at xyz.gianlu.librespot.core.Session$Builder.create(Session.java:583)         at xyz.gianlu.librespot.Main.main(Main.java:18)

Same issue here. Launched a fresh new debian VM at Google Cloud. Installed Java, Git and Maven... then I cloned the repo and build the java jar.
idmon@spotify-api:~/sp-playcount-librespot$ java -jar ./core/target/librespot-core-jar-with-dependencies.jar '###########' '############'

2023-11-14 19:38:22,195 INFO  ApResolver:66 - Loaded aps into pool: {accesspoint=[ap-guc3.spotify.com:4070, ap-guc3.spotify.com:443, ap-guc3.spotify.com:80, ap-gew4.spotify.com:4070, ap-gue1.spotify.com:443, ap-gae2.spotify.com:80], dealer=[guc3-dealer.spotify.com:443, gew4-dealer.spotify.com:443, gue1-dealer.spotify.com:443, gae2-dealer.spotify.com:443], spclient=[guc3-spclient.spotify.com:443, gew4-spclient.spotify.com:443, gue1-spclient.spotify.com:443, gae2-spclient.spotify.com:443]}

2023-11-14 19:38:22,284 INFO  Session:94 - Created new session! {deviceId: c70f928698cc099e39bddfd469f7de38e3b805db, ap: ap-guc3.spotify.com:4070}

2023-11-14 19:38:22,805 INFO  Session:223 - Connected successfully!
Exception in thread "main" xyz.gianlu.librespot.core.Session$SpotifyAuthenticationException: BadCredentials
        at xyz.gianlu.librespot.core.Session.authenticatePartial(Session.java:311)
        at xyz.gianlu.librespot.core.Session.authenticate(Session.java:231)
        at xyz.gianlu.librespot.core.Session$Builder.create(Session.java:583)
        at xyz.gianlu.librespot.Main.main(Main.java:18)`


Does "sriov-network-device-plugin" only discover the network device under "Network devices using DPDK-compatible driver" or even the devices under "Other Network devices"?

What issue would you like to bring attention to?
Does "sriov-network-device-plugin" only discover the network device under "Network devices using DPDK-compatible driver" or even the devices under "Other Network devices"?
I have a K8S cluster worker node with following network devices
> sudo dpdk-devbind --status
Network devices using DPDK-compatible driver
============================================
0000:00:07.0 'Ethernet Virtual Function 700 Series 154c' drv=igb_uio unused=iavf
0000:00:08.0 'Ethernet Virtual Function 700 Series 154c' drv=igb_uio unused=iavf
0000:00:09.0 'Ethernet Virtual Function 700 Series 154c' drv=igb_uio unused=iavf
0000:00:0a.0 'Ethernet Virtual Function 700 Series 154c' drv=igb_uio unused=iavf
0000:00:0b.0 'Ethernet Virtual Function 700 Series 154c' drv=igb_uio unused=iavf

Network devices using kernel driver
===================================
0000:00:03.0 'Virtio network device 1000' if=eth0 drv=virtio-pci unused=virtio_pci,igb_uio Active
0000:00:04.0 'Virtio network device 1000' if=eth1 drv=virtio-pci unused=virtio_pci,igb_uio Active
0000:00:05.0 'Virtio network device 1000' if=eth2 drv=virtio-pci unused=virtio_pci,igb_uio

Other Network devices
=====================
0000:00:0c.0 'Ethernet Virtual Function 700 Series 154c' unused=iavf,igb_uio

and config file defined like:
        {
            "resourceName": "intel_sriov_dpdk",
            "resourcePrefix": "intel.com",
            "selectors": {
                "vendors": ["8086"],
                "devices": ["154c", "10ed"],
                "drivers": ["vfio-pci", "igb_uio"]
            }
        }

So I would like to know whether all network devices from "0000:00:07.0" to "0000:00:0c.0" should be included into the "intel_sriov_dpdk" resource list? or the network device "0000:00:0c.0 " which in "Other Network devices" should be excluded?

@zshi-redhat  in case you have a quick answer for this simple question. Thanks.

@zshi-redhat in case you have a quick answer for this simple question. Thanks.

@harper1011 Devices from "0000:00:07.0" to "0000:00:0c.0"  are using igb_uio driver, but in your configmap selector, there is only kernel drivers i40evf, ixgbevf, iavf, you might want to add igb_uio as one of the drivers.

@zshi-redhat  sorry I paste wrong configmap. The drivers should be "vfio-pci" and "igb_uio"
I will edit my original post

could you also paste the device plugin log?

Here is the log
Running on machine: worker-pool10-5y0q4hsk-pccc-251-2
Binary: Built with gc go1.12.15 for linux/amd64
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
I1123 21:27:10.198865   15147 manager.go:70] Using Kubelet Plugin Registry Mode
I1123 21:27:10.199065   15147 main.go:44] resource manager reading configs
I1123 21:27:10.199289   15147 manager.go:98] ResourceList: [{ResourceName:intel_sriov_hostdevice IsRdma:false Selectors:{Vendors:[8086] Devices:[154c 10ed] Drivers:[i40evf ixgbevf iavf] PciAddresses:[] PfNames:[] LinkTypes:[]}} {ResourceName:intel_sriov_dpdk_device IsRdma:false Selectors:{Vendors:[8086] Devices:[154c 10ed] Drivers:[vfio-pci igb_uio] PciAddresses:[] PfNames:[] LinkTypes:[]}}]
I1123 21:27:10.199364   15147 main.go:60] Discovering host network devices
I1123 21:27:10.199374   15147 manager.go:179] discovering host network devices
I1123 21:27:10.241305   15147 manager.go:209] discoverDevices(): device found: 0000:00:03.0	02          	Red Hat, Inc        	Virtio network device
W1123 21:27:10.241402   15147 pciNetDevice.go:61] unable to get PF name "open /sys/bus/pci/devices/0000:00:03.0/net: no such file or directory"
I1123 21:27:10.241620   15147 manager.go:209] discoverDevices(): device found: 0000:00:04.0	02          	Red Hat, Inc        	Virtio network device
W1123 21:27:10.241686   15147 pciNetDevice.go:61] unable to get PF name "open /sys/bus/pci/devices/0000:00:04.0/net: no such file or directory"
I1123 21:27:10.241725   15147 manager.go:209] discoverDevices(): device found: 0000:00:05.0	02          	Red Hat, Inc        	Virtio network device
W1123 21:27:10.241778   15147 pciNetDevice.go:61] unable to get PF name "open /sys/bus/pci/devices/0000:00:05.0/net: no such file or directory"
I1123 21:27:10.241810   15147 manager.go:209] discoverDevices(): device found: 0000:00:07.0	02          	Intel Corporation   	XL710/X710 Virtual Function
W1123 21:27:10.241865   15147 pciNetDevice.go:61] unable to get PF name "open /sys/bus/pci/devices/0000:00:07.0/net: no such file or directory"
I1123 21:27:10.241924   15147 manager.go:209] discoverDevices(): device found: 0000:00:08.0	02          	Intel Corporation   	XL710/X710 Virtual Function
W1123 21:27:10.241985   15147 pciNetDevice.go:61] unable to get PF name "open /sys/bus/pci/devices/0000:00:08.0/net: no such file or directory"
I1123 21:27:10.242042   15147 manager.go:209] discoverDevices(): device found: 0000:00:09.0	02          	Intel Corporation   	XL710/X710 Virtual Function
W1123 21:27:10.242102   15147 pciNetDevice.go:61] unable to get PF name "open /sys/bus/pci/devices/0000:00:09.0/net: no such file or directory"
I1123 21:27:10.242159   15147 manager.go:209] discoverDevices(): device found: 0000:00:0a.0	02          	Intel Corporation   	XL710/X710 Virtual Function
W1123 21:27:10.242230   15147 pciNetDevice.go:61] unable to get PF name "open /sys/bus/pci/devices/0000:00:0a.0/net: no such file or directory"
I1123 21:27:10.242327   15147 manager.go:209] discoverDevices(): device found: 0000:00:0b.0	02          	Intel Corporation   	XL710/X710 Virtual Function
W1123 21:27:10.242385   15147 pciNetDevice.go:61] unable to get PF name "open /sys/bus/pci/devices/0000:00:0b.0/net: no such file or directory"
I1123 21:27:10.242439   15147 manager.go:209] discoverDevices(): device found: 0000:00:0c.0	02          	Intel Corporation   	XL710/X710 Virtual Function
W1123 21:27:10.242494   15147 pciNetDevice.go:61] unable to get PF name "open /sys/bus/pci/devices/0000:00:0c.0/net: no such file or directory"
I1123 21:27:10.242548   15147 main.go:66] Initializing resource servers
I1123 21:27:10.242558   15147 manager.go:108] number of config: 2
I1123 21:27:10.242563   15147 manager.go:111]
I1123 21:27:10.242570   15147 manager.go:112] Creating new ResourcePool: intel_sriov_hostdevice
I1123 21:27:10.242593   15147 manager.go:125] New resource server is created for intel_sriov_hostdevice ResourcePool
I1123 21:27:10.242599   15147 manager.go:111]
I1123 21:27:10.242604   15147 manager.go:112] Creating new ResourcePool: intel_sriov_dpdk_device
I1123 21:27:10.242615   15147 factory.go:153] device added: [pciAddr: 0000:00:07.0, vendor: 8086, device: 154c, driver: igb_uio]
I1123 21:27:10.242619   15147 factory.go:153] device added: [pciAddr: 0000:00:08.0, vendor: 8086, device: 154c, driver: igb_uio]
I1123 21:27:10.242623   15147 factory.go:153] device added: [pciAddr: 0000:00:09.0, vendor: 8086, device: 154c, driver: igb_uio]
I1123 21:27:10.242627   15147 factory.go:153] device added: [pciAddr: 0000:00:0a.0, vendor: 8086, device: 154c, driver: igb_uio]
I1123 21:27:10.242631   15147 factory.go:153] device added: [pciAddr: 0000:00:0b.0, vendor: 8086, device: 154c, driver: igb_uio]
I1123 21:27:10.242635   15147 factory.go:153] device added: [pciAddr: 0000:00:0c.0, vendor: 8086, device: 154c, driver: igb_uio]
I1123 21:27:10.242642   15147 manager.go:125] New resource server is created for intel_sriov_dpdk_device ResourcePool
I1123 21:27:10.242670   15147 main.go:72] Starting all servers...
I1123 21:27:10.242704   15147 server.go:190] starting intel_sriov_hostdevice device plugin endpoint at: intel_sriov_hostdevice.sock
I1123 21:27:10.243335   15147 server.go:216] intel_sriov_hostdevice device plugin endpoint started serving
I1123 21:27:10.243393   15147 server.go:190] starting intel_sriov_dpdk_device device plugin endpoint at: intel_sriov_dpdk_device.sock
I1123 21:27:10.243741   15147 server.go:216] intel_sriov_dpdk_device device plugin endpoint started serving
I1123 21:27:10.243764   15147 main.go:77] All servers started.
I1123 21:27:10.243770   15147 main.go:78] Listening for term signals
I1123 21:27:11.200509   15147 server.go:105] Plugin: intel_sriov_dpdk_device.sock gets registered successfully at Kubelet
I1123 21:27:11.200576   15147 server.go:130] ListAndWatch(intel_sriov_dpdk_device) invoked
I1123 21:27:11.200596   15147 server.go:130] ListAndWatch(intel_sriov_hostdevice) invoked
I1123 21:27:11.200627   15147 server.go:138] ListAndWatch(intel_sriov_hostdevice): send devices &ListAndWatchResponse{Devices:[]*Device{},}
I1123 21:27:11.200596   15147 server.go:105] Plugin: intel_sriov_hostdevice.sock gets registered successfully at Kubelet
I1123 21:27:11.200593   15147 server.go:138] ListAndWatch(intel_sriov_dpdk_device): send devices &ListAndWatchResponse{Devices:[]*Device{&Device{ID:0000:00:0c.0,Health:Healthy,Topology:nil,},&Device{ID:0000:00:07.0,Health:Healthy,Topology:nil,},&Device{ID:0000:00:08.0,Health:Healthy,Topology:nil,},&Device{ID:0000:00:09.0,Health:Healthy,Topology:nil,},&Device{ID:0000:00:0a.0,Health:Healthy,Topology:nil,},&Device{ID:0000:00:0b.0,Health:Healthy,Topology:nil,},},}
I1124 01:59:00.569891   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:07.0],},},}
I1124 01:59:00.570028   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:07.0]
I1124 01:59:00.570051   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:07.0]
I1124 01:59:00.570062   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:07.0]
I1124 01:59:00.570067   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:07.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio3,HostPath:/dev/uio3,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1124 01:59:01.203707   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:08.0],},},}
I1124 01:59:01.203764   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:08.0]
I1124 01:59:01.203774   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:08.0]
I1124 01:59:01.203781   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:08.0]
I1124 01:59:01.203786   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:08.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio4,HostPath:/dev/uio4,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1124 02:08:24.902941   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:0c.0],},},}
I1124 02:08:24.903074   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:0c.0]
I1124 02:08:24.903096   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:0c.0]
I1124 02:08:24.903102   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:0c.0]
I1124 02:08:24.903107   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:0c.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio2,HostPath:/dev/uio2,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1124 02:08:25.486552   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:0a.0],},},}
I1124 02:08:25.486617   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:0a.0]
I1124 02:08:25.486632   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:0a.0]
I1124 02:08:25.486640   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:0a.0]
I1124 02:08:25.486648   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:0a.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio0,HostPath:/dev/uio0,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1124 03:24:40.811160   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:0a.0],},},}
I1124 03:24:40.811308   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:0a.0]
I1124 03:24:40.811333   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:0a.0]
I1124 03:24:40.811345   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:0a.0]
I1124 03:24:40.811353   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:0a.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio0,HostPath:/dev/uio0,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1124 03:24:41.031957   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:08.0],},},}
I1124 03:24:41.032015   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:08.0]
I1124 03:24:41.032027   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:08.0]
I1124 03:24:41.032036   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:08.0]
I1124 03:24:41.032042   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:08.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio4,HostPath:/dev/uio4,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1124 07:01:54.290844   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:0c.0],},},}
I1124 07:01:54.290985   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:0c.0]
I1124 07:01:54.291010   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:0c.0]
I1124 07:01:54.291021   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:0c.0]
I1124 07:01:54.291030   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:0c.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio2,HostPath:/dev/uio2,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1124 07:01:54.910445   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:0b.0],},},}
I1124 07:01:54.910496   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:0b.0]
I1124 07:01:54.910507   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:0b.0]
I1124 07:01:54.910512   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:0b.0]
I1124 07:01:54.910517   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:0b.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio1,HostPath:/dev/uio1,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1124 07:48:21.142633   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:0a.0],},},}
I1124 07:48:21.142781   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:0a.0]
I1124 07:48:21.142806   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:0a.0]
I1124 07:48:21.142817   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:0a.0]
I1124 07:48:21.142825   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:0a.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio0,HostPath:/dev/uio0,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1124 07:48:21.642269   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:08.0],},},}
I1124 07:48:21.642329   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:08.0]
I1124 07:48:21.642340   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:08.0]
I1124 07:48:21.642348   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:08.0]
I1124 07:48:21.642352   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:08.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio4,HostPath:/dev/uio4,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1124 08:09:20.309074   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:0b.0],},},}
I1124 08:09:20.309146   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:0b.0]
I1124 08:09:20.309158   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:0b.0]
I1124 08:09:20.309164   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:0b.0]
I1124 08:09:20.309170   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:0b.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio1,HostPath:/dev/uio1,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1124 08:09:21.286049   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:0a.0],},},}
I1124 08:09:21.286097   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:0a.0]
I1124 08:09:21.286108   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:0a.0]
I1124 08:09:21.286113   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:0a.0]
I1124 08:09:21.286118   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:0a.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio0,HostPath:/dev/uio0,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1124 10:19:24.607323   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:0c.0],},},}
I1124 10:19:24.607517   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:0c.0]
I1124 10:19:24.607546   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:0c.0]
I1124 10:19:24.607559   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:0c.0]
I1124 10:19:24.607567   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:0c.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio2,HostPath:/dev/uio2,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1124 16:41:16.099931   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:07.0],},},}
I1124 16:41:16.100095   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:07.0]
I1124 16:41:16.100116   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:07.0]
I1124 16:41:16.100124   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:07.0]
I1124 16:41:16.100132   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:07.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio3,HostPath:/dev/uio3,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1124 16:41:17.499456   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:0c.0],},},}
I1124 16:41:17.499499   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:0c.0]
I1124 16:41:17.499507   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:0c.0]
I1124 16:41:17.499512   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:0c.0]
I1124 16:41:17.499517   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:0c.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio2,HostPath:/dev/uio2,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1125 01:58:50.465011   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:0b.0],},},}
I1125 01:58:50.465153   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:0b.0]
I1125 01:58:50.465173   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:0b.0]
I1125 01:58:50.465182   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:0b.0]
I1125 01:58:50.465187   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:0b.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio1,HostPath:/dev/uio1,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1125 01:58:51.544052   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:07.0],},},}
I1125 01:58:51.544104   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:07.0]
I1125 01:58:51.544114   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:07.0]
I1125 01:58:51.544119   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:07.0]
I1125 01:58:51.544124   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:07.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio3,HostPath:/dev/uio3,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1125 07:57:33.864955   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:09.0],},},}
I1125 07:57:33.865164   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:09.0]
I1125 07:57:33.865193   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:09.0]
I1125 07:57:33.865205   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:09.0]
I1125 07:57:33.865213   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:09.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio5,HostPath:/dev/uio5,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1125 07:57:34.586297   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:0a.0],},},}
I1125 07:57:34.586363   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:0a.0]
I1125 07:57:34.586375   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:0a.0]
I1125 07:57:34.586383   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:0a.0]
I1125 07:57:34.586388   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:0a.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio0,HostPath:/dev/uio0,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1125 10:43:34.340944   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:0c.0],},},}
I1125 10:43:34.341120   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:0c.0]
I1125 10:43:34.341144   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:0c.0]
I1125 10:43:34.341165   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:0c.0]
I1125 10:43:34.341171   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:0c.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio2,HostPath:/dev/uio2,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1125 10:43:34.734254   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:0b.0],},},}
I1125 10:43:34.734308   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:0b.0]
I1125 10:43:34.734319   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:0b.0]
I1125 10:43:34.734325   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:0b.0]
I1125 10:43:34.734330   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:0b.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio1,HostPath:/dev/uio1,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1125 16:01:00.422872   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:07.0],},},}
I1125 16:01:00.423018   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:07.0]
I1125 16:01:00.423039   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:07.0]
I1125 16:01:00.423049   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:07.0]
I1125 16:01:00.423054   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:07.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio3,HostPath:/dev/uio3,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1125 16:01:01.466156   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:09.0],},},}
I1125 16:01:01.466254   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:09.0]
I1125 16:01:01.466272   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:09.0]
I1125 16:01:01.466283   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:09.0]
I1125 16:01:01.466289   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:09.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio5,HostPath:/dev/uio5,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1125 19:42:14.546257   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:0b.0],},},}
I1125 19:42:14.546457   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:0b.0]
I1125 19:42:14.546487   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:0b.0]
I1125 19:42:14.546506   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:0b.0]
I1125 19:42:14.546514   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:0b.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio1,HostPath:/dev/uio1,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1125 19:42:15.462363   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:09.0],},},}
I1125 19:42:15.462431   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:09.0]
I1125 19:42:15.462442   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:09.0]
I1125 19:42:15.462450   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:09.0]
I1125 19:42:15.462455   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:09.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio5,HostPath:/dev/uio5,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1125 21:01:31.829987   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:0c.0],},},}
I1125 21:01:31.830176   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:0c.0]
I1125 21:01:31.830222   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:0c.0]
I1125 21:01:31.830237   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:0c.0]
I1125 21:01:31.830254   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:0c.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio2,HostPath:/dev/uio2,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1125 21:01:32.710781   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:0a.0],},},}
I1125 21:01:32.710832   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:0a.0]
I1125 21:01:32.710843   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:0a.0]
I1125 21:01:32.710848   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:0a.0]
I1125 21:01:32.710853   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:0a.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio0,HostPath:/dev/uio0,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1126 08:57:42.384715   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:0a.0],},},}
I1126 08:57:42.384877   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:0a.0]
I1126 08:57:42.384899   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:0a.0]
I1126 08:57:42.384908   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:0a.0]
I1126 08:57:42.384913   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:0a.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio0,HostPath:/dev/uio0,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1126 08:57:42.441752   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:09.0],},},}
I1126 08:57:42.441816   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:09.0]
I1126 08:57:42.441831   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:09.0]
I1126 08:57:42.441842   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:09.0]
I1126 08:57:42.441850   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:09.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio5,HostPath:/dev/uio5,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1126 09:00:47.202469   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:07.0],},},}
I1126 09:00:47.202542   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:07.0]
I1126 09:00:47.202555   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:07.0]
I1126 09:00:47.202561   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:07.0]
I1126 09:00:47.202567   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:07.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio3,HostPath:/dev/uio3,Permissions:mrw,},},Annotations:map[string]string{},},},}
I1126 09:00:47.833871   15147 server.go:114] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:00:08.0],},},}
I1126 09:00:47.833926   15147 pool_stub.go:64] GetDeviceSpecs(): for devices: [0000:00:08.0]
I1126 09:00:47.833936   15147 pool_stub.go:93] GetEnvs(): for devices: [0000:00:08.0]
I1126 09:00:47.833941   15147 pool_stub.go:108] GetMounts(): for devices: [0000:00:08.0]
I1126 09:00:47.833946   15147 server.go:123] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_DPDK_DEVICE: 0000:00:08.0,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/uio4,HostPath:/dev/uio4,Permissions:mrw,},},Annotations:map[string]string{},},},}

But I'm not quire sure what was the "dpdk-devbind --status" output when this log was generating.
As we start to check the "dpdk-devbind --status" command after quite long time when sriov-network-device-plugin generated the resource pool.
And the reason is that we figure out one of the DPDK device from resource pool is not working, and then finally we figure out it was not bind properly.
So we would like to know whether sriov-network-device-plugin will only discover those already bond DPDK device? or all device which matches its selector.

From device plugin, it seems reporting all devices as expected:
I1123 21:27:11.200593   15147 server.go:138] ListAndWatch(intel_sriov_dpdk_device): send devices &ListAndWatchResponse{Devices:[]*Device{&Device{ID:0000:00:0c.0,Health:Healthy,Topology:nil,},&Device{ID:0000:00:07.0,Health:Healthy,Topology:nil,},&Device{ID:0000:00:08.0,Health:Healthy,Topology:nil,},&Device{ID:0000:00:09.0,Health:Healthy,Topology:nil,},&Device{ID:0000:00:0a.0,Health:Healthy,Topology:nil,},&Device{ID:0000:00:0b.0,Health:Healthy,Topology:nil,},},}

Re device discovery, DP will:

First discovers all PCI devices on the host, no matter which dirver it binds to.
Then filter them according to each selector defined in configMap
The second step will filter out any device that doesn't match the driver in configMap driver selector.

Thanks quick help.
So if I understand correctly, this is the expected behaviour for SRIOV Network DP to include all device into "intel_sriov_dpdk_device" resource pool (even for the one which was not bond to DPDK yet)

Thanks quick help.
So if I understand correctly, this is the expected behaviour for SRIOV Network DP to include all device into "intel_sriov_dpdk_device" resource pool (even for the one which was not bond to DPDK yet)

nope, it should only expose devices whose driver is specified in selector.

@harper1011  I didn't see the PF device from dpdk-devbind --status, can you confirm PF exist on the host where Device Plugin is running? It looks like DP cannot find the PF of those VFs.

@zshi-redhat The PF doesn't exist there, as it is a VM node.
So SRIOV network DP will only discover the network device whose loaded driver can be found from "support list" which defined in selector?
which means from provided logs, the device of "0000:00:0c.0 " should be somehow bond to DPDK, but later due to some unknown reason it unbind and move to "Other Network devices"? and at this step, if we restart the SRIOV network DP Pod, then the resource pool should be refreshed with correct number 5 instead 6?

@zshi-redhat The PF doesn't exist there, as it is a VM node.
So SRIOV network DP will only discover the network device whose loaded driver can be found from "support list" which defined in selector?

Correct.

which means from provided logs, the device of "0000:00:0c.0 " should be somehow bond to DPDK, but later due to some unknown reason it unbind and move to "Other Network devices"?

It might be.

and at this step, if we restart the SRIOV network DP Pod, then the resource pool should be refreshed with correct number 5 instead 6?
Doe restart show right number of resource?

@zshi-redhat
We didn't get chance to try it.
The cluster got redeployed, and provide logs for asking why SRIOV network DP report wrong number of resource :(

Closing due to issue being stale. No bug found here it seems from logs. See virt support in readme.


make e2e-up fails to create capi-dns namespace

Short Description
Currently, when I run make e2e-up I see an error indicating that the capi-dns namespace does not exist. This same error then causes make test-connectivity-api to fail.
See this check run as an example.
However, the same check runs on the same commit passed on December 9th
I'm guessing some runtime in our tests that isn't pinned to a particular version has changed in a breaking way but I haven't tracked it down yet.
Steps To Reproduce
make build-images
make e2e-up

Output snippet toward the end:
Error from server (NotFound): namespaces "capi-dns" not found
configmap/coredns patched (no change)
Error from server (NotFound): namespaces "capi-dns" not found
configmap/coredns patched (no change)

Expected Behavior
make e2e-up succeeds without that error printing, and then make test-connectivity-api-dns passes.
Environment:

Cross-cluster connectivity version: 750c8d965b433229761cef5418daef339870745e
Kubernetes version: (use kubectl version):
Cloud provider or hardware configuration:

$ kubectl --context kind-management version
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.4", GitCommit:"224be7bdce5a9dd0c2fd0d46b83865648e2fe0ba", GitTreeState:"clean", BuildDate:"2019-12-11T12:47:40Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.1", GitCommit:"206bcadf021e76c27513500ca24182692aabd17e", GitTreeState:"clean", BuildDate:"2020-09-14T07:30:52Z", GoVersion:"go1.15", Compiler:"gc", Platform:"linux/amd64"}

$ kubectl --kubeconfig cluster-a.kubeconfig version
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.4", GitCommit:"224be7bdce5a9dd0c2fd0d46b83865648e2fe0ba", GitTreeState:"clean", BuildDate:"2019-12-11T12:47:40Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.2", GitCommit:"59603c6e503c87169aea6106f57b9f242f64df89", GitTreeState:"clean", BuildDate:"2020-02-07T01:05:17Z", GoVersion:"go1.13.5", Compiler:"gc", Platform:"linux/amd64"}

$ kubectl --kubeconfig cluster-b.kubeconfig version
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.4", GitCommit:"224be7bdce5a9dd0c2fd0d46b83865648e2fe0ba", GitTreeState:"clean", BuildDate:"2019-12-11T12:47:40Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.2", GitCommit:"59603c6e503c87169aea6106f57b9f242f64df89", GitTreeState:"clean", BuildDate:"2020-02-07T01:05:17Z", GoVersion:"go1.13.5", Compiler:"gc", Platform:"linux/amd64"}

$ clusterctl version
clusterctl version: &version.Info{Major:"0", Minor:"3", GitVersion:"v0.3.10", GitCommit:"af6630920560ca0e12179897b96d6ea8bd830b63", GitTreeState:"clean", BuildDate:"2020-10-01T14:29:50Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}

$ kind version
kind v0.9.0 go1.15.2 linux/amd64

Suspecting this diff between the two runs may be looking at closer:
< Installing Provider="cluster-api" Version="v0.3.11" TargetNamespace="capi-system"
< Installing Provider="bootstrap-kubeadm" Version="v0.3.11" TargetNamespace="capi-kubeadm-bootstrap-system"
< Installing Provider="control-plane-kubeadm" Version="v0.3.11" TargetNamespace="capi-kubeadm-control-plane-system"
---
> Installing Provider="cluster-api" Version="v0.3.12" TargetNamespace="capi-system"
> Installing Provider="bootstrap-kubeadm" Version="v0.3.12" TargetNamespace="capi-kubeadm-bootstrap-system"
> Installing Provider="control-plane-kubeadm" Version="v0.3.12" TargetNamespace="capi-kubeadm-control-plane-system"

Suspecting this diff between the two runs may be looking at closer:
< Installing Provider="cluster-api" Version="v0.3.11" TargetNamespace="capi-system"
< Installing Provider="bootstrap-kubeadm" Version="v0.3.11" TargetNamespace="capi-kubeadm-bootstrap-system"
< Installing Provider="control-plane-kubeadm" Version="v0.3.11" TargetNamespace="capi-kubeadm-control-plane-system"
---
> Installing Provider="cluster-api" Version="v0.3.12" TargetNamespace="capi-system"
> Installing Provider="bootstrap-kubeadm" Version="v0.3.12" TargetNamespace="capi-kubeadm-bootstrap-system"
> Installing Provider="control-plane-kubeadm" Version="v0.3.12" TargetNamespace="capi-kubeadm-control-plane-system"

@tylerschultz and I validated that this change does resolve this issue:
$ git diff
diff --git a/hack/e2e.sh b/hack/e2e.sh
index de0bf61..b01744b 100755
--- a/hack/e2e.sh
+++ b/hack/e2e.sh
@@ -143,7 +143,8 @@ function setup_management_cluster() {
   fi

   clusterctl init \
-    --kubeconfig-context "kind-${KIND_MANAGEMENT_CLUSTER}"
+    --kubeconfig-context "kind-${KIND_MANAGEMENT_CLUSTER}" \
+    --core "cluster-api:v0.3.11"

   # Enable the ClusterResourceSet feature in cluster API
   kubectl_mgc -n capi-webhook-system patch deployment capi-controller-manager \

We may make this fix temporarily to unblock things while we dig deeper into the root cause

@tylerschultz and I validated that this change does resolve this issue:
$ git diff
diff --git a/hack/e2e.sh b/hack/e2e.sh
index de0bf61..b01744b 100755
--- a/hack/e2e.sh
+++ b/hack/e2e.sh
@@ -143,7 +143,8 @@ function setup_management_cluster() {
   fi

   clusterctl init \
-    --kubeconfig-context "kind-${KIND_MANAGEMENT_CLUSTER}"
+    --kubeconfig-context "kind-${KIND_MANAGEMENT_CLUSTER}" \
+    --core "cluster-api:v0.3.11"

   # Enable the ClusterResourceSet feature in cluster API
   kubectl_mgc -n capi-webhook-system patch deployment capi-controller-manager \

We may make this fix temporarily to unblock things while we dig deeper into the root cause

Checked that the deployment.yaml data in the secret created in the e2e.sh script looks valid, and it does at first glance:
# targeting management cluster
kind export kubeconfig --name management

# dump secret data to file
kubectl get secret dns-server -oyaml | yq -r '.["data"]["deployment.yaml"]' | base64 -D > /tmp/dns-server.yaml

# compare to our manifests (no diff)
diff /tmp/dns-server.yaml manifests/dns-server/deployment.yaml

Checked that the deployment.yaml data in the secret created in the e2e.sh script looks valid, and it does at first glance:
# targeting management cluster
kind export kubeconfig --name management

# dump secret data to file
kubectl get secret dns-server -oyaml | yq -r '.["data"]["deployment.yaml"]' | base64 -D > /tmp/dns-server.yaml

# compare to our manifests (no diff)
diff /tmp/dns-server.yaml manifests/dns-server/deployment.yaml

CAPI's controller-manager shows the following in the logs:
kubectl -n capi-system logs -lcontrol-plane=controller-manager -c=manager

connectivity" "namespace"="default" "Resource kind"="Secret" "Resource name"="dns-server"
E0122 16:12:27.495097       1 controller.go:257] controller-runtime/controller "msg"="Reconciler error" "error"="[Object 'Kind' is missing in 'unstructured object has no kind', failed converting data to unstructured objects: failed to unmarshal the 1st yaml document: \"LS0tCmFwaVZlcnNpb246IHYxCmtpbmQ6IE5hbWVzcGFjZQptZXRhZGF0YToKICBuYW1lOiBjYXBpLWRucwotLS0KYXBpVmVyc2lvbjogdjEKa2luZDogU2VydmljZUFjY291bnQKbWV0YWRhdGE6CiAgbmFtZTogZG5zLXNlcnZlcgogIG5hbWVzcGFjZTogY2FwaS1kbnMKLS0tCmFwaVZlcnNpb246IGFwcHMvdjEKa2luZDogRGVwbG95bWVudAptZXRhZGF0YToKICBuYW1lOiBkbnMtc2VydmVyCiAgbmFtZXNwYWNlOiBjYXBpLWRucwogIGxhYmVsczoKICAgIGFwcDogZG5zLXNlcnZlcgpzcGVjOgogIHJlcGxpY2FzOiAxCiAgc2VsZWN0b3I6CiAgICBtYXRjaExhYmVsczoKICAgICAgYXBwOiBkbnMtc2VydmVyCiAgdGVtcGxhdGU6CiAgICBtZXRhZGF0YToKICAgICAgbGFiZWxzOgogICAgICAgIGFwcDogZG5zLXNlcnZlcgogICAgc3BlYzoKICAgICAgc2VydmljZUFjY291bnROYW1lOiBkbnMtc2VydmVyCiAgICAgIGNvbnRhaW5lcnM6CiAgICAgIC0gbmFtZTogZG5zLXNlcnZlcgogICAgICAgIGltYWdlOiBnaGNyLmlvL3Ztd2FyZS10YW56dS9jcm9zcy1jbHVzdGVyLWNvbm5lY3Rpdml0eS9kbnMtc2VydmVyOmRldgogICAgICAgIGFyZ3M6IFsgIi1jb25mIiwgIi9ldGMvY29yZWRucy9Db3JlZmlsZSIgXQogICAgICAgIGVudjoKICAgICAgICAtIG5hbWU6IE5BTUVTUEFDRQogICAgICAgICAgdmFsdWVGcm9tOgogICAgICAgICAgICBmaWVsZFJlZjoKICAgICAgICAgICAgICBmaWVsZFBhdGg6IG1ldGFkYXRhLm5hbWVzcGFjZQogICAgICAgIHZvbHVtZU1vdW50czoKICAgICAgICAtIG5hbWU6IGNvbmZpZy12b2x1bWUKICAgICAgICAgIG1vdW50UGF0aDogL2V0Yy9jb3JlZG5zCiAgICAgICAgICByZWFkT25seTogdHJ1ZQogICAgICAgIHBvcnRzOgogICAgICAgIC0gY29udGFpbmVyUG9ydDogNTMKICAgICAgICAgIG5hbWU6IGRucwogICAgICAgICAgcHJvdG9jb2w6IFVEUAogICAgICAgIC0gY29udGFpbmVyUG9ydDogNTMKICAgICAgICAgIG5hbWU6IGRucy10Y3AKICAgICAgICAgIHByb3RvY29sOiBUQ1AKICAgICAgdm9sdW1lczoKICAgICAgLSBuYW1lOiBjb25maWctdm9sdW1lCiAgICAgICAgY29uZmlnTWFwOgogICAgICAgICAgbmFtZTogZG5zLXNlcnZlci1jb3JlZmlsZQogICAgICAgICAgaXRlbXM6CiAgICAgICAgICAtIGtleTogQ29yZWZpbGUKICAgICAgICAgICAgcGF0aDogQ29yZWZpbGUKLS0tCmFwaVZlcnNpb246IHJiYWMuYXV0aG9yaXphdGlvbi5rOHMuaW8vdjFiZXRhMQpraW5kOiBSb2xlQmluZGluZwptZXRhZGF0YToKICBuYW1lOiBkbnMtc2VydmVyCiAgbmFtZXNwYWNlOiBjYXBpLWRucwpyb2xlUmVmOgogIGFwaUdyb3VwOiByYmFjLmF1dGhvcml6YXRpb24uazhzLmlvCiAga2luZDogUm9sZQogIG5hbWU6IGRucy1zZXJ2ZXIKc3ViamVjdHM6Ci0ga2luZDogU2VydmljZUFjY291bnQKICBuYW1lOiBkbnMtc2VydmVyCiAgbmFtZXNwYWNlOiBjYXBpLWRucwotLS0KYXBpVmVyc2lvbjogcmJhYy5hdXRob3JpemF0aW9uLms4cy5pby92MWJldGExCmtpbmQ6IFJvbGUKbWV0YWRhdGE6CiAgbmFtZTogZG5zLXNlcnZlcgogIG5hbWVzcGFjZTogY2FwaS1kbnMKcnVsZXM6Ci0gYXBpR3JvdXBzOgogIC0gImRpc2NvdmVyeS5rOHMuaW8iCiAgcmVzb3VyY2VzOgogIC0gZW5kcG9pbnRzbGljZXMKICB2ZXJiczoKICAtIGxpc3QKICAtIHdhdGNoCiAgLSBnZXQKLS0tCmFwaVZlcnNpb246IHYxCmtpbmQ6IFNlcnZpY2UKbWV0YWRhdGE6CiAgbmFtZTogZG5zLXNlcnZlcgogIG5hbWVzcGFjZTogY2FwaS1kbnMKICBsYWJlbHM6CiAgICBhcHA6IGRucy1zZXJ2ZXIKc3BlYzoKICBzZWxlY3RvcjoKICAgIGFwcDogZG5zLXNlcnZlcgogIHR5cGU6IENsdXN0ZXJJUAogIHBvcnRzOgogIC0gcG9ydDogNTMKICAgIHRhcmdldFBvcnQ6IDUzCiAgICBwcm90b2NvbDogVENQCiAgICBuYW1lOiBkbnMtdGNwCiAgLSBwb3J0OiA1MwogICAgdGFyZ2V0UG9ydDogNTMKICAgIHByb3RvY29sOiBVRFAKICAgIG5hbWU6IGRucwotLS0KYXBpVmVyc2lvbjogdjEKa2luZDogQ29uZmlnTWFwCm1ldGFkYXRhOgogIG5hbWU6IGRucy1zZXJ2ZXItY29yZWZpbGUKICBuYW1lc3BhY2U6IGNhcGktZG5zCmRhdGE6CiAgQ29yZWZpbGU6IHwKICAgIHhjYy50ZXN0IHsKICAgICAgICBsb2cKICAgICAgICBlcnJvcnMKICAgICAgICBoZWFsdGggewogICAgICAgICAgbGFtZWR1Y2sgNXMKICAgICAgICB9CiAgICAgICAgY3Jvc3NjbHVzdGVyCiAgICAgICAgcmVhZHkKICAgICAgICBwcm9tZXRoZXVzIDo5MTUzCiAgICAgICAgY2FjaGUgMzAKICAgICAgICByZWxvYWQKICAgICAgICBsb29wCiAgICAgICAgbG9hZGJhbGFuY2UKICAgICAgICB3aG9hbWkKICAgIH0K\\n\": error unmarshaling JSON: while decoding JSON: json: cannot unmarshal string into Go value of type map[string]interface {}]" "controller"="clusterresourceset" "name"="connectivity" "namespace"="default"

I tried deleting everything but the namespace resource in the deployment.yaml and got the same error (with just a smaller base64 encoded string).
But when I try running with --core "cluster-api:v0.3.11" and creating some invalid yaml, I see an error like this instead:
E0122 17:05:34.746500       1 controller.go:257] controller-runtime/controller "msg"="Reconciler error" "error"="failed converting data to unstructured objects: failed to unmarshal the 1st yaml document: \"---\\napiVersion: v1\\nkind: Namespace\\nmetadata:\\n  name: capi-dns\\n%%%\\n\": error converting YAML to JSON: yaml: line 6: could not find expected directive name" "controller"="clusterresourceset" "name"="connectivity" "namespace"="default"

Note that the string shown after "failed to unmarshal the 1st yaml document" is not base64 encoded in the error in v0.3.11. It seems that v0.3.12 may be missing the base64 decode somewhere. Reviewing the diff on v0.3.11 to v0.3.12 I don't see anything obvious yet...

CAPI's controller-manager shows the following in the logs:
kubectl -n capi-system logs -lcontrol-plane=controller-manager -c=manager

connectivity" "namespace"="default" "Resource kind"="Secret" "Resource name"="dns-server"
E0122 16:12:27.495097       1 controller.go:257] controller-runtime/controller "msg"="Reconciler error" "error"="[Object 'Kind' is missing in 'unstructured object has no kind', failed converting data to unstructured objects: failed to unmarshal the 1st yaml document: \"LS0tCmFwaVZlcnNpb246IHYxCmtpbmQ6IE5hbWVzcGFjZQptZXRhZGF0YToKICBuYW1lOiBjYXBpLWRucwotLS0KYXBpVmVyc2lvbjogdjEKa2luZDogU2VydmljZUFjY291bnQKbWV0YWRhdGE6CiAgbmFtZTogZG5zLXNlcnZlcgogIG5hbWVzcGFjZTogY2FwaS1kbnMKLS0tCmFwaVZlcnNpb246IGFwcHMvdjEKa2luZDogRGVwbG95bWVudAptZXRhZGF0YToKICBuYW1lOiBkbnMtc2VydmVyCiAgbmFtZXNwYWNlOiBjYXBpLWRucwogIGxhYmVsczoKICAgIGFwcDogZG5zLXNlcnZlcgpzcGVjOgogIHJlcGxpY2FzOiAxCiAgc2VsZWN0b3I6CiAgICBtYXRjaExhYmVsczoKICAgICAgYXBwOiBkbnMtc2VydmVyCiAgdGVtcGxhdGU6CiAgICBtZXRhZGF0YToKICAgICAgbGFiZWxzOgogICAgICAgIGFwcDogZG5zLXNlcnZlcgogICAgc3BlYzoKICAgICAgc2VydmljZUFjY291bnROYW1lOiBkbnMtc2VydmVyCiAgICAgIGNvbnRhaW5lcnM6CiAgICAgIC0gbmFtZTogZG5zLXNlcnZlcgogICAgICAgIGltYWdlOiBnaGNyLmlvL3Ztd2FyZS10YW56dS9jcm9zcy1jbHVzdGVyLWNvbm5lY3Rpdml0eS9kbnMtc2VydmVyOmRldgogICAgICAgIGFyZ3M6IFsgIi1jb25mIiwgIi9ldGMvY29yZWRucy9Db3JlZmlsZSIgXQogICAgICAgIGVudjoKICAgICAgICAtIG5hbWU6IE5BTUVTUEFDRQogICAgICAgICAgdmFsdWVGcm9tOgogICAgICAgICAgICBmaWVsZFJlZjoKICAgICAgICAgICAgICBmaWVsZFBhdGg6IG1ldGFkYXRhLm5hbWVzcGFjZQogICAgICAgIHZvbHVtZU1vdW50czoKICAgICAgICAtIG5hbWU6IGNvbmZpZy12b2x1bWUKICAgICAgICAgIG1vdW50UGF0aDogL2V0Yy9jb3JlZG5zCiAgICAgICAgICByZWFkT25seTogdHJ1ZQogICAgICAgIHBvcnRzOgogICAgICAgIC0gY29udGFpbmVyUG9ydDogNTMKICAgICAgICAgIG5hbWU6IGRucwogICAgICAgICAgcHJvdG9jb2w6IFVEUAogICAgICAgIC0gY29udGFpbmVyUG9ydDogNTMKICAgICAgICAgIG5hbWU6IGRucy10Y3AKICAgICAgICAgIHByb3RvY29sOiBUQ1AKICAgICAgdm9sdW1lczoKICAgICAgLSBuYW1lOiBjb25maWctdm9sdW1lCiAgICAgICAgY29uZmlnTWFwOgogICAgICAgICAgbmFtZTogZG5zLXNlcnZlci1jb3JlZmlsZQogICAgICAgICAgaXRlbXM6CiAgICAgICAgICAtIGtleTogQ29yZWZpbGUKICAgICAgICAgICAgcGF0aDogQ29yZWZpbGUKLS0tCmFwaVZlcnNpb246IHJiYWMuYXV0aG9yaXphdGlvbi5rOHMuaW8vdjFiZXRhMQpraW5kOiBSb2xlQmluZGluZwptZXRhZGF0YToKICBuYW1lOiBkbnMtc2VydmVyCiAgbmFtZXNwYWNlOiBjYXBpLWRucwpyb2xlUmVmOgogIGFwaUdyb3VwOiByYmFjLmF1dGhvcml6YXRpb24uazhzLmlvCiAga2luZDogUm9sZQogIG5hbWU6IGRucy1zZXJ2ZXIKc3ViamVjdHM6Ci0ga2luZDogU2VydmljZUFjY291bnQKICBuYW1lOiBkbnMtc2VydmVyCiAgbmFtZXNwYWNlOiBjYXBpLWRucwotLS0KYXBpVmVyc2lvbjogcmJhYy5hdXRob3JpemF0aW9uLms4cy5pby92MWJldGExCmtpbmQ6IFJvbGUKbWV0YWRhdGE6CiAgbmFtZTogZG5zLXNlcnZlcgogIG5hbWVzcGFjZTogY2FwaS1kbnMKcnVsZXM6Ci0gYXBpR3JvdXBzOgogIC0gImRpc2NvdmVyeS5rOHMuaW8iCiAgcmVzb3VyY2VzOgogIC0gZW5kcG9pbnRzbGljZXMKICB2ZXJiczoKICAtIGxpc3QKICAtIHdhdGNoCiAgLSBnZXQKLS0tCmFwaVZlcnNpb246IHYxCmtpbmQ6IFNlcnZpY2UKbWV0YWRhdGE6CiAgbmFtZTogZG5zLXNlcnZlcgogIG5hbWVzcGFjZTogY2FwaS1kbnMKICBsYWJlbHM6CiAgICBhcHA6IGRucy1zZXJ2ZXIKc3BlYzoKICBzZWxlY3RvcjoKICAgIGFwcDogZG5zLXNlcnZlcgogIHR5cGU6IENsdXN0ZXJJUAogIHBvcnRzOgogIC0gcG9ydDogNTMKICAgIHRhcmdldFBvcnQ6IDUzCiAgICBwcm90b2NvbDogVENQCiAgICBuYW1lOiBkbnMtdGNwCiAgLSBwb3J0OiA1MwogICAgdGFyZ2V0UG9ydDogNTMKICAgIHByb3RvY29sOiBVRFAKICAgIG5hbWU6IGRucwotLS0KYXBpVmVyc2lvbjogdjEKa2luZDogQ29uZmlnTWFwCm1ldGFkYXRhOgogIG5hbWU6IGRucy1zZXJ2ZXItY29yZWZpbGUKICBuYW1lc3BhY2U6IGNhcGktZG5zCmRhdGE6CiAgQ29yZWZpbGU6IHwKICAgIHhjYy50ZXN0IHsKICAgICAgICBsb2cKICAgICAgICBlcnJvcnMKICAgICAgICBoZWFsdGggewogICAgICAgICAgbGFtZWR1Y2sgNXMKICAgICAgICB9CiAgICAgICAgY3Jvc3NjbHVzdGVyCiAgICAgICAgcmVhZHkKICAgICAgICBwcm9tZXRoZXVzIDo5MTUzCiAgICAgICAgY2FjaGUgMzAKICAgICAgICByZWxvYWQKICAgICAgICBsb29wCiAgICAgICAgbG9hZGJhbGFuY2UKICAgICAgICB3aG9hbWkKICAgIH0K\\n\": error unmarshaling JSON: while decoding JSON: json: cannot unmarshal string into Go value of type map[string]interface {}]" "controller"="clusterresourceset" "name"="connectivity" "namespace"="default"

I tried deleting everything but the namespace resource in the deployment.yaml and got the same error (with just a smaller base64 encoded string).
But when I try running with --core "cluster-api:v0.3.11" and creating some invalid yaml, I see an error like this instead:
E0122 17:05:34.746500       1 controller.go:257] controller-runtime/controller "msg"="Reconciler error" "error"="failed converting data to unstructured objects: failed to unmarshal the 1st yaml document: \"---\\napiVersion: v1\\nkind: Namespace\\nmetadata:\\n  name: capi-dns\\n%%%\\n\": error converting YAML to JSON: yaml: line 6: could not find expected directive name" "controller"="clusterresourceset" "name"="connectivity" "namespace"="default"

Note that the string shown after "failed to unmarshal the 1st yaml document" is not base64 encoded in the error in v0.3.11. It seems that v0.3.12 may be missing the base64 decode somewhere. Reviewing the diff on v0.3.11 to v0.3.12 I don't see anything obvious yet...

We discussed this a bit offline and agreed it probably makes sense to just stop using ClusterResourceSet in our e2e scripts for now, so will consider doing that as a PR unless someone beats me to it.

We discussed this a bit offline and agreed it probably makes sense to just stop using ClusterResourceSet in our e2e scripts for now, so will consider doing that as a PR unless someone beats me to it.


Concurrernt write causes data corruption

The client's websockets lib gives out an exception(seems to received corrupted data) when there are many threads sending data to it at the same time.

received 1007 (invalid data); then sent 1007 (invalid data)

lock = asyncio.Lock()
async with lock:
        await conn.send(msg)

I already tried to set up a lock, but it didn't make any difference.

I don't have enough information to understand the problem. I don't even know if you're using websockets on the server side, the client side, or both. However, I'm pretty sure that websockets doesn't have that kind of bug.
If you provide a minimal example allowing me to reproduce the issue, I'll take a look.


Not compatible with the version of your running IDE (IntelliJ IDEA 2022.1, PyCharm 2022.1.1)

Is your feature request related to a problem? Please describe.
I'm using IntelliJ IDEA 2022.1 and PyCharm 2022.1.1. When I try to install the plugin from the marketplace, there is a warning message Not compatible with the version of your running IDE (IntelliJ IDEA 2022.1, PyCharm 2022.1.1) and I can't install the plugin.

Describe the solution you'd like
I hope to use this awesome plugin for latest PyCharm.
Describe alternatives you've considered
I also tried installing the plugin from ZIP but IDE shows Plugin 'AutoCp' (version 'v0.7.3') is not compatible with the current version of the IDE, ~~.

Additional context
This is my first issue for GitHub open source project so please tell me if I missed some important notice or broke community rules.

Hi @sunovivid, this was fixed in v0.7.4 which was not properly published, thanks for reminding me. There seems to be some issues while publishing, I am debugging them and will release it soon. btw, you did it nice on your first issue. congrats

Hi @sunovivid, v0.7.4 is now available to download as zip.


Is it possible to associate an already created QSO with an event?

I can't find anything in the QSO edit screen or Logbook list that seems to support this.

Yes, edit the QSO and changed the selected events and save the QSO. Let me know if this works for you.

i'll test that out now

I think I see how you are doing this now.  "No Event" or "None" as a valid event choice would be helpful instead of the non-intuitive deletion of all events if you just want to look at the raw log.


Add endtoend crossdock

Codecov Report

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

@@             Coverage Diff              @@
##             master     #154      +/-   ##
============================================
- Coverage     36.28%   36.24%   -0.05%
- Complexity      596      598       +2
============================================
  Files            94       94
  Lines          6349     6349
  Branches       1052     1052
============================================
- Hits           2304     2301       -3
- Misses         3861     3866       +5
+ Partials        184      182       -2

Impacted Files
Coverage Δ
Complexity Δ

...c/main/java/com/uber/jaeger/senders/UDPSender.java
67.34% <0%> (-4.09%)
10% <0%> (ø)

...java/com/uber/jaeger/reporters/RemoteReporter.java
80.95% <0%> (-3.18%)
5% <0%> (ø)

...uber/jaeger/reporters/protocols/TUDPTransport.java
83.05% <0%> (+1.69%)
16% <0%> (+2%)
:arrow_up:

Continue to review full report at Codecov.

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