[WINDOWS] INSTALL ERROR

Hello, I have tryed installing this and this might not be used for windows but when i try installing it I have try so many ways but I always get this:
"
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      C:\Users\steve\AppData\Roaming\npm-cache_logs\2017-10-02T00_49_13_732Z-debug.log
It seems like lwip failed to be intalled. Please check the errors.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: node lib/install.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      C:\Users\steve\AppData\Roaming\npm-cache_logs\2017-10-02T00_49_16_321Z-debug.log
"
FULL INSTALL LOG: https://pastebin.com/tjL2k4P2
Is there anyway you can help me install this right?
What I have tryed:
Installed 64 bit
Installed 32 bit
Tryed: npm i -g image-to-ascii
Tryed: npm i -g image-to-ascii --msvs_version=2017
Using: npm i --save image-to-ascii it save at that location and for windows it don't work so I have to install it in %Appdata%
If this is not for windows please let me know.
Thanks,
GoNotCougsWA

I'd recommend using GraphicsMagick to avoid compiling.


json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

I did exactly what you say in readme, but it turns out;
Traceback (most recent call last):
File "C:/Users/Terry/PycharmProjects/exercise/YT_download/YT_Chapters_Downloader.py", line 73, in
j = json.loads(os.popen('youtube-dl -j ' + url).read())
File "C:\ProgramData\Miniconda3\envs\autopy\lib\json_init_.py", line 348, in loads
return _default_decoder.decode(s)
File "C:\ProgramData\Miniconda3\envs\autopy\lib\json\decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "C:\ProgramData\Miniconda3\envs\autopy\lib\json\decoder.py", line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Hi!
First of all, thanks for using this little script of mine.
Does this happen with any video you tried? If not, could you please the link of the video you are using the script with?
I'll take a look at it as soon as possible (Tuesday, in the worst case).

Hi! First of all, thanks for using this little script of mine. Does this happen with any video you tried? If not, could you please the link of the video you are using the script with? I'll take a look at it as soon as possible (Tuesday, in the worst case).

Hi, Alex, thanks for your reply.  I used this command
python yt.py https://www.youtube.com/watch?v=5kzFCGE_2Y0
I renamed your file as yt.py
But... it looks like the bug is... unstable... Today it gave me:

And there are two new files in my folder, but I can't open the first, it's empty.

Hi!
Apparently there was an issue with the module Pytube.
You can fix it by running: python -m pip install git+https://github.com/Zeecka/pytube@fix_1060.
Note that this script was initially intended to be used to download videos with multiple chapters (like this one). However, I just updated it to download videos without chapters as well.
I'll leave this issue open, in case some other encounter the same error.


Nginx sticky annotations #258 made the global enable-sticky-sessions obsolete

Global ConfigMap setting enable-sticky-sessions is no longer in use.

This change is

Coverage decreased (-0.05%) to 46.181% when pulling 389e0f527c864d75f07a4f88f93892ac1ec3e1a1 on arjanschaaf:nginx-sticky-annotations into 9d4a8b8c17bd5fa92cb74841ed090292a7ae5cb5 on kubernetes:master.

@arjanschaaf why? Some users want/need sticky session enabled globally. If we remove this feature they are forced to add the annotation in all the rules.

@aledbf I could agree with you on that. Annotation based is better for my use case, but I can see the need for globally enabled sticky sessions as well. However the global functionality was already removed in pull request #258 My pull request only aligns documentation and cleans up some constant that was no longer used after #258

@arjanschaaf good point :) (I did not review that PR).
Let's merge this PR. We can add the global support if someone request that feature

/lgtm

@arjanschaaf thanks!


Apple TV Support

Description
Support for the Apple TV 2nd/3rd (2012 & 2013)/4 (HD) and 4K devices. Includes alternative method for displaying architectures in both iOS and tvOS.
Features
`  "iPhone OS")
case $kernel_machine in
AppleTV2,1):      "Apple TV 2" ;;
AppleTV3,1):      "Apple TV 3" ;;
AppleTV3,2):      "Apple TV 3 (2013)" ;;
	esac

        model=$_
;;

    "Apple TVOS")

        case $kernel_machine in
            AppleTV5,3):      "Apple TV 4 ($(sysctl -n hw.model))";;
	AppleTV6,2):      "Apple TV 4K ($(sysctl -n hw.model))";;

        esac

        model=$_
    ;;

"Apple TVOS")
boot=$(sysctl -n kern.boottime)
boot=${boot/{ sec = }
boot=${boot/,*}
        # Get current date in seconds.
        now=$(date +%s)
        s=$((now - boot))
    ;;

case $os in
"Apple TVOS"|"iPhone OS")
# Package Manager Programs.
has kiss       && tot kiss l
has pacman-key && tot pacman -Qq --color never
has dpkg       && tot dpkg-query -f '.\n' -W
has rpm        && tot rpm -qa
has xbps-query && tot xbps-query -l
has apk        && tot apk info
has opkg       && tot opkg list-installed
has pacman-g2  && tot pacman-g2 -Q
has lvu        && tot lvu installed
has tce-status && tot tce-status -i
has pkg_info   && tot pkg_info
has tazpkg     && tot tazpkg list && ((packages-=6))
has sorcery    && tot gaze installed
has alps       && tot alps showinstalled
has butch      && tot butch list
has mine       && tot mine -q
"iPhone OS")
case $kernel_machine in
            "AppleTV2,1"): "Apple A4 (1) @ 1GHz" ;;
	"AppleTV3,1"): "Apple A5 (1) @ 1GHz" ;;
	"AppleTV3,2"): "Apple A5 (1) @ 1GHz" ;;

        esac
        cpu="$_"
    ;;

    "Apple TVOS")
        case $kernel_machine in

            "AppleTV5,3"):                 "Apple A8 (2) @ 1.5GHz" ;;
	"AppleTV6,2"):      "Apple A10X (6) @ 2.38 GHz" ;;

        esac
        cpu="$_"
    ;;

                "Apple TVOS")       cores="${cpu/*\(}"; cores="${cores/\)*}" ;;
	    "iPhone OS")       cores="${cpu/*\(}"; cores="${cores/\)*}" ;;

"iPhone OS")
case $kernel_machine in
	"AppleTV2,1"): "PowerVR SGX535" ;;
            "AppleTV3,1"): "PowerVR SGX543MP2" ;;
	"AppleTV3,2"): "PowerVR SGX543MP4" ;;

        esac
        gpu="$_"
    ;;

    "Apple TVOS")
        case $kernel_machine in
            "AppleTV5,3"):   "PowerVR Series 6XT GX6450" ;;
	"AppleTV6,2"):   "Apple A10X Fusion" ;;

        esac
        gpu="$_"
    ;;

"Apple TVOS" | "iPhone OS")
mem_total="$(($(sysctl -n hw.memsize) / 1024 / 1024))"
mem_wired="$(vm_stat | awk '/ wired/ { print $4 }')"
mem_active="$(vm_stat | awk '/ active/ { printf $3 }')"
mem_compressed="$(vm_stat | awk '/ occupied/ { printf $5 }')"
mem_compressed="${mem_compressed:-0}"
mem_used="$(((${mem_wired//.} + ${mem_active//.} + ${mem_compressed//.}) * 4 / 1024))"
;;
"iPhone OS")
distro="iOS $osx_version $(uname -p) ($osx_build) "
        # "uname -m" doesn't print architecture on iOS.
	# fixing this one too for Apple TV 2 & 3 - JoshTV
        os_arch=off
    ;;

    "Apple TVOS")

        distro="tvOS $osx_version $(uname -p) ($osx_build) "

        # "uname -m" doesn't print architecture on iOS.
#Don't need this. Got uname -p working instead but keep os_arch off. - JoshTV
        os_arch=off
    ;;

Issues
TODO

You need to rebase on master and resubmit this PR. You're pulling in 500~ unrelated commits.


fix(share_plus): fallback for shareXFiles() to use download on web

Description
Adds fallback to use download files on web when Navigator.share() failed
Related Issues

Fix #1643

Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I titled the PR using Conventional Commits.
[x] I did not modify the CHANGELOG.md nor the plugin version in pubspec.yaml files.
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze) does not report any problems on my PR.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate that with a ! in the title as explained in Conventional Commits).
[x] No, this is not a breaking change.

Thanks for the PR! I will check it in the following days. Meanwhile, there are formatting errors in packages/share_plus/share_plus/example/lib/main.dart and packages/share_plus/share_plus/lib/src/share_plus_web.dart.

Taking a look at it now. So I think it's a good start, but I think that if we want to follow the idea that it should always fallback to download, then on any point of failure should fall back to downloading and not just the NotAllowedError. That would mean that, for example, the call to throw Exception('Navigator.canShare() is unavailable'); on line 207 should also be replaced by a call to _download(), also on 211, etc.

Taking a look at it now. So I think it's a good start, but I think that if we want to follow the idea that it should always fallback to download, then on any point of failure should fall back to downloading and not just the NotAllowedError. That would mean that, for example, the call to throw Exception('Navigator.canShare() is unavailable'); on line 207 should also be replaced by a call to _download(), also on 211, etc.

Makes sense. I'll update.
Also, the API docs says that shareXFiles() method "May throw PlatformException or FormatException from MethodChannel", but the web implementation throws plain Exception. Should I change it to use the PlatformException instead?
I also wonder if there should be a flag on the shareXFiles() method to enable/disable this fallback?
Perhaps that could be done as part of https://github.com/fluttercommunity/plus_plugins/issues/3307#issuecomment-2513723902

Also, the API docs says that shareXFiles() method "May throw PlatformException or FormatException from MethodChannel", but the web implementation throws plain Exception. Should I change it to use the PlatformException instead?

I think Exception is fine, instead the documentation should be updated once this feature is ready.

I also wonder if there should be a flag on the shareXFiles() method to enable/disable this fallback? Perhaps that could be done as part of #3307 (comment)

I was thinking that as well. Maybe is a very dirty hack, but even a static variable with a flag to enable/disable the download fallback could be an option. And then refactor properly in #3307

I also wonder if there should be a flag on the shareXFiles() method to enable/disable this fallback? Perhaps that could be done as part of #3307 (comment)

I was thinking that as well. Maybe is a very dirty hack, but even a static variable with a flag to enable/disable the download fallback could be an option. And then refactor properly in #3307

Updated.
On a side note. The XFile.saveTo(path) on the web also makes a file download with the HTMLAnchorElement. The "path" parameter is ignored and XFile.name is used for downloaded files, which won't allow for fileNameOverrides.

I'll go ahead and merge, if there are any other necessary changes they can go in a new PR

PS: those trailing comas are going away when dart_style is bumped to 3.0.0. Hopefully you could increase line length from 80 to 120 at that time...

Interesting.. now taking a look at https://github.com/dart-lang/dart_style/issues/1253


keccak256

What is wrong?
Users cannot perform keccak256 on values (e.g. my_num.keccak256()).
How can it be fixed
An attribute function keccak256 should be implemented on all data types.

I can see the convenience of being able to call keccak256() on any variable. But I think I'd prefer having it as a standalone function because:

Planning ahead, this may not be the only cryptographic function that we need (e.g. see)
In the future keccak256 usage my start to decline leaving us with "API pollution"
We can start having keccak256 globally available and eventually move it behind an import when we support them (e.g. from crypto import keccak256). This will be a less harsh breaking change compared to removing a builtin on all types.

In general, my stance is to be extra cautious with builtin methods that we provide on a broad set of types. I think that importing is generally more future proof and provides a cleaner way to evolve the language. I think that's also a general stance that the rust team uses as guidance.

This landed with #255


Templating mechanism for VMs

Is this a BUG REPORT or FEATURE REQUEST?:
/kind enhancement
Templating mechanism for VMs to abstract away API complexities from users. Something similar to what we get OpenShift templating

Document recommendation VMI specs for common use cases like Windows.

Bug scrub: This needs a bigger discussion. We need to see if we need anything more than existing alternatives (e.g. Helm)
@fabiand would you please join one of the next community calls to defend this?

/remove-lifecycle rotten

Discussions are on-going.
/remove-lifecycle stale


 It seems like this is caused when you guys turn concrete5.org into maintenance mode. That's pretty annoying and probably affects a lot of sites out there.

Can we please have some feedback on this? Did anyone verify this?

I think it's pretty obvious that concrete5 being down will effect the
marketplace item listing page, maybe we should separate what is available
in the marketplace from what is locally available to install to reduce the
annoyance here.
Another option would be to move this stuff to an https JavaScript API, but
I'm not sure how much work this would include.
On Tue, Dec 22, 2015 at 11:30 PM Remo Laubacher<EMAIL_ADDRESS>wrote:

Can we please have some feedback on this? Did anyone verify this?
—
Reply to this email directly or view it on GitHub
https://github.com/concrete5/concrete5/issues/2096#issuecomment-166822708
.


Unable to Proxy Firebase Url

[REQUIRED] Step 2: Describe your environment

Operating System version: macOs Sierra 10.12.5
Firebase SDK version: shouldn't make much of a difference in this issue
Library version: ^5.1.0
Firebase Product: database

[REQUIRED] Step 3: Describe the problem
When attempting to use firebase-admins initializeApp function, the URL is strictly enforced. I'm sure this is intended, however it is keeping me from proxying the firebase URL to a local server for testing. Example:
firebase.initializeApp({
  credential: firebase.credential.cert(FIREBASE_CREDENTIALS),
  databaseURL: 'http://localhost:4001/https://my.firebaseio.com'
});

Resulting in the following error:
Error: FIREBASE FATAL ERROR: Cannot parse Firebase url. Please use https://<YOUR FIREBASE>.firebaseio.com

I use mockyeah for integration testing, which is a nice solution for being able to record snapshots for outgoing requests and their responses. The only caveat is that in order to record the response you have to proxy the URL so that the server can make the call itself.
The issue isn't necessarily with implementation on either side. My overall question is, would supporting a proxied URL be feasible?
Steps to reproduce:
Relevant Code:
Listed above.

This bit of logic actually comes from the firebase-js-sdk: https://github.com/firebase/firebase-js-sdk/blob/master/src/database/core/util/libs/parser.ts
We are simply distributing the minified version of that code with the Admin SDK (at least for now --
this may change in the future). For now can you report this requirement in that repo?

Sounds great, thanks @hiranya911!

I will close this ticket, since this is already been tracked in firebase-js-sdk project.


Examples are slightly out of date

Note: I have druid = "0.7.0" in my cargo.toml
When attempting to run the code in the readme example (copied below), I get two compile errors relating to the WindowDesc::new() and the .log_to_console() methods.
use druid::widget::{Button, Flex, Label};
use druid::{AppLauncher, LocalizedString, PlatformError, Widget, WidgetExt, WindowDesc};

fn main() -> Result<(), PlatformError> {
    let main_window = WindowDesc::new(ui_builder());
    let data = 0_u32;
    AppLauncher::with_window(main_window)
        .log_to_console()
        .launch(data)
}

fn ui_builder() -> impl Widget<u32> {
    // The label text will be computed dynamically based on the current locale and count
    let text =
        LocalizedString::new("hello-counter").with_arg("count", |data: &u32, _env| (*data).into());
    let label = Label::new(text).padding(5.0).center();
    let button = Button::new("increment")
        .on_click(|_ctx, data, _env| *data += 1)
        .padding(5.0);

    Flex::column().with_child(label).with_child(button)
}

Errors:
<snip/>
error[E0277]: expected a `FnOnce<()>` closure, found `impl druid::Widget<u32>`
   --> src/main.rs:5:39
<snip/>
error[E0599]: no method named `log_to_console` found for struct `AppLauncher` in the current scope
 --> src/main.rs:8:10
<snip/>

I found that updating the new() call to remove the () and changing log_to_console to use_simple_logger fixed the issues. Fixed code:
use druid::widget::{Button, Flex, Label};
use druid::{AppLauncher, LocalizedString, PlatformError, Widget, WidgetExt, WindowDesc};

fn main() -> Result<(), PlatformError> {
    let main_window = WindowDesc::new(ui_builder);
    let data = 0_u32;
    AppLauncher::with_window(main_window)
        .use_simple_logger()
        .launch(data)
}

fn ui_builder() -> impl Widget<u32> {
    // The label text will be computed dynamically based on the current locale and count
    let text =
        LocalizedString::new("hello-counter").with_arg("count", |data: &u32, _env| (*data).into());
    let label = Label::new(text).padding(5.0).center();
    let button = Button::new("increment")
        .on_click(|_ctx, data, _env| *data += 1)
        .padding(5.0);

    Flex::column().with_child(label).with_child(button)
}

examples are indented for git version of druid.
README says:

This example works with master. Here's an example for 0.7.0: https://docs.rs/druid/latest/druid/#examples

Oh damn, sorry for the bother!


The UpdateDocuments method should be a partial update

Currently when doing this test:
var indexUID = "BasicDocumentsUpdateTest";
Index index = await this.client.GetOrCreateIndex(indexUID);

// Add the documents
UpdateStatus update = await index.AddDocuments(new[]
{
    new Movie { Id = "1", Name = "Batman", Genre = "Action" },
    new Movie { Id = "2", Name = "Superman" }
});

// Update the documents
update = await index.UpdateDocuments(new[] { new Movie { Id = "1", Name = "Ironman" } });

// Check the documents have been updated and added
var docs = await index.GetDocuments<Movie>();
Assert.Equal("1", docs.First().Id);
Assert.Equal("Ironman", docs.First().Name);
Assert.Equal("Action", docs.First().Genre);
Assert.Equal("2", docs.ElementAt(1).Id);
Assert.Equal("Superman", docs.ElementAt(1).Name);
docs.ElementAt(1).Genre.Should().BeNull();

The Assert.Equal("Action", docs.First().Genre); line fails because Genre is null but it should not be. The add-or-update-documents route should be a partial update, so the value a Genre should still be "Action".

Hello @huseyinsimsekk
MeiliSearch does not provide any PATCH method.
The SDK uses the PUT route add-or-update-documents, but the bad behavior is the fault of the SDK because even if you send only (following the example above):
await index.UpdateDocuments(new[] { new Movie { Id = "1", Name = "Ironman" } });

it will send actually
await index.UpdateDocuments(new[] { new Movie { Id = "1", Name = "Ironman", Genre = null } });

because Movie is defined like this:
`` `c#
public class Movie
{
public string Id { get; set; }
    public string Name { get; set; }

    public string Genre { get; set; }
}

**=> the SDK should only send the field that the user sends**

I hope this is clearer, sorry, my description wasn't, obviously


Deep namespaced routes not working

I'm building an international website, therefore I managed to have URLs looking like /{language}/{other_stuff} thank to some manipulation in RouteServiceProvider
/**
 * Define the routes for the application.
 *
 * @param  \Illuminate\Routing\Router  $router
 * @return void
 */
public function map(Router $router, Request $request)
{

	$locale = $request->segment(1);
	$this->app->setLocale($locale);

	/**
	 * Internationalization routing system
	 */
	$router->group(['namespace' => $this->namespace, 'prefix' => $locale], function($router) use ($locale) {

		if ($locale == 'en') require app_path('Http/routes_en.php');
		elseif ($locale == 'el') require app_path('Http/routes_el.php');

	});

}

Works like a charm. Every language will have his own route file, it's a choice.
Let's say we go to /en/ and you're an admin, I created another namespace within Http/route_en.php to focus on the admin section :
Route::group(['namespace' => 'Admin', 'prefix' => 'admin'], function() {

  Route::controller('', 'DashboardController');

  Route::controller('brands', 'BrandsController');
  Route::controller('contents', 'ContentsController');
  Route::controller('downloads', 'DownloadsController');
  Route::controller('news', 'NewsController');
  Route::controller('products', 'ProductsController');
  Route::controller('settings', 'SettingsController');
  Route::controller('users', 'UsersController');

});

So now I should access easily sections such as /en/admin/brands but it fails. I generate all my links dynamically thanks to the HTML class
{!! HTML::linkAction('Admin\BrandsController@getIndex', 'Brands') !!}

The generation works fine when I go to /en/admin which means Admin\BrandsController@getIndex is detected by this package, but when you click on it
Sorry, the page you are looking for could not be found.

I tested some stuff and when I just simply set the route outside group() it works fine.
Route::controller('admin/brands', 'Admin\BrandsController');

What am I missing here ? Shouldn't the HTML class and the routing system agree with each others ? Is there any mistake I made ? Maybe there's an issue ?

try to call artisan route:list.
and according to your code, /en/admin should lead to Admin\DashboardController@getIndex - is the method present in controller?

It is, and when I call all those routes outside the namespace it works fine. Also, I noticed that the DashboardController@getIndex was working even in the namespace.
website(master)$ php artisan route:list
Your application doesn't have any routes.

Well this is very very weird because my application is already full of routes ... Most of them working

OK. artisan isn't working because routes are included only of request segment is present (It is not in CLI mode) - I didn't notice it.
Try to debug routes at the end of your routes_en.php
dd($router->getRoutes()->getRoutes()); // Line correct - call getRoutes twice

Very interesting debugging functionality !
One of the routes looks like that
  12 => Route {#148 ▼
      #uri: "en/admin/brands"
      #methods: array:2 [▼
        0 => "GET"
        1 => "HEAD"
      ]
      #action: array:7 [▼
        "middleware" => "anything"
        "uses" => "App\Http\Controllers\Admin\BrandsController@getIndex"
        "as" => null
        "controller" => "App\Http\Controllers\Admin\BrandsController@getIndex"
        "namespace" => "App\Http\Controllers\Admin"
        "prefix" => "en/admin"
        "where" => []
      ]
      #defaults: []
      #wheres: []
      #parameters: null
      #parameterNames: null
      #compiled: null
      #container: Application {#2}
    }

And going to /en/admin/brands leads to Sorry, the page you are looking for could not be found.
What do you think ?
PS : i built a anything middleware but it return true every time right now so it doesn't really matter, just for you to understand the full route details

Here's the full route_en.php file
Route::group(['middleware' => 'anything'], function() use ($router) {
      Route::controller('admin/news', 'Admin\NewsController');

      /**
       * Admin
       */
      Route::group(['namespace' => 'Admin', 'prefix' => 'admin'], function() use ($router) {

        Route::controller('', 'DashboardController');

        Route::controller('brands', 'BrandsController');
        Route::controller('contents', 'ContentsController');
        Route::controller('downloads', 'DownloadsController');
        Route::controller('news', 'NewsController');
        Route::controller('products', 'ProductsController');
        Route::controller('settings', 'SettingsController');
        Route::controller('users', 'UsersController');

      });

      /**
       * Auth
       */
      Route::group(['namespace' => 'Auth'], function() use ($router) {

        Route::controller('auth', 'AuthController');
        Route::controller('password', 'PasswordController');

      });

      /**
       * Other
       */
      Route::controller('', 'HomeController');

    });

I'm not entirely sure about this, but I don't think routes are ever supposed to be registered conditionally.

I've copied your codes into a fresh laravel installation and everything works.
Does your middleware return true or $next($request);?

So it's getting weird. My middleware does exactly this
<?php namespace App\Http\Middleware;

    use Closure;
    use \Illuminate\Routing\Route as Route;

    class Anything {

      /**
       * Create a new filter instance.
       */
      public function __construct()
      {

      }

      /**
       * Handle an incoming request.
       *
       * @param  \Illuminate\Http\Request  $request
       * @param  \Closure  $next
       * @return mixed
       */
      public function handle($request, Closure $next)
      {

        // Every time it will be true
        return $next($request);

      }

    }

So I removed it and it doesn't change anything to my routing problem. I'm starting to be worried not finding any solution :(

Your code definetly works - I've checked.
So the problem is not in routing.
Try to make a new fresh installation and copy your step-by-step.
This is the only solution I can advice.

If php artisan route:list doesn't work, php artisan route:cache might not work either - just a reminder in case if you are relying on faster Route caching.


The id key in the android client is incorrect, making all requests to the server fail

https://github.com/traccar/traccar-client-android/blob/d4a4dbfd56c5a7ea19391bb5de252c9cd8aa7938/app/src/main/java/org/traccar/client/ProtocolFormatter.kt#L25
https://github.com/mostafamvh/traccar_flutter/blob/c06d739ad48b879bc3ac6ff066ffbe1c112126d5/android/src/main/kotlin/dev/mostafamovahhed/traccar_flutter/client/ProtocolFormatter.kt#L25
UnidId instead of id

Hi,
Thank you. I’ve reviewed your contribution, and I appreciate your effort!

https://github.com/traccar/traccar-client-android/blob/d4a4dbfd56c5a7ea19391bb5de252c9cd8aa7938/app/src/main/java/org/traccar/client/ProtocolFormatter.kt#L25
https://github.com/mostafamvh/traccar_flutter/blob/c06d739ad48b879bc3ac6ff066ffbe1c112126d5/android/src/main/kotlin/dev/mostafamovahhed/traccar_flutter/client/ProtocolFormatter.kt#L25
UnidId instead of id

Hi,
Thank you. I’ve reviewed your contribution, and I appreciate your effort!


Simplify blob sidecar availability checker

blobs get from EL are marked as valid (trust assumption on EL)
fixes #8740
Documentation

[ ] I thought about documentation and added the doc-change-required label to this PR if updates are required.

Changelog

[ ] I thought about adding a changelog entry, and added one if I deemed necessary.

since i forgot to do this marking i think the way I did it is a bit error prone. I'll change it.

I will join Mehdi feedback:

if some validation was not performed I expect that we want to run it now
if it means that it was actually performed but failed it's confusing
I'm happy with split kzg+inclusion / signature

Worth run on some test nodes before merging into master.

I run an historical sync test (mainnet) , I'll run more tests (mainnet and local)

I actually forgot this:

@zilm13 take a look to latest commit. Testing session was fine, historical sync, forward symc, chain follow.

@tbenr loooks good, the only nit, it maybe better to mark it as validated in if, by to your decision.


feat: allow importing pb schema from https

I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
When it's deployed in production, we expect users to store the Protobuf schema file in a remote store, such as S3, which typically provides an HTTP endpoint to access files. Therefore I think HTTP is a more common way to access pb schema than S3 API.
Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Documentation
If your pull request contains user-facing changes, please specify the types of the changes, and create a release note. Otherwise, please feel free to remove this section.
CREATE SOURCE pb_source WITH (
    connector = 'kafka',
    kafka.topic = 'live_stream_metrics',
    kafka.brokers = '<IP_ADDRESS>:61073',
    kafka.scan.startup.mode = 'earliest'
) ROW FORMAT PROTOBUF MESSAGE 'Trade'
ROW SCHEMA LOCATION 'https://xxx.xxx.com/test_pb_schema';

Types of user-facing changes
Please keep the types that apply to your changes, and remove those that do not apply.

Connector (sources & sinks)

Release note
Please create a release note for your changes. In the release note, focus on the impact on users, and mention the environment or conditions where the impact may occur.
Refer to a related PR or issue link (optional)

do we need to reserve some fields for building Authorization header

Not all vendors are using the same auth mechanism. For example, Aliyun OSS accepts auth credentials in URL params rather than in the Authorization header.


servo-mac9 and servo-mac5 take 14 minutes longer to compile than other mac builders

They both consistently report 37 minutes for ./mach build, while other macs like servo-mac3 report 23 minutes. This tends to push our end-to-end built times to >1 hour when these machines are selected. I sshed in and didn't see any renegade processes that have caused similar slowdowns in the past.

Filing in servo/servo instead.


solium: replace the arg-overflow rule with max-len

Closes #3

After two +1 on #3, and some time without negative comments, I'm merging this.


Sanitize question permalink slugs

Since question slugs are generated from the titles, we need to handle special characters and other things that shouldn't be in URLs. For example:
https://posthog.com/questions/typeerror:-cannot-read-property-'identify'-of-undefined-getting-this-when-i-use-posthog.identify
In above:

[ ] :
[ ] '
[ ] .

Closed via #270


OutputMode.SPLIT to support splitting on more than one context key

Not implementing this for the time being. Adding this would go against the "one step one operation" methodology that watergrid tries to enforce. If this is really needed, one could do two split operations one right after the other.


bug:  font is not rendering correctly

Did you check docs and existing issues?

[x] I have read all the LazyVim docs
[x] I have updated the plugin to the latest version before submitting this issue
[x] I have searched the existing issues of LazyVim
[x] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
NVIM v0.10.3 Build type: Release LuaJIT 2.1.1734355927
Operating system/version
Mac 15.1.1
Describe the bug

As you can see, the code is not correctly rendered. I have set the font to be FiraCode Nerd Font.
Steps To Reproduce
I have not change anything and I just clone the start repo
git clone https://github.com/LazyVim/starter ~/.config/nvim

Expected Behavior

It should be something like this
Repro
same as this repo "https://github.com/LazyVim/starter"

What does that have to do with LazyVim? How the fonts are rendered is purely dependent on the terminal you use and how you've configured it with the fonts you want to use.

Hi, thank you for ur responding.
I have set the font but it did not work, do you have any idea?

Tokyonight has some settings regarding styles as you can see in the docs under Default Options. By default for comments and keywords it uses italic. You can try changing that according to your preferences, but this is not a LazyVim bug.

thank you. I have test it for a while but I have not successfully changed the theme.... Could you help me out:)

What colorscheme would you like to use? The default is tokyonight. Or you can change it to something else if you'd like.

I just want the font is correctly rendered

Do you mean the colors of the keywords?

Sorry, but this is related to your terminal. I've configured Ghostty to use FiraCode Nerd Font like this

And I get the following with part of your code

I don't use your terminal so don't know how to be of further help. Make also sure that the Nerd fonts version that you use is the latest. Maybe you're not on Nerd fonts v3.x or greater?

I may found the issue.
https://github.com/warpdotdev/Warp/issues/3925


Add support for HLS/DASH content steering

Initial requested under https://github.com/google/ExoPlayer/issues/11203.  Please advise the plan for the feature to be available under Media3.
Content steering is a new feature of both HLS and DASH standards, simplifying the design of multi-CDN systems, redundancy/failover functions, load balancing, and various other traffic optimization applications. A number of players (DASH.js, HLS.js, Apple's AVplayer, etc.) already support this feature.
The relevant specifications are:
[1] HLS Content Steering Specification (v1.2b1) https://developer.apple.com/streaming/HLSContentSteeringSpecification.pdf
[2] DASH-IF – https://www.etsi.org/deliver/etsi_ts/103900_103999/103998/01.01.01_60/ts_103998v010101p.pdf
The ask is: please add support for Content Steering functionality in Exoplayer.
Finer-level detail: if feasible, please include the _HLS/DASH_pathway and _HLS/DASH_throughput parameters in calls to the steering servers. These parameters help servers to react faster in cases of failures or other problems with CDNs.

Thanks for filing.
I assign to @tonihei like issue https://github.com/google/ExoPlayer/issues/11203.. Usefulness of content steering for DASH/HLS is already acknowledged in that issue.

Yes, this is a duplicate of https://github.com/google/ExoPlayer/issues/11203, but I'll use the opportunity to move the issue over to the Media3 tracker and close the old one. We are still planning to implement HLS and DASH content steering.

FYI, a recent overview paper describing various features and benefits of this standard: https://www.ibc.org/technical-papers/ibc2024-tech-papers-content-steering-a-standard-for-multi-cdn-streaming/12072.article It also includes references to various existing implementations, streams, and tools that may be useful for testing.


Use new URL for API client

Make API Client docs use externalSourceUrl like CLI docs do. The content is now in GitHub, not in S3.
This will involve removing the redirects on Web
Excuse the branch name, I always confuse the two.

Not necessary


i love you man or woman

thank you for not putting the mp4 video support thank you!!!!!

i used an old version of the psych engine where mp4 video support was not included yet.


Script throws an error when all of the config Features are turned off

When running the script with all Features turned off in config.yaml, the script throws:
line 226, in <module>
    splitFont()
line 151, in splitFont
    pyftfeatfreeze.main([f"--features=rvrn,{','.join(fontOptions['Features'])}", outputPath, outputPath])
TypeError: can only join an iterable

I think this happens due to an invalid YAML file in that case, rather than a bug in the script. If you want to turn off all features you can specify an empty array in YAML like this:
Features: []

My thanks to both of you!
@mapadev, I appreciate the issue. I'll make the script handle this situation more gracefully before closing the issue.
@jwortmann thanks for the suggestion! I haven't tested it yet, but that does seem like a promising workaround until I can get to fixing this in a better way. @mapadev if you want to try it, please let me know if it works!

@arrowtype. The provided solution works for me as I just wanted to try some general settings without embedding any specific features.
Thank you @jwortmann.


Automated cherry pick of #6508: Exclude terminated Pods from group members (#6508)

Cherry pick of #6508 on release-2.0.
#6508: Exclude terminated Pods from group members (#6508)
For details on the cherry pick process, see the cherry pick requests page.

/skip-all


Refine StyleSheet Flow types

Nice addition of the recent Flow types for style props in 9c29ee1504a66979d7e87f60e42d437e044a1ada, however I think there are some slight issues in the definition.
type Styles = {[key: string]: Object} makes sense, as it's referring to the set of named style groups a user creates a StyleSheet from, e.g.
const styles: StyleSheet = StyleSheet.create({
  container: {
    height: 20
  },
  text: {
    color: '#999',
    fontSize: 12,
  },
}: Styles)

However type StyleValue = {[key: string]: Object} doesn't make sense.  You actually want only the Object portion of that definition, presuming it's meant to be used like below:
type MyTextProps = {
  style: StyleProp,
}

<MyText style={{ color: '#999', fontSize: 12 }}>Hello</Text>

I've also added void to the StyleValue, as undefined seems to be handled fine, and can be a useful shorthand in JSX.

And finally, I've allowed nesting of style prop arrays, by making StyleProp self-referencing, as RN seems to flatten those without issue.  This can be important if you're passing in a style prop quite high up the component tree, and sticking it in an array with other styles at several points while it's passed down.
Test Plan
N/A (These types aren't referenced anywhere else)
Release Notes
[INTERNAL] [MINOR] [StyleSheet] - Refine Flow types

LGTM!

Thanks for contributing!


Get-PnPTenantSite: Missing Teams related properties (ex: IsTeamsConnected)

The Get-SPOSite cmdlet now supports the following Teams-related properties that are currently missing in the Get-PnPTenantSite cmdlet.
$Sites = Get-SPOSite
$Sites[0] | Select Team | FL
IsTeamsConnected        : False
IsTeamsChannelConnected : False
TeamsChannelType        : None
@wobba @alirobe @jackpoz @erwinvanhunen

hi @morgantechspace , have added these properties to be returned when using Get-PnPTenantSite cmdlet.
It will be available in tomorrow's nightly

Thank you

hi @morgantechspace , have added these properties to be returned when using Get-PnPTenantSite cmdlet. It will be available in tomorrow's nightly

Thanks @gautamdsheth


Proper Integration Testing

Is your feature request related to a problem? Please describe.
As it came out in this PR  there are scenarios which currently can't be tested. That is caused by using mocks in all kind of specs, e.g.  MultiSheetTabSpec.
Describe the solution you'd like
We have to think about a way to implement integration tests for the modeler. In this it should be possible to test real user scenarios and to prevent certain bugs came out again. This will help us to avoid using mocks.

Next step: Just doing it!


Artifact Registry task template

Template for artifact registry package upload tasks, which will eventually replace the current cloud rapture package upload tasks.
No instances of this task are being called yet, until a follow up PR.

/hold

/unhold

/hold

/unhold


Enabling cla functionality in mungegithub for contrib.

This PR contains:

Modifications to the CLA munger to enable ping notifications
Fixes to the deployment, and addition of a new parameter required by the CLA munger.
Turning on the mungegithub handling of CLA on contrib.

cc @sarahnovotny @bgrant0607

This change is

@eparis It might be useful as a way to filter PRs by CLA status, and for the cla:human-approved thing to work. The submit-queue honors the labels and not the status. Do you think there is a way around that?

Cool thanks! looks good to me!

/lgtm


Unstable carbon instance

Hello,
I have 3 graphite servers which were working fine but recently we have had stability issues with one of the nodes.
I see this error in the console.log which occurs repeatedly,
04/05/2017 06:10:35 :: Starting factory CarbonClientFactory(<IP_ADDRESS>:2024:2)
04/05/2017 06:10:35 :: <twisted.internet.tcp.Connector instance at 0x7ff93269fea8> will retry in 4 seconds
04/05/2017 06:10:35 :: Stopping factory CarbonClientFactory(<IP_ADDRESS>:2024:2)
04/05/2017 06:10:40 :: Starting factory CarbonClientFactory(<IP_ADDRESS>:2024:2)
04/05/2017 06:18:58 :: <twisted.internet.tcp.Connector instance at 0x7ff9326af290> will retry in 3 seconds
04/05/2017 06:18:58 :: Stopping factory CarbonClientFactory(<IP_ADDRESS>:2014:1)
04/05/2017 06:19:01 :: Starting factory CarbonClientFactory(<IP_ADDRESS>:2014:1)
04/05/2017 06:19:01 :: <twisted.internet.tcp.Connector instance at 0x7ff9326af290> will retry in 5 seconds
04/05/2017 06:19:01 :: Stopping factory CarbonClientFactory(<IP_ADDRESS>:2014:1)
04/05/2017 06:19:03 :: Exception in cacheFull event handler: args=() kwargs={}
Traceback (most recent call last):
  File "/opt/owl/graphite/lib/twisted/internet/defer.py", line 393, in callback
    self._startRunCallbacks(result)
  File "/opt/owl/graphite/lib/twisted/internet/defer.py", line 501, in _startRunCallbacks
    self._runCallbacks()
  File "/opt/owl/graphite/lib/twisted/internet/defer.py", line 588, in _runCallbacks
    current.result = callback(current.result, *args, **kw)
  File "/opt/owl/graphite/lib/carbon/client.py", line 114, in queueFullCallback
    events.cacheFull()
--- <exception caught here> ---
  File "/opt/owl/graphite/lib/carbon/events.py", line 20, in __call__
    handler(*args, **kwargs)
  File "/opt/owl/graphite/lib/carbon/events.py", line 32, in <lambda>
    cacheFull.addHandler(lambda: carbon.instrumentation.increment('cache.overflow'))
exceptions.NameError: global name 'carbon' is not defined

04/05/2017 06:19:07 :: Starting factory CarbonClientFactory(<IP_ADDRESS>:2014:1)
04/05/2017 06:19:07 :: <twisted.internet.tcp.Connector instance at 0x7ff9326af290> will retry in 5 seconds
04/05/2017 06:19:07 :: Stopping factory CarbonClientFactory(<IP_ADDRESS>:2014:1)
04/05/2017 06:19:13 :: Starting factory CarbonClientFactory(<IP_ADDRESS>:2014:1)
04/05/2017 06:19:13 :: <twisted.internet.tcp.Connector instance at 0x7ff9326af290> will retry in 6 seconds
04/05/2017 06:19:13 :: Stopping factory CarbonClientFactory(<IP_ADDRESS>:2014:1)
04/05/2017 06:19:19 :: Starting factory CarbonClientFactory(<IP_ADDRESS>:2014:1)
04/05/2017 06:19:19 :: <twisted.internet.tcp.Connector instance at 0x7ff9326af290> will retry in 4 seconds

Also i see these error in the clients.log,
04/05/2017 06:35:58 :: CarbonClientFactory(<IP_ADDRESS>:2014:1)::clientConnectionFailed (<IP_ADDRESS>:2014) Connection was refused by other side: 111: Connection refused.
04/05/2017 06:36:02 :: CarbonClientFactory(<IP_ADDRESS>:2014:1)::startedConnecting (<IP_ADDRESS>:2014)
04/05/2017 06:36:02 :: CarbonClientFactory(<IP_ADDRESS>:2014:1)::clientConnectionFailed (<IP_ADDRESS>:2014) Connection was refused by other side: 111: Connection refused.
04/05/2017 06:36:06 :: CarbonClientFactory(<IP_ADDRESS>:2014:1)::startedConnecting (<IP_ADDRESS>:2014)

Please help, and please explain clearly the issue.

@kira510 - that's a bug, it was fixed in 0.9.16
In your case it's just a symptom though, your cache is overflowing, and throwing this error trying to instrument that condition.

Alright, thanks a lot. Upgrading over 0.9.13 might not fix the issue, i will perform a fresh deployment of 0.9.16


Deprecate the CamelSource controller

This is not a stop in our contributions to Knative, we've just moved to a better model where users can pick sources from a growing Catalog of Kamelets and use them in Knative.
The Camel K operator can now use sink-binding to determine the configured destination, so the CamelSource controller contained in this repository is no longer necessary.
The new kn-source-kamelet CLI plugin provides also a better user experience for Knative users that want to try Kamelets.
We can keep updating this repo for a few Knative releases, then it can be archived.
cc: @matzew , @christophd , @rhuss  , @grantr , @vaikas , @n3wscott , @mattmoor

Release Note

Knative CamelSources have been deprecated in favor of Kamelets

Docs

/lgtm

Looks good to me, and as there is a clear migration path I'm happy to archive this repo asap.
Maybe we could add already a date into the README when it will be archived ? E.g. with the next Knative release (0.23) or so ?

Right. Since deprecation will appear in next 0.23 release notes, I think we're fine to archive this right after next release. I'll specify it in the readme.

@nicolaferraro guess it's not important that the test is green and you don't plan to fix this issue? If so, happy to unprotect the branch for a moment and manually merge.

@nicolaferraro guess it's not important that the test is green and you don't plan to fix this issue? If so, happy to unprotect the branch for a moment and manually merge.

Yes, the E2E test is not working. We can merge it. Thanks


Benadryl Social Pollen Count Sensor

Description:
Adds a new sensor platform for the pollen count.

Pull request with documentation for home-assistant.io (if applicable): home-assistant/home-assistant.io#9583
Example entry for configuration.yaml (if applicable):
sensor:
  - platform: pollen_benadryl

Checklist:

[x] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[x] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[x] Untested files have been added to .coveragerc.

I have a few concerns regarding this one:

It's quite proprietary, which means the API is likely to change
It only covers the UK, nowhere else in the world
It doesn't hide the implementation details in a library
It's really just a wrapper around a single REST call.

My feeling is that this would be better served by a REST sensor, and not accepting this PR.

This is essentially an over-engineered rest sensor. Closing


Add fs-extra as dependency

The strategy of loading optional dependencies is non-deterministic as a fs-extra or graceful-fs library loaded in a subtree of the dependency tree may be loaded instead of the desired implementation.  This could be caused by the non-deterministic loading of npm3, but there may have been cases in npm2 where this occurred as well.  This is was also an issue in any-promise with a resolution discussed in kevinbeaty/any-promise#1
Options:

Add fs-extra as an explicit dependency.
Add graceful-fs as an explicit dependency
Only use fs and remove loading of optional dependencies.

Proposal:
Add fs-extra as an explicit dependency (Option 1).

FWIW, I would be fine with this library evolving into an extension for fs-extra. I almost always include both.

This issue may actually be overstated since the libraries are API compatible in the order of require, i.e. if fs-extra is loaded but the user is only expecting fs, all expected functions will still work as they are passed through.
I may leave this alone until someone actually experiences an issue with the current behavior.

Reopened because  @jonathantneal mentioned in #6 that he did indeed run into issues with the optional loading of fs-extra.

Closed by #8


test

How to display the test results, which is the confusion matrix

pls refer to lib/utils/measure.py

There is no the results of the confusion matrix when running text_submission. py

test_submission is just for the hold-out test, not for validation, there is no ground-truth for the hold-out test set, we only submit the results to the Challenge organizations, and then they will evaluate your submission on their hold-out ground-truth.

Is the indicator in the paper the result of the validation set or the test set

How to obtain the results of comparative experiments without real labels from the test set

Just compare models on your validation set. You cannot get the IOU or F1 scores on the hold-out test set now since the workshop has already ended and closed any submission evaluations.


Doesn't work with python 2.7

Describe the bug
The code doesn't work with python 2.7. converter.py in line 210 imports SimpleNamespace from types which was added only in python3.3, so it throws error for me. Any suggestions to quickly fix this will be appreciated a lot. Thanks!
Code
resnet = models.resnet50(pretrained=False)
modules = list(resnet.children())[:-1]
model = nn.Sequential(*modules)
 state_dict = load_checkpoint("resnet50_weights.pth")
 model.load_state_dict(state_dict)
 print("loading weights to resnet successful")
 torch.save({'state_dict': state_dict}, "im2recipe_resent_weigts.pth")

 input_np = np.random.uniform(0, 1, (1, 3, 224, 224))
 input_var = Variable(torch.FloatTensor(input_np))
 k_model = pytorch_to_keras(model, input_var, (3, 224, 224), verbose=True)

Error
Traceback (most recent call last):
File "get_resnet_weights.py", line 34, in
k_model = pytorch_to_keras(model, input_var, (3, 224, 224), verbose=True)
File "/home/mohsin/visio/scripts/im2recipe/py27/local/lib/python2.7/site-packages/pytorch2keras/converter.py", line 210, in pytorch_to_keras
from types import SimpleNamespace
ImportError: cannot import name SimpleNamespace
Environment

Ubuntu 16.04
Python 2.7.12

hello @mohsinkhn.
I fixed this issue. Can you fetch the latest (git master) version and try again?

Thanks! It works on master.


Make build command a bit more obvious

This tripped me up for a bit wondering why mvn was on my path, but there wasn't a mvnw

Thanks! I missed this one, as I don't use Linux myself.


Create prometheus-alertmanager-presubmits.yaml

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

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: abhay-krishna
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [abhay-krishna]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@abhay-krishna: Updated the job-config configmap in namespace default at cluster default using the following files:

key prometheus-alertmanager-presubmits.yaml using file jobs/aws/eks-distro-build-tooling/prometheus-alertmanager-presubmits.yaml

In response to this:

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

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Pathfinder 2E: World Time Sync causes massive lag

Describe the bug
A calendar with a lot of notes causes massive slowdown when using the module in the Pathfinder 2E system, if the Pathfinder 2E: World Time Sync setting is on.
To Reproduce
Steps to reproduce the behavior:

Fresh Pathfinder 2E world with no mods except Simple Calendar.
Set the Pathfinder 2E: World Time Sync setting to true.
Add a bunch of notes on different days in the calendar.
Clicking on different days, changing month, shifting from simple to detailed calendar view and other things will be increasively slowed down depending on the amount of notes. I could easily get it up to 10 seconds of freeze.

Expected behavior
No lagg-freezing with the Pathfinder 2E: World Time Sync setting enabled :grin:
Foundry Information

Foundry Version: 10
Game System: Pathfinder 2E 4.0.0-Beta3
Simple Calendar Version: 2.1.10

Browser (please complete the following information):

Chrome

Additional context
I thought I'd follow up from the discussion on the topic at Discord here.
The 2.1.10 version removed the warnings caused by having the World Time Sync setting active, but appearantly the root cause of the non-responsivness is still there. If I would have to hazard a guess, then something is looping a -lot-, since so many warnings were originally being thrown because of a singular click (sometimes 10k warnings).
I don't know the nature of the problem, and perhaps it is because of the current Pathfinder Beta version, but at least there's an issue to follow up on here now. 😄

Darn I was hoping it was just the flood of warnings slowing things down (which it can).
I had a look at it and the system changed the way I access some details to keep the 2 clocks in sync. I updated how I'm accessing them and the slow down disappeared. I tested with 1500 notes and it was nice and quick after.
I have a couple other things I want to get in the next update but hope to have it out in the next day or two.

Sorry about the delay, life got in the way of this release, but it has been fixed in version 2.1.18


bug with using credentials

A bug occurs when using a POST request with credentials and passing data through the request.body. If credentials not using or if turn off serverFactory, so all works is correctly. How to fix this?

can you show me a code example?

yes, sure... I'm using typescript and
// server.ts
import { fastifyUws, serverFactory } from '@geut/fastify-uws'
import fastify from 'fastify'
import dotenv from 'dotenv'
import app from './app'

dotenv.config()

const port = process.env.PORT as unknown as number
const host = process.env.HOST as unknown as string

const server = fastify({
  serverFactory,
})

server.register(fastifyUws)
server.register(app)

server.listen({ port, host }, () => {})

// app.ts
import cors from '@fastify/cors'
import type { FastifyPluginAsync } from 'fastify'

const app: FastifyPluginAsync = async (fastify, opts): Promise<void> => {
  void fastify.register(cors, {
    credentials: true,
    origin: ['http://<IP_ADDRESS>:3333'],
    methods: ['GET', 'POST', 'PUT', 'PATCH', 'DELETE'],
  })

  void fastify.register(AutoLoad, {
    dir: join(__dirname, 'plugins'),
    options: opts,
  })

  void fastify.register(AutoLoad, {
    dir: join(__dirname, 'routes'),
    options: Object.assign({ prefix: `/api/${process.env.API_VERSION}` }, opts),
  })
}

// router file
import type { FastifyPluginAsync } from 'fastify'
import { isLoggedIn } from '../../middleware/isLoggedIn'

const chart: FastifyPluginAsync = async (fastify): Promise<void> => {
  fastify.post('/create', {
    preHandler: isLoggedIn,
  },
  async (request, reply) => {
    try {
      const { ...someData } = await request.body
      const chart = await fastify.prisma.charts.create({
        data: { ... someData},
      })
      await reply.code(201).send(chart.id)
    }
    catch (e) {
      await reply.code(500).send('uups...')
    }
  },
  )

This request ('/create') is not executed at all, and there are no errors either, it just frozen. But if remove prehandler and credentials, then works fine.

P.S. One more clarification. The issue occurs only if the data is transferred via "body". If transferring through "query" then all works correctly too

thank you @brokolosov for all the information, I will look into it

i check this by doing a test and i cannot reproduce the problem:
import { test } from 'uvu'
import * as assert from 'uvu/assert'
import Fastify from 'fastify'
import cors from '@fastify/cors'
import { serverFactory, fastifyUws } from '../src/index.js'

test('cookies', async () => {
  const app = Fastify({
    serverFactory
  })

  app.register(fastifyUws)

  app.register(cors, {
    credentials: true,
    origin: ['http://<IP_ADDRESS>:3333'],
    methods: ['GET', 'POST', 'PUT', 'PATCH', 'DELETE']
  })

  app.post('/', {
    preHandler: async () => {
      console.log('all good')
    }
  }, (req, res) => {
    console.log(req.body)
    return { ok: true }
  })

  await app.listen({ port: 3333 })

  const res = await fetch(`http://localhost:${app.server.address().port}`, {
    method: 'POST',
    credentials: 'include',
    headers: {
      'Content-Type': 'application/json'
    },
    body: JSON.stringify({ hi: true })
  }).then(res => res.json())

  console.log(res)

  await app.close()
})

test.run()

Thank you for your time. It turned out to be much more complicated. The conflict occurs with the "session.store" module. But so far, I have not figured out what exactly the bug is.