use stat. codes for permissions

This should set the permissions on the _.nwb file and AnalysisNWBFiles to 644 to make sure that only the user can delete them. I have not yet tested this, however.

I tested by inserting a raw nwb file into database, then populating a table that created new analysis nwb files -- see resultant permissions below
alison@petrichor /stelmo/nwb/raw $ ls -l senor20201104*
-rwx------ 1 alison kachery-users<PHONE_NUMBER>9 Feb 24 08:34 senor20201104_.nwb
-rw-rw-r-- 1 alison root<PHONE_NUMBER>17 Dec 24 06:00 senor20201104.nwb

alison@petrichor /stelmo/nwb/analysis $ ls -l senor20201104*
-rwx------ 1 alison root 130944272 Feb 24 09:05 senor20201104_03U2PKGLCZ.nwb
-rwx------ 1 alison root  40179992 Feb 24 09:08 senor20201104_2600YVS6TN.nwb
-rwx------ 1 alison root  44802824 Feb 24 09:05 senor20201104_4XUGZN0V43.nwb
-rwx------ 1 alison root  65931440 Feb 24 09:11 senor20201104_6E3B9QDDZ6.nwb
-rwx------ 1 alison root   4784216 Feb 24 09:00 senor20201104_A1705PUKH4.nwb

Got. Not what I had intended, so I must have chosen the wrong permissions bits. I’ll look into that.
On Feb 24, 2022, at 9:19 AM, acomrie<EMAIL_ADDRESS>wrote:
This Message Is From an External Sender
This message came from outside your organization.
I tested by inserting a raw nwb file into database, then populating a table that created new analysis nwb files -- see resultant permissions below
@.*** /stelmo/nwb/raw $ ls -l senor20201104*
-rwx------ 1 alison kachery-users<PHONE_NUMBER>9 Feb 24 08:34 senor20201104_.nwb
-rw-rw-r-- 1 alison root<PHONE_NUMBER>17 Dec 24 06:00 senor20201104.nwb
@.*** /stelmo/nwb/analysis $ ls -l senor20201104*
-rwx------ 1 alison root 130944272 Feb 24 09:05 senor20201104_03U2PKGLCZ.nwb
-rwx------ 1 alison root  40179992 Feb 24 09:08 senor20201104_2600YVS6TN.nwb
-rwx------ 1 alison root  44802824 Feb 24 09:05 senor20201104_4XUGZN0V43.nwb
-rwx------ 1 alison root  65931440 Feb 24 09:11 senor20201104_6E3B9QDDZ6.nwb
-rwx------ 1 alison root   4784216 Feb 24 09:00 senor20201104_A1705PUKH4.nwb
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/LorenFrankLab/nwb_datajoint/pull/128*issuecomment-1050079563__;Iw!!LQC6Cpwp!9NyYIN-m34GGJ--hNZXkny1kvBETuVAj6Y1DblZsh9iYDEnMwkSOLrhbRy9-dgGCcQ$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ABV4PSKLGPEWEFSTSXSAA6LU4ZSB7ANCNFSM5PGGIXSA__;!!LQC6Cpwp!9NyYIN-m34GGJ--hNZXkny1kvBETuVAj6Y1DblZsh9iYDEnMwkSOLrhbRy_BbT0RVA$.
Triage notifications on the go with GitHub Mobile for iOShttps://urldefense.com/v3/__https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675__;!!LQC6Cpwp!9NyYIN-m34GGJ--hNZXkny1kvBETuVAj6Y1DblZsh9iYDEnMwkSOLrhbRy-o0CZfhw$ or Androidhttps://urldefense.com/v3/__https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign*3Dnotification-email*26utm_medium*3Demail*26utm_source*3Dgithub__;JSUlJSU!!LQC6Cpwp!9NyYIN-m34GGJ--hNZXkny1kvBETuVAj6Y1DblZsh9iYDEnMwkSOLrhbRy8awFvHXg$.
You are receiving this because you authored the thread.

new test -
alison@petrichor /stelmo/nwb/raw $ ls -l senor20201104*
-rw-r--r-- 1 alison kachery-users<PHONE_NUMBER>9 Feb 24 10:13 senor20201104_.nwb
-rw-rw-r-- 1 alison root<PHONE_NUMBER>17 Dec 24 06:00 senor20201104.nwb

and for an analysis nwb file -
-rw-r--r-- 1 alison root 4600328 Feb 24 11:12 senor20201104_LPOTEDQD79.nwb

@acomrie Is this ready for merging from your perspective?

Yes, was planning to mention it at lab meeting today then merge!
On Tue, Mar 1, 2022 at 10:08 AM Loren Frank @.***>
wrote:

@acomrie https://github.com/acomrie Is this ready for merging from your
perspective?
—
Reply to this email directly, view it on GitHub
https://github.com/LorenFrankLab/nwb_datajoint/pull/128#issuecomment-1055716374,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK7G2BK3NNYLWNIPYUFP2ADU5ZMKJANCNFSM5PGGIXSA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>


Feature: Flag/ENV to show output

Please add a flag(s) and/or an env variable(s) to show stdout & stderr output from the library benches and from binary benches.
Like https://doc.rust-lang.org/cargo/commands/cargo-bench.html#display-options > cargo bench -- --nocapture, or https://doc.rust-lang.org/nightly/book/ch11-02-running-tests.html#showing-function-output > cargo test -- --show-output.
If that is difficult, or not fitting the design, for library benches, please add a config option to show result returned from a (library) bench function if it implements ToString.

Hi. I like the idea. I thought about a teardown function similar to the way you can specify a setup function in the benches attribute. Roughly like this
use iai_callgrind::{library_benchmark, library_benchmark_group, main};

fn my_setup_func(a: i32, b: i32) -> Vec<i32> {
    vec![a, b]
}

fn my_teardown_func(output: Vec<i32>) {
    for i in output {
        println!("{i}");
    }
}

#[library_benchmark]
#[bench::with_setup_and_teardown(args = my_setup_func(1, 2), teardown = my_teardown_func)]
#[benches::multiple(args = [(1, 2), (3, 4)], setup = my_setup_func, teardown = my_teardown_func]
fn my_bench_function(input: Vec<i32>) -> Vec<i32> {
    input
}

library_benchmark_group!(
    name = bench_group;
    benchmarks = my_bench_function
);

main!(library_benchmark_groups = bench_group);

You can then do whatever you want with the result of the benchmark function. What do you think?
Although it's not the same, currently you can use the environment variable IAI_CALLGRIND_LOG=info. There's maybe more output than you actually need and the output is still captured and therefore stdout and stderr are printed separately but you can at least see the output of the benchmark function.

I think this issue is resolved with #192, #194. See the prs or the README for more details.
In short: (#192) The #[library_benchmark], #[bench] and #[benches] attribute now accept a teardown paramater, which takes a path to a function which is applied to the return value of the annotated benchmark function. (#194) Also, running cargo bench -- --nocapture tells iai-callgrind to not capture the output of the callgrind run. @peter-kehl Do you need anything else?

Closing this as completed.


Large stored values likely lead to unnecessary read load

The way leaf nodes are designed doesn't seem like it will perform very well if the stored values are large. Because values are embedded directly in leaf nodes, operations that nominally only need to manipulate the structure of a node will end up loading all of the data from the value. One example of this is when an insertion happens in a leaf node: this should not require pulling all the leaf node's attached value data from disk, but it does.
Maybe this was an acceptable design for Diem because the values were mostly things like account balances, which are small, but our values are sometimes larger structured data like compact blocks. This probably has a performance impact—path compression means that when you insert, you are always going to subordinate an existing leaf to a newly created internal node somewhere, so you always have to load a leaf's data that you didn't need to. We could benchmark this by instrumenting the MockTreeStore to record number of bytes written and read.
It's worth noting that we don't have to write back the value of the leaf unless it changes, because we can reuse the same node jet as the child of a newly created internal node, so it's primarily read volume and memory usage that is negatively affected by this design.
Another level of indirection would solve this: it would penalize every get operation by one extra database query, but would reduce the memory usage and read volume proportionate to the size of the values we store. The way we would do this would be to add another kind of node, a Payload node, with tag 4, that holds the actual value contained in a leaf. Every leaf would have a NodeKey that points to its payload. Updating a leaf's payload would require only updating the Payload node, not the leaf node itself. This would mean that no matter how large a leaf's associated data, manipulating parts of the tree that touch that leaf doesn't require loading the leaf's payload unless we explicitly need it during a get operation for that leaf itself.

This is fixed already.
The reason pd isn't on JMT 0.4 is because we have to change our RocksDB usage because the leaf DB values are separated out.


Store binary caches on Cachix?

It'd be great if there were binary caches somewhere, like on Cachix, since when I try to use the Dell XPS 13 9310 configuration, it tries to rebuild my whole kernel, and you know, ain't nobody got time for that.

Is there any way to reduce build time yet? At least a method to rebuild faster?
I am new to NixOS, so any direction would be nice.

@zimbatm can we enable hydra on this repository?

Good idea. Can you add a declarative pipeline to the repo first?

@Mic92 can I help you here? I'm planning to push some stuff in nixos-hardware for routers.

If you can add a declarative hydra config to this repo, I can then connect it Hydra.


Unable to hit enter after @addTagHelper directive

This is a weird one. The editor basically acts as if the enter key doesn't work immediately following this helper.
VS 2017 Build: 15.0.0+26288.0
Repo: https://github.com/MiniProfiler/dotnet/
File: samples/Samples.AspNetCore/Views/Shared/_Layout.cshtml
When adding a directive like this (no quotes):
@addTagHelper *, MiniProfiler.AspNetCore.Mvc

If your cursor is at the end of the line right after the c, the enter key just doesn't work. It has no effect, no new line is inserted. The key command goes into a black hole of an uncaring cosmos never to return.
Workarounds

Add a space, then hit enter
Use the quoted form: @addTagHelper "*, MiniProfiler.AspNetCore.Mvc"

Apologies if this is a duplicate, I couldn't find anything on it and just came across it today.

Doh, found the dupe thanks to @scottaddie: https://github.com/aspnet/Tooling/issues/945 Closing this and linking back, tooling is the more appropriate place it seems.

The key command goes into a black hole of an uncaring cosmos never to return.

❤ it

Re-opening until we verify that this is only a tooling issue.

Let's debug this and see if our code gets called

This is being tracked here https://devdiv.visualstudio.com/DevDiv/_workitems?_a=edit&id=369170&triage=true

This has been fixed in on the non-OSS side. Please verify 👍


Start versioning docs with the next release

This is two changes in one:

Add a dropdown for version selection to the docs on vast.io.
With the next release, automatically create a saved version of the docs when running the prepare-release script.

If you want to see what this looks like locally, run yarn docusaurus docs:version v3.0.0 from the web directory, and then preview with yarn docusaurus start as usual.

Nice. I always shied away from this changed because I thought it's a massive change. This looks like a clean surgical operation.

Can we rename "next"?

I'm not sure. I'll make sure to align it, but if it's a tough change to make then I'll unbureaucratically align unreleased to next in the changelog.
There's one other thing we need to change, but that's also mostly mechanical: Images in /static are unversioned (by design), so we need to move those referenced in the documentation over into the /docs directory.

There's one other thing we need to change, but that's also mostly mechanical: Images in /static are unversioned (by design), so we need to move those referenced in the documentation over into the /docs directory.

@dit7ya will love this, as it breaks the carousel fix for good.

@dit7ya will love this, as it breaks the carousel fix for good.

The carousel images are in blog posts, so they should be in /static anyways.

From https://docusaurus.io/docs/2.1.0/versioning:

By default, the current docs version is labeled as Next and hosted under /docs/next/*, but it is entirely configurable to fit your project's release lifecycle.

I want to make the following changes still:

Move blog assets to /static
Move docs assets to /docs
Rename changelog unreleased to next (or vice versa if possible, but appears unlikely)
Use relative links to .md files when cross-referencing docs
Avoid creating a new docs version with patch releases, they should instead update the matching minor release docs (e.g., cutting v3.0.1 should update the docs for v3.0)

Still some work to do, but it's mostly mechanical and can partially be automated. I think I may let this sit for a while as it's not high up on my priority list, but this is something that I can easily take care of whenever I feel like working on something that requires very few brain cells being available.

Use relative links to .md files when cross-referencing docs

Aren't we doing this already?

Aren't we doing this already?

It's mostly /docs/foo/bar that we use, but that has to be @site/foo/bar.md instead. This will also cause Docusaurus to properly error on wrong links.

It's mostly /docs/foo/bar that we use, but that has to be @site/foo/bar.md instead. This will also cause Docusaurus to properly error on wrong links.

That feels very unergonomic. When you are in foo/, you should be able to just link to bar.md.

That feels very unergonomic. When you are in foo/, you should be able to just link to bar.md.

That also works, you're just not allowed to start your links with a leading slash.

@dominiklohmann if you wait for #2879, I can do the movement into /docs as part of the image re-generation.

FWIW, this is unblocked now and only requires a rebase onto latest master.

We decided to add the relative links to #2971 instead, so I'm going ahead with merging this one.


Usage of deprecated k6 APIs

When running the latest xk6-kafka from master the following message appears:
Module 'k6/x/kafka' is using deprecated APIs that will be removed in k6 v0.38.0, for more details on how to update it see https://k6.io/docs/extensions/guides/create-an-extension/#advanced-javascript-extension
What should be done:

Identify deprecated API calls
Replace API calls

https://k6.io/docs/extensions/guides/create-an-extension/#advanced-javascript-extension

@thmshmm I fixed the issue in #41. but the are some regressions, which I'll fix.

The fixes on merged now, but not released because I couldn't figure out how to test SASL (no SSL), and I need someone to test it against a working instance of Kafka with SASL PLAIN/SCRAM enabled. I'll merge this, but won't release it until I fully test it. This means that you can test the feature by compiling with the latest commits on the main branch, but it won't be available as binary and a Docker image yet.


Modify existing code base v1.0

Created 1 new module (expense) under src/main/java/model/ with 4 new classes:

Expense
Description
Category
Amount

Modified some code base to adapt to our project. Yet to remove existing module for person under the same module created above.

I reverted cause the CI was failing for your addition @lamwj98


AcceptDialog does not show the whole title if the title is too long

Tested versions
Godot v4.3.dev (b94eb58d3)
System information
Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 (NVIDIA; <IP_ADDRESS>19) - 11th Gen Intel(R) Core(TM) i7-11700K @ 3.60GHz (16 Threads)
Issue description
When trying to reproduce https://github.com/godotengine/godot/issues/86226, I noticed that the AcceptDialog with the title : "Auto Create Tiles in Non-Transparent Texture Regions?" does not show the whole title as the image shown:

After some quick search, I find that in the ctor of AcceptDialog it did call the set_keep_title_visible(true), but the window's window_id is -1 so the following responsible code did not get excuted.
if (!embedder && window_id != DisplayServer::INVALID_WINDOW_ID && keep_title_visible) {
	Size2i title_size = DisplayServer::get_singleton()->window_get_title_size(tr_title, window_id);
	size_limit = size_limit.max(title_size);
}

Steps to reproduce
Follow the same step as https://github.com/godotengine/godot/issues/86226
After drag the provided png to create a tileset, the dialog will appear.
Minimal reproduction project (MRP)
Same as https://github.com/godotengine/godot/issues/86226

After some quick search, I find that in the ctor of AcceptDialog it did call the set_keep_title_visible(true), but the window's window_id is -1 so the following responsible code did not get excuted.

That's not why it doesn't get executed. We don't even call _update_window_size() from set_keep_title_visible() is the window ID is invalid. And whenever we assign the window ID, we do call _update_window_size().
In your screenshot you're using the single-window mode. Which means that all windows are embedded. Which doesn't pass the !embedder check. This feature for keeping the title fully visible is only for detached windows, I'm not sure we have anything in place for embedded windows.

Yes the screen shot above is using single window mode, but if I change to not use this mod, same will happen too :

Step into it will clearly show that window_id is -1 when the AcceptDialog pop up:

Hi @jsjtxietian, does this issue still exist? I cannot reproduce this in Windows 11 Godot v4.3.dev (#9c626b6).

@eugene87222  I'm stilling can see this in Godot v4.3.dev (ae51db75e) - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 (NVIDIA; <IP_ADDRESS>19) - 11th Gen Intel(R) Core(TM) i7-11700K @ 3.60GHz (16 Threads)

Not able to reproduce:

Godot v4.4.dev (efc7c628b) - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1070 (NVIDIA; <IP_ADDRESS>23) - Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz (8 Threads)


Components.TryGet() is not clear that you will only get a component copy and not a modifiable ref

if (HealthComponents.TryGet(entity, out var health))
{
    health.CurrentValue = 10;
}

This will compile and run without warning, but health component will never be modified. It is currently not really clear that this is the case and can cause unwanted time spent debugging.

Yes, the subtleties of using structs can be surprising sometimes. I will investigate a solution which will most likely take the form of a compiler warning.


Add KmsKeyId to the Redshift function.

As per http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-redshift-cluster.html#cfn-redshift-cluster-kmskeyid

Since the build's been failing for a week I'm assuming that this addition didn't cause the issue...


fix(controller): disallow unauthorized users from deleting apps

Authenticated users who were not given explicit permission to view
or modify an application were still allowed to delete other user's
applications, should the unauthorized user know what the ID of the
application would be. This returns a 404 message if the user is
unauthorized to see the application.
Because we were calling get_object_or_404(), we were not performing
any authorization against the API call. Calling self.get_object() is
the preferred method to retrieve an object since it authenticates
against the classes' permissions classes to ensure that the user is
authorized to see the application.
This also fixes up an issue where administrators were not explicitly
given permission to an app. They fell through the same "unauthorized"
issue as above.
closes #2845
closes #2846

get_object_or_404 is a standard Django view func, but self.get_object is a DRF method, so I see why the latter is preferable to invoke the intended auth. This code LGTM, but I'm going to test it by hand for a while as well.

also fixed up #2846 with this one.

Do we know why the rollback test didn't catch this?

Do we know why the rollback test didn't catch this?

I'm not quite sure. I'm still investigating the issue there, but this patched up the issue :)

I've tested this by hand and can't find any gaps now. After discussing this, we still want to revert some of the 404s to 403s, but we can do that in a subsequent PR.
LGTM.

Code LGTM.

unit tests passed with the most recent commit. No code changes were made; it was just fixing up the issue @carmstrong mentioned in https://github.com/deis/deis/pull/2853#issuecomment-68910935. Merging!


test/http: decrease test runs from 20 to 3 to decrease test time

Improves performance of test/http: https://github.com/baresip/re/issues/1211

Thanks, this looks much better .. do you have any numbers for benchmarking on Linux ...?
test_https_conn_post_handshake takes ~280ms instead ~1850ms on linux.


Create ability to share data sources to one/ all users

On the sharing a data source with other users feature:
Create ability to share to all  users &  the option to select the users to share the data source to.

This feature is now available in version 2.2.0


Idea: Filename example "{title} 005.cbz"

I've been trying to look for an argument in one of the features inside your project, but I can't find a way to get the manga title and then chapter number after it without volume number included, for example most of LuCaZ' files look like this but I can't find a way to do it about the same way.
How my files look now:
01.001.cbz
01.002.cbz
02.003.cbz
02.004.cbz
How I want it:
{title} 001.cbz
{title} 002.cbz
{title} 003.cbz
{title} 004.cbz
Example:
Chainsaw Man 001.cbz
Chainsaw Man 002.cbz
Chainsaw Man 003.cbz
Chainsaw Man 004.cbz
Chainsaw Man 005.cbz
Thanks a lot for this repo, has helped me out a lot already :)

So you want to add the --title input as the filename?
It might be a good idea to create an option to modify output format I guess.
I'll try to implement it this week, for now you can install regex-renamer and use it like this:
$ regex-rename '(\d+)\.(\d+).*.cbz' 'Chainsaw Man \2.cbz' --rename

Thanks! 🙏


Ability to store created twitter walls with the account

User should be able to create a set of twitter walls with different configurations and have them associated with the user's account.
Requires support from loklak_server for storage. (Will create issue soon)

I propose to store the configuration together with authentication json in a property 'apps'. Thats already implemented! Set apps to a json like
apps: {wall:{ .. your wall data }}

so every loklak app can add their property too.

Perfect! Is there a limit on how much data can be stored? Lets say, if i wanted to store a base64 image inside the JSON, would it be okay?

There is no limit yet. Should we set one?

Other apps (like the ones rendering images of maps) would store any amounts of images with an account. While there is no need for setting a limit now, there could be space constraints later. I am not sure about this, I leave that to you.

maps shall not be stored in that way but generated on-the-fly using the feature in https://github.com/loklak/loklak_server/issues/39

The account servlet can now be only accessed from localhost for security reason. Please check if this affects your architecture. Maybe this servlet must be retrieved through a proxy, i.e. the oauth_proxy (if applicable)

I'll edit the issue.

@aneeshd16 Do you have an update here?

#102, #103, and #74 are to be implemented together.Can we move this to M2.5?

Process to be followed:
If user is signed in:
    Get all user data from loklak_server
    Do changes
    Save all user data to loklak_server

Incremental updates are not possible as of now due to the nature of the API, so the the entire user data has to be loaded and saved everytime.

Closed via 67308b8826bb565873bf95432965f8dacca9c2cd


zIndex is broken across ScrollViews

🐛 Bug Report
zIndex is broken when you have a ScrollView between your two different zIndexes.  For example, given code like
render() {
    return <View style={styles.background}>
        <View style={styles.redBox}></View>
        <View>
            <View style={styles.greenBox}></View>
        </View>
    </View>
}

let styles = StyleSheet.create({
    background: {
        backgroundColor: "blue",
        height: "100%"
    },
    greenBox: {
        backgroundColor: "green",
        width: 100,
        height: 100,
        zIndex: 2
    },
    redBox: {
        height: 300,
        width: 300,
        backgroundColor: "red",
        position: "absolute",
        top: 0,
        left: 0,
        zIndex: 1
    },
});

you get a view that makes sense, blue background, then red box, then green box on top.

However, if you just switch the container of the green box to a ScrollView, the zIndex breaks:
<View style={styles.background}>
   <View style={styles.redBox}></View>
   <ScrollView>
        <View style={styles.greenBox}></View>
    </ScrollView>
</View>

Expected Behavior
Components inside of a ScrollView should still respect zIndex.
Code Example
import React, { Component } from 'react';
import {
    View,
    ScrollView,
    StyleSheet,
 } from 'react-native';

export default class App extends Component {
    render() {
        return (
            <View style={styles.background}>
                <View style={styles.redBox}></View>
                <ScrollView>
                    <View style={styles.greenBox}></View>
                </ScrollView>
            </View>
        );
    }
}

let styles = StyleSheet.create({
    background: {
        backgroundColor: "blue",
        height: "100%"
    },
    greenBox: {
        backgroundColor: "green",
        width: 100,
        height: 100,
        zIndex: 2
    },
    redBox: {
        height: 300,
        width: 300,
        backgroundColor: "red",
        position: "absolute",
        top: 0,
        left: 0,
        zIndex: 1
    },
});

Environment
Environment:
OS: Windows 10
Node: 9.3.0
Yarn: 1.3.2
npm: 4.6.1
Watchman: Not Found
Xcode: N/A
Android Studio: Version  <IP_ADDRESS> AI-181.55<IP_ADDRESS>56338
Packages: (wanted => installed)
react: 16.3.2 => 16.3.2
react-native: ^0.55.4 => 0.55.4
It's worth noting that on iOS not even the working example I give here works, it doesn't show the green box above the red one ever.

See https://github.com/facebook/react-native/issues/23615#issuecomment-466717338

Yeah I think the fact that green renders on top at all is the bug, unfortunately...

@acb Why did you close this? I'm experiencing this issue too.

I'm experiencing this issue too.

@tmaly1980 I guess this can be re-opened -- it's pretty similar to https://github.com/facebook/react-native/issues/23615, which has a snack that's an easier reproduction.
Personally I gave up on doing what I was trying to do with z-index and found another approach so I haven't been following these cases at all.

@acb I can't speak for others still experiencing this issue, but I was able to fix my issue by applying zIndex to both sibling and shared ancestor components.

scrollview is not working for me too on android. it works on ios.

any fixes/ alternatives or workaround for this?

for me it works in in scrollView i provide in contentContainerStyle={{flex:1}}.

@aditya1711
HI, Thanks for your reply.
I am not sure you tested it in 2 different ScrollViews.
I am going to implement drag/drop between two scrollviews but one directional dragging item was hiden by alternative target scrollview.
Could you verify for my actions?

@aditya1711
HI, Thanks for your reply.
I am not sure you tested it in 2 different ScrollViews.
I am going to implement drag/drop between two scrollviews but one directional dragging item was hiden by alternative target scrollview.
Could you verify for my actions?

I am unable to completely understand what you said, but I think you can have different flex values for both scroll views. But I doubt zIndex works as expected with siblings of different parents. Please try it out and let us know. I also will be prepare a better implementation of my functionality if that works.

<ScrollView style={{ zIndex: 3}} />

can you close?
<EMAIL_ADDRESS>

@fabriziobertoglio1987
Hey, you tested it in only one scrollview.
I mean drag/drop between two scrollviews.

RN 0.62.2
also having this issue , Any solution for this issue?

same issue

Scrollview with zIndex, and position absolute works someitmes and fails sometimes, still facing this issue.

same issue


Is Stable Video supported?

I'm trying to compile stable video for neuron, using:
optimum-cli export neuron -m stabilityai/stable-video-diffusion-img2vid-xt
stable_video_turbo \
--batch_size 1 --height 512 --width 512  \
--auto_cast matmul --auto_cast_type bf16

optimum-cli is complaining that it can't find a tokenizer, and sure enough there is no tokenizer subdir in the Huggingface repo.
ValueError: Pipeline <class 'diffusers.pipelines.stable_diffusion.pipeline_stable_diffusion.StableDiffusionPipeline'> expected {'tokenizer', 'image_encoder', 'unet', 'vae', 'text_encoder', 'safety_checker', 'feature_extractor', 'scheduler'}, but only {'image_encoder', 'unet', 'vae', 'feature_extractor', 'scheduler'} were passed.

The model weights svd.safetensors are sufficient to run the model in https://github.com/Stability-AI/generative-models, as suggested by the model card. So there are no missing model weights in the repository.  Is there a workaround to this compiler error?

Retrying this compilation using the version of optimum-neuron built from source (optimum-neuron @ git+https://github.com/huggingface/optimum-neuron.git@f2537d2ccb0ede387518e78e44ed6e0f7976b385), there is a similar error:
ValueError: Pipeline <class 'diffusers.pipelines.stable_diffusion.pipeline_stable_diffusion.StableDiffusionPipeline'> expected {'feature_extractor', 'vae', 'safety_checker', 'image_encoder', 'scheduler', 'text_encoder', 'tokenizer', 'unet'}, but only {'feature_extractor', 'vae', 'image_encoder', 'scheduler', 'unet'} were passed.

Hi @satsumas, the stable video diffusion is not yet supported in optimum-neuron. I am adding the support for exporting image encoder and the neuron version of StableVideoDiffusionPipeline in Optimum-neuron. I will keep you posted.

Thank you, that would be great.

Hi @satsumas, the stable video diffusion is not yet supported in optimum-neuron. I am adding the support for exporting image encoder and the neuron version of StableVideoDiffusionPipeline in Optimum-neuron. I will keep you posted.

I'm also interested in this new feature for SVD model on Inf2,  is there any approximately release date？ just roughly would be great
Thanks a lot!

@satsumas
hello satsumas
any update for the diffuser svd's neuron compile&inference?

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!

Hey @qingyuan18,
I believe we don't have SVD compiled for inf2 with optimum-neuron. You could try compiling it yourself with Inferentia's own neuronx compiler:
https://awsdocs-neuron.readthedocs-hosted.com/en/latest/compiler/neuronx-cc/api-reference-guide/neuron-compiler-cli-reference-guide.html

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!


E (1428) BT: btc_gattc_call_handler()

My scenario:
One ESP32 runs BLE_UART example
The second one runs BLE_Client (checking on name, not on UUID because I do not get the UUID)
Newest library, newest ESP32 build from yesterday. Built according to setup directions on GitHub
If I connect with my iPhone or Raspi to the UART ESP it starts to send notifications. I also see serviceUUID
The client ESP32 shows this log:
Starting Arduino BLE Client application...
BLE Advertised Device found: Name: UART Service, Address: 24:0a:c4:12:ee:ee, txPower: -21
BLE Name: UART Service
Found our device!  address: Forming a connection to 24:0a:c4:12:ee:ee

Created client
E (1428) BT: btc_gattc_call_handler()
E (1550) BT: bta_gattc_conn_cback() - cif=3 connected=0 conn_id=3 reason=0x003e
E (1550) BT: p_conn is NULL in bta_gattc_conn_cback

Connected to server

I get this error message (btc_gattc_call_handler()) with other devices like Polar H7, Xiaomi MiFloara

This is a little bit modified BLE_client from arduino test folder. Modifications are made to find the other esp32 by name, to connect with TX characteristic and to send message to RX characteristic. Only thing i have to check is why notifications are not working.

/**

A BLE client example that is rich in capabilities.
*/

#include "BLEDevice.h"
//#include "BLEScan.h"
// The remote service we wish to connect to.
#define SERVICE_UUID           "6E400001-B5A3-F393-E0A9-E50E24DCCA9E" // UART service UUID
#define CHARACTERISTIC_UUID_RX "6E400002-B5A3-F393-E0A9-E50E24DCCA9E"
#define CHARACTERISTIC_UUID_TX "6E400003-B5A3-F393-E0A9-E50E24DCCA9E"
static BLEAddress pServerAddress;
static boolean doConnect = false;
static boolean connected = false;
static BLERemoteCharacteristic pRemoteCharacteristic;
static BLERemoteCharacteristic* pRemoteCharacteristic2;
static void notifyCallback(
BLERemoteCharacteristic* pBLERemoteCharacteristic,
uint8_t* pData,
size_t length,
bool isNotify) {
Serial.print("Notify callback for characteristic ");
Serial.print(pBLERemoteCharacteristic->getUUID().toString().c_str());
Serial.print(" of data length ");
Serial.println(length);
}
bool connectToServer(BLEAddress pAddress) {
Serial.print("Forming a connection to ");
Serial.println(pAddress.toString().c_str());
BLEClient*  pClient  = BLEDevice::createClient();
Serial.println(" - Created client");

// Connect to the remove BLE Server.
pClient->connect(pAddress);
Serial.println(" - Connected to server");

// Obtain a reference to the service we are after in the remote BLE server.
BLERemoteService* pRemoteService = pClient->getService(SERVICE_UUID);
if (pRemoteService == nullptr) {
  Serial.print("Failed to find our service UUID: ");

//      Serial.println(SERVICE_UUID.toString().c_str());
return false;
}
Serial.println(" - Found our service");
// Obtain a reference to the characteristic in the service of the remote BLE server.
pRemoteCharacteristic = pRemoteService->getCharacteristic(CHARACTERISTIC_UUID_TX);
pRemoteCharacteristic2 = pRemoteService->getCharacteristic(CHARACTERISTIC_UUID_RX);
if (pRemoteCharacteristic == nullptr) {
  Serial.print("Failed to find our characteristic UUID: ");

//     Serial.println(CHARACTERISTIC_UUID_TX.toString().c_str());
return false;
}
Serial.println(" - Found our characteristic");
// Read the value of the characteristic.

pRemoteCharacteristic->registerForNotify(notifyCallback);

}
/**

Scan for BLE servers and find the first one that advertises the service we are looking for.
/
class MyAdvertisedDeviceCallbacks: public BLEAdvertisedDeviceCallbacks {
/*

Called for each advertising BLE server.
*/
void onResult(BLEAdvertisedDevice advertisedDevice) {
Serial.print("BLE Advertised Device found: ");
Serial.println(advertisedDevice.toString().c_str());

// We have found a device, let us now see if it contains the service we are looking for.
if (advertisedDevice.getName() == "UART Service") {
//
Serial.print("Found our device!  address: ");
advertisedDevice.getScan()->stop();
pServerAddress = new BLEAddress(advertisedDevice.getAddress());
doConnect = true;
} // Found our server
} // onResult
}; // MyAdvertisedDeviceCallbacks

void setup() {
Serial.begin(115200);
Serial.println("Starting Arduino BLE Client application...");
BLEDevice::init("");
// Retrieve a Scanner and set the callback we want to use to be informed when we
// have detected a new device.  Specify that we want active scanning and start the
// scan to run for 30 seconds.
BLEScan* pBLEScan = BLEDevice::getScan();
pBLEScan->setAdvertisedDeviceCallbacks(new MyAdvertisedDeviceCallbacks());
pBLEScan->setActiveScan(true);
pBLEScan->start(30);
} // End of setup.
// This is the Arduino main loop function.
void loop() {
// If the flag "doConnect" is true then we have scanned for and found the desired
// BLE Server with which we wish to connect.  Now we connect to it.  Once we are
// connected we set the connected flag to be true.
if (doConnect == true) {
if (connectToServer(*pServerAddress)) {
Serial.println("We are now connected to the BLE Server.");
connected = true;
} else {
Serial.println("We have failed to connect to the server; there is nothin more we will do.");
}
doConnect = false;
}
// If we are connected to a peer BLE Server, update the characteristic each time we are reached
// with the current time since boot.
if (connected) {
String newValue = "Time since boot: " + String(millis()/1000);
Serial.println("Setting new characteristic value to "" + newValue + """);
// Set the characteristic's value to be the array of bytes that is actually a string.
pRemoteCharacteristic2->writeValue(newValue.c_str(), newValue.length());

}
delay(1000); // Delay a second between loops.
} // End of loop

After further investigation i see there is from time to time this error:
BT: p_conn is NULL in bta_gattc_conn_cback

Closing for just now

yes, I have a Body Fat Scale which is sending notifications , i try to connect it with esp32 and registered the notifyCallback function , but it doesn't work at all.
i try to connect the scale using the FastBLE apk on Android and the notify success.

ok then, can we open new issue on this? we will make it work togheter, also im available on irc channel #esp32


Missing reference to System.Drawing ?

Version 1.0.7:

(works)
Version 1.1.0:

HOWEVER, as a caveat, if you downgrade to 1.0.7, compile, then upgrade the library to 1.1.0, it will then resolve and add the missing reference assembly??
not sure why this happens but its quite hilarious IMO

Just to clarify, you may notice that it says 'color.' instead of "Color." but it was just a typo, problem still remains with the missing assembly :P

Thanks for letting me know.  After much digging, it turns out that this is a NuGet bug that is going to be fixed soon:
https://github.com/NuGet/Home/issues/4853
I can't spend any more time on this tonight, but will come up with a workaround in the next few days.

I've just released an updated package that fixes this:
https://www.nuget.org/packages/Colorful.Console/1.1.1
System.Drawing should now be referenced automatically!  Thanks again for bringing this to my attention!


[Question] Get authenticated user from authentication middleware

Information

Version: 5.12.1
Type: Question

Description
I've created a custom authentication middleware like it is described in the documentation. To every request a session token is attached in the header. The middleware searches the database for the user record which has the session token. If there is no user with that token the middleware throws an error.
How can I provide the authenticated user, so I can access it in the controller?

I found out that the (undocumented) EndpointInfo.store does what I need.

EndpointInfo.store isn't here to store your user info. You should store authenticated user directly on the request object. Passport.js for example attach the user on request. Request is the context.
EndpointInfo.store is not documented for this reason. Isn't a kind of RequestContext. It's an Endpoint information (which endpoint - class and method name - is called by the request).
Please don't use store directly ;). Endpoint.store could be removed in future.
See you

Okay, but how can I attach something to a request? I already tried that, but the problem is, that the type of Express.Request doesn't allow that. I need a special place for that, that the client cannot set on their end.

You have to extend Express.Request with .d.ts
https://stackoverflow.com/questions/37377731/extend-express-request-object-using-typescript

Allright. Thank you for your help!


TestingCI

Why is this PR needed?
What changes were proposed in this PR?
Does this PR introduce any user interface change?

No
Yes. (please explain the change and update document)

Is any new testcase added?

No
Yes

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1838/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3578/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1843/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3582/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3585/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1846/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1850/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3589/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3591/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1852/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1853/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3592/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1854/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3593/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3594/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1855/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1859/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3599/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3601/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1862/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3605/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1866/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3606/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1867/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1869/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3608/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1873/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3612/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3616/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1877/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1886/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3625/

retest this please

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3636/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1897/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1904/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3643/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3661/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1922/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3663/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1924/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3664/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1925/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3665/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1926/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3666/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1927/

retest this please

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3667/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1928/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1932/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3671/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3676/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1937/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3681/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1942/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3688/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1949/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3690/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1951/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3692/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1953/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3696/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1957/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3699/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1960/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1962/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3701/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3705/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1966/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3708/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1969/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1970/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3709/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3765/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2025/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2031/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3774/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3776/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2034/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3781/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2039/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2045/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3787/

retest this please

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2049/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3791/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3801/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2060/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3802/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2061/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2063/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3804/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2067/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3808/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2072/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3813/

retest this please

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3826/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2085/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3828/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2087/

retest this please

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3840/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2099/

retest this please

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3842/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2101/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3843/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2102/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3846/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2105/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3849/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2108/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3850/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2109/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2111/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3852/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2112/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3853/

retest this please

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2113/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3854/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3860/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2119/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2128/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3869/

retest this please

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2130/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3893/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2152/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3895/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2154/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2156/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3897/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3899/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2158/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2163/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3904/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2164/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3905/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3906/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2165/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2167/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3908/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3919/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2178/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3922/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2182/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2184/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3925/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2187/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3928/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2195/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3936/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2205/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3945/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2217/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3957/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2222/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3962/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3966/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2226/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2227/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3967/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3968/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2229/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3980/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2240/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/4020/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2282/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2287/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/4026/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/4045/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2307/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/4047/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2309/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/4050/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2312/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/4054/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2316/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/4064/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2325/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/4075/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2335/


test_classification

Written file C:\Users\donghok\Desktop\dronet_model\rpg_public_dronet-master2\dronet_model\constant_regression.json
Written file C:\Users\donghok\Desktop\dronet_model\rpg_public_dronet-master2\dronet_model\predicted_and_real_steerings.json
Average accuracy =  0.9530456852791879
Precision =  0.8951841359773371
Recall =  0.8951841359773371
F1-score =  0.8951841359773371
Written file C:\Users\donghok\Desktop\dronet_model\rpg_public_dronet-master2\dronet_model\test_classification.json
Average accuracy =  0.5253807106598984
Precision =  0.2348993288590604
Recall =  0.2348993288590604
F1-score =  0.31876138433515483
Written file C:\Users\donghok\Desktop\dronet_model\rpg_public_dronet-master2\dronet_model\random_classification.json
Written file C:\Users\donghok\Desktop\dronet_model\rpg_public_dronet-master2\dronet_model\predicted_and_real_labels.json
test classification is 0.5. What is the meaning. I mean real_steering looks fine.
The collision is 0.5?

This is the result when using a random classifier for collision that, as you can expect, gives a 0.5 accuracy for binary classification!


JBMC tool

Results of a run using JPF, JayHorn and JBMC can be found here:~
https://pschrammel.bitbucket.io/schrammel-it/research/sv-comp-java-2018/
The benchmarks are in this PR: https://github.com/sosy-lab/sv-benchmarks/pull/565
The tool wrapper that enables using this is in this PR: https://github.com/sosy-lab/benchexec/pull/310

Nice to see that this seems to be working, but note that accepting this PR here means that these tools would be submitted to SV-COMP, and IIRC this is not the case for JPF and JayHorn, right?

Merged .set files and updated to sv-comp19

note that accepting this PR here means that these tools would be submitted to SV-COMP, and IIRC this is not the case for JPF and JayHorn, right?

The SV-COMP executions are triggered from the registration via the Google forms.
But still, this repo should not get cluttered. For reproducibility, it might be a good idea to collect benchmark definitions for tools that do not participate. I merged the other PRs as well.


Existing branch handling

Scenarios:

Suppose you're on a branch some-branch on the parent repo
You run wiby test
One of the dependent repos already has a branch called wiby-some-branch
a) It could be that you already ran wiby test and did not wiby clean afterwards (most common)
b) It could be that whoever was testing, wanted to make additional changes on the branch to get the tests to pass with the linked parent
c) It could be that it exists, because multiple dependencies are being tested

Thinking out loud:

In cases (b) and (c) we probably need to link the parent into package.json and push a commit into an existing branch; if the parent is already linked, then we probably want to push an empty commit (git commit -m "This is a blank commit" --allow-empty) to re-trigger the builds.
In case (a), we probably want to delete the branch, recreate it from HEAD and link the parent again.

The problem here is that we don't know if we're dealing with (a) or (b)/(c) - in case of (b)/(c) we want to keep all changes
The simple approach would be to not rebase, however that may mean that wiby test is running against outdated code (i.e. it no longer answers the question "will I break you"...)
Maybe the right answer is to always attempt to update the existing branch with master, before pushing a new commit? Can that be done via the API? We could then notify the user about the conflicts, if any, via wiby results?

Related issues:

https://github.com/pkgjs/wiby/issues/54
https://github.com/pkgjs/wiby/issues/78

Thank for thinking of these cases. Initially due to looking at this at the end of the day I did not understand the issues. But I think you have explained them. My turn to think aloud.
Essentially the wiby-some-branch may exist and there are different reasons to why it could be preexist. But these come down to 2 use cases ( a or b/c).
As a thought experiment I tried to rationalize methods of determining what the two cases are or avoiding having this situation.
avoid this situation
If the branch names where unique to a particular run of wiby wiby-branch-name-unique-id then the use cases would be known and the means to address them would be understood. However that would mean keeping track of the unique branch names raised locally. So that would make things complicated at a stage we don't want them to be complicated further.
Place a well known comment in the PR ( if one exists ) before we attempt to clean it. If as in the raise draft PR we check to see if a comment from clean was added.
accept the situation
If we accept that we cannot know what use case caused the branch to exist we can ask the user. This would require the user to understand things and would mean that wiby would essentially have to scan the repos for these situations before asking the question of the user.
Hope my thinking out load helps with this conversation.

OK, so after discussing this in PM WG meeting, here's my current thinking:

If the target branch exists - we should re-use that target branch
If the target branch already has the parent linked, we should push an empty commit to re-trigger any associated actions
If the target branch exists, the dependent needs to use PRs, but the PR does not exist - we should open a new PR after pushing the commit
If the target branch exists, and already has a PR open - we don't need to do anything (i.e. things should get automatically triggered due to a new commit)

Going forward:

If the target branch is not up to date with the default branch, we should let the user know when they request a wiby result (new feature)

The above applies to wiby-[branch name] when it is not up to date with its corresponding [branch name], if one exists - not just the default branches

We could also build a new command wiby rebase (naming TBD - we probably don't want to do an actual git rebase), which would make sure that the target branches are up to date with their corresponding default branches wherever possible

:tada: This issue has been resolved in version 0.9.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Custume log calculation

How i can calculate the logs . i use foreach any idea?

My fiend,
I really don't understand what you asking for. Can you describe exactly
what you want to do?
Best regards,
Cobis
El 07/04/2016 08:15, "dennist12"<EMAIL_ADDRESS>escribió:

How i can calculate the logs . i use foreach any idea?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/cobisja/tad-php/issues/12

[image: image.png]
how get the time interval of every logs?
21:21:16 and 21:23:52 - 2 mins and so on.
On Thu, Apr 7, 2016 at 11:30 PM Cobis<EMAIL_ADDRESS>wrote:

My fiend,
I really don't understand what you asking for. Can you describe exactly
what you want to do?
Best regards,
Cobis
El 07/04/2016 08:15, "dennist12"<EMAIL_ADDRESS>escribió:

How i can calculate the logs . i use foreach any idea?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/cobisja/tad-php/issues/12

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/cobisja/tad-php/issues/12#issuecomment-206953749

Hi my friend,
Well what you're asking for cannot be done through TAD-PHP. However, if you
want to do some dates calculations taking the timestamp returned by TAD I
suggest to use an excellent library called Carbon (
https://github.com/briannesbitt/Carbon). This library is intended to deal
with all dates calculations you might need offering you a lot of very
useful methods.
Best regards,
Cobis
[image: image.png]
how get the time interval of every logs?
21:21:16 and 21:23:52 - 2 mins and so on.
On Thu, Apr 7, 2016 at 11:30 PM Cobis<EMAIL_ADDRESS>wrote:

My fiend,
I really don't understand what you asking for. Can you describe exactly
what you want to do?
Best regards,
Cobis
El 07/04/2016 08:15, "dennist12"<EMAIL_ADDRESS>escribió:

How i can calculate the logs . i use foreach any idea?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/cobisja/tad-php/issues/12

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/cobisja/tad-php/issues/12#issuecomment-206953749

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/cobisja/tad-php/issues/12#issuecomment-207092831


Please confirm these before moving forward

[X] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
[X] I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue
Installation issue.
Brief description of your issue
As reported on Twitter, OpenJS.NodeJS should most likely be split into Major and Minor versions like other runtimes.
Steps to reproduce
winget upgrade --all with an earlier minor version of NodeJS installed.
Actual behavior
NodeJS is upgraded to the latest version.
Expected behavior
NodeJS should only be upgraded within the same minor version to the latest patch version.
Environment
Windows Package Manager (Preview) v1.4.2161-preview
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.25236.1001
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.19.2161.0

Screenshots and Logs
No response

@denelon - should we move versions under LTS too?

Yes.

You can do it, it's just less common (changes between major Node versions are usually much less breaking than in other languages). nvm is a tool commonly used for switching between Node versions.
With that being said, I agree that this should be solved through package pinning (although, I don't know if we have a solution to pinning multiple versions of a package at once yet, which would be required for side-by-side as you mention).

If we split the package into publisher.package.version and minor versions are installed side-by-side, each "package" could be pinned.

The minor versions can't be installed side-by-side, though. If you installed NodeJS 20 when you have NodeJS 19, for example, it would overwrite NodeJS 19.

Why not just set it to RequireExplicitUpgrade?


refactor: removing L1 block number from L2 block

Fixes #5274
A copy of https://github.com/AztecProtocol/aztec-packages/pull/5275 which got messed up when I tried to reorder branches in a stack.

Benchmark results
Metrics with a significant change:

note_trial_decrypting_time_in_ms (32): 120 (+78%)
note_trial_decrypting_time_in_ms (64): 113 (+142%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit 30908eb0 and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
64 txs

l1_rollup_calldata_size_in_bytes
5,668
18,820
36,356

l1_rollup_calldata_gas
66,316
238,672
469,580

l1_rollup_execution_gas
647,414
929,030
1,305,760

l2_block_processing_time_in_ms
1,352 (+2%)
4,859 (+1%)
9,350

note_successful_decrypting_time_in_ms
178 (-9%)
505 (-9%)
979 (-4%)

note_trial_decrypting_time_in_ms
81.4 (-21%)
:warning: 120 (+78%)
:warning: 113 (+142%)

l2_block_building_time_in_ms
18,321
68,874 (-1%)
136,816 (-4%)

l2_block_rollup_simulation_time_in_ms
8,116 (-1%)
28,750
56,573 (-6%)

l2_block_public_tx_process_time_in_ms
10,183
40,066 (-1%)
80,140 (-3%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
13,799
27,862 (+2%)

note_history_successful_decrypting_time_in_ms
1,254 (-1%)
2,486 (+1%)

note_history_trial_decrypting_time_in_ms
99.6 (+4%)
205 (+36%)

node_database_size_in_bytes
18,677,840 (-2%)
35,012,688 (-2%)

pxe_database_size_in_bytes
29,859
59,414

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
287 (-1%)
44,366
28,244

private-kernel-ordering
215
52,868
14,326

base-parity
1,883 (+3%)
128
311

base-rollup
717 (-1%)
165,787
925

root-parity
1,448 (-8%)
1,244
311

root-rollup
51.8 (-1%)
4,487
725

private-kernel-inner
646 (-1%)
73,771
28,244

public-kernel-app-logic
449
35,260
28,215

public-kernel-tail
174 (-1%)
40,926
28,215

merge-rollup
8.31
2,696
925

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
512 leaves
1024 leaves
2048 leaves
4096 leaves
32 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.0
16.1 (+1%)
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.8
31.6
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.585
0.497 (+1%)
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
45.8 (-2%)
72.7 (+1%)
230 (-1%)
445
884
1,732
N/A

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
96.0
159
543
1,055
2,079
4,127
N/A

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.470 (-2%)
0.448 (+1%)
0.421 (-1%)
0.417
0.419
0.414
N/A

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
53.8 (-1%)
107
337
663 (+1%)
1,315
2,610 (-1%)
N/A

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
104
207
691
1,363
2,707
5,395
N/A

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.479 (-1%)
0.481
0.458
0.457 (+1%)
0.455
0.453 (-1%)
N/A

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
61.5 (-1%)

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
109

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0.538 (-1%)

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes

tx_size_in_bytes
22,012

Transaction processing duration by data writes.

Metric
0 new note hashes
1 new note hashes

tx_pxe_processing_time_ms
3,224
1,756

Metric
0 public data writes
1 public data writes

tx_sequencer_processing_time_ms
11.1 (-8%)
1,250


Introduce some Map-usage in the AppOptions

This simplifies both checking if an entry exists and iteration of the entries, and will help reduce the size/scope of PR #18465.

/botio unittest

/botio integrationtest

Thank you for the patch!


Bug - Enum ArtifactType has no name defined for value 8

I'm getting the error "Enum ArtifactType has no name defined for value 8" when running the sample code for Text-to-Image.
stability_api = client.StabilityInference(
    key=os.environ['STABILITY_KEY'],
    verbose=True
)
answers = stability_api.generate(
    prompt="a humble house, photorealistic",
    steps=100,
    width=512,
    height=512,
    samples=4
)

for resp in answers:
    for artifact in resp.artifacts:
        if artifact.finish_reason == generation.FILTER:
            warnings.warn(
                "Your request activated the API's safety filters and could not be processed."
                "Please modify the prompt and try again.")
        if artifact.type == generation.ARTIFACT_IMAGE:
            img = Image.open(io.BytesIO(artifact.binary))
            img.save(str(artifact.seed)+ ".png")

The error appears when trying to get artifacts at for artifact in resp.artifacts:.
for resp in answers performs the loop just fine.
Although no images is returned, the credits are still consumed.

Facing the same issue here on 0.2.7, but an update to the latest version 0.3.0 fixed this error.

Facing the same issue here on 0.2.7, but an update to the latest version 0.3.0 fixed this error.

Thanks for bringing that up. That solved. I noticed stability-sdk version on Poetry was locked.

+1 agree... should have been in the release notes


addListener not working

The addListener is not working, here is my code:
        branch.init(settings.branchIoKey);
        branch.addListener('didShowBanner', () => {
            track('banner.branch.displayed');
        });
        branch.addListener('didDeepviewCTA', () => {
            track('banner.branch.clicked');
        });
        branch.banner({ showAndroid: true, showDesktop: false, showiOS: false, showmobileSticky: true });

I even tried to use addListener with a function to log all events, and I'm not getting any events :(

As a comment, this was working two weeks ago.

@francorisso sorry for the delay in our responding. For integration related issues<EMAIL_ADDRESS>is the fastest way to contact our team.
In any case, I did some testing and here's what I found:

A listener for the didShowBanner event does trigger correctly (see test plan below).
didDeepviewCTA is not an event that is published in the WebSDK
There is currently an outstanding bug when trying to listen for all events. I'm going to work on this shortly.

Test plan for 1:

Navigate to https://cdn.branch.io/example.html in Chrome
Once you've landed on the page, open up developer console and type in:
var listener = function(event) { console.log(event); }
then hit return
Keep developer console open and type in:
branch.addListener('didShowBanner', listener);
hit return again
Finally, push the ".banner" button on the page and you'll see the didShowBanner event trigger

I've tried the test above with:
branch.addListener('didShowBanner', (event) => {
            console.log('hello');
        });

and it works fine as well. Is this still an issue?

@francorisso previously there was confusion on my end with didDeepviewCTA around whether it worked/or was supported. I just tested it using:
branch.addListener('didDeepviewCTA', (event) => {
   alert('hello again');
});

in Chrome using a different test page with a Deepview. Once I called, branch.deepviewCta(); from my browser, the alert was thrown correctly. Turns out this is working as well.


Perf: only read files from disk once

Right now, slyp reads every file 3 times:

hashing
fixing
linting

It's just an artifact of the still-evolving app architecture.
This should only happen once, obviously.

This actually got done, but not closed.


Native macOS Universal AutoFill leaving the 'password' field blank on some websites

Bug Description
Native macOS (Universal) AutoFill leaving the 'password' field blank despite having everything correctly configured.
While it works fine on some other websites, there are still many where the AutoFill is broken.
I understand some websites don't have the optimal HTML forms that would be easily recognized by password managers, but this is something else, because it works with the Apple Passwords app.
Steps To Reproduce

Create an entry in Strongbox for e.g. https://jack-wolfskin.de with an username/password combination for testing
Turn on AutoFill for Strongbox and Strongbox only (both in System Settings on macOS and Strongbox > Database)
Make sure AutoFill 'User names and passwords' is enabled in Safari.
Go to e.g. https://jack-wolfskin.de and try to AutoFill username and password

Expected Behavior
Expected would be as in Apple Passwords, if you do the following:

Create an entry in Apple Passwords for e.g. https://jack-wolfskin.de with an username/password combination for testing
Turn on AutoFill for Passwords and Passwords only in System Settings
Make sure AutoFill 'User names and passwords' is enabled in Safari.
Go to e.g. https://jack-wolfskin.de and try to AutoFill username and password

Screenshots
https://github.com/user-attachments/assets/961186f4-0081-4a53-abe1-f81add432bee
Environment

Strongbox Version: com.markmcguill.strongbox [1.60.23 (5648)-P]
OS: MacOS Version 15.0.1 (Build 24A348)

Hi,
You've posted this issue to the wrong project. I assume you're referring to the strongbox-password-safe/Strongbox project. I'm therefore closing this bug report.
Kind regards,
Martin


broken link in codetour

I am doing the codetour for "hello, world", and on page #1 the link to hello.qnt seems broken.

All relative markdown links are broken in CodeTour, e.g., also the images:

@konnov I think #695 didn't actually update the tour. Run make? 🙃

This seems to be fixed long time ago

This seems to be fixed long time ago

Not true, both the link reported by Josef and the image are broken (opening VSCode inside ./tutorials).

This is a zombie issue, resurrecting two times :)


Initial suggestions for plugin release

Thanks @ellisvalentiner for creating another awesome plugin. Great to see some amazing work around the weatherkit APIs.
The basic structure and results look good so far. While using the plugin, we did come up with a few suggestions based on our best practices (You can check them out here - https://steampipe.io/docs/develop/plugin-release-checklist#table-documentation):

Could you please create a CHANGELOG file so that it will be easier to track the releases? A standard md file which includes the initial tables should suffice. You could use https://github.com/turbot/steampipe-plugin-vercel/blob/main/CHANGELOG.md#v001-2022-07-19 for reference.
The slack channel in docs/index.md (https://github.com/ellisvalentiner/steampipe-plugin-weatherkit/blob/main/docs/index.md#get-involved) should be updated to use the latest link. You can use https://github.com/turbot/steampipe-plugin-aws/blob/main/docs/index.md#get-involved as a reference.
The configuration section in the docs/index.md file should be a replica of the .spc file. Currently, it is missing information on the token argument.
Can the config arguments be set in the form of environment variables? If yes i think we need to add a provision to handle them.
Does the API support pagination, backoff and retry mechanism? Please refer https://steampipe.io/docs/develop/plugin-release-checklist#data-ingestion for more information. It might not since the API is still in beta state. We could add them back later when the API starts supporting them.
Without setting the config arguments when I run the queries, I had the following observation -

> select
    as_of,
    temperature,
    condition_code
from weatherkit_current_weather
where latitude = '42.281' and longitude = '-83.743';
Error: rpc error: code = Internal desc = hydrate function getCurrentWeather failed with panic key_id (SQLSTATE HV000)

> select *
from weatherkit_availability
where latitude='42.281' and longitude='-83.743';
Error: rpc error: code = Internal desc = hydrate function listAvailability failed with panic key_id (SQLSTATE HV000)

Could we update the error message to be more helpful? You could refer https://github.com/turbot/steampipe-plugin-vercel/blob/main/vercel/utils.go#L37 for more information.

For the table doc, docs/index.md, and README, could we update the query format to use newlines? It will enhance the readability. You can use https://github.com/turbot/steampipe-plugin-aws/blob/main/docs/tables/aws_s3_bucket.md as a reference.

I had a great time playing around with the tables. The results look great 👍 .
Please let us know in case you have questions about the above-mentioned suggestions. Looking forward to releasing it to the hub 😄 .

@misraved I believe I've addressed the issues you mentioned, would you mind giving this another look?

Thanks @ellisvalentiner, I will give it another pass, believe this should be ready for release 😄.

@ellisvalentiner apologies for the delay, I reviewed the plugin, and all the issues have been addressed 👍 .
Could you please add a small note in docs/index.md pertaining to the usage of environment variables? You can refer https://github.com/turbot/steampipe-plugin-aws/blob/main/docs/index.md#credentials-from-environment-variables for more information.
Apart from that, the plugin is ready for release. Great work 👍 .

@misraved Done!

Thanks @ellisvalentiner for the quick turnaround 🚀 .


WebSocket connection to 'ws: // localhost: 8015 / db' failed

I'm testing linux centos server and this error appeared in my browser:
WebSocket connection to 'ws: // localhost: 8015 / db' failed: Error in connection establishment: net :: ERR_CONNECTION_REFUSED
Unhandled rejection ReqlDriverError: Could not connect to localhost: 8015.
I have already released ports 8080, 8015 and 28015 in my csf firewall
Could anyone help?
Note: I'm using npm install --unsafe-perm to solve a problem with webpack. Is it recommended?
WARN optional SKIPPING OPTIONAL DEPENDENCY
and
WARN notsup SKIPPING OPTIONAL DEPENDENCY
They also appear, but I ignore them.

I forgot to swap localhost for my host. thanks guys.


Flyway + Spring boot  + DbMigrate debug log does not work

Which version and edition of Flyway are you using?
Flyway Pro 6.0.8
If this is not the latest version, can you reproduce the issue with the latest one as well?
(Many bugs are fixed in newer releases and upgrading will often resolve the issue)
NA
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Java API
Which database are you using (type & version)?
Oracle 12C
Which operating system are you using?
Windows 10
What did you do?
(Please include the content causing the issue, any relevant configuration settings, the SQL statement that failed (if relevant) and the command you ran.)
I am using Flyway + SpringBoot and trying to enable debug level logging for Migrate command alone. Configured below in application.properties file, but this is not printing the debug logs
logging.level.org.flywaydb.core.internal.command.DbMigrate=DEBUG
This WORKS, but am just interested in Migrate and undo logs->logging.level.org.flywaydb.core.internal=DEBUG
NOT working->logging.level.org.flywaydb.core.internal.command.DbMigrate=DEBUG
NOT working-> logging.level.org.flywaydb.core.internal.command=DEBUG
What did you expect to see?
DbMigrate debug level log messages.
What did you see instead?
Just seeing only Info level log messages.

The Spring Boot Flyway integration is developed by the Spring Boot team, so it's best to report this directly to them. It might be that Flyway needs to change in some way to support this change, in which case feel free to reopen this with more details.


Compile error with M5Stack Capsule RTC with BM8563

Greetings!  I am attempting to compile a program with the RTC; I've been able to compile examples with the internal SD card and IMU, but not the example for the RTC, gives the following error:
C:\Users\dirk6\AppData\Local\Temp.arduinoIDE-unsaved2024413-17884-3ssctb.stzp9\Unit_RTC_M5Core2\Unit_RTC_M5Core2.ino:17:10: fatal error: M5_BM8563.h: No such file or directory
#include "M5_BM8563.h"
^~~~~~~~~~~~~
compilation terminated.
exit status 1
Compilation error: M5_BM8563.h: No such file or directory
I did install the only library I could find named M5Unit-RTC, but that didn't help....
I tried using the line from other examples:
#include "Unit_RTC.h"
but got the following compilation error:
exit status 1
Compilation error: 'BM8563' does not name a type; did you mean 'BIT53'?
Sorry I'm a new guy; can anyone advise me as to what I should do?
Thank you

Are you using rtc in the m5 capsule examples? If correct? You follow this

Arduino ide --> Tools -->Board --> Boards Manager --> M5stack Arduino --> M5Capsule
This example requires it
/*

@Hardwares: M5Capsule
@Platform Version: Arduino M5Stack Board Manager v2.0.7
@Dependent Library:
M5GFX: https://github.com/m5stack/M5GFX
M5Unified: https://github.com/m5stack/M5Unified
*/

Select rtc examples File --> Examples --> M5Capsule --> rtc
Please tell me which examples are you using?

Thank you for your kind reply, Pandian!  I did get it working! (o: so all
is good!
but if you are interested, below I posted what I had to do (several things)
to get it working;
Yes, I did have the M5Stack Capsule board selected.....
[image: image.png]
However, I was not able to locate BM8563 RTC examples that are specific to
the M5 Capsule.......There is a group of examples labelled "Examples for M5
Capsule" (please see screen cap below) but I was unable to find any RTC
examples there.....
[image: image.png]
In attempting to use your recommendation, I was unable to find the exact
location of examples for M5Capsule (that is, I don't see a specific
category for the M5Capsule)......
[image: image.png]
I noticed the Board Manager I have installed is version 2.1.1, so I
installed 2.0.7 (as you recommend), hoping examples I need are included.....
In the Examples I2C_BM8563_RTC section I found an RTC example called
BM8563_Set But it appears 2.0.7 doesn't appear to have the M5Capsule board
profile, because I get the following compilation error:
Invalid FQBN: board m5stack:esp32:m5stack_capsule not found
Compilation error: Invalid FQBN: board m5stack:esp32:m5stack_capsule not
found
So I reloaded Board Manager 2.1.1 and that fixed that problem.
I also discovered a generic I2C_BM8563_RTC example folder.  I loaded those
SET (time) and GET (time).  Those examples were for other boards but worked
after setting the correct SDA and SCL I/O for the M5 Capsule... all good!
Thank you!
Dirk
On Thu, May 23, 2024 at 7:28 PM Pandian Nano @.***>
wrote:

Are you using rtc in the m5 capsule examples? If correct? You follow this

Arduino ide --> Tools -->Board --> Boards Manager --> M5stack
Arduino --> M5Capsule

This example requires it

/*

@hardwares https://github.com/hardwares: M5Capsule

@platform https://github.com/platform Version: Arduino M5Stack
Board Manager v2.0.7

@dependent https://github.com/dependent Library:

M5GFX: https://github.com/m5stack/M5GFX

M5Unified: https://github.com/m5stack/M5Unified
*/

Select rtc examples File --> Examples --> M5Capsule --> rtc

Please tell me which examples are you using?

image.png (view on web)
https://github.com/m5stack/M5Unit-RTC/assets/6286904/1957e01b-a7e4-4603-96ff-9bb1f0602ef5
—
Reply to this email directly, view it on GitHub
https://github.com/m5stack/M5Unit-RTC/issues/3#issuecomment-2128382106,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACW7MHER4EV4WFQLOVCCISLZD2QVJAVCNFSM6AAAAABHW63ZMCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRYGM4DEMJQGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Oh! didn't see your latest comment till now.....
It also works with
#include "I2C_BM8563.h"
Thx! (o:


fix: Call NOT_CONTANS in notContains method

I hereby confirm that I followed the code guidelines found at engineering guidelines
Affected Components

[x] CLI
[ ] Create CLI
[ ] Test
[ ] Docs
[ ] Examples
[ ] Other

Resolves #[306]

Sorry, it looks like we have an issue running our E2E tests from forked repositories. I'll try to get a colleague with admin access to merge this PR soon.


Possible corrections to CheckIPO.cmake script

add a warning when building for armv7 instead disable silently
better condition expression syntax

I wonder if it could be useful also to rename ENABLE_LTO with a SFIZZ_ prefix as all other options.

Regarding the armv7 special case:
Perhaps it's best to define some platform-specific defaults for our options, and LTO is one of the candidates for that.
eg. it's ARMv7, LTO is default to OFF, otherwise ON
Then it's not needed to force it off, even in case the user explicitly requests it.
The same could apply for instance, to building JACK: set it default to ON on Linux, and OFF on other platform.

I like jpcima's idea, although I do agree that the silent ignore is not good.
IIRC ENABLE_LTO is not really a sfizz specific option, it's a cmake one.

ENABLE_LTO is a custom option defined in the main CMakeLists.txt file, used as a flag in cmake/CheckIPO.cmake.
IIRC at the time we wrote that cmake module, the idea was to keep it generic for any project, but since it has also a SFIZZ_ENABLE_LTO_IF_NEEDED function defined in it we could rename that flag too (if not the function removing the SFIZZ bit).

Ok I thought not. In this case yes a size prefix would be better !
Dec 26, 2020 15:16:34 redtide<EMAIL_ADDRESS>
ENABLE_LTO is a custom option defined in the main CMakeLists.txt file, used as a flag in cmake/CheckIPO.cmake.
IIRC at the time we wrote that cmake module, the idea was to keep it generic for any project, but since it has also a SFIZZ_ENABLE_LTO_IF_NEEDED function defined in it we could rename that flag too (if not the function removing the SFIZZ bit).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub[https://github.com/sfztools/sfizz/pull/588#issuecomment-751360453], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ADUFWQJ74ZWUCA4SSNEYPELSWXV2TANCNFSM4VDO4CPA].
[data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAABHNCSVQICAgIfAhkiAAAAB9JREFUaIHtwQEBAAAAgiD/r25IQAEAAAAAAAAAAC8GJDAAAY7rwGcAAAAASUVORK5CYII=###24x24:true###][Tracking image][https://github.com/notifications/beacon/ADUFWQPMRURVHHD3IE7RH53SWXV2TA5CNFSM4VDO4CPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFTENTRI.gif]


🐞 dagger.io/dagger v0.11.7 is not available through dagger.io

What is the issue?
I think your proxy was left out in the cold when you pushed the latest release to github
Dagger version
dagger v0.11.7
Steps to reproduce
go get<EMAIL_ADDRESS>=> dagger.io/dagger v0.11.6
Log output
❯ go get<EMAIL_ADDRESS>go: downloading dagger.io/dagger v0.11.7
go<EMAIL_ADDRESS>requires<EMAIL_ADDRESS>parsing go.mod:
        module declares its path as: github.com/dagger/dagger
                but was required as: dagger.io/dagger

No response

<EMAIL_ADDRESS><EMAIL_ADDRESS>seems github.com/dagger/dagger is released as dagger.io/dagger

Investigating now.
Looks like https://github.com/dagger/dagger-go-sdk, the source of truth for this is wrong.

@jedevc it still seems broken:
❯ go get<EMAIL_ADDRESS>go<EMAIL_ADDRESS>requires<EMAIL_ADDRESS>parsing go.mod:
        module declares its path as: github.com/dagger/dagger
                but was required as: dagger.io/dagger

Yeah, sorry we still need to repush the v0.11.7 tag - @gerhard is looking into it.

Maybe tag a new version instead? Go is quite sensitive to changing tags.

The Go SDK has now been re-tagged: https://github.com/dagger/dagger-go-sdk/releases/tag/v0.11.7
This is the expected version & directory structure: https://github.com/dagger/dagger-go-sdk/tree/443305dc487d22254940e3029bd42d1b45de2dcc

And this is the expected go.sum: https://github.com/dagger/dagger-go-sdk/blob/443305dc487d22254940e3029bd42d1b45de2dcc/go.mod
With all that in place, I am still getting the following error - as captured in this issue:
❯ go get<EMAIL_ADDRESS>go<EMAIL_ADDRESS>requires<EMAIL_ADDRESS>parsing go.mod:
	module declares its path as: github.com/dagger/dagger
	        but was required as: dagger.io/dagger

I think this is happening because<EMAIL_ADDRESS>is not in the right shape. Still investigating.

dagger/dagger-go-sdk is a "mirror" of github.com/dagger/dagger/sdk/go.
The magic happens here: https://github.com/dagger/dagger/blob/main/ci/sdk_go.go#L67-L100
Can't check right away but maybe there have been recent modifications?

If we start a module from scratch, clean local mod cache (to reduce potential noise) and get<EMAIL_ADDRESS>without going through the proxy (GOPROXY=direct), we can see that the issue is due to a checksum missmatch. Given how the proxy works, it seems that the v0.11.7 will remain broken until it is cleared from sum.golang.org (which I'm not sure if its possible to do). You should be able to repro this with the following steps:
$ mkdir dagger-v0-11-7 && cd dagger-v0-11-7
$ go mod init testing
$ go clean -modcache
$ export GOPROXY=direct
$ go get -u<EMAIL_ADDRESS>go: downloading dagger.io/dagger v0.11.7
go<EMAIL_ADDRESS>verifying module: checksum mismatch
        downloaded: h1:5KwB14CNJ1WdW5MEKZwsIrepaQcXKmCAQEQNJgy5f5c=
        sum.golang.org: h1:xXa7dgyM5xGZlWC/uc9mlRIH2XrTZenemTM/2vfibb4=

SECURITY ERROR
This download does NOT match the one reported by the checksum server.
The bits may have been replaced on the origin server, or an attacker may
have intercepted the download attempt.

For more information, see 'go help module-auth'.

We had to update (force push) the v0.11.7 tag due to:

https://github.com/dagger/dagger/pull/7631

Considering that we discovered a few edge cases in our CI that we want to dig into, it sounds reasonable to follow-up with v0.11.8 and a few of these fixes. FTR: https://discord.com/channels/707636530424053791/1248289310105669734/1250122548633669663

go get<EMAIL_ADDRESS>is now available & it will work exactly as v0.11.7 would have.
We have hit a different problem with v0.11.8-rc.1 as captured here:

https://github.com/dagger/dagger/pull/7642#issuecomment-2163684518

We will need to release another RC - most probably rc.3 - so that the release notes line up & everything looks right, but we ran out of time today.

Thank you for reporting this @kjuulh 💪
<EMAIL_ADDRESS>