Call to undefined method inPlaceEditing

Hello,
I think the last update broke my LTM.
I did export the new migrations and migrate
Now, as soon as I try to reach my translation manager, I get a fatal error :
FatalThrowableError in helpers.php line 114:
Call to undefined method Illuminate\Translation\Translator::inPlaceEditing()

Did I miss something in the install/upgrade process ?

Are you sure you have the correct configuration in your app.php
        Vsch\TranslationManager\ManagerServiceProvider::class,
        Vsch\TranslationManager\TranslationServiceProvider::class,

See: https://github.com/vsch/laravel-translation-manager/wiki/Installation

@loranger, it looks like translator service is not replaced by one provided by LTM and is still the original one.
Check out step 2. of Installation
Please verify that the config/app.php still has the changes needed to use the LTM provided translation service.

Thanks for your replies,
I used to use the v 2.0 which worked perfectly. Thus, the official translator service was already replaced by the service providers of your (awesome, by the way) package :

    'providers' => [
        ...
        //Illuminate\Translation\TranslationServiceProvider::class,
        Vsch\TranslationManager\ManagerServiceProvider::class,
        Vsch\TranslationManager\TranslationServiceProvider::class,
        ...

If you DID NOT comment out this line:
        Illuminate\Translation\TranslationServiceProvider::class,
and if it is after
        Vsch\TranslationManager\TranslationServiceProvider::class,
it will still override the vsch/ltm translation service provider class. and you will get this error. If this is not your problem, then I think we need more information because I can't really think about anything else...

The providers array sample above is a copy-paste from my app.php, but you are right, this was the problem :
I now uses https://github.com/overtrue/laravel-lang and his service provider was overriding your. I did switch the order and the translation manager now works. I suppose Overture does not anymore...
    'providers' => [
        ...
        //Illuminate\Translation\TranslationServiceProvider::class,
        Overtrue\LaravelLang\TranslationServiceProvider::class,
        Vsch\TranslationManager\ManagerServiceProvider::class,
        Vsch\TranslationManager\TranslationServiceProvider::class,
        ...
    ],

Thanks for your package and for your support !


factorio-experimental, factorio-headless-experimental: 1.1.1 -> 1.1.2

Motivation for this change
Update factorio experimental to latest version 1.1.2.
Changelog: https://forums.factorio.com/viewtopic.php?f=3&t=92158
Things done

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

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

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

Sorry, you were bit late. But maybe you can review #105231?


updated javascript/typescript chapter

right back at you :)!
in this PR:

deleted some old recommendations/tools/practices
updated links or deleted them as necessary
splitted bash sudo apt-get line over multiple lines, so each line can be explained (I added the hashtags but could you fill in the comments in a later commit?)
I tried to adhere to a one-sentence-per-line in multi-sentence paragraphs, to facilitate easier diffing, as you would in e.g. latex

Thanks for merging,
-Jurriaan

Looks good to me. I'm not authorized to merge the pull request however.


What about playback speed feature?

What about playback speed feature? :)

i think this feature is very useful

There is an ongoing PR about that: https://github.com/luanpotter/audioplayers/pull/234
please help out finishing it off so that it can be merged!

Duplicated


[Help] Implement chaining(composition) of keystrokes?

Is there a way to chain input events into functions such as on_pre_event, on_pre_event_inner etc? or any workaround? I am trying to implement vim-like keybindings into my terminal application and would like to support commands such as gg, 2d, 12G, etc. AFAIK, Event type could be a character or chained with some modifier such as CtrlChar and so on. I am looking to chain multiple alphanumeric keys, without any limitation on length. For example, 2d will delete two items down, 20G will select the 20th item in SelectView, etc.
Any help would be greatly appreciated,
Thanks,
Hitesh Paul

Hi!
This sounds like a great use-case.
To be compatible with most views, the easiest solution would be to convert these "chained" events into regular events.
OnEventView is not ideal for that as you'd have to set individual callbacks for each event (each letter/number).
Instead, you could write your own WrapperView and override wrap_on_event. For testing, you can also just use a Canvas:
Using the new EventResult::and:
let main_view = make_main_view();
let mut previous_keys = Vec::new();
let canvas = Canvas::wrap(main_view)
    .with_on_event(move |child, event: Event| {
        if should_intercept(&event, &previous_keys) {
            previous_keys.push(event);
            // Combine the events into something bigger, for example 20x down
            let mut result = EventResult::Ignored;
            for _ in 1..20 {
                result = result.and(child.on_event(Event::Key(Key::Down)));
            }
            result
        } else {
            child.on_event(event)
        }
    });

Or, using the new Cursive::on_event:
// ...
        if chain_event(&event, &previous_keys) {
            previous_keys.push(event);
            // Combine the events into something bigger, for example 20x down
            EventResult::with_cb(|siv| {
                for _ in 1..20 {
                    siv.on_event(Event::Key(Key::Down));
                }
            })
        } else {
            child.on_event(event)
        }
// ...

The second example will have the simulated input go all the way the view tree, including this wrapper, so it can only simulate events it itself does not intercept. It will also let cursive react to any callback caused by the simulated events: if scrolling down triggers a popup to show, the first solution will still scroll down 20 times, then show the popup (possibly multiple times); while the second example will show the popup and this popup may consumes the remaining "down" events.

Hi, Sorry for the late reply, I was writing some error handling for the app.
Your first solution works like a charm, although I haven't tested the corner cases such as popup windows, etc. I will test some corner cases and will give the second solution a try. If I encounter any strange behaviour, I will report it here. For now, I am closing this issue.
Thanks,

Glad to hear it solved your issue!
As a note, Canvas can be convenient to quickly try something like that, but if you never change the callbacks, it can be a bit more efficient to define your own type and implement View (or ViewWrapper) on it. This way, you will get static dispatch (Canvas is doing dynamic dispatch for all methods).

Thanks for the suggestion! I tried ViewWrapper, but it seems according to my use-case, creating a custom struct and implementing View trait would be beneficial(Because I need to pass more arguments to callback functions, such as set_on_select for SelectView, where I am currently limited to &mut Cursive and &T.
I am stuck with the following thing(It's not related to this issue, but opening a new one for the same isn't worth either, so I'm mentioning here). My current project structure looks like the following:
struct MyApp {
   siv: Cursive,
   field1: fieldType1,
   field2: fieldType2,
   ...
}

impl MyApp {
   pub fn new() -> Self {
   // some code
   }

   pub fn add_tab(&mut self, param1, param2) -> Self {
   let mut sel_view = SelectView::default();
   // Add items to the view

   // Add key-bindings
   let event_view = OnEventView::new(sel_view)
        .on_pre_event_inner('k', |s| {})
        .on_pre_event('h', |siv: &mut Cursive| {
        // How can I use a field of the current struct?
        // For example, I want to use self.field1 to compute
        // in order to process this callback
        let some_value = some_function(&self.field1);
        });
   self.siv.add_layer(event_view);
   }

How can I use a field of my struct inside callbacks, like on_pre_event, add_global_callback, etc?
This is my first major project in Rust and I have spent a fair amount of time figuring out how this can be implemented(I am coming from an OO programming background), but couldn't find a way.
I also tried to figure out, how does OnEventView gets access to Cursive object? I tried implementing something similar but no luck! If you could help me with some pointers or ideas, I would greatly appreciate it!
Thanks,
Hitesh Paul
Link to source code if needed.

Your code in, say, on_pre_event, needs to access a variable. There are multiple options for this to happen, from most specific to most general:

The code can be "given" access to a variable when it executes, as part of the closure arguments. In most callbacks, this happens for &mut Cursive, but since the interface of the closure is fixed, you cannot add much more than that. Note the in the case of on_pre_event_inner, the value given is the wrapped view, SelectView in this case. So if the field you need is there, you can use that.
The code can "own" a variable: if you declare your closure as "move" (move || {}), it will try to own exclusively the variables it captures. This is useful if the closure is the only place where you access this variable, for example an accumulator.
The code can "share" a variable: using Rc (and RefCell if you need mutability), you can keep multiple "references" to the same data. For this, you need to keep a field1: Rc<RefCell<FieldType1>>. You can give a clone of the Rc to the closure in your callback, and it will reference the same FieldType1.

Thanks for the pointers and detailed explanation! It solved my problem. I resorted to using Rc<RefCell> type. It seems I have to polish some untouched corners of Rust programming :smiley:
Thanks again,
Hitesh Paul


add AMM call to get_strk_gas_price(), WIP

This change is

Codecov Report

Merging #941 (8ffe9c3) into main (8787ee1) will decrease coverage by 0.53%.
The diff coverage is 51.92%.

:exclamation: Current head 8ffe9c3 differs from pull request most recent head 779421e. Consider uploading reports for the commit 779421e to get more accurate results

@@            Coverage Diff             @@
##             main     #941      +/-   ##
==========================================
- Coverage   68.78%   68.25%   -0.53%
==========================================
  Files          44       44
  Lines        5942     5988      +46
  Branches     5942     5988      +46
==========================================
  Hits         4087     4087
- Misses       1480     1526      +46
  Partials      375      375

Files
Coverage Δ

crates/blockifier/src/fee/strk_gas_price/errors.rs
0.00% <ø> (ø)

...tes/blockifier/src/fee/strk_gas_price/gas_price.rs
96.42% <96.42%> (ø)

crates/native_blockifier/src/py_block_executor.rs
31.62% <0.00%> (-7.74%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[11.x] Introduce Schedule Grouping

Description
This PR introduces a new feature allowing related schedules to be grouped, similar to the Route::group method.
With this addition, developers can configure multiple schedules collectively, reducing the need for repetitive configuration of individual schedules.
Looking forward to your feedback. Thanks for all the great work that you guys do! 😍
Current Behavior
Schedule::command('command-one')->everyMinute()->runInBackground()->withoutOverlapping();
Schedule::command('command-two')->everyMinute()->runInBackground()->withoutOverlapping();
Schedule::command('command-three')->everyMinute()->runInBackground()->withoutOverlapping();

With This PR
Schedule::group()
    ->everyMinute()
    ->runInBackground()
    ->withoutOverlapping()
    ->schedules(function () {
        Schedule::command('command-one');
        Schedule::command('command-two');
        Schedule::command('command-three');
    });

Individual schedules can override group configurations as needed:
Schedule::group()
    ->everyMinute()
    ->runInBackground()
    ->withoutOverlapping()
    ->schedules(function () {
        Schedule::command('command-one');
        Schedule::command('command-two');
        Schedule::command('command-three')->everyTenMinutes();  // Override the group's cron expression
    });

Nested grouping is also supported:
Schedule::group()
    ->runInBackground()
    ->withoutOverlapping()
    ->schedules(function () {
        Schedule::group()->everyMinute()->schedules(function () {
            Schedule::command('command-one');
            Schedule::command('command-two');
        });

        Schedule::group()->everyTenMinutes()->schedules(function () {
            Schedule::command('command-three');
            Schedule::command('command-four');
        });
    });

Past similar proposals: #49832 #48046

Hope this will be merged. I think about this every time I call runInBackground for each event.

I'd prefer a syntax like this:
Schedule::group(function () {
    Schedule::command('command-one');
    Schedule::command('command-two');
})
    ->runInBackground()
    ->withoutOverlapping()
    ->everyMinute();

Thanks for the suggestion, @rodrigopedra!
In my view, the suggested syntax makes the chaining feel a bit less clean and slightly harder to follow. Keeping these configurations at the start helps highlight the group’s behavior, improving readability and clarity overall.
That said, if there’s strong preference for this approach, I’m definitely open to revisiting the implementation.

My preference is that it would be more inline with the route group feature, mentioned as inspiration for this feature.
Also, in my opinion, it is more declarative.
But let's wait for the maintainer's opinion.
Other than that, I think this is a great addition!

I'd prefer a syntax like this:
Schedule::group(function () {
    Schedule::command('command-one');
    Schedule::command('command-two');
})
    ->runInBackground()
    ->withoutOverlapping()
    ->everyMinute();

I agree! This is more inlined with how Laravel handles fluent route method.

@Rizky92 @rodrigopedra I looked into the route group feature again, and it seems that using the syntax you suggested doesn’t apply the group options to the routes.
For example:
Route::group([], function () {
    Route::get('/test', fn () => 'Admin Dashboard')->name('home');
})
    ->name('admin.') // doesn’t affect routes
    ->prefix('/admin'); // doesn’t affect routes

Instead, it needs to be structured like this:
Route::name('admin.')
    ->prefix('/admin')
    ->group(function () {
        Route::get('/test', fn () => 'Admin Dashboard')->name('home');
    });

This setup aligns with my suggested syntax. But let’s see what the maintainers think before making any changes. 🙏

Really would love to finally get this in the framework in some form. I am in agreement that consistency with the documented Route group syntax would be awesome where group is at the end and accepts a Closure.

@taylorotwell I can think of two ways to implement the Route::group-style syntax:

Implement it similarly to the Router class, using __call to proxy relevant method calls to a "Schedule Grouper." This keeps event attributes separate from the Schedule class, as they are currently, but doesn’t provide native IDE auto-completion.

Alternatively, duplicate the relevant methods from the Scheduling\Event class into the Schedule class to ensure auto-completion support.

Let me know which direction you'd prefer!

@taylorotwell I can think of two ways to implement the Route::group-style syntax:

Implement it similarly to the Router class, using __call to proxy relevant method calls to a "Schedule Grouper." This keeps event attributes separate from the Schedule class, as they are now, maintaining a clean structure but lacking native IDE auto-completion.

Alternatively, duplicate the relevant methods from the Scheduling\Event class into the Schedule class to ensure auto-completion support.

Let me know which direction you'd prefer!

How about extracting the relevant method to a trait and use that trait on both classes? That way, you get auto completion without duplicating the methods?

@morloderex Thanks for the reminder! That’s actually what I had planned to do; I just forgot to mention it. I’ve updated my previous reply to reflect this.

@taylorotwell I've taken a closer look at the codebase to explore implementing the syntax through the second method if we go that route. I've identified some potential side effects with this approach.
For example, end users could write:
Schedule::runInBackground()->command('command-one');

While that seems fine (similar to routes), issues arise with the callback event. The Schedule::call returns a CallbackEvent instance, which overrides some methods of the parent Event class.
For instance, runInBackground is prohibited for callback event:
Schedule::call('command-one')->runInBackground(); // Throws `RuntimeException`

Allowing runInBackground before knowing the event type prevents us from replicating this behavior.
A solution could be to only allow group to be called after event attribute methods or to add a check in Schedule::call before creating the event. Both options add complexity.
What do you think?

Wondering if it would work by just making runInBackground return somekind of shadow object which is just to allow chaining in this case then? And not actually make it throw the exception anymore. And then add a note in the docs for this specific method chain?

@morloderex That approach is possible, but it would completely change the current behavior, which may cause existing tests to fail and go against end-users' existing expectations. It might also be considered a breaking change, though I'm not entirely sure.
For now, it may be best to wait for feedback from @taylorotwell or other maintainers.

@stevebauman @taylorotwell I’ve updated the implementation to follow Route::group syntax, please review 🙏.
Here’s an example of the new Schedule group usage:
Schedule::everyMinute()
    ->runInBackground()
    ->withoutOverlapping()
    ->group(function () {
        Schedule::command('command-one');
        Schedule::command('command-two');
        Schedule::command('command-three')->everyTenMinutes();
    });

Additionally, this implementation allows users to declare schedules similarly to Route, like this:
Schedule::hourly()->command('inspire');

Thanks @istiak-tridip!

Strange but I get
Undefined property: Illuminate\Console\Scheduling\PendingEventAttributes::$mutex, vendor/laravel/framework/src/Illuminate/Console/Scheduling/ManagesAttributes.php, 145

when I use group with withoutOverlapping and run schedule:run.
Schedule::runInBackground()
    ->withoutOverlapping()
    ->everyMinute()
    ->group(function () {
        Schedule::command(FetchSchedule::class);
    });

If I comment withoutOverlapping Schedule works.

@decadence I was able to reproduce the issue and have submitted a bug fix in PR #53553. Could you please test the fix and share your feedback on the PR?
Thanks!


Latest TensorFlow fails to install due to yesterday's Keras requirement change

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):  Linux Ubuntu
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary):
TensorFlow version: latest as of https://github.com/tensorflow/tensorflow/commit/ca0fa154128d793df5e6809cb86336ac1fed3466
Python version: python3.8
Installed using virtualenv? pip? conda?: pip
Bazel version (if compiling from source):  3.7.2
GCC/Compiler version (if compiling from source): GCC9.3
CUDA/cuDNN version: NA
GPU model and memory: NA

Describe the problem
Build was successful, but installation of the wheel failed with the following Error message
09:34:20  ERROR: No matching distribution found for keras<2.8,>=2.7 (from tensorflow==2.8.0)
Provide the exact sequence of commands / steps that you executed before running into the problem
pip install /tmp/pip3/tensorflow-2.8.0-cp38-cp38-linux_x86_64.whl
Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.
You can take a detailed look here: https://tensorflow-ci.intel.com/job/tensorflow-mkl-build-whl-nightly/941/console

Broken for Linaro CI as well.
https://ci.linaro.org/job/ldcg-python-manylinux-tensorflow-nightly/123/console
The subtype: label for Ubuntu seems wrong, this is not related to the OS in use.

Could please provide the link or document of wheel file which you are trying.Thanks.

@sachinprasadhs , this is a link that shows we were able to build TensorFlow successfully. But failed at installation steps.
https://tensorflow-ci.intel.com/job/tensorflow-mkl-build-whl-nightly/942/console
02:46:49  INFO: Elapsed time: 2622.058s, Critical Path: 429.44s
02:46:49  INFO: 11295 processes: 1302 internal, 9993 local.
02:46:49  INFO: Build completed successfully, 11295 total actions
02:46:49  INFO: Build completed successfully, 11295 total actions
02:46:49  Fri Oct 8 09:46:36 UTC 2021 : === Preparing sources in dir: /tmp/tmp.2qdIZr4JRR
02:46:49  /tensorflow /tensorflow
02:47:01  /tensorflow
02:47:01  /tensorflow/bazel-bin/tensorflow/tools/pip_package/build_pip_package.runfiles/org_tensorflow /tensorflow
02:47:01  /tensorflow
02:47:01  /tmp/tmp.2qdIZr4JRR/tensorflow/include /tensorflow
02:47:01  /tensorflow
02:47:01  Fri Oct 8 09:47:00 UTC 2021 : === Building wheel
02:47:01  warning: no files found matching 'README'
02:47:01  warning: no files found matching '.pyd' under directory ''
02:47:02  warning: no files found matching '.pyi' under directory ''
02:47:02  warning: no files found matching '.pd' under directory ''
02:47:03  warning: no files found matching '.dylib' under directory ''
02:47:04  warning: no files found matching '.dll' under directory ''
02:47:04  warning: no files found matching '.lib' under directory ''
02:47:04  warning: no files found matching '.csv' under directory ''
02:47:04  warning: no files found matching '.h' under directory 'tensorflow/include/tensorflow'
02:47:04  warning: no files found matching '.proto' under directory 'tensorflow/include/tensorflow'
02:47:04  warning: no files found matching '*' under directory 'tensorflow/include/third_party'
02:47:51  Fri Oct 8 09:47:45 UTC 2021 : === Output wheel file is in: /tmp/pip3
02:47:51  Processing /tmp/pip3/tensorflow-2.8.0-cp38-cp38-linux_x86_64.whl
02:47:51  Requirement already satisfied, skipping upgrade: wheel<1.0,>=0.32.0 in /usr/lib/python3/dist-packages (from tensorflow==2.8.0) (0.34.2)
02:47:51  Collecting google-pasta>=0.1.1
02:47:51    Downloading google_pasta-0.2.0-py3-none-any.whl (57 kB)
02:47:51  Collecting tensorflow-io-gcs-filesystem>=0.21.0
02:47:51    Downloading tensorflow_io_gcs_filesystem-0.21.0-cp38-cp38-manylinux_2_12_x86_64.manylinux2010_x86_64.whl (2.1 MB)
02:47:51  Requirement already satisfied, skipping upgrade: h5py>=2.9.0 in /usr/local/lib/python3.8/dist-packages (from tensorflow==2.8.0) (3.4.0)
02:47:51  Requirement already satisfied, skipping upgrade: keras-preprocessing>=1.1.1 in /usr/local/lib/python3.8/dist-packages (from tensorflow==2.8.0) (1.1.2)
02:47:51  Requirement already satisfied, skipping upgrade: six>=1.12.0 in /usr/lib/python3/dist-packages (from tensorflow==2.8.0) (1.14.0)
02:47:51  Collecting wrapt>=1.11.0
02:47:51    Downloading wrapt-1.13.1-cp38-cp38-manylinux2010_x86_64.whl (84 kB)
02:47:51  ERROR: Could not find a version that satisfies the requirement keras<2.8,>=2.7 (from tensorflow==2.8.0) (from versions: 0.2.0, 0.3.0, 0.3.1, 0.3.2, 0.3.3, 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.1.0, 1.1.1, 1.1.2, 1.2.0, 1.2.1, 1.2.2, 2.0.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.5, 2.0.6, 2.0.7, 2.0.8, 2.0.9, 2.1.0, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.1.6, 2.2.0, 2.2.1, 2.2.2, 2.2.3, 2.2.4, 2.2.5, 2.3.0, 2.3.1, 2.4.0, 2.4.1, 2.4.2, 2.4.3, 2.5.0rc0, 2.6.0rc0, 2.6.0rc1, 2.6.0rc2, 2.6.0rc3, 2.6.0, 2.7.0rc0)
02:47:51  ERROR: No matching distribution found for keras<2.8,>=2.7 (from tensorflow==2.8.0)
In general, the installation is checking keras<2.8, and >=2.7. Looks like pypi keras is not released with v2.7?


Added new features from latest update to README.md, added TUTORIALS.txt as stopgap location for advanced NF usage

Added new features from latest update to README.md, added TUTORIALS.txt as stopgap location for advanced NF usage

Changes made

Looks good merged.


Rust SDK

I found the Rust SDK in Roadpmap, are there any official implementation now?
I'm working on a prototype rust-dapr for Rust binding, may I contribute some code to the Rust SDK?

Hey @flier, based on what you've done and other feedback we received, we've created a repository for the official Rust SDK. We'd love if you get involved and can help us get it and up and running.
https://github.com/dapr/rust-sdk

@ayax79

@flier @ayax79 I'd like to help out with a Rust SDK. @flier's gRPC based implementation looks promising. Perhaps we should use that as a basis for the official SDK?

@rylev
Yes, the prototype depends on the async/await support, it will be available in the 1.39 release  (November 7th, 2019). I believe this is the direction of the Rust community.
If you prefer to provide a traditional synchronous version, we can repackage based on the asynchronous API (need 1.39 or later), or reimplement another set of synchronization APIs with grpc-rust.
What's your opinion?

@flier let's base it on the 1.39 release, we are starting fresh here, it's better to start with latest, it's better from future support matrix perspective as well.

I’m also of the opinion we should base this on async/await. @flier I can start adding the very basics to the repo based on what you did in your repo. I’ll make sure to ping you in the PR

@amanbha Thanks
@rylev Sure, what's your username at crates.io? let's me transfer the dapr/dapr-derive crates owner to you.

@flier it should be the same as my GitHub username.

@flier I should also make it clear, we'd love your help with all of this! I don't mean to take over the development :-D This should be an opportunity for collaboration

@rylev Sure, I just need an official Rust SDK, and involve community, including me, can contribute code to it :)

Just to close out this conversation, I have a PR open on the new repo: https://github.com/dapr/rust-sdk/pull/2
It's based on @flier's work but makes some design changes that should be discussed. It's only the very beginning, so lots of room for discussion and collaboration!

Sweet! Looking forward to checking this out.


Add additional information to the metadata of the tuple, link to the tuple and its type.

done

done


OnDemandOrderingGate: refactor subject to observable chain

Signed-off-by: Andrei Lebedev<EMAIL_ADDRESS>

Description of the Change

Benefits

Possible Drawbacks

Usage Examples or Tests [optional]

Alternate Designs [optional]

Redundant


Strobe interface

Great use of a single display: https://www.youtube.com/watch?v=BUl0QvCrVIU
Or classic: https://www.youtube.com/watch?v=U9HJiiLz_5w

I like this project very much, but I can't run. Because the project is a bit old, a lot of dependency no longer exists, I did not use the webpack, hoping to get help.

Thank you for your timely reply to my information.I'm going to keep an eye on this project right now.

I'm really sorry I came to see the project again.

I'm a piano tuner, I like this project, but I can't successfully install dependencies now.I want to make a tuning WeChat Mini Program，For my students.Hope to update soon.

Thanks a lot for the reminder, @huanhuanhome ! Let me see if I can hack in updates over the holidays.

@digitarald Thank you so much


Possible credits

Hey Nooz,
I made wrote the def opts and main duinotize script for you awhile ago so it used an object instead of id based html items, i would appreciate it if you added some credits.
thank you, oxmc

👍


Slow application rendering (i.e. - slow resizing, slow preference dialog closing).

case 181332

For me the program is reasonably snappy (as much as I would expect from a winforms-wpf hybrid).
I will test this next week on a slower machine.

Tested on a 5 year old machine (Intel U3100 @ 1.3 ghz).
Performance is pretty bad. Most actions can take up to a second or two, especially the first time (opening auto complete, selection time entry, saving settings...)

Before we can do much about this, we need to:

[ ] discuss what our performance goals are
[ ] set up code to measure performance of a variety of systems
[ ] collect data from a number of different platforms
[ ] use that data to decide where optimizations are worthwhile.

This issue is on hold for now, until we are able to collect a lot more data.
Several improvements to the performance have already been done however, which might solve the problems for almost everybody.


Remove outdated example configs.

Maybe these could be updated instead of removed?

@MarkusTeufelberger SysVInit is essentially deprecated in the Linux world in favor of SystemD.

Yes, but you also want to remove the Systemd unit file. I agree about the SysVInit one (though there are still a few rebels out there, e.g. Alpine Linux, which is relatively often used in Docker base containers, but then again these don't need a service file).

SysVInit is essentially deprecated in the Linux world in favor of SystemD.

And how sad and unfortunate is that... :cry:
But more to the point: I'm not sure if we want these in the repo; they're borderline distribution-specific and I'm not sure they help very much as is. It'd be different if we had a "packages" folder with code to built distribution-specific packages and those files were in the appropriate folder, but as is they feel a bit random.

merged as e98c76110


Tasks can't be started on an EC2 instance

There was an issue with one of EC2 instances, so I've terminated it and the ASG has started new one. For some reason, the containers are not starting up on the new instance. They fail with (from /var/log/docker):
time="2018-03-02T10:07:55Z" level=info msg="2018/03/02 10:07:55 http: panic serving @: runtime error: invalid memory address or nil pointer dereference" plugin=3c95129f659d2d162550065c4200980c15d8d2ce25c002c9f01f96c84f3ea636
time="2018-03-02T10:07:55.565099089Z" level=warning msg="Unable to connect to plugin: /run/docker/plugins/3c95129f659d2d162550065c4200980c15d8d2ce25c002c9f01f96c84f3ea636/firecampvol.sock/VolumeDriver.Mount: Post http://%2Frun%2Fdocker%2Fplugins%2F3c95129f659d2d162550065c4200980c15d8d2ce25c002c9f01f96c84f3ea636%2Ffirecampvol.sock/VolumeDriver.Mount: EOF, retrying in 1s"

So, no volumes are mounted.
[root@ip-172-22-2-212 log]# docker ps
CONTAINER ID        IMAGE                                        COMMAND             CREATED             STATUS              PORTS               NAMES
634ef2c0ea2f        cloudstax/firecamp-amazon-ecs-agent:latest   "/agent"            5 hours ago         Up 5 hours                              ecs-agent
[root@ip-172-22-2-212 log]# docker plugin ls
ID                  NAME                               DESCRIPTION                                     ENABLED
3c95129f659d        cloudstax/firecamp-volume:latest   firecamp volume plugin for docker               true
656134559eb0        cloudstax/firecamp-log:latest      firecamp log plugin for docker: consume lo...   true

The only thing I did against this cluster recently was killing firecamp-manageserver task to make it updated to the latest.
Other two cluster nodes work w/o issues.
The only difference I see is the agent version:
grep Agent /var/log/firecamp/firecamp-dockervolume.INFO

"Amazon ECS Agent - v1.16.2 (*55b7b5f)" - at the new (non-working) instance
"Amazon ECS Agent - v1.16.0 (*e24ae08)" - at working instances
Please, help me to figure that out!

Thanks for reporting the issue! Killing the manageserver task will not cause this issue. Did you collect the logs on the node before terminating it? The /var/log/firecamp/*. Could you please collect them if you could reproduce the issue?

No, I didn't collect the logs, but the issue is still in place. There's only one file in /var/log/firecamp: firecamp-dockervolume.ip-172-22-2-212.root.log.INFO.20180302-100613.6
You may get it here: http://termbin.com/dva2

Thanks! Could you please use cli to send a list member request and collect the manageserver logs in cloudwatch?

The command is like: ./firecamp-service-cli -cluster=firecamp-qa -op=list-members -service-name=kafka-qa

One more question: when was service kafka-qa created? The cluster has been there for a long time?

Very strange:
# ./firecamp-service-cli -cluster=firecamp-qa -op=list-members -service-name=kafka-qa
2018-03-02 21:12:00.228983364 +0000 UTC ListServiceMember error Get http://firecamp-manageserver.firecamp-qa-firecamp.com:27040/?List-ServiceMember: EOF

CW logs during that call:
I0302 21:09:08.369488 1 server.go:114] request Method GET URL /?List-ServiceMember ?List-ServiceMember Host firecamp-manageserver.firecamp-qa-firecamp.com:27040 requuid req-b906e338444c4fe359c3f2d196b75eae headers map[User-Agent:[Go-http-client/1.1] Content-Length:[100] Accept-Encoding:[gzip]]
I0302 21:09:08.369764 1 server.go:743] listServiceMembers &{us-east-1 firecamp-qa kafka-qa } requuid req-b906e338444c4fe359c3f2d196b75eae
I0302 21:09:08.406271 1 dynamodb_service.go:81] get service &{firecamp-qa kafka-qa ae9a07f638c145866458232d81edbead} requuid req-b906e338444c4fe359c3f2d196b75eae
I0302 21:09:08.411854 1 dynamodb_servicemember.go:270] list serviceMembers succeeded, serviceUUID ae9a07f638c145866458232d81edbead limit 0 requuid req-b906e338444c4fe359c3f2d196b75eae resp count 0xc420624a38
2018/03/02 21:09:08 http: panic serving <IP_ADDRESS>:40344: runtime error: invalid memory address or nil pointer dereference
goroutine 74 [running]:
net/http.(*conn).serve.func1(0xc420606000)
/usr/local/go/src/net/http/server.go:1721 +0xd0
panic(0x1556be0, 0x220cb80)
/usr/local/go/src/runtime/panic.go:489 +0x2cf
github.com/cloudstax/firecamp/db/awsdynamodb.(*DynamoDB).attrsToServiceMember(0xc4203a5d10, 0xc42061b1c0, 0x20, 0xc420604ff0, 0x0, 0xc420601d80, 0x31)
/home/junius/work/go/src/github.com/cloudstax/firecamp/db/awsdynamodb/dynamodb_servicemember.go:383 +0x8f9
github.com/cloudstax/firecamp/db/awsdynamodb.(*DynamoDB).listServiceMembersWithLimit(0xc4203a5d10, 0x7f2a9c288bb0, 0xc4206321e0, 0xc42061b1c0, 0x20, 0x0, 0x2220a20, 0x0, 0xc4201776c0, 0x4, ...)
/home/junius/work/go/src/github.com/cloudstax/firecamp/db/awsdynamodb/dynamodb_servicemember.go:288 +0xba5
github.com/cloudstax/firecamp/db/awsdynamodb.(*DynamoDB).ListServiceMembers(0xc4203a5d10, 0x7f2a9c288bb0, 0xc4206321e0, 0xc42061b1c0, 0x20, 0xc420634288, 0x8, 0xc420514390, 0x0, 0x0)
/home/junius/work/go/src/github.com/cloudstax/firecamp/db/awsdynamodb/dynamodb_servicemember.go:229 +0x66
github.com/cloudstax/firecamp/manage/server.(*ManageHTTPServer).listServiceMembers(0xc4207247e0, 0x7f2a9c288bb0, 0xc4206321e0, 0x21c9820, 0xc4205e01c0, 0xc42000ac00, 0xc4206321b0, 0x24, 0x0, 0x1365642, ...)
/home/junius/work/go/src/github.com/cloudstax/firecamp/manage/server/server.go:751 +0xabc
github.com/cloudstax/firecamp/manage/server.(*ManageHTTPServer).getOp(0xc4207247e0, 0x7f2a9c288bb0, 0xc4206321e0, 0x21c9820, 0xc4205e01c0, 0xc42000ac00, 0xc4206320f5, 0x13, 0xc4206321b0, 0x24, ...)
/home/junius/work/go/src/github.com/cloudstax/firecamp/manage/server/server.go:573 +0x50b
github.com/cloudstax/firecamp/manage/server.(*ManageHTTPServer).ServeHTTP(0xc4207247e0, 0x21c9820, 0xc4205e01c0, 0xc42000ac00)
/home/junius/work/go/src/github.com/cloudstax/firecamp/manage/server/server.go:133 +0xce8
net/http.serverHandler.ServeHTTP(0xc4206ccbb0, 0x21c9820, 0xc4205e01c0, 0xc42000ac00)
/usr/local/go/src/net/http/server.go:2568 +0x92
net/http.(*conn).serve(0xc420606000, 0x21ca560, 0xc4206000c0)
/usr/local/go/src/net/http/server.go:1825 +0x612
created by net/http.(*Server).Serve
/usr/local/go/src/net/http/server.go:2668 +0x2ce

According to ECS console, the kafka service was created on Dec 12 and last updated on Jan 18. Yeah, this is our 1st firecamp cluster, it was created on Dec 12.

Thanks for sharing the detail information! This is an upgrade issue. The "Status" field in ServiceMember was added at Dec 30th for release 0.9.2. So the service created before that will not have the "Status" field. The upgrade is handled after 0.9.2. The data structure change after 0.9.2 is handled, but not before 0.9.2. Is it ok for you to delete the service and recreate it?

Looks like I can't delete it:
# ./firecamp-service-cli -cluster=firecamp-qa -op=delete-service -service-name=kafka-qa
2018-03-05 09:37:34.966205164 +0000 UTC DeleteService error Delete http://firecamp-manageserver.firecamp-qa-firecamp.com:27040/?Delete-Service: EOF

I've tried to downgrade firecamp-manager to 0.9.2 (and use cli of the same version) - no success: same thing in the logs.

Your are right. The latest manageserver is not able to delete the service. It will hit the same issue when listing all service members.
Using the downgraded firecamp-manager would be able to delete the service. For the deletion failure, could you please post the manageserver log?

The old log is not needed. It hits the same listing service member issue.
You mentioned the deletion against the downgraded manager also failed. Do you have that log? Just want to double check there is no any potential issue.

Sorry - this is the one I've deleted. At the moment I have a log of newly created firecamp cluster.
As I mentioned earlier, the delete-service command returned EOF, but it did the actual delete

Thanks. If the newly created service works well, we could close this issue?
One additional note: we can't guarantee the upgrade always works for different versions of the latest release. The latest release is under development. The upgrade from the old version after 0.9.2 to the new version will be supported. If some new fields are added to the service data structure, the cli tool will be provided to upgrade the old service to the new release. We will have the detail guide for it in the next release, for upgrading from release 0.9.4.
If you meet any issue, please feel free to report it. Thanks!

Got it, thank you!


Cherry-pick upstream transform dialect

This cherry-picks a group of upstream commits improving the usability and hardening the transform dialect:

[mlir] verify against nullptr payload in transform dialect
[mlir] improve error handling in Linalg op splitting
[mlir] fix use-after-free on error path in transform dialect
[mlir] adapt TransformEachOpTrait to parameter values
[mlir] NFC: move DiagnosedSilenceableFailure to Utils in Transform dialect
[mlir] NFC: rename TransformTypeInterface to TransformHandleTypeInterface
[mlir] introduce parameters into the transofrm dialect

Cherry-pick policy in IREE has changed. I forwarded you the email.

Sure, whoever does the integrate (I won't) is welcome to reuse this.

Prefetching integration changes in iree is still something we want. If this is what it does I think it should still go in.

It's fine to prefetch changes using cherry-picks on a branch and to prepare patches to fix build/test errors that are imminent. We should be avoiding cherry-picks on the main branch though, as even a single cherry-pick there has costs for all downstream users (including Google's downstream repository, which prompted the discussions about policy changes).
This looks like it could wait until the next rollup, or the IREE changes could be merged to an integrate (or collaboration) branch.

@ftynse thanks for the fixup PR. @hanhanW is on integration this week and I am on it next week.  We can use these changes when we hit this during integrate.
In any case cherry picking 7 at the same time is probably best avoided.

"[mlir] verify against nullptr payload in transform dialect" is not included in https://github.com/iree-org/iree/pull/11763, the fixes are cherry-picked into the PR.


SST tax changes

Please update this page with the changes made from GST to SST.

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

ID: f2178eb4-8295-2846-c926-5de18adfa791
Version Independent ID: be2c67de-df54-0495-81a5-44c8e5e8bb83
Content: Malaysia Goods and Services Tax - Finance & Operations | Dynamics 365 | #MSDyn365FO
Content Source: articles/financials/localizations/apac-mys-gst.md
Service: dynamics-ax-applications
Product: ****
Technology: ****
GitHub Login: @mrolecki
Microsoft Alias: mrolecki

@helicopterpilot, thanks for the feedback.
@mrolecki, please review and consider updating this topic.

@tonyafehr, @RichardLuan should be an owner and consider updating the topic

Bug 379345 has been logged to track this issue.

Please overview below what was mplemented for invoice layout.
To provide requirements for the SST invoice layout the following was implemented:

The new invoice type -Service type  (General ledger > General ledger parameters, Sales tax tab, GST option, Invoice type) has been added.
•	If the Invoice type value is Service tax, then the name of the tax columns is replaced to Service tax.
•	If the Invoice type value is Invoice, then the  he name of the tax columns is Tax
If the invoice currency differs from the legal entity currency then all amounts are output in two currencies in invoice layout.

Note 1: to display sales tax/service tax amount in two currencies it is necessary to set Registration and company currency in the Form setup (Account receivable > Setup > Forms > Form setup, General tab, Sales tax, Sales tax specification field)
Note 2: A user may change the invoice type when creating a Sales order, a Free text invoice before posting..


Clients file member order varies by platform

Today it caught my eye that the order of the members in the generated TypeScript clients file is different on Ubuntu than on Windows. When an API hasn't changed, a different clients file is generated nevertheless when building on a different platform (or perhaps machine). This causes unnecessary VCS commits.
I assume the order is depending on the .NET Runtime, which can be different across versions and platforms. As far as I remember, reflection results don't guarantee order.

The order of DTO properties?

I'm talking about the order of the classes in the clients file. I realize that by calling them 'members' I wasn't very clear.

I think there is already an issue for that, but it would make sense to order operations and classes when generating the spec - problem: might be a breaking change.

Its also important to point out that its not a per-platform difference. I'm only using Windows, and in the linked duplicate all that changed was a method signature.


bug: transactions hash and l1_data_gas_price mismatch with mainnet

Bug Report

The bug on transactions hash was introduced with #134
The bug with l1_data_gas_price mismatch was at least already there in #123

https://rpc-request-builder.voyager.online/
Using starknet_getBlockWithTxHashes, compare on block number 1 the json response over http://localhost:9944 and Mainnet (by clicking on Use default RPC URL)

The response Json from localhost should match with Mainnet.
Its partially working in #133 but not in #134

After further analysis, the problem doesn't seems to come from transactions.rs but lib.rs.
Remark: in #133 the block 0 can be requested, not in #134 (error generated from lib.rs "Block not found")


Issues adding Bootstrap 4

After adding bootstrap 4 (along with popper.js and JQuery). ng build/ng serve is broken.
error message below:
ERROR in ./node_modules/css-loader?{"sourceMap":false,"importLoaders":1}!./node_modules/postcss-loader/lib?{"ident":"postcss","sourceMap":false}!./node_modules/bootstrap/dist/css/bootstrap.min.css
Module build failed: BrowserslistError: Unknown browser major
at error (D:\TestApps\DotNetCoreCli-Bootstrap\ClientApp\node_modules\browserslist\index.js:37:11)
at Function.browserslist.checkName (D:\TestApps\DotNetCoreCli-Bootstrap\ClientApp\node_modules\browserslist\index.js:320:18)
FYI: tried importing boostrap.css in the algular-cli.json and also tried importing it in the styles.css, nothing seems working
When I revert back to bootstrap 3.3.7 it works fine.

This is an Angular CLI usage question, so please direct it to the Angular CLI project. Hope that's OK!


DL-Rail dataset download

Thanks for your great works!
Because i'm not in china, I couldn't download the dataset from Aliyundirve.
Shall you share the dataset to another platform (like gdrive)?.
thanks!

I second this request!
Thank you :)


Add is_deleted filter option to tunnel data source

This PR solves a problem we're having onboarding our services to Cloudflare. The problematic behaviour is already described in #3069.
With the addition of a is_deleted filter we can now ignore soft-deleted entities and get the correct tunnel back from the API.
The filter is utilising the already available IsDeleted parameter of the ListTunnel API.
make test and TESTARGS='-run ^TestAccCloudflareTunnel_Match' make testacc have been running successfully.
I have left the original functionality intact to not force anyone to adopt setting the parameter.
Closes #3069.

I'm unsure about the deletion make docs created for docs/resources/hyperdrive_config.md.
Should I drop them from my PR to make it simpler?

I'm unsure about the deletion make docs created for docs/resources/hyperdrive_config.md.
Should I drop them from my PR to make it simpler?

that looks to be because your branch is out of date with the upstream. if you update it, it should be present.

thanks for the contribution here!
looking at your test though, it doesn't actually do anything. if i comment out your newly added lines, the tests are still passing. i suspect it's related to https://github.com/cloudflare/terraform-provider-cloudflare/pull/3201/files#diff-3efcea7c71b17ecec6cfec3258b6a7d07026abc92fae723c69bad61941b1faeaR59 not actually doing anything.

Even after a rebase the make docs task does not change for me. Since this looks to be a problem for me locally I will remove the change.
The test case is weird. In theory the 3rd step removes the resource as well which is when you comment out the 2nd step you still see the same result. I added the 2nd step to ensure that the 3rd step runs after the resource has been fully removed from state and got deleted from the API. It basically should guard against a race condition for the delete - I hate flaky tests 😄

I have reworked the tests if you don't mind giving it another glance over.

thanks - i went ahead and tidied up the test assertions here as much of it wasn't needed for a minimal test case and was a little confusing as to what was trying to be achieved there.
acceptance tests are all passing
TF_ACC=1 go test ./internal/sdkv2provider -v -run "^TestAccCloudflareTunnel_Match" -count 1 -timeout 120m -parallel 1
=== RUN   TestAccCloudflareTunnel_MatchName
--- PASS: TestAccCloudflareTunnel_MatchName (9.63s)
=== RUN   TestAccCloudflareTunnel_MatchIsDeleted
--- PASS: TestAccCloudflareTunnel_MatchIsDeleted (22.83s)
PASS
ok  	github.com/cloudflare/terraform-provider-cloudflare/internal/sdkv2provider	33.431s


Add meltano list [plugin_type] to list plugins and their installed versions

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2139
Originally created by @nehiljain on 2020-07-07 15:47:30

Original title: Ability to do pip freeze for meltano install
Problem to solve
When I want to modify the version of tap (extractor) I am not able to verify the version of my installation easily
Target audience
A developer managing deployments for meltano
Proposal
Add a command like meltano invoke pip freeze or something along those lines

View 6 previous comments from the original issue on GitLab

Pending further work on the spec, but this is probably a 4.
I also wonder if meltano plugin list makes more sense than meltano list, and #6561 may be relevant.
$ meltano plugin list --help
Usage: meltano plugin list [OPTIONS]...

      List Meltano plugins and their installed versions.

      Read more at https://docs.meltano.com/reference/command-line-interface#plugin

Options:
  --plugin-type [extractor|extractors|loader|loaders|transform|transforms|orchestrator|orchestrators|transformer|transformers|file|files|utility|utilities|mapper|mappers|mapping|mappings]
  --plugin-name                   Only display detail for these plugins.
  --help                          Show this message and exit.


GUI sometimes does not pop up

Please make sure your issue complies with these guidelines:

[ ] Server Software must be the official PMMP w/o vanilla patching plugins (i.e. TeaSpoon)

[ ] Issue must have not been reported previously

[ ] Make sure you are on the latest version of PMMP & PiggyAuctions

[ ] Have a detailed title (i.e "Auctioned items remain in inventory")

Issue Description
https://youtu.be/2pLAv2-RGE4

Expected result: Open up a gui page
Actual result: GUI disappear

Steps to Reproduce the Issue

Do /ah
Click on the option

OS and Versions

PocketMine-MP: Latest
PiggyAuctions: Dev 9 (Latest)
PHP:
Server OS:

Extra Information

What version of Minecraft Bedrock are you on?

What version of Minecraft Bedrock are you on?

?

Why did you close the issue?

?

Sorry i updated the comment


Add support for WPA3 (SAE) on Linux

wpa_supplicant will use SAE, if required by the network. Support for WPA3 is required as part of v1.0 of the Matter Specification (refer to <IP_ADDRESS> for details).
Fixes #23402.

 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.

@afeatherstone-mm what are the preconditions for this value to be supported?
Is there any documentation you can link that describes possible values to key_mgmt and since when is SAE supported? Is the given value always ok or will we require some recent versions of a wifi networking stack/kernel/others?

Maybe linking to something like https://www.systutorials.com/docs/linux/man/5-wpa_supplicant.conf/ and https://w1.fi/wpa_supplicant/devel/dbus.html (the latter says that AddNetwork args correspond to a dictionary in wpa_supplicant configuration file) would help.
I can see in config examples that space-delimited entries work, so that seems fine. I am not sure how to find out if there are any restrictions in when SAE would be supported.

For example https://wiki.archlinux.org/title/wpa_supplicant claims that 6.7 Connections to mixed WPA2-PSK/WPA3-SAE access points should use key_mgmt=WPA-PSK-SHA256

Thanks for the feedback. I'll try and address the questions in turn.

what are the preconditions for this value to be supported?

The target's build of wpa_supplicant needs to be able to have SAE support. This has been present in the source code of  wpa_supplicant since 2014-02-04 - v2.1[1].
The target distro's package maintainers needs to have built wpa_supplicant with SAE support. This is enabled by default[2], so it'd be a conscious action by the package maintainer to remove support.

Ubuntu 20.04.05 LTS and Raspberry Pi OS (32-bit) 2022-09-22 are two examples of distros that have support in their builds of wpa_supplicant. I'd expect any current releases of Debian, CentOS, Fedora would similarly have support, but I haven't checked those.

Is there any documentation you can link that describes possible values to key_mgmt and since when is SAE supported?

For a running instance of wpa_supplicant the control interface can be used to determine what key_mgmt values are valid at run-time. e.g.
# wpa_cli get_capability key_mgmt
Selected interface 'wlan0'
NONE IEEE8021X WPA-EAP WPA-PSK OWE DPP FT-PSK FT-EAP SAE

Is the given value always ok or will we require some recent versions of a wifi networking stack/kernel/others?

The distro/package maintainer could remove support for their version of wpa_supplicant, so in the strictest sense, no I can't guarentee it will always be ok. In practice, I think this is fine for any "recent" (current and previous LTS or equivalent) mainstream Linux distro, and is consistent with the assumptions already made in this codebase.
A completely robust implementation would use the D-Bus API to wpa_supplicant's control interface to read the capabilities, and then match those up with what the Matter Spec requires. This isn't done currently, and I think for the sake of an example application is overly complicated.
[1] https://w1.fi/cgit/hostap/plain/wpa_supplicant/ChangeLog
[2] https://w1.fi/cgit/hostap/tree/wpa_supplicant/defconfig#n255

Any news here?


Ignore build user umask

The pkg-config file /usr/local/lib/pkgconfig/libqpdf.pc seems to be installed with the umask of the build user.
$ umask
0007
$ wget --quiet https://github.com/qpdf/qpdf/releases/download/release-qpdf-8.4.0/qpdf-8.4.0.tar.gz
$ tar xf qpdf-8.4.0.tar.gz
$ cd qpdf-8.4.0/
$ ./configure --disable-check-autofiles --disable-static
$ make
$ sudo make install
$ ls -l /usr/local/lib/pkgconfig/libqpdf.pc
-rw-r----- 1 root root 246 Apr 25 16:49 /usr/local/lib/pkgconfig/libqpdf.pc

I have to check if there is a standard for that, but wanted to report it.

Hmm, the issue for GNU Automake says that files are supposed to be installed with install -m 755 and that the problem only exists for directories. So this issue seems different.
For the record:
$ automake --version
automake (GNU automake) 1.15
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl-2.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Tom Tromey<EMAIL_ADDRESS>       and Alexandre Duret-Lutz<EMAIL_ADDRESS>

This is probably because my make install target just uses cp instead of, say, install. I don't use automake at all in qpdf. I can probably fix the installation to use install if available.


Why does Eloquent use its own file type for bibles?

It's not easy to convert to and from, as it's not documented anywhere, to my knowledge. It would be great if Eloquent used a more wide-spread format.

I'm not sure I understand your question.
Eloquent uses the format of bibles, commentaries, etc. that are available for SWORD at CrossWire.
The module installer in fact installs official SWORD compatible modules.
In addition to that Eloquent understands folder that have the suffix .swd and contain subfolders with "mods.d" and "modules" as SWORD modules.
If those .swd files are placed into ~/Library/Application Support/Sword/ they are treated as normal SWORD modules.
There is one thing in Eloquent that is incompatible with SWORD modules, that is the notes.
Notes are in fact .rtf files, native to OS X. Those can be opened with TextEdit app for example.
See here more for information about notes:
http://wiki.catug.org/Eloquent#Using_Notes

Ah, OK, I think I see. There wiki was a little unclear (or most likely, I just wasn't understanding). I've figured it out, and managed to get my modules imported. Thank you for your work on Eloquent.


Observability Operator for Prometheus & Alertmanager

Adds two options to observability_strategy:

use_redhat (OBO Only)
use_hybrid (OBO + grafana + elasticsearch + loki)

Default to use_redhat for new installs
Use upstream source for OBO in CI
Added sensubility to deployment validation
Adds  RBAC definitions required for OBO

These used to be handled by prometheus operator for us
If in the future we use the MonitoringStacks interface in OBO, it will manage them for us

test

I don't think the comment triggered testing has been working for several weeks. There are open issues about migrating away from smee as a trigger, but so far I haven't seen any replacement. (I always test it anyways, but pretty sure the expectation is that everything is manually executed at this point.)

I don't think the comment triggered testing has been working for several weeks. There are open issues about migrating away from smee as a trigger, but so far I haven't seen any replacement. (I always test it anyways, but pretty sure the expectation is that everything is manually executed at this point.)

Except that these machines were just rebuilt and I don't know where to find the password, so I couldn't manually trigger it if I wanted too, so figured it was worth a shot.... and, hey it's working!

Currently this does CI tests with "use_hybrid" instead of "use_redhat" because the tests depend on ElasticSearch for events testing. We have work scheduled to replace the built-in ES orcheastration with config that lets you point to an external one, and I figure that means moving the orcheastration from the operator role to the CI role so that we can still validate that functionality. As such, I didn't feel like it was a good idea to remove ES from the smoketests with this change, though I'm slightly uncomfortable that we're not testing with "use_redhat" (which will be the default for deployments). I think I will try adding some sort of ES bypass into the smoketest to allow us to test with "use_redhat" in the meantime.
I've also not tested moving between strategies yet. use_community <> use_redhat/hybrid seems tricky because you'll end up with two copies of things in under two namespdifferent APIs. I expect that use_redhat <> use_hybrid would be smooth.

I don't think the comment triggered testing has been working for several weeks. There are open issues about migrating away from smee as a trigger, but so far I haven't seen any replacement. (I always test it anyways, but pretty sure the expectation is that everything is manually executed at this point.)

Except that these machines were just rebuilt and I don't know where to find the password, so I couldn't manually trigger it if I wanted too, so figured it was worth a shot.... and, hey it's working!

Oh right! Well that's a nice find.
If you login to the openshift-install VM (which I think is where these machines are triggered from), the MOTD has a command/path for dumping the login password to the machines from the setup directory.

Currently this does CI tests with "use_hybrid" instead of "use_redhat" because the tests depend on ElasticSearch for events testing. We have work scheduled to replace the built-in ES orcheastration with config that lets you point to an external one, and I figure that means moving the orcheastration from the operator role to the CI role so that we can still validate that functionality. As such, I didn't feel like it was a good idea to remove ES from the smoketests with this change, though I'm slightly uncomfortable that we're not testing with "use_redhat" (which will be the default for deployments). I think I will try adding some sort of ES bypass into the smoketest to allow us to test with "use_redhat" in the meantime.
I've also not tested moving between strategies yet. use_community <> use_redhat/hybrid seems tricky because you'll end up with two copies of things in under two namespdifferent APIs. I expect that use_redhat <> use_hybrid would be smooth.

Thanks for this. You were probably typing this as I was going through the code, so I didn't see it yet. It addresses a few of my comments.

I'm inviting more reviewers to increase overall exposure and maybe get some ideas about how we could provide a smooth upgrade experience. The basic problem is that existing deployments are all implicitly "use_community" because they don't specify an observability_strategy. If we change the default to be "use_redhat" in future versions, it will cause unexpected changes (trying to use OBO suddently) that may require (as-yet-unspecified) manual interactions to bring things back to a settled state.
One idea I have in mind is to detect existing "use_community" installs that don't explicitly set observability_strategy and set it for them so that they will remain untouched until deliberately edited.

test

TESTING - Changing from observability_strategy: use_community to use_redhat (and back)
The latest commit adds the ability to smoothly transition from use_community to use_redhat and back, assuming both the community prometheus operator and OBO are installed.
$ oc get stf -o yaml | grep strategy
    observability_strategy: use_community

$ oc get po | grep default-0
alertmanager-default-0         3/3     Running     0               100m
prometheus-default-0           3/3     Running     1 (101m ago)    101m

$ oc get prometheus.monitoring.coreos.com
NAME      VERSION   DESIRED   READY   RECONCILED   AVAILABLE   AGE
default             1                                          102m

$ oc get prometheus.monitoring.rhobs
No resources found in service-telemetry namespace.

$ oc edit stf
[...]
observability_strategy: use_redhat

$ oc get po | grep default-0
alertmanager-default-0                                    3/3     Running     0               46s
prometheus-default-0                                      3/3     Running     0               51s

$ oc get prometheus.monitoring.coreos.com
No resources found in service-telemetry namespace.

$ oc get prometheus.monitoring.rhobs
NAME      VERSION   DESIRED   READY   RECONCILED   AVAILABLE   AGE
default             1         1       True         True        75s

I confirmed that the scrape targets are UP and everything looks to be fine.
I can even change it back the other way.
$ oc edit stf
[...]
observability_strategy: use_community

$ oc get po | grep default-0
alertmanager-default-0                                    0/3     Terminating   0               40s
prometheus-default-0                                      3/3     Running       1 (30s ago)     38s

$ oc get prometheus.monitoring.coreos.com
NAME      VERSION   DESIRED   READY   RECONCILED   AVAILABLE   AGE
default             1                                          2m9s

$ oc get prometheus.monitoring.rhobs
No resources found in service-telemetry namespace.

I believe the latest patch solves the upgrade problem. I've set the default to use_redhat, and added code for the following:

Existing STF objects get an explicit "use_community" added
New STF objects get the default ("use_redhat") explicitly added

TESTING - Upgrades (kinda)
I'm starting with an existing empty (all defaults) STF object in a system where use_community is the default. All containers up and healthy.
$ oc get stf -o yaml | grep -A 1 spec:
  spec: {}
  status:

$ oc get prometheus.monitoring.coreos.com
NAME      VERSION   DESIRED   READY   RECONCILED   AVAILABLE   AGE
default             1                                          61m

Now I upgrade to the new code where use_redhat is the default, but it honours existing community deploymemnts.
$ git reflog | head -1
0838da7 HEAD@{0}: commit (amend): Enforce explicit observability_strategy

$ ./build.sh
[...]
Successfully pushed image-registry.openshift-image-registry.svc:5000/service-telemetry/service-telemetry-operator@sha256:7aea4ac3942403c4494158d3e9564fefb5e414db15bda604ae028a3231972564
Push successful

$ oc delete po service-telemetry-operator-6dc87b7bbd-92vd4
pod "service-telemetry-operator-6dc87b7bbd-92vd4" deleted

$ oc get stf -o yaml | grep -A 1 spec:
  spec:
    observability_strategy: use_community

I create a second STF, also empty (defaults), which should default to redhat components.
$ oc apply -f - <<EOF
apiVersion: infra.watch/v1beta1
kind: ServiceTelemetry
metadata:
  name: default2redhat
spec: {}
EOF

$ oc get stf default2redhat -o yaml | grep -A 1 spec:
spec:
  observability_strategy: use_redhat

They even live happily side by side
$ oc get prometheus.monitoring.coreos.com
NAME      VERSION   DESIRED   READY   RECONCILED   AVAILABLE   AGE
default             1                                          34s

$ oc get prometheus.monitoring.rhobs
NAME             VERSION   DESIRED   READY   RECONCILED   AVAILABLE   AGE
default2redhat             1         1       True         True        39s

$ oc get po | egrep default.\*-0
alertmanager-default-0                                           3/3     Running     0             92s
alertmanager-default2redhat-0                                    3/3     Running     0             3m4s
prometheus-default-0                                             3/3     Running     0             97s
prometheus-default2redhat-0                                      3/3     Running     0             2m23s

test

I'm going to keep working on an ES bypass for the smoketests so we can test with use_redhat instead of use_hybrid, but I'll post that to another PR.
I consider this ready to merge once it passes CI but will keep it open for additional feedback.

I'm going to keep working on an ES bypass for the smoketests so we can test with use_redhat instead of use_hybrid, but I'll post that to another PR. (Edit: #422)
I consider this ready to merge once it passes CI but will keep it open for additional feedback.

Going to do another code walk through today and will provide feedback. Once this is all complete I'd like to talk next week about how we approach the Elasticsearch stuff that will follow these changes and build upon it.

I'm going to merge #422 into this and then try to get it to pass CI tests before ultimately merging this to maste.

test

4.12 builds are failing to push to the internal registry in the OCP cluster. I will investigate.

I found cluster-image-registry-operator spitting errors so I restarted it and it seemed to come up healthy. Shortly thereafter the cluster stopped responding to API calls and I could no longer log in. It came back, and I found the oauth container restarting.
I0508 20:26:52.862099       1 controller.go:450] Starting Controller
[...]
ditions.1.message={"Progressing: The registry is ready\nNodeCADaemonProgressing: The daemon set node-ca is deploying node pods" -> "Progressing: The registry is ready\nNodeCADaemonProgr
essing: The daemon set node-ca is deployed"}, changed:status.conditions.1.reason={"NodeCADaemonUnavailable::Ready" -> "Ready"}, changed:status.conditions.1.status={"True" -> "False"}
W0508 20:28:15.831346       1 reflector.go:347] github.com/openshift/client-go/route/informers/externalversions/factory.go:101: watch of *v1.Route ended with: an error on the server ("u
nable to decode an event from the watch stream: stream error: stream ID 111; INTERNAL_ERROR; received from peer") has prevented the request from succeeding

$ oc get po -A | egrep -v Running\|Completed
NAMESPACE                   NAME                                  READY   STATUS        RESTARTS         AGE
openshift-authentication    oauth-openshift-5fc7b6968c-nh8wq      0/1     Pending       0                4s
openshift-authentication    oauth-openshift-6b456c6dbb-8r8ds      1/1     Terminating   0                125m
openshift-etcd              installer-6-elf-412-5vmkz-master-2    0/1     Error         0                14d

It seems to have stabilized and builds are succeeding! Still, something bad going on here.

@elfiesmelfie I switched the setting here https://github.com/infrawatch/service-telemetry-operator/pull/402#issuecomment-1538891071  but now I think I need to switch it back?


Execution halts when useState is used after awaited function in useAsyncData

Environment
My pc:

Operating System: Darwin
Node Version:     v18.12.1
Nuxt Version:     3.1.0
Nitro Version:    2.0.0
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      -
Runtime Modules:  -
Build Modules:    -

Also happens in stackblitz:

Operating System: Linux
Node Version:     v16.14.2
Nuxt Version:     3.1.0
Nitro Version:    2.0.0
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction
https://stackblitz.com/edit/github-zrc5sy?file=components/StateGetter.vue
In this example there are two components that set the state, and one that reads the state.
The only difference between the setters is that useState is called after the awaited function in StateSetterAfterAwait.vue and before the awaited function in StateSetterBeforeAwait.vue.
Notice that the console.log in StateSetterAfterAwait.vue is never reached, nor is the state set.
Describe the bug
When useState is called after an awaited function in useAsyncData, execution halts.
Additional context
No response
Logs
No response

You should not use useState within your useAsyncData fetcher function (or indeed, any Nuxt composables). Instead, it should be called in your setup function directly.

Is this mentioned in the docs anywhere? Also I would expect an error/warning, when using them in the wrong place

Yes, we have an open issue to document this: https://github.com/nuxt/nuxt/issues/14723

link to this
https://github.com/nuxt/nuxt/issues/19382
Same issue with useFetch

You should not use useState within your useAsyncData fetcher function (or indeed, any Nuxt composables). Instead, it should be called in your setup function directly.

How to use because i use it in vue page for setting user data after getting data, or in init server, have you an exemple how it should be called in await call (useFetch, useLazyFetch etc ?)

finally i made a workaround
let username: String;
	let role: String;
	let isConnected: boolean = false;

	//useState('username', ()=>'test');
	if (token !== null && token?.length > 0) {
		await useFetch(REST_API_URL + '/auth/validate', {
			method: 'POST',
			headers: {
				'Authorization': 'Bearer ' + token,
				'Content-Type': 'Application/json'
			},
			onResponse({request, response, options}) {
				// Process the response data
				if (response.status === 200) {
					const payload = parseJwt(token)
					username = payload.username
					role = payload.role
					isConnected = true
				}
			},
			onResponseError({request, response, options}) {
				console.log('token is not valid or expired');
				if (response.status === 400) {
					console.error('token expired or invalid');
				} else {
					console.error('internal issue problem');
				}
				router.push("/")
			},
		});

		if (isConnected) {
			useState('isConnected', () => isConnected);
			useState('username', () => username);
			useState('role', () => role);
		}

	} else {
		console.log('No token registered')

	}


Change module path

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@c8e9e56). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff            @@
##             master       #1   +/-   ##
=========================================
  Coverage          ?   82.19%
=========================================
  Files             ?       32
  Lines             ?     2971
  Branches          ?        0
=========================================
  Hits              ?     2442
  Misses            ?      419
  Partials          ?      110

Flag
Coverage Δ

go
82.19% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.


[CELEBORN-1188][TEST] Using JUnit function instead of java assert

What changes were proposed in this pull request?
Using Junit function instead of java assert.
Why are the changes needed?
When java assert fail, will throw AssertException, which is hard to find diff.

Instead, when we use junit assert, we can clearly find diff.

Does this PR introduce any user-facing change?
NO, only test changed
How was this patch tested?
Run CI

Merged to main/0.4


onDidOpenTextDocument fired incorrectly & with the wrong Uri scheme

Version: 1.40.0-insider
Commit: ceeb587991f647659d42a82f87acf3d9778b4d0e
Date: 2019-10-14T10:18:06.503Z
Electron: 6.0.12
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Darwin x64 18.7.0
Steps to Reproduce:
First setup test data

Open a workspace with a file named abc.ipynb that has been commited in a git repo.
Edit the above file to ensure it is marked as dirty.

Debug extension to replicate issue

Create a new extension (yo code)
Add a handler to vscode.workspace.onDidOpenTextDocument and display the uri as follows:

vscode.workspace.onDidOpenTextDocument(e=> vscode.window.showInformationMessage(e.uri.toString()));

Configure the above extension to activate always
Debug the above extension
Go into Source Control activity bar
You'll see the file abc.ipynb has changes.
Click on this file

On Mac, we'll get events fired for onDidOpenTextDocument with a uri = git://.....
On Windows, we'll get events fired for onDidOpenTexxtDocument with uri = file:// and git://

The bug is in Windows.
We didn't open the file, we only opened the diff view, but VS Code is firing an event for text document opened with uri = file://
There seem to be other bugs in mac and windows:

Open file explorer, and click on the file abc.ipynb
You'll have two events fired for onDidOpenTextDocument event thought we opened one document!

First event uri = 'file://
Second event uri = 'git://

Bug, why is a second event fired for a document opened with a uri = git. This isn't right. we didn't open such a text document. Why is the uri = git when the file is opened from the file explorer view.

Does this issue occur when all extensions are disabled?: Yes

/cc @joaomoreno for an explainer if needed

@jrieken I don't know why on Windows you'd get one extra event. I also don't know why onDidOpenTextDocument is fired just by creating a text model. We need to create a text model to compute diffs, btw.

I also don't know why onDidOpenTextDocument is fired just by creating a text model

You should, you are causing it. A text document is a text model and that is not an editor.

@jrieken Hmm maybe I'm misunderstanding something. I'm just using createModelReference (just like References et al) and I use the URI of the model to compute a diff. The dirty diff editor doesn't really open a file. :thinking:
https://github.com/microsoft/vscode/blob/be68a4e14c28cc81cdf422739af23123b3c91fd2/src/vs/workbench/contrib/scm/browser/dirtydiffDecorator.ts#L1082-L1095
I can debug it and try to figure out where it's coming from.

Yes, in API lingo you "open a text document". Nothing new or wrong here and actually the reason why git:///-resources have a different file suffix. It's just that extension authors are often surprised by this. The doc tries to explain this but it seems hard to understand or isn't read much

@jrieken There are two things reported here. You seem to be talking about the  second one, which we all know about and decided to live with it: events firing for git:// documents.
I'm talking about the first one: extra event on Windows only.

I'm talking about the first one: extra event on Windows only.

Yeah, that's on your plate but createModelReference does create a text model and therefore fires said event unless the model already exists. Maybe that's different on windows 🤷♂

Actually @DonJayamanne I don't understand. It is expected for you to get two events: one for git:// (left side) and one for file:// (right side). Can you reconfirm that one macOS you only get one event?

On Mac I get two events fired and both are git

Are you sure you're not comparing between a staged change (mac) vs an unstaged change (windows)?

Ahh yes, thats correct. Apologies for taking you on a wild goose chase.


6.0.2xx is failing to build with the latest dependency flow.

https://dev.azure.com/dnceng/public/_build/results?buildId=1472120&view=logs&j=b9699899-7397-58dc-1551-d4801b3b3dfe&t=2beba4da-da67-557f-b169-2ed90945e20d&s=6884a131-87da-5381-61f3-d7acc3b91d76
The dependency flow was merged to unblock other work.

There are multiple issues.

SDK breaking online builds - https://github.com/dotnet/sdk/issues/22640
msbuild prebuilts breaking offline builds.

Current status:  Online builds pass now.  Offline is failing w/prebuilts which are tracked by the various linked issues.

Current status:  Online builds pass.  One remaining fsharp related prebuilt tracked with https://github.com/dotnet/fsharp/issues/12499.

cc @shushanhf

cc @shushanhf

Thanks～

Build passes now - smoke-test fails tracked with https://github.com/dotnet/source-build/issues/2736.


Add the ability to use multiple aliases and bindings to your mailbox

Checklist

[X] I have used the search function to see if someone else has already submitted the same feature request.
[X] I will describe the problem with as much detail as possible.
[X] This issue only contains a request for one single feature, not multiple (related) features.

App version
5.807
Problem you are trying to solve
I have both Russian-speaking recipients and English-speaking ones. And I need to use multiple aliases for one mailbox.
Suggested solution
Solution: in the mailbox settings, add the ability to create multiple aliases.
Screenshots / Drawings / Technical details
No response

K-9 Mail already supports multiple identities. You can add an additional one under Settings → [Account] → Sending mail → Manage identities.

Thanks


"Răzvad", "Gorgota" are listed in the drop-down menu

Description:
When user writes ” Răzvad” and "Gorgota" the locations appear in the drop-down menu next to the comune and the county which is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Răzvad"

Expected results
The location appears in the drop-down menu as "Sat Răzvad, DÂMBOVIȚA (Răzvad)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Gorgota"

Expected results
The location appears in the drop-down menu as "Sat Gorgota, DÂMBOVIȚA (Răzvad)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Valea Voievozilor"

Expected results
The location appears in the drop-down menu as "Sat Valea Voievozilor, DÂMBOVIȚA (Răzvad)".


Test issue to make sure Design label & auto-assigning is working

Action Performed:
Added Design label to e.cash repo & to some issue(s)
Expected Result:
Someone from design team is auto-assigned (like when Engineering label is added to an issue)
Related issues:
Master e.cash improvement tracker: https://github.com/Expensify/Expensify/issues/159560

Triggered auto assignment to @megankelso (Design), see these Stack Overflow questions for more details.

Triggered auto assignment to @sylveawong (Design), see these Stack Overflow questions for more details.

OK cool just testing that this works :D Sorry for the pings!


added always_xy option to transformer & minumum PROJ version to 6.1.0

#225
#238
#204

TODO: Change build pins to 6.1.0 when PROJ 6.1.0 is released.

Looks like PROJ 6.1.0 release is delayed to May 15th.

So, another thought I had is that in the pyproj.transform and pyproj.itransform functions, the transformer should always use always_xy for compatibility with pyproj 1.9.6. However, the default for Transformer will be always_xy=False as this was introduced in pyproj 2.1.0 and will be consistent with future behavior.
Thoughts @jswhit @jorisvandenbossche?

Pending a decision on https://github.com/pyproj4/pyproj/pull/286#issuecomment-489674657, I think this is good to go.
We are currently pinned to 6.1.0RC1, which is fine for now as we can update to the release of 6.1.0 before releasing pyproj 2.2.0. Merging this now will allow additional PROJ 6.1.0 specific functionality such as PR #289.
The reduction in coverage is due to PROJ no longer raising the exception & the associated test being removed from our code: See https://github.com/OSGeo/proj.4/issues/1449

So, another thought I had is that in the pyproj.transform and pyproj.itransform functions, the transformer should always use always_xy for compatibility with pyproj 1.9.6. However, the default for Transformer will be always_xy=False as this was introduced in pyproj 2.1.0 and will be consistent with future behavior.

I am not sure this is the case? When specifying a Proj in the "old" way as a proj4 string, it still has the old behaviour of not following the CRS defined axis order):
In [1]: import pyproj

In [2]: p1 = pyproj.Proj('+init=epsg:4326')

In [3]: p2 = pyproj.Proj('+init=epsg:31370')

In [4]: pyproj.transform(p1, p2, 4, 50)
Out[4]:<PHONE_NUMBER>7479196, 76585.07854289468)

In [5]: p1 = pyproj.Proj('EPSG:4326')

In [6]: p2 = pyproj.Proj('EPSG:31370')

In [7]: pyproj.transform(p1, p2, 4, 50)
Out[7]: (inf, inf)

In [8]: pyproj.transform(p1, p2, 50, 4)
Out[8]:<PHONE_NUMBER>7479196, 76585.07854289468)

Should't that make it backwards compatible (even with always_xy=False as the default, as it is now in the PR) ?
But, I think it might be good to also expose the always_xy keyword in pyproj.transform(..) as well and pass it through to the Transformer creation (and the same for itransform).

@jorisvandenbossche, you make a good point there about keeping pyproj.transformer as is as your example clearly defines that it is already backwards compatible. I agree that should be the case and I think doing so will prevent future confusion in behavior between the pyproj.Transformer and the pyproj.transformer.
My original reasoning for the change is that I ran into issues with mixing versions of pyproj and the rasterio.CRS class from an older code base, which is why I brought this up. It uses the CRS.to_string method which used to output in the proj4 string format (+init=epsg:4326) and has since been changed to this which now uses the epsg:4326 syntax. Somehow the installation of pyproj=1.9.6 and rasterio with conda works (probably the older versions are pinned together) and the installation of pyproj=2.1.3 and rasterio also work with the new to_string method and the axis swapped. I think the best solution for this case would be to just update the code I was mentioning and more strict pins :).
Also, I agree that it should be added to pyproj.transformer. I was originally thinking about forcing it to be always_xy, but your reasoning makes it clear that adding the option is the better path.
I appreciate you taking the time to provide clarity here.

Okay, I think this one is good to go now.

My original reasoning for the change is that I ran into issues with mixing versions of pyproj and the rasterio.CRS class from an older code base, which is why I brought this up. It uses the CRS.to_string method which used to output in the proj4 string format (+init=epsg:4326) and has since been changed to this which now uses the epsg:4326 syntax.

Ah, yes. Yeah, in the beginning, when "old" and "new" are still both used, this will certainly lead to some confusion. But, in practice this will be a reason to just always specify always_xy=True, then you can be sure of the output, regardless of whether you specified the CRS as 'EPSG:4326' or '+init=epsg:4326'.

in practice this will be a reason to just always specify always_xy=True

This will definitely be the case for geopandas in its current state.

This will definitely be the case for geopandas in its current state.

Yes, but since we typically still use proj.4 dicts or strings, we should normally always get the "old" behaviour (which is what we want), without specifying that keyword (that's the reason that geopandas currently "works" with pyproj 2.1 / proj 6.0).
But in our current implementation in geopandas, nothing forbids somebody to start doing gdf.crs = "EPSG:4326", which didn't work before, but now would wrongly work. So indeed good to start using this keyword if pyproj >= 2.2 is installed.


Performance

Can you achieve the performance that the paper claims in your experiment?

By simply run the code(train.py), I couldn't achieve the performance (results from test.py is bad, SAD is around 100). Is there more training tricks? Need help! Thanks a lot!

The performance of this experiment is illustrated in README.


API Reference support for Java

Some methods in Java and all in .NET are called on a specific instance of an object. Because this object can be named anything, it makes creating a pattern to match on difficult. See Java and .Net snippets for this example: https://stripe.com/docs/api/credit_notes/lines.
We need to look for an alternative way of supporting the hover-over reference.

first java lang support version released in v2.0.7


Bad background behavior on large viewport heights

Describe the bug
Page background on Homepage (/) does not fully extend to the footer.
Give the steps to reproduce

Open homepage.
Open browser devTools, go to responsive design mode
Enter viewport height: 2000
See really large white background appear between feature list and footer

What browsers are you seeing the problem on?
Firefox
Have you thought of a possible solution?
No
If you have thought of a solution, please tell us about it!
No response
Do you want to help fix the bug?
No
Is there anything else we need to know?
No response

I believe this is fixed now. @HonkingGoose can you confirm this, please?

It's fixed, I cannot reproduce the problem anymore.

Thanks for confirming!


CI: Build release binaries for Apple ARM64

Closes str4d/age-plugin-yubikey#71.

Codecov Report

Merging #87 (0ee618c) into main (ed6273d) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##            main     #87   +/-   ##
=====================================
  Coverage   1.33%   1.33%
=====================================
  Files          6       6
  Lines        375     375
=====================================
  Hits           5       5
  Misses       370     370

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

This appears to work: https://github.com/str4d/age-plugin-yubikey/actions/runs/3804651791/jobs/6472019922
Actual test will be after the next release, when I can fetch the resulting binary and confirm it works on my M1.


Deprecate getters/setters and annotate client.py with TODO project plans

@Matrixcoffee could you review this for me? It's the start of my attempt to address your general concerns from #192.
Getters/setters are being removed as they're considered poor python style, and there are ways to make normal attribute access behave like a getter/setter if necessary in the future.

I've looked through it and it generally looks sane. FYI, my next PR already moves _process_state_event to the room object.


Azure AD authentication fails when the end points are set to China

Rancher Server Setup

Rancher version: rancher/rancher:v2.6-0fd630dd1328233958bdef6b9f7f413eb7463005-linux-amd64
Installation option (Docker install/Helm Chart): Docker install

If Helm Chart, Kubernetes Info: k3s
Cluster Type (RKE1, RKE2, k3s, EKS, etc):
Node Setup: 1 node
Version: v1.21.3+k3s1

Proxy/Cert Details: self-signed

Describe the bug
Authentication with azure AD fails when end points are set to China.
Following is the error that is received when we try to authenticate:
 server error while authenticating: UsersClient.BaseClient.Get(): unexpected status 401 with OData error: InvalidAuthenticationToken: Access token validation failure. Invalid audience.

To Reproduce

Create a rancher server on v2.6-head
From explorer >> Users & Authentication >> Auth providers >> Azure AD
enable Azure AD by selecting the endpoints for China and providing required tenant ID, client ID and secret
Save the config

Result
Authentication fails with the error:
server error while authenticating: UsersClient.BaseClient.Get(): unexpected status 401 with OData error: InvalidAuthenticationToken: Access token validation failure. Invalid audience.

Expected Result
Expected the auth to be enabled.
Additional context
When we try custom end points by providing the values of endpoints for China, it fails with the error:
server error while authenticating: authority does not have two segments

https://github.com/rancher/dashboard/issues/5671#issuecomment-1157431071

Validated on rancher v2.6-head (df1b202)
Azure AD authentication uses china endpoint and auth can be enabled.


conflict solve

Coverage decreased (-4.3%) to 46.033% when pulling 04c3c7a692c674f7f4004426826ac2c616f80d3a on yuye/conflict-solve into 31d92f1d68809ef5c391cba4f9ba7e61bf737aff on authndev.

Coverage decreased (-4.3%) to 46.033% when pulling 04c3c7a692c674f7f4004426826ac2c616f80d3a on yuye/conflict-solve into 31d92f1d68809ef5c391cba4f9ba7e61bf737aff on authndev.


Could you add this library to official Arduino Library Manager?

This would give more visibility to your fantastic project
Thanks.
P.D: For more information, see https://github.com/arduino/Arduino/wiki/Library-Manager-FAQ

Awesome, I'll look into it!


Update dependencies

Update dependencies

This change is

The CI error is from the stylelint-config-vaadin.

@abdonrd thanks for the PR. We already merged #420 with stylelint-config-vaadin change.
Could you rebase please?

@web-padawan rebased!


Downloading an update VS Code when checking for an update

VS Code Version: 1.54.3
OS Version: Windows 10 x64

When checking for an update, the new version is downloaded. Personally, I expect that when I click on the "Check for update" button, a check for the existence of a new version occurs and if there is one, then this is reported to the user. When I click on the "Install update" button, then the download and installation of the update should already take place.
Steps to Reproduce:

Install not the latest version vs code
Click "Chech for Updates"

Actual behavior:
Vs code finds update and downloads it.
Expected behavior:
Vs code finds the update and informs the user about it. The update does not download.

Does this issue occur when all extensions are disabled?: Yes

Sorry about this, but we have revisited this story many times and we don't think this is worth the hassle. The vast majority of the users just wants to install the update.

Sorry about this, but we have revisited this story many times and we don't think this is worth the hassle. The vast majority of the users just wants to install the update.

Eh

@joaomoreno
Hello. I noticed one unpleasant thing with this behavior.
Due to the fact that the update is downloaded when the update is checked, the following happens. A new version was released, vs code downloaded the update, but then a new version came out and in this situation I will have to update 2 times for one place. That is, the download and installation will be performed 2 times, which is not very pleasant. This is especially annoying on insider assemblies, which appear frequently. If vs code did not download the update when checking, then we needed one download and installation.


$fetch - cyclic requests for invalid paths

Environment

Environment

Operating System: Linux
Node Version: v18.17.0
Nuxt Version: 3.6.5
Nitro Version: 2.5.2
Package Manager<EMAIL_ADDRESS>Builder: vite

Reproduction
https://stackblitz.com/edit/nuxt-starter-zb5jio?file=app.vue
Describe the bug
If you specify an explicitly invalid path for $fetch, the application freezes completely. This happens because of the endless loop of sending requests.
Apparently, this happens because we get into app.vue every time.

htop

Additional context
The problem was discovered by accident - we forgot to add API proxying when deploying to the stage server
Logs

Log
<--- Last few GCs --->

[41265:0x5a0bf40]   331633 ms: Mark-sweep 4014.0 (4129.3) -> 3998.4 (4129.6) MB, 4866.4 / 0.0 ms  (average mu = 0.112, current mu = 0.003) allocation failure; scavenge might not succeed
[41265:0x5a0bf40]   336414 ms: Mark-sweep 4014.2 (4129.6) -> 3998.6 (4129.8) MB, 4766.1 / 0.0 ms  (average mu = 0.061, current mu = 0.003) allocation failure; scavenge might not succeed

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0xb83f50 node::Abort() [node]
 2: 0xa94834  [node]
 3: 0xd647c0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
 4: 0xd64b67 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
 5: 0xf42265  [node]
 6: 0xf43168 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [node]
 7: 0xf53673  [node]
 8: 0xf544e8 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
 9: 0xf2ee4e v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
10: 0xf30217 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
11: 0xf113ea v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [node]
12: 0x12d674f v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [node]
13: 0x17035b9  [node]<--- Last few GCs --->

[41265:0x5a0bf40]   331633 ms: Mark-sweep 4014.0 (4129.3) -> 3998.4 (4129.6) MB, 4866.4 / 0.0 ms  (average mu = 0.112, current mu = 0.003) allocation failure; scavenge might not succeed
[41265:0x5a0bf40]   336414 ms: Mark-sweep 4014.2 (4129.6) -> 3998.6 (4129.8) MB, 4766.1 / 0.0 ms  (average mu = 0.061, current mu = 0.003) allocation failure; scavenge might not succeed

Yes, this is true. I think it might be a good DX improvement to add protection against this.

ref https://github.com/nuxt/nuxt/issues/14178

good spot - let's track there.


[WelcomeUX] esc should hide interface overlay

Testing #18091
'esc' is the first thing I try to hide the overlay, and it always hides popup things.

Tracked with #18871


System Status Page

A system status page like github has would be a welcome addition:
https://status.github.com/graphs/past_month
It would put numbers behind changes associated with #98 and would build confidence in relying on the service.

Or even something like npm's http://status.npmjs.org/ (which seems to use https://www.statuspage.io/ -- although I can't see if they have any open-source plans, or if the cheapest plan is their $30/mo tier).

yes, agreed. We currently use uptime robot. Not sure if we can expose that or not, but we should probably look into a status page. Here is our stats for the last 24 hours. Not good, but we have a plan to make things better.

Getting intermittent errors on our builds today:

'nsp-check' errored after 50 s
Got an invalid response from Node Security, please email the above debug output to<EMAIL_ADDRESS>
Would be awesome if this request was made reality since we're not sure if there's something wrong w/ our network to NSP, or something wrong on NSP's side causing the 50s timeout...


Tezos DID-Method

The Tezos-DID Method document is not maintained anymore see here.
! There is a call for maintainers !
It came up because I was updating the Chain Agnostic improvement proposals mentioned in #2523 for CAIP-2/10/122 and I realized that the Tezos DID URN was not correctly used in the credentials mentioned here.
After stating this in my issue I did also encounter the following w3c did-pkh-method-draft which correctly gives the examples like e.g.:
did:pkh:tezos:NetXdQprcVkpaWU:tz1TzrmTBSuiVHV2VfMnGRMYvTEPCP42oSM8
instead of currently incorrectly:
did:pkh:tz:tz1TzrmTBSuiVHV2VfMnGRMYvTEPCP42oSM8
The difference is that we should use the CAIP-10 compliant account-id correctly including the chain id
I think the correct way of the urn should be supported as well in Altme.
Best regards
Carlo

Hello
In practice I think we dont have hands on that as we use the Flutter Dart lib provided by Spruce for did:pkh in ldp_vc format.
The only place where we manage that is in the use of did:pkh with the vc_sd_jwt format

To clarify: It is actually two different topics

Replace with CAIP-10 compliant URN:
Old: did:pkh:tz:tz1TzrmTBSuiVHV2VfMnGRMYvTEPCP42oSM8
New: did:pkh:tezos:NetXdQprcVkpaWU:tz1TzrmTBSuiVHV2VfMnGRMYvTEPCP42oSM8

Do we even need a "did:tezos-Method" if there is a "did:pkh:tezos-method" ?

I think the did:tezos method is dead, nobody use did:tezos in practice.
did:pkh is much more used
We can use did:pkh:tezos:NetXdQprcVkpaWU:tz1xxxxx  for VC in jwt format  (jwt_vc_json, jwt_vc_json-ld) but i think  didkit does not support the new syntax so we cannot sign VC in json-ld format with linked data proof.

That would be worth a try:

We can use did:pkh:tezos:NetXdQprcVkpaWU:tz1xxxxx for VC in jwt format (jwt_vc_json, jwt_vc_json-ld) but i think didkit does not support the new syntax so we cannot sign VC in json-ld format with linked data proof.

I think I have to discuss this with @jfelixh
Are you sure it cannot be used with json-ld - did you test it?

The only lib we have to sign with did:pkh and jdon ld on flutter is the one provided by Spruce and it looks like they do not maintain it anymore. So the did:pkh is still the previous version with did:pkh:tz1 and no chain id