[HELP] How to implementa document based RAG with VectorDB using NanoLLM?

Hey,
I'm new to NanoLLM, so please forgive me if my question seems basic. I couldn't find any discussion group for NanoLLM so I am posting my question here. In the NanoLLM documentation, I have seen that it supports RAG. But i could only see multimodal RAG for chatting from images and videos. I'm interested in using NanoLLM for context-aware document chat using VectorDB. Could anyone point me to the relevant documentation or resources for this?
Thank you!

Hi @jais001, you are correct that the NanoDB I created/integrated with NanoLLM is mostly geared for low-latency multimodal retrieval/RAG, and although I have been meaning to find the time to go back and switch out the CLIP/SigLIP model it uses for embedding cosine simllarity to text-based embedding models (like from SentenceTransformers), today you can integrate your vectorDB/RAG solution of choice.  NanoLLM exposes a Huggingface-like API for the LLM/VLA models, so you can connect it with other code and applications that you want.

p.s. here are some other text RAG examples from Jetson AI Lab that use llama-index:

https://www.jetson-ai-lab.com/tutorial_jetson-copilot.html
https://www.jetson-ai-lab.com/tutorial_llamaindex.html

There is also langchain supported in jetson-containers should you want to use langchain.


[Map] Matrix-ServerReset

This isn't a Monster Arena map, but some kind of transitional arena for voting purposes (I assume). Here's how it's author describes it (via readme):

Just a simple map I made for my server and any server admins.  It's a hallway with a kill volume, everyone dies, and then a new map can be voted into play.

Should be moved elsewhere. Afaik, there is no Monster Arena gamemode in UT2004 at all.

URL: https://unrealarchive.org/maps/unreal-tournament-2004/monster-arena/T/matrix-serverreset_f0f07703.html
Hash: f0f07703ff1646e5153cc75ff400b29e5db71836
Current name: Matrix-ServerReset

I've moved this to unknown.


UI :Add meta information in explore entity cards

Describe your changes :

I worked on the ..... because ...

Type of change :

[x] Bug fix
[x] Improvement
[x] New feature
[] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[] Documentation

Frontend Preview (Screenshots) :
For frontend related change, please link screenshots of your changes preview! Optional for backend related changes.

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers

CC: @harshach @open-metadata/ui

Closing this PR as it's already done in the main.


Support cross-file rename for clang languages

This uses the indexed rename request I added to clangd to perform global rename in clang’s language using SourceKit-LSP’s index: SourceKit-LSP’s index is used to find the locations to rename and the indexed rename request to clangd is used to translate the rename locations to edits.
rdar://118996369

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test Windows


@FannyGautierr Thanks for submitting a PR! And welcome to the community! ✨
It looks like one of these corrections is in a file we don't accept contributions to. Can you remove that one from your PR? Then I can get this triaged for review ⚡

1 typo in content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md

Thank you for your interest in improving GitHub Docs! :sparkling_heart:

I just remove the file ! Sorry about that

@FannyGautierr No worries! Thanks for the quick action ⚡
I'll get this triaged for review. 👀
In the meantime, if you'd like to find other ways to contribute, check out our help wanted section to find open issues you can work on. 👍


i18n

Create JSON files for other languages. Can use the labels from wikidata items as the basis for translations.

At least for some of the big languages, e.g. the "More than 1,000,000 articles" langauges at the bottom of https://en.wikipedia.org/wiki/Main_Page


✨ Support for NUnit 4

Description
NUnit 4 has just been released. This issue is just to make sure that we are aware of it.
Tasks

[ ] Create NUnit 4 glue library

More Information
https://docs.nunit.org/articles/nunit/release-notes/framework.html#nunit-400---november-26-2023
Thanks!

Yeah.. I know. Never thought new versions of .NET and my favorite libraries would bring me such dread. 😅
xUnit 3 should be arriving soon as well.

sorry to hear mate. I scanned a bit the changelog and there shouldn't be any change affecting auto data.

@Kralizek it only supports .NET 6 and .NET Framework 4.6.2 😶

Yup, I read it too. Is that an issue?

Don't think so, but that means it will have to be moved to v6.

Bump!

+1
Not supporting nunit 4 is starting to become problematic for my company.

Same. Need NUnit 4 support :) If there are no issues with the 4 NUnit for the current version - you could just copy paste and add another dependencies

The issue so far wasn't the compatibility of the code but the target frameworks supported by NUnit 4.
The .NET 6+ support for planned for the v6 release.
I'm considering at the moment adding all the newer .NETs 5-8 in the next release.
There will be a lot of preprocessor directives anyway, so I might as well bite the bullet.

When do you plan releasing v6?

The current preview releases don't help, in case anyone is thinking of trying those.

Good luck with the new release!

@aivascu Doesn't seem to be working for me:

[NU1608] Detected package version outside of dependency constraint: AutoFixture.NUnit3 5.0.0-preview0011 requires NUnit (>= 3.7.0 && < 4.0.0) but version NUnit 4.1.0 was resolved.

Could we reopen this issue, and only close it once its out of preview?
My company can't use preview packages, but I want to know when this is released to actual v5

@saan800 You should be able to subscribe for notifications of new releases from the home page of the repo by clicking Watch -> Custom -> Releases .
@aivascu I also wanted to chime in here to say thanks for all the effort here in this and related PRs to add more runtime targets and, of course, NUnit 4 support itself.

@saan800 I'm using the issue states to check how close the project is to a milestone, in this case v5.
As mentioned there are other ways to be notified of when a release is out. I doubt you'll miss the v5 release since your IDE will likely tell there's an update.
@stevenaw thank you, I appreciate that.
I've taken a few days off, to work on AutoFixture, next week. I appreciate that not everyone can use preview versions, so I'm trying to make time in order to complete this release.

Hello @aivascu, is there any progress on the stable version? By the way, we really appreciate your time and effort on this.

@muratguneydev yes, last month I've been able to set some time aside and the testing of the NUnit attributes rewrite is almost done, but I've been working OT since then, and didn't have time to finish it. I should have more time this month. I believe we should have a RC by end of June.

@muratguneydev yes, last month I've been able to set some time aside and the testing of the NUnit attributes rewrite is almost done, but I've been working OT since then, and didn't have time to finish it. I should have more time this month. I believe we should have a RC by end of June.

Again I'm wondering about the release date. Do you have an estimate?


RUM-483 use macos runner

What does this PR do?
Adds instrumented test support to our Gitlab CI pipeline

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

Project coverage is 69.92%. Comparing base (4a3bc9f) to head (24d3125).
Report is 4 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #2154      +/-   ##
===========================================
- Coverage    70.05%   69.92%   -0.13%
===========================================
  Files          726      726
  Lines        26995    26982      -13
  Branches      4524     4523       -1
===========================================
- Hits         18909    18865      -44
- Misses        6818     6838      +20
- Partials      1268     1279      +11

see 31 files with indirect coverage changes


PICC type: Unknown type

Step 1: Describe your environment

OS version: MacOS
Arduino IDE version: 2.0.3
MFRC522 Library version: 1.4.10
Arduino device: Uno
MFRC522 device:  0x92 = v2.0

Step 2: Describe the problem
I'm trying to use the DumpInfo example with my elevator card but terminal always outputs
Card UID: A3 AC 6D 9A
Card SAK: 19
PICC type: Unknown type

Should I try with a different code version? What could be the possibles reasons for this error code?

Should I try with a different code version?

Yes why not?

What could be the possibles reasons for this error code?

Card too new or other vendor. As alternative use NXP app from google store on your phone.


[d3d9] TrackMania United Forever: freeze after choosing a medal ghost

This issue was originally reported in #1363 by @Iglu47 and me, but as I like to keep things ordered I opened this issue specifically for it, as the original one has 41 comments and it's getting pretty messy.

confirm freeze after choosing a medal ghost
track: united => race => bayA1
i checked master-git, dxvk 1.5.1 and d9vk 0.22 version - all 3 freezes
and no freezes on default wineD3D

It freezes for me on a Nadeo bay track, with both the provided DLL and DXVK 1.5.1, just after choosing a medal ghost. But not all bay tracks are affected.

However, if the shadows are turned down to PC2, @Iglu47 says that the issue is gone:

PC2 no have this issue and freeze issue - so game still good playble

Software information
TrackMania United Forever, maximum settings.
System information
@Iglu47 system specs:

GPU: NVIDIA GTX 1080 Ti.
Driver: NVIDIA propietary driver, 440.48.2.
Wine version: Wine-TkG 5.0.r2.
DXVK version: DXVK 1.5.1-53-g38a0d2c5.

My system specs:

CPU: Intel Core i3-2100 @ 3209 MHz.
GPU: NVIDIA, MSI GeForce GTX 1650 Ventus XS.
Driver: Debian Bullseye NVIDIA propietary driver, 430.64 (package version 430.64-6).
Wine version: wine-4.21 (Debian 4.21-2).
DXVK version: 1.5.2.

Apitrace file(s)

https://drive.google.com/open?id=1G0HEoHgXPy-9fvCfNh-Z98Q1cKXFvu0- (provided by @Iglu47)

Log files

d3d9.log: https://github.com/doitsujin/dxvk/files/4109102/TmForever_d3d9.log (provided by @Iglu47)
d3d11.log: N/A.
dxgi.log: N/A.

I tried next liquorix version and arch-LTS version of kernel and found (sudo journalctl -p 3 -xb and dmesg) that "freeze" actually is nvidia Xid error 8 - "GPU stopped processing"

Can you get me an nvidia-bug-report?

i made game app to window mode and run nvidia-script after "freeze"- all in one x-session
@Joshua-Ashton nvidia-bug-report.log

The game is using swvp and triggers this validation error on nv:
VUID-VkWriteDescriptorSet-descriptorType-00332(ERROR / SPEC): msgNum: 0 - vkUpdateDescriptorSetWithTemplate() failed write update validation for VkDescriptorSet 0x2dda0000002dda[] with error: Write update to VkDescriptorSet VkDescriptorSet 0x2dda0000002dda[] allocated with VkDescriptorSetLayout VkDescriptorSetLayout 0x2ca90000002ca9[] binding #0 failed with error message: Attempted write update to buffer descriptor failed due to: VkDescriptorBufferInfo range is 164096 which is greater than this device's maxUniformBufferRange (65536). The Vulkan spec states: If descriptorType is VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER or VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMIC, the range member of each element of pBufferInfo, or the effective range if range is VK_WHOLE_SIZE, must be less than or equal to VkPhysicalDeviceLimits::maxUniformBufferRange (https://www.khronos.org/registry/vulkan/specs/1.1-extensions/html/vkspec.html#VUID-VkWriteDescriptorSet-descriptorType-00332)


API unreachable

Integration can't get any API answer for a few days now. After the latest update to v0.3.0 I checked the log:
Logger: custom_components.rki_covid
Source: helpers/update_coordinator.py:166
Integration: RKI Covid numbers (documentation, issues)
First occurred: 12:21:32 (1 occurrences)
Last logged: 12:21:32

Error fetching rki_covid data: Error communicating with API: Cannot connect to host api.corona-zahlen.org:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate (_ssl.c:1125)')]

Seems as if the used API does not provide valid certificates.

2021-01-17 14:47:55 ERROR (MainThread) [custom_components.rki_covid] Error fetching rki_covid data: Error communicating with API: Cannot connect to host api.corona-zahlen.org:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate (_ssl.c:1125)')]
Same here.

2021-01-17 14:47:55 ERROR (MainThread) [custom_components.rki_covid] Error fetching rki_covid data: Error communicating with API: Cannot connect to host api.corona-zahlen.org:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate (_ssl.c:1125)')]
Same here.

Copy that.
Error fetching rki_covid data: Error communicating with API: Cannot connect to host api.corona-zahlen.org:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate (_ssl.c:1125)')]
Discovered this when upgrading to v0.3.0.
When will the certificate(s) be fixed? Don´t want to workaround by tweaking to "allow self-signed certificates" or disabling full ssl validity check.

Copy that.
Error fetching rki_covid data: Error communicating with API: Cannot connect to host api.corona-zahlen.org:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate (_ssl.c:1125)')]
Discovered this when upgrading to v0.3.0.
When will the certificate(s) be fixed? Don´t want to workaround by tweaking to "allow self-signed certificates" or disabling full ssl validity check.

Copy that.
Error fetching rki_covid data: Error communicating with API: Cannot connect to host api.corona-zahlen.org:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate (_ssl.c:1125)')]
Discovered this when upgrading to v0.3.0.
When will the certificate(s) be fixed? Don´t want to workaround by tweaking to "allow self-signed certificates" or disabling full ssl validity check.

It seams the sever is down and not the certificate is broken. Atleast I think that.

Copy that.
Error fetching rki_covid data: Error communicating with API: Cannot connect to host api.corona-zahlen.org:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate (_ssl.c:1125)')]
Discovered this when upgrading to v0.3.0.
When will the certificate(s) be fixed? Don´t want to workaround by tweaking to "allow self-signed certificates" or disabling full ssl validity check.

It seams the sever is down and not the certificate is broken. Atleast I think that.

Too bad, wanted to add the new entities provided with 0.3.0 update. Hopefully it will be fixed soon... by the way there´ve been some outages already the days before, but I can´t provide logs for those. Anyway, current messages are quite clear.

Too bad, wanted to add the new entities provided with 0.3.0 update. Hopefully it will be fixed soon... by the way there´ve been some outages already the days before, but I can´t provide logs for those. Anyway, current messages are quite clear.

Too bad, wanted to add the new entities provided with 0.3.0 update. Hopefully it will be fixed soon... by the way there´ve been some outages already the days before, but I can´t provide logs for those. Anyway, current messages are quite clear.

Same here. I waiting setup version 0.3 too.

Too bad, wanted to add the new entities provided with 0.3.0 update. Hopefully it will be fixed soon... by the way there´ve been some outages already the days before, but I can´t provide logs for those. Anyway, current messages are quite clear.

Same here. I waiting setup version 0.3 too.

API is now up and working.

API is now up and working.

API is up and running again. Sorry for the outage, hopefully the RKI system will now stay online.

API is up and running again. Sorry for the outage, hopefully the RKI system will now stay online.


Slack::BlockKit::Element::RadioButtonGroup

Add support for Radio button group element
https://api.slack.com/reference/block-kit/block-elements#radio

Closed by #52


How to get transactionId?

How do I know which id I can identify when a transaction is executed?

Hi, sorry for the long delay.
As far as I know, TypeORM doesn't have an option to get transaction id using its API, but you can make a regular sql query to get this id.


TinyUSB are not visible in VSCode workspace

I am not able to see TinyUsb examples in workspace folder despite being installed in Program Files/PicoSDK.

Can you provide some more details? What path do you have on your system, how are you trying to view it, can you provide a screenshot of that path not being visible?
The USB-specific examples should actually be located in C:\Users\<username>\Documents\Pico-v1.5.1\pico-examples\usb, and not in the SDK. The SDK has TinyUSB as a submodule, but the code there isn't meant to be part of the official examples.

Closing as we have not heard back from the issue author.

Hello,
I have a problem and I have some questions:
can anyone help me?

I can compile pico-examples with Vscode on windows11
I can compile TinyUSB webserial examples on Ubuntu

Now I'd like to include TinyUSB in Vscode because I'd like to stay on windows 11.
here are my questions:

I'd like to modify webserial but in pico-example I can't find the sources
in C:\Users\----\Documents\Pico-v1.5.1\pico-examples\usb\device I find that dev_hid_composite and dev_lowlevel
if I go to C:\Users\----\Documents\Pico-v1.5.1\pico-examples\build\usb\device\tinyusb_device_examples\webusb_serial I find that the result of compilation

When I compile the Webserial example from TinyUSB I do make BOARD=raspberry_pi_pico LOG=2 all
How do I activate LOG=2 if I compile with Vscode pico-example? (assuming I've managed to integrate tinyusb).

Do you have a simple tree structure of a minimal project so that I can better understand?

I'm sorry but I have a lot of trouble with non-integrated development chains, there are so many make and cmake that I'm lost.
Thanks in advance

@patfrench sorry I did not see your post earlier -- you posted this on a closed issue.
Anyway, if this is still relevant:

This is explained in the pico-examples ReadMe.
You can set any variable similar to this example for PICO_BOARD.
You can go through the readmes for pico-sdk and pico-examples for help on setting up a minimal tree structure.


Rollback preview

Codecov Report
Base: 28.47% // Head: 28.47% // No change to project coverage :thumbsup:

Coverage data is based on head (590943b) compared to base (acae7de).
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #448   +/-   ##
========================================
  Coverage    28.47%   28.47%
========================================
  Files           54       54
  Lines         4942     4942
========================================
  Hits          1407     1407
  Misses        3402     3402
  Partials       133      133

Flag
Coverage Δ

unittests
28.47% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Adding a more secure default cipher

A few concerns:

I kept DefaultAESCBCCipher, but deprecated it. The intent is that users of the library now know to transition away from it, but this won't leave their dbs encrypted with this deprecated cipher unaccessible.
I left almost all of the tests using the now deprecated AESCBC; to remake these tests, the db files in src/test/resources need to be re-created.
I named the name cipher Default1Cipher to cover a few intents: Let's not hardcode implementation details that aren't particularly relevant into this name, and also we now adhere to modern java naming conventions (which dictate DefaultAesCbcCipher). The 1 in the name is to leave room for a new default which is not compatible with this one.
The IV is now randomly generated and returned as part of the ciphertext. That does mean that the transition from plaintext to ciphertext is NOT deterministic (run the same code twice in a row and different ciphertext ensues; this is more or less the point, as otherwise you could at least recognize that the same data has been encrypted with the same key!), and that requires some reworks on the test code.
The basic crypto test HAS been updated, but almost all the other tests also use crypto and need an update.

See also issue #19

CONTEXT: Not a user of jsondb but was discussing this with @yawkat on freenode ##java and wanted to investigate GCM mode.

The song and dance routine with the bytebuffers is to avoid 1 additional byte array creation whose size is related to the size of the cipher/plaintext. However, the API of the ICipher interface (turning strings into Base64 strings) is fundamentally at odds with doing this efficiently. I've decided not to refactor the API, that felt a little drastic :)
Given that performance in the face of larger texts is already hard to accomplish, perhaps it was overkill.

Thanks for doing this, I will spend some time on this over the weekend, and merge it it in.

Just wanted to update here, i do plan to review this and merge it however last several months i have been totally swamped i hope to do this sometime in October

@rzwitserloot Thank you for doing this, please accept my apologies for the delay, i have been seriously crunched these last few months.


add initialIndex

this PR adds initial index functionality by setting currentPreviewItemIndex

This also fixes an issue with Urls I noticed on iOS 16 devices and earlier.

I will make some changes and merge sometime soon


arrow key navigation is not working if search-enabled="false"

if search is enabled then you can navigate with arrow keys between the select-items, if search is disabled then arrow key navigation is not working.

+1
Looks like keyboard shortcuts (specifically handleDropDownSelection) is being bound to _searchInput.on 'keydown', and disabling the input prevents it from working.

+1

+1
Please fix this issue..

+1

Problem is not (only) the event listener but the input focus. The input focus is set to searchInput even if search is disabled. Since the input element is not available the focus goes to the body instead and shortcuts and tab order are broken.
So the input focus should be set to another element, but which one...

+1. Just spent 20 minutes head-desking over this.

+1

+1

+1

+1

+1

+1

+1

This is because the input is hided with ngHide. This is not the proper solution but a dirty fix that breaks the keyboard acces to the component.
A better solution for the Select2 theme could be to use the "minimumResultsForSearch" option that Select2 provides.

+1 to fixing this bug.


Change DeviceList repr to use correct indices

The index from enumerate won't match the actual device index if the list is filtered/reordered for whatever reason (i.e. to restrict to inputs/outputs or a specific API). This also means the default mark would be wrong. This fix uses the index in the dictionary instead.

Hello @rmccampbell! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file sounddevice.py:

Line 1835:9: E306 expected 1 blank line before a nested definition, found 0

Thanks!


Ensure release tag names are consistent within the project

Please update the latest tag name so it states: 1.2.0 so all tags are naming-consistent within the project.
Thanks

Ugh, what an annoying mistake. Sorry about that. Will fix!

I ended up making a new release: https://github.com/mattmassicotte/nsui/releases/tag/1.3.0
Does this work for you?


Tests for vehicle_rider provider and app unhealthy status

Test load and save functionality of the vehicle_rider provider
Test the HTTP app for proper unhealthy status

Excellent PR!
Thank you 👍


missing information on private link

This page neglects the fact that connections are also possible through private link.

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

ID: 07adfd46-7af7-5966-a3de-d67623f6c642
Version Independent ID: a638d2d6-5be0-7e40-70ea-dc2a3f65e649
Content: Connectivity architecture - Azure Database for PostgreSQL - Single Server
Content Source: articles/postgresql/concepts-connectivity-architecture.md
Service: postgresql
GitHub Login: @kummanish
Microsoft Alias: manishku

@pmozbert Thank you for the feedback.
This is being assigned to the content author to evaluate and update the documentation as appropriate.

When customer are using the private link the traffic from the private endpoint resource which is in the customers VNet still goes to the customer's database but via the gateway. That is why the proxy mode of operation is still valid.
Let me know if there are more questions.

I thought private link was not supposed to touch public internet.  Is the gateway using a public ip address?

Also this -

Privately access services on the Azure platform: Connect your virtual network to services in Azure without a public IP address at the source or destination.

see - https://docs.microsoft.com/en-us/azure/private-link/private-link-overview#key-benefits

Passing through gateway does not expose the traffic to public internet. The traffic from VNet to Gateway is through a dedicated channel and which is unique to the connection. No one else can access the database outside the VNet. Because the connectivity to Azure Database for MySQL needs gateway to proxy the connection, the private link traffic has to reach the gateway.
Apart from setting the private Link, you can also set Deny public network access : https://docs.microsoft.com/en-us/azure/postgresql/concepts-data-access-and-security-private-link#deny-public-access-for-azure-database-for-postgresql-single-server
which completely blocks any existing connections through firewall and vnet service endpoints.
Let me know if there are any questions.

Hi,  to confirm, with private link, the connection goes to the gateway's public IP address.  This seems to contradict this statement from the private link docs -

Privately access services on the Azure platform: Connect your virtual network to services in Azure without a public IP address at the source or destination.

I would say that the private link docs are incorrect on this point?   Do you agree?

No. Just to confirm, the traffic goes to public gateway for reaching the database. The gateway IP is not the IP of the database node. So the database is still not reachable even if you get the gateway IP which we have already publicly documented.
Its the same architecture used for Azure SQL databases and DW. As mentioned, there is no public IP that can be used to access the database server when private link is set. i.e. no firewall rules needed, no service endpoint needed.

#please-close


Add a README to Azure.Template

The existing README is a README template -- we should add one in the sdk\template directory to describe what's in Azure.Template and how to extend it to build out a service library.

Closing; Azure Template has a read me.

Reopening;  I misunderstood the proposed content.  This does not exist currently.

Given we expect all SDKs to be starting with DPG onboarding guide, do we see value in adding the following content
/cc: @jsquire , @annelo-msft

See https://github.com/Azure/azure-sdk-for-net/issues/12903#issuecomment-1599012716
I still feel it would be good to at least link to other docs from the template directory, but I'm also happy to defer to whomever feels most strongly about this.

Given some of the onboarding is aspirational at this point, let's keep this tracking for now. As we see more of it come to light we can make the call at the time.

Given where we are with onboarding experience I believe this issue can be closed. I have not seen any new SDKs being created via the template as we did earlier in quite some time.
/cc: @jsquire , @annelo-msft - if you feel strongly about it please feel free to reopen.

I'm fine with closing this if we have a good holistic solution to onboarding and a different approach works better for the e2e

I can't say whether or not the template is still being used as a reference point, but the structure is definitely still being used for new libraries.  I have no issue closing this out, however.


[gradle-plugin] Support for configuration cache

Expected Behavior
When enabling the gradle configuration cache then detekt works
org.gradle.unsafe.configuration-cache=ON
org.gradle.unsafe.configuration-cache-problems=warn

Current Behavior (using 1.10.0-RC1)
gradle fails to configure project
field 'project' from type 'io.gitlab.arturbosch.detekt.extensions.DetektReport': cannot deserialize object of type 'org.gradle.api.Project' as these are not supported with the configuration cache.
  See https://docs.gradle.org/6.5/userguide/configuration_cache.html#disallowed_types

field 'project' from type 'io.gitlab.arturbosch.detekt.extensions.DetektReports': cannot deserialize object of type 'org.gradle.api.Project' as these are not supported with the configuration cache.
  See https://docs.gradle.org/6.5/userguide/configuration_cache.html#disallowed_types

Context
Trying out the experimental configuration caching and seeing what breaks!

That's still not working properly, we have some tests on our projects for configuration-cache compatibility and I see:
task :detekt of type io.gitlab.arturbosch.detekt.Detekt: invocation of 'Task.project' at execution time is unsupported.
I'm using 1.10.0 but I see in master branch the code is still the same.
The culprit: https://github.com/detekt/detekt/blob/master/detekt-gradle-plugin/src/main/kotlin/io/gitlab/arturbosch/detekt/Detekt.kt#L192
It get's called in line 220 which is execution time.


optimization, curves, indicator animation, fixed switch disable animation

A little help to the project 😉

wow that look amazing !
Thanks I merge this, this will be part of 3.0.0
I don't know if you noticed but I added you as contributor in the readme :)

you rock :)

@florent37 Thank you for adding to the list of contributors 🚀
I plan litl fix appBar tomorrow(icons, sizes, etc.) 😉

I pushed the 3.0.0 tonight, but no worry, it'll be in 3.0.1 :D
thanks a lot for you work


Add small explanation of issues with traditional init systems in containers

Proposed changes
Adds minor paragraph with some details on why "traditional" init systems aren't ideal for using inside docker containers.
Very open to adding more detail if required/suggested!

Deploy preview for docsdocker ready!
Built with commit 5cffe4f0bffc3129639b1d70997f79f8363675d7
https://deploy-preview-9634--docsdocker.netlify.com

I think this has been inflight for long enough :joy:  Gonna close it.


Drop -Werror from compiler flags

Please consider dropping -Werror from the compiler flags. Today it's not possible to install morphio on ArchLinux which has updated GCC to 12.2.0. It seems this version of the compiler has introduced new diagnostics which are emitted when building morphio. As a result I can't install any packages that have morphio as a dependency. Unless I install a different compiler.
Suggestions:

Simply drop -Werror; and keep fixing warning as one notices them during regular development cycles.
Add a flag MORPHIO_WITH_WERROR (or similar) which defaults to Off. During CI, for selected compilers one could set the flag to On to check that morphio actually builds without warnings on those selected compilers.
Add the same flags with default Off allowing us to disable -Werror when building with say Spack.

Yup, fully agree, not sure when I'll have a moment to give this a fix; I'm tempted to turn it on automatically for Debug builds, like we do in libsonata.

what happens if you set -DMorphIO_CXX_WARNINGS=OFF: https://github.com/BlueBrain/MorphIO/blob/master/CMakeLists.txt#L9

Seems to work. I'll update the Spack recipe accordingly. Thank you!


[CT-1470] Whither UserConfig?

https://docs.getdbt.com/reference/profiles.yml#user-config
The idea in the past has been: This is tied to my specific "machine," and should hold true / set defaults for all of my dbt activity. The original options were things like: don't use colors in the terminal, don't send anonymous usage tracking, don't use partial parsing. Those aren't tied to any one dbt project in particular, and they might be different for different users — hence, why they weren't stored in the project codebase and checked into version control.
However, these configs don't really have anything to do with connection profiles / credentials. We're all about splitting up our monolithic files. And profiles.yml really deserves a bigger refresh next year (https://github.com/dbt-labs/dbt-core/issues/1958 and then some).
Questions:

Where should these "user configs" go instead? Should they be settable in dbt_project.yml? In a new root-level file that lives alongside the project? Should that file be .gitignored (a la dbt.env), or version-controlled (dbt_config.yml)?
Is the distinction between "global configs" and "project configs" really meaningful? The addition of --log-path and --target-path as CLI flag / env var overrides already blurs that boundary. That said, I don't think --model-paths should really be a thing :)

Wherever we move the UserConfig, we'll need to support it in its current location for a period of time, with a clear deprecation warning.

How would we feel about a precedence order like:

CLI flag
Env var
UserConfig, in a dedicated file, always in the root directory, optionally version controlled

Idea being:

All "global" configs can be set in dbt_project.yml, too, to set a default for everyone running this particular project. Will be overridden by the same config set at the user/machine level, env level, or invocation level
No ifs-ands-or-buts-ing about where UserConfig is located, so we can safely load it first & foremost. I don't even want to have to think about --profiles-dir or --project-dir.

This comment is my attempt to summarize my latest thinking on the next steps here. Given the last few months of Fun With Flags, I think a solid answer here could provide us with much cleaner codepaths & initialization flows going forward. As always, we should aim to provide one minor version of back-compat for existing behavior, with deprecation warnings, if we can manage it.
Big idea: "Runtime configuration" can be provided by users in one of three ways:

CLI flags
Environment variables (read from system OR defined in dbt.env file)
Long-lived configuration file

Commentary:

The precedence order is (1) CLI flag > (2) env var > (3) config file
New: Users should have the ability to define env vars in a dbt.env file

This file must be located in the root directory where dbt is running.
This file can define any & all env vars relevant to dbt. Not limited to just the env var versions of "global configs"
If the file is found, dbt should use these values and only these values to resolve all env vars. It should never read them directly from the system. (See: https://github.com/dbt-labs/dbt-core/issues/6545.)
This .env file should use standard "text" syntax, one statement per line in the style of DBT_ENV_VAR=value
It can be optionally gitignored—or version controlled, to ensure a consistent "env" for all runs
It's likely that dbt Cloud would write this file on users' behalf, and block users from defining it themselves.

New: dedicated config file. This is a way to define "global" dbt configurations. It could be saved in version control to ensure consistent default configuration. It should be yaml for starters, but there's no reason we couldn't someday also support ini, toml, json, ...

We move it out of profiles.yml, into its own dedicated file: dbt_config.yml.
The file can be located in one of two places:

(a) root directory where dbt is running - preferred if available
(b) "home" directory for this system - Path.home() - default runtime config for any/all projects running on this user's machine

Note that these are the same file locations & precedence order as profiles.yml, minus the additional option of specifying a --profiles-dir flag. We cannot locate "UserConfig" on the basis of a flag, because we need to read user configs before we can resolve flags.
If we can't find dbt_config.yml, that's fine, keep going.
If we can locate dbt_config.yml, and there's an error while reading it, it's always an error. We immediately raise the error and stop.
dbt Cloud users could define this file themselves, and store it in their project's root directory.

How would this work in a unified deployment of multiple projects? Let me think more about it :)

I wonder if we can simplify the code/configuration but just having folks move to use .env files by having more support for these. What does a .yml config give that .env doesn't?
If we do want got the route of a dbt_config file, it would probably be handy to set per stage / environment configurations. Either declaratively by supporting: prod.dbt_config.yml and local.dbt_config.yml or by allowing the stages to be specified within the file.

Thanks @colin-rogers-dbt @gshank @dbeatty10 for talking through this live during BLG!

If the file is found, dbt should use these values and only these values to resolve all env vars. It should never read them directly from the system.

Inside dbt.env, we could make this flexible with some kind of PASSENV, e.g.
PASSENV=DBT_* SPECIFIC_ENV_VAR

Or for everything:
PASSENV=*

If we do want got the route of a dbt_config file, it would probably be handy to set per stage / environment configurations.

I do want to think more about this. My initial instinct is, per-environment configuration should be solved for with environment variables (.env).
Good idea: Let's call this something like dbt_defaults.yml!

What does a .yml config give that .env doesn't?

It does allow us to:

Allow users to write yaml (the standard configuration language of dbt)
Perform additional validation on those configs
Allows us to support structured/nested configs (à la --warn-error-options), rather than needing to add an additional flag for every possible permutation

Factor III in a twelve-factor app is " Config: Store config in the environment".
One way to load environment-specific environment variables is using set -a; source .env; set +a like @RobbertDM described here.
Using direnv is another alternative to loading environment variables.
A pro of direnv is that it loads from .envrc (or optionally .env) upon entering the project directory and unloads the environment variables when leaving that directory.
The cons are that it isn't a Python program, and installation instructions are system-specific. Also, anytime there is a change to .envrc, it needs to be approved by running direnv allow.

@dbeatty10 Hah, it felt a bit controversial when I wrote it too! I'm not all the way sold on it myself.
It would be a way of "exporting" the environment into a file, and providing predictability/portability: wherever dbt runs, it uses the environment variables defined in that file, rather than the system / environment it's running in. This was a need we'd identified while working on runtimes for dbt-core in dbt Cloud: https://github.com/dbt-labs/dbt-core/issues/6545
It might be sufficient (and less controversial) for dbt.env to simply take precedence over any env vars defined in the system, rather than completely preventing access.

It might be sufficient (and less controversial) for dbt.env to simply take precedence over any env vars defined in the system, rather than completely preventing access.

➕ This makes sense to me

Recent work on dynamic profiles has exposed another problem with profile.yml and mixing runtime/project configuration: since it's a very flat spec it does not support nested/conditional configuration. The particular use case/problem is the configuration of auth methods where certain configurations only make sense with certain authentication methods (see: dbt-bigquery -> if auth_method = 'service-account-json' then user must set key_file_json otherwise it's just ignored).  This is non-intuitive to the user, and requires a lot of validation code to manage in the adapter which introduces a lot of variance in behavior (i.e. sometimes we ignore unused parameters and sometimes we don't).
All of this is to say that we might want to look at a more structured configuration format like toml or even json-schema alongside a simple .env file.

@colin-rogers-dbt That makes sense to me — though it sounds more like something we'd want to address in a (long-overdue) rework of profiles.yml, rather than a consideration for UserConfig specifically. The goal of UserConfig is really just to offer an in-file & yaml-formatted equivalent to the "global" configs that users can set via env var or by passing CLI flags. Some flags are mutually interdependent (e.g. --defer requires that --state or --defer-state is also set), but we need to have those conditional checks living inside dbt-core anyway. Let me know if I'm missing something

@jtcohen6 sorry I could have written this clearer: I meant this in a more general "flat" or unstructured configs come with significant downsides way not that we solve for profiles.yml here.

we need to have those conditional checks living inside dbt-core anyway.

Tots agree, not saying this config would replace those checks as they are currently written (we have to support them now) but that it might encourage us to structure the flags differently in the future to encourage better ergonomics and it would allow us to surface the existing complexity in a more user friendly way.
An extreme case is how spark manages it's configuration: configuration is pretty error prone as it's very easy to set conflicting flags many of which will silently change the application's behavior in unpredictable ways.

Closing this in favor of https://github.com/dbt-labs/dbt-core/issues/9183 :)


Typescript error for useTransition

I'm using React with Typescript and getting typing errors for useTransition:
const items = [{id: 1}, {id: 2}];
const transitions = useTransition(items, item => item.id, {
  from: { opacity: 0 },
  enter: { opacity: 1 },
  leave: { opacity: 0 },
})

Resulting in "Expected 1 arguments, but got 3."
I'm not sufficient enough in writing types, would be nice if someone can add them.

Dude you are on 7.x.x and trying 8.x.x example.
or
using 8.x beta where the wrong typing for 7.x was there

The typing is off, but i'm looking at these types and don't understand what i would have to change. If any of you want to submit a pr, they're super welcome!

Much appreciated @brunolemos 🙏🏻


Calculation gap

Hi gang
First of all, thanks for the amazing piece of work.
I have tried to create an excel model re-using the algorythm used to estimate the energy required and the associated Carbon footprint.
I have tried many thing but always have a delta between the website output and my excel output attached.
With the parameters below, I get 5.77 kWh in my excel vs 4.56 kWh on the website.
I have tried many times and am not able to find out why. Are there other parameters that I should factor in?
Runtime - 24
Number of cores - 12
Model - Xeon E5-2683 V4
Memory available (GB) - 64
Local server in Autria - Europe
Computing Carbon Footprint tool_0.1.xlsx

Hi @Geodouss, thanks for your patience! I'm not sure where the difference comes from without seeing your calculations, but I've redone the calculation on Excel, hope that helps!
(Note that location doesn't matter for the power usage)

Actually I missed your attachment! I've found the error: you use 10W/core while it's actually 7.5 W/core (TDP=120W, and there are 16 cores) 😃


chore: update private token box

token standards/source code changed, so recompile artifacts with latest toolchain.
another commit will update the "unbox" name to kebab case
Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge.

[ ] If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag.
[ ] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code.
[ ] Every change is related to the PR description.
[ ] I have linked this pull request to relevant issues (if any exist).

Shouldn't we also update the noir contract in the box to adopt the new standard, no just recompiling it?


Setting config.PrometheusMetrics.Enabled to true doesn't add targetPort

Versions
Chart: 2.1.0
Helm: 3.11.2
Kubernetes cluster: 1.23
Steps to reproduce
The latest version of the chart doesn't add a targetPort for both the service and deployment resources when PrometheusMetrics is enabled because the template is looking for enabled but not Enabled (which is case sensitive). The following will trigger the port to be added but of course, will fail the config parsing:
  PrometheusMetrics:
    Enabled: true
    enabled: true

Snippet of the helm diff output for the Service resource after setting enabled: true:
      - port: 4317
        targetPort: grpc
        protocol: TCP
        name: grpc
+     - port: 9090
+       targetPort: metrics
+       protocol: TCP
+       name: metrics

    selector:
      app.kubernetes.io/name: refinery
      app.kubernetes.io/instance: honeycomb-refinery

Additional context
Only workaround is to fork the Chart and fix it with on both service and deployment templates:
    {{- if .Values.config.PrometheusMetrics.Enabled }}
    - port: 9090
      targetPort: metrics
      protocol: TCP
      name: metrics

@fredsig thanks for finding this.


Answers

@sojanpr @aaustin
You may also use the framework in a demo app directly for a quick live test.

👍

permission granted to merge and deploy after testing with the server flag

👍


util/log: automatic log redaction

PR: https://github.com/cockroachdb/cockroach/pull/48051
From release notes:

Advanced troubleshooting information (such as internal details from the Go runtime) is now saved in a separate log file named <program>-stderr.xxx.log in the configured log directory.  [#48051][#48051] {% comment %}doc{% endcomment %}

Dup of https://github.com/cockroachdb/docs/issues/7866


Regenerate the SDK and recapture the session records

Hi @tonytang-microsoft-com, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (tonytang). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;


Getting Timeout in RN app with RNRF

I have this test:
it('should Login in Mexico', async () => {
        const countryBtnMx = element(by.id('COUNTRY_BTN_MX'));
        await expect(countryBtnMx).toExist();
        await countryBtnMx.tap();
    });

My environment:

Detox: 9.1.2
React Native: 0.57.7
redux: 4.0.
redux-observable: 0.18.0
rxjs: 5.5.10
react-native-router-flux: 4.0.1
Node: 10.0.0
Xcode: 9.4.1 in my house, 10.1 in office
macOS: High Sierra in my house, Mojave in office

Getting error:
Timeout - Async callback was not invoked within the 120000ms timeout specified by jest.setTimeout.
The navigation in my app is done by react-native-router-flux,  so my button dispatches an action which changes the Scene and it is then where I'm having the timeout error. If I comment the line where I change the scene, then the test successfully passes.

Use the FAQ and read about debug-synchronization.


Fix Metrics/LineLength - PARTIAL - 02

Summary
Partially Fixing Metrics/LineLength
Details

Changed only offending file in bin
Unsure if this solution would be an acceptable one, but all tests pass. Can change as needed.

Motivation and Context
Working to help solve issue 1021!
How Has This Been Tested?
bundle exec rake :+1:
Screenshots (if appropriate):
Types of changes

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

History.md has been updated. PR coming soon. (Including my other PRs)


Fix dark mode navigation bar

1st commit

Update gradle wrapper

2nd commit

Methodize a few things in ForegroundService

3rd commit

Correct some theming duplicates
Made navigation bar dark for dark mode

Can you post screenshots? Previous vs after this PR.

Can you post screenshots? Previous vs after this PR.

Update gradle wrapper

How did you update the wrapper script?

Methodize a few things in ForegroundService

IMO it's fine as it currently is, so I don't think I'll merge this commit.

Made navigation bar dark for dark mode

Actually it is dark on my device running Android 10. Seems that I have to have a closer look at this.

Update gradle wrapper

How did you update the wrapper script?
With git bash.

Methodize a few things in ForegroundService

IMO it's fine as it currently is, so I don't think I'll merge this commit.
Alright.

Made navigation bar dark for dark mode

Actually it is dark on my device running Android 10. Seems that I have to have a closer look at this.
Well ok then.

Sorry for letting you wait. On api 22 the navigation bar is currently black and with this PR it changes to white. However the icons are also white:

AFAIK the nav bar icon color cannot be changed on api 22.
I made some improvements that are working on a AOSP api 30. Can you check the latest master on your device?

@mueller-ma Installed. It now works as shown in the screenshot above. Thanks!


add backup

Signed-off-by: Cameron Wall<EMAIL_ADDRESS>Related Issue: open-cluster-management/backlog#19854
Description of Changes:
adding another namespace to inspect
What resource is being added:
Is this a Hub or Managed cluster change?:
Hub Cluster
Notes:

I like it. Two thumbs up. 👍👍


Remove Logout button from Get Started page.

Description
This PR removes the logout button from the Get Started page.
Todos

[x] Tested and working locally
[x] Code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] Code changes documented
[x] Requested review from >= 2 devs on the team (one frontend and one backend recommended)

How to test

Launch the Guardian application.
Verify that there is no Logout button on the Get Started page.

Screenshots and/or Gifs
[Insert screenshots and/or gifs showing the graphic representation of the change]
Associated MS Planner Tasks

Task Title
Task Title

Created for demonstration purposes only.


Get a non-exsits skill through api causes a java.lang.NullPointerException

In order to integrate with my own system, I directly called some apis of skill service.
When I called GET /admin/projects/movies/skills/Fake it returned an error of 500. It would be nice if it returns 404 instead.

PR: #2141

@Nomango, thank you for reporting! The fix will be in 2.5.0 release.

:+1:

@Nomango 2.5.0 release is now available and contains this fix. Thank you again for reporting!


Render pipeline topology correctly, add missing nodes

Resolves:
RHOAIENG-6319
RHOAIENG-6572
RHOAIENG-6671
Description

This PR is resolving several issues when rendering the pipeline topology. Now it can find all the edges and nodes correctly. More details will be explained in the comments below.
How Has This Been Tested?

Compare the topology with the KF UI to see if it renders the same, and make sure there are no missing nodes and edges for any pipelines.
Test Impact

Updated some jest test cases.
Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

/retest

/retest


[Release] Deploy 0.2.0

Deploy
Deploy 🛠
Related PRs

#281

Before submitting

[!Warning]
The following is allowed for review only. (No additions or modifications are permitted.)

[x] I have read the Contribution Guidelines.
[x] I agree to the Code of Conduct.

Delete main branch due to broken git tree.
Create an empty main branch, then merge PR#281.

git checkout --orphan main
git push origin

Delete main branch due to broken git tree.
Create an empty main branch, then merge PR #281.

git checkout --orphan main
git commit --allow-empty -m "init"
git merge origin/develop --allow-unrelated-histories --squash -m "[Release] Deploy 0.2.0"

Note
Merged at c5c6043

This did not allow PR of the develop branch to main, so after deleting the main branch, the following was performed:

git checkout --orphan main
git rm -r --cached .
git clean -fxd
git commit --allow-empty -m "init (#282 related)"
git merge --allow-unrelated-histories develop
git push origin

Deploy at 5a79a07945dd567692005f6b8023a44f93b4aa84


command: Add themesDir command argument to specify themes directory

Currently, I don't see a way to specify themes directory to look for, while running the hugo command. So I added this command line argument which takes the path where themes are located.
Example usage:
$ hugo server --theme=docuapi --themesDir=/Users/avi/snakes/hugo-themes
$ hugo --theme=docuapi --themesDir=/Users/avi/snakes/hugo-themes

I guess you can do
env HUGO_THEMESDIR="/my/themes/ hugo --theme=docuapi

But you are right, this should be a CLI option.

^Oh! I did not know about that option. Even Google also didn't help.
Is there any changes I need to make for this PR?


Finding Executable Path

So the executable path should be changed.
Users open the desired browser then goto edge://version/ to find the executable path.
It works regardless of windows or mac and regardless of the chromium-based browser...

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

ID: aa0e4d86-12ac-7f7e-1c06-66377987487e
Version Independent ID: 52fa943b-5a87-0d35-1d89-a2a627486061
Content: Puppeteer - Microsoft Edge Development
Content Source: microsoft-edge/puppeteer.md
Product: microsoft-edge
Technology: devtools
GitHub Login: @zoherghadyali
Microsoft Alias: zoghadya

@HansUXdev I've made a pull request with your suggestion. Thank you.
#605


WSL2 Breaks, can't start.

I previously used VMWare, so I applied:
bcdedit /create {0cb3b571-2f2e-4343-a879-d86a476d7215} /d "DebugTool" /application osloader
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} path "\EFI\Microsoft\Boot\SecConfig.efi"
bcdedit /set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215}
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO,DISABLE-VBS
bcdedit /set hypervisorlaunchtype off

But now I changed it back with:
bcdedit /set hypervisorlaunchtype auto

And it still won't run WSL 2. I even turned on all the necessary Control Panel features.

Even Sandbox works now. But WSL2 doesn't.

I don't even know how to debug it.

v

Note: Not a Kali Issue, it happens with Ubuntu too.

Just in case someone doesn't believe me:

What is your Event Viewer saying? Go to Event Viewer and look for any logs that look like they have to do with Hyper-V, Virtual Machine Platform, or WSL/lxcore.

Nevermind, I rolled back Windows, then reinstalled Update. Thanks :)


Memory leak in 0.15.

Running a minimal app created with react-native init results in a small a memory leak (just under 1MB/minute) with the app simply idling. The leak grows more substantial with additional components added.
EDIT: I should note that this leak occurred when bundled with --dev=false.

Hey @npapanastasiou, is this on iOS or Android? How did you measure the memory usage? Can you provide some data / charts?

@mkonicek It was on iOS, measured using Leaks in XCode. I'll try to dig up some charts when I have a minute.

This should be fixed in master.

Im running in a similar issue for iOS, but in dev=true. With react-native 0.16.0
Boilerplate ios.index.js

stills in .16

I can confirm that this is still happening on 0.16.0 on iOS in the simulator.

I reach GBs easily.  :(

Same problem here.

Thanks for reporting it. Asked the iOS guys on the RN team.

Tadeu Zagallo tells me the fix for this will ship in 0.17: https://github.com/facebook/react-native/issues/3953. Closint this so we don't forget to close it (don't have an easy way to automatically close all issues related to a release at once).

Here's the commit: https://github.com/facebook/react-native/commit/ea96a7edb8a17fbcc57db99217783302bb790056

I've noticed some similar memory behavior, although not as drastic, over in https://github.com/facebook/react-native/issues/4761. Not sure if it's directly related or not.
Basically, running react-native init, and then throwing a setInterval when the component mounts that does something to the state every second or so, especially if that interval involves fetch, will have a gradual rise in the memory footprint. This has been seen in 0.15 and 0.17.0-rc with dev=false

still in 0.17rc

@ajwhite same as u, I use lots of fetch in my app

@DickyT when I run it in release mode I no longer have an issue. I think it's only a problem in debug mode.


HVS 390 - FOR.A Switcher

Please add support for this switcher.

Support for the HVS-390HS would be great.
The current plugin works for ME1 but it would be great to have the ability to control ME2 and even more useful would be to have control over Event Recall

Would it be possible to implement event recall? It would be very useful


Fusion - Some small bugfixes/updates

Changelog Description
This PR solves 3 small (but irritating) bugs in the Fusion integration. Instead of making 3 PRs I made this one as they are very small fixes.

The pyside2 installation now works for all Fusion versions from 16 and up (before it could only installed for Fusion 16).
_update_tool_with_data now generates the correct workdir if the user have changed the asset type in Publisher
If footage doesn't have Frames set (eg if you add from TrayPublisher) the footage now starts at Fusions global start instead of frame 0 (This is the way Fusion would do it)

Testing notes:

Try install pyside2 from the script
Open Publisher and change the asset type of a saver
Import footage that doesn't have Frames assigned to it

Hey, I just realized you also worked on the Install PySide script fix. Great work!
Please consider this additions:

I added install_pip_package, so you can use it to install other packages too.
The script now finds macos python executable correctly.
macos requires pyside6, so this is also accounted.
Actual python home variables for all supported Fusion versions are stored in openpype.hosts.fusion.
Not a big fan of wide exceptions like this, but I also did not find a better solution. Any ideas?

https://github.com/ynput/OpenPype/compare/develop...movalex:OpenPype:enhancement/fix-fusion-pyside-installation-script

I feel this PR is ready to be merge. One last review from @BigRoy maybe?

Friendly ping for @BigRoy :D

Because we're splitting OpenPype into ayon-core and individual host addons, this PR would have to be re-created to target one of those. It's also gotten a bit stale.
We're closing it down, but we'll he happy for a new PR to ynput/ayon-fusion repository once it's up.


Dim is not Dim

Describe the bug
Testing out new Dark > Dim mode, the Dim background contrast is almost the same contrast as Dark mode.
To Reproduce
Steps to reproduce the behavior:

Compare Dark and Dim mode
Notice almost same level of contrast

Expected behavior

A more significant change compared to Dark mode, with a lighter background color, a dark gray, such as #15202b

Screenshots
Details

Platform: web
Platform version: 1.68
App version:

Additional context
The type color may also need adjustment.

Straw proposal: https://github.com/bluesky-social/social-app/pull/2966


Removed poco dependency

As introduced in this PR https://github.com/ros2/ros2/issues/867 we use the poco library for loading shared libraries dynamically at runtime. It will be nice to remove this dependency which is relatively large.
This PR removed Poco dependency in Linux, Mac and Windows.
@wjwwood what do you think?
Signed-off-by: Alejandro Hernández<EMAIL_ADDRESS>

Can we have this for ros melodic ?

Can we have this for ros melodic ?

@ahoarau That seems unlikely. It could be considered for Noetic, but it would break ABI and maybe API in melodic, which would be a deal breaker.

I'm guessing using a fork in my own workspace would require to build ros from source ?

Yes.

rcpputils PR is merged, can you review this ? @wjwwood

Linux
Linux-aarch64
macOS
Windows

Linux
Linux-aarch64
macOS
Windows


python311Packages.py-multicodec: remove pytest-runner

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 236704 run on x86_64-linux 1

28 packages built:

python310Packages.cairo-lang
python310Packages.cairo-lang.dist
python310Packages.ipfshttpclient
python310Packages.ipfshttpclient.dist
python310Packages.py-cid
python310Packages.py-cid.dist
python310Packages.py-multiaddr
python310Packages.py-multiaddr.dist
python310Packages.py-multicodec
python310Packages.py-multicodec.dist
python310Packages.pytest-cid
python310Packages.pytest-cid.dist
python310Packages.web3
python310Packages.web3.dist
python311Packages.cairo-lang
python311Packages.cairo-lang.dist
python311Packages.ipfshttpclient
python311Packages.ipfshttpclient.dist
python311Packages.py-cid
python311Packages.py-cid.dist
python311Packages.py-multiaddr
python311Packages.py-multiaddr.dist
python311Packages.py-multicodec
python311Packages.py-multicodec.dist
python311Packages.pytest-cid
python311Packages.pytest-cid.dist
python311Packages.web3
python311Packages.web3.dist


luci-app-aria2: update web_script.htm#L2

Fix issue ulr 'nil value'
Replace /usr/lib/lua/luci/view/aria2/web_script.htm#L2 with this
XHR.poll(5, '<%=luci.dispatcher.build_url("admin", "services", "aria2", "status")%>', null,

Similar change has been implemented with https://github.com/openwrt/luci/commit/a4c8c206477b1c8d4fb60dcb73d777c9c9183e81 and https://github.com/openwrt/luci/commit/909083e6733bc1796e661f68fd5aef885edd9714 .
Any way, this PR has conflicts with the current code. Closing this.


Add --map-field-case / --map-table-case option

Describe your request
This library does a great job at a one time conversion, however I would like to use it to maintain consistency within my schema.
For example, say I want to maintain pascalCase for columns, but always map them to snake.
model Account {
  id             String  @id @default(cuid())
  userId         String
  firstName      String? @map("first_name") @db.Text
}

If you run prisma-case-format nothing will change
Proposed behaviour
With the --map-field-case=snake --map-table-case=snake flags, the schema will change. Now it is checking that each column correctly maps to the desired case.
model Account {
  id             String  @id @default(cuid())
  userId         String  @map("user_id")
  firstName      String? @map("first_name") @db.Text

  @@map("account")
}

Workarounds
I tried doing two conversions, eg converting to snake and then pascal, however this created duplicate @map on each column

Hey @marklawlor , glad you found the tool useful.
Can you describe your workflow for me? How are new properties being generated, and why is it infeasible to keep them in sync by hand after the initial migration?
If I understand correctly, it sounds like you're asking for "don't bother applying conventions if the table or field already has a map annotation applied.
I'm a bit swamped at work right now, so it could be awhile before I get around to it, but if you wanted to create a PR for this, I would happily merge it in because making the tool idempotent is a reasonable idea.

Can you describe your workflow for me? How are new properties being generated, and why is it infeasible to keep them in sync by hand after the initial migration?

We would like to keep our database in snake_case and JS in camelCase/PascalCase for legacy and stylist reasons. It's not infeasible to maintain by hand, and we have been doing so for quite a while - however someone evitiable forgets to add a @map() and accidently pushes a camelCase column.
Prisma has no linting tool, so we rely on PRs to catch human error but mistakes happen. I would like to use this CLI in our CI pipeline:

On PR creation run prisma-case-format
If the CLI changes the schema we can fail the PR as a column and/or @map() value is missing.

If I understand correctly, it sounds like you're asking for "don't bother applying conventions if the table or field already has a map annotation applied.

No. I would like a flag to also apply a case convention to the @map() attribute. If a @map() is missing (and the generated column will be in the wrong case) it should add a @map() attribute OR if the @map() is incorrect, it should be updated to the correct case.

Gotcha. Thanks for correcting me there. I see now that --map-[field|table]-case= are new properties you're proposing. I had not considered using this tool as "aftermarket" CI for prisma schemas, but I see the value.
I probably have time to get around to it in the next few weeks, either when work calms down or the mood strikes.
You could use --dry-run to diff the changes against your schema, or I could add a --check or --detect-drift flag that yields a number of validations to stderr.

@marklawlor, I've pushed out<EMAIL_ADDRESS>which corresponds to this pull request.
Per your suggestion, you can get ongoing convention-drift-checking by calling
prisma-case-format \
  --file=<du jour> \
  --dry-run \
  --field-case=<du jour> \
  --table-case=<du jour> \
  --map-field-case=snake \
  --map-table-case=snake

I teed up quite a few tests to make sure everything is on the up and up, but it would be great if you could pull this beta version and run it on your setup, even just once, to see if you can spot any obvious bugs.

That works really well :+1:


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 2774 ms

Resolved: Bofrost.at performance has improved in 7d58ecd after 8 minutes.


MN-583: add method deposit.create

- What I did
Added contract method deposit.create
- How I did it

Added switch case to member Call
Extended parameters of deposit constructor
Updated corresponding calls and wallet.FindOrCreateDeposit signature
- How to verify it
Run func tests
- Description for the changelog

Codecov Report

:exclamation: No coverage uploaded for pull request base (MN-574-2@e180be5). Click here to learn what that means.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             MN-574-2      #53   +/-   ##
===========================================
  Coverage            ?   14.73%
===========================================
  Files               ?        7
  Lines               ?     1086
  Branches            ?        0
===========================================
  Hits                ?      160
  Misses              ?      913
  Partials            ?       13

Continue to review full report at Codecov.

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


Publisher: Files Drag n Drop cleanup

Brief description
Cleanup code of files widgets used in publisher.
Description
Handle moving around of items in files widget. Stack widgets in files widget to handle their size hints. Proper showing of empty widget on moving items around. Hide Drag'n'Drop label if user can't drop any.
Additional info
Files widget changed a look when have no items in. The view is painted underneath so the beackground is dark grey.
Screenshot

Testing notes:

Open TrayPublisher where files widget is available
Try to play with it to validate if reported issues that should be resolved do not happen.

Resolves https://github.com/pypeclub/OpenPype/issues/3837
Resolves https://github.com/pypeclub/OpenPype/issues/3836

It fixed those issues but there is till some confusion here:

I would expect the file dragged to the upper box to be added there, not to replace existing one?


stdenv/darwin: enable tapi support in cctools

Motivation for this change
Working towards #19906 with the overall goal of Big Sur compatibility via .tbd files.
Comes with the unfortunate downside of requiring clang_6 to build the stdenv, which increases the time required.
Tested building up to nix-build -A hello and that the bootstrap tools work with nix-build pkgs/stdenv/darwin/make-bootstrap-tools.nix -A test.
cc @matthewbauer
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I see there's a link to 1100.0.11 here https://opensource.apple.com/release/developer-tools-1131.html, while it's currently broken it seems like a good indication that apple intends to publish the sources for the new version.

I see there's a link to 1100.0.11 here https://opensource.apple.com/release/developer-tools-1131.html, while it's currently broken it seems like a good indication that apple intends to publish the sources for the new version.

I sent an email to the listed address but no reply yet.

Tests for the updated libtapi finished building, seems ok. Updated main comment.

Looks good! I think it may cause conflicts with https://github.com/NixOS/nixpkgs/pull/93596 but this one is small enough to go first.

I'm interested in advancing this as a step towards a Big Sur compatible stdenv. Is there anything I can do to help get this merged?

It looks good to me. Maybe @lnl7 could rereview though.

I noticed this was causing a large amount of extra building in stage 4 by building a full cmake. I've pushed an updated version that avoids this by reusing make in stage 4. This change now only introduces a build of libtapi in stage 1 and stage 4. I've attempted to show the changes in the history of a gist.


BGA - S2G

changed the "session leads"
changed the rapid_pretext_to_tpf to James' one

@DLBPointon can you merge Michael's pull, please, so that I can fork the proper one into S2G organisation page.. Thanks!


scope verification

a general question
https://www.googleapis.com/auth/youtube.upload
to use the scope as stated in your installation guide, we need to get application verification on the above restricted scope?
how long would that take for someone that is trying to use this package?

I got verified in 3 days.


Add model Wav2Letter

Add Documentation related to module models
Add documentation to model wav2letter
Add Unit-test to wav2-letter
Add model Wav2Letter according to its paper wav2letter
#446

As a generic reminder: Since this creates a whole new top-level folder and design (collection of models) I think it's worth pausing to make sure we're not setting us up for some hard-to-reverse decisions down the road.

As a generic reminder: Since this creates a whole new top-level folder and design (collection of models) I think it's worth pausing to make sure we're not setting us up for some hard-to-reverse decisions down the road.

Yes, we need to make sure we think the interface correctly. This provides a nice forcing function for us to do so. :)

One open point is to ensure correctness when someone suggests a new model. The tests added here are very limited, and testing that the implementation is right is not obvious.

Is there an invariant that could be verified? say the shape remains the same at each layers?

 I will try to take a look today! Did not have the time yet :/

@vincentqb Sorry for the delay, I was a bit busy.
If you could take a look I would appreciate :)


CLI option to validate existing file

Description
There's no apparent way to validate that the existing generated types in the target file match the current schema.  This is useful in a CI pipeline.
Proposal
A validation mode triggered by a --validate should do the trick.  This would change the behavior from updating the file at the output path, to validating that its contents match the output that would be generated from the current schema.  If the file doesn't exist, or if there is any difference, an error should be emitted.
Checklist

[x] I’m willing to open a PR for this (see CONTRIBUTING.md)

It's easy to get a rudimentary variant of this functionality running using the API.  I would be willing to assist with this feature, but I don't know all of the complexity involved in rolling it in to the CLI at this point.

If this is as straightforward as it seems to me, after doing my own implementation, then I'm happy to do a PR for it.  As I envision it, the --validate flag would require either:

a valid redocly.yaml (in which case all defined apis will be validated and any failure would throw an error)
the --output flag to be specified

I’d love a PR for this! @markedwards I agree with your take on this.

Thanks @drwpow, I'll open one when I get a chance.

I notice that there is a new --check flag in the latest release, which I guess is supposed to do what I describe above?  However, it does not appear to work for me.  If I do openapi-typescript --check it passes regardless of whether there is even a file in the output location.
Does this feature not work with the redocly.yaml file?

Pinging on this.  Should I open a separate issue for the --check feature apparently not working?


feat(protocol-kit): add short name for Blast Sepolia Testnet

What it solves
Adds short names for Blast Sepolia Testnet:
https://github.com/ethereum-lists/chains/blob/master/_data/chains/eip155-168587773.json

Solved in https://github.com/safe-global/safe-core-sdk/pull/752


Make tabs render as four spaces in size

Currently, both versions of lite suffer from a problem where tabs don't exactly look like tabs. In other editors, they render like they are four spaces, as seen below, but in lite, they render like they're two spaces.

I'm not sure if this is easily accomplished, but it's been something that has been quite bothersome since first using lite.
The reason I'm making this on this repository instead of the official is because this version is so much better rendering than the other one, so I'd rather have the nicer looking version have fixed tabs.

Just noticed I was using spaces still. Whoops.

Hi, @howmanysmall, you may keep the issue open. There is actually a problem in Lite and Lite XL because that the tab size is hard-coded to two spaces.
I was planning to add a feature to auto-detect the tab size or let the user choose it in the settings.

It actually was rendering correctly. I'm not sure what happened, but I'll reopen it.

I am a little bit lost now :-)
May I ask you to test a few cases to clarify the problem ?
The tests I was thinking about are:

loading a file with actual "tab" characters
loading a file with two-space indentation
loading a file with four-space indentation

In each case observe the rendering, if the tabs are converted to spaces and, when typing a new line what happens hitting the "tab" key.
You can check if the editor is using a tab or spaces by moving the cursor over the space characters. If the movement cover all the spaces with a single keypress movement it means it is a "tab".
Of course I can test all this by myself but if you don't mind doing the tests it can be helpful just to be sure we are aligned and we observe the same behavior. The tests are also meant to clarify what problem or problems we actually want to fix.

I think I have solved the problem of indentation in this branch
https://github.com/franko/lite-plugins/tree/patch-detect-indent-stat
of my lite-plugins fork.
The file is:
https://github.com/franko/lite-plugins/blob/patch-detect-indent-stat/plugins/detectindent.lua
It will correctly auto-detect the indentation type even in problematic case. It reads the whole file and finds the optimal tab size in spaces or use hard tabs.
I may close this issue if it's ok for you.

That sounds good to me. Thanks!

Cool :-)
If you want you my star the Lite XL repository. It can help increase its visibility.

Definitely for the font rendering alone, I completely switched over.


MongoDB fails to cascade save annotations in a seperate document

Resolved in
https://github.com/SWEZenith/Living-History-API/commit/3f4cd7e01520c759bf9a963de8c29fdd6e23cfbf
https://github.com/SWEZenith/Living-History-API/commit/d7a4373d81c74499fae7cb9d890a8537746a19e1
https://github.com/SWEZenith/Living-History-API/commit/1621c0be4ba3a6c7da693a9ea4edf90c33681951


add circle.yml

This branch adds a working circle.yml for CircleCI integration. @jthandy if you enable CircleCI for this repo, you'll see a check below saying all checks passed on this branch.

cc @drewbanin

I believe I've now set up the config for circleci for the dbt repo. I was able to run a build from it from within circleci and the webhooks setup within the repo seems to be good to go. I am way out of my depth in terms of exactly the details of testing implementation and so am going to pass this PR over to @drewbanin.

nice! This looks great to me. @cmcarthur does Circle infer that it should run tox? don't see where that's configured. approved

When I ran it, the tox part failed…
On August 10, 2016 at 10:25:44 AM, Drew Banin<EMAIL_ADDRESS>wrote:
nice! This looks great to me. @cmcarthur https://github.com/cmcarthur
does Circle infer that it should run tox? don't see where that's
configured. approved
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/analyst-collective/dbt/pull/96#issuecomment-238883168,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACO70WlLEhcbkTgDm1aZq5xe5hMrdVWdks5qed9ngaJpZM4Jghmc
.

@drewbanin yeah, circle infers that it should use tox because tox.ini exists.


TES ignores tesExecutor/@workdir

Describe the bug
TES ignores tesExecutor/@workdir
Steps to Reproduce
Run any task where the command script assumes a working directory. Note that the script fails because the working directory is always /.
Expected behavior
Per the spec:

The working directory that the command will be executed in.
If not defined, the system will default to the directory set by
the container image.

Additional context
This attribute has been in every version of the spec. This implementation has never referenced it.

Fixed via #281


bug: Tip probe for pipettes associated with one tip rack shows tip rack as N/A

Current behavior
If 2 pipettes are associated with one tip rack, one pipette in the tip probe flow shows tip rack as N/A
Note: The tip probe process, calibration and run is still successful.
Steps to reproduce
Upload protocol that has 2 pipettes associated with one tip rack. Go to the calibration screen and check one of the pipettes show tiprack as N/A

Expected behavior
Both pipettes should show the tip rack for tip probe

Closed by #5319


Credentials should be Credential

[Enter feedback here]
Looks like there is typo "Credentials" it should be "Credential":
$credential = Get-Credential
#Connect to Microsoft Teams
Connect-MicrosoftTeams -Credential $credential
#Connection to Skype for Business Online and import into Ps session
$session = New-CsOnlineSession -Credential $credential
Import-PsSession $session

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

ID: cd283f6e-3865-ed70-d663-cc461ee8ba57
Version Independent ID: 2450d311-fc04-d8b6-b4a2-b1890ec6fc3e
Content: Install Microsoft Teams PowerShell - Microsoft Teams
Content Source: Teams/teams-powershell-install.md
Service: msteams
GitHub Login: @brandber
Microsoft Alias: brandber

@kalalvishal Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

Thank you for raising! Resolved in PR #5616

Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


Enhancement/method annotation

close #36

Thanks for the PR @coders-kitchen, will have a look during the day!

Hey Peter LGTM just two things:

Could you rename FailsafeBreaker annotation to Failsafe. This is shorter and from my point of view fitting better. What do you think?
I created the branch release/0.6.0 can you file your PR once more against this branch? I'd like to add some more features to it before releasing the next version.

Ah, just recognized there needs to be the possibility to reference the retryPolicy as well, right?
And I still thought about the option to make it more visible what's used as Fallback in the annotation. Maybe I am wrong, but wouldn't it be possible to use functional interface?

Hi Malte,

renaming sounds reasonable. Should we keep the existing annotation for compatibility reasons with the existing semantics? Or make it now simply @Failsafe
Will do so

Sounds like a good idea to provide at least the link to the retry policy. But maybe we could move this into a separate PR? WDYT?
In regards to the Fallback, the challenge here is that the fallback method has to have the same signature as the original method call (apart from the option that we could possible pass in the original exception as well). I'm not sure if this can be solved by a functional interface.
May be we could make it more explicit by annotating the methods with FailsafeFallbackwhich carries the circuit breaker name as parameter.
Using some of the lookup mechanics of spring we could possibly remove the restriction that the fallback method has to reside within the same class. By doing so, a client could extract an interface that is implemented twice. One has the original - primary - implementation  and the second could provide the fallback.

In regards to the fallback, I would propose to move this into a own PR as an improvement. WDYT?

We could keep both and mark it as @Deprecated until version 1.0. On the other hand I think it's not too much of an effort to switch to the other annotation and I'd like to avoid to carry around the old annotation for  a long time.
Since we are merging now against feature branch, I'm fine of moving fallback handling to another PR.
The only thing to fix is the one * import.

import is resolved


turn FILAMENT_DISABLE_MATOPT off cause SSR's rendering result error

when i turn FILAMENT_DISABLE_MATOPT off in cmakelist, i got a error rendering with screen space reflection which is right when i  open FILAMENT_DISABLE_MATOPT.
FILAMENT_DISABLE_MATOPT off:

FILAMENT_DISABLE_MATOPT on:

Which backend (OpenGL, Metal, Vulkan) / platform (macOS, Windows, etc) are you using?

Which backend (OpenGL, Metal, Vulkan) / platform (macOS, Windows, etc) are you using?

OpenGL with Nvidia GTX 2600, i found it is a similar case as  issue,  scaleMatrix in light_reflections.fs cause a bad optimization by SPIR-V tool.
highp mat4 uvFromViewMatrix =
scaleMatrix(res.x, res.y) *
frameUniforms.ssrUvFromViewMatrix;

I'm going to assume this is fixed because the spirv matrix assignment issue has been fixed.


feat(raiko): enable kzg blob check

Calculating the kzg commit from input tx_data in guest code to make it part of the verification. Change seems simple enought, but 2 tricky things are involved:

Need these 2 variables to compile.

export CC=gcc
export CC_riscv32im_risc0_zkvm_elf=/opt/riscv/bin/riscv32-unknown-elf-gcc

Because the ref libs c-kzg used has no riscv abi compilation, see: https://github.com/risc0/risc0/issues/443. Also it means it needs riscv toolchain locally (the whole building can be moved into a preconfigured docker env to save some effort, but local debugging still asks the toolchain)
Can we make a copy of riscv toolchain somewhere and install (like cargo install taiko-riscv) before the compile? @johntaiko, then maybe no other repo dependency.

The other trick is renaming optimizated c-kzg to c-kzg-taiko to avoid troublesome native lib conflict. An alternative way is we managing all 3rd party libs to link to that one. Seems current approach is easier.  optimization c-kzg lib ref: https://github.com/ethereum/c-kzg-4844/compare/main...smtmfft:c-kzg-4844:for-alpha7

Looks good, indeed unfortunate of building complications.
I got it to compile with risc0, but for some reason I cannot get the SP1 guest to compile using cargo build --features sp1 anymore so haven't been able to get that working.
Looks like we need that install.sh script! So that we can install/download all the stuff necessary to build all the provers without having to read the README and following the instructions. Downloading the riscv toolchain to some folder seems easy enough. This install.sh can then also be used by the ci to set stuff up, so we can also be sure it works and keeps working,
For the building with extra options, seems like we can do that using #133 and/or using a makefile like in the zkevm circuits: https://github.com/privacy-scaling-explorations/zkevm-circuits/blob/main/Makefile so we can just do things like make risc0 and  the makefile will do everything needed to make that happen. The makefile seems like a nice to have in general to do all kind of things we will want to do in a single place so also usable by everybody (including ci).

For SP1, I need to use +nightly to avoid this error:
error[E0554]: `#![feature]` may not be used on the stable release channel
  --> /home/ubuntu/.cargo/git/checkouts/sp1-20c98843a1ffc860/12c841b/core/src/lib.rs:15:1
   |
15 | #![feature(generic_const_exprs)]
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

I did not mention that because I thought it was the common sense of building sp1 since looks irrelevant with my change, no??

Where you download the riscv toolchain? I can create a install.sh within this PR and fix CI.
Mine comes from the src code repo and need make/install which is too complex to meet this simple requirement.

run ./toolchain.sh sp1 or ./toolchain.sh ris0 before building any guests it automatically sets the right tool chain
https://github.com/taikoxyz/raiko/blob/13ca16a920a091bb38eba348e235b86baf459d0e/toolchain.sh

For SP1, I need to use +nightly to avoid this error:
error[E0554]: `#![feature]` may not be used on the stable release channel
  --> /home/ubuntu/.cargo/git/checkouts/sp1-20c98843a1ffc860/12c841b/core/src/lib.rs:15:1
   |
15 | #![feature(generic_const_exprs)]
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

I did not mention that because I thought it was the common sense of building sp1 since looks irrelevant with my change, no??

export CC=gcc
export CC_riscv32im_risc0_zkvm_elf=/opt/riscv/bin/riscv32-unknown-elf-gcc

Nice! i guess u can leave it in the comment for now, and after the Pipeline in #133 is merged I can easily add this CC flag for R0 builder.

Where you download the riscv toolchain? I can create a install.sh within this PR and fix CI. Mine comes from the src code repo and need make/install which is too complex to meet this simple requirement.

I just downloaded it and did not build it, and worked okay for me to build the risc0 guest. No need to build it I think because only the headers are used?

I've already copied the correct toolchain file from EACH repo and this script is for copy and paste them when run in different guest targets

He's talking about https://github.com/stnolting/riscv-gcc-prebuilt I think, the thing we need to download now to be able to build c-kzg.

I did not mention that because I thought it was the common sense of building sp1 since looks irrelevant with my change, no??

Yeah need to run ./toolchain.sh sp1 before it. But my problem is that the SP1 guest binary simply does not get built. The compilation is successful, the guest elf simply not generated. If you already have an ELF you might think everything is okay because it will use an old one, but I deleted my elf to make sure it got build and it doesn't get generated for me when doing cargo build --features sp1, and using cargo prove in the sp1 guest folder doesn't seem to pick up the necessary extra flags.

Yeah need to run ./toolchain.sh sp1 before it. But my problem is that the SP1 guest binary simply does not get built. The compilation is successful, but the guest elf is not generated. If you already have an ELF it might look okay because it will use the elf that already exists, but I deleted my elf to make sure it got rebuilt and it doesn't get generated for me when doing cargo build --features sp1, and using cargo prove in the sp1 guest folder doesn't seem to pick up the necessary extra flags.

I think it was sp1's issue (guess due to no_std based on the error messages), yesterday I can not compile, but today I run sp1up again & compile works. Now to compile, use
source tool-chain.sh sp1  # using `source` to keep the export

Using scripts to manage toolchain files isn't a suitable approach. If we have lots of toolchain versions, maybe we can use another approach to manage them, be like using cargo command line with toolchain flag:
cargo +nightly-xx-xx build ..

Please see https://github.com/rust-lang/rustup/issues/3546
Or, we can identify a minimal compatible version, be like some nightly-xx.

Anohter issue is that, we don't need any build features to split different targets in host, since the host is likely to need to support all targets simultaneously. And the host` is not a performance bottleneck. The features have added complexity to the coding.

BTW, perhaps we can split zkVMs and SGX into different repos.

Can we still keep a monorepo? Otherwise I think we'll directly have

raiko-libs for traits
raiko-zkvms
raiko-sgx
raiko-host

which is quite cumbersome if PRs need to cover all 4 (like a trait change)

CI passed with some modifications on scripts.

If we have lots of toolchain versions, maybe we can use another approach to manage them, be like using cargo command line with toolchain flag in Makefile as Brechtpd said:
cargo +nightly-xx-xx build ..

Please see rust-lang/rustup#3546

Ah yeah this approach seems nice and simple!

Another issue is that, we don't need any build features to split different targets in host, since the host is likely to need to support all targets simultaneously. And the host is not a performance bottleneck. The features have added complexity to the code base.

The fear was that SP1 required a very specific compiler even for the host, so if any of the other prover backends would also need a very specific compiler version to work we would be in trouble and it would not be possible to compile all of them inside a single binary. Seems like things are less finicky now (though latest SP1 again requires some unstable features I think), hopefully it remains that way.

BTW, perhaps we can split zkVMs and SGX into different repos. Each target has its own approach to build, like SP1, they have building config in the repo's root and this configuration can be used in various complex situations:

I would also prefer keeping everything in the same repo because otherwise we'll have lots of version management and multiple PRs etc... I think a bit more complex on the building side will be worth it.

Let's ensure KISS. How do you all think?

Simplicity above all. 🫡

I think @johntaiko has a good point!
Let me do this: we remove all rust-toolchain and use Makefile only be like
RISC0_TOOLCHAIN = +nightly_02_01_2024
SP1_TOOLCHAIN = +nightly_04_23_2024
SGX_TOOLCHAIN = +stable

risc0:
	@cargo $(RISC0_TOOLCHAIN) run --bin risc0-builder && cargo $(RISC0_TOOLCHAIN) build --release --features risc0

sp1:
	@cargo  $(SP1_TOOLCHAIN)  run --bin sp1-builder &&	cargo $(SP1_TOOLCHAIN)  build --release --features sp1


Please ! Could you write a demo with code. I can't understand the Storyboard Method

           self.navigationController?.hero.isEnabled = true             self.navigationController?.hero.navigationAnimationType = .selectBy(presenting:.zoom, dismissing:.zoomOut)             self.navigationController?.pushViewController(SecondViewController(), animated: true)


French/German/Spanish Translation for Weather App

Extracted string resources so it the weather apps can be used in a few different countries.
Increasing reach for this open source project.
FRENCH

GERMAN

SPAINISH

Create New Branch.
Then, add all the changes in New Branch.


folder-factory and project-factory methods stubbed out

added asset and link factories to pull info from backend API


support adding new instances

Would be nice to be able to upload new instances for dogfooding

We could even integrate GradIO: https://gradio.app/sharing-your-app/


Figure out our CDN migration move from GitHub to GitLab

Always have latest and versions in a dependent folder.

[ ] how to publish GH to GL
[x] version number v.0.9.0 for the first one.
[x] work out a versioning strategy

@SoftwareChicago can you work with @dpmesa to document how we're pulling from GitHub to GitLab? This would be helpful for @nicklucius to understand, too.
Thanks!

@SoftwareChicago @dpmesa @mario-duran any update here? Thx!

@mario-duran : please create a user called svc_gitlab_mgmt so it can be used from the build process to get the "latest" version of the CDN.


[ForwardPort] Rancher-created registry secret is missing the auth field

[ForwardPort]https://github.com/rancher/rancher/issues/19177

on master-head - latest

Create a registry secret from the UI
Inspect it via kubectl
Decode the .dockerconfigjson field - echo '' | base64 -d in kubectl in cluster
{"auths":{"index.docker.io":{"auth":"c293bXlhdjp0ZXN0","password":"password","username":"username"}}}

On upgrade from 2.3.2 to master-head

Create a registry secret from the UI in 2.3.2 rancher
Inspect it via kubectl
Decode the .dockerconfigjson field - echo '' | base64 -d in kubectl in cluster
{"auths":{"index.docker.io":{"password":"password","username":"username"}}}
Upgrade rancher to master-head
Existing registry secrets will continue to have
{"auths":{"index.docker.io":{"password":"password","username":"username"}}}
Create a new registry secret
Decode the .dockerconfigjson field - echo '' | base64 -d in kubectl in cluster
{"auths":{"index.docker.io":{"auth":"c293bXlhOnNvd215YQ==","password":"password","username":"username"}}}

Including email in the registry credentials

Create a registry secret in master-head
View in API of the secret
You can edit/create a new secret
Give in email in registries
{"email":"email","username":"sowmya","password":"password"}
Inspect it via kubectl
Decode the .dockerconfigjson field - echo '' | base64 -d in kubectl in cluster
{"auths":{"index.docker.io":{"auth":"c293bXlhOnBhc3N3b3Jk","email":"email","password":"password","username":"sowmya"}}}


OCM-3280 | fix: Updated installation document

DONE
Updated installation document to work with go1.20
VERIFICATION
Make sure rosa-cli installs on go1.20

/approve


There are no weather or location conditions for the 10K dataset.

There are no weather or location conditions for 10K datasets.
Thanks for making a good library.
By the way, about 4000 sheets of semantic segmentation dataset (10K) are not in 100K json label files.
Therefore, it is not possible to know the weather or location condition of some images in the segmentation dataset (10K).
The current segmentation dataset (10K) of BDD100K is just a segmentation dataset. There is no information about various conditions such as weather.
Is there any way to infer the weather or location condition of the segmentation dataset (10K)?
Or can I get an instance segmenation label for 100K??

Metadata for the semantic segmentation (e.g weather and time of the day) would be also extremely important for my research. Are there plans on releasing them?

See the answer here

we are revising the labels on our instance segmentation dataset.

Meanwhile a subset of the 10K dataset is already contained in the 100K label file.

It would be useful to have the Metadata information about all 10k segmentation dataset. Is there any plan by when will it be available?

We will release updated tagging annotations including those on the 10K segmentation set.