text:
add jpeg quality option

Description of changes:
Adds option for JPEG quality.
Issue #, if available:

Fixes #811

Merge Checklist:
Put an x without space in the boxes that apply. If you are unsure about any checklist, please don't hesitate to ask. We are here to help! This is simply a reminder of what we are going to look for before merging your pull request.
General

[ ] I have read the contributor guidelines
[ ] This is a documentation change or typo fix. If so, skip the rest of this checklist.
[ ] I certify that the changes I am introducing will be backward compatible, and I have discussed concerns about this, if any, with the MosaicML team.
[ ] I have updated any necessary documentation, including README and API docs (if appropriate).

Tests

[ ] I ran pre-commit on my change. (check out the pre-commit section of prerequisites)
[ ] I have added tests that prove my fix is effective or that my feature works (if appropriate).
[ ] I ran the tests locally to make sure it pass. (check out testing)
[ ] I have added unit and/or integration tests as appropriate to ensure backward compatibility of the changes.

Hey @cabreraalex , thanks for creating a PR. One minor comment, can you please update your PR with the changes that are not relevant to this PR? Seems like there are some spacing changes, single/double quotes changes, etc.

oops yup, done

@cabreraalex Mind addressing the review comments when you have some time? Thanks!

AFAI can tell just the config is passed, e.g. from jpeg:12 only the 12 is passed to from_str: https://github.com/mosaicml/streaming/blob/45c2132fbd3e0621c403496b51b5b56e1c174a22/streaming/base/format/mds/encodings.py#L591
There is no formal type for the quality, just integer

repo: mosaicml/streaming


text:
Add combination rule as a force field property

Describe the behavior you would like added to Foyer
Mixing rules are important properties of force fields. Foyer should encode them as such in the Forcefield object model, much like 1-4 scaling factors (https://github.com/mosdef-hub/foyer/issues/397). Not doing so adds ambiguity around the intended scope of data in a force field and also leads to to issues like https://github.com/mosdef-hub/foyer/issues/431 and issues grad students (me) using the wrong mixing rules for years.
Part of the implementation (telling ParmEd which rule to use) and a TODO are in the codebase already. Just setting structure.combining_rule is not sufficient, however, as evidenced by #431, because of how 1-4 scaling factors are passed from OpenMM to ParmEd.
Describe the solution you'd like
Given the complexity with storing a non-Lorentz-Berthelot mixing rule in an openmm.System, the simplest approach might be to store the mixing rule as a high-level property. Then, if the mixing rule is set to geometric, apply at patch onto the ParmEd object before it's ultimately returned by Forcefield.apply().
Describe alternatives you've considered
Downstream developers and users could apply a fix that tidies things up, but IMHO this should really be done by foyer and it does not address the original issue of a force field not knowing its combing rule.
Additional context
I use "combination rule," "mixing rule", "combining rule," and possibly other terms interchangeably. This is a bad habit of mine but I think it comes from different people and fields not agreeing on a term, so it's probably not going to be fixed anytime soon.

Currently satisfied by #433 . Closing for now.

source: gharchive/issue

authors: justinGilmer mattwthompson

repo: mosdef-hub/foyer

license: mit

license_type: permissive

license_source: bigquery


text:
Upgrade wasmer-go to 1.0.4

Upgrade wasmer-go to 1.0.4, which upgrade the wasmer runtime to 2.0.0 to support Apple Silicon chip.
Fix issue #216

Codecov Report

Merging #217 (75b01b0) into main (288df7b) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 75b01b0 differs from pull request most recent head 13d66a8. Consider uploading reports for the commit 13d66a8 to get more accurate results

@@           Coverage Diff           @@
##             main     #217   +/-   ##
=======================================
  Coverage   56.73%   56.73%
=======================================
  Files          51       51
  Lines        2316     2316
=======================================
  Hits         1314     1314
  Misses        872      872
  Partials      130      130

Continue to review full report at Codecov.

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

source: gharchive/pull-request

authors: codecov-commenter khotyn

repo: mosn/layotto

license_source: github-api


text:
feat: layotto support s3

What this PR does:
Which issue(s) this PR fixes:

Fixes https://github.com/mosn/layotto/issues/510
Special notes for your reviewer:
对于支持S3的原因可以参考 #510
鉴于本次改动过大，文档单独提pr更新
s3接口设计
首先是对于s3 grpc接口的定义，在spec/proto下新增extension/v1/s3.proto作为接口的定义，然后将S3协议的接口翻译成pb定义，入参和返回值保持和s3现有的定义相同：

s3能力加载框架
首先通过Layotto的GrpcAPI接口进行S3服务的拓展，S3Server实现了GrpcAPI接口以及上述定义的grpc s3 service：

然后在main函数中加载NewS3Server作为自定义拓展的grpc api：

本次设计在配置方面复用file当前的配置，但新建OssFactory用于oss能力的开启，区分file和oss的功能：

s3能力component接口定义

这里主要讲述一下InitClient，InitConfig两个函数，其它函数都是对s3的pb定义的实现。不做赘述。
InitConfig：主要为了获取配置文件中的配置信息，和file的Init接口是对应的。
InitClient： 用户初始化操作。
对于InitClient来说，每个用户的初始化方式可能都是不同的，比如开源的client初始化可以获取配置文件中的ak、sk直接进行初始化操作，但有的用户需要根据InitClient传递过来的数据动态的获取ak,sk。因此，这里需要把初始化函数设计成可配置的。用户可以自定义自己的初始化函数实现。如下所示：

对于入参来说，分为两部分，第一部分staticConf代表的是InitConfig获取到的静态配置文件中的数据。第二部分的dynConf则是应用测通过InitClient传递过来的动态数据。目前看来，layotto主要包含这两种配置文件，具体的client初始化，用户可以根据自定义的函数来进行。
对于返回值来说，map[string]interface{}是属于uid:ossClient的映射关系，因为可能存在多个ossClient，这时候用户可以自定义映射关系。
因此在file的配置中，用户需要指定init函数的名字，如下图所示：

Does this PR introduce a user-facing change?:

@LXPWing @kevinten10 Hi, could u help review this PR?
We can use this new api to implement the demo project #647

Review process:

[ ] demo review. Prove that this design can help app run on alicloud and aws s3
[ ] API design review
[ ] core code review
[ ] code detail review

action:

[ ] @kevinten10 帮忙 review 下

卡点
这个PR 很难 review，倒不是因为大，毕竟之前更大的 PR 也挺多的, 比如 https://github.com/mosn/layotto/pull/549 ；
而且我相信，即使这个 PR 只提交了 proto 文件，也依然很难 review……
因为：

看不懂这些 API 是啥意思
没有解释，proto 的接口上也没有注释说明，我尝试去搜 S3 文档，但是有些接口搜不到 :(
新增 API 最好有个设计说明，解释调研结果、每个 API 的含义、为什么要这么设计，例如 https://github.com/dapr/dapr/issues/2988  或者 https://github.com/dapr/dapr/issues/4576

既然 reviewer 看不懂，合并之后该 API 的开源用户可能也看不懂

其他一些小问题：

reviewer 没法把 PR 跑起来，不好判断“这个feature 自测通过、能正常运行”

解释：通过“提交自测通过的截图” 来“证明我自测通过了” 只适合在公司里协作，比如把截图发给测试同事，证明“我自测通过了，后面的事情交给你了”。在公司里可以这么做，是因为测试同事总归要自己测一遍，“反正有测试同学来帮我写自动化测试、帮我兜底”。
但是开源项目没有人专职当 QA，想要保证稳定性，reviewer 就不仅要简单 review 一下代码，还要保证 merge进去的 feature 是自测通过的（不一定 bug free，但起码能跑通流程），某种程度上兼职了 QA；
但是 reviewer 又没法像公司里QA 人员一样帮你写测试，所以一般是把代码拉到本地、运行试试（其实很多 PR 运行就会报错），或者在 PR 里把 demo 加进 CI，让 CI 跑 demo，证明“自测通过”, 比如 https://github.com/mosn/layotto/pull/574
后者更好，因为是自动化的
这个问题的解决方案:

在 CI 中自动运行 demo，ak/sk 等敏感信息可以读 repo 中的 secret 配置。这样既能证明自测通过，又方便以后自动化测试。

again, 不是在要求大家“写 PR 时还得写复杂的集成测试”，而是“有个简单的demo，让 reviewer和用户能跑通流程，能证明自测通过就行”

白嫖测试资源：如果这功能有生产用户等着用，那交给生产用户的 QA 人员做测试也行

因为1、3，reviewer 没法判断“这个 API 具有可移植性”

解决方案
anyway, 既然要推进这个 PR，我想到的解决方案:

设计一种 API version 机制，比如版本号包括:

sandbox
alpha
beta
正式版
非正式版不保证兼容性、不保证生产稳定; sandbox 版本甚至不保证有文档，alpha 版本再保证有文档（比如 dapr 的alpha功能，文档很全）。
这个 PR 作为 sandbox 版本合并进去，等试用用户、QA 给出反馈后再改。

有一定的隔离机制，保证 sandbox 版本的 feature 不影响其他功能。有几种方案:
方案 a. 把sandbox 功能挪进单独仓库，比如 https://github.com/dapr-sandbox
方案 b. 把 sandbox 功能单独挪到一个目录下，比如把这个PR 的代码挪到 /plugins/api/v1/sandbox/oss下

有了 1、2 后，可以直接合并，不 review 了

卡点
这个PR 很难 review，倒不是因为大，毕竟之前更大的 PR 也挺多的, 比如 #549 ； 而且我相信，即使这个 PR 只提交了 proto 文件，也依然很难 review……
因为：

看不懂这些 API 是啥意思
没有解释，proto 的接口上也没有注释说明，我尝试去搜 S3 文档，但是有些接口搜不到 :(
新增 API 最好有个设计说明，解释调研结果、每个 API 的含义、为什么要这么设计，例如 [Proposal] configuration api design dapr/dapr#2988  或者 [Proposal] Workflow building block and engine dapr/dapr#4576
既然 reviewer 看不懂，合并之后该 API 的开源用户可能也看不懂

其他一些小问题：

reviewer 没法把 PR 跑起来，不好判断“这个feature 自测通过、能正常运行”

解释：通过“提交自测通过的截图” 来“证明我自测通过了” 只适合在公司里协作，比如把截图发给测试同事，证明“我自测通过了，后面的事情交给你了”。在公司里可以这么做，是因为测试同事总归要自己测一遍，“反正有测试同学来帮我写自动化测试、帮我兜底”。
但是开源项目没有人专职当 QA，想要保证稳定性，reviewer 就不仅要简单 review 一下代码，还要保证 merge进去的 feature 是自测通过的（不一定 bug free，但起码能跑通流程），某种程度上兼职了 QA； 但是 reviewer 又没法像公司里QA 人员一样帮你写测试，所以一般是把代码拉到本地、运行试试（其实很多 PR 运行就会报错），或者在 PR 里把 demo 加进 CI，让 CI 跑 demo，证明“自测通过”, 比如 #574 后者更好，因为是自动化的
这个问题的解决方案:

在 CI 中自动运行 demo，ak/sk 等敏感信息可以读 repo 中的 secret 配置。这样既能证明自测通过，又方便以后自动化测试。

again, 不是在要求大家“写 PR 时还得写复杂的集成测试”，而是“有个简单的demo，让 reviewer和用户能跑通流程，能证明自测通过就行”

白嫖测试资源：如果这功能有生产用户等着用，那交给生产用户的 QA 人员做测试也行

因为1、3，reviewer 没法判断“这个 API 具有可移植性”

解决方案
anyway, 既然要尽快推进这个 PR，我想到的解决方案:

设计一种 API version 机制，比如 API 版本号包括:

sandbox
alpha
beta
正式版
非正式版不保证兼容性、不保证生产稳定;
sandbox 版本甚至不保证有文档，alpha 版本再保证有文档（比如 dapr 的alpha功能，文档很全）。
这个 PR 作为 sandbox 版本合并进去，等试用用户、QA 给出反馈后再改。

有一定的隔离机制，保证 sandbox 版本的 feature 不影响其他功能。有几种方案:
方案 a. 把sandbox 功能挪进单独仓库，比如 https://github.com/dapr-sandbox
方案 b. 把 sandbox 功能单独挪到一个目录下，比如把这个PR 的代码挪到 /plugins/api/v1/sandbox/oss下
有了 1、2 后，可以直接合并，不 review 了

声明：
1.该套api不是s3的抄录，是结合了阿里云和s3共同指定的，可以理解为并集api，对于不支持的接口会返回相应的error。

2.该套api定义过程中，除了保证可移植性还保证了语义特征，比如IsObjectExist，aws里面并没有该接口，但可以通过headobject等形式实现，aliyun中有该接口。
提到的两个问题：

pb里面的接口定义加注释和设计原则，这个可以写文档，不是什么困难。作为reviewer可以提出你需要的参考。
reviewer看不懂，开源用户看不懂。这个其实本身并不成立，作为oss用户，接口的语义甚至都够了，当然对于并不了解oss的人来说，的确存在困难，所以1的需求是可以提出来的。eg. 用户在不需要任何支持的条件下，直接完成了迁移。
api version机制，这个没什么意见，在生产验证前所有的接口的可行性都是存疑的，包括dapr那套所谓的标准api。
各种版本保证稳定，这feature本身就是个独立的feature，本身不会影响到其它能力，为什么要进行所谓的feature隔离。
另外说到的测试问题，ak、sk在有了之后再说吧。

总结：

作为提pr的contributor，接口的定义和设计考量要加上。作为文档输出，用来做参考。
reviewer要让对应的领域的人来review，每个开源项目都有多个commiter，要区分出每个人专业的领域来负责review，这会大大提高review的质量以及降低reviewer的负担。不了解oss的reviewer也可以通过1的详细的文档来了解。
layotto的api不光新加的api，所有的api都应该有自己的sandbox，alpha.....，而不是follow dapr的。
对于feature隔离，个人感觉完全没必要，主链路的改动可以走这种模式，新的feature并不会产生主链路的影响，个人认为不需要进行隔离。

@seeflood @zhenjunMa @kevinten10 please help review the pr

For you guys who are not familiar with oss (like me), I did some research on object storage and wrote some articles:
调研各个云厂商的对象存储服务
why Object Storage
Hope they can help you review

@wenxuwan Looks good to me overall. Please fix the CI failure.
Thanks!

authors: seeflood wenxuwan


text:
🛑 api.buymezobo is down

In d6ca772, api.buymezobo (https://core.buymezobo.ng/api/healthcheck) was down:

HTTP code: 0
Response time: 0 ms

Resolved: api.buymezobo is back up in 44493c4 after 11 minutes.

repo: mossgrid/sentinel

license: MIT


text:
Integration of evaluation and experiment results

Make sure that the evaluation metrics are computed for the itembased predictions (the same like userbased predictions)
Make sure the splitting (if needed) and grid search are also working with itembased predictions.
In the runnables experiment, we calculate the best hyperparameters first (already done by grid search); then override it for each run configuration before initalizing the recommender. (The recommender can take config dictionary optionally instead of using the JSON folder)
Good prints for the experiment results so it's the easiest to present later on.

Making use of the AbstractRecommender for common functionalities would be a good idea.

repo: mostafa-mahmoud/sahwaka


text:
Docker Desktopユーザー向けの注釈を追加した

変更の内容
コンテナからホスト側のアプリへアクセスする場面に Docker Desktop 環境向けの注釈を追加した．

4節: 初めてのコントローラ

redis-cli で redis へアクセスするとき

7節: Volumes

MySQL Client でデータベースに接続するとき

変更の理由
Docker Desktop を使用した環境では，--network host を付けたとしても，localhost がコンテナ自身を参照してしまうようです．localhost の代わりに host.docker.internal を指定することで，コンテナ内からホスト側へリクエストを送信できました．
Explore networking features on Docker Desktop
今後，同じ問題に直面した方の助けになればと思い，注釈を追加しました．

読んでくださりありがとうございます。
Linux限定のオプションだったのですね。
ただ、ここではクライアント系のcliを使いたいだけなので、別にコンテナをつかなくても良いんですけどね...
私はすぐには試せないのですが、有効化するオプションがあるみたいなのですが、これで動いたりしますでしょうか？
https://docs.docker.com/engine/network/drivers/host/#docker-desktop
https://docs.docker.com/engine/network/tutorials/host/#prerequisites
これで動く場合は準備の章に追記しても良いかもしれません（betaですが）。

教えていただいた方法で host networking を有効化すると，localhost でもアクセスできました．
host networiking は 4.34.0から一般公開されたようなので，4.34.0以上をお使いの方に向けた案内を準備の章に追加しました．
https://docs.docker.com/desktop/release-notes/#4340


text:
Explain what this code does in ReadMe

The project description at the top sounds interesting, but how does it work?
A few lines describing the product, how it works and what the benefit of using it at the top of  readme.md would help. It would be good to have an example and a few screenshots.

@rimutaka I have updated the readme, lmk what you think. 10x

Jamal, it's getting there.
Moufette is an open-soruce [????], built for developers. - an open source what? An app? A library? What does it do exactly?
You need to reduce it to a very simple definition that speaks to your target user.
Here is a made-up example:
MF is an embedable JS widget with such and such back-end to collect user feedback with screenshots. Make it easeir for your users to help you build a better app.
A few screenshots of what the UI may look like will help.
Then you can go into all the technical details on how to install and use it.

@rimutaka thank you so much. really appreciate the feedback.
I've updated the description and added screenshots.

Nice :) I'd drop the badger illustration and add a sample embed snippet.
Ping me when you add more contents for another round of reviews. I'm interested to see how your docs progress.

repo: moufette-tools/moufette


text:
#19-Python

Reverts mouredev/roadmap-retos-programacion#4242

Hola,
Cerramos PR por inactividad. Puedes enviar una nueva cuando quieras. Recuerda revisar reglas y comentarios.
Muchas gracias.

authors: gringoam kontroldev

repo: mouredev/roadmap-retos-programacion


text:
Getting Started Errors Ubuntu 24.04

Description
Failing to get through the build step of the moveit2 tutorial https://moveit.picknik.ai/main/doc/tutorials/getting_started/getting_started.html#install-ros-2-and-colcon
Your environment

ROS Distro: Jazzy
OS Version: Ubuntu 24.04
Source or Binary build? Source, from tutorial
If binary, which release version?
If source, which git commit or tag?
Moveit2: 1d93035fc4fbc2831916bce26d7b03e15b8a86d5
Tutorials: b05445aa9dfe41916e34468a9f14b4058ce868bf

Steps to reproduce
I'm just following along the tutorial here https://moveit.picknik.ai/main/doc/tutorials/getting_started/getting_started.html#install-ros-2-and-colcon
When I try to colcon build --mixin release, I first get errors about catkin_pkg not being found to import. After pip installing catkin pip install catkin_pkg (seems like it shouldn't be needed anymore) I get a different error with moveit_msgs
I attached my notes stepping thru each step as markdown using warp terminal.
Expected behaviour
The build should complete successfully. I do recognize I'm on Ubuntu 24.04 and using the latest Ros2 build but it seems worth logging as an issue for those targets. I'll attempt to work around this by using a docker container to work with move it.
MoveIt Getting Started.md
Backtrace or Console output
colcon build --mixin release
Starting >>> moveit_resources_panda_description
Starting >>> moveit_common
Starting >>> moveit_msgs
Starting >>> moveit_resources_pr2_description
Starting >>> moveit_configs_utils
Starting >>> moveit_resources_fanuc_description
Starting >>> moveit_resources_prbt_support
Starting >>> gz_ros2_control
Starting >>> robotiq_description
Starting >>> kortex_api
Starting >>> rviz_visual_tools
Starting >>> serial
Starting >>> robotiq_controllers
Finished <<< moveit_common [0.29s]
Finished <<< moveit_resources_panda_description [0.30s]
Finished <<< robotiq_description [0.29s]
Starting >>> rviz_marker_tools
Finished <<< moveit_resources_pr2_description [0.30s]
Starting >>> moveit_resources_panda_moveit_config
Starting >>> dual_arm_panda_moveit_config
Finished <<< kortex_api [0.31s]
Starting >>> kortex_driver
Finished <<< moveit_resources_prbt_support [0.33s]
Finished <<< moveit_resources_fanuc_description [0.34s]
Starting >>> moveit_resources_fanuc_moveit_config
Finished <<< serial [0.35s]
Starting >>> robotiq_driver
Finished <<< robotiq_controllers [0.37s]
Finished <<< moveit_resources_panda_moveit_config [0.13s]
Finished <<< dual_arm_panda_moveit_config [0.14s]
Finished <<< moveit_resources_fanuc_moveit_config [0.12s]
Finished <<< rviz_marker_tools [0.17s]
Starting >>> moveit_resources
Finished <<< kortex_driver [0.16s]
--- stderr: moveit_msgs
CMake Error at /opt/ros/jazzy/share/rosidl_adapter/cmake/rosidl_adapt_interfaces.cmake:57 (message):
  execute_process(/home/michael-mentele/miniconda/bin/python3 -m
  rosidl_adapter --package-name moveit_msgs --arguments-file
  /home/michael-mentele/Desktop/trossen-pincher-hello-world/moveit-tutorial-integration-with-robot/build/moveit_msgs/rosidl_adapter__arguments__moveit_msgs.json
  --output-dir
  /home/michael-mentele/Desktop/trossen-pincher-hello-world/moveit-tutorial-integration-with-robot/build/moveit_msgs/rosidl_adapter/moveit_msgs
  --output-file
  /home/michael-mentele/Desktop/trossen-pincher-hello-world/moveit-tutorial-integration-with-robot/build/moveit_msgs/rosidl_adapter/moveit_msgs.idls)
  returned error code 1:

  AttributeError processing template 'msg.idl.em'

  Traceback (most recent call last):

    File "/opt/ros/jazzy/lib/python3.12/site-packages/rosidl_adapter/resource/__init__.py", line 48, in evaluate_template
      _interpreter = em.Interpreter(
                     ^^^^^^^^^^^^^^

  AttributeError: module 'em' has no attribute 'Interpreter'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):

    File "<frozen runpy>", line 198, in _run_module_as_main
    File "<frozen runpy>", line 88, in _run_code
    File "/opt/ros/jazzy/lib/python3.12/site-packages/rosidl_adapter/__main__.py", line 19, in <module>
      sys.exit(main())
               ^^^^^^
    File "/opt/ros/jazzy/lib/python3.12/site-packages/rosidl_adapter/main.py", line 53, in main
      abs_idl_file = convert_to_idl(
                     ^^^^^^^^^^^^^^^
    File "/opt/ros/jazzy/lib/python3.12/site-packages/rosidl_adapter/__init__.py", line 19, in convert_to_idl
      return convert_msg_to_idl(
             ^^^^^^^^^^^^^^^^^^^
    File "/opt/ros/jazzy/lib/python3.12/site-packages/rosidl_adapter/msg/__init__.py", line 39, in convert_msg_to_idl
      expand_template('msg.idl.em', data, output_file, encoding='iso-8859-1')
    File "/opt/ros/jazzy/lib/python3.12/site-packages/rosidl_adapter/resource/__init__.py", line 23, in expand_template
      content = evaluate_template(template_name, data)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/opt/ros/jazzy/lib/python3.12/site-packages/rosidl_adapter/resource/__init__.py", line 69, in evaluate_template
      _interpreter.shutdown()
      ^^^^^^^^^^^^^^^^^^^^^

  AttributeError: 'NoneType' object has no attribute 'shutdown'

Call Stack (most recent call first):
  /opt/ros/jazzy/share/rosidl_cmake/cmake/rosidl_generate_interfaces.cmake:132 (rosidl_adapt_interfaces)
  CMakeLists.txt:117 (rosidl_generate_interfaces)

---
Failed   <<< moveit_msgs [0.50s, exited with code 1]
Aborted  <<< rviz_visual_tools [0.49s]
Aborted  <<< robotiq_driver [0.14s]
Aborted  <<< moveit_configs_utils [0.58s]
Aborted  <<< gz_ros2_control [0.71s]
Aborted  <<< moveit_resources [0.41s]

Summary: 14 packages finished [1.08s]
  1 package failed: moveit_msgs
  5 packages aborted: gz_ros2_control moveit_configs_utils moveit_resources robotiq_driver rviz_visual_tools
  2 packages had stderr output: gz_ros2_control moveit_msgs
  52 packages not processed

Use gist.github.com to copy-paste the console output or segfault backtrace using gdb.

This is an issue with the Python packages configured locally on your end -- see e.g. here: https://github.com/ros/genmsg/issues/63
Given you're on Ubuntu 24.04, and if you don't want to use a virtual environment to do pip installs, you could consider trying sudo apt install ros-dev-tools as shown here:
https://github.com/ros/genmsg/issues/63

Thanks for the clue @sea-bass. I'll try rebuilding my virtual env with python.

I pasted a link wrong in my previous comment. Updated.

authors: MichaelrMentele sea-bass


text:
Bring back the ability to customize host and port in copilot proxy by .env file

This PR is a follow-up to #64, in which I temporarily fixed #61 by removing the ability to customize the host and port via the .env file in docker-compose.yaml. I'll go ahead and fix the issue completely here.

That should be it, but an alternative would be to remove the custom port functionality entirely. In fact, I've rarely encountered a need to change this port myself, and I'm not quite sure what motivated this feature to be added in the first place.

The thought was that someone may already be using port 5000 on their local machine (or remote server) for something else, so they should be able to customize it. Just to make sure, we're talking about the port that the Flask proxy app runs on (which is what you point the OpenAI library or Copilot plugin at), right?

I mean the port used by uvicorn (in the past, it's flask) in copilot_proxy. That is, ${API_PORT} in docker-compose.yaml.
In order to avoid port conflicts, we usually modify the HOST in ports: [ "HOST:CONTAINER" ], right? Because this conflict usually occurs in the host rather than the container. For example, if a server already occupies port 5000, then I think we usually change the ports that were originally 5000:5000 to 5001:5000 instead of 5000:5001. So I am not very clear on the necessity of this port modification.🤔

Ah, yes, of course you're right. Yeah, I can't think of any reason why someone would need to change that port inside the container, and if they do they're probably doing something weird enough that they can just change the source code.

So I guess we should use another scheme? That is, remove this function. If so, I'll be trying to work on this.
Or to keep it, this draft PR should be ready.

@fdegier, were you using the custom port stuff for anything?
If not, I think we can remove it, yes.

I think there needs to be some concrete examples of why this modification is necessary.

@Frederisk sorry for the late reply, I went over your PR and now better understand what you meant. I've incorporated your feedback into a new PR (https://github.com/moyix/fauxpilot/pull/73), as I also further simplified the setup. Thanks for picking up on some of the mistakes that I had made in my earlier PR and fixing them.

A solution to remove the feature was taken.

authors: Frederisk fdegier moyix

repo: moyix/fauxpilot


text:
fixes bug 1225860 - Upgrade raven and Sentry DSN

I've verified that it works locally using dev's DSN

Coverage remained the same at 84.907% when pulling 6403a2956cd49950d6996ca7217f2d3b48ca79fc on peterbe:bug-1225860-upgrade-raven-and-sentry-dsn into dc1e8bb20ac235633b3342b97319b806258d7a81 on mozilla:master.

authors: coveralls peterbe

repo: mozilla/airmozilla


text:
Attribute alteration

Datomic allows you to alter :db/cardinality, :db/isComponent, :db/noHistory, :db/index and :db/unique via :db.alter/attribute transacts. Datomic doesn't allow you to alter :db/valueType (which I think is fine) or :db/fulltext (which I think we could support with little effort).
I think we'll need to support these kinds of alterations, automatically effected by ensureSchema, in order to do very basic schema fixing/tweaking, particularly from JS code.
Note that this doesn't include actually managing schema versions and migrating data — these attribute alterations fail if the store contains incompatible data.

Schema changes:

cardinality

one to many: fine
many to one: validate

isComponent:

fine

noHistory:

Currently ignored, hint only -- fine.

unique

nil to value: validate
nil to identity: validate
identity to value or value to identity: fine

index

enable or disable the avet index.

repo: mozilla/datomish


text:
Schema extension: interned keywords

:db/valueType :db.type/keyword is used to denote a restricted set of values. But we store these as strings. We should consider a schema flag to signal that a keyword value should be automatically interned (as an ident or otherwise) to avoid storing duplicate strings in the database.

Note that Datomic does intern keywords.

This is interesting, because it's identical to using a :db/ref type to a :db/idented entid.  The set of known idents is kept in memory and should be very small; I think it would be okay to only accept keywords that already have an ident associated, so that keywords are really enums.  This could be loosened in the future by automatically generating idents for keyword values (at the cost of generating datoms the user didn't explicitly specify), or by storing the intern map separately from the datom store, or by fixing the intern mapping globally.

Additionally: I don't think it necessarily makes sense for this to be a property of an attribute, and we should think about doing this automatically for all keywords… or, conversely, making this an option for all large types (URIs, bigints, strings, keywords).
The nice thing about associating this with a type, rather than an attribute, is that we avoid the kind of split we have with fulltext strings.

authors: ncalexan rnewman

repo: mozilla/mentat


text:
Add some extra explanation on Open Canvas quadrants

Hi @acabunoc
Filling in the Open Canvas for OL7. Nice work!
I have a slight improvement you can consider, and that is to address each quadrant with a paragraph of explanatory text, adding additional rationale to having the quadrant, in order to help people interpret them correctly.
For instance:

Problem quadrant: Do I only mention product-/community-related external problems (probably), or also internal ones. E.g. external: "Most people are unaware of harms of technology and how they affect them" and internal: "Though project members express worry about tech harms, it is very hard to activate them to work on their solutions".

Key metrics: Should metrics be quantitative, qualitative or even subjective (e.g. "Frequent mention of our community in authoritative newspapers")

Just a tip. The paragraphs can be very short.

Huge thanks for this Arnold! I tend to leave things more open to interpretation, so people can answer in whatever way they think is useful. But I realize how that can lead to more confusion! Do you have a suggestion on to refine the current explainer text in the canvas?
I appreciate your insight here!

On Feb 10, 2019, at 3:33 AM, Arnold Schrijver notifications@github.com wrote:
Hi @acabunoc
Filling in the Open Canvas for OL7. Nice work!
I have a slight improvement you can consider, and that is to address each quadrant with a paragraph of explanatory text, adding additional rationale to having the quadrant, in order to help people interpret them correctly.
For instance:
Problem quadrant: Do I only mention product-/community-related external problems (probably), or also internal ones. E.g. external: "Most people are unaware of harms of technology and how they affect them" and internal: "Though project members express worry about tech harms, it is very hard to activate them to work on their solutions".
Key metrics: Should metrics be quantitative, qualitative or even subjective (e.g. "Frequent mention of our community in authoritative newspapers")
Just a tip. The paragraphs can be very short.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I tend to leave things more open to interpretation

Yes, that is not bad in itself, as there are multiple interpretations. I think the canvas should be used in ways that are most practical and may be different for each individual case.
Some general points:

After the first sentence in MVP paragraph, add that you best fill in the canvas with the scope of that MVP in mind. It is easy to go into too much detail or too general and the limited space of the canvas plus MVP in mind, helps scrapping that and only mention bare essentials.

Also I think the canvas is more of an internal tool, to focus the team itself and get them aligned to set the right priorities. When you fill in for an external audience one tends to fill in more 'beautiful' well-formed sentences, but distract from the essence of the canvas. You could mention the distinguisment.

Also mentioning practicality and freedom to make changes to applying the canvas, can be good. At Humane Tech Community our eventual scope, audience and stakeholders are vast. The canvas and MVP concept fit best for a concrete project or product, while our scope is more fitting to creating a 'product portfolio'. We created a single top-level canvas, and will probably later create lower-level ones, i.e. targeted to our focus areas of Wellbeing, Freedom and Society (and maybe one for Harms), etc.

The hardest to fill in - and mostly likely to lead to confusion - are Solution, Problem, Unique Value Proposition. I mentioned a point about Problem above, for the others:

Solution quadrant: Do I describe them conceptually or concreetly (e.g. "We collect solutions for the harms of technology, which we will promote to the public to stimulate their use" versus "We collect technical solutions on Github, discuss them on our forum, after which our Campaigners promote them via our Awareness Program"). Both approaches can be valid, I think, but maybe you should stick with the approach you've chosen.

UVP quadrant: "What you offer" and "Why you are different". The first has overlap with Solution. The second statement is more important, I think. It is what makes you stick out above other similar initiatives. Your unique position that'll make your project viable. Note that you are missing that last aspect in your second example.

The other quadrants are more or less clear, only in our case as a community we read 'users' as our 'audience' and 'contributors' as our 'members' divided into several groups (plus partners).

FYI, this is how we filled out our Open Canvas for OL7 Cohort B: https://github.com/MozillaFestival/open-leaders-7/issues/41#issuecomment-462317076

authors: acabunoc aschrijver

repo: mozilla/open-leadership-training-series


text:
Working on Safari, but not working on chrome and firefox with error: Missing PDF Exception

We store the PDF file above AWS S3, and access it through Cloudfront. To access the PDF file, I have to call api: /api/preview-file/30.json
But on chrome and firefox I get the error: "MissingPDFException", but on Safari everything works fine, which is confusing.
I have searched but have no answer, looking forward to your help. Thank you!
Configuration:

Web browser and its version: Chrome Version 89.0.4389.114 (Official Build) (x86_64), Firefox 87.0 (64-bit)
Operating system and its version: Mac OS High Sierra 10.13.6
PDF.js version: 2.6.347

What went wrong? (add screenshot)

Firefox:

Chrome:

My code: PreviewFile.vue
import * as pdfjsLib from 'pdfjs-dist'
import * as pdfjsWorker from 'pdfjs-dist/build/pdf.worker.entry'

pdfjsLib.GlobalWorkerOptions.workerSrc = pdfjsWorker

export default {
    name: 'PreviewFile',
    mounted () {
        // const url = this.$route.query.q
        pdfjsLib.getDocument('/api/preview-file/30.json').promise.then(pdf => {
            const viewer = document.getElementById('pdf-viewer')

            for (let pageNum = 1; pageNum <= pdf.numPages; pageNum++) {
                const canvas = document.createElement('canvas')
                canvas.className = 'pdf-page-canvas'
                viewer.appendChild(canvas)
                pdf.getPage(pageNum).then(page => {
                    const viewport = page.getViewport({ scale: 2 })
                    canvas.height = viewport.height
                    canvas.width = viewport.width
                    page.render({ canvasContext: canvas.getContext('2d'), viewport: viewport })
                })
            }
        })
    }
}

Network on firefox: 404

Network on safari: OK

When opening an issue, please provide all of the information requested in https://github.com/mozilla/pdf.js/blob/master/.github/ISSUE_TEMPLATE.md since as-is this issue unfortunately contains no actionable information and will be closed as INVALID.

We store the PDF file above AWS S3, and access it through Cloudfront. To access the PDF file, I have to call api: /api/preview-file/30.json
But on chrome and firefox I get the error: "MissingPDFException", but on Safari everything works fine, which is confusing.
I have searched but have no answer, looking forward to your help. Thank you!

You've not provided the PDF file in question, which is the very first thing we ask for in the ISSUE_TEMPLATE.
Furthermore, this looks for all intents and purposes like a browser bug, rather than a PDF.js library one.
Finally, since this is specific to a particular implementation you'll need to provide a runnable example; please see https://github.com/mozilla/pdf.js/blob/master/.github/CONTRIBUTING.md (emphasis mine):

If you are developing a custom solution, first check the examples at https://github.com/mozilla/pdf.js#learning and search existing issues. If this does not help, please prepare a short well-documented example that demonstrates the problem and make it accessible online on your website, JS Bin, GitHub, etc. before opening a new issue or contacting us in the Matrix room -- keep in mind that just code snippets won't help us troubleshoot the problem.

PDF.js version: 2.6.347

That version is no longer supported, please find the latest releases at https://mozilla.github.io/pdf.js/getting_started/#download

When opening an issue, please provide all of the information requested in https://github.com/mozilla/pdf.js/blob/master/.github/ISSUE_TEMPLATE.md since as-is this issue unfortunately contains no actionable information and will be closed as INVALID.

We store the PDF file above AWS S3, and access it through Cloudfront. To access the PDF file, I have to call api: /api/preview-file/30.json
But on chrome and firefox I get the error: "MissingPDFException", but on Safari everything works fine, which is confusing.
I have searched but have no answer, looking forward to your help. Thank you!

You've not provided the PDF file in question, which is the very first thing we ask for in the ISSUE_TEMPLATE.
Furthermore, since this is specific to a particular implementation you'll need to provide a runnable example; please see https://github.com/mozilla/pdf.js/blob/master/.github/CONTRIBUTING.md (emphasis mine):

If you are developing a custom solution, first check the examples at https://github.com/mozilla/pdf.js#learning and search existing issues. If this does not help, please prepare a short well-documented example that demonstrates the problem and make it accessible online on your website, JS Bin, GitHub, etc. before opening a new issue or contacting us in the Matrix room -- keep in mind that just code snippets won't help us troubleshoot the problem.

PDF.js version: 2.6.347

That version is no longer supported, please find the latest releases at https://mozilla.github.io/pdf.js/getting_started/#download

My link pdf: https://swell-cdn.checkit4team.com/132011/91fe7226-9cd9-455b-8cfa-0b4eaf26e785/sample.pdf It's in my attachment image, but it's stored in s3 and you won't have access to it.  It is difficult to deploy it. Can you review the error?

[...] but it's stored in s3 and you won't have access to it.

Again, as already mentioned, without a reduced test-case that we can run/debug this unfortunately isn't actionable!
Please understand that it's impossible to do any meaningful debugging from screen-shots alone; and that this is first and foremost a bug tracker, rather than a support forum, hence all issues are required to be complete and easily actionable.


text:
Add tests to check that the rendering is correct at different zoom levels

We could generate some images at different zoom level and use them as reference.

At the risk of overlooking something obvious, it seems that the (by far) simplest solution would be to just add a new optional scale property (with 1 as the default value) in the driver.js and test_manifest.json files and then just adding a few different entries in the manifest using the same PDF document but with different scale values.

And we could add a ref test for:
https://github.com/mozilla/pdf.js/issues/12868
@quaoaris, would you like to work on this bug ?

Yes, I can do so... if it may take some time...

I just made a PR regarding this issue. Therefore I just used an additional scale factor (default=1) to scale the output of the rendered pdf. This scales the complete pdf. If your request was to just scale an area, I have to redo this.

authors: Snuffleupagus calixteman quaoaris


text:
Using eval is strongly discouraged

When building a project that has direct or indirect dependency to pdf.js, following message is printed as error and breaks pipelines:
Use of eval in "node_modules/pdfjs-dist/build/pdf.js" is strongly discouraged as it poses security risks and may cause issues with minification.
Configuration:

PDF.js version: 2.16.105
Is a browser extension: No

Using it through ReactJS component react-pdf.

Duplicate of #16061

authors: Snuffleupagus erkib


text:
How I can load all contents When I used this plug In web app just once?

Link to PDF file (or attach file here):
Configuration:

Web browser and its version:
Operating system and its version:
PDF.js version:
Is an extension:

Steps to reproduce the problem:
1.
2.
What is the expected behavior? (add screenshot)
What went wrong? (add screenshot)
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

Closing as incomplete, since the lack of any details makes it impossible to understand what's being asked here. (Please fill out the issue template with all the relevant information when opening an issue.)


text:
Simplify the code that picks the appropriate NetworkStream-implementation

This code is quite old and has been moved/re-factored a few times over the years, however we can simplify this even further since we don't actually need a function to determine what NetworkStream-implementation to use.
Slightly smaller diff with https://github.com/mozilla/pdf.js/pull/18756/files?w=1

/botio test


text:
outputs-0.data-00000-of-00001: DATA_LOSS: not an sstable (bad magic number): perhaps your file is in a different file format and you need to use a different restore operator?

Hello, I have used the MIMIC data set, after training, I wanted to generate data but get the following Error: outputs-0.data-00000-of-00001: DATA_LOSS: not an sstable (bad magic number): perhaps your file is in a different file format and you need to use a different restore operator?
can anyone help?
Best,
Navid

I was using a wrong command to generate data, this command worrked:
python medgag.py matrixFile.matrix path to where resulting .npy file should be saved --model_file=path to the trained files/ -999 --generate_data=True --data_type= "count"


text:
Add CI testing via GitHub Actions

Add CI testing per https://game.ci/docs/github/test-runner/

Closed due to being unable to get Unity license key for personal account.


text:
小程序使用dio post请求出错

使用dio 在小程序中post请求带body时，body的参数会丢失

具体代码可以贴一下，或者提供完整的调用描述。
这个场景是经过验证的，正常情况不会出现问题。

您好，具体情况是这样，我们项目的登录接口需要header里content-type为application/json，但是小程序里的post如果要传body的话，需要将content-type改为application/x-www-form-urlencoded，否则body就丢了，这种是不是需要我们后端改一下接口呀

我在其它项目里没有遇到这样的问题，content-type 为 application/json 也是可以发送 body 的。
或者你可以试试把脱敏后的请求代码完整地发到这里，我可以帮忙 debug 一下。

您好，我调用了一个开源的接口，好像确实会丢body，具体情况，我截图给您看

左边的是小程序的，通过body传数据是失败了，后端没有接收到，右边是正常flutter的代码，是传body成功了

具体代码如下
Map<String, dynamic> par = {
"key": "98e04a2dc283e9b70ba9749e5418747d",
};
BaseOptions _options = BaseOptions(
baseUrl: Environment.host(),
connectTimeout: 15000,
contentType: "application/x-www-form-urlencoded");
Dio _dio = Dio(_options);
_dio.interceptors.add(LogInterceptor(
requestHeader: true,
requestBody: true,
responseBody: true,
responseHeader: true,
));
await _dio.request(
"http://v.juhe.cn/toutiao/index",
data: par,
options: Options(
method: "POST",
),
);

我用http库访问成功了，看样子还是dio库打包成微信小程序的问题，大佬有时间看看dio库中间转换成小程序出现了啥问题

把有问题的代码脱敏打包发一下这里吧。

该问题已修复，可以使用以下 dio 版本解决问题。
dio: "4.0.1+1"
非常感谢 @kksqql 反馈问题

我也遇到这个问题了，调试各个平台都正常 打包了后 Android iOS Mac都正常 就Windows异常...(post 异常 get正常)

我也遇到这个问题了，调试各个平台都正常 打包了后 Android iOS Mac都正常 就Windows异常...(post 异常 get正常) 版本 4.0.1+1

微信小程序在 windows 平台上不支持 wx. base64ToArrayBuffer 导致会有这个问题，稍后会出一个补丁修正。

authors: AriesHoo PonyCui kksqql

repo: mpflutter/mpflutter


text:
请问 MPFlutter 有什么好实现可按按钮动画的方式

看文档说 ElevatedButton 不能使用，请问有什么比较好实现按下动画的方式？

有方法了吗？我用Tapped这个包也不行，没有点击变色效果了


text:
[3.0] Including @queryParam crashes apidoc:generate

Running php artisan apidoc:generate yields ErrorException  : implode(): Invalid arguments passed (View: ~/vendor/mpociot/laravel-apidoc-generator/resources/views/partials/route.blade.php)
Looking into this, it doesn't appear that the description param is ever converted to an array. Not in my case anyways.
I resolved this locally by modifying route.blade.php from:
#### Query Parameters

Parameter | Status | Description
--------- | ------- | ------- | -----------
@foreach($route['queryParameters'] as $attribute => $parameter)
    {{$attribute}} | @if($parameter['required']) required @else optional @endif | {!! implode(' ',$parameter['description']) !!}
@endforeach

to:
#### Query Parameters

Parameter | Status | Description
--------- | ------- | ------- | -----------
@foreach($route['queryParameters'] as $attribute => $parameter)
    {{$attribute}} | @if($parameter['required']) required @else optional @endif | {!! $parameter['description'] !!}
@endforeach

I'm not sure if anyone has experienced the same issue, or if there is some array conversion somwhere not happening.

Thanks. You're right. Fixing this in a bit.
On Mon, 22 Oct 2018, 19:32 949mac, notifications@github.com wrote:

Running php artisan apidoc:generate yields ErrorException : implode():
Invalid arguments passed (View:
~/vendor/mpociot/laravel-apidoc-generator/resources/views/partials/route.blade.php)
Looking into this, it doesn't appear that the description param is ever
converted to an array. Not in my case anyways.
I resolved this locally by modifying route.blade.php from:
Query Parameters
Parameter | Status | Description
--------- | ------- | ------- | -----------
@foreach($route['queryParameters'] as $attribute => $parameter)
{{$attribute}} | @if($parameter['required']) required @else optional @endif | {!! implode(' ',$parameter['description']) !!}
@endforeach
to:
Query Parameters
Parameter | Status | Description
--------- | ------- | ------- | -----------
@foreach($route['queryParameters'] as $attribute => $parameter)
{{$attribute}} | @if($parameter['required']) required @else optional @endif | {!! $parameter['description'] !!}
@endforeach
I'm not sure if anyone has experienced the same issue, or if there is some
array conversion somwhere not happening.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mpociot/laravel-apidoc-generator/issues/385, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ANsh8ZhFN9HV0DKUNNfHtdFVmU29e3Zeks5ung83gaJpZM4Xz7GD
.

This should be fixed now (3.0.1)

repo: mpociot/laravel-apidoc-generator


text:
Not connecting to python

Hello there,
I've been trying to follow the instructions for Mac, although I continue to get errors that Python doesn't exist. I am sure I have used Python 3.1 for other apps, so is it possible I am somehow referencing the wrong path?
/opt/homebrew/bin/python3 -m venv .venv

Hi @maxbatt22,
You may not have python 3.10 installed, or if you do then you need to specifically reference python 3.10 and not just python 3, which will default to some version and maybe not the one you want. Note that python 3.10 is not the same as python 3.1 (semantic versioning looks like a decimal system but it is not).
When you run python3 from the terminal do you get an output like:
Python 3.10.10 (tags/v3.10.10:aad5f6a, Feb  7 2023, 17:20:36) [MSC v.1929 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>>

Regards,
Mac

Hello Mac,
Thank you so much! I am planning on using this tool for the next episode of my show, AI MASHUPS.
I think you're right. Python is ON my system, but every time I type python --version  into Terminal, it launches Xcode to install more software (then seemingly doesn't install it).
But then when I type in your command, it is almost identical
Python 3.9.6 (default, Jun 28 2021, 19:24:41)
[Clang 12.0.5 (clang-1205.0.22.9)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

Previously, when I tried to find the path of Python, the word "Homebrew" was in the path. Perhaps Homebrew installed the wrong version for Caliscope to use?

Hi @maxbatt22,
I'm primarily on Windows these days and occasionally Ubuntu as needed, so I don't have good specific guidance for navigating MacOS issues. It seems like you are having trouble setting up a python 3.10 virtual environment.
Do you have something on your filesystem named python3.10? If so, can you run the install code from the README?:

# Create a virtual environment named 'venv' using Python 3.10
/path/to/python3.10 -m venv .venv

If not, then you may need to install 3.10:  https://www.python.org/downloads/release/python-3100/
Regards,
Mac

closing as this was likely a python environment issue.

repo: mprib/caliscope


text:
Build failure: no matching function for call to ‘Groupsock::Groupsock(UsageEnvironment&, in_addr&, Port&, int&)

Looks like a function signature changed in the latest live555 version? Here's the full build output:
Groupsock build error.txt

Had a hard time figuring out which version of live555 was used for this build. Checking on their website, I find the following files and timestamps:
  | live.2020.12.11.tar.gz | 2020-12-10 16:44 | 663K |
  | live555-latest-md5.txt | 2020-12-10 16:44 | 33 |
  | live555-latest.tar.gz | 2020-12-10 16:44 | 663K |

not really related, but apparently this is not the only recent breakage due to live555 changes: #218 (already fixed by @mpromonet)

Ok, found this in their FAQ: 'To see which version of the code you currently have, look at the file "liveMedia/include/liveMedia_version.hh".' One may be excused for overlooking that one :o)
My version is
#define LIVEMEDIA_LIBRARY_VERSION_STRING	"2020.12.11"
#define LIVEMEDIA_LIBRARY_VERSION_INT		1607644800

Hi nettings,
live555 seems to change often of interface this days.... it doesnot even build with 2020.12.12.
You can build it with :
cmake -D LIVE555URL=https://download.videolan.org/pub/contrib/live555/live.2020.12.11.tar.gz .

Best Regards,
Michel.

Dear Michel, sorry to hear that - it must be a lot of extra work for you. Thank you for the workaround, that solves my problem! Maybe you should update your README.md to prevent other users from hitting this issue. All best, Jörn

Hi nettings,
This is quite uncommon, usually live555 doesnot evolve much, it seems there is work in progress about IPV6.
The approach of this project is to use latest version, often small refactoring vs big refactoring.
Anyway you suggestion seems meaningful, I will add a note in the README to build with an oldest live555 release (even this release comes from videolan)
Best Regards,
Michel.

authors: mpromonet nettings

license: unlicense


text:
crawl task not using baseUrl

I have the following configuration of crawl
crawl: {
            "sitemap": {
                "baseUrl": "http://localhost:8080",
                "content": false,
                "sitemap": true,
                "sitemapDir": "www"
            }
        }

When I run the grunt task grunt crawl, I see the following output:
Running "crawl:sitemap" (crawl) task
Crawling http://localhost:9000 ...
   ...finished crawling.

In my www directory I see an empty index.html.
I guess that the baseUrl is not taken into account and that content is also ignored. I would expect to have only a sitemap.xml file in there.

More poor documentation on my part, sorry.
Also, I would run this on the live site so that sitemap.xml doesn't get populated with 'http://localhost:8080' which Google will probably complain about.
  crawl: {
    sitemap {
      options: {
         "baseUrl": "http://localhost:8080",
         "content": false,
         "sitemap": true,
         "sitemapDir": "www"
      }
    }
  }

Ok, with a small change (adding a colon after sitemap), the command ran fine.
I'm a bit at a loss of what the expected output should have been.
This is my sitemap.xml:
<?xml version="1.0" encoding="utf-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"><url><loc>http://localhost:8080/#/</loc><lastmod>2015-11-09</lastmod><priority>1.0</priority><changefreq>weekly</changefreq></url></urlset>

I was expecting to get all the links that the site offers (in the form of http://www.yourwebsite.com/#!/relativePath)

Are you using fragment routing?
Could you add followFragment: true to the options?

What is fragment routing? (I guess I'm not using it.. I'm using ngRoute)
I see this output when running grunt crawl (with or without followFragment):
    ...Requesting [object Object]
    ...Server repsonded [object Object]
    ...Requesting [object Object]
    ...Requesting [object Object]
    ...Requesting [object Object]
    ...Requesting [object Object]
    ...Requesting [object Object]
    ...Requesting [object Object]
    ...Server repsonded [object Object]
    ...Server repsonded [object Object]
    ...Training sessions loaded [object Object],[object Object]
    ...Server repsonded [object Object]
    ...News loaded [object Object],[object Object]
    ...Server repsonded [object Object]
    ...Interim jobs loaded [object Object]
    ...Server repsonded [object Object]
    ...Events loaded [object Object],[object Object]
    ...Server repsonded [object Object]
    ...Permanent jobs loaded [object Object],[object Object],[object Object]

Fragment routing is just a generic term for web sites that "route" or use paths with # (the fragment of the URL). Yes, you should set followFragment to "true".
If there are no anchor elements on the page when the crawl script gets to it, and readySelector is set to false, then it will only find the one page to crawl. However if readySelector is set to the selector with a data-status attribute, then it will wait until data-status="ready". I have to do this for my personal angular app because I have dynamic links populated in my views/partials. So I have this code:
app.js
  .run(['$location', '$rootScope', function($location, $rootScope) {
    $rootScope.ready = function() {
      $rootScope.status = 'ready';
      if (!$rootScope.$$phase) $rootScope.apply();
    };
    $rootScope.loading = function() {
      $rootScope.status = 'loading';
      if (!$rootScope.$$phase) $rootScope.apply();
    };
   $rootScope.on('$routeChangeStart', function() {
     $rootScope.loading();
   };

and then in my partial I have
<main ng-view data-status="{{ status }}"></main>

and in a controller
.controller('myController', ['$scope', function($scope) {
  // do other stuff...
  $scope.ready();
}]);

Still doesn't work... This configuration is from the live website:
crawl: {
            sitemap: {
                options: {
                    "baseUrl": "https://www.inkoopjobs.nl/#/",
                    "content": false,
                    "sitemap": true,
                    "sitemapDir": "www",
                    "followFragment": true
                }
            }
        }

Hmm... I investigated tonight, and something is causing Phantom to exit out without finding the content. Phantom is very difficult to get errors out of, but I am still looking into it.

authors: mradcliffe treaz

repo: mradcliffe/grunt-crawl


text:
🛑 Where The Hell Michael [wherethehellismichael.com] is down

In 6a8df74, Where The Hell Michael [wherethehellismichael.com] (https://wherethehellismichael.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Where The Hell Michael [wherethehellismichael.com] is back up in a08f0ab after 40 minutes.


text:
🛑 Auto Lock Specialists [kalamazoo-locksmith.com] is down

In 091e40e, Auto Lock Specialists [kalamazoo-locksmith.com] (https://kalamazoo-locksmith.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auto Lock Specialists [kalamazoo-locksmith.com] is back up in ea015ba after 35 minutes.


text:
Please add to Arduino Library Manager

Please make this library available in the Arduino Library Manager.

Ensure your library is complaint with 1.5 format(1.5 format folder layout is not required)
Tag it and push the tag, or create a release with github "releases"
Open an issue on Arduino's github, specifying the git repo (or github url) from where to download your library

More information on https://github.com/arduino/Arduino/wiki/Library-Manager-FAQ

in theory this is a good idea.
it won't happen soon however.
i'm not currently working on the esp8266 and have no prior Arduino experience so would need to do a little research to make it happen.
i'll happily approve commits from you if you have the spare time.
alternatively i'll look into it next time i'm working with this code.
thanks for the feedback.

commit 9713a06 addresses this.
thanks for the submission.
is there anything else we need for this or should this issue be marked 'closed'?

Please create a release with github "releases". Then I can open an issue on Arduino's github repo.

https://github.com/mrdunk/esp8266_mdns/releases/tag/v1.0

https://github.com/arduino/Arduino/issues/4532

acknowledged.
thanks for the help.

https://github.com/arduino/Arduino/issues/4532#event-577678660

authors: mrdunk probonopd


text:
Blank

hi , i tried this app but i get a blank page.
thank you

Is there any db setup i need to do?

Ah, Windows. There is no DB setup needed. I use NeDB which is basically a document based database. I will get back to you on this. Although should work.

repo: mrgodhani/rss-reader


text:
Add setting.ini generator

应增加一个 setting.ini 文件生成器，用于快速生成配置文件，而不是手动去复制配置文件

增加了一个命令行工具，使用 java -jar database2api.jar --help 查看所有命令行功能。效果如下：
[database2api]
------------------------------------------------
DataBase to API, use database, generate open API
https://github.com/mrhuo/database2api
------------------------------------------------
用法：
	java -jar database2api.jar			启动 database2api
	java -jar database2api.jar --help		查看此帮助
	java -jar database2api.jar --gen-setting	快速生成数据库配置

当使用 java -jar database2api.jar --gen-setting 启动时，需要提供数据库连接字符串（必填），数据库用户名（可选，无密码直接回车），数据库密码（可选，无密码直接回车），实现自动创建 ./data/setting.ini 配置文件的功能。
[database2api]
------------------------------------------------
DataBase to API, use database, generate open API
https://github.com/mrhuo/database2api
------------------------------------------------
-> 正在生成数据库配置...
-> 警告:配置文件 D:\work\java\database2api\source\data\setting.ini 已存在，是否删除？(Y/N)
y
-> 警告:配置文件 D:\work\java\database2api\source\data\setting.ini 已删除

-> 请输入数据库连接字符串：
jdbc:sqlite://G:/database2api-test/sqlite/fqb.db
-> 请输入数据库用户名：

-> 请输入数据库密码：

-> 生成配置成功，保存路径 D:\work\java\database2api\source\data\setting.ini

Process finished with exit code 0


text:
Update to Swift 5

Hi!
Update pls this wonderful project to swift 5.
Than u!!!

Hello,
I too would like this to be updated to the latest Swift.
Any idea on the timeline for this?

sorry for the delayed response. @fury21 @stamizharasu is the swift 5 upgrade still desired?

@mrigdon Yes, if possible. I'm currently blocked due to the lack of version upgrades.

@stamizharasu  my apologies. will begin work on this immediately.

authors: fury21 mrigdon stamizharasu

repo: mrigdon/MRArticleViewController


text:
Fixing apikey bug

The check .v.type.toLowerCase() === 'apiKey' was broken
...perhaps fixes #328

I noticed it was already fixed in the past : https://github.com/mrin9/RapiDoc/commit/bd173247df7bb7b84d921e1feec8de9d96d43741#diff-55c42f67fbb6989d7dd4b662e9f2d0ec887dae69cb81327047b04830847926b7
But accidentally erased afterwards: https://github.com/mrin9/RapiDoc/commit/503997eb145d3b12b4f764b9f70f4b288fc740cc#diff-55c42f67fbb6989d7dd4b662e9f2d0ec887dae69cb81327047b04830847926b7

I noticed it was already fixed in the past : bd17324#diff-55c42f67fbb6989d7dd4b662e9f2d0ec887dae69cb81327047b04830847926b7

Yeah, #317 applied exactly this fix.

Yes, thanks for bringing it up and fixing it.  Was due to a merge conflict resolved incorrectly-
I have reapplied it in this commit 7104432e5c46ef9a43cf3a59652aa82d615fbc56 ,
I did not notice your PR, sorry for that
closing this PR - as its already taken care of

authors: dagnelies mrin9 waldyrious


text:
Parowanie openload

Please follow the guide below

Put an "x" into all boxes [ ] relevant to your issue
Use Preview tab to see how your issue will actually look like

Kodi & Addon

Kodi verison: _____
[ ] Filmy online - Mrknow
[ ] MrknowTV
[ ] Specto
[ ] FanFILM
Version / Wersja: _____

Descryption / Opis
Put here every imported thing such logs, how to reproduce etc.
Wstaw tutaj każdą ważna rzecz, taką jak logi, jak wywołać błąd itp.
Donation / Darowizna
This addons are free, but you can always thank the author for ... / Te wtyczki są darmowe, ale zawsze możesz podziękować autorowi za jej stworzenie...

Witam. Niestety problem parowania z openload wciąż występuje. Trzeba to robic za każdym razem i to częściej niż coś przewidziane 4h

Czy teraz już zawsze będzie trzeba parowac czy może będzie jak kiedyś że tylko kliknąć film i leciał?

Możesz użyć serwisu który omija takie zabezpieczanie, np realdebrid

authors: Kubackjeee mrknow

repo: mrknow/filmkodi


text:
Autofixing on errors

Hello,
I know that stylelint still not released yet with --fix feature, but after release when also stylefmt will be updated to use latest version of stylelint, what do you think about fix feature on format?
If you can don't close this issue, let it be, when stylelint and stylefmt will be updated with --fix feature we can discuss here to include it or no.

IMHO, this does not apply to this plugin. This should be implemented in the stylelint plugin.

@mrmlnc You're saying true, but stylelint plugin owner doesn't give a **** about that. By the way prettier is JS formatter, but it adds needed semicolons and so on, it works like --fix, but with extra addition, I was thinking the same for this CSS formatter, but anyway, you're saying true, this function not belongs for stylefmt.

You must to understand that they are two different entities and they are not associated. This functionality applies to Stylelint. Ideally, Stylelint must absorb Stylefmt because it uses the rules first. We can fork or send PR's to vscode-stylelint. I'm not going to close the issue to remember about him.

Fixed by #162.

authors: mrmlnc svipben

repo: mrmlnc/vscode-stylefmt


text:
Use of GitHub actions lint and Publish package

Added in actions that will perform tests on the package using GitHub actions. Allows for a greater amount of tests with a mix of operating systems and python versions.
Using GitHub actions the deploy flow will be.

Merge PR into master.
Tag the latest master with a tag starting with v
Push Tag to Github
Go to the release and a draft will appear. Fill it out an publish
Package will be uploaded to PyPi

@mrname To get the upload to work successfully, you will have to add a PyPi API token as a secret called PYPI_PASSWORD. Alternatively, we can create an organization for this project and transfer it there.

Coverage remained the same at 98.606% when pulling 577fef9d485c68188f9318d08c8b5b4726024dda on auto_deploy into 9b29d4cfa2b4c58bf77ab2090c1efb310559d280 on master.

Coverage remained the same at 98.606% when pulling 577fef9d485c68188f9318d08c8b5b4726024dda on auto_deploy into 9b29d4cfa2b4c58bf77ab2090c1efb310559d280 on master.

@mrname To get the upload to work successfully, you will have to add a PyPi API token as a secret called PYPI_PASSWORD. Alternatively, we can create an organization for this project and transfer it there.

No worries, token is added with appropriate secret name (I think you should be able to edit this if you ever need to). Happy to create an org as well if that seems easier to you or has other advantages.

@mrname I went ahead and setup an organization. Allows us for better collaboration. Once you join I will transfer ownership to you as this your project so you deserve the credit.

@mrname I went ahead and setup an organization. Allows us for better collaboration. Once you join I will transfer ownership to you as this your project so you deserve the credit.

Thanks, joined! I will take care of coveralls after we move the repo over 👍

authors: Cyb3r-Jak3 coveralls mrname

repo: mrname/haralyzer


text:
Grammar

Here instead of "a" , you want to say "and" .
Also I would say "lots" , instead of "loads" . It sounds a tiny bit more professional.

Fixed, thanks!

authors: jidanni mroczis

repo: mroczis/netmonster-core


text:
🐛  Square format doesn't work

What's happening?
I am trying to take a photo, either 1:1 or 4:5.
I have a toggle on my UI and two formats to choose from:
  const format = useCameraFormat(device, [
    {
      photoAspectRatio: isSquareRatio ? 1 / 1 : 4 / 5,
    },
    {photoResolution: { width: 1080, height: isSquareRatio ? 1080 : 1350 }},
    {videoAspectRatio: isSquareRatio ? 1 / 1 : 4 / 5},
    {videoResolution: {height: isSquareRatio ? 1080 : 1350, width: 1080}},
  ]);

The 4:5 works fine, it outputs the same view I have set for the camera, but 1:1 does not work.
When I set the photo resolution and ratio to 1 / 1, it does not output a square photo.
I used FFMPEG to do this before in v2, but now I am trying to get rid of this step (as it seems possible to just take the photo in that format instead of post cropping and processing all over again)...
Great library!
Reproduceable Code
N/A

Relevant log output
N/A

Camera Device
{"formats": [{"autoFocusSystem": "phase-detection", "fieldOfView": 64.72028350830078, "maxFps": 60, "maxISO": 3264, "maxZoom": 189, "minFps": 60, "minISO": 34, "photoHeight": 3024, "photoWidth": 4032, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 144, "videoStabilizationModes": [Array], "videoWidth": 192}, {"autoFocusSystem": "phase-detection", "fieldOfView": 64.72028350830078, "maxFps": 60, "maxISO": 3264, "maxZoom": 189, "minFps": 60, "minISO": 34, "photoHeight": 3024, "photoWidth": 4032, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 144, "videoStabilizationModes": [Array], "videoWidth": 192}, {"autoFocusSystem": "phase-detection", "fieldOfView": 59.326927185058594, "maxFps": 60, "maxISO": 3264, "maxZoom": 189, "minFps": 60, "minISO": 34, "photoHeight": 3024, "photoWidth": 3696, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 288, "videoStabilizationModes": [Array], "videoWidth": 352}, {"autoFocusSystem": "phase-detection", "fieldOfView": 59.326927185058594, "maxFps": 60, "maxISO": 3264, "maxZoom": 189, "minFps": 60, "minISO": 34, "photoHeight": 3024, "photoWidth": 3696, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 288, "videoStabilizationModes": [Array], "videoWidth": 352}, {"autoFocusSystem": "phase-detection", "fieldOfView": 64.72028350830078, "maxFps": 60, "maxISO": 3264, "maxZoom": 189, "minFps": 60, "minISO": 34, "photoHeight": 3024, "photoWidth": 4032, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 360, "videoStabilizationModes": [Array], "videoWidth": 480}, {"autoFocusSystem": "phase-detection", "fieldOfView": 64.72028350830078, "maxFps": 60, "maxISO": 3264, "maxZoom": 189, "minFps": 60, "minISO": 34, "photoHeight": 3024, "photoWidth": 4032, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 360, "videoStabilizationModes": [Array], "videoWidth": 480}, {"autoFocusSystem": "phase-detection", "fieldOfView": 64.72028350830078, "maxFps": 60, "maxISO": 3264, "maxZoom": 189, "minFps": 60, "minISO": 34, "photoHeight": 3024, "photoWidth": 4032, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 480, "videoStabilizationModes": [Array], "videoWidth": 640}, {"autoFocusSystem": "phase-detection", "fieldOfView": 64.72028350830078, "maxFps": 60, "maxISO": 3264, "maxZoom": 189, "minFps": 60, "minISO": 34, "photoHeight": 3024, "photoWidth": 4032, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 480, "videoStabilizationModes": [Array], "videoWidth": 640}, {"autoFocusSystem": "phase-detection", "fieldOfView": 64.72028350830078, "maxFps": 60, "maxISO": 3264, "maxZoom": 94.5, "minFps": 60, "minISO": 34, "photoHeight": 1512, "photoWidth": 2016, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 480, "videoStabilizationModes": [Array], "videoWidth": 640}, {"autoFocusSystem": "phase-detection", "fieldOfView": 64.72028350830078, "maxFps": 60, "maxISO": 3264, "maxZoom": 94.5, "minFps": 60, "minISO": 34, "photoHeight": 1512, "photoWidth": 2016, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 480, "videoStabilizationModes": [Array], "videoWidth": 640}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 60, "maxISO": 3264, "maxZoom": 123.75, "minFps": 60, "minISO": 34, "photoHeight": 2376, "photoWidth": 4224, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 540, "videoStabilizationModes": [Array], "videoWidth": 960}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 60, "maxISO": 3264, "maxZoom": 123.75, "minFps": 60, "minISO": 34, "photoHeight": 2376, "photoWidth": 4224, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 540, "videoStabilizationModes": [Array], "videoWidth": 960}, {"autoFocusSystem": "phase-detection", "fieldOfView": 64.72028350830078, "maxFps": 60, "maxISO": 3264, "maxZoom": 171.875, "minFps": 60, "minISO": 34, "photoHeight": 3024, "photoWidth": 4032, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 768, "videoStabilizationModes": [Array], "videoWidth": 1024}, {"autoFocusSystem": "phase-detection", "fieldOfView": 64.72028350830078, "maxFps": 60, "maxISO": 3264, "maxZoom": 171.875, "minFps": 60, "minISO": 34, "photoHeight": 3024, "photoWidth": 4032, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 768, "videoStabilizationModes": [Array], "videoWidth": 1024}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 30, "maxISO": 3264, "maxZoom": 123.75, "minFps": 30, "minISO": 34, "photoHeight": 2376, "photoWidth": 4224, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 30, "maxISO": 3264, "maxZoom": 123.75, "minFps": 30, "minISO": 34, "photoHeight": 2376, "photoWidth": 4224, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 30, "maxISO": 3264, "maxZoom": 123.75, "minFps": 30, "minISO": 34, "photoHeight": 2376, "photoWidth": 4224, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": true, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 60, "maxISO": 3264, "maxZoom": 123.75, "minFps": 60, "minISO": 34, "photoHeight": 2376, "photoWidth": 4224, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 60, "maxISO": 3264, "maxZoom": 123.75, "minFps": 60, "minISO": 34, "photoHeight": 2376, "photoWidth": 4224, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 60, "maxISO": 3264, "maxZoom": 123.75, "minFps": 60, "minISO": 34, "photoHeight": 2376, "photoWidth": 4224, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": true, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 60, "maxISO": 3264, "maxZoom": 61.875, "minFps": 60, "minISO": 34, "photoHeight": 1188, "photoWidth": 2112, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 60, "maxISO": 3264, "maxZoom": 61.875, "minFps": 60, "minISO": 34, "photoHeight": 1188, "photoWidth": 2112, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 240, "maxISO": 1360, "maxZoom": 67.5, "minFps": 240, "minISO": 34, "photoHeight": 720, "photoWidth": 1280, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 240, "maxISO": 1360, "maxZoom": 67.5, "minFps": 240, "minISO": 34, "photoHeight": 720, "photoWidth": 1280, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 720, "videoStabilizationModes": [Array], "videoWidth": 1280}, {"autoFocusSystem": "phase-detection", "fieldOfView": 64.72028350830078, "maxFps": 60, "maxISO": 3264, "maxZoom": 94.5, "minFps": 60, "minISO": 34, "photoHeight": 1512, "photoWidth": 2016, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 1080, "videoStabilizationModes": [Array], "videoWidth": 1440}, {"autoFocusSystem": "phase-detection", "fieldOfView": 64.72028350830078, "maxFps": 60, "maxISO": 3264, "maxZoom": 94.5, "minFps": 60, "minISO": 34, "photoHeight": 1512, "photoWidth": 2016, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 1080, "videoStabilizationModes": [Array], "videoWidth": 1440}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 30, "maxISO": 3264, "maxZoom": 123.75, "minFps": 30, "minISO": 34, "photoHeight": 2376, "photoWidth": 4224, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 1080, "videoStabilizationModes": [Array], "videoWidth": 1920}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 30, "maxISO": 3264, "maxZoom": 123.75, "minFps": 30, "minISO": 34, "photoHeight": 2376, "photoWidth": 4224, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 1080, "videoStabilizationModes": [Array], "videoWidth": 1920}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 30, "maxISO": 3264, "maxZoom": 123.75, "minFps": 30, "minISO": 34, "photoHeight": 2376, "photoWidth": 4224, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": true, "videoHeight": 1080, "videoStabilizationModes": [Array], "videoWidth": 1920}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 30, "maxISO": 3264, "maxZoom": 123.75, "minFps": 30, "minISO": 34, "photoHeight": 2376, "photoWidth": 4224, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 1080, "videoStabilizationModes": [Array], "videoWidth": 1920}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 60, "maxISO": 3264, "maxZoom": 123.75, "minFps": 60, "minISO": 34, "photoHeight": 2376, "photoWidth": 4224, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 1080, "videoStabilizationModes": [Array], "videoWidth": 1920}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 60, "maxISO": 3264, "maxZoom": 123.75, "minFps": 60, "minISO": 34, "photoHeight": 2376, "photoWidth": 4224, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 1080, "videoStabilizationModes": [Array], "videoWidth": 1920}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 60, "maxISO": 3264, "maxZoom": 123.75, "minFps": 60, "minISO": 34, "photoHeight": 2376, "photoWidth": 4224, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": true, "videoHeight": 1080, "videoStabilizationModes": [Array], "videoWidth": 1920}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 60, "maxISO": 3264, "maxZoom": 123.75, "minFps": 60, "minISO": 34, "photoHeight": 2376, "photoWidth": 4224, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 1080, "videoStabilizationModes": [Array], "videoWidth": 1920}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 60, "maxISO": 3264, "maxZoom": 61.875, "minFps": 60, "minISO": 34, "photoHeight": 1188, "photoWidth": 2112, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 1080, "videoStabilizationModes": [Array], "videoWidth": 1920}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 60, "maxISO": 3264, "maxZoom": 61.875, "minFps": 60, "minISO": 34, "photoHeight": 1188, "photoWidth": 2112, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 1080, "videoStabilizationModes": [Array], "videoWidth": 1920}, {"autoFocusSystem": "phase-detection", "fieldOfView": 38.78413772583008, "maxFps": 120, "maxISO": 1360, "maxZoom": 135, "minFps": 120, "minISO": 34, "photoHeight": 1080, "photoWidth": 1920, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 1080, "videoStabilizationModes": [Array], "videoWidth": 1920}, {"autoFocusSystem": "phase-detection", "fieldOfView": 38.78413772583008, "maxFps": 120, "maxISO": 1360, "maxZoom": 135, "minFps": 120, "minISO": 34, "photoHeight": 1080, "photoWidth": 1920, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 1080, "videoStabilizationModes": [Array], "videoWidth": 1920}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 240, "maxISO": 1360, "maxZoom": 67.5, "minFps": 240, "minISO": 34, "photoHeight": 1080, "photoWidth": 1920, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 1080, "videoStabilizationModes": [Array], "videoWidth": 1920}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 240, "maxISO": 1360, "maxZoom": 67.5, "minFps": 240, "minISO": 34, "photoHeight": 1080, "photoWidth": 1920, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 1080, "videoStabilizationModes": [Array], "videoWidth": 1920}, {"autoFocusSystem": "phase-detection", "fieldOfView": 67.09603881835938, "maxFps": 30, "maxISO": 3264, "maxZoom": 157.5, "minFps": 30, "minISO": 34, "photoHeight": 3024, "photoWidth": 4032, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 1440, "videoStabilizationModes": [Array], "videoWidth": 1920}, {"autoFocusSystem": "phase-detection", "fieldOfView": 67.09603881835938, "maxFps": 60, "maxISO": 3264, "maxZoom": 157.5, "minFps": 60, "minISO": 34, "photoHeight": 3024, "photoWidth": 4032, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 1440, "videoStabilizationModes": [Array], "videoWidth": 1920}, {"autoFocusSystem": "phase-detection", "fieldOfView": 67.09603881835938, "maxFps": 60, "maxISO": 3264, "maxZoom": 157.5, "minFps": 60, "minISO": 34, "photoHeight": 3024, "photoWidth": 4032, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 1440, "videoStabilizationModes": [Array], "videoWidth": 1920}, {"autoFocusSystem": "phase-detection", "fieldOfView": 67.09603881835938, "maxFps": 60, "maxISO": 3264, "maxZoom": 157.5, "minFps": 60, "minISO": 34, "photoHeight": 3024, "photoWidth": 4032, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": true, "videoHeight": 1440, "videoStabilizationModes": [Array], "videoWidth": 1920}, {"autoFocusSystem": "phase-detection", "fieldOfView": 67.09603881835938, "maxFps": 60, "maxISO": 3264, "maxZoom": 157.5, "minFps": 60, "minISO": 34, "photoHeight": 3024, "photoWidth": 4032, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 1440, "videoStabilizationModes": [Array], "videoWidth": 1920}, {"autoFocusSystem": "phase-detection", "fieldOfView": 67.09603881835938, "maxFps": 60, "maxISO": 3264, "maxZoom": 94.5, "minFps": 60, "minISO": 34, "photoHeight": 1512, "photoWidth": 2016, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 1440, "videoStabilizationModes": [Array], "videoWidth": 1920}, {"autoFocusSystem": "phase-detection", "fieldOfView": 67.09603881835938, "maxFps": 60, "maxISO": 3264, "maxZoom": 94.5, "minFps": 60, "minISO": 34, "photoHeight": 1512, "photoWidth": 2016, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 1440, "videoStabilizationModes": [Array], "videoWidth": 1920}, {"autoFocusSystem": "phase-detection", "fieldOfView": 67.09603881835938, "maxFps": 30, "maxISO": 3264, "maxZoom": 189, "minFps": 30, "minISO": 34, "photoHeight": 3024, "photoWidth": 4032, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 1944, "videoStabilizationModes": [Array], "videoWidth": 2592}, {"autoFocusSystem": "phase-detection", "fieldOfView": 67.09603881835938, "maxFps": 30, "maxISO": 3264, "maxZoom": 189, "minFps": 30, "minISO": 34, "photoHeight": 3024, "photoWidth": 4032, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 1944, "videoStabilizationModes": [Array], "videoWidth": 2592}, {"autoFocusSystem": "phase-detection", "fieldOfView": 67.09603881835938, "maxFps": 30, "maxISO": 3264, "maxZoom": 189, "minFps": 30, "minISO": 34, "photoHeight": 3024, "photoWidth": 4032, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 2448, "videoStabilizationModes": [Array], "videoWidth": 3264}, {"autoFocusSystem": "phase-detection", "fieldOfView": 67.09603881835938, "maxFps": 30, "maxISO": 3264, "maxZoom": 189, "minFps": 30, "minISO": 34, "photoHeight": 3024, "photoWidth": 4032, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 2448, "videoStabilizationModes": [Array], "videoWidth": 3264}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 30, "maxISO": 3264, "maxZoom": 129.125, "minFps": 30, "minISO": 34, "photoHeight": 2376, "photoWidth": 4224, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 2160, "videoStabilizationModes": [Array], "videoWidth": 3840}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 30, "maxISO": 3264, "maxZoom": 129.125, "minFps": 30, "minISO": 34, "photoHeight": 2376, "photoWidth": 4224, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 2160, "videoStabilizationModes": [Array], "videoWidth": 3840}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 30, "maxISO": 3264, "maxZoom": 129.125, "minFps": 30, "minISO": 34, "photoHeight": 2376, "photoWidth": 4224, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": true, "videoHeight": 2160, "videoStabilizationModes": [Array], "videoWidth": 3840}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 30, "maxISO": 3264, "maxZoom": 129.125, "minFps": 30, "minISO": 34, "photoHeight": 2376, "photoWidth": 4224, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 2160, "videoStabilizationModes": [Array], "videoWidth": 3840}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 60, "maxISO": 3264, "maxZoom": 129.125, "minFps": 60, "minISO": 34, "photoHeight": 2160, "photoWidth": 3840, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 2160, "videoStabilizationModes": [Array], "videoWidth": 3840}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 60, "maxISO": 3264, "maxZoom": 129.125, "minFps": 60, "minISO": 34, "photoHeight": 2160, "photoWidth": 3840, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 2160, "videoStabilizationModes": [Array], "videoWidth": 3840}, {"autoFocusSystem": "phase-detection", "fieldOfView": 70.29109191894531, "maxFps": 60, "maxISO": 3264, "maxZoom": 129.125, "minFps": 60, "minISO": 34, "photoHeight": 2160, "photoWidth": 3840, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": true, "videoHeight": 2160, "videoStabilizationModes": [Array], "videoWidth": 3840}, {"autoFocusSystem": "phase-detection", "fieldOfView": 67.09603881835938, "maxFps": 30, "maxISO": 7616, "maxZoom": 189, "minFps": 30, "minISO": 34, "photoHeight": 3024, "photoWidth": 4032, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 3024, "videoStabilizationModes": [Array], "videoWidth": 4032}, {"autoFocusSystem": "phase-detection", "fieldOfView": 67.09603881835938, "maxFps": 30, "maxISO": 7616, "maxZoom": 189, "minFps": 30, "minISO": 34, "photoHeight": 3024, "photoWidth": 4032, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHDR": false, "supportsVideoHDR": false, "videoHeight": 3024, "videoStabilizationModes": [Array], "videoWidth": 4032}], "hardwareLevel": "full", "hasFlash": true, "hasTorch": true, "id": "com.apple.avfoundation.avcapturedevice.built-in_video:0", "isMultiCam": false, "maxZoom": 189, "minZoom": 1, "name": "Back Camera", "neutralZoom": 1, "physicalDevices": ["wide-angle-camera"], "position": "back", "sensorOrientation": "landscape-right", "supportsFocus": true, "supportsLowLightBoost": false, "supportsRawCapture": false}

Device
iPhone 13 Pro Max
VisionCamera Version
3.6.4
Can you reproduce this issue in the VisionCamera Example app?
Yes, I can reproduce the same issue in the Example app here
Additional information

[ ] I am using Expo
[ ] I have enabled Frame Processors (react-native-worklets-core)
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

Hi @mrousavy
iOS does support square format. At least it does now, when I'm going the camera on the iphone :-) It doesn't seem like this library can support it atm though.. Do you think it will be possible? :-)

repo: mrousavy/react-native-vision-camera


text:
Reisebuddy toggle ui

@RocketChat/core

Closes #ISSUE_NUMBER

Should be part of Rocket.Chat Standard => Open a PR to RocketChat/develop if still needed


text:
where to add link of source file

please suggest how to convert local .dfq file using this code

You will have to change the code in console app. Console app simply takes dfq from the current folder.

repo: mrtomeq/DFQtoJSON-Converter


text:
[ BUG ] Not able to change or modify css using tailwind

Describe the bug
I'm using your starter pack, so integration shouldn't be an issue. However, I've encountered this problem multiple times. Whenever I try to use or modify one of your components, it doesn't work as expected. I'm not sure why this is happening. I've attached a screenshot below for your reference.
(Here:- I am using text-black to make text color black but its not working)
Expected behavior
We should be able to modify components to suit our needs.
Screenshots

Platform (please complete the following information):

Type: [Smart Phone]
OS: [iOS 18]

Hey @samarthasthan could you please provide a minimal reproduction repo and make sure it is using the latest version of NativeWind?

@mrzachnugent , Here is Link - https://github.com/samarthasthan/shadcn-react-native, please read the README file, i have mentioned the problems there.

@samarthasthan Your index file has a jsx extension. By switching the file name  to  index.tsx, it fixes your issue.

@mrzachnugent but why text above button is not rendering ?

@samarthasthan It's because of the flex-1 className in your <View className="flex-1 gap-3"> component at line 17. This is due to how styling is done in react-native. If you were to use the same styles using the StyleSheet instead of NativeWind, you would have the same issue.
As a solution, you can either add flex-1 to the SafeAreaView or remove it from the View mentioned above.

Facing same issue, it does not work at all, i am not understanding why its so in consistence and unpredictable.
import React from "react";
import { SafeAreaView } from "react-native-safe-area-context";
import { View, TouchableOpacity } from "react-native";
import { Text } from "~/components/ui/text";
import { Input } from "~/components/ui/input";
import { Button } from "~/components/ui/button";
import { Separator } from "~/components/ui/separator";

const SignInPage = () => {
  return (
    <SafeAreaView className="flex-1 justify-center px-4">
      <View className="items-center mb-6">
        <Text className="text-3xl font-bold">Instagram</Text>
      </View>
      <View className="space-y-4">
        <View>
          <Text className="mb-2">Email or Phone</Text>
          <Input placeholder="Email or Phone Number" />
        </View>

        <View>
          <Text className="mb-2">Password</Text>
          <Input placeholder="Password" secureTextEntry />
        </View>

        <TouchableOpacity className="self-end">
          <Text className="text-blue-500 mt-2">Forgot Password?</Text>
        </TouchableOpacity>

        <Button className="mt-4">
          <Text>Sign In</Text>
        </Button>
      </View>

      <View className="my-6">
        <Separator />
      </View>

      <View className="flex-row justify-center space-x-2">
        <Text>Don't have an account?</Text>
        <TouchableOpacity>
          <Text className="font-bold text-blue-500">Sign Up</Text>
        </TouchableOpacity>
      </View>
    </SafeAreaView>
  );
};

export default SignInPage;

@samarthasthan This is what I see when I copied your code in your reproduction repo:

What's missing?

authors: mrzachnugent samarthasthan

repo: mrzachnugent/react-native-reusables


text:
Question: Nested JSON and Dynamic Translation

Hi, Thanks for the nice library. Does it support Translation like the following?
{
    "LoginPage": {
        "title": "Authentication",
        "btnSignup": "Sign Up",
        "btnLogin": "Login"
    },
    "HomePage": {
        "title": "Welcome Home",
        "greeting": "Hi $name, how are you?" // Dynamic interpolation $name
    }
}

Not yet supported, contacted via email

authors: iambudi msayed-net


text:
Query: 32/64 bit support for Windows

Just a quick query.
Are both 32/64 bit versions of Windows support?
Cheers

Yes, both 32-bit and 64-bit Windows should work.

Great thanks,
I'm currently using nodejs and Azure so we are precompiling the dependency as only solution for working with this module on an Azure web app (app service) instance as they do not have the VS C++ build tools required.  Could be nice to document this particular requirement for Azure web apps as it may save some people time in the future.

authors: aaronpcz mscdex

repo: mscdex/mmmagic


text:
Not able to install coreferee

I am trying to install coreferee using commands mentioned in the documentation:
python3 -m pip install coreferee
python3 -m coreferee install en

but executing this is showing the following errors:
ERROR: Could not find a version that satisfies the requirement coreferee (from versions: none)
ERROR: No matching distribution found for coreferee
How to resolve this issue?

Duplicate of #2

authors: ansh-lehri richardpaulhudson

repo: msg-systems/coreferee