✨[FEATURE] Youtube Video Downloader

🌟 Feature Overview
This project integrates with yt-dlp to allow users to download videos from YouTube. It enables downloading in various formats and resolutions, giving users flexibility in managing their video downloads.
🤔 Why this feature?

Extract and download only the audio from a YouTube video.
Download videos in various resolutions (360p, 720p, 1080p, etc.).
Download multiple videos at once by providing a list of URLs.

Hi, thank you for your interest in the project! Just a reminder, this repository is focused specifically on the Python Voice Assistant. Please make sure that any issues or PRs are relevant to this project's scope. Unrelated features or suggestions should be directed elsewhere. Thanks for understanding!


change REQUIRE to Pkg3 TOML files

Please change the use of Pkg.dir()

Update the CI for v0.7 too.
We need to update the data files since @NT has been removed

Closed with 8ee873f


Uniwersytet Ekonomiczny w Poznaniu

@ukid I am sorry, this request has signs of fraud. I have to close it without merging. If you are a student of this school, please apply with official document ("OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students).


Removes deprecated power prototypes

Has map changes.
I fully expect to have to smash this pr and redo it when PJB fixes the corrupt map file.

making a mapping change with a mapping PR open

using DebugApc on the map instead of making it abstract and making a prototype for Saltern

pretty sure all you did was find & replace

didn't replace the other deprecated power stuff

🤔

making a mapping change with a mapping PR open

using DebugApc on the map instead of making it abstract and making a prototype for Saltern

pretty sure all you did was find & replace

didn't replace the other deprecated power stuff

🤔

I realized i'll have to redo most of this since I was talking with PJB in dms so I made one commit and left it.

Closing because i'm making a new pr rn


Update stress workbook parameters to filter by time->namespace->pod

This change reduces pod name noise in the dropdown, as we now filter by namespace first, and then also group the pod names by date. Additionally, the query time range for namespace/pods is configurable, so it's possible to look up non-active pods in the dashboard now.

Pod query diff:
3,4c3,5
< | distinct InstanceName
< | extend ResourceId = split(InstanceName, \'/\')
---
> | extend DayBin = bin(TimeGenerated, 3d)
> | summarize arg_max(TimeGenerated, *) by InstanceName
> | extend ResourceId = split(InstanceName, "/")
7d7
< | distinct ContainerName, PodUid
12c12
<   | where Namespace != "kube-system" and Namespace != "stress-infra"
---
>   | where Namespace in ({NamespaceParameter})
15c15,17
< | project value = PodUid, label = Name, group = Namespace
---
> | extend day = tostring(format_datetime(DayBin, "MM/dd"))
> | sort by day desc
> | project value = PodUid, label = Name, group = day

and do we not want the kube-system and stress-infra namespaces to be excluded anymore? can we get valuable info from those

and do we not want the kube-system and stress-infra namespaces to be excluded anymore? can we get valuable info from those

@ckairen They are effectively excluded still because you now choose a namespace and we filter against that. The new namespace dropdown parameter does exclude kube-system (query below), but I don't exclude stress-infra because it could be nice to view our service stats from this dashboard.
KubePodInventory\r\n| distinct Namespace\r\n| where Namespace !in ("kube-system", "kubernetes-dashboard", "gatekeeper-system")


Missing some facebook replies

If you look at https://www.brid.gy/facebook/515373050 you'll see it says a reply starting out "I fine spending money on it" (url: https://www.facebook.com/10153352091173051?comment_id=10153352370033051) I says it sent me a webmention... but I didn't get it. Could you maybe peek at any logs you have to see if my server gave back an error or something?

I have checked my wordpress spam, etc, and it's not there, so be clear.

hey @singpolyma, sorry for the trouble! you can actually click on the X ago links for each response on your user page to see the raw logs for sending webmention(s). e.g. for that response: https://www.brid.gy/log?start_time=1444672206&key=aglzfmJyaWQtZ3lyRwsSCFJlc3BvbnNlIjl0YWc6ZmFjZWJvb2suY29tLDIwMTM6MTAxNTMzNTIwOTExNzMwNTFfMTAxNTMzNTIzNzAwMzMwNTEM
here's the snippet where it sent the wm to your server and got a 200:
2015-10-12 17:50:03.089770 I Starting new HTTPS connection (1): singpolyma.net
2015-10-12 17:50:05.974230 D "POST /wordpress/?webmention=endpoint HTTP/1.1" 200 None
2015-10-12 17:50:06.054980 I Sent! {'body': u'/comment-page-/#comment-', 'request': u'POST https://singpolyma.net/wordpress/?webmention=endpoint (with source=https://brid-gy.appspot.com/comment/facebook/515373050/10153352091173051/10153352091173051_10153352370033051, target=https://singpolyma.net/actionstream/please-please-stop-pretending-meyers/)', 'http_status': 200}

'body': u'/comment-page-/#comment-'

What does this part mean?

that means /comment-page-/#comment- was the HTTP response body received from your server.

tentatively closing. feel free to reopen if necessary!


The performance problem with cloning document contains a lot of SVG nodes

[o] You are using the latest version
[o] You are testing using the non-minified version of html2canvas and checked any potential issues reported in the console

Bug reports:
If a page contains a log of SVG nodes, e.g. amCharts (based on SVG), the call html2canvas(pageNode) freezes Firefox & Safari for a while. It could take several minutes.
Just compare:

Render a big SVG chart takes ~ 15 seconds on my PC (https://jsfiddle.net/yaznayka/5axe04vt/33)
The same chart with turned "copyCssStyles" off (https://i.imgur.com/vDUhd3O.png) ~ 1 second (https://jsfiddle.net/yaznayka/5axe04vt/35)

Suggestion
Add an option in html2canvas to turn off copyCssStyles in SVG nodes.
Specifications:

html2canvas version tested with: 1.0.0-rc.7
Browser & version: Chrome Version 89.0.4389.90 (Official Build)
Operating system: Linux mint

I have this same issue (of an SVG heavy chart taking 30+ seconds to render all while hanging the entire web site in safari), so... +1 on this being needed!

Cloning the whole page to take a screenshot of a small part is an overkill IMHO. I'm wondering whether there is a way to not close the whole page.

@niklasvh
It makes sense. Please, pay attention to this


New Panic regression error on eth_call

New Panic regression error on eth_call json-rpc request
Description
I observed that b54f44f on develop introduces a new issue which causes a previously-working eth_call request to throw a panic and no longer return a 200 status.
Your environment

OS and version Ubuntu 20
version of the Polygon SDK b54f44f
branch that causes this issue develop

Steps to reproduce

Checkout a158b74 (the commit hash prior to b54f44f) and build + run ./main server
Observe a 200 response when sending a request similar to the following json-rpc request:

{
	"id": 0,
	"jsonrpc": "2.0",
	"method": "eth_call",
	"params": [{
		"data": "0x70a082310000000000000000000000000cd01b344f086d814c72a8d8195b3349f186eabf",
		"from": null,
		"to": "0xeafbbf62dffba085b717e215d82223fe2f212268"
	}, "0xF9309"]
}

Checkout a158b74 and build + run
Observe a panic (see logs below)

Expected behaviour
Shouldn't throw a panic.
Actual behaviour
Observe a panic in the logs and no response from the originating request.
Logs
2021-11-01T18:16:46.455Z [ERROR] polygon.dispatcher: failed to dispatch: method=eth_call err=<nil>"}
2021/11/01 18:16:46 http: panic serving <IP_ADDRESS>:50586: runtime error: invalid memory address or nil pointer dereference"}
goroutine 490 [running]:"}
net/http.(*conn).serve.func1(0xc0032d37c0)"}
\t/usr/local/go/src/net/http/server.go:1824 +0x153"}
panic(0xdf7720, 0x1a3ede0)"}
\t/usr/local/go/src/runtime/panic.go:971 +0x499"}
github.com/0xPolygon/polygon-sdk/state.(*TransitionApplicationError).Error(0x0, 0xfdcb38, 0x12)"}
\t/home/ubuntu/sx-node/state/executor.go:345 +0x33"}
github.com/0xPolygon/polygon-sdk/jsonrpc.(*Dispatcher).handleReq(0xc000ae1da0, 0xd9dac0, 0x1914aa0, 0xc000457d88, 0x8, 0xc000631550, 0xae, 0xb0, 0xc00065cca8, 0xc05829a300000002, ...)"}
\t/home/ubuntu/sx-node/jsonrpc/dispatcher.go:299 +0x63c"}
github.com/0xPolygon/polygon-sdk/jsonrpc.(*Dispatcher).Handle(0xc000ae1da0, 0xc00319f400, 0xf1, 0x200, 0x2, 0x2, 0x0, 0xc0033c3280, 0x800)"}
\t/home/ubuntu/sx-node/jsonrpc/dispatcher.go:243 +0x25e"}
github.com/0xPolygon/polygon-sdk/jsonrpc.(*JSONRPC).handle(0xc000b2aea0, 0x1250d78, 0xc0008f96c0, 0xc00335eb00)"}
net/http.HandlerFunc.ServeHTTP(0xc000b26850, 0x1250d78, 0xc0008f96c0, 0xc00335eb00)"}
\t/usr/local/go/src/net/http/server.go:2069 +0x44"}
net/http.(*ServeMux).ServeHTTP(0x1a72b00, 0x1250d78, 0xc0008f96c0, 0xc00335eb00)"}
\t/usr/local/go/src/net/http/server.go:2448 +0x1ad"}
net/http.serverHandler.ServeHTTP(0xc0008f8620, 0x1250d78, 0xc0008f96c0, 0xc00335eb00)"}
sr/local/go/src/net/http/server.go:2887 +0xa3"}
net/http.(*conn).serve(0xc0032d37c0, 0x12537c0, 0xc0033c3180)"}
\t/usr/local/go/src/net/http/server.go:1952 +0x8cd"}
created by net/http.(*Server).Serve"}
\t/usr/local/go/src/net/http/server.go:3013 +0x39b"}

Proposed solution
I'm not sure exactly what causes this error but narrowed it down to something introduced by b54f44f.

Hey @dankostiuk,
Thank you for reaching out. We've identified the issue, and a hotfix has already been applied through PR #189.
Please let us know if the issue has been resolved after you pull the latest changes from develop.

Looks like it has been resolved after pulling in that PR thanks @zivkovicmilos 👍


[Event Hubs] Add support for individual send message Retry

For each send operation, there is a time we wait between sending a message and waiting for an acknowledgement. Currently, it is set to operationTimeout. We want to add this to a retry policy.

Retry.TryTimeout.


Generated dataclass from CTE/WITH query should have nullable instance variable

Hi there,
Firstly, thanks heaps for maintaining such an awesome package! It is greatly appreciated :)
I have CTE as a custom query in a DAO and the dataclass that is generated uses a non-nullable data type for an instance variable which should actually nullable.
I have created a simple example to better illustrate the issue with two tables.  The employees table and another table with employee_notes. The WITH query gets the employee hierarchy - the employees that have no manager, then the employees that have those employees as managers and so on.
The result is the employee hierarchy and the notes on each employee.
tables.moor
CREATE TABLE IF NOT EXISTS "employees" (
	"id"	INTEGER NOT NULL PRIMARY KEY,
	"name"	TEXT NOT NULL UNIQUE,
	"manager_id" INTEGER
);

CREATE TABLE IF NOT EXISTS "employee_notes" (
	"employee_id"	INTEGER NOT NULL PRIMARY KEY,
	"note"	TEXT
);

@create: INSERT INTO "employees" ("id", "name", "manager_id")
VALUES (1, 'Alice', NULL),
       (2, 'Bob', NULL),
       (3, 'Charlie', 1),
       (4, 'David', 2);

@create: INSERT INTO "employee_notes" ("employee_id", "note")
VALUES (3, 'A note about Charlie');

employee.dao
@UseDao(include: {
  'tables.moor'
}, tables: [
  Employee,
  EmployeeNote,
], queries: {
  'employeeHierarchy': '''
WITH RECURSIVE
employeeHierarchy(id, name, manager_id) AS (
  SELECT id,
         name,
	 manager_id
    FROM employees
   WHERE manager_id IS NULL
   UNION ALL
  SELECT e.id,
         e.name,
	 e.manager_id
    FROM employees e
    JOIN employeeHierarchy ON e.manager_id = employeeHierarchy.id
)
SELECT e.id,
       e.name,
       e.manager_id,
       n.note
  FROM employeeHierarchy e
  LEFT OUTER JOIN
       employee_notes n ON e.id = n.employee_id
 ORDER BY e.id;
  '''
})

Generated dataclass
Here is where the issue is. The managerId should be final int? managerId, and as a result an exception is thrown when the query is parsed.
class EmployeeHierarchyResult {
  final int id;
  final String name;
  final int managerId;
  final String? note;
  EmployeeHierarchyResult({
    required this.id,
    required this.name,
    required this.managerId,
    this.note,
  });
}

I can work around this by doing the query and parsing the result manually but I thought I should log an issue anyway :)
Cheers!

Thanks for the very helpful report! After some digging, it looks like this is actually caused by the compound select statement. When the type inference algorithm has to unify two types (which needs to happen to resolve the column in a UNION), it didn't look at the nullability of the involved columns. This should be fixed in 0d8741a7b456d6ce1cc50379421ec7e414c44a48.

Thank you very much!!


Swift3

Will this PR merged anytime soon or do we need to use the swift3 branch for the time being?


ngf-accept file filtering doesn't seem to work

I've noticed that ngf-accept doesn't seem to work when you try to use it to filter for specific files.  Even on the jsfiddle demo if you change the accept attributes over to ngf-accept the filtering no longer works.  You can see this in jsfiddle http://jsfiddle.net/3t50b3fw/401/ for example.
This issue happens to me in Chrome, Firefox, and Internet Explorer.

What is not working? Steps to reproduce

Well I'm not quite sure how to be more clear than I was since my original post mentioned what isn't working and also mentioned how to reproduce it as well as included a jsfiddle recreating the issue but I'll try explaining it again.
In the reference section on the github it mentions the following for ngf-accept:
ngf-accept="'.pdf,.jpg'|validate($file)" // function or comma separated wildcard to filter files allowed
I've tried the following combinations (with and without single quotes just to see if it would make a difference) and none of them filter for the specific file types I listed.
ngf-accept=".pdf,.jpg"
ngf-accept="'.pdf,.jpg'"
When the browser's file select dialog box pops up it still shows all file types instead of just the ones I listed as filters.
I created another fiddle for you which is also based off the sample demo fiddle.  Hopefully this one makes it more clear what isn't working.

the browser file popup filter is browser specific and is controlled by accept attribute, ngf-accept is just filtering after the files are selected and set the files into ng-model or ng-model-rejected based on wether they are accepted or not

Ah, ok.  I did do some more tinkering around with it after your explanation and I see how it's supposed to work now.  The descriptions on the main github page for how to use some of the options in conjunction with the other options are a bit vague.  Also it might be helpful to note which ones are required options and which ones are strictly optional.
Thanks for the assistance though. I'll go ahead and close out this issue.

If you have suggestion to make it more clear let me know.
I added a note for ngf-drop optional attributes.

I do have a few suggestions listed below if you would like to implement them.
I would suggest adding a similar note to ngf-select as you did for ngf-drop since not all attributes are required for ngf-select either.
For the ngf-accept attribute maybe you could add a comment that says it is used to filter out the files after they have been selected and discards or accepts them based on whether or not they meet the filter criteria.  Then on the accept attribute comment you could a small statement that says it is used to filter the files before selection.  Doing that would make it really clear that the accept attribute is used to filter files before they are selected and ngf-accept is used to filter files after they are selected.
The only other thing I can think of is that it might be a good idea to mention somewhere that by default ng-file-upload won't inform you in any way if a file fails to meet the pattern in ngf-accept.  You have to either use ng-model-rejected to see that a file failed or you would need to write your own function that you would pass into ngf-accept to inform you that a file failed.  I only mention this because when I was first trying to implement ng-file-upload I kept looking for some kind of informational message in both the browser's debug console and on the page itself to see why my file wasn't getting set in ng-model.

ngf-accept is case sensitive. it shouldn't.

@cipianpascu create a separate issue for that.

Hi Danial,
Thought it was related with this one. :)
New incident created at 1546
Regards,
Ciprian

From the Readme:
*ngf-accept="'image/*'" // standard HTML accept attr, browser specific select popup window

This is very confusing. After reading that I assumed that ngf-accept was a ngf-specific way to get the functionality of the normal "accept" attribute. Only after a bunch of googling did I stumble on this issue and found your explanation of what it actually is.
It would be much appreciated if the documentation in the readme could be clearer about that.

@default0: Ditto

Yes, VERY confusing. Wasted an hour on this.


WFLY-4452 Use Flag.RESTART_RESOURCE_SERVICES for child resources of cache

https://issues.jboss.org/browse/WFLY-4575
Most resource attributes in the Infinispan subsystem use Flag.RESTART_ALL_SERVICES.  This is overly coarse/intrusive.  Changing any attribute of a cache configuration should only require the restart of a  minimal set of services.  This PR does just that.
To do this, every child resource of a cache installs a service which encompasses its configuration.  The cache resource need only depend on the requisite child configuration components for that cache type.  This means that the child resources of a cache are no longer just blocks of configuration, but now create fine-grained services.
I've made a number of tangential changes to the Infinispan subsystem, including:

Eliminate loading of cache configuration defaults from an external a file.  Because all components of a cache configuration are required, we no longer have a need for this (i.e. infinispan-defaults.xml).  All defaults are explicitly determined by the model.
Use better path names for cache and cache container components, e.g. /local-cache=test/component=transaction instead of /local-cache=test/transaction=TRANSACTION.  Paths are transformed to legacy path to support mixed domains.
Use better path names for cache stores, e.g. /local-cache=test/store=file instead of /local-cache=test/file-store=FILE_STORE
Refactor indexing related cache attributes into an Indexing child resource, including requisite transformers.
Refactor string-table/binary-table properties of jdbc cache stores into child resources, including requisite transformers.  This simplifies the corresponding jdbc store management operations significantly. e.g. /local-cache=test/store=mixed-jdbc/table=binary
Enumerated resource attributes.  This allows us to more easily operate on all attributes of a resource, and allows us to more easily do clever things with generic resource handlers.  This also minimizes the work required to add a new attribute to a resource.
Enhanced generic resource description resolver that looks for the description of a given key from a set of prefixes.  This prevents the need to duplicate descriptions when using resource hierarchies.

To facilitate this change, I've introduced a number of controller abstractions that reduce the amount of boilerplate code required to instrument a resource:

ResourceServiceBuilder, an extension of org.wildfly.clustering.service.Builder that allows the builder to configure itself via a resource model.
ResourceServiceHandler, an abstraction that encapsulates logic for installing and removing services for a resource
A simple ResourceServiceHandler that installs/removes a single service via a ResourceServiceBuilder factory
Generic resource add/remove operation handlers that delegate to a ResourceServiceHandler
Generic RestartParent*Handlers that delegate to a ResourceServiceBuilder factory.

Linux Build 6390 is now running using a merge of 54fd51c5eba8aa75c51124b107cccc04fbae22f9

Windows Build 1469 is now running using a merge of 54fd51c5eba8aa75c51124b107cccc04fbae22f9

Linux with security manager Build 1317 is now running using a merge of 54fd51c5eba8aa75c51124b107cccc04fbae22f9

Linux with security manager Build 1317 outcome was SUCCESS using a merge of 54fd51c5eba8aa75c51124b107cccc04fbae22f9
Summary: Tests passed: 825, ignored: 317 Build time: 0:05:02

Windows Build 1469 outcome was FAILURE using a merge of 54fd51c5eba8aa75c51124b107cccc04fbae22f9
Summary: Tests failed: 4 (4 new), passed: 2853, ignored: 373 Build time: 0:47:30
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.management.cli.WildCardReadsTestCase.testLenientReadOperationDescription: <no details avaliable>

org.jboss.as.test.integration.management.cli.WildCardReadsTestCase.testReadResourceDescriptionNoGenericRegistration: <no details avaliable>

org.jboss.as.test.integration.jmx.ModelControllerMBeanTestCase.testAllMBeanInfos: <no details avaliable>

org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.test: <no details avaliable>

Linux Build 6390 outcome was FAILURE using a merge of 54fd51c5eba8aa75c51124b107cccc04fbae22f9
Summary: Tests failed: 9 (9 new), passed: 2848, ignored: 373 Build time: 0:48:18
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.management.cli.WildCardReadsTestCase.testLenientReadOperationDescription: <no details avaliable>

org.jboss.as.test.integration.management.cli.WildCardReadsTestCase.testReadResourceDescriptionNoGenericRegistration: <no details avaliable>

org.jboss.as.test.integration.ejb.client.descriptor.EJBClientDescriptorTestCase.testClientPropertiesReplacementInConfig: <no details avaliable>

org.jboss.as.test.integration.ejb.remote.distinctname.EarDeploymentDistinctNameTestCase.testRemoteSLSBInvocation: <no details avaliable>

org.jboss.as.test.integration.ejb.remote.distinctname.JarDeploymentDistinctNameTestCase.testRemoteSLSBInvocation: <no details avaliable>

org.jboss.as.test.integration.ejb.remote.view.LocalViewRemoteInvocationTestCase.testLocalViewInvocationRemotelyOnSFSB: <no details avaliable>

org.jboss.as.test.integration.ejb.stateful.passivation.PassivationTestCase.testPassivationMaxSize: <no details avaliable>

org.jboss.as.test.integration.jmx.ModelControllerMBeanTestCase.testAllMBeanInfos: <no details avaliable>

org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.test: <no details avaliable>

Windows Build 1476 is now running using a merge of 296d9e938b825e5faf5efd0ac08afc97d8fb699a

Linux with security manager Build 1324 is now running using a merge of 296d9e938b825e5faf5efd0ac08afc97d8fb699a

Linux Build 6397 is now running using a merge of 296d9e938b825e5faf5efd0ac08afc97d8fb699a

Linux with security manager Build 1324 outcome was SUCCESS using a merge of 296d9e938b825e5faf5efd0ac08afc97d8fb699a
Summary: Tests passed: 825, ignored: 317 Build time: 0:05:08

Windows Build 1476 outcome was FAILURE using a merge of 296d9e938b825e5faf5efd0ac08afc97d8fb699a
Summary: Tests failed: 4, passed: 2863, ignored: 373 Build time: 0:46:58
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.management.cli.WildCardReadsTestCase.testLenientReadOperationDescription: <no details avaliable>

org.jboss.as.test.integration.management.cli.WildCardReadsTestCase.testReadResourceDescriptionNoGenericRegistration: <no details avaliable>

org.jboss.as.test.integration.jmx.ModelControllerMBeanTestCase.testAllMBeanInfos: <no details avaliable>

org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.test: <no details avaliable>

Linux Build 6397 outcome was FAILURE using a merge of 296d9e938b825e5faf5efd0ac08afc97d8fb699a
Summary: Tests failed: 4, passed: 2862, ignored: 373, muted: 1 Build time: 0:48:27
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.management.cli.WildCardReadsTestCase.testLenientReadOperationDescription: <no details avaliable>

org.jboss.as.test.integration.management.cli.WildCardReadsTestCase.testReadResourceDescriptionNoGenericRegistration: <no details avaliable>

org.jboss.as.test.integration.jmx.ModelControllerMBeanTestCase.testAllMBeanInfos: <no details avaliable>

org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.test: <no details avaliable>

Windows Build 1481 is now running using a merge of e807f3f649c75a7674a3e966c10b620661d47a0b

Linux Build 6402 is now running using a merge of e807f3f649c75a7674a3e966c10b620661d47a0b

Linux with security manager Build 1329 is now running using a merge of e807f3f649c75a7674a3e966c10b620661d47a0b

Linux with security manager Build 1329 outcome was FAILURE using a merge of e807f3f649c75a7674a3e966c10b620661d47a0b
Summary: Tests failed: 3 (3 new), passed: 822, ignored: 317 Build time: 0:05:30
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.web.jsp.taglib.external.ExternalTagLibTestCase.testExternalTagLibOnly: <no details avaliable>

org.jboss.as.test.integration.web.jsp.taglib.external.ExternalTagLibTestCase.testExternalAndInternalTagLib: <no details avaliable>

org.jboss.as.test.integration.jsp.JspTagTestCase.test: <no details avaliable>

Windows Build 1481 outcome was FAILURE using a merge of bb7e421163406029c80c38b798a7f4c8d8c628f5
Summary: Tests failed: 4, passed: 2863, ignored: 373 Build time: 0:50:34
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.management.cli.WildCardReadsTestCase.testLenientReadOperationDescription: <no details avaliable>

org.jboss.as.test.integration.management.cli.WildCardReadsTestCase.testReadResourceDescriptionNoGenericRegistration: <no details avaliable>

org.jboss.as.test.integration.jmx.ModelControllerMBeanTestCase.testAllMBeanInfos: <no details avaliable>

org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.test: <no details avaliable>

Linux Build 6402 outcome was FAILURE using a merge of bb7e421163406029c80c38b798a7f4c8d8c628f5
Summary: Tests failed: 4, passed: 2862, ignored: 373, muted: 1 Build time: 0:52:40
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.management.cli.WildCardReadsTestCase.testLenientReadOperationDescription: <no details avaliable>

org.jboss.as.test.integration.management.cli.WildCardReadsTestCase.testReadResourceDescriptionNoGenericRegistration: <no details avaliable>

org.jboss.as.test.integration.jmx.ModelControllerMBeanTestCase.testAllMBeanInfos: <no details avaliable>

org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.test: <no details avaliable>

Windows Build 1490 is now running using a merge of bb7e421163406029c80c38b798a7f4c8d8c628f5

Linux Build 6411 is now running using a merge of bb7e421163406029c80c38b798a7f4c8d8c628f5

Linux Build 6411 outcome was FAILURE using a merge of bb7e421163406029c80c38b798a7f4c8d8c628f5
Summary: Tests failed: 5 (2 new), passed: 2855, ignored: 373, muted: 1 Build time: 0:49:12
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.ejb.client.descriptor.EJBClientDescriptorTestCase.testEJBClientContextWithNoReceiversConfiguration: <no details avaliable>

org.jboss.as.test.integration.jca.moduledeployment.TwoModulesFlatTestCase: <no details avaliable>

org.jboss.as.test.integration.management.cli.WildCardReadsTestCase.testLenientReadOperationDescription: <no details avaliable>

org.jboss.as.test.integration.management.cli.WildCardReadsTestCase.testReadResourceDescriptionNoGenericRegistration: <no details avaliable>

org.jboss.as.test.integration.jmx.ModelControllerMBeanTestCase.testAllMBeanInfos: <no details avaliable>

Windows Build 1490 outcome was FAILURE using a merge of bb7e421163406029c80c38b798a7f4c8d8c628f5
Summary: Tests failed: 3, passed: 2865, ignored: 373 Build time: 0:49:44
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.management.cli.WildCardReadsTestCase.testLenientReadOperationDescription: <no details avaliable>

org.jboss.as.test.integration.management.cli.WildCardReadsTestCase.testReadResourceDescriptionNoGenericRegistration: <no details avaliable>

org.jboss.as.test.integration.jmx.ModelControllerMBeanTestCase.testAllMBeanInfos: <no details avaliable>

Linux Build 6415 is now running using a merge of 153c4f289f81ba353bc95212b26550775b702551

Windows Build 1494 is now running using a merge of 153c4f289f81ba353bc95212b26550775b702551

Windows Build 1494 outcome was FAILURE using a merge of 153c4f289f81ba353bc95212b26550775b702551
Summary: Tests failed: 2 (1 new), passed: 2866, ignored: 373 Build time: 0:46:07
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.test: <no details avaliable>

org.jboss.as.test.integration.jmx.ModelControllerMBeanTestCase.testAllMBeanInfos: <no details avaliable>

Linux Build 6415 outcome was FAILURE using a merge of 153c4f289f81ba353bc95212b26550775b702551
Summary: Tests failed: 2 (1 new), passed: 2862, ignored: 373, muted: 4 Build time: 0:49:22
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.test: <no details avaliable>

org.jboss.as.test.integration.jmx.ModelControllerMBeanTestCase.testAllMBeanInfos: <no details avaliable>

Windows Build 1529 is now running using a merge of 36d36926f5fc2c09cad9faa9c1470667552b2386

Linux with security manager Build 1357 is now running using a merge of 36d36926f5fc2c09cad9faa9c1470667552b2386

Linux Build 6451 is now running using a merge of 36d36926f5fc2c09cad9faa9c1470667552b2386

Linux with security manager Build 1357 outcome was FAILURE using a merge of 36d36926f5fc2c09cad9faa9c1470667552b2386
Summary: Tests failed: 3, passed: 823, ignored: 318 Build time: 0:06:05
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.web.jsp.taglib.external.ExternalTagLibTestCase.testExternalTagLibOnly: <no details avaliable>

org.jboss.as.test.integration.web.jsp.taglib.external.ExternalTagLibTestCase.testExternalAndInternalTagLib: <no details avaliable>

org.jboss.as.test.integration.jsp.JspTagTestCase.test: <no details avaliable>

Linux Build 6451 outcome was FAILURE using a merge of 36d36926f5fc2c09cad9faa9c1470667552b2386
Summary: Tests failed: 2, passed: 2866, ignored: 373 Build time: 0:46:02
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.jmx.ModelControllerMBeanTestCase.testAllMBeanInfos: <no details avaliable>

org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.test: <no details avaliable>

Windows Build 1529 outcome was FAILURE using a merge of 36d36926f5fc2c09cad9faa9c1470667552b2386
Summary: Tests failed: 2, passed: 2866, ignored: 373 Build time: 0:46:45
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.jmx.ModelControllerMBeanTestCase.testAllMBeanInfos: <no details avaliable>

org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.test: <no details avaliable>

Windows Build 1535 is now running using a merge of 472b3b09eef02f039dbe9771d0a56abad48ff78c

Linux with security manager Build 1363 is now running using a merge of 472b3b09eef02f039dbe9771d0a56abad48ff78c

Linux Build 6457 is now running using a merge of 472b3b09eef02f039dbe9771d0a56abad48ff78c

Linux with security manager Build 1363 outcome was FAILURE using a merge of 472b3b09eef02f039dbe9771d0a56abad48ff78c
Summary: Tests failed: 3, passed: 823, ignored: 318 Build time: 0:07:21
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.web.jsp.taglib.external.ExternalTagLibTestCase.testExternalTagLibOnly: <no details avaliable>

org.jboss.as.test.integration.web.jsp.taglib.external.ExternalTagLibTestCase.testExternalAndInternalTagLib: <no details avaliable>

org.jboss.as.test.integration.jsp.JspTagTestCase.test: <no details avaliable>

Linux Build 6457 outcome was FAILURE using a merge of 472b3b09eef02f039dbe9771d0a56abad48ff78c
Summary: Tests failed: 2, passed: 2866, ignored: 373 Build time: 0:51:29
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.jmx.ModelControllerMBeanTestCase.testAllMBeanInfos: <no details avaliable>

org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.test: <no details avaliable>

Windows Build 1535 outcome was FAILURE using a merge of 472b3b09eef02f039dbe9771d0a56abad48ff78c
Summary: Tests failed: 2, passed: 2866, ignored: 373 Build time: 0:52:28
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.jmx.ModelControllerMBeanTestCase.testAllMBeanInfos: <no details avaliable>

org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.test: <no details avaliable>

The above failure is due to https://issues.jboss.org/browse/WFCORE-692
and is fixed by: https://github.com/wildfly/wildfly-core/pull/728

Windows Build 1573 is now running using a merge of 82b32c72d5987ff4dc05598d2d7b59a6ec9dc0ed

Linux with security manager Build 1401 is now running using a merge of 82b32c72d5987ff4dc05598d2d7b59a6ec9dc0ed

Linux Build 6495 is now running using a merge of 82b32c72d5987ff4dc05598d2d7b59a6ec9dc0ed

Linux with security manager Build 1401 outcome was FAILURE using a merge of 82b32c72d5987ff4dc05598d2d7b59a6ec9dc0ed
Summary: Tests failed: 16 (16 new), passed: 787, ignored: 320 Build time: 0:05:00
Build problems:
Failed tests detected
Failed tests
org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseAndMarshalModel(0): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testSubsystem(0): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseAndMarshalModel(1): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testSubsystem(1): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseAndMarshalModel(2): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testSubsystem(2): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseAndMarshalModel(3): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testSubsystem(3): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseAndMarshalModel(4): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testSubsystem(4): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseAndMarshalModel(5): <no details avaliable>

##### there are 6 more failed tests, see build details

Windows Build 1573 outcome was FAILURE using a merge of 82b32c72d5987ff4dc05598d2d7b59a6ec9dc0ed
Summary: Tests failed: 68 (67 new), passed: 2776, ignored: 374, muted: 2 Build time: 0:37:19
Build problems:
Failed tests detected
Failed tests
org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseAndMarshalModel(0): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testSubsystem(0): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseAndMarshalModel(1): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testSubsystem(1): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseAndMarshalModel(2): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testSubsystem(2): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseAndMarshalModel(3): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testSubsystem(3): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseAndMarshalModel(4): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testSubsystem(4): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseAndMarshalModel(5): <no details avaliable>

##### there are 58 more failed tests, see build details

Linux Build 6495 outcome was FAILURE using a merge of 82b32c72d5987ff4dc05598d2d7b59a6ec9dc0ed
Summary: Tests failed: 70 (69 new), passed: 2774, ignored: 374, muted: 2 Build time: 0:37:36
Build problems:
Failed tests detected
Failed tests
org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseAndMarshalModel(0): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testSubsystem(0): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseAndMarshalModel(1): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testSubsystem(1): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseAndMarshalModel(2): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testSubsystem(2): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseAndMarshalModel(3): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testSubsystem(3): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseAndMarshalModel(4): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testSubsystem(4): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseAndMarshalModel(5): <no details avaliable>

##### there are 60 more failed tests, see build details

Hmm - this works fine for me.  Rebasing again...

Linux Build 6501 is now running using a merge of 82b32c72d5987ff4dc05598d2d7b59a6ec9dc0ed

Linux with security manager Build 1407 is now running using a merge of 82b32c72d5987ff4dc05598d2d7b59a6ec9dc0ed

Windows Build 1579 is now running using a merge of 82b32c72d5987ff4dc05598d2d7b59a6ec9dc0ed

Linux with security manager Build 1407 outcome was SUCCESS using a merge of 82b32c72d5987ff4dc05598d2d7b59a6ec9dc0ed
Summary: Tests passed: 821, ignored: 319 Build time: 0:05:02

Linux Build 6501 outcome was FAILURE using a merge of 82b32c72d5987ff4dc05598d2d7b59a6ec9dc0ed
Summary: Tests failed: 1, passed: 2862, ignored: 374 Build time: 0:49:45
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.management.cli.WildCardReadsTestCase.testReadResourceDescriptionNoGenericRegistration: <no details avaliable>

Windows Build 1579 outcome was FAILURE using a merge of 82b32c72d5987ff4dc05598d2d7b59a6ec9dc0ed
Summary: Tests failed: 1, passed: 2862, ignored: 374 Build time: 0:48:35
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.management.cli.WildCardReadsTestCase.testReadResourceDescriptionNoGenericRegistration: <no details avaliable>

Linux Build 6506 is now running using a merge of 6c4d474fe6d328d3639b57164a279bad277146e7

Linux with security manager Build 1412 is now running using a merge of 6c4d474fe6d328d3639b57164a279bad277146e7

Windows Build 1584 is now running using a merge of 6c4d474fe6d328d3639b57164a279bad277146e7

Linux with security manager Build 1412 outcome was SUCCESS using a merge of 6c4d474fe6d328d3639b57164a279bad277146e7
Summary: Tests passed: 821, ignored: 319 Build time: 0:05:10

Linux Build 6506 outcome was SUCCESS using a merge of 6c4d474fe6d328d3639b57164a279bad277146e7
Summary: Tests passed: 2863, ignored: 374 Build time: 0:48:09

Windows Build 1584 outcome was SUCCESS using a merge of 6c4d474fe6d328d3639b57164a279bad277146e7
Summary: Tests passed: 2863, ignored: 374 Build time: 0:48:36

Finally.  Ready for review.

I just realized that I need to bump the management api version (since this was originally for WF9, but is now for WF10).

Linux with security manager Build 1448 is now running using a merge of 3f08d999a2acb3fa2d3f6b4f2bdc6ced124cc481

Windows Build 1620 is now running using a merge of 3f08d999a2acb3fa2d3f6b4f2bdc6ced124cc481

Linux Build 6542 is now running using a merge of 3f08d999a2acb3fa2d3f6b4f2bdc6ced124cc481

Linux with security manager Build 1448 outcome was SUCCESS using a merge of 3f08d999a2acb3fa2d3f6b4f2bdc6ced124cc481
Summary: Tests passed: 821, ignored: 319 Build time: 0:04:59

Windows Build 1620 outcome was SUCCESS using a merge of 3f08d999a2acb3fa2d3f6b4f2bdc6ced124cc481
Summary: Tests passed: 2867, ignored: 374 Build time: 0:47:58

Linux Build 6542 outcome was SUCCESS using a merge of 3f08d999a2acb3fa2d3f6b4f2bdc6ced124cc481
Summary: Tests passed: 2867, ignored: 374 Build time: 0:48:24

Windows Build 1708 is now running using a merge of 9903f9b6323b5f1c9eb703b0e25e9a4984b8f0d5

Linux Build 6631 is now running using a merge of 9903f9b6323b5f1c9eb703b0e25e9a4984b8f0d5

Linux with security manager Build 1535 is now running using a merge of 9903f9b6323b5f1c9eb703b0e25e9a4984b8f0d5

Linux with security manager Build 1535 outcome was FAILURE using a merge of 9903f9b6323b5f1c9eb703b0e25e9a4984b8f0d5
Summary: Tests failed: 5 (5 new), passed: 829, ignored: 324 Build time: 0:05:02
Build problems:
Failed tests detected
Failed tests
org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseSubsystem(4): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseSubsystem(5): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseSubsystem(6): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseSubsystem(7): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseSubsystem(8): <no details avaliable>

Windows Build 1708 outcome was FAILURE using a merge of 9903f9b6323b5f1c9eb703b0e25e9a4984b8f0d5
Summary: Tests failed: 5 (5 new), passed: 2873, ignored: 379 Build time: 0:47:29
Build problems:
Failed tests detected
Failed tests
org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseSubsystem(4): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseSubsystem(5): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseSubsystem(6): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseSubsystem(7): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseSubsystem(8): <no details avaliable>

Linux Build 6631 outcome was FAILURE using a merge of 9903f9b6323b5f1c9eb703b0e25e9a4984b8f0d5
Summary: Tests failed: 5 (5 new), passed: 2872, ignored: 379, muted: 1 Build time: 0:48:32
Build problems:
Failed tests detected
Failed tests
org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseSubsystem(4): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseSubsystem(5): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseSubsystem(6): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseSubsystem(7): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseSubsystem(8): <no details avaliable>

Linux with security manager Build 1537 is now running using a merge of 4a3fa8caf007058cdff152774ca6d97b3119d128

Windows Build 1710 is now running using a merge of 4a3fa8caf007058cdff152774ca6d97b3119d128

Linux Build 6633 is now running using a merge of 4a3fa8caf007058cdff152774ca6d97b3119d128

Linux with security manager Build 1537 outcome was SUCCESS using a merge of 4a3fa8caf007058cdff152774ca6d97b3119d128
Summary: Tests passed: 834, ignored: 324 Build time: 0:05:03

Windows Build 1710 outcome was SUCCESS using a merge of 4a3fa8caf007058cdff152774ca6d97b3119d128
Summary: Tests passed: 2878, ignored: 379 Build time: 0:48:22

Linux Build 6633 outcome was SUCCESS using a merge of 4a3fa8caf007058cdff152774ca6d97b3119d128
Summary: Tests passed: 2878, ignored: 379 Build time: 0:48:53

Ready for review.

Linux Build 6679 is now running using a merge of 257cd6da0b7518203f033efdf088a1b7243aedb4

Windows Build 1753 is now running using a merge of 257cd6da0b7518203f033efdf088a1b7243aedb4

Linux with security manager Build 1580 is now running using a merge of 257cd6da0b7518203f033efdf088a1b7243aedb4

Linux with security manager Build 1580 outcome was SUCCESS using a merge of 257cd6da0b7518203f033efdf088a1b7243aedb4
Summary: Tests passed: 837, ignored: 324 Build time: 0:06:07

Windows Build 1753 outcome was SUCCESS using a merge of 257cd6da0b7518203f033efdf088a1b7243aedb4
Summary: Tests passed: 2882, ignored: 379 Build time: 0:47:43

Linux Build 6679 outcome was SUCCESS using a merge of 257cd6da0b7518203f033efdf088a1b7243aedb4
Summary: Tests passed: 2882, ignored: 379 Build time: 0:50:22

Linux Build 6807 is now running using a merge of 728782f42cf428248c8dd36304cb709b08b1626e

Linux with security manager Build 1705 is now running using a merge of 728782f42cf428248c8dd36304cb709b08b1626e

Windows Build 1882 is now running using a merge of 728782f42cf428248c8dd36304cb709b08b1626e

Linux with security manager Build 1705 outcome was SUCCESS using a merge of 728782f42cf428248c8dd36304cb709b08b1626e
Summary: Tests passed: 838, ignored: 326 Build time: 0:06:44

Windows Build 1882 outcome was SUCCESS using a merge of 728782f42cf428248c8dd36304cb709b08b1626e
Summary: Tests passed: 2883, ignored: 381 Build time: 0:48:13

Linux Build 6807 outcome was SUCCESS using a merge of 728782f42cf428248c8dd36304cb709b08b1626e
Summary: Tests passed: 2883, ignored: 381 Build time: 0:48:27

Linux Build 6819 is now running using a merge of 6ca1ab5a46b19f27dc62b70db453e81be247313d

Linux with security manager Build 1717 is now running using a merge of 6ca1ab5a46b19f27dc62b70db453e81be247313d

Windows Build 1894 is now running using a merge of 6ca1ab5a46b19f27dc62b70db453e81be247313d

Linux with security manager Build 1717 outcome was FAILURE using a merge of 6ca1ab5a46b19f27dc62b70db453e81be247313d
Summary: Tests failed: 3 (3 new), passed: 857, ignored: 326 Build time: 0:06:39
Build problems:
Failed tests detected
Failed tests
org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseAndMarshalModel(0): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testSubsystem(0): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testSubsystem(8): <no details avaliable>

Windows Build 1894 outcome was FAILURE using a merge of 6ca1ab5a46b19f27dc62b70db453e81be247313d
Summary: Tests failed: 4 (4 new), passed: 2876, ignored: 396 Build time: 0:46:19
Build problems:
Failed tests detected
Failed tests
org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseAndMarshalModel(0): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testSubsystem(0): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testSubsystem(8): <no details avaliable>

org.jboss.as.test.clustering.cluster.ejb.remote.RemoteFailoverTestCase(SYNC-tcp).testConcurrentFailover: <no details avaliable>

Linux Build 6819 outcome was FAILURE using a merge of 6ca1ab5a46b19f27dc62b70db453e81be247313d
Summary: Tests failed: 3 (3 new), passed: 2877, ignored: 396 Build time: 0:47:02
Build problems:
Failed tests detected
Failed tests
org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testParseAndMarshalModel(0): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testSubsystem(0): <no details avaliable>

org.jboss.as.clustering.infinispan.subsystem.SubsystemParsingTestCase.testSubsystem(8): <no details avaliable>

Linux with security manager Build 1739 is now running using a merge of 399a6e311fe6f9626a0511cf3b2e381597d23679

Linux Build 6842 is now running using a merge of 399a6e311fe6f9626a0511cf3b2e381597d23679

Windows Build 1917 is now running using a merge of 399a6e311fe6f9626a0511cf3b2e381597d23679

Linux with security manager Build 1739 outcome was SUCCESS using a merge of 399a6e311fe6f9626a0511cf3b2e381597d23679
Summary: Tests passed: 860, ignored: 325 Build time: 0:06:11

Linux Build 6842 outcome was FAILURE using a merge of 399a6e311fe6f9626a0511cf3b2e381597d23679
Summary: Tests failed: 2 (2 new), passed: 2891, ignored: 381, muted: 1 Build time: 0:47:30
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.jmx.ModelControllerMBeanTestCase.testAllMBeanInfos: <no details avaliable>

org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.test: <no details avaliable>

Windows Build 1917 outcome was FAILURE using a merge of 399a6e311fe6f9626a0511cf3b2e381597d23679
Summary: Tests failed: 2 (2 new), passed: 2892, ignored: 381 Build time: 0:50:23
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.jmx.ModelControllerMBeanTestCase.testAllMBeanInfos: <no details avaliable>

org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.test: <no details avaliable>

Linux with security manager Build 1742 is now running using a merge of 3269a41b947d820335cff551d3f188598b28e032

Windows Build 1920 is now running using a merge of 3269a41b947d820335cff551d3f188598b28e032

Linux Build 6845 is now running using a merge of 3269a41b947d820335cff551d3f188598b28e032

Linux with security manager Build 1742 outcome was SUCCESS using a merge of 3269a41b947d820335cff551d3f188598b28e032
Summary: Tests passed: 860, ignored: 325 Build time: 0:06:15

Linux Build 6845 outcome was SUCCESS using a merge of 3269a41b947d820335cff551d3f188598b28e032
Summary: Tests passed: 2894, ignored: 381 Build time: 0:45:48

Windows Build 1920 outcome was FAILURE using a merge of 3269a41b947d820335cff551d3f188598b28e032
Summary: Tests failed: 1 (1 new), passed: 2893, ignored: 381 Build time: 0:47:39
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.multinode.ejb.timer.database.DatabaseTimerServiceMultiNodeTestCase.testEjbTimeoutOnOtherNode: <no details avaliable>

Retest this please.

Windows Build 1921 is now running using a merge of 3269a41b947d820335cff551d3f188598b28e032

Linux Build 6846 is now running using a merge of 3269a41b947d820335cff551d3f188598b28e032

Linux with security manager Build 1743 is now running using a merge of 3269a41b947d820335cff551d3f188598b28e032

Linux with security manager Build 1743 outcome was SUCCESS using a merge of 3269a41b947d820335cff551d3f188598b28e032
Summary: Tests passed: 860, ignored: 325 Build time: 0:05:45

Windows Build 1921 outcome was SUCCESS using a merge of 3269a41b947d820335cff551d3f188598b28e032
Summary: Tests passed: 2894, ignored: 381 Build time: 0:46:16

Linux Build 6846 outcome was SUCCESS using a merge of 3269a41b947d820335cff551d3f188598b28e032
Summary: Tests passed: 2893, ignored: 381, muted: 1 Build time: 0:46:24

Please remove rebase-this flag.  Ready for review.

Based on chat today I think you know this, but in case not it still needs a rebase. Ping me when it's done so I can try and not let it sink from the mantle into the core.

Linux with security manager Build 1921 is now running using a merge of 8d7b1479b1ae1e60b1c9399067ed722d7979a9b8

Windows Build 2100 is now running using a merge of 8d7b1479b1ae1e60b1c9399067ed722d7979a9b8

Linux Build 7045 is now running using a merge of 8d7b1479b1ae1e60b1c9399067ed722d7979a9b8

Linux with security manager Build 1921 outcome was SUCCESS using a merge of 8d7b1479b1ae1e60b1c9399067ed722d7979a9b8
Summary: Tests passed: 876, ignored: 284 Build time: 0:06:56

Windows Build 2100 outcome was SUCCESS using a merge of 8d7b1479b1ae1e60b1c9399067ed722d7979a9b8
Summary: Tests passed: 2920, ignored: 346 Build time: 0:49:32

Linux Build 7045 outcome was FAILURE using a merge of 8d7b1479b1ae1e60b1c9399067ed722d7979a9b8
Summary: Tests failed: 109 (109 new), passed: 2713, ignored: 343, muted: 2 Build time: 0:55:56
Build problems:
Failed tests detected
Process exited with code 1
Failed tests
org.jboss.as.test.integration.ejb.remote.distinctname.EarDeploymentDistinctNameTestCase.testRemoteSLSBInvocation: <no details avaliable>

org.jboss.as.test.integration.ejb.timerservice.mgmt.PersistentCalendarTimerManagementTestCase.testResourceExistence: <no details avaliable>

org.jboss.as.test.integration.ejb.timerservice.mgmt.PersistentCalendarTimerManagementTestCase.testSuspendAndActivate: <no details avaliable>

org.jboss.as.test.integration.ejb.timerservice.mgmt.PersistentCalendarTimerManagementTestCase.testCancel: <no details avaliable>

org.jboss.as.test.integration.ejb.timerservice.mgmt.PersistentCalendarTimerManagementTestCase.testTrigger: <no details avaliable>

org.jboss.as.test.clustering.single.provider.ServiceProviderRegistrationTestCase: org.jboss.as.test.clustering.single.web.SimpleWebTestCase: <no details avaliable>

org.jboss.as.test.clustering.single.provider.ServiceProviderRegistrationTestCase: org.jboss.as.test.clustering.single.registry.RegistryTestCase: <no details avaliable>

org.jboss.as.test.clustering.single.provider.ServiceProviderRegistrationTestCase: org.jboss.as.test.clustering.single.dispatcher.CommandDispatcherTestCase: <no details avaliable>

org.jboss.as.test.clustering.single.provider.ServiceProviderRegistrationTestCase: org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase: <no details avaliable>

org.jboss.as.test.clustering.single.provider.ServiceProviderRegistrationTestCase: <no details avaliable>

org.jboss.as.test.clustering.messaging.ClusteredMessagingTestCase.testClusteredQueue: <no details avaliable>

##### there are 99 more failed tests, see build details

Linux Build 7047 is now running using a merge of 8d7b1479b1ae1e60b1c9399067ed722d7979a9b8

The Build 7045 failure:
[21:37:14][org.wildfly:wildfly-ts-integ-clustering] Running org.jboss.as.test.clustering.cluster.ejb.remote.RemoteFailoverTestCase
[22:01:20][org.wildfly:wildfly-ts-integ-clustering]
[22:01:20][org.wildfly:wildfly-ts-integ-clustering] Results :
[22:01:20][org.wildfly:wildfly-ts-integ-clustering]
[22:01:20][org.wildfly:wildfly-ts-integ-clustering] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
[22:01:20][org.wildfly:wildfly-ts-integ-clustering]
[22:01:20][org.wildfly:wildfly-ts-integ-clustering] [ERROR] There was a timeout or other error in the fork

This is happening regularly now. If you look at the history of the various CI jobs, most, maybe all recent cases of large #s of failures are due to this test not completing.
I was hoping this PR would fix it. Guess not. :( That test needs to be disabled until it works.

Linux Build 7047 outcome was FAILURE using a merge of 8d7b1479b1ae1e60b1c9399067ed722d7979a9b8
Summary: Tests failed: 78 (25 new), passed: 2801, ignored: 346, muted: 3 Build time: 1:00:36
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.testEAP610StandaloneJtsXml: <no details avaliable>

org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.testEAP640StandaloneHornetQCollocatedXml: <no details avaliable>

org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.testEAP640DomainXml: <no details avaliable>

org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.testEAP600StandaloneFullHaXml: <no details avaliable>

org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.testEAP610StandaloneXtsXml: <no details avaliable>

org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.testEAP610StandaloneFullHaXml: <no details avaliable>

org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.testEAP610StandaloneFullXml: <no details avaliable>

org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.testEAP600StandaloneJtsXml: <no details avaliable>

org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.testEAP640StandaloneMinimalisticXml: <no details avaliable>

org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.testEAP640StandaloneFullHaXml: <no details avaliable>

org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.testEAP640HostXml: <no details avaliable>

##### there are 68 more failed tests, see build details

@bstansberry Fixing of RemoteFailoverTestCase is beined tracked on https://issues.jboss.org/browse/WFLY-3532 and richard has been working on that past weeks so IMHO it won't get forgotten if we go ahead and ignore it..

https://github.com/wildfly/wildfly/pull/7769 @Ignores that test

retest this please

Windows Build 2117 is now running using a merge of 8d7b1479b1ae1e60b1c9399067ed722d7979a9b8

Linux Build 7063 is now running using a merge of 8d7b1479b1ae1e60b1c9399067ed722d7979a9b8

Linux with security manager Build 1938 is now running using a merge of 8d7b1479b1ae1e60b1c9399067ed722d7979a9b8

Linux with security manager Build 1938 outcome was SUCCESS using a merge of 8d7b1479b1ae1e60b1c9399067ed722d7979a9b8
Summary: Tests passed: 877, ignored: 284 Build time: 0:06:27

Windows Build 2117 outcome was FAILURE using a merge of 8d7b1479b1ae1e60b1c9399067ed722d7979a9b8
Summary: Tests failed: 2 (2 new), passed: 2944, ignored: 349, muted: 2 Build time: 0:49:20
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.clustering.messaging.ClusteredMessagingTestCase.testClusteredQueue: <no details avaliable>

org.jboss.as.test.clustering.messaging.ClusteredMessagingTestCase.testClusteredTopic: <no details avaliable>

Linux Build 7063 outcome was FAILURE using a merge of 8d7b1479b1ae1e60b1c9399067ed722d7979a9b8
Summary: Tests failed: 1 (1 new), passed: 2945, ignored: 349, muted: 2 Build time: 0:55:39
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.ejb.timerservice.mgmt.PersistentCalendarTimerManagementTestCase.testResourceExistence: <no details avaliable>

retest this please

Linux with security manager Build 1941 is now running using a merge of 8d7b1479b1ae1e60b1c9399067ed722d7979a9b8

Windows Build 2120 is now running using a merge of 8d7b1479b1ae1e60b1c9399067ed722d7979a9b8

Linux Build 7066 is now running using a merge of 8d7b1479b1ae1e60b1c9399067ed722d7979a9b8

Linux with security manager Build 1941 outcome was SUCCESS using a merge of 8d7b1479b1ae1e60b1c9399067ed722d7979a9b8
Summary: Tests passed: 877, ignored: 284 Build time: 0:06:25

Linux Build 7066 outcome was SUCCESS using a merge of 8d7b1479b1ae1e60b1c9399067ed722d7979a9b8
Summary: Tests passed: 2938, ignored: 353, muted: 1 Build time: 0:46:52

Windows Build 2120 outcome was SUCCESS using a merge of 8d7b1479b1ae1e60b1c9399067ed722d7979a9b8
Summary: Tests passed: 2937, ignored: 353, muted: 2 Build time: 0:50:06

Dear Paul,
I need your help, please. I've spent two days to clarify, why my WildFly9 Infinispan configuration stop working in WildFly10.
I just uses a cache with a custom store configuration. Cache configured through the jboss-cli like this:
/profile=full-ha/subsystem=infinispan/cache-container=cacheContainer:add()
/profile=full-ha/subsystem=infinispan/cache-container=cacheContainer/transport=TRANSPORT:add(lock-timeout=60000)
/profile=full-ha/subsystem=infinispan/cache-container=cacheContainer/replicated-cache=test:add(mode=ASYNC)
/profile=full-ha/subsystem=infinispan/cache-container=cacheContainer/replicated-cache=test/store=STORE:add(class=org.infinispan.persistence.sifs.configuration.SoftIndexFileStoreConfigurationBuilder,passivation=false,preload=false,purge=false,properties={dataLocation=${jboss.server.data.dir}/infinispan/container/testData,indexLocation=${jboss.server.data.dir}/infinispan/container/testIndex})

Ok, I read your comments and changed scripts accordingly. Nothing changed.
I know, that to start my Infinispan container in WF9 I need to inject CacheContainer instance inside the EJB container and after that, I can use CacheContainer.getCache("test") to get access to a properly configured cache instance.
@Singleton
@Startup
public class CacheAccessBean {

@Resource(lookup = "java:jboss/infinispan/container/cacheContainer")
private CacheContainer cc;

@PostConstruct
public void init() {
    Cache cache = cc.getCache("test");
...
}

This is not work in WilfFly10. As I can see, CacheContainer injected into the EJB container without named configuration "test", so the invocation of CacheContainer.getCache("test") returns default cache. Injection of the Cache instance itself by the JNDI link like "java:jboss/infinispan/container/cacheContainer/test" didn't work in WL9 and here too.
What did I wrong? Is there any special trick to start Cache service with the defined configuration?
Thank you for any advice.

@Maxoid This is not the appropriate place to ask support questions.  Please use the forums.


Documentation for exporting openai/whisper-large-v3 to ONNX

Feature request
Hello, I am exporting the OpenAI Whisper-large0v3 to ONNX and see it exports several files, most importantly in this case encoder (encoder_model.onnx & encoder_model.onnx.data) and decoder (decoder_model.onnx, decoder_model.onnx.data, decoder_with_past_model.onnx, decoder_with_past_model.onnx.data) files. I'd like to also be able to use as much as possible from the pipe in the new onnx files:
pipe = pipeline(     "automatic-speech-recognition",     model=model,     tokenizer=processor.tokenizer,     feature_extractor=processor.feature_extractor,     max_new_tokens=128,     chunk_length_s=30,     batch_size=16,     return_timestamps=True,     torch_dtype=torch_dtype,     device=device, )
Is there documentation that explains how to incorporate all these different things? I know transformer models are much different in this whole process and I cannot find a clear A -> B process on how to export this model and perform tasks such as quantization, etc. I see I can do the following for the tokenizer with ONNX, but I'd like more insight about the rest I mentioned above (how to use the seperate onnx files & how to use as much as the preexisting pipeline).
processor.tokenizer.save_pretrained(onnx_path)
I also see I can do:
model = ORTModelForSpeechSeq2Seq.from_pretrained(         model_id, export=True     )
but I cannot find documentation on how to specify where it is exported to, which seem's like I am either missing something fairly simple or it is just not hyperlinked in the documentation.
Motivation
I'd love to see further documentation on the entire export process for this highly popular model. Deployment is significantly slowed due to there not being a easy to find A -> B process for exporting the model and using the pipeline given in the vanilla model.
Your contribution
I am able to provide additional information to make this process easier.

@mmingo848 You can use:
optimum-cli export onnx --help
optimum-cli export onnx --model openai/whisper-large-v3 whisper_onnx

and then use ORTModelForSpeechSeq2Seq.
Although decoder_model.onnx and decoder_with_past_model.onnx are saved in the output folder, they are not required for inference and you can just use decoder_model_merged.onnx for the decoder, which handles both without KV cache (first decoding step) and with KV cache (following decoding steps) cases. ORTModelForSpeechSeq2Seq does not use decoder_model.onnx and decoder_with_past_model.onnx by default.
Feel free to refer to:

https://huggingface.co/docs/optimum/main/en/exporters/onnx/usage_guides/export_a_model
https://huggingface.co/docs/optimum/main/en/onnxruntime/usage_guides/pipelines
https://huggingface.co/docs/optimum/main/en/onnxruntime/package_reference/modeling_ort#optimum.onnxruntime.ORTModelForSpeechSeq2Seq

Let me know if this documentation is helpful!

@fxmarty  the log:
Validating ONNX model /b4-ai/share_model_zoo/LLM/openai/onnx_whisper-large-v3/encoder_model.onnx...
        -[✓] ONNX model output names match reference model (last_hidden_state)
        - Validating ONNX Model output "last_hidden_state":
                -[✓] (2, 1500, 1280) matches (2, 1500, 1280)
                -[x] values not close enough, max diff: 0.019733428955078125 (atol: 0.001)
Validating ONNX model /b4-ai/share_model_zoo/LLM/openai/onnx_whisper-large-v3/decoder_model.onnx...
        -[✓] ONNX model output names match reference model (logits)
        - Validating ONNX Model output "logits":
                -[✓] (2, 16, 51866) matches (2, 16, 51866)
                -[✓] all values close (atol: 0.001)
The ONNX export succeeded with the warning: The maximum absolute difference between the output of the reference model and the ONNX exported model is not within the set tolerance 0.001:
- last_hidden_state: max diff = 0.019733428955078125.

you can see [x] values not close enough, max diff: 0.019733428955078125 (atol: 0.001) for the "last_hidden_state",  Is it normal for this situation to occur?

@MrRace Yes it can happen, I would not be worried. We should improve the warning.

@mmingo848 You can use:
optimum-cli export onnx --help
optimum-cli export onnx --model openai/whisper-large-v3 whisper_onnx

and then use ORTModelForSpeechSeq2Seq.
Although decoder_model.onnx and decoder_with_past_model.onnx are saved in the output folder, they are not required for inference and you can just use decoder_model_merged.onnx for the decoder, which handles both without KV cache (first decoding step) and with KV cache (following decoding steps) cases. ORTModelForSpeechSeq2Seq does not use decoder_model.onnx and decoder_with_past_model.onnx by default.
Feel free to refer to:

https://huggingface.co/docs/optimum/main/en/exporters/onnx/usage_guides/export_a_model
https://huggingface.co/docs/optimum/main/en/onnxruntime/usage_guides/pipelines
https://huggingface.co/docs/optimum/main/en/onnxruntime/package_reference/modeling_ort#optimum.onnxruntime.ORTModelForSpeechSeq2Seq

Let me know if this documentation is helpful!

@fxmarty I exported the Whisper ONNX model files using the following command:
optimum-cli export onnx --model /share_model_zoo/LLM/openai/whisper-large-v3/ --task automatic-speech-recognition --device cuda:0 /share_model_zoo/LLM/openai/onnx_gpu_whisper-large-v3/

Under the export directory /share_model_zoo/LLM/openai/onnx_gpu_whisper-large-v3/, there are four ONNX model files: encoder_model.onnx_data, encoder_model.onnx, decoder_model.onnx_data, and decoder_model.onnx. However, the decoder_model_merged.onnx and decoder_with_past_model.onnx files you mentioned are not present. Why?

@MrRace You need --task automatic-speech-recognition-with-past. There should be a log during the export about it (that specifying --task automatic-speech-recognition disables KV cache).

@MrRace You need --task automatic-speech-recognition-with-past. There should be a log during the export about it (that specifying --task automatic-speech-recognition disables KV cache).

@fxmarty Thank you very much for your response. However, after following the commands you provided, the following error occurred. How can I fix this error? Thanks again.
Validation for the model /share_model_zoo/LLM/openai/onnx_gpu_with-past-whisper-large-v3/decoder_model_merged.onnx raised: [ONNXRuntimeError] : 1 : FAIL : Load model from /b4-ai/share_model_zoo/LLM/openai/onnx_gpu_with-past-whisper-large-v3/decoder_model_merged.onnx failed:/onnxruntime_src/onnxruntime/core/graph/model.cc:180 onnxruntime::Model::Model(onnx::ModelProto&&, const PathString&, const IOnnxRuntimeOpSchemaRegistryList*, const onnxruntime::logging::Logger&, const onnxruntime::ModelOptions&) Unsupported model IR version: 10, max supported IR version: 9

Traceback (most recent call last):
  File "/share/opt/minicoda/lib/python3.11/site-packages/optimum/exporters/onnx/convert.py", line 1207, in onnx_export_from_model
    validate_models_outputs(
  File "/share/opt/minicoda/lib/python3.11/site-packages/optimum/exporters/onnx/convert.py", line 182, in validate_models_outputs
    raise exceptions[-1][1]
  File "/share/opt/minicoda/lib/python3.11/site-packages/optimum/exporters/onnx/convert.py", line 165, in validate_models_outputs
    validate_model_outputs(
  File "/share/opt/minicoda/lib/python3.11/site-packages/optimum/exporters/onnx/convert.py", line 233, in validate_model_outputs
    raise error
onnxruntime.capi.onnxruntime_pybind11_state.Fail: [ONNXRuntimeError] : 1 : FAIL : Load model from /share_model_zoo/LLM/openai/onnx_gpu_with-past-whisper-large-v3/decoder_model_merged.onnx failed:/onnxruntime_src/onnxruntime/core/graph/model.cc:180 onnxruntime::Model::Model(onnx::ModelProto&&, const PathString&, const IOnnxRuntimeOpSchemaRegistryList*, const onnxruntime::logging::Logger&, const onnxruntime::ModelOptions&) Unsupported model IR version: 10, max supported IR version: 9

optimum : 1.18.0
onnx                     1.16.0
onnxruntime               1.17.1
onnxruntime_extensions    0.10.1
onnxruntime-gpu           1.17.1

Yes, this was fixed in https://github.com/huggingface/optimum/pull/1780, which is not yet in a release.
Please downgrade to onnx 1.15 or use optimum from source.

Yes, this was fixed in #1780, which is not yet in a release.
Please downgrade to onnx 1.15 or use optimum from source.

@fxmarty Thanks a lot, it can work. After obtaining the decoder_model_merged.onnx and decoder_with_past_model.onnx files, how can I perform inference on test audio? Could you provide a complete example? Or could you advise on how to modify my example below? Thank you very much.
import os
import pdb

from onnxruntime import InferenceSession
import onnxruntime as ort
from transformers import WhisperProcessor, WhisperForConditionalGeneration
import time
import soundfile as sf

print("onnxruntime device=", ort.get_device())

onnx_model_dir = "/share_model_zoo/LLM/openai/onnx_gpu_with-past-whisper-large-v3/"
onnx_model_file = "decoder_model_merged.onnx"
onnx_model_file_path = os.path.join(onnx_model_dir, onnx_model_file)
print("Use onnx file=", onnx_model_file_path)
is_use_gpu = True
if is_use_gpu:
    session = InferenceSession(onnx_model_file_path, providers=['CUDAExecutionProvider'])
    print("Use onnxruntime-GPU")
else:
    session = InferenceSession(onnx_model_file_path, providers=['CPUExecutionProvider'])
    print("Use onnxruntime-CPU")

processor = WhisperProcessor.from_pretrained(onnx_model_dir)

test_audio_file = "./samples/jfk.wav"
array, sampling_rate = sf.read(test_audio_file)

input_features = processor(array, sampling_rate=sampling_rate, return_tensors="pt").input_features

# for i in range(len(session.get_inputs())):
#     print("session.get_inputs()[{}].name={}".format(i, session.get_inputs()[i].name))

# inference
decoder_input = {session.get_inputs()[0].name: input_features}
decoder_output = session.run(None, decoder_input)
print("decoder_output=", decoder_output)

The above code will raise an error, such as ValueError: Required inputs (['encoder_hidden_states', 'past_key_values.0.decoder.key', 'past_key_values.0.decoder.value', 'past_key_values.0.encoder.key', 'past_key_values.0.encoder.value', 'past_key_values.1.decod ...  and so on.

Hi @MrRace, if you don't want to reimplement the inference code from scratch, I advise you to use https://huggingface.co/docs/optimum/main/en/onnxruntime/package_reference/modeling_ort#optimum.onnxruntime.ORTModelForSpeechSeq2Seq. An example is available there. By default, only encoder_model.onnx and decoder_model_merged.onnx will be used at inference.
I advise you to use https://github.com/lutzroeder/netron if you would like to visualize the ONNX graphs and understand their inputs/outputs.

Hi @MrRace, if you don't want to reimplement the inference code from scratch, I advise you to use https://huggingface.co/docs/optimum/main/en/onnxruntime/package_reference/modeling_ort#optimum.onnxruntime.ORTModelForSpeechSeq2Seq. An example is available there. By default, only encoder_model.onnx and decoder_model_merged.onnx will be used at inference.
I advise you to use https://github.com/lutzroeder/netron if you would like to visualize the ONNX graphs and understand their inputs/outputs.

@fxmarty Thanks a lot for your reply, yeah, I want to implement it from scratch to better understand the overall inference process.


Remove superfluous 'modules' in puppet file path.

Exactly how puppet converts ambiguous paths into absolute paths I'm not entirely
sure. I am sure, however, that the path modified that this commit resolved
into:
/etc/puppet/modules/modules/files/supervisor/logrotate

where the new path resolves to
/etc/puppet/modules/modules/supervisor/files/logrotate
The later, of course, being correct.
Signed-off-by: Brian L. Troutwine<EMAIL_ADDRESS>

A couple things:

Please keep your pull requests on a single topic, so that it is easier for me to merge individual patches.
I am 100% certain that the path is, in fact, correct. I suspect you have a different configuration that is leading to the files ending up not where you expect. What version of puppet are you using, and what does the relevant section of your puppet.conf look like? (modulepath is the relevant setting)

I'm going to close this instance of the pull so you can divide it up into separate topics.

Please keep your pull requests on a single topic, so that it is easier for me to merge individual patches.

Hmm, that's peculiar; I intended to send only the first patch. Apologies.

I am 100% certain that the path is, in fact, correct.

As was I. It does, in fact, work when I run puppetmasterd directly, but not when it's run in production mode, run in thin and fronted by nginx. At least, as both of those are configured.

I suspect you have a different configuration that is leading to the files ending up not where you expect. What version of puppet are you using,

2.7.9

and what does the relevant section of your puppet.conf look like? (modulepath is the relevant setting)

puppet.conf's running defaults, so
# puppet --configprint modulepath
/etc/puppet/modules:/usr/share/puppet/modules

and the relevant section of supervisord config giving my thin invocation:
[program:puppetmaster]
command=/usr/bin/thin start -e development --socket /var/run/puppet/master.%(process_num)02d.sock --user puppet --group puppet --chdir /etc/puppet -R /etc/puppet/config.ru

The path '/etc/puppet/modules/modules/files/supervisor/logrotate' was pulled directly from my nginx error log.

Huh. That is... weird. I'm unfamiliar with running under thin, but your puppet version is one I would expect to actually complain if you neglect to include "modules" in the path - as of puppet 2.6 leaving the "modules/" prefix out became deprecated and began to cause a warning.
"Notice that the file source path includes a modules/ component. In Puppet version 0.25 and later, you must include this component in source paths in order to serve files from modules. Puppet 0.25 will still accept source paths without it, but it will warn you with a deprecation notice about “Files found in modules without specifying ‘modules’ in file path”. In versions 0.24 and earlier, source paths should not include the modules/ component."
Could be a bug, but without the ability to explore your specific configuration I can't be sure; based on the above-quoted documentation excerpt I'm inclined to not merge the change, I hope you understand.

Oh, absolutely. Clearly there's something screwy going on with my end of things.
Do you have a reference to the documentation you quote, perhaps?

That came from: http://docs.puppetlabs.com/guides/modules.html#example


Car Racing Game

I am GSSOC'22 Contributor
I wanted to add Car Racing JS project...
Car Racing Game is one of the best and fun Js Project..

@arpit456jain

@itsmohitnamdeo make the PR but try to reduce its size

@itsmohitnamdeo


Parse error in Bcc header can make Bcc addresses visible to recipients

Perhaps there's a configuration to make this fail differently, but I found that when there is a parse error in the Bcc header, instead of a failure that prevents the mail from being sent, the Bcc header ended up encoded (and appended after the To) header. For example:
2.2.4 :093 > m = Mail.new; m[:to] =<EMAIL_ADDRESS>m[:bcc] = ['Not \(valid\<EMAIL_ADDRESS>m.header.fields[1].encoded
 => "bcc: Not \\(valid\\<EMAIL_ADDRESS>
as opposed to
2.2.4 :095 > m = Mail.new; m[:to] =<EMAIL_ADDRESS>m[:bcc] = ['"Not \(valid\)"<EMAIL_ADDRESS>m.header.fields[1].encoded
 => ""

I'm happy to work on a PR for this, but I wanted to get your thoughts on it first.

Great catch. Tricky one. We fall back to UnstructuredField for parse errors, but clearly shouldn't in this case. Better to guarantee BccField behavior. In which case we're best off raising the parse exception rather than putting the fallback field in place. PR welcome 😊


[Help] Sidecar command.stdout.on('data', () => {...}) not working

Code: Repo
Problem:
I have a Python application built to an .exe (pyinstaller)
It print json as strings to the terminal when done processing an image (here)
It works fine in the terminal, prints one line of json as string when one image is done processing
But when it works as a sidecar, and when I use command.stdout.on('data', line => console.log) (here)
It logs nothing to the console when it is running
And when the .exe process ends
The tauri app suddenly logs all the json strings that should be logged before, to the console all at once
When it's running: Not logging the things I want

Done running: (suddenly logging all the things I want)

Info: tauri info:
Environment
  › OS: Windows 10.0.22000 X64
  › Webview2: 104.0.1293.63
  › MSVC:
      - Visual Studio Build Tools 2019
      - Visual Studio Build Tools 2022
  › Node.js: 18.7.0
  › npm: 8.15.0
  › pnpm: 6.11.5
  › yarn: 1.22.18
  › rustup: 1.25.1
  › rustc: 1.62.1
  › cargo: 1.62.1
  › Rust toolchain: stable-x86_64-pc-windows-msvc

Packages
  › @tauri-apps/cli [NPM]: 1.0.5
  › @tauri-apps/api [NPM]: 1.0.2
  › tauri [RUST]: 1.0.5,
  › tauri-build [RUST]: 1.0.4,
  › tao [RUST]: 0.12.2,
  › wry [RUST]: 0.19.0,

App
  › build-type: bundle
  › CSP: unset
  › distDir: ../dist
  › devPath: http://localhost:5173/

App directory structure
  ├─ .git
  ├─ build
  ├─ node_modules
  ├─ public
  ├─ py-src
  ├─ src
  ├─ src-tauri
  └─ test_set

In my tests I had the same problem when running directly in the terminal. You need to flush the stdout buffer when printing, so instead of print(message) you call print(message, flush = True).

In my tests I had the same problem when running directly in the terminal. You need to flush the stdout buffer when printing, so instead of print(message) you call print(message, flush = True).

I added it to all of my prints and the strange behaviour is still there.
I even tried changing all the print to sys.stdout.write then flush
Rebuilt and it's still the same


On breakpoint enable/disable, breakpoint/method list browsers not updated (3.0.84)

When you have open project browser, breakpoint browser, and method list, all with breakpoints showing in red say,
and you disable breakpoints, using the menu item...
the highlight is not updated in the breakpoint or method list browsers, they are still red. PB is updated and correct.
If you click on and off a method in any of the browser, all the browsers do get updated.

Debugger breakpoints are the only breakpoints I see that are not updating properly. Breakpoint browser, method list browser, and project browser all seem to update in 3.0.89. Could you confirm?

Have a fix in the waiting branch in the Jadeite project. Will move to oscar after customer release finished. Tagging as Move to Oscar as a reminder.

looks okay in 3.0.92-2


added images to intro page

Added images to the Intro page

please remove the .DS_Store files

deleted.


Animation - Processing Sketch Requirements

Task 2: Animation
The task 2 of the exercise performance (LN). Write a Processing sketch that has an animated element. Conditions:

Follow the rules written down in exercise_performance_00_general.pdf.
The size of the drawing area is 640x480px.
Have some non-animated drawing in the background (> 5 elements. Don't use too many).
Have an animated "thing" (> 5 elements) flying from left to right (or top down).
When the "thing" leaves the drawing area, let it come back from the opposite side.
Comment your sketch properly (the rules are given in slides 02_Comments_Variables.pdf).
Store 2 frames of your animation as images (that show what's animated).
The sketch must be named task_2_animation.pde and the images task_2_animation_1.tif and task_2_animation_2.tif.
Hand in the images (.tif) and sketch (.pde) in iLearn!


Release method instead of change for sliders

https://github.com/KohakuBlueleaf/a1111-sd-webui-haku-img/issues/22

this is good but mixed with lens distoration feature which I have some concerns
will wait for lens distoration one be resolved

this is good but mixed with lens distoration feature which I have some concerns will wait for lens distoration one be resolved

I didn't understand a bit
The fish eye effect (with positive parameters)  will create black areas anyway:D
And you can adjust the size through 2 parameters

this is good but mixed with lens distoration feature which I have some concerns will wait for lens distoration one be resolved
https://github.com/KohakuBlueleaf/a1111-sd-webui-haku-img/pull/25


Build strategies design doc

Contrary to usual practice,
if you disagree or would like to add to the document,
please counter-PR with your changes.
We can go back and forth until we're happy,
or at least it's in an intermediate state we can tolerate.

          1 Message

:book:
mdspell or proselint not available - prose not linted

  Generated by :no_entry_sign: Danger

Codecov Report

Merging #496 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master    #496      +/-   ##
=========================================
+ Coverage    69.4%   69.4%   +<.01%
=========================================
  Files         196     196
  Lines       10685   10695      +10
=========================================
+ Hits         7416    7423       +7
- Misses       2734    2737       +3
  Partials      535     535

Impacted Files
Coverage Δ

main.go
0% <0%> (ø)
:arrow_up:

graph/actions.go
96.36% <0%> (+0.53%)
:arrow_up:

Continue to review full report at Codecov.

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

I'll prepare a counter-PR with these changes.

New requirement: some builders/plugins e.g. Maven plugins require the .git repo to be present inside the builder container. Should we always copy/mount including .git or make this an option of the builder image? cc @nyarly @JC1738

We will copy for sure because it's unsafe to do otherwise.


Fix SRIOV lane: bump kubevirtci

What this PR does / why we need it:
Bump kubevirtci to get latest changes sriov provider kubevirt/kubevirtci#459
With those changes SRIOV lane should run tests successfully.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

https://github.com/kubevirt/kubevirtci/pull/459

/test pull-kubevirt-e2e-kind-1.17-sriov

/test pull-kubevirt-e2e-kind-1.17-sriov

/test pull-kubevirt-e2e-kind-1.17-sriov

/cc @qinqon @EdDev @AlonaKaplan

/lgtm

/approve

Thank you!

/test pull-kubevirt-e2e-k8s-cnao-1.17


Modify paediatric filter under 7 yrs

Instead of excluding or including paediatric data under 7yrs, make the checkbox switch between paediatric under 7yrs and non paediatric over 7yrs (so never including both semiologies).

this was a major undetected bug until my new test
test_paed_exclusions_query_semio
until now, excluding paediatric cases with exclude_paediatric_cases() was actually excluding anything with either a y or a n and keeping the NaNs/nulls.

bug fixed in 0211f14aa288d309ad99851c967d290d56e6ca07

@fepegar please can the checkbox have a tooltip?
Exclude all cases for which we are certain that the semiology was reported in a patient under 7-years old

also @fepegar :
is it possible to modify the SemiologyVisualisation.py so that

No change in this part: as it is currently, the paediatric checkbox remains unticked by deafult and this does the same thing it currently does (i.e. sets paediatricCheckBox.isChecked() to False and include_paediatric_cases to False and so runs exclude_paediatric_cases)

if and when the check box is ticked, it now runs only_paediatric_cases() from exclusions.py?

The checkbox should mean "include", not "exclude". So the tooltip should probably say "Include..."
But if it's ticked, why should it include only paediatric cases?
Also, it says padeiatric in only_paediatric_cases.

So the tooltip should probably say "Include..."

perfectly agree! thanks

But if it's ticked, why should it include only paediatric cases?

because it would mean a paediatrician or paediatric epileptologist is querying the database. As mentioned elsewhere, the semiology of adults and children under 7 are very different due to differential brain maturity and functon.

Also, it says padeiatric in only_paediatric_cases.

it does indeed good spot. This is a propagated typo which exists in the database so won't fix for now.

I think this can be closed?


Excessive DNS Queries

Before start

check if your issue is known: https://github.com/FriendsOfGalaxy/galaxy-integration-paradox/wiki/Common-problems

Describe the bug
GOG is making an excessive number of DNS queries to api.paradoxplaza.com.
To Reproduce
I have previously logged into my Paradox account.
It is currently not connected.
Over a 24 hour period, I'm noting about 2400 DNS queries.
Expected behavior
I expect about a quarter of that behavior at the high end.
plugin-paradox-bfa5a6c9-r0c3-5g28-b921-f4cd75d4999a.txt

Hi @Xelveki thanks for report. Those are small API GETs a few Kb each but anyway - it may sum up to 10Mb for all day.
It just pooling to check for newly added games for better experience, but nobody is buying Paradox games everyday. I would decrease the check ratio 5 times. Do you think is it ok?

That seems reasonable. Doesn't seem like it should need to check the Paradox API more than the Galaxy checks GOG.
On Thu, Sep 24, 2020, at 08:01, FriendsOfGalaxy wrote:

Hi @Xelveki https://github.com/Xelveki thanks for report. Those are small API GETs a few Kb each but anyway - it may sum up to 10Mb for all day.

It just pooling to check for newly added games for better experience, but nobody is buying Paradox games everyday. I would decrease the check ratio 5 times. Do you think is it ok?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/FriendsOfGalaxy/galaxy-integration-paradox/issues/7#issuecomment-698401938, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARDIA6544KRVV4DGQXE5OX3SHNNN3ANCNFSM4RWFDN6A.

Joshua Miller

done.

That seems reasonable. Doesn't seem like it should need to check the Paradox API more than the Galaxy checks GOG.

I believe GOG has some kind of push notifications from their backend, so they do not need pooling to refresh ownership information.


Modulecounts.com and number of packages available

I'm the maintainer of modulecounts.com, which tries to give a very rough comparison of how many packages are available across different programming languages. I added the "Number of packages" number from http://godoc.org/-/index at a user's request back in June.
Since that number has begun growing so amazingly fast, some other users have objected because it seems to include quite a few forks of the same packages, rather than being a count of more truly unique packages.
Is there a "more correct" thing I should be reporting for Go? I haven't been able to find a package repository in the traditional sense. I don't want to exclude a language just because it's too easy to share code, but I also want to try to keep numbers as comparable as possible.
I realize that the github issues page for a site is not the normal forum for asking this sort of question. If there's a better place, please point me to it.
Regards,
Erik DeBill

Closing this as I don't see an action to take. Happy to reopen if that's not the case.

Here's a discussion about the godoc.org numbers reported on modulecounts.com:  https://github.com/mikeal/go-stats/blob/master/README.md


(PUP-3088) Fix zone provider debug call

The provider should directly call Puppet.debug and Puppet.err
because of the issue described in the PUP ticket.

Can you update the commit message with the PUP ticket?

CLA signed by all contributors.

It looks like there are other calls to self.fail in the provider that will trigger the same bug.

ping @joshcooper what's the state of this?

I'll follow up on this while @joshcooper's out. @hunner any updates on Josh's comments?

@MikaelSmith Updating the PR now...

I'm not sure I see the reason in the ticket why this uses the resource, instead of just falling through to to_s.

Lost comments from Josh on https://github.com/hunner/puppet/commit/afdbb23
@MikaelSmith I think you're referring to calling source.path vs. source.resource.path ? This is actually the problem that this commit fixes, as some providers provide .path property getters that override the provider's default path method such as https://github.com/puppetlabs/puppet/blob/3.8.1/lib/puppet/provider/zone/solaris.rb#L64
I can rename the default provider.path method to provider.resource_path or something, though this could have large ramifications than expected if anyone was otherwise depending on this behavior. What would you like?

No, I mean that for most providers .path wasn't defined, and they would fall through to the else clause to print using to_s. You've changed the behavior on all providers to now use the printing we do for Types, which changes the output as I outlined in my comment.

:+1:


Add GitHub CI config

This PR configures a GitHub workflow that matches the existing GitLab CI: https://gitlab.com/ros-tracing/ros2_tracing/-/blob/b695e4e367fb6e250d3147ab6b851b25a0e50299/.gitlab-ci.yml. It builds ros2_tracing with/without LTTng and with/without tracing being disabled, and checks if the tracing instrumentation is indeed available (or not).
The "sanity checks" workflow makes sure that the tracing instrumentation can be enabled when starting from a default source build or a binary installation, as explained in the build instructions in the README: https://github.com/ros2/ros2_tracing#building. This will also be documented on docs.ros.org, see: https://github.com/ros2/ros2_documentation/pull/2877.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@1fa9011). Click here to learn what that means.
The diff coverage is n/a.

This only affects local CI, so I'll merge this.


Mostly improve stats gui

Lots of typo
Fix some inconsitancy with visibility (but there is still pbm)
Rework options as a toolbar
[x] Upper case on title
[x] tooltip for COM
[x] 2 x 2 icons for the options

Thanks, Icons sounds like a great idea.

It's fine now.

Looks good. Thanks


Chroma and Spectrum

Spectrum comes with a built-in library called tinyColor for color manipulation. Is there a reason to be using both libraries?
Not really a bug, was just curious as it might help cut back on some unnecessary code? Unless chroma does something TinyColor can't do. But I believe they do very similar things.

Chroma was used in this project before Spectrum was introduced, so I guess the original dev didn't knew about TinyColor. Personally, I had no idea about it.
Chroma's function in this project is to return a gradient of colors based on either Bézier curve, RGB, HSL or LCH.
TinyColor might be able to do that, but I'm not sure if it would be a simple change.

Awe okay, I can take a look and see if I can replicate that feature in TinyColor, if so it will help cut back on libraries if possible.

I've tried some changes last night and my conclusion is that Chroma is needed because Tinycolor doesn't make gradients, and its sub-library that does it, Tinygradient, doesn't support the Bézier and LCH.
In the end I'd have the same number of libraries and less color options. I am not sure how many people use the other color modes, but there's no point in doing so if there would still be two libraries on the project.
Other findings:

The Colorjs library was considered, but it wouldn't reduce the number of libraries and it doesn't seem to support Bézier curves either at the time.
Updating Grapick 0.1.7 to 0.1.10 resulted in issues where the latest Grapick.getColor() returns a "rgba(r, g, b, a)" string, which broke Chroma because it works with "#hexes" or [r, g, b, a], but not a rgba string.


Gitter link

The group for Quasar on Gitter is no longer there so the link is now dead.

Yes, I've removed it. It was barely used.

Makes sense. Should probably remove it from the README too though. :)

We've created a Discord community for Quasar since the Gitter link was dead and plenty of people have joined already, @MaxXor it would be great if you could join
https://discordapp.com/invite/4vSJ372


[UI] UEFI support flag in host details

Description
This PR fixes #7356 adds the UEFI flag like below in Host details

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[x] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[x] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

@blueorangutan ui


Link to the artifacts of the latest run?

Feature Description
Hi,
We would like to link to the latest artifact. There is a relatively straightforward way this could be done. Right now one can link a specific run like this:
https://///actions/runs//artifacts/output
But you need to know the latest run id. We suggest to allow  to be "latest", referring to the last run. This would be very helpful not only in the README.md. We could use the link in any other app as well.
A word on the context: We are mainly building latex papers and having a link to the latest version would be very helpful.
What do you think?
Regards,
Max
Screenshots
No response

Did you mean #31808 ?

Ah ja! Perfect. Thank you! Looking forward for 1.23.


cformat star asterisk should behave differently when given negative sign

In string formatting, a print-f style format specifier can have its amount and precision formatted by variable value through use of star asterik(%*s).
In cformat_bytes and cformat_string, through try_update_quantity_from_tuple, try_update_quantity_from_element is used to update quantity if possible, but it makes the assumption that its behavior should be the same regardless of the sign value of the given element.
if let Some(i) = width_obj.payload::<PyInt>() {
    let i = i.try_to_primitive::<i32>(vm)?.unsigned_abs();
    Ok(CFormatQuantity::Amount(i as usize))
}

However, that assumption is false, as an amount can be preceded by a negative sign, and it should make the resulting string left adjusted, according to format specifier rule.
https://docs.python.org/3/library/stdtypes.html#old-string-formatting
assert('%*s' % (-5, 'abc') == 'abc  ')

This issue makes this test to fail.
I think this issue can be resolved by checking the sign of the element and adding the minus sign accordingly.
I'm working on the fix at the moment.

hah, first time I've heard of the asterisk tbh.

hah, first time I've heard of the asterisk tbh.

Same here lol. I wouldn't have known it if there wasn't a failing test that used it, haha.


Want similar feature like color picker for fonts

Description of the new feature / enhancement
This feature will work like a colour picker.
Scenario when this would be used?
When I hover over what is written then it shows what font style it is
Supporting information
No response

Neat idea but No plans currently


Character map UWP won't open

Nothing.  I simply tried to open the app.  Please let me know why it is doing this.

Class not registered (Exception from HRESULT: 0x80040154)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at CharacterMap.Core.FontFinder.<>c__DisplayClass48_0.<<LoadFontsAsync>b__1>d.MoveNext() + 0xfb
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult() + 0xb
   at CharacterMap.Core.FontFinder.<>c.<<LoadFontsAsync>b__48_0>d.MoveNext() + 0x181
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult() + 0xb
   at CharacterMap.App.<OnLaunched>d__13.MoveNext() + 0x7c
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__7_0(Object) + 0x1e
   at System.Action`1.Invoke(T) + 0x28
   at System.Threading.WinRTSynchronizationContext.Invoker.InvokeCore() + 0x33

OS Version: 10.0.19045.2130
OS Architecture: X64
App Version: 2<IP_ADDRESS>
App Culture: en-US

This should potentially be fixed in the latest build (check the store for updates), but if you're still having issues feel free to reopen this.


Removed check option from dotnet-format as that option disables savin…

…g changed files
See https://github.com/dotnet/format#:~:text=dotnet-format is a code,of preferences will be used.

Changes

Verification

/assign petemounce

@petemounce There doesn't seem to be an OWNERS file in this repo so it didn't mark this PR as approved. Could you manually merge it for us please? Would adding an OWNERS file allow us to pull the "merge" trigger next time once it has the approved label?

@Christopher-Steel this doesn't have prow wired up all the way. @DoomGerbil and I will fix that Monday; apologies.