Two Nuki Bridge

Hi,
First of all, thanks for your work, it's amazing to be able to have all the Nuki gadgets in HomeKit.
I have a Nuki Bridge paired with a Nuki Opener, Nuki Door Sensor and Nuki Smart Lock and everything works perfectly in Homekit with Homebridge.
The problem is that, in the same house, I have another Nuki Bridge paired with another Nuki Smart Lock, but don’t appear in Homekit.
Is it possible for the plugin to detect several Nuki bridges?
Thank you in advance,

Homebridge NB should be able to handle and support multiple Nuki bridges.  Make sure HTTP API and API Quick Discovery are enabled, see https://github.com/ebaauw/homebridge-nb/issues/73#issuecomment-1174775984.

It is solved now, thank you very much for your help.
Congratulations on your job once again.

Ich habe auch zwei Nuki Bridges.


Improve error message when deleting from an empty list

Fixes #250

Codecov Report

Merging #257 into master will decrease coverage by 0.03%.
The diff coverage is 66.66%.

@@             Coverage Diff              @@
##             master     #257      +/-   ##
============================================
- Coverage     76.92%   76.88%   -0.04%
  Complexity     1539     1539
============================================
  Files           141      141
  Lines          4156     4158       +2
  Branches        556      558       +2
============================================
  Hits           3197     3197
  Misses          862      862
- Partials         97       99       +2

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/chopchop/logic/commands/Command.java
89.47% <66.66%> (-10.53%)
7.00 <0.00> (ø)

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 cda135b...6e50cee. Read the comment docs.


Alert links

The "alert details" link. The links do work, however you need to be logged into sysdig (an expected step), AND be viewing the correct sysdig team (unexpected step) to be directed to the alert trigger details. The links should automatically direct you to the correct sysdig team and alert notification.

An update to SysDig was released.  This seems to be working now.


Added pages api for get method

There are still a bunch more of the pages API methods to add.  But figured I'd start with this.

The travis test seems to be complaining about an unrelated test

Thanks. I'll check what's going with the test.

Published as 1.0.1


Backend Development Resources added

Ruby on Rails Video Tutorials Added in Backend Development

@debrajhyper Please review this PR

@debrajhyper Can you please review it

@debrajhyper approve this PR please

Thanks a lot for your contributions.
Looking forward for more such resources which helps others and make the community grow. ❤


Model weights for TotalSeg v1

Hi, I was using the TotalSegmentator v1.5.6 for my previous code using python_api. Accidentally, I installed in the same Conda environment the TotalSegmentator v.2.0.5. as want to try out the new 'task'. (And v1.5.6 was uninstalled).
Now I try to reinstall back v1.5.6 in the Conda env as my previous code depends on it, but have the following error:
Downloading pretrained weights for Task 251 (~230MB) ...
Traceback (most recent call last):
c:\users\Anaconda3\envs\manta2\lib\site-packages\requests\models.py", line 960, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: http://<IP_ADDRESS>/static/Task251_TotalSegmentator_part1_organs_1139subj.zip

Would it please advice would the weights be still available and how shall I let the v1.5.6 to load it again?
Thanks a lot for the great work and new versions :)

If you want to use totalsegmentator v1 you should use v1.5.7. Does it work when you try installing
pip install --upgrade totalsegmentator==1.5.7
Does it work after deleting ~/.totalsegmentator? This will deleted all weights already downloaded. Then they are automatically redownloaded.


Feature additions

Feedback when you pick up items
Feedback for camp interactions
Options for longer feedback on any interaction.
Optional vibe bonus for not taking damage whilst exploring would be nice.

Wow. Had no idea anyone was even using this. :D
Will take those into consideration!

800+ downloads, and everyone is shy to give out suggestions maybe lol


Caching in AuthenticatedWebView

It'll be good to have an option to allow caching in AuthenticatedWebView.

@chiragmittal19 thanks for mentioning this option, we already have this task in our queue as Jira Story LEARNER-7230


Update MainMatrixMultiplication.js

Issue ID you have worked upon -
#38
Briefly explain your program logic -
This program is about multiplying two matrices given. This happens by computing the elements of the result matrix by multiplying the corresponding elements from both matrices.
Screenshots(Attach 2 screenshots of your own input and output) -
Attach here

By raising this PR I affirm that -

[x] My code follows the guidelines of this project.

[x] I have performed a self-review of my own code.

[x] I have commented my code.

[x] My code gives the correct output.

[x] I affirm that I strictly follow contributing guidelines and code of conduct.

Congratulations 🎉 @tmsagarofficial on your contribution.
Thanks for adding value to this repository. 😊
Let's celebrate this fest 😃 by providing more developers 👨💻👩💻 an opportunity to contribute. Help us make this repository reach far and more by sharing this to your friends and colleagues.
Your efforts can make difference.

Hey 👋, may you also encourage us by clicking the star icon on the repository main page. ⭐


Incorrect edges count after committing with sbtree-based ridbag

OrientDB Version: 3.2.6
Java Version: openjdk version "11.0.15"
OS: Ubuntu 22.04
Expected behavior
A committed vertex should return the correct edges after adding a new edge.
Actual behavior
When sbtree-based rigbad is activated (server configured with ORIENTDB_SETTINGS="-DridBag.embeddedToSbtreeBonsaiThreshold=-1"), adding an edge to a vertex and then committing, the vertex returns incorrect count of edges.
This is the same as #9076 but for OrientDB version 3.2 with Multi Model API. The behavior is correct in version 3.1. As noted in https://github.com/orientechnologies/orientdb/issues/9076#issuecomment-593975806, in 3.0 configuring the client with GlobalConfiguration.RID_BAG_EMBEDDED_TO_SBTREEBONSAI_THRESHOLD.setValue(-1) fixes the case, but this is not true in 3.2.
Steps to reproduce
        ODatabaseSession g = pool.acquire();
        g.begin();
        OVertex vertex1 = g.newVertex("V"); vertex1.save();
        OVertex vertex2 = g.newVertex("V"); vertex2.save();
        g.commit();

        int version = vertex1.getProperty("@version");
        System.out.println("Version: " + version);
        System.out.println("vertex1 out: " + countEdges(vertex1, ODirection.OUT));
        System.out.println("vertex2 in: " + countEdges(vertex2, ODirection.IN));
        /* output:
           Version: 1
           vertex1 out: 0
           vertex2 in: 0
        */

        g.begin();
        vertex1.addEdge(vertex2);
        vertex1.save();

        version = vertex1.getProperty("@version");
        System.out.println("Pre-commit:");
        System.out.println("Version: " + version);
        System.out.println("vertex1 out: " + countEdges(vertex1, ODirection.OUT));
        System.out.println("vertex2 in: " + countEdges(vertex2, ODirection.IN));
        /* output:
           Pre-commit:
           Version: 1
           vertex1 out: 1
           vertex2 in: 1
        */

        g.commit();

        version = vertex1.getProperty("@version");
        System.out.println("Post-commit:");
        System.out.println("Version: " + version);
        System.out.println("vertex1 out: " + countEdges(vertex1, ODirection.OUT));
        System.out.println("vertex2 in: " + countEdges(vertex2, ODirection.IN));
        /* output:
           Post-commit:
           Version: 2
           vertex1 out: 0 <- INCORRECT
           vertex2 in: 0 <- INCORRECT
        */

        g.close();

        g = pool.acquire();
        vertex1 = g.load(vertex1.getIdentity());
        vertex2 = g.load(vertex2.getIdentity());

        version = vertex1.getProperty("@version");
        System.out.println("Reload in new transaction:");
        System.out.println("Version: " + version);
        System.out.println("vertex1 out: " + countEdges(vertex1, ODirection.OUT));
        System.out.println("vertex2 in: " + countEdges(vertex2, ODirection.IN));
        /* output:
           Reload in new transaction:
           Version: 2
           vertex1 out: 1
           vertex2 in: 1
        */

    private int countEdges(OVertex v, ODirection dir) throws Exception {
        int c = 0;
        Iterator it = v.getEdges(dir).iterator();
        while (it.hasNext()) { c++; it.next(); }
        return c;
    }

Hi,
Tried to write a test out of the specified case, but seems to work fine, could you help me to reproduce?
here is the commit: https://github.com/orientechnologies/orientdb/commit/effc3138befc2c60bf4f46d6fcd04b4c9737da2c
Regards

Hi,
I could reproduce the case in remote and fix it, the fix will be released with the next hotfix 3.2.18.
Regards

Hi, I tested 3.2.18 and it is fixed. Thanks.


Minor fixes

Remove dead codes (Stage and Scene) from ClientInfoPage
Refactor UniqueTList -> UniqueList & isExisting -> isUnique #76
Change application icon (calendar -> muscle)
Add autocomplete to command box #100
[Draft] Homepage middle section to display today's schedule #31
Change HelpWindow design and utility
Modify Command TextField

Changed Icon

Auto-complete snip:

*Side effect: If the user presses "tab", it will auto-complete the first line
Homepage today's schedule (Draft)

Future fixes could include a nicer UI to display schedule. To be discussed
HelpWindow Changes

By clicking on the link itself, it will open the UG in a browser. Requires testing on Linux and MacOS

Pressing Enter will focus on the link and 'click' it.
Pressing ESC will close the window.

Modified Command TextField

Have we checked with Prof Damith on using controlsfx as external libraries?

Have we checked with Prof Damith on using controlsfx as external libraries?

Yup. Approved.
https://github.com/nus-cs2103-AY2021S1/forum/issues/308


Docs for trait implementations should show where the function bodies are located

Example: say you want to call read_to_string on some third party HTTP Response that implements std::io::Read. Looking at the documentation:

Unless you went to the std documentation for Read, there is no indication that the read_to_string function is actually located in a different place (std::io) than the read function (which is in the Response module).
This makes figuring out which things to use in your Rust code a considerably more awkward process. Perhaps there could be a way to better display this in the documentation?

This issue doesn't pertain to Cargo.

Yeah this is an issue for rustdoc which lives in rust-lang/rust, but feel free to reopen the issue over there!


Added notes about not filling the requires field.

The idea for this edit originated here: https://github.com/ros-infrastructure/rosdep/issues/497 .

:+1: Thank you!


PFM: FeePercentage param should default to zero if not set

At the moment, if the param is not set (i.e.: set to "") txs with forwarding will fail since https://github.com/cosmos/ibc-apps/blob/main/middleware/packet-forward-middleware/router/keeper/keeper.go#L214 can't convert it to a Dec.
Adding sensible defaults should be an easy fix

yeah, I noticed that too, but thought I'd ignore it to avoid having to migrate the params to the new key.

Hey! While exploring the PFM, also noticed that the ModuleName has a typo packetfowardmiddleware -> packetforwardmiddleware, would be nice to be renamed if it's an easy fix

Yes, we realized this after the first release of the middleware unfortunately, so it was already adopted with the typo by some chains. To prevent migrations, we decided to live with the typo.
https://github.com/strangelove-ventures/packet-forward-middleware/commits/f520372571b26f23e7ce4ba9925efbd1366fb0b6/router/types/keys.go

At the moment, if the param is not set (i.e.: set to "") txs with forwarding will fail since https://github.com/cosmos/ibc-apps/blob/main/middleware/packet-forward-middleware/router/keeper/keeper.go#L214 can't convert it to a Dec.
Adding sensible defaults should be an easy fix

I took a look at this and it seemed like we are using a default value of 0 and also doing some validation to ensure that the param value can be type coerced into the sdk.Dec type properly see
Is there something i'm overlooking here?

That looks good to me to right now. I can't remember the details here, but I think it was happening for us on a testnet when the parameter was not set on genesis or set to "". IIRC the validation occurs when setting the param, but if it never was initialized, it would somehow get ""

Thanks that bit of context actually helped me find what I think the issue could be then.
In module.go we are not calling ValidateGenesis in the InitGenesis call. I'll get a PR opened right now


#215 - use wagon maven plugin for ontology download

use wagon-maven-plugin for the download part of the ontology download/unpack process
use copy-rename-plugin to move files
use truezip plugin instead of unzip cmd (not available under windows)
update jdk in ci.yml

I tested this with @Frontman50 on a windows machine this morning, and it was working as it does on linux


[google_mlkit_entity_extraction] iOS and Android detect different timestamps

As I played around with the example app, I might found a bug trying to convert timestamp to DateTime.
On Android 25 Jul from the Screenshot below has timestamp:<PHONE_NUMBER>000. This is the expected value.
On iOS  timestamp of 25 Jul has timestamp<PHONE_NUMBER>.
As a workaround I multiply timestamp values on iOS with 1000, but it would be nice if this can be fixed.

@test0terter0n : this is an open source project, contributions are welcome. Feel free to send a PR with your contribution. Since you have already found the bug and know how to reproduce it, please go ahead and send us a PR.

@fbernaly  did create https://github.com/flutter-ml/google_ml_kit_flutter/pull/501


Add hyperspyui metapackage

[x] add hyperspyui to metapackage
[x] add mrcz dependency
[x] add myself as recipe-maintainer

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

It looks like the 'hyperspy' output doesn't have any tests.
It looks like the 'hyperspy-dev' output doesn't have any tests.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [63]

For recipe:

It looks like the 'hyperspy' output doesn't have any tests.
It looks like the 'hyperspy-dev' output doesn't have any tests.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

It looks like the 'hyperspy' output doesn't have any tests.
It looks like the 'hyperspy-dev' output doesn't have any tests.


MessagePackProtocol in Blazor

I have used MessagePackProtocol in projects with SignalR.
Does it apply the same way for Blazor WebAssembly projects?
(is not an issue, is only a doubt)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 08de9daf-79aa-ee76-431e-f2432f8d691e
Version Independent ID: 1a1ee728-1741-c82a-75e1-06159709935b
Content: Use ASP.NET Core SignalR with a hosted Blazor WebAssembly app
Content Source: aspnetcore/tutorials/signalr-blazor-webassembly.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @harveytriana ... I haven't heard that it wouldn't work, but ask the product unit on their repo at ...
https://github.com/dotnet/aspnetcore/issues

Hello @harveytriana ... I haven't heard that it wouldn't work, but ask the product unit on their repo at ...
https://github.com/dotnet/aspnetcore/issues


ESP32(SPI): Disable the write side when reading is being done in DMA …

…mode
Thank you for your contribution!
We appreciate the time and effort you've put into this pull request.
To help us review it efficiently, please ensure you've gone through the following checklist:
Submission Checklist 📝

[ ] I have updated existing examples or added new ones (if applicable).
[ ] I have used cargo xtask fmt-packages command to ensure that all changed code is formatted correctly.
[ ] My changes were added to the CHANGELOG.md in the proper section.
[ ] My changes are in accordance to the esp-rs API guidelines

Extra:

[ ] I have read the CONTRIBUTING.md guide and followed its instructions.

Pull Request Details 📖
Description
This PR is based on @Dominaezzz's suggestion from https://github.com/esp-rs/esp-hal/issues/1860#issuecomment-2252843420.
Testing
//! Connect MISO and MOSI pins
//!
//! The following wiring is assumed:
//! SCLK => GPIO0
//! MISO => GPIO2
//! MOSI => GPIO4

//% CHIPS: esp32 esp32c2 esp32c3 esp32c6 esp32h2 esp32s2 esp32s3
//% FEATURES: async embassy embassy-generic-timers embedded-hal embedded-hal-bus/async

#![no_std]
#![no_main]

use embassy_executor::Spawner;
use embassy_time::{Duration, Timer};
use embedded_hal::spi::Operation;
use embedded_hal_async::spi::SpiDevice;
use embedded_hal_bus::spi::ExclusiveDevice;
use esp_backtrace as _;
use esp_hal::{
    clock::ClockControl,
    dma::*,
    dma_descriptors,
    gpio::{Io, Level, Output},
    peripherals::Peripherals,
    prelude::*,
    spi::{
        master::{dma::SpiDma, prelude::*, Spi},
        FullDuplexMode,
        SpiMode,
    },
    system::SystemControl,
    timer::{timg::TimerGroup, ErasedTimer, OneShotTimer},
    Async,
    FlashSafeDma,
};
use esp_println::println;

// When you are okay with using a nightly compiler it's better to use https://docs.rs/static_cell/2.1.0/static_cell/macro.make_static.html
macro_rules! mk_static {
    ($t:ty,$val:expr) => {{
        static STATIC_CELL: static_cell::StaticCell<$t> = static_cell::StaticCell::new();
        #[deny(unused_attributes)]
        let x = STATIC_CELL.uninit().write(($val));
        x
    }};
}

const DMA_BUF: usize = 256;

#[cfg(not(any(feature = "esp32", feature = "esp32s2")))]
type SafeSpiDma = FlashSafeDma<
    SpiDma<'static, esp_hal::peripherals::SPI2, DmaChannel0, FullDuplexMode, Async>,
    DMA_BUF,
>;

#[cfg(any(feature = "esp32", feature = "esp32s2"))]
type SafeSpiDma = FlashSafeDma<
    SpiDma<'static, esp_hal::peripherals::SPI2, Spi2DmaChannel, FullDuplexMode, Async>,
    DMA_BUF,
>;

#[esp_hal_embassy::main]
async fn main(_spawner: Spawner) {
    esp_println::println!("Init!");
    let peripherals = Peripherals::take();
    let system = SystemControl::new(peripherals.SYSTEM);
    let clocks = ClockControl::boot_defaults(system.clock_control).freeze();

    let timg0 = TimerGroup::new(peripherals.TIMG0, &clocks);
    let timer0: ErasedTimer = timg0.timer0.into();
    let timers = [OneShotTimer::new(timer0)];
    let timers = mk_static!([OneShotTimer<ErasedTimer>; 1], timers);
    esp_hal_embassy::init(&clocks, timers);

    let io = Io::new(peripherals.GPIO, peripherals.IO_MUX);
    let sclk = io.pins.gpio0;
    let miso = io.pins.gpio2;
    let mosi = io.pins.gpio4;
    let cs = io.pins.gpio5;

    let dma = Dma::new(peripherals.DMA);

    #[cfg(any(feature = "esp32", feature = "esp32s2"))]
    let dma_channel = dma.spi2channel;
    #[cfg(not(any(feature = "esp32", feature = "esp32s2")))]
    let dma_channel = dma.channel0;

    let (descriptors, rx_descriptors) = dma_descriptors!(32000);

    let mut spi = Spi::new(peripherals.SPI2, 100.kHz(), SpiMode::Mode0, &clocks)
        .with_pins(Some(sclk), Some(mosi), Some(miso), Some(cs))
        .with_dma(
            dma_channel.configure_for_async(false, DmaPriority::Priority0),
            descriptors,
            rx_descriptors,
        );

    let cs = Output::new(io.pins.gpio18, Level::Low);

    let spi: SafeSpiDma = FlashSafeDma::new(spi);
    let mut spi_dev = ExclusiveDevice::new(spi, cs, embassy_time::Delay).unwrap();

    loop {
        let write_buf = &[1];
        let payload = &[5, 4, 3, 2, 1];

        println!("SPI 2 (write buffer)... ");
        let mut ops = [Operation::Write(write_buf), Operation::Write(payload)];
        let _ = spi_dev.transaction(&mut ops).await;

        println!("SPI 3 (read previous buffer)...");
        let mut read: [u8; 6] = [0x00u8; 6];
        let mut ops = [Operation::Read(&mut read)];
        let _ = spi_dev.transaction(&mut ops).await;
        println!("... result: {:?}", read);

        Timer::after(Duration::from_millis(1_000)).await;
    }
}

now prints
Init!
SPI 2 (write buffer)...
SPI 3 (read previous buffer)...
... result: [0, 0, 0, 0, 0, 0]
SPI 2 (write buffer)...
SPI 3 (read previous buffer)...
... result: [0, 0, 0, 0, 0, 0]
SPI 2 (write buffer)...
SPI 3 (read previous buffer)...
... result: [0, 0, 0, 0, 0, 0]

closes #1860

I will add a HIL test for this as well.

Gently ping


creep moving back and forth as the spawn tries to shove them

spawn shoves them
spawn probably reserves the position after the creep in the way when it tries to reserve it for the spawning creep. Thus the blocking creep moves back, stopping spawning totally

spawn shoves them
spawn probably reserves the position after the creep in the way when it tries to reserve it for the spawning creep. Thus the blocking creep moves back, stopping spawning totally


Handle movement of common_at.cfg

https://github.com/SpongePowered/SpongeCommon/pull/289 requires that I move the common_at.cfg for FMLAT (not used here). This updates SpongeVanilla to handle that. SpongeForge.

See SpongePowered/SpongeCommon#289, tl;dr merged into branch, will merge into master with some other changes soon; @kashike expects it to be in March.


Fixing assembly dependency resolution

Resolves #204
Resolvers #200

Can you give a little background on what the issue was and how this addresses it?

A function context is established for assembly loading, which enables us to properly resolve private assemblies and NuGet assembly references for a given function. When loading an indirect dependency, we were failing to resolve the context and therefore, failing to load those assemblies. With the changes in this PR, the context keeps track of the dependencies it loads, allowing us to correctly resolve the context when indirect dependencies are requested, which we then use to resolve those dependencies.

Updated comment as this also resolves issue #200

Looks OK to me. How did you test this? I understand adding regression tests for this might be difficult without making changes to make the loader more testable. If you think it would take to long to get tests in place, we can add to backlog.

The tests were indeed fairly manual. If you don't object, I'll create an issue to address this in a separate PR which will include some of the other code refactoring to better enable testing.

Sounds good.


Content-Type

Originally reported on Google Code with ID 220
What steps will reproduce the problem?
1. Call REST API POST Method
2. Add Headers Content-Type: application/json
3. also select Content-Type from drop down "application/json"

A) What is the expected output? What do you see instead?
When i call the API in the request header i am seeing
Content-Type: multipart/form-data; boundary=----WebKitFormBoundarysB8WKHBozuM7UQVY

But It should be application/json.

B) On what operating system, browser and browser version?
I am suing client as Windows 7 with Chrome browser 31.x, and my REST API running in
REDHAT

C) Please provide any additional information below.
Is there any setting i need to do to get the  Content-Type as application/json" over
writing multipart/form

Reported by ramesh.chundru on 2013-11-15 23:08:37

It's because you have attached file to the request.
However, this issue will be resolved with #320


Add Version() to BblfshClient

The recent bblfsh release adds Version() API. Support it here?

NativeParse should also be supported.

@zurk Since the support has landed, we urgently need to add the check into current ml's master.


Optical Tactile Sensor Plugin

Optical Tactile Sensor Plugin for GSoC 2020.
It retrieves the contacts given by a contact sensor and computes the normal surfaces of an object given the data returned by a Depth Camera. It also visualizes these forces in a similar way as Gazebo Classic, so this PR partially addresses #112.
Future work will be focused on:

[x] Update sensor and .sdf to more realistic environment and objects.
[ ]  Tutorial explaining the plugin.
[ ]  Computation performance.
[ ] Merging the data returned by contact and camera sensors.

CC @mabelzhang

Sorry, I'll push changes to another branch for a future PR!
I'll take a look to those indentations as well.

Apart from the feedback modifications, I've made quite some refactoring based on the feedback as well, but hopefully it's not too confusing.
The main changes are the following:

As provided in the feedback, I've separated the forces visualization from the computation. For that purpose, I've added Visualization.hh and Visualization.cc.
Depth camera callback: Instead of storing the point cloud into a nested std::vector variable, I get a specific point from the raw pointer returned when I compute the normal forces, so that should be faster.
The Configure and Load methods had overlapping functionality before. Now I basically use Configure to read all of the sdf parameters and Load to check the plugin structure with the EntityComponentManager and some additional things.
I've removed some attributes/methods that I wrote at the beginning of the project but actually don't use/need them.
In OpticalTactilePlugin.cc, I've changed the order in which the methods are written, so hopefully the file is more intuitive to read and things are easier to find.
Indentation!

I've addressed the comments and it should be ready for another review.
Apart from the minor changes, there were a few comments that made do some more refactoring:

In order to change the rendering to cylinders&spheres to points&lines, along with making the marker msg variables local, I had to refactor Visualization.hh and Visualization.cc. I've basically divided those methods into initialization (setting some common msg fields), addition in the case normal forces and request of the /marker service. I hope it's clearer than before.
Given the marker types change, I've also removed the plugin parameters that are no longer necessary.
I've removed the InterpolateContactData method.

Looks good. The only remaining thing to look into is the POINTS marker not taking on the scales specified, but that can be done outside of this PR.
DCO looks peculiar... probably from one of the merged commits. I might need to override that.
@azeey Could you take a last pass since you requested changes? Also good for another pair of eyes since we're merging into master.

@azeey Friendly ping for a review please :)

For visibility, we are reviewing newer additions into this branch on @mcres's fork https://github.com/mcres/ign-gazebo/pull/1 for the sake of time, so that we can get everything in by this Friday.
When this PR here is merged, we will open a new PR with changes from that fork. Hopefully that will take shorter time to review since I would have done a few passes.

Could you merge from master? That might fix the 3 new warnings on CI.

I'm going to remove the beta label from this PR, so it won't be included on Dome's initial release, but it can come on a minor release after that.

Seems that the Ubuntu CI was fixed. Should I do anything else before merging?

@mabelzhang / @azeey : both of you have requests for changes. Would it be possible to do another review? Thanks!

Looks like this comment is unresolved: https://github.com/ignitionrobotics/ign-gazebo/pull/229#discussion_r482524013
Mac CI is still failing.
Those are the only remaining things for this PR.

@osrf-jenkins run tests

Mac CI has a new warning https://build.osrfoundation.org/job/ignition_gazebo-ci-pr_any-homebrew-amd64/3994/
OpticalTactilePlugin.cc:529
expression result unused

That should be an easy fix.
Test failures:
ServerRepeat/DiffDriveTest.PublishCmdCustomTopics/0
ServerRepeat/DiffDriveTest.SkidPublishCmd/0
INTEGRATION_physics_system.test_ran
@chapulina are these flakey by any chance? The reference build 3993 has a different set of failing tests, so I can't really tell. Looks like the badge linked from osrf/buildfarmer has yet a different set of failing tests ha...

are these flakey by any chance?

We don't have many builds on ign-gazebo4 yet, but luckily we have enough to see these 2 are flaking:

https://build.osrfoundation.org/job/ignition_gazebo-ci-ign-gazebo4-homebrew-amd64/3/testReport/junit/(root)/ServerRepeat_DiffDriveTest/PublishCmdCustomTopics_0/history/
https://build.osrfoundation.org/job/ignition_gazebo-ci-ign-gazebo4-homebrew-amd64/3/testReport/junit/(root)/ServerRepeat_DiffDriveTest/SkidPublishCmd_0/history/

But the NonDefaultCanonicalLink test that segfaulted has been passing on ign-gazebo4:

https://build.osrfoundation.org/job/ignition_gazebo-ci-ign-gazebo4-homebrew-amd64/3/testReport/junit/(root)/PhysicsSystemFixture/NonDefaultCanonicalLink/history/

And ign-gazebo3:

https://build.osrfoundation.org/job/ignition_gazebo-ci-ign-gazebo3-homebrew-amd64/68/testReport/junit/(root)/PhysicsSystemFixture/NonDefaultCanonicalLink/history/

It may be worth rerunning just to see if it wasn't a spurious failure.

Ah, cool, took me a few minutes to figure out the correct order to click on History to get to those pages you linked. Nice graphs. Jenkins could use better UI.
Ubuntu CI has one failure,
ContactSystemTest.MultipleCollisionsAsContactSensors, but looks like it's failed once before
https://build.osrfoundation.org/job/ignition_gazebo-ci-pr_any-ubuntu_auto-amd64/4316/testReport/(root)/ContactSystemTest/MultipleCollisionsAsContactSensors/history/

@osrf-jenkins run tests

Grabbing the results before Jenkins shuts down today.
Ubuntu CI:
https://build.osrfoundation.org/job/ignition_gazebo-ci-pr_any-ubuntu_auto-amd64/4319/
Test Result (2 failures / +1)
ContactSystemTest.MultipleCollisionsAsContactSensors
EntityComponentManagerPerfrormance.Each
I am not sure if the ContactSystem test came from this PR... I saw another failure before 4316, and I think the earlier one is not from this PR. I didn't write down the number.
/var/lib/jenkins/workspace/ignition_gazebo-ci-pr_any-ubuntu_auto-amd64/ign-gazebo/test/integration/contact_system.cc:118
Value of: contactMsgs.size()
  Actual: 3
Expected: 0u
Which is: 0

Mac CI:
https://build.osrfoundation.org/job/ignition_gazebo-ci-pr_any-homebrew-amd64/3997/
There's a seg fault still.
Test Result (2 failures / +1)
PeerTracker.PeerTrackerStale
UNIT_Server_TEST.test_ran
So looks like the ones from 3994 above were flaky.
These new ones did not fail in 3994. PeerTrackerStale failed for both 3997 and 3998. So these look flaky.

ignition_gazebo-ci-pr_any-homebrew-amd64 is still reporting some failures:
The following tests FAILED:
	 79 - INTEGRATION_joint_state_publisher_system (SEGFAULT)
	 83 - INTEGRATION_level_manager (Subprocess aborted)

The first one I don't see anywhere else.
Related to the second one, level manager had some related failures, on
LevelManagerPerfrormance.LevelVsNoLevel https://build.osrfoundation.org/job/ignition_gazebo-ci-ign-gazebo4-homebrew-amd64/4/
and INTEGRATION_level_manager_runtime_performers.test_ran https://build.osrfoundation.org/job/ignition_gazebo-ci-ign-gazebo4-homebrew-amd64/3/
ignition_gazebo-ci-pr_any-ubuntu_auto-amd64's 2 out of 3 failures are expected (LogSystemTest.LogResources and SdfInclude.DownloadFromFuel).
This one failed but shouldn't: ServerRepeat/VelocityControlTest.PublishCmd/0
However, seeing that all the code changes in this PR are strictly within a new directory src/systems/optical_tactile_plugin, I really don't think it should affect any of the tests at all...
Will rerun and see if these fail again.

@osrf-jenkins run tests

Alright, those two on homebrew-amd64 were flaky. Not failing on the rerun. Rerun fails on INTEGRATION_breadcrumbs which is flaky.
ubuntu_auto-amd64 still failing on ServerRepeat/VelocityControlTest.PublishCmd/0, which is unexpected.
Looks like it could be a precision problem, but it's not comparing >=, it wants >.
123: /var/lib/jenkins/workspace/ignition_gazebo-ci-pr_any-ubuntu_auto-amd64/ign-gazebo/test/integration/velocity_control_system.cc:128: Failure
123: Expected: (poses[i].Pos().X()) > (poses[i-1].Pos().X()), actual: 2.12913e-10 vs 2.13556e-10
123: /var/lib/jenkins/workspace/ignition_gazebo-ci-pr_any-ubuntu_auto-amd64/ign-gazebo/test/integration/velocity_control_system.cc:129: Failure
123: Expected: (poses[i].Pos().Y()) > (poses[i-1].Pos().Y()), actual: 2 vs 2

However, the previous run had 4 unexpected comparison outcomes, the latest one only has 2. So it could just be flaky.
I will rerun one more time to be careful.

@osrf-jenkins run tests

It looks like ServerRepeat/VelocityControlTest.PublishCmd/0 on ubuntu_auto-amd64 is really failing just for this PR. All other tests are passing. Need to look into it.

Huh, that test is failing elsewhere too
https://build.osrfoundation.org/job/ignition_gazebo-ci-pr_any-ubuntu_auto-amd64/4751/testReport/
https://build.osrfoundation.org/job/ignition_gazebo-ci-pr_any-ubuntu_auto-amd64/4752/testReport/
https://build.osrfoundation.org/job/ignition_gazebo-ci-pr_any-ubuntu_auto-amd64/4755/testReport/
I think it's flaky.
That is the last test failure. I'm ready to approve this. Might wait for a few more runs on this test to see if it fails more to be sure.

I looked again, the 3 failures of the same test above come from 3 different PRs, so it's definitely flaky. Merging this.

@mabelzhang was this just a regular merge? It looks like we forgot to squash the PR into one commit before merging. Here's the diff between ign-gazebo4 and a branch I created just before thus was merged: https://github.com/ignitionrobotics/ign-gazebo/compare/adlarkin/4.1.0...ign-gazebo4

Yes just a regular merge, sorry I wasn't sure what was the preferred method of merge and just went with the default. Noted for the future.


Could you possibly support Microsoft.EntityFrameworkCore 5.0.3?

See title. Reason being we use AspNetZero and dont want to change too much of the core project.

Actually, nvm. I can just dump the 2 files in my project and be done with it. Thanks for creating this lib in the first place.

yep! It's my mistake that it only supports version 5.0.5.
I'll downgrade it to support 5.0 asap.

done


Right click menu Image resizer gone

Microsoft PowerToys version
0.73.0
Installation method
GitHub
Running as admin
Yes
Area(s) with issue?
Image Resizer
Steps to reproduce

PowerToysReport_2023-09-26-16-46-10.zip
Hi,
I have an issue with the image resizer. It used to be automatically in the right click menu of a picture so you could use it. Now its not there anymore. I previously installed Powertoys from the Windows app store but removed and reinstalled it from Github to see if the issue would be solved like this. I thought it did, since the option was back again. Then, after closing Powertoys, so not actually closing the program but putting it into the tray, the option disappeared again.. And afterward did not came back. How can I solve this?
I have this version of Windows 11 Pro x64: 22H2 Build: 22621.2283
Thanks for any help you can offer.
✔ Expected Behavior
That the option for Image resizer would be in the right click menu of a picture.
❌ Actual Behavior
The option for image resizer was not present anymore in the right click menu.
Other Software
No response

Same. Worked fine until updating to latest version.

Does it appear after restarting the computer?
/needinfo

No, after a reboot the situation is still the same.
-------- Oorspronkelijk bericht --------
Op 26 sep. 2023 20:04, schreef Davide Giacometti :

Does it appear after restarting the computer?
/needinfo
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Can you post a bug report?
/bugreport

It's already in my first message. The link is under the screenshot.
-------- Oorspronkelijk bericht --------
Op 26 sep. 2023 20:41, schreef microsoft-github-policy-service[bot] :

Hi there!
We need a bit more information to really debug this issue. Can you add a "Report Bug" zip file here?  Then drag the zipfile from your desktop onto the GitHub comment box in this issue. Thanks!
Report Bug
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Sorry, I missed that!

No worries, we're all human 🙏. Thanks for looking into the issue!
-------- Oorspronkelijk bericht --------
Op 26 sep. 2023 23:09, schreef Davide Giacometti :

Sorry, I missed that!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Unfortunately there is nothing useful in the report.
Can you attempt to update to the new releases 0.74 and see how it goes?
These Explorer extensions require a restart after the upgrade.
/needinfo

Ok, so I think it’s not a bug in Powertoys per se, but rather a reorganization of Windows 11. See the screenshot. The options for Image resizer and Power rename have now moved to the section of “more options” when you right click on the mouse.
I have updated to the most recent version of powertoys btw. And, at first after the update and a reboot, the option for image resizer was present again in the right click menu. But once again, this was only once, after that the situation stayed as described above.
Van: Davide Giacometti @.>
Verzonden: woensdag 27 september 2023 11:22
Aan: microsoft/PowerToys @.>
CC: Kas152 @.>; Author @.>
Onderwerp: Re: [microsoft/PowerToys] Right click menu Image resizer gone (Issue #28779)
Unfortunately there is nothing useful in the report.
Can you attempt to update to the new releases 0.74 and see how it goes?
These Explorer extensions require a restart after the upgrade.
/needinfo
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Also, when trying to acces the settings through the gear button in Image resizer this does not work. A screen pops up but disappears immedeately. See screenshot.

ImageResizer is also supposed to stay in the first section of the right click menu.
For the settings issues: are you able to open settings with a double click on the PowerToys icon on the taskbar?

I see, ok good to know.
About double clicking in the tray icon: no the same happens, a flash of trying to open the program and then it closes. This happens with double clicking and also with clicking the icon once (a submenu should appear). Even right clicking the icon and then clicking settings has the same result.

yes
I would have replied earlier but gmail had this in my Spam folder.
-Don
On Tue, Sep 26, 2023 at 1:04 PM Davide Giacometti @.***>
wrote:

Does it appear after restarting the computer?
/needinfo
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/28779#issuecomment-1736030831,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BCVIZXVLF5VAIHOLDJJEBD3X4MKMBANCNFSM6AAAAAA5H3XJ3M
.
You are receiving this because you commented.Message ID:
@.***>

Has there been any progress in this matter?

Has there been any progress in this matter?

Thanks for fixing the issue! Its solved now with the latest update 👍

An extra note for those using OneDrive.
If the image is on OneDrive cloud only, we will see "Resize with Image Resizer" in context menu (right-click menu) AFTER downloading to local drive.


thumbnail omits 0.5 pixels from each edge of image

🐛 Bug
The thumbnail extent seems to go from the center of the first pixel to the center of the last pixel, omitting the outer 0.5 pixels. You can see this by looking at the thumbnail appearance in the image below for a small 3x3 image. All but the central square are missing half their width in the thumbnail:

To Reproduce
import napari
import numpy as np

v = napari.Viewer()
labels = np.arange(1, 10).reshape(3, 3)
v.add_labels(labels)
napari.run()

Expected behavior
The thumbnail should cover the full pixel extents
Environment
current development branch of napari
Additional context
Fortunately, this issue will not really be noticeable for thumbnails of more realistically sized images.

As a broader comment on thumbnails generally not matching the canvas (see also, https://github.com/napari/napari/pull/4267#issuecomment-1069561112,  #3581, https://github.com/napari/napari/issues/3409, and other general "thumbnail mismatch" issues), we've talked often about the "ultimate" fix here being to somehow use vispy to render to an offscreen canvas buffer, using the same rendering logic as the layer-in-canvas.  This would also avoid needing to keep two rendering paths (CPU and GPU) in sync as they evolve.
I'm not sure it's going to be a trivial fix, but I'm also not sure it would be too hard?  and it would likely solve a big swath of issues in one fell swoop :)

@grlee77 hi there, do you still plan to take this one on? if not I can unassign it. Thanks!

No, I don't plan to work on it. Thanks


User font-awesome as icon for blocks

http://fontawesome.io/icons/

One Font, 634 Icons
No JavaScript Required
Infinite Scalability
Free, as in Speech
CSS Control
Perfect on Retina Displays
Plays Well with Others
Desktop Friendly
Accessibility-minded

https://github.com/alexgleason/wagtailfontawesome

The plugin above achieves Font Awesome support.
But I think there's a discussion to be had about including a more expansive iconset in core, be it Font Awesome or one of the many others. Or a combination.

http://fontawesome.io/icons/
http://ionicons.com/
https://octicons.github.com/

Torchbox can expand his iconset, i think that will be a better and unique solution.

I think bundling an icon font in Wagtail would be annoying to maintain, as the release cycles for Wagtail and Font Awesome do not line up, and old Wagtails would be stuck with old versions of Font Awesome. However, if Wagtail depended upon wagtailfontawesome (or some similar package), these issues would disappear, while still effectively shipping an expanded icon library with Wagtail.

IMO it's the least of our worries if the latest version of Wagtail doesn't always include the 10 random new icons Font Awesome added recently. The existing iconset has worked in 95% of the blocks I've built.

Let's continue the discussion at #2349, as this conversation is covering much the same ground as the earlier one.


test

Signed-off-by: Hyeonykim<EMAIL_ADDRESS>

File
Coverage [0%]
:x:

HelloWorld.java
0%
:x:

Total Project Coverage
0%
:x:

File
Coverage [0%]
:x:

HelloWorld.java
0%
:x:

Total Project Coverage
0%
:green_apple:

File
Coverage [0%]
:green_apple:

HelloWorld.java
0%
:green_apple:

Total Project Coverage
0%
:green_apple:

File
Coverage [0%]
:green_apple:

HelloWorld.java
0%
:green_apple:

Total Project Coverage
23.81%
:green_apple:

File
Coverage [0%]
:green_apple:

HelloWorld.java
0%
:green_apple:

Total Project Coverage
23.81%
:green_apple:

File
Coverage [0%]
:green_apple:

HelloWorld.java
0%
:green_apple:

Total Project Coverage
23.81%
:green_apple:

File
Coverage [0%]
:green_apple:

HelloWorld.java
0%
:green_apple:

Total Project Coverage
23.81%
:green_apple:

File
Coverage [0%]
:green_apple:

HelloWorld.java
0%
:green_apple:

Total Project Coverage
23.81%
:green_apple:

File
Coverage [0%]
:green_apple:

HelloWorld.java
0%
:green_apple:

Total Project Coverage
23.81%
:green_apple:

File
Coverage [0%]
:green_apple:

HelloWorld.java
0%
:green_apple:

Total Project Coverage
23.81%
:green_apple:

File
Coverage [0%]
:green_apple:

HelloWorld.java
0%
:green_apple:

Total Project Coverage
23.81%
:green_apple:

File
Coverage [23.81%]
:green_apple:

Greeter.java
100%
:green_apple:

HelloWorld.java
0%
:green_apple:

Total Project Coverage
23.81%
:green_apple:

File
Coverage [23.81%]
:green_apple:

Greeter.java
100%
:green_apple:

HelloWorld.java
0%
:green_apple:

Total Project Coverage
23.81%
:green_apple:

File
Coverage [23.81%]
:green_apple:

Greeter.java
100%
:green_apple:

HelloWorld.java
0%
:green_apple:

Total Project Coverage
23.81%
:green_apple:

File
Coverage [23.81%]
:green_apple:

Greeter.java
100%
:green_apple:

HelloWorld.java
0%
:green_apple:

Total Project Coverage
23.81%
:green_apple:

File
Coverage [23.81%]
:green_apple:

Greeter.java
100%
:green_apple:

HelloWorld.java
0%
:green_apple:

Total Project Coverage
23.81%
:green_apple:

File
Coverage [23.81%]
:green_apple:

Greeter.java
100%
:green_apple:

HelloWorld.java
0%
:green_apple:

Total Project Coverage
23.81%
:green_apple:

File
Coverage [23.81%]
:green_apple:

Greeter.java
100%
:green_apple:

HelloWorld.java
0%
:green_apple:

Total Project Coverage
23.81%
:green_apple:

File
Coverage [23.81%]
:green_apple:

Greeter.java
100%
:green_apple:

HelloWorld.java
0%
:green_apple:

Total Project Coverage
23.81%
:green_apple:

File
Coverage [23.81%]
:green_apple:

Greeter.java
100%
:green_apple:

HelloWorld.java
0%
:green_apple:

Total Project Coverage
23.81%
:green_apple:

File
Coverage [23.81%]
:green_apple:

Greeter.java
100%
:green_apple:

HelloWorld.java
0%
:green_apple:

Total Project Coverage
23.81%
:green_apple:

File
Coverage [23.81%]
:green_apple:

Greeter.java
100%
:green_apple:

HelloWorld.java
0%
:green_apple:

Total Project Coverage
23.81%
:green_apple:

File
Coverage [23.81%]
:green_apple:

Greeter.java
100%
:green_apple:

HelloWorld.java
0%
:green_apple:

Total Project Coverage
23.81%
:green_apple:

File
Coverage [23.81%]
:green_apple:

Greeter.java
100%
:green_apple:

HelloWorld.java
0%
:green_apple:

Total Project Coverage
23.81%
:green_apple:

File
Coverage [23.81%]
:green_apple:

Greeter.java
100%
:green_apple:

HelloWorld.java
0%
:green_apple:

Total Project Coverage
23.81%
:green_apple:

File
Coverage [23.81%]
:green_apple:

Greeter.java
100%
:green_apple:

HelloWorld.java
0%
:green_apple:

Total Project Coverage
23.81%
:green_apple:

File
Coverage [23.81%]
:green_apple:

Greeter.java
100%
:green_apple:

HelloWorld.java
0%
:green_apple:

Total Project Coverage
23.81%
:green_apple:


Attestation-Service: SNP verifier claim set should include CURRENT_TCB

On SEV_SNP microcode-only updates to a PSP might not be reflected in an snp report's reported_tcb.microcode field, but only in current_tcb.microcode. Currently we are only including the reported_tcb.* fields in the claim-set. To express a microcode only-update in a policy, we would want to include current_tcb.*.
cc @fitzthum
Folks at AMD should confirm the above reasoning makes sense, I'm not entirely sure. cc @ryansavino @larrydewey

I am a little confused by this behavior. According to 56860

ReportedTcb is initially set to the CurrentTcb. When SNP_CONFIG is invoked with a non-zero
REPORTED_TCB parameter, ReportedTcb is set to the provided value. ReportedTcb is reset to
CurrentTcb either on SNP_COMMIT or if SNP_CONIFG is provided a zero REPORTED_TCB.

Is this not true in the case of microcode-only updates?

according to this presentation (p11) current_tcb would indeed be merely "informational"

...
AFAIU reported_tcb is meant to cover a specific situation: Assume a given policy asserts tcb.fw_version == 1.0. Now the infra owner applies a patch on the system to bump the PSP firmware to 1.1. The assertion in the policy would fail, potentially breaking things for the guest owner. Hence at guest creation the infra owner can opt to still report tcb.fw_version: 1.0 at guest creation. until the guest owner adjust their policy accordingly.
That would reflect the situation in the initial comment. The infra-owner applied a microcode update, but the hypervisor chose to report an older TCB to the guest. In this sense everything works as designed.
Now, the guest owner might not be able to influence launch parameters of their specific virtual machine. In a public cloud reported_tcb might be configured globally to the fleet and be updated conservatively. In this case there's no way for the guest owner to write an attestation-service policy asserting TCB values larger than the reported one, even if the fleet has been patched. 🤔
(rephrasing the issue title)

related slack discussion about issues in the spec: https://cloud-native.slack.com/archives/C03K97S5JQL/p1695202432334559

I agree that this is the idea of the REPORTED_TCB. I am trying to understand if the behavior that you are seeing is the result of a bug or if the hypervisor is deliberately avoiding updating the REPORTED_TCB. While there is value in being conservative about the REPORTED_TCB, if there is a critical update that the user will expect to verify, I think the CSP should update the REPORTED_TCB to reflect the new version. Ofc this isn't really my decision to make. I wouldn't mind adding the extra fields to the claims map although I'm not sure that it's ideal for users to write policies that depend on the current TCB except in this particular case.

@mkulke do you remember what we concluded here? Can we close this?

I don't remember the conclusion either (probably there was none) and I think there has been some change in behaviour since, so let's revive this once it pops up again.


CLI options?

Great tool, thank you for this!
Is there a way to give arguments via cli to only output the addresses and amounts, as opposed to the whole thing?
And perhaps pointing to the chainstate location instead of copying it to the script first?
Sorry, I don't know C++, or programming in general that well to understand all the files.
Thanks.

@secretnumber Copying the chainstate is required because for some reason, and despite the fact chainstate doesn't modify the database, the wallet won't want to reuse it after having used chainstate against it. I still need to find out why.
I think the whole tool would require a lot of rewrite, and may be some day I'll take some time to add arguments & customization... but so far, it is a crappy hack... sorry for that!


Fix crash when exporting without assigned material

Simply moved the if statement to check for use_nodes on the material inside the
check if a material is actually given. This otherwise crashed with
AttributeError: 'NoneType' object has no attribute 'use_nodes'
if no material were assigned to a model prior to exporting it.

Thanks, I hope it's OK that I took the liberty of merging this since other people were running into this issue.

I did the same in opened pull request #41 , but doesn't matter. Please close it and also the associated issue.


On Battery Power, Awake does not work.

Microsoft PowerToys version
0.51.1
Running as admin

[X] Yes

Area(s) with issue?
Awake
Steps to reproduce
With my laptop plugged in, Awake works as intended and keeps my computer awake for the set amount of time (set for 3 hours currently).
On battery power, my laptop goes to sleep after 15 minutes although Awake has been turned on and set to keep my device awake.
This has only been happening since the most recent update.

PowerToysReport_2021-12-21-16-54-01.zip
✔ Expected Behavior
Awake to keep my device from going to sleep regardless of whether it is plugged in or on battery power.
❌ Actual Behavior
On battery power, my device still goes to sleep based on the current Power settings.
Other Software
No response

Please check this out: https://github.com/microsoft/PowerToys/issues/14225#issuecomment-996690135

duplicate of https://github.com/microsoft/PowerToys/issues/14225#issuecomment-996690135


RSA+SHA224 sigalg removed from master

Hello,
We use the s_client app for TLS integration tests against our server implementation. When using s_client compiled Openssl master, I noticed the RSA+SHA224 sigalg is no longer available.  A git-bisect shows 703bcee021 introduced this, but doesn't mention removing sha224. Was this sigalg intentionally removed?  If it was intentional(probably because it is removed in TLS1.3 and rarely in existing TLS systems) it is worth calling it out somewhere in the docs.
# s_client failure
> ./libcrypto-root-master/bin/openssl version
OpenSSL 1.1.1-dev  xx XXX xxxx
> ./libcrypto-root-master/bin/openssl s_client -connect s3.amazonaws.com:443 -sigalgs "RSA+SHA224"
Error with command: "-sigalgs RSA+SHA224"

Thanks

No, that commit is unrelated.
It worked in 1.0.2?  It should not have been removed in 1.1.  ping @mattcaswell

Works in latest 1.0.2 and 1.1.0 releases:
> /usr/local/openssl-1.1.0f/bin/openssl version
OpenSSL 1.1.0f  25 May 2017
 echo "Q" | /usr/local/openssl-1.1.0f/bin/openssl s_client -connect s3.amazonaws.com:443 -sigalgs "RSA+SHA224"
CONNECTED(00000005)
...
Peer signing digest: SHA224
Server Temp Key: ECDH, P-256, 256 bits
...
New, TLSv1.2, Cipher is ECDHE-RSA-AES128-GCM-SHA256
DONE

> /usr/local/openssl-1.0.2l/bin/openssl version
OpenSSL 1.0.2l  25 May 2017
> echo "Q" | /usr/local/openssl-1.0.2l/bin/openssl s_client -connect s3.amazonaws.com:443 -sigalgs "RSA+SHA224"
CONNECTED(00000003)
...
Peer signing digest: SHA224
Server Temp Key: ECDH, P-256, 256 bits
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES128-GCM-SHA256
...
DONE

Fix in #3639

Thanks!


Update http4s-client, http4s-core, ... to 0.23.8

Updates

org.http4s:http4s-client
org.http4s:http4s-core
org.http4s:http4s-dsl

from 0.23.0-RC1 to 0.23.8.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s" } ]

labels: library-update, early-semver-minor, semver-spec-pre-release, commit-count:1

Superseded by #536.


Error: No Policies Found!

Hi Christian - thanks for creating tis action - I am having trouble getting it to work.
Would you be able to take a look at my actions code and repo?
https://github.com/leizerbeam/soteria/actions

Hi @leizerbeam,
thanks for using my action. I'm not completely sure what the error is, but you first checkout the repos main and then at the already existing subfolder main again. Maybe the file structure is not the expected one. Could you add a "ls - l" in the kyverno folder?

I am not too familiar with GitHub actions code - I was copying your example 3 (policy code in git), what would I put to list the code?

You can just remove the "Checkout kyverno" step when the YAMLs you want to test and the policy-files are in the same repo.
Otherwise add this between the "Checkout kyverno" and "kyverno-test-policy":
- name: List files
  run: ls -l kyverno

Here is the screenshot. The folder is basically the root of my project

Yes, there's a nested kyverno folder from the second checkout. This overwrites the policies from this folder. Please try to remove the second checkout

progress! however I noticed it may not running the policy tests

I have tested the below policies using the Kyverno CLI and the Admission Controller on my K8s Cluster.
- name: kyverno-test-policy         # You may pin to the exact commit or the version.         # uses: ckotzbauer/kyverno-test-action@1c306c7062d34cf7648b831f8a28af7ecb7a13ae         uses: ckotzbauer/kyverno-test-action@v2         with:           # Github token           token: ${{ github.token }}           # Enter all application manifests here (Location Profiles, Data Protection Policies, Application Manifests)           resource-files: |             kyverno/backup-export-policy.yaml           # Test that the resource meets all required data protection policies           policy-files: |             kyverno/enforce-3-2-1.yaml             kyverno/enforce-data-protection-by-label.yaml             kyverno/enforce-minimum-retentions.yaml             kyverno/enforce-mission-critical-rpo.yaml

OK I understand that kyverno "test" functionality is not really ideal of the GitHub actions use case - I believe you are passing those resource-files and policy-files. But in order to generate an "Error" output that would be captured by Github actions, it is preferred to use the kyverno 'apply' which will generate the fail message.
The above code will always show 0 pass, 0 failed unless the 'variables.yaml' is included.I did this with mixed results

Hi - an alternative I see here is to use an additional section the required code to define the test result expectations (pass/fail)
results:

policy: disallow-empty-ingress-host
rule: disallow-empty-ingress-host
resource: ingress-wildcard-host
result: pass
kind: Ingress
policy: disallow-empty-ingress-host
rule: disallow-empty-ingress-host
resource: minimal-ingress
result: fail
kind: Ingress

Okay, some notes from me:

I have tested the below policies using the Kyverno CLI "apply" CLI vs the "test" functionality. Now I realize there is a config file needed here (kyverno-test.yaml) per https://kyverno.io/docs/kyverno-cli/#run-tests-on-a-git-repo

Yes, this action uses the "test" command. (Can be added to the docs)
Yes, there's a test-config-file needed for that. This is dynamically generated from this action accoring your resources and the given policies. No need to write this manually.

Also, you may want remove the 2nd checkout of the repo in your example since it caused my earlier bug.

You refer to the third example. This is meant to be used for the case, when your policies are in another repository. The first two examples do not have this additional checkout. So I won't remove this from the example, as its intended.

This action needs another section to trigger pass/fail checks - we need the optional "results" block to define the test result expectations (pass/fail) policy tests. If not, then you get 0pass/0fail every time running kyverno test.

The generated test-configs are using the "pass" result as expectation. This action is not useable for complete "unit-tests" of policies, so no "fail" result is ever expected. This action is designed to test YAMLs against a set of policies and all have to pass to pass this action.
Maybe I didn't fully understand your intention, please clarify if needed.

Regarding the current behavior, if the "results" block is not specified, the kyverno test command will always pass, regardless if the policies pass or not, this is because the CLI shows a "0 passed, 0 failed" output. if you see my first screenshot, I had an intentional error, and the action did not fail properly.

Then I inserted a manual run command for "kyverno test ." (this accepts the "kyverno-test.yaml" file that I had documented with a results block - this is my 2nd screenshot.

I think its a good unit test action with these few enhancements.  This is just my recommendation based on practicality, but you're the owner so I will let you decide.  Thanks for listening to my feedback.


Investigate: potential bug causing infinite loop on _terminate

@pierreca was seeing an infinite loop in the -ws transport when we called _terminate due to a timeout on a bad endpoint. See https://github.com/noodlefrenzy/node-amqp10-transport-ws/pull/2.

we should be able to recreate this by trying to connect to an invalid host right?

Yes, using the websocket transport. here's what happens:

try to connect to an invalid host
the socket (under websockets) returns an error (ENOTFOUND) that is propagated through events to amqp10
amqp10 calls _terminate
_terminate calls transport.end() (from amqp10 to transport)
transport.end() calls socket.close() (from transport to websocket lib)
in the websocket library, a 'close' event is emitted (every time the socket.close() is called)
the transport relays the close event to the amqp10 library
amqp10 receives the close event and calls _terminate... and there we go in a loop that ultimately ends in a stack overflow

it could also be the websocket library's fault for emitting a close event everytime close is called even though the socket is already closed...

@pierreca @noodlefrenzy what's going on with this issue?

Looks like we found a solution for that problem with the ws transport but @noodlefrenzy was keeping this open to investigate further. Not sure how it plays with the release of v3 now.


Update all Management endpoints' content negotiation to V3

Add new MediaTypeVersion V3 and ActuatorMediaType and add content negotiation logic for the latest version (V3).

This appears to be resolved by #887


Split Calyx into various crates

Some questions:

Why does interp depend on calyx_frontend and calyx_opt? Can we remove the dependency and rely on fud to execute Calyx passes for the interpreter?
Similarly, lots of tools need to rely on calyx_frontend. Maybe some way to change that (time for a bitcode!!)

TODO

[x] Build the docs website correctly
[x] Make cargo run -- <file> work again
[ ] Fix links in the documentation that point to the source code docs (Add a new pass from #1394)

Looks super useful! Was just wondering if you had an idea of how you were going to split things up/what is going to go where? I see a calyx_utils crate but want to make sure I have the full picture!

@priyasrikumar first pass on splitting up was trying to keep folders in calyx/src/ together while keeping a DAG dependency graph. The most unintuitive thing currently split up is putting some ir structures like Primitive in frontend because we never change their representation.

Not clear why we should have traversal stuff in the IR instead of the passes package (calyx-opt)

Okay, this has a couple of potentially controversial choices:

Some IR-related data structures like Primitive and Port live inside frontend. This is because their representation is not changed during the frontend -> IR conversion. The downside is that it makes the frontend and the parser a hard dependency for the IR which might not be desirable
Disables the building of source-code documentation. AFAIK, we never really used it to any large extent but it might be worth recreating for the Calyx tutorial

@EclecticGriffin @sampsyo @priyasrikumar @anshumanmohan thoughts?

Super cool; a big crate split like this seems like it will make a few things much easier.
About the "reverse dependency" on the frontend: makes sense to me! Probably an extremely naive question: any particular reason why these shouldn't go in the IR crates instead? The frontend could just have a type alias that says "my Port is the same as the IR's Port" or something. But truly, if this is the way things currently are, that decoupling could come in a future step, and obviously isn't a big deal immediately because we have the luxury of being in a monorepo.
Maybe in the future, we would want source code documentation back for only the IR crate. Not sure.

Yeah, a weird dependency issue is that the AST to IR conversion needs access to IR internals that shouldn't be generally exposed and is therefore in the IR crate. However, this creates a AST -> IR dependency so we can't move the structures in IR because that would create an IR -> AST dependency

Also we're running into a failure because cargo run can no longer find the futil binary is probably not building it correctly

Got it; thanks for explaining!
That makes it seem to me that the long-term decoupling solution is:

Move AST-to-IR transformation to the frontend crate.
Create an appropriately public API for constructing IR that suffixes to enable the above.
Move Primitive & Port to the IR crate, and either use them directly from the AST crate or conjure carbon copies of them in the AST crate.

Needless to say, that's definitely future work not for this PR…

All right, this beast is ready to be merged. We'll need to fix some links here and there but it should be fine

Incidentally, love the branch name!


Remove unneeded dependencies

inquirer          | 11.4s | 5.2 MB | 15

@trevorsg - any background on inquirer? It doesn't appear to be used, and is one of the top (by size of it and its dependencies) dependencies in tfs-cli.

I think this was an old dependency before I rewrote tfx. I can try removing it.


[Bug]  ERROR  Warning: Function components cannot be given refs.

The error warning occurs when following the guide to build and run the example app [Example App] (https://github.com/5-stones/react-native-readium/blob/main/example/README.md). It is shown in Metro after the app starts (see screenshot). There is also a warning pop up in the app itself (see second screenshot).

@robert-elles I've just merged an upgrade to the latest stable version of react-native. If you're still able, it'd be great to get your branched rebased on main. Then I'll pull it down and test it. If you're not able to rebase, I'll just have to fork your branch and do the rebase myself. LMK.

Fixed by https://github.com/5-stones/react-native-readium/pull/61


[Imporve][Connector-V2] Imporve iotdb connector

Purpose of this pull request
Source:

Add e2e testcase
Add example into documents
Support align by sql syntax
Support sql split ignore case
Support restore split offset to at-least-once
Support read timestamp from RowRecord
Fix assign split: splitId % taskSize -> splitId % readerSize

Sink:

Support extract timestamp、device、measurement from SeaTunnelRow
Support TINYINT、SMALLINT
Add example into documents
Support flush cache to database before prepareCommit

Check list

[x] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[x] If necessary, please update the documentation to describe the new feature. https://github.com/apache/incubator-seatunnel/tree/dev/docs

Can you move e2e IT to seatunnel-connector-v2-e2e module? you can see #2924.
spark doesn't work


[Expression] json() failure

json() fails for for the following string
{"d":{"__copyright":"\u00a9 2020 Microsoft and its suppliers. This API and any results cannot be used or accessed without Microsoft's express written permission.","results":[{"__metadata":{"uri":"http:\/\/spatial.virtualearth.net\/REST\/v1\/data\/20181f26d9e94c81acdf9496133d4f23\/FourthCoffeeSample\/FourthCoffeeShops('-11849')"},"EntityID":"-11849","Latitude":47.608022,"Longitude":-122.191012,"AddressLine":"300 112th Ave SE","PrimaryCity":"Bellevue","SecondaryCity":"","Subdivision":"WA","CountryRegion":"United States","PostalCode":"98004","Phone":"1-800-XXX-XXXX","Manager":"Jolie Lenehan","StoreOpen":"Y","StoreType":"Drive-Thru","Name":"Fourth Coffee Store #11849","DisplayName":"Fourth Coffee Store #11849, Bellevue, WA, United States","IsWiFiHotSpot":false,"SeatingCapacity":"","IsWheelchairAccessible":false,"AcceptsOnlineOrders":false,"AcceptsCoffeeCards":true,"Open":700,"Close":1800,"CreatedDate":"\/Date(634250351766060665)\/","LastUpdatedDate":"\/Date(634254671766060665)\/","__Distance":0.321865488068692},{"__metadata":{"uri":"http:\/\/spatial.virtualearth.net\/REST\/v1\/data\/20181f26d9e94c81acdf9496133d4f23\/FourthCoffeeSample\/FourthCoffeeShops('-11885')"},"EntityID":"-11885","Latitude":47.617235,"Longitude":-122.193123,"AddressLine":"11025 NE 8th St","PrimaryCity":"Bellevue","SecondaryCity":"","Subdivision":"WA","CountryRegion":"United States","PostalCode":"98004","Phone":"1-800-XXX-XXXX","Manager":"Tad Orman","StoreOpen":"N","StoreType":"Drive-Thru","Name":"Fourth Coffee Store #11885","DisplayName":"Fourth Coffee Store #11885, Bellevue, WA, United States","IsWiFiHotSpot":false,"SeatingCapacity":"","IsWheelchairAccessible":false,"AcceptsOnlineOrders":false,"AcceptsCoffeeCards":true,"Open":600,"Close":2300,"CreatedDate":"\/Date(634250351766060665)\/","LastUpdatedDate":"\/Date(634254671766060665)\/","__Distance":0.893310102166956},{"__metadata":{"uri":"http:\/\/spatial.virtualearth.net\/REST\/v1\/data\/20181f26d9e94c81acdf9496133d4f23\/FourthCoffeeSample\/FourthCoffeeShops('-11856')"},"EntityID":"-11856","Latitude":47.609561,"Longitude":-122.200289,"AddressLine":"144 105th Ave SE","PrimaryCity":"Bellevue","SecondaryCity":"","Subdivision":"WA","CountryRegion":"United States","PostalCode":"98004","Phone":"1-800-XXX-XXXX","Manager":"Jenny Lysaker","StoreOpen":"Y","StoreType":"Kiosk","Name":"Fourth Coffee Store #11856","DisplayName":"Fourth Coffee Store #11856, Bellevue, WA, United States","IsWiFiHotSpot":false,"SeatingCapacity":"","IsWheelchairAccessible":true,"AcceptsOnlineOrders":false,"AcceptsCoffeeCards":true,"Open":800,"Close":2200,"CreatedDate":"\/Date(634250351766060665)\/","LastUpdatedDate":"\/Date(634254671766060665)\/","__Distance":0.9302848346961}]}}

Error:
Ticks must be between DateTime.MinValue.Ticks and DateTime.MaxValue.Ticks. (Parameter ‘ticks’)

After narrow down after several binary breakdown,
{"CreatedDat":"/Date(634250351766060665)/"}
will cause JToken.parse to fail, looking into more details now

Further more, the issue is the default date parsing in JToken.parse is enabled and not support window tickts well, because by default it seems to looks for linux epoch time.
So the fix for now, is to disable the datetime parsing, later we may add parameters for people to control the process.


add/remove worker node; 2. using private key to deploy cluster

What type of PR is this?
/kind feature

What this PR does / why we need it:

add worker node
remove worker node
deploy cluster using private key
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

/lgtm


Uncaught SyntaxError: Unexpected token < when importing Modal

Hi, I'm starting from a simple quick start angular 2 project and I installed angular2-modal via npm
npm install angular2-modal --save
And now I have

angular2-modal/

dist/
docs/
src/
...

in my node_modules folder.
As soon as I import Modal in one of my component and add it to the providers array, I get an error
Uncaught SyntaxError: Unexpected token <
Evaluating http://localhost:3000/angular2-modal/src/components/angular2-modal/providers/Modal
Error loading http://localhost:3000/app/main.js

This is the component:
import {Component} from 'angular2/core';
import {Modal} from 'angular2-modal/src/components/angular2-modal/providers/Modal';

@Component({
    selector: 'my-app',
    template: `

My First Angular 2 App

            <button (click)="test()">Test</button>
    `,
    providers: [Modal],
})
export class AppComponent {
    constructor() {}

    test() {
        //here I want to open a modal
    }
}

I'm sure that I'm missing something, but don't know what

I got the same problem. Any updates here?

No, I still haven't figured out what is missing.

+1

You are trying to access it the wrong way.
Try doing import {Modal} from 'angular2-modal';
NPM packages should be loaded by name, not by path.
Loading by name ensures the package is loaded in the right order.
If you load by name you can't tell if something is missing in the runtime.
Also, please note that there are 2 directories, dist & src.
The src is there for debugging, hitting a breakpoint in the typescript files and not in the complied ES5 files, it is not intended for runtime use.
If you load the package using import 'angular2-modal' it will load from dist folder.
If later in your app you try something like import {...} from 'angular2-moda/src/... you are entering a type black hole and will probably result in 2 instances of angular2-modal running in your app.
That is, if you have a typescript compiler.

Thanks for your reply, but also with import {Modal} from 'angular2-modal'; I get the same error.

me too

It seems to be a problem related to the configuration with system.js (see here).
So I tried to change my index.html (following the proposed solution) in this way:
System.config({
  packages: {
    app: {
      format: 'register',
      defaultExtension: 'js'
    },
    'angular2-modal': {}
  },
  map: {
    'angular2-modal': 'node_modules/angular2-modal'
  }
});

But nothing changed.

I'm trying to rebuild your example.
Importing via import {Modal} from 'angular2-modal'; doesn't work and shows me the following error msg: "Unexpected token '<'↵	Evaluating http://localhost:3000/node_modules/angular2-modal↵	Error loading http://localhost:3000/app/boot.js"

Finally I resolved thanks to the Mapaxe comment here.
So, I changed my index.html
packages: {
  app: {
    format: 'register',
    defaultExtension: 'js'
  },
  'angular2-modal': {
    defaultExtension: 'js'
  }
},
map: {
  'angular2-modal': 'node_modules/angular2-modal/dist'
}

and imported the modules
import {Modal, ModalConfig, ...} from 'angular2-modal/angular2-modal';

Hi @tlorenzetti, thank you for creating this thread and posting the solution!
Would you be so kind to please share the syntax you used to open a test modal window? I am also working with quickstart-angular-2 project but I can't make the modals works although the import works successfully.

Hi @kat-liger, just follow the demo (source code here).
However, here is an example with a button than opens a simple confirm modal.
import {Component, Injector, provide} from 'angular2/core';
import {Modal, ModalConfig, ModalDialogInstance, YesNoModal, ICustomModal, YesNoModalContent} from 'angular2-modal/angular2-modal';

@Component({
    selector: 'my-app',
    template: `
        <button class="btn btn-primary" (click)="openModal()">Open</button>
        {{lastResult}}
    `,
    providers: [Modal],
})
export class AppComponent {
    private lastResult;

    constructor(private modal: Modal) {}

    openModal() {
        let component = YesNoModal;
        let dialog: Promise<ModalDialogInstance>;

        var modalContent = new YesNoModalContent('Modal title', 'Modal content', false, "Ok", "Cancel")
        let bindings = Injector.resolve([provide(ICustomModal, {useValue: modalContent})]);

        var modConf = new ModalConfig("sm", true, null);

        dialog = this.modal.open(<any>component, bindings, modConf);
        dialog.then(
            resultPromise => {
                return resultPromise.result.then(
                    result => {
                        this.lastResult = result; //result is true
                    },
                    () => this.lastResult = 'Canceled' //result is false
                );
            }
        );
    }
}

You can also create a custom modal by creating a Component that implements ICustomModalComponent and providing content to configure it (see AdditionCalculateWindow and AdditionCalculateWindowData in this example).
I hope this helps, let me know :)
Cheers,
Tiziano

Thank you, @tlorenzetti!
That's a great example, only now I realized I forgot to include Modal into the providers array, and as soon as I do it, I am back to square one:
Uncaught SyntaxError: Unexpected token <
Evaluating http://localhost:3000/node_modules/angular2-modal/dist/
Error loading http://localhost:3000/app/main.js
I tried all the proposed solutions, no luck so far.

I think i got this all working for me @kat-liger .
The file structure change a little bit in the dist folder.
in the System.config on the front HTML page i added /commonjs to the map
packages: {                         app: {                               format: 'register',                               defaultExtension: 'js'                         },                           'angular2-modal': {                             defaultExtension: 'js'                           }                   },                   map: {                           'angular2-modal': 'node_modules/angular2-modal/dist/commonjs'                   }
then the examples provided worked for me.  Thanks everyone


Blank page after new network registration

The issue appeared after the following network registration, before the app was working fine:

Name: Oxfordnet
Node: https://rpc.oxfordnet.teztnets.xyz

Self explained video, I am hard reloading (Ctrl + Shift + R) meanwhile:
https://github.com/trilitech/umami-v1/assets/30560280/6e508786-0031-4234-971c-d2ed6b4d9840
Information of interest

OS: Ubuntu 20.04.5 LTS
Installed version of umami (latest in snap):

$ snap list umami
Name   Version  Rev  Tracking       Publisher  Notes
umami  0.9.10   30   latest/stable  umami-nl   -

Embedded browser partial logs:

Failed to load resource: the server responded with a status of 404 ()
https://rpc.oxfordnet.teztnets.xyz/chains/main/blocks/head/context/contracts/<My main PK>/delegate
...

Ubuntu terminal partial logs:
$ umami
Gtk-Message: 01:25:20.792: Failed to load module "canberra-gtk-module"
Gtk-Message: 01:25:20.797: Failed to load module "canberra-gtk-module"
[7726:0914/012520.864750:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.DBus.ListNames: object_path= /org/freedesktop/DBus: org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.179" (uid=1000 pid=7726 comm="/snap/umami/30/umami/umami --no-sandbox --enable-c" label="snap.umami.umami (enforce)") interface="org.freedesktop.DBus" member="ListNames" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus)
/usr/share/libdrm/amdgpu.ids: No such file or directory
Checking for update
Error: Error: ENOENT: no such file or directory, open '/snap/umami/30/umami/resources/app-update.yml'
oops, an error:  [Error: ENOENT: no such file or directory, open '/snap/umami/30/umami/resources/app-update.yml'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/snap/umami/30/umami/resources/app-update.yml'
}
[7726:0914/012615.579502:ERROR:CONSOLE(1)] "Request Network.loadNetworkResource failed. {"code":-32602,"message":"Unsupported URL scheme"}", source: devtools://devtools/bundled/core/protocol_client/protocol_client.js (1)
...

Maybe the app is rendering the following page:
https://github.com/trilitech/umami-v1/blob/main/src/index.html


Remove redundant definitions in cupy_cufft.h

Complex numbers are defined in cupy_cuComplex.h, which gets included in cupy_cuda.h. We should just take advantage of the existing ones.

LGTM. Jenkins, test this please.

Jenkins CI test (for commit a0d5b5dd3bedb4cd1374f78b61badf6059b1664e, target branch master) failed with status FAILURE.

The only error is cryptic to me...@asi1024 are you able to decipher it for me?

Jenkins failure seems unrelated to this PR.

Jenkins, test this please.

Jenkins CI test (for commit a0d5b5dd3bedb4cd1374f78b61badf6059b1664e, target branch master) succeeded!

LGTM. Thank you for the PR!

Thank you!


[staging-next] python311Packages.scikit-learn: 1.3.2 -> 1.4.0

Fix pytest failure: https://hydra.nixos.org/build/247211840/nixlog/1 since: https://github.com/NixOS/nixpkgs/pull/282506.
This may or may not fix many downstream packages in staging-next.
See upstream https://github.com/scikit-learn/scikit-learn/pull/27628 for details.
Changelog: https://scikit-learn.org/stable/whats_new/v1.4.html
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Sounds OK to me, though I don't know this package in particular.  The ChangeLog shows lots of API changes, but I think that's relatively common for python packages.

I also do not understand the full repercussions of this version bump... Maybe some python expert should take a look? :wink: I failed to nixpkgs-review it as the change seems to be too large for my laptop...

Let me merge this PR as is, so that the build is fixed at least.  Further improvements can be done later.


Game Engine Patch v1.2.1

Description
Bug fixes and integration with the achievement system.
Type of change

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Code quality improvements

Fixes

Fix >1 speaker box appearing simultaneously
Fix Awards Hall awards positioning

Changes

Award mapping is no longer mandatory to be present for an award

Previously, award without valid award mapping lead to game to crash. Now, we use a default award property

Added pop up for explanation of 'asset key' in Award Menu
TextHover now allows word wrap. Now it uses normal text instead of bitmap text
Constants cleanup [WIP]
UserStateManager to fetch actual data for achievements [WIP]
Make Save Managers more efficient by only storing fast-forward (aka state-change) actions.
Fix speaker box bug that does not disappear when speaker id is "you"/"narrator"
Instead of checking for "Test Student", use NODE_ENV to determine whether or not to show hidden game-dev buttons.
Fix chapter-completion undefineds

Checklist
Please delete options that are not relevant.

[ ] I have tested this code
[ ] I have updated the documentation

Pull Request Test Coverage Report for Build 6831

0 of 2 (0.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.007%) to 34.696%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/features/storySimulator/cursorMode/SSCursorMode.ts
0
1
0.0%

src/pages/academy/game/Game.tsx
0
1
0.0%

Totals

Change from base Build 6824:
-0.007%

Covered Lines:
2344

Relevant Lines:
6304

💛  - Coveralls


use the active locale for urls in the file viewer (bug 1168794)

Fixes bug 1168794

Interesting solution... I guess it works, but it feels slightly wrong. Anyway, r+


Paint textarea in red when error happens for SolutionForm

Description
Currently the textarea in SolutionForm is shown gray (the same) when an error happens, staying the same color as before, being inconsistent with current https://join.x-team.com/applicant/:token/submit solution.
How
Paint the textarea borders in red, and shadow the background in a lighter gray this way:

@falcoagustin This is all looks good and work to me. Just added small adjustments to make code more consistent 😄


feat(GDK-152): Apply @yannickoo changes plus mobile filter

@dnsos I merged master into it and tested it now on mobile. Everything works nicely. I'll merge the branch now.
@yannickoo Thanks again. Merging your branch now! ㊗  🙌


Revert "send current timestamp inside departure info request"

Reverts skodaconnect/myskoda#302
one of the tests is failing, already working on a fix

fixed by PR #306


Update toolpad in example to try out memory improvements

Seeing 50% improvement in memory in the runtime when running https://github.com/mui/mui-toolpad/pull/2354 on tools-public. Let's see if we see the same improvement with this example.
Reopened this PR from the original repo instead of a fork to kick off render.com

Increased the plan on this service to be able to inspect the memory. We're getting so close:


Convo.ask callback function is not being executed

I have 3 postbacks that should execute the same set of instruction with a slight difference which is the question to ask the user. So I created a function to respond to those postback, here is the function :
//Params : question to ask the user, bot, message from the postback event.
function respondMessage(question,bot,message) {
    bot.startConversation(message, function (error, convo) {
        convo.ask(question, function (response, convo) {
		//Checking if the user type something
            if (response.text == "") {
                console.log("its working");
                convo.repeat();
                convo.next();
            }
            else {
			//My function
                newsCreator("WHAT", response.user, response.text);

                convo.say(
                    {
                        "attachment":{
                            "type": "template",
                            "payload": {
                                "template_type": "button",
                                "text": "Should I send to you  :",
                                "buttons":
                                    [
                                    {
                                        "type": "postback",
                                        "title": "Football News",
                                        "payload": "FOOTBALL"
                                    },
                                    {
                                        "type": "postback",
                                        "title": "Basket Ball News",
                                        "payload": "BASKET"
                                    },
                                    {
                                        "type": "postback",
                                        "title": "Volley Ball News",
                                        "payload": "VOLLEY"
                                    }]
                            }

                          }
                    });
                convo.next();
				//End of the conversation
            }
        });
        convo.next();
    });
}

Here is the postback hanlder:
controller.on('facebook_postback', function (bot, message) {
    switch (message.payload) {
	case "COACH":
		respondMessage("Which Coach?",bot,message);
	case "TEAM":
		respondMessage("How many Team?",bot,message);
	case "PLAYER":
		respondMessage("Players of which country?",bot,message);
	default:
	}
	});

The question are being asked, but not even a message_received or postback event is being trigger in the bot when the user has typed and send his response to the question. The convo ask call back function is not being executed.

Hi,
I'm having a similar issue using patterns, and noticed that while the buttons are not firing the callback, manually typing in the payload works just fine.
Here is my code, I hope this helps to debug the issue :smile: .
    // Start Onboarding
    convo.addQuestion({
      attachment: {
        'type': 'template',
        'payload': {
          'template_type': 'button',
          'text': 'my question',
          'buttons': [
            {
              'type': 'postback',
              'title': '1',
              'payload': '1'
            },
            {
              'type': 'postback',
              'title': '2',
              'payload': '2'
            }
          ]
        }
      }
    }, [
      {
        pattern: 'onboard_user',
        callback: (res, convo) => {
          console.log(res)
          convo.next()
        }
      },
      {
        pattern: 'explain_features',
        callback: (res, convo) => {
          console.log(res)
          convo.next()
        }
      },
      {
        default: true,
        callback: (res, convo) => {
          convo.repeat()
          convo.next()
        }
      }
    ])

Maybe this could help you, are you enable messages_postback permissions on fb?
https://github.com/hyperoslo/facebook-messenger/issues/15#issuecomment-216933326

Hey @azanoni, thanks for the info. Yeah, the postback hook is enabled.

This is the response the webhook is getting back from those buttons.
{ object: 'page',
  entry:
   [ { id: '115975565622062',
       time:<PHONE_NUMBER>832,
       messaging:
        [ { recipient: { id: '115975565622062' },
            timestamp:<PHONE_NUMBER>832,
            sender: { id: '1310044285740325' },
            postback: { payload: 'test_payload' } } ] } ] }
<IP_ADDRESS> - - [04/May/2017:06:14:56 +0000] "POST /facebook/receive HTTP/1.1" 200 2 "-" "-"

while this is what happen if I send back the payload as a simple message
{ object: 'page',
  entry:
   [ { id: '115975565622062',
       time:<PHONE_NUMBER>552,
       messaging:
        [ { sender: { id: '1310044285740325' },
            recipient: { id: '115975565622062' },
            timestamp:<PHONE_NUMBER>181,
            message:
             { mid: 'mid.$cAABpeoGieZ5iA2CFFVb0hs8Zj1sG',
               seq: 33257,
               text: 'test_payload' } } ] } ] }
debug: RECEIVED MESSAGE
debug: CUSTOM FIND CONVO<PHONE_NUMBER>740325<PHONE_NUMBER>740325
debug: FOUND EXISTING CONVO!
debug: HANDLING MESSAGE IN CONVO { text: 'test_payload',
  user: '1310044285740325',
  channel: '1310044285740325',
  page: '115975565622062',
  timestamp:<PHONE_NUMBER>181,
  seq: 33257,
  is_echo: undefined,
  mid: 'mid.$cAABpeoGieZ5iA2CFFVb0hs8Zj1sG',
  sticker_id: undefined,
  attachments: undefined,
  quick_reply: undefined,
  type: 'user_message' }
<IP_ADDRESS> - - [04/May/2017:06:17:33 +0000] "POST /facebook/receive HTTP/1.1" 200 2 "-" "-"
debug: Conversation is over with status completed
info: >   [End]  0  Conversation with<PHONE_NUMBER>740325 in<PHONE_NUMBER>740325
info: [End]  0  Task for<PHONE_NUMBER>740325 in<PHONE_NUMBER>740325

I have an hunch that Botkit is not using the postback to continue the conversation.

Oh ok, I figured this out to enable postback in the convo all that is needed is to pass in {receive_via_postback: true} in the configurations.
Reading the documentation I thought that was recommended for custom matches, but it looks like it's leveraged to use postback in conversations as well :smile: .

Glad you found a resolution!
On Thu, May 4, 2017 at 2:40 AM federicoweber<EMAIL_ADDRESS>wrote:

Oh ok, I figured this out to enable postback in the convo all that is
needed is to pass in {receive_via_postback: true} in the configurations.
Reading the documentation
https://github.com/howdyai/botkit/blob/master/docs/readme-facebook.md#receive-postback-button-clicks-as-typed-messages
I thought that was recommended for custom matches, but it looks like it's
leveraged to use postback in conversations as well 😄 .
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/howdyai/botkit/issues/815#issuecomment-299107901, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AMUR29D1hmp22BsIfLVhKqnT86yOoErHks5r2XLAgaJpZM4NMNo4
.

@federicoweber Thanks, it has helped me too.


Old and out of date

These steps do not work and reference runtimes that are over 2 years old.  Additionally the notebooks and references are hard coded in the build pipeline which is less than ideal.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 56b86f59-7a22-90c6-9aa6-652b85975612
Version Independent ID: b333ab7b-847b-7129-9b62-4b9b934747d7
Content: Continuous integration and delivery on Azure Databricks using Azure DevOps - Azure Databricks
Content Source: databricks/dev-tools/ci-cd/ci-cd-azure-devops.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

@PorterJosh
Thanks for your feedback! We will investigate and update as appropriate.

@leifbro
could you please review this and update as appropriate.

@PorterJosh
I've delegated this to @leifbro, a content author, to review and share their valuable insights.

Thanks for providing feedback that helps improve our documentation. We've created an internal work item (DOC-11112) to address your feedback. The timeline for resolution varies based on resourcing.
#please-close