EG4 LL 12v "TypeError" on nightly build

Describe the problem
I installed the nightly build on my GX when I saw the EG4-LL bms added.  Figured it could use some testing. It connects and outputs information via the troubleshoot commands but with an error and does not show on my GX device.  EG4 was not an option on the "bms type" drop down.
2024-07-02 13:51:32.740628500 TypeError: 'str' object is not callable
Driver version
v1.4x-dev
Venus OS device type
Cerbo GX
Venus OS version
v3.40~33
BMS type
Life/Tian Power
Cell count
4
Battery count
1
Connection type
Serial USB adapter to RS485
Config file
GNU nano 4.9.3                    /data/etc/dbus-serialbattery/config.ini                    Modified
[DEFAULT]

; If you want to add custom values/settings, then check the values/settings you                         >
; and insert them below to persist future driver updates.

; Example (remove the semicolon ";" to uncomment and activate the value/setting                         >
; MAX_BATTERY_CHARGE_CURRENT = 50.0
; MAX_BATTERY_DISCHARGE_CURRENT = 60.0

Relevant log output
root@einstein:~# tail -F -n 100 /data/log/dbus-serialbattery.ttyUSB2/current | tai64nlocal
2024-06-30 12:11:07.517837500 INFO:SerialBattery:Cell Total Voltage: 13.554v | Current: 4.55A
2024-06-30 12:11:07.518542500 INFO:SerialBattery:Capacity Left: 400 of 400.0 AH
2024-06-30 12:11:07.519218500 INFO:SerialBattery:SoC: 100% - Charging
2024-06-30 12:11:07.519797500 INFO:SerialBattery:===== DVCC State =====
2024-06-30 12:11:07.520722500 INFO:SerialBattery:DVCC Charger Mode: None
2024-06-30 12:11:07.521152500 INFO:SerialBattery:DVCC Charge Voltage: Nonev
2024-06-30 12:11:07.521795500 INFO:SerialBattery:Charge Current: None | Discharge Current: None
2024-06-30 12:11:07.522680500 INFO:SerialBattery:Charge Limit: None | Discharge Limit: None
2024-06-30 12:11:07.523071500 INFO:SerialBattery:===== Warning/Alarms =====
2024-06-30 12:11:07.523667500 INFO:SerialBattery: No Warnings - 0000
2024-06-30 12:11:07.524281500 INFO:SerialBattery: No Protection Events - 0000
2024-06-30 12:11:07.524880500 INFO:SerialBattery: No Errors - 0000
2024-06-30 12:11:07.525425500 INFO:SerialBattery:===== Temp =====
2024-06-30 12:11:07.525998500 INFO:SerialBattery:Temp 1: 27c | Temp 2: 24c | Temp Mos: 24c
2024-06-30 12:11:07.526760500 INFO:SerialBattery:Avg: 24c | Temp Max: 24c
2024-06-30 12:11:07.527363500 INFO:SerialBattery:Heater Status: False
2024-06-30 12:11:07.527902500 INFO:SerialBattery:===== Battery Stats =====
2024-06-30 12:11:07.528532500 INFO:SerialBattery:SoH: 100% | Cycle Count: 2
2024-06-30 12:11:07.529162500 INFO:SerialBattery:Max Charging Current: 220 A
2024-06-30 12:11:07.529708500 INFO:SerialBattery:===== Cell Stats =====
2024-06-30 12:11:07.530377500 INFO:SerialBattery:Cell 0 Voltage: 3.39
2024-06-30 12:11:07.531017500 INFO:SerialBattery:Cell 1 Voltage: 3.383
2024-06-30 12:11:07.531720500 INFO:SerialBattery:Cell 2 Voltage: 3.391
2024-06-30 12:11:07.532439500 INFO:SerialBattery:Cell 3 Voltage: 3.39
2024-06-30 12:11:07.533168500 INFO:SerialBattery:Cell Max/Min/Diff: (3.391/3.383/0.008)v
2024-06-30 12:11:07.796573500 INFO:SerialBattery:== Modbus packet good ==
2024-06-30 12:11:07.797407500 INFO:SerialBattery:Connection established to EG4_LL
2024-06-30 12:11:07.829009500 Traceback (most recent call last):
2024-06-30 12:11:07.829019500   File "/opt/victronenergy/dbus-serialbattery/dbus-serialbattery.py", li           ne 291, in <module>
2024-06-30 12:11:07.829023500     main()
2024-06-30 12:11:07.829024500   File "/opt/victronenergy/dbus-serialbattery/dbus-serialbattery.py", li           ne 238, in main
2024-06-30 12:11:07.829028500     helper = DbusHelper(battery)
2024-06-30 12:11:07.829030500   File "/opt/victronenergy/dbus-serialbattery/dbushelper.py", line 51, i           n __init__
2024-06-30 12:11:07.829033500     for c in self.battery.unique_identifier()
2024-06-30 12:11:07.829147500 TypeError: 'str' object is not callable
2024-06-30 12:12:10.611236500 *** CCGX booted (0) ***
2024-06-30 12:16:51.572259500 *** CCGX booted (0) ***
2024-06-30 12:21:29.614406500 *** CCGX booted (0) ***
2024-07-02 10:58:41.618424500 *** CCGX booted (0) ***
2024-07-02 11:07:01.503530500 *** CCGX booted (0) ***
2024-07-02 11:14:04.620909500 *** CCGX booted (0) ***
2024-07-02 13:39:19.513800500 *** CCGX booted (0) ***
2024-07-02 13:47:04.604420500 *** CCGX booted (0) ***
2024-07-02 13:51:15.357418500 INFO:SerialBattery:
2024-07-02 13:51:15.358068500 INFO:SerialBattery:Starting dbus-serialbattery
2024-07-02 13:51:15.360247500 INFO:SerialBattery:Venus OS v3.40~33
2024-07-02 13:51:15.360928500 INFO:SerialBattery:dbus-serialbattery v1.4.20240629dev
2024-07-02 13:51:31.379993500 INFO:SerialBattery:-- Testing BMS: 1 of 3 rounds
2024-07-02 13:51:31.380004500 INFO:SerialBattery:Testing Daly at address "\x40"
2024-07-02 13:51:31.530896500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-07-02 13:51:31.530905500 INFO:SerialBattery:Testing Daly at address "\x80"
2024-07-02 13:51:31.672625500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-07-02 13:51:31.674048500 INFO:SerialBattery:Testing Ecs
2024-07-02 13:51:31.756574500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-07-02 13:51:31.757324500 INFO:SerialBattery:Testing EG4_Lifepower
2024-07-02 13:51:32.051576500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-07-02 13:51:32.054191500 INFO:SerialBattery:Testing EG4_LL at address "\x7c"
2024-07-02 13:51:32.227997500 INFO:SerialBattery:== Modbus packet good ==
2024-07-02 13:51:32.388582500 INFO:SerialBattery:== Modbus packet good ==
2024-07-02 13:51:32.389806500 INFO:SerialBattery:===== HW Info =====
2024-07-02 13:51:32.390444500 INFO:SerialBattery:Battery Make/Model: FEG4-12.8V400Ah-V1.0
2024-07-02 13:51:32.391040500 INFO:SerialBattery:Hardware Version: Z01T01
2024-07-02 13:51:32.391599500 INFO:SerialBattery:Serial Number: 2022-10-25
2024-07-02 13:51:32.392137500 INFO:SerialBattery:===== BMS Data =====
2024-07-02 13:51:32.392748500 INFO:SerialBattery:Cell Total Voltage: 14.036v | Current: 0.0A
2024-07-02 13:51:32.393382500 INFO:SerialBattery:Capacity Left: 400 of 400.0 AH
2024-07-02 13:51:32.394334500 INFO:SerialBattery:SoC: 100% - Stanby
2024-07-02 13:51:32.395366500 INFO:SerialBattery:===== DVCC State =====
2024-07-02 13:51:32.396122500 INFO:SerialBattery:DVCC Charger Mode: None
2024-07-02 13:51:32.396812500 INFO:SerialBattery:DVCC Charge Voltage: Nonev
2024-07-02 13:51:32.397494500 INFO:SerialBattery:Charge Current: None | Discharge Current: None
2024-07-02 13:51:32.398149500 INFO:SerialBattery:Charge Limit: None | Discharge Limit: None
2024-07-02 13:51:32.398906500 INFO:SerialBattery:===== Warning/Alarms =====
2024-07-02 13:51:32.399477500 INFO:SerialBattery: No Warnings - 0000
2024-07-02 13:51:32.400023500 INFO:SerialBattery: No Protection Events - 0000
2024-07-02 13:51:32.400625500 INFO:SerialBattery: No Errors - 0000
2024-07-02 13:51:32.401973500 INFO:SerialBattery:===== Temp =====
2024-07-02 13:51:32.403132500 INFO:SerialBattery:Temp 1: 26c | Temp 2: 22c | Temp Mos: 23c
2024-07-02 13:51:32.403952500 INFO:SerialBattery:Avg: 22c | Temp Max: 23c
2024-07-02 13:51:32.404791500 INFO:SerialBattery:Heater Status: False
2024-07-02 13:51:32.405334500 INFO:SerialBattery:===== Battery Stats =====
2024-07-02 13:51:32.405947500 INFO:SerialBattery:SoH: 100% | Cycle Count: 2
2024-07-02 13:51:32.406745500 INFO:SerialBattery:Max Charging Current: 220 A
2024-07-02 13:51:32.407357500 INFO:SerialBattery:===== Cell Stats =====
2024-07-02 13:51:32.408066500 INFO:SerialBattery:Cell 0 Voltage: 3.517
2024-07-02 13:51:32.408737500 INFO:SerialBattery:Cell 1 Voltage: 3.487
2024-07-02 13:51:32.409389500 INFO:SerialBattery:Cell 2 Voltage: 3.514
2024-07-02 13:51:32.410036500 INFO:SerialBattery:Cell 3 Voltage: 3.518
2024-07-02 13:51:32.411001500 INFO:SerialBattery:Cell Max/Min/Diff: (3.518/3.487/0.031)v
2024-07-02 13:51:32.680426500 INFO:SerialBattery:== Modbus packet good ==
2024-07-02 13:51:32.681225500 INFO:SerialBattery:Connection established to EG4_LL
2024-07-02 13:51:32.740389500 Traceback (most recent call last):
2024-07-02 13:51:32.740398500   File "/opt/victronenergy/dbus-serialbattery/dbus-serialbattery.py", li           ne 291, in <module>
2024-07-02 13:51:32.740402500     main()
2024-07-02 13:51:32.740403500   File "/opt/victronenergy/dbus-serialbattery/dbus-serialbattery.py", li           ne 238, in main
2024-07-02 13:51:32.740407500     helper = DbusHelper(battery)
2024-07-02 13:51:32.740409500   File "/opt/victronenergy/dbus-serialbattery/dbushelper.py", line 51, i           n __init__
2024-07-02 13:51:32.740412500     for c in self.battery.unique_identifier()
2024-07-02 13:51:32.740628500 TypeError: 'str' object is not callable
2024-07-02 13:59:04.613304500 *** CCGX booted (0) ***

Any other information that may be helpful
No response

My bad, sorry!
Yes, that is now working!! everything seems good thus far.  I've got 3 batteries in my system total, so I'll have to look at combining them.  Thanks for the quick fix!

Is it possible to daisy chain the batteries over RS485 and give them different addresses?

Yes, they are currently all connected and different addresses.  Would the battery aggregator in your repo work?

Oh ok. I don't know how the batteries behave in this situation, since they are internally connected and not with RS485.

Those batteries look like they're connected the same way as Renogy batteries. They probably have or could be set to have unique Modbus device addresses.   Then they could all connect to the dbus driver over a single RS485-USB serial cable.

@BlueY21 Yea, I have them set with different addresses.  I just don't think the multi battery beta includes the EG4 code.  Because when I install it, nothing shows.  But when I install the nightly build it seems to work perfect for a single battery.

You're right.  I think the multi-battery on one cable code may only be in
the Renogy module.
On Wed, Jul 3, 2024 at 9:55 PM Justice12t @.***> wrote:

@BlueY21 https://github.com/BlueY21 Yea, I have them set with different
addresses. I just don't think the multi battery beta includes the EG4 code.
Because when I install it, nothing shows. But when I install the nightly
build it seems to work perfect for a single battery.
—
Reply to this email directly, view it on GitHub
https://github.com/Louisvdw/dbus-serialbattery/issues/1091#issuecomment-2207861090,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BC63RO7FHJOBLTV5GHXI2KTZKSTRRAVCNFSM6AAAAABKHWUPHCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBXHA3DCMBZGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

I updated the multiple batteries branch. Maybe it works now.

Thanks.  I can get it to show on the GX now.  I seem to be struggling with the modbus address.  If I leave it blank in the config.default.ini file it will work for one battery.  If I adjust it to 0x31, 0x32, 0x33 as I think it should be with my batteries being numbered 1, 2 and 3 via the dip switches.  Is there a command I can run to see what modbus address it is pulling to see if that points me in the right direction?  Threw a donation your way.  Really appreciate all the work on this.

Please continue in this discussion: https://github.com/mr-manuel/venus-os_dbus-serialbattery/discussions/46


Potential accidental capture of loop variable in Boxer

Hello!
Within the last list comprehension in this return statement, the cond value will always take the value of the last element of conds:
https://github.com/nltk/nltk/blob/4a130f1cdf642327378a4387b319cd2df6f79287/nltk/sem/boxer.py#L533-L537
This seems like it would be unexpected or undesired behaviour.
For those unaware of what I'm talking about, a Python implementation detail causes the following:
int_list = [1, 2, 3, 4, 5]
functions = [
    lambda: print(i)
    for i in int_list
]
for func in functions:
    func()

outputs
5
5
5
5
5

while one might expect
1
2
3
4
5

I don't have the time to look into this now, and I'm not sure if this affects many people, so that's why I'll just write it as an issue instead. This probably isn't the highest priority issue, by the way.

Tom Aarsen

i would like to contribute


Jest // markers at non-test files.

Hi since the last update of vscode-jest, I randomly find empty jest markers // at non test files.

Im on vscode-jest 2.2.0 / jest 20.0.3 / create-react-app canary ...

I've seen this also, off-hand I'm not certain what this is

They are also shown in test files.

Disabling InlineErrorMessages by setting "jest.enableInlineErrorMessages": false,
make them disappear.

Chevrolet K2500 2WD, 8 cyl Gas, AT
Our postal address: Zeughofstraße 20, Berlin 10997

From: Markus Hubig<EMAIL_ADDRESS>Sent: Sunday, May 21, 2017 4:16:36 AM
To: orta/vscode-jest
Cc: Subscribed
Subject: Re: [orta/vscode-jest] Jest // markers at non-test files. (#112)
Disabling InlineErrorMessages by setting "jest.enableInlineErrorMessages": false,
make them disappear.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/orta/vscode-jest/issues/112#issuecomment-302930318, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AagoZlbis_Yx7LlkoZQtxbI1DK-EUc4aks5r8B0UgaJpZM4NhCsn.

Maybe some regex is doing something wrong. Do you have any public project where this always happens?

I keep finding these randomly in my files as well. I'll turn off inline Error messages as a temporary fix. Just chiming in to keep this on the radar.

Do you have a sample repository we can look at to try to reproduce?

Not quite the same cause, but the symptom is the same. If an error stack trace has an incorrect line number when it's transpiled and mapped, you can get some weird results. It happens in our repo. :disappointed:


pyxasm token collector cannot handle function docs strings in qjit kernel

The following causes an assertion to be triggered
@qjit
def oracle(q : qreg):
    """
    Define the oracle for our phase estimation algorithm,
    a T gate on the last qubit
    """
    ... oracle code ...

but this does not
@qjit
def oracle(q : qreg):
    ... oracle code ...

I guess this might be because we're doing single-line parsing of the Python code. We probably need to track the scope of these multi-line comment blocks in the handler.


Add Nearby Selection example (not just docs)

A duplicate of more specific https://github.com/TimefoldAI/timefold-quickstarts/issues/124.


Entity utils

https://github.com/Featuretools/featuretools/issues/338

Continue the work here: https://github.com/Featuretools/featuretools/pull/423


feat(editor): add isParsing property

Codecov Report

Merging #25 (f05e802) into master (c453b30) will increase coverage by 0.11%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #25      +/-   ##
==========================================
+ Coverage   92.03%   92.15%   +0.11%
==========================================
  Files          10       10
  Lines         201      204       +3
==========================================
+ Hits          185      188       +3
  Misses         16       16

Impacted Files
Coverage Δ

packages/rdf-editor/src/RdfEditor.js
95.00% <100.00%> (+0.12%)
: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 c453b30...f05e802. Read the comment docs.


About the hyperparameter anchor_points

Nice work! Regarding the selection of the hyperparameter anchor_points, I noticed that your code provides quite a few predefined settings for different datasets. Could you tell me how these settings were determined in your code? Additionally, if I need to train on a custom dataset, how should I choose the optimal anchor_points?

Hi @Chenguoz ,
For each bin, the anchor point (in the paper we call it the representative count value) is obtained by averaging the count values falling into that bin. You may also try to use the middle point of each bin (e.g., 3 for the bin [2, 4)) as the anchor point to avoid complication.
Many thanks,
Yiming


Properties which implement KeyedCollection should emit uniqueItems: true

Fixes #945
KeyedCollection by it's nature is a collection of unique items, so uniqueItems: true should be set in the schema for properties of this type or implementing this type

Needs more work


fixprevent null pointer access if translate expression fails

Proposed changes
pick from master https://github.com/apache/doris/pull/33990

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

run buildall

can you add some test case？

can you add some test case？

I found the NPE in some unexpected scenario. Like user defined var is not replaced by literal in right place would cause the translation fail. After the bug is fixed, there is not NPE now. So this is just a fail-safe for unexpected fail in future.


[BUG] Empty response message when using signup

Describe the bug
Error Status 400: Empty response message. Maybe enabled Two-factor auth? when using the signup method to create a new account.
To Reproduce
Mostly taken from SignUpTestCase:
  client = Client()
  client.delay_range = [1, 3]
  client.set_proxy('socks5://...')

  # signup() doesn't set device_id but it needs it
  client.device_id = "android-%s" % hashlib.sha256(str(time.time()).encode()).hexdigest()[:16]

  email =<EMAIL_ADDRESS>  display_name = 'John Smith'
  username = 'jsmith123512'
  password = 'can389maw39mxruaj'
  phone_number = '+15559202020'

  user = client.signup(
    username, password, email, phone_number, display_name,
    year=random.randint(1970, 2004),
    month=random.randint(1, 12),
    day=random.randint(1, 28)
  )

Traceback
2024-05-23 11:49:02,420:INFO - https://i.instagram.com/api/v1/consent/get_signup_config/
2024-05-23 11:49:04,130:INFO - None [200] GET https://i.instagram.com/api/v1/consent/get_signup_config/?guid=9c636551-da32-4c5c-9416-9378d5c5fd57&main_account_selected=False (2<IP_ADDRESS>.75, OnePlus 6T Dev)
2024-05-23 11:49:06,605:INFO - https://i.instagram.com/api/v1/users/check_email/
2024-05-23 11:49:07,580:INFO - None [200] POST https://i.instagram.com/api/v1/users/check_email/ (2<IP_ADDRESS>.75, OnePlus 6T Dev)
2024-05-23 11:49:10,653:INFO - https://i.instagram.com/api/v1/accounts/send_verify_email/
2024-05-23 11:49:12,275:INFO - None [200] POST https://i.instagram.com/api/v1/accounts/send_verify_email/ (2<IP_ADDRESS>.75, OnePlus 6T Dev)
Enter code (6 digits) for [redacted] (1): 549160
Enter code "549160" for [redacted] (1 attempts, by 5 seconds)
2024-05-23 11:49:40,619:INFO - https://i.instagram.com/api/v1/accounts/check_confirmation_code/
2024-05-23 11:49:43,393:INFO - None [200] POST https://i.instagram.com/api/v1/accounts/check_confirmation_code/ (2<IP_ADDRESS>.75, OnePlus 6T Dev)
2024-05-23 11:49:47,801:INFO - https://i.instagram.com/api/v1/accounts/create/
2024-05-23 11:49:48,476:INFO - None [400] POST https://i.instagram.com/api/v1/accounts/create/ (2<IP_ADDRESS>.75, OnePlus 6T Dev)
2024-05-23 11:49:48,476:ERROR - 400 Client Error: Bad Request for url: https://i.instagram.com/api/v1/accounts/create/
Traceback (most recent call last):
  File "/private/var/tmp/_bazel_[redacted]/c1a212f4a3cbc7222015ce889f25da32/execroot/_main/bazel-out/darwin_arm64-fastbuild/bin/instagram/cli.runfiles/pypi_instagrapi/site-packages/instagrapi/mixins/private.py", line 359, in _send_private_request
    response.raise_for_status()
  File "/private/var/tmp/_bazel_[redacted]/c1a212f4a3cbc7222015ce889f25da32/execroot/_main/bazel-out/darwin_arm64-fastbuild/bin/instagram/cli.runfiles/pypi_requests/site-packages/requests/models.py", line 1021, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: https://i.instagram.com/api/v1/accounts/create/
2024-05-23 11:49:48,479:WARNING - Status 400: Empty response message. Maybe enabled Two-factor auth?
Error creating account: 400 Client Error: Bad Request for url: https://i.instagram.com/api/v1/accounts/create/

Expected behavior
A clear and concise description of what you expected to happen.
Desktop (please complete the following information):

OS: macOS Ventura 13.6.2
Python version: 3.12
instagrapi version: 2.1.2

that because instagrapi add more key when send data (thats what i found), so just remove the unrequired data when sending to endpoint accounts/create/

that because instagrapi add more key when send data (thats what i found), so just remove the unrequired data when sending to endpoint accounts/create/

see https://github.com/subzeroid/instagrapi/pull/1938

the signup method returns Instagram User after account creation :
pk='68663412806' username='Instagram User' full_name='' profile_pic_url=Url('https://instagram.fhex2-1.fna.fbcdn.net/v/t51.2885-19/44884218_345707102882519_2446069589734326272_n.jpg?_nc_ht=instagram.fhex2-1.fna.fbcdn.net&_nc_cat=1&_nc_ohc=nOPs76iqbjsQ7kNvgGaAit5&edm=AJ9x6zYBAAAA&ccb=7-5&ig_cache_key=YW5vbnltb3VzX3Byb2ZpbGVfcGlj.2-ccb7-5&oh=00_AYCWDUV_axRwc_xMinkPZlq9p_G9oeeUqEN0DVBrvJzIFg&oe=66BC130F&_nc_sid=65462d') profile_pic_url_hd=None is_private=True

Troubleshooting Steps:
1.	Check for Two-Factor Authentication: Ensure that 2FA is not interfering with the process.
2.	Switch Proxies: Try using a different proxy or disable it temporarily.
3.	Wait and Retry: If rate limiting might be the issue, wait for a while before trying again.
4.	Update the Instagrapi Version: Ensure that the package is up-to-date.
5.	Check the Data Consistency: Double-check all input data for validity and consistency.
6.	Use a Different Device ID Generation Strategy: Consider using a more stable and realistic device ID.

If none of these solutions work, you might want to debug further by capturing the exact request and response details to understand better why Instagram is rejecting the request.

import hashlib
import time
import random
from instagrapi import Client
client = Client()
client.delay_range = [1, 3]
Optional: Set User-Agent if not handled by Client
client.set_user_agent("Instagram <IP_ADDRESS>.114 Android (28/9; 320dpi; 720x1280; Xiaomi; HM 1SW; armani; qcom; en_US)")
Set proxy if necessary
client.set_proxy('socks5://...')
Generate and set device_id
client.device_id = "android-%s" % hashlib.sha256(str(time.time()).encode()).hexdigest()[:16]
email =<EMAIL_ADDRESS>display_name = 'John Smith'
username = 'jsmith123512'
password = 'can389maw39mxruaj'
phone_number = '+15559202020'
Encrypt the password if required
encrypted_password = client.password_encrypt(password)
try:
user = client.signup(
username, encrypted_password, email, phone_number, display_name,
year=random.randint(1970, 2004),
month=random.randint(1, 12),
day=random.randint(1, 28)
)
print("Account created successfully:", user)
except Exception as e:
print("Error creating account:", e)


The "comment bubble" should not be shown when there are no comments

@bruskiza @smn @miltontony tiny review please :)

:+1:


Constrain return statements in generator functions.

Generator functions should constrain their return types to match the result type of the return method on their declared Iterator subtype.
This is deeply related to https://github.com/Microsoft/TypeScript/issues/2983 - but I wanted to call it out separately because it's a small subset of the total changes required to completely support iterators as coroutines.
TypeScript Version:  2.5.2
Code
interface Iterator<T> {
    next(value?: any): IteratorResult<T>;
    return?(value?: any): IteratorResult<any>; // changed to represent current reality.
    throw?(e?: any): IteratorResult<T>;
}

type Effect = { op: string };

interface Coroutine extends Iterator<Effect> {
    // Override return to constrain return values to Effect.
    return?(value?: any): IteratorResult<Effect>;
}

interface Process extends Coroutine {
    [Symbol.iterator](): Coroutine;
}

let f = function* (): Process {
    yield { op: 'tick' }; // OK.
    yield 1; // Expected error: Not an effect.
    return 1; // Unexpected lack of error! Not an Effect.
}

@mhegazy @RyanCavanaugh @rbuckton can you please take a look at https://github.com/Microsoft/TypeScript/pull/23571?

I think generator function's return type is not constrained by iterator type. At least that return type can be undefined.

I do not think this is the correct solution to this issues. the underlying issue here is that the generator has two possible return states, and each has a possibly different type. each type is witnessed in different use case (done: true vs done: false). The solution thus is not to restrict return to fit the yielded type, but rather to correctly model the generator interface.
https://github.com/Microsoft/TypeScript/issues/11375 tracks correctly modelling the generator interface and correctly inferring the the three type, 1. yielded values, 2, returned values, and 3. yield expression type (input to next).


[Feature] - Add snippets in markdown instead Json.

What feature would you like to see?
While adding code in array it gets hard to manage indentation.
And we can use something like directories and files with markdown.
and properties too for storing metadata and a category json.
Similar to docusaurus setup.

This is already being fixed by #39, we will not change the format used to save snippets, but instead provide tools that makes it easier to create snippets.


⚠ PrivateHD has degraded performance

In d5670ed, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 2192 ms

Resolved: PrivateHD performance has improved in 0aed243.


DBZ-242 Corrected MySQL filters to handle built-in tables

When the table.ignore.built is set to false, the MySQL connector included all of the ~250 system tables yet the database and table filters were never applied to these system tables and therefore all would be captured. With this change, the database filters and table filters now apply to the system tables should they not be ignored.
Note that this does change the behavior of the connector when table.ignore.built is set to false. However, it is unlikely that anyone is seriously capturing all of the system table changes, so correcting the behavior is the preferred solution.

@gunnarmorling please review and merge if acceptable.

Rebased and merged. Thanks, @rhauch! Do we have a wiki page or so with migration notes where we could document the changed behavior for system tables?

We have the CHANGELOG.md that's part of the code base and the releases page that's on the website. Unfortunately they currently have to be updated separately. Feel free to make the changes or reopen the issue for me to fix on Monday.


Fixed inconsistencies in references.json file.

While trying to parse the data from references.json I found out that in one case an attack vector object was added without any <key, value> pair.
Another inconsistency I found was that a safeguard was added to the attack vector list.
I think these might be small inconsistencies and so I created a pull request without creating an issue.
[N.B.]: This is the signed version of PR-76.

Thank you very much @imranur-rahman


Make Library easily usable on Unix systems

Remove spaces from file and folder names.  Replace with _
Lowcase all file names.  If a users puts the library in the autocall path (the path SAS looks for macros without having %include the files) on UNIX, the uppercase filename will cause an error.

Fixed by #264


Upgrade Remnux "remnux-version: v2023.40.2" --> "renux-version: v2023.45.1 "Fails "Exit=Not Zero""

Hi,
Having a couple issues and was hoping someone can help me to resolve going forward. Linux skills are good, But, Remnux is still fairly new. I have attached the saltstack.log
saltstack.log
k.log
Update returned exit code not zero
Error: Update returned exit code not zero
at ChildProcess. (/snapshot/remnux-cli/remnux-cli.js:571:23)
at ChildProcess.emit (events.js:315:20)
saltstack.log
at maybeClose (internal/child_process.js:1021:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)

Sometimes problems occur due to network or server issues when
downloading packages, in which case retrying your operation
a bit later might lead to good results.
To determine the nature of the issue, please review the
saltstack.log file under /var/cache/remnux/cli in the
subdirectory that matches the REMnux version you're installing.
Search for the log file for "result: false" messages and look at
the surrounding lines to diagnose the issue.
For assistance go to https://github.com/REMnux/remnux-cli/issues

Hi @johnsageeek , it looks as if you've fallen prey to the "METADATA" issue which occurred with earlier versions of pip, setuptools, and wheel. Try running this command and the install process should succeed on the next go 'round:
sudo pip install --break-system-packages --force-reinstall protobuf==3.20.3

Let us know how this works out!
Cheers!

Hi @johnsageeek , did my suggestion manage to resolve your issue?

@lennyzeltser I think we should be able to close this issue.

@lennyzeltserhttps://github.com/lennyzeltser  Yes, please do. Thanks
From: Digital Sleuth  <>
Sent: Monday, May 20, 2024 8:13 PM
To: @.***
Cc: John M @.>; Mention @.>
Subject: Re: [REMnux/remnux-cli] Upgrade Remnux "remnux-version: v2023.40.2" --> "renux-version: v2023.45.1 "Fails "Exit=Not Zero"" (Issue #157)
[IronVest]
You can reply directly and still remain anonymous.
To protect your privacy, do not forward this message, or add new recipients like CCs or BCCs.
Is this email spam or just don't want to see it anymore? Disable @.***/toggle>
@lennyzeltserhttps://github.com/lennyzeltser I think we should be able to close this issue.

Reply to this email directly, view it on GitHubhttps://github.com/REMnux/remnux-cli/issues/157#issuecomment-2121518525, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AR5TOOZOE7W465Q2EB3Z423ZDKNRXAVCNFSM6AAAAABAIFG376VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRRGUYTQNJSGU.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Hi @johnsageeek , it looks as if you've fallen prey to the "METADATA" issue which occurred with earlier versions of pip, setuptools, and wheel. Try running this command and the install process should succeed on the next go 'round:
sudo pip install --break-system-packages --force-reinstall protobuf==3.20.3

Let us know how this works out! Cheers!

Sorry for the long delayed response. Your suggestion worked as stated. It also prompted me to update the pip <python3 -m pip install --upgrade pip> which was helpful. Thanks for the feedback, I will monitor my Github email more.

@lennyzeltserhttps://github.com/lennyzeltser Yes, please do. Thanks From: Digital Sleuth <> Sent: Monday, May 20, 2024 8:13 PM To: @.*** Cc: John M @.>; Mention @.> Subject: Re: [REMnux/remnux-cli] Upgrade Remnux "remnux-version: v2023.40.2" --> "renux-version: v2023.45.1 "Fails "Exit=Not Zero"" (Issue #157) [IronVest] You can reply directly and still remain anonymous. To protect your privacy, do not forward this message, or add new recipients like CCs or BCCs. Is this email spam or just don't want to see it anymore? Disable @./toggle> @lennyzeltserhttps://github.com/lennyzeltser I think we should be able to close this issue. - Reply to this email directly, view it on GitHub<#157 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AR5TOOZOE7W465Q2EB3Z423ZDKNRXAVCNFSM6AAAAABAIFG376VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRRGUYTQNJSGU. You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>
Thanks for the effort. :)


Self-checkpointed checkpointer crashloops

I noticed this on a running cluster:
diegs@xps13:~% kubectl --kubeconfig=kubeconfig -n kube-system get pods
NAME                                                              READY     STATUS             RESTARTS   AGE
...
pod-checkpointer-k3wfq                                            1/1       Running            0          18m
pod-checkpointer-k3wfq-ip-10-0-31-93.us-west-1.compute.internal   0/1       CrashLoopBackOff   12         17m
diegs@xps13:~% kubectl --kubeconfig=kubeconfig -n kube-system logs pod-checkpointer-k3wfq-ip-10-0-31-93.us-west-1.compute.internal
I0524 21:39:59.800790       1 main.go:106] Trying to acquire the flock at "/var/run/lock/pod-checkpointer.lock"

I'm not sure why the process is exiting there. The flock call should be blocking indefinitely. Kubernetes says it's exiting with code 2:
diegs@xps13:~% kubectl --kubeconfig=kubeconfig -n kube-system describe pod pod-checkpointer-k3wfq-ip-10-0-31-93.us-west-1.compute.internal
Name:		pod-checkpointer-k3wfq-ip-10-0-31-93.us-west-1.compute.internal
Namespace:	kube-system
Node:		ip-10-0-31-93.us-west-1.compute.internal/<IP_ADDRESS>
Start Time:	Wed, 24 May 2017 14:23:12 -0700
Labels:		k8s-app=pod-checkpointer
		pod-template-generation=1
		tier=control-plane
Status:		Running
IP:		<IP_ADDRESS>
Controllers:	<none>
Containers:
  checkpoint:
    Container ID:	docker://fd5bfdf7c327ce5afdb56323f9dadc75edf479c78df6f83651146f8094c3d86b
    Image:		quay.io/coreos/pod-checkpointer:7da334a1d768c346798601eb8387f266d15cf330
    Image ID:		docker-pullable://quay.io/coreos/pod-checkpointer@sha256:9f696878633bc763c1fbe34e04e40db43d72a4500346fc05f735715818767475
    Port:
    Command:
      /checkpoint
      --v=4
      --lock-file=/var/run/lock/pod-checkpointer.lock
    State:		Waiting
      Reason:		CrashLoopBackOff
    Last State:		Terminated
      Reason:		Error
      Exit Code:	2
      Started:		Mon, 01 Jan 0001 00:00:00 +0000
      Finished:		Wed, 24 May 2017 14:50:17 -0700
    Ready:		False
    Restart Count:	16
    Volume Mounts:
      /etc/kubernetes from etc-kubernetes (rw)
      /var/run from var-run (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-d456j (ro)
    Environment Variables:
      NODE_NAME:	 (v1:spec.nodeName)
      POD_NAME:		pod-checkpointer-k3wfq-ip-10-0-31-93.us-west-1.compute.internal (v1:metadata.name)
      POD_NAMESPACE:	kube-system (v1:metadata.namespace)
Conditions:
  Type		Status
  Initialized 	True
  Ready 	False
  PodScheduled 	True
Volumes:
  etc-kubernetes:
    Type:	HostPath (bare host directory volume)
    Path:	/etc/kubernetes
  var-run:
    Type:	HostPath (bare host directory volume)
    Path:	/var/run
  default-token-d456j:
    Type:	HostPath (bare host directory volume)
    Path:	/etc/kubernetes/checkpoint-secrets/kube-system/pod-checkpointer-k3wfq/default-token-d456j
QoS Class:	BestEffort
Tolerations:	<none>
No events.

The code itself should be logging an error if the flock system call fails, and glog.Flush() should also be running. Perhaps an uncaught panic is happening somewhere?
The manifests for the deployed and self-checkpointed pods are attached. I don't see a meaningful difference.
pod-checkpointer-k3wfq.yaml.txt
pod-checkpointer-k3wfq-ip-10-0-31-93.us-west-1.compute.internal.yaml.txt
cc @aaronlevy who I think also saw this today.

I have a feeling that this is being surfaced due to the atomic rename change.
The docker containers are exiting roughly every 3 seconds, and that's about how often we check if we should be starting the checkpoint. In this case we're trying to start the checkpointer itself every 3 seconds, then it's failing (also see the active checkpoint timestamp being updated).
Likely want to check if active checkpoint already exists, and don't overwrite if so (do we assume it's okay if it exists or should we check hash of contents match?)

@aaronlevy I'm not sure if I follow your explanation, but is this a regression?


[stable/gangway] - add option to extend env

Is this a new chart
no
What this PR does / why we need it:
currently, there is no option to add custom environment variables to the deployment config of gangway. Since a few of the configuration options are sensitive (GANGWAY_SESSION_SECURITY_KEY, GANGWAY_CLIENT_SECRET) I think we should be able to set these via pre-existing secrets.
Which issue this PR fixes
none
Special notes for your reviewer:
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @rk295

/ok-to-test

since https://github.com/helm/charts/pull/20486 is already merged there is now a way to specify environment variables. introducing this change would be a breaking change now because my solutions do not map key: value to environment variables but uses the toYaml.
the existing PR is no solution to my problem though since I need to add an environment variable passed on a secret. I'll try to fork again from the new master and maybe adds a secretEnv option wich also maps secrets to environment variables.


Remove file renaming from podspec

Both the prepare script and the podspec template, once https://github.com/CocoaPods/CocoaPods/issues/1437 is solved.

This was fixed by PR #3817.


Enable download in both formats: CSV and JSON

For historic reasons we allow downloading evaluation results in CSV and datasets in JSON. There is no reason to disallow the other format, so we should allow both CSV and JSON in both places.
UI: I would like to make the download button a dropdown, so that when you click "Donwload" there are buttons that appear under it: "Download CSV" and "Download JSON", somewhat like Supabase's "Export button".

Pointers:

Bare JSON download in dataset: https://github.com/lmnr-ai/lmnr/blob/main/frontend/app/api/projects/[projectId]/datasets/[datasetId]/download/route.ts
CSV conversion before download in https://github.com/lmnr-ai/lmnr/blob/main/frontend/app/api/projects/[projectId]/evaluations/[evaluationId]/download/route.ts#L69-L72

I'd like to work on this issue. Could you please assign it to me?

Addressed in #272


WIP: Implement backend for bitcoinsearch app

[x] Create routes for the search route
[x] Add business logic to the controllers
[ ] Write transformers for the response
[x] Write tests (Optional)

How do we handle these couple of features:

Pagination. query params? part of the request body?

what of filters: I noticed we have an implementation that uses facets in the request body
{
   "searchString": "bip "
   "facets": [
        {"field": "authors", "value": "pieter"}
     ]
}

The above implementation does work, but only for the "authors" field. Tags and domains don't.

what of sorting?

Also, can we have docs for the API? it would be really helpful compared to looking through the code to find what is possible and what isn't.
cc: @adamjonas


fix: removed line clamp plugin (included by default)

Describe the changes you have made in this PR

But don't we use line-clamp in our files? Is it not related to that? I didn't remove it because of that reason

Have a look at the screenshot I posted, you'll see the build warning there:
It's included by default (I removed it and the clamping still works).

It's included by default (I removed it and the clamping still works).

Aaah 😄 Sorry, I misunderstood it as the plugin is included by default (in addition, in default), so I thought, why are we removing this? So it must mean it is included in the main one by default, without the need to add anything; got it!


Corrected find and replace path seperator for Windows

We implemented this previously but removed it in a debugging step, this was never an issue and is a required fix to run pancake with sass on Windows.

Hold this until we merge #107


4.B. Submission

Submit project on ETHBerlin04 portal
Starting point: https://projects.ethberlin.org/teams/982
See top of our Notes doc https://hackmd.okfn.de/gZi7aAdoQ7a1tUrExYR_Sw?both.
@step21 @theotow @YYBer please all help fill out the 'challenges', and especially the final point 'technology used'. Thanks!

11:20 on 26-5


Question - Accessing home folder?

Hello
I was wondering if there is a reason the package is trying to access my home folder? I have the following filesystem lay-out with an open_basedir restriction:

~ (access not allowed)

~/Projects (access allowed)

~/Projects/MyProject (access allowed)

~/.atom/packages/atom-autocomplete-php/ (access allowed)

For some reason, when opening MyProject, php/parser.php generates a warning that an attempt was made to chdir() to the home folder (~). This message doesn't seem to break any functionality, but I thought I'd ask anyway to be sure this wasn't an unintended side effect.
Thanks in advance

Hello,
There will be a side effect. In fact, the package is writing an index file in ~/.atom/packages/atom-autocomplete-php/indexes to get all class names. (required for use .... and new .... autocompletion).
Regards,
Peekmo

After some debugging the error seems to be originating from Tools.php:21 where composer is executed. The error is actually being generated by composer and I think it's using the default working directory (which would then be my home folder). Adding this before that line seems to solve the issue:
chdir(Config::get('projectPath'));

Hi,
I'll look if there's no side effect to use a chdir.
Thank you

Hello,
Could you please tell me if the last version is broken for you ?
Thanks

Hello, thanks for the commit, I will try to test tomorrow when I have access to my development machine again.

Seems to be fixed, thanks!

Thank you :)


Datepicker doesn't appear fullscreen when inside card-reveal

I'd tried to put datepicker inside .card-reveal but when i clicked it, it shows only inside card-reveal and not appear in full screen.
you can look in:
http://codepen.io/muktisuperior/pen/vGbYmG
Thanks.

Used container option with pickadate
http://amsul.ca/pickadate.js/date/#container
;-)

Waa thank you it's work


Add reference to article on 'IDataView Type System' when talking about IDataView

At the end of the page it'd be good to have a references section and add a link pointing to this article focusing on the 'IDataView Type System' for further details deep-diving into the IDataView types:
https://xadupre.github.io/machinelearningext/mlnetdocs/idataviewtypesystem.html

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 6c846fa2-eecd-aab0-3ebf-a52f5c2db94e
Version Independent ID: fd80b6d4-04c0-34a3-09b3-d2d773eef9a3
Content: Inspect intermediate data during ML.NET processing - ML.NET
Content Source: docs/machine-learning/how-to-guides/inspect-intermediate-data-ml-net.md
Product: dotnet-ml
GitHub Login: @luisquintanilla
Microsoft Alias: luquinta

Add to overview doc, and resources.


Multi-Processing goes Berserk

main process stops logging because of the extreme load

will be obviated by #1377


ENH Check composer.json for module type

Issue

https://github.com/silverstripe/module-standardiser/issues/4

Ahh yup fair point. config isn't a Silverstripe CMS module technically, but I'm okay with pretending it is for the purposes of this tool, since we tend to treat it as though it is one.
Done


Better name

I don't think SimpleSL is a good name. I need to choose a better name for this language. If you have an idea for a name, please write it below.

Guitarfish


fix: use current domain as an origin to load demo files

We should be able to load the demo files from the current domain/origin and avoid having CORS errors.

☸ Build auto-deployed at: https://xlayers-29c84c3.angular.run

☸ Build auto-deployed at: https://xlayers-8134672.angular.run


Stop autostart Teams (in View horizon) for specific users

Hi there,
I have installed Microsoft Teams (VMWare Horizon edition) on my master image. Teams will be automatically started by a HKLM registry key.
Not all users in VDI will use Teams, so I would like to start Teams for those users in a specific group but not for the others.
This owuld require a HKCU registry key but this seems to not work.
Any suggestions how to tackle that?
Thanks
Kafipause

@kafipause thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.

@officedocsbot close


Only remove debug symbols from JDK for OpenJ9 builds

OpenJ9 builds capture debug symbols in the debug image; this avoids the duplication while retaining them when present in other (e.g. hotspot) builds.
Fixes: #1972.

@jennli - JIC you wanted to see this change

Thanks!!!

run tests


Reference lamp addition: 600 l/mm grating

Missing file goodman_comp_600UV_CuHeAr.fits
Check values for goodman_comp_600Mid_GG385_HgAr.fits

goodman_com_600Mid_GG385_HgAr.fits Double checked.
Setting GSP_A001 from 5460.75 to 5460.735
Setting GSP_A002 from 5769.61 to 5769.598
Setting GSP_A003 from 5790.67 to 5790.663
Setting GSP_A004 from 6965.431 to 6965.431

File goodman_comp_600UV_CuHeAr.fits was found in a "TODO" directory. Now is wavelength calibrated.


large empty sections (images? code?) in docs

https://reacttraining.com/react-router/web/guides/code-splitting

nvm, the code on the aligns with the doc on the left 👾


Better feature handling

A feature that is a native WebXR feature will not attach if the session was not enabled with it, or that the session doesn't support it.
In addition, a warning will be shown if the feature was initialized after the session has started.

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/14732/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14732/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14732/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/14732/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/14732/merge
https://gui.babylonjs.com/?snapshot=refs/pull/14732/merge
https://nme.babylonjs.com/?snapshot=refs/pull/14732/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/14732/merge#BCU1XR#0


SEGV on unknown address 0x000000000000

$ ./build/sanitize/mujs a.js
ASAN:DEADLYSIGNAL
==14039==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x561be0fa9e67 bp 0x7ffdec50f2d0 sp 0x7ffdec50f2a0 T0)
==14039==The signal is caused by a READ memory access.
==14039==Hint: address points to the zero page.
#0 0x561be0fa9e66 in compile /home/fuzzing/Desktop/mujs/regexp.c:644
#1 0x561be0fab982 in js_regcompx /home/fuzzing/Desktop/mujs/regexp.c:884
#2 0x561be0f89bca in js_newregexp /home/fuzzing/Desktop/mujs/jsregexp.c:19
#3 0x561be0f9e2d7 in Sp_match /home/fuzzing/Desktop/mujs/jsstring.c:338
#4 0x561be0f956f5 in jsR_callcfunction /home/fuzzing/Desktop/mujs/jsrun.c:1041
#5 0x561be0f960b2 in js_call /home/fuzzing/Desktop/mujs/jsrun.c:1083
#6 0x561be0f99ca2 in jsR_run /home/fuzzing/Desktop/mujs/jsrun.c:1511
#7 0x561be0f95498 in jsR_callscript /home/fuzzing/Desktop/mujs/jsrun.c:1024
#8 0x561be0f95f67 in js_call /home/fuzzing/Desktop/mujs/jsrun.c:1079
#9 0x561be0f9bc26 in js_dofile /home/fuzzing/Desktop/mujs/jsstate.c:207
#10 0x561be0fb031d in main /home/fuzzing/Desktop/mujs/main.c:347
#11 0x7f61855fdb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96)
#12 0x561be0f4ec19 in _start (/home/fuzzing/Desktop/mujs/build/sanitize/mujs+0x16c19)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV /home/fuzzing/Desktop/mujs/regexp.c:644 in compile
==14039==ABORTING
"AAAAAAAAAAA".match("(?:!)(?:)")

This is caused by node in compile being NULL

Closing fixed with e2b59201d5049a8ad509b280e729a871756abc99


Update @slack/web-api to 7.3.4 to remove Axios high severity vulnerability

Currently the outdated @slack/web-api dependency is creating a high severity vulnerability due to Axios.
In @slack/web-api 7.3.4, the Axios version was bumped to 1.7.4 to fix this issue.
What are the requirements for this package to update the @slack/web-api dependency?

Hi @Saku75
Will try to fix this this week.


Migrate to Arti

Unfortunately the interface had to be changed but only ever so slightly @sneurlax @rehrar

OK, I merged this in but some types used do not appear to be FFI-safe.  When I run cbindgen to generate tor-ffi.h I get:
~/src/arti_wallet/crypto_plugins/flutter_libarti/native/tor-ffi$ cbindgen --config cbindgen.toml --crate tor-ffi --output target/tor-ffi.h
WARN: Cannot find a mangling for generic path GenericPath { path: Path { name: "TorClient" }, export_name: "TorClient", generics: [Type(Path(GenericPath { path: Path { name: "TokioNativeTlsRuntime" }, export_name: "TokioNativeTlsRuntime", generics: [], ctype: None }))], ctype: None }. This usually means that a type referenced by this generic was incompatible or not found.
WARN: Cannot find a mangling for generic path GenericPath { path: Path { name: "TorClient" }, export_name: "TorClient", generics: [Type(Path(GenericPath { path: Path { name: "TokioNativeTlsRuntime" }, export_name: "TokioNativeTlsRuntime", generics: [], ctype: None }))], ctype: None }. This usually means that a type referenced by this generic was incompatible or not found.
WARN: Can't find TokioNativeTlsRuntime. This usually means that this type was incompatible or not found.
WARN: Can't find TorClient. This usually means that this type was incompatible or not found.
WARN: Can't find TokioNativeTlsRuntime. This usually means that this type was incompatible or not found.
WARN: Can't find TorClient. This usually means that this type was incompatible or not found.

I heard you can pass non-FFI-safe types by also passing the struct via a pointer, but I haven't done this myself yet.  The way I do know how to make work is to change, convert, or cast types towards something FFI-safe, which I'll tinker on

Yes, they are different.  It does build with your bindings, however the example app I made is broken, so I'm fixing that to check if it's actually working or not.

OK, when I run the example here I get
thread 'tokio-runtime-worker' panicked at 'Cannot drop a runtime in a context where blocking is not allowed. This happens when a runtime is dropped from within an asynchronous context.', /home/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/blocking/shutdown.rs:51:21
stack backtrace:
   0:     0x7f811fccac31 - std::backtrace_rs::backtrace::libunwind::trace::h6aeaf83abc038fe6
                               at /rustc/8ede3aae28fe6e4d52b38157d7bfe0d3bceef225/library/std/src/../../backtrace/src/backtrace/libunwind.rs:93:5
   1:     0x7f811fccac31 - std::backtrace_rs::backtrace::trace_unsynchronized::h4f9875212db0ad97
                               at /rustc/8ede3aae28fe6e4d52b38157d7bfe0d3bceef225/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
   2:     0x7f811fccac31 - std::sys_common::backtrace::_print_fmt::h3f820027e9c39d3b
                               at /rustc/8ede3aae28fe6e4d52b38157d7bfe0d3bceef225/library/std/src/sys_common/backtrace.rs:65:5
   3:     0x7f811fccac31 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hded4932df41373b3
                               at /rustc/8ede3aae28fe6e4d52b38157d7bfe0d3bceef225/library/std/src/sys_common/backtrace.rs:44:22
   4:     0x7f811fcf2ecf - core::fmt::rt::Argument::fmt::hc8ead7746b2406d6
                               at /rustc/8ede3aae28fe6e4d52b38157d7bfe0d3bceef225/library/core/src/fmt/rt.rs:138:9
   5:     0x7f811fcf2ecf - core::fmt::write::hb1cb56105a082ad9
                               at /rustc/8ede3aae28fe6e4d52b38157d7bfe0d3bceef225/library/core/src/fmt/mod.rs:1094:21
   6:     0x7f811fcc7a61 - std::io::Write::write_fmt::h797fda7085c97e57
                               at /rustc/8ede3aae28fe6e4d52b38157d7bfe0d3bceef225/library/std/src/io/mod.rs:1713:15
   7:     0x7f811fccaa45 - std::sys_common::backtrace::_print::h492d3c92d7400346
                               at /rustc/8ede3aae28fe6e4d52b38157d7bfe0d3bceef225/library/std/src/sys_common/backtrace.rs:47:5
   8:     0x7f811fccaa45 - std::sys_common::backtrace::print::hf74aa2eef05af215
                               at /rustc/8ede3aae28fe6e4d52b38157d7bfe0d3bceef225/library/std/src/sys_common/backtrace.rs:34:9
   9:     0x7f811fccc097 - std::panicking::default_hook::{{closure}}::h8cad394227ea3de8
  10:     0x7f811fccbe84 - std::panicking::default_hook::h249cc184fec99a8a
                               at /rustc/8ede3aae28fe6e4d52b38157d7bfe0d3bceef225/library/std/src/panicking.rs:288:9
  11:     0x7f811fccc54c - std::panicking::rust_panic_with_hook::h82ebcd5d5ed2fad4
                               at /rustc/8ede3aae28fe6e4d52b38157d7bfe0d3bceef225/library/std/src/panicking.rs:705:13
  12:     0x7f811fccc401 - std::panicking::begin_panic_handler::{{closure}}::h810bed8ecbe66f1a
                               at /rustc/8ede3aae28fe6e4d52b38157d7bfe0d3bceef225/library/std/src/panicking.rs:595:13
  13:     0x7f811fccb066 - std::sys_common::backtrace::__rust_end_short_backtrace::h1410008071796261
                               at /rustc/8ede3aae28fe6e4d52b38157d7bfe0d3bceef225/library/std/src/sys_common/backtrace.rs:151:18
  14:     0x7f811fccc192 - rust_begin_unwind
                               at /rustc/8ede3aae28fe6e4d52b38157d7bfe0d3bceef225/library/std/src/panicking.rs:593:5
  15:     0x7f811f4d0af3 - core::panicking::panic_fmt::ha0a42a25e0cf258d
                               at /rustc/8ede3aae28fe6e4d52b38157d7bfe0d3bceef225/library/core/src/panicking.rs:67:14
  16:     0x7f811fb71999 - tokio::runtime::blocking::shutdown::Receiver::wait::hdabf73f2f022867c
  17:     0x7f811fb63c4d - tokio::runtime::blocking::pool::BlockingPool::shutdown::h7471de1b9a5bdca9
  18:     0x7f811f4d89ae - core::ptr::drop_in_place<tokio::runtime::blocking::pool::BlockingPool>::h96a7fac705d7b8f3
  19:     0x7f811f4dee66 - alloc::sync::Arc<T>::drop_slow::hd236a11bd9fd0877
  20:     0x7f811f4d8cb1 - core::ptr::drop_in_place<tor_rtcompat::impls::tokio::TokioRuntimeHandle>::ha91c69a4fa91f3ed
  21:     0x7f811f4dd9ab - alloc::sync::Arc<T>::drop_slow::h904d286d243ab0e5
  22:     0x7f811f4ff5a6 - tor_guardmgr::daemon::run_periodic::{{closure}}::h9bbf1ab54b5dca00
  23:     0x7f811f9d1508 - tokio::runtime::task::core::Core<T,S>::poll::hafaa76092400a72c
  24:     0x7f811f9d685f - tokio::runtime::task::harness::Harness<T,S>::poll::h72230aab1c808404
  25:     0x7f811fb61db2 - tokio::runtime::scheduler::multi_thread::worker::Context::run_task::hb949ca596a26ed91
  26:     0x7f811fb61376 - tokio::runtime::scheduler::multi_thread::worker::Context::run::h98251bbc435e277d
  27:     0x7f811fb53837 - tokio::runtime::context::scoped::Scoped<T>::set::h8ea79f3d4988635a
  28:     0x7f811fb581ee - tokio::runtime::context::runtime::enter_runtime::h97612f0110e9a9ee
  29:     0x7f811fb60bea - tokio::runtime::scheduler::multi_thread::worker::run::h6cfa134b576f7590
  30:     0x7f811fb567ea - tokio::runtime::task::core::Core<T,S>::poll::h1cf5e3806106d1a2
  31:     0x7f811fb50e1f - tokio::runtime::task::harness::Harness<T,S>::poll::h93be5096c07ae3b0
  32:     0x7f811fb647e6 - tokio::runtime::blocking::pool::Inner::run::hc82320e2005c7226
  33:     0x7f811fb51d15 - std::sys_common::backtrace::__rust_begin_short_backtrace::h213d8fe07065a5c3
  34:     0x7f811fb6ec69 - core::ops::function::FnOnce::call_once{{vtable.shim}}::h1fcbad9084607fae
  35:     0x7f811fcd1055 - <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once::h9adfc2ae43657457
                               at /rustc/8ede3aae28fe6e4d52b38157d7bfe0d3bceef225/library/alloc/src/boxed.rs:1985:9
  36:     0x7f811fcd1055 - <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once::h14fefbfa7b574396
                               at /rustc/8ede3aae28fe6e4d52b38157d7bfe0d3bceef225/library/alloc/src/boxed.rs:1985:9
  37:     0x7f811fcd1055 - std::sys::unix::thread::Thread::new::thread_start::ha211bb47f6f5cedc
                               at /rustc/8ede3aae28fe6e4d52b38157d7bfe0d3bceef225/library/std/src/sys/unix/thread.rs:108:17
  38:     0x7f81f499f609 - start_thread
                               at /build/glibc-SzIz7B/glibc-2.31/nptl/pthread_create.c:477:8
  39:     0x7f81f4c14133 - clone
                               at /build/glibc-SzIz7B/glibc-2.31/misc/../sysdeps/unix/sysv/linux/x86_64/clone.S:95
  40:                0x0 - <unknown>

Going to try another clean approach to see if isolating changes helps

@sneurlax you're importing the old Dart file there. If you make these changes in your branch it works:
igor@igor-laptop:~/Code/sneurlax/tor/example$ git diff lib/main.dart
diff --git a/example/lib/main.dart b/example/lib/main.dart
index b74b65e..63fb6b7 100644
--- a/example/lib/main.dart
+++ b/example/lib/main.dart
@@ -3,7 +3,7 @@ import 'dart:convert';
 import 'dart:io';

 import 'package:flutter/material.dart';
-import 'package:flutter_libtor/flutter_libtor.dart';
+import 'package:flutter_libtor/tor.dart';
 // imports needed for tor usage:
 import 'package:flutter_libtor/models/tor_config.dart';
 import 'package:path_provider/path_provider.dart';
@@ -115,8 +115,7 @@ class _MyAppState extends State<MyApp> {
                           password: passwordController.text);

                       // Start the Tor daemon
-                      await tor.start(
-                          torDir: Directory(torConfig.dataDirectory));
+                      await tor.start();
                       print('done awaiting');
                     },
                     child: const Text("start tor")),
@@ -140,7 +139,7 @@ class _MyAppState extends State<MyApp> {
                         // Assign connection factory
                         SocksTCPClient.assignToHttpClient(client, [
                           ProxySettings(InternetAddress.loopbackIPv4,
-                              int.parse(portController.text),
+                              Tor().port,
                               password: passwordController.text),
                         ]);

There is probably more than that to adjust but this gives me an IP different than mine when I make the request in the example GUI.

Right you are!  Sorry about that.
I formatted https://github.com/Foundation-Devices/tor/pull/6 to minimize changes; the package and plugin are still named simply tor


Validation with process-exclusive devices

Most GPUs on our servers are process-exclusive. If I specify a process-exclusive GPU as a sockeye --device for training, the validation step throws an error:
cudaMalloc failed: all CUDA-capable devices are busy or unavailable

Presumably because I have specified a single device to be aquired and it's in Exclusive Mode.
With Nematus, I usually use a different device for the validation process. With sockeye, as far as I can see, I cannot specify a device that would only be used for the purpose of validation, is that correct?
Do you have a recommendation to deal with this? Thanks!

that is a good point, we should add arguments for this (or even allow CPU validation decoding if necessary). Probably named similar to --monitor-bleu to make clear that they are related.

A separate option for this would make sense yes. In the meantime, I have a related question:
If I specify several devices, which of them will be used for the validation process? The first one? Arbitrary choice?

It will use the last device in the context list (see here: https://github.com/awslabs/sockeye/blob/master/sockeye/training.py#L254). Which device is the last may depend on the order in which GPUs were acquired, so this is effectively arbitrary; we should have more control over this.

huh, I didn't know a CUDA device could be restricted to a single process. The validation runs in a separate background process. I guess it would make sense to give the option to specify a separate GPU (or run validation on the GPU). In the mean time you could turn off --monitor-bleu, as without that option there are no background processes.

I created a PR that would allow you to use the CPU for decoding or any other (separate) GPU device (which might also be useful in cases where memory is sparse on the GPU).

#228 was merged, closing this issue. Feel free to reopen if your issue persists.


Spanish Translation

Hello guru @QingWei-Li  🥇
I'd like to translate docsify in Spanish, what do you think?
My experience with translations to Spanish are:

Discourse through Transifex
AmpProject

It's going to take time, but I wanted to know if you agree before starting the translation.
PD: si alguien habla español, y se quiere sumar, responde aquí y me menciona., o envía un PR para modificar aquí y todos felices 😃

Thanks SidV,
But I afraid that this will be trouble in the feature. If I want to and new
features I need synchronous multiple documents.
I think you can create a new repo for Spanish, I can be add a link in the
website.
SidV<EMAIL_ADDRESS>于 2018年5月14日周一 21:08写道：

Hello guru @QingWei-Li https://github.com/QingWei-Li 🥇
I'd like to translate docsify in Spanish, what do you think?
My experience with translations to Spanish are:

Discourse https://github.com/discourse/discourse through Transifex
https://www.transifex.com/discourse/teams/19424/es/
AmpProject https://github.com/ampproject/docs/

It's going to take time, but I wanted to know if you agree before you
start.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/QingWei-Li/docsify/issues/484, or mute the thread
https://github.com/notifications/unsubscribe-auth/AHNxfH-5UuD3G-chZHPvBowpnZZpPjnmks5tyYHBgaJpZM4T9wpW
.

--
Cinwell Li
https://cinwell.com

First look good.
If you finished, please submit a PR to add the document link.
Thanks!

please submit a PR to add the document link.

I can not understand how do you add the content from the new repo?
https://sidval.github.io/docsify-es/

I mean you can add a link in there https://github.com/QingWei-Li/docsify/blob/master/docs/_navbar.md


Add Zodiac App

Name/Description
Zodiac
Type
New addition
Compatible Networks

Mainnet
Rinkeby

Code for review

https://github.com/gnosis/zodiac-safe-app
IPFS hash/App URL

https://gnosis-zodiac-app.netlify.app
Desired date
ASAP

👌  added, excited to have you!


⚠ Processors has degraded performance

In a13aa6c, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 43 ms

Resolved: Processors performance has improved in d618139.


Expression Transfer

Is it possible to transfer the expressions from a source to a target actor while keeping the pose and identity in-tact?

via 3DMM approach it's possible. You can change expression params and keep the pose and identity params. Please see network.py for SynergyNet parameter definition


v0.2.2

v0.2.2 April 13, 2020

Enhancements

Added New Primitives (#52)

Testing Changes

Refactored Unit Tests (#48)
Added Code Coverage Requirement (#48)

Instead of "Added New Primitives" can we say which primitives were added?


How is font/text dynamically resized

Where in the code is font/text dynamically resized?
In the code below from app/scripts/studio/forms/ImageField.js
the ctx.font , the font size is ${textHeight}px/${size.h}px , but both of these are fixed values, so should not change based number of characters.
case 'text':
          var size = { w: 6144, h: 1536 };
          var textHeight = size.h * 0.75;
          var ctx = imagelib.Drawing.context(size);
          var text = this.textParams_.text || '';
          text = ' ' + text + ' ';

          ctx.fillStyle = '#000';
          ctx.font = `bold ${textHeight}px/${size.h}px ${this.textParams_.fontStack}`;
          ctx.textBaseline = 'alphabetic';
          ctx.fillText(text, 0, textHeight);
          size.w = Math.ceil(Math.min(ctx.measureText(text).width, size.w) || size.w);

          resolve({ctx, size});
          break;

The text is first rendered to an offscreen buffer by ImageField, and the each generator (e.g. the launcher icon generator) calls drawCenterInside or drawCenterCrop to fit the rendered text into the desired space.


As a user, I want to delete a card

so that I can remove flashcards that I no longer need.

Resolved by #21 and #36


2.0.0版本安装好像不兼容

Fatal error: Declaration of Hyperf\Crontab\Process\CrontabDispatcherProcess::isEnable($server): bool must be compatible with Hyperf\Process\AbstractProcess::isEnable(): bool in /hyperf/vendor/hyperf/crontab/src/Process/CrontabDispatcherProcess.php on line 23

composer info | grep hyperf

2.0.0 就有这个问题， 我换成1.1.26就好了。
完整composer info
hyperf/cache                         v1.1.22  A cache component for hyperf.
hyperf/command                       v1.1.21  Command for hyperf
hyperf/config                        v1.1.22  An independent component that provides configuration container.
hyperf/constants                     v1.1.22  A constants component for hyperf.
hyperf/contract                      v1.1.22  The contracts of Hyperf.
hyperf/crontab                       v1.1.26  A crontab component for Hyperf.
hyperf/database                      v1.1.22  A flexible database library.
hyperf/db-connection                 v1.1.22  A hyperf db connection handler for hyperf/database.
hyperf/devtool                       v1.1.22  A Devtool for Hyperf.
hyperf/di                            v1.1.22  A DI for Hyperf.
hyperf/dispatcher                    v1.1.22  A HTTP Server for Hyperf.
hyperf/event                         v1.1.22  an event manager that implements PSR-14.
hyperf/exception-handler             v1.1.6   Exception handler for hyperf
hyperf/framework                     v1.1.22  A coroutine framework that focuses on hyperspeed and flexible, specifically use for build microservices and middlewares.
hyperf/guzzle                        v1.1.23  Swoole coroutine handler for guzzle
hyperf/http-message                  v1.1.22  microservice framework base on swoole
hyperf/http-server                   v1.1.22  A HTTP Server for Hyperf.
hyperf/json-rpc                      v1.1.30  A JSON RPC component for Hyperf RPC Server or Client.
hyperf/load-balancer                 v1.1.22  A load balancer library for Hyperf.
hyperf/logger                        v1.1.22  A logger component for hyperf.
hyperf/memory                        v1.1.22  An independent component that use to operate and manage memory.
hyperf/model-cache                   v1.1.22  A model cache component for hyperf.
hyperf/model-listener                v1.1.22  A model listener for Hyperf.
hyperf/paginator                     v1.1.22  A paginator component for hyperf.
hyperf/pool                          v1.1.23  An independent universal connection pool component.
hyperf/process                       v1.1.22  A process component for hyperf.
hyperf/redis                         v1.1.22  A redis component for hyperf.
hyperf/rpc                           v1.1.22  A rpc basic library for Hyperf.
hyperf/rpc-client                    v1.1.23  An abstract rpc server component for Hyperf.
hyperf/rpc-server                    v1.1.26  An abstract rpc server component for Hyperf.
hyperf/server                        v1.1.22  A base server library for Hyperf.
hyperf/snowflake                     v1.1.22  A snowflake library
hyperf/testing                       v1.1.23  Testing for hyperf
hyperf/translation                   v1.1.17  An independent translation component, forked by illuminate/translation.
hyperf/utils                         v1.1.22  A tools package that could help developer solved the problem quickly.
hyperf/validation                    v1.1.22  hyperf validation

贴一下你换成2.0的composer info

我这里也是这种情况：
96qbhy/hyperf-auth                   v1.6.1      hyperf 的 auth 组件
hyperf/amqp                          v1.1.32     A amqplib for hyperf.
hyperf/async-queue                   v1.1.26     A async queue component for hyperf.
hyperf/cache                         v1.1.30     A cache component for hyperf.
hyperf/command                       v1.1.32     Command for hyperf
hyperf/config                        v1.1.26     An independent component that provides configuration container.
hyperf/constants                     v1.1.26     A constants component for hyperf.
hyperf/consul                        v1.1.26     A Consul Client for Hyperf.
hyperf/contract                      v1.1.32     The contracts of Hyperf.
hyperf/crontab                       v2.0.0      A crontab component for Hyperf.
hyperf/database                      v1.1.32     A flexible database library.
hyperf/db-connection                 v1.1.26     A hyperf db connection handler for hyperf/database.
hyperf/devtool                       v1.1.31     A Devtool for Hyperf.
hyperf/di                            v1.1.28     A DI for Hyperf.
hyperf/dispatcher                    v1.1.26     A HTTP Server for Hyperf.
hyperf/event                         v1.1.26     an event manager that implements PSR-14.
hyperf/exception-handler             v1.1.31     Exception handler for hyperf
hyperf/framework                     v1.1.27     A coroutine framework that focuses on hyperspeed and flexible, specifically use for ...
hyperf/guzzle                        v1.1.26     Swoole coroutine handler for guzzle
hyperf/http-message                  v1.1.26     microservice framework base on swoole
hyperf/http-server                   v1.1.29     A HTTP Server for Hyperf.
hyperf/json-rpc                      v1.1.30     A JSON RPC component for Hyperf RPC Server or Client.
hyperf/load-balancer                 v1.1.26     A load balancer library for Hyperf.
hyperf/logger                        v1.1.26     A logger component for hyperf.
hyperf/memory                        v1.1.26     An independent component that use to operate and manage memory.
hyperf/model-cache                   v1.1.28     A model cache component for hyperf.
hyperf/model-listener                v1.1.26     A model listener for Hyperf.
hyperf/paginator                     v1.1.26     A paginator component for hyperf.
hyperf/pool                          v1.1.32     An independent universal connection pool component.
hyperf/process                       v1.1.26     A process component for hyperf.
hyperf/redis                         v1.1.26     A redis component for hyperf.
hyperf/rpc                           v1.1.26     A rpc basic library for Hyperf.
hyperf/rpc-client                    v1.1.28     An abstract rpc server component for Hyperf.
hyperf/rpc-server                    v1.1.26     An abstract rpc server component for Hyperf.
hyperf/server                        v1.1.32     A base server library for Hyperf.
hyperf/service-governance            v1.1.28     A service governance component for Hyperf.
hyperf/testing                       v1.1.28     Testing for hyperf
hyperf/tracer                        v1.1.26     A open tracing system implemented for Hyperf or other coroutine framework
hyperf/utils                         v1.1.31     A tools package that could help developer solved the problem quickly.

我这里也是这种情况：
96qbhy/hyperf-auth v1.6.1 hyperf 的 auth 组件
hyperf/amqp v1.1.32 A amqplib for hyperf.
hyperf/async-queue v1.1.26 A async queue component for hyperf.
hyperf/cache v1.1.30 A cache component for hyperf.
hyperf/command v1.1.32 Command for hyperf
hyperf/config v1.1.26 An independent component that provides configuration container.
hyperf/constants v1.1.26 A constants component for hyperf.
hyperf/consul v1.1.26 A Consul Client for Hyperf.
hyperf/contract v1.1.32 The contracts of Hyperf.
hyperf/crontab v2.0.0 A crontab component for Hyperf.
hyperf/database v1.1.32 A flexible database library.
hyperf/db-connection v1.1.26 A hyperf db connection handler for hyperf/database.
hyperf/devtool v1.1.31 A Devtool for Hyperf.
hyperf/di v1.1.28 A DI for Hyperf.
hyperf/dispatcher v1.1.26 A HTTP Server for Hyperf.
hyperf/event v1.1.26 an event manager that implements PSR-14.
hyperf/exception-handler v1.1.31 Exception handler for hyperf
hyperf/framework v1.1.27 A coroutine framework that focuses on hyperspeed and flexible, specifically use for ...
hyperf/guzzle v1.1.26 Swoole coroutine handler for guzzle
hyperf/http-message v1.1.26 microservice framework base on swoole
hyperf/http-server v1.1.29 A HTTP Server for Hyperf.
hyperf/json-rpc v1.1.30 A JSON RPC component for Hyperf RPC Server or Client.
hyperf/load-balancer v1.1.26 A load balancer library for Hyperf.
hyperf/logger v1.1.26 A logger component for hyperf.
hyperf/memory v1.1.26 An independent component that use to operate and manage memory.
hyperf/model-cache v1.1.28 A model cache component for hyperf.
hyperf/model-listener v1.1.26 A model listener for Hyperf.
hyperf/paginator v1.1.26 A paginator component for hyperf.
hyperf/pool v1.1.32 An independent universal connection pool component.
hyperf/process v1.1.26 A process component for hyperf.
hyperf/redis v1.1.26 A redis component for hyperf.
hyperf/rpc v1.1.26 A rpc basic library for Hyperf.
hyperf/rpc-client v1.1.28 An abstract rpc server component for Hyperf.
hyperf/rpc-server v1.1.26 An abstract rpc server component for Hyperf.
hyperf/server v1.1.32 A base server library for Hyperf.
hyperf/service-governance v1.1.28 A service governance component for Hyperf.
hyperf/testing v1.1.28 Testing for hyperf
hyperf/tracer v1.1.26 A open tracing system implemented for Hyperf or other coroutine framework
hyperf/utils v1.1.31 A tools package that could help developer solved the problem quickly.

执行安装低版本 试试
composer require hyperf/crontab:1.1.26

安装1.1版本🉐组件


Add offset and length argument to pycurl absorb and squeeze

Currently, pycurl absorb and squeeze only have trits argument, but pykerl have offset and length.
Although pycurl is a deprecated hash function, but in IRI snapshot, it used CURLP81 to sign the snapshot, so if we want to verify snapshot signature, we will need offset and length argument to used absorb and squeeze.

Hey @mlouielu thanks for reporting this!
Looks fairly straightforward to implement this; I'm going to tag this issue with help wanted.