do  you know how to find code for other good solutions ?

do  you know how to find code for other good solutions ?

do you know how to find code for other good solutions ?

I guess on kaggle can be a lot of good solutions

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @tyogautomo, @whmnoe4j, @RcrdBrt, @SpivEgin, @hustle961, @exsesx, @doonnaaa, @SamGMK, @lucyxliu, @Kevinw3i, @TREVORARNOLDS, @zachary95, @mysticaltech, @cedrictahina, @AzureCloudMonk, @Inux, @AmshenShanu07, @tsubasahiroe, @jegue, @nimoxdesign, @Nehadsys, @BillyHall, @Web3Magic, @thiagodelgado111, @m-bo-one, @0xAji, @franciosi, @kamaci, @keith-gardner, @dwdcth, @luojiyin1987, @wei-shiuan-chang, @iamabdh, @Rignesh-EWW, @markdown101, @willremor, @Sudip909, @zeecares, @ghosharindam, @thejchap, @gmarko, @seanmckdev, @GhtZzzz, @ryangoree, @PiNaKa30, @Adamwojty, @hujw77, @zacharyfmarion, @yasir2000, @ben-dyer

Celestia Airdrop - Claim Your Free TIA Tokens Now!

Don't Miss Out on Your Share of 60 Million $TIA Tokens!
Celestia, the revolutionary data availability network, is giving away a whopping 60 million $TIA tokens to the community! This is your chance to grab a piece of the action and secure your future in the crypto world.
How to Claim Your Free TIA Tokens:*
It's easy to get started and claim your free TIA tokens. Follow these simple steps:

Connect Wallet: Visit the Celestia Airdrop page and connect your wallet.
Claim: Click the Claim button to receive your tokens.
Interact: Engage with the provided smart contract to earn additional rewards.

Why Wait? Start Earning Today!
With Celestia, the sky's the limit. Don't let this opportunity slip through your fingers. Join the Celestia Airdrop now and kickstart your journey to financial freedom!Osub, @agatoff, @binoculars, @krsoninikhil, @Matthewjarredondo, @CapronYoan, @daoleno, @sfyumi, @psytron, @lightclient, @lcdupree, @Patrik-Stas, @tarvos21, @blackestwhite, @drbh, @lukeramsden, @Sabnock01, @rhaoio, @considine, @m4ns0ur


[Refactor] Refactor JavaScript Code for Improved Readability and Maintainability

File Name
signup.js
Reason for Refactoring the Code
The current JavaScript code in our project needs to be refactored to enhance its readability and maintainability. This issue is opened to address the following reasons for the refactoring:

Modularity and Organization: The existing code lacks proper modularization, making it challenging to comprehend and maintain. Refactoring will divide the functionality into separate functions, leading to better code organization and readability.

Descriptive Variable Names: The current code contains variable names that are not self-explanatory, making it difficult for developers to understand the purpose of certain variables. The refactored code will use descriptive variable names, improving the code's clarity.

Named Imports: The code uses default imports for Firebase modules, which might lead to confusion when there are multiple modules being imported. By using named imports, it will be easier for developers to identify which modules are being used.

Code Reusability: The current implementation lacks code reusability, with duplicated logic for error handling and input validation. Refactoring will consolidate common functionality into separate utility functions, making the code more maintainable and reducing redundancy.

Separation of Concerns: The current code mixes event listeners and authentication logic, which can make it challenging to manage and debug. The refactored code will clearly separate the signup and Google signup functionalities, leading to better maintainability.

Password Toggle Function: The refactoring introduces a function to handle password visibility toggling, isolating this functionality and making it reusable across the application.

By addressing these points, we aim to create a cleaner, more organized, and maintainable codebase. This refactoring will not only make it easier for the current development team to work with the code but also for future developers who might join the project. aintainability. This issue is opened to address the following reasons for the refactoring:

Modularity and Organization: The existing code lacks proper modularization, making it challenging to comprehend and maintain. Refactoring will divide the functionality into separate functions, leading to better code organization and readability.

Descriptive Variable Names: The current code contains variable names that are not self-explanatory, making it difficult for developers to understand the purpose of certain variables. The refactored code will use descriptive variable names, improving the code's clarity.

Named Imports: The code uses default imports for Firebase modules, which might lead to confusion when there are multiple modules being imported. By using named imports, it will be easier for developers to identify which modules are being used.

Code Reusability: The current implementation lacks code reusability, with duplicated logic for error handling and input validation. Refactoring will consolidate common functionality into separate utility functions, making the code more maintainable and reducing redundancy.

Separation of Concerns: The current code mixes event listeners and authentication logic, which can make it challenging to manage and debug. The refactored code will clearly separate the signup and Google signup functionalities, leading to better maintainability.

Password Toggle Function: The refactoring introduces a function to handle password visibility toggling, isolating this functionality and making it reusable across the application.

By addressing these points, we aim to create a cleaner, more organized, and maintainable codebase. This refactoring will not only make it easier for the current development team to work with the code but also for future developers who might join the project.
Checklist

[X] I have checked the existing issues.
[X] I have read the Contributing Guidelines.
[X] The changes don't break the code and don't introduce new functionality.
[X] I am willing to work on this issue (optional).
[X] I am a GSSoC23 contributor.

Hey @Vaishnavi-Patil2211  Please assign me this issue


RecoverableConnectionError raised on message.ack()

Discussed on the mailing list [1][2] but raising here for visibility.
When a consumer connection to RabbitMQ is lost while an AMQP entrypoint is mid-execution, the broker reclaims the unack'd message but the worker continues. We attempt to acknowledge the message when the execution finally completes, and this raises a RecoverableConnectionError because the message's connection is closed. We naively retry on this error, but even if a new connection is established, the channel for the particular message will never recover, which ultimately results in the container dying with the RecoverableConnectionError exception.
This bug was probably introduced in 2.5.4.

Fixed in #512


ROX-13786: Use SAC search helper FilteredSearcher and associated Search and Count functions instead of Apply and ApplyCount

Description
The SAC Search helper ApplyCount function can panic in scoped context.
This change deprecates and removes this function in favour of other SAC helper utilities.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
- [ ] Evaluated and added CHANGELOG entry if required
- [ ] Determined and documented upgrade steps
- [ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
CI should be enough

/test all

/test all


weblate user on GitHub

We used the Weblate public key as an SSH deploy key for r-devel/Mac-GUI to set up pushing translations to this fork, but when trying to do the same for rpart, it turned out that a deploy key can only be used with a single repo.
So I'm creating a new machine GH user with my<EMAIL_ADDRESS>email address, which is to be migrated to a shared email group later: https://github.com/r-devel-weblate

As discussed with @mmaechler at the R Dev Day PLUS 2024, it's OK to use my personal email address as per above for the next year or so, and we will revisit it after the r-project.org email/newsletter migration.


Fix ssh url

Ssh url uses :  instead of /  after the host. The comments above the function are correct but the implementation is not

Oops, sorry for not noticing the PR. I've just fixed it with changes to tests in #3


[slice] Adding slice owners to SliceFilter

Similar to https://github.com/apache/incubator-superset/pull/4520 this PR adds owners of a slice to the SliceFilter method which ensures that owners can view the slices they own irrelevant of the permission.
Note this really is a temporary partial fix as the current DashboardFilter, DatasourceFilter, and SliceFilter do not currently correctly apply the correct permission logic, i.e., for users without all-datasource-access the filters merely check if the corresponding datasource permission is explicitly defined for their roles, however it does not take into account indirect schema access, database access etc.
to: @graceguo-supercat @jeffreythewang @michellethomas @mistercrunch @timifasubaa

The solution sounds good to me but you have a linting error.

Just wondering, is there a scenario where we want this functionality? For the dashboard case, it came up because people often created empty dashboards to which they later added charts to. If a user viewed a dashboard they owned, they would still not be able to see charts associated with datasources they don't have access to.
For charts, is there a similar scenario?

@jefferythewang we had reports of some users not being able to see the slices they created. The SliceFilter logic isn’t correct as it only checks datasource access as opposed to schema and db access as well. If a user had access to a schema the in theory could create a slice using a datasource from said schema, however the slice would be filtered out because the datasource permission didn’t exist in the FAB security model.

Ah I see. Yeah this looks good as a temporary fix.

The right solutuon is to fix the permission logic for slices and datasources. This is quite involved as it would require deprecating the slice/datasource perm field and  instead use the datasource’s db, schema, and table name for permission checking.
In the case of custom SQL it should probably pass the SQL (not unlike SQL Lab) to determine the phsycial underlying tables/views and then check their permissions. The one caveat with this is the physical datasource may be inaccessible to the user but the custom SQL is ok, i.e.,it contains only aggregations, excludes rows etc. On the otherhand one could argue that’s easy to mutate the SQL and thus one should never access a custom view based on any datasource they can’t access.

We should make sure there's no way for users to point the slice that they own to another datasource they don't have access to. I wonder if there's an endpoint out there that they could POST to and rewire their slice to another datasource...

@mistercrunch I can dig into this. I think I just need to examine where slicemodelview is called.


chore: migrate to main as the default branch in ci

Signed-off-by: gkarthiks<EMAIL_ADDRESS>This PR will make the GitHub Actions consider main as the default branch.
Ref: https://github.com/kubernetes-sigs/contributor-tweets/issues/46
/cc @chris-short

/assign
@gkarthiks Is this safe to merge or is there an order of operations we need to follow?

/assign
@gkarthiks Is this safe to merge or is there an order of operations we need to follow?

Sorry @chris-short , I was out on medical emergency.
This should be good to merge.

Sorry to hear that @gkarthiks. I hope you're on the mend. Thank you for this work.
/lgtm
/approve

Sorry to hear that @gkarthiks. I hope you're on the mend. Thank you for this work.
/lgtm /approve

Thanks Chris. Everything is getting back to normal.


Implement legacy path pattern: W3C (bibxml4)

W3C (bibxml4)

(previous location) http://xml2rfc.tools.ietf.org/public/rfc/bibxml4/
Pattern 1: http://xml2rfc.ietf.org/public/rfc/bibxml4/reference.W3C.REC-example-name-date.xml

Legacy pattern(s) to implement:

https://{hostname}/public/rfc/bibxml4/reference.W3C.REC-{example-name}-{date}.xml

We need to parse the pattern to return the appropriate BibXML content.

Path pattern that works right now: http://<IP_ADDRESS>:8000/public/rfc/bibxml4/reference.WD-SWBP-SKOS-CORE-GUIDE-20051102.xml

Updated to: /public/rfc/bibxml4/reference.W3C.WD-SWBP-SKOS-CORE-GUIDE-20051102.xml

@ronaldtse

The pattern in the description: /public/rfc/bibxml4/reference.W3C.REC-example-name-date.xml
We have this working path: /public/rfc/bibxml4/reference.W3C.WD-SWBP-SKOS-CORE-GUIDE-20051102.xml

This works because files in bibxml-data-w3c seem to be already correctly named according to legacy path convention, e.g. “WD-SWBP-SKOS-CORE-GUIDE-20051102.xml”.
I’m closing, feel free to reopen if I got it wrong.

Excellent. Thanks @strogonoff !


TDLib Fatal Error Version <IP_ADDRESS>8

I started getting this TDLib fatal error after the recent TelegramX beta update. It's showing me a Aw,Snap! error page with logs and testing utilities. I have attached a screenshot below.
I've also submitted logs via mail and @TDLib_bot but got no responce so far. Please fix it asap and do the needful. Thank you.

This was fixed in a private TDLib version. The fix will be available in the future Telegram X version with updated TDLib.

This was fixed in a private TDLib version. The fix will be available in the future Telegram X version with updated TDLib.

Any ETA of the update? I'm asking this because I'm not able to use the telegram at all due to this issue and a "Failed to fetch messages. Tap to resolve" Notification stays 24x7 in my notification panel.

@piratebazaar I can't provide ETA for Telegram X update.

Telegram X beta was updated. Please update to Telegram X <IP_ADDRESS>9.


DirectLine API

Hello,
I'm trying to create my own client. I can send messages, but as for the replies, do I have to query the server to see, if there is any incoming messages for me? Or is there another way?
Thanks

Currently we only offer the polling model. Can you submit this on our feedback page? https://feedback.botframework.com/ Thank you!


Update Azure Firewall Standard Known Issue about ICMP

The first known issue under Azure Firewall Standard (https://docs.microsoft.com/en-us/azure/firewall/overview#azure-firewall-standard-1) "Network filtering rules for non-TCP/UDP protocols (for example ICMP) don't work for Internet bound traffic" should include an additional line under Mitigation to say "Azure Firewall Premium does not suffer from this".

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

ID: 474ba3cb-afa1-4ec5-37df-6553a5523dbb
Version Independent ID: 56096558-1943-3f6b-9609-7722200272fb
Content: What is Azure Firewall?
Content Source: articles/firewall/overview.md
Service: firewall
GitHub Login: @vhorne
Microsoft Alias: victorh

Hello @chriselleman-msft
Thank you for your feedback! We will review and update as appropriate.

Hello @chriselleman-msft,
We have assigned this issue to the author to review further and take the next course of action.

added note to known issues to indicate that any issue that applies to Standard also applies to Premium.
#please-close

@chriselleman-msft doesn't the edit by @vhorne PRECISELY contradict the very point which led you to raise this issue? 🤦🏼 May I suggest you two contact each other internally via MS Teams and clear this?


compliance_tool: except KeyError when reading AASX package

fix #14

Looks good to me. Can be merged.


Problems with auto mode on player

When having the input field for the sync player set to auto. When trying to play Youtube stream link. The log only say "Error details: Unspecified error". It works when you specify that it's a stream.
Vimeo video links only works when field is set to stream but not auto or video. But it detects the video as a stream when putting it in a playlist.
The following is the logs i get when i try to put a Youtube stream into the player when it's on auto.
2021.10.04 11:48:53 Log        -  [VideoTXL:SyncPlayer] Start video load https://www.youtube.com/watch?v=h1mWb7bFjXQ

2021.10.04 11:48:53 Log        -  [VideoTXL:ScreenManager] Capture valid

2021.10.04 11:48:53 Log        -  [Video Playback] Attempting to resolve URL 'https://www.youtube.com/watch?v=h1mWb7bFjXQ'

2021.10.04 11:48:53 Log        -  NativeProcess.Start: started process id [17768]: C:/Users/MYNAME/AppData/LocalLow/VRChat
/VRChat\Tools/youtube-dl.exe (...)

2021.10.04 11:48:56 Log        -  [API] Received Message of type: friend-location received at 10/04/2021 09:48:56 UTC

2021.10.04 11:48:56 Log        -  NativeProcess.HasExited: process exited with code 0, took 2862 ms. Command line: C:/Users/Anders/AppData/LocalLow/VRChat/VRChat\Tools/youtube-dl.exe (...)

2021.10.04 11:48:56 Log        -  [Video Playback] URL 'https://www.youtube.com/watch?v=h1mWb7bFjXQ' resolved to 'https://manifest.googlevideo.com/api/manifest/hls_playlist/expire/1633362534/ei/Bs5aYeG5OIb11wLeyI2oCA/ip/<IP_ADDRESS>/id/h1mWb7bFjXQ.2/itag/95/source/yt_live_broadcast/requiressl/yes/ratebypass/yes/live/1/sgoap/gir%3Dyes%3Bitag%3D140/sgovp/gir%3Dyes%3Bitag%3D136/hls_chunk_host/rr1---sn-o5voxunx-5goe.googlevideo.com/playlist_duration/30/manifest_duration/30/vprv/1/playlist_type/DVR/initcwndbps/12610/mh/Vv/mm/44/mn/sn-o5voxunx-5goe/ms/lva/mv/m/mvi/1/pl/19/dover/11/keepalive/yes/fexp/24001373,24007246/mt/1633340672/sparams/expire,ei,ip,id,itag,source,requiressl,ratebypass,live,sgoap,sgovp,playlist_duration,manifest_duration,vprv,playlist_type/sig/AOq0QJ8wRQIhAIkA2Ss3uIm321yVh0IpHCuNoEbvHCcRbH5fsomdU6w7AiBEQPLlBZUpaHfmm9gLsFjg9VqPCvctpcsMFsFaIZY-rQ%3D%3D/lsparams/hls_chunk_host,initcwndbps,mh,mm,mn,ms,mv,mvi,pl/lsig/AG3C_xAwRQIgKIuxzS8m2b1TSp_jtQSkvZctODjm5DZnnubRo-9YUYoCIQDwOyj-rtQf0gNWyt9M20Og05jG2toP1Zblt-FRVamHWg%3D%3D/playlist/index.m3u8'

2021.10.04 11:48:56 Error      -  WindowsVideoMedia error 0x80004005 while reading https://manifest.googlevideo.com/api/manifest/hls_playlist/expire/1633362534/ei/Bs5aYeG5OIb11wLeyI2oCA/ip/<IP_ADDRESS>/id/h1mWb7bFjXQ.2/itag/95/source/yt_live_broadcast/requiressl/yes/ratebypass/yes/live/1/sgoap/gir%3Dyes%3Bitag%3D140/sgovp/gir%3Dyes%3Bitag%3D136/hls_chunk_host/rr1---sn-o5voxunx-5goe.googlevideo.com/playlist_duration/30/manifest_duration/30/vprv/1/playlist_type/DVR/initcwndbps/12610/mh/Vv/mm/44/mn/sn-o5voxunx-5goe/ms/lva/mv/m/mvi/1/pl/19/dover/11/keepalive/yes/fexp/24001373,24007246/mt/1633340672/sparams/expire,ei,ip,id,itag,source,requiressl,ratebypass,live,sgoap,sgovp,playlist_duration,manifest_duration,vprv,playlist_type/sig/AOq0QJ8wRQIhAIkA2Ss3uIm321yVh0IpHCuNoEbvHCcRbH5fsomdU6w7AiBEQPLlBZUpaHfmm9gLsFjg9VqPCvctpcsMFsFaIZY-rQ%3D%3D/lsparams/hls_chunk_host,initcwndbps,mh,mm,mn,ms,mv,mvi,pl/lsig/AG3C_xAwRQIgKIuxzS8m2b1TSp_jtQSkvZctODjm5DZnnubRo-9YUYoCIQDwOyj-rtQf0gNWyt9M20Og05jG2toP1Zblt-FRVamHWg%3D%3D/playlist/index.m3u8

Context: MFCreateSourceReaderFromURL
Error details: Unspecified error

Track types:

Thanks, didn't notice I had a couple issues opened on the repo here.
The youtube stream issue is a limitation of auto mode right now because the links can't be distinguished.  The solution will be to try and fall back to stream mode if video mode fails here.
Can you give me an example vimeo url?

As of latest release, the player will fall back to stream mode if video mode produces a specific error code, this should allow youtube live streams to load on the fallback pass when the player is in auto mode.


Fix for database name in connection details after changing database

Generates new profile ids for non purpose (dashboard/connection etc) type uris such as those for Query Editor or Edit Data. This is to allow for the code to retrieve the correct profile with the right URI such as get current connection string (which expects to look up the profile via ID alone which it is currently not possible) while also allowing for connection and dashboard uris to share the same profile with the same ID (changing the profile ID for every addition of the same connection breaks loading with the connection profile in object explorer, so they will have to remain the same).
Additionally, this makes a change to the UntitledQueryEditorInput or EditDataInput so that it will disconnect the original connection to the database (made when attempting to run a select statement or edit data on a database), as it was observed that the URI for the editor has changed from that of the initial connection, causing the entry not to be deleted from connection status manager when the editor is closed.
GIF of the fix in action:

GIF of the fix on the base server before connecting (to demonstrate that it works in that scenario):

Addresses #6406

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

8 of 9 (88.89%)  changed or added relevant lines in 5 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.001%) to 41.931%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sql/workbench/services/connection/browser/connectionActions.ts
0
1
0.0%

Files with Coverage Reduction
New Missed Lines
%

extensions/notebook/src/dialog/configurePython/configurePathPage.ts
1
57.02%

src/sql/workbench/contrib/query/browser/queryActions.ts
1
48.06%

Totals

Change from base Build<PHONE_NUMBER>:
0.001%

Covered Lines:
28829

Relevant Lines:
63840

💛  - Coveralls

Connection ID generation has been added to the scriptingUtils file in order to differentiate between the existing dashboard connection and the editor connection (they are counted separately in the connection status manager, so the ids must be different for the check to work, otherwise it's indistinguishable from the dashboard entry).

@alanrenmsft would request your review, since this change mainly applies to Query Editor area.
This is an important change to address connection reliability issues when working with azdata APIs.
It would be good to bring it in the next release.

IIUC, most of the changes are to dispose the original connection when the editor is disposed. I think the correct behavior is to dispose the connection when the event happen, so that this is done in one centralized location. The event I can think of that you should test includes: change database, change connection, save untitled to a file and save as.

@alanrenmsft The disconnect connection isn't really the main fix for the issue it's to address another issue that co-exists with this one.
The actual fix is on this line: https://github.com/microsoft/azuredatastudio/pull/22376/files#diff-ec778410f6b6fdc9a6d158980959b3478e30964e6dcad4551b09a152a635a7a8R102
The disconnect connection is meant for cleaning up a brand new connection that is created here:
when we open up an untitled SQL editor input on a non master database but does not get cleaned up once you close the editor (it closes only the editor uri, but not the initial connection), once the editor is closed, there is no need for this connection anymore, so it has to be disposed along with the editor.
If we try to disconnect the connection when we change the database (including master), we end up closing the main underlying connection by accident and aren't able to continue further


Feature : Adding FASTAPI instead of legacy flask for backend

Is your feature request related to a problem? Please describe.
flask is not ideal for implementing ML-related backends as more prominent industry-graded frameworks like FASTAPI as open source. Tensormap can be brought up to the next level using FASTAPI integration
Describe the solution you'd like

Add FASTAPI REST interface to app.py
Change endpoints using FASTAPI

Can i work on this issue?


Correction for raw affiliation Data Aware Large Scale Computing; EDF R&D; Saclay Industrial Lab for Artificial Intelligence Research

Correction needed for raw affiliation Data Aware Large Scale Computing; EDF R&D; Saclay Industrial Lab for Artificial Intelligence Research
raw_affiliation_name: Data Aware Large Scale Computing; EDF R&D; Saclay Industrial Lab for Artificial Intelligence Research
new_rors: 03wb8xz10
previous_rors: 03w007e62
works_examples: W4382630617;W4380985799
contact: da141758d328dbbe74c0d2d6ae91c5a1:a6c87ae3da7b05054495f12c037e8c @ recherche.gouv.fr

This issue was accepted and ingested by the OpenAlex team on 2024-10-09. The new affiliations should be visible within the next 7 days.


Return specified intermediate outputs

Description
We want to introduce a way of specifying exactly which variable(s) from which primitive(s) should be returned. This way we would have the ability to get multiple intermediate outputs from the pipeline without needing to return the whole context.
Possible approach
We let the user define in the Pipeline JSON which intermediate outputs he wants to see. Using that information, MLBlocks keeps track of the outputs while iterating over the primitives and returns a dictionary containing all the outputs.
The JSON could look like:
{
...
"intermediate_output":
        ["sklearn.preprocessing.MinMaxScaler#1.X",
        "keras.Sequential.LSTMTimeSeriesRegressor#1.y"]
}

Also, we might want to add a general output field to the JSON, where the user can specify what the last output of the pipeline will be and that will be returned as an array.
Then we would have the general output of the pipeline and the intermediate outputs.
@csala you already had some specifics about the implementation in mind, so please let me know what you think about it and how you would do it.

@AlexanderGeiger
I like the way to dump the intermediate outputs like this.
One question about adding a general output field to the JSON. What is the difference between "general output field" and "intermediate output"? They seem serving the same purpose. In this regard, why not just name the "intermediate_output" to "output"?

I like the approach of specifying the outputs in the JSON file, but I want to suggest a slightly different JSON structure.
The concepts would be:

An output specification is a string that follows the same pattern as the current output_ specification: {primitive-name}#{counter}.{variable-name}. However, contrary to the fit and predict output_ argument, in this case the {variable-name} part is mandatory and cannot be skipped.
Optionally, the output specification can be a list of strings instead of a string, all of them following the same specification.

Then, in the JSON I would do the following:

Add an outputs field in the JSON. This field is optional, and can be:

missing: all the outputs from the last pipeline step produce method will be taken as the default output specification, in the same order (this is the current behavior).
A string or a list: it is just the default pipeline output specification.
A dictionary: it must contain at least one entry called default. This entry will be considered the default pipeline output specification just like in the previous steps. And, a part from the default, any other named output specifications can be added.

Some examples of possible specifications:
"output": "mlprimitives.custom.timeseries_anomalies.find_anomalies#1.y"

"output": [
    "mlprimitives.custom.timeseries_anomalies.find_anomalies#1.y"
]

"output": {
    "default": "mlprimitives.custom.timeseries_anomalies.find_anomalies#1.y,
}

"output": {
    "default": "mlprimitives.custom.timeseries_anomalies.find_anomalies#1.y,
    "debug": [
        "mlprimitives.custom.timeseries_preprocessing.rolling_window_sequences#1.X",
        "mlprimitives.custom.timeseries_preprocessing.rolling_window_sequences#1.y",
        "mlprimitives.custom.timeseries_preprocessing.rolling_window_sequences#1.target_index",
        "keras.Sequential.LSTMTimeSeriesRegressor#1.y_hat",
    ]
}

Notice how the first three examples are completely equivalent, and only the last one introduces an alternative output.
Also, internally, all the three options will end up represented in the dict format, with an entry called "default".
Finally, notice how the default output is NOT included in the list of debug outputs.
Now, the behavior will be: when executing the pipeline, the output_ argument will allow the user to either specify specific outputs (like in the current behavior) or give "named outputs".
These named outputs can be "default" or any other name specified, like "debug".
And the internal behavior will be:

If no output_ is given, "default" will be used.
If a string is given, it can either be one of the named outputs ("default", "debug", etc.) or one individual output specification ("{primitive-name}#{counter}.{variable-name}").
If a list is given, each element in the list can either be a named output or an individual output specification. If named outputs are given, they will be concatenated, forming a single output specification that contains all the elements from all the named outputs, in order.

Finally, when returning, if the output specification ends up having a single element, that element will be returned alone.
If more than one element exists in the output specification, all the elements will be returned as a tuple, in the exact same order, like in any multi-output method call.
Following this specification, if a pipeline is created using the last output example above, all these calls would be valid:
# return the default output, which is the y in the last primitive
anomalies = pipeline.predict(X)
anomalies = pipeline.predict(X, output_="default")

# return ONLY the debug outputs
X, y, target_index, y_hat = pipeline.predict(X, output_="debug")

# return BOTH the default and the debug outputs
anomalies, X, y, target_index, y_hat = pipeline.predict(X, output_=["default", "debug"])

# return ONLY one variable, y_hat
y_hat = pipeline.predict(X, output_="keras.Sequential.LSTMTimeSeriesRegressor#1.y_hat")

# return the default output and also one variable
y_hat = pipeline.predict(X, output_=["default", "keras.Sequential.LSTMTimeSeriesRegressor#1.y_hat"])

On a side note, the "get the whole context" behavior from the current implementation should be kept. This means that, even though the JSON specification will always require the {variable-name}, the output_ contents can point at a particular primitive context without variable. In this case, a deep copy of that context will be returned in that place.

Here is an additional proposal on top of the previous one.
A part from specifying the outputs in the JSON file as a single string, allow them to be specified as a dictionary with two entries:

name: a final name for the output. For example, "anomalies".
variable: the output specification from above: {primitive-name}#{counter}.{variable-name}.

On top of that, add these two methods to the MLPipeline object:

get_outputs(outputs=None): Return the list of dictionaries with the specification of the outputs that will be returned. If no outputs are passed, return the default outputs. Otherwise, if some outputs specification is given, compute the outputs and return the list of their specifications.
get_output_names(outputs=None): Just like get_outputs, but return the name of each output instead of the complete specification. If an output has no name because it was a single string, return the string.

For example, if the pipeline JSON specifies:
"output": {
    "default": {
        "name": "events"
        "variable": "mlprimitives.custom.timeseries_anomalies.find_anomalies#1.y",
    },
    "debug": [
        {
            "name": "X",
            "variable": "mlprimitives.custom.timeseries_preprocessing.rolling_window_sequences#1.X",
        },
        {
            "name": "y",
            "variable": "mlprimitives.custom.timeseries_preprocessing.rolling_window_sequences#1.y",
        },
        {
            "name": "index",
            "variable: "mlprimitives.custom.timeseries_preprocessing.rolling_window_sequences#1.target_index",
        {
            "name": "y_hat",
            "variable": "keras.Sequential.LSTMTimeSeriesRegressor#1.y_hat",
        }
    ]
}

One can do:
>>> pipeline.get_outputs()
[
    {
            "name": "events"
            "variable": "mlprimitives.custom.timeseries_anomalies.find_anomalies#1.y",
    }
]
>>> pipeline.get_outputs_names()
["events"]
>>> pipeline.get_outputs(["default", "keras.Sequential.LSTMTimeSeriesRegressor#1.y_hat"])
[
    {
            "name": "events"
            "variable": "mlprimitives.custom.timeseries_anomalies.find_anomalies#1.y",
    },
    "keras.Sequential.LSTMTimeSeriesRegressor#1.y_hat"
]
>>> pipeline.get_output_names(["default", "keras.Sequential.LSTMTimeSeriesRegressor#1.y_hat"])
["anomalies", "keras.Sequential.LSTMTimeSeriesRegressor#1.y_hat"]
>>> pipeline.get_output_names(["default", "debug"])
["anomalies", "X", "y", "index", "y_hat"]

And, potentially:
>>> outputs = ["default", "debug"]
>>> output_names = pipeline.get_output_names(outputs)
>>> output_values = pipeline.predict(data, output_=outputs)
>>> output_dict = dict(zip(output_names, output_values))
>>> output_dict
{
    "anomalies": ...,
    "X": ...
    "y": ...
    ...
}


Issue #3: Try to replace homemade editor with ACE

Hi!
Currently I use php-console at work. there i've seen that you have issue in which you propose to use ACE editor instead of your internal one.
Cause I like that idea and wanted to give you something back, ill came up with this possible solution.
I've tested that code on (apache 2.2.17 with php 5.3.6 on ubuntu 11.04):

Mozilla Firefox for Ubuntu 8.0 (canonical - 1.0)
Cromium Browser (14.0.835.202 (Developer Build 103287 Linux) Ubuntu 11.04)
Opera 11.60 buiild 1185 x86_64, 2.6.38-13-generic

Hope it helps :)

Thanks, sounds great! I will try it later.

Merged, tagged 1.2.0, and added a button to copy the selection in browsers that don't allow it (Opera).


feat: previous, next buttons on docs

Changes/Additions being made
Previous and next buttons for components on docs, PostLayout and ComponentLayout
Rationale behind the change or addition
On mobile navigation was a little annoying
Quality check

[ ] Are there any erroneous console logs, debuggers or leftover code in your changes?

It builds locally and on cloudfare, on netlify its giving build errors from code that already has been removed and does not exist in the codebase anymore.


[Static graph] Changes to enable building roslyn

Things needed to build roslyn/Compilers.sln with no changes to the roslyn repo.

cc @AndyGerlicher @smera

Can you lay out what the problems were when building Roslyn that you've resolved here? That would help place the review.
The commit Read ProjectReferenceItem.Targets is not landing for me clearly. I think I understand the goal but not the implementation.

Some Roslyn projects set the Targets metadata on certain ProjectReference items. Static graph did not initially take this metadata into account, and therefore it inferred the wrong entry targets for the references which had that metadata set. So then, in addition to the .default symbol I also added .projectReferenceTargetsOrDefault and updated the target protocol to use it instead of .default.
The actual change implies remembering the project reference metadata from graph construction, so it can be read by ProjectGraph.GetTargetLists when it infers entry targets.

@livarcocc @rainersigwald responded to all feedback


fix(web/applications): fixed local env check (BOAS-257)

Describe your changes
fix to check determining if the app is running in dev mode when ENV = "local"
Issue ticket number and link
Type of change 🧩

[ ] 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)
[ ] Documentation update
[ ] Other (please explain in the description section above)

Checklist before requesting a review

[ ] I have performed a self-review of my own code
[ ] I have double checked this work does not include any hardcoded secrets or passwords
[ ] I have made corresponding changes to the documentation
[ ] I have provided details on how I have tested my code
[ ] I have referenced the ticket number above
[ ] I have provided a description of the ticket
[ ] I have included unit tests to cover any testable code changes

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


PLAY Store content rating

Will there ever be a fastlane solution for the annoying IARC content rating needed to fill for each app?
Thnkx.

Thank you.
Can you help some more and link me to instructions how include the output of fastlane env?

@prolog3001 it means you must incluce your fastlane env when posting an issue, like this https://github.com/fastlane/fastlane/issues/6982#issue-188994796

Got it! here:
🚫 fastlane environment 🚫
Stack

Key
Value

OS
10.11.6

Ruby
2.0.0

Bundler?
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
8.0

Git
git version 2.8.4 (Apple Git-73)

Installation Source
/usr/local/bin/fastlane

Host
Mac OS X 10.11.6 (15G1108)

Ruby Lib Dir
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib

OpenSSL Version
OpenSSL 0.9.8zc 19 Mar 2015

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# Customise this file, documentation can be found here:
# https://github.com/fastlane/fastlane/tree/master/fastlane/docs
# All available actions: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Actions.md
# can also be listed using the `fastlane actions` command

# Change the syntax highlighting to Ruby
# All lines starting with a # are ignored when running `fastlane`

# If you want to automatically update fastlane if a new version is available:
update_fastlane

# This is the minimum version number required.
# Update this, if you use features of a newer version
fastlane_version "1.99.0"

default_platform :android

platform :android do
  before_all do
     ICON_FOLDER = "5XXX4"
  end

 # desc "Runs all the tests"
 # lane :test do
 #   gradle(task: "test")
 # end

 # desc "Submit a new Beta Build to Crashlytics Beta"
 # lane :beta do
 #  gradle(task: "assembleRelease")
 #  crashlytics

    # sh "your_script.sh"
    # You can also use other beta testing services here
 # end

  desc "Deploy a new version to the Google Play"
  lane :deploy do
    #gradle(task: "assembleRelease")
    sh "curl -o ./metadata/android/iw-IL/images/icon.png http://pro548.s3.amazonaws.com/apps/pb/psd9/#{ICON_FOLDER}/Icon-512.png"
    #supply
    #supply --skip_upload_apk [true]
    #supply --skip_upload_metadata
    #supply --skip_upload_images
    #supply --skip_upload_screenshots
    #supply --skip_upload_apk --skip_upload_screenshots

  end

  # You can define as many lanes as you want

  after_all do |lane|
    # This block is called, only if the executed lane was successful

    # slack(
    #   message: "Successfully deployed new App Update."
    # )
  end

  error do |lane, exception|
    # slack(
    #   message: exception.message,
    #   success: false
    # )
  end
end

# More information about multiple platforms in fastlane: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Platforms.md
# All available actions: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Actions.md

# fastlane reports which actions are used
# No personal data is sent or shared. Learn more at https://github.com/fastlane/enhancer

#https://github.com/fastlane/fastlane/blob/master/supply/lib/supply/options.rb#L92

`./fastlane/Appfile`

json_key_file "./fastlane/Google Play Android Developer-8aebb2d20ebd.json"

package_name "com.digital.pbapp"

fastlane gems

Gem
Version
Update-Status

credentials_manager
0.16.2
✅ Up-To-Date

spaceship
0.37.0
✅ Up-To-Date

fastlane_core
0.55.0
✅ Up-To-Date

deliver
1.15.0
✅ Up-To-Date

snapshot
1.16.3
✅ Up-To-Date

frameit
3.0.0
✅ Up-To-Date

pem
1.4.0
✅ Up-To-Date

cert
1.4.4
✅ Up-To-Date

sigh
1.11.2
✅ Up-To-Date

produce
1.3.0
✅ Up-To-Date

gym
1.12.0
✅ Up-To-Date

pilot
1.12.0
✅ Up-To-Date

scan
0.14.1
✅ Up-To-Date

supply
0.7.1
✅ Up-To-Date

match
0.11.0
✅ Up-To-Date

screengrab
0.5.3
🚫 Update availaible

fastlane
1.108.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

highline
1.7.8

commander
4.4.0

terminal-table
1.4.5

json
1.8.3

multipart-post
2.0.0

faraday
0.9.2

faraday_middleware
0.10.0

dotenv
2.1.1

net-ssh
3.2.0

net-sftp
2.1.2

plist
3.1.0

rubyzip
1.1.7

security
0.1.3

krausefx-shenzhen
0.14.11

slack-notifier
1.5.1

i18n
0.7.0

thread_safe
0.3.5

tzinfo
1.2.2

minitest
5.9.0

activesupport
4.2.7

colored
1.2

claide
1.0.1

xcodeproj
1.2.0

rouge
1.11.1

xcpretty
0.2.4

terminal-notifier
1.6.3

addressable
2.3.8

credentials_manager
0.16.2

multi_xml
0.5.5

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20160615

http-cookie
1.0.2

faraday-cookie_jar
0.0.6

xcode-install
2.0.2

word_wrap
1.0.0

multi_json
1.12.1

babosa
1.0.2

excon
0.45.4

gh_inspector
1.0.2

fastlane_core
0.55.0

bundler
1.12.5

fastimage
1.6.8

mini_magick
4.5.1

xcpretty-travis-formatter
0.0.4

uber
0.0.15

representable
2.3.0

retriable
2.1.0

mime-types-data
3.2016.0521

mime-types
3.1

hurley
0.2

little-plugger
1.1.4

logging
2.1.0

jwt
1.5.4

memoist
0.14.0

os
0.9.6

signet
0.7.3

googleauth
0.5.1

thor
0.19.1

httpclient
2.8.0

google-api-client
0.9.11

generated on: 2016-11-14

@prolog3001 Thanks for following up. Are you using deliver? Can you share your output? For new apps you'll have to set some initial content data.

Not deliver... using "supply" for Play Store.

@prolog3001 Thanks for following up. If this is possible to add we'd love to see a PR. Let me know if you are interested!


Django 2.0 compatibility

Based on #310, supports User.is_anonymous as both a method or attribute (Django 1.10+).

I mistakenly set out to write a similar pull request this morning without checking if one had already been written. My updates were similar but less thorough and somewhat less robust. Looks great to me!


Bump uc.micro module.

The module has been re-licensed from WTFPL to MIT.

Hey @wgrzelak 👋 Thanks for taking the time to open a PR, however I'm going to close this in favour of #9484 as that also brings our server-side markdown-it version in line with Ghost-Admin's current markdown-it version.


list index out of range when comparing more than 2 dataframes

Current Behaviour
The following example is from the docs (modified a bit for testing against my files):
from ydata_profiling import ProfileReport, compare

train_df = pd.read_excel("datasets/Train.xlsx")
train_report = ProfileReport(train_df, title="Train")

test_df = pd.read_excel("datasets/Test.xlsx")
test_report = ProfileReport(test_df, title="Test")

validation_df = pd.read_excel("datasets/Test.xlsx")
validation_report = ProfileReport(validation_df, title="Valid")

comparison_report = compare([train_report, validation_report, test_report])

# Obtain merged statistics
statistics = comparison_report.get_description()

# Save report to file
comparison_report.to_notebook_iframe()
# comparison_report.to_file("reports/comparison.html")

Expected Behaviour
To Generate a comparison report
Data Description
Files:
Test.xlsx
Train.xlsx
Code that reproduces the bug
Tried Both:

comparison_report.to_notebook_iframe()
# comparison_report.to_file("reports/comparison.html")

Throws:
```py
IndexError                                Traceback (most recent call last)
Cell In[42], line 19
     16 statistics = comparison_report.get_description()
     18 # Save report to file
---> 19 comparison_report.to_notebook_iframe()
     20 # comparison_report.to_file("reports/comparison.html")

.venv/lib/python3.11/site-packages/ydata_profiling/profile_report.py:526, in ProfileReport.to_notebook_iframe(self)
    524 with warnings.catch_warnings():
    525     warnings.simplefilter("ignore")
--> 526     display(get_notebook_iframe(self.config, self))

.venv/lib/python3.11/site-packages/ydata_profiling/report/presentation/flavours/widget/notebook.py:75, in get_notebook_iframe(config, profile)
     73     output = get_notebook_iframe_src(config, profile)
     74 elif attribute == IframeAttribute.srcdoc:
---> 75     output = get_notebook_iframe_srcdoc(config, profile)
     76 else:
     77     raise ValueError(
     78         f'Iframe Attribute can be "src" or "srcdoc" (current: {attribute}).'
     79     )

.venv/lib/python3.11/site-packages/ydata_profiling/report/presentation/flavours/widget/notebook.py:29, in get_notebook_iframe_srcdoc(config, profile)
     27 width = config.notebook.iframe.width
     28 height = config.notebook.iframe.height
...
     89             alpha=0.6,
     90         )
     92     if date:

IndexError: list index out of range

pandas-profiling version --> (ydata-profiling version)
v4.10.0
Dependencies
python = "~3.11"
blackcellmagic = "^0.0.3"
ruff = "^0.6.1"
ydata-profiling = "^4.10.0"
numpy = "2.0.1"
openpyxl = "^3.1.5"

OS
WSL Ubuntu
Checklist

[X] There is not yet another bug report for this issue in the issue tracker
[X] The problem is reproducible from this bug report. This guide can help to craft a minimal bug report.
[X] The issue has not been resolved by the entries listed under Common Issues.

Hi @alikleit ,
as mentioned in the docs Note (end of the page) , the compare functionality only ensure the report comparison for 2 datasets.
Meaning that only the statistics are calculated whenever 3 datasets are provided. The html functionality might work, but not guaranteed. Iframe won't work.
My suggestion is to either leverage the statistics calculated or change the code to compare 2 datasets at a time.
Any other questions let us know.


[BEAM-12456] Parallel querying in JdbcIO

Design docs can be found here: https://docs.google.com/document/d/1wBzVhQEhTK23ALzTSZ_CVouEOXTm3w2-LjmO3ieUvFc/edit
The proposed solution provides an extension for JdbcIO. This extension for JdbcIO supports parallel loading from JDBC sources with a query splitting mechanism. The user needs to specify a field for splitting the query, the range for values in this field, and the degree of parallelism. JdbcIO opens multiple connections to the database using split queries.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

@aromanenko-dev Could you please review this PR?

Run Java PreCommit

Also, checkstyle task  fails, ptal:
Execution failed for task ':sdks:java:io:jdbc:checkstyleMain'.

Run Java PreCommit

Run Java PreCommit

@aromanenko-dev CHANGES.md and commit message are updated


Fix metrics reporting to account for different types of hooks

Many kinds of hooks can run inside pre-commit, not just pre-commit hooks. We use several of them. Metrics should have distinct namespaces. Now they do.

I don't think it's worth keeping parity with existing metrics -- it's only been ~a week.


SOME/IP Specification Cleanup

The following change is a reboot of the SOME/IP specifications in an attempt to drastically simplify to show how we map up-l1 messages to SOME/IP messages and uSubscription messages to SOME/IP-SD messages.  the older specifications had a lot of uProtocol version 1.3.6 concepts (cloudevents) that were rather complicating the situation.
#93

Closing so we can use #165 instead


Adding SplashScreen

Have you read the Contributing Guidelines on Pull Requests?
YES
Description
Added Modern Splash Screen Feature in Algo-Phantoms Android.

Added 2 Photos for logo and background
Added New Bold Text
Added New Splashscreen.kt file
Changes in SplashScreen.xml file, Strings.xml file, themes.xml
Added dimes folder for setting dimensions.
Added SplashScreen to AndroidManifest.

These all things added and changes only for Modern Splash Screen Feature. Everything is working fine.
Note : Please set Android Version: 10
Appetize.io | App Review

Smartphone Info
Android Version

OnePlus 7
Android 10

Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.

Related Issues or Pull Requests
#11

@dheerajkotwani @tarun26091999 Sir, can you Please review my PR.

@Shreyash41 add the screenshot for the Splash Screen you have made.

@dheerajkotwani Sir, Please Review my PR. I have added the screenshot of Splash Screen.

@carotkut94 @dheerajkotwani Thanks sir for your time. I have resolved conflicts and Added a new Screenshot to compare New with Old. Please review my PR.


hummingbot.org - Limited Strategies Displayed in What strategies can you build with Hummingbot

URL: https://hummingbot.org/#what-strategies-can-you-build-with-hummingbot
limited display of strategies, contrary to the expected behavior.
Steps to Reproduce:

Go to https://hummingbot.org/#what-strategies-can-you-build-with-hummingbot
Review the strategies available as promoted to create by botcamp

Expected Behavior:
Upon entering the What strategies can you build with Hummingbot?, I anticipated seeing a variety of strategies available for Botcamp. The expected outcome was to have multiple strategies displayed for users to explore.
Actual Behavior:
only one YouTube video was shown in this section, making it not possible to access and check other strategies.
Screenshots/Additional Information:

Updated


Update Readme to reflect the current stage of the project and new Contribution model

I'm submitting a feature request.
What feature do you recommend to add?
Update the readme as the original readme was referring to the project as experiment. Also the way to contribute has changed.
What is the value of this feature?
Create a better experience for new team members in understanding the project and contributing to it.
Solution (or options to fix the bug)
Update readme with the following:

[ ] Replace Project Goals with Project description as it's now ready;
[ ] How to Install and Run the Project;
[ ] How to Use the Project;
[ ] How to Contribute to the Project (Collaboration: Working In a Forked Repository is now change and we need to update it: explain that we have two main branches - for staging and prod, and we create PR towards staging);
[ ] Update About section for the repo on top right - it's no longer an experiment;

Trello card

 [DEV]: Update Readme to reflect the current stage of the project and new contribution model


The intrins of the RGB camera of the L515

Hello, thank you for your dataset, it's great! Could you please tell me how to obtain the intrinsic parameters of the RGB camera in L515? I need to align the RGB images with the point cloud from the dataset and apply color to the point cloud.

I've found that this problem can be solved by running some calibration algorithm codes. Wondering are there other solutions？


Added Hero Notification Box

Ticket
Ticket Link
What is changed / added

Built the hero notification box, added styling for the notification box

Screenshots

@NerajM I noticed that you didn't include any types for your components. ALthough this component is not very complicated, we would like to have clear type annotations for the component itself (ie. the FC type) and also an interface for the props.

 Hero notification box

Only some tiny issues. Rmb to merge master 😃


[BUG]some bugs about mt.split

Describe the bug
I find mt.split does not work well when i try to use mt.unique and mt.split to group a sorted array.
I find two bugs:

mt.split does not support tuple and array as the first argument. Could you consider supporting this for convenience of usage? See below:

>>> mt.split((1,1,1,2,2,3), (3,5))

~/anaconda3/lib/python3.7/site-packages/mars/tensor/base/split.py in split(ary, indices_or_sections, axis)
    199
    200     """
--> 201     return _split(ary, indices_or_sections, axis=axis, is_split=True)

~/anaconda3/lib/python3.7/site-packages/mars/tensor/base/split.py in _split(a, indices_or_sections, axis, is_split)
    127
    128 def _split(a, indices_or_sections, axis=0, is_split=False):
--> 129     op = TensorSplit(axis=axis, dtype=a.dtype)
    130     return op(a, indices_or_sections, is_split=is_split)
    131

AttributeError: 'list' object has no attribute 'dtype'

>>> mt.split([1,1,1,2,2,3], (3,5))

~/anaconda3/lib/python3.7/site-packages/mars/tensor/base/split.py in split(ary, indices_or_sections, axis)
    199
    200     """
--> 201     return _split(ary, indices_or_sections, axis=axis, is_split=True)

~/anaconda3/lib/python3.7/site-packages/mars/tensor/base/split.py in _split(a, indices_or_sections, axis, is_split)
    127
    128 def _split(a, indices_or_sections, axis=0, is_split=False):
--> 129     op = TensorSplit(axis=axis, dtype=a.dtype)
    130     return op(a, indices_or_sections, is_split=is_split)
    131

AttributeError: 'tuple' object has no attribute 'dtype'

this one seems weird. I obtain the index from mt.unique with a sorted array and argument return_index True. When I passed the executed result of a slice of this index as the second arguments of mt.split, the returned sub-tensors all have nan shape and i cannot execute the sub-tensor to get the value. If i passed list, tuple or a mt.array with literal list, mt.split works well. See below for details:

In [67]: p = (1,1,1,2,2,3)

In [68]: unique, index = mt.unique(p, return_index=True)

In [69]: index.execute()
Out[69]: array([0, 3, 5])

In [70]: index1 = index[1:].execute()

In [71]: index1
Out[71]: array([3, 5])

In [72]: mt.split(mt.array(p), index1)
Out[72]:
(Tensor <op=TensorSplit, shape=(nan,), key=61fbfb5330abb901e5b56269d6fbad5f,
 Tensor <op=TensorSplit, shape=(nan,), key=f3a4dc180f9350bb7ac5ffcb18abd297,
 Tensor <op=TensorSplit, shape=(nan,), key=65fadafe692317ee6ba59630753cafb5)

In [73]: mt.split(mt.array(p), mt.array((3,5)))
Out[73]:
(Tensor <op=TensorSplit, shape=(3,), key=6f04c920a336bb8ae733b50c91da57ba,
 Tensor <op=TensorSplit, shape=(2,), key=11ef35d05602119da39c0924a6787245,
 Tensor <op=TensorSplit, shape=(1,), key=dd1c7e9460185aef0991c5cfa8e77823)

Thank you for your report, we will reproduce the error and fix it ASAP.

I am fixing the first bug, i will issue a PR later

Resolve the first feature in #1507

I find that the shapes of the tensors returned from mt.unique are all (nan,). This may cause the second bug. The nan shape is reasonable since you cannot infer the shape before execution.
In [98]: unique, index, counts = mt.unique((1,1,1,2,2,3), return_index=True, return_counts=True)

In [99]: unique.shape
Out[99]: (nan,)

In [100]: index.shape
Out[100]: (nan,)

In [101]: counts.shape
Out[101]: (nan,)

In [103]: index[1:].shape
Out[103]: (nan,)

In [104]: index[1:].execute().shape
Out[104]: (2,)

However, this cannot explain why the codes fails when i pass a executed tensor with (2,) shape.

Yes, mt.unique cannot decide the shape before execution.
For mt.split, if indices_or_sections is a tensor, we do not decide the shape as well,  actually, we did not check if it's executed or not. Maybe just pass  index.to_numpy() instead of passing a tensor?

Yes, mt.unique cannot decide the shape before execution.
For mt.split, if indices_or_sections is a tensor, we do not decide the shape as well, actually, we did not check if it's executed or not. Maybe just pass index.to_numpy() instead of passing a tensor?

OK, i passed index.to_numpy() and it works. Thanks a lot for your kind support!:heart:


[Bug]: Error when using anonymized_telemetry with PersistentClient

What happened?
Initializing a client with PersistentClient throws an error if the Settings(anonymized_telemetry=False) is passed in.
Maybe a different way is needed for that option?
import chromadb
from chromadb.config import Settings

chroma_client = chromadb.PersistentClient(Settings(anonymized_telemetry=False))

Also, it's not very clear from the docs how you pass in the Settings() and other args as path.
Error:
Traceback (most recent call last):
  File "edited", line 79, in <module>
    main(user_query)
  File "edited", line 33, in main
    collection = init_db(COLLECTION_NAME, embedder, CHROMA_PATH)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "edited", line 108, in init_db
    chroma_client = chromadb.PersistentClient(Settings(anonymized_telemetry=False))
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "edited /anaconda3/envs/torch/lib/python3.12/site-packages/chromadb/__init__.py", line 146, in PersistentClient
    return ClientCreator(tenant=tenant, database=database, settings=settings)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "edited /anaconda3/envs/torch/lib/python3.12/site-packages/chromadb/api/client.py", line 139, in __init__
    super().__init__(settings=settings)
  File "edited /anaconda3/envs/torch/lib/python3.12/site-packages/chromadb/api/client.py", line 43, in __init__
    SharedSystemClient._create_system_if_not_exists(self._identifier, settings)
  File "edited /anaconda3/envs/torch/lib/python3.12/site-packages/chromadb/api/client.py", line 49, in _create_system_if_not_exists
    if identifier not in cls._identifer_to_system:
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: unhashable type: 'Settings'

Versions
python 3.12
chroma 0.5.0
Relevant log output
No response

@onel, thanks for raising this. The issue you're facing is that PersistentClient takes positional arguments path, settings, tenant,database. So, in your case, Chroma tries to interpret the Settings you pass it as path.
https://github.com/chroma-core/chroma/blob/f8bc50a46162390d466281528d085c7303c0d219/chromadb/__init__.py#L123-L128
To resolve just add named param:
chroma_client = chromadb.PersistentClient(settings=Settings(anonymized_telemetry=False))

Ohhh, that makes perfect sense. Thank you.
Do we want to add that to the docs? I can help with a PR if needed.

Ohhh, that makes perfect sense. Thank you. Do we want to add that to the docs? I can help with a PR if needed.

Docs should be updated, indeed. Let me do that today unless you feel like you want to partake and update those yourself. This is the file - https://github.com/chroma-core/chroma/blob/main/docs/docs.trychroma.com/pages/reference/py-client.md

I think that file explains the arguments pretty well. If only I found it beforehand.
I was thinking more of this file which is more popular:
https://github.com/chroma-core/chroma/blob/main/docs/docs.trychroma.com/pages/telemetry.md
I'll make a PR today with an example for PersistentClient


tracking multiple clicks/hovers/events

You can have the track.php script return a 404. The browser won't cache the response and attempt to get it again on the next event.

@notVitaliy Seems its not posible to fetch URL(X) each time on focus in single session.
Im write some code (at https://github.com/Bogdaan/spycss-demo), and try almost all HTTP/1.1 codes.
Browser always cache first response in single session. Only after page refresh it can be downloaded again.


feat(api): add register static method #28

Alaska Airlines Pull Request
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Resolves: #28
Summary:

Update dependency versions
AuroDrawer.register is to easily register the element without extra importing
import "@aurodesignsystem/auro-drawer" will still register this element to
import { AuroDrawer } from '../src/auro-drawer wont register this element until AuroDrawer.register gets called
typo fix on doc clement -> element
bug fix on doc to open the proper drawer with custom-drawer example

Type of change:
Please delete options that are not relevant.

[x] New capability
[x] Revision of an existing capability
[ ] Infrastructure change (automation, etc.)
[ ] Other (please elaborate)

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team
Summary by Sourcery
Add a static method 'AuroDrawer.register' to facilitate manual registration of the 'auro-drawer' element, update dependencies, and correct documentation errors.
New Features:

Introduce a static method 'AuroDrawer.register' to allow manual registration of the custom element with a specified name.

Bug Fixes:

Correct documentation to open the proper drawer with the 'custom-drawer' example.

Enhancements:

Update dependency versions to the latest available.

Documentation:

Fix a typo in the documentation, changing 'clement' to 'element'.
Update documentation to reflect the new 'AuroDrawer.register' method for registering custom elements.

:tada: This PR is included in version 2.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update searching-in-forks.md

Anny1730/doc

Why:
Closes [issue link]

What's being changed:

Check off the following:

[x] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

Anny1730/doc
Why:
Closes [issue link]
What's being changed:
Check off the following:

[x]  I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[x]  For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ]  This pull request impacts the contribution experience

[ ]  I have added the 'writer impact' label
[ ]  I have added a description and/or a video demo of the changes below (e.g. a "before and after video")


Added Min Max values to Resizable component

#2 #3 #4

fork now only contains npm package content.


Set up CI tests

Set up GitHub Actions to run package tests (specs) upon every commit.

Note: Running CI after every commit is not possible (as of 2021-02-21, see the GitHub Actions reference). Running after every push (and pull request) seems to be the best alternative. This shouldn't be much of an issue.


Rebuild images regulary for uptodate GeoIP and better security

Hi,
first of all I love this project! It gives me a good confidential overview who is connected.
One point that annoys me sometimes, the GeoIP Database does not seem to be uptodate after some time (obviously).
Is there a chance that the images can be rebuilt like once a week?
watchtower can then update the image e.g. (specific to my setup).
BR
Alex

Also the security aspect is interesting:


Debug Readout throws exceptions in Main Menu

The debug readout throws exceptions while in the main menu after quitting a game, although they won't be visible until joining a new game.
Steps:

Join a game and enable debug readout.
Exit game to main menu.
Join another game without closing the actual program.
Note the exception spam fading out on the left.

Fixed in 55e6b21


Bindings for UProceduralMeshComponent not generated

Following the steps on macOS using the NimTemplate for UE 5.2 and for some reason bindings for UProceduralMeshComponent never get generated. I tried running ./nue genbindingsall and ./nue gencppbindings manually yet still no bindings for that component are generated. I'm not sure if there are any other pieces of the Unreal API that aren't generated. I haven't been able to test if the component is generated on Windows.

The template is not updated yet. So you will need to git pull origin devel the plugin. But this should be fixed now, thanks for reporting it. Indeed there was a MacOs specific issue. I didnt specifically generate the bindings for UProceduralMeshComponent (is it in GeometryScript?) but whatever plugin you are using, if it's activated it should generate the bindings for it.
Remember the bindings are store in src/nimforue/unreal/bindings


Release version 0.4.0

@akmorrow13 @jpdna Anything you need before I cut a release?

not from me

Nothing from me either thanks @heuermh !


issue #1602 - initial commit of helm chart

Introduces a helm chart for the IBM FHIR Server under /charts.
Also introduces a github action for publishing the updated chart on our Releases tab

This uses @helm/chart-releaser-action to turn your GitHub project into a self-hosted Helm chart repo. It does this by checking each chart in your project, and whenever there's a new chart version, creates a corresponding GitHub release named for the chart version, adds Helm chart artifacts to the release, and creates or updates an index.yaml file with metadata about those releases, which is then hosted on GitHub Pages

The chart uses helm hooks to execute the ibmcom/ibm-fhir-schematool image to create and update a database schema prior to deploying the updated application.
TODOs

Make it work with Db2

Signed-off-by: Lee Surprenant<EMAIL_ADDRESS>

After discussing this with Paul and others, we've decided that it makes more sense to keep this helm chart out of this repo for now (so that it can be released on a separate cadence without polluting our Releases tab).  Thus we have created a new repository under the Alvearie project and I've moved the content of this pull request to https://github.com/Alvearie/alvearie-helm/pull/1


clone! macro makes error messages cryptic

Hello,
when using the clone! macro rustc doesn't report the line where the errror occured correctly and instead just points to the entire macro invocation. This forces users of the macro to guess where the error occured, which isn't trivial when the function clone! encapsulates is longer than a few lines.
E.g. when I forget to put a semicolon somewhere the error message looks like this:
error: expected one of `.`, `;`, `?`, or an operator, found `self_`
   --> src/widgets/sync_list_box.rs:133:40
    |
133 |                   .connect_row_activated(clone!(@weak obj => move |list_box, row| {
    |  ________________________________________^
134 | |                     let self_ = imp::HealthSyncListBox::from_instance(&obj);
135 | |                     if (row == &self_.google_fit_start_sync_row.get()) {
136 | |                         self_.google_fit_stack.set_visible(true);
...   |
180 | |                     }
181 | |                 }));
    | |__________________^ expected one of `.`, `;`, `?`, or an operator
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to previous error

So I have to check some 50 lines to know where I forgot the semicolon.
See https://github.com/Cogitri/clone-reproducer for a reproducer:
error[E0599]: no method named `qiut` found for struct `gtk4::Application` in the current scope
   --> src/bin/entry_completion.rs:101:9
    |
101 | /         glib::clone!(@weak application => move |_action, _parameter| {
102 | |             application.qiut();
103 | |         }),
    | |__________^ method not found in `gtk4::Application`
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

In this case the error message seems OK because it's only a one line function, but ideally it'd point to only line 102 and not 101/103.

This looks like the clone! macro doesn't handle spans correctly.

@GuillaumeGomez Any guesses?

Not that I can see right away but I might have an idea if this is the proc-macro version.
@Cogitri Which version of glib-macro are you using? (the one from the repository I assume but just to be sure...)

The issue is with the proc-macro version yes

To be exact, only this code is needed:
let application = Application::new(
    Some("whatever"),
    Default::default(),
)
.expect("Initialization failed...");
let quit = SimpleAction::new("quit", None);
quit.connect_activate(
    glib::clone!(@weak application => move |_action, _parameter| {
        application.qiut();
    }),
);

And considering it's a span emitted on the code generated by the proc macro, I didn't find any way to be able to provide a better one. If someone has an idea?

@antoyo suggested a way to fix this. I'll give it a try.


security.acme doesn't work nicely with acme-dns provider

Describe the bug
Disclaimer: This is probably more of a lego issue/inconsistency, but due to some opinionated choices in the ACME NixOS module system it makes it hard to use this provider in NixOS.
I switched a few services over to use the NixOS ACME system. I use acme-dns to answer to DNS-01 challenges. Lego docs: https://go-acme.github.io/lego/dns/acme-dns/.
lego is configured with ACME_DNS_API_BASE and ACME_DNS_STORAGE_PATH. The latter already points to a file path containing secrets, so ACME_DNS_STORAGE_PATH_FILE probably allows specifying a path to a file which contains a path, which contains the secrets :shrug: .
This means, I cannot use our credentialFiles machinery to expose the file with the secrets, as it only allows configuring credentialFiles.*_FILE variables.
We should probably check back with upstream. I feel like ACME_DNS_STORAGE_PATH should just be deprecated in favor of ACME_DNS_STORAGE_FILE (which then doesn't do any indirections).
It seems unlikely someone is using ACME_DNS_STORAGE_FILE with its current behaviour.
As an alternative, we could extend the module system to allow ACME_DNS_STORAGE_PATH the same way we allow *_FILE, but it feels like an ugly hack, and I'd prefer fixing this upstream.
I currently manually set systemd.services."mydomain.example".serviceConfig.LoadCredential and systemd.services."mydomain.example".environment.ACME_DNS_{STORAGE_PATH,API_BASE} to get that behaviour.
Let me know what you think, I might be up to sending a PR upstream.
Notify maintainers
@NixOS/acme
Add a :+1: reaction to issues you find important.

Just commenting to say I have seen this and I agree it is a problem. I too would like to PR upstream if someone doesn't beat me to it (spoiler: I won't be quick :melting_face: ). Infact, I have a couple of ideas I want to try and PR upstream to simplify things on our end, so this might be a good motive to get into it.


Support sub-routes

When transitioning between pages in Hydrogen, an RSC request is sent to the server. Depending on what data requests are necessary, the transition can be noticeably slow while waiting for the RSC response. If Hydrogen supported sub-routes, on each RSC request, we should be able to determine what requests are necessary to re-run.
Consider a simplified PDP page:

When this page is directly loaded (or hard refreshed), data needs to be fetched for the header as well as the product information. If the user clicks the link for "Freestyle Collection", currently the RSC request will re-fetch everything for a new page render. We can 1) cache those request results and 2) try to optimize the RSC response to the browser. But it would be ideal if the RSC endpoint can be smart and know that the header did not change at all. This would be possible if the product details are in a sub-route, and as long as the destination route is a sibling sub-route.
Questions

The server is stateless between requests. Everything is "refetched" to potentially setup parent contexts above the sub-route. The client could send up state for each RSC request, but will that be sufficient to render all sub-routes?
How do we render a sub-route on the server independent of the default App tree?
How do we inject into the client sub-route RSC response?
a. We would need to make sure the RSC response supports both nested and base route changes
An alternative to sub-routes might be providing an "app shell" outside the router that doesn't get re-rendered on each RSC request. So if you want global data for the app that is fetched once, put it there. This might be a good approach because we can put restrictions on what data can be provided (use server context under the hood) and we serialize that data back and forth.

@wizardlyhel came up with a brilliant idea for sub-routes, partial refetching in RSC, and an option for continuing to use the new Remixed React Router (WIP). Here's my attempt at writing it down!
tl;dr - lean into Remix's pattern of "layout routes" to create multiple server component entrypoints for a Hydrogen app
Here's how this could work in Hydrogen:
Components
src
├── App.server.jsx # equivalent to Remix's `root`
└── routes
    ├── product.server.jsx
    ├── collection.server.jsx

Pretty much the same as today, except App.server is a layout which is persisted in the client (more on that later), and each individual route is rendered as a separate tree based on the incoming RSC request.
If devs have different "areas" of a site, they could even provide other layouts:
src
├── App.server.jsx # equivalent to Remix's `root`
└── routes
    ├── product.server.jsx
    ├── collection.server.jsx
    ├── __featured.server.jsx
    ├── __featured/thing.server.jsx

Where __featured is a new layout component, etc.
To make this work, we convert App.server (and any other layout components) to render the equivalent of RR's <Outlet> component:
export default function App() {
  // Layout stuff here. Fetch data if you want!
  return (
    <Layout>
      <Outlet />
    </Layout>
  );
}

Next, as part of our dev/build process, we generate a manifest which contains a map of all the file routes and their relationships, including a parentId for each component (leading up to the root App.server):

You can inspect this by visiting https://remix.run/docs/en/v1 and typing __remixManifest into your console
The client
Today, our entry-client looks a lot like this:
function ClientApp() {
  // makes a fetch request to the RSC endpoint
  const response = useServerResponse(serverState);

  return (
    <Suspense>
      {response.readRoot()}
    </Suspense>
  );
}

With this new proposal, the client would be much more aware of the app structure than it is today. We provide our entry-client with the manifest generated in the last step, and construct a virtual route tree based on the current pathname:
function ClientApp() {
  // This is generated programmatically. This is only a visual representation
  // of what is inferred based on parsing the manifest.
  return (
    <>
      <Suspense>
        <Content route="App.server">
          <Suspense>
            <Content route="product.server">
          </Suspense>
        </Content>
      </Suspense>
    </>
  );
}

function Content({route}) {
  // makes a fetch request to the RSC endpoint
  const response = useServerResponse({...serverState, route});

  return (
    <Suspense>
      {response.readRoot()}
    </Suspense>
  );
}

Note: this is a bit contrived, because we couldn't simply pass children to layout components due to the way of loading them as an RSC component stream. Instead, we'd leverage something like Context to pass the child values to the corresponding <Outlet> component.
Speaking of which: this is where (Remixed) React Router comes in! RR is perfectly set up to be used on the client:

Native <Outlet> support
You can use lazy-loaded components with Suspense boundaries
You can use fancy loader, transition and actions as needed

This effectively accomplishes what this issue aims for: a true sub-route experience, where the outer layouts stay rendered while the contents inside transitions as the RSC request changes.
The RSC server
Since we're passing route as a param from the client, our entry-server can reference the correct server component (based on import glob) and render it 🎉
The SSR server
SSR emulates what entry-client does by resolving the correct routes and building the virtual route tree. It creates multiple RSC readable streams and pipes them into an SSR HTML output.
Potential issues:

Server context: What happens if you render server context in a layout component and expect to be able to use it in a server component downstream? It isn't rendered in the app tree — is that a deal breaker?
Re-rendering layout components: It's possible you're using request data to render a specific layout. This approach falls short, because the layout isn't re-rendered with each request. This is how Remix behaves today. Is that OK?

Regarding the issues:

Server context: I think that this constraint makes sense. It's similar to remix as well. A nested route cannot access data from the parent route through useLoaderData(). I spoke to them about this, and it's necessary so that they can run the loaders in parallel without dependencies (no waterfall). I think we can make the similar tradeoff and educate on it.
Re-rendering layout components: This is a central feature of a nested router, and I think is also as expected.
No more component-based routes: This is the biggest downside, which might not be that bad. The main usecase we had for component routes was A/B testing and i18n. But I'm willing to bet that we can still do those things with the file-based approach. It might be a bit more complicated, but still doable. Maybe let's think through it though?

I bet we might be able to make that work @frandiox, but I think there's still some value in being explicit, especially when there get to be many routes. Is this also an area where being opinionated where convention over configuration is okay?

tl;dr - lean into Remix's pattern of "layout routes" to create multiple server component entrypoints for a Hydrogen app

You can use lazy-loaded components with Suspense boundaries

Chiming in to say this sounds AWESOME. We've done some looking into Remix as a option and loved some of what they were doing. Being able to incrementally adopt they're routing where it makes sense would be a huge win. 🚀

You can use lazy-loaded components with Suspense boundaries
You can use fancy loader, transition and actions as needed

Wouldn't infinite scrolling of product lists be a great application of this? Would love to make that pagination super easy style super easy and performant. So many UX considerations to make it good -- URL param updating, scroll position restoration, memory management with virtualized lists, intersection observer, skeleton components, etc.


How do you use the get_transcript method?

I don't see any useful documentation or examples for get_transcript. The one example in the original PR used a very long param and I can't find anything similar from the next or player methods. Where did it come from? And what about varying languages? Please explain, thank you.

Hi @Etorix0005, thanks for opening this issue. I admit that documentation is definitely somewhat lacking for this library unfortunately, however I'm more than happy to help explain how to use this endpoint. I'll whip up a quick demo now :)

I've created an example script to demo how to fetch the transcript for a video - https://github.com/tombulled/innertube/blob/c50bf67ff4e33e131530503df5f6bc3ce7f1c0ca/examples/get-video-transcript.py
Hope that helps!
In terms of fetching the transcript in different languages, I haven't looked into this, but I expect this should be achievable using a combination of the next and get_transcript endpoints :slightly_smiling_face:

I've created an example script to demo how to fetch the transcript for a video...

Thanks! I could have sworn I searched the next data for "Transcript" and came up empty but perhaps I didn't check any videos that had transcripts available. This is very helpful.

In terms of fetching the transcript in different languages, I haven't looked into this, but I expect this should be achievable using a combination of the next and get_transcript endpoints 🙂

Understood. I'll play around with it sometime soon and see if I can figure it out. Thanks again.


Starting new project as Postgresql

I have created the new project and tried to run mypy inside django container. I got error with database (set up as Postgresql) and CELERY_URL
File "/app/config/settings/base.py", line 48, in
DATABASES = {"default": env.db("DATABASE_URL")}
File "/app/config/settings/base.py", line 281, in
CELERY_BROKER_URL = env("CELERY_BROKER_URL")
I have fixed to add to base.py
DATABASES = {
"default": {
"ENGINE": "django.db.backends.postgresql",
"NAME": env("POSTGRES_DB"),
"USER": env("POSTGRES_USER"),
"PASSWORD": env("POSTGRES_PASSWORD"),
"HOST": env("POSTGRES_HOST"),
"PORT": env("POSTGRES_PORT"),
},
}
and to .envs/.local/.django
CELERY_BROKER_URL=redis://redis:6379/0
This fixed. Dunno if this is a bug or I missconfigured something.

Can you please paste the command you ran and the whole stack trace, as it's hard to help you without it.

For this one I runned this mypy comic_life_online  ...

Ok, and what did you do before running mypy? There are several ways of accessing a container...

git init
pre-commit install
git add .
git commit -m "first awesome commit"
git remote add origin git@github.com:lvalics/comic_life_online
git push -u origin master
docker compose -f docker-compose.local.yml build
docker compose -f docker-compose.local.yml up -d
inside the docker
mypy comic_life_online

And how did you do "inside the docker"? docker run or docker exec?

I think it's the same issue as https://github.com/cookiecutter/cookiecutter-django/issues/3224
This is a known limitation: https://cookiecutter-django.readthedocs.io/en/latest/developing-locally-docker.html#execute-management-commands


add_peer function mismatched with handle_other callback

I just noticed the message sent from Membrane.RTC.Engine.add_peer/3 does not match its handle_other callback. It looks as if the function expects a peer_id and some metadata, whereas the callback expects a Peer struct.

I'm not sure which one is preferable, which is why I'm filing the issue rather than a pull request.

Thanks. I have created PR with fix. After API changes, now we expect Peer struct.


when actionView is resizing, the editor text can be selected.

Describe the bug
as the titile said.
To Reproduce
Steps to reproduce the behavior:

open a file
drag the resize button
pull down your mouse, then you have a chance to select some texts from the editor

Expected behavior

no text is allowed to be selected during this process.

Screenshots

ancient issue.


Replace Apiary with SwaggerHub

Most of the references to Apiary are no longer valid. Where possible, they are replaced with references to SwaggerHub, or using neutral "API Design Platform" term.
Some parts like "complete development" need full rewrite as they are referring to additional deprecated tools and technologies (like Mashery).

@Amzani @jerzyn I've reflected some comments. Please keep in mind this is "remove Apiary" --NOT-- "fix everything in guidelines" Pull Request 💃 🙌


How long will it take for getting account been approved?

 Because some people said that they haven't get the account approved from several months ago. Thank you very much!

It definitely didn't take me several months. Maybe a couple of weeks or so? Just to be clear, I don't have any special contact or affiliation with the Human3.6M team, so I went through the same process as everyone else.

Thank you very much! I will wait patiently^_^

@Ixiaohuihuihui Have you received this dataset? I just have not get the account verified from several months ago.

@Ixiaohuihuihui Have you received this dataset? I just have not get the account verified from several months ago.

Yes, I have.

@Ixiaohuihuihui Have you received this dataset? I just have not get the account verified from several months ago.

Did you get approved ?


Network connection array limited by shell exec buffer of 2 MB

Describe the bug
Hello, and thank you for developing systeminformation.  One of my users discovered that on servers with a large number of concurrent open network connections (10K+), systeminformation fails to enumerate them.  We believe the culprit is this hard-coded 2 MB limit when you shell out to netstat here:
https://github.com/sebhildebrandt/systeminformation/blob/master/lib/network.js#L719
exec(cmd, { maxBuffer: 1024 * 2000 }, function (error, stdout) {

And here:
https://github.com/sebhildebrandt/systeminformation/blob/master/lib/network.js#L810
exec(cmd, { maxBuffer: 1024 * 2000 }, function (error, stdout) {

Would it be possible to increase this arbitrary byte limit, possibly to 20MB, or even make it configurable?
Thank you for an awesome module!
To Reproduce
Steps to reproduce the behavior:

Run systeminformation on a server with 10K+ concurrent network connections

Current Output
The array returned from si.networkConnections(cb) is empty.
Expected behavior
The array should contain all the open network connections.
Environment (please complete the following information):

systeminformation package version: 4.0.10
OS: Linux
Hardware: Unknown

Additional context
Reference issue: https://github.com/jhuckaby/performa-satellite/issues/1
cc @asyslinux

@jhuckaby : Yes, I will do this ... please wait a second

@jhuckaby Done ... version 4.12.0 just released

Fastest issue fix EVER.  Thank you!!!


Logs are not visible in log cache for a docker image deployed to kind

Upstream bug: https://github.com/cloudfoundry/cf-for-k8s/issues/157

Duplicate of https://github.com/cloudfoundry/cf-k8s-logging/issues/18, will be fixed in upcoming 0.2.0 release.


Add use of MutationObserver to fix issues with new Google Calendar UI

This commit introduces the use of MutationObserver in order to address issues with Google's new Calendar UI.
MutationObserver observes for changes in the DOM and with this it's possible to apply the disable scroll function each time there is a relevant event change (e.g. changing month, week, calendar format, create a new event).

How to try version #10 ? The one I tried was released by hamen as zip file :
google-calendar-scroll-disabler#9.zip

Download my revised code from here https://github.com/apphancer/google-calendar-scroll-disabler
And install the extension locally

apphancer : v0.3 is working for me. It look that you have your new version ;-)
Congratulations & thanks for your efforts.

Thanks for your feedback @DavGoodvibes
I have made a further commit where I have removed the jQuery library and changed 2 lines in content.js file lines to use VanillaJS


Can Arbitrary be biased?

I have a question that might be clarified in the documentation. Is Arbitrary supposed to be exactly uniformly distributed? Or is it supposed to be quick? For example, I can generate a number between 0 and 10 by dividing the value of a u8 by 26. With extra computations, the distribution could be made uniform, but is that necessary or desirable?

Arbitrary is not an RNG, so I don't think it makes much sense to impose uniformity requirements on its implementors. Instead most of the implementations will focus on generating data in a way that enables faster detection of faults in fuzzing and testing contexts.

At the end of the day, this is a library for fuzzing and related activities. That use case is the priority.
That said, we certainly want uniformity (or at least an approximation) for things like Arbitrary for u32 so long as it doesn't have such a cost on fuzzing throughput that the overall fuzzing efficiency is lowered (which is vague and very specific to a particular fuzz target).
An example where we balance these things: https://github.com/rust-fuzz/arbitrary/blob/master/derive/src/lib.rs#L74-L76

At the end of the day, this is a library for fuzzing and related activities. That use case is the priority.
That said, we certainly want uniformity (or at least an approximation) for things like Arbitrary for u32 so long as it doesn't have such a cost on fuzzing throughput that the overall fuzzing efficiency is lowered (which is vague and very specific to a particular fuzz target).
An example where we balance these things: https://github.com/rust-fuzz/arbitrary/blob/master/derive/src/lib.rs#L74-L76

Is Arbitrary supposed to be exactly uniformly distributed?

Also note that it's hard to say what this means for dynamically-sized collections like Vec, or recursive data types. For the latter case, there's Boltzmann sampling, but that seems hard to implement.


Uglify flags

It appears that the way to get Uglify to do the best job on compiled Elm code is to call the CLI like so:
$ uglifyjs code.js -mc 'pure_funcs="F2,F3,F4,F5,F6,F7,F8,F9"' > mini.js

I don't know if Webpack supports things like "use these uglify flags only for compiled Elm assets" but I thought I'd post this here in case anyone wants to investigate whether this info could improve the default Uglify settings for the Elm webpack loader!

I was able to try these flags on our Elm codebase, with the below Webpack 4 script.  The splitChunks option pulls the Main.elm file into a separate bundle.  Then, there are two Uglify plugins configured which work on the different bundles, one for Elm code, and one for everything else.
This does reduce the size, however, the pure_funcs options appear to break our Elm code.  Specifically, http requests no longer have the Authentication headers added to the requests.  Not sure if this is something specific to a package we are using, or if it something specific to our codebase.  Providing this as a starting point for someone else to get started with, as I don't really have time to keep working on this.
    optimization: {
        concatenateModules: true,
        minimizer: [
            new UglifyJsPlugin({ exclude: 'elm', sourceMap: true, parallel: true }),
            new UglifyJsPlugin({
                include: 'elm',
                parallel: true,
                sourceMap: false,
                uglifyOptions: {
                    compress: {
                        pure_funcs: [
                            'F2',
                            'F3',
                            'F4',
                            'F5',
                            'F6',
                            'F7',
                            'F8',
                            'F9',
                            'A2',
                            'A3',
                            'A4',
                            'A5',
                            'A6',
                            'A7',
                            'A8',
                            'A9'
                        ],
                        pure_getters: true,
                        keep_fargs: false,
                        unsafe_comps: true,
                        unsafe: true
                    }
                }
            })
        ],
        splitChunks: {
            cacheGroups: {
                default: false,
                elm: {
                    test: /[\\/]Main.elm/,
                    name: 'elm',
                    chunks: 'all'
                }
            }
        }
    },

Damn, guess there's more to this than I thought...sorry! 😅

I just gave this config a shot (slightly modified from @zacharybussey comment):
{
  ... // rest of webpack config
  optimization: {
    minimizer: [
      new UglifyJsPlugin({exclude: 'elm', sourceMap: true, parallel: true}),
      new UglifyJsPlugin({
        include: 'elm',
        sourceMap: true,
        minify(file, sourceMap) {
          const uglify = require('uglify-js');
          const {error, map, code, warnings} = uglify.minify(file, {
            mangle: false,
            compress: {
              pure_funcs: [
                'F2',
                'F3',
                'F4',
                'F5',
                'F6',
                'F7',
                'F8',
                'F9',
                'A2',
                'A3',
                'A4',
                'A5',
                'A6',
                'A7',
                'A8',
                'A9',
              ],
              pure_getters: true,
              keep_fargs: true,
              unsafe_comps: true,
              unsafe: true,
            },
          });
          if (error) {
            return {error, map, code, warnings,};
          }

          return uglify.minify(code, {
            mangle: true,
          });
        },
      }),
    ],
    splitChunks: {
      cacheGroups: {
        default: false,
        elm: {
          test: /[\\/]Main.elm/,
          name: 'elm',
          chunks: 'all',
        },
      },
    },
  },
}

This minifies the elm chunk twice, following the recommendation (here)[https://github.com/elm/compiler/blob/master/hints/optimize.md]. With this config (on 0.19.1), everything seems to be working and I'm not running into any issues with request headers. Turning on these flags on did reduce my bundle size by quite a bit though!
Use this with caution, I haven't done thorough testing!

In case anyone needs a config for Webpacker 3, here it is. With slight modifications you should be able to use it with plain Webpack 3 as well, just remove the Webpacker API calls like environment.plugins.append and add the code directly to you Webpack config.
Also, the config above has a small error: keep_fargs is supposed to be set to false, not true.

Webpacker 3 config
// Add this to config/webpack/production.js.
// Make sure you pass the `optimize` flag to elm make, you'll probably need to do this
// in the loader.
// Add<EMAIL_ADDRESS>to your package.json.

const webpack = require('webpack')
const UglifyJsPlugin = require('uglifyjs-webpack-plugin')

// Some UglifyJS optimizations for the Elm code.
// https://elm-lang.org/0.19.1/optimize

// Remove the default compression options that Webpacker adds. They're not optimal for the Elm code.
environment.plugins.delete("UglifyJs")

// First we need to extract a separate chunk with Elm only, so that we can run UglifyJS only on that
// chunk. We're going to use optimizations which are unsafe when ran on regular JS code.
environment.plugins.append('ElmChunk', new webpack.optimize.CommonsChunkPlugin({
  name: 'elm',
  minChunks: (module) => {
    return module.resource && module.resource.includes('.elm')
  }
}))

// Extract a manifest so that we can actually load our chunks.
environment.plugins.append('CommonsChunkManifest', new webpack.optimize.CommonsChunkPlugin({
  name: 'manifest', minChunks: Infinity
}))

// Compress the Elm chunk first. According to the guide, we must first compress and then mangle
// rather than doing it all in one step.
environment.plugins.append('UglifyElmCompress', new UglifyJsPlugin({
  include: 'elm',
  uglifyOptions: {
    mangle: false,
    compress: {
      pure_funcs: [
        'F2', 'F3', 'F4', 'F5', 'F6', 'F7', 'F8', 'F9', 'A2', 'A3', 'A4', 'A5', 'A6', 'A7',
        'A8', 'A9',
      ],
      pure_getters: true,
      keep_fargs: false,
      unsafe_comps: true,
      unsafe: true,
    }
  }
}))

// Finally, mangle the Elm chunk, reducing its size even more.
environment.plugins.append('UglifyElmMangle', new UglifyJsPlugin({
  include: 'elm',
  uglifyOptions: {
    mangle: true,
    compress: false,
  }
}))

// Enable Uglify for non-Elm code, since we removed the default configuration.
environment.plugins.append('UglifyOther', new UglifyJsPlugin({
  exclude: 'elm',
}))

Then in the view you need to load the manifest and the Elm chunk in production env:
<% if Rails.env.production? %>
  <%= javascript_pack_tag "manifest" %>
  <%= javascript_pack_tag "elm" %>
<% end %>
<%= javascript_pack_tag "application" %>

I confirmed that it works properly by using UglifyJS from the terminal and then comparing its size to what Webpack produced.


Added wasm signature

Hello, @danielgindi !
Thanks for all of you did, it's really amazing!
But could you just send me some contact (viber, telegram, slack, whatsapp)? We need to think about few things :)
My mail<EMAIL_ADDRESS>


Renaming to native for c-core root dir

Change Summary

renaming native_src to native
updating Package.swift and source sync script for the folder naming

Test & Verify
run shallow source sync locally to verify
./scripts/sync_grpc_src_shallow.sh

verify spm build via
swift build && swift test

LGTM by comment since cannot open 😂


⚠ Bofrost.lu has degraded performance

In 85a0f1d, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1585 ms

Resolved: Bofrost.lu performance has improved in 678dd19 after 7 minutes.


A11y: Closing a dropdown should return focus to the dropdown control

When a dropdown component https://getbootstrap.com/docs/5.1/components/dropdowns/ is closed, focus is currently lost (though most browsers then use heuristics to try and place it roughly in the correct area.
It should ideally be programmatically placed back to the trigger/control that opened the dropdown in the first place.
This may need an extra option to suppress this behaviour for clicks inside the dropdown, as moving focus explicitly back to the trigger/toggle may interfere with whatever the author may be doing with options/links/etc inside the dropdown

I have understand your problem. You can solve it by adopting following method: As all Twitter Bootstrap users know, the dropdown menu closes on click (even clicking inside it). To avoid this, I can easily attach a click event handler on the dropdown menu and simply add the famous event. stopPropagation() . Moreover visit Pinterest video downloader for more info.

I would love to help with this

feel free to have a stab at this, @Emeka-Ugbanu-hub

cna you tell me how to replicate this issue