First frame takes on appearance of second frame in Spritesheets created from trimmed Texture Atlas Frames

Version

Phaser Version: v3.14.0-FB

Operating system: Windows 10

Browser: Not applicable

Description

In SpriteSheets created from a texture atlas with TextureManager.addSpriteSheetFromAtlas(), the first frame becomes identical to the second frame. In all usage, including animations, the first frame will appear as the second frame instead.
Example Test Code

The following code is pulled directly from the following Phaser 3 Example. I have modified all the animation configurations to only use the first 2 frames in order to demonstrate that the animations derived from the trimmed texture atlases will appear to "freeze" because both frames are identical due to this bug, while their untrimmed counterparts will rapidly display the first 2 frames as expected.
var config = {
    type: Phaser.AUTO,
    parent: 'phaser-example',
    width: 800,
    height: 600,
    scene: {
        preload: preload,
        create: create
    }
};

var game = new Phaser.Game(config);

function preload ()
{
    this.load.path = 'http://labs.phaser.io/assets/atlas/trimsheet/';

    this.load.atlas('testanims', 'trimsheet.png', 'trimsheet.json');
}

function create ()
{
    var t1 = this.textures.addSpriteSheetFromAtlas(
        'boom1',
        {
            atlas: 'testanims',
            frame: 'explosion-notrim',
            frameWidth: 64,
            frameHeight: 64,
            endFrame: 23
        });

    var t2 = this.textures.addSpriteSheetFromAtlas(
        'boom2',
        {
            atlas: 'testanims',
            frame: 'explosion',
            frameWidth: 64,
            frameHeight: 64,
            endFrame: 23
        });

    var b1 = this.textures.addSpriteSheetFromAtlas(
        'bubble1',
        {
            atlas: 'testanims',
            frame: 'bubble-notrim',
            frameWidth: 34,
            frameHeight: 68
        });

    var b2 = this.textures.addSpriteSheetFromAtlas(
        'bubble2',
        {
            atlas: 'testanims',
            frame: 'bubble',
            frameWidth: 34,
            frameHeight: 68
        });

    var config1 = {
        key: 'explode1',
        frames: this.anims.generateFrameNumbers('boom1', { start: 0, end: 1 }),
        frameRate: 20,
        repeat: -1
    };

    var config2 = {
        key: 'explode2',
        frames: this.anims.generateFrameNumbers('boom2', { start: 0, end: 1 }),
        frameRate: 20,
        repeat: -1
    };

    var config3 = {
        key: 'bobble1',
        frames: this.anims.generateFrameNumbers('bubble1', { start: 0, end: 1 }),
        frameRate: 10,
        repeat: -1
    };

    var config4 = {
        key: 'bobble2',
        frames: this.anims.generateFrameNumbers('bubble2', { start: 0, end: 1 }),
        frameRate: 10,
        repeat: -1
    };

    this.anims.create(config1);
    this.anims.create(config2);
    this.anims.create(config3);
    this.anims.create(config4);

    this.add.sprite(300, 200).play('explode1');
    this.add.sprite(400, 200).play('explode2');

    this.add.sprite(300, 400).play('bobble1');
    this.add.sprite(400, 400).play('bobble2');
}

Additional Information

I have identified the cause of problem.
For untrimmed texture atlas frames, Parser.SpriteSheet() is used to create the SpriteSheet. This function adds a __BASE texture source entry.
However, for trimmed texture atlases texture atlases, Parser.SpriteSheetFromAtlas() is used, and this function does not add a __BASE texture source entry. This impacts how the texture is handled in Texture.get().
In Texture.get(), there is a check:
  //  null, undefined, empty string, zero
  if (!name)
  {
      name = this.firstFrame;
  }

If a number 0 is passed to this function, this normally would not be a problem for a SpriteSheet because its firstFrame is frame 0 anyway, and everything continues on as expected. However, in the case of a SpriteSheet without a __BASE texture source entry, the firstFrame ends up being the second frame instead due to the following code in Texture.add():
 //  Set the first frame of the Texture (other than __BASE)
  //  This is used to ensure we don't spam the display with entire
  //  atlases of sprite sheets, but instead just the first frame of them
  //  should the dev incorrectly specify the frame index
  if (this.frameTotal === 1)
  {
      this.firstFrame = name;
  }

Therefore the returned firstFrame is in fact the second frame.
I'm going to open a PR with a minimalist fix. The fix for this particular bug should be as simple as modifying the above check to handle the case where a __BASE texture does not exist.
That being said, it may be worth also having a look at why a __BASE texture entry isn't added in Parser.SpriteSheetFromAtlas() in the first place.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Thanks for opening this issue, and for submitting a PR to fix it. We have merged your PR into the master branch and attributed the work to you in the Change Log. If you need to tweak the code for whatever reason please submit a new PR.


Debug msa

Implements:

changes to the integration test framework
new test for the MSA checking provenance output
fixes bug in provenance output.
fixes some BE-FPLX renaming issues (maintaining backwards compatibility where possible).

Thanks!


Bump rand related crates.

rand_core to 0.6.4
rand to 0.8.5
Signed-off-by: Masaki Muranaka<EMAIL_ADDRESS>This will enable us to create mnemonics on wasm32.
I checked on the latest version of Chrome.
// Example: Part-of-core.rs
let m = Mnemonic::generate_in(Language::English, 12).unwrap();

// Example: Part-of-Cargo.toml
[patch.crates-io]
bip39 = { git = "https://github.com/monaka/rust-bip39", branch = "bump-rand-and-rand_core" }

[dependencies]
bip39 = { version = "1.0.1", features = ["rand"] }
getrandom = { version = "0.2", features = ["js"] }

Thanks for the PR!
The current rand versions are because of the old MSRV currently used (1.29). There is an open PR to bump that to 1.41.1 which includes the upgrades of rand crates you have here.
Steven the maintainer is a bit snowed under at the moment but soon we should have some progress here.

In v2.0.0 the constraints on rand_core and rand are relaxed, so you should be able to resolve your problem with that version.


Normalized line ending for .gitignore.

I also added in the exclude list the .idea/ subfolder created by PhpStorm.

@stof I removed the .idea and pushed the updated branch.
Regards
Adriano


Implemented workaround for GHDL 0.34dev.

Hello,
this pull request implements a workaround needed for the current GHDL 0.34dev release (tgingold/ghdl@6235a6a).
Workaround 1:
The issue is reported as issue #190.
GHDL complains that addr_value is not static in a case statement.
Workaround 2:
The issue is reported as issue #191.
GHDL complains about 'others' used to initialize unconstrained arrays as record elements.
BugFix 1:
Procedure parameters of kind inout cannot be connected to parameters of kind out.
(Sorry, my branch renaming operation closed the pull-request #5. This behavior is new to GitHub :( )

As I understand the explanations of @diogratia in 'others' choice not allowed for an aggregate in this context, it is not correct to use the others keyword. So my workaround submitted in a178fb3 becomes a bugfix.

Sorry for the (very) slow response on this bug.
I have implemented your bugfix on the latest UVVM release now. I did the update manually, so that I could apply the fix on all of our VIPs where the bug is present.
Thank you very much for the bug report!
Kind regards
Andre


remove dead Imperial Guards from party window's allies list

Would it be possible to remove the dead imperial guards spawned by the Imperial Guard Reinforcement Orders from the party window? The party window can get pretty confusing when some stones were popped and you have to watch allies, for example.
Thanks.

I guess you mean any dead summoning stone? Or is there any specific reason for Imperial Guards?
Anyway, this might be trickier than it seems, because not only we need to make the client hide them, but also make sure that nothing references those, and the client doesn't crash when the server eventually decides that it's time to hide them.

Its specific for imperial guards, they dont disappear from the group window at all.

TIL. This feels like one of the easy fixes the devs should implement. It should be easy for them and hard for us, but we'll see.

devs should implement

about that


Extend luigi.contrib.ecs module to support feeding additional kwargs to ecs run_task

Description
This updates the luigi.contrib.ecs module by providing a new overridable run_task_kwargs property that can be used to feed additional keyword arguments to the boto3 ECS run_task call.
Motivation and Context
The existing module only allows users to provide dynamic container commands via containerOverrides, so is very limited to running simple ECS tasks. With these changes, it's now possible to change the launch type on the fly (e.g. EC2 -> FARGATE), give a task additional ephemeral storage, specify custom network configuration, etc.
These changes play nicely with the old version of the module and don't break the previous API.
Have you tested this? If so, how?
Yes, I updated test/contrib/ecs_test.py and all tests pass.

@greenlaw , to my knowledge this project is still "alive", although very quiet. While I have write access to the repo as a community maintainer, I am not an admin nor employee of Spotify. I cannot speak to Spotify's stance on the luigi project. And while I do have write access, my project context and time grows stale as I no longer utilize luigi in my day job. As such, I have limited time to review and provide feedback here.
As folks submit PRs, I'm happy to take a look. However, I cannot be the sole person reviewing all submissions. Nor can I commit to an SLA on my responses. Please feel welcome to review and provide feedback to other community submissions as your time and energy allows!

For your PR, I apologize for approving your PR so long ago without merging. I've updated the branch and will merge once the checks pass.


PoC: Isolate dependency injections by specific pattern

Hey, I have a idea how to improve injector for scopes in business logic.
I create simple PR for discussing and share this idea
Idea
Imagine a situation when you have an application with 2 different scopes: Accounts and Orders. And in each scope (or domain) you have specific operations and repositories. And in account repo we have a similar method name find:
module Accounts
  # Operations for accounts
  module Operations
    class List
      # ...
    end

    class Show
      # ...
    end
  end

  # Repos for accounts
  module Repositories
    class Accounts
      def find(id)
        # ...
      end
    end
  end
end

module Orders
  # Operation for orders
  module Operations
    class Create
      # ...
    end

    class Checkout
      # ...
    end
  end

  # Repos for orders
  module Repositories
    class Orders
      # ...
    end

    class Accounts
      def find(order_id)
        # ...
      end
    end
  end
end

We put all these classes into a container and now we can fail if someone injects account repo from Accounts to Orders scope:
module Orders
  # Operation for orders
  module Operations
    class Create
      # OK for us
      include Inject['orders.repositories.accounts']

      # BAD but we get a exeption ONLY after first call
      include Inject['accounts.repositories.accounts']

      # ...
    end
  end
end

Important thing
This code (with injection 'accounts.repositories.accounts') raise error only after booting and first real call.

For detecting these situations I introduce allow method with simple regexp pattern:
module Accounts
  Inject = Inject.allow(/\Aaccounts.+/) # allow to inject only "accounts.*" keys

  # ...
end

module Orders
  Inject = Inject.allow(/\Aorders.+/) # allow to inject only "orders.*" keys

  module Operations
    class Create
      include Inject['orders.repositories.accounts'] # OK for us
      include Inject['accounts.repositories.accounts'] # raise error on object initialization step

      # ...
    end
  end

  # ...
end

And now, if we will try to inject 'accounts.repositories.accounts' to Orders::Operations::Create we fail on creating an instance of operation.
Implementation
It's just a proposal of my vision. I'm not sure that allow better name for this. But I'll be happy to discuss it with everyone ❤

cc @solnic @timriley @flash-gordon @GustavoCaso

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 4

See the complete overview on Codacy


agent: add default timeout for grpc requests

If guest is malfunctioning, we need a way to bail out. Add
a default timeout for most of the grpc requests so that the
runtime does not wait indefinitely.
Fixes: #1952

/test

weird error in nemu-ci
[3] Stderr: docker: Error response from daemon: OCI runtime create failed: nemu-system-x86_64: -device vhost-user-fs-pci,chardev=char-244fa09c3e4ac8e7,tag=kataShared,cache-size=1024M: Failed to read msg header. Read 0 instead of 12. Original request 1.
[3] nemu-system-x86_64: -device vhost-user-fs-pci,chardev=char-244fa09c3e4ac8e7,tag=kataShared,cache-size=1024M: vhost_dev_init failed: Operation not permitted: unknown.

@devimc That one seems to be a virtiofsd bug and is fixed by patch "virtiofsd: simplify setup_remount_slave" that I just sent to the virtiofs list today.

@bergwolf

@devimc That one seems to be a virtiofsd bug and is fixed by patch "virtiofsd: simplify setup_remount_slave" that I just sent to the virtiofs list today.

cool


An incorrect value is specified in the Source parameter or in the Destination parameter.

I am using the non hot fix version of 7.2.3 as the hot fix version has a bad signature and is blocked by AV.
Having trouble downloading drivers for Dell Latitude 5450, 5550, and 7350. Other Dell driver packages download and process properly. I get the same error in the log for each one.
DAT creates the source folders like \\server\sccm_source$\Drivers\Source\Dell\Latitude 5450\Driver Cab but then the download fails.

======== Dell ConfigMgr Latitude 5450 DRIVER PROCESSING STARTED ========	DriverAutomationTool	2024-04-03  3:22:59 PM	22208 (0x56C0)
ConfigMgr: Latest driver revision found - 	DriverAutomationTool	2024-04-03  3:22:59 PM	22208 (0x56C0)
ConfigMgr: Checking ConfigMgr for driver packages matching - Drivers - Dell Latitude 5450 - Windows 11 x64	DriverAutomationTool	2024-04-03  3:22:59 PM	22208 (0x56C0)
ConfigMgr: New driver package detected - Processing	DriverAutomationTool	2024-04-03  3:23:00 PM	22208 (0x56C0)
ConfigMgr: Calling content download function	DriverAutomationTool	2024-04-03  3:23:00 PM	22208 (0x56C0)
ConfigMgr: Creating Latitude 5450 download folder	DriverAutomationTool	2024-04-03  3:23:00 PM	22208 (0x56C0)
ConfigMgr: Creating \server\sccm_source$\Drivers\Source\Dell\Latitude 5450\Driver Cab folder 	DriverAutomationTool	2024-04-03  3:23:00 PM	22208 (0x56C0)
ConfigMgr: Downloading 	DriverAutomationTool	2024-04-03  3:23:00 PM	22208 (0x56C0)
ConfigMgr: Downloading from URL: https://downloads.dell.com/	DriverAutomationTool	2024-04-03  3:23:00 PM	22208 (0x56C0)
_**======== Errors(s) Occurred ========	DriverAutomationTool	2024-04-03  3:23:00 PM	22208 (0x56C0)
[Error] - An incorrect value is specified in the Source parameter or in the Destination parameter. Verify that the directory and file names in the Source and Destination parameters are correct.	DriverAutomationTool	2024-04-03  3:23:00 PM	22208 (0x56C0)**_
DriverAutomationTool	2024-04-03  3:23:00 PM	22208 (0x56C0)
ConfigMgr:  file download failed	DriverAutomationTool	2024-04-03  3:23:00 PM	22208 (0x56C0)
======== Dell ConfigMgr Latitude 5450 DRIVER PROCESSING FINISHED ========	DriverAutomationTool	2024-04-03  3:23:00 PM	22208 (0x56C0)

I'm seeing the same with the Latitude 5450 and Latitude 5550. Did a Optiplex 7020 (Micro and SFF) with out an issue.
I'm using the forked version  of the .ps1 provided by ajn142attamu (https://github.com/maurice-daly/DriverAutomationTool/issues/524#issuecomment-1972124395) until the msi hotfix issues are fixed.

I also tested it with the latest official .ps1 and received the same error.

I'm getting the same for 5550. Tried updating to 7.2.3 to see if it was something with the application and now my AV is eating the newer executable.. so we're dead in the water for this tool until I can get it whitelisted. Manually crafting driver packages is a pain when you're used to having this tool doing the work for you!

My guess is that it has something to do with these models being so new but
I don't know what.
On Thu, Apr 18, 2024 at 3:15 PM mchippy @.***> wrote:

I'm getting the same for 5550. Tried updating to 7.2.3 to see if it was
something with the application and now my AV is eating the newer
executable.. so we're dead in the water for this tool until I can get it
whitelisted. Manually crafting driver packages is a pain when you're used
to having this tool doing the work for you!
—
Reply to this email directly, view it on GitHub
https://github.com/maurice-daly/DriverAutomationTool/issues/537#issuecomment-2065337081,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWVSYTJLEDDADS6TYO2NRTTY6AZYTAVCNFSM6AAAAABFWDV3V2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRVGMZTOMBYGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Yeah, I'm not sure either. I downloaded the EXE manually and placed it, but it can't run the extraction now.

I couldn't make manual package creation work either. I downloaded the CAB,
expanded it using the EXE, and then used DISM to create my package.
On Thu, Apr 18, 2024 at 3:43 PM mchippy @.***> wrote:

Yeah, I'm not sure either. I downloaded the EXE manually and placed it,
but it can't run the extraction now.
image.png (view on web)
https://github.com/maurice-daly/DriverAutomationTool/assets/97312277/5e3ce191-4322-4fd4-8748-eb0cb5dbdebd
—
Reply to this email directly, view it on GitHub
https://github.com/maurice-daly/DriverAutomationTool/issues/537#issuecomment-2065375114,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWVSYTLAUYKNJHUZB4PUPJDY6A5AVAVCNFSM6AAAAABFWDV3V2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRVGM3TKMJRGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Ouch. Thanks, mate. Looks like these will have to be manual.

Yeah, it was ugly.
On Thu, Apr 18, 2024 at 3:47 PM mchippy @.***> wrote:

Ouch. Thanks, mate. Looks like these will have to be manual.
—
Reply to this email directly, view it on GitHub
https://github.com/maurice-daly/DriverAutomationTool/issues/537#issuecomment-2065379452,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWVSYTO6KAE2O3VPS2AVDJ3Y6A5PTAVCNFSM6AAAAABFWDV3V2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRVGM3TSNBVGI
.
You are receiving this because you authored the thread.Message ID:
@.***>

Looks like it might be working after I manually extracted the drivers to the "Windows11-" directory it creates. If I try and give the Windows11- it's version (A00), it doesn't see it, so it might have something to do with the way Dell is naming of the files? Might have to rename some of the directories to append "A00" and do a little cleanup. fingerscrossed

I'll try that, I have a couple more that aren't working.
On Thu, Apr 18, 2024 at 3:58 PM mchippy @.***> wrote:

Looks like it might be working after I manually extracted the drivers to
the "Windows11-" directory it creates. If I try and give the Windows11-
it's version (A00), it doesn't see it, so it might have something to do
with the way Dell is naming of the files? Might have to rename some of the
directories to append "A00" and do a little cleanup. fingerscrossed
image.png (view on web)
https://github.com/maurice-daly/DriverAutomationTool/assets/97312277/106f19bd-89de-4bf5-a58d-8339d2b2e79a
—
Reply to this email directly, view it on GitHub
https://github.com/maurice-daly/DriverAutomationTool/issues/537#issuecomment-2065394790,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWVSYTLVZQCW5YTWWPQEFHDY6A6YTAVCNFSM6AAAAABFWDV3V2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRVGM4TINZZGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Looks like it might be working after I manually extracted the drivers to the "Windows11-" directory it creates. If I try and give the Windows11- it's version (A00), it doesn't see it, so it might have something to do with the way Dell is naming of the files? Might have to rename some of the directories to append "A00" and do a little cleanup. fingerscrossed

Can you provide a bit more detail on how you accomplished this?

We have the issue with the Latitude 5550 as well. I'm suspecting this might have something to do with Dell's (idiotic) decision to re-use model names. Notice that both the 5550 and 5450 both have E-named equivalents, but the version of the name without the E was used in Dell's documentation - case in point: https://www.dell.com/support/manuals/en-us/latitude-e5450-laptop/dell_latitude_e5450_om-v1/technical-specifications?guid=guid-ff58d80e-59c8-4c89-bcf1-57aedc89cc0d&lang=en-us  - the "Dell Latitude E5450 / 5450 Owner's Manual"
I speculate that DAT needs some improved logic to handle Dell's stupid naming decisions.

@TokenRing  is right this issue is Dell recycling the model name.  Here is a breakdown of what I am seeing.  When downloading the Latitude 5550 driver with the DAT the Latitude 5550 has the SKU/Identifiers as 0CB9 and 0CBC.  The tool downloads, extracts, and creates the package for Windows 10 but fails for Windows 11 drivers. Here are the screenshots from these resources.
DAT Latitude 5550 item:

Package General Tab:

DAT downloaded cab and manifest xml:

Manually downloading the drivers from https://www.dell.com/support/kbdoc/en-us/000109893/dell-command-deploy-driver-packs-for-latitude-models

Notice the newer driver files are version A01.
As you can see the DAT is downloading the old Latitude E5550 model's driver package from 2020 version A08, then importing it as the newer Latitude 5550 and applying the newer sku's to the metadata of the old driver.
This is causing my OSD task sequences to fail and the computer blue screens after when booting to the full OS for the first time.  This is also the reason Windows 11 drivers are failing to download where Windows 10 is downloading something.  Since there are no Win 11 drivers available for that old device.
I am going to manually create my packages for this model.  If anyone has a good tutorial for me I would appreciate it.

To use DAT to create these driver packages after manually downloading the drivers:

Download the latest driver package from https://www.dell.com/support/kbdoc/en-us/000124139/dell-command-deploy-driver-packs-for-enterprise-client-os-deployment
Navigate to the share where DAT is saving your driver packages (this is found under the Common Settings tab in DAT).
Drill down to your list of models and create a folder for the model you are attempting to import, i.e. "Latitude 7350" (depending on how far DAT got before it failed, this folder along with some subfolders listed in the next steps may already exist).
Create a "Driver Cab" subfolder within the model folder you just created.
Copy the driver package you downloaded in Step 1 into this Driver Cab folder.
Go back to the model folder and create a "Windows11-" subfolder. Your folder structure will now look something like this:

Either use the command line or a program like 7zip to extract the driver package you copied into the Driver Cab folder into the Windows11- folder.
Open DAT and start the Download/Extract/Import process for the drivers again. It will see the driver package exists, see the extracted files exist in the Windows11- folder, and will automatically create the package for you.
Optionally, you can edit the package info in SCCM and add the correct driver version.

This should tide you over until these drivers can be processed natively via DAT. Hope this helps anyone who was confused, it took a bit of trial and error on my part before I got it working.

Thanks funky-d! That works great!
On Fri, Jul 12, 2024 at 12:13 AM funky-d @.***> wrote:

To use DAT to create these driver packages after manually downloading the
drivers:

Download the latest driver package from
https://www.dell.com/support/kbdoc/en-us/000124139/dell-command-deploy-driver-packs-for-enterprise-client-os-deployment
Navigate to the share where DAT is saving your driver packages
(this is found under the Common Settings tab in DAT).
Drill down to your list of models and create a folder for the model
you are attempting to import, i.e. "Latitude 7350" (depending on how far
DAT got before it failed, this folder along with some subfolders listed in
the next steps may already exist).
Create a "Driver Cab" subfolder within the model folder you just
created.
Copy the driver package you downloaded in Step 1 into this Driver
Cab folder.
Go back to the model folder and create a "Windows11-" subfolder.
Your folder structure will now look something like this:
image.png (view on web)
https://github.com/user-attachments/assets/a8f968d6-4e30-4656-8aec-07dd0243b99f
Either use the command line or a program like 7zip to extract the
driver package you copied into the Driver Cab folder into the Windows11-
folder.
Open DAT and start the Download/Extract/Import process for the
drivers again. It will see the driver package exists, see the extracted
files exist in the Windows11- folder, and will automatically create the
package for you.
Optionally, you can edit the package info in SCCM and add the
correct driver version.

This should tide you over until these drivers can be processed natively
via DAT. Hope this helps anyone who was confused, it took a bit of trial
and error on my part before I got it working.
—
Reply to this email directly, view it on GitHub
https://github.com/maurice-daly/DriverAutomationTool/issues/537#issuecomment-2224833479,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWVSYTMM2CX2YUTMJLKNDNTZL5XW5AVCNFSM6AAAAABFWDV3V2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRUHAZTGNBXHE
.
You are receiving this because you authored the thread.Message ID:
@.***>


[Feature Request] Pasta list with authentication

Currently the status of pasta list is either open (for everyone that has access to see and remove pastas if private pasta is not enabled) or closed (nobody can see anything at all).
I'm hoping for a mode that only the pasta list requires authentication. Or, if private pasta is enabled, one can see all the private pastas after authentication. Basically this sets an "administrator" role who can manage all the pastas.
I understand that microbin is not meant for public usage. But I think it will be useful if someone wants to manage all the pastas without turning on/off list and private and restarting the instance.

@zodiacg I think one way of achieving this (and my plan personally) is to use a reverse proxy to protect the /pastalist/ and /remove/ endpoints with Authentication.
I think deferring authentication to the reverse proxy might be the most appropriate way to keep the project simple - authentication can be messy.

@zodiacg I think one way of achieving this (and my plan personally) is to use a reverse proxy to protect the /pastalist/ and /remove/ endpoints with Authentication.
I think deferring authentication to the reverse proxy might be the most appropriate way to keep the project simple - authentication can be messy.

That's a good suggestion. I didn't realize there are specific endpoints for these operations. I got an Authelia instance and I will use that for authentication. Yes it's more elegant indeed!

I think deferring authentication to the reverse proxy might be the most appropriate way to keep the project simple - authentication can be messy.

I agree your way is definitely very safe and probably not too difficult to configure, although the project already uses http basic authentication, I think optionally only wrapping one or two paths in that would be relatively simple, but honestly I think the basic auth should be replaced with something a little neater at one point - firefox on iOS keeps crashing with this enabled and Safari keeps asking for the password again and again. Basic auth was a very lazy and temporary implementation that we can't really keep much longer, not as the only option anyway. I will not target this for 1.2.0 for now, let's get the small annoyances out of the way and then we can focus on larger issues like this and the sqlite database.


Zachmu/index refactor

Rewrote index interfaces. Indexes are now available either through a driver, or natively via the table implementations themselves.
Also re-enabled auth tests for windows by removing the pilosa dependency, and fixed several test suites that were broken on Linux.

The files to pay attention to are the interface definitions and index_analyzer.go. Almost everything else is rename / moves.


Disabling MapperFeature.DEFAULT_VIEW_INCLUSION is not respected in ModelResolver#hiddenByJsonView

Here https://github.com/swagger-api/swagger-core/blob/4fe32771edc05aed86ddbac5c856ceade13be8d7/modules/swagger-core/src/main/java/io/swagger/v3/core/jackson/ModelResolver.java#L1983 it should return true if DEFAULT_VIEW_INCLUSION is disabled in ObjectMapper.

Thanks for reporting this, not sure about the possible scenarios though; ObjectMapper used by ModelResolver can (and is by default) not the same as e.g. the one used for JSON (de)serialization of payloads by the JAX-RS implementation, or whatever other use. Also if I am not mistaken the fields not annotated with JsonView would be not serialized only when serialization explicitly invoked with a view; the desired behaviour would be therefore probably highly project dependent, please let me know what do you think.
A possible alternative approach since latest 2.1.2-SNAPSHOT would be to customize behaviour if needed by extending ModelResolver and overridding hiddenByJsonView().

Ok, that's fine for now, I can override this now, thanks! But here's the scenario:
I do this on starting my app:
Json.mapper().disable(MapperFeature.DEFAULT_VIEW_INCLUSION);
And then this option is not respected as I reported in this issue.
PS: I use Spring Boot Rest controllers without JAX-RS with this library https://springdoc.github.io/springdoc-openapi-demos/ .

What do you mean "option is not respected"?

@frantuma I call Json.mapper().disable(MapperFeature.DEFAULT_VIEW_INCLUSION); on application startup but in swagger a see properties without JsonView listed in api endpoints responses. That's why i thinks the hiddenByJsonView method should return _mapper.isDisabled(MapperFeature.DEFAULT_VIEW_INCLUSION) instead of just false.

I still believe this is highly project dependent and  should be handled as mentioned above instead of behaviour changed in core, see e.g. cases as mentioned above where serialization is invoked without a view or similar scenarios

Closing ticket, will reopen if alternative solutions come out of any further discussion

@frantuma Ok. Although I disagree that this is highly project dependent as you say because if I'm not mistaken disabled DEFAULT_VIEW_INCLUSION is default configuration for any Spring Boot project...

Hi @frantuma,
I agree with @denis111.
If DEFAULT_VIEW_INCLUSION is set to true, then non-annotated fields are serialized and non-annotated fields are shown in the Swagger UI model. This is fine.
If DEFAULT_VIEW_INCLUSION is set to false, then non-annotated fields are NOT serialized, but non-annotated fields are SHOWN in the Swagger UI model.
In this case, the behavior I would have expected is that Swagger UI mirros the behavior of Jackson, i.e. non-annotated fields are NOT shown in the Swagger UI model.
The default value in SpringBoot for DEFAULT_VIEW_INCLUSION is indeed false, leading to the unexpected behavior explained above by default.

@FlorianCodes thanks! Maybe we should address this issue to https://github.com/springdoc/springdoc-openapi/ then?...

@denis111 I think this is a good idea, since this problem is highly associated to Spring. Do you mind to open an issue and link to this issue?

@FlorianCodes there's similar issue https://github.com/springdoc/springdoc-openapi/issues/665 (but also closed)

Is there a solution to this issue by now?
Just encountered the same problem with springdoc-openapi-starter-webmvc-ui version 2.1.0


Updated to work with Swift 2

This is the only error it is giving for compatibility with Swift 2.

Thanks


Feature Request: loading more items

The current PRs, issues, or trends only display one page of items (30 items I guess), I think we need to support "loading more items by scrolling up" feature, otherwise, the information is incomplete.

I don't have a front-end development background, so the only thing I can help to improve this project is to throw issues and feedbacks to you. Hope you like it. 😃

I don't have a front-end development background, so the only thing I can help to improve this project is to throw issues and feedbacks to you. Hope you like it.

Sure I like it, reporting bugs and requesting features are definitely contributions! Thanks :)

The current PRs, issues, or trends only display one page of items (30 items I guess), I think we need to support "loading more items by scrolling up" feature, otherwise, the information is incomplete.

Yes, many pages have load more buttons except the Issues and PRs pages, added load more in these two pages is in plan, but since you mentioned, I'll try to do it as soon as possible, as for the trending page I'm afraid we cannot do anything because GitHub only shows 30 trending repositories or so (that's all)

Then you got a lot of stuff to do :) I believe you can manage your time well.

Hi @johnnychen94 , the latest version supports loading more in Issues page and Pulls page, please give it a try, if it doesn't work, feel free to reopen this issue :) thanks


Load policies from file/ConfigMap

The PoC implementation loads an included policy borrowed from kube-no-trouble.
Need to allow users to define their own policies and doing this with a flag to a file (thus a ConfigMap mount) is nice and simple.

I have this implemented on a local branch. To be pushed up soon 🚀


Preparing for Puppet-Community release

@nibalizer any idea why travis is failing?
despite the change to Gemfile to move puppet-blacksmith up, it's not actually happening.


Condition for making sure the user doesn't enter an empty word/sentence

add this :
while not user_input.strip():
print("Please enter a non-empty word or sentence.")
user_input = input("Enter text for ASCII art: ")


Migrations being reused repeatedly despite explicit instructions, coaxing, and bare threats

Describe the bug
After a few hours of progress, a set of policy changes were recommended to be applied to Supabase related to a specific set of fields in a single table.  The new RLS policy causes an infinite recursion, so I got a fix from Claude (don't tell Bolt...).  However, after renaming migrations, removing offending duplicate migrations, and begging, pleading, renaming, trying to run migrations manually, every migration is now stuck at 0059...Every one of them.
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-mrcqgkkf
Validations

[X] Please make your project public or accessible by URL. This will allow anyone trying to help you to easily reproduce the issue and provide assistance.

Steps to reproduce
Same as this: https://github.com/stackblitz/bolt.new/issues/4455 and https://github.com/stackblitz/bolt.new/issues/4727
Expected behavior
I should, at least, be able to rename the file without Bolt renaming it back, deleting it (when pressing "discard"), or ignoring my instructions to USE THIS FILE NAME: XXXX_WORD_WORD.sql
Screen Recording / Screenshot
No response
Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 131
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 155070906,
  "usedJSHeapSize": 113549846,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = surlysam-dev
Chat ID = 97bc8dafa4f1

Additional context
No response

Now it has moved on to 0060. :) But it's a duplicate and it's stuck again.


Current Selection->Add to Things crashes QS

Steps to reproduce the problem:

Open Things.App
Select text in safari browser (or the URL in the Safari address bar)
Bring up QuickSilver by typing CMD-Space
Type 'Current Selection' in the first pane
Type 'Add to Things'

Instead of step 5, if I type 'Large Type', I just hear a beep.

It's been a while, closing :)


Re-implemented storage engine to support record's TTL

Coverage decreased (-30.3%) to 42.598% when pulling fd8d351db75165964afa5f42ee7090b683ddbbe6 on ttl into 46b9e39ad12f04671130c4413721c9711d4bf4c4 on master.


image artifact with weekend classes

Seems like the canvas is drawing something larger than the boilerplate's width

https://github.com/aarctan/schedubuddy-web/commit/afb3cdeadcbb6dbd0ab1ba01a3ddaeec708927bd


Style and grammar tweaks

I was confused by this section:

The largest contig is 4,576,290 bp (for comparison E. coli K12 MG1655 strain genome length is 4,656,144 bp) and the smallest is 4,581,676 (total length) - 4,576,290 (length of the largest) = 5,386 bp.

"Largest" and "smallest" seem to be reversed? and the fact that the difference between them is small is just an accident, right? Maybe just remove it if it's not adding anything.

ping @Delphine-L

@mccalluc Sorry for the confusion, I mean here that the smallest is 5,386 bp, that I get by subtracting the length of the other contig from  the total length of the genome , but we can remove the substraction if it's confusing

Oh, I get it now: I won't add any edits around that section in this PR, so it can be reviewed as-is.
If other folks have thoughts about how to rephrase that, great, or it can just be left in its present state.

@Delphine-L : Sorry about that. See if that section seems right now, or if it needs more work.


optional route interception

In scenarios where a route may optionally require a token if the user is logged in, you can now mark ProtectedResourceScopes definitions as optional.  These requests will attach (after acquiring, if necessary) the required token if a user is authenticated.  If no user is currently authenticated, the request will simply go through as if it is an unprotected endpoint, and not force the user to authenticate.
#3758

@microsoft-github-policy-service agree


Create basic tests for Composite Orders migration task

https://github.com/FOLIO-FSE/folio_migration_tools/tree/202-create-migration-task-for-orders-422-add-basic-tests


Some portability improvements

Hi, I've made some minor tweaks to improve portability across toolchains. I have tested on gcc 14.2 on AArch64 Linux as well as both Apple Clang 15 and gcc 14.2 on macOS (14.6.1), both on Apple M2.

Thanks for this. Please split out the rename feat.s -> feat.S and the edits to feat.s in a separate commit, so it's easier to review.

Github's diff word highlight made it easy. Thanks for this!


Do not fill lookup.hits in HashLookup::reset

Description
Recently, in our benchmarking, we found that filling hits with nullptr is a rather expensive "cost", while not fully understanding its purpose based on our understanding of hashtable.
Some background and analysis:
For every input batch added to hashtable, hashlookup.reset() is called. It serves two purposes:

resize its members to be at least as large as the current input
fill hits with nullptr.

The resizing of members is just an alloc, not particularly expensive. However, filling hits with nullptr turns out to be somewhat costly. Because size of hits is proportional to input size, hence, the larger the avg input batch size, the more time is wasted on null'ing hits for each input.
A profiling sample from local benchmarking shows just how much time is consumed by HashLook.reset, specifically, null'ing hits consumes.

This led us to question the necessity of null'ing hits in HashLookup.reset() because based on our understanding of HashTable and our reading of code, it is redundant by virtue of the fact that we fail to identify a case where not null'ing hits would break any flow.
We further are skeptical about the up-to-dateness of the comment for hits, dated from Initial commit, stating:

"// Hit for each row of input. nullptr if no hit. Points to the corresponding group row."

We propose that we remove below from HashLookup.reset():
std::fill(hits.begin(), hits.end(), nullptr);
Our internal testing do not detect breakage, thus, we are submitting a PR(https://github.com/facebookincubator/velox/pull/6365) for further CI validation.
Estimated saving:
Depends on batchSize since the time it takes to set all of HashLookup.hits to nullptr is positively correlated to the size of HashLookup.hits. However, on larger batch size, 1mil, saving is roughly 5% of HashAggregation::AddInput. **The screenshot of profile used batchSize of 30mil.

cc @mbasmanova @oerling for consideration.

CC: @xiaoxmeng

@shiyu-bytedance This is a nice investigation. Thank you for detailed report.
It is a bit difficult to reason about the fields in HashLookup struct. I wonder if it would be possible to document each field and update comment for methods that take HashLookup& to clarify what is supposed to be filled in before method call and what is being set by the method.
I'm seeing this code in HashProbe.cpp which also resets hits to null. Wondering if similar performance issues exists here.
    auto numInput = input_->size();
    auto& hits = lookup_->hits;
    hits.resize(numInput);
    std::fill(hits.data(), hits.data() + numInput, nullptr);
    if (!lookup_->rows.empty()) {
      table_->joinProbe(*lookup_);
    }

Also, seeing this method which might rely on 'hits' being null.
  /// Returns the first hit for each key in 'lookup'. The keys are in
  /// 'lookup.hits' with a nullptr representing a miss. This is for use in hash
  /// join probe. Use listJoinResults to iterate over the results.
  virtual void joinProbe(HashLookup& lookup) = 0;

@mbasmanova
I verified the below case.
  /// Returns the first hit for each key in 'lookup'. The keys are in
  /// 'lookup.hits' with a nullptr representing a miss. This is for use in hash
  /// join probe. Use listJoinResults to iterate over the results.
  virtual void joinProbe(HashLookup& lookup) = 0;

I don't think it's a problem. The comment (confirmed with code) is saying for each row in hits, joinProbe will fill in a "hit" ptr or a nullptr if it's a miss. Effectively, the null'ing of hits in HashLookup.reset() is wasted, because in this case, joinProbe will "refill" every hits value anyway.


NETOBSERV-290 Preserve settings in NetFlow table

Either wait for https://github.com/netobserv/network-observability-console-plugin/pull/148 or close it (already included here).
Also https://github.com/netobserv/network-observability-console-plugin/pull/131 will be impacted since topology display has been merged into options.
This PR adds missing parameters to local storage and restore them when page is loaded.
{
  "netflow-traffic-query-params": "filters=resource%3DPod.openshift-operator-lifecycle-manager.olm-operator-55d596d44-qhlxn&timeRange=300&limit=100&match=all&reporter=destination&function=sum&type=bytes",
  "netflow-traffic-sort-id": "EndTime",
  "netflow-traffic-sort-direction": "asc",
  "netflow-traffic-columns": [
    "EndTime",
    "SrcK8S_Type",
    "SrcPort"
  ],
  "netflow-traffic-size-size": "m",
  "netflow-traffic-view-id": "topology"
}

URL query parameters are also restored when the page is opened without parameters / forced filters.

a small suggestion, otherwise tested & looks good

a small suggestion, otherwise tested & looks good

Done, thanks !

/lgtm


gRPC context should be propagated to service code

gRPC uses a io.grpc.Context class to make metadata about a call available to implementation code. The context of a call is stored in a ThreadLocal allowing it to be easily accessed within the service method call. Kotlin coroutines do not run on a single, predictable thread, making this storage insufficient. Fortunately, Kotlin provides an easy way to adapt this thread local pattern to a CoroutineContext, which is implemented in this commit.

One aspect I'm not completely sure about on this PR is weather or not the coroutineContext field of the ...ImplBase class should also be passed to launch. The new ContextCoroutineContextElement can be combined with the coroutineContext as follows:
launch (coroutineContext + ContextCoroutineContextElement()) {
}

LGTM!


add global columnNameMapCache and global modelInstanceCache

With pull requests:

Open your pull request against main
Your pull request should have no more than two commits, if not you should squash them.
You should pass all tests by go test -v ./... at the project root path in local.
It should pass all tests in the available continuous integration systems such as GitHub Actions.
You should add/modify tests to cover your proposed code changes.
If your pull request contains a new feature, please document it on the README.

Please enter this sentence in the comments

I have read the CLA Document and I hereby sign the CLA

I have read the CLA Document and I hereby sign the CLA

func BenchmarkExists(b *testing.B) {
b.ReportAllocs()
for i := 0; i < b.N; i++ {
gplus.NewQueryUser
}
}
没有cache
goos: windows
goarch: amd64
pkg: github.com/acmestack/gorm-plus/tests
cpu: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
BenchmarkExists
BenchmarkExists-8         226561              4446 ns/op            2500 B/op           84 allocs/op
有cache
goos: windows
goarch: amd64
pkg: github.com/acmestack/gorm-plus/tests
cpu: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
BenchmarkExists
BenchmarkExists-8       23007810                47.24 ns/op            0 B/op           0 allocs/op

well done！

I'm sorry, already done.

ok


hyprpm: protocol header install fails

Hyprland Version
 System/Version info
Hyprland, built from branch main at commit a66cfe0fbed7fb4dc69383e107c2bf3b1e7cd80a  (CMake: use add_custom_command for generating protocols (6104)).
Date: Thu May 16 18:34:03 2024
Tag: v0.40.0-103-ga66cfe0f, commits: 4709

flags: (if any)

System Information:
System name: Linux
Node name: blkheart
Release: 6.8.9-zen1-2-zen
Version: #1 ZEN SMP PREEMPT_DYNAMIC Tue, 07 May 2024 22:06:02 +0000

GPU information:
0d:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] [1002:73bf] (rev c0) (prog-if 00 [VGA controller])

os-release: NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://gitlab.archlinux.org/groups/archlinux/-/issues"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo

plugins:

Bug or Regression?
Bug
Description
✔ configured Hyprland
[v] installation will run: sed -i -e "s#PREFIX = /usr/local#PREFIX = /home/zakk/.local/share/hyprpm/headersRoot#" /tmp/hyprpm/hyprland-zakk/Makefile && cd /tmp/hyprpm/hyprland-zakk && make installheaders
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╍━━━━━━━━━  4 / 5  Installing sources[v] installer returned: # remove previous headers from hyprpm's dir
rm -fr /home/zakk/.local/share/hyprpm/headersRoot/include/hyprland
mkdir -p /home/zakk/.local/share/hyprpm/headersRoot/include/hyprland
mkdir -p /home/zakk/.local/share/hyprpm/headersRoot/include/hyprland/protocols
mkdir -p /home/zakk/.local/share/hyprpm/headersRoot/include/hyprland/wlr
mkdir -p /home/zakk/.local/share/hyprpm/headersRoot/share/pkgconfig
find src -name '.h' -print0 | cpio --quiet -0dump /home/zakk/.local/share/hyprpm/headersRoot/include/hyprland
cd subprojects/wlroots-hyprland/include/wlr && find . -name '.h' -print0 | cpio --quiet -0dump /home/zakk/.local/share/hyprpm/headersRoot/include/hyprland/wlr && cd ../../../..
cd subprojects/wlroots-hyprland/build/include && find . -name '.h' -print0 | cpio --quiet -0dump /home/zakk/.local/share/hyprpm/headersRoot/include/hyprland/wlr && cd ../../../..
cp ./protocols/.h /home/zakk/.local/share/hyprpm/headersRoot/include/hyprland/protocols
cp: cannot stat './protocols/.h': No such file or directory
make: *** [Makefile:57: installheaders] Error 1
How to reproduce
hyprpm update
Crash reports, logs, images, videos
No response

Works fine without commit a66cfe0fbed7fb4dc69383e107c2bf3b1e7cd80a

FUFFIEEEE @fufexan CAN YOU STOP BREAKING MY PLUGINS?

My bad gang, didn't test outside CI.

I will perform a prostate exam on you if you do that again

Any fix for this? Someone else fixed it by reinstalling hyprwayland-scanner, but that doesn't seem to work for me.

ask @fufexan

Same error here. Can't use any plugin, tried all possible suggestions I saw

Looks like the same error
cp ./protocols/*.h* /home/MyUser/.local/share/hyprpm/headersRoot/include/hyprland/protocols
cp: cannot stat './protocols/*.h*': No such file or directory
make: *** [Makefile:57: installheaders] Error 1

✖ failed to install headers with error code 2

hyprpmbug.txt
Hyprland, built from branch main at commit f8857e6072bd85b95393499688872aaf7f088b5b  (input: find surface pos correctly when mouse drag is active).
Date: Sat May 18 22:20:01 2024
Tag: v0.40.0-113-gf8857e60, commits: 4719

flags: (if any)

Maybe try the newest version of  hyprwayland-scanner-git. On my system installing hyprwayland-scanner from arch/extra didn't work, but replacing it with hyprwayland-scanner-git from the AUR (like mentioned here) fixed it somehow.

Not really  , I already had it from -git , but I tried with --devel just in case but also no

local/hyprwayland-scanner-git 0.3.8.r1.g3afed436-1
    A Hyprland implementation of wayland-scanner, in and for C++

Yeah I'm not even sure if the commit is at fault. Running diff on the generated include/hyprland/protocols dirs yields an empty diff, both after and before that commit.

I just retested with hyprwayland-scanner-git updated to latest
a66cfe0 fails
7a73f0c works

@fufexan In a66cfe0, you changed the hyprwayland-scanner commands from being executed at configure time (because of the use of execute_process), to being executed at build time (add_custom_command).
From what I can tell, hyprpm will configure Hyprland, but not build it. So the protocols/*.h* files will never be generated.

Makes sense. @cnt0 do you mind if I revert the commit, or do you have a better approach for this?

They're generated files, so no.

can we actually keep both execute_process and add_custom_command? This way these files will be generated during the configuration, and if they'll be deleted then rebuild won't fail (which was my motivation to add add_custom_command)

In my opinion the makefile should be changed so that installheaders is an actual cmake target (using add_custom_target) that depends on the OUTPUTS in the add_custom_commands. This way, they will only be generated when they are needed and not yet present.

But for now I think simply reverting is the best option until a better solution is implemented.


Problem with make in Fedora on RPI 3B

Hi!
I'm doing work where i see if the OS is affecting a clusters performance. Doing so i need to tryout diffrent OS with the same setup. I had gotten everything to work smoothfully on raspbian with a RPI 3B (not the plus model) where i used this (OpenBLAS). Now i'm trying to do the same on Fedora, but i get errors when i try to use make. I've attached the log and i hope everything is correct, otherwise i will upload it again. Hope i haven't forgotten to submit something important.
My RPI model have 4× ARM Cortex-A53, 1.2GHz CPU (it's a homogenous cluster so all RPI:s is of the same model)
logg.txt

The log appears to be incomplete (or you accidentally ran "make" in the interface subdirectory rather than the toplevel), but can you please retry with the current 0.3.9 version rather than the 0.2.20 from almost three years ago ?

thx, that solved it. I missed that there was never version available, sorry for any inconvenience


Integration tests bats code example issue

The location of the teardown function in the example code in test/integration/README.md is incorrect.

Am following the guildlines in CONTRIBUTING.md. It feels a little contrived to create a separate issue like this, is this still the recommended way? To contribute?


Viomi vacuum V8 Serial number timeout

[2021/03/23, 17:51:21] [homebridge-xiaomi-roborock-vacuum] This plugin slows down Homebridge. The read handler for the characteristic 'Serial Number' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.
[2021/03/23, 17:51:22] [Xiaomi ] ERR getSerialNumber | Failed getting the serial number. Error: Call to device timed out
at DeviceInfo._retryOnTimeout (C:\Users\David\AppData\Roaming\npm\node_modules\homebridge-xiaomi-roborock-vacuum\miio\lib\device_info.js:295:29)
at DeviceInfo.call (C:\Users\David\AppData\Roaming\npm\node_modules\homebridge-xiaomi-roborock-vacuum\miio\lib\device_info.js:227:12)
at module.exports.getSerialNumber (C:\Users\David\AppData\Roaming\npm\node_modules\homebridge-xiaomi-roborock-vacuum\miio\lib\devices\viomivacuum.js:141:20)
at XiaomiRoborockVacuum.getSerialNumber (C:\Users\David\AppData\Roaming\npm\node_modules\homebridge-xiaomi-roborock-vacuum\index.js:827:28)
at module.exports (C:\Users\David\AppData\Roaming\npm\node_modules\homebridge-xiaomi-roborock-vacuum\lib\callbackify.js:5:20) {
code: 'timeout'
}

Can confirm, having the exact same issue with my viomi.vacuum.v8 as well. It connects correctly and can read most data, but some values generate warnings, then a warning is issued "This plugin is slowing down HomeBridge", and eventually it starts throwing the error:
[3/27/2021, 7:54:34 PM] [Mi Robot Vacuum] STA getDevice | Connected to: <IP_ADDRESS>
[3/27/2021, 7:54:34 PM] [Mi Robot Vacuum] STA getDevice | Model: viomi.vacuum.v8
[3/27/2021, 7:54:34 PM] [Mi Robot Vacuum] STA getDevice | State: charging
[3/27/2021, 7:54:34 PM] [Mi Robot Vacuum] STA getDevice | FanSpeed: 3
[3/27/2021, 7:54:34 PM] [Mi Robot Vacuum] STA getDevice | BatteryLevel: 100
[3/27/2021, 7:54:44 PM] [Mi Robot Vacuum] ERR getRoomMap | Failed getting the Room Map. Error: Call to device timed out
    at DeviceInfo._retryOnTimeout (/homebridge/node_modules/homebridge-xiaomi-roborock-vacuum/miio/lib/device_info.js:295:29)
    at DeviceInfo.call (/homebridge/node_modules/homebridge-xiaomi-roborock-vacuum/miio/lib/device_info.js:227:12)
    at XiaomiRoborockVacuum.getRoomMap (/homebridge/node_modules/homebridge-xiaomi-roborock-vacuum/index.js:1069:19)
    at XiaomiRoborockVacuum.initializeDevice (/homebridge/node_modules/homebridge-xiaomi-roborock-vacuum/index.js:670:11)
    at XiaomiRoborockVacuum.connect (/homebridge/node_modules/homebridge-xiaomi-roborock-vacuum/index.js:755:7) {
  code: 'timeout'
}
[3/27/2021, 7:54:44 PM] [Mi Robot Vacuum] ERR connect | miio.device, next try in 2 minutes | Error: Call to device timed out
[3/27/2021, 7:54:48 PM] [Mi Robot Vacuum] INF getCleaning | viomi.vacuum.v8 | Cleaning is false
[3/27/2021, 7:54:48 PM] [Mi Robot Vacuum] INF getCareSensors | viomi.vacuum.v8 | Sensors dirtytime is undefined seconds / NaN%.
[3/27/2021, 7:54:48 PM] [Mi Robot Vacuum] INF getCareFilter | viomi.vacuum.v8 | Filter worktime is undefined seconds / NaN%.
[3/27/2021, 7:54:48 PM] [Mi Robot Vacuum] INF getCareSideBrush | viomi.vacuum.v8 | Sidebrush worktime is undefined seconds / NaN%.
[3/27/2021, 7:54:48 PM] [Mi Robot Vacuum] INF getCareSensors | viomi.vacuum.v8 | Sensors dirtytime is undefined seconds / NaN%.
[3/27/2021, 7:54:48 PM] [Mi Robot Vacuum] INF getCareFilter | viomi.vacuum.v8 | Filter worktime is undefined seconds / NaN%.
[3/27/2021, 7:54:48 PM] [Mi Robot Vacuum] INF getCareSideBrush | viomi.vacuum.v8 | Sidebrush worktime is undefined seconds / NaN%.
[3/27/2021, 7:54:48 PM] [Mi Robot Vacuum] INF getCharging | viomi.vacuum.v8 | Charging is true (Status is charging)
[3/27/2021, 7:54:48 PM] [Mi Robot Vacuum] INF getDocked | viomi.vacuum.v8 | Robot Docked is true (Status is charging)
[3/27/2021, 7:54:48 PM] [Mi Robot Vacuum] INF getCareSensors | viomi.vacuum.v8 | Sensors dirtytime is undefined seconds / NaN%.
[3/27/2021, 7:54:48 PM] [Mi Robot Vacuum] INF getCareSensors | viomi.vacuum.v8 | Sensors dirtytime is undefined seconds / NaN%.
[3/27/2021, 7:54:48 PM] [Mi Robot Vacuum] INF getCareFilter | viomi.vacuum.v8 | Filter worktime is undefined seconds / NaN%.
[3/27/2021, 7:54:48 PM] [Mi Robot Vacuum] INF getCareFilter | viomi.vacuum.v8 | Filter worktime is undefined seconds / NaN%.
[3/27/2021, 7:54:48 PM] [Mi Robot Vacuum] INF getCareSideBrush | viomi.vacuum.v8 | Sidebrush worktime is undefined seconds / NaN%.
[3/27/2021, 7:54:48 PM] [Mi Robot Vacuum] INF getCareSideBrush | viomi.vacuum.v8 | Sidebrush worktime is undefined seconds / NaN%.
[3/27/2021, 7:54:48 PM] [Mi Robot Vacuum] INF getCareMainBrush | viomi.vacuum.v8 | Mainbrush worktime is undefined seconds / NaN%.
[3/27/2021, 7:54:48 PM] [Mi Robot Vacuum] INF getCareMainBrush | viomi.vacuum.v8 | Mainbrush worktime is undefined seconds / NaN%.
[3/27/2021, 7:54:48 PM] [Mi Robot Vacuum] INF getBatteryLow | viomi.vacuum.v8 | Batterylevel is 100%
[3/27/2021, 7:54:48 PM] [Mi Robot Vacuum] INF getBattery | viomi.vacuum.v8 | Batterylevel is 100%
[3/27/2021, 7:54:48 PM] [Mi Robot Vacuum] INF getSpeed | viomi.vacuum.v8 | Fanspeed is 3 over miIO. Converting to HomeKit
[3/27/2021, 7:54:48 PM] [Mi Robot Vacuum] INF getSpeed | viomi.vacuum.v8 | Fanspeed is 3 over miIO "Turbo" > HomeKit speed 100%
[3/27/2021, 7:54:48 PM] [homebridge-xiaomi-roborock-vacuum] This plugin generated a warning from the characteristic 'Filter Life Level': characteristic value expected valid finite number and received "NaN" (number). See https://git.io/JtMGR for more info.
[3/27/2021, 7:54:48 PM] [Mi Robot Vacuum] INF getFirmware | viomi.vacuum.v8 | Firmwareversion is 3.5.3_0017
[3/27/2021, 7:54:51 PM] [homebridge-xiaomi-roborock-vacuum] This plugin slows down Homebridge. The read handler for the characteristic 'Serial Number' was slow to respond! See https://git.io/JtMGR for more info.
[3/27/2021, 7:54:57 PM] [homebridge-xiaomi-roborock-vacuum] This plugin slows down Homebridge. The read handler for the characteristic 'Serial Number' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.
[3/27/2021, 7:55:08 PM] [Mi Robot Vacuum] ERR getSerialNumber | Failed getting the serial number. Error: Call to device timed out
    at DeviceInfo._retryOnTimeout (/homebridge/node_modules/homebridge-xiaomi-roborock-vacuum/miio/lib/device_info.js:295:29)
    at DeviceInfo.call (/homebridge/node_modules/homebridge-xiaomi-roborock-vacuum/miio/lib/device_info.js:227:12)
    at module.exports.getSerialNumber (/homebridge/node_modules/homebridge-xiaomi-roborock-vacuum/miio/lib/devices/viomivacuum.js:141:20)
    at XiaomiRoborockVacuum.getSerialNumber (/homebridge/node_modules/homebridge-xiaomi-roborock-vacuum/index.js:827:28)
    at module.exports (/homebridge/node_modules/homebridge-xiaomi-roborock-vacuum/lib/callbackify.js:5:20) {
  code: 'timeout'
}

Some of the INF readouts and warnings also repeat randomly in the log multiple times.
I've had to disable the plugin for now. Hoping this gets fixed soon, this is the first time integrating the vacuum into any sort of automation actually showed signs of working :)

I am facing the same issue unfortunately.
https://github.com/homebridge-xiaomi-roborock-vacuum/homebridge-xiaomi-roborock-vacuum/discussions/449


goblender not available

Is goblender no more supported by you?
https://github.com/tsawler/goblender is giving a 404

It is supported, but it is a private package. I use it with paying clients, and do not share it.
—
Trevor Sawler, Ph.D.
506-262-4335
@.***
On Feb 22, 2023 at 1:34 PM -0400, jagmonan @.***>, wrote:

Is goblender no more supported by you?
https://github.com/tsawler/goblender is giving a 404
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


Why / Balance

to resolve #32271
Technical details

add new list of jobs in PickRandomPersonComponent
then for pick check if any of humans has the job in list
remove human from list
Media

Requirements

[X] I have read and am following the Pull Request and Changelog Guidelines.
[X] I have added media to this PR or it does not require an ingame showcase.

Breaking changes

Changelog

:cl:

tweak: Medical intern, technical assistant and research assistant now can't be traitor kill objectives.

I always skip the objectives if its an intern as well. Really good idea!

Service worker needs to be added if that pr to make them an intern job ever gets merged...

intern should probably be clarified into medical intern in the CL, also, why does this not include cadets? Because they’re sec?

Because they’re sec?

you have to play 15 hours overall to play as cadet
also for me sounds weird that syndicate wouldn't want to kill security guys

Add heads to this as well, heads should always fall under kill (not maroon) objective

Add heads to this as well, heads should always fall under kill (not maroon) objective

I don't see why?

Add heads to this as well, heads should always fall under kill (not maroon) objective

I don't see why?

Because a couple of months ago antag difficulty has been correctly capped, but still one traitor can get "kill the RD and escape unrestrained" and the other can get something absurd like "kill or maroon the captain, kill or maroon the hos and escape unrestrained", because maroon objectives are considered easier (a maroon objective, say, a bartender, can die on their own and nobody would care, and in general killing a bartender is of course easier then a captain)

I don't really see it making much of a difference? If the person teaching the intern is the target, then the same issue persists?  The game overall just isn't really that beginner friendly and par for the course honestly.
Like you can make all intern roles non-targeted, but the person teaching them may be targeted, so teaching halts once again.

At that point why not just make most, if not all service roles non-target since they're also usually where new players are recommended?

this is a false dichotomy, as even if new players are recommended to do service, that does not mean all service players are new players just because thats recommended.

At that point why not just make most, if not all service roles non-target since they're also usually where new players are recommended?

this is a false dichotomy, as even if new players are recommended to do service, that does not mean all service players are new players just because thats recommended.

and not all interns are new either? It's way more likely a new player is gonna be service vs a department intern. Like it's globally recommended people start janitor for their first few times playing I thought?

Hey, we had a maintainer vote and the result was to close this PR for the following reasons:

Being an intern does not equal being a new player. You could have lots of playtime in other departments or on other servers.
Being killed by antagonists is part of the game, the story it is telling and not always something negative. It can even be a good thing for newer player to learn that early.
There are other antagonists where such a safety feature does not exist (nukies, revs, eventually Wizard)

Thank you for your contribution.

weh, okay, it was good experience tho


Revert the default min SDK version back to 16

As this was the case prior to bf7da273dd2715b9f30242edc7727102e3559902

@mars-lan Why is this necessary? Today, minSdk that could be published to playstore is 26 i guess. Isn't it?

Do you think minSdk 21 will be ok?

minimum required targetSDK is 26 not minSDK

@hariks789 yeah. I realized later. Thanks. Merged this PR already.

@dooboolab thanks 👍


[FLINK-14038][docs] Extend Application Profiling documentation

What is the purpose of the change
This commit adds explanations on how to analyze/debug out of memory problems and
how to analyze GC behaviour.
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

Thanks for the review @TisonKun. I've addressed your comments. Merging this PR now.


problem with nodemon: [nodemon] clean exit - waiting for changes before restart

for some reason whewn i run the code
npm install
npm start -- --port [PORT]
with the port in it, it says: [nodemon] clean exit - waiting for changes before restart

then it cannot reach the server

change [PORT] to your port in game


Can't display VirtualBox guest (BIO_read returned a system error 0: Error 0)

Describe the bug
I try to connect from OpenIndiana 2019.04 desktop with FreeRDP e873e4f0042dd157f68ae99adb4dc9dcd167ca29 (the latest as of today) to a VirtualBox 6.0.8 guest running on a different OpenIndiana 2019.04 host, the guest is OpenIndiana 2019.04 as well:
xfreerdp /v:<IP_ADDRESS>:5912

On the VirtualBox host I have the Oracle extension pack 6.0.8 with VRDP installed and VRDP enabled in the guest. (I am able to connect to the guest via rdesktop 1.8.3 but not the latest rdesktop HEAD).
But the connection fails in about a second. For a second I can see the guest as expected. The error seems to be:
[18:31:46:498] [28099:00000002] [ERROR][com.freerdp.core.transport] - BIO_read returned a system error 0: Error 0
[18:31:46:498] [28099:00000002] [ERROR][com.freerdp.core] - freerdp_check_fds() failed - 0
[18:31:46:498] [28099:00000002] [INFO][com.freerdp.client.common] - Network disconnect!
[18:31:46:498] [28099:00000002] [ERROR][com.freerdp.client.x11] - Failed to check FreeRDP file descriptor

Also tried version 2.0.0 RC4 but it manifests the same.
Connection from Fedora 30 (5e672d474e0d8fb5560f1068d4b83328fd8e41ca / 20190918) to the guest worked fine. Tried this revision as well but no luck.
Application details

Version of FreeRDP: e873e4f0042dd157f68ae99adb4dc9dcd167ca29 & 2.0.0 RC4
Command line used: xfreerdp /v:<IP_ADDRESS>:5912
output of /buildconfig:

This is FreeRDP version 2.0.0-dev5 (5bc8da79e)
Build configuration: BUILD_TESTING=OFF BUILTIN_CHANNELS=OFF HAVE_AIO_H=1 HAVE_EXECINFO_H=1 HAVE_FCNTL_H=1 HAVE_INTTYPES_H=1 HAVE_MATH_C99_LONG_DOUBLE=1 HAVE_POLL_H=1 HAVE_PTHREAD_MUTEX_TIMEDLOCK=ON HAVE_PTHREAD_MUTEX_TIMEDLOCK_LIBS= HAVE_PTHREAD_MUTEX_TIMEDLOCK_SYMBOL=1 HAVE_SYSLOG_H=1 HAVE_SYS_EVENTFD_H=1 HAVE_SYS_FILIO_H=1 HAVE_SYS_MODEM_H= HAVE_SYS_SELECT_H=1 HAVE_SYS_SOCKIO_H=1 HAVE_SYS_STRTIO_H= HAVE_SYS_TIMERFD_H=1 HAVE_TM_GMTOFF= HAVE_UNISTD_H=1 HAVE_XI_TOUCH_CLASS=1 WITH_ALSA=OFF WITH_CAIRO=ON WITH_CCACHE=ON WITH_CHANNELS=ON WITH_CLANG_FORMAT=ON WITH_CLIENT=ON WITH_CLIENT_AVAILABLE=1 WITH_CLIENT_CHANNELS=ON WITH_CLIENT_CHANNELS_AVAILABLE=1 WITH_CLIENT_COMMON=ON WITH_CLIENT_INTERFACE=OFF WITH_CUPS=ON WITH_DEBUG_ALL=OFF WITH_DEBUG_CAPABILITIES=OFF WITH_DEBUG_CERTIFICATE=OFF WITH_DEBUG_CHANNELS=OFF WITH_DEBUG_CLIPRDR=OFF WITH_DEBUG_DVC=OFF WITH_DEBUG_KBD=OFF WITH_DEBUG_LICENSE=OFF WITH_DEBUG_MUTEX=OFF WITH_DEBUG_NEGO=OFF WITH_DEBUG_NLA=OFF WITH_DEBUG_NTLM=OFF WITH_DEBUG_RAIL=OFF WITH_DEBUG_RDP=OFF WITH_DEBUG_RDPDR=OFF WITH_DEBUG_RDPEI=OFF WITH_DEBUG_RDPGFX=OFF WITH_DEBUG_REDIR=OFF WITH_DEBUG_RFX=OFF WITH_DEBUG_RINGBUFFER=OFF WITH_DEBUG_SCARD=OFF WITH_DEBUG_SND=OFF WITH_DEBUG_SVC=OFF WITH_DEBUG_SYMBOLS=OFF WITH_DEBUG_THREADS=OFF WITH_DEBUG_TIMEZONE=OFF WITH_DEBUG_TRANSPORT=OFF WITH_DEBUG_TSG=OFF WITH_DEBUG_TSMF=OFF WITH_DEBUG_WND=OFF WITH_DEBUG_X11=OFF WITH_DEBUG_X11_CLIPRDR=OFF WITH_DEBUG_X11_LOCAL_MOVESIZE=OFF WITH_DEBUG_XV=OFF WITH_DIRECTFB=OFF WITH_DSP_EXPERIMENTAL=OFF WITH_EVENTFD_READ_WRITE=1 WITH_FAAC=OFF WITH_FAAD2=OFF WITH_FFMPEG=OFF WITH_GFX_H264=OFF WITH_GPROF=OFF WITH_GSM=OFF WITH_GSSAPI=OFF WITH_GSTREAMER_0_10=OFF WITH_GSTREAMER_1_0=ON WITH_ICU=ON WITH_IPP=OFF WITH_JPEG=ON WITH_KRB5=ON WITH_LAME=ON WITH_LIBRARY_VERSIONING=ON WITH_LIBRARY_VERSIONING=ON WITH_LIBSYSTEMD=OFF WITH_MACAUDIO=OFF WITH_MACAUDIO=OFF WITH_MACAUDIO_AVAILABLE=0 WITH_MANPAGES=ON WITH_MBEDTLS=OFF WITH_OPENH264=OFF WITH_OPENSLES=OFF WITH_OPENSSL=ON WITH_OSS=ON WITH_PAM=ON WITH_PCSC=OFF WITH_PROFILER=OFF WITH_PULSE=ON WITH_SAMPLE=OFF WITH_SANITIZE_ADDRESS=OFF WITH_SANITIZE_ADDRESS_AVAILABLE=1 WITH_SANITIZE_MEMORY=OFF WITH_SANITIZE_MEMORY_AVAILABLE=1 WITH_SANITIZE_THREAD=OFF WITH_SANITIZE_THREAD_AVAILABLE=1 WITH_SERVER=ON WITH_SERVER_CHANNELS=ON WITH_SERVER_INTERFACE=ON WITH_SMARTCARD_INSPECT=OFF WITH_SOXR=OFF WITH_SSE2=ON WITH_SWSCALE=OFF WITH_THIRD_PARTY=OFF WITH_VALGRIND_MEMCHECK=OFF WITH_VALGRIND_MEMCHECK_AVAILABLE=1 WITH_WAYLAND=OFF WITH_X11=ON WITH_X264=OFF WITH_XCURSOR=ON WITH_XDAMAGE=ON WITH_XEXT=ON WITH_XFIXES=ON WITH_XI=ON WITH_XINERAMA=ON WITH_XKBFILE=ON WITH_XRANDR=ON WITH_XRENDER=ON WITH_XSHM=ON WITH_XTEST=ON WITH_XV=ON WITH_ZLIB=ON
Build type:          Release
CFLAGS:              -m64 -O3 -Wall -Wno-unused-result -Wno-unused-but-set-variable -Wno-deprecated-declarations -fvisibility=hidden -Wimplicit-function-declaration -Wredundant-decls -DWINPR_DLL
Compiler:            GNU, 6.5.0
Target architecture:

OS version connecting to: OpenIndiana 2019.04 with VirtualBox 6.0.8 (host & guest)
If available the log output from a run with /log-level:trace :

xfreerdp.debug.txt
xfreerdp.trace.txt
xfreerdp.truss.txt

It works fine with -pthread like this (GCC used here):
--- FreeRDP-e873e4f0042dd157f68ae99adb4dc9dcd167ca29/CMakeLists.txt	2019-07-29 10:07:13.000000000 +0000
+++ FreeRDP-e873e4f0042dd157f68ae99adb4dc9dcd167ca29/CMakeLists.txt.new	2019-07-29 19:21:24.823354515 +0000
@@ -263,6 +263,7 @@ if(CMAKE_COMPILER_IS_GNUCC)

 	set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -Wall")

+	set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -pthread")
 	CHECK_C_COMPILER_FLAG (-Wno-unused-result Wno-unused-result)
 	if(Wno-unused-result)
 		set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -Wno-unused-result")

@Mno-hime the diff is strange, might that be a bug in your system?
We link pthread privately to WinPR and xfreerdp which are the places we use it.
What does your CMakeLists.txt say about pthread detection?

@Mno-hime and more importantely, is openssl properly linked against pthread in your system?

It's not related to pthread library, it's about -D_REENTRANT flag set by GCC when '-pthread' is passed to it. This clearly fixes something. Would be good to find out what exactly :)

Just adding another voice here to let folks know that those of us using VirtualBox still rely upon these things, and it seems even the latest releases are so affected. I managed to find a older build of the Windows client from July that works, but the latest ones definitely do not. I'm OK sticking with an older build for now, but in some cases (like Linux repos) this may not be possible. May have to try and find older sources to  build from if possible.
I should also point out that rdesktop project has seen connection issues past 1.8.4, as they work to freshen things up for new RDP features. There may be common thread. That said, if anyone knows of a way to adjust the VBox VRDE/VRDP configuration to better work with more recent freerdp builds, I'm definitely game for that.


Sideways movement in air should move by 2 if player is in mid-air

Closed via https://github.com/Skorezore/Gaem/commit/44847212d85a07ae1cef11a3c597cceed26ea0d8


Create an ssh key by filling nothing, an inappropriate error message shows

Steps to reproduce:

On the SSH key create page
Not filling anything on the page then click the create button

Result:
An error message shows and says: Name cannnot longer than 63 characters. Actually nothing is populated

addressed in https://github.com/rancher/harvester-ui/pull/99

Validated


Failed to compile

I clone the repository, launch a  npm install command and a npm start  and I have this error message on http://localhost:3000/react-ts-rxdb-bootstrap-table
./src/components/Dashboard.tsx
  Line 0:  Parsing error: Cannot read property 'map' of undefined

Hey @JulienVerkest ,
can you try git reset --hard f6da37ec7f02a45b55a527819789a4a96180bb34 in your local repo, and reinstall  with yarn/npm and try running again?

@vazra It works fine! Thanks you.


s3 batch delete fails when more than 1K objects are deleted

The batch delete api supports deleting a maximum of 1,000 objects per request: https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObjects.html
Currently, ocfl-java does not take this into account, and will happily create a single request to delete any number of object.s

resolved by https://github.com/OCFL/ocfl-java/pull/109


@calcom/lib not found

yarn install failes:
#11 1.256 error An unexpected error occurred: "https://registry.yarnpkg.com/@calcom%2flib: Not found".

This appears to be a duplicate of https://github.com/calcom/docker/issues/85.

Same issue here, have you find a solution plz !

The problem here seems that the docker setup tries to install the package @calcom/lib as it was a regular published in npm/yarn package, which is not.
@calcom/lib lives in calcom/packages/lib now. And it should be picked up during install of the monorepo/turborepo, hope this can find you debug the problem.

Please follow the instructions available in this PR to resolve this.
https://github.com/calcom/docker/pull/86#issuecomment-1047179700
I will summarize the steps here for your convenience.
git clone --recursive https://github.com/calendso/docker.git calendso-docker
cd calendso-docker/
git remote add searsaw https://github.com/searsaw/docker.git
git fetch --all
git checkout searsaw/fix-workspaces-build-issues
git submodule update --init --recursive
mv .env.example .env
docker-compose up --build -d

You will have to visit localhost:5555 afterward to set up the user(s). Reason? See below.

The password has to be generated using bcrypt. Which you can generate for testing purposes using the below app.
https://bcrypt-generator.com/

Please follow the instructions available in this PR to resolve this.
#86 (comment)
I will summarize the steps here for your convenience.
git clone --recursive https://github.com/calendso/docker.git calendso-docker
cd calendso-docker/
git remote add searsaw https://github.com/searsaw/docker.git
git fetch --all
git checkout searsaw/fix-workspaces-build-issues
git submodule update --init --recursive
mv .env.example .env
docker-compose up --build -d

You will have to visit localhost:5555 afterward to set up the user(s). Reason? See below.

The password has to be generated using bcrypt. Which you can generate for testing purposes using the below app.
https://bcrypt-generator.com/

Completly Agree with this solution. I had the same problem but got fixed by  #86 Comment

Submodule update is knocked out, and may have created some other issues now that we aren't one month behind anymore

resolves with latest


std::array error Seeeduino Xiao Arduino IDE

Compiling code with std::array I get the following error:
error: 'array' in namespace 'std' does not name a template type
Please adivise as to how to get around this error. Thanks in advance!

Please use the latest version downloaded directly from github, which does not use std::array.

Gotchya - thanks!MarshSent from my iPhoneOn Jan 19, 2024, at 12:50, Brian Taylor @.***> wrote:
Please use the latest version downloaded directly from github, which does not use std::array.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>


Write blogpost on costs of making a cluster SCS compliant

See Adaption Cost

The blogpost is underway now, @martinmo and me already wrote most of it.
We set the date for this to the 13-05-2024, hopefully we can get an approval for the post by this time.


docs: Mark Git repo as safe in docs-builder, for GitHub workflow too

In the docs-builder image, we marked /src as a safe GitHub repository for running Git command in it from a non-root user. This works well when building the documentation locally, but this is not enough to make the GitHub workflow run Git commands in the directory where it mounts the Cilium repository ("/github/workspace").
When trying to update to a recent docs-builder image, and because the spelling extensions needs to run some Git commands, this has led to spell checks failing with an error, blocking the build. Let's mark /github/workspace as a safe Git repository, too.
Ideally, we would declare the repository as safe when launching the container, but given that its owner is root but we're running with a different user (to work around some other issue), I don't see an easy way to do that.
@joestringer: We would need to tag and push a new docs-builder image with this change, so we can use it in the CI workflow (the last one I had you build cannot be used -- apologies!)

:+1: merged and I triggered a fresh build for docker.io/cilium/docs-builder:2022-08-23. If you're logged in I think you should be able to access this page for the details, but otherwise it should likely be available by the time you're online tomorrow: https://hub.docker.com/repository/docker/cilium/docs-builder/tags?page=1&ordering=last_updated


Final Docs Review

This PR will be the final docs check for consistency

Grafana App Dashboard
Hero Scenario Docs
Overall Docs Review

LGTM. With all the file changes let's wait to merge until we get a couple more reviews


Add cell types from transcriptomic of adult human brain

https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>1898v1.full.pdf
We need to add the superclasses
Some already are in CL
Need to read to ensure that they can be added in CL rather than PCL too.

Each was
manually annotated based on the literature and their
regional composition (Table S2) with one exception, a
supercluster that contained neurons from most brain
regions. In the tradition of naming neurons for their
shapes, we named them splatter neurons based on their
appearance on the two-dimensional embedding. Each
supercluster was separately reanalyzed, resulting in a final
set of 461 clusters. A dendrogram of these clusters mirrored
previous work in the mouse: neurons split separately from
non-neuronal cells and into two clades (Fig. 1C) (1). One
clade contained telencephalic excitatory neurons that
express glutamatergic genes like SLC17A6 and SLC17A7.
The other contained telencephalic inhibitory neurons
that express GABAergic genes like SLC32A1, as well as
all excitatory and inhibitory diencephalic, midbrain,
and hindbrain neurons. We additionally analyzed each
cluster separately to produce a more detailed but less
robust clustering that contained 3313 clusters, which we
subsequently refer to as “subclusters” (Fig. 1C).

[ ] Amygdala excitatory
[ ] Astrocyte
[ ] Bergmann glia
[ ] CGE interneuron
[ ] Cerebellar inhibitory
[ ] Choroid plexus
[ ] Committed oligodendrocyte precursor
[ ] Deep-layer corticothalamic and 6b
[ ] Deep-layer intratelencephalic
[ ] Deep-layer near-projecting
[ ] Eccentric medium spiny neuron
[ ] Ependymal
[ ] Fibroblast
[ ] Hippocampal CA1-3
[ ] Hippocampal CA4
[ ] Hippocampal dentate gyrus
[ ] LAMP5-LHX6 and Chandelier
[ ] Lower rhombic lip
[ ] MGE interneuron
[ ] Mammillary body
[ ] Medium spiny neuron
[ ] Microglia
[ ] Midbrain-derived inhibitory
[ ] Miscellaneous
[ ] Oligodendrocyte
[ ] Oligodendrocyte precursor
[ ] Splatter
[ ] Supercluster
[ ] Thalamic excitatory
[ ] Upper rhombic lip
[ ] Upper-layer intratelencephalic
[ ] Vascular

@dosumis - question: do we REALLY need http://purl.obolibrary.org/obo/CL_4023070 ('caudal ganglionic eminence derived GABAergic cortical interneuron') to be cortical specific? Currently there's a need to add CGE interneuron, and if I do, it CGE cortical interneuron will be the only child (unless I also created like hippocampus, amygdala etc. CGE interneuron. I don't see a huge use case for the proliferation of these terms as we tend to also annotate location of cell types (eg annotating cell type as "CGE interneuron" and location as "hippocampus"). Should we make a change for CGE and MGE to be wider brain applicable? If so should it be an obsolete and remake term (given we are changing the definition of the term)? Thanks

Issue:
Choroid plexus and Ependymal are separate clusters, yet there are Ependymal cells in the Choroid plexus - not sure how these clusters are actually separated?

I'm in favour of making a general MGE interneuron term but also keeping subclasses by major region.  It's some proliferation of terms, but I think potentially v.useful.

Is the choroid plexus cluster close to the ependymal cluster on the UMAP?  Presumably specialised ependymal cells that cluster separately.  Might be odd to have term for non-CP ependymal cells though, so any annotation of the ependymal cluster will have to be with a broader term.

Is the choroid plexus cluster close to the ependymal cluster on the UMAP?

They are a fully separate island, I'm guessing that Ependymal cluster doesn't include Ependymal in choroid plexus, light not details in writing about it.

Similar issue with 'Eccentric medium spiny neuron' and 'medium spiny neuron' which are separate clusters, but I assume 'medium spiny neurons' refers to “direct” (dSPN) and “indirect” (iSPN) spiny neurons only.


Add tests to gtest-parallel.

@pbos @kwiberg
Please take a look.
Don't know if this is the best way to introduce tests. I'd like to have unit tests, not only testing the whole script.

This diff is nasty looking, is there any way for it to detect renames during uploading or similar so that it can easily be reviewed?

Maybe I can temporarily copy gtest_parallel.py into gtest-parallel?
I don't know how to tell git that we renamed the file, since the original one still exists.

Or maybe rename gtest-parallel to something else in the meantime?

you can do everything except the rename during review, just call gtest-parallel gtest-herkaderk meanwhile?

Ok, please take a look now :)

I'd agree with that split, it shouldn't be too tricky and makes sense.

I did that, but for some reason I can't get it to work.
It gets stuck at the task = subprocess.Popen(self.test_command, stdout=log, stderr=log) line.

I had to add a main() function, for some reason.
Other than moving all the top level code into main, and declaring options, times, logger, task_manager and timeout as global, there shouldn't be more changes.
On the other hand, how important is to keep gtest-parallel as opposed to renaming it to gtest_parallel.py?

As one of our users, I'd like us to keep the source-code agnostic gtest-parallel alias. :)

Well, it's very cheap to keep the executable "gtest-parallel" around, so fine by me.

Ok :)
PTAL

GitHub is terrible at these diffs, use this one:
https://pastebin.mozilla.org/9021221

PTAL :)

lgtm, @kwiberg can you take a look as well? Do you think the change getting rid of global variables was worth it? I mostly thought that they'd be set inside main() and not once when loading the file.

Please update the pull request name/title as well. :)

As far as I'm concerned, this can be merged as soon as gtest-parallel2 is re-renamed.

Re-renamed :)


deploy.sh can't be used for topic branches

Want to be able to deploy and test topic branches. deploy.sh clobbers these with what's in master; have to comment out these lines or not use the script.
# Update the git repository
git fetch
git reset --hard origin/master
git clean -f

Related to large issue #185, creating a staging environment

Hmm... I think we can just do a git reset --hard origin/topic-branch for each one we want to push?
Though, I personally think we should only do origin/staging.
If we want to view topic branches live, we should set up heroku integration and spin up a PR app.

obsoleted via pr apps.


remote access terribly slow

hi all, first thanks for this free tool, really goot soft. however, dont know why, but my remote access is randomly slow, to connect on an Azure VM (, no firewall, 8CPU / 16GB RAM...), using internet fiber connection. and for unknown reasons sometimes the connection is sooo slow it makes impossible to use remote desktop.
Could you please tell me what kind of optmizations / settings I could change to check if it would be better ? I heard about websocket improves the connection... what does it means exactly ? anyway if you could give me some advices... thanks a lot

Did you enabled the websocket protocol on IIS? (https://www.iis.net/configreference/system.webserver/websocket)

lool omg yes it definitely better, ^^ perfect thanks


Windows support

This PR aims to add support for Windows.
But currently, it seems that we have some issues when building for Windows.
CMake Error at cmake_tflite_beam/eigen/CMakeLists.txt:138 (message):
  Can't link to the standard math library.  Please report to the Eigen
  developers, telling them about your platform.

-- Configuring incomplete, errors occurred!
NMAKE : fatal error U1077: 'if not exist "D:\a\tflite_beam\tflite_beam/priv/tflite_beam.dll" (  python3 "patches/apply_patch.py" "D:\a\tflite_beam\tflite_beam\3rd_party\tensorflow\tensorflow-2.16.1" "2.16.1" &&  cd "D:\a\tflite_beam\tflite_beam\cmake_tflite_beam" &&  cmake -G "NMake Makefiles"  -D C_SRC="D:\a\tflite_beam\tflite_beam\c_src"  -D PRIV_DIR="D:\a\tflite_beam\tflite_beam/priv"  -D TFLITE_ROOT_DIR="D:\a\tflite_beam\tflite_beam\3rd_party\tensorflow\tensorflow-2.16.1\tensorflow\lite"  -D GFLAGS_ROOT_DIR="D:\a\tflite_beam\tflite_beam\3rd_party\gflags"  -D GLOG_ROOT_DIR="D:\a\tflite_beam\tflite_beam\3rd_party\glog"  -D TFLITE_BEAM_CORAL_SUPPORT="false"  -D MIX_APP_PATH="D:\a\tflite_beam\tflite_beam"  "D:\a\tflite_beam\tflite_beam" &&  cmake --build .  &&  cmake --install . --config "Release"  )' : return code '0x1'

Closing as not planned.


Shoe classification

Pull Request for DL-Simplified 💡
Issue Title : Shoes Classification #37

Info about the related issue (Aim of the project) : Create a model to identify the brands of the shoes.
**Name:**Adithya S Kolavi
GitHub ID: adithya-s-k
Email ID<EMAIL_ADDRESS>**Idenitfy yourself:  SSOC Participant

Closes: #37
Describe the add-ons or changes you've made 📃
Shoe Classification using SVM and CNN
Type of change ☑
What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

How Has This Been Tested? ⚙
Describe how it has been tested
I have tested the model out using the testing data set and also have put the accuracy of it on the readme file
Checklist: ☑

[x] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have added things that prove my fix is effective or that my feature works.
[x] Any dependent changes have been merged and published in downstream modules.

@abhisheks008 I have made all the necessary changes please look into it


ZeroDivisionError: float division by zero

Im trying to run test.sh but  keep getting the same error,
seems I can't get the right utterances.
Can anyone kindly give me some advice?
Experiment name: seq2seq_mol_ppg2mel_vctk_libri_oneshotvc_r4_normMel_v2
Load PPG-model, PPG2Mel-model, Vocoder-model...
Removing weight norm...
Loaded the voice encoder model on cuda in 0.02 seconds.
Number of source utterances: 0.
0it [00:00, ?it/s]
RTF:
Traceback (most recent call last):
  File "convert_from_wav.py", line 216, in <module>
    main()
  File "convert_from_wav.py", line 212, in main
    convert(args)
  File "/usr/local/lib/python3.7/dist-packages/torch/autograd/grad_mode.py", line 15, in decorate_context
    return func(*args, **kwargs)
  File "convert_from_wav.py", line 167, in convert
    print(total_rtf / cnt)
ZeroDivisionError: float division by zero

I am having the same problem. Have you found any workaround ?

the <source_wav_dir> should be the file path, not a file


fix broken mesa dependencies

This pr resolves some dependency issues caused by the mesa update.

After updating these dependencies I tested all 7 examples in mesa-examples and they all work fine.

Thanks for the PR! The changes look good, only our pre-commit checks are failing. Would you like to fix that yourself, or would you prefer we fix it?

Thanks for your comment @EwoutH. I'm still getting familiar with the project and I'm not sure why the N803 rule about parameter names is triggered in the pre-commit. I would appreciate if you could help to resolve this issue.

Hmm somehow a force push closed this PR. Let me see how to bring it back.

Might be a GitHub issue: https://github.com/isaacs/github/issues/997
Updating others' PR through force push could cause problems.


bun start not working, I think  wrong import format on windows

CC @imrishabh18

i think this is an issue with make-vfs, it should use import path from "path/posix" instead of import path from "path" to be windows compatible. @Abse2001 would you like to take a stab at fixing it?

Taking a look

@Abse2001 Pull the latest main and let me know if it works

Ok

@imrishabh18  still the same problem

This seems weird, it should have not happened. Cause this file was not changed

Probably can you git stash your changes, and then checkout to the latest main and share what you see in this file?


JBPM-5704 - NPE when completing already completed user task

depends on https://github.com/droolsjbpm/jbpm/pull/752

jenkins retest this


Orzqwq scraping issue

I am having an issue downloading image sets in the form of a manga. Unsure if this is an issue with how the website is structured or an issue on my end.
Tried various methods to download
https://orzqwq.com/manga/camonome-bukatsu-chokugo-no-rikujoubu-joshi-ni-sasowarete/
get-sauce https://orzqwq.com/manga/camonome-bukatsu-chokugo-no-rikujoubu-joshi-ni-sasowarete/japanese/?style=list
Site:      https://orzqwq.com/
Title:
Type:      image
Stream:
 [0]  -------------------
 Type:            image
 Quality:         unknown
 Size:            0 B
 # download with: get-sauce -s 0 ...

get-sauce -p 1-61 https://orzqwq.com/manga/camonome-bukatsu-chokugo-no-rikujoubu-joshi-ni-sasowarete/
Site:      https://orzqwq.com/
Title:     [Camonome] Bukatsu Chokugo no Rikujoubu Joshi ni Sasowarete
Type:      image
Stream:
 [0]  -------------------
 Type:            image
 Quality:         unknown
 Parts:           61
 Size:            0 B
 # download with: get-sauce -s 0 ...

Downloaded 61 blank images
get-sauce https://orzqwq.com/manga/camonome-bukatsu-chokugo-no-rikujoubu-joshi-ni-sasowarete/japanese/p/1/
Site:      https://orzqwq.com/
Title:     [Camonome] Bukatsu Chokugo no Rikujoubu Joshi ni Sasowarete
Type:      image
Stream:
 [0]  -------------------
 Type:            image
 Quality:         unknown
 Size:            0 B
 # download with: get-sauce -s 0 ...

get-sauce -p 1-61 https://orzqwq.com/manga/camonome-bukatsu-chokugo-no-rikujoubu-joshi-ni-sasowarete/japanese/p/1/
panic: runtime error: index out of range [0] with length 0
goroutine 1 [running]:
github.com/gan-of-culture/get-sauce/extractors/orzqwq.extractData({0xc00007e060, 0x60})
C:/Users/XXXXX/go/pkg/mod/github.com/gan-of-culture/get-sauce@v1.2.37/extractors/orzqwq/orzqwq.go:92 +0x698
github.com/gan-of-culture/get-sauce/extractors/orzqwq.(*extractor).Extract(0x3c5ba0?, {0xc00007e060?, 0xc00007e068?})
C:/Users/XXXXX/go/pkg/mod/github.com/gan-of-culture/get-sauce@v1.2.37/extractors/orzqwq/orzqwq.go:34 +0xc5
github.com/gan-of-culture/get-sauce/extractors.Extract({0xc00007e060, 0x60})
C:/Users/XXXXX/go/pkg/mod/github.com/gan-of-culture/get-sauce@v1.2.37/extractors/extractors.go:127 +0xb6
main.download({0xc00007e060?, 0x60?})
C:/Users/XXXXX/go/pkg/mod/github.com/gan-of-culture/get-sauce@v1.2.37/main.go:46 +0xb5
main.main()
get-sauce https://orzqwq.com/manga/camonome-bukatsu-chokugo-no-rikujoubu-joshi-ni-sasowarete/japanese/?style=list
Site:      https://orzqwq.com/
Title:
Type:      image
Stream:
 [0]  -------------------
 Type:            image
 Quality:         unknown
 Size:            0 B
 # download with: get-sauce -s 0 ...

I did notice that there was no direct image address unless I went to the images on the page/list and copied the address from the image. When that url was used in get-sauce it was downloaded. The images are in the format:
https://img2.orzqwq.com/manga_62910f394c745/4fff8e79f1f2db9b2e349f1b1f770920/001.jpg
https://img2.orzqwq.com/manga_62910f394c745/4fff8e79f1f2db9b2e349f1b1f770920/002.jpg
https://img2.orzqwq.com/manga_62910f394c745/4fff8e79f1f2db9b2e349f1b1f770920/003.jpg
and so on
Is there a different command that I should be using for this website?

hmm interesting. I will take a look at it later today.

I think I fixed it. Please check if it works with the new version :>


Redundant Curly Braces, Trailing Comma, and Auto Correct Problem

It appears that the auto-correct removes the redundant curly braces, but still thinks it needs a comma, so we end up with two.
Original code
          expect(blah).to eq({
            @abc => 0,
            @xyz => 1
          })

Expected behavior
          expect(blah).to eq(
            @abc => 0,
            @xyz => 1,
          )

Actual behavior
          expect(blah).to eq(
            @free_service => 0,
            @express_24_service => 17.96,,
          )

Steps to reproduce the problem
rubocop -Ra spec_file.rb
RuboCop version
Tested against latest tag and master
0.38.0 (using Parser <IP_ADDRESS>, running on ruby 2.3.0 x86_64-darwin15)

I failed to confirm on master. I got:
expect(blah).to eq(@abc => 0,
                   @xyz => 1)

I put your original code in a test.rb file in rubocop's working directory, then ran bin/rubocop -Ra test.rb
Perhaps there's a difference in your .rubocop.yml that would explain this?

Style/TrailingCommaInArguments:
  EnforcedStyleForMultiline: comma

Style/TrailingCommaInLiteral:
  EnforcedStyleForMultiline: comma

What happens is this:

Style/TrailingCommaInArguments comes along and inserts a comma:

expect(blah).to eq({
  @abc => 0,
  @xyz => 1
},)

Style/TrailingCommaInLiteral comes and inserts its own:

expect(blah).to eq({
  @abc => 0,
  @xyz => 1,
},)

Style/BracesAroundHashParameters removes the braces:

expect(blah).to eq(
  @abc => 0,
  @xyz => 1,,
)

I'll leave it for someone else to suggest how to solve it, while I get some sleep. 😄

Style/BracesAroundHashParameters should probably also trim off the comma after the hash brace

After sleeping on it, I am thinking along the same lines @segiddins. At first it seemed strange this cop would check for it, but it is perfectly possible to have this to start with even without the cascading corrections:
expect(blah).to eq({
  @abc => 0,
  @xyz => 1,
},)


Installation on windows

I am using windows and GPU, so it seems GPU simulation is not feasible; can we do multiple simulation on CPU? when i try to use sim_backend cpu for num_envs it shows error

for CPU vectorization, the num_envs argument is not to be used as that is for GPU vectorization. Need to update the docs with CPU vectorization examples but there is example located here for RL setups: https://maniskill.readthedocs.io/en/latest/user_guide/reinforcement_learning/setup.html#evaluation

I forgot to mention, I am using Windows and I am trying to train using vector environments in the CPU; is it even feasible to do so. Cause while trying environment using above setup I got multiple errors.


Code to delete

ScalaToPyspark code is a big hack.
multi_equals is too niche and can probably be implemented better with the new PySpark 3 array functions.

Let's delete this code and then do the 1.0 release.

do we just have to remove whole code ?


RSS feeds

The new sms web app needs to generate the same RSS feeds as the old ones do for media items and collections. Examples:

http://rss.sms.cam.ac.uk/rss/media/2657898
http://rss.sms.cam.ac.uk/rss/collection/2448176

Once this story is completed, we will move rss.sms.cam.ac.uk from the old sms application to the new sms application

duplicated from #76


Support for SingleCellExperiment objects?

If your plan is to submit to BioC, it would be great to have support for SingleCellExperiment objects. I am trying to increase the diversity of cell type annotation methods in Bioconductor (SingleR, etc.), and it seems that this package would be a good fit.
We took SingleR through a similar refactoring process (see LTLA/SingleR#1), which considerably improved its performance and reference availability. Possibly worth considering some of the points here, especially the use of ExperimentHub to hold your datasets.

Thanks for the suggestion. We had internally talked about support for SCE, and now it's (roughly) done.
We have been watching your work on SingleR closely. The discussions and improvements made to it have been very helpful for us in thinking about our own package development.


Fix incorrect README command

Hi. Very cool repo and easy to spin up.
I was running this and noticed the devstats points to a script which wasn't working.
Using the command query was working fine so I updated it in the README.

Thank you @wd60622! I hope to get this repo into better shape soon. Would like to see weekly data snapshots and a better reporting pipeline. Thanks for giving it a try, and let me know if you have any ideas on how to improve it!

That's aweosome. Looking forward to see it. If you had a published Docker image, that'd be awesome.
I was able to generate the reports without issues by using the three exposed commands. But don't know how to generate an HTML report from the mardown which would allow me to see the data in a more visual way. If you have any tips on your workflow, let me know.