API to fetch the folder data

The developer will accept the folder name as input and send the folder data has its response

backend pythonClient server server simulation

convert everything to base64 then sending it over as a list.
React has an option to decode a file automatically.


python310Packages.starline: 0.1.5 -> 0.2.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.starline is: "Unofficial python library for StarLine API"
meta.homepage for python310Packages.starline is: "https://github.com/Anonym-tsk/starline"
meta.changelog for python310Packages.starline is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 0.2.0 with grep in /nix/store/am9a7dnagnp9sv19nv5s245f972lnkjk-python3.10-starline-0.2.0
found 0.2.0 in filename of file in /nix/store/am9a7dnagnp9sv19nv5s245f972lnkjk-python3.10-starline-0.2.0

Rebuild report (if merged into master) (click to expand)

5 total rebuild path(s)

3 package rebuild(s)

3 x86_64-linux rebuild(s)
2 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
home-assistant-component-tests.starline
python310Packages.starline
python39Packages.starline

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/am9a7dnagnp9sv19nv5s245f972lnkjk-python3.10-starline-0.2.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.starline https://github.com/r-ryantm/nixpkgs/archive/05566cf6d78c24da803d9657bfcc6acf9bd1f240.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/am9a7dnagnp9sv19nv5s245f972lnkjk-python3.10-starline-0.2.0
ls -la /nix/store/am9a7dnagnp9sv19nv5s245f972lnkjk-python3.10-starline-0.2.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

home-assistant-component-tests.starline
python310Packages.starline
python39Packages.starline

Maintainer pings
cc @dotlambda for testing.

duplicate of #173298


Internal caching layer documented?

Short of reverse engineering HMR, or the "cache" option, is the internal caching layer used by incremental builds documented anywhere?

Currently not, sorry.

K. Thx.


Add (or switch to) frameworks instead of static libraries

It would be nice if AudioKit.xcodeproj built AudioKit.framework. This would make initial setup easier, removing the need for the explicit user header search paths setting, for example. It would also provide compatibility with Carthage.

Agreed, and its been on our to-do list for a while and we're hoping for the next release.  I'll leave this issue open until it can be done.

Adding @megastep as a watcher on this one

To jump on this, CocoaPods does automatically build a framework (I think) when using use_frameworks! in your Podfile (in Swift, I'm not sure how it works in Obj-C). Instead of doing #import "AKFoundation.h" in a Bridging Header, you have to do import AudioKit in whatever file you want to use AudioKit classes in, including the AudioKit.swift helper.

Unless CocoaPods actually creates the appropriate targets in the Xcode config, I kinda doubt how this actually works. But in any case, this is definitely something we want to add sooner rather than later (probably after 2.3).

+1

+1

Working on it!

great to know, please let me know when is fully supported

This would be great, I found the setup and linking the hardest part of getting started with AK as a new Apple developer.

Trust me, working very hard on this and I can already tell you its basically working, just a few more things left.  Probably right around Christmas, but don't hold me to that.

Happy New Year !

Hi, yeah, Happy New Year. Looking to have it as a framework by January 21st!

When might it be a pure Swift framework?  I recall hearing some changes (every year) at WWDC, but Swift 2.1 so far produces very compact code reading and the compiler helps you do things that increase stability dramatically.

You'll never want it to be pure Swift if you want it as fast as possible.  Next release is a lot swiftier though.  I think you'll like it a lot.  I'm just building a few example apps now to smooth out initial kinks.

@aura great news !!

I realize it cannot be all Swift. But Swift is very expressive, so the more examples the quicker to solutions. Some involved know AudioKit extremely well.
I’ve chosen to abstract myself away from the core and use Swift as much as possible to focus on a long list of educational apps that teach some of the mathematics involved in sound synthesis and psychoacoustics, etc.

On Jan 5, 2016, at 9:46 PM, Aurelius Prochazka<EMAIL_ADDRESS>wrote:
You'll never want it to be pure Swift if you want it as fast as possible. Next release is a lot swiftier though. I think you'll like it a lot. I'm just building a few example apps now to smooth out initial kinks.
—
Reply to this email directly or view it on GitHub https://github.com/audiokit/AudioKit/issues/227#issuecomment-169203959.

I understand and agree, stay tuned.

I think this will suffice for easy framework installation....  https://vimeo.com/152398360


Cannot Compile: private NodeModel NewNode(double x, double y)

I am stuck on the updates from the earlier versions.
From the Getting Started example:
    private NodeModel NewNode(double x, double y)
This line does not compile. I get the following error:
Error	CS0246	The type or namespace name 'Point' could not be found (are you missing a using directive or an assembly reference?)
What am I doing wrong?

Hello,
You're just missing a using statement, VS should helo you with that normally.
Its using Blazor.Diagrams.Core.Geometry.

Thanks! That fixed the problem.
It would be useful to include that in the Getting Started guide, especially given the fact that Intellisense doesn't actually work in VS 2019 Preview.

I will do that as soon as I can, thank you.


Menu icon takes too much space on OSX

My Setup

Operating System: Mac OSX 10.9
App Version: Rocket.Chat+ 2.12.1

[x] I have tested with the latest version
[x] I can simulate the issue easily

Description

First let me thank you for removing the counter for 0 unread messages which was introduced in 2.12.0. While the counter no longer shows up, the space is still reserved

Current Behavior

Additional space right of the menu bar icon is added
Expected Behavior

No additional space should be added

In the right side is no space.
In the right side you should see the „private“ message count

@HappyTobi But if there are no private messages, the space should go away. This it at least the behaviour of many other applications which display a counter. For example https://github.com/ViennaRSS/vienna-rss

@HappyTobi  Thanks a lot for fixing this!


Package update request: Unity3D: 5.5.3xf1 -> 5.6.1xf1

Relevant default.nix:
https://github.com/NixOS/nixpkgs/blob/2090aa4f65e860567af03cb3b7aa042df7168ead/pkgs/development/tools/unity3d/default.nix
Binary/package download available here:
https://forum.unity3d.com/threads/unity-on-linux-release-notes-and-known-issues.350256/#post-3070212

I haven't tested it extensively, only verified that it runs (it still required some fixes in how we add RPATHs).


Client Allocation Request for: 郑州不忘初衷网络科技有限公司

Client Allocation Questions
Core Information

Name: phoenix
Website / Social Media:

wechat:18515015560
slack:lucas556
github:https://github.com/lucas556

Region: Greater China
DataCap Requested: 15TiB
Addresses to be Notarized: f1yogtfjjwsg2dpkjry2wepe3hxi3ap6mhimu6juq
Notary Requested: ozhtdong

This is the third application. The previous application information is in:
[/issues/294]  [/issues/783]
这是第三次申请;前两次的申请在这里:
[/issues/294]  [/issues/783]

the last allocation record:  https://github.com/lucas556/Filecoin_Datacap/raw/main/Filecoin_Datacap_2.xlsx
这是上次的分配记录: https://github.com/lucas556/Filecoin_Datacap/raw/main/Filecoin_Datacap_2.xlsx

now Datacap has 630G remaining; it is not enough for us to continue to store.;this time we have prepared at least 30TiB of data.
现在还剩余630G的datacap,不够完成一次的数据存储;这次我们准备了至少30TIB的数据.

@galen-mcandrew I can't approve the request.
Could you check the issue if there is any problem when it was created?

@galen-mcandrew I can't approve the request. Could you check the issue if there is any problem when it was created?

@galen-mcandrew ths

@ozhtdong @galen-mcandrew Can you continue?

@ozhtdong Can you continue?

There‘s some problem about the system. I can not approve this one now.

There‘s some problem about the system. I can not approve this one now.

ths,Can this problem be fixed?

@ozhtdong Can it be approved now?

No. The same problem still exists.

No. The same problem still exists.

Can it be solved?

@ozhtdong I am opening a new issue, please try, thank you.


Message function statuses

The message only considers a status of 404. It would be awesome if we could also return other statuses when successful. For exemple, when a user has created in a dashboard, we don't necessarily want to redirect. I'd like to return a status of 201 in order to show a success toast

You can set any status code with message: https://superforms.vercel.app/concepts/messages#the-message-helper

But it will only return a status of 200 on sucess
export function message<T extends AnyZodObject, M>(
  form: Validation<T, M>,
  message: M,
  options?: {
    status?: number;
    valid?: boolean;
  }
) {
  form.message = message;
  if (options?.valid !== undefined) form.valid = options.valid;

  const failure =
    (options?.status !== undefined && options.status >= 400) || !form.valid;

  return failure ? fail(options?.status ?? 400, { form }) : { form };
}

I want to return a status of 201 when a user was created successfully.
Maybe something like:
...
return failure ? fail(options?.status ?? 400, { form }) : { form, status: options?.status };

I think that's a SvelteKit thing, if you look at the examples, there is no obvious way of returning a different status code than 200 from a form action unless using fail: https://kit.svelte.dev/docs/form-actions#anatomy-of-an-action

You can of course add any message to form yourself, and return extra data with { form, status } at the end.


MB-7957 fix bug that bails if one payment request send fails

Description
Currently the PaymentRequestReviewedProcessor will bail out if a single payment request fails to process for any reason. However, the intention is that it should log errors and move on to the next payment request for processing.
Reviewer Notes
The test TestProcessLockedReviewedPaymentRequest seems to have become flakey for me locally. Would appreciate more 👀  on it.
Setup
Make sure GEX_URL is not set in your environment
change line 601 of cmd/milmove/serve.go to return a non 200 status
			w.WriteHeader(http.StatusForbidden)

setup the server
make db_dev_e2e_populate
make server_run

go run ./cmd/milmove-tasks process-edis --send-to-syncada

select * from payment_requests where status = 'EDI_ERROR';

There should be 2 marked as EDI_ERROR instead of just one in the e2e data.
Code Review Verification Steps

[X] Code follows the guidelines for Logging
[X] Request review from a member of a different team.
[X] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Warnings

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

  Generated by :no_entry_sign: dangerJS against cc1585271de3b44b15029be1bd33493cdd113f3e

The locked PR test is also failing for me intermittently. We should not knowingly commit a flakey test, so I would vote to remove it if we can't get it to pass reliably. I remain skeptical of the value of this test. It feels like we're testing Postgres functionality.

The locked PR test is also failing for me intermittently. We should not knowingly commit a flakey test, so I would vote to remove it if we can't get it to pass reliably. I remain skeptical of the value of this test. It feels like we're testing Postgres functionality.

I agree with not committing knowingly intermittent tests. At this point I'm going to take it out and file a story to review our concurrent handling


.env not loading without .env.local

Based on the current logic of selecting the appropriate env file, the .env is not getting loaded unless I also have a .env.local.
Line 36 here does not include .env:
https://github.com/pantheon-systems/wordpress-composer-managed/blob/3318e7eb07b996b69ea4da801808092bd6225a05/config/application.php#L34-L36
So when load() is called on line 40, $env_files contains only .env.pantheon, even though the conditional is checking that .env exists prior to loading:
https://github.com/pantheon-systems/wordpress-composer-managed/blob/3318e7eb07b996b69ea4da801808092bd6225a05/config/application.php#L38-L40
Expected
.env should load whether or not .env.local exists.
Actual
.env is only loaded if .env.local exists.
Solution
This is likely as simple as adding .env at index 0 in the array on line 36. That would more closely match how Bedrock handles it:
https://github.com/roots/bedrock/blob/master/config/application.php#L32-L43
I'm happy to submit a PR! just wanted to open a discussion first.

@jessedyck Good catch! A PR would be awesome, but otherwise we'll write up a fix for this next week.

This was now released to the actual upstream.


Add shellstorm.py to the repository

Aim

The shellstorm.py script is a Python script that interacts with the ShellStorm API to search and download shellcodes.

Details

It provides various command-line arguments to specify search keywords, extract raw shellcode bytes, and write the selected shellcode to a file.

Do I want to work on this:

[X]  Yes
[ ] No

Go Ahead @sabhisharma-ise


Return actual image height and width

Currently we just return the maxHeight and maxWidth version properties without checking the actual resized image (because this takes time). If someone needs it, they can submit a PR and make it optional for those who needs it.

Closed in 9d0ae8e


Can't run supabase db start

Describe the bug
I am facing a database is not healthy error when running supabase cli for the first time.
To Reproduce

Download the cli
run npx supabase init
run npx supabase db start
See "database is not healthy"

Expected behavior
The database should start as I am just choosing to run that portion atm.
Desktop (please complete the following information):

OS: [e.g. iOS] Windows 10
Version of CLI : 1.86.1
Version of Node.js : v18.12.1
Version of Docker: Docker version 24.0.5, build ced0996

Additional context
Here are the logs having run with debug flag.
npx supabase db start --debug
Supabase CLI 1.86.1
2023/08/17 08:57:37 Sent Header: Host [api.moby.localhost]
2023/08/17 08:57:37 Sent Header: User-Agent [Docker-Client/unknown-version (windows)]
2023/08/17 08:57:37 Send Done
2023/08/17 08:57:37 Recv First Byte
2023/08/17 08:57:37 Sent Header: Host [api.moby.localhost]
2023/08/17 08:57:37 Sent Header: User-Agent [Docker-Client/unknown-version (windows)]
2023/08/17 08:57:37 Send Done
2023/08/17 08:57:37 Recv First Byte
2023/08/17 08:57:37 Sent Header: Host [api.moby.localhost]
2023/08/17 08:57:37 Sent Header: User-Agent [Docker-Client/unknown-version (windows)]
2023/08/17 08:57:37 Send Done
2023/08/17 08:57:37 Recv First Byte
Starting database...
2023/08/17 08:57:37 Sent Header: Host [api.moby.localhost]
2023/08/17 08:57:37 Sent Header: User-Agent [Docker-Client/unknown-version (windows)]
2023/08/17 08:57:37 Send Done
2023/08/17 08:57:37 Recv First Byte
2023/08/17 08:57:37 Sent Header: Host [api.moby.localhost]
2023/08/17 08:57:37 Sent Header: User-Agent [Docker-Client/unknown-version (windows)]
2023/08/17 08:57:37 Sent Header: Content-Length [306]
2023/08/17 08:57:37 Sent Header: Content-Type [application/json]
2023/08/17 08:57:37 Send Done
2023/08/17 08:57:37 Recv First Byte
2023/08/17 08:57:37 Sent Header: Host [api.moby.localhost]
2023/08/17 08:57:37 Sent Header: User-Agent [Docker-Client/unknown-version (windows)]
2023/08/17 08:57:37 Sent Header: Content-Length [11457]
2023/08/17 08:57:37 Sent Header: Content-Type [application/json]
2023/08/17 08:57:37 Send Done
2023/08/17 08:57:39 Recv First Byte
2023/08/17 08:57:39 Sent Header: Host [api.moby.localhost]
2023/08/17 08:57:39 Sent Header: User-Agent [Docker-Client/unknown-version (windows)]
2023/08/17 08:57:39 Sent Header: Content-Length [0]
2023/08/17 08:57:39 Sent Header: Content-Type [text/plain]
2023/08/17 08:57:39 Send Done
2023/08/17 08:57:41 Recv First Byte
2023/08/17 08:57:41 Sent Header: Host [api.moby.localhost]
2023/08/17 08:57:41 Sent Header: User-Agent [Docker-Client/unknown-version (windows)]
2023/08/17 08:57:41 Send Done
2023/08/17 08:57:41 Recv First Byte
2023/08/17 08:57:42 Sent Header: Host [api.moby.localhost]
2023/08/17 08:57:42 Sent Header: User-Agent [Docker-Client/unknown-version (windows)]
2023/08/17 08:57:42 Send Done
2023/08/17 08:57:42 Recv First Byte
2023/08/17 08:57:43 Sent Header: Host [api.moby.localhost]
2023/08/17 08:57:43 Sent Header: User-Agent [Docker-Client/unknown-version (windows)]
2023/08/17 08:57:43 Send Done
2023/08/17 08:57:43 Recv First Byte
2023/08/17 08:57:44 Sent Header: Host [api.moby.localhost]
2023/08/17 08:57:44 Sent Header: User-Agent [Docker-Client/unknown-version (windows)]
2023/08/17 08:57:44 Send Done
2023/08/17 08:57:44 Recv First Byte
2023/08/17 08:57:45 Sent Header: Host [api.moby.localhost]
2023/08/17 08:57:45 Sent Header: User-Agent [Docker-Client/unknown-version (windows)]
2023/08/17 08:57:45 Send Done
2023/08/17 08:57:45 Recv First Byte
2023/08/17 08:57:46 Sent Header: Host [api.moby.localhost]
2023/08/17 08:57:46 Sent Header: User-Agent [Docker-Client/unknown-version (windows)]
2023/08/17 08:57:46 Send Done
2023/08/17 08:57:46 Recv First Byte
2023/08/17 08:57:47 Sent Header: Host [api.moby.localhost]
2023/08/17 08:57:47 Sent Header: User-Agent [Docker-Client/unknown-version (windows)]
2023/08/17 08:57:47 Send Done
2023/08/17 08:57:47 Recv First Byte
2023/08/17 08:57:48 Sent Header: Host [api.moby.localhost]
2023/08/17 08:57:48 Sent Header: User-Agent [Docker-Client/unknown-version (windows)]
2023/08/17 08:57:48 Send Done
2023/08/17 08:57:48 Recv First Byte
2023/08/17 08:57:49 Sent Header: Host [api.moby.localhost]
2023/08/17 08:57:49 Sent Header: User-Agent [Docker-Client/unknown-version (windows)]
2023/08/17 08:57:49 Send Done
2023/08/17 08:57:49 Recv First Byte
2023/08/17 08:57:50 Sent Header: Host [api.moby.localhost]
2023/08/17 08:57:50 Sent Header: User-Agent [Docker-Client/unknown-version (windows)]
2023/08/17 08:57:50 Send Done
2023/08/17 08:57:50 Recv First Byte
2023/08/17 08:57:51 Sent Header: Host [api.moby.localhost]
2023/08/17 08:57:51 Sent Header: User-Agent [Docker-Client/unknown-version (windows)]
2023/08/17 08:57:51 Send Done
2023/08/17 08:57:52 Recv First Byte
2023/08/17 08:57:52 Sent Header: Host [api.moby.localhost]
2023/08/17 08:57:52 Sent Header: User-Agent [Docker-Client/unknown-version (windows)]
2023/08/17 08:57:52 Send Done
2023/08/17 08:57:52 Recv First Byte
2023/08/17 08:57:53 Sent Header: Host [api.moby.localhost]
2023/08/17 08:57:53 Sent Header: User-Agent [Docker-Client/unknown-version (windows)]
2023/08/17 08:57:53 Send Done
2023/08/17 08:57:53 Recv First Byte
2023/08/17 08:57:54 Sent Header: Host [api.moby.localhost]
2023/08/17 08:57:54 Sent Header: User-Agent [Docker-Client/unknown-version (windows)]
2023/08/17 08:57:54 Send Done
2023/08/17 08:57:54 Recv First Byte
2023/08/17 08:57:55 Sent Header: Host [api.moby.localhost]
2023/08/17 08:57:55 Sent Header: User-Agent [Docker-Client/unknown-version (windows)]
2023/08/17 08:57:55 Send Done
2023/08/17 08:57:55 Recv First Byte
2023/08/17 08:57:56 Sent Header: Host [api.moby.localhost]
2023/08/17 08:57:56 Sent Header: User-Agent [Docker-Client/unknown-version (windows)]
2023/08/17 08:57:56 Send Done
2023/08/17 08:57:56 Recv First Byte
2023/08/17 08:57:57 Sent Header: Host [api.moby.localhost]
2023/08/17 08:57:57 Sent Header: User-Agent [Docker-Client/unknown-version (windows)]
2023/08/17 08:57:57 Send Done
2023/08/17 08:57:57 Recv First Byte
2023/08/17 08:57:58 Sent Header: Host [api.moby.localhost]
2023/08/17 08:57:58 Sent Header: User-Agent [Docker-Client/unknown-version (windows)]
2023/08/17 08:57:58 Send Done
2023/08/17 08:57:58 Recv First Byte
2023/08/17 08:57:59 Sent Header: Host [api.moby.localhost]
2023/08/17 08:57:59 Sent Header: User-Agent [Docker-Client/unknown-version (windows)]
2023/08/17 08:57:59 Send Done
2023/08/17 08:57:59 Recv First Byte
2023/08/17 08:58:00 Sent Header: Host [api.moby.localhost]
2023/08/17 08:58:00 Sent Header: User-Agent [Docker-Client/unknown-version (windows)]
2023/08/17 08:58:00 Send Done
2023/08/17 08:58:00 Recv First Byte
database is not `healthy`

When running docker ps, it will run  for about 20 seconds then timeout.
docker ps
CONTAINER ID   IMAGE                                         COMMAND                  CREATED         STATUS                            PORTS                     NAMES
aa0cc032a1f3   public.ecr.aws/supabase/postgres:<IP_ADDRESS>   "sh -c 'cat <<'EOF' …"   9 seconds ago   Up 4 seconds (health: starting)   <IP_ADDRESS>:54322->5432/tcp   supabase_db_cli_demo

When running docker stats on the container, I see that there is 12 gb mem limit but the container still fails to give healthy signal.
docker stats 3d35c98b9f35
CONTAINER ID   NAME                   CPU %     MEM USAGE / LIMIT     MEM %     NET I/O       BLOCK I/O   PIDS
3d35c98b9f35   supabase_db_cli_demo   0.08%     105.6MiB / 12.42GiB   0.83%     1.11kB / 0B   0B / 0B     14

I have also checked if anything is running on the ports in the config.toml with netstat -aon | find /i "listening"  and they are free.
Any help on what may be causing this issue would be much appreciated, looking to separate my dev / prod environments.

Closing as duplicate of https://github.com/supabase/cli/issues/1384. We have fixed it 1.86.2

I am still encountering the same issue after having deleted the images and updated the cli to 1.86.2.
"database is not healthy" and I can't seem to run the --ignore-health-check flag with npx supabase db start .

I am still facing it on Pop 22.04 with cli version 1.86.2.
Mentioned in the discord server too: https://discord.com/channels/839993398554656828/1142832328842940446/1142832328842940446
And i see no .temp folder as mentioned in #1384

same issue with version 1.82.2
npx supabase db reset
Resetting local database...
Restarting containers...
database is not healthy


transaction calculate-min-fee fails with missing extraPraosEntropy key

Description
The transaction calculate-min-fee command fails on current main with "extraPraosEntropy" not found in protocol parameters file that was generated on latest cardano-node.
Steps to Reproduce

cardano-cli transaction calculate-min-fee --testnet-magic 42 --protocol-params-file pparams.json --tx-in-count 1 --tx-out-count 3 --witness-count 23 --byron-witness-count 0 --tx-body-file transfer-register-delegate-fee-tx.txbody

Command failed: transaction calculate-min-fee  Error: Error while decoding the protocol parameters at: "/home/martink/Source/repos/cardano-node/state-cluster0/pparams.json" Error: "Error in $: key "extraPraosEntropy" not found"

The protocol parametrs were created in Shelley era.
Additional Context
cardano-node: 34d89af65439db92293b88967c299c20692abc1c
Files used for the command: calculate_fee_error.tar.gz

Confirm I can reproduce as of 974946afaf7c2e3ad661e99697b2d390eaa568a1. Thanks @mkoura for the detailed reproducing procedure :handshake:

@mkoura> how did you generate the pparams.json file?

@mkoura did you use the new era based commands?

I used cardano-cli query protocol-parameters. Using cardano-cli shelley query protocol-parameters has the same outcome. The important detail is that

The protocol parametrs were created in Shelley era.

The failure now happens when setting up a testnet that starts in Byron and goes to Babbage by update proposals.


Support for top level await

Do it

Support for top level await will be added to base app then

ok ill do it myself


After vcpkg builds hdf5 statically, my compiled DLL using hdf5 nevertheless depends on msmpi.dll...

...although vcpkg does seem to build msmpi statically.
Is this due to the following?
https://support.hdfgroup.org/HDF5/faq/windows.html#vs-checklist

Specifically:

Using /MT or /MTd, requires advanced changes to the supplied HDF5 libraries.

I was expecting everything to be statically linked (x86), tested OK on my PC (because I had msmpi.dll in SysWOW64) but crashed on a real 32-bit system...

MSMPI is provided as shared binaries by Microsoft only. So vcpkg has no other option than to use the DLLs for the static triplet.
\MT and \MTd are about how to link to the CRT (C Run-Time) and have nothing to do with MSMPI specifically.
What exactly is the problem you are facing with the shared DLLs? Maybe it can be fixed in some other way?!

Thanks for your answer!
I had thought that the MSMPI lib files could be linked statically.
I much prefer to deliver a single file, but it looks as if I'll just have to distribute MSMPI.DLL along with my DLL...


Changes for running as a (background) service

By default, relay.py will wait for user input by reading from the terminal.
This breaks catastrophically when the process is not attached to a terminal, e.g. when started as a systemd unit (#17).
I've changed relay.py so that it waits for signals. This works both for keyboard events as well as detached from a terminal. Additionally, a sample systemd unit is provided.

Yeah tried different variations of background service, doesn't work unfortunately.
It starts, Runs, then exits when run from systemd service.
Also when run normally from terminal, for the first time, if the MJPEG stream is DOWN (the link of whose id passed to the script when it was ran),  doesn't persistently keep trying.
But if the Stream is UP, it connects, then if I kill the stream , it keeps persistently trying and when the link is UP again, it connect successfully.
Either way, impossible to run as a service.
Can this be solved?


python310Packages.tern: 2.9.1 -> 2.10.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.tern is: "A software composition analysis tool and Python library that generates a Software Bill of Materials for container images and Dockerfiles"
meta.homepage for python310Packages.tern is: "https://github.com/tern-tools/tern"
meta.changelog for python310Packages.tern is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
Warning: no invocation of /nix/store/yk3645zl09x7ic43l6h6my4g5jzcx0y5-python3.10-tern-2.10.0/bin/tern had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/yk3645zl09x7ic43l6h6my4g5jzcx0y5-python3.10-tern-2.10.0/bin/.tern-wrapped had a zero exit code or showed the expected version
0 of 2 passed binary check by having a zero exit code.
0 of 2 passed binary check by having the new version present in output.
found 2.10.0 with grep in /nix/store/yk3645zl09x7ic43l6h6my4g5jzcx0y5-python3.10-tern-2.10.0
found 2.10.0 in filename of file in /nix/store/yk3645zl09x7ic43l6h6my4g5jzcx0y5-python3.10-tern-2.10.0

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

2 package rebuild(s)

2 x86_64-linux rebuild(s)
2 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
python310Packages.tern
python39Packages.tern

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/yk3645zl09x7ic43l6h6my4g5jzcx0y5-python3.10-tern-2.10.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.tern https://github.com/r-ryantm/nixpkgs/archive/752a0828229d2a6975bfbc7efafb921ee0569788.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/yk3645zl09x7ic43l6h6my4g5jzcx0y5-python3.10-tern-2.10.0
ls -la /nix/store/yk3645zl09x7ic43l6h6my4g5jzcx0y5-python3.10-tern-2.10.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

python310Packages.tern
python39Packages.tern

Maintainer pings
cc @cole-h @grahamc for testing.

Runtime failure for Python 3.10:
[nix-shell:~/.cache/nixpkgs-review/pr-168750]$ ./results/python310Packages.tern/bin/tern
Traceback (most recent call last):
  File "/nix/store/2l8cp7m9h4aiis1sx0c3fggp1sh2awvz-python3.10-tern-2.10.0/bin/.tern-wrapped", line 6, in <module>
    from tern.__main__ import main
  File "/nix/store/kb0i0k3g23wg5cyw2h3y4la588h0i3cz-python3.9-tern-2.10.0/lib/python3.9/site-packages/tern/__main__.py", line 17, in <module>
    from tern.utils import cache
  File "/nix/store/kb0i0k3g23wg5cyw2h3y4la588h0i3cz-python3.9-tern-2.10.0/lib/python3.9/site-packages/tern/utils/cache.py", line 27, in <module>
    from tern.utils import rootfs
  File "/nix/store/kb0i0k3g23wg5cyw2h3y4la588h0i3cz-python3.9-tern-2.10.0/lib/python3.9/site-packages/tern/utils/rootfs.py", line 17, in<module>
    from tern.utils import general
  File "/nix/store/kb0i0k3g23wg5cyw2h3y4la588h0i3cz-python3.9-tern-2.10.0/lib/python3.9/site-packages/tern/utils/general.py", line 9, in<module>
    import regex
  File "/nix/store/w81lgfi35zzy0iwrwwcm5i5acx82nh24-python3.9-regex-2022.3.2/lib/python3.9/site-packages/regex/__init__.py", line 1, in <module>
    from .regex import *
  File "/nix/store/w81lgfi35zzy0iwrwwcm5i5acx82nh24-python3.9-regex-2022.3.2/lib/python3.9/site-packages/regex/regex.py", line 419, in <module>
    import regex._regex_core as _regex_core
  File "/nix/store/w81lgfi35zzy0iwrwwcm5i5acx82nh24-python3.9-regex-2022.3.2/lib/python3.9/site-packages/regex/_regex_core.py", line 21,in <module>
    import regex._regex as _regex
ModuleNotFoundError: No module named 'regex._regex'

On master it looks fine.


./tohex.sh problem

hi, i got problem when i run ./tohex.sh. Any hints? thanks

It looks like you only need to mkdir riscv under the folder /src/chisel-template/src because riscv64-unknown-elf-objcopy won't automatically create folders that do not exist.

thank you Japanese Friend, greeting from Hong Kong
ありがとう日本の友人、香港からのご挨拶


[lidarr] refactor of exportarr sidecar and podmonitor

If these changes look good I'll update sonarr and radarr as well.
Checklist

[X] Chart version bumped in Chart.yaml according to semver.
[X] Title of the PR starts with chart name (e.g. [home-assistant])
[X] Variables are documented in the README.md (this can be done with using our helm-docs wrapper ./hack/gen-helm-docs.sh stable <chart>)

I think you can keep it consistent and make the key name exporter instead of exportarr

I think you can keep it consistent and make the key name exporter instead of exportarr, we can keep it like the qb one.

Yeah no problem. Are there any other additional env vars for exportarr you think should be included?

I think you got all the ones that should be configurable. Just made a comment on to rename the 2 default ones

@bjw-s or @onedr0p  So for whatever reason this didn't land in the repo. Sonarr and radarr went through just fine.

I see in lidarr-12.0.0 in the github releases.

If it's not coming thru we probably need to bump it to 12.0.1.


Gh-2693: Add CI workflow for legacy tests

Related Issue

Resolve #2693

Codecov Report

:exclamation: No coverage uploaded for pull request base (v2-alpha@5f22ae6). Click here to learn what that means.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff             @@
##             v2-alpha    #2894   +/-   ##
===========================================
  Coverage            ?   73.62%
  Complexity          ?      228
===========================================
  Files               ?       19
  Lines               ?      728
  Branches            ?       57
===========================================
  Hits                ?      536
  Misses              ?      143
  Partials            ?       49

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Reduce sidebar width to 260px and truncate tags

This doesn't handle hovering/displaying the entire tag as @tinybike suggested in CH.  Happy to add something for that if there are suggestions as to correct approach.
I don't think we want <ReactTooltips /> on each one because then each one will pop something up which IMO would be obtrusive (assuming the same behavior as on that packages demo site).  But I don't know, maybe a conditional <ReactTooltip /> if (s.length > x)?  Let me know thoughts.

I’m going to close this PR in favor of a PR from a branch in this repo (makes things easier to make changes).


eslint autofix doesn't fire

eslint autofix fires when manually extended build in nuxt.config.json
build: {
  extend(config, ctx) {
    config.module.rules.push({
      enforce: "pre",
      test: /\.(js|vue)$/,
      loader: "eslint-loader",
      exclude: /(node_modules)/,
      options: {
        fix: true
      }
    })
  }
}

but below code doesn't work
devModules: [
  '@nuxtjs/eslint-module'
],

eslint: {
  fix: true
},

nor
devModules: [
  ['@nuxtjs/eslint-module', { fix: true }]
],

fresh nuxt project v2.8.1

Hi @kakajansh
Can you either provide repository or a GIF of the blink ?

I created new app with npx create-nuxt-app. It turns out that it didn't pull the latest version of nuxt-app. So there was installed "@nuxtjs/eslint-module": "^0.0.1" version. Upgrading deps resolves issue 👍
➜  npx create-nuxt-app nuxt-app
npx: installed 379 in 51.567s
create-nuxt-app v2.8.0
✨  Generating Nuxt.js project in /nuxt-app
? Project name nuxt-app
? Project description My divine Nuxt.js project
? Author name Kakajan SH
? Choose the package manager Npm
? Choose UI framework None
? Choose custom server framework None (Recommended)
? Choose Nuxt.js modules
? Choose linting tools ESLint
? Choose test framework None
? Choose rendering mode Single Page App

Maybe some related issues on create-nuxt-app repo:

outdated dependencies in newly created app
linting doesn't work properly
install with npx create-nuxt-app, always install old version (v2.3.4)

How did you fix this ? I have the same issue

@begueradj check version @nuxtjs/eslint-module

npx create-nuxt-app still is using < v1.1.0

I have the same issue, and my @nuxtjs/eslint-module is version 3.0.1

@ricardogobbosouza - I know this is an old issue, but I'm running into this with @nuxtjs/eslint-module 3.0.2.
Based on the fact that I'm running the latest published version and, in combination with @bf's comment, I really don't think the solution is "use the latest version".
Unfortunately, I haven't figured out a solution.  If you have bandwidth to dig into this, doing so would be appreciated!

@metasean what's the issue with using the latest version?


Adding list of public resources

Adding a list with public talks/resources to repo+docs

rerun tests


Create a black list of genes with a high probability of being false positives

From email conversation with @vanaukenk:
We could use the ratio of curated references in WB to TextpressoCentral hits using the gene name as a keyword search as an indication of the probability of being a false positive. The higher the ration the lower the probability.

We also need a manual blacklist for other entities such as CB2 strain

We decided to try to implement TFIDF based threshold and to compare the results with manual blacklists: https://docs.google.com/spreadsheets/d/1hpo3DCIcOX20mrLNOQk4KdU3Bal7bJJGIdiJSsRqbsw

closing as we are using TFIDF, if need be to add manual blacklists we will comment them  in


Upgraded snowflake dependency to fix an issue with an unpinned depend…

…ency

Coverage remained the same at 91.279% when pulling 5a148c9250ffe4c3befe431594081ce208ed00ee on upgrade_snowflake_dep into 44318011c7cb3cfc97af20c3bc95b4cf8621d0f8 on master.


Playback Windows Support

Changelog:

Updated electron-prebuilt to the latest version
Checks to find if user is on windows or mac and change the titlebar and the window frame, depending on that.
Add Windows icon
Updated contribution information and readme file with new information
Windows Build

Good start!
It seems that protocol support isn't working yet on Windows (opening a magnet:// or playback:// URL from the browser with playback.exe just starts the app without the stream starting), as referenced in: https://github.com/mafintosh/playback/issues/40

This is awesome :+1:

I'm not on Windows so I can't check that this works, but otherwise it lgtm. @mafintosh should we merge?

Added a few comments. Other than that this is a great start to add full Windows support so LGTM!

@freeall It works fine on Windows, except for the protocol support. I also personally prefer the custom layout rather than the standard Windows one, which this one has. That's subjective though.

I did the recommended changes @mafintosh
@iadj I changed the frame value to build more native feeling in Windows user

@tsvetilian-ty perfect thanks! could i get you to squash this down to a single commit?

Done @mafintosh

@tsvetilian-ty NICE! merged! now we just need someone to do a windows build so we can release it hint hint

@mafintosh Windows build is already done :+1:

@tsvetilian-ty thats awesome. will publish as soon as i get to decent non-airport internet :)

Should add a note to the Windows build that protocols aren't yet supported


New Laravel WebConsole Integration

Hi,
I'm creating a new PR for my old https://github.com/bagisto/bagisto/pull/1762 PR.
I upgraded my package from version 1.5.1 to 2.2.1
In new version developers can add a forbidden commands in the config file, and the wrapper will detect it and not run.
Please check it, the Laravel 6 verison

Please do not provide a web console in the bagisto core.
@alkhachatryan you can extend the composer.json in your project in order to use the web console in your specific environment.

@thyseus I offer to have it imported in the bagisto by default. I talk with bagisto developers and have an acceptance to do it.

Hi @alkhachatryan
We appreciate your work but some of our customers are non technical and it adds extra dependencies, which is not required by every one.
So, we can not add it into our core project but you can make an extension for it and we will add your extension to our store so that according to   need of customer, they can use it.
Thanks

Hi @rahulshukla-webkul
Thank you.
Where can I see the documentation of extension creation?

Where can I see the documentation of extension creation?

https://devdocs.bagisto.com/create_package.html#how-to-create-package

Where can I see the documentation of extension creation?

https://devdocs.bagisto.com/create_package.html#how-to-create-package

Where can I publish my extension, so ppl can see it in bagisto.com?

Hi @alkhachatryan
You can submit here - https://bagisto.com/en/extension-form/
Thanks


Add config_utils tests

Description of the change
Add unit tests for the config_utils with 100% test coverage

Related issue number

Part of #75
How to verify the PR

Was the PR tested

[x] I have added >=1 unit test(s) for every new method I have added.
[x] I have ensured all unit tests pass

Thank you for the PR!
Just curious to know one thing:
In the test function test_get_hf_peft_config_returns_PT_config_correctly, below code checks and raises error tokenizer_name_or_path cannot be None.
    tuning_config = peft_config.PromptTuningConfig(prompt_tuning_init="TEXT")
    with pytest.raises(ValueError) as err:
        config_utils.get_hf_peft_config(None, tuning_config, None)
        assert "tokenizer_name_or_path can't be None" in err.value

As this check and raising of error is done by PromptTuningConfig Class of peft library and not by our code, so was just curious if we comment this code do we still get 100% coverage in file tuning/utils/config_utils.py?

Yea, you're right @Abhishek-TAMU . That test doesn't increase test coverage for tuning/utils/config_utils.py. I just wanted to test that the value None for tokenizer_name_or_path was passed down to PromptTuningConfig init and post_init properly and if there's error/exception, we are able to catch it in our utils.
Additional testing wasn't necessary but I'm sure wouldn't hurt


eslint fails during build of 2.32.0

System information: Alpine Linux edge

yarn run v1.22.17
$ eslint --fix "src/**/*.{ts,tsx}"
=============

WARNING: You are currently running a version of TypeScript which is not officially supported by @typescript-eslint/typescript-estree.

You may find that it works just fine, or you may not.

SUPPORTED TYPESCRIPT VERSIONS: >=3.3.1 <4.5.0

YOUR TYPESCRIPT VERSION: 4.5.4

Please only submit bug reports when using the officially supported version.

=============

Oops! Something went wrong! :(

ESLint: 8.4.1

Error: Rules with suggestions must set the `meta.hasSuggestions` property to `true`. `meta.docs.suggestion` is ignored by ESLint.
Occurred while linting /home/sircmpwn/sources/aports/community/prometheus/src/prometheus-2.32.0/web/ui/react-app/src/components/withStatusIndicator.tsx:14
Rule: "@typescript-eslint/no-explicit-any"
    at Object.report (/home/sircmpwn/sources/aports/community/prometheus/src/prometheus-2.32.0/web/ui/node_modules/@typescript-eslint/experimental-utils/node_modules/eslint-utils/node_modules/eslint/lib/linter/linter.js:1056:39)
    at TSAnyKeyword (/home/sircmpwn/sources/aports/community/prometheus/src/prometheus-2.32.0/web/ui/node_modules/@typescript-eslint/eslint-plugin/dist/rules/no-explicit-any.js:183:25)
    at ruleErrorHandler (/home/sircmpwn/sources/aports/community/prometheus/src/prometheus-2.32.0/web/ui/node_modules/@typescript-eslint/experimental-utils/node_modules/eslint-utils/node_modules/eslint/lib/linter/linter.js:1076:28)
    at /home/sircmpwn/sources/aports/community/prometheus/src/prometheus-2.32.0/web/ui/node_modules/@typescript-eslint/experimental-utils/node_modules/eslint-utils/node_modules/eslint/lib/linter/safe-emitter.js:45:58
    at Array.forEach (<anonymous>)
    at Object.emit (/home/sircmpwn/sources/aports/community/prometheus/src/prometheus-2.32.0/web/ui/node_modules/@typescript-eslint/experimental-utils/node_modules/eslint-utils/node_modules/eslint/lib/linter/safe-emitter.js:45:38)
    at NodeEventGenerator.applySelector (/home/sircmpwn/sources/aports/community/prometheus/src/prometheus-2.32.0/web/ui/node_modules/@typescript-eslint/experimental-utils/node_modules/eslint-utils/node_modules/eslint/lib/linter/node-event-generator.js:297:26)
    at NodeEventGenerator.applySelectors (/home/sircmpwn/sources/aports/community/prometheus/src/prometheus-2.32.0/web/ui/node_modules/@typescript-eslint/experimental-utils/node_modules/eslint-utils/node_modules/eslint/lib/linter/node-event-generator.js:326:22)
    at NodeEventGenerator.enterNode (/home/sircmpwn/sources/aports/community/prometheus/src/prometheus-2.32.0/web/ui/node_modules/@typescript-eslint/experimental-utils/node_modules/eslint-utils/node_modules/eslint/lib/linter/node-event-generator.js:340:14)
    at CodePathAnalyzer.enterNode (/home/sircmpwn/sources/aports/community/prometheus/src/prometheus-2.32.0/web/ui/node_modules/@typescript-eslint/experimental-utils/node_modules/eslint-utils/node_modules/eslint/lib/linter/code-path-analysis/code-path-analyzer.js:795:23)
error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Hello @ddevault ,
So far on our side the build is running fine, otherwise we won't be able to build Prometheus on the different platform.
A couple months ago we moved to npm (from yarn) as a dependency manager. I would suggest to do the same, perhaps it will help to solve your issue.

It's already close to my bandwidth limit trying to keep up packaging this software, as it's primarily designed for the Docker generation and does not pay much heed to the needs of Linux distributions. Would you be prepared to write up some documentation for building and installing Prometheus outside of a Docker container, so I don't have to keep guessing?

From the README at the root of the repo:

You can also clone the repository yourself and build using make build, which will compile in the web assets so that Prometheus can be run from anywhere

https://github.com/prometheus/prometheus#building-from-source
And you can have more information around the frontend specifically here: https://github.com/prometheus/prometheus/tree/main/web/ui
But the section building from source should be enough for your needs. You don't have to guess, I think you just have to read the documentation :).
Or if you think there is a miss in the doc, then definitely we can improve it or you can help to improve it.
And hopefully, for linux distributions, the precompiled binaries should be enough.

Sorry, I was in a bit of a bad mood last night and I should have been more polite.
These instructions are helpful, but not exactly what I'm looking for. I am not a user of a Linux distro - I am a representative of one. We package Prometheus so that users can install it on our distro by running apk install prometheus in one go. We need a process which essentially produces a binary tarball from source which can be extracted over / to install it.
I'll take some of these docs into account and see if my approach cannot be effectively adapted to use some of these details, though.

Alright, I'm using this build process now and it seems to work adequately:
prepare() {
	cd web/ui
	npm install
	sed -i node_modules/codemirror-promql/package.json -e 's/lezer-generator/npx lezer-generator/g'
}

build() {
	GOLDFLAGS="-X github.com/prometheus/common/version.Version=$pkgver
		-X github.com/prometheus/common/version.Revision=AlpineLinux
		-X github.com/prometheus/common/version.Branch=master
		-X github.com/prometheus/common/version.BuildUser=$USER@$HOSTNAME
		-X github.com/prometheus/common/version.BuildDate=$(date -u "+%Y%m%d-%H:%M:%S" ${SOURCE_DATE_EPOCH:+-d @$SOURCE_DATE_EPOCH})
	"
	if [ -n "$LDFLAGS" ]; then
		# LDFLAGS (and only LDFLAGS) should be passed to -extldflags.
		 Thanks for your help!


no window object present

Hi,
I use node-fetch in a reacts + rails project. I use https://github.com/shakacode/react_on_rails to glue between reactjs and Rails. Everything works fine except when I do server side rendering it complains the error "Encountered error "Error: no window object present" when prerendering".
I am willing to work a PR, just need some directions. Thanks!
The line that raise the error:
https://github.com/substack/http-browserify/blob/master/index.js#L54

Hi @ywen,
i'm not sure, but i think it may help you:
https://github.com/webpack/react-starter/issues/37#issuecomment-104304128

By removing a unnecessary node-fetch import the problem is fixed. Thanks for your help!

because server can not find window, you can use this
getInitialState() {
return {windowWidth: (typeof window !== 'undefined')? window.innerWidth:undefined};
},


[Bug] unexpected reltuples number in pg_class after delete and vacuum

Cloudberry Database version
No response
What happened
After delete 15 rows and vacuum,  the following query get unexpected 88 reltuples. But the test case would expect 85. Please confirm if this is incompatible change. Thanks.
SELECT relname, reltuples FROM pg_class WHERE relname = 'foo_index';
relname  | reltuples
-----------+-----------
foo_index |        88
More detailed information, please see how to reproduce section.
What you think should happen instead
No response
How to reproduce
CREATE TABLE foo (a INT, b INT, c CHAR(128)) WITH (appendonly=true) DISTRIBUTED BY (a);
CREATE INDEX foo_index ON foo(b);
INSERT INTO foo SELECT i as a, i as b, 'hello world' as c FROM generate_series(1, 50) AS i;
INSERT INTO foo SELECT i as a, i as b, 'hello world' as c FROM generate_series(51, 100) AS i;
ANALYZE foo;
DELETE FROM foo WHERE a < 16;
VACUUM foo;
SELECT relname, reltuples FROM pg_class WHERE relname = 'foo_index';
You will get reltuples 88:
relname  | reltuples
-----------+-----------
foo_index |        88
(1 row)
Operating System
centos7
Anything else
2 test cases failed due to this issue:
FAIL: UAOCompactionTestCase.test_stats
FAIL: UAOCOCompactionTestCase.test_stats
Are you willing to submit PR?

[ ] Yes, I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct.

Thanks Shengsong for the confirmation. I would update the test case accordingly.


Readers' RPi clusters

Readers' RPi clusters
Please comment here here with your name and URL to your cluster, plus any useful notes you have.
I'll then add it to the Readers' RPi clusters in the main README.
Alex
Join the #arm-and-pi channel on OpenFaaS Slack to chat with our community - https://docs.openfaas.com/community/

Hi @alexellis -
Link to my cluster: https://twitter.com/dnachman/status/1094419142948593664
Everything went relatively smoothly except for the dashboard deployment.  The pod was crashing/retrying. Eventually I went in to the logs and saw this:
kubectl logs pod/kubernetes-dashboard-head-7bc4868777-lzv9r -n kube-system 2019/02/10 16:41:21 Starting overwatch 2019/02/10 16:41:21 Using namespace: kube-system 2019/02/10 16:41:21 Using in-cluster config to connect to apiserver 2019/02/10 16:41:21 Using secret token for csrf signing 2019/02/10 16:41:21 Initializing csrf token from kubernetes-dashboard-csrf secret panic: secrets "kubernetes-dashboard-csrf" not found goroutine 1 [running]: github.com/kubernetes/dashboard/src/app/backend/client/csrf.(*csrfTokenManager).init(0x1f87250)     /home/travis/build/kubernetes/dashboard/.tmp/backend/src/github.com/kubernetes/dashboard/src/app/backend/client/csrf/manager.go:40 +0x2fc github.com/kubernetes/dashboard/src/app/backend/client/csrf.NewCsrfTokenManager(0xef9d40, 0x1fb4120, 0x1, 0xa5c9d4)     /home/travis/build/kubernetes/dashboard/.tmp/backend/src/github.com/kubernetes/dashboard/src/app/backend/client/csrf/manager.go:65 +0x4c github.com/kubernetes/dashboard/src/app/backend/client.(*clientManager).initCSRFKey(0x1f5a1e0)     /home/travis/build/kubernetes/dashboard/.tmp/backend/src/github.com/kubernetes/dashboard/src/app/backend/client/manager.go:362 +0x70 github.com/kubernetes/dashboard/src/app/backend/client.(*clientManager).init(0x1f5a1e0)     /home/travis/build/kubernetes/dashboard/.tmp/backend/src/github.com/kubernetes/dashboard/src/app/backend/client/manager.go:330 +0x34 github.com/kubernetes/dashboard/src/app/backend/client.NewClientManager(0x0, 0x0, 0x0, 0x0, 0x1, 0x0)     /home/travis/build/kubernetes/dashboard/.tmp/backend/src/github.com/kubernetes/dashboard/src/app/backend/client/manager.go:398 +0x6c main.main()     /home/travis/build/kubernetes/dashboard/.tmp/backend/src/github.com/kubernetes/dashboard/src/app/backend/dashboard.go:99 +0x104
Looking at the main dashboard, I executed this to create the kubernetes-dashboard-csrf:
echo 'apiVersion: v1 kind: Secret metadata:   labels:     k8s-app: kubernetes-dashboard   name: kubernetes-dashboard-csrf   namespace: kube-system type: Opaque data:   csrf: ""' | kubectl apply -f -
And then everything worked.
You might also want to include the port forwarding command (if people are running headless) and the dashboard url:
ssh -L 8001:localhost:8001 node-1
http://localhost:8001/api/v1/namespaces/kube-system/services/http:kubernetes-dashboard-head:/proxy/#/overview?namespace=default
Good stuff! Now I've got to go build some new arm docker images for my code (already had x86)

Hello @alexellis,
Here is the link to my RPi cluster:
https://twitter.com/ravidsinghbiz/status/1094529653362966528
Thank you,

Ravi

@dnachman please raise a separate issue.

Hi @alexellis
Here is my cluster:
Name: selexin (Australia)
URL: https://selexin.com/2019/04/12/kubernetes-on-raspberry-pi-cluster.html
Useful notes:
4x RPi Cluster, running dnscrypt-proxy/sonarr/couchpotato/nzbget, among other things :)
Had some issues setting up Load Balancing and Persistent Volumes/Storage - which I am covering in my new blog, along with setting up the services mentioned :)

Here it is mine:
https://twitter.com/henry2man/status/1085674266115407878
Nodes: 1x PI 3B & 2x PI 3B+
PSU: Anker 60W 6 port
Switch: TP-Link GIGABIT 5 ports powered by a USB-to-barrel adapter from PSU
Planned upgrade (waiting for shipping🤞): 1x PI 4B 4Gb
OS: Raspbian Stretch
Docker engine
K8s: #K3S


Revert "[ci] Switch to macOS VM with Flutter pre-installed"

Reverts flutter/plugins#1313
We've been started to get the following error on the Cirrus tasks:
./script/incremental_build.sh build-examples --ipa
fatal: No such ref: 'FETCH_HEAD'
fatal: Not a valid object name FETCH_HEAD

I suspect the reverted change is where it regressed.

@amirh do you have a link to the build where you saw it?

It happens on any macOS task since this change landed, I think what happens is that ./script/incremental_build.sh expects the current directory to be one where the plugins repo is cloned but it isn't(though let's first see if we're not getting the error with the revert).
e.g see the log for build here: https://cirrus-ci.com/task/4977285139005440

I think it's because git fetch origin master got removed. My bad! See #1865

Closing this in favor of #1865


feat: support merging output from multiple file keys when writing to stdout

Closes #114
Adds support for passing --file-key multiple times to the same invocation of rapids-dependency-file-generator, for requirements and conda output. This allows writing to stdout the union of multiple file keys.
Like this
rapids-dependency-file-generator \
  --output requirements \
  --file-key "py_build_libcuspatial" \
  --file-key "py_rapids_build_libcuspatial" \
  --matrix "cuda=11.8;arch=x86_64;py=3.11;cuda_suffixed=true"
| tee ./requirements-build.txt

Notes for Reviewers
The motivating use case for this is generating requirements.txt files containing all the build dependencies for wheels (https://github.com/rapidsai/cuspatial/pull/1473#pullrequestreview-2373307028).
Design choices?
See inline comments on the diff.
This does not support pyproject output
I cannot think of an application where we'd want to write the merged output of 2 pyproject.toml files to stdout, and the implementation to support that would be a lot more difficult than supporting conda and requirements, because with pyproject support we're splicing into an existing file's content (instead of creating the entire file content from scratch).
Here I'm proposing just raising an exception if someone attempts to pass multiple --file-key + --output pyproject and write to stdout.
How I tested this
Added new unit tests here.
Also tried some different invocations locally, in cudf and cuspatial.
Temporarily added code in ci/build_libcuspatial_wheel.sh over in https://github.com/rapidsai/cuspatial/pull/1473 to install rapids-dependency-file-generator from this branch, and saw it do the right thing there, generating a single list that merged the build backend (rapids-build-backend + scikit-build-core) and build-time dependencies (e.g. librmm):
# This file is generated by `rapids-dependency-file-generator`.
# To make changes, edit . and run `rapids-dependency-file-generator`.
--extra-index-url=https://pypi.anaconda.org/rapidsai-wheels-nightly/simple
--extra-index-url=https://pypi.nvidia.com/
cmake>=3.26.4,!=3.30.0
libcudf-cu11==24.12.*,>=0.0.0a0
librmm-cu11==24.12.*,>=0.0.0a0
ninja
rapids-build-backend>=0.3.0,<0.4.0.dev0
scikit-build-core[pyproject]>=0.10.0
wheel

(build link)

:tada: This PR is included in version 1.16.0 :tada:
The release is available on:

GitHub release
PyPI release
Conda release - rapidsai
Conda release - rapidsai-nightly

Your semantic-release bot :package::rocket:


BLECharacteristic get raw data

Currently, in BLECharacteristic you can get value only as std::string - std::string    getValue();
But what if I need raw data (can contain zeros in my case).
Is there is a workaround?
If not, will you accept pull request with the new function for this? And how fast it will appear in 'ESP32 BLE Arduino'?
Thanks

@nkolban

I was fighting with a similar challenge, but a simple casting to byte, short or uint solved my problem.

@u4mzu4 that is not a solution for my case.
I can receive e.g. 0x11110011. When it will be transformed into std::string the last byte 0x11 will be lost.

I made additional tests. And seems I was wrong std::string::length() not cut length by zero byte, so existed function is ok.
Sorry for bothering.


[feat] support apply one diff change only

Press A will check diff one by one, but i want to just check and apply one changes

Good point! Will be adding this feature soon!

The latest version is already supported.


Azcopy stopped working for blob copy from one storage account to another

Which version of the AzCopy was used? - 10.16.2
Note: The version is visible when running AzCopy without any argument
Which platform are you using? (ex: Windows, Mac, Linux) - Windows
What command did you run?
azcopy cp "https://source.blob.core.windows.net/?[SAS]" "https://destination.blob.core.windows.net/?[SAS]" --recursive=true --preserve-smb-permissions=true --preserve-smb-info=true
Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.
What problem was encountered? - Failing to copy blob data from source to destination
How can we reproduce the problem in the simplest way?
Have you found a mitigation/solution?
No

Hi @KillerFrost2000 Could you please share more information here? A snippet of the logs where the command fails would help, or a brief snippet on how to reproduce the issue. Sharing information on the permissions on the SAS tokens would help as well.


Use InnoDB tables throughout version 9

I believe that version 9 on Concrete5 and all future versions should be changed and set the standard for it's database to be using only InnoDB tables, as presently it's using both InnoDB and MyISAM.

Seems like a dupe of #6537


ruff: automatic docstring rules after numpy convention

since we are up to use numpy conventions (see contribution guidelines) I suggest to apply this set here.
I ignored a couple of rules, since we never really followed them:
    "D200", # One-line docstring should fit on one line with quotes
    "D202", # No blank lines allowed after function docstring
    "D205", # 1 blank line required between summary line and description
    "D401", # First line should be in imperative mood
    "D404", # First word of the docstring should not be "This"

https://docs.astral.sh/ruff/faq/#does-ruff-support-numpy-or-google-style-docstrings

Where do these r""" additions come from and why are they necessary?

fixed all maths in doc, ready to review


Multiple "Help" forms

Every my click menu "Help" creates separate window. If I click "Scan" or "Results" the "Help" windows disappear

Hey Oleg,
Can you provide more detail on the OS and ASA version you're using?

I use the latest ASA version: downloaded it from the git 2 days ago, built it for Windows and run in Windows 7.

I can't reproduce this on any supported platform, either in the Electron or slim GUIs.  There's no mechanism implemented which would close the help menus.
Clicking Help will open a new window each time, that is expected behavior.
When you navigate to scan or results the help windows are not closed. This is expected behavior.
Finally, if you are attempting to build the Electron GUI on Windows 7, that is not currently a platform we support.

@Oleg26Dev without more info I'll need to close this issue. Let me know if you're still having trouble.


Preparation for Training & Testing problem

hello,
problem 1 :
for Preparation for Training & Testing  step  have three point .
can I only do the first one? ( the second and the third do not  do it ).
problem 2 :
can I train my own dataset ?
if it can, how to do ?(I see the Preparation for Training & Testing  step , but I don't know)
thanks

If you only want to train on VOC, do 1 and 3. If you only want to train on COCO, do 2 and 3.
Yes. You need to check the code to see how to prepare training data.


MM-38260: Enabled the team list and team details system console pages in team edition build.

Summary
Enabled the team list and team details system console pages in team edition build.
Ticket Link
https://mattermost.atlassian.net/browse/MM-38260
Screenshots

Release Note
Enabled the team list and team details system console pages in team edition build.

Cherry pick is scheduled.

Thank you all! You rock 🤘


timestamp: always check for DST when assembling a time packet.

This makes usage of timestamp/time and timestamp/make-time nodes still
interoperating under DST on any machine.
Signed-off-by: Gustavo Lima Chaves<EMAIL_ADDRESS>It also makes check-fbp pass again.

@bdilly ^ all good?

It's working fine.
Thanks

Alright, I'll fix the place of attribution and merge.


If node hasn't any links, node stacked in left corner.

Describe the bug
There are some nodes without any links in my data,
and they are stacked in the left corner.
Why these things happen?
I've been try figure out to fix this problem for one week, but I couldn't.
Please help me.
My codes are very simple.
const data = {
   nodes: [{ id: "Harry" }, { id: "Sally" }, { id: "Alice" }, {id: "TestNode"}],
   links: [{ source: "Harry", target: "Sally" }, { source: "Harry", target: "Alice" }]
}
Screenshots

Environment:

OS : Windows 10
Browser : Chrome
Version : 77
Node version : 10.16.3
react-d3-graph version : 2.3.0
d3 version : 5.12.0
react version : 16.8.6

Additional context
This is completely perfect for me except just that bug. I really want to use this.

Hi @honggyookim thanks for the report. I tried myself with the small dataset example, using the following data:
module.exports = {
    links: [
        {
            source: 1,
            target: 2,
            label: "link 1 and 2",
        },
        {
            source: 1,
            target: 3,
        },
        {
            source: 1,
            target: 4,
        },
        {
            source: 3,
            target: 4,
        },
    ],
    nodes: [
        {
            id: 1,
            name: "Node 1",
        },
        {
            id: 2,
            name: "Node 2",
        },
        {
            id: 3,
            name: "Node 3",
        },
        {
            id: 4,
            name: "Node 4",
        },
        {
            id: 5,
            name: "Node 5",
        },
    ],
};

Everything seems to work fine. The solo node, is not stacked at the top left corner...

Do you have any error in the browser console that could give us more detail on your problem? Also can you provide the repository with this specific example?

Also, note that you might need to provide an initial position, as we do in the interactive sandbox example.
    decorateGraphNodesWithInitialPositioning = nodes => {
        return nodes.map(n =>
            Object.assign({}, n, {
                x: n.x || Math.floor(Math.random() * 500),
                y: n.y || Math.floor(Math.random() * 500),
            })
        );
    };

I'm really appreciate for your quick response.
I tried that your suggestion. and I faced on the same problem.
I created new project, and I didn't set any options.
Result is sames as below.

One node without any links is still on the left corner.
Yes, any errors and warnings don't exist.
What happened to me? (but I'm enjoying now.)
Now, I'm gonna trying to your second suggestion.
Thank you so much again.

I solved it in second way you suggested.
Thank you very much.


cannot be used to index type (2536) false positive with generic using array length

Bug Report

🔎 Search Terms
2536 cannot be used to index type generic
🕗 Version & Regression Information
4.4.0-dev.20210727
⏯ Playground Link

Playground link with relevant code
💻 Code

type _PrependNextNum<A extends Array<unknown>> = [...A, A['length']]

type _Enumerate<A extends Array<unknown>, N extends number> = N extends A['length']
    ? A
    : _Enumerate<_PrependNextNum<A>, N>

/**
 * creates a union type of numbers from 0 to generic `N`
 *
 * @example
 * type Foo = Enumerate<3> //0|1|2
 * @see https://stackoverflow.com/a/63918062
 */
export type Enumerate<N extends number> = number extends N
    ? number
    : _Enumerate<[], N> extends (infer E)[]
    ? E
    : never

declare function foo<T extends unknown[]>(
    value: T,
    index: T[Enumerate<T['length']>] //Type 'Enumerate<T["length"]>' cannot be used to index type 'T'.(2536)
    ): void

🙁 Actual behavior
Type 'Enumerate<T["length"]>' cannot be used to index type 'T'.(2536)

🙂 Expected behavior
no error

I feel like this is a super common thing with generic conditional types. You can give the compiler a hint about the constraint of E, which will make every branch of Enumerate look trivially assignable to number. How’s this?

You could also write this as
export type Enumerate<N extends number> = number & (number extends N
  ...


Missing component in components directory does NOT cause error message nor exception in a gRPC service

In what area(s)?

/area runtime

/area operator
/area placement
/area docs
/area test-and-release

What version of Dapr?

1.0.0

Output of git describe --dirty

Expected Behavior

With a gRPC service, when a pubsub component is missing from the .dapr/components directory and that missing pubsub component is used by a service subscribing to events and specifying that the missing component be used, an error message should show up on the console or log that clearly states the pubsub component is MISSING.
In other words, when my service software subscribes to a pubsub component that is not present, Dapr needs to generate an error message at least.
Even better would be a way to throw an exception in the service software stating that the component subscribed to is not present.  An exception would immediately  bring attention to the issue, while a mere console error message may not be so visible.
Note that at least when using the .NET SDK with gRPC services, that attempting to publish an event to a missing pubsub component does cause an exception in the service code.  For example:
Dapr.DaprException: Publish operation failed: the Dapr endpoint indicated a failure. See InnerException for details.				 ---> Grpc.Core.RpcException: Status(StatusCode="InvalidArgument", Detail="pubsub svs-pubsub-asbtopic not found")
Actual Behavior

When a pubsub component is missing and is subscribed to by a gRPC service, Dapr says nothing to indicate anything is wrong.  This means a  subscribing service  can be happily running for days with the operators thinking all is OK, yet it is not receiving messages and there is no indication anything is wrong.
Here is the output when I had previously removed 2 of the 3 pubsub components from the components directory, but kept the subscription registrations to all 3 in the service code.  There is no indication of anything wrong:
You're up and running! Dapr logs will appear here.
time="2021-03-06T14:16:38.2572424-05:00" level=info msg="app is subscribed to the following topics: [svcADemoEvents1] through pubsub=pubsub" app_id=serviceB instance=A-GeorgeXPS1 scope=dapr.runtime type=log ver=1.0.0
time="2021-03-06T14:16:38.2582381-05:00" level=info msg="app is subscribed to the following topics: [svcADemoEvents1] through pubsub=svs-pubsub-asbtopic" app_id=serviceB instance=A-GeorgeXPS1 scope=dapr.runtime type=log ver=1.0.0
time="2021-03-06T14:16:38.2582381-05:00" level=info msg="app is subscribed to the following topics: [svcADemoEvents1] through pubsub=svs-pubsub-envvarsecrets-asbtopic" app_id=serviceB instance=A-GeorgeXPS1 scope=dapr.runtime type=log ver=1.0.0
The latter 2 pubsub components had been removed from components directory, even though the subscription code remained in the service as shown below:
   public override Task<ListTopicSubscriptionsResponse> ListTopicSubscriptions(Empty request, ServerCallContext context)
    {
        var result = new ListTopicSubscriptionsResponse();
        try
        {
            result.Subscriptions.Add(new TopicSubscription
            {
                // Used with supplied default Redis pubsub component.
                PubsubName = NamesOfQueuesNPubSubs.PubSubDefaultDaprComponent,
                Topic = NamesOfQueuesNPubSubs.ServiceADemoEvents1Topic
            });
            result.Subscriptions.Add(new TopicSubscription
            {
                PubsubName = NamesOfQueuesNPubSubs.PubSubAzServiceBusComponent,
                Topic = NamesOfQueuesNPubSubs.ServiceADemoEvents1Topic
            });
            result.Subscriptions.Add(new TopicSubscription
            {
                PubsubName = NamesOfQueuesNPubSubs.PubSubAzServiceBusEnvVarSecretsComponent,
                Topic = NamesOfQueuesNPubSubs.ServiceADemoEvents1Topic
            });
        }
        catch (Exception ex)
        {
            m_Logger.LogError($"** ServiceB.ListTopicSubscriptions() threw exception ex={ex}");
            throw;
        }
        return Task.FromResult(result);
    }

Note that the above code did not cause an exception.
Steps to Reproduce the Problem

With a gRPC service in the AppCallback interface implementation, subscribe to one or more topics using the default pubsub component.  Then test it to make sure the subscription actually receives and processes published events.  Then stop the gRPC service.  Next remove the pubsub.yaml component from the .dapr/components directory.  Restart the gRPC service and you will see that it successfully subscribes to the topic, and says so, even though the component implementing the subscription is gone and will not work.
Release Note

RELEASE NOTE:

This is confirmed behavior:
from cloudevents.sdk.event import v1
from dapr.ext.grpc import App

import json

app = App()

@app.subscribe(pubsub_name='pubsub_foo', topic='TOPIC_A')
def mytopic(event: v1.Event) -> None:
    data = json.loads(event.Data())
    print(f'Subscriber received: id={data["id"]}, message="{data["message"]}", content_type="{event.content_type}"',flush=True)

app.run(50051)

dapr run --app-id python-subscriber --app-protocol grpc --app-port 50051 python3 subscriber.py

INFO[0000] Initialized name resolution to mdns           app_id=python-subscriber instance=DESKTOP-VT2HV7S.corp.microsoft.com scope=dapr.runtime type=log ver=1.2.2
INFO[0000] component loaded. name: pubsub, type: pubsub.mqtt/v1  app_id=python-subscriber instance=DESKTOP-VT2HV7S.corp.microsoft.com scope=dapr.runtime type=log ver=1.2.2
INFO[0000] waiting for all outstanding components to be processed  app_id=python-subscriber instance=DESKTOP-VT2HV7S.corp.microsoft.com scope=dapr.runtime type=log ver=1.2.2
INFO[0000] component loaded. name: statestore, type: state.redis/v1  app_id=python-subscriber instance=DESKTOP-VT2HV7S.corp.microsoft.com scope=dapr.runtime type=log ver=1.2.2
...
INFO[0000] app is subscribed to the following topics: [TOPIC_A] through pubsub=pubsub_foo  app_id=python-subscriber instance=DESKTOP-VT2HV7S.corp.microsoft.com scope=dapr.runtime type=log ver=1.2.2

We can definitely log an error for this case. We'd have to think about how to surface this for the app.

Surfacing an error would significantly decrease the debug time for this. Sent from Mail for Windows 10 From: Charlie StanleySent: Thursday, July 1, 2021 7:26 PMTo: dapr/daprCc: georgestevens99; AuthorSubject: Re: [dapr/dapr] Missing component in components directory does NOT cause error message nor exception in a gRPC service (#2895) We can definitely log an error for this case. We'd have to think about how to surface this for the app.—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.


Error: Please provide a Telegram Bot Token when instantiating

So.. I've added the first sample code. I've requested the Telegram Bot API Key via the BotFather and added it in there. Now I get the error:
Error: Please provide a Telegram Bot Token when instantiating
My Key looks like:

123456789:Ab1Cd2Ef3Gh4Ij5Kl6Mn7Op8Qr9

I'm using Node v8.1.2
Nothing found in the web

PS: Anyway you whole project looks good

Worked by simply removing the "process.env".

Worked by removing the "process.env". Thank u @Joni4Games

Sorry for not following up on this. process.env is for environment variables that are loaded into your shell, usually found in ~/.profile.
An example inside your ~/.profile would be:
export TELEGRAM_BOT_TOKEN='token string'

And you'd use it in Node like this:
const token = process.env['TELEGRAM_BOT_TOKEN']


Gurobi MIP solver in v1.0

In cvxpy 1.0 there seems to be an issue with the Gurobi solver interface. In particular, it doesn't seem to respect boolean and integer flags for variables.
var = cvxpy.Variable(1, boolean=True)
objective = cvxpy.Maximize(var)
constraints = []
prob = cvxpy.Problem(objective, constraints)
prob.solve(solver='GUROBI', verbose=True)

fails with an Unbounded model error.
If I change the constraint to [var <= 1.5], I get the non-integer solution var=1.5.
Thanks,
Felix

This should be fixed now for QPs on the latest commit. I'm still working on making it work for all problems that GUROBI can solve.

Ok this is fixed now for all GUROBI interfaces.


[v1.1.1] NPM version dist files changed?

Previously (before v1.1.1) the dist folder conveniently contained all palette theme css files such as material.teal-lime.min.css. And one of my projects could simply grab the files without running gulp. These files are gone in v1.1.1. May I ask the reason for this?

Also gulp styles:gen clearly relies on ./docs/_assets/customizer.js so there's no way I can generate those files on my own from the npm package (which doesn't have docs folder).

I'm also missing dist/material.css.template which was included up to 1.1.0 but is missing in 1.1.1

I have the same problem - dist folder is missing most css themes that were there in version 1.0.6.

ls -l node_modules/material-design-lite/dist
-rw-rw-r-- 1 user user 347302 Feb  3 15:46 material.css
-rw-rw-r-- 1 user user  34734 Feb  3 15:46 material-grid.css
-rw-rw-r-- 1 user user  18772 Feb  3 15:46 material-grid.min.css
-rw-rw-r-- 1 user user 143704 Feb  3 15:46 material.js
-rw-rw-r-- 1 user user 136656 Feb  3 15:46 material.min.css
-rw-rw-r-- 1 user user 918767 Feb  3 15:46 material.min.css.map
-rw-rw-r-- 1 user user  61655 Feb  3 15:46 material.min.js
-rw-rw-r-- 1 user user 353114 Feb  3 15:46 material.min.js.map

Time to add a check in the build system before releasing a version, to make sure everything is there :)

Sergio will have to look at this when he gets some time. He is the poor soul who does the release stuff. I have no clue how to debug this, much less push a new revision. (I have the instructions, just not a good idea to go doing it on my own.)

Yup, my bad, looks like I botched a step in the release process. This will be fixed in 1.0.2, which will be released once we have a few more fixes in.

1.1.2*

Indeed, 1.1.2, thank you, @surma :)

This has been fixed with the release of 1.1.2.


feat(controller): retry strategy support on daemon containers, fixes #13705

Addresses https://github.com/argoproj/argo-workflows/issues/13705
And https://github.com/argoproj/argo-workflows/issues/2963
Motivation
Add retryStrategy support to daemon container templates.
Some use cases require argo workflows features that aren't supported in resource template, f.e.

pod logs, statuses, and fails in the UI
passing input artifacts into the daemon container

Modifications
execution functions now consider "succeeded" daemoned nodes as failed
When a daemoned container completes execution, it is considered as failed, if it has a retry strategy it will retry.
the IP change in the node will cascade down to future executions.
Verification
added an examples to test locally

examples/dag-daemon-retry-strategy.yaml
examples/steps-daemon-retry-strategy.yaml

I simulated daemon failures by deleting the daemon pod manually

i added an E2E test and i can't get it to work on the CI (even though make test-functional works locally), any clue why?
the behavior of the controller is as if its built on main instead of on this branch


Support .blade.php files on Laravel

On native html files it works for me but I'm experiencing issues while trying to fold TW classes on .blade.php files while using Laravel Framework, e.g (this code does not being folded):
<x-app-layout>
    <x-slot name="header">

            {{ __('Dashboard') }}

    </x-slot>

                    {{ __("You're logged in!") }}

</x-app-layout>

I don't know much if the issue regards the file extension or code structure, bc Blade template files sometimes use custom tags like x-app-layout
Thanks 4 ur time

nvm I found #28

Further to this, while #28 does indeed work, any classes used within a Blade @class are not folded.
For example if you were to do something like this (which would always apply the first line of classes, and then only apply the second if the condition was true) ...
@class([
   'flex px-3 py-2 accent-primary w-full',
   'border-red-500' => $errors->has('name'),
])

... classes within that block are seemingly not folded. It would be nice if it could also look for those within @class([ ... ]).


Disable safe layout guidelines in the storyboards and set KinTestHost Deployment target to 8.1.

"Safe layout guides"


pyaudio Invalid number of channels

I ran the following snippet to initialize the recorder:
from RealtimeSTT import AudioToTextRecorder

recorder_config = {
        'spinner': False,
        'model': 'large-v2',
        'language': 'en',
        'silero_sensitivity': 0.4,
        'webrtc_sensitivity': 2,
        'post_speech_silence_duration': 0.4,
        'min_length_of_recording': 0,
        'min_gap_between_recordings': 0,
        'enable_realtime_transcription': True,
        'realtime_processing_pause': 0.2,
        'realtime_model_type': 'tiny.en',
        'compute_type': 'int8',
    }

recorder = AudioToTextRecorder(**recorder_config)

However I receive the error
ERROR:root:Error initializing pyaudio audio recording: [Errno -9998] Invalid number of channels OSError: [Errno -9998] Invalid number of channels
This seems to originate from the audio_interface.open call within audio_recorder.py. Running python 3.11 in a virtual environment on mac m3.

The error [Errno -9998] Invalid number of channels in PyAudio indicates that the audio device you're trying to use does not support the mono (1 channel) recording as required by RealtimeSTT. You might resolve this issue by selecting a different input_device_index that corresponds to a device supporting mono input.


Trying To Remove Api Key & Get Error: Output 'GraphQLAPIKeyOutput' not found in stack

Describe the bug
So when using amplify push after I have tried removing the use of API Key in graphql api using amplify update api I receive this error: Output 'GraphQLAPIKeyOutput' not found in stack
I have a lambda function that was setup to access this api. The above error seems to be related to my Serverless Express Lambda function.  I've tried different things and can't seem to figure out to how to get this to work without having to rebuild the api.
Amplify CLI Version
4.30.0
To Reproduce
Amplify Update Api
Remove Api Key
Amplify Push
Expected behavior
Should be able to push with no error.
Screenshots
Desktop (please complete the following information):

OS: Mac
Node Version: v12.18.3

Additional context
Basically I have been using API key until now as we are switching to authenticated requests through cognito user pool and groups. So just trying to make the switch and can't.

@lr001dev please follow the issue template and add all the missing information about versions, and repro steps to be able to help you better.

Closing due to lack of response.

@kaustavghosh06 I just updated the issue with the templated info, please reopen. Thanks!

Hello again, wondering if someone connect with me on this... This issue is holding up our development. Thank you!

Hello again, wondering if someone connect with me on this... This issue is holding up our development. Thank you!

@lr001dev I will mark this as a bug, You would need to remove the parameter in your function cfn at path amplify/backend/function/<resource-name>/<function-name>-cloudformation-template.json
    "api<project-name>GraphQLAPIKeyOutput": {
      "Type": "String",
      "Default": "apitagsGraphQLAPIKeyOutput"
    }

@lr001dev I will mark this as a bug, You would need to remove the parameter in your function cfn at path amplify/backend/function/<resource-name>/<function-name>-cloudformation-template.json
    "api<project-name>GraphQLAPIKeyOutput": {
      "Type": "String",
      "Default": "apitagsGraphQLAPIKeyOutput"
    }

Ok, removed the lines which appeared twice in the template file.. one instance with Default and the other with a Ref property. Then ran amplify update api and selected my new auth settings, coginito and iam. Ran amplify push and still received: UPDATE_FAILED               functiongroovesapi                        AWS::CloudFormation::Stack Sat Jan 23 2021 18:05:36 GMT-0800 (Pacific S tandard Time) Output 'GraphQLAPIKeyOutput' not found in stack 'arn:aws:cloudformation:us-west-2:907138769176:stack/amplify-groovestreambacken d-develop-14321-apigrooveql-13UPZZBG5VSKF/a92d64b0-fa55-11ea-bd2d-0239b11280c5'

Ok, removed the lines which appeared twice in the template file.. one instance with Default and the other with a Ref property. Then ran amplify update api and selected my new auth settings, coginito and iam. Ran amplify push and still received: UPDATE_FAILED               functiongroovesapi                        AWS::CloudFormation::Stack Sat Jan 23 2021 18:05:36 GMT-0800 (Pacific S tandard Time) Output 'GraphQLAPIKeyOutput' not found in stack 'arn:aws:cloudformation:us-west-2:907138769176:stack/amplify-groovestreambacken d-develop-14321-apigrooveql-13UPZZBG5VSKF/a92d64b0-fa55-11ea-bd2d-0239b11280c5'

Any other thoughts on this?

@lr001dev can you share the function's cloudformation template?

I can, how should I send @jhockett ?

@lr001dev copy + paste it here or you can email it to<EMAIL_ADDRESS>If you choose email, please include the issue number in the subject. Please redact anything sensitive before sharing either way.

I removed lambda role names as indicated by ""
{   "AWSTemplateFormatVersion": "2010-09-09",   "Description": "Lambda Function resource stack creation using Amplify CLI",   "Parameters": {     "CloudWatchRule": {       "Type": "String",       "Default": "NONE",       "Description": " Schedule Expression"     },     "env": {       "Type": "String"     },     "apigrooveqlGraphQLAPIIdOutput": {       "Type": "String",       "Default": "apigrooveqlGraphQLAPIIdOutput"     },     "apigrooveqlGraphQLAPIEndpointOutput": {       "Type": "String",       "Default": "apigrooveqlGraphQLAPIEndpointOutput"     }   },   "Conditions": {     "ShouldNotCreateEnvResources": {       "Fn::Equals": [         {           "Ref": "env"         },         "NONE"       ]     }   },   "Resources": {     "LambdaFunction": {       "Type": "AWS::Lambda::Function",       "Metadata": {         "aws:asset:path": "./src",         "aws:asset:property": "Code"       },       "Properties": {         "Handler": "index.handler",         "FunctionName": {           "Fn::If": [             "ShouldNotCreateEnvResources",             "groovesapi",             {               "Fn::Join": [                 "",                 [                   "groovesapi",                   "-",                   {                     "Ref": "env"                   }                 ]               ]             }           ]         },         "Environment": {           "Variables": {             "ENV": {               "Ref": "env"             },             "REGION": {               "Ref": "AWS::Region"             },             "API_GROOVEQL_GRAPHQLAPIIDOUTPUT": {               "Ref": "apigrooveqlGraphQLAPIIdOutput"             },             "API_GROOVEQL_GRAPHQLAPIENDPOINTOUTPUT": {               "Ref": "apigrooveqlGraphQLAPIEndpointOutput"             }           }         },         "Role": {           "Fn::GetAtt": [             "LambdaExecutionRole",             "Arn"           ]         },         "Runtime": "nodejs12.x",         "Layers": [],         "Timeout": "25",         "Code": {           "S3Bucket": "amplify-groovestreambackend-develop-14321-deployment",           "S3Key": "amplify-builds/groovesapi-6953734939335862514b-build.zip"         }       }     },     "LambdaExecutionRole": {       "Type": "AWS::IAM::Role",       "Properties": {         "RoleName": {           "Fn::If": [             "ShouldNotCreateEnvResources",             "",             {               "Fn::Join": [                 "",                 [                   "",                   "-",                   {                     "Ref": "env"                   }                 ]               ]             }           ]         },         "AssumeRolePolicyDocument": {           "Version": "2012-10-17",           "Statement": [             {               "Effect": "Allow",               "Principal": {                 "Service": [                   "lambda.amazonaws.com"                 ]               },               "Action": [                 "sts:AssumeRole"               ]             }           ]         }       }     },     "lambdaexecutionpolicy": {       "DependsOn": [         "LambdaExecutionRole"       ],       "Type": "AWS::IAM::Policy",       "Properties": {         "PolicyName": "lambda-execution-policy",         "Roles": [           {             "Ref": "LambdaExecutionRole"           }         ],         "PolicyDocument": {           "Version": "2012-10-17",           "Statement": [             {               "Effect": "Allow",               "Action": [                 "logs:CreateLogGroup",                 "logs:CreateLogStream",                 "logs:PutLogEvents"               ],               "Resource": {                 "Fn::Sub": [                   "arn:aws:logs:${region}:${account}:log-group:/aws/lambda/${lambda}:log-stream:*",                   {                     "region": {                       "Ref": "AWS::Region"                     },                     "account": {                       "Ref": "AWS::AccountId"                     },                     "lambda": {                       "Ref": "LambdaFunction"                     }                   }                 ]               }             }           ]         }       }     },     "AmplifyResourcesPolicy": {       "DependsOn": [         "LambdaExecutionRole"       ],       "Type": "AWS::IAM::Policy",       "Properties": {         "PolicyName": "amplify-lambda-execution-policy",         "Roles": [           {             "Ref": "LambdaExecutionRole"           }         ],         "PolicyDocument": {           "Version": "2012-10-17",           "Statement": [             {               "Effect": "Allow",               "Action": [                 "appsync:Create*",                 "appsync:StartSchemaCreation",                 "appsync:GraphQL",                 "appsync:Get*",                 "appsync:List*",                 "appsync:Update*"               ],               "Resource": [                 {                   "Fn::Join": [                     "",                     [                       "arn:aws:appsync:",                       {                         "Ref": "AWS::Region"                       },                       ":",                       {                         "Ref": "AWS::AccountId"                       },                       ":apis/",                       {                         "Ref": "apigrooveqlGraphQLAPIIdOutput"                       },                       "/*"                     ]                   ]                 }               ]             }           ]         }       }     }   },   "Outputs": {     "Name": {       "Value": {         "Ref": "LambdaFunction"       }     },     "Arn": {       "Value": {         "Fn::GetAtt": [           "LambdaFunction",           "Arn"         ]       }     },     "Region": {       "Value": {         "Ref": "AWS::Region"       }     },     "LambdaExecutionRole": {       "Value": {         "Ref": "LambdaExecutionRole"       }     }   } }

Any love on this?

@jhockett Possible to get an update on this issue? Any info would be helpful. Thank you!

Also having the same issue now. I haven't touched this project for a while, the api key must have expired and now I'm trying to push using CI/CD and it just keeps on failing, I'm tried to set "CreateAPIKey": 0 on parameters.json and this error appeared.

@lr001dev Do you still want to grant the function access to the API? If so we merged a PR which warns to reselect API in order to update the access to the API.
PR: https://github.com/aws-amplify/amplify-cli/pull/4923

I think the error is that the apiKey is not yet generated but the function depends on it. I think remove the API from resources of the function.

@lr001dev Do you still want to grant the function access to the API? If so we merged a PR which warns to reselect API in order to update the access to the API.
PR: https://github.com/aws-amplify/amplify-cli/pull/4923

Ideally yes...

@SwaySway So re-adding the Api Key for the api I was trying to initially removing from.,, then removing it again, then going to the function that is dependent on the api and running amplify update function and re-added the dependency did indeed fix the error. I did see the tip in the console letting me know to re-add the dependency. So that worked!

Closing this issue - should you experience any issues with re-assigning function permission to api please comment below.


use a semaphore to limit concurrent requests to the Hub API

Too many concurrent AsyncHTTPClient requests can result in TimeoutErrors
limit enforced with a Semaphore on Launcher
switching to pycurl may have alleviated this, but let's double-up the protection.
use c.Launcher.concurrency config to change the limit. Default is 10.
TODO:

[x] expose limit config via helm chart

I don't think we need this


[BUG] Xlsx exporter overwrites headers and then parser fails

Describe the bug
Xlsx exporter eats the headers.
To Reproduce
Steps to reproduce the behavior:

Export Xlsx
Import back to ts
Get error "Invalid XLSX file, check the headers!"

Expected behavior
Not have an error.
Desktop (please complete the following information):

OS windows
4.5.0

Additional context
Offending line: Xlsxbuilder.cpp:41
Reasoning:

add row if it's the first one. It's never first one (to be fair i see there is a commit that makes the header optional)
parser has similar issue which then parses the header line, even if it's also checking them

We have encountered the same error. Even though the xlsx file contains the correct header line as first line in the document.
I figured the parser always expects on import that the version info is present on the first 2 rows and looks for the header line on the 3rd row. Version output can be omitted at export by setting the parameter "--no-version".
XslxParser.cpp:22:
  const auto appVersion       = qApp->applicationVersion();     const auto currentVersion   = QVersionNumber::fromString(appVersion);     const auto TsSupportVersion = QVersionNumber(4, 5, 0);     InOutParameter p{ "", "", m_ioParameter.tsVersion, {} };     if (QVersionNumber::compare(currentVersion, TsSupportVersion) >= 0) {         p.tsVersion = xlsx.read(2, 1).toString();         offsetRow   = 2;     }
IMO it should be checked that the document contains the ts version info and only if present advance by 2 rows:
if (QVersionNumber::compare(currentVersion, TsSupportVersion) >= 0) {         if (xlsx.read(1,1) == TitleHeader::TsVersion) {             p.tsVersion = xlsx.read(2, 1).toString();             offsetRow   = 2;         } }


Add np.broadcast_to(scalar_array, ())

This PR adds a special case where the input to np.broadcast_to is a scalar array + empty shape.

The test failure looks unrelated, rest LGTM!

Yes, this should be fixed with #8354 -- but you may need to merge in main b/c RTD will build a PR against the branch head and not the branch merge, so the build doesn't include any fixes from main (unlike Azure).

CI failure is not related to this PR.

CI failure is not related to this PR.

Failed test was: ERROR: test_np_MachAr_deprecation_np122 (numba.tests.test_np_functions.TestNPMachineParameters). It indeed seems unrelated.

Running on the Anaconda Internal Build farm as numba_smoketest_cpu_yaml_138.

Running on the Anaconda Internal Build farm as numba_smoketest_cpu_yaml_138.

This was all green 🍏 -- but probably will need another review after @stuartarchibald 's comments have been addressed.

Build numba_smoketest_cpu_yaml_141 has started

@esc, can you please re-run this PR in the build farm?

Build numba_smoketest_cpu_yaml_141 has started

This was fine, again! Now waiting on a final sign-off from @stuartarchibald .


Update step_six.md

Proposed changes
Changed a period to a comma so that the sentence makes sense.

Thanks, @snesneros :)


Clean up interface and data structures for V1.0

I'm not super happy with the data structures and interface right now.
Data structures
projector-input
Can just encode as (type . number) conses. Less type info but it's easier to work with.
projector-status
For this it makes sense to encode it as an alist or plist, and rather than :ok, use nil to signify 'no error':
example:
(:fan nil
 :lamp nil
 :temperature nil
 :cover-open :error
 :filter :warning
 :other nil)

projector-lamp
it might also make sense to not bother recording the number and also turn them into (hours . status) conses. The lamp number would be implicit in the list.
projector-resolution
Ditto on simple (horizontal . vertical) resolution
Interface
Basically I'm not sure if the extra trouble I'm going through to support pjlink-config is worthwhile.
The point of having the extra method is to save users from having to pass all the necessary keyword args (primarily :password) repeatedly.
In the future I want to implement some sort of 'keep-alive' connection for cases where many commands are being done in a short time, so that could be enough for the case where the user would have to specify all the &key params.
It would also be better for security purposes since the connection need only remember the connection digest, not the actual password. And even that could be thrown away after first command.

Changed out classes for conses and alists in https://github.com/Zulu-Inuoe/pjlink/commit/f1ac11401144d3243f56121986e201e810c4d1fd
I'll see how I like it for now.
As per the persistent connection, I'll leave it as it is for now and tackle it in some future version


(Enhancement) Suggestion to incorporate GPTQ adapter merging into axolotl library

Hi,
There's been serious issues, still unresolved at this point, with merging qLora adapters easily and accurately without losing perplexity and finetuning quality. See https://github.com/huggingface/transformers/issues/26492 for example.
Think your technique can be really useful in improving the usefulness of 4-bit lora tuning. Would you consider contributing this technique to the axolotl library, which already has GPTQ training with flash attention, and is popular among OSS model trainers:
https://github.com/OpenAccess-AI-Collective/axolotl
As far as I know, the library does not permit merging GPTQ adapters. If your technique goes in - it will be really helpful to the community!!

Hi,
There's been serious issues, still unresolved at this point, with merging qLora adapters easily and accurately without losing perplexity and finetuning quality. See https://github.com/huggingface/transformers/issues/26492 for example.
Think your technique can be really useful in improving the usefulness of 4-bit lora tuning. Would you consider contributing this technique to the axolotl library, which already has GPTQ training with flash attention, and is popular among OSS model trainers:
https://github.com/OpenAccess-AI-Collective/axolotl
As far as I know, the library does not permit merging GPTQ adapters. If your technique goes in - it will be really helpful to the community!!

Thanks for your suggestion. It is quite interesting. I am not familiar with the axolotl repo. But I may merge with it in the future.


Stuck in infinite loop

Consider this sequence:
C# > interface ITest { public void Test(); }

C# > typeof(ITest).GetMethods()

At this point, dotnet-repl seems to go into some kind of infinite loop and becomes unresponsive while using large amounts of CPU.

I'm not familiar with this code yet, but it looks like it's trying to render a graph of objects that has a loop in it.

This is the same problem as #8. The recursion depth check is not in place like it is in the default .NET Interactive formatters.


 It will require detailed testing and review before I can merge it, so expect it to take a little longer than most pull requests.

Server crashes on player disconnect for failing to handle PlayerDisconnectException. All exceptions thrown from packet handlers should be handled gracefully - and PlayerDisconnectException is intentionally thrown from the disconnect handler.

Style convention errors here, too - private variables are likeThis, not _likeThis.

The exception is if you have a variable that's backing a property you need to raise PropertyChanged from.

Done.

:tada: