Generated ICE candidates are not accepted by Chrome

I'm trying out data channels in OpenWebRTC and Chrome complains about ICE candidates sent by Safari. Safari sends e.g. something like this:
"candidate:2 1 TCP<PHONE_NUMBER> fe80::4a0:1bff:fe63:21f7 9 typ host tcptype active"
and when Chrome tries to add such candidate:
connection.addIceCandidate(new RTCIceCandidate({
  sdpMLineIndex: 0,
  candidate: candidate
}));

I'm getting an error: Failed to execute 'addIceCandidate' on 'RTCPeerConnection': The ICE candidate could not be added.
For comparison, Chrome (41.0.2272.74 beta (64-bit) on OS X) sends candidates looking like this:
candidate: candidate:316526476 1 udp<PHONE_NUMBER> <IP_ADDRESS> 52796 typ host generation 0
candidate: candidate:3838686808 1 udp<PHONE_NUMBER> <IP_ADDRESS> 52796 typ srflx raddr <IP_ADDRESS> rport 52796 generation 0
candidate:1549677436 1 tcp<PHONE_NUMBER> <IP_ADDRESS> 0 typ host tcptype active generation 0

Does Chrome support IPv6 candidates?

I have no idea, but it's possible that that's what causing this issue. Is it possible to somehow disable IPv6? I'll create a new issue for the Firefox error.

According to release notes for Chrome 42, IPv6 is now turned on by default. Which version are you testing with?

I was testing it using the latest beta version (41.0.2272.74 beta (64-bit)), but I've just tried it in the latest canary (43.0.2323.0 canary (64-bit)) and I'm getting the same error there.

Note that the ICE-TCP RFC calls for a port number of 9 for an active TCP candidate (I guess 9 indicates not specified).  Chrome, however, doesn't follow the RFC and uses port number 0 instead (you can see this from the number after the IP in these candidates).  Perhaps when Chrome is accepting candidates it rejects candidates with port 9 (i.e. it's looking for 0 or >1024).

Have you filed a bug report on Chrome?

@stefanalund It looks like it's been already reported some time ago: https://code.google.com/p/webrtc/issues/detail?id=3849

@szimek Do you still have issues with this? The candidates look to have identical structure between openwebrtc and Chrome (I've tested 42 and 43) now, and I see no issues when applying them.

@stefhak I'll try later today. I've just tried rebuilding openwebrtc for osx platform with ./build-all.sh -Cbr osx (previously I built it for osx and ios), but it complains about iPhone SDK missing:
...
Marking sources installed in gettext-<IP_ADDRESS>
Already on 'master'
[master 20dc6c1] tag file identifying the build script that installed the sources
 1 file changed, 1 insertion(+)
 create mode 100644 .sources_installed_tag_file.txt
Switched to branch 'arm-apple-darwin10'
Setting up toolchain for ios.
ERROR: No SDK detected, looking in /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform

even though it worked before and I seem to have something there:
$ ls /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/
iPhoneOS.sdk	iPhoneOS8.2.sdk

so I need some more time to figure out what's wrong.
Could you try if https://staging.sharedrop.io works for you if you try to send a file to Chrome or Firefox?

@superdump can you comment on the build problems?
I tried staging.sharedrop, but it seems to me that owr produces an invalid sdp if you only have a data channel (there is no DTLS fingerprint, and no ICE credentials as far as I can see). I'll ask around.

There seems to be something strange going on in your application. The sdp that makes it (from owr) to Chrome in your app has no DTLS fingerprints and no ICE credentials so it can't be applied (look at the console in Chrome). I think that the problem with the ICE candidates is just a result of this (you can't add ICE candidates before the sdp has been set in the PeerConnection).
However, with demo.openwebrtc.io I get a datachannel-only chat to work, and the sdp produced by owr looks like:
v=0
o=-<PHONE_NUMBER>346015000 1 IN IP4 <IP_ADDRESS>
s=-
t=0 0
m=application 49800 DTLS/SCTP 5000
c=IN IP4 <IP_ADDRESS>
a=sendrecv
a=ice-ufrag:Jyuj
a=ice-pwd:OEC/dVRJCTow6X8diJPD6B
a=candidate:1 1 UDP<PHONE_NUMBER> fe80::24cd:4fff:fe7f:8024 57280 typ host
a=candidate:2 1 TCP<PHONE_NUMBER> fe80::24cd:4fff:fe7f:8024 9 typ host tcptype active
a=candidate:3 1 TCP<PHONE_NUMBER> fe80::24cd:4fff:fe7f:8024 60169 typ host tcptype passive
a=candidate:4 1 UDP<PHONE_NUMBER> <IP_ADDRESS> 49800 typ host
a=candidate:5 1 TCP<PHONE_NUMBER> <IP_ADDRESS> 9 typ host tcptype active
a=candidate:6 1 TCP<PHONE_NUMBER> <IP_ADDRESS> 60170 typ host tcptype passive
a=candidate:7 1 UDP<PHONE_NUMBER> fe80::22c9:d0ff:fed4:e175 49801 typ host
a=candidate:8 1 TCP<PHONE_NUMBER> fe80::22c9:d0ff:fed4:e175 9 typ host tcptype active
a=candidate:9 1 TCP<PHONE_NUMBER> fe80::22c9:d0ff:fed4:e175 60171 typ host tcptype passive
a=fingerprint:sha-256 78:5F:C8:98:F1:F6:EA:D1:F3:A6:7A:64:86:BA:D6:FA:B5:A2:37:45:59:A0:5E:24:98:AD:E1:3D:EF:6C:92:AD
a=setup:actpass
a=sctpmap:5000 webrtc-datachannel 1024
I.e. contains DTLS fingerprints and ICE credentials as it should. Does your code do anything special with the sdp's?

@stefhak I'm using peer.js lib (modified to work with Firebase as a signaling server) - https://github.com/cowbell/sharedrop/blob/master/vendor/peer.js. I don't think it does anything strange with SDPs, but if demo.openwebrtc.io works fine, then it must be doing something differently :)

@szimek we're fully focused on moving to cerbero as our build system for the future. I suspect the build problem you encountered is because we have not updated the build scripts to add iOS 8.2 SDK support. That exists in cerbero and we're busy fixing all the issues there. We will soon also be making a release and publishing downloadable binaries to help people get going.

@szimek I could not directly find any issue with peer.js (but I have to admit I'm not good at understanding and reviewing other's code). Could you try using demo.openwebrtc.io (chat only) and see if that works? And if so add console logs of the sdps to see if they look ok. If they do we could continue digging into what peer.js does.

@stefhak Unfortunately, it seems I've got an outdated version of openwebrtc, because in Safari I can't check "chat" checkbox (video and audio work just fine) and I can't build the new version, because of the issue with iPhone SDK

@szimek I think I found the issue.
If in peer.js you replace line 1196 ("sdp: offer,") and line 1236 ("sdp: answer,") with "sdp: pc.localDescription," (same at both places) things might just work. If you change your JS app, I can test tomorrow (just let me know) given that you have build issues.

@stefhak Thanks! I've just pushed a new version to https://staging.sharedrop.io with the changes you suggested.

@szimek It does not work, I probably made some error. I can't see the code (and peer.js at github does not seem to be updated). Details: works fine Chrome - Chrome, but with FF and Safari there are errors that seem related to the SDPs generated. Is there any way I could see the relevant snippets of the used peer.js?

@stefhak I've just pushed the fix to github as well: https://github.com/cowbell/sharedrop/compare/openwebrtc

@szimek I missed that we need to stringify.
"sdp: pc.localDescription," should be "sdp: JSON.stringify(pc.localDescription),"
hope that helps!

@stefhak Thank you so much for looking into this. I've tried doing JSON.stringify(pc.localDescription), but then I probably need to call JSON.parse when receiving such message, because I'm getting errors like: Argument 1 of mozRTCSessionDescription.constructor can't be converted to a dictionary.
I can't really remember why, but when I was sending the original offer/answer, I needed this code: https://github.com/cowbell/sharedrop/blob/openwebrtc/vendor/peer.js#L1228-L1230 to make it work in Firefox.
I'll try to fix it, so that it works between Chrome and Firefox later today and let you know when it's ready.

@szimek you're right - you need to parse on the receiving side!
Let me know when it works between FF and Chrome, and I'll test with owr.

Candidates should also have field "id":"audio" or "id":"video"...

@stefhak I've just pushed a new version to staging. I've tried it with Chrome <=> Firefox and it works.

Any idea when it will be avail in bowser release?

I'll test tomorrow!

25 Mar 2015 kl. 21:22 skrev Szymon Nowak<EMAIL_ADDRESS>@stefhak I've just pushed a new version to staging. I've tried it with Chrome <=> Firefox and it works.
—
Reply to this email directly or view it on GitHub.

I've tested, and we're making some progress at least. owr - Chrome and owr - FF now negotiates correctly, and data channel is established. But, when sending from owr -> FF or Chrome, there is a syntax error reported in the console of the receiving side in both cases that happens when the user clicks "save" in the dialog. Message on FF:
"SyntaxError: JSON.parse: unexpected character at line 1 column 2 of the JSON data vendor-60dedd58351276b6d98ee1ad84eadb86.js:10:17639" and on Chrome:
"Uncaught SyntaxError: Unexpected token o      staging.sharedrop.it/:1"
For the other direction nothing strange is shown in the console, but owr seem to crash with the following log:
"/GstPipeline:transport-agent-4/GstBin:transport_bin_4/GstBin:send-output-bin-1/GstDtlsSrtpEnc:dtls_srtp_rtp_encoder_1/GstSrtpEnc:srtp-encoder: random-key = false
/GstPipeline:transport-agent-4/GstBin:transport_bin_4/GstBin:send-output-bin-1/GstDtlsSrtpEnc:dtls_srtp_rtp_encoder_1/GstSrtpEnc:srtp-encoder: key = 88b571493627a5c282f9e1e8b174e3bcc257598bd3886ad7306f7122230f
/GstPipeline:transport-agent-4/GstBin:transport_bin_4/GstBin:send-output-bin-1/GstDtlsSrtpEnc:dtls_srtp_rtp_encoder_1/GstSrtpEnc:srtp-encoder: rtcp-auth = GST_SRTP_AUTH_HMAC_SHA1_80
/GstPipeline:transport-agent-4/GstBin:transport_bin_4/GstBin:send-output-bin-1/GstDtlsSrtpEnc:dtls_srtp_rtp_encoder_1/GstSrtpEnc:srtp-encoder: rtp-auth = GST_SRTP_AUTH_HMAC_SHA1_80
/GstPipeline:transport-agent-4/GstBin:transport_bin_4/GstBin:send-output-bin-1/GstDtlsSrtpEnc:dtls_srtp_rtp_encoder_1/GstSrtpEnc:srtp-encoder: rtcp-cipher = GST_SRTP_CIPHER_AES_128_ICM
/GstPipeline:transport-agent-4/GstBin:transport_bin_4/GstBin:send-output-bin-1/GstDtlsSrtpEnc:dtls_srtp_rtp_encoder_1/GstSrtpEnc:srtp-encoder: rtp-cipher = GST_SRTP_CIPHER_AES_128_ICM
** (:21762): CRITICAL **: Received message before datachannel was established.
/GstPipeline:transport-agent-4/GstBin:transport_bin_4/GstBin:send-output-bin-1/GstAppSrc:datasrc_1.GstPad:src: caps = "application/data,\ ordered=(boolean)true,\ ppid=(uint)51,\ partially-reliability=(string)none,\ reliability-parameter=(uint)0"
/GstPipeline:transport-agent-4/GstBin:transport_bin_4/GstBin:send-output-bin-1/GstSctpEnc:sctpenc_4.GstSctpEncPad:sink_1: caps = "application/data,\ ordered=(boolean)true,\ ppid=(uint)51,\ partially-reliability=(string)none,\ reliability-parameter=(uint)0""
@superdump can anyone look into what happens?

@stefhak I've just enabled JS source maps on staging, so at least Chrome should report the syntax error with a link to a non-minified file. It's also possible to run ShareDrop locally, but you need to set up a free FIrebase account for that to work.

@szimek could you give some instructions on how to run locally (I can create a firebase account)?
I won't promise anything, but I'll try to look into it.

@stefhak Sure - https://github.com/cowbell/sharedrop#how-to-set-it-up-for-local-development If something doesn't work, let me know.

@szimek I'll hopefully have a go at this soon.
@superdump assigned to you for the owr parts agreed.

@szimek setting up my own local copy seems to require some work. I'd like to do some limited tests as start instead if that's ok with you. It seems everything goes well until the user at the receiving end clicks "Save" in the dialog. I'd like to emulate what you got, so could you describe a bit? I assume you use "file" and FileReader to get hold of the file to transmit.
*How do you read the file ("readFileAsBinaryString"?)
*Is what you send over the data channel a Blob/ArrayBuffer or something else?
*How do you transmit the file name? As a separate data transmission of a string on the data channel?
*What happens when the user clicks "Save"?

@stefhak

Yup, I use FileReader#readFileAsBinaryString. This is the function responsible for reading and sending a single block of data.
If I remember correctly, I send ArrayBuffer. See this line which calls connection.send that is defined in peer.js library here. There's a lame type check which may be causing some problems. The same check is present again on the receiving side.
Yup. The code for handling incoming data is here.
To store incoming blocks of data on the receiving side I'm using FileSystem API , which is available only in Chrome (and even there probably not for very long) with IndexedDB based polyfill idb.filesystem.js for other browsers. When user clicks "Save" this function is called. It creates an <a> element, gets the URL to the image (either from FileSystem API or using URL.createObjectURL), sets it as href attribute and simulates a click.

Most of this code was written over a year ago, so even though it works in Chrome and Firefox, it's possible that it doesn't follow new versions of WebRTC standard accurately.
Again, thanks for looking into this!

@szimek You can thank me if I ever solve anything - so far I've only consumed your time :)
Regarding EDIT2: is this also pushed to the site (https://staging.sharedrop.io)? I assume it is.

@stefhak Now it is :)

I've determined that owr data channel can't handle ArrayBuffers, and filed an Issue on that (https://github.com/EricssonResearch/openwebrtc/issues/287). This may not be the only issue, but we need to fix that before doing any meaningful furhter testing.


NIFI-11874 update Process Group configuration layout in the UI

Summary
NIFI-11874
UI modification for the layout of Process Group configuration. It separates the increasing number of configuration options into two columns. Also, to assist in splitting configuration input into logically related pieces as well as be consistent with the configuration of other components, the Comments section was moved to its own tab. This presents better in the UI and keeps the Apply button easily accessible without the need to scroll (for most display resolutions.)
The PR includes additional details when mouse-over/hover the new "?" icon for several of the Process Group properties to explicitly clarify that the default connections settings apply only to new connections - not existing connections.
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[X] Apache NiFi Jira issue created

Pull Request Tracking

[X] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[X] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[X] Pull Request based on current revision of the main branch
[X] Pull Request refers to a feature branch with one commit containing changes

Verification
Installed NiFi on several different platforms each having a different display size and resolution. The results presented clearly in all cases tested.
Build

[X] Build completed using mvn clean install -P contrib-check

[X] JDK 17

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

@markobean Thanks for the PR! Utilizing the extra real estate of the Configuration dialog is a great idea. I have a couple of suggestions:

* Now that we have more than one column, the `Apply Recursively` checkbox looks out of place. Furthermore, if the browser width reduces, then the checkbox and label get pushed into the Parameter Context menu. I suggest moving the checkbox and label to the right of the `Apply` button and change the label to: `Apply Parameter Context recursively`, to be more clear of the action.

* Since we have still have a good amount of empty space remaining in the General tab, I suggest to remove the Comments tab and add the Comments `textarea` as a third column in the General tab. This way we can also keep the `Apply` click action in one place.
Thoughts?

Thanks for the feedback @mtien-apache! I am away for the next 10 days, but will get to this when I return.
As far as the comments tab, I like it being separate to be consistent with other components. It also leaves room for growth for the main General tab. It has seen the addition of numerous properties, and I feel this may continue over time.
Thanks,
Mark

As far as the comments tab, I like it being separate to be consistent with other components. It also leaves room for growth for the main General tab. It has seen the addition of numerous properties, and I feel this may continue over time.

@markobean and @mtien-apache One note about the Comments tab: although it aligns with the approach for the Processor configuration dialog, the important difference is the location of the Apply button. On the Processor configuration dialog, the Apply button is always visible, making it clear that it applies to all tabs. With the current approach, the button is not always visible. I could see separating the Comments field into its own tab, but only if we also relocate the Apply button.

@mtien-apache I have updated the UI elements so that the "Apply recursively" checkbox appears immediately underneath the Process Group Parameter Context combo. I think placing it next to the "Apply" button is too disjointed; it makes more sense to keep the checkbox next to the item to which it applies.
@exceptionfactory There is an "Apply" button on both the General and Comments tab. Did your comment of "always visible" mean you wanted to see it on the Controller Services tab as well. I think it is not necessary on that tab. Sure, maybe it's a little inconsistent, but there are no changes that need to be applied on the Controller Services tab; it would serve no functional purpose.
Part of the problem may be that the "Apply" button on a Process Group configuration dialog does not dismiss the dialog. It remains present. I have always found that behavior a little odd. I prefer to keep any changes to that as a separate ticket though; I'm not sure if there is a driving reason the dialog should not be dismissed and such a change should be commented on separately, IMO. If you think a change is needed and falls within the scope of this ticket, let me know.
Lastly, sorry for the slow reply. I was on vacation and it took a week on top of the time away to get caught up.

Branch has been rebased to main as well.

It's a slight scope creep to the original ticket, but I think it's reasonable. I'm going to refactor the UI a bit more than originally intended such that there will be a Cancel and Apply button on all tabs of the PG configuration. The "X" in the upper right will also go away since it will no longer be needed. Selection of either button will dismiss the dialog. This will be consistent with the configuration of other components such as processors.

It's a slight scope creep to the original ticket, but I think it's reasonable. I'm going to refactor the UI a bit more than originally intended such that there will be a Cancel and Apply button on all tabs of the PG configuration. The "X" in the upper right will also go away since it will no longer be needed. Selection of either button will dismiss the dialog. This will be consistent with the configuration of other components such as processors.

Thanks for the reply, that sounds like a good direction.

@markobean Thanks for the PR!
@exceptionfactory @mtien-apache Thanks for the reviews!
I just wanted to chime in here to provide some additional background that may help the direction we proceed here. The Process Group dialog used to be similar to other dialogs in terms of size and input field placement. However, when we introduced fine grain access controls we also added support for Process Group scoped Controller Services. Previous to that there was only a single collection of Controller Services that were available for all components. Because we introduced Process Group scoped Controller Services, we duplicated this table in the Process Group dialog. The previous size of the dialog didn't accommodate the full table and we moved this to a full-screen dialog.
This Controller Service table is something that I believe we should probably consider now when it comes to the Comments tab and the Apply button. The Apply button was only on the General tab because changes to the Controller Services are not saved when the user presses Apply. They are saved as the user Adds, Edits, Enables, Disables, and Deletes the Services directly in the Controller Service tab. This is also why the dialog doesn't close automatically after Applying changes to the General tab as the user may still want/need to make changes on the Controller Service tab. Because of this, I would avoid placing the Apply or Cancel buttons on the Controller Service tab.
Personally, I would vote for not having a separate Comments tab. While it's nice that there is some alignment with other component configurations, I worry it would leave the Process Group configuration a little confusing. We'd have 3 tabs where only two have an Apply button and pressing the Apply button would save changes made on both but not the other. Leaving the basic behavior in place where there are two tabs, General (with the Apply button) and Controller Services (where changes are saved automatically), would be the least surprising to users and would also eliminate a lot of the scope creep mentioned earlier.

Thanks for the additional background and perspective @mcgilman!
I tend to agree that having a separate tab for the Comments creates more complexity, as I highlighted earlier with the potential confusion related to button visibility and location. A multiple-column view still provides plenty of room for Comments. If we go down the road of separate tabs, then the button handling is a concern. If not, the scope remains focused on streamlining the arrangement on the current General tab.
Open to perspectives, but I would defer to @mcgilman on the optimal way forward.

Ok, you've convinced me to return the Comments to the General tab rather than a dedicated tab. I'll proceed with this.
Thanks @mcgilman for the explanation for why the Apply doesn't close the dialog.

Thanks @exceptionfactory and @mcgilman for weighing in and agree with your reasonings.
@markobean Thanks for all the changes! It seems there are many layout options to go with, so a few iterations are probably necessary until we get the right one (which we will). As far as the "Apply Recursively" checkbox, I don't mind it directly underneath the Parameter Content combo. I just want to point out it may throw off the visual rhythm of the rows of menu items across the dialog.

@mtien-apache @exceptionfactory @mcgilman
I've updated this PR to remove the Comments tab. Now the comments field is on the General tab and spans both columns of properties giving plenty of space to work with. It remains resizeable, if needed.
The placement of the Apply Recursively does throw off alignment between the two columns. But I don't find it too distracting. I would find it more distracting to intentionally add a spacer in the second column just to align with the first. The next best alternative would be to move the Process Group Parameter Context to the bottom of column 1 where the additional checkbox would not interfere with horizontal alignment with column 2.
Note: I have also submitted a PR for the this Jira issue to merge into the support/nifi-1.x branch (PR #7844)

@mtien-apache Here's an option which would keep the 2 columns in better alignment.
Thoughts?

@mtien-apache, @exceptionfactory, @mcgilman
Ping. Any additional comments on this PR? Also, note that I opened a separate PR for merging to nifi-1.x.
Thanks.

Thanks @markobean. I'll have a look today.

@mcgilman @mtien-apache @exceptionfactory
Hey all.. thank you for the time you've put into this PR so far. I'd like to get it over the line - and more importantly merge the corresponding nifi-1.x PR - before we get to the 1.24.0 release.
https://github.com/apache/nifi/pull/7844
Appreciate your time!

@exceptionfactory CI was apparently not run because you had requested changes. I just manually triggered it. I plan to merge this one once CI completes unless you had any other concerns. Thanks!


How do I make one cache entry expire when another one changes?

I'm looking for the equivalent to System.Runtime.Caching's MemoryCache.CreateCacheEntryChangeMonitor - Basically, expire one cache key if a different one is modified. The documentation says this is possible ("You can configure cache entries to depend on other cache entries") but doesn't explain how to actually do it.
I created a doc task too: https://github.com/aspnet/Docs/issues/1938

You can't directly link two entries, but entries can be removed based on IChangeTokens and you can use the same token for multiple entries.
https://github.com/aspnet/Caching/blob/dev/samples/MemoryCacheSample/Program.cs#L84-L96
Change tokens can even be inherited automatically:
https://github.com/aspnet/Caching/blob/dev/samples/MemoryCacheSample/Program.cs#L98-L114

So I need to maintain the cancellation tokens myself? If I have a web app with lots of stuff being cached, I'd need to have my own map of cancellation tokens too? That seems like boilerplate that should be unnecessary given System.Web.Caching.Cache and  System.Runtime.Caching both allow dependencies on other cache entries without needing to manually mess with tokens yourself.
It sounds like the documentation is incorrect in its assertion that you can configure cache entries to depend on other cache entries.

How do you update the the first entry?

We are closing this issue because no further action is planned for this issue. If you still have any issues or questions, please log a new issue with any additional details that you have.


SUBMARINE-432. [SDK] test_verify_rest_response is flaky in python 3.5

What is this PR for?
Fix test failure in python3.5
if we use python3.5 str({'a': 200, 'b': 2, 'c': 3}) will output different order like {'b': 2, 'c': 3, 'a': 200}
change to str(json object) will fix it.
with pytest.raises(RestException, match=str(mock_json_body)):
verify_rest_response(mock_response, '/api/v1/jobs')
E AssertionError: Pattern '{'b': 2, 'c': 3, 'a': 200}' not found in 'None: Response: {'c': 3, 'a': 200, 'b': 2}'

What type of PR is it?
[Bug Fix]
Todos

[ ] - Task

What is the Jira issue?
https://issues.apache.org/jira/browse/SUBMARINE-432
How should this be tested?
https://travis-ci.org/github/pingsutw/hadoop-submarine/builds/663060104
https://github.com/pingsutw/hadoop-submarine/runs/511082403
Screenshots (if appropriate)
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

@liuxunorg Thanks for the review and commit.


Node verified and UP but status N/A

I have my node up but showing my status N/A even i got shadows in my wallet

Please provide the full node address here in text. We can't copy the node address from a screenshot. Along with that, how many nodes are connected to your discord user?

This is my first node id but i lost my access to it. Becuase i formatted my ubuntu and lost my priv key. Also how can i get my priv key from support to get access to this account?
GLmFf23GA9jU6NJacm3Yb3b7rRdekTcQ2aDvQ4tetniL
This is the second one which i created and now is up
BUzcDRgs6Hvki7CA24E73yVhEzMepNEMpwRQtWv9Md3b

Please provide the full node address here in text. We can't copy the node address from a screenshot. Along with that, how many nodes are connected to your discord user?

This is my first node id but i lost my access to it. Becuase i formatted my ubuntu and lost my priv key. Also how can i get my priv key from support to get access to this account?
GLmFf23GA9jU6NJacm3Yb3b7rRdekTcQ2aDvQ4tetniL
This is the second one which i created and now is up
BUzcDRgs6Hvki7CA24E73yVhEzMepNEMpwRQtWv9Md3b

You will need to remove GLmFf23GA9jU6NJacm3Yb3b7rRdekTcQ2aDvQ4tetniL from your discord user through the verification system if you've added it, previously.
As for your private key, nobody can recover it for you. That defeats the purpose of a secure private key. You are solely responsible for keeping track of your keys.

The problem is yesterday i had one node is but having the same issue. Do you have any comment for this?

You will need to remove GLmFf23GA9jU6NJacm3Yb3b7rRdekTcQ2aDvQ4tetniL from your discord user through the verification system if you've added it, previously.
As for your private key, nobody can recover it for you. That defeats the purpose of a secure private key. You are solely responsible for keeping track of your keys.

The problem is yesterday i had one node is but having the same issue. Do you have any comment for this?

What time in UTC was this at, yesterday?

You will need to remove GLmFf23GA9jU6NJacm3Yb3b7rRdekTcQ2aDvQ4tetniL from your discord user through the verification system if you've added it, previously.
As for your private key, nobody can recover it for you. That defeats the purpose of a secure private key. You are solely responsible for keeping track of your keys.

The problem is yesterday i had one node is but having the same issue. Do you have any comment for this?

What time in UTC was this at, yesterday?

It was around 20:00. Check this one.

It looks like both of these have been removed from the discord verification system. Please try re-adding one of them to the verification system.
Additionally, if you are mamorucha in the Discord server, then the only wallet associated with your user is not a shdw node.
Not sure we can provide any further assistance here. Please try messaging in #general-tech-support in the Discord server and community members may be able to further assist you with this issue, as everything within the network seems to be operating as expected so this isn't a technical issue with dagger.


docs outdated on Label offset Table?

In both Label Offset Table and Postings Offset Table, there is a 4-byte entries field, but in ReadOffsetTable, read as following order:

cnt := d.Be32()
keyCount := d.Uvarint()
d.UvarintStr()
goto 2 if has more element

It seems that there is no entries in offset table, Am I missing anything?

cnt := d.Be32() is the #entries <4b> field. The len <4b> is gobbled up by encoding.NewDecbufAt(...).


Shape implemented not as derived from vector<size_t>

Why not just using Shape = std::vector<size_t>; or typedef std::vector<std::size_t> Shape_t;. Do you plan to extend the Shape class with additional data members and function methods?

We will be extending shape to allow for unspecified lengths. Having a real type also prevents non-shape vectors from accidentally being passed as shapes, as has happened when args were passed in the wrong order.

Ok, this makes sense.

I like the general idea of switching to "contains-a" instead of "is-a", and the change seems less disruptive than I would have expected within ngraph-tf proper. We should see how bad it is for the bridges.

@avijit-nervana This PR is intended to be a discussion on this. It will merge to master if and when it is ready and we all agree and not before. Your best bet is to click Request Changes now to prevent it from merging until you approve.

obsolete


Structured logging API in ClientLogger

Design ClientLogger API that supports efficiently adding key-value pairs to message context.
Implementation by default should output a message with populated context as a string (e.g. json) that's easy to parse.
Investigate passing context to APM tools through SLF4J MDC (depends on performance impact) or any other ways.

done in https://github.com/Azure/azure-sdk-for-java/pull/25247


Using with podman

I'm trying to use this with podman using the Docker API-compat socket. It seems like it'll probably work but I've hit a snag and don't know enough about the Docker ecosystem to know the "right solution" for a PR.
Running ctlptl apply with config to create a registry fails. It creates the container but then can't find it to proceed with the workflow. The problem is this line
https://github.com/tilt-dev/ctlptl/blob/f5d2f384255a1a1d435f0ffddf17d1805d7fd828/pkg/registry/registry.go#L106
If I change that to use the fully-qualified path docker.io/library/registry:2 then it works fine. I'm unsure if that would also work on native Docker though, or if instead I should add a check for podman and set the filter depending on Docker v podman. Thoughts?

ooh nice! Ya, would love to accept a PR that gets this working with podman
I just tried that with the docker CLI and it seemed to work OK. We also have pretty good integration tests that will run on CI, so don't worry too much about breaking it.

@ccakes what version of podman are you using? i was playing around with this and couldn't get the podman container ls --filter to work at all :thinking:

Thanks to

https://github.com/tilt-dev/ctlptl/pull/150

we now have a working registry with Podman. Using Podman pods to create network contexts still appears out of scope.
Meanwhile it happens that a specific networking setup for K3d clusters on Podman would also be required for connecting a K3d registry to a K3d cluster (on Podman):

https://github.com/tilt-dev/ctlptl/pull/265#issuecomment-1340214863

Besides the registries.conf addition (I put mine in ~/.config/containers/registries.conf), for running native rootless podman under Ubuntu 23.10 I also had to install the golang-github-containernetworking-plugin-dnsname package so the kind container could resolve the ctlptl-registry hostname. Since I already had the kind network created in podman, I had to run podman network rm kind and recreate the cluster/registry with ctlptl after installing the -plugin-dnsname package.

Creating local k8s clusters
Creating registry "ctlptl-registry"...
registry.ctlptl.dev/ctlptl-registry created
reading docker-desktop settings: Get "http://localhost/app/settings": dial unix /Users/amir/Library/Containers/com.docker.docker/Data/backend.sock: connect: no such file or directory
make: *** [Makefile:120: dev-env-cluster] Error 1

Another fun little issue with podman. ctlptl assumes its docker-desktop and tries to do docker-desktop things to it.

@aaomidi ??? what command are you running? we have a lot of integration tests. the machines they run on don't even have DD installed...


add LICENSE file

Docs/specs need this too, unfortunately.

I'm fine with any liberal OSI approved license.

I'm fine with any liberal OSI approved license.


Added support for Unity's ISerializationCallbackReceiver interface

Looks good, would you mind making the commented style fixes? I'll merge after that.

Finally got to it!

Thanks!


Keynote Speakers suggestion

Tasks

[ ] Prepare the Github discussion with the appropriate description
[ ] Create a bitly URL for the Github discussion for social media posts.
[ ] Prepare the content for the mailing list @Sc0rpi0n101
[ ] Prepare the content for the social media post, along with the picture @Sc0rpi0n101

Timeline
Post 4PM

[ ] Post on the inpycon mailing list @WatchfulHitman
[ ] Post on the social media channels, Instagram, Facebook, and Twitter @WatchfulHitman

Limit the conversation on Twitter so that people cannot reply on Twitter.

[ ] Send to other Python Mailing lists (BangPypers, PythonPune, HydPy, PyDelhi, ChennaiPy, MumbaiPy) @WatchfulHitman

Mailing List Content by Nikhil:
Hi everyone!

As you might already know, the preparations for PyCon India 2024 are underway[1]. We want to kick off the process of selecting the Keynote Speakers for the conference.

If you're new to PyCon India, our keynotes are a highlight; they're not just talks but impactful presentations delivered by distinguished community members. They provide valuable insights and perspectives from their experiences, genuinely elevating the conference atmosphere.

Please share your keynote speaker suggestions on the GitHub Discussion [2]. Please remember to send in one keynote speaker suggestion per comment containing a brief description of the speaker or include a link to the speaker's bio. If you like a speaker suggestion, please vote by writing a line about your vote, e.g., "I would also love to hear X as a keynote speaker [because of these Y reasons]".

We encourage suggestions from both Indian and international backgrounds as we aim to create a diverse lineup.

We will start reaching out to keynote speakers in the order of preference
within the next few weeks. Please suggest your keynote speakers by March 10th 23:59 IST.

[1]. https://mail.python.org/pipermail/inpycon/2024-January/013416.html
[2]. https://github.com/pythonindia/inpycon2024-tasks/discussions/25

Regards,
*Team PyCon India 2024*


[Feature request] A new git version string that builds from the literal latest commit

This might be a little weird, but I saw that inlay_hint got changed into inlay_hint.enable, so I wanted to update my config to fit it, but I found that the latest nightly does not have that commit included yet, and I don't see there being any way to get the latest git(latest seems to be the same as stable), so I had to grab the latest commit at the time myself and install that, so I thought it'd be nice to have a version tag git which will simply grab the newest commit and build with that.

Don't think I am following what you are trying to do, bob deals with 2 types of neovim files, binaries (nightly, stable and older versions) and source code so you can choose a specific commit paste it with bob install <commit hash> and it will build it for you.

Yeah, and I was hoping there can be a "version name"(like stable or nightly) for the latest commit, like even faster than nightly, because now if I manually set the latest commit to my version, it doesn't update with bob update because it is pinned.

So you want an alias for the last commit when running bob install?

So you want an alias for the last commit when running bob install?

I guess you can say an alias? But also when you do bob update, it installs the latest commit(like latest and nightly)

What would you call this alias?

I figured git would be a good name, similar to how AUR repos call it

Imo there is no need for this feature. Just wait for maximum 24 hours and then do bob install nightly. If you really want a feature just use the commit hash to install that specific commit.
KISS

I had this debate with myself as well, but the thing for me is that it's often not just this one time I want to do it(so I install the latest manually, uninstall tomorrow and update nightly), I would prefer if I could stay on the latest commit easily as you can with stable and nightly, at least personally, found it to be barely make past the -100 pts, plus it's not a particularly difficult feature either, and maybe it will come in helpful in the future.
Sorry, long sentences from me are very coherent, my point is, I think this is not complicated enough and is quite helpful when you need/want it, even if it's not often.
P.S. KISS is usually for designing systems, features typically use the -100pt rule

🤔

I will work on this, but it won't be a priority because it is slightly more complicated than expected

Something like this works if you have a get-github-token command or equivalent.
AUTH="Authorization: token $(get-github-token)"
SHA="$(curl -s -H "$AUTH" -H "Accept: application/vnd.github.VERSION.sha" https://api.github.com/repos/neovim/neovim/commits/master)"
bob install "$SHA"

Using a script like this could be a middle ground if nightly's are to slow and bob doesn't have a latest commit alias

@Ciel-MC Pretty late (I worked on this when you opened the issue but the solution originally was too complex) but the request is fulfilled.


how to make an ol.style.Text clickable?

I have a style.Text with ol.geom.Point.
How could I click the text and run some code?
<script>

    let labelStyle = new ol.style.Style({
        text: new ol.style.Text({
            font: 'bold 20px serif',
            text: 'here',
            fill: new ol.style.Fill({
                color: 'rgba(255, 0, 0, 1)'
            })
        })
    });

    let vectorSource = new ol.source.Vector();

    let vectorLayer = new ol.layer.Vector({
        source: vectorSource
    });

    let labelFeature = new ol.Feature({
        geometry: new ol.geom.Point([12956325, 4851028])
    });

    labelFeature.setStyle(labelStyle);

    vectorSource.addFeature(labelFeature);
    let map = new ol.Map({
        target: 'map',
        layers: [

            new ol.layer.Tile({
                source: new ol.source.OSM()
            }),

            vectorLayer
        ],
        view: ...
    });
</script>

I tried a normal text, sometimes it's clickable, sometimes not.
I trid an icon font to display an triangle, it's not clickable always.

Your example doesn't include the hit detection, so it's hard to say what may be the problem.
Here is an example with working hitdetection:
https://openlayers.org/en/latest/examples/icon.html
You may click the Edit button at the top-right to reproduce your problem and share the link with us here.

Your example doesn't include the hit detection, so it's hard to say what may be the problem.

Thank you.  But I did not use events on map. I am using ol.interaction.Select

If you need to see that you have selected text you would need to use style functions so the same text is displayed when selected and not selected https://codesandbox.io/s/street-labels-forked-0icpnj?file=/main.js


How to enable GPU support?

Thanks again for this package! Though I do have an active GPU on the device, it doesn't seem to be detected. Is there some way of enabling GPU acceleration (and would it be useful)?
No GPU active on this device
    Tuning XGBoost using CPU hyper-parameters. This will take time...

Found that this issue stems from further upstream with WSL not detecting the GPU - so closing the thread for now

Did you manage to use the gpu on WSL @zw10 ? I'm having the same issue


Default configuration for next js needs to be updated

I think the change from the command 'next export' to "output: export" in next.config.js has broken the default configuration
this doesnt work
      - name: Setup Pages
        uses: actions/configure-pages@v3
        with:
               static_site_generator: next

this does
      - name: Setup Pages
        uses: actions/configure-pages@v3

I have set up my own next config.
I spent some time trying to find out what was breaking my page so I thought I would pass this on so someone else doesnt have to

This might be resolved by https://github.com/actions/configure-pages/pull/102

A fix for this is now included in actions/configure-pages@v5. 🚀


Improve look of notifications.

This task is about properly design the look of the notifications to the user and apply it to our current implementation

The tasks for #5733 should be redesigned for new GUI


Unable to load altair: Linux latest snap

Describe the bug
This appears to be a very similar problem to that reported in https://github.com/imolorhe/altair/issues/1454 in the Mac environment. So similar that there is no point in repeating, except to say that loading just sits and does nothing in exactly the same fashion
To Reproduce
Select Altair from menu and click to run
Expected behavior
application to run
Screenshots
If applicable, add screenshots to help explain your problem.
I started altair from the command line. You can see in this screen shot that it is repeatedly looping and getting nowhere

Desktop (please complete the following information):

OS: Linux Ubuntu 20.04.2 LTS

snap-id:      qLPmwUZVQeeiCHb8QxmyQ9RUFOBLq2Qu
tracking:     latest/stable
refresh-date: today at 05:36 GMT
channels:
latest/stable:    3.2.1 2021-02-15 (56)  75MB -
latest/candidate: ↑
latest/beta:      ↑
latest/edge:      1.8.0 2018-08-13  (2) 156MB -
installed:          3.2.1            (56)  75MB

That issue was fixed in 3.2.2 which isn't on snap yet. The solution is to use the AppImage alternative or wait for the next release.

OK. cool. Thanks very much


Fix require for gem jira-ruby

Hello guys,
Just a very little fix. I tried today to use the "jira" action to add a comment on a jira ticket.
And I got an error on the require 'jira'.
I looked at the jira-ruby documentation (https://github.com/sumoheavy/jira-ruby) and it seems we need to require 'jira-ruby'.
That's what I did and it worked.
Best regards.

It looks like this change happened when jira-ruby 1.0 was released.
Thanks @pylebecq


Specifying container name

What this PR does / why we need it:
this command
kubectl logs $POD_NAME --namespace=default
will work fine if there is no other containers deployments other than vault,
but if there is , it will throw an error  Error from server (BadRequest): a container name must be specified for pod vault-operator-release-something ,
the fix is to specify the container name using  -c with the proper vault container name
-c vault-operator
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ ] DCO signed
[ ] Chart Version bumped
[ ] Variables are documented in the README.md
[ ] Title of the PR starts with chart name (e.g. [stable/chart])

/assign @mlaccetti

@hacktron95 just noticed that this isn't in the k8s org and I'm not a member; let me address that.

/assign @adamreese

/lgtm


feat: updating our callout emoji regex to use emoji-regex

Fix RM-3635

🧰 Changes
This updates our emoji regex in callouts to use the emoji-regex package.
We now require a space between the icon and title for callouts

This PR was released!
🚀 Changes included in v6.47.0


avergae FPS of each model

can provide more detail about inference speed of each model
the speed compare between each method
thanks

can provide more detail about inference speed of each model
the speed compare between each method
thanks

Do you mean the comparison of difference models (Swin-T, Swin-S, Swin-B and Swin-T)?  Will do, if I have the bandwidth.

Thanks for the reply, I am more concerned about the difference in inference speed between Transfromer and CNN after TRT acceleration, thanks! ! !


mutating trade IDs?

I downloaded some transaction data via the coinfloor REST API a while ago and recorded it to disk.  When I recently downloaded the same data I noticed that I had what appeared to be a bunch of over filled orders.  On closer inspection I noticed that I have two almost identical trades for a single order, differing only by their id.
The trade as it looks today is this:
  {
    "datetime": "2017-08-05 03:42:40",
    "id":<PHONE_NUMBER>496851,
    "type": 2,
    "xbt": "0.1000",
    "xbt_usd": "2678.00",
    "usd": "-267.80",
    "fee": "0.00",
    "order_id": 85721093
  }

But in the past i had this:
  {
    "datetime": "2017-08-05 03:42:40",
    "id":<PHONE_NUMBER>496850,
    "type": 2,
    "xbt": "0.1000",
    "xbt_usd": "2678.00",
    "usd": "-267.80",
    "fee": "0.00",
    "order_id": 85721093
  }

(Identical values apart from the id)
But this older version of the trade<PHONE_NUMBER>496850) is no longer returned but the API.  It's as if the trade id isn't constant.  Does it change? Could someone explain what's happened please?

Very thorough of you to notice. What happened is that the API had been returning rounded (to the "tens" place) trade IDs due to an unintended implicit cast in an SQL query in the back end. The bug in the back end has been fixed, but an unfortunate side effect is that trade IDs that were previously reported incorrectly are now being reported correctly, thus causing them to appear to have changed.
You will notice that, in every case, the corrected trade ID, when rounded to the "tens" place, matches a previously reported, incorrect trade ID. You could use this fact to correlate the corrected records with your existing records. Apologies for the inconvenience.

Incidentally, the "trade IDs" reported by the BIST API are really just the microsecond timestamps at which the trades occurred.

Hey @whitslack  - thanks for the quick reply! Understood.
What what it's worth, in my experience it doesn't pay to model database IDs in software as numbers.  Just because they look like numbers doesn't make them numeric.  You can't add them or multiply them, one ID isn't greater than another.  If you need to sort them by time then it's best and clearest to use an explicit time field.
But that's just my opinion! And the great thing about opinion is that it's easy to ignore ;)
Using a timestamp to generate an ID leaves you open to have 2 identical IDs though.  As unlikely as it is, it will happen at some point won't it?  Or do you have a way to guard against that happening?  I guess you can work out the exact likelihood from your data.  What would go wrong if this did happen?
Did you notify you customers of the change to the trade IDs?  It's taken me a while to figure this out and it played havoc with my accounting, I probably won't be the only one.

Using a timestamp to generate an ID leaves you open to have 2 identical IDs though. As unlikely as it is, it will happen at some point won't it? Or do you have a way to guard against that happening?

It won't be possible until computer hardware gets significantly faster. Back-to-back trades resulting from one limit order placement, despite being processed in native code in as tight a loop as we can manage, are still separated by hundreds of microseconds. No chance of duplicate trade timestamps for the foreseeable future.

Did you notify your customers of the change to the trade IDs? It's taken me a while to figure this out and it played havoc with my accounting, I probably won't be the only one.

I discovered the rounding issue on 14 July and immediately produced a fix, upon which I commented:

This fix corrects the trade transaction IDs reported by the BIST /user_transactions/ method so that they match the values actually recorded in the database, but this will appear to end users as though most (90%) of their historical trades are having their identifiers changed. If this is not acceptable, then we could augment the code so that it conditionally rounds trade timestamps older than the deployment date of this fix so that they match the previously (and erroneously) reported values. Alternatively, Coinfloor could send out an email blast to all users who have ever called the BIST /user_transactions/ method, informing them that the transaction IDs of their historical trades will be gaining an additional digit of precision thanks to a bug fix.

I followed up on 24 July:

Have we reached a decision about whether to explicitly round timestamps prior to the fix or to tell customers that trade IDs previously returned from /user_transactions/ were inaccurate?

The answer I received back was that the three biggest customers had reported that they would have no problems with the historical trade IDs changing and to go ahead with the fix. The fix was deployed to Coinfloor's internal test platform on 12 September and then to production on 20 September. Evidently no notification was ever sent out to customers. I do apologize for that. As you can see, I tried.

Where were these announcement made, via email?  I didn't get it.
You say it won't be possible to get duplicate IDs - is that because you are processing trades on a single server?

Where were these announcement made, via email? I didn't get it.

What I was trying to say is that I urged them to announce the change to customers by email, but I don't think they did it.

You say it won't be possible to get duplicate IDs - is that because you are processing trades on a single server?

There are multiple servers that handle the APIs (WebSocket and BIST), but order matching (i.e., trading) occurs on a single server.


Support XDG_CACHE_HOME environment variable

By using the XDG_CACHE_HOME environment variable, people who set kubectl's config file elsewhere (using the KUBECONFIG environment variable) could now bypass the error that ~/.kube directory doesn't exist, and also support the XDG standard :)

I signed it!

@rafi thanks for your patch. Does kubectl actually respect XDG_CACHE_HOME today to locate your .kube/config file? If so, we can follow suit.

@ahmetb No, it doesn't. But it supports the KUBECONFIG set a single or multiple configuration files, e.g. export KUBECONFIG="$XDG_CONFIG_HOME/kube/config.yml"

I see we're using ~/.kube for caching stuff, so this will work. But you will still need to set KUBECONFIG to actually make things work.
I'll think a bit to see if this matches XDG_CACHE_HOME, XDG_CONFIG_HOME or XDG_DATA_HOME. But I think your patch is fine, I may merge it soon.

Thanks a lot for your PR.


Webpack Image Support

DO NOT MERGE. IN PROGRESS

We already have svg load in renderer config.

What do you think about moving these changes to the renderer instead?

@jhen0409 would be great if you could review

What do you think about moving these changes to the webpack renderer config instead?

Yeah I think we should moving these changes to renderer config, because main process may not need it.
Also I think we can have renderer base config for development and production on webpack.config.base.js.

@jhen0409 Made my changes. Do they reflect what you described?


Is there a server issue for the downloading cityscape left sequence (324GB)

I am trying to download leftImg8bit_sequence_trainvaltest.zip (324GB) but cancels in the morning (CEST). This occurs in every attempt while using this script or directly from the website.
Kindly can you provide a solution to it.

Hi @testingshanu , I met the same issue. Have you managed to download it?
Thanks

Hi @testingshanu @jiaqixuac
if anyone of you have got the "leftImg8bit_sequence_trainvaltest" dataset, could you share just the "validation" split of it with me, please?
Let me know if it's possible for you to share a download link with me on my email


Add more adhoc tests configs.

Bug:
https://github.com/flutter/flutter/issues/63807

LGTM.
Nit: (Not related to this PR) validation_name analyze => Analyze for both linux try and prod builder.

Updated.


jfrog rt bdi - cannot delete promoted builds

Hello Jfrog
I have a cleanup script looking through my builds and deleting old builds. I have noticed that nothing is really deleted. The command I'm running is:
jfrog rt bdi --exlude-builds="xxx"
And in the log I find: Build 'xxx 'yyy' will not be discarded since it has been promoted in it's past.
I run "jfrog rt bpr ...." on every deployment to update build status and set properties on the relevant artifacts.
I can easily delete the builds in the UI. Is there any way to force jfrog rt bdi to delete builds even if they have been promoted in the past?
Artifactory version: Commercial license 7.5.5 rev 70505900
Brgds
Søren

@srindal -
This restriction is enforced on Artifactory's side, and it looks like there isn't a way to avoid this restriction by using the REST API (which is used by JFrog CLI).

Thanks for the answer. It's so strange and inconsequent. The cli don't report anything, it just completes without deleting anything. In the UI however I can delete these builds without being warned that they are promoted. What's the logic behind? I find it hard to believe that this is as designed.

I don't know, but if I specify jf rt bdi <name> --max-build 20 --delete-artifacts I'd expect that promoted builds not be deleted, even if they fall into the group that you requested to be deleted. These are "special" builds that you (or somebody wanted to actually avoid being deleted).

@srindal @enaess is this for all promoted builds or just builds promoted to status "Released"?
Is it possible to run the build discard cli command and exclude promoted "Released" builds? Or does it just ignore all promoted builds?

I am sure you can setup a test project and try that on a build.
Perhaps a clarification on this feature is in place by JFROG. But also @red8888 and @srindal, the logic to track what released build and explicitly exclude them seems like extra overhead you don't really need here. That is, if builds promoted are already excluded from the list of builds to be discarded and it is by design.
While you can design build promotions and release builds in many different ways dependent on what you are building, and how your pipeline for automatic deployment and testing looks like. What is missing in my opinion is a "best practices" guide to appropriately setup e.g. your Java builds, native builds, or even docker builds + releases, how does this differ if you design w/security in mind, see X-Ray, and how the build promotion resolve specific problems you may have. Right now, I am sitting here and having to figure that out on my own.
Jfrog documentation is either too high level, and/or specific documentation is too detailed with lack of the overall picture to what the problem you are trying to solve. There is little information in between that helps you connect the dots.


few doubts over sharing_createLink

can have more clarity over sharing_createLink (https://github.com/OneDrive/onedrive-api-docs/blob/master/items/sharing_createLink.md)
once the link generated,
Q1) when link will be expired?
Q2) will link be modified when file is updated for several time?
Q3) is it advisable to store share link, so tht whenever want to share with other, api calls will be saved?

#1: Sharing links don't expire. They can be deleted by the app that created them or by others with edit access, but they don't automatically expire.
#2: The link is always the same, but points to the "live" version of the file, so if someone makes edits to the file, the link points to the file with those edits.
#3: If an app asks calls createLink multiple times for the same kind of link (edit or view) we'll always return back an existing link if there is one.

I've added more details about sharing links, including the above answers, to the docs for createLink. These changes will go live with our next site refresh.

So Ryan, you don’t need anything from the UA side on this, right?
From: Ryan Gregg<EMAIL_ADDRESS>Sent: Sunday, May 3, 2015 8:18 AM
To: OneDrive/onedrive-api-docs
Subject: Re: [onedrive-api-docs] few doubts over sharing_createLink (#87)
I've added more details about sharing links, including the above answers, to the docs for createLink. These changes will go live with our next site refresh.
—
Reply to this email directly or view it on GitHubhttps://github.com/OneDrive/onedrive-api-docs/issues/87#issuecomment-98492111.

Nope. Thanks for reaching out though.
Sent from Outlookhttp://taps.io/outlookmobile
On Sun, May 3, 2015 at 4:33 PM -0700, "NGattuccio" <notifications<EMAIL_ADDRESS>wrote:
So Ryan, you don't need anything from the UA side on this, right?
From: Ryan Gregg<EMAIL_ADDRESS>Sent: Sunday, May 3, 2015 8:18 AM
To: OneDrive/onedrive-api-docs
Subject: Re: [onedrive-api-docs] few doubts over sharing_createLink (#87)
I've added more details about sharing links, including the above answers, to the docs for createLink. These changes will go live with our next site refresh.

Reply to this email directly or view it on GitHubhttps://github.com/OneDrive/onedrive-api-docs/issues/87#issuecomment-98492111.

Reply to this email directly or view it on GitHubhttps://github.com/OneDrive/onedrive-api-docs/issues/87#issuecomment-98556303.


[Bug] Default option is not passed by TVMC Front end

Under Hybrid Target, I have created target specific config or compiler options in the backend(codegen), These option are given with default values too.
Example:
TVM_ROOT/src/relay/backend/contrib/my_target/codegen.cc
struct MyCompilerConfigNode : public tvm::AttrsNode {
String mcpu;
TVM_DECLARE_ATTRS(MyCompilerConfigNode, "ext.attrs.MyCompilerConfigNode") {
TVM_ATTR_FIELD(mcpu)
.describe("CPU type")
.set_default("my_cpu");  <=========
}
};
In the TVMC , I try to access those options under the partition_for_target function
TVM_ROOT/relay/op/contrib/target.py
However, the default values given to these options are not visible.
I doubt TVMC is not handling or honoring the default values for options.
I have no clue if it works for other hybrid target like cmsis-nn or vitis-ai ? Could some put light on this ?
Expected behavior
What you were expecting
Actual behavior
Am expecting the default values for any command line options described in the codegen.cc
Environment
Any environment details, such as: Operating System, TVM version, etc
Steps to reproduce
Preferably a minimal script to cause the issue to occur.
Triage
Please refer to the list of label tags here to find the relevant tags and add them below in a bullet format (example below).

needs-triage

https://github.com/apache/tvm/pull/17014/
PR has been merged , hence closing this ticket


Template.dynamic appears to be broken

Ui.dynamic has been replaced with Template.dynamic. However, this:
+Template.dynamic(template=template)

Gives me this error: Expected template or null, found: undefined
{{> Template.dynamic template=template}}

Works correctly if it's in an .html file, but not when it's in a .jade file.

Sorry to bump a closed issue but I am having this problem (0.4.1).
+template.dynamic(template='hello')

I tested it in a fresh meteor app with the initial html file converted to jade:
Uncaught Error: Expected template or null, found: undefined
The crazy thing is this works:
+UI.dynamic(template='hello')

I am on<EMAIL_ADDRESS>

I cant get it to work! i changed the value of Template in many ways, but still not working, help please!
<body>

    {{> Template.dynamic template=Template data=data}}

</body>

<template name="Dynamic">
    {{#with getTemplate name}}
        {{> template}}
    {{/with}}
</template>

  Template.body.helpers({
    'Template': function() {
      return page.template;
    },
    'data': function() {
      return page.getTemplate();
    }
  });

'data' is fake, i was just testing everything.
I'm using the last version,  <IP_ADDRESS>


Request for help

Hello, I am new to Gnome apps and I really like to develop with GTK platform, but to be honest I have not found a good resource to get started. (Maybe because GTK is not used very much)
I know this request is off topic, but if it would be awesome if someone could suggest me a good resource (not including the docs) on how to use Gnome Builder and GTK 4 platform, or tell how you got stared building Gtk apps
Sorry if I am spamming you, but I would appreciate any reply! (You can close this "issue" any time you want)

Personally, I got started by learning Rust. To use GTK, you should have a pretty thorough understanding of the language you want to use. After that, I went through a large part of the gtk-rs book, revisiting chapters I didn’t understand after some time. I’ve also learned a lot by hanging around in GNOME’s social spaces on Matrix, Reddit and Discourse, so I definitely recommend to join them!
One tip is to make it a habit to use the docs as early as possible. You have the main GTK docs for C, and the docs specific to GTK for your language. If you understand how the main GTK docs for C are connected to your programming language, you’ll be all set once you know where the bits and pieces go.

To try building a project in GNOME Builder, just open Builder, click «Clone Repository», paste this URL: https://gitlab.gnome.org/World/Solanum.git, confirm, wait for things to load properly, click the play button and see what happens!

Thank you very much. I didn't expect any replies. You gave me some amazing resorses to follow.
I am excited to get started 😊. Thank you again!

Thanks a lot @bragefuglseth  :)


AllJoyn DSB Template: AdapterBackgroundService deploy error.

I am trying to run the AllJoyn DSB template and follow the GpioDevice Sample Tutorial.
I can succesfully run AdapterHostApp on my Win10 PC. However, when I tried to deploy "AdapterBackgroundService" to a MBM Win IoT Core system, I got the following error:
Error : DEP0700 : Registration of the app failed. C:.......\App1AdapterBackgroundServiceVS.Debug_Win32.Tester\AppxManifest.xml(25,6): error 0x80070490: Cannot register the App1AdapterBackgroundService_<IP_ADDRESS>_x86__XXXXX package because the following error was encountered while parsing the App1AdapterBackgroundService application: Element not found. Try again and contact the package publisher if the problem persists. (0x80073cf6).
Can any one help?

Hello,
We've reproduced this issue. Turns out the required Assets\ that are referenced in project AdapterBackgroundService file Package.appxmanifest are missing. They are present in the AdapterHostApp project.
So, to fix:

Copy Assets directory from AdapterHostApp folder to AdapterBackgroundService folder.
Under AdapterBackgroundService project, right click, Add -> New Filter, call it "Assets"
Right click on the created "Assets" filter,  Add -> Existing Item, and select all files under AdapterBackgroundService\Assets\

This will add all the missing Assets files back to AdapterBackgroundService.

Great. It fixes it.  By the way, do you know why there can only be 1 background service running at 1 time?  When I deploy this, the in-box ZWave Adapter service stops.

The template DeviceSystemBridgeTemplate.vsix file at https://github.com/ms-iot/samples/tree/develop/AllJoyn/AllJoynDSBGuide has been updated with the Assets fix.


Add option to disable inline representation of tagged field content when writing to ASDF file

I do not see this in the docs, but currently when writing to ASDF file, all ASDF tags are written inline if it is not nested (i.e., all children are leaf nodes).
Current Behavior:
#ASDF 1.0.0
#ASDF_STANDARD 1.5.0
%YAML 1.1
%TAG ! tag:stsci.edu:asdf/
--- !core/asdf-1.1.0
asdf_library: !core/software-1.0.0 {author: The ASDF Developers, homepage: 'http://github.com/asdf-format/asdf',
  name: asdf, version: 2.14.3}

Desired Behavior:
#ASDF 1.0.0
#ASDF_STANDARD 1.5.0
%YAML 1.1
%TAG ! tag:stsci.edu:asdf/
--- !core/asdf-1.1.0
asdf_library: !core/software-1.0.0
  author: The ASDF Developers
  homepage: 'http://github.com/asdf-format/asdf',
  name: asdf,
  version: 2.14.3

Can we add an option to disable this and I much prefer this to be the default.

Here's an example what happens if the tagged field has a child field
node: !<asdf://example.com/tags/node-1.0.0>
  child: !<asdf://example.com/tags/node-1.0.0> {child: null}

This looks a bit silly

This should be controlled by the flowStyle setting in the schema describing the tag. See https://asdf-standard.readthedocs.io/en/1.5.0/schemas/yaml_schema.html#Schema Definitions for details. Not that in your case I believe you need to set flowStyle: block in the schema.
It should work as the Roman asdf files make extensive use of this. For example if one generates and saves a wfi_image, its schema contains flowStyle: block here. A sample header is:
roman: !<asdf://stsci.edu/datamodels/roman/tags/wfi_image-1.0.0>
  meta:
    aperture: !<asdf://stsci.edu/datamodels/roman/tags/aperture-1.0.0>
      name: WFI_06_FULL
      position_angle: 30.149604523080143
    cal_step: !<asdf://stsci.edu/datamodels/roman/tags/cal_step-1.0.0>
      assign_wcs: INCOMPLETE
      flat_field: SKIPPED
      dark: COMPLETE
      dq_init: COMPLETE
      jump: COMPLETE
      linearity: SKIPPED
      photom: COMPLETE
      ramp_fit: COMPLETE
      saturation: INCOMPLETE
    calibration_software_version: !<asdf://stsci.edu/datamodels/roman/tags/calibration_software_version-1.0.0> Version
      94bb92d0a922867c94ed1fddcb4216a5
    coordinates: !<asdf://stsci.edu/datamodels/roman/tags/coordinates-1.0.0>
      reference_frame: ICRS
    crds_context_used: roman_8226.pmap
    crds_software_version: 63.1.67
    ephemeris: !<asdf://stsci.edu/datamodels/roman/tags/ephemeris-1.0.0>
      earth_angle: 1.301915411283766
      moon_angle: 1.1516403400836825
      sun_angle: 2.736255246678112
      type: PREDICTED
      time: 59865.65463414276
      ephemeris_reference_frame: Frame 3706a1f3
      spatial_x: -1.3623950365305825e+308
      spatial_y: -1.60804538172114e+306
      spatial_z: 1.5921914973582028e+307
      velocity_x: 1.3125923623238684e+308
      velocity_y: -1.6632717836035864e+308
      velocity_z: 2.352229275461757e+307

I believe yaml would have normally chosen to represent the part under aperture in the way you describe if the schemas involved did not specify the flowStyle: block.

How would I control this without defining a schema for the tag?
One may want to overwrite all tag's preference after all this is just for the serialization and does not affect deseralization.

This is currently not supported outside of setting the style within the tag definition. However, looking at the early history, adjusting the default for serialization was planned but never finished, see:
https://github.com/asdf-format/asdf/blob/d33ca09e62769a7e92e43af7ca3ae61eeb2e14ef/asdf/yamlutil.py#L90-L95
Please feel free to explore how to do this further if you wish and open PR adding the feature if you figure out how to do it.
Now I do have some broad thoughts on how to accomplish this. Note that the flowStyle key is read into this class attribute:

https://github.com/asdf-format/asdf/blob/d33ca09e62769a7e92e43af7ca3ae61eeb2e14ef/asdf/tagged.py#L59
https://github.com/asdf-format/asdf/blob/d33ca09e62769a7e92e43af7ca3ae61eeb2e14ef/asdf/tagged.py#L87

For the two wrapper objects that are used to wrap tagged objects in the ASDF tree. This is then read by the yaml dumper routines:

https://github.com/asdf-format/asdf/blob/d33ca09e62769a7e92e43af7ca3ae61eeb2e14ef/asdf/yamlutil.py#L57
https://github.com/asdf-format/asdf/blob/d33ca09e62769a7e92e43af7ca3ae61eeb2e14ef/asdf/yamlutil.py#L51

for the two wrapper types above. Thus if you examine the raw ASDF tree, once its been converted into data by the converters, you should be able to set the flow_style keyword on the tagged objects you wish to effect and then when that tree is passed through to pyyaml for dumping using the AsdfDumper everything should get correctly read and adjusted accordingly.
How and when to access will require more in-depth investigation and experimentation.

Very informative, thank you! I will take a stab it this.
First, ASDF is using whatever default the pyyaml dumper is using. This is fine as-is, but if ASDF has a preference, the change seems simple and this would not ignore the tag definition schema preference.
- flow_style = _flow_style_map.get(mapping.flow_style, None)
+ flow_style = _flow_style_map.get(mapping.flow_style, _flow_style_map['block'])

For adding user overrides of flow style, I'm seeing this would have to come from the configs elsewhere as the function signature for the representers will not support this (unless I'm mistaken and the object type for data/mapper/sequence do contain user configs).
Lastly, what are the interfaces the users can use to set stylistics preferences. Is it just AsdfFile.write_to() and/or config (e.g., asdf.get_config())?

This block style is not necessarily ideal, so I disagree with forcing the default to be "block".
Since ASDF uses pyyaml to write the yaml output to the header, it was decided that we would just let pyyaml decide how best to format the yaml rather than making a single decision. pyyaml uses a heuristic to decide when to switch from "flow" style to "block" style, and we felt like this seemed appropriate way to standardize the decision. Moreover, if users of ASDF disagree with this approach they can simply configure their schemas appropriately.
In so far as, enabling user overrides placing the interface in the asdf-config is a fine idea, this can even enable the AsdfFile.write_to() to set the overrides by simply letting it use the config context to temporally modify the configuration for a given write.

Note that "inlining" arrays (storing them in the yaml directly, instead of in a binary block) operates on the same principle as the flow_style, except it has a global configuration option which passes through to a write option.
The global setting for this is controlled by the all_array_storage setting in the AsdfConfig: https://github.com/asdf-format/asdf/blob/8dce02c664a9acbb7fd3e5335f5f373681ef10fc/asdf/config.py#L325-L347
I believe something like global_flow_style could be done in a similar way.

Here is where all_array_storage passes into the writing of the file:
https://github.com/asdf-format/asdf/blob/8dce02c664a9acbb7fd3e5335f5f373681ef10fc/asdf/asdf.py#L1188-L1190

This block style is not necessarily ideal, so I disagree with forcing the default to be "block".
pyyaml uses a heuristic

Okay I won't push further, but I will say it's not much of a heuristic -- it looks to be just a consistency rule:

By default, PyYAML chooses the style of a collection depending on whether it has nested collections. If a collection has nested collections, it will be assigned the block style. Otherwise it will have the flow style.
-- PyYAML

Thank you, the existing config for array serialization styling helps a lot.


Fix GUI for client

The GUI for the client is not centered properly and can't handle resizing.

The client GUI also needs the following things.
*Feedback when certain events complete (downloading sources, sending sources to server)
*An indication when the client is and isn't connnected to the server.
*Cleanup of unused textfields in the clientview.

Almost done, needs to test it on ubuntu or similar OS that is a bit more common than arch


Accelerate Diffusers CI

What does this PR do?

This PR aims at making the Diffusers fast tests faster:

some tests are now marked as slow, so they'll be executed in the nightly CI
Diffusers fast tests will now run in parallel of Transformers fast tests instead of waiting for them to be finished

Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Chapter 2 locked after completion of Chapter 1

Even after completing challenge 1 Chapter 2 remains locked from the Chapters page

Closed by #329


"Reporting service" contains additional spaces

@okamara, please add more details about this issue

unable to register git repository: reporting-service and open in inside jenkins correctly.
we already have several rules in nginx to redirect reporting-service traffic into the Zafira. But if it is "/jenkins/jobs/reporting-service" it should be moved to jenkins

fixed: https://github.com/zebrunner/zebrunner/commit/fd62cf6283c310ba089e5287bb66147e7d20ccfe
test scenario:

setup and start zebrunner from develo branch
register organization "zebrunner"
register repository "reporting-service" inside zebrunner folder on jenkins
open reporting-service folder on jenkins
-> folder is opened in jenkins
->onPush-reporting-service is red - as expected

Verified on release 5.2 version.Fixed.


Infering passed type of function argument?

const a = (a: string) => { }

const b = (...args: Parameters<typeof a>) {
}

// TS says x is any here, that's why it doesn't work as expected
const c = (x) => (...args: Parameters<typeof x>) => {
}

const d = <T>(...args: Parameters<T>) => {
}

// works:
b()

// doesnt work. i would like to get this working
c(a)(1)

// dont want this solution
d<typeof a>(1)

x is any because you're not explicitly giving it a type. If you want behavior where the next function call infers its argument type based on the previous, then you can do something like:
const c = <T extends (...args: any[]) => any>(x: T) => (...args: Parameters<T>) => {}

and then when you put in c(a) typescript infers the next function as (a: string) => void

Wow you are genius! it really works! thanks you !!!


Image Recon Notebook Updates and new plot_example jupyter Notebook

Updated Image recon notebook to HD and SPARSE probe and validated. TBD: use better headmodel (recon does not look convincing)

extended datasets.py to fetch new data

minor updates on finger_tapping_full_pipeline (not to be used for workshop)

Added new plots_example jupyter notebook. It includes the two gui plots from @ahns97 and @lauracarlton. plot_probe is currently commented out because i could not get it to run

i added @lauracarlton's scalp_plot as an example ot the plots_example notebook, removed a minor bug and did some docstring cleanup. I think this is ready to be merged now. Not planning other changes before the workshop @emiddell


PWA-486: HTML widget is now rerendered when config updates

Pull Request Test Coverage Report for Build 950

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 41.182%

Totals

Change from base Build 949:
0.0%

Covered Lines:
1559

Relevant Lines:
3795

💛  - Coveralls

Pull Request Test Coverage Report for Build 951

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 41.182%

Totals

Change from base Build 949:
0.0%

Covered Lines:
1559

Relevant Lines:
3795

💛  - Coveralls

Fixed


[1.1.1a] secondary library linked against libssl cannot dlopen()ed on AIX

Hi *,
a devteam using my provided OpenSSL 1.1.1a build for AIX runs into another issue I haven't seen so far coming my way.
They attempt to dlopen() a shared library that itself is linked against libssl and libcrypto and receive the following error:
 Library libfoo.so could not be loaded.

      Library Path: /path/to/foo/lib/libfoo.so
      ERROR: "rtld: 0712-001 Symbol main was referenced
      from module /path/to/openssl/lib/libssl.a(libssl64.so.1.1),
                but a runtime definition of the symbol was not found.
                rtld: 0712-001 Symbol main was referenced
      from module /path/to/openssl/lib/libcrypto.a(libcrypto64.so.1.1),
                but a runtime definition of the symbol was not found."

I am not quite sure why there is no symbol main in the runtime context, but that's not the point. The point is that both libraries are indeed importing main:
$ dump -X64 -Tv libssl.a
libssl.a[libssl64.so.1.1]:

                        ***Loader Section***

                        ***Loader Symbol Table Information***
[Index]      Value      Scn     IMEX Sclass   Type           IMPid Name

[0]     0x00000000    undef      IMP     RW EXTref libc.a(shr_64.o) errno
[...]
[955]   0x00000000    undef      IMP     DS EXTref              .. main

and
$ dump -X64 -Tv libcrypto.a

libcrypto.a[libcrypto64.so.1.1]:

                        ***Loader Section***

                        ***Loader Symbol Table Information***
[Index]      Value      Scn     IMEX Sclass   Type           IMPid Name

[0]     0x00000000    undef      IMP     RW EXTref libc.a(shr_64.o) errno
[...]
[4497]  0x00000000    undef      IMP     DS EXTref              .. main

Both are the very last entry in their table. Both are referencing .. as module to import main from. There is no problem if a program with a main()-function is calling dlopen() on libfoo.so.
Why is it referencing main and what is it used for?

I tried to grep through the source in crypto/ if I could find it, but to no avail.  I have no clue!  The only place I know that we deal with main at all is in libtestutil, with the test apps, but that shouldn't affect the main libraries...  however, this being AIX, I'm ready for surprises!

OK, I see. I'll try to find some clue on a live system...

Please do

Looks as if the $shared_ldflag in Configurations/10-main.conf:aix-common needs to be extended by ,-bnoentry. This remove quite a number of symbol references and still works with my brief tests. But as I couldn't provoke the original error anyway, I'll check with the complaining devteam first.

Okie.  Will you submit a PR if a change is actually needed?

Sure.

The PR #8282 should also go into 1.1.1. Let me know if you need a separate PR for this.


Data Flow Manifest

Initial version as Table and Flowchart in:
https://miro.com/app/board/uXjVKWSQqAk=/

Done in Miro


permission denied

Permission denied while running nr i, after installing @antfu/ni globally.

Permission denied while running nr i, after installing @antfu/ni globally.

missing script i， if you want install dependencies, you should exec ni, if you want run some script cmd, you should exec nr your script, eg: nr dev, nr start

This is probably not an issue of ni itself.

I encountered this problem after upgrading Node, running the following command to solve this problem:
sudo npm cache clean --force --unsafe-perm

https://stackoverflow.com/a/57268608/16248512


add spacesBetweenYears config option

Many projects already have copyright statements with years in the format "YYYY-YYYY". This adds a new spacesBetweenYears config option to allow maintaining that style.
Fixes #32.

I will be back online on Monday. I will create a new release on the marketplace then.
D


[Bug]: Interface 'JestImportMeta' incorrectly extends interface 'ImportMeta' in @jest/environment v29.7.0

Version
29.7.0
Steps to reproduce

Install @jest/environment
Enable exactOptionalPropertyTypes in your tsconfig
Run TS

See skaut/shared-drive-mover#1741
Expected behavior
No error
Actual behavior
/home/user/project/node_modules/@jest/environment/build/index.d.ts:401:26
Error: Interface 'JestImportMeta' incorrectly extends interface 'ImportMeta'.
  The types of 'jest.doMock' are incompatible between these types.
    Type '<T = unknown>(moduleName: string, moduleFactory?: (() => T) | undefined, options?: { virtual?: boolean; } | undefined) => Jest' is not assignable to type '<T = unknown>(moduleName: string, factory?: (() => T) | undefined, options?: MockOptions | undefined) => typeof jest'.
      Types of parameters 'options' and 'options' are incompatible.
        Type 'MockOptions | undefined' is not assignable to type '{ virtual?: boolean; } | undefined'.
          Type 'MockOptions' is not assignable to type '{ virtual?: boolean; }' with 'exactOptionalPropertyTypes: true'. Consider adding 'undefined' to the types of the target's properties.
            Types of property 'virtual' are incompatible.
              Type 'boolean | undefined' is not assignable to type 'boolean'.
                Type 'undefined' is not assignable to type 'boolean'.

export declare interface JestImportMeta extends ImportMeta {
  jest: Jest;

Additional context
No response
Environment
System:
  OS: Linux 6.5 Ubuntu 22.04.4 LTS 22.04.4 LTS (Jammy Jellyfish)
  CPU: (12) x64 12th Gen Intel(R) Core(TM) i7-1265U
Binaries:
  Node: 22.8.0 - /usr/bin/node
  Yarn: 1.22.21 - /usr/bin/yarn
  npm: 10.8.3 - /usr/bin/npm
  pnpm: 8.14.3 - /usr/bin/pnpm
npmPackages:
  jest: ^29.7.0 => 29.7.0

Could you check, if merging https://github.com/DefinitelyTyped/DefinitelyTyped/pull/70464 would fix the problem?

The PR that I mentioned got merged. Can you check with the latest version of @types/jest?


Document the Render setup process w/ blueprints

Document the workflow, and maybe save the knex setup scripts in package.json

Fixed with #373 and #374


"connect ECONNREFUSED <IP_ADDRESS>:443" in Node.js Lambda

I followed the instructions from the blog post: https://stackimpact.com/blog/aws-lambda-cpu-and-memory-profiling-node-js/. But it seems that something's wrong with the agent:

StackImpact 1.1.4: Error uploading messages to the dashboard, backing off next upload
StackImpact 1.1.4: connect ECONNREFUSED <IP_ADDRESS>:443
StackImpact 1.1.4: Error: connect ECONNREFUSED <IP_ADDRESS>:443 at Object.exports._errnoException (util.js:1018:11) at exports._exceptionWithHostPort (util.js:1041:20) at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1086:14)

I'm not sure how it is supposed to work. I use Serverless to build Lambdas on my local Macbook, so npm install stackimpact would yield:
> node node-gyp-fallback.js

Pre-built version of StackImpact addon not found, trying to build.
  CXX(target) Release/obj.target/stackimpact-addon/src/stackimpact_addon.o
  CXX(target) Release/obj.target/stackimpact-addon/src/heap_stats.o
  CXX(target) Release/obj.target/stackimpact-addon/src/gc_stats.o
  CXX(target) Release/obj.target/stackimpact-addon/src/event_loop_stats.o
  CXX(target) Release/obj.target/stackimpact-addon/src/cpu_profiler.o
  CXX(target) Release/obj.target/stackimpact-addon/src/allocation_sampler.o
  SOLINK_MODULE(target) Release/stackimpact-addon.node
npm WARN<EMAIL_ADDRESS>No repository field.

+<EMAIL_ADDRESS>added 2 packages in 5.074s

Then serverless deploy would package everything including ./node_modules/ and upload it to AWS. But how an executable that was built against OS X will run on Amazon Linux?

But how an executable that was built against OS X will run on Amazon Linux?

That's not the issue. Deploying from Amazon Linux machine leads to the same result:

StackImpact 1.1.4: Using pre-built native addon.
StackImpact 1.1.4: Agent started
...
StackImpact 1.1.4: ApiRequest: config request took 396ms
StackImpact 1.1.4: { hostname: 'agent-api.stackimpact.com',
port: null,
method: 'POST',
path: '/agent/v1/config',
headers:
{ Host: 'agent-api.stackimpact.com',
'Content-Type': 'application/json',
'Content-Encoding': 'gzip',
'Accept-Encoding': 'gzip',
Authorization: 'Basic XXXXXXX=' } }
...
StackImpact 1.1.4: Agent deactivated.
...
StackImpact 1.1.4: Using pre-built native addon.
...
StackImpact 1.1.4: connect ECONNREFUSED <IP_ADDRESS>:443

I'm worried about that Agent deactivated part.

I figured it out. You have to do stackimpact.start(...) outside your handler. For some reason you can't create a new agent per every call (makes sence, why would you do that?) or maybe have to destroy agent at the end of a call.


Use GraalVM to provide more language support + es6 support

GraalVm has a larger selection of scripts languages that are supported, and their GraalJS supports es6 , so there is better node package support.
Also, specifically for JS, Graal is several times faster in execution of JS, compared to nashorn.

Hi @StephenOTT, thank you for the proposal. I'll have a look into it.
Are you only interested in the better JS engine, or do you want to use other languages?

I tried to integrate GraalVM. It works in the tests but I'm not able to embed it into Spring Boot.

@saig0 what is the issue you are hitting with graalvm?  I was using spring boot with the js context of graal in a previous prototype i did.

I embed the GraalVM into Spring Boot (https://github.com/zeebe-io/zeebe-script-worker/blob/graalvm/pom.xml#L79-L89).
When I run the Spring Boot JAR and open a context then I get a FileSystemNotFoundException (https://github.com/zeebe-io/zeebe-script-worker/blob/graalvm/src/main/java/io/zeebe/script/GraalEvaluator.java#L38).

@saig0  remove the dep
<dependency>
			<groupId>org.graalvm.js</groupId>
			<artifactId>js</artifactId>
			<version>${version.graalvm}</version>
</dependency>

as Js is included in GraalVM.
Then with SDK man ensure to have the VM installed with like sdk install java 1.0.0-rc9-graal
If you are using IDE (like intelliJ) make sure to update your project SDK to map to the graal vm installed.

@saig0 also you might want to consider using Vertx instead of spring boot.  Vertx has a pretty seamless integration with Graal and non-graal es6 support: https://github.com/reactiverse/es4x.
Would be really interesting to connect zeebe to the vertx eventbus so that vertx workers can pick up jobs.  This is extra interesting because of the auto-scalling features of Vertx and the automatic polyglot support. I think this fits really well with the zeebe scale

You could just make the graal supoort optional. Allowing someone to use the graalVM if they chose to, and this if they did they would be able to execute multiple languages supported within their Runtime installation. Could do something like a env var to indicate to use the graalVM context.  Or detect it.

Ok, I can make the support optional.

Let's leave it as it is for now.


Infinite loop for certain function definitions

Example:
export async function bar() {
  const contents = await fetch('https://www.google.com')
  return contents
}

as seen here: https://www.loom.com/share/0e8073d3b4f542a2a7b3da1a97e1ce89

Root cause: Was missing void analysis.


[T4A3][F10-B2] Shi Xiyue

Ready for review

@shixiyue  Overall nice work. Practice to give the lowest possible access modifier and to add comments


help-docs: Update button text for enabling Enter to send.

Updates help center documentation for enabling "Enter to send" for the default button text (Ctrl + Enter to send).

Also adds back ticks to all references to the Enter key, so that they are updated by adjust_mac_shortcuts for Mac keyboards.
Follow-up task noted in #22273.
Remaining concerns:

The article title in the left sidebar is not updated when a Mac keyboard is detected (see screenshot below). At the same time, I don't feel like it makes sense to change the formatting of the left sidebar to include code elements, which is how we generally find keyboard shortcut / key references in the help center (and other) documentation pages.

Screenshots and screen captures:

Non-mac documentation

Mac documentation

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Cool, thanks for working on this! A few thoughts:

I wonder if we can be more specific regarding whee to find the menu? E.g. "at the bottom of the compose box" -> "below the Send button in the compose box"?
I know it's not new in this PR, but I think the table at the bottom of this page is more confusing than helpful. Let's convert the "Note that..." part to a !!! tip, and drop the table altogether.
It seems better for the left sidebar to say "Return" for Mac users, but I don't think it's critical. I think even Mac users would be generally familiar with "Enter" being ~ equivalent to "Return".

@alya - Thanks for the quick review! I've updated for those changes, and agree that the tip instead of the table is better (see screenshot below). I don't know if we want to make an issue for the left sidebar or just leave it as is. But I also agree that it doesn't feel critical.
Updated screenshot of changes (non-Mac):

Nice! The updated screenshot looks good to me. @timabbott over to you.

I don't know if we want to make an issue for the left sidebar text for Mac users or just leave it as is.

I guess it would be good if you could file an issue; we won't mark it as high-priority.

One thing that strikes me when looking at this is that we might want to adjust the way code blocks are styled -- the red text default Pygments styling does not look great, which is why we override it in the web application.


Improve Github owner documentation

the picture does not provide a clear example of the value that should be provided for owner this leaves some ambiguity about the value needed either the full url or just the owner name.
for reference see this answer on stack overflow:
https://stackoverflow.com/questions/71950079/how-to-connect-azure-synapse-and-an-enterprise-git-repo-using-personal-access-to
I've attempted to leave add this information to make it easier to troubleshoot.

@nabhishek
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Fixed in https://github.com/MicrosoftDocs/azure-docs-pr/pull/288202. #please-close

@jonburchel the pr link 404's and it looks like the page hasn't been updated in production yet. Can you correct the link to the pr so I can see the changes before deleting my branch. thanks


Cannot type quote mark in input

If you try to type quote marks " into the first example on your site, it goes bananas.
Help me solve this! Thanks

@sergiodlopes
The solution lies somewhere in here:

@sergiodlopes
It also happens on this example:

@jesserosenfield Thanks for the heads up.
Indeed the problem lies there. If your values don't use HTML special characters, you can remove that 'escapeHtml' line, it should be OK.
Fix will be on v2.3.1, coming soon.
Cheers

Thanks!
On Tue, Feb 23, 2021 at 5:30 PM Sérgio Dinis Lopes<EMAIL_ADDRESS>wrote:

@jesserosenfield https://github.com/jesserosenfield Thanks for the
heads up.
Indeed the problem lies there. If your values don't use HTML special
characters, you can remove that 'escapeHtml' line, it should be OK.
Fix will be on v2.3.1, coming soon.
Cheers
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sergiodlopes/jquery-flexdatalist/issues/230#issuecomment-784559812,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADV5AMLEA7ZZXOLY2OCECLTAQT65ANCNFSM4YDDWKEA
.

--
Web: handiworknyc.com
Phone:<PHONE_NUMBER>

Any progress on this one?
"coming soon" was like 3 years ago by now …


provide example of multiply browsers/drivers usage per each test

need simple example howto start 2 browsers per test and manipulate them via different page objects in 2 sessions in parallel

done: https://github.com/qaprosoft/carina-demo/pull/130/files

During the testing please scan carina-demo from qaprosoft org and execute Web-Multiple-Browser-Demo-Test job.
2 drivers and video recordings should be displayed in reporting

Verified.


Error in CustomPainter docs: 'CustomPaint' instead of 'CustomPainter'

Hi, while going through the code documentation of CustomPainter, I found an error in which CustomPaint was used instead of CustomPainter https://github.com/flutter/flutter/blob/master/packages/flutter/lib/src/rendering/custom_paint.dart#L29
Error: line 29, lib/src/rendering/custom_paint.dart
/// To implement a custom painter, either subclass or implement this interface
/// to define your custom paint delegate. [CustomPaint] subclasses must
/// implement the [paint] and [shouldRepaint] methods, and may optionally also...

Should be:
/// To implement a custom painter, either subclass or implement this interface
/// to define your custom paint delegate. [CustomPainter] subclasses must
/// implement the [paint] and [shouldRepaint] methods, and may optionally also...

Pull request: https://github.com/flutter/flutter/pull/107836

#107836 has been merged.
Closing as fixed.


Missing cast  'Fetch Values Predicate' where clause as sqlalchemy.sql text break its functionality

Multiple versions in the code file missing the cast funcion of  Fetch Values Predicate' where clause as Sqlalchemy Text, result in raising error such as: sqlalchemy.exc.ArgumentError: Textual SQL expression "ds < datetime('now')" should be explicitly declared as text("ds < datetime('now')")
This line
https://github.com/apache/incubator-superset/blob/master/superset/connectors/sqla/models.py#L604
should be modified as
qry = qry.where(text(tp.process_template(self.fetch_values_predicate)))

You're right @vnnw , I believe some dialects are more sensitive to these omissions. What dialect are you using? We should probably clean these up in one go.

You're right @vnnw , I believe some dialects are more sensitive to these omissions. What dialect are you using? We should probably clean these up in one go.

I tried Sqlite and Clickhouse. After doing the modification mentioned above, all seems good now.

@vnnw would you mind opening a Pull Request for this?


[#186] Add scripts to setup project

close #186
What happened
Add make.sh for install script.
Insight

Update all name labels in the templates with the same format to support find and replace it by scripts, for example:

{{ProjectName}} or {PROJECT_NAME}
{{BundleIdProduction}}
{{BundleIdStaging}}
...

Add scripts to support questions:

What is your project name? (e.g HelloWorld)
What is your bundle id for production? (e.g co.nimblehq.templates)
What is your bundle id for staging? (e.g co.nimblehq.templates.staging)

Add scripts to find and replace all labels with the inputs
Add scripts to install tuist if needed
Add scripts to run tuist generate command
Add scripts to remove Tuist folder and Project.swift file to prevent another dev run the command tuist generate again.

Proof Of Work

@blyscuit Please help me to rebase this PR :D