How to use StitcherService to directly play an mp3 file as a voiceover?

As you can see from the screenshot, a demonstration video VoiceoverDemo.mp4 explains at 2:20 that with StitcherService it is possible to directly play an mp3 file as a voiceover.

However when I try to use it a NameError occurs: name 'StitcherService' is not defined
from manim import *
from manim_voiceover import VoiceoverScene

class AzureExample(VoiceoverScene):
    def construct(self):
        # self.set_speech_service(
        #     AzureService(
        #         voice="ru-RU-DmitryNeural",
        #         style="newscast-casual",
        #         global_speed=1.15
        #     )
        # )
        self.set_speech_service(
            StitcherService("test.mp3")
        )

When I tried to fix it by importing StitcherService an ImportError occurred: cannot import name 'StitcherService' from 'manim_voiceover.services.stitcher' (/usr/local/lib/python3.11/site-packages/manim_voiceover/services/stitcher.py)
from manim import *
from manim_voiceover import VoiceoverScene
from manim_voiceover.services.stitcher import StitcherService

class AzureExample(VoiceoverScene):
    def construct(self):
        # self.set_speech_service(
        #     AzureService(
        #         voice="ru-RU-DmitryNeural",
        #         style="newscast-casual",
        #         global_speed=1.15
        #     )
        # )
        self.set_speech_service(
            StitcherService("test.mp3")
        )

So how to directly play an mp3 file as a voiceover?

I have run into the same problem. At the moment, the class has been renamed to _StitcherService, presumably because it is being worked on (?). In particular, I have noticed a bug, see #88. If you want to use _StitcherService anyway, you will have to go into the source code and modify the class as described in #88. This is only a workaround and should probably not be done long term... But at the moment, it works fine for me.


Add HotJar cookies to website usage section

Add the HotJar cookies that will be set for users that are visiting the website to the cookies page.

The copy sounds like it's aimed at us rather than our users.


[iOS] Re-initialize iOS App

Issue

close #441

Overview (Required)

Re-initialize iOS App Project

Run App Configurations with divided Xcode Projects

Setup project based on https://github.com/DroidKaigi/conference-app-2021/issues/439
Add document to README.md
There are no implementations about features.
No change to build tools, but this is no reason.

If it's necessary, switch to manage build tools with SPM.

TODOs

[x] Initialize AppScreen with 4 tabs

Links

Screenshot

Before
After

@takahirom
Please review this PR 🙏🏼
After this PR merged, we are ready to implement iOS App features.

:eyes:

@ostk0069
I fixed! Please re-review 🙏🏼

Merge this 🙏🏼


Add calculating ambient occlusion to the calclight routine

you have 2 new mapoptions:
ambientocclusion (value between 0 for off and 255 for very dark)
ambientocclusionradius (radius of the shadow)
a more detailed explanation taken from the source:

ambient occlusion (darkening of corners) works as follows:
you check for every point how much light possible comes onto it when the light comes from the whole sky (no lights/spotlights, whatever)
this will darken cracks and sharp edges and hence give a more realistic rendering output.
from every point we send out ray casts into the main directions (see below) and get a hit back if it touched the sky (or a skytextured cube, see RAY_SKIPSKY)
we then darken the lightmap color depending on how much the pixel is occlued.
(rays-hitting-a-wall / total-rays-sent -> value between 0 and 1.0) 1.0 = totally occlued, 0.0 = no occlusion

furthermore see https://github.com/inexor-game/code/wiki/Ambient-Occlusion
it has images
what does still need to be done?
nothing, it can be merged. (I may make some really small adjustments afterwards though)

+1

Just to be sure: are there good default values for these two variables?

Thats exactly what i want to improve actually: those default values are probably not in its best condition yet.  But i think after some fiddling we will find out the best default values. :)


Update CircleCI apt

From https://github.com/mne-tools/mne-nirs/pull/305/files

Ops I got mixed up between repos


"Focus Window" script doesn't work

Running "Focus Window" script does not show anything in the list.
Debugging the script it seems that w.name !== "" is always false on my machine.
Here's an example logging all windows:
[2024-01-16 15:23:10.488] [info]  Found mac-windows in /Users/alex/.kenv/package.json
[2024-01-16 15:23:10.588] [info]  {"height":1415,"name":"","number":20923,"ownerName":"Code","pid":39825,"width":2560,"x":0,"y":25}
[2024-01-16 15:23:10.588] [info]  {"height":500,"name":"","number":19675,"ownerName":"Open and Save Panel Service","pid":42256,"width":500,"x":0,"y":940}
[2024-01-16 15:23:10.588] [info]  {"height":500,"name":"","number":18734,"ownerName":"Emoji & Symbols","pid":39747,"width":500,"x":0,"y":940}
[2024-01-16 15:23:10.588] [info]  {"height":1415,"name":"","number":17988,"ownerName":"Google Chrome","pid":32027,"width":2560,"x":0,"y":25}
[2024-01-16 15:23:10.588] [info]  {"height":500,"name":"","number":15931,"ownerName":"Control Center","pid":651,"width":500,"x":0,"y":940}
[2024-01-16 15:23:10.588] [info]  {"height":100,"name":"","number":13743,"ownerName":"Dropbox","pid":79962,"width":100,"x":0,"y":1340}
[2024-01-16 15:23:10.588] [info]  {"height":50,"name":"","number":13742,"ownerName":"Dropbox","pid":79962,"width":50,"x":0,"y":1390}
[2024-01-16 15:23:10.589] [info]  {"height":380,"name":"","number":13741,"ownerName":"Dropbox","pid":79962,"width":360,"x":1100,"y":530}
[2024-01-16 15:23:10.589] [info]  {"height":1079,"name":"","number":8735,"ownerName":"Sourcetree","pid":649,"width":1728,"x":416,"y":193}
[2024-01-16 15:23:10.589] [info]  {"height":1415,"name":"","number":8668,"ownerName":"Code","pid":39825,"width":2560,"x":0,"y":25}
[2024-01-16 15:23:10.589] [info]  {"height":1415,"name":"","number":8667,"ownerName":"Code","pid":39825,"width":2560,"x":0,"y":25}
[2024-01-16 15:23:10.589] [info]  {"height":500,"name":"","number":8632,"ownerName":"CursorUIViewService","pid":829,"width":500,"x":0,"y":940}
[2024-01-16 15:23:10.589] [info]  {"height":500,"name":"","number":8783,"ownerName":"CursorUIViewService","pid":829,"width":500,"x":0,"y":940}
[2024-01-16 15:23:10.589] [info]  {"height":500,"name":"","number":20073,"ownerName":"CursorUIViewService","pid":829,"width":500,"x":0,"y":940}
[2024-01-16 15:23:10.589] [info]  {"height":500,"name":"","number":19847,"ownerName":"CursorUIViewService","pid":829,"width":500,"x":0,"y":940}
[2024-01-16 15:23:10.589] [info]  {"height":600,"name":"","number":13740,"ownerName":"Dropbox","pid":79962,"width":400,"x":0,"y":840}
[2024-01-16 15:23:10.589] [info]  {"height":500,"name":"","number":8613,"ownerName":"Open and Save Panel Service","pid":39738,"width":500,"x":0,"y":940}
[2024-01-16 15:23:10.589] [info]  {"height":180,"name":"","number":3664,"ownerName":"Kit","pid":7007,"width":240,"x":2080,"y":25}
[2024-01-16 15:23:10.589] [info]  {"height":500,"name":"","number":713,"ownerName":"loginwindow","pid":396,"width":500,"x":0,"y":940}
[2024-01-16 15:23:10.589] [info]  {"height":500,"name":"","number":180,"ownerName":"iTerm2","pid":2485,"width":500,"x":0,"y":940}
[2024-01-16 15:23:10.589] [info]  {"height":1415,"name":"","number":179,"ownerName":"iTerm2","pid":2485,"width":2560,"x":0,"y":25}
[2024-01-16 15:23:10.589] [info]  {"height":432,"name":"","number":106,"ownerName":"Alfred","pid":996,"width":718,"x":921,"y":214}
[2024-01-16 15:23:10.589] [info]  {"height":52,"name":"","number":101,"ownerName":"Karabiner-NotificationWindow","pid":1435,"width":398,"x":2150,"y":1378}
[2024-01-16 15:23:10.589] [info]  {"height":416,"name":"","number":97,"ownerName":"Google Drive","pid":1059,"width":350,"x":0,"y":1024}
[2024-01-16 15:23:10.589] [info]  {"height":1415,"name":"","number":94,"ownerName":"Sourcetree","pid":649,"width":2560,"x":0,"y":25}
[2024-01-16 15:23:10.590] [info]  {"height":160,"name":"","number":93,"ownerName":"TextInputSwitcher","pid":908,"width":247,"x":1156,"y":653}
[2024-01-16 15:23:10.590] [info]  {"height":500,"name":"","number":89,"ownerName":"Sourcetree","pid":649,"width":500,"x":0,"y":940}
[2024-01-16 15:23:10.590] [info]  {"height":128,"name":"","number":83,"ownerName":"Alfred","pid":996,"width":100,"x":100,"y":1212}
[2024-01-16 15:23:10.590] [info]  {"height":1415,"name":"","number":8737,"ownerName":"Sourcetree","pid":649,"width":2560,"x":0,"y":25}
[2024-01-16 15:23:10.590] [info]  {"height":500,"name":"","number":1644,"ownerName":"Kit","pid":7007,"width":500,"x":0,"y":940}
[2024-01-16 15:23:10.590] [info]  {"height":480,"name":"","number":1640,"ownerName":"Kit","pid":7007,"width":768,"x":896,"y":202}
[2024-01-16 15:23:10.590] [info]  {"height":1415,"name":"","number":64,"ownerName":"WhatsApp","pid":644,"width":2560,"x":0,"y":25}
[2024-01-16 15:23:10.590] [info]  {"height":500,"name":"","number":22117,"ownerName":"CursorUIViewService","pid":829,"width":500,"x":0,"y":940}
[2024-01-16 15:23:10.590] [info]  {"height":1415,"name":"","number":47,"ownerName":"Finder","pid":654,"width":2560,"x":0,"y":25}
[2024-01-16 15:23:10.590] [info]  {"height":570,"name":"","number":2015,"ownerName":"Notion","pid":7926,"width":755,"x":903,"y":379}
[2024-01-16 15:23:10.590] [info]  {"height":1415,"name":"","number":2014,"ownerName":"Notion","pid":7926,"width":2560,"x":0,"y":25}
[2024-01-16 15:23:10.590] [info]  {"height":1440,"name":"","number":35,"ownerName":"AXVisualSupportAgent","pid":606,"width":2560,"x":0,"y":0}
[2024-01-16 15:23:10.593] [info]  {"height":1440,"name":"","number":31,"ownerName":"Notification Center","pid":636,"width":2560,"x":0,"y":0}
[2024-01-16 15:23:10.593] [info]  {"height":500,"name":"","number":22487,"ownerName":"CursorUIViewService","pid":829,"width":500,"x":0,"y":940}
[2024-01-16 15:23:10.593] [info]  {"height":1440,"name":"","number":29,"ownerName":"AXVisualSupportAgent","pid":606,"width":2560,"x":0,"y":0}
[2024-01-16 15:23:10.593] [info]  {"height":500,"name":"","number":22486,"ownerName":"CursorUIViewService","pid":829,"width":500,"x":0,"y":940}
[2024-01-16 15:23:10.593] [info]  {"height":1440,"name":"","number":28,"ownerName":"AXVisualSupportAgent","pid":606,"width":2560,"x":0,"y":0}
[2024-01-16 15:23:10.593] [info]  {"height":1440,"name":"","number":27,"ownerName":"Dock","pid":650,"width":2560,"x":0,"y":0}
[2024-01-16 15:23:10.593] [info]  {"height":1440,"name":"","number":26,"ownerName":"Dock","pid":650,"width":2560,"x":0,"y":0}
[2024-01-16 15:23:10.594] [info]  {"height":254,"name":"","number":16065,"ownerName":"LinkedNotesUIService","pid":11478,"width":254,"x":2306,"y":1186}
[2024-01-16 15:23:10.594] [info]  {"height":76,"name":"","number":11,"ownerName":"AccessibilityVisualsAgent","pid":618,"width":302,"x":100,"y":1280}
[2024-01-16 15:23:10.594] [info]  {"height":300,"name":"","number":10,"ownerName":"AccessibilityVisualsAgent","pid":618,"width":300,"x":1279,"y":720}
[2024-01-16 15:23:10.594] [info]  {"height":84,"name":"","number":19211,"ownerName":"Google Chrome","pid":32027,"width":403,"x":1855,"y":97}
[2024-01-16 15:23:10.594] [info]  {"height":1415,"name":"","number":51,"ownerName":"Finder","pid":654,"width":2560,"x":0,"y":25}
[2024-01-16 15:23:10.594] [info]  {"height":1415,"name":"","number":50,"ownerName":"Finder","pid":654,"width":2560,"x":0,"y":25}
[2024-01-16 15:23:10.594] [info]  {"height":500,"name":"","number":8671,"ownerName":"Code","pid":39825,"width":500,"x":0,"y":940}

System
Is there an easy way to get the relevant system info using Script Kit for these bug reports?
macOS 14.2.1 (M1)
Kit 2.3.0

Indeed that was the issue.
I'm glad that it's a quick fix 😁
I wonder if a script could check the required permission and warn when it's not enabled?
Related https://github.com/johnlindquist/kit/issues/1420
Perhaps this permission should be added to the menu as well?


Table Theme, Badge, Table Badge, Table Text

PR Type
Enhancement, Tests

Description

Enhanced Badge component with new props and styles.
Added TableBadge component with editing capabilities and updated stories.
Implemented TableTextField component with support for editing and variants.
Updated various table components to use the new table theme.
Added new demo configurations and stories for TableBadge and TableTextField.

Changes walkthrough 📝
Relevant filesEnhancement15 files

Badge.stories.tsxUpdate Badge stories to include iconName prop

apps/demo/stories/Badge.stories.tsx
Added iconName prop to Badge component in stories.  Changed layout to center align items.

+3/-3

TableBadge.stories.tsxEnhance TableBadge stories with headings and editing options

apps/demo/stories/TableBadge.stories.tsx
Added Heading components for better sectioning.  Updated TableBadge component props and layout.  Added editing options for TableBadge.

+22/-11

TableTextField.stories.tsxAdd TableTextField component demo and variants

apps/demo/stories/TableTextField.stories.tsx
Added TableTextField component demo.  Added variants for TableTextField.

+29/-36

index.tsEnable TableBadge and TableTextField stories

apps/demo/stories/index.ts
Un-commented exports for TableBadge and TableTextField stories.

+2/-2

TableBadge.config.tsxAdd controls to TableBadge demo configuration

apps/demo/story-config/TableBadge.config.tsx

Added controls for TableBadge demo configuration.

+13/-1

TableTextField.config.tsxUpdate TableTextField demo configuration with variants

apps/demo/story-config/TableTextField.config.tsx

Updated TableTextField demo configuration to include variants.

+7/-4

Badge.tsxRefactor Badge component with new props and styles

packages/ui/src/Badge.tsx
Refactored Badge component to support new props and styles.  Added secondary border colors and improved layout.

+49/-28

Common.tsExtend Common interfaces for Table and Badge components

packages/ui/src/Common.ts
Added TableTheme interface.  Added new props for Badge, TableBadge, and TableTextField.

+96/-7

PickerSelect.tsxMake placeholder prop optional in RNPickerSelect

packages/ui/src/PickerSelect.tsx

Made placeholder prop optional in RNPickerSelect.

+1/-5

Theme.tsxAdd default table theme properties to theme configuration

packages/ui/src/Theme.tsx
Added default table theme properties to defaultPrimitives.  Included table theme in defaultTheme.

+16/-0

TableBadge.tsxImplement TableBadge component with editing capabilities

packages/ui/src/table/TableBadge.tsx

Implemented TableBadge component with editing capabilities.

+59/-15

TableBoolean.tsxUpdate TableBoolean component to use table theme

packages/ui/src/table/TableBoolean.tsx

Updated TableBoolean component to use table theme for max width.

+16/-2

TableDate.tsxUpdate TableDate component to use table theme

packages/ui/src/table/TableDate.tsx
Updated TableDate component to use table theme for max width and padding.

+10/-6

TableIconButton.tsxUpdate TableIconButton component to use table theme

packages/ui/src/table/TableIconButton.tsx
Updated TableIconButton component to use table theme for max width.

+18/-9

TableTextField.tsxImplement TableTextField component with editing and variants

packages/ui/src/table/TableTextField.tsx
Implemented TableTextField component with support for editing and variants.

+57/-5

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

FYI, there's still some stuff related to editing tables in here, even though we don't support that yet. Leaving it in for now since we'll want to put that in soon.

@kjkurtz ok, table should be fixed up on mobile, works on Android too


dump_as/_class isn't inferring the proper class

In the case of something like dm-types Csv or anything that essentially results in a String/Text the dm-migration tries to look up the type for that column from a type_map. This happens either by way of looking up the property class itself or by calling dump_class and alias for dump_as. dump_as is an option set on the property (akin to load_as, but that's a class method for the extended type itself).
I'm proposing that dump_as either infers the class that it should dump as (from the property it inherits from maybe, just call super if the option isn't set?) or, at the very least, it does not attempt to use load_as for the dump_as. Given most types are a mapping from something more complex (like an Array) to something simpler, it seems unlikely that load/dump would be the same type.
I'll send a PR if there is one that is preferred. But, if you find this page and you're hitting this problem, start by setting dump_as option on your property using a dm-type.

I think I already addressed that with my pull request in datamapper/dm-migrations#54 . Maybe you could take a look.

@tillsc This appears to solve it.
Maybe I was hoping that there could be a dump_as on the custom type just like there is a load_as. Rather than setting it with an option on the property. I guess I'm not sure where the change took place in dm-migrations that broke custom types base type.

It would be a change for sure to add dump_as, but I like the explicitness of it.

This never worked for me in any 1.x release. I always had to hack something to get a LOB beneath my JSON/CSV/... complex types.

Huh, I'm trying to figure out how my custom types worked in the past. Maybe I added the column by hand, rather than through auto upgrade … :shrugs:


Multiple node fields resolve to same GraphQL field

Wondering if you could point me in the right direction to fix these warnings about multiple node fields resolving to same GraphQL field. Things seem to be working fine but I try my best to handle warnings when they come in.
Error when running Gatsby develop:
warn Multiple node fields resolve to the same GraphQL field `StrapiArticle.author.avatar` - [`avatar`, `avatar___NODE`]. Gatsby will use `avatar___NODE`.
warn Multiple node fields resolve to the same GraphQL field `StrapiArticle.icon` - [`icon`, `icon___NODE`]. Gatsby will use `icon___NODE`.

Both of these refer to single media fields.

Buenas a todos, lo que hice fue hacer "gatsby clean" y luego "gatsby develop" y me funcionó. El proyecto lo hice con strapi.

I too have the same error Unable to use a same component twice on a single page. I fixed it by removing the components and adding the items as single items

@HAHRJR94 please only use English here, but I have translated your message for others:
Hi everyone, what I did was do "gatsby clean" and then "gatsby develop" and it worked for me. I did the project with strapi.

I trashed the .cache folder, but I guess gatsby clean is a better way. Cleared up my issues.

Or you can just ignore it as I did ((:

For anyone still having this issue when using Single Media fields in strapi
yarn add<EMAIL_ADDRESS>

guys I'm having the same warning and I run gatsby clean without difference.
NOTE : I'm not using strapi, instead these my library related to gatsby source : @robinmetral/gatsby-source-s3, gatsby-source-filesystem, gatsby-source-serverless-aurora


Theme in Time Picker

when i use inputType: CupertinoDateTimePickerInputType.both and change in theme the Changes occur in Date only, not in date and time
And when I just choose the inputType: CupertinoDateTimePickerInputType.time, there is no change in the theme either
Example
Future<TimeOfDay?> _showTimePicker(
      BuildContext context, DateTime? currentValue) async {
    final timePicker = widget.alwaysUse24HourFormat
        ? DatePicker.showTimePicker(
            context,
            showTitleActions: true,
            currentTime: currentValue,
            showSecondsColumn: false,
            theme: widget.theme,
            locale: _localeType(),
          )
        : DatePicker.showTime12hPicker(
            context,
            showTitleActions: true,
            currentTime: currentValue,
            locale: _localeType(),
            theme: widget.theme,
          );

Closing it since the PR which solves it is merged. Feel free to comment if it is not the case.


[JENKINS-57797] Update Casc version and rename classes to fit the parent

Update the casc version and the name of the class because the parent class was renamed at the last minute.
CC: @alecharp @kuisathaverat

CC: @oleg-nenashev 	@fcojfernandez @varyvol @batmat

Thank you, Iván

Could you cut a release @kuisathaverat? Thank you.

I've seen you already did, thanks!


Unable to set username and password

Description
I am attempting to set the password of my machine, but it's continually hanging on the command. I referenced other examples within this repos history/issues, but unfortunately, it continues to hang. Any help is appreciated!
Example Vagrantfile
# -*- mode: ruby -*-
# vi: set ft=ruby :

vmname = "unreal-base"

Vagrant.configure("2") do |config|
  config.vm.box = "google/gce"

  config.vm.guest = :windows
  config.vm.communicator = "winrm"
  config.winrm.port = 5986

  config.winrm.username = "shannen"
  config.winrm.password = "passw0rd"

  config.winrm.transport = :ssl
  config.winrm.ssl_peer_verification = false

  config.vm.define :winserver do |winserver|
    winserver.vm.synced_folder ".", "/vagrant", disabled: true

    winserver.vm.provider :google do |google, override|
      google.google_project_id = REDACTED

      google.image_family = "windows-2016"
      google.machine_type = "n1-standard-4"

      google.disk_size = "80"
      google.name = "dev"

      google.zone = "us-east4-c"

      google.setup_winrm_password = true

      google.tags = ['winrm', 'http-server', 'https-server']

      google.can_ip_forward = true

      google.accelerators = [{
        :type => "nvidia-tesla-p4-vws",
        :count => 1
      }]

      google.on_host_maintenance = "TERMINATE"

      override.winrm.port = 5986
      override.ssh.username = "shannen"
      override.ssh.private_key_path = "./tmp/id_rsa.pub"
    end
  end
end

Logs
Bringing machine 'winserver' up with 'google' provider...
==> winserver: Checking if box 'google/gce' version '0.1.0' is up to date...
==> winserver: Warning! The Google provider doesn't support any of the Vagrant
==> winserver: high-level network configurations (`config.vm.network`). They
==> winserver: will be silently ignored.
==> winserver: Launching an instance with the following settings...
==> winserver:  -- Name:                dev
==> winserver:  -- Project:              REDACTED
==> winserver:  -- Type:                 n1-standard-4
==> winserver:  -- Disk type:            pd-standard
==> winserver:  -- Disk size:            80 GB
==> winserver:  -- Disk name:
==> winserver:  -- Image:
==> winserver:  -- Image family:         windows-2016
==> winserver:  -- Instance Group:
==> winserver:  -- Zone:                 us-east4-c
==> winserver:  -- Network:              default
==> winserver:  -- Network Project:      REDACTED
==> winserver:  -- Metadata:             '{}'
==> winserver:  -- Labels:               '{}'
==> winserver:  -- Network tags:         '["winrm", "http-server", "https-server"]'
==> winserver:  -- IP Forward:           true
==> winserver:  -- Use private IP:       false
==> winserver:  -- External IP:
==> winserver:  -- Network IP:
==> winserver:  -- Preemptible:          false
==> winserver:  -- Auto Restart:         true
==> winserver:  -- On Maintenance:       TERMINATE
==> winserver:  -- Autodelete Disk:      true
==> winserver:  -- Additional Disks:     []
==> winserver:  -- Accelerators:         [{:type=>"nvidia-tesla-p4-vws", :count=>1}]
==> winserver: Waiting for instance to become "ready"...
==> winserver: Machine is booted and ready for use!
==> winserver: Setting up WinRM Password
==> winserver: Temp Password: REDACTED
==> winserver: Waiting for WinRM To be ready
    winserver: WinRM address: REDACTED
    winserver: WinRM username: shannen
    winserver: WinRM execution_time_limit: PT2H
    winserver: WinRM transport: ssl
==> winserver: Changing password from temporary to winrm password # Hangs here
Vagrant timed out while attempting to connect via WinRM. This usually
means that the VM booted, but there are issues with the WinRM configuration
or network connectivity issues. Please try to `vagrant reload` or
`vagrant up` again.

Additional details
Vagrant v2.3.4
Screenshots
I did notice below. I have added my ssh keys to Metadata and VMs are supposed to inherit the ssh keys automatically so I didn't think this is an issue

From Metadata:

for anyone who runs into a similar issue...I've added the following and it helped get me further
      google.metadata = {
        'sysprep-specialize-script-cmd' => "googet -noconfirm=true install google-compute-engine-ssh",
        'enable-windows-ssh' => true
      }


Unable to spend XZC from trezor via Electrum-XZC

I get the following error while trying to spend xzc from a trezor with the electrum wallet.This is the error:
ProcessError: Encountered invalid prev_hash
Traceback:
Traceback (most recent call last):
  File "electrum_xzc/gui/qt/util.py", line 718, in run
  File "electrum_xzc/wallet.py", line 1115, in sign_transaction
  File "/var/folders/n9/vwm9k4xs06nbyvcnk9w0znz80000gn/T/_MEIq3fFpY/electrum_xzc/plugins/trezor/trezor.py", line 91, in sign_transaction
    self.plugin.sign_transaction(self, tx, prev_tx, xpub_path)
  File "/var/folders/n9/vwm9k4xs06nbyvcnk9w0znz80000gn/T/_MEIq3fFpY/electrum_xzc/plugins/trezor/trezor.py", line 336, in signtransaction
    signatures,  = client.sign_tx(self.get_coin_name(), inputs, outputs, details=details, prev_txes=prev_tx)
  File "/var/folders/n9/vwm9k4xs06nbyvcnk9w0znz80000gn/T/_MEIq3fFpY/electrum_xzc/plugins/trezor/clientbase.py", line 224, in sign_tx
    return trezorlib.btc.sign_tx(self.client, *args, **kwargs)
  File "/var/folders/n9/vwm9k4xs06nbyvcnk9w0znz80000gn/T/_MEIq3fFpY/electrum_xzc/plugins/trezor/clientbase.py", line 74, in exit
    raise RuntimeError(str(e)) from e
RuntimeError: ProcessError: Encountered invalid prev_hash

I have updated trezor to latest firmware version thinking that was the issue,still same error after updating

Hi, @akshaynexus
Please check if there are Sigma transactions selected as the source for the the crashing tx.

yes,the inputs are sigma inputs

Please downgrade to the previous release or chose no Sigma spends as the tx outputs. I'll fix it quite soon.

Using previous version also fails to spend the coins.I suppose sigma spends is not possible in electrum currently?

Thanks for your input. Yes, it looks like it's not possible to use a Trezor device to sign a tx which input is a Sigma spend at the moment. Using just Electrum-XZC is OK in this case.

is it planned to support sigma spends on trezor soon?cant move my funds due this.

Yes, it'll be supported soon but I have just ordered a Trezor device, so ETA is 2-3 weeks.
There are 2 options to get access to your funds. 1. Set up an Electrum-XZC wallet without the Trezor, but with entering the BIP39 words that the Trezor generated during setup into Electrum-XZC (maybe the BIP44 checkbox should be enabled).

Ok

Was there any update to this issue?

I've just started today with it. I'll finish in a couple of days. My apologies for the delay (delivery took ways longer than usual)


cmd/cue: "help flags" documents unverifiable behaviour with --list and --merge

What version of CUE are you using (cue version)?

$ cue version
cue version v0.9.2

go version go1.22.4
      -buildmode exe
       -compiler gc
       -trimpath true
     CGO_ENABLED 0
          GOARCH amd64
            GOOS linux
         GOAMD64 v1
cue.lang.version v0.9.2

Does this issue reproduce with the latest stable release?
0.9.2 is latest.
What did you do?
I read https://cuelang.org/docs/reference/command/cue-help-flags/ (text updated here to reflect the correction anticipated in https://cuelang.org/cl/1199496):

Handling multiple documents or streams
To handle multi-document files, such as JSON Lines or YAML
files with document separators (---), the user must specify
the --merge, --list, or --files flag.
The --merge flag merges each element into a single package as
if each element was defined in a separate file. The --list flag
concatenates each entry in a file into a list.
Using --list flag in combination with the --merge flag
concatenates entries with the same path into a list, instead of
unifying them.

I then tried to use the information in the final sentence, combining --merge and --list in a single cue export command:
# Default behaviour is "--merge".
exec cue export data.yml
cmp stdout out.merge
exec cue export data.yml --merge
cmp stdout out.merge

# "--list" does something different".
exec cue export data.yml --list
cmp stdout out.list

# "--list --merge" behaves identically to "--list".
exec cue export data.yml --list --merge
cmp stdout out.list

-- data.yml --
---
A: 10
a:
  b: 1
doc0: true
---
A: 10
a:
  c: 2
doc1: true
---
A: 10
a:
  d: 3
doc2: true
-- out.merge --
{
    "A": 10,
    "a": {
        "b": 1,
        "c": 2,
        "d": 3
    },
    "doc0": true,
    "doc1": true,
    "doc2": true
}
-- out.list --
[
    {
        "A": 10,
        "a": {
            "b": 1
        },
        "doc0": true
    },
    {
        "A": 10,
        "a": {
            "c": 2
        },
        "doc1": true
    },
    {
        "A": 10,
        "a": {
            "d": 3
        },
        "doc2": true
    }
]

What did you expect to see?
I expected to see cue export --merge --list behaving differently from cue export --list, when given "entries with the same path" - resulting in a failing test.
What did you see instead?
A passing test. I can't provide a failing test, as I don't understand what effect the help text is documenting.

cc @mvdan because this could be related to recent JSONL issues.

Per my last review of https://review.gerrithub.io/c/cue-lang/cue/+/1199496 I actually think the help text was right in the original version; combining --list and --path is a supported behavior.
From my reading of the flags, combining --list and --merge shouldn't be useful, as they do opposite things, and perhaps we should treat that as an error for the sake of UX.


NextGame Error

Hi,
The next game returns a empty array while there is a next game coming up.

Hey thanks for feedback
Try new version.


WEBUMENIA-1241 Set up Laravel deployer

Description

Initial Laravel deployer configuration. Already deployed on http://test.webumenia.sk/
Image placeholders have been moved to /public/images/no-image/...
(Child) sitemaps are now being generated to /public/sitemaps/...

Fixes https://jira.sng.sk/browse/WEBUMENIA-1241
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] I have updated the CHANGELOG
[x] I have requested at least 1 reviewer for this PR
[x] I have made corresponding changes to the documentation

This is now ready for another review. Please note the updated PR description.


Python frame speedup

This fixes #187, amounting to a 100x speedup, which is nice.
Integration tests are all passing, but I shall leave a stress test running over the weekend to check this change doesn't introduce any memory leaks.

Fantastic!

Set a variant of the MazeRunner running that attempted to save every frame to disk. Over the weekend it saved around 3.7 million pngs, at 860x480 pixels each, amounting to 438GB of data. Frame rate stayed solid, memory use stayed level, and the time to save each png seemed to remain around the same (between 50-60ms). No crashes, nothing degrading, and nothing caught fire. I think it's safe to merge...


remove master node selector

This selector is causing frustration/confusion when people try to deploy the operator on clusters that do not have a master node labeled, or that have other default nodeselector's being applied to their resources.  Until we hear otherwise, I don't see a good reason to restrict ourselves to specifically the master node.
/assign @dmage

https://github.com/openshift/cluster-image-registry-operator/blob/7c61167496ab038f3294f253dbbb54b2c06b9b18/pkg/resource/podtemplatespec.go#L220
@bparees should this node selector be removed as well?

hm.  yes, i guess so, at least for now. will update.

updated, thanks @dmage

/lgtm


Cache cleared without creating default instance

It is possible to pass custom implementation of the cache to the constructor.
However, when the cache is cleared, it is always instantiated with default implementation.

Coverage remained the same at ?% when pulling b0c7d0f66f52e43fb02e0321509521edfcfe26dc on embecka:patch-1 into 2977814a20f5729fbe3fbaf97f437cc7a73878e9 on syrusakbary:master.


keepassxc: 2.6.4 -> 2.6.6

Motivation for this change
Things done

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

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

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 126828 at 699cac1e run on x86_64-linux 1

1 package built successfully:

keepassxc

4 suggestions:

warning: unused-argument
Unused argument: fetchpatch.
Near pkgs/applications/misc/keepassx/community.nix:3:3:
  |
3 | , fetchpatch
  |   ^

warning: unused-argument
Unused argument: makeWrapper.
Near pkgs/applications/misc/keepassx/community.nix:5:3:
  |
5 | , makeWrapper
  |   ^

warning: build-tools-in-build-inputs
asciidoctor is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/applications/misc/keepassx/community.nix:97:3:
   |
97 |   buildInputs = [
   |   ^

warning: missing-patch-comment
Consider adding a comment explaining the purpose of this patch on the line preceeding.
Near pkgs/applications/misc/keepassx/community.nix:64:5:
   |
64 |     ./darwin.patch
   |     ^


I'd like to use this with my own proxied backed to completely hide the API key

Possible?

Since the GoldRush Kit is a Client-side rendering lib that requires the Covalent API key to exist on the client, you cant hide you API key via a proxy
However, you can manage security for you key via the Covalent Platform and limit the key to only work for specific origins or IPs


Calibration is not functional.

The description is confusing, describing 10 Hz in the server. Target describes 100 Hz. I have a server with Arduino UNO and Calibrating attiny25. Calibration does not work even after checking plugged in.I use sketches from EXTRAS.
Thank you

Thank you for your detailed feedback!

I'm sorry, I had CKDIV8 set to TARGET. Division 8 is already set in the program. Have a great Christmas.

I'm sorry, I had CKDIV8 set to TARGET. Division 8 is already set in the
program. Have a great Christmas.
---------- Původní e-mail ----------
Od: Bernhard @.>
Komu: felias-fogg/avrCalibrate @.>
Kopie: mirekv8 @.>, Author @.>
Datum: 23. 12. 2024 22:27:04
Předmět: Re: [felias-fogg/avrCalibrate] Calibration is not functional.
(Issue #1)
"
Thank you for your detailed feedback!
—
Reply to this email directly, view it on GitHub
(https://github.com/felias-fogg/avrCalibrate/issues/1#issuecomment-2560314759)
, or unsubscribe
(https://github.com/notifications/unsubscribe-auth/BN5WV6HYJQL3JFLRKKBRZIL2HB52NAVCNFSM6AAAAABUDP3IUGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRQGMYTINZVHE)
.
You are receiving this because you authored the thread. Message ID: <felias-
@.***>
"


could not compile bevy_render

Bevy version
0.8.0
The release number or commit hash of the version you're using.
8b27124a801d83a1e92f1136ebd2bc9752c3e9d7
[Optional] Relevant system information
WIN10
Msys2
rustc 1.60.0
cargo 1.60.0
After I git the newest bevy
Then "cargo run --example breakout"
it rolls out the error info as following:
Compiling bevy_render v0.8.0-dev (E:\Cmder_Project\bevy\bevy\crates\bevy_render)
error[E0658]: trait bounds other than Sized on const fn parameters are unstable
--> crates\bevy_render\src\render_resource\buffer_vec.rs:17:6
|
17 | impl<T: Pod> BufferVec {
|      ^
18 |     pub const fn new(buffer_usage: BufferUsages) -> Self {
|     ---------------------------------------------------- function declared as const here
|
= note: see issue #93706 https://github.com/rust-lang/rust/issues/93706 for more information
For more information about this error, try rustc --explain E0658.
error: could not compile bevy_render due to previous error
warning: build failed, waiting for other jobs to finish...
error: build failed
Admin@DESKTOP-3SIKCVE MINGW64 /e/Cmder_Project/bevy/bevy
cargo run --example breakout
Compiling bevy_render v0.8.0-dev (E:\Cmder_Project\bevy\bevy\crates\bevy_render)
error[E0658]: trait bounds other than Sized on const fn parameters are unstable
--> crates\bevy_render\src\render_resource\buffer_vec.rs:17:6
|
17 | impl<T: Pod> BufferVec {
|      ^
18 |     pub const fn new(buffer_usage: BufferUsages) -> Self {
|     ---------------------------------------------------- function declared as const here
|
= note: see issue #93706 https://github.com/rust-lang/rust/issues/93706 for more information
For more information about this error, try rustc --explain E0658.
error: could not compile bevy_render due to previous error

Duplicate of https://github.com/bevyengine/bevy/issues/4862
Please update your rust version using rustup update


Add sp1 groth16

Before sending a task run
build-sp1-groth16-macos

and then
  make send-groth16_bn254-proof DA_SOLUTION=<calldata|eigen|celestia>

closing this since groth16 has been deprecated from sp1


[Bug] Dont't allow uppercase names for Machine Deployments

Hi,
both forms for adding a new Machine Deployment seems to have a bug while checking the name.
When i try to use special chars in the Machine Deployment name this message appears:

Alright. So as the message says in the brackets (the text in front of is also wrong) only lowercase chars, digits and dashes are allowed. But the message disappears if i remove the exclamation mark at the end.

And ... the Machine Deployment fails.

So please fix the name check :)
Thanks.

Hi @Schluggi, that sounds like https://github.com/kubermatic/kubermatic/issues/8301 to me, right? machine-controller isn't really the source of the bug here, as the validation is happening correctly in machine-controller (which is the problem, as the UI and machine-controller disagree on what's allowed).

@embik yes. It's duplicated. Sorry for that :/

No worries at all!


Rename style prop and fix all occurences

Details
Rename the style prop from styles to style and fix all occurrences passing the wrong prop.
Fixed Issues

$ https://github.com/Expensify/App/issues/19717
$ https://github.com/Expensify/App/issues/18658
$ https://github.com/Expensify/App/issues/18658#issuecomment-1560205815
Tests

Images -

Send an image to any chat.
Verify there is no outline on image thumbnail.
Verify there is no invalid prop error in console.
Verify that you can open the image by clicking on it (pressing on it on phone).
Verify that you can open the context menu by right clicking on it (long pressing on it on phone).

DetailsPage -

Open chat with different user
Click the user avatar/name on the top of the screen to open RHN with user details.
Verify that user avatar styling is unchanged and press action can be triggered correctly.

ProfilePage -

Go to settings > profile.
Check there is no error in the console.
Check that the profile picture appears without any outline.

[x] Verify that no errors appear in the JS console

Offline tests

Same steps as above.
QA Steps

Same as above.

[ ] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
https://github.com/Expensify/App/assets/31413407/2f2b2fd8-a5eb-4aa6-9d79-1436273e9d4a

Mobile Web - Chrome
https://github.com/Expensify/App/assets/31413407/c9f60f75-c564-4603-bdbf-5cf478c3f349

Mobile Web - Safari
https://github.com/Expensify/App/assets/31413407/4699daa5-736e-4aad-87fd-fd5044e09ed7
https://github.com/Expensify/App/assets/31413407/c223defa-f888-4d6f-b4f2-d86be7f65002

Desktop
https://github.com/Expensify/App/assets/31413407/258246e4-0dff-4555-997b-13d1bf03bb23

iOS
https://github.com/Expensify/App/assets/31413407/9bcb894b-70b6-44be-ae53-2e284d4de8d1

Android
https://github.com/Expensify/App/assets/31413407/b7a1efe2-4d7e-40a6-a129-1ab00d5d4126

@parasharrajat PR here.

@parasharrajat I found a couple of small mistakes there and added comments. I think maybe you can still merge that PR today, in which case we can close this.

@Nikhil-Vats Do you know if this PR is still needed?

Yes


Cmake warnings/error in FindSuiteSparse.cmake

CMake Warning (dev) at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:426 (message):
  The package name passed to `find_package_handle_standard_args`
  (SuiteSparse_CXSparse) does not match the name of the calling package
  (SuiteSparse).  This can lead to problems in calling code that expects
  `find_package` result variables (e.g., `_FOUND`) to follow a certain
  pattern.
Call Stack (most recent call first):
  cmake/FindSuiteSparse.cmake:89 (find_package_handle_standard_args)
  numerics/CMakeLists.txt:180 (find_package)
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Found SuiteSparse_CXSparse: /usr/include
CMake Warning (dev) at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:426 (message):
  The package name passed to `find_package_handle_standard_args`
  (SuiteSparse_LDL) does not match the name of the calling package
  (SuiteSparse).  This can lead to problems in calling code that expects
  `find_package` result variables (e.g., `_FOUND`) to follow a certain
  pattern.
Call Stack (most recent call first):
  cmake/FindSuiteSparse.cmake:89 (find_package_handle_standard_args)
  numerics/CMakeLists.txt:186 (find_package)
This warning is for project developers.  Use -Wno-dev to suppress it.

I did not have LDL installed on my system: cmake did not stop there, but then I had the following error (the Cmake Error was for a lot more target, just showing one here)
-- Configuring done
CMake Error at /usr/share/cmake/Modules/UseSWIG.cmake:783 (add_library):
  Target "_numerics" links to target "SuiteSparse::LDL" but the target was
  not found.  Perhaps a find_package() call is missing for an IMPORTED
  target, or an ALIAS target is missing?
Call Stack (most recent call first):
  cmake/swig_python_tools.cmake:86 (swig_add_library)
  cmake/swig_python_tools.cmake:205 (add_siconos_swig_sub_module)
  numerics/swig/CMakeLists.txt:52 (swig_module_setup)

It might be worthwhile looking at the Cmake warning and/or make the build fail of some suitesparse component are not found

Curious.  If you do not have LDL from Suitesparse on your system, cmake should find it in externals as for csparse. Do you use fclib in ?

Curious.  If you do not have LDL from Suitesparse on your system, cmake should find it in externals as for csparse. Do you use fclib in ?

No I didn't enable FCLIB.

No I didn't enable FCLIB.


Passes::GetDownsamplingBracket is wildly different from the ISO specification

I've noticed this during the independent reimplementation efforts. As specified, minshift is determined to be downsample[n] if there is an index n such that last_pass[n] is equal to the pass index, otherwise it's set to maxshift. In the current implementation though, n is the largest index such that last_pass[n] is no less than the pass index, or 0 if there's no such n.
Theoretically, and with my limited understanding of the modular mode, this can result in the following problems:

Some modular group data will be placed in wrong passes. By itself they will decode just fine (as the decoder and encoder have the exactly same bug), but it degrades the progressive decoding performance.
Some modular group data will be omitted (concrete example: num_passes = 2, num_ds = 1, downsample[0] = 2, last_pass[0] = 1). I believe the bitstream still decodes, but the decoded image would no longer match the original.
Some modular group data will be duplicated (concrete example: num_passes = 3, num_ds = 2, downsample[0..1] = [4, 2], last_pass[0..1] = [1, 0]; keep in mind that the bitstream has zero guarantee about the sortedness of these arrays). I believe the bitstream still decodes, but the same channel might get painted multiple times so again the decoded image would no longer match the original.

Thankfully the current libjxl only emits five combinations of Passes, which greatly limit the issue's extent. The following is a summary:

Case
A
B
C
D
E

--progressive_ac
No
Yes
Yes
Yes
Yes

--saliency_num_progressive_steps=
-
1
2
3
4¹

num_passes
1
2
3
4
2

downsample[0 .. num_ds-1]
-
4
4, 2
4, 2
2

last_pass[0 .. num_ds-1]
-
0
0, 1
0, 1
0

[minshift, maxshift) (spec)
[0,3)
[2,3), [0,2)
[2,3), [1,2), [0,1)
[2,3), [1,2), [1,1), [0,1)
[1,3), [0,1)

[minshift, maxshift) (libjxl)²
[0,3)
[2,3), [0,2)
[1,3), [1,1), [0,1)
[1,3), [1,1), [0,1), [0,0)
[1,3), [0,1)

Also requires a non-zero --saliency_threshold, otherwise it's same to the case D.
libjxl actually uses an inclusive maxshift, which is converted to an exclusive bound in this table.

So the normal case is just fine; even the ordinary progressive option -p is actually --qprogressive_ac and not affected by this bug. Even in rare cases where --progressive_ac --saliency_num_progressive_steps=2/3 are used some modular group data is just misplaced, but they will be technically an invalid bitstream under the specification.
I've written a simple Python script to enumerate all cases where the specification and libjxl disagrees.

I should note that the specification is ambiguous when there are multiple n such that last_pass[n] is equal to the pass index, so if we are going to fix libjxl to match the specification, we also need to clarify the specification as well ;-)

Thanks for reporting this!
Note for future me: looking at the table and cjxl code, the only way to produce weird values for shifts is to pass a non-default --saliency_num_progressive_steps, which should be rare at best.

This seems pretty reasonable to me.

Closing, feel free to re-open if there is still a need.


Add dynamic buffer support

I ran performance benchmarks against Alacritty and was able to confirm that this does not impact performance.
A test with the clipboard escape also allowed me to confirm, that the downstream bug https://github.com/jwilm/alacritty/issues/1002 is indeed fixed by this.


Can not access to datasets

Thanks for your wonderful work, the datasets you provide is not accessable in Google Drive.

Hi, thank you for your interest in our work, I have changed the permission of the shared datasets, so you can download them now.


Change Default TileMap Custom Transform to match default Square mode Cell Size

I think it's unintuitive that the TileMap node default value for the  Custom Transform property is Transform2D( 1, 0, 0, 1, 0, 0 ), and that it should match the Size default of Vector2(64,64) by having the default value of Transform2D( 64, 0, 0, 64, 0, 0 ).
Usage Reasons:

It is a large performance hit if you switch from mode Square to Custom without changing the default Custom Transform if you have a tileset loaded

This crashed godot the first time I tried using the custom transform due to this
I've seen multiple posts about performance with TileMap that can be attributed to this

A 1px by 1px TileMap doesn't make sense for most users

Aesthetic Reasons:

It helps new users understand how the transforms works by associating values with similar usage

There are the changes you are expecting as default?

Yep


request to get raw file is not working for filename having dot

Request to get raw file is not working when there is dot in filename.
Eg-
Filename without dot- Working fine
https://gitlab.com/api/v3/projects/3045354/repository/files/Gemfile/raw?ref=master
Filename with dot- Throwing error {"message":"404 File Not Found"}
https://gitlab.com/api/v3/projects/3045354/repository/files/Gemfile.lock/raw?ref=master
Encoded form-
https://gitlab.com/api/v3/projects/3045354/repository/files/Gemfile.lock/raw?ref=master

I apologize for not having read through this better.  You may be looking to file a bug against GitlabHQ not the Gitlab ruby gem that wraps the Gitlab API

I believe this is a bug in the gem. In fact in client.rb you have:
def url_encode(s)
ERB::Util.url_encode(s)
end
and erb Util won't convert the dot into %2E, but URI.encode(s, /\W/) will.
If you try to call file_contents with an already encoded string it'll double encode it so that won't work either.
I will be submitting a PR for this fix.

It seems its fixed now. File name with dot(.) working fine now


Automatically trigger e2e on AWS

This PR is the next step of replacing the e2e job that runs on a GitHub hosted
runner in favor of running it on AWS. These changes get the job running
automatically just like the original e2e, but does not block merges on it for
now. We can let this run in parallel for a short time to make sure it's stable
before switching over to it completely.
c7b57c0 e2e: Change t4-x1 workflow to report status in checks
fb7b05a e2e: Auto launch e2e-nvidia-t4-x1 workflow
b084bbf docs: Explain how we auto-run AWS e2e jobs
commit c7b57c006e786e5ab3d5fe5801bc4bc672443f1b
Author: Russell Bryant<EMAIL_ADDRESS>Date:   Tue Jul 9 16:46:13 2024 -0400
e2e: Change t4-x1 workflow to report status in checks

The `e2e-nvidia-t4-x1` workflow replicates the testing we do on every
PR using github's built-in GPU worker. This version that runs on AWS
costs much less to run.

This commit changes this workflow to report its status to PRs as a
status check instead of PR comments. This will make it show up in the
same place as any other CI job.

Signed-off-by: Russell Bryant<EMAIL_ADDRESS>
commit fb7b05a9ecd464c4d2a7c56721d045ee2d49b471
Author: Russell Bryant<EMAIL_ADDRESS>Date:   Tue Jul 9 17:32:07 2024 -0400
e2e: Auto launch e2e-nvidia-t4-x1 workflow

Automatically launch the e2e-nvidia-t4-x1 workflow that runs on an
AWS instance for PRs and pushes to main or release branches. This can
eventually replace the `e2e` that runs on every PR and runs on a
GitHob hosted runner.

For now I would like to have both versions run. This one is not
included in mergify configuration, so it will not block merges for
now. Once we deem this stable enough, we can drop the original e2e job
in favor of this one.

Signed-off-by: Russell Bryant<EMAIL_ADDRESS>
commit b084bbf14e8af4a8f0268e3d090ebfcf7e4cd112
Author: Russell Bryant<EMAIL_ADDRESS>Date:   Tue Jul 9 21:01:04 2024 -0400
docs: Explain how we auto-run AWS e2e jobs

Automatically running these e2e jobs on AWS is a bit convoluted and
warrants further explanation. The doc tries to lay out the different
parts involved.

Signed-off-by: Russell Bryant<EMAIL_ADDRESS>

I'm not totally sure why this isn't working. I think this permission must not be accessible in a PR that's modifying the trigger workflow. I did have this working on a personal repo before proposing here ... but it was running after having been applied to main already

to whoever considers placing the 2nd approval on here, can you ping me to make sure I'm available to respond quickly to what happens when it starts running against every PR?  You can also place the hold label before giving the 2nd approval. That way I can let it merge when I'm ready to focus on monitoring and response

to whoever considers placing the 2nd approval on here, can you ping me to make sure I'm available to respond quickly to what happens when it starts running against every PR? You can also place the hold label before giving the 2nd approval. That way I can let it merge when I'm ready to focus on monitoring and response

I went ahead added hold myself so I can control the merge timing.

I had a conversation with @n1hility offline about these changes. He pointed me to another event type that can trigger workflows.  https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request_target
This might be a better and simpler solution to how this trigger works, so I'm going to look into that next.

Reapproving after code updates


Additional changes to Hypothetical Budget, COS, ROAS Change calculator

The performance of the design is much better now that we've moved to Javascript, but we need to clean up the look and feel and add some form validation.

Also, in general, we'd like to come up with some sort of hover tool tip structure for defining terms.

Here is another change that we'd like to make.


[docs] Demo VirtualElementPopper crashes

[x] I have searched for similar issues in this repository and believe that this is not a duplicate.

Steps to Reproduce

Visit https://mui.com/material-ui/react-popper/#virtual-element
??
demo VirtualElementPopper crashes

Your Environment

Tech
Version

MUI
v5.6.2

netlify deploy
https://625d8dace3f575000853f781--material-ui-docs.netlify.app

Browser
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4896.127 Safari/537.36

I was just randomly checking the virtual element in mui popper while I encountered this issue.

I can't reproduce it. @bnays Do you still experience the issue?


CIF Admin Features

Given no issues/tickets have ever been added to this EPIC, we could close and re-open if there is a need/value in the future.

Talked to Pierre and we are good to close.


Updating Onramp Demo App - Adding More Use Cases

Updating onramp demo app to include the following use cases:

Generate onramp url with networks other than ethereum
Generate buy config, buy options, and buy quote
Generate one click buy link using parameters from buy quote response and request
Buy config / options / quote / url generation all linked in singular flow

Areas of Importance:

API folder represents a backend that calls the onramp API endpoints (secure-token, buy-options, buy-config, buy-quote)

Components folder houses all tabbed views ->

BuyQuoteBox contains the entire page / flow for the 'Onramp Aggregator URL tab'

BuyConfigBox contains the section for generating a buy configuration on the aggregator page

SecureTokenBox contains the section for generating an onramp view on both tabs

utils folder -> contains wrappers around the frontend query calls, defined types for API responses / requestes, and helper functions as needed

Sanity Checks:

app was tested during Onramp Bug Bash
Make sure ->
On the first tab, where you can generate a URL, ensure that URLs are only generated for valid Wallet Addresses and for a selected blockchain network that can support this Address
On second tab -> ensure section does not show until previous section is completed. Ensure proper output for OCB link that takes you to a page with the selected assets, network, and payment type

Other nitpicks:

make sure loading state does not persist if an error occurs
proper handling of errors -> incorrect inputs or nonexistent inputs (invalid wallet address, improper payment amount) result in the right errors

Review Error for zack-winchell-cb @ 2024-06-27 16:15:11 UTC
User must have write permissions to review


Saving a fs.watch()'d rapidly empties source file, but only in VSCode?

VSCode Version: 1.36.1
OS Version: Windows 10 Pro x64

Steps to Reproduce:

Create 2 files, index.js and source.txt
Edit them like so:

// Index.js
const fs = require('fs')
const sourcePath = './source.txt'
const targetPath = 'target.txt'

fs.watch(sourcePath, (e) => {
  fs.copyFile(sourcePath, targetPath, (err) => {
    console.log('error?', err)
  })
})

// source.txt
foobarbaz // any content will do

Start node index.js
Edit source.txt and verify target.txt is created
Rapidly save (~5 times per second, or as fast as you can) source.txt (no need to edit in between)
After 2-5 saves source.txt is cleared of all content, and Failed to save 'source.txt': Unable to write file (Unknown (FileSystemError): Error: EBUSY: resource busy or locked, appear in VSCode (and sometimes in the above started node process log)

Does this issue occur when all extensions are disabled?: Yes
In essence the copy operation should be done by the node process, so it's unclear why VSCode has trouble with reading/editing the file when other editors do not.
My guess is that VSCode cannot read the source file, clears the editor, and resaving is somehow impossible, as trying to keep saving the file keeps resulting in the same error.
This doesn't happen with another editor, for example with notepad. Replicated on colleague's PC (same OS).
Even though the issue would seemingly lie in the started node process, this only manifests in VSCode (at least on Windows), and hence I'm filing this issue.

@renotoaster this error is not coming from VSCode but from node.js so I would suggest you try to reproduce with a standalone node.js sample. E.g. add code that simulates the writing that VSCode does.
Btw I think it is a known issue that watching on Windows locks file resources. At least for folders that is true.

I did, with the notepad version. I'm not sure how to simulate "how VSCode writes it" to get enough understanding if there's something VSCode can do to mitigate this (it can't really override the OS behaviour).
I acknowledged beforehand that this might not be something VSCode can affect even if it manifests in it (as it's the node process that does the actual (b)locking), so do close/keep this open at your discression.

@renotoaster you can start with fs.writeFile to fill the file. Or fs.createReadStream(source).pipe(fs.createWriteStream(target)).

This issue seems to originate from an upstream component and is not something VSCode can fix by making a change to the code. As such, I will go ahead and close it. If you can identify the component that is causing the issue, please report it upstream:

for UI, OS integration: https://github.com/electron/electron
for Rendering: https://bugs.chromium.org/p/chromium/issues/list
for file IO: https://github.com/nodejs/node

Thanks for understanding.


Update service-govus-overview.md

@kfollis Please create pull request - Cyrus

@Hikmer : Thanks for your contribution! The author(s) have been notified to review your proposed change.


🍒 Cherry pick PR #4059 to staging 🍒

🍒 Cherry pick https://github.com/Expensify/Expensify.cash/pull/4059 to staging 🍒

🚀 Deployed to staging         in version: 1.0.78-1🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production         in version: 1.0.79-4🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Regression in jsonpath matching

Which version of WireMock you're using
works with 2.27.1
doesn't work with 2.28.0
Reproducing
Create such a json mapping and upload it to WireMock
{
  "id" : "eef52385-481f-4fb3-813d-ee657b437e9d",
  "request" : {
    "url" : "/api/user",
    "method" : "POST",
    "headers" : {
      "Content-Type" : {
        "matches" : "application/json.*"
      }
    },
    "bodyPatterns" : [ {
      "matchesJsonPath"<EMAIL_ADDRESS>=~ /([a-zA-Z0-9]+)?/)]"
    }, {
      "matchesJsonPath"<EMAIL_ADDRESS>=~ /([a-zA-Z0-9]+)?/)]"
    } ]
  },
  "response" : {
    "status" : 201,
  },
  "uuid" : "eef52385-481f-4fb3-813d-ee657b437e9d"
}

Send such a POST request to /api/user. Content-Type is application/json and the body
{ "foo" : null, "name": "" }

Attaching a project that reproduces the issue. Just run ./mvnw verify - the build will fail. Run ./mvnw verify -Dwiremock-jre8-standalone.version=2.27.1 and the build will pass.

jsonpath_regression.zip

This looks like it's been caused by a change to the JSONPath parser in the 2.4.0 -> 2.5.0 upgrade. The JSONPath expression isn't being parsed any more and an exception is being thrown (which WireMock only reports if you've got verbose logging turned on).
The previous behaviour looks wrong to me though, for a couple of reasons:

If you're requiring an address field to be present and not sending it, that ought to be a non-match.
Your name regex expects there to be at least one character, so sending an empty name field also ought to cause a non-match.

Removing the capture group brackets from the regex and sending a non-empty name and address makes things work again, so:
{
  "request" : {
    "url" : "/api/user",
    "method" : "POST",
    "headers" : {
      "Content-Type" : {
        "matches" : "application/json.*"
      }
    },
    "bodyPatterns" : [ {
      "matchesJsonPath"<EMAIL_ADDRESS>=~ /[a-zA-Z0-9]+?/)]"
    }, {
      "matchesJsonPath"<EMAIL_ADDRESS>=~ /[a-zA-Z0-9]+?/)]"
    } ]
  },
  "response" : {
    "status" : 201
  }
}

Will match
{ "foo" : null, "name": "a", "address": "b" }

Related json-path issue: https://github.com/json-path/JsonPath/issues/708

And also https://github.com/json-path/JsonPath/issues/692

Fixed in bbd7b2489d515f12ffd69beee3eda78c0bbe3b05


I can use this method to achieve

给html元素添加一个css3属性
touch-action: none;

即可解决这个问题
Originally posted by @xiaoxiongzi in https://github.com/surmon-china/vue-awesome-swiper/issues/423#issuecomment-432687839

I use this method to achieve!


Decouple Bridge from gRPC service

The Stargate v2 Bridge module is currently constructed as an extension of the gRPC module

The bridge proto files are part of the grpc-protos module
The bridge implementation reuses classes from the gRPC implementation

This coupling has had some benefits in terms of enabling us to bootstrap the bridge quickly, but also some undesirable side effects:

on multiple occasions we have had to consider carefully changes we want to make to the bridge that actually require changes to classes in the gRPC module, potentially changing behavior for public API users
under #1763 we're potentially making changes to the gRPC protos for behavior we want to add to the bridge. Even though these would be non-breaking changes to our public API, they are still changes, and we'd need to consider downstream impacts on documentation, etc.
we've had at least one defect that is arguably caused by bridge changes impacting gRPC behavior in downstream projects (see https://github.com/riptano/c2/issues/453 where the bridge appears to be impacting gRPC metrics reporting)

We should consider making a clean break between these two modules with separate protos and separate implementations.

I am just afraid now how can we revert anything in the #1763 once it becomes the public API?

I am just afraid now how can we revert anything in the #1763 once it becomes the public API?
EDIT: OK, I forgot this is in V2 branch.

Agree, while v2 is still Alpha I think we are ok, but we do need to resolve sooner rather than later.

I've started working on this. No blockers, but as expected almost all of the grpc module will now be duplicated in bridge.
Also I have to move the generated proto code for the bridge to a different package (technically because the testing module uses both, but also it makes sense conceptually). So all of v2 code that uses the bridge will be impacted.

@olim7t Can this be closed now?


Does react-spring uses FLIP animations?

Just found out that react-posed uses so called FLIP animations [1] for performance reasons. You can turn them off because it can create glitches (check this issue: https://github.com/Popmotion/popmotion/issues/672).
So, ...

Does react-spring also uses FLIP? I guess not, because the animation from issue above works flawlessly with react-spring, right?
Is FLIP worth, so does it really helps re performance or are there smarter ways?

[1] https://aerotwist.com/blog/flip-your-animations/

In your case all you need to animate is opacity, there's nothing that would make it faster unless you set classNames raw in css.
As for flip in general, i'm kinda opposed to having too much magic in the lib. Height: "auto" is probably the most it'll do. Magic is great, in a demo, but then you run into edge cases. I would like to go the explicit route with react-spring, in the end you should know what you do and how it affects your views, without surprises. I guess it's a preference ...

PS. That doesn't mean i'd ignore a proposal if there's one. If you have ideas and if it warrants a new primitive, shoot - we'll always listen.

Hey @drcmda, sorry for my late response and I agree with you: It's too much magic, I don't need such a feature. Just wanted to know your opinion on this topic. I'll close this now and if anyone wants FLIP they can open a new issue.

@desmap we wrote a tiny library on react-spring to have FLIP animations. Just sharing: react-spring-flip


Multiple Feeds Loop with Success Function

Hi there, I'm using a for loop in order to run multiple feeds as follows:
var galImages = document.querySelectorAll('#instafeed li').length;
for(var i=0; i < galImages; i++) {
    var feed = new Instafeed({
	get: 'user',
	userId: '5489104071',
	accessToken: '5489104071.d4ba55e.7f902a2487c247bf9764651b70599536',
	template: '',
	limit: (i*2)+2,
	resolution: 'standard_resolution',
	target: 'insta-gal-'+(i+1),
	success: function(data){
                console.log(i); // returns 9 9 9 9 9 9 9 9 9
		images = data.data;
                var spliceNum = i*2;
		images.splice(0,spliceNum);
	}
    });
    feed.run();
}

My issue is, I need to use the i variable in the success function, but I'm not sure how I can do this. If I console.log i within the success function, instead of returning 1,2,3,4,5,6,7,8,9 it just returns 9,9,9,9,9,9,9,9,9.
Can anyone help?

Hey @SteGreig,
This is happening because the success callback is run asynchronously to your for loop - it runs when the remote call to instagram completes, by which time the for loop has continued, incremented the value of i and completed.
What you need is a way to provide the value of i at the time the success callback was created to the body of the function. There are different ways to do that, but one simple one would be to store that value on the target element itself, and then retrieve it when the callback runs, something like this:
var galImages = document.querySelectorAll('#instafeed li').length;
for(var i=0; i < galImages; i++) {
  var target = document.querySelector('#insta-gal-'+(i+1));

  // Store the value of i on a data attribute on the target
  target.setAttribute('data-instafeed-set', i);

  var feed = new Instafeed({
    	get: 'user',
    	userId: '5489104071',
    	accessToken: '5489104071.d4ba55e.7f902a2487c247bf9764651b70599536',
    	template: '',
    	limit: (i*2)+2,
    	resolution: 'standard_resolution',
    	target: target, //Set the target to the DOM node directly
    	success: function(data){
        var i = parseInt(this.options.target.getAttribute('data-instafeed-set'));
        console.log(i); //Yields 0, 1, 2 ...
    		images = data.data;
        var spliceNum = i*2;
    		images.splice(0,spliceNum);
    	}
    });

  feed.run();
}

I haven't actually tested that (and I suspect there might be more efficient ways to approach what you're doing) but it should do the trick.

Hi @benjamin-hull
I got this to work with success callback, but this didn't seem to work with the filter callback.
filter: function (image) {
            var i = parseInt(this.options.target.getAttribute('data-instafeed-set'));
            console.log(i);
            return image.tags.indexOf(global_tag[i]) >= 0;
        }

I got the following error instead:
Uncaught TypeError: Cannot read property 'target' of undefined


Updates copyright to GraphQL Foundation

Yes! That was an accident! Thank you for the careful read and fix
On Thu, Nov 7, 2019 at 3:01 AM Erik Wittern<EMAIL_ADDRESS>wrote:

@ErikWittern commented on this pull request.
In c/GraphQLAstVisitor.cpp
https://github.com/graphql/libgraphqlparser/pull/93#discussion_r343591552
:

@@ -50,6 +50,6 @@ void graphql_node_visit(const struct GraphQLAstNode *node,
{
CVisitorBridge visitor(callbacks, userData);
if (node) {

reinterpret_cast<const facebook::graphql::ast::Node *>(node)->accept(&visitor);

reinterpret_cast<const graphql::ast::Node *>(node)->accept(&visitor);

Fixed in #95 https://github.com/graphql/libgraphqlparser/pull/95.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/graphql/libgraphqlparser/pull/93?email_source=notifications&email_token=AAAMHUTUZNFFL56YJK2JHNDQSPYQHA5CNFSM4JKBYWJKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCKV7THY#discussion_r343591552,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAMHUXLC4DALSSO4OLC5ELQSPYQHANCNFSM4JKBYWJA
.

--
Lee Byron


Generated files

Is there a way to access files it said it created?

it said it created

Does this refer to the output in the task results?
As a tool, we do not have the ability to output files, so files are never generated.


[lint] values.yaml: file does not exist

Hi,
Either the documentation is needs to be corrected or this bug with helm lint command needs to be resolved. At least if the flag is explicitly given by the user, this info is pointless.
As you can see below, description for the -f, --values flag for lint and template commands are exactly the same. However, the lint command doesn't work the way template does.
Thanks

-f, --values strings           specify values in a YAML file or a URL (can specify multiple)

$ helm lint .helm/app --values .helm/app/values-dev.yaml
==> Linting .helm/app
[INFO] values.yaml: file does not exist

1 chart(s) linted, 0 chart(s) failed

-f, --values strings               specify values in a YAML file or a URL (can specify multiple)

$ helm template .helm/app --values .helm/app/values-dev.yaml
// This works perfectly fine

Environment
$ helm version
version.BuildInfo{Version:"v3.8.0", GitCommit:"d14138609b01886f544b2025f5000351c9eb092e", GoVersion:"go1.17.6"}

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GoVersion:"go1.15.3", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.2",GoVersion:"go1.15", Platform:"linux/amd64"}

$ minikube version
minikube version: v1.14.2

Is there a values.yaml file next to your Chart.yaml?

No because I have specific multiple ones with different names for the same purpose.

Try placing an empty values.yaml file in your chart.
As per the Chart File Structure, a default values.yaml is required IIRC.

It feels like a hack to be fair :)


 I only tested kill() and setblock() besides say() but they both appeared to compile correctly.

The reason is that your if doesn't produce any command while sandstone expects commands. Probably should throw an error though.

Fixed in latest version v1.13.3.


Change format for list of task in Daily Note

In this feature request  you added possibility to list tasks from Full Calendar in current daily note. It's great but it will list the tasks in following format

[ ] Test [startTime:: 11:00]  [endTime:: 12:00]

To be able to write and read such list more easily it would be great to use just format like

[ ] 09:30 - 10:00 Setup for work
[ ] 10:00 - 11:00 Create new notes for #article review

It could be potentially used then also in Day Planner plugin that works with this format.
After adding a new item to calendar the output list is also not correctly ordered. The new task is displayed as the first although it is added as the last in the day.
Thanks

Hopping onto this issue to say that a custom format would also allow us to better combine full-calendar with Obsidian tasks.


Add example for setting log level on New() logger

closes #153

Thanks @GuyMorgan and sorry for the long delay here. I think this is fairly straightforward to anyone reading the docs, and the README covers the important basics. So I'll close for now. Feel free to reopen if you feel strongly about.t


fix issue providers like Dropbox not show in Android

The problem is that, in the resulting menu, I get far less content providers than I expected. Only Google Drive and Downloads. Others, like Dropbox, Solid Explorer,... are not show.

This change is already part of v3.

I hope you will release v3 earlier to me use main branch instead fork branch.

Since it's fixed in v3 branch, can this be clossed?


AssertionError quantizing miqu-1-70b-sf

I am unable to quantize the miqu-1-70b-sf model.  Running the standard quantization for other LLaMA2 models works fine but fails for miqu-1-70b-sf with the below stack.  I tested with current main branch as well as the 0.2.0 branch with the same error:
Loading checkpoint shards: 100%|████████████████████████████████████████████████████████████████████| 29/29 [00:01<00:00, 21.69it/s]
Quantizing model /models/models/miqu-1-70b-sf to /models/models/miqu-1-70b-sf-AWQ
/home/ubuntu/miniconda3/envs/exl2/lib/python3.10/site-packages/huggingface_hub/repocard.py:105: UserWarning: Repo card metadata block was not found. Setting CardData to empty.
  warnings.warn("Repo card metadata block was not found. Setting CardData to empty.")
AWQ:   0%|                                                                                | 0/80 [00:03<?, ?it/s]
Traceback (most recent call last):
  File "/home/ubuntu/git/exllamav2/./quant-model.py", line 915, in <module>
    main()
  File "/home/ubuntu/git/exllamav2/./quant-model.py", line 761, in main
    create_awq(model_dir, is_mixtral)
  File "/home/ubuntu/git/exllamav2/./quant-model.py", line 516, in create_awq
    model.quantize(
  File "/home/ubuntu/miniconda3/envs/exl2/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
  File "/home/ubuntu/git/AutoAWQ/awq/models/base.py", line 117, in quantize
    self.quantizer.quantize()
  File "/home/ubuntu/git/AutoAWQ/awq/quantize/quantizer.py", line 151, in quantize
    scales_list = [
  File "/home/ubuntu/git/AutoAWQ/awq/quantize/quantizer.py", line 152, in <listcomp>
    self._search_best_scale(self.modules[i], **layer)
  File "/home/ubuntu/miniconda3/envs/exl2/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
  File "/home/ubuntu/git/AutoAWQ/awq/quantize/quantizer.py", line 262, in _search_best_scale
    best_scales = self._compute_best_scale(
  File "/home/ubuntu/git/AutoAWQ/awq/quantize/quantizer.py", line 319, in _compute_best_scale
    self.pseudo_quantize_tensor(fc.weight.data)[0] / scales_view
  File "/home/ubuntu/git/AutoAWQ/awq/quantize/quantizer.py", line 64, in pseudo_quantize_tensor
    assert torch.isnan(w).sum() == 0
AssertionError

+1
I am having the same experience. Would be great to get this fixed.

This usually indicates that the weights are atypical and that some of them are filled with null values. Probably due to errors in conversion

I see! This was from a model that was converted from GGUF to F16, and you’re possibly right with errors in conversion.
Would you be able to take a look and see if there’s anything that can be done?

Well, I see others have tried to convert from GGUF to FP16, but it seems there are errors in that conversion. Perhaps ggerganov can highlight exactly how a correct conversion should be implemented since I am no expert in how GGUF works

I know that to create the EXL2 format the tolerances had to be relaxed, is it possible that the tolerances might just need to be reduced to get a successful quant?

I know that to create the EXL2 format the tolerances had to be relaxed, is it possible that the tolerances might just need to be reduced to get a successful quant?

This is not currently possible AFAIK - the problem is that the weights have NaN values that cannot be scaled. This is not something I am looking to fix in the short term, but I certainly welcome the community to investigate this problem.

I see! Is there any interactive viewer than you know of for different file
formats like FP16, GGUF, etc that I can use to investigate? More than happy
to work on this, just very new to the scene.
On Sun 11 Feb 2024 at 11:42, Casper @.***> wrote:

I know that to create the EXL2 format the tolerances had to be relaxed, is
it possible that the tolerances might just need to be reduced to get a
successful quant?
This is not currently possible AFAIK - the problem is that the weights
have NaN values that cannot be scaled. This is not something I am looking
to fix in the short term, but I certainly welcome the community to
investigate this problem.
—
Reply to this email directly, view it on GitHub
https://github.com/casper-hansen/AutoAWQ/issues/335#issuecomment-1937622523,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJIIID6WBKNFEJSZ264VV3YTCVBJAVCNFSM6AAAAABDCXHNNSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZXGYZDENJSGM
.
You are receiving this because you commented.Message ID:
@.***>

There are viewers like Netron, for example. I will close this issue as it's not planned to support model's that fail the assertions.

not planned to support model's that fail the assertions

Maybe it's the source code that is failing the model.


Remove some occurrences of num_eval_samples

Description of changes: some changes following #421
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #436 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #436   +/-   ##
=======================================
  Coverage   82.23%   82.23%
=======================================
  Files         147      147
  Lines        8555     8555
=======================================
  Hits         7035     7035
  Misses       1520     1520

Impacted Files
Coverage Δ

src/gluonts/model/forecast_generator.py
67.03% <ø> (ø)
:arrow_up:

src/gluonts/model/simple_feedforward/_estimator.py
100% <100%> (ø)
:arrow_up:


Fix python 3 compatibility

@cedricmessiant @mauritsvanrees as this seems to be already fixed, closing this one. Reopen if this is wrong.

And it is in release 2.0 from last week. Nice. Thanks.

Thanks !


Add support for running contracts with range_check builtin

added bitwise builtin as well

Added pedersen and output builtins as well


Feature: SLIM/BUILD - An ability to keep the linux distribution metadata in the minified image ( --include-distro-metadata flag)

Need a way to indicate that we don't want to remove the linux distribution metadata in the output image for the slim (aka build) command. This metadata is located in the /etc/os-release file. It is possible to keep that file by using the generic --include-path flag. The goal here is to introduce a custom --include* flag (--include-distro-metadata) that's a shortcut for the --include-path without having to specify the /etc/os-release file explicitly.
Unlike other custom --include* flags the custom --include-distro-metadata flag doesn't need to be propagated to the sensor. Instead, it's enough to "convert" --include-distro-metadata to a regular --include-path value internally in the main app when handling the slim command.

initial version of the --include-distro-info flag is now available (might need enhancements).


Specific Llamafiles rather than -m model

Thanks for making this. One suggestion is to modify the Dockerfile so that at build time you are passing an argument for a specific llamafile. That way you don't have the extra step of needing to specify the gguf files and mounting them in a volume. Maybe I'm just missing the point, but using the executable with gguf files as an argument feels like it's missing some of the value of llamafile just being a file you run. Would love your thoughts on this.

Thank you for the suggestion! To address your use case, if you’d like to specify a model at build time, I recommend creating your own Dockerfile based on mine (FROM iverly/llamafile-docker:latest). You can add the required steps to include the model file by using:
COPY /path-to-your-model /container-path-to-model
# or
RUN wget <url-to-model> -O /container-path-to-model

Then, modify the command by overriding the CMD line like this:
CMD ["--server", "--host", "<IP_ADDRESS>", "-m", "/container-path-to-model"]

Let me know if you have further questions!

Hey! Thanks for getting back to this comment so quickly. I forked and will do just that.


about producer's next(n) method

next(n) will be parked forever when n is bigger than bufferSize property

Thank you.


TCP address reuse does not work on linux

3.0.4 introduced "[Server] The TCP address is now reused when starting which should prevent "port in used" error when restarting."
This throws exception on linux:

System.Net.Sockets.SocketException : Permission denied
Stack Trace:
at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName)
at System.Net.Sockets.Socket.SetSocketOption(SocketOptionLevel optionLevel, SocketOptionName optionName, Int32 optionValue, Boolean silent)
at System.Net.Sockets.Socket.SetSocketOption(SocketOptionLevel optionLevel, SocketOptionName optionName, Int32 optionValue)
at MQTTnet.Implementations.MqttTcpServerListener.Start(Boolean treatErrorsAsWarning, CancellationToken cancellationToken)
at MQTTnet.Implementations.MqttTcpServerAdapter.RegisterListeners(MqttServerTcpEndpointBaseOptions options, X509Certificate2 tlsCertificate, CancellationToken cancellationToken)
at MQTTnet.Implementations.MqttTcpServerAdapter.StartAsync(IMqttServerOptions options)
at MQTTnet.Server.MqttServer.StartAsync(IMqttServerOptions options)

Does it also fail when using an admin account?

Yes. sudo dotnet test runs ok. But it should also run in Azure DevOps CI without admin account.

Ok you are right. I just want to understand that issue first. I will move that setting to the options instead.

I released 3.0.5. The setting is now moved to the options and off by default. So when this is needed/possible then it should be activated.

I have what appears to be the same issue when deploying container in Azure AKS Kubernetes service, but from this conversation  I can't quite understand what's happening. I have version 3.0.5.
Could you explain a bit more what is this option?

@chkr1011 This is something you need to explain.

@VladimirAkopyan I also have no clear understanding. I just implemented that based on a recommendation from another user.
But what I found is that a socket is still "open" when the application is closed. This is related to the clients which are still connected and the OS will keep the socket "alive" for some time to let the clients disconnect properly (sending FIN, ACK whatever TCP stuff). When restarting the MQTT server in a short time the socket is still "in use" by the OS waiting for disconnect ACK of the clients. Here the setting comes in and requests to the OS that we want to get the already existing socket back. The drawback is that we might get some data on that socket. But this is not a problem because we are hosting the same MQTT server on that port. If the socket was used by another application it might be not a good idea to take over that existing socket. Then the exception is welcome instead.
On linux this takeover of the socket requires admin rights.
I hope that is more or less correct. I someone else has more details please share.

@chkr1011 I also had this problem,so I still used version 3.0.2.

exception:
Unhandled Exception: System.Net.Sockets.SocketException: Permission denied
   at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName)
   at System.Net.Sockets.Socket.SetSocketOption(SocketOptionLevel optionLevel, SocketOptionName optionName, Int32 optionValue, Boolean silent)
   at System.Net.Sockets.Socket.SetSocketOption(SocketOptionLevel optionLevel, SocketOptionName optionName, Int32 optionValue)
   at MQTTnet.Implementations.MqttTcpServerListener.Start(Boolean treatErrorsAsWarning, CancellationToken cancellationToken)
   at MQTTnet.Implementations.MqttTcpServerAdapter.RegisterListeners(MqttServerTcpEndpointBaseOptions options, X509Certificate2 tlsCertificate, CancellationToken cancellationToken)
   at MQTTnet.Implementations.MqttTcpServerAdapter.StartAsync(IMqttServerOptions options)
   at MQTTnet.Server.MqttServer.StartAsync(IMqttServerOptions options)
   at Nito.AsyncEx.Synchronous.TaskExtensions.WaitAndUnwrapException(Task task)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
   at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot)
--- End of stack trace from previous location where exception was thrown ---
   at Nito.AsyncEx.Synchronous.TaskExtensions.WaitAndUnwrapException(Task task)
   at Nito.AsyncEx.AsyncContext.Run(Func`1 action)

code:
        public static void Main(string[] args)
        {
            //CreateWebHostBuilder(args).Build().Run();
            var mqttOptionBuilder = new MqttServerOptionsBuilder()
                .WithConnectionBacklog(100)
                .WithDefaultEndpointBoundIPAddress(IPAddress.Parse("<IP_ADDRESS>"))
                .WithDefaultEndpointPort(35001);

            var _mqttServer = new MqttFactory().CreateMqttServer();
            AsyncHelper.RunSync(()=>_mqttServer.StartAsync(mqttOptionBuilder.Build()));
        }

My operating system is centos 7.x,I can reproduce it in the Docker container.

You have to upgrade to 3.0.5. The fix is only there.


Add a unit test for python minesweeper

I think should add this test.
+-----+
    * |
+-----+

this is invalid

Thanks, @RryLee!
@betegelse You implemented this exercise originally; would you have time to review this change?

Sure, give me a couple of days

Do you need any help?

@behrtam I dont't see the offical solution, just completed it and found this flaw

So the actual example implementation already works for this proposed new test case. The existing test case test_faulty_border does basically the same check, just with a different incorrect character. That's why I don't see any reason to add this.


Flutter Firebase Codelab: google-services plugin could not detect any version for com.google.android.gms

Hi guys,
I'm trying the new flutter-firebase codelab but when I run my app with propers plugin imported ( step 6 ) here's what happen ( flutter run -v ):
[+5658 ms] google-services plugin could not detect any version for com.google.android.gms or com.google.firebase, default version: 9.0.0 will be used.
[        ] please apply google-services plugin at the bottom of the build file.
[  +68 ms] FAILURE: Build failed with an exception.
[   +1 ms] * Where:
[   +2 ms] Build file 'C:\Users\dario\Repos\friendlychat\android\build.gradle' line: 22
[   +1 ms] * What went wrong:
[   +1 ms] A problem occurred evaluating root project 'android'.
[   +1 ms] > A problem occurred configuring project ':app'.
[   +4 ms]    > Failed to notify project evaluation listener.
[   +1 ms]       > Could not resolve all dependencies for configuration ':app:_debugApk'.
[   +1 ms]          > A problem occurred configuring project ':firebase_analytics'.
[   +1 ms]             > Could not resolve all dependencies for configuration ':firebase_analytics:_debugPublishCopy'.
[   +1 ms]                > Could not find com.google.firebase:firebase-auth:10.2.1.
[   +1 ms]                  Required by:
[   +4 ms]                      io.flutter.firebase_analytics:firebase_analytics:1.0-SNAPSHOT
[   +2 ms]                > Could not find com.google.firebase:firebase-analytics:10.2.1.
[   +1 ms]                  Required by:
[   +2 ms]                      io.flutter.firebase_analytics:firebase_analytics:1.0-SNAPSHOT
[   +4 ms]       > Could not get unknown property 'compileDebugJavaWithJavac' for project ':app' of type org.gradle.api.Project.

Notice that " apply plugin: 'com.google.gms.google-services' " definitely is at the bottom of my android/app/gradle
flutter analyze: No issues
flutter doctor:
[√] Flutter (on Microsoft Windows [Version 10.0.15063], channel alpha)
• Flutter at C:\Users\dario\Repos\flutter
• Framework revision dc4ca8db83 (13 days ago), 2017-05-11 15:33:29 -0700
• Engine revision f99d3ef108
• Tools Dart version 1.23.0-dev.11.11
[√] Android toolchain - develop for Android devices (Android SDK 25.0.3)
• Android SDK at C:\Users\dario\AppData\Local\Android\sdk
• Platform android-25, build-tools 25.0.3
• ANDROID_HOME = C:\Users\dario\AppData\Local\Android\sdk
• Java binary at: C:\Program Files\Android\Android Studio1\jre\bin\java
• Java version: OpenJDK Runtime Environment (build 1.8.0_76-release-b03)
[√] Android Studio (version 2.2)
• Android Studio at C:\Program Files\Android\Android Studio1
• Gradle version 2.14.1
• Java version: OpenJDK Runtime Environment (build 1.8.0_76-release-b03)
[-] IntelliJ IDEA Community Edition (version 2016.3)
• Dart plugin not installed; this adds Dart specific functionality.
• Flutter plugin not installed; this adds Flutter specific functionality.
• For information about managing plugins, see
https://www.jetbrains.com/help/idea/managing-plugins.html
[√] IntelliJ IDEA Ultimate Edition (version 2017.1)
• Dart plugin version 171.4424.63
• Flutter plugin version 13.1
[√] WebStorm (version 2017.1)
• Flutter plugin version 13.1
[√] Connected devices
• Moto G4 • ZY2239WT6B • android-arm • Android 7.1.2 (API 25)

Does your android/build.gradle contain the following snippet?
allprojects {
    repositories {
        jcenter()
        maven { url "https://jitpack.io" }
    }
}

@Skylled
yeah sure, I added all code suggested by the codelab

@darioielardi
Make sure all your Android dependencies are up to date (Android Support Repository, etc.).
The easiest way is to open Android Studio and let it check everything for you (This is what I've done). Then you should be able to follow the codelab.

The GMS classpath has to be added to projectRoot/build.gradle and apply plugin [GMS] to the bottom of projectRooot/app/build.gradle. This will fix that.
This video covers wiring it up: https://www.youtube.com/watch?v=t_SgDznY99k

@darioielardi
I guess you have to install or update Google Repository and Google Play Services in SDK tools
This link might help you.
https://developers.google.com/android/guides/setup
I updated them from Android Studio > Preferences > Appearance & Behavior > System Settings > Android SDK.

The codelab has been updated with the Google Repository requirement. Please ping if you're still seeing this issue.

I'm just adding to the heap. But when you see gms errors, it could be that the gradle instructions have been missed.

https://github.com/flutter/plugins/tree/master/packages/firebase_auth

Enable the Google services by configuring the Gradle scripts as such.

Add the classpath to the [project]/android/build.gradle file.

dependencies {
  // Example existing classpath
  classpath 'com.android.tools.build:gradle:2.2.3'
  // Add the google services classpath
  classpath 'com.google.gms:google-services:3.1.0'
}

Add the apply plugin to the [project]/android/app/build.gradle file.

// ADD THIS AT THE BOTTOM
apply plugin: 'com.google.gms.google-services'

Closing because we are not seeing this during verification this week. Feel free to re-open if it's still an issue.

Did you forget to add  google repository In project build folder?
buildscript {
    repositories {
        jcenter()
        maven {
            url "https://maven.google.com"
        }
    }

i did all these but issue still not gone for analytics

i got the solution of this we have to use androidx instead of android and we dont need to add this
maven{
url "https://maven.google.com"
}