can't record the sound on windows 10

the issue is simple when i record anything on the desktop or on apps when i finish the record and i save the video i can't hear any sound is this an issue on the app itself or only on my device ? please reply fast.

Please use the search function, this has come up multiple times.
Also, it's a bit rude to ask someone to reply quickly like that.

thank you sir i saw that but i still don't know how to enable the Windows.Media.Transcoding or atleast add a Windows Audio Session if you could just show me how i would be so gratfull. and also i like your programe its lightweigh than other programs and  its the thing i was looking for for that's why im trying to make it work sir.

@BRUZON444 This open source project Fluent-Screen-Recorder may help you. It is based on SimpleRecorder and adds the feature to record audio.


API should switch to UUIDs for entity Identification

A binary ID is cumbersome and nonstandard on the web. From looking through the other issues this seems to be a leaky abstraction of the implementation detail;  the ID's in the database are encoded into binary values to increase indexing speed. While fine to use such an optimization on the database side of things it seems unwise to leak that to the API. Much more easily the API can consume UUID values and convert them to whatever you want.
UUIDs are the only type of IDs, that I know of, which are expected for an external user to generate before creating. It is not really possible for a user to keep track of an index of IDs outside of the database in order to create an ID other than generating it randomly anyway.
So if UUIDs are the expected id type then the API should explain that with it's contract not with it's documentation.

Thanks for checking out the project and giving feedback @from-nibly .
So here was my thinking regarding id's:

I didn't want an autogenerated incrementing integer provided by the database. It leaks information on how many other objects there are in the database.

That leaves some sort of universally unique identifier.

I could have had the server generate an id when an object is created, but I decided to have the user generate them since it allows for some convenience. For example, you can locally create a whole tree of accounts and upload them all in one POST. This wouldn't be possibly if the server assigned id's.

I looked into client generated UUID's. According to the wiki article, they are 128 bit keys. There are 5 different versions: 4 of them based on date / time / mac address / namespace. One of them based on random data. I only saw utility in the randomly generated version. The others include unnecessary data.

Instead of using the more complex UUID format, I decided to use a simpler format. Generate a random 128 bit number and encode it into a hex string. It's easy to consume and generate in the API. The database can get a performance boost by storing them as BINARY(16).

Do you see any advantage to using the traditional UUID format as opposed to the simpler 128 bit hex string?

Do you see any advantage to using the traditional UUID format as opposed to the simpler 128 bit hex string?

@pnagurny
Perhaps the only advantage is in the convention. UUID's are a fairly common practice and may be easier for client libraries to support. Also if someone were attempting to export/import data from another system which already uses UUID's it could greatly simplify things.
The logic and methodology behing the 128 bit hex string is sound, however UUID's is already an accepted practice with guidelines, tools and support systems in place, such as from a 5 second google search:
https://www.guidgenerator.com/online-guid-generator.aspx
The common practice in UUID generation is for backend models to optionally accept a UUID as an argument, otherwise generate them, or in the case of CQRS for the UUID to be either passed to or generated by the command, and required by the handler, so that the UUID is already established prior to the creation event.

I kinda like server generated, by a singleton, id's. Something like :smiley:
(+new Date()).toString(36)
"lbukw9cb"

Easy to generate combined keys:
tx = {
  key: `${user}:${debit}:${credit}`,
  value: 12345
}


No hint on radiobuttons when required

When using required=true on type radiobuttons the browser does not show a hint and does not prevent submitting.
Instead a jsonform error is created. I would expect a hint and that it does not submit until a selection is taken.
How to reproduce:

I have 3 fields: text, radiobuttons, birthdate

{
    "schema": {
        "name": {
            "title": "Name",
            "type": "string",
            "required": true
        },
        "birthdate": {
            "type": "string",
            "title": "Birth date",
            "required": true
        },
        "q1": {
            "type": "string",
            "title": "Question",
            "enum": [
                "yes",
                "no"
            ],
            "required": true
        }
    },
    "form": [
        {
            "key": "name",
            "type": "text"
        },
        {
            "key": "q1",
            "type": "radiobuttons",
            "activeClass": "btn-success"
        },
        {
            "key": "birthdate",
            "type": "date"
        },
        {
            "type": "submit",
            "title": "Submit"
        }
    ]
}

When submitting empty, only field 1 and 3 are marked, field 1 gets a hint. Required field 2 is ignored.

When field 1 is filled, only field 3 is marked and gets a hint. Required field 2 is ignored.

When field 1 and 3 are filled, I can submit the form and receive a jsonform error.

Using jquery-3.5.1, bootstrap v4.4.1 and latest underscore.js and jsonform.js, jsv.js from jsonform repo.
    <script src="/static/js/jquery-3.5.1.min.js" ></script>
    <script src="/static/js/bootstrap.bundle.min.js"></script>
    <script src='/static/js/underscore-min.js'></script>
    <script src='/static/js/jsv.js'></script>
    <script src='/static/js/jsonform.js'></script>

<style>
    .jsonform-required>label:after {
        content: ' *';
        color: red;
    }
    .btn-default {
        color: #343a40;
        background-color: transparent;
        background-image: none;
        border-color: #343a40;
    }
</style>

Some steps forward. I figured out that I need a CSS class to display the error with the radiobuttons.
    .error {
        border: 2px solid red;
        border-radius: .25rem;
    }

The hint is only displayed when the other fields are correctly filled out. And it still creates a jsonform error, where the others do not.

Funny, the activeClass is used on the header above the buttons when you click it. Test it in the official demo.

Hi @bluepuma77
Thanks for your report. I'm not entirely sure why this happens but I think it may be related to input group validation on the bootstrap side (https://getbootstrap.com/docs/4.5/components/forms/#validation); What do you think ?


Asynchronous Event Logging & improve doc

Using ActiveJob, so won't be asynchronous by default but the host app
can use any queue.

Looks OK given the condition on Rails.env.test? will be refactored with the specs at a later stage.

Looks good to me as well.


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_bfct8rvkgp/clone/recipe/meta.yaml:17: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_bfct8rvkgp/clone/recipe/meta.yaml:22: missing_wheel: For pypi packages, wheel should be present in the host section
WARNING: /tmp/abs_bfct8rvkgp/clone/recipe/meta.yaml:39: missing_description: The recipe is missing a description
ERROR: /tmp/abs_bfct8rvkgp/clone/recipe/meta.yaml:39: missing_license_family: The recipe is missing the about/license_family key.
ERROR: /tmp/abs_bfct8rvkgp/clone/recipe/meta.yaml:39: missing_dev_url: The recipe is missing a dev_url
ERROR: /tmp/abs_bfct8rvkgp/clone/recipe/meta.yaml:39: missing_documentation: The recipe is missing a doc_url or doc_source_url
Errors were found


Allow newer prettytable with newer python

This helps to allow icetea fit into the same Python environment as
mbed-os-tools or mbed-os.
pkg_resources.ContextualVersionConflict: (prettytable 0.7.2 (/usr/local/lib/python3.8/dist-packages), Requirement.parse('prettytable<3.0,>=2.0; python_version >= "3.6"'), {'mbed-os-tools'})
Fixes #114

Closing as this project is deprecated and archived, with no new releases


TLS off is not working

HI,
Even after disabling TLS.Compilation error is coming.
netopeer2-master/src/netconf_server_tls.c:189:50: error: ‘NC_TI_OPENSSL’ undeclared (first use in this function)
cmake -DENABLE_TLS=OFF -DENABLE_SSH=ON ..
Could you pleas help whether i used proper compiler flag?
Br
Rohit

Hi,
right, please try it again with the latest libnetconf2 and netopeer2 devel, there were a number of problems.
Regards,
Michal

Hi Michal,
After using devel pkg it is working.
but netopper is not starting.Below error is coming.
Order of installtion is:
sysrepo
libnetconf2
netooper
and then starting
netooper present inside build with
./netopeer2-server
Aug 12 17:22:21 clab1603node01 netopeer2-server[27478]: Module "sysrepo@2020-01-15" successfully parsed as implemented.
Aug 12 17:22:36 clab1603node01 netopeer2-server[27478]: Locking a mutex failed (sr_connect: Connection timed out).
Aug 12 17:22:36 clab1603node01 netopeer2-server[27478]: Connecting to sysrepo failed (Timeout expired).
Aug 12 17:22:36 clab1603node01 netopeer2-server[27478]: Server init failed.

Hi,
you probably have some invalid leftover sysrepo state. Run # make sr_clean for sysrepo, # make install for netopeer2, and then try again.
Regards,
Michal

Hi,
Netopper make install giving below error:
Installing missing sysrepo modules...
[ERR]: Module "ietf-netconf" in another revision already implemented.
[ERR]: Module "ietf-netconf-with-defaults" parsing failed.
sysrepoctl error: Failed to connect (libyang error)
[ERR]: Module "ietf-netconf" in another revision already implemented.
[ERR]: Module "ietf-netconf-with-defaults" parsing failed.
sysrepoctl error: Failed to connect (libyang error)
-- Generating a new RSA host key "genkey" if not already added...
[ERR]: Module "ietf-netconf" in another revision already implemented.
[ERR]: Module "ietf-netconf-with-defaults" parsing failed.
sysrepocfg error: Failed to connect (libyang error)
-- Merging default server listen configuration if there is none...
[ERR]: Module "ietf-netconf" in another revision already implemented.
[ERR]: Module "ietf-netconf-with-defaults" parsing failed.
sysrepocfg error: Failed to connect (libyang error)

Did you run # make install for sysrepo before? After that you can try sysrepoctl -l, which must work. Then also # make install for netopeer2 should work.

sysrepoctl -l works expected  before doing make install in netooper2 ,if i do make install in netooper2 ,sysreplctl -l command is hanging.
netopper2 dev pacakg i am using as suggest by you to disable TLS.

Hi,
what exactly are you doing? You have some netopeer2 dev package? I told you to install it from the devel branch from source, no package.

Yes devel from source,https://github.com/CESNET/netopeer2/tree/devel.

Okay, then something strange is going on. Can you please post the full output of you performing these commands one by one?
.../sysrepo/build# make sr_clean
sysrepoctl -l
.../netopeer2/build# make install

/*************************/
make sr_clean
Built target shm_clean
Built target sr_clean
/*********************/
sysrepoctl -l
Sysrepo repository: /root/netconf/sysrepo-master/build/repository
Module Name                | Revision   | Flags | Owner     | Permissions | Submodules | Features
ietf-datastores            | 2018-02-14 | I     | root:root | 666         |            |
ietf-inet-types            | 2013-07-15 | i     |           |             |            |
ietf-netconf               | 2011-06-01 | I     | root:root | 666         |            |
ietf-netconf-notifications | 2012-02-06 | I     | root:root | 666         |            |
ietf-netconf-with-defaults | 2011-06-01 | I     | root:root | 666         |            |
ietf-origin                | 2018-02-14 | I     | root:root | 666         |            |
ietf-yang-library          | 2019-01-04 | I     | root:root | 666         |            |
ietf-yang-metadata         | 2016-08-05 | i     |           |             |            |
ietf-yang-types            | 2013-07-15 | i     |           |             |            |
sysrepo-monitoring         | 2020-04-17 | I     | root:root | 600         |            |
yang                       | 2017-02-20 | I     | root:root | 666         |            |
Flags meaning: I - Installed/i - Imported; R - Replay support; N - New/X - Removed/U - Updated; F - Feature changes
Features: ! - Means that the feature is effectively disabled because of its false if-feature(s)
/***********************************************************************************************************************/
]# make install
[ 47%] Built target serverobj
[ 52%] Built target compat
[ 64%] Built target netopeer2-server
[100%] Built target netopeer2-cli
Install the project...
-- Install configuration: "debug"
-- Up-to-date: /usr/local/share/yang/modules/netopeer2
-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date: /usr/local/bin/netopeer2-server
-- Installing missing sysrepo modules...
[ERR]: Module "ietf-netconf" in another revision already implemented.
[ERR]: Module "ietf-netconf-with-defaults" parsing failed.
sysrepoctl error: Failed to apply changes (libyang error)
-- Generating a new RSA host key "genkey" if not already added...
[ERR]: Module "ietf-netconf" in another revision already implemented.
[ERR]: Module "ietf-netconf-with-defaults" parsing failed.
sysrepocfg error: Failed to connect (libyang error)
-- Merging default server listen configuration if there is none...
[ERR]: Module "ietf-netconf" in another revision already implemented.
[ERR]: Module "ietf-netconf-with-defaults" parsing failed.
sysrepocfg error: Failed to connect (libyang error)
-- Up-to-date: /usr/local/bin/netopeer2-cli
-- Up-to-date: /usr/local/share/man/man1/netopeer2-cli.1

Um, thanks, but it did not help at all. What distribution are you on? I cannot reproduce this and I do not even have any idea what the problem may be.

Its linux 7.X.When i execute make install in netooper it seems it is changing some files which is needed for sysrepo and then sysrepo stop working.

whether this error is due to compatibility issue between sysrepo and netopper-dev?

Um, what sysrepo version are you using? I just assumed you have at least the latest release 1.4.70 but if you have something older, it may very well be the reason.

its latest master.But it seems when netopper is trying to update some feature in sysrepo which is causing some corruption.

Okay, the please apply this print.patch.txt for netopeer2, run # make sr_clean for sysrepo and then post the output of # make install of netopeer2. Thanks.

make install
[  5%] Built target compat
[ 52%] Built target serverobj
[ 64%] Built target netopeer2-server
[100%] Built target netopeer2-cli
Install the project...
-- Install configuration: "debug"
-- Up-to-date: /usr/local/share/yang/modules/netopeer2
-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date: /usr/local/bin/netopeer2-server
Installing missing sysrepo modules...

'[' -z /usr/local/share/yang/modules/netopeer2 -o -z 600 -o -z root -o -z root ']'
++ id -u
'[' 0 -eq 0 ']'
++ su -c 'which sysrepoctl' -l root
SYSREPOCTL=/usr/local/bin/sysrepoctl
MODDIR=/usr/local/share/yang/modules/netopeer2
PERMS=600
OWNER=root
GROUP=root
<EMAIL_ADDRESS><EMAIL_ADDRESS>-e writable-running -e candidate -e rollback-on-error -e validate -e startup -e url -e xpath"<EMAIL_ADDRESS><EMAIL_ADDRESS>-e origin -e with-defaults"<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>-e keystore-supported"<EMAIL_ADDRESS>-e truststore-supported -e x509-certificates"<EMAIL_ADDRESS>-e keepalives-supported"<EMAIL_ADDRESS>-e local-client-auth-supported"<EMAIL_ADDRESS>-e local-client-auth-supported"<EMAIL_ADDRESS>-e ssh-listen -e tls-listen -e ssh-call-home -e tls-call-home")
++ /usr/local/bin/sysrepoctl -l
[ERR]: Module "ietf-netconf" in another revision already implemented.
[ERR]: Module "ietf-netconf-with-defaults" parsing failed.
sysrepoctl error: Failed to connect (libyang error)
SCTL_MODULES=
for i in '"${MODULES[@]}"'
++ echo<EMAIL_ADDRESS>++ sed 's/([^@])./\1/'
name=ietf-netconf-acm
++ echo ''
++ grep '^ietf-netconf-acm +|[^|]*| I'
SCTL_MODULE=
'[' -z '' ']'
INSTALL_MODULE<EMAIL_ADDRESS>/usr/local/bin/sysrepoctl -a -i<EMAIL_ADDRESS>-s /usr/local/share/yang/modules/netopeer2 -p 600 -o root -g root -v2
[ERR]: Module "ietf-netconf" in another revision already implemented.
[ERR]: Module "ietf-netconf-with-defaults" parsing failed.
sysrepoctl error: Failed to connect (libyang error)
local rc=1
'[' 1 -ne 0 ']'
exit 1
-- Generating a new RSA host key "genkey" if not already added...
[ERR]: Module "ietf-netconf" in another revision already implemented.
[ERR]: Module "ietf-netconf-with-defaults" parsing failed.
sysrepocfg error: Failed to connect (libyang error)
-- Merging default server listen configuration if there is none...
[ERR]: Module "ietf-netconf" in another revision already implemented.
[ERR]: Module "ietf-netconf-with-defaults" parsing failed.
sysrepocfg error: Failed to connect (libyang error)
-- Up-to-date: /usr/local/bin/netopeer2-cli
-- Up-to-date: /usr/local/share/man/man1/netopeer2-cli.1

Okay, we may be getting closer to the problem. Now please paste the output of which sysrepoctl.

which sysrepoctl
/usr/local/bin/sysrepoctl

Hm, then I do not know what the problem is. You execute sysrepoctl -l directly, it works fine. But when it is executed in the script, it fails. Just one last idea, could you try executing find / -name "sysrepoctl" 2>/dev/null?

find / -name "sysrepoctl" 2>/dev/null
/root/netconf/sysrepo-master/build/sysrepoctl
/root/netconf/sysrepo-devel/build/sysrepoctl
/usr/local/bin/sysrepoctl

That looks okay. So I have no more ideas, sorry.


Failures on [cfe] Use InferableTypeBuilder for primary constructor parameters

There are new test failures on [cfe] Use InferableTypeBuilder for primary constructor parameters.
The tests
pkg/dev_compiler/test/expression_compiler/expression_compiler_e2e_ddc_sound_test RuntimeError (expected Pass)

are failing on configurations
web-dev-unittest-asserts-linux

@srujzs The CL fixed the types of the parameters to be correct (and not dynamic). This caused the test to fail because it tries to create an extension type with an argument of the wrong type. I'm not sure what the right fix of the test is.

This seems to happen also for
pkg/dev_compiler/test/expression_compiler/expression_compiler_e2e_amd_sound_test
pkg/dev_compiler/test/expression_compiler/expression_compiler_e2e_amd_unsound_test
pkg/dev_compiler/test/expression_compiler/expression_compiler_e2e_ddc_unsound_test

@annagrin has recently been working with these tests - maybe she can add some details here?

Have a CL here: https://dart-review.googlesource.com/c/sdk/+/321202

Thanks @srujzs!


Confusing reinterpret_cast

Hi! I'm trying to understand the code in this application, and noticed a section that is confusing me.
In the the_window.cpp file, there is this code starting at line 144:
if ( m_func_draw )
    reinterpret_cast<void( __stdcall* )( void )>( m_func_draw )( );

What is this doing? If its no trouble, could a comment be added to this? 😄

the_window.cpp file
contains the window creation class, the function that will be used to draw in that window is passed as an argument in the class's oncreate.
https://github.com/Code-Building/ImGuiBuilder/blob/main/ImGuiBuilder/main.cpp#L7
the function pointer is associated with a member of the class that is called in the routine to draw everything.
https://github.com/Code-Building/ImGuiBuilder/blob/main/ImGuiBuilder/main/the_window.cpp#L145
it just checks if the pointer is valid and calls it as a function.
if you comment on that, everything from the imgui stops showing in the window.

Gotcha!
Also, I didnt mean comment the line out haha.
I just meant adding a comment explaining the line. Thanks for taking the time to explain it!


Support .m4a file type

Currently m4a type cannot be found in standardFormats. On Android and ChromeOS,  the file's format identifier will be identified as 'audio/mpeg' which is the same as mp3 file.
Is there any chance that the m4a file will be supported that could make distinction between m4a and mp3 file?
Love this package and thank you for the great support.

m4a should have mime type of audio/mp4 and is indeed missing in Formats.

Do you mean it will be added for future release?

Yes, I'l try to make a PR for it soon.


feat: html stories support

Purpose
Closes #178
Approach
Make use of docs prepareForInline to intercept HTML (string or Element) stories and render as React elements.
Also has matrix bundled in which is the replacement for our custom storiesOf, but could be split as a separate PR later.
Testing
Open preview deploy to see new stories core/Button and core/Icon.
Risks
Storybook canvas view is not supported.

Good job!

Thanks :)

FYI "Canvas" tab does not work, you're aware of this?

Yea listed under Risks.
There's probably a way to intercept all renderings, not just docs' with prepareForInline, but it's not well documented and I didn't look into storybook's internal code too much.

What would be your plan, once this is finised, merge and then work on other components, or continue with same PR for those also?

This is more of a Proof of Concept, so I would work on other stories later.
I'd also rework the current stories so they match React's, I just wanted to see wether the prop matrix for future visual regression tests would work too.

Something's not right now with latest updates:

I like this, some comments added though.
Probably downside here is that it complicates component development, that is more stories to write. But at the end we will get a good testing infrastructure (when such added).

Thanks for the patience and thoroughness.
We don't necessarily need to write HTML/core stories yet, but ultimately it will benefit our consumers so at some point we should.
The benefits for testing can be reaped from the React stories alone.

Something's not right now with latest updates

Fixed that bug, requires some explicit parameters: { display: 'flex' } for stories now, but I think that's the most obvious way to use it.
I could automatically apply that display to a Story created with matrix but it'd be kinda magical, and coupled to withContainer.

Oh noes, I force pushed an old version 🤦🏻

Phew not too bad, only missed one commit. Saved!


Struggling to follow with Sonos OS S2 15.3 & UniFi Network Network 7.8.83

As per the title, I came here hoping for an easy solution to my Sonos connectivity woes. But the guide seems to assume a much older version of both Sonos OS and UniFi Network; some of the options either I couldn’t find, or don’t exist anymore?!
Also I’d love to know whether this is even still required? I want to have all my Sonos devices running through WiFi only, none physically connected. Or alternatively, I can happily connect a single device to build SonosNet, but I’m struggling to find out what is the “recommended” approach!?

I've updated the guide for UniFi Network Application 7.4.156. They've been moved around or renamed somewhat, but not significantly. I don't think Sonos S2 15.3 changed anything in this regard.
If you connect all your Sonos devices via WiFi, you don't need any of this.

As long as you don't enable "Multicast and Broadcast Control", you should be fine with an all-WiFi setup across multiple APs.

Do we know whether things like “Multicast Enhancement” or “Client Device
Isolation” are either negative or positive to the Sonos connectivity?
Also I’d love a PR made to the README that make it explicit that if you’re
using JUST WiFi Sonos, then only the following settings are relevant?!
On Tue, 23 May 2023 at 23:02, Ingmar Stein @.***> wrote:

As long as you don't enable "Multicast and Broadcast Control", you should
be fine with an all-WiFi setup across multiple APs.
—
Reply to this email directly, view it on GitHub
https://github.com/IngmarStein/unifi-sonos-doc/issues/3#issuecomment-1560184670,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACSUOCDSWOMFZU63TNB64DXHUXX7ANCNFSM6AAAAAAYI3HNYU
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Simon Mansfield, Senior Manager, Solutions Architecture
@.***
The Old Piggery, Ham Lane, Compton Dundon,
Somerset, England, TA11 6PQ
Mob:<PHONE_NUMBER>3


Error: failed to convert to proto. unknown field "tracing" in v1alpha1.ProxyConfig

Describe the bug
I encountered the following issue today. The same YAML file was working fine couple of months back.
$ istioctl kube-inject -f dev-deployment.yaml
Error: failed to convert to proto. unknown field "tracing" in v1alpha1.ProxyConfig

Version
$ istioctl version
Version: 1.0.5
GitRevision: c1707e45e71c75d74bf3a5dec8c7086f32f32fad
User: root@6f6ea1061f2b
Hub: docker.io/istio
GolangVersion: go1.10.4
BuildStatus: Clean

Installation
Using helm charts.
Environment
Google Cloud Platform

Hello @linsun, your input would be helpful.

Hello @linsun, help would be appreciated.

my guess is your mesh config is outdated/not refreshed to 1.0.5 level but I haven't tried 1.0.5 personally myself.

After deleting istio as well as tiller and starting over.
The issue seems to be resolved.

I still see this issue with latest istio (1.0.6). Is there any workaround?
Following https://istio.io/docs/setup/kubernetes/sidecar-injection/#manual-sidecar-injection. All the istio pods are up and running.
$ curl -L https://git.io/getLatestIstio | sh -
$ cd istio-1.0.6

$ istioctl kube-inject -f samples/sleep/sleep.yaml | kubectl apply -f -
Error: failed to convert to proto. unknown field "tracing" in v1alpha1.ProxyConfig
error: no objects passed to apply

$ istioctl kube-inject -f samples/sleep/sleep.yaml
Error: failed to convert to proto. unknown field "tracing" in v1alpha1.ProxyConfig

Versions:
$ istioctl version
Version: 1.0.6
GitRevision: 98598f88f6ee9c1e6b3f03b652d8e0e3cd114fa2
User: root@464fc845-2bf8-11e9-b805-0a580a2c0506
Hub: docker.io/istio
GolangVersion: go1.10.4
BuildStatus: Clean

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.3", GitCommit:"435f92c719f279a3a67808c80521ea17d5715c66", GitTreeState:"clean", BuildDate:"2018-11-26T12:57:14Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.3", GitCommit:"435f92c719f279a3a67808c80521ea17d5715c66", GitTreeState:"clean", BuildDate:"2018-11-26T12:46:57Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}

$ helm version
Client: &version.Version{SemVer:"v2.12.2", GitCommit:"7d2b0c73d734f6586ed222a567c5d103fed435be", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.12.2", GitCommit:"7d2b0c73d734f6586ed222a567c5d103fed435be", GitTreeState:"clean"}

Tiller:
$ kubectl describe pod tiller-deploy-5f96fb458f-vvhqb -n=kube-system | grep Image:
    Image:          registry.ci.ciscolabs.com/cpsg_kaas-images/gcr.io/kubernetes-helm/tiller:v2.12.2

I ran into the same issue. The problem in my case was that I didn't update the istioctl binary.

The same code, that @vhosakot  shared works for me.
# Downloading and installing latest Istio
curl -L https://git.io/getLatestIstio | sh -
$ cd istio-1.1.2/bin
$ chmod +x istioctl
$ ./istioctl kube-inject -f ~/code/deployment.yaml
apiVersion: extensions/v1beta1
kind: Deployment
.....

I have installed kubectl using gcloud components install kubectl. Helm using Helm's Official Installa Instruction.
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.6", GitCommit:"ab91afd7062d4240e95e51ac00a18bd58fddd365", GitTreeState:"clean", BuildDate:"2019-02-26T12:59:46Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"12+", GitVersion:"v1.12.5-gke.5", GitCommit:"2c44750044d8aeeb6b51386ddb9c274ff0beb50b", GitTreeState:"clean", BuildDate:"2019-02-01T23:53:25Z", GoVersion:"go1.10.8b4", Compiler:"gc", Platform:"linux/amd64"}

$ helm version
Client: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.13.0", GitCommit:"79d07943b03aea2b76c12644b4b54733bc5958d6", GitTreeState:"clean"}

$ ./istioctl version
version.BuildInfo{Version:"1.1.2", GitRevision:"2b1331886076df103179e3da5dc9077fed59c989", User:"root", Host:"35adf5bb-5570-11e9-b00d-0a580a2c0205", GolangVersion:"go1.10.4", DockerHub:"docker.io/istio", BuildStatus:"Clean", GitTag:"1.1.1"}


[Run.Plugin.VSCodeWorkspaces] Enable analyzer and fix warning

Summary of the Pull Request
What is this about:
What is included in the PR:
How does someone test / validate:
Quality Checklist

[x] Linked issue: #16511
[x] Communication: I've discussed this with core contributors in the issue.
[x] Tests: Added/updated and all pass
[ ] Installer: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Docs: Added/ updated
[ ] Binaries: Any new files are added to WXS / YML

[ ] No new binaries
[ ] YML for signing for new binaries
[ ] WXS for installer for new binaries

Contributor License Agreement (CLA)
A CLA must be signed. If not, go over here and sign the CLA.

Thanks for this. Doesn't adding IgnoreCase change the logic? It was case sensitive before, right?

That's right, I changed the logic here. because windows treats filepaths as OrdinalIgnoreCase. So it should make no difference (famous last words).

Mircosoft recommends using OrdinalIgnoreCase as default for file paths


Include xml and yaml launch files in examples

Add examples on including Python, XML and YAML files in Python/XML/YAML launch files
Depends on the YAML launch files that were added with a pull request in ros2/demos.
Renamed example launch files to comply with documentation (as in 19366a0)

Related to #3369

Can you please rebase this onto the latest?  Thanks.

Yes, I rebased to 01e1968a2d41abbf42f33dc6546a500549d4c6e7.

You're welcome ! Glad to have contributed to a small bit of ROS2 !