Error on Report pages

I found this error "An internal error occurred while getting resources list. The current list of resources is not available. Diagnostics: Failure to receive response from manager daemon."

Please help to suggest me.

Hi, Dexus

How are your feed status? Administration->Feed Status
It looks for me like you interrupt the container while it was syncing. you should restart the container - then run (after feed status is not syncing anymore) the gvmd --rebuild-gvmd-data=all followed by a --rebuild-scap
Hope it help.

It's not work.

more error in below.

can you please provide docker inspect gvm99 ? I never had this issue before.

Can't help here, if you not provide information's.

Dexus,
Here's the result
sudo docker inspect gvm99
[
{
"Id": "7162f977530519747fef595a667279b1cc4293f8c47562aed966ca12d18aea94",
"Created": "2022-05-24T14:32:25.439354766Z",
"Path": "/opt/setup/scripts/entrypoint.sh",
"Args": [
"/usr/bin/supervisord",
"-n",
"-c",
"/etc/supervisord.conf"
],
"State": {
"Status": "running",
"Running": true,
"Paused": false,
"Restarting": false,
"OOMKilled": false,
"Dead": false,
"Pid": 115953,
"ExitCode": 0,
"Error": "",
"StartedAt": "2022-05-27T15:37:52.712046198Z",
"FinishedAt": "2022-05-27T15:37:45.740050842Z"
},
"Image": "sha256:b7bab7d0e09d22e4514db0e2b0a0d12b5f94962a2b49c3ccc2c771493f222d9d",
"ResolvConfPath": "/var/lib/docker/containers/7162f977530519747fef595a667279b1cc4293f8c47562aed966ca12d18aea94/resolv.conf",
"HostnamePath": "/var/lib/docker/containers/7162f977530519747fef595a667279b1cc4293f8c47562aed966ca12d18aea94/hostname",
"HostsPath": "/var/lib/docker/containers/7162f977530519747fef595a667279b1cc4293f8c47562aed966ca12d18aea94/hosts",
"LogPath": "",
"Name": "/gvm99",
"RestartCount": 0,
"Driver": "overlay2",
"MountLabel": "",
"ProcessLabel": "",
"AppArmorProfile": "",
"ExecIDs": null,
"HostConfig": {
"Binds": null,
"ContainerIDFile": "",
"LogConfig": {
"Type": "journald",
"Config": {}
},
"NetworkMode": "default",
"PortBindings": {
"22/tcp": [
{
"HostIp": "",
"HostPort": "2224"
}
],
"5432/tcp": [
{
"HostIp": "",
"HostPort": "5434"
}
],
"9392/tcp": [
{
"HostIp": "",
"HostPort": "8086"
}
]
},
"RestartPolicy": {
"Name": "no",
"MaximumRetryCount": 0
},
"AutoRemove": false,
"VolumeDriver": "",
"VolumesFrom": null,
"CapAdd": null,
"CapDrop": null,
"Dns": [],
"DnsOptions": [],
"DnsSearch": [],
"ExtraHosts": null,
"GroupAdd": null,
"IpcMode": "",
"Cgroup": "",
"Links": null,
"OomScoreAdj": 0,
"PidMode": "",
"Privileged": false,
"PublishAllPorts": false,
"ReadonlyRootfs": false,
"SecurityOpt": null,
"UTSMode": "",
"UsernsMode": "",
"ShmSize": 67108864,
"Runtime": "docker-runc",
"ConsoleSize": [
0,
0
],
"Isolation": "",
"CpuShares": 0,
"Memory": 0,
"NanoCpus": 0,
"CgroupParent": "",
"BlkioWeight": 0,
"BlkioWeightDevice": null,
"BlkioDeviceReadBps": null,
"BlkioDeviceWriteBps": null,
"BlkioDeviceReadIOps": null,
"BlkioDeviceWriteIOps": null,
"CpuPeriod": 0,
"CpuQuota": 0,
"CpuRealtimePeriod": 0,
"CpuRealtimeRuntime": 0,
"CpusetCpus": "",
"CpusetMems": "",
"Devices": [],
"DiskQuota": 0,
"KernelMemory": 0,
"MemoryReservation": 0,
"MemorySwap": 0,
"MemorySwappiness": -1,
"OomKillDisable": false,
"PidsLimit": 0,
"Ulimits": null,
"CpuCount": 0,
"CpuPercent": 0,
"IOMaximumIOps": 0,
"IOMaximumBandwidth": 0
},
"GraphDriver": {
"Name": "overlay2",
"Data": {
"LowerDir": "/var/lib/docker/overlay2/5dc58b458b230cdc7803e6cfca068fcc512ceabb534f74d140794fdb0e3105d2-init/diff:/var/lib/docker/overlay2/16a6152ac921f7fe2319ed2a3833f3543001c214e5934986267d1c6e2df70cd4/diff:/var/lib/docker/overlay2/10a2909508cdec2fd185a10bbe9c2da427cdddf2536c62563e932a496a83c5cf/diff:/var/lib/docker/overlay2/62f53717e9dc8f7700cccf0771c2f79974283699da6f9d8d79fd59288caf89dd/diff:/var/lib/docker/overlay2/dbd524fb0aa84d8ba240b83c5e314ae21c7f4b17849b86e2b9a262264c489d86/diff:/var/lib/docker/overlay2/20e3fcab4cd31f7a5b06e65a91230b033f54b06f631a13852d1e8c50982cc9bf/diff:/var/lib/docker/overlay2/0c7f8d6a7ef38381fc3421bbbee237f4cb3139b2a2598cddf3383ada7d1a4cd8/diff:/var/lib/docker/overlay2/c3058e5fbbbfc3887b3227407f2c0455ed8e4cbd4c9d9f20f6a61796e8178478/diff:/var/lib/docker/overlay2/e80699c14b1e67036139af1102d5dbc66f83fb2bdfdefcb93fff9f5f5f2ae267/diff:/var/lib/docker/overlay2/db730773ad06e9a819aede58ef0aa9fc33718c8de9a39d4b04b5adbefe385e82/diff:/var/lib/docker/overlay2/b9450633d2e311206dbf24c4b278bae7558a32ec956f84ba0406203e242f6cb2/diff:/var/lib/docker/overlay2/b33d655370b4c5ab2364ecf0bf150998caf9f8117eae460bcfd93d4ba1bf5b8b/diff",
"MergedDir": "/var/lib/docker/overlay2/5dc58b458b230cdc7803e6cfca068fcc512ceabb534f74d140794fdb0e3105d2/merged",
"UpperDir": "/var/lib/docker/overlay2/5dc58b458b230cdc7803e6cfca068fcc512ceabb534f74d140794fdb0e3105d2/diff",
"WorkDir": "/var/lib/docker/overlay2/5dc58b458b230cdc7803e6cfca068fcc512ceabb534f74d140794fdb0e3105d2/work"
}
},
"Mounts": [],
"Config": {
"Hostname": "7162f9775305",
"Domainname": "",
"User": "",
"AttachStdin": false,
"AttachStdout": false,
"AttachStderr": false,
"ExposedPorts": {
"22/tcp": {},
"5432/tcp": {},
"9392/tcp": {}
},
"Tty": false,
"OpenStdin": false,
"StdinOnce": false,
"Env": [
"DB_PASSWORD=GVMP@ssw0rd",
"PASSWORD=CatchingFire99",
"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
"POSTGRESQL_VERSION=13",
"GSAD_VERSION=21.4.4",
"GSA_VERSION=21.4.4",
"GVM_LIBS_VERSION=21.4.4",
"GVMD_VERSION=21.4.5",
"OPENVAS_SCANNER_VERSION=21.4.4",
"OPENVAS_SMB_VERSION=21.4.0",
"PYTHON_GVM_VERSION=21.11.0",
"OSPD_OPENVAS_VERSION=21.4.4",
"GVM_TOOLS_VERSION=21.10.0",
"SYSTEM_DIST=debian",
"SUPVISD=supervisorctl",
"USERNAME=admin",
"PASSWORD_FILE=none",
"TIMEOUT=15",
"DEBUG=N",
"RELAYHOST=smtp",
"SMTPPORT=25",
"AUTO_SYNC=YES",
"AUTO_SYNC_ON_START=YES",
"HTTPS=true",
"CERTIFICATE=none",
"CERTIFICATE_KEY=none",
"TZ=Etc/UTC",
"SSHD=false",
"DB_PASSWORD_FILE=none",
"DEBIAN_FRONTEND=noninteractive",
"LANG=en_US.UTF-8",
"SETUP=0",
"OPT_PDF=1",
"LANGUAGE=en_US.UTF-8",
"LC_ALL=en_US.UTF-8"
],
"Cmd": [
"/usr/bin/supervisord",
"-n",
"-c",
"/etc/supervisord.conf"
],
"ArgsEscaped": true,
"Image": "deineagenturug/gvm:latest-data-full",
"Volumes": null,
"WorkingDir": "",
"Entrypoint": [
"/opt/setup/scripts/entrypoint.sh"
],
"OnBuild": null,
"Labels": {}
},
"NetworkSettings": {
"Bridge": "",
"SandboxID": "4a1249087bec5284c62a239a99398c4dfe95355fdd3b3d1cabf3d85422249b4b",
"HairpinMode": false,
"LinkLocalIPv6Address": "",
"LinkLocalIPv6PrefixLen": 0,
"Ports": {
"22/tcp": [
{
"HostIp": "<IP_ADDRESS>",
"HostPort": "2224"
}
],
"5432/tcp": [
{
"HostIp": "<IP_ADDRESS>",
"HostPort": "5434"
}
],
"9392/tcp": [
{
"HostIp": "<IP_ADDRESS>",
"HostPort": "8086"
}
]
},
"SandboxKey": "/var/run/docker/netns/4a1249087bec",
"SecondaryIPAddresses": null,
"SecondaryIPv6Addresses": null,
"EndpointID": "43540ba21b06fa3bf039420480c2a172f261c45bba11c2d73a9c9a02fe4527f0",
"Gateway": "<IP_ADDRESS>",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"IPAddress": "<IP_ADDRESS>",
"IPPrefixLen": 16,
"IPv6Gateway": "",
"MacAddress": "02:42:ac:11:00:02",
"Networks": {
"bridge": {
"IPAMConfig": null,
"Links": null,
"Aliases": null,
"NetworkID": "53968d67d5f19c9725674b12b67863ba60aba8f8ee8b8e7e297447bc179ca6be",
"EndpointID": "43540ba21b06fa3bf039420480c2a172f261c45bba11c2d73a9c9a02fe4527f0",
"Gateway": "<IP_ADDRESS>",
"IPAddress": "<IP_ADDRESS>",
"IPPrefixLen": 16,
"IPv6Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"MacAddress": "02:42:ac:11:00:02"
}
}
}
}
]

Hmm, I'm not sure what here is the problem. It can have todo with your security profiles or with your firewall (don't expect that here). Can you look what the supervisorctl command within your container showing?


Validators Lib Check

Please refer to the git commits to know more about the code tweaks
Massiles.

Looks good!


stdout and stderr should be kept for failed jobs if they will be retried

Current those files will be remove if job retries.

Implemented in 0.9.0


fix: find the nearest tag for workflow updates

Description
The head of the default branch might not be tagged, i.e. ci commit, ... We now find the latest tag in the commit history to be able to create the comment when updating the workflows.
Verification
Locally.

:tada: This PR is included in version 1.3.7 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Pull Requests Don't appear

I created a pull request. It doesn't appear in the [Pull Requests] tab even though it seems my plugin is authenticating and otherwise working fine.
The Open in browser... link does faithfully open the URL (which shows a blank blue screen unless I revisit the url). Once displayed I can plainly see my PR in the browser view.
PR's are a fundamental use case (indeed, if not for PRs I don't see any reason to use this plugin at all?). Cloning, push and pull are all native functionality for git. It's only the PR functionality that is Azure specific, and it's not working very well.

For more info, I created the PR with the plugin, but subsequent display of the [Pull Requests] tab shows zero requested by me.


Add right-to-left layout support for EditorSpinSlider.

Add RTL layout support for EditorSpinSlider.
Property suffix is separated by thin space (one-fifth of an em).
Fix editor inspector margin for RTL layout.

Note: Localized suffixes are not implemented, one on the screenshot was hard-coded for testing only.

Thanks!


Update Airnode v0.9 from 0.9.0 to 0.9.1

Airnode v0.9.1 has been released https://github.com/api3dao/airnode/pull/1523

Done and deployed


created file 10

I created file 10 with 2 questions and answers
@Londeka-Zikalala  @NgomsoGaya @tommyshado  Please review and merge this PR .

👍🏿


Add escape characters to the regex on filter by test name

When I try to run a single test containing special chars in its name (eg. parenthesis), it doesn't run. I think that text without escaping chars applied to filter option don't match the test name

Hi @marilari88,
I don't see the problem with the adapter. I think it is a problem with the neojest framework. Do you mind opening an issue there?

Hi @adrigzr, the problem is related to Jest cli command. I opened a PR with a fix


Memory hungry

I've been using this for a couple of days and it's eating all my ram freezing my computer. Maybe there is an optimization to avoid using all that memory.

There are some tips for reducing memory usage on the documentation site:
https://umi-tools.readthedocs.io/en/latest/faq.html
For most samples, if you are running without --output-stats and you are remember to include --per-cell if you are doing single cell work, deduplication should use less memory than read alignment does. If you are using paired end sequencing and have a lot of reads where the two ends map to different chromosomes, you can also save memory with --chimeric-reads=discard, but you will then loose all those reads where the two ends map to different chromosomes.
However, for some samples with very large UMI networks there is just no way around the fact that the job is memory requiring. In order to compute an process a network of 20,000 UMIs at one location for example, it might be necessary to store up to 400 million connections.


[main< ] Improve storage memory

Description
Improve storage memory usage
Pull request type
Please check what kind of PR this is:

[x] Fix or improvement of an existing page
[ ] New documentation page, release related

Related PRs and issues
PR this doc page is related to:
(especially necessary if the PR is related to a release)
Closes https://github.com/memgraph/documentation/issues/106
Checklist:

[ ] Check all content with Grammarly
[ ] Perform a self-review of my code
[ ] Make corresponding changes to the rest of the documentation (consult with the DX team)
[ ] The build passes locally
[ ] My changes generate no new warnings or errors
[ ] Add a corresponding label
[ ] If release-related, add a product and version label
[ ] If release-related, add release note on product PR

I need to finish the LDAP example, delete the LDAP file and create a redirect


Does undefined alias to auto include compact notation?

Right now, this proposal specifies that undefined aliases to "auto".
Does this also include "compact" notation, considering ICU defaults it to "min2" for compact notation so that true equates to 'min2" for compact notation in the current Intl.NumberFormat?

Good catch!  Yes, I will change the proposal to reflect web reality, which is using "min2" for compact notation.


Get Travis working for PHP 5.4

The last version of PHPUnit to support PHP 5.4 was 4.8.*, but I'm having trouble getting that installed locally:
$ composer require --dev phpunit/phpunit 4.8.34
You are running composer with xdebug enabled. This has a major impact on runtime performance. See https://getcomposer.org/xdebug
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - phpunit/phpunit 4.8.34 conflicts with phpunit/phpunit-mock-objects[3.4.3].
    - phpunit/phpunit 4.8.34 conflicts with phpunit/phpunit-mock-objects[3.4.3].
    - phpunit/phpunit 4.8.34 conflicts with phpunit/phpunit-mock-objects[3.4.3].
    - Installation request for phpunit/phpunit 4.8.34 -> satisfiable by phpunit/phpunit[4.8.34].
    - Installation request for phpunit/phpunit-mock-objects (locked at 3.4.3) -> satisfiable by phpunit/phpunit-mock-objects[3.4.3].

Installation failed, reverting ./composer.json to its original content.

Until we drop support for 5.4 (https://github.com/vimeo/mill/issues/13), we should at least get tests running against it.

Mill will continue to theoretically work under 5.4 until https://github.com/vimeo/mill/issues/13, but I'm not going to spend any time fighting Composer and Travis to get it building under it as it's been EOL'd for a over a year now.


speed of scroll

I notice that when body lock is enabled the speed of the scroll is slow.  Is there an option or way to increase the scroll speed?

Perhaps you're missing -webkit-overflow-scrolling: touch;?


Getting 404 not found on resources.

Describe the bug
I've been trying to recover a BookStack installation from a backup for a client on a Plesk server. I don't have any configuration files that I could use and the domain hasn't changed. When entering the website it's missing all css and js files and you can see they're all giving a 404 error. I followed the manual installation right before the php artisan migrate step.
Steps To Reproduce
Steps to reproduce the behavior:

Go to the website.
All assets are missing.

Expected behavior
The website can properly find and load the files from dist/
Screenshots
If applicable, add screenshots to help explain your problem.

Your Configuration (please complete the following information):

Exact BookStack Version (Found in settings): v0.30.3
PHP Version: 7.4
Hosting Method (Nginx/Apache/Docker): Apache. Using Plesk.

Additional context
I added the following config to Apache:
ServerAdmin<EMAIL_ADDRESS>DocumentRoot /var/www/vhosts/{domain}/{subdomain}.{domain}/public
ServerName {domain}

<Directory /var/www/vhosts/{domain}/{subdomain}.{domain}/public/>
	Options FollowSymlinks
	AllowOverride All
	Require all granted
</Directory>

If I don't have this config, I can go to domain.com/public/login and it works fine, though that's not the recommended configuration.

The BookStack installation seems to work, but it won't load any files.

Hi @Niquify,
Sorry for my late response, Are you still experiencing issues?
If so, double check that the .env file and check the APP_URL value aligns with the URL you're now hosting BookStack on, including the starting http/https part.
Failing that, we'll need to see what URL bookstack is trying to access the resources on, by looking at the page source.
If you are accessing the instance with public in the URL then it's likely that you could have an insecure configuration unless specific care has been made.

Hey @ssddanbrown,
The APP_URL value matches the URL for bookstack.
The resources that are returning 404 are being accesed on APP_URL/dist/, ex: example.com/dist/file.js

@Niquify Okay, What do you see when you attempt to directly go to the URL https://<domain>/dist/app.js?

@ssddanbrown I get a 404 Not Found

Since there's been no follow-up I'm going to close this. If the issue remains and is something you still require to be fixed please open a new issue, referencing this one.

I'd like to re-open this if possible. I am using Plesk but when I navigate to the resource directly, I get the 404 page but with no CSS, ironically.

My bad, I was on the development branch and not release.


Support for BusinessTypes

I tried to copy the existing structure as much as possible to support Entity BusinessType and method businesstypes.list

Hi @maartendeblock. First off, thanks for the PR! However, we're currently working on implementing all calls on the v2-refactor branch. We've covered most calls already, including business types. We're nearly done and will merge these changes soon. I'm therefore going to close this PR. We appreciate the effort though!

Tnx for letting me know. I'll start working with the v2-refactor branch.


(2.0) Connected event emitted constantly

I'm submitting a ...
[x] bug report

Summary
From: https://github.com/bitfocus/companion-module-atem/issues/50

After reconnecting, the connected event can sometimes be emitted at least once a second

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)

I think it is likely this was down to the child being killed due to either the child or parent missing pings, so I am assuming this to be resolved in 2.0.0-nightly-20200626-195656-eb05a5c.0


[1704] Fix age range mappings

Context
We need the DTTP Id that corresponds to an age range in Register so we have a list of DTTP Ids. Some of them were incorrect.
Changes proposed in this pull request
Update them.
Guidance to review
The entity set in question in DTTP is dfe_coursephases. These should match their DTTP equivalent.
I'll review existing data in register and correct any that were incorrectly saved.

 Some age ranges are incorrectly mapped


About the moving speed

Thank you for developing the bot:)
Is it possible to let the train moving faster?

Great Idea, I'll see if I can figure that out. Stay tuned.

Done. I've added a "Speed Hack" bookmarklet.
https://github.com/manila/googlemaps-snake-bot/blob/master/googlemaps-snake-speedhack-bookmarklet


pretrained backbone

it is possibe luse pretrained backbone and train only predictor ?

you can. but the pretrained backbone for k210 I forced the deletion of some layers, so maybe you need retrain backbone.


add semantic versioning with github actions

:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


zod for validation

swaps out yup for zod
updates readme

Thank you @Staceadam  but i already added it while working on docs PR #25 , its gonna be merged soon.
By the way would love to hear your feedback about the new docs we are writing 🙏

Whoops. Sorry about the extra noise. I misunderstood your comment on the original issue. I'll close this.
Sounds good! I'll check the new docs out.


Surface Debug Trace err

Describe your changes and provide context
Surfacing a previously suppressed error in StateAtTransaction used for debug trace endpoints.
Testing performed to validate your change
N/A

Codecov Report
Attention: Patch coverage is 25.00000% with 3 lines in your changes are missing coverage. Please review.

Project coverage is 61.33%. Comparing base (e8e4b3b) to head (a94fadb).
Report is 30 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1650      +/-   ##
==========================================
- Coverage   61.64%   61.33%   -0.31%
==========================================
  Files         365      367       +2
  Lines       26178    26575     +397
==========================================
+ Hits        16138    16301     +163
- Misses       8967     9183     +216
- Partials     1073     1091      +18

Files
Coverage Δ

evmrpc/simulate.go
66.79% <25.00%> (-1.12%)
:arrow_down:

... and 11 files with indirect coverage changes


Glowing liquid does not glow ☢

title

Mop buckets should take on the colour of their reagent but for reagents to give a glow they'll need
A) to support being lit / unlit so they're constantly visible regardless of light.
B) to support being a pointlight and having light behaviour. Then you can have radiation glows and fun stuff like spilling chemlight fluid everywhere.


Make logo tighter

Up to you if you think this looks better, I think it's more consistent with the original logo since the characters are less wide! Since the logo is 'pixel' the ends of characters should have a single 'pixel' instead of two if that makes sense.
Old

New

Woot! Even better than before. :)


Why didn't I use GPU during training?

hi，when I am training the model， but it is not using GPU。

Did you figure out why? The same is happening for me

The same for me.

And for me too.


Arrange the boosts indicators in rows of 3 / 4

Basically don't let this happen and make it display in a rectagle not a big line.

This will be added in tomorrow’s update.


Possibly incorrect conjugation when present tense form ends with "se"

Avtor: @shibe2
Article: pasti sę
Present tense: pase
3.sg.: pe sę
present_tense_stem returns "p"

The Google Sheets DB has the irregular form, so this definitely a bug in JS logic:

Fixed in #41


Make EventScrubber also scrub exception entries

Problem Statement
I'd like to use EventScrubber (added in https://github.com/getsentry/sentry-python/pull/1943) to scrub the events we send to Sentry. However, our own current scrubbing implementation also scrubs event["exception"] based on whether exc_info is in the hint supplied to the before_send hook.
Not scrubbing the exception is a blocker to adoption of EventScrubber for us and I think it would be nice to add this functionality.
Solution Brainstorm
/

@DanielNoord DanielNoord event["exception"] is an entire interface, which field in the exception do you want to scrub?
Note that the scrubber is for stripping sensitive data like PII/security credentials and not for filtering events you don't want to send.

thanks for the snippet!
So basically the only actual container of data you're stripping is frame["vars"] which should be handled by this block here.
https://github.com/getsentry/sentry-python/blob/c4d03846cb3f1b157cc35d20ef73c7671839796a/sentry_sdk/scrubber.py#L108-L113
iter_event_frames goes through frames/stacktraces in both the threads and exception interfaces.

ah sorry are you requesting hint based conditional scrubbing?

Just to confirm the snippet you provide is basically the same as:

yes, iter_event_frames will iterate through both of those fields. You're just using hint["exc_info"] to just check if there's an exception in there, so I think that is also no longer necessary with the scrubber. It should just work.

Thanks! I'll start our bump then. If we do find issues I'll open a new one. Thanks for the speedy responses!


#23, fix EventLoggingListener throws Direct self-reference leading to…

… cycle.
What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)
Please review http://spark.apache.org/contributing.html before opening a pull request.

相关 issue: https://github.com/Kyligence/KAP/issues/12905


xCluster: When using distinguished naming of cluster, second pass of DSC fails.

I want to create the AD Cluster object in a specific OU
Verbose logs showing the problem
PSComputerName       : SRV70031
RunspaceId           : 83a68bc5-290c-46d9-8521-4b55093d7bb9
ConfigurationName    : QSClusterDsc
DependsOn            : {[WindowsFeature]WSCS}
ModuleName           : xFailoverCluster
ModuleVersion        : 1.16.0
PsDscRunAsCredential :
ResourceId           : [xCluster]PrepareCluster
SourceInfo           : \\tsclient\E\IGEL\Source\Platform\DSC\~Config\QSClusterDSC.ps1::223::13::xCluster
DurationInSeconds    : 9.353
Error                : {
                           "Exception":  {
                                             "Message":  "PowerShell DSC resource MSFT_xCluster  failed to execute
                       Set-TargetResource functionality with error message: There was an error adding node
                       \u0027SRV70031\u0027 to the cluster ",
                                             "Data":  {

                                                      },
                                             "InnerException":  {
                                                                    "SerializedRemoteException":
                       "Microsoft.FailoverClusters.PowerShell.ClusterCmdletException: T**here was an error adding node
                       \u0027SRV70031\u0027 to the cluster ---\u003e**
                       Microsoft.FailoverClusters.PowerShell.ClusterCmdletException: T**he computer
                       \u0027SRV70031.rd01.local\u0027 is joined to a cluster**.\r\n   --- End of inner exception stack
                       trace ---",
                                                                    "SerializedRemoteInvocationInfo":
                       "System.Management.Automation.InvocationInfo",
                                                                    "ErrorRecord":  "There was an error adding node
                       \u0027SRV70031\u0027 to the cluster\n    The computer \u0027SRV70031.rd01.local\u0027 is joined
                       to a cluster.",
                                                                    "WasThrownFromThrowStatement":  false,
                                                                    "Message":  "There was an error adding node
                       \u0027SRV70031\u0027 to the cluster",
                                                                    "Data":
                       "System.Collections.ListDictionaryInternal",
                                                                    "InnerException":  null,
                                                                    "TargetSite":  "Void EndInvoke()",
                                                                    "StackTrace":  "   at
                       System.Management.Automation.Runspaces.AsyncResult.EndInvoke()\r\n   at System.Management.Automa
                       tion.PowerShell.CoreInvokeRemoteHelper[TInput,TOutput](PSDataCollection`1 input,
                       PSDataCollection`1 output, PSInvocationSettings settings)\r\n   at
                       System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection`1 input,
                       PSDataCollection`1 output, PSInvocationSettings settings)\r\n   at
                       System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings
                       settings)\r\n   at Microsoft.PowerShell.DesiredStateConfiguration.Internal.ResourceProviderAdapt
                       er.ExecuteCommand(PowerShell powerShell, ResourceModuleInfo resInfo, String operationCmd,
                       List`1 acceptedProperties, CimInstance nonResourcePropeties, CimInstance resourceConfiguration,
                       LCMDebugMode debugMode, PSInvocationSettings pSInvocationSettings, UInt32\u0026
                       resultStatusHandle, Collection`1\u0026 result, ErrorRecord\u0026 errorRecord, PSModuleInfo
                       localRunSpaceModuleInfo)",
                                                                    "HelpLink":  null,
                                                                    "Source":  "System.Management.Automation",
                                                                    "HResult":  -2146233087
                                                                },
                                             "TargetSite":  null,
                                             "StackTrace":  null,
                                             "HelpLink":  null,
                                             "Source":  null,
                                             "HResult":  -2146233079
                                         },
                           "TargetObject":  null,
                           "CategoryInfo":  {
                                                "Category":  7,
                                                "Activity":  "",
                                                "Reason":  "InvalidOperationException",
                                                "TargetName":  "",
                                                "TargetType":  ""
                                            },
                           "FullyQualifiedErrorId":  "ProviderOperationExecutionFailure",
                           "ErrorDetails":  null,
                           "InvocationInfo":  null,
                           "ScriptStackTrace":  null,
                           "PipelineIterationInfo":  [

                                                     ]
                       }
FinalState           :
InDesiredState       : False
InitialState         :
InstanceName         : PrepareCluster
RebootRequested      : False
ResourceName         : xCluster
StartDate            : 4/12/2021 11:58:00 AM
StateChanged         : False

Suggested solution to the issue
The DSC configuration that is used to reproduce the issue (as detailed as possible)
        if ($Node.Replica -eq 'Primary') {
            xCluster 'PrepareCluster' {
                PsDscRunAsCredential = $SetupCredential
                DomainAdministratorCredential = $SetupCredential
                Name = $Node.FailoverClusterName
                StaticIPAddress = $Node.FailoverClusterIPAddress
                IgnoreNetwork = $Node.FailoverClusterIgnoreNetwork
                DependsOn = @('[WindowsFeature]WSCS')
            }
         } else {
            $FailoverClusterName = ((($Node.FailoverClusterName -split ',')[0]) -split '=')[1]
            xCluster 'PrepareCluster' {
                PsDscRunAsCredential = $SetupCredential
                DomainAdministratorCredential = $SetupCredential
                Name = $FailoverClusterName
                StaticIPAddress = $Node.FailoverClusterIPAddress
                IgnoreNetwork = $Node.FailoverClusterIgnoreNetwork
                DependsOn = @('[xWaitForCluster]WaitForCluster')
            }
            xWaitForCluster 'WaitForCluster' {
                PsDscRunAsCredential = $SetupCredential
                Name = $FailoverClusterName
                RetryIntervalSec = 5
                RetryCount = 15
                DependsOn = @('[WindowsFeature]WSCS')
            }

--First Nodes MOF
instance of MSFT_xCluster as $MSFT_xCluster1ref
{
ResourceID = "[xCluster]PrepareCluster";
 PsDscRunAsCredential = $MSFT_Credential1ref;
 IgnoreNetwork = {
    "<IP_ADDRESS>/16"
};
 StaticIPAddress = "<IP_ADDRESS>";
 DomainAdministratorCredential = $MSFT_Credential2ref;
 SourceInfo = "\\\\tsclient\\E\\IGEL\\Source\\Platform\\DSC\\~Config\\QSClusterDSC.ps1::223::13::xCluster";
 Name = "CN=SRV70CLU,OU=Computers,OU=Admin,OU=Resources,DC=rd01,DC=local";
 ModuleName = "xFailoverCluster";
 ModuleVersion = "1.16.0";

DependsOn = {

    "[WindowsFeature]WSCS"};

 ConfigurationName = "QSClusterDsc";

};

--Second Nodes MOF
instance of MSFT_xCluster as $MSFT_xCluster1ref
{
ResourceID = "[xCluster]PrepareCluster";
 PsDscRunAsCredential = $MSFT_Credential1ref;
 IgnoreNetwork = {
    "<IP_ADDRESS>/16"
};
 StaticIPAddress = "<IP_ADDRESS>";
 DomainAdministratorCredential = $MSFT_Credential2ref;
 SourceInfo = "\\\\tsclient\\E\\IGEL\\Source\\Platform\\DSC\\~Config\\QSClusterDSC.ps1::233::13::xCluster";
 Name = "SRV70CLU";
 ModuleName = "xFailoverCluster";
 ModuleVersion = "1.16.0";

DependsOn = {

    "[xWaitForCluster]WaitForCluster"};

 ConfigurationName = "QSClusterDsc";

};

instance of MSFT_xWaitForCluster as $MSFT_xWaitForCluster1ref
{
ResourceID = "[xWaitForCluster]WaitForCluster";
 PsDscRunAsCredential = $MSFT_Credential3ref;
 RetryCount = 15;
 SourceInfo = "\\\\tsclient\\E\\IGEL\\Source\\Platform\\DSC\\~Config\\QSClusterDSC.ps1::241::13::xWaitForCluster";
 Name = "SRV70CLU";
 ModuleName = "xFailoverCluster";
 RetryIntervalSec = 5;
 ModuleVersion = "1.16.0";

DependsOn = {

    "[WindowsFeature]WSCS"};

 ConfigurationName = "QSClusterDsc";

};

The operating system the target node is running
OsName               : Microsoft Windows Server 2019 Datacenter
OsOperatingSystemSKU : DatacenterServerEdition
OsArchitecture       : 64-bit
WindowsVersion       : 1809
WindowsBuildLabEx    : 17763.1.amd64fre.rs5_release.180914-1434
OsLanguage           : en-US
OsMuiLanguages       : {en-US}
Version and build of PowerShell the target node is running
SVersion                      5.1.17763.1490
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17763.1490
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
Version of the DSC module that was used
1.16.0

In the first node you have:
 Name = "CN=SRV70CLU,OU=Computers,OU=Admin,OU=Resources,DC=rd01,DC=local";

In the second node you have:
Name = "SRV70CLU";

By "second pass" do you mean that the first node creates the CNO in the OU, but when the configuration runs Test-TargetResource it fails (when it enforces the configuration and checks current state against desired state)?

Yes, and that is on the first pass of cluster node one and two. On the first pass it all works. Ont the second pass the first node falls. The one with a distibgusihed  name

From: Johan Ljunggren @.>
Sent: Monday, April 12, 2021 5:58:25 PM
To: dsccommunity/xFailOverCluster @.>
Cc: Ilian Nilsson @.>; Author @.>
Subject: Re: [dsccommunity/xFailOverCluster] xCluster: When using distinguished naming of cluster, second pass of DSC fails. (#256)
By "second pass" do you mean that the first node creates the CNO in the OU, but when the configuration runs Test-TargetResource it fails (when it enforces the configuration and checks current state against desired state)?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/dsccommunity/xFailOverCluster/issues/256#issuecomment-817928443, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AID6F4DROTJ2EPCHMSQ4VH3TIMKCDANCNFSM42Y7CW5Q.

I have used pre-staged accounts so never seen this. Sounds like there is an issue when using the full distinguished name.

Happy to review a pull request that fixes this.

I’ll try powershell in DSC format is not my thing.

From: Johan Ljunggren @.>
Sent: Monday, April 12, 2021 9:08:48 PM
To: dsccommunity/xFailOverCluster @.>
Cc: Ilian Nilsson @.>; Author @.>
Subject: Re: [dsccommunity/xFailOverCluster] xCluster: When using distinguished naming of cluster, second pass of DSC fails. (#256)
Happy to review a pull request that fixes this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/dsccommunity/xFailOverCluster/issues/256#issuecomment-818062944, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AID6F4CF3OMUWUXVLVECU53TINAMBANCNFSM42Y7CW5Q.

Well I've made best, but when i try to push my branch i get this:
E:\IGEL\Source\xFailoverCluster [fix_to_use_distinguised_name]> git push --set-upstream origin fix_to_use_distinguised_name
info: please complete authentication in your browser...
remote: Permission to dsccommunity/xFailOverCluster.git denied to IlleNilsson.
fatal: unable to access 'https://github.com/dsccommunity/xFailOverCluster.git/': The requested URL returned error: 403
E:\IGEL\Source\xFailoverCluster [fix_to_use_distinguised_name]>
And yes i got a browser to autenticate med, and it said, Success :(

You need to fork the main repository. On the repository page there is a button “Fork” at top right. Once you forked you need to make a remote my  to the fork, in the local repository folder. Then you push to the remote. From there you make the pull request.
Read how to do it here https://dsccommunity.org/guidelines/getting-started/#forking-a-repository-on-github

Thats intendent, when you do create-cluster it is valid to use distinguished name, not when searching to add nodes

From: Johan Ljunggren @.>
Sent: Saturday, April 17, 2021 5:33:55 PM
To: dsccommunity/xFailOverCluster @.>
Cc: Ilian Nilsson @.>; Author @.>
Subject: Re: [dsccommunity/xFailOverCluster] xCluster: When using distinguished naming of cluster, second pass of DSC fails. (#256)
You need to fork the main repository. On the repository page there is a button “Fork” at top right. Once you forked you need to make a remote my to the fork, in the local repository folder. Then you push to the remote. From there you make the pull request.
Read how to do it here https://dsccommunity.org/guidelines/getting-started/#forking-a-repository-on-github
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/dsccommunity/xFailOverCluster/issues/256#issuecomment-821841344, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AID6F4ESMBTD4SUJ4GAUKVDTJGS6HANCNFSM42Y7CW5Q.

Here we go, a fork IlleNilsson/xFailOverCluster. There is at least one thing I'm not happy with. I added a function named Convert-DistinguishedNameToSimpleName. I could not find a common place to put it, so it is in all Resources, not optimal.

Great! Now you need to go to your fork an create a pull request. Got to https://github.com/IlleNilsson/xFailOverCluster/pulls and click on new pull request. Base repository should be dsccommunity/xFailOverCluster and base should be main. The head repository should be IlleNilsson/xFailOverCluster and compare should be the working branch where you pushed the changes.

I could not find a common place to put it, so it is in all Resources, not optimal.

We could add a new common module FailoverCluster.Common similar to here: https://github.com/dsccommunity/DnsServerDsc/tree/main/source/Modules/DnsServerDsc.Common
We also need to copy it during build by changing build.yaml:
https://github.com/dsccommunity/DnsServerDsc/blob/97f6ef720def5fc0d920c63607f3ed2f8e03f9fb/build.yaml#L8
The we just need to import the module in the resource code like line 2 and 5 here:
https://github.com/dsccommunity/DnsServerDsc/blob/97f6ef720def5fc0d920c63607f3ed2f8e03f9fb/source/DSCResources/DSC_DnsServerADZone/DSC_DnsServerADZone.psm1#L2-L5

You said "we could", does that mean me. I'm not up to speed on this. Can we do it togheter?

We could, as in the community could. That can be resolved in another PR, or I could see if I have time to add an empty module where we can move the code.

I would like to get it done, l’m changing assignment and I’m afraid the customer won’t resolve this issue without me. So whatever I can do, let me know.

From: Johan Ljunggren @.>
Sent: Thursday, April 22, 2021 7:25:21 PM
To: dsccommunity/xFailOverCluster @.>
Cc: Ilian Nilsson @.>; Author @.>
Subject: Re: [dsccommunity/xFailOverCluster] xCluster: When using distinguished naming of cluster, second pass of DSC fails. (#256)
We could, as in the community could. That can be resolved in another PR, or I could see if I have time to add an empty module where we can move the code.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/dsccommunity/xFailOverCluster/issues/256#issuecomment-825043823, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AID6F4BX5D2FZLGYSOHS3LLTKBLYDANCNFSM42Y7CW5Q.

Done this, getting...
Tests completed in 77.33s
Tests Passed: 289, Failed: 0, Skipped: 4, Pending: 0, Inconclusive: 0
Code coverage report:
Covered 99.38% of 649 analyzed Commands in 8 Files.
Missed commands:
File                                                       Class Function                              Line Command

Modules\FailoverCluster.Common\FailoverCluster.Common.psm1       Convert-DistinguishedNameToSimpleName   29 $returnV...
Modules\FailoverCluster.Common\FailoverCluster.Common.psm1       Convert-DistinguishedNameToSimpleName   29 (($Disti...
Modules\FailoverCluster.Common\FailoverCluster.Common.psm1       Convert-DistinguishedNameToSimpleName   29 ($Distin...
Modules\FailoverCluster.Common\FailoverCluster.Common.psm1       Convert-DistinguishedNameToSimpleName   29 $Disting...
Any hints for me to resolve this?
From: Johan Ljunggren @.>
Sent: Sunday, 18 April 2021 12:51
To: dsccommunity/xFailOverCluster @.>
Cc: Ilian Nilsson @.>; Author @.>
Subject: Re: [dsccommunity/xFailOverCluster] xCluster: When using distinguished naming of cluster, second pass of DSC fails. (#256)
Great! Now you need to go to your fork an create a pull request. Got to https://github.com/IlleNilsson/xFailOverCluster/pulls and click on new pull request. Base repository should be dsccommunity/xFailOverCluster and base should be main. The head repository should be IlleNilsson/xFailOverCluster and compare should be the working branch where you pushed the changes.
I could not find a common place to put it, so it is in all Resources, not optimal.
We could add a new common module FailoverCluster.Common similar to here: https://github.com/dsccommunity/DnsServerDsc/tree/main/source/Modules/DnsServerDsc.Common
We also need to copy it during build by changing build.yaml:
https://github.com/dsccommunity/DnsServerDsc/blob/97f6ef720def5fc0d920c63607f3ed2f8e03f9fb/build.yaml#L8
The we just need to import the module in the resource code like line 2 and 5 here:
https://github.com/dsccommunity/DnsServerDsc/blob/97f6ef720def5fc0d920c63607f3ed2f8e03f9fb/source/DSCResources/DSC_DnsServerADZone/DSC_DnsServerADZone.psm1#L2-L5
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/dsccommunity/xFailOverCluster/issues/256#issuecomment-821972104, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AID6F4D2SWOBBDH5VLWG2VTTJK2STANCNFSM42Y7CW5Q.


Update ZAP submodule

Problem
Update ZAP submodule. We need it for relative path in .zap files for #3882, #3610 and likely for the all-clusters-app

@vivien-apple while updating zap submodule is a good idea, it would make much more sense to track directly the master branch since ZAP is still under heavy development. This could be done by editing the zap_configure and zap_generate script so they checkout master and do a git pull at each run. Once ZAP is stable with a release version we could simply remove those lines and update the submodule when necessary.

@vivien-apple while updating zap submodule is a good idea, it would make much more sense to track directly the master branch since ZAP is still under heavy development. This could be done by editing the zap_configure and zap_generate script so they checkout master and do a git pull at each run. Once ZAP is stable with a release version we could simply remove those lines and update the submodule when necessary.

No.
We can track master, but we should do it by building automation to update the submodule.


packages drop by FIB lookup failed

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
packages drop by FIB lookup failed
this data is generate by cilium monitor -j > cil_j.log
{"cpu":"CPU 14:","type":"drop","mark":"0x2f75d213","reason":"FIB lookup failed","source":2771,"bytes":66,"srcLabel":0,"dstLabel":0,"dstID":0,"summary":{"ethernet":"Ethern
et\t{Contents=[..14..] Payload=[..54..] SrcMAC=b4:0c:25:e2:80:16 DstMAC=00:62:0b:91:af:10 EthernetType=IPv4 Length=0}","ipv4":"IPv4\t{Contents=[..20..] Payload=[..32..] V
ersion=4 IHL=5 TOS=0 Length=52 Id=4700 Flags=DF FragOffset=0 TTL=122 Protocol=TCP Checksum=63297 SrcIP=<IP_ADDRESS> DstIP=<IP_ADDRESS> Options=[] Padding=[]}","tcp":"TCP\t{Conte
nts=[..32..] Payload=[] SrcPort=56284 DstPort=3306(mysql) Seq=2889614829 Ack=0 DataOffset=8 FIN=false SYN=true RST=false PSH=false ACK=false URG=false ECE=false CWR=false
NS=false Window=8192 Checksum=48644 Urgent=0 Options=[..6..] Padding=[]}","l2":{"src":"b4:0c:25:e2:80:16","dst":"00:62:0b:91:af:10"},"l3":{"src":"<IP_ADDRESS>","dst":"245.0.2
.38"},"l4":{"src":"56284","dst":"3306"}}}
{"cpu":"CPU 31:","type":"debug","message":"Encapsulating to node<PHONE_NUMBER> (0xc0a8ff25) from seclabel 59087"}
{"cpu":"CPU 35:","type":"debug","message":"Successfully mapped addr=<IP_ADDRESS> to identity=7"}
{"cpu":"CPU 41:","type":"debug","message":"Successfully mapped addr=<IP_ADDRESS> to identity=7"}
{"cpu":"CPU 14:","type":"debug","message":"Successfully mapped addr=<IP_ADDRESS> to identity=2"}
{"cpu":"CPU 14:","type":"debug","message":"Conntrack lookup 1/2: src=<IP_ADDRESS>:56284 dst=<IP_ADDRESS>:3306"}
{"cpu":"CPU 14:","type":"debug","message":"Conntrack lookup 2/2: nexthdr=6 flags=4"}
{"cpu":"CPU 14:","type":"debug","message":"CT verdict: New, revnat=0"}
{"cpu":"CPU 14:","type":"debug","message":"Conntrack create: proxy-port=0 revnat=124 src-identity=0 lb=<IP_ADDRESS>"}
{"cpu":"CPU 14:","type":"debug","message":"Conntrack lookup 1/2: src=<IP_ADDRESS>:56284 dst=<IP_ADDRESS>:3306"}
{"cpu":"CPU 14:","type":"debug","message":"Conntrack lookup 2/2: nexthdr=6 flags=1"}
{"cpu":"CPU 14:","type":"debug","message":"CT verdict: New, revnat=0"}
{"cpu":"CPU 14:","type":"debug","message":"Conntrack create: proxy-port=0 revnat=124 src-identity=2 lb=<IP_ADDRESS>"}
{"cpu":"CPU 14:","type":"drop","mark":"0x2f75d213","reason":"FIB lookup failed","source":2771,"bytes":66,"srcLabel":0,"dstLabel":0,"dstID":0,"summary":{"ethernet":"Ethern
et\t{Contents=[..14..] Payload=[..54..] SrcMAC=b4:0c:25:e2:80:16 DstMAC=00:62:0b:91:af:10 EthernetType=IPv4 Length=0}","ipv4":"IPv4\t{Contents=[..20..] Payload=[..32..] V
ersion=4 IHL=5 TOS=0 Length=52 Id=4700 Flags=DF FragOffset=0 TTL=122 Protocol=TCP Checksum=63297 SrcIP=<IP_ADDRESS> DstIP=<IP_ADDRESS> Options=[] Padding=[]}","tcp":"TCP\t{Conte
nts=[..32..] Payload=[] SrcPort=56284 DstPort=3306(mysql) Seq=2889614829 Ack=0 DataOffset=8 FIN=false SYN=true RST=false PSH=false ACK=false URG=false ECE=false CWR=false
 NS=false Window=8192 Checksum=48644 Urgent=0 Options=[..6..] Padding=[]}","l2":{"src":"b4:0c:25:e2:80:16","dst":"00:62:0b:91:af:10"},"l3":{"src":"<IP_ADDRESS>","dst":"245.0.2
.38"},"l4":{"src":"56284","dst":"3306"}}}
{"cpu":"CPU 04:","type":"debug","message":"Successfully mapped addr=<IP_ADDRESS> to identity=2"}
{"cpu":"CPU 22:","type":"debug","message":"Successfully mapped addr=<IP_ADDRESS> to identity=2"}
{"cpu":"CPU 52:","type":"debug","message":"Conntrack lookup 1/2: src=<IP_ADDRESS>:50186 dst=<IP_ADDRESS>:6443"}
{"cpu":"CPU 52:","type":"debug","message":"Conntrack lookup 2/2: nexthdr=6 flags=1"}
{"cpu":"CPU 52:","type":"debug","message":"CT entry found lifetime=3566377, revnat=0"}
{"cpu":"CPU 52:","type":"debug","message":"CT verdict: Established, revnat=0"}
{"cpu":"CPU 52:","type":"debug","message":"Successfully mapped addr=<IP_ADDRESS> to identity=1"}
{"cpu":"CPU 52:","type":"capture","mark":"0xddc507eb","message":"Delivery to ifindex 0","prefix":"-\u003e 0","source":1149,"bytes":66,"summary":"<IP_ADDRESS>:50186 -\u003e
<IP_ADDRESS>:6443 tcp ACK"}

Cilium Version
1.12.7
Kernel Version
Linux wcn-gdppd-qfusion1 6.2.11-1.el8.elrepo.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Apr 13 08:18:02 EDT 2023 x86_64 x86_64 x86_64 GNU/Linux
Kubernetes Version
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.17", GitCommit:"68b4e26caf6ede7af577db4af62fb405b4dd47e6", GitTreeState:"clean", BuildDate:"2021-03-18T01:02:41Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.17", GitCommit:"68b4e26caf6ede7af577db4af62fb405b4dd47e6", GitTreeState:"clean", BuildDate:"2021-03-18T00:54:02Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}
Sysdump
too big to upload
Relevant log output
No response
Anything else?
No response
Code of Conduct

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

:wave: are you looking for help in diagnosing why the drop occurred? If so, describing your test scenario, the cilium config and/or providing a sysdump (you could upload somewhere else and link here) would be a great start.

Yes, at present, when we frequently delete pods with the same name, there will be a probability of such a drop. I don’t know why
Here is the cilium sysdump file
url: https://pan.baidu.com/s/1mO3mGKgl83_dTqT5nsoR4Q    Extraction code: abcd

/reopen

From #28218:

This bug appeared once before, but since it never recurred, sysdump was not performed, causing the problem to be shelved. It happened again recently and a sysdump was executed. Since it was time to recover at that time, after completing the sysdump, restart the pod to resume business first. The specific pod is: pod-name: qfusion-admin/mysql-6ccf1fd801-0. This problem occurs occasionally, but it occurs from time to time.

cilium sysdump file:
https://drive.google.com/file/d/17aVXdvSpKmMTMQHnEdoBQruHciXU9HeO/view?usp=drive_link


Integration with bug trackers

an the moment you can add to issue/tms from test result https://docs.qameta.io/allure/#_links


Tutorials with gif backgrounds can't be opened on iPad

Describe the bug
The gif for lots of tutorials obscures the buttons to begin the tutorial on iPad
To Reproduce
Steps to reproduce the behavior:

Go to the homepage and click on Lemon Leak
The gif of the game, which should be greyed over, appears over the text description of the game, and it also masks the buttons to select to begin the tutorial

Screenshots

Smartphone (please complete the following information):

Device: iPad Pro
OS: iPadOS 13.6
Browser Safari and Chrome

Additional context
I've seen it recover from this once, but it hasn't again yet.

@livcheerful Are you able to to reproduce this / is this just a very rare thing? I tried for a bit on browserstack and wasn't able to get it back to get it to happen :(

@livcheerful Are you able to to reproduce this / is this just a very rare thing? I tried for a bit on browserstack and wasn't able to get it back to get it to happen :(

haha lemme try it now it's been a while

haha lemme try it now it's been a while

I clicked a lot in both browsers and couldn't repro! I think when I filed this it was super easy to repro, so I think we're good :D

I clicked a lot in both browsers and couldn't repro! I think when I filed this it was super easy to repro, so I think we're good :D

Hmm sounds good! Closing then~

Hmm sounds good! Closing then~

@abchatra this is the one you ran into, any details on device / how it occurred would be helpful

@abchatra this is the one you ran into, any details on device / how it occurred would be helpful

(I managed to repro with
 on browserstack so looking at this now)

(I managed to repro with
 on browserstack so looking at this now)


New version: OSGeo.GeoServer version 2.23.0

Pull request has been created with Komac v1.6.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Standard error:  Exception during executable launch operation System.AggregateException: One or more errors occurred. (The specified executable is not a valid application for this OS platform.)  --->
System.ComponentModel.Win32Exception (216): The specified executable is not a valid application for this OS platform.
--- End of stack trace from previous location where exception was thrown ---
--- End of inner exception stack trace ---    at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)

This server application seems to be non-interactive:
JSL Java Service Launcher by Michael Roeschter<EMAIL_ADDRESS>Version 0.99w January 2020
Command line options:
C:\Program Files\GeoServer\wrapper\GeoServer.exe -install [ini] [...]    to install the service
C:\Program Files\GeoServer\wrapper\GeoServer.exe -configure [ini] [...]  to reconfigure an installed service with new dependencies
C:\Program Files\GeoServer\wrapper\GeoServer.exe -remove [ini] [...]     to remove the service
C:\Program Files\GeoServer\wrapper\GeoServer.exe -debug [ini] [...]      to run as a standalone console app for debugging
C:\Program Files\GeoServer\wrapper\GeoServer.exe -run [ini] [...]        to run as a standalone console app
C:\Program Files\GeoServer\wrapper\GeoServer.exe -runapp [ini] [...]     to run as a standalone console app with no console output
C:\Program Files\GeoServer\wrapper\GeoServer.exe -ini ini                to use the specified init file for running as a service (this option is not useful on command line; only use it if you configure the service option in the registry)
Optional parameters: [...] -console hide | attach | new    'hide' will not show any output on console; 'attach' will show output in current console; 'new' will open a new console window
...


Issues found by WordPress Theme Check plugin

Hi Jordi,
Monolog is used in MerlinWP and when included in a WordPress theme and put through the Theme Check plugin, I get the following errors relating to Monolog:
WARNING: Found exec in the file merlin/vendor/monolog/monolog/tests/Monolog/Processor/MercurialProcessorTest.php. PHP system calls are often disabled by server admins and should not be in themes.
Line24: exec('where hg 2>NUL', $output, $result);
Line26: exec('which hg 2>/dev/null >/dev/null', $output, $result);
WARNING: Found base64_encode in the file merlin/vendor/monolog/monolog/tests/Monolog/Handler/ChromePHPHandlerTest.php. base64_encode() is not allowed.
Line41: 'X-ChromeLogger-Data' => base64_encode(utf8_encode(json_encode(array(
Line75: 'X-ChromeLogger-Data' => base64_encode(utf8_encode(json_encode(array(
Line118: 'X-ChromeLogger-Data' => base64_encode(utf8_encode(json_encode(array(
WARNING: Found base64_encode in the file merlin/vendor/monolog/monolog/src/Monolog/Handler/ChromePHPHandler.php. base64_encode() is not allowed.
Line138: $data = base64_encode(utf8_encode($json));
Line153: $data = base64_encode(utf8_encode($json));
WARNING: Found ->exec in the file merlin/vendor/monolog/monolog/src/Monolog/Handler/RedisHandler.php. PHP system calls are often disabled by server admins and should not be in themes.
Line79: ->exec();
WARNING: pfsockopen was found in the file merlin/vendor/monolog/monolog/src/Monolog/Handler/SocketHandler.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line17: * Stores to any socket - uses fsockopen() or pfsockopen().
Line196: protected function pfsockopen()
Line198: return @pfsockopen($this->connectionString, -1, $this->errno, $this->errstr, $this-
Line276: $resource = $this->pfsockopen();
WARNING: fwrite was found in the file merlin/vendor/monolog/monolog/tests/Monolog/Formatter/NormalizerFormatterTest.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line353: fwrite($resource, 'test_resource');
WARNING: fwrite was found in the file merlin/vendor/monolog/monolog/src/Monolog/Handler/StreamHandler.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line130: fwrite($stream, (string) $record['formatted']);
WARNING: fwrite was found in the file merlin/vendor/monolog/monolog/src/Monolog/Handler/SocketHandler.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line225: protected function fwrite($data)
Line227: return @fwrite($this->resource, $data);
Line300: $chunk = $this->fwrite($data);
Line302: $chunk = $this->fwrite(substr($data, $sent));
WARNING: fwrite was found in the file merlin/vendor/monolog/monolog/src/Monolog/Handler/DeduplicationHandler.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line156: fwrite($handle, $log);
WARNING: fsockopen was found in the file merlin/vendor/monolog/monolog/src/Monolog/Handler/SocketHandler.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line17: * Stores to any socket - uses fsockopen() or pfsockopen().
Line20: * @see http://php.net/manual/en/function.fsockopen.php
Line98: * @see http://php.net/manual/en/function.fsockopen.php
Line183: * UDP might appear to be connected but might fail when writing. See http://php.net/fsockopen for details.
Line196: protected function pfsockopen()
Line198: return @pfsockopen($this->connectionString, -1, $this->errno, $this->errstr, $this->
Line204: protected function fsockopen()
Line206: return @fsockopen($this->connectionString, -1, $this->errno, $this->errstr, $this->
Line276: $resource = $this->pfsockopen();
Line278: $resource = $this->fsockopen();
WARNING: fread was found in the file merlin/vendor/monolog/monolog/tests/Monolog/Handler/StreamHandlerTest.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line32: $this->assertEquals('testtest2test3', fread($handle, 100));
WARNING: fread was found in the file merlin/vendor/monolog/monolog/tests/Monolog/Handler/SocketHandlerTest.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line203: $this->assertEquals('test1test2test3', fread($this->res, 1024));
WARNING: fread was found in the file merlin/vendor/monolog/monolog/tests/Monolog/Handler/SlackHandlerTest.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line47: $content = fread($this->res, 1024);
Line57: $content = fread($this->res, 1024);
Line70: $content = fread($this->res, 1024);
Line76: $content2 = fread($this->res, 1024);
Line87: $content = fread($this->res, 1024);
Line100: $content = fread($this->res, 1024);
Line110: $content = fread($this->res, 1024);
WARNING: fread was found in the file merlin/vendor/monolog/monolog/tests/Monolog/Handler/PushoverHandlerTest.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line34: $content = fread($this->res, 1024);
Line54: $content = fread($this->res, 1024);
Line65: $content = fread($this->res, 1024);
Line77: $content = fread($this->res, 1024);
Line89: $content = fread($this->res, 1024);
Line99: $content = fread($this->res, 1024);
Line109: $content = fread($this->res, 1024);
WARNING: fread was found in the file merlin/vendor/monolog/monolog/tests/Monolog/Handler/LogEntriesHandlerTest.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line38: $content = fread($this->res, 1024);
Line54: $content = fread($this->res, 1024);
WARNING: fread was found in the file merlin/vendor/monolog/monolog/tests/Monolog/Handler/HipChatHandlerTest.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line32: $content = fread($this->res, 1024);
Line44: $content = fread($this->res, 1024);
Line56: $content = fread($this->res, 1024);
Line68: $content = fread($this->res, 1024);
Line80: $content = fread($this->res, 1024);
Line100: $content = fread($this->res, 1024);
Line136: $content = fread($this->res, 1024);
Line148: $content = fread($this->res, 1024);
Line158: $content = fread($this->res, 12000);
Line171: $content = fread($this->res, 1024);
Line200: $content = fread($this->res, 1024);
WARNING: fread was found in the file merlin/vendor/monolog/monolog/tests/Monolog/Handler/FlowdockHandlerTest.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line46: $content = fread($this->res, 1024);
WARNING: fread was found in the file merlin/vendor/monolog/monolog/src/Monolog/Handler/SlackHandler.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line160: @fread($res, 2048);
WARNING: fopen was found in the file merlin/vendor/monolog/monolog/tests/Monolog/Handler/StreamHandlerTest.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line25: $handle = fopen('php://memory', 'a+');
Line40: $handle = fopen('php://memory', 'a+');
WARNING: fopen was found in the file merlin/vendor/monolog/monolog/tests/Monolog/Handler/SocketHandlerTest.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line278: $this->res = fopen('php://memory', 'a');
WARNING: fopen was found in the file merlin/vendor/monolog/monolog/tests/Monolog/Handler/SlackHandlerTest.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line132: $this->res = fopen('php://memory', 'a');
WARNING: fopen was found in the file merlin/vendor/monolog/monolog/tests/Monolog/Handler/PushoverHandlerTest.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line118: $this->res = fopen('php://memory', 'a');
WARNING: fopen was found in the file merlin/vendor/monolog/monolog/tests/Monolog/Handler/LogEntriesHandlerTest.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line63: $this->res = fopen('php://memory', 'a');
WARNING: fopen was found in the file merlin/vendor/monolog/monolog/tests/Monolog/Handler/HipChatHandlerTest.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line242: $this->res = fopen('php://memory', 'a');
WARNING: fopen was found in the file merlin/vendor/monolog/monolog/tests/Monolog/Handler/FlowdockHandlerTest.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line65: $this->res = fopen('php://memory', 'a');
WARNING: fopen was found in the file merlin/vendor/monolog/monolog/tests/Monolog/Formatter/NormalizerFormatterTest.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line34: 'extra' => array('foo' => new TestFooNorm, 'bar' => new TestBarNorm, 'baz' => array(), 'res' => fopen('php://memory', 'rb')),
Line199: $resource = fopen(FILE, 'r');
Line352: $resource = fopen('php://memory', 'rw+');
WARNING: fopen was found in the file merlin/vendor/monolog/monolog/tests/Monolog/Formatter/LineFormatterTest.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line116: 'extra' => array('foo' => new TestFoo, 'bar' => new TestBar, 'baz' => array(), 'res' => fopen('php://memory', 'rb')),
WARNING: fopen was found in the file merlin/vendor/monolog/monolog/src/Monolog/Handler/StreamHandler.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line100: $this->stream = fopen($this->url, 'a');
Line135: $this->errorMessage = preg_replace('{^(fopen|mkdir)(.*?): }', '', $msg);
WARNING: fopen was found in the file merlin/vendor/monolog/monolog/src/Monolog/Handler/DeduplicationHandler.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line140: $handle = fopen($this->deduplicationStore, 'rw+');
WARNING: file_put_contents was found in the file merlin/vendor/monolog/monolog/tests/Monolog/Handler/RotatingFileHandlerTest.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line197: file_put_contents($log, 'foo');
WARNING: file_put_contents was found in the file merlin/vendor/monolog/monolog/src/Monolog/Handler/DeduplicationHandler.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line167: file_put_contents($this->deduplicationStore, $record['datetime']->getTimest
WARNING: file_get_contents was found in the file merlin/vendor/monolog/monolog/tests/Monolog/Handler/RotatingFileHandlerTest.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line73: $this->assertEquals('test', file_get_contents($log));
Line104: $this->assertEquals('test', file_get_contents($log));
Line201: $this->assertEquals('footest', file_get_contents($log));
WARNING: file_get_contents was found in the file merlin/vendor/monolog/monolog/tests/Monolog/Handler/DeduplicationHandlerTest.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line133: file_get_contents(sys_get_temp_dir() . '/monolog_dedup.log')
Line154: file_get_contents(sys_get_temp_dir() . '/monolog_dedup.log')
WARNING: file_get_contents was found in the file merlin/vendor/monolog/monolog/src/Monolog/Handler/CouchDBHandler.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line60: if (false === @file_get_contents($url, null, $context)) {
WARNING: fclose was found in the file merlin/vendor/monolog/monolog/tests/Monolog/Handler/SocketHandlerTest.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line181: fclose($res);
WARNING: fclose was found in the file merlin/vendor/monolog/monolog/src/Monolog/Handler/StreamHandler.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line63: fclose($this->stream);
WARNING: fclose was found in the file merlin/vendor/monolog/monolog/src/Monolog/Handler/SocketHandler.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line78: fclose($this->resource);
WARNING: fclose was found in the file merlin/vendor/monolog/monolog/src/Monolog/Handler/DeduplicationHandler.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line160: fclose($handle);
WARNING: curl_init was found in the file merlin/vendor/monolog/monolog/src/Monolog/Handler/SlackbotHandler.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line72: $ch = curl_init();
WARNING: curl_init was found in the file merlin/vendor/monolog/monolog/src/Monolog/Handler/SlackWebhookHandler.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line83: $ch = curl_init();
WARNING: curl_init was found in the file merlin/vendor/monolog/monolog/src/Monolog/Handler/MandrillHandler.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line55: $ch = curl_init();
WARNING: curl_init was found in the file merlin/vendor/monolog/monolog/src/Monolog/Handler/LogglyHandler.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line87: $ch = curl_init();
WARNING: curl_init was found in the file merlin/vendor/monolog/monolog/src/Monolog/Handler/IFTTTHandler.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line58: $ch = curl_init();
WARNING: curl_init was found in the file merlin/vendor/monolog/monolog/src/Monolog/Handler/CubeHandler.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line91: $this->httpConnection = curl_init('http://'.$this->host.':'.$this->port.'/1.0/event/put');
WARNING: curl_exec was found in the file merlin/vendor/monolog/monolog/src/Monolog/Handler/Curl/Util.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line35: if (curl_exec($ch) === false) {
I realize this is not specifically for Wordpress, but any ideas how to fix these errors?
Thanks!

I have no idea what system/static analysis these errors come from, but I am 100% sure we can not fix this in Monolog. There is no way we are going to use WP_Filesystem instead of fread for example.
I am not familiar enough with WP to help you here sorry. Maybe best to report this to MerlinWP if that's what's shipping Monolog in your WP setup?


[PROBLEM] Unable to Find .DLL file : Microsoft Visual Studio 2019

"To verify that everything works so far, compile the dynamic link library. To compile, choose Build > Build Solution on the menu bar. The DLL and related compiler output are placed in a folder called Debug directly below the solution folder. If you create a Release build, the output is placed in a folder called Release. The output should look something like this:"
The problem occurs after this step.
PROBLEM
After building the solution in Debug and Release, I am unable to find a .DLL file.
SOLUTION
Unknown
Reference
https://docs.microsoft.com/en-us/cpp/build/walkthrough-creating-and-using-a-dynamic-link-library-cpp?view=msvc-160

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

ID: 08c574a2-cef0-ab13-7375-55851f966ef6
Version Independent ID: fe3421c7-e9f4-4986-589f-fadaedce583e
Content: Walkthrough: Create and use your own Dynamic Link Library (C++)
Content Source: docs/build/walkthrough-creating-and-using-a-dynamic-link-library-cpp.md
Product: visual-cpp
Technology: cpp-tools
GitHub Login: @corob-msft
Microsoft Alias: corob

@yeokaiwei
I'm sorry you're having a difficult time with the walkthrough. However, I know that most people complete it successfully, so I don't think there's a problem in the article. I don't have enough information to tell you why you're not succeeding, and this issues board isn't meant for product support. I think you'd get better help by asking about this issue on the Microsoft Docs Q&A [C++ board)(https://docs.microsoft.com/en-us/answers/topics/c%2B%2B.html). Good luck!


Allow pasting phosphorus links into generator

If we just extracted the first number ([0-9]+), that might work

Submitted PR to website's repo:
https://github.com/scratchblocks/scratchblocks.github.io/pull/3

Finished. Thanks @PullJosh!


update list star to point

What type of this PR
Add one of the following kinds:
/kind bug
update list star to point
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Specified Reivewers:
/assign @sfwn

/approve


Missing graphics in meta-article

Following README instructions I re-generated the meta article on typhon.
I'm not sure if some of the graphics need to be pulled down via git-annex or if we just have a rendering error

Full article attached
article-1.pdf

This means that the diffs have not been generated. Are you sure you downloaded the article pdf data? Please post the output of:
 ls outputs/*/*pdf -lah

Looks like make container-article always does a clean, so that isn't the problem. (Btw, make article-clean only works with latex installed, so we might need to check that the container is doing this successfully?)
$ ls outputs/*/*pdf -lah
lrwxrwxrwx 1 asmacdo asmacdo 136 Sep 21 16:22 outputs/original/article.pdf -> ../../.git/annex/objects/f9/Pv/MD5E-s21852357--cda3904485734ab5c089894db1659fa0.pdf/MD5E-s21852357--cda3904485734ab5c089894db1659fa0.pdf
lrwxrwxrwx 1 asmacdo asmacdo 136 Sep 21 16:22 outputs/podman_20230906053037/article.pdf -> ../../.git/annex/objects/qW/zV/MD5E-s21529647--17365d13a65885d2fce3d65d1c96c9f7.pdf/MD5E-s21529647--17365d13a65885d2fce3d65d1c96c9f7.pdf
lrwxrwxrwx 1 asmacdo asmacdo 136 Sep 21 16:22 outputs/podman_20230908162849/article.pdf -> ../../.git/annex/objects/80/v6/MD5E-s21545132--cc38b0844b952a39cd8d4cbf96605105.pdf/MD5E-s21545132--cc38b0844b952a39cd8d4cbf96605105.pdf
lrwxrwxrwx 1 asmacdo asmacdo 136 Sep 21 16:22 outputs/podman_20230920004219/article.pdf -> ../../.git/annex/objects/PJ/0J/MD5E-s21532977--fd1bd9e0b630500be88a52f3880f7a96.pdf/MD5E-s21532977--fd1bd9e0b630500be88a52f3880f7a96.pdf
lrwxrwxrwx 1 asmacdo asmacdo 136 Sep 21 16:22 outputs/podman_20230920004416/article.pdf -> ../../.git/annex/objects/gx/Pj/MD5E-s21514941--990e16b8bb32fb21c65c71a73646301d.pdf/MD5E-s21514941--990e16b8bb32fb21c65c71a73646301d.pdf
-rw-r--r-- 1 asmacdo asmacdo 21M Sep 23 02:44 outputs/podman_20230922123546/article.pdf
lrwxrwxrwx 1 asmacdo asmacdo 136 Sep 21 16:22 outputs/singularity_20230904214036/article.pdf -> ../../.git/annex/objects/k1/6x/MD5E-s21487275--5ab7da033717219cf2b87dde21317777.pdf/MD5E-s21487275--5ab7da033717219cf2b87dde21317777.pdf
lrwxrwxrwx 1 asmacdo asmacdo 136 Sep 21 16:22 outputs/singularity_20230905040926/article.pdf -> ../../.git/annex/objects/16/fV/MD5E-s21487288--ad7b66af092f14b60d45b31ba5e09135.pdf/MD5E-s21487288--ad7b66af092f14b60d45b31ba5e09135.pdf
lrwxrwxrwx 1 asmacdo asmacdo 136 Sep 21 16:22 outputs/singularity_20230905204435/article.pdf -> ../../.git/annex/objects/wz/g9/MD5E-s21487302--9f76897f47716f6adda8c778917b920d.pdf/MD5E-s21487302--9f76897f47716f6adda8c778917b920d.pdf
lrwxrwxrwx 1 asmacdo asmacdo 136 Sep 21 16:22 outputs/singularity_20230906012936/article.pdf -> ../../.git/annex/objects/8v/q0/MD5E-s21551881--c92d2d5f2941e0a5a4eb25fca28a92ec.pdf/MD5E-s21551881--c92d2d5f2941e0a5a4eb25fca28a92ec.pdf
lrwxrwxrwx 1 asmacdo asmacdo 136 Sep 21 16:22 outputs/singularity_20230908122618/article.pdf -> ../../.git/annex/objects/K6/vv/MD5E-s21370913--dd4358584c78e366bc7940ed7c0965a8.pdf/MD5E-s21370913--dd4358584c78e366bc7940ed7c0965a8.pdf

I'm not in a clean git state though. After executing the analysis, commit steps aren't included in the readme. Is it safe to just commit these partial results so I can rebase onto your recent changes?
TODO: We should include commit points into the readme.
or
**TODO (asmacdo preference): We should change the make targets to datalad run
It does look like this is just an environment problem, since CI is building the pdf with images successfully.

Use ls -lL to see if you actually feed the data

$ ls -lLah outputs/*/*.pdf
-r--r--r-- 1 asmacdo asmacdo 21M Sep 25 10:36 outputs/original/article.pdf
-r--r--r-- 1 asmacdo asmacdo 21M Sep 25 10:33 outputs/podman_20230906053037/article.pdf
-r--r--r-- 1 asmacdo asmacdo 21M Sep 25 10:31 outputs/podman_20230908162849/article.pdf
-r--r--r-- 1 asmacdo asmacdo 21M Sep 25 10:35 outputs/podman_20230920004219/article.pdf
-r--r--r-- 1 asmacdo asmacdo 21M Sep 25 10:33 outputs/podman_20230920004416/article.pdf
-rw-r--r-- 1 asmacdo asmacdo 21M Sep 23 02:44 outputs/podman_20230922123546/article.pdf
-r--r--r-- 1 asmacdo asmacdo 21M Sep 25 10:32 outputs/singularity_20230904214036/article.pdf
-r--r--r-- 1 asmacdo asmacdo 21M Sep 25 10:37 outputs/singularity_20230905040926/article.pdf
-r--r--r-- 1 asmacdo asmacdo 21M Sep 25 10:32 outputs/singularity_20230905204435/article.pdf
-r--r--r-- 1 asmacdo asmacdo 21M Sep 25 10:34 outputs/singularity_20230906012936/article.pdf
-r--r--r-- 1 asmacdo asmacdo 21M Sep 25 10:35 outputs/singularity_20230908122618/article.pdf
asmacdo@typhon:~/tmp/opfvta-2023-9-21/opfvta-replication-2023$

After coworking session debugging it appears:

The data is there
Figures get generated with the correct aspect ration (thank to it being set explicitly in ghostscipr)
However, figures are blank
Though, the actual PDF diffs from which the figures are sliced by ghostscipt, are not blank

I conclude that this is probably some sort of ghostscirpt issue. The artifact on github CI is also correct (i.e. it shows figure contents), so probably we're trying to find something which is present on both github CI and on my machine, but not on @asmacdo 's account on typhon. This is very strange but we need to figure it out. @yarikoptic can you try it locally as well?

It could be that ghostscript has trouble operating without a display.

I think I have it, so we dynamically diff the latest 4 reexecutions, but for the figures an older one was hardcoded, which is why, in view of @asmacdo 's new reexecutions, the older pdf-diff which we were attempting to slice with ghostscript was no longer generated.


SCVMM retirement - power status bug

Current logic:
We check the power status of a VM and if it is running we power it off before deleting it.
Problem:
In SCVMM the power status of a VM in ManageIQ is not always accurate. Without event support we remain uninformed of power status changes until the next EMS refresh takes place which could be up to 15 minutes later.
Given the current logic, if a VM is OFF in ManageIQ but ON in SCVMM we will not power it off before deleting it, causing an exception to be thrown in SCVMM when an attempt is made to delete a running VM.
Fix:
Do not check the power status before deleting a VM, delete regardless of the power status. This requires the -Force parameter, without it an exception is thrown if we try to power off an already stopped VM.
https://bugzilla.redhat.com/show_bug.cgi?id=1299069

@gmcculloug  - I tested your suggestion to call:
Remove-SCVirtualMachine -VM $vm -Force
without powering off the VM first. This deleted the VM in SCVMM but not on HyperV. See the parameter description here: https://technet.microsoft.com/en-us/library/hh801721.aspx

@blomquisg @Fryguy @gmcculloug - over to you.

Looks good to me.  @blomquisg Please review/merge.


some interactive scenarios and blogs added

updated logo and exam brief
Added interactive labs by Sysdig and Promlabs
Some other helpful blogs

Thank you @kranurag7 much appreciated.

LGTM!


fix(plugins): change flexbox widths for IE11

Fix flexbox widths on Plugins page for IE11 users.

Before

After


Use car distance units & remove solar type from model

Fixes #284
Changes

Checking the vehicles gui_distance_units to determine whether to display miles vs kilometers instead of the user's Unit System setting in Home Assistant.
Remove solar_type from model. The Tesla API recently changed where solar_type is no longer included in the PRODUCT_LIST endpoint.

Ugh, just saw this with the nonstandard commits. I'll revert and fix.

solar_type is still present, but it is not at the top level, but under components. See my comment in #354 of teslajsonpy.
Hence shouldn't the change be the following?
-        model = f"{self._energysite.resource_type.title()} {self._energysite.solar_type.replace('_', ' ')}"
+        model = f"{self._energysite.resource_type.title()} {self._energysite.components.solar_type.replace('_', ' ')}""

I realise this has already been merged but I have never done a PR and don't know if I have the perms to start one.


No @timestamp on raw index

I'm trying to index some raw objects but no matter one, the @timestamp is never set:
Client.Raw.IndexAsync(myIndex, "fluentd", data)
I also tried this way without success:
http://stackoverflow.com/questions/26744742/index-a-dynamic-object-using-nest
Note that the index is created by fluentd which inserts most of the records and all of them have @timestamp.
Any idea?

@btecu can you share your mapping here?  You need to enable timestamp as it's disabled by default.  See the docs: http://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-timestamp-field.html

{
  "logstash-2015.04.01": {
  "aliases": {},
  "mappings": {
    "fluentd": {
      "properties": {
        ...,
        "@timestamp": {
          "type": "date",
          "format": "dateOptionalTime"
        },
        ...
      }
   }
}

Hey @btecu sorry I misread the issue initially and thought you were referring to the _timestamp field, not @timestamp.
IIRC, I think I remember running into a similar issue like this in the past and the problem was that @ is a reserved C# token.  Maybe that's the issue here as well?
Any chance you could post the actual request that's being sent (i.e. the contents of ConnectionStatus.Request)?

That is correct, @ is reserved for naming variables with keywords. However, I'm not currently setting @timestamp... I just expect Elasticsearch to set it for me. Should I be setting it, somehow?

I think maybe you're confusing the logstash @timestamp field and _timestamp in Elasticsearch?
You can enable _timestamp in which Elasticsearch will indeed set automatically- but not @timestamp.

I was... On the same index I had fluentd indexing records which does sets @timestamp and I can use it in Kibana. Since my data was a json, I ended up adding a field with the timestamp (JObject) and now I have a @timestamp.


Light up NS_FORMAT_FUNCTION and annotate every formatter

This pull request must merge after #2628. Otherwise, the build will be broken.

@bviglietta FYI, this is the other half of the formatting change -- it introduces build breaks for the things in #2628!

:shipit:

It appears that there were formats that changed since my previous format branch forked.

This is in build again.
I fully expect that this will cause our warnings to spike; there may even be build failures in the sample app collateral. This is expected and required for us to move forward withformatter safety.


How could I login by using chrome cookies ?

Cookies generated by puppeterer Instagram registration .

The web API and Android API are generally different so it wouldn't make sense to have the cookies from the browser on the phone. You could save the credentials and then log in.


Build fails with error generate_sdks.py: error: unrecognized arguments: --enable-virtual-operations

Describe the bug
When building custom clients, Build fails with error
Generating client for <my_service_name> version <my_service_version>
usage: generate_sdks.py [-h] [--outputLocation OUTPUTLOCATION]
[--serviceName SERVICENAME]
[--clientConfigDefaults CLIENTCONFIGDEFAULTS]
[--apiVersion APIVERSION] [--namespace NAMESPACE]
[--licenseText LICENSETEXT]
[--pathToApiDefinitions PATHTOAPIDEFINITIONS]
[--pathToGenerator PATHTOGENERATOR] [--prepareTools]
[--standalone] [--listAll] [--enableVirtualOperations]
generate_sdks.py: error: unrecognized arguments: --enable-virtual-operations
Reason:
Mismatch in argument names in sdks.cmake and generate_sdks.py
generate_sdks.py takes argument as "--enableVirtualOperations"
can be seen in Line 47 and used in Line 101 in
aws-sdk-cpp/tools/scripts/legacy/generate_sdks.py
However, in aws-sdk-cpp/cmake/sdks.cmake, when it calls generate_sdks.py, at Line 80:
if(ENABLE_VIRTUAL_OPERATIONS) # it could be set to 0/1 or ON/OFF
set(ENABLE_VIRTUAL_OPERATIONS_ARG "--enable-virtual-operations")
else()
set(ENABLE_VIRTUAL_OPERATIONS_ARG "")
endif()
it created argument as "--enable-virtual-operations" instead of "--enableVirtualOperations"
and used it at Line 145, as:
COMMAND ${PYTHON3_CMD} tools/scripts/legacy/generate_sdks.py --serviceName ${C_SERVICE_NAME} --apiVersion ${C_VERSION} ${ENABLE_VIRTUAL_OPERATIONS_ARG} --outputLocation ./generated/
Expected Behavior
Build should not fail
Current Behavior
Build fails
Reproduction Steps
Build custom client with Legacy build ON
Possible Solution
Change argument for generate_sdks.py to  "--enable-virtual-operations" instead of "--enableVirtualOperations"
Additional Information/Context
No response
AWS CPP SDK version used
1.11.169
Compiler and Version used
Visual Studio 2022
Operating System and version
Windows 10

Does this pr fix the error you see while generating the sdk?

No it doesn't. That PR is for a different issue  #2712
https://github.com/aws/aws-sdk-cpp/issues/2712  that was reported.
On Tue, Oct 17, 2023 at 4:38 PM Joseph Klix @.***>
wrote:

Does this pr https://github.com/aws/aws-sdk-cpp/pull/2720 fix the error
you see while generating the sdk?
—
Reply to this email directly, view it on GitHub
https://github.com/aws/aws-sdk-cpp/issues/2713#issuecomment-1767359445,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKJYAE6DLNDJK7SAZDLLA7DX74JJFAVCNFSM6AAAAAA57M3542VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRXGM2TSNBUGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

I added documentation for how to generate custom clients here. Can you try following those steps and let me know if you have any problems?

In added documentation, you mention placing the api-defintion in
Place your new model files in the correct folders:

c2j model (looks like this: mycustomservice-2020-08-01.normal.json)

In this path:
aws-sdk-cpp/tree/main/tools/code-generation/api-descriptions

I have been placing it here:
aws-sdk-cpp\code-generation\api-descriptions
There is no such path starting with aws-sdk-cpp/tree/..
On Tue, Nov 14, 2023 at 10:28 AM Joseph Klix @.***>
wrote:

I added documentation for how to generate custom clients here
https://github.com/aws/aws-sdk-cpp/pull/2748/files. Can you try
following those steps and let me know if you have any problems?
—
Reply to this email directly, view it on GitHub
https://github.com/aws/aws-sdk-cpp/issues/2713#issuecomment-1810892089,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKJYAE7BFHQDIWZ7SE3TSJTYEOZ4TAVCNFSM6AAAAAA57M3542VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJQHA4TEMBYHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Sorry for not noticing this initially, but it should be aws-sdk-cpp/tools/code-generation/api-descriptions not aws-sdk-cpp/tree/main/tools/code-generation/api-descriptions. I have updated the PR to include this change.
Does this work for you, or are you still running into errors building the sdk?

Thanks. I'm still running into issues building the sdk.
The next error thrown by the build was a java error:
"Unable to access jarfile ./code-generation/generator
target/aws-client-generator-1.0-SNAPSHOT-jar-with-dependencies.jar
Generating MyServiceName api version 2020-06-10"
MyServiceName - my service name
2020-06-10 - my service version
I'm currently stuck at this stage as there is no indication as to what
could be causing this next issue.
There are no error logs/outputs.
On Mon, Nov 20, 2023 at 4:31 PM Joseph Klix @.***>
wrote:

Sorry for not noticing this initially, but it should be
aws-sdk-cpp/tools/code-generation/api-descriptions not
aws-sdk-cpp/tree/main/tools/code-generation/api-descriptions. I have
updated the PR to include this change.
Does this work for you, or are you still running into errors building the
sdk?
—
Reply to this email directly, view it on GitHub
https://github.com/aws/aws-sdk-cpp/issues/2713#issuecomment-1820025704,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKJYAE7R6XTH22HU4Z7PWN3YFPY63AVCNFSM6AAAAAA57M3542VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRQGAZDKNZQGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

I’m using:

java -version

java version "1.8.0_202"
Java(TM) SE Runtime Environment (build 1.8.0_202-b08)
Java HotSpot(TM) 64-Bit Server VM (build 25.202-b08, mixed mode)

python.exe --version

Python 3.10.11
On Sat, Nov 25, 2023 at 4:17 PM github-actions[bot] <
@.***> wrote:

Greetings! It looks like this issue hasn’t been active in longer than a
week. We encourage you to check if this is still an issue in the latest
release. Because it has been longer than a week since the last update on
this, and in the absence of more information, we will be closing this issue
soon. If you find that this is still a problem, please feel free to provide
a comment or add an upvote to prevent automatic closure, or if the issue is
already closed, please feel free to open a new one.
—
Reply to this email directly, view it on GitHub
https://github.com/aws/aws-sdk-cpp/issues/2713#issuecomment-1826449930,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKJYAE5OTAQE5IDTPDQOCJDYGKDCJAVCNFSM6AAAAAA57M3542VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRWGQ2DSOJTGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Are you using this code generation script? Rather than the legacy one?


issue in installing ffmpeg with nv-codec-headers on centos 8 machine

Hi All,
I have CentOS Stream 8  vm which has 50 gb space and i have tried the below steps for installing ffmpeg on the the vm by following steps present in the link
https://developer.nvidia.com/blog/nvidia-ffmpeg-transcoding-guide/
1.Downloaded repository "https://git.ffmpeg.org/ffmpeg.git and cloned with
git clone https://git.ffmpeg.org/ffmpeg.git"
2.Downaloded the nvidia driver for tesla T4 product and linux 64-bit RHEL 8
file name is "nvidia-driver-local-repo-rhel8-510.47.03-1.0-1.x86_64.rpm"
3.Downloaded the cuda tool kit for centos 8 system by running following commands
(I)wget https://developer.download.nvidia.com/compute/cuda/11.6.2/local_installers/cuda-repo-rhel8-11-6-local-11.6.2_510.47.03-1.x86_64.rpm
(II)sudo rpm -i cuda-repo-rhel8-11-6-local-11.6.2_510.47.03-1.x86_64.rpm
(III)sudo dnf clean all
(IV)sudo dnf -y module install nvidia-driver:latest-dkms
(V)sudo dnf -y install cuda
4.cloned the rep FFmpeg/nv-codec-headers
git clone https://github.com/FFmpeg/nv-codec-headers.git
5.After completion of ffmpeg/nv-codec-headers,i have entered to the nv-codec-headers
cd nv-codec-headers
6.i'm  getting below installation messages when i ran the "make install" command and kindly help me in resolving the issue
[root@localhost nv-codec-headers]# make install
sed 's#@@PREFIX@@#/usr/local#' ffnvcodec.pc.in > ffnvcodec.pc
install -m 0755 -d '/usr/local/include/ffnvcodec'
install -m 0644 include/ffnvcodec/*.h '/usr/local/include/ffnvcodec'
install -m 0755 -d '/usr/local/lib/pkgconfig'
install -m 0644 ffnvcodec.pc '/usr/local/lib/pkgconfig'

The question is out of scope for this repo, since issues here are about these builds, not generic ffmpeg issues.
As far as building ffmpeg is concerned, your steps 2 and 3 are entirely irrelevant. Building FFmpeg by default uses clang to compile .cu code, and otherwise does not interact with the driver or the CUDA sdk at all otherwise.
But what exactly is your issue? I don't see any issue or error in what you pasted.

With some helpers like this uses clang to compile .cu code, that compresses PTX/streaming assembly further https://github.com/FFmpeg/FFmpeg/commit/072788c46e36a21ca9e8f1e3cc19a1944db5b89c

Hi ,
I have CentOS Stream 8 vm and i have cloned the ffmpeg repo by the following command
https://git.ffmpeg.org/ffmpeg.git
and I ran the below command and i have got an error  after execution of the command
./configure --enable-cuda --enable-cuvid --enable-nvdec --enable-nvenc --enable-nonfree --enable-libnpp --extra-cflags=-I/usr/local/cuda/include  --extra-ldflags=-L/usr/local/cuda/lib64 --disable-x86asm
below is the error i have got ,can u please help us in fixing the issue
ERROR: libnpp not found
config.log

ERROR: libnpp not found

That cannot be used without nonfree and thus without Nvidia SDK on Debian. I recomment disabling enable-nonfree for now and compiling everything from nvidia that is "free" with clang. That is most of it, cuda, nvdec, nvenc, etc. Everything escept libnpp.


Enable config file usage and flags

Enables config file usage and flags as follows:
Flags enabled for registry CLI:
  -c, --config string             Name of a settings profile or path to config file
      --registry.address string   the server and port of the registry api (eg. localhost:8080)
      --registry.insecure         set to true if client must connect via http (not https)
      --registry.token string     the token to use for authorization to registry

Notes:

This is 100% backward compatible
go test will use env vars, not flags
Settings are honored in prioritized order from: 1. flags, 2. env vars, 3. config file
Config files are assumed to be stored in $HOME/.config/registry
However, --config flag can specify an explicit path to a settings file directly

Config file management will be handled in #649
Fixes #647

Let's watch out for possible collisions between the --registry.* flags and options in autogenerated commands.
$ registry rpc update-api --help
UpdateApi can be used to modify a specified API.

Usage:
  registry rpc update-api [flags]

Flags:
      --allow_missing                       If set to true, and the api is not found, a new...
      --api.annotations stringArray         key=value pairs. Annotations attach non-identifying metadata to...
      --api.availability string             A user-definable description of the availability...
      --api.description string              A detailed description.
      --api.display_name string             Human-meaningful name.
      --api.labels stringArray              key=value pairs. Labels attach identifying metadata to resources....
      --api.name string                     Resource name.
      --api.recommended_deployment string   The recommended deployment of the API.  Format:...
      --api.recommended_version string      The recommended version of the API.  Format:...
      --from_file string                    Absolute path to JSON file containing request payload
  -h, --help                                help for update-api
      --update_mask.paths strings           The set of field mask paths.

Global Flags:
  -j, --json      Print JSON output
  -v, --verbose   Print verbose output

I think we're ok now because none of our API methods are taking a registry message as a request argument.

Hmm. I don't know how we could ensure that we don't collide with the current autogen scheme since it does't have it's own namespace...

I think the current option names are good. Just wanted to point out the possibility of future surprises.

The commit I just pushed fixes the generated rpc cmds to use the same files and flags as the main registry cmd. However, it leaves quite a bit of dead code in the generate clients that we need to work on removing. The following is a diff example of what we have yet to do: https://gist.github.com/theganyo/99150cbc129557d991205c87528aa972


test: add iptables masquerading without random-fully test

As suggested in the ticket, let's add a test for iptables masqueranding
without the random-fully option. This should tell us if the
"K8sDatapathConfig Encapsulation Check iptables masquerading with
random-fully" test is failing due to the random-fully option or not.
Related-to: #13773

test-me-please

test-missed-k8s

retest-net-next


chore: add spaced project name

Description

Fixes #(issue number)

Checklist

[x] My code follows the contributing guidelines of this
project, including, in particular, with regard to any style guidelines
[x] The title of my PR complies with the Conventional Commits
specification; in particular, it clearly indicates
that a change is a breaking change
[x] I acknowledge that all my commits will be squashed into a single commit,
using the PR title as the commit message
[x] I have performed a self-review of my own code
[x] I have commented my code in hard-to-understand areas
[x] I have updated the user-facing documentation to describe any new or
changed behavior
[x] I have added type annotations for all function/class/method interfaces
or updated existing ones (only for Python, TypeScript, etc.)
[x] I have provided appropriate documentation (Google-style Python
docstrings) for all packages/modules/functions/classes/
methods or updated existing ones
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature
works
[x] New and existing unit tests pass locally with my changes
[x] I have not reduced the existing code coverage

Comments

Summary by Sourcery
Revise project naming conventions across the codebase to support spaced, dashed, and underscored formats, ensuring consistency in documentation, CI workflows, and test paths.
Enhancements:

Update project naming conventions to use spaced, dashed, and underscored formats for better readability and consistency.

CI:

Modify CI workflow scripts to use the new underscored project name format.

Documentation:

Update README badges and links to reflect the new project naming conventions.

Tests:

Adjust test paths to accommodate the new underscored project name format.

Maybe make this change in the Makefile as well in this PR:
elixir-cloud-aai/cloud-storage-handler#17 (comment)

My reasoning was to let the user/dev know that, the corresponding console script project_name_dashed has been installed in their environment too. Well I have made that changes, if you think otherwise let me know.

Please check that the package meets all the requirements and lets merge.

Also this is the file str after.
tree command ran  inside the dir after-rename-done.
.
├── after_rename_done
│   ├── __init__.py
│   └── main.py
├── dist
│   ├── after_rename_done-0.1.0-py3-none-any.whl
│   └── after_rename_done-0.1.0.tar.gz
├── docs
│   ├── make.bat
│   ├── Makefile
│   └── source
│       ├── conf.py
│       ├── index.rst
│       └── pages
│           └── modules.rst
├── images
│   ├── logo-elixir-cloud-aai.svg
│   └── logo-elixir.svg
├── LICENSE
├── Makefile
├── poetry.lock
├── PULL_REQUEST_TEMPLATE.md
├── pyproject.toml
├── README.md
└── tests
    ├── __init__.py
    ├── test_integration
    │   ├── __init__.py
    │   └── test_init.py
    └── test_unit
        ├── __init__.py
        └── test_init.py

10 directories, 22 files


Delete marshal PVC after run

When Kale creates a pipeline, it includes a step to create a marshal PVC for marshalling of data between pipeline steps. However, this PVC doesn't seem to be deleted after the run, which creates a lot of stale volumes. Would it be an idea to add a step to remove the marshal PVC as the final step in the pipeline?

Hello!
We are working on KFP-level garbage control, without the need for Kale specific code. You can take a look at kubeflow/pipelines#1779, as well as other issues/PRs referencing that.
We target KFP gc because, in any case, a PVC will not be deleted until all pods that mount it are deleted. Since workflows leave Completed pods behind upon completion, deleting PVCs will not lead to actual deletion.

That makes sense! Thanks for pointing me in the right direction. I'll follow the KFP issue and close this for now.