[Feature Request]: Working directory argument support

It would be nice if the action had a way of specifying a working directory where to look for the flake.nix file in case it's not in the repository's root.
Example use case: flake.nix file defined in dev folder containing only "development" dependencies, like in srid/haskell-flake.

It supports arbitrary arguments, which can include any flake reference you like.  In the case you describe:
- use: nicknovitski/nix-develop@v1
  with:
    arguments: ./dev

Or if you wanted to use that repository directly, it would be arguments: "github:srid/haskell-flake?dir=dev"


useKeyPress: keyboard repeat not working

Describe the Bug
With useKeyPress(), if I press and hold a key, the action only happens once. I need to specifically release and press it again.
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
I think this speaks for itself.
Expected behavior
I want to press the key, and have actions repeating while I keep it pressed.
Screenshots or Videos
No response
Platform

OS: MacOS
Browser: All
Version: 10.1.0

Additional context
No response

Hey @raarts
This is not how the API is supposed to work. It's a hook that returns a boolean. If you want a repeating action you need to come up with your own implementation like:
const interval = useRef();
const metaPressed = useKeyPressed(['meta']);

useEffect(() => {
  if (metaPressed) {
    interval.current = window.setInterval(doSomething, 100);
  } else {
    window.clearInterval(interval.current);
  }
}, [metaPressed])

(untested pseudo code)


changed hero section

hey @Srijita-Mandal i didnt get the points for this

hey @Srijita-Mandal i didnt get the points for this

I have added the tags. Check once again if you get the points.


Cannot start Realsense Viewer

librealsense
2.50.0 RELEASE

OS
Windows

Intel RealSense Viewer / Depth Quality Tool has crashed with the following error message:
GL_INVALID_VALUE - C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\common\opengl3.cpp:572

Hi @Lasweiga  There was a recent case of this error on Windows at https://github.com/IntelRealSense/librealsense/issues/10544#issuecomment-1138569631 that was resolved with the following steps.

Download and run the standalone 2.21.0 version of the RealSense Viewer (Intel.RealSense.Viewer.exe) from the 'Assets' file list at the link below.

https://github.com/IntelRealSense/librealsense/releases/tag/v2.21.0
Once downloaded, Intel.RealSense.Viewer.exe should be launched with a double-leftclick from the folder location on your computer that it was downloaded to and not the Viewer launch shortcut icon on the Windows desktop.

If the 2.21.0 version of the Viewer has launched successfully, close it and then launch the 2.50.0 version of the Viewer with the usual desktop launch icon.  The previous error should now be gone and the Viewer can launch normally.

@MartyG-RealSense . Thank you the info. I have done the steps but did not fix the issue. at all . The same error poped up when I  launched the realsense viewer v 2.50. Earlier version was running fine.
What would be the next step to resolve this? Thanks.

Thanks for testing.  Let's try the standalone Intel.RealSense.Viewer.exe from 2.49.0 next to check whether or not the problem is with the 2.50.0 Viewer specifically.
https://github.com/IntelRealSense/librealsense/releases/tag/v2.49.0

Hi @Lasweiga  Do you require further assistance with this case, please?  Thanks!

Hi Marty,
Sorry for the late reply. Unfortunately, the 2.49.0 version was behaving
exactly the same. See screenshots attached. I also made sure I got the
latest graphics driver installed, in case  problems with opengl, but did
not make any difference.
On Thu, 23 Jun 2022 at 17:01, MartyG-RealSense @.***>
wrote:

Hi @Lasweiga https://github.com/Lasweiga Do you require further
assistance with this case, please? Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/IntelRealSense/librealsense/issues/10586#issuecomment-1164029312,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIJDIECCC3HFSHFZO5Y4QDVQQDTVANCNFSM5YSNNDBA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Is the rs-capture example program, which also makes use of OpenGL graphics, able to launch please?  Instructions for launching this program on the Windows version of the RealSense SDK can be found at https://github.com/IntelRealSense/librealsense/issues/8024#issuecomment-747630656

Hi @Lasweiga  After reading the comment above, do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.


Add a function that prettifies image plotting

Write a function in helpers.py that:

uses the matplotlib.pyplot.imshow() function
uses pyplot options to make the plot prettier in some way
Any of the following could make the plot prettier, you can choose some or do all

Add a title
Add x and y labels
Choose a custom color palette (Kudos if it's colorblind compliant)
Display the x and y axes in lat / lon instead of pixels (requires a bit of math)

Add an example in jupyter_notebooks/ (you can edit tutorial.ipynb or make your own notebook) which shows how to call this function and the cool options you added.

I want to work on it


[IM]  Add empty command Support[TE3]

Problem
We don't have support for empty command body / status code only in IM.

Summary of Changes

Add support to empty command support per spec(See tests below)
Update command codegen
Adjust some error code

Tests
$ chip-device-ctrl
CHIP:CTL: SyncSetKeyValue on ExampleOpCredsCAKey
CHIP:IN: TransportMgr initialized
CHIP:DIS: Init admin pairing table with server storage.
CHIP:IN: local node id is 0x000000000001b669
CHIP:ZCL: Using ZAP configuration...
CHIP:ZCL: deactivate report event
CHIP:CTL: Getting operational keys
CHIP:CTL: Generating operational certificate for the controller
CHIP:CTL: Getting root certificate for the controller from the issuer
CHIP:CTL: SyncSetKeyValue on CHIPAdmin0
CHIP:CTL: Generating credentials
CHIP:CTL: Loaded credentials successfully
CHIP:DL: CHIP task running
CHIP:DL: Platform main loop started.
Chip Device Controller Shell

chip-device-ctrl > connect -ip <IP_ADDRESS> 20202021 1
Device is assigned with nodeid = 1
CHIP:BLE: Assigned local session key ID 0
CHIP:BLE: Sent PBKDF param request
CHIP:CTL: SyncSetKeyValue on StartKeyID
CHIP:EM: Received message of type 33 and protocolId 0
CHIP:BLE: Received PBKDF param response
CHIP:BLE: Sent spake2p msg1
CHIP:EM: Received message of type 35 and protocolId 0
CHIP:BLE: Received spake2p msg2
CHIP:BLE: Peer assigned session key ID 0
CHIP:BLE: Sent spake2p msg3
CHIP:IN: New pairing for device 0x0000000000000001, key 0!!
CHIP:CTL: Remote device completed SPAKE2+ handshake

CHIP:CTL: Sending OpCSR request to 0x1f5f3f0 device
CHIP:DMG: ICR moving to [Initialize]
CHIP:DMG: ICR moving to [AddCommand]
CHIP:IN: Secure message was encrypted: Msg ID 1
CHIP:IN: Sending msg from 0x000000000001b669 to 0x0000000000000001 at utc time: 279380120 msec
CHIP:IN: Sending secure msg on generic transport
CHIP:IN: Secure msg send status No Error
CHIP:DMG: ICR moving to [   Sending]
CHIP:CTL: Sent OpCSR request, waiting for the CSR
CHIP:IN: Secure transport received message destined to node ID (112233)
CHIP:IN: Setting fabricID 1 on admin.
CHIP:IN: Since admin was modified, persisting changes to KVS
CHIP:CTL: SyncSetKeyValue on CHIPAdmin0
CHIP:EM: Received message of type 9 and protocolId 327680
CHIP:DMG: InvokeCommand =
CHIP:DMG: {
CHIP:DMG:       CommandList =
CHIP:DMG:       [
CHIP:DMG:               CommandDataElement =
CHIP:DMG:               {
CHIP:DMG:                       CommandPath =
CHIP:DMG:                       {
CHIP:DMG:                               EndpointId = 0x0,
CHIP:DMG:                               ClusterId = 0x3e,
CHIP:DMG:                               CommandId = 0x5,
CHIP:DMG:                       },
CHIP:DMG:
CHIP:DMG:                       CommandData =
CHIP:DMG:                       {
CHIP:DMG:                               0x0 = [
CHIP:DMG:                                       0x30, 0x81, 0xc9, 0x30, 0x70, 0x2, 0x1, 0x0, 0x30, 0xe, 0x31, 0xc, 0x30, 0xa, 0x6, 0x3, 0x55, 0x4, 0xa, 0xc, 0x3, 0x43, 0x53, 0x52, 0x30, 0x59, 0x30, 0x13, 0x6, 0x7, 0x2a, 0x86, 0x48, 0xce, 0x3d, 0x2, 0x1, 0x6, 0x8, 0x2a, 0x86, 0x48, 0xce, 0x3d, 0x3,
CHIP:DMG:                       ]
CHIP:DMG:                               0x1 = [
CHIP:DMG:                                       0x3d, 0x8f, 0xc7, 0x26, 0xfa, 0x79, 0x9e, 0x5e, 0x84, 0xca, 0x74, 0xd9, 0x2f, 0xc7, 0x8b, 0xb7, 0xe, 0x30, 0x88, 0xd3, 0x17, 0x96, 0x2c, 0x88, 0x3d, 0xaf, 0xd1, 0xeb, 0xfd, 0x2f, 0xdd, 0x25,
CHIP:DMG:                       ]
CHIP:DMG:                               0x2 = [
CHIP:DMG:
CHIP:DMG:                       ]
CHIP:DMG:                               0x3 = [
CHIP:DMG:
CHIP:DMG:                       ]
CHIP:DMG:                               0x4 = [
CHIP:DMG:
CHIP:DMG:                       ]
CHIP:DMG:                               0x5 = [
CHIP:DMG:
CHIP:DMG:                       ]
CHIP:DMG:                       },
CHIP:DMG:               },
CHIP:DMG:
CHIP:DMG:       ],
CHIP:DMG:
CHIP:DMG: }
CHIP:ZCL: Received Cluster Command: Cluster=3e Command=5 Endpoint=0

Note command specified response command still contains path
CHIP:ZCL: OpCSRResponse:
CHIP:ZCL:   CSR: 204
CHIP:ZCL:   CSRNonce: 32
CHIP:ZCL:   VendorReserved1: 0
CHIP:ZCL:   VendorReserved2: 0
CHIP:ZCL:   VendorReserved3: 0
CHIP:ZCL:   Signature: 0
CHIP:CTL: Received certificate signing request from the device
CHIP:CTL: Generating operational certificate for device 1
CHIP:CTL: Getting intermediate CA certificate from the issuer
CHIP:CTL: GetIntermediateCACertificate returned 4190
CHIP:CTL: Intermediate CA is not needed
CHIP:CTL: Sending operational certificate to the device. Op Cert Len 253, ICA Cert Len 0
CHIP:DMG: ICR moving to [Initialize]
CHIP:DMG: ICR moving to [AddCommand]
CHIP:IN: Secure message was encrypted: Msg ID 2
CHIP:IN: Sending msg from 0x000000000001b669 to 0x0000000000000001 at utc time: 279380135 msec
CHIP:IN: Sending secure msg on generic transport
CHIP:IN: Secure msg send status No Error
CHIP:DMG: ICR moving to [   Sending]
CHIP:CTL: Sent operational certificate to the device
CHIP:EM: Sending Standalone Ack for MsgId:00000001
CHIP:IN: Secure message was encrypted: Msg ID 3
CHIP:IN: Sending msg from 0x000000000001b669 to 0x0000000000000001 at utc time: 279380135 msec
CHIP:IN: Sending secure msg on generic transport
CHIP:IN: Secure msg send status No Error
CHIP:EM: Flushed pending ack for MsgId:00000001
CHIP:ZCL: DefaultResponse:
CHIP:ZCL:   Transaction: 0x7f091b8ec5c8
CHIP:ZCL:   status: EMBER_ZCL_STATUS_SUCCESS (0x00)
CHIP:ZCL: emberAfDefaultResponseCallback: Missing success callback
CHIP:ZCL: emberAfDefaultResponseCallback: Missing failure callback
CHIP:DMG: ICR moving to [Uninitiali]
CHIP:IN: Secure transport received message destined to node ID (112233)
CHIP:EM: Received message of type 9 and protocolId 327680
CHIP:DMG: InvokeCommand =
CHIP:DMG: {
CHIP:DMG:       CommandList =
CHIP:DMG:       [
CHIP:DMG:               CommandDataElement =
CHIP:DMG:               {
CHIP:DMG:                       StatusElement =
CHIP:DMG:                       {
CHIP:DMG:                               GeneralCode = 0x0,
CHIP:DMG:                               ProtocolId = 0x5,
CHIP:DMG:                               protocolCode = 0x0,
CHIP:DMG:                       },
CHIP:DMG:
CHIP:DMG:               },
CHIP:DMG:
CHIP:DMG:       ],
CHIP:DMG:
CHIP:DMG: }

Note this command element no longer contains path
SetCommandIndexStatus commandHandle=139677093775096 commandIndex=1
CHIP:EM: Sending Standalone Ack for MsgId:00000002
CHIP:IN: Secure message was encrypted: Msg ID 4
CHIP:IN: Sending msg from 0x000000000001b669 to 0x0000000000000001 at utc time: 279380139 msec
CHIP:IN: Sending secure msg on generic transport
CHIP:IN: Secure msg send status No Error
CHIP:EM: Flushed pending ack for MsgId:00000002
CHIP:ZCL: DefaultResponse:
CHIP:ZCL:   Transaction: 0x7f091b8ec6f8
CHIP:ZCL:   status: EMBER_ZCL_STATUS_SUCCESS (0x00)
CHIP:CTL: Device confirmed that it has received the operational certificate
CHIP:CTL: Sending root certificate to the device
CHIP:DMG: ICR moving to [Initialize]
CHIP:DMG: ICR moving to [AddCommand]
CHIP:IN: Secure message was encrypted: Msg ID 5
CHIP:IN: Sending msg from 0x000000000001b669 to 0x0000000000000001 at utc time: 279380139 msec
CHIP:IN: Sending secure msg on generic transport
CHIP:IN: Secure msg send status No Error
CHIP:DMG: ICR moving to [   Sending]
CHIP:CTL: Sent root certificate to the device
CHIP:DMG: ICR moving to [Uninitiali]
CHIP:IN: Secure transport received message destined to node ID (112233)
CHIP:EM: Received message of type 9 and protocolId 327680
CHIP:DMG: InvokeCommand =
CHIP:DMG: {
CHIP:DMG:       CommandList =
CHIP:DMG:       [
CHIP:DMG:               CommandDataElement =
CHIP:DMG:               {
CHIP:DMG:                       StatusElement =
CHIP:DMG:                       {
CHIP:DMG:                               GeneralCode = 0x0,
CHIP:DMG:                               ProtocolId = 0x5,
CHIP:DMG:                               protocolCode = 0x0,
CHIP:DMG:                       },
CHIP:DMG:
CHIP:DMG:               },
CHIP:DMG:
CHIP:DMG:       ],
CHIP:DMG:
CHIP:DMG: }

Note this command element no longer contains path
SetCommandIndexStatus commandHandle=139677093774792 commandIndex=1
CHIP:EM: Sending Standalone Ack for MsgId:00000003
CHIP:IN: Secure message was encrypted: Msg ID 6
CHIP:IN: Sending msg from 0x000000000001b669 to 0x0000000000000001 at utc time: 279380143 msec
CHIP:IN: Sending secure msg on generic transport
CHIP:IN: Secure msg send status No Error
CHIP:EM: Flushed pending ack for MsgId:00000003
CHIP:ZCL: DefaultResponse:
CHIP:ZCL:   Transaction: 0x7f091b8ec5c8
CHIP:ZCL:   status: EMBER_ZCL_STATUS_SUCCESS (0x00)
CHIP:CTL: Device confirmed that it has received the root certificate
CHIP:CTL: Operational credentials provisioned on device 0x1f5f3f0
CHIP:CTL: SyncSetKeyValue on PairedDevice1
CHIP:CTL: SyncSetKeyValue on ListPairedDevices0
CHIP:CTL: SyncSetKeyValue on StartKeyID
Secure Session to Device Established
CHIP:DMG: ICR moving to [Uninitiali]
Device temporary node id (**this does not match spec**): 1
chip-device-ctrl > zcl OnOff On 1 1 0
CHIP:DMG: ICR moving to [Initialize]
CHIP:DMG: ICR moving to [AddCommand]
CHIP:IN: Connection from 'UDP:<IP_ADDRESS>:11097' expired
CHIP:CTL: OnConnectionExpired was called for unknown device, ignoring it.
CHIP:IN: New pairing for device 0x0000000000000001, key 0!!
CHIP:IN: Secure message was encrypted: Msg ID 1
CHIP:IN: Sending msg from 0x000000000001b669 to 0x0000000000000001 at utc time: 279386910 msec
CHIP:IN: Sending secure msg on generic transport
CHIP:IN: Secure msg send status No Error
CHIP:DMG: ICR moving to [   Sending]
CHIP:IN: Secure transport received message destined to node ID (112233)
CHIP:EM: Received message of type 9 and protocolId 327680
CHIP:DMG: InvokeCommand =
CHIP:DMG: {
CHIP:DMG:       CommandList =
CHIP:DMG:       [
CHIP:DMG:               CommandDataElement =
CHIP:DMG:               {
CHIP:DMG:                       StatusElement =
CHIP:DMG:                       {
CHIP:DMG:                               GeneralCode = 0x0,
CHIP:DMG:                               ProtocolId = 0x5,
CHIP:DMG:                               protocolCode = 0x0,
CHIP:DMG:                       },
CHIP:DMG:
CHIP:DMG:               },
CHIP:DMG:
CHIP:DMG:       ],
CHIP:DMG:
CHIP:DMG: }

Note this command element no longer contains path
SetCommandIndexStatus commandHandle=139677093774792 commandIndex=1
CHIP:EM: Sending Standalone Ack for MsgId:00000004
CHIP:IN: Secure message was encrypted: Msg ID 2
CHIP:IN: Sending msg from 0x000000000001b669 to 0x0000000000000001 at utc time: 279386913 msec
CHIP:IN: Sending secure msg on generic transport
CHIP:IN: Secure msg send status No Error
CHIP:EM: Flushed pending ack for MsgId:00000004
CHIP:ZCL: DefaultResponse:
CHIP:ZCL:   Transaction: 0x7f091b8ec5c8
CHIP:ZCL:   status: EMBER_ZCL_STATUS_SUCCESS (0x00)
CHIP:ZCL: emberAfDefaultResponseCallback: Missing success callback
CHIP:ZCL: emberAfDefaultResponseCallback: Missing failure callback
CHIP:DMG: ICR moving to [Uninitiali]
Received command status response:
Container:
    GeneralCode = 0
    ProtocolId = 5
    ProtocolCode = 0
    CommandIndex = 1
chip-device-ctrl > zcl OnOff On 1 0 0
CHIP:DMG: ICR moving to [Initialize]
CHIP:DMG: ICR moving to [AddCommand]
CHIP:IN: Secure message was encrypted: Msg ID 3
CHIP:IN: Sending msg from 0x000000000001b669 to 0x0000000000000001 at utc time: 279405629 msec
CHIP:IN: Sending secure msg on generic transport
CHIP:IN: Secure msg send status No Error
CHIP:DMG: ICR moving to [   Sending]
CHIP:IN: Secure transport received message destined to node ID (112233)
CHIP:EM: Received message of type 9 and protocolId 327680
CHIP:DMG: InvokeCommand =
CHIP:DMG: {
CHIP:DMG:       CommandList =
CHIP:DMG:       [
CHIP:DMG:               CommandDataElement =
CHIP:DMG:               {
CHIP:DMG:                       StatusElement =
CHIP:DMG:                       {
CHIP:DMG:                               GeneralCode = 0xc,
CHIP:DMG:                               ProtocolId = 0x0,
CHIP:DMG:                               protocolCode = 0xffff,
CHIP:DMG:                       },
CHIP:DMG:
CHIP:DMG:               },
CHIP:DMG:
CHIP:DMG:       ],
CHIP:DMG:
CHIP:DMG: }

Note this command element no longer contains path
SetCommandIndexStatus commandHandle=139677093774792 commandIndex=1
CHIP:ZCL: DefaultResponse:
CHIP:ZCL:   Transaction: 0x7f091b8ec5c8
CHIP:ZCL:   status: EMBER_ZCL_STATUS_FAILURE (0x01)
CHIP:ZCL: emberAfDefaultResponseCallback: Missing success callback
CHIP:ZCL: emberAfDefaultResponseCallback: Missing failure callback
CHIP:EM: Sending Standalone Ack for MsgId:00000005
CHIP:IN: Secure message was encrypted: Msg ID 4
CHIP:IN: Sending msg from 0x000000000001b669 to 0x0000000000000001 at utc time: 279405634 msec
CHIP:IN: Sending secure msg on generic transport
CHIP:IN: Secure msg send status No Error
CHIP:EM: Flushed pending ack for MsgId:00000005
CHIP:ZCL: DefaultResponse:
CHIP:ZCL:   Transaction: 0x7f091b8ec5c8
CHIP:ZCL:   status: EMBER_ZCL_STATUS_SUCCESS (0x00)
CHIP:ZCL: emberAfDefaultResponseCallback: Missing success callback
CHIP:ZCL: emberAfDefaultResponseCallback: Missing failure callback
Received command status response:
CHIP:DMG: ICR moving to [Uninitiali]
Container:
    GeneralCode = 12
    ProtocolId = 0
    ProtocolCode = 65535
    CommandIndex = 1
chip-device-ctrl >

Device side:
...
CHIP:DMG: ICR moving to [Initialize]
CHIP:DMG: InvokeCommand =
CHIP:DMG: {
CHIP:DMG:       CommandList =
CHIP:DMG:       [
CHIP:DMG:               CommandDataElement =
CHIP:DMG:               {
CHIP:DMG:                       CommandPath =
CHIP:DMG:                       {
CHIP:DMG:                               EndpointId = 0x1,
CHIP:DMG:                               ClusterId = 0x6,
CHIP:DMG:                               CommandId = 0x1,
CHIP:DMG:                       },
CHIP:DMG:
CHIP:DMG:               },
CHIP:DMG:
CHIP:DMG:       ],
CHIP:DMG:
CHIP:DMG: }
CHIP:DMG: Received empty command for cluster 6
CHIP:ZCL: Received Cluster Command: Cluster=6 Command=1 Endpoint=1
CHIP:ZCL: On/Off set value: 1 1
CHIP:ZCL: Toggle on/off from 0 to 1
CHIP:DMG: ICR moving to [AddCommand]
....

Note it does not contains command body
Fixes #6988

One other thing: The encoding spec currently has InvokeRequestMessage take an "Array of CommandDataElement", with CommandDataElement being either Data or StatusCode.  This doesn't match how InvokeRequest actually works in the interaction model, afaict; it can never have StatusCode there.  The encoding spec is pretty far off here and needs to be fixed.
For InvokeResponse, there can be a status, but that status includes a path in the IM spec (see CommandStatusIB), if we get far enough that we are actually ending up with an InvokeResponse at all.


Upgrade pyparsing from 2.2.0 to 2.2.1

From https://github.com/pyparsing/pyparsing/blob/pyparsing_2.2.1/pyparsing.py, released today.
https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.2.1 says the release contains:

Updates to migrate source repo to GitHub
Fix deprecation warning in Python 3.7 re: importing collections.abc
Fix Literal/Keyword bug raising IndexError instead of ParseException

The deprecation warning is reported in https://github.com/pypa/pip/issues/5013 and was fixed upstream in https://github.com/pyparsing/pyparsing/pull/16.

Closing, PR was meant to go upstream.


Pet has a stroke

If you spam balls, the pet will eventually start to have a stroke. The ball speed also gets turned up waaaaay too high.
https://user-images.githubusercontent.com/14863373/155206330-2c5abab0-8fa5-45a5-8f39-09f46e45f025.mp4

I will have a look at this

Lol. Poor thing doesn't know which one to chase.

@tonybaloney where is the throw ball code - as I am working on this issue, I have tried rewriting the throwBall command as stated in this switch statement called by the webview after running the vscode-pets.throw-ball command. I have even tried removing this command altogether but the ball still throws. I was just wondering where is the code to throw the ball as seen in the webview during initiation of the command

Fixed in #167


How to paginate data in the Json file?

I want to paginate data in the Json file.

posts.json  file example:

[
   {
      "title":"title01",
      "img":"img_url01",
      "url":"url01"
   },
   {
      "title":"title02",
      "img":"img_url02",
      "url":"url02"
   },
   {
      "title":"title03",
      "img":"img_url03",
      "url":"url03"
   },
   {
      "title":"title04",
      "img":"img_url04",
      "url":"url04"
   },
   {
      "title":"title05",
      "img":"img_url05",
      "url":"url05"
   },
   {
      "title":"title06",
      "img":"img_url06",
      "url":"url06"
   }
]

page.vue file:

<template>
    <Layout>

          {{ post.img }}
          {{ post.title }}
          {{ post.url }}

    </Layout>
</template>

<page-query>
query {
  allJsonContent {
    edges {
      node {
        id
        data {
          title
          img
          url
        }
      }
    }
  }
}
</page-query>

I tried the tutorial in the https://gridsome.org/docs/pagination/, but failed.
query($page: Int) {
  allJsonContent(perPage: 3, page: $page) @paginate {
    pageInfo {
      totalPages
      currentPage
    }
    edges {
      node {
        id
        path
        data {
          title
          img
          url
        }
      }
    }
  }
}

How should I modify it? Thank you!

I can confirm the issue. I think the issue is that the Json is recognized as one node (see screenshot):

@RankinKeanan @eclectic-coding Are you using the source-filesystem plugin? I believe that Gridsome thinks you would have multiple files, i.e. post1.json post2.json etc. So all the JSON in one file will be added as one node.
You can solve this by using the store api to add the data from one file, rather than using the source filesystem plugin. Something like this example, but your data would be from const data = require('./path/to/posts.json')


Explain limitations of useSyncExternalStore with concurrency

Doesn't seem like we have this noted anywhere.

(@acdlite if you wouldn't mind checking the accuracy/completeness of my explanation)


RabbitMQ Unable to Communicate with Other Nodes

I have a cluster of EC2 instances setup with a service tag that allows RabbitMQ to identify cluster nodes (and is properly able to), however when attempting to communicate with the nodes RabbitMQ encounters an error:
autocluster: List of registered nodes retrieved from the backend: ['rabbit@ip-<address1>',
'rabbit@ip-<address2>',
'rabbit@ip-<address3>']

autocluster: Fetching node details. Responses: [{badrpc,
{'EXIT',
{noproc,
{gen_server,call,
[rabbit_node_monitor,
partitions,infinity]}}}}]

Google turned up nothing, so I'm not sure where to start.  I've opened up all ports on my EC2 instances thinking I had forgotten a port, but that hasn't helped.  Any ideas?

This plugin was forked by the RabbitMQ team and is now part of RabbitMQ. More information can be found @ https://github.com/rabbitmq/rabbitmq-autocluster


Refactor misc parts

(clearDOM) replace setTimeout with requestAnimationFrame

Nicer when it updated faster

(customElementHMR) : refactor - set cache to CustomElementRegistry

@kyr0 what do you think, keeping the cache  for HMR under CustomElementRegistry ?
Feels cleaner

Hi :)
hmm yeah, the idea is good, but... Yesterday I had the same idea in mind, but I wasn't sure if the global object CustomElementRegistry is writable for properties in all browsers.
I remember when I tried to polyfill console in IE some years ago and ran into an error with a live system because I lacked tests for this browser/feature combination. In all major browsers I could polyfill it, except IE. That taught me a painful lesson. So as of my knowledge, internal API's are not standardized to be mutable. So we cannot surely know if today or at some point in time in the future an internal implementation like that changes and the object becomes sealed.
For the same reason I reverted my caching method where I stored the pointer to the last impl. constructor on the defined impl. itself.
What do you think?

Agree, hard to say if someone will seal it in a browser update and break everything.
Lets it like we had it on window.
Should we rename the variable ? customElementCache
Any comments about using the requestAnimation ?

@kyr0
Just did a update, have a look.
Still have "dist" in gitignore until we are more ready

Looks good to me :)


Added some lunar spells + 2 standard teleports

Added Lumbridge + Falador teleport
Added qp requirement + gp cost for lunars/plank make
Added Spin flax spell, tan leather spell, string jewellery spell (Doesn't apply to silver amulet (u) jewellery atm), Plank make spell & recharge dragonstone spell.
Could be done much better but I just wanted to attempt to at least get them added even in a basic way - Doesn't check for Fremmy hard on Tan leather and recharge dragonstone
Description:

Changes:

Other checks:

[ ] I have tested all my changes thoroughly.

Tiz accidentally committed stuff that wasn't supposed to be in this PR and is making a new branch since easier to solve. Therefor closing this. <3


TypeError: 'NoneType' object is not subscriptable, in rpn_head.py

Describe the bug
Error raised:
File "~/.local/lib/python3.6/site-packages/mmdet-1.0rc1+cd0d37c-py3.6-linux-x86_64.egg/mmdet/models/anchor_heads/rpn_head.py", line 53, in loss
loss_rpn_cls=losses['loss_cls'], loss_rpn_bbox=losses['loss_bbox'])
TypeError: 'NoneType' object is not subscriptable
traceback:

cls_reg_targets is None in mmdet/models/anchor_heads/anchor_head.py#L178
expression “any([labels is None for labels in all_labels])” is True in mmdet/core/anchor/anchor_target.py#L65
condition "if not inside_flags.any():" satisfied in mmdet/core/anchor/anchor_target.py#L106
all valid flags positions exceed boundary in mmdet/core/anchor/anchor_target.py#L168

I guess:  all positions/locations are not valid,  or exceed image boundaries.
So what happens? Is there something wrong with the input data?  Is the input image too small?
The pipelines are as below:
104 train_pipeline = [
105     dict(type='LoadImageFromFile'),
106     dict(type='LoadAnnotations', with_bbox=True),
107     dict(type='Resize', img_scale=(1333, 800), keep_ratio=True),
108     dict(type='RandomFlip', flip_ratio=0.5),
109     dict(type='Normalize', **img_norm_cfg),
110     dict(type='Pad', size_divisor=32),
111     dict(type='DefaultFormatBundle'),
112     dict(type='Collect', keys=['img', 'gt_bboxes', 'gt_labels']),
113 ]
Reproduction

What command or script did you run?

I modified the original code for my own purpose, the command is not important. We can assume I run a faster rcnn without FPN but with RPN and BBox Head on ImageNet DET dataset.

Did you make any modifications on the code or config? Did you understand what you have modified?

My modification is irrelevant to this Error after my careful consideration, that is why I am here to ask a question.

What dataset did you use?

ImageNet DET.
Environment

Please run python tools/collect_env.py to collect necessary environment infomation and paste it here.

It is not a environment relevant problem.

You may add addition that may be helpful for locating the problem, such as

It is not a environment relevant problem.
Error traceback
If applicable, paste the error trackback here.
traceback:
- cls_reg_targets is None in mmdet/models/anchor_heads/anchor_head.py#L178
- expression “any([labels is None for labels in all_labels])” is True in mmdet/core/anchor/anchor_target.py#L65
- condition "if not inside_flags.any():" satisfied in mmdet/core/anchor/anchor_target.py#L106
- all valid flags positions exceed boundary in mmdet/core/anchor/anchor_target.py#L168

RPN does not generate any valid proposals, which is most likely to be caused by improper hyper-parameters so that the model is not trained well. The provided configs are designed for COCO dataset.

RPN does not generate any valid proposals, which is most likely to be caused by improper hyper-parameters so that the model is not trained well. The provided configs are designed for COCO dataset.

Sorry, I don't think it is hyper params problem yeilding null rpn proposals. The Error happens before loss function, where rpn scores feature maps are firstly used. It seems that there are problems in anchors generation.

Before loss function, the anchors are not well generated.

If inside_flags are all False, then there is no anchors inside the image boundary. You may check the image size and anchor sizes. You may set allowed_border to -1 to skip the condition, but it may not be a nice solution.

The anchors size is scale[8] and ratios[0.5, 1.0, 2.0 ], the input image size of the error is (img: 187 1333, pad: 192 1344). Maybe the input size is too small to generate any anchors.
It is better to add assertion with message to warn users about this.

Yes agree.

I got the same error TypeError: 'NoneType' object is not subscriptable with different traceback.
Traceback (most recent call last):   File "tools/train.py", line 188, in <module>     main()   File "tools/train.py", line 177, in main     train_detector(   File "/home/wellchecked/cbn/CBNetV2/mmdet/apis/train.py", line 185, in train_detector     runner.run(data_loaders, cfg.workflow)   File "/home/wellchecked/cbn/lib/python3.8/site-packages/mmcv/runner/epoch_based_runner.py", line 127, in run     epoch_runner(data_loaders[i], **kwargs)   File "/home/wellchecked/cbn/lib/python3.8/site-packages/mmcv/runner/epoch_based_runner.py", line 47, in train     for i, data_batch in enumerate(self.data_loader):   File "/home/wellchecked/cbn/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 521, in __next__     data = self._next_data()   File "/home/wellchecked/cbn/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 1203, in _next_data     return self._process_data(data)   File "/home/wellchecked/cbn/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 1229, in _process_data     data.reraise()   File "/home/wellchecked/cbn/lib/python3.8/site-packages/torch/_utils.py", line 425, in reraise     raise self.exc_type(msg) TypeError: Caught TypeError in DataLoader worker process 0. Original Traceback (most recent call last):   File "/home/wellchecked/cbn/lib/python3.8/site-packages/torch/utils/data/_utils/worker.py", line 287, in _worker_loop     data = fetcher.fetch(index)   File "/home/wellchecked/cbn/lib/python3.8/site-packages/torch/utils/data/_utils/fetch.py", line 44, in fetch     data = [self.dataset[idx] for idx in possibly_batched_index]   File "/home/wellchecked/cbn/lib/python3.8/site-packages/torch/utils/data/_utils/fetch.py", line 44, in <listcomp>     data = [self.dataset[idx] for idx in possibly_batched_index]   File "/home/wellchecked/cbn/CBNetV2/mmdet/datasets/custom.py", line 194, in __getitem__     data = self.prepare_train_img(idx)   File "/home/wellchecked/cbn/CBNetV2/mmdet/datasets/custom.py", line 217, in prepare_train_img     return self.pipeline(results)   File "/home/wellchecked/cbn/CBNetV2/mmdet/datasets/pipelines/compose.py", line 40, in __call__     data = t(data)   File "/home/wellchecked/cbn/CBNetV2/mmdet/datasets/pipelines/loading.py", line 371, in __call__     results = self._load_masks(results)   File "/home/wellchecked/cbn/CBNetV2/mmdet/datasets/pipelines/loading.py", line 323, in _load_masks     [self._poly2mask(mask, h, w) for mask in gt_masks], h, w)   File "/home/wellchecked/cbn/CBNetV2/mmdet/datasets/pipelines/loading.py", line 323, in <listcomp>     [self._poly2mask(mask, h, w) for mask in gt_masks], h, w)   File "/home/wellchecked/cbn/CBNetV2/mmdet/datasets/pipelines/loading.py", line 281, in _poly2mask     elif isinstance(mask_ann['counts'], list): TypeError: 'NoneType' object is not subscriptable

I got the same error with a different traceback. Any idea what's going on here?
/mmdet/datasets/pipelines/loading.py", line 323, in <listcomp>     [self._poly2mask(mask, h, w) for mask in gt_masks], h, w)
mmdet/datasets/pipelines/loading.py", line 281, in _poly2mask     elif isinstance(mask_ann['counts'], list): TypeError: 'NoneType' object is not subscriptable


feat(customAttribute): enable defaultBindingMode for customAttribute

Add a second parameter to customAttribute decorator, that allow to
specify the default binding mode on a custom attribute.

I need to think over this. It seems like a great idea though. Props also for the high quality PR with tests :)

Thanks :)
Actually, the idea came from a custom attribute I'm working on. I want to create a "focus" attribute, similar to the focus binding in Durandal. And without this new feature, developers would be forced to use the ".twoWay" command instead of the common ".bind" command.

Thanks again. This was a great quality PR! You should contribute more :)


SEEKING:   Volunteers to publish your list in a Global Searchable Directory

https://helpfulengineering.odoo.com/members
Is there any interest?

https://helpfulengineering.odoo.com/register - via a simple web page you can enter a NEED or HAVE entry.

Not able to adopt that. We are keeping it simple and focusing on collecting data about what hospitals will accept.

OK.  Thanks for considering.  Can I ask what isn't simple about this method of collecting data about what hospitals will accept?

We already have something in use that is meeting our needs.


Go update to 1.17.8 and cosign to 1.6.0

Summary

Go update to 1.17.8 and cosign to 1.6.0

Ticket Link
n/a
Release Note

Go update to 1.17.8 and cosign to 1.6.0

Codecov Report

Merging #705 (9617b6f) into main (1a884eb) will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #705      +/-   ##
==========================================
- Coverage   47.48%   47.44%   -0.04%
==========================================
  Files          65       65
  Lines        5600     5600
==========================================
- Hits         2659     2657       -2
- Misses       2651     2653       +2
  Partials      290      290

Impacted Files
Coverage Δ

pkg/types/alpine/v0.0.1/entry.go
61.24% <0.00%> (-0.78%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1a884eb...9617b6f. Read the comment docs.


Add verity x chicken nugget by chicken nugget

Song Name
verity x chicken nugget
Artist Name
chicken nugget
Source
Youtube
Youtube Link
eqphsrtLYEO
Direct File Link
No response
Song ID
677785
Start Offset [ms]
69000
Extra
Created from Auto Nong.
Created for level: 18834999

reject
verity is not the song and chicken nugget is not the artist anyway


Trigger from bottom of element

Would it be possible to make an element sticky when the bottom of the element reaches the top of the screen? Almost like a default option for topOffset with a value of the element's height?

This is coming

Actually, on re-reading this: This feature already exists in 3.0.0. Just set topOffset to the height of the element you are making sticky.


Fix : Added Documentation for Integers in  Java (#1251)

Description 📜
Documentation for Integers in Java.
Fixes #1251

Type of change 📝

[x] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] Java_Domain

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

@sumitaccess007 @AkMo3 @garvitraj
Made changes as instructed. Please review it.

@kashyap1905 looks great now.

@kashyap1905 looks great now.

@garvitraj Thank You Sir !! It's really motivating !!


Added test for non-homogenous component-wise boundary conditions

As always, this PR got away from me. It adds a bunch of boundary-condition related functionality to enable integration with the Tribol patch test.

Adds component-wise boundary condition enforcement to the base solver.
Adds a component-wise Dirichlet condition test for the nonlinear solid solver.
Improves the output for the solid solver using the deformed mesh.
Uses the isoparametric mesh representation in the solid solver.
Adds new cuboid MFEM meshes to the data directory.
Switches the WSL spack configs to use MPICH instead of OpenMPI.
Adds a boundary condition information data storage bundle type.
Adds output to the existing dynamic and quasi-static solid solver tests.

I think this is approaching done. I want to do some more verification tests, but let me know if you see anything glaringly wrong.

LGTM

LGTM

LGTM


[dart2wasm] Simplify handling null receivers in gets, tear-offs, invocations

In dart2wasm we don't use the Null class for null values, instead we use Wasm's null value (ref.null).
This means we need special cases in the code generator when generating gets, tear-offs, and invocations (dynamic or instance) to check for null Wasm values and based on the member name generate code for null.toString tear-off or invocation, or null.hashCode instance get etc. Currently these look like this:

Instance get: https://github.com/dart-lang/sdk/blob/50c5e8f47b4bc14e44a46c8a1af5dc0f182f8bc2/pkg/dart2wasm/lib/code_generator.dart#L1848-L1872
Instance tear-off: https://github.com/dart-lang/sdk/blob/50c5e8f47b4bc14e44a46c8a1af5dc0f182f8bc2/pkg/dart2wasm/lib/code_generator.dart#L1928-L1959
Instance invocation: https://github.com/dart-lang/sdk/blob/50c5e8f47b4bc14e44a46c8a1af5dc0f182f8bc2/pkg/dart2wasm/lib/code_generator.dart#L1455-L1476
There should also be a few lines in dynamic invocation code generator

Since we don't use an actual Dart object for null we can't completely avoid these special cases, but we can simplify them a little bit by having a class representing the null object (say, WasmNull), and when a receiver is null in a get, tear-off etc. we replace the receiver with the singleton instance of WasmNull. This class can be defined in Dart with the right toString, hashCode etc. implementations.
I tried this in a branch but it caused various crashes and it wasn't immediately obvious how can my changes break that much. This won't fix any tests but it may be a worthwhile simplification. We should probably revisit this at some point.
Related CLs:

https://dart-review.googlesource.com/c/sdk/+/268462 tries to use the core's Null class.
https://dart-review.googlesource.com/c/sdk/+/266627 uses a new class WasmNull instead of core's Null.

Without a null object, the special cases in instance invocations above need to also handle noSuchMethod.

The test tests/language/closure/tearoff_dynamic_test fails because of missing null.noSuchMethod handling.

The test tests/language/closure/tearoff_dynamic_test fails because of missing null.noSuchMethod handling.

This test seems to be passing now.


Use the globals of the function when evaluating the return type of serializers and computed_fields

Fixes https://github.com/pydantic/pydantic/issues/10919

Change Summary

Related issue number

Checklist

[ ] The pull request title is a good summary of the changes - it will be used in the changelog
[ ] Unit tests for the changes exist
[ ] Tests pass on CI
[ ] Documentation reflects the changes where applicable
[ ] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

Looking good, I'm guessing there are changes to get_function_return_type as well?

Looking good, I'm guessing there are changes to get_function_return_type as well?

Not passing any globals will let get_function_return_type -> get_function_type_hints fetch them using func.__module__


Disabled Reason: Agent doesn't support dynamic loading

I cant select which commands to include in agent. Actually, I cant to include even single command, its grayed out and says: "Disabled Reason: Agent doesn't support dynamic loading".

I installed agent by classic way:
sudo ./mythic-cli install github https://github.com/MythicAgents/thanatos
and its ONLINE. I restarted Mythic server also but still unable to generate payload.

So, if you look at that screenshot in the issue, all of the commands are listed on the side that says “commands included”, which means all of the commands are included in the agent at build time. The disabled piece means you can’t NOT include them because the agent doesn’t support dynamic loading

Oh, so they are already included. Sorry for my ignorance. Thanks so much for rapid response :)


Fix JOIN CSV(filename)

This PR fixes CSV functions inside JOIN clauses.
See #741 which was closed but with a workaround, not a complete fix.
Note: I applied the fix to alasqlparser.jison and then manually to alasqlparser.js instead of recompiling  alasqlparser.jison. If I recompile this file, the commented code at  https://github.com/agershun/alasql/blob/develop/src/alasqlparser.js#L477 gets re-enabled and then tests 394 and 400 fail.

Codecov Report

Merging #1092 into develop will increase coverage by 0.17%.
The diff coverage is 83.33%.

@@             Coverage Diff             @@
##           develop    #1092      +/-   ##
===========================================
+ Coverage    70.47%   70.64%   +0.17%
===========================================
  Files            1        1
  Lines        14181    14183       +2
  Branches      4789     4789
===========================================
+ Hits          9994    10020      +26
+ Misses        4187     4163      -24

Impacted Files
Coverage Δ

dist/alasql.fs.js
70.64% <83.33%> (+0.17%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update af51018...70927c8. Read the comment docs.

I previously committed the dist/alasql.d.ts file which had been updated by the gulp task. I reverted this file because the new version gives a TS compilation error: ./../node_modules/alasql/dist/alasql.d.ts:83:5 - error TS2666: Exports and export assignments are not permitted in module augmentations..
Looks like partners/alasql.d.ts needs a fix.

You are awesome. Thank yo so much.


Using wasmtime_wasi Dir struct can cause panic of TryFromIntError

Thanks for filing a bug report! Please fill out the TODOs below.
Note: if you want to report a security issue, please read our security policy!
Test Case
Here's the WASM code required to reproduce this bug:
fn main() {
    let dir = std::fs::read_dir("/").unwrap();
    println!("{:?}", dir.collect::<Vec<_>>());
}

cargo build --target wasm32-wasi --release

Compiled in release mode with debug = true:
test.wasm.tgz
Here's the Rust host code required, modified from the WASI example:
use wasmtime::*;
use wasmtime_wasi::{ambient_authority, sync::WasiCtxBuilder, Dir};

fn main() -> Result<()> {
    // Define the WASI functions globally on the `Config`.
    let engine = Engine::default();
    let mut linker = Linker::new(&engine);
    wasmtime_wasi::add_to_linker(&mut linker, |s| s)?;

    let wasm_fs = Dir::open_ambient_dir("/", ambient_authority())
        .expect("Filesystem root should be accessible");

    // Create a WASI context and put it in a Store; all instances in the store
    // share this context. `WasiCtxBuilder` provides a number of ways to
    // configure what the target program will have access to.
    let wasi = WasiCtxBuilder::new()
        .preopened_dir(wasm_fs, "/")
        .unwrap()
        .inherit_stdio()
        .inherit_args()?
        .build();
    let mut store = Store::new(&engine, wasi);

    // Instantiate our module with the imports we've created, and run it.
    let module = Module::from_file(&engine, "./test.wasm")?;
    linker.module(&mut store, "", &module)?;
    // --> Panic occurs here
    linker
        .get_default(&mut store, "")?
        .typed::<(), ()>(&store)?
        .call(&mut store, ())?;

    Ok(())
}

Steps to Reproduce

Use wasmtime_wasi::Dir to allow access to the root directory
Attempt to read the root directory from WASM

Expected Results
The program will print the files in the root directory: bin, dev, usr, etc.
Actual Results
Program panics:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: TryFromIntError(())', <...>/cap-primitives-2.0.0/src/rustix/fs/metadata_ext.rs:167:49

Versions and Environment
Wasmtime version or commit: v12.0.1
Operating system: macOS Ventura 13.5.1
Architecture: arm64 Apple Silicon
Extra Info
I'm not familiar with ambient authority.

it looks like this is a cap-primitives crate bug, can you please report it here: https://github.com/bytecodealliance/cap-std/issues

I'm not familiar with how wasmtime_wasi uses the Dir struct and I don't know anything about cap-primitives so I'm not really sure what to put in the bug report

It looks like u64::try_from(stat.st_dev).unwrap() fails. On Linux dev_t is a u64, but on macOS it is an i32: https://github.com/rust-lang/libc/blob/835661543db1ec42a6d9a809d69c3c5b5b978b81/src/unix/bsd/apple/mod.rs#L9 Presumably it is a negative number in this case. Could you try stat /* and see which dir gets which device number?

Not sure what to make of this:
$ stat /*
16777234 87498924 drwxrwxr-x 86 root admin 0 2752 "Sep 12 18:14:56 2023" "Sep 12 18:14:56 2023" "Sep 12 18:14:56 2023" "Sep  2 00:35:13 2023" 4096 0 0x100000 /Applications
16777234 87484854 drwxr-xr-x 72 root wheel 0 2304 "Sep  7 20:23:48 2023" "Sep  7 20:23:26 2023" "Sep  7 20:23:26 2023" "Sep  2 00:35:13 2023" 4096 0 0x100000 /Library
16777234<PHONE_NUMBER>311879701 drwxr-xr-x 10 root wheel 0 320 "Sep  2 00:35:13 2023" "Sep  2 00:35:13 2023" "Sep  2 00:35:13 2023" "Sep  2 00:35:13 2023" 4096 0 0x80000 /System
16777234 23836 drwxr-xr-x 6 root admin 0 192 "Sep  7 20:23:21 2023" "Sep  7 20:22:54 2023" "Sep  7 20:22:54 2023" "Aug 24 01:59:39 2022" 4096 0 0x100000 /Users
16777234 26293 drwxr-xr-x 3 root wheel 0 96 "Sep 11 19:52:22 2023" "Sep 11 19:52:22 2023" "Sep 11 19:52:22 2023" "Aug 24 01:59:39 2022" 4096 0 0x8000 /Volumes
16777234<PHONE_NUMBER>312435255 drwxr-xr-x 39 root wheel 0 1248 "Sep  2 00:35:13 2023" "Sep  2 00:35:13 2023" "Sep  2 00:35:13 2023" "Sep  2 00:35:13 2023" 4096 0 0x88000 /bin
16777234 26295 drwxr-xr-x 2 root wheel 0 64 "Sep 22 17:50:54 2022" "Aug 24 01:59:39 2022" "Sep 22 17:50:54 2022" "Aug 24 01:59:39 2022" 4096 0 0x8000 /cores
855137406 335 dr-xr-xr-x 4 root wheel 0 5023 "Sep 12 18:24:40 2023" "Sep  7 20:22:04 2023" "Sep  7 20:22:04 2023" "Dec 31 16:00:00 1969" 512 10 0x8000 /dev
16777234<PHONE_NUMBER>312435332 lrwxr-xr-x 1 root wheel 0 11 "Sep  2 00:35:13 2023" "Sep  2 00:35:13 2023" "Sep  2 00:35:13 2023" "Sep  2 00:35:13 2023" 4096 0 0x88000 /etc
16777234<PHONE_NUMBER>606781440 lrwxr-xr-x 1 root wheel 0 25 "Sep  7 20:23:38 2023" "Sep  7 20:23:38 2023" "Sep  7 20:23:38 2023" "Sep  7 20:23:38 2023" 4096 0 0x8000 /home
16777240 2 drwxr-xr-x 5 root nixbld 0 160 "Sep  8 14:52:37 2023" "Sep  8 14:52:31 2023" "Sep  8 14:52:31 2023" "Sep  8 14:52:12 2023" 4096 0 0 /nix
16777234 26292 drwxr-xr-x 4 root wheel 0 128 "Mar  9 17:51:16 2023" "Mar  3 22:04:09 2023" "Mar  3 22:04:09 2023" "Aug 24 01:59:39 2022" 4096 0 0x8000 /opt
16777234 87497982 drwxr-xr-x 6 root wheel 0 192 "Sep  8 08:24:55 2023" "Sep  7 20:23:34 2023" "Sep  7 20:23:34 2023" "Sep  2 00:35:13 2023" 4096 0 0x108000 /private
16777234<PHONE_NUMBER>606781443 lrwxr-xr-x 1 root wheel 0 15 "Sep  8 15:03:25 2023" "Sep  8 15:03:25 2023" "Sep  8 15:03:25 2023" "Sep  8 15:03:25 2023" 4096 0 0 /run
16777234<PHONE_NUMBER>312435335 drwxr-xr-x 64 root wheel 0 2048 "Sep  2 00:35:13 2023" "Sep  2 00:35:13 2023" "Sep  2 00:35:13 2023" "Sep  2 00:35:13 2023" 4096 0 0x88000 /sbin
16777234<PHONE_NUMBER>312435438 lrwxr-xr-x 1 root wheel 0 11 "Sep  2 00:35:13 2023" "Sep  2 00:35:13 2023" "Sep  2 00:35:13 2023" "Sep  2 00:35:13 2023" 4096 0 0x88000 /tmp
16777234<PHONE_NUMBER>312435439 drwxr-xr-x 11 root wheel 0 352 "Sep  2 00:35:13 2023" "Sep  2 00:35:13 2023" "Sep  2 00:35:13 2023" "Sep  2 00:35:13 2023" 4096 0 0x88000 /usr
16777234<PHONE_NUMBER>312470639 lrwxr-xr-x 1 root wheel 0 11 "Sep  2 00:35:13 2023" "Sep  2 00:35:13 2023" "Sep  2 00:35:13 2023" "Sep  2 00:35:13 2023" 4096 0 0x88000 /var

All these dev numbers are positive. Could you also try stat /? Maybe it is the root directory itself for which the dev number is negative?

Thanks for helping to track this down @bjorn3, I've posted a hypothetical fix at https://github.com/bytecodealliance/cap-std/pull/329, although I don't understand enough here to know if st_dev being negative is a bad thing or not. Once that's released I can help update it here in Wasmtime to get tested by @doinkythederp


Vidushi/progress bar

PR Title/Tagline
Issue Number(s): 67
What does this PR change and why?-- basic text and added a component called navigatorHeader which allows smooth transition of progress bar. Updated css of a few files and removed redundancy in code.
Checklist

[ ]  Database schema docs have been updated or are not necessary
[ ]  Code follows design and style guidelines
[ ]  Code is commented with doc blocks
[ ]  Tests have been written and executed or are not necessary
[ ]  Latest code has been rebased from base branch (usually develop)
[ ]  Commits follow guidelines (concise, squashed, etc)
[ ]  Github issues have been linked in relevant commits
[ ]  Relevant reviewers (Senior Dev/EM/Designers) have been assigned to this PR

Critical Changes

Database change / migration to run
Environment config change
Breaking API change

Related PRs

#PRNUMBER

How to Test

Please add or build upon a testing card to the Notion page and link it here

https://user-images.githubusercontent.com/92058859/216783953-1f933dca-6099-454d-ba99-4a543d78e7b8.mp4
https://user-images.githubusercontent.com/92058859/216783955-f88d9acc-1702-4998-8f02-6b41b524e122.mp4

Great job, and thank you for the refactoring!


Add fail option for regex extractor

Description
This change adds the option to automatically fail a sampler if a regular expression extraction can't find any matches.
Motivation and Context
This saves the need to add an assertion with a regex to be sure there are matches. This will either save doing the regex matching twice and/or improved the scripts by failing if the extraction fails rather fail later when there is no value
Based on this discussion. Thanks to @asfimport for initiating this and providing code
How Has This Been Tested?
I've tested this on HTTP Requests only with different types of matches (1: single extraction, 0: random and -1 to match multiple fields)
Screenshots (if appropriate):
Types of changes

New feature (non-breaking change which adds functionality)

Checklist:

[ ] My code follows the code style of this project.
[ ] I have updated the documentation accordingly.

Have you considered adding test case for the feature?

I've added unit tests and fixed some of your items. Seems to be working out really well

@vlsi Can you take a look? I've added test cases and made sure they work. Would be great to see this feature in next jmeter releases


2.0.2 again

Codecov Report

Merging #304 into release will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           release    #304      +/-   ##
==========================================
+ Coverage    86.09%   86.1%   +<.01%
==========================================
  Files          132     132
  Lines        15081   15081
==========================================
+ Hits         12984   12985       +1
+ Misses        2097    2096       -1

Impacted Files
Coverage Δ

pulsar/utils/http/parser.py
91.7% <0%> (+0.41%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0e47274...352ba19. Read the comment docs.


Add prolate spheroidal coordinates

I'm gearing up to add the Staeckel Fudge to Galax, so it would be useful to have a representation of prolate spheroidal coordinates. Transformations to this coordinate system need to specify a focal length parameter, Delta, so it's a bit different from other d3 representations. Thoughts on this approach?

How can I tell coordinax that Delta is not a coordinate component and is instead a parameter that helps specify the coordinate system?

That's a good question! We don't have a mechanism for that. This is complicated, essentially each value of $\Delta$ should result in a different representation. The non-viable but technically correct solution is to dynamically create a new class for each $Delta$. Not doing that, we could make $\Delta$ just be a property of the transformation, e.g. a mandatory kwarg to represent_as. However we still want to ensure math happens correctly, e.g. when 2 coords with different $\Delta$ are added it errors (or does some transformation then adds correctly). Therefore __add__ needs to know about $\Delta$, which can only happen if it's stored on the object. There are two options, both are a fair bit of work, and I'm not sure which is best.

$\Delta$ is a field on the representation class. We would then need to change the fundamental assumption on representations, which is that all fields are coordinate axes. coordinax uses field_items() and related functions liberally to perform generalized operations on representations. We would need to define new functions like axis_field_items to replace the other functions everywhere.
We define a new class (name TBD) RepDeltaWrapper that accepts the representation and the delta. The representation is still "pure" in that all fields are coordinates. RepDeltaWrapper would need to be made to work with the existing representation machinery. This might end up involving all the changes described for (1) + registering all the primitives.

So writing this out, (2) might be technically / mathematically better, but (1) seems best to do now.
I guess the first thing to do then is to define an Axis field descriptor, like how I've done in astropy.cosmology.Parameter. We can then filter the dataclass' fields by whether they are annotated as Axis types in the class definition (they would still be Quantity on the instance). The functions axis_field_<X> could actually just be field_<X> with a flag type (like in unxt) as the 2nd arg ... field_items(prolate_spheroid, Axes).

Steps 1-3 are now done!

@nstarman I think this is ready for a look! Tests are failing with a gnarly recursion error in test_jax_ops.py that I haven't figured out yet.

OK it turns out the recursion error was because one of the tests was calling the fallback represent_as(CartesianPos3D, ProlateSpheroidalPos), which shouldn't be possible because this transformation has no defined Delta, and (unrelated) was triggering a recursion. Fixing in the next batch of commits

Hm, not sure about the failing test. Adding the converter to VectorAttribute causes filter_jit to fail here:
@eqx.filter_jit
def func(q):
    return q.represent_as(cx.ProlateSpheroidalPos, Delta=Quantity(1.0, "kpc"))

q = cx.CartesianPos3D.from_([1, 2, 3], "kpc")
func(q)

Can you try removing the parametrization in the converter? Maybe just Quantity.from_. I think the dimensions will be checked against the field annotation when it's being set.

But also Happy Thanksgiving 🦃!  For after the holidays :)

Hm, removing the "length" parametrization didn't fix it! No rush to respond (but I'll be working on and off this weekend)

Then remove and flag in an Issue for followup! Let's get this in. Looks great otherwise.

I realized one other issue with this PR! Velocity transforms aren't working at the moment - I can look into it tomorrow:
pos = cx.CartesianPos3D.from_([1., 2., 3.], "kpc")
vel = cx.CartesianVel3D.from_([1., 2., 3.], "km/s")
vel.represent_as(cx.ProlateSpheroidalVel, pos, Delta=Quantity(0.1, "kpc"))

---------------------------------------------------------------------------
EquinoxTracetimeError                     Traceback (most recent call last)
Cell In[3], line 3
      1 pos = cx.CartesianPos3D.from_([1., 2., 3.], "kpc")
      2 vel = cx.CartesianVel3D.from_([1., 2., 3.], "km/s")
----> 3 vel.represent_as(cx.ProlateSpheroidalVel, pos, Delta=Quantity(0.1, "kpc"))

    [... skipping hidden 2 frame]

File ~/projects/coordinax/.venv/lib/python3.10/site-packages/jaxtyping/_decorator.py:449, in jaxtyped.<locals>.wrapped_fn_impl(args, kwargs, bound, memos)
    446             raise TypeCheckError(msg) from e
    448 # Actually call the function.
--> 449 out = fn(*args, **kwargs)
    451 if full_signature.return_annotation is not inspect.Signature.empty:
    452     # Now type-check the return value. We need to include the
    453     # parameters in the type-checking here in case there are any
   (...)
    464     # checking of the parameters. Unfortunately there doesn't seem
    465     # to be a way around that, so c'est la vie.
    466     kwargs[output_name] = out

File ~/projects/coordinax/src/coordinax/_src/vectors/base/base.py:203, in AbstractVector.represent_as(self, target, *args, **kwargs)
    153 def represent_as(self, target: type, *args: Any, **kwargs: Any) -> "AbstractVector":
    154     """Represent the vector as another type.
    155
    156     This just forwards to `coordinax.represent_as`.
   (...)
    201
    202     """
--> 203     return represent_as(self, target, *args, **kwargs)

    [... skipping hidden 2 frame]

File ~/projects/coordinax/.venv/lib/python3.10/site-packages/jaxtyping/_decorator.py:449, in jaxtyped.<locals>.wrapped_fn_impl(args, kwargs, bound, memos)
    446             raise TypeCheckError(msg) from e
    448 # Actually call the function.
--> 449 out = fn(*args, **kwargs)
    451 if full_signature.return_annotation is not inspect.Signature.empty:
    452     # Now type-check the return value. We need to include the
    453     # parameters in the type-checking here in case there are any
   (...)
    464     # checking of the parameters. Unfortunately there doesn't seem
    465     # to be a way around that, so c'est la vie.
    466     kwargs[output_name] = out

File ~/projects/coordinax/src/coordinax/_src/vectors/transform/differentials.py:130, in represent_as(current, target, position, **kwargs)
    115 current_pos = replace(
    116     current_pos,
    117     **{
   (...)
    121     },
    122 )
    124 # Takes the Jacobian through the representation transformation function.  This
    125 # returns a representation of the target type, where the value of each field the
    126 # corresponding row of the Jacobian. The value of the field is a Quantity with
    127 # the correct numerator unit (of the Jacobian row). The value is a Vector of the
    128 # original type, with fields that are the columns of that row, but with only the
    129 # denomicator's units.
--> 130 jac_nested_vecs = jac_rep_as(current_pos, target.integral_cls)
    132 # This changes the Jacobian to be a dictionary of each row, with the value
    133 # being that row's column as a dictionary, now with the correct units for
    134 # each element:  {row_i: {col_j: Quantity(value, row.unit / column.unit)}}
    135 jac_rows = {
    136     f"d_{k}": {
    137         kk: Quantity(vv.value, unit=v.unit / vv.unit)
   (...)
    140     for k, v in field_items(jac_nested_vecs)
    141 }

    [... skipping hidden 27 frame]

File ~/projects/coordinax/src/coordinax/_src/vectors/d3/transform.py:801, in represent_as(current, target, **kwargs)
    765 @dispatch
    766 def represent_as(
    767     current: AbstractPos3D,
   (...)
    770     **kwargs: Any,
    771 ) -> ProlateSpheroidalPos:
    772     """AbstractPos3D -> ProlateSpheroidalPos.
    773
    774     Examples
   (...)
    799
    800     """
--> 801     Delta = eqx.error_if(
    802         kwargs.get("Delta"),
    803         "Delta" not in kwargs,
    804         "Delta must be provided for ProlateSpheroidalPos.",
    805     )
    806     cyl = represent_as(current, CylindricalPos)
    807     return represent_as(cyl, target, Delta=Delta)

    [... skipping hidden 2 frame]

File ~/projects/coordinax/.venv/lib/python3.10/site-packages/equinox/_errors.py:313, in branched_error_if_impl(x, pred, index, msgs, on_error)
    311 assert type(index) is int
    312 if on_error == "raise":
--> 313     raise EquinoxTracetimeError(msgs[index])
    314 elif on_error == "breakpoint":
    315     print(msgs[index])

EquinoxTracetimeError: Delta must be provided for ProlateSpheroidalPos.

Looks like Delta needs to be passed through the represent_as calls.

Looks like Delta needs to be passed through the represent_as calls.

Yes exactly - but the way it is vmap'd, I think the kwargs get batched alone axis=0 which would obviously fail for a scalar Delta.

If it's enforced scalar, then vmap axis for Delta should be None!

I pushed a workaround that uses partial and moves the definition of the jacobian function inside. But the tests did not catch this -- are there any automated tests of the velocity transforms?

I suspect just unit tests ATM.

🎉


Debug Console output not printing output at correct interval

VSCode Version: 1.0.1-alpha
OS Version: Windows 10

Steps to Reproduce:
I was testing in Powershell but I was able to reproduce for Javascript.

Add the below code and debug with the Powershell extension
Observe the speed of the output numbers.

With Start-Sleep set at 100ms output prints 6 lines per refresh instead of printing one line every 100ms. Set at 200ms, 3 lines are printed per refresh, etc.
function Write-Item($itemCount) {
    $i = 1

    while ($i -le $itemCount) {
        $str = "Output $i"
        Write-Output $str

        # In the gutter on the left, right click and select "Add Conditional Breakpoint"
        # on the next line. Use the condition: $i -eq 25
        $i = $i + 1

        # Slow down execution a bit so user can test the "Pause debugger" feature.
        Start-Sleep -Milliseconds 100
    }
}

# Do-Work will be underlined in green if you haven't disable script analysis.
# Hover over the function name below to see the PSScriptAnalyzer warning that "Do-Work"
# doesn't use an approved verb.
function Do-Work($workCount) {
    Write-Output "Doing work..."
    Write-Item $workcount
    Write-Host "Done!"
}

Do-Work 50

@isidorn I don't know if this is us or powershell. Starting with you.

This is because we have a throttling of output otherwise the tree could be refreshed every ms and this could cause vscode to crash.
We use this to stop a potentially spammy extension from flooding the repl.
Closing as designed


HEALPix Utils function

some links:
https://healpy.readthedocs.io/en/latest/install.html
https://healpix.sourceforge.io/

It is not clear to me that we actually need to implement this. If the L2 code was modularized to the extent that any binning routine could be plugged in, it would allow whoever develops the Mapper tool to just plug in a binning function that would bin to HEALPix rather than Lat/Lon grid. It my be moot since Ultra is now requesting HEALPix number be included in their pset product.


log version on startup

on startup, log the application version and maybe the used jdk

implemented in development branch


[Bug]: Use swc-plugin-jsx-control-statements  Plugin error

System Info
System:
    OS: macOS 10.15.7
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 416.02 MB / 16.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 16.15.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 6.14.18 - /usr/local/bin/npm
    pnpm: 8.6.11 - /usr/local/bin/pnpm
  Browsers:
    Chrome: 122.0.6261.129
    Safari: 15.6.1

Details
trying to use https://github.com/intpp/swc-plugin-jsx-control-statements in my rsbuild project.
running rsbuild build:
Message:  Cannot start a runtime from within a runtime. This happens because a function (like `block_on`) attempted to block the current thread while the thread is being used to drive asynchronous tasks.
Location: /Users/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wasmer-wasix-0.9.0/src/runtime/task_manager/mod.rs:323

Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
Run with RUST_BACKTRACE=full to include source snippets.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 1: _napi_register_module_v1
    at <unknown source file>
 2: _napi_register_module_v1
    at <unknown source file>
 3: _napi_register_module_v1
    at <unknown source file>
 4: _napi_register_module_v1
    at <unknown source file>
 5: _napi_register_module_v1
    at <unknown source file>
 6: _wasmer_vm_imported_memory32_atomic_notify
    at <unknown source file>
 7: _napi_register_module_v1
    at <unknown source file>
 8: _napi_register_module_v1
    at <unknown source file>
 9: _napi_register_module_v1
    at <unknown source file>
10: _napi_register_module_v1
    at <unknown source file>
11: _napi_register_module_v1
    at <unknown source file>
zsh: abort      fap dev

Reproduce link
No response
Reproduce Steps

yarn create rsbuild

update rsbuild.config.ts to:

import { defineConfig } from '@rsbuild/core';
import { pluginReact } from '@rsbuild/plugin-react';

export default defineConfig({
  plugins: [pluginReact()],
  tools: {
    swc: {
      jsc: {
        experimental: {
          plugins: [
            ['swc-plugin-jsx-control-statements', {}],
          ],
        },
      },
    },
  },
});

3.run rsbuild build and it will show the error

May I ask when this will be repaired? Can you give me an idea of when

May I ask when this will be repaired? Can you give me an idea of when

This might be related to not matched version. For your reference: https://github.com/web-infra-dev/rspack/issues/5921

Followup, the swc_core version of this plugin is 0.79. This would cause potential loading error and segmentation fault. https://github.com/intpp/swc-plugin-jsx-control-statements/blob/main/Cargo.toml#L21. Only plugins in https://github.com/swc-project/plugins are recommended.

Followup, the swc_core version of this plugin is 0.79, which is not compatible with current rspack. Check out this for more info. Only plugins in https://github.com/swc-project/plugins are recommended. Otherwise, you need to fork the original repo and update the swc_core on your own to use it with the latest version of rspack.

I can use swc-core version 0.90.*？Other versions will report errors

Followup, the swc_core version of this plugin is 0.79, which is not compatible with current rspack. Check out this for more info. Only plugins in https://github.com/swc-project/plugins are recommended. Otherwise, you need to fork the original repo and update the swc_core on your own to use it with the latest version of rspack.

I can use swc-core version 0.90.*？Other versions will report errors

Compiling swc_ecma_transforms_testing v0.139.6
error[E0308]: mismatched types
--> /Users/zian/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/swc_ecma_transforms_testing-0.139.6/src/lib.rs:976:67
|
976 |             println!("SourceMap: {}", visualizer_url(&actual_src, sourcemap));
|                                       --------------              ^^^^^^^^^ expected sourcemap::SourceMap, found sourcemap::types::SourceMap
|                                       |
|                                       arguments to this function are incorrect
|
= note: sourcemap::types::SourceMap and sourcemap::SourceMap have similar names, but are actually distinct types
note: sourcemap::types::SourceMap is defined in crate sourcemap
--> /Users/zian/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/sourcemap-8.0.0/src/types.rs:481:1
|
481 | pub struct SourceMap {
| ^^^^^^^^^^^^^^^^^^^^
note: sourcemap::SourceMap is defined in crate sourcemap
--> /Users/zian/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/sourcemap-6.4.1/src/types.rs:459:1
|
459 | pub struct SourceMap {
| ^^^^^^^^^^^^^^^^^^^^
= note: perhaps two different versions of crate sourcemap are being used?
note: function defined here
--> /Users/zian/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/swc_ecma_transforms_testing-0.139.6/src/lib.rs:999:4
|
999 | fn visualizer_url(code: &str, map: &sourcemap::SourceMap) -> String {
|    ^^^^^^^^^^^^^^             --------------------------
For more information about this error, try rustc --explain E0308.
error: could not compile swc_ecma_transforms_testing (lib) due to 1 previous error

Followup, the swc_core version of this plugin is 0.79, which is not compatible with current rspack. Check out this for more info. Only plugins in https://github.com/swc-project/plugins are recommended. Otherwise, you need to fork the original repo and update the swc_core on your own to use it with the latest version of rspack.

I can use swc-core version 0.90.*？Other versions will report errors

Compiling swc_ecma_transforms_testing v0.139.6 error[E0308]: mismatched types --> /Users/zian/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/swc_ecma_transforms_testing-0.139.6/src/lib.rs:976:67 | 976 | println!("SourceMap: {}", visualizer_url(&actual_src, sourcemap)); | -------------- ^^^^^^^^^ expected `sourcemap::SourceMap`, found `sourcemap::types::SourceMap` | | | arguments to this function are incorrect | = note: `sourcemap::types::SourceMap` and `sourcemap::SourceMap` have similar names, but are actually distinct types note: `sourcemap::types::SourceMap` is defined in crate `sourcemap` --> /Users/zian/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/sourcemap-8.0.0/src/types.rs:481:1 | 481 | pub struct SourceMap { | ^^^^^^^^^^^^^^^^^^^^ note: `sourcemap::SourceMap` is defined in crate `sourcemap` --> /Users/zian/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/sourcemap-6.4.1/src/types.rs:459:1 | 459 | pub struct SourceMap { | ^^^^^^^^^^^^^^^^^^^^ = note: perhaps two different versions of crate `sourcemap` are being used? note: function defined here --> /Users/zian/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/swc_ecma_transforms_testing-0.139.6/src/lib.rs:999:4 | 999 | fn visualizer_url(code: &str, map: &sourcemap::SourceMap) -> String { | ^^^^^^^^^^^^^^ --------------------------
>
> For more information about this error, try `rustc --explain E0308`. error: could not compile `swc_ecma_transforms_testing` (lib) due to 1 previous error

Followup, the swc_core version of this plugin is 0.79, which is not compatible with current rspack. Check out this for more info. Only plugins in https://github.com/swc-project/plugins are recommended. Otherwise, you need to fork the original repo and update the swc_core on your own to use it with the latest version of rspack.

I can use swc-core version 0.90.*？Other versions will report errors

Compiling swc_ecma_transforms_testing v0.139.6 error[E0308]: mismatched types --> /Users/zian/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/swc_ecma_transforms_testing-0.139.6/src/lib.rs:976:67 | 976 | println!("SourceMap: {}", visualizer_url(&actual_src, sourcemap)); | -------------- ^^^^^^^^^ expected sourcemap::SourceMap, found sourcemap::types::SourceMap | | | arguments to this function are incorrect | = note: sourcemap::types::SourceMap and sourcemap::SourceMap have similar names, but are actually distinct types note: sourcemap::types::SourceMap is defined in crate sourcemap --> /Users/zian/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/sourcemap-8.0.0/src/types.rs:481:1 | 481 | pub struct SourceMap { | ^^^^^^^^^^^^^^^^^^^^ note: sourcemap::SourceMap is defined in crate sourcemap --> /Users/zian/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/sourcemap-6.4.1/src/types.rs:459:1 | 459 | pub struct SourceMap { | ^^^^^^^^^^^^^^^^^^^^ = note: perhaps two different versions of crate sourcemap are being used? note: function defined here --> /Users/zian/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/swc_ecma_transforms_testing-0.139.6/src/lib.rs:999:4 | 999 | fn visualizer_url(code: &str, map: &sourcemap::SourceMap) -> String { | ^^^^^^^^^^^^^^ --------------------------
For more information about this error, try rustc --explain E0308. error: could not compile swc_ecma_transforms_testing (lib) due to 1 previous error

Remove swc related lock files and reinstall

Still the same

Followup, the swc_core version of this plugin is 0.79, which is not compatible with current rspack. Check out this for more info. Only plugins in https://github.com/swc-project/plugins are recommended. Otherwise, you need to fork the original repo and update the swc_core on your own to use it with the latest version of rspack.

I can use swc-core version 0.90.*？Other versions will report errors

Compiling swc_ecma_transforms_testing v0.139.6 error[E0308]: mismatched types --> /Users/zian/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/swc_ecma_transforms_testing-0.139.6/src/lib.rs:976:67 | 976 | println!("SourceMap: {}", visualizer_url(&actual_src, sourcemap)); | -------------- ^^^^^^^^^ expected sourcemap::SourceMap, found sourcemap::types::SourceMap | | | arguments to this function are incorrect | = note: sourcemap::types::SourceMap and sourcemap::SourceMap have similar names, but are actually distinct types note: sourcemap::types::SourceMap is defined in crate sourcemap --> /Users/zian/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/sourcemap-8.0.0/src/types.rs:481:1 | 481 | pub struct SourceMap { | ^^^^^^^^^^^^^^^^^^^^ note: sourcemap::SourceMap is defined in crate sourcemap --> /Users/zian/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/sourcemap-6.4.1/src/types.rs:459:1 | 459 | pub struct SourceMap { | ^^^^^^^^^^^^^^^^^^^^ = note: perhaps two different versions of crate sourcemap are being used? note: function defined here --> /Users/zian/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/swc_ecma_transforms_testing-0.139.6/src/lib.rs:999:4 | 999 | fn visualizer_url(code: &str, map: &sourcemap::SourceMap) -> String { | ^^^^^^^^^^^^^^ --------------------------
For more information about this error, try rustc --explain E0308. error: could not compile swc_ecma_transforms_testing (lib) due to 1 previous error

Remove swc related lock files and reinstall

Still the same


Issues/issue 92

PR for https://github.com/SwiftWeekly/swiftweekly.github.io/issues/325

@RomanVolkov I can keep reviewing this and continue to make suggestions regarding wording if you'd like. I just don't want you to think I'm an 💩 😅 Appreciate your hard work on this 👍

Thanks for checking, @SD10! 🎉
Sent with GitHawk

Thanks @SD10 ! 👍 💯

@jessesquires don't forget to move it to _posts :)

@BasThomas done! 🥇


Trust Wallet uses token logos from this source, alongside a number of other projects.
The repository contains token info from several blockchains, info on dApps, staking validators, etc.
For every token a logo and optional additional information is available (such data is not available on-chain).
Such a large collection can be maintained only through a community effort, so feel free to add your token.

How to add token
Please note that brand new tokens are not accepted,
the projects have to be sound, with information available, and non-minimal circulation
(for limit details see https://community.trustwallet.com/t/how-to-submit-a-token-logo/3863).
Assets App
The Assets web app can be used for most new token additions (Github account is needed).
Quick starter
Details of the repository structure and contribution guidelines are listed on the
Developers site.
Here is a quick starter summary for the most common use case.
Adding an ERC20 token checklist:

[☑] Make sure your smartcontract has more than 2,500 address holders, otherwise you will be rejected
[☑] Fork the Github repository
[☑] Create folder with name of token smartcontact address in checksum format blockchains/ethereum/assets/<token_smartcontract_address>/.
[☑] Tell your designer that token image must be in PNG format, avoid transparent background, recommended size 256x256px, max. 512x512px, with max file size of 100kB, for further details read image rules.
[☑] Upload your logo with file named logo.png to previously created folder with smartcontract address, and if you done all correctly your path should look like this. blockchains/ethereum/assets/0x1234567461d3f8Db7496581774Bd869C83D51c93/logo.png
[☑] Create info.json file with info about the token/project
[☑] Create a pull request to the main repo
[☑] Pay the processing fee

Documentation
For details, see the Developers site:

Contribution guidelines

Repository details

Scripts
There are several scripts available for maintainers:

✅npm run check -- Execute validation checks; also used in continuous integration.
✅npm run check-sanity -- Strict subset of checks
✅npm run fix -- Perform automatic fixes where possible
✅npm run fix-sanity -- Stricter subset
✅npm run updateAuto -- Run automatic updates from external sources, executed regularly (GitHub action)
✅ npm run update -- Run manual updates from external sources, for manual use.
✅npm test -- Run script unit tests
✅npm lint -- Run Lint static code check

On Checks
This repo contais a set of scripts for verification of all the information.  Implemented as Typescript scripts, available through npm run check, and executed in CI build; checks the whole repo.
There are similar check logic implemeted:

in assets-management app; for checking changed token files in PRs, or when creating a PR.  Implemented as a Typescript library, checks diffs, can be run from browser environment.
in merge-fee-bot, which runs as a GitHub app shows result in PR comment.  Also uses library, but executes in a non-browser environment.

Trading pair maintenance
Info on supported trading pairs are stored in tokenlist.json files.
Trading pairs can be updated --
from Uniswap/Ethereum and PancakeSwap/Smartchain -- using update script (and checking in changes).
Minimal limit values for trading pair inclusion are set in the config.ts file.
There are also options for force-include and force-exclude in the config.
Disclaimer
Trust Wallet team allows anyone to submit new assets to this repository. However, this does not mean that we are in direct partnership with all of the projects.
Trust Wallet team will reject projects that are deemed as scam or fraudulent after careful review.
Trust Wallet team reserves the right to change the terms of asset submissions at any time due to changing market conditions, risk of fraud, or any other factors we deem relevant.

Terra Station mobile
::::{grid} auto
::: {grid-item}
:color: primary
:outline:
Desktop

:::
::: {grid-item}
:color: primary
:outline:
Chrome extension

:::
::: {grid-item}
:color: primary
Mobile

:::
::::
Complete this tutorial to get started with the Terra Station mobile app.
Download the Terra Station app

Tap the download link for your operating system. Your device’s app store will open.

Terra Station for iOS
Terra Station for Android

Install the Terra Station app on your phone.

Create a new wallet

Launch the Terra Station app and select New wallet
:class: sd-p-3
:width: 300 px

Enter a name for your wallet and a secure password. Confirm your password and tap Next
:class: sd-p-3
:width: 300 px

Using a pen and paper, write down your 24-word seed phrase exactly as it appears. Number each word to make verifying easier.
:::{admonition} Protect your seed phrase
:class: danger
Anyone with your seed phrase can access your money, and there is no recourse for someone stealing your seed phrase. To protect your seed phrase, consider the following tips:

Never save or store your seed phrase as a digital file on any device.
Always write down your seed phrase with a pen and paper.
Store the paper with your seed phrase on it somewhere safe.
Never give your seed phrase to anyone, not even support staff.
:::

Verify your writing to make sure every word is spelled correctly and in the right order. If you numbered your phrase, it can be helpful to verify it backward.
:class: sd-p-3
:width: 300 px

Tap I have written down my seed.

Confirm your seed phrase by typing or selecting the correct words in each prompt.
:class: sd-p-3
:width: 300 px

Tap Confirm and finish.

Congratulations, you have just created a wallet!
Receive tokens from an exchange

Purchase your tokens using any exchange that supports Terra. To view a list of current exchanges, visit the Integrations page

Withdraw any token supported by the Terra network from your exchange. Every exchange is different. Please visit your exchange's web page for guides on how to withdraw tokens. Use the following steps as a generic guide.

To receive tokens to your wallet, use your wallet address. Your wallet address will appear at the top of the Terra station Desktop app near your wallet name. Your wallet address will look like this: terra<random-numbers-and-letters>

Double-check your wallet address is correct before sending.

Send the tokens from the exchange to your Terra Station wallet address.

:::{admonition} Waiting times for transfers
:class: caution
When you transfer tokens from an exchange to Terra, some time will pass before the tokens appear in your wallet. Don't panic. This waiting period is normal and varies depending on the exchange. If a transfer does not appear immediately, check back after some time.
:::

Now you have tokens on Terra!
Swap coins

Open the Terra Station app extension and connect to your wallet. Tap Swap.
:class: sd-p-3
:width: 300 px

In the first dropdown, select a coin and enter the value you want to swap.

In the second dropdown, select a coin to receive.
:class: sd-p-3
:width: 300 px

Tap Next.

Select the coin you want to pay fees in.
:class: sd-p-3
:width: 300 px

Confirm your transaction amounts and tap Confirm.
:class: sd-p-3
:width: 300 px

Congratulations, you've just swapped coins!
Send tokens

Open the Terra Station app extension and connect to your wallet.
:class: sd-p-3
:width: 300 px

Tap on the token in your available balance that you want to send.

Enter the address of the wallet you want to send tokens to.

Enter the amount you want to send. You can also add a memo to specify what the transaction is for.
:class: sd-p-3
:width: 300 px

Tap Next.

Verify the transaction amounts and specify which token you want to pay fees in. Remember to always leave enough tokens in your account for other transactions.
:::{admonition} Keep coins for fees
:class: caution
Always keep some coins to pay fees with.  Without money for fees, you can't make any transactions.
:::
:class: sd-p-3
:width: 300 px

Enter your password and tap Confirm. Wait for the transaction to process. This generally takes a few seconds.

Stake Luna

Open the Terra Station app extension and connect to your wallet. Make sure you have Luna in your wallet to stake.

Tap Staking.

Browse the list and tap on the validator you would like to stake to.

Tap Delegate

Enter the amount of Luna you want to delegate. Tap Next.

Confirm the amount and select the coin you want to pay fees in.
:::{admonition} Keep coins for fees
:class: caution
Always keep some coins to pay fees with. Never stake your entire wallet amount. Without money for fees, you can't make any transactions.
:::

Tap Confirm and wait for your transaction to process.

Your Luna is now staked to a validator.
Withdraw staking rewards
Rewards start accruing the moment you stake Luna. Monitor your rewards in the staking section of Terra Station. Once you have sufficient rewards, follow these steps to withdraw them:

Open the Terra Station app. Connect to a wallet and tap Staking.

To claim all rewards, tap Withdraw all rewards at the top of the staking page.

Review the amounts and specify which coin you want to pay fees in.

Enter your password and tap Confirm.

Congratulations, you've just withdrawn your staking rewards!
Connect to a dApp

Open the Terra Station app and connect to your wallet.

In your browser, navigate to the dApp of your choice. This tutorial will use the Anchor protocol WebApp. Most dApps use a similar process, though others may vary.
:class: sd-p-3
:width: 300 px

Tap the wallet icon at the top of the page.

Wallet connect will open your Terra Station app.
:class: sd-p-3
:width: 300 px

When prompted, tap Allow.
:class: sd-p-3
:width: 300 px

You can now make transactions on different dApps in the Terra ecosystem from your mobile device.
Next steps
To use Terra Station on your computer, visit the Terra Station desktop tutorial. To learn how to use other Station features, visit the Station guides.


Significant rendering errors

Significant rendering errors throughout file.  It renders correctly in Adobe Acrobat.  (See Screen shots).  Using Windows 8.1 x64. Chrome 39.0.2171.95
File:  https://pdf.yt/d/_9N23mLX9_XzEhEQ
pdf.js screenshot

Adobe Acrobat

Closing as fixed by PR #5308.


Drop-and-recreate migration scripts do not work correctly with async/await

Environment
Knex 0.14.6
PostgreSQL 10.1
Bug
If migration script relies on async/await to wait for a column to be dropped before being created again, "column already exists" error is thrown. Same code works fine if .then block is used instead.
Code example:
exports.up = async (knex) => {
    await knex.schema.withSchema(`${SCHEMA}`).table('users', function (table) {
        table.dropColumn('officeId');
    });

    await knex.schema.withSchema(`${SCHEMA}`).table('users', function (table) {
        table.string('officeId', 255);
    });
};

@elhigu Yup, that works just fine.

That is really weird and doesn't make sense at all... if someone likes to write test case and figure out what is going on please do.

Closing as cannot reproduce anymore. Added tests that are not failing in master.

Happened to me too with this kind of migration:
export async function up(db: DbConnection): Promise<any> {
	await db.schema.alterTable('users', function(table: Knex.CreateTableBuilder) {
		table.dropColumn('max_item_size');
		table.dropColumn('can_share_folder');
		table.dropColumn('can_share_note');
	});

	await db.schema.alterTable('users', function(table: Knex.CreateTableBuilder) {
		table.integer('max_item_size').defaultTo(null).nullable();
		table.specificType('can_share_folder', 'smallint').defaultTo(null).nullable();
		table.specificType('can_share_note', 'smallint').defaultTo(null).nullable();
		table.bigInteger('max_total_item_size').defaultTo(null).nullable();
	});
}

My fix was to split it into two migrations, although it would be nice if it could be done without hack.

Additionally, this doesn't work either:
await db.schema.alterTable('users', function(table: Knex.CreateTableBuilder) {
	table.dropColumn('max_item_size');
	table.dropColumn('can_share_folder');
	table.dropColumn('can_share_note');

	table.integer('max_item_size').defaultTo(null).nullable();
	table.specificType('can_share_folder', 'smallint').defaultTo(null).nullable();
	table.specificType('can_share_note', 'smallint').defaultTo(null).nullable();
	table.bigInteger('max_total_item_size').defaultTo(null).nullable();
});

@laurent22 your problem is not the same that in original post, but something else: https://runkit.com/embed/aj7p07d29vz0
It clearly looks like a bug though, so please open a separate bug report for that.


Serialization Derive Macro does not support Tuples

As title, ref #104. Example:
#[derive(Debug, CanonicalSerialize)]
struct TestCase<E: PairingEngine> {
    a: (E::G1Affine, E::G1Affine), // this makes the macro fail
    b: E::G1Affine, // this works
    c: Vec<E::G2Affine>, // this works
}

It'd be nice if it would just serialize a.0 followed by a.1
Sidenote: In order to use the macro, I had to explicitly import algebra-core to my package. It'd be nice if the macro were usable via importing just algebra as well.
i.e. go from:
zexe_algebra = { package = "algebra", git = "https://github.com/scipr-lab/zexe", version = "0.1.0" }
zexe_algebra_core_derive = { package = "algebra-core-derive", git = "https://github.com/scipr-lab/zexe", version = "0.1.0" }
algebra_core = { package = "algebra-core", git = "https://github.com/scipr-lab/zexe", version = "0.1.0" }

to
zexe_algebra = { package = "algebra", git = "https://github.com/scipr-lab/zexe", version = "0.1.0", features = ["derive"] }
cc @paberr

I'll take a look into it. :)

I opened a PR with the functionality you were looking for.

So, the problem with not having algebra-core as a dependency is:

The derive macro generates code that refers to types like ::algebra_core::SerializationError.
Since algebra also re-exports these types, I tried choosing between algebra_core and algebra using a feature flag at compile time.
However, since feature flags are active within the whole workspace/project, the following will happen:

Let's suppose you write your own crate that only depends on algebra and gm17.
You want to use the derive macro using algebra only. Then, the feature will be set for the whole workspace. The derive macros will thus use ::algebra::<...> as a path.
However, gm17/groth16 only depend on algebra-core. This will cause gm17 to not compile anymore.

To avoid this mess, I guess the best way is to still require algebra-core as a dependency.
You don't need to explicitly depend on the algebra-core-derive anymore, but can use a feature flag in algebra-core.

Closing, thank you so much @paberr !


[scss/bulma] Vite is set up to automatically import variables.scss

Hello, I have encountered an error when attempting to use the bulma adder. Looking into it a bit, it looks like the problem stems from the scss loader. It looks to be a validation snafu rather than an error per se.
It looks like the error arises in L57 of https://github.com/svelte-add/scss/blame/main/__detect.js#L57
However, it looks like - as of 5 days ago - variables.scss is added via w/ @use rather than @import: (https://github.com/svelte-add/scss/blame/main/__run.js#L8).
My updated svelte.config.js appears to be reasonable (pasted below). Bulma appears to be working as expected when I add a small component to the app.
So perhaps a change on the validating string would be sufficient? (https://github.com/svelte-add/scss/blame/main/__detect.js#L57)
				if (!text.includes("@import")) return false; // existing
				if (!text.includes("@use")) return false;     // fix?

Updated svelte.config.js
import adapter from '@sveltejs/adapter-auto';
import preprocess from 'svelte-preprocess';

/** @type {import('@sveltejs/kit').Config} */
const config = {
	// Consult https://github.com/sveltejs/svelte-preprocess
	// for more information about preprocessors
	preprocess: [
		preprocess({
			scss: {
				prependData: '@use "src/variables.scss" as *;'
			}
		})
	],

	kit: {
		adapter: adapter(),

		// hydrate the <div id="svelte"> element in src/app.html
		target: '#svelte',

		vite: {
			css: {
				preprocessorOptions: {
					scss: {
						additionalData: '@use "src/variables.scss" as *;'
					}
				}
			}
		}
	}
};

export default config;

Full command output
Project setup:
❯ npm init svelte@next my-app
# Select typescript, eslint, prettier, demo app
❯ cd my-app
❯ npm i

Actual command:
❯ npx svelte-add@latest bulma
➕ Svelte Add (Version 2<IP_ADDRESS>)
The project directory you're giving to this command cannot be determined to be guaranteed fresh — maybe it is, maybe it isn't. If any issues arise after running this command, please try again, making sure you've run it on a freshly initialized SvelteKit or Vite–Svelte app template.

SCSS
  ✅ `sass` is installed
  ✅ `svelte-preprocess` is set up for SCSS in `svelte.config.js`
  ✅ `src/app.scss` exists
  ✅ `src/variables.scss` exists
  ❌ Vite is set up to automatically import variables.scss
  ✅ The main file (`src/routes/__layout.svelte` for SvelteKit, `src/main.js` or `src/main.ts` for Vite) imports `src/app.scss`

  ❌ was supposed to be set up for you but it appears not to have been?! (see above)
This is definitely not supposed to happen, so please create or find an existing issue at https://github.com/svelte-add/svelte-add/issues with the full command output.

Bulma
 ✅ successfully set up!
Create or find an existing issue at https://github.com/svelte-add/svelte-add/issues if this is wrong.

Run pnpm install to install new dependencies, and then reload your IDE before starting your app.

This is an excellent issue report — thank you so much!
You are correct that this error message is just an oversight from that change and there is no other known issue than this false error.


feat: Refactor mech driver

After this is tested and merged, I'm aware we can do a better cleanup in workflows as we won't need undersync_device workflow anymore.
This PR needs another change in Nautobot prep_switch_interface job as from now on we can use connected_interface_uuid instead of mac_address, so please leave merging to me.

overall LGTM. Added few more suggestions for missing docstrings and type hints.
One more (optional) idea - consider updating #update_nautobot to return an instance of UUID instead of plain string, this way we add another layer of data validation which would be better than a docstring promise of returning string that happens to contain uuid.

that's a good idea, implemented


Release Version 0.2.0

Version 0.2.0 introduces the following:

Added support for multivariate GMMs.
Introduces the UnivariateGMM and MultivariateGMM layers for adding MDN functionality to existing architectures.
Updates the native interface to support both univariate and multivariate models.

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/81950
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.0 -m "<description of version>" 828b9490e41f1c30b23e887d3dc8358fb6b0f67c
git push origin v0.2.0


Correct PHP version requirements

WHY are these changes introduced?
The current PHP version constraint (^8.0 || ^8.1 || ^8.2) doesn't make sense. It looks like the package is intended to support PHP versions 8.0.x and 8.1.x and 8.2.x with unknown status given to 8.3.x and 8.4.x and so on. However, the constraints used currently is equivalent to ^8.0 and supports all versions of 8.x.x.
https://jubianchi.github.io/semver-check/#/^8.0/8.1.45
WHAT is this pull request doing?
This pull request refines the supported versions to include only those that seem to be intended. When new versions are released, these can be added to the list.
Type of change

Patch: Bug (non-breaking change which fixes an issue)

I'm marking this as a 'patch' because we're only dropping support for future versions of PHP which don't currently exist. Also, given that the most recent pull request merged dropped support for PHP 7.x, and this hasn't been tagged / released yet, this is a great time to fix this bug too.
Checklist

[x] I have added a changelog entry, prefixed by the type of change noted above
[x] I have added/updated tests for this change
[x] I have updated the documentation for public APIs from the library (if applicable)

This is (somewhat) a duplicate of https://github.com/Shopify/shopify-api-php/pull/249.


Using wrong email address from GitHub account

Issue Type: Bug / Question
When i login with my github account, is doesnt use my primary email address which is configured in github.
Its always using an old one which doesnt even exist in my account anymore.
At this point i am not sure if this is an issue with live-share or VSC in general.
Extension version: 1.0.2427
VS Code version: Code 1.46.1 (cd9ea6488829f560dc949a8b2fb789f3cdc05f5d, 2020-06-17T21:13:08.304Z)
OS version: Linux x64 5.6.19-200.fc31.x86_64

Closed as this is a duplicate of #2327


No handler method error despite handler being defined.

In my project, I have 2 packets being sent between the server and client simply to share some information about the state of the game. Both the packets are being sent, and on the server side the packet is being handled (the same error does not occur, and I have Log statements during the handler that are being sent). However, on the client side, all I'm getting is this error message:
No client-side handler method found for message ID 2!
It's worth mentioning that I have the server logic and the client logic defined in the same unity project, switching between them by using the "Server Build" functionality in Unity's build settings. I have both the Server-Side and Client-Side Packet Handlers in one script however in early versions they were both in the client and server scripts respectively and it was still broken. Here is the code;
using System.Collections;
using UnityEngine;
using RiptideNetworking;

public class PacketHandlers : MonoBehaviour
{
    [MessageHandler((ushort)NetworkCommons.PacketType.SendingClientInfo)] //PacketType.SendingClientInfo is 1
    private static void RecieveClientInfo(ushort fromClientId, Message message)
    {
       //Logic
    }

    [MessageHandler((ushort)NetworkCommons.PacketType.RecievingServerInfo)] //PacketType.RecievingServerInfo is 2
    private static void ReceivingServerInfo(ushort fromClientId, Message message)
    {
        //Logic
    }
}

I am aware that this error has been brought up before but no actual solution was came to in that thread, so hopefully we can come up with a public solution to this error to kill it once and for all.

The error message is correct—you don't have a client-side handler method for message ID 2. Your ReceivingServerInfo method is a server-side message handler. Server-side handlers take two parameters (a ushort and a Message) while client-side handlers only take one parameter (a Message).

This is what i get for not reading the docs thoroughly enough lol, thanks


[BEAM-5341] create IT test for TfIdf example

Please add a meaningful description for your change here

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.