Help required for the deploy the Osgi Bundles

Hi Jim,
Now I am facing problems with the OsgI bundles.I am applying the plugin sling-bundle and issuing the gradlew clean install.
The Osgi bundle is getting generated locally in the build/libs folder of the project but nothing happens after that.Build is successful but the bundle doesn't get installed or even uploaded.
I am using the defaults except for the install path location.Am I invoking the plugin wrongly?
Please help.
Below is the build.gradle file I am using:
group = 'com.projectname'
description = 'ProjectName Core'
version = '0.1-SNAPSHOT'
configurations {
provided
compile.transitive = true
}
apply plugin: 'java'
apply plugin: 'maven'
apply plugin: 'osgi'
apply plugin: 'sling-bundle'
slingServers.author.installPath = '/apps/projectname/install'
sourceCompatibility = 1.8
targetCompatibility = 1.8
dependencies {
compile group: 'org.slf4j', name: 'slf4j-simple', version:'1.6.4'
compile group: 'org.slf4j', name: 'slf4j-api', version:'1.6.6'
compile group: 'org.apache.felix', name: 'org.osgi.core', version:'1.4.0'
compile group: 'org.apache.felix', name: 'org.apache.felix.scr', version:'1.6.0'
compile group: 'commons-collections', name: 'commons-collections', version:'3.0'
compile group: 'commons-lang', name: 'commons-lang', version:'2.3'
compile group: 'com.google.guava', name: 'guava', version:'14.0'
compile(group: 'org.apache.felix', name: 'org.apache.felix.scr.annotations', version:'1.9.10') {
/* This dependency was originally in the Maven provided scope, but the project was not of type war.
This behavior is not yet supported by Gradle, so this dependency has been converted to a compile dependency.
Please review and delete this closure when resolved. /
}
compile(group: 'org.apache.felix', name: 'org.apache.felix.ipojo', version:'1.8.0') {
/ This dependency was originally in the Maven provided scope, but the project was not of type war.
This behavior is not yet supported by Gradle, so this dependency has been converted to a compile dependency.
Please review and delete this closure when resolved. /
}
compile(group: 'org.osgi', name: 'org.osgi.core', version:'4.2.0') {
/ This dependency was originally in the Maven provided scope, but the project was not of type war.
This behavior is not yet supported by Gradle, so this dependency has been converted to a compile dependency.
Please review and delete this closure when resolved. /
}
compile(group: 'javax.servlet', name: 'servlet-api', version:'2.5') {
/ This dependency was originally in the Maven provided scope, but the project was not of type war.
This behavior is not yet supported by Gradle, so this dependency has been converted to a compile dependency.
Please review and delete this closure when resolved. /
}
compile(group: 'javax.servlet', name: 'jsp-api', version:'2.0') {
/ This dependency was originally in the Maven provided scope, but the project was not of type war.
This behavior is not yet supported by Gradle, so this dependency has been converted to a compile dependency.
Please review and delete this closure when resolved. /
}
compile(group: 'com.adobe.aem', name: 'aem-api', version:'<IP_ADDRESS>') {
/ This dependency was originally in the Maven provided scope, but the project was not of type war.
This behavior is not yet supported by Gradle, so this dependency has been converted to a compile dependency.
Please review and delete this closure when resolved. /
}
compile(group: 'org.apache.sling', name: 'org.apache.sling.jcr.jcr-wrapper', version:'2.0.0') {
/ This dependency was originally in the Maven provided scope, but the project was not of type war.
This behavior is not yet supported by Gradle, so this dependency has been converted to a compile dependency.
Please review and delete this closure when resolved. */
}
}
uploadBundle{
}
showBundle {
}

What does it say when you do the gradlew clean insall -iS?

Executing task ':projectname-core:install' (up-to-date check took 0.0 secs) due to:
Task has not declared any outputs.
[INFO] Installing projectname-core-0.1-SNAPSHOT.jar to F:\Project\0.1-SNAPSHOT\projectname-core-0.1-SNAPSHOT.jar
:projectname-core:install (Thread[main,5,main]) completed. Took 0.114 secs.
I have 3 osgi bundles and one content package.The content package is installing when I tried the workaround you mentioned.But the other 3 bundles which were installed before the latest git changes are not being installed now.The above output is for one of the osgi bundles.It is the same for the other two as well.
I am running the gradlew clean install -iS at the parent folder which encompasses all the 3 osgi bundles and the one content package project.I see the osgi bundles getting generated under the build folder of each of the osgi projects and te zip file gets installed for the content package.The only problem is with the Osgi bundles.

That's caused by a conflict with the maven plugin
// remove "mvn install" since it's not needed and causes a conflict
def installTask = tasks.findByPath('install')
if (installTask != null) tasks.remove(installTask)

Hi Jim,
I do not have the install anymore in all of the modules.I have removed the apply plugin: 'maven' in all my build.gradle files but still the result is same.I am running by giving the command
gradlew clean install..Is there anything else I need to correct?

I realized that removing the apply-plugin:'maven' doesnt even invoke the install in the tasks list iS ouput.I have applied it back but still having the same issue

You have something overriding the install task to copying it to F:\...  There's not anything in the sling-bundle plugin that does anything like that. You need to see if you can identify what is taking over.

Thanks Jim.I will try to find it out.
Can you please point me to the file which has those lines of code def installTask = tasks.findByPath('install')
if (installTask != null) tasks.remove(installTask).?
I was not able to find it in the master branch by doing a file search.

BTW, the reason there's no provided scope in this context is because (unless you're using a "fat jar" plugin) the dependencies aren't going to be packaged into the jar, so it doesn't serve a purpose. At the point where you are packaging dependencies you can exclude them from the configuration.
For example, when using the cqpackage plugin you would do something like
configurations.cq_package {
   exclude group: 'commons-io', module: 'commons-io'
}

to tell it what dependencies to not include when building the zip.

Also are the below plugins required If I use the sling-plugin?
apply plugin: 'osgi'
apply plugin: 'maven'

No file of the project has the tasks.remove(installTask) snippet. I was suggesting you might want to add them to your build file after applying the maven plugin but before applying the sling-bundle plugin to disable the maven install task.
The maven plugin isn't required for anything for sling-bundle. You may have special needs for it, but generally it is best to stay away from it.
If you don't apply the osgi plugin it will be done for you by sling-bundle since it depends on it.

Now I have removed all other modules and ran a build for only one of the Osgi Bundles.Below is the (gradlew clean install -iS) output.Also it printed the list of tasks and there is only one install task.Can you please suggest any other way to debug this?
F:\projectname-core>gradlew clean install -iS
Starting Build
Settings evaluated using empty settings script.
Projects loaded. Root project using build file 'F:\projectname-core\build.gradle'.
Included projects: [root project 'projectname-core']
Evaluating root project 'projectname-core' using build file 'F:\projectname-core\build.gradle'.
Compiling build file 'F:\projectname-core\build.gradle' using StatementExtractingScriptTransformer.
Compiling build file 'F:\projectname-core\build.gradle' using BuildScriptTransformer.
JSON environments file not passed in. Defaulting to localhost environment.
All projects evaluated.
Selected primary task 'clean' from project :
Selected primary task 'install' from project :
Tasks to be executed: [task ':clean', task ':compileJava', task ':processResources', task ':classes', task ':jar', task ':install']
:clean (Thread[main,5,main]) started.
:clean
Executing task ':clean' (up-to-date check took 0.001 secs) due to:
Task has not declared any outputs.
:clean UP-TO-DATE
:clean (Thread[main,5,main]) completed. Took 0.054 secs.
:compileJava (Thread[main,5,main]) started.
:compileJava
Executing task ':compileJava' (up-to-date check took 1.599 secs) due to:
No history is available.
All input files are considered out-of-date for incremental task ':compileJava'.
Compiling with JDK Java compiler API.
:compileJava (Thread[main,5,main]) completed. Took 2.54 secs.
:processResources (Thread[main,5,main]) started.
:processResources
Executing task ':processResources' (up-to-date check took 0.005 secs) due to:
No history is available.
:processResources (Thread[main,5,main]) completed. Took 0.039 secs.
:classes (Thread[main,5,main]) started.
:classes
Skipping task ':classes' as it has no actions.
:classes (Thread[main,5,main]) completed. Took 0.012 secs.
:jar (Thread[main,5,main]) started.
:jar
Executing task ':jar' (up-to-date check took 0.257 secs) due to:
No history is available.
:jar (Thread[main,5,main]) completed. Took 0.431 secs.
:install (Thread[main,5,main]) started.
:install
Executing task ':install' (up-to-date check took 0.0 secs) due to:
Task has not declared any outputs.
Publishing configuration: configuration ':archives'
Publishing to org.gradle.api.publication.maven.internal.ant.BaseMavenInstaller@7910f355
[INFO] Installing F:\projectname-core\build\libs\projectname-core-0.1-SNAPSHOT.jar to F:\MavenRepos\com\projectname\projectname-core
:install (Thread[main,5,main]) completed. Took 0.434 secs.
BUILD SUCCESSFUL
Total time: 9.707 secs

Ok so I have come to a point where if I remove the apply plugin: 'maven' from build.gradle file the build fails with the message:
org.gradle.execution.TaskSelectionException: Task 'install' not found in root project 'projectname-core'.
So I am assuming all this while the install command is being executed from the maven plugin in the build.gradle file.So which task  in the sling-bundle  plugin should I be invoking now for executing the install command  now?
My modified build.gradle file for the single Osgi module:
group = 'com.projectname'
description = 'projectname Core'
version = '0.1-SNAPSHOT'
buildscript {
repositories {
jcenter()
maven {
url "http://dl.bintray.com/twcable/aem"
}
}
dependencies {
    classpath "com.twcable.gradle:cq-gradle-plugins:3.0.1"
}

}
allprojects  {
repositories {
 mavenLocal()
maven { url "http://repo.adobe.com/nexus/content/groups/public/" }
maven { url "http://sd1pgo01lx.projectnamedirect.com:8081/artifactory/simple/libs-release-local" }
maven { url "http://repo.maven.apache.org/maven2" }

}
}
configurations {
provided
compile.transitive = true
}
apply plugin: 'java'
apply plugin: 'osgi'
apply plugin: 'sling-bundle'
slingServers.author.installPath = '/apps/projectname/install'
sourceCompatibility = 1.8
targetCompatibility = 1.8
dependencies {
compile group: 'org.slf4j', name: 'slf4j-simple', version:'1.6.4'
compile group: 'org.slf4j', name: 'slf4j-api', version:'1.6.6'
compile group: 'org.apache.felix', name: 'org.osgi.core', version:'1.4.0'
compile group: 'org.apache.felix', name: 'org.apache.felix.scr', version:'1.6.0'
compile group: 'commons-collections', name: 'commons-collections', version:'3.0'
compile group: 'commons-lang', name: 'commons-lang', version:'2.3'
compile group: 'com.google.guava', name: 'guava', version:'14.0'
compile(group: 'org.apache.felix', name: 'org.apache.felix.scr.annotations', version:'1.9.10') {
/* This dependency was originally in the Maven provided scope, but the project was not of type war.
This behavior is not yet supported by Gradle, so this dependency has been converted to a compile dependency.
Please review and delete this closure when resolved. /
}
compile(group: 'org.apache.felix', name: 'org.apache.felix.ipojo', version:'1.8.0') {
/ This dependency was originally in the Maven provided scope, but the project was not of type war.
This behavior is not yet supported by Gradle, so this dependency has been converted to a compile dependency.
Please review and delete this closure when resolved. /
}
compile(group: 'org.osgi', name: 'org.osgi.core', version:'4.2.0') {
/ This dependency was originally in the Maven provided scope, but the project was not of type war.
This behavior is not yet supported by Gradle, so this dependency has been converted to a compile dependency.
Please review and delete this closure when resolved. /
}
compile(group: 'javax.servlet', name: 'servlet-api', version:'2.5') {
/ This dependency was originally in the Maven provided scope, but the project was not of type war.
This behavior is not yet supported by Gradle, so this dependency has been converted to a compile dependency.
Please review and delete this closure when resolved. /
}
compile(group: 'javax.servlet', name: 'jsp-api', version:'2.0') {
/ This dependency was originally in the Maven provided scope, but the project was not of type war.
This behavior is not yet supported by Gradle, so this dependency has been converted to a compile dependency.
Please review and delete this closure when resolved. /
}
compile(group: 'com.adobe.aem', name: 'aem-api', version:'<IP_ADDRESS>') {
/ This dependency was originally in the Maven provided scope, but the project was not of type war.
This behavior is not yet supported by Gradle, so this dependency has been converted to a compile dependency.
Please review and delete this closure when resolved. /
}
compile(group: 'org.apache.sling', name: 'org.apache.sling.jcr.jcr-wrapper', version:'2.0.0') {
/ This dependency was originally in the Maven provided scope, but the project was not of type war.
This behavior is not yet supported by Gradle, so this dependency has been converted to a compile dependency.
Please review and delete this closure when resolved. */
}
compile(group: 'com.googlecode.jmockit', name: 'jmockit', version:'1.7')
compile(group: 'junit', name: 'junit', version:'4.12')
compile(group: 'org.codehaus.jackson', name: 'jackson-mapper-asl', version:'1.9.13')
}
uploadBundle{
}
showBundle {
}

:panda_face: There is no install task for sling-bundle. However there is uploadBundle...

Oh ok.
Can you please help in letting me know as to how should I install the generated Osgi bundle to CQ server?I do have the uploadBundle task in my gradle build file
like gradlew clean ?

oh ok.Now when I invoke the command gradlew uploadBundle,it fails with error:
Could not find id for com.projectname.core.I believe I need to change something in meta files?

It failed because the guava jar which gets embedded is missing in the plugin generated osgi bundle.How can I embed the missing jar to the generated osgi bundle?

"How can I embed the missing jar to the generated osgi bundle?"
Short answer: You don't. That's what the CQ Package Manager is for. Use the "cqpackage" plugin.
Longer answer: You can create a "fat jar", but the reasons for and against doing so, including how, are beyond scope...

FWIW, starting in AEM 6.0, Google Guava is included in AEM and will likely give you trouble unless you really know what you're doing. Use the v15 that AEM6 comes with.

oh ok.So if I use the cqpackage plugin the build fails stating that the contentSrc path is wrong since I do not have jcr_root like structure for this osGi bundle module.I have src/main/java and also I observed that OSGI-INF folder doesn't get generated.

You'd need at least some content if for nothing else than for the META-INF/vault information.
OSGI-INF doesn't get generated inside the bundle when you're using the scr plugin?

When I apply the scr plugin here is the error:
Execution failed for task ':projectname-core:processScrAnnotations'.

java.lang.IllegalArgumentException (no error message)

Don't forget to run Gradle with the -iS flag so you can see what's going on....

Sorry Jim,Yes I did do that but pasted only the topmost message.Here is the complete stack trace:

Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':projectname-core:processScrAnnotations'.
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:69)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:46)
at org.gradle.api.internal.tasks.execution.PostExecutionAnalysisTaskExecuter.execute(PostExecutionAnalysisTaskExecuter.jav
at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:64)
at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58)
at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:
at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52)
at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:53)
at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
at org.gradle.api.internal.AbstractTask.executeWithoutThrowingTaskFailure(AbstractTask.java:305)
at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.executeTask(AbstractTaskPlanExecutor.java:79
at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.processTask(AbstractTaskPlanExecutor.java:63
at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.run(AbstractTaskPlanExecutor.java:51)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor.process(DefaultTaskPlanExecutor.java:23)
at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter.execute(DefaultTaskGraphExecuter.java:88)
at org.gradle.execution.SelectedTaskExecutionAction.execute(SelectedTaskExecutionAction.java:29)
at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:62)
at org.gradle.execution.DefaultBuildExecuter.access$200(DefaultBuildExecuter.java:23)
at org.gradle.execution.DefaultBuildExecuter$2.proceed(DefaultBuildExecuter.java:68)
at org.gradle.execution.DryRunBuildExecutionAction.execute(DryRunBuildExecutionAction.java:32)
at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:62)
at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:55)
at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:149)
at org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:106)
at org.gradle.initialization.DefaultGradleLauncher.run(DefaultGradleLauncher.java:86)
at org.gradle.launcher.exec.InProcessBuildActionExecuter$DefaultBuildController.run(InProcessBuildActionExecuter.java:80)
at org.gradle.launcher.cli.ExecuteBuildAction.run(ExecuteBuildAction.java:33)
at org.gradle.launcher.cli.ExecuteBuildAction.run(ExecuteBuildAction.java:24)
at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:36)
at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:26)
at org.gradle.launcher.cli.RunBuildAction.run(RunBuildAction.java:51)
at org.gradle.internal.Actions$RunnableActionAdapter.execute(Actions.java:171)
at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:237)
at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:210)
at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:35)
at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24)
at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:206)
at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:169)
at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33)
at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22)
at org.gradle.launcher.Main.doAction(Main.java:33)
at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:54)
at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:35)
at org.gradle.launcher.GradleMain.main(GradleMain.java:23)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.gradle.wrapper.BootstrapMainStarter.start(BootstrapMainStarter.java:30)
at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:127)
at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:56)
Caused by: java.lang.IllegalArgumentException
at org.objectweb.asm.ClassReader.(Unknown Source)
at org.objectweb.asm.ClassReader.(Unknown Source)
at org.objectweb.asm.ClassReader.(Unknown Source)
at org.apache.felix.scrplugin.helper.ClassScanner.processClass(ClassScanner.java:172)
at org.apache.felix.scrplugin.helper.ClassScanner.scanSources(ClassScanner.java:143)
at org.apache.felix.scrplugin.SCRDescriptorGenerator.execute(SCRDescriptorGenerator.java:149)
at org.apache.felix.scrplugin.ant.SCRDescriptorTask.execute(SCRDescriptorTask.java:129)
at org.apache.felix.scrplugin.ant.SCRDescriptorTask$execute.call(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:112)
at com.twcable.gradle.scr.ScrPlugin.configureAction(ScrPlugin.groovy:77)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:324)
at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:368)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1016)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:807)
at groovy.lang.GroovyObjectSupport.invokeMethod(GroovyObjectSupport.java:44)
at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeOnDelegationObjects(ClosureMetaClass.java:430)
at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:355)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1016)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.callCurrent(PogoMetaClassSite.java:66)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:49)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:133)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:141)
at com.twcable.gradle.scr.ScrPlugin$_addScrTask_closure1_closure4.doCall(ScrPlugin.groovy:59)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:324)
at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:278)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1016)
at groovy.lang.Closure.call(Closure.java:423)
at groovy.lang.Closure.call(Closure.java:439)
at org.gradle.api.internal.AbstractTask$ClosureTaskAction.execute(AbstractTask.java:548)
at org.gradle.api.internal.AbstractTask$ClosureTaskAction.execute(AbstractTask.java:529)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:80)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:61)
... 55 more

These are the plugins am using in that order:
apply plugin: 'java'
apply plugin: 'scr'
apply plugin: 'osgi'
apply plugin: 'cqpackage'
apply plugin: 'sling-bundle'
and also I had to create a dummy META-INF folder under the projectname-core/src/main/ in order to use the cqpackage plugin.Is there a way that I can indicate to the plugin that I am actually building a OSGI bundle and not a content package?

So currently I removed the guava dependency and trying to build an OSGI jar but it is failing with same error however the difference now is that I can see my projectname-core bundle in the OSGI bundle console.That is probably because it is uninstalling and then checking for the bundle.Please find below log:
Uninstalling com.projectname.core
Removing com.projectname.core
:projectname-core:uploadBundle FAILED
:projectname-core:uploadBundle (Thread[main,5,main]) completed. Took 1.645 secs.
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':projectname-core:uploadBundle'.

Problem getting bundle location from http://localhost:4502/system/console/bundles - 404:

So I invoked the showBundle task after the uploadbundle and here  is the output:
{"status":"Bundle information: 435 bundles in total - all 435 bundles active.","s":[435,427,8,0,0],"data":[{"id":583,"name":"projectname-core","...............

"Is there a way that I can indicate to the plugin that I am actually building a OSGI bundle and not a content package?"  Yes, don't include the 'cqpackage' plugin. Again, bundles and packages serve different purposes.
What command are you using to install the bundle? Just a simple ./gradlew uploadBundle?

Yes Jim.
I am using gradlew uploadBundle -iS
Below is the list of plugins snippet from my build gradle file:
apply plugin: 'java'
apply plugin: 'osgi'
apply plugin: 'sling-bundle'
slingServers.author.installPath = '/apps/projectname/install'
sourceCompatibility = 1.8
targetCompatibility = 1.8
I am still getting a 404 and please find the trace of events leading to the error:I am not able to understand as to why after uninstalling bundle,the plugin searches for the projectname.core bundle and fails on execution.
Executing task ':projectname-core:uploadBundle' (up-to-date check took 0.001 secs) due to:
Task has not declared any outputs.
Uninstalling com.projectname.core
Removing com.projectname.core
:projectname-core:uploadBundle FAILED
:projectname-core:uploadBundle (Thread[main,5,main]) completed. Took 1.626 secs.
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':projectname-core:uploadBundle'.

Problem getting bundle location from http://localhost:4502/system/console/bundles - 404:

Just to level-set: This is happening with version '3.0.2' of the plugins?

Sorry Jim.What is the name of the plugin version  you  are referring to here?
I can find that and post it if you can help me with the name.

So I changed it to classpath 'com.twcable.gradle:cq-gradle-plugins:3.0.2' and still the same error

And sometimes I get a build failure with while trying to upload the bundle generated in the build/libs folder.
Caused by: java.lang.IllegalStateException: Could not find id for com.projectName.core
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at com.twcable.gradle.sling.osgi.SlingOsgiBundle.resetFelixId(SlingOsgiBundle.groovy:355)
at com.twcable.gradle.sling.osgi.SlingOsgiBundle$resetFelixId$3.callCurrent(Unknown Source)
at com.twcable.gradle.sling.osgi.SlingOsgiBundle.uploadBundle(SlingOsgiBundle.groovy:300)
at com.twcable.gradle.sling.osgi.SlingOsgiBundle$uploadBundle$0.call(Unknown Source)
at com.twcable.gradle.sling.osgi.SlingBundlePlugin$_uploadBundle_closure8_closure19_closure20.doCall(SlingBundlePlugin.groovy:172)

Is your bundle's id "com.projectName.core"? Are you setting it explicitly in MANIFEST.MF?

I am not setting it in MANIFEST explicitly.The plugin is generating it dynamically and in the generated MANIFEST I have the following:
Bundle-SymbolicName: com.projectName.core.
Is there another place I need to set this explicitly?


suggest menu bug

We have written the neede
Type: Bug
I use Kivy which is a Python library. In kivy, we have to import every function/class individually.In PYCHARM whenever I hover on undefined function of Kivy it shows suggestions to import that but when I use Kivy in VSCODE it doesn't show import suggestions of KIVY in suggestion menu instead it shows import suggestions of other modules/libraries of Pyhton.
I also used some KIVY extensions but that doesn't worked.
 Please paste.

/extPython

It looks like this is caused by the Python extension. Please file the issue to the Python extension repository. Make sure to check their issue reporting template and provide them relevant information such as the extension version you're using. See also our issue reporting guidelines for more information.
Happy Coding!


Update-Oracle-Manager-Base-Mainnet

hey @noisekit hoping to send this on friday, will confirm today with respect to kwenta readiness


CodeGenOpenCL : expect calling_conv equals CallingConv::kDeviceKernelLaunch

when I Compile PyTorch Models  demo in https://tvm.apache.org/docs/tutorials/frontend/from_pytorch.html#sphx-glr-tutorials-frontend-from-pytorch-py
i set the configure below
target = "opencl"
target_host = "opencl"
ctx = tvm.gpu(0)
there occurs the error below:
An internal invariant violated during the execution of TVM
Check failed: calling_conv == CallingConv::kDeviceKernelLaunch ==false: CodeGenOpenCL:expect calling_conv equals CallingConv::kDeviceKernelLaunch

Thanks @ctlinglingliu . please open a new thread on https://discuss.tvm.apache.org/ for followup Qs, you need to set target_host to be llvm


Upgrade to Node 20

GitHub has started deprecating Node 16, and using this action now outputs a warning to update it to Node 20.
It feels like it should be a simple change for this action, maybe just a matter of changing the requirement in the YAML file.

Note that actions/setup-node@v4 already did this so it would be good to catch up with them.


Release new models

Can we merge this and then make an announcement (blogpost/tweet) about this update?
Originally posted by @kjappelbaum in https://github.com/lamalab-org/chem-bench/issues/356#issuecomment-2172381034

[ ] Llama-3 family @MrtinoRG @n0w0f
[ ] GPT-4o @sreekanth221998
[ ] Claude-3.5 Sonnet @sreekanth221998
[ ] Gemma-7b @n0w0f
[ ] DeepSeek2 @sreekanth221998
[ ] Phi-3 @n0w0f

@n0w0f thanks for tracking this!

Very excited to see how the new models perform!

@n0w0f I think you forgot about Cohere models :)

The Command-R family looks like specifically optmized for tool use and the Aya ones on being multi-lingual

yeah, for the command model we discussed that it might be a candidate for the toolformer setup we tried

Tie again with the newer models on physical chemistry !!


Fastnlight: Watch Hulk24.com

Fastnlight requests the watch of the watch_keyword Hulk24\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Hulk24\.com has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Added Wikipathways and other changes

Branch merged with playbook CFDe main before making a pull request.
\components\core\input\scored\index.tsx - imported Variant and RegulatoryElement entities in order to creete ScoredVariants and ScoredRegulatoryElement
\components\filters\index.tsx - added imports for Variant(Set, Term and Scored) and RegulatoryElements (Set, Term and Scored). Alterd methods TopKScoredT, SelectScoredT, SetFromScoredT, ReduceMultiScoredT
\components\service\ctd\input.tsx - renaming of lables and descriptions
\components\service\ctd\service.tsx - merge the whole content as is, all current changes from CFDE main merged
\components\service\regulatoryElementInfo\index.tsx - renaming of a single label
\components\service\variantinfo\index.tsx - renaming of lables and descriptions, added download (json) options fof the views, added code changes in the nodes GetVarinatSetAlleleSpecificEvidence and GetVarinatSetXQTLEvidence

Squash merge in b610e1b83fc4e23742c253c9083ca1730b42a57c
Please rebase


ANSI 256 as #3-tuples

Docs says "there is currently no syntax for Color::Ansi256 because I couldn’t come up with a nice syntax and I never used these ansi colors…)". I do need those ones.
What about just using a #123 syntax? If RGB should always be 6-tuple strings, then there is no ambiguity with ANSI's 256 3-tuple.
The meaning should be straigthforward, but may collides in users mind with CSS' short 3-tuple RGB (for which #fff is a valid shortcut for #ffffff).
Alternatively, any other prefix may be used, like @, which reminds the A of ANSI.

Just so I don't misunderstand: the 123 in your example would be a decimal number between #0 and #255? Or is it three separate components as you said "3-tuple"? That wouldn't make a lot of sense according to Wikipedia, right? Because (a) how to split 8 bit into 3 components, and (b) the individual components wouldn't really have a meaning on their own like in RGB hex codes, right?
I also immediately thought it would cause confusion with people used to short hex codes in CSS. Thus I would prefer another prefix. Apart from @, $, %, ~ would also be fine I guess. But yeah, why not @ :shrug:

Yes, I was thinking of "three digits", between 001 and 255. That would be
@.", @."<EMAIL_ADDRESS>Le dim. 13 nov. 2022 à 10:01, Lukas Kalbertodt @.***> a
écrit :

Just so I don't misunderstand: the 123 in your example would be a decimal
number between #0 and #255? Or is it three separate components as you
said "3-tuple"? That wouldn't make a lot of sense according to Wikipedia
https://en.wikipedia.org/wiki/ANSI_escape_code#8-bit, right? Because
(a) how to split 8 bit into 3 components, and (b) the individual components
wouldn't really have a meaning on their own like in RGB hex codes, right?
I also immediately thought it would cause confusion with people used to
short hex codes in CSS. Thus I would prefer another prefix. Apart from @,
$, %, ~ would also be fine I guess. But yeah, why not @ 🤷
—
Reply to this email directly, view it on GitHub
https://github.com/LukasKalbertodt/bunt/issues/26#issuecomment-1312677808,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACFSUOTZCSFQBVC2MRKBZLWICU6RANCNFSM6AAAAAAR6HPS2Y
.
You are receiving this because you authored the thread.Message ID:
@.***>

Woopsie! Because you replied via mail, GitHub detected those the things around @ as email addresses and censored them. Could you write that again via GitHub UI? ^_^

Now that's a fun behavior.
I was thinking of "three digits", between 001 and 255. That would be "@001", "@012", "@123", "@255", etc.

Any specific reason you would force users to add leading 0s? The syntax would be unambiguous even for @12, right?

Looked more consistent to me, comparing with RGB hex. But it's probably better to just use short numbers, given that all docs on ANSI present them without leading zeros.

Okay yeah, I would also not force leading zeros I think.
I guess then we have a plan.  Do you wanna give it a try and prepare a PR? Otherwise I might do it in the near future -- no promises tho!

I still have to learn Rust and use it to port a project (using bunt ;), so it's going to take some time for me as well.

Then I will have a stab at it I guess! I hope you're enjoying Rust so far ;-)

Fixed in fc63556d96c89fee12d3e12a19f2ced35519ddd2 and released as v0.2.8


fluentd_output_status_num_errors is not reseting to zero after a successful retry

Check CONTRIBUTING guideline first and here is the list to help us investigate the problem.

fluentd or td-agent version  :  3.2.0
Environment information,  Docker container running on Centos 7.
Your configuration

td-agent.conf
<match prod.**>
 @type copy
 <store>
   @type forward
   <server>
     name <target server>
     host <target server ip>
     port 24224
   </server>
   <buffer>
     flush_interval 5s
     flush_thread_count 4
   </buffer>
 </store>
 <store>
   @type prometheus
   <metric>
     name fluentd_output_status_num_records_total
     type counter
     desc The total number of outgoing records
     <labels>
       tag ${tag}
       hostname ${hostname}
     </labels>
   </metric>
 </store>
</match>

### PROMETHEUS-PLUGIN OUTPUT
<source>
  @type prometheus
  bind <IP_ADDRESS>
  port 9010
  metrics_path /metrics
</source>
<source>
  @type prometheus_output_monitor
  interval 10
</source>

Your problem explanation. If you have an error logs, write it together.
'fluentd_output_status_num_errors' is not reseting to zero after a successful retry and this leads to a false active alerts in Prometheus. We have an alert defined if this remains non-zero for longer time.

fluentd_output_status_num_errors{job="tdagents"} > 0
I already read this  issue  [https://github.com/fluent/fluentd/issues/1379] but it looks to be existing in older version and has already been addressed however this exists in the latest version (td-agent-3.2.0) too.
Can you please look into this issue ?

prometheus plugin doesn't provide a metric for @retry.steps?

Do you want to remove fluentd_output_status_retry_count from metrics?
prometheus plugin issue?

So maybe one question why it is then of type gauge, when it is behaving like counter?


Added JDBC tracing section in Java Observability

Initial draft about enabling JDBC tracing in the Hana JDBC driver for CAP Java applications.

Hi @renejeglinsky, as parts of this documentation is rather CAP-unspecific (especially tracing activation via command line), I'm not sure if this the right part of our Capire to add this information to.
As Marc said, this should actually be in the HANA JDBC driver documentation, but that documentation is lacking severely in details, and users will surely contact us for guidance.
What do you think, should it better be placed elsewhere?

Hi @davidhunglam ,
if we can't link to docs that we deem appropriate, then it's fine to have the docs in capire. Especially in this case, where it's not too much.
Anyway we could provide feedback to the HANA colleagues about what we would expect. And if they can provide those docs, we can then remove it here and set just a link. Would you/Marc like to give feedback?

Hi @davidhunglam , if we can't link to docs that we deem appropriate, then it's fine to have the docs in capire. Especially in this case, where it's not too much.
Anyway we could provide feedback to the HANA colleagues about what we would expect. And if they can provide those docs, we can then remove it here and set just a link. Would you/Marc like to give feedback?

Hi @renejeglinsky, we've talked internally about it, and we've decided that our Capire might be the better place for the documentation. The Hana driver documentation is kept strictly environment agnostic, so they don't really care about where the driver runs.

Hi @davidhunglam , if we can't link to docs that we deem appropriate, then it's fine to have the docs in capire. Especially in this case, where it's not too much.
Anyway we could provide feedback to the HANA colleagues about what we would expect. And if they can provide those docs, we can then remove it here and set just a link. Would you/Marc like to give feedback?

Hi @renejeglinsky, we've talked internally about it, and we've decided that our Capire might be the better place for the documentation. The Hana driver documentation is kept strictly environment agnostic, so they don't really care about where the driver runs.

Thanks! :)

Are we fine with the current proposal?

@smahati Could you review this before the next release?


Develop

Codecov Report

Merging #41 (d5a07a0) into main (5b6d009) will decrease coverage by 1.97%.
The diff coverage is 96.85%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #41      +/-   ##
==========================================
- Coverage   99.27%   97.30%   -1.98%
==========================================
  Files          18       33      +15
  Lines         277      593     +316
==========================================
+ Hits          275      577     +302
- Misses          2       16      +14

Impacted Files
Coverage Δ

...ffleStack/EnvironmentValues/ShuffleAnimation.swift
100.00% <ø> (ø)

...huffleStack/EnvironmentValues/ShuffleContext.swift
100.00% <ø> (ø)

...huffleStack/EnvironmentValues/ShuffleDiabled.swift
100.00% <ø> (ø)

.../ShuffleStack/EnvironmentValues/ShuffleStyle.swift
100.00% <ø> (ø)

...leStack/EnvironmentValues/ShuffleTranslation.swift
100.00% <ø> (ø)

...huffleStack/EnvironmentValues/ShuffleTrigger.swift
100.00% <ø> (ø)

...ces/CarouselStack/View/CarouselStack+Gesture.swift
45.45% <45.45%> (ø)

Sources/CarouselStack/View/CarouselStack.swift
97.26% <97.26%> (ø)

...selStack/EnvironmentValues/CarouselAnimation.swift
100.00% <100.00%> (ø)

...ouselStack/EnvironmentValues/CarouselContext.swift
100.00% <100.00%> (ø)

... and 23 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 5b6d009...d5a07a0. Read the comment docs.


⚠ Bofrost.lu has degraded performance

In f61988f, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2322 ms

Resolved: Bofrost.lu performance has improved in 1c79aaf after 20 minutes.


Want to add fav icon in every page of title bar

Sure! You can work on it!

i would like to work on this issue under JWOC

You can work only on 1 issue at a time, @Monishparameswaran. Once you complete an issue and submit a PR for the same, the next issue will be assigned to you.

I want to work on this issue under JWOC so please assign it to me

Sure! You can work on it, @AimanSh123.
As it is an easy issue, a PR for the same is expected in a day. If not, the issue will be assigned to the next participant.

Hey @SSHSRN , I want to work on this issue under JWOC, Can you please assign it to me.

@SSHSRN I have added fav icon on every page


Points with annotation context don't show information about their annotation context on hover/select

Easy to reprodoce in mp_pose demo.
There should be information about how the point was labled.
Also, on select there should be a link to the annotation context. Note that this works fine on the image which also has an annotation context

Looks like this got fixed meanwhile!


chore(deps): upgrade compiler dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-compiler-dependencies-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2712

Questions ?
Please refer to the Backport tool documentation


⚠ Bofrost.es has degraded performance

In 4c5197b, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1666 ms

Resolved: Bofrost.es performance has improved in 02e8172 after 6 minutes.


github failure in get

A GET request to Github failed with a 500. The log entry is
ERROR 2024-11-22T10:38:06Z github get server failure code=500 status=500 Internal Server Error body=[]

This apparently happened while posting an issue comment:
ERROR 2024-11-22T10:37:42Z reporting err=post issue comment failed issue=70521: 500 Internal Server Error

Although it's strange that the time of the second log entry is earlier.
Although we failed to make a related-issues post, it's not worth retrying because the issue is closed (golang/go#70521).
If we did want to retry, we'd have a problem because the action log already contains a failed entry.
See #30.

This issue is for documentation purposes only. Closing it now.


Fix lint error: missing type for the implementations

I'm also using this PR to test the GCB Trigger integration, as I realized the build failed on the main branch.

/gcbrun


Reopen #24 (method to clear page items)

Please merge #24, currently I have to use reflections in order to clear existing page items:
Field list = PaginatedGui.class.getDeclaredField("pageItems");
list.setAccessible(true);
ArrayList<GuiItem> actualList = (ArrayList<GuiItem>) list.get(lobbySwitcherGui);
actualList.clear();
list.set(lobbySwitcherGui, actualList);
Would be a nice feature

This can be closed as the a new pull request which fixes this has been merged.

Thanks!


schema tests

Description
Add tests for the schema checking server error, response code, content type, response schema, and response headers against the proxy schema itself.
Changes
Add a tests.py file, requirements.txt, and workflow.yml.
Related Issues
https://github.com/threefoldtech/tfgrid-sdk-go/issues/51
Checklist

[x] Tests included
[ ] Build pass
[ ] Documentation
[ ] Code format and docstring

Good job ya @A-Harby
I have some comments, as far as I understood schemathesis reads the openapi spec and try to make each call to the server.

we have more live proxy servers than the ones running on *.grid.tf and i don't see a need to test them all actually tests will fail cause it reads the specs from the pushed code which may contains some changes not deployed yet on the running server, so i guess it will be enough to test on push/pull-request for the server running from the code itself. what do you think?
also, i see there is already an action from schemathsis themselves https://github.com/schemathesis/action, did you consider using it?

we have more live proxy servers than the ones running on *.grid.tf and i don't see a need to test them all actually tests will fail cause it reads the specs from the pushed code which may contains some changes not deployed yet on the running server, so i guess it will be enough to test on push/pull-request for the server running from the code itself. what do you think?

I added the trigger on the PR on the main branch and just left the manual trigger for the test run on every network (to make sure everything is working fine).

also, i see there is already an action from schemathsis themselves https://github.com/schemathesis/action, did you consider using it?

That does need a subscription, and running the coding does pretty much the same.

correct me if I got it wrong, schematest checks the openapi spec file and do all the possible requests to the target servers.
it is frequently that we update these specs like adding new filters or changing the response schemes.
the code will read the specs from the pushed code - which will contain the changes - but will try to make the request to the running server - which doesn't have the changes yet - so it will fail.
isn't it enough to run the test once on the push/pr? if we do need to run it on all the servers can we get the specs for each server running? maybe from https://gridproxy.dev.grid.tf/swagger/doc.json instead of reading it from the codebase

isn't it enough to run the test once on the push/pr? if we do need to run it on all the servers can we get the specs for each server running? maybe from https://gridproxy.dev.grid.tf/swagger/doc.json instead of reading it from the codebase

I did that in 1811cac, the PR should be ready for review.

code looks good to me, but the test fails due to some needed updates in the schema. we need to take care of this before merge this pr.
i will try to resolve them or you @A-Harby are very welcome to help :D


Restore ability to use tempfile kwargs other than dir

The changes in #38 broke the ability to use prefix, suffix and bufsize arguments when creating the tempfile. This  pull request restores the ability, and is intended to fix #39

I have updated get_fileobject to take suffix, prefix, dir, **kwargs - buffering is destined for io.open so it gets left in kwargs. The bufsize handling was just an artifact of using tempfile.NamedTemporaryFile which has a bufsize argument (like os.fdopen) argument while open and io.open both call the argument buffering

released 1.3.0, have fun :)

Awesome, thanks! This project has saved me from having to figure this all out myself :)


Load test iot simulator

Purpose
Some fixes after testing the e2e together
Does this introduce a breaking change?

[X] Yes
[ ] No

Author pre-publish checklist:

[ ] Added test to prove my fix is effective or new feature works
[X] No PII in logs
[X] Made corresponding changes to the documentation

Can we have more of a description in the title?
Also can you detail which issues are fixed in the PR comments?

Can we have more of a description in the title?
Also can you detail which issues are fixed in the PR comments?

Can we have more of a description in the title?
Also can you detail which issues are fixed in the PR comments?

ah yeah sorry about that, let me add more detail :D

@jmostella I've updated this PR with a brief readme. Can you help me review it again? thanks!


Use scientific notion for values that are too small for current precision setting

Only for "value" variable in live monitoring

https://github.com/ChannelFinder/pvinfo/pull/27


Added support for GitHub using AWS CodeStarSourceConnection

Added parameters for GitHub support using AWS CodeStarSourceConnection
Feature or Bugfix

Feature

Detail

Added support for using GitHub as source with CodeStar by implementing the AWS CodeStarSourceConnection.
Replaced the use of PAT Token with a more secure method using CodeStar connections.
This is the recommended method. See: https://docs.aws.amazon.com/cdk/api/v2/python/aws_cdk.pipelines/CodePipelineSource.html

Relates

Link to the CodeStar connection setup documentation: CodeStar Connection Documentation
Link to the relevant documentation update that should be updated by someone: AWS DataAll Deployment Documentation

Security
Please answer the questions below briefly where applicable, or write N/A. Based on
OWASP 10.

Does this PR introduce or modify any input fields or queries - this includes fetching data from storage outside the application (e.g. a database, an S3 bucket)?

Yes, this PR introduces support for inputting CodeStarSourceConnection ARN.

Is the input sanitized?

Yes, the input is properly sanitized before being processed.

What precautions are you taking before deserializing the data you consume?

We ensure that data is properly validated and sanitized before any deserialization takes place.

Is injection prevented by parameterizing queries?

Injection is prevented by utilizing parameterized queries.

Have you ensured no eval or similar functions are used?

We have ensured that no eval or similar functions are used.

Does this PR introduce any functionality or component that requires authorization?

Yes, this PR introduces a new way to authenticate with GitHub using CodeStar connections.

How have you ensured it respects the existing AuthN/AuthZ mechanisms?

We have ensured that the existing authentication and authorization mechanisms are respected.

Are you logging failed auth attempts?

N/A

Are you using or adding any cryptographic features?

No, this PR does not involve the use or addition of any cryptographic features.

Do you use a standard proven implementation?

Yes

Are the used keys controlled by the customer? Where are they stored?

No keys are used in this context.

Are you introducing any new policies/roles/users?

No new policies, roles, or users are being introduced with this PR.

Have you used the least-privilege principle? How?

We have strictly followed the principle of least privilege in the implementation of this feature.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Hi @asifma thanks for directly opening a PR :) I have read the docs and I agree with the general purpose of the PR. I will add some comments and we will sync internally to merge it in the following weeks.

@asifma is using CodeStar connections in AWS. In addition I tested that the CICD pipeline using CodeCommit is unnafected, that introducing a bad connection_arn throws an exception and that we can migrate from a CodeCommit deployment to a CodeStar connection deployment:
Error from bad input:

Successfully updated!


Retrieving url for thumbnail using standalone

Hi
I am trying to retrieve the thumbnail url.
Currently the standalone is saving the url to my database as /photos/1/filename.jpg but it is also saving a thumbnail as photos/1/thumb/filename.jpg.
Is there a way for me access the full size image url and the thumbnail url so that I can save both to the DB ?
Thanks very much

Try if the following works.
$lfm_helper = new \Unisharp\Laravelfilemanager\LfmHelper();
$full_file_path = ; // get this from db
$thumb_url = $lfm_helper->getThumbUrl($full_file_path);

Thank you very much

I have included the Class but I am getting the error
FatalThrowableError in PostsController.php line 83:
Class 'Unisharp\Laravelfilemanager\LfmHelper' not found

Sorry, LfmHelper's'.

np, it is still throwing the Class not found error :(
I am using the latest version of 5.2 could that be the issue?
I am also using 1.7 not 1.7.1

Updated : Unisharp\Laravelfilemanager\traits\LfmHelpers.

Updating to latest version is also suggested.

Thank you for the help but it still threw the same type of error.
I am new to using a file manager in Laravel so I am probably doing something wrong :)
I am still learning Laravel even though I have built a few blogs :)
I did find a quick fix that will allow me to get the full-size img url that is submited by the create form and append the "thumb" to the url.
Hopefully, this will help others, I will turn this into a function in a helpers.php file later but currently it will allow me to save it to the database should I need to :)
Thank you
`$img = $request['photo_path'];
$img_thumb = explode('/', $img);
$directory = dirname($img);
$thumbnail = $directory . '/thumb/' . end($img_thumb);
$input['photo_thumb'] = $thumbnail;`

You are welcome.

The getThumbUrl method from the trait is not accurately updated, as it is grabbing the thumbs from the wrong directory (not the thumb immediately next to the original file).

Unisharp\Laravelfilemanager\traits\LfmHelpers

Class 'Unisharp\Laravelfilemanager\traits\LfmHelpers' not found


v0.2.5

Description
Minor update that now includes the insertion codes in the PandasPdb.amino3to1 function to avoid potential bugs where relevant amino acids could be skipped
Related issues or pull requests
Fixes #58

Pull Request requirements
For new features or bug fixes, pleas consider the following to-do list:

[x] Added appropriate unit test functions in the ./biopandas/*/tests directories
[x] Ran nosetests ./biopandas -sv and make sure that all unit tests pass
[x] Checked the test coverage by running nosetests ./biopandas --with-coverage
[x] Checked for style issues by running flake8 ./biopandas
[x] Added a note about the modification or contribution to the ./docs/sources/CHANGELOG.md` file
[x] Modified documentation in the appropriate location under biopandas/docs/sources/ (optional)
[ ] Checked that the Travis-CI build passed at https://travis-ci.org/rasbt/biopandas

Hello @rasbt! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file biopandas/pdb/pandas_pdb.py:

Line 409:80: E501 line too long (87 > 79 characters)

Coverage increased (+0.05%) to 94.236% when pulling 9a7e380918070339d91e775d753a546a326797a0 on v0.2.5 into 615a7cf272692c12bbcfd9d1f217eab440120235 on master.


Friendly error message when input has syntax error

The way to get the reason why a hot reload failed from a ReloadReport is:
report.json?['notices'][0]['message'];

I might have noticed that the message sometimes weirdly formatted though, some kind of conversion might be needed.

@Keithcat1 That looks good. Feel free to PR!

We can firstly land a minimal version, and later reformat etc


fix(avatar): Parse unicode characters in name for avatar component

Hey, I just made a Pull Request!
A small PR that fixes generating avatar from name / surname containing unicode characters (like mine :) ).
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Can you mark the PR ready when it's ready for proper review + merge? :pray:

It is ready, thanks for review :)

Thanks :tada:


decode url parameters

Added decodeURIComponent calls around url parameter strings.

Thank you very much for pointing out this issue.
Now that you make me think about it, I'm pretty sure that we also have to decode the key ( tmp[0] ).
I'm manually merging this fix into the master.

Cool!  Thanks for your hard work on this project, btw.


Streamer Mode

When Process Hacker is configured as the system default Task Manager and when the user is streaming on youtube/twitch... Running PH while streaming (for example; ctrl+alt+del) reveals potentially sensitive and personal information about the streamer including:

Machine name
User name
Processes (Chat programs/Security software)
Services (Security software)
Drivers (Security software)
Network connections (Connected servers)
Disk activity (Folder paths)
Firewall activity

Process Hacker should include a Steamer Mode similar to other software (Discord/Games) to prevent information disclosure and unintentionally revealing sensitive information to the streamer's audience.

Perhaps, SetWindowDisplayAffinity with WDA_EXCLUDEFROMCAPTURE?

Perhaps, SetWindowDisplayAffinity with WDA_EXCLUDEFROMCAPTURE?

Perhaps, SetWindowDisplayAffinity

The streamer mode built into Discord/COD/PUBG/Fortnite was implemented by randomizing strings... If we randomized strings (for example: process1/process2/process3) you wouldn't be able to differentiate processes (notepad and chrome from discord) and might accidentally terminate the wrong program.
It just doesn't make sense to randomize strings for a task manager application so the idea was based on using SetWindowDisplayAffinity to exclude the entire window from capture.

WDA_EXCLUDEFROMCAPTURE

Yes, that's the only viable option available. I'm testing the implementation with different applications before pushing it live.

Perhaps, SetWindowDisplayAffinity

The streamer mode built into Discord/COD/PUBG/Fortnite was implemented by randomizing strings... If we randomized strings (for example: process1/process2/process3) you wouldn't be able to differentiate processes (notepad and chrome from discord) and might accidentally terminate the wrong program.
It just doesn't make sense to randomize strings for a task manager application so the idea was based on using SetWindowDisplayAffinity to exclude the entire window from capture.

WDA_EXCLUDEFROMCAPTURE

Yes, that's the only viable option available. I'm testing the implementation with different applications before pushing it live.

Perhaps, SetWindowDisplayAffinity

This function doesn't exclude menus, tooltips and shadows so the implementation requires more work.

Perhaps, SetWindowDisplayAffinity

This function doesn't exclude menus, tooltips and shadows so the implementation requires more work.

Why not just open task manager instead... if you have a cmd.exe or Run dialog and you create a copy of taskmgr.exe (call it taskmgr2.exe in system32), then in \system32\en-US create a copy of taskmgr.exe.mui and rename that copy to taskmgr2.exe.mui
Just a thought.
If you didn’t have an explorer or cmd to execute anything, I bet it wouldn’t be hard to have the Debugger regval instead execute some PowerShell or AutoIt script IF the left or right mouse button is held down when triggering Ctrl+Shift+Esc

@AltF5
What are you talking about?
This issue isn't about the binary name. It's about sharing images of your processes/services/drivers/networks connections from both PH and taskmgr while streaming to thousands of people just because you needed to open taskmgr and terminate a faulty game.

create a copy of taskmgr.exe (call it taskmgr2.exe in system32)

You still have the same problem with taskmgr2 showing everything running on your machine to viewers. If they can see you're running defender then they can tailor attacks for defender by emailing a game suggestion/executable binary that isn't currently detected by defender... In other cases if they can see discord connected to XYZ address then they know which region you live in and where to swat based on the caller id region.
The whole point of this feature is excluding the UI from streaming programs so you don't share that information about your machine to thousands of people who will analyse it for information - renaming the binary won't prevent taskmgr or PH from showing everything else on your machine while you're live - you have to exclude the entire window.

Ah I thought the issue was that Taskmgr = Fine but PH = exposes too much AIO. This is what through me off “When Process Hacker is configured as the system default Task Manage”... sounds like what persons need is to run a taskkill /im some.exe /f.

Streamer mode added in latest nightly

Streamer mode added in latest nightly

Cool.
Any plans to release another nightly build?
There were quite many changes since last one.


Add support for join with subselect

This is a split of #995 concerning the missing support for JOIN'ing with a subselect a la LEFT OUTER JOIN (SELECT ... ) AS alias ON alias.X = other_table.Y.
This is currently not possible with the SelectBuilder, which assumes that the joins will be tables.

@schauder  Thanks for implementing this. :)


Remove warning

This syntax is no longer experimental, so the warning can be removed.

It is a stage 3 proposal https://github.com/tc39/proposal-class-fields

My bad, i misunderstood what it was warning about 😅


Change migration example repository to Hardhat

https://github.com/OpenZeppelin/openzeppelin-upgrades-migration-example

Closing this assuming people have done the migration already.


comments in application/config/autoload.php are incorrect

This may seem like nit picking but the comments in application/config/autoload.php are incorrect which leads to confusion:
/*
| -------------------------------------------------------------------
|  Auto-load Libraries
| -------------------------------------------------------------------
| These are the classes located in the system/libraries folder
| or in your application/libraries folder.
|
| Prototype:
|
|	$autoload['libraries'] = array('database', 'email', 'session');
|
| You can also supply an alternative library name to be assigned
| in the controller:
|
|	$autoload['libraries'] = array('user_agent' => 'ua');
*/

$autoload['libraries'] = array('database', 'session');

"database" is clearly indicated as an option here but does not exist in the system/libraries or application/libraries folders. I have caught myself several times wondering whether "database" is in fact a library or a driver. Also, it is unclear what the difference is between a library and a driver. Based on the comments here about being "within their own subdirectory," I would imagine that Cache, Javascript, and Session are all drivers, whereas all the other individual files are libraries.
/*
| -------------------------------------------------------------------
|  Auto-load Drivers
| -------------------------------------------------------------------
| These classes are located in the system/libraries folder or in your
| application/libraries folder within their own subdirectory. They
| offer multiple interchangeable driver options.
|
| Prototype:
|
|	$autoload['drivers'] = array('cache');
*/

$autoload['drivers'] = array();

Perhaps we could clarify these? It would likely reduce a lot of confusion IMHO.

If you check the autoloader, when going through $autoload['libraries'], the autoloader first checks for 'database', and, if found, loads the database library (even though it's not in the system's libraries directory), then removes the entry from the array before going on to attempt to load all of the libraries in the array.
You're only really going to put classes in the 'drivers' list which extend CI_Driver_Library. In the built-in libraries, that means Cache, and nothing else. Session and Javascript are libraries which happen to use drivers, but those drivers don't even extend CI_Driver_Library, so the libraries don't use the loader's driver() method to load their drivers.
When looking at the documentation for a class, it tells you whether to use $this->load->library() or $this->load->driver() to load the class. This is an indication of which of these entries should be used for autoloading. Database is just a special case, in more ways that just this.

Thanks very much for the helpful detail. That sounds unfortunately ad-hoc.
I see that 'session' was only recently removed from drivers:
https://github.com/bcit-ci/CodeIgniter/commit/3a627d1951543b7e6ae3f3b3c93a013b33c8986e
I wonder if some of your wisdom here might be distilled into something brief and more accurate for these comments.

The Session library was never a "driver" in an official release. If you ever thought it was, it's because you were using the 3.0-dev version and you use development versions on your own risk ... it's your responsibility to follow dev-version changes.
I have also never, ever seen any confusion about how to auto-load the database classes.
That being said, yes - the comments are a bit unclear in that they don't mention the 'database' classes as a special case and they don't describe that a "driver" must actually use CI_Driver. That "driver" concept is horrible and will go away in the future.

I would imagine that removal of the autoloading of drivers -- something that could easily break an existing website -- is something that should happen with a major version change. (e.g., version 3.x to 4.x) and at the very least something that would happen with a minor version change (e.g., 3.0 to 3.1) and not something that would happen in a development branch for a single version.
I would also point out that the CodeIgniter home page (http://www.codeigniter.com/download ) directs users to the develop branch. The "download CI 3.0" link goes to the develop branch here:
https://github.com/bcit-ci/CodeIgniter/archive/3.0.0.zip
Is this branch expected to be unstable?
Perhaps then that link should be to some other branch (e.g., "master?"). It's not clear from the home page of the 'master' branch which version of CodeIgniter it refers to. Perhaps that is something we could add to the README file.

The codeigniter.com homepage directs users to the 3.0.0 download, and not to the develop branch. The only way to get the "develop" branch is to download the framework from github directly.

@sneakyimp You're overthinking it, a lot, and taking this way off-topic ... Of course we're not just going to drop $autoload['drivers'] in the next micro-version, this shouldn't be a discussion point at all.
And as @jim-parry said, the codeigniter.com/download points to the 3.0.0 download archive and not the develop branch - the fact that the ZIP archive itself is named 3.0.0.zip should tell you that.

I was mistaken about the download link - I apologize. I love CI and have adopted it for a lot of new projects. Just got worried for a second about how rapidly it might be changing.
The helpful thing for me to do would be to try and assist in formulating a slightly better comment based on the helpful info here. Is that something you guys could use? I'm not sure if I can commit to this project or not. Let me know if that's something you guys would find helpful.


feat(tutorial): complete step 3 - Endicott

Closes #
{{short description}}
Changelog
New

{{new thing}}

Changed

{{change thing}}

Removed

{{removed thing}}

Say goodbye to DPM....


Russian translation: improvements of runtime-logging

Q
A

Is bugfix?
yes (doc)

New feature?
no

Breaks BC?
no

Tests pass?
--

Fixed issues
--

Merged. Thanks!


⚠ Bofrost.ch has degraded performance

In 1aed77f, Bofrost.ch (https://www.bofrost.ch) experienced degraded performance:

HTTP code: 200
Response time: 1651 ms

Resolved: Bofrost.ch performance has improved in 695d1b1.


Is there an admin panel ?

Admin panel to manage restaurants, drivers, commissions, payment methods and payment distribution to restaurants?

No. This is just the user interface mockup.


Add return statements for non-void functions

All functions that are not void should return a value on every exit path.

Additionally, please add return statements for the following functions:
https://github.com/sepfy/pear/blob/8c6179ce338d98e735613bdc849bfa8027379366/src/sctp.c#L68
https://github.com/sepfy/pear/blob/8c6179ce338d98e735613bdc849bfa8027379366/src/sctp.c#L104-L105


Is distributed processing on the horizon?

Gotta kick all CPU cores' butts into gear!

I'm a Python pro but a Rust rookie. Hook me up with some learning materials, and I'm all set to rock a pull request. @mike-huls


test mode

add a testing mode, just sends the webhook with a fake trade or your most recent trade. useful for theme creators.

Two ways that I can think of that would be effective to do this:

On startup just removes one out of 10 of the saved confirmed trades, resulting in immediately detecting that 'one' as a new trade, sending a single notification, and then continuing on as normal.
As above, but instead of only removing it once, removes it every X amount of time till testing mode is disabled and Horizon is restarted.
I would like to hear others thoughts on this.

Two ways that I can think of that would be effective to do this:

On startup just removes one out of 10 of the saved confirmed trades, resulting in immediately detecting that 'one' as a new trade, sending a single notification, and then continuing on as normal.
As above, but instead of only removing it once, removes it every X amount of time till testing mode is disabled and Horizon is restarted.
I would like to hear others thoughts on this.

Both options suffice, I prefer Option 1, but that's just personal preference.

Both options suffice, I prefer Option 1, but that's just personal preference.


[WIP] Job Task Detail pages

Introduces Job Task Detail pages and links the Job Detail page to Job Task Detail pages!
No backend to confirm or deny functionality, also missing test. Work in progress.

Reviewer: @jfurrow

I get the following error, when I try to open the job task detail: Invariant Violation: Missing "id" parameter for path "/jobs/?/:id/?/:taskID/?"

Hmm I ran into some weird routing issues after rebasing.

Routing issues fixed by https://github.com/dcos/dcos-ui/pull/460! yay

@orlandohohmeier could you take a look if you get a chance?

For some reason, we lost the "empty" state.

There seems to be an issue with the logic to find the corresponding Mesos task.

Let's not display the "Kill Task" button for "failed" or "completed" tasks.

The log view fails due to an undefined slave id.
File URI:

/slave/undefined/files/download?path=/var/lib/mesos/slave/slaves/f6f119d7-e835-429c-8d89-3057411b87d9-S0/frameworks/f6f119d7-e835-429c-8d89-3057411b87d9-0001/executors/marathon.201606211606296Vy2Y.1d6af977-37ca-11e6-b9b0-aa50bf5e122f/runs/10ea80eb-82e9-4613-8866-9038cfd5de59/stdout

For the lost "empty" state, what is the routing of that page?

There is no extra route, it's displayed whenever we get an empty list of job form the server.

Closing this in favour of #495


Update build.gradle

changed compile to implementation dependencies

build.gradle has changed

Please push this to the master branch, thank you!

Waiting the acceptance of this pull request, I was about to make a pull request till I found it


[2012-04-21] GridFieldAddExistingAutocompleter incorrectly handling searchfields with relations

created by: @NicoHaase (NicoHaase)
created at: 2012-04-21
original ticket: http://open.silverstripe.org/ticket/7194

If the GridFieldAddExistingAutocompleter is set to search in relation fields (eg. through has_one), it incorrectly builds its search query as the JOINs are not added. You can find a patch attached to this ticket that will fix this easily.

Can't easily tell if this is fixed from the code. GridFieldAddExistingAutocompleterTest shows relation fields as scaffoldable, but doesn't show they affect search properly.

Patch is no longer available due to migration, no feedback from Nico in years, and no easy way to reproduce. Closing.


Request: Custom calendar app

Hi,
It would be interesting to be able to change the calendar app. I don’t use the default one.
Thanks for this great app!

Hi, @jlnbdt
Have you tried to change the default calendar app in your device settings? I haven't tried that, I'm just guessing here. I hope that helps.

I just double-checked this and can confirm that Unlauncher will open your default calendar app. If you have multiple calendar apps installed you should be prompted the first time you click the date in Unlauncher to choose which calendar app you want to use as the default.
If you want to change your default calendar app, go to the Device Settings > Apps & Notifications > See all apps. Then select the current default calendar app > Open by default > Clear defaults.  Then, from the Unlauncher homescreen, tap the date and you should be prompted to choose which calendar app you would like to use.
If this does not address your issue, feel free to reopen this issue for further discussion.


Containerize operator binary build

Signed-off-by: Jose A. Rivera<EMAIL_ADDRESS>

@umangachapagain PTAL. I tried to optimize it by either detecting code changes in the host directory or reusing the build cache on the host, but I couldn't figure anything out. If you have any ideas on how to make it faster, please let me know. Otherwise I think we can live with the extended build times.

@nb-ohad had some idea about containerized builds.
I believe the basic idea was to use operator-sdk build instead.

@nb-ohad had some idea about containerized builds.
I believe the basic idea was to use operator-sdk build instead.

It was, but my investigation leads me to believe that operator-sdk build does NOT perform containerized builds of the operator binaries, merely builds the operator container image. Furthermore, there is no way to NOT build the operator container image, so we can't call the command from within the CI anyway.

@jarrpa You are correct. I checked on the noobaa side and got to the conclusions that it is not a "containerized" build but a dockerized build (which means build using docker)
Still, there are benefits of using operator-sdk build as the image itself will not targeted for the local OP system the build is running on. It will be targeted to run as a container.

Still, there are benefits of using operator-sdk build as the image itself will not targeted for the local OP system the build is running on. It will be targeted to run as a container.

@nb-ohad I don't understand what this means. I looked at the debug logs, and it runs these two commands:
DEBU[0000] Running []string{"go", "build", "-o", "/home/jrivera/projects/golang/src/github.com/openshift/ocs-operator/build/_output/bin/ocs-operator", "-gcflags", "all=-trimpath=/home/jrivera/projects/golang/src/github.com/openshift", "-asmflags", "all=-trimpath=/home/jrivera/projects/golang/src/github.com/openshift", "-mod=vendor", "github.com/openshift/ocs-operator/cmd/manager"}
DEBU[0029] Running []string{"docker", "build", "-f", "build/Dockerfile", "-t", "jarrpa/ocs-operator", "."}

My understanding is that the go build above uses the system environment (e.g. go version installed on you laptop) as opposed to any standard environment (e.g. starting the build within a container based on registry.access.redhat.com/ubi8/ubi-minimal). As such, each developer will be potentially building binaries using different go tools in different runtime environments.
And that still doesn't address the problem that we can't run this in the CI because there's no way to NOT call the docker command.

/retest


Finding Highest Divisor

Problem Link
https://www.codechef.com/FEB21C/problems/HDIVISR
Coding platform
Codechef
Programming language

[ ] C
[ ] C++
[ ] Java
[ ] Python 3

I want to work on C on it

I would like to code on this issue in C++.Kindly Assign me

I would like to code on this issue in C++.Kindly Assign me

@Nivedita967 I want to solve this in Java :)

@jayantjethi Go for it :)

I will add my code(in C) after the above files are merged.

If you allow I can also provide python code for it

If you allow I can also provide python code for it

Sure go for it.

After merging above pull request, this issue can be closed


Enable proper CI for Mac OS

The people at Travis CI have very kindly enabled their multi-OS feature for sharp - hooray!
Here's the work-in-progress config - https://github.com/lovell/sharp/blob/travis-multi-os/.travis.yml
We'll need https://github.com/travis-ci/travis-ci/issues/2311 to add nvm to the Mac OS worker machines before continuing to avoid problems like https://travis-ci.org/lovell/sharp/jobs/74540011

#312 should remove the need to have libvips installed globally and therefore make this easier.

https://travis-ci.org/lovell/sharp/builds/118542840 :tada:


map.Functions.AddSource Crashes on Android

AddSource from a Polygon works great on iOS but will crash on Android EVERY time. Even the MapBoxQs demo for the Portland Polygon Draw crashes on AddSource.
Any thoughts or hints?

Hi,
Would you mind debugging without data? It's helpful for others if you could fix it and create a PR.
I am very pleased to merge it.
Thank you.


Unable to change Hash string size

I tried 10 first time. And later I tried to change it to 36. Unable to do this via UI. I still got 10.

Hi @smartin77,
I will investigate this issue. Thanks for reporting.

Meanwhile Hash string size can be changed in table 'piwik_plugin_setting.setting_name=ProtectTrackID' and 'piwik_plugin_setting.setting_name' = 'lengthSetting' and 'piwik_plugin_setting.setting_value = {YOUR DESIRED VALLUE}'

Hi @smartin77, sorry for a big delay in my response. I tried here and wasn't possible to reproduce the issue.

I defined length to 36 and matomo doesn't accepted because and is between 5 and 25.
I defined to 12 and after changed to 20 and worked fine.


Do you want to support asynchronous features for Python 3.3?

asyncio supports Python 3.3, but should be installed from external sources in this case. aiohttp stopped supporting Python 3.3 at v. 0.17.4 but my programs works with it OK. I suppose you to decide this case.

I don't want to support asyncio in Python 3.3, mainly because I don't want to test, and make my code compatible with, one more version of Python. I use the function BaseEventLoop.create_task() which is available only since 3.4.2. In fact, I chose to support async features from Python 3.4.3 on, mainly because that's the version I happened to get my hand on as I was writing them.


Add personal info

What is the purpose of the change

add wenjie's personal info #6

Brief change log

Add name, educational background, interest and so on.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Please add reviewers for this pull request, many thanks :)

how can i add reviewers base on this version ?

how can i add reviewers base on this version ?

simply click the button after reviewers and choose the people, it doesn't matter that I have add myself to review this PR.

/approve

how can i add reviewers base on this version ?

simply click the button after reviewers and choose the people, it doesn't matter that I have added myself to review this PR.


add exec to chef-client

http://redsymbol.net/articles/unofficial-bash-strict-mode/

exec chef-client -j runlist.json


Allow to configure Shopware::DocPath()

1. Why is this change necessary?
Currently Shopware determines its root directory from location of engine/Shopware/Application.php file.
Unfortunately this location can be nested in vendor/shopware/shopware which results into invalid paths in code relying on Shopware::DocPath().
2. What does this change do, exactly?
After provided change, it's possible to easily set correct DocPath from Kernel::initializeShopware() which can be overridden (and it is in mentioned composer-project).
Then there is no need of any special proxy or adapter object to fix behavior when using Shopware as a Composer dependency.
3. Describe each step to reproduce the issue or behaviour.
Install Shopware's composer-project and call Shopware()->DocPath(). It's suppose to return project root path which is not within vendor/shopware/shopware.
4. Please link to the relevant issues (if any).
This problem is related to https://github.com/shopware/composer-project/pull/15
5. Which documentation changes (if any) need to be made because of this PR?
None.
6. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hey @hranicka,
thank you for your contribution.
We'd rather have a fix for this in the composer project though.
In Shopware itself you're supposed to use the DIC parameter 'kernel.root_dir'.

kernel.root_dir, thanks :+1:


LMNet model & weights

Hello,
I'm interested in testing the LMNet network. I saw from here that you have your own model and weights. Are they available?

@vingtfranc please check the README of the package.

@amc-nu Do you have LMNet's training details?


Plugin's Task causes JsonMappingException when the Task extends TimestampFormatter.Task with @Config("default_timezone")

When a plugin has its Task interface which extends core's Task interface with default methods for compatibility, it causes JsonMappingException such as:
com.fasterxml.jackson.databind.JsonMappingException: Multiple entries with same key: default_timezone=org.embulk.config.TaskSerDe$TaskDeserializer$FieldEntry@2548fc01 and default_timezone=org.embulk.config.TaskSerDe$TaskDeserializer$FieldEntry@4331be30

embulk-filter-calcite is the case.
https://github.com/muga/embulk-filter-calcite/blob/v0.1.3/src/main/java/org/embulk/filter/calcite/CalciteFilterPlugin.java#L246-L248
The direct cause is that the extended interface has two getter methods with the same @Config("default_timezone").
Options to fix it:

If the parent's method has default implementation, and it does not have @Config, the overridden method behaves like it does not have @Config. In calcite's case, getDefaultTimeZone behaves like it does not have @Config.
Multiple getters with the same @Config configuration names are allowed.

#951 is a trial fix with the option (2).


Update application-monitoring-operator to v1.1.4

Type of change

Enhancement / new feature

Description
Update the application monitoring operator to the latest version. Not to be backported to 0.31.
Checklist

[ ] Update/write design documentation in ./documentation/design
[ ] Write tests and make sure they pass
[ ] Update documentation
[ ] Check RBAC rights for Kubernetes / OpenShift roles
[ ] Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
[ ] Reference relevant issue(s) and close them after merging
[ ] Update CHANGELOG.md

@enmasse-ci run tests testcase=MonitoringTest

@enmasse-ci run tests testcase=MonitoringTest

:x: Test Summary :x:
TEST_PROFILE: pr
TEST_CASE: MonitoringTest
TOTAL: 1
PASS: 0
FAIL: 1
SKIP: 0
BUILD_NUMBER: 117
:heavy_exclamation_mark: Test Failures :heavy_exclamation_mark:

testAddressSpaceRules in io.enmasse.systemtest.isolated.monitoring.MonitoringTest

:x: Test Summary :x:
TEST_PROFILE: pr
TEST_CASE: MonitoringTest
TOTAL: 1
PASS: 0
FAIL: 1
SKIP: 0
BUILD_NUMBER: 118
:heavy_exclamation_mark: Test Failures :heavy_exclamation_mark:

testAddressSpaceRules in io.enmasse.systemtest.isolated.monitoring.MonitoringTest


mqttx v1.01.1进入后台一段时间后会自动断开连接

mqttx v1.01.1进入后台一段时间后会自动断开连接

Duplicate of #1599
This is a problem caused by technical and code implementation. For the specific reason, please check the issue above. We will fix it in a future version. We are very sorry for causing this problem.


Autocomplete plus R

I search support for building an autocomplete plus R. If someone understand something about autocomplete providers, it could really help (because I don't...).

Would be nice to get this working. I'm thinking I might be able to dedicate some time to this mid-July.

PS: I have no idea how autocomplete works
Same here. I could not find a good tutorial.

I made a first step: (don't work :D)
https://github.com/guillaumechaumet/autocomplete-R/

It works! (almost)


[SPARK-34963][SQL][2.4] Fix nested column pruning for extracting case-insensitive struct field from array of struct

What changes were proposed in this pull request?

This patch proposes a fix of nested column pruning for extracting case-insensitive struct field from array of struct.
This is the backport of #32059 to branch-2.4.
Why are the changes needed?

Under case-insensitive mode, nested column pruning rule cannot correctly push down extractor of a struct field of an array of struct, e.g.,
val query = spark.table("contacts").select("friends.First", "friends.MiDDle")

Error stack:
[info]   java.lang.IllegalArgumentException: Field "First" does not exist.
[info] Available fields:
[info]   at org.apache.spark.sql.types.StructType$$anonfun$apply$1.apply(StructType.scala:274)
[info]   at org.apache.spark.sql.types.StructType$$anonfun$apply$1.apply(StructType.scala:274)
[info]   at scala.collection.MapLike$class.getOrElse(MapLike.scala:128)
[info]   at scala.collection.AbstractMap.getOrElse(Map.scala:59)
[info]   at org.apache.spark.sql.types.StructType.apply(StructType.scala:273)
[info]   at org.apache.spark.sql.execution.ProjectionOverSchema$$anonfun$getProjection$3.apply(ProjectionOverSchema.scala:44)
[info]   at org.apache.spark.sql.execution.ProjectionOverSchema$$anonfun$getProjection$3.apply(ProjectionOverSchema.scala:41)

Does this PR introduce any user-facing change?

No
How was this patch tested?

Unit test

cc @dongjoon-hyun @maropu

Test build #137153 has started for PR 32112 at commit 42d6eda.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41732/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41732/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/41732/

Test build #137153 has finished for PR 32112 at commit 42d6eda.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/137153/

Thanks @maropu. Merged to branch-2.4.


Add netlify _redirects file

What’s the problem?
The client-side router control. When you refresh a page whose path is not /. Then, you hit the 404 wall. Which is just a blank page.
The solution:
Add _redirects file to the dist folder, in order to redirect to the index.html file, so the routers can work properly in the Netlify.
/*    /index.html   200
https://www.netlify.com/docs/redirects/#rewrites-and-proxying
There are other solutions, if you guys do not like this one.

@hilquias-kil I created a plugin to resolve the problem
https://github.com/nicholasess/docz-plugin-netlify
thanks

Thanks @nicholasess.

The main documentation guides everyone to deploying with Netlify, can that be updated to point to a fix? There doesn't appear to be a section in the documentation to help users find this plugin.
Thanks @nicholasess for creating a fix for this issue. Does this still work with rc.8 and 1.0.0 release? When using it, the dev server doesn't appear to render anymore with react-hot-loader errors.
I'll try writing my own post build script for the package.json. That way it doesn't have to be updated with releases of Docz as often.


Removing question-mark encoding workaround.

Fixes #113 by removing the question-mark encoding workaround.
Now the tests pass with Scala 2.13 too.
So basically it's a revert of the old workaround added in #60

Thanks!


Implement player movement and navigation CU-86bxaj07m

fixed tolerable build error which happened when redrawing Edges in editor
added forwarding of NetworkNode related mouse events through Network
implemented Player navigation using godots AStar2D

navigation is initiated inside a new PlayerMovementController
for visualization and debugging I implemented NetworkNodePathVisualizer, which visualizes paths

currently: orange path is the path which the player is traveling and green path is a preview towards the node that the player is hovering over

Task linked: CU-86bxaj07m implement player movement and navigation


chore: Enable dependabot version updates

Might be a good idea to change the schedule from weekly to monthly? It could get out of hand very quickly with the number of projects.

I guess it comes down to whether you prefer a few PRs each week or a lot of them each month :-) They should all be pretty straightforward though.


[WFLY-12580] Explicitly disable the inheritance of Galleon configurations from transitive feature pack

Jira issue: https://issues.jboss.org/browse/WFLY-12580

@bstansberry FYI, Galleon layers job is green too: https://ci.wildfly.org/viewLog.html?buildId=169125&buildTypeId=WF_GalleonLinuxJdk11&tab=buildResultsDiv&branch_WF=%2Fbugs%2FWFCORE-4551%3B%2Fyersan


Reroot vmdb

:tada:

oops, yeah probably

I just decided to blow away the deprecations instead: #3379


SignedMailValidator.signatureNotVerified says BC- but all other email clients verify the signature

Hello there,
The attached email message (see the link below) does not validate in the SignedMailValidator, even after countless hours of analyzing and debugging. We have tried different validation approaches with other client software (Oulook, Thunderbird) and all validate the signature as correct. Even a validation with OpenSSL validates the signature as correct, only BC says that the email signature is wrong (SignedMailValidator.signatureNotVerified).
Since I am out of ideas, I am asking you whether it is a bug or a feature.
Best regards,
EmailMessage.txt

Yes, the signature is not valid.

Many thanks for the quick reply! I have already forwarded this information to the email's sender, asking for a correction of his mail software.
Nevertheless, I'd like to know whether there is some kind of option in Bouncy castle to bypass this BER / DER encoding probelm while validating the signature.
As I write before, the other software I 've used for testing (e.g. Outlook, Thunderbird and plain OpenSSL) validates the signature as correct, so I guess they have some way to bypass this encoding problem.
Best regards!

I met the same question, how can I verify it through?

Thank you very much!!

Yes, this helped us as well.


Need consistent treatment of the "eyebrow" section headings

I have seen 3 different treatments of the small, uppercase section headings just on the home page.
I propose they are all authored on the pages as H4 across the board, but will leave it to the group to decide. (note that there are H4s used in other places, such as the footer, but I think those can be styled specifically).
Current iterations seen on just the home page:

NEWS has it in CSS only
.cards.newscard .cards-card-body::before {  font-size: var(--font-size-11);  letter-spacing: 3.2px;  content: "NEWS";  padding-top: var(--spacer-element-10);  font-family: var(--sans-serif-font-medium); }

DECREASE under the 32% stat is a too-ambiguous P tag:
main .section-bottom .columns-2-cols > div > :nth-child(2) p:nth-of-type(1) {  font-family: var(--sans-serif-font-medium);  font-size: var(--font-size-11);  letter-spacing: 0.2em;  text-transform: uppercase; }

WHAT WE DO is a fairly specific H4, which is my preference
main .section.what-we-do > .default-content-wrapper > h4 {  font-family: var(--sans-serif-font-medium);  font-size: 14px;  letter-spacing: 3.2px;  line-height: var(--line-height-120);  color: #20201f;  margin-bottom: 32px; }

Do we want this detailed info in a basic authoring guide ? Authors might not even understand this and maybe we can have a discussion with Merative design guys to make it consistent if possible ?
OR
have a separate page for all these 1 offs so the merative team is aware. wdyt ?

@amol-anand Are we going to have page "templates', with placeholder text for the customer to refer to?

Can this issue be resolved yet?


feat: update configs

Signed-off-by: donniean<EMAIL_ADDRESS>

:tada: This PR is included in version 6.14.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Having only mutations in the .meshrc.yaml does not load the graphql client on the browser.

Describe the bug
When I set up a graphql mesh project with a  jsonSchema handler, and, add a .meshrc.yaml with only Mutation operations and run the app, the browser opens a blank page. If I add a Query operation, it works fine and loads the graphql client where i can test queries.
Granted that most of the time one would need to add Query Operations, but what if not? Is this expected behavior or a bug?
To Reproduce
Create a  new Project directory
install graphql, @graphql-mesh/cli and @graphql-mesh/json-schema
add your .meshrc.yaml  and a jsonSchema handler. Add  1 or 2 Mutation Operations to it. Do not add a Query operation.
Run the app, for example, with yarn mesh dev
Code Sandbox
https://codesandbox.io/s/cranky-lake-z4bl7
Expected behavior
When I add only Mutations to my .meshrc.yaml, I should be able to run the app and see the client on the browser.
Environment:

@graphql-mesh/json-schema
NodeJS:

Additional context
The .meshrc.yaml sample is in  this code sandbox link

Hi @lyndachiwetelu ,
I'm afraid having a Query Root Type is mandatory.
As per GraphQL specs:

The query root operation type must be provided and must be an Object type

Actually, the Query Root Type is the only one that is mandatory since Mutation and Subscription are optional.
This means that if you don't have a Query Type, your GraphQL schema is internally invalid.

@santino Thank you for the clarification. I wasn't aware of this at all. This makes sense. Closing this.


Add paged attention kernels for the Llama model architecture

Following the paged attention paper, add cuda kernels for the Llama model. Cuda kernels for the Llama architecture have been widely implemented in the open source community.
Moreover, paged attention kernels can be found in the original vLLM implementation here. Of special interest for us is the cuda implementation in attention_kernels.cu, which implements the attention logic using the pagination algorithms (described in the reference paper above).
NOTE: Issue 1 must be completed in order to progress onto issues 2,3.4

In order to further guide the work on this issue, we suggest the following:
[ ] - Get familiar with the main ideas in the paper.
[ ] - Understand how the Llama architecture works, at a high level (how KV cache is used, how attention is calculated, etc).
[ ] - Get familiar with the cuda code in attention_kernels.cu.
[ ] - Once you are familiar with the code in attention_kernels.cu, you can try your own implementation, or simply add the file here. Make sure, you include all necessary dependencies.
[ ] - Create a new PR, tagging this issue, and explaining briefly your understanding of paged attention and how it can be used to optimized Llama serving AI inference.

Hey @jorgeantonio21! Shall I take up this issue? I will follow every step as shown above

@RajeshRk18 please feel free to tackle this one down. Also, if any questions/issues arise while tackling this one feel free to ping me

hello, I would love to work on this too

Hi @jorgeantonio21. I will love to work on this.

Pls assign if available