Kingfisher.modulemap' not found

Check List
Thanks for considering to open an issue. Before you submit your issue, please confirm these boxes are checked.

[x] I have read the wiki page and cheat sheet, but there is no information I need.
[x] I have searched in existing issues, but did not find a same one.
[x] I want to report a problem instead of asking a question. It'd better to use kingfisher tag in Stack Overflow to ask a question.

Issue Description
What
:0: error: module map file '/Users/hetao/Library/Developer/Xcode/DerivedData/HetaoMath-bqogyzgnfgcqfafqjgrlaqedexfs/Build/Intermediates.noindex/ArchiveIntermediates/HetaoMath/BuildProductsPath/Release-iphoneos/Kingfisher/Kingfisher.modulemap' not found
Reproduce
Kingfisher updated from 6.0 to 7.0

It should not be an issue of Kingfisher. Maybe try cleaning your project/derived data or reinstalling the library.


Detecting vertical text with craft

Hello
CRAFT is doing great in detection of horizontal text but it is not able to detect the text in vertical orientation properly. Can you provide guidance/suggestions on how to achieve detection of vertical text with CRAFT? Will training with images with vertical orientation suffice?
Thanks

Have you tried rotating the image 90 degrees and redo a detection again, and obtain the union of bounding boxes in both original and rotated orientations?

No ,  I have not tried rotating the image. I will try this. Thank you for the suggestion

I have the same trouble, I'm trying to solve this, but it's to difficult to me... I think convolutional neural networks, its the best option to solve this problem...training word by word.


Add Command::absolute_path constructor

I'm not sure if it is the right approach to fix the #101 issue, but I would like to use the CARGO_BIN_EXE_... environment variable.
Additionally I'm not sure about naming. Logically it would be better to name the constructor from_absolute_path, but is somewhat too long and existing cargo_bin constructor did not use the use "from" naming either.

Could you help me understand how from_absolute_path is different than new?

@epage Looks like I totally missed the new method. :sweat_smile: For some reason I only noticed from_std and cargo_bin. I'm going to close this pull request, sorry for bothering.


API delegering - provider filter

Start API delegering
I am thinking of a scenario where there are many API providers in the list
In API provider filter I type 'Accenture' and I get 'Brønnøysundregistrene' in a red background
I type 'NAV' and I get 'NAV' in a red background
I am wondering what this red background is used for, since I get it for both positive and negative search result with this.

@allinox Guess this will be fixed in #81 ?

@anishastphen @jonkjetiloye
That purple outline is how the design-system displays focus. If you tab your way through the page you will see the same colored outline pop up on other components as well.
I assume that what is happening here is that the component is putting a focus on the first entry in the dropdown list, even if it isn't necessarily a match to your search. I'm not sure if this is intentional or not since we didn't actually make this component - we just use it as-is from the design system.
That said, I'm actually working on a new filter component (which is actually a filter component and not just a multi-select like this one) and once that is done, this select-component will be replaced with that one.

@anishastphen
Is this still an issue with the new filter component?

@allinox no this is not an issue, closing this


gnu-config: 2019-04-15 -> 2020-05-04

Motivation for this change
Update the config.sub and config.guess files that are replaced during some cross-compiles. This is specifically to support the Genode target that was added to lib/systems a few months ago. Note that the Genode toolchain and libc are still in an overlay and not in Nixpkgs.
This is a neat feature so I added a mention to the Nixpkgs manual.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Platform
Changed paths

x86_64-linux
6650

i686-linux
5816

aarch64-linux
29827

Ouch

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/redox-nix-was-where-does-the-cc-environment-variable-come-from/7784/10


Roll Flutter Engine from 36dccf7bb25c to 5f14067464c0 (3 revisions)

https://github.com/flutter/engine/compare/36dccf7bb25c...5f14067464c0
2024-07-11<EMAIL_ADDRESS>[Impeller] move more aiks tests to DL.  (flutter/engine#53792)
2024-07-11<EMAIL_ADDRESS>Roll Skia from ec4a1e03f7b0 to 004c81523e44 (23 revisions) (flutter/engine#53813)
2024-07-11<EMAIL_ADDRESS>Roll Skia from 2783ba54bf8e to ec4a1e03f7b0 (9 revisions) (flutter/engine#53797)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC bdero@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


[BUG] Incorrect positioning of 'Copy'

Fixes Issue
close #1049
Changes proposed

React Tooltip added
position is set to Top

Screenshots

@rupali-codes I have updated the color.

@rupali-codes Done

I have set the position to 'top'. I don't know why it is not behaving properly in some cases.

@rupali-codes Please merge this PR.

Its actually at the same position in popup, could you please place it at the top?

Then we are ready to go!

@kartikayasija please resolve the conflicts , and also try to do it as soon as possible or else i'll close this issue

Okay @k-deepak04

@kartikayasija any updates?

closing this, as being unresponded from a long time


Any chance of a pre-compiled 32-bit version for Windows?

My intended application to use D++ in, is currently built for 32-bit.
I followed the build instructions in the Documentation and it defaults to x64 debug. My attempts at switching to 32-bit architecture haven't worked thus far, and using CMake-Gui to generate a solution (which deviates from the recommended build procedure) appears to cause some unresolved external symbol issues. Perhaps because the packaged libraries are all x64?

Why do you need 32-bit windows? 32-bit CPUs haven't been manufactured for quite some time.

we have prebuilt 32 bit binaries if you need them, check the artifacts in the actions here for win32 x86: https://github.com/brainboxdotcc/DPP/actions
note you'll need 32 bit copies of the dependencies too e.g. opus.dll and friends. you can find a copy in our premade template. you may want to use that by the way:
https://github.com/brainboxdotcc/windows-bot-template
using the template will save you a lot of hassle.
let me know if this helps!

@SirObby - Good question. I don't 'require' 32-bit Windows, or the application to run in 32-bit as such. It's primarily a legacy matter. I plan to move to 64-bit eventually, just haven't gotten there yet.
@braindigitalis - This helped tremendously! After some wrangling between MT and MD builds which caused some heap corruption due to differing memory managers I now have Dpp starting in an application with my framework. However, for some reason Dpp doesn't seem to be as willing to connect when I run it in the framework-based application. I get the following output:
INFO: Auto Shard: Bot requires 1 shard
DEBUG: Auto Shard: 989 of 1000 session starts remaining
DEBUG: Starting with 1 shards...
DEBUG: Shards started.

But never the Logged in as <my bots name> print out, nor Shard 0/1 ready!. I don't get any error either. The framework I use (Cinder) sets up windows and OS environment handling mostly, so shouldn't prevent Dpp from doing its thing, but clearly something isn't quite right. Any ideas of where to start digging?

this happens if you have not set FD_SETSIZE big enough for the socket descriptors you get. does the framework you are adding it to do a lot of network or internet connectivity things?

just realised, were you using the release build of the template project? if so go grab it's 1.0.1 release I just made live and replace your dpp.dll and lib with the ones from that release. this'll fix it if that's the case. this was fixed days ago but the template bot wasn't re released with the fix, it was only in main branch.

The Framework (should) not do any network / internet stuff on start-up. It basically just acts as an intermediate layer between the OS and the C++ code enabling easier window handling and other typical application stuff.
I've been using the debug version thus far as I'm retooling my CMake back-end to allow for the planned 64-bit upgrade.
Just tested the 1.0.1 release (in both debug/release configurations) - same problem remains I'm afraid.
Once I've re-tooled my CMake stuff I can help confirm if the issue isn't present in the 64-bit variant for me.

Please give the 1.0.2 template release a try (released just now) :)

I wish I could say it worked like a charm, but now I get a crash after calling bot.start() O_o
Exception thrown at 0x0142B867 (dpp.dll) in SandBoxProject.exe: 0xC00000FD: Stack overflow (parameters: 0x00000000, 0x0B802000).
Unhandled exception at 0x0142B867 (dpp.dll) in SandBoxProject.exe: 0xC00000FD: Stack overflow (parameters: 0x00000000, 0x0B802000).

another day another go!
Looks like it was allocating too big an FD set for the stack.
Try the 1.0.3 release please: https://github.com/brainboxdotcc/windows-bot-template/releases/tag/1.0.3

The issue is also present on Win64

confirmed as working fine with win32 debug build using the windows-bot-template and the following test bot:
`#include <dpp/dpp.h>
#include
int main()
{
dpp::cluster bot("ODI2NTM1NDIyMzgxMzkxOTEz.YGN5GA.saEaizncFKtD1MxLvOhZ4nNpa2A");
bot.on_ready([&bot](const dpp::ready_t& event) {
    bot.log(dpp::ll_info, "Logged in as " + bot.me.username);
});

bot.on_message_create([&bot](const dpp::message_create_t& event) {
    if (event.msg->content == "!ping") {
        bot.message_create(dpp::message(event.msg->channel_id, "Pong!"));
    }
});

bot.on_log([](const dpp::log_t& event) {
    if (event.severity > dpp::ll_trace) {
        std::cout << dpp::utility::loglevel(event.severity) << ": " << event.message << "\n";
    }
});

bot.start(false);

return 0;

}
`
Output:
C:\Users\brain\source\repos\MyBot\Debug>MyBot.exe INFO: Auto Shard: Bot requires 1 shard DEBUG: Auto Shard: 992 of 1000 session starts remaining DEBUG: Starting with 1 shards... DEBUG: Connecting new session... INFO: Shard 0/1 ready! INFO: Logged in as D++ Test Bot DEBUG: Shards started.
Working great:

If you're still having issues with running this version have you considered raising the stack size for your project? (is this needed to be done for the DLL too?)
The default is only a meg, and i'm not sure what else you have running in your bot process...

Tested the latest version (1.0.3) in Win32 Debug and it worked! Thanks for the assistance and great work!
I'll confirm with the other versions when I finish retooling my CMake setup.

Confirmed that x86 and x64, and Debug / Release configurations all work in conjunction with the Cinder framework I'm building things in. Very much appreciate the prompt responses and help getting things up and running. I can't wait to leverage Dpp in my DJ/VJ application...!


Create a telegram bot notifying new commits and releases

I think it will be much better if we can have a telegram bot notifying in the group when there is a new commit or release

how about using this action?
https://github.com/appleboy/telegram-action
I think I can try to add this feature in the next few days.😁

I seem to have seen notify.yml.


Error: db error: ERROR: canceling statement due to statement timeout

Bug description
I set up a free tier project on supabase with no changes to the project. I then followed this guide. When I got to the step prisma migrate dev --name init, I received this error ...

I took a stab at running prisma migrate reset to see if that would fix anything and that seemed to run.

How to reproduce

Expected behavior
No response
Prisma information
datasource db {
  provider = “postgresql”
  url      = env(“DATABASE_URL”)
}

generator client {
  provider = “prisma-client-js”
}

model Post {
  id        Int     @id @default(autoincrement())
  title     String
  content   String?
  published Boolean @default(false)
  author    User?   @relation(fields: [authorId], references: [id])
  authorId  Int?
}

model User {
  id    Int     @id @default(autoincrement())
  email String  @unique
  name  String?
  posts Post[]
}

Environment & setup

OS: macOS
Database: PostgreSQL
Node.js version: v18.12.1

Prisma Version
Environment variables loaded from .env
prisma                  : 4.7.1
@prisma/client          : 4.7.1
Current platform        : darwin-arm64
Query Engine (Node-API) : libquery-engine 272861e07ab64f234d3ffc4094e32bd61775599c (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli 272861e07ab64f234d3ffc4094e32bd61775599c (at node_modules/@prisma/engines/migration-engine-darwin-arm64)
Introspection Engine    : introspection-core 272861e07ab64f234d3ffc4094e32bd61775599c (at node_modules/@prisma/engines/introspection-engine-darwin-arm64)
Format Binary           : prisma-fmt 272861e07ab64f234d3ffc4094e32bd61775599c (at node_modules/@prisma/engines/prisma-fmt-darwin-arm64)
Format Wasm             : @prisma/prisma-fmt-wasm 4.7.1-1.272861e07ab64f234d3ffc4094e32bd61775599c
Default Engines Hash    : 272861e07ab64f234d3ffc4094e32bd61775599c
Studio                  : 0.477.0

Which connection string from Supabase are you using in your app? (Should not influence things really, but just to clarify)
Generally this sounds more like a problem on the database side on Supabase. Prisma is just reporting what the database told it, and the steps you are following usually are expected to run without any problem.

this one ...

having this happen to me. Also with supabase and using their connection string. I've tried to do a migration using SQLite instead and it works

Prisma has been a pain to work with. Cannot work with elephatant sql and shows this when working with supabase. Too many issues to work around

I'm having exactly the same issue.
npx prisma migrate reset works as expected, as does npx prisma db seed.
Table reads are running fine, but migrations all fail with the error message described above.
Wondering if something has changed supebase end given I've not changed prisma version recently?

It looks like we're hitting the default supabase timeout of 2 minutes - from the supabase docs:

Additionally, all users are subject to a global limit of 2 minutes.

It looks like we're hitting the default supabase timeout of 2 minutes - from the supabase docs:

Additionally, all users are subject to a global limit of 2 minutes.

I think migration does not work on planetscale too.

Thanks for this research @samdigitalpanda, might be we should add this as a known error and give a better error message. It is really unfortunate that Supabase caps the query runtime like that.
Are you doing any super heavy things in your migration that are supposed to take 2+ minutes?

No I don't think so, adding two new tables with a couple of relations to other already existing tables. I did wonder if that could possibly be breaching the run time limit somehow and tried a migration with just adding a single column to a table and it still timed out.

I found this thread yesterday as I was running into the exact same issue with Supabase. I eventually just ran a prisma db push, which worked and then normal migrations started working beyond that. This isn't a fix, but it helped me out and hopefully will you all as well.

Ok, so a super simple migration that only adds a single column also times out after 2 minutes?
But you can talk normally to that database server via other tools or Prisma Client?
That is weird and maybe worth an investigation with Supabase support. Maybe something is wrong with that database.

Ok, so a super simple migration that only adds a single column also times out after 2 minutes? But you can talk normally to that database server via other tools or Prisma Client?
That is weird and maybe worth an investigation with Supabase support. Maybe something is wrong with that database.

Hmm thanks I will talk to them. I appreciate this is probably not a prisma issue. As someone said above the error message does seem to suggest that the error is coming from the DB provider and not prisma thanks to the 'Error: DB Error' line, so kudos for making that clear in your error messages at least!

I've since spun up a postgres docker container and run the same migrations which worked, giving further credence to this being a supabase issue rather than prisma. Thanks for your help all.

If I'm not mistaken db push will work  just fine on initial setup right?

I found this thread yesterday as I was running into the exact same issue with Supabase. I eventually just ran a prisma db push, which worked and then normal migrations started working beyond that. This isn't a fix, but it helped me out and hopefully will you all as well.

This did work and got my supabase instance in line with my prisma schema. Trying to run prisma migrate dev after this still fails with the same error though

Hi all, I too was having the same problem following the Mastering Nuxt 3 course.  I ran  a packet capture to see if there's any resets and who it's coming from. The resets seem to be normal resets (connection closing) but seems the connections closing may have been initiated by the client. I can't decrypt the capture so not sure exactly.  However, in doing some more research for this issue, a user named mmoreno, also having the same issue, found this where Prisma is suggesting that you must include a shadowDatabaseUrl for cloud hosted db's.  Then running a prisma db push followed by a prisma migrate dev worked for that user.  This seemed to work for me. Here's the steps I took:

ran prisma migrate reset (successfully)
added SHADOW_DATABASE_URL in my .env file and set it to the same value as DATABASE_URL (link says url and shadowDatabaseUrl should not be the same values)
added shadowDatabaseUrl = env("SHADOW_DATABASE_URL") to my shema.prisma datasource db config
ran prisma generate (successfully)
ran prisma db push (successfully)
ran prisma migrate dev (successfully)

Before doing this running migrate failed even after running db push.  So hopefully this helps.

pootytang you are the man. Thanks!!

@pootytang that worked for me too, thanks!!

Made everything like pootytang described, still fails to migrate

@pootytang Pootytang I did the same thing as you mentioned, and I am also doing the mastering nuxt 3 course, but for some reason, it will drop an error when trying to read the env. file, the only way it works is if I type my env key directly in the schema which is not the ideal way I guess, could it be because I am using windows and not a mac?
this is what i get: `Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Error: Prisma schema validation - (get-config wasm)
Error code: P1012
error: Environment variable not found: DATABASE_URL.
-->  schema.prisma:2
|
1 | datasource db {
2 |     url               = env("DATABASE_URL")
|
Validation Error Count: 1`

I'm pretty sure something broke on the supabase end here. I was using supabase + prisma without issue but just tried to do a migration and hit the issue here.
Some more data points:

I was getting Prisma timeouts trying to create a new dev migration
I opened the db in TablePlus and I see lots of orphaned shadow dbs

When I try and open one, I get this:

When I try and drop it, it times out

I tried adding the SHADOW_DATABASE_URL env var per https://github.com/prisma/prisma/issues/16853#issuecomment-1364180940 and I no longer get a timeout in Prisma. I can run migrate reset but when I try to create a new migration right after (even an empty one), I get:
Error: P3005

The database schema is not empty. Read more about how to baseline an existing production database: https://pris.ly/d/migrate-baseline

I'm pretty sure something broke on the supabase end here. I was using supabase + prisma without issue but just tried to do a migration and hit the issue here. Some more data points:

I was getting Prisma timeouts trying to create a new dev migration
I opened the db in TablePlus and I see lots of orphaned shadow dbs

When I try and open one, I get this:

When I try and drop it, it times out
I tried adding the SHADOW_DATABASE_URL env var per #16853 (comment) and I no longer get a timeout in Prisma. I can run migrate reset but when I try to create a new migration right after (even an empty one), I get:

Error: P3005

The database schema is not empty. Read more about how to baseline an existing production database: https://pris.ly/d/migrate-baseline

EDIT: I figured it out. Per the Prisma docs, the shadow URL should be the same URL but the db in the URL path should be postgres_shadow which they have you manually create in that same doc.

Thanks @gpeal.
This solution worked for me :partying_face:

Hi all, I too was having the same problem following the Mastering Nuxt 3 course. I ran a packet capture to see if there's any resets and who it's coming from. The resets seem to be normal resets (connection closing) but seems the connections closing may have been initiated by the client. I can't decrypt the capture so not sure exactly. However, in doing some more research for this issue, a user named mmoreno, also having the same issue, found this where Prisma is suggesting that you must include a shadowDatabaseUrl for cloud hosted db's. Then running a prisma db push followed by a prisma migrate dev worked for that user. This seemed to work for me. Here's the steps I took:

ran prisma migrate reset (successfully)
added SHADOW_DATABASE_URL in my .env file and set it to the same value as DATABASE_URL (link says url and shadowDatabaseUrl should not be the same values)
added shadowDatabaseUrl = env("SHADOW_DATABASE_URL") to my shema.prisma datasource db config
ran prisma generate (successfully)
ran prisma db push (successfully)
ran prisma migrate dev (successfully)

Before doing this running migrate failed even after running db push. So hopefully this helps.

That also worked for me! Thanks!

3.

Hi all, I too was having the same problem following the Mastering Nuxt 3 course. I ran a packet capture to see if there's any resets and who it's coming from. The resets seem to be normal resets (connection closing) but seems the connections closing may have been initiated by the client. I can't decrypt the capture so not sure exactly. However, in doing some more research for this issue, a user named mmoreno, also having the same issue, found this where Prisma is suggesting that you must include a shadowDatabaseUrl for cloud hosted db's. Then running a prisma db push followed by a prisma migrate dev worked for that user. This seemed to work for me. Here's the steps I took:

ran prisma migrate reset (successfully)
added SHADOW_DATABASE_URL in my .env file and set it to the same value as DATABASE_URL (link says url and shadowDatabaseUrl should not be the same values)
added shadowDatabaseUrl = env("SHADOW_DATABASE_URL") to my schema.prisma datasource db config
ran prisma generate (successfully)
ran prisma db push (successfully)
ran prisma migrate dev (successfully)

Before doing this running migrate failed even after running db push. So hopefully this helps.

After performing a reset, added the shadow database items then was able to perform a "migrate dev" without "db push".
Thanks : )

Hey everyone, we are investigating this together with Supabase. Here is our public issue for this: https://github.com/supabase/supabase/issues/11691
As long as the problem persists, you can indeed manually CREATE DATABASE a database in your existing project or create another free project and get its database - and then use that as an explicitly configured shadowDatabaseUrl in your Prisma schema file. Then all command should work successfully and as intended.

Problem confirmed by Supabase now: https://github.com/supabase/supabase/issues/11691#issuecomment-1398193618
Until this is figured out, please keep using the workaround of using a shadowDatabaseUrl with a separate project's database or one that you created manually with CREATE DATABASE.

Per the above referenced issue, this is what solved things for me: https://supabase.com/docs/guides/integrations/prisma#configuring-the-project-to-use-postgresql
Specifically, needed to connect to postgres and run CREATE DATABASE postgres_shadow;

I was working through these Supabase directions over the weekend and got stuck on the whole 'create a ghost database' thing. I couldn't find a spot within the project in the Supabase dashboard to create the ghost or a CLI to create it. I'm sure I'm missing something. Where can you go or what are the steps to create the ghost database?

Per the above referenced issue, this is what solved things for me: https://supabase.com/docs/guides/integrations/prisma#configuring-the-project-to-use-postgresql

Specifically, needed to connect to postgres and run CREATE DATABASE postgres_shadow;

I was working through these Supabase directions over the weekend and got stuck on the whole 'create a ghost database' thing. I couldn't find a spot within the project in the Supabase dashboard to create the ghost or a CLI to create it. I'm sure I'm missing something. Where can you go or what are the steps to create the ghost database?

The directions are referring to the PostgreSQL CLI psql. You'll just need to have that installed and then following the instructions should make more sense. If you are on a Mac you can get the CLI by installing Postgres with homebrew brew install postgresql or pretty easily by installing Postgres.app https://postgresapp.com/. If you're not on Mac, I'm not sure what the best resource would be but maybe someone else can chime in.

I couldn't find a spot within the project in the Supabase dashboard to create the ghost or a CLI to create it. I'm sure I'm missing something. Where can you go or what are the steps to create the ghost database?

Hi @trinkel - you should be able to run this command through the dashboard's SQL editor:
https://app.supabase.com/project/_/sql
Alternatively, if you prefer to install a standalone application to manage your database and can't use Postgres.app, pgAdmin is cross-platform and quite full featured.

You can also create a second project on Supabase and use the database of that project.
This will hopefully soon all be not necessary any more when the bug is fixed on Supabase side and all their databases have been updated. Afterwards we will also clean up their documentation on how to use Prisma.

@matthewatkins @pcnc : Thank you, thank you, thank you. That's exactly what I needed. I knew what to do, but I couldn't find where to do it.

Created a new Supabase project
Used SQL Editor in Supabase Dashboard to create a shadow database:

CREATE DATABASE postgres_shadow;

Added postgresql://postgres:[MY_PASSWORD]@db.[SUPABASE_HOST].supabase.co:5432/postgres_shadow to .env
Added shadowDatabaseUrl = env("SHADOW_DATABASE_URL") to schema.prisma
Ran npx prisma migrate dev --name init
Result: Your database is now in sync with your schema. (And some other stuff).

Thanks again for a quick and concise response.

As per Supabase, this should not be necessary any more as they fixed their PostgreSQL:
https://github.com/supabase/supabase/issues/11691#issuecomment-1404638760

@janpio: I saw that note and tried a new project last night. I got the same error. I figured it might not be ramped up yet. I'll try it again when I get a chance. Thanks!

@timrinkel we rolled out the new version today at around 7AM UTC.
It is necessary to pause/unpause your current project to be launched with the latest Postgres version.  I'll give it another shot over lunch (day-jobs always getting in the way of progress). Thanks!

@pcnc, @janpio:   So, lunch didn't happen. Sorry.
Anyway, I can confirm that after pausing/refreshing my project, merge dev was able to connect to the database. The shadow database still existed, but it was not referenced in the schema.
I also created a new project and merge dev connected to that as well.
So, I guess Ta-Das are in order. Thanks!

@matthewatkins @pcnc : Thank you, thank you, thank you. That's exactly what I needed. I knew what to do, but I couldn't find where to do it.

Created a new Supabase project

Used SQL Editor in Supabase Dashboard to create a shadow database:

CREATE DATABASE postgres_shadow;

Added postgresql://postgres:[MY_PASSWORD]@db.[SUPABASE_HOST].supabase.co:5432/postgres_shadow to .env

Added shadowDatabaseUrl = env("SHADOW_DATABASE_URL") to schema.prisma

Ran npx prisma migrate dev --name init

Result: Your database is now in sync with your schema. (And some other stuff).

Thanks again for a quick and concise response.

@trinkel @janpio This approach works for me as well :)

Manual definition of a shadow database should not be necessary for Supabase any more. If it is for you, please open a new issue. Thanks.

I have used Prisma against Supabase without creating a shadow db a couple of times since this was fixed and it has worked for me.

@janpio If I do not define a shadow db, I cannot create a migration locally. The schema is migrated correctly on Supabase, but there is no generated db in my local repo. Is that the normal behaviour or does it worth opening a new issue?  Cheers!

maybe create a dev branch and just db push dev

Absolutely not expected and worth creating an issue with as much info as possible. That sounds pretty weird.

Will do. Cheers @janpio

I am experiencing the same (or similar) error when working with Prisma + Supabase. I have a table with around 7M rows with multiple Decimal fields. I changed one of the field's type to @db.Decimal(10,2)  and ran prisma db push, this is the message I got:
• You are about to alter the column `price` on the `PricePoint` table, which contains 3841741 non-null values. The data in that column will be cast from `Decimal(65,30)` to `Decimal(10,2)`.
This is the error I got:
   0: sql_schema_connector::apply_migration::migration_step
           with step=AlterTable(AlterTable { table_ids: MigrationPair { previous: TableId(10), next: TableId(3) }, changes: [AlterColumn(AlterColumn { column_id: MigrationPair { previous: TableColumnId(196), next: TableColumnId(31) }, changes: ColumnChanges { type_change: Some(RiskyCast), changes: BitFlags<ColumnChange>(0b100, TypeChanged) }, type_change: Some(RiskyCast) })] })
             at schema-engine/connectors/sql-schema-connector/src/apply_migration.rs:21
   1: sql_schema_connector::apply_migration::apply_migration
             at schema-engine/connectors/sql-schema-connector/src/apply_migration.rs:10
   2: schema_core::state::SchemaPush
             at schema-engine/core/src/state.rs:433

Not sure if the fix on supabase side here is relevant since (if I understand correctly) is applied to DROP TABLE and I am altering fields here. Any help would be greatly appreciated 🙏

the error is related to the select query that you are making, try to figure out which argument makes your query slower, for example if you order data based on a column this will take time so try to index that column


Remove use of marked and dompurify dependencies

Contributes to https://github.com/rancher/dashboard/issues/8067
This PR removed the marked and dompurify dependencies.
These are used for markdown rendering, which is only used in the apps part of the UI - this has been removed from the navigation and is no longer supported.
This PR helps reduce the number of dependencies to maintain.

@mantis-toboggan-md Removed junk file and rebased to resolve conflict - can you re-approve


Checklist

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] Validation errors from the Linter extension for VS Code have all been fixed for this spec. (Note: for large, previously checked in specs, there will likely be many errors shown. Please contact our team so we can set a timeframe for fixing these errors if your PR is not going to address them).
[ ] The spec follows the patterns described in the Swagger good patterns document unless the service API makes this impossible.

@selvasingh  @markcowl @sphibbs @fearthecowboy @johanste @salameer @olydis #@kirthik - Please take a look at  this file https://github.com/selvasingh/azure-rest-api-specs/pull/2/files#diff-1791af80b13caa5e0bd8b977fc580618 in the PR

A general comment is that we are way to liberal with MUSTs. I'd prefer that we follow the guidelines in https://www.ietf.org/rfc/rfc2119.txt, which means that quite a few MUSTs should be SHOULD instead.


Remove panics from protocol

As discussed earlier, the error handling on the protocol side has to be improved as user input could cause a panic!. This is a work in progress, but I am pleased with the result and, if you agree, I will do the same for the write_* functions.

Looks good! I've started merging it but will take some time, a lot of changes in the upper layers. Stay tuned :)

Merged. Lots of generated code broken by this, still have to fix - opened an issue for that.


Minor issue - error 404

Hi - logged in today to get started with some projects and upon the Map page load, an error appeared at the top of the page that said:
404: We couldn't find path /dribbble-websites.jpg
I refreshed the page and it went away....but thought I would post here in case there was an issue.
Thanks and keep up the good work :)

I forgot to mention that the page seemed to load properly....everything was there and when I refreshed the error disappeared....

I don't think this is related to us as we do not have such a file associated with the map page (or any page other then maybe /news). This might have been left over from a previous site you where on.
Happy coding!


Issue in add torrent page checkboxes.

Describe the bug
There is an issue in add torrent page checkboxes that the state of the checkboxes (use as base path checkbox, sequential download checkbox, completed checkbox) does not change even on selecting/unselecting them.
To Reproduce
Steps to reproduce the behavior:

Go to 'home-screen' and click on add button at the right bottom.
Click on 'magnet/file icon'.
Try clicking on any of the checkboxes.
You will find no state change in checkboxes even after clicking on them.

Expected behavior
State of the checkbox should be changed clearly on selecting them.

hey can you assign this issue to me ?

Sure @Sudhanva-Nadiger assigning the issue to you.

hey i am unable to set the app locally in my system, the login to flood is not happening, i tried to join slack, but its asking tokens, can you help me set the app?

Hey @Sudhanva-Nadiger read this part in CONTRIBUTING.md for setup in your device :https://github.com/CCExtractor/Flood_Mobile/blob/master/CONTRIBUTING.md#login-into-app
I hope it will help you

I have been trying to set up the app from this instructions only
but its showing that the connection could not be verified !!

qbittorrent web ui

flood web ui

Error in console

http://<IP_ADDRESS>:3000/ Is this ip you use for flood web ui ?

@Sudhanva-Nadiger were you able to solve the issue you were facing while setting up the project? If not then this is what you need to do to resolve the issue.
Uninstall the older version of flood u have by using the command sudo npm uninstall -g flood and install the latest but not released version by using the command sudo npm i -g @jesec/flood

Yes it's looks like this. You are on right track.

Yes it's looks like this. You are on right track.

Yes it's looks like this. You are on right track.

Getting these error while running :(
Which version the app is using ?

Yes it's looks like this. You are on right track. Go ahead ...

There is multiple reasons for app:compileflutterbuilddebug this error . You can try solutions from this https://stackoverflow.com/questions/61930007/how-to-solve-execution-failed-for-task-appcompileflutterbuilddebug.

App is up and running !!! soon  i will add the required things !!! thanks guys for the help

@Akshatji800 the checkbox should remember the lastValue when its opened again ?

if you tap any of this checkbox then state of checkbox like select/unselect not reflected on the screen you have to fix this .

-okay I think I have solved the problem !! Take a look at it.
https://user-images.githubusercontent.com/93595710/212462379-5351b4d9-0898-41a3-9b3f-01b385c88b95.mp4

-okay I think I have solved the problem !! Take a look at it.
https://user-images.githubusercontent.com/93595710/212462379-5351b4d9-0898-41a3-9b3f-01b385c88b95.mp4

Should I send pull request?

Yes

Yes

Will do that tomo !!

@amitamrutiya2210 thanks for clearing @Sudhanva-Nadiger doubts and helping him in moving forward with the issue in mine absence. This really demonstrate the quality of a good open source contributor in you.

Thank you @Akshatji800


Try Typed DSPy

With the new typed dspy, you could replace
class PredictCategories(dspy.Signature):
    __doc__ = (
        f"Given the abstract of a scientific paper, "
        f"identify most relevant categories. "
        f"Valid categories are {CATEGORIES.keys()}"
    )
    title = dspy.InputField()
    abstract = dspy.InputField()
    categories = dspy.OutputField(
        desc="list of comma-separated categories",
        format=lambda x: ", ".join(x) if isinstance(x, list) else x,
    )
predict = dspy.ChainOfThought(PredictCategories)

with
from typing import Literal
class PredictCategories(dspy.Signature):
    """Given the abstract of a scientific paper, identify most relevant categories."""
    title = dspy.InputField()
    abstract = dspy.InputField()
    categories: list[Literal[*CATEGORIES.keys()]] = dspy.OutputField()
predict = dspy.functional.TypedChainOfThought(PredictCategories)

This will automatically ensure categories is a list of allowed values.
You can also use functional style:
from typing import Literal
from dspy.functional import cot

@cot
def predict_categories(title: str, abstract: str) -> list[Literal[*CATEGORIES.keys()]]:
    """Given the abstract of a scientific paper, identify most relevant categories."""

And then just call predict_categories(title="...", abstract="...") like you would predict :-)

Thanks! I'm gonna add it to the notebook.
Today I've take a look at the docs and a lot of thing has been added. Good job!
I have the impression that DSPy is moving really fast, is there a place (e.g. a changelog and roadmap in docs) that tracks past and future changes?

Even better would be just using enums and other nested pydantic objects. This works, but seems like there is no TypedChainOfThought yet.
class EmotionType(Enum):
    sadness = "sadness"
    joy = "joy"
    love = "love"
    anger = "anger"
    fear = "fear"
    surprise = "surprise"

class Emotion(dspy.Signature):
    sentence = dspy.InputField()
    sentiment: EmotionType = dspy.OutputField()

sentence = "i started feeling a little vulnerable when the giant spotlight started blinding me"

classify = TypedPredictor(Emotion)
classify(sentence=sentence)

Prediction(
    sentiment=<EmotionType.fear: 'fear'>
)

Also it should ideally just implicitly call the typed versions when annotations are available, and use function calling to generate structured outputs.

Even more elegant is using enums like so
class EmotionType(Enum):
    sadness = "sadness"
    joy = "joy"
    love = "love"
    anger = "anger"
    fear = "fear"
    surprise = "surprise"

class Emotion(dspy.Signature):
    sentence = dspy.InputField()
    sentiment: EmotionType = dspy.OutputField()

sentence = "i started feeling a little vulnerable when the giant spotlight started blinding me"

classify = TypedPredictor(Emotion)
classify(sentence=sentence)

Prediction(
    sentiment=<EmotionType.fear: 'fear'>
)

Enums are nice. But you'd still want a list I imagine, so
class Emotion(dspy.Signature):
    sentence = dspy.InputField()
    sentiment: list[EmotionType] = dspy.OutputField()
classify = TypedPredictor(Emotion)

or
@predictor
def classify(sentence: str) -> list[EmotionType]:
    pass

Thank you guys for the feedback. I wrote this simple classifier when the documentation of DSPy was incomplete. I will take a look at the new docs and try to implement new concepts in my future projects.


Development

Whoever accepts this, I would really appreciate it if you would accept my recent update push as well. Thanks!


[bal-carousel] - basic carousel with controls large transform the items not completly

The Basic Carousel with combination of Navigation "Large" causes not nice transforming.
On all Viewports the transformation is not full one item it calculations less and this leads to cutted logos at the end.
See videos :
desktop
https://user-images.githubusercontent.com/3681337/221572649-5f46ee10-0d49-4efa-b9d3-3a851e03387d.mov
tablet
https://user-images.githubusercontent.com/3681337/221572662-dd5b057c-a971-46a9-9e68-1bc17ceb5bf3.mov
mobile
https://user-images.githubusercontent.com/3681337/221572675-ff525b49-0285-477f-bc4e-2678f930ccea.mov

done with version 12.8.0
https://github.com/baloise-incubator/design-system/blob/next/packages/components/CHANGELOG.md#1280


Players joining the game don't see timers started from the command line

If a timer is started from the command line, players joining the game after the timer is started don't see the boss bar, even if they were in the game when the timer was started

Possibly fixed in 2.0-Dev3


comparing versions

Is this version of chromium (R64), the same as the version for raspberry pi(V R70)

Tried to use this version with R70 and does not work. Will there be any updates in the near future?


CGPathGetCurrentPoint: no current point emitted

When using PocketSVG, it continually emits 'no current point'.
I believe the problem is the following code is lines 576-578 in SVGEngine.mm
        CGPoint currentPoint = CGPathGetCurrentPoint(_path);
        CGFloat x = _operands[i+0] + (_cmd == 'm' ? currentPoint.x : 0);
        CGFloat y = _operands[i+1] + (_cmd == 'm' ? currentPoint.y : 0);

in pathDefinitionParser::appendMoveTo()
I believe the code should be changed to be:
        CGPoint currentPoint = _cmd == 'm' && !CGPathIsEmpty(_path) ? CGPathGetCurrentPoint(_path) : CGPointZero;
        CGFloat x = _operands[i+0] + currentPoint.x;
        CGFloat y = _operands[i+1] + currentPoint.y;

which will avoid calling CGPathGetCurrentPoint() when the path is most likely empty, and wouldn't be used anyway.

I think this is related to issue #133

Hi @robaho
Could you please provide steps to reproduce this issue?

I'm experiencing this issue as well. I can reproduce it with the following code and SVG:
let url = Bundle.main.url(forResource: "example", withExtension: "svg")
let svgLayer = SVGLayer(contentsOf: url!)

example.svg
<?xml version="1.0" encoding="UTF-8"?>
<svg xmlns="http://www.w3.org/2000/svg">
    <path d="M25,50 C25,100 150,100 150,50 Z" />
</svg>

I gave the PR that fixes it. And the previous poster has given the test case. I would suggest applying the PR.

On Aug 2, 2019, at 7:20 PM, Daniel Gibbs<EMAIL_ADDRESS>wrote:
I'm experiencing this issue as well. I can reproduce it with the following code and SVG:
let url = Bundle.main.url(forResource: "example", withExtension: "svg")
let svgLayer = SVGLayer(contentsOf: url!)
example.svg

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I don't see any PR originating from you @robaho

I’m sorry, I had a PR but didn’t submit it - the code changes I show in the comment are what is needed. I will see if I can resurrect the PR.

On Aug 7, 2019, at 6:48 PM, Fjölnir Ásgeirsson<EMAIL_ADDRESS>wrote:
I don't see any PR originating from you @robaho https://github.com/robaho
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/pocketsvg/PocketSVG/issues/150?email_source=notifications&email_token=ABF2U4OTIWTUYMIVG5KXYWLQDNNNLA5CNFSM4GX7SXS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD32ALOI#issuecomment-519308729, or mute the thread https://github.com/notifications/unsubscribe-auth/ABF2U4P5RDXTQX4FK3JUQGDQDNNNLANCNFSM4GX7SXSQ.

fixed via https://github.com/pocketsvg/PocketSVG/pull/173


Conflict with Cloudflare Warp

Describe the problem
When netbird connection is up, cloudflare warp is unable to connect
To Reproduce
Steps to reproduce the behavior:

Connect to netbird
Connect cloudflare warp
Cloudflare warp will fail the connection

Additional context
Only peers are added to netbird, not routing rules whatsoever

Hello @SooOverpowered do you have any specific DNS or network route configured in NetBird?

No I don't have any


changes : add support for controller 🎮

Details:
🆕Added the support for controllers.
Just works fine for my ps1 controller, but the key or button mappings may be different for different controllers, set it accordingly
after testing your controller, just change the event.button value accordingly.
You can test you controllers and get the button value from there easily as we have to use only 2 buttons or keys in the game.
Just visit hardwaretester(dot)com/gamepad to get your set of values.

Hello Mehmet,
I just added support for controllers to the game.
I've thoroughly tested it on my end, and it seems to be working smoothly. However, I understand the importance of ensuring compatibility across different setups.
I kindly request you to take a moment to review the pull request and test it on your end. If everything works fine, it's great.
If it encounters issues across different setups, I'll pull the request back.
Thank you.


INDFOR guns and body armor underpowered as compared to OPFOR (AK74vsAK47)

29ID Nelson: 09/25 EU Round 2
The AK74 vs AK47 matchup seemed unbalanced between INDFOR and OPFOR. INDFOR seemed to lose multiple 1 on 1 firefights despite their best efforts.
FNF_Ark_2020_09_23_ADSector_EU.ruha

Armor values are the same, will need good testing to see if there is actually a significant difference between the performance of RHS 7.62x39 and 5.45x39 that needs to be accounted for. Could always be that the OPFOR players outshot the INDFOR players. Need more data.


Nginx Config for Jigsaw + Wordpress as subfolder

Hi
Any idea how to have wordpress + jigsaw working together properly. So what I mean is having wordpress in subfolder under build_production.
Problem I found is handling 404 error between two. How do we accomplish that?

Mixing Jigsaw with Wordpress is probably not going to be a happy combination. But, in order for it to work, you'd have to alter your .htaccess file to exclude certain URLs from being rewritten, so they can get passed down directly to your Jigsaw folder and aren't handled by Wordpress. In order for this to work, you'd have to be willing to have all your Jigsaw pages accessible under some common path like /blog/....
If you want to go this route, this might be a good place to start: https://tanyanam.com/2012/12/09/wordpress-exclude-directory-from-url-rewrite-with-htaccess/

So this is what I have in nginx. It works fine.


"1 high severity vulnerability" related to npm during installation

Installing MagicMirror per https://docs.magicmirror.builders/getting-started/installation.html#manual-installation , I received the security warning below regarding the npm.
What changes are need in the installation procedure?
><EMAIL_ADDRESS>prepare
> [ -f node_modules/.bin/husky ] && husky install || echo no husky installed.

no husky installed.

added 265 packages, and audited 266 packages in 1m

20 packages are looking for funding
  run `npm fund` for details

1 high severity vulnerability

To address all issues, run:
  npm audit fix

Run `npm audit` for details.
npm notice
npm notice New minor version of npm available! 8.5.5 -> 8.11.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.11.0
npm notice Run npm install -g<EMAIL_ADDRESS>to update!
npm notice
pi@raspberrypi:~/MagicMirror $

please ignore the messages. nothing we can do about them. the audit fix causes more trouble than it fixes.
we haven't tested w npm 8.
next mm release  July 1

I request an update to the documentation to ignore the message, as most will apply the security fix.

See note on pull request ask why site does not reflect the merge?
https://github.com/MichMich/MagicMirror-Documentation/pull/116#issuecomment-1146006095

I dont know, maybe @MichMich has to trigger a deployment?

The automated build process seems to give an error. Not sure what causes this. Need to take a look at it after this weekend:
Wed Jun 1 12:45:01 CEST 2022

[Laravel Forge] Your server is running an older version of Ubuntu (16.04).
We recommend that you provision a new server and manually migrate your sites and resources.
You should not attempt to upgrade a server as this may have unintended side effects.

From github.com:MichMich/MagicMirror-Documentation
 * branch            master     -> FETCH_HEAD
Already up-to-date.
yarn install v1.21.1
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/4] Resolving packages...
[2/4] Fetching packages...
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The CPU architecture "x64" is incompatible with this module.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The CPU architecture "x64" is incompatible with this module.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The CPU architecture "x64" is incompatible with this module.
info<EMAIL_ADDRESS>The CPU architecture "x64" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The CPU architecture "x64" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The CPU architecture "x64" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The CPU architecture "x64" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The CPU architecture "x64" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The CPU architecture "x64" is incompatible with this module.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The CPU architecture "x64" is incompatible with this module.
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.

ℹ Compiling Client
ℹ Compiling Server
node:internal/crypto/hash:67
  this[kHandle] = new _Hash(algorithm, xofLen);
                  ^

Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:67:19)
    at Object.createHash (node:crypto:135:10)
    at module.exports (/usr/local/lib/node_modules/vuepress/node_modules/webpack/lib/util/createHash.js:135:53)
    at NormalModule._initBuildHash (/usr/local/lib/node_modules/vuepress/node_modules/webpack/lib/NormalModule.js:417:16)
    at handleParseError (/usr/local/lib/node_modules/vuepress/node_modules/webpack/lib/NormalModule.js:471:10)
    at /usr/local/lib/node_modules/vuepress/node_modules/webpack/lib/NormalModule.js:503:5
    at /usr/local/lib/node_modules/vuepress/node_modules/webpack/lib/NormalModule.js:358:12
    at /usr/local/lib/node_modules/vuepress/node_modules/loader-runner/lib/LoaderRunner.js:373:3
    at iterateNormalLoaders (/usr/local/lib/node_modules/vuepress/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
    at Array.<anonymous> (/usr/local/lib/node_modules/vuepress/node_modules/loader-runner/lib/LoaderRunner.js:205:4)
    at Storage.finished (/usr/local/lib/node_modules/vuepress/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:55:16)
    at /usr/local/lib/node_modules/vuepress/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:91:9
    at /usr/local/lib/node_modules/vuepress/node_modules/graceful-fs/graceful-fs.js:115:16
    at FSReqCallback.readFileAfterClose [as oncomplete] (node:internal/fs/read_file_context:68:3) {
  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

Node.js v17.7.2
HEAD is now at 7e775cf Merge pull request #116 from paulsp/patch-1

maybe this this is helpful ...

[Laravel Forge] Your server is running an older version of Ubuntu (16.04).
need to migrate the based test platform

2.21.0 adds new parms to install to turn off audit messages

there is new documentation with new release v2.21.0, should be closed @paulsp @MichMich


Pytorch version for conversion directly from Pytorch models

System information

MacOS
MACE version 1.0.4:
Python version(2.7 & 3.6):
Bazel version 0.13.0:

Describe the problem
Hi, I saw that MACE supports converting Pytorch models since version 1.0.0. I am wondering which Pytorch version (eg 1.0.1) should be used if I want to convert a Pytorch model directly, without converting to ONNX first. I did not find relevant information in the docs.
Thanks in advance.

Dear customer
At present, we do not recommend use this, First convert model to ONNX is better choose.
Thanks


'_debugSubtreeRelayoutRootAlreadyMarkedNeedsLayout()': is not true when I scroll the list quickly

I have a Listview and every item have a animation to open a view component
when i scroll the view and item rebuilder, i have a exception like this:
flutter: ══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════
flutter: The following assertion was thrown building Container(AlignmentDirectional.topStart, constraints:
flutter: BoxConstraints(0.0<=w<=Infinity, h=1.7), margin: EdgeInsets(8.0, 0.0, 8.0, 8.0)):
flutter: 'package:flutter/src/rendering/object.dart': Failed assertion: line 1408 pos 14:
flutter: '_debugSubtreeRelayoutRootAlreadyMarkedNeedsLayout()': is not true.
flutter:
flutter: Either the assertion indicates an error in the framework itself, or we should provide substantially
flutter: more information in this error message to help you determine and fix the underlying cause.
flutter: In either case, please report this assertion by filing a bug on GitHub:
flutter:   https://github.com/flutter/flutter/issues/new
flutter:
flutter: When the exception was thrown, this was the stack:
flutter: #2      RenderObject.markNeedsLayout (package:flutter/src/rendering/object.dart:1408:14)
flutter: #3      RenderBox.markNeedsLayout (package:flutter/src/rendering/box.dart:1852:11)
flutter: #4      RenderConstrainedBox.additionalConstraints= (package:flutter/src/rendering/proxy_box.dart:212:5)
flutter: #5      ConstrainedBox.updateRenderObject (package:flutter/src/widgets/basic.dart:1849:18)
flutter: #6      RenderObjectElement.update (package:flutter/src/widgets/framework.dart:4430:12)
flutter: #7      SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:4801:11)
flutter: #8      Element.updateChild (package:flutter/src/widgets/framework.dart:2729:15)
flutter: #9      SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:4803:14)
flutter: #10     Element.updateChild (package:flutter/src/widgets/framework.dart:2729:15)
flutter: #11     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:3689:16)
flutter: #12     Element.rebuild (package:flutter/src/widgets/framework.dart:3531:5)
flutter: #13     StatelessElement.update (package:flutter/src/widgets/framework.dart:3738:5)
flutter: #14     Element.updateChild (package:flutter/src/widgets/framework.dart:2729:15)
flutter: #15     SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:4803:14)
flutter: #16     Element.updateChild (package:flutter/src/widgets/framework.dart:2729:15)
flutter: #17     SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:4803:14)
flutter: #18     Element.updateChild (package:flutter/src/widgets/framework.dart:2729:15)
flutter: #19     SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:4803:14)
flutter: #20     Element.updateChild (package:flutter/src/widgets/framework.dart:2729:15)
flutter: #21     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:3689:16)
flutter: #22     Element.rebuild (package:flutter/src/widgets/framework.dart:3531:5)
flutter: #23     StatelessElement.update (package:flutter/src/widgets/framework.dart:3738:5)
flutter: #24     Element.updateChild (package:flutter/src/widgets/framework.dart:2729:15)
flutter: #25     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:3689:16)
flutter: #26     Element.rebuild (package:flutter/src/widgets/framework.dart:3531:5)
flutter: #27     BuildOwner.buildScope (package:flutter/src/widgets/framework.dart:2273:33)
flutter: #28     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding&PaintingBinding&SemanticsBinding&RendererBinding&WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:653:20)
flutter: #29     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding&PaintingBinding&SemanticsBinding&RendererBinding._handlePersistentFrameCallback (package:flutter/src/rendering/binding.dart:208:5)
flutter: #30     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:990:15)
flutter: #31     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:930:9)
flutter: #32     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding._handleDrawFrame (package:flutter/src/scheduler/binding.dart:842:5)
flutter: #33     _invoke (dart:ui/hooks.dart:128:13)
flutter: #34     _drawFrame (dart:ui/hooks.dart:117:3)
flutter: (elided 2 frames from class _AssertionError)

I do not know what happen, my code is very long, so .I don't have the convenience to provide  complete code
in my widget State class:
 @override
  void initState() {
    // TODO: implement initState
    super.initState();
    animationListener = () {
      setState(() {});
    };
    _initAnimation();
    if (widget.todo.showDetails) {
      show();
    }
  }

crash happen in  this line code:
 if (widget.todo.showDetails) {
      show();
    }

thanks for google flutter dev team

Please add the output of flutter doctor -v.
To investigate we would need a minimal runnable reproduction
as a single file so that we can just copy your code into lib/main.dart of a new project and run to reproduce.

Please consider asking support questions in one of the other channels listed at http://flutter.io/support .

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.

I also meet this problem. I find if I add WidgetSpan in a text, this assert must appear.


Attribution routes not showing all the info

Attribution index view:
http://localhost:8000/en-gb/funding/list/
Doesn't show funding sources which have not been approved. Page should contain two lists approved/not approved.
Steps:
Open project creation form
Add some funding sources and publications
Return to dashboard and visit attributions page
Publications are shown but not funding sources

We do tell the user in a message that their attribution will become visible once it is approved, so reprioritising this to a maybe for now.


Fix trying to render without dropped samples

This makes sure we don't loop over a None when doing viewitems.

Coverage increased (+0.05%) when pulling d9c2da22731d4b6e72bfe6c99e96d76f32e696a8 on squirrelo:render-with-missing-dropped-samples into 6614f27a540a6ee652b5e966979c06575056903c on biocore:master.

:+1:


[Question] Remote NFS Server

Question
Sorry if this isn't the right forum for this type of question but i've been searching all the docs and trying to understand if longhorn even supports this yet.
I have a external NFS server managed by different software and i'm trying to figure out how I could tell longhorn to dynamically mount a directory from that server and provide that to the cluster longhorn is running on.
I assumed longhorn filled in the gap here: https://kubernetes.io/docs/concepts/storage/storage-classes/#provisioner for NFS
to allow it to create something like this to be created
apiVersion: v1
kind: PersistentVolume
metadata:
  name: nfs
spec:
  capacity:
    storage: 1Mi
  accessModes:
    - ReadWriteMany
  nfs:
    server: MY_REMOTE_SERVER_HERE.com
    path: "/"

If this functionally does exist i'm having a hard time finding the documentation on it.  Any help or pointers on this would be greatly appreciated 🙏

This is not something longhorn supports, kubernetes natively supports nfs pv's
Here is an example on how to create an nfs volume:
https://matthewpalmer.net/kubernetes-app-developer/articles/kubernetes-volumes-example-nfs-persistent-volume.html
https://kubernetes.io/docs/concepts/storage/volumes/#nfs
Todo dynamic provisioning you would want to run an nfs provisioner on your nfs storage node that is capable of interacting with the kubernetes api server.

This is not something longhorn supports, kubernetes natively supports nfs pv's
Here is an example on how to create an nfs volume:
https://matthewpalmer.net/kubernetes-app-developer/articles/kubernetes-volumes-example-nfs-persistent-volume.html
https://kubernetes.io/docs/concepts/storage/volumes/#nfs
Todo dynamic provisioning you would want to run an nfs provisioner on your nfs storage node that is capable of interacting with the kubernetes api server.

It's a shame, this would be a great additional feature. Using both local storage and remote NFS for RWX PVCs...


Adding section on Violations Lib in README

Adding a section in the README on related projects.
Including my own project, Violations Lib, in that section.
The purpose being to promote my lib =)

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

Hi @tomasbjerre, sorry, but we're not able to promote related projects right now unless NullAway is directly built on them (like with Error Prone).


FIX fix array_range case for regress test

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

do not merge into 2.0 , it just for nereids


Display more useful error message

Without this, when user runs old tilt version the error is "unexpected
keyword argument discovery_strategy"

I am converting this to a draft. Unfortunately whenever you specify a tilt extension, tilt downloads the extension into a .tilt directory in your workspace. Some tilt extensions (like min_tilt_version) contain their own Tiltfiles. The vscode extension currently creates tasks for all files named Tiltfile in the workspace, so we'd have to couple this change with further vscode changes :(


substraTEE-client must accept a SHA256 hash of the WASM to be executed

Currently (M4), a WASM file has to be specified (or the default file is taken) and the SHA256 hash is calculated over the content.
The client is finally separated from the worker and has no access to his internals/files. Therefore, the user must be able to enter the SHA256 hash of the WASM code he/she wants to have executed in the TEE.

as of #61, WASM is no longer supported until we do #15


Remove timestamp printing from LeakReport

@curtisman @tcare @aneeshdk please review?

LGTM

LGTM

LGTM. Seems unlikely, but could any automation be affected by this?

Don't think so but we'll find out :) AFAIK, no automation or human relies on this data

'Human'. :D


Update to latest h5bp nginx settings

Maybe an update to match the latest update by h5bp

Sounds great! Would you like to put together a PR?

It'd be good to include actual expire rules https://github.com/h5bp/server-configs-nginx/blob/66d0c463e0a347563692e3df735512b3babdf959/h5bp/location/expires.conf

I can fix that up, give me some time i will get it together

💯

@KyleAMathews wanna put them in root or?

I think keeping it in a separate file and then just including it makes sense. Neater + easier to browse/maintain.

This is the structure i went for for now

👍


Iteration over maps and sets in the compiler can cause non-deterministic compilation

We have experienced dramatically different times in the execution of the same rules on the same data; for example, we've seen fluctuations from under 10 seconds to over 30 seconds when we repeatedly restart the JVM.  However, execution times seems to be more consistent when using the same JVM.  This leads me to suspect that differences in rulebase compilation are responsible for the fluctuation. Since Clara caches sessions, unless caching is disabled or the cache is manually cleared the rulebase used for a given set of rules will remain the same, but a JVM restart will force it to clear.
This sort of non-determinism poses problems for us in that

It makes it difficult to replicate and diagnose performance problems.
It could result in intermittent timeouts, although so far we have not had this problem.

I suggest that ensuring fully deterministic rulebase compilation would be desirable.  As a first step toward this, I suggest that when we iterate over sets and maps in rulebase compilation that these sets and maps be sorted, since iteration over the non-sorted versions of these data structures has undefined ordering.  I have an example of this type of change at https://github.com/WilliamParker/clara-rules/commit/18d8ac821489d82db2382c3ce8299f073d2ecebb
In that commit I changed mk-session* to include sorting of the productions with the following let binding:
productions (into (sorted-set-by (fn [a b]
                                           (< (-> a meta ::rule-load-order)
                                              (-> b meta ::rule-load-order))))
                          productions)

This uses the rule loader order metadata added in https://github.com/rbrush/clara-rules/issues/192
;;; The adding of rule loader order to the productions from issue 192
(map (fn [n production]
                                 (vary-meta production assoc ::rule-load-order (or n 0)))
                               (range))

The (or n 0) can actually just be changed to n; everything will have a defined rule order at this point since the seq returned by (range) will not have nil members.  Therefore the set of productions will be given a consistent ordering for all runs for constant ordering of the rules/rule sources passed to the compiler.
I suspect that there will be iterations over a BetaGraph [1] that will require ordering as well.  I'm still looking over the rest of the compiler, but I wanted to raise an issue here before getting too deep into this.
Note that I'm not saying that this will ensure fully deterministic compilation on its own, but it seems like a necessary step that will at least bring us closer to determinism.

https://github.com/rbrush/clara-rules/blob/0.11.1/src/main/clojure/clara/rules/schema.clj#L139

To clarify - iteration over hash based data structures could be impacted by the JVM instance restarting as well, even if we didn't cache.

I have submitted a pull request at https://github.com/rbrush/clara-rules/pull/201 with the following changes:

The sets of numbers in the value of the :forward-edges and :backward edges of [1] are now sorted.  I don't actually think this ends up mattering as currently implemented, since the usage at [2] just uses these sets as keys to select on the :id-to-node map and I made finding the set of common child nodes in add-conjunction [3] deterministic without it as discussed below. It just seems like a better practice and more resilient to future changes to make the BetaGraph [1] structure itself entirely sorted.
The maps in the empty-beta-graph are all now sorted.

In the case of :id-to-condition-node, I believe this matters because to-alpha-graph will use the order of :id-to-condition-node to determine the ordering of the children [4], which is reflected in the compiled alpha nodes [5], which determines the order that the engine will activate the children. [6]
I don't see anywhere where the others matter, but I just think that future modification will be easier/more reliably consistent if we can depend on the overall beta graph being sorted.

In add-conjunctions, when we have multiple common child IDs, I sorted the set of "common-children-ids" so that the "existing-id", if any, chosen will be deterministic even in any edge cases where the same (as in Clojure equal data structures) node occurs under multiple IDs.  This is more to be deterministic in case of any potential bugs here than for performance, although it could impact both, but it seems like something that should do no harm and could be helpful.
The map returned by compile-beta-graph [7] is now sorted.  This is needed so that the beta-roots in the rulebase will have a deterministic order [8], which is the order in which they will be left-activated by the empty token. [9]
I made changes to to-alpha-graph so that the alpha nodes will be returned in a deterministic order.  Specifically, conditions are sorted by the sum of the node-ids.  I don't see any obvious heuristics to improve performance here by choosing a particular ordering, so I just went with something simple that will be deterministic if node IDs are the same.  If anyone has thoughts on a useful heuristic for this I'd be interested.  This ordering matters because the ordering here is the ordering used in the alpha map of the rulebase [10], and for any given type this is the order in which the alpha nodes will be activated. [11, 12]  Note that there is still some nondeterminism in the alpha roots if the ordering of the ancestors can change, but that is not in the rule network so I'd consider that out of scope here. [13]
The set of productions will now be sorted by the load order.  This is necessary to make the node-id consistent, since we a stateful ID counter on a reduce over all productions. [14]

Remaining known sources of inconsistency:

As mentioned above, the alpha nodes for a single type are expected to be in a consistent order, but if a type C gets the alpha nodes for types A and B, then there may be some nondeterminism in whether the the nodes sequence that is doseq'ed over looks like

(concat type-a-alpha-nodes type-b-alpha-nodes)
;; or
(concat type-b-alpha-nodes type-a-alpha-nodes)
;; Note that this is just convenient notation.  I'm not saying this is actual code in Clara.

The type can be any arbitrary value, and there may not be any valid comparisons that can be made between types.  Since we cache on the types we probably wouldn't have much runtime cost
from some change here though, whatever that change might me.

There are various places in the engine where we iterate over return values from tuned-group-by [15]; this seq order will be nondeterministic.  Any ordering here would have to be considered carefully for possible overall performance degradation since it would impact runtimes after rulebase creation.

Other notes:

I believe node IDs should be consistent now, and have uncommented the test for node consistency.  However, I suspect that many potential sources of inconsistency would be consistent within the same JVM, so to more thoroughly test this would probably would require a test runner to start multiple JVMs and validate the node IDs.
Overall, while there is still significant variation from run to run, we had significantly increased consistency when I pulled the worst cases from our processing jobs and compared which subset of the data each case used and how long it took with these changes.

https://github.com/rbrush/clara-rules/blob/0.11.1/src/main/clojure/clara/rules/schema.clj#L139
https://github.com/rbrush/clara-rules/blob/0.11.1/src/main/clojure/clara/rules/compiler.clj#L1301
https://github.com/rbrush/clara-rules/blob/0.11.1/src/main/clojure/clara/rules/compiler.clj#L965
https://github.com/rbrush/clara-rules/blob/0.11.1/src/main/clojure/clara/rules/compiler.clj#L1340
https://github.com/rbrush/clara-rules/blob/0.11.1/src/main/clojure/clara/rules/compiler.clj#L1404
https://github.com/rbrush/clara-rules/blob/0.11.1/src/main/clojure/clara/rules/engine.cljc#L101
https://github.com/rbrush/clara-rules/blob/0.11.1/src/main/clojure/clara/rules/compiler.clj#L1263
https://github.com/rbrush/clara-rules/blob/0.11.1/src/main/clojure/clara/rules/compiler.clj#L1486
https://github.com/rbrush/clara-rules/blob/0.11.1/src/main/clojure/clara/rules/engine.cljc#L1220
https://github.com/rbrush/clara-rules/blob/0.11.1/src/main/clojure/clara/rules/compiler.clj#L1408
https://github.com/rbrush/clara-rules/blob/0.11.1/src/main/clojure/clara/rules/compiler.clj#L1460
https://github.com/rbrush/clara-rules/blob/0.11.1/src/main/clojure/clara/rules/engine.cljc#L165
https://github.com/rbrush/clara-rules/blob/0.11.1/src/main/clojure/clara/rules/compiler.clj#L1452
https://github.com/rbrush/clara-rules/blob/0.11.1/src/main/clojure/clara/rules/compiler.clj#L1098
https://github.com/rbrush/clara-rules/blob/0.11.1/src/main/clojure/clara/rules/platform.cljc#L10

I might be way off base here, but I seem to recall that we saw cache misses where we didn't expect them. We have a collect-sources function for the purposes of accepting both the namespaces where rules live, and dynamically generated rules which looks sorta like this:
(defn collect-sources
  [sources]
  (reduce (fn [res source]
            (cond
              (symbol? source)
              (concat res (com/load-rules source))

              (sequential? source)
              (into res source)

              :else
              (conj res source)))
          []
          sources))

When we dug in, we noticed that the orderings were off. In order to see a cache hit, we simply needed to do this:
(-> '[foo.bar foo.baz] (collect-sources) (set) (mk-session :cache true))

I made changes to to-alpha-graph so that the alpha nodes will be returned in a deterministic order. Specifically, conditions are sorted by the sum of the node-ids. I don't see any obvious heuristics to improve performance here by choosing a particular ordering, so I just went with something simple that will be deterministic if node IDs are the same. If anyone has thoughts on a useful heuristic for this I'd be interested. This ordering matters because the ordering here is the ordering used in the alpha map of the rulebase [10], and for any given type this is the order in which the alpha nodes will be activated. [11, 12] Note that there is still some nondeterminism in the alpha roots if the ordering of the ancestors can change, but that is not in the rule network so I'd consider that out of scope here. [13]

See https://github.com/rbrush/clara-rules/pull/201/files#r66372547

There are various places in the engine where we iterate over return values from tuned-group-by [15]; this seq order will be nondeterministic. Any ordering here would have to be considered carefully for possible overall performance degradation since it would impact runtimes after rulebase creation.

Outside of the scope of this issue for sure.  However, I want to make it a note that tuned-group-by could probably use java.util.LinkedHashMap to meet this need.  I'm pretty sure the insertion order of creating this map is deterministic.  Then once we have it, we always just seq over it (pretty sure on that).  LinkedHashMap meets this need dead on it looks like.  The overhead of the insertion order of it looks to be minimal too according to the docs.  Insertion is only slightly more expensive and iteration over the entries is potentially faster.  That's probably a good balance for our needs.

@WilliamParker apologies, I re-read your issue and realized I missed some of the context. When reading it seemed as if you might be conflating ordering with the check on the cache, but I understand the rationale now. Even if that had been the case, there are several good reasons for preferring what you're proposing. My response was more of a reaction to what seemed like missing benchmarks, but I realize now that these benchmarks are problematic to reliably produce for exactly the reason you've opened this issue.

No need for apologies @devn :)
FYI, the cached session had to have the same rules order to have a hit before https://github.com/rbrush/clara-rules/issues/157
Were your problems before that?  Also, the options have to be the same according to Clojure equality for there to be a cache hit.  So if you did something like
(mk-session rules-here :activation-group-sort-fn (fn-factory-returning-different-objects))

you'd always have misses since the function objects would not be equal.
I don't think these changes would change caching behavior since the caching is done in clara.rules.compiler/mk-session, while the highest level of these changes in the call stack is clara.rules.compiler/mk-session*.  mk-session calls mk-session* if there is a cache miss.

I don't think there is anything more to do here since https://github.com/rbrush/clara-rules/pull/201 has been merged.  Closing.


Newton-Raphson method. Make stable

Description: Make calculations (by N-R) stable and predictable on any grid configuration.
Current behavior: Falls or gives unrealistic results on the grid with PV-nodes.
Expected behavior: Stable results on PQ-only grids as well as PV/PQ grids

N-R stable version release candidate was added (https://github.com/ealux/PowerFlowCore/commit/4fbb0e84a83b39de633c4042426df232fa7066f7). Stable power flow on both PQ and PV/PQ grids.


fix(range): Range should be same for every subscriber

Description:
Range should be same for every subscriber.
We were mutating the start parameter that was passed in so the second subscriber was starting at the end of the first subscriber.
Related issue (if exists):
https://github.com/ReactiveX/rxjs/issues/3706

Coverage increased (+0.001%) to 96.63% when pulling e9b1e2ec86606bc49448eb3f0722c456f840a78b on bbonnet:fix-range into 537fe7db0248f05d21eef7fefc89f388c1491fe7 on ReactiveX:master.


Change query-string package version to 5.1.1

The query-string package uses an arrow function, which isn't available in IE11 (and therefore causes an error which prevents the page from loading). This doesn't work for <= IE10 as expected. HOWEVER, I'm not sure why this only affects the localhost version of the page (and to get it to work, I had to add localhost to my list of trusted sites). Thoughts?
(Also sorry, I forgot to prefix the branch name with emma/)

Can you commit into staging please.


Documentation

Hi,
Is there any docs available for the api methods?
I'm searching the api with "create address" and "create transaction" methods on board.

Hello?

Web3-Gear is just an Ethereum JSON-RPC adapter for users to use remix on Thor.

eth_getCode
eth_blockNumber
eth_estimateGas
eth_call
eth_sendTransaction
eth_getBalance
eth_getTransactionByHash
eth_getTransactionReceipt
eth_getBlockByHash
eth_getBlockByNumber
get_block
eth_newBlockFilter
eth_uninstallFilter
eth_getFilterChanges
eth_getLogs
debug_traceTransaction
debug_storageRangeAt


RLS: 0.20.3

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

I switched back to the github URL, since we can't upload the source dist to PyPI yet. The source file was generated and uploaded by me to Github, so it shouldn't change if / when the release page is edited.

And something went wrong with the SHA. It seems like anything like https://github.com/pandas-dev/pandas/archive/v0.20.3/*.tar.gz will redirect to Github's autogenerated version :/

Will the builders automatically follow redirects? https://github.com/pandas-dev/pandas/releases/download/v0.20.3/pandas-0.20.3.tar.gz is the canonical URL, but that redirects to a signed S3 url like https://github-production-release-asset-2e65be.s3.amazonaws.com/858127/dae238e0-630f-11e7-9dee-8a8b6bc83308?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20170707%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20170707T175302Z&X-Amz-Expires=300&X-Amz-Signature=ef124e8706b1cdae026a0b417555fd062eacf5aa4ab97d512883222e7631b153&X-Amz-SignedHeaders=host&actor_id=1312546&response-content-disposition=attachment%3B%20filename%3Dpandas-0.20.3.tar.gz&response-content-type=application%2Foctet-stream


add spatial program for reading/writing ascii, netCDF and HDF5

generalize LPET, LPT, OPT and tide scripts to use csv, netCDF4 or HDF5
add utilities for parsing date strings in form "time-units since yyyy-mm-dd hh:mm:ss"
will add similar generalized script for calculating tidal currents and displacements

Codecov Report

Merging #25 into master will increase coverage by 1.84%.
The diff coverage is 82.71%.

@@            Coverage Diff             @@
##           master      #25      +/-   ##
==========================================
+ Coverage   65.25%   67.09%   +1.84%
==========================================
  Files          38       40       +2
  Lines        3275     3550     +275
  Branches      297      336      +39
==========================================
+ Hits         2137     2382     +245
- Misses       1047     1058      +11
- Partials       91      110      +19

Flag
Coverage Δ

#unittests
67.09% <82.71%> (+1.84%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pyTMD/read_netcdf_model.py
7.14% <0.00%> (-0.09%)
:arrow_down:

pyTMD/utilities.py
41.66% <27.27%> (-13.21%)
:arrow_down:

pyTMD/read_FES_model.py
44.03% <33.33%> (-0.31%)
:arrow_down:

pyTMD/read_tide_model.py
38.33% <52.63%> (+13.38%)
:arrow_up:

pyTMD/time.py
59.72% <75.00%> (-20.56%)
:arrow_down:

pyTMD/spatial.py
81.54% <81.54%> (ø)

test/test_spatial.py
96.77% <96.77%> (ø)

pyTMD/calc_astrol_longitudes.py
72.50% <100.00%> (ø)

pyTMD/compute_tide_corrections.py
23.80% <100.00%> (-0.80%)
:arrow_down:

pyTMD/convert_calendar_decimal.py
88.09% <100.00%> (-0.55%)
:arrow_down:

... and 18 more

Continue to review full report at Codecov.

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