PIO support

Add support for PIO hardware. This PR is based on #9 and implements most of the missing features, including interrupts.
This PR depends on pio-rs#3.
Closes #5.

Was this implementation already testet on hardware?
I'm trying to drive a sk6812 (similar to wb2812) led strip with pio and I can't get it to work.
I might try a more minimalist example like blinking the onboard led on the pico using pio.

This is my code for driving a sk6812 (rgbw) strip of 60 leds using a rp pico.
Am I missing something?
#![no_std]
#![no_main]

use cortex_m_rt::entry;
use hal::pac;
use panic_halt as _;
use rp2040_hal as hal;

#[link_section = ".boot2"]
#[used]
pub static BOOT2: [u8; 256] = rp2040_boot2::BOOT_LOADER;

#[entry]
fn main() -> ! {
    let mut pac = pac::Peripherals::take().unwrap();

    let mut assembler = pio::Assembler::new();

    const T1: u8 = 2;
    const T2: u8 = 5;
    const T3: u8 = 3;

    let mut bitloop = assembler.label();
    let mut do_one = assembler.label();
    let mut do_zero = assembler.label();

    assembler.bind(&mut bitloop);
    assembler.out_with_delay_and_side_set(pio::OutDestination::X, 1, T3 - 1, 0);
    assembler.jmp_with_delay_and_side_set(pio::JmpCondition::XIsZero, &mut do_zero, T1 - 1, 1);
    assembler.bind(&mut do_one);
    assembler.jmp_with_delay_and_side_set(pio::JmpCondition::Always, &mut bitloop, T2 - 1, 1);
    assembler.bind(&mut do_zero);
    // Pseudoinstruction: NOP
    assembler.mov_with_delay_and_side_set(
        pio::MovDestination::Y,
        pio::MovOperation::None,
        pio::MovSource::Y,
        T2 - 1,
        0,
    );

    let program = assembler.assemble(None);

    let pio = hal::pio::PIO::new(pac.PIO0, &mut pac.RESETS);
    let sm = &pio.state_machines()[0];

    let cycles_per_bit = T1 + T2 + T3;
    const FREQ: u32 = 8_000_000;
    const SYSCLOCK_FREQ: u32 = 133_000_000;
    let div = SYSCLOCK_FREQ as f32 / (FREQ as f32 * cycles_per_bit as f32);

    hal::pio::PIOBuilder::default()
        .with_program(&program)
        .buffers(hal::pio::Buffers::OnlyTx)
        .side_set(pio::SideSet::new(false, 1, false))
        .side_set_pin_base(22)
        .out_shift_direction(hal::pio::ShiftDirection::Left) // Of Left?
        .autopull(true)
        .pull_threshold(32)
        .clock_divisor(div)
        .build(&pio, sm)
        .unwrap();

    sm.set_enabled(true);

    const NLED: usize = 60;

    let mut data = [0u32; NLED];
    for byte in &mut data {
        *byte = u32::MAX;
    }

    for word in data {
        sm.push(word);
    }

    loop {
        cortex_m::asm::nop();
    }
}

Was this implementation already testet on hardware?

Yes, in fact. I'm using PIO to decode DMX-512 signal.

Am I missing something?

What you are at least missing is handing GPIO pins over to PIO.
let sio = hal::sio::Sio::new(device.SIO);
let pins = Pins::new(
    device.IO_BANK0,
    device.PADS_BANK0,
    sio.gpio_bank0,
    &mut device.RESETS,
);
let _: Pin<_, FunctionPio0> = pins.gpio22;

This API is something I'm not entirely happy with this PR, but when I tried to implement a better API, I hit a wall with needing thousands of macro-generated trait implementations. I think it makes sense to get this PR merged as is for now as it is fully functional and PIO is such a central piece of what makes RP2040 special. A future API can then improve this API.
Ps. It seems that you are not initializing the clocks either. I suspect that at the boot they are not at 133MHz. See https://github.com/rp-rs/rp-hal/blob/main/boards/pico/examples/pico_blinky.rs#L31

@henkkuli
Does it suffice to just initialize GPIO and the clocks without passing them to the PIO? Or is there something else to do?
I just added this at the top:
// init GPIO for PIO
let sio = hal::sio::Sio::new(pac.SIO);
let pins = pico::Pins::new(
    pac.IO_BANK0,
    pac.PADS_BANK0,
    sio.gpio_bank0,
    &mut pac.RESETS,
);
let _pin22 = pins.gpio22;

// init clocks
let mut watchdog = hal::watchdog::Watchdog::new(pac.WATCHDOG);
let clocks = match hal::clocks::init_clocks_and_plls(
    pico::XOSC_CRYSTAL_FREQ,
    pac.XOSC,
    pac.CLOCKS,
    pac.PLL_SYS,
    pac.PLL_USB,
    &mut pac.RESETS,
    &mut watchdog,
) {
    Ok(c) => c,
    Err(_e) => panic!("clock init failed"),
};
let _system_clock = clocks.system_clock;

@henkkuli
Thanks, I added you suggestions.
The application doesn't panic anymore (I had to add the side set to the assembler). But unfortunately my LEDs don't work.
Is there some way to debug this? Or do you already see what's wrong?
Can you provide me  with your DMX-512 decoder implementation or some other PIO code to compare against?
This is my current code:
#![no_std]
#![no_main]

use embedded_time::fixed_point::FixedPoint;
use hal::clocks::Clock;
use pico::hal::{self, pac};
use pio;

use cortex_m_rt::entry;
use panic_semihosting as _;

#[link_section = ".boot2"]
#[used]
pub static BOOT2: [u8; 256] = rp2040_boot2::BOOT_LOADER;

#[entry]
fn main() -> ! {
    let mut pac = pac::Peripherals::take().unwrap();
    let core = pac::CorePeripherals::take().unwrap();

    // init GPIO for PIO
    let sio = hal::sio::Sio::new(pac.SIO);
    let pins = hal::gpio::Pins::new(
        pac.IO_BANK0,
        pac.PADS_BANK0,
        sio.gpio_bank0,
        &mut pac.RESETS,
    );
    let _pin22: hal::gpio::Pin<_, hal::gpio::FunctionPio0> = pins.gpio22.into_mode();

    // init clocks
    let mut watchdog = hal::watchdog::Watchdog::new(pac.WATCHDOG);
    let clocks = hal::clocks::init_clocks_and_plls(
        pico::XOSC_CRYSTAL_FREQ,
        pac.XOSC,
        pac.CLOCKS,
        pac.PLL_SYS,
        pac.PLL_USB,
        &mut pac.RESETS,
        &mut watchdog,
    )
    .ok()
    .unwrap();
    let _sysclock = core.SYST;
    let clock_freq = clocks.system_clock.freq().integer();

    let side_set = pio::SideSet::new(false, 1, false);

    let mut assembler = pio::Assembler::new_with_side_set(side_set);

    const T1: u8 = 2;
    const T2: u8 = 5;
    const T3: u8 = 3;
    let mut bitloop = assembler.label();
    let mut do_one = assembler.label();
    let mut do_zero = assembler.label();
    //let mut wrap_source = assembler.label();
    //assembler.bind(&mut wrap_target);
    assembler.bind(&mut bitloop);
    assembler.out_with_delay_and_side_set(pio::OutDestination::X, 1, T3 - 1, 0);
    assembler.jmp_with_delay_and_side_set(pio::JmpCondition::XIsZero, &mut do_zero, T1 - 1, 1);
    assembler.bind(&mut do_one);
    assembler.jmp_with_delay_and_side_set(pio::JmpCondition::Always, &mut bitloop, T2 - 1, 1);
    assembler.bind(&mut do_zero);
    // Pseudoinstruction: NOP
    assembler.mov_with_delay_and_side_set(
        pio::MovDestination::Y,
        pio::MovOperation::None,
        pio::MovSource::Y,
        T2 - 1,
        0,
    );

    let program = assembler.assemble(None);

    let pio = hal::pio::PIO::new(pac.PIO0, &mut pac.RESETS);
    let sm = &pio.state_machines()[0];

    let cycles_per_bit = T1 + T2 + T3;
    const FREQ: u32 = 8_000_000;
    let div = clock_freq as f32 / (FREQ as f32 * cycles_per_bit as f32);

    hal::pio::PIOBuilder::default()
        .with_program(&program)
        .buffers(hal::pio::Buffers::OnlyTx)
        .side_set(side_set)
        .side_set_pin_base(22)
        .out_shift_direction(hal::pio::ShiftDirection::Left)
        .autopull(true)
        .pull_threshold(32)
        .clock_divisor(div)
        .build(&pio, sm)
        .unwrap();

    sm.set_enabled(true);

    const NLED: usize = 60;

    let mut data = [0u32; NLED];
    for byte in &mut data {
        *byte = u32::MAX;
    }

    loop {
        for word in data {
            sm.push(word);
        }
        cortex_m::asm::delay(50_000);
        cortex_m::asm::nop();
    }
}

@LU15W1R7H
I added a blink pio example in my fork after pulling @henkkuli changes. I have found debugging pretty challenging as I just make incremental changes from a working state. Maybe the example could get included in this PR?

Follow up on playing around with this PIO hal. I can't seem to get side set to work. I am setting side set mandatory, only using one bit for side set pins, and have the side set base setup. Any ideas with the code below?
@henkkuli Does your DMX protocol use side set? I dumped the two state machine control registers and everything looked correct, the only thing I can think of is the Program defines or origin? A dis-assembler would be nice, haha.
    let side_set = pio::SideSet::new(false, 1, false);
    let mut a = pio::Assembler::new_with_side_set(side_set);
    let mut toggle_loop = a.label();

    a.bind(&mut toggle_loop);
    a.set_with_side_set(pio::SetDestination::PINDIRS, 1, 1);
    a.set_with_side_set(SetDestination::PINS, 1, 1);
    a.set_with_side_set(SetDestination::PINS, 0, 0);

    let program = a.assemble(None);

    let pio = hal::pio::PIO::new(pac.PIO0, &mut resets);
    let sm = &pio.state_machines()[0];

    hal::pio::PIOBuilder::default()
        .with_program(&program)
        .buffers(hal::pio::Buffers::RxTx)
        .out_pins(9, 2)
        .in_pin_base(9)
        .set_pins(9, 2)
        .side_set(side_set)
        .side_set_pin_base(18)
        .clock_divisor(5000 as f32)
        .build(&pio, sm)
        .unwrap();

    sm.set_enabled(true);

Is there a blocking variant of StateMachine::push?
The thing I came up with is: while !sm.write_tx(value), which just retries, until success.
Surely there is a better way of doing this.

It took a bit of head scratching but I got the wb2812 driver working and packaged it here (of course pending this PR merge).

If that can be of interest for this PR, here's some feedback on the troubles I faced:

In the reference implementation the need to setup the pin direction for sideset controlled pin is hidden and relies on the SMn_INSTR to execute the set pindir  ....  I don't know it that's something this API could handle internally. I generally prefer things explicit so it's fine by me if it stays like this.

Even though that'd be just an alias, having a proper nop (and associated) method on the assembler would remove noise in the user's code. Writing the mov(y,none,y) instruction is verbose and distracting.

The rp2040_hal::pio::PIOBuilder::build() does not build anything and do not explicitly say it's enabling the state machine, this may even be something one wants optional?

In rp2040_hal::pio::PIOBuilder::build(), maybe
let mut instr = 0b000_00000_000_00000; // JMP 0
instr |= offset as u16;
sm.set_instruction(instr);

could make use of the tools exposed in the module and be written
let instr = pio::InstructionOperands::JMP {
    condition: pio::JmpCondition::Always,
    address: offset as u8
};
sm.set_instruction(instr.encode());

Finally, the assembler does a lot of (useful) checks that panic if they fail. This makes it a bit hard to debug without rtt or some bigger setup to get those traces out. As far as I understand, failure on any of those induce instability of the system so it would be IMHO better to use Result::Err to report assembly failure rather than panics.

I hope this was useful feedback. I probably won't need PIO anytime soon in my keyboard project but still, let me know if I can of any help.

@ithinuel did you consider using the pio! macro? it allows you to write the text format assembly instead (and includes nop)

I did gave it a quick try but it doesn't work out of the box.
From what I could see, it requires to set the resolver in the root Cargo.toml otherwise it thinks std is required.
I had obscure messages like:
   = help: message: no entry found for key

when using a label that is not defined.
but after fixing the assembly it still fails with
could not find `pio_parser` in the list of imported crates

I pushed this branch if you want to git it a try. (you'll need to set the resolver in your workspace's Cargo.toml).


Issue 12520 - Remove BDX timeout tracking from TransferSession

Problem
Timeout tracking is unnecessary in BDX transfer session because OTA Query Image timeout has already been implemented at the BDX downloader layer via https://github.com/project-chip/connectedhomeip/pull/15768.
Fixes: https://github.com/project-chip/connectedhomeip/issues/12520
Change overview
Remove un-used BDX timeout tracking from TransferSession.
Testing

Verified Query Image succeeds.

Verify BDX timeout is caught if OTA-P is killed during Query Image transfer.

Example:
out/apps/ota-provider/chip-ota-provider-app -f ~/Downloads/test2.ota

out/apps/ota-requestor/chip-ota-requestor-app --discriminator 30 --secured-device-port 5560 --KVS /tmp/chip_kvs_requestor

out/apps/chip-tool/chip-tool otasoftwareupdaterequestor announce-ota-provider 0x00000000ABCD 0 0 0 0x0000001234567890 0

out/apps/chip-tool/chip-tool otasoftwareupdaterequestor subscribe-event download-error 5 10 1 0x1234567890 0

Control-C to kill OTA-P app. Then verify OTA-R logs after ~5 minutes:
[1648515793846] [50344:1212061] CHIP: [BDX] BDX transfer timeout*
[1648515793846] [50344:1212061] CHIP: [BDX] aborting due to timeout
[1648515793846] [50344:1212061] CHIP: [EVL] LogEvent event number: 0x00000000000D0003 priority: 1, endpoint id: 0x0 cluster id: 0x0000_002A event id: 0x2 Sys timestamp: 0x000000001638B06E
[1648515793846] [50344:1212061] CHIP: [DMG] Endpoint 0, Cluster 0x0000_002A update version to 31392a45
[1648515793846] [50344:1212061] CHIP: [EVL] LogEvent event number: 0x00000000000D0004 priority: 1, endpoint id: 0x0 cluster id: 0x0000_002A event id: 0x0 Sys timestamp: 0x000000001638B06E
[1648515793846] [50344:1212061] CHIP: [SWU] Unknown idle state reason so set the periodic timer for a next attempt
[1648515793846] [50344:1212061] CHIP: [SWU] Stopping the watchdog timer
[1648515793846] [50344:1212061] CHIP: [SWU] Starting the periodic query timer, timeout: 86400 seconds

Fast tracking, given this has had enough time for review (> 3 days)


Size of one bit and size of image should be dynamic.

Who dont like dynamic values.

Okay, you can already do that although you need to change bincode.py itself for that. And they arent compatible with each other.


unable to find firebase.js unable to find pi

I have  repeatedly done this part of the tutorial and have followed the instructions to boot The above appears to be an error from your side

#244 appears to fix the pi error.
yet the following error remains

It looks like you are opening the File directly using the browser in the local file path. Instead you need to run firebase serve,  this starts a web server and you can access your project using http://loclahost:5000/

Ah i see :-( my bad
Thanks for your quick reply


Dashboard skeleton

Looks like @KasperGroesLudvigsen and I have done some double work. I guess these can be merged.
Closes https://github.com/Dansk-Data-Science-Community/danish-data-science-salary-survey/issues/2.

@saattrupdan

@saattrupdan


Error in trianing

When I run the train scripts based on UCF101 database, I found the accuracy were always 0.00000. Maybe some error occur to me. What should I do?

I met the same question. Have you solved this problem?

I met the same question. Have you solved this problem?


change GH link swcarpentry > carpentries

There may be other places that we also need to update the GH  name.

Thanks @maneesha!


Trading home page

Lets remove the dummy content on the home page and instead make a simple application road map. It would be great if this could be easily editable perhaps via mdx.

what about this one?
I am working on it and it still needs more review.
Here's a screenshot from what I have locally:

This can probably be closed as dup of #305


CustomEditor extensions should be able to refuse to open a file

Different apps and file formats might use same file extensions or names for their files. Detecting the format by first line does not really work for JSON-based formats files that cannot have shebangs.
When creating extensions for those file formats, the conflicts are inevitable.
Also, sometimes even for a single file format an extension may, by design, only support a subset of the files of this format.
The current experience is that a single custom editor take over all files with some extension or file name. Sure, the use can change the association to another editor, but the problem remains.
I propose to make it possible for an extension to tell VSCode that it cannot edit a certain file. In that case, VSCode should try to open the file in the next best editor (e.g. the default editor).
Implementation options:
Option 1:
Add a file format validation method/hook that is called before the editor is activated for the file and resolveCustomTextEditor is called.
Option 2 (preferred):
Interpret unhandled exception thrown from resolveCustomTextEditor as refusal to open the document.
Option 3:
Interpret certain return value returned from resolveCustomTextEditor as refusal to open the document.

Option 2 example:
public async resolveCustomTextEditor(
  document: vscode.TextDocument,
  webviewPanel: vscode.WebviewPanel,
  _token: vscode.CancellationToken
): Promise<void> {
  if (!hasValidSchema(document.getText())) {
    throw Error("File format is invalid or unsupported by the extension.")
  }
  ...
}

With all options, the VSCode behavior should be to try open the file in the next best editor (e.g. the default editor).

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Add GetPackagesFromOwnerAsync for the TypedManager.

Implement for Npm and PyPI. Can't figure out NuGet easily so it just throws a NotImplementedException.

I think this is fine. I could take a look at the nuget implementation tomorrow if you want to wait for that.

We primarily needed this for npm, so no rush for NuGet. I think this is ok for now.


atom-beautify incorrectly beautifies alias in ruby, contradicting rubocop

Description
The results of beautification are not what I expect.
Input Before Beautification
This is what the code looked like before:
  alias invite_to_join_by! invite!

Expected Output
The beautified code should have looked like this:
  alias invite_to_join_by! invite!

Actual Output
The beautified code actually looked like this:
  alias_method :invite_to_join_by!, :invite!

Steps to Reproduce

Add code to Atom editor
Run command Atom Beautify: Beautify Editor
This beautified code does not look right!

Debug
Here is a link to the debug.md Gist: https://gist.github.com/moskyb/449ce5370c4e9ca1e665c48f122718bd
Checklist
I have:

[x] Tried uninstalling and reinstalling Atom Beautify to ensure it installed properly
[x] Reloaded (or restarted) Atom to ensure it is not a caching issue
[x] Searched through existing Atom Beautify Issues at https://github.com/Glavin001/atom-beautify/issues
so I know this is not a duplicate issue
[x] Filled out the Input, Expected, and Actual sections above or have edited/removed them in a way that fully describes the issue.
[x] Generated debugging information and added link for debug.md Gist to this issue

From your debugging logs:
2017-01-10T01:01:54.557Z - debug: [beautifiers/beautifier.coffee] spawn /Users/bmosky/.rbenv/shims/rubocop 0=--auto-correct, 1=--config, 2=/Users/bmosky/Carnival/carnival-consumers/.rubocop.yml, 3=/tmp/temp117010-860-wj05sx.hetzgjh5mi
2017-01-10T01:01:57.321Z - debug: [beautifiers/beautifier.coffee] spawn done 1 warning: parser/current is loading parser/ruby22, which recognizes
warning: 2.2-compliant syntax, but you are running 2.3.2.
 Inspecting 1 file
C

Offenses:

mp/temp117010-860-wj05sx.hetzgjh5mi:1:1: C: Use snake_case for source file names.
require_dependency 'concerns/devise_mailable'
^
mp/temp117010-860-wj05sx.hetzgjh5mi:104:3: C: [Corrected] Use alias_method instead of alias.
  alias invite_to_join_by! invite!
  ^^^^^

1 file inspected, 2 offenses detected, 1 offense corrected

2017-01-10T01:01:57.321Z - verbose: [beautifiers/beautifier.coffee] spawn result 1 Inspecting 1 file
C

Offenses:

mp/temp117010-860-wj05sx.hetzgjh5mi:1:1: C: Use snake_case for source file names.
require_dependency 'concerns/devise_mailable'
^
mp/temp117010-860-wj05sx.hetzgjh5mi:104:3: C: [Corrected] Use alias_method instead of alias.
  alias invite_to_join_by! invite!
  ^^^^^

1 file inspected, 2 offenses detected, 1 offense corrected
 warning: parser/current is loading parser/ruby22, which recognizes
warning: 2.2-compliant syntax, but you are running 2.3.2.

It looks like Atom-Beautify worked.
If it is an issue with the options Atom-Beautify passes to Rubocop, then https://github.com/Glavin001/atom-beautify/pull/1776 may resolve your issue.
Otherwise, I recommend making an issue over at https://github.com/bbatsov/rubocop

See #1776
Published to v0.32.0


How to run image-alpha to reduce to 32 colors?

Also, how to use the -m command?

Hello, this sets the setting in pngquant – from the docs at https://pngquant.org;
--quality min-max

  Instructs pngquant to use the least amount of colors required to meet or exceed the max quality. If conversion results in quality below the min quality the image won't be saved (if outputting to stdout, 24-bit original will be output) and pngquant will exit with status code 99.

  min and max are numbers in range 0 (worst) to 100 (perfect), similar to JPEG.

  pngquant --quality=65-80 image.png

Hope this helps, thanks.

thanks

I'm trying to reduce a .png with white gradients to transparent into 8 colors but it looks like :
imageoptim --imagealpha --number-of-colors 8 'spritesheet.png'
Does not really reduce it, if I run the GUI imagealpha on the same image after and reduce it inthere to 8 colors I can clearly see the gradients roughening up, indicating it is not yet at 8 colors after running imageoptim on it. Not sure what I'm doing wrong


Faster probable prime generation

Rebases and closes #118.

I've merged in master and commented out the unit test for now, until there's a way to do the unit tests.

I guess I'll do another rebase / merge at a later date then :).

Is this still relevant ?

My understanding is yes, but I won't have the bandwidth to look at this again. Feel free to close unless someone else wants to take ownership.

My understanding is yes, but I won't have the bandwidth to look at this again. Feel free to close unless someone else wants to take ownership.

Closing based on this comment.

My understanding is yes, but I won't have the bandwidth to look at this again. Feel free to close unless someone else wants to take ownership.

Closing based on this comment.


HyperExpress faster then uWebsockets

Hello again. I did benchmarking with simple "Hello, World!" case against HyperExpress and uWebockets. Of course I was expecting HyperExpress being a bit slower than uWebsockets us it is built on top of it and adds some overhead. But after dozens attempts of running both "wrk" and "bombardier" I constantly get HyperExpress being at least 20% faster than uWebsockets. And I want to understand the reason. I guess it can be one of the following reasons

HyperExpress uses other version of uWebsockets that by some reason significantly faster that mine
HyperExpress use some additional optimization
HyperExpress has some small bug that make it faster for simple cases, but may break something in more complex

Anyway I think you can determine it better that anybody else. So I will provide you with all benchmarking info and I think together we can understand the reason.
That is versions:
  "dependencies": {
    "hyper-express": "^6.15.2",
    "uWebSockets.js": "github:uNetworking/uWebSockets.js#v20.43.0"
  }

That is code of the scripts :
Pure uWebsockets
const uWebsockets = require("uWebSockets.js")
const PORT = 8080

const app = uWebsockets.App()

app.get("/uwebsocket", (response, request) => {
    response.end("Hello, World!")
})

app.listen(PORT, listenSocket => {
    if (listenSocket) {
        console.log(`Server is running in ${PORT}`)
    } else {
        console.log("Server could not start")
        process.exit(-1)
    }
})

HyperExpress
const HyperExpress = require("hyper-express")
const PORT = 8080

const server = new HyperExpress.Server()

server.get("/hyper", (request, response) => {
    response.send("Hello, World!")
})

server.listen(8080).then(_ => {
    console.log(`Server is running on ${PORT}`)
}).catch(_ => {
    console.log("Server could not start")
})

And before I provide benchmarking results also some notes:

Machine is Macbook Pro M1 (16 GB)
wrk is latest version
Node version is v20.10.0
I provide only results of wrk but the proportion of the results is the same for bombardier - (HyperExpress faster)
I provide only 5 runs for both servers, but during last days I did dozens of runs and the magnitude always the same.
There are always 60-70 socket read erros, but I think it something related to wrk as for bombardier all responses are 200.

And below is results:
uWebsockets
~ % wrk -c200 -t6 -d30s http://localhost:8080/uwebsocket
Running 30s test @ http://localhost:8080/uwebsocket
  6 threads and 200 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     2.18ms  533.37us  12.06ms   79.37%
    Req/Sec    15.14k     3.33k  150.69k    98.95%
  2713453 requests in 30.10s, 274.30MB read
  Socket errors: connect 0, read 66, write 0, timeout 0
Requests/sec:  90139.69
Transfer/sec:      9.11MB

~ % wrk -c200 -t6 -d30s http://localhost:8080/uwebsocket
Running 30s test @ http://localhost:8080/uwebsocket
  6 threads and 200 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     2.19ms  520.80us  14.02ms   78.11%
    Req/Sec    15.07k   766.28    20.72k    84.38%
  2706818 requests in 30.10s, 273.63MB read
  Socket errors: connect 0, read 67, write 0, timeout 0
Requests/sec:  89915.35
Transfer/sec:      9.09MB

~ % wrk -c200 -t6 -d30s http://localhost:8080/uwebsocket
Running 30s test @ http://localhost:8080/uwebsocket
  6 threads and 200 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     2.18ms  509.15us  12.24ms   78.40%
    Req/Sec    15.14k   698.19    20.50k    83.83%
  2720889 requests in 30.10s, 275.05MB read
  Socket errors: connect 0, read 65, write 0, timeout 0
Requests/sec:  90382.59
Transfer/sec:      9.14MB

~ % wrk -c200 -t6 -d30s http://localhost:8080/uwebsocket
Running 30s test @ http://localhost:8080/uwebsocket
  6 threads and 200 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     2.20ms  516.99us  13.22ms   79.11%
    Req/Sec    15.03k     1.01k   25.28k    90.53%
  2701558 requests in 30.10s, 273.10MB read
  Socket errors: connect 0, read 66, write 0, timeout 0
Requests/sec:  89742.12
Transfer/sec:      9.07MB

~ % wrk -c200 -t6 -d30s http://localhost:8080/uwebsocket
Running 30s test @ http://localhost:8080/uwebsocket
  6 threads and 200 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     2.19ms  518.38us  11.17ms   78.20%
    Req/Sec    15.11k   642.54    19.43k    79.96%
  2715818 requests in 30.10s, 274.54MB read
  Socket errors: connect 0, read 64, write 0, timeout 0
Requests/sec:  90215.96
Transfer/sec:      9.12MB

HyperExpress
 ~ % wrk -c200 -t6 -d30s http://localhost:8080/hyper
Running 30s test @ http://localhost:8080/hyper
  6 threads and 200 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     1.54ms  362.06us  11.94ms   63.11%
    Req/Sec    21.47k     3.22k   33.73k    86.82%
  3857715 requests in 30.10s, 327.43MB read
  Socket errors: connect 0, read 66, write 0, timeout 0
Requests/sec: 128145.99
Transfer/sec:     10.88MB

~ % wrk -c200 -t6 -d30s http://localhost:8080/hyper
Running 30s test @ http://localhost:8080/hyper
  6 threads and 200 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     1.31ms  371.49us  10.10ms   78.97%
    Req/Sec    25.14k     1.86k   46.43k    75.98%
  4510496 requests in 30.10s, 382.84MB read
  Socket errors: connect 0, read 66, write 0, timeout 0
Requests/sec: 149831.65
Transfer/sec:     12.72MB

~ % wrk -c200 -t6 -d30s http://localhost:8080/hyper
Running 30s test @ http://localhost:8080/hyper
  6 threads and 200 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     1.57ms  353.37us  10.85ms   70.03%
    Req/Sec    20.99k     2.93k   33.68k    88.78%
  3759839 requests in 30.00s, 319.12MB read
  Socket errors: connect 0, read 64, write 0, timeout 0
Requests/sec: 125311.52
Transfer/sec:     10.64MB

 ~ % wrk -c200 -t6 -d30s http://localhost:8080/hyper
Running 30s test @ http://localhost:8080/hyper
  6 threads and 200 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     1.57ms  340.61us  14.05ms   67.55%
    Req/Sec    20.97k     2.17k   34.83k    83.76%
  3764742 requests in 30.10s, 319.54MB read
  Socket errors: connect 0, read 63, write 0, timeout 0
Requests/sec: 125065.22
Transfer/sec:     10.62MB

 ~ % wrk -c200 -t6 -d30s http://localhost:8080/hyper
Running 30s test @ http://localhost:8080/hyper
  6 threads and 200 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     1.61ms  354.54us  11.29ms   75.93%
    Req/Sec    20.50k     4.98k  205.15k    94.95%
  3673264 requests in 30.10s, 311.78MB read
  Socket errors: connect 0, read 66, write 0, timeout 0
Requests/sec: 122025.33
Transfer/sec:     10.36MB

And also small note that I tried, in the HyperExpress,  to use response.end instead of response.send but the result is the same.

Hey, something is definitely off because HyperExpress should have a 10% - 15% overhead in pure GET performance alone.
This is a stable benchmark to refer to https://web-frameworks-benchmark.netlify.app/result?l=javascript for your debugging purposes.

hyper in your URL is shorter than uwebsocket, try using the same URL, because it affects the request size.


feat(cargo): change conditional callback function

Checks for existence of Cargo.toml in parent directories rather than just opts.dir. This allows the user to be editing any file in a Rust project and use cargo commands from Overseer. Fixes #24. Let me know if anything else needs to be changed!

LGTM, thanks!


[BUG]

The plugin was installed and the settings were saved successfully.
Also importing Github repos is working properly.
✅ Expected Behavior
When trying to click the Github icon to upload and push the new version it should work as expected
❌ Actual Behavior
Unfortunately the loading indicator freezes and nothing happens (see attached image)
📸 Screenshots

🔍 Environment Details

Chrome Version: 131.0.6778.205 (Officiell version)
Extension Version: 1.1.0
Operating System: MacOs Sonoma 14.5
Bolt.new Project Type: React Web app

💾 Additional Context

Did this work before?
Are you using any specific GitHub organization/repository settings?
Any error messages in the Chrome DevTools console? (Press F12 to open)

✔ Checklist

[ x ] I am on bolt.new website when trying to use the extension
[ x ] I have provided my GitHub token with correct permissions
[ x ] I have the latest version of the extension installed
[ x ] I have checked the extension popup for any error messages

Thanks, @Webylon, for creating an issue. This issue has been resolved in version 1.1.1, which is under review in the Chrome Web Store, submitted on Dec 20, 2024. But this repo already has the latest version. You can try to install the extension manually by loading the latest release zip file. Thanks!
Note: I'm keeping this issue open until version 1.1.1 is Published in CWS.

Thanks, @Webylon, for creating an issue. This issue has been resolved in version 1.1.1, which is under review in the Chrome Web Store, submitted on Dec 20, 2024. But this repo already has the latest version. You can try to install the extension manually by loading the latest release zip file. Thanks!
Note: I'm keeping this issue open until version 1.1.1 is Published in CWS.

@mamertofabian Got it, looking forward to trying out the latest version thank you!

@mamertofabian Will the extension work if I set my project to Private?

@Webylon The latest version has been approved. I'm closing this issue now. Thanks for your patience.

@mamertofabian Will the extension work if I set my project to Private?

@Webylon Yes, pushing to Github will work. Though you won't be able to load from GitHub to Bolt.

@mamertofabian Ok, just updated to the latest version and will try it out thank you!


Allow 1.x and 2.x of "cweagans/composer-patches".

This pull request is for: (mark with an "x")

[ ] modules/next

GitHub Issue: #704
Please add a link to the GitHub issue
where this problem is discussed.

[ ] I need help adding tests. (mark with an "x")
Code changes need test coverage. If you don't know
how to make tests, check this box to ask for help.

Describe your changes
Allow "cweagans/composer-patches" both versions i.e. 1.x and 2.x.

Yes, we can update "cweagans/composer-patches": "~2.0".

Yes, we can update "cweagans/composer-patches": "~2.0".

That's not what I requested. Removing the composer-patches requirement from the Next module will allow support for all versions of composer-patches from any project that requires Next module.

That make more sense to me and that will be great, thank you.

Considering your availability, can we anticipate the release on Drupal.org in a couple of weeks. Thank you!

@JohnAlbin can get this released on Drupal.org, thank you!

@JohnAlbin can get this released on Drupal.org, thank you!

+1

@rajeshreeputra @vishalkhode1 It's been on Drupal.org since March 12. https://www.drupal.org/project/next/releases/2.x-dev
Also, a new alpha or beta release will be made in the next couple weeks.


Defining the Main objectives of system #SoftwareDesign (Mustafa BERKAY - 010517 - PDM)

The Main Objectives of the System.pdf


[Bug] LED light entity wrong after device reboot

The problem
After the router goes through a reboot, LEDs are back on, but the status is still reported as off
This should be handled somehow
Your device model
RT-AX88U
Firmware type
Merlin
Firmware version
<IP_ADDRESS>.386.5_2
Integration version with the issue
0.4.0
Method of the integration installation
HACS
What version and type of Home Assistant installation do you use
Core 2022.6.4
Is there anything useful in the logs?
No response
Diagnostics information
No response
Additional information
No response

Confirmed to be only Merlin-related.
RT-AX88U with the stock FW doesn't have such a problem. With Merlin - does

This is an FW-related issue, not integration related. Since it cannot be fixed from my side, it will be closed.


secure admin api

how to secure kong's admin api (8001) if someone got access to the server where kong is installed?

Please see all the related issues and questions asked on this topic:
#668 #898 #1593


Performance Timing Interface Returning unexpected values

My elation at the advent of the W3C performance timing interface being included in phantomJS was short-lived.  I fired up a simple test to evaluate some timings and was greeted with partial failure.
What I see is all of the timing events up to responseStart being equal to the navigationStart (with the exception of redirect & SSL, I didn't take time to find a page with those events).
It seems like the actual request is being initiated before the timing object is created (that is purely speculation).
I'm attaching a simple script to illustrate the offending behavior.  The test URL was chosen as a control on the other side of the world (I'm in Ohio) that would ensure network latency.
I'm including both the output I get from my phantomJS script and the console in Chrome when I visit the same site.
Chrome Output
TTFB:1793 startRender:3278
VM179:18 0      secureConnectionStart
VM179:18 0      unloadEventStart
VM179:18 0      unloadEventEnd
VM179:18 0      redirectStart
VM179:18 0      redirectEnd
VM179:18<PHONE_NUMBER>218      navigationStart
VM179:18<PHONE_NUMBER>618      fetchStart
VM179:18<PHONE_NUMBER>622      domainLookupStart
VM179:18<PHONE_NUMBER>624      domainLookupEnd
VM179:18<PHONE_NUMBER>624      connectStart
VM179:18<PHONE_NUMBER>625      requestStart
VM179:18<PHONE_NUMBER>625      connectEnd
VM179:18<PHONE_NUMBER>011      responseStart
VM179:18<PHONE_NUMBER>013      responseEnd
VM179:18<PHONE_NUMBER>013      domLoading
VM179:18<PHONE_NUMBER>408      domInteractive
VM179:18<PHONE_NUMBER>408      domContentLoadedEventStart
VM179:18<PHONE_NUMBER>496      domContentLoadedEventEnd
VM179:18<PHONE_NUMBER>505      domComplete
VM179:18<PHONE_NUMBER>509      loadEventStart
VM179:18<PHONE_NUMBER>509      loadEventEnd

PhantomJS Output
Status: success
1426776521252
TTFB:0 startRender:174
0       redirectEnd
0       redirectStart
0       secureConnectionStart
0       unloadEventEnd
0       unloadEventStart
1426776521253       connectEnd
1426776521253       connectStart
1426776521253       domainLookupEnd
1426776521253       domainLookupStart
1426776521253       fetchStart
1426776521253       navigationStart
1426776521253       requestStart
1426776521253       responseStart
1426776521404       domLoading
1426776521426       responseEnd
1426776521427       domContentLoadedEventEnd
1426776521427       domContentLoadedEventStart
1426776521427       domInteractive
1426776521637       domComplete
1426776521637       loadEventStart
1426776521638       loadEventEnd

Script to recreate: wptDefect.js

var testURL='http://www.vilnius-tourism.lt/en/tourism';

var page = require('webpage').create();
var st = Date.now();
page.open(testURL, function(status) {
  console.log("Status: " + status);
  if(status === "success") {
    console.log(st);
    setTimeout(function(){
      // To unequivocally ensure that the page has finished.
      page.render('example.png');
      getMetrics(page);
      phantom.exit();
    },2000);
  }
});

function getMetrics(page) {
    var wpt=page.evaluate(function(){
        return window.performance.timing;
    });

    var ns=wpt.navigationStart;
    var ttfb=wpt.responseStart-ns;
    var sr=wpt.domContentLoadedEventEnd-ns;
    console.log('TTFB:'+ttfb+' startRender:'+sr);

      var metrics=[];

      for(var i=0;i<Object.keys(wpt).length;i++){
        val={};
        val.key=Object.keys(wpt)[i];
        val.value=wpt[val.key];
        metrics.push(val);
      }

  metrics.sort(function(a,b){
    return a.value-b.value;
  });
  metrics.forEach(function(d){console.log(d.value+'\t\t'+d.key);});
}

I had the similar issues...

We've now tried on a number of instance types and platforms - all with consistent results.
OSX, Ubuntu, Windows both from our local machines, servers in our datacenter, and cloud.
Universally, it appears navigationStart is being set in an unusual way.  I've again tried to look at the code, but have been unsuccessful parsing the content - my areas of familiarity/expertise are python & JS.

Hello.
For what it is worth, this is my test of your script executed from Copenhagen, Denmark (closer to Vilnius than Ohio :-))
Actually it looks like Chrome and PJS is reasonably equal. Very strange/interesting
PhantomJs <IP_ADDRESS> on Windows 7 prof + SP1 over 8/1 Mbit ADSL line
(no caching which is default)
Status: success
1431678557170
TTFB:1036 startRender:2104
0               secureConnectionStart
0               unloadEventEnd
0               unloadEventStart
1431678557172           navigationStart
1431678557172           redirectStart
1431678558208           connectEnd
1431678558208           connectStart
1431678558208           domainLookupEnd
1431678558208           domainLookupStart
1431678558208           fetchStart
1431678558208           redirectEnd
1431678558208           requestStart
1431678558208           responseStart
1431678558386           domLoading
1431678558412           responseEnd
1431678559227           domContentLoadedEventStart
1431678559227           domInteractive
1431678559276           domContentLoadedEventEnd
1431678567352           domComplete
1431678567353           loadEventStart
1431678567355           loadEventEnd
Chrome 42.0.2311.135 m
(caching disabled in F12, network)
TTFB:1112 startRender:1931
0		secureConnectionStart
0		unloadEventStart
0		unloadEventEnd
1431679552269		navigationStart
1431679552503		redirectStart
1431679553214		connectStart
1431679553214		fetchStart
1431679553214		domainLookupStart
1431679553214		domainLookupEnd
1431679553214		connectEnd
1431679553214		redirectEnd
1431679553218		requestStart
1431679553381		responseStart
1431679553387		domLoading
1431679553387		responseEnd
1431679554151		domContentLoadedEventStart
1431679554151		domInteractive
1431679554200		domContentLoadedEventEnd
1431679564194		loadEventStart
1431679564194		domComplete
1431679564197		loadEventEnd
I hope this can help in investigating this issue.
/Jan

Now I got curious.
I did a "resverse" test from Copenhagen towards http://consumer.discoverohio.com/ and this shows:
Chrome:  ttfb: 151, startRender: 2417
PJS:  ttfb: 0, startRender: 2082
More or less the same picture as Bens experience from Ohio->Vilnius. (all timings up to responseStart are identical)
/Jan

I just tried a fresh AWS image - us-west Oregon,  ubuntu 14.04, m3.2xl, followed the build instructions and tried running (looks like the current version is 2.0.1-development).
On my first hit, I got a non-zero TTFB - it was 2855.  Second try was 1020.
However, when I tried hitting the suggested "http:/consumer.discoverohio.com" it was zero TTFB.  When I try hitting something popular like http://baidu.com, i get the same results as above.
It's possible that there is some caching external to the instance that's taking place, but I would still expect some of the other intermediate metrics to be non-zero.

@benhastings  @JanHans1 hello!
is it type phantomjs wptDefect.js in shell?
I got a  wrong message .
➜  test git:(master) ✗ phantomjs wptDefect.js
Status: success
1450339307193
TypeError: 'undefined' is not an object (evaluating 'window.performance.timing')

  phantomjs://webpage.evaluate():2
  phantomjs://webpage.evaluate():3
  phantomjs://webpage.evaluate():3
TypeError: 'null' is not an object (evaluating 'wpt.navigationStart')

  wptDefect.js:23 in getMetrics
  wptDefect.js:12

@benhastings  @JanHans1 hello!
is it type phantomjs wptDefect.js in shell?
I got a  wrong message .
➜  test git:(master) ✗ phantomjs wptDefect.js
Status: success
1450339307193
TypeError: 'undefined' is not an object (evaluating 'window.performance.timing')

  phantomjs://webpage.evaluate():2
  phantomjs://webpage.evaluate():3
  phantomjs://webpage.evaluate():3
TypeError: 'null' is not an object (evaluating 'wpt.navigationStart')

  wptDefect.js:23 in getMetrics
  wptDefect.js:12

Yes @fromIRIS - the defect was evident when running from a shell.
I was just given a windows machine a few weeks ago and it seems to be working (as mentioned above).  I'm trying to fire up another ubuntu image and run it there.  My hope was to use remote hosts for periodic performance monitoring.

thanks! you mean you can run this method in windows machine? i will try it.  but in my mac os,i tried to run phantomjs wptDefect.js in shell. BUT i can not  get window.performance.timing when run page.evaluate. as you can see above TypeError: 'undefined' is not an object (evaluating 'window.performance.timing')  do you know why? @benhastings

now，I had the similar issues，i tried to test a web dns lookuptime,and i use chrome and phantomjs test it
why chrome domainlookupEnd-domainlookupStart not equal phantomjs ？
AND phantomjs domainlookupEnd-domainlookupStart always get 0
like your ex:
chrome:
VM179:18<PHONE_NUMBER>622      domainLookupStart
VM179:18<PHONE_NUMBER>624      domainLookupEnd
phantomjs:
1426776521253       domainLookupEnd
1426776521253       domainLookupStart
can you give any suggestion?
THX

With PhantomJS I usually have a TTFB of 0 milliseconds. Which is probably not true. With Google Chrome and chromedriver 2.38 I get more realistic values.


[HUDI-8232] Adding Index defn for Col stats to track the list of columns indexed

Change Logs

Adding Index defn for Col stats to track the list of columns indexed. This will be later leveraged during pruning to only lookup in col stats partition for indexed cols (HUDI-8663)

Impact

Adding Index defn for Col stats to track the list of columns indexed. This will be later leveraged during pruning to only lookup in col stats partition for indexed cols (HUDI-8663)

Risk level (write none, low medium or high below)
low
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change. If not, put "none".

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@codope : as suggested, we could avoid table services updating the list of cols to update. Those are not allowed to change.

@codope : Patch is ready for review. Addressed all comments.


SK-334 Updated README for column grouping support

Signed-off-by: skyflow-srivyshnavi<EMAIL_ADDRESS>

Approved by Joe, and Manny Silva. @Shaik-Luqmaan @saketh-skyflow


Snippets Are Not Rendering Anymore

The GIF above exemplifies the issue. Notice when it injects the code Bar(x: {{1:Int}}, y: {{2: String}}) that VSCode is not treating the arguments as tab stops.
It used to do this. This might have regressed Adopt SnippetString API. Though as far as I can tell we do this already.
My best guess right now is that the LSP defines a property insertTextFormat which is of type InsertTextFormat. Currently this implementation of the LSP has no such property or type. I do not remember that being there when I originally implemented this.
Current CompletionItem Sent
Content-Type: application/vscode-jsonrpc; charset=utf8
Content-Length: 161

{"id":10,"result":[{"label":"(x: Int, y: String)","kind":4,"detail":"bar.Bar (x: Int, y: String)","insertText":"x: {{1:Int}}, y: {{2:String}}"}],"jsonrpc":"2.0"}

Content-Type: application/vscode-jsonrpc; charset=utf8
Content-Length: 312

{"id":2,"result":[{"label":"(x: Int, y: String)","kind":4,"detail":"bar.Bar (x: Int, y: String)","insertTextFormat":2,"insertText":"x: {{1:Int}}, y: {{2:String}}","textEdit":{"range":{"start":{"character":12,"line":3},"end":{"character":12,"line":3}},"newText":"x: {{1:Int}}, y: {{2:String}}"}}],"jsonrpc":"2.0"}

Still does not work. 🤔


[VL] Remove unnecessary vanilla Spark compatibility code for VeloxCollectSet function

Following https://github.com/apache/incubator-gluten/pull/7451
Since https://github.com/facebookincubator/velox/pull/10737 was merged to Velox, the previous code for aligning Velox's collect_set with vanilla Spark's semantic in query planner is not needed now. Removing them.

@rui-mo @beliefer


Remove README instructions about setting EXISTING_{FOLDER,FILE}_ID

Users no longer need to set this values in BaseDemoActivity.java in the Demos app to test this sample. The use of these values was removed in an earlier app update.

I signed it!


Update package.json v 0.19.2 + Badges Devra 2016 and Chapeau 2016

Please don't update the version in package.json, this is handled at publish time, but whomever is publishing the package.


API-1835: libraryapplyconfiguration: require controllerInstanceName

requires: https://github.com/openshift/library-go/pull/1868

/hold
I need to expose the new method on the controllers before we can merge it.

/hold cancel

/lgtm


Fix MV rewrite error with constant predicate

What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] others

Which issues of this PR fixes ：

Fixes #3053
Problem Summary(Required) ：

When predicate is constant, the check is error

run starrocks_fe_unittest


Remove local span and exit span OP name register permanently

Today, there are endpoint register happens for entry, exit and local span, but we don’t need exit and local span OP names in 99% cases. We should remove it.
The only two scenarios is

Segment query including endpoint id for endpoint dashboard page, but that page only shows entry span as endpoint, so it is safe to keep the column empty
Endpoint dependency in ref header dependency analysis in the backend. Let’s ignore the scenario of end parent endpoint is local or entry. Treat it as none, and don’t generate it as endpoint relation in the OAP side.

@kezhenxu94 Would you want to do this? Or I should run this removal.

Local and exit register caused too much loads to the storage and waste a lot of endpoint ID for nothing. And entry span is the one could be used for metrics, endpoint dependency, and waste more time to finish register(because more ID required register).
So, from all perspectives, this mechanism should be removed. Actually, this should be removed earlier, but I forgot to propose this.


Fix(config): mask variables

Pull request related to this trello task
In order for the test to past variables have to be set elsewhere since the defaults have been removed from the file

This PR breaks the unit tests. This may be due to a difference between windows and Ubuntu OSs. This library should target Ubuntu as that is the target of all PSF libraries.
When I run npm test I get this error:
TypeError: Cannot read property 'slice' of undefined
    at BinTools.validateChecksum (/home/trout/work/psf/code/slp-avax-bridge/node_modules/avalanche/dist/utils/bintools.js:195:37)
    at BinTools.cb58Decode (/home/trout/work/psf/code/slp-avax-bridge/node_modules/avalanche/dist/utils/bintools.js:221:22)
    at Object.<anonymous> (/home/trout/work/psf/code/slp-avax-bridge/test/unit/mocks/avax-mocks.js:12:26)
    at Module._compile (internal/modules/cjs/loader.js:1063:30)
...

The issue seems to stem from this line which seems to fix an issue on Windows OS?
config[key] = config[key].trim()
If I comment out that line, I get additional errors that prevent the unit tests from running.
I believe you have access to an Ubuntu VM on your computer? If not, you can use the Ubuntu VM that runs our test AVAX node.
Please update this PR so that npm test works on an Ubuntu machine. Make any changes you need to also make it work on Windows, but running on Ubuntu is the priority.

I added a handler for the trim method call in the config instance, it shouldn't throw an error now. And now the unit test run on some mock configuration data that has been set up.

:tada: This PR is included in version 1.5.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


No entry found for key error in getting started Tutorial

Bug description
I am new to prisma and trying to use it with a brand new vanilla nest.js project. I followed the steps in the tutorial at this link
https://www.prisma.io/docs/getting-started/setup-prisma/add-to-existing-project
After creating the data tables using the scripts in the tutorial and verifying that the tables are created correctly, I tried to run the npx prisma db pull command to create the schemas. The script returns the following error.
× Introspecting based on datasource defined in prisma\schema.prisma
Oops, an unexpected error occured!
[libs\sql-schema-describer\src\postgres.rs:1039:28] no entry found for key
Please help us improve Prisma by submitting an error report.
Error reports never contain personal or other sensitive information.
Learn more: https://pris.ly/d/telemetry
How to reproduce

Create a new nest.js project using nest cli
Follow the tutorial at this page https://www.prisma.io/docs/getting-started/setup-prisma/add-to-existing-project

Expected behavior
Expected the command to generate schemas as per the tutorial
Prisma information

PS C:\Users\bhavi\Dev\nodejs\b2bapp_ui> npx prisma db pull
Prisma schema loaded from prisma\schema.prisma
Environment variables loaded from .env
Datasource "db": PostgreSQL database "defaultdb", schema "public" at "xxxx:25060"
× Introspecting based on datasource defined in prisma\schema.prisma
Oops, an unexpected error occured!
[libs\sql-schema-describer\src\postgres.rs:1039:28] no entry found for key
Environment & setup

OS: Windows 11
Database: PostgreSQL
Node.js version: 16.15.0

Prisma Version
Environment variables loaded from .env
prisma                  : 3.14.0
@prisma/client          : Not found
Current platform        : windows
Query Engine (Node-API) : libquery-engine 2b0c12756921c891fec4f68d9444e18c7d5d4a6a (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli 2b0c12756921c891fec4f68d9444e18c7d5d4a6a (at<EMAIL_ADDRESS>Introspection Engine    : introspection-core 2b0c12756921c891fec4f68d9444e18c7d5d4a6a (at<EMAIL_ADDRESS>Format Binary           : prisma-fmt 2b0c12756921c891fec4f68d9444e18c7d5d4a6a (at<EMAIL_ADDRESS>Default Engines Hash    : 2b0c12756921c891fec4f68d9444e18c7d5d4a6a
Studio                  : 0.460.0

Sorry for the false alarm. It was a permissions issue...Though the error could have been better.


The wallet connect confirmation is unable to be shown after opening the app from the browser

Describe the bug
Version test: v1.1.0(215)
Device test: IP 11
To reproduce the bug
Steps:

Perform sign transactions continuously used Wallet connect
Observe the displayed screen
Close app and re-open

Actual: https://bit.ly/46g05Wm
In step 2: Do not show confirmation modal
In step 3: Show the confirmation modal
Expect: Show confirmation after the request

@Quangdm-cdm Please re-check bug overlap modal

[ ] The confirmation isn't displayed when open scan QR screen
Steps:

Open Scan QR screen
Perform sign with wallet connect
Observe the displayed screen

Actual: The confirmation isn't displayed
https://konistudio-my.sharepoint.com/:v:/g/personal/nhungphung_koni_studio/EfLIvWI0xddPmksgohZl90ABGYgH66Bg746Gyi9oTi8COA?nav=eyJyZWZlcnJhbEluZm8iOnsicmVmZXJyYWxBcHAiOiJPbmVEcml2ZUZvckJ1c2luZXNzIiwicmVmZXJyYWxBcHBQbGF0Zm9ybSI6IldlYiIsInJlZmVycmFsTW9kZSI6InZpZXciLCJyZWZlcnJhbFZpZXciOiJNeUZpbGVzTGlua0RpcmVjdCJ9fQ&e=yh3ymu

@Quangdm-cdm Please re-check bug overlap modal

[x]  The confirmation isn't displayed when open scan QR screen
Steps:

Open Scan QR screen
Perform sign with wallet connect
Observe the displayed screen

Actual: The confirmation isn't displayed https://konistudio-my.sharepoint.com/✌/g/personal/nhungphung_koni_studio/EfLIvWI0xddPmksgohZl90ABGYgH66Bg746Gyi9oTi8COA?nav=eyJyZWZlcnJhbEluZm8iOnsicmVmZXJyYWxBcHAiOiJPbmVEcml2ZUZvckJ1c2luZXNzIiwicmVmZXJyYWxBcHBQbGF0Zm9ybSI6IldlYiIsInJlZmVycmFsTW9kZSI6InZpZXciLCJyZWZlcnJhbFZpZXciOiJNeUZpbGVzTGlua0RpcmVjdCJ9fQ&e=yh3ymu

Version test: https://file.cdmteck.com/s/DB9JLAnjJczopcC/download?path=%2F&files=SubWalletMobile-build-224-1080-merge-2023-10-16T07-25-48.ipa
Device test: IP 11
Validation passed.


bedtools intersect using sorted bed files - produces a failed (out of sort order) file

This is the role of the -sortout option, and as @jmarshall indicates, if you tell bedtools that your input is sorted (-sorted), then it uses a different algorithm that will not suffer from this.  One could argue, however, that the default behavior should be to always enforce sorted output.  Let me think about this and am open to discussion if you have firm opinions.


Adding MoveIt2 #include's stop VS Code Intellisense from working

Description
Adding MoveIt2 #include-line(s) to C++ project stops VS Code IntelliSense from working.

#include <moveit/move_group_interface/move_group_interface.h>
or
#include <moveit/move_group/move_group_capability.h>

Adding other libraries or #include <moveit/move_group/capability_names.h> does not break functionality.
Your environment

ROS Distro: Iron
OS Version: Ubuntu 22.04
Binary build
ros-iron-moveit 2.8.0-1jammy.20240815.154016 amd64
Default RMW

Steps to reproduce
After having set up VS Code with proper extensions (c/c++, ros, cmake etc), I can confirm IntelliSense is working both with error squiggles and autocomplete for a test c++-file.

#include <cstdio>
#include <rclcpp/rclcpp.hpp>

int main(int argc, char ** argv)
{
  (void) argc;
  (void) argv;
  rclcpp::init(argc, argv);
auto const node = std::make_shared<rclcpp::Node>(
    "hello_moveit",
    rclcpp::NodeOptions().automatically_declare_parameters_from_overrides(true)
  );

  auto const logger = rclcpp::get_logger("hello_moveit");

  // Next step goes here

  // Shutdown ROS
  rclcpp::shutdown();

  printf("hello world hello_moveit package\n");
  return 0;
}

As soon as I add #include for movit (from tutorial)
#include <moveit/move_group_interface/move_group_interface.h>
IntelliSense stops working completely. I get no include errors. Compiles ok with colcon.

Expected behaviour
I would expect IntelliSense to keep working, and allow me error squiggles and autocompletion for objects from the MoveIt-library as well as all others.
Actual behaviour
No errors are shown, nothing is autocompleted anymore until I remove the include.
Backtrace or Console output
Same thing happens even if moveit-#include is included from another header-file (hello_moveit.h)
I can autocomplete stuff from stdio, but if I add #include "hello_moveit.h" (which includes move_group_interface.h), IntelliSense stops again.

With move_group/capability_names.h it works, this would suggest that library include paths are ok.

Any ideas?

This seems to be a bug in VS Code, not MoveIt. I guess, including moveit/move_group_interface/move_group_interface.h just requires Code to perform analysis of this code, which takes a while. During this time, IntelliSense is not available?
For me, IntelliSense works in the MoveIt code base.

Hi @rhaschke, you are probably right, closing this. :)


Does personality insight API support simplified Chinese?

Hi there, I'm trying use personality insight API to get personality and value scores from social media posts in simplified Chinese. I find there do support Chinese in the API document, but I get the error when I doing so. Error info is {"code":400,"sub_code":"C00001","error":"The language you requested, zh-cn, is not supported. Languages supported: en,es,ja,ar,ko."}. Can anyone figure this out? If so, what is the code? THX!

Please see issue https://github.com/ibm-cloud-docs/personality-insights/issues/88.


Combine recipe property and ingredient based search

I think it would overcomplicate the search, so it will stay separate.


fix(chat): update emoji picker

What this PR does 📖

Remove duplicate emoji counter that already existed in UIStore
Make skintone selection persistent

Which issue(s) this PR fixes 🔨

Resolve #614

@Flemmli97 There is one automated test currently failing on your branch because the Frequently Used emojis have 5 now by default and therefore the count of emojis frequently used test is not matching with the current expectation from the tests. I have a PR to update the tests in case your pr is merged - https://github.com/Satellite-im/automated-tests-web/pull/179

@Flemmli97 There is one automated test currently failing on your branch because the Frequently Used emojis have 5 now by default and therefore the count of emojis frequently used test is not matching with the current expectation from the tests. I have a PR to update the tests in case your pr is merged - Satellite-im/automated-tests-web#179

ye we kinda duplicated the stuff there. we already had a "freq used" data saved (emoji counter)

Sara and I did some testing together and we both had the same behavior we select skin tone but it is not applied to selected emoji.
We tested this on Chrome, Brave, Safari and Opera
Screen.Recording.2024-10-10.at.1.18.50.PM.mov

those emoji do not have skin colors. scroll down a bit


Deploy doesn't quite work

The git push from travis doesn't quite work yet. See https://travis-ci.org/Code4SA/opengazettes/builds/153182774
Deploying to GitHub
Agent pid 4935
Identity added: deploy_key (deploy_key)
[detached HEAD 2ede05a] Updated index via TravisCI [ci skip]
 1 file changed, 1 insertion(+), 1 deletion(-)
warning: push.default is unset; its implicit value is changing in
Git 2.0 from 'matching' to 'simple'. To squelch this message
and maintain the current behavior after the default changes, use:
  git config --global push.default matching
To squelch this message and adopt the new behavior now, use:
  git config --global push.default simple
See 'git help config' and search for 'push.default' for further information.
(the 'simple' mode was introduced in Git 1.7.11. Use the similar mode
'current' instead of 'simple' if you sometimes use older versions of Git)
Warning: Permanently added the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts.
Everything up-to-date

fixed in f0b3770b9af8ab31447f3440e214b395c2368c37


support both OpenLDAP and ActiveDirectory

substitute passport-activedirectory with passport-ldapauth package  support both openldap and activedirectory

the node package comes from passport-ldapauth

Also you should be able to test OpenLDAP by testing with credentials similar to this
LDAP_HOST=ldap.forumsys.com
LDAP_PORT=389
LDAP_METHOD=plain
LDAP_BASE_DN=dc=example,dc=com
SQLPAD_LDAP_SEARCH_FILTER="(uid={{username}})"
LDAP_BIND_DN=
LDAP_BIND_PASSWORD=
see https://www.forumsys.com/tutorials/integration-how-to/ldap/online-ldap-test-server/

@eladeyal-intel I have tested successfully with the ldap. forumsys.com LDAP Server using their credentials.

Great! Thanks


Internal Server with transform query decoration

Is the transform query decorator broken?
It returns 500 Internal Server Error both in my local installation (docker grlc:latest connected with a blazegraph sparql endpoint) and in the the official example (  http://grlc.io/api-git/CLARIAH/grlc-queries/#/default/get_transform )

Hi @ecow -- yes that definitely looks like a bug. Thanks for reporting this, I will look into it.

It looks like transformations work, BUT...
Transformer always works with json, so it breaks when the content-type is not json. Granted, it should break in a more graceful way.
If you set the response content type to application/json it should work fine:

Does this work for you @ecow?
I'll leave his issue open, until more graceful handling of json content type is fixed.

Hi, @c-martinez .
even, if using header "Accept: application/json' , my test  fails with the simple decoration:
#+ transform: {
#+     "label": "?label"
#+   }

Instead the decoration
#+ transform: {
#+     "label": "?label",
#+     "$anchor": "label"
#+   }

works well, producing something like:
[
  {
    "label": {
      "language": "it",
      "value": "string1"
    }
  },
  {
    "label": {
      "language": "it",
      "value": "string2"
    }
  }
]

Is "$anchor" mandatory?
I would like to produce just a simple structure like:
[
"string1",
"string2"
]
Who to do it ? (if possible)?

Yes, I think the $anchor is mandatory.
I'm not an expert on transformer syntax, but maybe check their documentation. Otherwise, perhaps @pasqLisena might be able to shed some light.

Hi, yes the software requires an $anchor or an id field.
You can eventually mark it in this way:
transform: {
    "label": "?label$anchor"
}

Hi @ecow -- I just wanted to check with you if @pasqLisena's suggestion helped you solve your problem and if I can close this issue?

Yes, you can close these issue but docs should be updated. Thank you.


SolidStart barebones example is not building

I cannot build a barebones starter template.
To replicate it simply follow the instructions on Solidstart:
> npm init solid@latest
...
<choosing bare>
<opting out of SSR>
<enabling typescript>
...
> npm install
> npm run build

Nothing happens except a .solid folder is created in the root but it is empty. On top of that the process of "building" is indefinitely stuck. I let it run for an hour while watching a Game Of Thrones episode but it did not finish it's life-long mission of building this starter app unfortunately in that short amount of time. See the screenshot what I mean.

@JaielZeus I noticed this happened to me when I got an optional question of:

"Directory not empty. Continue?" ... yes

Which I think might be the issue because once I killed the directory and re-ran it multiple times with different options of the "bare" example it worked every time. Both with NPM and Pnpm.
Would you mind trying to run it again? It might also help to know your environment info (see example below):
  System:
    OS: Linux 5.10 Debian GNU/Linux 9 (stretch)
    CPU: (8) arm64
  Binaries:
    Node: 14.17.0 - /usr/local/bin/node
    Yarn: 1.22.5 - /usr/local/bin/yarn
    npm: 6.14.13 - /usr/local/bin/npm
  npmPackages:
   solid-start: 1.0.0 => 1.0.0
render: shell

I found the issue happens when the project path contains spaces. I'm on Windows.

Have you tried WSL?

@JaielZeus I noticed this happened to me when I got an optional question of:

"Directory not empty. Continue?" ... yes

Which I think might be the issue because once I killed the directory and re-ran it multiple times with different options of the "bare" example it worked every time. Both with NPM and Pnpm.
Would you mind trying to run it again? It might also help to know your environment info (see example below):
  System:
    OS: Linux 5.10 Debian GNU/Linux 9 (stretch)
    CPU: (8) arm64
  Binaries:
    Node: 14.17.0 - /usr/local/bin/node
    Yarn: 1.22.5 - /usr/local/bin/yarn
    npm: 6.14.13 - /usr/local/bin/npm
  npmPackages:
   solid-start: 1.0.0 => 1.0.0
render: shell

I ran again and it worked just. It was because of @NathanSkilton though. He is totally correct about the issue occuring because of paths with spaces in them:

I found the issue happens when the project path contains spaces. I'm on Windows.

This is definitely the cause of my building failing, which only occurs when using non-SSR option. With SSR and typescript enabled it builds successfully. Without it it does not!
Thank you @NathanSkilton you found a really strange behaviour

Path to vite config is unquoted.
https://github.com/solidjs/solid-start/blob/8cfe543c18c2ee2aed30478da9893c37ec8be7f7/packages/start/bin.cjs#L370-L378
Changed it to the following for a quick test and works.
...(config ? ["--config", `"${config.configFile}"`] : []),

Fixed in 0.2.27


The Tenancy Name and the Object Storage Namespace are not the same in new tenancies

The Tenancy Name and the Object Storage Namespace are not the same in new tenancies. Because of this, I have errors when doing the docker login. To fix this, some modifications should be done. Use the objectstorage_namespace instead of tenancy name, In variables.tf:
locals {
 (...)
  ocir_namespace = lookup(data.oci_objectstorage_namespace.test_namespace, "namespace" )
}

Plus we need to add the corresponding data source in datasources.tf
data "oci_objectstorage_namespace" "test_namespace" {
    compartment_id = var.tenancy_ocid
}

Issue fixed with the release: https://github.com/oracle-quickstart/oci-arch-load-file-into-adw-python/releases/tag/v1.0.1


Clarify resurrector behavior for unresponsive agents

https://www.pivotaltracker.com/story/show/170609374

scan_and_fix will resurrect unresponsive agents. bosh cck --auto will not.


aca-py failing to open wallet

This is with the latest master release of aca-py. I had the same problem with the previous release so its not a new bug but I pulled the latest version to see if the new version fixed it but it didn't. The bug is triggered when I supply a --seed parameter. It does not error when I do not supply a seed but then I can't create any schema etc on the ledger because no public DID.
Here is the invocation and debug console output:
aca-py start \
>         --inbound-transport http <IP_ADDRESS> 8100 \
>         --outbound-transport http \
>         --log-level debug \
>         --endpoint http://localhost:8100 \
>         --label leo \
>         --seed<PHONE_NUMBER>ABCDEF0123456789ABCDEF \
>         --genesis-url http://localhost:9000/genesis \
>         --pool-name localindypool \
>         --admin <IP_ADDRESS> 8150 --admin-insecure-mode \
>         --public-invites \
>         --auto-accept-invites \
>         --auto-accept-requests \
>         --auto-ping-connection \
>         --auto-respond-messages \
>         --auto-respond-credential-offer \
>         --auto-respond-presentation-request \
>         --auto-verify-presentation

2019-08-01 11:44:09,229 asyncio ERROR Task exception was never retrieved
future: <Task finished coro=<start_app() done, defined at /Data/Code/public/hyperledger/aries/cloudagentpy/aries_cloudagent/commands/start.py:16> exception=TypeError('an integer is required (got type NoneType)')>
Traceback (most recent call last):
  File "/Data/Code/public/hyperledger/aries/cloudagentpy/aries_cloudagent/commands/start.py", line 19, in start_app
    await conductor.start()
  File "/Data/Code/public/hyperledger/aries/cloudagentpy/aries_cloudagent/conductor.py", line 171, in start
    await ledger.update_endpoint_for_did(public_did, endpoint)
  File "/Data/Code/public/hyperledger/aries/cloudagentpy/aries_cloudagent/ledger/indy.py", line 465, in update_endpoint_for_did
    exist_endpoint = await self.get_endpoint_for_did(did)
  File "/Data/Code/public/hyperledger/aries/cloudagentpy/aries_cloudagent/ledger/indy.py", line 448, in get_endpoint_for_did
    response_json = await self._submit(request_json, sign=bool(public_did))
  File "/Data/Code/public/hyperledger/aries/cloudagentpy/aries_cloudagent/ledger/indy.py", line 207, in _submit
    request_result_json = await submit_op
  File "/Data/Code/public/hyperledger/indy/indy-sdk/wrappers/python/indy/ledger.py", line 39, in sign_and_submit_request
    c_wallet_handle = c_int32(wallet_handle)
TypeError: an integer is required (got type NoneType)

Attached is the full console output.
aca-py start \
>         --inbound-transport http <IP_ADDRESS> 8100 \
>         --outbound-transport http \
>         --log-level debug \
>         --endpoint http://localhost:8100 \
>         --label leo \
>         --seed<PHONE_NUMBER>ABCDEF0123456789ABCDEF \
>         --genesis-url http://localhost:9000/genesis \
>         --pool-name localindypool \
>         --admin <IP_ADDRESS> 8150 --admin-insecure-mode \
>         --public-invites \
>         --auto-accept-invites \
>         --auto-accept-requests \
>         --auto-ping-connection \
>         --auto-respond-messages \
>         --auto-respond-credential-offer \
>         --auto-respond-presentation-request \
>         --auto-verify-presentation
2019-08-01 11:44:09,108 asyncio DEBUG Using selector: KqueueSelector
2019-08-01 11:44:09,127 aries_cloudagent.wallet.provider INFO Opening wallet type: basic
2019-08-01 11:44:09,145 aries_cloudagent.ledger.indy DEBUG Opening the pool ledger
2019-08-01 11:44:09,145 indy.pool DEBUG set_protocol_version: >>> protocol_version: 2
2019-08-01 11:44:09,146 indy.pool DEBUG set_protocol_version: Creating callback
2019-08-01 11:44:09,146 indy.libindy DEBUG create_cb: >>> cb_type: <class 'ctypes.CFUNCTYPE.<locals>.CFunctionType'>
2019-08-01 11:44:09,146 indy.libindy DEBUG create_cb: <<< res: <CFunctionType object at 0x10bd65530>
2019-08-01 11:44:09,146 indy.libindy DEBUG do_call: >>> name: indy_set_protocol_version, args: (2, <CFunctionType object at 0x10bd65530>)
2019-08-01 11:44:09,146 indy.libindy DEBUG _load_cdll: >>>
2019-08-01 11:44:09,146 indy.libindy DEBUG _load_cdll: Detected OS name: darwin
2019-08-01 11:44:09,146 indy.libindy DEBUG _load_cdll: Resolved libindy name is: libindy.dylib
2019-08-01 11:44:09,155 indy.libindy DEBUG _load_cdll: <<< res: <CDLL 'libindy.dylib', handle 7fdba145be80 at 0x10bdc9490>
2019-08-01 11:44:09,156 indy.libindy DEBUG set_logger: >>>
2019-08-01 11:44:09,156 indy.libindy DEBUG do_call_sync: >>> name: indy_set_logger, args: (None, None, <CFunctionType object at 0x10bd65600>, None)
2019-08-01 11:44:09,156 indy.libindy DEBUG do_call_sync: <<< 0
2019-08-01 11:44:09,156 indy.libindy DEBUG set_logger: <<<
2019-08-01 11:44:09,157 indy.libindy.native.command_executor INFO 	src/commands/mod.rs:99 | Worker thread started
2019-08-01 11:44:09,157 indy.libindy DEBUG do_call: Function indy_set_protocol_version returned err: 0
2019-08-01 11:44:09,157 indy.libindy DEBUG do_call: <<< <Future pending>
2019-08-01 11:44:09,157 indy.libindy.native.indy.commands INFO 	src/commands/mod.rs:140 | PoolCommand command received
2019-08-01 11:44:09,157 indy.libindy.native.pool_command_executor INFO 	src/commands/pool.rs:131 | SetProtocolVersion command received
2019-08-01 11:44:09,158 indy.libindy.native.indy.commands.pool DEBUG 	src/commands/pool.rs:224 | set_protocol_version >>> version: 2
2019-08-01 11:44:09,158 indy.libindy.native.indy.commands.pool DEBUG 	src/commands/pool.rs:232 | set_protocol_version <<<
2019-08-01 11:44:09,158 indy.libindy DEBUG _indy_callback: >>> command_handle: 0, err , args: ()
2019-08-01 11:44:09,158 indy.libindy DEBUG _indy_callback: <<<
2019-08-01 11:44:09,158 indy.libindy DEBUG _indy_loop_callback: >>> command_handle: 0, err , args: ()
2019-08-01 11:44:09,158 indy.libindy DEBUG _indy_loop_callback: Function returned None
2019-08-01 11:44:09,158 indy.libindy DEBUG _indy_loop_callback <<<
2019-08-01 11:44:09,158 indy.pool DEBUG set_protocol_version: <<< res: None
2019-08-01 11:44:09,158 aries_cloudagent.ledger.indy DEBUG Creating pool ledger...
2019-08-01 11:44:09,158 indy.pool DEBUG create_pool_ledger_config: >>> config_name: 'default', config: '{"genesis_txn": "/var/folders/w0/gxdpc9094l96snjf_trkgrfm0001z4/T/indy_genesis_transactions.txt"}'
2019-08-01 11:44:09,158 indy.pool DEBUG create_pool_ledger_config: Creating callback
2019-08-01 11:44:09,158 indy.libindy DEBUG create_cb: >>> cb_type: <class 'ctypes.CFUNCTYPE.<locals>.CFunctionType'>
2019-08-01 11:44:09,158 indy.libindy DEBUG create_cb: <<< res: <CFunctionType object at 0x10bd65940>
2019-08-01 11:44:09,159 indy.libindy DEBUG do_call: >>> name: indy_create_pool_ledger_config, args: (c_char_p(4493990032), c_char_p(4493641776), <CFunctionType object at 0x10bd65940>)
2019-08-01 11:44:09,159 indy.libindy DEBUG do_call: Function indy_create_pool_ledger_config returned err: 0
2019-08-01 11:44:09,159 indy.libindy DEBUG do_call: <<< <Future pending>
2019-08-01 11:44:09,159 indy.libindy.native.indy.commands INFO 	src/commands/mod.rs:140 | PoolCommand command received
2019-08-01 11:44:09,159 indy.libindy.native.pool_command_executor INFO 	src/commands/pool.rs:62 | Create command received
2019-08-01 11:44:09,159 indy.libindy.native.indy.commands.pool DEBUG 	src/commands/pool.rs:138 | create >>> name: "default", config: Some(PoolConfig { genesis_txn: "/var/folders/w0/gxdpc9094l96snjf_trkgrfm0001z4/T/indy_genesis_transactions.txt" })
2019-08-01 11:44:09,160 indy.libindy DEBUG _get_error_details: >>>
2019-08-01 11:44:09,160 indy.libindy DEBUG _get_error_details: <<< error_details: {'backtrace': '', 'message': 'Error: Pool ledger config already exists\n  Caused by: Pool ledger config file with name "default" already exists\n'}
2019-08-01 11:44:09,160 indy.libindy DEBUG _indy_callback: >>> command_handle: 1, err , args: ()
2019-08-01 11:44:09,160 indy.libindy DEBUG _indy_callback: <<<
2019-08-01 11:44:09,160 indy.libindy DEBUG _indy_loop_callback: >>> command_handle: 1, err , args: ()
2019-08-01 11:44:09,160 indy.libindy WARNING _indy_loop_callback: Function returned error
2019-08-01 11:44:09,160 indy.libindy DEBUG _indy_loop_callback <<<
2019-08-01 11:44:09,161 aries_cloudagent.ledger.indy DEBUG Pool ledger already created.
2019-08-01 11:44:09,161 indy.pool DEBUG open_pool_ledger: >>> config_name: 'default', config: '{}'
2019-08-01 11:44:09,161 indy.pool DEBUG open_pool_ledger: Creating callback
2019-08-01 11:44:09,161 indy.libindy DEBUG create_cb: >>> cb_type: <class 'ctypes.CFUNCTYPE.<locals>.CFunctionType'>
2019-08-01 11:44:09,161 indy.libindy DEBUG create_cb: <<< res: <CFunctionType object at 0x10bd65bb0>
2019-08-01 11:44:09,161 indy.libindy DEBUG do_call: >>> name: indy_open_pool_ledger, args: (c_char_p(4491019760), c_char_p(4493989648), <CFunctionType object at 0x10bd65bb0>)
2019-08-01 11:44:09,162 indy.libindy DEBUG do_call: Function indy_open_pool_ledger returned err: 0
2019-08-01 11:44:09,162 indy.libindy DEBUG do_call: <<< <Future pending>
2019-08-01 11:44:09,162 indy.libindy.native.indy.commands INFO 	src/commands/mod.rs:140 | PoolCommand command received
2019-08-01 11:44:09,162 indy.libindy.native.pool_command_executor INFO 	src/commands/pool.rs:70 | Open command received
2019-08-01 11:44:09,162 indy.libindy.native.indy.commands.pool DEBUG 	src/commands/pool.rs:158 | open >>> name: "default", config: Some(PoolOpenConfig { timeout: 20, extended_timeout: 60, conn_limit: 5, conn_active_timeout: 5, preordered_nodes: [] })
2019-08-01 11:44:09,163 indy.libindy.native.indy.commands.pool DEBUG 	src/commands/pool.rs:172 | open <<<
2019-08-01 11:44:09,179 indy.libindy.native.indy.services.pool.networker DEBUG 	src/services/pool/networker.rs:332 | _get_socket: open new socket for node 0
2019-08-01 11:44:09,179 indy.libindy.native.indy.services.pool.networker DEBUG 	src/services/pool/networker.rs:332 | _get_socket: open new socket for node 1
2019-08-01 11:44:09,179 indy.libindy.native.indy.services.pool.networker DEBUG 	src/services/pool/networker.rs:332 | _get_socket: open new socket for node 2
2019-08-01 11:44:09,180 indy.libindy.native.indy.services.pool.networker DEBUG 	src/services/pool/networker.rs:332 | _get_socket: open new socket for node 3
2019-08-01 11:44:09,226 indy.libindy.native.indy.commands INFO 	src/commands/mod.rs:140 | PoolCommand command received
2019-08-01 11:44:09,226 indy.libindy.native.indy.commands.pool INFO 	src/commands/pool.rs:74 | OpenAck handle 2, pool_id 2, result Ok(())
2019-08-01 11:44:09,226 indy.libindy DEBUG _indy_callback: >>> command_handle: 2, err , args: (2,)
2019-08-01 11:44:09,226 indy.libindy DEBUG _indy_callback: <<<
2019-08-01 11:44:09,226 indy.libindy DEBUG _indy_loop_callback: >>> command_handle: 2, err , args: (2,)
2019-08-01 11:44:09,226 indy.libindy DEBUG _indy_loop_callback: Function returned 2
2019-08-01 11:44:09,226 indy.libindy DEBUG _indy_loop_callback <<<
2019-08-01 11:44:09,226 indy.pool DEBUG open_pool_ledger: <<< res: 2
2019-08-01 11:44:09,227 indy.ledger DEBUG build_get_attrib_request: >>> submitter_did: '3avoBCqDMFHFaKUHug9s8W', target_did: '3avoBCqDMFHFaKUHug9s8W', raw: 'endpoint', xhash: None, enc: None
2019-08-01 11:44:09,227 indy.ledger DEBUG build_get_attrib_request: Creating callback
2019-08-01 11:44:09,227 indy.libindy DEBUG create_cb: >>> cb_type: <class 'ctypes.CFUNCTYPE.<locals>.CFunctionType'>
2019-08-01 11:44:09,227 indy.libindy DEBUG create_cb: <<< res: <CFunctionType object at 0x10bd65e20>
2019-08-01 11:44:09,227 indy.libindy DEBUG do_call: >>> name: indy_build_get_attrib_request, args: (c_char_p(4493632912), c_char_p(4493633040), c_char_p(4493990224), None, None, <CFunctionType object at 0x10bd65e20>)
2019-08-01 11:44:09,227 indy.libindy DEBUG do_call: Function indy_build_get_attrib_request returned err: 0
2019-08-01 11:44:09,227 indy.libindy DEBUG do_call: <<< <Future pending>
2019-08-01 11:44:09,227 indy.libindy.native.indy.commands INFO 	src/commands/mod.rs:136 | LedgerCommand command received
2019-08-01 11:44:09,227 indy.libindy.native.ledger_command_executor INFO 	src/commands/ledger.rs:343 | BuildGetAttribRequest command received
2019-08-01 11:44:09,228 indy.libindy.native.indy.commands.ledger DEBUG 	src/commands/ledger.rs:698 | build_get_attrib_request >>> submitter_did: Some("3avoBCqDMFHFaKUHug9s8W"), target_did: "3avoBCqDMFHFaKUHug9s8W", raw: Some("endpoint"), hash: None, enc: None
2019-08-01 11:44:09,228 indy.libindy.native.indy.services.ledger INFO 	src/services/ledger/mod.rs:117 | build_get_attrib_request() => Ok("{\"reqId\":1564681449228407000,\"identifier\":\"3avoBCqDMFHFaKUHug9s8W\",\"operation\":{\"type\":\"104\",\"dest\":\"3avoBCqDMFHFaKUHug9s8W\",\"raw\":\"endpoint\"},\"protocolVersion\":2}")
2019-08-01 11:44:09,228 indy.libindy.native.indy.commands.ledger DEBUG 	src/commands/ledger.rs:710 | build_get_attrib_request <<< res: "{\"reqId\":1564681449228407000,\"identifier\":\"3avoBCqDMFHFaKUHug9s8W\",\"operation\":{\"type\":\"104\",\"dest\":\"3avoBCqDMFHFaKUHug9s8W\",\"raw\":\"endpoint\"},\"protocolVersion\":2}"
2019-08-01 11:44:09,228 indy.libindy DEBUG _indy_callback: >>> command_handle: 3, err , args: (b'{"reqId":1564681449228407000,"identifier":"3avoBCqDMFHFaKUHug9s8W","operation":{"type":"104","dest":"3avoBCqDMFHFaKUHug9s8W","raw":"endpoint"},"protocolVersion":2}',)
2019-08-01 11:44:09,228 indy.libindy DEBUG _indy_callback: <<<
2019-08-01 11:44:09,228 indy.libindy DEBUG _indy_loop_callback: >>> command_handle: 3, err , args: (b'{"reqId":1564681449228407000,"identifier":"3avoBCqDMFHFaKUHug9s8W","operation":{"type":"104","dest":"3avoBCqDMFHFaKUHug9s8W","raw":"endpoint"},"protocolVersion":2}',)
2019-08-01 11:44:09,228 indy.libindy DEBUG _indy_loop_callback: Function returned b'{"reqId":1564681449228407000,"identifier":"3avoBCqDMFHFaKUHug9s8W","operation":{"type":"104","dest":"3avoBCqDMFHFaKUHug9s8W","raw":"endpoint"},"protocolVersion":2}'
2019-08-01 11:44:09,229 indy.libindy DEBUG _indy_loop_callback <<<
2019-08-01 11:44:09,229 indy.ledger DEBUG build_get_attrib_request: <<< res: '{"reqId":1564681449228407000,"identifier":"3avoBCqDMFHFaKUHug9s8W","operation":{"type":"104","dest":"3avoBCqDMFHFaKUHug9s8W","raw":"endpoint"},"protocolVersion":2}'
2019-08-01 11:44:09,229 indy.ledger DEBUG sign_and_submit_request: >>> pool_handle: 2, wallet_handle: None, submitter_did: '3avoBCqDMFHFaKUHug9s8W', request_json: '{"reqId":1564681449228407000,"identifier":"3avoBCqDMFHFaKUHug9s8W","operation":{"type":"104","dest":"3avoBCqDMFHFaKUHug9s8W","raw":"endpoint"},"protocolVersion":2}'
2019-08-01 11:44:09,229 indy.ledger DEBUG sign_and_submit_request: Creating callback
2019-08-01 11:44:09,229 indy.libindy DEBUG create_cb: >>> cb_type: <class 'ctypes.CFUNCTYPE.<locals>.CFunctionType'>
2019-08-01 11:44:09,229 indy.libindy DEBUG create_cb: <<< res: <CFunctionType object at 0x10bdb2120>
2019-08-01 11:44:09,229 asyncio ERROR Task exception was never retrieved
future: <Task finished coro=<start_app() done, defined at /Data/Code/public/hyperledger/aries/cloudagentpy/aries_cloudagent/commands/start.py:16> exception=TypeError('an integer is required (got type NoneType)')>
Traceback (most recent call last):
  File "/Data/Code/public/hyperledger/aries/cloudagentpy/aries_cloudagent/commands/start.py", line 19, in start_app
    await conductor.start()
  File "/Data/Code/public/hyperledger/aries/cloudagentpy/aries_cloudagent/conductor.py", line 171, in start
    await ledger.update_endpoint_for_did(public_did, endpoint)
  File "/Data/Code/public/hyperledger/aries/cloudagentpy/aries_cloudagent/ledger/indy.py", line 465, in update_endpoint_for_did
    exist_endpoint = await self.get_endpoint_for_did(did)
  File "/Data/Code/public/hyperledger/aries/cloudagentpy/aries_cloudagent/ledger/indy.py", line 448, in get_endpoint_for_did
    response_json = await self._submit(request_json, sign=bool(public_did))
  File "/Data/Code/public/hyperledger/aries/cloudagentpy/aries_cloudagent/ledger/indy.py", line 207, in _submit
    request_result_json = await submit_op
  File "/Data/Code/public/hyperledger/indy/indy-sdk/wrappers/python/indy/ledger.py", line 39, in sign_and_submit_request
    c_wallet_handle = c_int32(wallet_handle)
TypeError: an integer is required (got type NoneType)
2019-08-01 11:44:14,183 indy.libindy.native.zmq DEBUG 	/Users/samuel/.cargo/registry/src/github.com-1ecc6299db9ec823/zmq-0.8.3/src/lib.rs:555 | socket dropped
2019-08-01 11:44:14,183 indy.libindy.native.zmq DEBUG 	/Users/samuel/.cargo/registry/src/github.com-1ecc6299db9ec823/zmq-0.8.3/src/lib.rs:555 | socket dropped
2019-08-01 11:44:14,183 indy.libindy.native.zmq DEBUG 	/Users/samuel/.cargo/registry/src/github.com-1ecc6299db9ec823/zmq-0.8.3/src/lib.rs:555 | socket dropped
2019-08-01 11:44:14,183 indy.libindy.native.zmq DEBUG 	/Users/samuel/.cargo/registry/src/github.com-1ecc6299db9ec823/zmq-0.8.3/src/lib.rs:555 | socket dropped
2019-08-01 11:44:14,183 indy.libindy.native.zmq DEBUG 	/Users/samuel/.cargo/registry/src/github.com-1ecc6299db9ec823/zmq-0.8.3/src/lib.rs:462 | context dropped
2019-08-01 11:44:14,231 aries_cloudagent.ledger.indy DEBUG Closing pool ledger after timeout
2019-08-01 11:44:14,231 indy.pool DEBUG close_pool_ledger: >>> config_name: 2
2019-08-01 11:44:14,231 indy.pool DEBUG close_pool_ledger: Creating callback
2019-08-01 11:44:14,231 indy.libindy DEBUG create_cb: >>> cb_type: <class 'ctypes.CFUNCTYPE.<locals>.CFunctionType'>
2019-08-01 11:44:14,231 indy.libindy DEBUG create_cb: <<< res: <CFunctionType object at 0x10bdb2390>
2019-08-01 11:44:14,231 indy.libindy DEBUG do_call: >>> name: indy_close_pool_ledger, args: (c_int(2), <CFunctionType object at 0x10bdb2390>)
2019-08-01 11:44:14,232 indy.libindy DEBUG do_call: Function indy_close_pool_ledger returned err: 0
2019-08-01 11:44:14,232 indy.libindy DEBUG do_call: <<< <Future pending>
2019-08-01 11:44:14,232 indy.libindy.native.indy.commands INFO 	src/commands/mod.rs:140 | PoolCommand command received
2019-08-01 11:44:14,232 indy.libindy.native.pool_command_executor INFO 	src/commands/pool.rs:94 | Close command received
2019-08-01 11:44:14,232 indy.libindy.native.indy.commands.pool DEBUG 	src/commands/pool.rs:188 | close >>> handle: 2
2019-08-01 11:44:14,232 indy.libindy.native.indy.services.pool.pool INFO 	src/services/pool/pool.rs:737 | Drop started
2019-08-01 11:44:14,232 indy.libindy.native.indy.services.pool.pool INFO 	src/services/pool/pool.rs:745 | Drop wait worker
2019-08-01 11:44:14,233 indy.libindy.native.zmq DEBUG 	/Users/samuel/.cargo/registry/src/github.com-1ecc6299db9ec823/zmq-0.8.3/src/lib.rs:555 | socket dropped
2019-08-01 11:44:14,233 indy.libindy.native.indy.services.pool.pool INFO 	src/services/pool/pool.rs:748 | Drop finished
2019-08-01 11:44:14,234 indy.libindy.native.zmq DEBUG 	/Users/samuel/.cargo/registry/src/github.com-1ecc6299db9ec823/zmq-0.8.3/src/lib.rs:555 | socket dropped
2019-08-01 11:44:14,234 indy.libindy.native.zmq DEBUG 	/Users/samuel/.cargo/registry/src/github.com-1ecc6299db9ec823/zmq-0.8.3/src/lib.rs:462 | context dropped
2019-08-01 11:44:14,235 indy.libindy.native.indy.commands.pool DEBUG 	src/commands/pool.rs:202 | close <<<
2019-08-01 11:44:14,235 indy.libindy.native.indy.commands INFO 	src/commands/mod.rs:140 | PoolCommand command received
2019-08-01 11:44:14,235 indy.libindy.native.pool_command_executor INFO 	src/commands/pool.rs:98 | CloseAck command received
2019-08-01 11:44:14,235 indy.libindy DEBUG _indy_callback: >>> command_handle: 4, err , args: ()
2019-08-01 11:44:14,235 indy.libindy DEBUG _indy_callback: <<<
2019-08-01 11:44:14,235 indy.libindy DEBUG _indy_loop_callback: >>> command_handle: 4, err , args: ()
2019-08-01 11:44:14,235 indy.libindy DEBUG _indy_loop_callback: Function returned None
2019-08-01 11:44:14,235 indy.libindy DEBUG _indy_loop_callback <<<
2019-08-01 11:44:14,236 indy.pool DEBUG close_pool_ledger: <<< res: None

aca-py doesn't register DID's on the ledger so you need to register your DID in advance, before starting aca-py
If you are running von-network you can register your did using the ledger browser UI.

Sorry for the confusion. I did register the DID on the ledger beforehand. It still creates this error. So maybe its just trying to put the DID it is creating from the seed into its wallet and that fails.

I need the public did in order to put stuff on the ledger like credentials. Its not clear to me what all the steps are on boot up.

I'll have to defer to @andrewwhitehead  or @nrempel  on this question


Fixes #354 fix(spotlight): set default z-index of 200

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


jib-cli native image PoC

I recently had a needs to run jib-cli on the machine that does not have a JRE.
So, I tried GraalVM native image build. Not perfect though but working.
The full run-down can be found here: https://github.com/appkr/jib/blob/a46e8a6b95db3dab7a653da91a241cfdeaf946f2/jib-cli/quickstart/README.md
The changes are find at https://github.com/appkr/jib/pull/1/files
I think you can reference the changes and nicely apply to your project.
I hope to see this functioning in official release soon.
Thanks a ton for the great one.

I've tested against a macos-amd64 machine and was OK.
When I tried on macos-aarch64, and ubuntu-latest, the builds are fine but the artifacts aren't working. I think that is because the config generated by a native-image-agent was incomplete.  Closing this, but I would not delete forked one, hoping somebody reached by googling can be benefited.


3 np.format

@dania-vera please sync with upstream, I saw that in your branch This branch is 11 commits behind SciSharp:master.


Add correct dir attribute to html tag in admin

Solves #5263

Will do!

Thanks @rinti! Merged in 1b22794da21abf9afb1ca6c870e0e07c748030b7.


NIMBUS-117:: PreviousLeafState fix

Description

Fixed an issue where previousLeafState was being stored correctly

Overview of Changes

See code change

Type of Change

[ ] Bug fix

Test Details

Functional Testing in petclinic
Test cases pending

Additional Notes

N/A

You did it @lopezton-anthem!
Thank you for signing the Anthem Opensource Software CLA.


Post type features

Post type features, tags, comments etc should not be enabled via the options page but be set by filters instead. There have been numerous occasions where sites have been deployed and settings from dev/staging/production have varied.

I'm going to close this because we've moved on to a new version of the plugin.


Support IS8601 strings with milliseconds and timezone

the iso8601 parser is not able to parse an iso8601 string that contains milliseconds and timezone, e.g. "2015-06-23T12:40:08.594+02:00"

@sononum This is great, Ulrich! Would you mind sending a PR including some additional test cases?

@sononum nevermind, just saw your PR :clap:


current_layer is wrong

Version of the moonraker integration
0.9.0
Describe the bug
Current layer says 6 when moonraker says 1.
I have done a light reading on the code and it is calculating the layer, I have that information being correctly set with SET_PRINT_STATS_INFO that sets the information on the print_stats.info object exposed by mooraker.
partial example below
{
   "result":{
      "status":{
         "print_stats":{
            "info":{
               "total_layer":132,
               "current_layer":1
            }
         },
         "eventtime":1057200.052048971
      }
   }
}

adding this before the current return in calculate_current_layer
if (data["status"]["print_stats"]["info"]["current_layer"] != null):
    return data["status"]["print_stats"]["info"]["current_layer"]

gives me the correct info

@nelsongraca we will look at fixing it in the next few weeks, that being said, if you have bandwith, feel free to propose a PR

@marcolivierarsenault I'll try to, since I have the code working should be quick, but I want to add an alternative way for the total layer count as well, it's contained in the same object that reports the current layer

@nelsongraca any chance with this?

Creating the PR right now.

Done: https://github.com/marcolivierarsenault/moonraker-home-assistant/pull/156
This has been running on my instance for a while and works