Where is instalation file?

I have searched standard Firefox install and https://hg.mozilla.org/mozilla-central. I cant find "Firefox central repository", to install and test your very useful code. Any hint?

Thank you for your interest. The problem is that Mozilla decided to stop supporting the AddOn-Builder platform and thus there is currently no way to run this addon. I'm working on a new version, but so far it is not ready yet (but hopefully soon...)

Any status updates?

I have a working prototype which however still needs some clean-up. Hopefully, there will be a first release in a few weeks.

A very early version is now available. Just follow the install instructions on the main page. It should work with the current Zotero and Firefox versions. If not, let me know. Any bug reports or feature requests are welcome!


Fix application of window in FFT

This fixes the input of the windowing function, which has to be based on the position within the whole FFT input buffer. The way it was, multiple windows could be potentially applied to different segments of the audio being accumulated.
Notes:

Given the change in the windowing expression, the change in the way p_src_frames and temporal_fft_pos are incremented came in as natural, which also may make the code faster.
The old post-windowing code which was applying a constant window and partially commented out is removed.

Thanks!

Cherry-picked for 3.2.4.


404

Welcome! Click here for Information and References! #4 points to The Adventurers (D&D Group Run by @mbround18 ), but wiki.boop.ninja returns 404.

Fixed 404 :)


Update load-data-to-from-excel-with-ssis.md

Under "Export long text values" the second option to create the excel file using a sql statement and columns of type LONGTEXT does NOT appear to work.  Only the first option works - having at least one row with data in each column > 255 double byte characters (i.e. 512 normal ones) already before writing anymore rows works.  So one can only make this work with an initial, manually created, dummy row.
Delete the second option - it may work for other data destinations but not for Excel.

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

@chugugrace Could you please take a look at this recommended change to the article? Look at the files changed tab. If this is correct, could you sign off? Thank you!

@chugugrace Because this is removing information that @simes1 has verified to not work, I am going to sign off on the change. If this is incorrect, please let me know and we can work on adding it back with more clarification. Thank you @simes1, and apologies for the delay! #sign-off

@rothja: I'm sorry - only the author of this article, @chugugrace, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


python3Packages.pyarlo: init at 0.2.4

Motivation for this change
Python Arlo is a library written in Python 2.7/3x that exposes the Netgear Arlo cameras as Python objects.
https://github.com/tchellomello/python-arlo
This is a Home Assistant dependency.
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 108236 1

3 packages built:

python37Packages.pyarlo
python38Packages.pyarlo
python39Packages.pyarlo

Result of nixpkgs-review pr 108236 1

3 packages built:

python37Packages.pyarlo
python38Packages.pyarlo
python39Packages.pyarlo

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108236 run on x86_64-darwin 1

3 packages built:

python37Packages.pyarlo
python38Packages.pyarlo
python39Packages.pyarlo

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108236 run on x86_64-darwin 1

3 packages built:

python37Packages.pyarlo
python38Packages.pyarlo
python39Packages.pyarlo

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108236 run on x86_64-linux 1

3 packages built:

python37Packages.pyarlo
python38Packages.pyarlo
python39Packages.pyarlo

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108236 run on x86_64-linux 1

3 packages built:

python37Packages.pyarlo
python38Packages.pyarlo
python39Packages.pyarlo

Result of nixpkgs-review pr 108236 run on x86_64-linux 1

1 package marked as broken and skipped:

python39Packages.pyarlo

2 packages built:

python37Packages.pyarlo
python38Packages.pyarlo

Fails on Python 3.9 because python39Packages.fixtures is marked as broken.

Result of nixpkgs-review pr 108236 run on x86_64-linux 1

1 package marked as broken and skipped:

python39Packages.pyarlo

2 packages built:

python37Packages.pyarlo
python38Packages.pyarlo

Fails on Python 3.9 because python39Packages.fixtures is marked as broken.

@mweinelt maybe you can cherry-pick to https://github.com/NixOS/nixpkgs/pull/108602 to re-generate component-packages.nix to avoid merge conflicts?

@mweinelt maybe you can cherry-pick to https://github.com/NixOS/nixpkgs/pull/108602 to re-generate component-packages.nix to avoid merge conflicts?

Yep, done. Thanks for the poke.

Yep, done. Thanks for the poke.


add project-level role/permissions management to ui and cli

Exactly what the title says.
We use plain Kubernetes RBAC on the back end, but that's an inadequate user experience and it provides end-users who don't also have cluster credentials with no way at all of managing permissions.

Is there any plan to support multi-tenancy within the same Kargo instance?
For example, if both team A and team B share the same Kargo instance (managed for them by a central platform team), I believe that team A can write a Promotion (manually or automatically) that syncs team B's ArgoCD Application resources.
This seems like an intrinsic limitation of using K8s RBAC for a single shared ServiceAccount with permissions to patch ArgoCD Application resources.

Is there any plan to support multi-tenancy within the same Kargo instance?

Yes. And we're about halfway there...

This seems like an intrinsic limitation of using K8s RBAC...

Our units of tenancy are "projects," which are just specially labeled namespaces. In general, this plays very nicely with k8s RBAC, which already makes it very easy to limit permissions on a per-namespace basis.

... for a single shared ServiceAccount with permissions to patch ArgoCD Application resources.

Right. That's where we're at now and it's a problem, but that's not the long-term plan for Applications -- or any other resource type for that matter.
For Kargo resources, we plan to move off of the single, shared ServiceAccount as soon as possible and move toward some TBD way to define mappings from Kargo users (who may not even have cluster credentials) to ServiceAccount(s) with the correct level of permissions. OpenShift works similarly to this, so there's plenty of precedent for the approach and prior art to emulate. (This issue is about managing those mappings.)
Even with that in place, managing permissions to patch various Argo CD Application resources remains a separate problem precisely because Argo CD did not use a namespace-based tenancy model -- a mistake we're learning from and keen not to repeat. To elaborate, all Argo CD Applications in a given cluster typically reside in the same namespace (typically argocd). This fact makes it impossible (in most clusters) to manage Application permissions using pure k8s RBAC.
To work around this, we'll continue using a single, shared ServiceAccount only for patching Applications, but Kargo itself (already) refuses to patch an Application on behalf of a Promotion unless the Application is explicitly annotated in a way that indicates consent from someone who already had sufficient authority to add that annotation in the first place -- i.e. for lack of a better term, the Application's owner.

For example, if both team A and team B share the same Kargo instance (managed for them by a central platform team), I believe that team A can write a Promotion (manually or automatically) that syncs team B's ArgoCD Application resources.

If we do things right, this won't be possible.

Awesome, that's great to hear. I believe ArgoCD does support Applications in multiple namespaces now, maybe it wouldn't be unreasonable to require Kargo users to employ that pattern if it simplifies the authorization problems?

I believe ArgoCD does support Applications in multiple namespaces now

That's correct, but it doesn't seem to be in broad use (yet?)

maybe it wouldn't be unreasonable to require Kargo users to employ that pattern if it simplifies the authorization problems

It's worth considering, but I would expect many who are accustomed to doing it the old way would be resistant to that requirement.


Question:How to Fixed container height?

If I keep adding , it will  beyond my Fixed container height。

What? I don't understand the question.
On Oct 23, 2017 8:42 PM, "90°"<EMAIL_ADDRESS>wrote:

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/STRML/react-grid-layout/issues/651, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ABJFPytrxH--wS3moa2VYkF9K_qkZ4iXks5svUB7gaJpZM4QDuaJ
.

there is not option to set height, instead you can try maxRows property.

+1

+1


Define at compile time in pico_asm!

Is there any way of doing the following:
fn some_function<const N : u8> -> ! {
    let led_program = pio_proc::pio_asm!(
        ".define T1 42",
        ".wrap_target",
            "mov pins , 0 [T0]",
            "mov pins , 1 [T1]",
        ".wrap",
        define(T0 = N) // Add T0 defined to the value of compile constant N
    );
    ...
}

Essentially where you can add a define to a pio_asm at compile time? If not I would like to propose this addition.

It's not currently possible, but it sounds like a nice enhancement.
However, I'm not sure if it's possible to actually evaluate N inside the macro at compile time.

I checked and you cannot evaluate constants at macro time, so this is DOA :(
I also noticed that since you can't get the type out from the public defines, you can't declare a pio_asm! as a constant variable. It might be worth adding a way to forward declare the ExpandedDefines type with a new option(public_defines_type) or something.
I can see a world where if you can at least declare it constant at compile time one could modify the program at compile with a custom define they needed.


Raise RepositoryNotFoundError if repository is not found when adding a repo to a collection

At the moment, when adding a repo to a collection, I get the following error. I think a RepositoryNotFoundError might be a better fit, but no strong opinion as I understand it would not encapsulate papers
HfHubHTTPError: 404 Client Error: Not Found for url: https://huggingface.co/api/collections/osanseviero/historical-spaces-of-the-week-6532465b9824bcc3f44cea3c/items (Request ID: Root=1-65329fd7-3e569eb24a070d6c0c820247;5d852b78-c691-4dd7-bdf8-0e854a12f245)

Repo or paper not found

Maybe what would be nice is to still raise a basic HTTP 404 (no RepoNotFound wrapper) but update the error message from the server to include the URL/ID that has not been found. At least it would be clear to the user what is missing. What do you think?
(so a moon-landing-only fix)

Yes, that would be clearer!

As discussed, the better error message has being shipped server-side (see https://github.com/huggingface/moon-landing/pull/7843 -internal repo-). Should be proded soon.
Error message is now:
HfHubHTTPError: 404 Client Error: Not Found for url: https://huggingface.co/api/collections/osanseviero/historical-spaces-of-the-week-6532465b9824bcc3f44cea3c/items (Request ID: Root=1-65329fd7-3e569eb24a070d6c0c820247;5d852b78-c691-4dd7-bdf8-0e854a12f245)

Cannot add item to collection: space 'username/my-space' not found


SPI-USB Adapter with OPC-N2 example does not work with any python version

Related to #69, running the example script for the device using python3 results in
Traceback (most recent call last):
  File "reviewTest.py", line 1, in <module>
    from usbiss.spi import SPI
ImportError: No module named 'usbiss'

Attempting to use python results in
ERROR:opc:Could not parse the fimrware version from ????????????????????????????????????????????????????????????
Traceback (most recent call last):
  File "/home/pi/py-opc/opc/__init__.py", line 77, in __init__
    self.firmware['version'] = int(re.findall("\d{3}", infostring)[-1])
IndexError: list index out of range
ERROR:opc:Could not parse the fimrware version from ?
Traceback (most recent call last):
  File "/home/pi/py-opc/opc/__init__.py", line 77, in __init__
    self.firmware['version'] = int(re.findall("\d{3}", infostring)[-1])
IndexError: list index out of range
WARNING:opc:Data transfer was incomplete

in addition to the device's fan continually running until unplugged.

The first error showed you haven't installed pyusbiss.
Did you execute pip install pyuabiss?
On Sat, 23 Jun 2018, 00:16 Tony Shu<EMAIL_ADDRESS>wrote:

Related to #69 https://github.com/dhhagan/py-opc/issues/69, running the
example script for the device using python3 results in
Traceback (most recent call last):
File "reviewTest.py", line 1, in
from usbiss.spi import SPI
ImportError: No module named 'usbiss'
Attempting to use python results in
ERROR:opc:Could not parse the fimrware version from ????????????????????????????????????????????????????????????
Traceback (most recent call last):
File "/home/pi/py-opc/opc/init.py", line 77, in init
self.firmware['version'] = int(re.findall("\d{3}", infostring)[-1])
IndexError: list index out of range
ERROR:opc:Could not parse the fimrware version from ?
Traceback (most recent call last):
File "/home/pi/py-opc/opc/init.py", line 77, in init
self.firmware['version'] = int(re.findall("\d{3}", infostring)[-1])
IndexError: list index out of range
WARNING:opc:Data transfer was incomplete
in addition to the device's fan continually running until unplugged.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dhhagan/py-opc/issues/70, or mute the thread
https://github.com/notifications/unsubscribe-auth/AIB3VVIpINi6fPQKWpr8he_zooeBCZH6ks5t_XregaJpZM4U0iJK
.

Ah. If you wanted python 3 to work then execute pip3 install pyusbiss

Your second issue after executing python2 appears to be a bad communication.
Can you connect your sensor to the adaptor and wait for a minute before executing the test-device.py script? We have numerous Github issues regarding the connection problems and one of the solutions was to wait between physically connecting the sensor and executing any commands.

Oh, your traceback does show that you successfully connected to your sensor.
The py-opc library attempts to communicate with your sensor a number of times before it succeeded. Your traceback shows two failed attempts and third attempt is successful.
Your real problem is the last line WARNING:opc:Data transfer was incomplete. This was due to test-device.py executing the histogram command at

@tshu Can you let me know which version of py-opc is installed (opc.__version__)? I thought I fixed several of these in the newest release after speaking with Alphasense on some of the issues. Thanks!

Great, so both python2 and python3 work with test-device.py after using pip3 and waiting after USB connection. I will occasionally fail to connect 2-3 times, but it will always run the script in the end. If there can be a note about the wait time in the readme, that would be great.
However, referring back to the original problem in this issue of running the example code from the readme, both python2 and python3 will attempt to connect 0-3 times before terminating with `WARNING:opc:Data transfer was incomplete'. Fan remains on. I can still run test-device.py to regain control of the device and have the fans turn off at the end of the script.
@dhhagan currently running 1.6.0

What is output of the following script (modified from readme)
import spidev
import opc
from time import sleep

spi = spidev.SpiDev()
spi.open(0, 0)
spi.mode = 1
spi.max_speed_hz = 500000

alphasense = opc.OPCN2(spi)

# Turn the opc ON
alphasense.on()

# Read the information string
print (alphasense.read_info_string())

# Turn the opc OFF
alphasense.off()

pi@raspberrypi:~/py-opc $ python3 reviewTest2.py
Traceback (most recent call last):
  File "reviewTest2.py", line 14, in <module>
    alphasense.on()
NameError: name 'alphasense' is not defined
pi@raspberrypi:~/py-opc $ python reviewTest2.py
Traceback (most recent call last):
  File "reviewTest2.py", line 14, in <module>
    alphasense.on()
NameError: name 'alphasense' is not defined

@DancingQuanta @tshu It would appear the script/code above is incorrect - it should be alpha.on() since that is what the OPCN2 class instance was initiated as. I have just merged the previous readme changes into v1.6.1. Care to check?

Opps, I made a name mistake.
import usbiss
from usbiss.spi import SPI
import opc
from time import sleep

spi = SPI("/dev/ttyACM0")

spi.mode = 1
spi.max_speed_hz = 500000

alpha = opc.OPCN2(spi, debug=True)

# Turn the opc ON
alpha.on()

# Read the information string
print (alpha.read_info_string())

# Turn the opc OFF
alpha.off()

pi@raspberrypi:~/py-opc $ python reviewTest2.py
ERROR:opc:Could not parse the fimrware version from ?
Traceback (most recent call last):
  File "/home/pi/py-opc/opc/__init__.py", line 77, in __init__
    self.firmware['version'] = int(re.findall("\d{3}", infostring)[-1])
IndexError: list index out of range

pi@raspberrypi:~/py-opc $ python3 reviewTest2.py
ERROR:opc:Could not parse the fimrware version from ?
Traceback (most recent call last):
  File "/home/pi/py-opc/opc/__init__.py", line 77, in __init__
    self.firmware['version'] = int(re.findall("\d{3}", infostring)[-1])
IndexError: list index out of range

Getting some garbage outputs.

Could you replace print(alpha.read_info_string()) with print(repr(alpha.read_info_string())) and try again  please?

pi@raspberrypi:~/py-opc $ python reviewTest2.py
ERROR:opc:Could not parse the fimrware version from ?
Traceback (most recent call last):
  File "/home/pi/py-opc/opc/__init__.py", line 77, in __init__
    self.firmware['version'] = int(re.findall("\d{3}", infostring)[-1])
IndexError: list index out of range
'\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01'
pi@raspberrypi:~/py-opc $ python3 reviewTest2.py
ERROR:opc:Could not parse the fimrware version from ?
Traceback (most recent call last):
  File "/home/pi/py-opc/opc/__init__.py", line 77, in __init__
    self.firmware['version'] = int(re.findall("\d{3}", infostring)[-1])
IndexError: list index out of range
'\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01\x01'

Your output shows that it is getting blank data from your sensor.
Can you add sleep(1) before each line containing alpha and run the script?

That did the trick.
pi@raspberrypi:~/py-opc $ python3 reviewTest2.py
'OPC-N2 FirmwareVer=OPC-018.2..............................BD'
pi@raspberrypi:~/py-opc $ python reviewTest2.py
'OPC-N2 FirmwareVer=OPC-018.2..............................BD'

The only necessary sleep is between turnon and the read. The following code works:
import usbiss
from usbiss.spi import SPI
import opc
from time import sleep

spi = SPI("/dev/ttyACM0")

spi.mode = 1
spi.max_speed_hz = 500000

alpha = opc.OPCN2(spi, debug=True)

# Turn the opc ON
alpha.on()

sleep(1)
# Read the information string
print(repr(alpha.read_info_string()))

# Turn the opc OFF
alpha.off()

We probably need to improve alpha.on(). A sleep could be added to end of alpha.on(). Or have a timer in the library that track which command have been sent. So that the script itself can work without being slowed down until it execute another alpha command which then will invoke sleep with time period equal to alphasense's response then execute. Like a debt.

@DancingQuanta Yea, I tried to avoid doing anything other than wrapping the SPI commands, but it seems that it is causing so much trouble for most users (myself included). I went ahead and added sleeps in the necessary places and will push a bit later on today as I have some free time.

Can I suggest a decorator to wrap some methods to add sleep to beginning of a method if the method was called in the specified time period since last method called. Like a cool down. We know that a method such as on takes a while to make the device ready.
Every time a method such as on is called the time of this call is recorded. Next time a method (any method) is called, the new time is compared to old time and the difference is used to delay execution of called method.
This way the time spent waiting for sleep in each method to work would be less if we could use the time in between calls as part of waiting.

@DancingQuanta I'll go ahead and merge a few PR's and push right now - maybe then take a look and see what you think is best? A decorator would be fine as you suggest - I think I just added a few sleeps. Give me 30 min or so.

@tshu I've added some notes to the readme. Should be okay now?


Upgrade Alert Increase Prominence

Wanted to make the upgrade a bit more prominent for those running nodes/pools/etc. Revised some copy to ensure normal users know they're expected to be safe.

Revisions include link to roadmap

cool thankyou


RHS projection

Vector.Project was not readyf or RHS systems.
Please validate my math!!
Playground to test with - #XCPP9Y#20954

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/14790/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14790/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14790/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/14790/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/14790/merge
https://gui.babylonjs.com/?snapshot=refs/pull/14790/merge
https://nme.babylonjs.com/?snapshot=refs/pull/14790/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/14790/merge#BCU1XR#0

WebGL2 visualization test reporter:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14790/merge/testResults/webgl2playwright/index.html

Visualization tests for WebGPU (Experimental)
Important - these might fail sporadically. This is an optional test.
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14790/merge/testResults/webgpuplaywright/index.html

Closing for now, have to test something.

Visualization tests for webgl1 have failed. If some tests failed because the snapshots do not match, the report can be found at
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14790/merge/testResults/webgl1/index.html
If tests were successful afterwards, this report might not be available anymore.


EasyGecNG becomes mysteriously unresponsive unless the USB connection is restarted

Requested by Barb. Original message:

I wanted to emphasize that a fairly urgent issue, that we've reproduced now on two computers, is that we are running into a problem where we need to press Stop and Start in between each runner in using the EasyGecNG program. (If we don't, then it just does not respond when students download.) It would be great if we could reproduce this problem in an environment that the development team has access to - and see if we can address it. It's a bit frustrating because it is intermittent - it generally happens after the first few downloads have worked without a problem. I ran into this at MLK school, and when testing Computer #3 (new) with Kit #2 (41-50) for VLUS PE. It happens with EasyGecNG but not with EasyGec (original).

[ ] Get more details about how this occurs
[ ] Recreate in dev environment

Works for ~20 downloads or so
Fails; becomes unresponsive
After restarting usb connection (via the gui button) it would work only once, then requirea restart again

The failure is supposedly caused by this file:
MC_2023_05_10.egc.txt

Reproduced!

We narrowed down the issue to a faulty ordering function in a results class, that crashes a thread when we ask Collections to sort that class. We still need to determine why this only happens sometimes. I suspect it is because this problem file contains duplicate results, ordered in such a way as to trigger Collections's detection of the bad ordering function.

[ ] Recreate with a minimal course file
[ ] Create unit test


Adds opt-in support for Pusher 6.x

Any estimated time of merging this? I really want to use pusher 6 on my new project. Thanks for all of your work on this package

Any estimated time of merging this? I really want to use pusher 6 on my new project. Thanks for all of your work on this package

Until Laravel 8.x supports Pusher 6.x. In theory, it shouldn't have a problem. You can test by using Laravel and trying to composer require pusher/pusher-http-php: 6.1.

It has been approved on Laravel side.

Thank you. I'll take care of this in the next couple of days as I'm trying to finish up the last missing pieces for a 2.0 stable release

Can we have an update on this one please?

Any update on this? It's been another 26 days 😛

I’ll personally wait until the first 6.x patch, if there is none.
Italo Baeza C.

El 09-08-2021, a la(s) 08:28, Tijn @.***> escribió:

Any update on this? It's been another 26 days 😛
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I think it's safe now to support Pusher 7.0.


added function for larc_history

Add some test for this functionality, please. For example test local repository for several sample transactions of different types


Numbers are unsupported

Hello! We are trying to build an application that uses your library. Unfortunately, there seems to be something wrong... We encounter a problem when we try to validate our test OAS which utilizes numbers, specifically in the server object definition. It seems that your validator does not like numbers in the OAS.
Here is our error:
AssertionError: expected 3000 to have type string
      expected 'number' to be 'string'

      at Assertion.fail (node_modules/should/cjs/should.js:258:17)
      at Assertion.value [as type] (node_modules/should/cjs/should.js:335:19)
      at checkServers (node_modules/swagger2openapi/validate.js:119:43)
      at Object.validateSync (node_modules/swagger2openapi/validate.js:349:3)

And here is our server object definition, note the default port number:
{
  "servers": [
    {
      "url": "http://localhost:{port}/{basePath}",
      "description": "The location of the local test server.",
      "variables": {
        "port": {
          "default": 3000
        },
        "basePath": {
          "default": "api"
        }
      }
    }
  ]
}

We thought that we were following proper OAS specification as the official specification page has a very similar example which can be seen here:
{
  "servers": [
    {
      "url": "https://{username}.gigantic-server.com:{port}/{basePath}",
      "description": "The production API server",
      "variables": {
        "username": {
          "default": "demo",
          "description": "this value is assigned by the service provider, in this example `gigantic-server.com`"
        },
        "port": {
          "enum": [
            8443,
            443
          ],
          "default": 8443
        },
        "basePath": {
          "default": "v2"
        }
      }
    }
  ]
}

Hi @Alan-Cha this isn't a generic problem with numbers in the validator.
Both the server variable  default and enum properties can only contain strings (the enum being an array of strings).
See here in the specification.
In this case, it is the example which is wrong.

I've raised a PR to correct the example in the specification: https://github.com/OAI/OpenAPI-Specification/pull/1251

https://github.com/OAI/OpenAPI-Specification/pull/1251 has been merged.


Update config.js

I'll grab this.

Update src/foundry/client/pixi/layers/grid/layer.d.mts for initializeMesh to use the correct style options


LogicalTypeID Assertion failed on parameterized queries

I encountered this assertion failure when using KuzuPreparedStatement from Java API with parameterized queries where a parameter appears multiple times.
what():  Assertion failed in file "/home/runner/actions-runner/_work/kuzu/kuzu/src/common/types/value/value.cpp" on line 18: dataType->getLogicalTypeID() == LogicalTypeID::ANY

For reference, this is one of the queries that I used:
MATCH
  (src:Account {id: $id1})-[edge1:AccountTransferAccount]->(dst:Account {id: $id2}),
	(dst)-[edge3:AccountTransferAccount]->(other:Account)-[edge2:AccountTransferAccount]->(src)
WHERE	$startTime < edge1.timestamp AND edge1.timestamp < $endTime
	AND $startTime < edge2.timestamp AND edge2.timestamp < $endTime
	AND $startTime < edge3.timestamp AND edge3.timestamp < $endTime
WITH
  other.id AS otherId,
  count(edge2) AS numEdge2, sum(edge2.amount) AS sumEdge2Amount, max(edge2.amount) AS maxEdge2Amount,
  count(edge3) AS numEdge3, sum(edge3.amount) AS sumEdge3Amount, max(edge3.amount) AS maxEdge3Amount
RETURN otherId, numEdge2, sumEdge2Amount, maxEdge2Amount, numEdge3, sumEdge3Amount, maxEdge3Amount
ORDER BY sumEdge2Amount DESC, sumEdge3Amount DESC, otherId;

It has $startTime and $endTime appear more than once, and when I changed to keep only 1 occurence of them in the query, it ran normally.
I also tried with Python API and got the same problem with the queries.
It's also noted that I only got this issue with the API packages built on the kuzu-selfhosted-benchmark-runner on uw2. The queries ran normally when I tried with API packages compiled from the source code on my laptop and on ac5.

This should be resolved in #3374. But I didn't run the driver again. Maybe @manh9203 can double check this.


Typo

Preparations Before You Run section in the README file has a typo. remote_machine_username should be remote_machine_password

ops, right. Thank you for noticing! :)