Azure service bus message renew_message_lock not working

Package Name:
azure-servicebus
Package Version:
7.12.2
Operating System:
Ubuntu
Python Version:
3.8

Describe the bug
I have a python service which uses azure service bus topic for sending and receiving messages. I am using azure-servicebus==7.12.2.
Max timeout I can set on azure portal is 5 minute, but the processing for the message on topic take around 60 minutes. So, I am using renew_message_lock to renew the message lock time
Here is my code
async def receive_messages_from_topic(
    servicebus_client: ServiceBusClient,
    topic_name: str,
    executor: Any,  # type: ignore
):
    async with servicebus_client:
        # renewer = AutoLockRenewer(max_lock_renewal_duration=3600)
        async with servicebus_client.get_subscription_receiver(
            topic_name=topic_name,
            subscription_name=SUBSCRIPTION_NAME,
        ) as receiver:
            logger.info(f"Listening to topic: {topic_name} for subscription: {SUBSCRIPTION_NAME}")
            while True:
                try:
                    messages = await receiver.receive_messages()
                    for message in messages:
                        _ = await receiver.renew_message_lock(message=message, timeout=21600)

                    for message in messages:
                        # Process the message
                        logger.info(
                            f"Received message from topic: {topic_name}, msg: {str(message)} message.locked_until_utc: {message.locked_until_utc} utc_now: {datetime.datetime.now(datetime.timezone.utc)}"
                        )

                        with make_temp_directory() as temp_dir:
                            try:
                                bytes_str = str(message)
                                bytes = ast.literal_eval(bytes_str)
                                executor(topic_name, bytes, temp_dir)
                                await receiver.complete_message(message)
                            except Exception as e:
                                logger.exception(
                                    f"Error executing job for topic: {topic_name} message: {message.message_id}, {e}"
                                )
                                await receiver.dead_letter_message(message)

                    if len(messages) == 0:
                        # Small sleep to avoid busy looping
                        await asyncio.sleep(60)
                except Exception as e:
                    logger.exception(f"Error processing message for topic: {topic_name}, {e}")

Log
2024-09-07 13:39:16,292 - __main__ - INFO - Received message from topic: dataset_deploy, msg: b'\n\x08foo\x12\x05fig' message.locked_until_utc: 2024-09-07 20:44:16.268000+00:00 utc_now: 2024-09-07 20:39:16.292080+00:00

executor(topic_name, bytes, temp_dir) will complete the processing in 40 minutes, no issues or errors. But, when I try to mark the message as complete in the above loop it will throw below exception
Traceback (most recent call last):
  File "/home/vscode/.cache/bazel/_bazel_vscode/d9fd8dd9485b3d1d1994c3846baefa35/execroot/_main/bazel-out/k8-opt-release/bin/tools/service_bus/run/run.runfiles/_main/tools/service_bus/run/run.py", line 72, in receive_messages_from_topic
    await receiver.complete_message(message)
  File "/home/vscode/.local/lib/python3.10/site-packages/azure/servicebus/aio/_servicebus_receiver_async.py", line 852, in complete_message
    await self._settle_message_with_retry(message, MESSAGE_COMPLETE)
  File "/home/vscode/.local/lib/python3.10/site-packages/azure/servicebus/aio/_servicebus_receiver_async.py", line 494, in _settle_message_with_retry
    raise MessageLockLostError(
azure.servicebus.exceptions.MessageLockLostError: The lock on the message lock has expired.

What I tried

I tried setting AutoLockRenewer on message and session still same result. https://azuresdkdocs.blob.core.windows.net/$web/python/azure-servicebus/latest/index.html#automatically-renew-message-or-session-locks

Not sure if I missing something or something is wrong with my implementation
To Reproduce
async def receive_messages_from_topic(
    servicebus_client: ServiceBusClient,
    topic_name: str,
    executor: Any,  # type: ignore
):
    async with servicebus_client:
        # renewer = AutoLockRenewer(max_lock_renewal_duration=3600)
        async with servicebus_client.get_subscription_receiver(
            topic_name=topic_name,
            subscription_name=SUBSCRIPTION_NAME,
        ) as receiver:
            logger.info(f"Listening to topic: {topic_name} for subscription: {SUBSCRIPTION_NAME}")
            while True:
                try:
                    messages = await receiver.receive_messages()
                    for message in messages:
                        _ = await receiver.renew_message_lock(message=message, timeout=600)

                    for message in messages:
                        # Process the message
                        logger.info(
                            f"Received message from topic: {topic_name}, msg: {str(message)} message.locked_until_utc: {message.locked_until_utc} utc_now: {datetime.datetime.now(datetime.timezone.utc)}"
                        )

                        with make_temp_directory() as temp_dir:
                            try:
                                bytes_str = str(message)
                                bytes = ast.literal_eval(bytes_str)
                                time.sleep(360)
                                await receiver.complete_message(message)
                            except Exception as e:
                                logger.exception(
                                    f"Error executing job for topic: {topic_name} message: {message.message_id}, {e}"
                                )
                                await receiver.dead_letter_message(message)

                    if len(messages) == 0:
                        # Small sleep to avoid busy looping
                        await asyncio.sleep(60)
                except Exception as e:
                    logger.exception(f"Error processing message for topic: {topic_name}, {e}")

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Hi @ShirishGajera ,
In this case simply calling renew_message_lock here is not going to work. It has to be called at some regular interval to make sure the lock is renewed before expiring.
In the first example
 messages = await receiver.receive_messages()
for message in messages:
    _ = await receiver.renew_message_lock(message=message, timeout=21600)

What happens here is that the messages are received and then iterated over one by one, renewing the lock on them exactly once. The timeout value here is not the timeout on the lock, its the timeout for the operation of renewing the lock. So at this point if your queue has a lock period of 5 mins, this call will extend it for another 5 mins.
The AutoLockRenewer is the functionality that will work here.  I think the reason why AutoLockRenewer is not working is because the call to the executor is a blocking call, preventing it from running in the background. If you change time.sleep(360) to await asyncio.sleep(360) in the repro code, youll see it working.

@kashifkhan moving executor to async worked with AutoLockRenewer. Thanks!!


added capability to handle fetch from public terraform registry

Hi everyone 👋 !
as asked by @nutellinoit , i implemented in furyctl the feature to customize the yaml in order to support also public terraform modules from terraform registry. It works, please review the code and ask for everything is you see some lacks or mistakes!

See: https://github.com/sighupio/fury-kubernetes-aws/issues/22

See: sighupio/fury-kubernetes-aws#22

Due to: https://github.com/sighupio/fury-kubernetes-aws/issues/22#issuecomment-581129931
We can continue with this PR. What is the state?

I guess is waiting to be merged

I guess is waiting to be merged

Ok, i take care of it ;) Thanks @lzecca78 !


CNCF Sanbox 提交探讨

[x]<EMAIL_ADDRESS>[x] 项目名称：Serverless Devs
[x] 项目描述：Serverless Devs 是一款基于云原生，开源开放的 Serverless 应用全生命周期管理工具，通过组件化建设，可以让开发者像玩手机一样玩转 Serverless 架构。通过 Serverless Devs 工具，开发者可以快速体验、使用包括 AWS Lambda、阿里云函数计算、百度智能云函数计算、华为云函数计算工作流、腾讯云云函数等在内的多家云厂商的 FaaS 服务，以及 OpenFunction 等开源 FaaS 能力；基于 Serverless Devs Model ，开发者可以通过更为一致的使用体验，快速进行多 FaaS 平台的 Serverless 应用初始化、打包构建、部署上线、后期运维等工作。Serverless Devs 将会持续关注 Serverless 开发者的幸福度，持续为 Serverless 开发者提供高效、简洁、开放的 Serverless 开发者工具。
[x] Repo 网址：https://github.com/Serverless-Devs/Serverless-Devs
[x] 项目 Roadmap（URL）：https://github.com/Serverless-Devs/Serverless-Devs/blob/master/ROADMAP.md
[x] 捐赠 CNCF 的动机，希望从 CNCF 获得什么:

Serverless 工具建设的必要性】：随着云计算的不断发展，云原生热度的不断提升，近些年来 Serverless 架构已逐渐地表现出了发展强劲的势头，一方面是被更多开发者所关注，另一方面市场采纳率也在稳步攀升。然而，云厂商和开源框架等所提供的 Serverless 服务无论从能力范围还是从产品形态、使用体验等方面来讲都是不尽相同的，这导致 Serverless 架构厂商绑定问题严重，不容忽视。在2020年10月中国信息通信研究院发布的国内首个《云原生用户调查报告》中，明确的表明了在使用Serverless 架构时约有24%的用户直接考虑工具链的完善情况，大于50%的用户间接关注到工具链的完善情况。这也充分说明了广大Serverless开发者对完善工具链的诉求和渴望。但是就目前来看，面向开发者的工具项目并不多，尤其是 Serverless 领域，所以我们希望可以通过 Serverless Devs 这个无厂商锁定，Serverless 应用全生命周期管理的工具，为这个领域做一些贡献，让更多的开发者不仅仅能用 Serverless 架构，而是可以“更快，更好，更方便“的使用 Serverless 架构。
-【让 Serverless 可以更普惠大众】：希望通过 CNCF 可以获得更多关于 Serverless 领域的合作机会与创新机会，以确保 Serverless Devs 社区可以不断的为开发者们提供更为便利、科学的 Serverless 应用全生命周期管理能力，为开发者提供感动且富有创造力的 Serverless 开发体验，以让 Serverless 技术可以更好、更快的普惠大众；
【建设长期、稳定且有创造力的 Serverless 开发者生态】：目前 Serverless 领域的开发者社区是比较少的，希望通过 CNCF 的号召力，可以和 Serverless Devs 一同创建活跃的，积极的 Serverless 开发者社区，并为更多的 Serverless 爱好者提供讨论、学习、创新的平台。希望通过 CNCF，可以得到更为科学、丰富的社区运营经验，以及更为丰富的社区运营资源，并希望以此进一步完善 Serverless 开发者社区生态；
【带领更多的中国开发者参与到 Serverless 社区生态的建设中】：我们希望可以通过 CNCF，带领更多中国开发者一起玩转 Serverless 架构，希望与 CNCF 一起努力，共建 CNCF Serverless China 的线下会议与活动。

[x] Code of conduct（URL）：https://github.com/Serverless-Devs/Serverless-Devs/blob/master/CODE_OF_CONDUCT.md
[x] 项目和云原生社区生态契合的点都有哪些：

Serverless 本身就是云原生的一个领域，或者说是一个方向，而 Serverless Devs 工具本身就是因 Serverless 而生，为 Serverkess 服务，并且成长在 Serverless 之上。无论是从 Serverless Devs 的社区合作关系出发，还是从 Serverless Devs 所肩负的使命出发，再或者是从 Serverless Devs 所呈现的形态出发，都可以认为是“Serverless Devs 就是云原生的一部分“，如果再进一步表述，可以这样说：Serverless Devs 因云原生而生，成长在云原生，为云原生项目服务，目前与云原生社区的关系包括不限于：

支持符合 CloudEvent 规范，Serverless Workflow 规范的组件；
支持诸多云原生项目相关的组件，包括不限于OpenFunctio、Kubevela、Kubernetes、Buildpacks等；

Serverless Devs 是 Serverless 领域的开发者工具，通过与更多的云原生项目进行联动可以为 Serverless 领域的开发者构建更为灵活、完善的 Serverless 应用全生命周期管理能力；与此同时，可以为更多开源 FaaS 产品提供规范、友好的工具侧使用体验。

通过 Serverless Devs 开发者工具，可以让云原生社区生态的很多产品产生联动：例如 Kubebela、Kubernetes、Buildpacks等项目与 Serverless 架构的联动，可以让 Serverless 开发者更简单、方便的上手 Serverless 架构，并以此快速的构建 Serverless 应用；
Serverless Devs 可以作为 FaaS 通用的工具链对这些项目进行工具层面的支持：例如对 OpenFunction 项目的支持等，以促进 Serverless 架构在用户体验层的一致性，提高更多的开源 FaaS 产品工具层的研发效能、用户体验。

已有的云原生社区生态开源项目契合点：

OpenFunction：OpenFunction 是一个开源的 FaaS 平台，目前已经进入 CNCF Sandbox。Serverless Devs 作为开源的 Serverless 工具链产品，目前已经得到 OpenFunction 社区的认可，并在社区的支持下，完成了 OpenFunction 与 Serverless Devs 的对接。在未来， Serverless Devs 将作为 OpenFunction 的工具链，为 OpenFunction 的开发者提供工具链支持；
Kubevela：Kubevela 是一个开源的，开箱即用、面向现代微服务架构的应用交付与管理平台，目前已经进入CNCF Sandbox。Serverless Devs 依赖 Kubevela 实现了 Serverless 多环境管理能力，通过 Kubevela 提供的资源管理，Serverless Devs 可以为开发者提供更为丰富和完整的 Serverless 使用体验，弥补部分 FaaS 平台对多环境划分能力不足的劣势；
Kubernetes：为提高 Serverless Devs 和其他云原生项目的可集成能力，Serverless Devs 推出 Serverless Devs Kubernetes Controller 组件，通过该面向Kubernetes 的控制面组件，可以让容器生态的用户更容易享受 Serverless 服务；
buildpacks：Serverless Devs 已支持容器镜像打包并部署到部分主流的 FaaS 平台。打包的过程，支持通过 Buildpacks 进行镜像的构建；
CloudEvent：Serverless Devs 目前通过组件层面已经支持部分符合 CloudEvent 规范的事件产品，例如部分云厂商的 EventBridge 等；
Serverless Workflow：Serverless Devs 目前通过组建层面已经支持部分符合 Serverless Workflow 规范的工作流项目，包括不限于工作流的创建、部署等。

[x] 是否有和你的项目类似的其他项目，有的请列出来：Serverless Framework，Stackery，Nocalhost
[x] 贡献者指南：https://github.com/Serverless-Devs/Serverless-Devs/blob/master/CONTRIBUTING.md

[x] Submitter's email address<EMAIL_ADDRESS>[x] Project name: Serverless Devs
[x] Project description: Serverless Devs is a cloud-native, open source serverless application full life cycle management tool. Through component construction, developers can play the serverless architecture like a mobile phone. Through Serverless Devs tools, developers can quickly experience and use FaaS services of many cloud vendors, including AWS Lambda, Alibaba Cloud Function Computing, Baidu Smart Cloud Function Computing, Huawei Cloud Function Computing Workflow, Tencent Cloud Function, etc., and Open source FaaS capabilities such as OpenFunction; based on the Serverless Devs Model, developers can quickly perform serverless application initialization, packaging and construction, deployment, and post-operation and maintenance of multiple FaaS platforms through a more consistent user experience. Serverless Devs will continue to pay attention to the happiness of serverless developers, and continue to provide efficient, concise and open serverless developer tools for serverless developers.
[x] Repo URL: https://github.com/Serverless-Devs/Serverless-Devs
[x] Project Roadmap (URL): https://github.com/Serverless-Devs/Serverless-Devs/projects?type=classic&query=
[x] Motivation for donating to CNCF, what to expect from CNCF:

Necessity of Serverless Tool Construction]: With the continuous development of cloud computing and the increasing popularity of cloud native, the serverless architecture has gradually shown a strong momentum of development in recent years. On the one hand, it has attracted the attention of more developers On the other hand, the market adoption rate is also rising steadily. However, the serverless services provided by cloud vendors and open source frameworks are not the same in terms of capability scope, product form, and user experience. This leads to a serious problem of serverless architecture vendor binding, which cannot be ignored. In the first "Cloud Native User Survey Report" released by the China Academy of Information and Communications Technology in October 2020, it clearly shows that about 24% of users directly consider the improvement of the tool chain when using the serverless
architecture, and more than 50% of users are indirectly concerned about the improvement of the tool chain. This also fully demonstrates the demand and desire of the majority of Serverless developers to improve the tool chain. But at present, there are not many tool projects for developers, especially in the serverless field, so we hope that we can make some contributions to this field through Serverless Devs, a tool for full life cycle management of serverless applications without vendor lock-in. More developers can not only use the serverless architecture, but can use the serverless architecture "faster, better, and more convenient".
-[Make Serverless more accessible to the public]: I hope that through CNCF, we can get more cooperation opportunities and innovation opportunities in the serverless field, so as to ensure that the Serverless Devs community can continue to provide developers with more convenient and scientific serverless applications. Life cycle management capabilities, providing developers with a touching and creative serverless development experience, so that serverless technology can benefit the public better and faster;
[Building a long-term, stable and creative serverless developer ecosystem]: At present, the developer community in the serverless field is relatively small. It is hoped that through the appeal of CNCF, we can create active and active serverless developers together with Serverless Devs. community, and provide a platform for more serverless enthusiasts to discuss, learn, and innovate. It is hoped that through CNCF, more scientific and rich community operation experience and richer community operation resources can be obtained, and it is hoped that this will further improve the serverless developer community ecology;
[Leading more Chinese developers to participate in the construction of the Serverless community ecosystem]: We hope that through CNCF, we can lead more Chinese developers to play with the Serverless architecture, and we hope to work together with CNCF to build the CNCF Serverless China line under Meetings and Events.

[x] Code of conduct (URL): https://github.com/Serverless-Devs/Serverless-Devs/blob/master/CODE_OF_CONDUCT.md
[x] What are the points of ecological compatibility between the project and the cloud native community:

Serverless itself is a field of cloud native, or a direction, and the Serverless Devs tool itself was born for Serverless, serves Serverkess, and grows on Serverless. Whether starting from the community partnership of Serverless Devs, starting from the mission of Serverless Devs, or starting from the form presented by Serverless Devs, it can be considered that "Serverless Devs are part of cloud native", if we go further To put it this way, it can be said as follows: Serverless Devs was born from cloud native, grew up in cloud native, and served cloud native projects. The current relationship with cloud native community includes but is not limited to:

Support components conforming to CloudEvent specification and Serverless Workflow specification;
Supports components related to many cloud native projects, including but not limited to OpenFunctio, Kubevela, Kubernetes, Buildpacks, etc.;

Serverless Devs is a developer tool in the serverless field. By linking with more cloud-native projects, it can build more flexible and complete serverless application lifecycle management capabilities for developers in the serverless field; Multiple open source FaaS products provide standardized and friendly tool-side experience.

Through the Serverless Devs developer tools, many products of the cloud native community ecosystem can be linked: For example, the linkage between Kubebela, Kubernetes, Buildpacks and other projects and the serverless architecture can make it easier and more convenient for serverless developers to get started with the serverless architecture, and use the This fast build serverless application;
Serverless Devs can be used as a common tool chain for FaaS to support these projects at the tool level: for example, support for the OpenFunction project, etc., to promote the consistency of the Serverless architecture in the user experience layer, and improve the development of more open source FaaS products at the tool layer performance, user experience.

Existing cloud native community ecological open source projects fit points:

OpenFunction: OpenFunction is an open source FaaS platform, which has now entered the CNCF Sandbox. As an open source serverless toolchain product, Serverless Devs has been recognized by the OpenFunction community, and with the support of the community, the connection between OpenFunction and Serverless Devs has been completed. In the future, Serverless Devs will serve as OpenFunction's toolchain, providing toolchain support for OpenFunction developers;
Kubevela: Kubevela is an open-source, out-of-the-box, application delivery and management platform for modern microservice architectures, which has now entered the CNCF Sandbox. Serverless Devs relies on Kubevela to achieve serverless multi-environment management capabilities. Through the resource management provided by Kubevela, Serverless Devs can provide developers with a richer and more complete serverless experience, making up for the disadvantage of some FaaS platforms that lack the ability to divide multiple environments;
Kubernetes: In order to improve the integration capabilities of Serverless Devs and other cloud-native projects, Serverless Devs has launched the Serverless Devs Kubernetes Controller component. This Kubernetes-oriented control plane component makes it easier for users of the container ecosystem to enjoy Serverless services;
buildpacks: Serverless Devs has supported container image packaging and deployment to some mainstream FaaS platforms. The packaging process supports image building through Buildpacks;
CloudEvent: Serverless Devs currently supports some event products that conform to the CloudEvent specification at the component level, such as EventBridge from some cloud vendors;
Serverless Workflow: Serverless Devs currently supports some workflow projects that conform to the Serverless Workflow specification through the component level, including but not limited to the creation and deployment of workflows.

[x] Are there other projects similar to yours, please list them: Serverless Framework
[x] Contributor guide: https://github.com/Serverless-Devs/Serverless-Devs/blob/master/CONTRIBUTING.md

补充相关资料：
THIS IS A RESUBMISSION AFTER FEEDBACK FROM Serverless WorkGroup：
We got a strong suppport from serverless group after we had our serverless devs introduced and demoed. Serverless Groups is really interested in our no vendor locked in tool chain and expecting us for further steps by offering developers from the group to anticipate our tool building.
More：
1: 2022/07/21: Community contributor Chelsea introduced Serverless Devs to Serverless Workgroup, and Serverless Workgroup said they would like to have a demo.[https://www.youtube.com/watch?v=LX-w6hwzd2o  20:52-41:35]
2: 2022/08/18:  Community contributor Chelsea show the Serverless Devs‘s demo to Serverless WorkGroup, and Serverless WorkGroup expressed their willingness to support the project and build Serverless Devs together.[xxxxxx xxx-xxxx]
Serverless Devs introduction PPT：https://drive.google.com/file/d/18xi0v638tdD5r6XDtH8229QH2gg4bcB8/view?usp=sharing

https://docs.google.com/document/d/1jpoKT12jf2jTf-2EJSAl4iTdA7Aoj_uiI19qIaECNFc/edit#heading=h.du7mbriwq3to


Log contract errors in 08-wasm

Summary
Some of the function calls in 08-wasm module omit the returned error. This makes it hard to understand what happened since it’s not easy to debug wasm contracts. The following function is an example but I’m willing to create a PR covering all cases.
During CheckForMisbehavior:
err should at least be logged here to make it easier.

Proposal
We can make sure that we are logging all errors returned from contract in all calls.

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged/assigned

Thanks for the issue, @aeryz. Much appreciated if you can also open a PR. 🙏
Is it urgent for you to have this released? I think we could pretty quickly tag a new patch release on v0.1.x (for both v7.3.x and v8.0.x). Please let us know!

Hey, thanks for quick response. We are not in a rush. I will create a PR soon :)

Just checking: @aeryz are you still able to open a PR for this issue?

Low hanging fruit, so I will take it!


pyGAM support python 3.8?

Dear pyGAM authors,
Thank you for the great library.
I found in the current documentation that it requires python >=3.6 (https://pypi.org/project/pygam/). Do you think python 3.8 will be supported as well?
Thank you in advance.

sorry for never responding!
i hope you tried it out for yourself!
currently pygam supports python 3.8 - 3.12


Angular JS 1.5 go to definition

Issue Type: Feature Request
Hi Team,
I working on a project in which we are using angulrjs version 1.5. The problem we are facing is that go to defination does not work on services that are injected to controller.
Would you please add this feature so that we can move to the service file by pressing ctrl + mouse.
Looking forward for your reply.
Thanks & Regards,
Shival
VS Code version: Code 1.23.1 (d0182c3417d225529c6d5ad24b7572815d0de9ac, 2018-05-10T17:11:17.614Z)
OS version: Windows_NT x64 6.1.7601

Please share some example code. Any angular specific features fall under the angular extension but it is unclear to me if this is an angular specific problem or a general js problem

Thanks Matt for your reply. The code is below.
angular.module('app').controller('searchEmployeeController', ['$scope', 'aclService','employeeService', 'commanService', 'CONFIG', '$filter', 'FileUploader',     function ($scope, aclService, employeeService, commanService, CONFIG, $filter, fileUploader) {      // Do things }....
Whenever I press ctrl + left mouse on commanService, it should open service 'commanService' which has been created in app.services.js .


Tiles for Automatic Collections are blank

Describe the bug
After I create a rule, the tiles in the Automatic Collections area are blank after the first time I view that page. They're fine the first time I am on the Collections page, but then any time I go back, they're all blank.
To Reproduce
Steps to reproduce the behavior:

Create rule.
Let collection get created.
View collection page. It'll look fine.
Leave page and come back any time later. Page will have blank tiles.

Expected behavior
Tile contents should be visible.
Screenshots

Device (please complete the following information):

OS: This is running in Docker
Version 2.1.2 but has been present for multiple versions of the service.

Additional context
This may be isolated to Safari on Desktop.
When I go into the inspector, if I disable the CSS
 .overflow-hidden {
/* overflow: hidden; */
}

on element <div class="z-1 absolute inset-0 flex flex-row overflow-hidden"> the tile contents are visible. There's still CSS issues with the text, but the contents are at least readable.
See attached screen shot:

This is strange behavior, and I haven't seen anyone else have this issue. When the tiles are blank, refreshing the page doesn't do anything?

Refreshing does not resolve the issue. Additionally, I forgot to add this looks to maybe be isolated to Safari on desktop. I haven't tested every browser though.

I am on Edge and haven't had the problem. I don't have the ability to test Safari on desktop.

If you know of a possible reason this could affect only Safari and need me to test any solutions, I'm happy to QA in some fashion.

I will see what I can find and let you know.

@macstainless What version of Safari are you using?

@macstainless What version of Safari are you using?
EDIT: I've reproduced on Safari 18

Sorry for the delay in responding. It's 17.3.1 but I see you have already coded a fix for this. THANK YOU!!!

:tada: This issue has been resolved in version 2.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


parameter srsname is missing  in .getfeature

To be more specific, WebFeatureService_2_0_0 is missing the srsname argument in the getfeature method. Is it missing by purpose?


Differences in PIPseeker official results?

I noticed in the PIPSeeker documentation there's now an ability to extract converted fastq reads, in the same sort of way your program does.
It would be optimal for my peace of mind if the two programs gave the same outputs.
You can test this by converting your example data to have the suffix .fastq.gz, for example with a soft link:
 example_R1.fastq.gz -> example_R1.fq.gz
Then run PipSeeker:
pipseeker barcode --fastq data/example_v3/. --output-path PIPseeker --chemistry v3
An R1 read from PIPSeeker:
@A01831:50:HCLHTDRX3:1:2101:16495:1000 1:N:0:TAAGGCGA
AGTACCGGCACGAAGTGGCGTCCGAACG
+
~~~~~~~~~~~~~~~~FFFFFFFFF:FF

An R1 read from your software (using your tutorial command to generate the data):
@A01831:50:HCLHTDRX3:1:2101:16495:1000 1:N:0:TAAGGCGA
AGAGGTGCACAGCAACAAAGACAAGTAGGGCGTCCGAACG
+
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF:FF```

You both agree on the UMI sequence, but your barcoded sequence is significantly longer than what PIPseeker emits.
AGTACCGGCACGAAGT GGCGTCCGAACG
AGAGGTGCACAGCAACAAAGACAAGTAG GGCGTCCGAACG

I have no idea what black voodoo magic they are performing to get to a 16bp barcode.

Hm that's interesting - I don't know how they would be able to get a 16bp barcode either considering the barcode lengths themselves are 8+6+6+8=28.
I guess the major question to answer is whether the number of unique cells changes between the two. If they don't maybe they just create a unique 16mer to be more compatible with existing software (i.e. you don't need to adjust the default technology flag for kallisto or salmon).

Hi all!
I was plagued with a similar problem, as to how we map from 28bp barcode generated by pipspeak, to the 16bp barcode generated by pipseeker. This was the response I received from their bioinformatics team:

Hi Zaki,

Within each tier, the barcode index is translated into a 4-base sequence:

0 ==> AAAA, 1 ==> AAAC, 2 ==> AAAG, 3 ==> AAAT, 4 ==> AACA, 5 ==> AACC, ..., 94 ==> CCTG, 95 ==> CCTT

The sequences from each of the 4 tiers are joined into a 16-base sequence.

That solved the problem for me.


NPE copying dashboard that user has read permission on

stroom.entity.server.EntityServiceCopyHandler.exec line 44
line 29

I can't replicate this

Seems to have gone away.


Different output in node vs in browser?

This may be more of a question than a bug report, but I can't find this in the docs. I'm precompiling my color manipulation so it doesn't bog runtime and I'm getting a different toString() output in node vs in browser.
new Color('#ffff33').to('hsl').toString()

Outputs strings color(hsl 60 100 60) in node and hsl(60 100% 60%) in browser. What's the intended way to get the CSS-accepted format in node?

Looks like for some reason spaces/hsl.js is not imported in Node so it falls back to the default output. Could you provide more details about how you are importing Color.js?

Thanks for the insane reply speed. I'm using it inside Vanilla Extract *.css.ts files (theme specifically) kind of like so (not actual implementation)
// theme.css.ts
import Color from 'colorjs.io'

export const styles = style({
   color: new Color('#ffff33').to('hsl').toString()
})

Wait, if HSL was not included at all, it wouldn't know how to do the conversion either. The plot thickens… Are you using the same version in both cases?

Yes, 0.4.1

Could I help here any further? Maybe a reproduction vite stack?

The less tooling that is needed to reproduce it, the better. E.g. can you reproduce it in plain Node? I have never used vanilla-extract or vite, so I'm not sure where to even start debugging this 😕
Oh, what happens if you call .toString({format: "hsl"})?

In 0.4.1 toString expects 0 arguments, but in 0.4.0 setting the format option did basically nothing, the resulting string was the same as without it.

Hmm, actually I can't reproduce it in pure node, the output is correct as hsl(60 100% 60%). Could be somehow related to Vanilla Extract which does some pre-compiling on the .css.ts files. I'll create some minimal environment where the problem is reproducible.

https://github.com/mystrdat/colorjs-vanilla-test
Barebones vite react-ts template just with vanilla-extract added. There are 2 logs, one in https://github.com/mystrdat/colorjs-vanilla-test/blob/master/src/App.css.ts which outputs color(hsl 60 100 60) in the terminal process (doesn't run in browser) a then one in https://github.com/mystrdat/colorjs-vanilla-test/blob/master/src/App.tsx which runs in browser and outputs hsl(60 100% 60%) correctly.
I'll see if I can reduce it further but given it works in node it does seems somehow related to https://vanilla-extract.style

Thank you so much for tracking this down!

@LeaVerou This seems to have some insight https://github.com/vanilla-extract-css/vanilla-extract/issues/899#issuecomment-1302592402

So to summarize, it seems that the gist of the issue is this bug that's overwriting  your processFormat function with the getPath function in esbuild, which was fixed in 0.12.17. Vite uses a recent version but Vanilla Extract is still on 0.11.*. Hopefully the authors will update soon. Case closed, thank you very much for your time Lea!


The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #78   +/-   ##
=======================================
  Coverage   10.69%   10.69%
=======================================
  Files           3        3
  Lines         374      374
=======================================
  Hits           40       40
  Misses        330      330
  Partials        4        4

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 038386e...a251cca. Read the comment docs.


Strange Connection issues - Raspberry Pi and Respeaker 4 Speaker Array

I'm trying to remotely connect to a raspberry pi running ODAS via a Linux computer. I've been fooling around with it for a while and can't work around the error

Sink hops: Cannot connect to server

Following the readme file in Odas_web, I have edited the odas configuration file on the pi to this:
`# Configuration file for ReSpeaker 4 Mic Array (a hat for Raspberry Pi)
version = "2.1";
Raw
raw:
{
fS = 16000;
hopSize = 128;
nBits = 32;
nChannels = 4;

# Input with raw signal from microphones
interface: {
    type = "soundcard";
    card = 1;
    device = 0;
}

}
Mapping
mapping:
{
map: (1, 2, 3, 4);

}
General
general:
{
epsilon = 1E-20;

size:
{
    hopSize = 128;
    frameSize = 256;
};

samplerate:
{
    mu = 16000;
    sigma2 = 0.01;
};

speedofsound:
{
    mu = 343.0;
    sigma2 = 25.0;
};

mics = (

    # Microphone 1
    {
        mu = ( -0.0405, +0.0000, +0.0000 );
        sigma2 = ( +0.000, +0.000, +0.000, +0.000, +0.000, +0.000, +0.000, +0.000, +0.000 );
        direction = ( +0.000, +0.000, +1.000 );
        angle = ( 80.0, 90.0 );
    },

    # Microphone 2
    {
        mu = ( +0.0000, +0.0405, +0.0000 );
        sigma2 = ( +0.000, +0.000, +0.000, +0.000, +0.000, +0.000, +0.000, +0.000, +0.000 );
        direction = ( +0.000, +0.000, +1.000 );
        angle = ( 80.0, 90.0 );
    },

    # Microphone 3
    {
        mu = ( +0.0405, +0.0000, +0.0000 );
        sigma2 = ( +0.000, +0.000, +0.000, +0.000, +0.000, +0.000, +0.000, +0.000, +0.000 );
        direction = ( +0.000, +0.000, +1.000 );
        angle = ( 80.0, 90.0 );
    },

    # Microphone 4
    {
        mu = ( +0.0000, -0.0405, +0.0000 );
        sigma2 = ( +0.000, +0.000, +0.000, +0.000, +0.000, +0.000, +0.000, +0.000, +0.000 );
        direction = ( +0.000, +0.000, +1.000 );
        angle = ( 80.0, 90.0 );
    }

);

# Spatial filters to include only a range of direction if required
# (may be useful to remove false detections from the floor, or
# limit the space search to a restricted region)
spatialfilters = (

    {

        direction = ( +0.000, +0.000, +1.000 );
        angle = (80.0, 90.0);

    }

);

nThetas = 181;
gainMin = 0.25;

};
Stationnary noise estimation
sne:
{
b = 3;
alphaS = 0.1;
L = 150;
delta = 3.0;
alphaD = 0.1;

}
Sound Source Localization
ssl:
{
nPots = 4;
nMatches = 10;
probMin = 0.5;
nRefinedLevels = 1;
interpRate = 4;

# Number of scans: level is the resolution of the sphere
# and delta is the size of the maximum sliding window
# (delta = -1 means the size is automatically computed)
scans = (
    { level = 2; delta = -1; },
    { level = 4; delta = -1; }
);

# Output to export potential sources
potential: {

    # format = "undefined";
    format = "json";

    interface: {
        # type = "blackhole";

        type = "socket"; ip = "<CORRECT IP>"; port = 9001;
    };
};

};
Sound Source Tracking
sst:
{
# Mode is either "kalman" or "particle"

mode = "kalman";

# Add is either "static" or "dynamic"

add = "dynamic";

# Parameters used by both the Kalman and particle filter

active = (
    { weight = 1.0; mu = 0.3; sigma2 = 0.0025 }
);

inactive = (
    { weight = 1.0; mu = 0.15; sigma2 = 0.0025 }
);

sigmaR2_prob = 0.0025;
sigmaR2_active = 0.0225;
sigmaR2_target = 0.0025;
Pfalse = 0.1;
Pnew = 0.1;
Ptrack = 0.8;

theta_new = 0.9;
N_prob = 5;
theta_prob = 0.8;
N_inactive = ( 150, 200, 250, 250 );
theta_inactive = 0.9;

# Parameters used by the Kalman filter only

kalman: {

    sigmaQ = 0.001;

};

# Parameters used by the particle filter only

particle: {

    nParticles = 1000;
    st_alpha = 2.0;
    st_beta = 0.04;
    st_ratio = 0.5;
    ve_alpha = 0.05;
    ve_beta = 0.2;
    ve_ratio = 0.3;
    ac_alpha = 0.5;
    ac_beta = 0.2;
    ac_ratio = 0.2;
    Nmin = 0.7;

};

target: ();

# Output to export tracked sources
tracked: {

    # format = "undefined";
    format = "json";

    interface: {
        # type = "blackhole";
        type = "socket"; ip = "<CORRECT IP"; port = 9000;
    };

};

}
sss:
{
# Mode is either "dds", "dgss" or "dmvdr"

mode_sep = "dds";
mode_pf = "ms";

gain_sep = 1.0;
gain_pf = 10.0;

dds: {

};

dgss: {

    mu = 0.01;
    lambda = 0.5;

};

dmvdr: {

};

ms: {

    alphaPmin = 0.07;
    eta = 0.5;
    alphaZ = 0.8;
    thetaWin = 0.3;
    alphaWin = 0.3;
    maxAbsenceProb = 0.9;
    Gmin = 0.01;
    winSizeLocal = 3;
    winSizeGlobal = 23;
    winSizeFrame = 256;

};

ss: {

    Gmin = 0.01;
    Gmid = 0.9;
    Gslope = 10.0;

}

separated: {

    fS = 44100;
    hopSize = 512;
    nBits = 16;

    interface: {
        type = "socket";
        ip = "<INCORRECT IP>";
        port = 10000;
    }

};

postfiltered: {

    fS = 44100;
    hopSize = 512;
    nBits = 16;

    interface: {
        type = "socket";
        ip = "<INCORRECT IP>";
        port = 10010;
    }

};

}
classify:
{
frameSize = 1024;
winSize = 3;
tauMin = 32;
tauMax = 200;
deltaTauMax = 7;
alpha = 0.3;
gamma = 0.05;
phiMin = 0.15;
r0 = 0.2;

category: {

    format = "undefined";

    interface: {
        type = "blackhole";
    }

}

}`
The ODAS studio on the Linux computer does show live data for roughly 2 seconds, after that the "Sink hops" error occurs. If you look closely at the code, I have 2 different IP addresses. The 2 IP's under SSS are incorrect for my computer while the first 2 IP's are the correct one. Don't ask me how I stumbled upon this, but that is the only way to get it read any data! If I have all IP's set to the correct address, the "Sink Hops" error immediately occurs and no data comes through on the desktop.
I'm not sure what to do next and I'm generally just bewildered at why putting the wrong IP address works better than the correct one. Any help is appreciated, thank you!

Okay I got it going. Turns out I only need to try and push SSL and SST through TCP, so I kept the IP address there and used the defaults under the SSS configurations. For example:
type = "file" path = "postfiltered.raw"
Now it's working, but I hit errors after running it for a few minutes. The error is reading
Segmentation Fault
Will keep working on it.

Hi, what you experience is ODAS not able to sink the audio streams to ODAS Studio (odas_web).
With the correct IP, ODAS immediately connects to the Studio and raise the "cannot sink hops" error. With the incorrect IP, the timeout while the audio sockets attempt to connect allow the data sockets to stream for a few seconds before the error occurs. That's why using the wrong address seems to "fix" the problem.
Looking at your configuration file I would first make sure you configure ODAS Studio to use de 44100 Hz you set as an audio sink frequency as ODAS Studio is configured for 16000 Hz by default. You could also change your sink frequency to 16000 Hz.
The default file interface saves the audio as files on the machine running ODAS, in this case, the Pi. If you are ok with no audio stream, you can set the interface to blackhole and the type to undefined, like the classify output. This will suppress the audio streams.
For the segmentation fault error, it's pretty hard to investigate, more so if it occurs after a few minutes. The ODAS repository will be more helpful for that one.


[Docs] New Page for Visualizer Views

Notes for Reviewers
This PR fixes #
Signed commits

[x] Yes, I signed my commits.

Looks good so far. 😉

@nwanduka Let'd discuss this on websites call. Add this as an agenda item to the meeting minutes, if you would :)

@nwanduka, can you expand the content? It's nice to explain what you can do with Views. Can we also mention how to do it? For example, how you can export views.

@nwanduka, can you expand the content? It's nice to explain what you can do with Views. Can we also mention how to do it? For example, how you can export views.

Done @iArchitSharma. How is it now?

Awesome @nwanduka
can you please do same for other things in managing views

@iArchitSharma I made a few changes. I'm facing some issues with the screenshots. They load in the markdown preview but not in the netlify preview. I can't figure out why but I think you can. Please review.

@nwanduka
See the format here :

Done @iArchitSharma


[WIP] Use 7.3.2 workflow

Description
Test use of workflow 7.3.2 to see if we can retry Cosmos DB Install.

Codecov Report

Merging #51 (3ffcb46) into main (5bf0c3b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #51   +/-   ##
=======================================
  Coverage   78.34%   78.34%
=======================================
  Files          48       48
  Lines        1025     1025
  Branches       81       81
=======================================
  Hits          803      803
  Misses        185      185
  Partials       37       37

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Use larger passives where space isn't an issue

When I was hand soldering this board, some passives were wayyy smaller than necessary. Larger sizes should be used where space isn't an issue.

Fixed with bf71a19349987ac357deccb69c8306bc20f59892 and d522288d2d880606d3754e8809d97bedbc7955e7


Integrate other databases

Currently, this only ranks through PUBCHEM's API. It would be nice to use other APIs to rank compounds. Then probably rename this project too. We would have to discuss how other databases are implemented. I.e. simply rank by the total number of "hits" across all databases, or allow filtering of search parameters, who knows. Probably the algorithm needs to be a bit more complex to get an accurate indication of the amount of data available for each compound in the dataset
Other databases (please add):

Google scholar (would have to pay a little bit)
Scifinder (don't think it's possible)
WikiData
Brenda (http://www.brenda-enzymes.org/)
KEGG (although Pubchem already uses KEGG)
HMDB
WikiPathways
ChEBI (https://www.ebi.ac.uk/chebi/)

Some more databases:

http://hmpdacc.org/resources/osdf-query.php
http://www.homd.org/
https://docs.figshare.com/api/
http://kbase.us/metabolic-modeling-in-kbase/
http://wikipathways.org

And can use this one to get SMILES from IUPAC

After some preliminary research it seems MetaCyc is the easiest to add since they have a REST API. They even have a nice service to search for foreign keys (e.g. PubChem or KEGG), see here.
However, the only issue is that you have to search on an organism specific basis. The url to search is something like:
http://websvc.biocyc.org/[ORGID]/foreignid?ids=[DATABASE-NAME]:[FOREIGNID]

Where ORGID is the organism ID.
@DeniseSl22 Is it okay to make the ranker only usable for human datasets for now? It should be easy to add other organisms in the future. However, bare in mind that the more databases are added, the harder it will be to keep the organism restriction broad since some databases may support fewer organisms.

Yeah sure. Is PubChem then searched for humans only as well?
Perhaps we can add a option in the future where people can say which organism they want to filter on ;)

Oh btw; Egon just told me there is a new service (I will get the details through mail) which allows automated search through articles (for a lot of publishers, not Elsevier). Perhaps we can do something with that as well (I remembered you told me that a specific search through literature was really missing when you guys were looking at the VOCs dataset)

Here the info from Egon:
CrossRef API (citation counts): https://github.com/CrossRef/rest-api-doc/blob/master/rest_api.md
EuroPubMedCentral API: http://europepmc.org/RestfulWebService#cites
Initiative for Open Citations: https://i4oc.org/

Hmm cool! CrossRef I guess is the most well known so can integrate that first.

Using MetaCyc, the flow is:

Get the MetaCyc ID using the PubChem ID with `https://metacyc.org/META/foreignid?ids=PUBCHEM:&fmt=json
Retrieve the set of MetaCyc objects concerning that compound with http://websvc.biocyc.org/apixml?fn=[API-FUNCTION]&id=[ORGID]:[OBJECT-ID]&detail=[none|low|full]

The second step is what is needed to be discussed. What information do we actually want to retrieve from MetaCyc? If you see here, there is quite a lot we can do.
The obvious ones are:

pathways-of-compound
reactions-of-compound

But, these may also be interesting:

all-products-of-gene
substrates-of-reaction

@egonw and @deniseSl22 could you provide some input?

I would go to number of pathways and number of substrates...

Hi Jacob,
Just found some info on the ChEBI website that they have an API....
Perhaps useful to add this to the Ranker Program?
https://www.ebi.ac.uk/chebi/libchebi.do

Oh wow! How did I not see that?
For my reference: here's the API library for Python

?Yeah I am a awesome googler :p
Kind regards,
Denise Slenter MSc
UNS50 H1.302
T: +316-50585586

From: Jacob Windsor<EMAIL_ADDRESS>Sent: Tuesday, May 16, 2017 11:25
To: jacobwindsor/pubchem-ranker
Cc: Slenter Denise (BIGCAT); Mention
Subject: Re: [jacobwindsor/pubchem-ranker] Integrate other databases (#6)
Oh wow! How did I not see that?
For my reference: here's the API library for Pythonhttps://github.com/libChEBI/libChEBIpy

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/jacobwindsor/pubchem-ranker/issues/6#issuecomment-301726125, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AZD3yJtY7r2-TyRShp0SX3Cx0okuCjHEks5r6WuDgaJpZM4Maj8J.

Oh and another one I can across (HMDB API):
https://github.com/mzmine/mzmine2/issues/195
I think you didn't look at this, cause Egon already checked if the compounds were in HMBD and ChEBI (which a lot f them weren't). SO, this could help other people to find which compounds they do not have to investigate any further :)


Add credit/tagline

Hey guys,
It would be great to add an infographic credits tag for the WebCR. See FK IEA

@superjai, I'm going to assign this to you for the time being. LMK if you want to discuss further.

Just an idea
•Artwork

Amanda Dillon

•Technical implementation

Ben Best
Jen Brown
Jai Raganathan
Pike Spector

•Tools

onmsR
infographiqR
etc

•Additional support

Jenny Waddell
Katie Wrubel


Tap on datepicker closes it on mobile devices

First of all thanks a lot for this nice library!
Describe the bug
When i'm trying to tap on some date on my phone datepicker closes and date didn't choose.
To Reproduce
Steps to reproduce the behavior:

Open page with datepicker on mobile device.
Tap on trigger-element.
Tap on some date.
Issue is reproduced.

Expected behavior
Date choses and if it's needed to be user can choose end date.
Additional context
Add any other context about the problem here.

Hi, Hope you are doing well
I am also facing the same issue in date range selector. Did you find any solution for that.
Thanks in Advance


⚠ Fetchers has degraded performance

In cd9eb25, Fetchers ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 307 ms

Resolved: Fetchers performance has improved in 2902422.


Need to customize userDataDir

Instead of hard coded .profile, I need:
carlo.launch({
  userDataDir: 'path/to/customDir'
})

I can create a PR if needed.

(Note: not a maintainer, new to this project.) I didn't understand what this request was about, reading it. I did some looking through the code. I found https://github.com/GoogleChromeLabs/carlo/blob/c3fa0ab717dd12efd146779e7f65712b42f9fbc9/lib/carlo.js#L188 which I think might be what this issue is about.
I agree it would be cool/great/maybe-necssary-sometimes to allow using different browser profiles.

@rektide I made a markdown previewer with carlo(https://github.com/djyde/koy). Now every time users run this command, a .profile will be created at cwd, which is not my expect.

Fixed in https://github.com/GoogleChromeLabs/carlo/commit/8435636d3a2a2d1a5f1023fcd2b3e3e3ac8dcb92

I can create a PR if needed.

Ah, I should have said yes, missed it.


should extract for RheoFreqData take a FreqDataType

At the moment, extract for RheoTimeData types needs a TimeDataType argument which makes sense because you might want to extract time, or time and stress, or time and strain.
However, extract for RheoFreqData types always just extracts the frequency vector as it doesn't make any sense to ever have Gp without Gpp and vice versa.
So when using extract for RheoFreqData, the second argument of FreqDataType is completely redundant.
I can think of a few options:

We keep behavior as it is

Remove second argument for RheoFreqData types

Rename the RheoFreqData method extractfrequency or something more specialised so it is clear from the function name what it does, and remove the redundant second argument.

Hi Louis,
I agree that this is odd. We treated the frec data as we did with time
data, but they are fundamentally different.
We probably still need a function to extract the freq vector as a new
RheoFreqData. We may also need a new generator function to create Gp and
Gpp from omega. Not sure if this exists.
I am happy with renaming the function extractfrequency. Maybe we should
then rename the other ones extracttime, extractstrain (t & epsilon) and
extractstress (t & sigma).
On Sun, 21 Jul 2019 at 17:04, Louis Kaplan<EMAIL_ADDRESS>wrote:

At the moment, extract for RheoTimeData types needs a TimeDataType
argument which makes sense because you might want to extract time, or time
and stress, or time and strain.
However, extract for RheoFreqData types always just extracts the
frequency vector as it doesn't make any sense to ever have Gp without Gpp
and vice versa.
So the second argument of FreqDataType is completely redundant.
I can think of a few options:

We keep behavior as it is, though I think it is a bit strange
Remove second argument for RheoFreqData types, which might also be a
little strange
Rename the RheoFreqData method extractfrequency or something more
specialised so it is clear from the function name what it does, and remove
the redundant second argument.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/JuliaRheology/RHEOS.jl/issues/23?email_source=notifications&email_token=AA6B24XTZMCVSTBK2WLWH23QASCIVA5CNFSM4IFSY4X2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HAPZQPQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6B24Q3WQ4RUR44UR5TRR3QASCIVANCNFSM4IFSY4XQ
.

I'm wondering if it would not be simpler to rename all extract functions for consistency:
extracttime
extractstrain
extractstress
extractfreq

I think it would make the code cleaner and simpler to read for the user, and for us. Most of the code of the extract function is spent working out which parameter to extract.
Note: these functions are currently defined in processing.jl

Sounds good to me!

The functions extract are still there to avoid breaking changes, but now deprecated. To be removed with version 1.0.

Need to include new functions in API


[USMON-1190] go detection

What does this PR do?
Add privileged detector to support golang detection.

Motivation
Covering golang binaries

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Dotnet core sdk installation on Ubuntu 18.04

Problem encountered on https://dotnet.microsoft.com/download/linux-package-manager/ubuntu18-04/sdk-2.1.300
Operating System: Linux Ubuntu 18.04 - x64
Provide details about the problem you are experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

sudo apt-get update
E: Malformed entry 1 in list file /etc/apt/sources.list.d/dotnetdev.list (URI)
E: The list of sources could not be read.

What are the contents of that file? As the error states, the file does not have the correct format.

Closing due to inactivity. @gnraju20411 feel free to reopen if you have more info, we will be happy to help.


chrony: use correct allow pattern

Description
1.2.3 version introduced a bug.
Chrony allow list is generated as:
allow allow SERVER

it should be
allow SERVER

This makes newer chrony daemons to fail.

Thanks @Seitanas ! 🚀


Redundant Promise usage

Promise callback actually has no effect because it has been executing in-place synchronously.
https://github.com/reactivestack/cookies/blob/4d12ae55e91a04d958b9c17f94ba152c951730a3/packages/universal-cookie/src/Cookies.ts#L21-L23
If it intended to be executed asynchronously, it should be rewritten like
 Promise.resolve().then(() => {
   this.HAS_DOCUMENT_COOKIE = hasDocumentCookie();
 });

or unwrapped at all.

Promise has been removed


Array pack u directive

Added support for the u/U directives for Array#pack (#195):

u -> uu-encoding of a string (https://en.wikipedia.org/wiki/Uuencoding)
U -> UTF-8 encoding of a number

There is quite a bit going on in here :)

I've simplified the index tracking in StringHandler as in fact only a single index was needed to begin with
Now be_computed_by expands the subject if it contains args to be passed to the method to test (an example of this can be found in the u spec ;) )
Added an IntegerHandler that only currently supports the U directive
Packer now returns a StringValue instead of a String so directives can now change the encoding (both u and U do, but u uses an ASCII encoding we do not support yet)
When parsing tokens we now skip the count modifier of a directive if it is a zero byte (MRI does too, but it's only present in a subset of specs we did not work on until now, I found that rather funny and there's definitely lots of improvements we could eventually bring to ruby/spec :^) )

Nice! I like your refactoring too. 😍


Doesn't work when launched from termite/sterminal

The theme does not display and fonts do not load. Furthermore, I get an error message when invoking fontviewer -h:
> fontviewer -h
application-specific initialization failed: Command-specific options:
(help message printed here)
Error in startup script: Command-specific options:
(help message printed here)
"load /usr/lib/libtk8.6.so Tk"
    ("package ifneeded Tk 8.6.8" script)
    invoked from within
"package require Tk 8.5"
    (file "/usr/bin/fontviewer" line 63)```

Thanks for the report, I will look into it.

I may be mislead but can it be there is no -h flag, so it simply can't be executed?
plain fontviewer works for me at least (manjaro, built from AUR)


Asses security scope of dynamics

Describe the issue
A clear and concise description of what you want to happen.
Which Sprint Priority is this issue related to?
The 'Milestone' should clearly list Sprint Priorities - which one is this issue related to?
Additional context
Add any other context, attachments or screenshots
Definition of done
Identify what will need to happen/be delivered for this to be completely done

waiting for access to BCGov's test instance


keycloak-backend plugin: Config Loader issue on Backstage v1.17

Describe the bug
Keycloak config schema is considered invalid on Backstage version 1.17
To Reproduce
Steps to reproduce the behavior:

Create and backstage 1.17 instance or upgrade an existing one
Configure the Keycloak plugin as the Readme file says
Start the backstage instance
See error

...
[1] Backend failed to start up Error: Invalid configuration schema in<EMAIL_ADDRESS>additional symbol definitions are not allowed, found 'KeycloakOrg'
...

Expected behavior
Backstage instance started without errors and plugin working as expected
Additional context
Backstage Config Loader CHANGELOG.

I asked for clarification on "illegal types" in their Discord.


Issue while creating exe using cx_freeze with error throwing up in scipy.sparse.csgraph._shortest_path

My issue is about ...
Reproducing code example:

Sample code to reproduce the problem

Error message:

Traceback (most recent call last):
 File "C:\ProgramData\Anaconda3\lib\site-packages\cx_Freeze\initscripts\__startup__.py", line 14, in run
    module.run()
  File "C:\ProgramData\Anaconda3\lib\site-packages\cx_Freeze\initscripts\Console.py", line 26, in run
    exec(code, m.__dict__)
  File "test.py", line 43, in <module>
  File "C:\ProgramData\Anaconda3\lib\site-packages\sklearn\__init__.py", line 134, in <module>
    from .base import clone
  File "C:\ProgramData\Anaconda3\lib\site-packages\sklearn\base.py", line 11, in <module>
    from scipy import sparse
  File "C:\ProgramData\Anaconda3\lib\site-packages\scipy\sparse\__init__.py", line 241, in <module>
    from .csgraph import cs_graph_components
  File "C:\ProgramData\Anaconda3\lib\site-packages\scipy\sparse\csgraph\__init__.py", line 167, in <module>
    from ._shortest_path import shortest_path, floyd_warshall, dijkstra,\
ImportError: cannot import name 'shortest_path'

### Scipy/Numpy/Python version information:
<!-- You can simply run the following and paste the result in a code block

import sys, scipy, numpy; print(scipy.version, numpy.version, sys.version_info)
0.19.1 1.15.1 sys.version_info(major=3, minor=6, micro=5, releaselevel='final', serial=0)
-->

@vmadhukumar you will need to give us some more info. can you produce a self-contained example to reproduce this issue?

If you can do the imports in a normal interpreter then this will point to an issue with cx_freeze itself.
I'm pretty sure this will be an issue with a cx_freeze recipe for scipy, you possibly need to specify it in include_files. I have no problems using pyinstaller with scipy.
If you get a similar issue running code from the interpreter please feel free to reopen this issue.


check Makefile now that we use ruff

In #268, @juanitorduz brought in use of ruff for formatting and linting.
I'm wondering if we need to make any edits here in the listing related parts of the Makefile
https://github.com/pymc-labs/CausalPy/blob/2169bf0b310c29187c957bd128c8774a46ab5138/Makefile#L6-L18

@drbenvincent I went through the PR steps and the makefile also need to be updated.
I have started to have a look, I will raise a PR soon!

Fantastic @jsakv :)

@jsakv we have one something similar for PyMC Marketing https://github.com/pymc-labs/pymc-marketing/pull/438 :)


Update and rename env.sample to .env

I don't think you wanted to publish this change. You should invalidate your secret key on openai.
Also, the secret key should not have the '<<' '>>' surrounding it - that is part of the placeholder that should be replaced.


New directory structure for Records

Change PCAPI high-level /records/ REST call to use a new directory structure underneath. In the new structure the records will be grouped by survey id.
Example
/records/local/UUID/Name used to translate to /fs/local/UUID/records/NAME/records.json but now it should translate to /fs/local/UUID/records/SID/NAME/record.json instead.
The new structure is better suited to COBWEB's survey-based structure and security system and is crucial for enabling scalablility and overcoming namespace pollution in records of different surveys.
This change will break compatibility in FTOpen as::

/records/ will require the SID as an extra parameter.
FTOpen might already be using low level /fs/ calls for record access that will need to be rewritten to use /records/

This issue is a spin-off of cobweb-eu/cobweb#166

The change for the app is in the cobweb-pcapi-43 branch of the sync plugin, but untested.  I will test it once it is available in the pcapi.


couldn't add home bridge

updated to macOS Mojave and opened the new Home app on my iMac and is showed all of the accessories connected to home bridge and not accessible.  verified with IOS app had same condition
I removed the bridge from home app.
I stopped the Homebridge service on my RPI
I deleted persist and accessories directory
I restarted the Homebridge service on my RPI
I re-added to the device and keyed in the setup code and the Homebridge showed up in the Home app
I selected the Homebridge to be added, responded add anyway to the "Uncertified Accessory", it started to add and then indicated that it couldn't add Homebridge - The setup code is incorrect.
I tried several times reentering the code with the exact same result.
Please help if you have any ideas on how to fix this

Problem resolved, Operator Error.  All is well.


VRAM requirements for training

Thanks for sharing your work. Can you provide the VRAM requirements for each type of training (full, vision only, LLM only)?

It doesn't support gradient checkpointing and other techniques so it takes more than it takes more than 96 GB. So I couldn't really test it for now.

2x 80GB as far as I've observed, anything less, not so much.


Forcibly disable vsync on Wayland to prevent crash

This commit fixes a crash on Wayland with the following error message
thread 'main' panicked at 'Could not create glutin window.: NoAvailablePixelFormat', src/main.rs:251:14

by forcibly disabling vsync on Wayland.

Just noticed there are issues with this PR I will make a new one when I solve them


[Enhancement]: add manual patch from pc

Describe the new feature or enhancement
With the new v63 update you can't acces the android data and obb folder, so why not make a manual patch from pc if everything is moved to java? (Sorry for my bad English, i am italian)

yes please do this.

agreed if possible

pls

Being done with the new installer.


Avoid copying in DefaultHttp2RemoteFlowController

We should identify all of the places in the flow controller that we're copying and try to eliminate/reduce the total amount of copying for each call to writePendingStreams writePendingBytes.

@nmittler - Thanks for filing this!

I'll take a stab at this after https://github.com/netty/netty/pull/3549 is pulled in.

We should also investigate if maintaining a separate collection for the streams that have bytes allocated is worth it.  For example if the number of streams that have bytes allocated is small relative to the total number of active stream it may be beneficial to maintain a separate set that tracks which streams have allocations.

+1

@Scottmitch were you going to look into this or shall I?

@nmittler - I updated the issue description to writePendingBytes.  I have a PR pending approval which avoids the copy operation and also prevents concurrent modification.  Stay tuned :)

@nmittler - I have not investigated if creating a separate collection which includes only the nodes that need writing is beneficial...but lets handle that after we avoid the copy.

@Scottmitch sgtm, thanks!

Closing.  Should be covered by https://github.com/netty/netty/pull/3577.

@Scottmitch there is still this copy that we may want to think about. If we decide it's necessary, that's fine.

@nmittler +1.  I thought about that briefly....now that we are not sorting it may be more feasible to remove.  The only hangup is how we are using this array to "re-visit" children that still want to send....we could maintain an alternative collection for this type of thing....but may make the loop a bit more complicated to handover to a secondary collection after the first iteration....WDYT?

@Scottmitch Yeah I was thinking something similar ... let me take a crack at this.

Remaining copy resolved by #3603.


Create initial survey

Ques

Gabs to organise the questions in either a spreadsheet or a survey, and send along to DPCs or coordinate with Dusica.


Alternatives to SMTP... too?

As previously discussed in Facebook comments [1, 2], SMTP setup with Gmail could be complicated and less secure.
Other solutions like Pushbullet, Telegram Bot, or IFTTT webhook could be considered as an alternative to this. All of them only require a single HTTPS request to deliver a message, and is relatively user friendly to set up. Personally I'm using Telegram Bot for different kinds of push notifications.

You're right. I'll think about this some more.
P.S. As far as you are aware, is there anything in particular that is problematic about the SMTP logic causing the Gmail authentication problems?

Would definitely like to take a look into that if I don't have AI exam next week. 😂

@matomatical
I've added some alternative notification methods to it. Please have a look if you have time.

Thanks, I'm looking forward to taking a close look when I get a chance!

Finished by #7, #9 and #10.


The training problem in "trj"

I don’t know what train data is used here when I’m in the TRJ step?
How is it obtained?
Whether the val data used in the TRJ step is the mapping_result obtained from the mapping step?

The train data consists of two parts, estimated map and gt trj. After you train the unc map models, you use it to evaluate the train data. This will be the training data (map part) for the TRJ step.
Here shows the merging process of estimated map data and trj data. This needs to be run for different splits: train, val, mini_train, mini_val etc.
The mapping_results here is more like a placeholder name, it can be mapping_results from evaluating on the train data, or it can be mapping_results from evaluating on the val data, depending on which split you want to generate. You should run this step for a minimum of two times (i.e. to generate the train and val data). So yes, the val data used in the TRJ step is the mapping_result obtained from the mapping step by evaluating on val, the train data used in the TRJ step is the mapping_result obtained from the mapping step by evaluating on train.

The train data consists of two parts, estimated map and gt trj. After you train the unc map models, you use it to evaluate the train data. This will be the training data (map part) for the TRJ step.
Here shows the merging process of estimated map data and trj data. This needs to be run for different splits: train, val, mini_train, mini_val etc.
The mapping_results here is more like a placeholder name, it can be mapping_results from evaluating on the train data, or it can be mapping_results from evaluating on the val data, depending on which split you want to generate. You should run this step for a minimum of two times (i.e. to generate the train and val data). So yes, the val data used in the TRJ step is the mapping_result obtained from the mapping step by evaluating on val, the train data used in the TRJ step is the mapping_result obtained from the mapping step by evaluating on train.

Thank you for your outstanding work and your reply. Your response is exactly the answer I need to verify. I have already been trying to do this. Thank you so much!

No problem, thank you for pointing this out👍. I will try to update it later after CVPR


Fix react peerDependency for @mui/styles

@mui/styles is not compatible with React 18, see https://mui.com/system/styles/basics/

@mnajdova , then can be removed 18 version from react/types? Because it's looks as mistake

@vadimka123 that's a good catch, I didn't see it. @michaldudak what was the reasoning for changing this? This package is not compatible with React 18.

This was likely a mistake. We can remove these React 18 types.


[Bug]: RAM OOM Error Loading 480GB MoE Model Despite Fix in PR #1395

Your current environment
PyTorch version: 2.1.2+cu121
Is debug build: False
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A
OS: Ubuntu 22.04.3 LTS (x86_64)
GCC version: (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Clang version: 14.0.0-1ubuntu1.1
CMake version: version 3.26.2
Libc version: glibc-2.35
Python version: 3.9.18 (main, Sep 11 2023, 13:41:44)  [GCC 11.2.0] (64-bit runtime)
Python platform: Linux-5.4.119-19-0009.11-x86_64-with-glibc2.35
Is CUDA available: True
CUDA runtime version: 12.3.107
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration:
GPU 0: NVIDIA A800-SXM4-80GB
GPU 1: NVIDIA A800-SXM4-80GB
GPU 2: NVIDIA A800-SXM4-80GB
GPU 3: NVIDIA A800-SXM4-80GB
GPU 4: NVIDIA A800-SXM4-80GB
GPU 5: NVIDIA A800-SXM4-80GB
GPU 6: NVIDIA A800-SXM4-80GB
GPU 7: NVIDIA A800-SXM4-80GB
Nvidia driver version: 470.182.03
cuDNN version: Probably one of the following:
/usr/lib/x86_64-linux-gnu/libcudnn.so.8.9.7
/usr/lib/x86_64-linux-gnu/libcudnn.so.9.0.0
/usr/lib/x86_64-linux-gnu/libcudnn_adv.so.9.0.0
/usr/lib/x86_64-linux-gnu/libcudnn_adv_infer.so.8.9.7
/usr/lib/x86_64-linux-gnu/libcudnn_adv_train.so.8.9.7
/usr/lib/x86_64-linux-gnu/libcudnn_cnn.so.9.0.0
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_infer.so.8.9.7
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_train.so.8.9.7
/usr/lib/x86_64-linux-gnu/libcudnn_engines_precompiled.so.9.0.0
/usr/lib/x86_64-linux-gnu/libcudnn_engines_runtime_compiled.so.9.0.0
/usr/lib/x86_64-linux-gnu/libcudnn_graph.so.9.0.0
/usr/lib/x86_64-linux-gnu/libcudnn_heuristic.so.9.0.0
/usr/lib/x86_64-linux-gnu/libcudnn_ops.so.9.0.0
/usr/lib/x86_64-linux-gnu/libcudnn_ops_infer.so.8.9.7
/usr/lib/x86_64-linux-gnu/libcudnn_ops_train.so.8.9.7
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True
CPU:
Architecture:                    x86_64
CPU op-mode(s):                  32-bit, 64-bit
Address sizes:                   48 bits physical, 48 bits virtual
Byte Order:                      Little Endian
CPU(s):                          232
On-line CPU(s) list:             0-231
Vendor ID:                       AuthenticAMD
Model name:                      AMD EPYC 7K83 64-Core Processor
CPU family:                      25
Model:                           1
Thread(s) per core:              2
Core(s) per socket:              58
Socket(s):                       2
Stepping:                        1
BogoMIPS:                        4890.80
Flags:                           fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid amd_dcm tsc_known_freq pni pclmulqdq monitor ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm cmp_legacy cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw topoext perfctr_core invpcid_single ssbd ibrs ibpb stibp vmmcall fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves clzero xsaveerptr wbnoinvd arat umip pku ospke vaes vpclmulqdq rdpid fsrm
Hypervisor vendor:               KVM
Virtualization type:             full
L1d cache:                       3.6 MiB (116 instances)
L1i cache:                       3.6 MiB (116 instances)
L2 cache:                        58 MiB (116 instances)
L3 cache:                        512 MiB (16 instances)
NUMA node(s):                    2
NUMA node0 CPU(s):               0-115
NUMA node1 CPU(s):               116-231
Vulnerability Itlb multihit:     Not affected
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Full AMD retpoline, IBPB conditional, IBRS_FW, STIBP conditional, RSB filling
Vulnerability Srbds:             Not affected
Vulnerability Tsx async abort:   Not affected
Versions of relevant libraries:
[pip3] mypy==0.991
[pip3] mypy-extensions==1.0.0
[pip3] numpy==1.26.4
[pip3] nvidia-nccl-cu12==2.18.1
[pip3] torch==2.1.2
[pip3] triton==2.1.0
[conda] numpy                     1.26.4                   pypi_0    pypi
[conda] nvidia-nccl-cu12          2.18.1                   pypi_0    pypi
[conda] torch                     2.1.2                    pypi_0    pypi
[conda] triton                    2.1.0                    pypi_0    pypiROCM Version: Could not collect
Neuron SDK Version: N/A
vLLM Version: 0.4.0
vLLM Build Flags:
CUDA Archs: Not Set; ROCm: Disabled; Neuron: Disabled
GPU Topology:
GPU0    GPU1    GPU2    GPU3    GPU4    GPU5    GPU6    GPU7    CPU Affinity    NUMA Affinity
GPU0     X      NV8     NV8     NV8     NV8     NV8     NV8     NV8     0-115   0
GPU1    NV8      X      NV8     NV8     NV8     NV8     NV8     NV8     0-115   0
GPU2    NV8     NV8      X      NV8     NV8     NV8     NV8     NV8     0-115   0
GPU3    NV8     NV8     NV8      X      NV8     NV8     NV8     NV8     0-115   0
GPU4    NV8     NV8     NV8     NV8      X      NV8     NV8     NV8     116-231 1
GPU5    NV8     NV8     NV8     NV8     NV8      X      NV8     NV8     116-231 1
GPU6    NV8     NV8     NV8     NV8     NV8     NV8      X      NV8     116-231 1
GPU7    NV8     NV8     NV8     NV8     NV8     NV8     NV8      X      116-231 1
Legend:
X    = Self
SYS  = Connection traversing PCIe as well as the SMP interconnect between NUMA nodes (e.g., QPI/UPI)
NODE = Connection traversing PCIe as well as the interconnect between PCIe Host Bridges within a NUMA node
PHB  = Connection traversing PCIe as well as a PCIe Host Bridge (typically the CPU)
PXB  = Connection traversing multiple PCIe bridges (without traversing the PCIe Host Bridge)
PIX  = Connection traversing at most a single PCIe bridge
NV#  = Connection traversing a bonded set of # NVLinks
🐛 Describe the bug
I run the following command on a server with 8 * A800 (80GB) GPUs and 1.8TB of memory:
python -m vllm.entrypoints.openai.api_server --model /mnt/llm_dataset/models/xverse_model/moe/moe24b-v112-276b/  --dtype auto --api-key xxx
 --trust-remote-code -tp 8 --port 8001

I noticed that vLLM initially loads the model into the 8 A800 GPUs, with each GPU consuming approximately 64GB of memory on average, without pre-allocating memory. Subsequently, I observed that the DRAM memory keeps increasing until an Out-of-Memory (OOM) error occurs. Please refer to the screenshot below for details.

Then, I learned that I can reduce the risk of RAM OOM by setting the --max-parallel-loading-workers parameter. However, when I set --max-parallel-loading-workers 1, I encountered the following error:
NotImplementedError: max_concurrent_workers is not supported yet.

#2588
I noticed that PR #1395 has fixed the RAM OOM issue, but why am I still encountering OOM errors when loading a 480GB MoE model with 8tp and 1.8TB of memory?

Hi @hxer7963, if my math is correct I do not think you can fit an unquantized 480GB model on 8x80GB GPUs. 8 * 80 = 640GB available memory and the model weights at BF16 would take up 2 * 480 = 960GB, so that is very much over the memory available. Maybe if you had an 8bit or 4bit quantization with GPTQ, you could fit the model.
Also, I would recommend trying to upgrade vLLM as you are on 0.4.0 per vLLM Version: 0.4.0


Review correctness and simplify tests

Head overlaps:

The test for head overlaps seems to be correct but it is too complicated!
Don’t test positions, test for an exact matching RangeDict (maybe create a fresh one and compare the keys?)
For example, [3,7) then [2,5) gives: [2,5), [5,7) and [2,5) as the _active_range

This is correct! The overlapped range [3,7) is replanted as [5,7)

Tail overlaps:

There is no test for tail overlaps(?) and it doesn’t seem to be correct
For example [2,5) then [3,7) gives:

an error when trying to access the repr
[2,3) and [3,7) in the keys of the internal ranges dict

This is correct, and is paired with the correct value, a RangeResponse on [2,5) with tail_mark of 2

an error when trying to compute the external ranges dict, arising from compute_external_ranges

I think some new fixtures would help simplify the testing (perhaps even break them out into a module for simplicity?)

I… don’t think the internal _ranges keys are meant to be different from the RangeResponse range, but they are? And this is the source of the bug in the tail overlap case, which arises when the tail mark gets applied multiple times (once internally, I think in some place where internal and external get mixed up maybe)
This does not happen in the head-overlap case (the _ranges keys match the ranges on the values at those keys in the RangeResponse)

I at first suspected the bug is coming from this line:
https://github.com/lmmx/range-streams/blob/56956498cf30ab27820dd2bbd6c64a8c858d24c5/src/range_streams/overlaps.py#L70
I also think that when the test for handle_overlaps stopped working I should have spotted that sign, and not replaced it with a working test(!)
The old test can be found here:


test(web-terminal) Remove TerminalComponent.test.tsx race condition issue

Investigate and fixed an issue that the TerminalComponent.test.tsx fails sometimes on the CI: example
The test contained a delay (800ms) to verify that it shows a <Progress /> while loading the web terminal.
After removing that delay the "should start loading" tests failed until I noticed that the backstage <Progress /> contain a delay until it was rendered:
https://github.com/backstage/backstage/blob/a070f29921cf7207a62e76abe5330f23364fdb07/packages/core-components/src/components/Progress/Progress.tsx#L24-L41
The tests run successfully after adding a ThemeProvider that disables that transition duration = delay.
After that, I removed the test anyway because the tests continue with the network call and logs an "update react component after unmount error". Instead of an extra test, I added the "show a  component assertion to the "should display terminal window" as it contains the same steps.

/cc @invincibleJai


Some Pokemon are highlighted in orange instead of gray

In v 1.1.0 of Optimizer (OS X environment), three of my Pokemon have their sprite and name highlighted in bright orange, rather than gray/black like all the others.
I can find no similarities among these three.  When sorted by number, Fast move, or CP, two are next to each other but the third is still elsewhere in the list. When sorted by all other categories, they are all separate from one another. There's nothing in common in their names- the Jynx is alphanumeric with no spaces, the Electabuzz is alphanumberic with one space, and the Hypno includes both a space and a special character (the greater-than sign > ).
If this orange highlighting is a feature, its purpose is not evident. Any guesses why this is happening?

It indicates that the Pokemon are favorited.

Oh geez. The one thing I didn't check. Thanks!

I'll think of some way to convey the meaning better!


Panel zoom out when using  '@fingers-key' key

When in zoomed into a pane, using the +F key makes the pane zoom out. Is this expected?
https://github.com/user-attachments/assets/aa2aadee-617b-4e88-89ee-d4d1341cdbf0

hmmm, that shouldn't happen ™
what version of tmux are you using?

The last stable one:
(base) [~]$ tmux -V
tmux 3.4

I thought that could be something with my config, but running it with this minimal config still causes the issue:
set -g @plugin 'tmux-plugins/tpm'
set -g @plugin 'tmux-plugins/tmux-sensible'
set -g @plugin 'Morantron/tmux-fingers'

run '~/.tmux/plugins/tpm/tpm'

In case it still helps:
(base) [main][~/.config/nvim]$ cat /tmp/tmux-$(echo $TMUX | cut -f2 -d',')/tmux-fingers/config.json | jq '.tmux_version'
"3.4"
``

Fixed in 2.2.0


Fixed pin number in comment

Hi!  This is Lex Kravitz - we're excited about your modifications and improvements to the FED code, and I'd like to incorporate some of them in our base FED code (crediting you of course).  But I know you're also modifying it for other purposes than a single feeder - would you want to talk on the phone or something and help us figure out what changes to pull into our base code?  I'm also curious about some of the tweaks you've made, and hearing how they've affected things.  Let me know, and thanks again!  -Lex

@alexxai, @KravitzLab
Dear Dr. Kravitz,
Sorry for the slow reply, I haven't been on GitHub much lately. I'm Caleb Norfleet, and, along with the Bohórquez Lab at Duke University,  I've been working on modifying your lab's feeder design to be part of an automated behavioral phenotyping system for mice.  We'd love to discuss some of the changes we've made with you.  I've already talked with our lab's principal investigator, Dr. Diego Bohórquez, and if you wouldn't mind getting in touch with him (his email address is<EMAIL_ADDRESS>we'd love to set up a phone call or meeting or something to talk about the feeder and our work.
Regards,
Caleb Norfleet


added doc for changed metric name in remote write

Adding prometheus_remote_storage_bytes_total in CHANGELOG since I was caught off guard that the metric changed after a recent update.
Did my best to correlate the change back to the correct version. Found what I believe to be the change here:
https://github.com/prometheus/prometheus/pull/8296/files#diff-1e66d5e658a9d99e1bd9b7be7d626d6b3bf9bbf480e210d2946c562cd746767cL200-R244

@beorn7 Should be a trivial changelog pr. Not sure if you're the right person, sorry in advance.

Looks correct to me. Do we have any policy about editing old changelogs? cc @roidelapluie

Thank you.


Support WebP

It looks like webp isn't a supported format...
It has been in graphicsmagicks since 1.3.19 (December 31, 2013)
https://github.com/thumbor/graphicsmagick-engine/blob/master/graphicsmagick_engine/engine.py#L21

This would be great to get implemented. The graphicsmagick engine hasn't been updated in 3 years! Looking at performance tests, graphicsmagick is faster then PiLLow so adding webp support makes sense.

@r0bdiabl0 Do you have a link to performance benchmarks? We're currently using Pillow because it's claimed to be faster then IM.


Make simulation time parameters available via model_params

The simulation start date/time should be made available to running modules, e.g. if a model uses the date or time to compute solar inclination (as Noah-OWP-Modular does--presently it has its own simulation start time in its init config files used for this purpose, and these may disagree). Useful values to make available would probably be:

simulation_start_epoch
simulation_timestep
simulation_start_ordinal_day (1-366)
simulation_end_epoch (because why not? Or YAGNI?)

Similar to #588, these should probably be specified like this:
{"source":"simulation_time"`, "from": "simulation_timestep"}

Names and "source" name open for discussion.
Current behavior
Expected behavior
Steps to replicate behavior (include URLs)

Screenshots

Given simulation_start_epoch, why can't the rare model that needs simulation_start_ordinal_day calculate it internally?


Hide Local Proxy to Remote Solana page on Neon Docs site

A request from DevOps relevant to the following Jira ticket:
https://neonlabs.atlassian.net/browse/SLA-77

Accidentally opened. Closing with no changes.


ERR  Linking react-native-fbsdk

rnpm-install ERR! Something went wrong while linking. Error: Expected "/*", "//", or "{" but "<" found.

@facebook-github-bot no-template


Your CLT does not support macOS 11.0 (Big Sur Beta 7)

Bug report
Please note we will close your issue without comment if you delete, do not read or do not fill out the issue checklist below and provide ALL the requested information. If you repeatedly fail to use the issue template, we will block you from ever submitting issues to Homebrew again.

[x] ran brew update and can still reproduce the problem?
[x] ran brew doctor, fixed all issues and can still reproduce the problem?
[x] ran brew config and brew doctor and included their output with your issue?

What you were trying to do (and why)
I was trying to install rabbitmq, which it failed with an error.. the same error/warning I get when running brew doctor
What happened (include command output)
Rabbitmq failed to install

Command output

Your CLT does not support macOS 11.0.
It is either outdated or was modified.
Please update your CLT or delete it if no updates are available.

What you expected to happen
I've expected the formula to get installed successfuly
Step-by-step reproduction instructions (by running brew commands)

Have homebrew installed on Big Sur Developer Beta 7
run brew doctor (same error/warning)
Install rabbitmq (same error/warning and the package fails to install)

Output of brew config and brew doctor commands

HOMEBREW_VERSION: 2.5.2
ORIGIN: https://github.com/Homebrew/brew
HEAD: cd4a3c0588abb82d916bc8558f4c157e951d449d
Last commit: 2 days ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: c899d98ff122c16facdf0aa0c206d4c3c6a2a662
Core tap last commit: 2 hours ago
Core tap branch: master
HOMEBREW_PREFIX: /usr/local
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 12
Homebrew Ruby: 2.6.3 => /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
CPU: dodeca-core 64-bit kabylake
Clang: 12.0 build 1200
Git: 2.24.3 => /Applications/Xcode-beta.app/Contents/Developer/usr/bin/git
Curl: 7.64.1 => /usr/bin/curl
macOS: 11.0-x86_64
CLT: <IP_ADDRESS>.1.1599194153
Xcode: 12.2 => /Applications/Xcode-beta.app/Contents/Developer

Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: You are using macOS 11.0.
We do not provide support for this pre-release version.
You will encounter build failures with some formulae.
Please create pull requests instead of asking for help on Homebrew's GitHub,
Discourse, Twitter or IRC. You are responsible for resolving any issues you
experience while you are running this pre-release version.

Warning: Your CLT does not support macOS 11.0.
It is either outdated or was modified.
Please update your CLT or delete it if no updates are available.

NOTE:
Based on https://github.com/Homebrew/brew/issues/8764 I've tried the following:
What didn't work:

switching between CLT 11 and CLT 12 in Xcode 12
installing Xcode 12.2 Beta and switching between all 3 available CLT's CLT 11, CLT 12, CLT 12.2
reinstalled the CLT from https://download.developer.apple.com/Developer_Tools/Command_Line_Tools_for_Xcode_12/Command_Line_Tools_for_Xcode_12.dmg

What did work:

uninstalling the CLT allowed me to install rabbitmq and got rid of CLT warning in brew doctor... but this is clearly not a solution

You need to install the CLT for Xcode 12 beta 5. The Xcode 12 release doesn't support macOS 12 and the CLT in Xcode is not the same as the normal Command Line Tools.

Closing this because of the output in brew doctor:

Please create pull requests instead of asking for help on Homebrew's GitHub,
Discourse, Twitter or IRC. You are responsible for resolving any issues you
experience while you are running this pre-release version.

Hi @SMillerDev,
I am facing some similar but a bit different issue (which might have the same cause). I just read your explanation below and could not understand it:

You need to install the CLT for Xcode 12 beta 5. The Xcode 12 release doesn't support macOS 12 and the CLT in Xcode is not the same as the normal Command Line Tools.

Can you help me understand the bold-ed statements?
TIA

That should have been macOS 11. The Command Line Tools are closely tied to macOS releases. XCode 12.0 only supports macOS 10.15 and below. Even if you install the XCode 12.2 beta though, that will not impact the installed Command Line Tools, so you'll need to install an older beta for the CLT (the beta 5 one for Xcode 12) that did support macOS 11.

I think my understanding is quiet outdated. I thought XCode 12.0 is the latest release of the IDE that should work just fine with MacOS 11 (Big Sur) so it should be 10.15 and above, no?
I checked also xcodereleases.com and seems to support my thoughts, do you have any thoughts on that?

so you'll need to install an older beta for the CLT (the beta 5 one for Xcode 12) that did support macOS 11
Again am confused with statement that it "did support MacOS 11" I thought MacOS11 is the latest version, and so should be supported even now?

Can you please provide the codename for the macOS 11 you are referring to?
Apple numbers someties gets confusing especially with their changes in numbering with Bigsur
And thanks for your time!

Just to add on my original question, my problem is well documented in Apple SE

As I can see, Xcode 12.2 Beta ships with macOS 11 SDK:

Xcode 12.2 beta includes SDKs for iOS 14.2, iPadOS 14.2, tvOS 14.2, watchOS 7.1, and macOS Big Sur 11.

Works fine on macOS Big Sur v11.0 Beta (20A5374i):
➜  git:(master) xcode-select -p
./../Xcode_12.2_beta.app/Contents/Developer

➜  git:(master) brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: You are using macOS 11.0.
We do not provide support for this pre-release version.
You will encounter build failures with some formulae.
Please create pull requests instead of asking for help on Homebrew's GitHub,
Discourse, Twitter or IRC. You are responsible for resolving any issues you
experience while you are running this pre-release version.

As I can see, Xcode 12.2 Beta ships with macOS 11 SDK:

Xcode 12.2 beta includes SDKs for iOS 14.2, iPadOS 14.2, tvOS 14.2, watchOS 7.1, and macOS Big Sur 11.

Works fine on macOS Big Sur v11.0 Beta (20A5374i):

I had XCode12 Beta 5 and was working fine and when I saw that they have just released 12.0 GM I thought it is the stable version of that Beta, so I thought if Beta was working probably GM will work. Now it seems am wrong.
Can you help me understand this: When Big Sur is released will there be XCode 12.3 for it? Because my thinking was XCode 12 was for Big Sur just like XCode 11 was for Mojave/Catalina?
This switch to Silcon blah blah is really confusing to me. BTW am using a 2015 MBP!

So I unpacked the XCode 12 Beta 5 that I had kept and did sudo xcode-select --switch /Applications/Xcode-beta.app/Contents/Developer and the build passes where it was failing.
Any article that explains how XCode version we working with this new change of numbering and hardware?

Sorry folks, we're not here to provide support for Big Sur. You'll have to figure this out yourself until we officially support it.


Increase compat with other git hosts via variables in base URL

I'm using Visual Studio Team Services (VSTS), and want to use jspm-git to link to Git repositories hosted in VSTS.
Unfortunately, the URLs of Git repositories in VSTS don't follow the common URL standard where the Base URL and repo names are simply concatenated together, one after another.
In my case, I'm using Visual Studio Team Services, and the Git Repositories have a URL which follows the following format: https://someaccount.visualstudio.com/DefaultCollection/PROJECTNAME/_git/REPOSITORYNAME
Thus, this PR adds a change which allows two variables to be set in the base URL, and if detected, jspm-git will replace the placeholders instead of appending the repo name.
The two variables proposed are:

$$projName$$: Project Name
$$repoName$$: Repository Name

The values for the two variables are split from the provided repo variable.
For example, if my registry configuration used the following base URL:
https://someaccount.visualstudio.com/DefaultCollection/$$projName$$/_git/$$repoName$$
And I tried to install with the command jspm mygit:AwesomeProject/SuperRepo, the resulting repository URL to be used would be:
https://someaccount.visualstudio.com/DefaultCollection/AwesomeProject/_git/SuperRepo

Hi @gerarde, thanks a lot for improving jspm-git! So far your PR looks good but I wonder if we should be using sprintf for injecting the variables into the base URL. This way it will be much more generic and covers more use cases. E.g. your URL would look then like
https://someaccount.visualstudio.com/DefaultCollection/%s/_git/%s

and then we could use vsprintf to format it
vsprintf(baseURL, repo.split('/'))

I'd like to introduce also a configuration flag like formatter: 'sprintf' so that you've to enable sprintf formatting explicitly via the advanced configurations of jspm-git.

Sorry I've totally missed you last update of the PR :( PR looks great now and I'll try to release it by tomorrow.

@gerarde Thanks for your effort! We can merge this PR once you resolve conflicts. @subesokun

@tauren, sorry for the late reply :( I've been quite busy lately but I've locally merged the PR already a few months ago and added some optimizations. Hope I can find my local changes again.


Run the DOM walker on observed mutations (in Live mode only)

Problem:
If the user's application includes state and interactions that change the rendered output, and they switch to using Live mode to trigger those changes, the captured metadata (and thus the Navigator) will be stale until the user switches to Select mode (or does anything else to dispatch an action).
Fix:
The underlying issue here is that we only run the DOM walker in response to a dispatched action, and no actions are dispatched whilst interacting with the app in Live mode. We do however have observers that will act on the changes introduced by interacting with the app, so we can use those to dispatch a new RUN_DOM_WALKER action whenever such a change is observed.
At first I experimented with using that action whilst in Select mode as well, as I'm 99% sure there are cases where we'd want that to happen, but unfortunately this has very real performance implications (it results in the DOM walker being run twice as often whilst in Select mode). I'm certain we could resolve that by attempting to marry up the intended walks to prevent duplicate walks from occurring, but doing so is non-trivial, as different paths are invalidated, and we can't just assume that we can skip a DOM walk if the previous action triggered one (since that would just negate the point of the RUN_DOM_WALKER action anyway), so we'd need some way of knowing beforehand that nothing had actually changed since the last walk.
So since the main reason for this work was to focus on Live mode, we only dispatch the actions if the editor is in Live mode.

I believe this should have a test (do a change in live mode and check if the metadata is updated, similarly to tests in dom-walker.spec.browser2)


Version mismatch with pytorch

hey @TABREZ-96 , Firstly thank u very much creating such a nice application.
however, i've been having problems running it
its running successfully but i'm not getting any results when i upload a picture. I'm getting an error somewhat like this

i think its related to pytorch. Couldyou please tell me the version of your python too

Hey, I am using Python 3.10.7


chore: remove event example for dataZoom

Since add an event for dataZoom has limited interest,  so we should remove in doc so user wouldn't be confused.

Close https://github.com/apache/echarts/issues/15775

So what sholud do when i need trigger    dataZoom click event?


add UTC time zone as an option on Application Setup page

Adds a UTC option to the drop-down list for time zone

:+1: