primordic/IssueDupesLite huggingface dataset:
Repository: cdnjs/cdnjs

Issue #13191: Incorrect unicode handling
Created: 2019-01-02T19:07:05Z
As reported in beautifier/js-beautify#1608
Compare this:
https://raw.githubusercontent.com/beautify-web/js-beautify/v1.8.9/js/lib/beautifier.min.js
https://cdn.rawgit.com/beautify-web/js-beautify/v1.8.9/js/lib/beautifier.min.js
https://cdnjs.cloudflare.com/ajax/libs/js-beautify/1.8.9/beautifier.min.js
In the regular expression in question:
// githubusercontent
e.identifier=new RegExp("[$@A-Z_a-zªµºÀ-ÖØ-öø-ˁˆ-ˑˠ-ˤˬˮͰ-ʹͶͷͺ-ͽΆ...")
// cdn.rawgit.com
e.identifier=new RegExp("[$@A-Z_a-zªµºÀ-ÖØ-öø-ˁˆ-ˑˠ-ˤˬˮͰ-ʹͶͷͺ-ͽΆ...")
// cdnjs
e.identifier=new RegExp("[$@A-Z_a-zÂªÂµÂºÃ€-Ã–Ã˜-Ã¶Ã¸-Ë�Ë...")
Not sure what is causing this.

Duplicate issue #13195: Incorrect jQueryValidate message arabic translate file
Created: 2019-01-05T18:56:57Z
Hello,
I encounter an error while using the file : "https://cdnjs.cloudflare.com/ajax/libs/jquery-validate/1.19.0/localization/messages_ar.js". The error is in the line 24.

Regards

Closing comment (2019-01-05T19:56:38Z): This issue appears to be an extension of a known issue reported in #13191
Repository: cdnjs/cdnjs

Issue #1638: Rename Twitter Bootstrap to Bootstrap
Created: 2013-07-31T01:14:28Z
@ryankirkman @thomasdavis
With the release of v3.0 of twitter bootstrap. it appears they have changed the name to just Bootstrap. Should we rename the library in cdnjs? or make a new library?

Duplicate issue #2128: twitter-bootstrap should be renamed "bootstrap
Created: 2013-11-11T21:08:06Z
twitter-bootstrap should be renamed "bootstrap

Closing comment (2013-12-09T00:32:14Z): Duplicate of #1638.
Repository: ceph/ceph-csi

Issue #826: Encrypt each RBD devices using uniquely generated ID in ceph-csi
Created: 2020-02-10T10:01:46Z
Describe the feature you'd like to have
What new functionality do you want?
currently, ceph-csi is supported only vault based encryption to encrypt each rbd device with unique Key, only one kubernetes secret will be used for encryption which will be provided in storage-class.
What is the value to the end user? (why is it a priority?)
if ceph-csi can generate its own secret and use it for encrypting the devices, the encryption will be more secure.
How would the end user gain value from having this feature?
How will we know we have a good solution? (acceptance criteria)
the ceph-csi can create/get a secret and update the secret with some imageID as key and the value as the unique key, the plugin who is responsible for encrypting and decrypting the rbd image can make use of a secret.
we can mount the secrets to some path in pod spec. but it will slow down the operation as the dynamic update of secrets takes some time to reflect in the pod as kubelet needs to sync the secrets and pod volume mounts.
Concern:

ceph-csi need to make sure the secret data is not corrupted when multiple instances are accessing it.
ceph-csi should not generate the different Keys for single RBD image if it's mounted on different nodes

Duplicate issue #1537: Enable Per PV unique key encryption when using "secret" based encryption for RBD 
Created: 2020-09-29T06:05:58Z
Describe the feature you'd like to have
While using secret based encryption at present, the PVCs are encrypted with a single passphrase which is in nodestage/provisioner secret. All the PVCs created on top of this sc will be encrypted with the same key/passphrase. The request here is to enable the encryption on this method with different keys.
I could think of few solutions as below, but I dont see this as an proper solution to sort this issue out:

Create Secrets per PV by the CSI driver -> Not possible as CSI driver don't talk to the API server directly.
Update existing secret for PV in nodestage and nodeprovisioner secret -> Not possible as CSI driver don't talk to the API server directly.
Generate and Store it in PV volume context -> Not recommended as it should not contain sensitive information.
Generate and Store it in OMAP -> Whoever got access to ceph pool got complete access so this is not a recommended solution.
Generate and Store it in RBD image metadata -> whoever got access to the ceph pool or image got complete access, again this is not a recommended solution.
One other solution would be having a brand new sidecar or controller which does the secret injection, but this needs heavy thought and may not want to be considered in this repo.

Inviting thoughts if any.
@vasyl-purchel @dillaman @JohnStrunk @ShyamsundarR

Closing comment (2020-09-29T06:12:10Z): isn't it almost same as #826
Repository: ceph/ceph-csi

Issue #1096: Add liveness sidecar to ceph csi drivers
Created: 2020-05-22T10:22:08Z
The CSI livenessprobe is a sidecar container that monitors the health of the CSI driver and reports it to Kubernetes via the Liveness Probe mechanism. This enables Kubernetes to automatically detect issues with the driver and restart the pod to try and fix the issue.

Duplicate issue #4482: support  liveness probe configure in kubernetes yaml
Created: 2024-03-08T08:21:17Z
Describe the feature you'd like to have
When the liveness check fails, the container should be restarted. Currently, the failure of the check can only be determined through the /metrics path with csi_liveness as shown below:
$ curl 10.46.1.6:8680/metrics|more
# HELP csi_liveness Liveness Probe
# TYPE csi_liveness gauge
csi_liveness 0


This is not very friendly for pod probe checks in Kubernetes. A common way to check pods is through the following method:
livenessProbe:
  httpGet:
    host: 127.0.0.1
    path: /healthz
    port: 8080
    scheme: HTTP
  failureThreshold: 8
  initialDelaySeconds: 15
  periodSeconds: 10
  successThreshold: 1
  timeoutSeconds: 15

Could you provide an endpoint for liveness to facilitate probe checks?
What is the value to the end user? (why is it a priority?)
When a health check fails, the container can be restarted instead of showing as running but not being able to do anything.
How will we know we have a good solution? (acceptance criteria)

 add new healthz endpoint, like /healthz

Closing comment (2024-03-12T11:48:58Z): @yylt is this duplicate of #1096?
Repository: ceph/ceph-csi

Issue #1483: Add storageclass definition and secret on file values
Created: 2020-09-16T10:18:34Z
Hi all,
I would like to bring to your attention an helpful improvment giving the possibility to set the storageclass definition and the secret directly on file values.
In our case we need to create sc definition and secret applying custom yaml files after the installation of ceph-csi-rbd by helm chart.
Below are the versions of chart and appl. used in our environment based on k8s 1.9.1:
appl.: v3.1.0
chart: ceph-csi-rbd-3.1.0

Duplicate issue #1765: Storage Class should be included with the helm charts
Created: 2020-12-04T17:32:33Z
Describe the feature you'd like to have
What new functionality do you want?

I would like to have to the ability to deploy a Storage Class when using the helm chart.
This means the helm chart should handle creating the csi-<rbd/cephfs>-secret as well.

What is the value to the end user? (why is it a priority?)
How would the end user gain value from having this feature?

The user would be able to deploy their desired csi quicker and easier.
There is no reason not to include both the secret and storage creation as csi is useless without a storage class. This should be included in both helm charts, other csi helm charts include a retain and a delete version of storage class.

How will we know we have a good solution? (acceptance criteria)
Add a list of criteria that should be met for this feature to be useful

I should be able to apply the helm charts and then be able to kubectl get storageclass -A and see the respective storage classes

Additional context
Add any other context or screenshots about the feature request here.

All of the documentation around this csi includes steps for creation the secret and the storage class. This should be included in the helm chart

Closing comment (2020-12-07T07:37:30Z): @ba-work Thanks for creating the issue. This looks to be the duplicate of #1483. closing it for the same reason, please feel free to reopen if its not.
Repository: ceph/ceph-csi

Issue #2032: [RBD] Support Regional DR for Encrypted PVC
Created: 2021-04-28T12:32:40Z
Currently, encryption is only supported for the PVC without mirroring., This issue is to track the support for encryption of mirrored PVC.
To complete the Whole DR story (failover and failback) the volume should be usable by the applications on the primary cluster.
The KMS setup is something up to the admins how they want to handle it and how they want to migrate the information from one KMS instance to another during the failover and failback operation it is left to them.
We need to test all the different KMS we support in cephcsi.

Duplicate issue #2027: Test encryption on mirrored image in Regional DR fail-over
Created: 2021-04-28T05:50:17Z
we need to test and make the encryption works on the mirrored image in case of Failover in regional DR

Closing comment (2021-05-10T08:55:31Z): dup of #2032, closing
Repository: ceph/ceph-csi

Issue #1188: Tracker to fix todo in #1160 snapshot PR
Created: 2020-06-26T08:41:34Z
This issue is for tracking the TODO which needs to be fixed after merging #1160, this will be closed after fixing all the todo's
for easier tracking am adding the TODO list here from the PR

 Create PVC from PVC
  Fix issues with snapshot/clone (510) limits #1098
 Add list of kernel versions that supports deep-flatten feature
  Allow Parallel cloning and snapshots creation on one PVC/clone (Need to work on in-memory locking)
  Check Anything Needed to support datapool
  Add doc file for the commands
  If required some code cleanup
  Replace GetStoredImageID with GetImageAttributes in all places
 Various calls to deleteImage does not need the rbdStatus check. That is only required when calling from DeleteVolume. Suggest a TODO to optimize the same outside of the deleteImage call Other callers: cleanUpSnapshot, createRBDClone, createBackingImage, checkFlatten
 Handle Bigger size Restore and Clone

Duplicate issue #1230: Parallelize the Snapshot Create and Restore and PVC-PVC cloning
Created: 2020-07-12T03:05:16Z
With the current implementation, the locking is taken based on the ID. if the lock already exists we return operation already exists Error Message, This works fine for Volume create/Delete/Resize. The current locking makes the operation serialized When its come for snapshot create and delete we need to take a lock on the parent volume when we are creating and deleting to Ensure that the parent volume should not be deleted or resized when we are taking a snapshot, This Holds true when we are restoring a snapshot into a new RBD image also.
During the cloning operation


Snapshot Restore:- When we get a request to Restore a snapshot to a new RBD Imae, we need to take a lock on the snapshot and also we need to ensure that the snapshot should not be deleted when restore operation is going on


Image to Image Clone:- When we get a request to Create an RBD Image-Image cloning we need to ensure that the request parent image should not be deleted or Resized when we are creating an RBD Image-Image cloning.


If we take an Operation based locking this helps in allowing parallel operation, Which means we can create parallel snapshots on an RBD image in a given time. Even We can Restore snapshots and Create Clones from an RBD image.

Closing comment (2020-07-12T03:05:50Z): This is tracked in  #1188
Repository: ceph/ceph-csi

Issue #1356: Expand Volume Health monitoring via VolumeCondition field in CSI RPC of Controller and Node
Created: 2020-08-11T12:27:45Z
Describe the feature you'd like to have
There is an enhancement in NodeGetVolumeStats() which gives provision for us to inform the volume condition of the PV. This is an optional interface and informational message at this moment. However it would be good if we can extend the current interface with this information.

 nodeGetVolumeStats() can be expanded for volumeCondition field , one simple check here would be checking the state of the mountpoint inside the node
 Validate the controller capabilties of get/list volume + volume condition field :
Implementhing the listVolumes may be costly operation for volume health, however getVolume for volume condition could be used to check the volume exist in the backend or not..etc and populate the response back to the user.

kubernetes/enhancements#1432
### Tasks
- [ ] report VolumeConfition for CephFS (#4125)

Duplicate issue #2794: Implement `VOLUME_CONDITION` capability
Created: 2022-01-19T12:07:36Z
Describe the feature you'd like to have
Healer Controller checks if a volume is still mounted and usable. To check whether a volume is usable, the CSI driver shall check if filesystem is corrupted, whether there are bad blocks, etc. in this RPC.
Instead of adding a new RPC, we can leverage the existing NodeGetVolumeStats RPC.
In the NodeGetVolumeStatsRequest, there are volume_id, volume_path, and staging_target_path. CSI driver can figure out whether a volume is still mounted based on these parameters.
A new message volume_condition will be added to NodeGetVolumeStatsResponse. A new Node capability VOLUME_CONDITION will be added to indicate whether a CSI driver has implemented this function. In a volume_condition message, there is a boolean parameter abnormal indicating whether the volume is normal or not and a message that describes the details of the volume condition.
What new functionality do you want?
Provide a way to check the volume health status
What is the value to the end-user? (why is it a priority?)
The healer controller can leverage this to auto-fix the volume without user intervention.
Additional context
Read more at https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1432-volume-health-monitor#add-node-volume-health-function

Closing comment (2022-02-17T09:10:07Z): @pkalever isnt this issue duplicate of #1356 ?

Nope, this is a subtask, the issue you pointed out intends to implement this for both controller and node, but this issue is only covers node cap. Thanks!

SubTasks can be part of Parent Issue Tracker.. Will add to that any way.. Thanks .
Repository: ceph/ceph-csi

Issue #421: document the differences between the three cephcsi images
Created: 2019-06-10T17:39:27Z
What new functionality do you want?
I would like a paragraph of documentation that describes the differences in the three images we publish:

cephcsi/cephfsplugin
cephcsi/rbdplugin
cephcsi/cephcsi

The differences between these three are not clear to me. I suspect cephfsplugin and rbdplugin are going to go away at some point, but this is just a wild guess. If they are going away, why are they still around now? When should users expect them to disappear?
How would the end user gain value from having this feature?
Users have a clear understanding of what the three images are, and why consume one or the other.
This is also important to know how we want to package and ship these downstream in Red Hat's OpenShift Container Storage 4 product.

Duplicate issue #424: ceph versions supported by ceph-csi
Created: 2019-06-12T05:48:08Z
we need to add a matrix related to the minimum and maximum version of ceph supported by the ceph-csi driver.

Closing comment (2019-06-12T08:55:17Z): Similar to #421
Repository: chaitin/SafeLine

Issue #384: [建议] DDNS域名回源场景优化 / 动态解析 upstream 的域名
Created: 2023-10-16T12:46:11Z
背景与遇到的问题
默认情况下，Nginx只会在启动的时候解析一次upstream块里配置的域名。
原站为DDNS域名，当DDNS域名变化时，Nginx还会缓存原来的解析记录，导致链接超时，希望可以在Nginx配置上做一下兼容。
建议的解决方案
Tengine 是支持这种模式的，参考文档。http://tengine.taobao.org/document_cn/http_upstream_dynamic_cn.html

Duplicate issue #679: [Bug] 当上游服务器为域名的情况下，域名变更指向后不会刷新
Created: 2024-02-18T14:30:09Z
问题描述
防护站点当上游服务器是动态域名或域名的情况下，不会刷新DNS
编辑提交后会重新刷新一次
版本号
4.3.2
复现方法
1、将上游服务器设置为域名
2、变更域名的指向，将不会刷新DNS指向
期望的结果
希望可以自动更新域名的DNS指向

Closing comment (2024-02-19T10:20:47Z): duplicate，可以集中讨论：

#384
Repository: chaitin/SafeLine

Issue #209: [suggestion] Config Rate Limiting by host or website or urlpath / 频率限制基于 host 或站点或 URL
Created: 2023-08-10T09:38:19Z
背景与遇到的问题
目前只能基于时间和访问次数判断高频攻击，希望高频策略加入host和URL维度，这样就可以对重点接口进行CC防御
建议的解决方案
No response

Duplicate issue #406: [建议] 能否针对不同站点有不同的私有配置
Created: 2023-10-24T07:48:49Z
背景与遇到的问题
1、黑白名单
2、频率限制
目前都是全局配置，是否可以优化为站点的个性化配置，毕竟不同站点场景差别很大。
建议的解决方案
No response

Closing comment (2023-10-27T07:04:52Z): 黑白名单配置 host 就可以了
限频 duplicate：

#209
Repository: chaitin/SafeLine

Issue #63: 能否增加检测日志删除功能 / 自动清理历史日志 / 设置日志保留时间
Created: 2023-05-09T09:33:59Z
检测日志越来越多，能否增加一个日志占用百分比自动删除，或者手动可以按照时间批量删除日志的功能？

Duplicate issue #588: [建议] 增加日志保存天数的功能
Created: 2024-01-09T10:36:00Z
背景与遇到的问题
No response
建议的解决方案
No response

Closing comment (2024-01-15T09:36:40Z): duplicate:

#63
Repository: chaitin/SafeLine

Issue #749: [建议] 5.0.0 强制用户使用账号密码登录，能否改为可选项功能，由使用者自己选择是否开启？
Created: 2024-03-14T08:22:29Z
背景与遇到的问题
我已经习惯了以往的OTP登录方式，很实用，不用去记账号密码，密码太多了，容易忘记，现在变成强制要使用账号密码+OTP 登录，很麻烦。
建议的解决方案
登录方式改为可选项功能，由使用者自己选择是否开启。

Duplicate issue #795: [建议] 默认的账号名可以修改
Created: 2024-04-02T03:12:22Z
背景与遇到的问题
建议将后台登录的账号密码和直接 totp 验证登录，做成二选一的方式，可以自由选择使用哪种，而不是现在强制开启账号密码登录
建议的解决方案
后台中可以配置，是否开启账号密码登录，开启后是否开启 totp 二步验证，且账号可以修改[是谁想出来的账号不允许修改的，出来挨打！！！]
关闭账号密码登录，totp 为强制开启，开启账号密码，totp 为可选开启

Closing comment (2024-04-02T03:41:25Z): 第一个 duplicate：

#749
Repository: chaitin/SafeLine

Issue #137: 支持配置管理页面允许登录的 IP 地址 / 登录 IP 白名单 / Restrict Admin Access by IP Address
Created: 2023-07-07T01:13:29Z
1、管理页面在客户端IP地址无变化的情况下，未点击退出系统。下一次登录雷池的时候直接免密码登录到系统中了。
2、建议对于管理页面增加一个只允许哪些IP地址可以访问的限制。
3、强制登录后多少分钟之后无操作自动退出管理页面。

Duplicate issue #510: Limit IP access to admin page
Created: 2023-12-10T08:33:56Z
背景与遇到的问题
I want to limit ip access to waf admin page
建议的解决方案
No response

Closing comment (2023-12-14T07:52:23Z): Duplicate，可以到这里集中讨论和跟进:

#137

不过这个可以通过防火墙规则等方式实现，所以目前优先级不是很高。But it can be achieved through other methods such as firewall, so the priority is not very high at present.
Repository: chaitin/SafeLine

Issue #111: [建议] 出一个证书夹功能 / 证书管理
Created: 2023-06-28T03:40:46Z
有些站点是共用的一个Wildcard通配符证书，有个证书夹直接选已保存的证书就行了，不用一个个复制粘贴/上传。而且，更重要的，更换新证书的时候只要到证书夹里更新一次对应的证书就可以啦，不用重复操作。

Duplicate issue #204: [建议] 增加证书管理管理
Created: 2023-08-09T09:15:13Z
背景与遇到的问题
在添加站点时,xxx.a.com,yyy.a.com,ccc.a.com都是同一域名的证书，建议增加一个证书管理模块，自动匹配域名证书，不用在添加站点时反复上传同一个文件。
建议的解决方案
No response

Closing comment (2023-08-10T07:23:15Z): duplicate：

#111

搜 “证书管理” 就可以找到了。
Repository: chaitin/SafeLine

Issue #90: [建议] 通过界面进行站点与系统配置的备份与还原
Created: 2023-06-01T10:21:37Z
希望防护站点-站点配置能批量导入导出

Duplicate issue #875: [建议] 希望可以增加对配置的导入导出功能
Created: 2024-05-12T03:27:08Z
背景与遇到的问题
No response
建议的解决方案
No response

Closing comment (2024-05-23T10:33:04Z): duplicate:

#90
Repository: chaitin/SafeLine

Issue #363: [建议] 增加前台拦截页面多语种显示 / 拦截页面支持英文 / 人机页面支持英文
Created: 2023-10-09T07:04:26Z
背景与遇到的问题
我的业务主要是外贸网站，访问人群主要是国外用户，目前的拦截页面是写死的中文显示。
建议的解决方案
建议增加根据浏览器识别语言，或者在后台增加相关页面的标题及文本设置。

Duplicate issue #395: [建议] 拦截界面添加英文提示
Created: 2023-10-20T09:30:10Z
背景与遇到的问题
目前的拦截界面是中文的，但是访问用户不全是中国的
建议的解决方案
建议拦截页面和人机界面都加上英文，中英文同时展示

Closing comment (2023-10-23T08:37:20Z): duplicate：

#363
Repository: chaitin/SafeLine

Issue #145: [suggestion] Access Log / 希望平台后续可以增加一个记录网站访问日志的功能，可选启用
Created: 2023-07-08T09:08:17Z
我查看了官网技术文档中的《如何记录所有访问雷池的请求》并做了配置，发现修改nginx配置并不能记录完整的请求和响应日志（好像是nginx本身不支持记录响应包，不确定）。
希望平台后续可以增加一个可以全量记录网站访问日志的功能，记录完整的请求包与响应包，可以让用户自几选择是否开启该功能，可以参考当前检测日志中的日志详情一样展示。
如果有了网站的访问日志记录，在发现网站被攻击的时候，我们可以根据攻击者IP，去检索近期攻击者的所有访问请求，便于分析攻击行为和目的。访问日志的作用可以方便用于很多的安全分析工作中。我还是比较期待这个功能！
雷池WAF真的很好用！希望越来越好！

Duplicate issue #246: 能否增加一个全量流量的日志记录，默认不开启，用户自己选择是否开启[建议] 
Created: 2023-08-21T09:47:21Z
背景与遇到的问题
有的时候，不知道攻击时候成功，还不能看清楚整体的攻击链条
建议的解决方案
No response

Closing comment (2023-08-22T03:33:18Z): duplicate:

#145

btw 真实使用中，网站每天几十万几百万访问，就算有未知的攻击成功，waf 没检测出来的话，手动翻也没什么可能翻得到的。
Repository: chaitin/SafeLine

Issue #209: [suggestion] Config Rate Limiting by host or website or urlpath / 频率限制基于 host 或站点或 URL
Created: 2023-08-10T09:38:19Z
背景与遇到的问题
目前只能基于时间和访问次数判断高频攻击，希望高频策略加入host和URL维度，这样就可以对重点接口进行CC防御
建议的解决方案
No response

Duplicate issue #708: [建议] 为不同的网站配置不同的频率限制规则
Created: 2024-02-27T03:15:59Z
背景与遇到的问题
有没有办法为每个帐户设置速率限制？ 我有几个网站，需要为每个不同的网站设置速率限制
-- from 社区群 Daniel Huynh
建议的解决方案
No response

Closing comment (2024-02-27T07:13:07Z): duplicate:

#209
Repository: chakra-ui/chakra-ui

Issue #1121: [Stack] Setting margin prop on children of Stack has no affect
Created: 2020-07-03T18:14:39Z
On Discord, hosmelq reported that adding margin to a child component of the Stack component doesn't do anything. This is due to the generated class having a higher precedence.


In the screen shot above, the third box should have been pulled all the way to the right.
This issue can been seeing in the latest 1.0 build.

Duplicate issue #1128: [Stack][V1] Stack spacing overrides children margins
Created: 2020-07-04T13:43:25Z
Currently Stack uses *:not(style) ~ *:not(style) but this selector has more specificity (read more here) than the class applied by emotion to stack children
A solution would be to add the !important to every margin style applied to child of stack, so we should document that
A sandbox with an example
https://codesandbox.io/s/upbeat-wind-s45ww?file=/src/App.js

Closing comment (2020-07-05T01:22:20Z): Duplicate of #1121. I've reposted your comment there as it has useful information :)
Repository: chakra-ui/chakra-ui

Issue #2264: Add a search to documentation
Created: 2020-10-18T15:30:55Z
Feature request
Add a search to documentation
Is your feature request related to a problem? Please describe.
Sometimes I know the component I want, but I want to see attributes or examples and it would be easier with the search...
Describe the solution you'd like
Add search to documentation
Describe alternatives you've considered

Additional context
A search is missing to facilitate and find information.
Yesterday I was showing the chakra to a friend, but I was lost in the doc and a search would have saved several minutes already ... Outside it would be +1 chakra user ...

Duplicate issue #2603: Docs 1.0: Add SearchField and/or order components alphabetically
Created: 2020-11-24T16:18:30Z
Feature request
Is your feature request related to a problem? Please describe.
With 0.8 the component docs are sorted alphabetically, so you can find what you are looking for pretty fast.
With 1.0 the component list is sorted by semantics. This makes it really hard to find the docs for specific components. For example to find the docs for the Accordion component you have to know that it is filed under "disclosure" and where that group is sorted relative to the other groups.
Describe the solution you'd like
Either provide a top bar search field to look up specific component docs or provide the possibility to sort the components alphabetically. I personally dislike the semantical grouping. It makes sense for a kitchen sink like showcase, but users of chakra will most likely be using the docs to lookup specific components as fast as they can.

Closing comment (2020-11-24T16:23:00Z): Hi @JohannesKlauss, I'm going to close this as a duplicate of #2264 for now. I agree that it's hard to find things but we're working on adding search functionality currently. If adding search doesn't resolve this, we can definitely revisit a flattened sidebar later.
Repository: chakra-ui/chakra-ui

Issue #4776: Number Input increment / decrement sometimes require 2 clicks at min / max respectively.
Created: 2021-10-01T12:06:31Z
Description
With the mobile spinner (Number Input) example from the docs, when the spinner is at its minimum it sometimes requires two clicks on the increment button to actually do anything (and vice-versa to decrement at max value)
Link to Reproduction
https://codesandbox.io/s/chakra-ui-number-input-inc-dec-bug-dfuq2
Steps to reproduce

Visit Sandbox and open console
Click minus button to decrement to minimum value of 1
Click on plus button to increment
Expect value to increase to 2 but remains at 1
Click plus button again to increment
Value finally increases to 2

Chakra UI Version
1.6.8
Browser
Brave V1.30.86
Operating System

 macOS
 Windows
 Linux

Additional Information

Duplicate issue #5118: Issue with limits on useNumberInput hook
Created: 2021-11-19T08:34:49Z
Description
When I reach the min/max limit while using the useNumberInput hook it takes me 2 clicks to increment/decrement
Link to Reproduction
https://chakra-ui.com/docs/form/number-input#create-a-mobile-spinner
Steps to reproduce

Keep on decrementing till you hit the lower limit
Click on the + button. The number doesn't increment .
Click on + button again the number starts to increment.

Attaching the screen recording for the same:

  
    
    

    Screen.Recording.2021-11-19.at.1.51.07.PM.mov
    
  

  

  


Chakra UI Version
1.6.10
Browser
Google Chrome 95.0.4638.69
Operating System

 macOS
 Windows
 Linux

Additional Information
On further inspection observed the update function keeps on getting called recursively when the lower limit is reached. When the user clicks + first time the recursive call stops and then the update gets called with the new value.

Closing comment (2021-11-24T06:53:22Z): Thanks for contributing. I'm going to close this as it looks like it's a duplicate of #4776 which has a PR #4982 submitted to fix the issue.
Repository: chakra-ui/chakra-ui

Issue #6855: Dark mode is broken in storybook after upgrading to @chakra/react 2.3.5
Created: 2022-10-19T19:33:42Z
Description
When I toggle dark mode in storybook, I expect to see the dark version of a button but it doesn't work as expected
Link to Reproduction
https://github.com/blechatellier/strokybook-chakra-bug
Steps to reproduce

Run yarn storybook
Go to the Button stories
Toggle dark mode

Chakra UI Version
2.3.5 and up
Browser
Version 1.42.88 Chromium: 104.0.5112.81 (Official Build) (64-bit)
Operating System

 macOS
 Windows
 Linux

Additional Information
Works with @chakra/react 2.3.4 and fails on 2.3.5 and 2.3.6

Duplicate issue #6922: Storybook-addon: Dark theme not working correctly. @chakra-ui/react@2.3.5 and above
Created: 2022-10-29T19:45:35Z
Description
Chakra UI in Storybook is not properly toggling theme after chakra-ui/react starting in version 2.3.5
Link to Reproduction
No starter template for storybook
Steps to reproduce

Create a storybook project using https://chakra-ui.com/getting-started/with-storybook and @chakra-ui/react@latest
Style a button with a light theme and a dark theme
Create a story for the button
Open the story in storybook and toggle the theme, notice that the button color is still the light theme
Install @chakra-ui/react@2.3.3 and restart storybook. Clear cache/cookies if necessary. Toggle the theme and notice that the button now correctly shows dark theme color.

Chakra UI Version
2.3.5 and 2.3.6
Browser
Chrome
Operating System

 macOS
 Windows
 Linux

Additional Information
https://chakra-ui.com/getting-started/with-storybook
Light mode:

Dark mode (@chakra-ui/react versions 2.2.4-2.3.4)

Dark mode (@chakra-ui/react versions 2.3.5-2.3.6)

Closing comment (2022-10-31T00:23:28Z): Closing this as it's a dup of #6855
Repository: chakra-ui/chakra-ui

Issue #2468: DrawerFooter doesn't appear in mobile browsers
Created: 2020-11-12T15:12:21Z
Bug report
Describe the bug
The DrawerFooter component is not appearing when a  Drawer is open in mobile browsers.  Tested on Chrome/Brave/Firefox/Safari on both Android and iOS
To reproduce


Click on "Open Drawer"
Drawer will open
Should see "Cancel" and "Upload File" buttons in lower right in DrawerFooter but do not appear on mobile browsers

Minimal reproduction
https://5neo3.csb.app/
Expected behavior
DrawerFooter component should appear when drawer is open
Screenshots

System information

OS: Android/iOS
Browser (if applies): Chrome/Brave/Firefox on Android - Safari on iOS
Version of @chakra-ui/core:  1.0.0-rc.8

Duplicate issue #2495: Modal footer hidden in mobile device
Created: 2020-11-14T11:34:28Z
Bug report
Describe the bug
When opening a modal, drawer footer is hidden in mobile devices
Screenshots

Suggestion
Change DrawerContent Height from 100vh to 100%

System information

OS: Android
Browser Chrome
Chakra Version 1.0
Device mobile

Thanks.

Closing comment (2020-11-14T12:55:10Z): Duplicate of #2468
Repository: chakra-ui/chakra-ui

Issue #5669: Floating UI (popper.js v3)
Created: 2022-03-01T19:22:54Z
Description
Implement Floating UI
https://floating-ui.com/
Problem Statement/Justification

smaller
faster
more features

Proposed Solution or API
https://floating-ui.com/
Alternatives
No response
Additional Information
No response

Duplicate issue #5784: Feature: Use FloatingUI over Popper
Created: 2022-03-28T19:53:47Z
Description
FloatingUI is super nice and very small. I also like some of it's primitives, particularly around scrolling (ie: arrow changing position, etc)
Problem Statement/Justification
While it seems to have dropped to the backburner, FloatingUI is cross platform and as such, may motivate more dev efforts into providing official RN support (one day). Here's a list of benefits: https://floating-ui.com/docs/motivation
Proposed Solution or API
https://floating-ui.com/
Alternatives
No response
Additional Information
No response

Closing comment (2022-04-09T00:51:41Z): duplicates #5669
Repository: chakra-ui/chakra-ui

Issue #4142: Hardcoded rem values vs using theme values
Created: 2021-06-02T08:54:06Z
We are currently integrating Chakra into an application that has a history of meddling with rem values. There are some weird font-sizes currently on the HTML element. To cut the story short, the base font-size for this app is now 10px.
So when I started integrating Chakra into the codebase, I first started with converting the base theme's spacing and sizes to px values so we can integrate Chakra cleanly. Once most of the codebase is working with Chakra, we can remove the font-sizes on the HTML element and also remove our theme overrides.
But, when trying out some random components, I noticed that not all of them strictly follow the spacings provided by the theme. The Switch component is a perfect example.
Is there any reason there are hardcoded values here (and maybe in other components)? Why are these not based on the theme?

Duplicate issue #4143: Hardcoded rem values vs using theme values
Created: 2021-06-02T08:54:50Z
We are currently integrating Chakra into an application that has a history of meddling with rem values. There are some weird font-sizes currently on the HTML element. To cut the story short, the base font-size for this app is now 10px.
So when I started integrating Chakra into the codebase, I first started with converting the base theme's spacing and sizes to px values so we can integrate Chakra cleanly. Once most of the codebase is working with Chakra, we can remove the font-sizes on the HTML element and also remove our theme overrides.
But, when trying out some random components, I noticed that not all of them strictly follow the spacings provided by the theme. The Switch component is a perfect example.
Is there any reason there are hardcoded values here (and maybe in other components)? Why are these not based on the theme?

Closing comment (2021-06-02T09:02:48Z): Look like GH was having issues, this is a duplicate of #4142
Repository: chakra-ui/chakra-ui

Issue #4623: `motion`izing Button component does not work
Created: 2021-08-25T14:06:25Z
Description
When I try to animate chakra-ui's Button component with framer-motion's motion() helper, the animation doesn't work
Link to Reproduction
https://codesandbox.io/s/chakra-button-framer-motion-bug-muxze?file=/src/Playground.js
Steps to reproduce

Click Toggle binary state button
Watch the first button changing BG gradient properly, the second one not so (only once - first time)

Chakra UI Version
1.6.6
Browser
Firefox Developer Edition, Chrome Dev Edition
Operating System

 macOS
 Windows
 Linux

Additional Information

  
    
    

    screencap-Firefox.Developer.Edition-2021-08-25---16-04-00.mp4
    
  

  

  


TL;DR:
This notation works:
<Button
  as={motion.button}
  {...motionConfig}
  animate={{
    backgroundImage: binary
      ? BG_GRADIENT_SOFT
      : BG_GRADIENT_SOFT_REVERSED,
  }}
>
This one doesn't:
const MotionButton = motion(Button)

...

<MotionButton
  {...motionConfig}
  animate={{
    backgroundImage: binary
      ? BG_GRADIENT_SOFT
      : BG_GRADIENT_SOFT_REVERSED,
  }}
>

Duplicate issue #4561: @chakra-ui/react >= 1.5 button elements are not compatible with framer-motion
Created: 2021-08-13T05:50:18Z
Description
When I click a button I expect the animations assigned to that button to occur.
Link to Reproduction
https://codesandbox.io/s/chakra-ui-framer-motion-example-forked-v5iir?file=/src/App.js
Steps to reproduce
After onClick causes a rerender, the whileHover and whileTap on a Chakra/Frame Motion button no longer work. This issue only presents itself after v1.4.2
Working Animated button (@chakra-ui/react:1.4.2)
https://codesandbox.io/s/chakra-ui-framer-motion-example-forked-70j93?file=/src/App.js:178-184
Failing Animated button (@chakra-ui/react:1.6.6)
https://codesandbox.io/s/chakra-ui-framer-motion-example-forked-v5iir?file=/src/App.js
Chakra UI Version
1.6.6
Browser
No response
Operating System

 macOS
 Windows
 Linux

Additional Information
No response

Closing comment (2021-09-09T10:30:10Z): Possibly a duplicate of #4623. I just pushed a fix for it.
How I fixed it:
The problem was related to how motion works under the hood. It seems to require a very stable ref to get it working correctly so I swapped out: mergeRefs function with a memoized useMergeRefs hook.
Repository: chalk/chalk

Issue #632: commonjs
Created: 2024-09-20T22:29:31Z
Instead of using ESM modules, you should also be able to use require CommonJS modules.
import chalk from "chalk"
or
const chalk = require('chalk')
currently only the first one works

Duplicate issue #641: commonjs
Created: 2024-12-20T18:10:27Z
hey, folks, do you have plans to publish chalk with both CommonJs and ESM using conditional exports?

Closing comment (2024-12-20T19:11:51Z): Duplicate of #632
Repository: chalk/chalk

Issue #549: something error please help 
Created: 2022-05-25T01:53:46Z
const chalk = require('chalk');
^
Error [ERR_REQUIRE_ESM]: require() of ES Module D:\nodejs\importExport\node_modules\chalk\source\index.js from D:\nodejs\importExport\import.js not supported.
Instead change the require of index.js in D:\nodejs\importExport\import.js to a dynamic import() which is available in all CommonJS modules.
at Object. (D:\nodejs\importExport\import.js:1:15) {
code: 'ERR_REQUIRE_ESM'
}
showing above type error

Duplicate issue #549: something error please help 
Created: 2022-05-25T01:53:46Z
const chalk = require('chalk');
^
Error [ERR_REQUIRE_ESM]: require() of ES Module D:\nodejs\importExport\node_modules\chalk\source\index.js from D:\nodejs\importExport\import.js not supported.
Instead change the require of index.js in D:\nodejs\importExport\import.js to a dynamic import() which is available in all CommonJS modules.
at Object. (D:\nodejs\importExport\import.js:1:15) {
code: 'ERR_REQUIRE_ESM'
}
showing above type error

Closing comment (2022-05-26T06:00:28Z): Duplicate of #549
Repository: chalk/chalk

Issue #1: Browser support?
Created: 2013-08-14T13:06:40Z
Are there plans for browser support, like colors has?

Duplicate issue #10: browser support
Created: 2014-01-30T15:55:43Z
would love to see browser support for this library:

http://stackoverflow.com/questions/7505623/colors-in-javascript-console
Multiple colors on same line: http://jsfiddle.net/yg6hk/5/

Closing comment (2014-01-30T16:05:28Z): Duplicate of #1
Since console.log coloring is so different it would be better as a separate module ;)
Repository: chalk/chalk

Issue #195: 2.1.0 release Breaking/Broken
Created: 2017-08-09T15:30:30Z
Platform: Windows Server 2012 R2
Console: Cmder
Node Version: v8.1.4
Example code that worked before 2.1.0 release:
const chalk = require('chalk');
const clk = new chalk.constructor({ enabled: true });

console.log(`${clk.bgBlue("Text with blue background")}${clk.bgMagenta("Text with magenta background")} ect`);
2.0.1:

2.1.0:

Duplicate issue #196: executing a script with babel-node doesn't show chalk colors 
Created: 2017-08-09T19:46:52Z
i'm using babel-cli to run some scripts in order to be transpiled before executed this scripts have some chalk colors but that doesn't show on the cli
here is a simple example
test.js
const chalk = require('chalk');

console.log(chalk.blue('Hello world!'));

CLI "'im using git bash"
node_modules/.bin/babel-node ./test.js
output

Closing comment (2017-08-17T11:28:48Z): Duplicate of #195
Repository: chalk/chalk

Issue #632: commonjs
Created: 2024-09-20T22:29:31Z
Instead of using ESM modules, you should also be able to use require CommonJS modules.
import chalk from "chalk"
or
const chalk = require('chalk')
currently only the first one works

Duplicate issue #633: should we support both esm and commonjs specifications?
Created: 2024-09-26T02:30:50Z
Now v4 is commonjs, v5 is esm, can we support both?

Closing comment (2024-09-26T04:12:15Z): Duplicate of #632
Repository: chalk/chalk

Issue #175: Truecolor methods crash when color is unsupported
Created: 2017-07-16T16:20:46Z
When supports-color returns false, supportsColor.level equals undefined here: https://github.com/chalk/chalk/blob/master/index.js#L22. This makes this.level equal undefined here https://github.com/chalk/chalk/blob/master/index.js#L75 and as a result, crashes when color is unsupported. This can be reproduced by executing a script with chalk output using child_process.spawn() and piping output to stdout.
The fix is to change this:
obj.level = options.level === undefined ? supportsColor.level : options.level;
to this:
obj.level = options.level === undefined ? (supportsColor.level || 0) : options.level;
I stumbled upon this issue when tests were passing in terminal and on Travis CI, but were failing when run by np.
I submitted a PR with a failing test here #174. If I didn't miss anything, I will modify this PR to fix the problem.
Note, that "regular" (e.g. chalk.blue()) methods don't fail.

Duplicate issue #176: Got a error when use `chalk.bgHex()` with arg `--no-color`
Created: 2017-07-17T05:19:24Z
const chalk = require('chalk');
try {
	chalk.bgHex('#cccccc')('message');
} catch (ex) {
	console.error(ex);
}
E:\work\gulp-reporter (master) (gulp-reporter@2.1.0)
$ node -v
v8.1.2

E:\work\gulp-reporter (master) (gulp-reporter@2.1.0)
$ node test.js --no-color
TypeError: Cannot read property 'hex' of undefined
    at Function.<anonymous> (E:\work\gulp-reporter\node_modules\chalk\index.js:98:57)
    at errors.map (E:\work\gulp-reporter\lib\formater.js:240:19)
    at Array.map (native)
    at formater (E:\work\gulp-reporter\lib\formater.js:235:18)
    at reporter (E:\work\gulp-reporter\lib\reporter.js:20:10)
    at getErrors.then.errors (E:\work\gulp-reporter\lib\gulp-plugin.js:19:19)

Closing comment (2017-07-21T18:42:10Z): duplicate of #175
Repository: chalk/chalk

Issue #272: Accommodating dark/light terminals, specifically for `chalk.blue/chalk.white/chalk.black`
Created: 2018-05-06T23:57:03Z
I have this question on SO:
https://stackoverflow.com/questions/50027162/determine-terminal-tty-background-color-at-runtime/50205367
I am looking to figure out how to make chalk.blue() and chalk.white()/chalk.black() readable.
Right now, if the user is using a light colored terminal, chalk.white() is gray
And if the user is using a dark colored terminal, chalk.black() is gray.
I am looking for something where the color scheme is readable for all terminals, however I can do it.

Duplicate issue #497: Detect if the terminal theme is light or dark
Created: 2021-07-07T13:28:42Z
It would be very useful to know the type of theme (light/dark) the terminal has.
In this way the dev can properly set the colors:

for light background to have dark colors
for dark background to have light colors

Currently if you want to specify even the generic colors Chalk provides, you end up with unusable ouput because the user might have a theme that do not work well with the colors.

Closing comment (2021-07-07T13:43:33Z): Duplicate of #272
Repository: chalk/chalk

Issue #2: Yellow and Magenta do not display in powershell
Created: 2013-08-14T16:49:36Z
I'm not sure what should be done about this, if anything.
Yellow isn't too much of a problem since it displays as white but magenta actually displays as the same colour as the powershell background which isn't exactly ideal.
The two options, as far as I can see, are:

leave it up to developers to use what is supported

In this case I think a notice about platform compatibility should be added to the readme


Use the 'intense' versions of these colours (they work)

Possibility of only using if on windows (although that will make chalk messy which is something I think you are very keen to avoid)
changes '\x1b[35m' to '\x1b[95m'



In addition to those colours italic, underline, inverse and strikethrough do not work on windows so I think something in the readme should note that.

Duplicate issue #155: Yellow color does not work in Windows PowerShell
Created: 2017-06-03T13:50:47Z
PowerShell has recently become the default shell in Windows, which means that most Windows users will start using it in the near future. However, yellow text does not work in Windows PowerShell, it shows up as being white.

Closing comment (2017-06-03T14:35:37Z): Duplicate of #2
Repository: chalk/chalk

Issue #528: Error [ERR_REQUIRE_ESM]: require() of ES Module /home/circleci/project/node_modules/chalk/source/index.js from /home/circleci/project/index.js not supported.
Created: 2021-12-05T04:30:45Z
https://app.circleci.com/pipelines/github/RadishTeam/RadishBot/33/workflows/905f695c-fd3a-4bba-9e29-bdd1111ed8a7/jobs/66?invite=true#step-105-20

Duplicate issue #529: chalk 5.0.0
Created: 2021-12-05T10:06:38Z
WHY? WHAT

Closing comment (2021-12-05T10:36:28Z): Duplicate of #528
Repository: chalk/chalk

Issue #176: Got a error when use `chalk.bgHex()` with arg `--no-color`
Created: 2017-07-17T05:19:24Z
const chalk = require('chalk');
try {
	chalk.bgHex('#cccccc')('message');
} catch (ex) {
	console.error(ex);
}
E:\work\gulp-reporter (master) (gulp-reporter@2.1.0)
$ node -v
v8.1.2

E:\work\gulp-reporter (master) (gulp-reporter@2.1.0)
$ node test.js --no-color
TypeError: Cannot read property 'hex' of undefined
    at Function.<anonymous> (E:\work\gulp-reporter\node_modules\chalk\index.js:98:57)
    at errors.map (E:\work\gulp-reporter\lib\formater.js:240:19)
    at Array.map (native)
    at formater (E:\work\gulp-reporter\lib\formater.js:235:18)
    at reporter (E:\work\gulp-reporter\lib\reporter.js:20:10)
    at getErrors.then.errors (E:\work\gulp-reporter\lib\gulp-plugin.js:19:19)

Duplicate issue #178: [BUG] chalk.hex crashes when color is not supported
Created: 2017-07-20T17:51:33Z
On a terminal where color is not supported, when I run the following code:
console.log('supportsColor:', chalk.supportsColor);
chalk.hex('ff5f6d')('A');
I get the following output:
supportsColor: false

X:\Boris\gradient-string\node_modules\chalk\index.js:75
    const open = ansiStyles.color[levelMapping[level]][model].apply(null, arguments);
                                                      ^

TypeError: Cannot read property 'hex' of undefined
    at Function.<anonymous> (X:\Boris\gradient-string\node_modules\chalk\index.js:75:55)


I guess the expected result would be a white string (without any color), am I right?
N.B: as you can see, I run this on a Windows machine 😕

Closing comment (2017-07-21T18:41:24Z): Duplicate of #176.
Repository: charlesbel/Microsoft-Rewards-Farmer

Issue #298: [BUG] Unacceptably high CPU Usage - Failure to close chrome upon script completion
Created: 2023-08-19T03:43:07Z
Before submitting a bug report...

 This bug wasn't already reported.
(I have checked every bug report on GitHub)

Title

 The title is no longer "[BUG] Title" and I edited it with the right error name.

Describe the bug
While running this and doing the mobile searches, the amount of resources used goes up astronomically high. Additionally, there are at least two zombie Chrome processes left open after the script terminates.
Copy and paste your error
No log error.
Screenshots


Value of dashboard variable
N/A

Duplicate issue #339: Windows - Script completes, but leaves browser and causes 100% CPU
Created: 2023-09-07T17:27:50Z
The script completes successfully for me, and goes through 3 different accounts.
At the end of the execution in Windows, all of the Chrome browsers are still there as processes, and causes 100% CPU.
Manually killing the powershell window clears them too.

Closing comment (2023-09-09T18:15:59Z): Duplicate of #298
Run this to clear the processes taskkill /pid chrome.exe /t /f
Repository: charlesbel/Microsoft-Rewards-Farmer

Issue #283: [BUG] Chrome driver too new?
Created: 2023-08-16T23:39:18Z
Before submitting a bug report...

 This bug wasn't already reported.
(I have checked every bug report on GitHub)

Title

 The title is no longer "[BUG] Title" and I edited it with the right error name.

Describe the bug
selenium.common.exceptions.WebDriverException: Message: unknown error: cannot connect to chrome at 127.0.0.1:50134
from session not created: This version of ChromeDriver only supports Chrome version 114
Current browser version is 116.0.5845.96
I've deleted everything and started over, getting the same error. Ran pip install -r requirements.txt --upgrade and the selenum upgrade command too.
Copy and paste your error
selenium.common.exceptions.WebDriverException: Message: unknown error: cannot connect to chrome at 127.0.0.1:50134
from session not created: This version of ChromeDriver only supports Chrome version 114
Current browser version is 116.0.5845.96
Screenshots
n/a
Value of dashboard variable
n/a

Duplicate issue #300: Wrong Chromedriver Version
Created: 2023-08-19T17:12:08Z
Tried "pip install selenium --upgrade" Doesnt seem to resolve.
file "C:\Users\AppData\Local\Programs\Python\Python311\Lib\site-packages\selenium\webdriver\remote\webdriver.py", line 345, in execute
self.error_handler.check_response(response)
File "C:\Users\AppData\Local\Programs\Python\Python311\Lib\site-packages\selenium\webdriver\remote\errorhandler.py", line 229, in check_response
raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.WebDriverException: Message: unknown error: cannot connect to chrome at 127.0.0.1:2517
from session not created: This version of ChromeDriver only supports Chrome version 114
Current browser version is 116.0.5845.97
Stacktrace:
Backtrace:
GetHandleVerifier [0x0064A813+48355]
(No symbol) [0x005DC4B1]
(No symbol) [0x004E5358]
(No symbol) [0x005061AC]
(No symbol) [0x005006B4]
(No symbol) [0x00500491]
(No symbol) [0x00530C55]
(No symbol) [0x0053093C]
(No symbol) [0x0052A536]
(No symbol) [0x005082DC]
(No symbol) [0x005093DD]
GetHandleVerifier [0x008AAABD+2539405]
GetHandleVerifier [0x008EA78F+2800735]
GetHandleVerifier [0x008E456C+2775612]
GetHandleVerifier [0x006D51E0+616112]
(No symbol) [0x005E5F8C]
(No symbol) [0x005E2328]
(No symbol) [0x005E240B]
(No symbol) [0x005D4FF7]
BaseThreadInitThunk [0x76567D59+25]
RtlInitializeExceptionChain [0x7751B79B+107]
RtlClearBits [0x7751B71F+191]

Closing comment (2023-08-19T17:13:27Z): Duplicate of #283
Repository: charlesbel/Microsoft-Rewards-Farmer

Issue #201: Create a mirror on gitlab in case of repo takedown (not a bug)
Created: 2023-07-23T22:06:03Z

Duplicate issue #220: Move To Gitlab
Created: 2023-07-28T08:50:49Z
Before submitting a bug report...

 This bug wasn't already reported.
(I have checked every bug report on GitHub)

Describe the bug
I would recommend you to move to gitlab immediately so that we do not repeat farshadz case/ or we can make a tg group to be in touch for continuous development
just my 2 cents
Copy and paste your error
xx----xx
Screenshot of the bug
xx----xx
Value of dashboard variable
xx----xx

Closing comment (2023-07-28T19:19:47Z): Duplicate of #201