primordic/IssueDupesLite huggingface dataset:
Repository: dpkp/kafka-python

Issue #2290: is kafka-python deprecated?
Created: 2022-01-05T23:29:59Z
No release in 1.5 yrs. Just wondering if eventually changes on Kafka broker will become incompatible with what we have. Is the project dead?

Duplicate issue #2349: Is this library maintained?  Is there a fork that is more maintained?
Created: 2023-01-20T11:33:48Z
There has not been an update besides documentation fixes in 3 years, nor a release in the same amount of time.  The officially supported version of python is only 3.8 (we are now at 3.11), and the officially supported version of Kafka is 2.9 (I believe 3.2 is the latest).  Additionally the owner no longer appears active on github.

Closing comment (2023-01-20T22:16:03Z): Closing as a duplicate of:

#2290

In particular, see #2290 (comment)
Repository: dpkp/kafka-python

Issue #592: KAFKA-3007: implement max.poll.records (KIP-41)
Created: 2016-03-14T07:53:40Z

Duplicate issue #823: KAFKA-3007: max.poll.records
Created: 2016-08-31T10:29:46Z
when dose kaka-python support max.poll.records option？
thx

Closing comment (2016-09-20T04:06:16Z): duplicate of #592
Repository: dpkp/kafka-python

Issue #1371: KafkaConsumer dies with IndexError: pop from an empty deque
Created: 2018-02-08T17:26:36Z
Since updating to 1.4.0 this error started showing up after running the consumer for some seconds:
    for msg in self.consumer:
  File "/home/user/.local/lib/python2.7/site-packages/kafka/vendor/six.py", line 561, in next
    return type(self).__next__(self)
  File "/home/user/.local/lib/python2.7/site-packages/kafka/consumer/group.py", line 1117, in next
    return next(self._iterator)
  File "/home/user/.local/lib/python2.7/site-packages/kafka/consumer/group.py", line 1061, in _message_generator
    self._client.poll(timeout_ms=poll_ms)
  File "/home/user/.local/lib/python2.7/site-packages/kafka/client_async.py", line 577, in poll
    responses.extend(self._fire_pending_completed_requests())
  File "/home/user/.local/lib/python2.7/site-packages/kafka/client_async.py", line 669, in _fire_pending_completed_requests
    response, future = self._pending_completion.popleft()
IndexError: pop from an empty deque
On my test machine this happens always after a few seconds of running the consumer.
Sometimes the consumer dies completely sometimes it carries on.
From my debugging it seems that if it hits the heartbeat Thread, the consumer won't die but if it hits my mainthread it's game over.

Duplicate issue #1377: Kafka Consumer tries to pop from empty deque
Created: 2018-02-09T15:11:56Z
After upgrading from python-kafka 1.3.5 to 1.4.0 we observed the following unhandled exception. The exception occured only randomly and not too often and was observed only under a production load, not under automated functional tests of our application.
Traceback (most recent call last):
...
File "<our app>.py", line 44, in <our method>
    for event in kafka_consumer:
File "/usr/local/lib/python2.7/site-packages/kafka/vendor/six.py", line 561, in next
    return type(self).__next__(self)
File "/usr/local/lib/python2.7/site-packages/kafka/consumer/group.py", line 1117, in __next__
    return next(self._iterator)
File "/usr/local/lib/python2.7/site-packages/kafka/consumer/group.py", line 1061, in _message_generator
    self._client.poll(timeout_ms=poll_ms)
File "/usr/local/lib/python2.7/site-packages/kafka/client_async.py", line 577, in poll
    responses.extend(self._fire_pending_completed_requests())
File "/usr/local/lib/python2.7/site-packages/kafka/client_async.py", line 669, in _fire_pending_completed_requests
    response, future = self._pending_completion.popleft()
IndexError: pop from an empty deque

Closing comment (2018-02-09T15:54:21Z): Dup of #1371 (please upgrade to 1.4.1)
Repository: dpkp/kafka-python

Issue #1346: KafkaConsumer.position can block forever when single broker is unreachable
Created: 2018-01-14T14:32:05Z
I have a situation where I am attempting to get the offset of the next record for each partition in a topic. When one of my brokers are down/unreachable via network, then it blocks. I can't figure out which of these timeout options I can tune to break out of this.
consumer = KafkaConsumer(bootstrap_servers=config.brokers, api_version=(0,10,1), reconnect_backoff_max_ms=100, fetch_max_wait_ms=config.session_timeout_ms, session_timeout_ms=config.session_timeout_ms, \
                        request_timeout_ms=config.request_timeout_ms, consumer_timeout_ms=2000, auto_offset_reset='latest')
        ps = [TopicPartition(config.topic, p) for p in consumer.partitions_for_topic(config.topic)]
        print("Assigning...")
        consumer.assign(ps)
        for p in ps:
            print(p)
            pos = consumer.position(p)

This will block at pos = consumer.position(p) once it attempts to retrieve the position from a partition belonging to the unreachable broker.
  File "/usr/lib64/nagios/plugins/kafka/consumer/fetcher.py", line 194, in update_fetch_positions
    self._reset_offset(tp)
  File "/usr/lib64/nagios/plugins/kafka/consumer/fetcher.py", line 245, in _reset_offset
    offsets = self._retrieve_offsets({partition: timestamp})
  File "/usr/lib64/nagios/plugins/kafka/consumer/fetcher.py", line 295, in _retrieve_offsets
    time.sleep(self.config['retry_backoff_ms'] / 1000.0)

Duplicate issue #1764: Consumer blocks indefinitely in `poll` when assigned partitions and brokers are unavailable
Created: 2019-03-26T02:56:18Z
Firstly: thanks (!) for writing this library.
I'm not sure if this is user error, a bug or a feature, but the following blocks indefinitely on the poll() command (no broker needed) in python2 and python3 on 1.3.5, 1.4.3, 1.4.5 as well as on 1.4.6.dev:
from kafka import KafkaConsumer, TopicPartition
# N.B. "yyy" does not resolve to any hostname on my network
consumer = KafkaConsumer(bootstrap_servers='yyy:9092', api_version='0.10.1')
consumer.assign([TopicPartition('zzz', 0)])
r_poll = consumer.poll(timeout_ms=1000)
I've also tested it by replacing "yyy" above with local hosts whose dns entries are defined but which have been turned off with the same results (blocks indefinitely). Adding group_id to KafkaConsumer also doesn't seem to help.
P.S. Removing the api_version='0.10.1' allows the KafkaConsumer() call to return immediately with no brokers available in 1.4.6.dev, blocks indefinitely on KafkaConsumer() in 1.4.5, returns immediately in 1.3.5.

Closing comment (2020-02-12T20:51:59Z): Closing as dupe of #1346
Repository: dremin/RetroBar

Issue #47: Allow for the system tray icons to be hid
Created: 2021-08-16T10:29:38Z
It's in the title

Duplicate issue #161: turn off unnecessary icons in tray
Created: 2021-11-11T16:24:45Z
for example i dont need those icons, I can't turn them off in any way, please add the option to turn them off

Closing comment (2022-01-10T04:30:53Z): Closing as duplicate of #47
Repository: dremin/RetroBar

Issue #45: Add a Windows 7 theme please
Created: 2021-07-23T06:51:52Z
Title says it all

Duplicate issue #832: Suggestion: Windows 7 bar adding.
Created: 2024-05-08T10:03:12Z
If you add windows 7 bar its can be good I guess.

Closing comment (2024-07-17T00:49:14Z): Duplicate of #45
Repository: dremin/RetroBar

Issue #19: Drag to rearrange Quick Launch icons and open windows
Created: 2021-06-13T13:22:54Z
Currently, dragging to rearrange Quick Launch icons and open windows does not work. It would be great if you implemented this feature.

Duplicate issue #165: Wishes: drag drop of taskbar buttons(?), double height taskbar, "Show the desktop" in context menu, option to make mouse wheel click on taskbar button(?) to close the app. Else perfect!!!
Created: 2021-11-15T00:37:45Z
Wishes:
-drag drop of taskbar buttons(?)
Very nice to have. Drag drop of notification icons could be nice too, but not important.
-double height taskbar
A blocker for me. I always use double height taskbar.
-"Show the desktop" in context menu
Currently only show "Task Manager". Would like to see "Show the desktop" too.
-option to make mouse wheel click on taskbar button(?) to close the app
I use 7+ Taskbar Tweaker to set this normally, but RetroBar should have its own option for this.
But very promising!!! I feel this could become something huge.

Closing comment (2021-11-15T10:23:32Z): №1 is a duplicate of #19, and №2 is a duplicate of #14.
Also №5 is a possible duplicate of #84, though by default this button is located at the very right
Repository: dremin/RetroBar

Issue #45: Add a Windows 7 theme please
Created: 2021-07-23T06:51:52Z
Title says it all

Duplicate issue #935: please i beg of you, add a windows 7 aero theme
Created: 2024-10-23T06:05:52Z
pretty please with a cherry on top
with all my heart i am begging you
i know you said something about retrobar emulating the pre windows 7 era or something, but hear me out
windows 7 came out in 2009, its aero theme is already pretty retro and iconic, it has been a part of many peoples childhoods including mine. who doesnt love aero? and personally, out of vista and 7, windows 7 pulls off the aero far better. also you have definetly noticed that a lot of people want to see a windows 7 theme for retrobar, so it is already pretty sought after.
in general it would be really awesome to see a 7 aero theme on retrobar

Closing comment (2024-11-29T21:58:45Z): Closing as duplicate of #45.
Repository: dremin/RetroBar

Issue #45: Add a Windows 7 theme please
Created: 2021-07-23T06:51:52Z
Title says it all

Duplicate issue #582: Add a windows 7 theme. The other way to get the windows 7 taskbar costs money since you have to use stardock.
Created: 2023-05-19T21:55:38Z

Closing comment (2023-05-19T21:58:19Z): Duplicate of #45
Repository: dremin/RetroBar

Issue #70: Windows 10 shortcut to switch windows not working.
Created: 2021-08-31T20:34:46Z
Normally with the normal taskbar, you can use shortcuts (like Win+1, Win+2 etc) to switch between windows but with Retrobar, the shortcuts don't work. Is it because the taskbar process is gone while Retrobar runs?

Duplicate issue #929: [Feature Request] WinKey + Num Shortcut
Created: 2024-10-17T07:29:02Z
Just like the built-in taskbar. WinKey + N (number), opens the Nth item on the tasklist.

Closing comment (2024-11-29T22:26:04Z): Closing as duplicate of #70.
Repository: dremin/RetroBar

Issue #14: change taskbar size
Created: 2021-05-09T21:55:31Z
i love the program,but there is a way yo increase the taskbar size? thaks!!

Duplicate issue #647: Resize taskbar width for vertical bar
Created: 2023-08-01T15:17:34Z
is it possible to add resizing taskbar width for vertical taskbar till start button width or even less.
although i'm not sure  does  win95-98-me  have this one.

Closing comment (2023-11-12T06:04:15Z): Duplicate of #14
Repository: dremin/RetroBar

Issue #14: change taskbar size
Created: 2021-05-09T21:55:31Z
i love the program,but there is a way yo increase the taskbar size? thaks!!

Duplicate issue #135: [Request] Taskbar Size
Created: 2021-10-26T17:33:11Z
i have a 4k monitor and as such the taskbar is... really really tiny compared to everything LMAO
for reference, the height of my taskbar without retrobar is 60px. retrobar is like 45px
would it be possible if, in the future, we could edit the size of the bar to make it more readable on bigger monitors?

Closing comment (2022-03-10T05:22:47Z): Closing as duplicate of #14
Repository: dremin/RetroBar

Issue #313: Issue - Retrobar crashes explorer constantly in windows 11 beta insider
Created: 2022-04-04T19:23:18Z
I have been trying to deal with this problem for multiple hours now, after my entire os got bootlooped for this bug
Yes, that's right, this bug has bootlooped my pc entirely, and i have just now traced the bug to retrobar.
it was restarting explorer constantly, somehow corrupted some random shell file, and unlucky me had that shell file be essential to svchost.exe
WER logs:
Faulting application name: explorer.exe, version: 10.0.22581.200, time stamp: 0x44383e7a
Faulting module name: ucrtbase.dll, version: 10.0.22581.1, time stamp: 0xf5fc15a3
Exception code: 0xc0000409
Fault offset: 0x000000000007f61e
Faulting process id: 0x0x329C
Faulting application start time: 0x0x1D8485810E13427
Faulting application path: C:\WINDOWS\explorer.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 298a51d8-075c-4c5b-af13-a0e7d4d0ff3b
Faulting package full name:
Faulting package-relative application ID:

Duplicate issue #457: Retrobar Crashes Explorer
Created: 2022-11-02T18:36:01Z
When explorer's shell restarts or opens while retrobar active, explorer crashes (making a crash loop of explorer)
Whatever this program does to keep the taskbar inactive in normal explorer seems to be crashing explorer on startup
The shell stopped unexpectedly and explorer.exe was restarted.
Source: WinLogon
EventSourceName: Wlclntfy
Event ID: 1002

Closing comment (2024-11-29T22:23:36Z): Probably (?) fixed by the latest build, as mentioned in issue #964. Will re-open if this appears again.
PS: I love how one bug spans over 3 Pull Requests + 11 'issues', and I made 3 of them. At least this issue is the 'definitive' issue, I guess.
Although technically this is a duplicate of #313
Repository: dremin/RetroBar

Issue #377: Quick Launch shows too many icons
Created: 2022-07-19T19:05:14Z
When I enable the quick launch area, there is no way to adjust how many icons are shown.
All of them are shown because this separator-like thing is missing which would allow me to adjust how many icons are shown (the rest would be accessible in a menu)
https://i.postimg.cc/0jG1sRQF/quicklaunch.jpg
I also think it would be nice if RetroBar used the same font and font size as the system setting (or at least it should be possible to set the font and font size in Retrobar's settings)

Duplicate issue #412: Unable to collapse quick launch
Created: 2022-08-04T17:12:16Z
More of a missing feature rather than a bug with something existing. There is no option to collapse the quick launch into just a few that show 24/7.

Closing comment (2024-11-29T22:44:03Z): Closing as duplicate of #377.
Repository: droe/sslsplit

Issue #46: Improve handling of renegotiation and client cert authentication
Created: 2014-11-04T17:51:53Z
Handle renegotiations and client certificate authentication more gracefully.

Duplicate issue #173: Client certificate authentication
Created: 2017-07-13T22:05:15Z
sslsplit works fine on sites that do not require server side client certs, if they do it can only handle them with the -P (passthrough) option.
Works when I actually connect to the site and not sslsplit:
curl -k --cert ca.cert.pem --cacert  ca.cert.pem --key key.pem -v https://somesite:8181
Fails when I try to go through sslsplit:
curl -k --cert ca.cert.pem --cacert  ca.cert.pem --key key.pem -v https://localhost:8181
with this error: Error from bufferevent: 0:- 336151570:1042:sslv3 alert bad certificate:20:SSL routines:148:ssl3_read_bytes
packet traces reveal the server is sending a bad certificate error presumably because the client (sslsplit) sent no client cert. The client cert does not appear to be being validated as the certs I am sending are self-signed, but the server is definitely requiring the cert to be there.
It would be nice to be able to specify a default client cert to avoid this. Will look at it.

Closing comment (2018-01-03T22:42:19Z): Duplicate of #46, closing this issue, thanks for your report.
Repository: droe/sslsplit

Issue #248: Certificate error: loading src server certificate failed
Created: 2019-03-01T13:06:45Z
This is very similar to #246.  I'm running Kali 2019.1 with SSLsplit 0.5.4 and see the "loading src server certificate failed" error..  I tested the same commands using SSLsplit 0.5.2 and everything works fine.
Below are the commands that I used to set up the server, client and SSLsplit.  The failing output from the server, client and SSLsplit are attached.
Server
The default options were used for the openssl req command.
openssl genrsa -out server.key 2048
openssl req -new -key server.key -out server.csr
openssl x509 -req -in server.csr -signkey server.key -out server_signed_cert.pem
openssl s_server -accept 9999 -key server.key -cert server_signed_cert.pem -debug

SSLsplit
The default options were used for the openssl req command.
openssl genrsa -out fake.key 2048
openssl req -new -key fake.key -out fake.csr
openssl x509 -req -in fake.csr -signkey fake.key -out fake_signed_cert.pem
sslsplit -D -c fake_signed_cert.pem -k fake.key ssl 0.0.0.0 8888 192.168.128.129 9999

Connections
Initial connection directly to server to prove the server/client works fine:
openssl s_client -connect 192.168.128.129:9999
Follow up connection via SSLsplit:
openssl s_client -connect 192.168.128.134:8888
openssl-client-trace.txt
openssl-server-trace.txt
sslsplit-trace.txt

Duplicate issue #246: Certificate error: loading src server certificate failed
Created: 2019-02-07T12:01:04Z
I 'm having the same issue like reported in #224.
The error I get is loading src server certificate failed.
I built multiple variations of sslsplit with different versions of openssl and without any success.
I think the problem is with storing the on-the-fly created certificates. When I used the -w Parameter, the directory only contained *.key files and no certificate files. This would explain why the certificates can't be loaded. It seems the certififacte is created correctly, but not stored properly as far as I can tell.
My setup is running on a Kali 2019.1

Closing comment (2019-08-02T10:03:48Z): Duplicate of #248
Repository: droe/sslsplit

Issue #248: Certificate error: loading src server certificate failed
Created: 2019-03-01T13:06:45Z
This is very similar to #246.  I'm running Kali 2019.1 with SSLsplit 0.5.4 and see the "loading src server certificate failed" error..  I tested the same commands using SSLsplit 0.5.2 and everything works fine.
Below are the commands that I used to set up the server, client and SSLsplit.  The failing output from the server, client and SSLsplit are attached.
Server
The default options were used for the openssl req command.
openssl genrsa -out server.key 2048
openssl req -new -key server.key -out server.csr
openssl x509 -req -in server.csr -signkey server.key -out server_signed_cert.pem
openssl s_server -accept 9999 -key server.key -cert server_signed_cert.pem -debug

SSLsplit
The default options were used for the openssl req command.
openssl genrsa -out fake.key 2048
openssl req -new -key fake.key -out fake.csr
openssl x509 -req -in fake.csr -signkey fake.key -out fake_signed_cert.pem
sslsplit -D -c fake_signed_cert.pem -k fake.key ssl 0.0.0.0 8888 192.168.128.129 9999

Connections
Initial connection directly to server to prove the server/client works fine:
openssl s_client -connect 192.168.128.129:9999
Follow up connection via SSLsplit:
openssl s_client -connect 192.168.128.134:8888
openssl-client-trace.txt
openssl-server-trace.txt
sslsplit-trace.txt

Duplicate issue #244: loading src server certificate failed
Created: 2018-12-01T02:16:50Z
Hi,
Straightforward brand new set up
Windows 10 client using a gateway to a kali mitm
traffic flow is fine to/fro client to the Internet via kali
I get loading src server certificate failed on port 443 (if (SSL_CTX_use_certificate(sslctx, crt) != 1)). Same behavior if using chrome browser or edge browser on the client, also same behavior when request comes from a locally installed app that attempts authentication to a remote server via port 443
I used https://blog.heckel.xyz/2013/08/04/use-sslsplit-to-transparently-sniff-tls-ssl-connections/ for basic configuration. The sslsplit certificate is installed in trusted root certification authorities on Windows client
Please let me know.
Thanks!
ca_crt.txt
iptables_rules.txt
openssl_version.txt
sslsplit_command.txt
sslsplit_debug_output.txt
sslsplit_V.txt
uname_a.txt
ca.key.txt

Closing comment (2019-08-02T10:03:04Z): Duplicate of #248
Repository: droe/sslsplit

Issue #20: Option -t loads files after detaching from TTY and chroot()
Created: 2014-01-29T19:51:55Z
Using -t fails under many circumstances, such as with encrypted keys in daemon mode, when chroot() is used, or when the user we drop privs to lacks the permissions to read the file.
-t should be rewritten to load the certificates into a list of cert_t before detaching from TTY; that list would need to be added to the certificate cache after detaching.

Duplicate issue #19: Option -t fails to load certificate on Linux
Created: 2014-01-29T11:31:12Z
sslsplit -D -l connections.log -j /tmp/sslsplit/ -S logdir/ -P -t ./certs/ ssl 0.0.0.0 9443 tcp 0.0.0.0 9080
...
Failed to load cert and key from PEM file './certs/'

certs directory exists and have a single PEM file inside (foobar.pem):
-----BEGIN ENCRYPTED PRIVATE KEY-----
MIIFDjBABgkqhkiG9w0BBQ0wMzAbBgkqhkiG9w0BBQwwDgQIb0sfVok+83ECAggA
MBQGCCqGSIb3DQMHBAiR0r6JINsSZgSCBMiEauatBQlxvspUMgYYL/EMznz3dXm3
Q...
-----END ENCRYPTED PRIVATE KEY-----
-----BEGIN CERTIFICATE-----
MIIDbzCCAlegAwIBAgIJANHqAxI0u/R9MA0GCSqGSIb3DQEBBQUAME4xCzAJBgNV
BAYTAkFVMRMwEQYDVQQIDApTb21lLVN0YXRlMREwDwYDVQQKDAhGYWNlYm9vazEX
MBUGA1UEAwwOKi5mYWNlYm9vay5jb20wHhcNMTQwMTI5MTAxNjE2WhcNMTkwMTI5...
-----END CERTIFICATE-----

I believe that the problem resides inside the sys.c/sys_dir_eachfile function which incorrectly traverses through directory structure.

Closing comment (2014-01-30T21:00:43Z): Looking at this again, I see the problem now. I totally missed the -j in your invocation, sorry. If you don't use -j then it should work. It should also work if you move the certs directory to /tmp/sslsplit/certs.
This bug is actually a result of the fact that -t loads the certificates after dropping privileges. I'm closing this issue as a duplicate of #20.
Repository: droe/sslsplit

Issue #18: Loading AJAX-heavy sites can completely stall with https proxyspecs
Created: 2014-01-14T23:38:39Z
Loading AJAX-heavy sites through SSLsplit can cause browsers to stall completely, seemingly loading forever without any progress. I suspect this has to do with the fact that SSLsplit downgrades Connection: keep-alive to Connection: close and removes other headers related to performance-improving HTTP features such as chunking. SSLsplit does that in order to get nice and clean, uncompressed and unencoded, straightforward loggable and tweakable HTTP requests and responses. However, this puts a lot of strain on browsers, servers and SSLsplit itself since it causes the browser to send lots of requests at the same time. This definitely needs more investigation.
As a workaround, using ssl proxyspecs instead of https disables all the HTTP header munging and generally gives better performance, at the cost of reduced features (e.g. no OCSP denial, less readable logs).
SSLsplit should probably implement more of the HTTP features like chunking, pipelining etc, but this would require a major rewrite of the https connection handling code.

Duplicate issue #25: Requests are compounded
Created: 2014-04-11T09:32:09Z
While parsing the log there are often requests like this:
2014-04-10 15:46:59 UTC [192.168.3.132]:50126 -> [2.16.170.224]:80 (460):
GET /configurations/pep/pipeline/pipeline0.html HTTP/1.1
Host: configuration.apple.com
Connection: Keep-Alive
GET /configurations/pep/pipeline/pipeline1.html HTTP/1.1
Host: configuration.apple.com
Connection: Keep-Alive
GET /configurations/pep/pipeline/pipeline2.html HTTP/1.1
Host: configuration.apple.com
Connection: Keep-Alive
GET /configurations/pep/pipeline/pipeline3.html HTTP/1.1
Host: configuration.apple.com
Connection: Keep-Alive
The responses aren't  compound like this and have seperate metadata.
Also a request counter for assigning a requests to its response whould be great.
The only solution for this I see is to compound also the responses with this connection counter.

Closing comment (2014-04-14T17:35:42Z): Possibly related to #18.
Repository: droe/sslsplit

Issue #27: Save traffic in PCAP format
Created: 2014-06-24T07:22:39Z
Is it possible to add a logging option that saves traffic in a format readable by Wireshark? This would make dissecting binary protocols over SSL much easier to analyse.

Duplicate issue #101: Using SSLsplit to feed decrypted data to IDS
Created: 2015-06-30T21:52:55Z
Hi folks,
I'm trying to find a way staying open source to get SSL traffic transparently over to an IDS.  I have commercial solutions that can do similar SSL intercept but they can get expensive.  Is there a way with SSLSplit to have it send the decrypted packet say out to a specified mac address?  I'm thinking if I had a system running sslsplit and another system running something like security onion if I could tell SSLSplit to duplicate all packets unencrypted to a mac address (so security onion would need to be on an attached network) I could then inspect the encrypted traffic.  Any suggestions?

Closing comment (2015-09-28T11:26:18Z): Marking this a duplicate of #27.
Repository: droe/sslsplit

Issue #214: SSLSPLIT doesnt do anything.
Created: 2018-09-03T18:19:12Z
Please supply the following with bug reports to allow for diagnostics:

Output of sslsplit -V

SSLsplit 0.5.2 (built 2018-03-31)
Copyright (c) 2009-2018, Daniel Roethlisberger <daniel@roe.ch>
https://www.roe.ch/SSLsplit
Build info: V:FILE
Features: -DHAVE_NETFILTER
NAT engines: netfilter* tproxy
netfilter: IP_TRANSPARENT IP6T_SO_ORIGINAL_DST
Local process info support: no
compiled against OpenSSL 1.1.0h  27 Mar 2018 (1010008f)
rtlinked against OpenSSL 1.1.0h  27 Mar 2018 (1010008f)
OpenSSL has support for TLS extensions
TLS Server Name Indication (SNI) supported
OpenSSL is thread-safe with THREADID
Using SSL_MODE_RELEASE_BUFFERS
SSL/TLS protocol availability: tls10 tls11 tls12 
SSL/TLS algorithm availability: !SHA0 RSA DSA ECDSA DH ECDH EC
OpenSSL option availability: SSL_OP_NO_COMPRESSION SSL_OP_NO_TICKET SSL_OP_ALLOW_UNSAFE_LEGACY_RENEGOTIATION SSL_OP_DONT_INSERT_EMPTY_FRAGMENTS SSL_OP_NO_SESSION_RESUMPTION_ON_RENEGOTIATION SSL_OP_TLS_ROLLBACK_BUG
compiled against libevent 2.1.8-stable
rtlinked against libevent 2.1.8-stable
4 CPU cores detected


Output of uname -a
Linux kali 4.17.0-kali1-amd64 #1 SMP Debian 4.17.8-1kali1 (2018-07-24) x86_64 GNU/Linux
Exact command line arguments used to run sslsplit
V -D -k  ca.key -c ca.crt -P  https 127.0.0.1 8443  https ::1 8443
NAT redirection rules you are using, if applicable

iptables -t nat -A PREROUTING -p tcp --dport 443 -j REDIRECT --to-ports 8443
iptables -t nat -A PREROUTING -p tcp --dport 80 -j REDIRECT --to-ports 8443

For build problems, please supply:
So after running sslslip it starts and then waits at line.
Starting main event loop.
I'm opening https websites but nothing is sniffed

Duplicate issue #213: Q: Intra-LAN client to server sslsplit
Created: 2018-09-03T13:26:03Z
Hello,
can sslsplit intercept an SSL connection between a client (macos) and server (webos) both connected to the same LAN via a switch/router where sslsplit runs on the same host as the client ?
All services to be intercepted are on the LAN, and none of the pf rules I've added get sslsplit to detect any connection. This scenario is close to the one in issue #212 but without an iphone.
Thank you.

Closing comment (2018-09-04T10:45:48Z): Similar to #214, to intercept traffic on intra LAN, traffic needs to be directed to a separate host/VM running sslsplit and setup the appropriate routing rules.
Repository: droe/sslsplit

Issue #94: Acting as browser-configured HTTP or SOCKS proxy
Created: 2015-05-01T09:52:01Z
SSLsplit currently only supports transparently intercepting connections. It would be useful to also support configuration as HTTP or SOCKS proxy (see #93). This however would require quite a rewrite of the proxy core (also see #40).

Duplicate issue #130: Can we modify sslsplit to socks5 proxy?
Created: 2016-04-04T02:04:34Z
I think it will make trivial modification to let sslplit change to socks5 proxy, through creating new engine in nat.c, and get source ip and nat from socks5 head.
My issue is I don't know where to add socks5 head for each response session.

Closing comment (2016-04-04T09:43:10Z): Duplicate of #94, closing this ticket, please move discussion there.
Repository: droe/sslsplit

Issue #10: Segmentation fault starting thread manager
Created: 2013-08-23T11:04:25Z
Hello,
when I try to run sslsplit (having libssl-dev and libevent-dev installed,generating self-signed certificates and using port forwarding before this) I get the following error:
Inserted events:
  0x9a01148 [fd 7] Read Persist
  0x9a0291c [fd 8] Read Persist
  0x9a01038 [fd 6] Read Persist
  0x9a02968 [fd 3] Signal Persist
  0x9a02ad0 [fd 1] Signal Persist
  0x9a02bb0 [fd 2] Signal Persist
  0x9a02c90 [fd 13] Signal Persist
Failed to start thread manager
Segmentation fault

I'm using:
./sslsplit -D -l connections.log -j /tmp/sslsplit/ -S logdir/ -k ca.key -c ca.crt ssl 0.0.0.0 9000

on the command line.
Could this be a resurfacing of previously reported bug (issue #9)?
Thank you

Duplicate issue #11: Segfault with OpenSSL version mismatch
Created: 2013-12-02T08:25:54Z
Comment by @exvance moved from #10 to new issue:
I don't know if my issue is the same as this one. It doesn't seem to matter whether or not I use the -j option.
sslsplit -D -l connections.log -k ca.key -c ca.crt ssl 0.0.0.0 8443
Generated RSA key for leaf certs.
SSLsplit (built 2013-11-29)
Copyright (c) 2009-2013, Daniel Roethlisberger daniel@roe.ch
http://www.roe.ch/SSLsplit
Features: -DDISABLE_SSLV2_SESSION_CACHE -DHAVE_NETFILTER
NAT engines: netfilter*
netfilter: !IP_TRANSPARENT SOL_IPV6 !IPV6_ORIGINAL_DST
compiled against OpenSSL 1.0.1e 11 Feb 2013 (1000105f)
rtlinked against OpenSSL 1.0.1c 10 May 2012 (1000103f)
TLS Server Name Indication (SNI) supported
OpenSSL is not thread-safe
Using direct access workaround when loading certs
SSL/TLS algorithm availability: RSA DSA !ECDSA DH !ECDH !EC
OpenSSL option availability: SSL_OP_NO_COMPRESSION SSL_OP_NO_TICKET SSL_OP_ALLOW_UNSAFE_LEGACY_RENEGOTIATION SSL_OP_DONT_INSERT_EMPTY_FRAGMENTS SSL_OP_NO_SESSION_RESUMPTION_ON_RENEGOTIATION SSL_OP_TLS_ROLLBACK_BUG
compiled against libevent 2.0.19-stable
rtlinked against libevent 2.0.19-stable
1 CPU cores detected
proxyspecs:
[0.0.0.0]:8443 ssl plain netfilter Loaded CA: '/C=US/ST=aa/L=aa/O=aa/OU=ssl/CN=aaaaa.com/emailAddress=aaaa' Using libevent backend 'epoll' Event base supports: edge yes, O(1) yes, anyfd no Inserted events: 0x888e48 [fd 7] Read Persist 0x887a34 [fd 8] Read Persist 0x888d38 [fd 6] Read Persist 0x889a30 [fd 3] Signal Persist 0x889b50 [fd 1] Signal Persist 0x889be0 [fd 2] Signal Persist 0x889c70 [fd 13] Signal Persist Failed to start thread manager

But then if I go back to version 0.4.6-1 it starts fine....but then I get the segmentation fault when I try to connect to port 8443 with telnet.

Closing comment (2013-12-23T12:19:03Z): I'm closing this issue again since it is a (originally deliberate) duplicate of #10. Please add any new information about a failing thread manager initialisation to issue #10.
Repository: dstackai/dstack

Issue #2095: [Bug]: `regions` is missing from GCP backends docs
Created: 2024-12-13T16:51:33Z
Steps to reproduce
The option to specify regions is not present in the docs for the GCP backend (https://dstack.ai/docs/reference/server/config.yml/#_gcp).
Actual behaviour
It gets filled in automatically when adding a new GCP backend---this is copied from the dstack web console in the "Backend config" editor:
regions: [northamerica-northeast1, northamerica-northeast2, us-central1, us-east1,
  us-east4, us-east5, us-south1, us-west1, us-west2, us-west3, us-west4, southamerica-east1,
  southamerica-west1, europe-central2, europe-north1, europe-southwest1, europe-west1,
  europe-west2, europe-west3, europe-west4, europe-west6, europe-west8, europe-west9,
  asia-east1, asia-east2, asia-northeast1, asia-northeast2, asia-northeast3, asia-south1,
  asia-south2, asia-southeast1, asia-southeast2, me-west1, australia-southeast1, australia-southeast2]
Expected behaviour
Does this option to restrict the valid regions for the GCP backend actually exist in the YAML, and if so, can it be documented?
dstack version
0.18.29
Server logs
No response
Additional information
No response

Duplicate issue #950: [UX]: Do not specify `regions` while initializing the default configuration for `aws`, `gcp`, `azure`
Created: 2024-02-29T11:36:05Z
Currently, when the user runs dstack server without ~/.dstack/server/config and if the user has any default credentials for aws, gcp, azure, then dstack initializes the default configuration in ~/.dstack/server/config and specifies all supported regions.
Let's use None for regions when initializing the default configuration, meaning that if regions aren't specified, then all regions are configured.

Closing comment (2024-12-13T18:55:03Z): Seems related to: #2095
Repository: dstackai/dstack

Issue #886: Can't use spot instances if `AWSServiceRoleForEC2Spot` is not created in the AWS account
Created: 2024-02-10T18:11:36Z
To use spot instances with an AWS account, the account needs to have the corresponding service-linked role created (AWSServiceRoleForEC2Spot).  If this role is not created, AWS will throw the following error upon an attempt to run a spot instance:
WARNING 2024-02-08T17:42:46.589 dstack._internal.core.backends.aws.compute Got botocore.exceptions.ClientError: An error occurred (AuthFailure.ServiceLinkedRoleCreationNotPermitted) when calling the RunInstances operation: The provided credentials do not have permission to create the service-linked role for EC2 Spot Instances.

From the docs:

Under most circumstances, you don't need to manually create a service-linked role. Amazon EC2 creates the AWSServiceRoleForEC2Spot service-linked role the first time you request a Spot Instance using the console.

Solution
If the role isn't created (e.g. if the AWS account was created long time ago), the role has to be created manually by the following command:
aws iam create-service-linked-role --aws-service-name spot.amazonaws.com
Note, this is not dstack's issue. If a spot instance cannot be created because of the lack of this role, dstack treats this as spot instances not available.

Duplicate issue #1618: [Bug]: AWS policy permissions for Backend Configuration
Created: 2024-08-25T04:45:30Z
Steps to reproduce
I get this permission error when setting up my dev environment with the current permission policy on the documentation.
I think, it might be helpful to specify what type of access key should be created for the CLI to gain permissions in the docs.
[10:14:40] WARNING  dstack._internal.core.backends.aws.compute:202 Got botocore.exceptions.ClientError: An error occurred (AuthFailure.ServiceLinkedRoleCreationNotPermitted) when calling the RunInstances operation: The provided credentials do not have permission to create the service-linked role for EC2 Spot Instances. 
           WARNING  dstack._internal.server.background.tasks.process_submitted_jobs:371 job(150fc6)vscode-0-0: m5.large launch in aws/us-east-1 failed: NoCapacityError()                                                                                                       
[10:14:51] WARNING  dstack._internal.core.backends.aws.compute:202 Got botocore.exceptions.ClientError: An error occurred (AuthFailure.ServiceLinkedRoleCreationNotPermitted) when calling the RunInstances operation: The provided credentials do not have permission to create the service-linked role for EC2 Spot Instances. 

Actual behaviour
No response
Expected behaviour
No response
dstack version
0.18.10
Server logs
No response
Additional information
No response

Closing comment (2024-08-25T10:49:02Z): Duplicate of #886
Repository: dstackai/dstack

Issue #1603: Prevent broken links in `dstack` docs
Created: 2024-08-21T17:42:18Z
dstack docs often contain broken links that hurt the user experience. To prevent broken links, these measures are suggested:

 Build docs in strict mode (mkdocs build -s) so that pipelines fail if there are broken links
 Ensure they do actually fail on broken links (didn't fail here)
 Build docs in pull request pipelines (without publishing or with publishing to a staging environment) to prevent merging changes that break links
 In doc files, only use local links and avoid using full self-referencing URLs (https://dstack.ai/docs/...)
 See if building in strict mode fails when there are broken anchor links. If not, come up with a solution
 See if there are solutions to check external links when building

Duplicate issue #2100: [Bug]: Duplicate anchors in the server/config.yml reference
Created: 2024-12-16T07:14:16Z
Steps to reproduce

Go to https://dstack.ai/docs/reference/server/config.yml/
Use ToC to go to Azure regions.
You'll go to AWS regions since regions property of all backends has the same #regions anchor.

Actual behaviour
No response
Expected behaviour
No response
dstack version
master
Server logs
No response
Additional information
No response

Closing comment (2024-12-16T07:20:33Z): There are also a lot of missing anchors as reported by mkdocs when generating docs. Related to #1603
Repository: dstackai/dstack

Issue #2180: [Feature]: Zero-downtime in-place update for services
Created: 2025-01-09T15:06:20Z
Problem
Currently, when re-deploying a service (e.g., a newer version), dstack stops the existing run before submitting the new one. This causes a disruption, which is unacceptable for any production-grade service.
Solution

Introduce a revision number for service replicas.
During an in-place update, ensure that older replicas are only stopped once the newer replicas are successfully running.

Workaround
No response
Would you like to help us implement this feature by sending a PR?
Yes

Duplicate issue #2181: [Feature]: Allow to configure a service healthcheck
Created: 2025-01-09T15:13:54Z
Problem
When running a service, I currently have to manually check the endpoint repeatedly to determine if it’s ready to handle requests (e.g. the model is loaded) or if there are any health issues. This is particularly critical for production-grade services.
Solution

Add an option in the service configuration to define a URL that dstack can use to:
a) Verify the service is up and healthy.
b) Warm up the service.
If the service does not pass the health check within the configured timeout, mark it as unhealthy.

Workaround
No response
Would you like to help us implement this feature by sending a PR?
Yes

Closing comment (2025-01-09T15:14:08Z): Can be related to #2180
Repository: dstackai/dstack

Issue #2134: [Bug] Sometimes the log loading spinner remains shown even though logs are loaded already
Created: 2024-12-24T09:33:21Z
No clear to reproduce yet but you can see the result on the screenshots below:

Duplicate issue #2246: [Bug]: Server admin UI - Log display seems broken
Created: 2025-01-30T15:45:03Z
Steps to reproduce
Look at the details of a running or completed task that has some log data.
Actual behaviour
Accessing the server UI from Brave (Chromium), I'm having a couple issues w/ the display of my task's log data:

The text spills over the UI element
The text can't be copy/pasted
There's always a 'Loading' spinner near the top of the UI element, even after the task is complete.  It's possible this explains the first two items.

See attached.

Expected behaviour

Text is contained in the element
Text can be copy/pasted
No Loading spinner, at least once the task is complete

dstack version
0.18.37
Server logs

Additional information
No response

Closing comment (2025-01-30T16:16:37Z): @peterschmidt85, I think this happens with any configuration and any browser. I can reproduce it in Firefox.
The problem was already reported in #2134, but let's keep the current issue as it provides more details.
Repository: dstackai/dstack

Issue #1667: [UI] Revert the list of projects and users in Administration
Created: 2024-09-06T15:29:53Z
Currently, the list of projects and users show newer entries in the end. It's more convenient to see new entries at the beginning and older entries at the end.

Duplicate issue #1807: [Bug]: [UI] Project → Runs sort order
Created: 2024-10-09T16:22:59Z
Steps to reproduce

Use Firefox.
Make sure you have several runs in one project.
Check /runs page.

Actual behaviour
Runs are sorted by "Submitted" in ascending order while paginated in descending order

Expected behaviour
Runs are sorted by "Submitted" in descending order
dstack version
0.18.17
Server logs
No response
Additional information
/administration/runs works as expected.
This is probably due to a buggy sorting function:
https://github.com/dstackai/dstack/blob/0.18.17/frontend/src/pages/Runs/MainList/index.tsx#L127
As IRun.submitted_at is a ISO8601-formatted string, -i.submitted_at returns NaN.
/administration/runs doesn't sort data at all.

Closing comment (2024-10-10T06:23:59Z): Related/duplicate of: #1667 not related
Repository: dstackai/dstack

Issue #2067: [Feature]: Support smaller AWS CPU instances
Created: 2024-12-06T17:02:51Z
Problem
The smallest AWS CPU instance dstack supports is t2.small (1xCPU, 2GB RAM). Some workflows may benefit from cheaper instances with less RAM and a lower baseline burstable CPU performance.
Solution
Support instances from the t2, t3, and t3a families that are smaller than t2.small.
Supporting larger instances from these families is questionable, since dstack does not distinguish burstable instances, so the difference between low-performance (t2, t3) and higher-performance (c5, m5) instances won't be visible in the offers list.
Workaround
No response
Would you like to help us implement this feature by sending a PR?
Yes

Duplicate issue #2073: [Bug]: some smaller instance types can be provisioned only with `resources`, not with `instance_types`
Created: 2024-12-09T11:11:37Z
Steps to reproduce
Try to apply a configuration with the specification
instance_types:
  - t2.small
Actual behaviour
It doesn't work (no offers are shown)
Expected behaviour
It would work.  This seems like a bug because you can provision t2.small instances by removing the instance_types constraint and using
resources:
  memory: 2GB
  cpu: 1
dstack version
0.18.29
Server logs
No response
Additional information
No response

Closing comment (2024-12-13T07:16:48Z): @greaber, thanks for reporting. We'll look into it.
Possibly related to #2067.
Repository: dstackai/dstack

Issue #1664: [Feature]: Support `resources` with the `gateway` configuration type
Created: 2024-09-05T18:41:58Z
If I send too many requests, like 2000 per second, the gateway can't handle that. Also, I have 9 services running. We need to either run multiple gateways or at least be able to increase instance resources.
Proposal:
Allow to specify resources for the gateway configuration type –just like for runs (dev-environment, task, and service) configurations.

Duplicate issue #2409: [Bug]: Gateway Deployment Fails in AWS Region `eu-north-1` Due to Unsupported Configuration
Created: 2025-03-14T18:33:13Z
Steps to reproduce
When attempting to deploy a gateway using dstack in the AWS eu-north-1 region, the deployment fails with an error indicating that the requested configuration is not supported. Changing the region to eu-west-1 allows the deployment to succeed, yet the documentation does not mention that eu-north-1 is unsupported.
Steps to Reproduce:

Configure your deployment to use AWS region eu-north-1 in your deploy/gateway.dstack.yaml file.

type: gateway
name: custom-gateway

backend: aws
region: eu-north-1

domain: api.example.com

Run the command:

dstack apply -f deploy/gateway.dstack.yaml


Observe the failure with the error message.

Actual behaviour
The deployment fails with an error message:
 NAME          BACKEND           HOSTNAME  DOMAIN       DEFAULT  STATUS  CREATED  ERROR                                                                           
 custom-gateway  aws (eu-north-1)            api.example.com           failed  17:19    Unexpected error: ClientError('An error occurred (Unsupported) when calling the 
                                                                                  RunInstances operation: The requested configuration is currently not supported. 
                                                                                  Please check the documentation for supported configurations.')                  

  Unexpected error: ClientError('An error occurred (Unsupported) when calling the RunInstances operation: The requested configuration is currently not supported. Please check the documentation for supported configurations.')

Expected behaviour

The gateway should deploy successfully in the configured region if it is supported.
If eu-north-1 is not supported, the system should provide a clear error message or documentation update indicating the supported regions.
The documentation should clearly state what regions are supported if not all of them are supported.

dstack version
0.18.44
Server logs

Additional information
Changing the AWS region to eu-west-1 in the configuration file allows the deployment to complete without errors.

Closing comment (2025-03-17T08:31:32Z): @movchan74, thanks for reporting. This is because dstack provisions t2.micro instances for gateways on AWS and t2 appears to be not supported in many regions. For now, I suggest we switch to t3.micro since t3 is supported everywhere. Eventually, we'll need to supported configuring gateway instance_type (related to #1664).
Repository: ebean-orm/ebean

Issue #52: JPA2 - @OneToMany or @ManyToOne not supported inside @Embeddables
Created: 2013-10-23T15:00:59Z
I tried to migrate a system from Hibernate to Ebean and this was one of the biggest problem!.

Duplicate issue #1385: Failed to create EbeanServer with @Embeddable class that relation to another entity
Created: 2018-05-23T14:20:33Z
Expected behaviour
Ebean should be able to handle entity structure described in the example 2 of the @Embeddable annotation documentation.
Actual behaviour
EbeanServer instantiation fails with an error message Error reading annotations for embeddabletest.EmbeddableTest$PhoneNumber.
Steps to reproduce
Add classes to ServerConfig and call EbeanServerFactory.create().
public class EmbeddableTest {
    public static void main(String[] args) {
        ServerConfig config = new ServerConfig();
        config.loadFromProperties();
        config.addClass(PhoneServiceProvider.class);
        config.addClass(PhoneNumber.class);
        EbeanServerFactory.create(config);
    }

    @Embeddable
    public static class PhoneNumber {
        private String areaCode;
        private String localNumber;
        @ManyToOne private PhoneServiceProvider provider;
        // Getters and setters omitted
    }

    @Entity
    public static class PhoneServiceProvider {
        @Id private String name;
        // Getters and setters omitted
    }
}
Problem cause
When embeddable class is deployed by BeanDescriptionManager.readEntityDeploymentInitial() it tries to do lookup for BeanTable of PhoneServiceProvider.class in BeanDescriptorManager.beanTableMap. But, the map is populated after the lookup, by BeanDescriptorManager.readEntityBeanTable().
Here is the stack-trace of BeanTable lookup:

beanTable:193, AnnotationAssocOnes (io.ebeaninternal.server.deploy.parse) ⬅️ exception is thrown.
readManyToOne:204, AnnotationAssocOnes (io.ebeaninternal.server.deploy.parse)
readAssocOne:66, AnnotationAssocOnes (io.ebeaninternal.server.deploy.parse)
parse:57, AnnotationAssocOnes (io.ebeaninternal.server.deploy.parse)
readAssociations:49, ReadAnnotations (io.ebeaninternal.server.deploy.parse)
readDeployAssociations:1313, BeanDescriptorManager (io.ebeaninternal.server.deploy)
readEntityDeploymentInitial:719, BeanDescriptorManager (io.ebeaninternal.server.deploy)
deploy:364, BeanDescriptorManager (io.ebeaninternal.server.deploy) ⬅️ interesting method.
:163, InternalConfiguration (io.ebeaninternal.server.core)
createServer:139, DefaultContainer (io.ebeaninternal.server.core)
createServer:45, DefaultContainer (io.ebeaninternal.server.core)
createInternal:109, EbeanServerFactory (io.ebean)
create:70, EbeanServerFactory (io.ebean)
main:18, EmbeddableTest (embeddabletest)

Closing comment (2018-05-24T00:44:14Z): This is a duplicate of #52