ValueError: SE: buffer too short

I'm getting this error when negotiating options. Is this a bug with the published wheel or am I doing something wrong?

Can you add some more information?  What data are you inputting?  What exactly is the error/traceback?

@uSpike When I'm negotiating options via IAC DO/WILL (or, rather, the server is doing the negotiation, I'm just accepting), one of two things happens:
If I negotiate some features but, for DOs, I say that there aren't any options supported, some negotiation works before the library starts subcommand negotiation and it gives this error:
>briefcase dev

[mudclient] Installing requirements...
# ...
Installing dev requirements... done

Starting in dev mode...
===========================================================================
Command(cmd=<Opt.DO: 253>, opt=34)
Command(cmd=<Opt.WILL: 251>, opt=3)
Command(cmd=<Opt.DO: 253>, opt=31)
Command(cmd=<Opt.DO: 253>, opt=24)
Command(cmd=<Opt.WILL: 251>, opt=86)
Command(cmd=<Opt.WILL: 251>, opt=70)
Command(cmd=<Opt.WILL: 251>, opt=69)
Command(cmd=<Opt.WILL: 251>, opt=201)
Command(cmd=<Opt.WILL: 251>, opt=91)
Task exception was never retrieved
source_traceback: Object created at (most recent call last):
  File "Lib\site-packages\toga_winforms\app.py", line 257, in run_app
    self.create()
  File "Lib\site-packages\toga_winforms\app.py", line 113, in create
    self.interface._startup()
  File "Lib\site-packages\toga\app.py", line 629, in _startup
    self.startup()
  File "app.py", line 49, in startup
    self.loop.create_task(self.start_telnet())
Traceback (most recent call last):
  File "app.py", line 69, in start_telnet
    self.machine.receive_data(data)
  File "Lib\site-packages\telnetio\_machine.py", line 120, in receive_data
    self._state.send(byte)
  File "Lib\site-packages\telnetio\_machine.py", line 210, in _state_sb
    raise ValueError("SE: buffer too short")
ValueError: SE: buffer too short

That's generated via this code:
    def handle_telnet_event(self, event):
        print(event)
        if isinstance(event, Command):
            self.handle_telnet_command(event)
        elif isinstance(event, SubCommand):
            self.handle_telnet_subcommand(event)
        else:
            print(event)

    def handle_telnet_command(self, event):
        match event.cmd:
            case Opt.NOP: return # Do nothing, no operation
            case Opt.WILL | Opt.WONT | Opt.DO | Opt.DONT:
                option = event.opt
                cmd = event.cmd
                bitmask = 1 << option
                option_enabled = self.features & bitmask
                match cmd:
                    case Opt.WILL:
                        if not option_enabled:
                            self.features |= bitmask
                            self.machine.send_command(Opt.DO, option)
                    case Opt.WONT:
                        if option_enabled:
                            self.features &= ~bitmask
                            self.machine.send_command(Opt.DONT, option)
                    case Opt.DO:
                        if not option_enabled:
                            if self.is_option_supported(option):
                                self.features |= bitmask
                                self.machine.send_command(Opt.WILL, option)
                            else:
                                self.machine.send_command(Opt.WONT, option)
                    case Opt.DONT:
                        if option_enabled:
                            self.features &= ~bitmask
                            self.machine.send_command(Opt.WONT, option)
            case Opt.DM: return # We can't handle this
            case Opt.BRK | Opt.EL:
                self.command_input.value = ""
            case Opt.EC:
                self.command_input.value = self.command_input.value[:len(self.command_input.value)-1]
            case _: return # Unknown command

    def is_option_supported(self, feature):
        return False # Currently we legitimately don't support anything

    def handle_telnet_subcommand(self, event):
        print(event) # We don't handle subcommands for now

On the other hand, if I claim that all possible options are supported, I get a very different error:
Starting in dev mode...
===========================================================================
Command(cmd=<Opt.DO: 253>, opt=34)
Command(cmd=<Opt.WILL: 251>, opt=3)
Command(cmd=<Opt.DO: 253>, opt=31)
Command(cmd=<Opt.DO: 253>, opt=24)
Command(cmd=<Opt.WILL: 251>, opt=86)
Command(cmd=<Opt.WILL: 251>, opt=70)
Command(cmd=<Opt.WILL: 251>, opt=69)
Command(cmd=<Opt.WILL: 251>, opt=201)
Command(cmd=<Opt.WILL: 251>, opt=91)
SubCommand(cmd=<Opt.LINEMODE: 34>, opts=bytearray(b'\x01\x03'))
SubCommand(cmd=<Opt.LINEMODE: 34>, opts=bytearray(b'\x01\x03'))
Task exception was never retrieved
source_traceback: Object created at (most recent call last):
  File "Lib\site-packages\toga_winforms\app.py", line 257, in run_app
    self.create()
  File "Lib\site-packages\toga_winforms\app.py", line 113, in create
    self.interface._startup()
  File "Lib\site-packages\toga\app.py", line 629, in _startup
    self.startup()
  File "app.py", line 49, in startup
    self.loop.create_task(self.start_telnet())
Traceback (most recent call last):
  File "app.py", line 69, in start_telnet
    self.machine.receive_data(data)
  File "Lib\site-packages\telnetio\_machine.py", line 120, in receive_data
    self._state.send(byte)
  File "Lib\site-packages\telnetio\_machine.py", line 212, in _state_sb
    cmd = Opt(buf[0])
          ^^^^^^^^^^^
  File "Python312\Lib\enum.py", line 744, in __call__
    return cls.__new__(cls, value)
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "Python312\Lib\enum.py", line 1158, in __new__
    raise ve_exc
ValueError: 24 is not a valid Opt

(As an aside, 24 is a valid option: it asks the client about it's terminal type.)
I've no idea what's happening with the first error since it doesn't make any sense. However, the second is problematic, particularly for MUDs; my recommendation would be to remove the Opt enum and just pass the option directly onto the client library/application, for two reasons:

DO/WILL/WONT/WILL are not telnet options; they are commands, so passing them off as options is misleading. This one is however a pedantic point and not the most important reason.
The most important reason for this is that telnet is designed to be flexible. Ideally, one should not need to copy the library directly into their application to handle options this library doesn't know about (e.g. GMCP or MCCP).

OK thank you for the additional info.

DO/WILL/WONT/WILL are not telnet options; they are commands, so passing them off as options is misleading. This one is however a pedantic point and not the most important reason.

This was changed in main but not released yet.  Options are just int now.
Also receive_data now returns a list of events including Error instead of raising, so you can ignore said errors if you want.
Can you test with the HEAD of main?  There was a small bit of work I wanted to do before releasing another version (1.x) but I could be convinced to cut a release with these changes if they help you.

@uSpike So, I updated to master and I still get that error, except that it doesn't throw an exception this time (and I'm not really sure what to do when I get an error like that -- do I just drop the problematic byte and move on?). That is: I get Error: Error(kind=<ErrorKind.SE_BUFFER_TOO_SHORT: 3>, data=b'V'), followed by exceptions because it gets treated like ordinary data. My event handling is like this:
            while True:
                data = await reader.read(4096)
                if not data:
                    break
                if data:
                    received_data = bytearray()
                    events = self.machine.receive_data(data)
                    for event in events:
                        if isinstance(event, Command):
                            await self.handle_telnet_command(event.cmd, event.opt)
                        elif isinstance(event, SubCommand):
                            await self.handle_telnet_subcommand(event)
                        elif isinstance(event, Data):
                            received_data += event.msg
                        elif isinstance(event, Error):
                            print(f"Error: {event}")
                        else:
                            print(event)
                    if len(received_data) > 0:
                        await self.handle_telnet_recv(received_data)

I don't know if this is a problem with telnetio or the application I'm connecting to.

Also, for some reason if I ignore errors, the received bytes end up being garbage. I'm decoding them, so I think this might (?) be a bug.

and I'm not really sure what to do when I get an error like that -- do I just drop the problematic byte and move on?)

That's up to you.  It seems that invalid data is being sent to the state machine, so it's up to you to continue or not.
It's hard for me to help diagnose your issue without having a way to reproduce it.  To answer your initial question, there are no known bugs.
If you can log all of the events, or even better all of the input data which causes your error, I could help more easily.


Test language model access API

Refs: https://github.com/microsoft/vscode/issues/199908

[ ] anyOS @mjbvz
[x] anyOS @ulugbekna

Complexity: 4
Create Issue

We have added API that allows extensions to access/reuse language models. This allows them to implement arbitrary features with LM support. The proposal is the vscode.proposed.languageModels.d.ts, the entry point is vscode.lm.requestLanguageModelAccess

Start by creating an extension or fork an existing extension sample
Add the proposed API to the package.json (see below)
Then run npx vscode-dts dev to get the typings

	"enabledApiProposals": [
		"languageModels"
	],

This TPI is about testing the API, make sure

the API is well documented and names are logic
the API works and allows you to implement a simple idea (add a command that says something about the selected line)
the concept of LM access and access getting revoked again is explained and clear

Implementing rename suggestions provider through LM access. Didn't have any problems, was able to be productive with the API fast. Cool work 💯

Couple of nits on API & docs:

as discussed, an extension dev could have more type safety when it comes to getting access (because it throws) and they need to check for isRevoked manually

documentation maybe could reference other symbols in the API that help with dev, e.g., makeChatRequest should use a model ID from vscode.lm.languageModels. Maybe mention that vscode.lm.languageModels is updated as extensions come in and one can use onDidChangeLanguageModels to subscribe to changes, etc.

documentation could use tags @throws to indicate what errors are thrown (and that the operation may throw)  and @remarks

Nice work! Works nicely in my testing and pretty easy to get started with. Also submitted a PR with a few small suggestions to the types/docs: https://github.com/microsoft/vscode/pull/205819


Various Boulders

Either hand built and or procedural, can include material variations such as granite / andesite / diorite.

A note for anyone looking to add hand built structures, all static structures should be made using the Sponge schematic addon, not with TerraScript. TerraScript is now strictly for dynamic structures.

Closing as marked "Done"


Add support for accepting invites

@bantic for you to review and merge.
Invites can be accepted by signed in users. Users who are not signed in will be redirected to login/signup and redirected back once they
complete the process.
The invite page itself renders, then starts the AJAX request to claim the invitation automatically.
URLs such as:

http://localhost:4200/claim?verification_code=abc&invitation_id=59ef9caa-292c-42b0-b90f-000b7432b743
http://localhost:4200/claim/59ef9caa-292c-42b0-b90f-000b7432b743/abc-verification-code

Are supported. This is compatible with emails out there in the wild.
This PR introduces general support for redirecting to a path after signing in. See the attemptedTransition property.

cool — I had a question about the impact of doing the async in the didTransition hook. I'm curious if that can be problematic, but I'm sure it's fine. This LGTM

Adds a button, addresses a few items caught by @bantic.
The screen for acceptance is very, very simple:

Significantly it does't have the organization name. This is passed with the URL from the email, but we should not be trusting that value. Instead, the API needs to be updated to allow us to easily fetch the organization for an invite. We can load that in the model hook and display the name here.
IMO there should also be a "this isn't me" button, or a "cancel" button.
I'd like to make those items a separate issue and keep moving forward though.
@bantic I think this is good to go.

nice. I like the look of that button. So inviting. So accepting.


Add the option to turn on notifications for when a specified potion runs out

I only saw that there was this option for overloads, I think it would be useful for a lot of players including myself.

If it has a chat message, use Chat Notifications
Duplicate of #9913

If it has a chat message, use Chat Notifications
Duplicate of #9913

It doesn't have a chat message, what can I do then?

What potion is it?

What potion is it?

Super combat potion

That's what the Threshold option in the Boosts Information plugin is for

That's what the Threshold option in the Boosts Information plugin is for

I want to know exactly when it ends, not when there's 1 minute remaining. The minimum amount you can set there is 1

so yeah, Duplicate of #9913

so yeah, Duplicate of #9913

You didn't help me at all, thanks

This is not a support forum, this is an issue tracker. Questions should be for the Discord


operator victoriametrics-operator (0.26.0)

Signed-off-by: Nikolay Khramchikhin<EMAIL_ADDRESS>Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/re-run

@f41gh7 please add full path including registry domain to victoriametrics/operator:v0.26.0 entry(es).

Thanks for pointing, will do at the next PR with hotfixes,  image generated incorrectly by script...


tests: use PHPStan binary directly

another attempt to fix 7cc0e00fa5961f609fe04643b74f951df0a1c1f9 and  73c8ebd86343fbfa4cc0477f798909f430332ac4
Ref https://github.com/phpstan/phpstan-doctrine/pull/81

This seems to work both on Windows (tested locally) and on Linux (tested in Travis).

Great, thank you :)


WGPU 0.15 compatibility

181  |         let rpass_egui = RenderPass::new(device, surface_cfg.format, 1);
     |                          ^^^^^^^^^^^^^^^ ------  ------------------ expected enum `egui_wgpu_backend::wgpu::TextureFormat`, found enum `wgpu::TextureFormat`
     |                                          |

How should we tackle this? Thank you.

This crate needs to be patched to support WGPU 0.15. PRs are welcome.

We support wgpu 0.16 now.


Add shortcuts support and automatic moving to next code selector

Sorry for the big PR, please have a look and let me know what you think of the proposed logic around processing user input (rows 60-137 in main_ui and rows 43 to 67 in view_model). The rest is primarily variable renames. Thanks!

Here's the demo: https://www.cl.cam.ac.uk/~mcm79/codav2_demos/tabbing-2018-10-07/

Thanks for this! I've resolved all your comments so far, please have another look!


Add PEN_TEST_SHARED_SECRET

In order to allow the penetration test team to connect to the API without exposing our SHARED_SECRET we are adding another valid secret that they can use.
This PR should be reverted once the penetration test is complete.

Just a general observation here.
Do we need to have a Utils/Env?
Could this not all be moved into StartUp.cs and be handled with a .json settings file overidden at startup with environment vars?

What would be the benefit? It sounds more complex than what we have at the moment to me?

Just a general observation here.
Do we need to have a Utils/Env?
Could this not all be moved into StartUp.cs and be handled with a .json settings file overidden at startup with environment vars?

What would be the benefit? It sounds more complex than what we have at the moment to me?

It's convention, and less complex because it automagically brings in your settings.  Less code

Created a ticket for picking this up in another PR: https://dfedigital.atlassian.net/browse/GITPB-572


Make sure the broadcast value is not 0

Fix #238 and potentially #232

perfect fix, thanks

Should we add this check for colorTemp also?

Can color temp go to 0?


fix typo in comment

What does this PR do?

Fixes typo in function comment.
Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Safe images implementation idea

Is your feature request related to a problem? Please describe.
The only problem is that the way one can express themselves is limited by only having text and voice.
Describe the solution you'd like
To avoid storing data and weird Angular code snippets in images we should have image popups when clicking on an Imgur link.
Describe alternatives you've considered
Maybe automatically embed Imgur links in chat/we can also use other image hosting platforms.
Also
Maybe we can also use an image hosting platform that has it's own content moderation so you wouldn't have to deal with porn being spammed, etc

"weird Angular code snippets"


CMake Generate step failed.

I'm building flashlight from source on Ubuntu 20.04 with cmake 3.18.0
cmake .. -DCMAKE_BUILD_TYPE=Release -DFLASHLIGHT_BACKEND=CPU -DFL_BUILD_DISTRIBUTED=OFF -DFL_BUILD_TESTS=OFF -DFL_BUILD_EXAMPLES=OFF -DFL_BUILD_CONTRIB=OFF

It fails with the following error
CMake Error at CMakeLists.txt:216 (add_library):
  Target "flashlight" links to target "ArrayFire::afcpu" but the target was
  not found.  Perhaps a find_package() call is missing for an IMPORTED
  target, or an ALIAS target is missing?

Earlier in the configuration process arrayfire was found
-- ArrayFire found (include: /usr/include, library: afcpu)

@dmakarov Could you post full log of your cmake command?

cmake .. -DCMAKE_BUILD_TYPE=Release -DFLASHLIGHT_BACKEND=CPU -DFL_BUILD_DISTRIBUTED=OFF -DFL_BUILD_TESTS=OFF -DFL_BUILD_EXAMPLES=OFF -DFL_BUILD_CONTRIB=OFF
-- The C compiler identification is GNU 9.3.0
-- The CXX compiler identification is GNU 9.3.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- ArrayFire found (include: /usr/include, library: afcpu)
-- Could NOT find cereal (missing: cereal_INCLUDE_DIRS)
-- cereal NOT found. Will download from source
-- Looking for sys/types.h
-- Looking for sys/types.h - found
-- Looking for stdint.h
-- Looking for stdint.h - found
-- Looking for stddef.h
-- Looking for stddef.h - found
-- Check size of void*
-- Check size of void* - done
-- Checking for [mkl_gf_lp64 - mkl_gnu_thread - mkl_core - iomp5 - pthread - m]
--   Library mkl_gf_lp64: not found
-- Checking for [mkl_gf_lp64 - mkl_intel_thread - mkl_core - iomp5 - pthread - m]
--   Library mkl_gf_lp64: not found
-- Checking for [mkl_gf - mkl_gnu_thread - mkl_core - iomp5 - pthread - m]
--   Library mkl_gf: not found
-- Checking for [mkl_gf - mkl_intel_thread - mkl_core - iomp5 - pthread - m]
--   Library mkl_gf: not found
-- Checking for [mkl_intel_lp64 - mkl_gnu_thread - mkl_core - iomp5 - pthread - m]
--   Library mkl_intel_lp64: not found
-- Checking for [mkl_intel_lp64 - mkl_intel_thread - mkl_core - iomp5 - pthread - m]
--   Library mkl_intel_lp64: not found
-- Checking for [mkl_intel - mkl_gnu_thread - mkl_core - iomp5 - pthread - m]
--   Library mkl_intel: not found
-- Checking for [mkl_intel - mkl_intel_thread - mkl_core - iomp5 - pthread - m]
--   Library mkl_intel: not found
-- Checking for [mkl_gf_lp64 - mkl_gnu_thread - mkl_core - pthread - m]
--   Library mkl_gf_lp64: not found
-- Checking for [mkl_gf_lp64 - mkl_intel_thread - mkl_core - pthread - m]
--   Library mkl_gf_lp64: not found
-- Checking for [mkl_gf - mkl_gnu_thread - mkl_core - pthread - m]
--   Library mkl_gf: not found
-- Checking for [mkl_gf - mkl_intel_thread - mkl_core - pthread - m]
--   Library mkl_gf: not found
-- Checking for [mkl_intel_lp64 - mkl_gnu_thread - mkl_core - pthread - m]
--   Library mkl_intel_lp64: not found
-- Checking for [mkl_intel_lp64 - mkl_intel_thread - mkl_core - pthread - m]
--   Library mkl_intel_lp64: not found
-- Checking for [mkl_intel - mkl_gnu_thread - mkl_core - pthread - m]
--   Library mkl_intel: not found
-- Checking for [mkl_intel - mkl_intel_thread - mkl_core - pthread - m]
--   Library mkl_intel: not found
-- Checking for [mkl_gf_lp64 - mkl_sequential - mkl_core - m]
--   Library mkl_gf_lp64: not found
-- Checking for [mkl_gf - mkl_sequential - mkl_core - m]
--   Library mkl_gf: not found
-- Checking for [mkl_intel_lp64 - mkl_sequential - mkl_core - m]
--   Library mkl_intel_lp64: not found
-- Checking for [mkl_intel - mkl_sequential - mkl_core - m]
--   Library mkl_intel: not found
-- Checking for [mkl_gf_lp64 - mkl_sequential - mkl_core - m]
--   Library mkl_gf_lp64: not found
-- Checking for [mkl_gf - mkl_sequential - mkl_core - m]
--   Library mkl_gf: not found
-- Checking for [mkl_intel_lp64 - mkl_sequential - mkl_core - m]
--   Library mkl_intel_lp64: not found
-- Checking for [mkl_intel - mkl_sequential - mkl_core - m]
--   Library mkl_intel: not found
-- Checking for [mkl_gf_lp64 - mkl_gnu_thread - mkl_core - iomp5 - pthread - m]
--   Library mkl_gf_lp64: not found
-- Checking for [mkl_gf_lp64 - mkl_intel_thread - mkl_core - iomp5 - pthread - m]
--   Library mkl_gf_lp64: not found
-- Checking for [mkl_gf - mkl_gnu_thread - mkl_core - iomp5 - pthread - m]
--   Library mkl_gf: not found
-- Checking for [mkl_gf - mkl_intel_thread - mkl_core - iomp5 - pthread - m]
--   Library mkl_gf: not found
-- Checking for [mkl_intel_lp64 - mkl_gnu_thread - mkl_core - iomp5 - pthread - m]
--   Library mkl_intel_lp64: not found
-- Checking for [mkl_intel_lp64 - mkl_intel_thread - mkl_core - iomp5 - pthread - m]
--   Library mkl_intel_lp64: not found
-- Checking for [mkl_intel - mkl_gnu_thread - mkl_core - iomp5 - pthread - m]
--   Library mkl_intel: not found
-- Checking for [mkl_intel - mkl_intel_thread - mkl_core - iomp5 - pthread - m]
--   Library mkl_intel: not found
-- Checking for [mkl_gf_lp64 - mkl_gnu_thread - mkl_core - pthread - m]
--   Library mkl_gf_lp64: not found
-- Checking for [mkl_gf_lp64 - mkl_intel_thread - mkl_core - pthread - m]
--   Library mkl_gf_lp64: not found
-- Checking for [mkl_gf - mkl_gnu_thread - mkl_core - pthread - m]
--   Library mkl_gf: not found
-- Checking for [mkl_gf - mkl_intel_thread - mkl_core - pthread - m]
--   Library mkl_gf: not found
-- Checking for [mkl_intel_lp64 - mkl_gnu_thread - mkl_core - pthread - m]
--   Library mkl_intel_lp64: not found
-- Checking for [mkl_intel_lp64 - mkl_intel_thread - mkl_core - pthread - m]
--   Library mkl_intel_lp64: not found
-- Checking for [mkl_intel - mkl_gnu_thread - mkl_core - pthread - m]
--   Library mkl_intel: not found
-- Checking for [mkl_intel - mkl_intel_thread - mkl_core - pthread - m]
--   Library mkl_intel: not found
-- Checking for [mkl - guide - pthread - m]
--   Library mkl: not found
-- MKL not found
-- Looking for sgemm_
-- Looking for sgemm_ - not found
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Could NOT find BLAS (missing: BLAS_LIBRARIES)
-- Attempting to build MKLDNN without MKL in current configuration.
-- MKLDNN headers found in /usr/include
-- Using MKLDNN library found in /usr/lib/x86_64-linux-gnu/libmkldnn.so
-- MKL not found; trying to fall back to mklml library
-- Using MKL-DNN without mklml headers
-- mklml not found; trying to fall back to system BLAS library
-- No GEMM implementation found - MKL-DNN will use internal GEMM implementation
-- MKLDNN found
CMake Warning (dev) at flashlight/autograd/CMakeLists.txt:16 (target_sources):
  Policy CMP0076 is not set: target_sources() command converts relative paths
  to absolute.  Run "cmake --help-policy CMP0076" for policy details.  Use
  the cmake_policy command to set the policy and suppress this warning.

  An interface source of target "Autograd" has a relative path.
Call Stack (most recent call first):
  CMakeLists.txt:279 (include)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at flashlight/autograd/CMakeLists.txt:46 (target_sources):
  Policy CMP0076 is not set: target_sources() command converts relative paths
  to absolute.  Run "cmake --help-policy CMP0076" for policy details.  Use
  the cmake_policy command to set the policy and suppress this warning.

  An interface source of target "Autograd" has a relative path.
Call Stack (most recent call first):
  CMakeLists.txt:279 (include)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at flashlight/common/CMakeLists.txt:25 (target_sources):
  Policy CMP0076 is not set: target_sources() command converts relative paths
  to absolute.  Run "cmake --help-policy CMP0076" for policy details.  Use
  the cmake_policy command to set the policy and suppress this warning.

  An interface source of target "Common" has a relative path.
Call Stack (most recent call first):
  CMakeLists.txt:282 (include)
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Check if compiler accepts -pthread
-- Check if compiler accepts -pthread - yes
CMake Warning (dev) at flashlight/dataset/CMakeLists.txt:25 (target_sources):
  Policy CMP0076 is not set: target_sources() command converts relative paths
  to absolute.  Run "cmake --help-policy CMP0076" for policy details.  Use
  the cmake_policy command to set the policy and suppress this warning.

  An interface source of target "Dataset" has a relative path.
Call Stack (most recent call first):
  CMakeLists.txt:285 (include)
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Gloo not found
-- NCCL not found
-- Found MPI_C: /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so (found version "3.1")
-- Found MPI_CXX: /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi_cxx.so (found version "3.1")
-- Found MPI: TRUE (found version "3.1")
-- MPI_VERSION found:  3.1
-- MPI_CXX found
-- MPI_CXX compile flags: -pthread
-- MPI_CXX include path: /usr/lib/x86_64-linux-gnu/openmpi/include/openmpi/usr/lib/x86_64-linux-gnu/openmpi/include
-- MPI_CXX LINK flags path: -pthread
-- MPI_CXX libraries: /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi_cxx.so/usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so
-- MPI_C found
-- MPI_C compile flags: -pthread
-- MPI_C include path: /usr/lib/x86_64-linux-gnu/openmpi/include/openmpi/usr/lib/x86_64-linux-gnu/openmpi/include
-- MPI_C LINK flags path: -pthread
-- MPI_C libraries: /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so
CMake Warning (dev) at flashlight/memory/CMakeLists.txt:17 (target_sources):
  Policy CMP0076 is not set: target_sources() command converts relative paths
  to absolute.  Run "cmake --help-policy CMP0076" for policy details.  Use
  the cmake_policy command to set the policy and suppress this warning.

  An interface source of target "Memory" has a relative path.
Call Stack (most recent call first):
  CMakeLists.txt:291 (include)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at flashlight/meter/CMakeLists.txt:18 (target_sources):
  Policy CMP0076 is not set: target_sources() command converts relative paths
  to absolute.  Run "cmake --help-policy CMP0076" for policy details.  Use
  the cmake_policy command to set the policy and suppress this warning.

  An interface source of target "Meter" has a relative path.
Call Stack (most recent call first):
  CMakeLists.txt:294 (include)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at flashlight/nn/CMakeLists.txt:44 (target_sources):
  Policy CMP0076 is not set: target_sources() command converts relative paths
  to absolute.  Run "cmake --help-policy CMP0076" for policy details.  Use
  the cmake_policy command to set the policy and suppress this warning.

  An interface source of target "NN" has a relative path.
Call Stack (most recent call first):
  CMakeLists.txt:297 (include)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at flashlight/optim/CMakeLists.txt:22 (target_sources):
  Policy CMP0076 is not set: target_sources() command converts relative paths
  to absolute.  Run "cmake --help-policy CMP0076" for policy details.  Use
  the cmake_policy command to set the policy and suppress this warning.

  An interface source of target "Optim" has a relative path.
Call Stack (most recent call first):
  CMakeLists.txt:300 (include)
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Configuring done
CMake Error at CMakeLists.txt:216 (add_library):
  Target "flashlight" links to target "ArrayFire::afcpu" but the target was
  not found.  Perhaps a find_package() call is missing for an IMPORTED
  target, or an ALIAS target is missing?

CMake Error at CMakeLists.txt:216 (add_library):
  Target "flashlight" links to target "ArrayFire::afcpu" but the target was
  not found.  Perhaps a find_package() call is missing for an IMPORTED
  target, or an ALIAS target is missing?

-- Generating done
CMake Generate step failed.  Build files cannot be regenerated correctly.

This change helps to make it pass the generation phase, although the build later fails with compiler syntax errors.
diff --git a/CMakeLists.txt b/CMakeLists.txt
index fbfc8ed..1613c9d 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -122,7 +122,7 @@ add_library(${FL_BACKEND} INTERFACE)
 if (TARGET CONAN_PKG::arrayfire)
   target_link_libraries(${FL_BACKEND} INTERFACE CONAN_PKG::arrayfire)
 else()
-  target_link_libraries(${FL_BACKEND} INTERFACE ArrayFire::${FL_AF_BACKEND})
+  target_link_libraries(${FL_BACKEND} INTERFACE ${FL_AF_BACKEND})
 endif()

cc @jacobkahn

@dmakarov thanks for reporting -- looking into it.

The way we link ArrayFire has been completely changed in the last several months; closing.

Please let me know how to link arrayfire, cereal right now - As i have the same issue

@avi-champ this generally means the ArrayFire target you intended to build wasn't built. Make sure you built the ArrayFire CPU backend/check for libafcpu.so.


web docker not pulling image

I first convert my branch to debian from the github repo, build the debian package with Dockerfile and then push it to my Docker Hub. I also put my own settings in this debian package (interface-config.js and custom-config.js)
Dockerfile:
FROM jitsi/web:web-1.0.8091-1
RUN apt-get update && apt-get install -y curl
COPY jitsi-meet-web_1.0.8091-1_all.deb /dir/
RUN dpkg -i /dir/jitsi-meet-web_1.0.8091-1_all.deb || apt-get install -f -y
RUN echo “Jitsi Debian Package has been installed.”
CMD [“/bin/bash”]
CMD [“tail”, “-f”, “/dev/null”]
EXPOSE 81 443

values.yaml:
global:
  # Set your cluster's DNS domain here.
  # "cluster.local" should work for most environments.
  # Set to "" to disable the use of FQDNs (default in older chart versions).
  clusterDomain: cluster.local
  podLabels: {}
  podAnnotations: {}
  releaseSecretsOverride:
    enabled: false
    # Support environment variables from pre-created secrets, such as 1Password operator
    # extraEnvFrom:
    #   - secretRef:
    #       name: '{{ include "prosody.fullname" . }}-overrides'
    #       optional: true

imagePullSecrets: []
nameOverride: ""
fullnameOverride: ""

enableAuth: false
enableGuests: true
# Where Jitsi Web UI is made available
# such as jitsi.example.com
publicURL: "kmeet.customjitsi.com"

tz: Europe/Amsterdam

image:
  pullPolicy: Always

## WebSocket configuration:
#
#  Both Colibri and XMPP WebSockets are disabled by default,
#  since some LoadBalancer / Reverse Proxy setups can't pass
#  WebSocket connections properly, which might result in breakage
#  for some clients.
#
#  Enable both Colibri and XMPP WebSockets to replicate the current
#  upstream `meet.jit.si` setup. Keep both disabled to replicate
#  older setups which might be more compatible in some cases.
websockets:
  ## Colibri (JVB signalling):
  colibri:
    enabled: true
  ## XMPP (Prosody signalling):
  xmpp:
    enabled: true

web:
  replicaCount: 1
  repository: 'harbor.xxx.com/root/custom-jitsi-1'
  #repository: jitsi/web
  tag: 'latest'

Then I add the url of the image I built in values.yaml but it doesn't pull my custom image.
It takes the image in the image below..

Is there a solution for this?

Hello @sakiphandursun!
The correct value structure for web pod image looks like this:
web:
  replicaCount: 1
  image:
    repository: jitsi/web
    tag: latest

In your case the values are misplaced as .Values.web.(repository|tag), which is incorrect.

We decided to throw away helm. We are not using it anymore. Thanks for your interest. Have a good day!


Empty ColorM is no longer valid

This code panics due to nil access after recent changes to make affine.ColorM an interface:
var a, b ebiten.ColorM
a.Concat(b)

As a workaround, this works:
var a, b ebiten.ColorM
b.Reset()
a.Concat(b)

var a, b ebiten.ColorM
a.Concat(b)

I couldn't reproduce the panic with this code. Is this the minimum code to reproduce the issue?

Oh, I forgot a crucial part when simplifying. This now crashes:
   var a, b ebiten.ColorM
   a.SetElement(1, 2, -1)
   a.Concat(b)

as follows:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x38 pc=0x53e817]

goroutine 1 [running, locked to thread]:
github.com/hajimehoshi/ebiten/v2/internal/affine.(*colorMImplBodyTranslate).Concat(0xc00b281f40, 0x0, 0x0, 0x2, 0xc0bf800000)
	/home/rpolzer/go/pkg/mod/github.com/hajimehoshi/ebiten/v2@v2.2.0-alpha.11.0.20210817032719-12350e2fee5d/internal/affine/colorm.go:498 +0x37
github.com/hajimehoshi/ebiten/v2.(*ColorM).Concat(...)
	/home/rpolzer/go/pkg/mod/github.com/hajimehoshi/ebiten/v2@v2.2.0-alpha.11.0.20210817032719-12350e2fee5d/colorm.go:67

The previous example didn't hit this crash due to this special case:
func (c ColorMIdentity) Concat(other ColorM) ColorM {
        return other
}

The issue appears to be that IsIdentity() can't be called when the interface value is an untyped nil - which is precisely the case in an ebiten.ColorM{}.
TBH I don't understand why the renderer doesn't crash all the time due to this issue, given that internal/graphicsdriver/opengl/graphics.go calls IsIdentity() on an interface value too.


Split CCapableErc20 and CErc20

Upgrade tests: https://github.com/CreamFi/comptroller-upgrade/tree/ctoken_internal_cash

Upgrade tests: https://github.com/CreamFi/comptroller-upgrade/tree/ctoken_internal_cash


TableView appears unscrollable on iPad simulator and Android emulator with two_dimensional_scrollables: ^0.2.0

Steps to reproduce

Check out https://github.com/domesticmouse/codelabs/tree/generate_crossword
Run the app in https://github.com/domesticmouse/codelabs/tree/generate_crossword/generate_crossword/step_09 on a iOS simulator or Android emulator
Try to scroll

Expected results
TableView scrolls.
Actual results
TableView does not scroll.
For context, it scrolls effortlessly on macOS native.
Code sample
See repo mentioned above
Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
➜  step_10 git:(generate_crossword) ✗ flutter run -d ipad
Launching lib/main.dart on iPad Pro (11-inch) (4th generation) in debug mode...
Running Xcode build...
 └─Compiling, linking and signing...                         4.7s
Xcode build done.                                           17.1s
[ERROR:flutter/shell/platform/darwin/graphics/FlutterDarwinContextMetalImpeller.mm(42)] Using the Impeller rendering backend.
Syncing files to device iPad Pro (11-inch) (4th generation)...        171ms

Flutter run key commands.
r Hot reload. 🔥🔥🔥
R Hot restart.
h List all available interactive commands.
d Detach (terminate "flutter run" but leave application running).
c Clear the screen
q Quit (terminate the application on the device).

A Dart VM Service on iPad Pro (11-inch) (4th generation) is available at: http://<IP_ADDRESS>:51762/dWkOMIMIo2k=/
The Flutter DevTools debugger and profiler on iPad Pro (11-inch) (4th generation) is available at:
http://<IP_ADDRESS>:9103?uri=http://<IP_ADDRESS>:51762/dWkOMIMIo2k=/
flutter: Generated 40 x 22 crossword in 10s with 4 workers.

Flutter Doctor output
Doctor output
➜  step_10 git:(generate_crossword) ✗ flutter doctor -v
[✓] Flutter (Channel stable, 3.19.5, on macOS 14.4.1 23E224 darwin-arm64, locale en)
    • Flutter version 3.19.5 on channel stable at /Users/brettmorgan/flutter
    • Upstream repository https://github.com/flutter/flutter
    • Framework revision 300451adae (2 days ago), 2024-03-27 21:54:07 -0500
    • Engine revision e76c956498
    • Dart version 3.3.3
    • DevTools version 2.31.1

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/brettmorgan/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15E204a
    • CocoaPods version 1.15.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2023.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)

[✓] IntelliJ IDEA Community Edition (version 2023.3.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 77.0.1
    • Dart plugin version 233.13135.65

[✓] VS Code (version 1.87.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.84.0

[✓] Connected device (4 available)
    • sdk gphone64 arm64 (mobile)                  • emulator-5554                        •
      android-arm64  • Android 14 (API 34) (emulator)
    • iPad Pro (11-inch) (4th generation) (mobile) • 6FD475F0-3280-48B0-8D3A-6A3A4BF8FC5B • ios
      • com.apple.CoreSimulator.SimRuntime.iOS-17-4 (simulator)
    • macOS (desktop)                              • macos                                •
      darwin-arm64   • macOS 14.4.1 23E224 darwin-arm64
    • Chrome (web)                                 • chrome                               •
      web-javascript • Google Chrome 123.0.6312.87

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Doing some further digging, I'm finding this a bit weird. On initial load, the grid is not scrollable. Change the size of the grid to a larger grid, then change it back to the original size... and it's suddenly scrollable?
I don't understand what I'm doing wrong here. =)

There is no step_09 so I use step_09_b example to reproduce this.
On a physical device and initial load, the grid is scrollable normally (I see the grid is CrosswordSize.medium(width: 40, height: 22)).
But I also can observe the issue similar to your case at https://github.com/flutter/flutter/issues/146015#issuecomment-2027933199. However, it seems to be fixed on master channel as I see it on 3.19.5 but not on 3.22.0-1.0.pre.37. Could you retry on master channel and confirm?

flutter doctor -v (stable and master)
[✓] Flutter (Channel stable, 3.19.5, on macOS 14.1 23B74 darwin-x64, locale en-VN)
    • Flutter version 3.19.5 on channel stable at /Users/huynq/Documents/GitHub/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 300451adae (25 hours ago), 2024-03-27 21:54:07 -0500
    • Engine revision e76c956498
    • Dart version 3.3.3
    • DevTools version 2.31.1

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15C500b
    • CocoaPods version 1.15.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2023.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • android-studio-dir = /Applications/Android Studio.app/
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)

[✓] VS Code (version 1.87.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.84.0

[✓] Connected device (3 available)
    • Pixel 7 (mobile) • 2B171FDH20084L • android-arm64  • Android 14 (API 34)
    • macOS (desktop)  • macos          • darwin-x64     • macOS 14.1 23B74 darwin-x64
    • Chrome (web)     • chrome         • web-javascript • Google Chrome 123.0.6312.86

[✓] Network resources
    • All expected network resources are available.

• No issues found!

[!] Flutter (Channel master, 3.22.0-1.0.pre.37, on macOS 14.1 23B74 darwin-x64, locale en-VN)
    • Flutter version 3.22.0-1.0.pre.37 on channel master at /Users/huynq/Documents/GitHub/flutter_master
    ! Warning: `flutter` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision fd8561a917 (6 hours ago), 2024-03-31 17:12:24 -0400
    • Engine revision 4f6b832c8e
    • Dart version 3.5.0 (build 3.5.0-5.0.dev)
    • DevTools version 2.34.1
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15C500b
    • CocoaPods version 1.15.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2023.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • android-studio-dir = /Applications/Android Studio.app/
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)

[✓] VS Code (version 1.87.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.84.0

[✓] Connected device (3 available)
    • iPad (mobile)   • 00008103-000A1464346A201E • ios            • iOS 17.2 21C62
    • macOS (desktop) • macos                     • darwin-x64     • macOS 14.1 23B74 darwin-x64
    • Chrome (web)    • chrome                    • web-javascript • Google Chrome 123.0.6312.87

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

I can still reproduce on the iPad simulator with master channel
$ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, 3.20.0-6.0.pre.1, on macOS 14.4.1 23E224 darwin-arm64, locale en)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.2)
[✓] IntelliJ IDEA Community Edition (version 2023.3.2)
[✓] VS Code (version 1.87.2)
[✓] Connected device (4 available)
[✓] Network resources

• No issues found!

Looks like I've forgotten how to use master. Agreed, appears fixed on Flutter master channel.
flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, 3.22.0-1.0.pre.41, on macOS 14.4.1 23E224 darwin-arm64, locale en)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.2)
[✓] IntelliJ IDEA Community Edition (version 2023.3.2)
[✓] VS Code (version 1.87.2)
[✓] Connected device (4 available)
[✓] Network resources

• No issues found!

Thanks for checking. I think this has the same cause with https://github.com/flutter/flutter/issues/144982 when setting diagonalDragBehavior to DiagonalDragBehavior.free. It's been fixed recently and on master channel only.
I will close this as fixed.


Reinitialize the whole thing when the window gets resized

Fixes #39 and other issues I had.

I don't know. I suppose it was for the callback. If it works, It works. 😄

I don't see why anyone would rely on that unless they're sure to only ever have 1 rellax element in their page, but I don't really care and it's not the point of this PR, so I re-added the positions argument.


Add support for Reveal.js scroll view

https://revealjs.com/scroll-view/

According to @King it can be used as is:

About ScrollView
Scroll view: I don't use it also, but I've tried it, mkslides supports it as well, no additional configuration and development is required, upstream reveal.js is already done. Add the parameter ?view=scroll directly after the URL you visit,like this site/index.html?view=scroll, and then refresh the page to become a scrolling view, you try.


Create a file manager ChatGPT plugin

Extending the DirReader plugin https://github.com/stoerr/chatGPTtools/tree/develop/plugins/dirreaderplugin create a ChatGPT plugin that can not only list and read but also write files.

That's https://github.com/stoerr/DevelopersChatGPTToolBench .


Cannot use latest micropython plugin

In Pycharm and InteliJ only plugin version available is 1.4.0
Downloaded 1.4.2 and tried to install via install Plugin from Disk
Get ERROR

Get same type of error in PyCharm and IntelliJ

might be related to REPL and #270

Is there any progress to get REPL working on 2023.3? Is there any way to install 1.4.2 on 2023.3?

Waiting for it

1.4.3 was released. It supports 2023.3+ versions.


Create a new release for milestone 3

Manually bumping version to v2.0.0 in pyproject.toml.
Closes #63.

Merged to main.

agreed on the changes


Compatible with Laravel 10

Hi, I see there is support for version 10 in the main branch, but couldn't find a release version (latest 0.2.2) that supports 10.
From the documentation the command composer require innocenzi/laravel-vite returns an error
 Problem 1
    - innocenzi/laravel-vite[0.0.1, ..., 0.1.22] require illuminate/contracts ^8.0 -> found illuminate/contracts[v8.0.0, ..., v8.83.27] but these were not loaded, likely because it conflicts with another require.
    - innocenzi/laravel-vite[0.1.23, ..., v0.2.2] require illuminate/contracts ^8.0|^9.0 -> found illuminate/contracts[v8.0.0, ..., v8.83.27, v9.0.0, ..., v9.52.0] but these were not loaded, likely because it conflicts with another require.
    - Root composer.json requires innocenzi/laravel-vite * -> satisfiable by innocenzi/laravel-vite[0.0.1, ..., v0.2.2].

Installation from main branch successful: composer require innocenzi/laravel-vite:dev-main
Maybe you forgot to release a new version?

Yes I didn't release, thanks for the heads up. v0.3.1 should work!
Note: you should, if you can, migrate to the official Vite integration from the Laravel team

Yes I didn't release, thanks for the heads up. v0.3.1 should work!
Note: you should, if you can, migrate to the official Vite integration from the Laravel team

thank you very much


feat: Add examples for Nutanix provider

added nutanix examples for clusterclass and cluster

@jimmidyson @faiq @dkoshkin @thunderboltsid any more comments? can we merge this?

For now, I think it would be better to have non-working minimal examples here and later down the line adding the proper code in the form of GeneratePatch hooks and Lifecycle hooks to get started.

For now, I think it would be better to have non-working minimal examples here and later down the line adding the proper code in the form of GeneratePatch hooks and Lifecycle hooks to get started.

yes thats the plan if i understand your comment correctly. is it not the case in this PR?

For now, I think it would be better to have non-working minimal examples here and later down the line adding the proper code in the form of GeneratePatch hooks and Lifecycle hooks to get started.

yes thats the plan if i understand your comment correctly. is it not the case in this PR?

we will remove ccm related things from the cluster-topology example yaml once we move ccm installation as addon thru post cluster creation step in ccm https://d2iq.atlassian.net/browse/D2IQ-99841

I strongly prefer to remove the CCM cluster resource sets from the examples.
I can live with the rest of the stuff not being patches.

could you please add more details on why you feel so strongly? would it not be ok with you if we do it thru above mentioned tracker? i think this is really minor change and does not really add value. mainly https://d2iq.atlassian.net/browse/D2IQ-99841. given we are still in dev phase, we should run in iterations. cc @jimmidyson

While I would prefer CCM to be added as an addon at this point, to keep this moving and to make it possible to create a Nutanix cluster using CAREN hooks, I agree we should merge this once it's working and do the refactoring as a follow up. This will unblock other work, such as testing Nutanix CSI, etc, and allow adding e2e tests, etc.

We don't need CCM to be enabled to be able to test CSI.

OK but CCM is required to bring a cluster fully up and make all nodes ready so it is still a blocker for e2e tests for Nutanix provider for example.

tests should fail until the code is complete.


Add dual-channel support

As presented in this comment: https://github.com/openai/whisper/discussions/1026#discussioncomment-5201398

by default, we re-record the file in .wav using mono because most of the lib expect mono only.


Create unqiue index for _id automatically

Description
Closes #2044, #1384.

Readiness checklist

[ ] I added/updated unit tests.
[x] I added/updated integration/compatibility tests.
[x] I added/updated comments and checked rendering.
[x] I made spot refactorings.
[ ] I updated user documentation.
[ ] I ran task all, and it passed.
[x] I ensured that PR title is good enough for the changelog.
[x] (for maintainers only) I set Reviewers (@FerretDB/core), Assignee, Labels, Project and project's Sprint fields.
[x] I marked all done items in this checklist.

@AlekSi because SetDocumentByID works with metadata table, and if we need to store data for the metadata table we can't use it. Ther is not metadata table for metadata table. I'll schedule a pair programming session with you, as it's not straightforward to me what exactly you consider useless.

@w84thesun could you specify the problems with the locks you see? I see PG times out, but it's quite expected: we started adding _id index for all the collections we create, so tests became slower. I think we should just increase the timeout for PG tests.

I did not say "useless", though. But there is a lot opportunity for refactoring (a.k.a. technical debt), and we should reduce it, not increase it. I don't believe that there is no opportunity for us to not have two very similar function doing two very similar things in the same package. We can do better, and we should.

@w84thesun could you specify the problems with the locks you see? I see PG times out, but it's quite expected: we started adding _id index for all the collections we create, so tests became slower. I think we should just increase the timeout for PG tests.

Yes, that's about timeout, not locks, I just started to read the output of the test from the end 😄


chore(api): update factory tests logging and smoothie handling

The data loss factory test gets spoofed by sending two crnls to smoothie,
which races with the smoothie's response and injects newlines into the data it
returns, breaking the test. Don't do this anymore.
Hide logging that confuses the line involving hard limits

Testing:

Run the tests on some robots, buildroot and balena, with default deck calibrations (i.e. rm /data/deck_calibration* first)

Also tested on wild-cloud, a build-root robot


Accounts for desired_channels > channels_in_file

With current implementation, loading jpg files with desired_channels set to RGBA would truncate the returned image to 3/4 of its original height. This PR fixes that.

Thanks for discovering this and submitting a patch.
I do all of the development work on the GitLab repo: https://gitlab.com/define-private-public/stb_image-Nim
Could you resubmit the PR/MR there?  Do you have a file/test that I could verify the issue and fix of it?

Sorry, I have been a bit busy over the last few days. I have added the test and submitted the MR on GitLab repo as requested.

Hi, sorry for the slow response (busy as well).  I'll be looking at it now.

Thanks for the fixup!  It's been merged and the version has been bumped on GitLab.


Update mma_invite.ics

thing that'll do it.
Signed-off-by: Rachel N<EMAIL_ADDRESS>Describe your changes in brief
Changes

[ ] Why is this change required? What problem does it solve?
[ ] If proposing a new change then please raise an issue first

How Has This Been Tested? (Optional)

[ ] Please describe in detail how you tested your changes.
[ ] Include details of your testing environment, and the tests you ran to
[ ] How your change affects other areas of the code, etc.

Screenshots (if appropriate)
Checklist

[ ] tested locally
[ ] added new dependencies
[ ] updated the docs
[ ] added a test

Thanks @novium258 !


Filter My Investment table for pools with small user balances ["dust"]

Added a filter to the usePoolsData get to filter out for small balances. Which is set in a the new constants file \beethovenx\constants\dust.ts
Before showing pools with small user balances:

After with filter:

I changed the constant to MINIMUM_DUST_VALUE_USD and did make it smaller. This particular value is just to remove from the tables, and I thought doing that in USD was better. For the rest of the dust filtering, deposit/withdraw/swapping, that would be done in shares, and a much smaller value. I questions about that so we can just put this on hold if you want.

gotcha, i missed the USD part


relap5 crash edits

Pull Request Description
What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)
Closes #317
What are the significant changes in functionality due to this change request?
realp5 interface

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[x] 1. Review all computer code. ok
[x] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts). n/a
[x] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details. ok
[x] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass. they pass
[x] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True. not a significant functionality
[x] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync. n/a
[x] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done. #317
[x] 8. If an analytic test is changed/added is the the analytic documentation updated/added? n/a

Comments addressed...
PR can be accepted.
Well done developer!

I made a small modification that should speed up the checking process. Let me know what do you think.

did you open a PR?

oh no, i have added that comment but it was already merged
what I changed was in the PR already

ok

Just for the record, did the last small modification get merged already, or does it need to be a new pull request?  Thanks.

the last modification was already included in the PR.
I added the comment prior refreshing my browser


Terminal hangs forever without jq

Current behavior
Whenever navigating to a node project my terminal would hang attempting to load the spaceship theme.
Installing jq solved the issue. I believe there may be issues with the fallbacks.
Expected behavior
Expected the non-jq package.json querying fallbacks to work. see https://github.com/denysdovhan/spaceship-prompt/compare/v3.10.0...v3.11.0#diff-5d757d19d3ecbe1198231a43380c2262
node as a command seems to work as shown in the first of the screenshots below.
Relevant Zsh configuration (.zshrc)
my zsh config can be found here - https://github.com/jthegedus/dotfiles/blob/master/zsh/.zshrc
Environment
Spaceship version: 3.11.0
Zsh version: zsh 5.5.1 (x86_64-ubuntu-linux-gnu)
Zsh framework: oh-my-zsh
Zsh plugin manager: zgen (latest)
Terminal emulator: GNOME Terminal
Operating system: Ubuntu 18.10
Screenshot
before installing jq

Ctrl+c results in the `$(spaceship_rprompt)
The terminal command syntax highlighting shows that I must Ctrl+c before I can get the terminal to execute another command.
node as a command works.
after installing jq

Installing jq solved the issue. I believe there may be issues with the fallbacks or could be something to do with how asdf-vm installs nodejs.

Could you apply this diff and post the output after that ?
diff --git a/sections/package.zsh b/sections/package.zsh
index 8795cd0..a505ad6 100644
--- a/sections/package.zsh
+++ b/sections/package.zsh
@@ -26,6 +26,7 @@ spaceship_package() {
   # Show package version only when repository is a package
   local 'package_version'

+  setopt xtrace
   if [[ -f package.json ]] && spaceship::exists npm; then
     if spaceship::exists jq; then
       package_version=$(jq -r '.version' package.json 2>/dev/null)
@@ -35,6 +36,7 @@ spaceship_package() {
       package_version=$(node -p "require('./package.json').version" 2> /dev/null)
     fi
   fi
+  unsetopt xtrace

   if [[ -f Cargo.toml ]] && spaceship::exists cargo; then
     # Handle missing field `version` in Cargo.toml.

Could you apply this diff and post the output with and without jq installed ?
diff --git a/sections/package.zsh b/sections/package.zsh
index 8795cd0..a505ad6 100644
--- a/sections/package.zsh
+++ b/sections/package.zsh
@@ -26,6 +26,7 @@ spaceship_package() {
   # Show package version only when repository is a package
   local 'package_version'

+  setopt xtrace
   if [[ -f package.json ]] && spaceship::exists npm; then
     if spaceship::exists jq; then
       package_version=$(jq -r '.version' package.json 2>/dev/null)
@@ -35,6 +36,7 @@ spaceship_package() {
       package_version=$(node -p "require('./package.json').version" 2> /dev/null)
     fi
   fi
+  unsetopt xtrace

   if [[ -f Cargo.toml ]] && spaceship::exists cargo; then
     # Handle missing field `version` in Cargo.toml.

I will give this a go when I get the chance, thanks for the guidance.

  setopt xtrace
  if [[ -f package.json ]] && spaceship::exists npm; then
    if spaceship::exists jq; then
      package_version=$(jq -r '.version' package.json 2>/dev/null)
    elif spaceship::exists python; then
      package_version=$(python -c "import json; print(json.load(open('package.json'))['version'])" 2>/dev/null)
    elif spaceship::exists node; then
      package_version=$(node -p "require('./package.json').version" 2> /dev/null)
    fi
  fi
  unsetopt xtrace

gave me this output:
~
➜ cd projects/dotfiles
+spaceship_package:7> [[ -f package.json ]]
+spaceship_package:7> spaceship::exists npm
+spaceship::exists:1> command -v npm
+spaceship_package:8> spaceship::exists jq
+spaceship::exists:1> command -v jq
+spaceship_package:10> spaceship::exists python
+spaceship::exists:1> command -v python
+spaceship_package:11> package_version=+spaceship_package:11> python -c 'import json; print(json.load(open('\''package.json'\''))['\''version'\''])'

This is where it hangs.

So commenting out the python bit and going with the node branch:
  setopt xtrace
  if [[ -f package.json ]] && spaceship::exists npm; then
    if spaceship::exists jq; then
      package_version=$(jq -r '.version' package.json 2>/dev/null)
    # elif spaceship::exists python; then
    #   package_version=$(python -c "import json; print(json.load(open('package.json'))['version'])" 2>/dev/null)
    elif spaceship::exists node; then
      package_version=$(node -p "require('./package.json').version" 2> /dev/null)
    fi
  fi
  unsetopt xtrace

gave me this output:
➜ cd dotfiles
+spaceship_package:7> [[ -f package.json ]]
+spaceship_package:7> spaceship::exists npm
+spaceship::exists:1> command -v npm
+spaceship_package:8> spaceship::exists jq
+spaceship::exists:1> command -v jq
+spaceship_package:12> spaceship::exists node
+spaceship::exists:1> command -v node
+spaceship_package:13> package_version=+spaceship_package:13> node -p 'require('\''./package.json'\'').version'
+spaceship_package:13> package_version=3.0.0
+spaceship_package:16> unsetopt xtrace

dotfiles on  master is 📦 v3.0.0 via ⬢ v10.15.3
➜

So node works fine, but python has some issues. I will investigate my python setup.

There was an issue with my python setup which was not allowing the python command to be run correctly.
Here is the output after fixing my python:
➜ cd projects/dotfiles
+spaceship_package:7> [[ -f package.json ]]
+spaceship_package:7> spaceship::exists npm
+spaceship::exists:1> command -v npm
+spaceship_package:8> spaceship::exists jq
+spaceship::exists:1> command -v jq
+spaceship_package:10> spaceship::exists python
+spaceship::exists:1> command -v python
+spaceship_package:11> package_version=+spaceship_package:11> python -c 'import json; print(json.load(open('\''package.json'\''))['\''version'\''])'
+spaceship_package:11> package_version=3.0.0
+spaceship_package:16> unsetopt xtrace

dotfiles on  master [!] is 📦 v3.0.0 via ⬢ v10.15.3

@salmanulfarzy thanks for your help diagnosing this. I barely use python so had not noticed that it wasn't setup correctly.

Glad it was resolved :v: Python had better performance than Node in parsing packge.json on our comparisons. For more regarding this see #439 #441


Adjust "Consortia" Seeding File Names to "Test" Seeding File

Description:
The current seeding files for the "Consortia" feature are named in a way that may not clearly indicate their purpose as test data. We need to rename these files to reflect that they are for testing environments and ensure they are segregated from release seed files.

Acceptance Criteria:

All seeding files currently named with the "consortia" prefix should be renamed with the "test" prefix.
Successfully tested the change
The renamed files are ideally located in a separate directory from production seed files to prevent accidental seeding in production environments.
Update all references to the "consortia" seeding files in the codebase to the new "test" prefixed file names.
Ensure that the seeding process still functions correctly after the file renaming, without any errors or data issues.
The changes should be documented, and the team should be informed of the new naming convention.

Proposed Test Cases:
Seeding Process Test:

Execute the seeding process with the renamed test files to ensure that there are no errors and the data is seeded as expected.
Confirm that the seeding process does not affect production databases and is isolated to the test environment.

consortia seeding files should be removed with the end of consortia, same for portal-backend

replaced by https://github.com/eclipse-tractusx/ssi-credential-issuer/issues/207


Liquibase 3.6.3 Has New Checksum Version, Prevents runOnChange="true"

Environment
Liquibase Version: 3.6.3
Liquibase Integration & Version: n/a, JAR file in Java project
Liquibase Extension(s) & Version: n/a
Database Vendor & Version: PostgreSQL 11.3
Operating System Type & Version: Windows 10
Description

Liquibase (3.6.3) is performing upgrade steps (changesets) against a database that was set up using Liquibase 3.5.3.
MD5sums in the DatabaseChangeLog are recorded as "7:....", which is apparently a "checksum version number".
Liquibase 3.6.3 apparently wants to use "checksum version number 8" now
Liquibase 3.6.3 has a chunk of code (StandardChangeLogHistoryService:244+) that checks the version number(s?) on existing MD5sum(s?), and if it is less than the new level (8), explicitly NULLs out all of the checksums in the database
Apparently, it expects the code to 'regenerate' the checksums using the 'new' version.

Unfortunately, this seems to lead to a logic error:

You have a script marked runOnChange="true"
You are moving up Liquibase versions, therefore the above comes into play
Liquibase determines the "onChange" part by comparing checksums...
...but the checksum has been regenerated using the new contents!

So the gist of the problem is:

If you change a script that says "run on change"
and you are moving up Liquibase versions where there is a checksum version change
you are screwed - the script will not rerun

Is this 'regenerate checksums' truly required?  Is there any way to disable it?
Steps To Reproduce
Please see the above for a description of the problem.  Basically:

Create a project using Liquibase 3.5.3
Write a changeset that has runOnChange="true"
Use Liquibase to create the database
The DatabaseChangeLog table will have your changeset with a md5sum starting with "7:"
Upgrade your project to use Liquibase 3.6.3
Change your changeset (from point #2)
Execute Liquibase against your database
The modified changeset will NOT run, inspite of runOnChange="true"

Actual Behavior
See problem description - the runOnChange="true" changeset does NOT rerun, even though it has been changed.
Expected/Desired Behavior
See problem description - the runOnChange="true" changeset SHOULD re-run, since it HAS been changed.
┆Issue is synchronized with this Jira Bug by Unito

@davelindquist-egistix Thanks for the detailed description of the issue.  It is much appreciated.  We will add this to our list of issues. As a workaround, maybe running a changeLogSync after upgrade and before making a change to an existing changeset might help you become unstuck for now?

The problem that we have is that there is no intermediate step between "upgrade Liquibase" and "run database patch scripts" as this is an application delivered to a client.  Thus even a 'changeLogSync' would presumably rewrite the checksums with the current (and incorrect/post-change) contents of the script.
As a workaround, I prefix any call to Liquibase updates with:

Find the current checksum version from Liquibase
Query the DatabaseChangeLog table for anything with an MD5Sum that is not  + ":"
Force update all of those records to have the NEW version number, keeping the same hash value.

This is not technically correct, because we haven't 'fixed' the hash value (that would be impossible), but it does work for us -- we have a (legacy) process that sits in front of Liquibase and doesn't feed any scripts to Liquibase unless they have already been determined to need a re-run (long story, legacy stuff).
However, for other users of Liquibase, there would literally be no possible solution.
I'm thinking that the 'right' thing to do here (I know, ivory tower) would be to have Liquibase support BOTH checksum versions -- so comparing a script checksum would:

Use whatever checksum was in the database, whatever version it was
Calculate the script checksum (for comparison) using whatever checksum version was used by the database record (which might mean using an old checksum version)
Only AFTER all of the scripts have been processed, regenerate checksums in the database (if needed or desired).
But of course that does add some extra complexity to the process.

Had the same problem. Thinking of workaround, because it's already happen.

after step "Upgrade your project to use Liquibase 3.6.3" you probably should not change any changesets and should immediately deploy this upgrade everythere.

This seems related to https://liquibase.jira.com/browse/CORE-3204


Highlight geocoder text on click

It would be nice to select the text previously entered into the geocoder so I can begin typing in a new location right away when I click the text box

I'm looking at this now.


PipeEventAttaching

Hi,
I noticed that such a mechanism is described:

// PipeEventAttaching is called before the Pipe is registered with the
// socket.  The intention is to permit the application to reject
// a pipe before it is attached.

Therefore, I wonder if the correct way to reject the client looks like this:
func pipeEventHook(action mangos.PipeEvent, pipe mangos.Pipe) {
   if action == mangos.PipeEventAttaching {
      pipe.close()
   }
}

If so, then why the client at the other end of the pipe receives the event PipeEventAttached?
Of course, he receives PipeEventDetached a moment later.
Nevertheless, it seems to me that it should not Attach in such a configuration in the first place.
Another thought.
I know I can get a remote IP and port of the client that is trying to Attache, to pipe.
Is there any other way to identify the client that connects to the server?
It would be ideal to have something like Hello msg. Message that is sent during Dial.
Without it, until client sends the first message, server knows who he is.

Pipe ID doesn't tell you anything about the peer.  The only way to really be sure is to use an authenticated connection.  TLS is the best option for mangos users at present.  (NNG does have a ZeroTier transport as an alternative, but that isn't Go code.)

Thank you.


Use latest base images.

Description:
The current Dockerfile uses the golang image of version 1.19 which is deprecated (c.f. https://endoflife.date/go) as well as the alpine image version 3.16 which is soon going to be deprecated (https://endoflife.date/alpine).
To always have the latest patched versions this PR changes the images to latest. If this is not desired, I would recommend that we at least use the latest version explicitly and update it.

Hi @anotherbridge, thanks for the PR.

If this is not desired, I would recommend that we at least use the latest version explicitly and update it.

I'd feel better pinning a version

can we get a version bump to include this change ?


opt optimize the number of threads of scanners, follow up #28640

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Graph Formatting

🐛 Describe the bug
Hi there! I'm a new user of this plugin (and Obsidian in general). I didn't see any Discussions tab, so I figured I'd ask here. From what I can gather, the file names are hashed in order to prevent collisions, so the links always match up properly (i.e. if you had multiple files named hello.md). However, now my graph looks like the following:

Is there some way to "prettify" the graph to make it understand what the files are supposed to be, maybe via reading the first header? Thanks a bunch in advance, and thanks for creating this plugin!
Versions
Latest version of Neovim nightly.

Hey @kylechui, as far as I know there's still no way to configure the graph that way. Alternatively you can customize the note naming function in Neovim to create more readable names. See https://github.com/epwalsh/obsidian.nvim#customizing-note-paths-and-ids. That's what I have in my personal configuration.

Thanks for the quick response; I think I'll settle for something like TOPIC_NAME_DATE or something like that.


horizontal bar chart drag x axis

Hi,
Thanks for your plugin, I found that with vertical bar chart the dragging works fine. However when I use the horizontal bar chart, it drags but along the Y axis, i.e. moving the mouse up and down, will move the horizontal bar left and right. I tried the DragX/Y options but did not get it to work, also putting DragData within the X/Y axis.
Also a smaller issue, was when I dragged to zero, I could not drag it out of zero, so I had to set the minimum to be 1 instead of 0.
Any fixes appreciated.
Thanks

Hi @carlgrayau,
Thanks for raising an issue!
So the underlying problem with the issue you are describing (also linked to https://github.com/chrispahm/chartjs-plugin-dragData/issues/19) is that bar charts were originally never within the scope of this plugin. That said, I was even surprised to learn that vertical bar charts are somewhat working.
I started fiddling around on a new branch, mainly because I wanted to get rid of the security vulnerabilities due to the old dependencies. I guess the horizontal bar charts should be working now, I will try to solve the issue with the stacked ones while I'm at it before I merge into master though
You can check out the working brach here:
https://github.com/chrispahm/chartjs-plugin-dragData/tree/bar-chart-fixes

@chrispahm thanks for the fix! works great!
Re Drag from 0 - I saw it working on your jsfiddle, but doesn't pick it up for me at 0.

Alright I just merged the changes into master, would be nice if you could have a look once again!
So about the drag from 0:
That's conceptually not easy, especially with bar charts. I mean what do you expect from a bar chart when a value is 0? Is guess we both agree, there shouldn't be a bar. Otherwise this would suggest that there still is a value > 0 for that variable, which would confuse users. Now that there is no actual bar drawn on canvas anymore (technically it's still there, it just doesn't have a height/width), it's also difficult to get a hold of it with the cursor or finger.
If you check out the example for the bar chart and drag one of the bars to 0, you can still get a hold of the bar afterwards if you hover right over the center of the data label (that's difficult to explain...).
From a UI perspective, that's terrible, because you have to 100% with your mouse in order to catch it. For the line charts, this can largely be fixed by increasing the value for the pointHitRadius in the dataset configuration. However, that options does not seem to be available for bar charts.
Best,
Christoph

Thanks Christoph,
Yep master is working fine!
Cheers for the update!
Carl

Ok thanks for confirming!
I guess about the 0 drag issue the best option I see is opening an issue on the Chart.js repo asking for a hitRadius option, or possible alternatives.
Cheers
Christoph

Hey Chris,
Re this, I found an option that helped me for 0 values, it was minBarLength which you can add. Don't know why the default wasn't working per a lot of examples, but this is a good fix.
Cheers
Carl

That's good to know! If you want to, it would be nice to have a jsFiddle, Plunker, ..., showing the difference, then I could make a reference in the readme for anyone interested in using this with bar charts.

Just as a reference, I made a fiddle showcasing how to use minBarLength with this plugin:
https://jsfiddle.net/nc0fh3su/2/
See #52 for discussion


bad test result

dear @jingyuanli001 , I really appreciate your great job. The result in your paper is amazing. Then I test my own image with your released pretrained model 'RFR_Net_pretrained/checkpoint_celeba.pth'.   But my result is bad. Can you help me?
the input are:

if I use my own mask, the result:

or:

if use the random mask(set mask_mode=1), the result:

dose it depends on the masks inputed?

using a mask with 1 indicating the hole region and 0 indicating the background should be adequate. But I am not sure if the result is going to be good when the image is not from the same distribution as CelebA

using a mask with 1 indicating the hole region and 0 indicating the background should be adequate. But I am not sure if the result is going to be good when the image is not from the same distribution as CelebA

thanks for your reply. My input mask fill the hole with 0, and fill other region with 255, and set mask_reverse = False.
if I set mask_reverse = True, then it means mask with 1 indicating the hole region and 0 indicating the background , but the result is worse, the output is not expected.

@tengshaofeng I have the same problem as you, have you solved it?

Do you solve the problem ?? I need the answer please !


Compatibility with websockets 10.x?

websockets is currently pinned with >=9.0. Poetry interprets that as >=9.0,<10.0.
Would it be possible to change it to >=9.0,<11.0? This would help resolve a dependency conflict for Home Assistant.
https://websockets.readthedocs.io/en/stable/project/changelog.html

Didn't saw that the dependency range was already updated, just not released yet.
https://github.com/Yakifo/amqtt/blob/8961b8fff57007a5d9907b98bc555f0519974ce9/pyproject.toml#L24


Readme enhancements

How we can improve our readme.md for show the features and documentation? Any ideas? @jairinhohw @juarezr @mariuz
I think we don't need more the firebird references.

I think we must explain the cargo features and how / when to use them in the readme, as there is no documentation in them at the moment.
Maybe create a new issue to review the features names too.

Something like:
Features
All features can be used at the same time if needed.
linking
Will use the dynamic library of the official fbclient at runtime and compiletime.
Used in systems where there is already a firebird client installed and configured.
dynamic_loading
Can find the official fbclient native library by path at runtime, does not need the library at compiletime.
Useful when you need to build in a system without a firebird client installed.
pure_rust
Uses a pure rust implementation of the firebird wire protocol, does not need the library at all.
Useful for cross-compilation and allow a single binary to be deployed without needing to install the firebird client.

@fernandobatels,
Maybe we should promote the strong points of using
FirebirdSQL with Rust in a section "Why you should use it!"  before the details of  "How to use it".
We can write a brief about the best selling points like:

A lean database server feature rich and with full SQL compliance embedded into 'your' app that are more powerful and faster than SQLite.
Pure ( no unsafe ) Rust connecting to FirebirdSQL.
etc...


Local images

Hi,
Great library!
I have noticed a new update to support local image and I am trying to use it.
Tried with the 'file:' + sourcePath but didn't manage to make it work.
Tried to do this:
const images = [{
url: 'file:../images/IMG.JPG'
}]
Is it possible ?
Thanks,
Ahikam

I don't have an environmental test right now, can you please try to debug this code: https://github.com/ascoders/react-native-image-viewer/blob/master/src/image-viewer.component.tsx#L148 ?
If it is startWith file:, it will set to load success.

Thats what we tried to do, used this file: from your last update.
Didn't manage to load the image on iPhone/Android.

@ahirag have you been able to display local images smoothly?

fix in version: 2.0.9


feat(app):  add wifi setting to robot settings

Overview
This PR is to make wifi setting components for unboxing flow available from RobotSettings and remove ODD menu from RobotSettings. I think we still need to keep ODD menu component for debug.
WifiConnectionDetails component that make available wifi settings from RobotSettings is messy right now. I will refactor this component by a following PR later.

Test Plan

Tap Settings
Tap NetworkSettings
Tap Wi-Fi
Try to set up wifi settings again

Changelog

update WifiConnectionDetails
update SetWifiCred header part  to align with the hi-fi RobotSettings
update SelectAuthenticationType header part to align with the hi-fi RobotSettings
remove ODD menu link from RobotSettings

Review requests

Risk assessment
low

[ ] merge https://github.com/Opentrons/opentrons/pull/12669

@shlokamin
https://github.com/Opentrons/opentrons/assets/474225/99a2e9c5-dbce-4f0d-a1d8-5057a287bd01


Middleware - Signing Issue Fix

Removed logic that would set nioRequest.head.uri to awsRequest.url.path + query.   nioRequest.head.uri will now be set to awsRequest.url.absoluteString.
Removed url: parameter from AWSClient.nioRequestWithSignedHeader(_:) in order to insure that all request transformations are handled by AWSRequest.toNIORequest().
These two changes were made in order to prevent the case in which AWSRequestMiddleware and Signer would receive different URLs.  (cough S3 cough)

@kyleishie ahoy! ok, excellent. Great work.
I am going to test this out - so the reason for not setting the header uri to the absoluteString is due to an issue with the aws ecs container credentials api that surfaced in the old httpClient used by this SDK (Prorsum). See https://github.com/noppoMan/Prorsum/issues/55
Using NIO now I am hopeful this is no longer an issue and we can merge this change.

@kyleishie looks good. after review, I clearly see the issue. great catch on the mismatch when using s3 middleware.
as for impact on the metadata service, there is a separate request method in that struct so it's irrelevant anyway.


removed my bad changes in trailes of chtulhu english + french + adapted my nights black agents folder

removed my pictures in the folder + html
-created sheet.css
-renamed styles to sheet-...
-transfered css styles from sheet.html to sheet.css
tried to remove my bad changed files in original trails of chthulhu and french version

There are a few things wrong with this:
You're deleting the images that the sheet uses, this will break the images on the sheet.
The sheets don't need the html, head, and body tags. Only the html inside of what wold be the body tag should be included.
You've moved the Trail of Cthulhu and the French version files all to the root directory, out of the folders they were in.

sorry for the moving out sheets that are not mine. Working on 2 different computers and different softwares do that + still trying to get used to github.
I will look at MY sheets (nights balck agents) and fix that.
+
The taking out images was intended, but don't bother. I will have another look.
I want to reduce the size of the sheet, so I will post my latest version again and fix according to your advice.


Appstudio update test-component-pac-acbq

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-component-pac-acbq-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
14 seconds
clone-repository

✅ Succeeded
39 seconds
build-container

✅ Succeeded
25 seconds
inspect-image

✅ Succeeded
25 seconds
deprecated-base-image-check

✅ Succeeded
44 seconds
clamav-scan

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
14 seconds
sbom-json-check

✅ Succeeded
16 seconds
label-check

✅ Succeeded
9 seconds
show-sbom

✅ Succeeded
9 seconds
show-summary

Pipelines as Code CI/test-component-pac-acbq-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
29 seconds
clone-repository

✅ Succeeded
55 seconds
build-container

✅ Succeeded
17 seconds
inspect-image

✅ Succeeded
16 seconds
deprecated-base-image-check

✅ Succeeded
35 seconds
clamav-scan

✅ Succeeded
10 seconds
clair-scan

✅ Succeeded
8 seconds
sbom-json-check

✅ Succeeded
14 seconds
label-check

✅ Succeeded
10 seconds
show-summary

✅ Succeeded
8 seconds
show-sbom


Updated development_guide.md

Signed-off-by: ErenYeager713<EMAIL_ADDRESS>

I have updated the changes in deployment_guide.md


Set jdk version to 8.

NetflixOSS » SimianArmy » SimianArmy-pull-requests #60 FAILURE
Looks like there's a problem with this pull request


Allow seeds to be passed to external calls for program signing

This adds the seeds parameter to external calls. This does not enable creating PDA style contracts yet, that will come in another PR.
This PR simply adds the seeds to contract.function{seeds: [ [ seed1 ], [ [ seed2 ]}(arg1, arg2);.

This adds the seeds parameter to external calls. This does not enable creating PDA style contracts yet, that will come in another PR.
This PR simply adds the seeds to contract.function{seeds: [ [ seed1 ], [ [ seed2 ]}(arg1, arg2);.

This is a weird syntax. Do we need to wrap the seeds with square brackets?

This adds the seeds parameter to external calls. This does not enable creating PDA style contracts yet, that will come in another PR.
This PR simply adds the seeds to contract.function{seeds: [ [ seed1 ], [ [ seed2 ]}(arg1, arg2);.

This is a weird syntax. Do we need to wrap the seeds with square brackets?

Yes, it's a slice of an slices of bytes. So you can do [ [ hex"12", hex"0000" ], [ "f", "o", "o", "b", "a", "r' ] ]. Those are two sets of seeds.


Custom Attributes Issue In Language Files

Laravel Version: 8.61.0
PHP Version: 7.4
Description:
Custom :attribute names are not fetched anymore from the attributes array of the resources/lang/xx/validation.php language file. It was working fine in version 8.57.0
Steps To Reproduce:
The rule:
public function rules()
{
    return [
        'lines.*.darabszam' => [
            'integer',
            'required',
            'min:1',
            'max:999999999999',
        ]
    ],
}

resources/lang/hu/validation.php
'attributes' => [
    'lines.*.darabszam' => 'Darabszám',
]

'custom' => [
    'lines.*.darabszam' => [
        'min' => 'A(z) :attribute -nak legalább ennyinek kell lennie: :min.',
    ]
]

It was still working in version 8.57.0

Thanks @derekmd

@derekmd Sorry for late reply. Thanks for the detailed description. This is an issue with Livewire >2.6.0. so Laravel works fine as you described. Waiting for a fix for Livewire.


Results for week of 3/6

Looks like you have a model id mismatch somewhere. I'd suggest double-checking that your submission and metadata match. - Alex


add BitVec support

This PR adds BitVec support to rkyv.

bitvec provides a foundational API for bitfields in Rust. It specializes standard-library data structures (slices, arrays, and vectors of bool) to use one-bit-per-bool storage, similar to std::bitset and std::vector in C++.

I modified https://github.com/rkyv/rkyv_contrib/pull/3 to directly implement Archive on BitVec instead of creating a wrapper type. While I was at it, I implemented it for the BitArray type too. Here are a few notes:

BitVec<T, O> now archives to ArchivedBitVec<Archived<T>, O> as opposed to https://github.com/rkyv/rkyv_contrib/pull/3 where it would archive to ArchivedBitVec<T, O> while using internally an ArchivedVec<Archived<T>>, which I think was incorrect behavior.

BitArray doesn't store the bit length because const generics are not stable yet, as explained in the bitvec docs. This means that an archived BitArray<usize, O> will not be equal to a BitArray<usize, O> if the size_XX cargo feature doesn't match the target's pointer width. This can be a big footgun so maybe removing the ArchivedBitArray implementation is the best decision until const generics are available.

I think implementing BitBox would require adding a bitvec feature to the ptr_meta crate. Indeed, we need to store an unsized BitSlice in ArchivedBox. The BitSpan docs, states that the Pointee trait could be defined as (usize, BitIdx<T::Mem>). However I don't think it's really important to support it as 99% of the people will be only using ArchivedBitVec anyway.

I moved a few things around to make it easier to cfg code in and out. Running tests currently gives a failure, could you take a look? I ran the tests with cargo test --no-default-features --features "bitvec size_32 alloc bitvec_alloc" -- bitvec.


[Question] How safe is it?

My Question. How safe is it?

@Akkihi
Hey mate,
I wouldn't recommend using this script at this stage.  The project is for educational purposes, and will be an ongoing work with a variety of libraries I haven't tested before.  I'm yet to add any life-like mouse movements, and a lot of the delays are just random ints to allow the window capture to keep up until I integrate multi-threading.

Thank you, this is a fairly comprehensive answer. I wanted to understand whether one of the libraries use injection or not, fortunately I got the answer - no. Knowing that the obfuscation and the launch of Python itself (as a virtual machine) is almost impossible to track in any way. If you do security, I think anticheat will not be able to find it for the next year. Moreover, not embedding in the game gives a very positive result. But for the future, who will read this, this question was written for the purpose of training and obtaining additional knowledge in the field of security of programs and anti-cheats. (OBS has a function for capturing with anti-cheats).


add prettier

This PR adds prettier for automated code formatting.
yarn run prettier for code formatting
yarn run prettier-list-different for listing files that are different to how prettier would format them (this is run in CI and fails if there are differences)

lgtm

\o/


Event handlers are not working on the "headerButtonRight"

Event handlers are not working on the "headerButtonRight" contentFor.
HTML
{{#contentFor "headerButtonRight"}}
    <button class="button button-icon icon ion-android-more-vertical" data-action="settingsMenu">
    </button>
  {{/contentFor}}

JS
'click [data-action=settingsMenu]': function (event, template) {
    console.log('ding!');
  }

Does not ding :(

Probably because the headerButtonRight region is rendered outside of your template? Try adding the event handler in your layout.


Remove "Relevance" filters from swag shop

Describe the bug
No matter which filter I select under "relevance"... I get to see JUST the mug

To Reproduce
Steps to reproduce the behavior:

Go to https://www.ensmerchshop.xyz/search/products
Click on an subtitle under 'Relevance'
See error

Expected behavior
There's not a lot of swag in the shop... I think we should just remove the entire "relevance" sectino from our frontend and not worry about tweaking for every edge case.
@jainkrati - maybe this is something Ramin can do quick?

nevermind, the problem seems resolved...