primordic/IssueDupesLite huggingface dataset:
Repository: taiki-e/cargo-llvm-cov

Issue #233: `cargo llvm-cov nextest run` skips tests
Created: 2022-12-15T16:41:47Z
cargo-llvm-cov v0.5.3
Maybe I'm misunderstanding, but the tests are not skipped when running either cargo llvm-cov or cargo nextest run alone, so my expectations are the tests should not be skipped in this scenario.
Steps to reproduce:
cargo new foo
cd foo
echo '
#[cfg(test)]
mod test {
    #[test]
    fn test_foo() {
        assert_eq!(1 + 1, 2);
    }
}' >> src/main.rs
cargo llvm-cov nextest run

Duplicate issue #260: Nextest is not being run recursively
Created: 2023-04-21T12:15:42Z
I tried using cargo llvm-cov nextest run on https://github.com/MaterializeInc/materialize/, but only the top-level tests seem to be run:
    Starting 17 tests across 102 binaries (523 skipped)

Meanwhile cargo nextest run is correctly traversing all the recursive Cargo.toml files and running the tests in them too:
    Starting 537 tests across 102 binaries (3 skipped)

Is this expected or am I missing something?

Closing comment (2023-04-21T12:30:31Z): Duplicate of #233.
Repository: tbruyelle/RxPermissions

Issue #310: how to support kotlin
Created: 2020-01-03T13:20:10Z
hey,my project use kotlin when I use this,it do not work well

Duplicate issue #311: how to support kotlin
Created: 2020-01-03T13:20:18Z
hey,my project use kotlin when I use this,it do not work well

Closing comment (2020-01-21T09:57:22Z): Duplicate of  #310 =\
Repository: tbruyelle/RxPermissions

Issue #261:  When the Android version is greater than 6.0, and the targetsdkversion is less than 23, the application permission will always return true regardless of whether or not the permission is granted. How to solve it?
Created: 2018-11-01T02:28:00Z

Duplicate issue #260: 在安卓版本大于6.0，而targetsdkversion小于23时，无论有没有授予权限都会出现申请权限一直返回true的问题，请问怎么解决
Created: 2018-11-01T02:25:46Z

Closing comment (2018-11-13T13:38:03Z): duplicate of #261 and it should be closed @tbruyelle
Repository: tbruyelle/RxPermissions

Issue #257: Hello, I have a problem, please help me to solve it
Created: 2018-10-22T09:57:33Z
This library comes with RxJava2 can you import RxJava2 yourself?Remove the library itself?

Duplicate issue #256: hello，You don't have to bring it RxJAVA
Created: 2018-10-22T09:53:45Z
This library comes with RxJava2 can you import RxJava2 yourself?Remove the library itself?

Closing comment (2018-11-13T13:43:59Z): @tbruyelle  this is another duplicate of #257 and it should be deleted.
@317056658 please do not add duplicate issues. That will just make maintainer jobs more difficult and solution will come later, if ever. Thanks
Repository: tbruyelle/RxPermissions

Issue #142: In XiaoMi5 ,Android 7.0,Rxpermission0.9.4 always return true
Created: 2017-04-25T06:15:01Z
As the title said,whenever I turn off the permission ,it always return true
Here's my code.
RxPermissions rxPermissions = new RxPermissions(this); rxPermissions.request(Manifest.permission.READ_CONTACTS) .subscribe(new Action1<Boolean>() { @Override public void call(Boolean aBoolean) { Log.d("permission", "--" + aBoolean); } });

Duplicate issue #171: xiaomi6(MiUI) mobile phone permission
Created: 2017-08-29T06:55:20Z
I request permission in onResume()，then I reject the pemission。Then onResume() and onPause() start an infinite loop.
This is my code:
@OverRide
protected void onResume() {
super.onResume();
LogUtil.error(getClass(), "onResume");
String[] permissions = {
Manifest.permission.WRITE_EXTERNAL_STORAGE,
Manifest.permission.READ_EXTERNAL_STORAGE};
RxPermissionsUtil.getRxPermissions(this).request(permissions).subscribe(new BaseObserver() {
@OverRide
public void onNext(Boolean value) {
}
});
}
@Override
protected void onPause() {
    super.onPause();
    LogUtil.error(getClass(), "onPause");
}

Closing comment (2017-09-02T17:50:46Z): Dup of #142
Repository: tbruyelle/RxPermissions

Issue #214: FragmentManager is already executing transactions
Created: 2018-03-12T22:40:34Z
Caused by: java.lang.IllegalStateException: FragmentManager is already executing transactions
                                                                                     at android.app.FragmentManagerImpl.ensureExecReady(FragmentManager.java:1981)
                                                                                     at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:2037)
                                                                                     at android.app.FragmentManagerImpl.executePendingTransactions(FragmentManager.java:799)
                                                                                     at com.tbruyelle.rxpermissions2.RxPermissions.getRxPermissionsFragment(RxPermissions.java:54)
                                                                                     at com.tbruyelle.rxpermissions2.RxPermissions.<init>(RxPermissions.java:41)
                                                                                     at com......MessagesActivity.initViews(MessagesActivity.java:113)

in this code :
   rxPermissions = new RxPermissions(this);
I don't know exactly the reason behind this as it was working before without any issue.

Duplicate issue #235: IllegalStateException: FragmentManager is already executing transactions
Created: 2018-07-10T08:50:37Z
I'm targeting API 27 and using the 0.10.1 version of the library but I receive this crash when I check the permissions onCreateView of a fragment I just added. Is there any workaround @epool ?
java.lang.IllegalStateException: FragmentManager is already executing transactions at android.support.v4.app.FragmentManagerImpl.ensureExecReady(FragmentManager.java:2179) at android.support.v4.app.FragmentManagerImpl.execSingleAction(FragmentManager.java:2211) at android.support.v4.app.BackStackRecord.commitNow(BackStackRecord.java:643) at com.tbruyelle.rxpermissions2.RxPermissions.getRxPermissionsFragment(RxPermissions.java:71) at com.tbruyelle.rxpermissions2.RxPermissions.access$000(RxPermissions.java:34) at com.tbruyelle.rxpermissions2.RxPermissions$1.get(RxPermissions.java:54) at com.tbruyelle.rxpermissions2.RxPermissions$1.get(RxPermissions.java:47) at com.tbruyelle.rxpermissions2.RxPermissions.isGranted(RxPermissions.java:302)

Closing comment (2018-07-10T15:59:44Z): duplicate of #214
Repository: tbruyelle/RxPermissions

Issue #142: In XiaoMi5 ,Android 7.0,Rxpermission0.9.4 always return true
Created: 2017-04-25T06:15:01Z
As the title said,whenever I turn off the permission ,it always return true
Here's my code.
RxPermissions rxPermissions = new RxPermissions(this); rxPermissions.request(Manifest.permission.READ_CONTACTS) .subscribe(new Action1<Boolean>() { @Override public void call(Boolean aBoolean) { Log.d("permission", "--" + aBoolean); } });

Duplicate issue #123: xiaomi(MiUI) mobile phone permission
Created: 2017-02-14T08:25:37Z
In a xiaomi(MiUI) mobile phone
we may need use both appOpsManager.checkOp and ActivityCompat.checkSelfPermission to check if the permission is granted;
like this
@TargetApi(Build.VERSION_CODES.M)
private static boolean hasSelfPermissionForXiaomi(Context context, String permission) {
  AppOpsManager appOpsManager = (AppOpsManager) context.getSystemService(Context.APP_OPS_SERVICE);
  int checkOp = appOpsManager.checkOp(AppOpsManager.permissionToOp(permission), Process.myUid(), context.getPackageName());
  return checkOp == AppOpsManager.MODE_ALLOWED && ActivityCompat.checkSelfPermission(context, permission) == PackageManager.PERMISSION_GRANTED;
}

ref:https://github.com/hotchemi/PermissionsDispatcher/blob/7189a29a831e48d4d6c6b3d0d413d39486ed58b6/library/src/main/android/permissions/dispatcher/PermissionUtils.java

Closing comment (2017-09-02T17:50:26Z): Dup of #142
Repository: tbruyelle/RxPermissions

Issue #45: Is there some Proguard rules to follow ?
Created: 2016-04-19T14:09:07Z
If yes, that would be good to put in the Readme.

Duplicate issue #148: This library no has rules for proguard
Created: 2017-05-29T05:06:09Z
This library has no rules for proguard

Closing comment (2017-06-15T12:53:15Z): Duplicate of #45
Add this to your file :
-dontwarn com.tbruyelle.rxpermissions.**
Repository: tbruyelle/RxPermissions

Issue #46: java.lang.IllegalStateException: RxPermissions.onRequestPermissionsResult invoked but didn't find the corresponding permission request.
Created: 2016-05-10T15:05:48Z
One of my activities asks for camera permission on trigger (button click)
After following steps, exception is thrown:

user presses button and shadow activity with dialog that asks for permission is shown
user goes to settings and revoke some other permission
user reopens app - shadow activity with dialog is still there
user allows/denies permission and app crashes with exception

from what I saw in code:
RxPermissions.request_() where mSubjects is filled is called before permission is revoked by user
After user revoked permission app is recreated in new process and mSubjects is empty - therefore exception is thrown in RxPermissions.onRequestPermissionsResult()
Can you please fix this or suggest a workaround?

Duplicate issue #82: is it a bug？
Created: 2016-10-08T09:00:07Z
RxPermissions.onRequestPermissionsResult invoked but didn't find the corresponding permission request

Closing comment (2016-10-15T17:10:15Z): Possible duplicate of #46
Repository: tbruyelle/RxPermissions

Issue #263: Android Jetpack
Created: 2018-11-05T12:24:26Z
Hi, i can not create RxPermissions(fragment) because Fragment is from androidx.fragment.app package. Is there any workaround ?

Duplicate issue #270: RxPermissions don't support AndroidX
Created: 2018-11-16T07:53:33Z
When initializing objects ，
rxPermissions = new RxPermissions( (FragmentActivity)this);
FragmentActivity.class is android.support.v4.app.FragmentActivity;
but AndroidX FragmentActivity.class is package androidx.fragment.app
Cause can not Cast

Closing comment (2018-12-28T10:40:50Z): This looks like a duplicate of #263.

I think it works even IDE shows error. Because i have
android.useAndroidX=true
android.enableJetifier=true

in gradle.properties

Enable jetifier which will convert all dependencies that use the old support library (including RxPermissions) to using AndroidX instead.
https://developer.android.com/jetpack/androidx/migrate

But there are errors warning on compile time. How can u run success?
Repository: tc39/ecma262

Issue #2903: GetIterator should check for `next` being a method
Created: 2022-09-10T19:15:48Z
The GetIterator abstract operation sometimes does return a broken iterator, in particular one where the [[NextMethod]] is not a function object. It seems that this goes against the spirit of #976 (#988/#1021) and #2591: not only should the .next method be accessed only once, it should also need to be checked for being a method only once. If an Iterator Record is produced, it should be a working iterator, where [[NextMethod]] has a "function object" value.
There would only be a minimal observable change (but still making this normative and requiring consensus). As far as I can tell from the spec, and as previously suggested by @devsnek, the only thing that would have different observable behaviour is array destructuring. Every single other usage of GetIterator in the spec is immediately followed by an IteratorStep, which attempts to call the [[NextMethod]] and throws an exception then. In particular:
const [] = {
  [Symbol.iterator]: () => ({
    next: undefined, // or some other non-callable value, or no property at all
    return(){ console.log("done"); return {done: true}; },
  }),
};
// now: logs "done", without checking `.next`
// then: throws error

function getObj() { console.log("side effect"); return {}; }
[getObj().prop] = {
  [Symbol.iterator]: () => ({}),
};
// now: logs "side effect" before throwing a TypeError
// then: throws the TypeError immediately
This would make tc39/proposal-iterator-helpers#232 PR superfluous, and it would lead to more consistent behaviour (early failure) since that's also what the iterator helper methods from the proposal will do (e.g. const [] = Object.create(Iterator.prototype).take(0); will throw during the take call).
If this behaviour were not to be changed, the table that defines the shapes of the Iterator Records needs an editorial change to say "unknown" instead of "function object".

Duplicate issue #3033: Iterator Record `[[NextMethod]]` type incorrect
Created: 2023-03-30T01:16:27Z
The type of the [[NextMethod]] field of Iterator Records is declared to be "a function object", but in GetIterator, ForIn/OfHeadEvaluation, and CreateAsyncFromSyncIterator, we stick the result of Get(iterator, "next") directly into there without validating it. We should either update the type or check/throw before constructing the Iterator Record (this seems to require impossible normative changes).

Closing comment (2023-04-04T02:02:11Z): The proposed normative change is a duplicate of #2903 and being considered at the next plenary.
Repository: tc39/ecma262

Issue #325: "but not one of" is rendered as "one of" in RegExp patterns
Created: 2016-01-26T18:21:56Z
For example, the checked-in version of the ClassAtomNoDash RegExp grammar in Section 21.2.1 says:
ClassAtomNoDash[U] ::
  SourceCharacter but not one of `\` or `]` or `-`
  `\` ClassEscape[?U]

However, the rendered version removes but not after SourceCharacter and shows it as:
ClassAtomNoDash[U] ::
  SourceCharacter one of `\` or `]` or `-`
  `\` ClassEscape[?U]

Duplicate issue #358: Transcription issue in 12.1 identifier definition
Created: 2016-02-04T13:24:54Z
We seem to have lost the words "but not" in the ecmarkup for Identifier
http://tc39.github.io/ecma262/#sec-identifiers
http://www.ecma-international.org/ecma-262/6.0/#sec-identifiers
In the 2015 version, there's "IdentifierName but not ReservedWord", but in 2016, "IdentifierName ReservedWord". Thanks to @nickie for pointing this out
@bterlson

Closing comment (2016-02-04T20:09:54Z): Related to #325?
Repository: tc39/ecma262

Issue #2371: "concrete method" is a weird term
Created: 2021-04-05T02:03:17Z
In IRC, @jmdyck points out that the term "concrete method", which we use for Environment Records and Module Records, is a little misleading in the context of the rest of the spec: it implies these are somehow more concrete than abstract operations. In fact, here these are "concrete" in the sense of "not abstract" where "abstract" has the meaning it does in OOP, rather than being at all related to the specification's "abstract operations".
Perhaps it's worth renaming these. For example, "Record method" is a little more descriptive.

Duplicate issue #2458: "concrete method" needs a definition
Created: 2021-07-15T15:41:40Z
Spec text includes many examples of "concrete method", but does not include a definition of that term.

Closing comment (2021-07-15T16:05:29Z): Duplicate of #2371?
Repository: tc39/ecma262

Issue #814: GetFunctionRealm argument
Created: 2017-02-11T05:35:56Z
The abstract operation GetFunctionRealm(_obj_) asserts that _obj_ is a callable object. However, consider the steps later in the definition:
  1. Let _proxyTarget_ be _obj_.[[ProxyTarget]].
  1. Return ? GetFunctionRealm(_proxyTarget_).

I don't think there's a guarantee that _obj_.[[ProxyTarget]] is callable, in which case the recursive call would fail the assertion.

Duplicate issue #1565: question re proxy handler "apply" method
Created: 2019-06-01T04:11:43Z
Consider a proxy object whose handler has an "apply" method and whose target is not a function object.
It looks like, because target isn't callable, ProxyCreate would have created the proxy object without a [[Call]] internal method, so the proxy object isn't callable, even though there's that "apply" method that could service a call.
So if you want the handler's "apply" method to be invoked, you have to create the proxy with a target that's a function, even though the latter won't be called?

Closing comment (2019-06-01T04:35:03Z): related to #814
Yes, i believe that is the case.
cc @erights and @tvcutsem for background.
Repository: tc39/ecma262

Issue #137: Annex B: Specify non-standard RegExp static properties
Created: 2015-10-28T14:08:56Z
Update: Link to proposal: https://github.com/tc39/proposal-regexp-legacy-features

All web browsers expose non-standard properties on the RegExp constructor, that are updated each time a match is done.
The list of properties that are exposed by all common browsers are the following. They typically expose other properties not mentioned here, but not shared by all implementations:
$1, $2, $3, $4, $5, $6, $7, $8, $9,

and (in pairs, where the first and the second one return the same value):
input, $_
lastMatch, $&
lastParen, $+
leftContext, $`
rightContext, $'

Some observations:

their value is always a string;
some implementations expose them as data properties, others as accessor properties;
those properties are non-enumerable;
they cannot be deleted or modified manually.

It would be useful to specify them. I think that the following should be required:

Those properties should be accessors. That would be more honest about the changing nature of their value;
They should be deletable. Indeed, they represent global communication channels that may be unwanted in some environments;
It should be specified when they are updated, presumably sometime during the execution of the builtin RegExp#exec method. This is useful if we want, in some future, separate the part of RegExp#exec that does the real work, and the part that does stateful updates on various objects.

Duplicate issue #665: Legacy RegExp features in JavaScript
Created: 2016-08-12T11:56:42Z
https://github.com/claudepache/es-regexp-legacy-static-properties by @claudepache
Please don’t tag this issue with the “web reality” label, as it’s a duplicate of #137. Thanks!

Closing comment (2016-08-12T12:02:57Z): Dupe of #137
Repository: tc39/ecma262

Issue #529: Is "NewTarget" defined anywhere? If so, can we get a <dfn>?
Created: 2016-04-08T04:52:28Z
I've always found the "NewTarget" notation confusing. (And especially, it's unclear to me when to use that versus GetNewTarget(). It seems like only syntax parts of the spec use the latter?) As far as I can tell it's a floating undefined ambient thing that all abstract operations have access to?
It would be great to give it a <dfn> and thus create autolinks to something defining this notation.
As an example of what I'm talking about, see basically every constructor in the spec, e.g. https://tc39.github.io/ecma262/#sec-symbol-description.

Duplicate issue #540: Consider cross-referencing NewTarget
Created: 2016-04-13T13:18:48Z
It's somewhat hard to find the definition if you're jumping directly into a function definition.

Closing comment (2016-04-13T14:06:34Z): dupe of #529
Repository: tc39/ecma262

Issue #1257: Editorial: Suspend execution context in many places is mislinked
Created: 2018-07-09T21:41:17Z
In many places in the spec, like

https://tc39.github.io/ecma262/#await-fulfilled
https://tc39.github.io/ecma262/#sec-runjobs

an execution context is suspended. However, a link to the Suspend abstract operation is generated, which doesn't seem to be the intended meaning in most of these places, which mean the concept defined in https://tc39.github.io/ecma262/#sec-execution-contexts.

Duplicate issue #2168: GeneratorResume mistakenly links the Suspend AO
Created: 2020-09-09T21:26:42Z
https://tc39.es/ecma262/#sec-generatorresume shouldn't be autolinking to Suspend.
Should rename Suspend to something else.

Closing comment (2020-09-09T21:46:33Z): Looks like a duplicate of #1257.
Repository: tchiotludo/akhq

Issue #1181: Error at runtime: Scala module 2.12.4 requires Jackson Databind version >= 2.12.0 and < 2.13.0
Created: 2022-08-24T14:00:04Z
I opened the source in Interllij, started App, project appears to run but the moment I try to access port 8080 I get this error:
2022-08-24 15:54:52,767 ERROR r-thread-1 i.m.h.server.RouteExecutor Unexpected error occurred: Error instantiating bean of type  [io.micronaut.jackson.databind.JacksonDatabindMapper]

Message: Scala module 2.12.4 requires Jackson Databind version >= 2.12.0 and < 2.13.0
Path Taken: new JsonBeanPropertyBinder(JsonMapper jsonMapper,JsonConfiguration configuration,BeanProvider exceptionHandlers) --> new JsonBeanPropertyBinder([JsonMapper jsonMapper],JsonConfiguration configuration,BeanProvider exceptionHandlers) --> new JacksonDatabindMapper([ObjectMapper objectMapper])
io.micronaut.context.exceptions.BeanInstantiationException: Error instantiating bean of type  [io.micronaut.jackson.databind.JacksonDatabindMapper]

I checked both the dev branch and the latest label 0.21.0 with the same result.

Duplicate issue #1181: Error at runtime: Scala module 2.12.4 requires Jackson Databind version >= 2.12.0 and < 2.13.0
Created: 2022-08-24T14:00:04Z
I opened the source in Interllij, started App, project appears to run but the moment I try to access port 8080 I get this error:
2022-08-24 15:54:52,767 ERROR r-thread-1 i.m.h.server.RouteExecutor Unexpected error occurred: Error instantiating bean of type  [io.micronaut.jackson.databind.JacksonDatabindMapper]

Message: Scala module 2.12.4 requires Jackson Databind version >= 2.12.0 and < 2.13.0
Path Taken: new JsonBeanPropertyBinder(JsonMapper jsonMapper,JsonConfiguration configuration,BeanProvider exceptionHandlers) --> new JsonBeanPropertyBinder([JsonMapper jsonMapper],JsonConfiguration configuration,BeanProvider exceptionHandlers) --> new JacksonDatabindMapper([ObjectMapper objectMapper])
io.micronaut.context.exceptions.BeanInstantiationException: Error instantiating bean of type  [io.micronaut.jackson.databind.JacksonDatabindMapper]

I checked both the dev branch and the latest label 0.21.0 with the same result.

Closing comment (2022-08-25T19:24:06Z): duplicate #1181
Repository: tchiotludo/akhq

Issue #1939: List topic messages is extreamly slow after upgrading from 0.25.0 to 0.25.1
Created: 2024-09-12T15:58:29Z
Hello
As a follow up of this conversation #1880, I'm raising this issue because I couldn't find any issue related to my problem.
Since upgrade to 0.25.1, this API became very slow. The topic I'm listing the content is empty.
2024-09-12 14:27:22,946 INFO io-executor-thread-6 org.akhq.log.access [Date: 2024-09-12T14:25:21.823535418Z] [Duration: 121123 ms] [Url: GET /api/dev/topic/facture.hospi.create/data] [Status: 200]
Same with 0.25.0 : Still the same empty topic.
2024-09-12 15:45:15,605 INFO io-executor-thread-13 org.akhq.log.access [Date: 2024-09-12T15:45:14.191436025Z] [Duration: 1415 ms] [Url: GET /api/dev/topic/facture.hospi.create/data] [Status: 200]

Duplicate issue #2056: Very slow topic search by value in the thread after upgrading from version 0.24.0 to 0.25.1
Created: 2025-01-29T13:36:18Z
Good afternoon, could you please advise what can be done?
After upgrading from version 0.24.0 to 0.25.1, the search in the UI has become very slow (related to visual rendering). We often lack sufficient information to add additional parameters to speed up the search.
For example, a searchByValue query that took ~10 seconds in version 0.24.0 (with ~800k topics in the thread) now takes 40 seconds in version 0.25.1. Setting a Timestamp parameter speeds up the search significantly, but this is not always convenient for us.
Has anyone encountered this issue and found a solution? The same problem occurs in version 0.25.0 and on the dev branch.
We tried reducing topic-data values, but it did not help.
Is there a parameter that can set the timestamp to a specific range, for example, a week or 5 days?

Closing comment (2025-03-10T07:59:59Z): Closing as duplicate of #1939
PR in progress
Repository: tchiotludo/akhq

Issue #77: Feature: support partition reassignment
Created: 2019-06-05T04:03:26Z
The only feature still missing to completely replace https://github.com/yahoo/kafka-manager  with KafkaHQ would be to have the ability to manage partition reassignment between brokers.

do you plan to add this feature in kafkaHQ?
thanks again for your great tool!

Duplicate issue #1410: Topic Rebalance feature reqeust
Created: 2023-03-10T22:50:54Z
I'm wondering if you can add a feature to rebalance topics. both manual option and a scheduled task.

Closing comment (2023-03-12T22:01:31Z): duplicate of #77
Repository: tchiotludo/akhq

Issue #1939: List topic messages is extreamly slow after upgrading from 0.25.0 to 0.25.1
Created: 2024-09-12T15:58:29Z
Hello
As a follow up of this conversation #1880, I'm raising this issue because I couldn't find any issue related to my problem.
Since upgrade to 0.25.1, this API became very slow. The topic I'm listing the content is empty.
2024-09-12 14:27:22,946 INFO io-executor-thread-6 org.akhq.log.access [Date: 2024-09-12T14:25:21.823535418Z] [Duration: 121123 ms] [Url: GET /api/dev/topic/facture.hospi.create/data] [Status: 200]
Same with 0.25.0 : Still the same empty topic.
2024-09-12 15:45:15,605 INFO io-executor-thread-13 org.akhq.log.access [Date: 2024-09-12T15:45:14.191436025Z] [Duration: 1415 ms] [Url: GET /api/dev/topic/facture.hospi.create/data] [Status: 200]

Duplicate issue #2093: Slow loading of data when empty partition
Created: 2025-03-04T21:31:55Z
Hello,
I noticed since the poll-timeout got bigger.
Our dev environment got really slow when fetching data.
The pattern is always the same, more partitions empty = more loading time.
I searched into the source code and it seems the loop on partitions is waiting poll-timeout x partition empty.
Here is an example of a topic with one message and 5 partitions (10s x 4 + fetchmessagetime):

You can also spot this in the gradle tests, in local some tests are waiting 10s to complete.
I don't think lowering the timeout will resolve anything, but skipping empty partition might do the trick.
@AlexisSouquiere Can you assign this issue to me if you don't see any objection ?
I think, I can fix it without too much effort.
Thank you.

Closing comment (2025-03-05T11:04:26Z): You are right, this is a duplicate of #1939.
I will continue the conversation on the PR and test but I think there is a subtlety when partitions are empty, the phrasing looks ambigious in the javadoc.
Repository: tchiotludo/akhq

Issue #914: Read timeout by micronaut client on configured enpoint
Created: 2021-11-19T13:36:07Z
I have configured the auth authentification along side with the call to a rest endpoint for permissions. Regularly the micronaut http clients runs into a time out as such:
2021-11-19 13:13:51,320 ERROR pGroup-1-7 .m.r.i.RecoveryInterceptor Type [org.akhq.utils.RestApiClaimProvider$Intercepted] executed with error: Read Timeout
io.micronaut.http.client.exceptions.ReadTimeoutException: Read Timeout
	at io.micronaut.http.client.exceptions.ReadTimeoutException.<clinit>(ReadTimeoutException.java:26)
	at io.micronaut.http.client.netty.DefaultHttpClient.lambda$null$36(DefaultHttpClient.java:1178)
	at io.reactivex.internal.operators.flowable.FlowableOnErrorNext$OnErrorNextSubscriber.onError(FlowableOnErrorNext.java:103)
	at io.micronaut.reactive.rxjava2.RxInstrumentedSubscriber.onError(RxInstrumentedSubscriber.java:66)
	at io.reactivex.internal.operators.flowable.FlowableTimeoutTimed$TimeoutSubscriber.onTimeout(FlowableTimeoutTimed.java:139)
	at io.reactivex.internal.operators.flowable.FlowableTimeoutTimed$TimeoutTask.run(FlowableTimeoutTimed.java:170)
	at io.reactivex.internal.schedulers.ScheduledRunnable.run(ScheduledRunnable.java:66)
	at io.reactivex.internal.schedulers.ScheduledRunnable.call(ScheduledRunnable.java:57)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)

which seems to mean that the rest client takes more than 10 sec to answer. On the rest server side we have Datadog APM configured and we see that all calls are being processed in a few ms, which makes me wonder if the issue could be in akhq. I have read somewhere that micronaut http client uses the main thread which can potentially conflict with akhq operations.

Duplicate issue #1148: BUG: Error instantiating bean of type  [io.micronaut.security.oauth2.client.DefaultOpenIdProviderMetadata
Created: 2022-07-12T11:58:25Z
Hi all,
I've configured authN using oauth2/oidc.
Time to time I've started catch an exception like this:
io.micronaut.context.exceptions.BeanInstantiationException: Error instantiating bean of type  [io.micronaut.security.oauth2.client.DefaultOpenIdProviderMetadata]\n\nMessage: Read Timeout\nPath Taken: DefaultOpenIdProviderMetadata.openIdConfiguration(OauthClientConfiguration oauthClientConfiguration,OpenIdClientConfiguration openIdClientConfiguration,HttpClient issuerClient
I noticed this problem on all versions of akhq.

Closing comment (2022-07-26T20:15:59Z): duplicate #914
Repository: tchiotludo/akhq

Issue #505: Connect connector configuration shows passwords in clear text
Created: 2020-11-11T16:04:11Z
Is it possible to make a modification so that passwords for Connectors are masked in the web interface?
I understand this is a bit tricky since connectors can be custom and there is not really any control over what could be added, but at least for the standard and more common ones I wonder if something could be done to detect these and mask them on the web UI?
For example the Confluent JdbcSinkConnector and JdbcSourceConnector both have the property connection.password and if someone is using Akhq just to view the connectors and maybe restart tasks, it is not so good if they can see what the password to the database is for this user.
Is it possible to identify what properties are of type password, either by a type, a list of known password property names, or a combination of the Connector type and property name?
And then at a minimum just mask the display on both the overview page and the detail configs page:

Duplicate issue #1116: Hidden Credentials for Kafka Connectors
Created: 2022-06-09T14:08:33Z
Hi,
We have working with AKHQ several months and we are very happy with the application, it´s fantastic!!
As we are using it every, we have been findind several little things to improve. Now, we are working with Kafka-Connect and creating multiples connector for differents purposes. When you access to connector configuration, you can see the passwords are displayed in plain text. We have vision reader over all the AKHQ to developers and it would be interesting that these credentials are not seen and are encrypted, for example: *************
Attached an image of what we have in mind that would be interesting to consult:

Thank you so much.
Javier Torres

Closing comment (2022-06-20T19:44:02Z): duplicate #505
Repository: tchiotludo/akhq

Issue #1795: Error displaying schemas in topics with different names [0.25.0]
Created: 2024-05-27T13:51:40Z
Hi,
today we have upgraded to AKHQ 25.0.
Seems we are having trouble when clicking on the schema ID of a message when the schema has a different name than the topic. Nothing happens. For other schemas it works fine.
Note that in the 'Schema Registry' tab we can still view the schemas without problems.
Do you know what could be causing this?

Duplicate issue #1846: [v 0.25] Produce to topic - select 'value schema' issue
Created: 2024-06-26T14:58:36Z
When selecting a topic and then trying to produce to it, I can only see and select schemas that have the suffix -value in the dropdown menu from value schema.
With the same setup, I was able to select from all available schemas when producing to a topic in the GUI in 0.24.
Yes, I have adapted the new group/roles layout from 0.24->0.25 - everything else works just fine.
I am also able to see all schemas in the Schema Registry overview, with 0.24 and with 0.25.

Closing comment (2024-06-27T05:58:25Z): Duplicate of #1795
Repository: tdryer/hangups

Issue #24: Pass messages to running client to send.
Created: 2014-10-07T04:05:31Z
It would be ideal if hangups would run as a daemon and accept rpc calls
Eg. ./hangouts-rpc –send-message “testing” email@email.com

Duplicate issue #118: Sending Message with command
Created: 2015-05-06T17:51:41Z
I would like send message direct with a command from the shell.
Its useful for example important Server logs.
Maybe like this:
hangups -t [the channel number] -m [message]
Is this possible?

Closing comment (2015-05-07T04:03:04Z): Duplicate of #24.
Repository: tdryer/hangups

Issue #97: [Feature Request] Load older conversations when you navigate to the bottom of the conversation list
Created: 2015-04-10T12:39:48Z
At the moment, 35 conversations are loaded into the list on startup (this is limited by the backend, I guess, since it is the same number on mail.google.com or g+). It would be nice to be able to load older conversations, too. At the moment, a workaround is to open the conversation on another client and restart hangups or ask the opposite site to write a message to yourself.

Duplicate issue #102: ConversationList is incomplete
Created: 2015-04-15T08:51:29Z
The ConversationList may be incomplete if the conversation list is too long. The get() method may throw KeyError even if the conversation is valid.
If I want to get the conversation name of an off-list conversation, I have to

Try to get it from ConversationList, catch the KeyError Exception
Call client.getconversation to retrieve the conversation from server
Add the ClientConverstaion to the list manually.

Is it possible to hook the step 3 to getconverstaion to simply this?

Closing comment (2015-04-16T03:26:39Z): Duplicate of #97.
Repository: tdryer/hangups

Issue #4: Hangups fails to find all contact names
Created: 2014-05-21T17:55:46Z
I get KeyError in on_connect() method in __main__.py when hangups tries to get user names for user_ids in conversations:
first_names = [contacts[user_ids]['first_name']
                        for user_ids in
                        conversations[conv_id]['participants']]

It works if I change it to:
first_names = [contacts[user_ids]['first_name'] if user_ids in contacts else "UNKNOWN"
                        for user_ids in
                        conversations[conv_id]['participants']]

But then I have a lot of UNKNOWN user names in list of conversations.

Duplicate issue #47: "Unknown" user name in converstaion
Created: 2014-12-18T06:19:25Z
I have got some "Unknown" user in hangups reference client.
client_conversation.participant_data contains  namespace(fallback_name=None, id_=namespace(chat_id='(ID)', gaia_id='(ID)')), note the fallback_name is None
``WARNING - Adding fallback User` Message were found.
I have tried gmail under fiddler, the contact name can be loaded using /chat/v1/contacts/getentitybyid.
If you need more information, please tell me how to gather them.
Thanks

Closing comment (2014-12-18T19:03:05Z): Duplicate of #4.
Repository: tdryer/hangups

Issue #270: Google prompt auth not working
Created: 2016-10-06T16:32:13Z
I'm using the google prompt for authentication, and hangups fails with error Login failed (Unknown verification code input) after entering email/password.
I get the prompt on my phone, but hangups exits before I can validate it.
If I disable the google prompt on my account, it works as expected.

Duplicate issue #338: Login does not work with new yes/no google auth
Created: 2017-06-26T09:53:56Z
Google has introduced a login method where instead of a verification code, you get to hit yes (authorize) or no (do not authorize) on your phone. See example of error below
$ hangups
Sign in with your Google account:
Email: aurelien.ooms@gmail.com
Password: 

Login failed (Unknown verification code input)

Closing comment (2017-06-27T02:01:20Z): Duplicate of #270.
Repository: tdryer/hangups

Issue #44: Allow creating new conversations
Created: 2014-12-14T22:57:28Z
I'm writing a plugin for an IM client using hangouts (https://github.com/davidedmundson/telepathy-hangups)
I have a lovely list of users from userlist, generated from entitites; what I seem to be missing is any call to create a new conversation with one of these contacts.

Duplicate issue #291: I don't see a way to initiate a new conversation in the text UI
Created: 2017-01-05T23:19:24Z
When I start the hangups text UI, it shows all of the conversations I have opened, but it does not seem to have a way to open a new conversation.
Am I missing something or does this functionality not exist?

Closing comment (2017-01-06T03:58:01Z): It's not implemented in the UI.
Duplicate of #44.
Repository: tdryer/hangups

Issue #114: Message parser doesn't check for closing token
Created: 2015-04-28T04:59:48Z
The following are italicized by the message parser when they shouldn't be:
*foo

<i>foo

@xmikos

Duplicate issue #375: send_message changes 2 underscore to 1 underscore
Created: 2017-12-27T09:04:34Z
Using send_message , for some reason if i send a message that contains 2 concatenated underscore it replaces them with one underscore i.e :

Sending the string "a__b" will send the string "a_b"
2)Sending the string "b__" will send the string "b"

But sending the string "a__" will send the same string

Closing comment (2017-12-30T01:49:40Z): The message formatting parser has some issues. I'm going to call this a duplicate of #114.
Repository: tdryer/hangups

Issue #139: Long URL's have a hard newline inserted, making them not copy-pastable or clickable
Created: 2015-07-07T18:00:59Z
Write a long URL into a chat (longer than terminal width) to reproduce.

Duplicate issue #278: Long links (shorten?)
Created: 2016-11-25T22:35:21Z
Would there be a way to have links shorten so that they do not span multiple lines? This causes issues with opening them as it only opens a partial link.

Closing comment (2016-12-02T19:50:54Z): Duplicate of #139.
Repository: teampoltergeist/poltergeist

Issue #192: Capybara::Poltergeist::ObsoleteNode Needs More Explanation
Created: 2012-11-07T16:49:01Z
So I recently started using Poltergeist as the JavaScript driver for my cucumber integration tests, and I have frequently encountered the exception Capybara::Poltergeist::ObsoleteNode:
When I click "New Requirement" # features/step_definitions/navigation_steps.rb:16
  Capybara::Poltergeist::ObsoleteNode (Capybara::Poltergeist::ObsoleteNode)
  ./features/step_definitions/navigation_steps.rb:21:in `block (2 levels) in <top (required)>'
  ./features/step_definitions/navigation_steps.rb:18:in `/^I click "(.*)"$/'
  features\requirements\create_requirement.feature:13:in `When I click "New Requirement"'

For quite a while, I was confused about what this exception meant. I eventually discovered that it means that the element I am trying to click (or perform some other action on) is currently not visible, but that didn't seem very obvious to me from the error message or the documentation. I believe it would be a good idea to update the documentation, error message and/or exception itself to make its intent more clear.

Duplicate issue #179: Better error message?
Created: 2012-10-16T19:54:06Z
1) basket integration handles item removal and empty state
     Failure/Error: click_button 'login_submit'
     Capybara::Poltergeist::ObsoleteNode:
       Capybara::Poltergeist::ObsoleteNode
     # (eval):2:in `click_button'
     # ./spec/requests/basket_exercise_spec.rb:167:in `login'
     # ./spec/requests/basket_exercise_spec.rb:28:in `block (2 levels) in <top (required)>'

As someone new to Poltergeist, I have no idea what this means or how to debug it.  An error message giving me some context would be useful.  Note I'm trying to port from capybara-webkit and the test works fine there.

Closing comment (2013-01-26T17:47:23Z): Closing this as a dup of #192.
Repository: teampoltergeist/poltergeist

Issue #217: Response Headers don't overwrite cookies
Created: 2012-12-20T20:09:36Z
set initial cookie before request
page.driver.set_cookie("user_id", 1)
controller sets cookies[:user_id] = 2
visit "/change_user?user_id=2"
this passes - the right headers were sent back by rails app
page.response_headers["Set-Cookie"].match("user_id=2").should_not be_nil
this fails, user_id cookie is still 1
page.driver.cookies["user_id"].value.should == 2

Duplicate issue #503: Using default address 127.0.0.1 leads to cookies problems when using Capybara.server_host
Created: 2014-06-07T04:58:50Z
Hi, sorry for bad English. Not sure that this is a bug, in my project i'm using
Capybara.server_port = 3000
Capybara.server_host = 'localhost'

next i wanted to set cookie
page.driver.set_cookie "auth_token", "8e9beU3E20YWHmF1RBSwFa"

i found that this doesn't work.
Next I found the problem. Because of different hosts.
poltergeist-c3d41c7652c4/lib/capybara/poltergeist/driver.rb @ line 218 Capybara::Poltergeist::Driver#set_cookie:
Capybara.app_host || "127.0.0.1"

After changing server_host from 'localhost' to '127.0.0.1' all works fine.

Closing comment (2014-06-17T09:09:43Z): I suppose it's related to #217
Repository: teampoltergeist/poltergeist

Issue #8: click_link and click_button just do nothing
Created: 2012-01-10T15:19:13Z
Hi,
I'm currently trying out poltergeist, but I can't seem to get it to work correctly. I just used it to run a few request specs which pass when using the standard :rack_test-driver, but all of these scenarios failed. It seems that click_link and click_button don't work. After calling click_link the site just does not change. The debug-trace is as follows:
{"name"=>"visit", "args"=>["http://127.0.0.1:57696/"]}
{"response"=>"success"}
{"name"=>"find", "args"=>[".//a[./@href][(((./@id = 'Anmelden' or normalize-space(string(.)) = 'Anmelden') or ./@title = 'Anmelden') or .//img[./@alt = 'Anmelden'])]", nil]}
{"response"=>[0]}
{"name"=>"visible", "args"=>[0]}
{"response"=>true}
{"name"=>"click", "args"=>[0]}
{"response"=>true}

However, fill_in for example works just fine.
I also cloned the poltergeist repository and ran the tests. I have 15 failures, all of them have to do with Capybara::Session. I don't know if this is related to this issue in any way.
My environment is the following:
Mac OS X 10.6.8
PhantomJS 1.4.1 (installed the pre-built static binary)
poltergeist (0.2.0)
capybara (1.1.2)

Thanks!

Duplicate issue #5: check() doesn't work
Created: 2011-11-02T15:32:35Z
I have the feeling that .check() doesn't work for me on poltergeist:
I modified the set() method a bit to get feedback, I also changed
if value && !checked? || !value && checked?

to
if value != checked?

Here's the modified method:
 def set(value)
  if tag_name == 'input'
    type = self[:type]
    if type == 'radio'
      click
    elsif type == 'checkbox'
      if value != checked?                      
        puts "Checkbox state before click: '#{checked?}'."
        click
        puts "Checkbox state after click: '#{checked?}'."
      end
    elsif type == 'file'
      command :select_file, value
    else
      command :set, value
    end
  elsif tag_name == 'textarea'
    command :set, value
  end
end

Here is the output when trying to uncheck a checkbox:
Checkbox state before click: 'true'.
Checkbox state after click: 'true'.

So the click doesn't really seem to do the trick as far as I can see

Closing comment (2012-01-12T10:12:25Z): Please could you confirm if this is still a problem (against master)? I think it might be the same as #8, which is now fixed.
Repository: teampoltergeist/poltergeist

Issue #382: Investigate failing spec on jruby, there must be some issues in code base or jruby sockets
Created: 2013-08-27T15:09:14Z
Here's the test https://github.com/jonleighton/poltergeist/blob/master/spec/integration/driver_spec.rb#L56

Duplicate issue #265: Error running specs ...
Created: 2013-02-27T21:55:44Z
rake
Compiling lib/capybara/poltergeist/client/agent.coffee
Compiling lib/capybara/poltergeist/client/browser.coffee
Compiling lib/capybara/poltergeist/client/connection.coffee
Compiling lib/capybara/poltergeist/client/main.coffee
Compiling lib/capybara/poltergeist/client/node.coffee
Compiling lib/capybara/poltergeist/client/web_page.coffee
/Users/michaelgr/.rvm/rubies/jruby-1.7.0/bin/jruby -S rspec ./spec/integration/driver_spec.rb ./spec/integration/session_spec.rb ./spec/unit/browser_spec.rb ./spec/unit/client_spec.rb ./spec/unit/driver_spec.rb ./spec/unit/inspector_spec.rb ./spec/unit/server_spec.rb
Run options: exclude {:requires=>#Proc:/Users/michaelgr/.rvm/gems/jruby-1.7.0/gems/capybara-2.0.2/lib/capybara/spec/spec_helper.rb:25}
..
An error occurred in an after hook
IOError: not opened for reading
occurred at org/jruby/ext/socket/RubyBasicSocket.java:410:in `close_read'
F
An error occurred in an after hook
Errno::EPIPE: Broken pipe - Broken pipe
occurred at org/jruby/RubyIO.java:1401:in `write'

Closing comment (2013-08-27T15:09:51Z): Was related to #382
Repository: teampoltergeist/poltergeist

Issue #286: Specs sporadically failing even with suggested timing handling
Created: 2013-03-25T20:43:55Z
I have this kind of test:
scenario '...', js: true do
  visit user_profile_path
  click_on 'Edit profile' # opens a modal with ajax
  page.should have_content('Location') # looks good - always passing this
  fill_in 'Location', with: 'Tokyo'
  click_on 'Save changes' # submits a regular form
  page.should have_selector('#publisher_info', text: 'from Tokyo')
end
the last line fails sometimes even though it should sit around and wait for the content to appear (as described here and here). It mostly fails when running the spec for the first time after a while and subsequent runs work well.

Duplicate issue #280: False positives on checkbox click (includes test case)
Created: 2013-03-18T20:34:42Z
We are seeing intermittent failures when trying to click a checkbox.  Symptoms sound very similar to #120 - Capybara/Poltergeist acts like the click was successful, but it seemed to have clicked in the wrong spot.  In our case we have a form that has options shown/hidden (no animations, just hide/show) depending on other choices, and it seems like there's some sort of a race condition where, intermittently, Poltergeist just misses the checkbox.
Put together a gist that seems to reproduce the problem.  Generally fails within the first 10 iterations for me, often even earlier, but it seems to be a timing thing so you might have to play with the delays a bit.
https://gist.github.com/jpurcell001/5190514
This is using master of capybara/xpath as well as master of poltergeist.
The same gist passes without issue when using either selenium or webkit, so it feels like a poltergeist-specific issue.

Closing comment (2015-11-12T01:17:32Z): This would seem to be a duplicate of #286 so I'm going to close this one - as a potential solution - rather than switching to trigger(:click) when you know your checkboxes will hide rows you can use
 #click the checkbox
 expect(page).not_to have_css('css selector of the element that should be hidden')
#click the next checkbox

This will have the effect of testing that your rows do hide as you expect, and also making the test wait until the page is stable to click the next checkbox