Update old and broken workflow test json templates

Impact of the bug
WMCore testing
Describe the bug
The following 3 workflows (Integration test json templates) are failing in MSTransferor because their input dataset got wiped out from the grid:
2022-05-07 02:06:03,748:ERROR:PycurlRucio: Failure in getBlocksAndSizeRucio function for container /RelValTTbar_14TeV/CMSSW_12_0_0_pre4-PU_120X_mcRun3_2021_realistic_v2-v1/GEN-SIM-DIGI-RAW. Response: {'url': 'http://cms-rucio.cern.ch/dids/cms/dids/search?type=dataset&long=True&name=/RelValTTbar_14TeV/CMSSW_12_0_0_pre4-PU_120X_mcRun3_2021_realistic_v2-v1/GEN-SIM-DIGI-RAW%23%2A', 'data': '', 'headers': 'HTTP/1.1 200 OK\r\nDate: Sat, 07 May 2022 00:06:03 GMT\r\nContent-Type: application/x-json-stream\r\nContent-Length: 0\r\nConnection: keep-alive\r\nAccess-Control-Allow-Origin: None\r\nAccess-Control-Allow-Headers: None\r\nAccess-Control-Allow-Methods: *\r\nAccess-Control-Allow-Credentials: true\r\nCache-Control: post-check=0, pre-check=0\r\nPragma: no-cache\r\nX-Rucio-Host: cms-rucio.cern.ch\r\n\r\n'}
2022-05-07 02:06:03,748:WARNING:RequestInfo: Removing workflow that failed processing in MSTransferor: amaltaro_TC_PY3_TTbarPU_HG2109_Val_210901_200000_9228
2022-05-07 02:06:03,748:WARNING:RequestInfo: Removing workflow that failed processing in MSTransferor: amaltaro_SC_PY3_PURecyc_HG2109_Val_210901_195950_2940
2022-05-07 02:06:03,748:WARNING:RequestInfo: Removing workflow that failed processing in MSTransferor: amaltaro_SC_PY3_PURecyc_HG2109_Val_210903_160613_9070

so those need to be updated once again.
How to reproduce it
Search for this in DAS Web: site dataset=/RelValTTbar_14TeV/CMSSW_12_0_0_pre4-PU_120X_mcRun3_2021_realistic_v2-v1/GEN-SIM-DIGI-RAW
Expected behavior
Either we find another input dataset that still work for those templates/configs, or we create other templates to test the same features as the current ones. We might as well check if those features are already covered by other templates, in that case we could simply remove them.
Additional context and error message
None

We start accumulating more of those templates that would need extra attention due to missing data in Rucio.  Here are some more  workflows suffering the same problem of completely missing inputs and those have been detected at MSTransferror.
2022-07-05 01:51:21,449:WARNING:RequestInfo: Removing workflow that failed processing in MSTransferor: tivanov_DQMHarvesting_HG2207_Val_220630_171451_6004
2022-07-05 01:51:21,449:WARNING:RequestInfo: Removing workflow that failed processing in MSTransferor: tivanov_TaskChain_PUMCRecyc_HG2207_Val_220630_171515_4708
2022-07-05 01:51:21,449:WARNING:RequestInfo: Removing workflow that failed processing in MSTransferor: tivanov_DQMHarvesting_MultiRun_HG2207_Val_220630_171453_7939
2022-07-05 01:51:21,449:WARNING:RequestInfo: Removing workflow that failed processing in MSTransferor: tivanov_DQMHarvesting_LumiMask_HG2207_Val_220630_171452_6718
2022-07-05 01:51:21,449:WARNING:RequestInfo: Removing workflow that failed processing in MSTransferor: tivanov_SC_ReDigi_Harvest_Prod_HG2207_Val_220630_171503_9802

While the above were missing the whole dataset/container, there were few workflows whose input and PU datasets are missing blocks in Rucio. Those blocks on the other hand were properly listed as valid in DBS though. The workflows suffering this issue were detected much later in the LocalWorkqueue of the agent. Here follows the rest of the list of broken templates:
2022-07-05 16:31:03,300:140554330814208:ERROR:WorkQueue:tivanov_DQMHarvest_RunWhitelist_HG2207_Val_220630_171416_4188, ['/ZeroBias/Run2016B-UL16_ver2_forHarvestOnly-v1/DQMIO']:

Another DMWM template that gets stuck in running-open, in the agent:
2022-08-04 14:30:42,853:140554330814208:ERROR:WorkQueue:amaltaro_DQMHarvest_RunWhitelist_HG2208_Val_220804_125609_3733, ['/ZeroBias/Run2016B-UL16_ver2_forHarvestOnly-v1/DQMIO']:
failed to retrieve data from DBS/Rucio in LQ:
<@========== WMException Start ==========@>
Exception Class: WMRucioDIDNotFoundException
Message: Data identifier not found in Rucio: /ZeroBias/Run2016B-UL16_ver2_forHarvestOnly-v1/DQMIO#bf288630-b881-4b66-ba8d-ed592f846d01. Error: Data identifier not found.
Details: Data identifier 'cms:/ZeroBias/Run2016B-UL16_ver2_forHarvestOnly-v1/DQMIO#bf288630-b881-4b66-ba8d-ed592f846d01' not found

We should finalize this development and have functional test templates, otherwise we are in a delicate situation with pre-production validation. Moving it to Q2, marking it as a High prio under Operations.

I won't be able to work on this one for the next couple of weeks, so I am moving it back to the ToDo queue.
Note that this PR https://github.com/dmwm/WMCore/pull/11238 already fixes many templates, but there is still a handful of other json templates that need to be revisited.

This is mostly done, and we have to finish it sooner than later. So setting to 2023 Q4 as an Operations ticket.


RFC: Revisit ensemble calling for paired tumor analyses

Rationale for this issue: a few days ago the wet lab people were validating some of the mutations I had found, and while they correctly validated them, it turned out they weren't somatic, but germline.
The reason is that when I evaluated them after the pipeline, there were some loci in common between the callers I used (MuTect and VarScan), however  MuTect (more stringent than VarScan) had rejected them (non-somatic variants). As I only evaluated the passing mutations (and since gemini uses --passonly), I completely skipped over that issue.
Ensemble calling would be a nice alternative to prevent these kinds of issues.  Perhaps there is no need for enhancements, but at least some rough documentation on how to proceed.

Hi
I am closing this because it seems an old issue. Come back if you find other issues  or want to continue with this one.
cheers


[ENHANCEMENT] Bump Kubevirt to 1.1.1-1505<IP_ADDRESS>

Is your enhancement related to a problem? Please describe.

Bump Kubevirt to 1.1.1-1505<IP_ADDRESS>
Describe the solution you'd like

Bump Kubevirt to 1.1.1-1505<IP_ADDRESS>
Describe alternatives you've considered

Additional context

Validated in master-09f3ca1-head. Version was rolled for virt-api, virt-controller, and virt-handler.


Travel Times

Add functions to summarize travel times, spatially and temporally, using long form capture history data. There's some stuff in the pilotStudy.R to use as a starting point.

I added the function summarise_movement() which provides a summary of movement times by reach, but I'd like to add functionality to:

Add reach lengths (rkm) to convert times to rates
Add week column and summarize movement times/rates by week as well

Drafts of the above were completed.


CAS uses the entityId as a service instead of the service itself

CAS 5.1.2-SNAPSHOT
When CAS is configured to display the SAML metadata (cas-server-support-saml-mdui), I get an "unauthorized application to use CAS" error.
However, the service called as a parameter (here, my shibboleth IDP) is declared as an authorized service.
It would appear that CAS takes the entityId parameter as a service instead of my IDP.
I think the entityId parameter should only be used to display the service description.
Indeed, it is not possible to define ALL the services of a federation of identities.

Indeed, it is not possible to define ALL the services of a federation of identities.

Valid point, indeed. I have not looked at the code yet, but I envision this would be most reasonable:

Find the entityId in metadata
Find the entityId in service registry
Service not authorized.

If the entityId is found in metadata sources or in the registry (removing the need for metadata), then that should work. Otherwise, the service is unauthorized.
Makes sense?

Yes, that seems correct

Sweet. Is this something you're prepared to handle with a PR?

After reflection, in my opinion, only the service should be present in the registry.
The entityId is already in the "registry" of the IdP. Indeed, the SP metadata is the services authorized by the IdPs.
So only information such as name, description and logo should override the definition of the CAS service in the registry (which should be the IdP).
As for the pull request, I'm afraid not to be stuck enough in programming (especially JAVA), sorry (only for a few basic things).
However, it is with pleasure that I will help for other simpler things.
Regards,

After reflection, in my opinion, only the service should be present in the registry.
The entityId is already in the "registry" of the IdP.

This is perfectly valid only with the assumption that there is metadata available for SPs in the MDUI model. This would allow you to enforce authz rules by simply saying: "SP not found in metadata, so unrecognized SP".
However, you can set up MDUI without any metadata and you can have it simply look into the CAS service registry to pull in information...in which case the SP must also be in the registry. Because you dont want cas/login?service=myValidId&entityId=4577834567843757834658734657863478sdjhfbdjshfghjdsf to be considered a valid request if it's not found in the metadata AND it's not found in the registry.
I can take a look later next week possibly to ensure whether the above description matches working code. Thanks for the follow up.

You should be able to test the fix in about an hour or so, by using the new SNAPSHOT.

I ported back the code to version 5.1 and it works like desired.
However, would it be possible to read the name and description of the metadata information only in the browser language, and if not, the English language (if available) and not all of the information in all languages ?
Thanks

The metadata information comes from the metadata, in whatever languages they are written in. We don't translate what's in the metadata.

I don't want to translate information.
I would to know if it possible to pick up them in browser language if available (or the first if not) instead of a concatenation of all

I don't understand what you mean by "pick up them in browser language".

SAML metadata can be defined like
<md:EntityDescriptor entityId="foo">
mdui:UIInfo
<mdui:DisplayName xml:lang="en">FOO</mdui: DisplayName>
<mdui:DisplayName xml:lang="fr">Test</mdui: DisplayName>
</mdui:UIInfo>
</md:EntityDescriptor>
I would like to know if it possible to display French "DisplayName" if I use a French browser (or display English if French description is not available).
Sorry for my English 😓

Gotcha. No it's not possible without code.

Will it be possible in future version (CAS  5.2.0 GA) ?

I am not sure what you mean by "possible". If you mean, is it "planned by someone to add that support"? then no, not that I know of.

Ok, thanks for your response

I can try to take a look myself some time next week, but I am not sure if I can promise anything. I am assuming you can make yourself available to test this? :)

I think I found how to solve it.
I will try to make a PR next week.

@mmoayyed @lsenecaux
You guys realize this breaks cas-server-support-shibboleth as documented here?
https://apereo.github.io/cas/5.1.x/installation/Configuring-Multifactor-Authentication-Triggers.html#entity-id-request-parameter
The intent was to "allow one to activate multifactor authentication policies based on the entity id that is registered in the CAS service registry" with a side benefit of the entityID being able to "take advantage of all other CAS features such as access strategies and authorization rules."

Have you confirmed that 5.2 or 5.1 does is in fact broken? Do you have a sample project you can share that demonstrates this?

@mmoayyed I'm on 5.1.1-SNAPSHOT and have done some fairly extensive testing with service definitions at this point.
With cas-server-support-shibboleth compiled in, my service definition containing only the entityID as the serviceId is not invoked when receiving a delegated authentication request from a Shibboleth 3 IdP:
Login URL:
https://cas.example.com/login?service=https%3A%2F%2Fidp.example.com%2Fidp%2FAuthn%2FExtCas%3Fconversation%3De1s1&entityId=https%3A%2F%2Fservice.example.com`

{
  "@class": "org.apereo.cas.services.RegexRegisteredService",
  "serviceId": "^https://service\\.example\\.com",
  "name": "Shibboleth - SP",
  "id": 1,
  ...

Definition a service with a lower priority that matches idp.example.com is invoked instead.
Unfortunately, I do not have a sample project prepared for sharing at this time.

Thanks. Could you repeat the same test with 5.1.5 plz? Anything less than the current release for a given CAS line is probably not worth the effort and if there is a problem to be fixed, it would get fixed for 5.1.5+.

Thanks for getting back to me on this. Rebuilding now...

Just to clarify, per the cas.authn.shibIdP.serverUrl property, given that the service URL will come through as following:
https://idp.example.com/idp/Authn/ExtCas?conversation=e1s1

Should the value of this property still be https://idp.example.com?

Well, it appears to be detecting it... I need to actually go back to 5.1.1-SNAPSHOT to test something because I didn't have that property in there previously.
There does appear to be at least a bug in extracting the entityID in that I get the following error in catalina.out:
Unauthorized Service Access. Service [https%3A%2F%2Fservice.example.com] is not found in service registry.

However, as before, that is how Shibboleth IdP 3 is formatting that URL when it goes to delegate auth to CAS.

Alright, results are in:

5.1.1-SNAPSHOT - Completely broken. CAS no longer cares about entityID.
5.1.5-SNAPSHOT - At least acknowledges the presence of an entityID but fails to properly URL decode it.

Best workaround to date appears to be including URL-encoded version of serviceId.
Example:
{
  "@class": "org.apereo.cas.services.RegexRegisteredService",
  "serviceId": "^(https://|https%3A%2F%2F)service\\.example\\.com$",
  "name": "Shibboleth - SP",
  "id": 1,
  "proxyPolicy": {
    "@class": "org.apereo.cas.services.RefuseRegisteredServiceProxyPolicy"
  },
  ...
}

Just as an aside, in 5.1.5-SNAPSHOT, CAS does not displayed the "Application Not Authorized to Use CAS" message in the UI as it normally does when it is unable to find it in the service registry.
Upon successful login, the user gets returned to the same login page with the following error thrown in the logs:
org.apereo.cas.services.UnauthorizedServiceException: Unauthorized Service Access. Service [http%3A%2F%2Fservice.example.com] is not found in service registry.

To update, we're abandoning this issues due to one that takes higher precedence for us here: https://github.com/apereo/cas/issues/3054


Bootstrap 4 modal does not allow to scroll on input field

When the modal is opened and drag down on the blank space between fields. It does work fine. However, if the touchstart event on the top of an input field, the scrolling does not work.

Operating system and version
iOS 12

Browser and version
Safari, Chrome

[Reduced test case]
https://www.bootply.com/SCifOFaozG

Here is my tweak to make the input field to be scrollable when touch on it
Reference: https://developer.mozilla.org/en-US/docs/Web/CSS/-webkit-overflow-scrolling
//allow scrolling the page when touch starts on the top of an input field
.modal{
-webkit-overflow-scrolling: touch;
}

Plenty of reasons for now adding the overflow scrolling that are mentioned in issues and PRs. Closing as a won't fix for now.


Remove stale comment

Fixes #1121

The issue listed (#1121) is about making sure that shader entry point functions are void(). My understanding reading the existing code is that this is already being checked, just the comments are a bit out of date. I am just updating the comments and closing out the issue with this PR.


SpongeForge !!

so iam trying to use Mods / Plugins in my earth world server
my mod list is :
1- CubicChunks-1.12.2-0.0.1055.0-SNAPSHOT-all.jar
2- CubicWorldGen-1.12.2-<IP_ADDRESS>-SNAPSHOT-all.jar
3- effortlessbuilding-1.12.2-2.16.jar
4-letsencryptcraft-1.10.2-1.2.0.jar
5- malisiscore-1.12.2-6.5.1.jar
6- worldedit-forge-mc1.12.2-6.1.10-cc975.01-SNAPSHOT-dist.jar
7- terra121-0.1.3.jar
so i tried to add SpongeForge its this : https://www.spongepowered.org/downloads/spongeforge/stable/1.12.2
and this happend : https://hastebin.com/qoyanicili.md
any idea how to fix or add complitable?
or maybe support this !
https://github.com/KettleFoundation/Kettle
what iam trying to do is add plugins support to my earth server !!
help please or add support to SpongeForge or Kettle !

Im not sure. I think sponge has to do with cubic chunks and it looks like you have two versions of that, so mabye delete that cc SNAPSHOT thing. If your working with the build the world project try to ask in the discord first if minecraft wont start

Cubic chunks is not compatible with sponge forge and won't be compatible in the near future.


chore: README updates, fix shields and update migration phrasing.

Summary
Minor README updates.
Test Plan
N/A

when I view the file, I'm still seeing license:not specified. is it just me?


Viewing a router looks editable and does not show all information

Information not shown (either on view or edit, which is problematic on edit because then saving removes whatever information should've been there):

Path
Header Rules
Cookie Rules

In general, when I view the details of a route by clicking on it, I can edit the fields (but nowhere to save/cancel). The only field I cannot edit is "Name". "Namespace" has a button to "Create new namespace" that should not be there.

3 Issues upon validation:

View does not allow me to edit fields anymore, which is good. However, Edit also does not allow me to edit fields anymore.

Path still doesn't show the value that was input

Headers and Cookies also don't show the data that was input. They both show 0: false. This might need to be a separate issue? I think possibly what we send to the API is incorrect when creating these:
Example request:
{"type":"rio.cattle.io.v1.router","kind":"Router","apiVersion":"rio.cattle.io/v1","metadata":{"annotations":{},"namespace":"default","name":"myuirt"},"spec":{"routes":[{"match":{"headers":[{"name":"0","value":{"name":"FOO","value":{"exact":"TEST"},"binary":false}}],"path":{"exact":"/v0"},"cookies":[{"name":"0","value":{"name":"MYCOOK","value":{"exact":"ISACHEF"},"binary":false}}]},"uuid":"M0LilJYGrehWDR7f","to":[{"app":"demo","version":"v0","port":80,"uuid":"lIbvUBlyueYwfL90"}]}]}}
Example response from above request:
{"_type":"rio.cattle.io.v1.router","apiVersion":"rio.cattle.io/v1","id":"default/myuirt","kind":"Router","links":{"remove":"https://dashboard-rio-system.yrxyrb.on-rio.io/v1/rio.cattle.io.v1.routers/default/myuirt","rioupdate":"https://dashboard-rio-system.yrxyrb.on-rio.io/v1/rio.cattle.io.v1.routers/default/myuirt?riofile","rioview":"https://dashboard-rio-system.yrxyrb.on-rio.io/v1/rio.cattle.io.v1.routers/default/myuirt?riofile","self":"https://dashboard-rio-system.yrxyrb.on-rio.io/v1/rio.cattle.io.v1.routers/default/myuirt","update":"https://dashboard-rio-system.yrxyrb.on-rio.io/v1/rio.cattle.io.v1.routers/default/myuirt"},"metadata":{"creationTimestamp":"2019-12-11T20:20:26Z","generation":1,"name":"myuirt","namespace":"default","resourceVersion":"247468","selfLink":"/apis/rio.cattle.io/v1/namespaces/default/routers/myuirt","uid":"2a1b1c2d-cbcf-4c54-8fd1-95df560ead96"},"spec":{"routes":[{"match":{"cookies":[{"name":"0","value":{"binary":false,"name":"MYCOOK","value":{"exact":"ISACHEF"}}}],"headers":[{"name":"0","value":{"binary":false,"name":"FOO","value":{"exact":"TEST"}}}],"path":{"exact":"/v0"}},"to":[{"app":"demo","port":80,"uuid":"lIbvUBlyueYwfL90","version":"v0"}],"uuid":"M0LilJYGrehWDR7f"}]},"type":"rio.cattle.io.v1.router"}
Example Desired Request (left out cookies in this):
{"kind":"Router","apiVersion":"rio.cattle.io/v1","metadata":{"name":"clirt","namespace":"default","creationTimestamp":null},"spec":{"routes":[{"match":{"path":{"exact":"/v0"},"headers":[{"name":"FOO","value":{"exact":"TEST"}}]},"to":[{"app":"demo","version":"v0"}]}]},"status":{}}

Rio is no longer supported. If this is a general Rancher dashboard issue, please feel free to re-open with additional information.


Increase code coverage

Q
A

Is bugfix?
❌

New feature?
❌

Breaks BC?
❌

Fixed issues
-

Looks alright but Psalm issues should be fixed.

Looks alright but Psalm issues should be fixed.

Done.

👍


Code Style Fixing

https://github.com/speechbrain/speechbrain/blob/develop/speechbrain/utils/metric_stats.py#:~:text=(self.-,labels,-%3D%3D 1).

It's better to use self.labels == self.positive_label than hardcode to self.labels == 1.

Hello,
Could you please open a PR with your modification?
Many thanks :)


Added Send trait to vector structs

[x] I agree to follow the project's code of conduct.
[ ] I added an entry to CHANGES.md if knowledge of this change could be valuable to users.

I needed vector structs to be send for my use case, due to use in an async functions. These changes for good for my use case, since I'm wrapping everything in an Arc<Mutex<, but let me know if this might cause potential issues, or if something else is needed to make these changes safer.

r? @ttencate

Rebasing over master should fix the CI error.

If merged, this will close #417.

I don't remember this paragraph; maybe it was added after I filed https://github.com/georust/gdal/issues/417.

That's pretty old, see for example the note at the top of https://gdal.org/drivers/raster/vrt.html#multi-threading-issues.

One option is to keep Send but add a stern warning to the docs. I think there are several more places in the crate already where safe Rust can actually trigger UB.

I don't want this. There are indeed some unsound APIs (ahem read_block), but we should fix them. Exposing this would be pretty horrible.

If everything needs to be made entirely safe, the crate could use the typestate pattern. Every refcounted type would get a generic parameter which indicates whether it's unique, or might be shared. Most GDAL functions would return shared objects, but constructor-like functions return unique ones.

This might work, but I'm not 100% sure yet. It does bring a fair amount of complexity, though.
In the meanwhile, you can usually work around the types being !Send by using channels. That should work even in async code.

After about a month of using this, I haven't encountered any issues. I am however not using any structs in multiple threads, only  async functions.
@ttencate Is the idea behind a typestate to enforce so that certain structs have to be moved therefore preventing accidental use in multi-thread? I'd we willing to take a stab at it, but would need some help with that idea.

After about a month of using this, I haven't encountered any issues. I am however not using any structs in multiple threads, only async functions.

Sure, it's not going to cause problems in practice, but the whole idea of Rust is that you're not supposed to do bad things like this in safe code, no matter how hard you try. There was a bit of a mess a while ago, with a web framework that pulled this kind of trick (implementing Send for !Send types).

Is the idea behind a typestate to enforce so that certain structs have to be moved therefore preventing accidental use in multi-thread?

It's to make sure you go through some hoops when you send them. For example, you have a normal (owned) Dataset that's !Send, you turn it into a SendableDataset which is (and check the reference count at this point), then the receiving thread turns it back into a Dataset. You can't use SendableDataset for anything else, consider this case:

you own a Dataset
you convert it to its Send flavour, asserting that the reference count is 1
you get a RasterBand from it
your dataset now has a reference count of 2

There's also the option to use a generic argument to keep track of "sendability", but I think it boils down to the same thing.
This makes some code look nicer (you can pass datasets to other threads instead of paths to open), but doesn't help much in async contexts, where you switch threads all the time.

What I had in mind with the typestate pattern was something along the lines of Dataset<Unique> vs. Dataset<Shared>, where only Dataset<Unique> is Send. However, I like @lnicola's idea much better, because it doesn't require changing literally all the types in the crate to be generic.
How about this then:

We add a trait RefCounted, which has (at least) a function ref_count(&self) -> usize;.
Reference-counted objects like Dataset implement this trait.
We add a wrapper struct Sender<T> which wraps a T and (unsafely, manually) implements Send. A Sender<T> can be constructed from any T: RefCounted, but the construction fails if the reference count is greater than 1:

pub struct Sender<T>(T);

unsafe impl<T> Send for Sender<T> {}

impl<T: RefCounted> Sender<T> {
    // Could also be a TryFrom impl.
    pub fn try_wrap(inner: T) -> Result<T> {
        if inner.ref_count() <= 1 {
            Ok(Self(inner))
        } else {
            Err(Error::...)
        }
    }

    // Could also be into, but we can't blanket-impl From<Sender<T>> for T due to orphan rules.
    pub fn into_inner(self) -> T {
        self.0
    }
}

However, this is still not fully sound. It can break if T contains references to other ref-counted objects inside it, if those inner objects don't hold a reference back to the T. For example, in the scenario I sketched earlier: OGRFeature has a reference to its OGRFeatureDefn but presumably not the other way round. So if we send a freshly created, uniquely referenced Feature to another thread, both threads have a reference to the underlying Defn.
(In this particular case, the Defn is probably only read from, and concurrent reads are probably okay, but neither is guaranteed.)

Yes, I suppose that's a data race.

Well, given all this, I don't think making the GDAL objects Send is a good idea.

Ok, is there a work around for async functions in that case? Just so I don't have to sync this branch to master indefinitely :)

I don't know your app, but you can do something like:

make an IO thread or thread pool, each with an associated async MPSC channel
in your request handler, make a new one-shot channel for the response and send it to an IO thread, along with the request data
await on the one-shot channel for the response
in the IO threads, block while waiting for a request, process it when it arrives, then send the response back

https://github.com/georust/gdal/issues/425 is somewhat related, too.

Well, given all this, I don't think making the GDAL objects Send is a good idea.

Not safely. But an unsafe API, where the user is responsible for upholding GDAL's thread safety rules, would still be better than no API at all.

I don't know your app, but you can do something like:

make an IO thread or thread pool, each with an associated async MPSC channel
in your request handler, make a new one-shot channel for the response and send it to an IO thread, along with the request data
await on the one-shot channel for the response
in the IO threads, block while waiting for a request, process it when it arrives, then send the response back

#425 is somewhat related, too.

Thanks. The app is basically a rabbitmq consumer(deadpool-lapin ) running in a loop waiting for messages, once a message is received it then sends a message to an actor(coerce-rs), which is where gdal functions are invoked, after gdal finishes that actor further delegates work to other actors (db, s3 etc).
Coerce is working basically how you're describing this to be implemented, only thing is they don't provide synchronous handlers, which is why I had to make this workaround. I'm also thinking about implementing a synchronous handler that can return a Box<Pin<Future<...>>> and get resolved later, that way I could call gdal functions in the synchronous part of the handler and just pass the data to async part, at which point gdal structs can safely be dropped.
That being said I also like the idea of implementing a Sender struct to handle unsafe code.

I just ran into this myself for using SpatialRef and I'm not convinced the following statement is true.

A problem exists even with structs that don't have a lifetime parameter, like SpatialRef. It is also internally refcounted, so I can Clone it and Send the clone to another thread, then call (mutating) functions on both copies concurrently, causing UB.

While the underlying OGRSpatialReference from GDAL is internally reference counted, the implementation here does not expose or use any explicit reference counting methods. The implementation for Clone correctly calls OSRClone(...), rather than simply using a reference count:
https://github.com/georust/gdal/blob/204e4700f71dcc63f1f4993f2d0a5fe118f92208/src/spatial_ref/srs.rs#L27-L32
Examining the code on GDAL's side we can see when OSRClone(...) is called they make a proper deep copy as well, and don't just increase the reference count:
https://github.com/OSGeo/gdal/blob/e4026b077a092f614dc8a25b0025f01080eee47d/ogr/ogrspatialreference.cpp#L1376-L1392
Given the above, I believe at least SpatialRef can be safely marked as Send in its current implementation. I do think there could be some possibility for unsafe behavior between threads if a user chooses to use to_c_hsrs(&self) -> OGRSpatialReferenceH. I could see marking the method as unsafe in the event SpatialRef implements Send. I haven't reviewed any of the other types in detail at this point, so I cannot speak to them directly, but it's possible some other reference counted types could also be Send with close inspection.


ziti-edge-tunnel dump does not obey path parameter and does not complete dump

The dump subcommand  indicates it takes a path parameter, but does not appear to do so.
Also when it is dumped into the journal, the information is not complete, it cuts off before the services list is complete and other information is missing.

Importantly, the dump sub-command sends IPC to the daemon, which in turn writes the dump. If a path -p is given, then the daemon, running as user ziti, must have write permission on the specified directory.


exception_base decorator

I added a app.exception_base as an alternative to app.exception, the differences is that exception_base use a real try except syntax to test is a error is a subclass of another error. It can let user take better care of different kinds of exceptions.
The main reason I add this is that sanic expose the error messages very clearly to the client side, I think we need an approach to handle unexpected error and keep server information away from attackers.

@asdfghjBennyHuang did you decide this is unnecessary, since you were running in debug mode?


prototype

[ ] ~5 Puzzles~
[X] 1 Tutorial Puzzle
[X] Basic Companion in Astro.js
[X] Basic Workflow
[x] Basic Commands
[ ] ~Basic Internal Documentation~
[ ] ~Workflow documented~

Going in a different direction with the project. This code will be merged in.


Can't access HTTP using newly created login/password.

Hi guys,
First of all thank you a lot for your efforts on this project!
So I've a flashed BFUS yi 1080p home camera.

just added username/password fields here:

Saved
Then rebooted camera.
Now I can't access camera by HTTP: it prompts me login/password but they are incorrect.
Only re-flash helps.
Is there a way to set username/password ?
Thank you.

My apologies, I have to use '#' sign.
Sorry and thanks for your efforts.

@roleoroleo last question here:
I set login/password. But how can I reach this camera by ftp? I tried to use mentioned login/password but ftp server says "530 Login authentication failed"

ftp login is with root user.


Kuhn Poker Documentation:

Is there any documentation explaining what each of the 11 indices in the state space of Kuh Poker represents? I understand the gist of the game, but I need to know what the indices mean -- in order to compare my final models against the Nash equilibrium strategies.

Hi @xkianteb , the contents of the tensor are encoded here: https://github.com/deepmind/open_spiel/blob/b8c2ff8e9a4f5dad9b179217f740ddb0df967f7c/open_spiel/games/kuhn_poker.cc#L70
Though it is certainly stilo not obvious, we should have an English description in comments there.
@elkhrt @michalsustr I believe one of you changed this, can you give us the plain Englush description, along with an example? (I will then add it to the code in that spot.)

Hi @xkianteb , the contents of the tensor are encoded here: https://github.com/deepmind/open_spiel/blob/b8c2ff8e9a4f5dad9b179217f740ddb0df967f7c/open_spiel/games/kuhn_poker.cc#L70
Though it is certainly stilo not obvious, we should have an English description in comments there.
@elkhrt @michalsustr I believe one of you changed this, can you give us the plain Englush description, along with an example? (I will then add it to the code in that spot.)

@lanctot Thank you  :)

@lanctot Thank you  :)

Indeed for Kuhn we can put a detailed comment.
Something along the lines of:
  // WriteTensor encodes the observation for the current state.
  //
  // For example, for a state with history of actions "0 2 0 1 1", i.e. after:
  //
  //  - 0: player 0 was dealt card 0,
  //  - 2: player 1 was dealt card 2,
  //  - 0: player 0 passed
  //  - 1: player 1 bet
  //  - 1: player 0 bet
  //
  // the observations can vary, depending on the IIGObservationType specified
  // in the constructor:
  //
  // - kDefaultObsType
  //   player: ◉◯
  //   private_card: ◉◯◯
  //   pot_contribution = [2.0, 2.0]
  //
  // - kInfoStateObsType
  //   player: ◉◯
  //   private_card: ◉◯◯
  //   betting: ◉◯
  //            ◯◉
  //            ◯◉
  //
  // - kPublicObsType
  //   pot_contribution = [2.0, 2.0]
  //
  // - kPublicStateObsType
  //   betting: ◉◯
  //            ◯◉
  //            ◯◉
  //
  // For more information, please see comments in the observer.h file.

Also I made a program called SpielViz (under the Observations card) which does this nicely.

Indeed for Kuhn we can put a detailed comment.
Something along the lines of:
  // WriteTensor encodes the observation for the current state.
  //
  // For example, for a state with history of actions "0 2 0 1 1", i.e. after:
  //
  //  - 0: player 0 was dealt card 0,
  //  - 2: player 1 was dealt card 2,
  //  - 0: player 0 passed
  //  - 1: player 1 bet
  //  - 1: player 0 bet
  //
  // the observations can vary, depending on the IIGObservationType specified
  // in the constructor:
  //
  // - kDefaultObsType
  //   player: ◉◯
  //   private_card: ◉◯◯
  //   pot_contribution = [2.0, 2.0]
  //
  // - kInfoStateObsType
  //   player: ◉◯
  //   private_card: ◉◯◯
  //   betting: ◉◯
  //            ◯◉
  //            ◯◉
  //
  // - kPublicObsType
  //   pot_contribution = [2.0, 2.0]
  //
  // - kPublicStateObsType
  //   betting: ◉◯
  //            ◯◉
  //            ◯◉
  //
  // For more information, please see comments in the observer.h file.

Also I made a program called SpielViz (under the Observations card) which does this nicely.

For Kuhn Poker with two players. What do the last two dimensions of the state space represent?
Player 1's state space:
0:  1 if the current player is player 1
1:  1 if the current player is player 2
2:  1 if player 1 dealt card 0
3:  1 if player 1 dealt card 1
4:  1 if player 1 dealt card 2
5:  1 if player 1 'Pass'
6:  1 if player 1 'Bet'
7:  1 if player 2 'Pass'
8:  1 if player 2 'Bet'
9:
10:
Player 2's state space:
0: 1 if the current player is player 1
1:  1 if the current player is player 2
2:  1 if player 2 dealt card 0
3:  1 if player 2 dealt card 1
4:  1 if player 2 dealt card 2
5:  1 if player 1 'Pass'
6:  1 if player 1 'Bet'
7:  1 if player 2 'Pass'
8:  1 if player 2 'Bet'
9:
10:

For Kuhn Poker with two players. What do the last two dimensions of the state space represent?
Player 1's state space:
0:  1 if the current player is player 1
1:  1 if the current player is player 2
2:  1 if player 1 dealt card 0
3:  1 if player 1 dealt card 1
4:  1 if player 1 dealt card 2
5:  1 if player 1 'Pass'
6:  1 if player 1 'Bet'
7:  1 if player 2 'Pass'
8:  1 if player 2 'Bet'
9:
10:
Player 2's state space:
0: 1 if the current player is player 1
1:  1 if the current player is player 2
2:  1 if player 2 dealt card 0
3:  1 if player 2 dealt card 1
4:  1 if player 2 dealt card 2
5:  1 if player 1 'Pass'
6:  1 if player 1 'Bet'
7:  1 if player 2 'Pass'
8:  1 if player 2 'Bet'
9:
10:

9 and 10 are if player 1 passes / bets -- if the sequence is player 0 passes, player 1 bets, then player 0 gets to act again:

9 and 10 are if player 1 passes / bets -- if the sequence is player 0 passes, player 1 bets, then player 0 gets to act again:

@michalsustr I am completely sold on the GUI :) Thanks

@michalsustr I am completely sold on the GUI :) Thanks


Markdown ignores  anchors

Gitea version (or commit ref): 1.7.5
Git version: 2.17.1
Operating system: Ubuntu 18.04
Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[ ] Not relevant

Log gist:

Description
Moved repo from github to gitea, and it seems that anchor points are not working.
Anchors are made that way:
* [Introduction](#anchor-introduction)

# Introduction

The following works for me:
Table of contents
=================

* [Introduction](#introduction)

Introduction
============

Blah blah.

Please note I'm using id, not name.

There is a closed list of attributes allowed for each element. I'm surprised that id is in the list.

The IDs come for free from the header elements automatically. Spaces are turned into hyphens.


chore: make request timeout configurable in NotionDBLoader

I am also hitting some timeouts on the Notion DB fetching (~20 documents in the source notion db)
https://github.com/hwchase17/langchain/pull/2056#issuecomment-1530002441
^ this user makes a good point about making this underlying fetch logic extensible for retries/Idempotence, but this PR just makes the request timeout configurable

checking on the failed lint job, sec


No tests shown in Test Explorer

Today I updated my local master with the latest origin/master. However, there are no tests in the Test Explorer of Visual Studio. I did followings:
git fetch upstream
git rebase upstream/master
and then run restore.cmd in the Command Prompt
Am I missing something? Is Expecto.VisualStudio.TestAdapter needed to be installed?

If you want to see running tests in The Test Explorer VS then yes you need it (I'm never used Expecto.VisualStudio.TestAdapter although). But you can run tests without it like console app.

I think Test Explorer makes our life easier. Is it possible to add the TestAdapter to the solution? I found this.

I've added the test adapter. The tests now do show up in the test explorer on my machine. Does that work for you?
I've noticed that the test project now takes quite some time to compile. Not sure why exactly, but it seems to correlate with the switch to Expecto.

at least, it doesn't work for me. Adapter couldn't find any suitable tests.

Even after rebuilding the test project?

In the Command Prompt, everything is OK. But at rebuilding on VS 2017 15.4.4, I got an error in the Tests Output: System.ArgumentException: An item with the same key has already been added.
Related issue is found at this.

In theory this should not affect us, since we already use Cecil 0.10-beta7. I also cannot repro yet on my side (works for me after restarting VS and rebuilding the test project). I wonder what is different between our setups.
Switching to FCS (instead of the system installed F# compiler) could remove one potential difference; I intended to do that anyway.

I've just tried it on another machine and it worked as well, in VS 2017 15.4.4, 15.5 preview 4 (after installing the test tools) and also on VS 2015.

But at rebuilding on VS 2017 15.4.4, I got an error in the Tests

The same error

If the change to FCS doesn't not help, I may have to revert. For me, no longer needing a test runner in the fist place makes things more straight forward, direct and simpler (especially also looking forward supporting .Net Standard). But it is important that this works for all contributors.

When starting UnitTests, an Exception panel appears on the problematic line and I can edit it. For me, it is easy and much more intuitive.


No background colour on light theme

Checklist:

[/] I updated to the latest version available
[/] I cleared the cache of my browser (Using android companion app)

Release with the issue: v2.1.4
Last working release (if known):
Browser and Operating System:
Android Companion App Android 14 OneUI 6.1
Description of problem:
On the Android companion app, using the light theme the entities blend in with the white background making it visually unappealing. It is difficult to describe the problem but I believe if shown alongside the dark theme it is clear what the issue is.

Notice how for the dark theme even when switches are off or it is an entity there is a dark background contrasting it whereas it is just white for the light theme.
I am using bubble card in a vertical stack.
Javascript errors shown in the web inspector (if applicable):

Additional information:

There's not much I can do about which theme colors custom cards use without making something in Home Assistant look incorrect. In this case I can change light mode --secondary-background-color to something other than pure white, but I can't do anything about the icon color being too light without change the theme accent color.
Try the 2.1.5 beta. It changes the light mode secondary background color.

You could also use bubble card's build in style options to change the background and icon colors.


ImageStacks does not calculate the correct origin (or offset) when a partial sequence is imported.

This causes alignment issues if two versions (e.g., partial sequence and full sequence is loaded).
I am not sure what how to approach this. Somehow we have to know the geometry of the full volume, but I can't think of a way to this consistently. But a way to keep these lined up correctly would be important. Especially if and when we implement the ROI based partial volume import too...

Certainly we cannot do this automatically, but we could give people an option to enter it manually.

OK. Let's just keep this open to discuss.
I think it might be possible to parse the whole sequence, but then do the selection in the table. That way we would at least know where we are in the Z-stack. This would require changing the load behavior such that they need to point a folder (as oppose to select the list of files they want to load).

There would be a tradeoff because currently you can select a subset of files from a directory.  It seems not-uncommon to have multiple stacks in a folder with custom naming conventions.  Forcing people to put their stacks in a folder may or may not be convenient.  Anyway I'm open to doing what's most productive for the users.

Linking this to #122. Perhaps in parser version if less than the fullset is selected, we can calculate and write the necessary offset.

closed per #139


CLOUDSTACK-9317: Fixed disable static nat on leaving ips on interface

FIxed issue in disabling multiple static  nat simultaneously.
This patch has taken changes from the PR 1450 and added the missing parts
https://github.com/apache/cloudstack/pull/1450

Thanks for adding the missing parts. Here is the PR that was open against 4.8 for this, which I guess can be closed now: https://github.com/apache/cloudstack/pull/1623
I guess the comment from @jburwell still applies to this.

Question: would #1907 be relevant to this? That change relied on sending all the IPs to the router, but under this change, we will be sending one at a time.

I'm looking at the DataBag code, and it seems that it loads information from the data located at /etc/cloudstack/ and therefore 1907 should work fine with this, ASSUMING that is smart enough to recognize that the IP should no longer be there.
I think this is a scenario that should definitely be tested as it has the potential to break the whole PR.

We have been testing this PR internally for some time now, and we have seen some strange arping issues. We have seen that /etc/cloudstack/ips.json on the router has IPs on them that aren't cleaned up. Since #1908 is now merged, I'm worried that the changes in this PR will not play well with #1908.
Specifically, we have seen that IPs left over in the ips.json file can be stuck on "add": true even if the IP is no longer on the account.
Thus, the code that was added in PR 1907 concerns me:
 if not address['add'] and not ip.configured():
    logging.info("Skipping %s as the add flag is set to %s " % (address['public_ip'], address['add']))
    continue

The if condition fails in a case we've been investigating. Because our IP is "add": true, but configured() returns False, the IP gets reconfigured anyway. This doesn't add the IP to the router's interface, but it does run an arping command (see CsAddress.py). Essentially, if this PR is merged as-is, we might wind up with a regression on CLOUDSTACK-9500.
I will do a bit of manual testing combining both #1908 and #1907 to see what happens. It may just be that after restarting the network (and thus cleaning the router), these issues will vanish.

@ProjectMoon
I have seen the issue of ips.json having the "add:true" while I am testing this PR. I tested this PR by manually removing the ip or setting add to false. Also I tested with the cleanup restart. With correct ips.json I did not see any issues with this PR.
I think the ips.json problem is independent of this PR that need to be fixed.

@jayapalu Quite possible, yes. It could be fixed by adding another condition to the check that was added with #1907. It could also be "fixed" by checkiing if configured() returns True in the arpPing() method of the CsIp class. But I'm guessing that it doesn't get properly deleted from the DataBag when it's removed from the router. Thus it just gets written to /etc/cloudstack/ips.json again.

@ProjectMoon  The ip issue can be worked as separate ticket/PR. It is an isolated issue, it is not having any dependency with this PR. So we will get this PR in and create a separate ticket for the ip issue. What do you say ?

@ProjectMoon
I have today this PR after rebasing latest master. I did not observe the add:true for the removed ip.
Here is output from the ips.json and ip addr show output.
Here is the output:
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 06:f6:cc:00:00:0e brd ff:ff:ff:ff:ff:ff
inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global eth2
inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global secondary eth2
"eth2": [
    {
        "add": true,
        "broadcast": "<IP_ADDRESS>",
        "cidr": "<IP_ADDRESS>/24",
        "device": "eth2",
        "first_i_p": true,
        "gateway": "<IP_ADDRESS>",
        "netmask": "<IP_ADDRESS>",
        "network": "<IP_ADDRESS>/24",
        "new_nic": false,
        "nic_dev_id": 2,
        "nw_type": "public",
        "one_to_one_nat": false,
        "public_ip": "<IP_ADDRESS>",
        "size": "24",
        "source_nat": true,
        "vif_mac_address": "06:4a:54:00:00:0e"
    },
    {
        "add": false,
        "broadcast": "<IP_ADDRESS>",
        "cidr": "<IP_ADDRESS>/24",
        "device": "eth2",
        "first_i_p": true,
        "gateway": "<IP_ADDRESS>",
        "netmask": "<IP_ADDRESS>",
        "network": "<IP_ADDRESS>/24",
        "new_nic": false,
        "nic_dev_id": 2,
        "nw_type": "public",
        "one_to_one_nat": true,
        "public_ip": "<IP_ADDRESS>",
        "size": "24",
        "source_nat": true,
        "vif_mac_address": "06:b5:36:00:00:13"
    },
    {
        "add": false,
        "broadcast": "<IP_ADDRESS>",
        "cidr": "<IP_ADDRESS>/24",
        "device": "eth2",
        "first_i_p": true,
        "gateway": "<IP_ADDRESS>",
        "netmask": "<IP_ADDRESS>",
        "network": "<IP_ADDRESS>/24",
        "new_nic": false,
        "nic_dev_id": 2,
        "nw_type": "public",
        "one_to_one_nat": true,
        "public_ip": "<IP_ADDRESS>",
        "size": "24",
        "source_nat": true,
        "vif_mac_address": "06:6d:c8:00:00:14"
    },
    {
        "add": false,
        "broadcast": "<IP_ADDRESS>",
        "cidr": "<IP_ADDRESS>/24",
        "device": "eth2",
        "first_i_p": true,
        "gateway": "<IP_ADDRESS>",
        "netmask": "<IP_ADDRESS>",
        "network": "<IP_ADDRESS>/24",
        "new_nic": false,
        "nic_dev_id": 2,
        "nw_type": "public",
        "one_to_one_nat": true,
        "public_ip": "<IP_ADDRESS>",
        "size": "24",
        "source_nat": true,
        "vif_mac_address": "06:32:90:00:00:17"
    },
    {
        "add": true,
        "broadcast": "<IP_ADDRESS>",
        "cidr": "<IP_ADDRESS>/24",
        "device": "eth2",
        "first_i_p": true,
        "gateway": "<IP_ADDRESS>",
        "netmask": "<IP_ADDRESS>",
        "network": "<IP_ADDRESS>/24",
        "new_nic": false,
        "nic_dev_id": 2,
        "nw_type": "public",
        "one_to_one_nat": true,
        "public_ip": "<IP_ADDRESS>",
        "size": "24",
        "source_nat": true,
        "vif_mac_address": "06:83:68:00:00:18"
    }

Hi, that's great news.

@ProjectMoon  Can you please review it.

@jayapalu can you change the PR base branch to 4.9?

ACS CI BVT Run
Sumarry:
Build Number 3
Hypervisor xenserver
NetworkType Advanced
Passed=623
Failed=290
Skipped=58
Link to logs Folder (search by build_no): https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0
Failed tests:

test_dhcp_dns_offload.py

ContextSuite context=TestDeployVMs>:setup Failed

test_affinity_groups_projects.py

test_01_deploy_vm_anti_affinity_group Failed

test_02_deploy_vm_anti_affinity_group_fail_on_not_enough_hosts Failed

test_01_list_aff_grps_for_vm Failed

test_02_list_multiple_aff_grps_for_vm Failed

test_01_update_aff_grp_by_ids Failed

test_ps_domain_limits.py

test_04_create_template_snapshot Failed

test_ss_domain_limits.py

test_04_create_template_delete_account Failed

test_04_create_template_delete_account Failing since 2 runs

test_01_multiple_domains_secondary_storage_limits Failed

test_01_multiple_domains_secondary_storage_limits Failing since 2 runs

test_02_multiple_domains_secondary_storage_counts Failed

test_deploy_vm_userdata_multi_nic.py

test_deployvm_multinic Failed

test_vpn_service.py

test_01_VPN_service Failed

test_organization_states.py

ContextSuite context=TestOrganizationStates>:setup Failed

test_escalations_snapshots.py

ContextSuite context=TestSnapshots>:setup Failed

test_dynamic_compute_offering.py

test_max_account_memory_scale_VM_1_ADMIN_ACCOUNT Failed

test_max_account_memory_scale_VM_2_USER_ACCOUNT Failed

test_deploy_VM_with_affinity_group_1_ADMIN_ACCOUNT Failed

test_deploy_VM_with_affinity_group_2_USER_ACCOUNT Failed

ContextSuite context=TestDynamicServiceOffering>:setup Failed

test_change_so_running_vm_dynamic_to_dynamic_1_ADMIN_ACCOUNT Failed

test_change_so_running_vm_dynamic_to_dynamic_2_USER_ACCOUNT Failed

test_change_so_running_vm_dynamic_to_static_1_ADMIN_ACCOUNT Failed

test_change_so_running_vm_dynamic_to_static_2_USER_ACCOUNT Failed

test_change_so_running_vm_static_to_dynamic_1_ADMIN_ACCOUNT Failed

test_change_so_running_vm_static_to_dynamic_2_USER_ACCOUNT Failed

test_change_so_running_vm_static_to_static_1_ADMIN_ACCOUNT Failed

test_change_so_running_vm_static_to_static_2_USER_ACCOUNT Failed

test_change_so_stopped_vm_dynamic_to_dynamic_1_ADMIN_ACCOUNT Failed

test_change_so_stopped_vm_dynamic_to_dynamic_2_USER_ACCOUNT Failed

test_change_so_stopped_vm_dynamic_to_static_1_ADMIN_ACCOUNT Failed

test_change_so_stopped_vm_dynamic_to_static_2_USER_ACCOUNT Failed

test_change_so_stopped_vm_static_to_dynamic_1_ADMIN_ACCOUNT Failed

test_change_so_stopped_vm_static_to_dynamic_2_USER_ACCOUNT Failed

test_change_so_stopped_vm_static_to_static_1_ADMIN_ACCOUNT Failed

test_ps_resource_limits_volume.py

test_attach_volume_exceeding_primary_limits Failed

test_vpc.py

test_07_restart_network_vm_running Failed

test_08_delete_vpc Failed

test_11_deploy_vm_wo_network_netdomain Failed

test_13_deploy_vm_with_vpc_netdomain Failed

test_14_deploy_vm_1 Failed

test_15_deploy_vm_2 Failed

test_16_deploy_vm_for_user_by_admin Failed

test_21_deploy_vm_with_gateway_ip Failed

test_22_vpn_customer_gw_with_hostname Failed

test_non_contiguous_vlan.py

test_01_add_non_contiguous_ranges Failed

test_project_usage.py

ContextSuite context=TestLBRuleUsage>:setup Failed

ContextSuite context=TestNatRuleUsage>:setup Failed

ContextSuite context=TestPublicIPUsage>:setup Failed

ContextSuite context=TestSnapshotUsage>:setup Failed

ContextSuite context=TestVmUsage>:setup Failed

ContextSuite context=TestVolumeUsage>:setup Failed

ContextSuite context=TestVpnUsage>:setup Failed

test_ps_max_limits.py

test_01_deploy_vm_domain_limit_reached Failed

test_02_deploy_vm_account_limit_reached Failed

test_03_deploy_vm_project_limit_reached Failed

test_project_resources.py

test_07_associate_public_ip Failed

test_vpc_network_staticnatrule.py

test_01_VPC_StaticNatRuleCreateStoppedState Failed

test_03_VPC_StopCreateMultipleStaticNatRuleStopppedState Failed

test_04_VPC_CreateMultipleStaticNatRule Failed

test_05_network_services_VPC_DeleteAllPF Failed

test_06_network_services_VPC_DeleteAllMultiplePF Failed

test_redundant_router_services.py

test_enableVPNOverRvR Failed

test_resource_limits.py

test_01_vm_per_account Failed

test_02_publicip_per_account Failed

test_03_snapshots_per_account Failed

test_04_volumes_per_account Failed

test_05_templates_per_account Failed

test_escalations_vpncustomergateways.py

test_01_list_vpncustomergateways_pagination Failed

test_02_update_vpncustomergateways Failed

test_multiple_public_interfaces.py

test_iptable_rules Failed

ContextSuite context=TestPortForwarding>:setup Failing since 8 runs

ContextSuite context=TestRouting>:setup Failed

ContextSuite context=TestStaticNat>:setup Failed

test_network_services_VPC_CreatePF Failed

test_network_services_VPC_CreatePF Failing since 2 runs

test_cpu_project_limits.py

test_01_project_counts_start_stop_instance Failed

test_02_project_counts_migrate_instance Failed

test_03_project_counts_delete_instance Failed

test_routers.py

test_01_RouterStopCreateFW Failed

test_overcommit.py

test_01_cluster_settings Failed

test_02_Overcommit_factor Failed

test_03_cluste_capacity_check Failed

test_04_zone_capacity_check Failed

test_custom_hostname.py

test_01_custom_hostname_instancename_false Failed

test_snapshots.py

test_01_createVM_snapshotTemplate Failed

ContextSuite context=TestSnapshotEvents>:setup Failed

test_01_volume_from_snapshot Failed

test_02_snapshot_data_disk Failed

test_03_snapshot_detachedDisk Failed

test_04_delete_snapshot Failed

test_07_template_from_snapshot Failed

test_egress_fw_rules.py

test_01_1_egress_fr1 Failed

test_01_2_egress_fr1 Failed

test_01_egress_fr1 Failed

test_02_1_egress_fr2 Failed

test_02_2_egress_fr2 Failed

test_02_egress_fr2 Failed

test_03_1_egress_fr3 Failed

test_03_egress_fr3 Failed

test_04_1_egress_fr4 Failed

test_04_egress_fr4 Failed

test_06_1_egress_fr6 Failed

test_06_egress_fr6 Failed

test_07_1_egress_fr7 Failed

test_07_egress_fr7 Failed

test_09_1_egress_fr9 Failed

test_redundant_router_cleanups.py

test_restart_network_with_destroyed_masterVR Failed

test_ss_max_limits.py

test_01_deploy_vm_domain_limit_reached Failing since 2 runs

test_02_deploy_vm_account_limit_reached Failing since 2 runs

test_03_deploy_vm_project_limit_reached Failing since 2 runs

test_ss_project_limits.py

test_01_register_template_with_project Failed

test_memory_limits.py

test_01_stop_start_instance Failed

test_02_migrate_instance Failed

test_03_delete_instance Failed

test_01_stop_start_instance Failing since 2 runs

test_02_migrate_instance Failing since 2 runs

test_vpc_network_pfrules.py

test_01_network_services_VPC_StopCreatePF Failed

test_02_network_services_VPC_CreatePF Failed

test_03_network_services_VPC_StopCreateMultiplePF Failed

test_04_network_services_VPC_CreateMultiplePF Failed

test_05_network_services_VPC_StopDeletePF Failed

test_06_network_services_VPC_DeletePF Failed

test_07_network_services_VPC_StopDeleteAllPF Failed

test_08_network_services_VPC_DeleteAllPF Failed

test_09_network_services_VPC_StopDeleteAllMultiplePF Failed

test_10_network_services_VPC_DeleteAllMultiplePF Failed

test_ip_reservation.py

test_reservation_after_router_restart Failed

test_vm_create_after_reservation Failed

test_vm_create_outside_cidr_after_reservation Failed

test_ip_reservation_in_multiple_networks_same_account Failed

test_nat_rules_1_nat_rule Failed

test_nat_rules_2_static_nat_rule Failed

test_update_cidr_multiple_vms_not_all_inclusive Failed

test_update_cidr_single_vm_not_inclusive Failed

test_vm_create_after_reservation Failing since 2 runs

test_vm_create_outside_cidr_after_reservation Failing since 2 runs

test_restart_network_with_cleanup_1_True Failed

test_vpc_vms_deployment.py

test_01_deploy_vms_in_network Failed

test_02_deploy_vms_delete_network Failed

test_03_deploy_vms_delete_add_network Failed

test_04_deploy_vms_delete_add_network_noLb Failed

test_05_create_network_max_limit Failed

test_06_delete_network_vm_running Failed

test_07_delete_network_with_rules Failed

test_vpc_network.py

ContextSuite context=TestVPCNetworkGc>:setup Failed

test_mm_project_limits.py

test_01_project_vmlifecycle_start_stop_instance Failed

test_02_project_vmlifecycle_migrate_instance Failed

test_03_project_vmlifecycle_delete_instance Failed

test_escalations_instances.py

test_13_attach_detach_iso Failed

test_14_vm_snapshot_pagination Failed

test_15_revert_vm_to_snapshot Failed

test_16_list_vm_volumes_pagination Failed

test_18_stopped_vm_change_service Failed

test_19_create_reset_vm_sshkey Failed

test_20_update_vm_displayname_group Failed

test_21_restore_vm Failed

test_22_deploy_vm_multiple_networks Failed

test_24_deploy_vm_with_static_ip_ES1662 Failed

test_25_ip_reallocation_ES1377 Failed

test_27_VM_restore_ES3467 Failed

test_28_VM_restore_ES3467 Failed

test_01_list_instances_pagination Failed

test_02_list_Running_vm Failed

test_03_list_Stopped_vm Failed

test_04_list_Destroyed_vm Failed

test_05_list_vm_by_id Failed

test_06_list_vm_by_name Failed

test_07_list_vm_by_name_state Failed

test_10_list_vm_by_zone_name_state Failed

test_11_register_reset_vm_sshkey Failed

test_12_running_vm_change_service Failed

test_13_vm_nics Failed

test_acl_isolatednetwork.py

ContextSuite context=TestIsolatedNetwork>:setup Failed

test_cpu_domain_limits.py

test_01_multiple_core_vm_start_stop_instance Failed

test_02_multiple_core_vm_migrate_instance Failed

test_03_multiple_core_vm_delete_instance Failed

test_04_deploy_multiple_vm_with_multiple_core Failed

test_01_multiple_child_domains Failed

test_escalations_networks.py

test_03_list_vpc_pagination Failed

test_04_create_vpc_with_networkdomain Failed

test_06_create_network_in_vpc Failed

test_10_list_networks_in_vpc Failed

test_11_update_vpc Failed

test_12_list_create_delete_networkACL Failed

test_19_create_list_reset_delete_vpnconnections Failed

test_accounts.py

ContextSuite context=TestAddVmToSubDomain>:setup Failed

test_DeleteDomain Failed

test_forceDeleteDomain Failed

test_01_user_remove_VM_running Failed

ContextSuite context=TestTemplateHierarchy>:setup Failed

test_LoginApiDomain Failed

test_LoginApiUuidResponse Failed

test_ps_limits.py

test_create_template_snapshot_1_root_domain_admin Failed

test_create_template_snapshot_2_child_domain_admin Failed

test_mm_max_limits.py

test_02_deploy_vm_account_limit_reached Failing since 3 runs

test_04_deployVm__account_limit_reached Failed

test_cpu_max_limits.py

test_02_deploy_vm_account_limit_reached Failing since 4 runs

test_04_deployVm__account_limit_reached Failing since 2 runs

test_escalation_listTemplateDomainAdmin.py

test_listtemplate Failed

test_portable_ip.py

test_associate_ip_address_services_enable_disable Failed

test_list_portable_ip_range_non_root_admin Failed

test_affinity_groups.py

test_03_delete_aff_grp_with_vms Failed

test_01_deploy_vm_without_aff_grp Failed

test_02_deploy_vm_by_aff_grp_name Failed

test_03_deploy_vm_by_aff_grp_id Failed

test_04_deploy_vm_anti_affinity_group Failed

test_05_deploy_vm_by_id Failed

test_08_deploy_vm_multiple_aff_grps Failed

test_09_deploy_vm_multiple_aff_grps Failed

test_01_list_aff_grps_for_vm Failing since 2 runs

test_02_list_multiple_aff_grps_for_vm Failing since 2 runs

test_07_list_all_vms_in_aff_grp Failed

test_02_update_aff_grp_by_names Failed

test_03_update_aff_grp_for_vm_with_no_aff_grp Failed

test_05_update_aff_grp_on_running_vm Failed

test_acl_listvolume.py

ContextSuite context=TestVolumeList>:setup Failed

test_mm_domain_limits.py

test_01_change_service_offering Failed

test_02_migrate_vm Failed

test_03_delete_vm Failed

test_04_deploy_multiple_vm Failed

test_01_multiple_child_domains Failing since 2 runs

test_blocker_bugs.py

ContextSuite context=TestDataPersistency>:setup Failed

ContextSuite context=TestNATRules>:setup Failed

ContextSuite context=TestRouterRestart>:setup Failed

test_01_list_routers_admin Failed

test_01_create_template Failed

test_vpc_network_internal_lbrules.py

test_02_internallb_rules_traffic Failed

test_03_internallb_rules_vpc_network_restarts_traffic Failed

test_04_internallb_appliance_operations_traffic Failed

test_add_remove_network.py

ContextSuite context=TestAddNetworkToVirtualMachine>:setup Failed

ContextSuite context=TestFailureScenariosAddNetworkToVM>:setup Failed

ContextSuite context=TestFailureScenariosRemoveNicFromVM>:setup Failed

ContextSuite context=TestFailureScenariosUpdateVirtualMachineNIC>:setup Failed

ContextSuite context=TestRemoveNetworkFromVirtualMachine>:setup Failed

ContextSuite context=TestUpdateVirtualMachineNIC>:setup Failed

test_escalations_ipaddresses.py

test_11_create_delete_firewallrule Failed

test_lb_secondary_ip.py

test_01_lb_rule_for_primary_ip Failed

test_02_lb_rule_for_primary_ip Failed

test_03_lb_rule_for_primary_and_secondary_ip Failed

test_04_lb_rule_primary_secondary_multiple_vms Failed

test_05_lb_rule_wrong_vm_id Failed

test_06_lb_rule_wrong_vm_ip Failed

test_08_lb_rule_remove_used_ip Failed

test_11_ssh_to_secondary_ip Failed

test_13_delete_lb_rule Failed

test_14_remove_lb_rule_secondary_ip Failed

test_15_remove_lb_rule_primary_ip Failed

test_16_delete_vm_from_lb_rule Failed

test_20_destroy_recover_vm Failed

test_21_modify_lb_rule_algorithm Failed

test_09_lbvmips_true Failed

test_10_lbvmips_false Failed

test_17_restart_router Failed

test_18_restart_network_cleanup_true Failed

test_19_restart_network_cleanup_false Failed

test_22_network_gc Failed

test_volumes.py

test_01_volume_attach_detach Failed

test_01_volume_attach_detach Failing since 2 runs

test_02_root_volume_attach_detach Failed

ContextSuite context=TestAttachVolume>:setup Failed

ContextSuite context=TestAttachVolumeISO>:setup Failed

ContextSuite context=TestMigrateVolume>:setup Failed

ContextSuite context=TestVolumes>:setup Failing since 12 runs

test_acl_listsnapshot.py

ContextSuite context=TestSnapshotList>:setup Failed

test_stopped_vm.py

test_deploy_vm_password_enabled Failed

test_snapshot_limits.py

ContextSuite context=TestSnapshotLimit>:setup Failed

test_escalations_templates.py

test_01_list_templates_pagination Failed

test_02_download_template Failed

test_03_edit_template_details Failed

test_ss_limits.py

test_01_register_template_1_root_domain_admin Failed

test_01_register_template_2_child_domain_admin Failed

test_ps_resize_volume.py

test_02_increase_volume_size_above_account_limit Failed

test_03_increase_volume_size_above_domain_limit Failed

test_usage.py

ContextSuite context=TestLBRuleUsage>:setup Failing since 2 runs

ContextSuite context=TestNatRuleUsage>:setup Failing since 2 runs

ContextSuite context=TestPublicIPUsage>:setup Failing since 2 runs

ContextSuite context=TestSnapshotUsage>:setup Failing since 2 runs

ContextSuite context=TestVmUsage>:setup Failing since 2 runs

ContextSuite context=TestVolumeUsage>:setup Failing since 2 runs

ContextSuite context=TestVpnUsage>:setup Failing since 2 runs

test_vpc_vm_life_cycle.py

test_06_migrate_instance_in_network Failed

test_07_migrate_instance_in_network Failed

test_project_limits.py

test_06_volumes_per_project Failed

test_07_templates_per_project Failed

test_templates.py

test_01_create_template Failing since 2 runs

test_assign_vm.py

test_13_move_across_subdomain_vm_snapshot Failed

test_15_move_across_subdomain_account_limit Failed

test_16_move_across_subdomain_volume_and_account_limit Failed

Skipped tests:
test_03_copy_template
ContextSuite context=TestvGPUWindowsVm>:setup
ContextSuite context=TestTemplateUsage>:setup
test_02_create_vpc_from_offering_with_regionlevelvpc_service_capability
test_03_deploy_vms_in_vpc_with_regionlevelvpc
test_02_cancel_host_maintenace_with_migration_jobs
ContextSuite context=TestInstanceNameFlagTrue>:setup
test_04_deploy_multiple_vm_with_multiple_cpus
test_05_1_egress_fr5
test_05_egress_fr5
test_08_1_egress_fr8
test_08_egress_fr8
test_04_vpn_tag
ContextSuite context=TestAffinityRules>:setup
ContextSuite context=TestAntiAffinityRules>:setup
test_02_create_vpc_from_offering_with_distributedrouter_service_capability
test_03_deploy_vms_in_vpc_with_distributedrouter
test_04_deploy_multiple_vm
ContextSuite context=TestProjectCreationNegative>:setup
ContextSuite context=TestProjectInviteRequiredTrue>:setup
ContextSuite context=TestProjectInviteTimeout>:setup
test_RVR_network
test_01_create_network_2_network_offering_vpcns
test_02_create_network_fail_2_network_offering_vpcns
test_04_create_multiple_networks_with_lb_1_network_offering
test_04_create_multiple_networks_with_lb_2_network_offering_vpcns
test_06_create_network_with_rvr
test_09_create_network_shared_nwoff_2_network_offering_vpcns
test_01_create_network_outside_range_2_network_offering_vpcns
test_03_create_network_inside_range_2_network_offering_vpcns
test_04_create_network_overlapping_range_2_network_offering_vpcns
test_05_create_network_diff_account_2_network_offering_vpcns
test_02_concurrent_snapshot_global_limit
test_01_migrate_vm_with_volume
test_02_migrate_volume
test_02_migrate_vm
test_03_delete_vm
test_01_deploy_vm_with_implicit_planner
test_destroy_recover_vm_1_root_domain_admin
test_destroy_recover_vm_2_child_domain_admin
test_04_copy_iso
test_04_update_aff_grp_remove_all
test_01_host_ha_with_nfs_storagepool_with_vm
test_02_host_ha_with_local_storage_and_nfs
test_03_host_ha_with_only_local_storage
ContextSuite context=TestTemplates>:setup
test_07_lb_rule_used_ip
test_12_ssh_to_primary_secondary_ip
test_09_stop_vm_migrate_vol
test_04_copy_template
test_04_copy_template_1_root_domain_admin
test_04_copy_template_2_child_domain_admin
test1_attach_volume_ide
test2_attach_ISO_in_CentOSVM
ContextSuite context=TestTemplateUsage>:setup
test_createSharedNetwork_usedVlan
test_01_addLdapConfiguration
ContextSuite context=TestTemplates>:setup
Passed test suits:
None
test_redundant_router_upgrades.py
test_VirtualRouter_alerts.py
test_regions_accounts.py
test_acl_isolatednetwork_delete.py
test_invalid_gw_nm.py
test_haproxy.py
test_vpc_offerings.py
test_snapshots_improvement.py
test_vpn_users.py
test_vpc_routers.py
test_acl_listvm.py
test_simultaneous_volume_attach.py
test_deploy_vm_userdata_reg.py
test_escalations_routers.py
test_vpc_network_lbrules.py
test_update_vm.py
test_escalations_volumes.py
test_regions.py
test_projects.py
test_acl_sharednetwork.py
test_allocation_states.py
test_snapshot_gc.py
test_vm_passwdenabled.py
test_network_offering.py
None

ACS CI BVT Run
Sumarry:
Build Number 5
Hypervisor xenserver
NetworkType Advanced
Passed=464
Failed=341
Skipped=53
Link to logs Folder (search by build_no): https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0
Failed tests:

test_dhcp_dns_offload.py

ContextSuite context=TestDeployVMs>:setup Failing since 2 runs

test_affinity_groups_projects.py

test_01_deploy_vm_anti_affinity_group Failing since 2 runs

test_02_deploy_vm_anti_affinity_group_fail_on_not_enough_hosts Failing since 2 runs

test_01_list_aff_grps_for_vm Failing since 3 runs

test_02_list_multiple_aff_grps_for_vm Failing since 3 runs

test_07_list_all_vms_in_aff_grp Failing since 2 runs

test_01_update_aff_grp_by_ids Failed

test_ps_domain_limits.py

test_04_create_template_snapshot Failing since 2 runs

test_VirtualRouter_alerts.py

test_01_VRServiceFailureAlerting Failed

test_ss_domain_limits.py

test_04_create_template_delete_account Failing since 3 runs

test_04_create_template_delete_account Failing since 4 runs

test_01_multiple_domains_secondary_storage_limits Failing since 3 runs

test_02_multiple_domains_secondary_storage_counts Failing since 2 runs

test_deploy_vm_userdata_multi_nic.py

test_deployvm_multinic Failing since 2 runs

test_vpn_service.py

test_01_VPN_service Failing since 2 runs

test_organization_states.py

ContextSuite context=TestOrganizationStates>:setup Failing since 2 runs

test_escalations_snapshots.py

ContextSuite context=TestSnapshots>:setup Failing since 2 runs

test_haproxy.py

test_01_create_sticky_policy_default_values Failed

test_02_create_sticky_policy_custom_values Failed

test_03_supported_policies_by_network Failed

test_04_delete_lb_rule Failed

test_05_error_alerts_after_create Failed

test_06_release_ip Failed

test_07_delete_account Failed

test_08_create_policy_router_stopped Failed

test_09_create_policy_router_destroy Failed

test_10_create_policy_enable_disable_vpn Failed

test_11_invalid_params Failed

test_dynamic_compute_offering.py

test_max_account_cpus_scale_VM_1_ADMIN_ACCOUNT Failed

test_max_account_cpus_scale_VM_2_USER_ACCOUNT Failed

test_max_account_memory_scale_VM_1_ADMIN_ACCOUNT Failing since 2 runs

test_max_account_memory_scale_VM_2_USER_ACCOUNT Failing since 2 runs

test_deploy_VM_with_affinity_group_1_ADMIN_ACCOUNT Failing since 2 runs

test_deploy_VM_with_affinity_group_2_USER_ACCOUNT Failing since 2 runs

ContextSuite context=TestDynamicServiceOffering>:setup Failing since 2 runs

test_change_so_running_vm_dynamic_to_dynamic_1_ADMIN_ACCOUNT Failing since 2 runs

test_change_so_running_vm_dynamic_to_dynamic_2_USER_ACCOUNT Failing since 2 runs

test_change_so_running_vm_dynamic_to_static_1_ADMIN_ACCOUNT Failing since 2 runs

test_change_so_running_vm_dynamic_to_static_2_USER_ACCOUNT Failing since 2 runs

test_change_so_running_vm_static_to_dynamic_1_ADMIN_ACCOUNT Failing since 2 runs

test_change_so_running_vm_static_to_dynamic_2_USER_ACCOUNT Failing since 2 runs

test_change_so_running_vm_static_to_static_1_ADMIN_ACCOUNT Failing since 2 runs

test_change_so_running_vm_static_to_static_2_USER_ACCOUNT Failing since 2 runs

test_change_so_stopped_vm_dynamic_to_dynamic_1_ADMIN_ACCOUNT Failing since 2 runs

test_change_so_stopped_vm_dynamic_to_dynamic_2_USER_ACCOUNT Failing since 2 runs

test_change_so_stopped_vm_dynamic_to_static_1_ADMIN_ACCOUNT Failing since 2 runs

test_change_so_stopped_vm_dynamic_to_static_2_USER_ACCOUNT Failing since 2 runs

test_change_so_stopped_vm_static_to_dynamic_1_ADMIN_ACCOUNT Failing since 2 runs

test_change_so_stopped_vm_static_to_dynamic_2_USER_ACCOUNT Failing since 2 runs

test_change_so_stopped_vm_static_to_static_1_ADMIN_ACCOUNT Failing since 2 runs

test_change_so_stopped_vm_static_to_static_2_USER_ACCOUNT Failed

test_ps_resource_limits_volume.py

test_attach_volume_exceeding_primary_limits Failing since 2 runs

test_vpc.py

test_07_restart_network_vm_running Failing since 2 runs

test_08_delete_vpc Failing since 2 runs

test_11_deploy_vm_wo_network_netdomain Failing since 2 runs

test_13_deploy_vm_with_vpc_netdomain Failing since 2 runs

test_14_deploy_vm_1 Failing since 2 runs

test_15_deploy_vm_2 Failing since 2 runs

test_16_deploy_vm_for_user_by_admin Failing since 2 runs

test_21_deploy_vm_with_gateway_ip Failing since 2 runs

test_22_vpn_customer_gw_with_hostname Failing since 2 runs

test_non_contiguous_vlan.py

test_01_add_non_contiguous_ranges Failing since 2 runs

test_05_remove_used_range Failed

test_project_usage.py

ContextSuite context=TestLBRuleUsage>:setup Failing since 3 runs

ContextSuite context=TestNatRuleUsage>:setup Failing since 3 runs

ContextSuite context=TestPublicIPUsage>:setup Failing since 3 runs

ContextSuite context=TestSnapshotUsage>:setup Failing since 3 runs

ContextSuite context=TestVmUsage>:setup Failing since 3 runs

ContextSuite context=TestVolumeUsage>:setup Failing since 3 runs

ContextSuite context=TestVpnUsage>:setup Failing since 3 runs

test_ps_max_limits.py

test_01_deploy_vm_domain_limit_reached Failed

test_02_deploy_vm_account_limit_reached Failing since 5 runs

test_03_deploy_vm_project_limit_reached Failed

test_project_resources.py

test_07_associate_public_ip Failing since 2 runs

test_vpc_network_staticnatrule.py

test_01_VPC_StaticNatRuleCreateStoppedState Failing since 2 runs

test_02_VPC_CreateStaticNatRule Failed

test_03_VPC_StopCreateMultipleStaticNatRuleStopppedState Failing since 2 runs

test_04_VPC_CreateMultipleStaticNatRule Failing since 2 runs

test_05_network_services_VPC_DeleteAllPF Failing since 2 runs

test_06_network_services_VPC_DeleteAllMultiplePF Failing since 2 runs

test_redundant_router_services.py

test_enableVPNOverRvR Failing since 2 runs

test_resource_limits.py

test_01_vm_per_account Failing since 2 runs

test_02_publicip_per_account Failing since 2 runs

test_03_snapshots_per_account Failing since 2 runs

test_04_volumes_per_account Failing since 2 runs

test_05_templates_per_account Failing since 2 runs

test_01_publicip_per_domain Failed

test_01_vm_per_domain Failed

test_03_snapshots_per_domain Failed

test_04_volumes_per_domain Failed

test_05_templates_per_domain Failed

test_escalations_vpncustomergateways.py

test_01_list_vpncustomergateways_pagination Failing since 2 runs

test_02_update_vpncustomergateways Failing since 2 runs

test_snapshots_improvement.py

test_01_concurrent_snapshots_live_migrate Failed

test_02_stop_vm_concurrent_snapshots Failed

test_03_concurrent_snapshots_create_template Failed

test_04_concurrent_snapshots_create_volume Failed

test_01_snapshot_on_rootVolume Failed

test_multiple_public_interfaces.py

ContextSuite context=TestIptables>:setup Failed

ContextSuite context=TestPortForwarding>:setup Failing since 9 runs

ContextSuite context=TestRouting>:setup Failing since 2 runs

ContextSuite context=TestStaticNat>:setup Failing since 2 runs

test_network_services_VPC_CreatePF Failing since 3 runs

test_network_services_VPC_CreatePF Failing since 4 runs

test_vpn_users.py

test_01_VPN_user_limit Failed

test_02_use_vpn_port Failed

test_03_enable_vpn_use_port Failed

test_04_add_new_users Failed

test_05_add_duplicate_user Failed

test_06_add_VPN_user_global_admin Failed

test_07_add_VPN_user_domain_admin Failed

test_08_add_TCP_PF_Rule_In_VPN Failed

test_cpu_project_limits.py

test_01_project_counts_start_stop_instance Failing since 2 runs

test_02_project_counts_migrate_instance Failing since 2 runs

test_03_project_counts_delete_instance Failing since 2 runs

test_routers.py

ContextSuite context=TestRouterServices>:setup Failing since 11 runs

ContextSuite context=TestRouterStopCreateFW>:setup Failed

ContextSuite context=TestRouterStopCreateLB>:setup Failed

ContextSuite context=TestRouterStopCreatePF>:setup Failed

test_overcommit.py

test_01_cluster_settings Failing since 2 runs

test_02_Overcommit_factor Failing since 2 runs

test_03_cluste_capacity_check Failing since 2 runs

test_04_zone_capacity_check Failing since 2 runs

test_custom_hostname.py

test_01_custom_hostname_instancename_false Failing since 2 runs

test_snapshots.py

test_01_createVM_snapshotTemplate Failing since 2 runs

ContextSuite context=TestSnapshotEvents>:setup Failing since 2 runs

test_01_volume_from_snapshot Failing since 2 runs

test_02_snapshot_data_disk Failing since 2 runs

test_03_snapshot_detachedDisk Failing since 2 runs

test_04_delete_snapshot Failing since 2 runs

test_07_template_from_snapshot Failing since 2 runs

test_egress_fw_rules.py

test_01_1_egress_fr1 Failing since 2 runs

test_01_2_egress_fr1 Failing since 2 runs

test_01_egress_fr1 Failing since 2 runs

test_02_1_egress_fr2 Failing since 2 runs

test_02_2_egress_fr2 Failing since 2 runs

test_02_egress_fr2 Failing since 2 runs

test_03_1_egress_fr3 Failing since 2 runs

test_03_egress_fr3 Failing since 2 runs

test_04_1_egress_fr4 Failing since 2 runs

test_04_egress_fr4 Failing since 2 runs

test_06_1_egress_fr6 Failing since 2 runs

test_06_egress_fr6 Failing since 2 runs

test_07_1_egress_fr7 Failing since 2 runs

test_07_egress_fr7 Failing since 2 runs

test_09_1_egress_fr9 Failing since 2 runs

test_09_egress_fr9 Failed

test_10_1_egress_fr10 Failed

test_10_egress_fr10 Failed

test_11_1_egress_fr11 Failed

test_11_egress_fr11 Failed

test_12_1_egress_fr12 Failed

test_12_egress_fr12 Failed

test_13_1_egress_fr13 Failed

test_13_egress_fr13 Failed

test_tags.py

ContextSuite context=TestResourceTags>:setup Failed

test_redundant_router_cleanups.py

test_network_gc Failed

test_restart_network_with_destroyed_masterVR Failing since 2 runs

test_restart_ntwk_no_cleanup Failed

test_restart_ntwk_with_cleanup Failed

test_ss_max_limits.py

test_01_deploy_vm_domain_limit_reached Failing since 2 runs

test_02_deploy_vm_account_limit_reached Failing since 6 runs

test_03_deploy_vm_project_limit_reached Failing since 2 runs

test_ss_project_limits.py

test_01_register_template_with_project Failing since 2 runs

test_deploy_vm_userdata_reg.py

test_deployvm_userdata_post Failed

test_memory_limits.py

test_01_stop_start_instance Failing since 1 runs

test_02_migrate_instance Failing since 1 runs

test_03_delete_instance Failed

test_01_stop_start_instance Failing since 2 runs

test_02_migrate_instance Failing since 2 runs

test_03_delete_instance Failing since 2 runs

test_04_deploy_multiple_vm Failing since 2 runs

test_vpc_network_pfrules.py

test_01_network_services_VPC_StopCreatePF Failing since 2 runs

test_02_network_services_VPC_CreatePF Failing since 2 runs

test_03_network_services_VPC_StopCreateMultiplePF Failing since 2 runs

test_04_network_services_VPC_CreateMultiplePF Failing since 2 runs

test_05_network_services_VPC_StopDeletePF Failing since 2 runs

test_06_network_services_VPC_DeletePF Failing since 2 runs

test_07_network_services_VPC_StopDeleteAllPF Failing since 2 runs

test_08_network_services_VPC_DeleteAllPF Failing since 2 runs

test_09_network_services_VPC_StopDeleteAllMultiplePF Failing since 2 runs

test_10_network_services_VPC_DeleteAllMultiplePF Failing since 2 runs

test_ip_reservation.py

test_reservation_after_router_restart Failed

test_vm_create_after_reservation Failing since 3 runs

test_vm_create_outside_cidr_after_reservation Failing since 3 runs

test_ip_reservation_in_multiple_networks_same_account Failing since 2 runs

test_nat_rules_1_nat_rule Failing since 2 runs

test_nat_rules_2_static_nat_rule Failing since 2 runs

test_update_cidr_multiple_vms_not_all_inclusive Failing since 2 runs

test_update_cidr_single_vm_not_inclusive Failing since 2 runs

test_vm_create_after_reservation Failing since 4 runs

test_vm_create_outside_cidr_after_reservation Failing since 4 runs

test_restart_network_with_cleanup_1_True Failing since 2 runs

test_restart_network_with_cleanup_2_False Failed

test_destroy_recreate_router Failed

test_reservation_after_router_restart Failing since 2 runs

test_update_network_guestvmcidr_1_existingVmInclusive Failed

test_update_network_guestvmcidr_2_existingVmExclusive Failed

test_vpc_vms_deployment.py

test_01_deploy_vms_in_network Failing since 2 runs

test_02_deploy_vms_delete_network Failing since 2 runs

test_03_deploy_vms_delete_add_network Failing since 2 runs

test_04_deploy_vms_delete_add_network_noLb Failing since 2 runs

test_05_create_network_max_limit Failing since 2 runs

test_06_delete_network_vm_running Failing since 2 runs

test_07_delete_network_with_rules Failing since 2 runs

test_vpc_network.py

ContextSuite context=TestVPCNetworkGc>:setup Failing since 2 runs

test_mm_project_limits.py

test_01_project_vmlifecycle_start_stop_instance Failing since 2 runs

test_02_project_vmlifecycle_migrate_instance Failing since 2 runs

test_03_project_vmlifecycle_delete_instance Failing since 2 runs

test_escalations_instances.py

test_13_attach_detach_iso Failing since 2 runs

test_14_vm_snapshot_pagination Failing since 2 runs

test_15_revert_vm_to_snapshot Failing since 2 runs

test_16_list_vm_volumes_pagination Failing since 2 runs

test_18_stopped_vm_change_service Failing since 2 runs

test_19_create_reset_vm_sshkey Failing since 2 runs

test_20_update_vm_displayname_group Failing since 2 runs

test_21_restore_vm Failing since 2 runs

test_22_deploy_vm_multiple_networks Failing since 2 runs

test_24_deploy_vm_with_static_ip_ES1662 Failing since 2 runs

test_25_ip_reallocation_ES1377 Failing since 2 runs

test_27_VM_restore_ES3467 Failing since 2 runs

test_28_VM_restore_ES3467 Failing since 2 runs

test_01_list_instances_pagination Failing since 2 runs

test_02_list_Running_vm Failing since 2 runs

test_03_list_Stopped_vm Failing since 2 runs

test_04_list_Destroyed_vm Failing since 2 runs

test_05_list_vm_by_id Failing since 2 runs

test_06_list_vm_by_name Failing since 2 runs

test_07_list_vm_by_name_state Failing since 2 runs

test_10_list_vm_by_zone_name_state Failing since 2 runs

test_11_register_reset_vm_sshkey Failing since 2 runs

test_12_running_vm_change_service Failing since 2 runs

test_13_vm_nics Failing since 2 runs

test_acl_isolatednetwork.py

ContextSuite context=TestIsolatedNetwork>:setup Failing since 2 runs

test_cpu_domain_limits.py

test_01_multiple_core_vm_start_stop_instance Failing since 2 runs

test_02_multiple_core_vm_migrate_instance Failing since 2 runs

test_03_multiple_core_vm_delete_instance Failing since 2 runs

test_04_deploy_multiple_vm_with_multiple_core Failing since 2 runs

test_01_multiple_child_domains Failing since 3 runs

test_escalations_networks.py

test_03_list_vpc_pagination Failing since 2 runs

test_04_create_vpc_with_networkdomain Failing since 2 runs

test_06_create_network_in_vpc Failing since 2 runs

test_10_list_networks_in_vpc Failing since 2 runs

test_11_update_vpc Failing since 2 runs

test_12_list_create_delete_networkACL Failing since 2 runs

test_19_create_list_reset_delete_vpnconnections Failing since 2 runs

test_storage_motion.py

ContextSuite context=TestStorageMotion>:setup Failed

test_accounts.py

ContextSuite context=TestAddVmToSubDomain>:setup Failing since 2 runs

test_DeleteDomain Failing since 2 runs

test_forceDeleteDomain Failing since 2 runs

test_01_user_remove_VM_running Failing since 2 runs

ContextSuite context=TestTemplateHierarchy>:setup Failing since 2 runs

test_LoginApiDomain Failing since 2 runs

test_LoginApiUuidResponse Failing since 2 runs

test_escalations_routers.py

test_01_FTPModulesInVR Failed

test_ps_limits.py

test_create_template_snapshot_1_root_domain_admin Failing since 2 runs

test_create_template_snapshot_2_child_domain_admin Failing since 2 runs

test_mm_max_limits.py

test_02_deploy_vm_account_limit_reached Failing since 7 runs

test_04_deployVm__account_limit_reached Failing since 3 runs

test_cpu_max_limits.py

test_02_deploy_vm_account_limit_reached Failing since 8 runs

test_04_deployVm__account_limit_reached Failing since 4 runs

test_escalation_listTemplateDomainAdmin.py

test_listtemplate Failing since 2 runs

test_projects.py

test_09_project_suspend Failed

test_10_project_activation Failed

test_portable_ip.py

test_associate_ip_address_services_enable_disable Failing since 2 runs

test_list_portable_ip_range_non_root_admin Failed

test_affinity_groups.py

test_03_delete_aff_grp_with_vms Failing since 2 runs

test_01_deploy_vm_without_aff_grp Failing since 2 runs

test_02_deploy_vm_by_aff_grp_name Failing since 2 runs

test_03_deploy_vm_by_aff_grp_id Failing since 2 runs

test_04_deploy_vm_anti_affinity_group Failing since 2 runs

test_05_deploy_vm_by_id Failing since 2 runs

test_08_deploy_vm_multiple_aff_grps Failing since 2 runs

test_09_deploy_vm_multiple_aff_grps Failing since 2 runs

test_01_list_aff_grps_for_vm Failing since 4 runs

test_02_list_multiple_aff_grps_for_vm Failing since 4 runs

test_07_list_all_vms_in_aff_grp Failing since 3 runs

test_01_update_aff_grp_by_ids Failing since 2 runs

test_02_update_aff_grp_by_names Failing since 2 runs

test_03_update_aff_grp_for_vm_with_no_aff_grp Failing since 2 runs

test_05_update_aff_grp_on_running_vm Failing since 2 runs

test_acl_listvolume.py

ContextSuite context=TestVolumeList>:setup Failing since 2 runs

test_mm_domain_limits.py

test_01_change_service_offering Failing since 2 runs

test_02_migrate_vm Failing since 2 runs

test_03_delete_vm Failing since 2 runs

test_04_deploy_multiple_vm Failing since 3 runs

test_01_multiple_child_domains Failing since 4 runs

test_blocker_bugs.py

ContextSuite context=TestDataPersistency>:setup Failing since 2 runs

ContextSuite context=TestNATRules>:setup Failing since 2 runs

ContextSuite context=TestRouterRestart>:setup Failing since 2 runs

test_01_list_routers_admin Failing since 2 runs

test_01_create_template Failing since 3 runs

test_vpc_network_internal_lbrules.py

test_02_internallb_rules_traffic Failing since 2 runs

test_03_internallb_rules_vpc_network_restarts_traffic Failing since 2 runs

test_04_internallb_appliance_operations_traffic Failing since 2 runs

test_add_remove_network.py

ContextSuite context=TestAddNetworkToVirtualMachine>:setup Failing since 2 runs

ContextSuite context=TestFailureScenariosAddNetworkToVM>:setup Failing since 2 runs

ContextSuite context=TestFailureScenariosRemoveNicFromVM>:setup Failing since 2 runs

ContextSuite context=TestFailureScenariosUpdateVirtualMachineNIC>:setup Failing since 2 runs

ContextSuite context=TestRemoveNetworkFromVirtualMachine>:setup Failing since 2 runs

ContextSuite context=TestUpdateVirtualMachineNIC>:setup Failing since 2 runs

test_escalations_ipaddresses.py

test_11_create_delete_firewallrule Failing since 2 runs

test_volumes.py

ContextSuite context=TestAttachDetachVolume>:setup Failed

ContextSuite context=TestAttachVolume>:setup Failing since 2 runs

ContextSuite context=TestAttachVolumeISO>:setup Failing since 2 runs

ContextSuite context=TestMigrateVolume>:setup Failing since 2 runs

ContextSuite context=TestVolumes>:setup Failing since 13 runs

test_acl_listsnapshot.py

ContextSuite context=TestSnapshotList>:setup Failing since 2 runs

test_stopped_vm.py

test_deploy_vm_password_enabled Failing since 2 runs

test_escalations_templates.py

test_01_list_templates_pagination Failing since 2 runs

test_02_download_template Failing since 2 runs

test_03_edit_template_details Failing since 2 runs

test_ss_limits.py

test_01_register_template_1_root_domain_admin Failing since 2 runs

test_01_register_template_2_child_domain_admin Failing since 2 runs

test_02_create_template_snapshot_1_root_domain_admin Failed

test_02_create_template_snapshot_2_child_domain_admin Failed

test_ps_resize_volume.py

test_01_increase_volume_size_within_account_limit Failed

test_02_increase_volume_size_above_account_limit Failing since 2 runs

test_03_increase_volume_size_above_domain_limit Failing since 2 runs

test_vm_passwdenabled.py

ContextSuite context=TestVMPasswordEnabled>:setup Failed

test_usage.py

ContextSuite context=TestLBRuleUsage>:setup Failing since 4 runs

ContextSuite context=TestNatRuleUsage>:setup Failing since 4 runs

ContextSuite context=TestPublicIPUsage>:setup Failing since 4 runs

ContextSuite context=TestSnapshotUsage>:setup Failing since 4 runs

ContextSuite context=TestVmUsage>:setup Failing since 4 runs

ContextSuite context=TestVolumeUsage>:setup Failing since 4 runs

ContextSuite context=TestVpnUsage>:setup Failing since 4 runs

test_vpc_vm_life_cycle.py

test_02_deploy_vm_vpcvr_stopped Failed

ContextSuite context=TestVMLifeCycleDiffHosts>:setup Failed

ContextSuite context=TestVMLifeCycleSharedNwVPC>:setup Failed

ContextSuite context=TestVMLifeCycleStoppedVPCVR>:setup Failed

ContextSuite context=TestVMLifeCycleVPC>:setup Failed

test_project_limits.py

test_03_vm_per_project Failed

test_04_publicip_per_project Failed

test_05_snapshots_per_project Failed

test_06_volumes_per_project Failing since 2 runs

test_07_templates_per_project Failing since 2 runs

test_templates.py

test_01_create_template Failing since 4 runs

test_assign_vm.py

test_13_move_across_subdomain_vm_snapshot Failing since 2 runs

test_15_move_across_subdomain_account_limit Failing since 2 runs

test_16_move_across_subdomain_volume_and_account_limit Failing since 2 runs

Skipped tests:
test_03_copy_template
ContextSuite context=TestvGPUWindowsVm>:setup
ContextSuite context=TestTemplateUsage>:setup
test_02_create_vpc_from_offering_with_regionlevelvpc_service_capability
test_03_deploy_vms_in_vpc_with_regionlevelvpc
test_02_cancel_host_maintenace_with_migration_jobs
ContextSuite context=TestInstanceNameFlagTrue>:setup
test_04_deploy_multiple_vm_with_multiple_cpus
test_05_1_egress_fr5
test_05_egress_fr5
test_08_1_egress_fr8
test_08_egress_fr8
ContextSuite context=TestAffinityRules>:setup
ContextSuite context=TestAntiAffinityRules>:setup
test_02_create_vpc_from_offering_with_distributedrouter_service_capability
test_03_deploy_vms_in_vpc_with_distributedrouter
test_04_deploy_multiple_vm
ContextSuite context=TestProjectCreationNegative>:setup
ContextSuite context=TestProjectInviteRequiredTrue>:setup
ContextSuite context=TestProjectInviteTimeout>:setup
test_RVR_network
test_01_create_network_2_network_offering_vpcns
test_02_create_network_fail_2_network_offering_vpcns
test_04_create_multiple_networks_with_lb_1_network_offering
test_04_create_multiple_networks_with_lb_2_network_offering_vpcns
test_06_create_network_with_rvr
test_09_create_network_shared_nwoff_2_network_offering_vpcns
test_01_create_network_outside_range_2_network_offering_vpcns
test_03_create_network_inside_range_2_network_offering_vpcns
test_04_create_network_overlapping_range_2_network_offering_vpcns
test_05_create_network_diff_account_2_network_offering_vpcns
test_02_concurrent_snapshot_global_limit
test_01_VM_start_stop
test_02_migrate_vm
test_03_delete_vm
test_01_deploy_vm_with_implicit_planner
test_destroy_recover_vm_1_root_domain_admin
test_destroy_recover_vm_2_child_domain_admin
test_04_copy_iso
test_04_update_aff_grp_remove_all
test_01_host_ha_with_nfs_storagepool_with_vm
test_02_host_ha_with_local_storage_and_nfs
test_03_host_ha_with_only_local_storage
ContextSuite context=TestTemplates>:setup
test_09_stop_vm_migrate_vol
test_04_copy_template
test_04_copy_template_1_root_domain_admin
test_04_copy_template_2_child_domain_admin
test1_attach_volume_ide
test2_attach_ISO_in_CentOSVM
ContextSuite context=TestTemplateUsage>:setup
test_01_addLdapConfiguration
ContextSuite context=TestTemplates>:setup
Passed test suits:
None
test_redundant_router_upgrades.py
test_regions_accounts.py
test_acl_isolatednetwork_delete.py
test_invalid_gw_nm.py
test_vpc_offerings.py
test_vpc_routers.py
test_acl_listvm.py
test_simultaneous_volume_attach.py
test_update_vm.py
test_escalations_volumes.py
test_regions.py
test_acl_sharednetwork.py
test_allocation_states.py
test_snapshot_gc.py
test_network_offering.py
None

Looks good now. Not sure what's up with Jenkins though.

Jenkins got timed out. I am force pushing again to trigger jenkins.

@ProjectMoon  Jenkins and CI is passed, Can you please give LGTM

Looks fine to me.

@borisstoyanov  Can you please trigger the travis CI on this PR please

@jayapalu Travis is already green, assuming you mean Trillian I'll kick some jobs
@blueorangutan package

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian.   Marking tag:mergeready

Disable static NAT working fine, IP's are leaving interface as soon as they are disabled.

Test results are as expected. LGTM

@blueorangutan package

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-721

merge conflicts

Merge conflicts addressed.

@jayapalu thanks, can you also squash your changes?


Add custom row rendering

Q
A

Bug fix?
[ ]

New feature?
[X]

New sample?
[ ]

Related issues?
fixes #1153

What's in this Pull Request?
Exposed extra property onRenderRow.
Info on how to use this property in this example.

@milanholemans Many thanks for the PR. I added just two small comments for you to review, please.
I have also updated the PR to target the dev branch instead of master.
Thank you!

Indeed forgot to target the right branch. Thx for the correction!

@milanholemans many thanks, merged


Reconcile table ownership semantics

We currently have two representations of each low-level table -- one that owns its data and one that does not.
This design is arguably confusing and arose primarily over concerns about memory safety.
However, it should be fixed to give a clearer API.
We should be able to write something like:
pub struct EdgeTable(TableManager<tsk_edge_table_t>)

where the manager type is responsible for ownership.
Then, EdgeTable is just a smart pointer and can Deref/DerefMut safely to the manager's public API.

To prevent any immediate API breakage, we can supply type aliases for the owning table types.
Marking the aliases as deprecated will cause client code lints to pick up on the change.

This is not API breaking after all!  The OwningXTable can be a type alias for XTable.  This alias will be deprecated in 0.13.0 and removed "eventually".

#448 managed to do this w/o appealing to any Deref/DerefMut!


Split "should requeued after job status ready" test.

What type of PR is this?
/kind bug

What this PR does / why we need it:
Split "should requeued after job status ready" test into two, with two different values for BackoffBaseSeconds. One large, which will be used to assert that Requeued=False, and one short to assert that Requeued=True.
Which issue(s) this PR fixes:

Fixes #2155
Special notes for your reviewer:
Related for this comment https://github.com/kubernetes-sigs/kueue/pull/2161#discussion_r1595141135.
Does this PR introduce a user-facing change?

None

/ok-to-test

/cc @mimowo

/test pull-kueue-test-integration-main

/lgtm
/approve
Thanks, now we should be safe from flakes here :)


Missing imports/exports January – June 2009

On this first

this is on dev

still missing on all regions other than NSW.

I was using NSW1 as a test and left it in init
it's all updated now

thanks… looks good on dev @nc9. now for prod!

it's on prod

@simonhac this one gets closed, right - emissions < 2009 are a separate issue


NO-ADS/Advert View

Problem
When opening #214 I realised that the PR did not really match how the rest of no-player operates in terms of listeners and views.
Solution
Create an AdvertView that behaves similar to PlayerView in that it holds its own AdvertListener, which contains the generic advert events that occur. When an event occurs the UI can update accordingly. This AdvertView is passed to the no-player where the listener is bound to the collection of AdvertListeners. The adsLoader, which responds to user interactions, is bound to the AdvertView.
Test(s) added
Just updated some of the AdsLoader tests to ensure that the new onAdvertsLoaded is called once we have loaded the adverts.
Paired with
Nobody.

It would swallow the log @pablisco but tbh if you are in the wrong state you have a bigger problem 😄


Include rippled version in validation

It would be useful to know what version the server is running when it issues a validation.

What would be your use case?
If it is added somehow, this information can't be verified anyways by the way.

The information would be in the signed portion of the validation. If a validator wants to lie they can and there's nothing we can do to stop them; but why would they?
As for what, having the information available in a validation will make it easier for anyone to collect and report on metrics about what version of the software validators are running. Having this information is useful and can affect decisions that validator operators take.

If a validator wants to lie they can and there's nothing we can do to stop them; but why would they?

Because telling everyone exactly which version of a software you're using increases your attack surface. It also leaks information about your operating procedures (e.g. how fast + when you update after a new software release). It also increases traffic network wide.
Maybe there could/should be an option for some kind of arbitrary "memo" key/value pairs attached to validations, but I'm not so sure if software version is a useful field there. Some other things that validators might want to communicate (though I'm not sure if that's really necessary to do with every single validation) include: jurisdiction of operator, jurisdiction of server hosting provider, some more general info about the operator...
All of these might be interesting to have signed and broadcast periodically, though ALL of these are much better off in a https://xrpl.org/xrp-ledger-toml.html file.

Hi Markus, you bring up some very valid concerns. Another option is to use a proto buffer message that contains the server's public key, version number, etc. This would only be sent once when a peer connects and reduce the impact on network traffic.  Broadcasting the version number in this way would not increase the attack surface since there are other ways for malicious actors to get the version number. The issue with including version number in the .toml file is that it will become out of date quickly. I do agree that things like jurisdiction should be included in the .toml.

You should not be able to connect directly to a validator and if you do you should definititely not be able to know that this is a validator you're connected to. I thought you wanted to know the software version of validators, not random nodes on the network? They are anyways already visible in the /crawl endpoint, so no need to send this in the peer protocol too...
The .toml file should be actively maintained and a responsible operator would anyways not just auto-update but have a certain process. Programmatically updating a file can certainly be part of such a process.

You should not be able to connect directly to a validator and if you do you should definititely not be able to know that this is a validator you're connected to.
I don't know that I agree. Certainly, locking down a validator by limiting who can connect to it is a prudent security step that an operator can take (and one I recommend), but it's by no mean a requirement.

Furthermore, if onion-routing of proposals and validations is implemented, this argument becomes somewhat moot, since the validations will "emerge" at another part of the network, and you can't know if the server broadcasting it is the source or the relay.

The .toml file should be actively maintained and a responsible operator would anyways not just auto-update but have a certain process. Programmatically updating a file can certainly be part of such a process.
Agreed, but I think that if we can automate something within the protocol in a lightweight and unobtrusive manner, eliminating the need for a third-party service, then we probably should do that.