Python extension does not load, stuck at Python extension loading

unfortunately this issue has not been completely fixed: I just updated to the latest vscode: Version 1.33.1 (1.33.1) and the "Python extension loading" has been stuck for the last 3 hours, and I am staring at my source code.
None of the provided solutions works.
Originally posted by @a2975667 in https://github.com/microsoft/vscode-python/issues/3967#issuecomment-480054041

So I can help you, please could you fill in the issue template with the missing information.

I also have the same problem but only in directories with a lot of files and subdirectories. If I create a new workspace with a few files, then the extension loads fine but with a large number of files  (most of which are not .py files)  and subdirectories the extension takes a very long time to load.
I am using VScode 1.33.1
Python extension 2019.4.12954
Ubuntu 16.04.6
Python 3.7
Miniconda3 virtual environnments
Log
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:3264 [Extension Host] debugger listening on port 36465
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] (node:6589) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
t.log @ /usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Display locator refreshing progress, Class name = p, , Return Value: undefined
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Notify locators are locating, Class name = p, , Return Value: undefined
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Checking whether locactors have completed locating, Class name = p, , Return Value: false
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Detected refreshing of Interpreters, Class name = p, Arg 1: {}, Return Value: undefined
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Display locator refreshing progress, Class name = p, , Return Value: undefined
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Notify locators are locating, Class name = p, , Return Value: undefined
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Checking whether locactors have completed locating, Class name = p, , Return Value: false
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Detected refreshing of Interpreters, Class name = p, Arg 1: {}, Return Value: undefined
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Display locator refreshing progress, Class name = p, , Return Value: undefined
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Notify locators are locating, Class name = p, , Return Value: undefined
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Checking whether locactors have completed locating, Class name = p, , Return Value: false
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Detected refreshing of Interpreters, Class name = p, Arg 1: {}, Return Value: undefined
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Display locator refreshing progress, Class name = p, , Return Value: undefined
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Notify locators are locating, Class name = p, , Return Value: undefined
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Checking whether locactors have completed locating, Class name = p, , Return Value: false
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Detected refreshing of Interpreters, Class name = p, Arg 1: {}, Return Value: undefined
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Create file systemwatcher with pattern */python
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Create file systemwatcher with pattern */*/python
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Display locator refreshing progress, Class name = p, , Return Value: undefined
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Notify locators are locating, Class name = p, , Return Value: undefined
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Checking whether locactors have completed locating, Class name = p, , Return Value: false
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Detected refreshing of Interpreters, Class name = p, Arg 1: {}, Return Value: undefined
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Display locator refreshing progress, Class name = p, , Return Value: undefined
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Notify locators are locating, Class name = p, , Return Value: undefined
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Checking whether locactors have completed locating, Class name = p, , Return Value: false
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Detected refreshing of Interpreters, Class name = p, Arg 1: {}, Return Value: undefined
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Display locator refreshing progress, Class name = p, , Return Value: undefined
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Notify locators are locating, Class name = p, , Return Value: undefined
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Checking whether locactors have completed locating, Class name = p, , Return Value: false
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Detected refreshing of Interpreters, Class name = p, Arg 1: {}, Return Value: undefined
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Register Intepreter Watcher, Class name = p, Arg 1: <Uri:/mnt/atlas/my_home/HIV-DRM-Hunter/scripts/data_utils.py>, Return Value: undefined
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Build the workspace interpreter watcher, Class name = h, Arg 1: <Uri:/mnt/atlas/my_home/HIV-DRM-Hunter/scripts/data_utils.py>, Return Value: <Return value cannot be serialized for logging>
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Rule = settings, result = runNextRule
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Executing next rule from settings
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Display locator refreshing progress, Class name = p, , Return Value: undefined
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Notify locators are locating, Class name = p, , Return Value: undefined
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Checking whether locactors have completed locating, Class name = p, , Return Value: false
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Detected refreshing of Interpreters, Class name = p, Arg 1: {}, Return Value: undefined
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Display locator refreshing progress, Class name = p, , Return Value: undefined
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Notify locators are locating, Class name = p, , Return Value: undefined
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Checking whether locactors have completed locating, Class name = p, , Return Value: false
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Detected refreshing of Interpreters, Class name = p, Arg 1: {}, Return Value: undefined
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Detection of Python Interpreter for Command python3.7 and args  failed
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Detection of Python Interpreter for Command python3.6 and args  failed
2/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Interpreters returned by PipEnvService are of count 0
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:235 [Extension Host] Python Extension: Interpreters returned by VirtualEnvService are of count 0
extensionHost.ts:215 Extension Host
extensionHost.ts:216 Debugger attached.

log.ts:167  WARN UNRESPONSIVE extension host, 'ms-python.python' took 100% of 5215.392ms, saved PROFILE here: '/tmp/exthost-6e84f6.cpuprofile' (2) [{…}, {…}]

@zlanderous
I'm sorry about this, however there's some good news.
We fixed a bug related to I/O and the fix is in our developer build.

Please could you download the developer build
Install this extension using the command Extensions: Install from VSIX
Select the above download VSIX
Reload VS Code
Note, installing this developer build is safe, as it has passed our CI and when a new version is released the new version will automatically get installed over this... I.e. you don't need to worry about uninstall this version.

Please let us know how the performance is after installing this new developer build.
If that doesn't work, then we'll address this as part of https://github.com/microsoft/vscode-python/issues/5613. We'll do more to ensure we can identify these bottlenecks and resolve this.

I have this issue as well, since installing the latest two releases of VS Code (currently 1.34.0). I have narrowed it down to: it occurs when opening a workspace that already has Python files open in it.
The workaround: Close all python editors > Command Pallet > Reload Window > Open a Python file and the extension loads correctly.
The projects I'm working with are not large at all.
I have tried the suggested developer build. It did not solve the issue.
[Extension Host] Python Extension: extension activation failed Error: Missing required @injectable annotation in: d.
	at l (/var/home/bdeeming/.vscode/extensions/ms-python.python-2019.5.15582-dev/out/client/extension.js:24:22015)
	at Object.module.exports.t.getDependencies (/var/home/bdeeming/.vscode/extensions/ms-python.python-2019.5.15582-dev/out/client/extension.js:24:23677)
	at /var/home/bdeeming/.vscode/extensions/ms-python.python-2019.5.15582-dev/out/client/extension.js:24:20708
	at Array.forEach (<anonymous>)
	at e (/var/home/bdeeming/.vscode/extensions/ms-python.python-2019.5.15582-dev/out/client/extension.js:24:20522)
	at Object.module.exports.t.plan (/var/home/bdeeming/.vscode/extensions/ms-python.python-2019.5.15582-dev/out/client/extension.js:24:20806)
	at module.exports.e._planAndResolve (/var/home/bdeeming/.vscode/extensions/ms-python.python-2019.5.15582-dev/out/client/extension.js:24:17690)
	at e.module.exports.e._get (/var/home/bdeeming/.vscode/extensions/ms-python.python-2019.5.15582-dev/out/client/extension.js:24:17599)
	at e.module.exports.e.get (/var/home/bdeeming/.vscode/extensions/ms-python.python-2019.5.15582-dev/out/client/extension.js:24:16290)
	at o.get (/var/home/bdeeming/.vscode/extensions/ms-python.python-2019.5.15582-dev/out/client/extension.js:83:687946)
	at /var/home/bdeeming/.vscode/extensions/ms-python.python-2019.5.15582-dev/out/client/extension.js:9:98534
	at /var/home/bdeeming/.vscode/extensions/ms-python.python-2019.5.15582-dev/out/client/extension.js:9:99297
	at module.exports.t.activate (/var/home/bdeeming/.vscode/extensions/ms-python.python-2019.5.15582-dev/out/client/extension.js:9:102021)
	at Function._callActivateOptional (/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:731:936)
	at Function._callActivate (/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:731:625)
	at define._doActivateExtension.Promise.all.then.e (/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:730:635)
t.log @ workbench.main.js:238
workbench.main.js:3855 Activating extension 'ms-python.python' failed: Missing required @injectable annotation in: d..
_logMessageInConsole @ workbench.main.js:3855

Thanks :-)

@DonJayamanne
I uninstalled the released Pyhthon extension before installing from the VSIX you provided, and reloaded VScode. The extensions loads after 25 mins so it's a little better.
I also noticed that I dont get the following warning anymore (like I did before):
log.ts:167  WARN UNRESPONSIVE extension host, 'ms-python.python' took 100% of 5215.392ms, saved PROFILE here: '/tmp/exthost-6e84f6.cpuprofile' (2) [{…}, {…}]

Also I failed to mention before, but the folder on which I am having problems is also network mounted, so it might slow IO a bit.

Closing as the issue has been resolved.
We have a separate issue that'll track further improvements #5613.

@DonJayamanne I have just downloaded the developer build again, removed my old install from the filesystem, then installed it. I still have this issue. 100% reproducible every time I open a workspace that has Python files already open in the editor view. If I close them and reload, it opens perfectly.
I'm running VS Code stable.
@zlanderous mentions a 25min load time. Wouldn't really call that fixed...
Please let me know if you would like any additional details, happy to assist any way I can.

Wouldn't really call that fixed...

Agreed, I've created a separate issue to track that.
I closed this issue as fixed as the message now disappears after some time.

I have just downloaded the developer build again, removed my old install from the filesystem, then installed it. I still have this issue. 100% reproducible every time I open a workspace that has Python files already open in the editor view. If I close them and reload, it opens perfectly.
I'm running VS Code stable.

I'm sorry to hear this is still the case & should have checked with you before closing this issue. However I believe you are experiencing a different issue, basically the extension isn't loading for you (as opposed to waiting indefinitely). Please could you open a separate issue with the error messages you are getting.

I guess my issue is more akin to the original problem description of this issue from @fxgx99, rather than that described by @zlanderous which does indeed seem to be different.
I've opened #5835.
Thanks.


os/gcron: add graceful shutdown support

I found that cron job do not support graceful shutdown, so I tried to implement it. If there are any problems, please point them out and I will fix them.

how to re run ci?

Have ran agian


Copy/Clone Closures

Implement Clone and Copy for closures where possible:
// Many closures can now be passed by-value to multiple functions:
fn call<F: FnOnce()>(f: F) { f() }
let hello = || println!("Hello, world!");
call(hello);
call(hello);

// Many `Iterator` combinators are now `Copy`/`Clone`:
let x = (1..100).map(|x| x * 5);
let _ = x.map(|x| x - 3); // moves `x` by `Copy`ing
let _ = x.chain(y); // moves `x` again
let _ = x.cycle(); // `.cycle()` is only possible when `Self: Clone`

// Closures which reference data mutably are not `Copy`/`Clone`:
let mut x = 0;
let incr_x = || x += 1;
call(incr_x);
call(incr_x); // ERROR: `incr_x` moved in the call above.

// `move` closures implement `Clone`/`Copy` if the values they capture
// implement `Clone`/`Copy`:
let mut x = 0;
let print_incr = move || { println!("{}", x); x += 1; };

fn call_three_times<F: FnMut()>(mut f: F) {
    for i in 0..3 {
        f();
    }
}

call_three_times(print_incr); // prints "0", "1", "2"
call_three_times(print_incr); // prints "0", "1", "2"

Rendered
Note: this RFC was made possible by the recent change to make Clone a lang item.

FWIW I keep seeing people refer to that change as "making Clone a lang item" but that is neither sufficient nor necessary (if you really wanted to you could just extract it from Copy's only supertrait).
What happened was automagic Clone::clone shimming in the compiler, like syntactic deriving but done on semantic type information and producing MIR, which makes it more powerful.

Does this include function types and function pointers as well?

@kennytm This RFC as written doesn't cover those, but I think those impls should definitely added. I think, though, that they probably belong in #2133 rather than this RFC.

@cramertj Can you update the description to refer to #2133 instead?

How will this interact with generators (#2033)?

@kennytm I'd like to think that generators would follow the same rules, but as no formal RFC for generators has been merged, I think that's outside the scope of this RFC.

This is a pretty straightfoward and very welcome RFC (eliminating a small but painful papercut). I'm going to go ahead and get the wheels turning toward FCP review:
@rfcbot fcp merge

I remember being sort of happy in the implementation that closures were just never Copy; I'm trying to think precisely why. But I guess if there's a big problem it will surface during the implementation.

@nikomatsakis Is it because it could be confusing to accidentally make a copy, resume the copy, and not see side effects on the original? (Same as iterators.) Maybe it makes sense to deliberately make generators not Copy, but they should definitely be Clone whenever possible.

@SimonSapin Hmm. I don't think that issue is specific to generators per se, it applies to any closure that owns mutable state. (After all, at a deep level at least, a generator is just a function.) Example:
fn main() {
    let mut i = 0;
    let mut get_value = move || -> u32 { i += 1; return i; };
    println!("{}", get_value()); // prints 1
    let mut get_value2 = get_value; // currently errors, but wouldn't with this RFC.
    println!("{}", get_value()); // prints 2
    println!("{}", get_value2()); // prints 1
}

I'm not sure if you consider surprising, or just expected behavior. It certainly behaves the same as any other value would, but it depends on how precise your "mental model" is for what state is owned by the closure versus being referenced from the surrounding stack frame, I suppose.

@SimonSapin I have an example of this in the RFC-- check out how call_three_times is used in the summary.

Is it because it could be confusing to accidentally make a copy, resume the copy, and not see side effects on the original? (Same as iterators.) Maybe it makes sense to deliberately make generators not Copy, but they should definitely be Clone whenever possible.

IIRC, this is basically the reason Range isn't Copy.
...ah, in fact, I think we're both remembering the same discussion.

Considering Range is not Copy, would it be feasible to implement Copy only when closure implements Fn (i.e. doesn't mutate anything). The table of possible autotraits would look like this.

Closure trait  Can automatically implement
Fn  Copy
FnMut  Clone
FnOnce  none

Also out of curiosity I consider the behaviour of call_three_times with &Cell instead of moved variable, and it seems reasonable to me even if a bit confusing - it returns 0, 1, 2, 3, 4, 5 - matching the behaviour of reference cell.
Here is a reference version to be called with call_three_times:
let cell = Cell::new(0);
let print_incr = &|| {
    println!("{}", cell.get());
    cell.set(cell.get() + 1);
};

And here is Copy version.
#![feature(fn_traits, unboxed_closures)]

use std::cell::Cell;

#[derive(Copy, Clone)]
struct Incrementer<'a> {
    cell: &'a Cell<i32>,
}

impl<'a> Fn<()> for Incrementer<'a> {
    extern "rust-call" fn call(&self, _args: ()) {
        let cell = self.cell;
        println!("{}", cell.get());
        cell.set(cell.get() + 1)
    }
}

fn main() {
    let cell = Cell::new(0);
    let incrementer = Incrementer { cell: &cell };

    fn call_three_times<F: FnMut()>(mut f: F) {
        for _ in 0..3 {
            f();
        }
    }

    call_three_times(incrementer);
    call_three_times(incrementer);
}

// Noise needed for technical reasons
impl<'a> FnMut<()> for Incrementer<'a> {
    extern "rust-call" fn call_mut(&mut self, args: ()) {
        self.call(args)
    }
}

impl<'a> FnOnce<()> for Incrementer<'a> {
    type Output = ();
    extern "rust-call" fn call_once(self, args: ()) {
        self.call(args)
    }
}

I think I would propose separately feature-gating "Copy" and "Clone" on closures -- in particular, I don't think there is much objection to closures being clone, but it'd be interesting to see if copy closures cause any kinds of problems.
But really I think a lot of these concerns come back to the desire to have a kind of "Copy" lint that warns you when you are implicitly copying values that you may not want to implicitly copy. (Which could then be silenced by invoking clone() explicitly.) We've always planned to have it, but never done it.

This RFC has been merged! Tracking issue.

Forgive me if I'm just totally wrong here, but wouldn't this break boxed closures? I've had issues before with not being able to box a trait because it implemented Clone.

@dead10ck Do you have any code the reproduce the error? ("not being able to box a trait because it implemented Clone")

@dead10ck Clone isn't object safe itself, but it's fine to have a type that implements Clone and some object safe trait like Fn turn into a Fn trait object.

@kennytm yeah, e.g. https://play.rust-lang.org/?gist=cc5e61ee6a37a21dae1e145911bb620f&version=stable
@sfackler right, but if I'm understanding this RFC proposal, wouldn't it make Fn: Clone, which would make it object-unsafe?

@dead10ck Ok, the problem in your code is that Foo has a supertrait Clone. The proposal doesn't make Fn: Clone, but that some instances of Fn now implements Clone. There can still be non-Clone closures, like what OP demonstrated:
// Closures which reference data mutably are not `Copy`/`Clone`:
let mut x = 0;
let incr_x = || x += 1;
call(incr_x);
call(incr_x); // ERROR: `incr_x` moved in the call above.

@kennytm I see, so it's not a blanket impl; but what about the cases that do : Clone? The ones from this case, for example, couldn't be boxed, right? And consequently, we wouldn't be able to return them from a function.
// Many `Iterator` combinators are now `Copy`/`Clone`:
let x = (1..100).map(|x| x * 5);
let _ = x.map(|x| x - 3); // moves `x` by `Copy`ing
let _ = x.chain(y); // moves `x` again
let _ = x.cycle(); // `.cycle()` is only possible when `Self: Clone`

@dead10ck It is fine to box and return it as Box<Iterator<Item=i32>>, because Iterator<Item=i32> itself is an object-safe trait. It doesn't matter if .cycle() relies on Clone. You can't return Box<Foo> because  Foo reait is not object-safe.

@kennytm I see, thank you! Sorry for the confusion. I'm still pretty inexperienced with Rust.


Make D3 Dynamic

Currently, the bubble radii are determined by a constant factor, the goal is to change the radii to be in terms of the window screen size and height. Along with this, the position of the force on the SVG component must be made dynamic according to the window size and not be at a fixed pixel (as it currently is)


wshowkeys: init at 2020-03-29

Motivation for this change
Only a draft for discoverability (not sure if that makes sense, but there where a few requests already and maybe someone would like to use it already).
I've tested it and it works but the software itself seems still alpha/beta quality and I don't think it's ready for Nixpkgs yet (it doesn't crash, but there are some rendering issues, the overlay doesn't disappear automatically after a few secondes, etc. and we should wait for a tagged (pre-)release anyway).
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

@primeos Was this closed because wshowkeys seem unmaintained?

Kinda. It should still be maintained (especially if you send Drew a patch) but there isn't any active development anymore. However, while it's probably feature complete it doesn't really seem that usable/polished yet. And without a tagged release (which I was hoping for after a few more patches) it doesn't really make much sense to merge this into Nixpkgs.
But it seems like e.g. Fedora packages it already: https://repology.org/project/wshowkeys/versions

I think this package is relevant to the wayland community and should be reopened.

Yeah, I'm not aware of any alternatives and it can clearly be useful. But a tagged release would be helpful, though not required.
I'll reopen this PR for now but it's probably a good idea to quickly ask Drew first if it's ok to package this already.

I propose adding myself to the list of maintainers if you wish.

That would be helpful as I didn't really need it myself so far.

I'll reopen this PR for now but it's probably a good idea to quickly ask Drew first if it's ok to package this already.

Ok, I finally asked Drew via IRC and he's fine with it :)
So this is now ready for a final review and merging (if there aren't any objections).

Result of nixpkgs-review pr 83687 1

1 package blacklisted:
- tests.nixos-functions.nixos-test

1 package built:
- wshowkeys


shouldnt this be <IP_ADDRESS>

The values provided in examples are sometimes wrong or irrelevant in real cases. Users should consult official AWS documentation if in doubt.


powered_effect is not calculated in the StudentsTTest

I'm a bit confused why the powered_effect is not calculated in the StudentsTTest but it's provided in ZTest.

The above is the data frame which I passed into both
stat_res_df = confidence.ZTest(
    stats_df,
    numerator_column='conversions',
    numerator_sum_squares_column=None,
    denominator_column='total',
    categorical_group_columns='variant_id',
    correction_method='bonferroni')

and
stat_res_df = confidence.StudentsTTest(
    stats_df,
    numerator_column='conversions',
    numerator_sum_squares_column=None,
    denominator_column='total',
    categorical_group_columns='variant_id',
    correction_method='bonferroni')

but when I called stat_res_df.difference(level_1='control', level_2='treatment') I found the result from z-test provides the powered_effect column as below

but it's missing from the t-test result. Another question, why is the required_sample_size missing? Is there a way to also provide the sample size estimation in the result? Thanks!

Since our sample sizes at Spotify are usually very large, it doesn't make a difference whether we use Z-tests or T-tests. Therefore we have mostly focused on the Z-test case and just not got around to implement everything for the other variants. It should be a simple thing to add though. The only difference should be in these lines, where we could use the corresponding t-distribution methods to get test statistics.
Time to make a first PR?  😉


[Eventing - Control Plane] Error Signalling Test Plan

Description

This issue describes the creation of a "Manual Testing Plan" for a portion of the Eventing Spec.
Below is a link to the Spec Sub-heading which this issue is referencing, alongside a template upon which you should base your PR.
Link to Spec: https://github.com/knative/specs/blob/main/specs/eventing/control-plane.md#error-signalling
Template: https://hackmd.io/D1S9NPaRTG2dcyFtdURSww?view
If you have any questions, please reach out in the #conformance channel on Slack

Acceptance Criteria

[ ] Contributing to the right place

GIVEN I am accepting the PR that closes this issue
WHEN I inspect the .md file
THEN I see it is being committed to the /test/test-plan/ folder in the specs repo

[ ]   Conformance to Template

GIVEN I am reviewing the submitted .md file
WHEN I compare it to the template linked above
THEN I see that the submitted .md conforms to the template

[ ]  Coverage of Spec

GIVEN I am reviewing the submitted .md file
WHEN I compare the .md file to the Error Signalling subheading in the spec
THEN all of the  "MUST" "MUST NOT" and "REQUIRED" sentences under the Error Signalling sub-heading are covered within the submitted .md file

[ ] Coverage of Tests

GIVEN I am running each of the tests in the submitted .md file
AND each test has a expected output
WHEN I am finished running the tests
THEN all of my tests pass (when compared to the expected output)
AND at least 2 reviewers feel it is properly covering all portions of the spec outlined at the top .md file

/assign


Fail build: gtest-1.7.0.zip unavailable

Hi,
I can't build the library because gtest is unavailable. Looking at tmp/fblualib-build.5RjQLZ/thpp/thpp/build.sh, I see this url gtest-1.7.0, which does not exist.
This is the ouput:
+ echo 'Installing TH++'
Installing TH++
+ echo

+ cd /tmp/fblualib-build.5RjQLZ/thpp/thpp
+ ./build.sh
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  1582  100  1582    0     0   8506      0 --:--:-- --:--:-- --:--:--  8551
Invalid gtest-1.7.0.zip file

Should have been fixed: https://github.com/facebook/thpp/issues/19

I'm using Ubuntu 14, and from install_all.sh, we can see that when using 14 or 15, variable "current" is not equal to 1. Because of that, the script install version 1.0 of thpp (see here https://github.com/facebook/fblualib/blob/master/install_all.sh#L97) which still has the reported issue. So, I set current to 1, and it installed "fine" (still had to manually install mstch https://github.com/no1msd/mstch though).

same issue with @ltrottier. why ubuntu 14 cannot use current=1?

same issue

Same issue here for Ubuntu 14. When attempting to override the current variable of the installation script, I get a different error (see here for details).

I followed this thread and it solved the problem.

the issue is due to the change of url of gtest-1.7.0.zip.
It can be solved by modify the build.sh:
#curl -JLO https://googletest.googlecode.com/files/gtest-1.7.0.zip
#if [[ $(sha1sum -b gtest-1.7.0.zip | cut -d' ' -f1) != \
'f85f6d2481e2c6c4a18539e391aa4ea8ab0394af' ]]; then
echo "Invalid gtest-1.7.0.zip file" >&2
exit 1
#fi
#unzip gtest-1.7.0.zip
rm -rf googletest-release-1.7.0 googletest-release-1.7.0.zip
curl -JLO https://github.com/google/googletest/archive/release-1.7.0.zip
mv googletest-release-1.7.0.zip gtest-1.7.0.zip
unzip gtest-1.7.0.zip
mv googletest-release-1.7.0 gtest-1.7.0


feat: View functions with static context enforcing

Closes https://github.com/AztecProtocol/aztec-packages/issues/6078
Introduces the #[aztec(view)] (open to different naming, @spalladino @rahul-kothari ) modifier to functions, that forces them to be executed in an static context. It also forces generation of a "static only" CallInterface for them, trying to spare users from making regular calls to them.
Need input from the AVM team (@dbanks12 @fcarreiro) on how to implement the concept in the AVMContext.
Also adds the ability to navigate from contract interfaces to their implementations via LSP!

Docs Preview
Hey there! 👋 You can check your preview at https://6643be0b3028a70e9333fedc--aztec-docs-dev.netlify.app

Benchmark results
Metrics with a significant change:

app_circuit_proving_time_in_ms (Test:emit_nullifier): 3,010 (+29%)
app_circuit_proving_time_in_ms (FPC:fee_entrypoint_public): 8,334 (-39%)
protocol_circuit_witness_generation_time_in_ms (public-kernel-setup): 342 (+16%)
protocol_circuit_witness_generation_time_in_ms (public-kernel-app-logic): 377 (+44%)
protocol_circuit_witness_generation_time_in_ms (public-kernel-teardown): 424 (+48%)
protocol_circuit_proving_time_in_ms (base-parity): 3,092 (-17%)
protocol_circuit_proving_time_in_ms (public-kernel-setup): 861 (+17%)
protocol_circuit_proving_time_in_ms (public-kernel-app-logic): 867 (+28%)
protocol_circuit_proving_time_in_ms (merge-rollup): 2,160 (+41%)

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.
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
740
740
740

l1_rollup_calldata_gas
6,680
6,680
6,680

l1_rollup_execution_gas
586,865
586,865
586,865

l2_block_processing_time_in_ms
1,592 (-1%)
5,997 (-1%)
12,002

l2_block_building_time_in_ms
26,591 (-1%)
104,300 (-1%)
207,488 (-1%)

l2_block_rollup_simulation_time_in_ms
26,413 (-1%)
103,670 (-1%)
206,146 (-1%)

l2_block_public_tx_process_time_in_ms
11,810 (-2%)
50,322 (-2%)
101,162 (-1%)

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
18,034 (+1%)
33,355

node_database_size_in_bytes
21,356,624
37,990,480

pxe_database_size_in_bytes
29,868
59,425

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

Circuit
protocol_circuit_simulation_time_in_ms
protocol_circuit_witness_generation_time_in_ms
protocol_circuit_proving_time_in_ms
protocol_circuit_input_size_in_bytes
protocol_circuit_output_size_in_bytes
protocol_circuit_proof_size_in_bytes
protocol_circuit_num_public_inputs
protocol_circuit_size_in_gates

private-kernel-init
140 (-1%)
2,624 (+2%)
22,338
19,398
46,118
62,400
1,883
1,048,576

private-kernel-inner
418
3,701 (+2%)
39,074 (+2%)
72,584
46,118
62,400
1,883
2,097,152

private-kernel-reset
673 (-1%)
4,205 (-4%)
45,660
219,992
46,118
62,400
1,883
2,097,152

private-kernel-tail
443
4,078 (-9%)
39,977 (+7%)
70,968
64,320
10,656
266
2,097,152

base-parity
8.11
623 (-2%)
:warning: 3,092 (-17%)
128
64.0
2,208
2.00
131,072

root-parity
51.2
139 (+9%)
38,582 (-4%)
27,064
64.0
2,720
18.0
2,097,152

base-rollup
823 (-1%)
4,782 (-13%)
43,713 (+1%)
111,126
925
3,104
30.0
2,097,152

root-rollup
72.3
168 (-1%)
8,294 (+1%)
11,454
789
3,424
40.0
524,288

public-kernel-app-logic
155
:warning: 377 (+44%)
:warning: 867 (+28%)
78,388
68,775
90,432
2,759
4,096

public-kernel-tail
532 (-1%)
587 (-11%)
863
184,419
7,723
10,144
250
512

public-kernel-setup
130 (-3%)
:warning: 342 (+16%)
:warning: 861 (+17%)
110,523
68,775
90,432
2,759
4,096

public-kernel-teardown
138 (+1%)
:warning: 424 (+48%)
985 (+15%)
114,418
68,775
90,432
2,759
4,096

merge-rollup
6.56 (-2%)
97.7 (+11%)
:warning: 2,160 (+41%)
2,696
925
3,104
30.0
65,536

private-kernel-tail-to-public
N/A
10,186 (+14%)
41,937 (-3%)
N/A
N/A
90,944
2,775
2,097,152

Stats on running time collected for app circuits

Function
app_circuit_proof_size_in_bytes
app_circuit_proving_time_in_ms
app_circuit_size_in_gates
app_circuit_num_public_inputs

SchnorrAccount:entrypoint
13,600
46,590 (+1%)
2,097,152
358

Test:emit_nullifier
13,600
:warning: 3,010 (+29%)
65,536
358

FPC:fee_entrypoint_public
13,600
:warning: 8,334 (-39%)
524,288
358

Token:transfer
13,600
41,089 (-7%)
2,097,152
358

FPC:fee_entrypoint_private
13,600
10,660 (-6%)
524,288
358

Token:unshield
13,600
34,016 (+1%)
2,097,152
358

SchnorrAccount:spend_private_authwit
13,600
2,597 (+2%)
131,072
358

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
13.0
21.3
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.7
31.8
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.766
0.657
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
61.8
97.5
313 (-1%)
608
1,182 (-1%)
2,355
N/A

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
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.635
0.604
0.569 (-1%)
0.569
0.561 (-1%)
0.563
N/A

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
73.9
142 (-1%)
450 (-1%)
892
1,762 (-1%)
3,525
N/A

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
106
208
692
1,363
2,707
5,395
N/A

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.646
0.643 (-1%)
0.614 (-1%)
0.615
0.613
0.615
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
80.5

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
108

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.709

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

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
68,450
668,031

Transaction size based on fee payment method
| Metric |  |
| - |  |
Transaction processing duration by data writes.

Metric
0 new note hashes
1 new note hashes
2 new note hashes

tx_pxe_processing_time_ms
28,152
3,052
91,709

Metric
0 public data writes
1 public data writes
2 public data writes
4 public data writes
8 public data writes

tx_sequencer_processing_time_ms
841 (-3%)
1,549 (-1%)
1,325
2,137 (+1%)
1,333


Group check command returns incorrect value

Description
The command used to check a permission node of a group returns false information.
If the node is not defined, it will return undefined as it should, however if the node is defined and its value is false, the command will still return that the permission node is set to true regardless.
Steps to Reproduce

Set up a clean installation of Spigot (Paper 1.16.1 was used for testing) with only LuckPerms.
Add any permission node to the default group. (here, we'll use example.example) and set its value to false:

/lp group default permission set example.example false

Query the value of the permission node you created using the command:

/lp group default permission check example.example

Expected Output
Notice how it says that the node is set to false, as it should be.
[LP] default has permission example.example set to false in context global.

Actual Output
Notice how it says that the node is set to true, despite us clearly declaring its state.
[LP] default has permission example.example set to true in context global.

It was suggested that I add this screenshot to this issue.
https://cdn.discordapp.com/attachments/241667244927483904/736249179935866971/unknown.png

Should be fixed by the above commit! Thank you for the excellent bug report. :)


MSW memory leak

According to https://github.com/mswjs/msw/discussions/1650 it can be safely ignored

I triggered this issue by switch tabs a of couple times

Apparently it should have been fixed now anyway according to that tracked issue mentioned in the link.


1415 - Handle long interpreter directives in external programs

Fixes #1415
I'm not sure about how to test it, though. Any suggestions?

fyi - this isn't something I have a good way of testing.  I'm not really inclined to merge this without a way to reproduce it through unit tests to verify it actually worked.  Also, the code submitted lowers the over all code coverage, since it also does not contain unit tests.

I'm going to hold off from merging this.  As you know Ansible is adopting Molecule, therefore I do not want to merge anything that may impact future architectural decisions, as I will no longer be leading the development of this project.

Once the repo has been moved under Ansible we can look at getting this merged.
In the short term we welcome testing and feedback on this PR.
Thanks for your understanding.

@kdask thank you for the PR. Looks like for this to progress we need to work out a way to test it, any ideas?

close/repopren to trigger travis build.

Now that I look better a the code I realise that it is totally outside molecule scope to fix broken shebangs lines in scripts not produced by it.
Molecule is not the place to address this issue.


Disallow including the same part in multiple libraries in the same program

Motivated by the discussion in https://github.com/dart-lang/sdk/issues/32999 we want to make it a compile-time error if a file is used as a part in more than one library in the same program.
The implementation of the check for this in Fasta is covered by https://github.com/dart-lang/sdk/issues/32999 - this issue covers the specification change.

Tentatively assigning to @eernstg

Here's a CL for that.

The language team accepted said CL and it has now been landed (as of d7e5332057f012adcd1d57956249582516a07337)


Remove Swift 2.2 curried functions warnings

Since Swift 2.2 (Xcode 7.3+), use of curried functions is deprecated. It will be marked as an error in Swift 3.0. It means only single parameter list functions will be allowed.

I've moved it to lambdas now, didn't see any warning, do you see it again?

Sounds good now :+1: Thanks!


fix formatting error in build configuration

A '```' was indented so it did not end the code section properly

@sebkraemer : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@corob-msft : Thanks for your contribution! The author(s) have been notified to review your proposed change.


What is the best way to test trained model?

I'd like two things as output:

test all images in test set
output only one image instead of 1x4 grid

Which file should be looking at to make these changes? BBDMRunner.py?

Readme updated, test command now involved :)


Add --log-level flag to influxd upgrade

Closes #1795

[x] Tests pass (no build errors)
[x] Rebased/mergeable

Pending https://github.com/influxdata/influxdb/pull/19967.


Directive not working on github but the one on the examples does.

We where using your directive which is really nice but the code on github is not working. We ended copying the one in the examples and it seems newer than the one in github.

You're right.  You seem do this on  #10 .

No, I did't update the code, I just added bower.json but the code is still broken (thanks for the fast response by the way)


Option/property to hide all operations by default

Describe the enhancement you'd like to see
I'd like to be able to hide all operations by default and only expose those that I want by specifying x-kust.enabled=true  at the path or operation level. In this way I'm sure that any new operations I add to my OpenAPI definitions aren't exposed before they're ready
Scenarios

Global options defined but no path or operation has enabled = true - ?
Path has enabled = true but no enabled specified at operation level - ?
Path has no enabled specified but some of the operations do - ?
Is an unspecified enabled option to be treated as an explicit enabled = false and thus disable the whole path

Ole and I discussed this briefly on a call and wanted to open a discussion to nail down how this should actually behave.
Below I've compiled a small example that we can use as the basis for this discussion based on the different possible scenarios
---
# Global options defined but no path or operation has enabled/disabled option set
openapi: 3.0.1
x-kusk:
  SOME_OPTIONS
paths:
  /:
    get: {}
    post: {}
---
# Path has enabled = true but no enabled specified at operation level
openapi: 3.0.1
x-kusk:
  SOME_OPTIONS
paths:
  /:
    x-kusk:
      enabled: true
    get: {}
    post: {}
---
# Path has no enabled specified but some of the operations do
openapi: 3.0.1
x-kusk:
  SOME_OPTIONS
paths:
  /:
    get:
      x-kusk:
        enabled: true
    post: {}

# Question: Is an unspecified enabled option to be treated as an explicit enabled = false

We need to discuss what should happen in each of the scenarios above


Claim.fee_address is missing

Transaction b5a1bf5345c2c727fb866bd312f6e6d23d607da139f54da8ad55ef2591f95cad contains a tip sent for lbry://microsoft-releasing-linux-based#09e79ec21b8e331ddd12a6141fbf9037af9b0766.
However, this transaction is not reported as a tip in the SQL report that shows tips. I believe this because claim.fee_address is not set for claim_id 09e79ec21b8e331ddd12a6141fbf9037af9b0766:
mysql> SELECT id, claim_id, fee_address FROM claim WHERE claim_id = '0f399396ec18a783f9bc66d58fe2095b31f36d40';
+--------+------------------------------------------+-------------+
| id     | claim_id                                 | fee_address |
+--------+------------------------------------------+-------------+
| 133791 | 0f399396ec18a783f9bc66d58fe2095b31f36d40 |             |
+--------+------------------------------------------+-------------+

(It may be appropriate that fee_address is blank here and we need to revise the approach for determining tips. @tiger5226 and I have been discussing over Slack.)

claim0f399396ec18a783f9bc66d58fe2095b31f36d40, does not have a a fee address, therefore it cannot be tipped. The app from what I understand uses the fee_address to tip. In the case you provided, this is a support instead of a tip. The claim owner cannot unlock the tip. If you removed the INNER JOIN you will see the support in chainquery.
SELECT support.supported_claim_id, support.transaction_hash
FROM support
LEFT JOIN claim ON claim.claim_id = support.supported_claim_id
LEFT JOIN address ON address.address = claim.fee_address
LEFT JOIN transaction ON transaction.hash = support.transaction_hash
-- INNER JOIN transaction_address ON transaction_address.transaction_id = transaction.id AND transaction_address.address_id = address.id
WHERE support.transaction_hash = "b5a1bf5345c2c727fb866bd312f6e6d23d607da139f54da8ad55ef2591f95cad"

From what I understood from the tip tracking issue is that @lyoshenka did not want to include supports where it could be taken away but only tips that the claim owner can unlock. We can get both supports and tips in chainquery.
Again my understanding could be wrong. Happy to be corrected here and I can revisit the query.

Talked with @kauffj and he agrees it is not a bug. Also https://lbryio.github.io/lbry/#wallet_send says

If given a claim id, send a tip
to the owner of a claim specified by uri. A tip is a claim support where the recipient
of the support is the claim address for the claim being supported.

Also attempting to tip a claim that has no fee_address will result in daemon error.

This was a misunderstanding. When a claim is supported or tipped the address of the output that created/updated the claim is where the LBC goes.

[ ] Add claim_address field to claim.
[ ] Add an upgrade script to set the claim_address field for all claims.

Closed out @ 8f4959964e6a2a7a50f43cb9b3b8d12a4a4ddbcf


How to fix this error?

error: SWIFT_VERSION '5.0' is unsupported, supported versions are: 3.0, 4.0, 4.2. (in target 'Starscream')

@jannomeister are you still seeing this? If you're using cocoapods try pod update

Or try to install newest cocoapods:
[sudo] gem install cocoapods


Add Docker files, update README

This PR adds the ability to setup playground with docker. Both in development and production mode.

@fsteeg Please try out the development mode.

Added port mappings for lein watch (runs on 8280, uses something on 9630) and updated README with links to the local server. With this, for me the playground starts in dev mode and can be used to run workflows. When I edit code however, it's not reflected in the running instance (which plain lein watch should do).
(You did not ask me to review it, but I still tried prod mode, but that is not working for me: logs look good, but can't connect on port 3000.)

Added port mappings for lein watch (runs on 8280, uses something on 9630) and updated README with links to the local server. With this, for me the playground starts in dev mode and can be used to run workflows.

Thank you! :heart:

When I edit code however, it's not reflected in the running instance (which plain lein watch should do).

Because i forgot to add a bind mount from the project folder on the host to the container, caught up with https://github.com/metafacture/metafacture-playground/pull/171/commits/8a8b9eb907f30ac6a9a59de61dc52b44251cc467

(You did not ask me to review it, but I still tried prod mode, but that is not working for me: logs look good, but can't connect on port 3000.)

Some docker caching is getting in the way, i think. When starting a second mode, you have to use the flag --force-recreate, eg. docker compose up --force-recreate, forcing Docker to create the container anew.
Hopefully, by adding different project names and environments respectively we have a cleaner solution. See this commit https://github.com/metafacture/metafacture-playground/pull/171/commits/a925d77b2643125aa3ac8d8d9c7fc3c86a5c0cf0
Now you should be able to can start both modes independently and in parallel. Check running containers with docker ps.

Picking up code changes in dev mode now works! :+1:
Prod mode also starts, I can access and run examples in general. However, I get a java.security.AccessControlException: access denied ("java.io.FilePermission" "/opt/.project" "read") when running http://localhost:3000/?example=How+to+use+the+Playground

Prod mode also starts, I can access and run examples in general. However, I get a java.security.AccessControlException: access denied ("java.io.FilePermission" "/opt/.project" "read") when running http://localhost:3000/?example=How+to+use+the+Playground

Thanks! Changed installation directory from /opt to /home/playground in order to match permissions set in the provided java policy template. We are using this template as is without any modification. See https://github.com/metafacture/metafacture-playground/pull/171/commits/adbc52fbddff9efbf99ce16df931a8fc862524dc
Please execute docker compose -f docker-compose-dev.yml up --build --force-recreate for Docker to rebuild the underlying image. Otherwise Docker won't pick up changes made in the Dockerfile. (Look for lines beginning with => CACHED in the output of the docker compose command)
You also may want to cleanup unused images and reduce disk usage. Check: docker image ls and delete all unused images: docker image prune -a.


reference python app layer example

create a python app instantiation example

docker
flask or flask-like?

I feel this was accomplished by the Jupyter notebook well enough for now.
https://github.com/SoMind/dtlab-scala-alligator/blob/master/examples/Basic NEO Actors.ipynb


Hover and opacity effects added(#226)

Added hover, opacity and other CSS effects to the buttons.

Your changes look good to me, I am approving this PR.
Also, As this project uses SASS/SCSS, try to make your code changes in .scss files only and then compile it to CSS. If you need any help with this, feel free to ask.

Yeah! Okay @yashsehgal! First I'll learn SASS/SCSS and try to contribute in different ways. If any doubt's regarding that, I'll ask you further. Thank you so much @yashsehgal

Sure, @vimalprogrammer 👍🏽 Take your time :D


Adding ipam options to ipam driver requests

Currently ipam options doesnt seem to be passed to remote ipam drivers. Remote ipam drivers that depend on any driver specific options will not work if ipam options are not included in the
RequestAddress from the swarm manager to allocate IPs. This is a minor fix to pass the ipam options to ipam drivers.
Signed-off-by: Abhinandan Prativadi<EMAIL_ADDRESS>

CI fails :

inconsistent dependencies! what you have in vendor.conf does not match with what you have in vendor
make: *** [dep-validate] Error 1

.vendor.bak/golang.org/x/text/unicode/norm/maketables.go
👹 please format Go code with 'gofmt -s -w'
make: *** [fmt] Error 1

CI fails :

inconsistent dependencies! what you have in vendor.conf does not match with what you have in vendor
make: *** [dep-validate] Error 1

Rebasing on the lastest swarmkit master should fix this. It looks like the branch is based on an old version.

ping @aluzzardi @mavenugo

@nishanttotla This change is needed for the release. libnetwork part of the change is merged.

cc @nishanttotla @dperny @anshulpundir for review.

Vendoring issue seems fixed now.

I'm not very well aware of this part of the codebase, but after reading the initial description and going through the code, it looks fine.

Addressed comments. @nishanttotla @anshulpundir @marcusmartins @mavenugo PTAL.


Convert cobertura to jacoco

Convert cobertura to jacoco

Codecov Report

Merging #5 into master will decrease coverage by 0.09%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             master       #5     +/-   ##
===========================================
- Coverage     24.25%   24.16%   -0.1%
- Complexity        0      453    +453
===========================================
  Files            89       89
  Lines          6288     6287      -1
  Branches       1171     1048    -123
===========================================
- Hits           1525     1519      -6
- Misses         4540     4550     +10
+ Partials        223      218      -5

Impacted Files
Coverage Δ
Complexity Δ

...libaba/com/caucho/hessian/util/IdentityIntMap.java
32.14% <0%> (-7.15%)
7% <0%> (+7%)

...ibaba/com/caucho/hessian/io/SerializerFactory.java
65.12% <0%> (-0.36%)
52% <0%> (+52%)

.../alibaba/com/caucho/hessian/io/JavaSerializer.java
69.1% <0%> (-0.17%)
35% <0%> (+35%)

...libaba/com/caucho/hessian/io/JavaDeserializer.java
57.22% <0%> (-0.13%)
48% <0%> (+48%)

...libaba/com/caucho/hessian/io/BeanDeserializer.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...com/caucho/hessian/io/HessianSerializerOutput.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...ba/com/caucho/hessian/security/X509Encryption.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

.../alibaba/com/caucho/hessian/io/BeanSerializer.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

.../com/caucho/hessian/io/HessianSerializerInput.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...aba/com/caucho/hessian/security/X509Signature.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

... and 4 more

Continue to review full report at Codecov.

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


Bringing the code up to date with latest rustc

Two tiny fixes to the code. It still does not compile because of infinite recursion.
I'm not sure why we need these types instead of using the one in the official simd crate so I'm not going to put any more work into this before I understand that reason.

Closing because of repository inactivity.


Request for Slack api WebhookResponse send(String url, Payload payload)  to return ts value

My issue is similar to the problem described here: https://stackoverflow.com/questions/56291169/slack-get-thread-id-after-posting-message-using-incoming-web-hook
I am currently using slack as our new service notification hub. But I like to organize the notification per a specific event id. So when the service is going to persist the ts value for the first message related to the event id and put subsequent message in the thread.
Category (place an x in each of the [ ])

[ x] bolt (Bolt for Java)
[ ] bolt-{sub modules} (Bolt for Java - optional modules)
[ ] slack-api-client (Slack API Clients)
[ ] slack-api-model (Slack API Data Models)
[ ] slack-api-*-kotlin-extension (Kotlin Extensions for Slack API Clients)
[ ] slack-app-backend (The primitive layer of Bolt for Java)

Requirements
Please make sure if this topic is specific to this SDK. For general questions/issues about Slack API platform or its server-side, could you submit questions at https://my.slack.com/help/requests/new instead. :bow:
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you agree to those rules.

Hi, @rhibiscusc! Thank you for your question! 🙌
Based on the documentation, it looks like not returning the ts is not just a limitation of the Java SDK, but a limitation of Incoming Webhooks in general:

You can use an Incoming Webhook to make your message appear as a reply in a thread. You'll need to retrieve the message ts value, however, as it is not returned when sending a request to an Incoming Webhook.

You can retrieve the ts value in one of the following ways:

Enable and use the Events API so that you can subscribe to event types that will send a callback when a new message is sent by your webhook.
Use the search.messages method to search for the message you sent based on the timestamp.
Use the conversations.history method to search for the message from a set of messages.

I hope this helps!

As Ashly mentioned, you can utilize other web APIs to fetch the data. Another suggestio is to switch to chat.postMessage API rather than using an incoming webhook. The chat.postMessage API response provides the posted message's channel ID and ts. This should be the most straight-forward way to achieve your goal.
Since we don't have anything else to share on this topic, let me close this issue. That said, whenever you have any follow up questions on this topic, please don't hesitate to write in!


Updated Parameter -UsernameMatchesAnyOfPatterns

The Accept wildcard characters under Parameter -UsernameMatchesAnyOfPatterns is set to True.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/client-access/New-ClientAccessRule.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


cargo-vet interoperability?

There's now a substantial repository of cargo-vet reviews.
The interface of cargo vet is IMHO much more simple and practical.
And it's a waste to have two dependency verification tools, each with incomplete dependency coverage.
So I think we need to consider what is crev's role in relation to cargo-vet. I think having interoperability between the tools would be very useful.
crev to vet
Every crev proof repository could also be a cargo-vet audit repository. We could automatically convert crev proofs into list of vet audits, and put it in the same repo.
The main problem is how to map crev's attributes, like thoroughness and understanding into vet's criteria of safe-to-run and safe-to-deploy. Vet supports custom criteria, so crev could make some up (like trust-medium-rating-positive), but the two built-in ones are essential for vet.
vet to crev
We could have a bot that loads the vet registry and updates a crev proof repo with them.

For now I went for deducing safe-to-run and safe-to-deploy from a bit of fuzzy logic combining trust + rating + thoroughness + understanding of reviews.
I'm worried that this is not good enough — people's opinions may differ both ways. Some may want more approvals for cargo vet, and some may object that the existing reviews never explicitly stated these criteria, so guessing them is not robust enough.
I think we should just add the criteria field to the reviews explicitly. For the old reviews without them, I'll add config to tune or disable the fuzzy-guessing logic.


59 test expressions

Codecov Report
Patch coverage: 72.14% and project coverage change: -4.20 :warning:

Comparison is base (a38b8dd) 97.45% compared to head (8428d0b) 93.25%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff              @@
##               main      #61      +/-   ##
============================================
- Coverage     97.45%   93.25%   -4.20%
- Complexity      522      581      +59
============================================
  Files           143      157      +14
  Lines          1101     1320     +219
  Branches         32       36       +4
============================================
+ Hits           1073     1231     +158
- Misses           23       80      +57
- Partials          5        9       +4

Impacted Files
Coverage Δ

...ain/java/org/saynotobugs/confidence/Assertion.java
61.11% <0.00%> (-30.56%)
:arrow_down:

...tobugs/confidence/quality/composite/WhenGiven.java
0.00% <0.00%> (ø)

...bugs/confidence/utils/DescriptionCharSequence.java
0.00% <0.00%> (ø)

...ugs/confidence/junit5/engine/verifiable/Using.java
0.00% <0.00%> (ø)

...ugs/confidence/junit5/engine/verifiable/Given.java
55.55% <55.55%> (ø)

...nce/junit5/engine/testengine/ConfidenceEngine.java
84.61% <84.61%> (ø)

.../testdescriptor/VerifiableGroupTestDescriptor.java
86.95% <86.95%> (ø)

...e/testdescriptor/AssertionArrayTestDescriptor.java
87.50% <87.50%> (ø)

...it5/engine/testdescriptor/FieldTestDescriptor.java
87.50% <87.50%> (ø)

...saynotobugs/confidence/quality/object/Affects.java
100.00% <100.00%> (ø)

... and 5 more

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


build error

D:\diary\mydiary>hugo.exe version
Hugo Static Site Generator v0.38.2 windows/amd64 BuildDate: 2018-04-09T08:17:46Z
Started building sites ...
ERROR 2018/04/12 09:24:34 Error while rendering "home" in "": template: D:\diary\mydiary\themes\hugo-theme-jane\layouts\index.html:11:5: executing "D:\\diary\\mydiary\\themes\\hugo-theme-jane\\layouts\\index.html" at <partial "head.html" ...>: error calling partial: template: theme/partials/head.html:26:116: executing "theme/partials/head.html" at <safeHTML>: wrong number of args for safeHTML: want 1 got 0
ERROR 2018/04/12 09:24:34 Error while rendering "taxonomyTerm" in "": template: D:\diary\mydiary\themes\hugo-theme-jane\layouts\_default\terms.html:11:5: executing "D:\\diary\\mydiary\\themes\\hugo-theme-jane\\layouts\\_default\\terms.html" at <partial "head.html" ...>: error calling partial: template: theme/partials/head.html:26:116: executing "theme/partials/head.html" at <safeHTML>: wrong number of args for safeHTML: want 1 got 0
ERROR 2018/04/12 09:24:34 Error while rendering "404" in "": template: D:\diary\mydiary\themes\hugo-theme-jane\layouts\404.html:11:5: executing "D:\\diary\\mydiary\\themes\\hugo-theme-jane\\layouts\\404.html" at <partial "head.html" ...>: error calling partial: template: theme/partials/head.html:26:116: executing "theme/partials/head.html" at <safeHTML>: wrong number of args for safeHTML: want 1 got 0
Total in 106 ms
Started building sites ...
Total in 51 ms

Could you paste your config.toml ?

That config.toml  is default , I just add the jane theme name.

Are you using the default config by hugo new site?
Maybe you'd better use the default config.toml from the themes/jane/exampleSite/config.toml.
You could take a look at README https://github.com/xianmin/hugo-theme-jane#3-quick-use-hugo-theme-jane

@xianmin  OK, I try again  follow the README.

It is my fault .I copied the config.toml and solved .
And how can I remove icon-new-window from external-link ?

header.html

    {{ range .Site.Menus.main -}}

        {{if hasPrefix .URL "http"}}

          {{ .Name }}

        {{else}}
        {{ .Name }}
        {{end}}

    {{- end }}


The validated value is never be null

The value parameter of the FormeValidator that will never be null.It makes "if(v==null)" in the Validator never work.
In FormeFieldState, the value field is T, not T?. The _value initialize by initialValue in beforeInitiation.
And 'initialValue' depends on widget.initialValue from FormeField .
But FormeField's initialValue is not T? too.
FormeField's initialValue initialize by subclass, such as FormeTextField.
In FormeTextField's constructor, initialValue is treated as a valid value (‘’) to super.
class FormeTextField extends FormeField<String> {
  FormeTextField({
  String? initialValue,
  ...
  }): super(
     ...
     initialValue: initialValue ?? '',
     ...
  );
}

class FormeField<T> extends StatefulWidget {
  ...
  final T initialValue;
  ...
}

class FormeFieldState<T> extends State<FormeField<T>> {
  ...
  late T _value;

  T get value => _value;
  ...

  void _validate() {
  if (_hasValidator) {
      final String? errorText = widget.validator!(controller, value);
      ...
      }
    }
  }

@protected
  @mustCallSuper
  void beforeInitiation() {
    _readOnlyNotifier.value = readOnly;
    _value = initialValue;
    _valueNotifier = FormeMountedValueNotifier(initialValue, this);
    _validation = _initialValidationState;
    _validationNotifier = FormeMountedValueNotifier(_validation, this);
  }

  /// get initialValue
  T get initialValue =>
      widget.initialValue ??
      _formeState?.getInitialValue(name, widget.initialValue) as T;
}

Sorry I didn't notice the generic type of FormeTextField, and frankly, I didn't know that generic T could be instantiated as a nullable.Thanks.:smile:


Needs a man page

added

make install DESTDIR=/tmp/dan1
go build -v -o oci-registerMachine
github.com/godbus/dbus
_/home/dwalsh/Register
go get github.com/cpuguy83/go-md2man
go-md2man -in "oci-registerMachine.1.md" -out "oci-registerMachine.1"
gzip oci-registerMachine.1
install -d -m 0755 /tmp/dan1/usr/libexec/docker/hooks.d
install -m 755 oci-registerMachine /tmp/dan1/usr/libexec/docker/hooks.d
cp oci-registerMachine.1.gz /usr/share/man/man1
cp: cannot create regular file ‘/usr/share/man/man1/oci-registerMachine.1.gz’: Permission denied
Makefile:32: recipe for target 'install' failed
make: *** [install] Error 1
Broken.

Can we get the path generated on the fly?  Since we have HOOKSDIR defined in the makefile.

sudo make install ok?

Well yes but that is not the way rpm works,  You need DESTDIR support.  You should also use install not cp.

Use sed to switch the HOOKSDIR in the man page to give you the path to HOOKCDIR>

I updated, added DESTDIR support
On Wed, Nov 11, 2015 at 3:49 PM, Daniel J Walsh<EMAIL_ADDRESS>wrote:

Use sed to switch the HOOKSDIR in the man page to give you the path to
HOOKCDIR>
—
Reply to this email directly or view it on GitHub
https://github.com/sallyom/Register/issues/7#issuecomment-155905440.


WIP: Improve lighting in 3D viz

This PR reworks lighting in 3d viz scenes:

master
PR

Related to https://github.com/mne-tools/mne-python/pull/6731#issuecomment-532625434

is there a lighting result (eg from pysurfer) that you are aiming for?

The goal is to reproduce the lighting method used by Mayavi. Should I maybe update the table to integrate it?

Yes I have noticed that they are different. The right still doesn't quite look like Mayavi, though -- the contrast is too large. Maybe the ambient light level is higher in Mayavi?

I agree it requires some adjustment for mayavi like figure.

Hm... I checked the ambient and diffuse values and they are the same (mayavi against pyvista) :thinking:
I'll keep looking

Difference in light follows camera vs not? Default light locations?

Maybe this?
https://github.com/nipy/PySurfer/blob/master/surfer/viz.py#L3496-L3502

It's trickier than it seems. It's technically 3 lights (of type CameraLight) but the first one (of type HeadLight) is actually disabled.

Updated table after e23c884

master
PR

I like the way it looks !

@larsoner I pushed 4df834b to integrate https://github.com/mne-tools/mne-python/pull/8182#issuecomment-684932447

I'll merge this, let's take care of sph_to_cart deduplication in another PR when someone sees it and remembers to do it

Thanks @GuillaumeFavelier !


Support pre-nehalem processors

hello, its my first time using cranelift as a back-end, my first hello world program which is just a cargo new project,
crashes with SIGILL
`
build
cg_clif_dir/build/cargo.sh b
`
this is lldb output
`

thread #1, name = 'hello_world', stop reason = signal SIGILL: illegal instruction operand
frame #0: 0x0000555555655f96 hello_worldcore::alloc::layout::Layout::from_size_align::h6048d467bfec8bb4 + 8 hello_worldcore::alloc::layout::Layout::from_size_align::h6048d467bfec8bb4:
->  0x555555655f96 <+8>:  popcntq %rsi, %rax
0x555555655f9b <+13>: movl   $0x1, %ecx
0x555555655fa0 <+18>: cmpl   %ecx, %eax
0x555555655fa2 <+20>: jne    0x55555565600d            ; <+127> at layout.rs:63:20
(lldb) bt
thread #1, name = 'hello_world', stop reason = signal SIGILL: illegal instruction operand

frame #0: 0x0000555555655f96 hello_worldcore::alloc::layout::Layout::from_size_align::h6048d467bfec8bb4 + 8 frame #1: 0x0000555555655ebe hello_worldcore::alloc::layout::Layout::pad_to_align::h3568c8d4bff4febc at nonzero.rs:148:1
frame #2: 0x0000555555656117 hello_worldcore::alloc::layout::Layout::array::h015c7a99e7b0bc37 at layout.rs:394:14 frame #3: 0x000055555565daf6 hello_worldalloc::raw_vec::RawVec$LT$T$C$A$GT$::allocate_in::hd048b82a60ccc1a8 + 43
frame #4: 0x000055555556c7eb hello_world_$LT$T$u20$as$u20$alloc..slice..hack..ConvertVec$GT$::to_vec::h95d9fe7b35c0ffb0 at mod.rs:117:22 frame #5: 0x000055555557ee5c hello_worldstd::rt::lang_start_internal::h55442e27331b7102 at rt.rs:44:39
frame #6: 0x00005555555671d9 hello_worldstd::rt::lang_start::hd60cecbcdf6bd999 at rt.rs:66:9 frame #7: 0x0000555555567268 hello_worldmain + 29
frame #8: 0x00007ffff7db4b25 libc.so.6__libc_start_main + 213 frame #9: 0x000055555556706e hello_world_start + 46
`

my cpu is core 2 due T7300

The popcnt instruction seems to have been introduced with nehalem (https://github.com/bytecodealliance/wasmtime/blob/5c1d728e3ae8ee7aa329e294999a2c3086b21676/cranelift/codegen/meta/src/isa/x86/settings.rs#L108-L111). Your processor predates this introduction.
You could try disabling the nehalem preset here: https://github.com/bjorn3/rustc_codegen_cranelift/blob/341a4863fabe8c67b1b72c6d3183ee824878f950/src/lib.rs#L338 It is possible that compilation will fail though. If it fails removing this line may help: https://github.com/bjorn3/rustc_codegen_cranelift/blob/341a4863fabe8c67b1b72c6d3183ee824878f950/src/common.rs#L73
If disabling the nehalem preset fixes the problem, I would like to keep this issue open as tracking issue for pre-nehalem processors.

The popcnt instruction seems to have been introduced with nehalem (https://github.com/bytecodealliance/wasmtime/blob/5c1d728e3ae8ee7aa329e294999a2c3086b21676/cranelift/codegen/meta/src/isa/x86/settings.rs#L108-L111). Your processor predates this introduction.
You could try disabling the nehalem preset here:
https://github.com/bjorn3/rustc_codegen_cranelift/blob/341a4863fabe8c67b1b72c6d3183ee824878f950/src/lib.rs#L338
It is possible that compilation will fail though. If it fails removing this line may help:
https://github.com/bjorn3/rustc_codegen_cranelift/blob/341a4863fabe8c67b1b72c6d3183ee824878f950/src/common.rs#L73
If disabling the nehalem preset fixes the problem, I would like to keep this issue open as tracking issue for pre-nehalem processors.

commenting the nehalem line solved the problem, thank you

The popcnt instruction seems to have been introduced with nehalem (https://github.com/bytecodealliance/wasmtime/blob/5c1d728e3ae8ee7aa329e294999a2c3086b21676/cranelift/codegen/meta/src/isa/x86/settings.rs#L108-L111). Your processor predates this introduction.
You could try disabling the nehalem preset here:
https://github.com/bjorn3/rustc_codegen_cranelift/blob/341a4863fabe8c67b1b72c6d3183ee824878f950/src/lib.rs#L338
It is possible that compilation will fail though. If it fails removing this line may help:
https://github.com/bjorn3/rustc_codegen_cranelift/blob/341a4863fabe8c67b1b72c6d3183ee824878f950/src/common.rs#L73
If disabling the nehalem preset fixes the problem, I would like to keep this issue open as tracking issue for pre-nehalem processors.

commenting the nehalem line solved the problem, thank you

(deleted a duplicate comment)

cg_clif should now compile against the same target cpu as the LLVM backend would. I haven't tested if it doesn't accidentally use any newer instruction though.


Add Kubernetes release artifacts

Currently, we support AWS and Azure deployments. It would be beneficial to add Kubernetes deployments (preferably a Helm chart) for VMClarity.

@ramizpolic thanks for adding this, the first step for this is #345 IMO, and thats something I'm going to be putting a PR up for soon. Once we've got that then I think a helm chart is 100% the right choice, and then we can think about EKS/AKS/GKE deployments.


[rancherd] Bump RKE2 version - 1.20

Once the Rancher team is ready, we should plan to update rancherd to RKE2 version 1.20.x (latest stable).

Related issue for 1.19.x: https://github.com/rancher/rancher/issues/30492 - this issue has more context and and example covering the processs if you look at the linked PR and comments.

Utilize v1.20.5+k3s1 now instead of v1.20.4+k3s1 due to a CVE called out in v1.20.5 k3s release notes.

Rancherd is failing to start. It looks to be using the rke2-runtime:latest tag instead of rke2-runtime:v1.20.6-rke2r1
> curl -sfL https://get.rancher.io | sudo INSTALL_RANCHERD_VERSION=v2.5.8-rc12 sh -
> systemctl enable rancherd-server.service && systemctl start rancherd-server.service
> journalctl -eu rancherd-server -f
...
rancherd[2608]: time="2021-04-28T16:43:49Z" level=fatal msg="Runtime image index.docker.io/rancher/rke2-runtime:latest is not a not a reference to a digest or version tag matching pattern ^v[0-9]"
...

Validated rancherd is using v1.20.5+rke2r1 and installs correctly in both airgap and not.


[go_router] UI is stuck while trying to navigate between routes

Is there an existing issue for this?

[X] I have searched the existing package issues
[X] I have read the guide to filing a bug

What package does this bug report belong to?
go_router
What target platforms are you seeing this bug on?
iOS
Have you already upgraded your packages?
Yes
Dependency versions
pubspec.lock
[Paste file content here]

Steps to reproduce

Start the app
Click the button
Click another button and start swipe the current route and wait for new route to appear

Expected results
Interface is active
Actual results
Interface is inactive
Code sample

import 'package:flutter/material.dart';
import 'package:go_router/go_router.dart';

void main() {
  runApp(const MyApp());
}

final _rootNavigatorKey = GlobalKey<NavigatorState>();

final router = GoRouter(
  navigatorKey: _rootNavigatorKey,
  initialLocation: '/feed',
  routes: <RouteBase>[
    GoRoute(
      path: '/feed',
      builder: (context, state) => const FeedPage(),
      routes: <RouteBase>[
        GoRoute(
          path: 'details',
          parentNavigatorKey: _rootNavigatorKey,
          builder: (context, state) {
            return const DetailsPage();
          },
        ),
        GoRoute(
          path: 'test',
          parentNavigatorKey: _rootNavigatorKey,
          builder: (context, state) {
            return const Test();
          },
        ),
      ],
    ),
  ],
);

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp.router(
      title: 'Flutter Demo',
      theme: ThemeData(
        colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
        useMaterial3: true,
      ),
      routerConfig: router,
    );
  }
}

class Test extends StatelessWidget {
  const Test({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: [
            Text(
              'Test',
              style: Theme.of(context).textTheme.headlineLarge,
            ),
            ElevatedButton(onPressed: () => print('touch'), child: Text('click')),
          ],
        ),
      ),
    );
  }
}

class FeedPage extends StatelessWidget {
  const FeedPage({super.key, this.label, this.child});

  final String? label;
  final Widget? child;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: [
            Text(
              'Feed',
              style: Theme.of(context).textTheme.headlineLarge,
            ),
            ElevatedButton(
              onPressed: () {
                context.go('/feed/details');
              },
              child: const Text('Go to feed/details'),
            ),
          ],
        ),
      ),
    );
  }
}

class DetailsPage extends StatelessWidget {
  const DetailsPage({super.key});

  void _go(BuildContext context) {
    Future.delayed(const Duration(seconds: 2), () {
      context.go('/feed/test');
    });
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: [
            Text(
              'Feed Details',
              style: Theme.of(context).textTheme.headlineLarge,
            ),
            ElevatedButton(
              onPressed: () => _go(context),
              child: const Text('Go to feed/details/test'),
            ),
          ],
        ),
      ),
    );
  }
}

Screenshots or Videos

Screenshots / Video demonstration
[Upload media here]

https://github.com/flutter/flutter/assets/109822566/58f284ad-19b4-42ef-92aa-c792c45eb0c3
Logs
Logs
[Paste your logs here]

Doctor output
[✓] Flutter (Channel stable, 3.13.0, on macOS 12.5 21G72 darwin-arm64, locale en-US)
    • Flutter version 3.13.0 on channel stable at /Users/user/fvm/versions/3.10.6
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision efbf63d9c6 (10 weeks ago), 2023-08-15 21:05:06 -0500
    • Engine revision 1ac611c64e
    • Dart version 3.1.0
    • DevTools version 2.25.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    • Android SDK at /Users/user/Library/Android/sdk
    • Platform android-33, build-tools 33.0.1
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14C18
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] VS Code (version 1.83.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.74.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 12.5 21G72 darwin-arm64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 118.0.5993.88

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Thanks for the report. Seeing the same behavior as reported.

 stable, master flutter doctor -v
[!] Flutter (Channel stable, 3.13.8, on macOS 12.2.1 21D62 darwin-x64, locale
    en-GB)
    • Flutter version 3.13.8 on channel stable at
      /Users/dhs/documents/fluttersdk/flutter
    ! Warning: `flutter` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/flutter, which is not inside
      your current Flutter SDK checkout at
      /Users/dhs/documents/fluttersdk/flutter. Consider adding
      /Users/dhs/documents/fluttersdk/flutter/bin to the front of your path.
    ! Warning: `dart` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/dart, which is not inside your
      current Flutter SDK checkout at /Users/dhs/documents/fluttersdk/flutter.
      Consider adding /Users/dhs/documents/fluttersdk/flutter/bin to the front
      of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 6c4930c4ac (5 days ago), 2023-10-18 10:57:55 -0500
    • Engine revision 767d8c75e8
    • Dart version 3.1.4
    • DevTools version 2.25.0
    • If those were intentional, you can disregard the above warnings; however
      it is recommended to use "git" directly to perform update checks and
      upgrades.

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.62.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

[!] Flutter (Channel master, 3.16.0-15.0.pre.1, on macOS 12.2.1 21D62
    darwin-x64, locale en-GB)
    • Flutter version 3.16.0-15.0.pre.1 on channel master at
      /Users/dhs/documents/fluttersdk/flutter
    ! Warning: `flutter` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/flutter, which is not inside
      your current Flutter SDK checkout at
      /Users/dhs/documents/fluttersdk/flutter. Consider adding
      /Users/dhs/documents/fluttersdk/flutter/bin to the front of your path.
    ! Warning: `dart` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/dart, which is not inside your
      current Flutter SDK checkout at /Users/dhs/documents/fluttersdk/flutter.
      Consider adding /Users/dhs/documents/fluttersdk/flutter/bin to the front
      of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision eefafdacdb (3 days ago), 2023-10-20 00:06:34 -0400
    • Engine revision 9dd59f7fcf
    • Dart version 3.3.0 (build 3.3.0-45.0.dev)
    • DevTools version 2.28.1
    • If those were intentional, you can disregard the above warnings; however
      it is recommended to use "git" directly to perform update checks and
      upgrades.

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/dhs/Library/Android/sdk
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for
      more details.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 13C100
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] IntelliJ IDEA Ultimate Edition (version 2021.3.2)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 65.1.4
    • Dart plugin version 213.7228

[✓] VS Code (version 1.62.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.29.0

[✓] Connected device (3 available)
    • Darshan's iphone (mobile) • 21150b119064aecc249dfcfe05e259197461ce23 • ios
      • iOS 15.3.1 19D52
    • macOS (desktop)           • macos                                    •
      darwin-x64     • macOS 12.2.1 21D62 darwin-x64
    • Chrome (web)              • chrome                                   •
      web-javascript • Google Chrome 109.0.5414.119

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.62.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

looks like a framework issue

cc @hangyujin

I was not able to reproduce it with default flutter route, but I will try again and send the result

My guts feeling tells me there is something wrong with cupertinoBackSwipe disable/re-enable gestures when it is triggered

Yes this it due to _CupertinoBackGestureDetector is disposed during the drag.


Added 1 to 5 words to make up a matlib story

Dear Siva,
Requesting you to review my work here!
Regards,
Harshavardhana

changes look good!


Create tests for vessel-charging/messages/ProviderStatusMessageParams using jest.

first-timers-only
This issue is tagged :octocat: first-timers-only. It is only for people who have never contributed to open source before, and are looking for an easy way take their first steps.
Consider this your chance to dip your toe into the world of open-source, and get some bragging rights for writing code that makes drones fly, lets cars find charging stations, helps people and goods get from place to place, and more.
Find more first-timers-only issues from DAV Foundation here.
Thank you for your help :heart:
What is this project?
DAV (Decentralized Autonomous Vehicles) is a new foundation working to build an open-source infrastructure for autonomous vehicles (cars, drones, trucks, robots, and all the service providers around them) to communicate and transact with each other over blockchain.
As an organization that believes in building a large community of open-source contributors, we often create issues like this one to help people take their first few steps into the world of open source.
dav-js
This SDK enabled integrating any client side JS and NodeJS code with the DAV Network.
How you can help
The Issue
Create tests for vessel-charging/messages/ProviderStatusMessageParams using jest.
You need to create tests to check that the serialize and deserialize methods work as expected.
Please use the test file for class NeedParams as a basis for your new code.

Function serialize in class MessageParams must return a JSON object that contains all properties defined in the MessageParams instance.

Function deserialize in class MessageParams receives a JSON string and must initialize all the properties of the MessageParams instance with the values in the JSON string.

messageParams1.desrialize(messageParams2.serialize()) == messageParams2 must therefore always be true.
NOTE: Some names are changed between protocol string representation of instance properties:

location is internally represented as { lat , lon } but serialized as { latitude , longitude }
Private properties are internally prefixed with _ but serialized without the prefix. i.e. _protocol becomes protocol

Contributing to dav-js

[ ] Make sure this issue is labeled up-for-grabs and not labeled claimed, to verify no one else is working on it.
[ ] Comment in this issue that you would like to do it.
[ ] Open dav-js GitHub page and click the ★ Star and then ⑂ Fork buttons.
[ ] Clone a copy to your local machine with $ git clone git@github.com:YOUR-GITHUB-USER-NAME/dav-js.git
[ ] Code Code Code
[ ] Once you've made sure all your changes work correctly and committed all your changes, push your local changes back to github with $ git push -u origin master
[ ] Visit your fork on GitHub.com (https://github.com/YOUR-USER-NAME/dav-js) and create a pull request for your changes.
[ ] Make sure your pull request describes exactly what you changed and references this issue (include the issue number in the title like this: #7)
[ ] Please do not fix more than one issue at a time. Your pull request should only fix what is described in this issue.

Asking for help
We appreciate your effort in taking the time to work on this issue and help out the open source community and the foundation. If you need any help, feel free to ask below or in our gitter channel. We are always happy to help 😄

Hi, I am a newbie to open source and would like to handle this issue

Please go ahead @rashmithajunoothula 👍

@rashmithajunoothula  I believe there is a bug in all the message files for vessel-charging which will cause you to not be able to complete this issue.
I'll update here once we fix this.

@rashmithajunoothula The bug has been resolved. Are you still interested in doing this issue?

HI @rashmithajunoothula are you still interested in this? I'd love to work on some tests in the meanwhile. Perhaps I should take this @TalAter


Provide 'or'-like funcitonality for providers so that they can provide a one-of like relationship for inputs

Provider is similar to the JDK Optional type in that a value is derived through some execution path or the value derivation is not present. When wrapping existing tools or developing new tools, the ability to specify a one-of or hierarchy of values can be useful. For example when wrapping the Kubernetes built-in tool kustomize, it uses a default input file of one of kustomization.yaml, kustomization.yml, or Kustomization. Attempting to map this to an @InputFile or @InputFiles from its contents can be difficult given the existing APIs.
Expected Behavior
Provider and lazy configuration APIs should allow for providing one-of like semantics as shown below. Provider types should be more functional and allow or composition like most functional types that exist today.
A workaround today for providing one-of files to a task might be accomplished by something like:
project.objects.fileProperty().apply {
        convention(
            project.layout.file(
                project.provider {
                    val a = project.file("a")
                    if (a.exists()) {
                        return@provider a
                    }
                    val b = project.file("b")
                    if (b.exists()) {
                        return@provider b
                    }
                    project.file("c")
                }
            )
        )
    }

Current Behavior
No API exist today, so the behavior needs to be sort-of wrapped through the use of an a provider {} wrapped block that performs the logic itself
Context
I was attempting to provide a one-of default value (or value in general) for a Property task input, such that one of the inputs are considered for up-to-date with some hierarchy. It would be useful if all inputs were considered and some type of error message could be considered, so that a "there are multiple inputs" type error message could be returned to users.

Added via https://github.com/gradle/gradle/pull/9774


Docs only showing tags in details section of source objects

Describe the bug
User is not seeing their sources details from their yaml file displayed in docs after doing a dbt docs generate on 1.6 and 1.7.
Steps To Reproduce

dev (or prod) env on v1.7 or 1.6
do dbt docs generate
Switch env to 1.5 then generate again, and the details section is populated.

Expected behavior

Screenshots and log output

The output of dbt --version:
1.6 and 1.7
Additional context
Displayed in dbt Explorer in 1.7.

Thanks for reporting this @crystalro0 !
I see what you are saying about 1.5 working but 1.6 and 1.7 having a bug.
Reprex
Here's the models/_sources.yml that I used:
version: 2

sources:
  - name: agdirect_dbo
    tables:
      - name: dim_customers

Then I ran these commands using dbt-core:
dbt docs generate
dbt docs serve

When I open the developer tools in Chrome, I can see the following javascript errors:
(index):73 TypeError: Cannot read properties of undefined (reading 'contract')
(index):73 TypeError: Cannot read properties of undefined (reading 'enforced')

@dbeatty10 you're awesome! fixed my sandbox with:
version: 2

sources:

  - name: agdirect_dbo
    config:
      contract:
        enforced: false
    database: DEMO_DB
    loader: qlik_replicate
    tables:
      - name: dim_customers

Thank you!

Thanks for reporting this @crystalro0 !
I see what you are saying about 1.5 working but 1.6 and 1.7 having a bug.
Reprex
Here's the models/_sources.yml that I used:
version: 2

sources:
  - name: agdirect_dbo
    tables:
      - name: dim_customers

Then I ran these commands using dbt-core:
dbt docs generate
dbt docs serve

When I open the developer tools in Chrome, I can see the following javascript errors:
(index):73 TypeError: Cannot read properties of undefined (reading 'contract')
(index):73 TypeError: Cannot read properties of undefined (reading 'enforced')

Nice idea @crystalro0 -- adding the contract config is a clever workaround! 🧠

This looks like it is fixed in v1.8.
I'm not sure if it was fixed in a commit in dbt-docs or something within dbt-core.
Either way, I'm closing this as resolved.


Fix date serialization

JSON: Prevents "date" objects to fail with serialization

Coverage decreased (-0.08%) to 81.415% when pulling c086c4f85a49cebb1d4b976ad57c5b10effe421b on gbrian:fix_date_serialization into aaef338539eff4ff855e0f87bcb17ca71440e251 on airbnb:master.

@xrmx Sorry not that good in Python. Please feel free to change accordingly to the project standards. I'll take note for the next one.

@gbrian i can't change it :)

Ops, done! :)

@gbrian  Thanks a lot!

Coverage decreased (-0.08%) to 81.415% when pulling 9696d74186aec0bd578f0837aa39dc8243751154 on gbrian:fix_date_serialization into aaef338539eff4ff855e0f87bcb17ca71440e251 on airbnb:master.

Coverage decreased (-0.08%) to 81.415% when pulling 6de1489bfb97432133e2f993d514560d2b7d768c on gbrian:fix_date_serialization into 82a8e6316f874b28c8b8ff718917006b524cd7d6 on airbnb:master.

@mistercrunch: ok, gotcha and updated.

Coverage decreased (-0.1%) to 81.396% when pulling 2bf6dfb4a4aeae915c12ea52684f355442cfe9c2 on gbrian:fix_date_serialization into 82a8e6316f874b28c8b8ff718917006b524cd7d6 on airbnb:master.

Coverage decreased (-0.08%) to 81.396% when pulling e594e617803a401641dd64ca3e168816b215a927 on gbrian:fix_date_serialization into cb23362a5bff9cec8354968b5a8a612126e1d82d on airbnb:master.

Coverage decreased (-0.05%) to 81.426% when pulling e594e617803a401641dd64ca3e168816b215a927 on gbrian:fix_date_serialization into cb23362a5bff9cec8354968b5a8a612126e1d82d on airbnb:master.

@xrmx done and thanks

Coverage decreased (-0.05%) to 81.426% when pulling 8b4c94bbcd79e54482b381625a473de31d30ae72 on gbrian:fix_date_serialization into b0a1f07818cc1454bb823933a783035f753d72e8 on airbnb:master.

Coverage decreased (-0.05%) to 81.426% when pulling 8b4c94bbcd79e54482b381625a473de31d30ae72 on gbrian:fix_date_serialization into b0a1f07818cc1454bb823933a783035f753d72e8 on airbnb:master.

![img] (http://reaction.club/r/a0b8a78.gif)