Alt+Tab switches tabs

Describe the bug
Alt+Tab is used to switch between windows. It should not switch tabs within an application.
To Reproduce

Open sniffnet
Press Alt+Tab to switch to a different window
Switch back to sniffnet
Notice that a different tab is focused

Expected behavior
Alt+Tab should not switch tabs.
Desktop (please complete the following information):

OS: Linux
Version 1.2.1

Additional context
Installed with cargo install sniffnet

This little bug was introduced just a few days ago in #248.
I will personally fix it before the next release 👍

Oh, I think the bug is two-fold:

When sniffnet is focused, pressing Alt+Tab immediately switches to the next tab (introduced in v1.2.1)
When another program is focused, pressing Alt+Tab to switch to sniffnet may also switch to the next tab (existed before)

The 2nd bug seems to only occur when the Tab key is released after the Alt key.

Thanks for the detailed report.
I'll better investigate.

I've restored the original situation (that of v1.2.0, with the difference that now also esc and enter only apply the shortcut when no modifier at all is pressed).

When another program is focused, pressing Alt+Tab to switch to sniffnet may also switch to the next tab (existed before)

The 2nd bug seems to only occur when the Tab key is released after the Alt key.

I was not able to reproduce this behaviour though.
If Sniffnet is not focused, shouldn't receive commands at all.
The fact that it happens when you release the tab key later suggests that it triggers when no modifiers are pressed, which is what we want (if the app is focused ofc).

alt+tab should not have an effect now on the app.
Could you try releasing the tab slightly before the alt?
I guess that the problem is that if you have tab pressed (without modifiers) even for a short instant, the app immediately captures it.
Really weird that's happening with the app unfocused though.
On which OS are you running @starccy?
Feel free to provide a short video if you want, so that I can better understand your specific situation.

@GyulyVGC
I am using Kali Linux with Gnome 44 + X11.

alt+tab should not have an effect now on the app.

Even if you released tab after alt?
I try to slow down my actions to make sure every Tab be released before Alt be released, the tabs within the app won't switch. :heavy_check_mark:

I guess that the problem is that if you have tab pressed (without modifiers) even for a short instant, the app immediately captures it.

Yes you are right. I have done a small test to compare keyboard events between the iced-based app and the gtk-based app to find the difference.
For the iced app (this project), I simply insert a print statement here to log keyboard events:
https://github.com/GyulyVGC/sniffnet/blob/3268b0e0b126cc4cecb8e7e7005d40445cefd878/src/gui/app.rs#L110-L114

For the gtk app, I write a small app to print key events:
use gtk::{Application, ApplicationWindow, EventControllerKey, glib};
use gtk::prelude::*;

const APP_ID: &str = "just.for.test";

fn main() -> glib::ExitCode {
    let app = Application::builder()
        .application_id(APP_ID)
        .build();

    app.connect_activate(build_ui);

    app.run()
}

fn build_ui(app: &Application) {
    let window = ApplicationWindow::builder()
        .application(app)
        .title("test")
        .build();

    let event_ctrl = EventControllerKey::new();
    event_ctrl.connect_key_pressed(|_, key, _, modifier| {
        println!("Pressed | Key: {}, Modifier: {:?}", key.name().unwrap_or(key.to_string().into()), modifier);
        gtk::Inhibit(true)
    });
    event_ctrl.connect_key_released(|_, key, _, modifier| {
        println!("Released | Key: {}, Modifier: {:?}", key.name().unwrap_or(key.to_string().into()), modifier);
    });

    window.add_controller(event_ctrl);

    window.present();
}

For the both apps, I do the following procedures:

Using Alt + Tab to switch back to the app, and make sure the Tab key is released before Alt. I got no output from both apps, which is as expected. :heavy_check_mark:
Using Alt + Tab to switch back to the app, but let Tab be released after Alt. Here are the outputs:

The iced app output:
KeyPressed { key_code: Tab, modifiers: (empty) }
KeyReleased { key_code: Tab, modifiers: (empty) }

The gtk4 app output:
Release | Key: Tab, Modifier: (empty)

The result is obvious, the gtk4 program does not emit the pressed event immediately, which is the culprit causing this problem.
In fact, If I keep pressing the Tab key for enough long time, the gtk app will also start to emit the pressed event. But in contrast to iced, it has a slight delay to trigger.
I haven't dug too deep into iced or gtk, so I don't know if they serve different purposes and make different logic. But in my opinion, the gtk one is more intuitive and can avoid this issue.
In conclusion, the key point is how to avoid emit key event immediately, or should we open an issue in iced repo?

Wow, thanks for the very detailed report.
So, if I get it correctly the problem is that the tab key immediately results as 'pressed' even if the alt key was 'released' just an instance before.
I think that from a logic point of view it's hard to define which alternative is better, to me it's not even so meaningful to have a state 'released tab' if the reality is that it was the alt to be released.
Of course iced logic could lead to some usability problems, which should be the following two in our case (correct me if I'm wrong):

a user wants to switch app while using Sniffnet. He presses tab slightly before alt, causing also Sniffnet to switch
a user wants to switch app coming back to Sniffnet. He releases alt slightly before tab, causing also Sniffnet to switch

I'll try to see if I can do something using some timer and the KeyReleased event: https://docs.iced.rs/iced/keyboard/enum.Event.html

I second that.
But for the first case, I am unable to do further verification. I don't think it's a problem because pressing tab before alt is not a valid combination, at least for my OS, the Task Switcher won't pop up. So in this situation, they should be treated as two individual events as normal.
I found a similar issue from iced: https://github.com/iced-rs/iced/issues/612. Unfortunately, it seems to be closed by misunderstanding.

'll try to see if I can do something using some timer and the KeyReleased event

If along this line of thought, I think we can record the last focus time for the window. Every time when Tab be pressed, we can check the diff time.
Here is an available code:
diff --git a/src/gui/app.rs b/src/gui/app.rs
index ff99bae..a58b5c6 100644
--- a/src/gui/app.rs
+++ b/src/gui/app.rs
@@ -104,10 +104,14 @@ fn view(&self) -> Element<Message> {

     fn subscription(&self) -> Subscription<Message> {
         use iced_native::keyboard::{Event, KeyCode, Modifiers};
+        use iced_native::window;
         const NO_MODIFIER: iced_native::keyboard::Modifiers =
             iced_native::keyboard::Modifiers::empty();
         let hot_keys_subscription =
             iced_native::subscription::events_with(|event, _| match event {
+                iced_native::Event::Window(window::Event::Focused) => {
+                    Some(Message::WindowFocused)
+                }
                 iced_native::Event::Keyboard(Event::KeyPressed {
                     key_code,
                     modifiers,
diff --git a/src/gui/types/message.rs b/src/gui/types/message.rs
index 229fed3..d2179cb 100644
--- a/src/gui/types/message.rs
+++ b/src/gui/types/message.rs
@@ -80,4 +80,5 @@ pub enum Message {
     UpdatePageNumber(bool),
     /// Left (false) or Right (true) arrow key has been pressed
     ArrowPressed(bool),
+    WindowFocused,
 }
diff --git a/src/gui/types/sniffer.rs b/src/gui/types/sniffer.rs
index 374150b..a6151da 100644
--- a/src/gui/types/sniffer.rs
+++ b/src/gui/types/sniffer.rs
@@ -81,6 +81,31 @@ pub struct Sniffer {
     pub page_number: usize,
     /// Currently selected connection for inspection of its details
     pub selected_connection: usize,
+    pub focus_state: FocusState,
+}
+
+const FOCUS_TIMEOUT: u64 = 200;
+
+pub struct FocusState {
+    last_focus_time: std::time::Instant,
+    focus_timeout: std::time::Duration,
+}
+
+impl FocusState {
+    fn new(focus_timeout: u64) -> Self {
+        Self {
+            last_focus_time: std::time::Instant::now(),
+            focus_timeout: std::time::Duration::from_millis(focus_timeout),
+        }
+    }
+
+    fn update(&mut self) {
+        self.last_focus_time = std::time::Instant::now();
+    }
+
+    pub fn is_just_focus(&self) -> bool {
+        self.last_focus_time.elapsed() < self.focus_timeout
+    }
 }

 impl Sniffer {
@@ -116,6 +141,7 @@ pub fn new(
             search: SearchParameters::default(),
             page_number: 1,
             selected_connection: 0,
+            focus_state: FocusState::new(FOCUS_TIMEOUT),
         }
     }

@@ -182,7 +208,11 @@ pub fn update(&mut self, message: Message) -> Command<Message> {
                 return self.update(Message::HideModal);
             }
             Message::Quit => return window::close(),
-            Message::SwitchPage(next) => self.switch_page(next),
+            Message::SwitchPage(next) => {
+                if !self.focus_state.is_just_focus() {
+                    self.switch_page(next)
+                }
+            },
             Message::ReturnKeyPressed => return self.shortcut_return(),
             Message::EscKeyPressed => return self.shortcut_esc(),
             Message::ResetButtonPressed => return self.reset_button_pressed(),
@@ -215,6 +245,9 @@ pub fn update(&mut self, message: Message) -> Command<Message> {
                     }
                 }
             }
+            Message::WindowFocused => {
+                self.focus_state.update();
+            }
         }
         Command::none()
     }

The idea seems good to me.
If it already works, feel free to open a PR so that we can better discuss it.
Thank you very much!

Yes, I've tested the code on my computer and it works as expected. I will submit a pull request later.


Feature/asb 1964 move homepage behind feature flag

Describe your changes

Ticket: https://pins-ds.atlassian.net/browse/ASB-1964

Useful information to review or test

Type of change 🧩

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update
[ ] Other (please explain in the description section above)

Checklist before requesting a review

[x] I have performed a self-review of my own code
[x] I have double checked this work does not include any hardcoded secrets or passwords
[x] I have made corresponding changes to the documentation
[x] I have provided details on how I have tested my code
[x] I have referenced the ticket number above
[x] I have provided a description of the ticket
[x] I have included unit tests to cover any testable code changes

:tada: This PR is included in version 2.19.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.5.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.15.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Testing: selection filtering

As per title

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 61.08%. Comparing base (0c58b24) to head (80114ac).

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #69      +/-   ##
==========================================
+ Coverage   59.10%   61.08%   +1.98%
==========================================
  Files          11       11
  Lines         956      956
  Branches      244      244
==========================================
+ Hits          565      584      +19
+ Misses        312      289      -23
- Partials       79       83       +4

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests
JS Bundle Analysis - Avoid shipping oversized bundles


Uncaught exception 'BadMethodCallException' with message 'Method setDebug not defined for Analytics class'

It looks like there is no method setDebug as explained in the docs.
I copy pasted the code and the error was thrown.

You are either:

Using v1, which lacks newer features such as Debug and Hit validation (this is in the README)
or
Using a very old version of v2

To fix this, you can update to the latest version:
composer require theiconic/php-ga-measurement-protocol ^2.0

This should upgrade you to v2.7.1  which is the latest.


Create About us Section

Deliverables

Make Generalized components.
Also Generalized color as well. (I mean we can pass using props).

Sample

Additional context

Tech/Framework:- React Js

I would like to work on this issue. Please assign me.

I would like to work on this issue.Can I Work on it.

@shreyanshi16 go ahed !

@codewithvk when this issue will be passed on to other participant? After how many days?

Hi @codewithvk does this look good to you? Or is there any changes that I need to do?

@shreyanshi16 Ya looks good for me :)
Go ahead and make PR.


Bug: Investigate issue in TUF root upgrade with consistent snapshots

Description
Investigate buggy behavior with consistent snapshots in the sigstore TUF root upgrade path:
Verifying with an upgraded TUF root that enables consistent snapshots causes a bug in a fresh environment. Explicitly calling cosign initialize and then verifying avoids the bug.
Reproduced by replacing the default remote store to the brokenv3 (consistent snapshot) branch of root-signing:
asraa@asraa1:~/git/cosign$ go build -o cosign ./cmd/cosign
asraa@asraa1:~/git/cosign$ COSIGN_EXPERIMENTAL=1 ./cosign verify gcr.io/distroless/base:debug
panic: error getting targets

goroutine 1 [running]:
github.com/sigstore/cosign/cmd/cosign/cli/fulcio/fulcioroots.Get.func1()
	/home/asraa/git/cosign/cmd/cosign/cli/fulcio/fulcioroots/fulcioroots.go:69 +0x74
sync.(*Once).doSlow(0xc00084ade0?, 0x1d?)
	/usr/local/go/src/sync/once.go:68 +0xc2
sync.(*Once).Do(...)
	/usr/local/go/src/sync/once.go:59
github.com/sigstore/cosign/cmd/cosign/cli/fulcio/fulcioroots.Get()
	/home/asraa/git/cosign/cmd/cosign/cli/fulcio/fulcioroots/fulcioroots.go:65 +0x31
github.com/sigstore/cosign/cmd/cosign/cli/fulcio.GetRoots(...)
	/home/asraa/git/cosign/cmd/cosign/cli/fulcio/fulcio.go:174
github.com/sigstore/cosign/cmd/cosign/cli/verify.(*VerifyCommand).Exec(0xc0005b9c30, {0x2e23cd8, 0xc000054108}, {0xc000876a90, 0x1, 0x6bc9a5?})
	/home/asraa/git/cosign/cmd/cosign/cli/verify/verify.go:113 +0x3f5
github.com/sigstore/cosign/cmd/cosign/cli.Verify.func1(0xc0007d5b80, {0xc000876a90, 0x1, 0x1})
	/home/asraa/git/cosign/cmd/cosign/cli/verify.go:115 +0x265
github.com/spf13/cobra.(*Command).execute(0xc0007d5b80, {0xc000876a70, 0x1, 0x1})
	/home/asraa/go/pkg/mod/github.com/spf13/cobra@v1.4.0/command.go:856 +0x67c
github.com/spf13/cobra.(*Command).ExecuteC(0xc000908500)
	/home/asraa/go/pkg/mod/github.com/spf13/cobra@v1.4.0/command.go:974 +0x3b4
github.com/spf13/cobra.(*Command).Execute(...)
	/home/asraa/go/pkg/mod/github.com/spf13/cobra@v1.4.0/command.go:902
main.main()
	/home/asraa/git/cosign/cmd/cosign/main.go:51 +0x4c
asraa@asraa1:~/git/cosign$ ls $HOME/.sigstore
root
asraa@asraa1:~/git/cosign$ rm -r $HOME/.sigstore
asraa@asraa1:~/git/cosign$ ./cosign initialize
Root status:
 {
	"local": "/home/asraa/.sigstore/root",
	"remote": "test-sigstore-root",
	"metadata": {
		"root.json": {
			"version": 3,
			"len": 5285,
			"expiration": "10 Nov 22 02:19 UTC",
			"error": ""
		},
		"snapshot.json": {
			"version": 29,
			"len": 1975,
			"expiration": "31 May 22 17:41 UTC",
			"error": ""
		},
		"targets.json": {
			"version": 3,
			"len": 6088,
			"expiration": "10 Nov 22 02:19 UTC",
			"error": ""
		},
		"timestamp.json": {
			"version": 29,
			"len": 717,
			"expiration": "24 May 22 17:41 UTC",
			"error": ""
		}
	},
	"targets": [
		"fulcio_v1.crt.pem",
		"rekor.0.pub",
		"rekor.pub",
		"artifact.pub",
		"ctfe.pub",
		"fulcio.crt.pem",
		"fulcio_intermediate_v1.crt.pem"
	]
}
asraa@asraa1:~/git/cosign$ COSIGN_EXPERIMENTAL=1 ./cosign verify gcr.io/distroless/base:debug

Verification for gcr.io/distroless/base:debug --
[success]

cc @haydentherapper
Questions:

Where is GetTargets pulling targets from in each case?
What target names are being pulled in each case?

When I did a cursory investigation, I added a lot more logging to print out the target names - Probably worth adding that in to Cosign.

Notes:
It's not a consistent snapshot problem. It's a problem that we introduced a new target fulcio_intermediate_v1.crt.pem. In the embedded workflow, we are still trying to retrieve a target from the embedded file system, and it doesn't exist! It doesn't pick up from the disk cache, even though it writes the cached targets
https://github.com/sigstore/cosign/blob/03e66aad02cf7c987ea489cdeda1fd580b6b1fc6/pkg/cosign/tuf/client.go#L596
I think I need to clean up the targetImpl/setImpl, not sure I understand how the functionality is being separated
https://github.com/sigstore/cosign/blob/03e66aad02cf7c987ea489cdeda1fd580b6b1fc6/pkg/cosign/tuf/client.go#L592-L597
The embedded impl has a disk cache for the setter, but gets targets from the embedded repository, not the disk cache. cc @dlorenc

One line fix is to switch to a diskCache if there's a need for an update in the embedded start workflow

In-memory initialize is kinda a no-op -- in-memory only makes sense during a verification.
But yes, embedded is only for the start root -- if there's any updates it's a newFileImpl(), which is either a disk cache, or in-memory impl if you don't have caching enabled.
So my fix I think is to make it clear that embedded is a "starting state", and it eventually moves to a file impl on an update.

On top of this memoryCache doesn't have a Getter. So I'm just going to clean up the targetImpl and setImpls


[SPARK-39160][SQL] Remove workaround for ARROW-1948

What changes were proposed in this pull request?

Remove workaround for ARROW-1948(got fixed in arrow 0.9) which originally comes from SPARK-22530
Why are the changes needed?

Remove unnecessary code.
Does this PR introduce any user-facing change?

No
How was this patch tested?

The exsiting UT ArrowColumnVectorSuite

cc @BryanCutler

Can one of the admins verify this patch?

merged to master, thanks @pan3793


Uncaught TypeError: date1.format is not a function

Describe the bug
https://jsfiddle.net/8hrbyw9u/
I found this demo, that showing 'onSelect' in action and using<EMAIL_ADDRESS>All works great.
But with last version of litepicker (1.5.7) I become error:
Uncaught TypeError: date1.format is not a function
To Reproduce
https://jsfiddle.net/4n60cktm/

It seemed to work with<EMAIL_ADDRESS>but not with<EMAIL_ADDRESS>I think it might have stopped working with this commit (I haven't thoroughly tested different versions).
Possible workaround: date1.toDateString() helped me get the format I needed.

In v2 starts DateTime object again.
https://wakirin.github.io/Litepicker/docs/events#selected

In v2 starts DateTime object again.
https://wakirin.github.io/Litepicker/docs/events#selected


Image stitching

I would like to add a new feature, for image stitching.
Here, I would take 2/3 images and join them in a single frame, which will appear like a single image.

Add your implementation in awesome face operations


gh-154 Standartize Button Types

Add default and primary classes for Button as prop type
Replace all buttons with this classes

close #154

close #154


refactor send

The code refactored
add stop channel to handle graceful close

changes cleaned up and merged in #25 thanks :heart:
please test current master


albert: 0.14.15 -> 0.14.21

Motivation for this change
Albert has a new release including several extensions and bug fixes.
Additionally, this upgrade solves current QT build issues. See
https://albertlauncher.github.io/news/ for the full changelog.
Things done

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

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

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

@GrahamcOfBorg  build albert

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: albert
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: albert
Partial log (click to expand)
shrinking /nix/store/vnlvhppbqdsapz83jzvkl78pxvh57ciy-albert-0.14.21/libs/albert/libalbertcore.so
shrinking /nix/store/vnlvhppbqdsapz83jzvkl78pxvh57ciy-albert-0.14.21/libs/albert/libglobalshortcut.so
shrinking /nix/store/vnlvhppbqdsapz83jzvkl78pxvh57ciy-albert-0.14.21/libs/albert/libxdg.so
shrinking /nix/store/vnlvhppbqdsapz83jzvkl78pxvh57ciy-albert-0.14.21/bin/.albert-wrapped
strip is /nix/store/4qvrxzxa535y8304mk195x50b6p9607d-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/vnlvhppbqdsapz83jzvkl78pxvh57ciy-albert-0.14.21/bin
patching script interpreter paths in /nix/store/vnlvhppbqdsapz83jzvkl78pxvh57ciy-albert-0.14.21
checking for references to /build in /nix/store/vnlvhppbqdsapz83jzvkl78pxvh57ciy-albert-0.14.21...
postPatchMkspecs
postPatchMkspecs

Success on aarch64-linux (full log)
Attempted: albert
Partial log (click to expand)
shrinking /nix/store/kqqk7xf9qfks2867i7khgk15mbgcnzag-albert-0.14.21/libs/albert/libxdg.so
shrinking /nix/store/kqqk7xf9qfks2867i7khgk15mbgcnzag-albert-0.14.21/libs/albert/libalbertcore.so
shrinking /nix/store/kqqk7xf9qfks2867i7khgk15mbgcnzag-albert-0.14.21/bin/.albert-wrapped
strip is /nix/store/0pjsgkxz0rp5baycq5sp2s72lrr5q9sg-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/kqqk7xf9qfks2867i7khgk15mbgcnzag-albert-0.14.21/bin
patching script interpreter paths in /nix/store/kqqk7xf9qfks2867i7khgk15mbgcnzag-albert-0.14.21
checking for references to /build in /nix/store/kqqk7xf9qfks2867i7khgk15mbgcnzag-albert-0.14.21...
postPatchMkspecs
postPatchMkspecs
/nix/store/kqqk7xf9qfks2867i7khgk15mbgcnzag-albert-0.14.21


Fix MacOS builds code signing

Mac OS builds linked with zig are improperly output, making them impossible to sign & notarize, thus making it difficult to use in professional electron apps/games.
This goes back to building MacOS builds on MacOS with XCode's linker to produce correct build outputs.
Fixes #103

Note: This is intended to fix #103.

This PR seems important. Can we merge it?

@ceifa Just checking in on this to see if there's any concerns or issues preventing it from being merged?

sorry guys, I'm very busy these days, merging it now


v1.3.0

hasRepresentation (#318)
SHACL-based Brick Implementation (#341)
adding documentation on Brick releases (#264)
Class-based shapes (#240)
Fix Nightly Builds (#241)
Amending QUDT Definitions (#239)
Update Ontology Metadata (#245)
amend definition for isPointOf (#251)
Adding quantities, sensor classes for air quality (#247)
use brick value, not brick area inside the entity property (#254)
Regenerate air quality sensor example (#255)
generalizing solar panel and adding its subclasses (#248)
add building electrical meter example (#265)
Fixing Meter relationship in example (#266)
add types to external properties and classes (#267)
Fixing ASHRAE reference (#268)
Fix the rest of the rdfs:seeAlso URI encoding (#275)
Added Water Level Alarms (#282)
Added Lockout and Availability Status Points (#280)
added flow sensors points (#279)
Added New Boiler Types (#283)
Additional air handling unit types (#274)
Update pre-commit configuration (#286)
added air system classes (#278)
fix bad merge: remove exhaust air system (#288)
Radiant system terminal unit classes (#270)
Add Shapes to Brick distribution (#285)
PV Systems and Entity Properties (#273)
Updating Nightly Builds (#289)
use "/" suffix for sosa namespace (#295)
add imbalance sensors (#293)
add stage riser; update riser defn (#296)
value of path should be sh:class, not rdfs:range (#300)
Add testing for examples (#299)
Add UFAD and diffuser equipment and points (#297)
Fixing validation of entity properties (#301)
remove reference to defunct tags.py file (#303)
Add collection types (#269)
Adding Differential Quantities to Brick (#294)
V1.2.1 release (#309)
added diff temp points and water temp setpoints (#277)
Added Differential Pressure Points (#276)
make sure we do not add duplicate RDFS labels (#307)
remove controls (#310)
Allow Entity Properties to have generic numeric values (#311)
Expand ApplicableUnits annotations (#306)

Add Chilled Beam and subclasses (#302)

Fix RDFS Labels (#313)
Added brick:Relief_Damper, brick:Relief_Fan and tag:Relief (#312)
Adding optimized SHACL shapes to reduce inference time (#316)
Reduce automated test time (#320)
Add Sensors from NREL Example Models (#317)
Labels on properties and entity properties (#322)
Fix spelling (#323)
Ignore generated files (#327)
fix Dew_Point to Dewpoint (#338)
add misc concepts (#335)
restructure valve hierarchy and add TMV (#333)
remote incorrect tags (#340)
add miscellaneous alarms (#331)
add missing points (#329)
add CRAH (#342)
Update files generated from source (#326)
Added heating, cooling enable commands (#339)
Remove second skos:definition for Brick#Building (#343)

Co-authored-by: Jason B. Koh<EMAIL_ADDRESS>Co-authored-by: Carlos Duarte<EMAIL_ADDRESS>Co-authored-by: Gabe Fierro<EMAIL_ADDRESS>Co-authored-by: wcrd<EMAIL_ADDRESS>Co-authored-by: David Waterworth<EMAIL_ADDRESS>Co-authored-by: David Waterworth<EMAIL_ADDRESS>Co-authored-by: Jonas Bülow<EMAIL_ADDRESS>Co-authored-by: Jonas Bülow<EMAIL_ADDRESS>

How is bacnet.ttl created? Is it an import from bacpypes or somewhere else? Or did Gabe manually create it? We should note the source inside the file for future references (e.g., for the purpose of updating and fixing the file later.)

Why do we limit the types of BACnet properties used for BACnetReferences into the few? BACnetReference can be a placeholder for any standard properties in BACnet.
(Sorry that I raise those questions now. I should've done this in #318 )

BAcnet.ttl is a draft form of the BACnet standard translated into RDF/SHACL created by @JoelBender . Once the draft form is accepted as a standard distribution of BACnet in some way, we can refer to that official source. Until then, while it has already been fairly stable, I can take care of updating it in the same way that I take care of updating QUDT.
The types of BACnet properties are not limited in the definition; the BACnetReference shape merely requires that a certain number of properties be included in order to facilitate interaction with that object over the BACnet network.

Cool. Thanks for the info! I will report bugs and questions to Joel then.
Could you explain why we introduce BACnetReference instead of directly using bacnet:StandardObject? Given bacnet.ttl is (semi-)stable, we can just use the shapes and the classes in the file.

@epaulson @jbkoh here's some draft release language:

Brick v1.3.0 is the result of more than a year of work by the Brick development team and a growing community of international contributors. This release of Brick contains several major
improvements and changes since Brick v1.2.1 as well as a number of bug fixes and smaller additions.
The big features in Brick v1.3.0 are:

moving from an OWL-based ontology to a SHACL-based ontology. This allows Brick and Brick tooling to make use of the validation features of SHACL, which will
help to ensure that Brick models are consistent and valid. We recommend using the pySHACL project to conduct validation of
Brick models. The brickschema package also provides support for validation
ref:hasExternalReference is a new relationship that relates Brick entities to their representations in other digital forms, for example IFC models, BACnet networks
and timeseries databases. This builds on work on the ref-schema, a new RDF schema for standardizing these external references
ability to model meter/submeter hierarchies, their relationships to devices and rooms, and the data they produce
dramatically expanded sets of entity properties, capturing "nameplate" and other static characteristics of Brick entities
adding useful semantic annotations to all Brick Point classes with the brick:hasSubstance and brick:hasQuantity properties
unit tests added to all Brick examples to ensure they are up-to-date with correct Brick usage
additional classes covering, among other thigns, different kinds of fans, sensors, PV systems

Many of these major features are documented at https://docs.brickschema.org/ .

I believe we intended to have https://github.com/BrickSchema/Brick/pull/246 in 1.3.0, didn't we?

@gtfierro  Yes, I think we agreed on all the items as in the last note, as far as I recall.

We should be sure to add lastKnownValue to the release notes!


Text change.

All your Friends & Family will see this wallet name going forward

Verified this issue on dev app v1.9.5(334)


Issues with mobile mints

Some users have told us that they were not able to mine via mobile.
Either this page came up (see attachment), or the users were redirected to metamask, but then only a white blank page opened on metamask, without any request to mine.
I would appreciate any response.

#28 might be connected, this one lacks details, so closing for now


Parsing a stringified Python date doesn't work anymore

Hey folks!
This used to work, right?
$ python
Python 2.7.6 (default, Mar 22 2014, 22:59:56)
[GCC 4.8.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import datetime
>>> import dateparser
>>> dateparser.__version__
'0.4.0'
>>> datetime.datetime.now()
datetime.datetime(2016, 6, 21, 10, 10, 2, 214991)
>>> str(datetime.datetime.now())
'2016-06-21 10:10:05.626942'
>>> dateparser.parse(str(datetime.datetime.now()))
>>>  # expected a datetime object, but it returned None

I tried to use an old script (I can't remember which version I was using at the time) that relied on this, but this doesn't working with the newest version.

This works on 0.3.5:
Python 3.5.1 (default, Dec 18 2015, 00:00:00)
[GCC 4.8.4] on linux
Type "help", "copyright", "credits" or "license" for more information.
(InteractiveConsole)
>>> import datetime
>>> import dateparser
>>> dateparser.__version__
'0.3.5'
>>> str(datetime.datetime.now())
'2016-06-22 15:47:06.267928'
>>> dateparser.parse(str(datetime.datetime.now()))
datetime.datetime(2016, 6, 22, 15, 47, 14, 964083)
>>>

Is this related to "Replaced dateutil.parser.parse with dateparser's own parser." introduced in 0.4.0?  #187 seems like a huge change ... that really should have been done upstream as suggested in the ticket.

@adamn yes it was related to the changes in PR #187. The reason why I didn't choose to do the upstream was new parser is designed around use cases handled by dateparser with little consideration for extensibility and is tightly coupled with customizable configurations (i.e. dateparser.conf.settings). It would have taken more work to make it suitable for dateutil given it has a slightly different approach planned for future to overhaul its parser.


Quick assist: allow inverting terms in conditional (c?x:y) expressions

If I use the following if/else construct quick assist offers me the option "Invert 'if' statement":
if (c!=1){
  return x;
}else{
  return y;
}

That option converts it into:
if (c==1){
  return y;
}else{
  return x;
}

It would be valuable to have the same quick assist for constructs like:
return c!=1?x:y;

Which would convert it into:
return c==1?y:x;

Duplicate of #45669, although this is clearer.

I commented there, but I can try that after I'm done with some other quick-fix improvements. No promises though.


[Issue_#246/GNMT] Add support to drop duplicates

In accuracy mode, we want to have the option to skip duplicate queries.
Note that the corresponding change in process_accuracy.py could potentially
allow for some sort of cheating, by not processing hard-to-predict
sentences. process_accuracy skips records with empty data in the
accuracy log.
On another note @briandersn : I noticed that the Offline scenario is no longer generating all sentence IDs.

Hi @briandersn, that is actually a very good idea. I agree that we don't want the SUT to know which mode we're running in :). I reverted the old solution and added a new one.

Looks good. Thanks Max!

On another note @briandersn : I noticed that the Offline scenario is no longer generating all sentence IDs.

I haven't forgotten about this, btw. I'm going to write some unit tests for this next week to make sure this doesn't keep regressing.


Wrong mask for 64 bits IO access in NaxRiscvProbe

Hi Charles,
The current mask value is zero for 64-bit access.
https://github.com/SpinalHDL/NaxRiscv/blob/8f0bd88d2bad93d4c6e5fcabae83391453888c13/src/main/scala/naxriscv/platform/NaxriscvProbe.scala#L266
When booting Linux "rv64imafdcsu" with SocSim & RVLS, I got the following error:
[info] *** INTEGER WRITE MISSMATCH DUT=216309d REF=0 ***
[info] commit error
[info] - std::exception

For debugging, I saw the spike.log ,  tracer.log and the output waves :
**SPIKE.LOG**
core   0: 0x0000000080008f22 (0x00006108) c.ld    a0, 0(a0)
core   0: 3 0x0000000080008f22 (0x6108) x10 0x0000000000000000 mem 0x000000001001bff8

**TRACER.LOG**
rv io 0 0<PHONE_NUMBER>01bff8<PHONE_NUMBER>000000 ff 8 0
rv rf w 0 0 32<PHONE_NUMBER>16309d
rv commit 0<PHONE_NUMBER>008f22

In the output waves, we can see that the data at the address 0x1001bff8 is equal to 0x216309d, as shown in the following line from the tracer.log file
rv rf w 0 0 32<PHONE_NUMBER>16309d

In the spike.log instead of having this value 216309d. I have a data value which is equal to zero, this value  is sent to RVLS via IOAccess as shown in the following line from the Tracer.log (because the value of the mask is zero)
rv io 0 0<PHONE_NUMBER>01bff8<PHONE_NUMBER>000000 ff 8 0

Here is the modification that I made to the mask to have a mask that is equal to 0xFFFFFFFF for 64-bit access
     val mask = (BigInt(1) << ioAccess.size*8)-1
     ioAccess.data = (ioBus.rsp.data.toLong >> offset*8) & mask.toLong

Thank you !

Hi,
Ahhh io access on 64 bits is something untested XD
Can you open a PR ?
Thanks :D


Define duration of contribution for Institutional Contributor

The topic of Institutional Partners and Contributors came up in our recent Steering Council meeting. In particular, we noticed that our current governance documents do not specify what duration of time an individual would need to contribute to the Project to qualify as an Institutional Contributor (and thereby qualifying the host institution to be an Institutional Partner). This edit propose a six month duration of sustained contribution and leaves in place the one-year grace period should an Institutional Partner have a window without an active contributor.
cc @pangeo-data/steering-council, @pangeo-data/pangeo-members

Cross posted here: https://discourse.pangeo.io/t/proposing-edits-to-pangeos-governance-documents-contribution-duration-for-institutional-partners/154

@guillaumeeb - as I read it, the definition of an Institutional Partner is provided in lines 147-152 (particularly the last two sentences). The goal of these three paragraphs is to provide definition around the role and qualification of  Institutional Partners and it seems somewhat necessary to have some circular references. Happy to make edits though if need be.

Yes, I guess I'm over thinking this, it's quite clear as it is.

Thanks for this Joe! Since there appear to be no objections, I will merge.


CI/CD: fix error in prepare work

Runner 16 is broken, reinstall and reconfigure runner 16 can solve this problem now.
However, it takes time to observe further.

After a week of observation, it was preliminarily determined to be the cause of runner 16, so this issue was closed first


Message payload should return object on simple messages

Change message payload to retrieve the sole object if only one of one kind is found:

If a DataSet is present and it is only one, return the Dataset object
If any ItemScheme or Definition is present, return the sole object
If more than one is present, but of the same kind, return a list
If more than one is present from different kinds, return same type as content

Instead of modifying the read_sdmx function, I have added the methods get_organisationschemes, get_codlists, get_concepts, get_dataflows and get_datastructures to the class message. I have modified the payload to return the sole object if it is only one Dataset too , I have modified a bit the returns in read_sdmx and added the read_xml to return the type of data. It is already committed all of it.

Add function get with an specific key for DataStructures, Dataflows, OrganisationSchemes, Codelists and Concepts.

Add function with get_dataset with key, if there is only one, check dataset.unique_id = key, if it is not equal raise ValueError exception.


slide change transition events are not emitted properly when using slider with effect property

Vue: 2.5.13
vue-awesome-swiper: 3.1.2
Steps to reproduce
Create a component that uses vue-awesome-swiper. Add an effect property. Listen for slideNextTransitionStart & slidePrevTransitionStart events.
What is Expected?
Events are emitted when swiping left/right
What is actually happening?
Events are not always emitted. Seems that the event is occasionaly emitted but not on every left/right swipe
When slider is initialized without effect property the events are fired correctly.
Seems that all of the following events are not properly emitted:
slideChangeTransitionStart
slideChangeTransitionEnd
slideNextTransitionStart
slideNextTransitionEnd
slidePrevTransitionStart
slidePrevTransitionEnd

Even the demos of official site(zh version) have the same issue.Check out here:
http://www.swiper.com.cn/api/event/slideNextTransitionEnd.html
http://www.swiper.com.cn/api/event/slidePrevTransitionEnd.html
They both are either emitting incorrectly or  not emitting at all.
Please check it out ASAP.I think it maybe caused by swiper.js version.
Because the demos of this site(none-official) just work properly.Here:
http://caibaojian.com/swiper-api/event/slideNextTransitionEnd.html

i'm using the 8.3.1 version and i have the same problem
onSlideNextTransitionEnd fires only once at swiper mount
any way to solve it? do i have to downgrade it?


Error in Log while refreshing - (31135) Send this info to developer !!! { Unhandable information found in DoHome : "legacyHeatingInstallationsEnabled" with value : true

IoBroker Log throw error message:
31135) Send this info to developer !!! { Unhandable information found in DoHome : "legacyHeatingInstallationsEnabled" with value : true
Used accessoires from Tado:
Heating Thermostat 1x
Radiator theromstat 4x
Br
Arne

This schools ne fixed already, which version do you have installed ?

Hi,
I am still using 0.1.9 - I don't see the 0.2.0 version in iobroker - do I need to upgrade manually?

That sound that you are using the "default" repository for your adapters (which is fine as Tado is not released to stable yet)
If you want to use beta version, please switch your repository to "latest".
My suggestions always is to stay on stable if you are a regular end-user and only switch to beta if you exactly know how to troubleshoot and live with error (as other adapter update can break functionality)
Advice in this case : switch your repository temporary to latest, update the tado adapter (version 0.2.0-beta.1 will be shown)
Switch back to default again to keep all other adapters on stable version.
As long we release beta (expect to have stable release in October) this is the only propper way, by subscribing to this repository you will receive an message if new versions are released or join our Discord channel :)
https://discord.com/invite/HwUCwsH

Thank you, I've just updated the adapter manually via console and it after restarting it the error does not pop up anymore.

Thank you, I've just updated the adapter manually via console and it after restarting it the error does not pop up anymore.

thanks for the hint, indeed totally forget just using npm I iobroker.tado@latest does the same trick


Button BORDER_WIDTH is not being saved into rgs file

rGuiStyler may not be saving the button border width to the rgs file. After loading the style and making sure that guiStyleLoaded is true, GuiGetStyle(BUTTON, BORDER_WIDTH) always returns 2 even though it was set to 1 and saved.

I think the issue is related to raygui lazy initialization that overwrites button border width. How are you loading the new gui style?

GuiLoadStyle("./asset/gui_style/gui_style.rgs"); in the main function after I raylib InitWindow, before entering the main loop

@ssoher I updated raygui, now it should work as expected, please, could you try it?

Thank you @raysan5

Opened my style to make sure button width is 1, it shows up as 2. Made it 1 and save. Closed rGuiStyler, re-opened, opened the same style file and button border width is reset back to 2 again.
Pulled the latest raygui commit (https://github.com/raysan5/raygui/commit/e3f67f3c02300bf927a343d767d51b9b1ffe41a9) built my application, borders load up as 2.

I feel it has something to do with rGuiStyle serialization code but it's just a guess, didn't look at the code myself.

Here is the rgs file I'm observing this problem with if it helps you debug
gui_style.zip


message view: Make borders be 1px.

Is the idea to test-deploy this on chat.zulip.org for feedback?

Yup, exactly!

Done: https://chat.zulip.org/#narrow/stream/101-design/topic/message.20feed.20borders.20and.20unreads/near/1312412
Next time, it'd be helpful if you provided the backlink to the thread where this idea was proposed in this thread, since then I know what to read / update without having to be caught up :)

You have actually reduced the lines from 3px to 2px, not from 2px to 1px. This is because they’re composed of two shadows: an inner one that you’ve reduced from 2px to 1px, and an outer one that remains 1px).
A side effect of this change is that the unread marker is now separated from the stream color marker by 1px. Not sure whether that was intentional.

These commits are still only intended for prototyping on czo.

See https://chat.zulip.org/#narrow/stream/101-design/topic/message.20feed.20borders.20and.20unreads/near/1313321 for context.

Playing around with this PR, I noticed that while the stream color borders have been removed, we still have a black border for PMs. I suppose we should remove that too, since I don't think we're likely to keep the border for PMs and remove it for streams?

Playing around with this PR, I noticed that while the stream color borders have been removed, we still have a black border for PMs. I suppose we should remove that too, since I don't think we're likely to keep the border for PMs and remove it for streams?

Fixed.

When we push this to czo, I hope we can delay announcing the change, since I think it's occasionally the case that the "something looks different here" kind of feedback can be a good data point.
To repeat an earlier comment, this still isn't pixel perfect or ready for the main branch, but if we are happy with the second iteration of the experiment, it should be relatively straightforward to make a main-ready commit.

I'm test-deploying this to chat.zulip.org.

The unread markers are now significantly misaligned.

Removing the colored left border also makes it less obvious when the floating recipient bar hasn’t yet updated while scrolling the all messages view. The ideal fix is something like #9910, but without that, this makes the delayed update feel even more buggy.

Even though I knew this was coming, I failed to actually notice it! That said, I don't use All messages, so I only rarely find myself in multi-stream views.


Fix clone util to skip undefined children

This is particularly a problem when conditionally including a component/node into the toolbar, for example.

@abobwhite done. thanks for the contribution 👍


Two instance consumers in the same machine will both consume message in the mode of CLUSTERING.

There is a consumer in my application, I start this application twice with different ports, then there are two instance of application, and there are two consumers in the same machine. But the message is consumed in both consumers, but the consumers are set to CLUSTERING mode.
I checked in the rocketmq-console, the two consumers have same customerid.

This is normal behavior if you use the same consumer id @zhangdp-taozi please follow the issue template and read carefully, this is not the rational place for user question. Any question, please send to RocketMQ user email-list. Thanks for your comprehension.

If you could be careful of the code of the RocketMQ parts - how to create a instanceId, you will find the answer. As for consumerId, you could set the same consumerid to assemeble a cluster to consume together;


MAINT: add dividends datasets to inits

Adds dividends data/loaders to inits.

Coverage increased (+0.05%) to 88.863% when pulling 84171a562027172832a22b42cf08bd85a46c52a5 on finish-dividends-in-pipeline into 9b27f3439da44e4080df3a71963b64d860529587 on master.

Coverage increased (+0.002%) to 88.861% when pulling d7a012a4773cfa0f79cfc19b1f5c0dea427cf9b4 on finish-dividends-in-pipeline into 6a24731971ccc123926246b3cebb85710965e75b on master.

Coverage increased (+0.002%) to 88.861% when pulling d7a012a4773cfa0f79cfc19b1f5c0dea427cf9b4 on finish-dividends-in-pipeline into 6a24731971ccc123926246b3cebb85710965e75b on master.


Build failed: @types/aws-lambda

Environment
Node v18.14.0
unbuild v1.2.1
Caused by:
@types/aws-lambda v8.10.119
Reproduction
https://github.com/NamesMT/lambda-voie/tree/649142212e66e91c071389b6e57b224176d2369a
https://stackblitz.com/edit/github-5eousq?file=package.json
Enter the link above, install dependencies and run build.
Describe the bug
@types/aws-lambda have an export as namespace line that caused Syntax Error when building
Additional context
No response
Logs
~/projects/github-5eousq 1m 4s
❯ pnpm build

><EMAIL_ADDRESS>build /home/projects/github-5eousq
> unbuild

ℹ Building lambda-voie                                                                                18:17:07
Error building /home/projects/github-5eousq: SyntaxError: Unexpected token (96:7) in /home/projects/github-5eousq/node_modules/.pnpm/@types+aws-lambda<EMAIL_ADDRESS>SyntaxError: Unexpected token (96:7) in /home/projects/github-5eousq/node_modules/.pnpm/@types+aws-lambda<EMAIL_ADDRESS>    at pp$4.raise (file:///home/projects/github-5eousq/node_modules/.pnpm/rollup@3.26.0/node_modules/rollup/dist/es/shared/node-entry.js:21421:13)
    at pp$9.unexpected (file:///home/projects/github-5eousq/node_modules/.pnpm/rollup@3.26.0/node_modules/rollup/dist/es/shared/node-entry.js:18632:8)
    at pp$9.expect (file:///home/projects/github-5eousq/node_modules/.pnpm/rollup@3.26.0/node_modules/rollup/dist/es/shared/node-entry.js:18626:26)
    at pp$8.parseExportSpecifiers (file:///home/projects/github-5eousq/node_modules/.pnpm/rollup@3.26.0/node_modules/rollup/dist/es/shared/node-entry.js:19680:8)
    at Parser.parseExport (file:///home/projects/github-5eousq/node_modules/.pnpm/rollup@3.26.0/node_modules/rollup/dist/es/shared/node-entry.js:25883:32)
    at pp$8.parseStatement (file:///home/projects/github-5eousq/node_modules/.pnpm/rollup@3.26.0/node_modules/rollup/dist/es/shared/node-entry.js:18808:74)
    at pp$8.parseTopLevel (file:///home/projects/github-5eousq/node_modules/.pnpm/rollup@3.26.0/node_modules/rollup/dist/es/shared/node-entry.js:18689:21)
    at Parser.parse (file:///home/projects/github-5eousq/node_modules/.pnpm/rollup@3.26.0/node_modules/rollup/dist/es/shared/node-entry.js:18461:15)
    at _0x35edf6.parse (file:///home/projects/github-5eousq/node_modules/.pnpm/rollup@3.26.0/node_modules/rollup/dist/es/shared/node-entry.js:18511:35)
    at Graph.contextParse (file:///home/projects/github-5eousq/node_modules/.pnpm/rollup@3.26.0/node_modules/rollup/dist/es/shared/node-entry.js:25547:38) {
  pos: 5039,
  loc: {
    column: 7,
    file: '/home/projects/github-5eousq/node_modules/.pnpm/@types+aws-lambda<EMAIL_ADDRESS>    line: 96
  },
  raisedAt: 5041,
  frame: "94: export * from './trigger/amplify-resolver';\n" +
    '95: \n' +
    '96: export as namespace AWSLambda;\n' +
    '           ^',
  id: '/home/projects/github-5eousq/node_modules/.pnpm/@types+aws-lambda<EMAIL_ADDRESS>  hook: 'resolveId',
  code: 'PLUGIN_ERROR',
  plugin: 'commonjs--resolver',
  watchFiles: [
    '/home/projects/github-5eousq/src/index.ts',
    '/home/projects/github-5eousq/src/logger.ts',
    '/home/projects/github-5eousq/src/utils.ts',
    '/home/projects/github-5eousq/node_modules/.pnpm/@types+aws-lambda<EMAIL_ADDRESS>  ]
}
 ELIFECYCLE  Command failed with exit code 1.

I have the exact same error in a pnpm monorepo with the h3 reference:
 ERROR  Error building /home/wsl/repos/project/common/core: SyntaxError: Unexpected token (8:5) in<EMAIL_ADDRESS>                                   4:18:42 PM

 ERROR  Unexpected token (8:5) in<EMAIL_ADDRESS>

I have the exact same error in a pnpm monorepo with the h3 reference:
 ERROR  Error building /home/wsl/repos/project/common/core: SyntaxError: Unexpected token (8:5) in<EMAIL_ADDRESS>                                   4:18:42 PM

 ERROR  Unexpected token (8:5) in<EMAIL_ADDRESS>
  at pp$4.raise (/home/wsl/repos/project/node_modules/.pnpm/rollup@3.29.4/node_modules/rollup/dist/es/shared/node-entry.js:21621:13)
  at pp$9.unexpected (/home/wsl/repos/project/node_modules/.pnpm/rollup@3.29.4/node_modules/rollup/dist/es/shared/node-entry.js:18829:8)
  at pp$9.semicolon (/home/wsl/repos/project/node_modules/.pnpm/rollup@3.29.4/node_modules/rollup/dist/es/shared/node-entry.js:18806:66)
  at pp$8.parseExpressionStatement (/home/wsl/repos/project/node_modules/.pnpm/rollup@3.29.4/node_modules/rollup/dist/es/shared/node-entry.js:19295:8)
  at pp$8.parseStatement (/home/wsl/repos/project/node_modules/.pnpm/rollup@3.29.4/node_modules/rollup/dist/es/shared/node-entry.js:19022:24)
  at pp$8.parseTopLevel (/home/wsl/repos/project/node_modules/.pnpm/rollup@3.29.4/node_modules/rollup/dist/es/shared/node-entry.js:18886:21)
  at Parser.parse (/home/wsl/repos/project/node_modules/.pnpm/rollup@3.29.4/node_modules/rollup/dist/es/shared/node-entry.js:18658:15)
  at Function.parse (/home/wsl/repos/project/node_modules/.pnpm/rollup@3.29.4/node_modules/rollup/dist/es/shared/node-entry.js:18708:35)
  at Graph.contextParse (/home/wsl/repos/project/node_modules/.pnpm/rollup@3.29.4/node_modules/rollup/dist/es/shared/node-entry.js:25754:38)
  at tryParse (/home/wsl/repos/project/node_modules/.pnpm/@rollup+plugin-commonjs@25.0.7_rollup@3.29.4/node_modules/@rollup/plugin-commonjs/dist/es/index.js:17:12)
  at analyzeTopLevelStatements (/home/wsl/repos/project/node_modules/.pnpm/@rollup+plugin-commonjs@25.0.7_rollup@3.29.4/node_modules/@rollup/plugin-commonjs/dist/es/index.js:37:15)
  at Object.transformAndCheckExports (/home/wsl/repos/project/node_modules/.pnpm/@rollup+plugin-commonjs@25.0.7_rollup@3.29.4/node_modules/@rollup/plugin-commonjs/dist/es/index.js:2085:68)
  at Object.transform (/home/wsl/repos/project/node_modules/.pnpm/@rollup+plugin-commonjs@25.0.7_rollup@3.29.4/node_modules/@rollup/plugin-commonjs/dist/es/index.js:2285:41)
  at /home/wsl/repos/project/node_modules/.pnpm/rollup@3.29.4/node_modules/rollup/dist/es/shared/node-entry.js:25544:40

Do you know how to fix it? I encountered the same error while using Prettier.

If the type package is installed under devDependencies, it seems to cause a build failure.

I'm having a similar issue with @types/express and a transitive dependency.
npm run build

><EMAIL_ADDRESS>build
> unbuild

ℹ Automatically detected entries: src/index [esm] [cjs] [dts]                                                                                12:32:24 PM
ℹ Building pae-microservices-runtime-sdk                                                                                12:32:24 PM
ℹ Cleaning dist directory: ./dist                                                                                12:32:24 PM

[12:32:25 PM]  ERROR  Error building /Users/jfernandes/dev/platform/pae/pae-microservices-runtime-sdk: SyntaxError: Unexpected token (19:8) in<EMAIL_ADDRESS>

 ERROR  Unexpected token (19:8) in<EMAIL_ADDRESS>                              12:32:25 PM

  at pp$4.raise (node_modules/rollup/dist/es/shared/node-entry.js:21621:13)
  at pp$9.unexpected (node_modules/rollup/dist/es/shared/node-entry.js:18829:8)
  at pp$9.semicolon (node_modules/rollup/dist/es/shared/node-entry.js:18806:66)
  at pp$8.parseExpressionStatement (node_modules/rollup/dist/es/shared/node-entry.js:19295:8)
  at pp$8.parseStatement (node_modules/rollup/dist/es/shared/node-entry.js:19022:24)
  at pp$8.parseTopLevel (node_modules/rollup/dist/es/shared/node-entry.js:18886:21)
  at Parser.parse (node_modules/rollup/dist/es/shared/node-entry.js:18658:15)
  at Function.parse (node_modules/rollup/dist/es/shared/node-entry.js:18708:35)
  at Graph.contextParse (node_modules/rollup/dist/es/shared/node-entry.js:25754:38)
  at tryParse (node_modules/@rollup/plugin-commonjs/dist/es/index.js:17:12)

 ERROR  Unexpected token (19:8) in<EMAIL_ADDRESS>
I've tried moving the dependency from "devDependencies" but got the same error.
It seems to be a pretty straighforward build configuration
{
  "name": "pae-microservices-runtime-sdk",
  "version": "1.0.0",
  "type": "module",
  "exports": {
    ".": {
      "import": "./dist/index.mjs",
      "require": "./dist/index.cjs"
    }
  },
  "main": "./dist/index.cjs",
  "types": "./dist/index.d.ts",
  "files": ["dist"],
  "scripts": {
    "build": "unbuild"
  },
  "dependencies": {
    "ts-loader": "9.5.1",
    "typescript": "5.4.4"
  },
  "devDependencies": {
    "@types/express": "^4.17.21",
    "@types/node": "^20.12.6",
    "unbuild": "2.0.0"
  }
}

I'd appreciate any ideas or suggestions.
Thanks !

If the type package is installed under devDependencies, it seems to cause a build failure.

Saved my day. Thanks!


Fix NullDereferenceException in Add-PnPField

Fix NullDereferenceException in Add-PnPField when not including -Type parameter and specifying Choice, MultiChoice or Calculated as Type later on
Before creating a pull request, make sure that you have read the contribution file located at
https://github.com/pnp/powerShell/blob/dev/CONTRIBUTING.md
Type

[x] Bug Fix
[ ] New Feature
[ ] Sample

Related Issues?
No linked issues
What is in this Pull Request ?
Similar to https://github.com/pnp/powershell/pull/2156 and New-PnPSite, this PR fixes NullDereferenceExceptions thrown when calling Add-PnPField without specifying -Type parameter but later selecting a Type that requires dynamic parameters.
The affected -Type options are:

Choice
MultiChoice
Calculated

Tests
Old behavior:

New behavior:

Test passing -Type:

Test without passing -Type but specifying Text:

Thanks @jackpoz for fixing this, have merged this.


AddInsACS assessment queued

Hi,
When trying to start an AddInsACS assessment got the following error: "Assessment job not started due to error: Invalid URI: The format of the URI could not be determined.", when running list command the job shows as queued, any clues? (I'm suspecting that could have some to do with Vanity URLs, my tenant uses them but InfoPath and Workflow scans works fine).
Please assist
Thanks!

@Zetkai84 : could there be a wrongly formatted url in your sites file (lastsitelist.txt)?

Got the same error even if I don't use site list file, also works fine for Workflow or InfoPath assessment. I've set up settings file as My tenant is using vanity urls

@Zetkai84 : can you share the command line used and the created log file? If these can't be shared publicly then send them to<EMAIL_ADDRESS>

closing per offline discussion with @Zetkai84 .


update default filters

RetryFilter: Filters out hosts that have already been attempted for scheduling purposes. If the scheduler selects a host to respond to a service request, and the host fails to respond to the request, this filter prevents the scheduler from retrying that host for the service request.
AvailabilityZoneFilter: Filters hosts by availability zone. You must enable this filter for the scheduler to respect availability zones in requests.
RamFilter: Only schedules instances on hosts that have sufficient RAM available.
ComputeFilter: Passes all hosts that are operational and enabled.
CoreFilter: Only schedules instances on hosts if sufficient CPU cores are available.
ComputeCapabilitiesFilter: Matches properties defined in extra specs for an instance type against compute capabilities.
ImagePropertiesFilter: Filters hosts based on properties defined on the instance's image.
ServerGroupAntiAffinityFilter,ServerGroupAffinityFilter: allow for affinty/antiaffinity based on server group membership.

retest

why you gotta be like this jenkins ?

restest

retest

This looks good to me, once jenkins gets done making you it's....

retest

retest


Assign "hover over tool-tip" to a  keyboard combination

VSCode Version: 1.11.2
OS Version: 1.11.2, Windows 7 Pro, Service PAck 1

Steps to Reproduce:

Hover cursor over code

Requesting a feature:
The "hover over tool-tip" is very annoying. Most of the time it blocks the code I am looking at. I am aware I can disable it in settings.json file by doing "editor.hover":  false, but I need the feature sometimes.  It would be great to assign its invocation to a keyboard combination like "CTRL+SHIFT+T". This way it is always off until you need it at which time you could invoke it by hitting "CTRL+SHIFT+T" or a keyboard combination of user's choice settable in "settings.json" file.

This extension https://marketplace.visualstudio.com/items?itemName=hoovercj.vscode-settings-cycler can help you out with this problem. You can disable it in your settings file, turn it on by shortcut when you want to have it.


Use EncodeUri() if part of the URL path or EncodeUriComponent() if used as a URL parameter

When reviewing your template we've noticed that it is using parameters to build a url. It's a best practice to use [EncodeUri()](https://developers.google.com/tag-manager/templates/api#encodeuri) if part of the URL path or [EncodeUriComponent()](https://developers.google.com/tag-manager/templates/api#encodeuricomponent) if used as a URL parameter.

I added the encodeUri https://github.com/EdinCuturic/awin-advertiser-mastertag-google-tag-manager/commit/ec5b664e257567896e1af512a8d4405489152821


Group Chat with TEAMS

You have done an amazing job with the design.
Try to develop a group chat with teams feature with a different design style
What I mean is, let's say we have a party house group, In that group, there will be 2teams For Example Samsung and iPhone, People can join either Samsung or iPhone, Once they select their team then they will be sent to the chat section filled with Samsung and iPhone teams. For the Samsung team users, all their group members chats including theirs will be on the right side and iPhone users on the left.

I am adding the Rooms feature soon, so owner can make rooms & members can join those rooms.


add github issue templates for bug report and feature request, to facilitate project management

Closes: https://github.com/osmosis-labs/osmosis/issues/1339
What is the purpose of the change
This PR adds github issue templates for bug report and feature request, to facilitate project management and prioritization
Brief change log

added template "bug_report.md"
added template "feature_request.md" to redirect to https://github.com/osmosis-labs/feature-requests/issues

Testing and Verifying
Tested in my local repo. Here's the workflow and screenshots

click "New issue" as usual

with this PR, github will start to show 2 templates to choose from

choose "Bug report", the bug report template will show up as prepopulated

Documentation and Release Note

Does this pull request introduce a new feature or user-facing behavior changes? (no)
Is a relevant changelog entry added to the Unreleased section in CHANGELOG.md? (no)
How is the feature or change documented? (not applicable)

cc @ValarDragon @alexanderbez @daniel-farina

btw, you can try and see it yourself here

Codecov Report

Merging #1348 (039404e) into main (f56fbe5) will decrease coverage by 0.02%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #1348      +/-   ##
==========================================
- Coverage   19.82%   19.79%   -0.03%
==========================================
  Files         202      202
  Lines       27685    27725      +40
==========================================
  Hits         5489     5489
- Misses      21175    21215      +40
  Partials     1021     1021

Impacted Files
Coverage Δ

x/gamm/pool-models/balancer/amm.go
17.58% <ø> (ø)

x/gamm/pool-models/stableswap/amm.go
43.28% <0.00%> (-12.49%)
:arrow_down:

x/gamm/pool-models/stableswap/pool.go
0.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 1c7ea07...039404e. Read the comment docs.

Hi @jlbit !
Thanks for this template. Everything looks great. I would only like to suggest having another type of issue.
I think it would be useful to have a story/task type of issue to be mainly used by the core team. Feature requests and the suggested template seem to be useful for external contributors. On the other hand, when our team members write up the issues, they are, oftentimes, not requests but well-defined stories or tasks.
In addition, I find having "Acceptance Criteria" extremely useful. These short descriptions help with defining what exactly needs to be fulfilled for a solution to the issue to be accepted. It helps the author of the issue to plan the scope in advance. Moreover, it eases the reviewer's job by letting them go through the checklist and make sure that all "Acceptance Criteria" have been met. I've brought this up with the team, and folks seemed to be happy to try it. Please take a look at the following example of its use: https://github.com/osmosis-labs/osmosis/issues/1332
Please let me know what you think

@p0mvn right, the feature requests are from external users, and @daniel-farina pointed out that such requests should be in https://github.com/osmosis-labs/feature-requests/issues rather than the main repo to avoid distraction.
I've updated the PR to have feature_request.md redirecting to https://github.com/osmosis-labs/feature-requests/issues, and greatly simplified bug_reports.md

Thanks for the update @jlbit
My earlier comment about needing a type for a story/task issue still seems to apply. Our team doesn't only create issues for bugs. Most of the time, we create an issue to do a simple task that may or may not require a code change or investigate a problem. The current bug report template wouldn't apply to a large proportion of the issues that our team creates since most of them are not bugs.
Having a story/task type of issue with sections like:

"Background"
"Acceptance Criteria"
would be helpful. Here is an example: https://github.com/osmosis-labs/osmosis/issues/1332

I understand that this issue type would primarily be meant to be used by the team. We could add a note in the description about the purpose of this template.

I'm going to close this for now since there is a more up to date PR with this: https://github.com/osmosis-labs/osmosis/pull/1399
Please let me know if any concerns


SmartIR stopped working after recent Homeassisant update

Home Assistant version
HassOS 4.13
SmartIR version
1.13.2
SmartIR configuration

smartir:

switch:
  - platform: broadlink
    host: <IP_ADDRESS>
    mac: '78:0F:77:60:B3:75'

climate:
  - platform: smartir
    name: AircoDion
    unique_id: aircodion
    device_code: 4020
    controller_data: <IP_ADDRESS>

Describe the bug
So it randomly stopped working. And getting these errors inside the console of core
Debug log
2020-09-21 20:40:07 ERROR (MainThread) [custom_components.smartir.climate] not a valid value for dictionary value @ data['entity_id']
Traceback (most recent call last):
  File "/config/custom_components/smartir/climate.py", line 330, in send_command
    await self._controller.send(self._commands['off'])
  File "/config/custom_components/smartir/controller.py", line 109, in send
    await self.hass.services.async_call(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1269, in async_call
    processed_data = handler.schema(service_data)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/validators.py", line 208, in __call__
    return self._exec((Schema(val) for val in self.validators), v)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/validators.py", line 287, in _exec
    raise e if self.msg is None else AllInvalid(self.msg, path=path)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/validators.py", line 283, in _exec
    v = func(v)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/schema_builder.py", line 272, in __call__
    return self._compiled([], data)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/schema_builder.py", line 817, in validate_callable
    return schema(data)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/schema_builder.py", line 272, in __call__
    return self._compiled([], data)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/schema_builder.py", line 594, in validate_dict
    return base_validate(path, iteritems(data), out)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/schema_builder.py", line 432, in validate_mapping
    raise er.MultipleInvalid(errors)
voluptuous.error.MultipleInvalid: not a valid value for dictionary value @ data['entity_id']

Additional context
Add any other context about the problem here.

https://github.com/smartHomeHub/SmartIR/issues/480#issuecomment-695755305

Also stopped working for me in latest update, the UI works but no IR is being sent, and there is nothing in the error log regarding this.
climate:
  - platform: smartir
    name: Livingroom AC
    unique_id: livingroom_ac
    device_code: 4
    controller_data: remote.livingroombroadlink_remote

It is impossible not to have an error in the logs.

I dont know what to say, it worked before the latest update (0.115.2) and for years before that :)
I changed to the new format once the new broadlink integration and smartir came out.

I'm clicking it a bunch of times, multiple temps/fan speeds etc... nothing is coming out of the broadlink device from climate (but its working on my other "manual" switches with the built in integration)

Did you try if the remote.send_command service works properly?

Hmm you're right that didnt work for me either, so it turns out that this needs to be turned on (dont know how it got turned off but its such a bad user experience from HA with this new integration)

now its working, thanks for the help

Oh, I do not even know what this switch means.


goleak: Errors on successful test run: found unexpected goroutines: k8s.io/client-go/util/workqueue.(*delayingType).waitingLoop

CI failure
Hit on unrelated PR: https://github.com/cilium/cilium/pull/27232
2023-10-09T09:10:17.2939044Z FAIL	github.com/cilium/cilium/operator/pkg/lbipam	4.408s

2023-10-09T09:10:17.2929437Z goleak: Errors on successful test run: found unexpected goroutines:
2023-10-09T09:10:17.2931023Z [Goroutine 87 in state select, with k8s.io/client-go/util/workqueue.(*delayingType).waitingLoop on top of the stack:
2023-10-09T09:10:17.2932040Z goroutine 87 [select]:
2023-10-09T09:10:17.2933690Z k8s.io/client-go/util/workqueue.(*delayingType).waitingLoop(0xc000869320)
2023-10-09T09:10:17.2935011Z 	/host/vendor/k8s.io/client-go/util/workqueue/delaying_queue.go:276 +0x305
2023-10-09T09:10:17.2937442Z created by k8s.io/client-go/util/workqueue.newDelayingQueue in goroutine 74
2023-10-09T09:10:17.2938366Z 	/host/vendor/k8s.io/client-go/util/workqueue/delaying_queue.go:113 +0x21f

I'm not entirely sure whether area/ci + ci/flake are the right labels. This looks more like a code correctness issue identified by CI.

hit here as well: https://github.com/cilium/cilium/actions/runs/6483079306/attempts/1. I see at least 1 other similar, recent failure in the job history as well https://github.com/cilium/cilium/actions/runs/6483875611

I know Dylan was looking into this so I'll assign him for now. It looks like it may have been introduced by https://github.com/cilium/cilium/pull/27340.


feature: add Paths Interface

Proposed changes

This PR is targeting the develop branch.
Some implementations may rely on a gateway or bridge to communicate with the internet.
This is especially more common in IoT and mesh networks.
This PR adds an interface to support environments where a properly formatted URL can be obtained for passing to another device.
• Add 'Host' class
• Add 'Host' tests
• Update CMakeLists.txt to find 'Host' class & test
• Add Path Interface
• Add Path tests
• Update CMakeLists.txt to find 'Paths' & test
• Add Path examples in documentation
• Update API headers to include 'Host'
• Update API Classes to utilize Paths
• Update MockApi to utilize Paths
• Remove 'host' and 'ip' from 'HTTP'
• Remove 'HTTP' 'setHost' class and mock methods
• Update 'HTTP' to receive only a formatted request/url
Types of changes

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Refactoring (improve a current implementation without adding a new feature or fixing a bug)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Build (changes that affect the build system)
[ ] Docs (documentation only changes)
[ ] Test (adding missing tests or fixing existing tests)
[ ] Other... Please describe:

Checklist

[x] I have read the CONTRIBUTING documentation
[x] Lint and unit tests pass locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)

Codecov Report

Merging #46 into develop will increase coverage by 35.49%.
The diff coverage is 84.05%.

@@             Coverage Diff              @@
##           develop      #46       +/-   ##
============================================
+ Coverage    37.93%   73.42%   +35.49%
============================================
  Files           20       23        +3
  Lines          203      301       +98
============================================
+ Hits            77      221      +144
+ Misses         126       80       -46

Impacted Files
Coverage Δ

src/include/cpp-client/connection/connection.h
100% <ø> (ø)
:arrow_up:

src/api/votes/votes.cpp
0% <0%> (ø)
:arrow_up:

src/api/wallets/wallets.cpp
0% <0%> (ø)
:arrow_up:

src/api/delegates/delegates.cpp
0% <0%> (ø)
:arrow_up:

src/api/node/node.cpp
0% <0%> (ø)
:arrow_up:

src/api/transactions/transactions.cpp
0% <0%> (ø)
:arrow_up:

src/api/peers/peers.cpp
0% <0%> (ø)
:arrow_up:

src/include/cpp-client/api/abstract.h
100% <100%> (ø)
:arrow_up:

src/include/cpp-client/api/api.h
100% <100%> (ø)
:arrow_up:

src/include/cpp-client/api/base.h
100% <100%> (ø)
:arrow_up:

... and 17 more

Continue to review full report at Codecov.

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


Index out of range while slicing ReadOnlyBuffer

hi there im having issues with ReadOnlyBuffer.

the ReadCursor is at 4018 end is 4032 and im trying to slice 2. why do i get index out of bounds exception? for me the segment in the cursor looks broken as readcursor.tosting ends with hello w but the segment seem to just contain the first character

the issue seems to be that the buffer is not a single span buffer and end.index is smaller than start.index

i switched to ReadableBufferReader and now the issue is more clear. the end of the buffer is set wrong by System.IO.Pipelines.Socket.SocketConnection. the reader has readcursor at index 3116 with end = true but the read result (input) of the socket pipe says end is readcoursor at 3120 but that does not have IsEnd = true so i suppose the endcoursor of the readbuffer produced by the socket is wrong.

@JanEggers just FYI, we have no plans to ship:

System.IO.Pipelines.Networking.Libuv
System.IO.Pipelines.Networking.Sockets
System.IO.Pipelines.Networking.Windows.RIO

These implementations exist to help push the design of pipelines forward but the true implementations will ship as part of the bedrock effort described here https://github.com/aspnet/KestrelHttpServer/issues/1980.
We should still make sure this isn't a general pipeline issue.

im just experimenting with the bits i can find until the rock rocks

Kewl. Also you might want to look at https://github.com/aspnet/KestrelHttpServer/blob/bb9840a5529405fb0a78d8acf748e9390786e9b0/src/Kestrel.Core/Internal/Http/HttpParser.cs to see how a very fast parser can be written using pipelines APIs today.

my fault after all, reader.end == input.end, the issue was my parser that calculated the remaining bytes based on reader.Index and not reader.ConsumedBytes. for me it would have been less confusing if the reader has a Length property with the length of the buffer or Index could be renamed to IndexInCurrentSpan like the Span property should be CurrentSpan to indicate it is not the complete span, or if there would be a Property with the total remaining bytes because that was where i screwed it up.


Querying elements does provide unexpected behavior

react-testing-library version: 5.3.2
react version: 16.6.0
node version: 8.12.0
yarn version: 1.12.3

Relevant code or config:
const renderer1 = render(

); // first render
const renderer2 = render(

); // second render

console.log(renderer1.queryByTestId('first-render') !== null) // true
console.log(renderer1.queryByTestId('second-render') === null) // should true (but getting false)

console.log(renderer2.queryByTestId('first-render') === null) // should true (but getting false)

What you did:
I'm testing two components at same time.
What happened:
I have two separate components and when I rendered both at same time and querying elements does not provide expected behavior.
Reproduction:
Here is online a demo: https://stackblitz.com/edit/react-ts-dixecs?file=index.tsx
Problem description:
Querying elements searches from baseElement instead of container element, this makes elements available from another render.
Suggested solution:
The solution is, needs to generate queries on container element instead of baseElement (https://github.com/kentcdodds/react-testing-library/blob/master/src/index.js#L50).

baseElement defaults to the container in https://github.com/kentcdodds/react-testing-library/blob/master/src/index.js#L8, so there may be some other issue

@alexkrolick baseElement defaults to document.body in https://github.com/kentcdodds/react-testing-library/blob/master/src/index.js#L13 if container is undefined and container is a child node of document.body

generate queries on container element instead of baseElement

The queries are based on the baseElement so that testing portals is straightforward. It should normally work fine because you should be rendering your element on a clean HTML document so it shouldn't make any difference. Typically you will not be calling render in a single test (just like you wouldn't typically do ReactDOM.render twice in your app). Is there a reason you're calling render twice?

@kentcdodds yes and no :)
it is being called twice, the component is rendering in beforeEach at the first time and I have one special case that needs to render the element with different props as freshly. The second render with different props change some nodes and when I'm expecting that nodes to be null the query function is finding that nodes from the previous render giving me a not null value.
It should not happen if I'm getting query methods from renderer like this:
const {getByTestId} = renderer;
this does not make sense to me when it gets the element from other render.

If you are doing a render in beforeEach, you can include an afterEach that cleans up the DOM after each test:
import { cleanup } from 'react-testing-library'
afterEach(cleanup);

https://github.com/kentcdodds/react-testing-library#cleanup

I'm using cleanup in afterEach but in this case I have to use cleanup before creating new render in my special case which resolves my problem.
Just to let you know, I noticed sometimes when I forget to add cleanup it gives me the same problem.
It makes more sense to me to scope queries to each new render which I can achieve by custom render within your provided example.
BTW, thanks for help.


trovo.live

Checklist

[x] I'm reporting a new site support request
[x] I've verified that I'm running youtube-dl version 2<IP_ADDRESS>
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that none of provided URLs violate any copyrights
[x] I've searched the bugtracker for similar site support requests including closed ones

Example URLs

Example Stream: https://trovo.live/RelaxBeats

Description

Trovo is an interactive live streaming platform, you can check out the hottest games live, share your own gaming experiences, and join an amazing community created especially for gamers, creators and do-ers.... is like Twitch and also looks similar.
# ./youtube-dl -v https://www.trovo.live/RelaxBeats
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'-v', u'https://www.trovo.live/RelaxBeats']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2<IP_ADDRESS>
[debug] Python version 2.7.13 (CPython) - Linux-4.9.182-xxxx-std-ipv6-64-x86_64-with-Debian-7
[debug] exe versions: avconv 3.2.14-1, avprobe 3.2.14-1, ffmpeg N-48007-g62f8d27ef1-static, ffprobe 3.2.14-1
[debug] Proxy map: {}
[generic] RelaxBeats: Requesting header
WARNING: Could not send HEAD request to https://www.trovo.live/RelaxBeats: HTTP Error 405: Method Not Allowed
[generic] RelaxBeats: Downloading webpage
WARNING: Falling back on generic information extractor.
[generic] RelaxBeats: Extracting information
ERROR: Unsupported URL: https://www.trovo.live/RelaxBeats
Traceback (most recent call last):
  File "./youtube-dl/youtube_dl/extractor/generic.py", line 2387, in _real_extract
    doc = compat_etree_fromstring(webpage.encode('utf-8'))
  File "./youtube-dl/youtube_dl/compat.py", line 2562, in compat_etree_fromstring
    doc = _XML(text, parser=etree.XMLParser(target=_TreeBuilder(element_factory=_element_factory)))
  File "./youtube-dl/youtube_dl/compat.py", line 2551, in _XML
    parser.feed(text)
  File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1653, in feed
    self._raiseerror(v)
  File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1517, in _raiseerror
    raise err
ParseError: syntax error: line 1, column 0
Traceback (most recent call last):
  File "./youtube-dl/youtube_dl/YoutubeDL.py", line 797, in extract_info
    ie_result = ie.extract(url)
  File "./youtube-dl/youtube_dl/extractor/common.py", line 530, in extract
    ie_result = self._real_extract(url)
  File "./youtube-dl/youtube_dl/extractor/generic.py", line 3382, in _real_extract
    raise UnsupportedError(url)
UnsupportedError: Unsupported URL: https://www.trovo.live/RelaxBeats

Hi,
I'm giving this a push. Would be also interested at this site.
Would like to give this additional infos:
Example URLs

Single video: https://trovo.live/video/ltv-100095501_100095501_1609596043?ltab=videos
Playlist: https://trovo.live/Exsl (the video tab shows all stuff)
Live Stream: https://trovo.live/Exsl (if channel is live)

Description
Trovo is a gaming streaming portal. Login credentials should be not required. There are strems with age verification by a simple button. I'm really don't know much about extracting stuff. I'm able to find a URL of an .m3u8 file with Web Development tools in Firefox which can be passed to ffmpeg. It seems to have it's home in a big Nuxt.js object. Site itself looks full of JavaScript. For me it looks a bit tricky to parse out the download url. Googled a bit how to handle things but I think my knowledge is not enough to build a working extractor at this moment. Would be very thankful for an extractor which supports single video download, download of the past streams and clips and recording a livestream.

Hi,
I'm giving this a push. Would be also interested at this site.
Would like to give this additional infos:
Example URLs

Single video: https://trovo.live/video/ltv-100095501_100095501_1609596043?ltab=videos
Playlist: https://trovo.live/Exsl (the video tab shows all stuff)
Live Stream: https://trovo.live/Exsl (if channel is live)

Description
Trovo is a gaming streaming portal. Login credentials should be not required. There are strems with age verification by a simple button. I'm really don't know much about extracting stuff. I'm able to find a URL of an .m3u8 file with Web Development tools in Firefox which can be passed to ffmpeg. It seems to have it's home in a big Nuxt.js object. Site itself looks full of JavaScript. For me it looks a bit tricky to parse out the download url. Googled a bit how to handle things but I think my knowledge is not enough to build a working extractor at this moment. Would be very thankful for an extractor which supports single video download, download of the past streams and clips and recording a livestream.

Wanted to bump this as well as I would also be interested in downloading from here

Wanted to bump this as well as I would also be interested in downloading from here

Would like support for Trovo as well—creators are moving over DLive.

Would like support for Trovo as well—creators are moving over DLive.

This would be a decent addition, Many popular creators from Dlive are moving over to Trovo due to censorship and persecution. Would be nice to be able to download vods that I've missed.

This would be a decent addition, Many popular creators from Dlive are moving over to Trovo due to censorship and persecution. Would be nice to be able to download vods that I've missed.


Add mysql command

Add the mysql command to quickly open a mysql root shell into the
runnind database container of the stack.
Kudos to Lando for the idea.
Also: alias the wp command to the cli one.
Screencast of the mysql command and wp alias in action.

Looks useful!


feat: ttl=0/instant/forever/humantime&ttl refactor

I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
What's changed and what's your intention?
support ttl='instant'/'forever'
Please explain IN DETAIL what the changes are in this PR and why they are needed:

support ttl='instant'/'forever', however to keep compatibilty, ttl='0s'/'null'/'' still equals to ttl='forever'
refactor ttl to enum
refactor table/database ttl, so that once table ttl is set, it can't be override by database, only after unset table ttl can database ttl be applied on a table
add more sqlness tests for alter ttl

Checklist

[ ] I have written the necessary rustdoc comments.
[ ] I have added the necessary unit tests and integration tests.
[x] This PR requires documentation updates.

Use instant instead of immediate for brevity and clarity. What do you think? @discord9

Use instant instead of immediate for brevity and clarity. What do you think? @discord9

How about imme or now? instant also seems a bit long

now sounds good. imme isn't well-known.

Seems to be encounter https://github.com/rust-lang/rust/issues/64552
Trying to bypass it

added a fix for alter ttl to instant should remove expired ssts too

Don't forget to update the PR title and description.

should SET DATABASE 'ttl'='instant' be forbidden? Or should on insert also check database ttl?

should SET DATABASE 'ttl'='instant' be forbidden? Or should on insert also check database ttl?

Let's prohibit the database from setting TTL to instant, as it is illogical.


fix: use util.TextEncoder, util.TextDecoder for Node 10

Fixes #947 (once more), specifically, this comment.

@alexander-fenster LGTM, but it seems like we should make sure browser tests are passing for this one?


Fix erroneous workflow cancellation

The concurrency groups for both integration-tests and test-mindeps were named the same, creating a race condition such that whichever workflow was started first would be cancelled by the start of the second workflow. This fix gives them distinct group names to avoid erroneously cancelling one or the other.
Fixes #503

📚 Documentation preview 📚: https://earthaccess--505.org.readthedocs.build/en/505/

Ah, nice! Thanks @chuckwondo

Great eye!


Remove scrollIntoView for activeTab

Problem solved
Short description of the bug fixed or feature added

PR-Codex overview
This PR focuses on modifying the transition effects and scroll behavior of tab elements in the tabs.tsx component.
Detailed summary

Added a transition effect for lineEl with properties transform and width over 0.3s.
Removed the scrollIntoView method call for -activeTabEl with smooth behavior and specific alignment options.
Adjusted the width of lineRef.current to 0px if it exists.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

#5000  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @MananTank and the rest of your teammates on  Graphite


Update to use DLPack v0.6

Update DLPack version from v0.3 to v0.6

Rename kPinned => kCUDAHost
Fix class/field names

Rename DLContext -> DLDevice
DLTensor.ctx -> DLTensor.device

Add kCudaManaged type

The followings are updates from the DLPack header file:
v0.6

Add kDLROCMHost
Add kDLCUDAManaged

v0.5

kDLGPU -> kDLCUDA
kDLCPUPinned -> kDLCUDAHost

v0.4

OpaqueHandle type
Complex support
Rename DLContext -> DLDevice

DLTensor.ctx -> DLTensor.device
This requires dependent frameworks to upgrade the type name.
The ABI is backward compatible, as it is only change of constant name, exchange can still happen between the new version and old version.

Address #67
Signed-off-by: Gigon Bae<EMAIL_ADDRESS>

@gpucibot merge

Thanks Gigon! 🙏


Error in compiling project

In file included from ...\Arduino\libraries\sim800\sim800Client.h:6:0,
             from ...\Arduino\libraries\sim800\sim800.cpp:21:

...\Arduino\libraries\sim800\sim800.h:14:24: error: 'Serial1' was not declared in this scope
#define HARDWARESERIAL Serial1
                    ^

...\Arduino\libraries\sim800\sim800.cpp:27:28: note: in expansion of macro 'HARDWARESERIAL'
HardwareSerial *modem = &HARDWARESERIAL;
                        ^

exit status 1
Error compiling for board Arduino Nano.
PS: i am beginner in Ardunio plz suggest me

Try to add HardwareSerial.h on your sketch.
#include "HardwareSerial.h
See this Topic for more info.


Example missing import of rxjs methods

[Example missing import of rxjs methods for filter, Subject, takeUntil. Theese are used in the broadcast service MSAL subject. Had to add this to make it work: import { filter, Subject, takeUntil } from 'rxjs';]

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

ID: 83fd7dcc-68e2-b9a4-cda7-b03a21449579
Version Independent ID: 87e2ea5c-7e9d-027b-34f2-516229b38299
Content: Acquire a token to call a web API (single-page apps) - Microsoft identity platform
Content Source: articles/active-directory/develop/scenario-spa-acquire-token.md
Service: active-directory
Sub-service: develop
GitHub Login: @negoe
Microsoft Alias: negoe

@tnorling @sameerag Can one of you please take a look at this for livesite? Thanks!

@BennyHoang Can you confirm the headers are missing in the Angular v2 docs? @derisen Can you please update these if that is the case?

@sameerag looking into it. @JamesTran-MSFT please assign this on me.


Weight base & longest waiting-master

Weight base & longest waiting-master

Please validate possible null values before its use to ignore the possible panic paths.
ex:- validate concInfo and handle error properly
concInfo, err := GetConcurrencyInfo(resObj.Company, resObj.Tenant, resObj.ResourceId, reqObj.RequestType)
if err != nil {
fmt.Println("Error in GetConcurrencyInfo")
}
calcWeight := CalculateWeight(reqObj.AttributeInfo, resObj.ResourceAttributeInfo)
resKey := fmt.Sprintf("Resource:%d:%d:%s", resObj.Company, resObj.Tenant, resObj.ResourceId)
var tempWeightInfo WeightBaseResourceInfo
tempWeightInfo.ResourceId = resKey
tempWeightInfo.Weight = calcWeight
tempWeightInfo.LastConnectedTime=concInfo.LastConnectedTime
				resourceWeightInfo = append(resourceWeightInfo, tempWeightInfo)

added validation for concInfo object


Link seems broken in SOS page

The link https://go.microsoft.com/fwlink/?LinkID=67325 in the section TraverseHeap [-xml] <filename> redirects me to https://www.microsoft.com/en-us/download

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

ID: 8e01c075-7a07-5850-d462-706675b545f1
Version Independent ID: 0dd6c661-01a1-592c-ea53-8427412ff8d0
Content: SOS.dll (SOS Debugging Extension) - .NET Framework
Content Source: docs/framework/tools/sos-dll-sos-debugging-extension.md
Product: dotnet-framework
GitHub Login: @tdykstra
Microsoft Alias: tdykstra

Sorry, but the CLR profiler download is no longer available. I'm removing the link from the article.


Update testsubmit.py

Thanks for the suggestion Michelle, but that syntax error is deliberate. It's a test to make sure that if you submit a syntactically incorrect pascal program you get a compile error (outcome = 11) rather than a successful run (outcome = 15), as in the immediately preceding test. The two relevant lines of console output are:
Good Hello world Pascal test OK
Fail Hello world Pascal test OK

With your change in place, the second test fails.

Hi,
Thank's a lot.
One of our IT people told me that he was having trouble setting up a jobe server because of this line. I pass the information on to him.
Best regards
MC

OK. Note that that line relates to Pascal, which isn't a language that gets much use nowadays. If only one line in the test suite fails, and it's a test of a language you won't be using, you can safely ignore the failure.


fixed 404 in documentation

links were pointing to ./commandApp, however
the generated page is ./commandapp

Merged! Thank you for your contribution. Much appreciated! 👍


Resources for bots

Hi, please tell me.
If I understand correctly, now it is possible to launch several drivers.
How much to spend on their work RAM?
Now I use this approach. One bot, one container. But it uses 200 to 500 megabytes of RAM.

It is possible to launch multiple drivers . But if you want to launch multiple drivers , the amount of RAM you need will be dependent on the number of drivers launched . But as a baseline , I think a minimum of 4GB of RAM will be enough to get you started .


Allow to set spec.activeDeadlineSeconds

Hi,
we're using Kubedock in a multi-tenant cluster where quotas are used to restrict the resources that can be used by each tenant. There are different quota scopes based on the activeDeadlineSeconds property: short-lived pods (activeDeadlineSeconds > 0) consume resources from the "Terminating" quota while long-lived pods (activeDeadlineSeconds not set) consume resources from the "NotTerminating" quota. Currently Kubedock doesn't allow to specify the activeDeadlineSeconds property and this results in all the pods consuming resources from the "NotTerminating" quota even if the pod is short-lived (for example, used to run tests based on Testcontainers). We'd like to be able to set activeDeadlineSeconds; for example (much like pods request/limit) we could have a cmd line argument for setting the default value and we could use labels to override it.
If you think the feature is worth implementing I can try to put a PR together.
Thanks,
lorenzo

Hi,
Thanks for raising this. We have same requirement for terminating and non-terminating pods.
I think we can specify the activeDeadlineSeconds using YAML pod template. But I didn't test it.
Would be useful to have this on the command line.
Regards,

Sounds like something useful, feel free to open a pr. Note that you can probably already achieve your goal by using the pod template feature (--pod-template), but without the ability to override it via labels.

Created https://github.com/joyrex2001/kubedock/pull/71
Please bear with me, I haven't coded in Go for a while.
Thanks,
lorenzo

Hi @joyrex2001 , are there any upcoming releases? Thanks!

@lorenzobenvenuti I expect to release somewhere this or next week.

Ack, tyvm!

@lorenzobenvenuti 0.15.3 is just released.

Awesome, thanks a lot!


Increment version for identity releases

Increment package version after release of com.azure azure-identity

Closing this as it doesn't target master.


eigen error occurs when running apollo on arm64 ?

I'm running apollo 5.5 on arm64 platform. When velodyne driver run into here:

It will show error of eigen:

The code of the error occured is in modules/drivers/velodyne/compensator/compensator.cc here,two vector multiply:

How to solve this problem?

Create a small program just using eigen, run the same code piece, and figure out from there.

I'm running apollo 5.5 on arm64 platform. When velodyne driver run into here:

It will show error of eigen:

The code of the error occured is in modules/drivers/velodyne/compensator/compensator.cc here,two vector multiply:

How to solve this problem?

This problem was caused by eigen alignment requirement which Apollo r5.5.0 doesn't address well.
See http://eigen.tuxfamily.org/dox-devel/group__TopicUnalignedArrayAssert.html .
It was fixed in Apollo master as of master 3711be4317

closing now, please try the solution above


'get' of undefined thing

Help me to solve this
TypeError: Cannot read property 'get' of undefined

and this
const targetServer = client.guilds.cache.get(guildID)

and this
const targetServer = client.guilds.cache.get(guildID)

is the bot in the server you specified in the config ?

is the bot in the server you specified in the config ?


over is not exported

    var SockJS = require( 'sockjs-client' );
    var sock = new SockJS( SocketUri );
    var Stomp = require( 'stompjs' );
    return Stomp.over( sock );

so although this works my IDE (IntelliJ Idea) didn't think over was a method, and didn't see it documented on npmjs. It'd be nice to have over documented and exported so that  it's easier to find and use. I initially thought that the API had changed since version 0.3.

  exports.overTCP = overTCP;

  exports.overWS = overWS;

Are exported. I guess its to provide more explictness when handling a nodejs based client?

I want to use websocket with SockJs and Stomp client-side, and Java server-side, in a Spring-boot web application. I have installed with npm sockjs-client and stompjs. My client-side code is:
    var SockJS = require('sockjs-client');     var Stomp = require("stompjs");             var socket = new SockJS('/webSocketEndPoint');           stompClient = Stomp.over(socket);           stompClient.connect({}, function (frame) {           stompClient.subscribe('/topic/notification', function (notificationBody) {              alert(JSON.parse(notificationBody.body).content);           });         })
The methods over and subscribe are not working, so the websocket i want to build is not working. IntelliJ say me "Unresolved function or method over" and "Unresolved function or method subscribe ". I've included in my package.json stompjs and sockjs-client (correct version). The initial requires not makes me problem, but i'm not able to run this script..Someone can help me?! Thanks a lot

I'm using it without problems, this is an extract of the code:

const Stomp = require('webstomp-client')
const WebSocketClient = require('ws')
var ws = new WebSocketClient(stompEndpoint)
var stompClient = Stomp.over(ws, options)

Thanks, the problem was IntelliJ, now it's solved.

The problem was only IntelliJ..Now i have another problem: Stomp's over method works, but connect method is not working..
socket = new SockJS('/webSocketEndPoint');       stompClient = Stomp.over(socket);       console.log("************ inizio ************");       stompClient.connect({}, function (frame) {         console.log('Connected: ' + frame);         stompClient.subscribe('/topic/notification', function (notificationBody) {           showNotification(angular.fromJson(notificationBody.body).content);         });       });

This is not a support forum... Anyway you can find a real world usage example here:
https://github.com/melis-wallet/melis-api-js/blob/master/src/cm.js


Compatibility issue when container has height 100vh

If a container has min-height: 100vh.
Polyfill creates the following CSS variable --fgp-min-height which points to:
--fgp-min-height: var(--element-has-fgp) calc(100vh + var(--fgp-gap-row, 0%))

However 100vh + 0% can't be calculated, so the height is not applied.

Fixed by the latest release 5.0.0