poetry install console output corrupted on Windows

[x] I am on the latest Poetry version.

[x] I have searched the issues of this repo and believe that this is not a duplicate.

[ ] If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

OS version and name: Windows 10 x64

Poetry version: 0.12.11

Link of a Gist with the contents of your pyproject.toml file: https://gist.github.com/jimbo1qaz/d97d3da78cece9a38157656f9a082034

Issue
When I run poetry install, and look at console output, all upgrade lines have the "arrow and new version" overwriting the beginning of the line of text.
 -> 2019.3.9)certifi (2018.11.29
  - Installing makefun (1.6.1)
 -> 6.0.0)ng more-itertools (4.3.0
 -> 0.9.0)ng pluggy (0.8.1
 -> 1.8.0)ng py (1.7.0
 -> 4.5.3)ng coverage (4.5.2
  - Installing decopatch (1.4.1)
 -> 1.16.2)g numpy (1.16.1
 -> 4.19.15) pyqt5-sip (4.19.13
 -> 4.3.1)ng pytest (4.2.0
 -> 2.8.0)ng python-dateutil (2.7.5
 -> 3.0.3)ng matplotlib (3.0.2
 -> 3.5.dev0+g5bed1af2 5bed1af)
 -> 5.12.1)g pyqt5 (5.11.3
  - Installing pytest-cases (1.5.0)
 -> 1.10.2)g pytest-mock (1.10.0
 -> 0.15.89) ruamel.yaml (0.15.87
  - Installing corrscope (0.5.0-pre)

This happens in Pycharm, Appveyor, and cmd, and appears to be there since 0.12.0 or earlier.

I think poetry prints a stray carriage return on Windows. I theorize poetry strips the final character using [:-1] (which removes the newline on Unix and universal newlines, but when performed Windows binary output \r\n, leaves behind \r.)
poetry/installation/installer.py
            self._io.writeln(
                "  - Updating <info>{}</> (<comment>{}</> -> <comment>{}</>)".format(
                    target.pretty_name,
                    source.full_pretty_version,
                    target.full_pretty_version,
                )
            )

Is source obtained by parsing CLI output from pip list or similar?

I'm not sure that universal_newlines does what you expect it to. What should be done is that freeze_output.split(os.linesep).
At least, that's my guess based off a wild assumption that windows is presenting the \r\n newline rather than it being some more niche bug. I haven't looked at the code at all yet.

Looks like this is fixed in 1.0.0b5!

Thanks for reporting.
I close this issue.


PPSSPP

Hey,
Did u try the PPSSPP Emulator with CSPSP ?
Its works for me but not able to test the Multiplayer section

Not really, i test the game only at singleplayer and only on PSP.
I don't really know how to fix the Multiplayer section bug at PPSSPP, so im kinda confused with it.
Sorry for very late response. I don't use github at all, because it's too hard for me :d
Hey, are you Marcin Ploska? (aka Drakon)


Button not rendering

Bug Report
The newest release (0.80.1) seems to have broken Button
Expected Result
<Button>test</Button> should render a Button
Actual Result
instance.render is not a function
Version
0.80.1
Testcase
https://codesandbox.io/s/lpknn729pl

This bug doesn't just impact <Button>.
Reports of it impacting: Accordion, Input, Label, List and Menu too.

I can confirm this, having same issue:
Warning: Button(...): No `render` method found on the returned component instance: you may have forgotten to define `render`.
Uncaught TypeError: instance.render is not a function

Reverting back to 0.79.1 resolved it.

0.80.0 should work fine as that was what i was working on prior to this update.

See #2831#comment.


Add a section for Medium articles

As GSSoC has ended now, we'll feature the medium articles by our contributors in README.md.
Here're two articles:

GirlScript Summer of Code 2020 Mentor Experience by @PragatiVerma18

GSSOC 2020-A journey to explore the “UNEXPLORED” by @Swarnimashukla

Comment below if you've written one.

@vinitshahdeo I can do this.
Could you assign me

I would like to take this up . Could you assign me?

@PragatiVerma18 if we do not receive a PR from @m-code12 by Sunday EOD. Please re-assign to @Kashish121.

A gentle reminder @m-code12

Yeah I am working on it @vinitshahdeo @PragatiVerma18

@m-code12 Awesome! 👍
Create the PR to channel/documentation once you're done.

@PragatiVerma18  Please review my pr #311

@PragatiVerma18 @vinitshahdeo Please review my pr #311

@m-code12  Please resolve the conflicts in the readme.

@PragatiVerma18 I have created a new pr #315 .Please review and merge.

I want to contribute , can you assign me @nandikajain

@kartikagarwal9 This section is already there in the Readme
Can you make more changes to the existing one?
If yes, go ahead, if not, I will close this issue.

i want to comtribute to it can you assign me

@123mansha Do you have any medium articles?


Implement Bin function push down

Feature Request
Describe the feature you'd like:

We'd like to support Bin function push down.
Teachability, Documentation, Adoption, Migration Strategy:

At least one integration test and several unit tests.

Hi @Willendless ,  I have committed my code in PR #5246 but get build failed in stage "Static Analysis". The details can be found in https://ci.pingcap.net/blue/organizations/jenkins/tiflash-build-common/detail/tiflash-build-common/7484/pipeline/
All the error message are same:
error: use auto when initializing with a template cast to avoid duplicating the type name
[modernize-use-auto,-warnings-as-errors]

These static-check errors are not introducted by my new codes...

Hi @Willendless , I have committed my code in PR #5246 but get build failed in stage "Static Analysis". The details can be found in https://ci.pingcap.net/blue/organizations/jenkins/tiflash-build-common/detail/tiflash-build-common/7484/pipeline/
All the error message are same:
error: use auto when initializing with a template cast to avoid duplicating the type name
[modernize-use-auto,-warnings-as-errors]

These static-check errors are not introducted by my new codes...

Got it! It seems not your code's problem that causes the building error.


HowTo Register an App via portal.azure.com

Project
Virtual Assistant
Description
In the documentation it is explained to create new app via https://apps.dev.microsoft.com. But I get message "Insufficient privileges to complete the operation." when I try to create registration for an app. It seems that I need to be Global Administrator. Another possibility is to create the registration via portal.azure.com -Azure AD - Register (Preview).
But there is no documentation how to do it right for Virtual Assistant.
Expected behavior
Documentation how to register an app via portal.azure.com for Virtual Assistant.
Thank you.

Hi David,
The Azure Portal route is the new approach for creating this (in preview), have you tried that route to see if you can create the application? I'm assuming you ran into the automatic creation issue hence your trying to do manually?

Hello @darrenj
Yes, I tried. But I'm not sure what are the exact setting, e.g. what to take for 'Supported account types' and where is now 'Leave Allow Implicit Flow checked'?
The consequence is that the deployment seems do not work completely. When testing with Emulator I get the message error Code 401.  So assume that perhabs the registration of the app is not completly correct.
Please advice which settings I should normally take if I use the new route.
Thank you.

The Azure Portal method of creating an app registration has been documented here: https://github.com/Microsoft/AI/blob/master/solutions/Virtual-Assistant/docs/virtualassistant-createvirtualassistant.md#skill-authentication


Need to create launch.json

We should be able to launch the project by pressing F5 on both linux and windows

I have never had a use for it since I use the CMake extension (shortcuts are SHIFT+F5 to run and CTRL+F5 to debug) but you are right! Would you be kind enough to open a pull request?

I believe using the CMake extension is enough.

I believe using the CMake extension will be enough.


Merge dev with main

This fails
Quitting from lines 56-67 (CalculateEmissionFactors.Rmd)
Error in utils::download.file(paste0(debug_url, "/", source), paste0(directory,  :
  cannot open URL 'https://edap-ord-data-commons.s3.amazonaws.com/useeior/NGHGIAM_GHG_TotalsBySector_2012.csv'

These GHG flow by sector files by year never got added into the Data Commons. Are there actually prepared with final formatting?

FYI @catherinebirney

By default, only purchaser price matrices are used to prepare final table. Is it necessary to give users option for grabbing producer price matrices? @WesIngwersen

let's just do PUR for now to reduce confusion and see what kind of requests/feedback that we get

These GHG flow by sector files by year never got added into the Data Commons. Are there actually prepared with final formatting?

@WesIngwersen @MoLi7 I don't see the csv files on sharepoint - let me know where they are and I can add to Data Commons

These GHG flow by sector files by year never got added into the Data Commons. Are there actually prepared with final formatting?

@WesIngwersen @MoLi7 I don't see the csv files on sharepoint - let me know where they are and I can add to Data Commons

I can upload them to 'USEEIO_team/useeior' on sharepoint, is it a good place?

@MoLi7 Yes, thanks

Files are on Data Commons

CalculateEmissionFactors.Rmd will fail for Industry or Summary models. The string processing lacks insertion of - before of after. It wasn't a simple fix because the additions depend on whether or not one or both of those cases are true, and therefore likely needs refactoring. Another option that might be preferable is to load the model table and index it by selected options to match the model name.

How about adding a - right after 2.0.xx to ensure i, s, or is always has a leading -. Then for commodity-detail model, replace -- with - in modelname. @WesIngwersen
modelname <- paste0("USEEIOv2.0.",
                    substr(params$modelyear, 3, 4),
                    "-",
                    ifelse(params$modeltype=="Commodity", "", "i"),
                    ifelse(params$modellevel=="Detail", "", "s"),
                    "-GHG")
modelname <- sub("--", "-", modelname)

CalculateEmissionFactors.Rmd will fail for Industry or Summary models. The string processing lacks insertion of - before of after. It wasn't a simple fix because the additions depend on whether or not one or both of those cases are true, and therefore likely needs refactoring. Another option that might be preferable is to load the model table and index it by selected options to match the model name.

How about adding a - right after 2.0.xx to ensure i, s, or is always has a leading -. Then for commodity-detail model, replace -- with - in modelname. @WesIngwersen
modelname <- paste0("USEEIOv2.0.",
                    substr(params$modelyear, 3, 4),
                    "-",
                    ifelse(params$modeltype=="Commodity", "", "i"),
                    ifelse(params$modellevel=="Detail", "", "s"),
                    "-GHG")
modelname <- sub("--", "-", modelname)

Sure, just need a solution.

The DQ file names had not been updated to reflect the naming convention that the code was expecting

i have now tested and successfully produced factors from all models. merge when ready

@WesIngwersen any other changes you'd want to make before merge?


FancyZones with Virtual Desktops

Microsoft PowerToys version
0.55.1
Running as admin

[X] Yes

Area(s) with issue?
FancyZones
Steps to reproduce
Lock (Win+L) PC overnight.
✔ Expected Behavior
Zones don't change.
❌ Actual Behavior
I have set up different zones for my Virtual Desktop. During any open Windows session, the zones work as they should. However, after 'Locking' my session overnight, when I re-login Windows desktop, the zones from my main desktop have taken over my virtual desktop. I must reset the zones in the virtual desktop each time.
One thing to note here, I have a multi-display setup, and my main display is a TV, not a computer display. It's possible this is the reason as the TV completely shuts off, it doesn't just go into Sleep mode like the computer displays.
Other Software
DIsplayFUsion Pro 10.00
Samsung Dex (not using, but its running)

Does it happen in the latest release? If yes, please attach a /bugreport.

Pardon the delayed response; the issue is still occurring. Here's the file...
PowerToysReport_2022-04-22-08-10-24.zip

Thank you for the report. I see there that you have the same problem as https://github.com/microsoft/PowerToys/issues/16370.
So let's keep this one closed as a dulplicate. You can track progress in the mentioned issue.


Use Prisma Client from within the browser to connect to SqlLite Javascript in memory database without server side

Problem
I wish to use Prisma Client from within the browser entirely without a server, connecting to SqlLite Javascript in memory, when I tried to pack it up with browserify it complained in the console log that it would not work in the browser.

Example
const client = new PrismaClient()
Throws
Error: PrismaClient is unable to be run in the browser. In case this error is unexpected for you, please report it in https://github.com/prisma/prisma-client-js/issues

The motivation for doing this is that the trend is to move towards JAMStack pages which are webpages where most of the functionality is HTML and Javascript and minimizing the server side. If I can load a SqlLite database in Javascript in the client browser from static files hosted on CDN then it makes it easy to provide the type of data querying I want to do at a lower cost (no server required) for a large number of users. That is, I can scale out to many users without the need for a Prisma server side. I could query a SqlLite database which is just a file. I could send any changes in GraphQL off to be processed to somewhere else.
Sales pitch: Getting onto the JAMStack wagon would help promote Prisma!
SqlLite in Javascript is here
https://github.com/sql-js/sql.js
JamStack sites are now getting popular.
https://jamstack.org/
Suggested solution
Well I'm not sure if it can even be done. I see TypeORM can work with SqlLite in Javascript all within the browser and I think that's useful.

We have a similar use where we want to use Prisma with sqlite from within an app built with Ionic/Vue. Individual apps will have their own the sqlite database and when we push for updates, if there are database changes, we will run the migration on each of those devices. If it's the initial installation, it will simply run all the migrations. This would add a great usage for things like offline apps which store the data in databases like sqlite and then sync when online.

Quick background why this would be difficult in the current implementation of our Query Engine:
The Query Engine we are using ships with the SQLite client and can only talk to a local file. That is a limitation that makes total sense on the server side where Prisma is usually used. It becomes harder in a web/browser context, where there is not real file system and SQLite is usually provided via a browser API or a native API (as in the Capacitor and Cordova plugin). I am sure there is a solution on how to make them talk to each other, but it is not something that works out of the box and that will be trivial to figure out and fix (Especially with all the mobile platforms, versions, changes by device manufacturer etc)

My use case is to use Node.js + MySQL in prod, but SQL.js in the browser during development with the Node.js back-end APIs running in the browser. Integration tests would be running the front-end and back-end together with SQL.js as well. So, development could mostly occur in the browser with this type of setup.
As it stands now, the query builder and query engine are coupled together in the Prisma client. However, I wonder if Prisma could have a client type that doesn't even use an engine binary, and instead calls a user-defined callback. For example, imagine if queries could be routed to SQL.js (or other JavaScript libraries) like so:
const db = new SQL.Database();

const prisma = new EnginelessPrismaClient((sql: string) => {
  return db.exec(sql);
});

const allUsers = await prisma.user.findMany({
  include: { posts: true }
});

Perhaps the callback would have to be way more complex than I am imagining, or there is some reason why this wouldn't even be possible.

I'm also interested in this use case. For node.js there are lots of alternatives already. For use in a JS environment w/ SQL.js / sqlite there is only TypeORM currently.
Prisma has the option to establish itself as a viable alternative for that use case easily.
Especially considering the trend towards edge computing and offline first and the fact that the expected user experience is making a database on frontends more common by the day.
Using the same rust engine compiled to WASM seems like a good idea to me.

Up on this topic! There are now examples of SQLite running in the browser in WASM on top of Origin-Private FileSystem (OPFS).
This should make a browser based version of Prisma doable, and extremely appealing, for offline use cases.
https://news.ycombinator.com/item?id=33374402

Chrome dev blog mentioning this approach today, this is gaining steam! Would be awesome to get Prisma support
https://developer.chrome.com/blog/sqlite-wasm-in-the-browser-backed-by-the-origin-private-file-system/

Seems like the prisma vscode extension already uses a WASM engine.
https://www.prisma.io/blog/vscode-extension-prisma-rust-webassembly
https://www.prisma.io/blog/wnip-q4-dsk0golh8v#vs-code-extension-now-uses-a-wasm-module

Seems like the prisma vscode extension already uses a WASM engine. https://www.prisma.io/blog/vscode-extension-prisma-rust-webassembly https://www.prisma.io/blog/wnip-q4-dsk0golh8v#vs-code-extension-now-uses-a-wasm-module

Exactly, since the engine is written in Rust it is quite easy to build a WebAssembly bundle to enable support for the browser. This is a huge untapped potential for prisma. Now that OPFS is available, the recommended way of doing SQL in the browser is already via wasm. Hopefully someone from the team can take a look!

Yeah, the potential is huge. For example you could build offline first PWAs and use the same prisma client on a server and directly browser.

the prisma-schema engine code is released here:
https://github.com/prisma/prisma-engines/blob/main/prisma-schema-wasm
They also have a wasm engine here:
https://github.com/prisma/prisma-engines/tree/main/query-engine/query-engine-wasm
so it seems like the plumbing is available- and the main repo has gotten lots of WASM attention in the past few weeks.

the prisma-schema engine code is released here:
https://github.com/prisma/prisma-engines/blob/main/prisma-schema-wasm
They also have a wasm query engine here:
https://github.com/prisma/prisma-engines/tree/main/query-engine/query-engine-wasm
so it seems like the plumbing is available- and the main repo has gotten lots of WASM attention in the past few weeks.
Our best bet is to compile each wasm module and run the tests as a web client instead of a server node client

any updates on this? also related - how's wasm-support for prisma client now ? I saw there were some binaries needed so wasm is not fully et

Yeah, the potential is huge. For example you could build offline first PWAs and use the same prisma client on a server and directly in the browser.

This is exactly my use case.
It would make migrating any pre-existing non local-first projects a breeze. Youd be comfortable knowing you'd have the same type contracts when building out your local sqlite database to match your server.

+1 this... would be amazing

Would be great for building Tauri apps. There is a rust plugin for doing things on the rust backend but being able to keep an sqlite database on the front end would greatly simplify the creation of desktop apps with more than just localstorage for offline.

+1 https://github.com/prisma/prisma/issues/5385#issuecomment-2417881298
Would be hella cool to use with service-workers / hono
app.get(
  "/users",
  cache({
    cacheName: "users",
    wait: true,
    cacheControl: "max-age=3600",
  }),
  async (c) => {
    const referer = c.req.header("Referer");
    c.header("Access-Control-Allow-Origin", "*");
    c.header("Access-Control-Allow-Methods", "OPTIONS,GET,PUT,POST,DELETE");
    c.header("Access-Control-Allow-Headers", "*");

    console.log(c.req.routePath.replace("sw/", ""));
    const data = await ofetch(
      "http://localhost:3010" + c.req.routePath.replace("sw/", "")
    );
    console.log({ data });
    return c.json(data);
  }
);

currently CORS isnt an issue, but have to forward a SW.js request to a server 🤦


AppSync subscription support

I think that more and more people use AppSync nowadays, so it would be great to support its subscription via Altair as well.
Tried to set it and finally when in the subscription URL is put wss but with AppSync endpoint and not with the realtime URL
I got some response but says  Error during WebSocket handshake: Unexpected response code: 404
With the realtime URL receives: Both, the "header", and the "payload" query string parameters are missing
Also found this one https://github.com/imolorhe/altair/issues/417 but seems it has been closed with no solution.
Am I doing something wrong or it's not supported yet?

Hey @Sunac, do you have (or know about) a publicly available graphql server using aws appsync that I could use for testing the implementation for this?

Thanks @imolorhe  !! Unfortunatelly, this project is not publicly available but will try to get some that could be used.

@Sunac I've deployed the changes with AppSync integration here: https://s18767-altair-imolorhe.surge.sh/
Please test the changes and let me know if it works.

@imolorhe I am looking for something like that. I have tried to test your site, but it returns ```
An error occurred in subscription.
Error: can't access property "url", t is undefined
I am trying to connect mine one which is using JWT

@joseph-so nice that you're testing it. I need it. Could you provide more of the error stack?

@imolorhe ,
I am using the Firefox developer edition. The application is using JWT for the authentication
An error occurred starting the subscription. TypeError: can't access property "url", t is undefined
    n https://s18767-altair-imolorhe.surge.sh/main.js:1
    createSubscriptionHandshakeLink https://s18767-altair-imolorhe.surge.sh/main.js:1
    execute https://s18767-altair-imolorhe.surge.sh/main.js:1
    e/this.startSubscription$< https://s18767-altair-imolorhe.surge.sh/main.js:1
    _next https://s18767-altair-imolorhe.surge.sh/main.js:1
    next https://s18767-altair-imolorhe.surge.sh/main.js:1
    notifyNext https://s18767-altair-imolorhe.surge.sh/main.js:1
    _next https://s18767-altair-imolorhe.surge.sh/main.js:1
    next https://s18767-altair-imolorhe.surge.sh/main.js:1
    notifyNext https://s18767-altair-imolorhe.surge.sh/main.js:1
    _next https://s18767-altair-imolorhe.surge.sh/main.js:1
    next https://s18767-altair-imolorhe.surge.sh/main.js:1
    r https://s18767-altair-imolorhe.surge.sh/main.js:1
    _trySubscribe https://s18767-altair-imolorhe.surge.sh/main.js:1
    subscribe https://s18767-altair-imolorhe.surge.sh/main.js:1
    a https://s18767-altair-imolorhe.surge.sh/main.js:1
    _trySubscribe https://s18767-altair-imolorhe.surge.sh/main.js:1
    subscribe https://s18767-altair-imolorhe.surge.sh/main.js:1
    a https://s18767-altair-imolorhe.surge.sh/main.js:1
    _innerSub https://s18767-altair-imolorhe.surge.sh/main.js:1
    _next https://s18767-altair-imolorhe.surge.sh/main.js:1
    next https://s18767-altair-imolorhe.surge.sh/main.js:1
    r https://s18767-altair-imolorhe.surge.sh/main.js:1
    _trySubscribe https://s18767-altair-imolorhe.surge.sh/main.js:1
    subscribe https://s18767-altair-imolorhe.surge.sh/main.js:1
    call https://s18767-altair-imolorhe.surge.sh/main.js:1
    subscribe https://s18767-altair-imolorhe.surge.sh/main.js:1
    a https://s18767-altair-imolorhe.surge.sh/main.js:1
    _innerSub https://s18767-altair-imolorhe.surge.sh/main.js:1
    _next https://s18767-altair-imolorhe.surge.sh/main.js:1
    next https://s18767-altair-imolorhe.surge.sh/main.js:1
    _tryProject https://s18767-altair-imolorhe.surge.sh/main.js:1
    _next https://s18767-altair-imolorhe.surge.sh/main.js:1
    next https://s18767-altair-imolorhe.surge.sh/main.js:1
    _next https://s18767-altair-imolorhe.surge.sh/main.js:1
    next https://s18767-altair-imolorhe.surge.sh/main.js:1
    next https://s18767-altair-imolorhe.surge.sh/main.js:1
    d https://s18767-altair-imolorhe.surge.sh/main.js:1
    __tryOrUnsub https://s18767-altair-imolorhe.surge.sh/main.js:1
    next https://s18767-altair-imolorhe.surge.sh/main.js:1
    _next https://s18767-altair-imolorhe.surge.sh/main.js:1
    next https://s18767-altair-imolorhe.surge.sh/main.js:1
    _tryNext https://s18767-altair-imolorhe.surge.sh/main.js:1
    _next https://s18767-altair-imolorhe.surge.sh/main.js:1
    next https://s18767-altair-imolorhe.surge.sh/main.js:1
    _next https://s18767-altair-imolorhe.surge.sh/main.js:1
    next https://s18767-altair-imolorhe.surge.sh/main.js:1
    observe https://s18767-altair-imolorhe.surge.sh/main.js:1
    dispatch https://s18767-altair-imolorhe.surge.sh/main.js:1
    _execute https://s18767-altair-imolorhe.surge.sh/main.js:1
    execute https://s18767-altair-imolorhe.surge.sh/main.js:1
    flush https://s18767-altair-imolorhe.surge.sh/main.js:1
    schedule https://s18767-altair-imolorhe.surge.sh/main.js:1
    schedule https://s18767-altair-imolorhe.surge.sh/main.js:1
    schedule https://s18767-altair-imolorhe.surge.sh/main.js:1
    scheduleMessage https://s18767-altair-imolorhe.surge.sh/main.js:1
    _next https://s18767-altair-imolorhe.surge.sh/main.js:1
    next https://s18767-altair-imolorhe.surge.sh/main.js:1
    notifyNext https://s18767-altair-imolorhe.surge.sh/main.js:1
    _next https://s18767-altair-imolorhe.surge.sh/main.js:1
    next https://s18767-altair-imolorhe.surge.sh/main.js:1
    _next https://s18767-altair-imolorhe.surge.sh/main.js:1
    next https://s18767-altair-imolorhe.surge.sh/main.js:1
    notifyNext https://s18767-altair-imolorhe.surge.sh/main.js:1
    _next https://s18767-altair-imolorhe.surge.sh/main.js:1
    next https://s18767-altair-imolorhe.surge.sh/main.js:1
    _next https://s18767-altair-imolorhe.surge.sh/main.js:1
    next https://s18767-altair-imolorhe.surge.sh/main.js:1
    next https://s18767-altair-imolorhe.surge.sh/main.js:1
    next https://s18767-altair-imolorhe.surge.sh/main.js:1
    next https://s18767-altair-imolorhe.surge.sh/main.js:1
    dispatch https://s18767-altair-imolorhe.surge.sh/main.js:1
    sendRequest https://s18767-altair-imolorhe.surge.sh/main.js:1
    template https://s18767-altair-imolorhe.surge.sh/main.js:1
    ba https://s18767-altair-imolorhe.surge.sh/main.js:1
    i https://s18767-altair-imolorhe.surge.sh/main.js:1
    o https://s18767-altair-imolorhe.surge.sh/main.js:1
    __tryOrUnsub https://s18767-altair-imolorhe.surge.sh/main.js:1
    next https://s18767-altair-imolorhe.surge.sh/main.js:1
    _next https://s18767-altair-imolorhe.surge.sh/main.js:1
    next https://s18767-altair-imolorhe.surge.sh/main.js:1
    next https://s18767-altair-imolorhe.surge.sh/main.js:1
    emit https://s18767-altair-imolorhe.surge.sh/main.js:1
    DR https://s18767-altair-imolorhe.surge.sh/main.js:1
    ba https://s18767-altair-imolorhe.surge.sh/main.js:1
    i https://s18767-altair-imolorhe.surge.sh/main.js:1
    O https://s18767-altair-imolorhe.surge.sh/main.js:1
    invokeTask https://s18767-altair-imolorhe.surge.sh/polyfills.js:1
    onInvokeTask https://s18767-altair-imolorhe.surge.sh/main.js:1
    invokeTask https://s18767-altair-imolorhe.surge.sh/polyfills.js:1
    runTask https://s18767-altair-imolorhe.surge.sh/polyfills.js:1
    invokeTask https://s18767-altair-imolorhe.surge.sh/polyfills.js:1
    p https://s18767-altair-imolorhe.surge.sh/polyfills.js:1
    h https://s18767-altair-imolorhe.surge.sh/polyfills.js:1
main.js:1:2138721

I have followed https://docs.aws.amazon.com/appsync/latest/devguide/real-time-websocket-client.html to get up the authentication header as
{
    "Authorization":"<JWT_TOKEN>",
    "host":"<application_url>"
}

I have also set up the corresponding in the HTTP Header, so I can confirm the value is correct (I can get the Query and the Schema Document working)
P.S. I am looking for a simple way to confirm the AppSync developed by my colleague is correct before I start to write my own code.

@joseph-so For the appsync subscription, I'm making use of https://github.com/awslabs/aws-mobile-appsync-sdk-js
You should only need to set the connection parameters with something like this:
{
    "aws_project_region": "us-west-2",
    "aws_appsync_graphqlEndpoint": "https://<id>.appsync-api.us-west-2.amazonaws.com/graphql",
    "aws_appsync_region": "us-west-2",
    "aws_appsync_authenticationType": "API_KEY",
    "aws_appsync_apiKey": "<api-key>"
}

.. and provide the same graphql endpoint as the URL in Altair and the subscription URL as well. You shouldn't need to set any headers. You should have the URLs as https:// as well, and not wss://
If it's possible, you could also checkout the simolorhe/implement-app-sync-subscription-provider branch locally and run Altair locally (from packages/altair-app). That would yield better error stacks that would be better to debug with. You could also end up debugging yourself.

@imolorhe
Thanks a lot for your reply. However, our AppSync is implemented with the OpenID Connect, which cannot use API-KEY

I don't think it only works with the API_KEY authentication type. What I'm just saying is that the data you pass in the connection parameters should be a valid aws export config

@imolorhe YOU'RE THE BEST :1st_place_medal:
Sorry, I was off for several days and spotted it today. Tested it and looks fine :+1:
I'm finally able to use my fav Altair for subscription as well.
Thanks a lot!

Awesome! Thanks for confirming @Sunac! Was it straightforward to work with? Are there any things to take note of? Can you post a snapshot of the valid config you used (remove sensitive aspects replaced with dummy before posting)?
I'd need to add that to the docs and ensure things are working as expected (since I can't test or use it myself 😅 )

@imolorhe Thank you!
Sure, I'll share with you my try. Basically, I just did what you already mentioned here: https://github.com/imolorhe/altair/issues/1352#issuecomment-725375052

So, to start receiving subscriptions this was enough. Didn't try yet to optimize the config but this works fine :).
It could be mentioned that the client uses MQTT over WebSockets (checked network) as full mutation payload is received and not only the selection set from my subscription as you can see in the response. That could be useful.
More details could be found here: https://docs.aws.amazon.com/appsync/latest/devguide/aws-appsync-real-time-data.html

Thanks for sharing. I'll most likely be using these screenshots as-is in the docs as well 🙂

Now in v3.0.0

I don't think it only works with the API_KEY authentication type. What I'm just saying is that the data you pass in the connection parameters should be a valid aws export config

Hi @imolorhe, I have spent sometimes to understand the code and found out that you have allowed apiKey to be passed but not the jwtToken. That is the reason why I got the authentication fail.
I have created a new issue and pull request for you to review. Thanks a lot

I don't think it only works with the API_KEY authentication type. What I'm just saying is that the data you pass in the connection parameters should be a valid aws export config

Hi @imolorhe, I have spent sometimes to understand the code and found out that you have allowed apiKey to be passed but not the jwtToken. That is the reason why I got the authentication fail.
I have created a new issue and pull request for you to review. Thanks a lot

@joseph-so awesome! I'll take a look.

@joseph-so awesome! I'll take a look.


Docker seams to be a dead project

Steps To Reproduce
go over to https://github.com/evidence-dev/docker-devenv have a look at the issues. They are very old, and no answer from any maintainer
also the latest docker image is 8 month old
Environment
docker
Expected Behavior
maintainers at least answer the most simple questions and close the answered once
ideally: solve the documentation bugs, and real bugs with wsl
Actual Behaviour
nobody seams to take care
Workarounds
ignore docker-container, and build your own images from a fork

@mdopp thanks for flagging this -- we're going to pin an issue on the repo, and remove the docker dev env from our docs until we're able to prioritize it again.
We would certainly welcome a PR if you're interested in contributing to it.


How to: line breaks in label

I have the next issue:

How to make labels more responsive?

Admittedly, there is unfortunately no current way to move the labels anywhere (#10), wrap them, or add line breaks. It is rather non-trivial to add these elements, but certainly desirable.

Upon further inspection, it appears like it would be relatively easy to support manually-defined line breaks. Would just need to add appropriate <tspan> elements. Just need to make sure that the first element has a dy of (-1 * textHeight * (length - 1)) / 2 while the rest of the <tspan> elements have a dy of textHeight.
<text x="160" y="280" fill="#fff" text-anchor="middle" dominant-baseline="middle" pointer-events="none" style="font-size: 14px;">
  <tspan dy="-10" x="160" text-anchor="middle" dominant-baseline="middle">Applicants</tspan>
  <tspan dy="20" x="160" text-anchor="middle" dominant-baseline="middle">12,000</tspan>
</text>

I'll target this for a release soon.

Line breaks are now supported in the label.format. It is important to note that this is not done responsively: the chart will not automatically break lines when it the text will exceed the container.
Since this is a change from previous treatment of newline characters, this will be released in a new major version.


add xarray to environment.yml

Satisfies #37

Do we want to add an additional dependency? I really like xarray so far, and would love to use it. I'm a bit hesitant to add more requirements to the core framework. Part of being a lightweight framework is that it has minimal dependencies. I've even wondered if I should remove the qtoml dependency.
Thoughts?

I thought we agreed environment.yml was going to be for a development environment, not for turbopy dependencies. We need xarray for the particle_in_field integration test that I'm putting in.

@padamson I took a look at the xarray website and saw that the big draw is that you can apply and utilize labels on an array. how are you planning on using this feature in the particle-in-field integration test?

It’s already used in tests/fixtures/particle_in_field/particle_in_field.py. We need to think through exactly if/how we want to use example apps for testing, but one approach is just to store “good” output in tests/fixtures/particle_in_field/ and and compare the output from the test to the stored data.  There is even a way to compare output from plots to “good” images of plots.
--
Paul Adamson, PhD
Naval Research Laboratory, Code 6770.1
4555 Overlook Ave. SW
Washington, DC 20375-5320
(o)<PHONE_NUMBER>
(c)<PHONE_NUMBER>
From: Gareth Morgan<EMAIL_ADDRESS>Reply-To: NRL-Plasma-Physics-Division/turbopy<EMAIL_ADDRESS>Date: Tuesday, July 21, 2020 at 1:59 PM
To: NRL-Plasma-Physics-Division/turbopy<EMAIL_ADDRESS>Cc: Paul Adamson<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [NRL-Plasma-Physics-Division/turbopy] add xarray to environment.yml (#39)
@padamson I took a look at the xarray website and saw that the big draw is that you can apply and utilize labels on an array. how are you planning on using this feature in the particle-in-field integration test?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Cool! Thank you

I didn't realize you were using xarray in the tests. And good point about this being a dev environment.


Jet-Main Page + Schedule  Page

Scheudle page with mobile repsonisvness no safari check
Merged in Main page, needed ot do some modifications becasue i changed hte abckground as well.

Alex also contributed oops should of added that in the title sorry!


sharding-proxy doesn't has some tables in the config default datasource,why?

Question
i has three databases,the config-sharding.yaml like that :
schemaName: sharding_db
dataSources:
  ds:
    url: jdbc:mysql://******/dface_v3_base?serverTimezone=UTC&useSSL=false
    username: ****
    password: ****
    autoCommit: true
    connectionTimeout: 30000
    idleTimeout: 60000
    maxLifetime: 1800000
    maximumPoolSize: 50
  ds_0:
    url: jdbc:mysql://****/dface_v3_0?serverTimezone=UTC&useSSL=false
    username: ****
    password: ****
    autoCommit: true
    connectionTimeout: 30000
    idleTimeout: 60000
    maxLifetime: 1800000
    maximumPoolSize: 50
  ds_1:
    url: jdbc:mysql://****/dface_v3_1?serverTimezone=UTC&useSSL=false
    username: ****
    password: ****
    autoCommit: true
    connectionTimeout: 30000
    idleTimeout: 60000
    maxLifetime: 1800000
    maximumPoolSize: 50
shardingRule:
  tables:
    t_order:
      actualDataNodes: ds_${0..1}.t_order_${0..1}
      tableStrategy:
        inline:
          shardingColumn: order_id
          algorithmExpression: t_order_${order_id % 2}
      keyGeneratorColumnName: order_id
    t_order_item:
      actualDataNodes: ds_${0..1}.t_order_item_${0..1}
      tableStrategy:
        inline:
          shardingColumn: order_id
          algorithmExpression: t_order_item_${order_id % 2}
      keyGeneratorColumnName: order_item_id
  bindingTables:
    - t_order,t_order_item
  defaultDataSourceName: ds
  defaultDatabaseStrategy:
    inline:
      shardingColumn: user_id
      algorithmExpression: ds_${user_id % 2}
  defaultTableStrategy:
    none:
  defaultKeyGeneratorClassName: io.shardingsphere.core.keygen.DefaultKeyGenerator

The dface_v3_base has three tables:face_update,recurrence,t_config.
The dface_v3_0 has four tables:t_order_0,t_order_1,t_order_item_0,t_order_item_1.
The dface_v3_1 has four tables:t_order_0,t_order_1,t_order_item_0,t_order_item_1.
The question is :why the sharding-proxy just show four tables:recurrence,t_config,t_order,t_order_item

hi，please let me know the proxy version you used.

sharding-proxy-3.0.0

@cherrylzhao  sharding-proxy-3.0.0

@tianyijushi
I could't reproduce your issue on my local environment. the show tables logic for 3.0.0 is only display these table which configured sharding-rule, so it should be t_order and t_order_item

which mysql-client have you used? Navicat or command line? please use mysql command line, then show tables to verify it.

for 4.0.0-RC1, we should enhance it, show tables will be routed to a random datasource include default datasource.

@cherrylzhao

the rule and real database is :

ps:I has tried Navicat and command line ,just the same.

are you sure the version is 3.0.0

please make sql.show = true, and send the logicSQL and actual SQL to me.

these libs should be in that version.

also please make 'sql.show: true` in server.yaml, then send the log including startup to me.

@cherrylzhao

ok, I'll investigate it later.

Thank you! Waiting for your news.

we have a bug in 3.0.0 for retrieving metadata of default datasource.I think you have a database instance also named ds to make the sense more complex.

@tianyijushi I have fixed this issue, you can verify it again.

No response any more, I just close this issue.


ci: try to re-generate previews

This was a mistake for now, meant to test this out in my own repository before seeing if it was worth raising.


Trigger homebrew action post release

@lionello wanna merge this and trigger a build to see if it works?


[GalException/NOT_SUPPORTED_FORMAT]: Unsupported file formats

Describe the bug
Sending an SVG to an iPad fails.
To reproduce

Open LocalSend on two devices, on one which is iPad.
Send a SVG to the iPad
Download errors.

Expected behavior
Download should complete successfully.
Smartphone (please complete the following information)
iPadOS 17.4.1
Additional context
In advanced options, disabling saving to gallery fixes the problem. Apparently this exception was introduced in gal 1.4.0, because iOS doesn't support SVG format...

I got the same problem when i send .MKV file to my iphone.

Got the same error when sending MKV files from MacBook Pro (macOS 15.0.1) to iPhone (iOS 18.0.1)

For me, unchecking "Save media to gallery" under the "Receive" section in settings resolves this problem.


Need some help

So when I go to run a basic Telepathy query I get the following:
The API access for bot users is restricted. The method you tried to invoke cannot be executed as a bot (caused by GetHistoryRequest)

Hi! It seems you're trying to use this via details from the Telegram Bot API, rather than from setting up a Telegram's main API. Methods from one will not work on the other.
You'll need to set up a Telegram account and then get API details via this method. https://core.telegram.org/api/obtaining_api_id
Let me know if that works for you, or if you run into any other problems.


Nebra App issues - The app gives a blank screen at launching, Unable to Onboard & Can't assert the location

We have received the following from customers over the last few weeks. (Jan 2023 - Present)

The app gives a blank screen at launching on some devices (it does not start at all)
Unable to Onboard new devices: 404 error
Nebra android app can't sign in via google and throws this error: Access blocked: Authorization Error; Error 403: disallowed user agent
Can't assert the location

All customers have been contacted and asked to make sure their phone is on the latest OS and also if they could delete the Nebra App and re-install it again.
We'll keep adding to the list if needed which can be found HERE
Quick summary of the phone models below.

One plus 7, Android 12
Phone Pixel 6 App version 1.0.11
Latest version app on iOS (1.0.6) iPhone 14 Pro running the latest iOS 16.3
Samsung S20 Blank Page
Samsung S21 Blank Page
Galaxy A32 , Android 12
Model Xiaomi Version MIUI 12.0.1
Samsung S20+ SM-G985F Android Version 13 Using Nebra version 1.0.11
Samsung A53, Xcover5, Xiaomi Redmi 4
Apple iPhone X, latest iOS
iPhone 14 Pro. iOS version 16.3.1

@kashifpk, I know there are many priorities at the moment, any ETA or when someone can look at this? 🙂

Another issue that many have reported:

In the Onboarding process, clicking on Select WiFi or Connect via Ethernet won't do anything.

We have 25 outstanding tickets as of today.

cc @KevinWassermann94 @pritamghanghas

@kashifpk It's OK - Spoke to Kevin about this and ofc it's all hands on deck at the moment. We have found a workaround for now (Seems to be working)

@WayneNebra what is the workaround. Is it latest app release. Iphone is not tested as I don't have one. But android was tested before release.

@pritamghanghas Spoke to Kevin about the workaround for now, for an updated list of phones > Phone Models


DiscordIntegration bot does not have permissions to use non-vanilla commands

LuckPerms Version: 4.1.54
Sponge Version: spongeforge-1.12.2-2611-7.1.0-BETA-2990
Hello, I am using a Discord bot from Chikachi/DiscordIntegration and I am having issues with permissions for non-vanilla commands. The fake player UUID is 828653ca-0185-43d4-b26d-620a7f016be6, as seen in the README of the repo.
lp user 828653ca-0185-43d4-b26d-620a7f016be6 info

[01:12:13] [pool-6-thread-1/INFO]: [LP] > User Info: Unknown
[01:12:13] [pool-6-thread-1/INFO]: [LP] - UUID: 828653ca-0185-43d4-b26d-620a7f016be6 (type: mojang)
[01:12:13] [pool-6-thread-1/INFO]: [LP] - Status: Offline
[01:12:13] [pool-6-thread-1/INFO]: [LP] - Primary Group: admin
[01:12:13] [pool-6-thread-1/INFO]: [LP] - Parent Groups:
[01:12:13] [pool-6-thread-1/INFO]: [LP] -    > default
[01:12:13] [pool-6-thread-1/INFO]: [LP] -    > admin
[01:12:13] [pool-6-thread-1/INFO]: [LP] - Contextual Data:
[01:12:13] [pool-6-thread-1/INFO]: [LP] -    Has contextual data: false
[01:12:13] [pool-6-thread-1/INFO]: [LP] -    Applicable contexts: None
[01:12:13] [pool-6-thread-1/INFO]: [LP] -    Prefix: None
[01:12:13] [pool-6-thread-1/INFO]: [LP] -    Suffix: None
[01:12:13] [pool-6-thread-1/INFO]: [LP] -    Meta: None

lp user 828653ca-0185-43d4-b26d-620a7f016be6 permission info

[01:14:10] [pool-6-thread-1/INFO]: [LP] 828653ca-0185-43d4-b26d-620a7f016be6's Permissions:  (page 1 of 1 - 1 entries)
[01:14:10] [pool-6-thread-1/INFO]: > * (true)

Despite giving the bot the * permission, commands from LuckPerms, Nucleus, and Prism all result in "You do not have permission to use this command!". Vanilla minecraft commands do indeed work, so I believe this is a result of LuckPerms rather than the bot. Also, this same setup has worked on a previous 1.12 spongeforge server with the exact same permissions (checked old H2 database).

See the discussion in #834


Use Fedora 40 as image-version

Build worked, push perms error, bypassing... Might want to investigate, though.


Write a first draft of a FHIR profile for our systems for full ELR

As a ReportStream user / dev I want to know what data we're storing in the FHIR bundle and how it's represented in FHIR.
AC:

The profile is based on https://www.hl7.org/fhir/us/core/StructureDefinition-us-core-observation-lab.html
All fields which have an hl7Field  from the base covid-19.schema have a representation in FHIR.
Document those fields in covid-19.schema that are not covered.
Record the relationship between the covid-19.schema columns and FHIR resources
The result is represented as JSON-Schema
Generate one or more examples of the corresponding FHIR JSON

@whytheplatypus says this needs to be re-groomed.

relates to #4469

@clediggins-usds @carlosfelix2 Do we still need this ticket, or have you two covered this in the tickets you wrote?

Closed while we figure out what we really want to do with profiles if anything.


ref(pkg/helm) replace  'pkg/helm' with 'pkg/helmx'

Lost of change, but diffs mostly consist of removing old pkg/helm code, moving pkg/helmx to pkg/helm, and dropping pkg/helmx

Hooray! Once it's merged, I'll start testing. Then I'll try to kill pkg/chart! Yay!


[Proposal] Getting coupon name, not code for display in invoice

https://github.com/laravel/cashier/blob/3f8b198f85431012d18f9645179bac35a03753e6/src/Invoice.php#L126-L136
Hi there,
I would like to suggest adding a method to the Invoice.php  along the lines of:
/**
     * Get the coupon name of the applied coupon code to the invoice.
     *
     * @return string|null
     */
    public function couponName()
    {
        if (isset($this->invoice->discount)) {
            return $this->invoice->discount->coupon->name?$this->invoice->discount->coupon->name:$this->invoice->discount->coupon->id;
        }
    }

That way one can access the coupon name, as it is intended by Stripe https://stripe.com/docs/api#discounts. I guess there are many reasons for this, first and foremost because one doesn't necessarily want to show the coupon code to the customer again, as it might be a coupon without limited use etc.
If interested I'd be happy to prep a pull request.
Best,
Tobias

You can obtain the coupon name like in the following example (would be used in receipt.blade.php):
{{ $invoice->discount->coupon->name }}

You can obtain the coupon name like in the following example (would be used in receipt.blade.php):
{{ $invoice->discount->coupon->name }}

I don't think we should add shortcuts like this to the main library. You can add a helper for this to your own codebase if you want.


File drag and drop not working under wayland

Describe the bug
Under wayland, File drag and drop is unrecognized. In particular, the following two interfaces are always empty:
&ctx.input().raw.hovered_files
&ctx.input().raw.dropped_files

To Reproduce
Use the egui::DroppedFile interface under wayland.
Expected behavior
Under wayland, raw.hovered_files and raw.dropped_files should be recognized and processed.
Under the web, the events are recognized.
Under Xwayland (via env -u WAYLAND_DISPLAY cargo run) the events are also recognized
Desktop (please complete the following information):

OS: 5.17.5-arch1-1
WM: sway version 1.7
Version: egui = "0.18.0" && eframe = "0.18.0"

Additional context
I tried forcing
let mut native_options = eframe::NativeOptions::default();
native_options.drag_and_drop_support = true;

with no luck.

Do you get a WindowEvent::DroppedFile in egui-winit/src/lib.rs?

How do I best test for this? I basically use the code provided here

Ok, I built it manually. This are prints of the Event under wayland:
Received Event: CursorMoved { device_id: DeviceId(Wayland(DeviceId)), position: PhysicalPosition { x: 75.5234375, y: 225.234375 }, modifiers: (empty) }
Received Event: CursorMoved { device_id: DeviceId(Wayland(DeviceId)), position: PhysicalPosition { x: 34.3203125, y:<PHONE_NUMBER>5 }, modifiers: (empty) }
Received Event: CursorLeft { device_id: DeviceId(Wayland(DeviceId)) }
Received Event: Focused(false)
Received Event: Focused(true)
Received Event: ModifiersChanged((empty))
Received Event: CursorEntered { device_id: DeviceId(Wayland(DeviceId)) }
Received Event: CursorMoved { device_id: DeviceId(Wayland(DeviceId)), position: PhysicalPosition { x:<PHONE_NUMBER>5, y:<PHONE_NUMBER>5 }, modifiers: (empty) }

and this under Xwayland:
Received Event: AxisMotion { device_id: DeviceId(X(DeviceId(2))), axis: 0, value: 968.0 }
Received Event: AxisMotion { device_id: DeviceId(X(DeviceId(2))), axis: 1, value: 781.0 }
Received Event: ModifiersChanged((empty))
Received Event: Focused(false)
Received Event: Focused(true)
Received Event: CursorMoved { device_id: DeviceId(X(DeviceId(2))), position: PhysicalPosition { x: 3.0, y: 221.0 }, modifiers: (empty) }
Received Event: HoveredFile("/home/timo/bitmap.png")
Received Event: DroppedFile("/home/timo/bitmap.png")
Received Event: HoveredFileCancelled
Received Event: ModifiersChanged((empty))
Received Event: Focused(false)
Received Event: Focused(true)
Received Event: CursorMoved { device_id: DeviceId(X(DeviceId(2))), position: PhysicalPosition { x: 3.0, y: 221.0 }, modifiers: (empty) }
Received Event: CursorMoved { device_id: DeviceId(X(DeviceId(2))), position: PhysicalPosition { x: 427.0, y: 173.0 }, modifiers: (empty) }
Received Event: AxisMotion { device_id: DeviceId(X(DeviceId(2))), axis: 0, value: 1392.0 }

So indeed, no WindowEvent::DroppedFile is emitted

Then that sounds like a bug in winit. I suggest making a simple drag-and-drop demo for winit (you can find some templates at https://github.com/rust-windowing/winit/tree/master/examples) and open an winit issue.

Thanks for the clarification that it's the responsibility of winit. There is an open issue in for exactly that: https://github.com/rust-windowing/winit/issues/1881
Currently, it's just not implemented yet. If it is resolved, we can mark this issue as resolved as well.

I think this is relevant
docs
drag and drop wayland


version bump to 232

Bugfix

transaction status transmission of txstatus "paid"

Maintenance

Shopware <IP_ADDRESS> compatibility

Notice

We're dropping compatibility with Shopware 6.2.* in a future release of this plugin

Bugfix

transaction status transmission of txstatus "paid"

Maintenance

Shopware <IP_ADDRESS> compatibility

Notice

We're dropping compatibility with Shopware 6.2.* in a future release of this plugin


[Docs] Replace image in README file

Current  #State:
See the white background between the man and woman in the image below that needs to be updated to a better version in the README file.

Desired State:
This is the desired image.

Replace with the image below.

Contributor Resources

Meshery documentation site
Meshery documentation source
Instructions for contributing to documentation

Hey @iambami can I work on this?

I have resolved the issue and create a PR


jQuery Dependency throws Uncaught Error during testing

I'm using Karma as a test runner, here is the output from the console to help debug.
.
I'm using the standalone build, v2.3.0. Works great in-app, but am unable to run tests due to this error.
Things I've tried that did not work:

adding external (CDN) jQuery script reference to the files that are loaded
installing through jquery as a dependency through bower, then through npm (neither)

Any help is appreciated.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/39464673-jquery-dependency-throws-uncaught-error-during-testing?utm_campaign=plugin&utm_content=tracker%2F1022469&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1022469&utm_medium=issues&utm_source=github).

This seems unrelated to this library.


rkt doesn't like spaces ¯_(ツ)_/¯

apparently it thinks we're trying to pull host image when we have --net host (space instead of a =)

LGTM


How to remove settings icon from player ?

could you please suggest some thoughts.

find R.id.app_video_clarity in DefaultMediaController.java,then you can remove it or let it gone

yeah, thank you much.its working fine


Resolve environment variables in the security configuration

Suggestion to enable resolution of environment variables while running the securityadmin.sh script as mentioned in the link: https://opensearch.org/docs/2.0/security-plugin/configuration/security-admin/ - using '-rev' parameter.

Hi @madhukarmmallia-plivo. Could you please describe what your usecase for this is, what you want to accomplish with this feature?

Hi @swoehrl-mw ,
I am trying to enable LDAP integration using the config.yml and as part of the configuration, I am passing in the LDAP credentials as environment variables with format - '${env.PASSWORD}' which is not being picked up. Securityadmin.sh script is throwing error when executed. Appreciate if there is any work around for the same.
Regards,
Madhukar

Hi @madhukarmmallia-plivo. Just so I understand correctly:

I am passing in the LDAP credentials as environment variables

You are using the spec.nodePools.env option to provide PASSWORD?
If so even if we set -rev it would not change anything as env is only set for the normal opensearch pods. securityadmin.sh is run in a separate job/pod that does not have any extra env set.
Could you not set the ldap password directly in the config.yml of the securityconfig? That is already stored in a secret so should be safe enough for a password. Even if you provide it via env you just move the problem of safely provisioning/storing sensitive information from the securityconfig secret to a secret containg the password.
If you are doing infrastructure-as-code and are storing the deployment yamls in a git repo you can use something like sops to encrypt it.

Could you not set the ldap password directly in the config.yml of the securityconfig? That is already stored in a secret so should be safe enough for a password. Even if you provide it via env you just move the problem of safely provisioning/storing sensitive information from the securityconfig secret to a secret containg the password.

what i would expect is that config.yml would be a configmap, possibly clear text, while the password would be in a secret retrieved at run time from a keyvault ...

Hi @madhukarmmallia-plivo . Could you please give an update if this is still a concern to you?

i think that this definitely remains a concern.
not only having passwords in text isn't a good idea, but also, regardless of how the password is passed , if an env variable isn't used in config.yaml, that password remains visible via the opensearch UI.

this can be easily addressed as described here, by using securityadmin.sh with the parameter --resolve-env-vars
https://forum.opensearch.org/t/using-environmental-variables-in-open-distro-security-plugin-configuration/1193/2?u=anubisg1

We would also appreciate this enhancement, it would help us to remove client id/secret for keycloak SSO from the configuration of opensearch cluster

+1 for this. We are leveraging Argo CD for OpenSearch cluster (i.e. resources) management. I'd actually like to avoid having to store plain text passwords in a ConfigMap committed into our Git repos. Using a secret instead is not quite an option due to its nature of storing Base64-encoded values. SealedSecrets might mitigate that, but usage in the context of a GitOps strategy is cumbersome as one would have to keep the unencoded file someplace else which is also not an option.


Ensure am11/pangyp not fetched via SSH

Pin am11/pangyp to the particular commit
Should fix the problem mentioned in:
https://github.com/sass/node-sass/commit/579baf322ca48f73b04a009b70220a6c0a3cbc15#commitcomment-11082041

I have this problem through the windows meteor build system on v3.0.0:
C:\Users\Mathew Hartley>  meteor publish-for-arch<EMAIL_ADDRESS>compileScss: updating npm dependencies -- node-sass, lodash, autoprefixer-core...
npm WARN package.json<EMAIL_ADDRESS>No description
npm WARN package.json<EMAIL_ADDRESS>No repository field.
npm WARN package.json<EMAIL_ADDRESS>No README data
npm ERR! Windows_NT 6.2.9200
npm ERR! argv "C:\\Users\\Mathew
Hartley\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.1.3\\mt-os.windows.x86_32\\dev_bundle\\bin\\\\node.exe"
"C:\\Users\\Mathew
Hartley\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.1.3\\mt-os.windows.x86_32\\dev_bundle\\bin\\node_modules\\npm\\bin\\npm-cli.js"
"install"
npm ERR! node v0.10.36
npm ERR! npm  v2.7.3
npm ERR! code ETARGET

npm ERR! notarget No compatible version found:
pangyp<EMAIL_ADDRESS>npm ERR! notarget Valid install targets:
npm ERR! notarget ["2.0.0","2.0.1","2.0.2","2.1.0"]
npm ERR! notarget
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of 'node-sass'
npm ERR! notarget

=> Errors while initializing project:

While building plugin `compileScss` in package `fourseven:scss`:
error: couldn't install npm packages from npm-shrinkwrap

That's interesting:
changing the pangyp line to "http" causes the same symptomps as reported by the original poster:
￼￼
https://gist.github.com/941c4f5c16f30d88efb2
https:// seems to work better.

Unsurprising. Github is https only.
On 7 May 2015 23:44, "Marcin Cieślak"<EMAIL_ADDRESS>wrote:

That's interesting:
changing the pangyp line to "http" causes the same symptomps as reported
by the original poster:
￼￼
https://gist.github.com/941c4f5c16f30d88efb2
https:// seems to work better.
—
Reply to this email directly or view it on GitHub
https://github.com/sass/node-sass/pull/931#issuecomment-99870670.

Thanks @saper! I would say, lets pursue this here: https://github.com/rvagg/pangyp/pull/5.
@rvagg, could you please publish pangyp vNext to npm after the merge? Thanks in anticipation. :gift:

CI seems pretty unhappy about this.

This doesn't appear to be a usable solution. We need to wait until it's solved upstream. Addressing this in #942 for now.


yolo_weights.h5 is different from yolo.h5

Thanks for u code!
when I run train.py without loading pretrained model，I get yolo_weights.h5 whose structure is different from yolo.h5.

What structure do you mean?

like this.

I think it doesn't matter, because only Conv and BN layers have weights that we need. Keras model.load_weights can handle this.


Allow library to be webpackable

Allows for the webpacking / browserifying of avrgirl-arduino
The main change is in package.json, but also updated the avr109 to support pre-reading the hex file with something other than fs
This is being used on the pagenodes hardware extension:  https://github.com/iceddev/hardware-extension/blob/master/src/lib/writeFirmware.js#L2

Coverage decreased (-0.4%) to 45.977% when pulling 01ddd060938c490c7c9bea75936a8274385d8b68 on monteslu:master into dde5d42d3c96421f8e3cbff64d45e3060e1a0f5c on noopkat:master.

@monteslu this is awesome!
One small catch before we merge this:
This week I upgraded avrgirl-arduino's node-serialport to version 4.x, which causes a couple of small incompatibilities with browser-serialport. I think a relatively straightforward PR to browser-serialport would fix this (ie. just getting the API's back in sync with each other), so I'll see if I can get this going for us 😁

@monteslu thank you again! 🎉  We're on a temp browser-serialport branch as the dependency for the moment, but I felt it was better to merge now. I'll add some info to the docs soon to let other folks know how to use this in the browser. 🙇


[DO NOT LAND] Properly use EOL on Windows when logging

This patch ensures proper EOL handling on Windows, but needs https://github.com/pinojs/pino/pull/327 to be merged and released to work.
Refs: https://github.com/joyeecheung/node-core-utils/pull/47

Update: https://github.com/pinojs/pino/pull/327 was merged, still need to wait for their next release.

Update: pino 4.9.0 was released containing my patch.


Poor contains performance

Steps to reproduce:
List the minimal actions needed to reproduce the behavior.

Actual behavior:
The query 2 (using equals) takes 0.3s while query 3 (using contains) takes 5.5s
Both yield the same results as I would expect
Environment info:

System info: Linux 5.10.0-19-amd64 x86_64
InfluxDB version: InfluxDB v2.5.1 (git: 5b6fdbf05d) build_date: 2022-11-02T18:06:28Z

I first encountered this problem of poor contains performance in 2020 along with other people but it sadly persists till this day.
One work-around is to replace contains with boolean expressions of multiple comparisons. E.g., replace
fields = ["F1", "F2"]
...
|> filter(fn: (r) => r._measurement == "M" and contains(value: r._field, set: fields))

with
|> filter(fn: (r) => r._measurement == "M" and (r._field == "F1" or r._field == "F2"))

Having said that, contains must exhibit same or better performance as this tedious boolean expression with multiple comparisons above, or not exist at all. contains poor performance defeats the purpose of its existence, in my opinion.

Indeed that's what I've been doing, though I simplified the case in the issue as it already happens with only one single element...!
And sometimes it is not possible (ie: contains from a variable list of options, in Grafana)


Training inf and nan

Hi, I am using the latest commit (eee5ce36242fa1de808a287a3cfe6055486e42b5) in the master branch, and I tried to train COCO dataset with four GPUs, with pytorch 1.3.0
See logs below
root@HDFS-Slave-01:/work/code/yolact_git# python train.py --config=yolact_resnet50_config --batch_size=96
Multiple GPUs detected! Turning off JIT.
Scaling parameters by 12.00 to account for a batch size of 96.
loading annotations into memory...
Done (t=17.48s)
creating index...
index created!
loading annotations into memory...
Done (t=0.60s)
creating index...
index created!
Initializing weights...
Begin training!
[  0]       0 || B: 6.872 | C: 22.219 | M: 10.292 | S: 65.478 | T: 104.861 || ETA: 30 days, 18:40:57 || timer: 39.889
[  0]      10 || B: 5.774 | C: 18.310 | M: 6.371 | S: 44.301 | T: 74.756 || ETA: 3 days, 23:40:39 || timer: 1.618
[  0]      20 || B: 5.730 | C: 15.922 | M: 6.166 | S: 24.768 | T: 52.586 || ETA: 2 days, 17:52:39 || timer: 1.614
[  0]      30 || B: 5.725 | C: 13.624 | M: 6.076 | S: 17.789 | T: 43.214 || ETA: 2 days, 11:05:50 || timer: 2.174
[  0]      40 || B: 5.592 | C: 11.825 | M: 5.970 | S: 14.158 | T: 37.545 || ETA: 2 days, 6:18:21 || timer: 1.583
[  0]      50 || B: 5.509 | C: 10.415 | M: 5.919 | S: 11.737 | T: 33.580 || ETA: 2 days, 4:28:42 || timer: 1.898
[  0]      60 || B: 5.422 | C: 9.391 | M: 5.852 | S: 10.065 | T: 30.730 || ETA: 2 days, 2:07:50 || timer: 1.851
[  0]      70 || B: 5.355 | C: 8.618 | M: 5.821 | S: 8.828 | T: 28.622 || ETA: 2 days, 1:02:20 || timer: 1.582
[  0]      80 || B: 5.288 | C: 8.018 | M: 5.788 | S: 7.888 | T: 26.983 || ETA: 2 days, 0:03:05 || timer: 1.935
[  0]      90 || B: 5.215 | C: 7.533 | M: 5.759 | S: 7.162 | T: 25.670 || ETA: 1 day, 23:11:19 || timer: 1.686
[  0]     100 || B: 5.138 | C: 6.994 | M: 5.684 | S: 5.983 | T: 23.798 || ETA: 1 day, 22:40:53 || timer: 1.966
[  0]     110 || B: 5.022 | C: 5.560 | M: 5.631 | S: 1.887 | T: 18.101 || ETA: 1 day, 22:03:22 || timer: 1.795
[  0]     120 || B: 4.899 | C: 4.587 | M: 5.580 | S: 1.682 | T: 16.747 || ETA: 1 day, 21:31:30 || timer: 1.684
[  0]     130 || B: 4.761 | C: 4.059 | M: 5.537 | S: 1.484 | T: 15.841 || ETA: 1 day, 21:08:44 || timer: 1.611
[  0]     140 || B: 4.678 | C: 3.780 | M: 5.514 | S: 1.299 | T: 15.272 || ETA: 1 day, 21:04:35 || timer: 1.660
[  0]     150 || B: 4.595 | C: 3.673 | M: 5.473 | S: 1.231 | T: 14.972 || ETA: 1 day, 20:52:10 || timer: 1.952
[  0]     160 || B: 4.525 | C: 3.803 | M: 5.459 | S: 1.214 | T: 15.001 || ETA: 1 day, 20:45:43 || timer: 1.831
[  0]     170 || B: 4.491 | C: 3.780 | M: 5.470 | S: 1.221 | T: 14.962 || ETA: 1 day, 20:26:25 || timer: 2.007
[  0]     180 || B: 4.444 | C: 3.763 | M: 5.467 | S: 1.221 | T: 14.895 || ETA: 1 day, 20:18:10 || timer: 1.700
[  0]     190 || B: 4.400 | C: 3.756 | M: 5.476 | S: 1.209 | T: 14.841 || ETA: 1 day, 20:04:57 || timer: 2.215
[  0]     200 || B: 4.366 | C: 3.805 | M: 5.494 | S: 1.214 | T: 14.879 || ETA: 1 day, 20:00:01 || timer: 1.852
[  0]     210 || B: 4.328 | C: 3.802 | M: 5.500 | S: 1.209 | T: 14.839 || ETA: 1 day, 19:49:29 || timer: 1.886
[  0]     220 || B: 4.282 | C: 3.798 | M: 5.501 | S: 1.211 | T: 14.792 || ETA: 1 day, 19:47:41 || timer: 1.716
[  0]     230 || B: 4.232 | C: 3.802 | M: 5.480 | S: 1.207 | T: 14.720 || ETA: 1 day, 19:33:02 || timer: 1.762
[  0]     240 || B: 4.177 | C: 3.807 | M: 5.457 | S: 1.215 | T: 14.657 || ETA: 1 day, 19:24:41 || timer: 1.769
[  0]     250 || B: 4.135 | C: 3.793 | M: 5.459 | S: 1.211 | T: 14.598 || ETA: 1 day, 19:23:43 || timer: 2.137
[  0]     260 || B: 4.069 | C: 3.578 | M: 5.425 | S: 1.183 | T: 14.255 || ETA: 1 day, 19:19:09 || timer: 1.905
[  0]     270 || B: 3.972 | C: 3.548 | M: 5.342 | S: 1.157 | T: 14.018 || ETA: 1 day, 19:10:36 || timer: 1.624
[  0]     280 || B: 3.888 | C: 3.520 | M: 5.262 | S: 1.145 | T: 13.815 || ETA: 1 day, 19:04:11 || timer: 1.836
[  0]     290 || B: 3.815 | C: 3.491 | M: 5.171 | S: 1.139 | T: 13.615 || ETA: 1 day, 18:56:37 || timer: 1.971
[  0]     300 || B: 3.738 | C: 3.401 | M: 5.097 | S: 1.112 | T: 13.348 || ETA: 1 day, 18:56:39 || timer: 1.989
[  0]     310 || B: 3.668 | C: 3.368 | M: 5.027 | S: 1.098 | T: 13.160 || ETA: 1 day, 18:49:17 || timer: 1.872
[  0]     320 || B: 3.605 | C: 3.328 | M: 4.949 | S: 1.073 | T: 12.956 || ETA: 1 day, 18:44:44 || timer: 1.844
[  0]     330 || B: 3.557 | C: 3.276 | M: 4.887 | S: 1.055 | T: 12.776 || ETA: 1 day, 18:39:40 || timer: 2.098
[  0]     340 || B: 3.517 | C: 3.237 | M: 4.845 | S: 1.047 | T: 12.646 || ETA: 1 day, 18:34:12 || timer: 1.657
[  0]     350 || B: 3.451 | C: 3.196 | M: 4.772 | S: 1.043 | T: 12.462 || ETA: 1 day, 18:24:13 || timer: 1.566
[  0]     360 || B: 3.426 | C: 3.148 | M: 4.739 | S: 1.027 | T: 12.341 || ETA: 1 day, 18:26:16 || timer: 1.976
[  0]     370 || B: 3.391 | C: 3.105 | M: 4.706 | S: 1.013 | T: 12.215 || ETA: 1 day, 18:17:22 || timer: 1.808
[  0]     380 || B: 3.365 | C: 3.059 | M: 4.687 | S: 1.004 | T: 12.116 || ETA: 1 day, 18:18:23 || timer: 1.665
[  0]     390 || B: 3.345 | C: 3.011 | M: 4.678 | S: 0.989 | T: 12.022 || ETA: 1 day, 18:09:35 || timer: 1.626
[  0]     400 || B: 3.325 | C: 2.967 | M: 4.649 | S: 0.973 | T: 11.914 || ETA: 1 day, 18:11:08 || timer: 1.645
[  0]     410 || B: 3.296 | C: 2.927 | M: 4.607 | S: 0.968 | T: 11.799 || ETA: 1 day, 18:01:48 || timer: 1.627
[  0]     420 || B: 3.289 | C: 2.891 | M: 4.593 | S: 0.961 | T: 11.734 || ETA: 1 day, 18:04:22 || timer: 1.762
[  0]     430 || B: 3.273 | C: 2.861 | M: 4.572 | S: 0.964 | T: 11.670 || ETA: 1 day, 18:01:27 || timer: 1.787
[  0]     440 || B: 3.258 | C: 2.815 | M: 4.547 | S: 0.948 | T: 11.567 || ETA: 1 day, 17:58:56 || timer: 1.716
[  0]     450 || B: 3.256 | C: 2.775 | M: 4.542 | S: 0.935 | T: 11.508 || ETA: 1 day, 17:56:44 || timer: 1.886
[  0]     460 || B: 3.248 | C: 2.755 | M: 4.519 | S: 0.937 | T: 11.458 || ETA: 1 day, 17:59:23 || timer: 1.641
[  0]     470 || B: 3.231 | C: 2.719 | M: 4.511 | S: 0.930 | T: 11.393 || ETA: 1 day, 17:57:11 || timer: 1.949
[  0]     480 || B: 3.234 | C: 2.682 | M: 4.498 | S: 0.920 | T: 11.333 || ETA: 1 day, 17:58:01 || timer: 1.969
[  0]     490 || B: 3.238 | C: 2.657 | M: 4.482 | S: 0.921 | T: 11.297 || ETA: 1 day, 17:55:02 || timer: 1.846
[  0]     500 || B: 3.243 | C: 2.632 | M: 4.473 | S: 0.919 | T: 11.268 || ETA: 1 day, 17:58:24 || timer: 1.619
[  0]     510 || B: 3.259 | C: 2.587 | M: 4.480 | S: 0.909 | T: 11.236 || ETA: 1 day, 17:56:39 || timer: 1.960
[  0]     520 || B: 3.244 | C: 2.549 | M: 4.470 | S: 0.909 | T: 11.173 || ETA: 1 day, 18:04:09 || timer: 1.751
[  0]     530 || B: 3.233 | C: 2.508 | M: 4.462 | S: 0.910 | T: 11.113 || ETA: 1 day, 17:55:18 || timer: 1.783
[  0]     540 || B: 3.224 | C: 2.471 | M: 4.457 | S: 0.919 | T: 11.071 || ETA: 1 day, 17:50:57 || timer: 1.956
[  0]     550 || B: 3.214 | C: 2.432 | M: 4.439 | S: 0.911 | T: 10.997 || ETA: 1 day, 17:46:56 || timer: 1.644
[  0]     560 || B: 3.192 | C: 2.396 | M: 4.418 | S: 0.907 | T: 10.914 || ETA: 1 day, 17:45:10 || timer: 2.157
[  0]     570 || B: 3.185 | C: 2.365 | M: 4.393 | S: 0.908 | T: 10.851 || ETA: 1 day, 17:45:48 || timer: 1.767
[  0]     580 || B: 3.166 | C: 2.350 | M: 4.377 | S: 0.911 | T: 10.804 || ETA: 1 day, 17:46:02 || timer: 1.605
[  0]     590 || B: 3.142 | C: 2.314 | M: 4.357 | S: 0.897 | T: 10.710 || ETA: 1 day, 17:45:47 || timer: 1.671
[  0]     600 || B: 3.116 | C: 2.273 | M: 4.329 | S: 0.899 | T: 10.617 || ETA: 1 day, 17:46:10 || timer: 1.613
[  0]     610 || B: 3.088 | C: 2.247 | M: 4.305 | S: 0.895 | T: 10.534 || ETA: 1 day, 17:45:04 || timer: 1.643
[  0]     620 || B: 3.078 | C: 2.219 | M: 4.288 | S: 0.883 | T: 10.467 || ETA: 1 day, 17:43:27 || timer: 1.601
[  0]     630 || B: 3.073 | C: 2.196 | M: 4.280 | S: 0.865 | T: 10.415 || ETA: 1 day, 17:42:06 || timer: 1.857
[  0]     640 || B: 3.062 | C: 2.178 | M: 4.269 | S: 0.847 | T: 10.356 || ETA: 1 day, 17:44:44 || timer: 1.804
[  0]     650 || B: 3.043 | C: 2.158 | M: 4.244 | S: 0.844 | T: 10.290 || ETA: 1 day, 17:39:18 || timer: 1.568
[  0]     660 || B: 3.043 | C: 2.141 | M: 4.237 | S: 0.836 | T: 10.257 || ETA: 1 day, 17:38:26 || timer: 1.930
[  0]     670 || B: 3.041 | C: 2.113 | M: 4.236 | S: 0.829 | T: 10.218 || ETA: 1 day, 17:36:09 || timer: 1.862
[  0]     680 || B: 3.041 | C: 2.079 | M: 4.234 | S: 0.811 | T: 10.165 || ETA: 1 day, 17:37:51 || timer: 1.778
[  0]     690 || B: 3.042 | C: 2.055 | M: 4.226 | S: 0.808 | T: 10.131 || ETA: 1 day, 17:35:31 || timer: 1.824
[  0]     700 || B: 3.023 | C: 2.043 | M: 4.216 | S: 0.811 | T: 10.092 || ETA: 1 day, 17:35:55 || timer: 1.636
[  0]     710 || B: 3.027 | C: 2.033 | M: 4.213 | S: 0.806 | T: 10.079 || ETA: 1 day, 17:34:29 || timer: 1.911
[  0]     720 || B: 3.031 | C: 2.028 | M: 4.206 | S: 0.808 | T: 10.074 || ETA: 1 day, 17:37:05 || timer: 1.632
[  0]     730 || B: 3.032 | C: 2.009 | M: 4.198 | S: 0.809 | T: 10.048 || ETA: 1 day, 17:35:38 || timer: 1.668
[  0]     740 || B: 3.021 | C: 1.994 | M: 4.175 | S: 0.808 | T: 9.998 || ETA: 1 day, 17:37:06 || timer: 1.733
[  0]     750 || B: 3.023 | C: 1.981 | M: 4.183 | S: 0.802 | T: 9.989 || ETA: 1 day, 17:35:04 || timer: 1.840
[  0]     760 || B: 3.013 | C: 1.958 | M: 4.177 | S: 0.797 | T: 9.944 || ETA: 1 day, 17:34:07 || timer: 1.703
[  0]     770 || B: 3.011 | C: 2.095 | M: 4.173 | S: 0.791 | T: 10.070 || ETA: 1 day, 17:33:14 || timer: 1.877
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
[  0]     780 || B:<PHONE_NUMBER>01.176 | C:<PHONE_NUMBER>2.783 | M: 8.589 | S:<PHONE_NUMBER>4973579552620544.000 | T:<PHONE_NUMBER>4973860872978432.000 || ETA: 1 day, 17:31:33 || timer: 1.876
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
[  0]     790 || B:<PHONE_NUMBER>01.176 | C:<PHONE_NUMBER>2.783 | M: 18.004 | S:<PHONE_NUMBER>2893461812281344.000 | T:<PHONE_NUMBER>2893745280122880.000 || ETA: 1 day, 17:28:32 || timer: 1.577
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
[  0]     800 || B:<PHONE_NUMBER>01.176 | C:<PHONE_NUMBER>2.783 | M: 27.277 | S:<PHONE_NUMBER>4036052683718656.000 | T:<PHONE_NUMBER>4036327561625600.000 || ETA: 1 day, 17:30:08 || timer: 1.535
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
[  0]     810 || B:<PHONE_NUMBER>01.176 | C:<PHONE_NUMBER>2.783 | M: 36.434 | S:<PHONE_NUMBER>26481968836640768.000 | T:<PHONE_NUMBER>26482243714547712.000 || ETA: 1 day, 17:33:02 || timer: 1.974
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
[  0]     820 || B:<PHONE_NUMBER>01.176 | C:<PHONE_NUMBER>2.783 | M: 45.753 | S:<PHONE_NUMBER>55506417989058560.000 | T:<PHONE_NUMBER>55506692866965504.000 || ETA: 1 day, 17:30:01 || timer: 1.904
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
[  0]     830 || B:<PHONE_NUMBER>01.176 | C:<PHONE_NUMBER>2.783 | M: 54.797 | S:<PHONE_NUMBER>66717338280525824.000 | T:<PHONE_NUMBER>66717613158432768.000 || ETA: 1 day, 17:29:55 || timer: 1.684
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
[  0]     840 || B:<PHONE_NUMBER>01.176 | C:<PHONE_NUMBER>2.783 | M: 63.979 | S:<PHONE_NUMBER>97487086551040000.000 | T:<PHONE_NUMBER>97487361428946944.000 || ETA: 1 day, 17:31:50 || timer: 1.893
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
[  0]     850 || B:<PHONE_NUMBER>01.176 | C:<PHONE_NUMBER>2.783 | M: 73.085 | S:<PHONE_NUMBER>97670565655347200.000 | T:<PHONE_NUMBER>97670840533254144.000 || ETA: 1 day, 17:30:57 || timer: 1.658
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan

Uh oh.
Does this happen every time you train? Typically this kind of thing only happens in the first epoch or two, so if you get past that it might be fine.
Also this may have to do with your batch size being super high, since the learning rate is automatically multiplied by 12 here so that might affect the instability.
Perhaps try reducing the batch size a little or changing the warmup_until parameter in the config (i.e., how long to keep the initial lr low for) to something much higher than 1000 (which I think it is right now). Seeing as the explosion happened close the the end of lr warmup, that might be your best bet.

Hi，I tried to train with 2 GPUs and batchsize=48, failed again.
But, so far batchsize=32 is ok:
CUDA_VISIBLE_DEVICES=5,6 python train.py --config=yolact_resnet50_config --batch_size=32
I just changed the batch size, without touching the warp_until parameter.
error logs below:
root@HDFS-Slave-01:/work/code/yolact_git# CUDA_VISIBLE_DEVICES=5,6 python train.py --config=yolact_resnet50_config --batch_size=48
Multiple GPUs detected! Turning off JIT.
Scaling parameters by 6.00 to account for a batch size of 48.
loading annotations into memory...
Done (t=18.21s)
creating index...
index created!
loading annotations into memory...
Done (t=0.66s)
creating index...
index created!
Initializing weights...
Begin training!
[  0]       0 || B: 6.326 | C: 27.412 | M: 6.040 | S: 65.752 | T: 105.530 || ETA: 27 days, 0:51:02 || timer: 17.519
[  0]      10 || B: 5.982 | C: 20.326 | M: 6.039 | S: 46.819 | T: 79.166 || ETA: 4 days, 8:06:50 || timer: 1.368
[  0]      20 || B: 5.712 | C: 17.446 | M: 5.869 | S: 27.535 | T: 56.561 || ETA: 3 days, 5:27:57 || timer: 1.281
[  0]      30 || B: 5.598 | C: 15.078 | M: 5.994 | S: 19.303 | T: 45.974 || ETA: 2 days, 20:22:37 || timer: 1.507
[  0]      40 || B: 5.470 | C: 13.464 | M: 6.011 | S: 15.002 | T: 39.947 || ETA: 2 days, 15:57:51 || timer: 1.332
[  0]      50 || B: 5.380 | C: 12.317 | M: 5.985 | S: 12.370 | T: 36.052 || ETA: 2 days, 12:57:29 || timer: 1.276
[  0]      60 || B: 5.305 | C: 11.411 | M: 5.949 | S: 10.584 | T: 33.250 || ETA: 2 days, 11:14:02 || timer: 1.469
[  0]      70 || B: 5.241 | C: 10.757 | M: 5.895 | S: 9.273 | T: 31.166 || ETA: 2 days, 9:57:38 || timer: 1.401
[  0]      80 || B: 5.191 | C: 10.288 | M: 5.858 | S: 8.302 | T: 29.639 || ETA: 2 days, 8:53:42 || timer: 1.336
[  0]      90 || B: 5.151 | C: 9.908 | M: 5.832 | S: 7.530 | T: 28.421 || ETA: 2 days, 8:01:22 || timer: 1.204
[  0]     100 || B: 5.104 | C: 9.413 | M: 5.805 | S: 6.321 | T: 26.643 || ETA: 2 days, 7:26:22 || timer: 1.312
[  0]     110 || B: 4.990 | C: 8.121 | M: 5.802 | S: 1.949 | T: 20.862 || ETA: 2 days, 6:54:05 || timer: 1.343
[  0]     120 || B: 4.907 | C: 7.348 | M: 5.785 | S: 1.441 | T: 19.481 || ETA: 2 days, 6:23:29 || timer: 1.266
[  0]     130 || B: 4.832 | C: 7.012 | M: 5.727 | S: 1.358 | T: 18.929 || ETA: 2 days, 6:05:09 || timer: 1.261
[  0]     140 || B: 4.793 | C: 6.829 | M: 5.689 | S: 1.325 | T: 18.636 || ETA: 2 days, 5:46:28 || timer: 1.240
[  0]     150 || B: 4.761 | C: 6.741 | M: 5.674 | S: 1.300 | T: 18.476 || ETA: 2 days, 5:27:03 || timer: 1.295
[  0]     160 || B: 4.773 | C: 6.637 | M: 5.675 | S: 1.380 | T: 18.464 || ETA: 2 days, 5:17:23 || timer: 1.295
[  0]     170 || B: 4.777 | C: 6.357 | M: 5.683 | S: 1.426 | T: 18.243 || ETA: 2 days, 5:06:25 || timer: 1.351
[  0]     180 || B: 4.751 | C: 6.135 | M: 5.675 | S: 1.443 | T: 18.004 || ETA: 2 days, 4:56:50 || timer: 1.376
[  0]     190 || B: 4.719 | C: 5.831 | M: 5.670 | S: 1.464 | T: 17.685 || ETA: 2 days, 4:45:15 || timer: 1.424
[  0]     200 || B: 4.686 | C: 5.522 | M: 5.665 | S: 1.472 | T: 17.344 || ETA: 2 days, 4:35:31 || timer: 1.332
[  0]     210 || B: 4.626 | C: 5.213 | M: 5.602 | S: 1.490 | T: 16.931 || ETA: 2 days, 4:23:36 || timer: 1.378
[  0]     220 || B: 4.585 | C: 4.925 | M: 5.590 | S: 1.497 | T: 16.596 || ETA: 2 days, 4:14:22 || timer: 1.255
[  0]     230 || B: 4.541 | C: 4.601 | M: 5.564 | S: 1.495 | T: 16.201 || ETA: 2 days, 4:06:46 || timer: 1.342
[  0]     240 || B: 4.495 | C: 4.287 | M: 5.537 | S: 1.482 | T: 15.801 || ETA: 2 days, 4:00:15 || timer: 1.340
[  0]     250 || B: 4.438 | C: 3.959 | M: 5.497 | S: 1.470 | T: 15.363 || ETA: 2 days, 3:57:12 || timer: 1.392
[  0]     260 || B: 4.336 | C: 3.725 | M: 5.446 | S: 1.362 | T: 14.869 || ETA: 2 days, 3:55:16 || timer: 1.379
[  0]     270 || B: 4.262 | C: 3.671 | M: 5.429 | S: 1.289 | T: 14.651 || ETA: 2 days, 3:55:31 || timer: 1.335
[  0]     280 || B: 4.202 | C: 3.540 | M: 5.406 | S: 1.227 | T: 14.376 || ETA: 2 days, 3:55:46 || timer: 1.388
[  0]     290 || B: 4.146 | C: 3.508 | M: 5.366 | S: 1.182 | T: 14.202 || ETA: 2 days, 3:56:11 || timer: 1.414
[  0]     300 || B: 4.077 | C: 3.488 | M: 5.335 | S: 1.163 | T: 14.064 || ETA: 2 days, 3:56:16 || timer: 1.305
[  0]     310 || B: 4.041 | C: 3.471 | M: 5.300 | S: 1.128 | T: 13.941 || ETA: 2 days, 3:54:41 || timer: 1.359
[  0]     320 || B: 3.993 | C: 3.434 | M: 5.265 | S: 1.108 | T: 13.800 || ETA: 2 days, 3:58:09 || timer: 1.414
[  0]     330 || B: 3.954 | C: 3.414 | M: 5.219 | S: 1.090 | T: 13.677 || ETA: 2 days, 3:56:59 || timer: 1.367
[  0]     340 || B: 3.905 | C: 3.382 | M: 5.185 | S: 1.068 | T: 13.539 || ETA: 2 days, 3:57:44 || timer: 1.356
[  0]     350 || B: 3.864 | C: 3.368 | M: 5.148 | S: 1.049 | T: 13.429 || ETA: 2 days, 3:59:08 || timer: 1.373
[  0]     360 || B: 3.813 | C: 3.346 | M: 5.110 | S: 1.033 | T: 13.301 || ETA: 2 days, 4:00:49 || timer: 1.551
[  0]     370 || B: 3.761 | C: 3.319 | M: 5.043 | S: 1.021 | T: 13.144 || ETA: 2 days, 4:00:06 || timer: 1.455
[  0]     380 || B: 3.714 | C: 3.303 | M: 4.989 | S: 1.041 | T: 13.046 || ETA: 2 days, 4:01:50 || timer: 1.557
[  0]     390 || B: 3.668 | C: 3.276 | M: 4.951 | S: 1.041 | T: 12.937 || ETA: 2 days, 4:02:18 || timer: 1.471
[  0]     400 || B: 3.623 | C: 3.259 | M: 4.896 | S: 1.036 | T: 12.814 || ETA: 2 days, 4:02:53 || timer: 1.268
[  0]     410 || B: 3.585 | C: 3.237 | M: 4.870 | S: 1.049 | T: 12.740 || ETA: 2 days, 4:06:38 || timer: 1.549
[  0]     420 || B: 3.557 | C: 3.227 | M: 4.834 | S: 1.037 | T: 12.655 || ETA: 2 days, 4:07:38 || timer: 1.446
[  0]     430 || B: 3.532 | C: 3.208 | M: 4.803 | S: 1.043 | T: 12.585 || ETA: 2 days, 4:09:50 || timer: 1.346
[  0]     440 || B: 3.487 | C: 3.209 | M: 4.752 | S: 1.049 | T: 12.497 || ETA: 2 days, 4:11:13 || timer: 1.388
[  0]     450 || B: 3.456 | C: 3.168 | M: 4.720 | S: 1.048 | T: 12.392 || ETA: 2 days, 4:13:00 || timer: 1.542
[  0]     460 || B: 3.445 | C: 3.152 | M: 4.691 | S: 1.045 | T: 12.333 || ETA: 2 days, 4:16:13 || timer: 1.491
[  0]     470 || B: 3.441 | C: 3.141 | M: 4.694 | S: 1.048 | T: 12.324 || ETA: 2 days, 4:19:39 || timer: 1.392
[  0]     480 || B: 3.435 | C: 3.107 | M: 4.684 | S: 1.020 | T: 12.246 || ETA: 2 days, 4:19:17 || timer: 1.375
[  0]     490 || B: 3.422 | C: 3.076 | M: 4.671 | S: 1.005 | T: 12.174 || ETA: 2 days, 4:23:11 || timer: 1.472
[  0]     500 || B: 3.438 | C: 3.037 | M: 4.675 | S: 0.982 | T: 12.132 || ETA: 2 days, 4:23:34 || timer: 1.506
[  0]     510 || B: 3.458 | C: 2.993 | M: 4.682 | S: 0.949 | T: 12.082 || ETA: 2 days, 4:26:35 || timer: 1.749
[  0]     520 || B: 3.451 | C: 2.964 | M: 4.671 | S: 0.945 | T: 12.031 || ETA: 2 days, 4:31:22 || timer: 1.364
[  0]     530 || B: 3.443 | C: 2.929 | M: 4.674 | S: 0.926 | T: 11.972 || ETA: 2 days, 4:33:06 || timer: 1.256
[  0]     540 || B: 3.446 | C: 2.875 | M: 4.671 | S: 0.914 | T: 11.905 || ETA: 2 days, 4:39:56 || timer: 1.655
[  0]     550 || B: 3.455 | C: 2.862 | M: 4.662 | S: 0.905 | T: 11.884 || ETA: 2 days, 4:40:43 || timer: 1.515
[  0]     560 || B: 3.455 | C: 2.826 | M: 4.665 | S: 0.892 | T: 11.838 || ETA: 2 days, 4:36:31 || timer: 1.381
[  0]     570 || B: 3.429 | C: 2.782 | M: 4.641 | S: 0.891 | T: 11.744 || ETA: 2 days, 4:31:51 || timer: 1.295
[  0]     580 || B: 3.408 | C: 2.759 | M: 4.620 | S: 0.901 | T: 11.687 || ETA: 2 days, 4:28:40 || timer: 1.315
[  0]     590 || B: 3.392 | C: 2.738 | M: 4.596 | S: 0.900 | T: 11.625 || ETA: 2 days, 4:24:53 || timer: 1.347
[  0]     600 || B: 3.372 | C: 2.695 | M: 4.570 | S: 0.898 | T: 11.535 || ETA: 2 days, 4:22:26 || timer: 1.512
[  0]     610 || B: 3.331 | C: 2.675 | M: 4.532 | S: 0.918 | T: 11.456 || ETA: 2 days, 4:18:59 || timer: 1.334
[  0]     620 || B: 3.325 | C: 2.630 | M: 4.528 | S: 0.902 | T: 11.385 || ETA: 2 days, 4:16:14 || timer: 1.257
[  0]     630 || B: 3.308 | C: 2.604 | M: 4.506 | S: 0.904 | T: 11.322 || ETA: 2 days, 4:12:57 || timer: 1.271
[  0]     640 || B: 3.301 | C: 2.592 | M: 4.493 | S: 0.895 | T: 11.281 || ETA: 2 days, 4:10:08 || timer: 1.253
[  0]     650 || B: 3.263 | C: 2.562 | M: 4.475 | S: 0.897 | T: 11.197 || ETA: 2 days, 4:07:18 || timer: 1.433
[  0]     660 || B: 3.239 | C: 2.530 | M: 4.448 | S: 0.900 | T: 11.117 || ETA: 2 days, 4:03:40 || timer: 1.329
[  0]     670 || B: 3.224 | C: 2.508 | M: 4.424 | S: 0.896 | T: 11.052 || ETA: 2 days, 4:00:19 || timer: 1.296
[  0]     680 || B: 3.213 | C: 2.466 | M: 4.425 | S: 0.886 | T: 10.990 || ETA: 2 days, 3:57:02 || timer: 1.305
[  0]     690 || B: 3.204 | C: 2.435 | M: 4.435 | S: 0.897 | T: 10.971 || ETA: 2 days, 3:55:27 || timer: 1.419
[  0]     700 || B: 3.194 | C: 2.420 | M: 4.433 | S: 0.907 | T: 10.953 || ETA: 2 days, 3:52:37 || timer: 1.215
[  0]     710 || B: 3.173 | C: 2.398 | M: 4.408 | S: 0.894 | T: 10.873 || ETA: 2 days, 3:49:41 || timer: 1.277
[  0]     720 || B: 3.156 | C: 2.376 | M: 4.385 | S: 0.906 | T: 10.823 || ETA: 2 days, 3:46:22 || timer: 1.256
[  0]     730 || B: 3.151 | C: 2.354 | M: 4.386 | S: 0.905 | T: 10.796 || ETA: 2 days, 3:44:22 || timer: 1.408
[  0]     740 || B: 3.120 | C: 2.325 | M: 4.367 | S: 0.911 | T: 10.724 || ETA: 2 days, 3:40:56 || timer: 1.381
[  0]     750 || B: 3.125 | C: 2.320 | M: 4.361 | S: 0.903 | T: 10.709 || ETA: 2 days, 3:38:30 || timer: 1.318
[  0]     760 || B: 3.121 | C: 2.325 | M: 4.351 | S: 0.895 | T: 10.691 || ETA: 2 days, 3:35:30 || timer: 1.446
[  0]     770 || B: 3.107 | C: 2.314 | M: 4.341 | S: 0.902 | T: 10.664 || ETA: 2 days, 3:32:20 || timer: 1.300
[  0]     780 || B: 3.120 | C: 2.299 | M: 4.335 | S: 0.901 | T: 10.655 || ETA: 2 days, 3:37:55 || timer: 1.267
[  0]     790 || B: 3.121 | C: 2.290 | M: 4.304 | S: 0.891 | T: 10.605 || ETA: 2 days, 3:34:54 || timer: 1.360
[  0]     800 || B: 3.107 | C: 2.272 | M: 4.285 | S: 0.881 | T: 10.545 || ETA: 2 days, 3:32:41 || timer: 1.339
[  0]     810 || B: 3.113 | C: 2.238 | M: 4.282 | S: 0.865 | T: 10.498 || ETA: 2 days, 3:30:29 || timer: 1.484
[  0]     820 || B: 3.109 | C: 2.226 | M: 4.280 | S: 0.852 | T: 10.467 || ETA: 2 days, 3:28:36 || timer: 1.240
[  0]     830 || B: 3.088 | C: 2.207 | M: 4.251 | S: 0.845 | T: 10.391 || ETA: 2 days, 3:26:06 || timer: 1.233
[  0]     840 || B: 3.120 | C: 2.199 | M: 4.274 | S: 0.831 | T: 10.424 || ETA: 2 days, 3:26:28 || timer: 1.393
[  0]     850 || B: 3.121 | C: 2.175 | M: 4.278 | S: 0.820 | T: 10.393 || ETA: 2 days, 3:24:07 || timer: 1.269
[  0]     860 || B: 3.111 | C: 2.154 | M: 4.286 | S: 0.814 | T: 10.365 || ETA: 2 days, 3:22:05 || timer: 1.379
[  0]     870 || B: 3.116 | C: 2.136 | M: 4.271 | S: 0.800 | T: 10.323 || ETA: 2 days, 3:19:34 || timer: 1.292
[  0]     880 || B: 3.099 | C: 2.127 | M: 4.262 | S: 0.799 | T: 10.286 || ETA: 2 days, 3:18:17 || timer: 1.415
[  0]     890 || B: 3.094 | C: 2.091 | M: 4.271 | S: 0.786 | T: 10.243 || ETA: 2 days, 3:16:26 || timer: 1.344
[  0]     900 || B: 3.105 | C: 2.076 | M: 4.293 | S: 0.784 | T: 10.258 || ETA: 2 days, 3:14:02 || timer: 1.334
[  0]     910 || B: 3.115 | C: 2.079 | M: 4.315 | S: 0.792 | T: 10.301 || ETA: 2 days, 3:13:12 || timer: 1.337
[  0]     920 || B: 3.115 | C: 2.063 | M: 4.317 | S: 0.795 | T: 10.289 || ETA: 2 days, 3:10:30 || timer: 1.264
[  0]     930 || B: 3.128 | C: 2.048 | M: 4.326 | S: 0.795 | T: 10.297 || ETA: 2 days, 3:09:32 || timer: 1.291
[  0]     940 || B: 3.120 | C: 2.028 | M: 4.315 | S: 0.795 | T: 10.258 || ETA: 2 days, 3:07:51 || timer: 1.288
[  0]     950 || B: 3.128 | C: 2.016 | M: 4.319 | S: 0.801 | T: 10.264 || ETA: 2 days, 3:06:38 || timer: 1.324
[  0]     960 || B: 3.130 | C: 2.004 | M: 4.317 | S: 0.810 | T: 10.260 || ETA: 2 days, 3:04:57 || timer: 1.511
[  0]     970 || B: 3.130 | C: 1.978 | M: 4.339 | S: 0.808 | T: 10.254 || ETA: 2 days, 3:03:12 || timer: 1.327
[  0]     980 || B: 3.141 | C: 1.984 | M: 4.351 | S: 0.806 | T: 10.282 || ETA: 2 days, 3:01:15 || timer: 1.371
[  0]     990 || B: 3.145 | C: 1.993 | M: 4.348 | S: 0.800 | T: 10.286 || ETA: 2 days, 2:59:48 || timer: 1.461
[  0]    1000 || B: 3.143 | C: 1.992 | M: 4.314 | S: 0.796 | T: 10.244 || ETA: 2 days, 2:22:11 || timer: 1.217
[  0]    1010 || B: 3.127 | C: 1.986 | M: 4.283 | S: 0.795 | T: 10.191 || ETA: 2 days, 2:21:44 || timer: 1.271
[  0]    1020 || B: 3.134 | C: 1.978 | M: 4.283 | S: 0.796 | T: 10.191 || ETA: 2 days, 2:22:32 || timer: 1.373
[  0]    1030 || B: 3.136 | C: 1.977 | M: 4.279 | S: 0.801 | T: 10.193 || ETA: 2 days, 2:21:54 || timer: 1.275
[  0]    1040 || B: 3.126 | C: 1.969 | M: 4.277 | S: 0.802 | T: 10.174 || ETA: 2 days, 2:21:43 || timer: 1.386
[  0]    1050 || B: 3.113 | C: 1.950 | M: 4.271 | S: 0.798 | T: 10.132 || ETA: 2 days, 2:22:42 || timer: 1.387
[  0]    1060 || B: 3.359 | C: 4.154 | M: 4.322 | S: 0.809 | T: 12.644 || ETA: 2 days, 2:22:57 || timer: 1.438
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
[  0]    1070 || B:<PHONE_NUMBER>40854940336128.000 | C:<PHONE_NUMBER>3204984324096.000 | M: 7.313 | S: 596456.118 | T:<PHONE_NUMBER>84059891105792.000 || ETA: 2 days, 2:21:36 || timer: 1.320
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan
Warning: Moving average ignored a value of inf
Warning: Moving average ignored a value of nan

Hi, training with batchsize=16 seems ok.
CUDA_VISIBLE_DEVICES=5,6 python train.py --config=yolact_resnet50_config --batch_size=16

Lowering the learning rate solved the issue for me, I hope I could help

So it does look like the issue was with the learning rate. If you want to still train with 4 GPUs I'd suggest something like 4 GPUs batch size 32.

Thanks @eslambakr @dbolya !


Feature/Volume Texture Node

This PR adds the Volume Texture node to coreBlackbird. This node allows sampling a vdb file from disk and uses the grid result in shading context.
Test file: Volume_Texture_Node.zip (Requires updated schema)

Hey @sergeneren
This looks awesome. Just wondering, would we also need an OSL shader of this also to mirror the SVM shader?

@dedoardo I've gone ahead and tested again with your review. It seems like the generated coordinates does not exactly give the world coordinate even after a transform. I've also failed to do it with a vector transform node, so it's probably another bug that needs to be fixed in a separate pr. Setting the position inside a sop create node with a sop level transform works correctly.


Simply format and license checks

This moves legacy source into an oldsrc root dir so that tools don't inspect it.

@justinethier branch protection rules need an actual approval result if you don't mind updating your review.


NPE: user

https://hastebin.com/nijozegifu.md

GD 1.5.2 is available to all, update, 1.4.7 is not supported anymore.


Expand support node range to include v17

Fixes #40

cc @clenfest for visibility, just going to land and release this today