Use double scalar multiplication optimisations in the ristretto255 group and the ECVRF impl

          > Interesting comparison results, I was originally surprised they are so close because for Ed25519 we've found that the sweet point was at about 40x, but here it's only 4x. I can imagine the results makes sense because in ECVRF we use

map to point (which doesn't exist in ed25519)
operations over non group generators (every H(m) and ChaumPed proofs result to unknown points) (and for ed25519 we applied precomputed tables which improve performance by far)
Ristretto implementations are slightly more expensive than pure ed25519 in Rust.
we don't utilize aG + bP double scalar mul optimizations.

There are a multiple different operations and libraries in play which makes it hard to compare them, so I suggest that we create benchmarks for basic operations (hash-to-curve, arithmetic) for the groups we support to make comparison easier.
We don't utilise double scalar multiplication, but I'll check if it's possible.
Originally posted by @jonas-lj in https://github.com/MystenLabs/fastcrypto/issues/381#issuecomment-1411609755

This seems to speed-up verification with ~35%.


Configurable download_url

Would you be opposed to a pull request moving the downlad_url value to config.exs?
We use this behind a firewall and can only get database updates with tzdata releases.

Hi. I'm not opposed to that :)

You mentioned you only get database updates with tzdata releases so you don't use the download functionality of tzdata? In that case, perhaps it's enough for you to disable the auto updater? https://github.com/lau/tzdata#automatic-data-updates


Provide documentation explaining default module invocation

Only documentation changes and tests so didn't bump version.

:+1:


fix: specify node version for create-remix on cloudflare-pages

Hey folks!
Cloudflare Pages uses Node version 12.18.0 by default and new Remix Pages apps will no longer build without specifying a Node version. I was able to get this template working by adding a .node-version file but @GregBrimble thought it would be a nice thing to add to the template.

Thanks @jkup!


Use a workflow closer to the one used in master

The mingw builds need patches from my previous pull request.

Can you add them?

Did you mean to create a pull request with that same change but for 1.14 branch?

Sorry, I somehow messed it up. I though I was using a copy of the file after your changes. I'll close this one and do another with your changes.

In fact, I did not messed it up :smile: I think I don't know what are the changes you refer to.

The file ccpp.yml in this branch is the same as the file in the master branch, except for the two lines @Vollstrecker said that should be commented.

I said that the CMake changes are required for the mingw CI build.

I think he means 2226adc72079e7a54c59171f9378 but I also think this one is backported.

I might have messed up in the backport, anyone care to check?

It seems I got it, this one was a bit harder as cmake complained about line 19 where the wrong value was used and not set. But if I see this correct, the teststep itself is missing in mingw.

I did not added tests in CI because many tests failed. Three options I had:

disable tests entirely.
enable tests but make CI happy without the failure.
enable tests and CI will be red if any test failed.

I selected the first one. Hence, I commented the pr as "basic build workflow".

k, are you going to fix or at least report the fails? As for now it seems that you're the only one seeing them.

I can try.

From what I recall, it's not clear everytime what lib is missing. Does mingw set an rpath on the binaries? If not, something like the env-settings in the before the tests could be needed there also.

In msys2/mingw environment, the PATH variable looks like this:
$ echo $PATH
/mingw64/bin:/mingw64/bin/site_perl/5.32.1:/mingw64/bin/vendor_perl:/mingw64/bin/core_perl:/usr/local/bin:/usr/bin:/bin:/c/Windows/System32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0/

/mingw64/bin contains all the .exe and .dll files.

Sure, but the test-progs also need libupnp which is not in these paths, On Linux systems the somewhere in the bin is a path noted where the libs have been on linking time, the rpath. With that info it can run without installing the lib previously. On Windows this isn't given, so we had to add the path's of the libs to PATH before the tests.
I hardly guess in mingw it's the same, as you say the static ones run.


Publish to NPM

I've been migrating the PlayCanvas Developer Site to the shiny new @metalsmith-prefixed NPM packages. Great to see these being updated! Is the metadata plugin going to be published to NPM as @metalsmith/metadata soon?

Hi @willeastcott, thanks for checking in. The metadata plugin is still WIP, I'll be out on vacation until second week in March but then it should be soon.
And congrats for migrating the PlayCanvas Developer Site. It is good to see that the community is starting to grow again.


imodel-transformer test-app category filter

add an option to the script (with the same interface as subCategoryFilter) to prune elements of a certain category
add a unit test for the new option

linting and trying to get a rush change going

reverted to draft due to possible bug that could change the PR contents substantially and makes it not worth reviewing

@scsewall are these build errors transient? I restarted the build and got them again. They don't look related


Some species seem to pass through the taxon filter

I still see these when I filter on fungi?

Confirmed with:
http://amigo.geneontology.org/amigo/search/annotation?q=*:*&fq=-taxon_subset_closure_label:"Fungi"&fq=assigned_by:"AspGD"&sfq=document_category:"annotation"
@cmungall Is it possible that the subspecies are somehow missing getting picked up in the closure? Possibly as a result of using a subset?

Okay, something bad is happening here. Please note the following search within AspGD:
http://golr.geneontology.org/select?defType=edismax&qt=standard&indent=on&wt=json&rows=1000&start=0&fl=taxon,taxon_label,taxon_closure,taxon_closure_label,taxon_subset_closure,taxon_subset_closure_label&facet=false&json.nl=arrarr&fq=assigned_by:%22AspGD%22&fq=document_category:%22annotation%22&q=*:*

Okay, so looking through a sample of a thousand annotations (above), most seem to be fine, but there are some NCBITaxon IDs that have none of the closures; for example:
NCBITaxon:41063
NCBITaxon:1137211
NCBITaxon:767769
NCBITaxon:75750
NCBITaxon:1160497
NCBITaxon:1073089

These are all Aspergillus?
@cmungall While I can grasp there might be holes in the subsets, the fact that it's missing the regular closures entirely is rather...worrying.

Any thoughts here @cmungall ?

take one of the gene products and look at the taxon closure, should help us debug

amigo knows about http://amigo.geneontology.org/amigo/term/NCBITaxon:5052
but not the subclasses below
  is_a NCBITaxon:131567 ! cellular organisms
   is_a NCBITaxon:2759 ! Eukaryota
    is_a NCBITaxon:33154 ! Opisthokonta
     is_a NCBITaxon:4751 ! Fungi
      is_a NCBITaxon:451864 ! Dikarya
       is_a NCBITaxon:4890 ! Ascomycota
        is_a NCBITaxon:716545 ! saccharomyceta
         is_a NCBITaxon:147538 ! Pezizomycotina
          is_a NCBITaxon:716546 ! leotiomyceta
           is_a NCBITaxon:147545 ! Eurotiomycetes
            is_a NCBITaxon:451871 ! Eurotiomycetidae
             is_a NCBITaxon:5042 ! Eurotiales
              is_a NCBITaxon:1131492 ! Aspergillaceae
               is_a NCBITaxon:5052 ! Aspergillus ***
                is_a NCBITaxon:5066 ! Aspergillus wentii
                 is_a NCBITaxon:1073089 ! Aspergillus wentii DTO 134E9

this is what we load: https://github.com/geneontology/amigo/blob/master/conf/examples/amigo.yaml.production#L183
historically we have updated taxslim with all taxa in the GAF but it will be easier if we just load everything

This might turn into a problem. The NCBI created taxon IDs for many strains. We had this issue with pombe. At PomBase we want to annotate at the species level not the strain level.
It seems that here sometimes annotations are at the strain level  (Aspergillus wentii DTO 134E9), which will create species duplicates.
I'm not sure  what the solution is but I think UniProt have dealt with this internally now (at least I have a recollection of a discussion that this was resolved, but I can't remember who with...), might be worth using their solution ?
I guess sometimes for  rapidly evolving pathogens it might be important to capture info at the strain level. Maybe a similar solution to  curating splice variants is required so that  the annotations sit on one species object, but the strain id is stored too....

@pgaudet
We just came actoss this. Still unfixed. Causes big problems trying to filter in Amigo (for example on bacteria), you get ~25,000 Aspergillus entries.
Can we just remove until fixed?


New version: DuckDB.cli version 0.9.0

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

Manual Validation ended with:

@wingetbot waivers Add Validation-Executable-Error

Thanks!


Create tickets for focused elements not providing visual feedback

Check each one of these app sections that all focusable elements provide visual feedback so that the user can visually see where they have navigated via focus in the app. Tick checked sections once all appropriate elements provide this feedback in each corresponding section.
Checklist

[ ] Header (Desktop)

#4148 Need to fix and close
#4146 Need to fix and close

[ ] Header (Mobile)
[ ] Footer
[ ] Home
[ ] Sign In
[ ] Reset Password
[ ] Register
[ ] Product

[ ] View Product
[ ] Product List
[ ] Add to cart

[ ] Cart
[ ] Checkout

[ ] Shipping Address

[ ] Choose Shipping Address
[ ] Add New Address

[ ] Delivery Mode
[ ] Payment Details

[ ] Choose Payment Method
[ ] Add New Payment

[ ] Review Order
[ ] Order Confirmation

[ ] My Account

[ ] Order History
[ ] Address Book

[ ] Addresses
[ ] Add New Address
[ ] Edit Address

[ ] Payment Details
[ ] Personal Details
[ ] Change Password
[ ] Email Address
[ ] Consent Management
[ ] Close Account

[ ] Miscellaneous/General

#2216 Need to fix and close
#3777 Need to fix and close
Note: Remove pages coming from cms from this list

All ticket have been created


Add the passing accessibility scores as ratio keys

Hi, I'd like to add AAA: 7.0, AA: 4.5, and "AA+": 3.0 to the ratios object as valid ratioKeys, along with the supporting logic and tests. Having a ratio of 7.0 would be something I'd find helpful.
Please let me know if this is something you'd be willing to accept for this project. thanks

Never mind, I see you're already working on this in the numeric-contrast-ratio branch. I'll be excited to see when this is merged into master!

I will re-open this issue until the PR is merged.


Many improvements to disposals room

Changed the airlock so it had a name and could occlude, added a small light

The diff is so big because all the parents and many of the IDs were updated and some APCs drawed power for some reason and modified their startingCharge by a bit.

Merge conflicts solved


modernise tests + lint

I've swapped some parts and added linting in prep for writing some more tests about blob replication during initial sync.
This PR does not change functionality, it's mainly about linting and replacing use of secret-stack in tests for the tidier scuttle-testbot (same thing but with common convenience methods built in, which means less code to read when setting up tests)

Alas, looks like an intermittent test failure (given 8/9 pass). Recent refactoring might have fixed this, will have to push and see

planning to merge this if these pass


Liberty-assembly packaging type build war file

Currently the liberty-assembly packaging type will install applications into the assembly if you provide it as a compile dependency. If I have files in src/main/java it would be cool if it did the following:

compiled the code
compiled any test code in src/test/java
ran unit tests
ran the maven war plugin to create a war file
installed the war into the assembly

For this I would expect the user to have a project that was structured like this:
src/main
+-java/Application.java
+-test
+-Test.java
+-resources/server.xml
pom.xml
With a pom file like this:
<groupId>sample.test</groupId>
<artifactId>test.plugin</artifactId>
<version>0.0.1-SNAPSHOT</version>
<packaging>liberty-assembly</packaging>

<build>
  <plugins>
    <plugin>
      <groupId>net.wasdev.wlp.maven.plugins</groupId>
      <artifactId>liberty-maven-plugin</artifactId>
      <version>1.3-SNAPSHOT</version>
      <configuration>
      <assemblyArtifact><!--define assembly here--></assemblyArtifact>
      </configuration>
    </plugin>
  </plugins>
</build>

And the result of running mvn install would be:

code compiled
test code compiled
unit test run
war built
liberty installed
server created
war installed into server
server packaged
integration test
install packaged server into local maven repo

Further, I would like an option to keep the war file in the server package expanded in the package (to avoid the immediate following step of auto-extracting the war file when the server is run)

That should probably be the primary option. Also the tools would require a change in Liberty to make that happen since it just uses the packaging tool so you should probably take this up there instead.

maven is what copies the built war file into the target server dir.  I was thinking of an option that would extract the war into the target server dir, rather than copying the war file.

OK, I understand now. I think it could be easily argued this should be the default, rather than an option.

I would be happy for the war file to be extracted rather than copied, since the output I am after is a Liberty server package as I user I don't require it to be a war inside the zip and the extracted war allows for dynamic updates. In fact, what if the work flow from the packaging type was:

code compiled
test code compiled
unit test run
classes copied into server as loose config war
liberty installed
server created
war installed into server
server packaged
integration test
install packaged server into local maven repo

I think your order isn't quite right, wouldn't the loose config war need to be created after the server is created? If we do that order the server package tool would absolutely need to be updated to package as an expanded war rather than a war file, otherwise the maven tools would need to replace the loose war with a non-loose one.p before packaging.

Yes, sorry I just replaced "war built" with "classes copied into server..", it should actually be:

code compiled
test code compiled
unit test run
liberty installed
server created
classes copied into server as loose config war
server packaged
integration test
install packaged server into local maven repo

Does that make more sense?

Yes. Just need to update the maven tools and the server package tool.

The tools-integration branch has been updated for this issue.  When the type is liberty-assembly, the following phases are bound:
pre-clean
liberty:stop-server
process-resources
resources:resources
compile
compiler:compile
process-test-resources
resources:testResources
test-compile
compiler:testCompile
test
surefire:test
prepare-package
liberty:install-server
liberty:create-server
liberty:install-feature
liberty:install-apps
package
liberty:package-server
pre-integration-test
liberty:start-server
integration-test
failsafe:integration-test
post-integration-test
liberty:stop-server
install
install:install
deploy
deploy:deploy
Since a war is not built, the configuration for loose application needs to be added for the application to be installed:
true

This capability is now available in the 2.0-SNAPSHOT.  When you start using this version, you might want to remove bindings from your pom file.


Switch health check port of node local dns to a less often used port.

Switch health check port of node local dns to a less often used port.
Per default, node local dns uses port 8080 for its health check. As node local dns
binds the port on the node level it might conflict with other node wide services
or pods running in the host network. As port 8080 is sometimes used for http like
services it seems to provoke conflicts if node local dns uses this port for health
checks.
This change simply moves the node local dns health check port to a different, less
utilized port.
How to categorize this PR?

/area networking
/kind enhancement
What this PR does / why we need it:
Switch health check port of node local dns to a less often used port.
Per default, node local dns uses port 8080 for its health check. As node local dns
binds the port on the node level it might conflict with other node wide services
or pods running in the host network. As port 8080 is sometimes used for http like
services it seems to provoke conflicts if node local dns uses this port for health
checks.
This change simply moves the node local dns health check port to a different, less
utilized port.
Which issue(s) this PR fixes:
None.
Special notes for your reviewer:
Release note:

Node-local-dns health check does not longer use port 8080 of the host, but uses port 8099 instead.

/invite @dguendisch


Makes SNS topics indempodent

Closes #1323

Once Travis is happy, it should be good. Great first PR :+1:

Coverage increased (+0.0007%) to 92.155% when pulling 1ed101dc0c131027e396930bf0449119153e5849 on adamgilman:master into 3740db80598fd4fb96a681bae0232f2c6afdda63 on spulec:master.

Great work :smile:, welcome to moto

fyi @JackDanger, I've tagged some stuff with unreleased, so if you search for that when rolling a new release it should make life easier (https://github.com/spulec/moto/pulls?q=is%3Apr+is%3Aclosed+label%3Aunreleased), obvs you'll have to pop onto the issue and untag but you normally comment with release message anyway.


Proposal: Vendor whatwg-fetch

Pretender uses the whatwg-fetch package in order to intercept fetch calls.
Even though whatwg-fetch is explicitly imported here (and used here), Pretender is actually relying implicitly on whatwg-fetch's internals to get the fetch intercepting behavior working correctly.
The reason is because the fetch implementation that whatwg-fetch provides actually delegates to window.XMLHTTPRequest under the hood. Since Pretender also monkey patches window.XMLHTTPRequest, it is able to intercept fetch calls equally as well. But it's only due to those internals – due to the fact that the whatwg-fetch polyfill happens to use XMLHTTPRequest under the hood. This is not part of whatwg-fetch's public API, even though it is unlikely the change.
The reason this bit us recently is because some folks are trying to use Mirage with Next.js. Next performs some build-time optimizations to ensure apps don't include multiple or heavy versions of popular polyfills, whatwg-fetch being one of them. So, they actually swap out the package that whatwg-fetch resolves to, meaning when Pretender tries to import * from 'whatwg-fetch', it ends up with a different polyfill entirely, and one that does not happen to use XMLHTTPRequest under the hood. Therefore, Pretender (and thus Mirage) don't work.
We asked about how to opt-out of this optimizing behavior here, but as of right now the Zeit team doesn't have any plans to make the behavior configurable.
In any case, regardless of whether Next.js chooses to expose such an option, it is still true that today, Pretender is relying on internals of whatwg-fetch, and that poses a risk to Pretender in the event those internals ever change.
I'm proposing that we vendor the latest version of whatwg-fetch into Pretender directly, since we are relying on observable but undocumented behavior of its current implementation. This would give us total control over the code, and would also address the Next.js issue since whatwg-fetch would no longer be an external dependency that could be hoisted or replaced.

It's likely ok to bundle whatwg-fetch as part of a dev time build step and presenting them as one bundle to consumers.
But I am not super enthusiastic about actually copying whatwg-fetch code & tests into this repo. It seems like keeping it simple to upgrade if we want to is important, and having the code copied seems like a hazard.
I can be convinced, these are only my first thoughts.

Ya. I think we would just copy this file: https://github.com/github/fetch/blob/master/fetch.js. So 500 lines of code. The last release of whatwg-fetch was 1 year ago.
If there were updates to whatwg-fetch, it's true we wouldn't know about them (at least right away). But again we should compare that to the current situation, in which we're relying on internals, which means whatwg-fetch could push out a patch version that refactors away from their reliance on XMLHTTPRequest and that would break Pretender. Is that likely to happen? Not sure. There are other newer polyfills of fetch that don't use XMLHTTPRequest, so maybe. In any case I do think it's strange for us to be relying on the internals of an external dependency.
I don't think we'd need whatwg-fetch's tests, I think our tests cover Pretender's public API and that's sufficient.
An alternative would be to update Pretender's code to "properly" support intercepting fetch, i.e. actually proxy the fetch APIs to Pretender's. But that would effectively involve bringing in a fetch implementation, and pointing it to our APIs, which effectively would boil down to something that looks a lot like bringing in whatwg-fetch and using it as the boundary layer to redirect fetch APIs to our own.
So ultimately I think vendoring whatwg-fetch is a lot like adding a "proper" fetch adapter to Pretender.

I haven't digged into how next.js resolves import * from 'whatwg-fetch', I would +1 to Stef's suggestion to do this at build time and make sure the scoped xhr is used.
Not sure about proxying fetch. It seems like building another polyfill, which whatwg-fetch already did the work.

Ohh I see – I don't think I fully understood.
Are you all saying we could keep whatwg-fetch as a dependency here in package.json, but for Pretender's publishing step, go ahead and pull it in + make it into an internal dependency? So there's no chance of it being overridden, hoisted or something else?

Another point @ryanto raised is that, currently Pretender is not importable in node, due to whatwg-fetch assuming a browser-like environment. This is another headache for us because even though Mirage doesn't yet work in Node, it needs to be importable so it doesn't break setups like Gatsby that expect isomorphic app code.
This led us needing to create some polyfills and use them like this: https://github.com/miragejs/miragejs/blob/23fb9fe3278af513e1a95c8a09c669e4a47fcd45/lib/server.js#L3. This ensure our polyfill code runs before Pretender is imported (and thus before whatwg-fetch is imported). The code essentially just ensures self is defined, which is all whatwg-fetch needs to be importable (again, not functional, which is not what we're interested at this time).
So, if we were to copy the 500-line whatwg-fetch file directly into Pretender, we could also solve this issue and make sure Pretender doesn't break node apps if it's in the import path, by simply wrapping the code in an if global.self === 'undefined') block.
I understand the purist argument about leaving whatwg-fetch in package.json, but Pretender's build file + logic is already pretty messy + hard to read/maintain, and whatwg-fetch's last release was over a year ago, so I think pragmatically the simplest way to solve this problem today is to just create a new file in Pretender, copy the 500 lines, make a comment at the top of the file and be done with it. And I also think the risk is very low.
Just some more of my thoughts!

@samselikoff I don't have strong feelings either way, but am happy to support your calls here. They seem perfectly reasonable.

Right, thanks man. If we do pull the trigger on this, it will be quite easy to undo if it causes any issues.
Thanks a lot Stef!

Really appreciate the effort here guys! 🙌

Any trick to getting Pretender's test suite running locally? I started work on this but master is failing on my machine for a bunch of reasons...

yarn test
➜  pretender git:(vendor-whatwg-fetch) ✗ yarn test
yarn run v1.21.1
$ bower install
$ npm run lint && npm run eslint && npm run tests-only
npm WARN lifecycle The node binary used for scripts is /var/folders/v5/5bs4trnx5v7bly3f0cg4_sc40000gn/T/yarn--15824094412
85-0.3022276787043625/node but npm is using /Users/samselikoff/.nodenv/versions/12.16.0/bin/node itself. Use the `--scrip
ts-prepend-node-path` option to include the path for the node binary npm was executed with.

><EMAIL_ADDRESS>lint /Users/samselikoff/Projects/oss/pretender
> jshint test

npm WARN lifecycle The node binary used for scripts is /var/folders/v5/5bs4trnx5v7bly3f0cg4_sc40000gn/T/yarn--15824094412
85-0.3022276787043625/node but npm is using /Users/samselikoff/.nodenv/versions/12.16.0/bin/node itself. Use the `--scrip
ts-prepend-node-path` option to include the path for the node binary npm was executed with.

><EMAIL_ADDRESS>eslint /Users/samselikoff/Projects/oss/pretender
> eslint src/**/*.ts test

npm WARN lifecycle The node binary used for scripts is /var/folders/v5/5bs4trnx5v7bly3f0cg4_sc40000gn/T/yarn--15824094412
85-0.3022276787043625/node but npm is using /Users/samselikoff/.nodenv/versions/12.16.0/bin/node itself. Use the `--scrip
ts-prepend-node-path` option to include the path for the node binary npm was executed with.

><EMAIL_ADDRESS>tests-only /Users/samselikoff/Projects/oss/pretender
> karma start --single-run

22 02 2020 17:10:44.445:INFO [karma]: Karma v1.7.1 server started at http://<IP_ADDRESS>:9876/
22 02 2020 17:10:44.447:INFO [launcher]: Launching browsers Chrome, PhantomJS with unlimited concurrency
22 02 2020 17:10:44.451:INFO [launcher]: Starting browser Chrome
22 02 2020 17:10:44.457:INFO [launcher]: Starting browser PhantomJS
22 02 2020 17:10:45.453:INFO [Chrome 80.0.3987 (Mac OS X 10.15.3)]: Connected on socket VCT2Nx9PjwzfYoIfAAAA with id 2170
2188
22 02 2020 17:10:45.557:INFO [PhantomJS 2.1.1 (Mac OS X 0.0.0)]: Connected on socket oRy3yOMfjOk2sBphAAAB with id 2755994
5
..........................................
Chrome 80.0.3987 (Mac OS X 10.15.3) pretender invoking async requests with `onprogress` upload events in the upload  trig
ger a progress event each 50ms FAILED
        ProgressEvent has total of requestBody byte size
        Expected: 9
        Actual: 300
            at EventedObject.xhr.upload.onprogress (test/calling_test.js:423:16)
            at EventedObject.<anonymous> (node_modules/fake-xml-http-request/fake_xml_http_request.js:137:18)
            at EventedObject.dispatchEvent (node_modules/fake-xml-http-request/fake_xml_http_request.js:181:24)
            at EventedObject._progress (node_modules/fake-xml-http-request/fake_xml_http_request.js:199:12)
            at dist/pretender.js:9:16177

        ProgressEvent has total of requestBody byte size
        Expected: 9
        Actual: 300
            at EventedObject.xhr.upload.onprogress (test/calling_test.js:423:16)
            at EventedObject.<anonymous> (node_modules/fake-xml-http-request/fake_xml_http_request.js:137:18)
            at EventedObject.dispatchEvent (node_modules/fake-xml-http-request/fake_xml_http_request.js:181:24)
            at EventedObject._progress (node_modules/fake-xml-http-request/fake_xml_http_request.js:199:12)
            at dist/pretender.js:9:16177

        ProgressEvent has total of requestBody byte size
        Expected: 9
        Actual: 300
            at EventedObject.xhr.upload.onprogress (test/calling_test.js:423:16)
            at EventedObject.<anonymous> (node_modules/fake-xml-http-request/fake_xml_http_request.js:137:18)
            at EventedObject.dispatchEvent (node_modules/fake-xml-http-request/fake_xml_http_request.js:181:24)
            at EventedObject._progress (node_modules/fake-xml-http-request/fake_xml_http_request.js:199:12)
            at dist/pretender.js:9:16177

        ProgressEvent has total of requestBody byte size
        Expected: 9
        Actual: 300
            at EventedObject.xhr.upload.onprogress (test/calling_test.js:423:16)
            at EventedObject.<anonymous> (node_modules/fake-xml-http-request/fake_xml_http_request.js:137:18)
            at EventedObject.dispatchEvent (node_modules/fake-xml-http-request/fake_xml_http_request.js:181:24)
            at EventedObject._progress (node_modules/fake-xml-http-request/fake_xml_http_request.js:199:12)
            at dist/pretender.js:9:16177

        ProgressEvent has total of requestBody byte size
        Expected: 9
        Actual: 300
            at EventedObject.xhr.upload.onprogress (test/calling_test.js:423:16)
            at EventedObject.<anonymous> (node_modules/fake-xml-http-request/fake_xml_http_request.js:137:18)
            at EventedObject.dispatchEvent (node_modules/fake-xml-http-request/fake_xml_http_request.js:181:24)
            at EventedObject._progress (node_modules/fake-xml-http-request/fake_xml_http_request.js:199:12)
            at dist/pretender.js:9:16177

Chrome 80.0.3987 (Mac OS X 10.15.3) pretender invoking `onprogress` upload events don't keep firing once the request has
ended FAILED
        ProgressEvent has total of requestBody byte size
        Expected: 9
        Actual: 210
            at EventedObject.xhr.upload.onprogress (test/calling_test.js:460:14)
            at EventedObject.<anonymous> (node_modules/fake-xml-http-request/fake_xml_http_request.js:137:18)
            at EventedObject.dispatchEvent (node_modules/fake-xml-http-request/fake_xml_http_request.js:181:24)
            at EventedObject._progress (node_modules/fake-xml-http-request/fake_xml_http_request.js:199:12)
            at dist/pretender.js:9:16177
            at callTimer (node_modules/sinon/pkg/sinon.js:7096:20)

        ProgressEvent has total of requestBody byte size
        Expected: 9
        Actual: 210
            at EventedObject.xhr.upload.onprogress (test/calling_test.js:460:14)
            at EventedObject.<anonymous> (node_modules/fake-xml-http-request/fake_xml_http_request.js:137:18)
            at EventedObject.dispatchEvent (node_modules/fake-xml-http-request/fake_xml_http_request.js:181:24)
            at EventedObject._progress (node_modules/fake-xml-http-request/fake_xml_http_request.js:199:12)
            at dist/pretender.js:9:16177
            at callTimer (node_modules/sinon/pkg/sinon.js:7096:20)

        ProgressEvent has total of requestBody byte size
        Expected: 9
        Actual: 210
            at EventedObject.xhr.upload.onprogress (test/calling_test.js:460:14)
            at EventedObject.<anonymous> (node_modules/fake-xml-http-request/fake_xml_http_request.js:137:18)
            at EventedObject.dispatchEvent (node_modules/fake-xml-http-request/fake_xml_http_request.js:181:24)
            at EventedObject._progress (node_modules/fake-xml-http-request/fake_xml_http_request.js:199:12)
            at dist/pretender.js:9:16177
            at callTimer (node_modules/sinon/pkg/sinon.js:7096:20)

        ProgressEvent has total of requestBody byte size
        Expected: 9
        Actual: 210
            at EventedObject.xhr.upload.onprogress (test/calling_test.js:460:14)
            at EventedObject.<anonymous> (node_modules/fake-xml-http-request/fake_xml_http_request.js:137:18)
            at EventedObject.dispatchEvent (node_modules/fake-xml-http-request/fake_xml_http_request.js:181:24)
            at EventedObject._progress (node_modules/fake-xml-http-request/fake_xml_http_request.js:199:12)
            at dist/pretender.js:9:16177
            at callTimer (node_modules/sinon/pkg/sinon.js:7096:20)

Chrome 80.0.3987 (Mac OS X 10.15.3) pretender invoking no progress upload events are fired after the request is aborted FAILED
        ProgressEvent has total of requestBody byte size
        Expected: 8
        Actual: 210
            at EventedObject.xhr.upload.onprogress (test/calling_test.js:495:14)
            at EventedObject.<anonymous> (node_modules/fake-xml-http-request/fake_xml_http_request.js:137:18)
            at EventedObject.dispatchEvent (node_modules/fake-xml-http-request/fake_xml_http_request.js:181:24)
            at EventedObject._progress (node_modules/fake-xml-http-request/fake_xml_http_request.js:199:12)
            at dist/pretender.js:9:16177
            at callTimer (node_modules/sinon/pkg/sinon.js:7096:20)

PhantomJS 2.1.1 (Mac OS X 0.0.0) pretender invoking async requests with `onprogress` upload events in the upload  trigger a progress event each 50ms FAILED
        ProgressEvent has total of requestBody byte size
        Expected: 9
        Actual: 300
        onprogress@test/calling_test.js:423:21
        node_modules/fake-xml-http-request/fake_xml_http_request.js:137:22
        dispatchEvent@node_modules/fake-xml-http-request/fake_xml_http_request.js:181:28
        _progress@node_modules/fake-xml-http-request/fake_xml_http_request.js:199:25
        dist/pretender.js:9:18046

        ProgressEvent has total of requestBody byte size
        Expected: 9
        Actual: 300
        onprogress@test/calling_test.js:423:21
        node_modules/fake-xml-http-request/fake_xml_http_request.js:137:22
        dispatchEvent@node_modules/fake-xml-http-request/fake_xml_http_request.js:181:28
        _progress@node_modules/fake-xml-http-request/fake_xml_http_request.js:199:25
        dist/pretender.js:9:18046

        ProgressEvent has total of requestBody byte size
        Expected: 9
        Actual: 300
        onprogress@test/calling_test.js:423:21
        node_modules/fake-xml-http-request/fake_xml_http_request.js:137:22
        dispatchEvent@node_modules/fake-xml-http-request/fake_xml_http_request.js:181:28
        _progress@node_modules/fake-xml-http-request/fake_xml_http_request.js:199:25
        dist/pretender.js:9:18046

        ProgressEvent has total of requestBody byte size
        Expected: 9
        Actual: 300
        onprogress@test/calling_test.js:423:21
        node_modules/fake-xml-http-request/fake_xml_http_request.js:137:22
        dispatchEvent@node_modules/fake-xml-http-request/fake_xml_http_request.js:181:28
        _progress@node_modules/fake-xml-http-request/fake_xml_http_request.js:199:25
        dist/pretender.js:9:18046

        ProgressEvent has total of requestBody byte size
        Expected: 9
        Actual: 300
        onprogress@test/calling_test.js:423:21
        node_modules/fake-xml-http-request/fake_xml_http_request.js:137:22
        dispatchEvent@node_modules/fake-xml-http-request/fake_xml_http_request.js:181:28
        _progress@node_modules/fake-xml-http-request/fake_xml_http_request.js:199:25
        dist/pretender.js:9:18046

PhantomJS 2.1.1 (Mac OS X 0.0.0) pretender invoking `onprogress` upload events don't keep firing once the request has ended FAILED
        ProgressEvent has total of requestBody byte size
        Expected: 9
        Actual: 210
        onprogress@test/calling_test.js:460:19
        node_modules/fake-xml-http-request/fake_xml_http_request.js:137:22
        dispatchEvent@node_modules/fake-xml-http-request/fake_xml_http_request.js:181:28
        _progress@node_modules/fake-xml-http-request/fake_xml_http_request.js:199:25
        dist/pretender.js:9:18046
        callTimer@node_modules/sinon/pkg/sinon.js:7096:25
        tick@node_modules/sinon/pkg/sinon.js:7319:30
        test/calling_test.js:466:15
        runTest@node_modules/qunit/qunit/qunit.js:3041:34
        run@node_modules/qunit/qunit/qunit.js:3027:13
        node_modules/qunit/qunit/qunit.js:3258:15
        processTaskQueue@node_modules/qunit/qunit/qunit.js:2614:28
        node_modules/qunit/qunit/qunit.js:2618:24
        invokeCallback@node_modules/qunit/qunit/qunit.js:1699:25
        node_modules/qunit/qunit/qunit.js:1467:30
        flush@node_modules/qunit/qunit/qunit.js:1419:15

        ProgressEvent has total of requestBody byte size
        Expected: 9
        Actual: 210
        onprogress@test/calling_test.js:460:19
        node_modules/fake-xml-http-request/fake_xml_http_request.js:137:22
        dispatchEvent@node_modules/fake-xml-http-request/fake_xml_http_request.js:181:28
        _progress@node_modules/fake-xml-http-request/fake_xml_http_request.js:199:25
        dist/pretender.js:9:18046
        callTimer@node_modules/sinon/pkg/sinon.js:7096:25
        tick@node_modules/sinon/pkg/sinon.js:7319:30
        test/calling_test.js:466:15
        runTest@node_modules/qunit/qunit/qunit.js:3041:34
        run@node_modules/qunit/qunit/qunit.js:3027:13
        node_modules/qunit/qunit/qunit.js:3258:15
        processTaskQueue@node_modules/qunit/qunit/qunit.js:2614:28
        node_modules/qunit/qunit/qunit.js:2618:24
        invokeCallback@node_modules/qunit/qunit/qunit.js:1699:25
        node_modules/qunit/qunit/qunit.js:1467:30
        flush@node_modules/qunit/qunit/qunit.js:1419:15

        ProgressEvent has total of requestBody byte size
        Expected: 9
        Actual: 210
        onprogress@test/calling_test.js:460:19
        node_modules/fake-xml-http-request/fake_xml_http_request.js:137:22
        dispatchEvent@node_modules/fake-xml-http-request/fake_xml_http_request.js:181:28
        _progress@node_modules/fake-xml-http-request/fake_xml_http_request.js:199:25
        dist/pretender.js:9:18046
        callTimer@node_modules/sinon/pkg/sinon.js:7096:25
        tick@node_modules/sinon/pkg/sinon.js:7319:30
        test/calling_test.js:466:15
        runTest@node_modules/qunit/qunit/qunit.js:3041:34
        run@node_modules/qunit/qunit/qunit.js:3027:13
        node_modules/qunit/qunit/qunit.js:3258:15
        processTaskQueue@node_modules/qunit/qunit/qunit.js:2614:28
        node_modules/qunit/qunit/qunit.js:2618:24
        invokeCallback@node_modules/qunit/qunit/qunit.js:1699:25
        node_modules/qunit/qunit/qunit.js:1467:30
        flush@node_modules/qunit/qunit/qunit.js:1419:15

        ProgressEvent has total of requestBody byte size
        Expected: 9
        Actual: 210
        onprogress@test/calling_test.js:460:19
        node_modules/fake-xml-http-request/fake_xml_http_request.js:137:22
        dispatchEvent@node_modules/fake-xml-http-request/fake_xml_http_request.js:181:28
        _progress@node_modules/fake-xml-http-request/fake_xml_http_request.js:199:25
        dist/pretender.js:9:18046
        callTimer@node_modules/sinon/pkg/sinon.js:7096:25
        tick@node_modules/sinon/pkg/sinon.js:7319:30
        test/calling_test.js:466:15
        runTest@node_modules/qunit/qunit/qunit.js:3041:34
        run@node_modules/qunit/qunit/qunit.js:3027:13
        node_modules/qunit/qunit/qunit.js:3258:15
        processTaskQueue@node_modules/qunit/qunit/qunit.js:2614:28
        node_modules/qunit/qunit/qunit.js:2618:24
        invokeCallback@node_modules/qunit/qunit/qunit.js:1699:25
        node_modules/qunit/qunit/qunit.js:1467:30
        flush@node_modules/qunit/qunit/qunit.js:1419:15

PhantomJS 2.1.1 (Mac OS X 0.0.0) pretender invoking no progress upload events are fired after the request is aborted FAILED
        ProgressEvent has total of requestBody byte size
        Expected: 8
        Actual: 210
        onprogress@test/calling_test.js:495:19
        node_modules/fake-xml-http-request/fake_xml_http_request.js:137:22
        dispatchEvent@node_modules/fake-xml-http-request/fake_xml_http_request.js:181:28
        _progress@node_modules/fake-xml-http-request/fake_xml_http_request.js:199:25
        dist/pretender.js:9:18046
        callTimer@node_modules/sinon/pkg/sinon.js:7096:25
        tick@node_modules/sinon/pkg/sinon.js:7319:30
        test/calling_test.js:502:15
        runTest@node_modules/qunit/qunit/qunit.js:3041:34
        run@node_modules/qunit/qunit/qunit.js:3027:13
        node_modules/qunit/qunit/qunit.js:3258:15
        processTaskQueue@node_modules/qunit/qunit/qunit.js:2614:28
        node_modules/qunit/qunit/qunit.js:2618:24
        invokeCallback@node_modules/qunit/qunit/qunit.js:1699:25
        node_modules/qunit/qunit/qunit.js:1467:30
        flush@node_modules/qunit/qunit/qunit.js:1419:15

Chrome 80.0.3987 (Mac OS X 10.15.3) pretender invoking async requests with `onprogress` events trigger a progress event each 50ms FAILED
        GET request has no requestBody
        Expected: 0
        Actual: 300
            at FakeRequest.xhr.onprogress (test/calling_test.js:528:14)
            at FakeRequest.<anonymous> (node_modules/fake-xml-http-request/fake_xml_http_request.js:137:18)
            at FakeRequest.dispatchEvent (node_modules/fake-xml-http-request/fake_xml_http_request.js:181:24)
            at FakeRequest._progress (node_modules/fake-xml-http-request/fake_xml_http_request.js:199:12)
            at dist/pretender.js:9:16264

        Expected: 300
        Actual: 51
            at FakeRequest.xhr.onprogress (test/calling_test.js:529:14)
            at FakeRequest.<anonymous> (node_modules/fake-xml-http-request/fake_xml_http_request.js:137:18)
            at FakeRequest.dispatchEvent (node_modules/fake-xml-http-request/fake_xml_http_request.js:181:24)
            at FakeRequest._progress (node_modules/fake-xml-http-request/fake_xml_http_request.js:199:12)
            at dist/pretender.js:9:16264

        GET request has no requestBody
        Expected: 0
        Actual: 300
            at FakeRequest.xhr.onprogress (test/calling_test.js:528:14)
            at FakeRequest.<anonymous> (node_modules/fake-xml-http-request/fake_xml_http_request.js:137:18)
            at FakeRequest.dispatchEvent (node_modules/fake-xml-http-request/fake_xml_http_request.js:181:24)
            at FakeRequest._progress (node_modules/fake-xml-http-request/fake_xml_http_request.js:199:12)
            at dist/pretender.js:9:16264

        Expected: 300
        Actual: 103
            at FakeRequest.xhr.onprogress (test/calling_test.js:529:14)
            at FakeRequest.<anonymous> (node_modules/fake-xml-http-request/fake_xml_http_request.js:137:18)
            at FakeRequest.dispatchEvent (node_modules/fake-xml-http-request/fake_xml_http_request.js:181:24)
            at FakeRequest._progress (node_modules/fake-xml-http-request/fake_xml_http_request.js:199:12)
            at dist/pretender.js:9:16264

        GET request has no requestBody
        Expected: 0
        Actual: 300
            at FakeRequest.xhr.onprogress (test/calling_test.js:528:14)
            at FakeRequest.<anonymous> (node_modules/fake-xml-http-request/fake_xml_http_request.js:137:18)
            at FakeRequest.dispatchEvent (node_modules/fake-xml-http-request/fake_xml_http_request.js:181:24)
            at FakeRequest._progress (node_modules/fake-xml-http-request/fake_xml_http_request.js:199:12)
            at dist/pretender.js:9:16264

        Expected: 300
        Actual: 157
            at FakeRequest.xhr.onprogress (test/calling_test.js:529:14)
            at FakeRequest.<anonymous> (node_modules/fake-xml-http-request/fake_xml_http_request.js:137:18)
            at FakeRequest.dispatchEvent (node_modules/fake-xml-http-request/fake_xml_http_request.js:181:24)
            at FakeRequest._progress (node_modules/fake-xml-http-request/fake_xml_http_request.js:199:12)
            at dist/pretender.js:9:16264

        GET request has no requestBody
        Expected: 0
        Actual: 300
            at FakeRequest.xhr.onprogress (test/calling_test.js:528:14)
            at FakeRequest.<anonymous> (node_modules/fake-xml-http-request/fake_xml_http_request.js:137:18)
            at FakeRequest.dispatchEvent (node_modules/fake-xml-http-request/fake_xml_http_request.js:181:24)
            at FakeRequest._progress (node_modules/fake-xml-http-request/fake_xml_http_request.js:199:12)
            at dist/pretender.js:9:16264

        Expected: 300
        Actual: 209
            at FakeRequest.xhr.onprogress (test/calling_test.js:529:14)
            at FakeRequest.<anonymous> (node_modules/fake-xml-http-request/fake_xml_http_request.js:137:18)
            at FakeRequest.dispatchEvent (node_modules/fake-xml-http-request/fake_xml_http_request.js:181:24)
            at FakeRequest._progress (node_modules/fake-xml-http-request/fake_xml_http_request.js:199:12)
            at dist/pretender.js:9:16264

        GET request has no requestBody
        Expected: 0
        Actual: 300
            at FakeRequest.xhr.onprogress (test/calling_test.js:528:14)
            at FakeRequest.<anonymous> (node_modules/fake-xml-http-request/fake_xml_http_request.js:137:18)
            at FakeRequest.dispatchEvent (node_modules/fake-xml-http-request/fake_xml_http_request.js:181:24)
            at FakeRequest._progress (node_modules/fake-xml-http-request/fake_xml_http_request.js:199:12)
            at dist/pretender.js:9:16264

        Expected: 300
        Actual: 260
            at FakeRequest.xhr.onprogress (test/calling_test.js:529:14)
            at FakeRequest.<anonymous> (node_modules/fake-xml-http-request/fake_xml_http_request.js:137:18)
            at FakeRequest.dispatchEvent (node_modules/fake-xml-http-request/fake_xml_http_request.js:181:24)
            at FakeRequest._progress (node_modules/fake-xml-http-request/fake_xml_http_request.js:199:12)
            at dist/pretender.js:9:16264

.............22 02 2020 17:10:46.565:WARN [web-server]: 404: /some/path
.

Chrome 80.0.3987 (Mac OS X 10.15.3) passthrough requests asynchronous request with pass-through and empty response FAILED
        response for real and fake xhr are both blank strings
        Expected: ""
        Actual: null
            at FakeRequest._onload (test/passthrough_test.js:332:14)
            at FakeRequest.dispatchEvent (node_modules/fake-xml-http-request/fake_xml_http_request.js:181:24)
            at dispatchEvent (dist/pretender.js:9:11588)
            at testXHR.xhr.<computed> [as onload] (dist/pretender.js:9:12162)
            at Object.apply (test/passthrough_test.js:316:15)
            at FakeRequest.send (dist/pretender.js:9:9275)

Chrome 80.0.3987 (Mac OS X 10.15.3) passthrough requests > the `.passthrough()` property allows a passthrough on an unhandledRequest FAILED
        Expected: 404
        Actual: 0
            at Object.error (test/passthrough_test.js:354:18)
            at j (bower_components/jquery-1/index.js:2:27309)
            at Object.fireWith [as rejectWith] (bower_components/jquery-1/index.js:2:28122)
            at x (bower_components/jquery-1/index.js:5:22136)
            at Function.ajax (bower_components/jquery-1/index.js:5:21607)
            at Object.<anonymous> (test/passthrough_test.js:351:9)

.
Chrome 80.0.3987 (Mac OS X 10.15.3) passthrough requests > the `.passthrough()` property returns a native xhr FAILED
        Died on test #1     at Object.<anonymous> (test/passthrough_test.js:360:5)
            at processModule (node_modules/qunit/qunit/qunit.js:1191:16)
            at module$1 (node_modules/qunit/qunit/qunit.js:1216:4)
            at Object.<anonymous> (test/passthrough_test.js:343:3)
            at processModule (node_modules/qunit/qunit/qunit.js:1191:16)
            at module$1 (node_modules/qunit/qunit/qunit.js:1216:4)
            at test/passthrough_test.js:5:1: request.passthrough is not a function
        TypeError: request.passthrough is not a function
            at Pretender.pretender.unhandledRequest (test/passthrough_test.js:385:37)
            at Pretender.handleRequest (dist/pretender.js:9:21831)
            at FakeRequest.send (dist/pretender.js:9:9397)
            at Object.<anonymous> (test/passthrough_test.js:390:11)
            at runTest (node_modules/qunit/qunit/qunit.js:3041:30)
            at Test.run (node_modules/qunit/qunit/qunit.js:3027:6)
            at node_modules/qunit/qunit/qunit.js:3258:12
            at processTaskQueue (node_modules/qunit/qunit/qunit.js:2614:24)
            at node_modules/qunit/qunit/qunit.js:2618:8

22 02 2020 17:10:46.629:WARN [web-server]: 404: /some/path
.22 02 2020 17:10:46.644:WARN [web-server]: 404: /some/path
.................
Chrome 80.0.3987 (Mac OS X 10.15.3): Executed 78 of 78 (7 FAILED) (0.962 secs / 0.921 secs)
.............22 02 2020 17:10:46.671:WARN [web-server]: 404: /some/path
.22 02 2020 17:10:46.685:WARN [web-server]: 404: /some/path
....22 02 2020 17:10:46.701:WARN [web-server]: 404: /some/otherpath
.22 02 2020 17:10:46.708:WARN [web-server]: 404: /some/otherpath
.
PhantomJS 2.1.1 (Mac OS X 0.0.0) passthrough requests asynchronous request with pass-through and empty response FAILED
        response for real and fake xhr are both blank strings
        Expected: ""
        Actual: null
        _onload@test/passthrough_test.js:332:19
        dispatchEvent@node_modules/fake-xml-http-request/fake_xml_http_request.js:181:28
        dispatchEvent@dist/pretender.js:9:30958
        dist/pretender.js:9:31532
        apply@test/passthrough_test.js:316:21
        send@dist/pretender.js:9:19183
        test/passthrough_test.js:340:13
        runTest@node_modules/qunit/qunit/qunit.js:3041:34
        run@node_modules/qunit/qunit/qunit.js:3027:13
        node_modules/qunit/qunit/qunit.js:3258:15
        processTaskQueue@node_modules/qunit/qunit/qunit.js:2614:28
        node_modules/qunit/qunit/qunit.js:2618:24
        invokeCallback@node_modules/qunit/qunit/qunit.js:1699:25
        node_modules/qunit/qunit/qunit.js:1467:30
        flush@node_modules/qunit/qunit/qunit.js:1419:15

PhantomJS 2.1.1 (Mac OS X 0.0.0) passthrough requests > the `.passthrough()` property allows a passthrough on an unhandledRequest FAILED
        Expected: 404
        Actual: 0
        error@test/passthrough_test.js:354:23
        j@bower_components/jquery-1/index.js:2:27578
        fireWith@bower_components/jquery-1/index.js:2:55529
        x@bower_components/jquery-1/index.js:5:41346
        ajax@bower_components/jquery-1/index.js:5:21608
        test/passthrough_test.js:351:13
        runTest@node_modules/qunit/qunit/qunit.js:3041:34
        run@node_modules/qunit/qunit/qunit.js:3027:13
        node_modules/qunit/qunit/qunit.js:3258:15
        processTaskQueue@node_modules/qunit/qunit/qunit.js:2614:28
        node_modules/qunit/qunit/qunit.js:2618:24
        invokeCallback@node_modules/qunit/qunit/qunit.js:1699:25
        node_modules/qunit/qunit/qunit.js:1467:30
        flush@node_modules/qunit/qunit/qunit.js:1419:15

22 02 2020 17:10:46.738:WARN [web-server]: 404: /some/path
PhantomJS 2.1.1 (Mac OS X 0.0.0) passthrough requests > the `.passthrough()` property returns a native xhr FAILED
        Died on test #1 undefined: undefined is not a constructor (evaluating 'request.passthrough()')
        unhandledRequest@test/passthrough_test.js:385:48
        handleRequest@dist/pretender.js:9:23707
        send@dist/pretender.js:9:19313
        test/passthrough_test.js:390:15
        runTest@node_modules/qunit/qunit/qunit.js:3041:34
        run@node_modules/qunit/qunit/qunit.js:3027:13
        node_modules/qunit/qunit/qunit.js:3258:15
        processTaskQueue@node_modules/qunit/qunit/qunit.js:2614:28
        node_modules/qunit/qunit/qunit.js:2618:24
        invokeCallback@node_modules/qunit/qunit/qunit.js:1699:25
        node_modules/qunit/qunit/qunit.js:1467:30
        flush@node_modules/qunit/qunit/qunit.js:1419:15

.................
PhantomJS 2.1.1 (Mac OS X 0.0.0): Executed 78 of 78 (7 FAILED) (0.982 secs / 0.962 secs)
TOTAL: 14 FAILED, 142 SUCCESS
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>tests-only: `karma start --single-run`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>tests-only script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/samselikoff/.npm/_logs/2020-02-22T22_10_46_916Z-debug.log
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

test does run successfully after running test-ci once, seems like the pretest task is missing in the test command, does that help?

@GriffinSauce not sure but thanks for the suggestion, after Thomas' latest commit I have it working + can now get to work on this!

Closed by https://github.com/pretenderjs/pretender/pull/296


Add your own contact info and links to SupportButton

Hey, I just made a Pull Request!

You can pass your own links and contact info to SupportButton, using a SupportItem array
:heavy_check_mark: Checklist

[X] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[X] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)

Tugboat has finished building the preview for this pull request!
Link:

https://pr4847-wkai6ieb4tuuttw6guohqrlol8tptnyz.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6042b2c6fcb22df3256a1718

Tugboat has finished building the preview for this pull request!
Link:

https://pr4847-wkai6ieb4tuuttw6guohqrlol8tptnyz.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6042b2c6fcb22df3256a1718

Tugboat has finished building the preview for this pull request!
Link:

https://pr4847-wkai6ieb4tuuttw6guohqrlol8tptnyz.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6042b2c6fcb22df3256a1718

@backstage/maintainers - I think this is ready for review.

Allow me to be a bit of a pain in the behind. Just spitballing a bit here. Sorry to come in so late with this, but I felt I had to think out loud just to settle my own thinking :)
So we have a bunch of possible sources of info that could go into the button.

The plugin maker themselves, as hard coded things that they think that everybody in the world should see. Like a PagerDuty plugin linking to their overall info pages to drive people to their plugin usage docs (if any) and licensing funnel etc.
The team that owns Backstage, adding custom additional per-plugin info. For example, internally at Spotify we may want to use the PagerDuty plugin but if people want to go somewhere for help with that, they shouldn't go to PagerDuty's corporate offices, they should go to our team internally that owns the service monitoring concerns.
The overall app. Fallback support info guiding people to for example a support ticketing system, or to a slack channel, or similar. This is set once per installation, by the team owning Backstage.

I'm kinda wondering where this PR actually takes us, in terms of that direction.
So in terms of these custom items you mention in this PR, who will add those, and what is it that is being overridden? Will the plugin maker use these to override what the app wants to show? Will the app owner use it to ... no they can't right, because they aren't in control of the props of this component because it's deep inside the react tree in a plugin.
I guess I'm just overall unclear who (what persona) this serves.
We have been thinking for a long time, that each route in a plugin will be wrapped in a special PluginContext, such that for example the support button can ask the current plugin (in terms of, what page we are on and which plugin generates that react tree) "hey what are your support items" basically. Remember, these buttons will typically live somewhere kinda deep inside the react tree and need to be fed contextually somehow. But, who draws this button in the first place? If the plugin maker physically renders the support button themselves, then there's very little point in doing that particular indirection. They could just use children and some nice composability pattern. Just winging it here:
<SupportButton title="PagerDuty">
  <SupportButton.List title="Resources">
    <SupportButton.ListItem title="About" url="https://pagerduty.com/about-our-backstage-plugin" />
  </SupportButton.List>
</SupportButton>

And then it's part of the contract, that there WILL be more items stacked on top of those children, as supplied by the global app.
<Route path="/catalog" element={
  <SupportButton.Context titleOverride="" contents={<...>}>
    <CatalogIndexPage />
  </SupportButton.Context>
} />

I dunno, something like that?

+1 to what @freben is saying, and I would also add that it would be good to be able to tie the support concept into error handling as well, so that when an error happens you'll be able to receive metadata and information about who to contact in the error display, which is something we do internally. That would mean the support context needs to happen at a bit higher level than just the support button, likely per plugin. Still not quite sure what a good way to tie it all together is though.

Could we suggest - maybe make only the title change? That one does make sense. And then revert the other changes and let's discuss the larger picture separately.

Hey @freben, thanks for your comments, so, according to your last comment, Keep I the title prop and then we can discuss about how to add new contact info to the support list?

Yeah. Sorry for the noise, for a feature that sounds so simple on the surface - you just were unfortunate to hit a spot that had been eagerly introduced even though it had a lot of lingering unsolved design in it.

Tugboat has finished building the preview for this pull request!
Link:

https://pr4847-wkai6ieb4tuuttw6guohqrlol8tptnyz.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6042b2c6fcb22df3256a1718

My apologies if I lead this down the wrong path. This would have allowed custom plugins to add items that are then merged with the backstage instance owners support, but may have fallen short of allowing for custom content within a support item group (e.g. the PagerDuty button). I guess that's where using children versus props would come in handy. I guess some questions I have are:

Would the layout be defined at a global level. For instance as the backstage instance owner, I want to have the general support items at the top, and plugin ones underneath. Or I might decide, no I want the general one at the bottom if there is some plugin specific ones.
I'm also guessing there might be a need for multiple general purpose support item groups rather then one.
How much flexibility in content should a plugin be allowed to inject?
Would there be a need to inject dynamic support items? For instance, I'm viewing an entity page and maybe there's a specific support link and/or contextual pager button.

@GunnerStraiker1 Hi, is slimming down the PR to just change the title prop something you want to look at? Otherwise I can finish it up in a bit.

Hi @Rugvip, I'm gonna change it today, sorry for the delay

I'm gonna close this PR because the PR's branch is so many commits behind, so I'm going to open a new PR with all the issues fixed (#5720 )


added input single_end option

PR checklist

[ ] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs
[ ] If necessary, also make a PR on the nf-core/metatdenovo branch on the nf-core/test-datasets repository.
[ ] Make sure your code lints (nf-core lint).
[ ] Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[ ] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).

I noticed that metatdenovo wasn't able to properly deal with single end input so I tried to fix this issue. I think the code can be improved since it is not possible to run an input with mixed samples (single ends and pair ends) but only one type. I am open to suggestions!

I need to run nf-core lint but I am testing another branch at the moment, I will do it later.


Bump dash packages to latest versions. Refs #47

Untested. This commit hopefully triggers the CI pipeline.

Fixes #47

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: ecederstrand sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Hi @ecederstrand,
Working with your PR now as part of the upgrade to dash and dash-table. Should be in 'dash-upgrade' branch if you'd like to see how it connects.
GitHub didn't pick this up as a PR merge (forgot to switch target branch before merge on our end), but your commits are in and it will resolve it once all of the dash-table port is done. Thanks again for the PR!

Cool. Thanks for the update and happy coding!


Marker not shown

Hi all,
I am just trying to Add a marker to the map with a particular LatLng but the marker icon is not visible only the info window is being shown and it is not at the correct location how can I fix this?please correct me if I am coding wrongly.
Please clone my repo https://github.com/Dineshrajaa/MapMan.git

In your code, you should pass the raw div object like this: var mapDiv = $("#mapHolder")[0];.
If you use only with dialog, you just do map = plugin.google.maps.Map.getMap(mapOptions);.
At least for me, this work like this.

Thanks will try this.


(fix/release): update snapshots for common tests

✅ Checklist

[ ] npx changeset was attached.
[ ] Covered by automatic tests.
[ ] Impact of the changes:

...

📝 Description
Replace this text by a clear and concise description of what this pull request is about and why it is needed. Be sure to explain the problem you're addressing and the solution you're proposing.
For libraries, you can add a code sample of how to use it.
For bug fixes, you can explain the previous behaviour and how it was fixed.
In case of visual features, please attach screenshots or video recordings to demonstrate the changes.

❓ Context

JIRA or GitHub link:

🧐 Checklist for the PR Reviewers

The code aligns with the requirements described in the linked JIRA or GitHub issue.
The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
There are no undocumented trade-offs, technical debt, or maintainability issues.
The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
Any new dependencies have been justified and documented.
Performance considerations have been taken into account. (changes have been profiled or benchmarked if necessary)

/generate-screenshots


Reconsider "all maintainers must sign off" rule

As things stand today, all maintainers must sign-off before we move to FCP. I think we run the risk of being blocked more frequently than we think if we follow this rule. I propose we move to a 2/3rds rule or similar.

I think that we might just identify what Fabric component is subject of RFC and ask for sign-off from component owners.

I agree with @C0rWin I think identifying areas of "ownership", or at least expertise, for the maintainers would be an improvement anyway.

@C0rWin: Let's create a PR that builds on PR #5 with the changes that you recommend.

@kchristidis makes sense, will do it.

I'm not strictly opposed to identifying Fabric components, and component ownership, but do we really need this to be a matter of process?  I'd suggest that maintainers are generally aware of who component experts are, and, are willing to defer to those experts where appropriate.
Simply requiring a 2/3rds, or even a simple majority sign-off, where most maintainers will end up concurring with the component experts seems fine and flexible to me.  Given rates of code review and other maintainer engagement, I even question whether a plain majority is too onerous.

Does the above close this issue?


[stable/filebeat] Allow for additional operator overrides

What this PR does / why we need it:
Allows for users to add command, args, imagePullSecrets, and envVars from secrets and configMaps
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:

/lgtm

/lgtm


How to create a submission file for validation set on waymo evaluation server for 3D detection

Hi,
I have been trying to figure out how to create a submission file to evaluate my detections using the top lidar only.
Could you please point me to some example code?
Is the file create_prediction_file_example.py usable for this?
Best Regards
Sambit

you can check this https://github.com/waymo-research/waymo-open-dataset/blob/master/docs/quick_start.md#submit-to-leaderboard


Resolve symfony/polyfill-php80 should be moved to require section in composer.json file #37

Fixes https://github.com/php-openapi/yii2-openapi/issues/37

Thank  you!


bug in Series.replace with timezone-aware datetime columns

Seeing the following behavior in 0.17.1 with the patch from https://github.com/pydata/pandas/pull/11715 applied (would raise without the patch):
In [29]: ser = pd.Series([pd.NaT, pd.Timestamp('2015/01/01', tz='UTC')])

# works
In [30]: ser.replace(pd.NaT, pd.Timestamp.min)
Out[30]:
0    1677-09-22 00:12:43.145225
1     2015-01-01 00:00:00+00:00
dtype: object

# doesn't work
In [31]: ser.replace([np.nan, pd.NaT], pd.Timestamp.min)
Out[31]:
0                         NaT
1   2015-01-01 00:00:00+00:00
dtype: datetime64[ns, UTC]

# works without timezone-aware datetimes
In [32]: ser = pd.Series([pd.NaT, pd.Timestamp('2015/01/01')])
In [33]: ser.replace([np.nan, pd.NaT], pd.Timestamp.min)
Out[33]:
0   1677-09-22 00:12:43.145225
1   2015-01-01 00:00:00.000000
dtype: datetime64[ns]

yep, looks like a buggie! (thanks for the multiple reports BTW). interested in a pull-request to fix?

sure, I'll look into over the weekend


Identify all unreleased related images for an FBC fragment

The set of related images will only continue to grow for a FBC fragment as bundles are added to the packages' channels. Once fragments are released and become part of the target index, we no longer need to consider the validity of these related images. Therefore, we want to be able to determine the set of unique unreleased related images for an FBC fragment so that we know the minimal set of pullspecs that might need to be further inspected and/or verified.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Please upload report for BASE (main@2e1f663). Learn more about missing BASE report.

Additional details and impacted files
@@           Coverage Diff            @@
##             main      #344   +/-   ##
========================================
  Coverage        ?   100.00%
========================================
  Files           ?        18
  Lines           ?       502
  Branches        ?         0
========================================
  Hits            ?       502
  Misses          ?         0
  Partials        ?         0

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Windows 10 720p Bigbunny video playback is poor and audio is scrambled

@akallabeth
playing 720p bigbunny video audio is getting scrambled also tried with /sound:sys:alsa
but got same result
Client VM:- Ubuntu 12.04 xfce
Server:- Windows 10 Enterprise LTSB
Note:-Same on Windows 2k12R2 video playback is good only with /gfx:rfx
Tried  below command one by one but no good result:-
/gfx:AVC444
/gfx:AVC420
freerdp-nightly-dbg_2.0.0+020170110024932.3231.gbp8fd926_i386.deb
xfreerdp /cert-ignore +compression -toggle-fullscreen /title:xx /bpp:16 /f  /microphone -wallpaper +fonts /kbd:0x00000409  /d:xxxx /u:xxx /p:xxxx /v:x.x.x.x /sound:sys:pulse /gfx:AVC444
[17:33:46:749] [6444:6444] [INFO][com.freerdp.utils] - Registering signal hook...
[17:33:46:754] [6444:6445] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpdr
[17:33:46:754] [6444:6445] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpsnd
[17:33:46:755] [6444:6445] [WARN][com.freerdp.core.client] - Skipping, channel already loaded
[17:33:46:755] [6444:6445] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpsnd
[17:33:46:756] [6444:6445] [INFO][com.freerdp.client.common.cmdline] - loading channelEx drdynvc
[17:33:46:791] [6444:6445] [ERROR][com.winpr.timezone] - Unable to find a match for unix timezone: Asia/Kolkata
[17:33:46:848] [6444:6445] [INFO][com.freerdp.gdi] - Local framebuffer format  PIXEL_FORMAT_BGRX32
[17:33:46:849] [6444:6445] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_ABGR32
[17:33:46:865] [6444:6445] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel rdpgfx
[17:33:46:868] [6444:6451] [INFO][com.freerdp.channels.rdpsnd.client] - Loaded pulse backend for rdpsnd
[17:33:50:153] [6444:6452] [ERROR][com.freerdp.channels.drdynvc.client] - ChannelId 10 not found!
[17:33:50:245] [6444:6452] [ERROR][com.freerdp.channels.drdynvc.client] - ChannelId 10 not found!
[17:33:52:930] [6444:6452] [ERROR][com.freerdp.channels.drdynvc.client] - ChannelId 10 not found!

my own build is working fine with audio
This is FreeRDP version 2.0.0-dev (git 90877f5)
Build configuration: BUILD_TESTING=OFF BUILTIN_CHANNELS=OFF HAVE_AIO_H=1 HAVE_EVENTFD_H=1 HAVE_EXECINFO_H=1 HAVE_FCNTL_H=1 HAVE_INTTYPES_H=1 HAVE_MATH_C99_LONG_DOUBLE=1 HAVE_POLL_H=1 HAVE_PTHREAD_MUTEX_TIMEDLOCK=ON HAVE_PTHREAD_MUTEX_TIMEDLOCK_LIB=1 HAVE_PTHREAD_MUTEX_TIMEDLOCK_SYMBOL= HAVE_SYSLOG_H=1 HAVE_SYS_FILIO_H= HAVE_SYS_MODEM_H= HAVE_SYS_SELECT_H=1 HAVE_SYS_SOCKIO_H= HAVE_SYS_STRTIO_H= HAVE_TIMERFD_H=1 HAVE_TM_GMTOFF=1 HAVE_UNISTD_H=1 HAVE_XI_TOUCH_CLASS=1 WITH_ALSA=ON WITH_CHANNELS=ON WITH_CLIENT=ON WITH_CLIENT_AVAILABLE=1 WITH_CLIENT_CHANNELS=ON WITH_CLIENT_CHANNELS_AVAILABLE=1 WITH_CLIENT_COMMON=ON WITH_CLIENT_INTERFACE=OFF WITH_CUPS=ON WITH_DEBUG_ALL=OFF WITH_DEBUG_CAPABILITIES=OFF WITH_DEBUG_CERTIFICATE=OFF WITH_DEBUG_CHANNELS=OFF WITH_DEBUG_CLIPRDR=OFF WITH_DEBUG_DVC=OFF WITH_DEBUG_KBD=OFF WITH_DEBUG_LICENSE=OFF WITH_DEBUG_MUTEX=OFF WITH_DEBUG_NEGO=OFF WITH_DEBUG_NLA=OFF WITH_DEBUG_NTLM=OFF WITH_DEBUG_RAIL=OFF WITH_DEBUG_RDP=OFF WITH_DEBUG_RDPEI=OFF WITH_DEBUG_REDIR=OFF WITH_DEBUG_RFX=OFF WITH_DEBUG_RINGBUFFER=OFF WITH_DEBUG_SCARD=OFF WITH_DEBUG_SND=OFF WITH_DEBUG_SVC=OFF WITH_DEBUG_SYMBOLS=OFF WITH_DEBUG_THREADS=OFF WITH_DEBUG_TIMEZONE=OFF WITH_DEBUG_TRANSPORT=OFF WITH_DEBUG_TSG=OFF WITH_DEBUG_TSMF=OFF WITH_DEBUG_WND=OFF WITH_DEBUG_X11=OFF WITH_DEBUG_X11_CLIPRDR=OFF WITH_DEBUG_X11_LOCAL_MOVESIZE=OFF WITH_DEBUG_XV=OFF WITH_DIRECTFB=OFF WITH_EVENTFD_READ_WRITE=1 WITH_FFMPEG=ON WITH_GPROF=OFF WITH_GSM=OFF WITH_GSTREAMER_0_10=ON WITH_GSTREAMER_1_0=OFF WITH_IPP=OFF WITH_JPEG=ON WITH_LIBAVCODEC=ON WITH_LIBRARY_VERSIONING=ON WITH_LIBSYSTEMD=OFF WITH_MACAUDIO=OFF WITH_MACAUDIO_AVAILABLE=0 WITH_MANPAGES=OFF WITH_MBEDTLS=OFF WITH_OPENH264=ON WITH_OPENSLES=OFF WITH_OPENSSL=ON WITH_OSS=OFF WITH_PCSC=OFF WITH_PROFILER=OFF WITH_PULSE=ON WITH_SAMPLE=OFF WITH_SANITIZE_ADDRESS=OFF WITH_SANITIZE_ADDRESS_AVAILABLE=1 WITH_SANITIZE_LEAK=OFF WITH_SANITIZE_LEAK_AVAILABLE=1 WITH_SERVER=OFF WITH_SERVER_INTERFACE=ON WITH_SMARTCARD_INSPECT=OFF WITH_SSE2=ON WITH_THIRD_PARTY=OFF WITH_VALGRIND_MEMCHECK=OFF WITH_VALGRIND_MEMCHECK_AVAILABLE=1 WITH_WAYLAND=OFF WITH_X11=ON WITH_X264=OFF WITH_XCURSOR=ON WITH_XEXT=ON WITH_XFIXES=ON WITH_XI=ON WITH_XINERAMA=ON WITH_XKBFILE=OFF WITH_XRANDR=ON WITH_XRENDER=ON WITH_XSHM=ON WITH_XV=ON WITH_ZLIB=ON
Build type:          Release
CFLAGS:               -march=i686 -Wall -Wno-unused-result -Wno-unused-but-set-variable -Wno-deprecated-declarations -fvisibility=hidden -Wimplicit-function-declaration -Wredundant-decls -msse2
Compiler:            GNU,
Target architecture: x86

@gnshkl1 The nightly builds are compiled with RelWithDebInfo, so that can explain your issue. The VM is not fast enough to process data in the (less) optimized build, but works fine with a full optimized one.

ok


Type for cosmosDB input binding is specified ambiguously in documentation

In the Configuration section for Python, it says "type: Must be set to cosmosDBTrigger.
However, all examples above this use "type": "cosmosDB"
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: f9e3fe74-1d65-41eb-6a5e-0595e6d06029
Version Independent ID: 8933389b-f4c0-acbd-afe3-86f18738c1f9
Content: Azure Cosmos DB input binding for Functions 2.x and higher
Content Source: articles/azure-functions/functions-bindings-cosmosdb-v2-input.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@KjeldSchmidt Thanks for the feedback. We will review and update as appropriate.

@KjeldSchmidt I've found in the integration test files:


ImportError: cannot import name 'CropRandomizer' from robomimic.models.base_nets

Hello,
I am currently trying to replicate the experiments on LIBERO but am running into the following error:
ImportError: cannot import name 'CropRandomizer' from 'robomimic.robomimic.models.base_nets'
CropRandomizer is not defined in the program. Seems like this person had the same issue, but it was not resolved. I tried the suggested fix to upgrade robomimic to 0.3.0, but it did not change the error.
Any suggestions on how to resolve this would be very appreciated.

downgrade robomimic to 0.2.0 works for me


[Bug report] Not able to download some iqiyi video

[x] I've verified and I assure that I'm running youtube-dl 2016.10.07

Before submitting an issue make sure you have:

[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

youtube-dl -v http://www.iqiyi.com/v_19rr9nv6do.html
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'http://www.iqiyi.com/v_19rr9nv6do.html']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2016.10.07
[debug] Python version 2.7.12 - Darwin-16.0.0-x86_64-i386-64bit
[debug] exe versions: avconv 11.4, avprobe 11.4, ffmpeg 3.1.4, ffprobe 3.1.4
[debug] Proxy map: {}
[iqiyi] temp_id: download video page
[iqiyi] 6491fcdf5cfbdadafc52e89903e89c57: Downloading JSON metadata
ERROR: Unable to load data. Error code: A00110; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 694, in extract_info
ie_result = ie.extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 356, in extract
return self._real_extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/iqiyi.py", line 356, in _real_extract
raise ExtractorError('Unable to load data. Error code: ' + raw_data['code'])
ExtractorError: Unable to load data. Error code: A00110; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Failed to download http://www.iqiyi.com/v_19rr9nv6do.html
Other iqiyi videos are supported but just experienced some issue on this series.
You need a Chinese proxy to view this. You can obtain one here https://vnet.one/?rc=2879

Duplicate of #10088.


Broken repository url with amdgpu-install 5.5.50500-1 for Ubuntu

When installing amdgpu-install_5.5.50500-1_all.deb it writes a file named /etc/apt/sources.list.d/amdgpu-proprietary.list that contains this content:
# Enabling this repository requires acceptance of the following license:
# /usr/share/amdgpu-install/AMDGPUPROEULA
#deb https://repo.radeon.com/amdgpu/@AMDGPUVER@/ubuntu jammy proprietary

Notice the bad @AMDGPUVER@ string (instead of 5.5 version string) that makes this file unusable.

Yes, I had to set 5.4.5 instead:
# Enabling this repository requires acceptance of the following license:
# /usr/share/amdgpu-install/AMDGPUPROEULA
deb https://repo.radeon.com/amdgpu/5.4.5/ubuntu jammy proprietary

Stumbled upon this as well. Am I mistaken if I assume that having fixed versions (like 5.6) in my sources.list-files would mean that ROCM won't update to versions (like 5.7) in the future? That'd be my expectation and I don't really want to manually look up ROCM versions every now an then.

My experience is that when updating the package, the version string in the amdgpu-proprietary.list file gets replaced by @AMDGPUVER@ again.

Thanks to the both of you! I'll keep it as it is for now. 5.6 is performing decently and I'll know if versions >5.6  will be released so I can manually update anyways!

@illwieckz Apologies for the lack of response. Can you please test with latest ROCm 6.1.1? If resolved, please close ticket. Thanks!

@ppanchad-amd Hi, the problem is fixed since ROCm 5.7.


Suggestion: Find frames for link rng based on what number pokemon is recived

For registeel, you need to find a frame (x), then find a frame that advances to x (y), and then find a frame that advances to y (z). Having an option to do this automatically would be great

This function only works for Pokemon Link Regis(inconstant delay), don't wanna make other part slower.
You can search and substract 09-12 frames by yourself. Sometimes multiple frames are satisified.


Change screen address

Would it be possible to change the screen address to be used with the commands which act on the screen ? (if they use kernal routines maybe it's not possible as $0400 should be hardcoded).

I've been thinking about this for a long time.

The easiest way to implement this is through a compiler directive that would instruct the compiler to translate memory locations to the specified VIC bank and a specified screen address within the bank. This would be constant through the program. KERNAL must be notified about the change of course.

To allow dynamic switching of the bank and screen address in runtime - that's a harder job and would slow down all related commands. If one wishes to do this, POKE is the only way I'm afraid.

All in all I think we should go for solution #1

I'm closing this for now as this is going to be solved in #82 .


Catch in Controllers/Checks.php

Hi,
Netbeans give me error because of naming the function "catch".
The issue is in "application/Controllers/Checks.php" in line 300 at the current state.
public function catch() {

Well - that is a temp controller so it will eventually disappear. :)
That being said - we've seen this before and it's an issue with NetBeans and reserved keyword detection.


 to satisfy <string|DOMDocument>

Had use for this the other day, ended up using to satisfy with document.documentElement.
Probably not hard to achieve.

Implemented as part of https://github.com/Munter/unexpected-dom/pull/77


Clarified application developer responsibility when using onException in native mode

[ ] An issue should be filed for the change unless this is a trivial change (fixing a typo or similar). One issue should ideally be fixed by not more than one commit and the other way round, each commit should fix just one issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful and properly spelled subject line and body. Copying the title of the associated issue is typically enough. Please include the issue number in the commit message prefixed by #.
[ ] The pull request description should explain what the pull request does, how, and why. If the info is available in the associated issue or some other external document, a link is enough.
[ ] Phrases like Fix # or Fixes # will auto-close the named issue upon merging the pull request. Using them is typically a good idea.
[ ] Please run mvn process-resources -Pformat (and amend the changes if necessary) before sending the pull request.
[ ] Contributor guide is your good friend: https://camel.apache.org/camel-quarkus/latest/contributor-guide.html

I'm pushing 2 commits at least for review. I'm happy to discuss rebasing them if preferred.


Handle identifiers file not found

https://github.com/Porthmeus/MeMoMe/blob/fc2041b3c4b9cc85d69f7bb94304e1ed66e9c3c1/src/annotateModelSEED.py#L62
Please handle the case that the file is missing appropriately.

Related to #8 if Modelseed  file could not be downloaded

Also related to https://github.com/Porthmeus/MeMoMe/issues/123

Still not done


Screenshot an external webpage

What should i do if i want to screenshot a external webpage? Can you give an example such as a function which accept an url and output an screenshot image?

@shartoo

Are you looking for a client-side, or a server-side solution?
Is the external site under your control?

A client-side solution and the external website is out of my control which could be any website from internet.Something like
const img = jsFunction('https://github.com/html-screen-capture-js/html-screen-capture-js/issues/61')

the img is a image as below

@shartoo Does the server of the external site allow you to fetch from a browser?
Try running the Javascript function fetch(), and check the console for CORS errors.

@shartoo There is another problem. Even if the external site lets you fetch, you can't just capture it. You need its resources loaded and its Javascript to run.

Load all resource  of a website and render and screenshot  seems a very heavy solution.Caputuring iframes  may works, any api from this repo can achieve this?

@shartoo Loading all the resources and running the initial Javascript code must happen anyway, since just the initial HTML text is not enough to display a regular site. I need to check if inlining iframes is even possible.

Moving the mouse hoving over a tab of pages in chrome,a screenshot of the selected page will appear