How to confirm if LocalVideoTrack sent from HoloLens 2 to remote Peer?

Hello,
I'm using the Release 1.0 C# library. I'm using a modified TestAppUWP on the HoloLens 2 to make video call with another app running on a desktop.
The problem I'm facing is that when I run the TestAppUWP on Hololens 2, the video is not rendered on the remote peer. However, when I run the TestAppUWP on a Win 10 Laptop, the video is rendered successfully on the remote peer.
One possibility appears to be that the HoloLens 2 is not encoding into H.264 and/or sending out the packets to the remote peer. On the Hololens 2, the Local video playback works fine, and the callback when an I420A Frame is received from local device (_localVideoTrack.I420AVideoFrameReady) also succeeds. Does this mean that the video frame is also being successfully encoded into H.264 (preferred video codec) and sent out to the remote peer? Is there anyway for me to confirm this?
The other possibility I'm not seeing video on the remote peer is that maybe the remote peer is receiving the frames, but is not rendering it because of, say a mis-match in the video profile and resolution. But the rendering on remote peer works fine when the local peer is a Win 10 laptop. When I use the exact same profile Id and resolution on the Hololens, the rendering doesn't work on the remote peer. The Remote peer is constant in both these cases - Win 10 laptop.
I've also ensured no other apps are using H.264 encoding on the Hololens device while I was running this.
For reference, here's how the Local tracks are added to the peer connection:
await _peerConnection.AddLocalAudioTrackAsync();
var trackConfig = new LocalVideoTrackSettings
{
trackName = "local_video",
videoDevice = captureDeviceInfo,
videoProfileId = videoProfileId,
videoProfileKind = SelectedVideoProfileKind,
width = width,
height = height,
framerate = framerate,
enableMrc = false
};
_localVideoTrack = await _peerConnection.AddLocalVideoTrackAsync(trackConfig);
Thanks,
Rahul

Hi,

Does this mean that the video frame is also being successfully encoded into H.264 (preferred video codec) and sent out to the remote peer? Is there anyway for me to confirm this?

No, and no. Though I doubt this is the issue, unless the video track is not negotiated correctly, but I can't tell without the SDP messages.

is not rendering it because of, say a mis-match in the video profile and resolution.

There is no concept of video profile or resolution on the receiving peer. This is only used to configure the local webcam, and only on UWP. WebRTC doesn't even know what a video profile is. And the resolution is sent per frame alongside the video frame itself, not pre-configured, so by design there is nothing for it to be mismatching with.
Could you please:

Try not to add the audio track, to see if there's a negotiation timing issue.
Try not to constraint the width/height/framerate and let the implementation peek one instead, to see if you are over-constraining. In particular framerate constraints are flaky; it only works if you are setting a value previously retrieved by enumerating the supported capture formats. You cannot just set 30.0 and expect it to work, because the device might list 29.9999999 and that will mismatch.
Paste the SDP offer/answer in both cases, to see if there's a difference and whether the video track is correctly negotiated.

When Both Local Audio and Local Video Tracks are added to the PeerConnection:
The SDP Offer:
v=0
o=-<PHONE_NUMBER>195153007 2 IN IP4 <IP_ADDRESS>
s=-
t=0 0
a=group:BUNDLE 0 1
a=msid-semantic: WMS local_av_stream
m=audio 9 UDP/TLS/RTP/SAVPF 111 103 9 102 0 8 105 13 110 113 126
b=TIAS:64000
c=IN IP4 <IP_ADDRESS>
a=rtcp:9 IN IP4 <IP_ADDRESS>
a=ice-ufrag:+sKI
a=ice-pwd:oAaSqibMeGXmi3Kjt2TQtN/7
a=ice-options:trickle
a=fingerprint:sha-256 D1:F5:3C:92:AA:A0:70:AE:CA:82:B1:9F:20:4B:4D:82:B4:5B:59:D3:70:26:18:4F:3C:62:32:38:11:0C:C2:41
a=setup:actpass
a=mid:0
a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level
a=extmap:9 urn:ietf:params:rtp-hdrext:sdes:mid
a=sendrecv
a=msid:local_av_stream local_audio
a=rtcp-mux
a=rtpmap:111 opus/48000/2
a=rtcp-fb:111 transport-cc
a=fmtp:111 minptime=10;useinbandfec=1
a=rtpmap:103 ISAC/16000
a=rtpmap:9 G722/8000
a=rtpmap:102 ILBC/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:105 CN/16000
a=rtpmap:13 CN/8000
a=rtpmap:110 telephone-event/48000
a=rtpmap:113 telephone-event/16000
a=rtpmap:126 telephone-event/8000
a=ssrc:1454952447 cname:AjgOFH9AoL1fRy2Z
a=ssrc:1454952447 msid:local_av_stream local_audio
a=ssrc:1454952447 mslabel:local_av_stream
a=ssrc:1454952447 label:local_audio
m=video 9 UDP/TLS/RTP/SAVPF 100
b=TIAS:4000000
c=IN IP4 <IP_ADDRESS>
a=rtcp:9 IN IP4 <IP_ADDRESS>
a=ice-ufrag:+sKI
a=ice-pwd:oAaSqibMeGXmi3Kjt2TQtN/7
a=ice-options:trickle
a=fingerprint:sha-256 D1:F5:3C:92:AA:A0:70:AE:CA:82:B1:9F:20:4B:4D:82:B4:5B:59:D3:70:26:18:4F:3C:62:32:38:11:0C:C2:41
a=setup:actpass
a=mid:1
a=extmap:2 urn:ietf:params:rtp-hdrext:toffset
a=extmap:3 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time
a=extmap:4 urn:3gpp:video-orientation
a=extmap:5 http://www.ietf.org/id/draft-holmer-rmcat-transport-wide-cc-extensions-01
a=extmap:6 http://www.webrtc.org/experiments/rtp-hdrext/playout-delay
a=extmap:7 http://www.webrtc.org/experiments/rtp-hdrext/video-content-type
a=extmap:8 http://www.webrtc.org/experiments/rtp-hdrext/video-timing
a=extmap:10 http://tools.ietf.org/html/draft-ietf-avtext-framemarking-07
a=extmap:9 urn:ietf:params:rtp-hdrext:sdes:mid
a=sendrecv
a=msid:local_av_stream local_video
a=rtcp-mux
a=rtcp-rsize
a=rtpmap:100 H264/90000
a=rtcp-fb:100 goog-remb
a=rtcp-fb:100 transport-cc
a=rtcp-fb:100 ccm fir
a=rtcp-fb:100 nack
a=rtcp-fb:100 nack pli
a=fmtp:100 profile-level-id=42e01f;packetization-mode=1;max-fs=8160
a=ssrc-group:FID<PHONE_NUMBER><PHONE_NUMBER>
a=ssrc:3993736492 cname:AjgOFH9AoL1fRy2Z
a=ssrc:3993736492 msid:local_av_stream local_video
a=ssrc:3993736492 mslabel:local_av_stream
a=ssrc:3993736492 label:local_video
a=ssrc:3580006070 cname:AjgOFH9AoL1fRy2Z
a=ssrc:3580006070 msid:local_av_stream local_video
a=ssrc:3580006070 mslabel:local_av_stream
a=ssrc:3580006070 label:local_video`
The SDP Answer:
v=0
o=linus 0 1 IN IP4 <IP_ADDRESS>
s=-
c=IN IP4 <IP_ADDRESS>
b=TIAS:664000
t=0 0
a=ice-lite
m=audio 5004 UDP/TLS/RTP/SAVPF 98 101
c=IN IP4 <IP_ADDRESS>
b=TIAS:64000
a=content:main
a=sendrecv
a=rtpmap:98 opus/48000/2
a=fmtp:98 maxplaybackrate=48000;maxaveragebitrate=64000;stereo=1
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtcp-mux
a=label:100
a=mid:0
a=ice-ufrag:dwda0XX2
a=ice-pwd:4jBTSoBS/9H4APOXXhnhq7qu6yIDEXuG
a=setup:passive
a=fingerprint:sha-1 F7:E7:80:0A:F5:CF:63:BD:14:E4:29:82:DC:D2:AD:60:77:91:2B:08
m=video 5004 UDP/TLS/RTP/SAVPF 108
c=IN IP4 <IP_ADDRESS>
b=TIAS:600000
a=content:main
a=sendrecv
a=rtpmap:108 H264/90000
a=fmtp:108 profile-level-id=42400C;packetization-mode=1;max-mbps=27600;max-fs=920;max-fps=3000;max-br=600;max-dpb=891;level-asymmetry-allowed=1
a=rtcp-fb:* nack pli
a=rtcp-fb:* ccm fir
a=extmap:3/sendrecv urn:ietf:params:rtp-hdrext:toffset
a=extmap:5/sendrecv urn:3gpp:video-orientation
a=rtcp-mux
a=label:200
a=mid:1
a=ice-ufrag:esdthOCl
a=ice-pwd:Ojlx5bGNl112T0/v0k1UAD/nK0t/q6jR
a=setup:passive
a=fingerprint:sha-1 F7:E7:80:0A:F5:CF:63:BD:14:E4:29:82:DC:D2:AD:60:77:91:2B:08

When Local Audio Track Not added to Peer Connection
SDP offer:
v=0
o=-<PHONE_NUMBER>03095692 2 IN IP4 <IP_ADDRESS>
s=-
t=0 0
a=group:BUNDLE 0 1
a=msid-semantic: WMS local_av_stream
m=video 9 UDP/TLS/RTP/SAVPF 100
b=TIAS:4000000
c=IN IP4 <IP_ADDRESS>
a=rtcp:9 IN IP4 <IP_ADDRESS>
a=ice-ufrag:W9mA
a=ice-pwd:Af/6k8LLam6SAsC0dFboz8m/
a=ice-options:trickle
a=fingerprint:sha-256 FF:57:85:83:35:6D:ED:19:58:77:4E:15:EB:F5:0C:51:F2:23:53:00:2E:AF:6D:80:C3:B7:CF:A9:3F:5C:F3:16
a=setup:actpass
a=mid:0
a=extmap:2 urn:ietf:params:rtp-hdrext:toffset
a=extmap:3 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time
a=extmap:4 urn:3gpp:video-orientation
a=extmap:5 http://www.ietf.org/id/draft-holmer-rmcat-transport-wide-cc-extensions-01
a=extmap:6 http://www.webrtc.org/experiments/rtp-hdrext/playout-delay
a=extmap:7 http://www.webrtc.org/experiments/rtp-hdrext/video-content-type
a=extmap:8 http://www.webrtc.org/experiments/rtp-hdrext/video-timing
a=extmap:10 http://tools.ietf.org/html/draft-ietf-avtext-framemarking-07
a=extmap:9 urn:ietf:params:rtp-hdrext:sdes:mid
a=sendrecv
a=msid:local_av_stream local_video
a=rtcp-mux
a=rtcp-rsize
a=rtpmap:100 H264/90000
a=rtcp-fb:100 goog-remb
a=rtcp-fb:100 transport-cc
a=rtcp-fb:100 ccm fir
a=rtcp-fb:100 nack
a=rtcp-fb:100 nack pli
a=fmtp:100 profile-level-id=42e01f;packetization-mode=1;max-fs=8160
a=ssrc-group:FID<PHONE_NUMBER><PHONE_NUMBER>
a=ssrc:3082858118 cname:Ib3d3ZfGNHJMFajI
a=ssrc:3082858118 msid:local_av_stream local_video
a=ssrc:3082858118 mslabel:local_av_stream
a=ssrc:3082858118 label:local_video
a=ssrc:3873205121 cname:Ib3d3ZfGNHJMFajI
a=ssrc:3873205121 msid:local_av_stream local_video
a=ssrc:3873205121 mslabel:local_av_stream
a=ssrc:3873205121 label:local_video
m=audio 9 UDP/TLS/RTP/SAVPF 111 103 9 102 0 8 105 13 110 113 126
b=TIAS:64000
c=IN IP4 <IP_ADDRESS>
a=rtcp:9 IN IP4 <IP_ADDRESS>
a=ice-ufrag:W9mA
a=ice-pwd:Af/6k8LLam6SAsC0dFboz8m/
a=ice-options:trickle
a=fingerprint:sha-256 FF:57:85:83:35:6D:ED:19:58:77:4E:15:EB:F5:0C:51:F2:23:53:00:2E:AF:6D:80:C3:B7:CF:A9:3F:5C:F3:16
a=setup:actpass
a=mid:1
a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level
a=extmap:9 urn:ietf:params:rtp-hdrext:sdes:mid
a=recvonly
a=rtcp-mux
a=rtpmap:111 opus/48000/2
a=rtcp-fb:111 transport-cc
a=fmtp:111 minptime=10;useinbandfec=1
a=rtpmap:103 ISAC/16000
a=rtpmap:9 G722/8000
a=rtpmap:102 ILBC/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:105 CN/16000
a=rtpmap:13 CN/8000
a=rtpmap:110 telephone-event/48000
a=rtpmap:113 telephone-event/16000
a=rtpmap:126 telephone-event/8000
SDP Answer:
v=0
o=linus 0 1 IN IP4 <IP_ADDRESS>
s=-
c=IN IP4 <IP_ADDRESS>
b=TIAS:664000
t=0 0
a=ice-lite
m=video 5004 UDP/TLS/RTP/SAVPF 108
c=IN IP4 <IP_ADDRESS>
b=TIAS:600000
a=content:main
a=sendrecv
a=rtpmap:108 H264/90000
a=fmtp:108 profile-level-id=42400C;packetization-mode=1;max-mbps=27600;max-fs=920;max-fps=3000;max-br=600;max-dpb=891;level-asymmetry-allowed=1
a=rtcp-fb:* nack pli
a=rtcp-fb:* ccm fir
a=extmap:3/sendrecv urn:ietf:params:rtp-hdrext:toffset
a=extmap:5/sendrecv urn:3gpp:video-orientation
a=rtcp-mux
a=label:200
a=mid:0
a=ice-ufrag:+JfqYsKf
a=ice-pwd:mhPmUqLjWtTcJKqjKGTj9ZpRRvmtKGyo
a=setup:passive
a=fingerprint:sha-1 F7:E7:80:0A:F5:CF:63:BD:14:E4:29:82:DC:D2:AD:60:77:91:2B:08
m=audio 5004 UDP/TLS/RTP/SAVPF 98 101
c=IN IP4 <IP_ADDRESS>
b=TIAS:64000
a=content:main
a=sendonly
a=rtpmap:98 opus/48000/2
a=fmtp:98 maxplaybackrate=48000;maxaveragebitrate=64000;stereo=1
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtcp-mux
a=label:100
a=mid:1
a=ice-ufrag:UqIo8b+I
a=ice-pwd:Ufbaiwno+mb/3obcHwTQuzMw4yh3ynX2
a=setup:passive
a=fingerprint:sha-1 F7:E7:80:0A:F5:CF:63:BD:14:E4:29:82:DC:D2:AD:60:77:91:2B:08

Also, the implementation picks the height/width/framerate. So it doesn't run into the floating-point comparison inaccuracies you've mentioned above.

An update: I used Wireshark to monitor the packets received by the remote peer from the Hololens device. It looks like the video frames are not received by the remote peer.
Why might this happen? Why might the HoloLens not be sending out the video frames? Like I mentioned above, there is no issue in with the playback of local video on the Hololens. Also, the LocalVideoTrack callbacks when a new frame is received is successful. So the video signal from the hololens camera appears to be successfully delivered to the app.

I am using Release 1.0. Might there be any advantage in moving to the current "Master", at least towards resolving this issue?

I am a bit confused by your SDP message; one of them is likely from MixedReality-WebRTC/libwebrtc, but the other doesn't look like it is. Also I am not an SDP expert but it looks to me like the answer is invalid. The offer has codec H264/90000 with payload type number 100, and the answer replies with H264/90000 at payload type number 108. But the RFC seems to say that number shouldn't change (and I never saw it changed in my experience)
https://tools.ietf.org/html/rfc3264#page-10:

In the case of RTP, if a particular codec was referenced with a specific payload type number in the offer, that same payload type number SHOULD be used for that codec in the answer.

So I am wondering if this is the issue. What library/software generated the answer?

An update: I used Wireshark to monitor the packets received by the remote peer from the Hololens device. It looks like the video frames are not received by the remote peer.
Why might this happen? Why might the HoloLens not be sending out the video frames?

You are drawing hasty conclusions no? You say Wireshark shows no video frames received; how can you tell that the frames are not sent in the first place, and this is not an issue with network losses, firewall, etc.? I think it's not because I think both incoming and outgoing video feeds use the same port and you say one of them work, but still that's not 100% conclusive to me.

Might there be any advantage in moving to the current "Master", at least towards resolving this issue?

We don't know what the issue is, so I can't tell what moving to master would change.

I am a bit confused by your SDP message; one of them is likely from MixedReality-WebRTC/libwebrtc, but the other doesn't look like it is. Also I am not an SDP expert but it looks to me like the answer is invalid. The offer has codec H264/90000 with payload type number 100, and the answer replies with H264/90000 at payload type number 108. But the RFC seems to say that number shouldn't change (and I never saw it changed in my experience)
https://tools.ietf.org/html/rfc3264#page-10:

In the case of RTP, if a particular codec was referenced with a specific payload type number in the offer, that same payload type number SHOULD be used for that codec in the answer.

That's a good catch. I am no SDP expert either. However, there are also some references on the internet to the contrary - that they don't need to match: https://lists.w3.org/Archives/Public/public-webrtc/2016Jun/0077.html
Just FYI. I have no idea if this is accurate, though it appears to be from the Google Chrome team.
I'm continuing to look into this in more detail.

So I am wondering if this is the issue. What library/software generated the answer?

When a Win 10 Laptop is running TestAppUWP, there is no issue with the video. The RTP payload types are still 100 and 108, and the video works fine. The issue arises only when a HoloLens 2 device is running TestAppUWP.
So I doubt this is the issue. TestAppUWP is talking to a Webex media server. This is what generated the answer. The media server seems to be implementing ICE-lite and SFU.

An update: I used Wireshark to monitor the packets received by the remote peer from the Hololens device. It looks like the video frames are not received by the remote peer.
Why might this happen? Why might the HoloLens not be sending out the video frames?

You are drawing hasty conclusions no? You say Wireshark shows no video frames received; how can you tell that the frames are not sent in the first place, and this is not an issue with network losses, firewall, etc.? I think it's not because I think both incoming and outgoing video feeds use the same port and you say one of them work, but still that's not 100% conclusive to me.

Fair point. However, I doubt they are network losses since the issue is reproducible at various times.
It is possible that the media server is receiving the video frames, but for some reason is not sending out those frames to my client. I've raised this with the media server team to see if they can find out if this is happening - I'm yet to hear back from them.
But again, I don't see why this would work on a laptop, but not Hololens 2. These factors mainly pointed me to the hypothesis that perhaps the Hololens 2 is itself not sending out frames.

Might there be any advantage in moving to the current "Master", at least towards resolving this issue?

We don't know what the issue is, so I can't tell what moving to master would change.

Is the code that sends out local frames exposed in the master? Can I put some logging there to ensure that that code executes on the Hololens? I couldn't find this in the release/1.0.3 - was wondering if master exposes some of these.
I appreciate very much your prompt and continued support in these forums. I was also wondering if there's any way we can get on a call to resolve this. Thanks.

Closing this issue as I was able to get this working.
Unfortunately, I'm not certain what the problem was. I solved it by rewriting the app removing unnecessary aspects for our use case - this included removing the local media player, and initializing remote video player as early as possible. I used the nuget release/1.0.3 packages.
Thanks for this library and your continued support :)


Update shapeshift

This PR fixes the payment address for Shapeshift.

Update: Shapeshift is working now, so this PR only fixes the variable being incorrect.


Getting 404

Package

[X] lucide
[ ] lucide-angular
[ ] lucide-flutter
[ ] lucide-preact
[ ] lucide-react
[ ] lucide-react-native
[ ] lucide-solid
[ ] lucide-svelte
[ ] lucide-vue
[ ] lucide-vue-next
[ ] Figma plugin
[ ] source/main
[ ] other/not relevant

Version
0.462.0
Can you reproduce this in the latest version?

[ ] Yes
[ ] No

Browser

[X] Chrome/Chromium
[ ] Firefox
[ ] Safari
[X] Edge
[ ] iOS Safari
[ ] Opera
[ ] Other/not relevant

Operating system

[X] Windows
[ ] Linux
[ ] macOS
[ ] ChromeOS
[ ] iOS
[ ] Android
[ ] Other/not relevant

Description
https://lucide.dev/icons/
https://lucide.dev/icons/?focus
Getting 404 | Not Found
Steps to reproduce
https://lucide.dev/icons/
https://lucide.dev/icons/?focus
Visit these pages
Checklist

[X] I have searched if someone has submitted a similar issue before and there weren't any. (Please make sure to also search closed issues, as this issue might already have been resolved.)

@samnayakawadi Works on my machine. Is this still happening?

Now started working. Still I recommend you should look into this matter.

I can see the 404 screen flashing when I load the page but then it get's populated with icons.


react-redux 4.0.0

Until React Native is compatible with React 0.14, we need to keep using React Redux 3.x.
Waiting for this to be resolved https://github.com/facebook/react-native/issues/2985
Then we can remove children as function syntax, and maybe use import Component from 'react-pure-render/component' for React Native as well.

It will work or update to react-native 0.15rc

https://github.com/facebook/react-native/issues/4022

I think we can update redux to 4.* as you already using the correct provider for the react-native as described in the issue you linked. See also https://github.com/este/este/blob/master/src/native/index.js#L5


esteem-surfer Automatically logs me out

Expected behavior
After an account  is logged in, it shouldn't log the user out automatically.
Actual behavior
The latest version of eSteem-Surfer logs me out with this error Looks like your steem connect access token has expired. Please login again.
How to reproduce

Download/Launch the latest version of eSteem-Surfer then login.
scroll, click on tabs until this error Looks like your steem connect access token has expired. Please login again. pops up.

App version: eSteem Surfer v  1.0.10
Operating system: Windows 10 (64-bit)

Recording Of The Bug
https://youtu.be/TaxIm603OQI

This is expected behavior for security reasons and only users signed in via Steemconnect should see this messages.

So it means I can't use surfer comfortably anymore? It feels loging  my account out

@realrufans you can use it comfortably, logout happens because steemconnect gives you access token during login which expires after 7 days. It is because of security reasons steemconnect requires you to relogin so new access token can be fetched. You could however use traditional login that will keep your keys locally encrypted on your device and it never expires or logs you out.

Okay I will try it later 👍


Ho to debugg this?

I used your plugin severyl times but no it's not working anymore.
I load it like this:

This does nothing. It doesnt even throw an error. It simply doesn't work. What's the catch here?

Sorry for the delay. Have you figured this out ?
I'm running your code and it seems to be working fine in the latest Firefox, Chrome and Safari.
Closing this for now but let me know if you need further help.


Side menu has gaps

All menu options should be evenly spaced.  Create New Request and Create New Request should be separate options probably - need to check with UI team, but presume yes for now.


Feature/pushrestore

Description of Change
Support for push restore: sdk.archive.stream_to_device().
Switch to the v9 API for web restore to mirror the console UI.
Issues Resolved
N/a
Testing Procedure
Make sure you can perform both a push restore and that web restore still works.
sdk.archive.stream_to_device(["file/to/restore"], "device_guid", "accepting_device_guid", restore_path="C:/")
PR Checklist
Did you remember to do the below?

[ ] Add unit tests to verify this change
[x] Add an entry to CHANGELOG.md describing this change
[x] Add docstrings for any new public parameters / methods / classes

Tests are coming.

Ugh a lot is going on to make this work.  Basically can either create two restore session and use one for creating the file selections and the other for doing the restore, or you can ignore file sizes and rely on the user inputting the correct path and then you only need to create the push restore session. This made it make most sense to break up ArchiveAccessor into several use-cases. Also, push restore requires the master URL, so that is the reason for the connection changes.

I've got this working for V3 archives now and have tested it.

Keep in mind that you can speed up restores but setting file_size_calc_timeout=0, which will skip calculating file size

Is it correct to assume file/to/restore is a single file or a list of files but not a path?

Is it correct to assume file/to/restore is a single file or a list of files but not a path?

It is a list of string file paths or a single file path. It can also be a path to directories.

GitHub actions are currently down: https://www.githubstatus.com/


Fix for live site hang

In the live website, an event handler which calls SdlWindow::SetWindowSize() is attached to the window resize event. However, this may be called before the SdlWindow is actually initialized; the end result is that the live site hangs on a condition_variable that is never woken. To fix this:

We call SetSingleThread() earlier in the SdlMainThread initialization, so we can avoid calling multithreaded code before the first window is initialized.
Window-specific functions on SdlMainThread first check for the validity of the incoming handle, in order to avoid queuing up events for a null window.

@tomstitt or @v-dobrev, were you able to give this a try?

@kanye-quest, this does not fix the font issue from #182, correct?

@kanye-quest, this does not fix the font issue from #182, correct?

I believe that is fixed in a PR beyond the commit of glvis I ultimately pushed into glvis-js. I will test this PR and verify!

I tested this and glvis/web works for me with mkdocs serve! awesome work @kanye-quest !!
I see the small font issue though so I'm not sure what I was seeing before when I thought it was fixed in master.

Sorry to bug you @tomstitt, but can you regenerate the library in the glvis-js repo?

Sorry to bug you @tomstitt, but can you regenerate the library in the glvis-js repo?

done!

thanks!


Quoting doesn't always work correctly

import { $ } from "./mod.ts";
const a = "a/b";
await $`mkdir ${a}/c`.printCommand();

> mkdir 'a/b'/c
error: Uncaught (in promise) "Unexpected character.\n  /c\n  ~"

I opened https://github.com/denoland/deno_task_shell/issues/66


In integrated terminal, setInterval console.log does not show up at correct time

I write a very simple demo to show the bug.

You can see it. Node correctly logs a number per second, but in vscode integrated terminal, the second console.log shows up a little late.

does this reproduce in an external terminal?


Fix __type queries sometimes not returning data

If the queried type was not defined it would return an empty data section instead of __type: null
Fixes #539

@simhnna thank you for opening the issue and contributing with a PR. Does the response in the current version of the library actually violate the GraphQL Spec?

https://spec.graphql.org/October2021/#sec-Schema-Introspection
Defines __type(name: String!): __Type
And https://spec.graphql.org/October2021/#sec-Executing-Fields
states that

Each field requested in the grouped field set that is defined on the selected objectType will result in an entry in the response map.

So yes I would say the current implementation violates the spec. I know that Apollo server returns a field with null value for such queries. If you want I can double check the JavaScript reference implementation tomorrow on my work PC, but I'm pretty certain it also returns a field with a null if asked for an unknown type.


[Enhancement] Specific ScanView child classes to limit acceptable QR types

Aside from the MainMenuView's "Scan" option, all other ScanView calls are expecting a specific type of QR code (e.g. "Scan a PSBT") but nothing is stopping ScanView from accepting an unexpected but supported QR type.
This PR:

adds specific ScanView child classes that display an error screen if the user scans an unexpected QR type.

displays a friendlier error screen when an invalid or unrecognized QR format is scanned (the current approach just raises an Exception and makes it look like a bug in SeedSigner).

promotes "Verify address" to the Tools menu. Previously it was a kind of hidden feature that would be activated if a bitcoin address was scanned by ScanView.

Testing notes
If a user scans the wrong kind of QR, verify that they get another chance to resume their task and scan again.

Concept ACK
I like: flexibility of being able to enter generic scan view without expectations (as currently) and additionally being able to enter a specific scan view when navigation has been specific... and having better instructions as well as error messages.
I also like having a new ErrorView to direct flow when things go "a little" wrong instead of the dire-warning-ish "raise an exception" for errors that are common user mistakes.... reserving exceptions to truly exceptional cases.
I will test this.

ACK Tested and reviewed


Maya: Make tx option configurable with presets

Feature
make tx option in look creator was not set to be configurable with creator plugin presets.

OpenPype 3 version is #1332


Separate bulleted list from trailing text

The text following "Referer" needed to be separated by a blank line.

@DavidGoll,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@msatranjr PTAL


Rename “cheat sheet” page

This is a Feature Request

What would you like to be added

Find a new title and URL for https://kubernetes.io/docs/reference/kubectl/cheatsheet/
Redirect https://kubernetes.io/docs/reference/kubectl/cheatsheet/ to the new page
Optionally set up a new short URL, https://k8s.io/somethingshort, that also redirects to the new page

Why is this needed
The “kubectl cheat sheet” page has an unfortunate name, in that we now have actual exams where cheating is unacceptable and prohibited.
Comments
Some contributors suggest cheat sheet changes that feel a bit close to what the CNCF doesn't want to see in the exam (that is: help with specific exam questions).

/priority backlog
(or lower)

Let me try to help with this.
/assign

How about rename kubectl Cheat Sheet to kubectl Quick Reference or kubectl Quick Guide?

/triage accepted

@mengjiao-liu please review the PR #43611


Polywoof Update

Includes many visual and code changes, new BlockEntries and the biggest change is a new db schema.

You should provide a custom user agent to distinguish your requests from the RuneLite client requests: https://github.com/furfy/Polywoof/blob/92478476e049278cec8c0d18d1259c4f41bcc3cf/src/main/java/com/polywoof/PolywoofPlugin.java#L48
Otherwise lgtm

What do you mean?
https://github.com/furfy/Polywoof/blob/92478476e049278cec8c0d18d1259c4f41bcc3cf/src/main/java/com/polywoof/PolywoofTranslator.java#L130

I see, nevermind


Location.pinStyle Sizing

Description
I noticed in XYZ that it is not possible to re-size the scale applied to the location.pinStyle - it is always set to 3, in lib\ui\locations\listview.mjs
      // Create OL Style object for pin icon.
      location.pinStyle = mapp.utils.style({
        icon: {
          type: 'markerLetter',
          letter: record.symbol,
          color: location.style.strokeColor,
          scale: 3,
          anchor: [0.5, 1]
        }
      })

Can we update this so that it can be defined in the config - I think this would be one of two ways:

In an infoj entry - something like:

   {
      "field": "pin",
      "fieldfx": "ARRAY[ST_X(ST_PointOnSurface(geom_3857)),ST_Y(ST_PointOnSurface(geom_3857))]",
      "type": "pin",
     "style": {
       "scale": 1
     }
    }

In the locale.listview_records on the locale (if provided) - something like:

 "listview_records": [
        {
          "symbol": "A",
          "colour": "#2E6F9E",
          "scale": 1
        },
        {
          "symbol": "B",
          "colour": "#EC602D",
          "scale": 1
        },
        {
          "symbol": "C",
          "colour": "#5B8C5A",
          "scale": 1
        }
]

Type of Issue
Please delete options that are not relevant, and select all options that apply.

✅ New Feature

Both should be possible. It should be possible to define a custom style.icon in the listview records. It should also be possible to define a custom icon style or scale in the pin entry json.

Both should be possible. It should be possible to define a custom style.icon in the listview records. It should also be possible to define a custom icon style or scale in the pin entry json.

Agree, this would be useful too!
I also wonder if we should add a shorthand way to update them all across an instance, let's say it has lots of layers, you wouldn't want to update the infoj entry on them all, and you shouldn't have to define the whole listview_records to do so.
Maybe we could add a locale.pinStyleScale flag that would overwrite all?

The mapview location listview_records could be modified in a plugin to alter the default.
It's a good idea for a plugin to provide the location listview_records configuration.
But it is too specific for a locale.pinStyleScale flag (which effectively is a plugin) to be core. In any case the issue of being able to control the style icon in either the listview_records or pin entry configuration will have to be resolved first.


discussion archives for license development list should be merged and made publicly available

When we moved the licenses@ list from ibiblio, a new discussion archive was started. Here is the earlier archive (from CC's very beginning thru November 2015): http://lists.ibiblio.org/pipermail/cc-licenses/, which is linked to on https://creativecommons.org/about/get-involved/.
Here is the archive for the list now that it has moved:
https://creativecommons.email/mailman/private/licenses/

Merge the two archives if possible
Update the link on /get-involved/ to the merged archive
Ensure the archive is publicly accessible even if the list is moderated
Post an update to licenses@ when completed so the community is aware

When we moved the licenses@ list from ibiblio, a new discussion archive was started. Here is the earlier archive (from CC's very beginning thru November 2015): http://lists.ibiblio.org/pipermail/cc-licenses/, which is linked to on https://creativecommons.org/about/get-involved/.
Here is the archive for the list now that it has moved: https://creativecommons.email/mailman/private/licenses/

Merge the two archives if possible
Update the link on /get-involved/ to the merged archive
Ensure the archive is publicly accessible even if the list is moderated
Post an update to licenses@ when completed so the community is aware


Added cookie and max collision metrics

New in Unbound 1.18.0.

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

Comparison is base (2faff03) 5.23% compared to head (a92ba27) 5.23%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@          Coverage Diff          @@
##            main     #61   +/-   ##
=====================================
  Coverage   5.23%   5.23%
=====================================
  Files          1       1
  Lines        191     191
=====================================
  Hits          10      10
  Misses       181     181

Flag
Coverage Δ

unbound_exporter_tests
5.23% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Do not handle package activation exceptions in test mode.

I've run into difficulty writing tests a few times when my package failed to activate but the test environment didn't have anything interesting in the console or test output indicating that's where it failed. In package.coffee we should just re-raise if we're in test mode rather than calling ::handleError. I plan to do this today, just writing up this issue to remind myself when I switch contexts (or in case I never get to it!)

:+1: This will probably help a lot of people.

Hi, I am a new here. Can I work on this bug?

@kepta Absolutely! Thanks for taking an interest. Do you have the information you need?

@maxbrunsfeld I went through the docs and the source code specifically package.coffee.
In this file the @devMode is what seems relevant to me or is it? I am not able to get the complete idea, any pointers?

Is this still an open issue? If it's beginner-friendly I'd be happy to take it on.

@b-lambert yes it is!

Hi, I've made a PR #13119 for this bug. Could someone review it?


Unable to detect camera is using or not

Microsoft PowerToys version
0.49.1
Running as admin

[X] Yes

Area(s) with issue?
Video Conference Mute
Steps to reproduce
PowerToysReport_2021-11-05-16-35-40.zip
✔ Expected Behavior
must detect that camera is using
❌ Actual Behavior
unable to detect
Other Software
Zoom 5.8.0

Sounds similar to #14301.
Is it possible that an app (like zoom) makes first contact with the camera, making it unaccessable for the driver?

Thanks for the feedback but VCM is moving to maintenance only in the 0.67 timeframe. Our team will only directly address critical bugs, security and accessibility issues.
We'll accept community PRs for enhancements.


plugin: check errors

Signed-off-by: Antonio Murdaca<EMAIL_ADDRESS>

I'll clean this up tomorrow, thanks guys

@cpuguy83 @vdemeester @anusha-ragunathan @AkihiroSuda updated

LGTM


feat: Add support for confirmAckChannel

Added support for confirmAckChannel, similar to the RabbitMQ Binder (confirmAckChannel) and the Kafka Binder (recordMetadataChannel). The acknowledge channel is crucial for a reliable message publishing confirmation.

Thank you for creating and maintaining the SNS/SQS binders!


Add a Custom Ice Cream Maker

Custom Ice Cream Maker
Project Description

Change the color of the scoop and toppings using the buttons.
Check out the project here

https://user-images.githubusercontent.com/78037846/156030809-01767008-004e-49a2-af4f-cb8b48f561e4.mp4
Stack:

[x] Html
[x] CSS
[x] JavaScript

@Adit0507 you have raised many issue. But at a time , only 3 issues will be assigned to a contributor.
First you can complete those issue, then I will assign it to you.

Plz assign me


Consider table "individual"

In GitLab by @peterdesmet on Sep 8, 2020, 20:14
Note: this was suggested in the 2020-09-08 EUROMAMMAL technical call
individual_id in observations allows to indicate repeat viewings of individuals, but apart from the sex and the life_stage (at the time) no further information (like other tag numbers) can be provided. Information on recognizable/marked individuals that did were not observed by the camera traps cannot be shared either.
To share this information, we could consider adding an extra file individuals.csv, where further information regarding recognizable/marked individuals can be shared. Fields could be:

individual_id
scientific_name
life_stage: debatable since it can change over time
sex: not likely to change for camera trap observed species
other_identifiers: e.g. ring_number:HR456; movebank_id:894
comments

But I think this needs further community feedback before we can decide if and how this should be part of the standard.

Note the example dataset now includes an individuals resource, but only to showcase that it is possible to include non Camtrap DP resources in a Camtrap DP dataset (as long as they don't use the reserved names deployments, ...)

See https://github.com/inbo/camtrapdp/pull/149

This is now implemented in the camtrapdp R package, as a derived table from observations. There are a couple of such tables:

locations(): from deployments
taxa(): from observations + taxonomic
events(): from observations
individuals(): from observations

We won't add an individual table to the Camtrap DP model:

There is no use case for it
There is an easy helper function in camtrapdp to generate one from observations
It is always possible to add a custom table

We will extend the example dataset to include individual info (see #396).


Feature Request - Support for VSCode Custom File Systems

I am building VSCode extensions for Data Platforms like Databricks (Databricks Power Tools) and Microsoft Fabric (Fabric Studio, OneLake) where I heavily rely on Custom File Systems in VSCode
e.g. the URI of a parquet file might be onelake://myworkspace/myfile.parquet
within a VSCode extension that file can be read using vscode.fs.readFile(<url>) and has the following signature async readFile(uri: vscode.Uri): Promise<Uint8Array>
It seems that this is currently not supported - are there any plans in that direction?
It would add a great benefit to directly browse data processed by those Data Platform directly from VSCode using your extension

Great suggestion.
Where can I read more about custom file systems in vscode, how they work and their use cases?

well, there would need to be a file system provider for abfss scheme as a separate VSCode extensions - I dont think it exists yet
if you have Microsoft Fabric/PowerBI or Databricks somewhere accessible I could guide you through my extensions to get a demo case

I will write a small extension that allows you to upload a local file into a custom file system - should not take long
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Lucien Martijn @.>
Sent: Monday, December 16, 2024 6:10:21 PM
To: luusluus/vscode-parquet-visualizer @.>
Cc: Gerhard Brueckl @.>; Author @.>
Subject: Re: [luusluus/vscode-parquet-visualizer] Feature Request - Support for VSCode Custom File Systems (Issue #133)
I currently don't have a license of Fabric/PowerBI or Databricks. But I can try to implement s3 maybe in order to test
—
Reply to this email directly, view it on GitHubhttps://github.com/luusluus/vscode-parquet-visualizer/issues/133#issuecomment-2546183512, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AC2VO4WAHB54B5TQ2CLYVND2F4CP3AVCNFSM6AAAAABTWAUSSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBWGE4DGNJRGI.
You are receiving this because you authored the thread.Message ID: @.***>

here is a link to the repo and the final VSIX as a release
https://github.com/gbrueckl/VSCode-VirtualFileSystemDemo/releases/tag/v0.0.1
it implements basic commands to upload a file to a virtualfs:/ and browse them via the VSCode Explorer

call VirtualFS.uploadFile
call VirtualFS.showInExplorer

Very cool, ill check it out!

uploaded a new version
https://github.com/gbrueckl/VSCode-VirtualFileSystemDemo/releases/tag/v0.2.0
you can now specify default files which are always loaded and easily upload local files via the context menu
should make your tests easier :)

has there been any update?
kindly let me know if there is anything else I could support you with
an alternative approach would be that you expose a VSCode Command Download and View which takes a vscode.URI as a parameter. That command would then download the content of the selected file into a temporary local destination and view it from there. What are your thoughts about this?

Not an update yet. I haven't had much time due to my work, and holidays.
Would you say this is high priority for you?

Not at all, take your time and enjoy your holidays 😊
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Lucien Martijn @.>
Sent: Monday, December 23, 2024 1:58:35 PM
To: luusluus/vscode-parquet-visualizer @.>
Cc: Gerhard Brueckl @.>; Author @.>
Subject: Re: [luusluus/vscode-parquet-visualizer] Feature Request - Support for VSCode Custom File Systems (Issue #133)
Not an update yet. I haven't had much time due to my work, and holidays.
Would you say this is high priority for you?
—
Reply to this email directly, view it on GitHubhttps://github.com/luusluus/vscode-parquet-visualizer/issues/133#issuecomment-2559663856, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AC2VO4RB5F55BJ4WVD2RVXL2HACHXAVCNFSM6AAAAABTWAUSSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJZGY3DGOBVGY.
You are receiving this because you authored the thread.Message ID: @.***>


Create endpoint to add application from https request

Did some research on how our endpoints are setup and had a quick meeting with Conner to understand how we are setting up ours.
[t:20]

Updated endpoint for applications
[t:10]


error in make the file

I am using ubuntu 18.04
:~/Downloads/Yolo_mark-master$ cmake .
-- The CXX compiler identification is GNU 7.3.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
-- Generating done
-- Build files have been written to: /home/rgukt/Downloads/Yolo_mark-master
rgukt@rgukt-TravelMate-P243-M:~/Downloads/Yolo_mark-master$ make
Scanning dependencies of target yolo_mark
[ 50%] Building CXX object CMakeFiles/yolo_mark.dir/main.cpp.o
[100%] Linking CXX executable yolo_mark
//usr/lib/x86_64-linux-gnu/libatk-1.0.so.0: undefined reference to `g_log_structured_standard'
collect2: error: ld returned 1 exit status
CMakeFiles/yolo_mark.dir/build.make:134: recipe for target 'yolo_mark' failed
make[2]: *** [yolo_mark] Error 1
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/yolo_mark.dir/all' failed
make[1]: *** [CMakeFiles/yolo_mark.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2
please help me out
thanks

I solved it by installing glib : conda install -c anaconda glib


Confusing typo

[Enter feedback here]
This line
Create a new file named auth.js under the router folder and add the following code there:
should probably read
Create a new file named auth.js under the routes folder and add the following code there:
In following along with your example there is no folder called router

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

ID: 6486232e-d58e-fe4e-1d88-2b3d3d281dc3
Version Independent ID: d5e93d37-d132-27e0-ff95-72cfde1653d6
Content: Tutorial: Sign in users in a Node.js & Express web app - Microsoft Entra
Content Source: articles/active-directory/develop/tutorial-v2-nodejs-webapp-msal.md
Service: active-directory
Sub-service: develop
GitHub Login: @cilwerner
Microsoft Alias: cwerner

@RoYoMi
Thanks for your feedback! We will investigate and update as appropriate.

@RoYoMi
Thanks for bringing this to our attention.
We have created a PR for this issue and the changes should go live soon.


Needs tests & CI

This project needs tests and CI. I was debugging #6 and am not sure that what I'm doing isn't breaking everything.

Got it, let me try and figure it out.


Correct casting on newer versions of Numpy

This PR corrects the casting of float to int for newer Numpy versions, it was marked as a warning in previous versions.

Shouldn't it be x = np.divide(x, 255., out=norm, casting="unsafe")
The modification should also pass the PEP8 test

This would make the function incompatible with symbolic tensors. We something that works for both symbolic tensors and numpy arrays.

The correct approach would be np.divide(x, 255., out=x, casting='unsafe'), but that only works for Numpy arrays. Again, we need something that also works for symbolic tensors (like the current approach). Closing PR for now, feel free to reopen with a updated fix.