text:
org.jetbrains.kotlin.util.KotlinFrontEndException: Front-end Internal error: Failed to analyze declaration

Hi All!
I tried adding Realm to my current project and it failed to build with the following stacktrace:
e: org.jetbrains.kotlin.util.KotlinFrontEndException: Front-end Internal error: Failed to analyze declaration Intent
File being compiled: (7,5) in /Users/steve/code/chorgi/shared/src/commonMain/kotlin/chorgi/store/CharacterListStore.kt
The root cause java.lang.AssertionError was thrown at: org.jetbrains.kotlin.resolve.lazy.descriptors.AbstractLazyMemberScope.getContributedClassifier(AbstractLazyMemberScope.kt:75)
        at org.jetbrains.kotlin.resolve.ExceptionWrappingKtVisitorVoid.visitDeclaration(ExceptionWrappingKtVisitorVoid.kt:43)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitDeclaration(KtVisitorVoid.java:457)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitDeclaration(KtVisitorVoid.java:21)
        at org.jetbrains.kotlin.psi.KtVisitor.visitNamedDeclaration(KtVisitor.java:398)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitNamedDeclaration(KtVisitorVoid.java:381)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitNamedDeclaration(KtVisitorVoid.java:969)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitNamedDeclaration(KtVisitorVoid.java:21)
        at org.jetbrains.kotlin.psi.KtVisitor.visitClassOrObject(KtVisitor.java:41)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitClassOrObject(KtVisitorVoid.java:37)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitClassOrObject(KtVisitorVoid.java:469)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitClassOrObject(KtVisitorVoid.java:21)
        at org.jetbrains.kotlin.psi.KtVisitor.visitClass(KtVisitor.java:33)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitClass(KtVisitorVoid.java:33)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitClass(KtVisitorVoid.java:463)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitClass(KtVisitorVoid.java:21)
        at org.jetbrains.kotlin.psi.KtClass.accept(KtClass.kt:20)
        at org.jetbrains.kotlin.psi.KtElementImplStub.accept(KtElementImplStub.java:60)
        at org.jetbrains.kotlin.resolve.LazyTopDownAnalyzer$analyzeDeclarations$1.registerDeclarations(LazyTopDownAnalyzer.kt:80)
        at org.jetbrains.kotlin.resolve.LazyTopDownAnalyzer$analyzeDeclarations$1.visitClassOrObject(LazyTopDownAnalyzer.kt:123)
        at org.jetbrains.kotlin.resolve.LazyTopDownAnalyzer$analyzeDeclarations$1.visitClass(LazyTopDownAnalyzer.kt:148)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitClass(KtVisitorVoid.java:463)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitClass(KtVisitorVoid.java:21)
        at org.jetbrains.kotlin.psi.KtClass.accept(KtClass.kt:20)
        at org.jetbrains.kotlin.psi.KtElementImplStub.accept(KtElementImplStub.java:60)
        at org.jetbrains.kotlin.resolve.ExceptionWrappingKtVisitorVoid.visitDeclaration(ExceptionWrappingKtVisitorVoid.kt:32)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitDeclaration(KtVisitorVoid.java:457)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitDeclaration(KtVisitorVoid.java:21)
        at org.jetbrains.kotlin.psi.KtVisitor.visitNamedDeclaration(KtVisitor.java:398)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitNamedDeclaration(KtVisitorVoid.java:381)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitNamedDeclaration(KtVisitorVoid.java:969)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitNamedDeclaration(KtVisitorVoid.java:21)
        at org.jetbrains.kotlin.psi.KtVisitor.visitClassOrObject(KtVisitor.java:41)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitClassOrObject(KtVisitorVoid.java:37)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitClassOrObject(KtVisitorVoid.java:469)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitClassOrObject(KtVisitorVoid.java:21)
        at org.jetbrains.kotlin.psi.KtVisitor.visitClass(KtVisitor.java:33)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitClass(KtVisitorVoid.java:33)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitClass(KtVisitorVoid.java:463)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitClass(KtVisitorVoid.java:21)
        at org.jetbrains.kotlin.psi.KtClass.accept(KtClass.kt:20)
        at org.jetbrains.kotlin.psi.KtElementImplStub.accept(KtElementImplStub.java:60)
        at org.jetbrains.kotlin.resolve.LazyTopDownAnalyzer$analyzeDeclarations$1.registerDeclarations(LazyTopDownAnalyzer.kt:80)
        at org.jetbrains.kotlin.resolve.LazyTopDownAnalyzer$analyzeDeclarations$1.visitKtFile(LazyTopDownAnalyzer.kt:98)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitKtFile(KtVisitorVoid.java:517)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitKtFile(KtVisitorVoid.java:21)
        at org.jetbrains.kotlin.psi.KtFile.accept(KtFile.kt:243)
        at org.jetbrains.kotlin.psi.KtFile.accept(KtFile.kt:230)
        at org.jetbrains.kotlin.resolve.ExceptionWrappingKtVisitorVoid.visitElement(ExceptionWrappingKtVisitorVoid.kt:27)
        at org.jetbrains.kotlin.com.intellij.psi.PsiElementVisitor.visitFile(PsiElementVisitor.java:35)
        at org.jetbrains.kotlin.psi.KtVisitor.visitKtFile(KtVisitor.java:73)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitKtFile(KtVisitorVoid.java:69)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitKtFile(KtVisitorVoid.java:517)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitKtFile(KtVisitorVoid.java:21)
        at org.jetbrains.kotlin.psi.KtFile.accept(KtFile.kt:243)
        at org.jetbrains.kotlin.psi.KtFile.accept(KtFile.kt:230)
        at org.jetbrains.kotlin.resolve.LazyTopDownAnalyzer.analyzeDeclarations(LazyTopDownAnalyzer.kt:203)
        at org.jetbrains.kotlin.resolve.LazyTopDownAnalyzer.analyzeDeclarations$default(LazyTopDownAnalyzer.kt:58)
        at org.jetbrains.kotlin.analyzer.common.CommonResolverForModuleFactory$Companion.analyzeFiles(CommonResolverForModuleFactory.kt:182)
        at org.jetbrains.kotlin.analyzer.common.CommonResolverForModuleFactory$Companion.analyzeFiles$default(CommonResolverForModuleFactory.kt:120)
        at org.jetbrains.kotlin.cli.metadata.CommonAnalysisKt$runCommonAnalysis$1.invoke(CommonAnalysis.kt:62)
        at org.jetbrains.kotlin.cli.metadata.CommonAnalysisKt$runCommonAnalysis$1.invoke(CommonAnalysis.kt:61)
        at org.jetbrains.kotlin.cli.common.messages.AnalyzerWithCompilerReport.analyzeAndReport(AnalyzerWithCompilerReport.kt:113)
        at org.jetbrains.kotlin.cli.metadata.CommonAnalysisKt.runCommonAnalysis(CommonAnalysis.kt:61)
        at org.jetbrains.kotlin.cli.metadata.CommonAnalysisKt.runCommonAnalysisForSerialization(CommonAnalysis.kt:39)
        at org.jetbrains.kotlin.cli.metadata.K2MetadataKlibSerializer.serialize(K2MetadataKlibSerializer.kt:57)
        at org.jetbrains.kotlin.cli.metadata.K2MetadataCompiler.doExecute(K2MetadataCompiler.kt:110)
        at org.jetbrains.kotlin.cli.metadata.K2MetadataCompiler.doExecute(K2MetadataCompiler.kt:40)
        at org.jetbrains.kotlin.cli.common.CLICompiler.execImpl(CLICompiler.kt:90)
        at org.jetbrains.kotlin.cli.common.CLICompiler.execImpl(CLICompiler.kt:44)
        at org.jetbrains.kotlin.cli.common.CLITool.exec(CLITool.kt:98)
        at org.jetbrains.kotlin.daemon.CompileServiceImpl.compile(CompileServiceImpl.kt:1575)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at java.rmi/sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:359)
        at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:200)
        at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:197)
        at java.base/java.security.AccessController.doPrivileged(Native Method)
        at java.rmi/sun.rmi.transport.Transport.serviceCall(Transport.java:196)
        at java.rmi/sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:562)
        at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:796)
        at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:677)
        at java.base/java.security.AccessController.doPrivileged(Native Method)
        at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:676)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.lang.AssertionError: Recursion detected on input: Intent under LockBasedStorageManager@84212be (metadata serializer)
        at org.jetbrains.kotlin.resolve.lazy.descriptors.AbstractLazyMemberScope.getContributedClassifier(AbstractLazyMemberScope.kt:75)
        at org.jetbrains.kotlin.resolve.scopes.InnerClassesScopeWrapper.getContributedClassifier(InnerClassesScopeWrapper.kt:29)
        at org.jetbrains.kotlin.resolve.QualifiedExpressionResolver.resolveQualifierPartListForType(QualifiedExpressionResolver.kt:151)
        at org.jetbrains.kotlin.resolve.QualifiedExpressionResolver.resolveDescriptorForType(QualifiedExpressionResolver.kt:129)
        at org.jetbrains.kotlin.resolve.TypeResolver.resolveDescriptorForType(TypeResolver.kt:970)
        at org.jetbrains.kotlin.resolve.TypeResolver$resolveTypeElement$1.visitUserType(TypeResolver.kt:247)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitUserType(KtVisitorVoid.java:933)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitUserType(KtVisitorVoid.java:21)
        at org.jetbrains.kotlin.psi.KtUserType.accept(KtUserType.java:42)
        at org.jetbrains.kotlin.psi.KtElementImplStub.accept(KtElementImplStub.java:60)
        at org.jetbrains.kotlin.resolve.TypeResolver.resolveTypeElement(TypeResolver.kt:245)
        at org.jetbrains.kotlin.resolve.TypeResolver.resolvePossiblyBareType(TypeResolver.kt:124)
        at org.jetbrains.kotlin.resolve.TypeResolver.resolveType(TypeResolver.kt:114)
        at org.jetbrains.kotlin.resolve.TypeResolver.resolveTypeProjections(TypeResolver.kt:923)
        at org.jetbrains.kotlin.resolve.TypeResolver.resolveTypeForClass(TypeResolver.kt:545)
        at org.jetbrains.kotlin.resolve.TypeResolver.resolveTypeForClassifier(TypeResolver.kt:512)
        at org.jetbrains.kotlin.resolve.TypeResolver$resolveTypeElement$1.visitUserType(TypeResolver.kt:263)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitUserType(KtVisitorVoid.java:933)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitUserType(KtVisitorVoid.java:21)
        at org.jetbrains.kotlin.psi.KtUserType.accept(KtUserType.java:42)
        at org.jetbrains.kotlin.psi.KtElementImplStub.accept(KtElementImplStub.java:60)
        at org.jetbrains.kotlin.resolve.TypeResolver.resolveTypeElement(TypeResolver.kt:245)
        at org.jetbrains.kotlin.resolve.TypeResolver.resolvePossiblyBareType(TypeResolver.kt:124)
        at org.jetbrains.kotlin.resolve.TypeResolver.resolveType(TypeResolver.kt:114)
        at org.jetbrains.kotlin.resolve.TypeResolver.resolveType(TypeResolver.kt:85)
        at org.jetbrains.kotlin.resolve.DescriptorResolver.resolveSuperTypeListEntries(DescriptorResolver.java:212)
        at org.jetbrains.kotlin.resolve.DescriptorResolver.resolveSupertypes(DescriptorResolver.java:148)
        at org.jetbrains.kotlin.resolve.lazy.descriptors.LazyClassDescriptor.computeSupertypes(LazyClassDescriptor.java:780)
        at org.jetbrains.kotlin.resolve.lazy.descriptors.LazyClassDescriptor$LazyClassTypeConstructor.computeSupertypes(LazyClassDescriptor.java:677)
        at org.jetbrains.kotlin.types.AbstractTypeConstructor$supertypes$1.invoke(AbstractTypeConstructor.kt:83)
        at org.jetbrains.kotlin.types.AbstractTypeConstructor$supertypes$1.invoke(AbstractTypeConstructor.kt:83)
        at org.jetbrains.kotlin.storage.LockBasedStorageManager$LockBasedLazyValue.invoke(LockBasedStorageManager.java:408)
        at org.jetbrains.kotlin.storage.LockBasedStorageManager$LockBasedLazyValueWithPostCompute.invoke(LockBasedStorageManager.java:481)
        at org.jetbrains.kotlin.storage.LockBasedStorageManager$LockBasedNotNullLazyValueWithPostCompute.invoke(LockBasedStorageManager.java:512)
        at org.jetbrains.kotlin.types.AbstractTypeConstructor.getSupertypes(AbstractTypeConstructor.kt:30)
        at org.jetbrains.kotlin.types.AbstractTypeConstructor.getSupertypes(AbstractTypeConstructor.kt:27)
        at org.jetbrains.kotlin.resolve.descriptorUtil.DescriptorUtilsKt.getSuperInterfaces(DescriptorUtils.kt:158)
        at io.realm.compiler.IrUtilsKt.getHasRealmModelInterface(IrUtils.kt:90)
        at io.realm.compiler.RealmModelSyntheticCompanionExtension.getSyntheticCompanionObjectNameIfNeeded(RealmModelSyntheticCompanionExtension.kt:45)
        at org.jetbrains.kotlin.resolve.extensions.SyntheticResolveExtension$Companion$getInstance$1.getSyntheticCompanionObjectNameIfNeeded(SyntheticResolveExtension.kt:83)
        at org.jetbrains.kotlin.resolve.lazy.descriptors.LazyClassMemberScope.generateSyntheticCompanionObject(LazyClassMemberScope.kt:370)
        at org.jetbrains.kotlin.resolve.lazy.descriptors.LazyClassMemberScope.getNonDeclaredClasses(LazyClassMemberScope.kt:255)
        at org.jetbrains.kotlin.resolve.lazy.descriptors.AbstractLazyMemberScope.doGetClasses(AbstractLazyMemberScope.kt:68)
        at org.jetbrains.kotlin.resolve.lazy.descriptors.AbstractLazyMemberScope.access$doGetClasses(AbstractLazyMemberScope.kt:36)
        at org.jetbrains.kotlin.resolve.lazy.descriptors.AbstractLazyMemberScope$classDescriptors$1.invoke(AbstractLazyMemberScope.kt:47)
        at org.jetbrains.kotlin.resolve.lazy.descriptors.AbstractLazyMemberScope$classDescriptors$1.invoke(AbstractLazyMemberScope.kt:47)
        at org.jetbrains.kotlin.storage.LockBasedStorageManager$MapBasedMemoizedFunction.invoke(LockBasedStorageManager.java:578)
        at org.jetbrains.kotlin.storage.LockBasedStorageManager$MapBasedMemoizedFunctionToNotNull.invoke(LockBasedStorageManager.java:651)
        at org.jetbrains.kotlin.resolve.lazy.descriptors.AbstractLazyMemberScope.getContributedClassifier(AbstractLazyMemberScope.kt:75)
        at org.jetbrains.kotlin.resolve.lazy.LazyDeclarationResolver.findClassDescriptorIfAny(LazyDeclarationResolver.kt:77)
        at org.jetbrains.kotlin.resolve.lazy.LazyDeclarationResolver.findClassDescriptor(LazyDeclarationResolver.kt:87)
        at org.jetbrains.kotlin.resolve.lazy.LazyDeclarationResolver.getClassDescriptor(LazyDeclarationResolver.kt:62)
        at org.jetbrains.kotlin.resolve.LazyTopDownAnalyzer$analyzeDeclarations$1.visitClassOrObject(LazyTopDownAnalyzer.kt:120)
        at org.jetbrains.kotlin.resolve.LazyTopDownAnalyzer$analyzeDeclarations$1.visitClass(LazyTopDownAnalyzer.kt:148)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitClass(KtVisitorVoid.java:463)
        at org.jetbrains.kotlin.psi.KtVisitorVoid.visitClass(KtVisitorVoid.java:21)
        at org.jetbrains.kotlin.psi.KtClass.accept(KtClass.kt:20)
        at org.jetbrains.kotlin.psi.KtElementImplStub.accept(KtElementImplStub.java:60)
        at org.jetbrains.kotlin.resolve.ExceptionWrappingKtVisitorVoid.visitDeclaration(ExceptionWrappingKtVisitorVoid.kt:32)
        ... 87 more

Here is the offending class:
interface CharacterListStore : Store<CharacterListStore.Intent, CharacterListStore.State, Nothing> {
    sealed class Intent {
        data class Delete(val id: Long) : Intent()
        object Loaded : Intent()
    }

    data class State(
        val characters: List<Character> = emptyList(),
        val selectedCharacterId: Long? = null,
    )
}

I've created a new minimal project from the KMM plugin in Android studio that replicates the error:
https://github.com/iamsteveholmes/RealmMVIKotlinTest
Here is the only code I created and it replicates the problem:
package com.example.realmmvikotlintest

import com.example.realmmvikotlintest.CharacterListStore.Intent
import com.example.realmmvikotlintest.CharacterListStore.State
import com.arkivanov.mvikotlin.core.store.Store

interface CharacterListStore : Store<Intent, State, Nothing> {
    sealed class Intent {
        object Loaded : Intent()
    }

    data class State(
        val characters: List<Character> = emptyList()
    )
}

data class Character(val id: Long)

Hi @iamsteveholmes thanks for reporting this. I can reproduce the issue, this is a bug in the compiler plugin that needs to be investigated, basically there's a recursion when trying to resolve companion object of CharacterListStore interface. In the meantime you can work around this by declaring the store classes outside the interface
package com.example.realmmvikotlintest
import com.arkivanov.mvikotlin.core.store.Store

sealed class Intent {
    object Loaded : Intent()
}

data class State(
    val characters: List<Character> = emptyList()
)

interface CharacterListStore : Store<Intent, State, Nothing> {

}

data class Character(val id: Long)

Thanks @nhachicha!  Curiously I didn't get your message and popped on to let you know I figured that out 😊.  This does, however, create.a naming issue with iOS.  Essentially all the inner classes have to be renamed so as not to create conflicts resulting in weird names.  But I'm going with the workaround for now.

The minimal model definition to trigger this is
interface Generic<T>

interface Outer : Generic<Outer.Inner> {
        class Inner
}

Haven't found a way to test if Outer implements our interface without triggering the same recursion in other ways yet. Will have to investigate further.

Hi. I got this error after migrate build.gradle to kotlin in my android project

Hi @Charon1997
Just be sure. Is there something preventing you from moving the Store outside the class? Or is it autogenerated for you? Currently, this is problematic to implement due to how the Kotlin Compiler runs. You can see more details here: https://kotlinlang.slack.com/archives/C7L3JB43G/p1626430519160400

@iamsteveholmes  What was your solution?
My workaround is to

Create a new multiplatform target (Gradle subproject) that separates Realm from other common code
Apply plugin only for that target/subproject.

hi，我已经收到你的邮件了，我会尽快查看的~

authors: Charon1997 ValeryBoretsky cmelchior iamsteveholmes nhachicha rorbech thipokch

repo: realm/realm-kotlin


text:
How do I use a non-default browser

I'd like Reanimate to load the animation in a browser that is not my default one. Is that possible? It seems not given
https://github.com/reanimate/reanimate/blob/5ea023980ff7f488934d40593cc5069f5fd038b0/src/Reanimate/Driver/Server.hs#L126
Forcing users to use the default browser only seems unfortunately inflexible!

You can always just open your favorite browser manually and copy over the URL. Since this only has to be done once per session, I don't think it merits a configuration option.

Hi @Lemmih, thanks for your response.

You can always just open your favorite browser manually and copy over the URL

That would be great! But where do I get the URL from? My system is set to load the Calibre eBook reader as the default browser (I have no idea why). It doesn't show the URL so there's no way for me to copy it across. Is it possible to get reanimate to print the URL on stdout?
(I realise that my setup is rather weird. If my aim were just to use reanimate in a browser then I'd set a better default browser. However, I think this experience highlights a way that reanimate could be slightly more flexible.)
Feel free to close this issue if you prefer. It's not a big deal for me.

I don't think it's worthwhile supporting this use-case. You can solve the problem by changing your default browser to Firefox or chrome, and then bookmarking the URL.

source: gharchive/issue

authors: Lemmih tomjaguarpaw

repo: reanimate/reanimate

license: Unlicense

license_type: permissive

license_source: github-api


text:
It does not recognize the right attribute

Hi all
On the following component:
let component = ReasonReact.statelessComponent("NavItemView");

let make = (~text: string, ~href: string, ~icon: string, _children) => {
  ...component,
  render: (_self) => {

        {ReasonReact.string(text)}

  }
};

Use it like:

As you can recognize, the compiler complains. But I am using component correctly.
Thanks

@bifunctor Merlin only "sees" changes in modules signatures after a compilation takes place. In your case, it seems that you changed the signature of the make function in NavItemView to add a new prop icon? In that case, you'd need to rebuild first by calling bsb -make-world (or adding bsb to reason.diagnostics.tools and saving), so Merlin can get the latest signatures.
Please let us know if the issue is solved after rebuilding.

authors: bifunctor jchavarri

repo: reasonml-editor/vscode-reasonml


text:
Allow to use ocamlformat instead ocp-indent

This ocaml format looks good
https://github.com/ocaml-ppx/ocamlformat

Thanks for the suggestion. This feature has already been requested at #184.

authors: freebroccolo mrkaspa


text:
Using rebass to create a styled component with theme

There are times when using a simple Box as='anything' is not enough.
I'm using rebass with straight emotion-theming; and I'm trying to make a styled (with theme interpolated values; responsive and everything) Font-awesome Icon.
I just don't get why, but this just doesn't work (I'm loosing the font awesome icon prop for some reason)
<Box as={FontAwesomeIcon} />

So I started to wonder : What if I want to take a custom component; make it pass through rebass / styled-system; and just use any sx or shorthand-properties on it ?
I digged into the Rebass source code and found this (how Box is constructed).
I think a quickwin would be to simply expose that function as an HoC (filled with styled-system sensible defaults props just like Box). Basically; making the div part dynamic in the expression styled('div').
What do you think ?
EDIT: to be clear;

I know I can just

import styled from 'emotion-theming'
const MyAwesomeIcon = styled(FontAwesomeIcon)`
  ${({ theme }) => /*anything you want */}
`

I also know that I can digg into styled-system compose and stuff and basically redo what rebass done for Box

But though I think it's a pity to install some sort of abstraction layer in front of more "low-level" APIs (like styled-system and emotion, for rebass); but to be forced to digg into some code and re-do it for; at the end of the day, not using rebass at-all for a particular component.

How did you end up solving this?

authors: cyrilchapon dsacramone

repo: rebassjs/rebass

license: MIT


text:
Strange decimal comparison result

>> 1.333333333333333 > 1.333333333333332
== true
>> 1.333333333333333 = 1.333333333333332
== true

This is by design and should be closed.

repo: rebol/rebol

license_source: bigquery


text:
Create Open PR

Please merge this PR
PA not responding and issue was fixed.
https://github.com/Rakesh9100/Beautiify/pull/1374
@sanjay-kv

PR is getting reviewed one by one and merged, remove the point label from here
@sanjay-kv

source: gharchive/pull-request

repo: recodehive/Opensource-practice


text:
Added RecurlyVerification for Recurly.js

Please see seperate email.
Best wishes
-Kay

This looks fantastic!  Any update on whether this pull request might be incorporated?

authors: ericas kayh

repo: recurly/recurly-client-net

license: mit


text:
Large data sets

It may be good to have a different way to work with large datasets. For example the https://ldbcouncil.org/benchmarks/graphalytics/ data sets are 1.1Tb in total.

Do you have any idea?
What should we care about it? Local storage size? Download time? ...?

Can have a threshold for streaming data from disk, instead of reading all data into memory. Have a default such as 500Mb which the user can adjust
Local storage may be an issue, perhaps ask the user if they want to proceed and give an estimate of storage space required.
For download time, cannot do much about this, on Linux wget -c is helpful for continuing an incomplete download without starting again.  If the data is stored on the cloud in a suitable form, one can stream the interesting portion, but this requires infrastructure allows this and perhaps is another step for the future.  At present want to consider datasets upto 100 Gb which may be analyzed on a workstation.

authors: bkmgit kou

repo: red-data-tools/red-datasets


text:
Fix str/bytes confusion in crypto signer API

From @pacejackson:

crypto.make_signature returns a "bytes" object but crypto.verify_signature says that signature should be a str.  In practice, a string or a bytes object for signature works because the base64 decode methods started accepting both bytes and strings in python 3.3

I think this is fixed in https://github.com/reddit/baseplate.py/pull/293
Do you agree, @pacejackson ?

Yep!

authors: pacejackson spladug


text:
Http error codes

This is actually two separate commits. One to fix postRouteServerMiddleware not being called. The other is giving a setStatus action and its relevant reducer.
:eyeglasses: @nramadas @schwers

LGTM. :fish: 🍣

repo: reddit/node-platform


text:
Nothing is done on frontend

@shubhamgupta2956 we need to complete frontend, do this fast.

Resolved in #15

@shubhamgupta2956 kuch toh kar leta

I had completed the whole frontend. Also added a README.md file

repo: redestro/zeronet


text:
Fix file path issues

Fixes #832 and includes tests!  The fix was easy...the tests were hard to develop.

This also fixes #534.

@roblg I can try to refactor that using a mock.  That would be much cleaner, you're right.

Finished refactoring the PR to use a mock of callerDependency instead of mangling it like I did before.  Thanks for the ideas, guys!

repo: redfin/react-server


text:
JobFinished is not called when using plan branches

I use this wonderful plugin. It works really well for all of my needs. The only thing which does not work so far is that there is no call for the JobFinished action when running a branch build.

@soerendd , meet the same problem, can you please state the version of Bamboo server you are using, it seems that one of the methods used comes from 6.9 version of Bamboo server, I will try to resolve the issue in the nearest future

In the meantime we use bamboo 7.0.4 and version 1.0.1 of the webhook plugin

In the meantime we use bamboo 7.0.4 and version 1.0.1 of the webhook plugin

Got it. Can you, please, provide a Bamboo error output from the build plan with configured webhooks, which do not work?

There is no error logged. The web call is just not done as it seams

authors: mettizik soerendd soerenmuehlbauer

repo: redfox-tools/bamboo-webhooks


text:
Appstudio update test-component-pac-xqug

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-component-pac-xqug-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
4 seconds
init

✅ Succeeded
19 seconds
clone-repository

✅ Succeeded
38 seconds
build-container

✅ Succeeded
8 seconds
clair-scan

✅ Succeeded
29 seconds
deprecated-base-image-check

✅ Succeeded
46 seconds
clamav-scan

✅ Succeeded
26 seconds
inspect-image

✅ Succeeded
15 seconds
sbom-json-check

✅ Succeeded
14 seconds
label-check

✅ Succeeded
7 seconds
show-sbom

✅ Succeeded
8 seconds
show-summary

Pipelines as Code CI/test-component-pac-xqug-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
4 seconds
init

✅ Succeeded
19 seconds
clone-repository

✅ Succeeded
38 seconds
build-container

✅ Succeeded
29 seconds
deprecated-base-image-check

✅ Succeeded
8 seconds
clair-scan

✅ Succeeded
46 seconds
clamav-scan

✅ Succeeded
26 seconds
inspect-image

✅ Succeeded
15 seconds
sbom-json-check

✅ Succeeded
14 seconds
label-check

✅ Succeeded
8 seconds
show-summary

✅ Succeeded
7 seconds
show-sbom


text:
Adding PyTest and github workflow

adding PyTest to pipfile.
adding pytest.yml file which create a github workflow to test code file of every PR
adding pytest.ini file and pipe file.lock file.
adding tests.py file
resolves #52

@Yarboa pipefile.lock added.


text:
team 5 login1

Burst repair sqlinjection
mysqli_real_escape_string — Escapes special characters in a string for use in an SQL statement, taking into account the current charset of the connection

Escaping works. Good thing you separated to 2 different PRs (each feature should get it's own PR).

repo: redhat-beyond/sqlinjection-training-app


text:
Improve chart-testing docs

updated "chartTesting" to "chart-testing"
Add info on using a config file.

Waiting for doc team reviews

@mmulholla Nice work! I have left a few suggestions as review comments. Please incorporate them and intimate me. I would like to take a look at the final changes. Thanks!

authors: Srivaralakshmi mmulholla

repo: redhat-certification/chart-verifier


text:
Failure using bigboot with nvme block devices

Uncovered a couple related issues while testing bigboot role on a RHEL7 instance with nvme block devices. The main issue is that the device special file for the boot partition is not being detected correctly. Here's is an example of the script invocation and resulting error output...
switch_root:/# /usr/bin/bigboot.sh -d="/dev/nvme0n1" -s="800M" -b="1" -p="p"
Device (/dev/nvme0n1) not found
...

Following this error message, the bigboot.sh script also then output a lengthy usage message which leads to the next issue. The output is too much for /dev/kmsg, so rather than seeing the error on the console, we observed this...
[    7.740073] dracut-pre-mount[377]: //lib/dracut/hooks/pre-mount/99-increase-boot-partition.sh: line 27: echo: write error: Invalid argument

This resulted in some fun head scratching, but we were finally able to figure out the root cause by adding rd.break=pre-mount kernel param and then manually running the script at the emergency shell prompt.
So there are a few things I want to fix here:

Figure out why bigboot.sh is getting "device not found" error.
Don't output the lengthy usage message when there is any error and correct some inaccuracies.
Maybe find a sysfs way to identify the actual device names rather than messing prefix strings and partition numbers.

@swapdisk what's the correct device? These parameters are passed to the script by the Ansible role code. Are -b="1" and -p="p" correct?

These are the device names from the instance...
# lsblk -p
NAME                                MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
/dev/nvme0n1                        259:0    0   32G  0 disk
├─/dev/nvme0n1p1                    259:1    0  476M  0 part /boot
└─/dev/nvme0n1p2                    259:2    0 29.5G  0 part
  ├─/dev/mapper/VolGroup00-rootVol  253:0    0    7G  0 lvm  /
  ├─/dev/mapper/VolGroup00-swapVol  253:1    0    1G  0 lvm  [SWAP]
  ├─/dev/mapper/VolGroup00-homeVol  253:2    0    2G  0 lvm  /home
  ├─/dev/mapper/VolGroup00-varVol   253:3    0    6G  0 lvm  /var
  ├─/dev/mapper/VolGroup00-logVol   253:4    0    2G  0 lvm  /var/log
  ├─/dev/mapper/VolGroup00-auditVol 253:5    0    1G  0 lvm  /var/log/audit
  └─/dev/mapper/VolGroup00-dataVol  253:6    0    1G  0 lvm  /data

The parameters we see configured by the role code were -d="/dev/nvme0n1" -s="800M" -b="1" -p="p".

authors: swapdisk ygalblum


text:
Add e2e tests

There's a lot of code moving around, and the best way to keep the tool stable is via e2e tests.
We should work towards adding e2e test for most (if not all) the commands.
ping @ashetty1 @kadel

client-go has fake package for almost all the code in there, we could leverage that.

client-go has fake package for almost all the code in there, we could leverage that.

but that is not for e2e tests but for unit tests

@containscafeine I haven't pushed many changes yet because I was waiting for a few changes to be merged over last week. Will \be pushing tests for more commands this sprint.

@ashetty1 It will be better if we can add them continuously. As soon as you have something (even a single test) please open PR with it.

@ashetty1 please link all PRs related to e2e tests to this issue so we can keep track of what is happening

Listing the PRs so far merged:
PR #242
PR #268

A complete coverage matrix for e2e tests maintained here: https://github.com/redhat-developer/ocdev/tree/master/tests/e2e

This is going awesome :fire:

This is ongoing work, I guess we can close this

authors: ashetty1 containscafeine kadel

repo: redhat-developer/odo


text:
Refactor test-cmd-link-unlink-4-cluster

/kind tests
Which functionality do you think we should add?

[ ] test-cmd-link-unlink-4-cluster should use new test approach and run successfully (217 lines of code)
[ ] compare with https://github.com/redhat-developer/odo/blob/main/tests/integration/operatorhub/cmd_link_test.go, duplicate test cases, merge together if possible

Why is this needed?
Improve tests readability and spec clean up #4741

Closing without making changes as link / unlink will be removed.


text:
Updating th oc cluster version

Signed-off-by: mdas mrinald7@gmail.com
This PR updates the OC Cluster from 3.7.2 to 3.9

Why is this update needed?

https://github.com/redhat-developer/odo/pull/518 won't run properly on v3.7.2 , so upgrading to the latest version

The oc update implementation in #518 with v3.7.2 was not able to update the deploymentConfigs properly. Things like initContainers were not removed from the deploymentConfig even after the update using the client-go. Cause of the problem is unknown to me but I guess since we are using the latest version of client-go and using a older version of oc binary, so it might be causing the problem.
So for making the current implementation of #518 work, I think we need to update oc version too.

authors: kadel mik-dass


text:
Display URL link of the deployed image

As a user, once I have deployed my application, I'd like the URL to the application to be displayed in the window.
Right now it automatically opens a new tab in the browser, but I might need to get that URL as a clickable link, as I might close the browser tab or need to copy/paste the URL in another tool.

You can already copy the route URL from the last output line (Application is exposed as: ' + route).
But I think we need to use a regular div instead of a textarea to show the output, so we can display richer content, like hyperlinks.

We can use https://www.npmjs.com/package/react-lazylog.

@dgolovin react-lazylog doesn't have clickable links, although there's a 7 month old PR for that.
Regardless, when I tried to use it, I managed to see something the 1st time, then the page rendering was gone when I reloaded.
export function DeploymentOutput(props: DeploymentOutputProps) {

  let output = props?.deployResponse;

  return (
    <Box
      display="flex"
      flexDirection="column"
      flexGrow={1}
      width="100%"
    >
      <LazyLog extraLines={1} follow enableSearch text={output} caseInsensitive />
    </Box>
  );
}

Restarting the dashboard didn't help. Something makes it crash but no idea what/why.
Uncaught Error: Invalid offset NaN specified
    at CellSizeAndPositionManager._findNearestCell (CellSizeAndPositionManager.js:277:1)
    at CellSizeAndPositionManager.getVisibleCellRange (CellSizeAndPositionManager.js:205:1)
    at ScalingCellSizeAndPositionManager.getVisibleCellRange (ScalingCellSizeAndPositionManager.js:133:1)
    at Grid._calculateChildrenToRender (Grid.js:752:1)
    at Grid.render (Grid.js:669:1)
    at finishClassComponent (react-dom.development.js:17485:1)
    at updateClassComponent (react-dom.development.js:17435:1)
    at beginWork (react-dom.development.js:19073:1)
    at HTMLUnknownElement.callCallback (react-dom.development.js:3945:1)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:3994:1)
_findNearestCell @ CellSizeAndPositionManager.js:277
getVisibleCellRange @ CellSizeAndPositionManager.js:205
getVisibleCellRange @ ScalingCellSizeAndPositionManager.js:133
_calculateChildrenToRender @ Grid.js:752
render @ Grid.js:669
finishClassComponent @ react-dom.development.js:17485
updateClassComponent @ react-dom.development.js:17435
beginWork @ react-dom.development.js:19073
callCallback @ react-dom.development.js:3945
invokeGuardedCallbackDev @ react-dom.development.js:3994
invokeGuardedCallback @ react-dom.development.js:4056
beginWork$1 @ react-dom.development.js:23964
performUnitOfWork @ react-dom.development.js:22776
workLoopSync @ react-dom.development.js:22707
renderRootSync @ react-dom.development.js:22670
performSyncWorkOnRoot @ react-dom.development.js:22293
(anonymous) @ react-dom.development.js:11327
unstable_runWithPriority @ scheduler.development.js:468
runWithPriority$1 @ react-dom.development.js:11276
flushSyncCallbackQueueImpl @ react-dom.development.js:11322
flushSyncCallbackQueue @ react-dom.development.js:11309
discreteUpdates$1 @ react-dom.development.js:22420
discreteUpdates @ react-dom.development.js:3756
dispatchDiscreteEvent @ react-dom.development.js:5889
react-dom.development.js:20085 The above error occurred in the <Grid> component:

    at Grid (http://localhost:3000/static/js/bundle.js:89761:86)
    at List (http://localhost:3000/static/js/bundle.js:92708:86)
    at div
    at AutoSizer (http://localhost:3000/static/js/bundle.js:87460:86)
    at t (http://localhost:3000/static/js/bundle.js:74527:9)
    at div
    at http://localhost:3000/static/js/bundle.js:4325:66
    at Box (http://localhost:3000/static/js/bundle.js:30235:72)
    at DeploymentOutput
    at div
    at http://localhost:3000/static/js/bundle.js:4325:66
    at Box (http://localhost:3000/static/js/bundle.js:30235:72)
    at App (http://localhost:3000/static/js/bundle.js:67:94)
    at InnerThemeProvider (http://localhost:3000/static/js/bundle.js:29473:70)
    at ThemeProvider (http://localhost:3000/static/js/bundle.js:29166:5)
    at ThemeProvider (http://localhost:3000/static/js/bundle.js:29493:5)
    at DockerMuiThemeProvider (http://localhost:3000/static/js/bundle.js:3246:3)

Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://reactjs.org/link/error-boundaries to learn more about error boundaries.
logCapturedError @ react-dom.development.js:20085
update.callback @ react-dom.development.js:20118
callCallback @ react-dom.development.js:12318
commitUpdateQueue @ react-dom.development.js:12339
commitLifeCycles @ react-dom.development.js:20736
commitLayoutEffects @ react-dom.development.js:23426
callCallback @ react-dom.development.js:3945
invokeGuardedCallbackDev @ react-dom.development.js:3994
invokeGuardedCallback @ react-dom.development.js:4056
commitRootImpl @ react-dom.development.js:23151
unstable_runWithPriority @ scheduler.development.js:468
runWithPriority$1 @ react-dom.development.js:11276
commitRoot @ react-dom.development.js:22990
performSyncWorkOnRoot @ react-dom.development.js:22329
(anonymous) @ react-dom.development.js:11327
unstable_runWithPriority @ scheduler.development.js:468
runWithPriority$1 @ react-dom.development.js:11276
flushSyncCallbackQueueImpl @ react-dom.development.js:11322
flushSyncCallbackQueue @ react-dom.development.js:11309
discreteUpdates$1 @ react-dom.development.js:22420
discreteUpdates @ react-dom.development.js:3756
dispatchDiscreteEvent @ react-dom.development.js:5889
CellSizeAndPositionManager.js:277 Uncaught Error: Invalid offset NaN specified
    at CellSizeAndPositionManager._findNearestCell (CellSizeAndPositionManager.js:277:1)
    at CellSizeAndPositionManager.getVisibleCellRange (CellSizeAndPositionManager.js:205:1)
    at ScalingCellSizeAndPositionManager.getVisibleCellRange (ScalingCellSizeAndPositionManager.js:133:1)
    at Grid._calculateChildrenToRender (Grid.js:752:1)
    at Grid.render (Grid.js:669:1)
    at finishClassComponent (react-dom.development.js:17485:1)
    at updateClassComponent (react-dom.development.js:17435:1)
    at beginWork (react-dom.development.js:19073:1)
    at HTMLUnknownElement.callCallback (react-dom.development.js:3945:1)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:3994:1)
_findNearestCell @ CellSizeAndPositionManager.js:277
getVisibleCellRange @ CellSizeAndPositionManager.js:205
getVisibleCellRange @ ScalingCellSizeAndPositionManager.js:133
_calculateChildrenToRender @ Grid.js:752
render @ Grid.js:669
finishClassComponent @ react-dom.development.js:17485
updateClassComponent @ react-dom.development.js:17435
beginWork @ react-dom.development.js:19073
callCallback @ react-dom.development.js:3945
invokeGuardedCallbackDev @ react-dom.development.js:3994
invokeGuardedCallback @ react-dom.development.js:4056
beginWork$1 @ react-dom.development.js:23964
performUnitOfWork @ react-dom.development.js:22776
workLoopSync @ react-dom.development.js:22707
renderRootSync @ react-dom.development.js:22670
performSyncWorkOnRoot @ react-dom.development.js:22293
(anonymous) @ react-dom.development.js:11327
unstable_runWithPriority @ scheduler.development.js:468
runWithPriority$1 @ react-dom.development.js:11276
flushSyncCallbackQueueImpl @ react-dom.development.js:11322
flushSyncCallbackQueue @ react-dom.development.js:11309
discreteUpdates$1 @ react-dom.development.js:22420
discreteUpdates @ react-dom.development.js:3756
dispatchDiscreteEvent @ react-dom.development.js:5889
react-dom.development.js:67 Warning: Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in a useEffect cleanup function.
    at ImageSelector (http://localhost:3000/static/js/bundle.js:2152:94)
    at div
    at http://localhost:3000/static/js/bundle.js:4325:66
    at Box (http://localhost:3000/static/js/bundle.js:30235:72)
    at App (http://localhost:3000/static/js/bundle.js:67:94)
    at InnerThemeProvider (http://localhost:3000/static/js/bundle.js:29473:70)
    at ThemeProvider (http://localhost:3000/static/js/bundle.js:29166:5)
    at ThemeProvider (http://localhost:3000/static/js/bundle.js:29493:5)
    at DockerMuiThemeProvider (http://localhost:3000/static/js/bundle.js:3246:3)

@fbricon It was is old and abandoned, but it is working fine in VSCode OpenShift. Another option to use PatternFly reat-log-viewer but I have no idea how to control styles there and if it support links.

authors: dgolovin fbricon slemeur

repo: redhat-developer/openshift-dd-ext


text:
Adjust "resolved" field of package-lock.json.

Signed-off-by: Roland Grunberg rgrunber@redhat.com

When I run npm i --also=dev, the package-lock.json gets modified due to npm-force-resolutions. It might be worth committing these changes as well.
diff --git a/package-lock.json b/package-lock.json
index 69b13ad..877614b 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -2941,13 +2941,13 @@
           "dev": true,
           "optional": true,
           "requires": {
-            "minimist": "0.0.8"
+            "minimist": "1.2.5"
           },
           "dependencies": {
             "minimist": {
-              "version": "0.0.8",
-              "resolved": "https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz",
-              "integrity": "sha1-hX/Kv8M5fSYluCKCYuhqp6ARsF0=",
+              "version": "1.2.5",
+              "resolved": "https://registry.npmjs.org/minimist/-/minimist-1.2.5.tgz",
+              "integrity": "sha512-FM9nNUYrRBAELZQT3xeZQ7fmMOBg6nWNmJKTcgsJeaLstP/UODVpGsr5OhXhhXg6f+qtJ8uiZ+PUxkDWcgIXLw==",
               "dev": true,
               "optional": true
             }
@@ -3098,7 +3098,7 @@
           "requires": {
             "deep-extend": "^0.6.0",
             "ini": "~1.3.0",
-            "minimist": "^1.2.0",
+            "minimist": "1.2.5",
             "strip-json-comments": "~2.0.1"
           },
           "dependencies": {

repo: redhat-developer/vscode-quarkus


text:
Update readme

First draft for the readme.
Would it be good if I added some gifs to the readme for some of the features?
Signed-off-by: David Kwon dakwon@redhat.com

Very nice! Thanks @xorye

authors: fbricon xorye


text:
operator [O] kubecost (1.106.0)

Signed-off-by: chipzoller chipzoller@gmail.com
This PR increases the memory limit to the correct container in the manager controller.
Thanks for submitting your Operator. Please check the below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?
[ ] Have you tested your Operator with all Custom Resource Definitions?
[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want to use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description of the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/merge possible

/merge possible

authors: chipzoller framework-automation


text:
change dependabot to weekly checks to reduce the noise

Changing the interval for dependabot to weekly to hopefully reduce the number of PR's, and the number of /retest that we have to run while waiting for infrastructure.

Coverage: 82.09%. Remained the same when pulling 2dbcfddd43e939f95afcadff3ede73aa3f816fa9 on acornett21:updating_dependabot into cd2df56df2665604f70da453b2f67e41cca1ac41 on redhat-openshift-ecosystem:main.


text:
Use more tags

Need to make better use of task tagging throughout the oooq roles.

There is some overlap between this and #12, although being able to do stuff via playbooks suggests variables rather than tags as the basic control paradigm.

This is a bit too general to be actionable. We can open new issues for specific places where tags need adding.

authors: larsks trown

repo: redhat-openstack/tripleo-quickstart


text:
Openshift integration with jetpack

I find jetpack is the simplest way to deploy Redhat OSP/triple-O.  Do you have plans to integrate openshift deployment  with jetpack in your roadmap?

In OSP15, the OCP deployment process has deprecated via Director. As Jetpack backend is Infrared, so it is possible to provision OCP nodes as Infrared have these pre-defined plugins available.
  --topology-nodes TOPOLOGY-NODES
                        Provision topology.
                        List of nodes types and they amount, in a "key:value" format.
                        Example: "'--topology-nodes 'undercloud:1,controller:3,compute:2'"
                        Available values: ['diskless', 'ceph', 'odl', 'compute_dvr', 'mds', 'ironic', 'freeipa', 'osdcompute', 'vqfx-pfe', 'openshift-worker', 'monitor', 'hcicephmon', 'novacontrol', 'telemetry', 'networker', 'cfme', 'radosgw', 'cfme_tester', 'contnet', 'serviceapi', 'tester', 'standalone', 'controller', '**openshift-teste**r', 'tripleo', '**openshift-master**', 'swift', 'vqfx', 'compute', 'database', 'undercloud', 'heat', '**openshift-infra**', 'aio', 'messaging', 'opstools', 'loadbalancer', 'hcicephall']

@psuriset Yes, I have plans to integrate 4.x using custom playbooks but not 3.11
@pradiptapks We can do this outside of infrared.

authors: pradiptapks psuriset smalleni

repo: redhat-performance/jetpack


text:
Implement config parser

A few values are appearing in the code that we could make available for users in a config file, using the config crate. For example the IP and Port values here

can assign to me if happy with the idea, also we could create some labels like (won't fix, invalid, question etc).

@leonjia0112 proposed something similar in https://github.com/redhat-university-partnerships/keylime/pull/18
I think you're both right that it makes sense to have a config file.  My concerns with that PR were twofold: first, compatibility with MIT, and second, not exposing options unnecessarily.  (The more handles we have, the more possible misconfigurations there are.)
MIT puts the config file at /etc/keylime.conf, with an environment variable indicating path to alternate configuration.  They also seem to be using an INI-style file there as expected, with separate section for the cloud node (as well as some general options we probably should look at too).
That said, I think this should be used as a starting point, not a final decider.  We probably won't want all the features they've implemented (definitely not in a first pass, at any rate).

May I reopen the PR for another review? I think we can use that config parser for storing the registrar IP address and port number at this point, which is needed in cloud_node functions.

good point @frozencemetery , so we should use the existing namespace [cloud_node] and /etc/keylime.conf naming [0]
This way if folks run an "all in one" single machine deployment for testing / development they can have a single config for all values, and if they run a server / client arch, then the rust cloud node will only parse out the [cloud_node] section.
[0] https://github.com/mit-ll/python-keylime/blob/master/keylime.conf#L36

authors: frozencemetery leonjia0112 lukehinds

repo: redhat-university-partnerships/keylime


text:
Redisson : Issue while unlock lock for a key ,  attempt to unlock lock, not locked by current thread

Hi, I am getting below errors in my logs.
java.lang.IllegalMonitorStateException: attempt to unlock lock, not locked by current thread by node id: 8c8ffe61-5bd3-4d78-a5c0-2d2386af488e thread-id: 76
at org.redisson.RedissonLock.lambda$unlockAsync$3(RedissonLock.java:581)

I am using below dependency for redisson:
<dependency> 			<groupId>org.redisson</groupId> 			<artifactId>redisson-spring-boot-starter</artifactId> 			<version>3.12.4</version> 			<exclusions> 				<exclusion> 			 		<groupId>com.fasterxml.jackson.datatype</groupId>   					<artifactId>jackson-datatype-jsr310</artifactId> 				</exclusion> 			</exclusions> 		</dependency>
And I've implemented a wrapper that will acquire and release the lock:
`public  T lock(final String key, final CustomSupplier task) throws BaseException {
	try {
		RLock lock = redissonClient.getLock(key);
		boolean res = lock.tryLock(WAIT_TIME, LEASE_TIME, TimeUnit.SECONDS);
		if (res) {
			log.info("Acquired lock for key {}", key);
			try {
				final T response = task.get();
				return response;
			} catch (Exception e) {
				log.error("Error occured while executing task",e);
				throw e;
			} finally {
				if (lock.isLocked() && lock.isHeldByCurrentThread()) {
					log.info("Unlocking lock for key {}", key);
					lock.unlock();
					log.info("Released lock for key {}", key);

				}
			}
		} else {
			log.info("Failed to acquire lock for key {} as lock for this key is already held", key);
			throw new BaseException("Failed to acquire lock for key" + key, ErrorCodes.LOCK_ACQUIRE_FAILURE,
					HttpStatus.INTERNAL_SERVER_ERROR);
		}
	} catch (InterruptedException e) {
		throw new BaseException("Failed to acquire lock for key" + key, ErrorCodes.LOCK_ACQUIRE_FAILURE,
				HttpStatus.INTERNAL_SERVER_ERROR);
	}

}`

But the log "Released lock for key" is logged rarely. The task after acquiring the lock gets finished within 1 or 2 seconds and the wait and lease time are 5 and 15 secs respectively.
RedisConfig is :
	@Bean(destroyMethod = "shutdown") 	public RedissonClient redissonClient() throws IOException { 		Config config = new Config(); 		config.useSingleServer().setAddress(redisAddress); 		return Redisson.create(config); 	}
We have redis server in Kubernetes cluster with 2 pod instances both as master.
Would appreciate any suggestions?

RLock object behaves according to the Java Lock specification. It means only lock owner thread can unlock it otherwise IllegalMonitorStateException would be thrown. Otherwise consider to use RSemaphore object.
https://github.com/redisson/redisson/wiki/8.-distributed-locks-and-synchronizers/#81-lock

感觉你在释放锁之前需要做一下判断，
public void unlockSingle(String lockKey, String user) {
RLock lock = redissonClient.getLock(lockKey);
if (lock.isLocked() && lock.isHeldByCurrentThread()) {
lock.unlock();
}
}

As option you can store id of current thread and pass it to unlockAsync() method.

authors: lzh1043060917 mrniko sharmakaumudi

repo: redisson/redisson


text:
Redisson >= 3.24.3 and Scala 2.12.15 does not compile

Expected behavior
Redisson >= 3.24.3 and Scala 2.12.15 should compile when selecting Codecs and build as before. Previous versions have no issues.
Actual behavior
[ERROR] Failed to execute goal net.alchim31.maven:scala-maven-plugin:4.8.1:compile (default-cli) on project scala-redisson-experiment: wrap: scala.reflect.internal.FatalError:
[ERROR]   bad constant pool index: 0 at pos: 1020
[ERROR]      while compiling: /Users/tester/test/projects/personal/scala-redisson-experiment/src/main/scala/com/test/HelloWorld.scala
[ERROR]         during phase: globalPhase=typer, enteringPhase=namer
[ERROR]      library version: version 2.12.15
[ERROR]     compiler version: version 2.12.15
[ERROR]   reconstructed args: -bootclasspath /Users/tester/.m2/repository/org/scala-lang/scala-library/2.12.15/scala-library-2.12.15.jar -classpath /Users/tester/.m2/repository/com/esotericsoftware/minlog/1.3.1/minlog-1.3.1.jar:/Users/tester/.m2/repository/io/netty/netty-resolver/4.1.100.Final/netty-resolver-4.1.100.Final.jar:/Users/tester/.m2/repository/com/fasterxml/jackson/core/jackson-annotations/2.15.2/jackson-annotations-2.15.2.jar:/Users/tester/.m2/repository/org/reactivestreams/reactive-streams/1.0.4/reactive-streams-1.0.4.jar:/Users/tester/.m2/repository/javax/cache/cache-api/1.1.1/cache-api-1.1.1.jar:/Users/tester/.m2/repository/io/netty/netty-handler/4.1.100.Final/netty-handler-4.1.100.Final.jar:/Users/tester/.m2/repository/io/netty/netty-common/4.1.100.Final/netty-common-4.1.100.Final.jar:/Users/tester/.m2/repository/io/netty/netty-codec-dns/4.1.100.Final/netty-codec-dns-4.1.100.Final.jar:/Users/tester/.m2/repository/io/netty/netty-buffer/4.1.100.Final/netty-buffer-4.1.100.Final.jar:/Users/tester/.m2/repository/io/reactivex/rxjava3/rxjava/3.1.6/rxjava-3.1.6.jar:/Users/tester/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.15.2/jackson-databind-2.15.2.jar:/Users/tester/.m2/repository/com/fasterxml/jackson/dataformat/jackson-dataformat-yaml/2.15.2/jackson-dataformat-yaml-2.15.2.jar:/Users/tester/.m2/repository/io/netty/netty-transport/4.1.100.Final/netty-transport-4.1.100.Final.jar:/Users/tester/.m2/repository/org/yaml/snakeyaml/2.0/snakeyaml-2.0.jar:/Users/tester/.m2/repository/org/redisson/redisson/3.24.3/redisson-3.24.3.jar:/Users/tester/.m2/repository/net/bytebuddy/byte-buddy/1.14.5/byte-buddy-1.14.5.jar:/Users/tester/.m2/repository/io/netty/netty-codec/4.1.100.Final/netty-codec-4.1.100.Final.jar:/Users/tester/.m2/repository/io/netty/netty-transport-native-unix-common/4.1.100.Final/netty-transport-native-unix-common-4.1.100.Final.jar:/Users/tester/.m2/repository/com/esotericsoftware/reflectasm/1.11.9/reflectasm-1.11.9.jar:/Users/tester/.m2/repository/com/esotericsoftware/kryo/5.5.0/kryo-5.5.0.jar:/Users/tester/.m2/repository/org/objenesis/objenesis/3.3/objenesis-3.3.jar:/Users/tester/.m2/repository/org/jboss/marshalling/jboss-marshalling/2.0.11.Final/jboss-marshalling-2.0.11.Final.jar:/Users/tester/.m2/repository/io/projectreactor/reactor-core/3.5.3/reactor-core-3.5.3.jar:/Users/tester/.m2/repository/com/fasterxml/jackson/core/jackson-core/2.15.2/jackson-core-2.15.2.jar:/Users/tester/.m2/repository/org/jodd/jodd-bean/5.1.6/jodd-bean-5.1.6.jar:/Users/tester/.m2/repository/io/netty/netty-resolver-dns/4.1.100.Final/netty-resolver-dns-4.1.100.Final.jar:/Users/tester/.m2/repository/org/slf4j/slf4j-api/1.7.36/slf4j-api-1.7.36.jar:/Users/tester/.m2/repository/org/jodd/jodd-core/5.1.6/jodd-core-5.1.6.jar:/Users/tester/.m2/repository/org/jboss/marshalling/jboss-marshalling-river/2.0.11.Final/jboss-marshalling-river-2.0.11.Final.jar:/Users/tester/test/projects/personal/scala-redisson-experiment/target/classes:/Users/tester/.m2/repository/org/scala-lang/scala-compiler/2.12.15/scala-compiler-2.12.15.jar:/Users/tester/.m2/repository/org/scala-lang/scala-library/2.12.15/scala-library-2.12.15.jar:/Users/tester/.m2/repository/org/scala-lang/modules/scala-xml_2.12/1.0.6/scala-xml_2.12-1.0.6.jar:/Users/tester/.m2/repository/jline/jline/2.14.6/jline-2.14.6.jar:/Users/tester/.m2/repository/org/scala-lang/scala-reflect/2.12.15/scala-reflect-2.12.15.jar -Ypartial-unification -Xexperimental
[ERROR]
[ERROR]   last tree to typer: Ident(MarshallingCodec)
[ERROR]        tree position: line 11 of /Users/tester/test/projects/personal/scala-redisson-experiment/src/main/scala/com/test/HelloWorld.scala
[ERROR]               symbol: <none>
[ERROR]    symbol definition: <none> (a NoSymbol)
[ERROR]       symbol package: <none>
[ERROR]        symbol owners:
[ERROR]            call site: method main in object HelloWorld in package test
[ERROR]
[ERROR] == Source file context for tree position ==
[ERROR]
[ERROR]      8   def main(args: Array[String]) = {
[ERROR]      9     println("Hello, world")
[ERROR]     10     val conf = new Config()
[ERROR]     11     conf.setCodec(new MarshallingCodec())
[ERROR]     12   }
[ERROR]     13 }
[ERROR]     14
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Steps to reproduce or test case
I made a git repo which if you check out and run mvn scala:compile then you should see the same error.
Make sure you have jdk 17 and Scala 2.12.15.
Github
Redis version
Redisson version
2.12.15
Redisson configuration

Sorry, I don't have any experience with Scala. What is the issue?

It doesnt compile starting from redisson version 3.24.3, but it worked fine before

I don't have tests with scala. So can't help here

Others seem to work. Just that we already have an old project using this particular codec, so I was wondering if this bug could be resolved.
Is there any support for codec conversion would we just need to rewrite existing data?

Try to upgrade/downgrade MarshallingCodec version.

authors: jakobjaks mrniko


text:
High Memory Consumption during Conversation Indexing

In setting where public channels with a lot of messages are indexed Smarti suffer from very high memory usage resulting in extrem slowdowns due to high GC load. In settings with lower heap space limits we even see OOM errors such as
Exception in thread "conversation-indexing-thread-1" java.lang.OutOfMemoryError: Java heap space
    at java.util.Arrays.copyOf(Arrays.java:3332)
[..]
    at java.io.StringWriter.write(StringWriter.java:77)
    at org.apache.solr.common.util.XML.escape(XML.java:203)
    at org.apache.solr.common.util.XML.escapeAttributeValue(XML.java:80)
    at org.apache.solr.common.util.XML.writeXML(XML.java:138)
    at org.apache.solr.client.solrj.util.ClientUtils.writeVal(ClientUtils.java:125)
[..]
    at org.apache.solr.client.solrj.SolrClient.add(SolrClient.java:190)
    at io.redlink.smarti.query.conversation.ConversationIndexer.updateConversation(ConversationIndexer.java:253)

After investigations this was caused by the combination of the following:

Could Sync loads conversations in batches of 10
Indexing conversations requires copy the text of messages

to merge messages sent by the same user within a configured time limit
collect text of messages with the conversation (done for MLT searches)

the use of an embedded Solr Server requires also the Server side processing of large document to be in the same JVM

Messages are stored as sub-documents of the conversation resulting in huge Solr Documents for conversations
Copy Field configurations with different analysis will require to keep multiple copies of the text in memory

in a first step I will make the batch size configurable. This should decrease the memory pressure as only a single conversation is loaded into memory. The other points require further analysis as changes with those could affect the functionality of the conversation search and the similar conversation search

NOTE: the cuase of this is that public channels with a high amount of messages can not be indexed in the current index layout. The adaption of the index layout to this new requirement will be implemented by #302 in smarti 0.9.0

repo: redlink-gmbh/smarti


text:
Replace deleteFilteredStreamRuletag by deleteFilteredStreamRuleId

Twitter API has not an endpoint to delete a stream rule by tag. Instead of that, it has one to delete it by id.
@link https://documenter.getpostman.com/view/9956214/T1LMiT5U#6960d456-14d6-4042-a3cd-5ae2add9e499

Hi, I've just updated the javadoc ;)

Thank you very much!


text:
Calculator works very slow and not always gets input

Describe the bug
I'm choosing GUI library for my project and tried calculator from examples, but it works very very slow and doesn't always register mouse button(on gif I clicked at every single one button, but only sometimes number shows).
There is no difference between debug and release build.

OS
Ubuntu 20.04
Orbtk
0.3.14-alpha4
2ca5c6efe1f9f2d91fe5955b6f0d09056e9e0f51
Hotspot perf report(https://github.com/KDAB/hotspot)

Thank you for the report maybe it is connected to issue #314 (memory leak) on Linux. We are working on alternatives to the current backend but I will also check to fix this.
What display server are you using?

X11 - Gnome 3.36.4

Thanks.

This commit caused also problems with other demos like  tab_widget

@qarmin thank you very much. This will speed up the fix a lot. I finish one task I'm currently work on and after that I will fix this.

authors: FloVanGH qarmin

repo: redox-os/orbtk


text:
SASL Authentication failed

I was able to go through the steps in methods 1 and 2 without issues. But when going through the steps outlined in method 3 I run into the following error:
> kubectl -n redpanda run rpk -ti --rm --restart=Never --image vectorized/redpanda:v21.11.15 --command -- /bin/bash -c "rpk topic create test-topic --user admin --password test --sasl-mechanism SCRAM-SHA-256 --brokers redpanda-0.redpanda.redpanda.svc.cluster.local.:9092 --tls-enabled --tls-truststore <(echo '$CERT')"
unable to create topics [test-topic]: SASL authentication failed: security: Invalid credentials: SASL_AUTHENTICATION_FAILED: SASL Authentication failed.

Running the following command is successful:
> helm test redpanda -n redpanda
NAME: redpanda
LAST DEPLOYED: Fri Apr 29 10:17:03 2022
NAMESPACE: redpanda
STATUS: deployed
REVISION: 1
TEST SUITE:     redpanda-test-kafka-sasl-status
Last Started:   Fri Apr 29 10:19:57 2022
Last Completed: Fri Apr 29 10:20:05 2022
Phase:          Succeeded
NOTES:
Congratulations on installing redpanda!

I'll look more into this, maybe the credentials aren't actually being enabled for SASL as the README says.
===========================
Adding more details on my environment:
System:
Ubuntu 22.04
Docker 20.10.12

Install arkade (my version was v0.8.23):
curl -sLS https://get.arkade.dev | sudo sh

> ark get helm jq minikube kubectl@v1.23.3 kubens kubectx
> minikube start --kubernetes-version v1.23.3
> ark install cert-manager
> helm install redpanda . -f values_add_tls.yaml -f values_add_sasl.yaml -n redpanda --create-namespace
> CERT=$(kubectl exec -n redpanda  redpanda-0 -c redpanda -- cat /etc/tls/certs/ca.crt)
> kubectl -n redpanda run rpk -ti --rm --restart=Never --image vectorized/redpanda:v21.11.15 --command -- /bin/bash -c "rpk topic create test-topic --user admin --password test --sasl-mechanism SCRAM-SHA-256 --brokers redpanda-0.redpanda.redpanda.svc.cluster.local.:9092 --tls-enabled --tls-truststore <(echo '$CERT')"
unable to create topics [test-topic]: SASL authentication failed: security: Invalid credentials: SASL_AUTHENTICATION_FAILED: SASL Authentication failed.
pod "rpk" deleted
pod redpanda/rpk terminated (Error)

Arkade installed minikube@v1.25.2, but that probably doesn't impact much since the commands above pin the k8s version.

This is because the admin user is registered in the config though needs explicitly creating via the rpk acl create command. The helm tests do create this user and then at the end of the test delete it. I will update the NOTES.txt to include the commands necessary and to avoid any confusion.

This is because the admin user is registered in the config though needs explicitly creating via the rpk acl create command. The helm tests do create this user and then at the end of the test delete it. I will update the NOTES.txt to include the commands necessary and to avoid any confusion.

Thanks for updating the README with this! I should have checked to see if the user was created, I assumed it had to be because the test was passing, but I didn't realize the test also created and then removed a user.
Just to point out that there is another PR waiting to be approved that also modifies the README, so you may branch from that to make it easy to merge both. It looks like Roko has approved/merged most PRs here, maybe @rkruze or @jrkinley could approve this?

After creating the user (thanks @redp01 !) I was able to run through this test with the following commands:
k create ns helm-test
helm -n helm-test install redpanda redpanda -f redpanda/values_add_sasl.yaml -f redpanda/values_add_tls.yaml
CERT=$(k exec -n helm-test redpanda-0 -c redpanda -- cat /etc/tls/certs/ca.crt)
k exec -it -n helm-test redpanda-0 -- rpk acl user create admin -p test --api-urls redpanda.helm-test.svc.cluster.local:9644 --admin-api-tls-truststore /etc/tls/certs/admin/ca.crt --tls-truststore /etc/tls/certs/ca.crt
k -n helm-test run rpk -ti --rm --restart=Never --image vectorized/redpanda:v21.11.16 --command -- /bin/bash -c "rpk topic create test-topic --user admin --password test --sasl-mechanism SCRAM-SHA-256 --brokers redpanda-0.redpanda.helm-test.svc.cluster.local.:9092 --tls-enabled --tls-truststore <(echo '$CERT')"

repo: redpanda-data/helm-charts


text:
Small scrolling improvement

I just have another suggestion concerning the scrolling behavior.
If there is a <pre> section in a Markdown notes file, which is wider than the current devices' screen, then it appears a horizontal scrollbar for the whole note file. In fact, this disturbs sometimes when you accidentally scroll horizontally but just want to scroll the document vertically.
My suggestion would be: Making a <pre> section with following style rules would result in a scrollable area only for this part of the document.
pre {
  max-width: 100%;
  overflow-x: scroll;
}

Would this be possible? Thank you in advance!

Added in https://github.com/redsolver/noteless/releases/tag/v1.2.1

Added in https://github.com/redsolver/noteless/releases/tag/v1.2.1

Just installed your latest version v1.2.1 and it works perfectly, thank you for your instant work on this - just great!
Closing this.

authors: femto-code redsolver

repo: redsolver/noteless


text:
CRA failing with React 18

Hey, I'm trying to spin up a new app using the following:
npx create-react-app my-app --template redux-typescript
and seeing this error even when using --force or --legacy-peer-deps
Installing template dependencies using npm...
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: mc-qa-app-demo@0.1.0
npm ERR! Found: react@18.0.0
npm ERR! node_modules/react
npm ERR!   react@"^18.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.8.3 || ^17" from react-redux@7.2.6
npm ERR! node_modules/react-redux
npm ERR!   react-redux@"^7.2.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /Users/christopher.mowbray/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/christopher.mowbray/.npm/_logs/2022-03-30T10_07_21_210Z-debug.log
`npm install --no-audit --save @reduxjs/toolkit@^1.5.1 @testing-library/react@^9.3.2 @testing-library/jest-dom@^4.2.4 @testing-library/user-event@^7.1.2 @types/node@^12.0.0 @types/react@^16.9.0 @types/react-dom@^16.9.0 @types/react-redux@^7.1.7 @types/jest@^24.0.0 react-redux@^7.2.0 typescript@~4.1.5` failed

Yeah, it's an unfortunate combination of CRA + NPM behavior.
Tracking this in https://github.com/reduxjs/react-redux/issues/1881 , and related thoughts at https://github.com/reduxjs/react-redux/issues/1740#issuecomment-1083184887.

Cheers @markerikson!

authors: chrismowbraybv markerikson

repo: reduxjs/cra-template-redux-typescript


text:
Performance many listeners

What docs page needs to be fixed?

Section: Performance

Page:  How well does Redux “scale” in terms of performance and architecture?

What is the problem?
From what I can tell, redux will notify all subscribers to the store when anything in the store changes no matter if it's a subscription to a deeply nested leaf or a subscription to the top level of the state.
In an application where you follow the guiding principle:

many individual components should be connected to the store instead of just a few... [docs]

You could end up with lots of listeners and potentially performance issues?
I understand that often the key bottleneck is to avoid rerenders and just because the listener function is evaluated doesn't mean the subscribing component will re-render. However, isn't it worth adding a performance consideration that all listener functions will be evaluated?
What should be changed to fix the problem?
Put a footnote that all listener functions will be evaluated, therefore the listener functions should generally be fast to evaluate and potentially kept to a minimum? Or potentially just acknowledge that evaluating all the listeners will most likely not be the bottleneck in a typical application?

This is already covered repeatedly in the docs, and I answered this in your Stack Overflow issue ( https://stackoverflow.com/a/65811853/62937 ) as well.

This is already covered repeatedly in the docs, and I answered this in your Stack Overflow issue ( https://stackoverflow.com/a/65811853/62937 ) as well.

thanks

thanks

repo: reduxjs/redux


text:
Modify: optimize compose，support more args

const logger1 = (next, ctx) => action => {
    console.log(ctx);
    console.log('logger1 >>>')
    next(action)
    console.log('logger1 <<<')
}

const logger2 = (next, ctx) => action => {
    console.log(ctx);
    console.log('logger2 >>>')
    next(action)
    console.log('logger2 <<<')
}

const dispose = action => {
   console.log(action)
}

const compose = funcs => {
   return funcs.reduce((a, b) => (next, ...rest) => a(b(next, ...rest), ...rest))
}

const newDispose = compose([logger1, logger2])(dispose, 'ctx')
newDispose('action')

middleware function can support more agrs by…rest.

Appreciate the PR, but there's no reason to make changes to compose at this time.

Sorry, Maybe I can not agree.
Some times, i need some context in every middleware, it  need pass all agrs to every middleware.
In origin code,
a(b(...args))

function a just receive one arg, but b receive all args, params not equal i every middleware, so maybe i think it is a bug.

Appreciate the PR, but there's no reason to make changes to compose at this time.
Sorry, Maybe I can not agree.
Some times, i need some context in every middleware, it need pass all agrs to every middleware.

In origin code,
a(b(...args))
function a just receive one arg, but b receive all args, params not equal i every middleware, so maybe i think it is a bug.

Appreciate the PR, but there's no reason to make changes to compose at this time.

Sorry, Maybe I can not agree.
Some times, i need some context in every middleware, it need pass all agrs to every middleware.
In origin code,
a(b(...args))
function a just receive one arg, but b receive all args, params not equal i every middleware, so maybe i think it is a bug.

authors: maquannene markerikson


text:
docs(introduction): add "Quick Start" page

PR Type
Does this PR add a new page, or update an existing page?

Adds the "Quick Start" page,

Checklist

[x] Is there an existing issue for this PR?

#3594

[x] Have the files been linted and formatted?

What docs page is being added or updated?

Section: Introduction
Page: QuickStart

For Adding New Content
What kind of content category is this page (tutorial, how-to, explanation, reference)?
tutorial.
Who is the intended target audience?
Redux users who want to quickly bootstrap their next project with the latest technologies.
What knowledge are we assuming they have?
Very minimal Redux knowledge, no prior Redux Toolkit experience needed. Basic JS and/or React knowledge.
What are the intended results or takeaways from reading this page?
To be able to gain just enough Redux and Redux Toolkit knowledge to be able to start their next project. They can learn Redux more in-depth in later tutorials.
What is the most critical info they should learn?
Learning the basics of Redux and Redux Toolkit, and how to tie those basics in to building vanilla or React based apps.
TODOs

[ ] Add CodeSandboxes to ensure the code runs properly
[ ] Add more links throughout the tutorial
[ ] Add links for external resources at the end of the page

I actually just opened up #3674 to cover creating a "Quick Start" page, and I'd forgotten that you'd filed this.
I just had some discussion with @taniarascia about some ideas for this, and I jotted some notes in that issue.
I'm going to skim yours, but then take a stab at putting together my own version.

I'm going to skim yours, but then take a stab at putting together my own version.

Sounds good, should I go ahead and close this then?

Superseded by #3675


text:
BLD: since we already use setuptools, let's remove the optional logic…

… in setup.py (GH18113).

[x] closes #18113
[x] tests passed
[x] passes git diff upstream/master -u -- "*.py" | flake8 --diff
[x] whatsnew entry

:+1:
I did not find anything beyond the above https://github.com/reef-technologies/pandas/pull/4#issuecomment-342876149 . And I am not that certain it should be removed, it won't fail and documents the actual conditions when the bug described in next line happens. Use your best judgement, I would still lean towards removing it as the path to not having setuptools in setup.py is closed IMO.

I also checked if any other dependencies do distutils can be removed, namely I checked if https://github.com/reef-technologies/pandas/blob/2bd0ffc523060832c2eb02f3fc1ef90affa3acd3/setup.py#L15 was possibly reimplemented in setuptools and no, it was not, that was a dead end.

Thank you for the review :+1:
Fixed applied according to https://github.com/reef-technologies/pandas/pull/4#issuecomment-342876149

Codecov Report

Merging #4 into master will increase coverage by 0.38%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master       #4      +/-   ##
==========================================
+ Coverage   91.38%   91.76%   +0.38%
==========================================
  Files         163      163
  Lines       50068    52372    +2304
==========================================
+ Hits        45755    48060    +2305
+ Misses       4313     4312       -1

Flag
Coverage Δ

#multiple
89.67% <ø> (+0.47%)
:arrow_up:

#single
41.09% <ø> (+0.73%)
:arrow_up:

Impacted Files
Coverage Δ

pandas/core/groupby.py
91.93% <0%> (-0.12%)
:arrow_down:

pandas/core/generic.py
96.14% <0%> (+0.41%)
:arrow_up:

pandas/core/tools/timedeltas.py
98.9% <0%> (+0.48%)
:arrow_up:

pandas/core/nanops.py
97.22% <0%> (+0.55%)
:arrow_up:

pandas/compat/__init__.py
58.79% <0%> (+0.69%)
:arrow_up:

pandas/core/indexes/datetimelike.py
97.93% <0%> (+0.82%)
:arrow_up:

pandas/tseries/offsets.py
97.96% <0%> (+0.84%)
:arrow_up:

pandas/io/parquet.py
66.25% <0%> (+0.86%)
:arrow_up:

pandas/core/indexes/datetimes.py
96.88% <0%> (+1.4%)
:arrow_up:

pandas/core/indexes/period.py
94.55% <0%> (+1.66%)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8dac633...58ce358. Read the comment docs.

repo: reef-technologies/pandas


text:
Mod View Red Text?

If you go to Mod View and then clicking on the Mod Permissions the text would be in full red?
Vanilla:

Midnight:

I found 2 classes,
the first is permissionItemHeader__327be > permissionTitle_ffc8c2 > text-xs-normal__56c35 (--header-muted by default)
the second is  permissionItemDescription__284c1 > text-sm-normal_e612c7 (--text-secondary by default)
Idk why you set most of the variable to red in the css file
Jump ↗
--text-primary: red;
--text-secondary: red;

Jump ↗
--header-muted: red;

Idk why you set most of the variable to red in the css file

I set things to red when I don't know where they are so it's easier to find them. Thanks for pointing this one out.


text:
Add a filter on notification screen to easily selected merged|closed|draft|opened Pull Requests

Description
As maintainer of popular repository, it's quite common I need to select all merged|closed pull requests on my notification screen to mark those as "done".
I have to do it manually, which is pretty annoying.
What about adding a filter on pull request status, and even for issues?
Screenshot

Example URLs
As notification screen is per user, I can't provide a link. The screenshot talk for itself

We already do, did you install Refined GitHub?

Missed it sorry. Thanks for your answer :+1:

authors: fregante welcoMattic

repo: refined-github/refined-github


text:
Remove debounce_timeout prop from Input and TextArea components

See https://github.com/reflex-dev/reflex/pull/1627#discussion_r1299594001 for detailed explanation and suggested fix.

debounce_timeout isn't a real prop on Input or TextArea and should never be rendered into the JSX for these chakra components.
Instead, this value should be handled specially in the Input.create constructor when determining whether to use a real Input or DebounceInput wrapped Input

Ok I'll look for it

Thanks for fixing this.

Thanks for fixing this.

You are welcome.

repo: reflex-dev/reflex


text:
Clean up config parameters

Remove parameters that are unused / not pure string values
Remove .env configuration for environment variables
Update how defaults are read in reflex.py

ah hah, i knew adding a smoke test for output_system_info wouldn't be in vein... i just didn't realize it would pay off so quickly 😅

authors: masenf picklelo


text:
🛑 SmartProtection is down

In 4e71c61, SmartProtection (https://smartprotection.com) was down:

HTTP code: 404
Response time: 254 ms

Resolved: SmartProtection is back up in 577c08d after 42 minutes.

repo: reinaldoleon/monitoring


text:
🛑 Scribees is down

In 68754e1, Scribees (https://binus.ac.id/scribees/login/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Scribees is back up in 9b1ac54.


text:
🛑 BINUSMAYA (Academic Services) is down

In 705d47d, BINUSMAYA (Academic Services) (https://binusmaya.binus.ac.id/LoginAD.php) was down:

HTTP code: 404
Response time: 995 ms

Resolved: BINUSMAYA (Academic Services) is back up in 8db9ec9.


text:
🛑 Library and Knowledge Center (LKC) is down

In 150f6cf, Library and Knowledge Center (LKC) (http://library.binus.ac.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Library and Knowledge Center (LKC) is back up in ce06780.


text:
🛑 GreatNusa.com is down

In 22a91eb, GreatNusa.com (https://greatnusa.com) was down:

HTTP code: 403
Response time: 92 ms

Resolved: GreatNusa.com is back up in e8b1a37.


text:
🛑 GreatNusa.com is down

In 0f58d98, GreatNusa.com (https://greatnusa.com) was down:

HTTP code: 403
Response time: 39 ms

Resolved: GreatNusa.com is back up in dbf689e.


text:
🛑 GreatNusa.com is down

In ef48279, GreatNusa.com (https://greatnusa.com) was down:

HTTP code: 403
Response time: 117 ms

Resolved: GreatNusa.com is back up in 9f04484.


text:
Unable to open database file

Traceback (most recent call last):
  File "twitter_likes.py", line 104, in <module>
    downloader.main()
  File "twitter_likes.py", line 96, in main
    self.downloadLikes(api, args.user, args.force)
  File "twitter_likes.py", line 14, in downloadLikes
    liked_tweets = Likes(api, screen_name, self._current_path, force_redownload)
  File "/home/installation/twitter-likes-media-downloader/twitter-likes-media-downloader/likes.py", line 21, in __init__
    conn = sqlite3.connect(os.path.join(os.path.normpath(
sqlite3.OperationalError: unable to open database file

Is there a way to solve this issue ? Try to modify in likes.py line 22 without success.
Thanks for your help or advice.

Try it out now. It should create the database file in the same folder

Work as expected 👍
Thanks for your work.

authors: reinhartP toniohc


text:
adding grunt build to the boilerplate

[x] adding grunt build to into the mix
[x] integrating node inside of maven lifecycle

Changes Unknown when pulling dae4675a01693fe8870bbb4c5456de6c1da12957 on build into ** on master**.

authors: coveralls reiniergs

repo: reiniergs/polyfill-service


text:
title-intro instead of title-main

The specs in metanorma-standoc have all been addressed by your update to 1.16.2, thank you!
Except:
If you fetch ISO/IEC TR 12382:1992 with the new relaton-iso, it is now populating title-intro instead of title-main.
<bibdata type="standard" schema-version="v1.2.4">
  <fetched>2023-10-21</fetched>
  <title type="title-intro" format="text/plain" language="en" script="Latn">Permuted index of the vocabulary of information technology</title>
  <title type="main" format="text/plain" language="en" script="Latn">Permuted index of the vocabulary of information technology</title>
  <title type="title-intro" format="text/plain" language="fr" script="Latn">Index permuté du vocabulaire des technologies de l'information</title>
  <title type="main" format="text/plain" language="fr" script="Latn">Index permuté du vocabulaire des technologies de l'information</title>

That is incorrect. The hierarchy is always title-main > title-intro, title-part. If only one title-* is present, it needs to be treated as title-main.
Not urgent for this release, I'll deal, but it's still an error.

In addition,
ISO 31-0  was fetching as:
               <title type="title-intro" format="text/plain" language="en" script="Latn">Title missing</title>
                <title type="title-main" format="text/plain" language="en" script="Latn">Legacy paper document</title>
                <title type="main" format="text/plain" language="en" script="Latn">Title missing — Legacy paper document</title>

and is now fetching as:
 <title type="title-intro" format="text/plain" language="en" script="Latn">Title missing — Legacy paper document</title>
<title type="main" format="text/plain" language="en" script="Latn">Title missing — Legacy paper document</title>

So it is not splitting intro and main any more.
And ISO 683-3 was fetching as:
                <title type="title-main" format="text/plain" language="en" script="Latn">Heat-treatable steels, alloy steels and free-cutting steels</title>
                <title type="title-part" format="text/plain" language="en" script="Latn">Part 3: Case-hardening steels</title>
                <title type="main" format="text/plain" language="en" script="Latn">Heat-treatable steels, alloy steels and free-cutting steels — Part 3: Case-hardening steels</title>

and is now fetching as:
     <title type="title-intro" format="text/plain" language="en" script="Latn">Heat-treatable steels, alloy steels and free-cutting steels</title>
     <title type="title-main" format="text/plain" language="en" script="Latn">Part 3: Case-hardening steels</title>
     <title type="main" format="text/plain" language="en" script="Latn">Heat-treatable steels, alloy steels and free-cutting steels — Part 3: Case-hardening steels</title>

So part titles are no longer being recognised.
.

Because ISO keeps changing its site, we really do need to test live screenscraping of ISO against a fixture, as part of gem testing. Currently, metanorma is catching these changes instead of relaton, and that is a result of poor testing technique in metanorma, keeping the fetched records fixed in the spec.

@andrew2net can we fix this ASAP?
We also need to keep specs that involve ISO's live site and have them run daily so we can catch these issues before our users do.

Fixed in v1.16.3
$ relaton fetch 'ISO/IEC TR 12382:1992'
Resolving dependencies...
[relaton-iso] (ISO/IEC TR 12382:1992) Fetching from iso.org ...
[relaton-iso] (ISO/IEC TR 12382:1992) Found: `ISO/IEC TR 12382:1992`
<bibdata type="standard" schema-version="v1.2.4">
  <fetched>2023-10-21</fetched>
  <title type="title-main" format="text/plain" language="en" script="Latn">Permuted index of the vocabulary of information technology</title>
  <title type="main" format="text/plain" language="en" script="Latn">Permuted index of the vocabulary of information technology</title>
  <title type="title-main" format="text/plain" language="fr" script="Latn">Index permuté du vocabulaire des technologies de l'information</title>
  <title type="main" format="text/plain" language="fr" script="Latn">Index permuté du vocabulaire des technologies de l'information</title>
  ...

$ relaton fetch 'ISO 31-0'
Resolving dependencies...
[relaton-iso] (ISO 31-0) Fetching from iso.org ...
[relaton-iso] (ISO 31-0) Found: `ISO 31-0:1974`
<bibdata type="standard" schema-version="v1.2.4">
  <fetched>2023-10-21</fetched>
  <title type="title-intro" format="text/plain" language="en" script="Latn">Title missing</title>
  <title type="title-main" format="text/plain" language="en" script="Latn">Legacy paper document</title>
  <title type="main" format="text/plain" language="en" script="Latn">Title missing - Legacy paper document</title>
  <title type="title-intro" format="text/plain" language="fr" script="Latn">Title missing</title>
  <title type="title-main" format="text/plain" language="fr" script="Latn">Legacy paper document</title>
  <title type="main" format="text/plain" language="fr" script="Latn">Title missing - Legacy paper document</title>
  ...

$ relaton fetch 'ISO 683-3'
Resolving dependencies...
[relaton-iso] (ISO 683-3) Fetching from iso.org ...
[relaton-iso] (ISO 683-3) Found: `ISO 683-3:2022`
<bibdata type="standard" schema-version="v1.2.4">
  <fetched>2023-10-21</fetched>
  <title type="title-main" format="text/plain" language="en" script="Latn">Heat-treatable steels, alloy steels and free-cutting steels</title>
  <title type="title-part" format="text/plain" language="en" script="Latn">Part 3: Case-hardening steels</title>
  <title type="main" format="text/plain" language="en" script="Latn">Heat-treatable steels, alloy steels and free-cutting steels - Part 3: Case-hardening steels</title>
  <title type="title-main" format="text/plain" language="fr" script="Latn">Aciers pour traitement thermique, aciers alliés et aciers pour décolletage</title>
  <title type="title-part" format="text/plain" language="fr" script="Latn">Partie 3: Aciers pour cémentation</title>
  <title type="main" format="text/plain" language="fr" script="Latn">Aciers pour traitement thermique, aciers alliés et aciers pour décolletage - Partie 3: Aciers pour cémentation</title>
  ...

authors: andrew2net opoudjis ronaldtse

repo: relaton/relaton-iso


text:
feat: Add curl to container image

Is your feature request related to a problem? Please describe.
Due to the container image being a Alpine variant, there are not many apps preinstalled, thus the command to execute for update is a bit useless.
Describe the solution you'd like
By adding curl it would be possible to enable API request to for example podman to update an image.
Describe alternatives you've considered
I currently build a custom version of Argus by adding curl myself.

I'll add this for you now. Didn't account for all the apps that commands may want in the switch to Alpine, apologies

repo: release-argus/Argus


text:
report selector

Refactoring that was required to get objectives and objectives results accurately, as well as the addition of selector -l, --selector option for reports and filtering by manifest. Manifest can be ignored with --ignore-manifest instead of reading reliably.yaml, this allows to view everything in the org on the server.

maybe add some info to the changelog as well, as you have new user flags

maybe add some info to the changelog as well, as you have new user flags

@dmartin35 good point, I've update the changelog now

repo: reliablyhq/cli


text:
reamx如何引入babel-plugin-lodash，能提供示例吗

问题描述
reamx如何引入babel-plugin-lodash，能提供示例吗
示例代码
其他信息

你自己引入有碰到什么问题吗？另外其实没必要用这个插件，用 lodash-es 就可以了，会有 Tree Shaking。

用lodash-es需要改很多代码的，有其他方式搞不

我先用loadsh-es解决这个问题吧

authors: fewoy yesmeck

repo: remaxjs/remax


text:
🛑 Remix Dashboard is down

In c1d52c6, Remix Dashboard (https://remix.fairuse.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Remix Dashboard is back up in 9aee8d0 after 16 minutes.

repo: remix-bot/status


text:
Scroll on docs page has gross overlapping elements

This is the same issue remix-website had
The changes that need to be made should be pretty similar to the fix I added

Have a look at PR #107

authors: brookslybrand louis-smit

repo: remix-run/react-router-website


text:
CSS Side-Effect Imports not working anymore with Cloudscape

What version of Remix are you using?
1.16.0
Are all your remix dependencies & dev-dependencies using the same version?

[x] Yes

Steps to Reproduce

Pull https://github.com/joejemmely/remix-cloudscape
Run npm run dev

Expected Behavior
Styles should be extracted and applied
Actual Behavior
Styles are not extracted and applied. It used to work with unstable_cssSideEffectImports on 1.14.0

This looks like it's because Cloudscape contains files using the .css.js extension which Remix mistakenly thinks are Vanilla Extract files.
Similar to how Tailwind works in Remix, we might want to think about detecting the presence of the @vanilla-extract/css package before attempting to process these files. This still wouldn't handle the case where you want to use non-Vanilla-Extract .css.js files and Vanilla Extract at the same time, but that's much more of an edge case.

Thanks for the prompt response.

we might want to think about detecting the presence of the @vanilla-extract/css package before attempting to process these files

Related to this, I noticed that if name is missing in the package.json, the project will fail to build with Couldn't find parent package.json with a name field from XXX, the error is thrown in vanilla-extract-plugin, even though it's not installed. And even if vanilla-extract-plugin was installed, most remix apps won't have a name defined in the package.json. Is the name necessary for vanilla-extract to work properly?

Thanks for raising this issue! This should be fixed in the next release.

I gave the fix a try but it didn't work as expected. @remix-run/dev takes a dependency on @vanilla-extract/integration so there currently isn't a nice way to not have any of the vanilla-extract dependencies.

@joejemmely Thanks for the update. You're right, I missed that @vanilla-extract/css can still be requirable from your app since Remix depends on @vanilla-extract/integration which in turn depends on @vanilla-extract/css. I've just merged a PR that updates the detection logic so we now look in your app's package.json to see whether you have a direct dependency on it.

@joejemmely Could you try again with the latest nightly?

Works like a charm 🥳 Thanks for your help

authors: joejemmely markdalgleish

repo: remix-run/remix


text:
HMR does not work with anonymous exports

What version of Remix are you using?
2.0.0
Are all your remix dependencies & dev-dependencies using the same version?

[X] Yes

Steps to Reproduce
In a route file, instead of naming the route function, export it as default without a name:
export default function () {
  return (

Hello World

  )
}

Run the dev server.
Make some changes (either to the markdown or the styling)
Hit save

Expected Behavior
HMR kicks in and hot-reloads the changed element/s
Actual Behavior
Nothing happens. The page needs to be reloaded for changes to be reflected on screen.
Reproduction Repository
https://github.com/moishinetzer/remix-broken-hmr-repro (Note: Run this locally - not on codesandbox)

This is a limitation of React Fast Refresh (e.g. see the Limitations section for Fast Refresh on Next's docs), not Remix. For React Fast Refresh to track component changes, those components need to be named.

Thanks for the reply! Can we add this to the docs? It was a very tricky bug to find in the first place.

Thanks for the reply! Can we add this to the docs? It was a very tricky bug to find in the first place.

Good suggestion! Here's the PR: https://github.com/remix-run/remix/pull/7501

authors: moishinetzer pcattori


text:
fix(dev): kill app server when remix dev terminates

Closes: #

[ ] Docs
[ ] Tests

Testing Strategy:

holding off on merging this. need to rebase to release-next after v2 prerelease is cut


text:
chore: remove all React default imports

We're pushing react-jsx in our templates
https://github.com/remix-run/remix/blob/f5a551ee139484f8d821220986a0515f95a69ce2/packages/create-remix/templates/_shared_ts/tsconfig.json#L6

@jacob-ebey Do you have any idea where the problem could be in the failing tests?

Note that our compiler (esbuild) doesn't actually use the react-jsx runtime, it still uses React.createElement, we just automatically include it in .jsx|.tsx files. Might be the reason things are failing?
Do they fail locally?

@ryanflorence This should be fine now I think

authors: MichaelDeBoey ryanflorence


text:
Embed GraalVM configuration in picocli jar

Embed GraalVM configuration in picocli jar as described here: https://medium.com/graalvm/simplifying-native-image-generation-with-maven-plugin-and-embeddable-configuration-d5b283b92f57 and here: https://github.com/graalvm/graalvm-demos/tree/master/native-netty-plot#build-parameters
To equip the picocli library with out-of-the-box native-image compatibility:
META-INF/native-image/info.picocli/picocli/reflection-config.json
META-INF/native-image/info.picocli/picocli/native-image.properties

Won't do: the simplest thing to do is to generate configuration files that contain all necessary settings, rather than having some reflection data reside in the picocli jar and other reflection data in the application jar.

repo: remkop/picocli


text:
Not correctly parsing public suffix for blogspot.com

The tldjs package correctly parsed "subdomain.blogspot.com" as having a public suffix of "blogspot.com".
This tldts package seems to not recognize blogspot.com as a public suffix, as noted in the Public Suffix List.
Steps to reproduce:
const tldjs = require("tldjs");
const tldts = require("tldts");
const input = "subdomain.blogspot.com";
if (tldjs.getPublicSuffix(input) !== tldts.getPublicSuffix(input)) {
  throw new Error(`${input} did not match in both libraries`);
}

Hi @davidbielik and thank you for taking the time to open an issue,
This one is a bit tricky and is the expected behavior (although that might seem counter-intuitive). Let me try to explain. There are two sections in the public suffix list: ICANN domains and private domains. In tldjs both sections will be looked-up by default. At the time we found that this behavior was surprising to a lot of users of the library because it contains suffixes like blogspot.com or us-east-1.amazonaws.com which means that the domain of myapp.us-east-1.amazonaws.com is actually myapp.us-east-1.amazonaws.com whereas a lot of people would have expected amazonaws.com.
Long story short, depending on your use-case you might want to lookup the private section of the list or not and in tldts the default is to not do it (which is somewhat an opinionated choice). You can enable it using an option:
const { parse } = require('tldts');
parse('subdomain.blogspot.com', { allowPrivateDomains: true });
// {
//   domain: 'subdomain.blogspot.com',
//   domainWithoutSuffix: 'subdomain',
//   hostname: 'subdomain.blogspot.com',
//   isIcann: false,
//   isIp: false,
//   isPrivate: true,
//   publicSuffix: 'blogspot.com',
//   subdomain: ''
// }

There are a few other options that one can use to customize the behavior of tldts which you can find documented here: https://github.com/remusao/tldts/tree/master/packages/tldts#api
I hope this helps,
Best,

Very helpful, thanks for clarifying!

authors: davidbielik remusao

repo: remusao/tldts