[PDI-16614] - Data service in CSV File Input does not work with Lazy …

…conversion active

Fixed a side effect potentially caused by BACKLOG-18754.
Ensured the number precision is not lost when conversion masks are different.

Build Completed
:white_check_mark: This pull request has passed all validations.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'core' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'core' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  core/src/main/java/org/pentaho/di/core/row/value/ValueMetaBase.java
  core/src/test/java/org/pentaho/di/core/row/value/ValueMetaBaseTest.java

Build Completed
:white_check_mark: This pull request has passed all validations.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'core' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'core' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  core/src/main/java/org/pentaho/di/core/row/value/ValueMetaBase.java
  core/src/test/java/org/pentaho/di/core/row/value/ValueMetaBaseTest.java

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'core' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'core' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  core/src/main/java/org/pentaho/di/core/row/value/ValueMetaBase.java
  core/src/test/java/org/pentaho/di/core/row/value/ValueMetaBaseTest.java

Newly Broken Tests:
org.pentaho.di.core.row.RowTest.testNormalStringConversion:
:red_circle: org.pentaho.di.core.exception.KettleValueException
org.pentaho.di.core.exception.KettleValueException:

numberValue -(5, 2) : couldn't convert Number to String
 at org.apache.maven.surefire.booter.ForkedBooter.main (ForkedBooter.java:413)
 at org.apache.maven.surefire.booter.ForkedBooter.execute (ForkedBooter.java:125)
 at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess (ForkedBooter.java:340)
 at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader (ForkedBooter.java:379)
 at org.apache.maven.surefire

org.pentaho.di.core.row.value.ValueMetaBaseTest.testConvertNumberToString:
:red_circle: org.pentaho.di.core.exception.KettleValueException
org.pentaho.di.core.exception.KettleValueException:

ValueMetaNumber Number : couldn't convert Number to String
 at org.apache.maven.surefire.booter.ForkedBooter.main (ForkedBooter.java:413)
 at org.apache.maven.surefire.booter.ForkedBooter.execute (ForkedBooter.java:125)
 at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess (ForkedBooter.java:340)
 at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader (ForkedBooter.java:379)
 at org.apache.maven.suref

org.pentaho.di.core.row.ValueMetaTest.testConvertDataNumber:
:red_circle: org.pentaho.di.core.exception.KettleValueException
org.pentaho.di.core.exception.KettleValueException:

tgt Number(12, 4) : couldn't convert Number to String
 at org.apache.maven.surefire.booter.ForkedBooter.main (ForkedBooter.java:413)
 at org.apache.maven.surefire.booter.ForkedBooter.execute (ForkedBooter.java:125)
 at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess (ForkedBooter.java:340)
 at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader (ForkedBooter.java:379)
 at org.apache.maven.surefire.j

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes: -2.9% (click to expand)
:new: org.pentaho.di.trans.step.mqtt.MQTTConstants

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.step.mqtt.MQTTConsumer

Line Coverage: 78.6% :exclamation:

:new: org.pentaho.di.trans.step.mqtt.MQTTConsumerDialog

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.step.mqtt.MQTTConsumerMeta

Branch Coverage: 50% :exclamation:
Complexity Coverage: 58.2% :exclamation:

:new: org.pentaho.di.trans.step.mqtt.MqttDialogOptionsLayout

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.step.mqtt.MqttDialogSecurityLayout

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.step.mqtt.MQTTProducer

Branch Coverage: 59.1% :exclamation:
Complexity Coverage: 56.5% :exclamation:

:new: org.pentaho.di.trans.step.mqtt.MQTTProducerDialog

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.step.mqtt.MQTTProducerMeta

Branch Coverage: 50% :exclamation:
Complexity Coverage: 28.6% :exclamation:
Instruction Coverage: 70.3% :exclamation:
Line Coverage: 74.5% :exclamation:
Method Coverage: 76.9% :exclamation:

:new: org.pentaho.di.trans.step.mqtt.MQTTStreamSource

Branch Coverage: 75% :exclamation:

:new: org.pentaho.di.trans.steps.aggregaterows.AggregateRows

Branch Coverage: 36.2% :exclamation:
Complexity Coverage: 30.3% :exclamation:
Instruction Coverage: 55.2% :exclamation:
Line Coverage: 60.5% :exclamation:

:new: org.pentaho.di.trans.steps.aggregaterows.AggregateRowsMeta

Branch Coverage: 0% :exclamation:
Complexity Coverage: 2.2% :exclamation:
Instruction Coverage: 10.4% :exclamation:
Line Coverage: 7.6% :exclamation:
Method Coverage: 4.5% :exclamation:

:new: org.pentaho.di.ui.trans.steps.aggregaterows.AggregateRowsDialog

Coverage: 0% :exclamation:

:new: org.pentaho.di.job.entries.abort.JobEntryAbort

Branch Coverage: 0% :exclamation:
Complexity Coverage: 58.8% :exclamation:
Instruction Coverage: 41.9% :exclamation:
Line Coverage: 47.2% :exclamation:
Method Coverage: 62.5% :exclamation:

:new: org.pentaho.di.job.entries.addresultfilenames.JobEntryAddResultFilenames

Branch Coverage: 5.3% :exclamation:
Complexity Coverage: 18.6% :exclamation:
Instruction Coverage: 24% :exclamation:
Line Coverage: 28.6% :exclamation:
Method Coverage: 52.4% :exclamation:

Note: The list of offending coverage changes extends beyond the presented results and was truncated to prevent reaching the comment size limit.

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'core' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'core' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  core/src/main/java/org/pentaho/di/core/row/value/ValueMetaBase.java
  core/src/test/java/org/pentaho/di/core/row/value/ValueMetaBaseTest.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.di.core.row.value.ValueMetaBase

Complexity Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.ifnull.IfNullMeta

Branch Change: -2% :small_red_triangle_down:
Complexity Change: -1.9% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change: -1.1% :small_red_triangle_down:
Complexity Change: -1.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.singlethreader.SingleThreaderMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.symmetriccrypto.symmetriccryptotrans.SymmetricCryptoTransMeta

Branch Change: -3.3% :small_red_triangle_down:
Complexity Change: -1.8% :small_red_triangle_down:
Instruction Change: -0.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.uniquerows.UniqueRowsMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.gpload.GPLoadMeta

Branch Change: -0.9% :small_red_triangle_down:
Complexity Change: -0.8% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.salesforceinsert.SalesforceInsertMeta

Instruction Change: -0.1% :small_red_triangle_down:

Checkstyle violations
The code submitted is not complying with one or more of our guidelines. To perform these checks locally, please use this tool.
/home/buildguy/project/core/src/main/java/org/pentaho/di/core/row/value/ValueMetaBase.java

:heavy_exclamation_mark: '&&' should be on a new line. at Line: 994 Column: 67

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'core' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'core' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  core/src/main/java/org/pentaho/di/core/row/value/ValueMetaBase.java
  core/src/test/java/org/pentaho/di/core/row/value/ValueMetaBaseTest.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.di.core.row.value.ValueMetaBase

Complexity Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.checksum.CheckSumMeta

Branch Change: -1.3% :small_red_triangle_down:
Complexity Change: -1.4% :small_red_triangle_down:
Instruction Change: -0.4% :small_red_triangle_down:

org.pentaho.di.job.entries.waitforsql.JobEntryWaitForSQL

Branch Change: -0.8% :small_red_triangle_down:
Complexity Change: -1% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.step.StepMeta

Branch Change: -0.6% :small_red_triangle_down:
Complexity Change: -0.6% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:
Line Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.dimensionlookup.DimensionLookupMeta

Method Change: -1% :small_red_triangle_down:

org.pentaho.di.trans.steps.groupby.GroupByMeta

Branch Change: -1.1% :small_red_triangle_down:
Complexity Change: -1% :small_red_triangle_down:

org.pentaho.di.trans.steps.replacestring.ReplaceStringMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.sortedmerge.SortedMergeMeta

Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.textfileinput.TextFileInputMeta

Branch Change: -0.5% :small_red_triangle_down:

org.pentaho.di.trans.steps.gpload.GPLoadMeta

Branch Change: -0.9% :small_red_triangle_down:
Complexity Change: -0.8% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.salesforceinsert.SalesforceInsertMeta

Instruction Change: -0.1% :small_red_triangle_down:

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'core' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'core' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  core/src/main/java/org/pentaho/di/core/row/value/ValueMetaBase.java
  core/src/test/java/org/pentaho/di/core/row/value/ValueMetaBaseTest.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.di.core.logging.BufferLine

Complexity Change: -20% :small_red_triangle_down:
Instruction Change: -11.5% :small_red_triangle_down:
Line Change: -12.5% :small_red_triangle_down:
Method Change: -20% :small_red_triangle_down:

org.pentaho.di.core.logging.LoggingBuffer

Branch Change: -6.2% :small_red_triangle_down:
Complexity Change: -1.9% :small_red_triangle_down:
Instruction Change: -2.1% :small_red_triangle_down:
Method Change: -2.6% :small_red_triangle_down:

org.pentaho.di.core.row.value.ValueMetaBase

Complexity Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.checksum.CheckSumMeta

Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.core.auth.core.impl.DefaultAuthenticationConsumerFactory

Branch Change: -7.2% :small_red_triangle_down:
Complexity Change: -7.7% :small_red_triangle_down:

org.pentaho.di.core.injection.bean.BeanInjector

Branch Change: -0.8% :small_red_triangle_down:
Complexity Change: -1.2% :small_red_triangle_down:

org.pentaho.di.job.entries.evalfilesmetrics.JobEntryEvalFilesMetrics

Branch Change: -0.8% :small_red_triangle_down:
Complexity Change: -1% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.job.entries.getpop.MailConnectionMeta

Branch Change: -1% :small_red_triangle_down:
Complexity Change: -1.5% :small_red_triangle_down:
Instruction Change: -0.3% :small_red_triangle_down:

org.pentaho.di.job.entries.sql.JobEntrySQL

Instruction Change: -3.4% :small_red_triangle_down:
Line Change: -3.8% :small_red_triangle_down:

org.pentaho.di.trans.steps.csvinput.CsvInputMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.ldapoutput.LDAPOutputMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change: -1.1% :small_red_triangle_down:
Complexity Change: -1.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.replacestring.ReplaceStringMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.rowgenerator.RowGeneratorMeta

Branch Change: -2.6% :small_red_triangle_down:
Complexity Change: -1.5% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.symmetriccrypto.symmetriccryptotrans.SymmetricCryptoTransMeta

Branch Change: -3.3% :small_red_triangle_down:
Complexity Change: -1.8% :small_red_triangle_down:
Instruction Change: -0.3% :small_red_triangle_down:

Note: The list of offending coverage changes extends beyond the presented results and was truncated to prevent reaching the comment size limit.

Build Failed
:x: Something went wrong while validating this pull request.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'core' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Stdout log
(last 100 lines)
[INFO]
[INFO] --- build-helper-maven-plugin:3.0.0:remove-project-artifact (default-cli) @ pdi-xml-plugin ---
[INFO] /home/buildguy/.m2/repository/org/pentaho/di/plugins/pdi-xml-plugin removed.
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building pentaho-jms-plugin Blueprint Bundle <IP_ADDRESS>-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- build-helper-maven-plugin:3.0.0:remove-project-artifact (default-cli) @ pentaho-streaming-jms-plugin ---
[INFO] /home/buildguy/.m2/repository/org/pentaho/di/plugins/pentaho-streaming-jms-plugin removed.
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building MQTT Streaming Step Plugin Bundle <IP_ADDRESS>-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- build-helper-maven-plugin:3.0.0:remove-project-artifact (default-cli) @ pentaho-streaming-mqtt-plugin ---
[INFO] /home/buildguy/.m2/repository/org/pentaho/di/plugins/pentaho-streaming-mqtt-plugin removed.
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Pentaho Streaming Plugin Feature <IP_ADDRESS>-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- build-helper-maven-plugin:3.0.0:remove-project-artifact (default-cli) @ pentaho-streaming-feature ---
[INFO] /home/buildguy/.m2/repository/org/pentaho/di/plugins/pentaho-streaming-feature removed.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] PDI Core ........................................... SUCCESS [  6.449 s]
[INFO] PDI Engine ......................................... SUCCESS [  0.192 s]
[INFO] PDI DB Dialog ...................................... SUCCESS [  0.214 s]
[INFO] PDI User Interface ................................. SUCCESS [  0.155 s]
[INFO] PDI Log4j Plugin Core .............................. SUCCESS [  0.278 s]
[INFO] PDI Log4j Plugin Distribution ...................... SUCCESS [  0.130 s]
[INFO] PDI Core Plugins Impl .............................. SUCCESS [  0.042 s]
[INFO] PDI Core Plugins UI ................................ SUCCESS [  0.051 s]
[INFO] PDI Core Plugins Distribution ...................... SUCCESS [  0.030 s]
[INFO] PDI File Open and Save Plugin Core ................. SUCCESS [  0.225 s]
[INFO] PDI File Open and Save Plugin Distribution ......... SUCCESS [  0.263 s]
[INFO] PDI Repositories Plugin Core ....................... SUCCESS [  0.087 s]
[INFO] PDI Repositories Plugin Feature .................... SUCCESS [  0.003 s]
[INFO] PDI Metadata Injection Plugin ...................... SUCCESS [  0.075 s]
[INFO] PDI Engine Configuration Plugin API ................ SUCCESS [  0.002 s]
[INFO] PDI Engine Configuration Plugin Implementation ..... SUCCESS [  0.002 s]
[INFO] PDI Engine Configuration Plugin UI ................. SUCCESS [  0.002 s]
[INFO] PDI Engine Configuration Plugin Feature ............ SUCCESS [  0.081 s]
[INFO] PDI Get Previous Row Field Plugin Core ............. SUCCESS [  0.005 s]
[INFO] PDI Get Previous Row Field Plugin .................. SUCCESS [  0.004 s]
[INFO] PDI Aggregate Rows Plugin Core ..................... SUCCESS [  0.005 s]
[INFO] PDI Aggregate Rows Plugin Distribution ............. SUCCESS [  0.002 s]
[INFO] PDI Elasticsearch Bulk Insert Plugin Core .......... SUCCESS [  0.002 s]
[INFO] PDI Elasticsearch Bulk Insert Plugin Distribution .. SUCCESS [  0.001 s]
[INFO] PDI Google Analytics Plugin Core ................... SUCCESS [  0.004 s]
[INFO] PDI Google Analytics Plugin Distribution ........... SUCCESS [  0.002 s]
[INFO] PDI GP Bulk Loader Plugin Core ..................... SUCCESS [  0.001 s]
[INFO] PDI GP Bulk Loader Plugin Distribution ............. SUCCESS [  0.001 s]
[INFO] Pentaho Google Drive VFS Plugin Core ............... SUCCESS [  0.001 s]
[INFO] Pentaho Google Drive VFS Plugin Distribution ....... SUCCESS [  0.002 s]
[INFO] PDI HL7 Plugin Core ................................ SUCCESS [  0.001 s]
[INFO] PDI HL7 Plugin Distribution ........................ SUCCESS [  0.002 s]
[INFO] PDI Drools Plugin Core ............................. SUCCESS [  0.003 s]
[INFO] PDI Drools Plugin Distribution ..................... SUCCESS [  0.001 s]
[INFO] PDI Dummy Plugin Core .............................. SUCCESS [  0.003 s]
[INFO] PDI Dummy Plugin Distribution ...................... SUCCESS [  0.001 s]
[INFO] PDI Json Plugin Core ............................... SUCCESS [  0.003 s]
[INFO] PDI Json Plugin Distribution ....................... SUCCESS [  0.002 s]
[INFO] PDI S3 CSV Input Plugin Core ....................... SUCCESS [  0.001 s]
[INFO] PDI S3 CSV Input Plugin Distribution ............... SUCCESS [  0.001 s]
[INFO] PDI SAP Plugin Core ................................ SUCCESS [  0.002 s]
[INFO] PDI SAP Plugin Distribution ........................ SUCCESS [  0.001 s]
[INFO] PDI Shape File Reader Plugin Core .................. SUCCESS [  0.002 s]
[INFO] PDI Shape File Reader Plugin Distribution .......... SUCCESS [  0.001 s]
[INFO] PDI GPLoad Plugin Core ............................. SUCCESS [  0.002 s]
[INFO] PDI GPLoad Plugin Distribution ..................... SUCCESS [  0.001 s]
[INFO] PDI Openerp Plugin Core ............................ SUCCESS [  0.002 s]
[INFO] PDI Openerp Plugin Distribution .................... SUCCESS [  0.001 s]
[INFO] PDI Palo Plugin Core ............................... SUCCESS [  0.001 s]
[INFO] PDI Palo Plugin Distribution ....................... SUCCESS [  0.002 s]
[INFO] PDI Version Checker Plugin Core .................... SUCCESS [  0.001 s]
[INFO] PDI Version Checker Plugin Distribution ............ SUCCESS [  0.001 s]
[INFO] PDI Lucid DB Streaming Loader Plugin Core .......... SUCCESS [  0.002 s]
[INFO] PDI Lucid DB Streaming Loader Plugin Distribution .. SUCCESS [  0.001 s]
[INFO] PDI Salesforce Plugin Core ......................... SUCCESS [  0.001 s]
[INFO] PDI Salesforce Plugin Distribution ................. SUCCESS [  0.001 s]
[INFO] PDI PUR Plugin Core ................................ SUCCESS [  0.002 s]
[INFO] PDI PUR Plugin Distribution ........................ SUCCESS [  0.002 s]
[INFO] PDI MS Access Plugins Impl ......................... SUCCESS [  0.001 s]
[INFO] PDI MS Access Plugins UI ........................... SUCCESS [  0.001 s]
[INFO] PDI Ms Access Plugins Distribution ................. SUCCESS [  0.002 s]
[INFO] PDI XML Plugin Core ................................ SUCCESS [  0.001 s]
[INFO] PDI XML Plugin Distribution ........................ SUCCESS [  0.001 s]
[INFO] pentaho-jms-plugin Blueprint Bundle ................ SUCCESS [  0.002 s]
[INFO] MQTT Streaming Step Plugin Bundle .................. SUCCESS [  0.001 s]
[INFO] Pentaho Streaming Plugin Feature ................... SUCCESS [  0.001 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 53.133 s
[INFO] Finished at: 2018-06-22T17:16:33+00:00
[INFO] Final Memory: 60M/898M
[INFO] ------------------------------------------------------------------------

Stderr log
(last 100 lines)
java.lang.Exception: org.pentaho.build.buddy.bundles.orchestrator.OrchestratorImpl$BuildException: java.io.IOException: Head build returned with code 137
	at org.pentaho.build.buddy.bundles.orchestrator.OrchestratorImpl.orchestrate(OrchestratorImpl.java:381)
	at Proxyc4592c18_b83f_4150_88d7_97add644aa90.orchestrate(Unknown Source)
	at org.pentaho.build.buddy.bundles.rest.OrchestratorRestService$1.write(OrchestratorRestService.java:62)
	at org.apache.cxf.jaxrs.provider.BinaryDataProvider.writeTo(BinaryDataProvider.java:172)
	at org.apache.cxf.jaxrs.utils.JAXRSUtils.writeMessageBody(JAXRSUtils.java:1381)
	at org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor.serializeMessage(JAXRSOutInterceptor.java:244)
	at org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor.processResponse(JAXRSOutInterceptor.java:120)
	at org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor.handleMessage(JAXRSOutInterceptor.java:83)
	at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
	at org.apache.cxf.interceptor.OutgoingChainInterceptor.handleMessage(OutgoingChainInterceptor.java:83)
	at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
	at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
	at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:253)
	at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:234)
	at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:208)
	at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160)
	at org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:180)
	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:298)
	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:217)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:273)
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587)
	at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:71)
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
	at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
	at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:287)
	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
	at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:80)
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
	at org.eclipse.jetty.server.Server.handle(Server.java:499)
	at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311)
	at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
	at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544)
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
	at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
	at java.lang.Thread.run(Thread.java:748)
Caused by: org.pentaho.build.buddy.bundles.orchestrator.OrchestratorImpl$BuildException: java.io.IOException: Head build returned with code 137
	at org.pentaho.build.buddy.bundles.orchestrator.OrchestratorImpl.doOrchestrate(OrchestratorImpl.java:609)
	at org.pentaho.build.buddy.bundles.orchestrator.OrchestratorImpl.orchestrate(OrchestratorImpl.java:364)
	... 41 more
Caused by: java.io.IOException: Head build returned with code 137
	... 43 more

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'core' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'core' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  core/src/main/java/org/pentaho/di/core/row/value/ValueMetaBase.java
  core/src/test/java/org/pentaho/di/core/row/value/ValueMetaBaseTest.java

Newly Fixed Tests:
org.pentaho.di.trans.step.jms.context.ActiveMQProviderTest.testFullCircle:
:large_blue_circle: java.util.concurrent.TimeoutException
java.util.concurrent.TimeoutException
	at org.pentaho.di.trans.step.jms.context.ActiveMQProviderTest.testFullCircle(ActiveMQProviderTest.java:101)

org.pentaho.di.trans.steps.rowgenerator.RowGeneratorUnitTest.doesNotWriteRowOnTimeWhenStopped:
:large_blue_circle: java.lang.AssertionError
java.lang.AssertionError: expected:<1> but was:<9>
	at org.pentaho.di.trans.steps.rowgenerator.RowGeneratorUnitTest.doesNotWriteRowOnTimeWhenStopped(RowGeneratorUnitTest.java:107)

org.pentaho.di.trans.streaming.common.BlockingQueueStreamSourceTest.streamIsPausable:
:large_blue_circle: junit.framework.AssertionFailedError
junit.framework.AssertionFailedError
	at org.pentaho.di.trans.streaming.common.BlockingQueueStreamSourceTest.getQuickly(BlockingQueueStreamSourceTest.java:225)
	at org.pentaho.di.trans.streaming.common.BlockingQueueStreamSourceTest.streamIsPausable(BlockingQueueStreamSourceTest.java:136)

org.pentaho.di.trans.streaming.common.BlockingQueueStreamSourceTest.testRowsFilled:
:large_blue_circle: junit.framework.AssertionFailedError
junit.framework.AssertionFailedError
	at org.pentaho.di.trans.streaming.common.BlockingQueueStreamSourceTest.getQuickly(BlockingQueueStreamSourceTest.java:225)
	at org.pentaho.di.trans.streaming.common.BlockingQueueStreamSourceTest.testRowsFilled(BlockingQueueStreamSourceTest.java:169)

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes: -0.1% (click to expand)
:new: org.pentaho.di.trans.step.mqtt.MQTTConstants

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.step.mqtt.MQTTConsumer

Line Coverage: 78.6% :exclamation:

:new: org.pentaho.di.trans.step.mqtt.MQTTConsumerDialog

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.step.mqtt.MQTTConsumerMeta

Branch Coverage: 50% :exclamation:
Complexity Coverage: 58.2% :exclamation:

:new: org.pentaho.di.trans.step.mqtt.MqttDialogOptionsLayout

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.step.mqtt.MqttDialogSecurityLayout

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.step.mqtt.MQTTProducer

Branch Coverage: 59.1% :exclamation:
Complexity Coverage: 56.5% :exclamation:

:new: org.pentaho.di.trans.step.mqtt.MQTTProducerDialog

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.step.mqtt.MQTTProducerMeta

Branch Coverage: 50% :exclamation:
Complexity Coverage: 28.6% :exclamation:
Instruction Coverage: 70.3% :exclamation:
Line Coverage: 74.5% :exclamation:
Method Coverage: 76.9% :exclamation:

:new: org.pentaho.di.trans.step.mqtt.MQTTStreamSource

Branch Coverage: 75% :exclamation:

:new: org.pentaho.di.trans.steps.aggregaterows.AggregateRows

Branch Coverage: 36.2% :exclamation:
Complexity Coverage: 30.3% :exclamation:
Instruction Coverage: 55.2% :exclamation:
Line Coverage: 60.5% :exclamation:

:new: org.pentaho.di.trans.steps.aggregaterows.AggregateRowsMeta

Branch Coverage: 0% :exclamation:
Complexity Coverage: 2.2% :exclamation:
Instruction Coverage: 10.4% :exclamation:
Line Coverage: 7.6% :exclamation:
Method Coverage: 4.5% :exclamation:

:new: org.pentaho.di.ui.trans.steps.aggregaterows.AggregateRowsDialog

Coverage: 0% :exclamation:

:new: org.pentaho.di.cluster.HttpUtil

Branch Coverage: 60% :exclamation:
Complexity Coverage: 43.8% :exclamation:

:new: org.pentaho.di.cluster.SlaveConnectionManager

Complexity Coverage: 58.3% :exclamation:
Instruction Coverage: 46.5% :exclamation:
Line Coverage: 39.5% :exclamation:
Method Coverage: 55.6% :exclamation:

Note: The list of offending coverage changes extends beyond the presented results and was truncated to prevent reaching the comment size limit.


Expose a few more details of underlying backends

This commit updates the various backends to export some more information, where
all of these changes were motivated in getting the tokio-tls test suite running
again. (it's just a bunch of smoke tests really). A summary of the changes are:

Add an ErrorExt trait to each backend to lower a native_tls::Error to the
backend-specific error. This allows inspection of errors codes and such if
necessary.

Add TlsConnectorBuilderExt to the security_framework backend, with one
function called anchor_certificates. This function transitively calls the
security framework crate's anchor_certificates function to set a custom
trusted certificate for a connection. Along the way this required using the
ClientBuilder type which in turn required changes to work with async I/O.

The changes to the security framework side of things forces this crate to depend
on the changes in sfackler/rust-security-framework#23, so it shouldn't be merged
before that's updated and released!

Security Framework released.

Updated to those changes

We should eventually switch the native-tls side APIs over to version min/version max as well.

@sfackler is it possible to get a minor release with this change? It would help for testing on mac without having to use native-tls as a git dependency.

Oops, done!

Awesome, thanks so much!


fixed space between testimonial cards

for issue #573

added variableWidth: true in settings of slick to adjust space between two cards in testimonial section
attached screenshots of different screen Size

@Akshaykumar4524 After adding variable width ture, the bottom margin increases too much

@Akshaykumar4524 After adding variable width ture, the bottom margin increases too much and the left right button also shifts down

Thanks @RavindraP04  I guess adding adaptiveHeight: true, will fix this issue, I added it pls have look


Increase the usage of augmented assignment statements

:eyes: Some source code analysis tools can help to find opportunities for improving software components.
:thought_balloon: I propose to increase the usage of augmented assignment statements accordingly.
Would you like to integrate anything from a transformation result which can be generated by a command like the following?
(:point_right: Please check also for questionable change suggestions because of an evolving search pattern.)
[Markus_Elfring@fedora lokal]$ perl -p -i.orig -0777 -e 's/^(?<indentation>\s+)(?<target>\S+)\s*=\s*\k<target>[ \t]*(?<operator>[+\-%&|^@]|\*\*?|\/\/?|<<|>>)/$+{indentation}$+{target} $+{operator}=/gm' $(find ~/Projekte/Zappa/lokal -name '*.py')

:crystal_ball: How will the development interests evolve further also according to update candidates in 31 lines of this software?

Hey!
Happy to get a PR on specific changes. I'm not sure an automated solution in a CI/CD script is needed, yet

:thought_balloon: Would you dare to take another look at any generated change suggestions?

💭 Would you dare to take another look at any generated change suggestions?

Sorry, just tried the command - it doesn't return anything for me (but I'm also no perl expert :)

:thought_balloon: Did you adjust the specification “~/Projekte/Zappa/lokal” (from the command example) according to your software analysis and test environment?

yes

Can you explain the value of the results and maybe paste them here?
In any case I'd welcome you to open a pull request with potential changes 😊

:thought_balloon: You made me curious why no update candidates would be found in your test environment.
(How many Python files may be taken into account for a corresponding source code analysis in a selected directory?)
I am also looking for further possibilities to improve the mentioned transformation approach.

Happy to discuss this in dm or public channel on slack :) closing this issue for housekeeping

:thought_balloon: Can you follow the rationale from the Python enhancement proposal 203 (from 2000-07-13)?


Fix bug reencoding 9patch pngs

Fixes issue 1180.
#1180

Thanks for this. As I don't fully comprehend the inner workings of 9patch. Give me a bit to run a series of tests on images. Regressions in that past have images going darker/lighter on recompile so I don't want to run into that again.

Of course that makes sense.
The bug that I intended to fix was when the original png is encoded as a paletted image or as a gray image.  In that case, setRect() won't work because that call simply performs a memcpy().  What we really need to do is "draw" the original PNG into an RGBA output png.  The output PNG must be RGBA because of how we set the ninepatch border (and because it must "have alpha").

Sorry for the delay. I wrote a unit test to check basic properties of a 9 patch (the black border on decoded form, the 0,0 pixel and the middle part of image) to determine if

the 9patch data is retained
the color retains

https://github.com/iBotPeaches/Apktool/commit/fc43ec2470075c1652e4e66b72a13526acbfd5e2

Thanks a lot!


[FEATURE] Change TlaOperDecl to use isRecursive as a case-class parameter

Currently, TlaOperDecl delcares an isRecursive var. The problem is, it does not get copied with the default case-class copy constructor. This makes it easy to accidentally remove the recursive flag, when modifying operator declarations:
val d = TlaOperDecl("Decl",...)
d.isRecursive = true
val d2 = d.copy(name = "DeclCopy", ...) // d2.isRecursive == false !

On a similar topic, we should remove the var tag from TlaOperDecl.body

This seems to require a more major refactoring that we have thought

Shall we prioritize this refactoring? I just found that at.forsyte.apalache.tla.lir.transformations.impl.Lift hits the same bug.

Shall we prioritize this refactoring? I just found that at.forsyte.apalache.tla.lir.transformations.impl.Lift hits the same bug.


can not generate earlybound classes

in on-premise environment with command "spkl earlybound /l"
with the following errors "
The application terminated with an error.
Value cannot be null.
Parameter name: fileName "

Make sure you have done a Nuget Restore.

Apologies for bumping an old thread but I've run into this issue on two separate projects, through no fault of spkl itself.
In both of my cases, spkl was unable to find the "CrmSvcUtil.exe" in the NuGet packages directory of the project. Even triggering a NuGet Restore did not seem to bring down the necessary files. What I ended up having to do was to uninstall the spkl package, and then the Microsoft.CrmSdk.CoreTools NuGet package.
Once both were uninstalled, I just installed them in the reverse order (Microsoft.CrmSdk.CoreTools, and then spkl) and earlyboundtype generation started working again.


Can't install Turboodbc in docker enviroment

Hello I have tried to deploy an image in docker that contains the turboodbc library.
Running pip install turboodbc gives me this error.
n-38-x86_64-linux-gnu.so -Wl,-rpath,$ORIGIN
#50 327.9   /usr/bin/ld: cannot find -lturbodbc.cpython-38-x86_64-linux-gnu
#50 327.9   collect2: error: ld returned 1 exit status
#50 327.9   error: command '/usr/bin/g++' failed with exit code 1
#50 328.0   error: subprocess-exited-with-error
#50 328.0
#50 328.0   × Running setup.py install for turbodbc did not run successfully.
#50 328.0   │ exit code: 1
#50 328.0   ╰─> See above for output.
#50 328.0
#50 328.0   note: This error originates from a subprocess, and is likely not a problem with pip.
#50 328.0   full command: /usr/local/bin/python -u -c '
#50 328.0   exec(compile('"'"''"'"''"'"'
#50 328.0   # This is  -- a caller that pip uses to run setup.py
#50 328.0   #
#50 328.0   # - It imports setuptools before invoking setup.py, to enable projects that directly
#50 328.0   #   import from distutils.core to work with newer packaging standards.
#50 328.0   # - It provides a clear error message when setuptools is not installed.
#50 328.0   # - It sets sys.argv[0] to the underlying setup.py, when invoking setup.py so
#50 328.0   #   setuptools doesn'"'"'t think the script is -c. This avoids the following warning:
#50 328.0   #     manifest_maker: standard file '"'"'-c'"'"' not found".
#50 328.0   # - It generates a shim setup.py, for handling setup.cfg-only projects.
#50 328.0   import os, sys, tokenize
#50 328.0
#50 328.0   try:
#50 328.0       import setuptools
#50 328.0   except ImportError as error:
#50 328.0       print(
#50 328.0           "ERROR: Can not execute setup.py since setuptools is not available in "
#50 328.0           "the build environment.",
#50 328.0           file=sys.stderr,
#50 328.0       )
#50 328.0       sys.exit(1)
#50 328.0
#50 328.0   file = %r
#50 328.0   sys.argv[0] = file
#50 328.0
#50 328.0   if os.path.exists(file):
#50 328.0       filename = file
#50 328.0       with tokenize.open(file) as f:
#50 328.0           setup_py_code = f.read()
#50 328.0   else:
#50 328.0       filename = ""
#50 328.0       setup_py_code = "from setuptools import setup; setup()"
#50 328.0
#50 328.0   exec(compile(setup_py_code, filename, "exec"))
#50 328.0   '"'"''"'"''"'"' % ('"'"'/tmp/pip-install-bx7n_618/turbodbc_23852eb7d4d349609e69b687d99f7495/setup.py'"'"',), "", "exec"))' install --record /tmp/pip-record-wa41bumo/install-record.txt --single-version-externally-managed --user --prefix= --compile --install-headers /home/airflow/.local/include/python3.8/turbodbc
#50 328.0   cwd: /tmp/pip-install-bx7n_618/turbodbc_23852eb7d4d349609e69b687d99f7495/
#50 328.0   Running setup.py install for turbodbc: finished with status 'error'
#50 328.0 error: legacy-install-failure
#50 328.0
#50 328.0 × Encountered error while trying to install package.
#50 328.0 ╰─> turbodbc
#50 328.0
#50 328.0 note: This is an issue with the package mentioned above, not pip.
#50 328.0 hint: See above for output from the failure.

I've recently submitted a similar issue - https://github.com/blue-yonder/turbodbc/issues/351. I'm still unable to build in docker without conda.  /usr/bin/ld: cannot find -lturbodbc.cpython-38-x86_64-linux-gnu is the same short form error message as I receive. Steps to reproduce can be found in the issue.

I've closed out my issue and added a minimum viable dockerfile setup here. Hope this helps!

@david-engelmann   Thank you. I've Added the flag CFLAGS="-D_GLIBCXX_USE_CXX11_ABI=0 and my image compiles.
I share a link in case someone wants to delve into the error. https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dual_abi.html

@david-engelmann Thank you. I've Added the flag CFLAGS="-D_GLIBCXX_USE_CXX11_ABI=0 and my image compiles. I share a link in case someone wants to delve into the error. https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dual_abi.html

Love to Hear It! Happy Hackings!


solved

solved

hello,can you tell the path of Features extraction
'path-to-dataset'
'path-to-train-annos'
'path-to-test-annos'
'path-to-pretrained-c3d'
also Training and Generate ROC curve
thank you

@libb999
dataset path - download the videos to your local drive from https://visionlab.uncc.edu/download/summary/60-data/477-ucf-anomaly-detection-dataset
annotations are provided in this repository and all other data is provided in README.

@libb999
dataset path - download the videos to your local drive from https://visionlab.uncc.edu/download/summary/60-data/477-ucf-anomaly-detection-dataset
annotations are provided in this repository and all other data is provided in README.

thank you very much！now i can see the ROC curve
next, i will train it and see the result


Responsive

Is there any way to make it responsive? I want for example that the width on large screens is 40% and on xs screens 100%.
Thanks.

It worked for me by setting the className to a css class of your choosing, and setting the width as !important for all your desired breakpoints

Adding to @michelsch92 answer, I borrowed Semantic UI's modal rules and applied them to boron modal's:
@media only screen and (max-width: 767px) {
  .large.boron-modal,
  .medium.boron-modal,
  .small.boron-modal {
    width: 95% !important;
  }
}

@media only screen and (min-width: 768px) {
  .large.boron-modal,
  .medium.boron-modal {
    width: 88% !important;
  }

  .small.boron-modal {
    width: 70.4% !important;
  }
}

@media only screen and (min-width: 992px) {
  .large.boron-modal {
    width: 1020px !important;
  }

  .medium.boron-modal {
    width: 850px !important;
  }

  .small.boron-modal {
    width: 680px !important;
  }
}

@media only screen and (min-width: 1200px) {
  .large.boron-modal {
    width: 1080px !important;
  }

  .medium.boron-modal {
    width: 900px !important;
  }

  .small.boron-modal {
    width: 720px !important;
  }
}

@media only screen and (min-width: 1920px) {
  .large.boron-modal {
    width: 1140px !important;
  }

  .medium.boron-modal {
    width: 950px !important;
  }

  .small.boron-modal {
    width: 760px !important;
  }
}


解决 Audio data must be floating-point

在魔塔在线体验和本地部署之后，上传wav音频，均遇到如下报错：
File "funclip/launch.py", line 21, in audio_recog
return audio_clipper.recog(audio_input, sd_switch, hotwords=hotwords)
File "/root/FunClip/FunClip/funclip/videoclipper.py", line 30, in recog
data = librosa.resample(data, orig_sr=sr, target_sr=16000)
File "/root/miniconda3/envs/funclip/lib/python3.8/site-packages/librosa/core/audio.py", line 627, in resample
util.valid_audio(y, mono=False)
File "/root/miniconda3/envs/funclip/lib/python3.8/site-packages/librosa/util/utils.py", line 298, in valid_audio
raise ParameterError("Audio data must be floating-point")
librosa.util.exceptions.ParameterError: Audio data must be floating-point
这段报错，主要是librosa 在处理音频数据时期望浮点型数据，但接收到的可能是整型数据（例如int16）。librosa 处理音频时，音频数据需要是浮点数格式，通常范围在 -1.0 到 1.0，所以增加了convert_pcm_to_float 函数将音频转成浮点数

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.zhouzhenneng seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


pypy3: fix sitecustomize

Description of changes
This is a stop-gap solution for pypy3.withPackages to actually find the correct site-packages directory. This should be a workaround for #39356.

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

https://github.com/NixOS/nixpkgs/pull/217558 did not fix the issue entirely?

When we upgraded past this version and added Python 3.8 support 1, the sitePackages value was never updated, leading bootstrapped-pip to fail to build, because wheel was trying to be located in $out/site-packages, when it was actually installed to $out/lib/pypy3.8/site-packages.

It went into a different direction and now is searching for $out/lib/pypy3.8/lib/pypy3.8/site-packages

drafting because of the proper fix in #240301


Conversion of all '==' and '!=' to '===' and '!=='

Let's make sure comparisons are using triple equals. Whether there is a performance boost of this - due to implicit casting involved with double equals operators - is browser dependent.

This has been handled in #108 .


iOS 6 AFNetworking/UIKit

With Version 2.5.2 it ist not possible to have to UKit subspec without the the NSURLSession subspec. Breaking backwards compatibility with iOS 6.

Same issue for me, i use pod 'AFNetworking', '~> 2.0' and in my device on iOS 6.1 not working
Please help me

See #2638.


F1 disorder loader also loading F10

https://github.com/Aarhus-Psychiatry-Research/psycop-common/blob/4f6736de46c198f335a68365e43cd44fd5158573/psycop/common/feature_generation/loaders/raw/load_diagnoses.py#L553
Doing revisions for the ECT paper and double checking some feature importance, I noticed that the wildcard=True parameter in the f1_disorders loader might cause it to also load F10 diagnoses. Can someone check (and fix) if this is the case?

@HLasse I think this is the intended behaviour, since f1 contains f10-f19 as subgroups, and as far as I can tell, f1 does not exist as a diagnosis on its own. Also possible that I'm confused, feel free to give me a call or send me a message if this doesn't make sense.

no probs ;-)


feat(iroha2-ledger): add Iroha V2 test ledger image and setup class

Add a new test image for Iroha V2 (iroha2-all-in-one). It start a test ledger in single container,
and also contains a proxy script for running iroha_client_cli.
Add the new image to the CI.
Add a new class for starting and interacting with Iroha V2 test ledger
from typescript test - Iroha2TestLedger.
Add test for test setup class to ensure basic functions are working correctly.

Relates to #2138
Signed-off-by: Michal Bajer<EMAIL_ADDRESS>

@petermetz I've updated the Dockerfile to use specific image instead of generic Iroha2 LTS tag that broke recently. Please upload this image once again, so I can update it through the tests.

@petermetz I've updated the Dockerfile to use specific image instead of generic Iroha2 LTS tag that broke recently. Please upload this image once again, so I can update it through the tests.

@outSH I published the new image as ghcr.io/hyperledger/cactus-iroha2-all-in-one:2022-10-18-06770b6c


ReferenceError: Can't find variable: document

https://github.com/symisc/faceio-npm/blob/233e8d35777fa920088a3a4dc648042555a4ed3e/index.js#L8C34-L8C34

Hello,

First and foremost React != React Native This should help you to dig around and will of course help to why the document is not available.
The fio.js library is intended for web applications that run in the browser. When running in the context of a browser, the document element is available by default.
Now, the fix is to install the React Webview component and instantiate fio.js  inside the Webview.
Refer to the forum question at: How Do I Implement FACEIO (fio.js) on My React Native App? for additional information.

Do you Have an any code solution ?


CORE-11532 - [WIP]: Quick NFT Test

As marked on the ticket the below issue seems to be appearing on every resilience testing run with a frequency of 1 or 2 flows / 400 flows on a flow's request to the crypto worker sign operation:
-- failure 1 --Flow launched as holdingId '594BEDF2992B' with requestId '594BEDF2992B-flow-144-1685249031877' failed: {"holdingIdentityShortHash":"594BEDF2992B","clientRequestId":"594BEDF2992B-flow-144-1685249031877","flowId":"4eae3a35-11a9-4240-88c2-4188ec564afc","flowStatus":"FAILED","flowResult":null,"flowError":{"type":"FLOW_FAILED","message":"Component net.corda.crypto.service.CryptoServiceFactory is not ready."},"timestamp":"2023-05-28T04:43:52.400Z"}

The interesting part of the above error line is: "Component net.corda.crypto.service.CryptoServiceFactory is not ready"
It seems the issue is SigningServiceImpl which seems to be a non lifecycle service, however it references a lifecycle service: CryptoServiceFactory. Now SigningServiceImpl is being used by 2 Kafka consumers ("processors"):  CryptoFlowOpsBusProcessor and CryptoOpsBusProcessor. What seems to be happening is it might happen that CryptoServiceFactory goes DOWN/ ERROR, however the processors are not being notified of those events and so they "think" they are still UP, however their underlying CryptoServiceFactory service is DOWN.
This PR takes the processors down (detaches them from Kafka) so we stop processing events targeting those processors when CryptoServiceFactory is DOWN/ ERROR, at the CryptoProcessorImpl level, and we can do that there, because CryptoProcessorImpl lifecycle depends on CryptoServiceFactory and therefore it can "see" when CryptoServiceFactory has gone DOWN/ ERROR.

I've updated CryptoWorkerFailureTests to launch one flow every half second instead of every second (that doubles the amount of flows executed by each test) and executed CryptoWorkerFailureTests 10 times in a row from the pipeline without any failure (this accounts to, roughly, 7000 flow executions without failure).


Fix a minor grammar mistake in README.md

I fixed a minor grammar mistake in README.md.
Have a happy new year!

It feels that the current wording is correct. Please correct me if I’m wro ng.
Happy new year!


Add Sign In/Sign Up button and Improvement  of footer section

I want to add sign in /sign up button for better user experience
In footer section no contact us option or helpline number is there
In Key Features of PathSphere options are not responding
I want to work on it please assign it to me @Apoorva57 @aditya-bhaumik

this issue has been solved, so we are closing this issue.


theme cicada

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
[x] I have searched the existing issues, open and closed, and I'm convinced that mine is new.
[x] The title contains the plugin to which this issue belongs

Describe the bug
The new REPORTING: UNBOUND DNS page color scheme needs to adjusted for the new page color scheme released by OpnSense.  On the Details page, the white text on the pastel background makes the text unreadable.
To Reproduce
Steps to reproduce the behavior:

Go to 'Reporting->Unbound DNS -> Overview and Reporting -> Unbound DNS -> Detail'
See error

Expected behavior
Change text color in stylesheet to #000
Screenshots
Overview page

Details page

Environment
Software version used and hardware type if relevant.
OPNsense 23.1-amd64

duplicate https://github.com/opnsense/plugins/issues/3267


Exclude .git directory from deployment

Due to some repository having a big .git files, this change adds the exclusion of the .git directory to the list of patterns in the deployment process. This also ensures that sensitive version control information is not deployed along with the rest of the code, reducing the size of the deployment package.

Closing this as it is unnecessary and is included by default in the serverless framework.
https://www.serverless.com/framework/docs/providers/aws/guide/packaging#patterns


optimize \PriorPrice\HistoryStorage::get_minimal_from_sale_start if it is from sale start, do not check all the history, return from some transient

doable only when #10 is merged

also: this method uses very similar code to get_minimal, think about removing code duplication


Discord bot restart bug

https://drive.google.com/file/d/1STvO7Yb1jxseEe-yxpNEJI8xiJfuB_FS/view?usp=drivesdk
Link to video with proof. After restart bot does not recognize giveaways

I recognize it to be a server requirement giveaway with you not being present in the server, if the bot does not recognize the giveaway it won't remove the reaction, if you are still facing this issue I request you to join the Support Server direct message me on discord with the details, I am 0_0#6666, closing this issue.


rename relation filter values - document search

Rename the filter title and/or values for something which is more user friendly.
From the current state the user does not know that the filter is supposed to filter the documents which have other related editions/languages or are a part of series.

I would go with something like
Relations -> Related content
Edition -> By edition
Multipart_monograph -> By series (completed)
Serial -> By series (periodic)
language -> By language
previous -> By predecessors (I don't remembers if it is in this filter, should it be added ? ping @ntarocco)
next -> By continuation (I don't remembers if it is in this filter, should it be added ? ping @ntarocco)


userLikes feature

Addresses #27 , allows you to get like/dislike data for the current logged in user without having to iterate and check ->liked for each row, minimizing query count.

How it will work for guest users? Could you add tests, please?

@a-komarev auth()->id() just returns null, so the query will yield no results. do you want a test that asserts that?

@acidjazz yes, tests which will cover this case would be great!


I do not have an active Azure subscription.

No tengo acceso a AZure

Yes, it sounds like the issue may be that you do not have an active Azure subscription. Your best bet will be to follow the prompts in Azure portal to ensure you have an active Azure subscription you can deploy to.
Here is a couple additional links to help:
https://azure.microsoft.com/free/
https://azure.microsoft.com/en-us/get-started/
I will close this issue, but please feel free to start a Discussion if you have any additional questions or issues deploying your site.


Registering a repo with HTTPS without adding .git extension points to HTML page

When registering a package I used https and no .git extension which caused the bower package to install the HTML page instead of the repo. This is should at the very least be documented and provide a warning. Personally I'd like to see the default be a nice error message telling the user to put ".git" or to use the "force" flag if they really wanted to set the HTML page. This is especially a problem for people who don't use GitHub for the repo and cannot fix it without creating an issue for it (as is my case).
Note: I did not test using "git" as the protocol but I'm assuming it does not have the same problem

This likely belong in the bower repo. Moving it there.


lens-desktop: 2024.3.191333 -> 2024.11.261604

The new UI for lens-desktop is now out for some while, see announcement: https://k8slens.dev/blog/lens-just-got-better-october-2024
It looks like for linux it is sufficient to just bump the source AppImage's version.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Since the alternative fork/package was removed, I would vouch for keeping this package up-to-date.
@dbirks @RossComputerGuy @starkca90 Are there any blockers you could think of not to bump the version?


typo on lab OE 2

Issue #, if available:
N/A
Description of changes:
Correction of typo in the OE 100 lab in lab 2.3 step 2. The instruction was to navigate to the IAM console instead of the EC2 console to create a key pair, causing confusion for some attendees that were new to AWS.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Thanks for identifying the typo and providing the fix. I thought I had previously corrected this but the commit history disagrees. I appreciate your input!


Need three "back button" clicks to back through admin/assets folder view

Navigate to admin/assets/
Click on a folder
Hit back button in browser

Expected: Navigates back on first click, not third.
In Chrome, both when webroot is in subfolder and on a top level domain.
/cc @tractorcow

we also have problems leaving the admin/assets section, since requests to admin/assets automatically redirect to admin/assets/show/0. We should make "admin/assets" the canonical url for "showing root folder"

Actually, in the current version you can't go back at all any more. We could solve this via a admin/assets canonical URL for root folder as Damian suggested, but I think as the baseline solution, we should allow back navigation. If it takes two back clicks to get from admin/assets/show/0 back to admin/assets, then on to admin/my-previous-section, that's OK as well.

Well, if you navigate A, B (redirects to) C, D, then if you're on D, pressing back should take you to A.
I'm not sure if we could make page.js skip storing of B in the history though.

This doesn't seem to be an issue anymore with the new react-router work (just tested on asset-admin 0a6d1fa, cms ef46dee and framework bbb2824


get zookeper hosts from ipv4 adress.

this line was failing with
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": "AnsibleUndefinedVariable: ERROR! 'unicode object' has no attribute 'host'"}

i was able to get it to work with this change. i don't have much of a clue if this is the right way.
any comments?

seems like i needed to set zookeeper_hosts variable properly.
i got around it by supplying a filter
def zookeeper_role_hack(group):
    return [{'host': host} for host in group]

with
    - role: 'ansible-zookeeper'
      zookeeper_hosts: "{{ groups.mesos_primaries | zookeeper_role_hack }}"
      tags: ['mesos-tools']

feel free to close if this is the intended behavior. or give some direction onto how to handle this. i'll be happy to spend time on the implementation.

@ibrahimsag closing this in favor of https://github.com/AnsibleShipyard/ansible-zookeeper/releases/tag/v0.9.2, role now supports hash and array of hosts or you can use array of IP's in your case.


Fixed a couple of problems

1 - Set the root folder to My Computer to allow the user to browse the entire computer. Currently it was getting stuck on the Desktop (This may be machine specific!)
2 - Disabled the YouTube tab if the user doesnt have VLC installed.

Could you post a screenshot of your FolderBrowserDialog how it looks without your fix?
On my machine it looks like this without your fix:

And with your fix, it looks like:

I like the first version much better, so this commit isn't really an option.
The second commit doesn't compile, as it says The name 'locationTab' does not exist in the current context. After a few tests on my machine and if it works properly, I will move the code to the ViewModel anyway.
Thank you for your pull request, I'll use as many code of you as possible!

Hi,
When i run the code without my change the dialog looks like this:

As you can see i only have access to one folder and that is on my Desktop.
This is in Vista Ultimate. What OS are you running?
Cheers,
Gareth

Yeah, I see, this is definitely a problem that we should investigate.
I'm running in Windows 7 Professional 64-bit

Well, interesting, just now I'm sitting on my Dektop (I was on my notebook when I tested your fix) and and regardless what folder I set as root folder, my ´FolderBrowserDialog` always looks the same.

Does it help if you set the RootFolder´ property to Environment.SpecialFolder.DesktopDirectory`?

No i get the same problem.
The way it works is that whatever is set as the RootFolder you cannot go any higher than that level.
Obviously this is causing some issues in Vista that dont appear in Win7.
I think it might be better to allow the user to start from MyComputer anyway, as most people will have music all over the place, you dont want to limit the locations where they can add it from!

But what if the user wants to add music from the network, for example from a NAS? I don't think that the network folder can be selected anymore, if the access is restricted to MyComputer.

Thats a fair comment. I have spent a bit of time trying out some other WPF libraries to no avail.
I dont know if its just a problem with my machine. I turned of UAC and that didnt do anything and I have full admin rights.
I will continue to look into this and let you know if i find a solution.


Replace Node's deprecated punycode

Importing markdown-it into Node.js triggers a warning now:
node:11893) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.

Looks like anything relying on Node.js's punycode implementation should switch to a userland implementation.
https://github.com/markdown-it/markdown-it/blob/e476f78bc3ea3576beb61bdc94322d0a6b2d85cc/lib/index.js#L14
Let me know if you want a PR.

see also: https://github.com/DavidAnson/markdownlint-cli2/issues/234 and https://github.com/igorshubovych/markdownlint-cli/issues/437 and https://github.com/DavidAnson/markdownlint/issues/1032

Thank you. Most downstream users will not get an update until we tag/release.

https://github.com/markdown-it/markdown-it/pull/863#issuecomment-1837022282 in progress.

@puzrin any chance this could be backported to v13? I'm stuck on a dep chain that requires markdown-it unfortunately pinned at 13.0.1, via<EMAIL_ADDRESS>- but if markdown-it v13 avoids this deprecation warning, then i can try to ask markdown-lint to backport it to v0.29.

@ljharb I don't think we do any backports usually. :(
Latest<EMAIL_ADDRESS>does depend on<EMAIL_ADDRESS>can you check if you can use that instead?
Alternatively, you can temporarily backport the change yourself until the dep chain situation is resolved. I'm not familiar with this, but surely there must be some tools that allow patching transitive dependencies in npm ecosystem (similar to rust cargo's [patch] section).

@rlidwka i might, but i'm pinned to markdownlint on v0.29.0 for a reason I can't recall right now.
Patching deps is certainly doable but it's a very bad idea; i'd rather just ignore the deprecation warning for the time being.
Backports aren't difficult; I'm happy to do it if you're willing :-) in this case it's just changing 'punycode' to 'punycode/' and adding the package dep.


Added a few more things to the gitignore

i don't think this is really needed - i can just not push stuff that shouldn't be on the repo (and review PRs before merging to make sure they also don't contain anything)

idk think it would be helpful for others that wanna work on it too so they don't have files like batch file to intervene, just don't think it work hurt really


":class" removes classes added programmatically

Version
2.4.2
Reproduction link
https://jsfiddle.net/g2annvu5/
Steps to reproduce
Click "Change color" and inspect DOM
What is expected?
Component "test" should have "redBg" and "blueTxt" classes.
What is actually happening?
Component "test" has only "redBg" class.

I found this bug by using custom directive, which adds flex layout related classes to element. Classes added by directive were removed if element had ":class" defined in template.
If this is intentional, are there some workarounds to add/remove classes via native DOM methods?

dup of #5677


IBMSampler should take a single circuit as input

Describe the bug
This fails:
with ibm_sampler(circuits=qc, skip_transpilation=False) as sampler:

with: AttributeError: 'tuple' object has no attribute 'parameters'
However circuits=[qc] works.
Steps to reproduce
Expected behavior
The docstrings say I should be able to pass a single circuit.
Suggested solutions
Additional Information

qiskit-ibm-runtime version:
Python version:
Operating system:

This issue was fixed here https://github.com/Qiskit/qiskit-ibm-runtime/pull/220 and will be released soon.


All EXT4 tests passed but test case aborted

https://github.com/LIS/LISAv2/blob/master/Testscripts/Windows/FILE-SYSTEM-VERIFICATION-TESTS.ps1#L88
All EXT4 tests got passed, but because the timer sees the run-time issue, this test got aborted. if all tests passed, then it should be 'passed' not 'aborted'

@adriansuhov  please ack or comment

@juhlee-microsoft could you please let know which image you using, is it because the tests hung in ext4/023 cause timeout?

I don't recall it was from Mv2 or test kernel testing. I will close this.


Application chrome not visible on 11" Macbook Air

When I open the Composer application, the top chrome with the min/max/close buttons is not visible and the buttons in the top bar are partially obscured.
See attached screenshot.

Not related to framework code. Closing.


new changes

Thanks for the PR.
Hope to see more contribution from you in this organization in future.
We will like have you onboard.
Feel free to contact me in case of any doubt.


Add the possibility of sharing properties between workflows

Description
It would be interesting to allow the system to use variables set by a workflow instance within another workflow instance.
Implementation ideas
In kIE overall, Implement a context API that allow loading and save variables to a persistent store  (the key of the variable being a context id plus a property name)
In BPMN, add a ContextNode to load and save through input/output
In SWF, add $WORKLOW.context reserved word for usage in expressions.

Adding the design constraints:

Should be stored outside the process state
Pluggable (data base store as default impl)
Should be lazy load. Not required to access anytime we access the process state but should be involved automatically in any input/output like a process or context variable
Setup should be logically defined through idiom definition but wired at runtime level. It is to say. The workflow definition should say this store points to this logica store and runtime define the mappimg between the logical store and physical storage.
The store should define what is stored in it. For instance it has store the variable name with this structure. ( that way we can use those identifiers like variables amd we can compute the outcome type)
Persistence is something decoupled from the variable itself

Regarding the DataNode or Context node I would leave this to another issue as it seems we agreed to use the variable within context to use an extensible mechanism to read/write from. So let's stick to this idea and we can discuss more in depth the other another time.

Wouldn't the "extensible mechanism to read/write from" be the already existing pluggable variable persistence?  So rather than storing the variable directly in the process state, you delegate to a pluggable persistence that can load/save externally (even on demand).
Where would you want to store this state?  If it's in specific tables on a database (either the same one where you are storing process instance state or a separate one), this would be architecturally similar to how the JPA persister worked, just implemented differently.

@krisv Currently, runtime persistence mechanism is tied to the concept of process instance. In fact, persistence addon is essentially an implementation of ProcessIntances interface.
Since the context is intended to share information between process instance, I think we need to add a new Context interface to Kogito API, provide an in memory implementation and implement it in the persistence addons.

@tiagobento This was already discussed and agreed on https://lists.apache.org/thread/g0804hvzs3hxhqb9zjdxt72h252l53t9 and https://lists.apache.org/thread/w04t62ybc7t0hkqjqpn05xzwj8s4hcky

@tiagobento This issue was the result of a discussion that was started because we need to change our software in order to fulfill a customer requirement  .
The requirement is pretty clear, being able to share information between workflows.
For SonataFlow, there wont be any impact at tooling, since access to the context will be done through jq expresion (using the extension mechanism defined here. This is equivalent to other existing expression like $WORKFLOW.processInstanceId, documented here. Therefore, from documentation point of view, we just need to update that guide (the effort is meaningless compared with the implementation one)
I appreciate your interest, but unless you see a blocking problem with the agreed proposal, I do not see any need to defer the implementation of it.

@tiagobento The reason I included the customer JIRA is because you were initially asking for a use case and I think a customer request is a real use case.
Also, taking benefit that you are mentioning community best practises, I guess Apache encourage this kind of discussion to happen on the Apache list (where this was discussed and agreed long time ago, I ignore if an agreed discussion can be reopened without solid background on the matter, just a feel)
But, in order to continue being transparent, the detailed task to be performed are:
1 Define the context API (a new Java interface or new methods to an existing one, in existing Kogito API module)
2 Provide two implementations of that API, one in memory (the default one unless overriden) and another one in DB (we do not have to implement it for every DB, just postgres would suffice)
3 Define mechanism to access that API for the BPMN/Sonataflow definitions. So far, the proposal is to add a new node in BPMN and the $WORKFLOW keyword in Sonataflow. @elguardian can elaborate more on the bpmn side.
Note that 3 is not really needed to be done at the same time than 1 and 2. Sonataflow access mechanism (which impact on tooling is not existant and in documentation is meaningless, as already explained in my previous comment) can be implemented separately from BPMN none.
Therefore, I hardly see this a huge feature at all.

@fjtirado maybe we should start this. as Data Stores, Data Object is something I want to implement. Maybe we should sketch a bit how the infra for this should work so we can move this forward. If you are ok, we can start writing a bit.

@fjtirado I agree the more complex part that we need to do to support shared information between workflows is the persistent layer. Specifically how to store non primitive data (since, at least, in theory, you can share any type of information).
Since we have multiple persistence addon, my plan was to implement support only for the JDBC one and, maybe the mongodb. The latter will be trivial since you can model the complex object as a json document. For JDBC, I was thinking on using a three column table (contextId, name and value) where complex objects are normalized into simple ones (and use . as separator char for naming)

@fjtirado Let me throw something into the table.
I am ok with the suggested database persistence tier, that should be enough. So I would say something like this. As for the impl we are using variables for this, I would suggest to say something like
For the variable (in the process definition)
Variable
a. Variable Persistence Strategy (at least two impl). In this case we should add to the strategy the state of the variable to avoid loading the variable several times like not loaded, dirty, in sync... something like that.

In process state variable (current strategy): in this case the state of the variable is always in sync.
database persistence strategy. in this case depends how it is readed.

b. state of the variable just façade against hte variable persistence strategy.
VariablePersistenceStrategy should contain the name and the context id (TBD later) as variable name can be duplicated among subcontext. I am ok with the tree columns if the value column contains at least the type; otherwise we need to include that
We can reuse the
https://github.com/apache/incubator-kie-kogito-runtimes/blob/main/jbpm/process-serialization-protobuf/src/main/java/org/jbpm/flow/serialization/impl/ProtobufVariableReader.java
https://github.com/apache/incubator-kie-kogito-runtimes/blob/main/jbpm/process-serialization-protobuf/src/main/java/org/jbpm/flow/serialization/impl/ProtobufVariableWriter.java
for persistence strategy depending of the variable type.
Regarding how to specify what type of strategy. that is up to the parser. So in case of sonataflow should setup The variable process definition in the right approach, in the same way for BPMN or CMMN case entries.
That would be the general idea from my side

ok, should I file the PR or do you prefer to do so?


integration cannot have the same name as package

System Health details
System Information

version
core-2023.8.3

installation_type
Unsupported Third Party Container

dev
false

hassio
false

docker
true

user
vscode

virtualenv
false

python_version
3.11.4

os_name
Linux

os_version
5.10.76-linuxkit

arch
x86_64

timezone
UTC

config_dir
/workspaces/ocpp/config

Home Assistant Cloud

logged_in
false

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Dashboards

dashboards
1

resources
0

mode
auto-gen

Recorder

oldest_recorder_run
August 20, 2023 at 12:22 PM

current_recorder_run
August 21, 2023 at 12:14 AM

estimated_db_size
0.31 MiB

database_engine
sqlite

database_version
3.34.1

Checklist

[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of currently previous issues..

Describe the issue
i'm trying to modify an integration called ocpp to be in line with integration_blueprint.
This integration has the same name as a python package it depends upon.
I have installed this package using pip, and verified that it is indeed installed.
When starting hass using the develop script provided in this template, I cannot add the integration because elements in the ocpp package cannot be found.
2023-08-20 21:51:17.452 ERROR (MainThread) [homeassistant.setup]
Setup failed for custom integration ocpp:
Unable to import component: No module named 'ocpp.v16'

When the integration is installed through hacs, everything works fine.
When I rename the custom_components/ocpp to custom_components/ocpp_integration everything works fine.
I suspect the issue may be related to the modification of PYTHONPATH.
Reproduction steps

clone ocpp integration from https://github.com/lbbrhzn/ocpp
run pip install < requirements_test.txt
add and run setup and develop scripts
add the OCPP integration in home assistant

Debug logs
2023-08-20 21:51:12.694 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration ocpp which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-08-20 21:51:12.832 INFO (MainThread) [homeassistant.setup] Setup of domain logger took 0.0 seconds
2023-08-20 21:51:12.836 INFO (MainThread) [homeassistant.bootstrap] Setting up frontend: {'frontend'}
2023-08-20 21:51:12.864 INFO (MainThread) [homeassistant.setup] Setting up device_automation
2023-08-20 21:51:12.865 INFO (MainThread) [homeassistant.setup] Setup of domain device_automation took 0.0 seconds
2023-08-20 21:51:13.023 INFO (MainThread) [homeassistant.setup] Setting up lovelace
2023-08-20 21:51:13.026 WARNING (MainThread) [asyncio] Executing <Task pending name='setup component lovelace' coro=<_async_setup_component() running at /home/vscode/.local/lib/python3.11/site-packages/homeassistant/setup.py:288> wait_for=<Task pending name='Storage load lovelace_dashboards' coro=<Store._async_load() running at /home/vscode/.local/lib/python3.11/site-packages/homeassistant/helpers/storage.py:133> cb=[set.remove(), Task.task_wakeup()] created at /home/vscode/.local/lib/python3.11/site-packages/homeassistant/core.py:558> cb=[set.remove(), Task.task_wakeup()] created at /home/vscode/.local/lib/python3.11/site-packages/homeassistant/core.py:558> took 0.158 seconds
2023-08-20 21:51:13.043 INFO (MainThread) [homeassistant.setup] Setting up http
2023-08-20 21:51:13.060 INFO (MainThread) [homeassistant.setup] Setup of domain lovelace took 0.0 seconds
2023-08-20 21:51:13.092 INFO (MainThread) [homeassistant.setup] Setup of domain http took 0.0 seconds
2023-08-20 21:51:13.130 INFO (MainThread) [homeassistant.setup] Setting up api
2023-08-20 21:51:13.137 INFO (MainThread) [homeassistant.setup] Setup of domain api took 0.0 seconds
2023-08-20 21:51:13.137 INFO (MainThread) [homeassistant.setup] Setting up auth
2023-08-20 21:51:13.140 INFO (MainThread) [homeassistant.setup] Setup of domain auth took 0.0 seconds
2023-08-20 21:51:13.176 INFO (MainThread) [homeassistant.setup] Setting up config
2023-08-20 21:51:13.219 INFO (MainThread) [homeassistant.setup] Setting up diagnostics
2023-08-20 21:51:13.263 INFO (MainThread) [homeassistant.setup] Setting up repairs
2023-08-20 21:51:13.269 INFO (MainThread) [homeassistant.setup] Setup of domain repairs took 0.0 seconds
2023-08-20 21:51:13.436 WARNING (MainThread) [asyncio] Executing <Task finished name='Task-93' coro=<async_setup.<locals>.setup_panel() done, defined at /home/vscode/.local/lib/python3.11/site-packages/homeassistant/components/config/__init__.py:45> result=None created at /usr/local/lib/python3.11/asyncio/tasks.py:374> took 0.150 seconds
2023-08-20 21:51:13.476 INFO (MainThread) [homeassistant.setup] Setting up file_upload
2023-08-20 21:51:13.477 INFO (MainThread) [homeassistant.setup] Setup of domain file_upload took 0.0 seconds
2023-08-20 21:51:13.477 INFO (MainThread) [homeassistant.setup] Setup of domain config took 0.3 seconds
2023-08-20 21:51:13.478 INFO (MainThread) [homeassistant.setup] Setup of domain diagnostics took 0.3 seconds
2023-08-20 21:51:13.595 INFO (MainThread) [homeassistant.setup] Setting up image_upload
2023-08-20 21:51:13.597 WARNING (MainThread) [asyncio] Executing <Task pending name='setup component image_upload' coro=<_async_setup_component() running at /home/vscode/.local/lib/python3.11/site-packages/homeassistant/setup.py:288> wait_for=<Task pending name='Storage load image' coro=<Store._async_load() running at /home/vscode/.local/lib/python3.11/site-packages/homeassistant/helpers/storage.py:133> cb=[set.remove(), Task.task_wakeup()] created at /home/vscode/.local/lib/python3.11/site-packages/homeassistant/core.py:558> cb=[set.remove(), Task.task_wakeup()] created at /home/vscode/.local/lib/python3.11/site-packages/homeassistant/core.py:558> took 0.102 seconds
2023-08-20 21:51:13.604 INFO (MainThread) [homeassistant.setup] Setting up websocket_api
2023-08-20 21:51:13.605 INFO (MainThread) [homeassistant.setup] Setup of domain websocket_api took 0.0 seconds
2023-08-20 21:51:13.612 INFO (MainThread) [homeassistant.setup] Setup of domain image_upload took 0.0 seconds
2023-08-20 21:51:13.620 INFO (SyncWorker_1) [homeassistant.loader] Loaded group from homeassistant.components.group
2023-08-20 21:51:13.640 INFO (SyncWorker_2) [homeassistant.loader] Loaded device_tracker from homeassistant.components.device_tracker
2023-08-20 21:51:13.744 INFO (MainThread) [homeassistant.setup] Setting up search
2023-08-20 21:51:13.745 INFO (MainThread) [homeassistant.setup] Setup of domain search took 0.0 seconds
2023-08-20 21:51:13.746 WARNING (MainThread) [asyncio] Executing <Task pending name='setup component search' coro=<_async_setup_component() running at /home/vscode/.local/lib/python3.11/site-packages/homeassistant/setup.py:321> cb=[set.remove(), Task.task_wakeup()] created at /home/vscode/.local/lib/python3.11/site-packages/homeassistant/core.py:558> took 0.108 seconds
2023-08-20 21:51:14.519 INFO (MainThread) [homeassistant.setup] Setting up analytics
2023-08-20 21:51:14.525 WARNING (MainThread) [asyncio] Executing <Task pending name='setup component analytics' coro=<_async_setup_component() running at /home/vscode/.local/lib/python3.11/site-packages/homeassistant/setup.py:288> wait_for=<Task pending name='Storage load core.analytics' coro=<Store._async_load() running at /home/vscode/.local/lib/python3.11/site-packages/homeassistant/helpers/storage.py:133> cb=[set.remove(), Task.task_wakeup()] created at /home/vscode/.local/lib/python3.11/site-packages/homeassistant/core.py:558> cb=[set.remove(), Task.task_wakeup()] created at /home/vscode/.local/lib/python3.11/site-packages/homeassistant/core.py:558> took 0.779 seconds
2023-08-20 21:51:14.540 INFO (MainThread) [homeassistant.setup] Setting up person
2023-08-20 21:51:14.546 INFO (MainThread) [homeassistant.setup] Setup of domain analytics took 0.0 seconds
2023-08-20 21:51:14.570 INFO (MainThread) [homeassistant.setup] Setup of domain person took 0.0 seconds
2023-08-20 21:51:14.581 INFO (SyncWorker_1) [homeassistant.loader] Loaded hassio from homeassistant.components.hassio
2023-08-20 21:51:14.585 INFO (MainThread) [homeassistant.setup] Setting up onboarding
2023-08-20 21:51:14.600 INFO (MainThread) [homeassistant.setup] Setup of domain onboarding took 0.0 seconds
2023-08-20 21:51:14.622 INFO (MainThread) [homeassistant.setup] Setting up frontend
2023-08-20 21:51:14.638 INFO (MainThread) [homeassistant.setup] Setup of domain frontend took 0.0 seconds
2023-08-20 21:51:14.646 INFO (MainThread) [homeassistant.bootstrap] Setting up recorder: {'recorder'}
2023-08-20 21:51:14.651 INFO (MainThread) [homeassistant.setup] Setting up recorder
2023-08-20 21:51:14.670 INFO (MainThread) [asyncio] <Server sockets=(<asyncio.TransportSocket fd=8, family=10, type=1, proto=6, laddr=('::', 8123, 0, 0)>, <asyncio.TransportSocket fd=10, family=2, type=1, proto=6, laddr=('<IP_ADDRESS>', 8123)>)> is serving
2023-08-20 21:51:14.670 INFO (MainThread) [homeassistant.components.http] Now listening on port 8123
2023-08-20 21:51:14.791 INFO (MainThread) [homeassistant.setup] Setup of domain recorder took 0.1 seconds
2023-08-20 21:51:14.792 INFO (MainThread) [homeassistant.bootstrap] Setting up stage 1: {'cloud', 'ssdp', 'usb', 'bluetooth', 'zeroconf', 'api', 'network', 'websocket_api', 'http', 'logger', 'webhook', 'dhcp'}
2023-08-20 21:51:14.831 INFO (MainThread) [homeassistant.setup] Setting up webhook
2023-08-20 21:51:14.833 INFO (MainThread) [homeassistant.setup] Setup of domain webhook took 0.0 seconds
2023-08-20 21:51:14.882 INFO (MainThread) [homeassistant.setup] Setting up usb
2023-08-20 21:51:14.883 INFO (MainThread) [homeassistant.setup] Setup of domain usb took 0.0 seconds
2023-08-20 21:51:14.956 INFO (MainThread) [homeassistant.setup] Setting up dhcp
2023-08-20 21:51:14.957 INFO (MainThread) [homeassistant.setup] Setup of domain dhcp took 0.0 seconds
2023-08-20 21:51:14.958 INFO (MainThread) [homeassistant.setup] Setting up network
2023-08-20 21:51:14.959 INFO (MainThread) [homeassistant.setup] Setup of domain network took 0.0 seconds
2023-08-20 21:51:14.976 INFO (SyncWorker_1) [homeassistant.loader] Loaded google_assistant from homeassistant.components.google_assistant
2023-08-20 21:51:14.977 INFO (SyncWorker_1) [homeassistant.loader] Loaded alexa from homeassistant.components.alexa
2023-08-20 21:51:14.989 INFO (SyncWorker_1) [homeassistant.loader] Loaded camera from homeassistant.components.camera
2023-08-20 21:51:15.096 INFO (MainThread) [homeassistant.setup] Setting up bluetooth
2023-08-20 21:51:15.108 WARNING (MainThread) [asyncio] Executing <Task pending name='setup component bluetooth' coro=<_async_setup_component() running at /home/vscode/.local/lib/python3.11/site-packages/homeassistant/setup.py:288> wait_for=<Task pending name='Storage load bluetooth.remote_scanners' coro=<Store._async_load() running at /home/vscode/.local/lib/python3.11/site-packages/homeassistant/helpers/storage.py:133> cb=[set.remove(), Task.task_wakeup()] created at /home/vscode/.local/lib/python3.11/site-packages/homeassistant/core.py:558> cb=[set.remove(), Task.task_wakeup()] created at /home/vscode/.local/lib/python3.11/site-packages/homeassistant/core.py:558> took 0.119 seconds
2023-08-20 21:51:15.227 INFO (MainThread) [homeassistant.setup] Setting up zeroconf
2023-08-20 21:51:15.242 INFO (MainThread) [homeassistant.setup] Setup of domain zeroconf took 0.0 seconds
2023-08-20 21:51:15.258 INFO (SyncWorker_0) [homeassistant.loader] Loaded media_player from homeassistant.components.media_player
2023-08-20 21:51:15.299 INFO (MainThread) [homeassistant.components.zeroconf] Starting Zeroconf broadcast
2023-08-20 21:51:15.307 INFO (MainThread) [homeassistant.setup] Setup of domain bluetooth took 0.2 seconds
2023-08-20 21:51:16.200 INFO (MainThread) [homeassistant.setup] Setting up cloud
2023-08-20 21:51:16.204 WARNING (MainThread) [asyncio] Executing <Task pending name='setup component cloud' coro=<_async_setup_component() running at /home/vscode/.local/lib/python3.11/site-packages/homeassistant/setup.py:288> wait_for=<Task pending name='Storage load cloud' coro=<Store._async_load() running at /home/vscode/.local/lib/python3.11/site-packages/homeassistant/helpers/storage.py:133> cb=[set.remove(), Task.task_wakeup()] created at /home/vscode/.local/lib/python3.11/site-packages/homeassistant/core.py:558> cb=[set.remove(), Task.task_wakeup()] created at /home/vscode/.local/lib/python3.11/site-packages/homeassistant/core.py:558> took 0.883 seconds
2023-08-20 21:51:16.283 INFO (MainThread) [homeassistant.setup] Setting up ssdp
2023-08-20 21:51:16.311 INFO (MainThread) [homeassistant.setup] Setup of domain cloud took 0.1 seconds
2023-08-20 21:51:16.316 INFO (MainThread) [homeassistant.setup] Setup of domain ssdp took 0.0 seconds
2023-08-20 21:51:16.324 INFO (MainThread) [homeassistant.bootstrap] Setting up stage 2: {'config', 'counter', 'analytics', 'schedule', 'default_config', 'timer', 'input_datetime', 'automation', 'script', 'input_button', 'history', 'diagnostics', 'repairs', 'application_credentials', 'trace', 'lovelace', 'search', 'mobile_app', 'sun', 'media_source', 'assist_pipeline', 'input_number', 'input_boolean', 'input_text', 'scene', 'stt', 'conversation', 'map', 'tag', 'homeassistant_alerts', 'logbook', 'onboarding', 'device_automation', 'input_select', 'file_upload', 'energy', 'image_upload', 'zone', 'radio_browser', 'tts', 'ocpp', 'stream', 'person', 'blueprint', 'hardware', 'my', 'system_health', 'auth'}
2023-08-20 21:51:16.345 INFO (MainThread) [homeassistant.setup] Setting up counter
2023-08-20 21:51:16.351 INFO (MainThread) [homeassistant.setup] Setting up schedule
2023-08-20 21:51:16.362 INFO (MainThread) [homeassistant.setup] Setting up timer
2023-08-20 21:51:16.367 INFO (MainThread) [homeassistant.setup] Setting up input_datetime
2023-08-20 21:51:16.373 INFO (MainThread) [homeassistant.setup] Setting up input_button
2023-08-20 21:51:16.485 INFO (MainThread) [homeassistant.setup] Setting up history
2023-08-20 21:51:16.486 INFO (MainThread) [homeassistant.setup] Setup of domain history took 0.0 seconds
2023-08-20 21:51:16.489 WARNING (MainThread) [asyncio] Executing <Task pending name='setup component history' coro=<_async_setup_component() running at /home/vscode/.local/lib/python3.11/site-packages/homeassistant/setup.py:321> cb=[set.remove(), Task.task_wakeup()] created at /home/vscode/.local/lib/python3.11/site-packages/homeassistant/core.py:558> took 0.113 seconds
2023-08-20 21:51:16.493 INFO (MainThread) [homeassistant.setup] Setting up trace
2023-08-20 21:51:16.494 INFO (MainThread) [homeassistant.setup] Setup of domain trace took 0.0 seconds
2023-08-20 21:51:16.497 INFO (MainThread) [homeassistant.setup] Setting up sun
2023-08-20 21:51:16.502 INFO (MainThread) [homeassistant.setup] Setup of domain sun took 0.0 seconds
2023-08-20 21:51:16.607 INFO (MainThread) [homeassistant.setup] Setting up input_number
2023-08-20 21:51:16.613 INFO (MainThread) [homeassistant.setup] Setting up input_boolean
2023-08-20 21:51:16.623 INFO (MainThread) [homeassistant.setup] Setting up input_text
2023-08-20 21:51:16.641 INFO (MainThread) [homeassistant.setup] Setting up scene
2023-08-20 21:51:16.666 INFO (MainThread) [homeassistant.setup] Setting up stt
2023-08-20 21:51:16.668 INFO (MainThread) [homeassistant.setup] Setup of domain stt took 0.0 seconds
2023-08-20 21:51:16.669 INFO (MainThread) [homeassistant.setup] Setting up conversation
2023-08-20 21:51:16.675 INFO (MainThread) [homeassistant.setup] Setup of domain conversation took 0.0 seconds
2023-08-20 21:51:16.736 INFO (MainThread) [homeassistant.setup] Setting up tag
2023-08-20 21:51:16.778 INFO (MainThread) [homeassistant.setup] Setting up homeassistant_alerts
2023-08-20 21:51:16.781 INFO (MainThread) [homeassistant.setup] Setup of domain homeassistant_alerts took 0.0 seconds
2023-08-20 21:51:16.784 INFO (MainThread) [homeassistant.setup] Setting up input_select
2023-08-20 21:51:16.789 INFO (MainThread) [homeassistant.setup] Setting up zone
2023-08-20 21:51:16.792 INFO (MainThread) [homeassistant.setup] Setting up tts
2023-08-20 21:51:16.796 INFO (MainThread) [homeassistant.setup] Setting up blueprint
2023-08-20 21:51:16.800 INFO (MainThread) [homeassistant.setup] Setup of domain blueprint took 0.0 seconds
2023-08-20 21:51:16.842 INFO (MainThread) [homeassistant.setup] Setting up hardware
2023-08-20 21:51:16.965 INFO (MainThread) [homeassistant.setup] Setting up radio_browser
2023-08-20 21:51:16.966 INFO (MainThread) [homeassistant.setup] Setup of domain radio_browser took 0.0 seconds
2023-08-20 21:51:17.026 INFO (MainThread) [homeassistant.setup] Setting up application_credentials
2023-08-20 21:51:17.031 INFO (MainThread) [homeassistant.setup] Setting up media_source
2023-08-20 21:51:17.050 INFO (MainThread) [homeassistant.setup] Setup of domain hardware took 0.2 seconds
2023-08-20 21:51:17.103 INFO (MainThread) [homeassistant.setup] Setting up map
2023-08-20 21:51:17.112 INFO (MainThread) [homeassistant.setup] Setup of domain map took 0.0 seconds
2023-08-20 21:51:17.141 INFO (MainThread) [homeassistant.setup] Setting up logbook
2023-08-20 21:51:17.153 INFO (MainThread) [homeassistant.setup] Setting up energy
2023-08-20 21:51:17.155 INFO (MainThread) [homeassistant.setup] Setup of domain energy took 0.0 seconds
2023-08-20 21:51:17.201 INFO (MainThread) [homeassistant.setup] Setting up my
2023-08-20 21:51:17.202 INFO (MainThread) [homeassistant.setup] Setup of domain my took 0.0 seconds
2023-08-20 21:51:17.203 INFO (MainThread) [homeassistant.setup] Setting up system_health
2023-08-20 21:51:17.217 INFO (MainThread) [homeassistant.setup] Setup of domain counter took 0.9 seconds
2023-08-20 21:51:17.220 INFO (MainThread) [homeassistant.setup] Setup of domain timer took 0.9 seconds
2023-08-20 21:51:17.246 INFO (MainThread) [homeassistant.setup] Setup of domain tag took 0.5 seconds
2023-08-20 21:51:17.269 INFO (MainThread) [homeassistant.setup] Setting up automation
2023-08-20 21:51:17.274 INFO (MainThread) [homeassistant.setup] Setting up script
2023-08-20 21:51:17.314 INFO (SyncWorker_0) [homeassistant.loader] Loaded sensor from homeassistant.components.sensor
2023-08-20 21:51:17.331 INFO (MainThread) [homeassistant.setup] Setup of domain media_source took 0.3 seconds
2023-08-20 21:51:17.340 INFO (MainThread) [homeassistant.setup] Setup of domain logbook took 0.2 seconds
2023-08-20 21:51:17.346 INFO (MainThread) [homeassistant.setup] Setup of domain tts took 0.6 seconds
2023-08-20 21:51:17.350 INFO (MainThread) [homeassistant.setup] Setup of domain system_health took 0.1 seconds
2023-08-20 21:51:17.363 INFO (MainThread) [homeassistant.setup] Setup of domain schedule took 1.0 seconds
2023-08-20 21:51:17.371 INFO (MainThread) [homeassistant.setup] Setup of domain input_button took 1.0 seconds
2023-08-20 21:51:17.377 INFO (MainThread) [homeassistant.setup] Setup of domain input_datetime took 1.0 seconds
2023-08-20 21:51:17.384 INFO (MainThread) [homeassistant.setup] Setup of domain application_credentials took 0.4 seconds
2023-08-20 21:51:17.400 INFO (MainThread) [homeassistant.setup] Setup of domain zone took 0.6 seconds
2023-08-20 21:51:17.452 ERROR (MainThread) [homeassistant.setup] Setup failed for custom integration ocpp: Unable to import component: No module named 'ocpp.v16'
Traceback (most recent call last):
  File "/home/vscode/.local/lib/python3.11/site-packages/homeassistant/setup.py", line 215, in _async_setup_component
    component = integration.get_component()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/vscode/.local/lib/python3.11/site-packages/homeassistant/loader.py", line 813, in get_component
    ComponentProtocol, importlib.import_module(self.pkg_path)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1204, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1176, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1147, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 690, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 940, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/workspaces/ocpp/custom_components/ocpp/__init__.py", line 12, in <module>
    from ocpp.v16.enums import AuthorizationStatus
  File "/workspaces/ocpp/custom_components/ocpp/__init__.py", line 12, in <module>
    from ocpp.v16.enums import AuthorizationStatus
ModuleNotFoundError: No module named 'ocpp.v16'

Diagnostics dump
not available.

There are no packages in this example.
 I have the same problem since upgrading my generated repo using the updated devcontainer.json. I've pinned the problem down to having a requirement in the manifest with the same name as as the integration package. In your case that would be occp. The package is downloaded by hass but it seems that hass cannot resolve the dependency correctly.
from your manifest
}
"issue_tracker": "https://github.com/lbbrhzn/ocpp/issues",
	"requirements": [
		"ocpp>=1.0.0",
		"websockets>=12.0"
	],
	"version": "0.5.12"
}

There are no packages in this example. Everything here are just examples, and you as as the maintainer of your repository need to adjust it to fit your needs.

@ludeeus Another approach might be using an additional mount in devcontainer.json avoiding the need for usage of both PYTHONPATH and symlinks.
{
    // Below will mount custom_components inside /config dir in the container.
    "mounts": [
        "source=${localWorkspaceFolder}/custom_components,target=${containerWorkspaceFolder}/config/custom_components,type=bind,consistency=cached"
    ],
}


ablation experiment

Hello, I would like to ask how the ablation experiment in this experiment was completed in the report you sent above
Looking for your reply, thanks sincerely.
Regard!

Hello, Thanks for your attention to our work. The details about ablation experiment can be found in our paper at CSTTN_FINAL.pdf.


fix(ng-update): material update fails due to circular dependency

Currently running ng update for both Material and CDK fails because there
is a circular dependency in the CDK schematics that cause the update-tool
exports to be not available to the Material ng-update schematic.
Without putting to much effort into ensuring no circular dependencies, this
commit also sets up Madge to avoid such issues in the future.

To clarify: I did various manual testings after the ng-update rework but such issues are not easy to test with packages which are not published on NPM as ng update behaves differently if it installs packages through NPM or uses local ones.
Ideally we'll have some real integration tests for this. And next time I'll make sure to push the schematics to a NPM package for manual testing (even though it's way more effort..)