[BACKLOG-14180] shared object synchronization with repository and name changes

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
ant -Dtestreports.dir=bin/reports/unit-test -f engine/build.xml clean-all resolve jacoco && ant -f engine/build.xml checkstyle publish-local
ant -Dtestreports.dir=bin/reports/unit-test -f ui/build.xml clean-all resolve jacoco && ant -f ui/build.xml checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  engine/src/org/pentaho/di/base/AbstractMeta.java
  engine/src/org/pentaho/di/cluster/SlaveServer.java
  engine/src/org/pentaho/di/job/JobMeta.java
  engine/src/org/pentaho/di/shared/SharedObjects.java
  engine/src/org/pentaho/di/shared/SharedObjectsMetaStore.java
  engine/src/org/pentaho/di/trans/TransMeta.java
  engine/src/org/pentaho/di/trans/step/StepMeta.java
  engine/test-src/org/pentaho/di/cluster/SlaveServerTest.java
  engine/test-src/org/pentaho/di/shared/SharedObjectsTest.java
  engine/test-src/org/pentaho/di/trans/step/StepMetaTest.java
  engine/test-src/org/pentaho/di/utils/TestUtils.java
  ui/src/org/pentaho/di/ui/repository/repositoryexplorer/RepositoryExplorer.java
  ui/src/org/pentaho/di/ui/repository/repositoryexplorer/controllers/ClustersController.java
  ui/src/org/pentaho/di/ui/repository/repositoryexplorer/controllers/ConnectionsController.java
  ui/src/org/pentaho/di/ui/repository/repositoryexplorer/controllers/MainController.java
  ui/src/org/pentaho/di/ui/repository/repositoryexplorer/controllers/PartitionsController.java
  ui/src/org/pentaho/di/ui/repository/repositoryexplorer/controllers/SlavesController.java
  ui/src/org/pentaho/di/ui/spoon/SharedObjectSyncUtil.java
  ui/src/org/pentaho/di/ui/spoon/Spoon.java
  ui/src/org/pentaho/di/ui/spoon/delegates/SpoonClustersDelegate.java
  ui/src/org/pentaho/di/ui/spoon/delegates/SpoonDBDelegate.java
  ui/src/org/pentaho/di/ui/spoon/delegates/SpoonPartitionsDelegate.java
  ui/src/org/pentaho/di/ui/spoon/delegates/SpoonSharedObjectDelegate.java
  ui/src/org/pentaho/di/ui/spoon/delegates/SpoonSlaveDelegate.java
  ui/test-src/org/pentaho/di/ui/spoon/SharedObjectSyncUtilTest.java
  ui/test-src/org/pentaho/di/ui/spoon/SpoonRefreshSlavesSubtreeTest.java

Still Broken Tests:
org.pentaho.di.trans.steps.syslog.SyslogMessageConcurrentTest.concurrentSyslogMessageTest:
:red_circle: org.junit.runners.model.TestTimedOutException
org.junit.runners.model.TestTimedOutException: test timed out after 2000 milliseconds
	at org.jacoco.agent.rt.internal_14f7ee5.asm.commons.AnalyzerAdapter.visitIntInsn(AnalyzerAdapter.java:267)
	at org.jacoco.agent.rt.internal_14f7ee5.asm.tree.IntInsnNode.accept(IntInsnNode.java:80)
	at org.jacoco.agent.rt.internal_14f7ee5.asm.tree.InsnList.accept(InsnList.java:162)
	at org.jacoco.agent.rt.internal_14f7ee5.asm.tree.MethodNode.accept(MethodNode.java:817)
	at org.jacoco.agent.rt.internal_14f7ee5.c

Unit test coverage change
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.
org.pentaho.di.base.AbstractMeta

Branch Change: -3.98%:small_red_triangle_down:
Complexity Change: -2.74%:small_red_triangle_down:
Instruction Change: -5.61%:small_red_triangle_down:
Line Change: -5.79%:small_red_triangle_down:
Method Change: -1.90%:small_red_triangle_down:

org.pentaho.di.cluster.SlaveServer

Branch Change:  + .88%
Complexity Change:  + 1.24%
Instruction Change:  + .90%
Line Change:  + 1.07%
Method Change:  + 1.92%

org.pentaho.di.job.entries.checkdbconnection.JobEntryCheckDbConnections

Branch Change: -1.23%:small_red_triangle_down:
Complexity Change: -1.52%:small_red_triangle_down:
Instruction Change: -.21%:small_red_triangle_down:

org.pentaho.di.job.entries.evaluatetablecontent.JobEntryEvalTableContent

Branch Change: -1.01%:small_red_triangle_down:
Complexity Change: -1.06%:small_red_triangle_down:
Instruction Change: -.17%:small_red_triangle_down:

org.pentaho.di.job.JobMeta

Branch Change:  + .09%
Complexity Change: -.24%:small_red_triangle_down:
Instruction Change:  + .15%
Line Change:  + .23%
Method Change: -.92%:small_red_triangle_down:

org.pentaho.di.shared.SharedObjects

Branch Change:  + 16.61%
Complexity Change:  + 16.48%
Instruction Change:  + 26.84%
Line Change:  + 29.58%
Method Change:  + 30.43%

org.pentaho.di.shared.SharedObjects.SharedEntry

Complexity Change:  + 40.00%
Instruction Change:  + 51.28%
Line Change:  + 71.43%
Method Change:  + 66.67%

org.pentaho.di.trans.step.StepMeta

Complexity Change:  + .58%
Instruction Change:  + .09%
Method Change:  + 1.01%

org.pentaho.di.trans.steps.combinationlookup.CombinationLookupMeta

Instruction Change: -.04%:small_red_triangle_down:

org.pentaho.di.trans.steps.constant.ConstantMeta

Instruction Change: -.10%:small_red_triangle_down:

org.pentaho.di.trans.steps.datagrid.DataGridMeta

Instruction Change: -.09%:small_red_triangle_down:

org.pentaho.di.trans.steps.dbproc.DBProcMeta

Instruction Change: -.11%:small_red_triangle_down:

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

Branch Change: -.31%:small_red_triangle_down:
Instruction Change: -.06%:small_red_triangle_down:
Line Change:  + .23%
Method Change:  + 1.02%

org.pentaho.di.trans.steps.excelwriter.ExcelWriterStepMeta

Branch Change:  + 1.28%
Complexity Change:  + .78%
Instruction Change:  + .08%

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

Branch Change: -1.04%:small_red_triangle_down:
Complexity Change: -1.05%:small_red_triangle_down:

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

Branch Change: -2.00%:small_red_triangle_down:
Complexity Change: -1.89%:small_red_triangle_down:
Instruction Change: -.17%:small_red_triangle_down:

org.pentaho.di.trans.steps.insertupdate.InsertUpdateMeta

Instruction Change: -.05%:small_red_triangle_down:

org.pentaho.di.trans.steps.processfiles.ProcessFilesMeta

Branch Change: -3.57%:small_red_triangle_down:
Complexity Change: -2.13%:small_red_triangle_down:
Instruction Change: -.33%:small_red_triangle_down:

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

Instruction Change: -.07%:small_red_triangle_down:

org.pentaho.di.trans.steps.setvalueconstant.SetValueConstantMeta

Instruction Change: -.14%:small_red_triangle_down:

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

Branch Change: -3.33%:small_red_triangle_down:
Complexity Change: -1.85%:small_red_triangle_down:
Instruction Change: -.28%:small_red_triangle_down:

org.pentaho.di.trans.steps.syslog.SyslogMessage

Branch Change: -13.33%:small_red_triangle_down:
Complexity Change: -4.76%:small_red_triangle_down:
Instruction Change: -10.05%:small_red_triangle_down:
Line Change: -11.69%:small_red_triangle_down:
Method Change: -16.67%:small_red_triangle_down:

org.pentaho.di.trans.TransMeta

Branch Change:  + .03%
Complexity Change: -.11%:small_red_triangle_down:
Instruction Change: -.03%:small_red_triangle_down:
Line Change:  + .05%
Method Change: -.61%:small_red_triangle_down:

org.pentaho.di.ui.repository.repositoryexplorer.controllers.ConnectionsController

Branch Change:  + .36%
Complexity Change:  + .71%
Instruction Change:  + .29%
Line Change:  + .62%
Method Change:  + 3.08%

org.pentaho.di.ui.spoon.delegates.SpoonClustersDelegate

Complexity Change:  + 6.25%
Instruction Change:  + 1.85%
Line Change:  + 3.77%
Method Change:  + 20.00%

org.pentaho.di.ui.spoon.delegates.SpoonDBDelegate

Complexity Change:  + 5.56%
Instruction Change:  + .92%
Line Change:  + 1.95%
Method Change:  + 16.67%

org.pentaho.di.ui.spoon.delegates.SpoonPartitionsDelegate

Branch Change:  + 12.50%
Complexity Change:  + 11.76%
Instruction Change:  + 17.03%
Line Change:  + 19.64%
Method Change:  + 40.00%

org.pentaho.di.ui.spoon.delegates.SpoonSharedObjectDelegate

Branch Change: -60.00%:small_red_triangle_down:
Complexity Change: -10.99%:small_red_triangle_down:
Instruction Change: -26.86%:small_red_triangle_down:
Line Change: -22.90%:small_red_triangle_down:
Method Change:  + 10.00%

org.pentaho.di.ui.spoon.delegates.SpoonSlaveDelegate

Branch Change:  + 13.64%
Complexity Change:  + 16.67%
Instruction Change:  + 13.24%
Line Change:  + 17.46%
Method Change:  + 42.86%

org.pentaho.di.ui.spoon.SharedObjectSyncUtil

Branch Change: -33.33%:small_red_triangle_down:
Complexity Change: -35.29%:small_red_triangle_down:
Instruction Change: -22.28%:small_red_triangle_down:
Line Change: -27.56%:small_red_triangle_down:
Method Change: -28.95%:small_red_triangle_down:

org.pentaho.di.ui.spoon.SharedObjectSyncUtil.ClusterSchemaSynchronizationHandler

Instruction Change: -2.38%:small_red_triangle_down:

org.pentaho.di.ui.spoon.SharedObjectSyncUtil.ConnectionSynchronizationHandler

Complexity Change:  + 25.00%
Instruction Change:  + 20.00%
Line Change:  + 20.00%
Method Change:  + 25.00%

org.pentaho.di.ui.spoon.SharedObjectSyncUtil.PartitionSchemaSynchronizationHandler

Instruction Change: -2.38%:small_red_triangle_down:

org.pentaho.di.ui.spoon.SharedObjectSyncUtil.SlaveServerSynchronizationHandler

Instruction Change: -3.08%:small_red_triangle_down:

org.pentaho.di.ui.spoon.SharedObjectSyncUtil.StepMetaSynchronizationHandler

Instruction Change: -2.38%:small_red_triangle_down:

org.pentaho.di.ui.spoon.Spoon

Branch Change:  + .01%
Complexity Change: -.02%:small_red_triangle_down:
Instruction Change: -.01%:small_red_triangle_down:
Line Change:  + .02%
Method Change: -.17%:small_red_triangle_down:

org.pentaho.di.ui.spoon.Spoon.new Comparator() {...}

Complexity Change:  + 100.00%
Instruction Change:  + 100.00%
Line Change:  + 100.00%
Method Change:  + 100.00%

License header violations

:heavy_exclamation_mark: Copyright year is not the current year on engine/src/org/pentaho/di/shared/SharedObjectsMetaStore.java. Found 2013. Was expecting 2017

:heavy_exclamation_mark: Copyright year is not the current year on engine/test-src/org/pentaho/di/trans/step/StepMetaTest.java. Found 2015. Was expecting 2017

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/ui/src/org/pentaho/di/ui/spoon/delegates/SpoonDBDelegate.java

:heavy_exclamation_mark: Line has trailing spaces at Line: 116

:heavy_exclamation_mark: Line has trailing spaces at Line: 466

/home/buildguy/project/ui/src/org/pentaho/di/ui/spoon/delegates/SpoonPartitionsDelegate.java

:heavy_exclamation_mark: 'if' is not followed by whitespace. at Line: 63 Column: 15

/home/buildguy/project/ui/src/org/pentaho/di/ui/spoon/delegates/SpoonSharedObjectDelegate.java

:heavy_exclamation_mark: Line has trailing spaces at Line: 78

/home/buildguy/project/ui/src/org/pentaho/di/ui/spoon/delegates/SpoonSlaveDelegate.java

:heavy_exclamation_mark: 'if' is not followed by whitespace. at Line: 79 Column: 9

:heavy_exclamation_mark: Line has trailing spaces at Line: 82

:heavy_exclamation_mark: 'if' is not followed by whitespace. at Line: 102 Column: 15

/home/buildguy/project/ui/test-src/org/pentaho/di/ui/spoon/SharedObjectSyncUtilTest.java

:heavy_exclamation_mark: Line has trailing spaces at Line: 758

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
ant -Dtestreports.dir=bin/reports/unit-test -f engine/build.xml clean-all resolve jacoco && ant -f engine/build.xml checkstyle publish-local
ant -Dtestreports.dir=bin/reports/unit-test -f ui/build.xml clean-all resolve jacoco && ant -f ui/build.xml checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  engine/src/org/pentaho/di/base/AbstractMeta.java
  engine/src/org/pentaho/di/cluster/SlaveServer.java
  engine/src/org/pentaho/di/job/JobMeta.java
  engine/src/org/pentaho/di/shared/SharedObjects.java
  engine/src/org/pentaho/di/shared/SharedObjectsMetaStore.java
  engine/src/org/pentaho/di/trans/TransMeta.java
  engine/src/org/pentaho/di/trans/step/StepMeta.java
  engine/test-src/org/pentaho/di/cluster/SlaveServerTest.java
  engine/test-src/org/pentaho/di/shared/SharedObjectsTest.java
  engine/test-src/org/pentaho/di/trans/step/StepMetaTest.java
  engine/test-src/org/pentaho/di/utils/TestUtils.java
  ui/src/org/pentaho/di/ui/repository/repositoryexplorer/RepositoryExplorer.java
  ui/src/org/pentaho/di/ui/repository/repositoryexplorer/controllers/ClustersController.java
  ui/src/org/pentaho/di/ui/repository/repositoryexplorer/controllers/ConnectionsController.java
  ui/src/org/pentaho/di/ui/repository/repositoryexplorer/controllers/MainController.java
  ui/src/org/pentaho/di/ui/repository/repositoryexplorer/controllers/PartitionsController.java
  ui/src/org/pentaho/di/ui/repository/repositoryexplorer/controllers/SlavesController.java
  ui/src/org/pentaho/di/ui/spoon/SharedObjectSyncUtil.java
  ui/src/org/pentaho/di/ui/spoon/Spoon.java
  ui/src/org/pentaho/di/ui/spoon/delegates/SpoonClustersDelegate.java
  ui/src/org/pentaho/di/ui/spoon/delegates/SpoonDBDelegate.java
  ui/src/org/pentaho/di/ui/spoon/delegates/SpoonPartitionsDelegate.java
  ui/src/org/pentaho/di/ui/spoon/delegates/SpoonSharedObjectDelegate.java
  ui/src/org/pentaho/di/ui/spoon/delegates/SpoonSlaveDelegate.java
  ui/test-src/org/pentaho/di/ui/spoon/SharedObjectSyncUtilTest.java
  ui/test-src/org/pentaho/di/ui/spoon/SpoonRefreshSlavesSubtreeTest.java

Still Broken Tests:
org.pentaho.di.trans.steps.syslog.SyslogMessageConcurrentTest.concurrentSyslogMessageTest:
:red_circle: org.junit.runners.model.TestTimedOutException
org.junit.runners.model.TestTimedOutException: test timed out after 2000 milliseconds
	at java.lang.Object.hashCode(Native Method)
	at java.util.HashMap.hash(HashMap.java:338)
	at java.util.HashMap.containsKey(HashMap.java:595)
	at org.jacoco.agent.rt.internal_14f7ee5.core.internal.flow.MethodProbesAdapter.visitLabel(MethodProbesAdapter.java:83)
	at org.jacoco.agent.rt.internal_14f7ee5.asm.commons.AnalyzerAdapter.visitLabel(AnalyzerAdapter.java:398)
	at org.jacoco.agent.rt.internal_14f7ee5.asm.t

Unit test coverage change
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.
org.pentaho.di.base.AbstractMeta

Branch Change: -3.98%:small_red_triangle_down:
Complexity Change: -2.74%:small_red_triangle_down:
Instruction Change: -5.61%:small_red_triangle_down:
Line Change: -5.79%:small_red_triangle_down:
Method Change: -1.90%:small_red_triangle_down:

org.pentaho.di.cluster.SlaveServer

Branch Change:  + .88%
Complexity Change:  + 1.24%
Instruction Change:  + .90%
Line Change:  + 1.07%
Method Change:  + 1.92%

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

Branch Change:  + .39%
Complexity Change:  + .51%
Instruction Change:  + .08%

org.pentaho.di.job.entries.ftpsget.JobEntryFTPSGet

Branch Change: -.53%:small_red_triangle_down:
Complexity Change: -.56%:small_red_triangle_down:
Instruction Change: -.07%:small_red_triangle_down:

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

Instruction Change:  + 3.28%
Line Change:  + 3.87%

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

Branch Change: -.66%:small_red_triangle_down:
Complexity Change: -.93%:small_red_triangle_down:
Instruction Change: -.13%:small_red_triangle_down:

org.pentaho.di.job.JobMeta

Branch Change:  + .09%
Complexity Change: -.24%:small_red_triangle_down:
Instruction Change:  + .15%
Line Change:  + .23%
Method Change: -.92%:small_red_triangle_down:

org.pentaho.di.shared.SharedObjects

Branch Change:  + 16.61%
Complexity Change:  + 16.48%
Instruction Change:  + 26.84%
Line Change:  + 29.58%
Method Change:  + 30.43%

org.pentaho.di.shared.SharedObjects.SharedEntry

Complexity Change:  + 40.00%
Instruction Change:  + 51.28%
Line Change:  + 71.43%
Method Change:  + 66.67%

org.pentaho.di.trans.step.StepMeta

Complexity Change:  + .58%
Instruction Change:  + .47%
Line Change:  + .52%
Method Change:  + 1.01%

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

Instruction Change: -.05%:small_red_triangle_down:

org.pentaho.di.trans.steps.datagrid.DataGridMeta

Instruction Change:  + .09%

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

Instruction Change:  + .14%
Line Change:  + .37%

org.pentaho.di.trans.steps.insertupdate.InsertUpdateMeta

Instruction Change:  + .05%

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

Instruction Change:  + .06%

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

Branch Change:  + 2.35%
Complexity Change:  + 2.70%

org.pentaho.di.trans.steps.setvalueconstant.SetValueConstantMeta

Instruction Change:  + .14%

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

Instruction Change:  + .10%

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

Branch Change:  + 3.33%
Complexity Change:  + 1.85%
Instruction Change:  + .28%

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

Instruction Change:  + .18%

org.pentaho.di.trans.TransMeta

Branch Change:  + .03%
Complexity Change: -.11%:small_red_triangle_down:
Instruction Change: -.03%:small_red_triangle_down:
Line Change:  + .05%
Method Change: -.61%:small_red_triangle_down:

org.pentaho.di.www.TransformationMap

Branch Change:  + 9.09%
Complexity Change:  + 6.15%
Instruction Change:  + 10.03%
Line Change:  + 10.00%

org.pentaho.di.ui.repository.repositoryexplorer.controllers.ConnectionsController

Branch Change:  + .36%
Complexity Change:  + .71%
Instruction Change:  + .29%
Line Change:  + .62%
Method Change:  + 3.08%

org.pentaho.di.ui.spoon.delegates.SpoonClustersDelegate

Complexity Change:  + 6.25%
Instruction Change:  + 1.85%
Line Change:  + 3.77%
Method Change:  + 20.00%

org.pentaho.di.ui.spoon.delegates.SpoonDBDelegate

Complexity Change:  + 5.56%
Instruction Change:  + .92%
Line Change:  + 1.95%
Method Change:  + 16.67%

org.pentaho.di.ui.spoon.delegates.SpoonPartitionsDelegate

Branch Change:  + 12.50%
Complexity Change:  + 11.76%
Instruction Change:  + 17.03%
Line Change:  + 19.64%
Method Change:  + 40.00%

org.pentaho.di.ui.spoon.delegates.SpoonSharedObjectDelegate

Branch Change: -60.00%:small_red_triangle_down:
Complexity Change: -10.99%:small_red_triangle_down:
Instruction Change: -26.86%:small_red_triangle_down:
Line Change: -22.90%:small_red_triangle_down:
Method Change:  + 10.00%

org.pentaho.di.ui.spoon.delegates.SpoonSlaveDelegate

Branch Change:  + 13.64%
Complexity Change:  + 16.67%
Instruction Change:  + 13.24%
Line Change:  + 17.46%
Method Change:  + 42.86%

org.pentaho.di.ui.spoon.SharedObjectSyncUtil

Branch Change: -33.33%:small_red_triangle_down:
Complexity Change: -35.29%:small_red_triangle_down:
Instruction Change: -22.28%:small_red_triangle_down:
Line Change: -27.56%:small_red_triangle_down:
Method Change: -28.95%:small_red_triangle_down:

org.pentaho.di.ui.spoon.SharedObjectSyncUtil.ClusterSchemaSynchronizationHandler

Instruction Change: -2.38%:small_red_triangle_down:

org.pentaho.di.ui.spoon.SharedObjectSyncUtil.ConnectionSynchronizationHandler

Complexity Change:  + 25.00%
Instruction Change:  + 20.00%
Line Change:  + 20.00%
Method Change:  + 25.00%

org.pentaho.di.ui.spoon.SharedObjectSyncUtil.PartitionSchemaSynchronizationHandler

Instruction Change: -2.38%:small_red_triangle_down:

org.pentaho.di.ui.spoon.SharedObjectSyncUtil.SlaveServerSynchronizationHandler

Instruction Change: -3.08%:small_red_triangle_down:

org.pentaho.di.ui.spoon.SharedObjectSyncUtil.StepMetaSynchronizationHandler

Instruction Change: -2.38%:small_red_triangle_down:

org.pentaho.di.ui.spoon.Spoon

Branch Change:  + .01%
Complexity Change: -.02%:small_red_triangle_down:
Instruction Change: -.01%:small_red_triangle_down:
Line Change:  + .02%
Method Change: -.17%:small_red_triangle_down:

org.pentaho.di.ui.spoon.Spoon.new Comparator() {...}

Complexity Change:  + 100.00%
Instruction Change:  + 100.00%
Line Change:  + 100.00%
Method Change:  + 100.00%

@bmorrise please review


add a flake8 target for tox

this makes it easier to run the test suite + flake8 locally

Coverage remained the same at 94.514% when pulling bbba9c36c4428ca61af43347ab134d951e35dbc0 on ryanpetrello:tox-flake8 into c5d246a1bfa5dcc56f716c7d5b0cac8acb4ad7cd on ansible:master.

Coverage remained the same at 94.514% when pulling bbba9c36c4428ca61af43347ab134d951e35dbc0 on ryanpetrello:tox-flake8 into c5d246a1bfa5dcc56f716c7d5b0cac8acb4ad7cd on ansible:master.


Multilingualism

do you need a hand? if yes,  add more detail to your issues and add "up for grab" or you can assign issues directly to me

and even if you can invite me directly to hicode organization, I will be happy to, interact with you. it's been a long time since we were far apart. I like to do one project together if you like

Thank you for this very good suggestion. I'm very eager to add another contributor to the project, but unfortunately this issue is not on the agenda right now.
I will consult with you soon about a new issue. @BamdadTabari

safa bashe @sajadkardel

by the way. see this repository. may help you
https://github.com/blogifierdotnet/Blogifier


Accessibility

Screen reader does not read the label title which is highly informative. Consider adding aria-label="[title text] + [label text]". For example aria-label="Average 3 stars". FYI, aria-label overrides the label text itself so screen reader will only hear this once.

@WW3 thank you for the comment. Is it true for all screen readers? If so, I will try to find a moment to fix this.

@szynszyliszys guess so though i haven't tested it besides WIN/NVDA. see https://www.w3.org/TR/accname-aam-1.1/#mapping_additional_nd_te

@WW3 sounds good enough, added aria-label attribute. Thank you for your help. :)

@WW3 just did testing with Voice Over. It doesn't read any label in the new Chrome (56), when the aria-label is in there. It turns out that there can be either label text or aria-label attribute. Apparently the text in the label is considered visible here. I will stick to the label text then and remove the aria-label attribute.


Http Request parser fails on request with no headers

Get's a parse exception "invalid content in header first line"

Cannot reproduce, parsing the request GET /foo HTTP/1.1\r\n\r\n works just fine.  It's possible our sighting of this error in the wild was due to some other issue and the lack of headers was a red herring.


Looking for a page builder example

Hey, I really like using groqd, but I'm struggling to build more advanced queries.
I'm looking to do something like this, where I need to resolve the projections of the different content types:
content[]{
  _type == 'module.one' => {
   ...
  },
  _type == 'module.two' => {
   ...
  }
}

const homeQuery = q('*')
  .filterByType('home')
  .slice(0)
  .grab({
    _type: q.string(),
    _id: q.string(),
    title: q.string(),
    slug: q.slug('slug'),
    content: ??
  })

What would be super useful in the arcade/playground is to be able to write a groq query, and get the corresponding groqd queries. Or as an alternative create more examples, maybe inspired by this: https://www.sanity.io/docs/query-cheat-sheet. I'd be happy to contribute to that effort.

hey @th-km thanks for reaching out. Yea we currently have some resources for this type of functionality. Have you checked out the section in our docs for Forking Selections? I think it might be what you're looking for.
We also have an arcade example of this type of functionality here . Our arcade goes shows the output from GROQD -> GROQ so you can see what the resulting GROQD query looks like if that helps.
If neither of those satisfy your initial inquiry I'd be happy to provide further support.

Hey @littlemilkstudio thanks for the reply. I did try something based on the forking selection example from the documentation, but it was failing because of the deeply nested structure of my modules. I'm using the query below and it's working as expected so far.
const content = q('content').filter().select({
  '_type == "module.one"': moduleOne,
  '_type == "module.two"': moduleTwo
})

Thanks again for the help.

@th-km any issue using sanityImage on PortableText?


Add onIdentify and authenticateCannyLink

Adding a little more functionality.

Add the onIdentify callback for the identify command
Expose the authenticateCannyLink command
Update the README to include docs for both identify and authenticateCannyLink

Docs for both these features can be found here: https://developers.canny.io/install/advanced
I tried to test this out locally, but i'm very familiar with library development and had trouble getting it resolve the correct React package in my development environment, so my testing was limited. If you have advice I can test further, or you can give it a shot yourself.

Well done
Thanks


Has the Open Source Summer task been completed？

As the title.

Hi all. Thank you for your interest in the kvrocks community. Recently, many students have come to inquire about summer-ospp-related questions. Here, we will provide some unified answers.
Background
kvrocks-operator is a project donated by Boss-Zhipin to the kvrocks community. This project is a rewrite of the Redis operator they previously used, and the internal version already meets the production needs of Boss-Zhipin's kvrocks deployment.
However, for other users who have cloud deployment requirements, the existing kvrocks-operator is not user-friendly enough. It cannot be used out of the box, and there are many aspects that need improvement. From the perspective of an open-source project, it is still in its early stages and has not even released its first official release. The community's plan is to refactor kvrocks-operator according to the standards of the Apache project. After iterating through several versions and having 3-5 users validate its usage in production, kvrocks-operator will be moved from RocksLab to Apache as a subsidiary project of kvrocks.
Summer-ospp
Since summer-ospp only allows one student to officially sign up, with clear tasks and deadlines, we have chosen a student @jiayouxujin who has previously participated in the kvrocks community and has relevant experience in cloud-native domains  . If you were not selected, it does not mean you are not outstanding. The main reason is that we do not have enough knowledge about you. We welcome anyone to raise issues or submit pull requests. If you don't mind the bonus, students who were not selected can still participate in various projects within the community and grow together with the kvrocks community.
Others
We also welcome participation in other projects within the community ecosystem, such as kvrocks-controller and kvrocks-exporter. In the future, they will also be included in Apache as subsidiary projects of kvrocks.
Contact us
In addition to using issues or email, we often use Slack for communication.
Reference
These references may help you integrate into the community more quickly.
How to submit your first Pull Request to an open-source project?
Tison's Blog

CC @xiao-jay

CC @xiao-jay

ok，I know it，The issue #19  should complete by @jiayouxujin，because this is the project output requirements of ospp.


Audio playground player issues

Describe the bug

Issue 1: The waveform is incorrect when playing audio

The waveforms before and after the pause are different
After pausing and then clicking play again, the waveform in the latter part remains flat.

Issue 2: Seeking with the progress bar does not work
https://github.com/user-attachments/assets/52aff7d0-2c11-4ef5-bc34-c9997b1f3eea
Environment

GPUStack version: main 28e5269
UI version: b1d13f5

Additional context
Add any other context about the problem here.

UI version:
Can not stop now.

Verified on UI version 4c75a5b


Revert "Update parser value set types"

Reverts p4lang/p4-spec#873

Why should we revert the value set types?

Yes I don't see why can't signed types be valid here? (the bitwise operators are valid for fixed signed integer types even).
For serializable enum case, should it decay to the underlying type instead or does it keep it as the enum type?

I'd merged this prematurely at the last LDWG...

Can we close this PR?

I think it's too late now to consider this, we should just close it.


bad  code

Note: Please use sites such as http://stackoverflow.com for general questions about JGit usage, not issues in this project. Issues should be used for problems with snippets and suggestions of missing snippets. Snippets from good answers on stackoverflow can then be included here, naturally.
https://github.com/centic9/jgit-cookbook/blob/master/src/main/java/org/dstadler/jgit/OpenRepository.java
The last line "FileUtils.deleteDirectory(dir);" delete all my code!Thanks to I hava push to my git rep!

I am sorry that it caused you data-loss, but obviously you adjusted the code to do something different as in the original version it only removes a freshly created test-repository which is safe to delete, not anything else unless the code is modified so that it does something different.


wetrun testing

Currently, I have pulled some opensource data: https://osf.io/k2nme/ and Doc here: https://github.com/khanlab/hippunfold/pull/303
TODO:

ideally, we should make all of these wetrun data into a snakemake workflow and automate
ideally outputs will be kept to avoid re-running (and updated when a PR is merged) (i.e. hippunfold_outputs_version-latest on OSF) (maybe revisit with zenodo?)
add some metrics to compare hippunfold version (or between commits)
[ ] surface-surface differences
[ ] subfields volume difference
[ ] table of failed cases (e.g. >5mm difference)
plot and view differences
add workflow for automatically running this comparison (maybe snake-batch?)

This is something @Dhananjhay is working on, should include some aspect of this (whatever is feasible) into v2.0


Include error handling and reporting to template.

Description
Error handling and reporting is not trivial in Flutter and is needed in every application.
It is convenient to have it in template.
This change adds to the application template:

Error reporting mechanism
Simple error screen

Related Issues
https://github.com/flutter/flutter/issues/70059
Tests
The change does not change existing behavior.
Checklist
Before you create this PR, confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

[ ] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[ ] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[ ] I wrote a migration guide: https://flutter.dev/go/breaking-changes-template Replace this with a link to a pull request that adds the migration guide to https://flutter.dev/docs/release/breaking-changes

Please, review the changes. If the suggestion looks good, I will update the tests.

Thank you for the contribution, unfortunately we can't merge this. Let's continue discussion on the issue.


Re-enable string Optimizations

I think I've found the fix for the failing optimization on the main swift branch.
We should be able to re-enable optimizations once that merges.
The fixing merge is: https://github.com/apple/llvm-project/pull/3439

https://github.com/apple/llvm-project/pull/3439
@swift-ci please test


from dpark import DparkContext  ERROR

results is below:
raceback (most recent call last):
File "test_dpark.py", line 20, in
from dpark import DparkContext
File "/usr/lib64/python2.6/site-packages/DPark-0.3.5-py2.6-linux-x86_64.egg/dpark/init.py", line 1, in
from context import DparkContext, parser as optParser
File "/usr/lib64/python2.6/site-packages/DPark-0.3.5-py2.6-linux-x86_64.egg/dpark/context.py", line 10, in
from dpark.schedule import LocalScheduler, MultiProcessScheduler, MesosScheduler
File "/usr/lib64/python2.6/site-packages/DPark-0.3.5-py2.6-linux-x86_64.egg/dpark/schedule.py", line 15, in
import pymesos as mesos
File "/usr/lib64/python2.6/site-packages/pymesos-0.1.6-py2.6.egg/pymesos/init.py", line 1, in
from .scheduler import MesosSchedulerDriver
File "/usr/lib64/python2.6/site-packages/pymesos-0.1.6-py2.6.egg/pymesos/scheduler.py", line 18, in
from .process import UPID, Process, async
File "/usr/lib64/python2.6/site-packages/pymesos-0.1.6-py2.6.egg/pymesos/process.py", line 141
args = {f.name: getattr(msg, f.name) for f in msg.DESCRIPTOR.fields}
^
SyntaxError: invalid syntax

hi karottc, please use python 2.7,
2.6 is no longer supported by DPark

@windreamer   thx


1--return factored matrix

Fixes #1.
This PR introduces the following changes:

Update typing for kernel return types so that the expected return takes the format of a tuple of matrices ("A" and "B" for convenience) with the expectation that A @ B, their product, is the low-rank approximation returned by the kernel. (In the previous version of the code, this low-rank approximation was returned directly.)
Adds a new function, two_part_factor, in the decomposition utilities which takes an input matrix X of dimension (M x N) and rank r and returns a Tuple of two matrices ("A" and "B" for convenience) such that A @ B = X, A.shape = (M, r), and B.shape = (r, N).
Adds test for new utility function
Updates unit and integration tests for existing kernels to confirm effective use of new function
Updates documentation to describe the new return values and give example in readme

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (8d6e276) 100.00% compared to head (b8596d7) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##             trunk        #6   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           19        19
  Lines          373       382    +9
=========================================
+ Hits           373       382    +9

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[docs-infra] Improve affordance on the code block expansion

[x] I have followed (at least) the PR section of the contributing guide.

This PR's main goal is to improve the affordance of the code expansion functionality in the demo toolbar. Even though this feature is the most triggered event, we've seen some feedback floating around that people didn't know they could expand the code snippets of the demos given the <> icon button wasn't entirely clear for doing that.
So, what I did here is turn that button into a labeled one, immediately clearer. And then, simplified the copy to say "Show code" instead of "source". Additionally, to ensure the toolbar's responsiveness, I moved the "Edit in StackBlitz" feature onto the three-dot menu. According to GA, that event is not in the top 10 (it's 12, this year so far) out of the most triggered actions, so I figured it shouldn't be a super problematic change.
https://deploy-preview-38421--material-ui.netlify.app/base-ui/react-button/

I moved the "Edit in StackBlitz" feature onto the three-dot menu.

Related to #27255, and

https://analytics.google.com/analytics/web/#/report/content-event-events/a106598593w159022482p272209095/explorer-segmentExplorer.segmentId=analytics.eventAction&_r.drilldown=analytics.eventCategory:demo&explorer-table.plotKeys=[]

Related to https://github.com/mui/material-ui/issues/27255, and

So from dev editing the code, 15% use StackBlitz and 85% the codesandbox. But maybe it's better to move the copy button, or simply remove it since it is now available directly in the code view.

Uhm... that's interesting! The GA view I saw before (link here) doesn't even show StackBlitz on the top 10 action events. However, I'm cool with @alexfauquette's suggestion of removing the copy action given it's now located in the code block itself. @oliviertassinari what do you think?

Uhm... that's interesting! The GA view I saw before (link here) doesn't even show StackBlitz on the top 10 action events

That's because Olivier filtered actions that are in the demo

I was also confused, but the fact that copy-click was missing. I did not understood why so many people copy from the demo bar and not from the code preview.
But it's just because this action got filtered. It's the most used one after expend.

removing the copy action given it's now located in the code block

It's not the same copy action though. Does the TypeScript / JavaScript toggle deserve this much space?

@oliviertassinari for learning, what's the difference between the toolbar copy action versus the code block?

Note that almost nobody uses

I personally never, and the analytics says it's (7+18)/40434 = 0.06% of the use.

The analytics says it's (7+18)/40434 = 0.06% of the use, relative to the other copy button. I don't recall ever using it.

I refuse to believe it's true, because we got issues, and it seems that data are false. The copy button has a stopPropagation which prevent de to be sent to the
https://github.com/mui/material-ui/blob/master/docs/src/modules/components/CodeCopyButton.tsx/#L23-L26
      onClick={async (event) => {
        event.stopPropagation();
        await copy(code);
      }}

The only data we receive is when a demo use "iframe": true so some demo from AppBar and Container pages

Since there is no emergency for this PR, we can fix the analytics, and wait for a week of data to see which button is the most used

Does the TypeScript / JavaScript toggle deserve this much space? Developers shouldn't toggle it often.

I agree that TS/JS logos or intials could do the job

Just rolled the toolbar's copy action back in and changed the JavaScript/TypeScript toggle buttons to use their initials, consuming way less space. As much as I prefer having their full names written out, I think it allows us to solve the show/hide affordance problem without any major changes to other actions while keeping things clear ⎯ and also avoiding scope creep!

👌


vnc: Decouple VNC server from NX graphic stack

Summary
since VNC server is very useful even without NX

vnc: Decouple VNC server from NX graphic stack
grahpics: Move VNC server to drivers/video
boards/sim: Add vnc config for test

Impact
vnc server can be used without enabling nx stack
Testing
Pass new vnc config

Please ignore the false nxstyle warning:
Error: /home/runner/work/incubator-nuttx/incubator-nuttx/nuttx/drivers/video/vnc/vnc_keymap.c:123:1: error: Blank line precedes right brace at line
Error: /home/runner/work/incubator-nuttx/incubator-nuttx/nuttx/drivers/video/vnc/vnc_keymap.c:127:1: error: Blank line follows left brace
Error: /home/runner/work/incubator-nuttx/incubator-nuttx/nuttx/drivers/video/vnc/vnc_keymap.c:130:1: error: Blank line precedes right brace at line

Very @xiaoxiang781216! Because we have VNC Server and VNC Client I suggest renaming boards/sim/sim/sim/configs/vnc/defconfig to boards/sim/sim/sim/configs/vncserver/defconfig
Did you test the VNC Client on NuttX?

Very nice @xiaoxiang781216! Because we have VNC Server and VNC Client I suggest renaming boards/sim/sim/sim/configs/vnc/defconfig to boards/sim/sim/sim/configs/vncserver/defconfig

Ok, I will update the config name

Did you test the VNC Client on NuttX?

No, NuttX doesn't really implement VNC client now, just VNC server as a FB driver. VNC client is better to move to user space application. There are many 3rd party library can be ported there.

Done, @acassis please take a look.


Fixed module command.

Parameters for install and update can be >= 2 (--save, --dont-install etc).

Thanks @dekz .  Coincidentally I was working on this fix in another branch already, and did not see this PR until now.  Closing as fixed in https://github.com/jaws-framework/JAWS/pull/142 HOWEVER I still have some todo's in there to better handle params length checking (I have an idea just haven't had time to implement).  Really wish commander had sub-sub-command support :)

I am gonna steal your [install,update] help syntax tho

Hah ok cool. Do you know what the current situation is with the --save option, should this be functional now?

Yep should work, but I have to admit I haven't had time to make a testcase for it.  Here is the entry point for the logic: https://github.com/jaws-framework/JAWS/blob/master/lib/commands/module_install.js#L53
If you run into a problem with it, please open a new issue and I'll dig into it (prob tonight)


After update to version 81.0.4044.43 address bar background is white

After the update to version 81.0.4044.43 the address bar background is white.
I think it's related to this commit.

Previously, it seems that the omnibox colour was derived from the toolbar colour, but the theme author could override if they wanted to. Pretty much no one has overriden, because almost no one knew you could do so!
Now it seems that they've removed the ability to derive the colour from the toolbar, but overriding is still possible. So I'm updating my own themes to override the omnibox colour for now.

By the way, you should probably just uninstall my theme anyway :) The official dark theme has been implemented for a while; my theme has been superseded by that for months. I'll make the update, but I suggest just uninstalling the theme regardless.


No payment modalities listed

Tested with DSC 6.2 and UI 8.5.1
When creating a new resource or editing an existing resource no payment modalities are listed:

You need to update to DSC 6.3.0

Yes, I just tested and it works with 6.3.0


Single meds entrypoint for command line tools

It would be nice to have a single entrypoint for the meds command line tools. e.g.
meds convert --from omop --to meds [OMOP_PATH] [MEDS_PATH]
meds convert --from meds --to omop [MEDS_PATH] [OMOP_PATH]
meds convert --from mimic --to meds [MIMIC_PATH] [MEDS_PATH]

This would be more flexible and enable a single help command meds --help. Not sure how best to manage a single entrypoint across multiple repos.
@rafgia mentioned that he was interested in exploring possibility of converting from MEDS to other formats (e.g. MEDS -> MIMIC). Restructuring entrypoints might be an early step in implementing this?

Yeah, this seems like a really good idea.
I probably wouldn't do a single entrypoint for meds in general, but a single entry point for meds_etl is a great suggestion.


Fix cleanup pipeline not running daily

Suggested workarounds from DevOps team: Make a trivial change to the file and try again.

Closing in favor of manual scheduling.


How to edit main menu?

Thanks for the really nice minimal theme!
I was trying to edit the main menu (Home  •   Projects  •   Blog  •   About) but I couldn't find out how to do so. I'm using hugo-academic by gcushen on another site and there I can do this in the config.toml:
[[menu.main]]
  name = "Home"
  url = "#about"
  weight = 1

#[[menu.main]]
#  name = "Publications"
#  url = "#publications_selected"
#  weight = 2

The commented "Publications" pane just disappers, menu entries change when I change url or name
But I guess that is just controlling something deeper in the theme (I don't fully understand how theming works unfortunatly). So how does one change the menu if

Home  •   Projects  •   Blog  •   About

is not what is needed?

@theorangepotato How can I change the main homepage? Currently, I see Projects and About but I want it to display my latest blog posts.

@rohitbommisetti You might want to open a new issue for this if it is still a problem, as your issue seems to be different.
Also, without seeing your code, it is a little hard to see where you went wrong. Nevertheless, I recommend looking at the example site (particularly the content/ folder) to see a working example.  If you copy that exactly, it should show up as you intend, and you can tweak it from there.
Good luck!
(@JBGruber or @jhu247 Feel free to close this issue since it was fixed by PR #12 )


move bucketblocker into its own module

What does this change?
This is the minimum work required to move bucket-blocker into its own workspace so we can add additional tools. Namely, one that will rectify instances of EC2.2.
We should also rename the repo to fsbp-tools after this is merged
Currently, we have CI set up so that it is only looking for things in the bucket-blocker subdirectory. A future PR will be raised that makes use of Go workspaces to run the same kind of task across all modules.
How to test
CI and release should still work.
The commit that allowed this PR to create a release has been removed, but you can see the resulting action run here, confirming that it is able to pull the artifacts and determine whether a release should happen or not.

Does anything need to be done re the brew download for bucket-blocker?

No, the release job knows where to find the artifacts and how to version them. And this PR won't generate a release anyway so there's no work to do to update brew.


analyzer plugins crash with The system cannot find the file specified. error

https://github.com/dart-code-checker/dart-code-metrics/issues/749#issuecomment-1078981826

that doesn't seem to work anymore since i updated flutter to the master channel, no longer seeing errors in intellij despite having the plugin enabled in analysis_options.yaml:
analyzer:
  plugins:
    - dart_code_metrics

dart_code_metrics:
  rules:
    - no-empty-block

>flutter --version
Flutter 2.13.0-0.0.pre.242 • channel master • https://github.com/flutter/flutter.git
Framework • revision 10142b5817 (11 hours ago) • 2022-03-24 18:47:19 -0700
Engine • revision 816c8651d8
Tools • Dart 2.17.0 (build 2.17.0-232.0.dev) • DevTools 2.11.4

i see this when i open the analyzer diagnostics:
ProcessException: The system cannot find the file specified.

  Command: C:\Users\amogus\Documents\flutter\bin\cache\dart-sdk\bin\pub.bat upgrade
#0      _ProcessImpl._runAndWait (dart:io-patch/process_patch.dart:487:7)
#1      _runNonInteractiveProcessSync (dart:io-patch/process_patch.dart:632:18)
#2      Process.runSync (dart:io-patch/process_patch.dart:68:12)
#3      PluginManager._computeFiles (package:analysis_server/src/plugin/plugin_manager.dart:641:28)
#4      PluginManager.filesFor (package:analysis_server/src/plugin/plugin_manager.dart:462:14)
#5      PluginManager.addPluginToContextRoot (package:analysis_server/src/plugin/plugin_manager.dart:328:23)
#6      PluginWatcher.addedDriver (package:analysis_server/src/plugin/plugin_watcher.dart:68:19)
#7      AnalysisDriver.configure (package:analyzer/src/dart/analysis/driver.dart:555:33)
#8      ContextBuilderImpl.createContext (package:analyzer/src/dart/analysis/context_builder.dart:137:12)
#9      new AnalysisContextCollectionImpl (package:analyzer/src/dart/analysis/analysis_context_collection.dart:67:36)
#10     ContextManagerImpl._createAnalysisContexts.performContextRebuildGuarded.performContextRebuild (package:analysis_server/src/context_manager.dart:449:40)
#11     ContextManagerImpl._createAnalysisContexts.performContextRebuildGuarded.performContextRebuild (package:analysis_server/src/context_manager.dart:444:41)
#12     ContextManagerImpl._createAnalysisContexts.performContextRebuildGuarded (package:analysis_server/src/context_manager.dart:559:17)

#13     ContextManagerImpl.setRoots (package:analysis_server/src/context_manager.dart:280:5)

#14     AnalysisServer.setAnalysisRoots (package:analysis_server/src/analysis_server.dart:456:7)

#15     AnalysisSetAnalysisRootsHandler.handle (package:analysis_server/src/handler/legacy/analysis_set_analysis_roots.dart:50:7)

CC @scheglov @bwilkerson
I see we run pub directly in analysis_server, which might be removed in Dart 2.17? Actually, according to the changelog, it was removed in 2.16: https://github.com/dart-lang/sdk/blob/main/CHANGELOG.md#tools-1
pkg/analysis_server/lib/src/plugin/plugin_manager.dart:      var pubPath = path.join(path.dirname(vmPath), 'pub');

Marking as P1 unless we think this is not on the hot path for analyzer plugins.

Interestingly, I see from code that we should not be able to run pub, but somehow we get the plugin configured.

Ah, I still have pub in my xcodebuild/ReleaseARM64/dart-sdk/bin, remaining there since the time it still existed.

This seems to help.
https://dart-review.googlesource.com/c/sdk/+/240901

One more reference, but can be fixed separately:
pkg/analysis_server/lib/src/services/pub/pub_command.dart:      Platform.isWindows ? 'pub.bat' : 'pub',

@srawlins @scheglov - I see the fix for this landed. See my comment on the dup of this issue - https://github.com/dart-lang/sdk/issues/48786#issuecomment-1095536945; we'll probably want to file a cherry pick request for the fix.

Hey, any news about it being cherry-picked to earlier versions?
With Flutter 3.0 and Dart 2.17 being released to stable, it now blocks using the analyzer plugins.

+1 This makes all plugins crash, especially dart_code_metrics which provides many useful linter rules in addition to official rules

+1. dart_code_metrics is still crashing because of this

Hey @devoncarew,
is there an estimated date when this fix will be available in Dart >2.17.0 and Flutter >3.0.0?

Could the fix be cherry-picked in the latest Dart stable release?

Execute flutter upgrade. With the new flutter version  3.0.1 it's working again.


loading Serlo video page fails

at Renate's Laptop, Firefox 39.0, Windows 7 Ultimate
It does work on my Laptop

Confirmed, Firefox 39.0, OS X 10.10.4. JS Console:
The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol.

This is most likely caused because varnish doesn't (currently) separate between AJAX and regular requests, but the backend does. If anyone has an idea (or link) how to fix this, it would be much appreciated.

Remember: de.serlo.org/1234 is used for
a. redirecting
b. injections


Fixes #188 in the master repo by replacing the path in the import with the new path

This changes has been tested in our app and we didn't find any issue. The changes are a simple find and replace with the new path for the import and should be ok to be merged now.
Thanks for all your effort in your awesome library.

Add >=15.4.0 as peer dependency

Are there any outstanding issues with this patch which prevents it from being merged? Given the pace of RN it'd be nice to get this great library up and working with RN 0.38.

This is working well for me. What else will it take to have this merged? Please, let me know and I will see if there is something I can do to help get this merged.
Thanks!

Thanks for this PR.
I'll get this merged later.
Quite busy those days


Problem with setting Filter and Mask during bus traffic

Hello,
I have got still trouble with setting Filters and Masks when other Nodes are sending messages very fast:
My Shield is using in industrial application and I do not have influence if other nodes are sending and with which frequency. So when there is a node sending messages (with IDs which should be blocked) when MCP is initializing, filtering does not work because I only can call init_Mask and init_Filt after CAN.begin is called. Maybe it is better if there is a possibility to set filters and masks before CAN.begin.
Example: A node is sending on ID 5 very, very fast all time.
When starting sketch I call CAN.begin and init_Mask and init_Filt to receive ID 522 only.
    if(CAN_OK == CAN.begin(CAN_500KBPS))                   // init can bus : baudrate = 500k
    {
        Serial.println("CAN BUS Shield init ok!");
        CAN.init_Mask(0, 0, 0x3FF);
        CAN.init_Mask(1, 0, 0x3FF);
        CAN.init_Filt(0, 0, 0x20A);
        CAN.init_Filt(1, 0, 0x20A);
        CAN.init_Filt(2, 0, 0x20A);
        CAN.init_Filt(3, 0, 0x20A);
        CAN.init_Filt(4, 0, 0x20A);
        CAN.init_Filt(5, 0, 0x20A);
        delay(100);
        Serial.println("masks and filters set!");
    }

The result: No message is filtered. All messages from all IDs arrive the buffer. MCP gets overflow.
If there is no other Node sending data when resetting MCP, the filtering is working find and only ID 522 comes into buffer.

Hi, I'm using your fork, But I have same probleme to init mask.
I want to get 0x613 ID only, I tried this code, but i got return to previous mod failure, init mask failure :
`#include <mcp_can.h>
#include <SPI.h>
long unsigned int rxId;
unsigned char len = 0;
unsigned char rxBuf[8];
MCP_CAN CAN0(10);                          // Set CS to pin 10
void setup()
{
Serial.begin(115200);
if(CAN0.begin(MCP_STDEXT, CAN_500KBPS, MCP_16MHZ) == CAN_OK) Serial.print("MCP2515 Init Okay!!\r\n");
else Serial.print("MCP2515 Init Failed!!\r\n");
pinMode(A5, INPUT);             /*I'm using TFT SCREEN which need pin 2, so i plugged pin 2 of canbus shield to A5 on my uno board */
CAN0.init_Mask(0,0,0x06FF0000);                // Init first mask...
CAN0.init_Filt(0,0,0x06120000);                // Init first filter...
Serial.println("MCP2515 Library Mask & Filter Example...");
CAN0.setMode(MCP_NORMAL);                // Change to normal mode to allow messages to be transmitted
}
void loop()
{
if(!digitalRead(A5))                    // If pin 2 is low, read receive buffer
{
CAN0.readMsgBuf(&rxId, &len, rxBuf); // Read data: len = data length, buf = data byte(s)
Serial.print("ID: ");
Serial.print(rxId, HEX);
Serial.print(" Data: ");
for(int i = 0; i<len; i++)           // Print each byte of the data
{
if(rxBuf[i] < 0x10)                // If data byte is less than 0x10, add a leading zero
{
Serial.print("0");
}
Serial.print(rxBuf[i], HEX);
Serial.print(" ");
}
Serial.println();
}
}
/*********************************************************************************************************
END FILE
*********************************************************************************************************/`
Could you tell me if I'm wrong or if it's doesn't work yet  ?

There was a bug in the library, re-download or correct the typo in mcp_can.cpp.
Also, there are five filters and two masks, by only setting one, you will receive ID 000 and potentially receive extended ID 00000000 as well.  The mask should be 7FF otherwise that mask will receive IDs 612 and 712 since that bit isn't masked and thus ignored.

thank you !! perfect.
I changed init line, giving MODE_CONFIG constant parameters, and replacing STDEXT by MODE_CONFIG in your library. I was able to set mask and filter before set normal mode, even if I have error while returning to previous mod :)
It's work fine !
https://www.youtube.com/watch?v=zJZtAQl4v20

@psy460
Can you post the complete modified library?
Thanks mate.

Use my fork of this CAN library... and set your masks and filters before the CAN.setMode(MCP_NORMAL) function in the setup function.  If you need to change masks and filters while live, your routine will have to CAN.setMode(MCP_LOOPBACK), do changes and then CAN.setMode(MCP_NORMAL) or the filters and masks behave in undesirable ways.


<!-- throw err ^    ? trying to run a Lynda.com exercise and I get this; what's a throw err?

Bug Report or Feature Request (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ ] feature request

Versions.

Repro steps.

The log given by the failure.

Desired functionality.

Mention any other details that might be useful.

Thanks for reporting this issue. However, you didn't provide sufficient information for us to understand and reproduce the problem. Please check out our submission guidelines to understand why we can't act on issues that are lacking important information.
If the problem persists, please file a new issue and ensure you provide all of the required information when filling out the issue template.


Do not use Autoprefixer for text-decoration property with CSS var as value

I just noticed that Autoprefixer adds a vendor prefix for the text decoration property (-webkit-text-decoration), which uses the CSS var as its value, for example:
    -webkit-text-decoration: var(--ifm-link-hover-decoration);
    text-decoration: var(--ifm-link-hover-decoration)

I'm not sure if this is an Autoprefixer bug, as this property has "extra" values that have little support yet. https://caniuse.com/?search=text-decoration
Since we are using "regular" values, we should explicitly disable Autoprefixer for this property.

Apparently forgot to do this, thanks for letting me know, I'll fix it soon.
2021-02-17 18:58 GMT+03:00, Bartosz Kaszubowski<EMAIL_ADDRESS>
@Simek commented on this pull request.

@@ -22,7 +22,6 @@ const scss = require('postcss-scss');

module.exports = (options) => ({
plugins: [

autoprefixer(),

@lex111 So why you have left import for autoprefixer and package
definition in the dependencies?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/facebookincubator/infima/pull/49#discussion_r577731904

Apparently forgot to do this, thanks for letting me know, I'll fix it soon. 2021-02-17 18:58 GMT+03:00, Bartosz Kaszubowski<EMAIL_ADDRESS>…
@Simek commented on this pull request. > @@ -22,7 +22,6 @@ const scss = require('postcss-scss'); module.exports = (options) => ({ plugins: [ - autoprefixer(), @lex111 So why you have left import for autoprefixer and package definition in the dependencies? -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: #49 (comment)

It's already fixed in #58

@lex111 I have also left few comments in various, already merged PR by you. It would be nice, if you can address the question and comments in there too.


Option to add username and password for user

I need to add a user name and password for user to be able to connect instead of using the certificate. What changes are required?

This is not an issue with the script and this will not be supported in the near future.
https://www.google.com/search?q=openvpn+username+password

Can I avail your services to do some modifications in the script?

Ability to connect via user name and password. In built certificate to connect not required for my use case.
Ability for unlimited users to connect with same username and password.

I am willing to pay/donate. Let me know.

Here you have the script modified to add the two features you requested:

PAM authetication used instead of client certificates
duplicate-cn to allow multiple connections per user

https://gist.github.com/Nyr/01717d9cf5db045e9520
This is only to satisfy your request and totally unmaintained/unsupported.
Pay/donate whatever you want.

I was under the impression you would maybe "forget" to pay if I acted in good faith and provided the work first + allowed you to contribute as little as you felt was right for my time.
It doesn't surprise me I wasn't wrong after all and you didn't keep your word.


Wfc605

Refer to this link for build results (access rights to CI server needed):
https://fabric8-ci.fusesource.com/job/wildfly-camel-pullreq/435/
Test PASSed.


Fix blevebindings script to not use GOPATH

Description
It was writing files to $GOPATH/src/$packageName, which is not what we want. It just happened to work in CI.
Checklist

[x] Investigated and inspected CI test results
[x] Unit test and regression tests added
[x] Evaluated and added CHANGELOG entry if required
[x] Determined and documented upgrade steps
[x] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
Local testing

while you're here, can you change the wrapper to use python3 :)

I took a look, we just call python and the code is written in a way that's compatible with either version. I don't know if we should just blindly change that to python3, since I'm not sure if the standard is to always have a python3 binary available.

I took a look, we just call python and the code is written in a way that's compatible with either version. I don't know if we should just blindly change that to python3, since I'm not sure if the standard is to always have a python3 binary available.

Python2 is completely sunset and I've already changes a bunch of the other bindings to python3 and no one has hollered. Python binary isn't installed on any macs anymore :(

I took a look, we just call python and the code is written in a way that's compatible with either version. I don't know if we should just blindly change that to python3, since I'm not sure if the standard is to always have a python3 binary available.

Python2 is completely sunset and I've already changes a bunch of the other bindings to python3 and no one has hollered. Python binary isn't installed on any macs anymore :(

Oh, I always thought they would make python point to python3 eventually? Do they not?

 python
-bash: python: command not found

I took a look, we just call python and the code is written in a way that's compatible with either version. I don't know if we should just blindly change that to python3, since I'm not sure if the standard is to always have a python3 binary available.

Python2 is completely sunset and I've already changes a bunch of the other bindings to python3 and no one has hollered. Python binary isn't installed on any macs anymore :(

Oh, I always thought they would make python point to python3 eventually? Do they not?

In any case, I've updated it. Didn't realize you had change some of the others already.


Update dependency requirements-dev.txt for aide_design

@ethan92429 should aide_render be included in the dependencies list now that we're using it for the classes?

@fletchapin I think that makes sense... All of these packages will be included in the Aide package that Oliver and Anishka are working on.

We've moved to using pipenv.


Implement dedicated error variant when executable file cannot be found

This is an edge case, but sometimes the error message, cannot find executable, will be misleading. I poked around a bit, and not-found errors can occur because, for example, a dynamically linked library could not be found. It might be better to keep the error generic, something like:
File not found error when executing `BINARY`: IO-ERROR

Here's an example of a someone being befuddled about a file not found when the executable does exist:
https://unix.stackexchange.com/questions/378301/linux-executable-fails-with-file-not-found-even-though-the-file-is-there-and-i
Aside from that this looks good!

Good point. I'll change it.


Porting the CI/CD system to GitHub Actions

PR #855 started to implement the current CI system in GitHub Actions. A couple of things are missing to make it fully functional and be able to replace Travis and Appveyor:

[ ] Solve problem with Sundials libraries in MacOS. They seem to install properly, but tests fail, complaining they are not found.
[ ] Implement a scheduled testing. This should be easy by using on.schedule.
[ ] Implement a CD system to deploy PyBaMM to PyPI after a tagged commit to the master branch. Again, this should be easy using this Action.

I also had problems with sundials libraries in MacOS. One difference is you need to specify DYLD_LIBRARY_PATH instead of LD_LIBRARY_PATH.

I think this can be closed? Re-open if not


refactor: Change tilelayer URL

Refactor Request
** discord username: autoMagic#2912 **
Is your refactor request pertaining to a problem? Please elaborate.
We'd like to replace the tilelayer URL used from the start on, with a production ready tilelayer with a Google Maps API key (the key is incoming).
Suggested solution
We'd like to replace the tilelayer URL used from the start on, with a production ready tilelayer with a Google Maps API key (the key is incoming).
Additional context
None

İlgili dokümantasyon: https://developers.google.com/maps/documentation/tile/request-tile?hl=tr#tile-request

@EmirBoyaci projeye ekleyin approval dan sonra.

is this still a valid issue? is it being worked on? if not i can take this. i would need the API key of course

@EmirBoyaci

We are currently waiting for API key. I will introduce PR after we get API key.


Attempting to create a new tracker using an existing namespace should do nothing

Inspired by this user group thread: https://groups.google.com/forum/#!topic/snowplow-user/UGHyekhRn8Y

At the moment, the new tracker shadows the old tracker but page pings and event handlers set up by the old tracker still work.

java -jar node-v1.0.jar --key key.store 2>&1 &
// customize some configuration
java -jar node-v1.0.jar --server.port=8081 --spring.profiles.active=dev --key key.store 2>&1 &TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t


ImportError: No module named densecrf

Hai,
I installed densecrf module using
python setup.py install
It got installed succesfully.
import pydensecrf---->works
import pydensecrf.densecrf as dcrf----> fails with Import error..
Kindly suggest how to go further

you should put init.py   into the  file: densecrf.

huh, that's odd, it works just fine for me, and I can't reproduce your problem, no matter what I try. I will need more info in order to help here.
@yaxingwang That file has existed for a long time, are you somehow missing it?

Also, the recommended way of installing is now through pip from the cheeseshop pip install pydensecrf.

Problem got solved since i copied .so files from /usr/loca/pydense.egg to my local directory. Iam able to retrieve the result. Thanks for your kind reply.


Mark AfterAccess policy internal

This does not need to be part of the public API surface.

coverage: 98.6% (-0.04%) from 98.642%
when pulling 2ef610c5a3e400788c71b9001aba8b712ec0bc01 on users/alexpeck/makeint
into ba6ddc052a6dc9f11b64da4a1add071c3d5f0b44 on main.


[Bug] error when lineDash is function in vchart

Version
1.7.4
Link to Minimal Reproduction
no need
Steps to Reproduce
related issue in vchart: https://github.com/VisActor/VChart/issues/1746
Current Behavior

Expected Behavior
no error
Environment
- OS:
- Browser:
- Framework:

Any additional comments?
No response

the attribute of area
{
    "lineDash": [
        1,
        0
    ],
    "segments": [
        {
            "lineDash": [
                1,
                0
            ],
            "points": [
                {
                    "x": 0,
                    "y":<PHONE_NUMBER>156216,
                    "lineDash": [
                        1,
                        0
                    ],
                    "y1": 304,
                    "context": "20231212_b28a7cc47b8d9f3e453677c61401dd62,1,bulk_copy_dashboard,B"
                }
            ]
        },
        {
            "lineDash": [
                5,
                3
            ],
            "points": [
                {
                    "x": 1807,
                    "y": 304,
                    "lineDash": [
                        5,
                        3
                    ],
                    "y1": 304,
                    "context": "20231213_b28a7cc47b8d9f3e453677c61401dd62,1,bulk_copy_dashboard,B"
                }
            ]
        }
    ],
    "points": null,
    "visible": true,
    "lineWidth": 2,
    "lineCap": "round",
    "lineJoin": "round",
    "fillOpacity": 0.2,
    "fill": "#1AC6FF",
    "stroke": [
        "#1AC6FF",
        false,
        false,
        false
    ],
    "defined": true,
    "connectedType": "none",
    "pickable": true,
    "clipRange": 0
}

https://github.com/VisActor/VChart/issues/1746


⚠ Bofrost.ch has degraded performance

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

HTTP code: 200
Response time: 2786 ms

Resolved: Bofrost.ch performance has improved in 1363ee6.


Three OCR errors in the file 汉字表 2023 （only 3000).csv

I noticed three OCR errors in levels 7-9 relevant for the file: 汉字表 2023 （only 3000).csv

脏 (a HSK2 character) should be 赃 [page 29, character 1101 in the Standards]
洵 should be 汛 [page 29, character 1000]
箫 should be 萧 [page 28, character 957]

(I think these have already  been fixed in 汉字.csv)

I will check it, thanks!

You are right 汉字.csv) more accurate. I will remove 2023 file.


Add support for Polled clusters and use it for ts011f plug Metering

ts011f plug is known not to properly report Metering information and they need to be polled periodically.
I've implemented this initially just for this plug implementation, but given it can be useful for other devices too, I decided to generalize it a bit (allowing different polling frequency per each attribute, that makes things to complicate a bit as I wanted to prioritize batched queries anyways...).
Let me know if this is not wanted, in any case commits are atomic so I could squash them or just use the initial ones.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

25 of 111 (22.52%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-1.1%) to 79.304%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

zhaquirks/init.py
22
108
20.37%

Totals

Change from base Build<PHONE_NUMBER>:
-1.1%

Covered Lines:
4583

Relevant Lines:
5779

💛  - Coveralls

I think this is a great contribution. Any chance you can add tests for the device monitor and polling cluster implementations

@Adminiuga / @puddly any thoughts on this one?

We may want to start documenting reusable parts like this also… probably time to start creating development docs aside from the getting started stuff to make it easier for folks to contribute

IMO we're taking the wrong approach with Tuya -- we are over complicating the quirks, just to make Tuya to appear as a regular ZCL compliant device and they are not.
I think the quirks just should define the data point types in the manufacturer specific channel and essentially in ZHA we  define  the entities based on the data points, manufacturer and model (like we somewhat do already for Tuya valves)
In other words instead of the quirk reading the attribute regularly and exposing that data over the metering cluster, let's have a polled ZHA sensor entity which reads the  consumption data point directly and exposes it as a meeting sensor?

@dmulcahey yeah, I was thinking indeed to add tests... However I also wanted a prior feedback on the idea first :)
@Adminuga, sure I see that approach as something fair indeed. I wanted to get something quickly working for my setup so I started at the point where I had to touch less aspects.
However, in the ZHA approach: I would think that zha-device-handlers should still provide an hint to ZHA about whether they want a polled sensor for a entity or not, no?
As I assume other devices like this may be around and it would be annoying to handle this specifically for them all, while just changing a quick bit could be easier and quicker.

However, in the ZHA approach: I would think that zha-device-handlers should still provide an hint to ZHA about whether they want a polled sensor for a entity or not, no

How does this quirk know that it has to poll the "consumption" cluster/data point? Zha could use the same criteria.
And depending how it's done, may take same approach bas with HUE lights which are also polled.

Well in this case we're just hardcoding this information...
But I had the feeling that this was also the point of this repository: add all the device specific information so that upper levels can just process the data accordingly.
Thus, while I'm fine to have ZHA to handle the polling itself, IMHO would be better if the device handlers would expose to it (and other zygpy customers, if any) such detail. In this way, there's not device-specific code hardcoded in ZHA, but only class-specific (i.e. device.pid == 'foo' and device.gid == 'bar' vs device.cluster_foo.needs_polling().
I was wondering if in some cases there should be also a "fallback" mode for ZHA to just try to poll (at least the powered) devices when some endpoint doesn't get updated for a long time, but not sure if that would be correct to cover all the cases.

However, in the ZHA approach: I would think that zha-device-handlers should still provide an hint to ZHA about whether they want a polled sensor for a entity or not, no

How does this quirk know that it has to poll the "consumption" cluster/data point? Zha could use the same criteria. And depending how it's done, may take same approach bas with HUE lights which are also polled.

while I see your point I'll add that doing it here would allow this functionality to work for the other home automation platforms that are adopting Zigpy and it would allow us to keep mfg specifics out of HA. If we can make this clean enough it may make sense to migrate what is already in HA to quirks... either way will work it's more a matter of how do we want this to work?

it may make sense to migrate what is already in HA to quirks

As you mentioned, there have to be device/manufacturer specifics and whether those should be inside HA/ZHA is another topic which I don't have strong feeling about.
Quirks are fine for fixing a small deviation/non standard behavior here or there, but Tuya proved, bringing their devices to look like a normal ZCL compliant implementation could be done, but quickly gets out of hand and increases complexity.
In other words, zigpy/quirks should be left to deal with ZigBee and ZCL layer interfacing (like defining new attributes, commands or fixing/overriding some attribute values), and manufacturer/device specific behavior/implementation should be handled at the layer above it. Maybe split ZHA channels out of HA and morph them into proto-entites/channels?

My Blitzwolf SHP-15 power plugs are crippled because as this pull request describes, they do not automatically report the total power consumed and require polling.
In the meanwhile, is there a way I can get ZHA to poll this manually? (By adding a timed automation or even an external script etc.). Restarting the ZHA integration retrieves this value once, but I can't really just go around and restart ZHA every 4 hours or so...

I wrote a python script that uses the home assistant websocket to detect the plugs and poll the energy consumption: https://github.com/dumpfheimer/hass_zha_attr_poll_workaround
Maybe this is enough for you or at least gives you an idea on how to make your own workaround.

I have a lot of these plugs. How can I implement this?

Hi @3v1n0
May I ask, how many of these plugs do you have in your network?
The reason why I am asking is: I made a workaround over websockets and polled the energy for all plugs in a regular interval. I noticed that they jam the network when too many are polled at the same time (I have > 10 of them).
I then added a minimum time between polling the devices (10 or 20s not sure anymore) which improved network reliability again. The difference was subtle but definately noticable (mostly remote controll button events were dropped).
Has anyone experienced the same issue?
If this is repreducable it might be considered in the polling cluster.

I have about 15 of these plugs. Made a workaround using ZHA Toolkit, and a automation for attribute read that runs every 5 minutes. Have not experienced any issues, but I don't  have much other traffic on my zigbee network, yet.

Do all the plugs poll at the same time / pretty much at the same time?
Are you also on a ZNP coordinator?
I was polling the attributes every minute and I think it was the worsed when 1 or 2 of the plugs were not available / unplugged and it was trying and retrying to reach them.

They're all in the same automation, so pretty much polled at the same time. I use the Sonoff zigbee WiFi-bridge with Tasmota FW.
I have not activated any re-tries, as it's not critical.

Okay, thanks.
I will try to replicate the issues as soon as this PR is merged. Maybe it was something else.

With this patch the TS011F-Plugs are working fine. Problem is with every update the fix is gone and need to be replaced. Is there an approach to make this fix persistent?

Try the ZHA toolkit and the following automation:
alias: Update energy
description: ''
trigger:

platform: time_pattern
minutes: /5
condition: []
action:
service: zha_toolkit.attr_read
data:
ieee: sensor.varmepumpe_smartenergy_metering_summation_delivered
cluster: 1794
attribute: 0
mode: single

Try the ZHA toolkit and the following automation:
`alias: Update energy description: '' trigger:

platform: time_pattern
minutes: /5
condition: []
action:
service: zha_toolkit.attr_read
data:
ieee: sensor.varmepumpe_smartenergy_metering_summation_delivered
cluster: 1794
attribute: 0
mode: single`

Thank you for your solution! With the downside though, that I have to do this for every plug  ;)

If you are willing to run a separate script that uses a websocket connection (you will need an API key) to hass you can check out https://github.com/dumpfheimer/hass_zha_attr_poll_workaround
It should automatically detect the devices.

Thank you for your solution! With the downside though, that I have to do this for every plug ;)

I have them all listed in the same automation.

@3v1n0 Thank you very much for your solution and I hope it will be integrated in zigpy soon.
This works perfectly with my TS011F OEM plug "Blitzwolf BW-SHP15" from Banggood.
I noticed that my plug also does not send updates about its On/Off status on changes, e.g. initial state when replugging or when using the plug's button, but after reading the on_off attribute from the TuyaZBOnOffAttributeCluster cluster, the status is updated correctly. So also pulling the On/Off status could be worth for full compatibility.

Try the ZHA toolkit and the following automation:
[...]

Happy to use this workaround for the meanwhile but looking forward seeing this quirks merged into release soon. Thanks

we're going to go with this approach: https://github.com/home-assistant/core/pull/71527
Thanks for the contribution though

we're going to go with this approach: https://github.com/home-assistant/core/pull/71527
Thanks for the contribution though

ZHA

How do i add this automation? So far, i only use the gui for automations: /config/automation/edit/new

With the polling feature that has been merged into ZHA, an automation should no longer be necessary, as long as the polling quirk is enabled for the device. So if it does not work out of the box for your device, you should open an issue to get your device added.
To use an automation in the meanwhile, you also can add this via GUI, either by setting up the time_pattern trigger and zha_toolkit service call action by GUI, or by switching the GUI editor to yaml mode via three dots menu, the yaml above, "Edit as yaml", and pasting the yaml from above. After pasting the yaml source, you may also switch back to GUI mode via three dots menu and continue editing the automation via GUI.


Update adapter setting in svelte.config.js

fallback option by default is null.  When executing build, "npm run build," fallback is needed.

Much appreciated, thank you!

Isn't fallback supposed to be a string?

Isn't fallback supposed to be a string?

When you want to redirect it to the fallback page, it is a string, '200.html'. Otherwise, it is a Boolean, and SvelteKit __error.svelte is used.


"Ghenetea,Cheț" is a locality in "MARGHITA" city, "BIHOR" county

Description
Check that the locality is displayed in the search bar in accordance with Act 2 02/16/1968

Precondition
Empty the search bar after every step

Steps 1
Acces to the link https://peviitor-ro.github.io/ui.orase/
Expected result
The page opens

Steps 2
Write "Cheț"
Expected result
In the drop down menu you find "Cheț, BIHOR(MARGHITA)"
Test Data
Cheț

Steps 2
Write " Ghenetea"
Expected result
In the drop down menu you find " Ghenetea, BIHOR(MARGHITA)"
Test Data
Ghenetea


feat(clustering) optional config override for protocol.

Not a feature flag, but an override.  The DP performs the negotiation as
usual, but if the setting has a non-nil value, it's used instead of the
negotiated one.
Also handy for doing every test on both protocols.

As people suggested, just for testing is not a good reason to do so, and this option is very likely to be abused by users.
Can we find a better solution, like a patch before (and only for) tests?

I think this is how the code should function:

DP has a hardcoded list of protocols it supports
DP sends this over to CP
CP responds back with the protocol chosen
DP and CP start communicating on this protocol

The configuration option being added here influences step 2, the DP still must send the protocol over to the CP to negotiate it.

As people suggested, just for testing is not a good reason to do so, and this option is very likely to be abused by users.

It depends on how you look at it. It can also be useful if there is a serious bug in a newer protocol. Giving an escape hatch to our users is an insurance policy that we should buy.
If by "abuse" you mean that certain bugs can be exploited, I see your point. An attacker could certainly use that surface but if an attacker has gained permission to change kong.conf, there are other bigger worries than the exploitation of bugs in Kong. What do you think?

I think this is how the code should function:

DP has a hardcoded list of protocols it supports
DP sends this over to CP
CP responds back with the protocol chosen
DP and CP start communicating on this protocol

The configuration option being added here influences step 2, the DP still must send the protocol over to the CP to negotiate it.

As people suggested, just for testing is not a good reason to do so, and this option is very likely to be abused by users.

It depends on how you look at it. It can also be useful if there is a serious bug in a newer protocol. Giving an escape hatch to our users is an insurance policy that we should buy.
If by "abuse" you mean that certain bugs can be exploited, I see your point. An attacker could certainly use that surface but if an attacker has gained permission to change kong.conf, there are other bigger worries than the exploitation of bugs in Kong. What do you think?

By design, CP is compatible with older DPs, but not vice versa, and maybe later we will stop maintaining the DP's backward compatibility. The design to designate versions from DP will be meaningless in that case, and the tests depending on this will also fail.
By "abuse" I mean, it would always be a bug if the newer version fails. The better option would be for users to switch back to an older version of the gateway itself, rather than using an older version of the protocol.

And I‘ve considered CP to pretend it does not support newer protocol, but the main purpose of this test is to show that newer CP supports older DPs

I feel that different things are conflated here.  It would be great if a single concept could manage everything, but first we have to be sure what we're talking about:

Both CP and DP have hardcoded lists of what they support.  I think it's best for this to be hardcoded, since it should reflect the respective code capabilities on each side.
DP presents the CP with its supported list.
CP responds with the entries it prefers.  currently the algorithm is trivial: pick the first entry from it's own list that also appears on the DP list.  But it could be as complex as we want.  for example, we could set a list of node-specific overrrides.  or allow some version only if the DP also asks for another specific service.  or whatever.
Both CP and DP keep the negotiation results and could read them and use for whatever purpose.  currently neither side stores a list of other non-chosen options from the other side.

the version negotiation task finishes there.  It's supposed to work with any service we want to expose on wRPC, but actually the "service" could be anything that we want to define versions on.
In order to allow some "manual override" from the DP, I first thought of something very general, so we wouldn't have to rewrite for any new protocol/version.  my first Idea was to add a "ban list" that removes version or services from the DP list before step 2 (the empty default would mean no change).  It wasn't well received, so I came up with this other solution (the one implemented in this PR).  It doesn't interfere with negotiation at all.  It simply adds a specific configuration option which, if set, is used instead of whatever was specified in the negotiation. If any other code consults the negotiation option, it's still what the CP accepted and not (necessarily) what the DP actually used.

hey guys, how can we get this moving?
I really think we need this or some other solution that allows a DP to override whatever is negotiated.  not to be used everywhere, but to fix specific problems, and sometimes to troubleshoot complex interactions between DP and CP, especially around updates.
As I see it, there are some different options:

specific flags that are checked by a given feature to choose, ignoring the negotiation (this PR, for protocol)
a "banned services/versions" setting that removes options from the set the DP presents to the CP.  This keeps the negotiation process but allows the user to avoid a particular codepath.
tweak the CP choosing/rejection logic?

I'm ok with either (my personal favorite is number 2), but something is necessary

hey guys, how can we get this moving? I really think we need this or some other solution that allows a DP to override whatever is negotiated. not to be used everywhere, but to fix specific problems, and sometimes to troubleshoot complex interactions between DP and CP, especially around updates.
As I see it, there are some different options:

specific flags that are checked by a given feature to choose, ignoring the negotiation (this PR, for protocol)
a "banned services/versions" setting that removes options from the set the DP presents to the CP.  This keeps the negotiation process but allows the user to avoid a particular codepath.
tweak the CP choosing/rejection logic?

I'm ok with either (my personal favorite is number 2), but something is necessary

I think it would be better for CP to return a list of all accepted protocols, preferably sorted by priority.

I think it would be better for CP to return a list of all accepted protocols, preferably sorted by priority.

that is not how version negotiation works (CP returns a single chosen version for each accepted service), nor what this PR is about (allowing the administrator to override negotiation)
I don't see how changing the negotiation protocol would change this PR.  it would still require some override mechanism.

I think it would be better for CP to return a list of all accepted protocols, preferably sorted by priority.

that is not how version negotiation works (CP returns a single chosen version for each accepted service), nor what this PR is about (allowing the administrator to override negotiation)
I don't see how changing the negotiation protocol would change this PR. it would still require some override mechanism.

The purpose of this PR is to allow users to force the use of a certain protocol.
The wrpc protocol may also be upgraded in the future, such as wrpcv1.1 wrpcv1.4 wrpcv2.0, etc.
If the user wants to use wrpcv1.4. but the response from the CP maybe "I accept wrpcv2.0", but in reality, the CP may still support wrpcv1.4. this can cause some problems.

I personally believe that even if we want to hack with the DP version, we need to follow the standard, especially for the negotiation.
So it's better we do this from the list of "supported versions", to fake a list with only the designated version.

The purpose of this PR is to allow users to force the use of a certain protocol.

That is incorrect. The purpose is to make DP use a specific version of a wRPC service. This doesn't cover different versions of wRPC spec itself.
The purpose here is to force a specific version from the DP and assert DP and CP behaviors from that configuration.
Yes, it is possible that the CP doesn't support the version being forced by this configuration property, and that is completely okay.
Why? Let's take a step back, this feature is really for debugging and more so testing of DP with different CP implementations, as well as to allow for testing for older versions of a wRPC service (once there are multiple versions of wRPC service - not the case yet).

obsoleted by #8775


Remove duplication of functionality between webPreload and webviewPreload

The duplication of this functionality we have between webPreload and webviewPreload (also maybe rename the latter file to make it clearer it is the SAFE functionality executed on preload?)
To do-

[x] Remove duplicate code between WebViewPreload and WebPreload
[x] Move createRemoteCall from WebViewPreload to WebPreload

This issue is resolved with #950.


Basic skeleton for dist binary

This implements the basic structure of the dist binary following the UX proposal in #43 so it will be subject to change, but provides a working base nevertheless.
General usage
$ ./dist --help
NAME:
   dist - Package and ship Docker content

USAGE:
   dist [global options] command [command options] [arguments...]

VERSION:
   0.0.0

AUTHOR:
  Author - <unknown@email>

COMMANDS:
   list		List available images
   pull		Pull and verify an image from a registry
   push		Push an image to a registry
   help, h	Shows a list of commands or help for one command

GLOBAL OPTIONS:
   --help, -h		show help
   --version, -v	print the version

List images
$ ./dist list --help
NAME:
   list - List available images

USAGE:
   command list [arguments...]

Pull images
$ ./dist pull --help
NAME:
   pull - Pull and verify an image from a registry

USAGE:
   command pull [command options] [arguments...]

OPTIONS:
   -r, --registry "hub.docker.io"	Registry to use (e.g.: localhost:5000)

Push images
$ ./dist push --help
NAME:
   push - Push an image to a registry

USAGE:
   command push [command options] [arguments...]

OPTIONS:
   -r, --registry "hub.docker.io"	Registry to use (e.g.: localhost:5000)

Updated with a stripped down version that only has list, push, and pull, so we can start playing around with the registry/client/ interfaces.
Ping @stevvooe @crosbymichael

Updated: list renamed to images.

LGTM!


[Production & Staging] Fix typo in component warning modal

Steps

Log in to osf.io.
Navigate to one of your private projects.
Create a component if you do not already have one.
Click "Make Public" from the component page.
Read warning modal.

Current message:
Once a component is made public, there is no way to guarantee that access to the data it contains can be completely prevented. Users should assume that one a component is made public, it will always be public […]
Change to:
Once a component is made public, there is no way to guarantee that access to the data it contains can be completely prevented. Users should assume that once a component is made public, it will always be public […]

Fixed. Closing.


Make v3 format as default segment format

All servers will convert all segments to v3 format by default.
Tables can be explicitly configured to use v1 format. Segment
generation is still in v1 format. This commit is first step towards
making v3 format as default.

will this happen in prod as well? What happens in the case of refresh and real-time scenarios, will the segment not be available during conversion?.
Should we not start generating segments in V3 format during creation before pushing this change. I understand we still need to generate indices on the fly when needed but we can at least avoid conversion every time.

Current coverage is 58.11% (diff: 83.33%)

Merging #938 into master will decrease coverage by 6.81%

@@             master       #938   diff @@
==========================================
  Files           753        753
  Lines         35468      35462      -6
  Methods           0          0
  Messages          0          0
  Branches       5290       5289      -1
==========================================
- Hits          23028      20608   -2420
- Misses        10949      13425   +2476
+ Partials       1491       1429     -62

Powered by Codecov. Last update 19ae3ed...191385b

Is the test coverage dropping down from ~64% to ~58% because of changes in this PR or something unrelated? If former, may be we should address it before merging this PR. If latter, would be great to understand what is going on.

That's because of build failure. Coverage numbers are usually messed up if
the build fails.
On Mon, Jan 9, 2017 at 5:10 PM, Mayank Shrivastava<EMAIL_ADDRESS>
wrote:

Is the test coverage dropping down from ~64% to ~58% because of changes in
this PR or something unrelated? If former, may be we should address it
before merging this PR. If latter, would be great to understand what is
going on.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/linkedin/pinot/pull/938#issuecomment-271457802, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABAmRtTPCGxHxLdQcm7rP4Yn38puMc1Zks5rQtqTgaJpZM4LdRPs
.


Some suggestions

Image Generation

Leonardo AI (Proprietary, Sign Up, Paid, Free Limited daily generations)
https://app.leonardo.ai/

ControlNet (Open Source, Apache 2, Free)
Let's put your character, in the correct position.
https://github.com/lllyasviel/ControlNet-v1-1-nightly
Don't know how to draw that animated sprite?

MPT-7B-StoryWriter-65k+ (Open Source, Apache-2.0, Free)
https://huggingface.co/mosaicml/mpt-7b-storywriter

Claude 100k (Proprietary, Paid, API access, Waitlisted)
https://huggingface.co/mosaicml/mpt-7b-storywriter

GTP-4 32k (Proprietary, Paid, API access, Waitlisted)
https://platform.openai.com/docs/models/overview

Ok no problem I'm making it. Thanks for you suggestions 🤗

✅


GraphQLError with property field in v0.8.2

With v0.8.2 (due to https://github.com/strawberry-graphql/strawberry-graphql-django/commit/d2ad144f51a3fd66228655ee2ae9b2718b78e377, added via https://github.com/strawberry-graphql/strawberry-graphql-django/pull/214) I am seeing an error with a field that is a property on the model:

GraphQLError("Field 'fooProp' argument 'pk' of type 'ID!' is required, but it was not provided.")

@django_type(models.Bar, filters=BarFilter, pagination=True)
class Bar:
    foo_prop: Foo | None = field(
        only=["foo__status"],
    )

/cc @benjaminderei @stygmate

Hey @blueyed . Based on the fact that you are passing only=["foo__status"], you are probably using strawberry_django_plus, correctly? If so, does the same issue happen if you use the type decorator and the field from strawberry_django_plus?

Based on the fact that you are passing only=["foo__status"], you are probably using strawberry_django_plus, correctly?

Yes.

If so, does the same issue happen if you use the type decorator and the field from strawberry_django_plus?

Yes.
Both when using strawberry_django.type on the class, and strawberry_django.field for the field (without only then).
(btw, it reminded me of https://github.com/blb-ventures/strawberry-django-plus/issues/55 btw, where the error is the same)

@blueyed do you have a minimal reproducible example so that I can use to try to understand what might be causing the issue?

0.8.2 caused a similar issue for me too.
This is a simplified extract of the code
class Foo(models.Model):
    pass

class Bar(models.Model):
    def get_foo(self) -> Foo:
        return Foo.objects.first()

@strawberry.django.type(Bar)
class BarType:
    get_foo: FooType = strawberry.field(name="foo")

@bellini666 does the minimal example work for you?
@illia-v have you found a solution/workaround?
Is there a way to exclude properties / not directly queried fields?

@blueyed I think a workaround was creating a method for the foo field
@strawberry.django.type(Bar)
class BarType:
    @strawberry.field
    def foo(self, root: Bar) -> FooType:
        return root.get_foo()

@blueyed @illia-v yes, defining a method resolver should work! Regarding the example, it would not work because get_foo is a function and not a property. If it was written like this it should work:
class Foo(models.Model):
    pass

class Bar(models.Model):
    @property
    def get_foo(self) -> Foo:
        return Foo.objects.first()

@strawberry.django.type(Bar)
class BarType:
    get_foo: FooType = strawberry.field(name="foo")

@bellini666 it does work if get_foo is a function, the breaking change of 0.8.2 was that it stopped working when get_foo was a function returning a model object. It started failing with that argument 'pk' of type 'ID!' is required error.

Oh sorry, I totally missed the previous messages (it is being a while).
Will try to take a look at the minimal reproduction example soon to try to fix it.

Hey @illia-v @blueyed , sorry for taking so long to take a look at this.
Just opened a PR that should fix this issue.

@bellini666 thank you! I can confirm that it fixes this issue.