Curriculum update needed on fundamentals-4.md

The Odin's file, fundamentals-4.md is updated. Please update the Kampus' file, checkout file here fundamentals-4.md
Latest commits:

fixed an unordered list and a extra emphasis with correct syntax (additions: 2, deletions: 2) on Feb 3 2024, 14:08 UTC
fixed 'emphasis' format (additions: 2, deletions: 2) on Feb 2 2024, 16:24 UTC
list items content updated to a single space before the content (additions: 1, deletions: 1) on Feb 2 2024, 14:37 UTC
switch to lazy numbering schema for ordered lists (additions: 2, deletions: 2) on Feb 2 2024, 14:36 UTC
asterisks are replaced by hypens in unordered lists (additions: 4, deletions: 4) on Feb 2 2024, 14:35 UTC

Dublicated issue


Basic fix for issue #273

This change simply forbids FnMuts from being used in js! macros, without implementing any Mut modifier or any other solution that would allow FnMuts to be used in the js! macro safely.
This change is NOT backwards compatible, but any fixes to #273 will have to break backwards compatibility in some way.
Most notably, MutationObserver::new and IEventTarget::add_event_listener accepted FnMut+'static closures as arguments. I changed these to accept only Fn+'static closures, as handling FnMuts correctly incurs unnecessary overhead for very little benefit (due to the 'static bound), as discussed in #273.
I'll wait on your opinion on whether you think a Mut modifier is worth it or not (and what should happen if illegal recursion is detected, a JavaScript exception or a Rust error) before trying to implement that.

Whoops I accidentally posted this to my own fork, not the original one. Ignore this.


Feature/patch

Adds the monkey_patch() functionality so np.ndarrays are auto-magically represented by lovely-numpy's representation.
Since NumPy's np.ndarray is written in C, you can't monkey-patch it the normal way. Instead we use the dedicated function np.set_string_function
set_string_function has a parameter called repr which determines which function will be set (__str__ or __repr__). This PR sets both, in order to align with the main lovely-tensors behavior.
Personally I think it should be considered to patch only __str__, so that __repr__ still gives a representation that is useful for example for reconstructing the array.

@xl0 I would love your opinion on the __str__ / __repr__ issue.
Also I'm new to open-source contribution so please let me know if I need to improve anything. Thanks for the opportunity!

Thank you, looks good to me!
For str/repr, I understand the semantical difference, but I think here, the UX is more important:
If we do print(array), str is called.
If we return an array from the cell, repr is called.
I think we want both to produce the same output.


Replace Home ui

Is your feature request related to a problem? Please describe.
We want to upgrade the home page UI to a new UI. The prototype of the new UI is given below. You have to use HTML,CSS, Bootstrap to make this type of Responsive UI.
Things to remember

Make Sure you connect all the backend features to the frontend part.
All the functionality which is working now should be working after upgradation.
Those features which are not introduced yet in backend those frontend components like button should not be linked but those components should be present.

Prototype

Hi @harsh-9in, I want to work on this new feature. Please assign this to me.

go ahead :+1:

go ahead

Yes

Hey, Can I work on this issue, Is this issue still open?

Hey, Can I work on this issue, Is this issue still open?

If this issue is still open, I'd like to work on it.

If this issue is still open, I'd like to work on it.


⚠ Bofrost.at has degraded performance

In fb7f3d1, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1095 ms

Resolved: Bofrost.at performance has improved in c877e53 after 17 minutes.


pdf.worker.js: Invalid XRef stream header for every PDF.

Hope this is the right place to ask this question (I don't know for sure, because it isn't actually an issue with pdf.js itself, but more with my implementation of it). If it isn't, I will be glad to move this question to the appropriate page.
Whenever I try to display a PDF using pdf.js I get the following error:
Error: Invalid XRef stream header

XRef_readXRef@[...]/pdf.js/build/generic/build/pdf.worker.js:23811:13
XRef_parse@[...]/pdf.js/build/generic/build/pdf.worker.js:23394:23
PDFDocument_setup@[...]/pdf.js/build/generic/build/pdf.worker.js:40294:7
PDFDocument_parse@[...]/pdf.js/build/generic/build/pdf.worker.js:40175:7
LocalPdfManager_ensure/<@[...]/pdf.js/build/generic/build/pdf.worker.js:40484:22
LocalPdfManager_ensure@[...]/pdf.js/build/generic/build/pdf.worker.js:40479:1
BasePdfManager_ensureDoc@[...]/pdf.js/build/generic/build/pdf.worker.js:40413:14
loadDocument/</<@[...]/pdf.js/build/generic/build/pdf.worker.js:40746:11

Warning: Indexing all PDF objects

InvalidPDFException: Invalid PDF structure

Where I have replaced the path leading to the pdf.js directory with [...], and which is prepended by a whole list of warnings, for just about any character, like these:
Warning: Ignoring invalid character "114" in hex string
Warning: Ignoring invalid character "115" in hex string
Warning: Ignoring invalid character "45" in hex string

Now, this looks like I am trying to display a corrupt PDF (which was my first thought). However, no matter what example PDF I plug in, it always results in exactly the same error, including the same number and ordering of Invalid Character Warnings. This strikes me as very peculiar, because I would not suspect that two PDFs would have characters in the exact same ordering.
This led me to believe that it might be loading a corrupt PDF from the cache, but after clearing it the problem persisted. I also updated my PDF.js plugin to the latest version, and again to the most recent release. This also did not result in any improvements.
To determine if this really occurred with every PDF, I eventually use this piece of Javascript code, loading the (certainly not corrupt) example PDF of this github page:
var url = encodeURIComponent('compressed.tracemonkey-pldi-09.pdf');
PDFJS.getDocument('http://mozilla.github.io/pdf.js/web/viewer.html?file=' + url).then(function(pdfFile) {
...
});

Note that this url var is declared separately because that is how I would normally load the value of the PDF I want to obtain.
I load these scripts:
<script type="text/javascript" src="{% static 'website/search/pdf.js/build/generic/build/pdf.js' %}"></script>
<script type="text/javascript" src="{% static 'website/search/pdf.js/build/generic/web/compatibility.js' %}"></script>

Where these files are the ones generated by running
node make generic

after following the getting started instructions from the github page.
Is there anybody here that can help me detect this problem? Did I miss something obvious? Do you require additional information? And again, if this isn't the correct place to ask this question, please refer me to the location where it should be.
Thanks in advance.

I think the problem is this line: PDFJS.getDocument('http://mozilla.github.io/pdf.js/web/viewer.html?file=' + url). You should be feeding the file itself (PDF content) to the getDocument call, whereas you are now feeding it HTML content because of the web page. Most likely PDFJS.getDocument(url) will be better. If not, please setup a demo page somewhere (own server, JSBin, JSFiddle, et cetera) so we can try to debug the issue.

Thank you very much, your solution has indeed fixed my problem. I don't know why I was feeding it the HTML content of that page, it must have been a remnant from an example I have used some time ago. Thanks for the rapid response; is there any way I should tag your answer as correct / up vote something? If not, I will close the thread afterwards.

You're welcome, I'm glad you can use PDF.js now! I'll close the issue for you, as that indicates that the issue is solved. If you have more questions, feel free to contact us on IRC or the mailing list.


8/25/2020 Publish

Docs Build status updates of commit d008e7d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

README.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Migrate zzmaps to Mlang

zzmaps still uses the legacy material system. Low priority.
Postponed from #266

zzmaps is deprecated. I will revive it from git history if and when necessary.


⚠ Avatar API Endpoint has degraded performance

In 4dbb280, Avatar API Endpoint (https://avatar.roblox.com/v1/avatar-rules) experienced degraded performance:

HTTP code: 200
Response time: 1820 ms

Resolved: Avatar API Endpoint performance has improved in 8e58bf7.


Pick overlapping zones closest to mouse

Summary of the new feature/enhancement
Overlapping zone selection calculated by distance of pointer to center point/area of zone.
As implemented in https://github.com/microsoft/PowerToys/pull/438 (a big improvement over previous functionality) when selecting overlapping zones while moving a window, it selects the smallest zone so that the larger zone can be selected in an area that doesn't overlap. This could be further improved as it doesn't work well for scenarios where there are 3+ overlapping zones, with the largest covering multiple smaller ones (only the smallest and largest can be selected).
Proposed technical implementation details (optional)
https://github.com/microsoft/PowerToys/blob/master/src/modules/fancyzones/lib/ZoneSet.cpp#L78-L112
Instead of returning smallestKnownZone, return closestKnownZone. If multiple zone centers are of equal distance, default to smallestKnownZone.
To implement, the center point/area of each zone would need to be determined, and a distance from the mouse pointer would then be calculated.

Beside the scenario described here, there is also the scenario described by https://github.com/microsoft/PowerToys/issues/475
There might be other scenarios were the current algorithm fails to activate an overlapped zone.
To make a proper fix, we should come up with an algorithm robust enough to always guarantee a way to activate any zone.

After further investigation, I can't find a zone layout different from the one described by https://github.com/microsoft/PowerToys/issues/475 that would make a zone impossible to activate.
@eastokes can you please post a screenshot of the troubled layout you described? Thank you.

@enricogior This is issue #475, is there another you're looking at? The only scenario in conflict I can think of is the 3+ overlapping zones, with the largest covering multiple smaller ones (only the smallest and largest can be selected).
Thanks for looking into this.

Sorry, I meant https://github.com/microsoft/PowerToys/issues/819

When dragging a window with a mouse, we hold the window by its caption bar. We should snap to the zone which top border is the closest, not the zone center.

@crutkas
since this one is related to https://github.com/microsoft/PowerToys/issues/819, let's also move this one to the next milestone.


Detached Instance Error

Even with expire_on_commit=False i'm with a detached instance error with sqlalchemy_oso this is really anoying, i have need to use expunge_all to be able to bypass the error.

Hi Matheus, could you provide details on what steps to take to reproduce this error?


[LOCALIZATION]:

Request a language
Chinese
Additional context
No response

Traditional?

It's possible now to join as translator for Chinese (traditional) on crowdin.


Signature form correct for non-std SIGHASH values

Fixes edge case where SIGHASH_ALL = 0 instead of 1

Newer BIPs leave open the door for non-standard sighash values
Malformed Txs with sighash = 0 (sighash_all) exist, such as this test vector:
["The following is c99c49da4c38af669dea436d3e73780dfdb6c1ecf9958baa52960e8baee30e73"],
["It is of interest because it contains a 0-sequence as well as a signature of SIGHASH type 0 (which is not a real type)"],
[[["406b2b06bcd34d3c8733e6b79f7a394c8a431fbf4ff5ac705c93f4076bb77602", 0, "DUP HASH160 0x14 0xdc44b1164188067c3a32d4780f5996fa14a4f2d9 EQUALVERIFY CHECKSIG"]],
"01000000010276b76b07f4935c70acf54fbf1f438a4c397a9fb7e633873c4dd3bc062b6b40000000008c493046022100d23459d03ed7e9511a47d13292d3430a04627de6235b6e51a40f9cd386f2abe3022100e7d25b080f0bb8d8d5f878bba7d54ad2fda650ea8d158a33ee3cbd11768191fd004104b0e2c879e4daf7b9ab68350228c159766676a14f5815084ba166432aab46198d4cca98fa3e9981d0a90b2effc514b76279476550ba3663fdcaff94c38420e9d5000000000100093d00000000001976a9149a7b0f3b80c6baaeedce0a0842553800f832ba1f88ac00000000", true]


Allow cargo +rust-version build|test|...

Problem
Now that rust-version is stable it makes sense to have a CI task/job that asserts this commitment. In that case, one would need to set up a CI config that runs tests on the selected Rust version. Usually, it means that the specific version will be specified twice

rust-version in Cargo.toml
Somewhere in CI configuration.

And they need to be in sync to make sense. This is where extra work is required and that may be avoided.
Proposed Solution
I suggest teaching cargo to understand the +rust-version parameter, alongside the +stable, +nightly, and friends. When specified it will cause cargo to use the Rust toolchain referenced in the rust-version parameter. (And installing it on demand as it does today when used with other +toolchain parameters).
If used for crates that lack rust-version parameter it will fall back to otherwise default toolchain configured for this crate.
As a result, the potential disagreement between CI and rust-version will be avoided completely, better usability, less time wasted, etc
Notes
No response

I do not have permissions to transfer to rustup. @imp can you open an issue there?

Done


fix: windows hard coded well-known group name

Issue #, if available:
Description of changes:
WindowsPlatform.java: Lookup Windows group name "Everyone" and "Administrators" by SID instead of the hard-coded English string.
Why is this change necessary:
Non-English Windows versions can have localized name for groups such as "Everyone" and "Administrators". On those Windows versions, nucleus won't be able to install or function.
How was this change tested:
Manual test with German language Windows EC2 (AMI: Windows_Server-2019-German-Full-Base-2021.09.15)
Without this fix the test will fail:
[ERROR] Failures:
[ERROR]   WindowsPlatformTest.GIVEN_a_well_known_group_sid_WHEN_lookupGroupByIdentifier_THEN_succeed:292
Expected: "Everyone"
     but: was "Jeder"

Any additional information or context required to review the change:
To re-produce/test this, seems a non-English windows installation is required. If the system is English based, changing display language or system locale won't change the group names to localized ones.
Checklist:

[ ] Updated the README if applicable
[x] Updated or added new unit tests
[ ] Updated or added new integration tests
[ ] Updated or added new end-to-end tests
[ ] If your code makes a remote network call, it was tested with a proxy
[x] You confirm that the change is backwards compatible

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

Hi,
Would you mind sharing the .jar file so as it could be downloaded on the AWS console?
Thanks, regards.
Daniel.

Hi,
Would you mind sharing the .jar file so as it could be downloaded on the AWS console?
Thanks, regards. Daniel.

We will release a version with this fix soon. Meanwhile, you may cherry-pick this change and build the jar with maven package command.

Hi,
Would you mind sharing the .jar file so as it could be downloaded on the AWS console?
Thanks, regards. Daniel.

We will release a version with this fix soon. Meanwhile, you may cherry-pick this change and build the jar with maven package command.

Hi tilo-chen,
I have built the source code and it appears to be working right now :)
Thanks,
Regards.


Form in swipeable tabs

Has anyone tried putting some materialize form elements into a tabs-component initialized with .tabs({swipeable:true})?
I've tried so and it bugs out completely and it is not useable at all

@bert-w General questions should be asked in the Gitter channel. Please read the issue template when you create an issue. It would be good to have a codepen.
You might have to call Materialize.updateTextFields(); in combination with onShow() of the tab component. But the change to make this work with swipeable is not yet available in a release but in the master branch, see https://github.com/Dogfalo/materialize/commit/8129f11bea975c46af391a28614f490d4fa6024e
Please prepare a codepen and post your question in the Gitter channel.


feat: Add support for bgp dynamic neighbours subcommand for metal gateway

Fixes: https://github.com/equinix/metal-cli/issues/413

Can you add tests for this subcommand?

@ctreatma I am working on the tests but should we keep small PRs and raise tests in the next one? It'll be easier to review as well. And anyway this is a new functionality which is not release

@ctreatma I am working on the tests but should we keep small PRs and raise tests in the next one? It'll be easier to review as well. And anyway this is a new functionality which is not release

Tests build the reviewer's confidence that the changes actually work the way they are supposed to.  Doing them in a separate PR only serves to delay finishing the code.

I enabled VRF over Shared Connections, VRF Static Routers, and BGP Dynamic Neighbors for the testing org. We should see better progress in the E2E.

strings.Contains(err.Error(), "Not Found")

Yes after enabling FFs, tests started passing for BGP
https://github.com/equinix/metal-cli/actions/runs/7700595014/job/20986048893?pr=433#step:5:111

We're having issues getting the device create tests to pass, but I firmly believe that's unrelated to this PR and we can improve those in a separate PR. Going to merge now.

=== RUN   TestBgpDynamicNeighbors_Create
=== RUN   TestBgpDynamicNeighbors_Create/create_bgp_dynamic_neighbor
--- PASS: TestBgpDynamicNeighbors_Create (5.21s)
    --- PASS: TestBgpDynamicNeighbors_Create/create_bgp_dynamic_neighbor (0.45s)
=== RUN   TestBgpDynamicNeighbors_Delete
=== RUN   TestBgpDynamicNeighbors_Delete/delete_bgpDynamicNeighbor_by_ID
--- PASS: TestBgpDynamicNeighbors_Delete (3.82s)
    --- PASS: TestBgpDynamicNeighbors_Delete/delete_bgpDynamicNeighbor_by_ID (0.36s)
=== RUN   TestBgpDynamicNeighbors_Get
=== RUN   TestBgpDynamicNeighbors_Get/get_bgpDynamicNeighbor_by_ID
--- PASS: TestBgpDynamicNeighbors_Get (3.22s)
    --- PASS: TestBgpDynamicNeighbors_Get/get_bgpDynamicNeighbor_by_ID (0.19s)
=== RUN   TestBgpDynamicNeighbors_List
=== RUN   TestBgpDynamicNeighbors_List/list_bgpDynamicNeighbor_by_ID
--- PASS: TestBgpDynamicNeighbors_List (3.61s)
    --- PASS: TestBgpDynamicNeighbors_List/list_bgpDynamicNeighbor_by_ID (0.19s)

All related tests are passing in this test run @ctreatma can you please approve this PR


Move all issues across from the parent fork

https://github.com/adafruit/jupyter_micropython_kernel/issues/

copied the streaming issue over


ARROW-10988: [C++] Require CMake 3.5 or later

Because Ubuntu 16.04 ships CMake 3.5.1.

@github-actions crossbow submit -g nightly

+1


Add '.venv/bin' to PATH before excute every bash scrips

So that you could make sure you are always using a virtual envirnoment

done


Duration of the video

Hello! I'm having a problem capturing video with the camera I gave the duration of 15 minutes and I can only record only 21 seconds
MediaStore.EXTRA_DURATION_LIMIT, 900
my device is an XPeria Android 4.4
Would I have to configure something else?
`
private void takeVideo() {
    cameraPicker = new CameraVideoPicker(this);
    cameraPicker.shouldGenerateMetadata(true);
    //cameraPicker.setCacheLocation(CacheLocation.INTERNAL_APP_DIR);
    cameraPicker.setCacheLocation(CacheLocation.EXTERNAL_STORAGE_APP_DIR);
    cameraPicker.shouldGeneratePreviewImages(true);
    Bundle extras = new Bundle();
    // For capturing Low quality videos; Default is 1: HIGH
    extras.putInt(MediaStore.EXTRA_VIDEO_QUALITY, 0);
    // Set the duration of the video
    extras.putInt(MediaStore.EXTRA_DURATION_LIMIT, 900);
    cameraPicker.setExtras(extras);
    cameraPicker.setVideoPickerCallback(this);
    pickerPath = cameraPicker.pickVideo();

}

`
I'm sure it's not lib's problem anymore how to fix it?
Thanks for your comments
Agradeço

Also, EXTRA_DURATION_LIMIT is not working for me on device One Plus 3T with OS version 8.0
It working with other devices up to OS 7.0.
Any solution for this issue?


Add bug handling for invalid prefixes

Currently, the implementation is to ignore invalid prefixes. However, a better implementation is to handle invalid parameters as a bug to notify users, in case they made a typo. This can be implemented in ArgumentMultimap and ArgumentTokenizer.

arameters.

Test Case to try: view f/Engineering d/Engineering


This doesn't work

There is no vue-devtools tab.

me too

Please read the readme carefully and make sure you are

Using non-minified build of Vue.js;
If not serving the page over http, you need to check "allow accesss to file system" for the extension.

Same here. Installed from the Chrome Web Store and I have no tab in dev tools - but I do have a button in my browser

Please read the readme carefully and make sure you've checked the following:

[ ] Using a non-minified version of Vue.
[ ] Serving the page over HTTP
[ ] If the page is opened via file:// protocol, you need to check "Allow access to file URLs" for this extension in Chrome's extension management panel.

If you've done all of the above and the devtool is still not showing up, please provide more information:

The version of Vue you are using.
The version of Chrome you are using.
The OS you are using.

Finally:

The tab only shows up when Vue.js is detected on the page.
The button on the top right does nothing. Chrome just displays an empty icon for every extension now. You can just hide it.

I have no control over your first point because I installed it from Chrome Web Store . The other points are true for me.

@martin-wiseweb the first point is referring to the Vue.js you are using in your application, not the devtools.

Script tag: src="https://cdnjs.cloudflare.com/ajax/libs/vue/1.0.21/vue.min.js"
Chromium browser: Version 49.0.2623.108 Built on Ubuntu 14.04, running on LinuxMint 17.3 (64-bit)
"Allow access to file URLs" is checked, though I run Apache locally.

I reinstalled extension and still nothing, no tab shown.

Are you using self-built Chromium? Do you have the same issue if using the stable-channel Chrome/Chrome Canary?

I am not using the minified version

@yyx990803 I've just tried with chrome (Version 50.0.2661.94 - 64-bit) and I managed to get it working, sort of. It acts kind of funny. I have to close and open (or hide/show) dev tools, it somehow gets stucked, hard to explain... I think that something goes wrong if I navigate from non-vue page to vue-page...
I will try reinstalling chrome and chromium, and also enabling extensions one by one to see what's going on.

@ergonomicus You are not the only one. When I open a page with VUE on it and I don't have the devtools open and active it doesn't always load at all and then when it does load I can't click on anything. If I do click on something, I have to refresh the page in order for it to refresh the devtools panel. I have the most recent version of Chrome and I just installed 1.0.24 of Vue. The Javascript that is compiled from gulp is not minified.

I know this is affecting a lot of people, and it was affecting me as well on the unminified version of Vue. By default, Chrome doesn't show the http:// protocol. I'm developping in a local virtual host served over a host file, say local.dev. Manually typing http:// before the URL got the vue devtools to appear (still chrome doesn't show http://, but vue devtools worked..)

Quit Chrome and reopen, and it works fine for me.
Chrome version 51.0.2704.84 (64-bit), Vue.js version 1.0.24
It's odd, 尤老师.

Sometimes you need to re-open Chrome DevTools.
Also, if vue loaded inside <iframe></iframe> (jsfidde, jsbin, codepen.io, etc) will not work.

It works fine for me by restarting chrome and setting Vue.config.devtools=true.
my version is v1.0.22.

Does anyone try to use it for developing chrome extensions?
Due to some requirements @yyx990803 mentioned in his comment, it doesn't work.
I was wondering is it because it's working with chrome-extension:// protocol.
If we could have it work that would be amazing. I'm not able to enable it when I'm developing chrome extensions that is using Vue JS as a library.
Tev.

@tevfik6: I'm in the same situation so I looked around a bit and found that this plugin is actually specifying the protocol it allows to serve over in the manifest file (shells/chrome/manifest.json:22). I tried to force to load it over chrome-extension:// protocol and I did a quick search about this and found this documentation from Google:
https://developer.chrome.com/extensions/match_patterns
This is actually saying a chrome extension is not allowed to load on a chrome-extension:// protocol.
It would have been cool to have this for chrome development but it's not gonna happen.


round down in chap02.ipynb

Concerning the running simulations section, int() truncates and does not necessarily round down.
Kind of a minor nitpick, but feedback is feedback.

Thanks!


Currently, a module cannot receive cloud-to-device messages

This let me a little bit confused since on the service sdk a sendAsync method exists that accepts as parameters, deviceId, moduleId, and the message;
https://docs.microsoft.com/en-us/dotnet/api/microsoft.azure.devices.serviceclient.sendasync?view=azure-dotnet#Microsoft_Azure_Devices_ServiceClient_SendAsync_System_String_System_String_Microsoft_Azure_Devices_Message_

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

ID: 6c7aa1ca-7807-7b0e-6ddb-887106288aa8
Version Independent ID: c20a9ac2-63a3-fe68-ba5b-038af4fe3c90
Content: Develop modules for Azure IoT Edge
Content Source: articles/iot-edge/module-development.md
Service: iot-edge
GitHub Login: @kgremban
Microsoft Alias: kgremban

@rcoccia Thank you for reporting this issue! We will investigate and make any necessary changes.

@kgremban got any thoughts on this one?

@rcoccia and @mike-urnun-msft I've reached out to the product team to ask them about this.

@rcoccia Here's the answer that I got:
Cloud-to-module messages are not supported in Azure IoT Edge. IoT Hub however seems to have partial support for this. In my test, I was able to receive a cloud-to-module message over MQTT but not over AMQP.
Until it's officially in preview or supported in IoT Edge, I won't be documenting this capability in our docs. But good sleuthing on your part to find this partially available functionality. You can go to https://feedback.azure.com/forums/907045-azure-iot-edge to request product features or upvote other requests.

@rcoccia just checking if the above answered your question. Pls let us know if we can close this issue.

@rcoccia Have we answered your question, or are you looking for more information?

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Hard to interpret error when deploying application

Describe the bug
I was following the guide found on "Deploy Spring microservices to Azure ->  Build a Spring Boot microservice". It's close to impossible to understand what went wrong with the error message under.
Command Name
az spring-cloud app deploy Extension Name: spring-cloud. Version: 2.12.2.
Errors:
The command failed with an unexpected error. Here is the traceback:
Expecting value: line 1 column 1 (char 0)
Traceback (most recent call last):
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 231, in invoke
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 658, in execute
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 721, in _run_jobs_serially
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 713, in _run_job
  File "C:\Users\marku\.azure\cliextensions\spring-cloud\azext_spring_cloud\_utils.py", line 251, in handle_asc_exception
    response_dict = json.loads(ex.response.internal_response.text)
  File "json\__init__.py", line 357, in loads
  File "json\decoder.py", line 337, in decode
  File "json\decoder.py", line 355, in raw_decode
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

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

Follow the guide on https://docs.microsoft.com/en-us/learn/modules/azure-spring-cloud-workshop/4-build-spring-boot-microservice
az spring-cloud app deploy --name {} --service {} --resource-group {} --jar-path {}

Expected Behavior
To deploy application
Environment Summary
Windows-10-10.0.19041-SP0
Python 3.8.9
Installer: MSI

azure-cli 2.31.0 *

Extensions:
spring-cloud 2.12.2

Additional Context

route to service team

@MarkusRa1 There was a bug introduced in 2.12.2. You can upgrade the extension spring-cloud to the latest version by running the command az extension update -n spring-cloud
Sorry for the inconvenience.

It works, thanks!

Closing the thread


Detection of duplicate enum literals in dictionary keys (F601)

multi-value-repeated-key-literal (F601) only works with primitive literals like keys and strings. In our codebase we use enums extensively for increased type safety over strings, and that includes mappings of enum values to other values. I'd love ruff to find issues in those too.
This triggers F601:
string_keys = {"a": 1, "a": 2}

This doesn't trigger but should:
from enum import Enum
class E(Enum):
    A = "a"

enum_keys = {E.A: 1, E.A: 2}

(ruff 0.6.9)
Thanks for the awesome tool!

That makes sense but isn't something that ruff can support today without proper multifile analysis (to support enums imported from other files) and type inference (to get the types of enum constants).

Would it make sense to make a separate rule that checks for identical expressions in keys? It can have false positives if the expression has side effects and changes value on every evaluation, but one can argue that using those as "keys" in a dictionary is very confusing and obscures the code intent.

Good point. We could extend the rule to support identical attribute chains.


Next-intl translation are not working

Description
On my login page the translation of navbar is not working after refresh it
when i navigate to different page and then come on the login it works
but when i refresh the page it stops working for some reason i don't understand
I get hydration error on the login page as well
the thing is when removed the header and check the login page it did not had any hydration error as well
so issue is in the header component but header works completely fine on other page and translation works as great as well
it just than in the login page it stops
Verifications

[X] I've verified that the problem I'm experiencing isn't covered in the docs.
[X] I've searched for similar, existing issues on GitHub and Stack Overflow.
[X] I've compared my app to a working example to look for differences.

Mandatory reproduction URL
http://localhost:3001/login
Reproduction description
Steps to reproduce:

Open reproduction
Click on …
See error: …

i cant give the website as it is confidential
Expected behaviour
I want the header to be translated on every page

Sorry, I don't know either and also can't have a look since there's no reproduction.
I'll move this to a discussion since it looks like a usage question.


NHK sports url not supported

Checklist

[x] I'm reporting a new site support request
[x] I've verified that I'm running youtube-dl version 2021.06.06
[x] I've checked that all provided URLs are alive and playable in a browser
[ ] I've checked that none of provided URLs violate any copyrights
[x] I've searched the bugtracker for similar site support requests including closed ones

Example URLs

Single video: https://sports.nhk.or.jp/olympic/highlights/content/dadd1ba3-97c9-4a56-98e2-3d5a27657914/
Single video: https://sports.nhk.or.jp/olympic/highlights/content/1d7d133d-ce2c-4892-b4ab-bdaf3ab4db79/

Description

ERROR: Unsupported URL: https://sports.nhk.or.jp/olympic/highlights/content/1d7d133d-ce2c-4892-b4ab-bdaf3ab4db79/

They are DRM protected.

Issue should be closed, URL is dead


Disallow the self/Self keyword where it’s not allowed in types

We weren’t matching the C++ parser’s behavior here. The self keyword is not allowed as a type name. Self in a nested type refers to a type named Self instead of the Self keyword.

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test Windows

@swift-ci Please test

@swift-ci Please test Windows


Make a discord server

I realized you are struggling with making the mods, if you don't have ideas try making a discord server, people would love to suggest their ideas in there

I am currently using the Warp Modding server for this purpose it was previously the HexMC discord however I plan it to be more multipurpsose.
Late response I know but if you want to join it can be done so here: https://discord.gg/S6uH5ykDQy


device tree: generate pinmux

Generate board pinmux from device tree file.
Aim is to use fully pinmux information from dts and get rid of pinmux.c

Part of #2288

Closing this in favor of #22748


Implement RAG for CSP LLMs or Local LLaMa LLMs

see also https://github.com/ObrienlabsDev/blog/issues/47
see https://github.com/ObrienlabsDev/rag/issues/4

follow
https://python.langchain.com/v0.2/docs/tutorials/rag/
pip install langchain langchain_community langchain_chroma

[notice] A new release of pip is available: 23.0.1 -> 24.2
[notice] To update, run: python.exe -m pip install --upgrade pip

sign up to langsmith
https://smith.langchain.com/o/71626d73-7ad4-57ab-8c7d-82cc7d004740/
pip install -qU langchain-google-vertexai

hitting rate limit
https://platform.openai.com/settings/organization/limits

pt-4o-mini | 60,000 TPM | 3 RPM200 RPD | 200,000 TPD
-- | -- | -- | --

```
openai.RateLimitError: Error code: 429 - {'error': {'message': 'You exceeded your current quota, please check your plan and billing details. For more information on this error, read the docs: https://platform.openai.com/docs/guides/error-codes/api-errors.', 'type': 'insufficient_quota', 'param': None, 'code': 'insufficient_quota'}}

working with RAG prompt to OpenAI

# from https://python.langchain.com/v0.2/docs/tutorials/rag/
import getpass
import os
import bs4

from langchain_openai import ChatOpenAI
from langchain import hub
from langchain_chroma import Chroma
from langchain_community.document_loaders import WebBaseLoader
from langchain_core.output_parsers import StrOutputParser
from langchain_core.runnables import RunnablePassthrough
from langchain_openai import OpenAIEmbeddings
from langchain_text_splitters import RecursiveCharacterTextSplitter

os.environ["OPENAI_API_KEY"] = "sk-..A"
#getpass.getpass()

llm = ChatOpenAI(model="gpt-4o-mini")

os.environ["LANGCHAIN_TRACING_V2"] = "true"
os.environ["LANGCHAIN_API_KEY"] = "lsv...9"
#getpass.getpass()

# Load, chunk and index the contents of the blog.
loader = WebBaseLoader(
    web_paths=("https://lilianweng.github.io/posts/2023-06-23-agent/",),
    bs_kwargs=dict(
        parse_only=bs4.SoupStrainer(
            class_=("post-content", "post-title", "post-header")
        )
    ),
)
docs = loader.load()

print(f"docs content size: %s" % (len(docs[0].page_content)))
print(docs[0].page_content[:500])

text_splitter = RecursiveCharacterTextSplitter(
   chunk_size=1000, chunk_overlap=200) #  add_start_index=True
splits = text_splitter.split_documents(docs)
print(f"splits: %s" % (len(splits)))
print(f"page_content: %s" % (len(splits[0].page_content)))
print(f"metadata: %s" % (len(splits[10].metadata)))

vectorstore = Chroma.from_documents(documents=splits, embedding=OpenAIEmbeddings())

def format_docs(docs):
    return "\n\n".join(doc.page_content for doc in docs)

  # Retrieve and generate using the relevant snippets of the blog.
retriever = vectorstore.as_retriever() # search_type="similarity", search_kwargs={"k": 6}

print ("test")
#def skip():

prompt = hub.pull("rlm/rag-prompt")
rag_chain = (
  {"context": retriever | format_docs, "question": RunnablePassthrough()}
   | prompt
   | llm
   | StrOutputParser()
  )

retrieved = rag_chain.invoke("What is Task Decomposition?")
print(f"retrieved: %s" % (len(retrieved)))
print(f"retrieved content: %s" % (retrieved))#[0].page_content))

michael@13900d MINGW64 /c/wse_github/obrienlabsdev/rag/src/rag (main)
$ python app.py
USER_AGENT environment variable not set, consider setting it to identify your requests.
docs content size: 43131

      LLM Powered Autonomous Agents

Date: June 23, 2023  |  Estimated Reading Time: 31 min  |  Author: Lilian Weng

Building agents with LLM (large language model) as its core controller is a cool concept. Several proof-of-concepts demos, such as AutoGPT, GPT-Engineer and BabyAGI, serve as inspiring examples. The potentiality of LLM extends beyond generating well-written copies, stories, essays and programs; it can be framed as a powerful general problem solver.
Agent System Overview#
In
splits: 66
page_content: 969
metadata: 1
test
C:\opt\Python310\lib\site-packages\langsmith\client.py:5431: LangChainBetaWarning: The function `loads` is in beta. It is actively being worked on, so the API may change.
  prompt = loads(json.dumps(prompt_object.manifest))
retrieved: 343
retrieved content: Task Decomposition is the process of breaking down complex tasks into smaller, manageable steps. This can be achieved through various methods, including prompting models to think step by step or providing task-specific instructions. It enhances performance by allowing easier handling of complicated tasks and clarifying the reasoning process.

michaelobrien@mbp7 rag % python app.py
USER_AGENT environment variable not set, consider setting it to identify your requests.
docs content size: 43131

      LLM Powered Autonomous Agents

Date: June 23, 2023  |  Estimated Reading Time: 31 min  |  Author: Lilian Weng

Building agents with LLM (large language model) as its core controller is a cool concept. Several proof-of-concepts demos, such as AutoGPT, GPT-Engineer and BabyAGI, serve as inspiring examples. The potentiality of LLM extends beyond generating well-written copies, stories, essays and programs; it can be framed as a powerful general problem solver.
Agent System Overview#
In
splits: 66
page_content: 969
metadata: 1
INFO:chromadb.telemetry.product.posthog:Anonymized telemetry enabled. See                     https://docs.trychroma.com/telemetry for more information.
INFO:httpx:HTTP Request: POST https://api.openai.com/v1/embeddings "HTTP/1.1 200 OK"
retriever: tags=['Chroma', 'OpenAIEmbeddings'] vectorstore=<langchain_chroma.vectorstores.Chroma object at 0x1226373d0> search_kwargs={'k': 6}
INFO:httpx:HTTP Request: POST https://api.openai.com/v1/embeddings "HTTP/1.1 200 OK"
vectorstore retrieved: 6
vectorstore retrieved content: Tree of Thoughts (Yao et al. 2023) extends CoT by exploring multiple reasoning possibilities at each step. It first decomposes the problem into multiple thought steps and generates multiple thoughts per step, creating a tree structure. The search process can be BFS (breadth-first search) or DFS (depth-first search) with each state evaluated by a classifier (via a prompt) or majority vote.
Task decomposition can be done (1) by LLM with simple prompting like "Steps for XYZ.\n1.", "What are the subgoals for achieving XYZ?", (2) by using task-specific instructions; e.g. "Write a story outline." for writing a novel, or (3) with human inputs.
/Users/michaelobrien/Library/Python/3.9/lib/python/site-packages/langsmith/client.py:5431: LangChainBetaWarning: The function `loads` is in beta. It is actively being worked on, so the API may change.
  prompt = loads(json.dumps(prompt_object.manifest))
example_messages: You are an assistant for question-answering tasks. Use the following pieces of retrieved context to answer the question. If you don't know the answer, just say that you don't know. Use three sentences maximum and keep the answer concise.
Question: filler question
Context: filler context
Answer:
INFO:httpx:HTTP Request: POST https://api.openai.com/v1/embeddings "HTTP/1.1 200 OK"
INFO:httpx:HTTP Request: POST https://api.openai.com/v1/chat/completions "HTTP/1.1 200 OK"
rag_chain retrieved: 396
rag_chain retrieved content: Task decomposition is the process of breaking down a complex task into smaller, more manageable steps. This can be achieved through techniques like Chain of Thought (CoT) prompting, which encourages step-by-step reasoning, or by using task-specific instructions and human inputs. The goal is to simplify the execution of difficult tasks and enhance understanding of the model's reasoning process.

refactor rag_chain
# from https://python.langchain.com/v0.2/docs/tutorials/rag/
import getpass
import os
import bs4

from langchain_openai import ChatOpenAI
from langchain import hub
from langchain_chroma import Chroma
from langchain_community.document_loaders import WebBaseLoader
from langchain_core.output_parsers import StrOutputParser
from langchain_core.runnables import RunnablePassthrough
from langchain_openai import OpenAIEmbeddings
from langchain_text_splitters import RecursiveCharacterTextSplitter
import logging

logging.basicConfig(level=logging.INFO)
# Configure logging
logging.basicConfig(level=logging.INFO)

def set_environment_variables():
#    os.environ["OPENAI_API_KEY"] = ""
#    os.environ["LANGCHAIN_API_KEY"] = ""

def initialize_llm():
    return ChatOpenAI(model="gpt-4o-mini")

def load_documents():
    loader = WebBaseLoader(
        web_paths=("https://lilianweng.github.io/posts/2023-06-23-agent/",),
        bs_kwargs=dict(
            parse_only=bs4.SoupStrainer(
                class_=("post-content", "post-title", "post-header")
            )
        ),
    )
    return loader.load()

def split_documents(docs):
    text_splitter = RecursiveCharacterTextSplitter(
        chunk_size=1000, chunk_overlap=200
    )
    return text_splitter.split_documents(docs)

def create_vectorstore(splits):
    return Chroma.from_documents(documents=splits, embedding=OpenAIEmbeddings())

def retrieve_documents(vectorstore, query, k=6):
    retriever = vectorstore.as_retriever(search_type="similarity", search_kwargs={"k": k})
    return retriever.invoke(query)

def format_docs(docs):
    return "\n\n".join(doc.page_content for doc in docs)

## refactor out rag_chain setup to allow for a non-local retriever from the vectorstore
def setup_rag_chain(retriever, prompt, llm):
    """
    Sets up the RAG (Retrieval-Augmented Generation) chain.

    Parameters:
    - retriever: The retriever object for document retrieval.
    - prompt: The prompt object for generating responses.
    - llm: The language model object.

    Returns:
    - The configured RAG chain.
    """
    return (
        {"context": retriever | format_docs, "question": RunnablePassthrough()}
        | prompt
        | llm
        | StrOutputParser()
    )

def main():
    set_environment_variables()
    llm = initialize_llm()

    try:
        docs = load_documents()
        logging.info(f"Docs content size: {len(docs[0].page_content)}")
        logging.info(docs[0].page_content[:500])

        splits = split_documents(docs)
        logging.info(f"Splits: {len(splits)}")
        logging.info(f"Page content size: {len(splits[0].page_content)}")
        logging.info(f"Metadata size: {len(splits[10].metadata)}")

        vectorstore = create_vectorstore(splits)
        # retrieved_docs are not used
        retrieved_docs = retrieve_documents(vectorstore, "What are the approaches to Task Decomposition?")
        logging.info(f"Vectorstore retrieved: {len(retrieved_docs)}")

        prompt = hub.pull("rlm/rag-prompt")
        example_messages = prompt.invoke(
            {"context": "filler context", "question": "filler question"}
        ).to_messages()
        logging.info(f"Example messages: {example_messages[0].content}")

        # unroll retriever
        retriever = vectorstore.as_retriever(search_type="similarity", search_kwargs={"k": 6})
        rag_chain = setup_rag_chain(retriever, prompt, llm)

        # Uncomment to use the RAG chain
        # for chunk in rag_chain.stream("What is Task Decomposition?"):
        #     logging.info(chunk)
        retrieved = rag_chain.invoke("What is Task Decomposition?")
        logging.info(f"rag_chain retrieved: {len(retrieved)}")
        logging.info(f"rag_chain retrieved content: {retrieved}")

    except Exception as e:
        logging.error(f"An error occurred: {e}")

if __name__ == "__main__":
    main()

output
michael@13900d MINGW64 /c/wse_github/obrienlabsdev/rag/src/rag (main)
$ python app.py
USER_AGENT environment variable not set, consider setting it to identify your requests.
INFO:root:Docs content size: 43131
INFO:root:

      LLM Powered Autonomous Agents

Date: June 23, 2023  |  Estimated Reading Time: 31 min  |  Author: Lilian Weng

Building agents with LLM (large language model) as its core controller is a cool concept. Several proof-of-concepts demos, such as AutoGPT, GPT-Engineer and BabyAGI, serve as inspiring examples. The potentiality of LLM extends beyond generating well-written copies, stories, essays and programs; it can be framed as a powerful general problem solver.
Agent System Overview#
In
INFO:root:Splits: 66
INFO:root:Page content size: 969
INFO:root:Metadata size: 1
INFO:chromadb.telemetry.product.posthog:Anonymized telemetry enabled. See                     https://docs.trychroma.com/telemetry for more information.
INFO:httpx:HTTP Request: POST https://api.openai.com/v1/embeddings "HTTP/1.1 200 OK"
INFO:httpx:HTTP Request: POST https://api.openai.com/v1/embeddings "HTTP/1.1 200 OK"
INFO:root:Vectorstore retrieved: 6
C:\opt\Python310\lib\site-packages\langsmith\client.py:5431: LangChainBetaWarning: The function `loads` is in beta. It is actively being worked on, so the API may change.
  prompt = loads(json.dumps(prompt_object.manifest))
INFO:root:Example messages: You are an assistant for question-answering tasks. Use the following pieces of retrieved context to answer the question. If you don't know the answer, just say that you don't know. Use three sentences maximum and keep the answer concise.
Question: filler question
Context: filler context
Answer:
INFO:httpx:HTTP Request: POST https://api.openai.com/v1/embeddings "HTTP/1.1 200 OK"
INFO:httpx:HTTP Request: POST https://api.openai.com/v1/chat/completions "HTTP/1.1 200 OK"
INFO:root:rag_chain retrieved: 349
INFO:root:rag_chain retrieved content: Task Decomposition is a technique used in planning complex tasks by breaking them down into smaller, more manageable steps. This process enhances model performance by allowing the agent to think step-by-step and utilize more computational resources effectively. It can be achieved through simple prompts, task-specific instructions, or human inputs.


Month Issue

Hello,
There is a bug when you use the date input mask where you input either a 10 or 11 as the month value and then try and change it to another month such as 01. This is happening on the first input on your demo page: http://robinherbots.github.io/Inputmask/
Steps to replicate:

Enter the date 21/10/2016
Try to change the date to 21/01/2016 - You will notice when you enter the first digit of the month (0) that nothing happens until you press the 1. If you continue writing the date the end date is 21/12/2016 rather than 21/01/2016

Thank you
Lucy

@fseve ,
I am missing something, because I cannot reproduce.  What I see.
You enter 21102016
Put the caret in front of the month part and type 0  => this will give you 21/00/2016 => this should be 21/0_/2016
But I can continue with typing 1

@RobinHerbots
Sorry if I was somewhat confusing.
What I mean is that once a day digit is deleted the month should not move to the left.
I did some reading and found that someone also reported that issue here: 2006


[New game]: Spider Attack

🎮 Game Request
Game logic and basic description -
It's a spider game which I'm making using HTML, CSS & JavaScript.
It will contain Man with a Gun to shoot Spiders . 👍🏻
Point down the features
Game Includes Sounds, Gun, Spider, Man, Pop-Up and few more functionality.
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @SyedImtiyaz-1 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/assign

Hey @SyedImtiyaz-1 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


Freely move through history

This includes the ability to copy an image which is not the latest one

Fix also the scroll


Update to github 4.31.0 provider

Match what we have in other repos
Signed-off-by: Lance Albertson<EMAIL_ADDRESS>

The following members are trying to be added back during the plan run.

@brholtkamp
@lamont-granquist
@PowerSchill
@reset
@sam1el

Do any of you want me to go ahead and remove you from this Sous Chefs? I seem to recall this happening the last time this ran.

@ramereth can you reccy and update the members list as appropriate from the diff (ignore the fact my account is outside of the maintainers, I did that manually due to noise spam)


Add 'backup' and 'restore' functions with pluggable backends

Backup in kafka is poorly supported. There is the S3 connector and also https://github.com/itadventurer/kafka-backup
SpecMesh would allow (via tags) - the ability to run backup to one of the following  S3, filesystem, topic etc and also restore.  it would include topic-partition data, topic config and offsets

https://aws.amazon.com/blogs/big-data/back-up-and-restore-kafka-topic-data-using-amazon-msk-connect/


[WIP] 2.1 Training: Intro + Ops Basics

Updates to training for 2.1

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/1e8428a6a3b4de8164885da3aa8bf1f7f483b530/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/ff7598f2e2a1ffe289439488dd5dab771974c3bc/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/e3912328ed0195086217543ebd3d1751b34d2c0c/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/f9e8bef8679e9c0351333c402542dfa879f34d71/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/cbe2166383fd73ddb9b6651c7bf4ee02c6b2357e/

New lab content for Production Deployments / Debug Logs. Is this needed?

@lhirata, no. After chatting with @rolandcrosby, I think we're going to consolidate these slide-only modules into more of a see also list. I'll handle that at some point.

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/a9a4390316f4f212d45eb27c7ef7c484b4bea475/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/b2bf9f22e70ad1c2e547563d329b4b203d8cb877/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/eca4ee3ba59ec26b61827aa809d708eaee32e7e9/


README:  Warn users about use of guest accounts

Warn users against using guest accounts in the Smart Life App.
They can't be paired with Tuya's IOT platform, and attempting to pair them causes the guest account to be deleted and all paired devices forgotten, which can be a pain if you've already set everything up.

Thanks for the doc update, @Hello1024 .Hopefully this will help others. 🙏


Add Organizers

Add in new Organizers Section.
Note: This is just to create the structure. Content and approval is needed before merge.
Context:
https://github.com/techqueria/website/issues/98

lets collect more bios

We'll need to change the file naming conventions to be lowercase with dashes for spaces but otherwise, it looks good and the info just needs to be added in (I can help with this once the info gets added in).
Thank you for getting this started @Bedrock02!

@WilliamMena @Bedrock02 We're going to close this PR in favor of #190 and we ask that you both open a PR to add your bios in. Thank you!


[RFC] A new network wire protocol

tl;dr: We're changing from stream-oriented communication to message-oriented communication.
Why?
We've been operating the current network stack in Libra for almost a year with little to no issues, and acceptable performance. So why change? Here are a few reasons:

Performance: The current protocol and implementation stack is based on Yamux. Yamux allows us to multiplex several "streams" on a single TCP connection, enabling execution of several RPCs and message sends in parallel. It also allows for "server-initiated" streams, making it a good fit for p2p communication needed in blockchain systems. However, the protocol introduces limitations as a result of the critical design choice of using per-stream flow control. Yamux has a notion of receive_window which enables per-stream flow control. A receiver must issue a receive_window_update before the sender can send any more data on a stream once the current window has been saturated. The default assumed receive window size is 256KB, but can be updated any time during a stream's lifetime. This, however, introduces extra latency of 1 RTT in communication whenever the sender needs to send data larger than the default window size, since it must wait for the receive_window_update to arrive after the 256 KB of data is sent. We believe this is unnecessary for our purpose, and that TCP's in-built flow control is sufficient. Additionally, this makes the protocol hard to debug, since sending of data blocks if the receiver has not updated the receive window.
Message priority: Although Yamux provides fairness through per-stream flow control, it doesn't have a notion of stream priority. This means that all streams compete for a shared resource, i.e., the underlying connection. Having prioritized delivery is useful in cases like Libra, where the message priority is fairly deterministic (e.g. consensus messages are higher priority than mempool messages) and which can benefit from reduced latency in some parts while sacrificing latency in others. One could implement notions of priority in the Yamux libraries at the two ends of a connection, but that seems a fairly complex undertaking.
Safety and inter-operability with TCB networking: The current state-of-the-art Yamux implementation in Rust exposes an async API and requires a futures executor to drive the underlying connection. Since we wish to use LibraNet for secure communication between consensus and TCB (instead of the current bespoke TCB networking library), it's desirable to avoid the need for using an executor, since executors such as tokio use (or depend on) a fair amount of unsafe code.
Ecosystem: Although the Yamux protocol is now more than 5 years old, it lacks community-wide adoption. Quality implementations are only available in Go and Rust. Implementors of Libra in any other language would need to take on the necessary undertaking of implementing the Yamux protocol in addition to the Libra protocol. Since re-implementing Libra in as many languages as possible and increasing ecosystem diversity is something we believe is important, we think it's best to remove Yamux and instead leverage lcs which needs to be implemented anyhow.

New protocol:
While complete details of the new protocol are still being flushed out, here are the basic pieces:
The core networking protocol is built around sending and receiving the fully self-contained NetworkMessage struct defined below:
/// Message variants that are sent on the wire.
#[derive(Clone, Debug, Deserialize, Serialize)]
pub enum NetworkMessage {
    Error(ErrorCode),
    Ping(Nonce),
    Pong(Nonce),
    RpcRequest(RpcRequest),
    RpcResponse(RpcResponse),
    DirectSendMsg(DirectSendMsg),
}

/// Enum representing various error codes that can be embedded in error messages.
#[derive(Clone, Debug, Deserialize, Serialize)]
pub enum ErrorCode {
    /// Failed to parse NetworkMessage when interpreting according to provided protocol version.
    ParsingError(MessagingProtocolVersion, Box<NetworkMessage>),
    UnsupportedProtocol(ProtocolId),
    TimedOut,
}

/// Nonces used by Ping and Pong message types.
#[derive(Clone, Debug, Deserialize, Serialize)]
pub struct Nonce(u32);

#[derive(Clone, Debug, Deserialize, Serialize)]
pub struct RpcRequest {
    // RequestId for the RPC Request.
    pub request_id: u32,
    // `protocol_id` is an enum variant of ProtocolId enum defined in the handshake
    // protocol.
    pub protocol_id: ProtocolId,
    // Request priority.
    pub priority: u8,
    // Request payload. This will be parsed by the application-level handler.
    pub raw_request: Bytes,
}

#[derive(Clone, Debug, Deserialize, Serialize)]
pub struct RpcResponse {
    // RequestId for corresponding request; copied as is from RpcRequest.
    pub request_id: u32,
    // Response priority. This will likely be same as the priority of corresponding request.
    pub priority: u8,
    // Response payload.
    pub raw_response: Bytes,
}

#[derive(Clone, Debug, Deserialize, Serialize)]
pub struct DirectSendMsg {
    // `protocol_id` is an enum variant of ProtocolId enum defined in the handshake
    // protocol.
    pub protocol_id: ProtocolId,
    // Message priority.
    pub priority: u8,
    // Message payload.
    pub raw_msg: Bytes,
}

/// Type for unique identifier associated with each network protocol
/// List of application level protocols.
#[repr(u8)]
#[derive(Clone, Copy, Debug, Hash, Eq, PartialEq, Deserialize_repr, Serialize_repr)]
pub enum ProtocolId {
    ConsensusRpc = 0,
    ConsensusDirectSend = 1,
    MempoolDirectSend = 2,
    StateSynchronizerDirectSend = 3,
    DiscoveryDirectSend = 4,
    HealthCheckerRpc = 5,
}

We use lcs for serializing the NetworkMessage struct on the wire and length-prefix that with a u32. Note that all fields are in little-endian form. Effectively, the network socket (which can be thought of as a stream of bytes) becomes a stream (and sink) of NetworkMessages. These network messages are then handled by the network module and sent to registered upstream handlers.
It is important to note that there will be some added complexity in the implementation of the rpc module which now needs to manage RPC completions instead of relying on the request and responses being embedded inside streams which are managed by the yamux library. On the other hand, we will get rid of things such as per-stream protocol negotiation (since the ProtocolId is now embedded inside the messages), maintaining long-lived streams for DirectSend, and the need to open a new stream per RPC.
More details, such as dependencies and protocol upgradability, will be captured in the full Libra wire spec.
cc: @phlip9, @aching, @davidiw

Could you elaborate on the handshake protocol?

@phlip9 any reason not to close this one?


Do not receive anything in OSD mode

@tumbili This will save quite a bit of RAM on the Pixracer and might help you.

A side note: OSDs can request message streams. Although this is not implemented on our side yet, and the default streams cover everything anyway. I see not big issue taking this out ATM, might just need to be added later again.

Applied.


Timelines

Hey!
Thanks for taking up this initiative.
I wanted to know when will the training script be released publicly?

Thank you for your interest! I'm actively working on verifying the training implementation to ensure alignment with the original settings. I'm considering an initial release of the script that would allow everyone to try it out and contribute to its refinement. I anticipate this release within the next couple of weeks. Your input is highly appreciated, and I'll provide updates as I make progress.

Thanks for the response. Looking forward to contributing.

Will keep this open. You can close it once you release it :)

Hi, super thanks to your great initiative!
Do you have any updates on the training script?

Hi @lirus7 @Xiashangning
The training script is just released. Please let me know if it works well! Cheers!

Great! Will test it asap
Thanks a lot


[mini.files] open buffer

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md

Module(s)
mini.files
Description
Would be nice to have a mapping for opening the currently selected file and closing the filetree at once.
It feels a bit off not to be able to smash enter and instantly jump in the file.

It is L by default and can be configured in config.mappings.go_in_plus.

Oh sorry. It was actually not that hard to understand, my bad, but maybe comments would help.
			mappings = {
				close = "q", -- close filetree
				go_in = "l",
				go_in_plus = "<CR>", -- open file & close filetree
				go_out = "h",
				go_out_plus = "<BS>",
				mark_goto = "'", -- go to bookmark
				mark_set = "m", -- set bookmark
				reset = "<BS>", -- go back to $CWD
				reveal_cwd = "Y",
				show_help = "g?",
				synchronize = "<C-w>", -- save changes
				trim_left = "<Left>", -- ??
				trim_right = "<Right>", -- ??
			},


Btcatomicswap for Electrum

While atomic swaps are great and enable trustless trading, they do have some drawbacks. The current toolset requires wallets with full nodes.
In order to eliminate the need to download the blockchain, the atomic swap tools should be able to use thin clients.  For bitcoin, we could use Electrum.
Part of https://github.com/rivine/rivine/blob/master/specs/beyond_atomic swaps.md#1-eliminate-the-need-to-download-the-blockchain

Please provide more information.

Updated the original comment

https://github.com/rivine/atomicswap


Copy instead of assign input state for ProductState multiplication

Fixes: https://github.com/quantumlib/Cirq/issues/3691

Can we add a test that would have failed with the previous behavior?

Can we add a test that would have failed with the previous behavior?

@mpharrigan Done.

@mpharrigan Done.

Thanks for the fix!!!

Thanks for the fix!!!


ERROR: CUDA

ERROR:  CUDA failed at prehash.cu: 65
CUDA error code 209
Miner is now terminated
version NVMiner 2.0.0

I got the same issues and fixed by trying out different version of driver. I'm currently still using kepler card, 1 of my card cannot be use because of its low memory capacity.
I just compile the source code on my own and modify the line 461th in autolykos.cu from for (int i=0; i< deviceCount; ++i) to for (int i=0; i<deviceCount - 1; ++i) to omit the low capacity card and use only the remaining ones.


retryStrategy on GKE preemptive node does't work

Hi guys,
this issue is still active.
argo version: 2.8.1 on GKE
In particular, if a pod failed is marked with a red /!\ (pod deleted) and the workflow is running forever.
this is my retry strategy:
retryStrategy:
limit: 4
retryPolicy: "Always"
backoff:
duration: "12s"
factor: 5
maxDuration: "200m"

Hi @fabio-rigato, it seems that we accidentally didn't include the fix for this (https://github.com/argoproj/argo/pull/2976) in v2.8.1.
The fix is present on v2.9.0-rc1, but that is a pre-release and is not recommended for production systems yet. I will look into releasing a v2.8.2 with the fix soon.

Hi @simster7 thanks a lot for your fast reply.
Happy to hear that mate!
I hope you a great day!
All the best
Fabio

Hey @simster7 do you have any ETA for v2.8.2 release? because this issue is affecting us in production and we need to upgrade asap.
Thanks for your effort.
Cheers.
Fabio

I’ll try to get a release out this week

thanks for that @simster7

#3214

Fixed in #2976


Individual webhooks

An ability to assign webhooks to specific notifications such as deaths

This exists as another plugin, Raid Shamer

I would build a UI where you can have individual webhooks with their own respective whitelists and blacklists.
For example webhookUrl for a discord server with your group ironman, where 1 rsn is whitelisted, but in another 3 are whitelisted.


[Feature Request] - Login/Authentication support (at least basic support like token or something)

First of all, Awesome Tool 😎
if i deployed this somewhere to have the access from internet, then some kind of auth should be there so that only i can access my cluster.

Hello @moinologics thanks so much for trying out and kind words.
Sure this is in our pipeline we are looking to add this.
How about pain basic auth we can look into it quite quickly in the next couple of releases.

A neat addition would be to support Kubernetes impersonation. This could work by allowing an admin to configure a default Kubernetes configuration with broad access (for example, access to namespaces A, B, and C). Then, a proxy would inject the impersonation headers corresponding to the current user, who might have access only to namespace A. These impersonation headers would then be used in the Kubernetes API queries to limit the result scope to only namespace A. This approach can ease setup for organizations using SSO, as it allows skipping the need for database and session management entirely.
References:

https://kubernetes.io/docs/reference/access-authn-authz/authentication/#user-impersonation
https://github.com/kubernetes/dashboard/blob/d6c217d20b1ab52815955ea819bdc832529d71db/docs/user/README.md


Block functions do not seem to work with iOS 6

I'm using SDK version 2.2.0 and 2.2.1, but on iOS 6 for example method 'invokeAPI' doesn't do anything.
While for iOS 7 and 8 it works fine.
What is the minimum iOS version for SDK 2.2.x?
On https://github.com/Azure/azure-mobile-services/blob/master/CHANGELOG.ios.md is mentioned at 1.1.2: "Now requires iOS 6 or newer to use"
At higher versions, iOS minimum target is never mentioned.

Yes, 2.0 should have called out it requires iOS 7.0, as we took a dependency on NSURLSession, which doesn't exist in iOS 6.

Updated changelog to indicate dependency.


US Phone number not recognized within Spanish text

Issue
US Phone number not recognized within Spanish text
Sample Input
"Llámame al<PHONE_NUMBER> cuando puedas si no puedes contactarme al <IP_ADDRESS>"
Response:
(206)555-1212 --> not detected as Phone Number.

This works correctly in /master. The next release of the packages will include the fix.
Thanks.


Simpler float index conv., xsd:double fix #196

This is WIP, we may want to also restore if the original value was
xsd:double or xsd:decimal

DO NOT MERGE AS THIS IS STILL INCOMPLETE/BROKEN

Ok I've just tested this on Wikidata Full and with the queries from #196 and it works really well (after previously running the wrong version on the new index). @floriankramer or @joka921 can you give this a quick look?


Remove VisualScriptSubCall

As described in proposal 3543 this PR removes the broken VisualScriptSubcall class.

Requires rebasing.

Closing as we just removed VisualScript for 4.0, so this can no longer be evaluated as is.
The VisualScript module has been moved to https://github.com/godotengine/godot-visual-script with the aim that it might be ported to a GDExtension if there are interested contributors to do so. Further work to improve the features could be done on that repository too (so currently there isn't anyone dedicated to maintain this repository, it will depend again on whether some contributors step up to do so).


Overseer custom template yields an error

Hello mate,
I think there is an issue with the overseer custom template where if I run a test it basically says that the overseer template validation fails expecting a string and finding nil.
Here is the offending code:
  see.register_template {
     generator = function()
       local logHandler = io.popen [[fd -e log]]
       local ret = {}
       if logHandler then
         local logs = logHandler:read "*a"
         logHandler:close()
         for log in logs:gmatch "([^\r\n]+)" do
           table.insert(ret, {
             name = "Show " .. log,
             builder = function()
               return {
                 name = "Show " .. log,
                 cmd = "tail --follow --retry " .. log,
               }
             end,
             priority = 1000,
             params = {},
           })
         end
       end
       return ret
     end,
   }
 end

I think the tail fails and ret is just an empty {}.

hi dude, thank you
fixed via https://github.com/abzcoding/lvim/commit/665b4d7705f371f8c2d04024b24903951a00e1ad


Implement NATS TLS and subscriber security

Implement TLS between NATS server and NATS subscribers, plus authorize NATS subscribers (e.g. via client certificates).  Consider implementing this security as part of migrating to JetStream.

This was done as a part of migration to JetStream.

This was done as a part of migration to JetStream.


Tabs Web Part Not Fully Functional in Modern Page

After adding the Tabs wp to my modern page, I noticed that I do not see the toolbars as pictured in your Overview, and I can only update the first tab.  Clicking additional tabs kicks the wp out of edit mode.
Same results in Chrome version 58.0.3029.110 (64-bit), Internet Explorer 11 version 11.672.105860.0, and Edge 25.10586.672.0 (HTML 13.10586)
To better illustrate, see this video snip.   Any words of wisdom?

Thanks you @hrn111 for this bug report. We will correct it soon.
Regards,
Olivier

Hi @hrn111, I confirm you that this bug is now fix in the new version <IP_ADDRESS>, available in the source control or here:  https://github.com/OlivierCC/spfx-40-fantastics/releases
Thanks again for your bug report, regards,
Olivier


Documentation is not accessible

I get a 403 Forbidden error when I click on User Manual/Developer Manual on Documentation page.

I just extended the SSL certificate. I wonder if it shouldn't still have worked for you, as it was good for a couple of hours. Anyways, seems to work now.


Version <IP_ADDRESS>70615 crashes after a couple of hours

The new versions runs inbetween 4 and 36 hours (I had to crashes). Then the Web-Interface and obviously the execution of programs, initiated by events, does not work.
The old version was stable over weeks.

I have exactly the same problem

Are there entries in the log? What is the output of 'ps -ef' on the ssh console when the ccu2 is crashed? Maybe https://homematic-forum.de/forum/viewforum.php?f=65 is the better place to discuss until the problem/bug is found.

I already found and fixed the problem (it is an issue with the linux kernel) thanks for the reports. I will try to release a fixed version until monday

Great :-) Firmware 2.29 is on it's way too ;-)

Sure, but this will have to be integrated in another version.

Commit fd1c3c67b266cca783f18d7aa9cf1a6e771549ad should fix this problem.


Update bigint2 impl with 4096 bit support

Draft PR until this is released into 1.2 -- as this is pointing to the git version

Running tests in zkvm, most pass but one hits memory cap (might just be too many tests run and using bump alloc, but will check the specific failure to make sure not an edge case)
running 8 tests
test decode_rsa2048_priv_der ... ok
test decode_rsa2048_priv_pem ... ok
test decode_rsa2048_pub_der ... ok
test decode_rsa2048_pub_pem ... ok
test encode_rsa2048_priv_der ... ok
test encode_rsa2048_priv_pem ... ok
test encode_rsa2048_pub_der ... ok
test encode_rsa2048_pub_pem ... ok

test result: ok. 8 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out

Running test in guest: /Users/austinabell/development/risc0/RustCrypto-RSA/target/riscv32im-risc0-zkvm-elf/debug/deps/pkcs1v15-d75b7fdbf54859c1 []

running 1 test
test signature_stringify ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out

Running test in guest: /Users/austinabell/development/risc0/RustCrypto-RSA/target/riscv32im-risc0-zkvm-elf/debug/deps/pkcs1-37c12db8e7c347cb []

running 16 tests
test decode_rsa2048_priv_der ... ok
test decode_rsa2048_priv_pem ... ok
test decode_rsa2048_pub_der ... ok
test decode_rsa2048_pub_pem ... ok
test decode_rsa4096_priv_der ... ok
test decode_rsa4096_priv_pem ... ok
test decode_rsa4096_pub_der ... ok
test decode_rsa4096_pub_pem ... ok
test encode_rsa2048_priv_der ... ok
test encode_rsa2048_priv_pem ... ok
test encode_rsa2048_pub_der ... ok
test encode_rsa2048_pub_pem ... ok
test encode_rsa4096_priv_der ... ok
test encode_rsa4096_priv_pem ... ok
test encode_rsa4096_pub_der ... ok
test encode_rsa4096_pub_pem ... ok

test result: ok. 16 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out

Running test in guest: /Users/austinabell/development/risc0/RustCrypto-RSA/target/riscv32im-risc0-zkvm-elf/debug/deps/rsa-ad39eb3288bfe13d []

running 55 tests
test algorithms::generate::tests::key_generation_1024 ... ok
test algorithms::generate::tests::key_generation_128 ... ok
test algorithms::generate::tests::key_generation_multi_16_1024 ... ok
test algorithms::generate::tests::key_generation_multi_3_256 ... ok
test algorithms::generate::tests::key_generation_multi_4_64 ... ok
test algorithms::generate::tests::key_generation_multi_5_64 ... ok
test algorithms::generate::tests::key_generation_multi_8_576 ... ok
test algorithms::generate::tests::test_impossible_keys ... ok
test algorithms::pad::tests::test_left_pad ... ok
test algorithms::pkcs1v15::tests::test_non_zero_bytes ... ok
test algorithms::rsa::tests::recover_primes_works ... ok
test key::tests::build_key_from_p_q ... ok
test key::tests::build_key_from_primes ... ok
test key::tests::invalid_coeff_private_key_regression ... ok
test key::tests::key_generation_1024 ... ok
test key::tests::key_generation_128 ... ok
test key::tests::key_generation_multi_16_1024 ... ok
test key::tests::key_generation_multi_3_256 ... ok
test key::tests::key_generation_multi_4_64 ... ok
test key::tests::key_generation_multi_5_64 ... ok
test key::tests::key_generation_multi_8_576 ... ok
test key::tests::reject_oversized_private_key ... ok
test key::tests::test_from_into ... ok
test key::tests::test_negative_decryption_value ... ok
test oaep::tests::test_decrypt_oaep_invalid_hash ... ok
test oaep::tests::test_decrypt_oaep_invalid_hash_traits ... ok
test oaep::tests::test_encrypt_decrypt_oaep ... ok
test oaep::tests::test_encrypt_decrypt_oaep_traits ... ok
test pkcs1v15::tests::test_decrypt_pkcs1v15 ... ok
test pkcs1v15::tests::test_decrypt_pkcs1v15_traits ... ok
test pkcs1v15::tests::test_encrypt_decrypt_pkcs1v15 ... ok
test pkcs1v15::tests::test_encrypt_decrypt_pkcs1v15_traits ... ok
test pkcs1v15::tests::test_sign_pkcs1v15 ... ok
test pkcs1v15::tests::test_sign_pkcs1v15_digest_signer ... ok
test pkcs1v15::tests::test_sign_pkcs1v15_signer ... ok
test pkcs1v15::tests::test_sign_pkcs1v15_signer_sha2_256 ... ok
test pkcs1v15::tests::test_sign_pkcs1v15_signer_sha3_256 ... ok
test pkcs1v15::tests::test_unpadded_signature ... ok
test pkcs1v15::tests::test_unpadded_signature_hazmat ... ok
test pkcs1v15::tests::test_verify_pkcs1v15 ... ok
test pkcs1v15::tests::test_verify_pkcs1v15_digest_signer ... ok
test pkcs1v15::tests::test_verify_pkcs1v15_signer ... ok
Error: Guest panicked: Out of memory!
test pss::test::test_sign_and_verify_2049bit_key ...

Update on the above, running tests without that test passes all, and running just that test in isolation works fine. It's just a very large execution with a profile that looks like this:

(not sure if a use case we want to focus on adding a precompile for)


Prisma connection not closing in Playwright test runner

Bug description
Hello, Prisma team, thanks for your amazing work.
We use Playwright for running e2e tests against our web applications at my company. We are already using Prisma on the backend and would like to use it also for seeding (and tearing down) the data that is required for running the tests (creating a test user, deleting a post after creating it, etc).
So far Prisma works well for this purpose, speeding up my workflow a lot. However, some of the time, the playwright process gets stuck and It never exits. I suspect that it is related to the Prisma client connection because I see these logs over and over when the tests have been completed (using DEBUG=*):

This goes on forever and I have to manually Ctrl+C, which is not ideal for a CI environment
How to reproduce
So far I have not reached a reliable reproduction. For every 5 tests that I run, 3 of them get stuck and never exit.
I'd like to know if you can give me any hints at what may be causing this problem or how to properly manage my connections. It might be useful to consider that Playwright runs tests in parallel using worker processes.
Expected behavior
I expect the Playwright process to exit immediately after the tests have completed (either successful or unsuccessfully)
Prisma information

Environment & setup

OS: KDE Neon 5.24
Database: MySQL 8
Node.js version: 14.17.4

Prisma Version
prisma                  : 3.13.0
@prisma/client          : 3.13.0
Current platform        : debian-openssl-1.1.x
Query Engine (Node-API) : libquery-engine efdf9b1183dddfd4258cd181a72125755215ab7b (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli efdf9b1183dddfd4258cd181a72125755215ab7b (at<EMAIL_ADDRESS>Introspection Engine    : introspection-core efdf9b1183dddfd4258cd181a72125755215ab7b (at<EMAIL_ADDRESS>Format Binary           : prisma-fmt efdf9b1183dddfd4258cd181a72125755215ab7b (at<EMAIL_ADDRESS>Default Engines Hash    : efdf9b1183dddfd4258cd181a72125755215ab7b
Studio                  : 0.459.0
Preview Features        : fullTextSearch, fullTextIndex

Is the log sequence repeating? Can you post a full "iteration" of that sequence as text (instead of screenshot)? Thanks.

Sure, @janpio, here it is:

pw:channel:event {
pw:channel:event   guid: '',
pw:channel:event   method: 'create',
pw:channel:event   params: {
pw:channel:event     type: 'BrowserType',
pw:channel:event     initializer: {
pw:channel:event       executablePath: '/home/alexrv/.cache/ms-playwright/chromium-1000/chrome-linux/chrome',
pw:channel:event       name: 'chromium'
pw:channel:event     },
pw:channel:event     guid: 'browser-type@f74b5c965c6ef7df504f24ab3a245f00'
pw:channel:event   }
pw:channel:event } +0ms
pw:channel:event {
pw:channel:event   guid: '',
pw:channel:event   method: 'create',
pw:channel:event   params: {
pw:channel:event     type: 'BrowserType',
pw:channel:event     initializer: {
pw:channel:event       executablePath: '/home/alexrv/.cache/ms-playwright/firefox-1322/firefox/firefox',
pw:channel:event       name: 'firefox'
pw:channel:event     },
pw:channel:event     guid: 'browser-type@18ba76dba19b322467cce041bd976e15'
pw:channel:event   }
pw:channel:event } +3ms
pw:channel:event {
pw:channel:event   guid: '',
pw:channel:event   method: 'create',
pw:channel:event   params: {
pw:channel:event     type: 'BrowserType',
pw:channel:event     initializer: {
pw:channel:event       executablePath: '/home/alexrv/.cache/ms-playwright/webkit-1630/pw_run.sh',
pw:channel:event       name: 'webkit'
pw:channel:event     },
pw:channel:event     guid: 'browser-type@302788b257e2fb98f8dba0dded9d30aa'
pw:channel:event   }
pw:channel:event } +0ms
pw:channel:event {
pw:channel:event   guid: '',
pw:channel:event   method: 'create',
pw:channel:event   params: {
pw:channel:event     type: 'Android',
pw:channel:event     initializer: {},
pw:channel:event     guid: 'android@56bdc20f6990c78c062ff5acc5b28aac'
pw:channel:event   }
pw:channel:event } +1ms
pw:channel:event {
pw:channel:event   guid: '',
pw:channel:event   method: 'create',
pw:channel:event   params: {
pw:channel:event     type: 'Electron',
pw:channel:event     initializer: {},
pw:channel:event     guid: 'electron@f6d62861742e61fdabf2edabd4761ef2'
pw:channel:event   }
pw:channel:event } +0ms
pw:channel:event {
pw:channel:event   guid: '',
pw:channel:event   method: 'create',
pw:channel:event   params: {
pw:channel:event     type: 'LocalUtils',
pw:channel:event     initializer: {},
pw:channel:event     guid: 'localUtils@e7dae7e82008aa79d77ee920fd592f07'
pw:channel:event   }
pw:channel:event } +1ms
pw:channel:event {
pw:channel:event   guid: '',
pw:channel:event   method: 'create',
pw:channel:event   params: {
pw:channel:event     type: 'Selectors',
pw:channel:event     initializer: {},
pw:channel:event     guid: 'selectors@688d465a25a225f2e3e18e618e57b105'
pw:channel:event   }
pw:channel:event } +0ms
pw:channel:event {
pw:channel:event   guid: '',
pw:channel:event   method: 'create',
pw:channel:event   params: {
pw:channel:event     type: 'Playwright',
pw:channel:event     initializer: {
pw:channel:event       chromium: [Object],
pw:channel:event       firefox: [Object],
pw:channel:event       webkit: [Object],
pw:channel:event       android: [Object],
pw:channel:event       electron: [Object],
pw:channel:event       utils: [Object],
pw:channel:event       deviceDescriptors: [Array],
pw:channel:event       selectors: [Object],
pw:channel:event       preLaunchedBrowser: undefined,
pw:channel:event       socksSupport: undefined
pw:channel:event     },
pw:channel:event     guid: 'Playwright'
pw:channel:event   }
pw:channel:event } +1ms
prisma:tryLoadEnv Environment variables loaded from /home/alexrv/Projects/quentli/quentli/.env +0ms
prisma:tryLoadEnv Environment variables loaded from /home/alexrv/Projects/quentli/quentli/.env +406ms
prisma:client dirname /home/alexrv/Projects/quentli/quentli/node_modules/.prisma/client +0ms
prisma:client relativePath ../../../prisma +0ms
prisma:client cwd /home/alexrv/Projects/quentli/quentli/prisma +0ms
prisma:client clientVersion: 3.13.0 +36ms
prisma:client clientEngineType: library +0ms
prisma:client:libraryEngine internalSetup +0ms
prisma:client:libraryEngine hookProcess received: exit +274ms
prisma:client:libraryEngine runBeforeExit +0ms

@arvindell thank you for this issue, would you be able to run your e2e tests with Node.js v18.3.0 (which might provide more insights and diagnostics about leaked promises/resources) and prisma v3.15.0, and see if you get the same issue?

How do we get to a reproduction of this @arvindell? Right now we are just guessing, but of course we would love to experience this ourselves so we can actually fix it. Thanks.

How do we get to a reproduction of this @arvindell? Right now we are just guessing, but of course we would love to experience this ourselves so we can actually fix it. Thanks.

Hi! Since I created this issue this is not a problem anymore. The tests are closing the connection correctly now. I'm guessing it was a Playwright bug that got fixed
Thanks!

Awesome, thanks for the update!


Updated URDF masses and collision shapes

This URDF change contains:

More accurate mass and inertial values for linkages
Tighter collision shapes, and secondary linkages containing additional collision shapes

@rethink-forrest likely these changes are fine, but you you mind giving them a quick once-over?

:shipit:
Looks good

thanks!


Intellisense docstrings do not follow functools.wraps() semantics

Environment data

VS Code version: 1.27.2 (user setup)
Extension version (available under the Extensions sidebar): 2018.8.0
OS and version: Windows 10 Enterprise 1803 (64-bit)
Python version (& distribution if applicable, e.g. Anaconda): Official CPython 3.7.0
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): replicated with system-level interpreter & pipenv
Relevant/affected Python packages and their versions: N/A (problem is with core language and stdlib)

Actual behavior
The function docstrings shown in the intellisense popout (visible on hover) are showing docstrings which do not match those of the interpreter's inspect.getdoc() output.
Expected behavior
The function docstrings shown in the intellisense popout (visible on hover) should match the docstrings shown by the interpreter (output of inspect.getdoc() used as reference), even when there are decorators (sometimes multiple layers) covering them.
Steps to reproduce:
This issue is somewhat reproducible with jedi as the backing language server, but seems more consistent with then new language server.

Hover over the function references on lines 38-39 of the included reproduction script:
issue.py.txt

Note that the docstrings shown are not the same as the output of inspect.getdoc()

I have included a gif of the reproduction (located at the end of this issue document) to show the kind of output I am getting.
Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
Starting Microsoft Python language server.
Initializing for D:\Python37\python.exe

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)
None

Gif

Opening a new issue after #210 was closed.  I was asked to replicate the issue on the new language server before reopening, which I have done.

Verified that this behaviour is indeed happening in Windows 10 on the latest VSCode + extension + Language Server.

Fixed by microsoft/python-language-server#546


Routing on Zynq with PS7 takes a long time on the first iteration

With designs that do instantiate the PS7 primitive, the router takes quite some time on the first iteration with the following output:
## Initializing router criticalities took 0.00 seconds (max_rss 1887.3 MiB, delta_rss +0.0 MiB)
---- ------ ------- ---- ------- ------- ------- ----------------- --------------- -------- ---------- ---------- ---------- ---------- --------
Iter   Time    pres  BBs    Heap  Re-Rtd  Re-Rtd Overused RR Nodes      Wirelength      CPD       sTNS       sWNS       hTNS       hWNS Est Succ
      (sec)     fac Updt    push    Nets   Conns                                       (ns)       (ns)       (ns)       (ns)       (ns)     Iter
---- ------ ------- ---- ------- ------- ------- ----------------- --------------- -------- ---------- ---------- ---------- ---------- --------
Warning 693: No routing path for connection to sink_rr 321098, retrying with full device bounding box
Warning 694: No routing path for connection to sink_rr 321111, retrying with full device bounding box
Warning 695: No routing path for connection to sink_rr 321110, retrying with full device bounding box
Warning 696: No routing path for connection to sink_rr 321109, retrying with full device bounding box
Warning 697: No routing path for connection to sink_rr 321108, retrying with full device bounding box
Warning 698: No routing path for connection to sink_rr 321107, retrying with full device bounding box
Warning 699: No routing path for connection to sink_rr 321106, retrying with full device bounding box
Warning 700: No routing path for connection to sink_rr 321105, retrying with full device bounding box
Warning 701: No routing path for connection to sink_rr 321104, retrying with full device bounding box
Warning 702: No routing path for connection to sink_rr 321103, retrying with full device bounding box
Warning 703: No routing path for connection to sink_rr 321102, retrying with full device bounding box
Warning 704: No routing path for connection to sink_rr 321101, retrying with full device bounding box
Warning 705: No routing path for connection to sink_rr 321100, retrying with full device bounding box
Warning 706: No routing path for connection to sink_rr 321099, retrying with full device bounding box
Warning 707: No routing path for connection to sink_rr 321112, retrying with full device bounding box
Warning 708: No routing path for connection to sink_rr 321097, retrying with full device bounding box
Warning 709: No routing path for connection to sink_rr 321096, retrying with full device bounding box
Warning 710: No routing path for connection to sink_rr 321095, retrying with full device bounding box
Warning 711: No routing path for connection to sink_rr 321094, retrying with full device bounding box
Warning 712: No routing path for connection to sink_rr 321093, retrying with full device bounding box
Warning 713: No routing path for connection to sink_rr 321092, retrying with full device bounding box
Warning 714: No routing path for connection to sink_rr 321091, retrying with full device bounding box
Warning 715: No routing path for connection to sink_rr 321090, retrying with full device bounding box
Warning 716: No routing path for connection to sink_rr 321089, retrying with full device bounding box
Warning 717: No routing path for connection to sink_rr 321088, retrying with full device bounding box
Warning 718: No routing path for connection to sink_rr 321087, retrying with full device bounding box
Warning 719: No routing path for connection to sink_rr 321086, retrying with full device bounding box
Warning 720: No routing path for connection to sink_rr 321085, retrying with full device bounding box

I believe that this might be a lookahead related issue, as the PS7 is a tile which height is the same height of the full device (at least for the z010 part). The router might be misguided when trying to reach sinks in the PS7 site, as certain connections to the PS7 might be found in very different Y-locations.
One other thing to note is that the PS7, has all the unconnected pins routed to $false, and there are more than 1000 pins for the PS7 primitive.
I need to gather more data to add some details on the issue and to have a clearer understanding on what is going on.

The connection box lookahead likely helped with this in the past.  Xifan is working on a map lookahead improvement with tall tiles, which might help us if we enlarge the PS7 tile in the arch description.


[FEATURE] delta_uniform_iceberg property on tables API

Problem Statement
The tables API returns a delta_uniform_iceberg field which includes information like the metadata location. This is extremely important for reading UniForm tables from Iceberg clients.
GET api/2.1/unity-catalog/tables/<catalog-name>.<schame-name>.<table-name>
Proposed Solution
Update the TableInfo Dataclass to support all current properties returned by the API.
Additional Context
I am surprised that the SDK is not better synchronized with the current state of the API - how long should we expect this lag to be when new features are introduced?

Alternatively, it would be great if every single dataclass had a response field that includes the unmodified response JSON. This would allow us to use that directly when a new feature has not been implemented yet.


Improve documentation for "how to run a parse"

I'm requesting improvement of the doc at http://nomad-lab.eu/prod/v1/staging/docs/apis/local_parsers.html
Details:

The concept of a parser might not be familiar to the user, so a link to the doc describing it would help.
A lot of the doc is about handling potential troubleshooting related to installing a dependency. This could be handled in a separate doc and be linked from here.
Add a link to the normalization doc.
Explain under what circumstances can the normalization step may be skipped?
The python code should explain that the normalization step may be commented out for the case when normalization is not required.

Hello, I followed tutorial 13 but executed the following command:
nomad parse tests/data/test_sintering.archive.yaml --show-archive > normalized.archive.json
the following error appears even though everything is configured correctly in my environment:
ModuleNotFoundError: No module named 'sintering'
You are accessing functionality that requires extra dependencies.
Check the NOMAD documentation or install all extra dependencies:
pip install nomad-lab[infrastructure,dev]
But these modules are well installed too.

Hello, I followed tutorial 13 but executed the following command:
nomad parse tests/data/test_sintering.archive.yaml --show-archive > normalized.archive.json
the following error appears even though everything is configured correctly in my environment: ModuleNotFoundError: No module named 'sintering' You are accessing functionality that requires extra dependencies. Check the NOMAD documentation or install all extra dependencies: pip install nomad-lab[infrastructure,dev]
But these modules are well installed too.

@PauloGitHB this is probably not the best place to discuss this problem as this is not an issue concerning the parsing documentation. I would recommend to either ask on our Discord server: https://discord.gg/Gyzx3ukUw8 (recommended as I believe it's an issue with your environment and not a problem with NOMAD), or open a separate issue describing your problem, ideally with a link to a repository where you are working and a set of steps for how to reproduce your issue.
That being said, the error states that you don't have a module called 'sintering' which would either suggest that you have not installed the plugin you are developing in your environment or that said plugin doesn't include a module called 'sintering'.

Hello,
Sorry I saw the forum title too late but I have already deleted my comment.
Thank you for your help
Have a nice day

De : Hampus Näsström @.>
Envoyé : jeudi 19 septembre 2024 15:12
À : nomad-coe/nomad @.>
Cc : Paul Levasseur @.>; Mention @.>
Objet : Re: [nomad-coe/nomad] Improve documentation for "how to run a parse" (Issue #86)
Vous ne recevez pas souvent de courriers de la part de @.*** Découvrez pourquoi cela est importanthttps://aka.ms/LearnAboutSenderIdentification
Hello, I followed tutorial 13 but executed the following command:
nomad parse tests/data/test_sintering.archive.yaml --show-archive > normalized.archive.json
the following error appears even though everything is configured correctly in my environment: ModuleNotFoundError: No module named 'sintering' You are accessing functionality that requires extra dependencies. Check the NOMAD documentation or install all extra dependencies: pip install nomad-lab[infrastructure,dev]
But these modules are well installed too.
@PauloGitHBhttps://github.com/PauloGitHB this is probably not the best place to discuss this problem as this is not an issue concerning the parsing documentation. I would recommend to either ask on our Discord server: https://discord.gg/Gyzx3ukUw8 (recommended as I believe it's an issue with your environment and not a problem with NOMAD), or open a separate issue describing your problem, ideally with a link to a repository where you are working and a set of steps for how to reproduce your issue.
That being said, the error states that you don't have a module called 'sintering' which would either suggest that you have not installed the plugin you are developing in your environment or that said plugin doesn't include a module called 'sintering'.
—
Reply to this email directly, view it on GitHubhttps://github.com/nomad-coe/nomad/issues/86#issuecomment-2360950181, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A6D3PVQSKHNQJRXII2GPDNLZXLETHAVCNFSM6AAAAABOPZFZLGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRQHE2TAMJYGE.
You are receiving this because you were mentioned.Message ID: @.***>


Allow Nil values in Log::Context

It is often helpful to log when something is not set.
Right now that is not possible without weird workarounds like settings
nil to "". Even that doesn't always work because you may have a
complex Hash/NamedTuple where doing this is complex.
This allows setting values to nil and adds a spec to make sure it
works along with an example use case

Note: this does not allow Log::Context.set nil. So we still protect against accidental logging of just nil

Closed by #9121


Simplify initialization contexts in the AST

This PR simplifies and normalizes the handling of initialization contexts in the AST, so parameter with default arguments and initializers of non-local pattern bindings have consistent, descriptive DeclContexts. Should be NFC.

@swift-ci please smoke test and merge

Ended up having to remove an unnecessary #include in LLDB.
@swift-ci please smoke test Linux


Feature Request - Crouch Function

Presently it appears room scale crouching is supported but button crouch is not an official function.

This goes quite nicely with some other features we've been thinking of which control the players body, including:

height calibration (for tall players and people in wheel chairs)
shrinking the player height while climbing to allow for pulling the body on to the top of buildings.

@Malcolmnixon I have an alpha version of getting climbing to the top of platforms and buildings working by adding / replacing this code to the climbing function after the code where you have the average offset for left and right hands combined.  Does this approach make sense to you?
https://pastebin.com/PFT5ESrz

@Malcolmnixon is your controller suffering from drift or something else? If its broken due to drift I have found that compressed air and electronic contact cleaner (mine is CRC Mass Air Flow Sensor Cleaner) work wonders.

Could you check out the crouch functionality in the latest https://github.com/Malcolmnixon/godot-xr-tools-demo and let me know if it works for you?

This works!! Nice work! I couldn't figure how to do this no matter how hard I thought about it and tried.