primordic/IssueDupesLite huggingface dataset:
Repository: kanasimi/work_crawler

Issue #567: AlphaPolis_official_manga 皆顯示章節資料無效：undefined
Created: 2022-07-02T06:42:06Z
Version: 
Interface: 
Arguments:

Duplicate issue #574: アルファポリスの公式Web漫画下載失敗
Created: 2022-08-11T00:41:22Z

Closing comment (2022-08-11T01:27:34Z): Duplicate of #567
Repository: kanasimi/work_crawler

Issue #19: 733mh 無法下載
Created: 2018-07-03T04:38:56Z
下載下來的圖是"訪問受限提示"
"網站未授權"
"正確的網址只有 733.so 域名"

Duplicate issue #44: 733mh 無法下載
Created: 2018-08-10T11:51:12Z
下載733出現以下圖片

Closing comment (2018-08-10T12:07:12Z): Duplicate of #19
Repository: kanasimi/work_crawler

Issue #480: docker 容器启动失败
Created: 2021-02-05T09:43:38Z
通过 docker run -d --name work_crawler -p 8800:80 kanasimi/work_crawler:latest 启动容器失败, 截图是启动日志

Duplicate issue #545: docker版本安装成功后，依赖库报错无法正常运行（libxshmfence.so.1）
Created: 2022-01-29T19:44:14Z
日志信息如下：
Loading work_crawler GUI...
/app/work_crawler-master/node_modules/electron/dist/electron: error while loading shared libraries: libxshmfence.so.1: cannot open shared object file: No such file or directory
./start_gui_electron.sh: 6: ./start_gui_electron.sh: /root/node_modules/.bin/electron: not found
——---——---——---——---——---——---——
本人才疏学浅，搭设只懂皮毛，尝试按照错误信息下载并安装Debian发行版下 libxshmfence-dev:amd64 依赖库
显示安装失败，万般无奈前来求助，错误信息如下
error processing package libxshmfence-dev:amd64 (--install):
dependency problems - leaving unconfigured
Errors were encountered while processing:
libxshmfence-dev:amd64
——---——---——---——---——---——---——
能否详细告知该如何设置

Closing comment (2022-06-23T22:33:35Z): Duplicate of #480
Repository: kanasimi/work_crawler

Issue #164: 請求增加  哔哩哔哩漫画  https://manga.bilibili.com/m
Created: 2019-01-18T18:23:43Z
未找到
https://manga.bilibili.com/m/detail/mc25915
https://manga.bilibili.com/m/detail/mc25813
https://manga.bilibili.com/m/detail/mc25854
https://manga.bilibili.com/m/detail/mc25870
https://manga.bilibili.com/m/detail/mc25757
https://manga.bilibili.com/m/detail/mc25750
https://manga.bilibili.com/m/detail/mc25852
https://manga.bilibili.com/m/detail/mc25758
https://manga.bilibili.com/m/detail/mc25723
https://manga.bilibili.com/m/detail/mc25845
https://manga.bilibili.com/detail/mc25111
感謝閱讀
請您慢慢來

Duplicate issue #229: 請求增加 哔哩哔哩漫画 https://manga.bilibili.com/m
Created: 2019-02-27T12:14:45Z
发现之前有一个人提出类似问题，但是发现使用谷歌浏览器开发者工具还是可以在Network里发现jpg图片的，是不是考虑增加一个抓取哔哩哔哩漫画图片的功能，本人不会编程，不懂此类技术，但是既然浏览器中可以找到图片链接，应该是能实行抓取的，还请您再研究一下解决方案？

Closing comment (2019-02-27T13:14:03Z): Duplicate of #164
這邊看不到日本漫畫
大陸的又多收費
無法搜尋漫畫
在其他網站可以看到更多...
似乎沒有優勢
Repository: kanasimi/work_crawler

Issue #229: 請求增加 哔哩哔哩漫画 https://manga.bilibili.com/m
Created: 2019-02-27T12:14:45Z
发现之前有一个人提出类似问题，但是发现使用谷歌浏览器开发者工具还是可以在Network里发现jpg图片的，是不是考虑增加一个抓取哔哩哔哩漫画图片的功能，本人不会编程，不懂此类技术，但是既然浏览器中可以找到图片链接，应该是能实行抓取的，还请您再研究一下解决方案？

Duplicate issue #233: bilibili漫画app版【可正常搜索】 https://manga.bilibili.com/twirp/comic.v1.Comic/Search
Created: 2019-03-02T17:02:36Z
哔哩哔哩漫画 搜索功能可以借助app版，漫画详情与章节内容可选择网页版。
搜索方法如下
api接口 https://manga.bilibili.com/twirp/comic.v1.Comic/Search
post form or json，{"page_num":number,"page_size": number,"key_word":keyword}
一个例子如下
POST https://manga.bilibili.com/twirp/comic.v1.Comic/Search HTTP/1.1
Host: manga.bilibili.com
Content-Type: application/json
Content-Length: 55
{"page_num":1,"page_size":10,"key_word":"蜉蝣一梦"}

例子中详情页与目录页对应于 蜉蝣一梦 https://manga.bilibili.com/m/detail/mc25915 <--JSON.data.id
如有计划，或许可做尝试。
感谢阅读

Closing comment (2019-03-03T01:09:11Z): Duplicate of #229
Repository: kanasimi/work_crawler

Issue #575: 【BUG】windows gui 未正常显示
Created: 2022-08-13T06:15:05Z
2.14.0

Duplicate issue #591: 2.14版本无法使用，是因为还在预发布状态么？即便使用2.13进行更新，也还是无法解决
Created: 2022-11-29T14:33:54Z
这个问题有够无聊的，作为白嫖人士，怪不好意思的

Closing comment (2022-11-30T19:14:11Z): Duplicate of #575
Repository: kanasimi/work_crawler

Issue #528: 请求增加Mangabz
Created: 2021-08-22T23:19:29Z
Version: 
Interface: 
Arguments: 


https://mangabz.com/

Duplicate issue #544: 建议新增mangabz.com
Created: 2022-01-27T06:28:56Z
现有网站没有《总之就是非常可爱》的最新资源，就算有也不能用较快速度访问mangabz.com就很快
mangabz.com有一部分漫画是搬运copymanga.org更新速度应该能保证
mangabz.com是免费的
我在用最新的work_crawler

Closing comment (2022-06-25T00:13:21Z): Duplicate of #528
Repository: kanasimi/work_crawler

Issue #560: 建议增加支持漫画源kakaowebtoon台湾
Created: 2022-06-11T13:10:01Z
域名： https://tw.kakaowebtoon.com/
需要台灣ip 有付費內容
不知道大佬有空做不？

Duplicate issue #517: 請求增加kakaowebtoon
Created: 2021-06-18T14:02:54Z
Version: 
Interface: 
Arguments:

Closing comment (2022-06-24T05:10:26Z): Duplicate of #560
Repository: karlstav/cava

Issue #194: Cava configuration issues with konsole
Created: 2018-01-15T00:00:20Z
I am running Fedora 27 with kde 5 and have finally been able to put cava in my background. I have only been able to make transparency and desktop configurations work with konsole, however now cava only creates brick like bars and gradiant as shown:

It works normally in gnome-terminal on the right, even though the cava configurations are the same.
This happened before when the user define gradients were not real colour codes, but when gradient is disabled the bars are still brick shaped.
Any ideas? Thanks.

Duplicate issue #233: Gradient color bug in Konsole
Created: 2018-08-19T15:37:09Z
I don't know why, but the color with gradient are all bugged in Konsole (work fine in "normal" mode), while in gnone-terminal everything is ok
https://i.imgur.com/yOWm66Z.png
Left = Konsole
Right = Gnome Terminal

Closing comment (2018-08-20T09:51:15Z): this is a duplicate of #194 that i closed for some reason. I will reopen that issue and close this.
Repository: karlstav/cava

Issue #121: cava not working(solved)
Created: 2016-12-10T03:46:16Z
I am using Arch.
I have tried installing cava from distinct ways.
my mpd is working just fine.
I can run it, but it is not working. there is just a blank terminal screen, nothing jumps.
I have edited the config file many ways, but.
how can i fix it?

Duplicate issue #109: cannot see bars even though they are there
Created: 2016-08-28T16:52:14Z
So I know the bars are there because when I highlight them I can see them moving but I cannot see them without highlighting them, is there anything I can do?

Closing comment (2019-08-02T20:11:41Z): maybe it is far fetched, but can this be related to #121 ? That was solved by setting the locale:
localectl set-locale LANG=en_US.UTF-8


I'm having this issue as well, but applying the system locale (localectl set-locale LANG=en_US.UTF-8) doesn't do anything. The bars are invisible, unless highlighted. I have tried changing terminals from urxvt to xfce4-terminal, but still get the same issue.
Repository: karlstav/cava

Issue #196: Slight tearing
Created: 2018-02-26T15:49:46Z
pkgname=cava
pkgver=0.6.0
pkgrel=1


I am experiencing some random tearing with Cava (it happens once every 10 seconds or so). Not experiencing this with any other application.
Someone have simular issues out there or perhaps know where to look for clues to identify what could be wrong?

Duplicate issue #261: Cava tearing on ST with multiple fonts
Created: 2019-02-06T21:03:11Z
I just got around to installing Cava on my new system, and am encountering a weird bug with tearing I've never experienced.
I'm currently using Suckless Terminal with Fira Code font, size 10. Config is set to default.
Whenever I launch cava, I get frequent (almost on a one second interval) tears in the bars. I've also tried using alacritty just now, and even without transparency set with compton, the tears still happen. I'm assuming this has something to do with ncurses, but after searching around the issues page I haven't found anything that applies to me.

Closing comment (2019-02-24T21:32:45Z): Then this is probably the same as #196.
Repository: karlstav/cava

Issue #555: Segmentation fault
Created: 2024-03-27T15:11:29Z
READ THIS BEFORE CREATING NEW ISSUE
Are you using cava from a package repository, like AUR?
I have tried cava from this github repo (I did the ./autogen.sh and ./configure) and from AUR but both give the same error
If so, clone the master branch from here, build and run. Is your issue already resolved?
Don't know how to clone or compile source code? File report to package maintainer instead!
Describe the bug
I get a segmentation fault error with the [E] pw.loop. The screen is below.
To Reproduce
Steps to reproduce the behavior:

Install & run cava, literally.

Expected behavior
Cava to run
Screenshots

Desktop (please complete the following information):

Arch Linux kernel 6.8.1-arch1-1

Terminal emulator
kitty
0.33.0
Additional context
This is really just a fresh install of arch.

Duplicate issue #553: Two squares (not umlaut) on top of each bar if starting over ssh
Created: 2024-03-09T19:27:17Z
Hi all,
I run cava on a raspberry pi 1B with a small hdmi screen. Works well using noncurses. However, to avoid keeping a keyboard attached, I ssh from my PC using PuTTY.  To start cava, I simply type on the computer connected via ssh: cava > /dev/tty1
When I invoke cava in this fashion, each of the bars has an umlaut as in: Ä, but without the A. Connecting a keyboard to the pi and invoking normally cava, the umlaut doesn't appear.. Not a big deal really, but they are a bit distracting. They remind me of "peak" markers except they drop instantly with the bar. Sorry for the long post. Any thoughts? Thank you.

Closing comment (2024-03-29T15:06:35Z): Sorry for the delay. When I run the command suggested in the README via ssh to the RPi, this happens:
root@raspi1:~# cava  <> /dev/console >&0 2>&1
Segmentation fault
and on the RPi console screen appears this:

This is somewhat similar to error reported in #555.
When I run cava > /dev/tty1 via ssh, closer inspection reveals that the "umlaut" appears to be two small squares side by side. Interestingly, one of the bars doesn't have the squares. They appear to be there on all bars when watching dynamically. Must have caught one as it was changing direction.

Cava works fine with alsa noncurses when run from a usb keyboard.
By default, Raspberry Pi OS has the UK locale. I changed it to US when I installed. Tried putting it back to UK, but it made no difference. Honestly this is no problem for me. I just keep a small keyboard available for the unit. Feel free to close, I just didn't want to leave the thread hanging.
Repository: karlstav/cava

Issue #83: Build fail on Gentoo Linux
Created: 2015-12-03T23:20:14Z
Building fails on Gentoo Linux. ./autogen.sh and ./configure ran fine though.
https://bpaste.net/show/08086febace8

Duplicate issue #186: make error
Created: 2017-11-06T18:16:46Z
Hi...
I use Gentoo and I have installed FFTW package.
I'm not a big bos in compilation and in C language.
I try to compil your CAVA (I like this... :), but I have this error :
skippy@Gentoo ~/compilations/cava $ make
make[1] : on entre dans le répertoire « /home/skippy/compilations/cava »
gcc -DPACKAGE_NAME="cava" -DPACKAGE_TARNAME="cava" -DPACKAGE_VERSION="0.6.0-12-g51e48d8" -DPACKAGE_STRING="cava\ 0.6.0-12-g51e48d8" -DPACKAGE_BUGREPORT="karl@stavestrand.no" -DPACKAGE_URL="" -DPACKAGE="cava" -DVERSION="0.6.0-12-g51e48d8" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=".libs/" -DHAVE_PTHREAD_H=1 -DHAVE_CURSES_H=1 -DHAVE_INIPARSER_H=1 -I.  -DPACKAGE="cava" -DVERSION="0.6.0-12-g51e48d8" -D_POSIX_SOURCE -D _POSIX_C_SOURCE=200809L  -DHAVE_ALLOCA_H -DALSA -DPULSE -D_GNU_SOURCE -I/usr/include/ncursesw -DNCURSES -std=c99 -Wall -Wextra -Wno-unused-result -Wno-maybe-uninitialized  -g -O2 -MT cava-cava.o -MD -MP -MF .deps/cava-cava.Tpo -c -o cava-cava.o test -f 'cava.c' || echo './'cava.c
In file included from cava.c:69:0:
config.c: Dans la fonction ‘load_config’:
config.c:389:2: erreur : too many arguments to function ‘iniparser_getseckeys’
iniparser_getseckeys(ini, "eq", keys);
^
In file included from cava.c:66:0:
/usr/include/iniparser.h:142:9: note : declared here
char ** iniparser_getseckeys(dictionary * d, char * s);
^
make[1]: *** [Makefile:527: cava-cava.o] Error 1
make[1] : on quitte le répertoire « /home/skippy/compilations/cava »
make: *** [Makefile:577: all-recursive] Error 1
It's my mistake or what...
Thanks, and sorry for my english, I'm so french... :p

Closing comment (2017-11-07T12:04:46Z): hi @Skippythekangoo this is actually the same as #83
configure with this option:
./configure --legacy-iniparser

then run make again
Repository: karlstav/cava

Issue #227: Apt Install Broken on Ubuntu 18.04
Created: 2018-07-04T16:24:19Z
$ sudo apt-get update
Hit:1 https://download.docker.com/linux/ubuntu bionic InRelease
Hit:2 http://security.ubuntu.com/ubuntu bionic-security InRelease
Hit:3 http://us.archive.ubuntu.com/ubuntu bionic InRelease
Ign:4 http://ppa.launchpad.net/tehtotalpwnage/ppa/ubuntu bionic InRelease
Hit:5 http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:6 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease
Hit:7 https://packages.microsoft.com/repos/vscode stable InRelease
Err:8 http://ppa.launchpad.net/tehtotalpwnage/ppa/ubuntu bionic Release
404  Not Found [IP: 91.189.95.83 80]
Reading package lists... Done
E: The repository 'http://ppa.launchpad.net/tehtotalpwnage/ppa/ubuntu bionic Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Looks like there's no release file for bionic
I know you're busy so just when you get a second :)

Duplicate issue #281: No work for ubuntu 18.04
Created: 2019-09-21T16:52:12Z
You instruction:
sudo add-apt-repository ppa:tehtotalpwnage/ppa
sudo apt-get update
sudo apt-get install cava

But when update:
Err:5 http://ppa.launchpad.net/tehtotalpwnage/ppa/ubuntu bionic Release
  404  Not Found [IP: 91.189.95.83 80]
Obj:6 http://archive.ubuntu.com/ubuntu bionic-security InRelease
Leyendo lista de paquetes... Hecho
E: El repositorio «http://ppa.launchpad.net/tehtotalpwnage/ppa/ubuntu bionic Release» no tiene un fichero de Publicación.

The respository: https://launchpad.net/~tehtotalpwnage/+archive/ubuntu/ppa/ no support bionic release (18.04).
Solve for me:
$ wget 'https://launchpad.net/~tehtotalpwnage/+archive/ubuntu/ppa/+files/cava_0.6.0-0ubuntu3_amd64.deb'
$ sudo dpkg -i cava_0.6.0-0ubuntu3_amd64.deb
$ sudo apt install -f
$ cava

And works fine.

Closing comment (2019-09-28T20:11:41Z): duplicate #227
Repository: karlstav/cava

Issue #594: autoconf-archive broken (_AX_CHECK_GL_MANUAL_LIBS_GENERIC: argument must not be empty)
Created: 2024-10-29T20:52:25Z
Cava is not building from source or from AUR on arch The arror is in bothe one: (Arch, Terminal: tillix DE:gnome)
/usr/share/automake-1.17/am/depend2.am: error: am__fastdepCC does not appear in AM_CONDITIONAL
/usr/share/automake-1.17/am/depend2.am:   The usual way to define 'am__fastdepCC' is to add 'AC_PROG_CC'
/usr/share/automake-1.17/am/depend2.am:   to 'configure.ac' and run 'aclocal' and 'autoconf' again
/usr/share/automake-1.17/am/depend2.am: error: AMDEP does not appear in AM_CONDITIONAL
/usr/share/automake-1.17/am/depend2.am:   The usual way to define 'AMDEP' is to add one of the compiler tests
/usr/share/automake-1.17/am/depend2.am:     AC_PROG_CC, AC_PROG_CXX, AC_PROG_OBJC, AC_PROG_OBJCXX,
/usr/share/automake-1.17/am/depend2.am:     AM_PROG_AS, AM_PROG_GCJ, AM_PROG_UPC
/usr/share/automake-1.17/am/depend2.am:   to 'configure.ac' and run 'aclocal' and 'autoconf' again

Duplicate issue #630: Fails to build with OpenGL support.
Created: 2025-03-25T09:43:57Z
Are you using cava from a package repository, like AUR?
Yes and no ( tried both )
If so, clone the master branch from here, build and run. Is your issue already resolved?
No.
ALWAYS TRY TO BUILD AND RUN FROM THE SOURCE BEFORE POSTING ISSUES
Have tried.
Describe the bug
autom4te exits with status: 1
To Reproduce
Tried this on two machines, same behaviour both times.
Steps to reproduce the behavior:

clone repo && cd into it
yay -S sdl2 pipewire pkgconf fftw iniparser base-devel autoconf autoconf-archive
./autogen.sh
Outputs:

libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
libtoolize: and rerunning libtoolize and aclocal.
configure.ac:306: error: _AX_CHECK_GL_MANUAL_LIBS_GENERIC: argument must not be empty
lib/m4sugar/m4sh.m4:690: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:697: AS_IF is expanded from...
/usr/share/aclocal/ax_check_gl.m4:187: _AX_CHECK_GL_MANUAL_LIBS_GENERIC is expanded from...
lib/m4sugar/m4sh.m4:595: AS_CASE is expanded from...
/usr/share/aclocal/ax_check_gl.m4:253: AX_CHECK_GL is expanded from...
lib/m4sugar/m4sh.m4:697: AS_IF is expanded from...
lib/m4sugar/m4sh.m4:697: AS_IF is expanded from...
configure.ac:306: the top level
autom4te: error: /usr/bin/m4 failed with exit status: 1
aclocal: error: autom4te failed with exit status: 1

Expected behavior
Expected: Build with openGL support.
Desktop (please complete the following information):

OS: Arch Linux
Version: 6.13.8-arch1-1

Terminal emulator

Kitty
0.40.1

Closing comment (2025-03-26T17:53:16Z): this is the same as #594, if you do not need openGL support, just remove autoconf-archive. If you do want to use the openGL output you need to use the tar  distribution, it should contain a working configure script, no need to run ./autogen.sh
Repository: kedacore/keda

Issue #470: KEDA might break existing deployment on cluster which already has another External Metrics Adapter installed
Created: 2019-11-18T21:16:24Z
KEDA is using metrics adapter based on custom-metrics-apiserver
library. As part of the deployment, user need to specify cluster wide APIService object named v1beta1.external.metrics.k8s.io, see in the library example and in KEDA deployment .
I wonder what would happen, if user has already deployed another Metrics Adapter (which is using the same APIService based approach) and we try to install Keda. It will probably replace the original APIService definition with KEDA one, so KEDA will work, but the original stuff installed on cluster probably not. We should not break things or should make clear, that this could happen.
We should investigate what are the possibilities and whether there are a better solutions on how to deal with the metrics. Or my assumptions are wrong, so please correct me in this case.

Duplicate issue #225: keda conflict with ambassador
Created: 2019-05-25T19:03:18Z
After installing Keda, Ambassador stop working.
The issue is cauded by v1beta1.custom.metrics.k8s.io
Ambassaor opened issue
apiVersion: apiregistration.k8s.io/v1beta1
kind: APIService
metadata:
  name: v1beta1.custom.metrics.k8s.io
spec:
  service:
    name: {{ template "keda.fullname" . }}
    namespace: {{ .Release.Namespace }}
  group: custom.metrics.k8s.io
  version: v1beta1
  insecureSkipTLSVerify: true
  groupPriorityMinimum: 100
  versionPriority: 100
as workaround to let ambassador works:
k -n keda delete apiservice v1beta1.custom.metrics.k8s.io
Why do we need custom.metrics in keda?

Closing comment (2019-11-21T06:00:17Z): @zroubalik is this related to #470 ?
Repository: kedacore/keda

Issue #5159: Support for Returning Float Values in GetMetrics for External Scalers
Created: 2023-11-03T13:21:10Z
Proposal
We have identified a discrepancy in the behavior of the GetMetrics function for external scalers in KEDA  as per the discussions slack . When an external scaler makes a GetMetrics call, it returns a GetMetricsResponse that does not allow for the return of float values.
To address this, we need to enable the return of float values, as these are crucial for certain use cases, without requiring users to manually adjust the metric values. We want to explore options for managing this behavior without breaking existing functionality.
Use-Case
No response
Is this a feature you are interested in implementing yourself?
Maybe
Anything else?
Might need help to figure out how we can implement it with backward compatibility.

Duplicate issue #6483: External scaler should be able to report also metrics that are not integers
Created: 2025-01-13T17:10:59Z
Report
No response
Expected Behavior
0.5 for instance should be also accepted
Actual Behavior
The proto definition for MetricValue allows only int64 metricValue = 2; atm
Steps to Reproduce the Problem

create an external scaler
try to report a float value to KEDA
...
no profit

Logs from KEDA operator
example

KEDA Version
2.16.1
Kubernetes Version
1.30
Platform
Any
Scaler Details
external
Anything else?
No response

Closing comment (2025-01-13T17:12:13Z): meh, dupe of #5159
Repository: kedacore/keda

Issue #208: Integrate KEDA scale logic with coming HPA scale to zero features
Created: 2019-05-17T16:01:26Z
kubernetes/kubernetes#74526

Duplicate issue #4697: create HPA object which can scale to 0
Created: 2023-06-16T13:54:30Z
Proposal
Although KEDA support to scale objects' replicas to 0, it is slow to scale down from 1 to 0.
Actually, Kubernetes support the feature-gate HPAScaleToZero, which can be used to create a HPA object with 0 min value. That would be more faster.
Use-Case
No response
Is this a feature you are interested in implementing yourself?
Yes
Anything else?
No response

Closing comment (2023-06-17T14:07:31Z): This is a duplicate of #208
Repository: kedacore/keda

Issue #1789: Azure Blob Storage Scaler doesn't list blobs recursively
Created: 2021-05-06T14:52:30Z
Proposal
I'm not sure if this is a bug in the current implementation but given the default values, if I upload a blob to foo/bar/blob.txt the scaler will not "see" the file in order to count it. I think (next to 0 Go knowledge) this is because 
  
    
      keda/pkg/scalers/azure/azure_blob.go
    
    
         Line 26
      in
      c2ad43e
    
  
  
    

        
          
           props, err := containerURL.ListBlobsHierarchySegment(ctx, azblob.Marker{}, blobDelimiter, listBlobsSegmentOptions) 
        
    
  

 calls ListBlobsHierarchySegment whereas  ListBlobsFlatSegment tells the Azure API to "flatten" the list of files on the server side prior to returning the list.
If this is a bug then it would be great to get this fixed or docs updated to make this clear. However, if this is intended behaviour it would be great to have this as a new feature whereby a developer can pass a switch to the trigger metadata:
  triggers:
    - type: azure-blob
      metadata:
        blobContainerName: mycontainer
        blobCount: "5"
        blobPrefix: ""
        blobDelimiter: "/"
        ignoreBlobHierarchy: true

Use-Case
when I upload a blob which includes a directory structure, it is still included in the blobCount to trigger the Scale Target.
Given this directory tree:
.
├── baz.txt
├── bin.txt
└── foo
    ├── bar
    │   └── world.txt
    └── hello.txt

The call to GetAzureBlobListLength would return 2
With the proposed feature in place, GetAzureBlobListLength would return 4.
Anything else?
No response

Duplicate issue #1210: watch all sub folders in azure blob storage scaler?
Created: 2020-10-02T11:22:02Z
is it possible to watch all subfolders in azure blob storage scaler
like can i provide blobPrefix as "RawData/Processing/{containername}" where {containername} is dynamic and need to listen files in and scale accrodingly

Closing comment (2021-09-28T06:32:00Z): Duplicate of #1789
Repository: kedacore/keda

Issue #1943: kubectl get scaledobject only displays one trigger
Created: 2021-07-08T11:04:13Z
Report
For scaled objects with multiple triggers, kubectl get scaledobject only shows the first trigger:
~ $ k get scaledobject myapp
NAME           SCALETARGETKIND      SCALETARGETNAME   MIN   MAX   TRIGGERS     AUTHENTICATION   READY   ACTIVE   AGE
myapp          apps/v1.Deployment   myapp             1     2     prometheus                    True    True     7d

~ $ k get scaledobject myapp -o jsonpath='{.spec.triggers[*].type}'
prometheus cpu
Expected Behavior
All trigger types should be displayed
Actual Behavior
Only the first trigger is displayed
Steps to Reproduce the Problem

create a scaled object with two triggers
run kubectl get scaledobject

Logs from KEDA operator
N/A
KEDA Version
2.2.0
Kubernetes Version
1.19
Platform
Microsoft Azure
Scaler Details
any (e.g. prometheus, cpu, memory)
Anything else?
No response

Duplicate issue #2047: Provide capability to show multiple triggers in CLI
Created: 2021-08-20T08:41:43Z
Proposal
Provide the capability to show multiple triggers in CLI.
If you create a ScaledObject with multiple triggers today, and run k get so/<name> you will have the following output:
NAME     SCALETARGETKIND      SCALETARGETNAME   MIN     MAX     TRIGGERS   AUTHENTICATION   READY     ACTIVE    AGE
<name>   apps/v1.Deployment   <target>          1       3       cpu                         True      True      247d

However, it would be nice to see all applicable triggers, maybe something like this:
NAME     SCALETARGETKIND      SCALETARGETNAME   MIN     MAX     TRIGGERS      AUTHENTICATION   READY     ACTIVE    AGE
<name>   apps/v1.Deployment   <target>          1       3       cpu, memory                         True      True      247d

Use-Case
Improve operational experience and avoid confusion.
Anything else?
No response

Closing comment (2021-08-23T11:12:01Z): Duplicate of: #1943
Repository: kedacore/keda

Issue #3065: Prometheus scaler - add option to consider null values as errors
Created: 2022-05-24T13:52:37Z
Proposal
Add option to consider null values as errors
Use-Case
We heavily rely on KEDA on our prod, had an incident and I’m looking for ways to circumvent such cases in the future.
We scale some of our deployments based on the number of requests they’re getting per second which works very well most of the time.
During this incident, we had an issue with our prometheus and all of our queries returned null values which it looks like the prometheus scaler interpreted as 0.
If that scaledobject was failing, we would have gotten alerts about it and figured out the issue, but because it didn’t happen, all of our deployments that relayed on the prometheus scaler scaled to the minimum number of replicas during peak hours and it wasn’t pretty.
Anything else?
No response

Duplicate issue #3064: Should we return error when  target lost for prometheus scaler
Created: 2022-05-24T08:56:28Z
Report
when Prometheus target is lost, the prometheus query will return an empty result here:
https://github.com/kedacore/keda/blob/main/pkg/scalers/prometheus_scaler.go#L55
The hpa controller will get an 0 value and using the minReplicas. Maybe we should return an error when len(reslut) = 0? To let the hpa forget about this workload for a while until the prometheus is back to normal?
There are related issue regarding to this: #657. But I think we shouldn't patch the replicas when the dependency is not available. Maybe somebody can share more thoughts about that?
Expected Behavior
keda-metrics return 0 when prometheus is unavailable, hpa controller is patching the minReplicas to workload
Actual Behavior
keda-metrics should return error when prometheus is unavailable, hpa controller should maintain the same replicas
Steps to Reproduce the Problem

Lost prometheus target

Logs from KEDA operator
example

KEDA Version
2.7.1
Kubernetes Version
1.20
Platform
Any
Scaler Details
No response
Anything else?
No response

Closing comment (2022-05-26T07:45:13Z): @bamboo12366 yeah that would be great, let me close this issue and continue on the other one.
Duplicate of #3065
Repository: kedacore/keda

Issue #470: KEDA might break existing deployment on cluster which already has another External Metrics Adapter installed
Created: 2019-11-18T21:16:24Z
KEDA is using metrics adapter based on custom-metrics-apiserver
library. As part of the deployment, user need to specify cluster wide APIService object named v1beta1.external.metrics.k8s.io, see in the library example and in KEDA deployment .
I wonder what would happen, if user has already deployed another Metrics Adapter (which is using the same APIService based approach) and we try to install Keda. It will probably replace the original APIService definition with KEDA one, so KEDA will work, but the original stuff installed on cluster probably not. We should not break things or should make clear, that this could happen.
We should investigate what are the possibilities and whether there are a better solutions on how to deal with the metrics. Or my assumptions are wrong, so please correct me in this case.

Duplicate issue #2093: Install fails because v1beta1.external.metrics.k8s.io it's already installed
Created: 2021-09-07T18:16:24Z
Report
Running helm install keda kedacore/keda --namespace keda fails with error
Error: rendered manifests contain a resource that already exists. Unable to continue with install: existing resource conflict: kind: APIService, namespace: , name: v1beta1.external.metrics.k8s.io
Expected Behavior
helm install keda kedacore/keda --namespace keda installs keda on cluster
Actual Behavior
There is an error because v1beta1.external.metrics.k8s.io already exists in our cluster since it's being installed by the datadog cluster agent
Steps to Reproduce the Problem

Install datadog cluster agent: https://docs.datadoghq.com/agent/cluster_agent/setup/?tab=helm
Try to install keda helm install keda kedacore/keda --namespace keda
Get an error

Logs from KEDA operator
example

KEDA Version
2.4.0
Kubernetes Version
1.19
Platform
Amazon Web Services
Scaler Details
Postgres
Anything else?
No response

Closing comment (2021-09-10T07:26:58Z): Duplicate of #470
Repository: kedacore/keda

Issue #5274: Kafka scaler: excludePersistentLag not working for partitions with invalid offset (that is -1)
Created: 2023-12-11T03:40:00Z
Report
When I set excludePersistentLag flag to true, it does not excludes persistent lags for the partition with invalid offset (that is -1).
Expected Behavior
If the lags for these partitions with invalid offset is persistent, it should be ignored in the custom metrics.
Actual Behavior
In my test set up, this resulted in no of kafka consumer pods to set to max.
Steps to Reproduce the Problem

In the setup, you should have some partitions that has not been consumed till now.  (Invalid offset)
There should be no new message coming to the partition.
Old messages are not in kafka buffer as they are already expired.

Use kafka scalar to scale the consumer deployment.
I know this is might not be a real production set up. I had this set up in my sandbox landscape for . And it took me hard time to find out what was the problem.
Logs from KEDA operator
example

KEDA Version
2.12.1
Kubernetes Version
None
Platform
Other
Scaler Details
Kafka
Anything else?
No response

Duplicate issue #5906: Kafka scaler: excludePersistentLag not working for partitions with invalid offset (that is -1)
Created: 2024-06-24T08:18:56Z
Report
When I set excludePersistentLag flag to true, it does not excludes persistent lags for the partition with invalid offset (that is -1).
Expected Behavior
If the lags for these partitions with invalid offset is persistent, it should be ignored in the custom metrics.
Actual Behavior
In my set up, this resulted in no of kafka consumer pods to set to max.
Steps to Reproduce the Problem
In the setup, you should have some partitions that has not been consumed till now. (Invalid offset)
Old messages are not in kafka buffer as they are already expired.
Use kafka scalar to scale the consumer deployment.
Logs from KEDA operator
example

KEDA Version
2.14.0
Kubernetes Version
None
Platform
Amazon Web Services
Scaler Details
Kafka
Anything else?
Hi
Refer to #5274
The issue got reproduced in my system again. I did some analysis by adding some debug logging in the kafka scaler and found that we have a topic in the consumer group where the lag is like below. The below is output from kafka-consumer-groups.sh...



GROUP
TOPIC
PARTITION
CURRENT-OFFSET
LOG-END-OFFSET
LAG
CONSUMER-ID
HOST
CLIENT-ID




group1
topic1
0
80
80
0
rdkafka-xxx-xxx-xxx-xxx-xxx
/xx.xx.xx.xx
rdkafka


group1
topic1
1
-
60
-
rdkafka-xxx-xxx-xxx-xxx-xxy
/100.100.17.69
rdkafka


group1
topic1
2
-
96
-
rdkafka-xxx-xxx-xxx-xxx-xxz
/100.100.14.23
rdkafka



Because of this the lag comes as 156.
Here in our case, the topic1 get messages, once in 2-3 months or more. So if we create a new consumer (new group), the lag will be - for some time for all partitions and then suddenly we get one message and lag will be 0 in one partition and will be '-' in other partitions and then the lag for other partitions will start getting counted.
Can you please check?

Closing comment (2024-06-25T20:08:24Z): Duplicate of #5274
Repository: kedacore/keda

Issue #3949: Add circuit breaking (immediately scale to 0) on specific Trigger
Created: 2022-12-03T01:10:47Z
Proposal
Proposing a circuit breaking feature for Keda.  Effectively, if a specific circuitBreak trigger crosses a threshold, it overrides the other triggers and scales the Deployment/ReplicaSet/StatefulSet down to 0.
This would be useful in situations where some microservice upstream or downstream releases bad data into the target process; effectively stopping the data transmission at the top of the funnel.
Possible recovery options could include:

Manual intervention (a redeploy or annotation deletion)
When the circuitBreak threshold is under the target value

Use-Case
For example, we have a Kafka stream worker that ingests messages and pushes them downstream to APIs and Seldon models.  We have implemented a dead letter queue; and if the target rate of messages going to the dlq is above a certain threshold, we would like to stop the stream worker in its' tracks.
Anything else?
There are other ways to do this using Istio and various other tooling; but Keda would offer much more flexibility than what I have seen.

Duplicate issue #5529: Need Circuit breaker functionality for scaler
Created: 2024-02-23T08:57:46Z
Proposal

In case of continuous failures of not getting metadata information from the metric source (eg. Kafka), the scaler should have a circuit breaker to not flood the metric source with multiple requests.
This could be a configuration which specifies following:


The number of failures after which circuit breaker would trigger
Duration for which the circuit would remain broken before retry

Use-Case
We had a use case where Kafka scaler was used to scale the workload based on the topic lag.
However, when the scaler did not have correct permissions for the user it was using, it resulted into many requests being sent to the Kafka. In this case, we had an unfortunate case where AWS MSK went down. One of the reason we got the response is that the user we had used created lot many auth failures for MSK resulting into issue for them.
We
Is this a feature you are interested in implementing yourself?
No
Anything else?
No response

Closing comment (2024-02-23T09:13:13Z): This is a duplicate of #3949, feel free to join the conversation there
Repository: kedro-org/kedro

Issue #2307: Automatically skip running nodes with persisted outputs
Created: 2023-02-10T16:35:14Z
Description
Re-running nodes which have:

Persisted outputs
No upstream dependencies which would cause their output to change

is an unnecessary expense. It might be a good idea to have a flag which would automatically skip running these nodes.
It is currently possible to achieve this by specifying nodes to run from, though this process is manual and potentially error-prone.
Context
User @pedro-sarpen opened #2005 to address this issue, though there may be a better solution to the problem that we should investigate.

Duplicate issue #4400: Can Kedro Pipeline be stateless?
Created: 2025-01-06T04:06:09Z
Description
Can Kedro support a stateless design where nodes are not recomputed even when a new pipeline is initialized, by leveraging the database model and computation state from a previous run?
Context
In a stateless setup, the pipeline is rebuilt from scratch on every run. This leads to all nodes being recomputed, which is inefficient for costly operations (e.g., LLM calls) and large datasets.
Possible Implementation
Could Kedro allow recovering pipeline computation states (e.g., node outputs) stored externally, such as in S3, to avoid recomputation with a new pipeline instance?

Closing comment (2025-01-16T14:13:04Z): Thanks for opening this issue @duy-rhombus ! This is a duplicate of #2307 , let's continue the conversation there
Repository: kedro-org/kedro

Issue #2115: Investigate creation of Versioned PartitionedDataSet 
Created: 2022-12-12T14:30:41Z
Description
Different users have requested a versioned PartitionedDataSet. We need to investigate how such an implementation works and what's required.
Investigation

Collect all issues/PRs/questions about this
Investigate possible next steps and implementation

Issues opened by users requesting this dataset feature

 #2043

Duplicate issue #2043: Versioned PartitionedDataSet
Created: 2022-11-21T09:14:19Z
Description
Is it possible to add a new class that handle versions of a PartitionedDataSet? So, when we replace PartitionedDataSet with VersionedPartitionedDataSet things should work the same way except that multiple folders are stored.
Context
There are two reasons for this feature:

Spark datasets can be versioned and to read those into Pandas using transcoding, we'll need a versioned PartitionedDataSet.
I'd like to compare changes in the output of my pipeline (and store past output for future reference) which cannot be stored in any other format than a PartitionedDataSet. Others might have the same need.

Possible Implementation
Borrow code from other versioned datasets.

Closing comment (2022-12-12T17:36:40Z): Thanks for raising this @mle-els ! We've had similar requests before. The main reason we haven't implemented this functionality yet, is because it's very complex. We have now decided to investigate both the demand from users and implementation of a versioned partitioned dataset. This work will be tracked in #2115
Repository: kedro-org/kedro

Issue #4467: [Spike] Decide on versioning: keep or remove
Created: 2025-02-07T11:45:52Z
Description
While we've done a lot of exploration into integrating Kedro with other tools to facilitate versioning, we haven't actually made the decision to keep or remove the native Kedro versioning feature.
The purpose of this spike is to collect information and insights into what it would mean if we removed the native versioning feature, so that we can make a decision.

Pros & cons of removal
Impact of removal: what does this mean for users? For other features?
Estimate of engineering effort of removal

Context
#4199 (comment)
#4199 (comment)
#4129 (comment)

Duplicate issue #1979: How can we improve dataset versioning?
Created: 2022-10-26T13:32:08Z
Introduction
The catalog and dataset APIs and code needs to be improved. One of the most complex things related to datasets and the catalog is versioning. As a team we need to get a better understanding of how versioning works, so we can refactor it.
Background
#1778
What's in scope

Understand how versioning works: can be a group exercise or one person can to a deep dive and teach the team
A proposal of how to improve versioning.

Closing comment (2025-02-13T09:23:24Z): This is being tracked in #4467
Repository: kedro-org/kedro

Issue #3386: Don't include requirements only needed for example pipeline
Created: 2023-12-04T14:53:04Z
Description
With the tools selection flow requirements get added but the following are only needed for running the example pipeline and also get included if the user doesn't want the example:

seaborn
scikit-learn
kedro-datasets[....] the problem here is not kedro-dataset itself, but the preselected specific datasets e.g. ExcelDataset.

Duplicate issue #3433: README generated by `kedro new` references Spaceflights, even if that's not what you chose
Created: 2023-12-15T23:22:15Z
Description
Seems to be yet another issue related to modifying the starter template...
Context
I just noticed it was wrong, when trying to create a starter myself.
Steps to Reproduce
Run kedro new with data and viz tools included (as an example).
Expected Result
Leave out the stuff about Spaceflights.
This is your new Kedro project, which was generated using `kedro 0.19.1`.
would work.
Actual Result
It says:
This is your new Kedro project for the [spaceflights tutorial](https://docs.kedro.org/en/stable/tutorial/spaceflights_tutorial.html) and the extra tutorial sections on [visualisation with Kedro-Viz](https://docs.kedro.org/projects/kedro-viz/en/stable/kedro-viz_visualisation.html) and [experiment tracking with Kedro-Viz](https://docs.kedro.org/projects/kedro-viz/en/stable/experiment_tracking.html), which was generated using `kedro 0.19.1`.
Your Environment


Kedro version used (pip show kedro or kedro -V): 0.19.1
Python version used (python -V): 3.11.5
Operating system and version: OSX

Closing comment (2023-12-15T23:34:44Z): Somewhat related to #3386.
Repository: kedro-org/kedro

Issue #2669: Update documentation around credentials management
Created: 2023-06-12T15:41:08Z
Description
Short description of the problem here.
parquet_dataset:
  type: dask.ParquetDataSet
  filepath: "s3://bucket_name/path/to/folder"
  credentials:
    client_kwargs:
      aws_access_key_id: YOUR_KEY
      aws_secret_access_key: "YOUR SECRET"
This is the way we mentioned how to provide credentials in Kedro's doc. However fsspec has update the API for quite a while and if you are using newer version of fsspec, you should use key,secret instead of aws_access_key_id instead.
It could be only affecting s3fs (This is how I bump into error), but potentially affect gcs and more.
Context
The docs on credentials are out of date and mention wrong key names. All doc chapters mentioning credentials should be updated to use the correct keys.

Duplicate issue #3164: Consolidate credentials documentation
Created: 2023-10-11T15:50:50Z
Description
There is lots of useful credential related information in the docs, but it's not actually all in the  main credentials page.
Env vars and hooks are our recommended pattern for advanced users - we don't make this clear in the main credentials page.

Env vars are linked in this page, but it's not actually very visible.
After context created hooks are our recommended pattern for advanced users and this is not linked at all in the docs.

I propose we move all the examples and details of the above patterns to the main credentials page and link to that from the advanced config and hook examples pages respectively.

Closing comment (2023-10-11T15:55:32Z): Duplicate (or at least related) to #2669 ?
Repository: kedro-org/kedro

Issue #2307: Automatically skip running nodes with persisted outputs
Created: 2023-02-10T16:35:14Z
Description
Re-running nodes which have:

Persisted outputs
No upstream dependencies which would cause their output to change

is an unnecessary expense. It might be a good idea to have a flag which would automatically skip running these nodes.
It is currently possible to achieve this by specifying nodes to run from, though this process is manual and potentially error-prone.
Context
User @pedro-sarpen opened #2005 to address this issue, though there may be a better solution to the problem that we should investigate.

Duplicate issue #2057: Performance analysis and smart re-running of pipelines
Created: 2022-11-23T15:53:01Z
Description
Kedro currently doesn't offer any options to analyse the performance of pipelines. Additionally, our users have flagged that they would like to be able to re-run only parts of their pipeline.
Implementation ideas

Stats on performance of pipelines
Record Kedro run metadata and use it for suggesting pipeline optimisations
Make Kedro run faster
Rerun Kedro Pipeline should be smarter. Only re-run necessary data "kedro run -xxx"

Questions

Closing comment (2025-02-18T12:08:28Z): Kedro currently doesn't offer any options to analyse the performance of pipelines.

Similarly to #4264, what prevents users from using cProfile, line-profiler, PyInstrument, or any other Python tool for performance analysis?

Additionally, our users have flagged that they would like to be able to re-run only parts of their pipeline. [...] Only re-run necessary data "kedro run -xxx"

Tracked in #2307, more context in #221

Moving this to Discussions
Repository: keepassium/KeePassium

Issue #259: Quick Auto Fill fills nothing on macOS
Created: 2022-10-03T10:49:31Z
Description
The quick fill does now work on macOS. The quick fill window shows, but when the TouchID is pressed, nothing is filled.

  
    
    

    2022-10-03.03.35.57.mov
    
  

  

  


How to reproduce
Steps to reproduce the behavior:

Download KeePassium on MacOS
Open any website and setup quick auto fill
Reboot the macOS, than repeat step 2
See error

Expected behavior
The KeePassium works like the iCloud Password Manager
Below is the screen recording of what iCloud Password Manager works like

  
    
    

    2022-10-03.03.45.45.mov
    
  

  

  


Environment:

Device: MacBook Air M2 2022
OS: macOS 12.6
App Version: 1.36

Duplicate issue #374: Cant fill in any password in Safari
Created: 2024-07-05T16:45:50Z
KeePassium is configured for password management
I can select KeePassium in a password field as password supplier
I can login in the KeePassium password db
I can select an Item
but the password will not filled in in the password field of the website
Expected behavior
Put the password of the selected entry in the password field of the website
Environment:
macOS Sonoma 17.5,
Safari 17.5 (19618.2.12.11.6)

Closing comment (2024-07-05T22:13:32Z): Unfortunately, this is a system issue. Closing as duplicate of #259
Repository: keepassium/KeePassium

Issue #153: Manual TOTP setup
Created: 2021-03-26T16:01:57Z
Describe the feature you'd like
Hello I immediately noticed as a user that the TOTP setup in KeePassium is very cumbersome and you don't immediately know how to set it up in KeePassium.
It is not designed in a user-friendly way, only by searching the internet search later did I find out how it works on your website. I find it very poorly designed.
I think it's better if an app is designed in such a way that it works immediately at first sight or through logical behaviour in the UI.
In this case, that means adding a setup for TOTP. Under entry "TOTP setup" button should be added, when user clicks on it he can set the time (by default it uses the default values) and can simply insert the key in field and click "OK", then it is set up immediately in 3 steps.

Duplicate issue #220: Easy entry of TOTP token by using "otp" or "verification code" as the field name
Created: 2022-03-21T23:00:58Z
Describe the feature you'd like
Allow "otp" and "verification code" to be alternative one-time password field labels. Or make a field with one of those labels automatically create the "TOTP Seed" and "TOTP Setting" fields (that must be entered with the exact case) with defaults for "TOTP Setting".
I'm trying to migrate from 1Password KeePassium by placing the apps side-by-side and manually copying items over. It's tedious to have to type and define both TOTP Seed and TOTP Settings fields.

Closing comment (2022-03-21T23:02:26Z): Related to #153