False positive when capturing a variable declared through a binding

Not sure if the title is clear but when declaring a variable through a binding and then trying to capture and use it in a lambda I get an error that doesn't exist when compiling:
#include <functional>
#include <iostream>

int main() {
    int a[2] = {0, 1};

    auto [b, c] = a;
    auto d = a[0];
    auto e = a[1];

    std::function<void()> f = [a, b, c, d, e]() {
        std::cout << "a: " << a << "\nb: " << b << "\nc: " << c << "\nd: " << d << "\ne: " << e << "\n";
    };

    f();
}

I get these errors on the capture:
Diagnostics:
1. 'b' in capture list does not name a variable [capture_does_not_name_variable]
2. 'c' in capture list does not name a variable [capture_does_not_name_variable]

and these when trying to use the variables inside the capture:
Diagnostics:
1. Reference to local binding 'b' declared in enclosing function 'main' [reference_to_local_in_enclosing_context]
2. Reference to local binding 'c' declared in enclosing function 'main' [reference_to_local_in_enclosing_context]

The code compiles and runs fine.
System information
Output of clangd --version:
clangd version 14.0.6
Features: linux
Platform: x86_64-unknown-linux-gnu

Editor/LSP plugin: neovim, nvim-lspconfig
Operating system: NixOS Unstable

Capturing structured bindings is a C++20 feature that, according to https://clang.llvm.org/cxx_status.html, was first added to clang in clang 16 (see "Structured bindinge extensions").
As such, you need clangd 16 or later to understand them.

should've checked, thank you!


Styles from Geoserver

In geoserver you can customize the styles of the points or lines.
How can I bring those styles from the geoserver server together with the wfs request?

I think this cannot be done.
WFS only sends the data from GeoServer and any styling must be done by the client.
Cheers.

Am keen on this one too. if we cannot import Geoserver styles, how can we add custom styles to map?

You can load the data from GeoServer as wms (not wfs) and the style will
come with the layer.
On Tue, 3 May 2022, 2:04 pm ShwetaMorkhandikar, @.***>
wrote:

Am keen on this one too. if we cannot import Geoserver styles, how can we
add custom styles to map?
—
Reply to this email directly, view it on GitHub
https://github.com/iag-geo/bootleaf/issues/32#issuecomment-1115721329,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKEPO2UZUL4AXKU4XHVT6YTVICQTPANCNFSM4RA4SLXA
.
You are receiving this because you commented.Message ID:
@.***>

Thank you


My account is suspended

Subject: My account is suspended
Description:
My account is suspended. My email is<EMAIL_ADDRESS>Results:
My account is suspended. My email is<EMAIL_ADDRESS>Backend version: develop-0023fa73
Frontend version:
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Page: https://couchers.org/login?from=%2Fmessages%2Fsurfing
User:

I created a ticket for support to reach out to this user.

Dupe of #5054


Implement explicit Variation Set

VariationSets are essential to ClinGen's goal to represent ClinVar variation.
This issue is to collect input on and implement a static Variation Set defined by explicit enumeration of constituent variation.

The current direction is this hierarchy:
Variation
+- DiscreteVariation
   +- Allele
   +- (Translocation?)
+- AggregateVariation
   +- DiscreteVariationSet
   +- Haplotype (of DiscreteVariation, with constraints)
   +- Genotype (of Haplotypes)
   +- VariationSet (unconstrained set of Variation)

Implemented enref/deref in Implemented enref/deref in 152fae1. Need to add tests to vr-python and vr-spec.


Plugin not found after update

After updating to the most recent version, the plugin no longer executes:
% yarn outdated
Usage Error: Couldn't find a script named "outdated".

I am using Yarn 2 - not sure if it may be connected.

Version 2+ of this plugin is only compatible with Yarn 3.  I'd recommend updating your project to Yarn 3 to continue using the new features.
yarn set version latest


Add Verify method to content store

It would be good to add a method that can actively verify the integrity of the content store, in partial or completely. This would be good for recovery situations or periodic paranoia.

May help in detecting data corruption issues like https://github.com/containerd/containerd/issues/934
I can work on this, if no one working on this.

@kunalkushwaha It doesn't look like this will do much for #934, as this will just verify on disk, packed content.

Understood, It will just verify the packed content, not at snapshot side.

@kunalkushwaha Yes, but this is fairly low priority.

This would be useful to find a bug like https://github.com/containerd/containerd/issues/1368 , which allows a committed snapshot to be modified unexpectedly.

memo: fsverity could be used for this purpose, although not available in the upstream kernel (yet)
https://schd.ws/hosted_files/lssna18/af/fs-verity slide deck.pdf

This could still be useful as a separate utility to checking validity or even introspection of containerd's root. Going to mark this as a help wanted.

Hi @dmcgowan ,  I'm a student from UT Austin. I am taking a virtualization class that requires us to work on an open source project, so I was wondering if you are still looking for people to contribute to this. If so, can I get more information on this issue? Thank you very much!

Looks like fs-verity IOCTLs are in kernel since v5.4; some distros have the command line components. Not sure if that is the right approach, but just as a follow-up to a 2018 comment :).


Request: allow method calls on constants

Currently methods & predicates can be called on self:
(_ #predicate?(:arg, %1) ...)
(_ #method(:arg, %1) ...)

Request is to allow calling them on constants:
(_ #Foo.predicate?(:arg, %1) ...)
(_ #Foo::Bar.method(:arg, %1) ...)
(_ #::Global::X.method(:arg, %1) ...)

Just for the reference, the idea was to allow usage of #rspec.example_groups.regular call chains, for namespacing purposes. Since this would only create complication in NP parser, and since Ruby has namespacing capabilities built-in, I completely support RSpec::ExampleGroups.regular syntax instead.
Just to make sure, is it correct that given:
module A
  module B
    def self.a_method
       # ...
    end
  end
end

module RuboCop
  module Cop
    class SomeCop < Base
      include A
      def_node_matcher :a, '( #B.a_method ...)'
    end
  end
end

would be able to call A::B.a_method?
It would be a nice way to structure configurable DSL helpers.

If the namespace is relative, i.e. you don't have to specify #A::B.a_method when A is included, I'd go with constants, no method call chaining.

Released as v1.1.0

@marcandre You're like a ⚡-man! 💯
This is just in time for the 2.0 RuboCop-RSpec release, thanks a lot!


Automated cherry pick of #1699: 同优先级规则deny优先于allow规则生效

Cherry pick of #1699 on release/2.11.0.
#1699: 同优先级规则deny优先于allow规则生效

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.11.0@6d50bdd). Click here to learn what that means.
The diff coverage is n/a.

@@               Coverage Diff                @@
##             release/2.11.0   #1700   +/-   ##
================================================
  Coverage                  ?   7.65%
================================================
  Files                     ?     412
  Lines                     ?   63111
  Branches                  ?       0
================================================
  Hits                      ?    4834
  Misses                    ?   57869
  Partials                  ?     408

Flag
Coverage Δ

#aFlag
7.65% <ø> (?)

Impacted Files
Coverage Δ

pkg/compute/models/guests.go
0.71% <ø> (ø)

Continue to review full report at Codecov.

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

/approve
/lgtm


[aliri_axum] feat: support axum 0.7

resolves #44
Support of axum 0.7 following the axum release note as upgrade path.
Blockers:
-[ ] https://github.com/seanmonstar/reqwest/issues/2039: Upgrade to hyper 1.0
-[ ] https://github.com/hyperium/tonic/issues/1579: Upgrade to http 1.0 and axum 0.7

Thank you for putting together a PR to kick this off. Indeed I too have been waiting a bit for some movement in other ecosystem areas before putting updating to 0.7.

Closing in favor of #70. Now that reqwest was also updated, there was greater benefit to moving this along. Still waiting for tonic and reqwest-middleware for other parts. Thanks for helping to kick this off!


No connection after firmware update

U_CELL: initialising with enable power pin not connected, PWR_ON pin 21 (0x15) (and is toggled from 1 to 0) and VInt pin not connected.
AT
AT
AT
AT
AT
U_CELL_PWR: powering on.
[00]AT
AT
AT
AT
AT
AT
AT
AT
AT
[00]AT
AT
OK
ATE0
ATE0
OK
AT+CMEE=2
OK
AT+UDCONF=1,0
OK
ATI9
M0.12.00,A.02.21
OK
AT&C1
OK
AT&D0
OK
AT+UCGED=5
OK
AT&K3
OK
AT+UPSV=4
OK
AT+CPSMS?
+CPSMS:0,,,"00011000","00001010"
OK
AT+CEDRXS?
+CEDRXS: 2,"0010"
+CEDRXS: 4,"0010"
+CEDRXS: 5,"0010"
OK
AT+CEDRXS=2,2
OK
AT+CEDRXS=2,4
OK
AT+CEDRXS=2,5
OK
AT+UMNOPROF?
+UMNOPROF: 0
OK
AT+UGPRF?
+UGPRF: 2,0,""
OK
AT+CFUN=4
OK
Opened device with return code 0.
Bringing up the network...
U_CELL_NET: preparing to register/connect...
AT+CREG=2
OK
AT+CGREG=2
OK
AT+CEREG=4
OK
AT+CIMI
901405103271762
OK
U_CELL_NET: user-specified APN is "iot.1nce.net".
AT+CGDCONT=1,"IP","iot.1nce.net"
OK
U_CELL_NET: setting automatic network selection mode...
AT+COPS?
+COPS: 0
OK
AT+CFUN=1
OK
AT+CREG?
+CREG: 2,0
OK
0: NReg
AT+CGREG?
+CGREG: 2,4
OK
0: OoC
AT+CEREG?
+CEREG: 4,0
OK
0: NReg
AT+CREG?
+CREG: 2,0
OK
0: NReg
AT+CGREG?
+CGREG: 2,4
OK
0: OoC
AT+CEREG?
+CEREG: 4,0
OK
0: NReg
AT+CREG?
+CREG: 2,0
OK
0: NReg
AT+CGREG?
+CGREG: 2,4
OK
0: OoC
AT+CEREG?
+CEREG: 4,0
OK
0: NReg
AT+CREG?
+CREG: 2,0
OK
0: NReg
AT+CGREG?
+CGREG: 2,4
OK
0: OoC
AT+CEREG?
+CEREG: 4,0
OK
0: NReg
AT+CREG?
+CREG: 2,0
OK
0: NReg
AT+CGREG?
+CGREG: 2,4
OK
0: OoC
AT+CEREG?
+CEREG: 4,0
OK
0: NReg
AT+CREG?
+CREG: 2,0
OK
0: NReg
AT+CGREG?
+CGREG: 2,4
OK
0: OoC
AT+CEREG?
+CEREG: 4,0
OK
0: NReg
AT+CREG?
+CREG: 2,0
OK
0: NReg
AT+CGREG?
+CGREG: 2,4
OK
0: OoC
AT+CEREG?
+CEREG: 4,0
OK
0: NReg
AT+CREG?
+CREG: 2,0
OK
0: NReg
AT+CGREG?
+CGREG: 2,4
OK
0: OoC
AT+CEREG?
+CEREG: 4,0
OK
0: NReg
AT+CREG?
+CREG: 2,0
OK
0: NReg
AT+CGREG?
+CGREG: 2,4
OK
0: OoC
AT+CEREG?
+CEREG: 4,0
OK
0: NReg
AT+CREG?
+CREG: 2,0
OK
0: NReg
AT+CGREG?
+CGREG: 2,4
OK
0: OoC
AT+CEREG?
+CEREG: 4,0
OK
0: NReg
AT+CREG?
+CREG: 2,0
OK
0: NReg
AT+CGREG?
+CGREG: 2,4
OK
0: OoC
AT+CEREG?
+CEREG: 4,0
OK
0: NReg
AT+CREG?
+CREG: 2,0
OK
0: NReg
AT+CGREG?
+CGREG: 2,4
OK
0: OoC
AT+CEREG?
+CEREG: 4,0
OK
0: NReg
AT+CREG?
+CREG: 2,0

Hi Alex.  Looking at #25, with the virtual network operator of your SIM (1nce) you ended up registered on the physical network of Deutsche Telecom and, I believe, on 2G.  If the RAT settings of the module happen to include NBIot, a complete network search can take 10s of minutes, so it might just take a while to get to 2G.  Forcing a manual selection on Deutsche Telecom likely cuts through that long process, 'cos you're telling the module exactly what you want.
That's my guess anyway.  All 3GPP stuff, not really something ubxlib knows much about I'm afraid.


go/registry: Remove support for DeprecatedBeacon

The PVSS backend is no longer present in 22.x and so the field is now
removed, and even genesis registrations without a VRF signing key will
be rejected.
Fixes #4394
Fixes #4393

Superseded by #4668


Accept header is missing from http requests

My Environment

ArangoDB Version:        3.7.2
Storage Engine:             RocksDB
Deployment Mode:       Single Server
Deployment Strategy:   ArangoDB Starter in Docker | Kubernetes
Configuration:               any
Infrastructure:               AWS | own
Operating System:        Ubuntu 20.04
Total RAM in your machine:        16GB
Disks in use:        SSD
Used Package:            Docker - official

Component, Query & Data
Affected feature: GraphiQL GUI
Steps to reproduce

Install GraphQL demo app https://github.com/arangodb-foxx/demo-graphql
Try to access GraphQL  service GraphiQL the button is gray

Problem:
Graphiql interface stopped working and it is giving me "'Must provide query string'" error in json.
The demo graphql app has the same error.
The real problem is that req.headers is missing "Accept" header and makes req.accept(['json', 'html']) to always return 'json' as accept library takes null for '*'.
Here you can see the json message in upper part JSON.stringify(req.headers) and actual Accept part of headers in lower right.

Expected result:
in Point 2. one should be able to click on green button and see GraphiQL GUI. And in foxx code one should be able to get "Accept" header.

@pluma What's the status here? Any update?

the C++ protocol implementation pulls out these headers on constant request object members. These need to be re-syntesized in the V8 callgates.

Hi @simcha,
This issue is fixed via https://github.com/arangodb/arangodb/pull/13068 in version 3.7.5.
Thanks again for reporting, the GraphQL service interface is now accessible as expected.


Cleanup quadtree space

Currently, the quadtree indexes the framedGraph space, normalizing the sizes by the container width. This works but is conceptually weird and might cause issues with screens having a vertical aspect ratio.
We could use the nullCamera viewport space to index but there are two issues with this:

Handling rotations
We would be wasting some part of the x or y dimension (we already are actually), since we rescale the graph aspect ratio wrt viewport aspect ratio.

Once #1382 is dealt with, this issue will be solved.


refactor: add main module and code clean up

Description
Git issue: https://github.ibm.com/GoldenEye/issues/issues/6142
Release required?

[ ] No release
[ ] Patch release (x.x.X)
[x] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Added root module (currently, only the VPC submodule is included; others can be added in separate PRs).
Refactored the code to align with the module template.
Fixed pre-commit failures (many pre-commit warnings remain and should be addressed when submodules are included in the main module; respective pre-commit issues can then be resolved).
Added a new complete example and test.
Removed input.tfvars from examples.
Made minor code cleanups in the VPC submodule.
Added IBM-Cloud/ibm provider version in submodules and examples.

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

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


Pod install fail - Podspec

Hi,
Thanks for this new release, the following line in the podspec will give an error during pod install as mraid.js file does not exist after importing the dependency through npm or yarn.
https://github.com/audienzzag/react-native-audienzz/blob/0213ce8760754d2d2d161d8c9f9bb091e8a55044/react-native-audienzz.podspec#L22

Hi @huextrat,
Thanks for your report. This is a known bug and we're releasing a new version today, where this will be fixed. This is caused by a fix of a bug in native AppNexus SDK preventing videos playback on iOS 13.+.

Hi @huextrat, please check out the latest version (0.3.4), the issue should be fixed there.
Feel free to reopen the issue if it still doesn't compile.


X-Axis Label Distortion at Lowest Data Level

When I drill down to lowest level, the X-axis labels in the waterfall chart are becoming distorted and appear disorganized.

Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce (for bugs)

Context

Screenshots

On "Drillable measures" page in the simple waterfall local testing power bi report, if you will drill down on "lowest level of data" by clicking on drill down option (as shown), the chart is not looking in a proper structure.


[YUNIKORN-2523] Bump go to 1.22

What is this PR for?
A few sentences describing the overall goals of the pull request's commits.
First time? Check out the contributing guide - http://yunikorn.apache.org/community/how_to_contribute
What type of PR is it?

[ ] - Bug Fix
[x] - Improvement
[ ] - Feature
[ ] - Documentation
[ ] - Hot Fix
[ ] - Refactoring

Todos

[ ] - Task

What is the Jira issue?

Open an issue on Jira https://issues.apache.org/jira/browse/YUNIKORN/
Put link here, and add [YUNIKORN-Jira number] in PR title, eg. [YUNIKORN-2] Gang scheduling interface parameters

How should this be tested?
Screenshots (if appropriate)
Questions:

[ ] - The licenses files need update.
[ ] - There is breaking changes for older versions.
[ ] - It needs documentation.

@lowc1012 Could you correct the JIRA link?


Tournament brackets

use the ladder seedings to organize tournaments

I suggest a mashup with Challonge.com instead - they do all of this and have a full API


make WorldQuery very flat

Objective
Simplify the worldquery trait hierarchy as much as possible by putting it all in one trait that can be easily migrated to use gats when (if rolls eyes) they stabilize.
first commit is #5170 so only the second commit really needs to be looked at...
Solution
methods on FetchState and Fetch are moved to WorldQuery. Any associated types that require the use of a gat lifetime are put on WorldQueryGats, everything else on WorldQuery

Changelog

This section is optional. If this was a trivial fix, or has no externally-visible impact, you can delete this section.

What changed as a result of this PR?
If applicable, organize changes under "Added", "Changed", or "Fixed" sub-headings
Stick to one or two sentences. If more detail is needed for a particular change, consider adding it to the "Solution" section

If you can't summarize the work, your change may be unreasonably large / unrelated. Consider splitting your PR to make it easier to review and merge!

Migration Guide

This section is optional. If there are no breaking changes, you can delete this section.

If this PR is a breaking change (relative to the last release of Bevy), describe how a user might need to migrate their code to support these changes
Simply adding new functionality is not a breaking change.
Fixing behavior that was definitely a bug, rather than a questionable design choice is not a breaking change.

This might be easier if you merge in #4800 first and then base off main + 4800 + 5170?

Yeah honestly no point reviewing this rn because it needs my other PR to get merged anyway :woman_shrugging: mostly just opening as proof of concept "look we can actually make the traits 1000x simpler even without gats"

I'm very impressed that this is possible, and think this is important to prioritize. We even get nicer user-facing error messages! @cart, when you're ready I think we should do:

#5170
#5205
#4800

in order to reduce rebasing pain.

bors r+


reading openapi string regular expression pattern

What:
String Pattern should consider the regular expression in OpenAPI while matching and generating values
Why:

Contract Tests

Request - Values generated should be according to regular expression since application may be expecting it
Response - Verification of Strings against regular expression makes tests even more thorough

Stubs

Request - Verification of Strings against regular expression makes the stub behave exactly as per spec
Response - Generating values as per regular expression emulates the Provider even better

How:

Matching leverage Kotlin libraries
Generating is done with generex

Checklist:

[ ] Documentation added to the README.md OR link to PR on https://github.com/specmatic/specmatic-documentation
[x] Tests
[ ] Sonar Quality Gate

Closing this because the PR is quite old and we need to chose another approach to generate stub responses based on regex.


Add support for AAD interactive connection strings for project data sources

This PR fixes #11262. This adds support for AAD interactive connection strings for data sources and publish profiles. If a profile that has an AAD interactive connection string is loaded, then the connection dialog opens with the authentication type set to Azure Active Directory - Universal with MFA Support.

Coverage increased (+0.002%) to 37.885% when pulling bd4dd39e8a4ae981715ac31d87cf92a682e942a5 on kisantia/aadInteractive into acd9fc8fd62ee8fdf7be5cc3922aee1c74e03638 on main.


nRF54L20 board soc support

Added support for nRF54L20 device with configuration of initial PDK board.

Please split this big commit into smaller ones related to particular areas: soc:, dts:, modules:, boards:, and a separate one that introduces SOC_NRF54LX_SKIP_TAMPC_SETUP.

Done

see my comment

I see it is merged now

see my comment

I see it is merged now

Then please, align

see my comment

I see it is merged now

Then please, align

done


Compilation error

Ran into the following after swift run.  First, here's my Package.swift:

let package = Package(
    name: "Linux",
    products: [
        .library(
            name: "Linux",
            targets: ["Linux"]),
        ],
    dependencies: [
        .package(url: "https://github.com/IBM-Swift/BlueSocket.git",.upToNextMajor(from: "1.0.0")),
        .package(url: "https://github.com/Bouke/NetService.git",.upToNextMajor(from: "0.4.1"))
    ],
    targets: [
        .target(
            name: "Linux",
            dependencies: ["Socket", "NetService"]),
        .testTarget(
            name: "LinuxTests",
            dependencies: ["Linux"]),
    ]
)

Here's the error:
/home/robreuss/Development/VirtualMobileController/VirtualMobileController_Linux/.build/checkouts/NetService.git-469506449312911919/Sources/NetService/NetServiceBrowser.swift:100:35: error: value of type '[ResourceRecord]' has no member 'compactMap'
        let newPointers = message.answers
                          ~~~~~~~~^~~~~~~
/home/robreuss/Development/VirtualMobileController/VirtualMobileController_Linux/.build/checkouts/NetService.git-469506449312911919/Sources/NetService/Responder.swift:66:21: error: value of type '[Socket.Address]' has no member 'compactMap'
      hostRecords = addresses.compactMap { (address) -> HostRecord<IPv4>? in
                    ^~~~~~~~~ ~~~~~~~~~~
/home/robreuss/Development/VirtualMobileController/VirtualMobileController_Linux/.build/checkouts/NetService.git-469506449312911919/Sources/NetService/Responder.swift:74:22: error: value of type '[Socket.Address]' has no member 'compactMap'
      host6Records = addresses.compactMap { (address) -> HostRecord<IPv6>? in
                     ^~~~~~~~~ ~~~~~~~~~~
/home/robreuss/Development/VirtualMobileController/VirtualMobileController_Linux/.build/checkouts/NetService.git-469506449312911919/Sources/NetService/NetService.swift:291:18: error: value of type '[ResourceRecord]' has no member 'compactMap'
      if message.answers.compactMap({ $0 as? ServiceRecord }).contains(where: { $0.name == fqdn }) {
         ~~~~~~~~^~~~~~~ ~~~~~~~~~~
/home/robreuss/Development/VirtualMobileController/VirtualMobileController_Linux/.build/checkouts/NetService.git-469506449312911919/Sources/NetService/Utils.swift:185:10: error: value of type '[UnsafeMutablePointer<ifaddrs>]' has no member 'compactMap'
        .filter { Int($0.pointee.ifa_flags) & Int(IFF_LOOPBACK) == 0 }
~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
error: terminated(1): /home/robreuss/swift-4.0-RELEASE-ubuntu16.04/usr/bin/swift-build-tool -f /home/robreuss/Development/VirtualMobileController/VirtualMobileController_Linux/.build/debug.yaml Linux.exe

Building on 4.1.3 fixed the issue.  Will try the other branch.
A side question: when I try to get the local hostname under Linux using the same method as I do on macOS I get nil.  What is the correct way to get the hostname under Linux?  Thanks!
Host.current().localizedName

I located your function get getting the hostname in your utils but how do I get access to the posix library for that?  I get this error:
/home/robreuss/Development/VirtualMobileController/VirtualMobileController_Linux/Sources/Linux/Networker.swift:110:17: error: use of unresolved identifier 'posix'
Do I need to import something to make posix function calls?

posix is not a library, but a function like gethostname, both defined in: https://github.com/Bouke/NetService/blob/master/Sources/NetService/Utils.swift.


Add a chemiscope example.

Just adding a small example to raise awareness of the utility of the tool. I am happy to change the scope as necessary.
Note that I have not made the python code testable to avoid the need for a new dev dependancy,

i think having the code testable is worth a dev dependcy

Added the dependency, tests should pass.


Azure Communication service won't start during install.

I followed the instructions on this page, and was able to start communicating with the MT3620 device last week. Today, after an automatic Windows OS update, I could not communicate with it. This may not be related, but I mention it just in case.
I have Visual Studio 16.2.2, but am unable to find out what version of Azure Sphere I have - see below.
As per the instructions, I uninstalled Azure Sphere, and tried to reinstall it. It failed on the first re-install, and I have not been able to get it to install since then.
It never asks me to re-install the TAP services described above (it did the first time when it worked), and no TAP devices appear in Networks. I cannot find anywhere to uninstall TAP drivers to force a re-install of this part.
The failing installation pop up states "Service 'Azure Sphere Device Communication Service' (AzureSphereDeviceCommunicationService) failed to start. Verify that you have sufficient privileges to start system services".
I have also tries to reinstall Visual Studio (with computer restarts after uninstall and re-install), but get the same error.
The complete log of the failure follows.
[0B50:0B4C][2019-08-19T12:04:51]i001: Burn v<IP_ADDRESS>1, Windows v10.0 (Build 18362: Service Pack 0), path: C:\Users\glynj\AppData\Local\Temp{DFC85812-DFE7-468C-9400-4DA5CA995712}.cr\Azure_Sphere_SDK_Preview_for_Visual_Studio(1).exe
[0B50:0B4C][2019-08-19T12:04:51]i000: Initializing string variable 'MbaNetfxPackageId' to value 'netfxfullredist_43'
[0B50:0B4C][2019-08-19T12:04:51]i000: Initializing string variable 'vsixQuiet' to value 'yes'
[0B50:0B4C][2019-08-19T12:04:51]i009: Command Line: '-burn.clean.room=C:\Users\glynj\Downloads\Azure_Sphere_SDK_Preview_for_Visual_Studio(1).exe -burn.filehandle.attached=668 -burn.filehandle.self=664'
[0B50:0B4C][2019-08-19T12:04:51]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\glynj\Downloads\Azure_Sphere_SDK_Preview_for_Visual_Studio(1).exe'
[0B50:0B4C][2019-08-19T12:04:51]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'C:\Users\glynj\Downloads'
[0B50:0B4C][2019-08-19T12:04:51]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\glynj\AppData\Local\Temp\dd_VC_AzureSphere_20190819120451.log'
[0B50:0B4C][2019-08-19T12:04:51]i052: Condition '(VersionNT >= v6.1)' evaluates to true.
[0B50:0B4C][2019-08-19T12:04:51]i000: Setting string variable 'WixBundleName' to value 'Azure Sphere SDK Preview for Visual Studio'
[0B50:0B4C][2019-08-19T12:04:51]i000: Setting string variable 'WixBundleManufacturer' to value 'Microsoft Corporation'
[0B50:0BD0][2019-08-19T12:04:51]i000: Setting numeric variable 'WixStdBALanguageId' to value 1033
[0B50:0BD0][2019-08-19T12:04:51]i000: Setting version variable 'WixBundleFileVersion' to value '<IP_ADDRESS>816'
[0B50:0BD0][2019-08-19T12:04:51]i000: Visual Studio Instance: Microsoft.VisualStudio.Product.Professional, Version 16.2.29209.62
[0B50:0BD0][2019-08-19T12:04:51]i000: Setting numeric variable 'VS2019_16_0_P2_Available' to value 1
[0B50:0BD0][2019-08-19T12:04:51]i000: Setting numeric variable 'VS2019_16_0_4_Available' to value 1
[0B50:0B4C][2019-08-19T12:04:51]i100: Detect begin, 11 packages
[0B50:0B4C][2019-08-19T12:04:51]i000: Product or related product not found: {D0C37DF0-56F6-4D80-BDFC-74EEB20F578D}
[0B50:0B4C][2019-08-19T12:04:51]i000: Setting version variable 'installedExtensionVersion' to value '<IP_ADDRESS>'
[0B50:0B4C][2019-08-19T12:04:51]i000: Setting string variable 'WindowsBuildNumber' to value '18362'
[0B50:0B4C][2019-08-19T12:04:51]i000: Setting string variable 'NETFRAMEWORK45' to value '528040'
[0B50:0B4C][2019-08-19T12:04:51]i000: Setting version variable 'vsixInstallerVersion' to value '16.2.3073.13146'
[0B50:0B4C][2019-08-19T12:04:51]i052: Condition 'NETFRAMEWORK45 >= 461808' evaluates to true.
[0B50:0B4C][2019-08-19T12:04:51]i052: Condition 'NOT (WixBundleAction = 3 AND WixBundleUILevel = 1)' evaluates to true.
[0B50:0B4C][2019-08-19T12:04:51]i052: Condition 'NOT (WixBundleAction = 3 AND WixBundleUILevel = 1)' evaluates to true.
[0B50:0B4C][2019-08-19T12:04:51]i052: Condition '(WixBundleAction=3) AND (NOT WixBundleUILevel=1)' evaluates to false.
[0B50:0B4C][2019-08-19T12:04:51]i052: Condition '(WixBundleAction=3) AND (NOT WixBundleUILevel=1)' evaluates to false.
[0B50:0B4C][2019-08-19T12:04:51]i101: Detected package: NetFx472Redist, state: Present, cached: None
[0B50:0B4C][2019-08-19T12:04:51]i101: Detected package: ConnectedServiceLegacyUninstallQuiet, state: Present, cached: None
[0B50:0B4C][2019-08-19T12:04:51]i101: Detected package: ConnectedServiceUninstallQuietV16, state: Present, cached: None
[0B50:0B4C][2019-08-19T12:04:51]i101: Detected package: VSExtensionVSIXV15, state: Absent, cached: None
[0B50:0B4C][2019-08-19T12:04:51]i101: Detected package: VSExtensionVSIXV16, state: Absent, cached: None
[0B50:0B4C][2019-08-19T12:04:51]i101: Detected package: TapDriverInstaller, state: Absent, cached: None
[0B50:0B4C][2019-08-19T12:04:51]i101: Detected package: AzureSphereCore, state: Absent, cached: None
[0B50:0B4C][2019-08-19T12:04:51]i101: Detected package: SlipService, state: Absent, cached: None
[0B50:0B4C][2019-08-19T12:04:51]i101: Detected package: Sysroot_index0, state: Absent, cached: Complete
[0B50:0B4C][2019-08-19T12:04:51]i101: Detected package: Sysroot_index1, state: Absent, cached: Complete
[0B50:0B4C][2019-08-19T12:04:51]i101: Detected package: Sysroot_index2, state: Absent, cached: Complete
[0B50:0B4C][2019-08-19T12:04:51]i052: Condition 'WindowsBuildNumber >= 14393' evaluates to true.
[0B50:0B4C][2019-08-19T12:04:51]i052: Condition 'VS2017_15_9_Available OR VS2019_16_0_4_Available' evaluates to true.
[0B50:0B4C][2019-08-19T12:04:51]i199: Detect complete, result: 0x0
[0B50:0BD0][2019-08-19T12:04:55]i000: Setting numeric variable 'EulaAcceptCheckbox' to value 1
[0B50:0BD0][2019-08-19T12:04:57]i000: Setting numeric variable 'EulaAcceptCheckbox' to value 1
[0B50:0B4C][2019-08-19T12:04:57]i200: Plan begin, 11 packages, action: Install
[0B50:0B4C][2019-08-19T12:04:57]w321: Skipping dependency registration on package with no dependency providers: NetFx472Redist
[0B50:0B4C][2019-08-19T12:04:57]w321: Skipping dependency registration on package with no dependency providers: ConnectedServiceLegacyUninstallQuiet
[0B50:0B4C][2019-08-19T12:04:57]w321: Skipping dependency registration on package with no dependency providers: ConnectedServiceUninstallQuietV16
[0B50:0B4C][2019-08-19T12:04:57]w321: Skipping dependency registration on package with no dependency providers: VSExtensionVSIXV15
[0B50:0B4C][2019-08-19T12:04:57]i000: Setting string variable 'WixBundleLog_VSExtensionVSIXV15' to value 'C:\Users\glynj\AppData\Local\Temp\dd_VC_AzureSphere_20190819120451_000_VSExtensionVSIXV15.log'
[0B50:0B4C][2019-08-19T12:04:57]i000: Setting string variable 'WixBundleRollbackLog_VSExtensionVSIXV15' to value 'C:\Users\glynj\AppData\Local\Temp\dd_VC_AzureSphere_20190819120451_000_VSExtensionVSIXV15_rollback.log'
[0B50:0B4C][2019-08-19T12:04:57]w321: Skipping dependency registration on package with no dependency providers: VSExtensionVSIXV16
[0B50:0B4C][2019-08-19T12:04:57]i000: Setting string variable 'WixBundleLog_VSExtensionVSIXV16' to value 'C:\Users\glynj\AppData\Local\Temp\dd_VC_AzureSphere_20190819120451_001_VSExtensionVSIXV16.log'
[0B50:0B4C][2019-08-19T12:04:57]i000: Setting string variable 'WixBundleRollbackLog_VSExtensionVSIXV16' to value 'C:\Users\glynj\AppData\Local\Temp\dd_VC_AzureSphere_20190819120451_001_VSExtensionVSIXV16_rollback.log'
[0B50:0B4C][2019-08-19T12:04:57]i000: Setting string variable 'WixBundleRollbackLog_TapDriverInstaller' to value 'C:\Users\glynj\AppData\Local\Temp\dd_VC_AzureSphere_20190819120451_002_TapDriverInstaller_rollback.log'
[0B50:0B4C][2019-08-19T12:04:57]i000: Setting string variable 'WixBundleLog_TapDriverInstaller' to value 'C:\Users\glynj\AppData\Local\Temp\dd_VC_AzureSphere_20190819120451_002_TapDriverInstaller.log'
[0B50:0B4C][2019-08-19T12:04:57]i000: Setting string variable 'WixBundleRollbackLog_AzureSphereCore' to value 'C:\Users\glynj\AppData\Local\Temp\dd_VC_AzureSphere_20190819120451_003_AzureSphereCore_rollback.log'
[0B50:0B4C][2019-08-19T12:04:57]i000: Setting string variable 'WixBundleLog_AzureSphereCore' to value 'C:\Users\glynj\AppData\Local\Temp\dd_VC_AzureSphere_20190819120451_003_AzureSphereCore.log'
[0B50:0B4C][2019-08-19T12:04:57]i000: Setting string variable 'WixBundleRollbackLog_SlipService' to value 'C:\Users\glynj\AppData\Local\Temp\dd_VC_AzureSphere_20190819120451_004_SlipService_rollback.log'
[0B50:0B4C][2019-08-19T12:04:57]i000: Setting string variable 'WixBundleLog_SlipService' to value 'C:\Users\glynj\AppData\Local\Temp\dd_VC_AzureSphere_20190819120451_004_SlipService.log'
[0B50:0B4C][2019-08-19T12:04:57]i000: Setting string variable 'WixBundleRollbackLog_Sysroot_index0' to value 'C:\Users\glynj\AppData\Local\Temp\dd_VC_AzureSphere_20190819120451_005_Sysroot_index0_rollback.log'
[0B50:0B4C][2019-08-19T12:04:57]i000: Setting string variable 'WixBundleLog_Sysroot_index0' to value 'C:\Users\glynj\AppData\Local\Temp\dd_VC_AzureSphere_20190819120451_005_Sysroot_index0.log'
[0B50:0B4C][2019-08-19T12:04:57]i000: Setting string variable 'WixBundleRollbackLog_Sysroot_index1' to value 'C:\Users\glynj\AppData\Local\Temp\dd_VC_AzureSphere_20190819120451_006_Sysroot_index1_rollback.log'
[0B50:0B4C][2019-08-19T12:04:57]i000: Setting string variable 'WixBundleLog_Sysroot_index1' to value 'C:\Users\glynj\AppData\Local\Temp\dd_VC_AzureSphere_20190819120451_006_Sysroot_index1.log'
[0B50:0B4C][2019-08-19T12:04:57]i000: Setting string variable 'WixBundleRollbackLog_Sysroot_index2' to value 'C:\Users\glynj\AppData\Local\Temp\dd_VC_AzureSphere_20190819120451_007_Sysroot_index2_rollback.log'
[0B50:0B4C][2019-08-19T12:04:57]i000: Setting string variable 'WixBundleLog_Sysroot_index2' to value 'C:\Users\glynj\AppData\Local\Temp\dd_VC_AzureSphere_20190819120451_007_Sysroot_index2.log'
[0B50:0B4C][2019-08-19T12:04:57]i201: Planned package: NetFx472Redist, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[0B50:0B4C][2019-08-19T12:04:57]i201: Planned package: ConnectedServiceLegacyUninstallQuiet, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[0B50:0B4C][2019-08-19T12:04:57]i201: Planned package: ConnectedServiceUninstallQuietV16, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[0B50:0B4C][2019-08-19T12:04:57]i201: Planned package: VSExtensionVSIXV15, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: None
[0B50:0B4C][2019-08-19T12:04:57]i201: Planned package: VSExtensionVSIXV16, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: None
[0B50:0B4C][2019-08-19T12:04:57]i201: Planned package: TapDriverInstaller, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[0B50:0B4C][2019-08-19T12:04:57]i201: Planned package: AzureSphereCore, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[0B50:0B4C][2019-08-19T12:04:57]i201: Planned package: SlipService, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[0B50:0B4C][2019-08-19T12:04:57]i201: Planned package: Sysroot_index0, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: No, uncache: No, dependency: Register
[0B50:0B4C][2019-08-19T12:04:57]i201: Planned package: Sysroot_index1, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: No, uncache: No, dependency: Register
[0B50:0B4C][2019-08-19T12:04:57]i201: Planned package: Sysroot_index2, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: No, uncache: No, dependency: Register
[0B50:0B4C][2019-08-19T12:04:57]i299: Plan complete, result: 0x0
[0B50:0B4C][2019-08-19T12:04:57]i300: Apply begin
[0B50:0B4C][2019-08-19T12:04:57]i010: Launching elevated engine process.
[0B50:0B4C][2019-08-19T12:05:01]i011: Launched elevated engine process.
[0B50:0B4C][2019-08-19T12:05:01]i012: Connected to elevated engine.
[13F0:13E8][2019-08-19T12:05:01]i358: Pausing automatic updates.
[13F0:13E8][2019-08-19T12:05:01]i359: Paused automatic updates.
[13F0:13E8][2019-08-19T12:05:01]i360: Creating a system restore point.
[13F0:13E8][2019-08-19T12:05:02]i361: Created a system restore point.
[13F0:13E8][2019-08-19T12:05:02]i370: Session begin, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{afaa4203-0409-4e16-ad86-0c52321dc834}, options: 0x7, disable resume: No
[13F0:13E8][2019-08-19T12:05:02]i000: Caching bundle from: 'C:\Users\glynj\AppData\Local\Temp{BD19295F-676C-4688-AB93-151A1020CA90}.be\Azure_Sphere_SDK_Preview_for_Visual_Studio.exe' to: 'C:\ProgramData\Package Cache{afaa4203-0409-4e16-ad86-0c52321dc834}\Azure_Sphere_SDK_Preview_for_Visual_Studio.exe'
[13F0:13E8][2019-08-19T12:05:02]i320: Registering bundle dependency provider: {afaa4203-0409-4e16-ad86-0c52321dc834}, version: <IP_ADDRESS>816
[13F0:13E8][2019-08-19T12:05:02]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{afaa4203-0409-4e16-ad86-0c52321dc834}, resume: Active, restart initiated: No, disable resume: No
[13F0:1538][2019-08-19T12:05:02]i305: Verified acquired payload: VSExtensionVSIXV15 at path: C:\ProgramData\Package Cache.unverified\VSExtensionVSIXV15, moving to: C:\ProgramData\Package Cache\VSIXBootstrapper.<IP_ADDRESS>816\VSIXBootstrapper.exe.
[13F0:1538][2019-08-19T12:05:02]i305: Verified acquired payload: pay4F357484EB30226D85A1F8D7990E3A62 at path: C:\ProgramData\Package Cache.unverified\pay4F357484EB30226D85A1F8D7990E3A62, moving to: C:\ProgramData\Package Cache\VSIXBootstrapper.<IP_ADDRESS>816\Microsoft.VisualStudio.AzureSphere.ProjectSystem.V15.vsix.
[13F0:1538][2019-08-19T12:05:02]i304: Verified existing payload: pay604BC1C19D2A4CFD8C3B77865142EA44 at path: C:\ProgramData\Package Cache\VSIXBootstrapper.<IP_ADDRESS>816\VSIXBootstrapper.exe.
[13F0:1538][2019-08-19T12:05:02]i305: Verified acquired payload: pay7A13C3CF128AFA2EF560FFF6492A76EB at path: C:\ProgramData\Package Cache.unverified\pay7A13C3CF128AFA2EF560FFF6492A76EB, moving to: C:\ProgramData\Package Cache\VSIXBootstrapper.<IP_ADDRESS>816\Microsoft.VisualStudio.AzureSphere.ProjectSystem.V16.vsix.
[13F0:13E8][2019-08-19T12:05:02]i052: Condition '(vsixQuiet = "yes") OR (WixBundleUILevel=2)' evaluates to true.
[13F0:13E8][2019-08-19T12:05:02]i301: Applying execute package: VSExtensionVSIXV15, action: Install, path: C:\ProgramData\Package Cache\VSIXBootstrapper.<IP_ADDRESS>816\VSIXBootstrapper.exe, arguments: '"C:\ProgramData\Package Cache\VSIXBootstrapper.<IP_ADDRESS>816\VSIXBootstrapper.exe" /admin /shutdownprocesses "Microsoft.VisualStudio.AzureSphere.ProjectSystem.V15.vsix" /q'
[13F0:1538][2019-08-19T12:05:02]i304: Verified existing payload: VSExtensionVSIXV16 at path: C:\ProgramData\Package Cache\VSIXBootstrapper.<IP_ADDRESS>816\VSIXBootstrapper.exe.
[13F0:1538][2019-08-19T12:05:02]i304: Verified existing payload: pay4F357484EB30226D85A1F8D7990E3A62 at path: C:\ProgramData\Package Cache\VSIXBootstrapper.<IP_ADDRESS>816\Microsoft.VisualStudio.AzureSphere.ProjectSystem.V15.vsix.
[13F0:1538][2019-08-19T12:05:02]i304: Verified existing payload: pay604BC1C19D2A4CFD8C3B77865142EA44 at path: C:\ProgramData\Package Cache\VSIXBootstrapper.<IP_ADDRESS>816\VSIXBootstrapper.exe.
[13F0:1538][2019-08-19T12:05:02]i304: Verified existing payload: pay7A13C3CF128AFA2EF560FFF6492A76EB at path: C:\ProgramData\Package Cache\VSIXBootstrapper.<IP_ADDRESS>816\Microsoft.VisualStudio.AzureSphere.ProjectSystem.V16.vsix.
[13F0:1538][2019-08-19T12:05:02]i305: Verified acquired payload: TapDriverInstaller at path: C:\ProgramData\Package Cache.unverified\TapDriverInstaller, moving to: C:\ProgramData\Package Cache{BF7D823B-6E5F-433B-9C85-E9EECB1124BC}v2.2.0\packages\TapDriverInstaller\TapDriverInstaller.msi.
[13F0:1538][2019-08-19T12:05:02]i305: Verified acquired payload: AzureSphereCore at path: C:\ProgramData\Package Cache.unverified\AzureSphereCore, moving to: C:\ProgramData\Package Cache{DEC4629D-08A5-4D6A-90D9-1E89B8024CFA}v<IP_ADDRESS>731\packages\AzureSphereCore\AzureSphereCore.msi.
[13F0:1538][2019-08-19T12:05:02]i305: Verified acquired payload: SlipService at path: C:\ProgramData\Package Cache.unverified\SlipService, moving to: C:\ProgramData\Package Cache{15D970F1-2AB1-4553-94E0-12DEC338AF1F}v<IP_ADDRESS>731\packages\SlipService\Azure Sphere Device Communication Service.msi.
[13F0:1538][2019-08-19T12:05:03]i304: Verified existing payload: Sysroot_index0 at path: C:\ProgramData\Package Cache{CB7B85C6-65E4-4313-B137-1CD5A66D52E3}v<IP_ADDRESS>866\Sysroot0.msi.
[13F0:1538][2019-08-19T12:05:04]i304: Verified existing payload: Sysroot_index1 at path: C:\ProgramData\Package Cache{F5C48017-9F0C-4496-A7F3-F7575F918838}v<IP_ADDRESS>931\Sysroot1.msi.
[13F0:1538][2019-08-19T12:05:05]i304: Verified existing payload: Sysroot_index2 at path: C:\ProgramData\Package Cache{992C25E5-6E67-4B8C-99A7-692329CE45D6}v<IP_ADDRESS>935\Sysroot2.msi.
[0B50:0B4C][2019-08-19T12:05:07]i319: Applied execute package: VSExtensionVSIXV15, result: 0x0, restart: None
[13F0:13E8][2019-08-19T12:05:07]i052: Condition '(vsixQuiet = "yes") OR (WixBundleUILevel=2)' evaluates to true.
[13F0:13E8][2019-08-19T12:05:07]i301: Applying execute package: VSExtensionVSIXV16, action: Install, path: C:\ProgramData\Package Cache\VSIXBootstrapper.<IP_ADDRESS>816\VSIXBootstrapper.exe, arguments: '"C:\ProgramData\Package Cache\VSIXBootstrapper.<IP_ADDRESS>816\VSIXBootstrapper.exe" /admin /shutdownprocesses "Microsoft.VisualStudio.AzureSphere.ProjectSystem.V16.vsix" /q'
[0B50:0B4C][2019-08-19T12:07:01]i319: Applied execute package: VSExtensionVSIXV16, result: 0x0, restart: None
[13F0:13E8][2019-08-19T12:07:01]i323: Registering package dependency provider: {BF7D823B-6E5F-433B-9C85-E9EECB1124BC}, version: 2.2.0, package: TapDriverInstaller
[13F0:13E8][2019-08-19T12:07:01]i301: Applying execute package: TapDriverInstaller, action: Install, path: C:\ProgramData\Package Cache{BF7D823B-6E5F-433B-9C85-E9EECB1124BC}v2.2.0\packages\TapDriverInstaller\TapDriverInstaller.msi, arguments: ' MSIFASTINSTALL="7" VSEXTUI="1" VSFOLDER=""'
[0B50:0B4C][2019-08-19T12:07:06]i319: Applied execute package: TapDriverInstaller, result: 0x0, restart: None
[13F0:13E8][2019-08-19T12:07:06]i325: Registering dependency: {afaa4203-0409-4e16-ad86-0c52321dc834} on package provider: {BF7D823B-6E5F-433B-9C85-E9EECB1124BC}, package: TapDriverInstaller
[13F0:13E8][2019-08-19T12:07:06]i323: Registering package dependency provider: {DEC4629D-08A5-4D6A-90D9-1E89B8024CFA}, version: <IP_ADDRESS>731, package: AzureSphereCore
[13F0:13E8][2019-08-19T12:07:06]i301: Applying execute package: AzureSphereCore, action: Install, path: C:\ProgramData\Package Cache{DEC4629D-08A5-4D6A-90D9-1E89B8024CFA}v<IP_ADDRESS>731\packages\AzureSphereCore\AzureSphereCore.msi, arguments: ' MSIFASTINSTALL="7" VSEXTUI="1" INSTALLFOLDER=""'
[0B50:0B4C][2019-08-19T12:07:07]i319: Applied execute package: AzureSphereCore, result: 0x0, restart: None
[13F0:13E8][2019-08-19T12:07:07]i325: Registering dependency: {afaa4203-0409-4e16-ad86-0c52321dc834} on package provider: {DEC4629D-08A5-4D6A-90D9-1E89B8024CFA}, package: AzureSphereCore
[13F0:13E8][2019-08-19T12:07:07]i323: Registering package dependency provider: {15D970F1-2AB1-4553-94E0-12DEC338AF1F}, version: <IP_ADDRESS>731, package: SlipService
[13F0:13E8][2019-08-19T12:07:07]i301: Applying execute package: SlipService, action: Install, path: C:\ProgramData\Package Cache{15D970F1-2AB1-4553-94E0-12DEC338AF1F}v<IP_ADDRESS>731\packages\SlipService\Azure Sphere Device Communication Service.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7" VSEXTUI="1" VSFOLDER=""'
[13F0:13E8][2019-08-19T12:20:04]e000: Error 0x80070643: Failed to install MSI package.
[13F0:13E8][2019-08-19T12:20:04]e000: Error 0x80070643: Failed to execute MSI package.
[0B50:0B4C][2019-08-19T12:20:04]e000: Error 0x80070643: Failed to configure per-machine MSI package.
[0B50:0B4C][2019-08-19T12:20:04]i319: Applied execute package: SlipService, result: 0x80070643, restart: None
[0B50:0B4C][2019-08-19T12:20:04]e000: Error 0x80070643: Failed to execute MSI package.
[13F0:13E8][2019-08-19T12:20:04]i318: Skipped rollback of package: SlipService, action: Uninstall, already: Absent
[0B50:0B4C][2019-08-19T12:20:04]i319: Applied rollback package: SlipService, result: 0x0, restart: None
[13F0:13E8][2019-08-19T12:20:04]i329: Removed package dependency provider: {15D970F1-2AB1-4553-94E0-12DEC338AF1F}, package: SlipService
[13F0:13E8][2019-08-19T12:20:04]i351: Removing cached package: SlipService, from path: C:\ProgramData\Package Cache{15D970F1-2AB1-4553-94E0-12DEC338AF1F}v<IP_ADDRESS>731
[13F0:13E8][2019-08-19T12:20:04]i326: Removed dependency: {afaa4203-0409-4e16-ad86-0c52321dc834} on package provider: {DEC4629D-08A5-4D6A-90D9-1E89B8024CFA}, package AzureSphereCore
[13F0:13E8][2019-08-19T12:20:04]i301: Applying rollback package: AzureSphereCore, action: Uninstall, path: (null), arguments: ' MSIFASTINSTALL="7" VSEXTUI="1" INSTALLFOLDER=""'
[0B50:0B4C][2019-08-19T12:20:06]i319: Applied rollback package: AzureSphereCore, result: 0x0, restart: None
[13F0:13E8][2019-08-19T12:20:06]i329: Removed package dependency provider: {DEC4629D-08A5-4D6A-90D9-1E89B8024CFA}, package: AzureSphereCore
[13F0:13E8][2019-08-19T12:20:06]i351: Removing cached package: AzureSphereCore, from path: C:\ProgramData\Package Cache{DEC4629D-08A5-4D6A-90D9-1E89B8024CFA}v<IP_ADDRESS>731
[13F0:13E8][2019-08-19T12:20:06]i326: Removed dependency: {afaa4203-0409-4e16-ad86-0c52321dc834} on package provider: {BF7D823B-6E5F-433B-9C85-E9EECB1124BC}, package TapDriverInstaller
[13F0:13E8][2019-08-19T12:20:06]i301: Applying rollback package: TapDriverInstaller, action: Uninstall, path: (null), arguments: ' MSIFASTINSTALL="7" VSEXTUI="1" VSFOLDER=""'
[0B50:0B4C][2019-08-19T12:20:10]i319: Applied rollback package: TapDriverInstaller, result: 0x0, restart: None
[13F0:13E8][2019-08-19T12:20:10]i329: Removed package dependency provider: {BF7D823B-6E5F-433B-9C85-E9EECB1124BC}, package: TapDriverInstaller
[13F0:13E8][2019-08-19T12:20:10]i351: Removing cached package: TapDriverInstaller, from path: C:\ProgramData\Package Cache{BF7D823B-6E5F-433B-9C85-E9EECB1124BC}v2.2.0
[13F0:13E8][2019-08-19T12:20:10]i052: Condition '(vsixQuiet = "yes") OR (WixBundleUILevel=2)' evaluates to true.
[13F0:13E8][2019-08-19T12:20:10]i301: Applying rollback package: VSExtensionVSIXV16, action: Uninstall, path: C:\ProgramData\Package Cache\VSIXBootstrapper.<IP_ADDRESS>816\VSIXBootstrapper.exe, arguments: '"C:\ProgramData\Package Cache\VSIXBootstrapper.<IP_ADDRESS>816\VSIXBootstrapper.exe" /admin /shutdownprocesses /u:Microsoft.VisualStudio.VC.AzureSphere.358C73EE-4D62-434F-AEFE-D915180CAC82 /q'
[0B50:0B4C][2019-08-19T12:21:27]i319: Applied rollback package: VSExtensionVSIXV16, result: 0x0, restart: None
[13F0:13E8][2019-08-19T12:21:27]i351: Removing cached package: VSExtensionVSIXV16, from path: C:\ProgramData\Package Cache\VSIXBootstrapper.<IP_ADDRESS>816
[13F0:13E8][2019-08-19T12:21:27]i052: Condition '(vsixQuiet = "yes") OR (WixBundleUILevel=2)' evaluates to true.
[13F0:13E8][2019-08-19T12:21:27]i301: Applying rollback package: VSExtensionVSIXV15, action: Uninstall, path: C:\ProgramData\Package Cache\VSIXBootstrapper.<IP_ADDRESS>816\VSIXBootstrapper.exe, arguments: '"C:\ProgramData\Package Cache\VSIXBootstrapper.<IP_ADDRESS>816\VSIXBootstrapper.exe" /admin /shutdownprocesses /u:Microsoft.VisualStudio.VC.FourByFour.750771ED-69BE-4B1A-BD6E-B336AC5EB960 /q'
[13F0:13E8][2019-08-19T12:21:27]e000: Error 0x80070003: Failed to CreateProcess on path: C:\ProgramData\Package Cache\VSIXBootstrapper.<IP_ADDRESS>816\VSIXBootstrapper.exe
[13F0:13E8][2019-08-19T12:21:27]e000: Error 0x80070003: Failed to execute EXE package.
[0B50:0B4C][2019-08-19T12:21:27]e000: Error 0x80070003: Failed to configure per-machine EXE package.
[0B50:0B4C][2019-08-19T12:21:27]i319: Applied rollback package: VSExtensionVSIXV15, result: 0x80070003, restart: None
[13F0:13E8][2019-08-19T12:21:27]i351: Removing cached package: VSExtensionVSIXV15, from path: C:\ProgramData\Package Cache\VSIXBootstrapper.<IP_ADDRESS>816
[13F0:13E8][2019-08-19T12:21:27]w353: Unable to remove cached package: VSExtensionVSIXV15, from path: C:\ProgramData\Package Cache\VSIXBootstrapper.<IP_ADDRESS>816, reason: 0x80070003. Continuing...
[13F0:13E8][2019-08-19T12:21:27]i372: Session end, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{afaa4203-0409-4e16-ad86-0c52321dc834}, resume: None, restart: None, disable resume: No
[13F0:13E8][2019-08-19T12:21:27]i330: Removed bundle dependency provider: {afaa4203-0409-4e16-ad86-0c52321dc834}
[13F0:13E8][2019-08-19T12:21:27]i352: Removing cached bundle: {afaa4203-0409-4e16-ad86-0c52321dc834}, from path: C:\ProgramData\Package Cache{afaa4203-0409-4e16-ad86-0c52321dc834}
[13F0:13E8][2019-08-19T12:21:27]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{afaa4203-0409-4e16-ad86-0c52321dc834}, resume: None, restart initiated: No, disable resume: No
[0B50:0B4C][2019-08-19T12:21:27]i399: Apply complete, result: 0x80070643, restart: None, ba requested restart:  No

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

ID: de08ad95-5a5b-7d0d-860c-f9eb2e20c25e
Version Independent ID: 496bd01d-da35-136d-cfec-c5b4c5479bab
Content: Set up your device and install the Azure Sphere SDK
Content Source: AzureSphere/articles/install/install.md
Product: azure-sphere
GitHub Login: @pennyo
Microsoft Alias: azurespheredocs

I have verified that three COM ports are opened when I plug in the Sphere device.

Hi - please can you:

save a copy of this file: c:\windows\serviceprofiles\localservice\appdata\local\Azure Sphere Tools\restore.json
delete this file from that location
retry the installation

Please let us know if this solves the problem and, if so, send the saved .json file to<EMAIL_ADDRESS>referencing this issue. Thanks.

Thanks for the quick response. Unfortunately this makes no difference. When I click cancel on the failure dialog, the installation does automatically undo the various stages. The Restore.json file was not replaced by a new one after the retried install.
The one I deleted contains only this:
[]

Sorry that didn't help.  One of my colleagues will continue to progress this ticket, and suggest next steps as soon as possible.

@richardtaylorrt the problem related by the correspondent there, resembles the first problem I developed. (And that's one of two reasons why I put mine aside for the moment.)
@glynj-bsquare  Did all of this happen after the computer was restarted? Or did you see this happen all the time during an install attempt?

The computer rebooted unattended over the weekend due to an OS update.
Visual Studio was not left running at the time, and the Sphere device was not connected at the time.
This morning I was unable to communicate to the device using azsphere - the error suggested I uninstall then reinstall the Sphere dev SDK.
I did the uninstall, whihc was successful, but now every time I try to install the SDK I get the same error.

Makes sense. Depending on the OS you run, its certainly possible that something else changed. Mind you the operative term is "certainly possible".

In case it's relevant, I'm running on Windows 10.

@glynj-bsquare Please follow the instructions from Richard and email us so we can get you help from a support engineer.
If you have access to a support plan: can you please file a support request @ https://aka.ms/azsupt?
If you do not have access to a support plan, please reach out<EMAIL_ADDRESS>with a link to this Doc/Issue as well as your subscription ID and we can help get the support ticket opened for this issue.

@Alberto-Vega-MSFT  how would you define a subscription ID? And this presupposes I did have an account with Azure in general, where would I find it?

@Alberto-Vega-MSFT I have already tried Richard's suggestion, but it made no difference.
I am following up with my company to see if we have a support contract. Like @DoctorWho8  I do not know what the subscription ID is or where to find it, but have contacted the community as you suggest to see if this can be expedited.

@glynj-bsquare @DoctorWho8 Please follow the steps to get your SubscriptionID: https://blogs.msdn.microsoft.com/mschray/2016/03/18/getting-your-azure-subscription-guid-new-portal/

@AshokPeddakotla-MSFT There are no subscriptions listed in my account. (The instructions are also out of date - there is no "Browse" option available in the portal's left hand pane.)

@glynj-bsquare You can click on All Services -> search Subscriptions

Please collect and share the results of azsphere get-support-data  to<EMAIL_ADDRESS>

I have done this, and it states that I have no subscriptions.

I also cannot run azsphere, as I cannot install it.

In my case I have not tried to install the SDK again. In my defense I am decidedly busy with other work, and since the azsphere idea was something that I am doing on my own, not as part of a company sponsored project, I can't bill things to a card for that purpose.

Subscription has now been found. I will create a support ticket and reference this discussion.

Sure. Please update this issue with the resolution so that it can be beneficial to the others.

Good to know. Now that the laptop has updated itself, I might even try to install the SDK again. And I might even try and create an account on Azure again.

@glynj-bsquare We will be closing this issue for now,  since it went to support.

Yo tuve la siguiente experiencia, realice la desinstalación, al volver a instalar este me marco erro al finalizar "azure sphere device communication service failed to start...." La solución en mi caso fue la siguiente.
Durante la instalación note que se creaba un nuevo adaptador de red de tipo "Tap-Windows Adapter V9" pero con el nombre Ethernet 1... en este punto actualice el nombre por Azure Sphere y le di continuar a la instalación en el botón de reintentar, la instalación finalizo de forma satisfactoria.
Al reclamar el dispositivo este volvió a marcar error , la solución fue la siguiente, tuve que setear la dirección IP (<IP_ADDRESS>) de forma manual en el apartado de TCP/IPv4 del adaptador "Azure Sphere".
Adjunto referencia donde viene esta especificación del adaptador de red para "Azure Sphere"
https://docs.microsoft.com/en-us/azure-sphere/network/ports-protocols-domains
Listo con esto resolví ambos problemas de comunicación e instalación para el uso de mi Tarjeta.
Yo tengo la MT3620

abrahamiab
You said "I had the following experience, I did the uninstallation, when reinstalling this I was wrong at the end "azure sphere device communication service failed to start ...." The solution in my case was the following.
During the installation I noticed that a new network adapter of the "Tap-Windows Adapter V9" type was created but with the Ethernet name 1 ... at this point I updated the name with Azure Sphere and I gave it to continue the installation in the button of retry, the installation completed successfully.
When claiming the device, this again marked an error, the solution was as follows, I had to set the IP address (<IP_ADDRESS>) manually in the TCP / IPv4 section of the "Azure Sphere" adapter.
Attachment reference where this specification of the network adapter for "Azure Sphere" comes
https://docs.microsoft.com/en-us/azure-sphere/network/ports-protocols-domains
Ready with this I solved both communication and installation problems for the use of my Card.
I have the MT3620 " (Translated via Google Translate)
Technically this a closed issue as one of the others will respond appropriately. However as it must be of interest to someone, I have posted this translation.


EBPF TCP flags start times always 0

I wanted to get the tcp flags times when using Ebpf but it is always return 0 and after some digging I discovered that in ebpf/common.h there is a function that suppose to init the flags times but the line
__u64 tm = flow->last; in the function inits tm with 0 every time.
As a work around I change the func to init tm with 1 and then I can get an indication that the flag was raised because that all I needed but I there is a way to understand why flow->last dont work I think that would sold the issue.

I submitted a fix, can you give it a try
#2151

Still doesn't work :(

would you be able to send a PR ? or can you point me the exact line ?

I tried to upload a new branch but I don't have permissions.
I just move line 242 to be above line 230 in ebpf/flow.c

could you try this one :
https://github.com/skydive-project/skydive/pull/2153

Closing it, please re-open if needed


Update R parameter constructor.

          > *Since this PR concerns the user interface, would be great if we could get some help for review from an R user's perspective @mayer79 @jameslamb*

Thanks for the @, sorry I did not get to it before this was merged.

The idea behind this constructor function is to offer an IDE-friendly way of creating and discovering XGBoost parameters, with full in-package documentation as is typical in R packages

I think it's a great idea, and would definitely be helpful for interactive development.
Some suggestions (to consider in follow-ups, given that this was already merged):

it would be good to have explicit unit tests on this new function, not just rely on implicit coverage from other tests. For example:

confirming that only non-NULL items show up in the return value
confirming that calling this with 0 arguments returns an empty list

I understand that existing names with . in them need to be preserved for backwards compatibility, but I'd stop adding new ones (e.g. I'd prefer xgb_params to xgb.params)

to reduce the risk of "R thinks this is an S3 method" confusion like the ones that led to #9577

I'd have asked to change the line wrapping of the roxygen comments instead of ignoring the project's preferred line length with # nolint comments

or at least, asked that the linter be allowed to cover the function signature, which it currently cannot because of this placement:

https://github.com/dmlc/xgboost/blob/85ccb8f88a00c131b508b780750bd17b0ac98e04/R-package/R/xgb.train.R#L811
I also would have asked for a little research supporting it being safe to change xgb.parameters to xgb.model.parameters without a deprecation cycle. For example, it looks to me like nothing on CRAN is currently using xgb.parameters (https://github.com/search?q=org%3Acran "xgb.parameters"&type=code), so I guess it at least won't break anything on CRAN. (I don't recall where the discussion about xgboost2 vs. releasing this as a new version of xgboost ended, disregard this last comment if the plan is to release a new package).
Originally posted by @jameslamb in https://github.com/dmlc/xgboost/issues/11072#issuecomment-2526860694

cc @david-cortes
Converted from https://github.com/dmlc/xgboost/pull/11072#issuecomment-2526860694 .

Added a PR with tests: https://github.com/dmlc/xgboost/pull/11084
To address the other points:

I understand that existing names with . in them need to be preserved for backwards compatibility, but I'd stop adding new ones (e.g. I'd prefer xgb_params to xgb.params)

We've been adding all new non-method functions with the xgb. prefix. These haven't been a problem as there's no "xgb" class (nearest are "xgb.Booster" and "xgb.DMatrix", which do not clash with "xgb." as prefix). I wouldn't want to change that as it makes the code calls similar to the python examples where xgboost is imported as xgb, and changing it for some functions but not others would be confusing.

I'd have asked to change the line wrapping of the roxygen comments instead of ignoring the project's preferred line length with # nolint comments

I think the closer the R docs stay to the original .rst, the easier it'd be to update them later on. The .rst file doesn't manually break lines, relying on sphinx doing the line wrapping instead. Current logic (nolint) makes it easy to copy-paste from them, which is how the file was generated.

or at least, asked that the linter be allowed to cover the function signature, which it currently cannot because of this placement:

That's already checked by R CMD check.

I also would have asked for a little research supporting it being safe to change xgb.parameters to xgb.model.parameters without a deprecation cycle.

We haven't decided on that aspect yet, but we've already established that we're going to do big breaking changes with the next major release. There will be no deprecation cycle, other than for a few renames.

Thanks very much for the tests and explanation @david-cortes . If the decisions about continuing the use of names with . in them and making big breaking changes have already been decided, I won't re-litigate them.
The point about copying directly from other non-R docs is a good justification to ignore line-length preferences there, I hadn't considered that it was literally copying and pasting.
There's just one thing I want to clarify:

That's already checked by R CMD check.

R CMD check will check for things like "argument in signature but not in docs" (and vice-versa), but it won't check for the types of preferences that might be enforced with {lintr}, like indentation, comma-first vs. comma-last, or spacing around the =. Today this new function has all = NULL in the signature but if that ever changed and some arguments defaulted to other R objects, then R CMD check would also not enforce things like this project's preference for using the form "single-string" instead of c("single-string"):
https://github.com/dmlc/xgboost/blob/f4f3bd4e61a2375f9ea8cbb2dd1d3af7d5b09cf4/ops/script/lint_r.R#L50
It's for those reasons that I think the # nolint should have been placed before and not after the signature.

It's for those reasons that I think the # nolint should have been placed before and not after the signature.

That could potentially bring problems later on when #' and # are interleaved, with both roxygen and git.

Today this new function has all = NULL in the signature but if that ever changed and some arguments defaulted to other R objects, then R CMD check would also not enforce things like this project's preference for using the form "single-string" instead of c("single-string"):

I don't think that'd matter much since the signature that's written into the .Rd file gets post-processed by roxygen, so those details would be lost.

but it won't check for the types of preferences that might be enforced with {lintr}, like indentation, comma-first vs. comma-last, or spacing around the =.

Should be fixed here: https://github.com/dmlc/xgboost/pull/11090


cpptoml does not allow empty inline objects

as e.g. used in redox toml files
🚫 Input TOML could not be parsed
Value must follow after a '=' at line 13
  12: #binutils = {}
➤ 13: contain = {}
  14: coreutils = {}

Simplest example:
[foo]
 bar = {}

echo -e "[foo]\n bar = {}" | ./tomlutil -
🚫 Input TOML could not be parsed
Value must follow after a '=' at line 2
  1: [foo]
➤ 2:  bar = {}

Should be fixed with your PR now.


[ROCm] Adding Cuda Alias to Gpu functions

This PR is a follow-up to PR #24293. This PR depends on & includes code changes from PR #28116. Code updates for this PR are in the tensorflow/core/util path
Through utility functions defined in gpu_cuda_alias.h, this PR provides a Cuda* alias to existing Gpu* functions. The reason for this PR is to create backward compatibility to both the TensorFlow master branch as well as ROCm's develop-upstream branch. It allows TensorFlow master branch to slowly deprecate Cuda* aliased function, to the final goal of using GPU as the prefix to unify both Cuda and ROCm builds. All aliasing is done through perfect forwarding macro so that it is easy to maintain/take out.
Tests performed: Both Cuda/ROCm build successfully in both master and develop-upstream branch.
@whchung @deven-amd

I don't have the expertise to review this; removing myself.

Working on the broken builds...

Will post back to address review feedback after PR439 approved. Will also integrate macro only change from GPU_LAUNCH_KERNEL to GpuLaunchKernel

@jerryyin multiple definition of `gpuGetErrorString(cudaError)'

@jerryyin multiple definition of `gpuGetErrorString(cudaError)'

I was trying to forwarding the full set of __host__ and __device__ identifiers here according to Cuda's documentation here, but forgot that this is a header file with the function definition. When multiple compilation unit pulls it in, the compiler complains. I added inline identifier and local compilation works.

Hi Zhuoran. I started the rename from our side, sorry that I didn't look more carefully at your approach first. Generally, please do not mix several changes into the same PR. It makes it hard to understand and review.
Could you please make a PR that introduces the macros only, and a follow-up to generate the various alias functions/macros/types, maybe even split into multiple PRs. At that point I can start preparing changes to use the new 'gpu' symbols.

Hi Zhuoran. I started the rename from our side, sorry that I didn't look more carefully at your approach first. Generally, please do not mix several changes into the same PR. It makes it hard to understand and review.
Could you please make a PR that introduces the macros only, and a follow-up to generate the various alias functions/macros/types, maybe even split into multiple PRs. At that point I can start preparing changes to use the new 'gpu' symbols.

@chsigg No worries, good feedback on breaking the PR. I'm planning on doing the following:

[ ] One PR for create forwarding type macro, and corresponding changes in using the marco
[ ] One PR for create forwarding host function macro, and corresponding changes in using the macro
[ ] One PR for create forwarding device function macro, and corresponding changes in using the macro
[ ] One PR for create GpuLaunchKernel
[ ] One PR for updating GPU_LAUNCH_KERNEL to GpuLaunchKernel
[ ] One PR for Removing GPU_LAUNCH_KERNEL

I will post back to here I as make progress, with the final goal of closing the large PR.

Closing the review as all sub-PRs are merged


How to read Android Demo Detection Model Priors.pb file ?

Hello !
I would like to look into the assets file : multibox_location_priors.pb which contains boxpriors locations.
I want to use them in a iPythonNotebook to test the model with offline images but I don't know how to access properly to the values for all locations.
Is there any easy way to parse the file and get the locations values like it is possible to do with graph.pb file using these lines
with tf.gfile.FastGFile("graph.pb", 'rb') as f:
    graph_def = tf.GraphDef()
    graph_def.ParseFromString(f.read())

Thanks in advance for your help
Alex

@AlexandreBriot The easiest thing to do would be to add tensorflow/examples/android/proto/box_coder.proto to CORE_PROTO_SRCS in tensorflow/core/BUILD (you may need to copy the file), and then you should be able to rebuild TF with support for reading it. It's not there already simply because it's a very model-specific proto only currently used for the demo.

@andrewharp Hello Andrew and thank you for your precious help !
I followed your instructions and here is where I am.

I modified  CORE_PROTO_SRCS in tensorflow/core/BUILD adding "framework/box_coder.proto",

I copied box_coder.proto in the corresponding core/framework/ directory

I rebuild tensorflow from source but get some errors related to proto version 2 vs 3

I modified box_coder.proto by doing these changes

Change syntax = "proto2"; to syntax = "proto3";
Changepackage org_tensorflow_demo;to package tensorflow;
Removing all optional and all default value
ex : optional float mean = 1 [default = 0.0]; becomes float mean = 1;
Suppressing all ; after message section

Is that correct ? Or is there some inexact/unappropriate changes ?

Now I am able to import this freshly built tensorflow in my iPythonNotebook
The new proto definition is supposed to decode my box-priors.pb file
I want to do so using the lines as I can do for GraphDef but I don't know which Object I should create to replace GraphDef one and then loading data with ParseFromString method ...

with tf.gfile.FastGFile("box-priors.pb", 'rb') as f:
    priors = tf._?Object?_()
    priors.ParseFromString(f.read())

Could you give me your advice on that part ?
Thanks in advance for your help
Alex

@AlexandreBriot We'll probably update the code soon to just load from a txt file, as separately supporting a  proto build in the Android example adds disproportionate overhead.
In the meantime, I've exported entire box prior proto to text, which you should be able to easily load into your Python code:
https://gist.github.com/andrewharp/136b07af1f221e9c95b383889f9911e0

@andrewharp Thanks for your answer !

@andrewharp  I have a trained spam detection model trained using keras and have got the .pb I am trying it to implement it into a mobile app. Can you please guide me to the right documentation please. It will be of great help.


app report istio-proxy close connection unexpectly, and raise socket hang up

Bug Description
app report istio-proxy close connection unexpectable, and raise socket hang up
SERVER ERROR request to http://device-web.xxx-production-device.svc.cluster.local/ failed, reason: socket hang up
I found some conf in envoy like:
common_http_protocol_options:
  headers_with_underscores_action: REJECT_REQUEST
  idle_timeout: 900s

I guess it is by design for istio close connection after idle. am I right?
Should client side handle such case instead of istio?
Version
istio 1.6.8
k8s 1.17

Additional Information
No response

I think the issue is as same as:
https://github.com/istio/istio/issues/36499


The command failed with an unexpected error. Here is the traceback: Azure sandbox

This is autogenerated. Please review and update as needed.
Describe the bug bug occurred in training: https://learn.microsoft.com/en-us/training/modules/describe-core-architectural-components-of-azure/4-exercise-explore-learn-sandbox
Command Name
az interactive
Errors:
The command failed with an unexpected error. Here is the traceback:
No module named 'prompt_toolkit.interface'
Traceback (most recent call last):
  File "/usr/lib64/az/lib/python3.9/site-packages/knack/cli.py", line 233, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 663, in execute
    raise ex
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 697, in _run_job
    result = cmd_copy(params)
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 333, in __call__
    return self.handler(*args, **kwargs)
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
    return op(**command_args)
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/command_modules/interactive/custom.py", line 41, in start_shell
    azext_interactive.start_shell(cmd, style=style)
  File "/home/brandon_hertel/.azure/cliextensions/interactive/azext_interactive/__init__.py", line 10, in start_shell
    from .azclishell.app import AzInteractiveShell
  File "/home/brandon_hertel/.azure/cliextensions/interactive/azext_interactive/azclishell/app.py", line 33, in <module>
    from prompt_toolkit.interface import Application, CommandLineInterface
ModuleNotFoundError: No module named 'prompt_toolkit.interface'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az interactive

Expected Behavior
Environment Summary
Linux-5.4.0-1091-azure-x86_64-with-glibc2.35 (Cloud Shell), CBL-Mariner/Linux
Python 3.9.13
Installer: RPM

azure-cli 2.41.0

Extensions:
interactive 0.4.5
ai-examples 0.2.5
ml 2.10.0
ssh 1.1.2

Dependencies:
msal 1.20.0b1
azure-mgmt-resource 21.1.0b1

Additional Context

Duplicate of https://github.com/Azure/azure-cli/issues/24213


Move Github OAuth secret to Rails secrets.yml file

Previously we were using a home grown solution requiring the secret to be placed in /app/kochiku/secrets/. This was put into place well be before Rails 4.1 introduced the secrets.yml feature. We can just use that now.

On second thought, this should go into the git_servers section of config/application.yml as a location to the oauth file.


Existential crisis

Hey guys,
I'm doubting my approach, if my API token is protected by this plugin like this:
val headers = HashMap<String, String>()
headers["api-token"] = Secrets().getApiTokenProd(requireContext().packageName)
ApiService.getServerStatus(headers) ()

Couldn't the the hacker that got his hands on the code via disassembly simply set a breakpoint there and read the token?
How have I protected the token then? 🤔

Hello @houmie , as said in the Readme nothing is unbreakable. But a hacker should not be able to execute your code in an IDE with all keys set up inside.
If your are worried about your code accessibility in production I encourage you to use obfuscation of your code provided by , for example, proguard.

Hi Ben,
Thank you for your reply.  Yes, you are right. They can see the code after a disassembly but they won't be able to run it in a IDE like I would do. Hence it's important to hide the obvious tokens from plain sight, so that they can't read them to access the API.
I have one last question. Why is it the name -PkeyName usually autogenerated, unless explicitly specified? If they can't read the key value, why does it manner that I named it ProductionToken or something unrecognisable?
Thanks,
Houman

@houmie your code can be extracted and some value can be read. The key is random by default but you can provide the name you want. It is your choice.
To understand more how works this library, you can decompile your apk file and see what hackers can see with apktool: https://ibotpeaches.github.io/Apktool/


Questions about the training settings

Hi! I am really interested in this fascinating work. However, I have some questions about the training methods for the transformer model.
In the paper you mention the transformer model is trained with learning rate = 6e-4 but do not say which lr decay method you are using, which I am curious about. I am also curious about the number of layers in the encoder and decoder.
Could you please demonstrate more specifically about the training settings? It will be more convenient for someone like me who want to reproduce your results if you could just publish your training source codes.
Thank you very much!

I don't think they use a learning rate decay. At least it is not mentioned anywhere. They do train on all tasks simultaneously (according to the first author) for 500k steps with the attention-is-all-you-need transformer architecture which is a 6 layer encoder and decoder with a hidden size of 512 and a dense filter size of 2048. The batch size is 1024 so you will need some serious compute in order to reproduce this. With this config trained on 4 V100 GPUs, you can do 50k steps in ~13h.
They used the tensor2tensor implementation of the transformer. So technically the code is public. Good luck with that.
Have you had any success @mayukuner?

That's correct: no learning rate decay for the results reported in the paper. 6 layers in the decoder and encoder.

@ischlag Not even close to success. I used transformer_base_v1 as the base parameter set and modified it a little by adding a constant lr scheduler, a warmup procedure, and other stuff like this:
PROBLEM=algorithmic_math_deepmind_all
MODEL=transformer
HPARAMS=transformer_base_v1
t2t-trainer    --data_dir=$DATA_DIR    --problem=$PROBLEM    --model=$MODEL    --hparams_set=$HPARAMS    --output_dir=$TRAIN_DIR    --worker_gpu=8    --hparams='max_length=64,num_hidden_layers=6,learning_rate=6e-4,learning_rate_schedule=constant*linear_warmup,learning_rate_constant=6e-4,clip_grad_norm=0.1,optimizer_adam_beta2=0.995,batch_size=8192'
And the result is:

By the way, I changed the dataset generator a little by random selecting training data from train-easy, train-medium, and train-hard to make the dataset's size approximately 2M. The validation set is sampled from interpolation.
@davidsaxton Have you used curriculum training? I don't think you have while I really couldn't figure out why I cannot reproduce your results. Am I missing something here?

I'd highly recommend to not deviate from the hyperparameters that are given in the paper. The transformer architecture is rather sensible to those. Remove your schedule and set the batch_size to 1024. Then train for 500k steps. Make sure your accuracy is 1 for getting all output tokens right and 0 for getting them even just one wrong (no per symbol accuracy is reported).

@ischlag I am trying my best to get close to the settings in the paper.
As you can see, the batch_size here is the maximum tokens per batch per GPU, so overall each batch contains 8192*8 tokens, which is close to 1024 sentences per batch.
Plus, I did not use any scheduler except for the warmup, the learning rate curve is as follows:

Also, the reported accuracy_per_sequence is exactly the criterion for this dataset as the paper states.
So I guess I am not doing anything wrong here, right?

Well, I'm not sure how I'm supposed to "see" that. If you are certain that batch_size is actually the number of tokens per GPU instead of the number of samples used for one step, then so be it.

I changed the dataset generator a little by random selecting training data

Are you sure this is not going to skip data? The tf.data pipeline might do some caching and only goes through the generator once. Unfortunately, it is virtually impossible for me to tell by looking at the t2t code.

@ischlag Sorry I did not explain it well because I thought you are familiar with T2T. The generator in T2T generates 2 million (question, answer) pairs per module. So I have to change it to make it generate 2M samples in total. The data generation procedure has been verified.

I'm somewhat familiar with it but I decided to not use it due to its obscurity. I'm just trying to help you here. We are working on reproducing it ourselves with a clean PyTorch implementation and I'll post the results one we managed.
That said, you should not have 2M samples in total but n * 2M where n is the number of modules (I think 56 or so). Furthermore, it is not clear to me how you encode the characters. Your gist file says text_problems.VocabType.CHARACTER which indicates byte-level encoding. I might be wrong on that though.
If that also doesn't help then I'm out of ideas.

@ischlag You are right, I missed per module in the paper. So I guess 2M * 56 sequences should be used for training. Thank you for your help and look forward to your result!

@mayukuner I'm currently training 3 baselines with my PyTorch implementation. The best result so far is 50% accuracy on all interpolation data after 45k steps and improving. So this starts to look promising. However, this is with a learning rate of 1e-4, not 6e-4. The 6e-4 run is stuck at a loss of 3.15 and 0% train accuracy even after 50k steps.
@davidsaxton Are you sure your learning rate in the paper is 6e-4 and not 6e-5?

@ischlag Have you clipped the gradients of the tensors? You may also try to use warmup in the beginning of the training stage. The LR of 6e-4 seems OK to me. With tensor2tensor, the model can be trained to have an accuracy of 70% on interpolation test after 300k steps.

Yes, I'm clipping the gradient norm of the parameters at 0.1. 6e-4 doesn't work at all. Even 3e-4 doesn't work at all. I've been very carefully going through my implementation several times.
My parameters are initialized with a=sqrt(6/in_out_avg) drawing from U[-a,a]. I share the Embedding matrix with the last layer before the softmax. I only scale the Embedding by sqrt(d_model) and I scale the dot products by 1/sqrt(d_k). Beta1 0.9, beta2 0.995. With the default epsilon. The Embedding I scale just like in the official transformer code but I'm not sure why it is sqrt(d_model). The one for the keys makes sense though. @mayukuner are you doing the same?
I'm still training and I'm now at 60% interpolation accuracy after 120k steps. So it looks good, just not with the right learning rate for me.

@ischlag I clipped the gradient absolute value not norm (i.e., |g_i| <= 0.1 for every gradient index i)


There are some installation problems such as 'tflite-model-maker'.

System information

OS Platform and Distribution: macOS 13.3.1 (MacBook Pro M2)
TensorFlow installed from (source or binary): tf-nightly 2.14.0.dev20230503
TensorFlow version (or github SHA if from source): Version:  2.14.0-dev20230503
Python Version(Default): Python 3.11.3

Provide the text output from 'tflite-model-maker'
# Summary: Successfully installed TensorFlow(2.14.0-dev20230503) but struggling about installing tflite-model-maker
#
sudo pip3 install tflite-model-maker
haesunglee@MacBookPro14-haesunglee ~ % sudo pip3 install tflite-model-maker
Password:
WARNING: The directory '/Users/haesunglee/Library/Caches/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Collecting tflite-model-maker
  Downloading tflite_model_maker-0.4.2-py3-none-any.whl (577 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 577.3/577.3 kB 6.4 MB/s eta 0:00:00
Collecting tf-models-official==2.3.0 (from tflite-model-maker)
  Downloading tf_models_official-2.3.0-py2.py3-none-any.whl (840 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 840.9/840.9 kB 7.0 MB/s eta 0:00:00
...
...
...
Collecting tflite-model-maker
  Downloading tflite_model_maker-0.1.0-py3-none-any.whl (84 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 84.6/84.6 kB 6.1 MB/s eta 0:00:00
ERROR: Cannot install tflite-model-maker==0.1.2, tflite-model-maker==0.2.0, tflite-model-maker==0.2.1, tflite-model-maker==0.2.2, tflite-model-maker==0.2.3, tflite-model-maker==0.2.4, tflite-model-maker==0.2.5, tflite-model-maker==0.3.0, tflite-model-maker==0.3.1, tflite-model-maker==0.3.2, tflite-model-maker==0.3.3, tflite-model-maker==0.3.4, tflite-model-maker==0.4.0, tflite-model-maker==0.4.1 and tflite-model-maker==0.4.2 because these package versions have conflicting dependencies.

The conflict is caused by:
    tflite-model-maker 0.4.2 depends on tflite-support>=0.4.2
    tflite-model-maker 0.4.1 depends on tflite-support-nightly
    tflite-model-maker 0.4.0 depends on tflite-support>=0.4.0
    tflite-model-maker 0.3.4 depends on tflite-support>=0.3.1
    tflite-model-maker 0.3.3 depends on tflite-support>=0.3.1
    tflite-model-maker 0.3.2 depends on tflite-support>=0.1.0rc4
    tflite-model-maker 0.3.1 depends on tflite-support>=0.1.0rc4
    tflite-model-maker 0.3.0 depends on tflite-support>=0.1.0rc4
    tflite-model-maker 0.2.5 depends on tflite-support==0.1.0rc4
    tflite-model-maker 0.2.4 depends on tflite-support==0.1.0rc4
    tflite-model-maker 0.2.3 depends on tflite-support==0.1.0rc3.dev2
    tflite-model-maker 0.2.2 depends on tflite-support==0.1.0rc3.dev2
    tflite-model-maker 0.2.1 depends on tflite-support==0.1.0rc3.dev2
    tflite-model-maker 0.2.0 depends on tflite-support==0.1.0rc3.dev2
    tflite-model-maker 0.1.2 depends on tflite-support==0.1.0rc3.dev2

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
haesunglee@MacBookPro14-haesunglee ~ %
haesunglee@MacBookPro14-haesunglee ~ %

Last year I successfully installed tflite-model-maker on my 1st mac. I'm still using it on my 1st mac.
Please help me update and fix the tflite-model-maker.

Hi @cugfk ,
This is known issue and our dev team already working on it at #60431 . The problem mainly here might be due to Python version compatibility. If you are Ok with downgrading python to 3.9.x version and also few other dependencies like numpy and others which you may get under log stack. More context can be found in the mentioned ticket here. Thanks!

Hi @cugfk ,
This is known issue and our dev team already working on it at #60431 . The problem mainly here might be due to Python version compatibility. If you are Ok with downgrading python to 3.9.x version and also few other dependencies like numpy and others which you may get under log stack. More context can be found in the mentioned ticket here. Thanks!

=========================================
Thank you for helping it but I'm still struggling.
Let's have a look.
System information

OS Platform and Distribution: macOS 13.3.1 (MacBook Pro M2)
tensorflow-macos Version:         2.12.0
tensorflow-metal Version:        0.8.0
Python Version: Python 3.9.16
Pip versions:  pip 23.0.1 from /Users/haesunglee/miniconda/lib/python3.9/site-packages/pip (python 3.9)
TensorFlow Version:  2.12.0
numpy Version:  1.24.3

My log:
haesunglee@MacBookPro14-haesunglee ~ %
haesunglee@MacBookPro14-haesunglee ~ % sudo pip3 install tflite-model-maker
Password:
WARNING: The directory '/Users/haesunglee/Library/Caches/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Collecting tflite-model-maker
Downloading tflite_model_maker-0.4.2-py3-none-any.whl (577 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 577.3/577.3 kB 12.6 MB/s eta 0:00:00
Collecting librosa==0.8.1
Downloading librosa-0.8.1-py3-none-any.whl (203 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 203.8/203.8 kB 12.1 MB/s eta 0:00:00
Collecting lxml>=4.6.1
...
...
...
INFO: pip is looking at multiple versions of sentencepiece to determine which version is compatible with other requirements. This could take a while.
Collecting sentencepiece
Downloading sentencepiece-0.1.98-cp39-cp39-macosx_11_0_arm64.whl (1.2 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.2/1.2 MB 2.1 MB/s eta 0:00:00
Downloading sentencepiece-0.1.97-cp39-cp39-macosx_11_0_arm64.whl (1.1 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.1/1.1 MB 2.5 MB/s eta 0:00:00
Downloading sentencepiece-0.1.96.tar.gz (508 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 508.6/508.6 kB 1.4 MB/s eta 0:00:00
Preparing metadata (setup.py) ... done
Downloading sentencepiece-0.1.95.tar.gz (508 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 508.7/508.7 kB 2.1 MB/s eta 0:00:00
Preparing metadata (setup.py) ... done
Downloading sentencepiece-0.1.94.tar.gz (507 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 507.5/507.5 kB 2.5 MB/s eta 0:00:00
Preparing metadata (setup.py) ... done
Downloading sentencepiece-0.1.91.tar.gz (500 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 500.5/500.5 kB 2.6 MB/s eta 0:00:00
**Preparing metadata (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [2 lines of output]
/bin/sh: pkg-config: command not found
Failed to find sentencepiece pkgconfig
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.**
haesunglee@MacBookPro14-haesunglee ~ %

@pjpratik , Please look into the issue. Thanks!

Hi @cugfk
The tflite-model-maker installation has a problem and our team is working on it.
Meanwhile, if you are trying to perform image classification, you can try out the MediaPipe Model Maker ImageClassifier API.
Thanks.

Hi @cugfk
The tflite-model-maker installation has a problem and our team is working on it.
Meanwhile, if you are trying to perform image classification, you can try out the MediaPipe Model Maker ImageClassifier API.
Thanks.

Thank you for helping but there are some problems.
Let's have a look.
System information

OS Platform and Distribution: macOS 13.3.1 (MacBook Pro M2)
tensorflow-macos Version: 2.12.0
tensorflow-metal Version: 0.8.0
Python Version: Python 3.9.16
Pip versions: pip 23.0.1 from /Users/haesunglee/miniconda/lib/python3.9/site-packages/pip (python 3.9)
TensorFlow Version: 2.12.0
numpy Version: 1.24.3

My log:
`
haesunglee@MacBookPro14-haesunglee ~ % sudo pip3 install mediapipe-model-maker
Password:
WARNING: The directory '/Users/haesunglee/Library/Caches/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Collecting mediapipe-model-maker
Downloading mediapipe_model_maker-<IP_ADDRESS>-py3-none-any.whl (106 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 106.3/106.3 kB 13.9 MB/s eta 0:00:00
Requirement already satisfied: absl-py in ./miniconda/lib/python3.9/site-packages (from mediapipe-model-maker) (1.4.0)
INFO: pip is looking at multiple versions of mediapipe-model-maker to determine which version is compatible with other requirements. This could take a while.
Downloading mediapipe_model_maker-<IP_ADDRESS>-py3-none-any.whl (106 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 106.3/106.3 kB 12.7 MB/s eta 0:00:00
Downloading mediapipe_model_maker-<IP_ADDRESS>-py3-none-any.whl (7.2 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 7.2/7.2 MB 11.7 MB/s eta 0:00:00
Downloading mediapipe_model_maker-<IP_ADDRESS>-py3-none-any.whl (7.2 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 7.2/7.2 MB 11.7 MB/s eta 0:00:00
Requirement already satisfied: mediapipe>=0.9.0 in ./miniconda/lib/python3.9/site-packages (from mediapipe-model-maker) (<IP_ADDRESS>)
Requirement already satisfied: numpy in ./miniconda/lib/python3.9/site-packages (from mediapipe-model-maker) (1.23.5)
Requirement already satisfied: opencv-python in ./miniconda/lib/python3.9/site-packages (from mediapipe-model-maker) (<IP_ADDRESS>)
Downloading mediapipe_model_maker-0.1.0-py3-none-any.whl (7.0 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 7.0/7.0 MB 11.7 MB/s eta 0:00:00
ERROR: Cannot install mediapipe-model-maker==0.1.0, mediapipe-model-maker==<IP_ADDRESS>, mediapipe-model-maker==<IP_ADDRESS>, mediapipe-model-maker==<IP_ADDRESS> and mediapipe-model-maker==<IP_ADDRESS> because these package versions have conflicting dependencies.
The conflict is caused by:
mediapipe-model-maker <IP_ADDRESS> depends on mediapipe==<IP_ADDRESS>
mediapipe-model-maker <IP_ADDRESS> depends on mediapipe==<IP_ADDRESS>
mediapipe-model-maker <IP_ADDRESS> depends on mediapipe==<IP_ADDRESS>
mediapipe-model-maker <IP_ADDRESS> depends on tensorflow>=2.10
mediapipe-model-maker 0.1.0 depends on tensorflow>=2.10
To fix this you could try to:

loosen the range of package versions you've specified
remove package versions to allow pip attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
haesunglee@MacBookPro14-haesunglee ~ %
`

Hi @cugfk
Sorry for the inconvenience caused. The mediapipe model maker is yet to support on arm mac devices. As a workaround please use colab for using the mediapipe model maker.
Please check this sample gist on getting started and refer to this documentation on customizing the image classifier using model maker.
Thanks.

Still facing this issue
`ERROR: Cannot install tflite-model-maker==0.1.2, tflite-model-maker==0.2.0, tflite-model-maker==0.2.1, tflite-model-maker==0.2.2, tflite-model-maker==0.2.3, tflite-model-maker==0.2.4, tflite-model-maker==0.2.5, tflite-model-maker==0.3.3, tflite-model-maker==0.3.4, tflite-model-maker==0.4.0, tflite-model-maker==0.4.1 and tflite-model-maker==0.4.2 because these package versions have conflicting dependencies.
The conflict is caused by:
tflite-model-maker 0.4.2 depends on numba==0.53
tflite-model-maker 0.4.1 depends on numba==0.53
tflite-model-maker 0.4.0 depends on numba==0.53
tflite-model-maker 0.3.4 depends on numba==0.53
tflite-model-maker 0.3.3 depends on numba==0.53
tflite-model-maker 0.2.5 depends on tflite-support==0.1.0rc4
tflite-model-maker 0.2.4 depends on tflite-support==0.1.0rc4
tflite-model-maker 0.2.3 depends on tflite-support==0.1.0rc3.dev2
tflite-model-maker 0.2.2 depends on tflite-support==0.1.0rc3.dev2
tflite-model-maker 0.2.1 depends on tflite-support==0.1.0rc3.dev2
tflite-model-maker 0.2.0 depends on tflite-support==0.1.0rc3.dev2
tflite-model-maker 0.1.2 depends on tflite-support==0.1.0rc3.dev2
To fix this you could try to:

loosen the range of package versions you've specified
remove package versions to allow pip attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
`

Still facing this issue `ERROR: Cannot install tflite-model-maker==0.1.2, tflite-model-maker==0.2.0, tflite-model-maker==0.2.1, tflite-model-maker==0.2.2, tflite-model-maker==0.2.3, tflite-model-maker==0.2.4, tflite-model-maker==0.2.5, tflite-model-maker==0.3.3, tflite-model-maker==0.3.4, tflite-model-maker==0.4.0, tflite-model-maker==0.4.1 and tflite-model-maker==0.4.2 because these package versions have conflicting dependencies.
The conflict is caused by: tflite-model-maker 0.4.2 depends on numba==0.53 tflite-model-maker 0.4.1 depends on numba==0.53 tflite-model-maker 0.4.0 depends on numba==0.53 tflite-model-maker 0.3.4 depends on numba==0.53 tflite-model-maker 0.3.3 depends on numba==0.53 tflite-model-maker 0.2.5 depends on tflite-support==0.1.0rc4 tflite-model-maker 0.2.4 depends on tflite-support==0.1.0rc4 tflite-model-maker 0.2.3 depends on tflite-support==0.1.0rc3.dev2 tflite-model-maker 0.2.2 depends on tflite-support==0.1.0rc3.dev2 tflite-model-maker 0.2.1 depends on tflite-support==0.1.0rc3.dev2 tflite-model-maker 0.2.0 depends on tflite-support==0.1.0rc3.dev2 tflite-model-maker 0.1.2 depends on tflite-support==0.1.0rc3.dev2
To fix this you could try to:
1. loosen the range of package versions you've specified

2. remove package versions to allow pip attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts `

I checked numba version support for python version, It's only up to python3.9.
So I changed my python version to python3.9 then It's solved


Proposed R21C changes 2024-01-29

Zero-diff from the GCM perspective

Interesting CI failure. I don't have time to investigate now, but since I approved, @sdrabenh can pull in if needed. I'll try and figure out how to fix up the R21C branch later

@rtodling @elakkraoui these PR were initially marked as drafts for reviewing. Clicking the button "Ready for review" now so they are regular PRs. Please keep in mind CircleCI may fail for some of these PRs as we don't have an automated way to checkout latest within the R21C branches just yet.

@rtodling @elakkraoui these PR were initially marked as drafts for reviewing. Clicking the button "Ready for review" now so they are regular PRs. Please keep in mind CircleCI may fail for some of these PRs as we don't have an automated way to checkout latest within the R21C branches just yet.

Indeed, I have a test to fix up the CI in #342 I'll monitor. If it works, we can merge it into this PR.