Add QueuingContext for queue interactions

Context:
A refactor of the queuing system was proposed in the corresponding ADR to replace the poorly encapsulated queue interactions relying on qml._current_context.
Description of the Change:
An abstract base class QueuingContext oversees all queue interactions. Calls to _current_context._append_op and _current_context._remove_op where replaced with QueuingContext.append_operation and .remove_operation calls.
Due to this, the code for the OperationRecorder class simplified a lot and the underlying Recorder (basically a mock QNode) class is no longer necessary.
Benefits:
A clearer and more versatile QueuingInterface

I also tried to tackle issue #360 in this PR by removing the deletion and reinsertion of the observable in the measurement routines. But this caused the check that all observables have to be returned in order of creation to fail. But this will also be updated (and measure.py greatly simplified) when the other parts of the queuing ADR are being implemented.

Thanks @johannesjmeyer, that answers most of my questions. Happy for this to be merged in after @antalszava's had a chance to look it over.


[HOLD for payment 2024-06-06] [$250] [Search v1] Remove multiple API calls and clean up const

Problem
Clean up items from this PR

Remove multiple API calls made when changing policyID filter
Clean up const value

cc @WojtekBoman
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~014700a68531e38ed9
Upwork Job ID:<PHONE_NUMBER>139613696
Last Price Increase: 2024-05-15
Automatic offers:

ahmedGaber93 | Reviewer | 0

Issue OwnerCurrent Issue Owner: @mallenexpensify

Clean up items from https://github.com/Expensify/App/pull/41769
@luacmartins , I'm assuming this is a new job and @ahmedGaber93 should be compensated $250 as C+, let me know if that's not accurate. Thx

BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[x] [@ahmedGaber93] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.

Regression Test Proposal

Open the app
Go to Search tab from the bottom tab
Open the browser DevTools on Network monitor.
Click on switch-workspace button and switch current workspace
Verify that the /Search request is sent only once

https://github.com/Expensify/App/assets/41129870/10c4bb89-26a0-4998-bfca-fcde56378bc1
Do we agree 👍 or 👎

@ahmedGaber93 can you please accept the job and reply here once you have?
https://www.upwork.com/jobs/~014700a68531e38ed9
Thx for the test steps, added below

https://github.com/Expensify/Expensify/issues/404097

@mallenexpensify Offer accepted, thanks!

@mallenexpensify bump for payment.

Contributor+: @ahmedGaber93 paid $250 via Upwork.
Thx!


Feature Request: Multi-Lingual Support for Species' Common Names

Hello iNaturalist team,
I am writing to request a feature that I believe will enhance the user experience for multi-lingual individuals such as myself. I am a Slovak who often works with Latin species names in Norway and the dominant working language is often English.
At present, the iNaturalist app only displays the common name of a species in a single language. I find myself having to juggle different languages when trying to identify species, which can be quite challenging and confusing.
To help streamline this process, I propose a feature that allows displaying multiple common names of a species simultaneously. The user could be able to select their preferred languages from the settings, and then see the species' common names in all selected languages whenever they identify a species. This would essentially create a side-by-side comparison of the common names, aiding users in learning and memorizing species across languages.
This approach would significantly reduce the mental burden of switching between languages, and help users like me to consolidate our knowledge of species in different languages. Furthermore, this feature could potentially make the app more accessible and user-friendly for a wider international audience.
Thank you for considering this feature request. I strongly believe it would greatly enrich the iNaturalist app, and I look forward to hearing your thoughts on this suggestion.
Best regards,
Michal

Thanks for the suggestion, Michal. Please use the Forum to request new features, and check to see if someone has already requested what you want before starting a new topic (in this case, someone has).
In other news, we are working on a feature like this! It will launch on the website first, but we hope to figure out how to incorporate it into the apps once we work out the problems on the web.


Fix errors saving a 2D scene preview when the 2D editor was never opened

Continuation of #40163. Addressed https://github.com/godotengine/godot/issues/36456#issuecomment-662301553. Reasoning is detailed in https://github.com/godotengine/godot/pull/40163#issuecomment-664394995.
Couldn't properly test on master, as it crashes with unrelated Script Editor issues if you try to follow the reproduction steps. Works fine on 3.2 branch with the same changes applied, though.

No idea, why macOS Editor build fails. A fluke?

@pycbouh Reading the log, it seems the macOS build is failing due to caching: https://github.com/godotengine/godot/pull/40759/checks?check_run_id=914865814

@pycbouh Reading the log, it seems the macOS build is failing due to caching: https://github.com/godotengine/godot/pull/40759/checks?check_run_id=914865814

Yes, I mean it can be a fluke, because that doesn't seem to be related to the changes whatsoever. I don't see any other recent build failing due to this neither.

Thanks!

I hope we won't forget to cherrypick this without any labels 🙃

Cherry-picked for 3.2.3.


Updating to latest Selenium and Selenium support NuGetPackages raises Casting issue

Description
Updating to latest Selenium(v3.12.0) and selenium support (v3.12.0) NuGetPackages raises Casting issue
It was working fine till earlier version v3.11.2
Environment
Appium version 1.8.0
Desktop OS/version used to run Appium: Windows 10 Pro
Node.js version (unless using Appium.app|exe): 8.10.0
Mobile platform/version under test: Android API 25 ,v7.1.1
Real device or emulator/simulator: Real Device Samsung Tab
Appium CLI or Appium.app|exe: both
IDE: VisualStudio 2017 Enterprise and C# as coding language
Selenium Driver and Selenium support driver : v3.12.0 (Issue creating version)
Selenium Driver and Selenium support driver v3.11.2 worked fine without any casting issues
Code To Reproduce Issue [ Good To Have ]
public static AndroidElement UserName_Field()
    {
        AndroidElement UserName = driver.FindElement(By.Id("*:id/LoginView_txtUsername"));
        return UserName;
    }

Ecxeption stacktraces
Test Name:	TestMethod1
Test FullName:	UnitTestProject1.UnitTest1.TestMethod1
Test Source:	C:\Users\gokulnath.kumar\source\repos\UnitTestProject1\UnitTestProject1\UnitTest1.cs : line 25
Test Outcome:	Failed
Test Duration:	0:00:53.4154213
Result StackTrace:
at OpenQA.Selenium.Appium.AppiumDriver`1.FindElement(By by)
at *_Mobile.Page_Objects.Login_Objects.UserName_Field() in C:\Users\gokulnath.kumar\source\repos\UnitTestProject1\UnitTestProject1\Page_Objects\Login_Objects.cs:line 21
at *_Mobile.Log_in_module.Login_module.Login(String Uname, String Pwd) in C:\Users\gokulnath.kumar\source\repos\UnitTestProject1\UnitTestProject1\App_Modules\Login_module.cs:line 18
at UnitTestProject1.UnitTest1.TestMethod1() in C:\Users\gokulnath.kumar\source\repos\UnitTestProject1\UnitTestProject1\UnitTest1.cs:line 27
Result Message:
Test method UnitTestProject1.UnitTest1.TestMethod1 threw exception:
System.InvalidCastException: Unable to cast object of type 'OpenQA.Selenium.Remote.RemoteWebElement' to type 'OpenQA.Selenium.Appium.Android.AndroidElement'.
Link to Appium logs
https://gist.github.com/Gocoollnath/c6b4be5ababf838a0acf0adb72552a20

For some reason, when you have the last version of the Selenium WebDriver and Selenium Support installed with Appium in your NuGet Packages your project will crash.
So, my suggestion is: uninstall the Selenium leaving only the Appium.
Or: downgrade the Selenium version (if you need to use Selenium anyway).

https://github.com/SeleniumHQ/selenium/issues/6045 . It's confirmed that how RemoteWebDriver works have been changed based on request in latest Selenium driver versions. Can the update be also made to Appium? @jlipps @TikhomirovSergey @mykola-mokhnach .Please, can you provide an update when this change be incorporated in Appium too?

#230 I've been running into these invalid casts for a while too!

Okay wontfix... so what's the workaround?

Apologies all, install the latest beta version

Thanks. Selenium changed some method signatures and switched DesiredCapabilities to some new interface. Is there documentation on how the beta version handles these changes?

Not yet but AppiumOptions.cs is the replacement class for now.

Cool thank you very much!

Did anyone figure out the new usage of the AppiumOptions will look? Does anyone have a code sample? Thanks

@nikolay-advolodkin I believe this is only available from the nuget package beta3?

@akinsolb which pare is only Nuget?
I did: Install-Package Appium.WebDriver -Version <IP_ADDRESS>-beta
https://screencast.com/t/RCw4nx8qMT

@nikolay-advolodkin That is correct. With this package version, you should not be receiving 'Unable to cast object of type'. If you are, can you upload a gist of your stacktrace

Here's the stacktrace @akinsolb  - https://gist.github.com/nikolay-advolodkin/f0cc583d44cfbd95078431c384d65354

@nikolay-advolodkin The latest and beta release supports up to Selenium v3.14. Your screenshot shows you have 3.14.1. Please raise a new issue using the issue template.

@nikolay-advolodkin The latest and beta release supports up to Selenium v3.14. Your screenshot shows you have 3.14.1. Please raise a new issue using the issue template.

You're right, that was the problem

Hi,
In appiumoptions.additionalcapability how do u set the current working directory?


Add e2e tests check for available Envoys and Contours

This patch adds check for available envoys and contours during e2e
test.
Fix https://github.com/projectcontour/contour-operator/issues/271
Signed-off-by: Kenjiro Nakayama<EMAIL_ADDRESS>/cc  @danehans @sunjayBhatia

@nak3 can you please rebase when you have a moment?

Sure, rebased.
Test failed but I think https://github.com/projectcontour/contour-operator/pull/304 will fix it.


Support for Embree

Requirements

That Embree be included as a backend by default if available on the system
That Vulkan likewise be included as a backend by default if available on the system
That if Embree is included as a backend, we fall back to Embree on systems without dedicated graphics cards at application runtime

This will require some changes be made to GPRT’s backend, likely that all C calls redirect to a structure derived from a common interface. A particular backend could be selected by the user via gprtContextCreate.
We would also need to refactor the GPRTProgram handle to support multiple different device codes from multiple different platforms. I believe this should be doable if we transform the GPRTProgram into a structure which is included in the main host code through an extern declaration. That GPRTProgram structure would in-turn have an extern GPRTEmbreeProgram declaration and a GPRTVulkanProgram declaration, which are defined to some default NULL value if a particular backend isn’t included.

With this design, we could also include a DXR or OptiX backend down the road, while also avoiding preference for any particular vendor.


Adding afterClick option to LaunchLink to allow for parent element to…

… determine if launched in webtop
This change is necessary to allow for HUD to report different metrics based on whether or not the link is launched in webtop or in a new tab. That state is determined by the underlying component, so I created a callback that will be passed the state of whether or not it is launched in webtop.

:+1:

:+1:


feat(breadcrumb): core breadcrumb component

Carrying over the external contribution (#5876) so we can do a final fit and finish and merge.
Co-authored by @derkoe from Porsche Informatic. 🎉
I will clean up the commit message when we are ready for the final squash/rebase.
PR Checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[ ] If applicable, have a visual design approval

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] clarity.design website / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

@jeeyun : this looks like we are good to merge. Any chance we could merge it for the next release?

Yes! I realized forgot to add a react wrapper for this. Let me add that to the PR today and get it reviewed in time for next release?

Great to see it finished!
Thanks @derkoe, @jeeyun & clarity team for the good collaboration!!!

Thanks @d-m-s and @derkoe !


Home Assistant forces zwave probe to wake up interval 1 second

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.46.1
Python release (python3 --version):
3.4.2
Component/platform:
Zwave
Description of problem:
I have a Fibaro Motion Sensor that was included just fine in HA 0.45. Since upgrading to 0.46.1 HA forces the wake up interval to 1 second and the motion sensor becomes unresponsive. I have tried to exclude, include and even reset and include the sensor. Every time HA forces the wake up interval to 1 second.
Expected:
The interval should not change from default 7200 seconds upon inclusion.
Problem-relevant configuration.yaml entries and steps to reproduce:

Include node
Node changes wake up interval from 7200 seconds (default) to 1 second without me doing anything.

Traceback (if applicable):

Additional info:

I can confirm I have had the same issue with 5 of the same sensor.  It seems to work fine on the older version but the z-wave plus version keeps resetting to 1 sec wake-up.  It is a major drag and kills batteries!

You should check the OZW. Log to see if it is really set. I have a aeotec recessed door sensor that do have a default of 320 but is always reported as 0.

Yes it is really set to 1 sec. I have done this multiple times to verify. Doesn't happen to my Sensative strips which is also battery powered. Just the Fibaro Motion Sensor.

Then there are two clues for you to look for in the logs:
In homeassitant.log you should see a service call for set_wakeup.2017-06-21 20:07:56 INFO (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: service_data=node_id=12, value=250, service_call_id=139688674316696-296, service=set_wakeup, domain=zwave>  Please paste this line and the 10 before and after that line.
In OZW.log you should see a line with the same timestamp as in the homeasssitant.log and it should be like: 2017-06-21 20:07:56.911 Info, Node012, Value::Set - COMMAND_CLASS_WAKE_UP - Wake-up Interval - 0 - 1 - 250 Please paste in the 20-30 lines or so before and after that line.

Hi, nothing of that kind in homeassistant.log
It only contains warnings. Only thing regarding Zwave is slow start (as always):
2017-06-22 16:19:45 WARNING (MainThread) [homeassistant.setup] Setup of automation is taking over 10 seconds.
2017-06-22 16:19:45 WARNING (MainThread) [homeassistant.setup] Setup of sensor is taking over 10 seconds.
2017-06-22 16:19:46 WARNING (MainThread) [homeassistant.components.sensor] Setup of platform template is taking over 10 seconds.
2017-06-22 16:19:46 WARNING (MainThread) [homeassistant.setup] Setup of media_player is taking over 10 seconds.
2017-06-22 16:19:46 WARNING (MainThread) [homeassistant.setup] Setup of device_tracker is taking over 10 seconds.
2017-06-22 16:19:48 WARNING (MainThread) [homeassistant.components.sensor] Setup of platform fastdotcom is taking over 10 seconds.
2017-06-22 16:19:48 WARNING (MainThread) [homeassistant.components.media_player] Setup of platform cast is taking over 10 seconds.
2017-06-22 16:20:31 WARNING (Thread-4) [homeassistant.components.zwave] zwave not ready after 30 seconds, continuing anyway
In OZW_log there is this regarding IntervalSet, directly after inclusion without me doing anything:
2017-06-22 16:24:17.617 Info, Node012, Processing (Query) Nonce Request message (Callback ID=0x93, Expected Reply=0x04)
2017-06-22 16:24:17.617 Info, Node012, Sending (Query) message (Callback ID=0x93, Expected Reply=0x04) - Nonce_Get(WakeUpCmd_IntervalGet) - 0x01, 0x09, 0x00, 0x13, 0x0c, 0x02, 0x98, 0x40, 0x05, 0x02:
2017-06-22 16:24:17.623 Detail, Node012,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-06-22 16:24:17.623 Detail, Node012,   ZW_SEND_DATA delivered to Z-Wave stack
2017-06-22 16:24:17.637 Detail, Node012,   Received: 0x01, 0x07, 0x00, 0x13, 0x02, 0x00, 0x00, 0x02, 0xeb
2017-06-22 16:24:17.638 Detail, Node012,   ZW_SEND_DATA Request with callback ID 0x02 received (expected 0x02)
2017-06-22 16:24:17.638 Info, Node012, Request RTT 20 Average Request RTT 33
2017-06-22 16:24:17.650 Detail, Node012,   Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x0c, 0x0a, 0x98, 0x80, 0x74, 0x19, 0xf3, 0x37, 0x2f, 0x6e, 0x18, 0xc1, 0xc4
2017-06-22 16:24:17.650 Info, Node012, Received SecurityCmd_NonceReport from node 12
2017-06-22 16:24:17.650 Info, Node012, Sending (Query) message (Callback ID=0x94, Expected Reply=0x04) - WakeUpCmd_IntervalGet (Node=12): 0x01, 0x09, 0x00, 0x13, 0x0c, 0x02, 0x84, 0x05, 0x25, 0x94, 0xdb
2017-06-22 16:24:17.658 Detail, Node012,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-06-22 16:24:17.659 Detail, Node012,   ZW_SEND_DATA delivered to Z-Wave stack
2017-06-22 16:24:17.675 Detail, Node012,   Received: 0x01, 0x07, 0x00, 0x13, 0x94, 0x00, 0x00, 0x02, 0x7d
2017-06-22 16:24:17.675 Detail, Node012,   ZW_SEND_DATA Request with callback ID 0x94 received (expected 0x94)
2017-06-22 16:24:17.675 Info, Node012, Request RTT 58 Average Request RTT 45
2017-06-22 16:24:17.675 Detail,   Expected callbackId was received
2017-06-22 16:24:17.688 Detail, Node012,   Received: 0x01, 0x08, 0x00, 0x04, 0x00, 0x0c, 0x02, 0x98, 0x40, 0x25
2017-06-22 16:24:17.688 Info, Node012, Received SecurityCmd_NonceGet from node 12
2017-06-22 16:24:17.688 Info, NONCES: 0xe3, 0x13, 0xa6, 0x3f, 0xa1, 0x3a, 0xb3, 0x51
2017-06-22 16:24:17.688 Info, NONCES: 0x48, 0x8b, 0xb8, 0x1c, 0x78, 0x97, 0xf1, 0x73
2017-06-22 16:24:17.688 Info, NONCES: 0xad, 0x7b, 0x7b, 0x4e, 0xb6, 0x2e, 0x9f, 0x0a
2017-06-22 16:24:17.688 Info, NONCES: 0xbb, 0x54, 0xbd, 0x33, 0xeb, 0xaf, 0xa7, 0x41
2017-06-22 16:24:17.688 Info, NONCES: 0xfc, 0x00, 0xd3, 0x54, 0x30, 0x6f, 0xf5, 0xeb
2017-06-22 16:24:17.688 Info, NONCES: 0x80, 0x93, 0x29, 0x46, 0xdd, 0x7e, 0x76, 0xd9
2017-06-22 16:24:17.689 Info, NONCES: 0x53, 0xee, 0xe8, 0x9f, 0xd6, 0xd1, 0x7e, 0x55
2017-06-22 16:24:17.689 Info, NONCES: 0x5d, 0x49, 0x54, 0x17, 0x6d, 0xef, 0x95, 0x43
2017-06-22 16:24:17.689 Info, Node012, Sending (Query) message (Callback ID=0x01, Expected Reply=0x04) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x0c, 0x0a, 0x98, 0x80, 0x5d, 0x49, 0x54, 0x17, 0x6d, 0xef, 0x95, 0x43, 0x05, 0x01, 0xe4:
2017-06-22 16:24:17.695 Detail, Node012,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-06-22 16:24:17.695 Detail, Node012,   ZW_SEND_DATA delivered to Z-Wave stack
2017-06-22 16:24:17.711 Detail, Node012,   Received: 0x01, 0x07, 0x00, 0x13, 0x01, 0x00, 0x00, 0x01, 0xeb
2017-06-22 16:24:17.711 Detail, Node012,   ZW_SEND_DATA Request with callback ID 0x01 received (expected 0x01)
2017-06-22 16:24:17.711 Info, Node012, Request RTT 94 Average Request RTT 69
2017-06-22 16:24:17.729 Detail, Node012,   Received: 0x01, 0x20, 0x00, 0x04, 0x00, 0x0c, 0x1a, 0x98, 0x81, 0x12, 0x3c, 0xc5, 0xc4, 0xc2, 0xe4, 0x02, 0x73, 0xf3, 0x55, 0x59, 0xee, 0x3d, 0xc6, 0x08, 0x5d, 0xf0, 0x5b, 0xa0, 0x64, 0xe2, 0x25, 0x45, 0x6a, 0x94
2017-06-22 16:24:17.730 Info, Raw: 0x98, 0x81, 0x12, 0x3c, 0xc5, 0xc4, 0xc2, 0xe4, 0x02, 0x73, 0xf3, 0x55, 0x59, 0xee, 0x3d, 0xc6, 0x08, 0x5d, 0xf0, 0x5b, 0xa0, 0x64, 0xe2, 0x25, 0x45, 0x6a, 0x94
2017-06-22 16:24:17.730 Detail, Node012, Decrypted Packet: 0x00, 0x84, 0x06, 0x00, 0x1c, 0x20, 0xff
2017-06-22 16:24:17.730 Detail,
2017-06-22 16:24:17.730 Info, Node012, Response RTT 112 Average Response RTT 100
2017-06-22 16:24:17.730 Info, Node012, Received Wakeup Interval report from node 12: Interval=7200, Target Node=255
2017-06-22 16:24:17.730 Detail, Node012, Initial read of value
2017-06-22 16:24:17.730 Detail, Node012, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_WAKE_UP
2017-06-22 16:24:17.730 Detail, Node012, Queuing (WakeUp) WakeUpCmd_IntervalSet (Node=12): 0x01, 0x0d, 0x00, 0x13, 0x0c, 0x06, 0x84, 0x04, 0x00, 0x1c, 0x20, 0x01, 0x25, 0x95, 0xe6
2017-06-22 16:24:17.730 Detail, Node012,   Expected reply and command class was received
2017-06-22 16:24:17.730 Detail, Node012,   Message transaction complete
2017-06-22 16:24:17.731 Detail,
2017-06-22 16:24:17.731 Detail, Node012, Removing current message
2017-06-22 16:24:17.731 Detail, Node012, Notification: ValueChanged
2017-06-22 16:24:17.753 Detail,
2017-06-22 16:24:17.753 Info, Node012, Processing (WakeUp) Nonce Request message (Callback ID=0x95, Expected Reply=0x13)
2017-06-22 16:24:17.753 Info, Node012, Sending (WakeUp) message (Callback ID=0x95, Expected Reply=0x13) - Nonce_Get(WakeUpCmd_IntervalSet) - 0x01, 0x09, 0x00, 0x13, 0x0c, 0x02, 0x98, 0x40, 0x05, 0x02:
2017-06-22 16:24:17.759 Detail, Node012,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-06-22 16:24:17.759 Detail, Node012,   ZW_SEND_DATA delivered to Z-Wave stack
2017-06-22 16:24:17.774 Detail, Node012,   Received: 0x01, 0x07, 0x00, 0x13, 0x02, 0x00, 0x00, 0x02, 0xeb
2017-06-22 16:24:17.774 Detail, Node012,   ZW_SEND_DATA Request with callback ID 0x02 received (expected 0x02)
2017-06-22 16:24:17.774 Info, Node012, Request RTT 20 Average Request RTT 44
2017-06-22 16:24:17.786 Detail, Node012,   Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x0c, 0x0a, 0x98, 0x80, 0x49, 0xc0, 0x3b, 0x0c, 0x55, 0x92, 0x45, 0x61, 0xa8
2017-06-22 16:24:17.786 Info, Node012, Received SecurityCmd_NonceReport from node 12
2017-06-22 16:24:17.786 Info, Node012, Sending (WakeUp) message (Callback ID=0x96, Expected Reply=0x13) - WakeUpCmd_IntervalSet (Node=12): 0x01, 0x0d, 0x00, 0x13, 0x0c, 0x06, 0x84, 0x04, 0x00, 0x1c, 0x20, 0x01, 0x25, 0x96, 0xe5
2017-06-22 16:24:17.795 Detail, Node012,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-06-22 16:24:17.795 Detail, Node012,   ZW_SEND_DATA delivered to Z-Wave stack
2017-06-22 16:24:17.797 Detail, Node012,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-06-22 16:24:17.797 Detail, Node012,   ZW_SEND_DATA delivered to Z-Wave stack
2017-06-22 16:24:17.812 Detail, Node012,   Received: 0x01, 0x07, 0x00, 0x13, 0x96, 0x00, 0x00, 0x02, 0x7f
2017-06-22 16:24:17.812 Detail, Node012,   ZW_SEND_DATA Request with callback ID 0x96 received (expected 0x96)
2017-06-22 16:24:17.812 Info, Node012, Request RTT 58 Average Request RTT 51
2017-06-22 16:24:17.812 Detail,   Expected callbackId was received
2017-06-22 16:24:17.812 Detail,   Expected reply was received
2017-06-22 16:24:17.812 Detail,   Message transaction complete
2017-06-22 16:24:17.812 Detail,
2017-06-22 16:24:17.812 Detail, Node012, Removing current message
2017-06-22 16:24:17.813 Detail, Node012, Query Stage Complete (Session)
2017-06-22 16:24:17.813 Detail, Node012, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Dynamic live=1
2017-06-22 16:24:17.813 Detail, Node012, QueryStage_Dynamic
2017-06-22 16:24:17.813 Detail, Node012, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_BASIC
2017-06-22 16:24:17.813 Detail, Node012, Queuing (Send) BasicCmd_Get (Node=12): 0x01, 0x09, 0x00, 0x13, 0x0c, 0x02, 0x20, 0x02, 0x25, 0x97, 0x7b
2017-06-22 16:24:17.813 Detail, Node012, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_SENSOR_BINARY
2017-06-22 16:24:17.813 Detail, Node012, Queuing (Send) SensorBinaryCmd_Get (Node=12): 0x01, 0x09, 0x00, 0x13, 0x0c, 0x02, 0x30, 0x02, 0x25, 0x98, 0x64
The sensor is reporting lux and temp values almost every second until it just dies after a couple of minutes and is unresponsive until I reset it.
I hope this is some sort of help, even if it's not exactly what you asked for.
Best regards,
Andreas

Is this being worked on or can we provide anything to you to help make it easier?  I am still having the same issue with 2 sensors and like @andreaswulff  do not have the log entries you are looking for.
Thanks in advance,  Greg

Well, I do not have any good tips about this. As it is happening in the inclusion process HA does not control that, we only issue the command to start the process. Only thing I can think of is if you use a bundled HA version like docker or AIO that  provides a fixed version of OZW and a change in OZW or PYOZW introduces this. Also that it only happens on the fibaro device. I would have understood if you had a service call log line in HA log. Does the device change the wakeup interval if you change it in HA? (Set wakeup interval and then manually wakeup the device per instructions )

Actually it happens after inclusion also, if i include using ozwcp and later launch HA. Working fine in ozwcp and changera when HA is launched. I used latest Hassbian which I later upgraded to 0.46.1 (not working) and then 0.47.1 (still not working). Trying to change wake up interval in HA does nothing.

This is still a problem on a new rpi3 with a fresh install of HA with AIO installer today. Using a different Razberry card also. Same Fibaro sensor though.

Yeah, it works now. Don’t know why though.

Updated every time a new version came out.


Onnx links in model zoo are broken

Tried every link, they all lead to error.

Thank you for pointing out the problem. The onnx links have been corrected.

thank you


Testing

TEST WORKFLOW

wrong repo bruh

@all-contributors add @all-contributors to the doc

@all-contributors add https://github.com/all-contributors to the doc

@all-contributors add @sc0rp10n-py to the doc

@all-contributors please add @sc0rp10n-py for docs

@all-contributors add @all-contributors to the doc

bruh looks like @allcontributers is broken

Reference in

Nah, I messed something up... I fixed all the issues yesterday night.


License

@andersesbensen
Hello,
I would like to ask you. There is no license in the code or in the repository, so this code and its parts are free to use yes?
Our research team is working on the detection of threats and anomalies in IoT Networks.  I want to use this code as collector of Z-Wave traffic. I also tried waving_z, EZ-Wave with scapy-radio but this rtl-zwave works best.
Thanks!

Hello sorry for the late reply. Yes feel free to use this code. I would appreciate if you mention the origin of the code in any publications you may create.
Best regards
Anders
/Anders

Den 25. mar. 2019 kl. 14.57 skrev jozhalaj<EMAIL_ADDRESS>@andersesbensen
Hello,
I would like to ask you. There is no license in the code or in the repository, so this code and its parts are free to use yes?
Our research team is working on the detection of threats and anomalies in IoT Networks. I want to use this code as collector of Z-Wave traffic. I also tried waving_z, EZ-Wave with scapy-radio but this rtl-zwave works best.
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Ok, as you wish.
Thank You
JH


Package Black Box terminal

Description of changes
Added the Black Box terminal as blackbox-terminal.
Added the Marble library, a dependency of Black Box, as libmarble.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

This effort is partially based on the previous flake-based packaging effort by @mitchmindtree, which is GPL-licensed. However, they have graciously provided permission to reuse the code in Nixpkgs in an email conversation.

Reopened with proper meta at #188609


fix: add "in" rule in default number rules (#44)

🔗 Linked issue
#44
❓ Type of change

[X] 🐞 Bug fix (a non-breaking change that fixes an issue)

📚 Description
Resolves #44 and add inRulein default number rules as asked in #53

[X] I have linked an issue or discussion.
[X] I have updated the documentation accordingly. (not in this PR, but on the PR I did for vinejs.dev)

Thanks!


Update Composer dependencies (2022-06-10-00-11)

Visual regression test passed!
View the visual regression test report


Add Observations for send/receive

This adds observations to PulsarTemplate and DefaultPulsarMessageListenerContainer.
Remaining items (follow on PRs)

[x] auto-generate docs and plug-in to newly added observability section in ref guide
[x] ~add properties and hook into our Spring Boot starter where it makes sense~ (#147)

Big thanks to @artembilan and @garyrussell for trailblazing this in spring-kafka as this was my reference model for this proposal.
@marcingrzejszczak @jonatan-ivanov if either of you get a chance to give this a once-over that would be great. However, I know that treatment was applied to spring-kafka and as stated above, this was modeled from that. I am fairly certain there will be no surprises here.

I went ahead and added the auto-generated docs as a 2nd commit in this PR. Looks good...

Do you check them in SI  ?

I do at the moment. Plus I also added a condition to not run that Gradle task on CI.
My point was that this doc eventually going to be "very static" when the code base will have settled.
Although I'll debate with myself if this really has to be deferred to the docs creation phase instead.

Do you check them in SI  ?

I do at the moment. Plus I also added a condition to not run that Gradle task on CI. My point was that this doc eventually going to be "very static" when the code base will have settled.
Although I'll debate with myself if this really has to be deferred to the docs creation phase instead.

That would be a true optimization (dont' run during build if its 99% static content). However, if the tool picks up changes (would not happen automatically unless version was set to latest or snaphot though) we would not see those w/o manually running. Also, people may forget to run the docs generator when something changes. They would have to know what those change-worthy things are.

Did you see Checkstyle failures:

Yeh I did. I am going to squash/rebase a bit and will address then.

Error: eckstyle] [ERROR] /home/runner/work/spring-pulsar/spring-pulsar/spring-pulsar/src/main/java/org/springframework/pulsar/observation/PulsarMessageSenderContext.java:74:9: Class MessageHolder should be declared as final. [FinalClass]


Added omitNew option to toJSON, it excludes relations that return true to .isNew()

This closes #753.

I'm not sure this is the intended behaviour. I'm removing relations if they're new, but maybe I should just return null instead of removing them from the relations object.

@rhys-vdw, what do you think should be the intended behaviour?

Ok, this PR is in better shape now; one thing to address is if a isNew == true relation should be completely removed from the serialized object or just left with null as it's value:
Having
model = new bookshelf.Model({id: 1, name: 'Test'});
model.relations = { rel: new bookshelf.Model({attr: 'Test'}) };

Should model.serialize({omitNew: true}) be
{
  id: 1,
  name: 'Test'
}

or
{
  id: 1,
  name: 'Test',
  rel: null
}

came to the realization that the relation shall be absent from the JSON if its new.

@vellotis, that's the current behaviour. This should be good to go then?

Good work! The final result is pretty decent. :+1:


Create Branch per solution

Each solution should have its own branch and the main branch should reflect the location of each solution.

Resolved with #23

Resolved with #23


azk start command verbose

Verbose level 2 will show command output:

This closes #482

LGTM! Very helpful!

LGTM!


Use 4:3 resolution for Nest Hello

Nest Hello native resolution is 4:3 but the current plugin stretches the image to 16:9. Is it possible to maintain the 4:3 resolution within HomeKit?

@schmittx - I'm sure I probably broke something in a way I do not yet understand (I need to find a list of supported Homekit resolutions), but I was able to get the Nest Hello to show as a 4:3 video feed when viewed in the Home app. I only have the one camera, so I do not need to support a mixture of 16:9 and 4:3 feeds which would probably require a lot more code changes.
Home App =

Nest App =

In the local copy of nestcam.js in my C:\Users\muzzymate\AppData\Roaming\npm\node_modules\homebridge-nest-cam\lib, lines 45-51, I replaced the contents with the below list to maintain the 4:3 aspect ratio. I then restarted the Homebridge instance running homebridge-nest-cam and now the Nest Hello's video stream is 4:3.
  [320, 240, 30],
  [480, 360, 30],
  [640, 480, 30],
  [1280, 960, 30],
  [1600, 1200, 30]

@muzzymate Glad to hear you got 4:3 working. Thanks for the settings, I'll give these a shot and see how it works for me. I have both a Hello and an Indoor IQ, so I'll probably try adding some method to change the resolution for each camera (if possible).

I’m having the same problem, but I installed everything over an Homebridge iOS app(I’m not so tech-savvy) on my pi3. This app only lets me change the config.json and has a (linux)terminal. Is there any way for me to adjust the resolutions(16:9->4:3) manually? If not, an implementation of some 4:3 resolutions for the nest hello in the next update would be awesome :)

My Pi3 only sees the nest cams as motion sensors. What did you do to make them work as cameras?
Thanks!

On Sep 20, 2019, at 10:53 AM, karmin0<EMAIL_ADDRESS>wrote:

I’m having the same problem, but I installed everything over an Homebridge iOS app(I’m not so tech-savvy) on my pi3. This app only lets me change the config.json and has a (linux)terminal. Is there any way for me to adjust the resolutions(16:9->4:3) manually? If not, an implementation of some 4:3 resolutions for the nest hello in the next update would be awesome :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@pipdog05 I just followed the instructions and it worked so...idk really if i can help you out. For installing FFmpeg i used these instructions:
https://github.com/legotheboss/YouTube-files/wiki/(RPi)-Compile-FFmpeg-with-the-OpenMAX-H.264-GPU-acceleration

@muzzymate I worked on this a bit and figured out a solution that sets resolution based on camera type, check our #75.

Nice job @schmittx! I only have a Nest Hello but will try and merge in your code changes with my local instance soon.

Does anyone know how to go about setting it back to 4:3 if you are running homebridge via MacOS? Is there a line I can add to my config.json file?


Make download information more compact

Is it possible to make the download information more compact? How about update the status in the same line instead of printing many lines?

@dclong In the first case (files downloaded by a bootstrap), the "Downloaded X missing file(s)" messages should be printed on the same line when ANSI output is enabled. It's only disabled in a limited number of cases.

Same for the second case. When ANSI output is enabled, you get progress bars just like the GIF on the coursier website frontpage.

Is there an option to force enabling ANSI output?


fix for bootstrap.sh 401 issue: https://github.com/awslabs/amazon-eks…

…-ami/issues/594
Issue #, if available: 594
Description of changes:
Add retries to getting an aws metadata service token and for obtaining the metadata.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thanks for the PR! What tests did you run to confirm your changes?

Thanks for the PR! What tests did you run to confirm your changes?

Thanks for the PR! What tests did you run to confirm your changes?

I built EKS clusters using the modified version by passing the modified version as part of the userdata, placing it in /etc/eks/bootstrap-v2.sh and then had my main userdata script invoke that instead of the original /etc/eks/bootstrap.sh.
The only conditional part in the script that was modified is around whether 'DNS_CLUSTER_IP' is supplied or not, and this was also tested.
Also the lines:
      local lines=$(echo "$metadata_result" | wc -l)
      echo "$metadata_result" | head -n $(( lines - 1 ))

could actually be changed to
      echo "$metadata_result" | head -n -1

but I opted for the former as head may not support negative indexes in all the main distros and I am not sure where this script ends up.

Thanks for the PR! What tests did you run to confirm your changes?

I built EKS clusters using the modified version by passing the modified version as part of the userdata, placing it in /etc/eks/bootstrap-v2.sh and then had my main userdata script invoke that instead of the original /etc/eks/bootstrap.sh.
The only conditional part in the script that was modified is around whether 'DNS_CLUSTER_IP' is supplied or not, and this was also tested.
Also the lines:
      local lines=$(echo "$metadata_result" | wc -l)
      echo "$metadata_result" | head -n $(( lines - 1 ))

could actually be changed to
      echo "$metadata_result" | head -n -1

but I opted for the former as head may not support negative indexes in all the main distros and I am not sure where this script ends up.


emptydir: look for (nearly) empty directories and delete them

🚀 Deployed on https://667977bf120fcabf6e0c8ba1--alexwlchan.netlify.app


Division by zero on smart crop

I'm getting a float division by zero error here:
sorl/thumbnail/engines/pil_engine.py in _get_image_entropy, line 239

I'm calling it using:
{% thumbnail comment.user.profile.avatar_image "30x30" crop="smart" as im %}

This happens on some images and not others. The image that's causing me issues is this one:
https://www.dropbox.com/s/m5e79cvk53ujs7b/Chelsea_physic_garden.jpg?dl=0
From a brief bit of digging the code is:
def _get_image_entropy(self, image):
    """calculate the entropy of an image"""
    hist = image.histogram()
    hist_size = sum(hist)
    print hist_size
    hist = [float(h) / hist_size for h in hist]
    return -sum([p * math.log(p, 2) for p in hist if p != 0])

print hist_size gives a zero in the console - hence the error. We need some sort of try/except on this calculation, but I'm not sure what the except should be!

Should have said I'm using sorl-thumbnail==11.12.1b

Have the same bug

Same bug is reproduced when calling get_thumbnail from sorl.thumbnail even when crop='center' is used

Try with pillow==3.1.0. See #429.

@lampslave Thanks. Solves the issue.


Update: tailscale.tailscale version 1.8.5

Removing old versions to reduce clutter
Microsoft Reviewers: Open in CodeFlow

/azp run


Mark functions that take the address of a global function as host…

…-only.
clang is about to get pickier about disallowing references to things
from host+device code when it won't work on either host or device.
clang doesn't currently support launching kernels from the device side,
thus these __host__ __device__ functions that take a function pointer to
__global__ functions are no good.
It doesn't look like Thrust tries to use nested kernels, so the
__device__ attribute appears unnecessary here.  But if you like we could
make these functions __host__ __device__ for compilers other than clang.

cc @Artem-B

Thanks Justin. This won't quite work for us because Thrust does actually launch kernels from __device__ functions :-) It's possible to use nested Thrust algorithms when the compiler generates relocatable device code and the SM arch is >= sm_35.
I think what we ought to do to make this work for Clang is to retain the annotations of these functions but also guard these places where the address of a __global__ function is taken with a preprocessor macro. I think nvcc already defines a preprocessor symbol that indicates whether kernel launches are enabled for __device__ functions. Basically this macro (whose name I can't recall at the moment) indicates whether "Dynamic Parallelism" is available.
Does Clang also provide this macro?

This won't quite work for us because Thrust does actually launch kernels from device functions :-)

Interesting, I would have expected this not to compile with clang either, then.  (We are building with sm_35.)
In any case, let's figure out that macro, if it exists.  I don't see it in the nvcc docs [1], and I can't figure out how to print all #defines from nvcc [2].  Any other ideas?
[1] http://docs.nvidia.com/cuda/cuda-compiler-driver-nvcc/
[2] With clang, it's -E -x clang -dM /dev/null

nvcc defines CUDACC_RDC macro in a separable compilation mode (-rdc=true). Together with CUDA_ARCH >= 350, it indicates that  device-side kernel launches are permitted.
Thrust has unit tests that check device-side launches [1]. Device-side launches will be used only with -rdc=true -arch=sm_35 (or higher).
A macro like this [2] can be used to annotate a function. If device-side launches are supported,  it will annotate a function with host device, otheriwse it will be just host
[1] https://github.com/thrust/thrust/blob/master/testing/backend/cuda/for_each.cu#L63
[2] https://github.com/NVlabs/cub/blob/1.5.2/cub/util_arch.cuh#L58

Thanks Evghenii.
I will probably be less disruptive on the overall code to change the annotations (I'm worried that will lead to attempting to call a __host__ function from a __host__ __device__ function, for example). So I think all we need to do is to guard taking the address with something like #if __CUDACC_RDC__. The #else branch can just return 0.

I will probably be less disruptive on the overall code to retain the annotations (I'm worried that will lead to attempting to call a host function from a host device function, for example). So I think all we need to do is to guard taking the address with something like #if defined(CUDACC_RDC). The #else branch can just return 0.

WFM, updated the patch.

Sorry, I should have waited for Evghenii's review before merging this.
@jlebar: Could you resubmit a PR with the corrected guard?

https://github.com/thrust/thrust/pull/835


Shade dependencies using shadow jar plugin

Obviously for discussion, but I figured to leave a sample here. Feel free to close, if this misses something 😀

This was merged as part of another PR

LGTM - This was merged as part of another PR 👍


fix: wait for quicklink to be processed before adding more

Since adding a link involves fetching the metadata, the current validation was not effective considering that we're calling an async function.
I tried debouncing and this but this feels better... maybe when the quicklink is a slow website it might not be so nice.
Any ideas? Maybe using a different data structure could also work?

Is it ok that the fetching occurs multiple times? Like whenever a new item is added, the whole fetch process happens again.

That's probably okay. Those fetches are pretty cheap

Does anything else need to be done for this PR?


review changes

See if there is anything in here we can add to the base theme.

Some slick slider stuff:

https://github.com/gios-asu/sustainability-solutions-wordpress-theme/blob/master/stylesheets/scss/_slick.scss
https://github.com/gios-asu/sustainability-solutions-wordpress-theme/blob/master/javascripts/js/_slick-starter.js

Changes Claire made for the Walton site: https://github.com/gios-asu/sustainability-solutions-wordpress-theme/blob/master/style.css


Scala bridge fails if display is invoked before.

As a user, I want the scala bridge to work all the time
Expected behavior
It should work all the time
Actual behavior
It works only if display is not called. Once display is called, there is the following exception:
scala.MatchError:null

Fix has been released on PyPI with 1.1.9


Fix missing tabBarIcon option key on Tab navigation sample

Reference: https://reactnavigation.org/docs/en/next/tab-based-navigation.html

Closing due to no response


Custom poll frequency

Hi, it would be great if instead of a predefined set of values, users can define a custom poll frequency. Currently the options are too limited (from a flexibility point of view).
For instance, I would love to have a frequency of 45 minutes, but that is not possible with the current set of values.

This might be pointless given #1237


update chttpd

Bring in following two commits

Do not pass unknown_error atom to plugin
Call appropriate sockname function for socket type

+1


Fix Line Renderer editor error

Overview
The MixedRealityLineRenderer class executes always and thus in edit mode. The control has the capability to fade in the line via a coroutine executed in OnEnable. The problem is the control directly modifies the gradient value and executes in edit mode. So the fade overwrites any defaults or changing of the gradient in edit mode
Also some clean up on related classes with comments etc
Changes

Fixes: # .

Verification

As a reviewer, it is possible to check out this change locally by using the following
commands (substituting {PR_ID} with the ID of this pull request):
git fetch origin pull/{PR_ID}/head:name_of_local_branch
git checkout name_of_local_branch

/azp run


Add fallback parsing with collision detection as well as requires par…

Shared Model Changes
BaseElement.[h|cpp]: Implementation of new base class underlying both BaseCardElement and BaseActionElement that combines the previously duplicated functionality of each. This was needed to ensure that we only needed a single implementation of fallback and requires parsing/API access.
ParseContext.[h|cpp]: Add parse-time stack to track elements as they're being parsed. This is needed to detect id collisions across disparate portions of a card. More details on this implementation will be made available before checkin.
Everything else: Either push/pop calls when parsing child elements (e.g. Container) or cleanup/follow-on changes to support fallback. See comment in ParseContext.cpp for algorithm details.
Test Changes
samples/Tests/FallbackParsing.json: Test card containing element fallback and requires directives
ObjectModelTest.cpp: Contains new tests for id collision detection and [de]serialization of new requires and fallback properties
Various UWP test app JSON file changes to account for the fact that id is no longer emitted if it isn't set.

    Actions,

If you move Actions in the .cpp we should probably move it here too (nothing depends on these matching up, right?)

Refers to: source/shared/cpp/ObjectModel/Enums.h:13 in 2a849bc. [](commit_id = 2a849bc5bf520fc17acc57d50f2b65651013ff29, deletion_comment = False)

    Actions,

order doesn't matter. I was going for a sorted list to make it easier to spot mistakes. :D

In reply to: 459806981 [](ancestors = 459806981)

Refers to: source/shared/cpp/ObjectModel/Enums.h:13 in 2a849bc. [](commit_id = 2a849bc5bf520fc17acc57d50f2b65651013ff29, deletion_comment = False)

I've theoretically addressed all feedback. :)


Upadte demo app, and use local app for faststart

I would prefer not to introduce more diffs than necessary to the AppServer directory. Could we just include the fancy app on the disk image instead of putting it in the repo?


bug fix

I found a bug and fixed it.

:speak_no_evil: That's why it's a bad idea to refactor code after midnight ...
Thanks, I'll merge it


Recommended low-memory options

Duktape has large set of low-memory options so figuring out an optimal set is difficult. Could you recommend me a flag set which satisfies the following conditions:

An ES 5.1 compatible engine, which has 100% pass rate on es5-tests branch of test262 test suite excluding the internalization tests (i.e. all unnecessary features are disabled to reduce binary size).

Enabling low-memory options. Although test262 conformance tests and SunSpider benchmark suite should still work. The low-memory options should have an acceptable trade-of, e.g. 10% memory save for 10% perf loss is ok, but 100% perf loss for that memory gain is too much.

The engine should be optimized for 32 bit systems, 64 bit support is not needed at all (might affect choosing the options).

Thank you very much.

Any help would be appreciated. I thought Duktape works on low-end sytems, or that is not a target anymore?

Have you gone through https://github.com/svaarala/duktape/blob/master/doc/low-memory.rst ? You'll need to run your own benchmarks, but that documentation is pretty complete.

@zherczeg I've missed this issue for some reason. Duktape does target low memory systems and @saghul pointed to the currently best documentation going through the various options for that.
Some quick answers below:

An ES 5.1 compatible engine, which has 100% pass rate on es5-tests branch of test262 test suite excluding the internalization tests (i.e. all unnecessary features are disabled to reduce binary size).

Duktape doesn't currently pass all the test262:es5-tests; there are about 12 (?) failing tests whose issues boil down to (see doc/release-notes-xxx.rst for details):

Array .length issues for arrays longer than 2G elements.
Regexp empty quantified issue causes some regexps to match an empty quantified until they bail out due to a sanity limit.
A corner case issue for enumeration where an object has a non-enumerable property named P and an ancestor has an enumerable property also named P.  Test262 requires that "P" is not enumerated, but Duktape currently enumerates it.

Enabling low-memory options. Although test262 conformance tests and SunSpider benchmark suite should still work. The low-memory options should have an acceptable trade-of, e.g. 10% memory save for 10% perf loss is ok, but 100% perf loss for that memory gain is too much.

I'm not sure I understand why the relative performance loss is a useful criteria: different targets have different absolute performance requirements and an acceptable trade-off would depend on how close to that requirement a baseline configuration is.
In any case, you should be able to use most of the low memory suggestions in the document @saghul pointed to above. Pointer compression may affect performance more than the 10% you indicated - it depends on how the compression macros are defined; the macros are provided by the application code so they may make a function call or handle the pointer packing/unpacking inline. Dropping the hash part of the internal object representation (which is normally used for relatively large objects) may affect performance more than 10% for code dealing heavily with large objects (though low memory targets rarely have very large objects for obvious reasons).

The engine should be optimized for 32 bit systems, 64 bit support is not needed at all (might affect choosing the options).

There aren't any 32-bit vs. 64-bit target optimization options as such, but 32-bit systems should use "packed" duk_tval so that tagged values are represented by 8 bytes instead of 16. The duk_config.h config header tries to do that automatically based on architecture etc, but if that doesn't work you may need to force it manually.

Duktape doesn't currently pass all the test262:es5-tests; there are about 12 (?) failing tests whose issues boil down to (see doc/release-notes-xxx.rst for details):

That is not a problem. I just want to exclude non ES 5.1 features.
The documentation provided is about fine tuning the engine for those who already have deep knowledge about the internals. But this topic is about the evaluation of the engine for a newcomer. When people download the latest tarball, they don't want to do fine tuning, just setting a mode (e.g. default, low-memory, high-performance, etc.) and see how the engine performs on industry standard benchmarks. Since an evaluator knows little about the engine, there is a high chance of mis-configuring it, and that affects the outcome when several engines compared (imagine when you have to figure out the best options in a few days for 3-5 engines). The authors of an engine usually know the best options for a given scenario. Although that could be further fine tuned by 5-10% on certain architectures, but it still shows the general performance of an engine in a given scenario. When differences are high, fine tuning will not likely help.

Ah, I didn't realize you were specifically interested about general benchmarking rather than looking for options for a specific target.
There's no "benchmark configuration" at present, but the configuration example file config/examples/low_memory.yaml tries to answer that use case to some extent. It contains the most common low memory options which can be enabled without much thought. However, it's not really possible to provide a full out-of-the-box (very) low memory configuration (with Duktape at least) because low memory targets typically need carefully optimized allocation providers and pointer compression macros need to be defined to match that allocation provider and configuration. With Duktape the allocation provider is external to the engine to allow it to be adapted as flexibly as possible (e.g. to non-continuous memory pools, an existing system allocator, etc).
Typically the process with a specific target starts with defaults, and seeing how memory usage turns out on the target. If low memory optimization is needed, one can progressively enable low memory config options until some goal is reached. Each option comes with some trade-off: for example, disabling tracebacks has some usability implications but no compliance impact since they're not an ES5.1 feature. Because of these trade-offs, it's usually best to enable options one by one as needed - ideally one would need to give up a minimum of features to achieve the memory footprint for a certain target. (If no trade-offs were involved, there would only be a low memory configuration to begin with :-)

Hmm, since there's a pool allocator example already in the repo it'd be a relatively small effort to make a benchmark configuration based on that. It would then allow benchmarking builds with pointer compressions and (separately) builds with pointer compression and ROM built-in objects (which is a relevant configuration for very low RAM targets).
Performance optimized configuration is in config/examples/performance_sensitive.yaml. It's much easier to use as is because there's no external dependency like the allocator. There's one trade-off at least which may not be obvious: whether to enable or disable refcounting. Some environments rely on having accurate and prompt GC (which refcounting provides) while in others a periodic or emergency mark-and-sweep suffices. Refcounting has a clear performance impact because it affects a lot of operations.
I'll open a separate issue for making a more clearly defined set of benchmark-friendly configurations and support files available in the distributable. #845.

Thank you for the help.


Add entities on dialogflow

(NOT FOR MERGE.)
I'd need a review for now.

This pull request has been merged directly into dialogflow_integration.


Community Reshape to Discord + GitHub Discussions

For the JS SDK we are opening a GitHub discussions page to keep track of the soon to be released articles page as part of a larger README overhaul
The main reason for doing that is since we see several points that could be improved community wise:

Currently companies are tracked through one main issue (where is it again...)
Announcements are made on Discord and might get lost / not tracked through email
Community Meeting agendas are now in dapr/community, but it might make more sense to have this in a Forum functionality format
...

Next to the above, we also would like to:

Keep track of articles written by the community -> let our members post those so we can update the documentation
Discuss features more in a discussion kind of overview

Because of this, I think it also would make sense to open a discussion (through this issue) to see if we can have GitHub Discussions on the main dapr/dapr repository instead of dapr/community as dapr/dapr is the main entry point towards using it.
Looking forward to opinions! 😊

Do you have any examples of other repos that are doing this and how it works with their community? I haven't seen a repo do this, though I haven't looked too hard. Or is this all new and we'd be pioneering it?
Aside from that though, I think this could be cool. I like the idea of being able to find everything in a more centralized location and allowing users to share articles about dapr/the repo.

I do prefer the forum discussion over random chat on Discord. Is is hard to follow discussions in a single big thread. I am all in for this proposal. /cc @msfussell  @yaron2

The tricky issue here is that there is a large Discord community now and we cannot move that. So this would have to become a both GitHub Discussions and Discord and that means some duplication of issues, questions etc.

I do not necessarily agree, I think we can push the community to put more constructive discussions on GitHub discussions, while Discord is more for ad-hoc help from maintainers / community.
Vercel is doing it this way as well and it is working out quite nicely for them :)


⚠ Bofrost.be has degraded performance

In 38018ea, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1571 ms

Resolved: Bofrost.be performance has improved in af70fd5.


.github/workflows/tox.yml: add vagrant boxes caching

Add caching for the vagrant boxes to avoid errors like:
"An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.
The requested URL returned error: 429"
Fixes: #128
Signed-off-by: Arnaud Patard<EMAIL_ADDRESS>

That is going to be fun, we have some size limitation for caching,... i hope we do not hit them.

That is going to be fun, we have some size limitation for caching,... i hope we do not hit them.

yeah, I know that caching is not perfect but CI failures due to not being able to download is not nice either :(


Error with the demo

Hi, I run the demo with app.py but get this error:

Could you please help me with that?
I change the backend from "video_reader" to "pyav" because it sames that my pytorch doesn't support "video_reader", and the other code are unchanged.
# torchvision.set_video_backend('video_reader') torchvision.set_video_backend('pyav')

I forgot to install av, and this error disappears after installing av, but the program seems to be stuck at here.

The output in ther terminal is like this:

It is weird. Could you try cli.py? Also what is your GPU

I use A100, cli.py seems to work, it ouputs like this and end here:

Ok but the sentence seems not ending... Have you changed eos token id?

No, in fact I think I haven't done any changes to the code except for the video reader backend, you mean the output of the cli.py is not correct, either?

Yes, let me try that. Please wait a moment

Hi, my side is correct:

The possible reason is the HF Llama-3 version. HF originally has the wrong EOS token <|end_of_text|> (128001), but the actual eos token in chatting should be <|eot_id|> (128009). Could you check your llama-3 HF cache?

By default, the path is: ~/.cache/huggingface/hub/models--meta-llama--Meta-Llama-3-8B-Instruct/snapshots/xxx(see what folders you have under snapshots)/config.json. Make sure eos_token_id is 128009.

Hi wenyu, does the above solve your problems ;)

I'm very sorry for the late reply because I caught a cold recently and It also took me a while to download the newer llama-3 version. The new version seems to be correct, the config is as follows. But the result still seems to be wrong:

oh, I find the problem, the newer version llama3 I download is from a third-party url, and the eos token is not changed in the version I downloaded:

I renew it and It works fine!:

Thanks again for your warm help and great work.

Nice!

oh, I find the problem, the newer version llama3 I download is from a third-party url, and the eos token is not changed in the version I downloaded:  I renew it and It works fine!:
Thanks again for your warm help and great work.

Hello, I also meet this problem. I also download llama3 from third-party url. However, the output did not change even if I changed config.json(128009) and tokenizer_config.json as you said, is there anything else needed to change? Thanks a lot.


as3.6 create flutter project has been stuck in creating flutter project and then reported an error

Error creating project
			******  B A T C H   R E C U R S I O N  exceeds STACK limits ******
			Recursion Count=317, Stack Usage=90 percent
			******       B A T C H   PROCESSING IS   A B O R T E D      ******
			pub get failed (255; ******       B A T C H   PROCESSING IS   A B O R T E D

Hi @lihui123456
could you please provide your flutter doctor -v ,
and your flutter create test --verbose
Thank you

Hello,
Seems I'm experiencing the same behavior when trying to install and run flutter.
should I open a new issue or use this one?
Same error same number count and percent
Thanks


fix: Raise all boto and awscli versions

Issue #, if available:
Description of changes:
fix: Raise all boto and awscli versions
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

nit: do we again keep this in sync with exact NBI versions we used for model packages or update it to latest?


FIX typos and update README instructions

With this change I'm fixing couple of typos. Also, I'm including a basic use section

@snewcomer Conflict is fixed, error on Travis is due to Yarn

@Willibaur I don't think my approval counts for anything.  Will have to get somebody else to approve and merge...


Import from ofl, qif or csv file always give a "0 transactions imported"

Hello
I tried to import data from my bank account but whatever the format I choose (qif, ofl, csv), I always get the "0 itransactions imported" message.
I'm french and using a Linux Fedora 37 workstation with french numeric / date / time / numbers format settings.
Is there a way to get debug message that might help finding the root cause. I tried to use different localization settings in the export tool of my bank and tried to put american-like localization settings, but it didn't change anything, I still get the same result.

The american-styled date and amount formats should work no problem.
Granted for csv, the file must be of correct format...see #262
There won't be any error messages since the program catches them to avoid crashes. If you could send me samples of the files you are using that'd be great!

Here is an example using OFX with format of Money 2003 or later.
comptes.txt

I'm experiencing the same issues, also using Fedora 37.

Will be fixed in #286
NOTE: QIF files must have dates in US format. OFX files must have dates in YYYYMMDD format (as per document specifications).

https://github.com/nlogozzo/NickvisionMoney/releases/tag/2023.2.0-rc1-f1


GitHub: Invite member

Who should be invited to Catena-X ng
GitHub User:
JanisKretschmann - Developer for standardization within Catena - X
Vouching person:
Evgeny Vinokurov (GitHub Username: evgenyvinokurov) - Process Owner for Standardization within Catena - X

Invitation sent. @JanisKretschmann has to accept the invite within the next 7 days, otherwize the invitation will expire. After the invitation has been accepted you can add JanisKretschmann to your GH team.

The person was successfully added to the Standardization - Repository. Thank you


error in protobuf creation

Traceback (most recent call last):
File "C:\Users\rangabar.KEYSIGHT\Desktop\snappi_env\openapiart\lib\site-packages\openapiart\openapiart.py", line 102, in _generate
protobuf.generate(self._openapi)
File "C:\Users\rangabar.KEYSIGHT\Desktop\snappi_env\openapiart\lib\site-packages\openapiart\openapiartprotobuf.py", line 24, in generate
self._write_request_msg(path_object)
File "C:\Users\rangabar.KEYSIGHT\Desktop\snappi_env\openapiart\lib\site-packages\openapiart\openapiartprotobuf.py", line 44, in _write_request_msg
operation = self._get_operation(path_item_object)
File "C:\Users\rangabar.KEYSIGHT\Desktop\snappi_env\openapiart\lib\site-packages\openapiart\openapiartprotobuf.py", line 30, in _get_operation
operation_id = path_item_object['operationId']
TypeError: string indices must be integers
Bypassed creation of protobuf file: string indices must be integers

Please retry your test case with the latest version of openapiart 0.0.26.

@Rangababu-R have you retried your test case with the latest version of openapiart and is it resolved?

@ajbalogh could not get back, will update you tomorrow IST first half.

@ajbalogh issue is still seen in the latest branch too.


[Bug]:  Datasource Dropdown  is not displayed to user after the enter is cleared

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
API Datasource list is not displayed to the user when the user deletes the entered API once
Video:

Steps To Reproduce
1) Navigate to API pane
2) Save the data source
3) Navigate back to the API pane
4) Now delete the API
5) click on the API field
and observe

Environment
Release
Version
Cloud

@albinAppsmith can we fix the design system here? The enter is not captured in the URL field


feat: Improve search context feature

This PR builds on the feature built on #279. It improves the UI and add a new option useAllContextsWithNoSearchContext.

useAllContextsWithNoSearchContext
Adds an option that is off by default. The indexes from all contexts will also be present on the default index. This is to allow searching on every index. Using this option together with searchContextByPaths allows context and global searches.
Improvements to the the context UI by:

Displaying an indicator on the search bar when the using a specific context

Add a select to search by context on the search page

The following new strings are added and will need to be added to the translation files:

theme.SearchBar.searchInContext
theme.SearchPage.searchContext.everywhere

@weareoutman can you take a look when you have some spare time? 😄

@aericson Thanks for you contribution, this seems great!
However, I got very busy these weeks, I'll try to look into it later.

@aericson Thanks for you contribution, this seems great!
However, I got very busy these weeks, I'll try to look into it later.

Take your time, just wanted to get it in your radar in case you haven't seen it.

Thanks again, release in 0.34.0


Appstudio update test-component-pac-plqf

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-component-pac-plqf-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
15 seconds
clone-repository

✅ Succeeded
34 seconds
build-container

✅ Succeeded
26 seconds
inspect-image

✅ Succeeded
25 seconds
deprecated-base-image-check

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
24 seconds
sbom-json-check

✅ Succeeded
15 seconds
label-check

✅ Succeeded
11 seconds
show-sbom

✅ Succeeded
18 seconds
show-summary

Pipelines as Code CI/test-component-pac-plqf-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
10 seconds
init

✅ Succeeded
14 seconds
clone-repository

✅ Succeeded
35 seconds
build-container

✅ Succeeded
19 seconds
inspect-image

✅ Succeeded
18 seconds
deprecated-base-image-check

✅ Succeeded
11 seconds
clair-scan

✅ Succeeded
44 seconds
clamav-scan

✅ Succeeded
11 seconds
sbom-json-check

✅ Succeeded
21 seconds
label-check

✅ Succeeded
11 seconds
show-summary

✅ Succeeded
8 seconds
show-sbom

Pipelines as Code CI/test-component-pac-plqf-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
10 seconds
init

✅ Succeeded
14 seconds
clone-repository

✅ Succeeded
35 seconds
build-container

✅ Succeeded
19 seconds
inspect-image

✅ Succeeded
18 seconds
deprecated-base-image-check

✅ Succeeded
44 seconds
clamav-scan

✅ Succeeded
11 seconds
clair-scan

✅ Succeeded
11 seconds
sbom-json-check

✅ Succeeded
21 seconds
label-check

✅ Succeeded
8 seconds
show-sbom

✅ Succeeded
11 seconds
show-summary


Support function argument labels

Not sure whether this is a good idea, as it interferes with how public contract functions will be called


Fix Model specularEnvironmentMaps bug

Fixes #7684
If specularEnvironmentMaps is set twice to the same value before Model.update is called, then the specularEnvironmentMapAtlas is not updated properly

Thanks for the pull request @hpinkos!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

Thanks @hpinkos!


Popover and Stage scroll with fixed Element

Added the possibility to add the property elementPosition to a Driver.Step. When this property is set to 'fixed', the popup and the stage will be positioned 'fixed'. This fixes in issue, in which the tooltip would not stay on the highlighted Element, when the user scrolled.
It was not enough to set the position to 'fixed' on all 'fixed' highlighted elements, because a child of 'fixed' position element is itself not 'fixed' but behaves that way because of its parent.

Apologies for the radio silence, I got super busy and couldn't find time to maintain this project. We have started to actively use it at my current company and decided to rewrite it due to underlying implementation issues. It now has much simpler API and is feature rich as compared to the previous version.
Please have a look at the release docs for v1.0 and the documentation and do let me know if you face any issues. Thanks again for taking your time to submit the PR! 🙏


Pop up an error when restoring a C# project with .NET Core SDK 2.2.x installed

OS: Win10
Build Version: 20191120.2
Func Version: 3.0.1704
Repro Steps:

Make sure there is no any .NET Core SDKs --> Create a C# project.
Pop up an error to prompt the users to install 2.x or 3.x of the .NET Core SDK.

Install .NET Core SDK 2.2.207.
Create a C# project -->Prompt to restore the C# project.

Expect:
Succeed to restore.
Actual:
Fail to restore with an error "The current .NET SDK does not support targeting .NET Core 3.0...".

More Info:
Restore C# projects well with .NET Core SDK 3.0.101 installed.

So here's the problem:

User has v3 of the func cli
We tell them to install 2.x or 3.x of the .NET Core sdk
If user installs 2.x, they run into a mismatch because the default template uses 3.x

Users can work around this by modifying the target framework directly in the csproj to 2.x. Not exactly sure what we should do here

Got it. Thanks for your sharing.
So we need to make sure the version of .NET Core SDK matches the version of func cli?

@v-dantch you don't need to do anything for now. We still have to decide how to handle this scenario

Got it :) .

Let's change our error message to tell people 3.x is recommended


Testgrid dashboard is not showing consistent data for CircleCI Jobs

http://k8s-testgrid.appspot.com/istio-presubmits
Some of the links in the presubmit is showing data from each checkin, whereas the other ones are showing data from nightly runs, or some unrelated branches/jobs.
Some examples:
http://k8s-testgrid.appspot.com/istio-presubmits#circleci-e2e-simple
http://k8s-testgrid.appspot.com/istio-presubmits#circleci-e2e-pilot-cloudfoundry-v1alpha3-v2
http://k8s-testgrid.appspot.com/istio-presubmits#circleci-test
Counter example:
http://k8s-testgrid.appspot.com/istio-presubmits#circleci-racetest
It is probable that this is because of our dependency on CIRCLE_PULL_REQUEST environment variable, which may be getting set inconsistently:
https://discuss.circleci.com/t/circle-pull-request-not-being-set/14409

I found some more problem symptoms.

Some circle presubmits are not longer uploading to GCS. Example https://circleci.com/gh/istio/istio/193967

#!/bin/bash -eo pipefail
bin/ci2gubernator.sh --job_starts
GCS_BUCKET_TOKEN not defined

The non presubmit bucket now have post submit data from master branch, while the presubmit buckets have post submit data from all other branches.

I will try to fix it.

The first problem is fixed by @rshriram. GCS_BUCKET_TOKEN  is now passed to all test jobs.
The second problem is fixed by https://github.com/istio/istio/pull/8910.

I am going to fix testgrid config to make sure things are pointing to the right bucket.


Implement np.clip as __array_function__

Would close https://github.com/pydata/xarray/issues/2570
Because of https://numpy.org/neps/nep-0018-array-function-protocol.html#partial-implementation-of-numpy-s-api, no option is ideal:

Don't do anything — don't implement __array_function__. Any numpy function that's not a ufunc — such as np.clip will materialize the array into memory.
Implement __array_function__ and lose the ability to call any non-ufunc-numpy-func that we don't explicitly configure here. So np.lexsort(da) wouldn't work, for example; and users would have to run np.lexsort(da.values).
Implement __array_function__, and attempt to handle the functions we don't explicitly configure by coercing to numpy arrays. This requires writing code to walk a tree of objects looking for arrays to coerce. It seems to go against the original numpy proposal.

@shoyer is this summary accurate?

This summary looks right to me!
Another option is to make our own library of elementwise "universal" functions, like the old xarray.ufuncs. I think this might be a more maintainable and explicit option, because the user knows that something Xarray related is going on and hence doesn't have to wonder whether Xarray objects will be converted into NumPy or not. It would also work better for static type checking.

OK, thanks, I'll close this.

Another option is to make our own library of elementwise "universal" functions, like the old xarray.ufuncs. I think this might be a more maintainable and explicit option,

I think most of them are methods at the moment — e.g. .clip, and I'm not sure there's a huge space for things that are significant enough to put in a small library, but not significant enough to put as methods? Or maybe having actual functions is a bit nicer than methods specific to each type?


luma.oled 3.2.1 identifies ssd1327 as ssd1306 gives black screen

Type of Raspberry Pi
Raspberry pi zero W
Linux Kernel version
Linux raspberrypi 4.19.42+ #1219
Expected behaviour
when running tv_snow.py with a ssd1327 I expect the program to identify the oled as a ssd1327 with 128x128 resolution.
Actual behaviour
what actually happens is the ssd1327 is identified as a ssd1306 with 128x64 and the tv_snow.py program runs but nothing is displayed on the ssd1327 screen.
I have tested with a ssd1306 attached and it works fine. I have verified the ssd1327 is working by testing on another project. I have tried 7 ssd1327's all are identified as ssd1306
this just started happening after the most recent update.

If you are using the luma.examples, the demo scripts aren't smart enough to figure out which display you are using, so you should generally specify the device, interface and width/height. There is a config flag and some predefined options (see https://github.com/rm-hull/luma.examples/tree/master/conf).
So you should start the examples with:
$ python examples/tv_snow.py -f conf/xxx.conf

Where xxx is your display device. I thought I had added one for SSD1327, but looks like I haven't so I'll do that shortly.
The default options on the examples are to select SSD1306 and I2C. If you look at the readme there are many options you can tweak for your device, but I will make it clearer that if no options are set it will default to SSD1306.
Also, for the short term you should follow the advice in the comments of #253 until we sort out the bug.

@A-n-o-r-a-k when you run the tv-snow example, could you provide the command you use and console output please when you run the examples.

@rm-hull tried it again with the -f conf file and with several ssd1327 screens and the tv_show.py program does not throw an error, I get the prompt back and nothing on the screen. I have checked all of the wiring and confirmed the screen works on another project. I am going to try to back rev the package as described above.

Uploading a photo of the wiring going from the screen to the raspberry pi would help.
The latest luma.core package fixes the bug mentioned in #253, so you should make sure it is up-to-date with pip install luma.core -U

any feedback @A-n-o-r-a-k?

no feedback, closing.


Authorization header is missing in some curl commands

Is your suggestion related to a missing or misleading document? Please describe.
Authorization header is missing in some curl commands. Therefore curls are not usable in copy pasted manner.
example:
https://is.docs.wso2.com/en/next/apis/scim2-rest-apis/#tag/Groups-Endpoint/operation/getGroup

Ideally the API section should contain an option to set the authorization header based on user input (basic auth, bearer token ..)
But now we have hard coded curls. Therefore appending a dynamic authorization header is not possible.
Eventhough bearer token based authorization is the common case and which we promote, to give usability aspect in current curl commands we need to add basic auth based authorization header to hardcoded curls

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


What if I spelled "fcuk" wrong?


Mask R CNN using L515

Camera Model: L515
Firmware Version: v2.45.0
Operating System & Version: Ubuntu 18.04
Kernel Version: 5.4.0-72-generic
Platform: PC
Language: Python
I am using mask rcnn using L515.

In this example, what is the input resolution to L515?
https://github.com/IntelRealSense/librealsense/blob/master/wrappers/python/examples/align-depth2color.py

I want to lower the resolution only when I detect the input image and use the original resolution for re-output. What should I do?

oh,, i did


Automatic check of API backward compatibility

For the planned release on 09/2024, we should contribute some kind of automatic checking for backward compatibility of API of our libraries. Once #10369 is merged, it should not be difficult.
#10369 refines the BindingsMap.exportedSymbols field to contain all the resolved symbols in the exports.
The automated backward compatibility check could work as follows:

Store the dumped exportedSymbols field into a binary signature file for all the Main modules of our libraries.

Dumping can be done using our Persistance framework, that already works for that field.

Once a change is made, compare the new exportedSymbols field with the one stored in the signature file.

What is and what is not backward compatible is yet to be defined. For example, if to_json already resolves to multiple extension methods, having even more extension methods there is backward compatible. But removing an exported symbol is not backward compatible.
Inspiration from NetBeans:

https://github.com/jtulach/netbeans-apitest
https://github.com/jtulach/netbeans-apitest/blob/master/src/test/resources/org/netbeans/apitest/org-netbeans-api-java.sig

Prepare a design for review, Pavel.

As part of library compilation, we already generate cached Suggestions. They are later sent to the IDE in JSON format. The sigfile can thus be a JSON-formatted .suggestions. Implementation-wise this should be the most straightforward approach. Moreover, for the backward compatibility, suggestions are what we should care about the most.

The sigfile can thus be a JSON-formatted .suggestions.

Related to #9999

CCing @4e6 and @hubertp


Correct acceptable electoral district values

The old list in the error message does not match the actual validation. The error message has been updated with the actual regular expression used.
Pivotal bug: 105787956

Do we show error messages with regexes?
LGTM

@ericnormand we do now!


Start a custom "technology radar" for Artsy

For a while we've talked about making shared technology decisions and strategy more visible across Artsy. This is a quick attempt to build a custom "technology radar" for Artsy using ThoughtWorks' approach and tool.
There are lots of gaps and I'd love for others to add the significant technologies they're discouraging, evaluating, and encouraging to this framework.
The links should start working after this is merged 🤞, but in the meantime you can interact with a version built with the same data here. Screenshots:

Some orgs give formal ownership of this process to a technology review committee and reevaluate status every quarter or month. It's interesting to imagine how we might evolve a process like that.

Wow, this is so cool!
How do you imagine people should edit this? (at-will? with some kind of process?)

Good question about how this should be edited, especially since of these choices may be controversial.
I think we were already documenting some of these preferences and communicating others informally, so this just makes that information a little more accessible. (If it inspires debate, great!)
At the moment there are entire technology/technique categories where I don't even know what placeholders to include, or where, so I'd love for others to freely add those. E.g., Relay, Redux, Fastlane, ...
Once we've addressed the remaining "easy" stuff (about which there's broad agreement), any meaningful changes probably should be taken up only very deliberately. Maybe by a practice meeting or RFC?

Great initiative! Thanks for starting this. This visualization is very powerful.

At the moment there are entire technology/technique categories where I don't even know what placeholders to include, or where, so I'd love for others to freely add those. E.g., Relay, Redux, Fastlane,

@joeyAghion https://github.com/artsy/README/pull/202


spicedb CLI returns error code 0 regardless of application errors

What
SpiceDB spicedb CLI should return non-zero error codes when a failure happens
Why
The application should signal why did the process terminate through error codes. This particularly important for container schedulers like kubernetes that make use of the error code to determine pod lifecycle state (e.g. pods that terminate with non-zero error code are considered in Failed state). If a pod terminates with a zero error code (state Succeeded) no restarts will take place.

@jzelinskie yeah I had already tested the same snippet locally and seemed to do what I needed:

SIGTERM'ing the process returned error code zero
Any error returned in the execution of the command would return non-zero

A quick look into the cobra repository (https://github.com/spf13/cobra/issues/914) invites to think it should be sufficient to do what you posted above, with some friction around when to show the command list.


Allow for MySQL 8.0 in a few places

Oracle MySQL now have a dev version of 8.0. It seems useful to be able to at least recognise the version in the code etc. So there are 2 patches here which allow for that.
On a side note it seems to me that the MYSQL_FLAVOR=MySQL56 definition which has been used is a little outdated and thus confusing given it also applies to MySQL 5.7 and 8.0. Perhaps a more appropriate value might be OracleMySQL or similar?  Adapting the code to use a different name might be better (as this is currently a configuration option) though an improvement would be to recognise the appropriate version where this is needed and automatically adjust behaviour accordingly.
In any case this small patch at least makes Vitess minimally aware of MySQL 8.0 and ensures it should do the right thing.

LGTM
Alain, any objections?
@sjmudd Yes, using MySQL56 for MySQL 5.7 is confusing, I agree. But I don't have a good solution either. I think the flavors mostly exist between the GTID handling is different between MariaDB and MySQL.

So if this patch looks ok to you please accept.
If you want me to make a separate issue for the MYSQL_FLAVOR name change please let me know and I will do that.

Yeah, this one is good to merge as is unless Alain disagrees.
Let's hold off on the flavor change for now. I'm concerned it's going to be more involved (documentation, Docker images?) for very little value. And OracleMySQL is not that appealing as well. If we change it, we should just go with MySQL.

Ok. That's fine with me. The point I was making with this is that I had to double check what value to use and you doubt using the value MySQL56 when actually you're using MySQL 5.7 and if I want to try 8.0 what's the right value to use there? This just confuses people and given 5.7 has been GA for nearly 2 years and 8.0 is likely to go GA (I'm guessing) some time after OOW in October this year it will only make things worse.
My feeling is this should just be handled by the code. It's not generally too hard to do that at the moment and means one less setting to worry about which simplifies things for anyone setting up Vitess for the first time. I'm still having trouble getting the setup to work I guess as I've overhacked vttablet-up.sh and its friends, so any reduction in configuration settings will remove possible problems.
In any case thanks for listening.

LGTM

I agree 100% we need to do better. In all cases, we can detect the MySQL version and act appropriately. The only reason we haven't done better is the Google internal versioning scheme, where we need to detect the version correctly, and so we have left the open source version lag somewhat behind.
You rightfully filed issue https://github.com/youtube/vitess/issues/2877 I'll try to prioritize it.


problem occur after adding my firebase.

My project where work perfectly, but when I add the Firebase and start work on it the I could not open it agin on the simulator
the output which I resive
note: I m using tabBar in my project
Launching lib/main.dart on iPhone 11 Pro in debug mode...
Running Xcode build...
Xcode build done. 19.6s
Configuring the default Firebase app...
Connecting to the VM Service is taking longer than expected...
Still attempting to connect to the VM Service...
If you do NOT see the Flutter application running, it might have crashed. The device logs (e.g. from adb or XCode) might have more details.
If you do see the Flutter application running on the device, try re-running with --host-vmservice-port to use a specific port known to be available.
Exception attempting to connect to the VM Service: SocketException: OS Error: Connection refused, errno = 61, address = <IP_ADDRESS>, port = 60093
This was attempt #50. Will retry in 0:00:01.600000.
Exception attempting to connect to the VM Service: SocketException: OS Error: Connection refused, errno = 61, address = <IP_ADDRESS>, port = 60230
This was attempt #100. Will retry in 0:00:01.600000.
my flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, 1.20.0-1.0.pre.157, on Mac OS X 10.15.5 19F101,
locale en-SA)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
[✓] Android Studio (version 3.6)
[✓] Connected device (1 available)
• No issues found!
MBPalkhasbSara:~ saraalrabiah$ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, 1.20.0-1.0.pre.157, on Mac OS X 10.15.5 19F101,
locale en-SA)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
[✓] Android Studio (version 3.6)
[✓] Connected device (1 available)
• No issues found!

Hi @Saraalr
From what I can see, the issue is related to a FlutterFire plugin rather than to Flutter itself. Please open the issue in the dedicated repository.
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments, possibly providing a minimal reproducible code sample that does not use flutter fire or other 3rd party plugins, and I will reopen it.
Thank you

In my case, I got that error because I added the google file by second time
like this: GoogleService-Info (2).plist,
So my solution was delate all the google files from Downloads and from my .xcworkspace
And repeat the steps to link with Firebase
When you download one more time the google file you must always include like this: GoogleService-Info.plist


combining chunks of a large file produces file too large

Type of issue

[ ] Bug report

Uploader type

[ ] Traditional

chunking success called multiple times resulting in oversized file
Fine Uploader version
5.16.2
Browsers where the bug is reproducible
{example: "Firefox" and "IE11"}
Operating systems where the bug is reproducible
Any OS, tested on google chrome
Exact steps required to reproduce the issue
Upload large file, 7GB with chunking enabled
All relevant Fine Uploader-related code that you have written
chunking: {
        enabled: true,
        concurrent: { enabled: true},
        partSize: 20 * 1048576,
        success: { endpoint: myhost + "/success" }
    },

Your Fine Uploader template markup (if using Fine Uploader UI and the issue is UI-related)
{simply copy and paste your template markup}
Detailed explanation of the problem
chunking success gets called at the end of a large upload (7GB).
As the chunks are being combined on the backend (nodejs), it takes approximately 2 minutes to complete.
After roughly 60 seconds, the chunking success call occurs again, is this retry logic?
As a result, their are 2 processes combining the chunks.
The resulting file is too large.
Chunk size: 20MB, 353 total chunks.
It appears that if combineChunks() doesn't finish quickly enough, it will auto retry and kick off another separate process and corrupt the file.

This isn’t a fine Uploader issue. My guess is that the request is timing out or being cancelled due to the fact that the connection is idle for so long. ELBs are known to do this, for example. You’ll need to consider another approach server side, such as combining chunks async or combining them as the chunks come in.


Updating Markdown to markdownlint

Description
Updates CHANGELOG.md so it passes markdownlint test.
Issues Resolved
https://github.com/sous-chefs/atom/issues/36
Check List

[x] All tests pass. See TESTING.md for details.
[x] New functionality includes testing.
[x] New functionality has been documented in the README if applicable.

Thanks @maskott. Congrats on the first Sous Chefs PR


Adding scene to new story is broken

New scene not being added on new story.

Created a new story. Clicked Save Story Information. From client-side log, the story was created. I can see the story ID. No page refresh, which is good.
Entered a scene title and clicked +. Client-side log says, "We need to establish a draft before adding a scene." Should have added the scene.

Initial scene is created by service, so that should have appeared in list of scenes when the story was created.
** SAVED_DRAFT action needs to trigger load of first scene (or all scenes) when creating new story.

Reorganized so new draft is created from Desktop.
Fixed some problems in reducers that were not updating state on saveDraft. Pulled out components on edit story and got rid of internal state. Just looking at Redux state.


Maven central

now able to deploy to maven central

merging

oh sry wrong project ;)

Decebal Suiu » pf4j #91 FAILURE
Looks like there's a problem with this pull request
(what's this?)


Unable to find template _Entity_SearchResultInterface.php.html.twig

Unable to find template<EMAIL_ADDRESS>(looked into: [...]umc/src/Umc/MagentoBundle/Resources/views).

This should be fixed in Version 4.3.6


get error when runing python captcha_train.py

hi
Time to run the following code :
python captcha_train.py
im using the flow library:
https://github.com/PatrickLib/captcha_recognize
im installation :

python 2.7
Anaconda2 4.3.1
TensorFlow 1.1

get this erros :((
Traceback (most recent call last):   File "captcha_train.py", line 89, in <module>     tf.app.run(main=main, argv=[sys.argv[0]] + unparsed)   File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/platform/app.py", line 48, in run     _sys.exit(main(_sys.argv[:1] + flags_passthrough))   File "captcha_train.py", line 65, in main     run_train()   File "captcha_train.py", line 57, in run_train     coord.join(threads)   File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/coordinator.py", line 389, in join     six.reraise(*self._exc_info_to_raise)   File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/queue_runner_impl.py", line 234, in _run     sess.run(enqueue_op)   File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 778, in run     run_metadata_ptr)   File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 982, in _run     feed_dict_string, options, run_metadata)   File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 1032, in _do_run     target_list, options, run_metadata)   File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 1052, in _do_call     raise type(e)(node_def, op, message) tensorflow.python.framework.errors_impl.NotFoundError: ./data/train.tfrecords          [[Node: input/ReaderReadV2 = ReaderReadV2[_device="/job:localhost/replica:0/task:0/cpu:0"](input/TFRecordReaderV2, input/input_producer)]]
Caused by op u'input/ReaderReadV2', defined at:   File "captcha_train.py", line 89, in <module>     tf.app.run(main=main, argv=[sys.argv[0]] + unparsed)   File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/platform/app.py", line 48, in run     _sys.exit(main(_sys.argv[:1] + flags_passthrough))   File "captcha_train.py", line 65, in main     run_train()   File "captcha_train.py", line 19, in run_train     images, labels = captcha.inputs(train=True, batch_size=FLAGS.batch_size)   File "/app/captcha/captcha_model.py", line 15, in inputs     return captcha_input.inputs(train, batch_size=batch_size)   File "/app/captcha/captcha_input.py", line 44, in inputs     image, label = read_and_decode(filename_queue)   File "/app/captcha/captcha_input.py", line 21, in read_and_decode     _, serialized_example = reader.read(filename_queue)   File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/io_ops.py", line 193, in read     return gen_io_ops._reader_read_v2(self._reader_ref, queue_ref, name=name)   File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/gen_io_ops.py", line 411, in _reader_read_v2     queue_handle=queue_handle, name=name)   File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/op_def_library.py", line 768, in apply_op     op_def=op_def)   File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/ops.py", line 2336, in create_op     original_op=self._default_original_op, op_def=op_def)   File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/ops.py", line 1228, in init     self._traceback = _extract_stack()
NotFoundError (see above for traceback): ./data/train.tfrecords          [[Node: input/ReaderReadV2 = ReaderReadV2[_device="/job:localhost/replica:0/task:0/cpu:0"](input/TFRecordReaderV2, input/input_producer)]] 2020-07-02 07:33:55.821848: W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use SSE4.1 instructions, but these are available on your machine and could speed up CPU computations. 2020-07-02 07:33:55.822614: W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use SSE4.2 instructions, but these are available on your machine and could speed up CPU computations. 2020-07-02 07:33:55.823256: W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use AVX instructions, but these are available on your machine and could speed up CPU computations. 2020-07-02 07:33:55.823711: W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use AVX2 instructions, but these are available on your machine and could speed up CPU computations.
please help me

TF 1.1 is very old version .Request you try with latest TF versions such as 1.15 or 2.3-rc0 and let me know if the issue still persists.
Please, provide the exact sequence of commands / steps that you executed before running into the problem.Thanks!