monocraft: init at 1.2

Description of changes

It's a monospace font that replicates the Minecraft typeface.
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 190428 run on aarch64-darwin 1

1 package built:

monocraft


Discharge an item

For SCSB, we need the ability to discharge an item from the ReCAP circulation desk.
SCSB is aware of the MMS Id, Holding Id, and Item Id, so it should not require an item lookup by barcode before doing it.
proposed route: post '/discharge', to: 'items#discharge'
with required params: mms_id, holding_id, item_id, auth_token
The endpoint should require a valid, hard-coded auth token.
The alma endpoint to use is as follows. Note that the values provided for these parameters won't vary, just the ids sent in the api path.
url = 'https://api-na.hosted.exlibrisgroup.com'
response = alma_conn(url).post do |req|
  req.url 'almaws/v1/bibs/9968643943506421/holdings/22258767470006421/items/23258767460006421'
  req.headers['Content-Type'] = 'application/json'
  req.headers['Accept'] = 'application/json'
  req.params['apikey'] = [key]
  req.params['op'] = 'scan'
  req.params['external_id'] = 'false'
  req.params['library'] = 'recap'
  req.params['circ_desk'] = 'DEFAULT_CIRC_DESK'
  req.params['done'] = 'true'
end

If there are required params should we do something like post '/bibliographic/:mms_id/holdings/:holding_id/items/:item_id/discharge? Seems like that would leverage more of Rails' handling of params.

👍🏻 that sounds good to me.


inline images in RTFM theme not inline

I have not tested this outside of the RTFM theme yet, so I'm not sure whose bug it is, but inline images are not being rendered as inline elements.
Or I could be getting the markdown wrong. Currently I'm doing:
![foo](../path/to/dir/image.png) Blah blah blah...

Which according to everything I find online should work as an inline image. However, it renders itself on a separate line.
I've done a cursory check through the source code but I'm not finding where the actual conversion from md to html is happening. I imagine it would just be a matter of checking for a newline and using either inline-block or block depending on the result.

This is really how markdown and html works. If you want an image to be inline, you need to add a class to it and then set that class to have display: inline. Alternatively you can just use an HTML tag.

Oh, cheers for that. I didn't realise. Daring Fireball tutorial on markdown suggests otherwise, but I'm happy to just use html tag directly. Thanks.


Re-title header on B+ onwards

Just realized (whilst in the middle of the pins re-factor, mulling over exactly how to handle inter-device pin locking) that the header on the B+ onwards isn't P1 ... it's J8. I'll get this fixed up while I'm at it to avoid any confusion of users looking at their Pi's and going "but where the hell is P1?!"

...but it's labelled as "GPIO".

look at the bit just by pin 1

had a look on a Zero, a 2B, and a 3B (haven't got a B+ but I've found some photos online) - I'm pretty sure that header is labelled J8 but you're right there's a "GPIO" label silk-screened on too.

Ah yes. They even kept the "J8" labelling on the PiZero, which is surprising.

BTW I had already noticed this (P1 discrepancy), but I didn't think it was worth fixing ;-)

Somehow the fact you'd already noticed it doesn't surprise me ;)

What do P1 and J8 stand for?

@bennuttall I think this has been done, as the pinout diagrams now include 'J8' ?


Broken link in the README

The link to the paper in the README seems to be broken. You could alternatively post a bibliography entry for the paper; that would probably be sufficient.
It is always fun to see new languages!

Thank you.
I will add a link to archive.


⚠ Bofrost.fr has degraded performance

In 7d197b7, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 963 ms

Resolved: Bofrost.fr performance has improved in 63c244f.


Are there plans to support YOLOX？

Are there plans to support YOLOX？I tried YOLOX myself and it didn't seem to work very well

Thanks for your reply. I have a question, why is it better to choose model.model.model.model[-2] 23rd  layer than model.model.model.model[-5] 20th layer in yolov5s? In fact, they are both pre-layer of Detection.

result of target_layers = [model.model.model.model[23]]

result of target_layers=[model.model.model.model[20]]

If I use YOLOX, do you have any suggestions for selecting target_layers? Thank you very much.

Hello friend, have you successfully applied thisHello friend, have you successfully applied this on yolox? If so, can you communicate with me? I am also doing relevant research.

thisHello

not yet，I have tried some target layers，but only model.backbone.dark4 looks a little bit like right. I'm not sure that's right.

OK, thank you for your response,and i find someothers,like C3_n4 in backbone, cls_conv[2], obj_conv[2] and reg_preds[2] in head may make a seemingly correct result.
in addition, I found that only EigenCAM can be directly applied to YOLOX，maybe I made a mistake。

OK, thank you for your response,and i find someothers,like C3_n4 in backbone, cls_conv[2], obj_conv[2] and reg_preds[2] in head may make a seemingly correct result. in addition, I found that only EigenCAM can be directly applied to YOLOX，maybe I made a mistake。

hello friend. have u ever successfully applied this into yolox?

OK, thank you for your response,and i find someothers,like C3_n4 in backbone, cls_conv[2], obj_conv[2] and reg_preds[2] in head may make a seemingly correct result. in addition, I found that only EigenCAM can be directly applied to YOLOX，maybe I made a mistake。

hello friend. have u ever successfully applied this into yolox?how do it?

Hello! I also found this problem. I think it should be because Yolox's head is decoupled. Can you tell me your latest progress. Thank you.

OK, thank you for your response,and i find someothers,like C3_n4 in backbone, cls_conv[2], obj_conv[2] and reg_preds[2] in head may make a seemingly correct result. in addition, I found that only EigenCAM can be directly applied to YOLOX，maybe I made a mistake。

Hello! I also found this problem. I think it should be because Yolox's head is decoupled. Can you tell me your latest progress. Thank you.

target_layers = [model.backbone.backbone.dark5]
target_layers = [model.head.obj_preds[2], model.head.reg_preds[2], model.head.cls_preds[2]]
I set it up like this，

OK, thank you for your response,and i find someothers,like C3_n4 in backbone, cls_conv[2], obj_conv[2] and reg_preds[2] in head may make a seemingly correct result. in addition, I found that only EigenCAM can be directly applied to YOLOX，maybe I made a mistake。

Hello! I also found this problem. I think it should be because Yolox's head is decoupled. Can you tell me your latest progress. Thank you.

target_layers = [model.backbone.backbone.dark5]
target_layers = [model.head.obj_preds[2], model.head.reg_preds[2], model.head.cls_preds[2]]
I set it up like this，

OK, thank you for your response,and i find someothers,like C3_n4 in backbone, cls_conv[2], obj_conv[2] and reg_preds[2] in head may make a seemingly correct result. in addition, I found that only EigenCAM can be directly applied to YOLOX，maybe I made a mistake。

Hello! I also found this problem. I think it should be because Yolox's head is decoupled. Can you tell me your latest progress. Thank you.

target_layers = [model.backbone.backbone.dark5] target_layers = [model.head.obj_preds[2], model.head.reg_preds[2], model.head.cls_preds[2]] I set it up like this，

Thank you for your reply! The target layers I selected are the same as yours, but when I output the thermal map, I found that the target area is not highlighted but the background area is highlighted. Do you know why? Look forward to your reply!!!

OK, thank you for your response,and i find someothers,like C3_n4 in backbone, cls_conv[2], obj_conv[2] and reg_preds[2] in head may make a seemingly correct result. in addition, I found that only EigenCAM can be directly applied to YOLOX，maybe I made a mistake。

Hello! I also found this problem. I think it should be because Yolox's head is decoupled. Can you tell me your latest progress. Thank you.

target_layers = [model.backbone.backbone.dark5] target_layers = [model.head.obj_preds[2], model.head.reg_preds[2], model.head.cls_preds[2]] I set it up like this，

Thank you for your reply! The target layers I selected are the same as yours, but when I output the thermal map, I found that the target area is not highlighted but the background area is highlighted. Do you know why? Look forward to your reply!!!

Maybe you can try a different setup， mine turned out like this

thisHello

not yet，I have tried some target layers，but only model.backbone.dark4 looks a little bit like right. I'm not sure that's right.

Hello, I found the same situation in my experiment and couldn't get satisfactory results after changing multiple settings. Could you please tell me how you solved it?


_feed.html.erb it seems not work!

Hi,
Feed.rb logic does work, but does not display the icon tag or the name. Nor if a post recommended does not show "Recommended by Stories ... and other 5".
Why is this happening?
Thanks!

this has been fixed since https://github.com/kenny-hibino/stories/commit/dddac06d26a530eaa12496bbf2452f578861f8d4


Clean conda install results in No module named 'nbconvert.exporters.export'

Clean installation in new, empty conda environment using:
conda install -c conda-forge nbpresent
results in
ModuleNotFoundError: No module named 'nbconvert.exporters.export'

same with pip install nbpresent


fix(curriculum): Add solutions to 16 Applied Accessibility challenges #35751

This commit adds 16 full working solutions to the responsive web design
principles dealing with applied accessibility.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

Related to issue #35751

Hi @thecodingaviator - the changes you suggested were applied. Let me know if further work needs to be done on these. Thank you.

@rimij405 Can you squash the commits in a rebase?

Yes. Would I just push after the rebase or do I need to make a new pull request for that?

Yes. Would I just push after the rebase or do I need to make a new pull request for that?

You would do this on this PR.  You can squash the 17 commits down to a single commit.  It cleans up the PR.

Ah, gotcha. I'll get right to that.

@RandellDawson - History for this pull request has been rebased, commits squashed, and changes pushed to the branch. Pending the Travis CI check, everything should be in order now. The git push -f clarification helped because I wasn't sure if I should have merged the existing remote (since it couldn't fast-forward) or if I should overwrite it.
Thank you for the guidance!

Hi

Hi

Hi

@thecodingaviator If you're happy with the changes, I think this is ready to merge.

Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


docker-ejabberd and ejabberd deb

Hello,
I need some help.
I have installed ejabberd 18.03 deb package on ubuntu from here (https://www.process-one.net/en/ejabberd/downloads/) and also enabled external auth with php script. Which is running successfully and no issues.
Now I am trying to use the same script with latest 18.03 "docker-ejabberd" and its not working. Error log says
10:07:07.584 [info] (<0.717.0>) Accepted connection ::ffff: <IP_ADDRESS>:41628 -> ::ffff: <IP_ADDRESS>:5222 10:08:07.587 [error] extauth call '[<<"auth">>,<<"admin">>,<<"xxxxxxxxxxxxx.com">>,<<"xxxxxxxxxxxxx">>]' didn't receive response
Can somebody shed some light on what could be the possible issues.
Thanks in advance

Looks like your external auth script is not working as expected. Check there first.

@mitchellurgero
ejabberd is able to execute php script because I can see all the logs that I have mentioned in the script.
this time php script is kept inside /bin/index.php
while earlier when I was using ejabberd without docker the script was kept inside /var/www/html/index.php and its was working. I was able to authenticate.

No i am not sending response in hex its just for logging purpose.
See the last line
fwrite(..............
That line is being used to send response.
I also noticed that you are not using that line. While if you search all the PHP scripts available on the internet are using
fwrite for sending response to ejabberd.
You sure we don't need that line?

Sorry - for context on my code:
https://github.com/mitchellurgero/ejabberd_gnusocial/blob/master/xmpp_auth.php

Thanks for all your support. I will try this.


Tests for Mailer and Notification modules

Related issues
https://github.com/DivanteLtd/vue-storefront/issues/1878
Short description and why it's useful
Unit tests for two new modules to check if functionality is working correctly. Also updated docs for Notification module, since it wasn't actualized after latest refactoring.
Upgrade Notes and Changelog

[x] No upgrade steps required (100% backward compatibility)
[ ] I've updated the Upgrade notes and Changelog on how to port existing VS sites with this new feature

Contribution and currently important rules acceptance

[x] I read and followed contribution rules
[x] I read the TypeScript Action Plan and adjusted my PR according to it
[x] I read about Vue Storefront Modules and I am aware that every new feature should be a module

It's perfect! Thanks buddy!


Add missing "prints" comment

Fixes rdar://103039462

Force pushed to make a minor change to the commit message only.


Add LINE Things Starter for Puck.js

Puck.js and Espruino is now supporting paring/bonding!
https://www.espruino.com/BLE+Security#bonding-whitelisting
Let's add a sample code to LINE Things Starter!

Cool! Looks good to me! Tested with 5 Pucks and 3 Phones. No issues.


operator test-operator-wcheang (0.0.1)

There were some errors in your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-run-2vljj
Start Time: 2021-12-16 06:48:54+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2021-12-16 06:48:55+00:00
7 seconds

:heavy_check_mark:
set-env
2021-12-16 06:49:05+00:00
8 seconds

:heavy_check_mark:
checkout
2021-12-16 06:49:15+00:00
18 seconds

:heavy_check_mark:
validate-pr-title
2021-12-16 06:49:37+00:00
7 seconds

:heavy_check_mark:
get-bundle-path
2021-12-16 06:49:46+00:00
7 seconds

:heavy_check_mark:
bundle-path-validation
2021-12-16 06:49:56+00:00
17 seconds

:heavy_check_mark:
content-hash
2021-12-16 06:50:16+00:00
2 minutes

:heavy_check_mark:
certification-project-check
2021-12-16 06:50:16+00:00
17 seconds

:heavy_check_mark:
create-support-link-for-pr
2021-12-16 06:50:36+00:00
7 seconds

:heavy_check_mark:
get-organization
2021-12-16 06:50:36+00:00
17 seconds

:heavy_check_mark:
get-cert-project-related-data
2021-12-16 06:50:37+00:00
a minute

:x:
annotations-validation
2021-12-16 06:50:56+00:00
18 seconds

Troubleshooting
Please refer to the troubleshooting guide.

There were some errors in your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-run-886dt
Start Time: 2021-12-16 07:08:59+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2021-12-16 07:09:00+00:00
8 seconds

:heavy_check_mark:
set-env
2021-12-16 07:09:12+00:00
8 seconds

:heavy_check_mark:
checkout
2021-12-16 07:09:23+00:00
22 seconds

:heavy_check_mark:
validate-pr-title
2021-12-16 07:09:49+00:00
7 seconds

:heavy_check_mark:
get-bundle-path
2021-12-16 07:09:58+00:00
7 seconds

:heavy_check_mark:
bundle-path-validation
2021-12-16 07:10:08+00:00
16 seconds

:heavy_check_mark:
content-hash
2021-12-16 07:10:27+00:00
2 minutes

:heavy_check_mark:
certification-project-check
2021-12-16 07:10:27+00:00
18 seconds

:heavy_check_mark:
create-support-link-for-pr
2021-12-16 07:10:47+00:00
8 seconds

:heavy_check_mark:
get-organization
2021-12-16 07:10:47+00:00
19 seconds

:heavy_check_mark:
get-cert-project-related-data
2021-12-16 07:10:48+00:00
a minute

:x:
annotations-validation
2021-12-16 07:11:09+00:00
18 seconds

Troubleshooting
Please refer to the troubleshooting guide.

There were some errors in your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-run-6dhkb
Start Time: 2021-12-16 07:15:44+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2021-12-16 07:15:45+00:00
6 seconds

:heavy_check_mark:
set-env
2021-12-16 07:15:54+00:00
6 seconds

:heavy_check_mark:
checkout
2021-12-16 07:16:04+00:00
22 seconds

:heavy_check_mark:
validate-pr-title
2021-12-16 07:16:29+00:00
8 seconds

:heavy_check_mark:
get-bundle-path
2021-12-16 07:16:39+00:00
8 seconds

:heavy_check_mark:
bundle-path-validation
2021-12-16 07:16:49+00:00
17 seconds

:heavy_check_mark:
certification-project-check
2021-12-16 07:17:09+00:00
17 seconds

:heavy_check_mark:
content-hash
2021-12-16 07:17:09+00:00
2 minutes

:heavy_check_mark:
get-organization
2021-12-16 07:17:29+00:00
16 seconds

:heavy_check_mark:
create-support-link-for-pr
2021-12-16 07:17:29+00:00
7 seconds

:heavy_check_mark:
get-cert-project-related-data
2021-12-16 07:17:30+00:00
4 minutes

:heavy_check_mark:
annotations-validation
2021-12-16 07:17:49+00:00
16 seconds

:heavy_check_mark:
get-supported-versions
2021-12-16 07:18:08+00:00
19 seconds

:heavy_check_mark:
yaml-lint
2021-12-16 07:18:08+00:00
18 seconds

:heavy_check_mark:
verify-changed-directories
2021-12-16 07:18:09+00:00
7 seconds

:heavy_check_mark:
get-ci-results-attempt
2021-12-16 07:19:35+00:00
4 minutes

:heavy_check_mark:
verify-project-distribution
2021-12-16 07:21:58+00:00
6 seconds

:heavy_check_mark:
submission-validation
2021-12-16 07:21:58+00:00
11 seconds

:heavy_check_mark:
merge-registry-credentials
2021-12-16 07:21:58+00:00
a minute

:heavy_check_mark:
update-cert-project-status
2021-12-16 07:22:11+00:00
8 seconds

:heavy_check_mark:
digest-pinning
2021-12-16 07:23:56+00:00
29 seconds

:x:
preflight-trigger
2021-12-16 07:23:59+00:00
3 minutes

:heavy_check_mark:
verify-pinned-digest
2021-12-16 07:24:27+00:00
6 seconds

:heavy_check_mark:
dockerfile-creation
2021-12-16 07:24:34+00:00
11 seconds

:heavy_check_mark:
build-bundle
2021-12-16 07:24:48+00:00
23 seconds

:x:
generate-index
2021-12-16 07:25:12+00:00
21 seconds

Troubleshooting
Please refer to the troubleshooting guide.

Pipeline Summary
Pipeline: operator-release-pipeline
PipelineRun: operator-release-pipeline-run-kgf8h
Start Time: 2021-12-16 07:47:20+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2021-12-16 07:47:20+00:00
7 seconds

:heavy_check_mark:
set-env
2021-12-16 07:47:29+00:00
7 seconds

:heavy_check_mark:
checkout
2021-12-16 07:47:39+00:00
17 seconds

:heavy_check_mark:
get-bundle-path
2021-12-16 07:47:59+00:00
6 seconds

:x:
bundle-path-validation
2021-12-16 07:48:07+00:00
26 seconds

There were errors while publishing your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-release-pipeline
PipelineRun: operator-release-pipeline-run-jv2jf
Start Time: 2021-12-16 08:12:46+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2021-12-16 08:12:47+00:00
7 seconds

:heavy_check_mark:
set-env
2021-12-16 08:12:56+00:00
7 seconds

:heavy_check_mark:
checkout
2021-12-16 08:13:04+00:00
22 seconds

:heavy_check_mark:
get-bundle-path
2021-12-16 08:13:28+00:00
7 seconds

:heavy_check_mark:
bundle-path-validation
2021-12-16 08:13:38+00:00
9 seconds

:heavy_check_mark:
get-supported-versions
2021-12-16 08:13:49+00:00
2 minutes

:heavy_check_mark:
certification-project-check
2021-12-16 08:13:49+00:00
11 seconds

:heavy_check_mark:
content-hash
2021-12-16 08:13:49+00:00
10 seconds

:heavy_check_mark:
inspect-image
2021-12-16 08:13:50+00:00
25 seconds

:heavy_check_mark:
get-organization
2021-12-16 08:14:01+00:00
18 seconds

:heavy_check_mark:
create-support-link-for-pr
2021-12-16 08:14:01+00:00
8 seconds

:heavy_check_mark:
get-cert-project-related-data
2021-12-16 08:14:21+00:00
20 seconds

:heavy_check_mark:
get-vendor-related-data
2021-12-16 08:14:44+00:00
7 seconds

:x:
publish-to-ocp-registry
2021-12-16 08:14:53+00:00
9 seconds

There were errors while publishing your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-release-pipeline
PipelineRun: operator-release-pipeline-run-rvpgw
Start Time: 2021-12-16 19:27:40+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2021-12-16 19:27:41+00:00
7 seconds

:heavy_check_mark:
set-env
2021-12-16 19:27:51+00:00
6 seconds

:heavy_check_mark:
checkout
2021-12-16 19:27:59+00:00
23 seconds

:heavy_check_mark:
get-bundle-path
2021-12-16 19:28:24+00:00
8 seconds

:heavy_check_mark:
bundle-path-validation
2021-12-16 19:28:34+00:00
6 minutes

:heavy_check_mark:
get-supported-versions
2021-12-16 19:34:57+00:00
12 seconds

:heavy_check_mark:
certification-project-check
2021-12-16 19:34:57+00:00
41 seconds

:heavy_check_mark:
content-hash
2021-12-16 19:34:57+00:00
9 seconds

:heavy_check_mark:
inspect-image
2021-12-16 19:34:58+00:00
24 seconds

:heavy_check_mark:
get-organization
2021-12-16 19:35:39+00:00
9 seconds

:heavy_check_mark:
create-support-link-for-pr
2021-12-16 19:35:40+00:00
6 seconds

:heavy_check_mark:
get-cert-project-related-data
2021-12-16 19:35:49+00:00
32 seconds

:heavy_check_mark:
get-vendor-related-data
2021-12-16 19:36:23+00:00
10 seconds

:x:
publish-to-ocp-registry
2021-12-16 19:36:35+00:00
9 seconds

There were some errors in your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-run-zcsx8
Start Time: 2021-12-16 19:42:04+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2021-12-16 19:42:05+00:00
8 seconds

:heavy_check_mark:
set-env
2021-12-16 19:42:18+00:00
10 seconds

:heavy_check_mark:
checkout
2021-12-16 19:42:31+00:00
22 seconds

:heavy_check_mark:
validate-pr-title
2021-12-16 19:42:56+00:00
7 seconds

:heavy_check_mark:
get-bundle-path
2021-12-16 19:43:06+00:00
7 seconds

:heavy_check_mark:
bundle-path-validation
2021-12-16 19:43:16+00:00
17 seconds

:heavy_check_mark:
certification-project-check
2021-12-16 19:43:37+00:00
18 seconds

:heavy_check_mark:
content-hash
2021-12-16 19:43:37+00:00
19 seconds

:heavy_check_mark:
get-organization
2021-12-16 19:43:57+00:00
26 seconds

:heavy_check_mark:
create-support-link-for-pr
2021-12-16 19:43:57+00:00
10 seconds

:heavy_check_mark:
get-cert-project-related-data
2021-12-16 19:43:59+00:00
a minute

:heavy_check_mark:
annotations-validation
2021-12-16 19:44:25+00:00
25 seconds

:heavy_check_mark:
submission-validation
2021-12-16 19:45:24+00:00
27 seconds

:heavy_check_mark:
verify-project-distribution
2021-12-16 19:45:24+00:00
8 seconds

:heavy_check_mark:
merge-registry-credentials
2021-12-16 19:45:24+00:00
22 seconds

:heavy_check_mark:
update-cert-project-status
2021-12-16 19:45:53+00:00
7 seconds

:heavy_check_mark:
reserve-operator-name
2021-12-16 19:46:04+00:00
7 seconds

:heavy_check_mark:
get-supported-versions
2021-12-16 19:46:14+00:00
28 seconds

:heavy_check_mark:
digest-pinning
2021-12-16 19:46:14+00:00
33 seconds

:x:
yaml-lint
2021-12-16 19:46:14+00:00
a minute

:heavy_check_mark:
verify-changed-directories
2021-12-16 19:46:15+00:00
7 seconds

:heavy_check_mark:
verify-pinned-digest
2021-12-16 19:46:49+00:00
7 seconds

Troubleshooting
Please refer to the troubleshooting guide.

There were some errors in your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

There were errors while publishing your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-release-pipeline
PipelineRun: operator-release-pipeline-run-s2qqm
Start Time: 2021-12-16 21:21:43+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2021-12-16 21:21:43+00:00
7 seconds

:heavy_check_mark:
set-env
2021-12-16 21:21:51+00:00
7 seconds

:heavy_check_mark:
checkout
2021-12-16 21:22:00+00:00
30 seconds

:heavy_check_mark:
get-bundle-path
2021-12-16 21:22:32+00:00
8 seconds

:heavy_check_mark:
bundle-path-validation
2021-12-16 21:22:45+00:00
14 seconds

:heavy_check_mark:
certification-project-check
2021-12-16 21:23:03+00:00
a minute

:heavy_check_mark:
content-hash
2021-12-16 21:23:03+00:00
17 seconds

:heavy_check_mark:
get-supported-versions
2021-12-16 21:23:04+00:00
2 minutes

:heavy_check_mark:
inspect-image
2021-12-16 21:23:04+00:00
21 seconds

:heavy_check_mark:
get-organization
2021-12-16 21:24:17+00:00
25 seconds

:heavy_check_mark:
create-support-link-for-pr
2021-12-16 21:24:17+00:00
8 seconds

:heavy_check_mark:
get-cert-project-related-data
2021-12-16 21:24:46+00:00
a minute

:heavy_check_mark:
get-vendor-related-data
2021-12-16 21:26:10+00:00
8 seconds

:x:
publish-to-ocp-registry
2021-12-16 21:26:20+00:00
15 seconds

There were errors while publishing your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

There were errors while publishing your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

There were errors while publishing your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

There were errors while publishing your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-release-pipeline
PipelineRun: operator-release-pipeline-run-rgg6r
Start Time: 2021-12-16 22:30:03+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2021-12-16 22:30:03+00:00
7 seconds

:heavy_check_mark:
set-env
2021-12-16 22:30:13+00:00
8 seconds

:heavy_check_mark:
checkout
2021-12-16 22:30:22+00:00
21 seconds

:heavy_check_mark:
get-bundle-path
2021-12-16 22:30:45+00:00
8 seconds

:heavy_check_mark:
bundle-path-validation
2021-12-16 22:30:55+00:00
11 seconds

:heavy_check_mark:
content-hash
2021-12-16 22:31:07+00:00
9 seconds

:heavy_check_mark:
certification-project-check
2021-12-16 22:31:07+00:00
a minute

:heavy_check_mark:
get-supported-versions
2021-12-16 22:31:08+00:00
41 seconds

:heavy_check_mark:
inspect-image
2021-12-16 22:31:08+00:00
21 seconds

:heavy_check_mark:
get-organization
2021-12-16 22:32:22+00:00
8 seconds

:heavy_check_mark:
create-support-link-for-pr
2021-12-16 22:32:22+00:00
7 seconds

:heavy_check_mark:
get-cert-project-related-data
2021-12-16 22:32:32+00:00
32 seconds

:heavy_check_mark:
get-vendor-related-data
2021-12-16 22:33:06+00:00
7 seconds

:heavy_check_mark:
publish-to-ocp-registry
2021-12-16 22:33:16+00:00
9 seconds

:heavy_check_mark:
create-container-image
2021-12-16 22:33:27+00:00
16 seconds

:heavy_check_mark:
trigger-marketplace-replication
2021-12-16 22:33:27+00:00
25 seconds

:heavy_check_mark:
publish-bundle
2021-12-16 22:33:53+00:00
8 seconds

:x:
publish-resources
2021-12-16 22:34:02+00:00
10 seconds

There were errors while publishing your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-release-pipeline
PipelineRun: operator-release-pipeline-run-srm2h
Start Time: 2022-03-16 05:00:15+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2022-03-16 05:00:15+00:00
8 seconds

:heavy_check_mark:
set-env
2022-03-16 05:00:26+00:00
7 seconds

:heavy_check_mark:
checkout
2022-03-16 05:00:35+00:00
22 seconds

:heavy_check_mark:
get-bundle-path
2022-03-16 05:00:59+00:00
8 seconds

:heavy_check_mark:
bundle-path-validation
2022-03-16 05:01:09+00:00
17 seconds

:heavy_check_mark:
content-hash
2022-03-16 05:01:28+00:00
9 seconds

:heavy_check_mark:
certification-project-check
2022-03-16 05:01:28+00:00
11 seconds

:heavy_check_mark:
inspect-image
2022-03-16 05:01:29+00:00
21 seconds

:heavy_check_mark:
get-supported-versions
2022-03-16 05:01:29+00:00
a minute

:heavy_check_mark:
create-support-link-for-pr
2022-03-16 05:01:40+00:00
8 seconds

:heavy_check_mark:
get-organization
2022-03-16 05:01:41+00:00
9 seconds

:heavy_check_mark:
get-cert-project-related-data
2022-03-16 05:01:52+00:00
a minute

:heavy_check_mark:
get-vendor-related-data
2022-03-16 05:03:14+00:00
9 seconds

:heavy_check_mark:
publish-to-ocp-registry
2022-03-16 05:03:24+00:00
9 seconds

:heavy_check_mark:
trigger-marketplace-replication
2022-03-16 05:03:35+00:00
13 seconds

:heavy_check_mark:
create-container-image
2022-03-16 05:03:36+00:00
12 seconds

:heavy_check_mark:
publish-bundle
2022-03-16 05:03:50+00:00
7 seconds

:heavy_check_mark:
request-signature
2022-03-16 05:03:59+00:00
32 seconds

:heavy_check_mark:
upload-signature
2022-03-16 05:04:31+00:00
12 seconds

:x:
publish-resources
2022-03-16 05:04:45+00:00
11 seconds

There were errors while publishing your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

There were some errors in your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

View your certification test results and logs here.

There were errors while publishing your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-release-pipeline
PipelineRun: operator-release-pipeline-run-5ncl6
Start Time: 2022-03-31 23:24:10+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2022-03-31 23:24:13+00:00
8 seconds

:heavy_check_mark:
set-env
2022-03-31 23:24:25+00:00
7 seconds

:heavy_check_mark:
checkout
2022-03-31 23:24:38+00:00
21 seconds

:heavy_check_mark:
get-bundle-path
2022-03-31 23:25:02+00:00
9 seconds

:heavy_check_mark:
bundle-path-validation
2022-03-31 23:25:16+00:00
13 seconds

:heavy_check_mark:
content-hash
2022-03-31 23:25:34+00:00
14 seconds

:heavy_check_mark:
certification-project-check
2022-03-31 23:25:34+00:00
a minute

:heavy_check_mark:
inspect-image
2022-03-31 23:25:35+00:00
21 seconds

:heavy_check_mark:
get-supported-versions
2022-03-31 23:25:35+00:00
14 seconds

:heavy_check_mark:
get-organization
2022-03-31 23:26:53+00:00
26 seconds

:heavy_check_mark:
create-support-link-for-pr
2022-03-31 23:26:54+00:00
7 seconds

:heavy_check_mark:
get-cert-project-related-data
2022-03-31 23:27:22+00:00
20 seconds

:heavy_check_mark:
get-vendor-related-data
2022-03-31 23:27:43+00:00
9 seconds

:heavy_check_mark:
publish-to-ocp-registry
2022-03-31 23:27:55+00:00
8 seconds

:heavy_check_mark:
trigger-marketplace-replication
2022-03-31 23:28:05+00:00
14 seconds

:heavy_check_mark:
create-container-image
2022-03-31 23:28:05+00:00
17 seconds

:heavy_check_mark:
publish-bundle
2022-03-31 23:28:28+00:00
6 seconds

:heavy_check_mark:
request-signature
2022-03-31 23:28:38+00:00
33 seconds

:heavy_check_mark:
upload-signature
2022-03-31 23:29:13+00:00
19 seconds

:x:
publish-resources
2022-03-31 23:29:37+00:00
11 seconds

There were some errors in your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

View your certification test results and logs here.

There were errors while publishing your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-release-pipeline
PipelineRun: operator-release-pipeline-run-962ng
Start Time: 2022-03-31 23:44:01+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2022-03-31 23:44:02+00:00
7 seconds

:heavy_check_mark:
set-env
2022-03-31 23:44:12+00:00
8 seconds

:heavy_check_mark:
checkout
2022-03-31 23:44:22+00:00
20 seconds

:heavy_check_mark:
get-bundle-path
2022-03-31 23:44:44+00:00
7 seconds

:heavy_check_mark:
bundle-path-validation
2022-03-31 23:44:53+00:00
17 seconds

:heavy_check_mark:
inspect-image
2022-03-31 23:45:12+00:00
25 seconds

:heavy_check_mark:
get-supported-versions
2022-03-31 23:45:12+00:00
12 seconds

:heavy_check_mark:
content-hash
2022-03-31 23:45:12+00:00
10 seconds

:heavy_check_mark:
certification-project-check
2022-03-31 23:45:12+00:00
41 seconds

:heavy_check_mark:
create-support-link-for-pr
2022-03-31 23:45:55+00:00
7 seconds

:heavy_check_mark:
get-organization
2022-03-31 23:45:55+00:00
9 seconds

:heavy_check_mark:
get-cert-project-related-data
2022-03-31 23:46:06+00:00
33 seconds

:heavy_check_mark:
get-vendor-related-data
2022-03-31 23:46:40+00:00
8 seconds

:heavy_check_mark:
publish-to-ocp-registry
2022-03-31 23:46:49+00:00
9 seconds

:heavy_check_mark:
trigger-marketplace-replication
2022-03-31 23:47:00+00:00
12 seconds

:heavy_check_mark:
create-container-image
2022-03-31 23:47:00+00:00
19 seconds

:heavy_check_mark:
publish-bundle
2022-03-31 23:47:19+00:00
8 seconds

:heavy_check_mark:
request-signature
2022-03-31 23:47:28+00:00
21 seconds

:heavy_check_mark:
upload-signature
2022-03-31 23:47:49+00:00
11 seconds

:x:
publish-resources
2022-03-31 23:48:02+00:00
10 seconds

There were errors while publishing your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-release-pipeline
PipelineRun: operator-release-pipeline-run-fzvkf
Start Time: 2022-04-14 06:12:32+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2022-04-14 06:12:33+00:00
9 seconds

:heavy_check_mark:
set-env
2022-04-14 06:12:43+00:00
9 seconds

:heavy_check_mark:
checkout
2022-04-14 06:12:54+00:00
20 seconds

:heavy_check_mark:
get-bundle-path
2022-04-14 06:13:17+00:00
8 seconds

:heavy_check_mark:
bundle-path-validation
2022-04-14 06:13:27+00:00
17 seconds

:heavy_check_mark:
content-hash
2022-04-14 06:13:46+00:00
27 seconds

:heavy_check_mark:
certification-project-check
2022-04-14 06:13:46+00:00
26 seconds

:heavy_check_mark:
inspect-image
2022-04-14 06:13:47+00:00
24 seconds

:heavy_check_mark:
get-supported-versions
2022-04-14 06:13:47+00:00
28 seconds

:heavy_check_mark:
create-support-link-for-pr
2022-04-14 06:14:14+00:00
10 seconds

:heavy_check_mark:
get-organization
2022-04-14 06:14:14+00:00
11 seconds

:x:
get-cert-project-related-data
2022-04-14 06:14:28+00:00
21 seconds

There were errors while publishing your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-release-pipeline
PipelineRun: operator-release-pipeline-run-s2dt9
Start Time: 2022-04-14 06:18:01+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2022-04-14 06:18:02+00:00
8 seconds

:heavy_check_mark:
set-env
2022-04-14 06:18:12+00:00
8 seconds

:heavy_check_mark:
checkout
2022-04-14 06:18:21+00:00
23 seconds

:heavy_check_mark:
get-bundle-path
2022-04-14 06:18:45+00:00
8 seconds

:heavy_check_mark:
bundle-path-validation
2022-04-14 06:18:56+00:00
26 seconds

:heavy_check_mark:
certification-project-check
2022-04-14 06:19:24+00:00
10 seconds

:heavy_check_mark:
content-hash
2022-04-14 06:19:24+00:00
10 seconds

:heavy_check_mark:
get-supported-versions
2022-04-14 06:19:24+00:00
a minute

:heavy_check_mark:
inspect-image
2022-04-14 06:19:24+00:00
28 seconds

:heavy_check_mark:
create-support-link-for-pr
2022-04-14 06:19:36+00:00
8 seconds

:heavy_check_mark:
get-organization
2022-04-14 06:19:37+00:00
26 seconds

:heavy_check_mark:
get-cert-project-related-data
2022-04-14 06:20:05+00:00
34 seconds

:heavy_check_mark:
get-vendor-related-data
2022-04-14 06:20:41+00:00
8 seconds

:heavy_check_mark:
publish-to-ocp-registry
2022-04-14 06:20:51+00:00
10 seconds

:heavy_check_mark:
trigger-marketplace-replication
2022-04-14 06:21:02+00:00
13 seconds

:heavy_check_mark:
create-container-image
2022-04-14 06:21:02+00:00
15 seconds

:x:
publish-bundle
2022-04-14 06:21:18+00:00
a minute

There were errors while publishing your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-release-pipeline
PipelineRun: operator-release-pipeline-run-mh5vb
Start Time: 2022-04-14 06:02:07+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2022-04-14 06:02:08+00:00
9 seconds

:heavy_check_mark:
set-env
2022-04-14 06:02:19+00:00
7 seconds

:heavy_check_mark:
checkout
2022-04-14 06:02:27+00:00
31 seconds

:heavy_check_mark:
get-bundle-path
2022-04-14 06:03:00+00:00
8 seconds

:heavy_check_mark:
bundle-path-validation
2022-04-14 06:03:10+00:00
14 seconds

:heavy_check_mark:
inspect-image
2022-04-14 06:03:26+00:00
25 seconds

:heavy_check_mark:
content-hash
2022-04-14 06:03:26+00:00
19 seconds

:heavy_check_mark:
get-supported-versions
2022-04-14 06:03:26+00:00
26 seconds

:heavy_check_mark:
certification-project-check
2022-04-14 06:03:26+00:00
17 seconds

:heavy_check_mark:
get-organization
2022-04-14 06:03:45+00:00
16 seconds

:heavy_check_mark:
create-support-link-for-pr
2022-04-14 06:03:45+00:00
15 seconds

:heavy_check_mark:
get-cert-project-related-data
2022-04-14 06:04:04+00:00
24 seconds

:heavy_check_mark:
get-vendor-related-data
2022-04-14 06:04:29+00:00
8 seconds

:heavy_check_mark:
publish-to-ocp-registry
2022-04-14 06:04:39+00:00
12 seconds

:heavy_check_mark:
trigger-marketplace-replication
2022-04-14 06:04:52+00:00
15 seconds

:heavy_check_mark:
create-container-image
2022-04-14 06:04:52+00:00
14 seconds

:heavy_check_mark:
publish-bundle
2022-04-14 06:05:09+00:00
7 seconds

:heavy_check_mark:
get-manifest-list-digests
2022-04-14 06:05:18+00:00
8 seconds

:x:
publish-resources
2022-04-14 06:05:18+00:00
13 seconds

:x:
request-signature
2022-04-14 06:05:26+00:00
20 minutes

There were errors while publishing your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-release-pipeline
PipelineRun: operator-release-pipeline-run-smr4l
Start Time: 2022-04-14 06:27:48+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2022-04-14 06:27:48+00:00
8 seconds

:heavy_check_mark:
set-env
2022-04-14 06:27:58+00:00
10 seconds

:heavy_check_mark:
checkout
2022-04-14 06:28:11+00:00
31 seconds

:heavy_check_mark:
get-bundle-path
2022-04-14 06:28:45+00:00
7 seconds

:heavy_check_mark:
bundle-path-validation
2022-04-14 06:28:54+00:00
13 seconds

:heavy_check_mark:
certification-project-check
2022-04-14 06:29:10+00:00
21 seconds

:heavy_check_mark:
content-hash
2022-04-14 06:29:10+00:00
17 seconds

:heavy_check_mark:
get-supported-versions
2022-04-14 06:29:10+00:00
20 seconds

:heavy_check_mark:
inspect-image
2022-04-14 06:29:10+00:00
24 seconds

:heavy_check_mark:
create-support-link-for-pr
2022-04-14 06:29:33+00:00
8 seconds

:heavy_check_mark:
get-organization
2022-04-14 06:29:33+00:00
10 seconds

:heavy_check_mark:
get-cert-project-related-data
2022-04-14 06:29:45+00:00
26 seconds

:heavy_check_mark:
get-vendor-related-data
2022-04-14 06:30:13+00:00
8 seconds

:heavy_check_mark:
publish-to-ocp-registry
2022-04-14 06:30:24+00:00
9 seconds

:heavy_check_mark:
trigger-marketplace-replication
2022-04-14 06:30:34+00:00
13 seconds

:heavy_check_mark:
create-container-image
2022-04-14 06:30:34+00:00
13 seconds

:x:
publish-bundle
2022-04-14 06:30:48+00:00
a minute

There were errors while publishing your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-release-pipeline
PipelineRun: operator-release-pipeline-run-mbq64
Start Time: 2022-04-14 06:37:25+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2022-04-14 06:37:26+00:00
8 seconds

:heavy_check_mark:
set-env
2022-04-14 06:37:36+00:00
7 seconds

:heavy_check_mark:
checkout
2022-04-14 06:37:46+00:00
23 seconds

:heavy_check_mark:
get-bundle-path
2022-04-14 06:38:11+00:00
8 seconds

:heavy_check_mark:
bundle-path-validation
2022-04-14 06:38:21+00:00
18 seconds

:heavy_check_mark:
content-hash
2022-04-14 06:38:41+00:00
10 seconds

:heavy_check_mark:
get-supported-versions
2022-04-14 06:38:41+00:00
11 seconds

:heavy_check_mark:
certification-project-check
2022-04-14 06:38:41+00:00
12 seconds

:heavy_check_mark:
inspect-image
2022-04-14 06:38:42+00:00
24 seconds

:heavy_check_mark:
create-support-link-for-pr
2022-04-14 06:38:55+00:00
8 seconds

:heavy_check_mark:
get-organization
2022-04-14 06:38:56+00:00
9 seconds

:heavy_check_mark:
get-cert-project-related-data
2022-04-14 06:39:07+00:00
21 seconds

:heavy_check_mark:
get-vendor-related-data
2022-04-14 06:39:30+00:00
13 seconds

:heavy_check_mark:
publish-to-ocp-registry
2022-04-14 06:39:45+00:00
12 seconds

:heavy_check_mark:
trigger-marketplace-replication
2022-04-14 06:39:58+00:00
27 seconds

:heavy_check_mark:
create-container-image
2022-04-14 06:39:59+00:00
25 seconds

:x:
publish-bundle
2022-04-14 06:40:27+00:00
a minute

There were errors while publishing your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-release-pipeline
PipelineRun: operator-release-pipeline-run-s4vcm
Start Time: 2022-04-18 21:50:52+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2022-04-18 21:50:53+00:00
8 seconds

:heavy_check_mark:
set-env
2022-04-18 21:51:03+00:00
8 seconds

:heavy_check_mark:
checkout
2022-04-18 21:51:13+00:00
23 seconds

:heavy_check_mark:
get-bundle-path
2022-04-18 21:51:38+00:00
7 seconds

:heavy_check_mark:
bundle-path-validation
2022-04-18 21:51:46+00:00
18 seconds

:heavy_check_mark:
content-hash
2022-04-18 21:52:06+00:00
10 seconds

:heavy_check_mark:
certification-project-check
2022-04-18 21:52:06+00:00
15 seconds

:heavy_check_mark:
get-supported-versions
2022-04-18 21:52:07+00:00
15 seconds

:heavy_check_mark:
inspect-image
2022-04-18 21:52:07+00:00
21 seconds

:heavy_check_mark:
create-support-link-for-pr
2022-04-18 21:52:24+00:00
9 seconds

:heavy_check_mark:
get-organization
2022-04-18 21:52:25+00:00
24 seconds

:heavy_check_mark:
get-cert-project-related-data
2022-04-18 21:52:51+00:00
25 seconds

:heavy_check_mark:
get-vendor-related-data
2022-04-18 21:53:17+00:00
10 seconds

:heavy_check_mark:
publish-to-ocp-registry
2022-04-18 21:53:30+00:00
11 seconds

:heavy_check_mark:
trigger-marketplace-replication
2022-04-18 21:53:42+00:00
14 seconds

:heavy_check_mark:
create-container-image
2022-04-18 21:53:42+00:00
14 seconds

:x:
publish-bundle
2022-04-18 21:53:58+00:00
2 minutes

View your certification test results and logs here.

There were some errors in your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-run-z4wxx
Start Time: 2022-07-01 18:22:21+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2022-07-01 18:22:21+00:00
7 seconds

:heavy_check_mark:
set-env
2022-07-01 18:22:31+00:00
6 seconds

:heavy_check_mark:
checkout
2022-07-01 18:22:40+00:00
20 seconds

:heavy_check_mark:
validate-pr-title
2022-07-01 18:23:04+00:00
7 seconds

:heavy_check_mark:
get-bundle-path
2022-07-01 18:23:14+00:00
6 seconds

:heavy_check_mark:
bundle-path-validation
2022-07-01 18:23:24+00:00
19 seconds

:heavy_check_mark:
certification-project-check
2022-07-01 18:23:45+00:00
18 seconds

:heavy_check_mark:
content-hash
2022-07-01 18:23:46+00:00
a minute

:heavy_check_mark:
get-organization
2022-07-01 18:24:07+00:00
50 seconds

:x:
get-cert-project-related-data
2022-07-01 18:24:07+00:00
19 seconds

:heavy_check_mark:
create-support-link-for-pr
2022-07-01 18:24:07+00:00
6 seconds

Troubleshooting
Please refer to the troubleshooting guide.

There were some errors in your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

View your certification test results and logs here.

Pipeline Summary
Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-run-vwc9d
Start Time: 2022-07-01 18:37:30+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2022-07-01 18:37:32+00:00
7 seconds

:heavy_check_mark:
set-env
2022-07-01 18:37:44+00:00
7 seconds

:heavy_check_mark:
checkout
2022-07-01 18:37:56+00:00
22 seconds

:heavy_check_mark:
validate-pr-title
2022-07-01 18:38:22+00:00
6 seconds

:heavy_check_mark:
get-bundle-path
2022-07-01 18:38:31+00:00
5 seconds

:heavy_check_mark:
bundle-path-validation
2022-07-01 18:38:40+00:00
12 seconds

:heavy_check_mark:
content-hash
2022-07-01 18:38:54+00:00
16 seconds

:heavy_check_mark:
certification-project-check
2022-07-01 18:38:55+00:00
36 seconds

:heavy_check_mark:
get-organization
2022-07-01 18:39:33+00:00
11 seconds

:heavy_check_mark:
create-support-link-for-pr
2022-07-01 18:39:33+00:00
8 seconds

:x:
get-cert-project-related-data
2022-07-01 18:39:35+00:00
28 seconds

:heavy_check_mark:
annotations-validation
2022-07-01 18:39:46+00:00
45 seconds

Troubleshooting
Please refer to the troubleshooting guide.

There were some errors in your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

View your certification test results and logs here.

Pipeline Summary
Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-run-rs96w
Start Time: 2022-07-01 18:57:28+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2022-07-01 18:57:30+00:00
7 seconds

:heavy_check_mark:
set-env
2022-07-01 18:57:39+00:00
7 seconds

:heavy_check_mark:
checkout
2022-07-01 18:57:49+00:00
17 seconds

:heavy_check_mark:
validate-pr-title
2022-07-01 18:58:10+00:00
7 seconds

:heavy_check_mark:
get-bundle-path
2022-07-01 18:58:21+00:00
6 seconds

:heavy_check_mark:
bundle-path-validation
2022-07-01 18:58:30+00:00
15 seconds

:heavy_check_mark:
certification-project-check
2022-07-01 18:58:49+00:00
18 seconds

:heavy_check_mark:
content-hash
2022-07-01 18:58:49+00:00
a minute

:heavy_check_mark:
get-organization
2022-07-01 18:59:09+00:00
19 seconds

:heavy_check_mark:
create-support-link-for-pr
2022-07-01 18:59:09+00:00
7 seconds

:x:
get-cert-project-related-data
2022-07-01 18:59:10+00:00
a minute

:heavy_check_mark:
annotations-validation
2022-07-01 18:59:31+00:00
17 seconds

Troubleshooting
Please refer to the troubleshooting guide.

There were some errors in your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

View your certification test results and logs here.

Pipeline Summary
Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-run-fkltw
Start Time: 2022-07-01 19:20:02+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2022-07-01 19:20:03+00:00
7 seconds

:heavy_check_mark:
set-env
2022-07-01 19:20:13+00:00
6 seconds

:heavy_check_mark:
checkout
2022-07-01 19:20:22+00:00
18 seconds

:heavy_check_mark:
validate-pr-title
2022-07-01 19:20:43+00:00
7 seconds

:heavy_check_mark:
get-bundle-path
2022-07-01 19:20:53+00:00
6 seconds

:heavy_check_mark:
bundle-path-validation
2022-07-01 19:21:01+00:00
13 seconds

:heavy_check_mark:
content-hash
2022-07-01 19:21:17+00:00
a minute

:heavy_check_mark:
certification-project-check
2022-07-01 19:21:17+00:00
16 seconds

:heavy_check_mark:
create-support-link-for-pr
2022-07-01 19:21:36+00:00
6 seconds

:heavy_check_mark:
get-organization
2022-07-01 19:21:36+00:00
17 seconds

:heavy_check_mark:
get-cert-project-related-data
2022-07-01 19:21:37+00:00
58 seconds

:heavy_check_mark:
annotations-validation
2022-07-01 19:21:55+00:00
18 seconds

:heavy_check_mark:
submission-validation
2022-07-01 19:22:38+00:00
17 seconds

:heavy_check_mark:
verify-project-distribution
2022-07-01 19:22:38+00:00
7 seconds

:heavy_check_mark:
merge-registry-credentials
2022-07-01 19:22:38+00:00
19 seconds

:heavy_check_mark:
update-cert-project-status
2022-07-01 19:22:58+00:00
7 seconds

:heavy_check_mark:
reserve-operator-name
2022-07-01 19:23:07+00:00
8 seconds

:heavy_check_mark:
get-supported-versions
2022-07-01 19:23:17+00:00
40 seconds

:heavy_check_mark:
yaml-lint
2022-07-01 19:23:17+00:00
20 seconds

:heavy_check_mark:
digest-pinning
2022-07-01 19:23:18+00:00
42 seconds

:x:
verify-changed-directories
2022-07-01 19:23:18+00:00
6 seconds

Troubleshooting
Please refer to the troubleshooting guide.

View your certification test results and logs here.

There were some errors in your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-run-zglml
Start Time: 2022-07-01 20:33:19+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2022-07-01 20:33:20+00:00
7 seconds

:heavy_check_mark:
set-env
2022-07-01 20:33:30+00:00
7 seconds

:heavy_check_mark:
checkout
2022-07-01 20:33:39+00:00
18 seconds

:heavy_check_mark:
validate-pr-title
2022-07-01 20:34:01+00:00
5 seconds

:heavy_check_mark:
get-bundle-path
2022-07-01 20:34:09+00:00
6 seconds

:heavy_check_mark:
bundle-path-validation
2022-07-01 20:34:18+00:00
15 seconds

:heavy_check_mark:
certification-project-check
2022-07-01 20:34:35+00:00
17 seconds

:heavy_check_mark:
content-hash
2022-07-01 20:34:35+00:00
a minute

:heavy_check_mark:
create-support-link-for-pr
2022-07-01 20:34:55+00:00
6 seconds

:heavy_check_mark:
get-organization
2022-07-01 20:34:55+00:00
18 seconds

:heavy_check_mark:
get-cert-project-related-data
2022-07-01 20:34:56+00:00
59 seconds

:heavy_check_mark:
annotations-validation
2022-07-01 20:35:15+00:00
10 seconds

:heavy_check_mark:
verify-project-distribution
2022-07-01 20:35:57+00:00
7 seconds

:heavy_check_mark:
merge-registry-credentials
2022-07-01 20:35:57+00:00
31 seconds

:heavy_check_mark:
submission-validation
2022-07-01 20:35:58+00:00
28 seconds

:heavy_check_mark:
update-cert-project-status
2022-07-01 20:36:29+00:00
7 seconds

:heavy_check_mark:
reserve-operator-name
2022-07-01 20:36:38+00:00
9 seconds

:heavy_check_mark:
get-supported-versions
2022-07-01 20:36:49+00:00
18 seconds

:heavy_check_mark:
yaml-lint
2022-07-01 20:36:49+00:00
47 seconds

:heavy_check_mark:
digest-pinning
2022-07-01 20:36:50+00:00
20 seconds

:heavy_check_mark:
verify-changed-directories
2022-07-01 20:36:50+00:00
8 seconds

:heavy_check_mark:
verify-pinned-digest
2022-07-01 20:37:12+00:00
7 seconds

:heavy_check_mark:
dockerfile-creation
2022-07-01 20:37:38+00:00
24 seconds

:x:
build-bundle
2022-07-01 20:38:04+00:00
23 seconds

Troubleshooting
Please refer to the troubleshooting guide.

There were some errors in your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

View your certification test results and logs here.

Pipeline Summary
Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-run-lvwsb
Start Time: 2022-07-08 20:47:17+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2022-07-08 20:47:17+00:00
8 seconds

:heavy_check_mark:
set-env
2022-07-08 20:47:29+00:00
7 seconds

:heavy_check_mark:
checkout
2022-07-08 20:47:39+00:00
17 seconds

:heavy_check_mark:
validate-pr-title
2022-07-08 20:48:00+00:00
6 seconds

:heavy_check_mark:
get-bundle-path
2022-07-08 20:48:08+00:00
8 seconds

:heavy_check_mark:
bundle-path-validation
2022-07-08 20:48:19+00:00
14 seconds

:heavy_check_mark:
certification-project-check
2022-07-08 20:48:35+00:00
49 seconds

:heavy_check_mark:
content-hash
2022-07-08 20:48:35+00:00
20 seconds

:heavy_check_mark:
create-support-link-for-pr
2022-07-08 20:49:27+00:00
8 seconds

:heavy_check_mark:
get-organization
2022-07-08 20:49:27+00:00
27 seconds

:heavy_check_mark:
get-cert-project-related-data
2022-07-08 20:49:29+00:00
48 seconds

:heavy_check_mark:
annotations-validation
2022-07-08 20:49:57+00:00
a minute

:heavy_check_mark:
submission-validation
2022-07-08 20:50:19+00:00
15 seconds

:heavy_check_mark:
verify-project-distribution
2022-07-08 20:50:19+00:00
7 seconds

:heavy_check_mark:
merge-registry-credentials
2022-07-08 20:50:19+00:00
25 seconds

:heavy_check_mark:
update-cert-project-status
2022-07-08 20:50:37+00:00
7 seconds

:heavy_check_mark:
reserve-operator-name
2022-07-08 20:51:08+00:00
8 seconds

:heavy_check_mark:
get-supported-versions
2022-07-08 20:51:17+00:00
13 seconds

:heavy_check_mark:
yaml-lint
2022-07-08 20:51:17+00:00
8 seconds

:heavy_check_mark:
digest-pinning
2022-07-08 20:51:18+00:00
41 seconds

:heavy_check_mark:
verify-changed-directories
2022-07-08 20:51:18+00:00
5 seconds

:heavy_check_mark:
verify-pinned-digest
2022-07-08 20:52:01+00:00
6 seconds

:heavy_check_mark:
dockerfile-creation
2022-07-08 20:52:09+00:00
19 seconds

:x:
build-bundle
2022-07-08 20:52:30+00:00
31 seconds

Troubleshooting
Please refer to the troubleshooting guide.

There were errors while publishing your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

There were errors while publishing your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

 You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-release-pipeline
PipelineRun: operator-release-pipeline-run-fm6rc
Start Time: 2022-10-07 21:11:37+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2022-10-07 21:11:38+00:00
9 seconds

:heavy_check_mark:
set-env
2022-10-07 21:11:50+00:00
19 seconds

:heavy_check_mark:
checkout
2022-10-07 21:12:12+00:00
17 seconds

:heavy_check_mark:
get-bundle-path
2022-10-07 21:12:35+00:00
8 seconds

:heavy_check_mark:
bundle-path-validation
2022-10-07 21:12:49+00:00
11 seconds

:heavy_check_mark:
content-hash
2022-10-07 21:13:06+00:00
13 seconds

:heavy_check_mark:
certification-project-check
2022-10-07 21:13:06+00:00
14 seconds

:heavy_check_mark:
inspect-image
2022-10-07 21:13:07+00:00
19 seconds

:heavy_check_mark:
get-supported-versions
2022-10-07 21:13:07+00:00
13 seconds

:heavy_check_mark:
create-support-link-for-pr
2022-10-07 21:13:25+00:00
7 seconds

:heavy_check_mark:
get-organization
2022-10-07 21:13:26+00:00
13 seconds

:x:
get-cert-project-related-data
2022-10-07 21:13:44+00:00
8 minutes

There were errors while publishing your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-release-pipeline
PipelineRun: operator-release-pipeline-run-p2lkv
Start Time: 2022-10-13 21:52:37+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2022-10-13 21:52:38+00:00
6 seconds

:heavy_check_mark:
set-env
2022-10-13 21:52:47+00:00
6 seconds

:heavy_check_mark:
checkout
2022-10-13 21:52:55+00:00
15 seconds

:heavy_check_mark:
get-bundle-path
2022-10-13 21:53:12+00:00
6 seconds

:heavy_check_mark:
bundle-path-validation
2022-10-13 21:53:21+00:00
16 seconds

:heavy_check_mark:
certification-project-check
2022-10-13 21:53:39+00:00
49 seconds

:heavy_check_mark:
content-hash
2022-10-13 21:53:39+00:00
20 seconds

:heavy_check_mark:
get-supported-versions
2022-10-13 21:53:39+00:00
20 seconds

:heavy_check_mark:
inspect-image
2022-10-13 21:53:40+00:00
23 seconds

:heavy_check_mark:
get-organization
2022-10-13 21:54:30+00:00
24 seconds

:heavy_check_mark:
create-support-link-for-pr
2022-10-13 21:54:30+00:00
6 seconds

:x:
get-cert-project-related-data
2022-10-13 21:54:55+00:00
8 minutes

There were errors while publishing your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-release-pipeline
PipelineRun: operator-release-pipeline-run-ncc7p
Start Time: 2022-10-13 22:06:55+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2022-10-13 22:06:56+00:00
6 seconds

:heavy_check_mark:
set-env
2022-10-13 22:07:04+00:00
8 seconds

:heavy_check_mark:
checkout
2022-10-13 22:07:15+00:00
23 seconds

:heavy_check_mark:
get-bundle-path
2022-10-13 22:07:39+00:00
8 seconds

:heavy_check_mark:
bundle-path-validation
2022-10-13 22:07:50+00:00
17 seconds

:heavy_check_mark:
content-hash
2022-10-13 22:08:08+00:00
8 seconds

:heavy_check_mark:
certification-project-check
2022-10-13 22:08:08+00:00
10 seconds

:heavy_check_mark:
inspect-image
2022-10-13 22:08:09+00:00
24 seconds

:heavy_check_mark:
get-supported-versions
2022-10-13 22:08:09+00:00
12 seconds

:heavy_check_mark:
create-support-link-for-pr
2022-10-13 22:08:19+00:00
7 seconds

:heavy_check_mark:
get-organization
2022-10-13 22:08:19+00:00
8 seconds

:x:
get-cert-project-related-data
2022-10-13 22:08:29+00:00
8 minutes

There were errors while publishing your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-release-pipeline
PipelineRun: operator-release-pipeline-run-xlsr2
Start Time: 2022-10-13 22:29:14+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2022-10-13 22:29:14+00:00
7 seconds

:heavy_check_mark:
set-env
2022-10-13 22:29:22+00:00
8 seconds

:heavy_check_mark:
checkout
2022-10-13 22:29:32+00:00
17 seconds

:heavy_check_mark:
get-bundle-path
2022-10-13 22:29:51+00:00
7 seconds

:heavy_check_mark:
bundle-path-validation
2022-10-13 22:30:00+00:00
16 seconds

:heavy_check_mark:
content-hash
2022-10-13 22:30:18+00:00
26 seconds

:heavy_check_mark:
certification-project-check
2022-10-13 22:30:18+00:00
27 seconds

:heavy_check_mark:
get-supported-versions
2022-10-13 22:30:18+00:00
29 seconds

:heavy_check_mark:
inspect-image
2022-10-13 22:30:19+00:00
20 seconds

:heavy_check_mark:
create-support-link-for-pr
2022-10-13 22:30:47+00:00
7 seconds

:heavy_check_mark:
get-organization
2022-10-13 22:30:47+00:00
9 seconds

:heavy_check_mark:
get-cert-project-related-data
2022-10-13 22:30:57+00:00
19 seconds

:heavy_check_mark:
get-vendor-related-data
2022-10-13 22:31:18+00:00
8 seconds

:x:
copy-bundle-image-to-released-registry
2022-10-13 22:31:27+00:00
7 seconds

There were errors while publishing your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-release-pipeline
PipelineRun: operator-release-pipeline-run-v2gtq
Start Time: 2022-10-13 22:38:12+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2022-10-13 22:38:13+00:00
6 seconds

:heavy_check_mark:
set-env
2022-10-13 22:38:22+00:00
7 seconds

:heavy_check_mark:
checkout
2022-10-13 22:38:31+00:00
17 seconds

:heavy_check_mark:
get-bundle-path
2022-10-13 22:38:50+00:00
5 seconds

:heavy_check_mark:
bundle-path-validation
2022-10-13 22:38:57+00:00
18 seconds

:heavy_check_mark:
content-hash
2022-10-13 22:39:16+00:00
11 seconds

:heavy_check_mark:
certification-project-check
2022-10-13 22:39:16+00:00
13 seconds

:heavy_check_mark:
inspect-image
2022-10-13 22:39:17+00:00
25 seconds

:heavy_check_mark:
get-supported-versions
2022-10-13 22:39:17+00:00
12 seconds

:heavy_check_mark:
create-support-link-for-pr
2022-10-13 22:39:31+00:00
6 seconds

:heavy_check_mark:
get-organization
2022-10-13 22:39:31+00:00
14 seconds

:heavy_check_mark:
get-cert-project-related-data
2022-10-13 22:39:47+00:00
20 seconds

:heavy_check_mark:
get-vendor-related-data
2022-10-13 22:40:09+00:00
8 seconds

:x:
copy-bundle-image-to-released-registry
2022-10-13 22:40:17+00:00
8 seconds

There were errors while publishing your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-release-pipeline
PipelineRun: operator-release-pipeline-run-9zwdk
Start Time: 2022-10-13 22:49:21+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2022-10-13 22:49:22+00:00
7 seconds

:heavy_check_mark:
set-env
2022-10-13 22:49:32+00:00
6 seconds

:heavy_check_mark:
checkout
2022-10-13 22:49:41+00:00
22 seconds

:heavy_check_mark:
get-bundle-path
2022-10-13 22:50:05+00:00
6 seconds

:heavy_check_mark:
bundle-path-validation
2022-10-13 22:50:13+00:00
15 seconds

:heavy_check_mark:
content-hash
2022-10-13 22:50:29+00:00
11 seconds

:heavy_check_mark:
certification-project-check
2022-10-13 22:50:29+00:00
11 seconds

:heavy_check_mark:
inspect-image
2022-10-13 22:50:30+00:00
26 seconds

:heavy_check_mark:
get-supported-versions
2022-10-13 22:50:30+00:00
13 seconds

:heavy_check_mark:
create-support-link-for-pr
2022-10-13 22:50:41+00:00
7 seconds

:heavy_check_mark:
get-organization
2022-10-13 22:50:41+00:00
27 seconds

:heavy_check_mark:
get-cert-project-related-data
2022-10-13 22:51:09+00:00
23 seconds

:heavy_check_mark:
get-vendor-related-data
2022-10-13 22:51:33+00:00
9 seconds

:x:
copy-bundle-image-to-released-registry
2022-10-13 22:51:42+00:00
6 seconds

There were errors while publishing your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-release-pipeline
PipelineRun: operator-release-pipeline-run-5cmtn
Start Time: 2022-10-13 23:06:37+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2022-10-13 23:06:37+00:00
7 seconds

:heavy_check_mark:
set-env
2022-10-13 23:06:47+00:00
7 seconds

:heavy_check_mark:
checkout
2022-10-13 23:06:57+00:00
16 seconds

:heavy_check_mark:
get-bundle-path
2022-10-13 23:07:15+00:00
7 seconds

:heavy_check_mark:
bundle-path-validation
2022-10-13 23:07:24+00:00
19 seconds

:heavy_check_mark:
content-hash
2022-10-13 23:07:45+00:00
16 seconds

:heavy_check_mark:
certification-project-check
2022-10-13 23:07:45+00:00
17 seconds

:heavy_check_mark:
get-supported-versions
2022-10-13 23:07:45+00:00
30 seconds

:heavy_check_mark:
inspect-image
2022-10-13 23:07:46+00:00
19 seconds

:heavy_check_mark:
create-support-link-for-pr
2022-10-13 23:08:03+00:00
8 seconds

:heavy_check_mark:
get-organization
2022-10-13 23:08:03+00:00
8 seconds

:heavy_check_mark:
get-cert-project-related-data
2022-10-13 23:08:12+00:00
20 seconds

:heavy_check_mark:
get-vendor-related-data
2022-10-13 23:08:32+00:00
9 seconds

:x:
copy-bundle-image-to-released-registry
2022-10-13 23:08:41+00:00
11 seconds

There were errors while publishing your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-release-pipeline
PipelineRun: operator-release-pipeline-run-x64ld
Start Time: 2022-10-13 23:14:03+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2022-10-13 23:14:03+00:00
8 seconds

:heavy_check_mark:
set-env
2022-10-13 23:14:13+00:00
8 seconds

:heavy_check_mark:
checkout
2022-10-13 23:14:24+00:00
17 seconds

:heavy_check_mark:
get-bundle-path
2022-10-13 23:14:43+00:00
8 seconds

:heavy_check_mark:
bundle-path-validation
2022-10-13 23:14:52+00:00
18 seconds

:heavy_check_mark:
content-hash
2022-10-13 23:15:11+00:00
19 seconds

:heavy_check_mark:
certification-project-check
2022-10-13 23:15:11+00:00
19 seconds

:heavy_check_mark:
inspect-image
2022-10-13 23:15:12+00:00
19 seconds

:heavy_check_mark:
get-supported-versions
2022-10-13 23:15:12+00:00
20 seconds

:heavy_check_mark:
create-support-link-for-pr
2022-10-13 23:15:31+00:00
7 seconds

:heavy_check_mark:
get-organization
2022-10-13 23:15:31+00:00
9 seconds

:heavy_check_mark:
get-cert-project-related-data
2022-10-13 23:15:42+00:00
17 seconds

:heavy_check_mark:
get-vendor-related-data
2022-10-13 23:16:01+00:00
8 seconds

:x:
copy-bundle-image-to-released-registry
2022-10-13 23:16:10+00:00
9 seconds

There were errors while publishing your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-release-pipeline
PipelineRun: operator-release-pipeline-run-2v2dr
Start Time: 2022-10-13 23:20:17+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2022-10-13 23:20:18+00:00
7 seconds

:heavy_check_mark:
set-env
2022-10-13 23:20:28+00:00
7 seconds

:heavy_check_mark:
checkout
2022-10-13 23:20:38+00:00
20 seconds

:heavy_check_mark:
get-bundle-path
2022-10-13 23:21:01+00:00
7 seconds

:heavy_check_mark:
bundle-path-validation
2022-10-13 23:21:09+00:00
17 seconds

:heavy_check_mark:
content-hash
2022-10-13 23:21:28+00:00
19 seconds

:heavy_check_mark:
certification-project-check
2022-10-13 23:21:28+00:00
21 seconds

:heavy_check_mark:
inspect-image
2022-10-13 23:21:29+00:00
22 seconds

:heavy_check_mark:
get-supported-versions
2022-10-13 23:21:29+00:00
21 seconds

:heavy_check_mark:
create-support-link-for-pr
2022-10-13 23:21:50+00:00
8 seconds

:heavy_check_mark:
get-organization
2022-10-13 23:21:50+00:00
10 seconds

:heavy_check_mark:
get-cert-project-related-data
2022-10-13 23:22:02+00:00
19 seconds

:heavy_check_mark:
get-vendor-related-data
2022-10-13 23:22:22+00:00
10 seconds

:x:
copy-bundle-image-to-released-registry
2022-10-13 23:22:32+00:00
9 seconds

There were errors while publishing your Operator bundle. You can use this support case to contact the Red Hat certification team for review.

Pipeline Summary
Pipeline: operator-release-pipeline
PipelineRun: operator-release-pipeline-run-vkqd6
Start Time: 2022-10-13 23:24:31+00:00
Tasks

Status
Task
Start Time
Duration

:heavy_check_mark:
set-github-status-pending
2022-10-13 23:24:32+00:00
7 seconds

:heavy_check_mark:
set-env
2022-10-13 23:24:41+00:00
7 seconds

:heavy_check_mark:
checkout
2022-10-13 23:24:51+00:00
23 seconds

:heavy_check_mark:
get-bundle-path
2022-10-13 23:25:16+00:00
7 seconds

:heavy_check_mark:
bundle-path-validation
2022-10-13 23:25:24+00:00
17 seconds

:heavy_check_mark:
get-supported-versions
2022-10-13 23:25:43+00:00
22 seconds

:heavy_check_mark:
content-hash
2022-10-13 23:25:43+00:00
20 seconds

:heavy_check_mark:
certification-project-check
2022-10-13 23:25:43+00:00
21 seconds

:heavy_check_mark:
inspect-image
2022-10-13 23:25:44+00:00
23 seconds

:heavy_check_mark:
get-organization
2022-10-13 23:26:05+00:00
9 seconds

:heavy_check_mark:
create-support-link-for-pr
2022-10-13 23:26:05+00:00
7 seconds

:heavy_check_mark:
get-cert-project-related-data
2022-10-13 23:26:15+00:00
19 seconds

:heavy_check_mark:
get-vendor-related-data
2022-10-13 23:26:36+00:00
7 seconds

:heavy_check_mark:
copy-bundle-image-to-released-registry
2022-10-13 23:26:43+00:00
9 seconds

:heavy_check_mark:
set-cert-project-repository
2022-10-13 23:26:53+00:00
8 seconds

:heavy_check_mark:
create-container-image
2022-10-13 23:27:01+00:00
17 seconds

:x:
publish-resources
2022-10-13 23:27:18+00:00
13 seconds


Fix aHelp relay to detect AFK Admins

About the PR
Gave Admins a separate 5min AFK timer and if someone send an aHelp and they are AFK it will send in the relay as a SOS instead of looking like the admin has seen it. Thank you @nikthechampiongr for this better idea than to kick everyone 😄
Why / Balance
I have made this be cause I went AFK for several rounds and a bunch of aHelps were missed but to the relay they looked ok.
Technical details
Add admin detection condition to the afk detection and update the bwoink system discord relay message to take in to account if the admin is AFK or not.
Media
Admin online/Not AFK

Admin online/AFK detected

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes
NA
Changelog
:cl: Repo

tweak: AFK admins will trigger the SOS in aHelp relay.

If someone could tell me how to make this only show on the admin changelog you will get 100 points.

Should do 10min. We do a lot of AFKing sometimes until we hear the bwoink.

I hit the wrong button. :)

If someone could tell me how to make this only show on the admin changelog you will get 100 points.

I would like my 100 points please.
🆑 Repo
ADMIN:

tweak: AFK admins will trigger the SOS in aHelp relay.

I hit the wrong button. :)

10min now.

@Titian3 Looking at the usages of GetTargetAdmins, it is also used to notify online admins for new ahelps. Did you test what afk admins see or hear when an ahelp is made while they are afk? A lot of admins have the game minimized and wait for the bwoink sound.

The changes to the GetTargetAdmins function make all ahelps completely invisible to afk admins. Maybe you should have a separate function for this?

Yes you are right, when I first tested it, I think I saw the red aHelp from the first message, making the new function and testing now.
🙏Thank you! 200 points have been deposited in your account!

The changes to the GetTargetAdmins function make all ahelps completely invisible to afk admins. Maybe you should have a separate function for this?

Re-tested, all looks working right now.


Fixed Module name

Removed "Module" postfix on module name, this prevented the module from being mounted properly in a build version of the plugin.

Thank you!


I got into trouble using this lib in android.

My code is same as the demo code, and iOS is running alright.

I am sorry, this is a problem of RN.
https://github.com/facebook/react-native/issues/21754

Cool man.
发自我的 iPhone

在 2018年12月3日，下午4:02，DeJavuJo<EMAIL_ADDRESS>写道：
I am sorry, this is a problem of RN.
facebook/react-native#21754
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


KAFKA-16565: IncrementalAssignmentConsumerEventHandler throws error when attempting to remove a partition that isn't assigned

Checking that the TopicPartition is in assignment before attempting to remove it.
Also added some logging and refactoring.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Do I understand it correctly that there is no functional change here, just logging?


Link the form to the google sheets

Link the form created in the #33  issue to a google sheets API. Try using this

Refer this.


support more limiter algorithm

Now we have supported RateLimit. but we still need to config it. so if we have many different types of machines, we will config more version configure. it is too hard to complete. It is more sad story that if we support VPA, the performance of the machine can be changed, this config will be unavailable after the change. so we need adaptive limiters like BBR and so on. we need to implement the ratelimit interface to replace with ratelimit.

/assign


tour: Rename Abs() to Sqrt()

Context: https://tour.golang.org/methods/1
It seems that the Abs() function should be renamed to Sqrt()

That looks intentional. In the next few pages Abs is defined on different values. It returns an absolute value. For a vector it uses Sqrt to implement Abs.

https://en.wikipedia.org/wiki/Absolute_value#Vector_spaces


Error 400 -> cognitive-services-speech-sdk/quickstart/javascript/node/from-blob/

Hy.
I'm using the from-blob.js code in cognitive-services-speech-sdk/quickstart/javascript/node/from-blob/ and it returns me a error 400.
What's is a error 400 in this case? Can help me please??

I have the same question!

There is an error in the sample. Please remove the backtick (`) in this line of the sample. The sample will be updated shortly.

closing as issue identified and we are updating the sample


Minor UI issues fixed

Get MD Access to public names and its services
Show loading while publishing template
Handle filter to disable/enable buttons
Other minor UI issue fixed

r? @ustulation
(maidsafe_highfive has picked a reviewer for you, use r? to override)


Numbers - Detection

The number in the log is partially getting considered as number
The results do not mask the data completely
To Reproduce
Steps to reproduce the behavior:

In the log, please add a log with a 16 digit number<PHONE_NUMBER>463111
Example -<PHONE_NUMBER>463111
Run Stringlifier
In the output, it shows 49291

Hi @vimalathithanr ,
Thank you for signalling this bug. I've just created a quick fix and will be releasing the package to include this (<IP_ADDRESS>).
In [4]: s("Example -<PHONE_NUMBER>463111", return_tokens=True)
Out[4]: (['Example - <NUMERIC>'], [[('4929193454463111', 10, 25, '<NUMERIC>')]])

Thank you for your quick response and fix, @tiberiu44!

Hi @tiberiu44, I tried executing and I faced a different issue this time.
Input -<PHONE_NUMBER>987654321
Output - ['1234567890987654321'] [[]]
Am I missing something?

I just tried it. I confirm the issue is still present. It's harder to solve than anticipated, because numbers can be part of random strings, GUIDs and other special sequences. This must be solved through model training. I hope the fix for package versions will also solve this one.

Thank you, Tiberiu for your quick response! We are excited to use this open-source library on our logging services. Please let me know when the fix is available.

I think I got it working. Here are some outputs:
In [5]: s('test 2313241')
Out[5]: ['test <NUMERIC>']

In [7]: s('test 10.2.3')
Out[7]: ['test 10.2.3']

In [8]: s("Example -<PHONE_NUMBER>463111", return_tokens=True)
Out[8]: (['Example - <NUMERIC>'], [[('4929193454463111', 10, 25, '<NUMERIC>')]])

In [9]: s('1234567890987654321')
Out[9]: ['<NUMERIC>']

In [10]: s('MongoDB v4.4.2')
Out[10]: ['MongoDB v4.4.2']

In [11]: s('MongoDB v124.432.212')
Out[11]: ['MongoDB v<NUMERIC>']

In [14]: s("com.docker.hyperkit -A -u -F vms/0/hyperkit.pid -c 8 -m 8192M -b <IP_ADDRESS> --pass=\"NlcXVpYWRvcg\" -s 0:0,hostbridge -s 31,lpc -s 1:0,virtio-vpnkit,path=vpnkit.eth.sock,uuid=45172425-08d1-41ec-9d13-437481803412 -U c6fb5010-a83e-4f74-9a5a-50d9086b9 -jwt=eyJ0eXAiOiJKV1QiL
    ...: CJhbGciOiJIUzI1NiJ9.eyJpZCI6IjAuMDc5MDExMTgxNTAzNjY0NDgiLCJjbGllbnRfaWQiOiIwLjM3MjUyMTgyMzI3MDYwMDU3IiwidXNlcl9pZCI6InByb191c2VyIiwidHlwZSI6ImFjY2Vzc190b2tlbiIsImV4cGlyZXNfaW4iOiIzNjAwMDAwIiwic2NvcGUiOiJyZWFkLCB3cml0ZSIsImNyZWF0ZWRfYXQiOiIxNjAxOTIxNjc5MzE4In0.Dh6q3iiwk-mF-
    ...: gNCoOSpsJUSvpo5X2qEaw1wZX-6WYY")
Out[14]: ['com.docker.hyperkit -A -u -F vms/0/hyperkit.pid -c 8 -m 8192M -b <IP_ADDR> --pass="<RANDOM_STRING>" -s 0:0,hostbridge -s 31,lpc -s 1:0,virtio-vpnkit,path=vpnkit.eth.sock,uuid=<UUID> -U <UUID> -jwt=<JWT>']

One note: by default stringlifier will never replace strings that have less than 6 characters with detected tokens. We cannot change that, because it would break some of the use-cases. However, you can now pass this as the cutoff parameter on the method call:
In [5]: s('test 123')
Out[5]: ['test 123']

In [6]: s('test 123', cutoff=1)
Out[6]: ['test <RANDOM_STRING>']

However, it is really hard to actually classify short strings as being random or not, so lowering this cutoff could potentially break the results.
Releasing the new package version now, but I will keep training the model for a couple of days.

Thank you, @tiberiu44 for the fix! I have tested the latest version and things are looking good.


[BEAM-10961] enable strict dependency checking for sdks/java/io/tika

Split from #13688
R: @ibzib

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run Java PreCommit


Add code for Microsoft.Azure.Services.AppAuthentication library

Description

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] I have read the contribution guidelines.
[x] The pull request does not introduce breaking changes.

General Guidelines

[x] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[x] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

@varunsh-msft would be really great if you can clean up your commits. if you can rebase/squash that will be really great.
I am reviewing your changes from your fork. Will keep updating this PR.


Perf improvements

Fixes #9
Converts the chunk-by-chunk passing of blocks to IPLD to be done in parallel instead using pull-paramap.
You can limit the concurrency in pull-paramap - I wasn't sure which value to use so I did a comparison using this test which uses pull-buffer-stream to generate streams of buffers of random bytes:
it('massive', function (done) {
  this.timeout(600000000)

  const size = 500000000
  let read = 0
  let lastDate = Date.now()
  let lastPercent = 0

  options.progress = (bufSize) => {
    read += bufSize

    const percent = parseInt((read / size) * 100)

    if (percent > lastPercent) {
      console.info(`${Date.now() - lastDate}`)

      lastDate = Date.now()
      lastPercent = percent
    }
  }

  pull(
    values([{
      path: '200Bytes.txt',
      content: bufferStream(size, {
        chunkSize: 256000
      })
    }]),
    importer(ipld, options),
    onEnd((err) => {
      expect(err).to.not.exist()
      done()
    })
  )
})

The results were (lower is better):

So there's a slight overhead with 100x concurrency, but unbounded is about the same as 50x on my laptop so in this PR I leave it unbounded.
This is only 0-20% of the file being added.  I was interested by the jump so left it running in unbounded parallel mode to see if there were any other bottlenecks:

The line is reasonably straight, so at least it's constant and that's ok, right?  Wrong.  Each value on the x axis is 1%, but the y axis is how long it took to ingest that 1% so it's getting slower over time.
Adding a file to IPFS is basically going at O(n log n) time which is kind of bad for large files.
What's causing this?  Turns out using pull-stream/throughs/map to calculate file ingest progress is causing this, and it allocates a new buffer for the file chunk to boot, so slow and memory inefficient.
Switching that out for a pull-stream/throughs/through results in the following graph:

Or about 2300x faster.
Writing the file chunks in series results in:

Or about 2200x faster.

In real-world use, this changed the time it takes to jsipfs add a 260MB file to a fresh repo from 13.7s to 1.95s.  By comparisongo-ipfs takes 1.58s to add the same file to a fresh repo.

Wow, this is really amazing! Really great analysis.

wow! :D

I'm trying to dig deeper into what is the actual bit of work that was getting repeated or backed up here.  Fundamentally I don't believe it.  I've seen it with my own eyes but I still don't believe it.

I was expecting something like this. You might see some more improvement once https://github.com/ipfs/js-datastore-fs/pull/21 lands. We should likely do a call to understand what is happening and why.

The only significant difference I can see in the pull stream code between through and map is that map has a try/catch.

Wow, this is absolutely fantastic!!! Amazing work @achingbrain!! 👏🏽👏🏽👏🏽

@achingbrain would you be down record a 5 minute screencast (maybe even just 2) to share with the community? Also, would love to have a session on how you approach this performance problems and generate these graphs so that everyone can learn from it.


Fixing some types and adjusting the wording (a bit).

1. Why is this change necessary?
To fix typos in the docs and make the reading experience a bit more pleasing.
2. What does this change do, exactly?
Change typos and wording in the Storefront docs.
3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
5. Checklist

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

There are plenty of cases where the docs speak about the "Storefront", but the writing is mixed between lowercase and uppercase. Could you clarify that please? I found many more minor errors in the Storefront section of the docs and would like to fix them.
Thank you!

Hi @mikewink,
thanks for helping out with the documentation.
When talking about the "Storefront" in general it should be uppercase. It should only be lowercase when the docs talk about technical things like the app/storefront directory. So your fixes look fine to me. 👍
Best regards
Tobias

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

I have imported your pull request and it should be merged soon.
Thanks for your contribution. 🎉


Expose password utilites

Has some functionality for rotating passwords and ensuring that passwords confirm to some simple rules (e.g., must have certain types of characters or limited character sets).
Should expose those features since they are hidden internally.

Currently have functionality for following rules, needs the ability to rotate the password


Stars are Wrong

Hello,
I have the current code:
<View style={{ alignItems:'center' }} >                     <Stars                         value={1}                         spacing={8}                         count={5}                         starSize={40}                         backingColor='transparent'                         fullStar={require('../../images/fullstar.png')}                         emptyStar={require('../../images/emptystar.png')}                         halfStar={require('../../images/halfstar.png')}                     />                 </View>             </View>
but when I have a value of 1, it shows 2 stars. Same happens for any values put in

Hi, I will take a look at this soon.
Thanks,
Austin
On Thu, Jun 29, 2017 at 12:49 eyalabadi98<EMAIL_ADDRESS>wrote:

Hello,
I have the current code:
<View style={{ alignItems:'center' }} > <Stars value={1} spacing={8}
count={5} starSize={40} backingColor='transparent'
fullStar={require('../../images/fullstar.png')}
emptyStar={require('../../images/emptystar.png')}
halfStar={require('../../images/halfstar.png')} />
but when I have a value of 1, it shows 2 stars. Same happens for any
values put in
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Extrct/react-native-stars/issues/1, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AJiM7D38AQgkYU2lRvhLapJvnQWN3irJks5sI9WjgaJpZM4OJlY1
.

So I just tested and it seems like there is a core issue with the module's behavior after recent RN changes. I'll try to fix the issue within the week, however if the changes are more fundamental to the module's image layering strategy then it will take significantly more time to fix.

The issue is that when using the module in default display mode (passing a value prop and not setting the opacity flag) the backgroundColor prop cannot be transparent.  Apologies if this conflicts with your intended use of the component, but for now this is the hacky way the module is set up. Eventually I intend to introduce a more legitimate way of processing partial images using svgs so this will no longer be a constraint.


Image from JPG file not working correctly

When using image() to plot a JPG file, the colors aren't matching. Also, the color bar is being showed by default, and in this case there's no point on showing a color bar.
C = imread('ngc6543a.jpg');
image(C)

fig2plotly(gcf, 'offline', false);

The previous code prints the following warning message:
Unrecognized field name "DisplayName".
We had trouble parsing the image object.
This trace might not render properly.

Expected and generated (https://chart-studio.plotly.com/~xarico10/859/#/) plots:

Examples un using image() can be found on:
https://www.mathworks.com/help/matlab/ref/image.html#responsive_offcanvas

This issue has been fixed by this commit: https://github.com/plotly/plotly_matlab/commit/59481e8885d17e6795fd447f5d9005fb48feadc3

I have recognised that the same issue might happen in updateArea and updatePatch and I have created a fix here: https://github.com/plotly/plotly_matlab/pull/326

PR #331 fix this issue


md-select position change in fixed top header

Bug, feature request, or proposal:
I set md-select at top of the page as position fixed
It is working fine at default position
when i scroll my page and click md-menu it open in another position (out of my page)
What is the expected behavior?
Is there any position i have to define ...?
What is the current behavior?
What are the steps to reproduce?
Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: https://goo.gl/DlHd6U
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, browsers are affected?
Is there anything else we should know?

Can you please replicate in a plunker? And have you included a theme? (often a cause of menu position errors)

Yeah, it sounds like you may be missing our core styles / theme. Without a plunker, it's hard for us to look into this. Can you double-check that you've included a theme, and if you have and still think it's a Material bug, please open a new issue with a plunker repro.


Persisted connection...

Hi,
May I apologise in advance for any lack of understanding.
I created a connection to the cache and successfully received a PING response from the ping_check() coroutine in this call (see below)
awaitable Cache_session::connect_() noexcept {
    auto result = false;
    auto executor = co_await this_coro::executor;

    try {

        config cfg;
        cfg.addr.host = get_environment_variable(cache_host_address);
        cfg.addr.port = get_environment_variable(cache_host_port);
        cfg.health_check_interval = std::chrono::seconds{stoi(get_environment_variable(cache_health_check_interval))};
        cache_ptr_ = std::make_shared<boost::redis::connection>(executor);
        cache_ptr_->async_run(cfg, {boost::redis::logger::level::crit}, consign(detached, cache_ptr_));
        result = co_await co_spawn(executor, ping_check(), use_awaitable);
        /*
        result = co_await co_spawn(executor, key_value_checks(), use_awaitable);
        result = co_await co_spawn(executor, hash_checks(), use_awaitable);
        result = co_await co_spawn(executor, set_checks(), use_awaitable);
        result = true;
        */

    } catch (std::exception& e) {

        handle_exception(boost::log::v2_mt_posix::trivial::fatal, e.what());
    }

    co_return result;
}

awaitable Cache_session::ping_check() noexcept {
    auto result = false;

    try {

        request req;
        req.push("PING", cache_ping_message);
        response<std::string> resp;
        co_await cache_ptr_->async_exec(req, resp, use_awaitable);
        if (cache_ping_message != std::get<0>(resp).value()) {

            handle_exception(boost::log::v2_mt_posix::trivial::fatal, cache_ping_check_failed);

        }

        result = true;

    } catch (const std::exception& e) {

        handle_exception(boost::log::v2_mt_posix::trivial::fatal, e.what());
    }

    co_return result;
}

I then make the same call to ping_check() coroutine from another part of the code using :
          result = co_await co_spawn(executor,
                                   cache_session_ptr_->ping_check(),
                                   use_awaitable);

On the second call I get a segmentation fault at the line:

        co_await cache_ptr_->async_exec(req, resp, use_awaitable);

Where it was previously successful.

Can you suggest where there is a gap in my understanding as to why the second call is unsuccessful ? - thanks!

Can you share some code so I can investigate? Also, notice the connection class has built it health-checks so in gneral you don't have to perform pings manually.

This is the call which encapsulates the issue...
awaitable Server::connect_to_cache() noexcept {
    auto result = false;
    auto executor = co_await this_coro::executor;

    try {

        cache_session_ptr_ = std::make_shared<Cache_session>();
        result = co_await co_spawn(executor,
                                   cache_session_ptr_->connect_(),
                                   use_awaitable);

        result = co_await co_spawn(executor,
                                   cache_session_ptr_->ping_check(),
                                   use_awaitable);

        if (!result)
            handle_exception(boost::log::v2_mt_posix::trivial::fatal,
                             cache_connection_failed);

        co_spawn(executor, audit(severity_level::info,
                                 cache_connection_succeeded), detached);

        result = true;

    } catch (std::exception& e) {

        handle_exception(boost::log::v2_mt_posix::trivial::fatal, e.what());
    }

    co_return result;
}

Within the first call to cache_session_ptr_->connect() the call to ping_check() works (I was just using PING to verify there were no issues interacting with the interface and would remove it later) - in the call thereafter it does not - is it possible that the executor that was used in std::make_sharedboost::redis::connection(executor) has gone out of scope?

Hi - please let me know if you need any further info (a snippet of code for a "long-lived" connection would be of great help)

Within the first call to cache_session_ptr_->connect() the call to ping_check() works (I was just using PING to verify there were no issues interacting with the interface and would remove it later) - in the call thereafter it does not -

Unless you have disabled reconnection, the function async_run should be called only once in your program. Also, you should not call it again before the previous call has completed. If you want to wait for it to complete replace net::detached with net::use_awaitable for example.
If that does not work, please send a minimal example with which I can reproduce the problem.

Did my comment above helped you any further, can we close the issue?

Hi - yes it did - please go ahead and close the issue - thanks!


Work on software requirements

@lee-matthews  I know you've put in a lot of work into this. Can you add a link here? What remains to be done?  Thanks.

question: should https://github.com/innolitics/rdm be brought in as a submodule

@neelfirst no.  it isn't required for the repo.  It should be setup as a python requirement for anyone who intends to modify the documents or make a release

We have migrated SW reqs to Valispace and people have definitely worked on them.


Uncaught TypeError: Cannot read property 'then' of undefined

When trying to split a tab with ensime open, I get the error.
~/.atom/packages/Ensime/lib/features/implicits.coffee:57
TypeError: Cannot read property 'then' of undefined
    at Implicits.showImplicits (~/.atom/packages/Ensime/lib/features/implicits.coffee:57:63)
    at Implicits.handleSetting (~/.atom/packages/Ensime/lib/features/implicits.coffee:11:8)
    at ~/.atom/packages/Ensime/lib/features/implicits.coffee:7:93
    at Config.module.exports.Config.observeKeyPath (/Applications/Atom.app/Contents/Resources/app.asar/src/config.js:616:7)
    at Config.module.exports.Config.observe (/Applications/Atom.app/Contents/Resources/app.asar/src/config.js:141:21)
    at new Implicits (~/.atom/packages/Ensime/lib/features/implicits.coffee:7:34)
    at ~/.atom/packages/Ensime/lib/ensime.coffee:102:91
    at /Applications/Atom.app/Contents/Resources/app.asar/src/workspace.js:334:16
    at Function.module.exports.Emitter.simpleDispatch (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:25:14)
    at Emitter.module.exports.Emitter.emit (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:129:28)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/workspace.js:265:34
    at Function.module.exports.Emitter.simpleDispatch (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:25:14)
    at Emitter.module.exports.Emitter.emit (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:129:28)
    at PaneContainer.module.exports.PaneContainer.addedPaneItem (/Applications/Atom.app/Contents/Resources/app.asar/src/pane-container.js:390:27)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/pane-container.js:368:19
    at /Applications/Atom.app/Contents/Resources/app.asar/src/pane-container.js:95:16
    at Function.module.exports.Emitter.simpleDispatch (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:25:14)
    at Emitter.module.exports.Emitter.emit (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:129:28)
    at PaneContainer.module.exports.PaneContainer.didAddPane (/Applications/Atom.app/Contents/Resources/app.asar/src/pane-container.js:308:27)
    at Pane.module.exports.Pane.setContainer (/Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:131:26)
    at PaneAxis.module.exports.PaneAxis.addChild (/Applications/Atom.app/Contents/Resources/app.asar/src/pane-axis.js:145:13)
    at PaneAxis.module.exports.PaneAxis.insertChildAfter (/Applications/Atom.app/Contents/Resources/app.asar/src/pane-axis.js:216:19)
    at Pane.module.exports.Pane.split (/Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:923:23)
    at Pane.module.exports.Pane.splitRight (/Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:884:19)
    at atom-tabs.TabBarView.splitTab (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/tabs/lib/tab-bar-view.js:376:31)
    at Object.addElementCommands.tabs:split-right (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/tabs/lib/tab-bar-view.js:140:26)
    at atom-tabs.commandsWithPropagationStopped.(anonymous function) (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/tabs/lib/tab-bar-view.js:86:36)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:259:29)
    at CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:59)
    at CommandRegistry.module.exports.CommandRegistry.dispatch (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:160:19)
    at AtomEnvironment.module.exports.AtomEnvironment.dispatchContextMenuCommand (/Applications/Atom.app/Contents/Resources/app.asar/src/atom-environment.js:1181:28)
    at EventEmitter.outerCallback (/Applications/Atom.app/Contents/Resources/app.asar/src/application-delegate.js:332:25)
    at emitThree (events.js:116:13)
    at EventEmitter.emit (events.js:194:7)

Sorry for late response. Do you still have this issue? I'm unable to reproduce :(

I've actually moved off of ensime because I can't get it to work reliably for my project.  I'm sure this is something with my setup that I haven't had time to debug yet, so I'll close this issue for now.  When I get time to work on getting ensime working again, I'll check this to see if it is still a problem.
Thanks

I have the same issue