Feature

The Glowing Spheres bonus stage update is complete and ready to be merged back into master.

Absolutely amazing job! This looks and feels exactly like the original, I am so impressed.
A small change you should make to how checkpoints work. Tails as player 2 can hit checkpoints which will not spawn the BonusStage Portal even if player 1 has enough rings. In both Mania and 3k player 2 can't hit checkpoints, so if you want to allow player 2 to hit checkpoints use player 1's ring count to check whether or not to spawn the BonusStage Portal.
Unless it's split screen multiplayer mode. In the case, probably just disable Bonus Stages perhaps?

Absolutely amazing job! This looks and feels exactly like the original, I am so impressed.
A small change you should make to how checkpoints work. Tails as player 2 can hit checkpoints which will not spawn the BonusStage Portal even if player 1 has enough rings. In both Mania and 3k player 2 can't hit checkpoints, so if you want to allow player 2 to hit checkpoints use player 1's ring count to check whether or not to spawn the BonusStage Portal.
Unless it's split screen multiplayer mode. In the case, probably just disable Bonus Stages perhaps?

Thank you for the kind words. I agree with your proposals regarding checkpoints and multiplayer functionality, so I will add one more update to clear out those issues before finally merging into master. Please let me know if you run into any other issues regarding the bonus stage in particular.


adding results files to the tutorial for comparison

Hi,
Would it be possible for you to add results files that correspond to the test data set you made available here?
I finished a successful run of this pipeline and I would like to compare my results with yours.
Thanks much in advance.
--Gloria

Hi Gloria,
Glad you got it working. I am heading out of town for vacation tomorrow so don’t think I will get to it until first week of April. I don’t think we have a results file for the tutorial (if we kept it, it would be in the github repo I think). We have data from our benchmarking study (McCrone and Lauring JVI 2016) - there are links in that paper to the actual fastq files as well as the github repo for that paper.

Adam

On Mar 22, 2019, at 4:51 PM, grendon<EMAIL_ADDRESS>wrote:
Hi,
Would it be possible for you to add results files that correspond to the test data set you made available here?
I finished a successful run of this pipeline and I would like to compare my results with yours.
Thanks much in advance.
--Gloria
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/lauringlab/variant_pipeline/issues/16, or mute the thread https://github.com/notifications/unsubscribe-auth/AKC-HKXikxl8kUjW2T6yMnhlRDzYkereks5vZUJmgaJpZM4cEZZk.


[BUG] Godot 4

Describe the bug
When adding the plugin in Godot 4.0.2 , you get a lot of errors with the plugin.gd file.
To Reproduce
Steps to reproduce the behavior:

Open Godot 4.0.2, and create a new project.
Add the addon to the new project.
Attempt to enable to addon (fails), and then check plugin.gd file in the discord presence folder.
You can now see the many errors and why it does not work.

Expected behavior
The addon/plugin to work with Godot 4.0.2.
Screenshots

I removed the random tool at the top:

Desktop (please complete the following information):

OS: [e.g. iOS]
Plugin Version: [e.g. 1.2.5]
Godot Version:  [e.g. 4.0.2]

Additional context
Add any other context about the problem here.
Checklist

[x] I have checked for duplicate issues.
[x] I have provided a detailed description of the issue.
[x] I have provided reproduction steps (if applicable).

This is expected. The plugin currently is only for Godot 3.x as such it cannot be used in Godot 4.x. A port to Godot 4 is underway. You can see the progress here #11


AutoWidth

Hey guys,
Is AutoWidth implemented in your lovely component?

I just added it and published to npm!


Incorrect SPEC - multiple public keys for "reference"

According to the official spec we are allowed to use multiple public keys for reference, and indeed the encodeURL API from Solana Pay allows us to pass an array of public keys for this.
However, while trying to find the transaction signature - we use the getSignaturesForAddress API from Solana which expects this field to be a single public key.
Due to this, the findTransactionSignature API from Solana pay only accepts a single public key. This means that we can't effectively use multiple public keys for the reference field 😦
Is this correct? If so, the documentation need to be corrected.

I responded on Discord, but this isn't a bug. The spec allows for multiple reference keys, and the reference implementation will encode them and parse them from a URL.
As you pointed out, getSignaturesForAddress will only allow one key, and findTransactionSignature uses this. If you want to make sure a transaction references multiple keys, you could use getSignaturesForAddress with one of them, and then further check that the other keys are also referenced as accounts.


fix: incorrect error when sending txn with insufficient funds

Description
In summary, we get this error :

While sending value i.e greater than our wallet balance, Ideally it should have given us "Sender doesn't have enought fund...." error
Check out https://github.com/wagmi-dev/wagmi/issues/3155 for full context
Removing chainId from useContractWrite solves this problem, We could also wait until https://github.com/wagmi-dev/wagmi/issues/3155 is fixed and close this 🙌

Thanks @technophile-04 ! And thanks for the review.
Yep, maybe we don't need chainId in the write hook after all: https://github.com/scaffold-eth/scaffold-eth-2/pull/584#discussion_r1371101002
I guess we do need it on the Read hooks (in case no wallet is connected) and ofc in the ENS ones (where we always want to look up mainnet)


Can't import the package

Trying to import like this
        "github.com/ernyoke/imger/grayscale"
	"github.com/ernyoke/imger/threshold"

and go get -u github.com/ernyoke/imger/grayscale and go get -u github.com/ernyoke/imger/threshold
Somehow grayscale imports fine, but then I get
go: finding module for package github.com/ernyoke/imger/threshold
github.com/monzo/wearedev/service.cheque-image-processor/domain imports
        github.com/ernyoke/imger/threshold: module github.com/ernyoke/imger@latest found (v0.1.0), but does not contain package github.com/ernyoke/imger/threshold

Note the capitalisation ernyoke/imger, as otherwise
 go get github.com/Ernyoke/Imger
go<EMAIL_ADDRESS>parsing go.mod:
        module declares its path as: github.com/ernyoke/imger
                but was required as: github.com/Ernyoke/Imger

I was able to work around this with
go get github.com/Ernyoke/Imger@55700becd332

Hi Albert,
Thank you for reporting this issue.
I suggest you should use go get -u<EMAIL_ADDRESS>The golang cache from google had an erroneous version of this project for version numbers bellow 1.0.0`.
Let me know if there are other issues you are facing.
Apologies for the late response,
Ervin


feat:Standard live preview ECO-183

Title: Standard live preview implementation
Changes: Enabling/Disabling live preview & live edit from config parameters.
Jira: https://contentstack.atlassian.net/browse/ECO-183

Closing this branch due to conflict in package.json & package-lock.json


find_peaks_cwt custom wavelet definition via a 1-D vector rather than callable

Should 'wavelet' be changed to accept any normalized 1-D array that describes the pattern of the peak you are searching for? Or at least to easily accept the distributions available in 'scipy.stats'?  It seems cumbersome to change the wavelet to anything other than Ricker (aka Mexican hat).
Ideally, I would like to pass any vector into the 'wavelet' parameter to be used as a model of the shape for which I expect to find peaks.
Can the documentation can be expanded to show additional examples that demonstrate use all of the parameters?  It would be great to have a visual for how the function behaves depending on how the parameters are adjusted.  Thanks!

Further work on this would be fine. However, the original contributor of
the code is probably not around any more, so this requires someone to go
through how the algorithm works again.

It should be possible to specify a numpy vector inside the lambda sent into the wavelet argument. Therefore, I think this issue should be closed. CC: @rgommers


Reducing heap usage

The entire dataset is loaded into a TreeMap . Make sure that you have about 3 GB of Heap space available to load it.

3GB might be too much for some apps. Heap usage can be brought down by interning city/province strings in ResourceImporter. I was able to get down heap usage from 2.4G to 1.7G by interning strings.
Further, by using integer instead of InetAddress in GeoAttributes, the heap usage further came down to 1.3G.  (Not that this won't affect the API, which will still accept InetAddress).
I think the gains are significant, and I'd be happy to create a pull request for the same. Let me know what you think!

Hello Jatin.
Thanks for the feedback. This project was made in quite a hurry. I had to
get rid of another system that was built on Redis and had only 3-4 days to
build this one. I must profess of having limited knowledge of 'interning
strings', but whole heartedly agree with your second one.
I agree on the point that the gains would indeed be significant. Feel free
to make a pull request, by all means!
Thank you.
Ankush.
On Sat, Jan 21, 2017 at 5:22 PM, jatins<EMAIL_ADDRESS>wrote:

The entire dataset is loaded into a TreeMap . Make sure that you have
about 3 GB of Heap space available to load it.
3GB might be too much for some apps. Heap usage can be brought down by
interning city/province strings in ResourceImporter. I was able to get
down heap usage from 2.4G to 1.7G by interning strings.
Further, by using integer instead of InetAddress in GeoAttributes, the
heap usage further came down to 1.3G. (Not that this won't affect the API,
which will still accept InetAddress).
I think the gains are significant, and I'd be happy to create a pull
request for the same. Let me know what you think!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ankushs92/Java-DB-IP/issues/14, or mute the thread
https://github.com/notifications/unsubscribe-auth/AHVhCJbs20fAZ-UmVlNou67vkjXxV4Kmks5rUfFhgaJpZM4LqDCB
.

Created pull request #15

Thanks , I'll update on maven soon enough.


optimize: optimize read of storage configuration

Signed-off-by: slievrly<EMAIL_ADDRESS>

[x] I have registered the PR changes.

Ⅰ. Describe what this PR did
optimize read of storage configuration

ParameterParser  only responsible for startup parameters
storeMode,  sessionMode, lockMode  aggregated into  StoreConfig,  to avoid using getConfig everywhere.
storeMode,  sessionMode, lockMode ignore case.
resolved  not recognized license by SW-eyes

Ⅱ. Does this pull request fix one issue?

fixes #4916 #4923 #4937
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #4936 (d009da5) into develop (a986644) will increase coverage by 0.06%.
The diff coverage is 53.92%.

@@              Coverage Diff              @@
##             develop    #4936      +/-   ##
=============================================
+ Coverage      49.20%   49.26%   +0.06%
- Complexity      4111     4115       +4
=============================================
  Files            736      734       -2
  Lines          25800    25833      +33
  Branches        3181     3187       +6
=============================================
+ Hits           12695    12727      +32
+ Misses         11763    11755       -8
- Partials        1342     1351       +9

Impacted Files
Coverage Δ

...in/java/io/seata/server/session/SessionHelper.java
65.95% <0.00%> (-0.71%)
:arrow_down:

...in/java/io/seata/server/session/SessionHolder.java
48.20% <31.81%> (ø)

...src/main/java/io/seata/server/ParameterParser.java
66.66% <33.33%> (+0.59%)
:arrow_up:

...ava/io/seata/server/lock/LockerManagerFactory.java
56.25% <50.00%> (+20.95%)
:arrow_up:

...c/main/java/io/seata/server/store/StoreConfig.java
62.16% <60.29%> (-21.18%)
:arrow_down:

server/src/main/java/io/seata/server/Server.java
80.00% <100.00%> (-0.77%)
:arrow_down:

...ava/io/seata/server/ServerApplicationListener.java
43.18% <100.00%> (-2.48%)
:arrow_down:

LGTM


Go Panic on sst deploy using remix + cloudflare dns

I'm trying to deploy the default remix app using a custom domain hosted using cloudflare dns. (Now using v0.0.354 everything deploys properly when I don't cloudflare, thanks for addressing #386 !)
My sst.config.ts
/// <reference path="./.sst/platform/config.d.ts" />

export default $config({
  app(input) {
    return {
      name: "my-remix-app",
      removal: input?.stage === "production" ? "retain" : "remove",
      home: "aws",
      providers: { aws: true, cloudflare: true },
    };
  },
  async run() {
    new sst.aws.Remix("MyWeb", {
      domain: {
        name: "owen-remix-test.mydomain.org",
        dns: sst.cloudflare.dns(),
      }
    });
  },
});

Using sst version 0.0.354:
➜  my-remix-app sst deploy --verbose
time=2024-05-07T17:04:18.261-06:00 level=INFO msg="checking for pulumi" path="/Users/ocoutts/Library/Application Support/sst/bin/pulumi"
time=2024-05-07T17:04:18.599-06:00 level=INFO msg="checking for bun" path="/Users/ocoutts/Library/Application Support/sst/bin/bun"
time=2024-05-07T17:04:18.614-06:00 level=INFO msg="initializing project" version=0.0.354
time=2024-05-07T17:04:18.616-06:00 level=INFO msg="esbuild building"
time=2024-05-07T17:04:18.626-06:00 level=INFO msg="esbuild built" outfile=/Users/ocoutts/dev/my-remix-app/.sst/eval/eval-1715123058615.mjs
time=2024-05-07T17:04:18.626-06:00 level=INFO msg="evaluating config"
time=2024-05-07T17:04:18.783-06:00 level=INFO msg="config evaluated"
time=2024-05-07T17:04:18.784-06:00 level=INFO msg="checking platform"
time=2024-05-07T17:04:18.785-06:00 level=INFO msg="checking provider" name=cloudflare version=latest compare=latest
time=2024-05-07T17:04:18.785-06:00 level=INFO msg="checking provider" name=aws version=latest compare=latest
time=2024-05-07T17:04:18.787-06:00 level=INFO msg="credentials found"
panic: runtime error: index out of range [0] with length 0

goroutine 1 [running]:
github.com/sst/ion/pkg/project/provider.(*CloudflareProvider).Init(0x140007cecf0, {0x140007ce930?, 0x14000681e69?}, {0x3?, 0x7?}, 0x140007ce780)
	/home/runner/work/ion/ion/pkg/project/provider/cloudflare.go:68 +0x458
github.com/sst/ion/pkg/project.(*Project).LoadHome(0x140001f0000)
	/home/runner/work/ion/ion/pkg/project/project.go:243 +0x19c
main.initProject(0x140001ac5a0)
	/home/runner/work/ion/ion/cmd/sst/main.go:1600 +0x650
main.init.func3(0x140001ac5a0)
	/home/runner/work/ion/ion/cmd/sst/main.go:435 +0x38
main.run()
	/home/runner/work/ion/ion/cmd/sst/main.go:159 +0x6cc
main.main()
	/home/runner/work/ion/ion/cmd/sst/main.go:51 +0x12c

I'm using:

An existing coudflare account.
A fresh aws account

@tallowen Do you have a CLOUDFLARE_DEFAULT_ACCOUNT_ID configured in your env? That does the trick for me

@markhker - thanks, setting that env variable did indeed fix it!

I had a slightly similar issue with Remix + Cloudflare (exposed Go error).
Logs:
sst deploy --verbose
time=2024-05-08T10:41:19.080-03:00 level=INFO msg="checking for pulumi" path="/Users/ruan/Library/Application Support/sst/bin/pulumi"
time=2024-05-08T10:41:19.390-03:00 level=INFO msg="checking for bun" path="/Users/ruan/Library/Application Support/sst/bin/bun"
time=2024-05-08T10:41:19.407-03:00 level=INFO msg="initializing project" version=0.0.355
time=2024-05-08T10:41:19.407-03:00 level=INFO msg="esbuild building"
time=2024-05-08T10:41:19.409-03:00 level=INFO msg="esbuild built" outfile=/Users/ruan/Desktop/sst-rmx/.sst/eval/eval-1715175679407.mjs
time=2024-05-08T10:41:19.409-03:00 level=INFO msg="evaluating config"
time=2024-05-08T10:41:19.518-03:00 level=INFO msg="config evaluated"
time=2024-05-08T10:41:19.519-03:00 level=INFO msg="checking platform"
panic: interface conversion: interface {} is nil, not map[string]interface {}

goroutine 1 [running]:
github.com/sst/ion/pkg/project.(*Project).NeedsInstall(0x140000fc600)
	/home/runner/work/ion/ion/pkg/project/install.go:25 +0x29c
main.initProject(0x140006d20f0)
	/home/runner/work/ion/ion/cmd/sst/main.go:1591 +0x574
main.init.func3(0x140006d20f0)
	/home/runner/work/ion/ion/cmd/sst/main.go:435 +0x38
main.run()
	/home/runner/work/ion/ion/cmd/sst/main.go:159 +0x6cc
main.main()
	/home/runner/work/ion/ion/cmd/sst/main.go:51 +0x12c

sst.config.ts:
export default $config({
  app(input) {
    return {
      name: "sst-remix",
      removal: input?.stage === "production" ? "retain" : "remove",
      home: "cloudflare",
    };
  },
  async run() {
    new sst.cloudflare.Remix("MyWeb");
  },
});

The issue is that I didn't install the Cloudflare provider (obvious I know, but I'm new to SST and the docs don't mention that). Only the AWS provider is installed by default.
sst add cloudflare solved it for me, posting it in case it helps anyone.

is this still an issue in the latest sst? thought i handled the case when there's no account id able to be inferred

@thdxr - should version 0.0.354 have the fix? That version (I believe from yesterday) does have at least the issue when CLOUDFLARE_DEFAULT_ACCOUNT_ID is not set.

I'm getting a slightly different error, not sure if it is related to this or not. I cloned the ion repo and tried running the cloudflare-remix example, added a .env file with the CLOUDFLARE_API_TOKEN and CLOUDFLARE_DEFAULT_ACCOUNT_ID values set.
Error:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x15ac83b]goroutine 107 [running]:
github.com/sst/ion/pkg/project.(*stack).Run(0xc00098c080, {0x2ae8308, 0xc000b5c5a0}, 0xc00079bcc0)
	/home/runner/work/ion/ion/pkg/project/stack.go:535 +0x347b
github.com/sst/ion/pkg/server.startDeployer.func2()
	/home/runner/work/ion/ion/pkg/server/deployer.go:33 +0x166
created by github.com/sst/ion/pkg/server.startDeployer in goroutine 1
	/home/runner/work/ion/ion/pkg/server/deployer.go:30 +0x1b9

Verbose logs
time=2024-05-18T13:21:35.830-04:00 level=INFO msg="checking for pulumi" path=/home/robb/.config/sst/bin/pulumi
time=2024-05-18T13:21:36.004-04:00 level=INFO msg="checking for bun" path=/home/robb/.config/sst/bin/bun
time=2024-05-18T13:21:36.010-04:00 level=INFO msg=args args="[remix dev]" length=2
time=2024-05-18T13:21:36.010-04:00 level=INFO msg="connecting to server" addr=<IP_ADDRESS>:13557
time=2024-05-18T13:21:36.011-04:00 level=INFO msg="no existing server found, starting new one"
time=2024-05-18T13:21:36.011-04:00 level=INFO msg="waiting for server to start"
time=2024-05-18T13:21:36.039-04:00 level=INFO msg="checking for pulumi" path=/home/robb/.config/sst/bin/pulumi
time=2024-05-18T13:21:36.184-04:00 level=INFO msg="checking for bun" path=/home/robb/.config/sst/bin/bun
time=2024-05-18T13:21:36.186-04:00 level=INFO msg="initializing project" version=0.0.373
time=2024-05-18T13:21:36.186-04:00 level=INFO msg="esbuild building"
time=2024-05-18T13:21:36.189-04:00 level=INFO msg="esbuild built" outfile=/home/robb/Code/ion/examples/cloudflare-remix/.sst/eval/eval-1716052896186.mjs
time=2024-05-18T13:21:36.189-04:00 level=INFO msg="evaluating config"
time=2024-05-18T13:21:36.226-04:00 level=INFO msg="config evaluated"
time=2024-05-18T13:21:36.226-04:00 level=INFO msg="checking platform"
time=2024-05-18T13:21:36.226-04:00 level=INFO msg="checking provider" name=cloudflare version=latest compare=latest
time=2024-05-18T13:21:36.226-04:00 level=INFO msg="cloudflare account selected" account=20345ff0f6029a679752211d8c3acfdd
time=2024-05-18T13:21:37.598-04:00 level=INFO msg="found existing bucket" bucket=sst-state
time=2024-05-18T13:21:37.598-04:00 level=INFO msg="loaded config" app=cloudflare-remix stage=robb
time=2024-05-18T13:21:37.599-04:00 level=INFO msg=server addr=<IP_ADDRESS>:13557
time=2024-05-18T13:21:37.599-04:00 level=INFO msg=subscribed type=*project.StackEvent
time=2024-05-18T13:21:37.599-04:00 level=INFO msg=subscribed type=*watcher.FileChangedEvent
time=2024-05-18T13:21:37.599-04:00 level=INFO msg=subscribed type=*aws.FunctionInvokedEvent
time=2024-05-18T13:21:37.599-04:00 level=INFO msg=subscribed type=*aws.FunctionResponseEvent
time=2024-05-18T13:21:37.599-04:00 level=INFO msg=subscribed type=*aws.FunctionErrorEvent
time=2024-05-18T13:21:37.599-04:00 level=INFO msg=subscribed type=*aws.FunctionLogEvent
time=2024-05-18T13:21:37.599-04:00 level=INFO msg=subscribed type=*project.StackEvent
time=2024-05-18T13:21:37.599-04:00 level=INFO msg=watching path=/home/robb/Code/ion/examples/cloudflare-remix
time=2024-05-18T13:21:37.599-04:00 level=INFO msg=watching path=/home/robb/Code/ion/examples/cloudflare-remix/app
time=2024-05-18T13:21:37.599-04:00 level=INFO msg=watching path=/home/robb/Code/ion/examples/cloudflare-remix/app/routes
time=2024-05-18T13:21:37.600-04:00 level=INFO msg=watching path=/home/robb/Code/ion/examples/cloudflare-remix/public
time=2024-05-18T13:21:37.601-04:00 level=INFO msg=subscribed type=*watcher.FileChangedEvent
time=2024-05-18T13:21:37.601-04:00 level=INFO msg=subscribed type=*server.DeployRequestedEvent
time=2024-05-18T13:21:37.601-04:00 level=INFO msg=subscribed type=*project.StackEvent
time=2024-05-18T13:21:37.601-04:00 level=INFO msg="running stack command" cmd=uptime=2024-05-18T13:21:37.601-04:00 level=INFO msg=publishing type=*project.StackEvent
time=2024-05-18T13:21:37.601-04:00 level=INFO msg=publishing type=*watcher.FileChangedEventtime=2024-05-18T13:21:37.601-04:00 level=INFO msg="INFO locking app=cloudflare-remix stage=robb"
time=2024-05-18T13:21:37.601-04:00 level=INFO msg="INFO getting data key=lock app=cloudflare-remix stage=robb"time=2024-05-18T13:21:37.618-04:00 level=INFO msg="connecting to server" addr=<IP_ADDRESS>:13557time=2024-05-18T13:21:37.619-04:00 level=INFO msg=subscribed addr=<IP_ADDRESS>:38286time=2024-05-18T13:21:37.619-04:00 level=INFO msg=subscribed type=*aws.FunctionInvokedEventtime=2024-05-18T13:21:37.619-04:00 level=INFO msg=subscribed type=*aws.FunctionResponseEvent
time=2024-05-18T13:21:37.619-04:00 level=INFO msg=subscribed type=*aws.FunctionErrorEventtime=2024-05-18T13:21:37.619-04:00 level=INFO msg=subscribed type=*aws.FunctionLogEvent
time=2024-05-18T13:21:37.619-04:00 level=INFO msg=subscribed type=*project.StackEventtime=2024-05-18T13:21:37.619-04:00 level=INFO msg=subscribed type=*aws.FunctionBuildEventtime=2024-05-18T13:21:37.619-04:00 level=INFO msg=subscribed type=*cloudflare.WorkerBuildEvent
time=2024-05-18T13:21:37.619-04:00 level=INFO msg=subscribed type=*cloudflare.WorkerUpdatedEventtime=2024-05-18T13:21:37.619-04:00 level=INFO msg=subscribed type=*cloudflare.WorkerInvokedEvent
time=2024-05-18T13:21:37.622-04:00 level=INFO msg="got server stream"time=2024-05-18T13:21:37.624-04:00 level=INFO msg="file event" path=/home/robb/Code/ion/examples/cloudflare-remix/out.txt op=WRITE
time=2024-05-18T13:21:37.624-04:00 level=INFO msg=publishing type=*watcher.FileChangedEvent
time=2024-05-18T13:21:37.624-04:00 level=INFO msg="file event" path=/home/robb/Code/ion/examples/cloudflare-remix/out.txt op=WRITEtime=2024-05-18T13:21:37.624-04:00 level=INFO msg="file event" path=/home/robb/Code/ion/examples/cloudflare-remix/out.txt op=WRITE
time=2024-05-18T13:21:37.624-04:00 level=INFO msg="file event" path=/home/robb/Code/ion/examples/cloudflare-remix/out.txt op=WRITEtime=2024-05-18T13:21:37.625-04:00 level=INFO msg="file event" path=/home/robb/Code/ion/examples/cloudflare-remix/out.txt op=WRITEtime=2024-05-18T13:21:37.625-04:00 level=INFO msg="file event" path=/home/robb/Code/ion/examples/cloudflare-remix/out.txt op=WRITEtime=2024-05-18T13:21:38.101-04:00 level=INFO msg=publishing type=*watcher.FileChangedEventtime=2024-05-18T13:21:38.519-04:00 level=INFO msg="INFO putting data key=lock app=cloudflare-remix stage=robb"time=2024-05-18T13:21:38.601-04:00 level=INFO msg=publishing type=*watcher.FileChangedEventtime=2024-05-18T13:21:39.101-04:00 level=INFO msg=publishing type=*watcher.FileChangedEvent
time=2024-05-18T13:21:39.380-04:00 level=INFO msg="INFO pulling state app=cloudflare-remix stage=robb out=/home/robb/Code/ion/examples/cloudflare-remix/.sst/.pulumi/stacks/cloudflare-remix/robb.json"
time=2024-05-18T13:21:39.601-04:00 level=INFO msg=publishing type=*watcher.FileChangedEvent
time=2024-05-18T13:21:40.101-04:00 level=INFO msg=publishing type=*watcher.FileChangedEvent
time=2024-05-18T13:21:40.362-04:00 level=INFO msg="INFO getting passphrase app=cloudflare-remix stage=robb"time=2024-05-18T13:21:40.601-04:00 level=INFO msg=publishing type=*watcher.FileChangedEventtime=2024-05-18T13:21:41.065-04:00 level=INFO msg="INFO getting data key=secret app=cloudflare-remix stage=robb"time=2024-05-18T13:21:41.101-04:00 level=INFO msg=publishing type=*watcher.FileChangedEventtime=2024-05-18T13:21:41.601-04:00 level=INFO msg=publishing type=*watcher.FileChangedEventtime=2024-05-18T13:21:41.897-04:00 level=INFO msg="esbuild building"
time=2024-05-18T13:21:41.952-04:00 level=INFO msg="esbuild built" outfile=/home/robb/Code/ion/examples/cloudflare-remix/.sst/platform/eval/eval-1716052901897.mjs
time=2024-05-18T13:21:41.957-04:00 level=INFO msg="files changed" files=127
time=2024-05-18T13:21:41.957-04:00 level=INFO msg="tracked files"
time=2024-05-18T13:21:42.101-04:00 level=INFO msg=publishing type=*watcher.FileChangedEventtime=2024-05-18T13:21:42.122-04:00 level=INFO msg="built workspace"
time=2024-05-18T13:21:42.304-04:00 level=INFO msg="built stack"time=2024-05-18T13:21:42.479-04:00 level=INFO msg="built config"
time=2024-05-18T13:21:42.479-04:00 level=INFO msg="running stack command" cmd=up
time=2024-05-18T13:21:42.480-04:00 level=INFO msg="stack command complete"
time=2024-05-18T13:21:42.601-04:00 level=INFO msg=publishing type=*watcher.FileChangedEventtime=2024-05-18T13:21:43.101-04:00 level=INFO msg=publishing type=*watcher.FileChangedEvent
time=2024-05-18T13:21:43.244-04:00 level=INFO msg=publishing type=*project.StackEventtime=2024-05-18T13:21:43.244-04:00 level=INFO msg="INFO pushing state app=cloudflare-remix stage=robb from=/home/robb/Code/ion/examples/cloudflare-remix/.sst/.pulumi/stacks/cloudflare-remix/robb.json"
time=2024-05-18T13:21:43.245-04:00 level=INFO msg="file event" path=/home/robb/Code/ion/examples/cloudflare-remix/out.txt op=WRITE
time=2024-05-18T13:21:43.245-04:00 level=INFO msg=publishing type=*watcher.FileChangedEventtime=2024-05-18T13:21:43.245-04:00 level=INFO msg=done addr=<IP_ADDRESS>:38286
time=2024-05-18T13:21:43.245-04:00 level=INFO msg="file event" path=/home/robb/Code/ion/examples/cloudflare-remix/out.txt op=WRITE
time=2024-05-18T13:21:43.245-04:00 level=INFO msg="file event" path=/home/robb/Code/ion/examples/cloudflare-remix/out.txt op=WRITE
time=2024-05-18T13:21:43.245-04:00 level=INFO msg=unsubscribing type=*aws.FunctionInvokedEvent
time=2024-05-18T13:21:43.245-04:00 level=INFO msg=unsubscribing type=*cloudflare.WorkerInvokedEvent
time=2024-05-18T13:21:43.245-04:00 level=INFO msg=unsubscribing type=*aws.FunctionLogEvent
time=2024-05-18T13:21:43.245-04:00 level=INFO msg=unsubscribing type=*cloudflare.WorkerUpdatedEvent
time=2024-05-18T13:21:43.245-04:00 level=INFO msg="cleaning up deployer"
time=2024-05-18T13:21:43.245-04:00 level=INFO msg=unsubscribing type=*cloudflare.WorkerBuildEvent
time=2024-05-18T13:21:43.245-04:00 level=INFO msg=unsubscribing type=*project.StackEvent
time=2024-05-18T13:21:43.245-04:00 level=INFO msg=unsubscribing type=*aws.FunctionResponseEvent
time=2024-05-18T13:21:43.245-04:00 level=ERROR msg="exited with error" err="http: read on closed response body"
time=2024-05-18T13:21:43.245-04:00 level=INFO msg=unsubscribing type=*aws.FunctionBuildEvent
time=2024-05-18T13:21:43.245-04:00 level=INFO msg=unsubscribing type=*aws.FunctionErrorEvent
time=2024-05-18T13:21:43.245-04:00 level=INFO msg=unsubscribing type=*aws.FunctionErrorEvent
time=2024-05-18T13:21:43.245-04:00 level=INFO msg=unsubscribing type=*project.StackEvent
time=2024-05-18T13:21:43.245-04:00 level=INFO msg=unsubscribing type=*aws.FunctionLogEvent
time=2024-05-18T13:21:43.245-04:00 level=INFO msg=unsubscribing type=*server.DeployRequestedEvent
time=2024-05-18T13:21:43.245-04:00 level=INFO msg=unsubscribing type=*watcher.FileChangedEvent
time=2024-05-18T13:21:43.245-04:00 level=INFO msg=unsubscribing type=*aws.FunctionInvokedEvent
time=2024-05-18T13:21:43.245-04:00 level=INFO msg=unsubscribing type=*project.StackEvent
time=2024-05-18T13:21:43.245-04:00 level=INFO msg=unsubscribing type=*aws.FunctionResponseEvent
time=2024-05-18T13:21:43.245-04:00 level=INFO msg=unsubscribing type=*project.StackEvent
time=2024-05-18T13:21:43.245-04:00 level=INFO msg=unsubscribing type=*watcher.FileChangedEvent
time=2024-05-18T13:21:44.354-04:00 level=INFO msg="INFO unlocking app=cloudflare-remix stage=robb"
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x15ac83b]goroutine 107 [running]:
github.com/sst/ion/pkg/project.(*stack).Run(0xc00098c080, {0x2ae8308, 0xc000b5c5a0}, 0xc00079bcc0)
	/home/runner/work/ion/ion/pkg/project/stack.go:535 +0x347b
github.com/sst/ion/pkg/server.startDeployer.func2()
	/home/runner/work/ion/ion/pkg/server/deployer.go:33 +0x166
created by github.com/sst/ion/pkg/server.startDeployer in goroutine 1
	/home/runner/work/ion/ion/pkg/server/deployer.go:30 +0x1b9

Cloudflare API Token Summary

Hopefully that is helpful information.

still happening on 0.390 with no CLOUDFLARE_ACCOUNT_ID set

should be fixed in v0.0.412

Just hit this on v3.1.46. I hadn't added cloudflare as a provder. Adding the provider fixed the issue.
panic: interface conversion: interface {} is nil, not map[string]interface {}

goroutine 1 [running]:
github.com/sst/ion/pkg/project.(*Project).NeedsInstall(0xc0005de580)
        /home/runner/work/ion/ion/pkg/project/install.go:25 +0x2d0
github.com/sst/ion/cmd/sst/cli.(*Cli).InitProject(0xc000a9b180)
        /home/runner/work/ion/ion/cmd/sst/cli/project.go:84 +0x716
main.CmdDeploy(0xc000a9b180)
        /home/runner/work/ion/ion/cmd/sst/deploy.go:15 +0x33
github.com/sst/ion/cmd/sst/cli.(*Cli).Run(0xc000a9b180)
        /home/runner/work/ion/ion/cmd/sst/cli/cli.go:90 +0x124
main.run()
        /home/runner/work/ion/ion/cmd/sst/main.go:113 +0x1fe
main.main()
        /home/runner/work/ion/ion/cmd/sst/main.go:55 +0x4cb


Complete rewrite of Parser and Tokenizer

Decouple the Tokenizer and Parser:

No cross talk or dependency between Tokenizer and Parser for easier debugging.
Parser works purely on token list generated by Tokenizer.

Complete include parsing support:

Support required, file, url, and classpath keyword. Include types are passed to the HoconIncludeCallback delegate.
Support parsing hocon configuration that contains a pure array (should be used for array include only).
Include can be declared floating in an object (merged with the fields on the same level), assigned to a field key, and declared inside an array.
require, file, url, and classpath starting declaration needs to be typed exactly as "required(", "file(", "url(" and "classpath(" with no space between the keyword and the open parenthesis.
Change ExternalIncludes example to show how to use the new include implementation.

Complete self-referencing substitution support.

Support for the += array assignment operator.

Make Hocon parser to be completely free from Akka related implementation:

Configuration related classes are moved to Hocon.Configuration.
Create similar functionalities to Config class in HoconRoot class.
CONFIGURATION compiler directive is removed by bumping Hocon.Configuration netstandard version to 2.0 and including System.Configuration.ConfigurationManager package.

Add ability to normalize a parsed Hocon to minimize the memory footprint.

Add PrettyPrint feature to HoconRoot.

Add Infinity, -Infinity and NaN support for float and double value.

Add hexadecimal and octal value support for long, int, and byte value.

Breaking changes:

String types are now stored as separate types, meaning:

Unquoted null string are resolved as null value
Quoted "null" strings are resolved as a string "null"
Paths and keys are fully parsed, a quoted key needs to be quoted to be valid, eg:

"a.\"some quoted, key\"" is not the same as "a.some quoted, key" because commas are invalid inside an unquoted string.
"\"a.key.with.dots\"" will actually use the whole quoted string as a field key, while "a.key.with.dots" will be resolved as a path with 4 keys.

@Arkatufus looks like build server barfed on some new language features in your latest set of commits

@Aaronontheweb which C# version is our build server using? We should go to latest by default (now 7.3).

@Horusiath since we're building against the .NET Core SDK, I think you can just set the language setting in the .CSPROJ file.  Build server has 7.1 installed on it by default I think, but the CSPROJ settings should override.

@Arkatufus, these changes look fantastic and I appreciate the amount of time and trouble it take to implement them. Also really appreciate the amount of time and effort spent by @Horusiath and @rogeralsing reviewing the code in detail over the summer.
I'm going to merge this in now so we can start applying other changes (such as porting https://github.com/akkadotnet/akka.net/pull/3600 into this library) in separate PRs on top of this one, and I think we might be ready to do a new release of the library soon. Nice work.


serverPrefetch hooks in mixins not called during SSR

Version
3.0.4
Reproduction link
https://codesandbox.io/s/vue-ssr-bug-o1nbv?file=/src/index.js
Steps to reproduce
const MyComponent = defineComponent({
  name: "MyComponent",
  template: `<div>MyComponent</div>`,
  mixins: [
    {
      serverPrefetch() {
        console.log("mixin defined serverPrefetch call on", this.$options.name);
        return Promise.resolve();
      }
    }
  ]
});

The serverPrefetch hook mixed into MyComponent is not called during SSR.
What is expected?
When refreshing the SSR page, it is expected to see serverPrefetch hooks for both ComponentA (defined explicitly as a local option) and ComponentB (defined via a mixin) invoked by server renderer.
$ node index.js
serving on port 8080
locally defined serverPrefetch call on ComponentA
mixin defined serverPrefetch call on ComponentB

What is actually happening?
Only the locally defined hook for ComponentA is invoked:
$ node index.js
serving on port 8080
locally defined serverPrefetch call on ComponentA

I'm not very familiar with Vue. Sorry if this turns out to be an id10t error.

Took a deeper look in the source. render.ts doesn't really check if there is any serverPrefetch defined in mixins. Is this an intentional design? It seems to be supported in vue 2 though.

The logic for processing mixin serverPrefetch should be written here:
https://github.com/vuejs/vue-next/blob/8ac2241b22/packages/runtime-core/src/componentOptions.ts#L438

Hey @edison1105! Thanks for the timely reply. So is it confirmed to be a bug of Vue 3?
I am not sure if writing serverPrefech processing logic where you pointed is a good idea. To my limited knowledge of Vue:

servePrefetch is only related to SSR, namely the server-renderer package. Being a not standard lifecycle, it feels questionable to process servePrefetch in the runtime-core package.

applyOptions deals with post-created lifecycles only, all of which are essentially noops for SSR.

Please correct me. It's very likely that I misunderstood something here and there...

I'm think the best is to make it consistent with Vue 2.
https://github.com/vuejs/vue/blob/dev/src/core/util/options.js#L172

...make it consistent with Vue 2

Thank you for pointing the direction. I'll take a deeper look!

BTW, your code not handled globalMixins

No, it doesn't, and it doesn't handle mixins with a mixin either. By no means that was a proper fix. :joy:

@tabjy I think you can submit your PR if it is ready.

@edison1105 I don't know the workflow here. I was under the impression submitting it after someone from @vuejs confirms it to be a bug and assigns me to it, but you're right. I might as well submit it now. Worst case they can just close it if it's a wontfix.
Thank you!

@tabjy Thanks your PR, and sorry for being late.
The merge logic of the serverPrefect hook cannot be written in applyOptions, because applyOptions is controlled by __FEATURE_OPTIONS_API__, details can be found here feature-flags. I will take a closer look at this issue later.

After this https://github.com/vuejs/vue-next/pull/3070, I think it's ok to define merge logic in applyOptions


Inner product without vector rotation

I am wondering about how to compute the inner product of a plaintext vector and a ciphertext vector under CKKS scheme without using vector rotation. That is to say, I want to find out a way that computes the inner product slot-wise, and does not use galois keys in the computation. Is that possible to do that in SEAL?

Given a plaintext that encodes {a0, a1, a2, ...} and a ciphertext that encodes and encrypts {b0, b1, b2, ...}, you can compute a ciphertext that can be decrypted and decoded to {a0*b0, a1*b1, a2*b2, ...} without Galois keys. Is this what you want?

Thanks for your reply.
I think what I want is how to sum up {a0*b0, a1*b1, a2*b2, ...} without Galois key. Is that possible?

Not possible. You have to rotate the underlying vector, e.g., moving a1*b1 to slot 0. Rotation requires Galois keys.

Actually, if you only need inner product (and no more further computation) you should try the inner product trick (which I called for years). Ref you to the paper Secure pattern matching using somewhat homomorphic encryption


Refactor address encoding/decoding

closes #278
What started as a small pach, ended up being quite an important refactoring, with Moonbeam/river in mind (there's still the back-end to port). In any case, this is touching everything that is linked to an address. From the watch accounts, to the account displayed, the multisig creation/change

Wow thanks a lot for all these tests, certainly things I haven't tested myself in a while :)


Playing from audio_cache

I was wondering if there is any way to get the bot to play music from the cache without manually entering every single song? Like a shuffle play of everything in the cache?

When I write local playlists, this will be one of the special playlists, like the autoplaylist.

Thanks


deepcopy() looses precision

Expected behavior and actual behavior.
I would expect that a deepcopy of any geometry returns a geometry with the precision preserved, but this is not the case.
Steps to reproduce the problem.
from copy import deepcopy
from shapely import Point, set_precision, get_precision

p = set_precision(Point([0,0]), 0.1)
print(f"original precision: {get_precision(p)}")
print(f"precision after deepcopy: {get_precision(deepcopy(p))}")

Output
original precision: 0.1
precision after deepcopy: 0.0

I tried with LineString and Polygon and I get the same result.
I think it's discussed in this issue #1821
Operating system
Ubuntu 22.04
Shapely version and provenance
Python 3.10.12
shapely==2.0.4 installed from PyPI using pip

I think it's discussed in this issue #1821

It's indeed the same explanation: deepcopy essentially pickles/unpickles the object (if the object does not define __copy__ and __deepcopy__), and so what you see is a limitation of the way we pickle geometries.
I agree that you would expect a copy (and maybe also a pickle/unpickle) of a geometry would preserve the precision, but currently we don't do that. In theory we could get the precision from the geometry (get_precision), pickle that number together with the WKB representation, and then set the precision again when unpickling (set_precision). Although I am not entire sure the set_precision could not have other side effects that might change the geometry (which we also don't want in case of copy/pickling).


Incomprehensible description of round-number time boundaries

The documentation says:

InfluxDB uses preset round-number time boundaries for GROUP BY intervals that are independent of any time conditions in the WHERE clause. When it calculates the results, all returned data must occur within the query’s explicit time range but the GROUP BY intervals will be based on the preset time boundaries.

But why is there no description of how these boundaries are calculated?
For example: when grouping for 7 seconds from 10:04:00Z, I get intervals staring in:
10:03:59Z
10:04:06Z
10:04:13Z
and so on

By grouping for 9 seconds:
10:03:54Z
10:04:03Z
10:04:12Z
and so on

There is an idea that there is some kind of starting point in time and groupping is by intervals relative to it, but what value does this point have?
Relevant URLs
https://docs.influxdata.com/influxdb/v1.8/query_language/explore-data/#unexpected-timestamps-and-values-in-query-results
And Submit docs issue on 1.8 docs page redirects to docs-v2. Is this the expected behavior?

Experimentally, it was found that this point is 1970-01-01T00:00:00Z (timestamp 0). It would be helpful to add this to the documentation.


GPII-1280: Initial implementation of user management...

See GPII-1280 for details.

Test failure on "forgot" tests as follows:
15:44:52.937:  Sending a POST request to: http://localhost:8779/api/user/reset/efb147e1cdd00b3f95e209ab62578042 on port 8779
15:44:52.985:  DataSource Issuing HTTP request with options {
"port": "8765",
"method": "GET",
"headers": {
},
"protocol": "http:",
"auth": null,
"host": "localhost:8765",
"hostname": "localhost",
"path": "/users/_design/lookup/_view/byResetCode?key=%22efb147e1cdd00b3f95e209ab62578042%22",
"url": "http://localhost:8765/users/_design/lookup/_view/byResetCode?key=\"%code\"",
"termMap": {
    "code": "%code"
},
"directModel": {
    "code": "efb147e1cdd00b3f95e209ab62578042"
},
"operation": "get",
"reverse": false,
"writeMethod": "PUT"

}
15:44:53.041:  Sending a POST request to: http://localhost:8779/api/user/login on port 8779
15:44:53.086:  DataSource Issuing HTTP request with options {
"port": "8765",
"method": "GET",
"headers": {
},
"protocol": "http:",
"auth": null,
"host": "localhost:8765",
"hostname": "localhost",
"path": "/users/_design/lookup/_view/byUsernameOrEmail?key=%22existing%22",
"url": "http://localhost:8765/users/_design/lookup/_view/byUsernameOrEmail?key=\"%username\"",
"termMap": {
    "username": "%username"
},
"directModel": {
    "username": "existing",
    "password": "Password1"
},
"operation": "get",
"reverse": false,
"writeMethod": "PUT"

}
express deprecated res.send(status): Use res.sendStatus(status) instead node_modules\gpii-json-schema\node_modules\gpii-express\src\js\handler.js:77:38
15:44:53.135:  FATAL ERROR: Uncaught exception: Unexpected token O
SyntaxError: Unexpected token O
at Object.parse (native)
at gpii.express.user.api.reset.test.caseHolder.verifyResponse (E:\source\gits\gpii-express-user\tests\js\server\forgot-tests.js:162:48)
at togo (E:\source\gits\gpii-express-user\node_modules\infusion\tests\test-core\utils\js\IoCTestUtils.js:248:33)
at wrapped (E:\source\gits\gpii-express-user\node_modules\infusion\tests\test-core\utils\js\IoCTestUtils.js:323:26)
at that.fire (E:\source\gits\gpii-express-user\node_modules\infusion\src\framework\core\js\Fluid.js:1399:40)
at IncomingMessage. (E:\source\gits\gpii-express-user\node_modules\kettle\lib\test\KettleTestUtils.http.js:132:13)
at emitNone (events.js:72:20)
at IncomingMessage.emit (events.js:166:7)
at endReadableNT (_stream_readable.js:903:12)
at doNTCallback2 (node.js:439:9)
at process._tickCallback (node.js:353:17)
15:44:53.139:  Current activity:
15:44:53.140:  jq: FAIL: Test name "Testing resetting a user's password, end-to-end..." - Message: Unexpected failure in test case (see following log for more d
etails): Unexpected token O
15:44:53.141:  jq: Source:     at kettle.test.handleUncaughtException (E:\source\gits\gpii-express-user\node_modules\kettle\lib\test\KettleTestUtils.js:31:15)
at Object.that.fire (E:\source\gits\gpii-express-user\node_modules\infusion\src\framework\core\js\Fluid.js:1399:40)
at process.onUncaughtException (E:\source\gits\gpii-express-user\node_modules\infusion\src\module\fluid.js:121:35)
at emitOne (events.js:82:20)
at process.emit (events.js:169:7)
at process._fatalException (node.js:221:26)
Also 1 minor linting error

This was another variation on the problems with updating the sendResponse method in gpii.express.handler.  Specifically it prevented /hbs from delivering template content, which killed the client-side components.  Turns out I had fixed only four of the five packages that depend on gpii-express, and not gpii-pouchdb.  I have fixed that and am testing now.

That was it, my Windows build works again.  You'll have to pull the latest changes, and you may need to run npm cache clear, as the name of the package changed from gpii-pouch to the correct gpii-pouchdb.

These tests seem to run better than before, but I notice that they now have the behaviour of repeatedly creating and destroying a top-level electron window on the desktop. This is survivable but would be highly desirable to avoid. I do get two tests failures on the run though, here is the trail of the transcript:
14:32:54.795:  jq: FAIL: Test name "Create and verify a new user from end to end..." - Message: A login success message should now be displayed... - at sequence
position 18 of 23
14:32:54.798:  jq: Source:     at pok (E:\source\gits\gpii-express-user\node_modules\infusion\tests\test-core\jqUnit\js\jqUnit.js:110:15)
at jsUnitCompat.assertTrue (E:\source\gits\gpii-express-user\node_modules\infusion\tests\test-core\jqUnit\js\jqUnit.js:143:13)
at togo (E:\source\gits\gpii-express-user\node_modules\infusion\tests\test-core\utils\js\IoCTestUtils.js:248:33)
at wrapped (E:\source\gits\gpii-express-user\node_modules\infusion\tests\test-core\utils\js\IoCTestUtils.js:323:26)
at Object.that.fire (E:\source\gits\gpii-express-user\node_modules\infusion\src\framework\core\js\Fluid.js:1399:40)
at Nightmare. (E:\source\gits\gpii-express-user\node_modules\gpii-test-browser\src\js\nightmare.js:123:36)
at Nightmare.done (E:\source\gits\gpii-express-user\node_modules\gpii-test-browser\node_modules\nightmare\lib\nightmare.js:225:15)
at Nightmare.next (E:\source\gits\gpii-express-user\node_modules\gpii-test-browser\node_modules\nightmare\lib\nightmare.js:203:35)
at EventEmitter. (E:\source\gits\gpii-express-user\node_modules\gpii-test-browser\node_modules\nightmare\lib\nightmare.js:213:12)
at EventEmitter.g (events.js:260:16)
at emitNone (events.js:67:13)
at EventEmitter.emit (events.js:166:7)
at ChildProcess. (E:\source\gits\gpii-express-user\node_modules\gpii-test-browser\node_modules\nightmare\lib\ipc.js:28:10)
at emitTwo (events.js:87:13)
at ChildProcess.emit (events.js:172:7)
at handleMessage (internal/child_process.js:686:10)
at Pipe.channel.onread (internal/child_process.js:440:11)
14:32:54.813:  Express stopped...
14:32:54.820:  Stopped mail server...
14:32:54.839:  jq: Test concluded - Test name "Create and verify a new user from end to end...": 1/2 passed - FAIL
14:32:54.848:  Deleted existing data from database 'users'...
14:32:54.851:  jq: ***************
14:32:54.854:  jq: All tests concluded: 103/105 total passed in 122324ms - FAIL
14:32:54.856:  jq: ***************

I will look at the tests.  The creation of a "top level" Electron instance is a byproduct of using Nightmare, which previously was not obvious as we were using the defaults and hiding everything.  I'm not sure we have any control over that short of writing our own alternative to Nightmare, but I will look through their docs to confirm.

Nightmare does not have any options that can be used to control the behavior of launching electron once for every browser instance.  Their own tests run with the same tell-tale twitch that demonstrates that electron is being launched and torn down for each run.

On the other hand, I can avoid using the browser test environment for tests that don't actually require a browser.  That should reduce the twitching blackness that was part of the 78 "server" runs.

The intermittent failures were the result of the tests running a few milliseconds before the page completed its initial render.  For now, adding a browser wait after the initial page load avoids the problems.  A better long-term fix is to get GPII-1574 working and wait until the client-side component finishes rendering before continuing the tests.


Bugfix incorrect coverage values in the compare test coverage workflow

A duplicate PR to fork to QA coverage.

coverage: 65.609% (+55.9%) from 9.688% when pulling 962d9f41894490cff77d1f2cfb150171739deb83 on bugfix-incorrect-coverage-values-in-the-compare-test-coverage-workflow into 6e45c806a54869944550a6be8b102a1a751408a3 on development.


Fix Travis

Travis failed on node 0.8 and below because the associated npm versions are too old to understand caret ranges.

Thanks!


Add minimum score criteria for AI search results

A filtering mechanism based on minimum score criteria for documents. By setting a minimum value for both search_score and reranker_score. This aims to improve the relevance of documents sent to the AI, that only the most relevant information is sent for further processing.
Suggested change: https://github.com/Azure-Samples/azure-search-openai-demo/pull/1417
This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [x] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Any log messages given by the failure

Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

azd version?

run azd version and copy paste here.

Versions

Mention any other details that might be useful

Thanks! We'll be in touch soon.

Thanks for the PR! We can close this now since you implemented it. :)


Body HTML is rendered in live preview but not in MAIL itself

This is a small bug where the text actually sent to the MAIL Body is not the HTML but rather the text itself, so all we need to do is instead of sending the direct text from the textbox we need to parse the markdown and send the HTML to the body, this can be achieved via body = markdown.markdown(body)

Hey I'm new to open source. I'd like to take this issue!

Hey @charmainessseah Sure I am assigning this to you, please feel free to ask any doubts if you have any.


Non-HoloLens platforms should implement a rotation gesture

On HoloLens, GE has a "tilt" button. When GE is not running on a HoloLens, the "tilt" button should be removed and a "well-thought-out" rotate gesture should be plumbed through the input manager.

#102


Retire product devfile registry

Which area this feature is related to?
/area registry
Which functionality do you think we should add?
Retire the devfile product registry https://devfile-registry.redhat.com/ .
Why is this needed? Is your feature request related to a problem?
To reduce the long term maintenance.
Detailed description:
Describe the solution you'd like
Things to cover:

[ ] Communicate with the JBoss team to notify. They can reach out to the Dev Spaces team that is currently planning on keeping their list of supported devfile configured via ConfigMap.
[ ] Take down the product registry
[ ] Take down the product registry viewer
[ ] Archive the product registry repo
[ ] Offboading the product registry from App-SRE

Describe alternatives you've considered
Additional context

/lifecycle frozen


add websocket handshake_auth.go

add a handshake-plugin of  websocket  to auth by URL.Query info
Usage:
@see func TestHandshakeWebsocketAuth

Good job, I think it is basically ok, but you need to add some comments

maybe you can set your github email for github push account.

maybe you can set your github email for github push account.

thx for suggest

@deepziyu Are you ready to merge?

@deepziyu Are you ready to merge?

it's ok


Building on WSL fails because of PATH

PATH in WSL is a concatenation of Linux' PATH with Windows' PATH. Example:
/home/felipecrs/.local/bin:/home/felipecrs/bin:/home/felipecrs/go/bin:/home/felipecrs/.deno/bin:/home/felipecrs/.volta/bin:/home/linuxbrew/.linuxbrew/bin:/home/linuxbrew/.linuxbrew/sbin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/wsl/lib:/mnt/c/Program Files/Volta/:/mnt/c/Program Files/Eclipse Adoptium/jre-<IP_ADDRESS>-hotspot/bin:/mnt/c/Program Files/OpenSSH/:/mnt/c/Windows/system32:/mnt/c/Windows:/mnt/c/Windows/System32/Wbem:/mnt/c/Windows/System32/WindowsPowerShell/v1.0/:/mnt/c/Windows/System32/OpenSSH/:/mnt/c/Program Files (x86)/NVIDIA Corporation/PhysX/Common:/mnt/c/Windows/system32/config/systemprofile/AppData/Local/Microsoft/WindowsApps:/mnt/c/Program Files/dotnet/:/mnt/c/WINDOWS/system32:/mnt/c/WINDOWS:/mnt/c/WINDOWS/System32/Wbem:/mnt/c/WINDOWS/System32/WindowsPowerShell/v1.0/:/mnt/c/WINDOWS/System32/OpenSSH/:/mnt/c/Program Files (x86)/Windows Kits/10/Windows Performance Toolkit/:/mnt/c/Program Files/WireGuard/:/mnt/c/Program Files/NVIDIA Corporation/NVIDIA App/NvDLISR:/mnt/c/Program Files/gsudo/Current:/mnt/c/Program Files/Git/cmd:/mnt/c/Program Files/Go/bin:/mnt/c/Program Files/PuTTY/:/mnt/c/Program Files/GitHub CLI/:/mnt/c/Users/felip/AppData/Local/Programs/Python/Python312/Scripts/:/mnt/c/Users/felip/AppData/Local/Programs/Python/Python312/:/mnt/c/Users/felip/AppData/Local/Programs/Python/Launcher/:/mnt/c/Users/felip/.cargo/bin:/mnt/c/Users/felip/AppData/Local/Volta/bin:/mnt/c/Users/felip/AppData/Local/Microsoft/WindowsApps:/mnt/c/Users/felip/AppData/Local/Programs/oh-my-posh/bin:/mnt/c/Users/felip/AppData/Local/Microsoft/WinGet/Links:/mnt/c/Users/felip/AppData/Local/Programs/Microsoft VS Code/bin:/mnt/c/Users/felip/AppData/Local/Microsoft/WindowsApps:/mnt/c/Users/felip/AppData/Local/Programs/Komac/bin:/mnt/c/Mtl-Multisync/Rewriters/_msrgallwinner.zip/:/mnt/c/Users/felip/AppData/Local/Microsoft/WinGet/Packages/PolarGoose.BluetoothDevicePairing_Microsoft.Winget.Source_8wekyb3d8bbwe/:/mnt/c/Users/felip/AppData/Local/Microsoft/WinGet/Packages/Google.PlatformTools_Microsoft.Winget.Source_8wekyb3d8bbwe/platform-tools:/mnt/c/Program Files/Multipass/bin:/mnt/c/Users/felip/go/bin:/mnt/c/Program Files (x86)/Nmap

And make fails with:
Your PATH contains spaces, TABs, and/or newline (\n) characters.
This doesn't work. Fix you PATH.

I wonder if this requirement can be alleviated.
The workaround is to add:
[interop]
appendWindowsPath = false

To /etc/wsl.conf.

do not build in wsl.
https://github.com/themactep/thingino-firmware/wiki/Development#containers

the space in the path issue is with the buildroot system itself, we added a check in the top level Makefile to prevent people from running into errors during the build... do not build in WSL =D
If you're on windows you could try the docker container that @themactep linked above... ymmv, i dont use windows lol

Well, the workaround I mentioned worked just fine. I was able to build the firmware multiple times on WSL.
But I'll check this container out.
And if it's a limitation of buildroot, then there's nothing we can do indeed. At least the workaround is now documented.
Thank you!

we use a patched buildroot so if you figure out a fix we can add it to our buildroot repo.


Web component generator

Custom elements / web components will integrate nicely in fyord. If you need a component that can work outside of a fyord app, or anywhere for that matter, we should push CEs/WCs as a solution.

Custom element generator added on 6/18/21.
Web component should be basically the same, just with a shadow dom.


Remove Eigen::PartialPivLU and replace it with Crout LU decomposition

Remove Eigen::PartialPivLU and replace it with Crout LU decomposition
closes #943

Some very minor comments otherwise look good to me!
One question for the performance aspect though - have we checked this via neuron paper models (channel-benchmark and olfactory-bulb model) and see if the execution time of respective MOD files block (the ones with sparse/derivimplicit solver) is comparable to old implementation?

In terms of performance, I have just added timers in the unit test (measuring the time of eigen solvers and crout ones). These are the results I just got:
eigen_timing [ms] : 20.3689
crout_timing [ms] : 18.3714

Keep in-mid that crout includes the transposeInPlace from eigen.
Therefore, performance-wise I am expecting same or even better results.
(I will push later my changes)

I run the CoreNEURON performance metrics CI and it seems like the time got reduced since the last run slightly but last CPU runtimes are a bit unstable. You can see the output here https://bbpgitlab.epfl.ch/hpc/cellular/coreneuron-perf-tests/-/jobs/391196. It run with commit https://github.com/BlueBrain/nmodl/pull/964/commits/3a2c7c27666a185f57c701f49a6c3c655b7cb28e. Maybe we should rerun it with the latest changes before merging and see whether the runtime is closer to the previous average CPU runtimes?

PYTHONPATH=/home/vsts/work/1/s/nrn/build/lib::/home/vsts/work/1/s/nrn/build/lib/python MODLUNIT=/home/vsts/work/1/s/nrn/build/share/mod2c/nrnunits.lib /home/vsts/work/1/s/nrn/build/bin/nmodl x86_64/corenrn/mod2c/hh.mod -o x86_64/corenrn/mod2c/ host --c passes --inline sympy --analytic
Segmentation fault (core dumped)
make[3]: *** [/home/vsts/work/1/s/nrn/build/share/coreneuron/nrnivmodl_core_makefile:253: x86_64/corenrn/mod2c/halfgap.cpp] Error 139
make[3]: *** Waiting for unfinished jobs....

Is something worth looking for segfault?

@pramodk shall we merge it?
I have added the error checking.
All the tests are passing, see as well: https://github.com/BlueBrain/CoreNeuron/pull/871


Have obstacle store obstacle type and render correct obstacle

The JSON currently has obstacle types, but the renderer only shows trees. Add variable for obstacle type and link it to the renderer.

Don't remember precisely, I noted in the discord and the merge request, this collection of features (including other closed issues in this batch) took 6 hours, so something like 4ish on this one? Whatever makes that math check out


Add icon button

This new button also includes a suite of visual tests within a new test project, containing basic infrastructure for visual widget testing.
The project has not been properly packaged in a package named kivydesigner, with visual widgets stored in a uix subpackage similar to the kivy project. Widgets are automatically registered with the kvlang builder during the toplevel package initialization.

Closes #5.
Found a minor bug we can fix later reported in #11. The current test framework is clunky and could use some improvements down the line. Documented ideas in #10.


lets combine ReplicaSet and ReplicationControllers in the model into a model.replicas and then view those in the Replicas UI?

@jstrachan think this is all set now?

yes thanks!

I haven't looked at what it looks like (sure it's awesome though!) but just wanted to check you've handled the new label selector format (in, not in, etc) in the UI somehow?

@jimmidyson we don't have any nice UI stuff for the new RS selection extensions am afraid; it just uses the usual matchesLabels stuff

Don't be afraid! Was just mentioning it - sure it will be there soon enough :-b


BUG- timeout and simultanous notify when async_mode default value

Description
Notify are being shown simultaneously even if time passes between two 'notify' in the code.
Functions that work with async_mode="threading" are in timeout with async_mode default. The page is not actualized.
How to reproduce
from taipy.gui import Gui, notify

import time

sleep_value = 1

md = """
<|{sleep_value}|number|>

<|Wait|button|on_action=wait|>
"""

def wait(state):
    notify(state,'i', 'First')
    time.sleep(state.sleep_value)
    notify(state,'i', 'Last')

Gui(md).run()

Expected behavior
Notifications should happen in real-time, corresponding to the time they are sent in the code.
Functions that work with async_mode="threading" should also work with the default value of async_mode.

similar to #458

Can you try :

Not specify async_mode (=> gevent)
add this at the beginning of your main script

from gevent import monkey
    monkey.patch_all()


Improve upgrading docs

Here are some small changes to the upgrading documentation that I found when doing following it myself. I took the liberty to do some small and simple improvements (like add the set-image example for kube-proxy).
I tried to split the logical changes in different commits and explain on each commit message, but if something is not clear please don't hesitate to ask.
Thanks a lot!
Rodrigo

could you please squash the commits, please ?

@rmenn sure, like this? If not, feel free to merge with the squash option in github and edit, if that is easier. Hopefully this is fine, though :)

@andrewrynhard @bradbeam fixed now, thanks! :-D

/assign andrewrynhard

@rmenn @andrewrynhard I think the GH approve status is not used by tide. I think you need to do /lgtm and /approve commands for tide to merge this (I used that on kubernetes org, I guess is the same :))

/approve

Hmm. Seems to think I’m not an owner.

/lgtm

/lgtm

/approve

/assign @rphillips

Gonna give this another go hoping that the move to kubernetes-sigs fixed any issues.
/approve

/lgtm
/approve

Thanks for all the attempts to merge this! :-D


Feature/acompanhar pedido por data

Track orders as in PR #2 , but establishing a date parameter

:+1:


opted-in-at-round: null in ApplicationLocalState of opted-in account

This might be an issue or not, or might be an issue else where.
Printing the ApplicationLocalState of account 6IMMVVL2ZRXK53KIKA3QNNMC6JGRUR4FXDGHK26UA4IF3C3S4FQOI32WCY on testnet, we get:
{id: 32969536, schema: Instance of 'ApplicationStateSchema',
closed-out-at-round: null, deleted: null, key-value: [],
opted-in-at-round: null}

Why is the "opted-in-at-round" null? The account is in opted-in, else we would not even have that ApplicationLocalState.

Both Algod and Indexer have an endpoint to get the account information from a given address, however the Algod response does not contain all ApplicationLocalState related fields. I think the best bet would always be to check the transaction reference pages:

Algod: https://developer.algorand.org/docs/rest-apis/algod/v2/#applicationlocalstate
Indexer: https://developer.algorand.org/docs/rest-apis/indexer/#applicationlocalstate


Use version range for logging components

This commit shifts to the use of version ranges for SLF4J and logback.
SLF4J is capped at 1.7.9999 to avoid picking up 1.8.0-betaX releases
which will not work with released versions of Logback before 1.3.x.
The minimum versions of Logback is 1.2.11 which requires a minumum
version of SLF4J of 1.7.32.
While developing this update, it was observed that the SLF4J version
must "align" with the Logback version for Logback to be properly
initialized.  With this observation, tests for ConsoleAppenderCapture
are changed to terminate with a more informative assertion to avoid
an obscure test failure.
The configuration for the enforcer plugin is lifted out of an
execution configuration to permit its use as a top-level task.

This PR begins the cascade.

Version spec changed


Why no support for Kodi 18.7?

Hey,
I'm on the newest version of Raspbian 10 buster but unfortunately Kodi 19 is still not released for this Raspbian version.
Previously I used this add-on without problems with 18.7 but unfortunately that support was dropped.
Is it possible to make this add-on backwards compatible with 18.7?
Thanks!

I agree that this message isn't true. But it's a simple sentence to explain to users that they might have problems with Kodi 18.


String array not removing strings that are deleted from the top of the list

Hi. If I use a quick field for an array of strings, the automatic form fields allow adding and deleting of strings for the field. If a string is deleted from the top of the list, it reappears in the list again as a blank string, so it appears that it cannot be removed. Is this a bug?
See quick sample video
https://youtu.be/_8VaH_ukupE

having the same issue, any plans on the fix?


Make Localstack services optional.

Fixes #6428

Thanks for your contribution, @maciejwalkowiak ! I've applied the suggestions.

Thanks @eddumelendez!


Text Size can't be changed

Please add a method to change text size of hidden text. Thanks.

Hey @ErfanThinker I fixed this bug, check and close this issue please.


pipenv lock fails when Pipfile has several sources from v2022.3.23

Issue description
When Pipfile has multiple sources e.g. public and private pypi servers, and the public (default) one is not declared first, pipenv lock fails.
With pipenv v2022.1.8 it worked fine, but with v2022.3.23 or newer it shows an error.
If this change is intentional, it's kind of breaking backward compatibility, so I think it needs to be written in the release note or the documentation.
Expected result
pipenv lock succeeds.
Actual result
No matching distribution found for requests will be shown.
Locking [dev-packages] dependencies...
Locking [packages] dependencies...
Building requirements...
Resolving dependencies...
✘ Locking Failed!

CRITICAL:pipenv.patched.notpip._internal.resolution.resolvelib.factory:Could not find a version that satisfies the requirement requests (from versions: none)
[ResolutionFailure]:   File "/usr/local/lib/python3.8/site-packages/pipenv/resolver.py", line 743, in _main
[ResolutionFailure]:       resolve_packages(pre, clear, verbose, system, write, requirements_dir, packages, dev)
[ResolutionFailure]:   File "/usr/local/lib/python3.8/site-packages/pipenv/resolver.py", line 704, in resolve_packages
[ResolutionFailure]:       results, resolver = resolve(
[ResolutionFailure]:   File "/usr/local/lib/python3.8/site-packages/pipenv/resolver.py", line 685, in resolve
[ResolutionFailure]:       return resolve_deps(
[ResolutionFailure]:   File "/usr/local/lib/python3.8/site-packages/pipenv/utils.py", line 1398, in resolve_deps
[ResolutionFailure]:       results, hashes, markers_lookup, resolver, skipped = actually_resolve_deps(
[ResolutionFailure]:   File "/usr/local/lib/python3.8/site-packages/pipenv/utils.py", line 1127, in actually_resolve_deps
[ResolutionFailure]:       resolver.resolve()
[ResolutionFailure]:   File "/usr/local/lib/python3.8/site-packages/pipenv/utils.py", line 905, in resolve
[ResolutionFailure]:       raise ResolutionFailure(message=str(e))
[pipenv.exceptions.ResolutionFailure]: Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies.
  You can use $ pipenv install --skip-lock to bypass this mechanism, then run $ pipenv graph to inspect the situation.
  Hint: try $ pipenv lock --pre if it is a pre-release dependency.
ERROR: No matching distribution found for requests

Steps to replicate
Here's Pipfile.
[[source]]
name = "private"
url = "URL"
verify_ssl = true

[[source]]
name = "pypi"
url = "https://pypi.org/simple"
verify_ssl = true

[packages]
requests = "*"  # I use requests as an example, but any package will be OK.
mypackage = {version = "*", index = "private"}

Run pipenv lock.
$ pip3 install pipenv==2022.3.28
$ pipenv lock

$ pipenv --support
Pipenv version: '2022.3.28'
Pipenv location: '/usr/local/lib/python3.8/site-packages/pipenv'
Python location: '/usr/local/bin/python'
Python installations found:

3.9.2: /usr/bin/python3.9
3.9.2: /usr/bin/python3
3.8.12: /usr/local/bin/python
3.8.12: /usr/local/bin/python3
3.8.12: /usr/local/bin/python3.8

PEP 508 Information:
{'implementation_name': 'cpython',
 'implementation_version': '3.8.12',
 'os_name': 'posix',
 'platform_machine': 'x86_64',
 'platform_python_implementation': 'CPython',
 'platform_release': '5.10.104-linuxkit',
 'platform_system': 'Linux',
 'platform_version': '#1 SMP Wed Mar 9 19:05:23 UTC 2022',
 'python_full_version': '3.8.12',
 'python_version': '3.8',
 'sys_platform': 'linux'}

System environment variables:

HOSTNAME
PYTHON_VERSION
PWD
PYTHON_SETUPTOOLS_VERSION
JFROG_USER
HOME
LANG
GPG_KEY
TERM
SHLVL
PYTHON_PIP_VERSION
PYTHON_GET_PIP_SHA256
PYTHON_GET_PIP_URL
PATH
JFROG_TOKEN
_
PIP_SHIMS_BASE_MODULE
PIP_DISABLE_PIP_VERSION_CHECK
PYTHONDONTWRITEBYTECODE
PIP_PYTHON_PATH
PYTHONFINDER_IGNORE_UNSUPPORTED

Pipenv–specific environment variables:
Debug–specific environment variables:

PATH: /usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
LANG: C.UTF-8
PWD: /root/pipenv-test

Contents of Pipfile ('/root/pipenv-test/Pipfile'):
[[source]]
url =<EMAIL_ADDRESS>verify_ssl = true
name = "local"

[[source]]
name = "pypi"
url = "https://pypi.org/simple"
verify_ssl = true

[packages]
requests = "*"
authority-sdk-python = {version = "*", index = "local"}
#requests = {version = "*", index = "pypi"}

@ysk24ok  I started working on documentation improvements related to this, but basically the 2022.3.x releases of pipenv changed to treat indexes strictly to prevent package confusion attacks.   The first index in the Pipfile is considered the default index for the project and technically while this fact did not change, how we uses the indexes to search and resolve has become more strict so no package will ever search more than one index to be resolved.   Please see this PR for more details and feel free to recommend additional improvements to the docs or feature flags that would be helpful:  https://github.com/pypa/pipenv/pull/5029

Thank you for the info, and your hard work! You're already working on doc improvements, so it should be OK.
Let me close this issue.


Create File System Catalog Store Implementation

Create a FS based catalog store implementation, similar to the Artifact Store one.

Closed in #478


feat: support optionalChaining & nullishCoalscingOperator

WHAT

Support optionalChaining & nullishCoalscingOperator

WHY

Try to resolve this error

SyntaxError: This experimental syntax requires enabling the parser plugin: 'optionalChaining' (10:46)
    at Object.raise (/Users/huynhducdung/.config/yarn/global/node_modules/js2flowchart/dist/js2flowchart.js:1:210466)

HOW

Add to AST Parser

'optionalChaining',
'nullishCoalescingOperator'

Screenshots (if appropriate):

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] Linter
[x] Tests
[ ] Review comments
[ ] Security

Hi, @Bogdan-Lyashenko Thank you for your awesome work. Could you take a look at my pull request?


Move hyphen to end of allowed characters regex for ~user and project slugs

Closes #4295. This disallows characters like / and ? from being used in slugs, which fubars URLs.

Gonna need a test or four for this. Ideally the tests would be on a separate commit, pushed first so we can see Travis fail.

Similar to testing the error message, but asserting a different response?
    def test_error_message_for_invalid_team_name(self):
        self.make_participant('alice', claimed_time='now'<EMAIL_ADDRESS>last_paypal_result='')
        data = dict(self.valid_data)
        data['name'] = '~Invalid:Name;'
        r = self.post_new(data, expected=400)
        assert self.db.one("SELECT COUNT(*) FROM teams") == 0
        assert "Sorry, your team name is invalid." in r.body

E.g.,
    def test_invalid_team_name(self):
        self.make_participant('alice', claimed_time='now'<EMAIL_ADDRESS>last_paypal_result='')
        data = dict(self.valid_data)
        data['name'] = 'invalid?name/goes\here?'
        r = self.post_new(data, expected=400)
        assert self.db.one("SELECT COUNT(*) FROM teams") == 0
        assert "Sorry, your team name is invalid." in r.body

I know this tests for the output...

Temporarily reverted ee11dfc in dff5b4b. Added a test. It should fail.

Success?

I moved the hyphen in the ~username regex as well, but from what I can tell it was already working correctly.

Looks good to me.

I moved the hyphen in the ~username regex as well, but from what I can tell it was already working correctly.

Turns out it is a set and not a regex. 🐻

I should read more closely.


Add formal proofs of bytecode optimisations.

There are some patterns in EVM bytecode that can optimised gas-wise.
Some examples are listed in this MSc Thesis.
With our API we can formally prove that these optimisations are correct:

they generate the same final state (upto the value of gas and PC)
they consume strictly less gas.

Note that we can prove them given an arbitrary initial state (of course satisfying some constraints wrt stack size, gas etc).

I think an interesting question here is how many examples we want to put in this repository.  Every example extends the time it takes to verify the codebase and, hence, how long a merge request takes to complete.  Potentially, we might want to consider a secondary repository which includes a more extensive list of examples?  Or maybe not.

yeah, I think it is good to have examples. It helps to showcase what we can do with the semantics.


Redundant Pattern Detector: headtail patterns

Non-redundant headtail patterns are incorrectly recognized as redundant in the case when a more specific tail pattern breaks the subsumption. As an example, the following program incorrectly raises a redundant pattern exception...
load system io.
load system math.

function lhs_exp
  with [] do
    1
  with [ value | [] ] do
    value
  with [ value | tail ] do
    math@pow( lhs_exp tail, value)
end

let x = [2,3,4].
io@println( lhs_exp x ).

... as shown here ...
error: CSC493/programs/x.ast: 14: Redundant Pattern Detected
    Function: lhs_exp from file CSC493/programs/x.ast
    Pattern: [value|[]] on line 7
    will consume all matches for
    Pattern: [value|tail] on line 9

after code renovation of unify head-tail is no longer supported by redundancy checking (#266)


SDHC reading never starts (SDCard.vhd)

On SDHC cards, the SD Card controller (SDCard.vhd) stalls in line 455:
https://github.com/xesscorp/VHDL_Lib/blob/master/SDCard.vhd#L455
What seems to happen is: SDHC cards seem to take longer to be ready for reading, so they seem not to only send one NO_TOKEN_C, but many. But as far as I got it (sorry if I am wrong, I am a beginner): Don't we need to continue sending something like 0xFF to be able to do some kind of "active waiting" (otherwise SPI won't send anything back)?
If yes, is there any easy way to do so without redoing the whole state machine? Something like replacing the "null;" command by something like this:
txCmd_v := x"FFFFFFFFFFFF";
bitCnt_v := 8; -- only send one byte, not the whole txCmd_v, as we only want to "poll"
getCmdResponse_v := true;
rtnState_v := RD_BLK; -- return when done sending the dummy command
state_v  := START_TX

The goal would be to keep the SDHC card "actively engaged", so that we finally are able to receive a START_TOKEN_C.
What I am referring to, when writing "actively engaged" or "active waiting" is also what is written here:
http://electronics.stackexchange.com/questions/13112/sd-card-read-write-problems-in-spi-mode

In SPI, you have to send data to be able to read from the client. Remember that the master always drives the clock line. The dummy data I send when reading SD cards is 0xFF, too.

In the meantime, I found this VHDL SD card controller that is capable of handling SDHC as well as SD:
https://github.com/ibm2030/SimpleSDHC


start using https with hdl.handle.net

Does this include updating the metadata (dc.identifier.uri); if yes, will that work with our OAI-PMH consumers that require identifiers? Or is an update in refbox sufficient?


Correct dtype casting

What does this PR do?
This PR fixes a small "pre-bug" where in some very niche cases model buffers are saved in int, uint or bool. Therefore sometimes there is no need to cast their dtype to the desired dtype and we want to keep them in their native dtype.
I don't know if this is relevant but I ran tests/test_big_modeling.py slow tests to make sure this does not break anything on a multi-GPU setup (2x Tesla T4 16GB)
cc @sgugger @muellerzr

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Update Copyright Year Dynamically in Footer

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Hey @anuragverma108, the current footer in index.html contains a hardcoded copyright year. To ensure that the copyright year is always up-to-date, it would be beneficial to update it dynamically. This can be achieved by implementing a mechanism that automatically updates the year to the current year. Please assign the GSSOC label and I would like to work on it. Thank you!!
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Work on it!!


Unblock connection to SharePoint 2013

Transformation On Prem flag added
Before creating a pull request, make sure that you have read the contribution file located at
https://github.com/pnp/powerShell/blob/dev/CONTRIBUTING.md
Type

[X] Bug Fix
[ ] New Feature
[ ] Sample

Related Issues?
Fixes #4609
What is in this Pull Request ?
Flag to bypass client id check on transformation on-premises.
Tested with SP2013

Not sure why this is failing here, but fine on my local machine. I've only changed one line lol. Am i missing something?

@gautamdsheth - this is most odd. Still fails.

@gautamdsheth - I'm stuck here, is there a dependency I am missing in GitHub, seems like it cannot build due to a missing Graph dependency. The only change I have made to this PR is one line, Boolean check which doesn't change any Graph dependencies. All local builds work.

@pkbullock - yeah, must be something weird with the GH action. Tested it locally, builds fine, merged it. Thank you !

Awesome, thank you @gautamdsheth


[Doc] Need a sample for local claim and remote claim mapping

Type: Improvement
Priority: High
Severity: Minor
Release: wso2is-5.4.0-update1
Need a sample for local claim and remote claim mapping under "Claim configuration level parameters". The description too lengthy and difficult to understand.
claimMappings.localClaim.claimUri
claimMappings.remoteClaim.claimUri
https://docs.wso2.com/display/IS540/Using+the+Service+Provider+API

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.


issue in CMap and CHash

CMap use thes CHash::MurmurHash3 algorithm
	int32_t CMap::hash(const K& key)
	{
		return CHash::MurmurHash3((uint8_t*)(&key), sizeof(key), 0xDEADBEEF) % hash_size;
	}

	const char* cc="may";
	std::cout<<CHash::MurmurHash3((uint8_t *)&cc, sizeof("may"), 1)<<std::endl;

	char *c1=SG_MALLOC(char, strlen("may")+1);
	strcpy(c1, "may");
	std::cout<<CHash::MurmurHash3((uint8_t *)&c1, sizeof(c1), 1)<<std::endl;

	char *c2=SG_MALLOC(char, strlen("may")+1);
	strcpy(c2, "may");
	std::cout<<CHash::MurmurHash3((uint8_t *)&c2, sizeof(c2), 1)<<std::endl;

However, the hash function may be wrong. (I guess the algorithm uses some information from the memory address)
The three outputs are different.
What is worse, the outputs are different every time I run the program.

@lisitsyn
@iglesias

However, the MD5 algorithm works fine
	unsigned char buff[17];
	const char* cc="may";

	CHash::MD5((unsigned char *)cc, strlen(cc), buff);
	buff[16]='\0';
	std::cout<<"["<<buff<<"]"<<std::endl;

	char *c1=SG_MALLOC(char, strlen("may")+1);
	strcpy(c1, "may");

	CHash::MD5((unsigned char *)c1, strlen("may"), buff);
	buff[16]='\0';
	std::cout<<"["<<buff<<"]"<<std::endl;

	char *c2=SG_MALLOC(char, strlen("may")+1);
	strcpy(c2, "may");

	CHash::MD5((unsigned char *)c2, strlen("may"), buff);
	buff[16]='\0';
	std::cout<<"["<<buff<<"]"<<std::endl;

The outputs are the same.

A bug is CHash
	int32_t index_of(const K& key)
	{
		int32_t index=hash(key);
		CMapNode<K ,T>* result=chain_search(index, key);

		if (result!=NULL)
			return result->index;

		return -1;
	}

    int32_t hash(const K& key)
    {
        return CHash::MurmurHash3((uint8_t*)(&key), sizeof(key), 0xDEADBEEF) % hash_size;
    }

The bug is CHash::MurmurHash3((uint8_t*)(&key), sizeof(key), 0xDEADBEEF) can return negative value

why is it a bug that the hash can return a negative value? i mean the function defintion is int32_t hash(const K& key) which means that the return value is signed, i.e. half of the time it should actually return negative values...

on the other hand using that as an index is a pure choice... since the definition of murmurhash3 is static uint32_t MurmurHash3(uint8_t* data, int32_t len, uint32_t seed) you can simply change the definition in CMap::hash to return uint32_t, this way the there will be no problems with negative values

@vigsterkr
Author of Map uses int32_t everywhere.

@vigsterkr
I write an unit test and it give a segment fault due to the conversion between unit32_t to int32_t.
For example, the positive range represent by int32_t is  less than the positive range represent by unit32_t

@vigsterkr
We need to change the index from int32_t to unit32_t.

@yorkerlin no you don't need to: sizeof(int32_t) = sizeof(unit32_t) except that the MSB is in one case part of the number while the other case it's the sign value...

and please note the modulo hash_size... i  mean by default the hash is a bucket of 41 different values...

I think the main issue is
return CHash::MurmurHash3((uint8_t*)(&key), sizeof(key), 0xDEADBEEF) % hash_size;

(uint32_t) % (int32_t), it seems compiler will autocratically convert unit32_t to int32_t.
If so, the fix is
return CHash::MurmurHash3((uint8_t*)(&key), sizeof(key), 0xDEADBEEF) % (unit32_t) hash_size;

@vigsterkr
The fix works!

@vigsterkr
My bad.
The conversion from unit32_t to int32_t is due to a method used by me.

The issue is solved.
I close this


[dv] Security Feature Coverage

Document and add coverage points then ensure they're getting hit for:

[ ] Data independent timing enabled  whilst executing all instruction categories - Estimate 2
[ ] Random instruction generation

[ ] enabled whilst executing all instruction categories  - Estimate 2
[ ] Random instruction generated, for all possible kinds of random instruction - Estimate 2
[ ] Cross of different generator configurations  - Estimate 2

[ ] Various faults seen - Estimate 2

[ ] Register File ECC fault seen
[ ] Register File write enable glitch fault seen
[ ] Lockstep glitch fault seen
[ ] Icache ECC Fault seen

Estimate 10

Per discussion in internal HW meeting, Canberk going to work (with Andreas) on this. Priority on this over CSRNG V2 items as Ibex V2S scheduled for next week. If it is going to take substantial effort, then Canberk to message @GregAC given that CSRNG also needs substantial time based on initial scoping work.

remaining 2022-11-01 2


Switch from snapshot to officially published releases of JavaParser

alpha1.patch
Currently, the code is using a custom artifact of JavaParser, i.e., Lib/javaparser-core-3.0.0-SNAPSHOT.jar. Of course, there is an officially published release: javaparser-core-3.0.0-alpha.1.jar. For consistency, the officially published release should be used.
After applying the patch and after processing the JAR file javaparser-core-3.0.0-alpha.1.jar with the new IKVM, the code compiles without any errors or warnings.

The same is the case for the release javaparser-core-3.0.0-alpha.2.jar.
alpha2.patch

From the release javaparser-core-3.0.0-alpha.3.jar and up, any attempt to compile the code runs into errors. So, changes are required to use at least javaparser-core-3.0.0.jar. Note that in the meantime javaparser-core-3.25.3.jar has been published (cf. https://github.com/javaparser/javaparser/releases/latest).
alpha3.patch

@Adrian-Devries Thanks for the info, this is already being tracked as #12, so closing this as duplicate. There are a few IKVM things standing in the way at the moment for me, working through those. Thanks!


pathfinder: stringify args expecting numbers

I cba to test but I believe 515 changed some behavior related to this

tgmc is the one who uses this anyways, so you probably know best


Custom parameters in pg connection string

I'm attempting to use the Postgres driver for SQLx to connect to a hosted CockroachDB. Due to the server implementation, the connection requires passing in some custom parameters, so the connection string looks like this:
let pool = PgPool::connect(
  "postgres://user:pass@free-tier.gcp-us-central1.cockroachlabs.cloud:26257/db?options=--cluster%3Dmy-serverless-db-1234"
).await?;

Based on the error I get back (Error: error returned from database: codeParamsRoutingFailed: missing cluster name in connection string), it seems like SQLx is dropping the unknown options param from the query string because it's unrecognized.
Is there a good workaround for this presently or would we need to add support for an arbitrary map of options when connection?

That's actually being worked on in #1539 right now.

Closed by #1539


Be able to set buffer-size at layer level

With mapnik we can set buffer-size at layer level:
<Layer name="wadus" srs="+init=epsg:3857" buffer-size="64">
If we try to set buffer-size at layer level directly in CartoCSS:
#layer { buffer-size: 64 }
then carto raises the following error:
Error: Map properties are not permitted in other rules
In order to take advantage of mapnik's feature we need to be able to set buffer-size as layer's property as we can do at Map level.
cc @rochoa, @javisantana, @jorgesancha

what reference are you using?
If we can use the Map {} buffe-size I think is an low priority issue

To be clear: this is a nice to have, we don't need it for the migration.


Add CI (pre-commit.ci) for running pre-commit as CI

the pre-commit.ci CI will automatically run pre-commit config via CI pre-commit-ing PRs.
TODO: Add correct link to pre-commit.ci badge. @fneum
Change proposed in this Pull Request
n/a

Description

n/a
Motivation and Context

Easier than GitHub Actions.
How Has This Been Tested?

In different repository.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] I tested my contribution locally and it seems to work fine.
[ ] I locally ran pytest inside the repository and no unexpected problems came up.
[ ] I have adjusted the docstrings in the code appropriately.
[ ] I have documented the effects of my code changes in the documentation doc/.
[ ] I have added newly introduced dependencies to environment.yaml file.
[ ] I have added a note to release notes doc/release_notes.rst.
[ ] I have used pre-commit run --all to lint/format/check my contribution

Due to reasonable concerns brought up in https://github.com/pre-commit/pre-commit-hooks/issues/291, we should not add pytest to the commit hooks (commits should be fast). So I'd say, we set up GH actions for testing and deploying (instead of travis) side by side with pre-commit ci.

TODO: Add correct link to pre-commit.ci badge. @fneum

see suggestion, as if already in master.


Show percentage spread on market overview spread column

At the moment we show spread as an absolute value:

Could we add percentage (relative to mid say)? Maybe for spread we may prefer to show bps (basis points).

Going to include this in the  market page overhaul ... dont do it yet,

Included as AC on #5095


Fix entity names to avoid duplicate "tempest"

After upgrading to 2023.8.0 I was met with this message:
Some MQTT entities have an entity name that starts with the device name. This is not expected. To avoid a duplicate name the device name prefix is stripped of the entity name as a work-a-round. Please inform the maintainer of the software application that supplies the affected entities to fix this issue.
List of affected entities:

sensor.tempest_pressure_trend
sensor.tempest_solar_elevation
sensor.tempest_wind_speed
sensor.tempest_snow_probability
sensor.tempest_air_density
sensor.tempest_rain_today
sensor.tempest_zambretti_number
sensor.tempest_lightning_count
sensor.tempest_dew_point
sensor.tempest_solar_radiation
sensor.tempest_sea_level_pressure
sensor.tempest_precipitation_type
sensor.tempest_fog_probability
sensor.tempest_rain_rate
sensor.tempest_temperature
sensor.tempest_station_pressure
sensor.tempest_lightning_count_today
sensor.tempest_lightning_distance
sensor.tempest_last_lightning_strike
sensor.tempest_dewpoint_comfort_level
sensor.tempest_rain_duration_yesterday
sensor.tempest_temperature_level
sensor.tempest_wind_speed_avg
sensor.tempest_wind_gust
sensor.tempest_uv_index
sensor.hub_hb_00123976_weather
sensor.tempest_cloud_base_altitude
sensor.tempest_zambretti_text
sensor.tempest_uv_level
sensor.tempest_wet_bulb_globe_temperature
sensor.tempest_rain_yesterday
sensor.tempest_illuminance
sensor.tempest_last_rain_start
sensor.tempest_lightning_count_last_hour
sensor.tempest_battery
sensor.tempest_beaufort_scale
sensor.tempest_delta_t
sensor.tempest_freezing_level_altitude
sensor.tempest_wind_bearing_avg
sensor.tempest_battery_mode
sensor.tempest_lightning_energy
sensor.tempest_wet_bulb_temperature
sensor.hub_hb_00123976_status
sensor.tempest_lightning_count_3_hours
sensor.tempest_wind_bearing
sensor.tempest_rain_duration_today
sensor.tempest_visibility
sensor.tempest_wind_direction
sensor.tempest_absolute_humidity
sensor.tempest_wind_lull
sensor.tempest_voltage
sensor.tempest_wind_direction_avg
sensor.tempest_solar_insolation
sensor.tempest_status
sensor.tempest_humidity
sensor.tempest_rain_intensity
sensor.tempest_feels_like_temperature

It also included the note that "This stops working in version 2024.2.0. Please address before upgrading.", so we have some time to fix this, but it still needs addressing.

@pcfens Everyone got this, it's not related to WeatherFlow, it's an issue with HA that the forums say will be addressed in September and can safely be ignored.  Apparently they did some changes in MQTT regarding the names but have not written the mitigation needed to avoid this message.

That sounds way better than having to patch everything. Thanks for the quick reply.

You were only lucky, I was here to report an issue with the hourly weather being broken for 8.0 :).


[WIP] [deliver] Adding in platform support for deliver

This is a WIP at the moment to add platform support to deliver.
This is dependent on #4447 and may need even more changes as well on that pull request.

Closing this as it depends on items from #3825

:+1: This looks good and we can merge it once #4781 is merged.

@mpirri This is #4781 😉

Somebody now when whe tvOS support will come? :)

@nonnname Sorry for delay, will look into this shortly.

@bassrock Can you rebase this from master so that we can merge this as soon as #4447 is merged?  Thanks!

@mpirri Rebased!


Feature Request: Authentication needed for public domain

In order to use in Public domain, we need to ability to password protect our Langflow instances in  public domain. Without this feature I cant use langflow on a vps or vm instances .

Going to second this. Why is there no authentication? Basic password and username option is a quick add. Thanks

Thank you for the feedback! We're actively working on implementing this improvement, and you can expect it to be fully addressed in the upcoming release.

Very much needed, would like to have authentication

I was going to open this same feature request just right now. Following...

also in need of this :)

We have a working pre-release version (0.5.0a0, you should be careful deploying it over your current setup) and the dev branch also is constantly being updated to flesh out this feature.


docs: pythonhosted.org -> readthedocs.io

Signed-off-by: Jiri Kuncar<EMAIL_ADDRESS>

Why are we changing to ReadTheDocs?

:scream:


Issues with stack clearing while in Editor

Describe the Bug
When in editor mode, clearing the cursor doesn't work while time is frozen.
To Reproduce
Steps to reproduce the behavior:
activate editor mode.
set time to frozen.
take an item, and build it on the world.
clearing the cursor should stop working at this point while time is frozen.

Thanks for the report, fixed for the next release.


Allow dynamic linking

I want to be able to specify that go/who/{NAME} unpacks into: https://github.com/{NAME}.
This allows for more flexible links that plug into my workflow.
Use cases:

Engaging multiple search engines from the browser: e.g go/google/{QUERY} vs. go/duckduckgo/{QUERY}
Sanely exploring sub-domains: e.g go/r/{SUBREDDIT} -> https://reddit.com/r/{SUBREDDIT}

The google DeclarativeNetRequest paradigm makes this difficult because it expects to have explicit URL-redirect rules. We'd need some kind of just-in-time creation-and-destruction of rules to make this happen—or switch paradigms altogether.

Making sure to reserve 1000 IDs of the allowed dynamic rules space to see if we can use those for this feature in this #15


Tidyup and re-enable a LocalChannel test

Previously this was in the /integration/ test directory, which is skipped when running automatic tests (due to a filter in conftest.py)
Type of change

Code maintenance/cleanup

I'm mildly curious why not just remove the test entirely? It's been unused ~forever, and channels are imminently going away.

There's a lot of complexity removing channels, because they aren't "not used" - they're tangled throughout our provider layer.
So the process of removing them is probably not a simple "merge these 74 commits in PR #3650 all in one go"
... and at the end of #3650, the execute_wait part of LocalChannel stays in the codebase, just no longer inside the channel abstraction.
So this test probably should stay around in some form or another to test that execute_wait continues to work as #3650 is piecewise merged, and onwards.

(execute_wait ends up in parsl.utils in #3650)


Grafana Version Tested

Hi paregupt,
I'm having a few issues to put the dashboards to work and I think that it's related to my grafana version. Could you please provide the versions that you tested it so I can compare here with mine?
Regards,
lzsilva-br

Just replying to myself to maybe help anyone in the future. My Grafana installation was 6.7.1 and after upgrade it to the current latest version (9.5.2) all dashboards starts to working like a charm.
Thanks for the dashboards, paregupt.
Regards,
lzsilva-br

Thanks for verifying it. MTM is based on UTM. Grafana version 6.x is old. AFAIR they restructured the queries in 7.x. Glad to know that even 9.x works fine. If you find something broken, let me know. Should be minor change to fix such issues.