Minimal example with Transaction?

Hello,
I'm trying to make a transaction, but I am hitting a wall and can't figure it out.
Is it possible for an example with transaction and 2 inserts for example?

Hey elpiel! What you're asking should be very simple, if you know intermediate level Rust. bb8 uses Tokio async (learn just a bit of that), the builder pattern (you should know what this is), and Rust traits (this too), and although you can implement the connection manager trait yourself, the builder is more than enough for general purposes. Also, check out the bb8 docs.

Well actually I coulnd't.

run requires output future Ok((_, conn)) or Err((_, conn)), but transaction on other hand is a bit different. It accepts a Future. You can still probably map it, although I do remember trying.
if I move |...| connection also gets moved(in order not to clone every value I need for the query when executing it).
I can't wrap my head around how to create 2 inserts(probably with join) and then again use the connection to create a transaction which should return the connection itself, because you cannot do await! inside run()

I haven't actually run this against a real database but I think it should work:
https://github.com/khuey/bb8/commit/36c52b6ba5622edb398d9b66b155fd4f6ee76a07#diff-fe61805d997a94ac99aa2ae71f7750d7R30
The tokio-postgres transaction API is not usable from bb8 at the moment, unfortunately, so you need to do it manually like this.

@khuey would you guide me through the implementation? I would like to try to implement it, if you have an idea how it will work?

Guide you through the implementation of what, exactly?

How to implement the Transaction API of tokio-postgres in bb8.

So tokio-postgres's transaction API is available[0], it just doesn't work. The TransactionBuilder object that tokio-postgres gives you takes a Future, and we need to move the connection object[1] into the future (so that we can do SQL queries on the connection). But if the TransactionBuilder fails internally, we have no way to attach the connection object to its error (because we moved the connection into the future) so the connection is lost and then you can't make the type signatures match up with what bb8 expects.
What we need is a transaction method that looks something like this:
fn transaction<R, E, Fut, F>(connection: tokio_postgres::Client, f: F) -> impl Future<Item = (tokio_postgres::Client, R), Error = (tokio_postgres::Client, E)>
  where F: FnOnce(tokio_postgres::Client) -> Fut,
        Fut: Future<Item = (tokio_postgres::Client, R), Error = (tokio_postgres::Client, E),
        E: From<tokio_postgres::Error>
{
    connection.simple_query("BEGIN")
        ...
        .and_then(|connection| {
            f(connection)
        })
        .and_then(|(mut connection, result)| {
            connection.simple_query("COMMIT")
                ...
                .then(|r| match r {
                    Ok(_) => Ok((connection, result)),
                    Err(e) => Err((connection, e))
                 })
        })
        .or_else(|(mut connection, e)| {
            connection.simple_query("ROLLBACK")
                ...
                .then(|_| Err((connection, e)))
        })
}

So step 1 is to write that function and get it working.
[0] https://docs.rs/tokio-postgres/0.4.0-rc.2/tokio_postgres/struct.Client.html#method.build_transaction
[1] i.e. a tokio_postgres::Client

Something like this works.
diff --git a/postgres/src/lib.rs b/postgres/src/lib.rs
index 87c38ce..47bd6a7 100644
--- a/postgres/src/lib.rs
+++ b/postgres/src/lib.rs
@@ -90,16 +90,20 @@ where
 }

 /// Run asynchronous into a Transaction
-pub fn transaction<R, Fut, F>(mut connection: tokio_postgres::Client, f: F) -> impl Future<Item=(R, tokio_postgres::Client), Error=(tokio_postgres::Error, tokio_postgres::Client)>
+pub fn transaction<R, E, Fut, F>(mut connection: tokio_postgres::Client, f: F) -> impl Future<Item=(R, tokio_postgres::Client), Error=(E, tokio_postgres::Client)>
     where
         F: FnOnce(tokio_postgres::Client) -> Fut,
-        Fut: Future<Item=(R, tokio_postgres::Client), Error=(tokio_postgres::Error, tokio_postgres::Client)>,
+        E: From<tokio_postgres::Error>,
+        Fut: Future<Item=(R, tokio_postgres::Client), Error=(E, tokio_postgres::Client)>,
 {
     connection.simple_query("BEGIN")
         .for_each(|_| Ok(()))
         .then(|r| match r {
             Ok(_) => Ok(connection),
-            Err(e) => Err((e, connection)),
+            Err(e) => {
+                let error: E = e.into();
+                Err((error, connection))
+            },
         })
         .and_then(|connection| f(connection))
         .and_then(|(result, mut connection)| {
@@ -107,11 +111,11 @@ pub fn transaction<R, Fut, F>(mut connection: tokio_postgres::Client, f: F) -> i
                 .for_each(|_| Ok(()))
                 .then(|r| match r {
                     Ok(_) => Ok((result, connection)),
-                    Err(e) => Err((e, connection))
+                    Err(e) => Err((e.into(), connection))
                 })
         })
         .or_else(|(e, mut connection)| {
             connection.simple_query("ROLLBACK").for_each(|_| Ok(()))
-                .then(|_| Err((e, connection)))
+                .then(|_| Err((e.into(), connection)))
         })
-}
\ No newline at end of file
+}

Woops, meant to post that in the PR.


⚠ Fortnite has degraded performance

In 7d9f47f, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1770 ms

Resolved: Fortnite performance has improved in 8a09bd3.


std::logic_error: Mat::init(): requested size is not compatible with column vector layout

Hi,
I tried to run your code, but keep getting the error: std::logic_error: Mat::init(): requested size is not compatible with column vector layout
I didn't change anything, just make first and the ./main
The full log is: ADF test results:
Test statistic: -61.3412
P-value: 0
The series is stationary
n = 74934
libc++abi: terminating due to uncaught exception of type std::logic_error: Mat::init(): requested size is not compatible with column vector layout
zsh: abort      ./main
Do you have any idea why is it?
Thank you very much
Best
Xintong He

Hello,
I fixed the error now, looks I made a mistake in PACF function call. However I also have to emphasize that I still haven't implemented APIs for autoregressive (AR) or moving average (MA) terms(p,q). But thanks for bringing this up.


Preview app doesn't fit on the screen 1366 x 768

I have checked all my display settings and everything is right. I can't even scroll or resize this app.

That region should be scrollable, probably a layout issue

Same here, app is unusable in native settings because I can't save any of the textures made.
Issue is probably related to High-DPI scaling issues.
I have a 1080p laptop monitor with 150% scaling

FastNoiseLite application has no scroll:

After resized scaling:

Application is fully visible:

has anyone been able to solve this yet? I'm trying to do it myself but I have no clue how to open the visual editor

Fixed in v1.1.0 with new web app


[Bug] --fail-fast not supported in RPC server

Is there an existing feature request for this?

[X] I have searched the existing issues

Describe the Feature
--fail-fast cancels a dbt run if any model has an issue. This flag should also be supported for dbt test (I thought it already was, and told a community member to use this).
It's as relevant for a failing test in a CI environment to cancel a run.
Describe alternatives you've considered
I don't think there is an alternative right now
Who will this benefit?
CI users who want a failing test to cancel the rest of the run
Are you interested in contributing this feature?
Yeah go on!
Anything else?

Slack thread
I haven't looked into the behaviour with dbt build - I'm guessing that right now, --fail-fast would apply when the model was built, but not when the tests were run. If that's true, this change should also fail a test that happens in a build context.

Thanks @jtcohen6! I'll open an equivalent docs issue to get that info onto build and test as well


Add 'deleteprivkey' RPC command.

See #220 for discussion.

If you feel comfortable - go ahead and pull it in.
I think the changes you made cover our due diligence.


chore: Removed wrappedChildren in FlexComponent

Description
wrappedChildren is used to add a div around widget which sets 100% height and width. This happens only on deploy mode. This was added to make sure some widgets are getting properly displayed in deploy mode.
In this PR, we are removing it and make the necessary changes in the widget's code itself.
PR fixes following issue(s)
Fixes #27085
Type of change

Chore (housekeeping or task changes that don't impact user perception)

Testing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

[x] Manual
[ ] JUnit
[ ] Jest
[ ] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/ok-to-test

@rahulramesha Other widgets might already be having these. That's why they render properly.
I've added width: 100% only to the widgets that doesn't render properly.

/build-deploy-preview

/build-deploy-preview env=release


Add a new rule: filename matches component

For named components, this enforces that the camelcase component
name matches the underscore file name.

In Airbnb's case, we want the camelcase component name to match the camelcase file name - I'd want this to be enforceable too, regardless of the default.
However, this seems like a generic rule: that the name of the default export of a file matches the filename - either camelcase or snake_case - rather than a React-specific rule.


Enhancing init command

With this update Init command can specify custom config names.
All these commands are valid:
$ vendor/bin/phinx init
$ vendor/bin/phinx init .
$ vendor/bin/phinx init phinx.yml
$ vendor/bin/phinx init ~/Project/custom-config.yml

Codecov Report

Merging #1266 into master will increase coverage by 0.21%.
The diff coverage is 88.23%.

@@            Coverage Diff             @@
##           master    #1266      +/-   ##
==========================================
+ Coverage   74.63%   74.84%   +0.21%
==========================================
  Files          35       35
  Lines        4739     4763      +24
==========================================
+ Hits         3537     3565      +28
+ Misses       1202     1198       -4

Impacted Files
Coverage Δ

src/Phinx/Console/Command/Init.php
80% <88.23%> (+10.55%)
:arrow_up:

src/Phinx/Db/Adapter/PostgresAdapter.php
93.73% <0%> (+0.02%)
:arrow_up:

src/Phinx/Migration/Manager.php
90.54% <0%> (+0.52%)
:arrow_up:

src/Phinx/Seed/AbstractSeed.php
48.83% <0%> (+2.49%)
:arrow_up:

Continue to review full report at Codecov.

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

Just created an issue https://github.com/cakephp/phinx/issues/1279 for this PR

By the way, why not adding an ability to customize the $fileName simply? Wouldn't it work if you add a new option like --config-file-name which defaults to phinx.xml?

I am applying all requested changes.
I am not enthusiastic about the proposed new option, I really like when code is straight forward.
My proposed solution is fully backward compatible, you can define a directory path or a file path... it will work. Furthermore adding a new option will force me to check the docs twice before start using it.
I really like the solution as is.

OK. I left a comment about is_writable(). Other changes look good to me.


[FEATURE] Integration tests using test-harness and flagd

Requirements
Execution of integration tests utilizing the test-harness repository, the BDD tests, and the flagd provider.

Here's a link to the shared Gherkin tests:
https://github.com/open-feature/test-harness


Resource AI

Added the beginnings of the resource AI

Ill merge this once i get it working properly.


sync remove only uninstalled, not disabled, extensions?

Visual Studio Code Version : 1.23.0-insider
Code Settings Sync Version : 2.9.0
Operating System : Win10
Occurs On: Upload
Proxy Enabled: No
GIst Id: b265edcb9ef1100fcf49b9caf7874953
Would it be possible to add a setting for syncing / not removing DISABLED addons?
"sync.removeExtensions": true,
This removes disabled and uninstalled extensions?
Seems like would be best if it saved disabled addons and saved the disabled state?
Else maybe another setting? sync.RemoveDisabledExtensions?
Please and thanks.

Great!
But low priority for me.
PR is welcome :) - I can help you if you want to work on it and release new version.

I would love it also ! Just noticed i'm missing a lot of extensions.
It depends a lot on what i work on. And i prefer to only enable core extensions. All the other would be workspace specific.

Duplicate of #143

API limitation from Code side for now.
Feel free to discuss there.


createTokenPromise function cannot use on mobile phone in Next.js

I try to use createTokenPromise in Next.js On window OS or macOS it work properly. But when I use on Mobile phone (Safari, Chrome) it return "de is not a function. (In 'de("card",t)', 'de' is null)"  when I was submitted  . I don't know why previously I also have a problem with Omise.createToken and then I try your libs . thanks

I think this is related to https://github.com/cpvdeveloper/use-omise/issues/7#issuecomment-1407269361. Basically, the Omise script has not loaded yet and so the function you're trying to call - createToken - is still null.


fix: get a correct sheet name based on the schema name field

Summary
Change type of private lazy val schemas from List[Schema] to List[(Schema, SchemaName)] to use the correct name when getting the sheet name of schema's attributes.
PR Type: Bug Fix
Status: Ready to review
Breaking change? No

@hayssams


[Bug-App]: Relative Time on X-axis Not Showing Meaningful Units

Describe the bug
When I use "Relative Time (Wall)" or "Relative Time (Process)", it gives me no units (is about 40k for 12 hours, so probably in seconds). It used to show it in minutes or hours dynamically. This makes it very hard to understand the time axis and not nice to share updates with my labmates.
Current behavior:

Current behavior on System section (defaults to x-axis being time)

Old Behavior on System section from video (https://www.youtube.com/watch?v=gnD8BFuyVUA)

Browser and OS:

Google Chrome: Same issue on Ubuntu, Android, and Windows

Hi @tylerlum Thank you for reporting this to us as well. May I know your current SDK version when you logged this experiments to wandb so I can try to reproduce the issue and investigate? Thank you!

python
Python 3.8.20 | packaged by conda-forge | (default, Sep 30 2024, 17:52:49)
[GCC 13.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import wandb
>>> wandb.__version__
'0.12.21'

I also just tried with this:
mamba create -n test_env python=3.10
mamba activate test_env
pip install wandb

Then
# test_wandb.py

import wandb
import time
import math

# Initialize a new wandb run
wandb.init(project="sine_wave_logging", name="sine_wave_test")

# Set up parameters
num_steps = 100  # Number of steps in the loop
frequency = 0.1  # Frequency of the sine wave

# Log sine wave values in a loop
for step in range(num_steps):
    x = step * frequency
    y = math.sin(x)

    # Log to wandb
    wandb.log({"step": step, "x": x, "sine_value": y})
    time.sleep(10)

# Finish the wandb run
wandb.finish()

python test_wandb.py

^ same problem. The time goes up to 200 (and doesn't show units, but it is seconds), should be turned into minutes by now.
python
Python 3.10.15 | packaged by conda-forge | (main, Oct 16 2024, 01:24:24) [GCC 13.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import wandb
>>> wandb.__version__
'0.18.5'

This is the latest version and still has the problem

Been 350 seconds, still not showing it in minutes

Thanks for sharing these useful information @tylerlum I will further investigate this and will get back to you for another update tomorrow. Along with the another issue we are checking with downloading PNG. Thank you!

Thank you! Any update on this?

Any update on this?

Yes, it used to change dynamically so it would show in minutes or hours (whichever was appropriate). However, now everything shows in seconds. The video tutorial is what the behavior used to be like for me before (which I liked a lot).
Now, if I train for 1.5 days, I would like it to tell me 1.5 days or 36 hours, but it actually shows me 129600 seconds, which is very hard to interpret.

Thank you for the update! This will be very helpful when fixed

Yes that workaround works for me. This would still be great to fix, but this workaround is helpful, thanks!


[feat-50]-add-DND-to-applications

Added DND support to list component
Main changes:

In Firestore - added "columns" collection to each user
Modified List component to suit the new data structure
Slight change to design in List component and general style (only changed scroll behavior)

Added DND support to list component
Main changes:

In Firestore - added "columns" collection to each user
Modified List component to suit the new data structure
Slight change to design in List component and general style (only changed scroll behavior)


Use Microsoft dependency with DryIoc in prism

hi
my setup:

`  <PackageReference Include="Prism.DryIoc.Extensions" Version="<IP_ADDRESS>4" />

    <PackageReference Include="Prism.Forms.Extended" Version="<IP_ADDRESS>4" />

    <PackageReference Include="Shiny.Prism" Version="<IP_ADDRESS>4" />
 `

i add som service to   protected override void RegisterTypes(IContainerRegistry containerRegistry) as below

            containerRegistry.RegisterServices(services =>// PrismContainerExtension.Current.RegisterServices(x =>
            {
                // services.AddOptions<AgentOptions>();IPoolConfigurator,  PoolConfigurator

                services.AddLogging(logging => logging.AddConsole());
                services.Add(ServiceDescriptor.Singleton<ILoggerFactory, LoggerFactory>());
                services.Add(ServiceDescriptor.Singleton(typeof(ILogger<>), typeof(Logger<>)));

dryioc installed and used in xamarin only but other project that referenced and used by xamarin dos'n have  dryioc  you see in picture IServiceProvider is dryioc

we have error  for using  Logger =  provider.GetRequiredService<ILogger<AgentBase>>();  but as you see below source of error is Microsoft dependency

is this correct and how it can be solved

I am not using the Xamarin Prism personally so it is hard to answer. Please post the question on StackOverflow with dryioc, prism tags.

Thanks


Make it possible to configure a graceful shutdown period for tests

I have a use case where my tests have a really heavy setup and teardown logic. This logic happens within the test functions themselves. Each test function individually runs a terraform apply at the begging of the tests and terraform destroy deploying various resources to the AWS cloud temporarily.
terraform and AWS cloud are quite heavy-weight. It may take the from 1 to 10 minutes to perform the setup and maybe 1-5 minutes to teardown and cleanup the resources.
Right now cargo-nextest sends a SIGKILL to the test process leaving it no chance to gracefully terminate. It would solve this problem if cargo-nextest could allow configuring the behavior of graceful shutdown for tests. For example, if I could say in the config file that "these tests" selected by the DSL (in my case I don't need it, I need to select them all, but I think it may be useful for other use cases) need to be shutdown gracefully. Then configure the UNIX signal that will be sent to the tests, and the timeout for the tests to exit by themselves, after which cargo nextests will send a SIGKILL.

Hi there -- please see https://nexte.st/book/slow-tests.html#how-nextest-terminates-tests. On encountering a timeout, nextest sends a SIGTERM, waits 10 seconds, and then sends a SIGKILL. You can customize the timeout with the grace-period setting.
The initial signal is not configurable, but I hope SIGTERM would work for you. If it doesn't work for you could you explain why? If there's a solid use case for a non-SIGTERM signal I'd be happy to accept patch contributions.

I think I missed to mention the main thing in the issue. The problem here is not with the tests that time out. The problem is with the following scenario.
Given I already have tests in the process of running.
I suddenly want to abort the tests.
I press Ctrl+C on the terminal.
I expect that my tests receive a SIGINT and they gracefully shut down themselves and perform cleanup of the resources they created for themselves.
Right now cargo-nextest always sends SIGKILL to the tests when I abort it with Ctrl+C, but I want cargo-nextest to send SIGINT to my tests instead.
Why SIGINT? It's because this is the signal that tokio listens for in its tokio::signal::ctrl_c() function, which is a cross-platform tool to listen for interrupt signals. SIGTERM on the other hand requires writing some unix-specific code to handle this type of signal.
Anyway, I don't think it's critical to be able to configure the signal which is sent, it's still possible to write unix-only code for handling the SIGTERM.
My tests don't need to run on windows, but if the process were killed in a way that tokio::signal::ctrl_c() could also catch that on windows, it would be cool as well.

Hmm that's weird -- no, tests should get a SIGINT, not a SIGKILL, if you ctrl-c them.

I figured out the following.

If I send SIGINT by pressing Ctrl+C on the terminal, then cargo-nextest gives exactly 10 seconds to my tests process before killing it. I couldn't find a way to configure a value greater than 10 seconds for this.
Here is the rust code I used:

Details
#[tokio::test]
async fn sigabox() {
    let teardown_duration = std::time::Duration::from_secs(15);

    eprintln!("Waiting for SIGINT (Ctrl-C)...");

    tokio::signal::ctrl_c().await.unwrap();

    eprintln!("SIGINT received, tearing down...");

    tokio::time::sleep(teardown_duration).await;

    eprintln!("Teardown succesful, bye bye!");
}

[package]
edition = "2021"
name    = "nextest-sigint-repro"
version = "0.1.0"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
tokio = { version = "1.22", features = ["macros", "rt-multi-thread", "signal", "time"] }

I started the tests and immediately (within 1 second) pressed a Ctrl+C.
Here is the output I saw in the terminal.
$ cargo nextest run --no-capture
    Finished test [unoptimized + debuginfo] target(s) in 0.04s
    Starting 1 test across 1 binary
       START             nextest-sigint-repro sigabox

running 1 test
Waiting for SIGINT (Ctrl-C)...
^C   Canceling due to interrupt: 1 tests still running
SIGINT received, tearing down...
     SIGKILL [  10.377s] nextest-sigint-repro sigabox
------------
     Summary [  10.377s] 1 test run: 0 passed, 1 failed, 0 skipped
error: test run failed

I also tried this config, but it didn't influence the period that nextest gave the tests to tear down, the grace period was still 10 seconds for Ctrl+C
[profile.default]
slow-timeout = { period = "60s", terminate-after = 1, grace-period = "20s" }

If I send SIGTERM to cargo-nextest it sends SIGKILL to the test and immediately exists.
I didn't expect that SIGTERM is handled in a different want than SIGINT by cargo-nextest

OK:

I think a custom grace period should probably also apply to SIGINT/ctrl-c. This suggests that grace-period should live outside slow-timeout and be a top-level option.
Sending a SIGTERM to nextest should send SIGTERM to test processes and then apply the grace period, not SIGKILL.

I'm currently sick and otherwise very busy, so probably won't have time to fix either of these any time soon. If you're interested in working on it I'd love it if you submitted a PR or two to fix it. Thanks!

+1 on this feature request. I have some slow cleanup actions that get performed on SIGINT, where the hard-coded 10 second grace period is too quick. I was hoping slow-timeout.grace-period would also configure the SIGINT grace period, but no such luck.
I looked at the source code and think I could probably make this change here in the next few weeks when I have some capacity.
One question remains for me: should slow-timeout.grace-period be kept for compatibility? or are we okay with moving forward with a breaking change to the config (introducing grace-period at the top-level and removing it from slow-timeout)

Opened a PR for this #1039 .
I went with shutdown-grace-period as the name for the new top-level config, but I'm open to suggestions on what to call it instead.


Is there a way to hide navigations which user don't have permissions for?

Instead of showing all navigation on the left side, do we have any way to hide navigations which user don't have permissions for?

You can assign roles to menus so that only the user with those roles can see the menu on the left side.
http://laravel-admin.org/demo/auth/menu

Wow! Worked like this. Amazing. Thanks 👍  😄


Unable to resolve dependency tree

When attempting to install react-usa-map on linux (npm install react-usa-map --save)
I got the following errors:
While resolving<EMAIL_ADDRESS>Found<EMAIL_ADDRESS>node_modules/react
<EMAIL_ADDRESS>from the root project
Could not resolve dependency:
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/react-usa-map
react-usa-map@"*" from the root project
Any suggestions on how to resolve this issue?

I had this problem a month or so ago. The only way I was able to resolve it was to change my react and react-dom dependences both to ^16.13.1. If you're not using any version 17-specific features of react, this may work for you. @gabidavila says on her bio page that she needs help with this repo, so I wouldn't expect version 17 compatibility soon.

The library can be installed without having to downgrade to version 16 of react and react-dom by using the --force option when installing it:
npm i --save react-usa-map --force
This --force option will also need to be specified when running npm install or npm ci.
I'm using React 17 and it works great.

Thanks for the tip. I must admit that I'm hesitant to use --force on production code, as that could allow other potentially serious incompatibilities to be bypassed.


Kanban board is private, readme suggests it should be public

Current behavior 😯
The Kanban board is private. On the Projects tab:

I'm able to access it, because I'm a member of the GitoxideLabs organization, but it is not visible to most people (or if one is logged out).
Maybe this happened when the repository was moved into the GitoxideLabs organization?
Expected behavior 🤔
I believe it is intended to be public, because:

I don't know of any reason for it to be private.
The projects associated with this repository were public in the past.
The README refers to it in a way makes the most sense if people who have not yet begin to contribute to gitoxide can read it.

On that third point, this is the relevant part of the readme:

A backlog for work ready to be picked up is available in the Project's Kanban board, which contains instructions on how to pick a task. If it's empty or you have other questions, feel free to start a discussion or reach out to @Byron privately.

If for some reason the Kanban board is to be kept private, then the readme could be edited.
Although it looks like GitHub would let me close the Kanban board project, it doesn't seem like it would let me make it public. I think the information here may help in making it public. Maybe it became private unintentionally when moving this repository into the GitoxideLabs organization, relating to the organization's base permission for projects, as described in the note here.
Git behavior
Not applicable.
Steps to reproduce 🕹
Examining the project identifies it as private and shows a lock icon, as shown in the screenshot above, and attempting view it while logged out verified that this is currently the case.

Thanks for making me aware, this was an oversight. These are now private by default it seems.
This has now been corrected.

Thanks!


Option NavigateTo() of Table doesn't work

Bug type
Component
Component name
MudTable
What happened?
I try manually set start page of MudTable by using NavigateTo, but get no result

protected override async Task OnAfterRenderAsync(bool firstRender){
await base.OnAfterRenderAsync(firstRender).ConfigureAwait(true);
if(firstRender){
table.NavigateTo(2);
}
}
Expected behavior
I want after using NavigateTo, see selected page on Table
Reproduction link
https://try.mudblazor.com/snippet/GkQbvkvcxNzoxxaq
Reproduction steps
Just run reproduction link
Relevant log output
No response
Version (bug)
5.1.4
Version (working)
No response
What browsers are you seeing the problem on?
Chrome
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

A reaction is very necessary. Maybe it can be solved easily?

Hello @tatti9018,
since I am experiencing the same issue, could you please explain how you solved it?
Any help would be appreciated.
Thanks

Also experiencing this with the latest version 6.1.4? Any feedback on how to solve this yet?

Still not working. Any feedback?

Still not working...


WIP: reimplement stdio on windows

Note: doesn't work yet. I will setup the windows WM tomorrow.
Also, getting appveyor on this repo might be a good idea.

Now it manages to receive [0, 1, b"poll", []] message, but for some reason it doesn't seem to reply to it...

I think that the buffer of sys.stderr is overflowing and the reader thread is blocking. My branch based on your code works for now.
I can not completion deoplete.vim and denite.vim freezes without reproducibility. It is obviously slower than using pyuv. For the above reasons it seems difficult to routinely use at present.
neovim's functionaltest and python-clien tests succeed.
C:\> set TEST_FILE=test/functional/provider/python3_spec.lua
C:\> mingw32-make functionaltest
[  0%] Built target printargs-test
[100%] Built target nvim
[100%] Built target shell-test
[==========] Running tests from scanned files.
[----------] Global test environment setup.
[----------] Running tests from test/functional/provider/python3_spec.lua
[ RUN      ] test/functional/provider/python3_spec.lua @ 22: python3 commands and functions feature test
[       OK ] test/functional/provider/python3_spec.lua @ 22: python3 commands and functions feature test (0.00 ms)
[ RUN      ] test/functional/provider/python3_spec.lua @ 26: python3 commands and functions python3_execute
[       OK ] test/functional/provider/python3_spec.lua @ 26: python3 commands and functions python3_execute (15.00 ms)
[ RUN      ] test/functional/provider/python3_spec.lua @ 31: python3 commands and functions does not truncate error message <1 MB
[       OK ] test/functional/provider/python3_spec.lua @ 31: python3 commands and functions does not truncate error message <1 MB (374.00 ms)
[ RUN      ] test/functional/provider/python3_spec.lua @ 40: python3 commands and functions python3_execute with nested commands
[       OK ] test/functional/provider/python3_spec.lua @ 40: python3 commands and functions python3_execute with nested commands (110.00 ms)
[ RUN      ] test/functional/provider/python3_spec.lua @ 45: python3 commands and functions python3_execute with range
[       OK ] test/functional/provider/python3_spec.lua @ 45: python3 commands and functions python3_execute with range (47.00 ms)
[ RUN      ] test/functional/provider/python3_spec.lua @ 55: python3 commands and functions py3file
[       OK ] test/functional/provider/python3_spec.lua @ 55: python3 commands and functions py3file (31.00 ms)
[ RUN      ] test/functional/provider/python3_spec.lua @ 63: python3 commands and functions py3do
[       OK ] test/functional/provider/python3_spec.lua @ 63: python3 commands and functions py3do (31.00 ms)
[ RUN      ] test/functional/provider/python3_spec.lua @ 82: python3 commands and functions py3eval
[       OK ] test/functional/provider/python3_spec.lua @ 82: python3 commands and functions py3eval (15.00 ms)
[----------] 8 tests from test/functional/provider/python3_spec.lua (51807.00 ms total)

[----------] Global test environment teardown.
[==========] 8 tests from 1 test file ran. (51807.00 ms total)
[  PASSED  ] 8 tests.
[100%] Built target functionaltest

When pyuv is used, functionalteste ends at about 4072.00 ms.
C:\> python3 -m nose
.....................................................
----------------------------------------------------------------------
Ran 53 tests in 6.820s

OK
Exception ignored in: <bound method BaseEventLoop.__del__ of <ProactorEventLoop running=False closed=False debug=False>>
Traceback (most recent call last):
  File "I:\msys64\mingw64\lib\python3.6\asyncio\base_events.py", line 512, in __del__
  File "I:\msys64\mingw64\lib\python3.6\asyncio\proactor_events.py", line 437, in close
  File "I:\msys64\mingw64\lib\python3.6\asyncio\windows_events.py", line 747, in close
  File "I:\msys64\mingw64\lib\python3.6\logging\__init__.py", line 1294, in debug
  File "I:\msys64\mingw64\lib\python3.6\logging\__init__.py", line 1442, in _log
  File "I:\msys64\mingw64\lib\python3.6\logging\__init__.py", line 1452, in handle
  File "I:\msys64\mingw64\lib\python3.6\logging\__init__.py", line 1514, in callHandlers
  File "I:\msys64\mingw64\lib\python3.6\logging\__init__.py", line 863, in handle
  File "I:\msys64\mingw64\lib\python3.6\logging\__init__.py", line 1069, in emit
  File "I:\msys64\mingw64\lib\python3.6\logging\__init__.py", line 1059, in _open
NameError: name 'open' is not defined
Exception ignored in: <object repr() failed>
Traceback (most recent call last):
  File "I:\msys64\mingw64\lib\python3.6\asyncio\proactor_events.py", line 95, in __del__
  File "I:\msys64\mingw64\lib\python3.6\asyncio\proactor_events.py", line 54, in __repr__
  File "I:\msys64\mingw64\lib\python3.6\asyncio\windows_utils.py", line 152, in fileno
ValueError: I/O operatioon on closed pipe

I changed to delay the call to data_received, and functionaltest now ends at about 5257.00 ms. It seems that deoplete and denite also started working without problems.

I think that the buffer of sys.stderr is overflowing a

stderr is not buffered. This should only hurt performance not correctness

I changed to delay the call to data_receive

Yes, of course the read buffer size should be increased from one. I wanted to get it working (independently of blocking pipe state) before adjusting for performance...

Also, I may be saying something strange, but is the reader thread dead before sys.stderr is redirected to nvim.err_write (data)? In that case, I think that nothing is output, I applied the following patch to your code and executed nvim -u NONE --cmd "py3 print('Hello')", I got the following output in $NVIM_PYTHON_LOG_FILE.
--- a/neovim/msgpack_rpc/event_loop/asyncio.py
+++ b/neovim/msgpack_rpc/event_loop/asyncio.py
@@ -124,11 +124,17 @@ class AsyncioEventLoop(BaseEventLoop, asyncio.Protocol,
             self.data_received(data)

     def _stdin_reader(self):
-        sys.stderr.write("a {}\n".format(os.getpid()))
-        while True: #self._active
-            data = sys.stdin.buffer.read(1)
-            sys.stderr.write("b {}\n".format(len(data)))
-            self._loop.call_soon_threadsafe(self.data_received, data)
+        try:
+            sys.stderr.write("a {}\n".format(os.getpid()))
+            while True: #self._active
+                data = sys.stdin.buffer.read(1)
+                sys.stderr.write("b {}\n".format(len(data)))
+                self._loop.call_soon_threadsafe(self.data_received, data)
+        except:
+            import traceback
+            exc_type, exc_value, exc_traceback = sys.exc_info()
+            debug("%s %s %s", exc_type, exc_value,
+                    traceback.format_list(traceback.extract_tb(exc_traceback)))

     def _connect_stdio(self):
         self._loop = loop_cls()

2018-03-11 11:51:44,033 [DEBUG @ msgpack_stream.py:send:34] 3132 - sent [0, 1, b'vim_get_api_info', ()]
2018-03-11 11:51:44,034 [DEBUG @ base.py:send:117] 3132 - Sending 'b'\x94\x00\x01\xb0vim_get_api_info\x90''
2018-03-11 11:51:44,034 [DEBUG @ asyncio.py:_send:174] 3132 - sent b'\x94\x00\x01\xb0vim_get_api_info\x90' True
2018-03-11 11:51:44,034 [DEBUG @ base.py:run:142] 3132 - Entering event loop
2018-03-11 11:51:44,035 [DEBUG @ msgpack_stream.py:_on_data:59] 3132 - waiting for message...
2018-03-11 11:51:44,035 [DEBUG @ msgpack_stream.py:_on_data:64] 3132 - unpacker needs more data...
2018-03-11 11:51:44,035 [DEBUG @ msgpack_stream.py:_on_data:59] 3132 - waiting for message...
2018-03-11 11:51:44,035 [DEBUG @ msgpack_stream.py:_on_data:64] 3132 - unpacker needs more data...
2018-03-11 11:51:44,035 [DEBUG @ msgpack_stream.py:_on_data:59] 3132 - waiting for message...
2018-03-11 11:51:44,035 [DEBUG @ msgpack_stream.py:_on_data:64] 3132 - unpacker needs more data...
2018-03-11 11:51:44,036 [DEBUG @ msgpack_stream.py:_on_data:59] 3132 - waiting for message...
2018-03-11 11:51:44,036 [DEBUG @ msgpack_stream.py:_on_data:64] 3132 - unpacker needs more data...
2018-03-11 11:51:44,036 [DEBUG @ msgpack_stream.py:_on_data:59] 3132 - waiting for message...
2018-03-11 11:51:44,036 [DEBUG @ msgpack_stream.py:_on_data:64] 3132 - unpacker needs more data...
2018-03-11 11:51:44,036 [DEBUG @ msgpack_stream.py:_on_data:59] 3132 - waiting for message...
2018-03-11 11:51:44,037 [DEBUG @ asyncio.py:_stdin_reader:137] 3132 - <class 'OSError'> [Errno 22] Invalid argument ['  File "C:\\cygwin64\\home\\erw7\\work\\src\\python-client\\neovim\\msgpack_rpc\\event_loop\\asyncio.py", line 130, in _stdin_reader\n    data = sys.stdin.buffer.read(1)\n']
2018-03-11 11:51:44,037 [DEBUG @ msgpack_stream.py:_on_data:64] 3132 - unpacker needs more data...
2018-03-11 11:51:44,037 [DEBUG @ msgpack_stream.py:_on_data:59] 3132 - waiting for message...
2018-03-11 11:51:44,037 [DEBUG @ msgpack_stream.py:_on_data:64] 3132 - unpacker needs more data...
2018-03-11 11:51:44,037 [DEBUG @ msgpack_stream.py:_on_data:59] 3132 - waiting for message...
2018-03-11 11:51:44,037 [DEBUG @ msgpack_stream.py:_on_data:64] 3132 - unpacker needs more data...
2018-03-11 11:51:44,038 [DEBUG @ msgpack_stream.py:_on_data:59] 3132 - waiting for message...
2018-03-11 11:51:44,038 [DEBUG @ msgpack_stream.py:_on_data:61] 3132 - received message: [0, 1, b'poll', []]
2018-03-11 11:51:44,038 [DEBUG @ async_session.py:_on_request:91] 3132 - received request: b'poll', []
2018-03-11 11:51:44,038 [DEBUG @ msgpack_stream.py:_on_data:59] 3132 - waiting for message...
2018-03-11 11:51:44,038 [DEBUG @ msgpack_stream.py:_on_data:64] 3132 - unpacker needs more data...

I suspecting that sys.stdin.read(1) may cause an exception, if repeatedly read a file handle specified with PIPE_NOWAIT on Windows.
In my Linux environment processing will progress to the next place even in your code, so maybe there is a completely different reason in your environment, but I hope it will be helpful.
...
2018-03-11 12:14:09,144 [DEBUG @ base.py:stop:153] 3147 - Stopped event loop
2018-03-11 12:14:09,144 [DEBUG @ msgpack_stream.py:_on_data:59] 3147 - waiting for message...
2018-03-11 12:14:09,144 [DEBUG @ msgpack_stream.py:_on_data:64] 3147 - unpacker needs more data...
2018-03-11 12:14:09,144 [DEBUG @ base.py:run:144] 3147 - Exited event loop
2018-03-11 12:14:09,172 [INFO @ script_host.py:setup:56] 3147 - install import hook/path
2018-03-11 12:14:09,173 [INFO @ script_host.py:setup:61] 3147 - redirect sys.stdout and sys.stderr
2018-03-11 12:14:09,176 [DEBUG @ session.py:_on_request:205] 3147 - received rpc request, greenlet <greenlet.greenlet object at 0x7f27e36a5210> will handle it
2018-03-11 12:14:09,176 [DEBUG @ host.py:_on_request:90] 3147 - calling request handler for "poll", args: "[]"
2018-03-11 12:14:09,176 [DEBUG @ host.py:_on_request:92] 3147 - request handler for 'poll []' returns: ok
2018-03-11 12:14:09,176 [DEBUG @ session.py:handler:191] 3147 - greenlet <greenlet.greenlet object at 0x7f27e36a5210> finished executing, sending ok as response
2018-03-11 12:14:09,176 [DEBUG @ async_session.py:send:138] 3147 - sending response to request 1: [1, 1, None, 'ok']
2018-03-11 12:14:09,177 [DEBUG @ msgpack_stream.py:send:34] 3147 - sent [1, 1, None, 'ok']
2018-03-11 12:14:09,177 [DEBUG @ base.py:send:117] 3147 - Sending 'b'\x94\x01\x01\xc0\xa2ok''
2018-03-11 12:14:09,177 [DEBUG @ asyncio.py:_send:169] 3147 - sent b'\x94\x01\x01\xc0\xa2ok' True
2018-03-11 12:14:09,264 [WARNING @ session.py:handler:199] 3147 - error caught while processing request 'b'poll' []': Traceback (most recent call last):
  File "/home/erw7/work/python-client/neovim/msgpack_rpc/session.py", line 192, in handler
    response.send(rv)
  File "/home/erw7/work/python-client/neovim/msgpack_rpc/async_session.py", line 139, in send
    self._msgpack_stream.send(resp)
  File "/home/erw7/work/python-client/neovim/msgpack_rpc/msgpack_stream.py", line 35, in send
    self.loop.send(self._packer.pack(msg))
  File "/home/erw7/work/python-client/neovim/msgpack_rpc/event_loop/base.py", line 118, in send
    self._send(data)
  File "/home/erw7/work/python-client/neovim/msgpack_rpc/event_loop/asyncio.py", line 171, in _send
    sys.stdout.buffer.write(data)
AttributeError: 'RedirectStream' object has no attribute 'buffer'

As you might already know, the explanation of PIPE_NOWAITE of Microsoft's CreateNamedPipe has the following description.

Nonblocking mode is enabled. In this mode, ReadFile, WriteFile, and ConnectNamedPipe always return immediately.
Note that nonblocking mode is supported for compatibility with Microsoft LAN Manager version 2.0  and should not be used to achieve asynchronous I/O with named pipes. For more information on asynchronous pipe I/O, see Synchronous and Overlapped Input and Output.

sys.stderr is redirected to nvim.err_write (data)?

Ahyes, that would be a problem, though I would think the deadlock I got was before that, because I never saw that error message in my logs. We should keep private copies of stdout and stderr in the event loop.

Note that nonblocking mode is supported for compatibility with Microsoft LAN Manager version 2.0 and should not be used to achieve asynchronous I/O with named pipes. For more information on asynchronous pipe I/O, see Synchronous and Overlapped Input and Output.

Indeed, the "main" option forward should be https://github.com/neovim/neovim/pull/8113 (IPC mode didn't work, probably requires both ends to be libuv, so trying a patch for only the overlapped flag now), but we probably should support this thread fallback until nvim 0.2.3 is released.

Progress: now works together with  neovim/neovim#8113
@erw7 I just noticed your latest commit https://github.com/erw7/python-client/commit/4c97b67a229da359ebb73791b06011d168b55d0c, does it work to use stdin even if it hasn't been prepared by nvim?

No, My last commit require neovim/neovim#8113.
I think that this(#307) is necessary as a fallback.

I tried also to use the handle trick on stdout but it doesn't work. Guess we can live with blocking writes...
However, the fallback for stdin doesn't seem to work, for some reason the OsError for stdin is not getting propagated out of the loop (as it does just fine for stdout), so the thread code path is never reached...

Exception of stdin does not propagate, because it is caught on line 202 of proactor_events.py.
On my experiment-fallback-reader-thread branch, I tried to start the reader thread with connection_lost for the time being. @bfredl What do you think.
Because child_watcher does not support on Windows, this correspondence is also necessary.
About stdout, it seems that it is an error trying to read here. I can not understand what that code is going to do, so I do not know if it can be resolved.

After all, On my experiment-fallback-reader-thread branch, I changed to use  NtQueryInformationFIle like libuv to decide overlapped pipe. It seems that it is working.

I looked at the implementation of windows_utils.Popen, it passing a duplex pipe.
Therefore, I applied the following patch to https://github.com/neovim/neovim/pull/8113 and tried it.
diff --git a/src/nvim/event/libuv_process.c b/src/nvim/event/libuv_process.c
index b6f6e545c..c777d6f62 100644
--- a/src/nvim/event/libuv_process.c
+++ b/src/nvim/event/libuv_process.c
@@ -58,7 +58,7 @@ int libuv_process_spawn(LibuvProcess *uvproc)
   if (!proc->out.closed) {
     uvproc->uvstdio[1].flags = UV_CREATE_PIPE | UV_WRITABLE_PIPE;
 #ifdef WIN32
-    uvproc->uvstdio[1].flags |= UV_OVERLAPPED_PIPE;
+    uvproc->uvstdio[1].flags |= UV_READABLE_PIPE | UV_OVERLAPPED_PIPE;
 #endif
     uvproc->uvstdio[1].data.stream = STRUCT_CAST(uv_stream_t,
                                                  &proc->out.uv.pipe);

It seems that stdout also started to work with asynchronous writing due to this change.

@erw7 Thanks for looking it up. I will go through your changes and clean this PR up, soon...

Update: with nvim 0.3.0 now works on windows without reader thread. So removed all that.
@erw7 Thanks for all your input. Do you see any potential issue with the current code?

@bfredl On Windows, EventLoopPolicy.set_child_watcher() is not supported. Therefore, I think that the following patch is also necessary. Some tests will fail, so there may be other problems.
diff --git a/neovim/msgpack_rpc/event_loop/asyncio.py b/neovim/msgpack_rpc/event_loop/asyncio.py
index 0679289..59d0504 100644
--- a/neovim/msgpack_rpc/event_loop/asyncio.py
+++ b/neovim/msgpack_rpc/event_loop/asyncio.py
@@ -113,8 +113,9 @@ class AsyncioEventLoop(BaseEventLoop, asyncio.Protocol,
         debug("native stdout connection successful")

     def _connect_child(self, argv):
-        self._child_watcher = asyncio.get_child_watcher()
-        self._child_watcher.attach_loop(self._loop)
+        if os.name != 'nt':
+            self._child_watcher = asyncio.get_child_watcher()
+            self._child_watcher.attach_loop(self._loop)
         coroutine = self._loop.subprocess_exec(self._fact, *argv)
         self._loop.run_until_complete(coroutine)

For now the primary goal stdio support so nvim python plugins are supported, if child support has trouble we can fix it later.


.Net: Bug: .NET Google Gimini connector Issue

Describe the bug
Google Gimini connector error when we pass custom http client. The API is exposed from GIF.
To Reproduce
Steps to reproduce the behavior:
Code block Google Gimini connector using below code
GoogleAIGeminiChatCompletionService chatCompletionService = new(
     modelId: "chat-bison:predict",
     apiKey: .xxxxxxx,
     apiVersion: GoogleAIVersion.V1,
     httpClient: httpClient
);

var resultdata = await chatCompletionService.GetChatMessageContentsAsync(chat, chatRequestSettings, Kernel.CreateBuilder().Build());
Expected behavior
As the service is setup through GIF it should user token from HTTP client and authenticate API
Error details
Microsoft.SemanticKernel.HttpOperationException: 'Response status code does not indicate success: 401 (Unauthorized).'

Thanks for the issue!
Not fully sure what is the use case in this issue.

I'm assuming also that GIF means Gateway Integration Framework correct here if I'm wrong.
If this is correct, in theory your Gateway should ignore any provided header content and override it in the middle of the request.

If there's no Gateway, from my understanding when using your custom HttpClient you should be able to override the header thru a Custom DelegatingHandler overriding the SendAsync with the request Header you want.
Custom Http Handler Example

Yes it’s Gateway Integrated Framework. This is working fine for all Azure Open AI models but getting 401 for Gimini.
We verified the API call with Postman and it’s working as expected.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Roger Barreto @.>
Sent: Wednesday, August 7, 2024 4:32:23 AM
To: microsoft/semantic-kernel @.>
Cc: Hrishikesh Sawalkar (US) @.>; Author @.>
Subject: Re: [microsoft/semantic-kernel] .Net: Bug: .NET Google Gimini connector Issue (Issue #7904)
Thanks for the issue!
Not fully sure what is the use case in this issue.

I'm assuming also that GIF means Gateway Integration Framework correct here if I'm wrong.
If this is correct, in theory your Gateway should ignore any provided header content and override it in the middle of the request.

If there's no Gateway, from my understanding when using your custom HttpClient you should be able to override the header thru a Custom DelegatingHandler overriding the SendAsync with the request Header you want.

Custom Http Handler Examplehttps://urldefense.com/v3/__https://github.com/microsoft/semantic-kernel/blob/7b8ac8abf54c3c0e98c9e3f7653f44b0bb7565d3/dotnet/samples/Concepts/Memory/HuggingFace_TextEmbeddingCustomHttpHandler.cs*L43__;Iw!!Nyu6ZXf5!qHiSpaicGnsJurOM-UhcnQDzzl9bA0raz_G4J3b3AE-Hy6afK3-dN1RxSuGpkXc68_XrG9Ifn9twe0f9_8P-SiZNUHzcHQ$
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/microsoft/semantic-kernel/issues/7904*issuecomment-2273037594__;Iw!!Nyu6ZXf5!qHiSpaicGnsJurOM-UhcnQDzzl9bA0raz_G4J3b3AE-Hy6afK3-dN1RxSuGpkXc68_XrG9Ifn9twe0f9_8P-Siadl7U7FQ$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AZH3M7BSMX33SE5PQWR5LS3ZQHSSPAVCNFSM6AAAAABMCWNN7WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZTGAZTONJZGQ__;!!Nyu6ZXf5!qHiSpaicGnsJurOM-UhcnQDzzl9bA0raz_G4J3b3AE-Hy6afK3-dN1RxSuGpkXc68_XrG9Ifn9twe0f9_8P-SiY1F3i9XA$.
You are receiving this because you authored the thread.Message ID: @.***>

The information transmitted, including any attachments, is only for the intended recipient and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited, and all liability arising therefrom is disclaimed. If you received this in error, please contact the sender and delete the material from any computer and destroy any copies.
If the content of this email includes tax advice, the advice is limited to the matters specifically addressed herein and is not intended to address other potential tax consequences or the potential application of tax penalties.
PwC refers to one or more US member firms of the PwC network. Each member firm is a separate legal entity. Please see www.pwc.com/structure for further details.


Add comment in connection handshake how versions are constructed

Summary
Add a comment in connection handshake on how versions are constructed to align more with the ICS spec

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

closing as stale


vulkaninfo: Add Android build support

This change adds a build step to "build-android/build_all.sh" to create a command-line version of vulkaninfo for Android devices. Once built, vulkaninfo can be pushed to the device and executed using adb.
Because it is not possible to create ANativeWindow from a native command-line application, VULKANINFO_WSI_ENABLED is not defined for Android builds of vulkaninfo.

Author andy-poole-samsung not on autobuild list. Waiting for curator authorization before starting CI build.

Author andy-poole-samsung not on autobuild list. Waiting for curator authorization before starting CI build.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

CI Vulkan-Tools build queued with queue ID 51425.

CI Vulkan-Tools build # 953 running.

CI Vulkan-Tools build # 953 passed.

@charles-lunarg no problem at all - I am glad to contribute this. Upstreaming this change has been in my TODO list for a while now! Thank you for approving and pushing it through CI (not sure what's happened to the queued checks)

So I'm going to merge this because the failed/delayed checks are Ubuntu 18 jobs, which has just been removed from the github actions. Thats gonna have to be fixed pretty soon but thankfully all the other jobs succeeded.


Make gutter dragging experience consistent across selection modes

Refs #8350
Regardless of whether you're holding shift or cmd, the autoscroll behavior should be consistent.
@izuzak Can you try to break this?

@izuzak Can you try to break this?

I tried and failed. :clap: :clap:
And :zap: for cleaning this up, I believe I was the author of those cmd-click and shift-click handlers :sweat_smile:


fix(@angular-devkit/build-angular): printed server builder errors and warnings

Previously server builder errors and warnings were not being printed in the console correctly.
Closes #24612

I tested the patch locally on my projects and confirm that it fixes the issue.


Pin libsdformat to 9.*

In view of https://github.com/conda-forge/libsdformat-feedstock/issues/118, better make sure that libsdformat==9.* is always installed.
Similar to https://github.com/conda-forge/gazebo-feedstock/pull/217 .
Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender


feat: add x-origin property

This PR adds the x-origin property to the AsyncAPI Document before dereferencing external $refs, with the value of the according $ref, to keep traceability of $refs' origins after dereference.
Partial resolution of https://github.com/asyncapi/bundler/issues/141

@KhudaDad414 @derberg
@asyncapi/bounty_team

For anyone waiting on this PR who doesn't want to fork, you can use @apidevtools/json-schema-ref-parser in your local script before calling bundler, i.e., just dereference first, e.g.:
import bundle from '@asyncapi/bundler';
import $RefParser from "@apidevtools/json-schema-ref-parser";
import { writeFileSync } from 'fs';
import { resolve } from "node:path"
import { mkdir } from "node:fs/promises"

process.chdir("specs")

const srcFileName = 'events.asyncapi.yml';
const outputBase = resolve("../generated/docs/specs") + "/"
const outputPath = `${outputBase}${srcFileName}`;

try {
    await mkdir(outputBase, {recursive: true})
    const clonedSchema = await $RefParser.dereference(srcFileName, {
        dereference: {
            excludedPathMatcher: (path) => {
                console.log('Excluded path', path);
                return path.includes("operations")
            },
        },
        mutateInputSchema: false
    });
    const document = await bundle([clonedSchema], {
        referenceIntoComponents: true,
    });
    writeFileSync(outputPath, document.yml());
    console.log(`Bundled ${srcFileName} to ${outputPath}`)
} catch (err) {
    console.error(err);
}

This PR is ready for merge, but it should be merged only AFTER https://github.com/asyncapi/optimizer/pull/216 is merged (it will be merged only to next not master) and Optimizer 1.0.0 is released, due to the transfer of functionality of moving components into components to Optimizer starting from its version v1.0.0.

/rtm

/bounty


Add open/focus ranger example

I came up with a little script to open ranger file manager and in case it's already opened to just focus on it.
I didn't find a better way to choose required window than to compare title and class, so you need to find out which class your terminal windows have in order to use it.

How hard would it be to generalize this into a "run-or-raise" script where the user can choose what window they would like to either focus or start?

@acrisci it wouldn't be hard if the method of choosing the window was not so fuzzy, I'll try to look into it.


refactored example.rs for exercise circular-buffer

I did a couple changes to the example code of circular-buffer based on suggestions by user petertseng. I think this version is much more readable.

Cool!  Thanks!


ARC for iOS4

My last pull request were not compatible with iOS4 ARC target.
This commit replace weak with unsafe_unretained, so it works now.
Sorry for the double pull request.
René

jerbeers's solution is perfect.

+1

I've added this in https://github.com/jdg/MBProgressHUD/pull/45 .
All the issues from this request should be now addressed, so I'm closing this one.


Adetailer not working

Hi, I believe with the new update to adetailer, the adetailer extension is not working. I get the following error.
[-] ADetailer: Invalid arguments passed to ADetailer.
    input: ()
    ADetailer disabled.

Also, with the update the controlnet settings in the adetailer extension seems to be missing in the UI

Didn't see this one. I have verified the install just now, everything runs including ADetailer and Controlnet.


[FEATURE] "View All" option on Icons page

Description
Currently, we need to search the icons by name. But there might be some less popular icons that the user wants to use but does not know the search term to look for it.
So an option to view all the available icons at once would come in handy.
Screenshots
No response
Additional information
No response

Thank you for the suggestion but I think this will make the page very slow as there will be so many, we use react-icons with multiple icon sets.


Twitter - Multiple images appears to be broken for some users

Example: https://twitter.com/EricTse_/status/1504457559301890063
Expected:

What is happening:

This is now fixed in version 0.7.2: