Add WAFU Smart Electronic Lock (Deadbolt)

Any chance you guys can add integration for the Wafu deadbolt?
{
"result": {
"active_time":<PHONE_NUMBER>,
"biz_type": 18,
"category": "ms",
"create_time":<PHONE_NUMBER>,
"icon": "smart/icon/bay1605170594678IbeH/fad5891225b6191bb2563d6deac53c87.jpg",
"id": "66074035e868e76ce739",
"ip": "<IP_ADDRESS>",
"lat": "xxx",
"local_key": "xxx",
"lon": "xxx",
"name": "Deadbolt",
"online": true,
"owner_id": "xxx",
"product_id": "gj9eyv7lvtinjvui",
"product_name": "HANDLOCK CERRADURA ELECTRICA INVISIBLE",
"status": [],
"sub": false,
"time_zone": "-05:00",
"uid": "az162507203720968Onq",
"update_time":<PHONE_NUMBER>,
"uuid": "66074035e868e76ce739"
},
"success": true,
"t":<PHONE_NUMBER>110
}
I see category "ms" is not yet supported, I'm a developer perhaps I can integrate it myself?  If so any documentation or example integrations so I can start?
Thank you,
Steve

@steve-tapgen You can read this doc https://github.com/tuya/tuya-home-assistant/wiki/How-to-develop-a-new-driver.

Here is the lock's instruction set https://developer.tuya.com/en/docs/iot/f?id=K9i5ql58frxa2
You are welcome to create a PR about the lock.

Thanks for the insight, it seems this lock is quite different than the standard docs.
device status gives:
{
"code": 2003,
"msg": "function not support",
"success": false,
"t":<PHONE_NUMBER>804
}
if I query for functions:
{
"code": 2009,
"msg": "not support this device",
"success": false,
"t":<PHONE_NUMBER>094
}
In the HA logs it says for specifications same thing:
2021-07-03 21:33:02 DEBUG (SyncWorker_0) [tuya iot] Request: method = GET, url = https://openapi.tuyaus.com/v1.0/devices/66074035e868e76ce739/specifications, params = None, body = None, headers = {'client_id': 'xxx', 'sign': 'aaa', 'sign_method': 'HMAC-SHA256', 'access_token': 'aaa', 't': '1625362382146', 'lang': 'en'}
2021-07-03 21:33:02 DEBUG (SyncWorker_0) [tuya iot] Response: {
"code": 2009,
"msg": "not support this device",
"success": false,
"t":<PHONE_NUMBER>234
}
I've tried running various commands from the documents, along with smart lock documents.
The only success I've had is using TuyAPI where it lists the dpIds:
{ devId: '66074035e868e76ce739', dps: { '15': 2, '101': true } }
The dpsid 15 is a counter how many times the lock has been opened.
I can set the dpsId 101 to false and true to open and close the lock:
device.set({dps: 101, set: locked})
However I can't seem to find what functions these dps is to call using the cloud api.
Is there any way to directly set the dpsid's instead of sending commands in the code?
Is there a way to trace what commands the Smart Life application is sending to the API?
Thank you,
Steve

@steve-tapgen  The device specifications need to standardize, we will fix it soon.
After that, you can develop on it.

@tsutsuku i will use this topic to not create another...
Actually i have a smartlock... and get the information on log.
So i saw the ""category": "ms","
My ask is...if exist possibility to create a archive to put this smartlock there?
the model is: X2

@freitas666 You mean to develop a lock driver or something else?

Yes a lock driver...
Its possible? Could you help me?
Enviado do meu iPhone
Em 6 de jul. de 2021, à(s) 03:43, tsutsuku @.***> escreveu:

@freitas666https://github.com/freitas666 You mean to develop a lock driver or something else?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/tuya/tuya-home-assistant/issues/38#issuecomment-874502581, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAQ7DLWL6C5H2BLA2IKAQH3TWKQXRANCNFSM47VFQWXA.

Some idea?

@freitas666 We will consider it.

Support for these WAFU locks would be really great.


Add groundshaking to report

This is a statewide layer (will appear on all reports)
Add to Table 1
Add as the first hazard in the Earthquake group
Layer in webmab is Utah Earthquake Hazards - Groundshaking Polygons
HazardUnitTextTable contains associated text

Make this map 2x zoom out from the rest, due to the resolution of the data.  So if the other maps are at a scale of 1:15,000, make this one 1:30,000.


Refactor Setup into Getting Started

This is a...

[x] Feature Request
[ ] Bug Report

Problem
The organization of content in Setup doesn't make sense, and currently forms a hodgepodge of vendor-specific walkthroughs. These walkthroughs are often outdated and needlessly duplicated on kubernetes.io.
Proposed Solution

[ ] Rename the section from Setup to Getting Started
[ ] Refactor content to form a sequential, sensible journey through how to get started with Kubernetes, rather than vendor-specific configuration information.
[ ] Rename section headings to focus on tasks specific to getting started

Page to update
https://kubernetes.io/docs/setup/

10468

/open


Support 84-track SCP files

According to version 2.2 of the SCP image specification at cbmstuff.com the number of Track Data Entries for a floppy can be up to 168, so that up to 84 tracks can be recorded (e.g., fluxengine -c 0-83).

BYTES 0x10-0x2AF (for floppy image files) are a table of longwords with each entry being an offset to a Track Data Header (TDH) for each track that is stored in the image.  The table is always sequential.  There is an entry for every track, with up to 168 entries supported for floppy disks.  This means that floppy disk images of up to 84 tracks with sides 0/1 are possible.

Additionally, instead of segfaulting if a too-large number of tracks (e.g. -c 0-84) is used, print a message and continue.

Much better --- thanks very much!


register logger(s) as error handler(s) (opt-in)

adds module init listener to register loggers as error handlers. this is a configurable (opt-in) behavior.

@snapshotpl i really appreciated your feedback on #18 , and would love it if you could jump in on this retry.
i have become a collaborator on this project since the last time we worked together. updates to minimum dependency versions (and PHP syntax) are coming soon : )

I realize that you ping me about this PR... Let's review! ;)

closing due to inactivity


How to handle "variants" of a schema.

Hypothetical scenario:
User DOUG creates a new schema named D_SCHEMA, which consists of two characters - SIZE and COLOR. Character COLOR has three possible states - RED, GREEN, or BLUE.
User ANDREW likes D_SCHEMA, but he wants to use a slightly different version.
Andrew's Changes:

ADD new state PURPLE to character COLOR
REPLACE state GREEN with new state YELLOW
SYNONYMIZE state RED with new state CRIMSON

What is the best way to represent this in the database?

There are two end-member solutions, with a gradient between them.
Type 1-Extreme:
Create an entirely new schema A_SCHEMA that is a full duplicate of D_SCHEMA with the various changes added, and then add some sort of :IS_VARIANT_OF tag from A_SCHEMA node to the original D_SCHEMA node.
Type 2- Extreme:
Add new nodes to the existing D_SCHEMA tree, but flag them in the properties as being variants.

After my meeting with the NEO4J people, I actually think that Type-2 is closer to the graph way of thinking.

I'm wondering if Type 1 would behave better when we run the comparison function on a new specimen. But I suppose, in the case of Type 2, we could build whether or not to use variant nodes into the compare function.

This is essentially solved by the recent rework to :Description nodes described in #12 - i.e., we just handle it in an analogous to way to the OTU and Specimen relationship
:Schema {type: "original"}
:Schema {type: "variant"}


Add space to the top of magnifying glass

@AbdurazaaqMohammed A new magnifier icon for you (it more reflect the minimal app style):


Update sinon-chai support

Simplify peerDependency versions
This should resolve https://github.com/kmees/karma-sinon-chai/issues/55

+1

Published as<EMAIL_ADDRESS>

Thank you!


Update setup.cfg for README.rst

README file type has changed

This PR is related to openjournals/joss-reviews#5444


Cache glob'd configs

I am checking the skipConfig flag in both functions similar to the checks in both __invoke and  mergeModuleConfig.

Can you add a test for this, please?

Why not using Zend\Cache to cache config files ?

Because this is happening before we have configuration available, and
should be as lightweight as possible. Also, note that the cached file can
then be directly used by include(), without requiring de-serialization.
On Sunday, January 8, 2012, Marc Bennewitz <
<EMAIL_ADDRESS>wrote:

Why not using Zend\Cache to cache config files ?

Reply to this email directly or view it on GitHub:
https://github.com/zendframework/zf2/pull/703#issuecomment-3401791

--
Matthew Weier O'Phinney
<EMAIL_ADDRESS>http://mwop.net/


mAP@small and @medium is -1.00

I'm running custom dataset, tt100k. Json format converted to Coco Style.
Why is this happening?
Any Suggestions?
Thank you!

What is your mmdet version?
This issue duplicates https://github.com/open-mmlab/mmdetection/issues/3468 and should already be fixed in https://github.com/open-mmlab/mmdetection/pull/3497.


View Logs for InitContainers in Dashboard

As of now I can only find this possibility in Explorer whilst I dont happen to see them in Dashboard

@vincent99 nailed it. In the old manager view we were able to see these logs. As the manager is totally unaavailable with 2.6.0 this is somewhat critical as I cant view the logs of any initContainer (thats possibly crashing) through rancher anymore

Thanks @boindil

Verified on v2.6-head 1a57856
init cotainer logs are shown in the pods details page:


Set of new features

Issue #, if available:
Description of changes:

Migrate from deps to go modules - This is done mainly to use latest version of the goformation
WAF 2 integration
HostedZone integration
Support for route53 in shred account
Features provided in https://github.com/awslabs/amazon-apigateway-ingress-controller/pull/15

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

When do we think this PR can be merged? These are long pending updates.

@danushkaf .. Does your PR support  following :

Lambda Authorizers
HTTP Proxy integration

@danushkaf The long standing updates here are pretty great and it would be awesome if we could go ahead and merge

Any chance this will ever get merged? We've been looking forward to these features ever since this was first developed a year ago and would love to implement into our stack


Create a new type-alias AssetId

I think it could be helpful to add a type alias for the ContractId type: AssetId.
It would be purely for the added semantic context, as all AssetIds  (with the exception of the NATIVE_ASSET_ID) are also ContractIds, but not all ContractIds represent assets.
cc @sezna @adlerjohn

I'm wondering if Sway (and this issue) might be better served with Newtype rather than type aliases.
Adding a new EthAddress type would be another place we could use NewType and actually get type safety as a benefit.
As I understand it, type aliases don't give us that.

This is true, but also supported by the fact that Sway doesn't have type aliases 😄

Rust has newtype via struct AssetId(ContractId); AFAICT although I've personally never used them.  We should have those.

Cool. I think the only reason I hadn't implemented the  AssetId type yet was a lack of type aliases 😅. But now I think NewType is a better fit.

In Rust it looks a bit like a tuple and you index the inner with .0 (at zero cost).  I say I've never used them but they're everywhere in the IR for the context arenas, e.g., pub struct Block(pub generational_arena::Index);
So you either explicitly use .0 to 'unwrap' the newtype, or yeah you could use a simple from() but if you're passing the newtype to something that expects the inner type then explicit unwrapping is probably desirable?

It's called a tuple struct in rust (scroll down a bit on that page). We could add tuple structs in general, or we could keep using the named inner field pattern for newtypes, since it's the same thing but with a name instead of .0?

Bumping this :)

This is now done.


URL missing

The referenced ARM template does not exist in the specified link
'https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/101-app-configuration-store-kv/azuredeploy.json'

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

ID: 0000e043-0717-23d4-5d63-c5728919cda8
Version Independent ID: b8726c93-69e0-07d5-5bff-0b875dec00ab
Content: Create an Azure App Configuration store by using Azure Resource Manager template (ARM template) - Azure App Configuration
Content Source: articles/azure-app-configuration/quickstart-resource-manager.md
Service: azure-app-configuration
GitHub Login: @GrantMeStrength
Microsoft Alias: jken

@Gordonby Thanks for the feedback. We shall evaluate and update the document as appropriate.

@Gordonby Thanks for bringing this to our attention. I have submitted a PR to fix the issue that's in review.


Custom Styles

Component backgroundColor, grid lines color, done button text styles, footer presented as header component properties exposed to user.

Thanks @shahjahanpak


fyne navigation menu issues

When the fyne interface is launched, all the functions for rendering the different pages get invoked instead of when the appropriate tab/menu item is selected. See the calls to render all pages as soon as fyne is started here: https://github.com/raedahgroup/godcr/blob/master/fyne/pages/menu.go#L67-L74.
Admittedly, all the pages are not rendered simultaneously, but are pre-loaded. Clicking on the tab menu item only displays the pre-loaded content. Quite obviously not a good idea to preload page contents.

Visiting a page (say staking page), leaving to another page (say overview) and returning to the page previously visited does not cause the page to reload. There's a hack here https://github.com/raedahgroup/godcr/blob/master/fyne/pages/menu.go#L78-L91, which I've previously mentioned to be not okay - using a goroutine to refresh dynamic content on the active tab page every second. The recommended approach is to only trigger content reload when a tab menu item is activated/clicked.

A temporary fix to issue 2 above would be to track changes to the active tab index in that goroutine and only reload content if the tab index was actually changed; i.e. if I stay on tab 1 for 10 seconds, instead of reloading tab 1 content 10 times (for each second I remain on the tab), content should be reloaded only once.
Considering that it is not currently possible to load dynamic contents using fyne tab menus, I recommend changing the canvas item (view) used for the menu. Tabs require that the content for each page be loaded from the beginning and does not allow refreshing content when switching between pages.
An alternative to changing the canvas item (view) used for the menu would be to make changes to the TabContainer canvas object upstream or within godcr (extending TabContainer with additional helper methods perhaps) to account for the issues mentioned above.

Tabcontainer contents are all loaded on start and are static, to dynamically change content data, the go routine was used. I think updating contents only when users change tab doesnt just cut it imagine changing tabs repeatedly to check for a new transaction, when it's pending and when it's confirmed, mobile wallet doesnt have that feature godcr shouldn't.

Tabcontainer contents are all loaded on start and are static, to dynamically change content "data", the go routine was used, we are not reloading the selected tab every seconds it's quite obvious that doing that wont give users interactivity but rather we are updating selected data in the page.

My grammar was wrong, I agree that only some portion of the active page is being updated. My concern is with the frequency, refreshing/reloading some data on the active page every second is obviously a bad idea.

I think fetching contents only when users change tabs doesnt just cut it, imagine changing tabs repeatedly to check for a new transaction, when it's pending and when it's confirmed, mobile wallet doesnt have that feature godcr shouldn't.

Mobile wallets do not use a repeating 1-second timer to check for transaction updates. There is a better way to implement that feature - using transaction notification listener. Until such a time when this is implemented, it's very fine to switch tabs to get updated information. Definitely better than refreshing said information every second.
We can have an issue created to implement tx notification listener. It's something that can be done in a pretty small PR in a pretty short timeframe when needed.

Yes we both discussed about transaction notification listener function recently, tabcontainer doesn't support a calling function when a tab is changed, best thing to do is to implement a notification listener function instead. Would be lovely if you can create an issue on that instead.


fix(backend-version): role accepts latest with postfix

I think the scope for this commit should be params


Unable to launch debugger worker process

Issue Description
Unable to launch an external console under Fedora 30 and KDE desktop. This works fine on the same machine in gnome but not KDE. Both Konsole and gnome Terminal are installed.
More than happy to run any test and post any log on your request.
Your help is much appreciated.
Many thanks.
Steps to Reproduce
1- Create a dotnet core console app
2- Set "console" to "externalTerminal" in launch.json
3- Save the launch.json file
4- Try to run the app
Expected Behavior
A new terminal should open to allow output from app and input from the user.
Actual Behavior
A dialog is displayed stating the following message:
Unable to launch debugger worker process (vsdebug) through the terminal. can't find terminal application 'dumb'
Logs
OmniSharp log

Starting OmniSharp server at 16/07/2019, 05:22:12
    Target: /media/workspace/Projects/CSharp/DDD/VendingMachine
OmniSharp server started.
Path: /home/masoud/.vscode/extensions/ms-vscode.csharp-1.20.0/.omnisharp/1.32.20/run
PID: 10384
    Starting OmniSharp on fedora 30.0 (x64)

    DotNetPath set to dotnet

    Located 1 MSBuild instance(s)
        1: StandAlone 15.0 - "/home/masoud/.vscode/extensions/ms-vscode.csharp-1.20.0/.omnisharp/1.32.20/omnisharp/.msbuild/Current/Bin"

    MSBUILD_EXE_PATH environment variable set to '/home/masoud/.vscode/extensions/ms-vscode.csharp-1.20.0/.omnisharp/1.32.20/omnisharp/.msbuild/Current/Bin/MSBuild.dll'

    Registered MSBuild instance: StandAlone 15.0 - "/home/masoud/.vscode/extensions/ms-vscode.csharp-1.20.0/.omnisharp/1.32.20/omnisharp/.msbuild/Current/Bin"
        MSBuildExtensionsPath = /home/masoud/.vscode/extensions/ms-vscode.csharp-1.20.0/.omnisharp/1.32.20/omnisharp/.msbuild
        BypassFrameworkInstallChecks = true
        CscToolPath = /home/masoud/.vscode/extensions/ms-vscode.csharp-1.20.0/.omnisharp/1.32.20/omnisharp/.msbuild/Current/Bin/Roslyn
        CscToolExe = csc.exe
        MSBuildToolsPath = /home/masoud/.vscode/extensions/ms-vscode.csharp-1.20.0/.omnisharp/1.32.20/omnisharp/.msbuild/Current/Bin

    Detecting Cake files in '/media/workspace/Projects/CSharp/DDD/VendingMachine'.

    Could not find any Cake files

    Project system 'OmniSharp.DotNet.DotNetProjectSystem' is disabled in the configuration.

    No solution files found in '/media/workspace/Projects/CSharp/DDD/VendingMachine'

    Queue project update for '/media/workspace/Projects/CSharp/DDD/VendingMachine/VM.Logic/VM.Logic.csproj'

    Queue project update for '/media/workspace/Projects/CSharp/DDD/VendingMachine/VM.UI/VM.UI.csproj'

    Detecting CSX files in '/media/workspace/Projects/CSharp/DDD/VendingMachine'.

    Could not find any CSX files

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpWorkspaceOptionsProvider

    Loading project: /media/workspace/Projects/CSharp/DDD/VendingMachine/VM.Logic/VM.Logic.csproj

    Configuration finished.

    Omnisharp server running using Stdio at location '/media/workspace/Projects/CSharp/DDD/VendingMachine' on host 10244.

    Successfully loaded project file '/media/workspace/Projects/CSharp/DDD/VendingMachine/VM.Logic/VM.Logic.csproj'.

    Adding project '/media/workspace/Projects/CSharp/DDD/VendingMachine/VM.Logic/VM.Logic.csproj'

    Loading project: /media/workspace/Projects/CSharp/DDD/VendingMachine/VM.UI/VM.UI.csproj

    Successfully loaded project file '/media/workspace/Projects/CSharp/DDD/VendingMachine/VM.UI/VM.UI.csproj'.

    Adding project '/media/workspace/Projects/CSharp/DDD/VendingMachine/VM.UI/VM.UI.csproj'

    Update project: VM.Logic

    Update project: VM.UI

C# log
Looked for output from Output-->C# but it's empty
Environment information
VSCode version: 1.36.1
C# Extension: 1.20.0
Mono Information
        OmniSharp using built-in mono
Dotnet Information
.NET Core SDK (reflecting any global.json):
 Version:   2.2.301
 Commit:    70d6be0814
Runtime Environment:
OS Name:     fedora
OS Version:  30
OS Platform: Linux
RID:         fedora.30-x64
Base Path:   /usr/share/dotnet/sdk/2.2.301/
Host (useful for support):
Version: 2.2.6
Commit:  7dac9b1b51
.NET Core SDKs installed:
2.2.301 [/usr/share/dotnet/sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.2.6 [/usr/share/dotnet/shared/Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.2.6 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.2.6 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download

Visual Studio Code Extensions

Extension
Author
Version

beautify
HookyQR
1.5.0

cpptools
ms-vscode
0.24.0

csharp
ms-vscode
1.20.0

csharpextensions
jchannon
1.3.0

debugger-for-chrome
msjsdiag
4.11.6

docomment
k--kato
0.1.8

gitlens
eamodio
9.8.5

html-css-class-completion
Zignd
1.19.0

ng-template
Angular
0.800.0

npm-intellisense
christian-kohler
1.3.0

path-intellisense
christian-kohler
1.4.2

vs-keybindings
ms-vscode
0.2.0

vscode-html-css
ecmel
0.2.0

vscode-icons
vscode-icons-team
8.8.0

vsliveshare
ms-vsliveshare
1.0.509

vsliveshare-audio
ms-vsliveshare
0.1.59

Please see below my launch.json file:
{
    // Use IntelliSense to find out which attributes exist for C# debugging
    // Use hover for the description of the existing attributes
    // For further information visit https://github.com/OmniSharp/omnisharp-vscode/blob/master/debugger-launchjson.md
    "version": "0.2.0",
    "configurations": [{
            "name": ".NET Core Launch (console)",
            "type": "coreclr",
            "request": "launch",
            "preLaunchTask": "build",
            // If you have changed target frameworks, make sure to update the program path.
            "program": "${workspaceFolder}/VM.UI/bin/Debug/netcoreapp2.2/VM.UI.dll",
            "args": [],
            "cwd": "${workspaceFolder}/VM.UI",
            // For more information about the 'console' field, see https://aka.ms/VSCode-CS-LaunchJson-Console
            "console": "externalTerminal",
            "stopAtEntry": false
        },
        {
            "name": ".NET Core Attach",
            "type": "coreclr",
            "request": "attach",
            "processId": "${command:pickProcess}"
        }
    ]
}

Many many thanks.

Hi @mdx0111 the code that is failing is actually in VS Code rather than this extension. The C# extension is just reporting the error message that VS Code returns -- can't find terminal application 'dumb'.
I may need to pass you off to the VS Code repo for more help, but one thing to check is that in VS Code preferences you can set what external terminal you want to use. So you might see what that is configured to and if you can change it to something that works.

Hi Gregg,
You were absolutely right. It was VS Code that couldn't find the right terminal to use. For some reason that I don't understand, it was set to 'dumb'! I just changed it to KDE Konsole and the problem is resolved.
Many many thanks for your help.


fix: process event listeners are removed on stop

When the agent is started, a warning event listener is added
to process.  With this change, the listener is removed when
the agent is stopped.

Closed in favor of PR #376.


Matching HFNet features with superglue?

Hi, thank you for this code.
I am trying to use HFNet to detect features, and Superglue from this repo to match them, but I see very few matches, on two exactly matching images. I am doing:
(*mpExtractorLeft)(image, vKeyPoints, localDescriptors, globalDescriptors); //to extract features to cv::Keypoint / cv::Mat
Then:
//matching
    std::string config_path = "config.yaml";
    std::string model_dir = "weights";
    Configs configs(config_path, model_dir);
    std::cout << "Building inference engine......" << std::endl;

    Eigen::Matrix<double, 259, Eigen::Dynamic> feature_points0, feature_points1;
    std::vector<cv::DMatch> superglue_matches;

    //fill eigen from desc and keys
    //image 1
    feature_points0.resize(259, vKeyPoints.size());
    for (int i = 0; i < vKeyPoints.size(); i++) {
        feature_points0(0, i) = 1;
    }

    for (int j = 0; j < vKeyPoints.size(); ++j) {
        feature_points0(1, j) = vKeyPoints[j].pt.x;
        feature_points0(2, j) = vKeyPoints[j].pt.y;
    }

    for (int m = 3; m < 259; ++m) {
        for (int n = 0; n < localDescriptors.rows; ++n) //rows is kpnts size, cols is 256
        {
            feature_points0(n, m) = localDescriptors.at<double>(n,m);
        }
    }

    feature_points1 = feature_points0;

    auto superglue = std::make_shared<SuperGlue>(configs.superglue_config);
    if (!superglue->build()) {
        std::cerr << "Error in SuperGlue building engine. Please check your onnx model path." << std::endl;
        return 0;
    }
    auto start = std::chrono::high_resolution_clock::now();
    superglue->matching_points(feature_points0, feature_points1, superglue_matches,true);
    auto end = std::chrono::high_resolution_clock::now();
    auto duration = std::chrono::duration_cast<std::chrono::milliseconds>(end - start);

    std::cout << "matching took: " << duration.count() << std::endl;

from 712 features (the exact same image) I get 35 matches.
I assume that i am filling the matrix incorrectly. Can you see what I am doing wrong here?
Thank you!

Ah, normalizing the descriptors has this working for me.
void normalize_descriptors(std::vector<std::vector<double>>& dest_descriptors) {
    for (auto& descriptor : dest_descriptors) {
        double norm_inv = 1.0 / vector_normalize(descriptor.begin(), descriptor.end());
        std::transform(descriptor.begin(), descriptor.end(), descriptor.begin(),
            std::bind1st(std::multiplies<double>(), norm_inv));
    }
}

    std::vector<std::vector<double>> dest_descriptors;
    for (int n = 0; n < localDescriptors.rows; ++n) //rows is kpnts size, cols is 256
    {
        std::vector<double> v;
        localDescriptors.row(n).copyTo(v);
        dest_descriptors.push_back(v);
    }
    normalize_descriptors(dest_descriptors);

    feature_points0.resize(259, vKeyPoints.size());
    for (int i = 0; i < vKeyPoints.size(); i++) {
        feature_points0(0, i) = 1;
        feature_points0(1, i) = vKeyPoints[i].pt.x;
        feature_points0(2, i) = vKeyPoints[i].pt.y;
    }

    for (int m = 3; m < 259; ++m) {
        for (int n = 0; n < dest_descriptors.size(); ++n) {
            feature_points0(m, n) = dest_descriptors[n][m - 3];
        }
    }


Add Icon channel field

This field is used in DM group channels.

Please PR this into develop branch, thank you.

Thanks for the PR!


Added maven support

Added maven support, some files were moved,  old project can be still be run the "old" way.

Won't merge


infinite loading page on java or json creation

I deployed Apache camel karavan web application on minikube using maven and linked it with GitLab omnibus with nginx Infront to reverse proxy but whenever I create a java or Json file in the designer it loads infinitely.

and keep getting this result http code 204, logs not showing any error, what seems to be the problem.

To install Karavan on Kubernetes/Minikube please use Karavan CLI
https://github.com/apache/camel-karavan/blob/main/docs/WEB_INSTALL.md

To install Karavan on Kubernetes/Minikube please use Karavan CLI
https://github.com/apache/camel-karavan/blob/main/docs/WEB_INSTALL.md

I already did install it, and it is working, but the issue is with java and JSON file creation which stuck in infinite loading.

Does it work without nginx reverse proxy?

no actually same issue

Any assistance would be highly appreciated.

Does Integration creation work? Only Java file creation causes issue?
Any errors in the Karavan-web container log?

Mr.@mgubaidullin I really appreciate your assistance.
Integration create works fine, not only Java file creation but also OpenApi Json and Yaml makes the same behavior, and there are no errors in the container log as below:
2023-08-28 16:26:29,948 INFO  [io.qua.sma.ope.run.OpenApiRecorder] (main) CORS filtering is disabled and cross-origin resource sharing is allowed without restriction, which is not recommended in production. Please configure the CORS filter through 'quarkus.http.cors.*' properties. For more information, see Quarkus HTTP CORS documentation
2023-08-28 16:26:30,145 INFO  [org.apa.cam.kar.ser.KaravanService] (main) Start Karavan
2023-08-28 16:26:30,211 INFO  [org.apa.cam.kar.ser.KaravanService] (main) InfinispanService is starting in local mode
2023-08-28 16:26:30,727 INFO  [org.inf.CONTAINER] (main) ISPN000389: Loaded global state, version=14.0.6.Final timestamp=2023-08-28T16:26:24.942646Z
2023-08-28 16:26:30,893 INFO  [org.inf.CONTAINER] (main) ISPN000556: Starting user marshaller 'org.infinispan.commons.marshall.ImmutableProtoStreamMarshaller'
2023-08-28 16:26:31,043 INFO  [org.inf.CLUSTER] (main) ISPN000088: Unable to use any JGroups configuration mechanisms provided in properties {}. Using default JGroups configuration!
2023-08-28 16:26:31,253 INFO  [org.inf.CLUSTER] (main) ISPN000078: Starting JGroups channel ISPN
2023-08-28 16:26:31,268 INFO  [org.jgr.JChannel] (main) local_addr: 97e37916-e44c-4c72-92ac-2925bafd30a7, name: karavan-6bfb65b5b-7zj86-42276
2023-08-28 16:26:31,278 WARN  [org.jgr.pro.UDP] (main) JGRP000015: the receive buffer of socket MulticastSocket was set to 20MB, but the OS only allocated 212.99KB
2023-08-28 16:26:31,278 WARN  [org.jgr.pro.UDP] (main) JGRP000015: the receive buffer of socket MulticastSocket was set to 25MB, but the OS only allocated 212.99KB
2023-08-28 16:26:31,292 INFO  [org.jgr.pro.FD_SOCK2] (main) server listening on *.28123
2023-08-28 16:26:33,298 INFO  [org.jgr.pro.pbc.GMS] (main) karavan-6bfb65b5b-7zj86-42276: no members discovered after 2003 ms: creating cluster as coordinator
2023-08-28 16:26:33,309 INFO  [org.inf.CLUSTER] (main) ISPN000094: Received new cluster view for channel ISPN: [karavan-6bfb65b5b-7zj86-42276|0] (1) [karavan-6bfb65b5b-7zj86-42276]
2023-08-28 16:26:33,333 INFO  [org.inf.CLUSTER] (main) ISPN000079: Channel ISPN local address is karavan-6bfb65b5b-7zj86-42276, physical addresses are [<IP_ADDRESS>:43659]
2023-08-28 16:26:33,995 WARN  [org.inf.CONFIG] (main) ISPN000595: ClusterLoader has been deprecated and will be removed in a future version with no direct replacement
2023-08-28 16:26:34,201 WARN  [org.inf.CONFIG] (main) ISPN000595: ClusterLoader has been deprecated and will be removed in a future version with no direct replacement
2023-08-28 16:26:34,244 WARN  [org.inf.CONFIG] (main) ISPN000595: ClusterLoader has been deprecated and will be removed in a future version with no direct replacement
2023-08-28 16:26:34,282 WARN  [org.inf.CONFIG] (main) ISPN000595: ClusterLoader has been deprecated and will be removed in a future version with no direct replacement
2023-08-28 16:26:34,299 WARN  [org.inf.CONFIG] (main) ISPN000595: ClusterLoader has been deprecated and will be removed in a future version with no direct replacement
2023-08-28 16:26:34,312 WARN  [org.inf.CONFIG] (main) ISPN000595: ClusterLoader has been deprecated and will be removed in a future version with no direct replacement
2023-08-28 16:26:34,361 WARN  [org.inf.CONFIG] (main) ISPN000595: ClusterLoader has been deprecated and will be removed in a future version with no direct replacement
2023-08-28 16:26:34,382 WARN  [org.inf.CONFIG] (main) ISPN000595: ClusterLoader has been deprecated and will be removed in a future version with no direct replacement
2023-08-28 16:26:34,394 WARN  [org.inf.CONFIG] (main) ISPN000595: ClusterLoader has been deprecated and will be removed in a future version with no direct replacement
2023-08-28 16:26:34,408 WARN  [org.inf.CONFIG] (main) ISPN000595: ClusterLoader has been deprecated and will be removed in a future version with no direct replacement
2023-08-28 16:26:35,340 INFO  [org.apa.cam.kar.ser.KubernetesService] (executor-thread-1) Stop Kubernetes Informers
2023-08-28 16:26:35,341 INFO  [org.apa.cam.kar.ser.KubernetesService] (executor-thread-1) Starting Kubernetes Informers
2023-08-28 16:26:35,453 INFO  [org.apa.cam.kar.ser.ProjectService] (executor-thread-0) Add templates project if not exists
2023-08-28 16:26:35,454 INFO  [org.apa.cam.kar.ser.ProjectService] (executor-thread-0) Import commits...
2023-08-28 16:26:35,456 INFO  [org.apa.cam.kar.ser.GitService] (executor-thread-0) Git checkout
2023-08-28 16:26:35,457 INFO  [org.apa.cam.kar.ser.GitService] (executor-thread-0) inKubernetes karavan
2023-08-28 16:26:35,992 INFO  [io.quarkus] (main) karavan 3.21.0 on JVM (powered by Quarkus 2.16.7.Final) started in 9.022s. Listening on: http://<IP_ADDRESS>:8080
2023-08-28 16:26:35,995 INFO  [io.quarkus] (main) Profile public activated.
2023-08-28 16:26:35,995 INFO  [io.quarkus] (main) Installed features: [cdi, infinispan-client, jgit, jsch, kubernetes, kubernetes-client, oidc, openshift-client, quinoa, qute, resteasy-reactive, resteasy-reactive-jackson, scheduler, security, security-properties-file, smallrye-context-propagation, smallrye-fault-tolerance, smallrye-health, smallrye-openapi, smallrye-reactive-messaging, swagger-ui, vertx]
2023-08-28 16:26:36,541 INFO  [org.apa.cam.kar.ser.GitService] (executor-thread-0) Temp folder created /tmp/import9903535921224121253
2023-08-28 16:26:38,269 WARN  [io.fab.kub.cli.dsl.int.VersionUsageUtils] (executor-thread-1) The client is using resource type 'pipelineruns' with unstable version 'v1beta1'
2023-08-28 16:26:38,949 INFO  [org.apa.cam.kar.han.PipelineRunEventHandler] (executor-thread-1) onAdd karavan-bassem-project-hwncj
2023-08-28 16:26:39,341 INFO  [org.apa.cam.kar.ser.KubernetesService] (executor-thread-1) Started Kubernetes Informers

What version have you installed?

Could you please try to create custom Java processor from integration like in this video (starts at 4:15): https://youtu.be/trsZyzEvbWw?feature=shared&t=255
Does it work?

infact no it faces the same issue

What version have you installed?

maven-dependency-plugin: 3.0.2
apache.camel.karavan:karavan-cli: 3.21.0 jar

Do you have templates folder in your git repository?

Do you have templates folder in your git repository?

I didn't have it, but I added it and tried and still the same issue.

Hello MR.@mgubaidullin I want to inform you that I did install Karavan web app again on a new CentOS 7 server following the documentation and using the Apache Maven 3.9.4, Java version: 17.0.2 and Minikube version: v1.31.2 and am still facing the same issue

Can you share Karavan container log?

The only thing I am missing is the oidc-server is it crucial for the Karavan functionality?

Can you share Karavan container log?

Here you go:
k logs -f karavan-6bfb65b5b-fcvw8
2023-08-31 11:02:54,670 INFO  [io.qua.sma.ope.run.OpenApiRecorder] (main) CORS filtering is disabled and cross-origin resource sharing is allowed without restriction, which is not recommended in production. Please configure the CORS filter through 'quarkus.http.cors.*' properties. For more information, see Quarkus HTTP CORS documentation
2023-08-31 11:02:54,842 INFO  [org.apa.cam.kar.ser.KaravanService] (main) Start Karavan
2023-08-31 11:02:54,900 INFO  [org.apa.cam.kar.ser.KaravanService] (main) InfinispanService is starting in local mode
2023-08-31 11:02:55,392 INFO  [org.inf.CONTAINER] (main) ISPN000389: Loaded global state, version=14.0.6.Final timestamp=2023-08-31T11:02:49.837984Z
2023-08-31 11:02:55,554 INFO  [org.inf.CONTAINER] (main) ISPN000556: Starting user marshaller 'org.infinispan.commons.marshall.ImmutableProtoStreamMarshaller'
2023-08-31 11:02:55,738 INFO  [org.inf.CLUSTER] (main) ISPN000088: Unable to use any JGroups configuration mechanisms provided in properties {}. Using default JGroups configuration!
2023-08-31 11:02:55,956 INFO  [org.inf.CLUSTER] (main) ISPN000078: Starting JGroups channel ISPN
2023-08-31 11:02:55,971 INFO  [org.jgr.JChannel] (main) local_addr: e1b02794-cf70-4520-b549-5296a171887a, name: karavan-6bfb65b5b-fcvw8-54876
2023-08-31 11:02:55,978 WARN  [org.jgr.pro.UDP] (main) JGRP000015: the send buffer of socket MulticastSocket was set to 1MB, but the OS only allocated 212.99KB
2023-08-31 11:02:55,978 WARN  [org.jgr.pro.UDP] (main) JGRP000015: the receive buffer of socket MulticastSocket was set to 20MB, but the OS only allocated 212.99KB
2023-08-31 11:02:55,979 WARN  [org.jgr.pro.UDP] (main) JGRP000015: the send buffer of socket MulticastSocket was set to 1MB, but the OS only allocated 212.99KB
2023-08-31 11:02:55,980 WARN  [org.jgr.pro.UDP] (main) JGRP000015: the receive buffer of socket MulticastSocket was set to 25MB, but the OS only allocated 212.99KB
2023-08-31 11:02:56,008 INFO  [org.jgr.pro.FD_SOCK2] (main) server listening on *.41681
2023-08-31 11:02:58,045 INFO  [org.jgr.pro.pbc.GMS] (main) karavan-6bfb65b5b-fcvw8-54876: no members discovered after 2006 ms: creating cluster as coordinator
2023-08-31 11:02:58,056 INFO  [org.inf.CLUSTER] (main) ISPN000094: Received new cluster view for channel ISPN: [karavan-6bfb65b5b-fcvw8-54876|0] (1) [karavan-6bfb65b5b-fcvw8-54876]
2023-08-31 11:02:58,074 INFO  [org.inf.CLUSTER] (main) ISPN000079: Channel ISPN local address is karavan-6bfb65b5b-fcvw8-54876, physical addresses are [<IP_ADDRESS>:57217]
2023-08-31 11:02:58,789 WARN  [org.inf.CONFIG] (main) ISPN000595: ClusterLoader has been deprecated and will be removed in a future version with no direct replacement
2023-08-31 11:02:59,016 WARN  [org.inf.CONFIG] (main) ISPN000595: ClusterLoader has been deprecated and will be removed in a future version with no direct replacement
2023-08-31 11:02:59,061 WARN  [org.inf.CONFIG] (main) ISPN000595: ClusterLoader has been deprecated and will be removed in a future version with no direct replacement
2023-08-31 11:02:59,080 WARN  [org.inf.CONFIG] (main) ISPN000595: ClusterLoader has been deprecated and will be removed in a future version with no direct replacement
2023-08-31 11:02:59,095 WARN  [org.inf.CONFIG] (main) ISPN000595: ClusterLoader has been deprecated and will be removed in a future version with no direct replacement
2023-08-31 11:02:59,138 WARN  [org.inf.CONFIG] (main) ISPN000595: ClusterLoader has been deprecated and will be removed in a future version with no direct replacement
2023-08-31 11:02:59,157 WARN  [org.inf.CONFIG] (main) ISPN000595: ClusterLoader has been deprecated and will be removed in a future version with no direct replacement
2023-08-31 11:02:59,170 WARN  [org.inf.CONFIG] (main) ISPN000595: ClusterLoader has been deprecated and will be removed in a future version with no direct replacement
2023-08-31 11:02:59,182 WARN  [org.inf.CONFIG] (main) ISPN000595: ClusterLoader has been deprecated and will be removed in a future version with no direct replacement
2023-08-31 11:02:59,348 WARN  [org.inf.CONFIG] (main) ISPN000595: ClusterLoader has been deprecated and will be removed in a future version with no direct replacement
2023-08-31 11:02:59,973 INFO  [org.apa.cam.kar.ser.KubernetesService] (executor-thread-0) Stop Kubernetes Informers
2023-08-31 11:02:59,977 INFO  [org.apa.cam.kar.ser.KubernetesService] (executor-thread-0) Starting Kubernetes Informers
2023-08-31 11:03:00,173 INFO  [org.apa.cam.kar.ser.ProjectService] (executor-thread-1) Add templates project if not exists
2023-08-31 11:03:00,174 INFO  [org.apa.cam.kar.ser.ProjectService] (executor-thread-1) Import commits...
2023-08-31 11:03:00,175 INFO  [org.apa.cam.kar.ser.GitService] (executor-thread-1) Git checkout
2023-08-31 11:03:00,180 INFO  [org.apa.cam.kar.ser.GitService] (executor-thread-1) inKubernetes karavan
2023-08-31 11:03:00,276 INFO  [io.quarkus] (main) karavan 3.21.0 on JVM (powered by Quarkus 2.16.7.Final) started in 8.018s. Listening on: http://<IP_ADDRESS>:8080
2023-08-31 11:03:00,277 INFO  [io.quarkus] (main) Profile public activated.
2023-08-31 11:03:00,277 INFO  [io.quarkus] (main) Installed features: [cdi, infinispan-client, jgit, jsch, kubernetes, kubernetes-client, oidc, openshift-client, quinoa, qute, resteasy-reactive, resteasy-reactive-jackson, scheduler, security, security-properties-file, smallrye-context-propagation, smallrye-fault-tolerance, smallrye-health, smallrye-openapi, smallrye-reactive-messaging, swagger-ui, vertx]
2023-08-31 11:03:00,700 INFO  [org.apa.cam.kar.ser.GitService] (executor-thread-1) Temp folder created /tmp/import9546624777898388738
2023-08-31 11:03:01,952 WARN  [io.fab.kub.cli.dsl.int.VersionUsageUtils] (executor-thread-0) The client is using resource type 'pipelineruns' with unstable version 'v1beta1'
2023-08-31 11:03:02,632 INFO  [org.apa.cam.kar.ser.KubernetesService] (executor-thread-0) Started Kubernetes Informers
2023-08-31 11:03:04,156 ERROR [org.apa.cam.kar.ser.GitService] (executor-thread-1) New repository
2023-08-31 11:03:04,197 ERROR [org.apa.cam.kar.ser.GitService] (executor-thread-1) No HEAD exists and no explicit starting revision was specified
this log is after I created and pushed the below files

all files are empty on the GitLab and infinitely loading on karavan

@mgubaidullin any updates kindly.

Try Karavan 4.0.0

Thanks, @mgubaidullin Java files working fine now, but I believe there is a bug in the knowledge section as mini window keeps popping up even when I close it multiple times as you can see below:


[Hub Generated] Review request for Microsoft.Maps/Microsoft.Maps to add version preview/2.0

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
[ ] Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

@rasub2: we have new client structure merged in https://github.com/Azure/azure-rest-api-specs/pull/14871, should we proceed with merging this update into https://github.com/Azure/azure-rest-api-specs/blob/master/specification/maps/data-plane/Render/preview/2.0/render.json ?

@rasub2, @chgennar: is this superseded by https://github.com/Azure/azure-rest-api-specs/pull/14625/files

@rasub2, @chgennar: Should we close this one, is this superseded by #14625?

Yes, this work was carried over into the merged PR.


[TRT]    Could not register plugin creator -  ::FlattenConcat_TRT version 1

I am using the video tutorial on Youtube to develop my first real time object detection. When I try to run the script, the following error show up [TRT]    Could not register plugin creator -  ::FlattenConcat_TRT version 1
After the error, the camera never turns on and the terminal keeps on spitting values like this:
After concat removal: 66 layers
[TRT]    Graph construction and optimization completed in 0.045886 seconds.
[TRT]    Constructing optimization profile number 0 [1/1].
[TRT]    --------------- Timing Runner:  (Reformat)
[TRT]    Tactic: 1002 time 0.747864
[TRT]    Tactic: 0 time 1.23659
[TRT]    Fastest Tactic: 1002 Time: 0.747864
[TRT]    --------------- Timing Runner:  (Reformat)
[TRT]    Tactic: 1002 time 20.0891
[TRT]    Tactic: 0 time 1.31471
[TRT]    Fastest Tactic: 0 Time: 1.31471
Has anyone come up with the same issue and knows how to fix it? I'm running the script on the Jetson Nano 4GB Development kit with Jetpack 4.4 installed and using the Raspberry Pi Camera V2.
This is the actual script:
import jetson.utils

net = jetson.inference.detectNet("coco-dog", threshold=0.5)
camera = jetson.utils.videoSource("csi://0")      # '/dev/video0' for V4L2
display = jetson.utils.videoOutput("display://0") # 'my_video.mp4' for file

while display.IsStreaming():
        img = camera.Capture()
        detections = net.Detect(img)
        display.Render(img)
        display.SetStatus("Object Detection | Network {:.0f} FPS".format(net.GetNetworkFPS()))```

When I try to run the script, the following error show up [TRT] Could not register plugin creator - ::FlattenConcat_TRT version 1

Hi @naimulhq , you can ignore that warning.

After the error, the camera never turns on and the terminal keeps on spitting values like this:

It is normal the first time that you load a model, it will take some minutes for TensorRT to optimize the model.  It should only happen the first time that you run each model, because the optimized model gets cached to disk.   If you let it run for a while it should complete the optimizations and then start the camera normally.

Hi @dusty-nv
I did that and everything ran smoothly. Thank you for the help!

Had the same issue, was about to complain but found this. Thanks so much for this repo and your video. It really helps a lot to have a first contact with the entire material.
@dusty-nv Do you have a link list of other videos you made? You mentioned that you want to provide another video w.r.t. PyTorch, is it available somewhere?
Thanks a lot for all your work. Very much appreciated. I came from a Raspberry PI 4B/Coral TPU solution and wanted to check, if the Jetson Nano with its GPU is a competitor. I need to infer from 3 cameras simultaneoulsy, will check the next days, how the Jetson and your project performs here.
BTW: Is the camera capturer thread-safe?

Had the same issue, was about to complain but found this. Thanks so much for this repo and your video. It really helps a lot to have a first contact with the entire material.
@dusty-nv Do you have a link list of other videos you made? You mentioned that you want to provide another video w.r.t. PyTorch, is it available somewhere?
Thanks a lot for all your work. Very much appreciated. I came from a Raspberry PI 4B/Coral TPU solution and wanted to check, if the Jetson Nano with its GPU is a competitor. I need to infer from 3 cameras simultaneoulsy, will check the next days, how the Jetson and your project performs here.
BTW: Is the camera capturer thread-safe?

Hi @neilyoung , you can find all the screencast videos for Hello AI World here:
https://github.com/dusty-nv/jetson-inference#video-walkthroughs

Hi @neilyoung , you can find all the screencast videos for Hello AI World here:
https://github.com/dusty-nv/jetson-inference#video-walkthroughs

Hi@dusty-nv，when i try to run "./imagenet images/orange_0.jpg images/test/output_0.jpg" , the following error show up:
...
[TRT]    Could not register plugin creator -  ::FlattenConcat_TRT version 1
...
[TRT]    2: [utils.cpp::checkMemLimit::380] Error Code 2: Internal Error (Assertion upperBound != 0 failed. Unknown embedded device detected. Please update the table with the entry: {{1794, 6, 16}, 12653},)
[TRT]    device GPU, failed to build CUDA engine
[TRT]    device GPU, failed to load networks/bvlc_googlenet.caffemodel
[TRT]    failed to load networks/bvlc_googlenet.caffemodel
[TRT]    imageNet -- failed to initialize.
imagenet:  failed to initialize imageNet
Could you help me to solve the problem?


🐛 [firebase_messaging] Serious issue: on Android requestPermission() causes an exception

Bug report
Describe the bug
First of all I want to mention that I know about #9904. But this one is already closed without any real solution.
I've recently updated firebase plugins to the latest version, and released the app:
  firebase_core: ^2.8.0
  firebase_analytics: ^10.1.6
  firebase_crashlytics: ^3.0.17
  firebase_messaging: ^14.3.0
  firebase_remote_config: ^3.0.15
  flutter_local_notifications: ^13.0.0 # just in case, my app also depends on this plugin

Previously, I used a combination with firebase_messaging 12.0.1. That version didn't handle Android 13 notifications.
During the app startup I call:
firebaseMessaging.requestPermission();

Just to show the permission popup for users with Android 13. I thought it's a no-op for older versions.
After running a new release for 2 days, I see this report in Firebase Crashlytics console:

Here is the stack trace for devices with Android versions less than 13:
Fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError: [firebase_messaging/unknown] Attempt to invoke virtual method 'java.lang.Object android.content.Context.getSystemService(java.lang.String)' on a null object reference
#00 pc 0x60f337 com.*** (StandardMethodCodec.decodeEnvelope [message_codecs.dart:653]) (BuildId: bca64abfc2bc13d631bb8f1c8a3224fd)
#01 pc 0x648827 com.*** (MethodChannel._invokeMethod [platform_channel.dart:315]) (BuildId: bca64abfc2bc13d631bb8f1c8a3224fd)
#02 pc 0x626167 com.*** (_SuspendState._createAsyncStarCallback.<anonymous closure> [async_patch.dart:353]) (BuildId: bca64abfc2bc13d631bb8f1c8a3224fd)
#03 pc 0x26074f com.*** (_FutureListener.handleValue [zone.dart:1660]) (BuildId: bca64abfc2bc13d631bb8f1c8a3224fd)
#04 pc 0x64cd0f com.*** (Future._propagateToListeners.handleValueCallback [future_impl.dart:767]) (BuildId: bca64abfc2bc13d631bb8f1c8a3224fd)
#05 pc 0x25c2cf com.*** (Future._propagateToListeners [future_impl.dart:796]) (BuildId: bca64abfc2bc13d631bb8f1c8a3224fd)
#06 pc 0x25d503 com.*** (Future._completeWithValue [future_impl.dart:567]) (BuildId: bca64abfc2bc13d631bb8f1c8a3224fd)
#07 pc 0x25d463 com.*** (Future._asyncCompleteWithValue.<anonymous closure> [future_impl.dart:640]) (BuildId: bca64abfc2bc13d631bb8f1c8a3224fd)
#08 pc 0x25cd47 com.*** (_microtaskLoop [schedule_microtask.dart:40]) (BuildId: bca64abfc2bc13d631bb8f1c8a3224fd)
#09 pc 0x64b5e7 com.*** (_startMicrotaskLoop [schedule_microtask.dart:49]) (BuildId: bca64abfc2bc13d631bb8f1c8a3224fd)
#10 pc 0x25ccbb com.*** (_startMicrotaskLoop [schedule_microtask.dart:44]) (BuildId: bca64abfc2bc13d631bb8f1c8a3224fd)

And this is a stack trace for devices with Android 13:
Fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError: [firebase_messaging/unknown] Unable to detect current Android Activity.
#00 pc 0x60f337 com.*** (StandardMethodCodec.decodeEnvelope [message_codecs.dart:653]) (BuildId: bca64abfc2bc13d631bb8f1c8a3224fd)
#01 pc 0x648827 com.*** (MethodChannel._invokeMethod [platform_channel.dart:315]) (BuildId: bca64abfc2bc13d631bb8f1c8a3224fd)
#02 pc 0x626167 com.*** (_SuspendState._createAsyncStarCallback.<anonymous closure> [async_patch.dart:353]) (BuildId: bca64abfc2bc13d631bb8f1c8a3224fd)
#03 pc 0x26074f com.*** (_FutureListener.handleValue [zone.dart:1660]) (BuildId: bca64abfc2bc13d631bb8f1c8a3224fd)
#04 pc 0x64cd0f com.*** (Future._propagateToListeners.handleValueCallback [future_impl.dart:767]) (BuildId: bca64abfc2bc13d631bb8f1c8a3224fd)
#05 pc 0x25c2cf com.*** (Future._propagateToListeners [future_impl.dart:796]) (BuildId: bca64abfc2bc13d631bb8f1c8a3224fd)
#06 pc 0x25d503 com.*** (Future._completeWithValue [future_impl.dart:567]) (BuildId: bca64abfc2bc13d631bb8f1c8a3224fd)
#07 pc 0x25d463 com.*** (Future._asyncCompleteWithValue.<anonymous closure> [future_impl.dart:640]) (BuildId: bca64abfc2bc13d631bb8f1c8a3224fd)
#08 pc 0x25cd47 com.*** (_microtaskLoop [schedule_microtask.dart:40]) (BuildId: bca64abfc2bc13d631bb8f1c8a3224fd)
#09 pc 0x64b5e7 com.*** (_startMicrotaskLoop [schedule_microtask.dart:49]) (BuildId: bca64abfc2bc13d631bb8f1c8a3224fd)
#10 pc 0x25ccbb com.*** (_startMicrotaskLoop [schedule_microtask.dart:44]) (BuildId: bca64abfc2bc13d631bb8f1c8a3224fd)

So, I'm afraid there is a serious issue with the requestPermission() implementation.
Steps to reproduce
Sorry, I can't reproduce any bug on my environment. Emulators don't show it, and my phone has Android 13.
Expected behavior
requestPermission() works without any exception
Sample project

Additional context
Just in case, my app also depends on flutter_local_notificaions

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
[✓] Flutter (Channel stable, 3.7.9, on macOS 12.6.3 21G419 darwin-x64, locale en)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.1)
[✓] VS Code (version 1.52.1)
[✓] Connected device (3 available)
[✓] HTTP Host Availability

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 2.19.6
Flutter SDK 3.7.9
noname 3.6.0+3006000

dependencies:
- animations 2.0.7 [flutter]
- app_settings 4.2.0 [flutter]
- audio_service 0.18.9 [audio_service_platform_interface audio_service_web audio_session rxdart flutter_cache_manager clock js flutter flutter_web_plugins]
- audio_session 0.1.13 [flutter flutter_web_plugins rxdart meta]
- equatable 2.0.5 [collection meta]
- firebase_analytics 10.1.6 [firebase_analytics_platform_interface firebase_analytics_web firebase_core firebase_core_platform_interface flutter]
- firebase_core 2.8.0 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_crashlytics 3.0.17 [firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface flutter stack_trace]
- firebase_messaging 14.3.0 [firebase_core firebase_core_platform_interface firebase_messaging_platform_interface firebase_messaging_web flutter meta]
- firebase_remote_config 3.0.15 [firebase_core firebase_core_platform_interface firebase_remote_config_platform_interface firebase_remote_config_web flutter]
- flutter 0.0.0 [characters collection js material_color_utilities meta vector_math sky_engine]
- flutter_local_notifications 13.0.0 [clock flutter flutter_local_notifications_linux flutter_local_notifications_platform_interface timezone]
- flutter_localizations 0.0.0 [flutter intl characters clock collection js material_color_utilities meta path vector_math]
- flutter_riverpod 1.0.4 [collection flutter meta riverpod state_notifier]
- flutter_timezone 1.0.4 [flutter_web_plugins flutter js]
- get_it 7.2.0 [async collection]
- in_app_purchase 3.1.5 [flutter in_app_purchase_android in_app_purchase_platform_interface in_app_purchase_storekit]
- in_app_purchase_android 0.2.4+3 [collection flutter in_app_purchase_platform_interface json_annotation]
- intl 0.17.0 [clock path]
- keep_screen_on 2.1.0 [flutter keep_screen_on_platform_interface]
- launch_review 3.0.1 [flutter]
- meta 1.8.0
- package_info 2.0.2 [flutter]
- path 1.8.2
- path_provider 2.0.14 [flutter path_provider_android path_provider_foundation path_provider_linux path_provider_platform_interface path_provider_windows]
- pointycastle 3.7.1 [collection convert js]
- share_plus 6.3.1 [cross_file meta mime flutter flutter_web_plugins share_plus_platform_interface file url_launcher_web url_launcher_windows url_launcher_linux url_launcher_platform_interface ffi win32]
- sqflite 2.2.6 [flutter sqflite_common path]
- synchronized 3.0.1
- timezone 0.9.1 [path]
- url_launcher 6.1.10 [flutter url_launcher_android url_launcher_ios url_launcher_linux url_launcher_macos url_launcher_platform_interface url_launcher_web url_launcher_windows]

dev dependencies:
- flutter_driver 0.0.0 [file flutter flutter_test fuchsia_remote_debug_protocol path meta vm_service webdriver archive async boolean_selector characters clock collection crypto js matcher material_color_utilities platform process source_span stack_trace stream_channel string_scanner sync_http term_glyph test_api typed_data vector_math]
- flutter_lints 2.0.1 [lints]
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters collection js matcher material_color_utilities meta source_span stream_channel string_scanner term_glyph]
- test 1.22.0 [analyzer async boolean_selector collection coverage http_multi_server io js node_preamble package_config path pool shelf shelf_packages_handler shelf_static shelf_web_socket source_span stack_trace stream_channel typed_data web_socket_channel webkit_inspection_protocol yaml test_api test_core]

transitive dependencies:
- _fe_analyzer_shared 57.0.0 [meta]
- _flutterfire_internals 1.0.18 [collection firebase_core firebase_core_platform_interface flutter meta]
- analyzer 5.9.0 [_fe_analyzer_shared collection convert crypto glob meta package_config path pub_semver source_span watcher yaml]
- archive 3.3.2 [crypto path]
- args 2.4.0
- async 2.10.0 [collection meta]
- audio_service_platform_interface 0.1.0 [flutter plugin_platform_interface meta]
- audio_service_web 0.1.1 [audio_service_platform_interface rxdart js flutter flutter_web_plugins]
- boolean_selector 2.1.1 [source_span string_scanner]
- characters 1.2.1
- clock 1.1.1
- collection 1.17.0
- convert 3.1.1 [typed_data]
- coverage 1.6.3 [args logging package_config path source_maps stack_trace vm_service]
- cross_file 0.3.3+4 [js meta]
- crypto 3.0.2 [typed_data]
- dbus 0.7.8 [args ffi meta xml]
- fake_async 1.3.1 [clock collection]
- ffi 2.0.1
- file 6.1.4 [meta path]
- firebase_analytics_platform_interface 3.3.23 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_analytics_web 0.5.1+14 [_flutterfire_internals firebase_analytics_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- firebase_core_platform_interface 4.5.3 [collection flutter flutter_test meta plugin_platform_interface]
- firebase_core_web 2.2.2 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_crashlytics_platform_interface 3.3.17 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_platform_interface 4.2.16 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_web 3.2.17 [_flutterfire_internals firebase_core firebase_core_web firebase_messaging_platform_interface flutter flutter_web_plugins js meta]
- firebase_remote_config_platform_interface 1.1.35 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_remote_config_web 1.1.24 [firebase_core firebase_core_web firebase_remote_config_platform_interface flutter flutter_web_plugins js]
- flutter_cache_manager 3.3.0 [clock collection file flutter http path path_provider pedantic rxdart sqflite uuid]
- flutter_local_notifications_linux 3.0.0+1 [dbus ffi flutter flutter_local_notifications_platform_interface path xdg_directories]
- flutter_local_notifications_platform_interface 6.0.0 [flutter plugin_platform_interface]
- flutter_web_plugins 0.0.0 [flutter js characters collection material_color_utilities meta vector_math]
- frontend_server_client 3.2.0 [async path]
- fuchsia_remote_debug_protocol 0.0.0 [process vm_service file meta path platform]
- glob 2.1.1 [async collection file path string_scanner]
- http 0.13.5 [async http_parser meta path]
- http_multi_server 3.2.1 [async]
- http_parser 4.0.2 [collection source_span string_scanner typed_data]
- in_app_purchase_platform_interface 1.3.3 [flutter plugin_platform_interface]
- in_app_purchase_storekit 0.3.6+2 [collection flutter in_app_purchase_platform_interface json_annotation]
- io 1.0.4 [meta path string_scanner]
- js 0.6.5 [meta]
- json_annotation 4.8.0 [meta]
- keep_screen_on_platform_interface 2.0.0+1 [flutter plugin_platform_interface]
- lints 2.0.1
- logging 1.1.1
- matcher 0.12.13 [meta stack_trace]
- material_color_utilities 0.2.0
- mime 1.0.4
- node_preamble 2.0.2
- package_config 2.1.0 [path]
- path_provider_android 2.0.24 [flutter path_provider_platform_interface]
- path_provider_foundation 2.2.0 [flutter path_provider_platform_interface]
- path_provider_linux 2.1.10 [ffi flutter path path_provider_platform_interface xdg_directories]
- path_provider_platform_interface 2.0.6 [flutter platform plugin_platform_interface]
- path_provider_windows 2.1.5 [ffi flutter path path_provider_platform_interface win32]
- pedantic 1.11.1
- petitparser 5.1.0 [meta]
- platform 3.1.0
- plugin_platform_interface 2.1.4 [meta]
- pool 1.5.1 [async stack_trace]
- process 4.2.4 [file path platform]
- pub_semver 2.1.3 [collection meta]
- riverpod 1.0.3 [collection meta state_notifier]
- rxdart 0.27.7
- share_plus_platform_interface 3.2.0 [cross_file flutter meta mime plugin_platform_interface path_provider uuid]
- shelf 1.4.0 [async collection http_parser path stack_trace stream_channel]
- shelf_packages_handler 3.0.1 [path shelf shelf_static]
- shelf_static 1.1.1 [convert http_parser mime path shelf]
- shelf_web_socket 1.0.3 [shelf stream_channel web_socket_channel]
- sky_engine 0.0.99
- source_map_stack_trace 2.1.1 [path source_maps stack_trace]
- source_maps 0.10.12 [source_span]
- source_span 1.9.1 [collection path term_glyph]
- sqflite_common 2.4.3 [synchronized path meta]
- stack_trace 1.11.0 [path]
- state_notifier 0.7.2+1 [meta]
- stream_channel 2.1.1 [async]
- string_scanner 1.2.0 [source_span]
- sync_http 0.3.1
- term_glyph 1.2.1
- test_api 0.4.16 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph matcher]
- test_core 0.4.20 [analyzer async args boolean_selector collection coverage frontend_server_client glob io meta package_config path pool source_map_stack_trace source_maps source_span stack_trace stream_channel vm_service yaml matcher test_api]
- typed_data 1.3.1 [collection]
- url_launcher_android 6.0.26 [flutter url_launcher_platform_interface]
- url_launcher_ios 6.1.3 [flutter url_launcher_platform_interface]
- url_launcher_linux 3.0.4 [flutter url_launcher_platform_interface]
- url_launcher_macos 3.0.4 [flutter url_launcher_platform_interface]
- url_launcher_platform_interface 2.1.2 [flutter plugin_platform_interface]
- url_launcher_web 2.0.16 [flutter flutter_web_plugins url_launcher_platform_interface]
- url_launcher_windows 3.0.5 [flutter url_launcher_platform_interface]
- uuid 3.0.7 [crypto]
- vector_math 2.1.4
- vm_service 9.4.0
- watcher 1.0.2 [async path]
- web_socket_channel 2.3.0 [async crypto stream_channel]
- webdriver 3.0.1 [archive matcher path stack_trace sync_http]
- webkit_inspection_protocol 1.2.0 [logging]
- win32 3.1.3 [ffi]
- xdg_directories 0.2.0+3 [meta path process]
- xml 6.2.2 [collection meta petitparser]
- yaml 3.1.1 [collection source_span string_scanner]

@darshankawar Thank you for replying to this issue. I confirm that the app was configured accordingly to the provided instructions (compile and target SDK was set to 33 in build.gradle, and exported="true" in the app manifest).

During the app startup I call:
firebaseMessaging.requestPermission();

Is there a way for you to provide a complete minimal code sample that has this usage and triggers this error ?
Usually the requestPermission() method is called as such:
return await FirebaseMessaging.instance.requestPermission(
      alert: true,
      announcement: false,
      badge: true,
      carPlay: false,
      criticalAlert: false,
      provisional: false,
      sound: true,
    );

@darshankawar Sorry, I really can't reproduce this exception on my Android device. However, here's the minimal code that should provoke this exception.
pubspec.yaml:
  firebase_core: ^2.8.0
  firebase_analytics: ^10.1.6
  firebase_crashlytics: ^3.0.17
  firebase_messaging: ^14.3.0
  firebase_remote_config: ^3.0.15
  flutter_local_notifications: ^13.0.0 # just in case, my app also depends on this plugin

main.dart:
import 'dart:async';

import 'package:firebase_core/firebase_core.dart';
import 'package:firebase_crashlytics/firebase_crashlytics.dart';
import 'package:firebase_messaging/firebase_messaging.dart';
import 'package:flutter/foundation.dart';
import 'package:flutter/material.dart';
import 'package:flutter_local_notifications/flutter_local_notifications.dart';

import 'firebase_options.dart';

Future<void> main() async {
  WidgetsFlutterBinding.ensureInitialized();
  // Firebase Core
  await Firebase.initializeApp(
    options: DefaultFirebaseOptions.currentPlatform,
  );
  // Firebase Crashlytics
  FlutterError.onError = FirebaseCrashlytics.instance.recordFlutterFatalError;
  PlatformDispatcher.instance.onError = (error, stack) {
    FirebaseCrashlytics.instance.recordError(error, stack, fatal: true);
    return true;
  };
  // flutter_local_notifications
  await initializeFlutterLocalNotificationsPlugin();
  //
  runApp(
    MaterialApp(
      home: FirebaseConfiguration(
        child: Scaffold(
          appBar: AppBar(),
        ),
      ),
    ),
  );
}

Future<void> initializeFlutterLocalNotificationsPlugin() async {
  final flutterLocalNotificationsPlugin = FlutterLocalNotificationsPlugin();
  const kAndroidInitializationSettings =
      AndroidInitializationSettings('ic_stat_watch_later');
  const kDarwinInitializationSettings = DarwinInitializationSettings(
    requestAlertPermission: false,
    requestBadgePermission: false,
    requestSoundPermission: false,
  );
  const initializationSettings = InitializationSettings(
    android: kAndroidInitializationSettings,
    iOS: kDarwinInitializationSettings,
  );
  await flutterLocalNotificationsPlugin.initialize(
    initializationSettings,
    onDidReceiveNotificationResponse: (_) {},
  );
}

class FirebaseConfiguration extends StatefulWidget {
  final Widget child;

  const FirebaseConfiguration({
    super.key,
    required this.child,
  });

  @override
  State<FirebaseConfiguration> createState() => _FirebaseConfigurationState();
}

class _FirebaseConfigurationState extends State<FirebaseConfiguration> {
  @override
  void initState() {
    super.initState();
    _init();
  }

  Future<void> _init() async {
    final firebaseMessaging = FirebaseMessaging.instance;
    // Request the notification permission during the start up.
    await firebaseMessaging.requestPermission();
  }

  @override
  Widget build(BuildContext context) => widget.child;
}

Thanks for the update. I tried using the code sample you provided on Pixel XL emulator (although not on Android 13), but was unable to replicate the exception.
I am going ahead and labeling this issue for team's attention and thoughts.
/cc @Lyokone

We're seeing the same issues in our app. Our app is not using flutter_local_notifications but another notification plugin called awesome_notifications.
For us we're mostly seeing the error on Samsung devices and 99% of them were running "in background"

@serhii-k Do you know which version of firebase_messaging you used before upgrading to the latest version?

Hi,
We went from 13.1.0 to 14.3.0.
pubspecs.zip

@Lyokone Previously it was:
firebase_messaging: ^12.0.1

Any update on this?. I'm facing the exactly same issue.

I am having the same issue with background messages.
`I/flutter (10686): FlutterFire Messaging: An error occurred in your background messaging handler:
I/flutter (10686): [firebase_messaging/unknown] Attempt to invoke virtual method 'java.lang.Object android.content.Context.getSystemService(java.lang.String)' on a null object reference

Using latest version of firebase_messaging.

I have the same issue with the latest version of firebase_messaging: ^14.6.2

Try new version they have solved this issues
firebase_messaging: ^14.6.3

My observations:
1) On Android 13 the exception says "Unable to detect current Android Activity."
Probably it happens here:
https://github.com/firebase/flutterfire/blob/d11440aba7e1172e69086dc12b07a94f27670fc8/packages/firebase_messaging/firebase_messaging/android/src/main/java/io/flutter/plugins/firebase/messaging/FlutterFirebasePermissionManager.java#L57
When activity is null.
I'm trying to show the notification permission popup during the start up. So probably the activity has not yet been initialized at this stage.
2) From the Firebase Console I see that this issue happens on:

practically every Pixel model
Sony devices
devices of a lot of Chinese manufacturers

BUT. For example, it has never happened on any Samsung device.

Hi @serhii-k, your observation is likely correct. Requesting permission relies on the activity to be started & available. If you're receiving that error, there isn't much to be done on FlutterFire side. You would need to design your application in a manner where you delay requesting permission to ensure the activity has been created and hasn't been closed out due to inactivity (e.g. in background state for a period of time).

Hello @russellwheatley, Thank you for the suggestions. I think you are right. I'm closing this issue for now.


[Synapse] New OnBoard Synapse cli extension

Synapse is a new service. We submitted this PR to on board Synapse to azure cli.
The command groups and commands are as bellow:

az synapse workspace

show
list
create
delete

az synapse spark pool

show
list
create
delete

az synapse sql pool

show
list
create
pause
resume
delete

az synapse spark batch

show
list
create
cancel

az synapse spark session

show
list
create
cancel
reset-timeout

az synapse spark session-statement

show
list
create
cancel

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/aim-for-better/azure-cli-extensions.git@synapse_cli_extension#subdirectory=src/$EXT&egg=$EXT"

Please replace with src/synapse/azext_synapse/vendored_sdks/azure_mgmt_synapse with https://github.com/Azure/azure-sdk-for-python/tree/master/sdk/synapse/azure-mgmt-synapse/azure/mgmt/synapse

updated

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


Pretty option

How about an option mp.pretty = True to make repr = str? This would lead to
slightly cleaner interactive examples.

Original issue for #193: http://code.google.com/p/mpmath/issues/detail?id=153
Original author: https://code.google.com/u/111502149103757882156/
Original owner: https://code.google.com/u/111502149103757882156/

I think this is fixed.


tls: support async cert validation

Commit Message: change TLS transport socket to use SSL_CTX_set_custom_verify() instead of SSL_CTX_set_verify() and change CertValidator interface to support async cert validation. Also change EnvoyQuicCertVerifier to use the new async interfaces.
This change is needed for https://github.com/envoyproxy/envoy-mobile/issues/1575. Envoy Mobile allows certificates to be verified by the OS-provided certificate verifier. And these verification can be very slow and so blocking the network thread while the verification happens is not an option. Instead, the verification should be performed asynchronously on a different thread. (This is how the cert verification works in Chrome, which is what we're modeling this implementation on).
Risk Level: high, change boring SSL interface used
Testing: added new unit tests and integration tests
Docs Changes: release note
Release Notes: documented tls transport changes.
Runtime guard: envoy.reloadable_features.tls_async_cert_validation

/assign @RyanTheOptimist

High level question to start, since it wasn't obvious from skimming through the code: why does this need to become async?
/wait-any

High level question to start, since it wasn't obvious from skimming through the code: why does this need to become async?
/wait-any

Oh, great question. We should discuss that in the PR and potentially link to envoyproxy/envoy-mobile#1575. This PR lays the ground work for eventually allowing certificates to be verified by the OS-provided certificate verifier. Annoyingly, these verifications can be very slow and so blocking the network thread while the verification happens is not an option. Instead, the verification will be performed on a different thread. (This is how the cert verification works in Chrome, which is what we're modeling this implementation on). Hopefully that helps?

Another use case is support for cloud HSM, that require RPC for key operations.

High level question to start, since it wasn't obvious from skimming through the code: why does this need to become async?
/wait-any

Oh, great question. We should discuss that in the PR and potentially link to envoyproxy/envoy-mobile#1575. This PR lays the ground work for eventually allowing certificates to be verified by the OS-provided certificate verifier. Annoyingly, these verifications can be very slow and so blocking the network thread while the verification happens is not an option. Instead, the verification will be performed on a different thread. (This is how the cert verification works in Chrome, which is what we're modeling this implementation on). Hopefully that helps?

Another use case is support for cloud HSM, that require RPC for key operations.

This change is to validation; I think it would be a different change to do async signing.

High level question to start, since it wasn't obvious from skimming through the code: why does this need to become async?
/wait-any

Oh, great question. We should discuss that in the PR and potentially link to envoyproxy/envoy-mobile#1575. This PR lays the ground work for eventually allowing certificates to be verified by the OS-provided certificate verifier. Annoyingly, these verifications can be very slow and so blocking the network thread while the verification happens is not an option. Instead, the verification will be performed on a different thread. (This is how the cert verification works in Chrome, which is what we're modeling this implementation on). Hopefully that helps?

Nice explanation! Added it into PR description.

There's a lot going on in this PR, as you mentioned :) If there are any opportunities to break out refactors into smaller PRs, I would strongly recommend doing so to expedite getting this landed. Here's a first pass at reviewing source/.

sds_integration_test failure is fixed!
Meanwhile I'm moving the verification context change into https://github.com/envoyproxy/envoy/pull/21444 and split out some refactoring changes.

There's a lot going on in this PR, as you mentioned :) If there are any opportunities to break out refactors into smaller PRs, I would strongly recommend doing so to expedite getting this landed. Here's a first pass at reviewing source/.

sds_integration_test failure is fixed! Meanwhile I'm moving the verification context change into #21444 and split out some refactoring changes.

Has that code been moved out of this PR yet, or is that coming in a future commit? (No rush, just trying to make sure I'm following)

Looking at the linux_x64 compile_time_options build failure, I think some of the BoringSSL functions you're calling aren't supported in the FIPS version yet.

/assign @davidben

I tried to review this CL, but my eyes started to glaze over at some point. It's very large and contains a lot of Envoy bits that I'm not familiar with.

Thanks for the initial review!
The PR switch to using a different cert validation interface in [source/extensions/transport_sockets/tls/context_impl.cc](https://github.com/envoyproxy/envoy/pull/21417/files/148bf887ff77c09f9e54140e842573564e9740d3#diff-2b39f212c2f760ae547351a46f92ad08c0ec84c556d678ebe9388b9d008e7313. So it will be great if you could help reviewing its interaction with source/extensions/transport_sockets/tls/cert_validator/default_validator.cc and source/extensions/transport_sockets/tls/context_impl.cc.
Thanks!

clang-tidy fails spuriously again with error source/common/common/logger_impl.h' file not found [clang-diagnostic-error].

@davidben do you

I tried to review this CL, but my eyes started to glaze over at some point. It's very large and contains a lot of Envoy bits that I'm not familiar with.

Thanks for the initial review! The PR switch to using a different cert validation interface in [source/extensions/transport_sockets/tls/context_impl.cc](https://github.com/envoyproxy/envoy/pull/21417/files/148bf887ff77c09f9e54140e842573564e9740d3#diff-2b39f212c2f760ae547351a46f92ad08c0ec84c556d678ebe9388b9d008e7313. So it will be great if you could help reviewing its interaction with source/extensions/transport_sockets/tls/cert_validator/default_validator.cc and source/extensions/transport_sockets/tls/context_impl.cc.
Thanks!

@davidben it would be great if you could review this and confirm (or not) if we're doing the right things here.

/retest

/retest

/retest

clang-tidy failed because of the build prefix of logger.h:
  FilePath: ./source/common/common/logger.h
    Message: '''source/common/common/logger_impl.h'' file not found'
    Ranges:
    - FileOffset: 303
      FilePath: ./source/common/common/logger.h

This is unrelated to this change. @RyanTheOptimist PTAL

@ggreenway are you happy with this PR no?

I'll take a look today. I haven't looked at this one in quite awhile.

/retest

PTAL @ggreenway

/wait-any

clang-tidy is still complaining the unrelated missing include in source/common/common/logger.h.
PTAL @ggreenway

clang-tidy error is a tool failure; I don't understand why it's producing this error.
Writing fixes to clang-tidy-fixes.yaml ...
clang-tidy check failed, potentially fixed by clang-apply-replacements:
Diagnostics:
- BuildDirectory: /build/tmp/_bazel_envoybuild/b570b5ccd0454dc9af9f65ab1833764d/execroot/envoy
  DiagnosticMessage:
    FileOffset: 303
    FilePath: ./source/common/common/logger.h
    Message: '''source/common/common/logger_impl.h'' file not found'
    Ranges:
    - FileOffset: 303
      FilePath: ./source/common/common/logger.h
      Length: 36
    Replacements: []
  DiagnosticName: clang-diagnostic-error
  Level: Error
MainSourceFile: ''

@RyanTheOptimist This is good to merge. Thanks!

Alas, I can't merge 'cause of the spurious clang tidy error. @alyssawilk, can you?

alas by now it needs a main merge, but I'm happy to force merge once that's sorted

The PR is sync'ed @alyssawilk


Chore: Avoid memory leaks on ONNX loader

Changes the wrapper to a Resource, and handles properly the deletion of C# disposables.

Hey, I'm going trough the suggestions, don't worry, in the editor it might seem as if it wasn't proceeding with the notification function, but it is, you just need to run the editor in --verbose to make sure, as most messages printed from the _notification won't show unless you do that. Also, we should still close the file before disposing it

.15 ms using dispose, .13 with no dispose, not bad, seems everything's going ok I just gotta check the scene change issue you mentioned

Hey, thanks a lot for going through the suggestions and for the additional information.

In the editor it might seem as if it wasn't proceeding with the notification function, but it is, you just need to run the editor in --verbose to make sure, as most messages printed from the _notification won't show unless you do that.

Thanks! I didn't know this, that should simplify the solution a lot. I will try it.

We should still close the file before disposing it

Here is a snippet from the official Godot tutorial example (https://docs.godotengine.org/en/stable/classes/class_fileaccess.html):
public string Load()
{
    using var file = FileAccess.Open("user://save_game.dat", FileAccess.ModeFlags.Read);
    string content = file.GetAsText();
    return content;
}

Also from the docs for the Close method:

Note: FileAccess will automatically close when it's freed, which happens when it goes out of scope or when it gets assigned with null. In C# the reference must be disposed after we are done using it, this can be done with the using statement or calling the Dispose method directly.

With the using statement applied applied to the LoadModel method, it would look like this:
        public InferenceSession LoadModel(string Path)
        {
            using Godot.FileAccess file = FileAccess.Open(Path, Godot.FileAccess.ModeFlags.Read);
            byte[] model = file.GetBuffer((int)file.GetLength());
            return new InferenceSession(model, SessionOpt); //Load the model
        }

(This calls .Dispose() only, but it seems to be slightly different than manually calling .Dispose(), more information below)
Is the file not getting closed when needed unless .Close() is called? If it is managed properly in this case, perhaps the milliseconds can be reduced without the .Close() call in case it is performing some operations twice (I didn't measure the time so I can't be sure).
Visual studio recommends to me to use the using statement instead of .Dispose() (related style rule: https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/style-rules/ide0063)
While the style is just a design choice usually, in this case it has some functional benefits to use it where possible (sometimes we will have to use .Dispose() manually when calling disposal methods from Godot side). The using block will call dispose in a finalize block, ensuring disposal even in case of exceptions.
Additional info here (https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/statements/using?redirectedfrom=MSDN):

In particular, the using statement ensures that a disposable instance is disposed even if an exception occurs within the block of the using statement.

And here:
https://stackoverflow.com/a/10984354
Let me know your thoughts on this and whether I can help with testing or implementing some parts. I appreciate your experience and implementations.

Alright, I made a last set of changes, used the "using" keyword just once, not for the results as I actually find useful being able to catch any exception and print it out.

@Ivan-267 can you check if the crashes are gone? It should be ready to merge now

Hello, thank you for these changes. I agree with you regarding using, actually I made an error in the code I provided regarding using for results, it's still possible to use using inside of the try block (corrected the snippet above), but it may not be as convenient to have everything in the try block so we can consider whether we want using later due to its advantages of disposing on error, that shouldn't slow down this PR.
The issue still happens regarding scene switching.
I tried to propose changes in the review, but with multiple line changes, it is difficult to show them line by one and make sure I copy the changes properly, so I made a PR to your fork instead, hopefully that works as a simpler solution:
https://github.com/yaelatletl/godot_rl_agents_plugin/pull/1
As a side-note I also had to disable line 31 in sync.gd while testing scene switching:
	#await get_tree().root.ready

With that and the above PR, it did pass the test locally with changing scenes and no crashing or errors.
However that part not added to my changes since it may have side effects, I only used it for testing. I would need to check the code more in-depth and spend some time testing different cases before proposing any changes to that part. Perhaps we can look into that more later.
Other than the config disposal/creation suggestions, the PR should now be ready for merging.

Alright, now it should problem free! Just awaiting aproval from @edbeeching


Sammyjroberts issue 10290/fix blocking queue

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes #10290
Type of Change
Please delete options that are not relevant.

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

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Added new unit/integration tests
[ ] Added new notebook (that tests end-to-end)
[x] I stared at the code and made sure it makes sense

Suggested Checklist:

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added Google Colab support for the newly added notebooks.
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I ran make format; make lint to appease the lint gods

Going to close this in favor of https://github.com/run-llama/llama_index/pull/10339 for now


What exactly makes this improved over the normal std?

I'm just wondering because I just stumbled across this as of right now.

well, mostly it's just a funny name :D
it's basically my personal standard library.
it has stuff like allocators & simd (only aarch64 atm, i haven't done x86 yet), which std has, but aren't stable yet.
there's also some stuff for the common "handles instead of pointers" pattern (in the keyed module).


Unable to deploy a pod on Kubernetes cluster

Gives following error on kubectl describe pods:
Warning: FailedSync Error syncing pod, skipping: failed to "SetupNetwork" <pod_name> with SetupNetworkError: "Failed to setup network for pod using network plugins "cni\

The issue has been resolved in the latest Vagrantfile.

Did you recently update the Vagrantfile? I was working on the version which was merged today(Pull request #29) .

Check the output of the command from k8s master:
kubectl get pods --all-namespaces
In case the weave is showing crashing (Issue #26), The fix is merged with Pull Request #31

Doesn't have enough information to go on. The latest boxes have been seen to bring up the cluster fine.
If you see the issue again, provide the logs from the installation.


Implement combine mode for area

Slower implementation of #1559 that does not break when area priority is changed programmatically.
The area order calculation is done on every integration step.

merged, can you implement this also in 2D?

Sure, I'll work on that tomorrow, it shouldn't take long.


fix: Remove horizontal scrollbar from docs navbar

Fixes Issue #11
Scrollbar doesn't show up on the docs navbar.

Hi @Truezeber,
I’ve made the changes you suggested.

Looks great, merging. Thanks for your contribution!


Test review apps

Closing as this PR did not trigger the desired Heroku Review App for some reason.  It might have been because the PR was created as a draft initially.  Will try again with a new PR.


The maximized state before the window was minimized is not restored

When restoring the application from the system tray, the maximized state before the window was minimized is not restored, and the operating system is Windows 11.

Thanks for the bug report.  This should now be fixed -- see release 1.0.3.


Pre-train the BART

Hi,
Do you have a script to pre-train the BART model? I read your documentation, but I can’t find it. Thanks.
Cahya

Hi @cahya-wirawan, the pretraining is carried out using Fairseq framework.
Check the denoising task that is used to pretrain Bart.


Stop copying curl.exe manually

We fixed this upstream in the Mesos build. curl.exe is now
appropriately placed next to mesos-agent.exe by CMake automatically.

This was found in Review 64720, but it can be merged immediately, as the CMake build was fixed in the last few weeks to automatically deploy curl.exe to the right location. Thus this stopgap can (and should) be removed.

It was in:
commit b464f49cb79c4921f83cb4bf0f12c47a5d8fa4ed
Author: John Kordich<EMAIL_ADDRESS>Date:   Wed Dec 6 12:08:32 2017 -0800

    Added `curl` executable to Windows build.

    Some Mesos health checks use the `curl` executable, which is a required
    component on Linux, but also shipped on the system. On Windows,
    `curl.exe` is not normally available. However, we already build `curl`
    for other components which link to `libcurl`. Part of this build also
    builds `curl.exe`, so we renamed the `curl` target to
    `libcurl` (explicitly meaning the library), and added `curl` as an
    imported executable target on Windows.

    Note that this uses `add_custom_command(... POST_BUILD)` to inject a
    copy step as a post-build side effect of the `ExternalProject_Add`
    target which builds cURL. There is no cleaner way to accomplish this as
    CMake does not otherwise have an easy way to copy a file as part of an
    _imported_ target at build time. The `add_custom_target` command does
    not work because it adds a target that will always be built (not what
    we're trying to accomplish here), and the other signature of
    `add_custom_command` does not produce a target dependency. While the
    `OUTPUT` argument would let us use file dependencies, `curl.exe` isn't a
    source file that another target can depend on.

    Review: https://reviews.apache.org/r/64102/


chore: upgrade iot-app-kit versions

What this PR does / why we need it:
Upgrading iot-app-kit versions

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


The state this._opened is not really true for a short amount of time

Hi,
Just playing around with the menu and I found an issue. When closing the menu the this._opened is set to false before the menu is really closed. The same goes for opening the menu, it is set to true before it is even opened.
relevant code this._opened is set before setTimeout:
/**
 * Opens the slideout menu.
 */
Slideout.prototype.open = function() {
  var self = this;
  if (html.className.search('slideout-open') === -1) { html.className += ' slideout-open'; }
  this._setTransition();
  this._translateXTo(this._padding);
  this._opened = true;  // it is not really opened now
  setTimeout(function() {
    self.panel.style.transition = self.panel.style['-webkit-transition'] = '';
  }, this._duration + 50);
  return this;
};

/**
 * Closes slideout menu.
 */
Slideout.prototype.close = function() {
  var self = this;
  if (!this.isOpen() && !this._opening) { return this; }
  this._setTransition();
  this._translateXTo(0);
  this._opened = false;  // it is not really closed now
  setTimeout(function() {
    html.className = html.className.replace(/ slideout-open/, '');
    self.panel.style.transition = self.panel.style['-webkit-transition'] = '';
  }, this._duration + 50);
  return this;
};

Consider the following usage scenario:
elastoApp.prototype.createMenu = function () {
  this.menu = new Slideout({
    'panel': document.getElementById('container'),
  'menu': document.getElementById('menu'),
  'padding': 256,
  'tolerance': 70
  });
};

elastoApp.prototype.scrollToLinks = function() {
  var self = this;
  var scrollers = document.querySelectorAll('.menu[href^="#"]');
  var scrollEvent = function(e) {
    e.preventDefault();
    var link = e.target.getAttribute('href');
    var domid = link.replace(/#/,'');
    var ele = document.getElementById(domid);
    if ( ele ) {
      self.scrollIntoView(ele);
    }
  };

  for ( var i=0; i<scrollers.length; i++ ) {
    scrollers[i].addEventListener('click', scrollEvent);
  }
};

// we need to scroll into view after the menu is closed, else the browser
// will remember the position with an open menu
// so we wait for the menu transition to finish
elastoApp.prototype.scrollIntoView = function(element) {

  var self = this;
  var wait_for_it = function(ele) {

    // the problem occurs here, if the menu is _opened = false
    // we scroll into view, but if the menu is not really closed because
    // of the setTimeout, we run in to trouble
    if ( self.menu._opened ) {
      setTimeout(function() {
        wait_for_it(ele);
      }, 100);
    } else {
      element.scrollIntoView(true);
    }
  };

  wait_for_it();

};

Regards,
Frodo

Thanks @flarik for the heads up. It is really true what you say. The idea of _opened starting with an underscore is because it is a "private" variable in the sense we are not exposing it as part of the Slideout.js API, it's part of the internal implementation. That's when the proposed events become relevant, the idea is you can hook to events like open or close. While implementing those events, we'll make sure the given information will be accurate.

#3


XML entities are replaced with corresponding character

I'm not sure if it's intended, but XML entities are replaced with their corresponding charachter during rearrangement.
For example, I substituted an en dash in my strings.xml with – to prevent confusion with the normal dash.
Before rearrangement:
<string name="timePeriod">27.09.2017, 10:00 – 27.09.2017, 11:00</string>
After rearrangement:
<string name="timePeriod">27.09.2017, 10:00 – 27.09.2017, 11:00</string>
Can you please include an option in the popup dialog to disable this behaviour if this is actually intended.
Thanks!

Hi @xvlcw

Before rearrangement:
27.09.2017, 10:00 – 27.09.2017, 11:00
After rearrangement:
27.09.2017, 10:00 – 27.09.2017, 11:00

This is not intended. I will fix problem.
But, I may take time for fix.
Thanks issue !

@xvlcw
I investigated this and I thought not bug.
XML have "numeric character references" and "string entity references".
IntelliJ IDE can't refer a part of "string entity references", and convert it to actual on default.
- and – is same mean on XML.
Why do you use – (numeric character reference) ?
Example...

actual
string
10 numeric
16 numeric

>
<
<
<

-
–
–
–

> can refer all references, and <<< replaced to <<<.
- can't refer –, and –– replaced to --.
In my opinion.
Make a list of actual condition and "numeric character references" that IntelliJ IDE can't refer a part of "string entity references".
Add option that actual condition convert to "numeric character references".
You can solve the problem.
But, all actual condition are converted. It's not good. 🤔

@xvlcw I will close after 3 days if no response.  😓 🙏


Track pod's hostnames to mitigate false results on IP address reuse

Description
On loaded clusters with small range of pod ip addresses, pods can reuse IP addresses in relatively short periods of times.
When that happens, it triggers a sort of "time of set - time of use" bug:
The sniffer detects traffic from a certain IP at a current time. The mapper would eventually get that report and try to resolve the IP address to a pod name, at that point the address could belong to a newer pod (but that shouldn't cause an issue because we check the creation time). or more seriously, the mapper would use a not yet updated cache and link the traffic to a pod that doesn't exist anymore.
This PR gets the hostname of the container responsible for the traffic at realtime (in addition to its IP address). The hostname should always be the same as the pod name, therefor the mapper uses it to verify it found the right pod.
References
Testing
Checklist

recheck


Add Signal and Zotero icons, assign PDF to Preview

Hey, can we merge this in? :)

Hi! Of course, I'm doing this soon (today or tomorrow) :)