text:
Are There any examples for dsl script.

Describe your use-case which is not covered by existing documentation.
I would like to create a job with tags via dsl plugin. I'm not sure is it possible to do that?
Reference any relevant documentation, other materials or issues/pull requests that can be used for inspiration.
No response

The Job DSL documentation suggests that it is possible:
jobTagPublisher {
    tags {
        jobTag {
            value(String value)
        }
    }
}

http://<JENKINS URL>/plugin/job-dsl/api-viewer/index.html#path/javaposse.jobdsl.dsl.DslFactory.job-properties-jobTagPublisher
(Note: Jenkins must have the "jobtag" plugin installed)
However, when I try this DSL script:
job('example') {
    properties {
        jobTagPublisher {
            tags {
                jobTag {
                    value("TEST")
                }
            }
        }
    }
}

It always fails:
Processing provided DSL script
java.lang.IllegalArgumentException: Could not instantiate {tags=[io.jenkins.plugins.jobtag.JobTag@273c92]} for io.jenkins.plugins.jobtag.JobTagPublisher: java.lang.IllegalArgumentException: java.lang.ClassCastException@789fa279
	at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:334)
	at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:272)
	at org.jenkinsci.plugins.structs.describable.DescribableModel$instantiate$1.call(Unknown Source)
	at javaposse.jobdsl.plugin.structs.DescribableContext.createInstance(DescribableContext.groovy:50)
	at javaposse.jobdsl.plugin.structs.DescribableContext$createInstance.call(Unknown Source)
	at javaposse.jobdsl.plugin.ExtensionPointHelper$DescribableExtension.call(ExtensionPointHelper.groovy:117)
	at javaposse.jobdsl.plugin.JenkinsJobManagement.callExtension(JenkinsJobManagement.java:414)
	at javaposse.jobdsl.dsl.JobManagement$callExtension$0.call(Unknown Source)
	at javaposse.jobdsl.plugin.InterruptibleJobManagement.callExtension(InterruptibleJobManagement.groovy:151)
	at javaposse.jobdsl.dsl.JobManagement$callExtension$0.call(Unknown Source)
	at javaposse.jobdsl.dsl.AbstractExtensibleContext.methodMissing(AbstractExtensibleContext.groovy:17)
	at jdk.internal.reflect.GeneratedMethodAccessor561.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaClassImpl.invokeMissingMethod(MetaClassImpl.java:951)
	at groovy.lang.MetaClassImpl.invokePropertyOrMissing(MetaClassImpl.java:1279)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1227)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at javaposse.jobdsl.dsl.AbstractContext.invokeMethod(AbstractContext.groovy)
	at groovy.lang.GroovyObject$invokeMethod.call(Unknown Source)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
	at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:180)
	at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23)
	at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:163)
	at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:178)
	at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:182)
	at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:152)
	at org.kohsuke.groovy.sandbox.impl.Checker$checkedCall$1.callStatic(Unknown Source)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:55)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:197)
	at script$_run_closure1$_closure2.doCall(script:3)
	at script$_run_closure1$_closure2.doCall(script)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:264)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:41)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:56)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:120)
	at javaposse.jobdsl.dsl.ContextHelper.executeInContext(ContextHelper.groovy:16)
	at javaposse.jobdsl.dsl.ContextHelper$executeInContext.call(Unknown Source)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
	at javaposse.jobdsl.dsl.ContextHelper$executeInContext.call(Unknown Source)
	at javaposse.jobdsl.dsl.Job.properties(Job.groovy:332)
	at javaposse.jobdsl.dsl.Job$properties.call(Unknown Source)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
	at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:180)
	at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23)
	at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:163)
	at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:178)
	at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:182)
	at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:147)
	at org.kohsuke.groovy.sandbox.impl.Checker$checkedCall$1.callStatic(Unknown Source)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:55)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:197)
	at script$_run_closure1.doCall(script:2)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:264)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.Closure.call(Closure.java:420)
	at groovy.lang.Closure.call(Closure.java:436)
	at org.codehaus.groovy.runtime.DefaultGroovyMethods.with(DefaultGroovyMethods.java:327)
	at org.codehaus.groovy.runtime.dgm$758.invoke(Unknown Source)
	at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoMetaMethodSiteNoUnwrapNoCoerce.invoke(PogoMetaMethodSite.java:251)
	at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.call(PogoMetaMethodSite.java:71)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.call(PogoMetaMethodSite.java:76)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:128)
	at javaposse.jobdsl.dsl.JobParent.processItem(JobParent.groovy:238)
	at jdk.internal.reflect.GeneratedMethodAccessor589.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoCachedMethodSiteNoUnwrapNoCoerce.invoke(PogoMetaMethodSite.java:210)
	at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(PogoMetaMethodSite.java:59)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:51)
	at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(PogoMetaMethodSite.java:64)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at javaposse.jobdsl.dsl.JobParent.freeStyleJob(JobParent.groovy:46)
	at javaposse.jobdsl.dsl.JobParent$freeStyleJob$0.callCurrent(Unknown Source)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:51)
	at javaposse.jobdsl.dsl.JobParent$freeStyleJob$0.callCurrent(Unknown Source)
	at javaposse.jobdsl.dsl.JobParent.job(JobParent.groovy:38)
	at javaposse.jobdsl.dsl.DslFactory$job.call(Unknown Source)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
	at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:180)
	at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23)
	at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:163)
	at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:178)
	at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:182)
	at org.kohsuke.groovy.sandbox.impl.Checker$checkedCall$1.callStatic(Unknown Source)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:55)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:197)
	at script.run(script:1)
	at script$run.call(Unknown Source)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
	at script$run.call(Unknown Source)
	at javaposse.jobdsl.plugin.SandboxDslScriptLoader$2.call(SandboxDslScriptLoader.groovy:76)
	at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:331)
	at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox$runInSandbox$1.call(Unknown Source)
	at javaposse.jobdsl.plugin.SandboxDslScriptLoader.runScript(SandboxDslScriptLoader.groovy:78)
	at jdk.internal.reflect.GeneratedMethodAccessor1064.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoCachedMethodSiteNoUnwrapNoCoerce.invoke(PogoMetaMethodSite.java:210)
	at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(PogoMetaMethodSite.java:59)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:51)
	at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(PogoMetaMethodSite.java:64)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:169)
	at javaposse.jobdsl.dsl.AbstractDslScriptLoader.runScriptEngine(AbstractDslScriptLoader.groovy:108)
	at javaposse.jobdsl.plugin.SandboxDslScriptLoader.super$2$runScriptEngine(SandboxDslScriptLoader.groovy)
	at jdk.internal.reflect.GeneratedMethodAccessor1058.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeMethodOnSuperN(ScriptBytecodeAdapter.java:145)
	at javaposse.jobdsl.plugin.SandboxDslScriptLoader.runScriptEngine(SandboxDslScriptLoader.groovy:54)
	at jdk.internal.reflect.GeneratedMethodAccessor1055.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:352)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.callCurrent(PogoMetaClassSite.java:68)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:177)
	at javaposse.jobdsl.dsl.AbstractDslScriptLoader$_runScripts_closure1.doCall(AbstractDslScriptLoader.groovy:61)
	at jdk.internal.reflect.GeneratedMethodAccessor1040.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:264)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.Closure.call(Closure.java:420)
	at groovy.lang.Closure.call(Closure.java:436)
	at org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:2125)
	at org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:2110)
	at org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:2151)
	at org.codehaus.groovy.runtime.dgm$163.invoke(Unknown Source)
	at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoMetaMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:274)
	at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:56)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:128)
	at javaposse.jobdsl.dsl.AbstractDslScriptLoader.runScripts(AbstractDslScriptLoader.groovy:46)
	at javaposse.jobdsl.plugin.SecureDslScriptLoader.super$2$runScripts(SecureDslScriptLoader.groovy)
	at jdk.internal.reflect.GeneratedMethodAccessor1050.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeMethodOnSuperN(ScriptBytecodeAdapter.java:145)
	at javaposse.jobdsl.plugin.SecureDslScriptLoader.runScripts(SecureDslScriptLoader.groovy:14)
	at javaposse.jobdsl.plugin.ExecuteDslScripts.perform(ExecuteDslScripts.java:351)
	at jenkins.tasks.SimpleBuildStep.perform(SimpleBuildStep.java:123)
	at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:80)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:818)
	at hudson.model.Build$BuildExecution.build(Build.java:199)
	at hudson.model.Build$BuildExecution.doRun(Build.java:164)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:526)
	at hudson.model.Run.execute(Run.java:1900)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:44)
	at hudson.model.ResourceController.execute(ResourceController.java:107)
	at hudson.model.Executor.run(Executor.java:449)
Caused by: java.lang.IllegalArgumentException: java.lang.ClassCastException@789fa279
	at jdk.internal.reflect.GeneratedMethodAccessor1047.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.jenkinsci.plugins.structs.describable.Setter$1.set(Setter.java:33)
	at org.jenkinsci.plugins.structs.describable.DescribableModel.injectSetters(DescribableModel.java:429)
	at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:331)
	... 180 more
ERROR: Could not instantiate {tags=[io.jenkins.plugins.jobtag.JobTag@273c92]} for io.jenkins.plugins.jobtag.JobTagPublisher: java.lang.IllegalArgumentException: java.lang.ClassCastException@789fa279
Finished: FAILURE

Jenkins 2.375.2
jobtag 25.va_12b_1dd63367
job-dsl 1.81

Until jobTagPublisher  works, it is possible to add tags using the configure block
job('example') {
    configure { project ->
        def tagRoot = project / 'properties' / 'io.jenkins.plugins.jobtag.JobTagPublisher' / 'tags'
        tagRoot << 'io.jenkins.plugins.jobtag.JobTag' {
            'color'('#FFC300')
            'value'('TAG1')
        }
        tagRoot << 'io.jenkins.plugins.jobtag.JobTag' {
            'color'('#FF5733')
            'value'('TAG2')
        }
    }
}

authors: DTHaydon RiddlerKnight

repo: jenkinsci/jobtag-plugin


text:
s3copy doesn't copy folders

Description
s3copy doesn't copy folders, throws 404 instead
Steps to Reproduce

Pipeline:

pipeline {
    agent {
        ...
    }

    options {
        withAWS(credentials: "some-account")
    }

    stages {
        stage('s3copy dir test') {
            steps {
                script {
                    s3Copy(fromBucket: "some-bucket",
                            fromPath: "foo-bar/",
                            toBucket: "some-bucket",
                            toPath: "foo-bar2/")
                    }
            }
        }
    }
}

Run pipeline

Expected behavior:
Copies folder and all nested files.
Copying s3://some-bucket/foo-bar to s3://some-bucket/foo-bar2

Copy complete

Actual behavior:
Exception being thrown and copy/sync never occurs.
Copying s3://some-bucket/foo-bar to s3://some-bucket/foo-bar2

com.amazonaws.services.s3.model.AmazonS3Exception: Not Found (Service: Amazon S3; Status Code: 404; Error Code: 404 Not Found; Request ID: A00F4C91064D6806; S3 Extended Request ID: 6GdVYHExff+URzOnD8/CH3TPd8JEidoa0L5C+lB7bVBug1PKMpg93PQOKLNqWw0lTDO8e7Bo0E0=), S3 Extended Request ID: 6GdVYHExff+URzOnD8/CH3TPd8JEidoa0L5C+lB7bVBug1PKMpg93PQOKLNqWw0lTDO8e7Bo0E0=
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleErrorResponse(AmazonHttpClient.java:1695)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1350)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1101)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:758)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:732)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:714)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:674)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:656)
	at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:520)
	at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4705)
	at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4652)
	at com.amazonaws.services.s3.AmazonS3Client.getObjectMetadata(AmazonS3Client.java:1310)
	at com.amazonaws.services.s3.transfer.TransferManager.copy(TransferManager.java:1977)
	at com.amazonaws.services.s3.transfer.TransferManager.copy(TransferManager.java:1910)
	at com.amazonaws.services.s3.transfer.TransferManager.copy(TransferManager.java:1862)
	at de.taimos.pipeline.aws.S3CopyStep$Execution.run(S3CopyStep.java:251)
	at de.taimos.pipeline.aws.S3CopyStep$Execution.run(S3CopyStep.java:175)
	at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

Environment
Jenkins-Version:
2.150.2
Java-Version:
1.8.0_181
Plugin-Version:
1.36
Master/Slave Setup:
Tested on master

Hi there, I just noticed that you posted this. It's possible that you are having a similar issue as in https://github.com/jenkinsci/pipeline-aws-plugin/issues/159. You may want to check the last comment where we found a solution.

@ofasterling thanks, but It's not the same.
In this case the method fails to copy whole folder but works fine for a single file.

The AWS SDK copy supports only one object to be copied at a time.

A "folder" is not an object in S3, that is why you can not get it by key, but the folder path is actually a prefix for all the keys of the objects contained by the folder.

So in order to copy a complete folder, the copy algorithm has to be repeated for the number of objects in the folder. This implementation is not in the plugin since this is a very unusual case.

source: gharchive/issue

repo: jenkinsci/pipeline-aws-plugin

license_type: permissive

license_source: github-api


text:
increase jenkinsrule timeout for flaky tests

SshLauncherTest#trackCredentialsWithUsernameAndPrivateKey and SshLauncherTest#trackCredentialsWithUsernameAndPassword are flaky.
Tests itself are good, but from time to time they hit JenkinsRule's timeout (180 sec), so I suggest to increase timeout to 600 sec as some of tests in other plugin do (search)

Submitter checklist

[ ] JIRA issue is well described
[ ] Appropriate autotests or explanation to why this change has no tests

I did not see those tests failed in ci.jenkins.io, Could you give more details about where you see those failures?

I did not see those tests failed in ci.jenkins.io, Could you give more details about where you see those failures?

Cloudbees CI fails intermittently when running this test, I'will attach the log soon

Cloudbees CI fails intermittently when running this test, I'will attach the log soon

It fails on Cloudbees CI  and not in ci.jenkins.io looks like an issue on Cloudbees CI not in the tests. when a test is flaky, it is flaky everywhere not only in one CI/environment.

Checking the logs, the agent is created and the SSH agent is trying to reconnect two tomes so, for some reason the Jenkins is not responsible enough in your CI, it looks like resources issues on the Agent used to run the test.

Cloudbees CI fails intermittently when running this test, I'will attach the log soon

It fails on Cloudbees CI and not in ci.jenkins.io looks like an issue on Cloudbees CI not in the tests. when a test is flaky, it is flaky everywhere not only in one CI/environment.

Hm, I tried to run this test in the IntelliJ and it failed on first attempt with the same log (next 9 attempts was fine), it is not looks like Cloudbees CI issue.

Which commit are you using? Which JDK are you using? In the last three days ci.jenkins.io has running the test 3 times, in the last 11 days there is no issues related to those tests

I'm using latest main branch, openjdk version "1.8.0_292". IMO 11 runs is not representative, in our CI it fails once in hundreds of runs (other note: when I running locally on system with low resources it fails each time)

I have ran it on my local three times without issues, I am using JDK 11, JDK 8 is not recommended in the Jenkins core 2.346.2 version (since https://www.jenkins.io/changelog-stable/#v2.332.2) I am no longer compile on JDK 8 since this plugin is updated to the latest BOM and does not make sense compile on JDK 8 anymore.
However, checking the execution of the test should take about 150-160 seconds (you can check the execution in the Agent logs in the Jenkins instantiated by the test), so it is possible to make the test faster by configuring less wait between reconnections and less timeout of connection. This change will resolve your issue and improve the test execution instead of making it wait longer.

I am making a PR with the changes

it is possible to make the test faster by configuring less wait between reconnections and less timeout of connection. This change will resolve your issue and improve the test execution instead of making it wait longer.

I agree, sounds much better

superseded by https://github.com/jenkinsci/ssh-slaves-plugin/pull/323

source: gharchive/pull-request

repo: jenkinsci/ssh-slaves-plugin

license: MIT


text:
Replace use of recommendedPlugins with explicit configurations in Jenkinsfile

#163 fixed the build after it was broken by https://github.com/jenkins-infra/pipeline-library/pull/92, but then https://github.com/jenkins-infra/pipeline-library/pull/146 broke it again.
This PR stops using buildPlugin.recommendedConfigurations to avoid these kinds of issues in the first place.

Rebuilding:

[2020-05-28T20:57:15.881Z] EC2 (aws) - Ubuntu 18.04 LTS (i-0fe3f98bb2db782d4) was marked offline: Node is being removed
Unable to create live FilePath for EC2 (aws) - Ubuntu 18.04 LTS (i-0fe3f98bb2db782d4)

EC2 (aws) - Ubuntu 18.04 LTS (i-0ea714d759e16f365) was marked offline: Connection was broken: java.io.EOFException

repo: jenkinsci/workflow-job-plugin


text:
Not possible to "teach-in" HmIP-MOD-OC8

Describe the issue you are experiencing
I have two HMIP-MOD-OC8 (8-Kanal-Empfangsmodul) that I want to train on the RaspberryMatic. Both fail the teach-in process.
In the past, they used to work with RaspberryMatic and Homematic CCU3 (cannot test the latter anymore, as no CCU3 is available). It appears to me that the device fails to bind on a newer Raspberrymatic
Describe the behavior you expected
The Teach-in process should find the devices.
Steps to reproduce the issue

factory reset of the HMip-MOD-OC8
starting the teach-in process on the RaspberryMatic

What is the version this bug report is based on?
3.61.5.20211113
Which base platform are you running?
rpi4 (RaspberryPi4)
Which HomeMatic/homematicIP radio module are you using?
HM-MOD-RPI-PCB
Anything in the logs that might be useful for us?
.

Additional information
Manual binding (without internet connection) doesn't work either.

The Raspberry Pi4B has strong radio interference capatibilitys especially for HmIP.
If your HM-MOD-RPI-PCB is connected directly to GPIO, then interferences are programmed.
Do not use the USB3 ports of the Pi4B and if possible put your RF-Module at least 50cm away from the Pi4B.
Use a GPIO extension cable or better the HB-RF-USB-2 or HB-RF-ETH.
Tipps for using the Pi4B as Homematic-Central in the Homematic-Forum (in german) >here<

repo: jens-maus/RaspberryMatic

license_source: bigquery


text:
fix nltk error; update pandas; update dockerfile; add nltk req

Fixes nltk error

Downloads necessary nltk externals in separate script
Updated dockerfile and pushed to registry
pandas==1.5.3 resulted in some weird bug: updated requirements to pandas==2.2.2

ok. although, i'm not sure if we need all the files for the different languages of nltk. but thanks!

ok. although, i'm not sure if we need all the files for the different languages of nltk. but thanks!

files are not needed at all since they are downloaded separately in script. I forgot to remove them, have done now

authors: jeremychia jonfoong


text:
dependecy check could not analyze pom.xml for java

For java related projects, when build is successfully done and jar are created in target directory those are only analyzed by dependecy-check not the pom.xml separatly where all other dependecy are mentioned.
Need to provide feature like to analyze pom.xml.
Thank You in advance

The DependencyCheck Maven plugin analyzes poms.
https://jeremylong.github.io/DependencyCheck/dependency-check-maven/

Thank You Steve.
I think its quite hard to understand the example. Do you have any full
documentation to explain it could be great like build process , maven
through directory scanning example, any options in cli to provide only
pom.xml to scan ?
On Thu, May 10, 2018 at 10:31 AM, Steve Springett notifications@github.com
wrote:

The DependencyCheck Maven plugin analyzes poms.
https://jeremylong.github.io/DependencyCheck/dependency-check-maven/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jeremylong/DependencyCheck/issues/1270#issuecomment-387952505,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AL-TzqIruULd7V1-LqpoEwv7loDCj4Lbks5tw8mXgaJpZM4T5Wtq
.

The CLI doesn’t understand poms which is why we recommend using the maven plugin for maven builds.
In its simplest form, the plugin can be executed from the command line similar to other maven plugins.
mvn org.owasp:dependency-check-maven:check

If you want to customize the execution or automate it as part of the build, the examples and the configuration link provides all necessary info.

I am also confused by this. when run org.owasp:dependency-check-maven working perfect，but why can not run cli in pom.xml's current directory?
why“CLI doesn’t understand poms ” ？

The CLI doesn't have dependencies on Maven core, so it doesn't know how to resolve Maven dependencies. This keeps the CLI lightweight and puts an emphasis on using best-practices. We've always recommended that if a Dependency-Check plugin exists for a given build system (Maven, Gradle, SBT, etc), then users are highly encouraged to use the plugin over the CLI. The results will be much more accurate.

authors: nanolikeyou praveensutar stevespringett

repo: jeremylong/DependencyCheck


text:
Exception not caught

I want to use your library to catch Exceptions in Tasks or methods which will use async/await.
Unfortunately the Exception is not caught.
public class TaskExtensionsTests
    {
        [Fact]
        public async Task CatchReturnStatusTest()
        {
            try
            {
                await GetException().Then(() =>
                {

                }).Catch<Exception>(exception =>
                {

                });
            }
            catch (Exception e)
            {

            }
        }

        private Task GetException() => throw new NotImplementedException();
    }

Found my mistake.. 🤦♂

Glad to see that you have solved the issue. This Library was develop many years ago as a workaround to missing async/await in legacy C# Versions... You should try to use async/await instead if you can / are allowed, as it offers the same possibilities to handle async processings and more (better support for try/catch, loops...)

Thanks for the feedback! Unfortunately, I haven't found a clean way to catch exceptions cleanly without the hassle of using a TryCatch block.
I use a ReturnStatus class in my code with which I perform all error handling and logging.
The combination with your extension methods seems quite elegant to me!
You are welcome to correct me and show me a better way.
public static Task<HtReturnStatus<T>> ToHtReturnStatus<T>([NotNull] this Task<T> first, [CanBeNull] TaskScheduler taskScheduler = null)
      => first.Then(HtReturnStatus.Success).Catch<HtReturnStatus<T>, Exception>(exception => HtReturnStatus.Failed<T>(exception), taskScheduler);

[Fact]
public async Task ToHtReturnStatus_ReturnValueTest()
{
	var result = await ThrowArgumentNullWithReturnValue().ToHtReturnStatus();
	result.ShouldHaveFailed(HtErrorCode.EXCEPTION_ArgumentNull);

	var result2 = await SuccessTaskWithReturnValue().ToHtReturnStatus();
	result2.ShouldHaveSucceeded();
	result2.Result.Should().Be(123);
}

private async Task<int> SuccessTaskWithReturnValue()
{
	await Task.Delay(1);
	return 123;
}

private async Task<int> ThrowArgumentNullWithReturnValue()
{
	await Task.Delay(1);
	throw new ArgumentNullException();
}

repo: jeromerg/NAsync


text:
no unicode

https://eldood.uk/010b75c2d3

Fixed in https://github.com/jes/eldood/commit/dfdba63ff3c5b52b21b0e1c03430f1b72784b25f
Thank you!

Can confirm it works, thank you!

repo: jes/eldood

license: Unlicense


text:
Type hints

Hey!
Would you accept PRs with type hints? I find this package very useful and would be willing to invest some time in type-hinting this package in future months.

Thanks!
Yes I'm willing (and grateful) to accept type hints. I had to check, but looks like type hints are supported from Python 3.5 and higher so no issues there.

After investing about 3 hours to type hinting the code, it seems like we have some problems with architectural structure of the project. It is not uncommon for type hints to expose circular imports due to the tangled file/object dependency graph, and as it seems right now, circular imports are somehow making the code not operationable.
Examples:

polarion.polarion has circular import with polarion.project
polarion.document has circular import with polarion.project and polarion.polarion
polarion.testrun  has circular import with polarion.record
polarion.document  has circular import with polarion.workitem
...

What are your thoughts on this - did you experience problems elsewhere (tests, everyday usage, import order issues, ...)?
I know most of these things are solvable by even more abstraction (and current implementation is far from poor), but these modifications are never quick and simple. They take time and might break some backward compatibility, as code sometimes must be moved to other places.
You can inspect the changes on this branch.

I've known there were circular dependencies, but i have not run into any issues with it apart from when i started this project some time ago. I cannot remember why this was not addressed then, but here we are.
As you examples show, this is mostly caused by a class creating a new class, but the new class 'needs' a reference to the creator.
Polarion creates Project, but Project needs polarion. Then Project createsd Workitem and workitem needs Polarion and Project.
So I'm happy to improve the structure, but I would need some suggestions on what and how to change it.

Maybe a good starting point is to draw a layout of Polarion itself, and see what are the relations between its parts.
For example, after a connection is created, our entry point is a Polarion Project. It can hold many items, for example WorkItems, Documents, TestRuns, ... Furthermore, Documents (and others) can also hold WorkItems.
That directly means that Project and Documents are users of WorkItem(s), not vice versa. WorkItem has only dependency on Connection, but not on any of these other items.
... and so on. To set a more direct example, maybe something like this is the way to go:

polarion/polarion.py is a "root" file - it does not reference any other file/object.
It has no dependencies other than to files in base directory.
Polarion class can stay as it is except getProject() method, which could be moved to polarion/project.py
in form of a public function or Project class static method. This function receive Polarion class instance as an attribute.
Other files can than always import polarion.py as it is free of any dependencies. In example above, this is a Connection.
project.py on the other hand needs majority of other objects (WorkItem, Document, ...).
That explicitly determine the relations: project.py imports other files, and not vice versa. Other files can import
only other low level files, like workitem.py and polarion.py.
workitem.py, as stated above, is an "isolated object" from project.py - it does not import it or anyhow interact
with its instance directly. Objects of other type are never created from WorkItem itself.
The same goes for some other items, record.py for example.
4.WorkItem creator (__init__()) logic to find and build WorkItem from Project should be moved to Project
itself, for example, into the getWorkitem() method.
Maybe in workitem.py there should be more helper functions/methods to create WorkItem (new or from existing data) instead of current "large" constructor?
Back-links or "creator references", could be solved by items holding only IDs of the
referencing object, not the object instance itself. User can than decide what to do with this ID, and if necessary
find parent item via that ID and appropriate helper function/method.
I am aware this is not as convenient as it is now, but that way you keep things separated and you get the option
to completely refactor entire parent referencing object, without actually modifying child object at all - you only
keep an ID, not the object itself.
If performance is the issue (user finding parent item and re-creating objects), you could implement object caching
(found by object ID) inside polarion package or similar.
I can see that in workitem.py there are helper functions to get WorkItem statuses (enum), which use project
instance. As this is probably the only way (designed by Polarion), getters for enums maybe shouldn't be there but in
Project itself, as they are not limited to one specific WorkItem, but work items of that specific type.
btw: setStatus() does not warn user if new status is not known (which is dangerous, like caught exception
with only pass in except block).

Now, this is just an example based on very limited knowledge of your actual implementation/package/caveats. I might
understand it wrong or can't see all use cases, and even if I could, there might be many solutions to this problem
and even when choosing one, you can't be sure it is the right one - such knowledge comes from experience and is hard
to write down a "how-to guide".
Main point here is that relations between your objects are always in one-way, otherwise you will keep getting circular
imports which are a good indicator, that object dependency graph is tangled IMO. If you search google images for code dependency graphs, you will see, that relations are always one way from object A to object B.
Hope this is of any help. This would be a massive change, which you might not be willing to do, and I can understand it.

Thank you for additional wording. i will get back to this at some point, but it should not be expected anytime soon.

Hi @schperplata ,
It has been a while and i have something that I'd like to share and maybe get your thoughts on.
Is start by (as suggested) removed the connection element out of the class structure as is should hold no function there apart from allowing a connection.
So this class only knows the API and provides a wrapper for it. I've decided to add an abstraction layer here since there will be a REST API coming to Polarion and this way it is prepared. But it is currently unknown whether it will have the same function, complementary functions or a complete replacement of WSDL.

After this a set of base classes are defined with (potential) common functionality. These are used by various Polarion items, basically as used currently, but a bit more separated.

And finally all Polarion items. The smallest being a user, which is merely a info container. Workitem being the smallest Polarion item and thus can be referenced by all and may not reference anything but itself (needed for linking). If there is something where it would need to point to a bigger object, that must then be done via the project class.
The Plan, test run, record and document may all use workitem and user (left our of drawing for clarity). There should be no need for those object to reference each other.
Finally Project creates all. All object to know about the project, but only because it is contained in their Polarion data. This will not be an object reference.

I hope you may have some feedback on this.
After this I plan to do the following:

Find out how to mark stuff as deprecated so users can get a early warning
Create this structure in a new branch and see if i missed anything
Start creating this implementation

While doing this I also want to change the coding style to be more compatible with PEP8 as the names currently have always bothered me. Also this will mark the time it will be switched to a version number using year and moth. so .. as this is more compatible with Polarion version numbering.
While addressed @schperplata I encourage everyone who reads this to reply with an opinion.

Hey!
Yeah, that is exactly the way I see the layout of this project. Your thoughts match mine (above) and if properly implemented, will surelly address issues that type hinting exposed.
I can't be 100% sure about all the object relations, as I don't know all the details and Polarion-side gotchas. Anyway, the goal is to create an isolated objects that would be easy to develop, test and maintain. Also (same as you proposed), enoguh abstraction must be implemented on all layers so that adding another connection/feature can be done  without changing current WSDL part or other un-related functionality. I think this is the way to go, we can look at the details further down the road, if necessary.
What I am a bit more concerned is the last part:

While doing this I also want to change the coding style to be more compatible with PEP8 as the names currently have always bothered me. Also this will mark the time it will be switched to a version number using year and moth. so .. as this is more compatible with Polarion version numbering.

In my point of view, all proposed changes (which are more than welcome in my opinion) represent major changes: either breaking backward compatibility or have a lot (A LOT) of extra code and temporary code mess. What I would do in this case is either:

Increase major package version and left current implementation intact.
Create completely new package.

I know these are hard to make decisions and no decision is pleasant as it affect users or maintainer. I personally would go into point 1.
In any case, I'm glad that you found time and a willingness to improve this package. I am currently quite busy, but if you need help, there is always a minute or two to spare (as long as there is no ETAs :) )

Hi @schperplata
I'm back with a question.
I'm running into some trouble at abstracting the API's. The WSDL API return some objects that represent all polarion items. However the REST API returns everything nicely in JSON structures.
I'm thinking of going through the effort of converting everything from WSDL to JSON as well. This moves some complexity from other parts to the WSDL API but with this comes the bigger potential for bugs as now we have to touch all fields of a workitem for example.
Converting the REST API output into objects from WSDL is probably not an option because we cannot presume the WSDL objects they will always be available.
Alternatively the abstraction point could be the actions that we preform on an object. So 'update field' for example. But this moves the functionality from what would be the Workitem class to the API and that seems to make little sense to me.
I would like to hear your thoughts on this.

I think this might be a good example of a various design patterns (depends which ones on a chosen concept), for example adapter pattern.
My instinct also tells me what you proposed, that is an abstraction layer above I/O data that can either come from JSON, WSDL, or who knows, maybe some SQL database one day. As (I assume) Polarion items (objects) aren’t very varying part, I would probably create a Polarion-like models of items completely separated from any I/O data. Actual objects creation could benefit from another pattern, that is factory pattern, while I/O data manipulation could use adapter pattern to transform data JSON/WSDL.
Theoretically 😉 Practically implementation often depends on a bunch of other factors and compromises. Also, I am by no means some badass expert, so there might be a lot of other better solutions, opinions and experiences. I am also still learning design patterns and will continue to do so for the next few years. Light years 😂 However, I think we might be on the right path with abstraction of actual Polarion objects (models) and low level data manipulation.
Hopefully the response is of any use. If design patterns are something you aren’t familiar with (I’m sure you are), check for the book ‘Head first design patterns’.

Hello!
Can somebody help me? :D
I have got some problem with workitem linking, if i add a link to a workitem with service.addLinkedItem() its working correctly, but if i want to delete a link from the same work item thats literally do nothing (service.removeLinkedItem()). Whrn the function is called there is some delay in it so its do something but don't delete the link.
That is working correctly:
service = self._polarion.getService('Tracker')
service.addLinkedItem(self.uri, workitem.uri, role={'id': link_type})
But this don't:
service = self._polarion.getService('Tracker')
service.removeLinkedItem(self.uri, workitem.uri, role={'id': role})
The uris that i hand over 100% correct:
self.uri - the workitem uri who have links in it
workitem.uri  - which is linked to the workitem
role - the link role
Anyone have any ideas?
I look forward to receiving your reply
Sorry for bad English :D

@Zoli2000 I am not an owner of this repo, but still: This is not the right place for your problem - please open a new issue, as this has nothing to do with a debate here. It is a common practice across GitHub (and other) projects. Thanks.

authors: Zoli2000 jesper-raemaekers schperplata

repo: jesper-raemaekers/python-polarion


text:
Wyze Cam Outdoor, Model HL_WCC2 not supported

Is your feature request related to a problem? Please describe:

Describe the solution you'd like:

Describe alternatives you've considered:

Additional context:

I’m getting the same error message
“Camera (Model: HL_WCO2 not supported submit a request to…”
The issue I’m having is that this message prints constantly to the Homebridge logs, even when I exclude the MAC address in the settings. Any ideas on how to get this to stop and/or support the Outdoor Cam v2?

authors: WSewell afridorian


text:
Update Read.me

Update with App Dev and data science
NB: I am a GSSOC Contributor

Hey @jfmartinz I am GSSOC contributor can you please assign this issue to me I would be glad to work on it!

Check my pull req #283

I've noticed your project lacks a README.md file, crucial for sharing essential project details and fostering collaboration. As a GSSoC 2024 participant, I'm keen on contributing meaningfully. Can you assign me this task? I'm dedicated to crafting a thorough README for the project's benefit. Thanks for considering. Eagerly awaiting your response.
Thank u @jfmartinz

I've noticed your project lacks a README.md file, crucial for sharing essential project details and fostering collaboration. As a GSSoC 2024 participant, I'm keen on contributing meaningfully. Can you assign me this task? I'm dedicated to crafting a thorough README for the project's benefit. Thanks for considering. Eagerly awaiting your response.
Thank u @jfmartinz

I actually have a README.me file. Is this what youre referring for?

@jfmartinz you can close this issue as its done

@jfmartinz please assign it to me, i want to work on this

repo: jfmartinz/ResourceHub


text:
jfrog-cli distributed as nuget package

Hi,
do you plan to distribute jfrog-cli as nuget package with tools folder per platform?

Hi @AdaskoTheBeAsT,
Nice idea!
We will gladly accept a pull request packaging JFrog CLI as s nuget package.

repo: jfrog/jfrog-cli


text:
Undefined symbols for architecture x86_64 / i386

I asked this a s comment on another issue, but as it is closed one, thught it could be better to ask as separate issue:
I was able to compile for iOS, as:
cargo lipo --release

But got error while exciting, i.e. once building the iOS app in Xcode.
I tried simple statement:
    let conn = Connection::open_in_memory().unwrap();
    conn.execute(
        "CREATE TABLE person (
                  name            TEXT NOT NULL,
                  )",
        NO_PARAMS,
    ).unwrap();

    conn.execute(
        "INSERT INTO person (name, time_created, data)
                  VALUES (?1)",
        &[&to.to_owned() as &ToSql],
    ).unwrap();

The error I got is:

symbol(s) not found for architecture x86_64

Undefined symbols for architecture x86_64:
"_sqlite3_column_int64", referenced from:
rusqlite::statement::Statement::value_ref::h1ef4d7e4ee859386 in libgreetings.a(rusqlite-39d80e8cd3d6a115.rusqlite.99wt63ts-cgu.3.rcgu.o)
"_sqlite3_column_blob", referenced from:
rusqlite::statement::Statement::value_ref::h1ef4d7e4ee859386 in libgreetings.a(rusqlite-39d80e8cd3d6a115.rusqlite.99wt63ts-cgu.3.rcgu.o)
"_sqlite3_bind_int64", referenced from:
rusqlite::statement::Statement::bind_parameter::hc14d4185381afdbf in
...
...
...

Even when I changed the iOS Development target and installed simulator iOS 10, and changed the Architectures to $(ARCHS_STANDARD_32_BIT) instead of $(ARCHS_STANDARD) I got the same error with:

ld: symbol(s) not found for architecture i386

Well, the build issue had been solved with me, once my android issue ad been resolved, i.e. by using:
[dependencies]
rusqlite = {version = "0.15.0", features = ["bundled"]}

instead of:
[dependencies]
rusqlite = "0.15.0"

Now I've to l

repo: jgallagher/rusqlite

license: mit


text:
Why the T in query_map, and query_and_then is constrained with 'static?

The query_map has a following signature:
fn query_map<'a, T, F>(&'a mut self, params: &[&ToSql], f: F) -> SqliteResult<MappedRows<'a, F>>
where T: 'static, F: FnMut(SqliteRow) -> T

From my understanding, the T: 'static constraint is redundant. What is the reason for it to be there?

Hmm, yeah, I think you're right. The intent was to make sure the caller couldn't collect the SqliteRow handles being passed into the closure; e.g.,
let rows = query.query_map(&[], |row| row);

but even without the T: 'static I don't think it's possible to get this to compile. I wonder if a solution to this open bug (related to this SO question about closures that return references) would make it possible to write this, at which point the T: 'static would no longer be redundant. What do you think?

Oh, now I see the reason of that static. But the worst thing that would happen, if somebody's collected these rows, would be just a panic, nothing more, right?
So if the 'static were removed, the bug (still not fixed :disappointed:) wouldn't prevent returning rows from a closure (the workarounds a really simple (create standalone fn or just don't use annotations)).
But I think there's a way to prevent collecting rows without restricting T! I you'd change the F type inside MappedRows from FnMut(SqliteRow) -> T to FnMut(&SqliteRow) -> T, Rust would naturally prevent the short-lived reference from escaping the closure body. And since SqliteRow is not Copy, then no panics guaranteed! (expect of somebody calling .get(999) of course.

But the worst thing that would happen, if somebody's collected these rows, would be just a panic, nothing more, right?

Correct. And actually just collecting them is fine; it'd just panic if someone tried to use a collected row.

I you'd change the F type inside MappedRows from FnMut(SqliteRow) -> T to FnMut(&SqliteRow) -> T, Rust would naturally prevent the short-lived reference from escaping the closure body.

Ahh, that's a great point. Will make that change shortly.

authors: jgallagher krdln


text:
don't truncate text columns that contain nul bytes, round 2

Sorry about that regression. This PR contains the previous changes plus an extra patch that should ensure text content is coerced to utf-8 first, by calling bytes() prior to blob():
https://github.com/ankitects/rusqlite/commit/c0c264c1694805e4d03774f9ee9090a74c46d4a0
From the sqlite docs:
"Type conversions and pointer invalidations might occur in the following cases:
The initial content is a BLOB and sqlite3_column_text() or sqlite3_column_text16() is called. A zero-terminator might need to be added to the string.
The initial content is UTF-8 text and sqlite3_column_bytes16() or sqlite3_column_text16() is called. The content must be converted to UTF-16.
The initial content is UTF-16 text and sqlite3_column_bytes() or sqlite3_column_text() is called. The content must be converted to UTF-8."
Tested the benchmark again, and it did not change.

I would prefer #659.

authors: dae gwenn


text:
Delete files

Issue #29

Great work! Convert tabs to spaces and then it's all good.

Thanks!  It looks like my tabstop didn't take in vim for some reason.  Fixed.

authors: ThomasWo tylervz

repo: jglamine/calvinwebprint


text:
nullAttr doesn't seem to work as before with pandoc filter

I come to get a runtime error with nullAttr (from Text.Pandoc.Defitnition) in pandoc-types-1.23.1 when I use it within a pandoc filter like bellow;
$ cat myfilter.hs
import Text.Pandoc.JSON

main :: IO ()
main = toJSONFilter block

block (Para _) = Div nullAttr []
block b = b

This leads to an unexpected error instead of the expected result [ Div ( "" , [] , [] ) [] ];
$ pandoc --filter myfilter.hs -f markdown -t native
foo
(hit ctrl-d)
Error running filter myfilter.hs:
Filter returned error status -11

This filter worked as expected before, though I'm not sure until which version. And I could get the expected result now if I redefined nullAttr as the same definition as the original ("",[],[]), hiding the imported definition.
Does somebody has any clue regarding this error?
-- Sorry in advance if this was to be issued in pandoc itself instead of here.

I can't understand why this would be so, nor can I reproduce the issue!

Thank you for trying to check that. Then it might be caused by my environment including GHC. Sorry to have bothered you. I closed this issue anyway.

Just some follow-ups. My ghc version is 9.4.4, and I tried more minimal reproducible example;
import Text.Pandoc.Definition

main = do
  putStrLn $ show $ Div nullAttr []

This ended up a segmenation failt with runghc.
$ runghc myfilter.hs
Div ("Segmentation fault

Funnily enough, the compiled binary works fine.
$ ./myfilter
Div ("",[],[]) []

Some tweeking with lldb tells the segv happend at Data.Text.
$ lldb -- ~/.ghcup/ghc/9.4.4/lib/ghc-9.4.4/bin/runhaskell ./myfilter.hs
(snip)
...
CodeBlock ("Process 362618 stopped
* thread #5, name = 'ghc:w', stop reason = signal SIGSEGV: invalid address (fault address: 0x0)
    frame #0: 0x00007fffed56a12c libHStext-2.0.1-ghc9.4.4.so
->  0x7fffed56a12c: jmpq   *(%rbx)
    0x7fffed56a12e: nop
    0x7fffed56a130: addl   %eax, (%rax)
    0x7fffed56a132: addb   %al, (%rax)

This gave me a curious inspiration of forcing precedences by adding $.
import Text.Pandoc.Definition

main = do
  putStrLn $ show $ Div nullAttr $ []

And it just worked even with runghc without any segv!

Very strange...I can't say what's going on here.

repo: jgm/pandoc-types


text:
Problem parsing IE hacks

Found another issue, and I realise this is not really on you, but rather in scss-parser but it doesn't seem to be open source.
If you have a style such as
&:focus {
   outline: 0;
   outline: thin dotted \9; /* IE6-9 */
}

scss-parser will throw an error trying to parse the \:
Unhandled rejection Error: Can't handle character: "\" (39:25)
    at InputStream.err (C:\myproj\node_modules\scss-parser\dist\input-stream.js:122:13)
    at Object.err (C:\myproj\node_modules\scss-parser\dist\input-stream.js:161:20)
    at TokenStream.err (C:\myproj\node_modules\scss-parser\dist\token-stream.js:297:40)
    at TokenStream.read_next (C:\myproj\node_modules\scss-parser\dist\token-stream.js:352:12)
    at TokenStream.peek (C:\myproj\node_modules\scss-parser\dist\token-stream.js:254:27)
    at Object.peek (C:\myproj\node_modules\scss-parser\dist\token-stream.js:625:21)
    at C:\myproj\node_modules\scss-parser\dist\parse.js:90:30
    at Array.reduce (<anonymous>)
    at Parser.is_type (C:\myproj\node_modules\scss-parser\dist\parse.js:89:21)
    at Parser.is_punctuation (C:\myproj\node_modules\scss-parser\dist\parse.js:128:27)
    at Parser.is_interpolation (C:\myproj\node_modules\scss-parser\dist\parse.js:176:19)
    at C:\myproj\node_modules\scss-parser\dist\parse.js:426:20
    at Parser.maybe_function (C:\myproj\node_modules\scss-parser\dist\parse.js:609:14)
    at Parser.parse_atom (C:\myproj\node_modules\scss-parser\dist\parse.js:420:19)
    at Parser.parse_node (C:\myproj\node_modules\scss-parser\dist\parse.js:353:25)
    at Parser.parse_block (C:\myproj\node_modules\scss-parser\dist\parse.js:539:25)

For what it's worth I hate these dodgy style hacks but I didn't write it 😄
Replacing this token with an empty string before calling  (0, _scssParser.parse) in parse.js makes the parser happy again

This is fixed in the latest 2.0.0 release. Thank you for reporting it!

authors: JoshSchreuder jgranstrom

repo: jgranstrom/sass-extract


text:
How to associate xml files with desktop app?

When I want to edit graph with this app, I hope to click demo.xml file rather than lanuch app first and then open demo.xml file.
the following maybe a solution but not available now:
chrome.exe  --profile-directory=Default --app-id=pebppomjfocnoigkeepgbmcifnnlndla demo.xml

By any chance, is there any plan to switch to an extension specific to draw.io, such as .drawio?

Yes. As a workaround you can click on the filename and change it to *.drawio (or any other custom extension).

I was suggesting the possibility for draw.io to produce by default a .drawio file instead of a .xml file when saving a figure :)

The original issue for this thread still exists on OSX. Regardless of the extension, once an association is made in OSX, double clicking the file brings the draw.io desktop app to the foreground but doesn't load the file.

Almost 2 years now since this ticket was opened.
I see if you search by most commented, this issue is number 1: https://github.com/jgraph/drawio/issues?q=is%3Aissue+is%3Aopen+sort%3Acomments-desc
It would be great if you guys could prioritize a fix.

Duplicate of https://github.com/jgraph/drawio-desktop/issues/11

authors: Gwend4l JesseAldridge alderg g-mu seasonxuan

repo: jgraph/drawio


text:
get the corresponding DOM element of the selected 'cell'

[ ] I agree to follow the Code of Conduct that this project adheres to.

questions
Hello everyone
Is there a way to get the corresponding DOM element of the selected 'cell'?
thus DOM elements can be manipulated
thx

How do I manipulate a Cell's corresponding DOM element

Hello. I need too. I want to add a handler to add the functionality I need, but I don't know how to pass the selected diagram elements to the function.
Thx


text:
Connect to an Edge (not connection point or object) to ensure connection lines stay straight

[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Is your feature request related to a problem? Please describe.
Drawing block diagrams that have lots of lines going into a box (etc.) it's a pain to get all the lines straight.
At the moment, you can connect to either the entire object, or to a point on the edge of that object. But...
Describe the solution you'd like
It would be brilliant to be able to be able to drag a line onto a side of an object, and the line just goes straight (horizontally or vertically) into it. Here's a mockup:

Then... with these three circles connected to the bottom edge of the box, I could resize or move either the box or any of the circles... and the lines would stay perfectly straight... until they moved out of bounds of course, at which point the line would curve as required.
This means that diagrams would stay beautifully ordered, without having to line up connection points perfectly.

This seems to be implemented with the addition of these two new line types.

That said, it seems that the tooltips are wrong (they're all set to say "Simple".


text:
Shape-texts overlay in IE 11

Take 2 shapes with random text and give them the same position on the graph. In IE(11) the text from the underlying shape shines through.
FF 57.0.1 (64-Bit) and Chrome Version 64.0.3282.71 (Official Build) beta (64-Bit) show correct behaviour.
Is any workaround available?

What is the exact workaround here?

It's not really a workaround, it's just HTML. The SVG DOM is always "behind" in z-order, thus HTML labels alway overlay in front.

authors: AndreasSchul arundhatikan6 davidjgraph

repo: jgraph/mxgraph


text:
Implement configuration file

Currently, tests are defined and configured within the application logic. Break these out into an external configuration file.

Resolved in pull request last week

repo: jhandfield/supreme-pancake


text:
Fix installation error by upgrading remotedev-server

With a fresh yarn or npm cache, remotedev-rn-debugger cannot be installed. Yarn fails with
error An unexpected error occurred: "https://registry.yarnpkg.com/uws/-/uws-0.13.0.tgz: Request failed \"404 Not Found\"".

The problem is that uws@0.13.0 has been removed from yarn/npm (they call it archived here https://github.com/uNetworking/uWebSockets/releases) and socketcluster@5.x depends on uws@0.13.0...
It doesn't look like the breaking changes in socketcluster@6 will have any effect. See https://github.com/SocketCluster/socketcluster/releases/tag/v6.0.1
See https://github.com/zalmoxisus/remotedev-server/pull/45#event-1237438733

Thanks. :)

Thanks for the quick feedback!

@jhen0409 when do you plan to release this?

@skovhus, for the patch version of dependencies you can run yarn upgrade remotedev-rn-debugger or re-install. I think this PR just ensure people to use ^0.2.4.


text:
Conflict when an entity has two image fields

The is a conflict when an entity has two image fields.
The code was generated for an angular application.
There is only one fileInput in the -update.ts:
@ViewChild('fileInput', { static: false }) fileInput;
And in getPicture() method this.fileInput.nativeElement.click(); is called.
Both  fields from -update.html have #fileInput.
The result is that only the first entity image field can be set, regardless of which button is pressed in the UI.

I'm not ignoring this issue, I've just been really busy lately. I don't know when I'll get to this issue, but it'll be on my radar until I do. :)

@Luca1234 I won't be able to get to this until January. I'll add a bug bounty in case someone else wants to fix it in the meantime.

Hi all,
I'm a follower of ionic framework, and I have already worked on this blueprint in the past.
If there are not problems, I can investigate on this issue trying of resolving its (I worked on a old version of jhipster-ionic)

@amanganiello90 If you'd like to work on this issue, please go ahead. I'd be happy to QA when you're finished.

$100 bug bounty claim: https://opencollective.com/generator-jhipster/expenses/131589

repo: jhipster/generator-jhipster-ionic


text:
Fix #1492:Attributes equals now is order sensitive

Since Attributes are implemented by map, so the comparison can be realized by calling equals() for map in the function equals() in Attributes.java

Thanks and sorry for the late reply.
This implementation doesn't work, because dataset() is a filtered list of attributes that start with "data-".
You're basically making equals() return true for every attribute set that does not include data- attributes.
Generally it's a good idea when writing test cases to include negative cases (in this case, things that should not be equal) to catch that kind of error.

authors: jhy zoey-shan

repo: jhy/jsoup


text:
New feature: Remove green menu

Not to be rude, but some people really shoudn't have a green menu in their cars... I get many many mails on a daily basis from people who think they don't need to read any manual or warning, and mess up their systems... 🤕
These people really need a button that removes the entire green menu and all of its features.
I think it's best if this will be a button with the name "FIX ALL YOUR ISSUES" 😜

Agree with that!

It's insane... the response I get is either:

someone not reading anything and messing up his unit because of it
someone demanding a toolbox for MIB2STD RIGHT NOW 😨

authors: hxigor jilleb


text:
SearchRequest using database_code

According to the docs here: https://www.quandl.com/docs/api#dataset-search we can use the search endpoint to get all the datasets within a database by hitting something like datasets.csv?database_code=WIKI. I'd like to submit a pull request enabling this functionality, unfortunately with the current implementation, the Query parameter is required even though it's not required according to the docs. In order to enable the database only query we'd need the Query parameter to not be required.
I'm not sure if there's a nice way to enable this workflow with the exception of breaking backwards compatibility. What are your thoughts on doing that? I'm also happy to try something else if you have a better suggestion.

So the reason the current docs are different is that it's a different API
version being supported. I hit the v1 endpoints. We should move to v3
though (from what I can tell v2 was internal or something). My suggestion
to resolve this but retain compatibility is:

@Deprecate the of(query) static factory.
Add a public no-arg constructor to the builder.
Add with() methods for query and database code to the builder.
Add appropriate optional handling of query and database code arguments to
the request builder.
Make sure the request hits the v3 endpoint.
figure out what else needs updating and at least create issues.

If there's any of that you can put in a pull request, I'll happily review
it. If you do, it would be helpful if you could match the code style.
Have I missed anything?
Cheers,
Jim
On 1 Nov 2015 3:52 am, "hkothari" notifications@github.com wrote:

According to the docs here: https://www.quandl.com/docs/api#dataset-search
we can use the search endpoint to get all the datasets within a database by
hitting something like datasets.csv?database_code=WIKI. I'd like to submit
a pull request enabling this functionality, unfortunately with the current
implementation, the Query parameter is required even though it's not
required according to the docs. In order to enable the database only query
we'd need the Query parameter to not be required.
I'm not sure if there's a nice way to enable this workflow with the
exception of breaking backwards compatibility. What are your thoughts on
doing that? I'm also happy to try something else if you have a better
suggestion.
—
Reply to this email directly or view it on GitHub
https://github.com/jimmoores/quandl4j/issues/12.

First attempt at a PR here: https://github.com/jimmoores/quandl4j/pull/13

I've refactored the examples, javadocs and tutorial and added your github user to the contributors file.  Let me know if your full name if you want that included.
Thanks again!
Jim

My full name is Hamel Ajay Kothari, I'll add it with my next PR whenever that comes around :)

authors: hkothari jimmoores


text:
Feature: Save Current data Button | Import & Export Data

As the Service works on device to device locally, I want to work on the button which allows the user to one click download all the passwords in a single Document File.
This Feature can also be further enhanced as import and export passwords feature,

@jindalpriyanshu101 @jinx-vi-0 Can I work on this? Also add the appropriate tags on the issue

Assigned @AskitEndo


text:
now doesn't account for DST

Hey,
I'm in central Europe, and we currently still have daylight saving time (timezone CEST instead of CET).
now doesn't seem to account for the extra hour, so now.BeginningOfYear() currently returns 2014-12-31 23:00:00 +0100 CET instead of midnight.
Greets,
Bobselp

+1
Just ran into this myself - had a program which uses beginning and end of month stop working because multi-month spans were being returned due to BeginningOfMonth.

@Bobselp @wrouesnel: http://www.timeanddate.com/time/zones/cest
it says "CEST is currently not used at all"?

@SDkie CEST was over on October 25th. It will begin again on March 27th 2016.

As @Bobselp said this issue just appeared again. If you try to do today : now.BeginningOfDay() you will get 2016-03-26 23:00:00 +0000 WET

+1 this bit me today too.
package main
import (
	"fmt"
	"time"
	"github.com/jinzhu/now"
)

func main() {
	fmt.Println(now.New(time.Date(2016, 11, 6, 0, 0, 0, 0, time.Local)).EndOfMonth())
	fmt.Println(now.New(time.Date(2016, 11, 7, 0, 0, 0, 0, time.Local)).EndOfMonth())
}

results in
2016-11-30 23:59:59.999999999 -0500 EST
2016-12-01 00:59:59.999999999 -0500 EST

Mandatory link because the implementation of this library wrongly assumes that days are always 24h long:
http://infiniteundo.com/post/25509354022/more-falsehoods-programmers-believe-about-time

Fixed by PR #21 , sorry for the problem.

authors: Bobselp PolyviosT SDkie dolmen jinzhu kmanley wrouesnel

repo: jinzhu/now


text:
Spellcheck?

Does monologue not support spellcheck? It seemed like the default installation didn't have it which seemed a bit weird.

Good question! I don't think so. @msevestre sounds familiar?

nope. I always assumed this would be something out of the box
On Fri, Nov 25, 2016 at 12:04 AM Jean-Philippe Boily <
notifications@github.com> wrote:

Good question! I don't think so. @msevestre https://github.com/msevestre
sounds familiar?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jipiboily/monologue/issues/302#issuecomment-262881418,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA_jVcge7-BJUrQSvCf0ovFR2Bb-I69Fks5rBmxggaJpZM4K7Iyk
.

I know TinyMCE supports a lot more functionality that the current RCE that you are using doesn't have. I'm more familiar with it so I'm biased towards it but if you want to migrate toward having that as the 'base' RCE functionality I wouldn't be opposed to adding that as a pull request. Here is the spellcheck plugin they use - https://www.tinymce.com/docs/plugins/spellchecker/
What rich content editor do you guys use so I could double check if something existing is present we can plug in?

Ah. ckeditor - really hard to find that dependency! Looking at spellcheck options.

Might want to put that in the readme somewhere?

http://docs.ckeditor.com/#!/guide/dev_spellcheck
Seems spellcheck is disabled by default, I'll open a PR with this config option enabled.

Sounds good, thanks!
JP Boily
PS: Want to get the most out of Google Analytics? Get our free email
course http://metricswatch.com/free-5-part-email-course/.
Founder @ Metrics Watch - Reports & Alerts for Google Analytics
Check out our new product "Email Reports for Agencies
http://metricswatch.com/email-reports-for-agencies/" - Send weekly
Google Analytics reports to your all your clients, with your name and logo.
Want to share some news or events with your customer? Add it to their
weekly report! Happy to jump on a quick 15 minutes call for a demo
https://calendly.com/metricswatch/report-for-agencies-demo.
On Sat, Nov 26, 2016 at 8:01 PM, Ben Nelson notifications@github.com
wrote:

http://docs.ckeditor.com/#!/guide/dev_spellcheck
Seems spellcheck is disabled by default, I'll open a PR with this config
option enabled.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jipiboily/monologue/issues/302#issuecomment-263095498,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOOIb8-JAw3Ie_vCHLFbCtkNcL6Ji9jks5rCNZjgaJpZM4K7Iyk
.

authors: illegalnumbers jipiboily msevestre

repo: jipiboily/monologue


text:
Can't build app in profile mode

Dears,
I am not able to build app in profile mode though it is working in debug and release.
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':jitsi_meet_flutter_sdk:generateProfileRFile'.
> Could not resolve all files for configuration ':jitsi_meet_flutter_sdk:profileCompileClasspath'.
   > Could not resolve com.facebook.react:react-android:0.72.9.
     Required by:
         project :jitsi_meet_flutter_sdk > org.jitsi.react:jitsi-meet-sdk:9.2.2
         project :jitsi_meet_flutter_sdk > com.facebook.react:react-native-amplitude:2.7.0-jitsi-16757212
         project :jitsi_meet_flutter_sdk > com.facebook.react:react-native-giphy:2.3.0-jitsi-16757212
         project :jitsi_meet_flutter_sdk > com.facebook.react:react-native-google-signin:10.1.0-jitsi-16757212
         project :jitsi_meet_flutter_sdk > com.facebook.react:react-native-async-storage:1.19.4-jitsi-16757212
         project :jitsi_meet_flutter_sdk > com.facebook.react:react-native-background-timer:2.4.1-jitsi-16757212
         project :jitsi_meet_flutter_sdk > com.facebook.react:react-native-calendar-events:2.2.0-jitsi-16757212
         project :jitsi_meet_flutter_sdk > com.facebook.react:react-native-community_clipboard:1.5.1-jitsi-16757212
         project :jitsi_meet_flutter_sdk > com.facebook.react:react-native-community_netinfo:11.1.0-jitsi-16757212
         project :jitsi_meet_flutter_sdk > com.facebook.react:react-native-default-preference:1.4.4-jitsi-16757212
         project :jitsi_meet_flutter_sdk > com.facebook.react:react-native-device-info:10.9.0-jitsi-16757212
         project :jitsi_meet_flutter_sdk > com.facebook.react:react-native-gesture-handler:2.9.0-jitsi-16757212
         project :jitsi_meet_flutter_sdk > com.facebook.react:react-native-get-random-values:1.9.0-jitsi-16757212
         project :jitsi_meet_flutter_sdk > com.facebook.react:react-native-immersive-mode:2.0.1-jitsi-16757212
         project :jitsi_meet_flutter_sdk > com.facebook.react:react-native-keep-awake:4.0.0-jitsi-16757212
         project :jitsi_meet_flutter_sdk > com.facebook.react:react-native-orientation-locker:1.6.0-jitsi-16757212
         project :jitsi_meet_flutter_sdk > com.facebook.react:react-native-pager-view:6.2.0-jitsi-16757212
         project :jitsi_meet_flutter_sdk > com.facebook.react:react-native-performance:5.0.0-jitsi-16757212
         project :jitsi_meet_flutter_sdk > com.facebook.react:react-native-safe-area-context:4.7.1-jitsi-16757212
         project :jitsi_meet_flutter_sdk > com.facebook.react:react-native-screens:3.24.0-jitsi-16757212
         project :jitsi_meet_flutter_sdk > com.facebook.react:react-native-slider:4.4.3-jitsi-16757212
         project :jitsi_meet_flutter_sdk > com.facebook.react:react-native-sound:0.11.2-jitsi-16757212
         project :jitsi_meet_flutter_sdk > com.facebook.react:react-native-splash-screen:3.3.0-jitsi-16757212
         project :jitsi_meet_flutter_sdk > com.facebook.react:react-native-svg:13.13.0-jitsi-16757212
         project :jitsi_meet_flutter_sdk > com.facebook.react:react-native-video:6.0.0-alpha.11-jitsi-16757212
         project :jitsi_meet_flutter_sdk > com.facebook.react:react-native-webrtc:118.0.7-jitsi-16757212
         project :jitsi_meet_flutter_sdk > com.facebook.react:react-native-webview:13.5.1-jitsi-16757212
      > No matching variant of com.facebook.react:react-android:0.72.9 was found. The consumer was configured to find a library for use during compile-time
, preferably optimized for Android, as well as attribute 'com.android.build.api.attributes.AgpVersionAttr' with value '8.7.0', attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'profile', attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm' but:
          - Variant 'debugVariantDefaultApiPublication' declares a library for use during compile-time:
              - Incompatible because this component declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug' and the consumer needed a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'profile'
              - Other compatible attributes:
                  - Doesn't say anything about com.android.build.api.attributes.AgpVersionAttr (required '8.7.0')
                  - Doesn't say anything about its target Java environment (preferred optimized for Android)
                  - Doesn't say anything about org.jetbrains.kotlin.platform.type (required 'androidJvm')
          - Variant 'debugVariantDefaultRuntimePublication' declares a library for use during runtime:
              - Incompatible because this component declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug' and the consumer needed a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'profile'
              - Other compatible attributes:
                  - Doesn't say anything about com.android.build.api.attributes.AgpVersionAttr (required '8.7.0')
                  - Doesn't say anything about its target Java environment (preferred optimized for Android)
                  - Doesn't say anything about org.jetbrains.kotlin.platform.type (required 'androidJvm')
          - Variant 'debugVariantDefaultSourcePublication' declares a component for use during runtime:
              - Incompatible because this component declares documentation, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug' and the consumer needed a library, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'profile'
              - Other compatible attributes:
                  - Doesn't say anything about com.android.build.api.attributes.AgpVersionAttr (required '8.7.0')
                  - Doesn't say anything about its target Java environment (preferred optimized for Android)
                  - Doesn't say anything about org.jetbrains.kotlin.platform.type (required 'androidJvm')
          - Variant 'releaseVariantDefaultApiPublication' declares a library for use during compile-time:
              - Incompatible because this component declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release' and the consumer needed a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'profile'
              - Other compatible attributes:
                  - Doesn't say anything about com.android.build.api.attributes.AgpVersionAttr (required '8.7.0')
                  - Doesn't say anything about its target Java environment (preferred optimized for Android)
                  - Doesn't say anything about org.jetbrains.kotlin.platform.type (required 'androidJvm')
          - Variant 'releaseVariantDefaultRuntimePublication' declares a library for use during runtime:
              - Incompatible because this component declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release' and the consumer needed a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'profile'
              - Other compatible attributes:
                  - Doesn't say anything about com.android.build.api.attributes.AgpVersionAttr (required '8.7.0')
                  - Doesn't say anything about its target Java environment (preferred optimized for Android)
                  - Doesn't say anything about org.jetbrains.kotlin.platform.type (required 'androidJvm')
          - Variant 'releaseVariantDefaultSourcePublication' declares a component for use during runtime:
              - Incompatible because this component declares documentation, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release' and the consumer needed a library, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'profile'
              - Other compatible attributes:
                  - Doesn't say anything about com.android.build.api.attributes.AgpVersionAttr (required '8.7.0')
                  - Doesn't say anything about its target Java environment (preferred optimized for Android)
                  - Doesn't say anything about org.jetbrains.kotlin.platform.type (required 'androidJvm')

* Try:
> No matching variant errors are explained in more detail at https://docs.gradle.org/8.10.2/userguide/variant_model.html#sub:variant-no-match.
> Review the variant matching algorithm at https://docs.gradle.org/8.10.2/userguide/variant_attributes.html#sec:abm_algorithm.
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

BUILD FAILED in 58s
Running Gradle task 'assembleProfile'...                           59.3s
Error: Gradle task assembleProfile failed with exit code 1
#0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
#1      AndroidGradleBuilder.buildGradleApp (package:flutter_tools/src/android/gradle.dart:497:9)
<asynchronous suspension>
#2      AndroidGradleBuilder.buildApk (package:flutter_tools/src/android/gradle.dart:220:5)
<asynchronous suspension>
#3      AndroidDevice.startApp (package:flutter_tools/src/android/android_device.dart:584:7)
<asynchronous suspension>
#4      FlutterDevice.runCold (package:flutter_tools/src/resident_runner.dart:525:33)
<asynchronous suspension>
#5      ColdRunner.run (package:flutter_tools/src/run_cold.dart:53:28)
<asynchronous suspension>
#6      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:850:27)
<asynchronous suspension>
#7      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1450:27)
<asynchronous suspension>
#8      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
<asynchronous suspension>
#9      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
<asynchronous suspension>
#10     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:421:9)
<asynchronous suspension>
#11     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
<asynchronous suspension>
#12     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:364:5)
<asynchronous suspension>
#13     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:130:9)
<asynchronous suspension>
#14     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
<asynchronous suspension>
#15     main (package:flutter_tools/executable.dart:94:3)
<asynchronous suspension>

flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel beta, 3.26.0-0.1.pre, on Microsoft Windows [Version 10.0.22631.4169], locale en-US)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
[√] Chrome - develop for the web
[√] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.10.4)
[√] Android Studio (version 2024.2)
[√] VS Code (version 1.94.0)
[√] Connected device (6 available)
[√] Network resources

• No issues found!

plugins{
    id "com.android.application" version "8.7.0" apply false
    id "org.jetbrains.kotlin.android" version "2.0.20" apply false
}

distributionUrl=https\://services.gradle.org/distributions/gradle-8.10.2-all.zip

compileSdk = 35
ndkVersion = "27.0.12077973"

compileOptions {
        coreLibraryDesugaringEnabled  = true
        sourceCompatibility = JavaVersion.VERSION_1_8
        targetCompatibility = JavaVersion.VERSION_1_8
    }

    kotlinOptions {
        jvmTarget = JavaVersion.VERSION_1_8
    }

We don't seem to support running in profile mode, though we haven't been able to figure out why :-/

Is there any workaround?

Not that I know of, sorry.

Finally, after some debugging, I found the solution
Change the build.gradle to this
implementation ('org.jitsi.react:jitsi-meet-sdk:10.2.1') {
        exclude group: 'com.facebook.react', module: 'react-android'
        transitive = true
    }
    implementation("com.facebook.react:react-android:0.76.0-rc.4") {
        attributes {
            attribute(Attribute.of("com.android.build.api.attributes.BuildTypeAttr", String), "release")
        }
    }

the version 0.76.0-rc.4 is the latest. You can change it as you need. but this is working.
Confirm and close this.

Please I want to know how to solve this to be able to upgrade
External screen not removed

Sorry but that's a bad idea. Our SDK relies on a specific React Native SDK. If you change that then things might break in unexpected ways.

Sorry but that's a bad idea. Our SDK relies on a specific React Native SDK. If you change that then things might break in unexpected ways.

You are right.
I found that the app crashes when start meeting
So, I put the version required by the org.jitsi.react:jitsi-meet-sdk:10.2.1 which is com.facebook.react:react-android:0.73.8 and it worked
So, it will be better using the required version with defining this attribute for it
Last edit
implementation ('org.jitsi.react:jitsi-meet-sdk:10.2.1') {
        exclude group: 'com.facebook.react', module: 'react-android'
        transitive = true
    }
    implementation("com.facebook.react:react-android:0.73.8") {
        attributes {
            attribute(Attribute.of("com.android.build.api.attributes.BuildTypeAttr", String), "release")
        }
    }

Great to know!🙏

Great to know!🙏

Will be integrated in next versions?

If it's supported out of the box in RN then we'll pick it up when we upgrade, yes.

@a7mdragab1 I think this issue should not be closed, as it has not been fixed yet.

We cannot fix it, it's a React Native thing and will be fixed with an update.

You can use this solution

You are right.
I found that the app crashes when start meeting
So, I put the version required by the org.jitsi.react:jitsi-meet-sdk:10.2.1 which is com.facebook.react:react-android:0.73.8 and it worked
So, it will be better using the required version with defining this attribute for it
Last edit
implementation ('org.jitsi.react:jitsi-meet-sdk:10.2.1') {
        exclude group: 'com.facebook.react', module: 'react-android'
        transitive = true
    }
    implementation("com.facebook.react:react-android:0.73.8") {
        attributes {
            attribute(Attribute.of("com.android.build.api.attributes.BuildTypeAttr", String), "release")
        }
    }

@a7mdragab1 I think this issue should not be closed, as it has not been fixed yet.

You can use this solution

You are right.
I found that the app crashes when start meeting
So, I put the version required by the org.jitsi.react:jitsi-meet-sdk:10.2.1 which is com.facebook.react:react-android:0.73.8 and it worked
So, it will be better using the required version with defining this attribute for it
Last edit
implementation ('org.jitsi.react:jitsi-meet-sdk:10.2.1') {
        exclude group: 'com.facebook.react', module: 'react-android'
        transitive = true
    }
    implementation("com.facebook.react:react-android:0.73.8") {
        attributes {
            attribute(Attribute.of("com.android.build.api.attributes.BuildTypeAttr", String), "release")
        }
    }

We cannot fix it, it's a React Native thing and will be fixed with an update.

I mean this kindly: This is precisely why I suggest keeping this issue open. As an “end user,” I don’t particularly care whether this Flutter package uses React behind the scenes; I only care about whether it works or not.

Fair enough.

authors: a7mdragab1 saghul saibotma

repo: jitsi/jitsi-meet-flutter-sdk


text:
line chart in linup column: add actual measurements

the lineup column that shows predictions over cycles should contain some annotation about actual measurements, if available (i.e. if there is a yield value, we want to indicate the number of the cycle, where it was introduced and the value of the yield)

such annotations can be added by including 2 columns for value and step. the naming convention is as follows:
"[col_name]_step" and "[col_name]_value" where col_name is the name of the time series column e.g. "pred_step" and "pred_value"

repo: jku-vds-lab/reaction-cime


text:
Highlight single and double citations in text

Words or sentences inside single or double citation marks  ``like this'' will be highlighted as a string.
Pretty straight-forward. Captures everything except newlines.

I think you do not need to escape  ` and " but you must check that these characters are not escaped by a backslash before matching them.

I am fine with the feature but the implementation should go to syntaxes/data/LaTeX.tmLanguage.json, see https://github.com/jlelong/vscode-latex-basics/blob/8581ce5042d5387c485d5fbc95b149b7baa883f4/syntaxes/README.md.
Moreover, the regex still has issues: [^\\] requires a character different from backslash. You need to use a negative lookbehind (?<!\\\\). See https://javascript.info/regexp-lookahead-lookbehind

authors: jlelong nilsjor

repo: jlelong/vscode-latex-basics


text:
Crashplan waiting for connection issues

Hi,
Crashplan enterprise waiting for connection issues, looks like an SSL issue not sure how to resolve it?
Brand new container deployed as follows
docker run -d
--name=crashplan-enterprise
-e USER_ID=0 -e GROUP_ID=0 -e TZ=Etc/AU -e KEEP_APP_RUNNING=1
-p 5800:5800
-v /volume1/docker/appdata/crashplan-enterprise:/config:rw
-v /volume1/Fileshare:/storage:ro
jlesage/crashplan-enterprise
See Log. many thanks!
re-event-5-1 handler.AppProtocolStartListener] SABRE:: Channel failed to reach state for app protocol start. reason=javax.net.ssl.SSLHandshakeException: (SERVER) Not Trusted.  Reasons: {Sabre Trust Manager: CertificateException->java.security.cert.CertificateException: Not Trusted - Invalid CN of 'Unknown'. }, {Whitelist: CertificateException->server certificate with unknown fingerprint: CN=Unknown, OU=PROe Server, O=Code42, L=Minneapolis, ST=Minnesota, C=US}, {DefaultTrustStore: ValidatorException->PKIX path building failed: java.security.cert.CertPathBuilderException: Unable to find certificate chain.}, channel=[id: 0x46f6feab, L:/172.17.0.2:41926 - R:/103.8.239.204:443]
[03.30.21 06:21:36.173 INFO  re-event-5-1 .handler.ChannelExceptionHandler] SABRE:: Decoder issue in channel pipeline! msg=javax.net.ssl.SSLHandshakeException: (SERVER) Not Trusted.  Reasons: {Sabre Trust Manager: CertificateException->java.security.cert.CertificateException: Not Trusted - Invalid CN of 'Unknown'. }, {Whitelist: CertificateException->server certificate with unknown fingerprint: CN=Unknown, OU=PROe Server, O=Code42, L=Minneapolis, ST=Minnesota, C=US}, {DefaultTrustStore: ValidatorException->PKIX path building failed: java.security.cert.CertPathBuilderException: Unable to find certificate chain.}. cause=java.security.cert.CertificateException: (SERVER) Not Trusted.  Reasons: {Sabre Trust Manager: CertificateException->java.security.cert.CertificateException: Not Trusted - Invalid CN of 'Unknown'. }, {Whitelist: CertificateException->server certificate with unknown fingerprint: CN=Unknown, OU=PROe Server, O=Code42, L=Minneapolis, ST=Minnesota, C=US}, {DefaultTrustStore: ValidatorException->PKIX path building failed: java.security.cert.CertPathBuilderException: Unable to find certificate chain.}. Closing ctx=ChannelHandlerContext(EXCEPTION, [id: 0x46f6feab, L:/172.17.0.2:41926 ! R:/103.8.239.204:443])
[03.30.21 06:21:36.174 INFO  re-event-5-1 .handler.ChannelLifecycleHandler] SABRE:: Channel became inactive. closedBy=THIS_SIDE, channel=[id: 0x46f6feab, L:/172.17.0.2:41926 ! R:/103.8.239.204:443], sessionState=RemotePeer-[guid=63, state=CONNECTING]; Session-[localID=1000488633526847464, remoteID=0, closed=false, expiration=null, remoteIdentity=ENDPOINT, local=null, remote=null]

Does the server you are connected to have a valid certificate ?

I haven't ever had to deal with Certs with crashplan?
Are you referring to a cert installed into our crashplan console? the server is central.crashplan.com

Hi Yes using central.crashplan.com Ive never got it working, also created the container multiple times with no resolve.

all of out other instances that run on macs have no issues, we also have instances that run in Ubunto 20.04 no issues.

When you tried to re-create the container, did you also clear the /config folder ?

I did, I trash everything each time I create a new container.

Is there a way I can reach you privately so you can provide me with a temporary account?  It would be easier if I can reproduce myself.

Thanks Jocelyn,
I actually created a ticket with crashplan, got no reply and then the
following week all instances just started working.
Really weird i know!
On Fri, Apr 16, 2021 at 12:03 PM Jocelyn Le Sage @.***>
wrote:

Is there a way I can reach you privately so you can provide me with a
temporary account? It would be easier if I can reproduce myself.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jlesage/docker-crashplan-enterprise/issues/5#issuecomment-820856607,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATOFPDQS2FWLVB7C35ZJIITTI6LH3ANCNFSM42BKSZLQ
.

--
Kind Regards
Sean Inkley
Level 2, 106 Parramatta Rd, Stanmore NSW 2048
https://maps.google.com/?q=106+Parramatta+Rd,+Stanmore+NSW+2048&entry=gmail&source=g
Phone: +61 2 9550 1110 Web: www.macumen.com.au
http://www.macumen.com.au/
This communication, including any attachments, may be confidential. If you
are not the intended
recipient, can you please contact me immediately, destroy the message, and
do not copy or use any
part of this communication or disclose anything about it.

Ok, maybe a glitch on their side.  Keep me updated if you get answers from your ticket.
I will close this issue, please reopen if needed.

repo: jlesage/docker-crashplan-enterprise


text:
Fix sliders for use with recent matplotlib

Hi,
I ran into a issue using your project with a recent version of madplotlib (matplotlib==3.10.0), the call to create the sliders failed with error message Slider.__init__() takes 5 positional arguments but 6 positional arguments (and 1 keyword-only argument) were given . I updated the calls and it works for me now, perhaps you want to consider merging.
Thank you for the fun project!

Thanks a lot for the fix!

authors: fluffyjuniorcat jlesuffleur


text:
goog.inherits JSDoc not rendering as intended

Looking at the JSDoc for goog.inherits
https://google.github.io/closure-library/api/namespace_goog.html#inherits
There is HTML pre tag for the code example that doesn't render as intended.  The pre tag ends too soon.
Here is the JSDoc in the code (closure/goog/base.js):

2204	/**
2205	 * Inherit the prototype methods from one constructor into another.
2206	 *
2207	 * Usage:
2208	 *

2209	 * function ParentClass(a, b) { }
2210	 * ParentClass.prototype.foo = function(a) { };
2211	 *
2212	 * function ChildClass(a, b, c) {
2213	 *   ChildClass.base(this, 'constructor', a, b);
2214	 * }
2215	 * goog.inherits(ChildClass, ParentClass);
2216	 *
2217	 * var child = new ChildClass('a', 'b', 'see');
2218	 * child.foo(); // This works.
2219	 *

2220	 *
2221	 * @param {!Function} childCtor Child class.
2222	 * @param {!Function} parentCtor Parent class.
2223	 */

and here is how Chrome version 48.0.2564.116 m displays it:

inherits(childCtor, parentCtor)
    code »Inherit the prototype methods from one constructor into another.Usage:  function ParentClass(a, b) { } ParentClass.prototype.foo = function(a) { };function ChildClass(a, b, c) {  ChildClass.base(this, 'constructor', a, b); } goog.inherits(ChildClass, ParentClass);var child = new ChildClass('a', 'b', 'see'); child.foo(); // This works. ParameterschildCtorFunctionChild class.parentCtorFunctionParent class.

Closure is several versions behind on dossier. This renders correctly with the latest version:

Inherit the prototype methods from one constructor into another.

Usage:

 function ParentClass(a, b) { }
 ParentClass.prototype.foo = function(a) { };

 function ChildClass(a, b, c) {
   ChildClass.base(this, 'constructor', a, b);
 }
 goog.inherits(ChildClass, ParentClass);

 var child = new ChildClass('a', 'b', 'see');
 child.foo(); // This works.

authors: glennsimon jleyba

repo: jleyba/js-dossier


text:
Dev

When submitting a pull request, make sure you do the following:

[ ] submit the PR to the dev branch on the main repo, not the master branch
[ ] include a brief description what the PR is for in the subject
[ ] in the body, explain what the PR addresses
[ ] in the body, reference the issue that it closes by number in the format Closes #000.
[ ] squash multiple commits into one and use good commit messages (https://github.com/ngOfficeUIFabric/ng-officeuifabric/blob/master/docs/guides/CODING.md#commit-messages)

Please ensure you have followed the guidelines outlined in the docs: https://github.com/ngOfficeUIFabric/ng-officeuifabric/blob/master/docs/guides/PULL-REQUESTS.md
The branch manager can handle breaking up / squashing commits and updating commit messages if you don't do it, but this will delay your PR from being merged most likely.

done also

repo: jlsfernandez/ng-officeuifabric


text:
Releasing 0.4.1 - see README.md release notes

Releasing 0.4.1 to main. Resolves issue #6.

Resolving #6


text:
Continuous Domain Tutorial Problem

Hello guys, I was just trying to run the continuous time example code. At some point I know it was working, I tested it like a month ago, but I had to format my computer, then I tried again with the github version and it's not working. Here's the important information while compiling.
ContinuousDomainTutorial.java:58: error: qualified new of static class
		TerminalFunction tf = mcGen.new ClassicMCTF();
		                      ^
ContinuousDomainTutorial.java:95: error: qualified new of static class
		TerminalFunction tf = mcGen.new ClassicMCTF();
		                      ^
ContinuousDomainTutorial.java:145: error: cannot find symbol
		ip.actionNoise = 0.;
		  ^
  symbol:   variable actionNoise
  location: variable ip of type InvertedPendulum
3 errors

HI,
I'm guessing you just updated? Last week some changes were made to make Domain generators reusable with new physics parameters without affecting previously generated domains created from the same generator object. One of the consequences of that is that ClassicMCTF is now a static class and physics parameters for the domain are wrapped within an object. I'll be updating the tutorials shortly, but here is how the code should change:
TerminalFunction tf = new MountainCar.ClassicMCTF();
ip.physParams.actionNoise = 0.;

Yeah, that was it, it solved my problem, thanks =)

authors: jmacglashan silgon

repo: jmacglashan/burlap