text:
偶发客户端全局事务线程卡死，此线程长时间没有直接结果返回。

[ ] I have searched the issues of this repository and believe that this is not a duplicate.

Ⅰ. Issue Description
- JDK version(e.g. `java -version`):  java version "1.8.0_291"
- Seata client/server version:  1.5.2/1.5.2
- Database version: oracle 10
- OS(e.g. `uname -a`): windows 2016
- org.springframework.boot: 2.3.12.RELEASE
- com.alibaba.cloud: 2.2.7.RELEASE
- spring-cloud-starter-dubbo: 2.2.7.RELEASE
- mybatis-plus-boot-starter: 3.5.1
- com.oracle.database.jdbc: 11.2.0.4

windows 系统 命令行启动服务，偶发客户端全局事务线程卡死，此线程长时间没有直接结果返回。其他服务其他业务不受影响。
线程卡死后，无法关闭服务时(关闭到一半时，停止)。

Ⅱ. Describe what happened
全局事务采用：AT模式， 调用 receiveDataRefund，进行2条数据的退费业务。长时间没有直接结果返回，业务在等待后续执行。

客户端seata 日志:
2023-07-07 09:59:37.356 [http-nio-28095-exec-6] INFO  c.y.t.web.interceptor.TLogWebInvokeTimeInterceptor - [NONE][NONE][0][12957724007217344] [TLOG]开始请求URL[/api/diagnosis/record/receive/data/refund],参数为:{}
2023-07-07 09:59:37.356 [http-nio-28095-exec-6] INFO  com.hzrings.kfxt.patternPdkf.api.aspect.Aspects - [NONE][NONE][0][12957724007217344]  com.hzrings.kfxt.patternPdkf.api.controller.diagnosis.DiagnosisRecordController@6970687e.receiveDataRefund([[PushItemRefundDataVo(hospitalCode=15439370, departmentCode=434, itemCode=PDJBZL046, yjxh=49281220, zfpb=1, zfrq=Thu Jul 06 17:04:28 CST 2023, zfgh=0001107), PushItemRefundDataVo(hospitalCode=15439370, departmentCode=434, itemCode=PDJBZL054, yjxh=49281220, zfpb=1, zfrq=Thu Jul 06 17:04:28 CST 2023, zfgh=0001107), PushItemRefundDataVo(hospitalCode=15439370, departmentCode=434, itemCode=PDJBZL060, yjxh=49281220, zfpb=1, zfrq=Thu Jul 06 17:04:28 CST 2023, zfgh=0001107)]]) start!
2023-07-07 09:59:37.371 [http-nio-28095-exec-6] INFO  io.seata.tm.api.DefaultGlobalTransaction - [NONE][NONE][0][12957724007217344] Begin new global transaction [10.88.88.227:58901:3549234767466526513]
2023-07-07 09:59:37.444 [http-nio-28095-exec-6] INFO  c.h.k.patternPdkf.api.config.MyMetaObjectHandler - [NONE][NONE][0][12957724007217344] start update fill......

后面客户端seata日志中没 10.88.88.227:58901:3549234767466526513 此事务的任何可追踪日志
如：获取全局锁超时日志错误、Suspending current transaction、事务状态 commit status 的日志。
而且是有两条数据更新应该会有两个 start update fill...... 日志，这里只有一条。说明在执行第一个条数据更新时就卡住了。
服务端 seata 有事务60秒超时回滚日志，并回滚成功。

2023-07-07 09:59:37.371  INFO --- [  ServerHandlerThread_1_25_500] i.s.s.coordinator.DefaultCoordinator     : Begin new global transaction applicationId: pdkf,transactionServiceGroup: order-service-group, transactionName: receiveDataRefund(java.util.List),timeout:60000,xid:10.88.88.227:58901:3549234767466526513
2023-07-07 10:00:38.240  INFO --- [            TxTimeoutCheck_1_1] i.s.s.coordinator.DefaultCoordinator     : Global transaction[10.88.88.227:58901:3549234767466526513] is timeout and will be rollback.
2023-07-07 10:00:39.244  INFO --- [          RetryRollbacking_1_1] io.seata.server.coordinator.DefaultCore  : Rollback global transaction successfully, xid = 10.88.88.227:58901:3549234767466526513.

出现卡死业务后
在cmd 窗口关闭服务时
com.zaxxer.hikari.HikariDataSource- HikariPoo1-1Shutdown initiated... 后就无法继续关闭服务
2023-07-07 10:47:48.305 [SpringContextShutdownHook] INFO o.s.scheduling. concurrent.ThreadPoolTaskscheduler- Shutting downxecutorServicetaskScheduler
2023-07-07 10:47:48.310 [SpringContextShutdownHook] INFO c.a.cloud.nacos.registrw.lacosSeryiceRegistrwDezresistering frorNacos Server now...
2023-07-07 10:47:48.345 [SpringContextShutdownHook] INFO c.a.cloud.nacos.registry.NacosServiceRegistryregistration firDeshed.
2023-07-07 10:47:48.666 [SpringContextShutdownHook] INFO o.s.scheduling.concurrent.ThreadPoolTaskExecutorShutting down ExcutorService applicationTaskExecutor
2023-07-07 10:47:48.890 [SpringContextShutdownHook] INFO com.zaxxer.hikari.HikariDataSource- HikariPoo1-1Shutdown initiated...

这是服务重启后，正常处理的客户端日志
2023-07-07 10:53:53.653 [http-nio-28095-exec-9] INFO  c.y.t.web.interceptor.TLogWebInvokeTimeInterceptor - [NONE][NONE][0][12957937411897536] [TLOG]开始请求URL[/api/diagnosis/record/receive/data/refund],参数为:{}
2023-07-07 10:53:53.658 [http-nio-28095-exec-9] INFO  com.hzrings.kfxt.patternPdkf.api.aspect.Aspects - [NONE][NONE][0][12957937411897536]  com.hzrings.kfxt.patternPdkf.api.controller.diagnosis.DiagnosisRecordController@2d839402.receiveDataRefund([[PushItemRefundDataVo(hospitalCode=15439370, departmentCode=434, itemCode=PDJBZL046, yjxh=49281220, zfpb=1, zfrq=Thu Jul 06 17:04:28 CST 2023, zfgh=0001107), PushItemRefundDataVo(hospitalCode=15439370, departmentCode=434, itemCode=PDJBZL054, yjxh=49281220, zfpb=1, zfrq=Thu Jul 06 17:04:28 CST 2023, zfgh=0001107), PushItemRefundDataVo(hospitalCode=15439370, departmentCode=434, itemCode=PDJBZL060, yjxh=49281220, zfpb=1, zfrq=Thu Jul 06 17:04:28 CST 2023, zfgh=0001107)]]) start!
2023-07-07 10:53:53.663 [http-nio-28095-exec-9] INFO  io.seata.tm.api.DefaultGlobalTransaction - [NONE][NONE][0][12957937411897536] Begin new global transaction [10.88.88.227:58901:3549234767466553941]
2023-07-07 10:53:53.741 [http-nio-28095-exec-9] INFO  c.h.k.patternPdkf.api.config.MyMetaObjectHandler - [NONE][NONE][0][12957937411897536] start update fill......
2023-07-07 10:53:53.941 [http-nio-28095-exec-9] INFO  c.h.k.patternPdkf.api.config.MyMetaObjectHandler - [NONE][NONE][0][12957937411897536] start update fill......
2023-07-07 10:53:54.259 [http-nio-28095-exec-9] INFO  io.seata.tm.api.DefaultGlobalTransaction - [NONE][NONE][0][12957937411897536] Suspending current transaction, xid = 10.88.88.227:58901:3549234767466553941
2023-07-07 10:53:54.262 [http-nio-28095-exec-9] INFO  io.seata.tm.api.DefaultGlobalTransaction - [NONE][NONE][0][12957937411897536] [10.88.88.227:58901:3549234767466553941] commit status: Committed
2023-07-07 10:53:54.262 [http-nio-28095-exec-9] INFO  com.hzrings.kfxt.patternPdkf.api.aspect.Aspects - [NONE][NONE][0][12957937411897536] com.hzrings.kfxt.patternPdkf.api.controller.diagnosis.DiagnosisRecordController@2d839402.receiveDataRefund([[PushItemRefundDataVo(hospitalCode=15439370, departmentCode=434, itemCode=PDJBZL046, yjxh=49281220, zfpb=1, zfrq=Thu Jul 06 17:04:28 CST 2023, zfgh=0001107), PushItemRefundDataVo(hospitalCode=15439370, departmentCode=434, itemCode=PDJBZL054, yjxh=49281220, zfpb=1, zfrq=Thu Jul 06 17:04:28 CST 2023, zfgh=0001107), PushItemRefundDataVo(hospitalCode=15439370, departmentCode=434, itemCode=PDJBZL060, yjxh=49281220, zfpb=1, zfrq=Thu Jul 06 17:04:28 CST 2023, zfgh=0001107)]]) end! result = ResponseUtils{code=10200, message='操作成功', data=null}
2023-07-07 10:53:54.263 [http-nio-28095-exec-9] INFO  c.y.t.web.interceptor.TLogWebInvokeTimeInterceptor - [NONE][NONE][0][12957937411897536] [TLOG]结束URL[/api/diagnosis/record/receive/data/refund]的调用,耗时为:607毫秒

Ⅲ. Describe what you expected to happen
1、目前无法确定原因，而且是偶发的，重新概率比较小。 确定和数据无关。 排查了日子，排除资源争抢情况。

Ⅳ. How to reproduce it (as minimally and precisely as possible)
Minimal yet complete reproducer code (or URL to code):
Ⅴ. Anything else we need to know?
c.h.k.patternPdkf.api.config.MyMetaObjectHandler  只是更新了一下操作时间。
package com.hzrings.kfxt.patternPdkf.api.config;

import com.baomidou.mybatisplus.core.handlers.MetaObjectHandler;
import lombok.extern.slf4j.Slf4j;
import org.apache.ibatis.reflection.MetaObject;
import org.springframework.stereotype.Component;

import java.util.Date;

@Slf4j
@Component
public class MyMetaObjectHandler implements MetaObjectHandler {

    @Override
    public void insertFill(MetaObject metaObject) {
        log.info("start insert fill......");
        this.setFieldValByName("createTime", new Date(), metaObject);
        this.setFieldValByName("updateTime", new Date(), metaObject);
    }

    @Override
    public void updateFill(MetaObject metaObject) {
        log.info("start update fill......");
        this.setFieldValByName("updateTime", new Date(), metaObject);
    }
}

Ⅵ. Environment:
- JDK version(e.g. `java -version`):  java version "1.8.0_291"
- Seata client/server version:  1.5.2/1.5.2
- Database version: oracle 10
- OS(e.g. `uname -a`): windows 2016
- org.springframework.boot: 2.3.12.RELEASE
- com.alibaba.cloud: 2.2.7.RELEASE
- spring-cloud-starter-dubbo: 2.2.7.RELEASE
- mybatis-plus-boot-starter: 3.5.1
- com.oracle.database.jdbc: 11.2.0.4

jstack或者arthas trace去看，而不是直接kill

repo: seata/seata


text:
bugfix: fix xidInterceptorType is null

Ⅰ. Describe what this PR did
Ⅱ. Does this pull request fix one issue?

fixes #1908
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #1909 into develop will decrease coverage by <.01%.
The diff coverage is 0%.

@@              Coverage Diff              @@
##             develop    #1909      +/-   ##
=============================================
- Coverage      55.43%   55.42%   -0.01%
  Complexity      2406     2406
=============================================
  Files            428      428
  Lines          14346    14348       +2
  Branches        1699     1699
=============================================
  Hits            7953     7953
- Misses          5677     5679       +2
  Partials         716      716

Impacted Files
Coverage Δ
Complexity Δ

...c/main/java/io/seata/core/context/RootContext.java
36.17% <0%> (-1.61%)
9 <0> (ø)

source: gharchive/pull-request

authors: cmonkey codecov-io

license_type: permissive

license_source: github-api


text:
Documentation?

Hi! Thanks for making this library publicly available. What's the best way to go through the documentation for this library? I can see that there's a short usage guide on the README but where can I find more details about the difference between ratio, partial_ratio, token_sort_ratio, token_set_ratio and so on?

It's difficult to tell at first glance what the output numbers even mean. At first, I thought it was like: "the bigger the number, the bigger the difference between the strings", but it seems to be the other way around (like a percentage of confidence that those two strings match?)

source: gharchive/issue

authors: adam-sierakowski nikhilweee

repo: seatgeek/thefuzz

license: MIT


text:
Side menu always visible

Hello, very good work.
Is possible to mantain alwais visible the side menu?
Thank you for your great contribution.

Hi! Do you mean something similar to how the SplitPane works?

yes. Exactly this. Do you have an expample of this?

Do you have an example  for split pane with MultiLevelSideMenu

Hi @sirin8. I haven't tried yet but it should work as it is since the component only adds some content to the side menu.
@sirin8, @oliveravanze this weekend I'll create a demo using the split pane (will add the link in this issue). Thank you both for the feedback.

authors: oliveravanze sebaferreras sirin8

license: mit

license_source: bigquery


text:
🎉 1.0.3

ℹ About this release

Version: 1.0.3
Type: patch
Last Release: 1.0.2 (12/11/2022, 2:53:12 PM) [?]
Commits to merge: 28 [?]

🐛 Bug Fixes

Use bot token to check pull requests (559064c)

📦 Dependencies

Update simple-git from ^3.15.0 to ^3.16.0

:tada: This PR is included in version 1.0.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
Add pseudoinverse, SVD

Pseudoinverse and singular value decomposition calculation, while difficult, is useful if nphysics (or some animation library) ever wants to implement Jacobian-based inverse kinematics methods. It's doable with just the transpose, but incredibly imprecise.

SVD and pseudo-inverse will be released on the next version of nalgebra. See #274 .

authors: Jragonmiris sebcrozet

repo: sebcrozet/nalgebra


text:
Triangular shape with Shape+Clone?

Hi dear ncollide maintainers 👋
I'd like to use a 2d triangular shape for collisions – which implements both Shape and Clone.
First, I tried to use shape::Triangle, but even though it's available in ncollide2d, it appears to use the feature switch dim3, http://www.ncollide.org/rustdoc/src/ncollide2d/shape/shape_impl.rs.html#79-84.
Then, I looked at shape::ConvexPolygon, which appears to be the way to go for a triangular 2d shape. However, ConvexPolygon does not implement Clone.
Is there a specific reason for this? And am I looking at the wrong shapes?
I am using ncollide2d 0.15.3 – really am impressed by this library so far, great work! 😊

Hi! ConvexPolygon is indeed the right shape to use here. Triangle does not implement Shape in 2D. ConvexPolygon should implement Clone but it seems I forgot to make it so.

@sebcrozet Thanks for the quick answer, Sébastien, much appreciated! I'm relieved to hear it's just an oversight 😊I'm closing this – if it's against Repo policy, please reopen. Thanks again 😊

@floere Actually, there is usually no need to close an issue manually (unless if it is not going to be fixed). It will automatically be closed by github as soon as the corresponding pull request #203 is merged. That way, you will get a notification from github as soon as the fix is merged to master (and I usually publish it to crates.io soon after that).

@sebcrozet Ah I see, thanks – I'll not close it in the future 😊

authors: floere sebcrozet

repo: sebcrozet/ncollide


text:
How do you install this?

I cloned the files, this placed a folder on my desktop. Ok, I renamed the folder to 'Sass.codaplugin' and this made it look like a plugin.
But when I place this in the plug-ins folder, this is not being picked up by Coda?
Lost here ;(

The files here on GitHub are just the source files for the plugin and require Xcode to compile the actual Sass.plugin. I will add the actual Sass.codaplugin file to GitHub soon. In the meantime you can download the Sass.codaplugin from this page https://sites.google.com/site/codasassplugin/

authors: blackfalcon secca

repo: secca/Coda-Sass-Plug-in


text:
HEU是否支持GPU计算？

HEU是否支持GPU计算？如果不支持，是否有这方面的计划

基于硬件加速的算法以合作团队、社区贡献为主，曾经有一个团队给 HEU 贡献了 GPU Paillier 算法，但是性能一直没有达到预期，因此没有放到 github 上。合作团队的人力不太可控，短期内调优 GPU Paillier 的性能希望渺茫，而我们内部暂时没有往 GPU 方向投入资源的计划

authors: dtera usafchn

repo: secretflow/heu


text:
kuscia数据接入问题

支持csv，试了ok。数据库能支持吗，怎么基于数据库执行psi任务

支持csv，试了ok。数据库能支持吗，怎么基于数据库执行psi任务

“基于数据库执行psi任务“，具体是指什么意思呢

https://www.secretflow.org.cn/docs/kuscia/latest/zh-Hans/tutorial/run_secretflow_with_api_cn

是按照这个指导，把自己的数据库导出为csv文件，然后放到/home/kuscia/var/storage/data。
想着怎么可以直接代码连到数据库

https://www.secretflow.org.cn/docs/kuscia/latest/zh-Hans/tutorial/run_secretflow_with_api_cn  是按照这个指导，把自己的数据库导出为csv文件，然后放到/home/kuscia/var/storage/data。 想着怎么可以直接代码连到数据库

所以你测试用的数据，是从自己的数据库导出为csv文件放置在上述文档的指定的位置？

https://www.secretflow.org.cn/docs/kuscia/latest/zh-Hans/tutorial/run_secretflow_with_api_cn  是按照这个指导，把自己的数据库导出为csv文件，然后放到/home/kuscia/var/storage/data。 想着怎么可以直接代码连到数据库

目前secretflow 引擎是直接读取 /home/kuscia/var/storage/data 下的数据执行psi算子。Kuscia将推出DataProxy，对引擎屏蔽数据的实际存储位置（数据库，oss，本地）。引擎对接DataProxy即可获取数据内容。对于用户而言，只需配置相对应的数据源的地址/账户密钥信息即可。

这个功能好，大致什么时间可以有
我们在下个月版本，用户可见应该是10月初。
请问你是在生产环境要用数据库吗？是哪类型的数据库啊？mysql？有评估过数据量多大吗？

mysql，求交数据量一般在千万到亿级，走测试

mysql，求交数据量一般在千万到亿级，走测试

OK，下个月增加了Mysql的支持。 不过暂不支持where过滤。

请问你们是在企业单位、还是高效用户啊？是工业场景还是POC场景呢？

企业poc

先关闭此issue了，有问题可以再交流。

mysql，求交数据量一般在千万到亿级，走测试

OK，下个月增加了Mysql的支持。 不过暂不支持where过滤。

对mysql的支持请问有了吗 @Eiji911

mysql，求交数据量一般在千万到亿级，走测试

OK，下个月增加了Mysql的支持。 不过暂不支持where过滤。

对mysql的支持请问有了吗 @Eiji911

hi，这部分目前还在开发中，预计到10月底，敬请关注

您好，对于mysql的支持，在这次的发布中吗
https://github.com/secretflow/kuscia/releases/tag/v0.4.0b0

哈喽，因为这部分涉及到要做开源改造，所以本次没带出，更新后之后我们会在这里同步

请问目前 dataproxy 研发是什么状态，是否在新版本中可用？

同上的问题

hi  @killomsc @changhr2013 @daydayuphere   感谢您对DataProxy 的关注，为了能让dataproxy更加通用与易用，我们决定将DataProxy接口与SDK 进行了重新设计，目前方案还在评审中，有最新消息我们会在此Issue中及时同步。

同上

authors: Eiji911 UniqueMarvin changhr2013 daydayuphere killomsc ruhengChen wangyixianggogo yushiqie

repo: secretflow/kuscia


text:
Cemu for macOS

As far as I know, this work is more focused on getting the adapters working on Dolphin.
Is it possible to get this driver to work on the Wii U emulator Cemu for macOS? More specifically for the Super Smash Bros. for Wii U game, which allows the usage of GameCube controllers through an adapter?
Have asked regarding support on the Cemu Discord server and the reply I received from a mod was, quote "No idea! I don't think anyone has tried." "If they show up in the Mac's Settings/Controllers panel, you should be good to go with SDLcontroller at the Cemu side."

This driver mostly stops macOS from grabbing the device and making apps unable to read it; CEMU would need to add support for natively reading it - or if your adapter supports “PC mode”, SDL should be able to pick that up.
On Sun, Dec 31, 2023 at 11:48, Elías M. @.***(mailto:On Sun, Dec 31, 2023 at 11:48, Elías M. < wrote:

As far as I know, this work is more focused on getting the adapters working on Dolphin.
Is it possible to get this driver to work on the Wii U emulator Cemu for macOS? More specifically for the Super Smash Bros. for Wii U game, which allows the usage of GameCube controllers through an adapter?
Have asked regarding support on the Cemu Discord server and the reply I received from a mod was, quote "No idea! I don't think anyone has tried." "If they show up in the Mac's Settings/Controllers panel, you should be good to go with SDLcontroller at the Cemu side."
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

The adapter that I'm trying to use is the original one, so no PC/Wii U switch. With the driver, the adapter only "turns on" when using Dolphin. Otherwise it's just connected and detected on macOS but not usable. Even with the adapter being "activated" with Dolphin, it cannot be used outside of Dolphin.
So, is that the issue? Using the official adapter with no PC/Wii U switch, therefore not being usable with SDL?

That being said, you're right. There's no "native support" like the one Dolphin has.
Presented a "request" regarding "native support" on Cemu's Discord server. Will see depending on their response if the idea may be presented on the "Issues" section of their GitHub.

Since this request is more on Cemu's side, I shall close this issue.

authors: GreetingsIExist ryanmcgrath

repo: secretkeysio/GCAdapterDriver


text:
INTRODUCTION TO VITE 2.0

INTRODUCTION TO VITE 2.0
Vite.Js (a French word for "fast"  or “quick”, pronounced /vit/) developed by the creator of Vue.js, Evan You.
Vite.Js 2.0 is a front-end build tool or framework for designing a rich, elegant and sleek User Interface, it is referred to as the next-generation framework for front-end tooling.
In this tutorial, we are going to install Vite 2.0 with all its dependencies and explore its advantages and reasons for choosing Vite.
WHY VITE?
ViteJs have the following advantages over other frameworks;

Instant server-side rendering

CSS preprocessor

Mono repo support

Lighting fast HMR

Rich features

Optimized building

Fully typed APIs

Faster dependency pre-building

PREREQUISITES
To be able to use Vite 2.0, we would need the following:
Good understanding of Node.Js
Good understanding of React.Js
Node. Js version 12 or later, it's assumed that you have installed Node.Js in your system, but if you haven`t you can download the latest compatible version for your OS from here
INSTALLATION PROCEDURE
There are basically different ways to install Vite but in this tutorial, we will only focus on installing using NPM and YARN
Installing using npm
Open your terminal, navigate into the folder you want to install Vite, and run the following commands:
Key takeaways:
At the end of this tutorial, the reader can differentiate ViteJs from other frameworks, how to install vite on his/her machine, its advantages, and its relevance in frontend development.
References:
www.vitejs.dev
www.google.com
www.stackoverflow.com

seems like a helpful topic - approved  @Danmasanii

Just closing this TOPIC to make room in the queue - it can be REOPENED whenever the PR is ready 👍
https://github.com/section-engineering-education/engineering-education/pull/2462

authors: Danmasanii hectorkambow


text:
C Program to Implement Playfair Cipher Algorithm

C Program to Implement Play fair Cipher Algorithm
Introduction
Encryption and decryption require a cipher. The ciphertext is the term used to describe it. Different algorithms may transform plain text to encoded text using the ciphertext process. The first practical digraph substitution cipher was the Play fair cipher. In this type of cipher, we encrypt a pair of alphabets instead of a single alphabet.
Key takeaways
By the end of the article, the learners should have covered:

Generating key squares
Encryption techniques using play fair cipher
Decryption algorithm
Advantages and disadvantages of using this algorithm

Article quality
This article will provide a thorough understanding of the recommended subject. The topic is suitable for beginners since everything is thoroughly described and detailed. For optimal comprehension of the ideas needed, code snippets will be used.
References
N/A

This topic appears a bit over-saturated - search We focus more on unique projects. Feel free to suggest another topic. Thanks

authors: KARIUKIJOHN WanjaMIKE


text:
Linux container (LXC ) vs. Docker container , what's the difference and why Docker is better

A LCX vs Docker article and the related images
Article checklist
ATTENTION: In your PR - add the ISSUE (topic form) # that this PR corresponds to. You can do this by also adding a comment that states "This fixes #(enter your Idea Content Form #)" to link and close your Idea Content (issue) when the PR is merged.
NOTE: (Please ensure that you have only one open issue + linked pull request at a time. This will ensure that we complete the article in a timely manner from inception to publishing.)
If you have not already please go over our Resources Page for more tips and tricks on how to improve our overall technical writing.
Preliminary Checks - Formatting and Structure

[ ] Does your article follow any of the suggested structure formats? - see example formats
[ ] Is your article properly formatted in Markdown? - see Github Markdown guide
[ ] Have you used the correct folder and file structure? - see Contribution Guidelines
[ ] Is your article over 750 words? - Tool: Wordcounter.net
[ ] Have you used our preferred heading structure? - H3 (###) and up
[ ] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.
[ ] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.
[ ] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images
[ ] In your PR - add a comment that states "This fixes #(enter your Idea Content Form #)" to link and close your Idea Content (issue) when the PR is merged.

Grammar & plagiarism checks

[ ] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid -  Grammarly
[ ] Please place your article through a 3rd party plagiarism checker? We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[ ] Have you checked your article for readability? - Tool: Hemmingway
[ ] Have you added sources for quotes and images that aren't yours?

Technical checks

[ ] Are your code snippets properly formatted for syntax highlighting - see Syntax guide

Contribution guidelines
For first-time contributors and for more details, see Contributing Guidelines

@JuliusGikonyoNyambura Congrats on your first article!✨
Please add a bio and a profile pic to the content/author folder in your branch. Take a look at how the other authors created their bio folders and follow the structure.

@JuliusGikonyoNyambura Can you please add an author page? We can move to a final review once it's done.

plagiarism check done

@JuliusGikonyoNyambura any updates?

@JuliusGikonyoNyambura any updates?

Sorry for the delay. I have added the author @zolomohan

nice work @JuliusGikonyoNyambura
please go through my final edits to see what can be improved for future articles.
cc @zolomohan

Thank you @hectorkambow. There is one image not visible on the blog, check it please.
https://www.section.io/engineering-education/lxc-vs-docker-what-is-the-difference-and-why-docker-is-better/


text:
Creating a React app using Vite

This fixes #3142
Article checklist
ATTENTION: In your PR - add the ISSUE (topic form) # that this PR corresponds to. You can do this by also adding a comment that states "This fixes #(enter your Idea Content Form #)" to link and close your Idea Content (issue) when the PR is merged.
NOTE: (Please ensure that you have only one open issue + linked pull request at a time. This will ensure that we complete the article in a timely manner from inception to publishing.)
If you have not already please go over our Resources Page for more tips and tricks on how to improve our overall technical writing.
Preliminary Checks - Formatting and Structure

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.
[x] Does your article follow any of the suggested structure formats? - see example formats
[x] Is your article properly formatted in Markdown? - see Github Markdown guide
[x] Have you used the correct folder and file structure? - see Contribution Guidelines
[x] Is your article over 750 words? - Tool: Wordcounter.net
[x] Have you used our preferred heading structure? - H3 (###) and up
[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.
[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.
[x] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images
[x] In your PR - add a comment that states "This fixes #(enter your Idea Content Form #)" to link and close your Idea Content (issue) when the PR is merged.

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid -  Grammarly
[x] Please place your article through a 3rd party plagiarism checker? We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide

Contribution guidelines
For first-time contributors and for more details, see Contributing Guidelines

I'd wish to review this article

If this not a duplicate, I'm interested in reviewing this one.

Great work ladies @Neema-2016 @WanjaMIKE 🚀
Please go over the changes I made.

Great work ladies @Neema-2016 @WanjaMIKE 🚀
Please go over the changes I made.

Thank you @ahmadmardeni1 and @WanjaMIKE also😊


text:
A dive into Message Queue Telemetry Transport Protocol

article
Article checklist
Pre-submission checks

Please ensure that you have only one open topic suggestion (issue) + in-review article (linked pull request) at a time. This will ensure that we complete the review process in a timely manner from inception to publishing

If you have not already, please go over our Resources Page for more tips and tricks on how to improve your overall technical writing so reviews are swifter, increase the chance of a payout and provide more value to our readers.

For first-time contributors and for more details on our submission guidelines, see our Contributing Guidelines.

Formatting and structure checks

[x] Have you used the correct folder and file structure? - see Contribution Guidelines

[x] Is your article properly formatted in Markdown? - see Github Markdown guide

[x] Have you used our preferred heading structure? - H3 (###) and up

[x] Does your article follow any of the suggested structure formats? - see example formats

[x] Is your article over 750 words? - Tool: Wordcounter.net

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.

[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.

[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.

[x] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[x] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[ ] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[x] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?
[x] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?

Topic suggestion this closes

Remove the backticks and add the issue number below to link and close your Topic Suggestion (issue) when your article has been published (PR has been merged). See this video for more details.

`This closes #3432

Finally, delete the article checklist notes in blockquotes and submit your PR. We look forward to reviewing your article.

Upon running your article through our 3rd party plagiarism checker it seemed to raise a few flags and the % was higher than we typically accept.
Please see attached PDF - and revisit the article to ensure we are contributing wholly unique and original content.
Be sure to see our resources page to see more info on plagiarism and what is considered as such.
A dive into Message Queue Telemetry Transport Protocol#3983

Hello @ahmadmardeni1 and @mercymeave I have corrected the plagiarism error.
Please check. Thank you

hello @mercymeave hope you are doing great.
just curious about the progress of the review. Thank you

Working on the finals.

authors: ahmadmardeni1 mercymeave rene-shigolah


text:
[Languages]: Building a Screen Recording Application Using JavaScript

Article checklist
Attention
Our Peer Reviewer and Content Moderator teams do NOT provide any revisions services. All revisions and edits should be completed on your own forked repo (as to not take up room in the queue) in order for our team to review them all in a timely manner.
ANY ARTICLE SUBMITTED WITH GLARING ERRORS WILL BE IMMEDIATELY CLOSED.

As a rule of thumb - please be sure to only submit articles (pull requests) that are fully polished and ready to be published. Be sure to go through our resources documents for extra and 3rd party (vetted) resources to help improve overall technical writing.

Pre-submission checks

Please ensure that you have only one open topic suggestion (issue) + in-review article (linked pull request) at a time. This will ensure that we complete the review process in a timely manner from inception to publishing

If you have not already, please go over our Resources Page for more tips and tricks on how to improve your overall technical writing so reviews are swifter, increase the chance of a payout and provide more value to our readers.

For first-time contributors and for more details on our submission guidelines, see our Contributing Guidelines.

Formatting and structure checks

[x] Have you used the correct folder and file structure? - see Contribution Guidelines

[x] Is your article properly formatted in Markdown? - see Github Markdown guide

[x] Have you used our preferred heading structure? - H3 (###) and up

[x] Does your article follow any of the suggested structure formats? - see example formats

[x] Is your article over 750 words? - Tool: Wordcounter.net

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.

[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.

[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.

[x] Have you included a hero image that is 600x400 pixels, under 300KB in size, and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[x] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[x] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?
[x] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?

Topic suggestion this closes

Remove the backticks and add the issue number below to link and close your Topic Suggestion (issue) when your article has been published (PR has been merged). See this video for more details.

This closes #5470

Finally, delete the article checklist notes in blockquotes and submit your PR. We look forward to reviewing your article.

This fixes #5470

Hello @Qodestackr , Glad to see you are back to give the community more content. Please remember to fill in the checkboxes in the PR as you wait for an available member of the Peer Review team to jump on the PR.

Hey @katungi, let me jump on this. I love javascript :smile:

Hey @mercymeave , sure thing. Have fun 🥳

Plagiarism check done.

authors: Qodestackr WanjaMIKE katungi mercymeave


text:
testing-pipelines

test pr

/retest

repo: securesign/rekor


text:
Localization for rule descriptions

Hi!
I could not find any specs about how to localize rule string result. I need to localize for example rule string "Weekly, on tuesdays".

Hey Mikko,
Internationalization has been a long dream of mine for the project - and a recent refactor has put me in a really good place to integrate it.  I was waiting for someone to ask to build it, to avoid building things no one wanted.
I'll take this on as a feature branch, and update here as appropriate.  Thanks!
JC

+1

+1 for this!

its there a way to add it manualy for one language ?? thank you great gem

You could copy a locale file and make a pull request. What language would that be? There reason I haven't been working on this, is that I lack the understanding of how to generalise the locale format so that it would work with as many different languages as possible.

@Frank004 it looks like this fork is working. You can PR them with your language file.
https://github.com/gocardless/ice_cube

@joelmeyerhamme  and @dgilperez  Hi I got it working using this one gem 'ice_cube'  , :git => 'git://github.com/dgilperez/ice_cube.git'.  Thanks for this great gem. Save us days and days of code

This was done in #311. Thanks everyone!

authors: Frank004 TangMonk avit dgilperez joelmeyerhamme mruokojo seejohnrun


text:
Set input type for SpecifiedPersonForm email/phone

This makes little difference on desktop browsers, but causes mobile software keyboards to customise their layout.

repo: seek-oss/wingman


text:
"Bad Gateway" Error

I recently installed the new email add-on and installed successfully. However, the emails are not sending. In the "_Job Results" folder, errors show "Bad Gateway"

It appears that the email service is not running on your system. If you have administrator access can you check the value of Components/EmailerService/Enabled within Admin\Configuration with the advanced flag?

Thanks for the quick response. You are correct in that I did not have that value set to True. However, after changing it, I still get the same result. Does the Seeq server need to be restarted or anything?

Yes it would. Please file a ticket in our support portal https://seeq.atlassian.net/servicedesk/customer/portal/3 for assistance enabling the email service? Thanks!
From: liz-luft @.>
Sent: Thursday, February 23, 2023 2:17 PM
To: seeq12/seeq-email-addon @.>
Cc: Chris Herrera @.>; Comment @.>
Subject: Re: [seeq12/seeq-email-addon] "Bad Gateway" Error (Issue #8)
Thanks for the quick response. You are correct in that I did not have that value set to True. However, after changing it, I still get the same result. Does the Seeq server need to be restarted or anything?
—
Reply to this email directly, view it on GitHubhttps://github.com/seeq12/seeq-email-addon/issues/8#issuecomment-1442443292, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABNGCD6L3BDY6ZTJEXAPGDDWY7HTPANCNFSM6AAAAAAVGDHF3U.
You are receiving this because you commented.Message ID: @.@.>>


text:
F: update import code style

This line confused my IDE a little.
As I searched through the project, only a few use import @. Most code prefer import ../.
Are they legacy code from previous repos?
Will fix more and include a changeset if approved.
[] I've included a changeset (psst. run yarn changeset. Read about changesets here).

This was added in: https://github.com/segmentio/analytics-next/commit/86b98572a24bfc7c8b6feea8a6feef1bdbe9202a

authors: hbrls silesky

repo: segmentio/analytics-next


text:
Release major node version

Other than a version bump, no real changes.

Looks good to me - will this be automatically updated without the version tag to 1.0.0 with the patch release?

Yep


text:
Autocomplete: allowOtherValues does not work

Steps to reproduce
Use the <Autocomplete/> component with allowOtherValues prop.
const Page = () => {
  const [value, setValue] = useState('')
  return (
    <div>
      <Autocomplete
        allowOtherValues
        id="autocomplete-test"
        onChange={setValue}
        items={[
          'red',
          'green',
          'yellow',
          'this does not render on the textbox but sets the state correctly'
        ]}
      >
        {({ getInputProps, getRef, openMenu, inputValue }) => {
          return (
            <TextInput
              ref={getRef}
              {...getInputProps({ onFocus: openMenu })}
              value={inputValue}
            />
          )
        }}
      </Autocomplete>
      <Button onClick={() => console.debug('value... ', value)}>
        Log Value
      </Button>
    </div>
  )
}

Hi @harish-prakash, what version are you using? I believe this was fixed with #1496 / https://github.com/segmentio/evergreen/releases/tag/v6.10.4. Here's a CodeSandbox with your example code: https://codesandbox.io/s/issue-1562-38zjfj?file=/src/App.tsx

I see that this was fixed in 6.10.4, I am using 6.10.3 🤦♂. Closing this issue 🙌

authors: brandongregoryscott harish-prakash

repo: segmentio/evergreen


text:
Acoustic Catalog initial submit

Initial Catalog entry for Acoustic (Actions) Destination
Merge timing
<!-- When should this get merged/published?

ASAP once approved, please.

Hi Folks,
As it's been two weeks without an update, can we get an idea of the timing to complete a review?
Thanks,

Thank you Thomas,
Appreciate all the help on getting this over the line,
Kip
Kip W. Landry
WW Solutions Architect
[signature_1720021682]
Email: @.*** @.***>
     How Can Acoustic Help?

Acoustic Help Centerhttps://help.goacoustic.com/hc/en-us
Subscribe for Product Updates and Releaseshttps://acoustic.com/client-signup/
New Product Releases
Acoustic Support Portalhttps://support.goacoustic.com/
Product Status Pages for Outages or Reduced Servicehttps://status.goacoustic.com/
Insights Help Documentationhttps://help.goacoustic.com/hc/en-us/categories/12538307189657-Insights
Acoustic Support Chathttps://support.goacoustic.com/
Insights Academy Traininghttps://learn.goacoustic.com/lms/index.php?r=site/sso&sso_type=saml&id_course=479&utm_source=shareButton&utm_content=course_link
Acoustic Academyhttps://learn.goacoustic.com/learn
Developer - REST API Referencehttps://api2.silverpop.com/restdoc/
Developer - API Referencehttps://developer.goacoustic.com/acoustic-campaign/reference/xml-api-overview-1
Feedback and Product Ideashttps://ideas.goacoustic.com/
Developer - Postman Collectionhttps://developer.goacoustic.com/acoustic-campaign/reference/postman-collection
Developer – API Endpoints and credentialshttps://developer.goacoustic.com/acoustic-campaign/reference/getting-started-with-oauth
From: Thomas Gilbert @.>
Date: Tuesday, May 14, 2024 at 1:08 PM
To: segmentio/segment-docs @.>
Cc: Kip Landry @.>, Mention @.>
Subject: Re: [segmentio/segment-docs] Acoustic Catalog initial submit (PR #6425)
@tcgilbert approved this pull request.
—
Reply to this email directly, view it on GitHubhttps://github.com/segmentio/segment-docs/pull/6425#pullrequestreview-2055975815, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYV2WAF34P3NDTV35SQKQW3ZCJAINAVCNFSM6AAAAABGU2EMRSVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDANJVHE3TKOBRGU.
You are receiving this because you were mentioned.Message ID: @.***>
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain Acoustic proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

Hi Thomas,
Yes, we’re ready to move forward, we’ve had a beta with two Customers running for a fair few months now and there are no issues to resolve at this point, we’ll only be adding additional features from this point forward,
Many Thanks,
Kip
Kip W. Landry
WW Solutions Architect
[signature_1720021682]
Email: @.*** @.***>
     How Can Acoustic Help?

Acoustic Help Centerhttps://help.goacoustic.com/hc/en-us
Subscribe for Product Updates and Releaseshttps://acoustic.com/client-signup/
New Product Releases
Acoustic Support Portalhttps://support.goacoustic.com/
Product Status Pages for Outages or Reduced Servicehttps://status.goacoustic.com/
Insights Help Documentationhttps://help.goacoustic.com/hc/en-us/categories/12538307189657-Insights
Acoustic Support Chathttps://support.goacoustic.com/
Insights Academy Traininghttps://learn.goacoustic.com/lms/index.php?r=site/sso&sso_type=saml&id_course=479&utm_source=shareButton&utm_content=course_link
Acoustic Academyhttps://learn.goacoustic.com/learn
Developer - REST API Referencehttps://api2.silverpop.com/restdoc/
Developer - API Referencehttps://developer.goacoustic.com/acoustic-campaign/reference/xml-api-overview-1
Feedback and Product Ideashttps://ideas.goacoustic.com/
Developer - Postman Collectionhttps://developer.goacoustic.com/acoustic-campaign/reference/postman-collection
Developer – API Endpoints and credentialshttps://developer.goacoustic.com/acoustic-campaign/reference/getting-started-with-oauth
From: Thomas Gilbert @.>
Date: Tuesday, May 14, 2024 at 1:10 PM
To: segmentio/segment-docs @.>
Cc: Kip Landry @.>, Mention @.>
Subject: Re: [segmentio/segment-docs] Acoustic Catalog initial submit (PR #6425)
@KWLandry-acoustichttps://github.com/KWLandry-acoustic thanks for making those updates. @pwseghttps://github.com/pwseg from our docs team will give a final review and get this through for you.
Do you have a timeline for when you want your integration to go live? We have everything needed on our end. As long as you have tested your integration and ensured it is behaving as expected we can move it into Public Beta.
—
Reply to this email directly, view it on GitHubhttps://github.com/segmentio/segment-docs/pull/6425#issuecomment-2110733093, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYV2WAAHRSDI3XZHW2TYV4LZCJARTAVCNFSM6AAAAABGU2EMRSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJQG4ZTGMBZGM.
You are receiving this because you were mentioned.Message ID: @.***>
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain Acoustic proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

@tcgilbert Merging this now, it'll be live after our regular Thursday deploy.

authors: KWLandry-acoustic pwseg

repo: segmentio/segment-docs


text:
Bug fix: objective reaction not adhering to upper bound

Bug description: In FBACell.run, the upper bound on the biomass reaction is set to be equivalent to the rate that would fill the current cell. This overrides the limit set in the model file, which we may want to limit. For example, I discovered this when trying knockouts of every reaction, and the model that knocks out the "growth" reaction still grew.
Sorry for not making this change myself, turns out my local code base is kind of screwy since I didn't properly migrate to the github repo. Could one of you please make the following changes?
Step 1: Modify FBACell.run(model[]) to change the part that says
/************************* SET MAX BIOMASS *****************************/
((FBAModel)models[i]).setObjectiveUpperBound((cParams.getMaxSpaceBiomass() - (Utility.sum(biomass) + Utility.sum(deltaBiomass))) / (biomass[i] * cParams.getTimeStep()));
to
/************************* SET MAX BIOMASS *****************************/
double bioUB = ((FBAModel)models[i]).getBaseUB()[((FBAModel)models[i]).getBiomassReaction()];
double capacityUB = (cParams.getMaxSpaceBiomass() - (Utility.sum(biomass) + Utility.sum(deltaBiomass))) / (biomass[i] * cParams.getTimeStep());
((FBAModel)models[i]).setObjectiveUpperBound(Math.min(bioUB, capacityUB));
Step 2: Add getBaseUB() to FBAModel
public double[] getBaseUB() { 		return baseUB; 	}

minor typo, dropped a parentheses: Should be
double capacityUB = (cParams.getMaxSpaceBiomass() - (Utility.sum(biomass) + Utility.sum(deltaBiomass))) / (biomass[i] * cParams.getTimeStep());
so all addition/subtraction is in the numerator

This should be fixed in my "signal bugfix" pull request.

authors: jeremymchacon mquintin

repo: segrelab/comets


text:
Could not initialize class com.letv.sarrsdesktop.blockcanaryex.BlockCanaryExPlugin

Applying BlockCanaryExPlugin 0.9.9.5 apply plugin: 'blockcanaryex' fails on Android Studio 3.1.1. and Gradle 3.1.1  with
org.gradle.api.plugins.PluginInstantiationException: Could not create plugin of type 'BlockCanaryExPlugin'.
	at org.gradle.api.internal.plugins.DefaultPluginManager.instantiatePlugin(DefaultPluginManager.java:74)
	at org.gradle.api.internal.plugins.DefaultPluginManager.producePluginInstance(DefaultPluginManager.java:183)
	at org.gradle.api.internal.plugins.DefaultPluginManager.addPlugin(DefaultPluginManager.java:159)
	at org.gradle.api.internal.plugins.DefaultPluginManager.access$200(DefaultPluginManager.java:47)
	at org.gradle.api.internal.plugins.DefaultPluginManager$AddPluginBuildOperation.run(DefaultPluginManager.java:252)
	at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
	at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)
	at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199)
	at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110)
	at org.gradle.api.internal.plugins.DefaultPluginManager.doApply(DefaultPluginManager.java:144)
	at org.gradle.api.internal.plugins.DefaultPluginManager.apply(DefaultPluginManager.java:125)
	at org.gradle.api.internal.plugins.DefaultObjectConfigurationAction.applyType(DefaultObjectConfigurationAction.java:120)
	at org.gradle.api.internal.plugins.DefaultObjectConfigurationAction.access$200(DefaultObjectConfigurationAction.java:38)
	at org.gradle.api.internal.plugins.DefaultObjectConfigurationAction$3.run(DefaultObjectConfigurationAction.java:86)
	at org.gradle.api.internal.plugins.DefaultObjectConfigurationAction.execute(DefaultObjectConfigurationAction.java:143)
	at org.gradle.api.internal.project.AbstractPluginAware.apply(AbstractPluginAware.java:46)
	at org.gradle.api.internal.project.ProjectScript.apply(ProjectScript.java:34)
	at org.gradle.api.Script$apply.callCurrent(Unknown Source)
	at build_b1ys5e8qfk52p84cbe1hfm92m.run(/home/erik/src.local/wifi_led_stripes/app/app/build.gradle:122)
	at org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:90)
	at org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl$2.run(DefaultScriptPluginFactory.java:204)
	at org.gradle.configuration.ProjectScriptTarget.addConfiguration(ProjectScriptTarget.java:77)
	at org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.apply(DefaultScriptPluginFactory.java:209)
	at org.gradle.configuration.BuildOperationScriptPlugin$1.run(BuildOperationScriptPlugin.java:61)
	at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
	at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)
	at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199)
	at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110)
	at org.gradle.configuration.BuildOperationScriptPlugin.apply(BuildOperationScriptPlugin.java:58)
	at org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:41)
	at org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:26)
	at org.gradle.configuration.project.ConfigureActionsProjectEvaluator.evaluate(ConfigureActionsProjectEvaluator.java:34)
	at org.gradle.configuration.project.LifecycleProjectEvaluator.doConfigure(LifecycleProjectEvaluator.java:64)
	at org.gradle.configuration.project.LifecycleProjectEvaluator.access$100(LifecycleProjectEvaluator.java:34)
	at org.gradle.configuration.project.LifecycleProjectEvaluator$ConfigureProject.run(LifecycleProjectEvaluator.java:110)
	at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
	at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)
	at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199)
	at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110)
	at org.gradle.configuration.project.LifecycleProjectEvaluator.evaluate(LifecycleProjectEvaluator.java:50)
	at org.gradle.api.internal.project.DefaultProject.evaluate(DefaultProject.java:667)
	at org.gradle.api.internal.project.DefaultProject.evaluate(DefaultProject.java:136)
	at org.gradle.execution.TaskPathProjectEvaluator.configure(TaskPathProjectEvaluator.java:35)
	at org.gradle.execution.TaskPathProjectEvaluator.configureHierarchy(TaskPathProjectEvaluator.java:62)
	at org.gradle.configuration.DefaultBuildConfigurer.configure(DefaultBuildConfigurer.java:38)
	at org.gradle.initialization.DefaultGradleLauncher$ConfigureBuild.run(DefaultGradleLauncher.java:261)
	at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
	at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)
	at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199)
	at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110)
	at org.gradle.initialization.DefaultGradleLauncher.configureBuild(DefaultGradleLauncher.java:173)
	at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:132)
	at org.gradle.initialization.DefaultGradleLauncher.getConfiguredBuild(DefaultGradleLauncher.java:110)
	at org.gradle.internal.invocation.GradleBuildController$2.call(GradleBuildController.java:87)
	at org.gradle.internal.invocation.GradleBuildController$2.call(GradleBuildController.java:84)
	at org.gradle.internal.work.DefaultWorkerLeaseService.withLocks(DefaultWorkerLeaseService.java:152)
	at org.gradle.internal.invocation.GradleBuildController.doBuild(GradleBuildController.java:100)
	at org.gradle.internal.invocation.GradleBuildController.configure(GradleBuildController.java:84)
	at org.gradle.tooling.internal.provider.runner.ClientProvidedBuildActionRunner.run(ClientProvidedBuildActionRunner.java:64)
	at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)
	at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)
	at org.gradle.tooling.internal.provider.ValidatingBuildActionRunner.run(ValidatingBuildActionRunner.java:32)
	at org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner$1.run(RunAsBuildOperationBuildActionRunner.java:43)
	at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
	at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)
	at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199)
	at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110)
	at org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner.run(RunAsBuildOperationBuildActionRunner.java:40)
	at org.gradle.tooling.internal.provider.SubscribableBuildActionRunner.run(SubscribableBuildActionRunner.java:51)
	at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:49)
	at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:32)
	at org.gradle.launcher.exec.BuildTreeScopeBuildActionExecuter.execute(BuildTreeScopeBuildActionExecuter.java:39)
	at org.gradle.launcher.exec.BuildTreeScopeBuildActionExecuter.execute(BuildTreeScopeBuildActionExecuter.java:25)
	at org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:80)
	at org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:53)
	at org.gradle.tooling.internal.provider.ServicesSetupBuildActionExecuter.execute(ServicesSetupBuildActionExecuter.java:57)
	at org.gradle.tooling.internal.provider.ServicesSetupBuildActionExecuter.execute(ServicesSetupBuildActionExecuter.java:32)
	at org.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute(GradleThreadBuildActionExecuter.java:36)
	at org.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute(GradleThreadBuildActionExecuter.java:25)
	at org.gradle.tooling.internal.provider.ParallelismConfigurationBuildActionExecuter.execute(ParallelismConfigurationBuildActionExecuter.java:43)
	at org.gradle.tooling.internal.provider.ParallelismConfigurationBuildActionExecuter.execute(ParallelismConfigurationBuildActionExecuter.java:29)
	at org.gradle.tooling.internal.provider.StartParamsValidatingActionExecuter.execute(StartParamsValidatingActionExecuter.java:64)
	at org.gradle.tooling.internal.provider.StartParamsValidatingActionExecuter.execute(StartParamsValidatingActionExecuter.java:29)
	at org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute(SessionFailureReportingActionExecuter.java:59)
	at org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute(SessionFailureReportingActionExecuter.java:44)
	at org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute(SetupLoggingActionExecuter.java:45)
	at org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute(SetupLoggingActionExecuter.java:30)
	at org.gradle.launcher.daemon.server.exec.ExecuteBuild.doBuild(ExecuteBuild.java:67)
	at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
	at org.gradle.launcher.daemon.server.exec.WatchForDisconnection.execute(WatchForDisconnection.java:37)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
	at org.gradle.launcher.daemon.server.exec.ResetDeprecationLogger.execute(ResetDeprecationLogger.java:26)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
	at org.gradle.launcher.daemon.server.exec.RequestStopIfSingleUsedDaemon.execute(RequestStopIfSingleUsedDaemon.java:34)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
	at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.call(ForwardClientInput.java:74)
	at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.call(ForwardClientInput.java:72)
	at org.gradle.util.Swapper.swap(Swapper.java:38)
	at org.gradle.launcher.daemon.server.exec.ForwardClientInput.execute(ForwardClientInput.java:72)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
	at org.gradle.launcher.daemon.server.exec.LogAndCheckHealth.execute(LogAndCheckHealth.java:55)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
	at org.gradle.launcher.daemon.server.exec.LogToClient.doBuild(LogToClient.java:62)
	at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
	at org.gradle.launcher.daemon.server.exec.EstablishBuildEnvironment.doBuild(EstablishBuildEnvironment.java:82)
	at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
	at org.gradle.launcher.daemon.server.exec.StartBuildOrRespondWithBusy$1.run(StartBuildOrRespondWithBusy.java:50)
	at org.gradle.launcher.daemon.server.DaemonStateCoordinator$1.run(DaemonStateCoordinator.java:295)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
	at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.letv.sarrsdesktop.blockcanaryex.BlockCanaryExPlugin
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.gradle.api.internal.DependencyInjectingInstantiator.newInstance(DependencyInjectingInstantiator.java:81)
	at org.gradle.api.internal.plugins.DefaultPluginManager.instantiatePlugin(DefaultPluginManager.java:72)
	... 116 more

the same
dependencies {
    classpath 'com.android.tools.build:gradle:3.1.0'
    classpath 'com.letv.sarrsdesktop:BlockCanaryExPlugin:0.9.9.5'
}

我也遇到这个问题了，有解决方法吗

也遇到了这个问题，并且也加了
dependencies {
classpath 'com.android.tools.build:gradle:3.1.0'
classpath 'com.letv.sarrsdesktop:BlockCanaryExPlugin:0.9.9.5'
}

遇到同样的问题

我也是...  报这个错。

mine as well.
classpath 'com.android.tools.build:gradle:4.1.3'
classpath 'com.letv.sarrsdesktop:BlockCanaryExPlugin:0.9.9.5'

这是来自QQ邮箱的假期自动回复邮件。

您好，我最近正在休假中，无法亲自回复您的邮件。我将在假期结束后，尽快给您回复。

同样的问题，期待楼主适配。

这是来自QQ邮箱的假期自动回复邮件。

您好，我最近正在休假中，无法亲自回复您的邮件。我将在假期结束后，尽快给您回复。

authors: HeCaser PeterXiaosa eku lincocc louisLuo njzhangsan2013 yuqirong zyl409214686

repo: seiginonakama/BlockCanaryEx


text:
Support %%grid

the tool is amazing. I'm not sure why %%grid2 1 isn't working.
should look something like this.

grid2 isn't supported by abcjs, so not available in my tool.

authors: seisiuneer talthent

repo: seisiuneer/abctools


text:
dropdown option values are not adjusting with the parent dropdown when scrolling on modal popup

Prerequisites

[x] I have searched for similar issues in both open and closed tickets and cannot find a duplicate
[ ] The issue still exists against the latest master branch of Select2
[ ] This is not a usage question (Those should be directed to the community)
[ ] I have attempted to find the simplest possible steos to reproduce the issue
[ ] I have included a failing test as a pull request (Optional)

Steps to reproduce the issue

Expected behavior and actual behavior
When I follow those steps, I see...
I was expecting...
Environment
Browsers

[x] Google Chrome
[x] Mozilla Firefox
[x] Internet Explorer

Operating System

[x] Windows
[x] Mac OS X
[ ] Linux
[x] Mobile

Libraries

jQuery version:
Select2 version:

Isolating the problem

[ ] This bug happens on the examples page
[ ] The bug happens consistently across all tested browsers
[ ] This bug happens when using Select2 without other pluigns
[ ] I can reproduce this bug in a jsbin

Currently, we are using bootstrap modal popup. On popup i have ten dropdown boxes, fifth dropdown box has ten three dropdown option values. On Click of fifth dropdown, am scrolling on modal popup. The dropdown option values related to fifth dropdown remains in static position, option vales are not scrolling with respect to the parent dropdown.

It is unclear what the issue is here.  Without a jsbin or screenshots, we cannot determine the problem.

authors: ChanduSirigiri alexweissman