Restart of OMRS stack - not rejoining cohort

Hi,
I can bring up the OMRS stack in a repository server and the repository connector registers with the cohort. If I then deactivate the OMRS stack in that server, adjust the configuration (e.g. specify a different topic root) and restart the OMRS stack, it is not allowed to re-register.
I get the following audit message:
myserver OMRS-AUDIT-0006 Configuration error detected while connecting to cohort CoCoCohort1, error message was: OMRS-COHORT-REGISTRY-400-002 The Open Metadata Repository Cohort CoCoCohort1 is not available to server myserver because the local metadata collection id has been changed from 7c4166a1-1135-4ac1-ab21-090d34e68fdb to e97f61f6-475c-47ab-957a-340401bf450f since this server registered with the cohort. (OMRSAuditLogDestination:94)
My question is this: if the above is a valid scenario (i.e. deactivate, adjust config and reactivate) then am I doing something wrong that is causing the change of metadata collection Id? Should I be preserving the same id across the restarts?
Thanks!

It is valid to be able to disconnect from a cohort, update cohort configuration and reconnect.  However, it needs to be done in a coherent manner.  This error message suggests that the update to the configuration changed the local metadata collection id.  This is not valid if the repository disconnected temporarily (ie permanent=false).
The local metadata collection id is the identifier of the metadata stored in the local repository.  It is assigned when the local repository is first configured and is used in remote repositories to identify the master repository of any reference copies they have stored.  If a repository changes its local metadata collection id in an ad hoc manner then the instances stored in other repositories now have the wrong metadata collection Id stored in their reference copies.   Subsequent updates to these instances will appear to come from a different metadata repository than the master repository which suggests conflicting guids, or some other sort of protocol violation.
This is why the OMRS validates that the local metadata collection id does not change between restarts of the server.   However, all other aspects of the configuration may change between server restarts, including server name.   This is because the repository issues a re-registration request when it reconnects to the cohort.  This allows all of the information about the repository to change except the local metadata collection id since that is the repository's unique identifier in the cohort.
When a repository disconnects permanently, it is saying that the other repositories are no longer going to receive any more metadata from this metadata collection id - the remote repositories get an unregistration event to remove the configuration about the metadata collection from their records.  The other members may choose to leave the reference copies from this metadata collection id in their local repositories or purge them.  The current OMRS behaviour is to leave the reference copies, and let an administrator purge them if requried.
The OMRS logs the local metadata collection id on the audit log on start up.  It is also stored in the local repository's cohort registry store (which is how the OMRS detects an invalid change in local metadata collection id and outputs that audit event reported at the start of this issue).

Many thanks.
I think I must have reset the repository mode by mistake when I tested this before. I checked through the local repository config handling in the initialisation code and have re-tested an activate, deactivate, reactivate sequence, which is working as expected. The metdataCollectionId is maintained between first activation and reactivation, and the repository is functioning correctly following the reactivation.
When the repository rejoined the cohort, there was a REFRESH_REGISTRATION_REQUEST event followed by a RE_REGISTRATION_EVENT from the other server on the cohort.

There's some interesting implications here that I should account for in the k8s setup

if a pod is restarted - this is often because of a temporary failure/crash -- so the server (atlas or egeria) should come up with the same metadata id.
if I have multiple servers they each need their own unique id. I assume this is automatically allocated on initial configuration
I assume the mcid is stored in the *config file - and so this needs to be made persistant in a k8s environment

Finally a question - if it valid to have multiple instances of the omag server with the same mcid. For example if both were referring to the same metadata collection, through for example, using the same backend graph or rdbms store? (this would be the case if one wanted to scale for throughput/redundancy at the omag server level)

The metadata collection id is stored in both the config file and the cohort registry store.  The have to match on rejoining the cohort.  So both the config and the registry store need to be persisted.  Otherwise the other members of the cohort will think this is a new repository and will report logic errors if it sends out updates to instances with a different home id.

Thanks. Will bear that in mind when I add persistence #766


problem when add platform ios

Why does this happen when I add the ios platform?

Run cd platforms/ios && pod install --verbose or cordova platform ios --verbose to get a detailed error as to why pod install failed.
A likely cause is out-of-date local pods repo, so be sure to run pod repo update as outlined in the documentation.
Also try building the example project to rule out possible causes specific to your project such as plugin conflicts.


make error

d/src/kvstore/kvstore.o
In file included from src/kvstore/kvstore.cc:35:0:
src/kvstore/./kvstore_nccl.h:30:18: fatal error: nccl.h: 没有那个文件或目录
compilation terminated.
Makefile:451: recipe for target 'build/src/kvstore/kvstore.o' failed
make: *** [build/src/kvstore/kvstore.o] Error 1
when i try to make it ,this error happened

Please refer to #43

d/src/kvstore/kvstore.o
In file included from src/kvstore/kvstore.cc:35:0:
src/kvstore/./kvstore_nccl.h:30:18: fatal error: nccl.h: 没有那个文件或目录
compilation terminated.
Makefile:451: recipe for target 'build/src/kvstore/kvstore.o' failed
make: *** [build/src/kvstore/kvstore.o] Error 1
when i try to make it ,this error happened

Hello, have you solved this problem? I meet the same, but i don not how to  use docker or singualr

The same error...


Dropdown for agency

Create dynamic drop down that pulls all job types of agencies from USA jobs. This will be a fetch request into  list creation

Working as needed may need UI updates


[Hub Generated] Review request for Microsoft.DataReplication to add version preview/2021-02-16-preview

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
ARM (Control Plane) API Specification Update Pull Request
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!

[x] New API version. (Such PR should have been generated with OpenAPI Hub, per this wiki doc.)
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix swagger quality issues in S360.
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I have reviewed the general guidance on the spec PR review process: https://aka.ms/specprreview.
[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data-plane related specifications.
[x] I commit to follow the Breaking Change Policy.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can request review from an ARM API Review board.

ARM API changes review

If you want for the ARM team to review this PR, you must add the ARMReview label.
The automation may automatically add the ARMReview label, if appropriate.
If this happens, proceed according to guidance given in GitHub comments also added by the automation.

Breaking change review
If you have any breaking changes as defined in the Breaking Change Policy,
follow the process outlined in the High-level Breaking Change Process doc.
Getting help

For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For additional help, see https://aka.ms/azsdk/support/spectools.

he issue link that you created in step 1 in this PR

Link to New RP Namespace Issue: https://github.com/Azure/azure-sdk-pr/issues/1220

@rkmanda I assigned you as @minhsuanlee was asking me for help with LintDiff failures.

For LintDiff errors LroErrorContent and OperationsApiResponseSchema, I have taken necessary steps to locally reproduce the errors but from what I can tell, the cause of the error does not seem to be valid as our schema is already following the guidelines. I even tried copy-paste the schema from types.json to our swagger directly and re-run Lint validation, it still failed.

@mayada83 if you confirm the Swagger LintDiff failure is incorrect, please add the Approved-LintDiff label. If you approve this PR on behalf of the ARM team, please add the ARMSignedOff label. Thank you!

Moving to a new PR [Hub Generated] Review request for Microsoft.DataReplication to add version preview/2021-02-16-preview #24974 as Service Name has been updated from 'azuresiterecovery' to 'recoveryservicesdatareplication'

{

Observed that your new RP is not RPaaS based RP. Non-RPaaS RPs are not allowed, unless you have got an exception. If that's the case, please forward me the RPaaS exception email/communication for your RP.

Refers to: specification/azuresiterecovery/resource-manager/Microsoft.DataReplication/preview/2021-02-16-preview/azuresiterecovery.json:1 in 5ef4eea. [](commit_id = 5ef4eea5b09ea6eb26eb92f4f7a911e20e0e9d46, deletion_comment = False)


configure command backend arg is ignored when env var is set

description will be added soon

According to:
https://docs.bigchaindb.com/projects/server/en/latest/server-reference/configuration.html
The value of each BigchainDB Server configuration setting is determined according to the following rules:

If it’s set by an environment variable, then use that value
Otherwise, if it’s set in a local config file, then use that value
Otherwise, use the default value


Use smoltcp dev temporarily

Temporarily use the development version of smoltcp to provide the Hash trait and fully support the thiserror crate.

Merged. I had hoped that GitHub would be clever enough to mark this as merged instead of closed when synchronizing it with the master branch.


Task/NLU-2697 - 3,000,000 detected as 3 in "es-mx" MS Recognizers library

Just so everyone knows, this bugfix was originally just for amountOfMoney, but Conor has also fixed the issue for number, which is an improvement on what LUIS currently offers

Do we need to bump package versions here? How will these changes be pulled into our service?


242 3.25 use application canceled state

Display buttons in execution phase on events#show and application_letters#show to

cancel accepted applications
accept alternative applications, if enough free places
[WIP] display some fancy icon if applicants were not informed about the latest application status

Coverage remained the same at 100.0% when pulling ce5a29ae757455e2892e9ab24aa2b454cdc77845 on 242_3.25_UseApplicationCanceledState into 8d9c84c1234179bb44c7f0dad39eb632b9aa4e4e on dev.

Coverage remained the same at 100.0% when pulling 2044d8c46ba4351b1d634bbecae0ed67b5d6c257 on 242_3.25_UseApplicationCanceledState into 8d9c84c1234179bb44c7f0dad39eb632b9aa4e4e on dev.

The new change looks good to me as well.

Coverage remained the same at 100.0% when pulling 2803ed678120115088bda192eca3c19356ab5d92 on 242_3.25_UseApplicationCanceledState into 8d9c84c1234179bb44c7f0dad39eb632b9aa4e4e on dev.

Coverage remained the same at 100.0% when pulling 97cd33724932d3dd4a7afa4515ed16b3c12b2cb2 on 242_3.25_UseApplicationCanceledState into ef47b22dfa75fc339b4068e0b9df2b861fe6ebae on dev.

Coverage remained the same at 100.0% when pulling 97cd33724932d3dd4a7afa4515ed16b3c12b2cb2 on 242_3.25_UseApplicationCanceledState into ef47b22dfa75fc339b4068e0b9df2b861fe6ebae on dev.


Adjust OS:Nova:Server to changed security_groups requirements

Since Ocata Release OS::Nova::Server has the following requirements for the optional property security_groups:

security_groups
List of security group names or IDs. Cannot be used if neutron ports are associated with this server; assign security groups to the ports instead.

At least the basic instance needs to be changed accordingly, other occurences of OS:Nova:Server should be checked as well

Correct, please submit a pull request

Is OS::Nova::Server used in any other repo than heat-iaas?


UI issue - width of threshold could be wider

This is not really an "issue" with the rails_autoscale_agent and very minor as well.
We have one worker, which we do not need to scale too quickly, therefore our upscale threshold is 100_000 seconds. And this is not easily visible in the Settings page UI:

Looking through the HTML, I found the attribute size="4" on the input, when this is for example changed to size="7" the number fits (but needs a text-align="right" for smaller numbers I think):

Maybe this is something that can be changed in the Settings UI.

@mobilutz Done. Thanks for the suggestion!

Thanks for the fast change!


Added the parameter to disable camera dragging in some levels

Issue
In some game dev levels when we use camera zoom, mouseClick control activates dragging and that's annoying for players.
Fix
UI system parameter to disable cameraDragging for certain levels.

@AndrewJakubowicz
It's undefined by default already. I didn't add this parameter to the camera, I just added one more point to switch it on.  Plus it get default parameter from UI system which has default parameter


Mixed up encoding of months

Here it is claimed that months are numbered starting by 0.
Here 2 is supposed to mean 'February'.

Fixed, thanks


mybatis调用Oracle存储过程开启事务报错

Ⅰ. Issue Description
mybatis调用Oracle

存储过程开启事务报错
-jdk8

Seata 2.0   spring-cloud-starter-alibaba-seata 2<IP_ADDRESS>
Database version:Oracle11g
Linux

不支持该功能
not support

报错信息expect has not xid, but was:<IP_ADDRESS>:8091:6918058001194657137

Stored procedures or triggers are not supported.


[BUG] fixing lizard's stomach sizes

My first ever PR and it's a webeddit, yay. Can't see this going wrong or just straight out denied.

About the PR
fixes #15108 = lizards having twice the stomach volumes they should

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

Changelog

:cl:

Lizards have found digestion easier as they no longer suffer from x2 size stomachs.

Imo, Lizards would be better balanced with 100u stomach size. Thx.

it was a bug from wrong variable name not balancing


Extraneous asterixs in 'branches' content

In the 2nd paragraph of the Branches section, there are a number of asterisks between words which serve no purpose.  Removing them, the sentence reads correctly.

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

ID: 4e18eead-7795-0752-93b0-e07f6d088089
Version Independent ID: f637de69-b13c-eed8-ab05-3515106c9270
Content: What is Git? - Azure DevOps
Content Source: https://mseng.visualstudio.com/DefaultCollection/TechnicalContent/_git/devops-learn-pr?path=%2fdocs%2fgit%2fwhat-is-git.md&version=GBlive&_a=contents
Service: unspecified
GitHub Login: @samgu
Microsoft Alias: kangan

@DaveDustin Thanks for letting us know, this content was recently migrated over from WordPress and it looks like some formatting errors slipped through, I'll get this fixed up.

@DaveDustin I just checked in the fix and it should be live soon. Thanks for letting us know.


GoHANmem Problem

I wanted to modify the attack in souls sacrifice delta but I always result 0
I do not understand or made a mistake
sorry for my bad English

data type -> 2bytes
try again?

Not all numbers will be EXACT. Im in the process of writing up some tutorials for GoHANmem on my site. Once Rice releases next version that has fuzzy search abilities we can make advanced codes and get around things like this. www.OneHitGamerStudios.com hit the forums. Ive released a bunch of codes for some random games using GoHANmem.


(login): fix image code auth bug

Codecov Report

Merging #17 (100602e) into release-1.0.0 (2fb05a2) will not change coverage.
The diff coverage is 0.00%.

@@               Coverage Diff                @@
##             release-1.0.0      #17   +/-   ##
================================================
  Coverage            24.55%   24.55%
  Complexity             108      108
================================================
  Files                   43       43
  Lines                 1792     1792
  Branches               122      122
================================================
  Hits                   440      440
  Misses                1322     1322
  Partials                30       30

Impacted Files
Coverage Δ
Complexity Δ

...ross/account/service/authcode/AuthCodeManager.java
14.92% <0.00%> (ø)
3.00 <0.00> (ø)

Continue to review full report at Codecov.

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


New version: Aries-Sciences-LLC.AI-Chess version 1.0

Pull request has been created with WinGet Automation 🪟📦🤖
Microsoft Reviewers: Open in CodeFlow

This appears to be 0.0.1 re-released as 1.0.

Hi @vedantmgoyal2009,

This PR's version number "1.0" has 2 parameters (sets of numbers between dots - major, minor, etc), which is less than the current manifest's version 0.0.1, which has 3 parameters.

Is this intentional?
(Automated response - build 586)


why dtype=int32?

SequenceMask, SequenceReverse, and SequenceLast all expect valid_length to be float32. It requires casting to float32. I am not sure how expensive casting is but any reason this is int32? Maybe we can make this an option as well?
https://github.com/dmlc/gluon-nlp/blob/7a10dca33b4e0684eee5198c447afeec22659ea3/gluonnlp/data/batchify/batchify.py#L73

For large input/output space, float32 cannot represent int32 accurately, since float32 has fewer mantissa bits than int32. I think we should extend the sequence operators to more types.

@szha I am actually surprised that sequence operators are acting on float32 in the first place. I am sure there is a reason. But I can't think of one

likely just legacy

Should I create an issue on mxnet?

@whamza15 I created one here: https://github.com/apache/incubator-mxnet/issues/12649

This issue is tracked at upstream.


Update configure-sharepoint-content-source.md

The viva learning content provider menu is moved from admin.microsoft.com in to the admin tab of the Viva Learning app in Teams. Viva learning app in teams also links back to this outdated doc.

Looks good, thanks for the quick feedback

@bhaswatic
PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


How to pass multiple data from excel sheet in our scenarios

Hi @seymen ,
I have a issue where i have multiple data in excel sheet and i want to use that multiple times for the same test case.
Eg:         Name                         Place
value       ABC                           ABC
value       XYZ                            XYZ
With Apache Jmeter i am able to pass everything from a file as comma separated and run the same test multiple times with different test data.
Could you please suggest how can this be done here.

Hi @seymen,
Could you please help us with the above issue.

Hi @animesh-gupta - check out scenario outlines feature of cucumber-js (https://github.com/cucumber/cucumber-js/blob/master/features/scenario_outlines.feature). apickli doesn't provide any additional functionality on top of this.

@animesh-gupta  I have added a s


Points from the List should display an empty View Details window, instead of saying "No Data"

Background
Points that are added to the list using the Map Point tool, by default will not have any "attribute" information to them, but still have a coordinate to display in the title of the View Details window.

For both ArcMap and ArcGIS Pro

Current behavior
If you try to view details for a point that has no "attribute" information to it, it displays a window that say "No data available". This is a.) untrue, as there is a title/coordinate to display from what you clicked, and b.) very unsightly and not what is expected.

Expected behavior

only a mock up, text size and content may change

View Details gives expected message now:
Pro:

ArcMap:

Note: As noted in https://github.com/Esri/coordinate-conversion-addin-dotnet/issues/590#issuecomment-493126056 - the default size is somewhat large - in Pro if you resize the window, close, and reopen, the last window size is used, but not in ArcMap (so the large size is more of an issue in ArcMap)

ArcMap 10.4.1

updated to CC june release topic
updated MT june release topic

https://solutionsdev.arcgis.com/defense/help/coordinate-conversion/resources/june-2019-coordinate-conversion.htm
\...\DefenseSolutions\CoordinateConversion\Dev\140\
https://solutionsdev.arcgis.com/defense/help/military-tools/resources/june-2019-military-tools-for-arcgis.htm
\...\DefenseSolutions\MilitaryToolsforArcGIS\Dev\309\

Doc verified on CC 143, MT 314, solutionsstg


Ember Client retry reset connection and broken pipe errors

This is a follow up for #4935 and #5286. To sum it up, there are more IO exceptions from which we can recover and retry idempotent requests.
While the particular conditions I'm trying to observe here are very well-defined within the TCP layer, the various IO syscalls and the Java IO API make it impossible to observe those conditions with any precision. I also don't want to blindly match against any IOException because that may catch non-retryable IO errors like connect exceptions, unresolved hosts, etc. We may be able to enumerate those out but it seems risky
So, we have to resort to match against exception messages instead. Unsurprisingly, there is precedent for doing this:

https://github.com/AsyncHttpClient/async-http-client/blob/master/client/src/main/java/org/asynchttpclient/netty/future/StackTraceInspector.java
https://github.com/reactor/reactor-netty/blob/058159592584fcc3a66c32b48a5bfe6a8fe09297/reactor-netty-core/src/main/java/reactor/netty/channel/AbortedException.java#L46

I'm pretty sure Okhttp is doing something similar but not sure where to look in their codebase. I'm also not sure how much of these condition matches we should port over, but I think it's a good start and we can expand as user reports come in.
Alternatives: some HTTP clients try reading before writing to a socket to see if the connection has closed already. This lowers the probability of getting a reset/broken pipe, but it's also not bulletproof because network shenanigans.

Also, I've figured out how I want to write tests for these things so I'll open up another follow up later

Desired behavior


Destroying toruses

Closes #95

FYI the StreamPlayer in Board is temporary, so that we can check whether destruction works properly. Has to be replaced by proper function call before merging. TODO decide how we want to structure the calls, whether we call destroy on piece, tile or what.

TODO draw diagram of tcp handshake-like flow of what info is passed where when making move


drivers/timers:Arch_alarm and arch_timer add up_ndelay interface

Summary
Arch_alarm and arch_timer add up_ndelay interface
Impact
no impact
Testing
ostest

[Experimental Bot, please feedback here]
No, this PR does not meet the NuttX requirements.
Missing Information:

Summary:

Lacks a clear explanation of why the change is necessary (fix, update, new feature).
Needs more detail on how the change works (what will change and how).  "Add up_ndelay interface" is too vague.  Explain what this interface does and how it is used.

Impact:

While you state "no impact,"  adding a new interface almost certainly has some impact.  Consider:

Documentation: Does this new interface need to be documented?
Compatibility: Does this addition affect backward compatibility in any way?

Testing:

"ostest" is not sufficient. Please provide:

Specific build host details (OS, CPU, compiler version).
Target details (architecture, board, configuration).
Relevant testing logs that demonstrate the functionality before and after the change.  Don't just dump entire logs – highlight the important parts.

Recommendations:

Expand the Summary:  Clearly state the purpose of adding the up_ndelay interface. Explain what problem it solves or what functionality it adds.
Review the Impact: Carefully consider all potential impacts. Even small changes can have ripple effects.
Provide Detailed Testing Information:  Be specific about your testing environment and provide relevant logs that demonstrate the change's effect.

By addressing these points, you will make your PR much stronger and easier for the NuttX maintainers to review.


set interface mtu based on lwaftr v4/v6 mtu

Fix for https://github.com/Igalia/snabb/issues/487
It calculates the MTU for the interface based on the ipv4_mtu and ipv6_mtu, by taking the numerically larger one and add 14 to cover the size of the ethernet header. The change will also print out the mtu to STDOUT together with the interface name.
Fixing README files for snabbvmx ipv4_interface and ipv6_interface settings.

Thanks marcel. One addition Please. If mtu is not configured under soft wire it shall be derived from interface mtu please.
Thanks
Christian
Von meinem Windows Phone gesendet

Von: Marcel<EMAIL_ADDRESS>Gesendet: 15.10.2016 07:25
An<EMAIL_ADDRESS>Betreff: [Igalia/snabb] set interface mtu based on lwaftr v4/v6 mtu (#488)
Fix for #487https://github.com/Igalia/snabb/issues/487
It calculates the MTU for the interface based on the ipv4_mtu and ipv6_mtu, by taking the numerically larger one and add 14 to cover the size of the ethernet header. The change will also print out the mtu to STDOUT together with the interface name.
Fixing README files for snabbvmx ipv4_interface and ipv6_interface settings.

You can view, comment on, or merge this pull request online at:
https://github.com/Igalia/snabb/pull/488
Commit Summary

set interface mtu based on lwaftr v4/v6 mtu

File Changes

M src/program/snabbvmx/README.mdhttps://github.com/Igalia/snabb/pull/488/files#diff-0 (11)
M src/program/snabbvmx/lwaftr/READMEhttps://github.com/Igalia/snabb/pull/488/files#diff-1 (6)
M src/program/snabbvmx/lwaftr/lwaftr.luahttps://github.com/Igalia/snabb/pull/488/files#diff-2 (9)
M src/program/snabbvmx/lwaftr/setup.luahttps://github.com/Igalia/snabb/pull/488/files#diff-3 (10)

Patch Links:

https://github.com/Igalia/snabb/pull/488.patch
https://github.com/Igalia/snabb/pull/488.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/Igalia/snabb/pull/488, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AU_G6lOIAUM-FqGCHgE8xEvd6PIYaccsks5q0GPegaJpZM4KXngU.

@chrgraf: There is no mtu other than the tunnel-payload-mtu and tunnel-path-mru, both are mandatory. If no br-instance is configured, then I set the MTU to DEFAULT_MTU = 9500, which is used in transparent mode, so all packets will be sent to the vMX 0/0/x interface, where the MTU from the vMX will be applied.

Hi Marcel,
I have meant the [edit interfaces] mtu or even better by issuing a operational command show interface ge000 | match mtu.
Having two places to configure mtu (edit interface and edit softwire] does create unnecessary conflicts.
Ideally if the [edit softwire] has no mtu configured it would be good if it would be derived from the ge000 mtu.
Many thanks
Christian
Von meinem Windows Phone gesendet

Von: Marcel<EMAIL_ADDRESS>Gesendet: 15.10.2016 09:54
An<EMAIL_ADDRESS>Cc: Christian<EMAIL_ADDRESS><EMAIL_ADDRESS>Betreff: Re: [Igalia/snabb] set interface mtu based on lwaftr v4/v6 mtu (#488)
@chrgrafhttps://github.com/chrgraf: There is no mtu other than the tunnel-payload-mtu and tunnel-path-mru, both are mandatory. If no br-instance is configured, then I set the MTU to DEFAULT_MTU = 9500, which is used in transparent mode, so all packets will be sent to the vMX 0/0/x interface, where the MTU from the vMX will be applied.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Igalia/snabb/pull/488#issuecomment-253969428, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AU_G6v1v7SmAI4jy3OcWBlPwKAyoWlmkks5q0IbHgaJpZM4KXngU.

@chrgraf: Don't want to mix the configs of the 'micro VNF' snabbvmx with the config of the vMX. Remember that subscriber packets never reach the vMX, so the MTU must be configured by the br-instance. I also can't make the [xe|ge]-0/0/x mtu the only MTU, because the ietf-softwire I-D made the mtu and mru settings mandatory. In addition, Junos allows setting the IFD and IFF MTU seperately, which will make it complicated to derive it.
Bottom line, IMHO the straight forward method is to derive the interface (L2) MTU for snabb 10GE from the softwire mtu/mru settings.

Hi Marcel,
Thanks for this explanation - its the way to go.
Christian

Christian Graf
Senior Consulting Engineer
Telephone +49 5651/336174
Mobile +49 175/2929 167
<EMAIL_ADDRESS>www.juniper.net
Juniper Networks GmbH
Sitz der Gesellschaft / Registered office: Oskar-Schlemmer-Str. 15, 80807 München
Registergericht / Commercial registry: München, HRB 205571
Geschäftsführer / Directors: Johannes Albers, Stephen Byrne, Terrance Floyd Spidell

This email contains material that is confidential. The content of this email is for the sole use of the intended recipient(s).
Any review or distribution by persons other than the intended recipient(s) without the express permission of Juniper Networks is strictly prohibited.
If you are not the intended recipient, please contact the sender and delete/destroy all copies of this email and any related attachments.
Juniper does not guarantee the accuracy or completeness of third party materials or information

From: Marcel Wiget <notifications<EMAIL_ADDRESS>Reply-To: Igalia/snabb <reply<EMAIL_ADDRESS>Date: Samstag, 15. Oktober 2016 12:02
To: Igalia/snabb <snabb<EMAIL_ADDRESS>Cc: Christian Graf <cgraf<EMAIL_ADDRESS>Mention <mention<EMAIL_ADDRESS>Subject: Re: [Igalia/snabb] set interface mtu based on lwaftr v4/v6 mtu (#488)
@chrgrafhttps://github.com/chrgraf: Don't want to mix the configs of the 'micro VNF' snabbvmx with the config of the vMX. Remember that subscriber packets never reach the vMX, so the MTU must be configured by the br-instance. I also can't make the [xe|ge]-0/0/x mtu the only MTU, because the ietf-softwire I-D made the mtu and mru settings mandatory. In addition, Junos allows setting the IFD and IFF MTU seperately, which will make it complicated to derive it.
Bottom line, IMHO the straight forward method is to derive the interface (L2) MTU for snabb 10GE from the softwire mtu/mru settings.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Igalia/snabb/pull/488#issuecomment-253974609, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AU_G6vUFrTTb9nJsAiwRL-Qs-ZZV6dP2ks5q0KSpgaJpZM4KXngU.

@dpino thanks for the suggestion. Updated the files and also covered the places I missed earlier. We seem to have too many cases for loading phy and virt and soon one more when adding virtio_net. Refactoring would be a good idea at some point ;-)


Master

Description

Related issues

Related PRs

Screenshots

1176 changes, including merge conflicts in files. What are you trying to do here ?

Have I done some permanent damage?? I was not supposed to modify the original, but only a forked copy. For studying purposes in Tampere University.
br Joonas Tapio

Lähettäjä: Pierre Slamich<EMAIL_ADDRESS>Lähetetty: tiistai 9. helmikuuta 2021 15.30
Vastaanottaja: openfoodfacts/openfoodfacts-androidapp<EMAIL_ADDRESS>Kopio: TapsG<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Aihe: Re: [openfoodfacts/openfoodfacts-androidapp] Master (#3817)
1176 changes, including merge conflicts in files. What are you trying to do here ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/openfoodfacts/openfoodfacts-androidapp/pull/3817#issuecomment-775936272, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AL6BFNG4YADMFKYA37SO4S3S6E2HRANCNFSM4XHSYOIA.

Have I done some permanent damage?? I was not supposed to modify the original, but only a forked copy. For studying purposes in Tampere University. br Joonas Tapio
…
________________________________ Lähettäjä: Pierre Slamich<EMAIL_ADDRESS>Lähetetty: tiistai 9. helmikuuta 2021 15.30 Vastaanottaja: openfoodfacts/openfoodfacts-androidapp<EMAIL_ADDRESS>Kopio: TapsG<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Aihe: Re: [openfoodfacts/openfoodfacts-androidapp] Master (#3817) 1176 changes, including merge conflicts in files. What are you trying to do here ? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#3817 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AL6BFNG4YADMFKYA37SO4S3S6E2HRANCNFSM4XHSYOIA.

No damage here, don't worry! You just opened a Pull Request to merge the content of your branch. We will close this. @teolemon


Failing grep command in /opt/seagate/cortx/hare/libexec/m0crate-io-conf > /tmp/m0crate-io.yaml.

While running IO test using m0crate utility, grep command is failing /opt/seagate/cortx/hare/libexec/m0crate-io-conf >/tmp/m0crate-io.yaml step.
Identical error message present in https://github.com/Seagate/cortx-hare/issues/1391 issue at the bottom.
[root ~]# /opt/seagate/cortx/hare/libexec/m0crate-io-conf >/tmp/m0crate-io.yaml
Usage: grep [OPTION]... PATTERN [FILE]...
Try 'grep --help' for more information.
Usage: grep [OPTION]... PATTERN [FILE]...
Try 'grep --help' for more information.

@somnathbghule You can ignore those "Usage: grep" messages if resulting yaml file in /tmp folder is created.
We are tracking this as a minor bug as its not breaking functionality.

Not getting this error now:
[root@ssc-vm-g2-rhev4-1947 ~]# /opt/seagate/cortx/hare/libexec/m0crate-io-conf
CrateConfig_Sections: [MOTR_CONFIG, WORKLOAD_SPEC]
MOTR_CONFIG:
MOTR_LOCAL_ADDR: inet:tcp:<IP_ADDRESS>@21501
MOTR_HA_ADDR:    inet:tcp:<IP_ADDRESS>@22001
PROF: <0x7000000000000001:0x4e>  # Profile fid
LAYOUT_ID: 9                      # Defines the UNIT_SIZE (9: 1MB)
IS_OOSTORE: 1                     # Is oostore-mode?
IS_READ_VERIFY: 0                 # Enable read-verify?
TM_RECV_QUEUE_MIN_LEN: 16  # Minimum length of the receive queue
MAX_RPC_MSG_SIZE: 65536    # Maximum rpc message size
PROCESS_FID: <0x7200000000000001:0x27>
IDX_SERVICE_ID: 1
LOG_LEVEL: 4  # err(0), warn(1), info(2), trace(3), debug(4)
WORKLOAD_SPEC:                # Workload specification section
WORKLOAD:                  # First Workload
WORKLOAD_TYPE: 1        # Index(0), IO(1)
WORKLOAD_SEED: tstamp   # SEED to the random number generator
OPCODE: 3               # Operation(s) to test: 2-WRITE, 3-WRITE+READ
IOSIZE: 10m      # Total Size of IO to perform per object
BLOCK_SIZE: 2m          # In N+K conf set to (N * UNIT_SIZE) for max perf
BLOCKS_PER_OP: 1        # Number of blocks per motr operation
MAX_NR_OPS: 1           # Max concurrent operations per thread
NR_OBJS: 10             # Number of objects to create by each thread
NR_THREADS: 4           # Number of threads to run in this workload
RAND_IO: 1              # Random (1) or sequential (0) IO?
MODE: 1                 # Synchronous=0, Asynchronous=1
THREAD_OPS: 0           # All threads write to the same object?
NR_ROUNDS: 1            # Number of times this workload is run
EXEC_TIME: unlimited    # Execution time (secs or "unlimited")
SOURCE_FILE: /tmp/128M  # Source data file
Closing this ticket

Vaibhav Prakash Paratwar commented in Jira Server:

Now we are not getting this error..
[root@ssc-vm-g2-rhev4-1947 ~]# /opt/seagate/cortx/hare/libexec/m0crate-io-conf
CrateConfig_Sections: [MOTR_CONFIG, WORKLOAD_SPEC]
MOTR_CONFIG:
MOTR_LOCAL_ADDR: inet:tcp:<IP_ADDRESS>@21501
MOTR_HA_ADDR:    inet:tcp:<IP_ADDRESS>@22001
PROF: <0x7000000000000001:0x4e>  # Profile fid
LAYOUT_ID: 9                      # Defines the UNIT_SIZE (9: 1MB)
IS_OOSTORE: 1                     # Is oostore-mode?
IS_READ_VERIFY: 0                 # Enable read-verify?
TM_RECV_QUEUE_MIN_LEN: 16  # Minimum length of the receive queue
MAX_RPC_MSG_SIZE: 65536    # Maximum rpc message size
PROCESS_FID: <0x7200000000000001:0x27>
IDX_SERVICE_ID: 1
LOG_LEVEL: 4  # err(0), warn(1), info(2), trace(3), debug(4)
WORKLOAD_SPEC:                # Workload specification section
WORKLOAD:                  # First Workload
WORKLOAD_TYPE: 1        # Index(0), IO(1)
WORKLOAD_SEED: tstamp   # SEED to the random number generator
OPCODE: 3               # Operation(s) to test: 2-WRITE, 3-WRITE+READ
IOSIZE: 10m      # Total Size of IO to perform per object
BLOCK_SIZE: 2m          # In N+K conf set to (N * UNIT_SIZE) for max perf
BLOCKS_PER_OP: 1        # Number of blocks per motr operation
MAX_NR_OPS: 1           # Max concurrent operations per thread
NR_OBJS: 10             # Number of objects to create by each thread
NR_THREADS: 4           # Number of threads to run in this workload
RAND_IO: 1              # Random (1) or sequential (0) IO?
MODE: 1                 # Synchronous=0, Asynchronous=1
THREAD_OPS: 0           # All threads write to the same object?
NR_ROUNDS: 1            # Number of times this workload is run
EXEC_TIME: unlimited    # Execution time (secs or "unlimited")
SOURCE_FILE: /tmp/128M  # Source data file

Vaibhav Prakash Paratwar commented in Jira Server:

Not reproducing now

Vaibhav Prakash Paratwar commented in Jira Server:

.

Vaibhav Prakash Paratwar commented in Jira Server:

.

Vaibhav Prakash Paratwar commented in Jira Server:

.


Update generate.py

reducing checks by changing extra 'if's to 'elif's.
Breaking Change:

Description:
Related issue (if applicable): fixes #
Pull request with documentation for home-assistant.io (if applicable): home-assistant/home-assistant.io#<home-assistant.io PR number goes here>
Example entry for configuration.yaml (if applicable):

Checklist:

[ ] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass
[ ] There is no commented out code in this PR.
[ ] I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[ ] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[ ] Untested files have been added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

Hi @MrAfrazKhan,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Hacktoberfest spam.
The other PR's:

https://github.com/django/django/pull/11864/files
https://github.com/getsentry/sentry/pull/14908/files
https://github.com/wagtail/wagtail/pull/5598/files
https://github.com/fabric/fabric/pull/2020/files


City - Azrael IDs Change Based on Order

Doing Azrael's side mission in a different order causes the save IDs to be different. This is problematic as we currently only keep track of two possible IDs per entry, and tracking (up to) 8 alternate IDs in the route spreadsheet is not ideal.
There is likely a pattern to these save IDs that we can identify and take advantage of.

This was resolved a few weeks ago by this: https://github.com/ShikenNuggets/ArkhamRouteTracker/commit/e8807b1be7efdfc1e6cef953d9cf41a9bfedfaa6, forgot to close this.


Make implementation for actix MultipartForm

#[utoipa::path(
  tag = "Master Storage",
  context_path = "/api/v1/storage",
)]
#[post("/")]
pub async fn store(
  pool: Data<DbPool>,
  form: MultipartForm<Upload>,
  socket: Data<WebsocketServer>,
) -> Result<impl Responder, Error> {
  /* some code */
}

👍🏻

I haven't seen any updates related to this issue yet. I guess it's not planned to be implemented, is it?
As far as I see, multipart forms with file uploads are supported by OpenApi. Is there any other "manual" way to define a proper schema for similar endpoints with Utoipa?

this works fine:
use actix_multipart::form::MultipartForm;
use actix_multipart::form::{tempfile::TempFile, MultipartForm};
use utoipa::ToSchema;

#[derive(Debug, MultipartForm, ToSchema)]
pub struct UpdatePhoto {
    #[schema(value_type = String, format = Binary)]
    #[multipart(limit = "8 MiB")]
    pub photo: TempFile,
}

#[utoipa::path(
    put,
    request_body(content = UpdatePhoto, content_type = "multipart/form-data"),
    responses((status = 200))
)]
#[put("/upload/")]
async fn upload(form: MultipartForm<UpdatePhoto>) -> HttpResponse {}

Thank you, works like charm. 👍

I am not sure what kind of information should be possible to extract form the actix-web multipart data. However the multipart thing will change a bit in coming utoipa 5.0.0. Here is PR which adds some examples for the file upload #1113.


Use an ADT for commandline options instead of a record.

Since Repl/Script are mutually exclusive, represent them by different
alternatives.  That way a script can't be accidentally provided to the
repl.

thanks!


Filter out invalid PRs

Description of the change
This PR filters out contribution in archived repo and and PR labeled as invalid while calculating the score.

@Swechhya Thank you for contributing. 💯 👍


taking care of main vs. master branch

Hey @manoelcampos,
first off: thanks for providing the Asciidoctor GitHub Pages Action, much appreciated! I was looking forward to use it for one of my projects but I did notice that it assumes that the main development branch is master but now GitHub offers the possibility to also use main as the default branch.
I hope this contribution fixes this, so that we can use both versions.
Stay safe and cheers,
Robert

That is strange. I thought this issue is related to the fact that I have main as my default branch instead of master but now it fails in your repo as well even though you have a master branch.

Hey @HaRo87
Thanks for that.
I think the issue is because git branch --list expects user interaction and the script stops waiting for it.
I just changed the command, check my last commit.
I'm using act to try it locally.
I'm going to perform some tests before merging the PR.

Hey @HaRo87
I've merged the PR and made some tweaks. I even renamed my branch to main and updated the yml workflow file so that it fires the action for main or master branches.
It's working fine.
Thanks again.

Awesome @manoelcampos and thanks for the quick response, much appreciated!


Allow "multiple" prop on EfVideo field

need the ability to wrap multiple fields into 1 EasyField, but without the "rows" logic of an EfMiniForm.


Quick Accent doesn't work anymore

Microsoft PowerToys version
0.76.0
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
Quick Accent
Steps to reproduce
Even if Quick Accent is enabled, the toolbar with accented characters doesn't appear when I press the activation keys.
✔ Expected Behavior
The toolbar with accented character appear when I press the activation keys.
❌ Actual Behavior
The toolbar with accented character doesn't appear when I press the activation keys.
Other Software
No response

PowerToysReport_2023-12-12-17-20-15.zip

From the report: [17:25:30.4968498] [Error] Selector::.ctor Exception in SystemThemeWatcher.Watch, issue 30177. The system cannot find the file specified. (0x80070002)
Seems to be another case of https://github.com/lepoco/wpfui/issues/593

/dup #30357

This was hotfixed with 0.76.2. Please update PowerToys.


feat: removing the table of content and adding the title if not present before posting to medium

I improved the medium plugin by using BeautifulSoup to remove the generated table of content because it's totally messing the medium article.
I also added a <h1> tag with the post title in the article if it's not present already because filling the title attribute in the medium api doesnt work and the article ends up being without any title.
I also formatted the previous code to be compliant with PEP style.

From Medium’s API docs:

The title of the post. Note that this title is used for SEO and when rendering the post as a listing, but will not appear in the actual post—for that, the title must be specified in the content field as well.

I knew Medium was dumb, but never that it was completely braindead.  Oh well.

My code works for the TOC made with pandoc, but I don't know how rst is generating the table of content in html so I don't know if it will works for removing the toc.

It uses div id="contents", but I would be wary about removing it, since that ID could happen in organic content.

Ok, just thought that I forgot to remove BeautifulSoup from the requirement.txt 🤦🏻♂

Mmh, it is not in the requirements.txt anymore, maybe I actually did remove it ^^nevermind

Oh no even better, I actually forgot to put it there the first time ahah well at least everything is fine. Have a great day!


租户数据无法隔离

Search before asking

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

Description
租户数据无法隔离
Use case
租户数据无法隔离
Related issues
租户数据无法隔离
Feature Priority
High
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

We have reserved sys_code and user_code, and need to implement user/tenant isolation by ourselves


feat: implement provider side of tls certificates v4

Description
Implement the provider side of the TLS certificates library V4.
Notable changes from V3
Remove custom events
In our TLS Providers we heavily rely on getters (instead of the TLS custom events) to get the outstanding certificate requests and other tls related information. Because of this, we completely remove custom events from the tls lib v4.
Replace jsonschemas with Pydantic
Just like we did for the requirer side, we use Pydantic for relation data validation instead of json schemas.
Replace harness with scenario
Just like we did for the requirer side, here we use scenario instead of harness for unit testing.
Remove Self Signed Certificates specific helpers
There were a couple of helper methods here that were used only by self signed certificates and those have been removed and will be added in the self-signed-certificates charm instead:

generate_certificate
generate_ca

Checklist

[ ] My code follows the style guidelines of this project.
[ ] I have performed a self-review of my own code.
[ ] I have made corresponding changes to the documentation.
[ ] I have added tests that validate the behaviour of the software.
[ ] I validated that new and existing unit tests pass locally with my changes.
[ ] Any dependent changes have been merged and published in downstream modules.
[ ] I have bumped the version of any required library.

Good catch. Made sense when I saw it, but I didn't notice it (obviously).


InteriorLeftNav passes invalid onClick prop

A warning is being issued for invalid props in InteriorLeftNav:
warning.js?6327:33 Warning: Expected `onClick` listener to be a function, instead got a value of `boolean` type.
    in nav (created by InteriorLeftNav)
    in InteriorLeftNav

For some reason, the toggle function is only added if !this.state.open. I'm not sure of the history or what this is supposed to do, so my fix may not be correct, but I'm thinking this could be:
      <nav
        role="navigation"
        aria-label="Interior Left Navigation"
        className={classNames}
-       onClick={!this.state.open && this.toggle}
+       onClick={!this.state.open ? this.toggle : () => {}}
        {...other}
      >

If someone wants to confirm, I'll submit the PR.

Bluemix toolchain: Delivery Pipeline deployed carbon-components-react to Bluemix Design System, including commit ff69e0af707d8107ea8c170d88b2bd7b2a99fe69


Let users define how often to publish status

from https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/happybubbles/eJ1awxKZ_gA
add a command-line option to only send the status every X seconds if someone wants that. But default to 1 if not defined.

I would like this feature too to avoid flooding my home assistant log. In addition to changing the update rate in the presence software, a firmware option to adjust the update rate from the actual units to the MQTT server would be useful too. This would be to prevent against flooding mosquitto's  logs.

@siam28 could you just turn down what you're logging on MQTT? I don't really want to add any update limits on the firmware/units themselves because it would really reduce their performance a lot. Their job is to forward the latest readings as fast as possible. How do you propose to reduce that?
I suggest you adjust your Mosquitto config to log only errors/warnings and not every message coming in. Take a look at this good tutorial on doing that: http://www.steves-internet-guide.com/mosquitto-logging/
You could also enable something like logrotate to purge out old logs to keep Mosquitto from filling up logs on your filesystem.
But I really think too much logging is more of a problem than how often the presence system updates.

fixed with 0a1d7c3f5c3ab35bf41d56cca5e3baf604b7acf6

We could make these arguments (turning down logging, purging etc.) for not adding an option to change the publish status period from presence.
I still think having the publish period configurable in the device firmware is a good feature. By default, you can have the devices send updates as fast possible like they currently do. So by default, the performance wouldn't be affected. For users who are using it for automation scenarios that don't require immediate updates, they can adjust if needed. Having options is never a bad thing.
Also, turning down logging for MQTT is not always possible or desirable because there could be some MQTT devices for which you want or need to see all messages.


fix: bump btjs

Description

Bumps BTJS to add CRA warning.

Testing required outside of automated testing?

[ ] Not Applicable

Screenshots (if appropriate):

[ ] Not Applicable

Rollback / Rollforward Procedure

[x] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

:tada: This PR is included in version 1.12.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Molecule test by default runs cleanup before destroy on test

Issue Type

Bug report

Molecule and Ansible details
ansible 2.8.1
  config file = None
  configured module search path = ['/Users/user/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /Users/user/Envs/project/lib/python3.7/site-packages/ansible
  executable location = /Users/user/Envs/project/bin/ansible
  python version = 3.7.3 (default, Jun 25 2019, 11:10:25) [Clang 10.0.1 (clang-1<IP_ADDRESS>)]
molecule, version 2.20.1

Molecule installation method (one of):

pip

Ansible installation method (one of):

pip

Detail any linters or test runners used:
Desired Behavior
Molecule test runs like the following:
test_sequence:
    - lint
    - destroy
    - dependency
    - syntax
    - create
    - prepare
    - converge
    - idempotence
    - side_effect
    - verify
    - cleanup
    - destroy

Actual Behaviour
Molecule test is being ran like the following:
test_sequence:
    - lint
    - cleanup
    - destroy
    - dependency
    - syntax
    - create
    - prepare
    - converge
    - idempotence
    - side_effect
    - verify
    - cleanup
    - destroy

Molecule test should not run cleanup before VMs are created and converged. Molecule test fails because ansible can't run on vms that do not exist yet. This is using Vagrant/Virtualbox, I have not tested with Docker.
Molecule Test Log
--> Validating schema /Users/user/git/project/roles/common/molecule/default/molecule.yml.
Validation completed successfully.
--> Test matrix

└── default
    ├── lint
    ├── cleanup
    ├── destroy
    ├── dependency
    ├── syntax
    ├── create
    ├── prepare
    ├── converge
    ├── idempotence
    ├── side_effect
    ├── verify
    ├── cleanup
    └── destroy

--> Inventory /Users/user/git/project/roles/common/molecule/default/../../../../development.yml linked to /var/folders/pl/rxj8k5v54017g9nnb34yxkr4tg3p52/T/molecule/common/default/inventory/hosts
--> Inventory /Users/user/git/project/roles/common/molecule/default/../../../../group_vars/ linked to /var/folders/pl/rxj8k5v54017g9nnb34yxkr4tg3p52/T/molecule/common/default/inventory/group_vars
--> Inventory /Users/user/git/project/roles/common/molecule/default/../../../../host_vars/ linked to /var/folders/pl/rxj8k5v54017g9nnb34yxkr4tg3p52/T/molecule/common/default/inventory/host_vars
--> Scenario: 'default'
--> Action: 'lint'
--> Executing Yamllint on files found in /Users/user/git/project/roles/common/...
Lint completed successfully.
--> Executing Flake8 on files found in /Users/user/git/project/roles/common/molecule/default/tests/...
Lint completed successfully.
--> Executing Ansible Lint on /Users/user/git/project/roles/common/molecule/default/playbook.yml...

Lint completed successfully.
--> Inventory /Users/user/git/project/roles/common/molecule/default/../../../../development.yml linked to /var/folders/pl/rxj8k5v54017g9nnb34yxkr4tg3p52/T/molecule/common/default/inventory/hosts
--> Inventory /Users/user/git/project/roles/common/molecule/default/../../../../group_vars/ linked to /var/folders/pl/rxj8k5v54017g9nnb34yxkr4tg3p52/T/molecule/common/default/inventory/group_vars
--> Inventory /Users/user/git/project/roles/common/molecule/default/../../../../host_vars/ linked to /var/folders/pl/rxj8k5v54017g9nnb34yxkr4tg3p52/T/molecule/common/default/inventory/host_vars
--> Scenario: 'default'
--> Action: 'cleanup'

    PLAY [Converge] ****************************************************************

    TASK [Gathering Facts] *********************************************************
    fatal: [cos-7]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ssh: Could not resolve hostname cos-7: nodename nor servname provided, or not known", "unreachable": true}
    fatal: [u-1604]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ssh: connect to host u-1604 port 22: Operation timed out", "unreachable": true}
    fatal: [u-1804]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ssh: connect to host u-1804 port 22: Operation timed out", "unreachable": true}

    PLAY RECAP *********************************************************************
    cos-7             : ok=0    changed=0    unreachable=1    failed=0    skipped=0    rescued=0    ignored=0
    u-1604            : ok=0    changed=0    unreachable=1    failed=0    skipped=0    rescued=0    ignored=0
    u-1804            : ok=0    changed=0    unreachable=1    failed=0    skipped=0    rescued=0    ignored=0

ERROR:
An error occurred during the test sequence action: 'cleanup'. Cleaning up.
--> Inventory /Users/user/git/project/roles/common/molecule/default/../../../../development.yml linked to /var/folders/pl/rxj8k5v54017g9nnb34yxkr4tg3p52/T/molecule/common/default/inventory/hosts
--> Inventory /Users/user/git/project/roles/common/molecule/default/../../../../group_vars/ linked to /var/folders/pl/rxj8k5v54017g9nnb34yxkr4tg3p52/T/molecule/common/default/inventory/group_vars
--> Inventory /Users/user/git/project/roles/common/molecule/default/../../../../host_vars/ linked to /var/folders/pl/rxj8k5v54017g9nnb34yxkr4tg3p52/T/molecule/common/default/inventory/host_vars
--> Scenario: 'default'
--> Action: 'destroy'

    PLAY [Destroy] *****************************************************************

    TASK [Destroy molecule instance(s)] ********************************************
    ok: [localhost] => (item=None)
    ok: [localhost] => (item=None)
    ok: [localhost] => (item=None)
    ok: [localhost]

    TASK [Populate instance config] ************************************************
    ok: [localhost]

    TASK [Dump instance config] ****************************************************
    skipping: [localhost]

    PLAY RECAP *********************************************************************
    localhost                  : ok=2    changed=0    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0

From https://molecule.readthedocs.io/en/latest/configuration.html:

The cleanup step is executed directly before every destroy step. Just like the destroy step, it will be run twice. An initial clean before converge and then a clean before the last destroy step. This means that the cleanup playbook must handle failures to cleanup resources which have not been created yet.

Our documentation isn't so discoverable but yes, this is all by design.

I've read that, but the way this is designed makes molecule test impossible to run with a cleanup playbook without modification to the molecule.yml file.

the way this is designed makes molecule test impossible to run with a cleanup playbook without modification to the molecule.yml file.

Explain please.

If molecule has not created my VMs yet it can't cleanup, causing the error
    TASK [Gathering Facts] *********************************************************
    fatal: [cos-7]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ssh: Could not resolve hostname cos-7: nodename nor servname provided, or not known", "unreachable": true}
    fatal: [u-1604]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ssh: connect to host u-1604 port 22: Operation timed out", "unreachable": true}
    fatal: [u-1804]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ssh: connect to host u-1804 port 22: Operation timed out", "unreachable": true}

If I for instance ran molecule create then molecule test test would work since it would be able to connect to my existing vms, run cleanup, run destroy, then run the rest of the stack, but if I have not created my vms molecule cleanup will try to connect to non-existant vms and fail.

The documentation states that your cleanup.yml should handle the case when test resources are not available. Cleanup should not assume molecule managed resources. It's not for that. If you want to propose a design change, please raise another issue in a proposal form.

If this is the way this is designed to work that's fine, but are there examples of how to handle the case where resources aren't available?

Happily accepting documention PRs!

I end up with something like this:
---
- hosts: all
  gather_facts: false
  tasks:
    - wait_for_connection:
        timeout: 10
      register: wait_for_instances
      failed_when: false

    - name: 'cleanup'
      command: losetup -d /dev/loop0
      when: wait_for_instances.elapsed < 10

Sadly I have to sacrifice 10 seconds to know whether instances has been spawned yet or not.

Thanks @Zempashi , I think for now I will just force test to skip the first cleanup by using the test_scenario override here.

I'm presently using when: ansible_host != inventory_hostname on tasks in cleanup.yml and that seems to working as ansible_host is populated in the inventory file when the host is created.

I'm having luck adding when: ansible_host != inventory_hostname as the former appears to only be set (to IP, at least in the case of the OpenStack driver) when the instance in question has been successfully created.

I landed here because had the same problem, but with RHEL images on Docker.
My scenario is as follows:

I use the docker driver
Role must be tested on RHEL
Preparation needs some packages thus needing a subscription
I didn't want to manually remove subscriptions from RH portal

My previous setup was to subscribe the container with the prepare.yml and remove the subscription at the end of converge.yml in a block/always statement.
This way I was losing idempotence test though. Since both cleanup/destroy are done BEFORE AND AFTER everything it would just not be enough to unsubscribe in those steps.
TL;DR:
I achieved it this way:
$ cat molecule/default/prepare.yml
---
- name: Prepare
  hosts: all
  tasks:
    - name: Register container
      redhat_subscription:
         state: present
         username: "{{ rhn_username | default('default-username-if-any', true) }}"
         password: "{{ rhn_password | default('default-password-if-any', true) }}"
         auto_attach: true
      when: ansible_facts['distribution'] == "RedHat"
      vars:
        rhn_username: overridden-username
        rhn_password: overridden-username

[work@maguro vsm_deploy]$ cat molecule/default/cleanup.yml
---
- name: Cleanup
  hosts: all
  gather_facts: no
  tasks:
    - name: Block
      block:
        - name: Check if containers are up
          docker_container_info:
            name: "{{ item['name'] }}"
          register: molecule_test
          until:
            - molecule_test['exists']
            - molecule_test['container']['State']['Running']
          retries: 1
          delay: 1
          loop: "{{ molecule_yml['platforms'] | flatten(levels=1) }}"
          delegate_to: localhost

        - name: Gather facts
          setup:
            gather_subset:
              - '!all'
              - '!any'
              - distribution

        - name: Unregister system
          redhat_subscription:
            state: absent
          when: ansible_facts['distribution'] == "RedHat"
      rescue:
        - name: It's ok we're at startup
          meta: noop

All of this because I wanted to use the ansible_facts['distribution'] == "RedHat" and not checking grepping the content of /etc/redhat-release.
Hope this will help somebody else.


feat:B11009058-aws

Checks

[ ] Your YAML file has required fields as listed in Specs
[ ] All checks have passed yaml-lint passed
[ ] You agree to contribute your work under MIT license

achieved


[angel] Add extractor

Template
Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8 and ran relevant tests

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Fix or improvement to an extractor (Make sure to add/update tests)
[x] New extractor (Piracy websites will not be accepted)
[ ] Core bug fix/improvement
[ ] New feature (It is strongly recommended to open an issue first)

Description of your pull request and other information

This PR adds an extractor for the angel (https://www.angel.com/). All of the information required for the episodes were in an application/ld+json tag in the webpage.
One thing to note is that there were several transformations on the thumbnail url in the JSON-LD in the that I have removed. I thought it would be best to remove all transformations and just return the original thumbnail. These transformations can result in returning smaller thumbnails for example:

https://images.angelstudios.com/image/upload/f_auto,c_limit,w_3840,q_auto/c_fill,q_auto,ar_16:9,g_north/v1643403801/angel-app/tuttle-twins/videos/season_1/Episode_1_App_Thumbnail.jpeg
https://images.angelstudios.com/image/upload/b_rgb:000000,c_fill,h_630,w_1200,g_north/v1643403801/angel-app/tuttle-twins/videos/season_1/Episode_1_App_Thumbnail

Indirectly fixes #1243. There are several links from https://watch.angelstudios.com that lead to https://www.angel.com where The Chosen series is also hosted, but supporting angel.com leads to support of more series.

There looks to still be an issue.
I tried to download a few episodes and they started off fine on my windows desktop with the creator talking then after that the audio drops out (video keeps going). On my Android Tablet and default player the first plays and then i get an error.  VLC on my tablet did not even want to play  them
Here are two examples.
https://watch.angelstudios.com/thechosen/watch/episodes/season-2-episode-1-thunder
https://watch.angelstudios.com/thechosen/watch/episodes/season-2-episode-2-i-saw-you


feat: Add kurtosis service exec command

Description:
Users can now run kurtosis service exec <ENCLAVE_ID> <SERVICE_ID> 'any sh command'. The command will be executed inside the designated user service and the result will be printed in the CLI output.
The main different with kurtosis service shell <ENCLAVE_ID> <SERVICE_ID> --exec 'any sh command' is that the former expects a zero exit code for the command otherwise throws an exception, whereas the latter returns gracefully whatever the exit code of the command was.
In short, kurtosis service shell is designed for interactive sessions and will always return gracefully as long as the session terminated is ended successfully. kurtosis service exec provides a way to run a single command and returns immediately, taking the status of the command into account.
Is this change user facing?
YES

References (if applicable):


feat: Add managed cluster set for GitOps support

Is your feature request related to a problem? Please describe.
It is useful to include RHACM's support for managing GitOps applications on remote clusters, as documented in https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.7/html/applications/managing-applications#gitops-config.
Describe the solution you'd like
Use instructions from https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.7/html/applications/managing-applications#gitops-config to manage GitOps applications in remote clusters without having to deploy GitOps on those clusters.
Describe alternatives you've considered
Continue using solely the current approach of deploying GitOps operator to target clusters.
Additional context
Useful page on RBAC permissions to ManagedClusterSet resources:
https://open-cluster-management.io/concepts/managedclusterset/#clusterset-rbac-permission-control

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