Update WQ to handle PhEDExNodeNames; fixed remote read

Fixes 2 things.

My last fix for DQMHarvest :(, since I followed the SE convention instead of PNNs
setting to read data remotely would fail since updating a set with string will break the string down in chars and update the set with each elements

Do NOT merge yet please, needs further test.

Beginning pylint and unit tests.
See https://cmssdt.cern.ch/jenkins/job/DMWM-PR-test/862/ for details

Summary of pylint changes for pull request 6331:
Abbreviated pylint report for src/python/WMCore/WorkQueue/WorkQueue.py follows:

Line 335 in WorkQueue.getWork W0612 Unused variable '_'
Line 727 in WorkQueue.pullWork W0613 Unused argument 'continuousReplication'
Line 752 in WorkQueue.pullWork W0612 Unused variable '_'
plus 14 total warnings
plus 37 comments on code style

Unit test changes for pull request 6331:

WMComponent_t.DBS3Buffer_t.DBSBufferFile_t.DBSBufferFileTest:testAddCKSumByLFN was added. Status is success
WMComponent_t.DBS3Buffer_t.DBSBufferFile_t.DBSBufferFileTest:testAddChild was added. Status is success
WMComponent_t.DBS3Buffer_t.DBSBufferFile_t.DBSBufferFileTest:testAddChildTransaction was added. Status is success
WMComponent_t.DBS3Buffer_t.DBSBufferFile_t.DBSBufferFileTest:testAddParents was added. Status is success
WMComponent_t.DBS3Buffer_t.DBSBufferFile_t.DBSBufferFileTest:testAddRunSet was added. Status is success
WMComponent_t.DBS3Buffer_t.DBSBufferFile_t.DBSBufferFileTest:testBulkLoad was added. Status is success
WMComponent_t.DBS3Buffer_t.DBSBufferFile_t.DBSBufferFileTest:testCountFilesDAO was added. Status is success
WMComponent_t.DBS3Buffer_t.DBSBufferFile_t.DBSBufferFileTest:testCreateDeleteExists was added. Status is success
WMComponent_t.DBS3Buffer_t.DBSBufferFile_t.DBSBufferFileTest:testCreateTransaction was added. Status is success
WMComponent_t.DBS3Buffer_t.DBSBufferFile_t.DBSBufferFileTest:testDeleteTransaction was added. Status is success
WMComponent_t.DBS3Buffer_t.DBSBufferFile_t.DBSBufferFileTest:testGetChildrenDAO was added. Status is success
WMComponent_t.DBS3Buffer_t.DBSBufferFile_t.DBSBufferFileTest:testGetParentLFNs was added. Status is success
WMComponent_t.DBS3Buffer_t.DBSBufferFile_t.DBSBufferFileTest:testGetParentStatusDAO was added. Status is success
WMComponent_t.DBS3Buffer_t.DBSBufferFile_t.DBSBufferFileTest:testLoad was added. Status is success
WMComponent_t.DBS3Buffer_t.DBSBufferFile_t.DBSBufferFileTest:testLocationsConstructor was added. Status is success
WMComponent_t.DBS3Buffer_t.DBSBufferFile_t.DBSBufferFileTest:testProperties was added. Status is success
WMComponent_t.DBS3Buffer_t.DBSBufferFile_t.DBSBufferFileTest:testSetBlock was added. Status is success
WMComponent_t.DBS3Buffer_t.DBSBufferFile_t.DBSBufferFileTest:testSetLocation was added. Status is success
WMComponent_t.DBS3Buffer_t.DBSBufferFile_t.DBSBufferFileTest:testSetLocationByLFN was added. Status is success
WMComponent_t.DBS3Buffer_t.DBSBufferFile_t.DBSBufferFileTest:testSetLocationTransaction was added. Status is success
WMComponent_t.DBS3Buffer_t.DBSUpload_t.DBSUploadTest:testCloseSettingsPerWorkflow was added. Status is success
WMComponent_t.ErrorHandler_t.ErrorHandler_t.ErrorHandlerTest:testA_Create changed from error to success
WMComponent_t.ErrorHandler_t.ErrorHandler_t.ErrorHandlerTest:testB_Submit changed from error to success
WMComponent_t.ErrorHandler_t.ErrorHandler_t.ErrorHandlerTest:testC_Jobs changed from error to success
WMComponent_t.ErrorHandler_t.ErrorHandler_t.ErrorHandlerTest:testD_Exhausted changed from error to success
WMComponent_t.ErrorHandler_t.ErrorHandler_t.ErrorHandlerTest:testE_FailJobs changed from error to success
WMComponent_t.JobAccountant_t.JobAccountant_t.JobAccountantTest:testBadFWJR changed from error to success
WMComponent_t.JobAccountant_t.JobAccountant_t.JobAccountantTest:testDBRollback changed from error to success
WMComponent_t.JobAccountant_t.JobAccountant_t.JobAccountantTest:testEmptyFWJR changed from error to success
WMComponent_t.JobAccountant_t.JobAccountant_t.JobAccountantTest:testFailedJob changed from error to success
WMComponent_t.JobAccountant_t.JobAccountant_t.JobAccountantTest:testMergeSuccess changed from error to success
WMComponent_t.JobAccountant_t.JobAccountant_t.JobAccountantTest:testMergeSuccessNoLumi changed from error to success
WMComponent_t.JobAccountant_t.JobAccountant_t.JobAccountantTest:testMergeSuccessSkippedFiles changed from error to success
WMComponent_t.JobAccountant_t.JobAccountant_t.JobAccountantTest:testMergedSkim changed from error to success
WMComponent_t.JobAccountant_t.JobAccountant_t.JobAccountantTest:testNoFileReport changed from error to success
WMComponent_t.JobAccountant_t.JobAccountant_t.JobAccountantTest:testParentlessMergeSuccess changed from error to success
WMComponent_t.JobAccountant_t.JobAccountant_t.JobAccountantTest:testReportReturn changed from error to success
WMComponent_t.JobAccountant_t.JobAccountant_t.JobAccountantTest:testSplitJobs changed from error to success
WMComponent_t.JobAccountant_t.JobAccountant_t.JobAccountantTest:testZ1_BigHeritage changed from error to success
WMComponent_t.JobCreator_t.JobCreator_t.JobCreatorTest:testA_VerySimpleTest changed from error to success
WMComponent_t.JobCreator_t.JobCreator_t.JobCreatorTest:testC_ProfileWorker changed from error to success
WMComponent_t.JobCreator_t.JobCreator_t.JobCreatorTest:testD_HugeTest changed from error to success
WMComponent_t.JobCreator_t.JobCreator_t.JobCreatorTest:testE_TestNonProxySplitting changed from error to success
WMComponent_t.JobSubmitter_t.JobSubmitterCaching_t.JobSubmitterCachingTest:testCaching changed from error to success
WMComponent_t.JobSubmitter_t.JobSubmitter_t.JobSubmitterTest:testA_BasicTest changed from error to success
WMComponent_t.JobSubmitter_t.JobSubmitter_t.JobSubmitterTest:testB_thresholdTest changed from error to success
WMComponent_t.JobSubmitter_t.JobSubmitter_t.JobSubmitterTest:testC_prioritization changed from error to success
WMComponent_t.JobSubmitter_t.JobSubmitter_t.JobSubmitterTest:testD_WhiteListBlackList changed from error to failure
WMComponent_t.JobSubmitter_t.JobSubmitter_t.JobSubmitterTest:testE_SiteModesTest changed from error to success
WMComponent_t.JobTracker_t.JobTracker_t.JobTrackerTest:testAlerts changed from error to success
WMComponent_t.PhEDExInjector_t.PhEDExInjectorPoller_t.PhEDExInjectorPollerTest:test_CustodialSiteA was added. Status is success
WMComponent_t.PhEDExInjector_t.PhEDExInjectorSubscriber_t.PhEDExInjectorSubscriberTest:testNormalModeSubscriptions was added. Status is failure
WMCore_t.BossAir_t.ARCPlugin_t.ARCPluginTest:testG_monitoringDAO changed from error to success
WMCore_t.BossAir_t.ARCPlugin_t.BossAirTest:testG_monitoringDAO changed from error to success
WMCore_t.BossAir_t.ARCTest_t.ARCTest:testG_monitoringDAO changed from error to success
WMCore_t.BossAir_t.ARCTest_t.BossAirTest:testG_monitoringDAO changed from error to success
WMCore_t.BossAir_t.BossAir_t.BossAirTest:testG_monitoringDAO changed from error to success
WMCore_t.BossAir_t.CondorPlugin_t.BossAirTest:testG_monitoringDAO changed from error to success
WMCore_t.BossAir_t.CondorPlugin_t.CondorPluginTest:testG_monitoringDAO changed from error to success
WMCore_t.BossAir_t.PyCondorPlugin_t.BossAirTest:testG_monitoringDAO changed from error to success
WMCore_t.BossAir_t.PyCondorPlugin_t.PyCondorPluginTest:testG_monitoringDAO changed from error to success
WMCore_t.BossAir_t.RunJob_t.RunJobTest:testA_BulkDAOs changed from error to success
WMCore_t.BossAir_t.RunJob_t.RunJobTest:testB_CheckWMBSBuild changed from error to success
WMCore_t.BossAir_t.RunJob_t.RunJobTest:testC_CheckWMBSBuildRoleAndGroup changed from error to success
WMCore_t.BossAir_t.VanillaCondorPlugin_t.BossAirTest:testG_monitoringDAO changed from error to success
WMCore_t.BossAir_t.VanillaCondorPlugin_t.VanillaCondorPluginTest:testG_monitoringDAO changed from error to success
WMCore_t.BossAir_t.gLitePlugin_t.BossAirTest:testG_monitoringDAO changed from error to success
WMCore_t.BossAir_t.gLitePlugin_t.gLitePluginTest:testG_monitoringDAO changed from error to success
WMCore_t.FwkJobReport_t.ReportIntegration_t.ReportIntegrationTest:testReportHandling changed from error to failure
WMCore_t.JobStateMachine_t.ChangeState_t.TestChangeState:testDuplicateJobReports changed from error to success
WMCore_t.JobStateMachine_t.ChangeState_t.TestChangeState:testFWJRInputFileTruncation changed from error to success
WMCore_t.JobStateMachine_t.ChangeState_t.TestChangeState:testIndexConflict changed from error to success
WMCore_t.JobStateMachine_t.ChangeState_t.TestChangeState:testJobKilling changed from error to success
WMCore_t.JobStateMachine_t.ChangeState_t.TestChangeState:testJobSerialization changed from error to success
WMCore_t.JobStateMachine_t.ChangeState_t.TestChangeState:testJobSummary changed from error to success
WMCore_t.JobStateMachine_t.ChangeState_t.TestChangeState:testPersist changed from error to success
WMCore_t.JobStateMachine_t.ChangeState_t.TestChangeState:testRecordInCouch changed from error to success
WMCore_t.JobStateMachine_t.ChangeState_t.TestChangeState:testRetryCount changed from error to success
WMCore_t.JobStateMachine_t.ChangeState_t.TestChangeState:testUpdateFailedDoc changed from error to success
WMCore_t.JobStateMachine_t.ChangeState_t.TestChangeState:testUpdateLocation changed from error to success
WMCore_t.ResourceControl_t.ResourceControl_t.ResourceControlTest:testInsertAllSEs changed from failure to success
WMCore_t.ResourceControl_t.ResourceControl_t.ResourceControlTest:testInsertAllSEs2 changed from failure to success
WMCore_t.ResourceControl_t.ResourceControl_t.ResourceControlTest:testInsertT0 changed from failure to success
WMCore_t.ResourceControl_t.ResourceControl_t.ResourceControlTest:testListSiteInfo changed from error to success
WMCore_t.Services_t.DBS_t.DBSReader_t.DBSReaderTest:testListBlockParents changed from error to success
WMCore_t.Services_t.EmulatorSwitch_t.EmulatorSwitch_t:testGetEmulators changed from failure to success
WMCore_t.Services_t.Service_t.ServiceTest:testBadStatusLine changed from error to success
WMCore_t.Services_t.Service_t.ServiceTest:testCacheDuration changed from error to success
WMCore_t.Services_t.Service_t.ServiceTest:testCacheFileName changed from error to success
WMCore_t.Services_t.Service_t.ServiceTest:testCachePath changed from error to success
WMCore_t.Services_t.Service_t.ServiceTest:testCachePermissions changed from error to success
WMCore_t.Services_t.Service_t.ServiceTest:testClear changed from error to success
WMCore_t.Services_t.Service_t.ServiceTest:testClearAndRepopulate changed from error to success
WMCore_t.Services_t.Service_t.ServiceTest:testNoCache changed from error to success
WMCore_t.Services_t.Service_t.ServiceTest:testNoCacheDuration changed from error to success
WMCore_t.Services_t.Service_t.ServiceTest:testSocketTimeout changed from error to success
WMCore_t.WMBS_t.File_t.FileTest:testAddChecksumsByLFN changed from error to success
WMCore_t.WMBS_t.File_t.FileTest:testAddChild changed from error to success
WMCore_t.WMBS_t.File_t.FileTest:testAddChildTransaction changed from error to success
WMCore_t.WMBS_t.File_t.FileTest:testAddDupsToFileset changed from error to success
WMCore_t.WMBS_t.File_t.FileTest:testAddDupsToFilesetBulk changed from error to success
WMCore_t.WMBS_t.File_t.FileTest:testAddRunSet changed from error to success
WMCore_t.WMBS_t.File_t.FileTest:testAddToFileset changed from error to success
WMCore_t.WMBS_t.File_t.FileTest:testBulkParentage changed from error to success
WMCore_t.WMBS_t.File_t.FileTest:testCreateDeleteExists changed from error to success
WMCore_t.WMBS_t.File_t.FileTest:testCreateTransaction changed from error to success
WMCore_t.WMBS_t.File_t.FileTest:testCreateWithLocation changed from error to success
WMCore_t.WMBS_t.File_t.FileTest:testCreateWithParent changed from error to success
WMCore_t.WMBS_t.File_t.FileTest:testDataStructsFile changed from error to success
WMCore_t.WMBS_t.File_t.FileTest:testDeleteTransaction changed from error to success
WMCore_t.WMBS_t.File_t.FileTest:testGetAncestorLFNs changed from error to success
WMCore_t.WMBS_t.File_t.FileTest:testGetBulkLocations changed from error to success
WMCore_t.WMBS_t.File_t.FileTest:testGetInfo changed from error to success
WMCore_t.WMBS_t.File_t.FileTest:testGetParentLFNs changed from error to success
WMCore_t.WMBS_t.File_t.FileTest:testLoad changed from error to success
WMCore_t.WMBS_t.File_t.FileTest:testLoadData changed from error to success
WMCore_t.WMBS_t.File_t.FileTest:testLocationsConstructor changed from error to success
WMCore_t.WMBS_t.File_t.FileTest:testParentageByJob changed from error to success
WMCore_t.WMBS_t.File_t.FileTest:testParentageByMergeJob changed from error to failure
WMCore_t.WMBS_t.File_t.FileTest:testSetLocation changed from error to success
WMCore_t.WMBS_t.File_t.FileTest:testSetLocationByLFN changed from error to success
WMCore_t.WMBS_t.File_t.FileTest:testSetLocationOrder changed from error to success
WMCore_t.WMBS_t.File_t.FileTest:testSetLocationTransaction changed from error to success
WMCore_t.WMBS_t.File_t.FileTest:test_SetLocationsForWorkQueue changed from error to success
WMCore_t.WMBS_t.Fileset_t.FilesetTest:testAddBulkByLFN changed from error to success
WMCore_t.WMBS_t.Fileset_t.FilesetTest:testAddToWMBSInBulk changed from error to success
WMCore_t.WMBS_t.Fileset_t.FilesetTest:testBulkAddDAO changed from error to success
WMCore_t.WMBS_t.Fileset_t.FilesetTest:testCreateDeleteExists changed from error to success
WMCore_t.WMBS_t.Fileset_t.FilesetTest:testCreateTransaction changed from error to success
WMCore_t.WMBS_t.Fileset_t.FilesetTest:testDeleteTransaction changed from error to success
WMCore_t.WMBS_t.Fileset_t.FilesetTest:testFileCreate changed from error to success
WMCore_t.WMBS_t.Fileset_t.FilesetTest:testFileCreateTransaction changed from error to success
WMCore_t.WMBS_t.Fileset_t.FilesetTest:testFilesetClosing changed from error to success
WMCore_t.WMBS_t.Fileset_t.FilesetTest:testFilesetClosing2 changed from error to success
WMCore_t.WMBS_t.Fileset_t.FilesetTest:testFilesetClosing3 changed from error to success
WMCore_t.WMBS_t.Fileset_t.FilesetTest:testFilesetClosing4 changed from error to success
WMCore_t.WMBS_t.Fileset_t.FilesetTest:testFilesetClosing5 changed from error to success
WMCore_t.WMBS_t.Fileset_t.FilesetTest:testGetFiles changed from error to success
WMCore_t.WMBS_t.Fileset_t.FilesetTest:testListFilesetByTask changed from error to success
WMCore_t.WMBS_t.Fileset_t.FilesetTest:testLoad changed from error to success
WMCore_t.WMBS_t.Fileset_t.FilesetTest:testLoadData changed from error to success
WMCore_t.WMBS_t.Fileset_t.FilesetTest:testMarkOpen changed from error to success
WMCore_t.WMBS_t.Fileset_t.FilesetTest:testSetLastUpdate changed from error to success
WMCore_t.WMBS_t.JobGroup_t.JobGroupTest:testCommit changed from error to success
WMCore_t.WMBS_t.JobGroup_t.JobGroupTest:testCommitBulk changed from error to success
WMCore_t.WMBS_t.JobGroup_t.JobGroupTest:testCommitTransaction changed from error to success
WMCore_t.WMBS_t.JobGroup_t.JobGroupTest:testCreateDeleteExists changed from error to success
WMCore_t.WMBS_t.JobGroup_t.JobGroupTest:testCreateTransaction changed from error to success
WMCore_t.WMBS_t.JobGroup_t.JobGroupTest:testDeleteTransaction changed from error to success
WMCore_t.WMBS_t.JobGroup_t.JobGroupTest:testGetGroupsByJobStateDAO changed from error to success
WMCore_t.WMBS_t.JobGroup_t.JobGroupTest:testGetLocationsForJobs changed from error to success
WMCore_t.WMBS_t.JobGroup_t.JobGroupTest:testLoad changed from error to success
WMCore_t.WMBS_t.JobGroup_t.JobGroupTest:testLoadData changed from error to success
WMCore_t.WMBS_t.JobGroup_t.JobGroupTest:testSetGetSite changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.EventAwareLumiBased_t.EventAwareLumiBasedTest:testA_FileSplitNoHardLimit changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.EventAwareLumiBased_t.EventAwareLumiBasedTest:testB_NoFileSplitNoHardLimit changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.EventAwareLumiBased_t.EventAwareLumiBasedTest:testC_HardLimitSplitting changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.EventAwareLumiBased_t.EventAwareLumiBasedTest:testD_HardLimitSplittingOnly changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.EventBased_t.EventBasedTest:test100EventMultipleFileSplit changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.EventBased_t.EventBasedTest:test100EventMultipleSite changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.EventBased_t.EventBasedTest:test150EventMultipleFileSplit changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.EventBased_t.EventBasedTest:test50EventMultipleFileSplit changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.EventBased_t.EventBasedTest:test50EventSplit changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.EventBased_t.EventBasedTest:test99EventSplit changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.EventBased_t.EventBasedTest:testExactEvents changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.EventBased_t.EventBasedTest:testMCEventSplitOver32bit changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.EventBased_t.EventBasedTest:testMoreEvents changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.EventBased_t.EventBasedTest:test_addParents changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.FileBased_t.FileBasedTest:test2FileSplit changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.FileBased_t.FileBasedTest:test3FileSplit changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.FileBased_t.FileBasedTest:testExactFiles changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.FileBased_t.FileBasedTest:testLimit changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.FileBased_t.FileBasedTest:testLocationSplit changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.FileBased_t.FileBasedTest:testMoreFiles changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.FileBased_t.FileBasedTest:testRespectRunBoundaries changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.FileBased_t.FileBasedTest:testZ_randomCrapForGenerators changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.FileBased_t.FileBasedTest:test_getParents changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.FixedDelay_t.FixedDelayTest:testAllAcquired changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.FixedDelay_t.FixedDelayTest:testClosed changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.FixedDelay_t.FixedDelayTest:testClosedSomeAcquired changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.FixedDelay_t.FixedDelayTest:testNone changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.LumiBased_t.LumiBasedTest:testA_FileSplitting changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.LumiBased_t.LumiBasedTest:testB_NoRunNoFileSplitting changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.LumiBased_t.LumiBasedTest:testC_ACDCTest changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.LumiBased_t.LumiBasedTest:testD_NonContinuousLumis changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.LumiBased_t.LumiBasedTest:testE_getParents changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.LumiBased_t.LumiBasedTest:testF_RunWhitelist changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.MinFileBased_t.FileBasedTest:testA_ExactFiles changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.MinFileBased_t.FileBasedTest:testB_LessFilesOpen changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.MinFileBased_t.FileBasedTest:testC_LessFilesClosed changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.MinFileBased_t.FileBasedTest:testD_MoreFilesOpen changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.MinFileBased_t.FileBasedTest:testE_MoreFilesClosed changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.ParentlessMergeBySize_t.ParentlessMergeBySizeTest:testDifferentSubscritionIDs changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.ParentlessMergeBySize_t.ParentlessMergeBySizeTest:testLocationMerging changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.ParentlessMergeBySize_t.ParentlessMergeBySizeTest:testMaxEvents changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.ParentlessMergeBySize_t.ParentlessMergeBySizeTest:testMaxEventsNoRunMerge changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.ParentlessMergeBySize_t.ParentlessMergeBySizeTest:testMaxMergeSize changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.ParentlessMergeBySize_t.ParentlessMergeBySizeTest:testMaxMergeSizeNoRunMerge changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.ParentlessMergeBySize_t.ParentlessMergeBySizeTest:testMaxWaitTime changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.ParentlessMergeBySize_t.ParentlessMergeBySizeTest:testMinMergeSize1 changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.ParentlessMergeBySize_t.ParentlessMergeBySizeTest:testMinMergeSize1a changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.ParentlessMergeBySize_t.ParentlessMergeBySizeTest:testMinMergeSize1aNoRunMerge changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.RunBased_t.EventBasedTest:testExactRuns changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.RunBased_t.EventBasedTest:testMoreRuns changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.RunBased_t.EventBasedTest:testMultipleRuns changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.RunBased_t.EventBasedTest:testMultipleRunsCombine changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.RunBased_t.EventBasedTest:testPersistSingleRunsCombineUneven changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.RunBased_t.EventBasedTest:testSingleRunsCombineUneven changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.RunBased_t.EventBasedTest:testSingleRunsMultipleLumiCombineUneven changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.SiblingProcessingBased_t.SiblingProcessingBasedTest:testFilesWithoutOtherSubscriptions changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.SiblingProcessingBased_t.SiblingProcessingBasedTest:testLargeNumberOfFiles changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.SiblingProcessingBased_t.SiblingProcessingBasedTest:testMultipleLocations changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.SiblingProcessingBased_t.SiblingProcessingBasedTest:testSiblingProcessing changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.SizeBased_t.SizeBasedTest:testExactEvents changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.SizeBased_t.SizeBasedTest:testMultipleFiles changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.SizeBased_t.SizeBasedTest:testMultipleFiles2000 changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.SizeBased_t.SizeBasedTest:testMultipleFiles2500 changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.SizeBased_t.SizeBasedTest:testMultipleFiles500 changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.SizeBased_t.SizeBasedTest:testMultipleSites changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.SplitFileBased_t.SplitFileBasedTest:testSplitAlgo changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.WMBSMergeBySize_t.WMBSMergeBySize:testFilesetCloseout changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.WMBSMergeBySize_t.WMBSMergeBySize:testFilesetCloseout2 changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.WMBSMergeBySize_t.WMBSMergeBySize:testForcedMerge changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.WMBSMergeBySize_t.WMBSMergeBySize:testLocationMerging changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.WMBSMergeBySize_t.WMBSMergeBySize:testMaxEvents1 changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.WMBSMergeBySize_t.WMBSMergeBySize:testMaxEvents2 changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.WMBSMergeBySize_t.WMBSMergeBySize:testMaxMergeSize1 changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.WMBSMergeBySize_t.WMBSMergeBySize:testMaxMergeSize2 changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.WMBSMergeBySize_t.WMBSMergeBySize:testMinMergeSize1 changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.WMBSMergeBySize_t.WMBSMergeBySize:testMinMergeSize1a changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.WMBSMergeBySize_t.WMBSMergeBySize:testMinMergeSize2 changed from error to success
WMCore_t.WMBS_t.JobSplitting_t.WMBSMergeBySize_t.WMBSMergeBySize:testParallelProcessing changed from error to success
WMCore_t.WMBS_t.Job_t.JobTest:testCompleteJobInput changed from error to success
WMCore_t.WMBS_t.Job_t.JobTest:testCreateDeleteExists changed from error to success
WMCore_t.WMBS_t.Job_t.JobTest:testCreateDeleteExistsNoFiles changed from error to success
WMCore_t.WMBS_t.Job_t.JobTest:testCreateTransaction changed from error to success
WMCore_t.WMBS_t.Job_t.JobTest:testDeleteTransaction changed from error to success
WMCore_t.WMBS_t.Job_t.JobTest:testFailJobInput changed from error to success
WMCore_t.WMBS_t.Job_t.JobTest:testGetDataStructsJob changed from error to success
WMCore_t.WMBS_t.Job_t.JobTest:testGetFiles changed from error to success
WMCore_t.WMBS_t.Job_t.JobTest:testGetOutputMapDAO changed from error to success
WMCore_t.WMBS_t.Job_t.JobTest:testGetOutputParentLFNs changed from error to success
WMCore_t.WMBS_t.Job_t.JobTest:testJobCacheDir changed from error to success
WMCore_t.WMBS_t.Job_t.JobTest:testJobFWJRPath changed from error to success
WMCore_t.WMBS_t.Job_t.JobTest:testJobState changed from error to success
WMCore_t.WMBS_t.Job_t.JobTest:testJobTypeDAO changed from error to success
WMCore_t.WMBS_t.Job_t.JobTest:testJobTypeDAOBulk changed from error to success
WMCore_t.WMBS_t.Job_t.JobTest:testLoad changed from error to success
WMCore_t.WMBS_t.Job_t.JobTest:testLoadData changed from error to success
WMCore_t.WMBS_t.Job_t.JobTest:testLoadForTaskArchiver changed from error to success
WMCore_t.WMBS_t.Job_t.JobTest:testLoadOutputID changed from error to success
WMCore_t.WMBS_t.Job_t.JobTest:testLocations changed from error to success
WMCore_t.WMBS_t.Job_t.JobTest:testMask changed from error to success
WMCore_t.WMBS_t.Job_t.JobTest:testSaveTransaction changed from error to success
WMCore_t.WMBS_t.Job_t.JobTest:test_AutoIncrementCheck changed from error to success
WMCore_t.WMBS_t.Locations_t.LocationsTest:testDrain changed from error to success
WMCore_t.WMBS_t.Locations_t.LocationsTest:testGetSiteInfo changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testAcquireFiles changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testAcquireFilesTransaction changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testAvailableFiles changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testAvailableFilesMeta changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testAvailableFilesTransaction changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testBulkCommit changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testCompleteFiles changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testCompleteFilesTransaction changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testCreateDeleteExists changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testCreateTransaction changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testDeleteEverything changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testDeleteTransaction changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testFailFiles changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testFailFilesTransaction changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testFilesOfStatusByLimit changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testGetJobGroups changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testGetNumberOfJobsPerSite changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testGetSubTypes changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testIsFileCompleted changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testJobs changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testListIncompleteDAO changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testLoad changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testLoadData changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testMarkNewFinishedSubscriptions changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testMarkNewFinishedSubscriptionsParentage changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testMarkNewFinishedSubscriptionsTimeout changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testSubTypesInsertion changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testSubscriptionCompleteStatusByRun changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testSubscriptionList changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testSucceededJobs changed from error to success
WMCore_t.WMBS_t.Subscription_t.SubscriptionTest:testWhitelistBlacklist changed from error to success
WMCore_t.WMLogging_t.WMLoggingTest:testLog changed from error to success
WMCore_t.WMSpec_t.StdSpecs_t.DQMHarvest_t.DQMHarvestTests:testDQMHarvest changed from failure to success
WMCore_t.WMSpec_t.StdSpecs_t.MonteCarloFromGEN_t.MonteCarloFromGENTest:testMCFromGENWithPileup changed from error to success
WMCore_t.WMSpec_t.StdSpecs_t.MonteCarloFromGEN_t.MonteCarloFromGENTest:testMonteCarloFromGEN changed from error to success
WMCore_t.WMSpec_t.StdSpecs_t.MonteCarlo_t.MonteCarloTest:testMCWithLHE changed from error to success
WMCore_t.WMSpec_t.StdSpecs_t.MonteCarlo_t.MonteCarloTest:testMCWithPileup changed from error to success
WMCore_t.WMSpec_t.StdSpecs_t.TaskChain_t.TaskChainTests:testPileupTaskChain changed from error to success
WMCore_t.WMSpec_t.WMTask_t.WMTaskTest:testSubscriptionInformation changed from failure to success
WMCore_t.WebTools_t.RESTFormat_t.RESTFormatTest:testGenerator changed from failure to success
WMCore_t.WorkQueue_t.Policy_t.Start_t.Block_t.BlockTestCase:testContinuousSplittingSupport changed from failure to success
WMCore_t.WorkQueue_t.Policy_t.Start_t.Block_t.BlockTestCase:testDataDirectiveFromQueue changed from error to success
WMCore_t.WorkQueue_t.Policy_t.Start_t.Block_t.BlockTestCase:testDatasetLocation changed from failure to success
WMCore_t.WorkQueue_t.Policy_t.Start_t.Block_t.BlockTestCase:testMultiTaskProcessingWorkload changed from failure to success
WMCore_t.WorkQueue_t.Policy_t.Start_t.Block_t.BlockTestCase:testWhiteBlackLists changed from failure to success
WMCore_t.WorkQueue_t.Policy_t.Start_t.Dataset_t.DatasetTestCase:testMultiTaskProcessingWorkload changed from success to failure
WMCore_t.WorkQueue_t.Policy_t.Start_t.Dataset_t.DatasetTestCase:testParentProcessing changed from success to failure
WMCore_t.WorkQueue_t.Policy_t.Start_t.Dataset_t.DatasetTestCase:testTier1ReRecoWorkload changed from success to failure
WMCore_t.WorkQueue_t.Policy_t.Start_t.Dataset_t.DatasetTestCase:testWhiteBlackLists changed from success to failure
WMCore_t.WorkQueue_t.WMBSHelper_t.WMBSHelperTest:testCreateSubscription changed from error to success
WMCore_t.WorkQueue_t.WMBSHelper_t.WMBSHelperTest:testKillWorkflow changed from error to success
WMCore_t.WorkQueue_t.WMBSHelper_t.WMBSHelperTest:testTruncatedWFInsertion changed from error to success
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:test0eventBlock changed from error to failure
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testBlackList changed from error to failure
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testCancelWork changed from error to failure
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testCancelWorkGlobal changed from error to failure
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testCloseWorkOpenBlocks changed from error to failure
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testCloseWorkTimeout changed from error to success
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testConflicts changed from error to failure
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testDeleteWork changed from error to failure
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testDrainMode changed from error to success
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testEndPolicyNegotiating changed from error to failure
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testFailRequestAfterTimeout changed from error to success
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testGlobalBlockSplitting changed from error to failure
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testGlobalDatasetSplitting changed from error to failure
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testIgnoreDuplicates changed from error to success
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testInvalidSpecs changed from error to success
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testMultiTaskProduction changed from error to success
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testMultipleTeams changed from error to failure
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testOpenBlocks changed from error to failure
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testParentProcessing changed from error to failure
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testPileupOnProduction changed from error to success
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testPrioritiesWorkPolling changed from error to failure
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testPriority changed from error to success
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testProcessing changed from error to failure
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testProcessingWithContinuousSplitting changed from error to failure
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testProcessingWithPileup changed from error to failure
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testProduction changed from error to success
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testProductionMultiQueue changed from error to failure
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testQueueChaining changed from error to failure
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testQueueChainingStatusUpdates changed from error to failure
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testResetWork changed from error to failure
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testResubmissionWithParentsWorkflow changed from error to success
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testResubmissionWorkflow changed from error to failure
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testResubmissionWorkflowSiteWhitelistLocations changed from error to failure
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testSiteStatus changed from error to failure
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testSitesFromResourceControl changed from error to failure
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testSplittingLargeInputs changed from error to failure
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testTeams changed from error to failure
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testThrottling changed from error to failure
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testWMBSInjectionStatus changed from error to failure

Previously working unit tests have failed!

test this please

Beginning pylint and unit tests.
See https://cmssdt.cern.ch/jenkins/job/DMWM-PR-test/866/ for details

Beginning pylint and unit tests.
See https://cmssdt.cern.ch/jenkins/job/DMWM-PR-test/867/ for details

Summary of pylint changes for pull request 6331:
Abbreviated pylint report for src/python/WMCore/WorkQueue/WorkQueue.py follows:

Line 335 in WorkQueue.getWork W0612 Unused variable '_'
Line 727 in WorkQueue.pullWork W0613 Unused argument 'continuousReplication'
Line 752 in WorkQueue.pullWork W0612 Unused variable '_'
plus 14 total warnings
plus 37 comments on code style

Unit test changes for pull request 6331:

WMCore_t.WebTools_t.NestedModel_t.NestedModelTest:testInnerPingPass changed from success to failure

Previously working unit tests have failed!

Beginning pylint and unit tests.
See https://cmssdt.cern.ch/jenkins/job/DMWM-PR-test/870/ for details

Summary of pylint changes for pull request 6331:

Score for src/python/WMCore/WorkQueue/DataLocationMapper.py changed from 9.45 to 9.18 with 1 (8) total errors (warnings)

src/python/WMCore/WorkQueue/DataLocationMapper.py got worse in pylint. Report follows:

Line 32 in isGlobalDBS W0703 Catching too general exception Exception
Line 32 in isGlobalDBS W0612 Unused variable 'ex'
Line 73 in DataLocationMapper.call W0102 Dangerous default value {} as argument
Line 126 in DataLocationMapper.locationsFromPhEDEx W0703 Catching too general exception Exception
Line 127 in DataLocationMapper.locationsFromPhEDEx W1201 Specify string format arguments as logging function parameters
Line 99 in DataLocationMapper.locationsFromPhEDEx R0912 Too many branches (15/12)
Line 152 in DataLocationMapper.locationsFromDBS W0703 Catching too general exception Exception
Line 146 in DataLocationMapper.locationsFromDBS E0602 Undefined variable 'dataItem'
Line 153 in DataLocationMapper.locationsFromDBS W1201 Specify string format arguments as logging function parameters
Line 165 in DataLocationMapper.organiseByDbs R0201 Method could be a function
Line 184 in WorkQueueDataLocationMapper.call W0221 Arguments number differs from overridden method
plus 23 comments on code style

Abbreviated pylint report for src/python/WMCore/WorkQueue/WorkQueue.py follows:

Line 335 in WorkQueue.getWork W0612 Unused variable '_'
Line 727 in WorkQueue.pullWork W0613 Unused argument 'continuousReplication'
Line 752 in WorkQueue.pullWork W0612 Unused variable '_'
plus 14 total warnings
plus 37 comments on code style

No changes to unit tests for pull request 6331

The LumiList change should fix the mystery of subscriptions without actual files in WMBS. The problem is that lumiList is a list of lists which then fails to be sorted here
https://github.com/dmwm/WMCore/blob/master/src/python/WMCore/DataStructs/LumiList.py#L87
giving as result an empty compactList, which later on does not match in WMBSHelper..
Let's see whether it breaks any unit tests.

Please don't change lumilist. I think we're using it wrong if it doesn't work as is.

Ok, I reverted the changes in LumiList. It was indeed being initialized in the wrong way. Now instead of passing "lumis" (list of list) we pass a dict with runAndLumis.

Changing globals to fix most of the WMBS unit tests, still some to go, but I mainly want to see whether this change will break other tests or not...

test this please

test this please

Tried to fix a few more unit tests, though it seems Dataset_t is using the old DBSReader (DBS2) emulator, which is completely outdated. I still have to look at the WorkQueue issues, I'm not sure they are related to this change or Seangchan's change.
I'll look at it later in the evening @ticoann if possible wait for me before merging it

"though it seems Dataset_t is using the old DBSReader (DBS2) emulator, " no surprise there. That code is everywhere.

@ticoann just deployed this branch and run the Harvest and JobGroup tests and they ran without any issues. Please review and merge it for the new tag.


Mix and Match is broken

this will crash on
[0] ???
[1] SpineSprite::update_mesh_from_skeleton (C:\Projects\godot\modules\spine_runtime\SpineSprite.cpp:342)
	var hair: SpineSkin = spine_sprite.get_skeleton().get_data().find_skin("hair/brown")
	var at = hair.get_attachments()
	while at.has_next():
		var at1 = at.next()
		print(at1.get_attachment().get_attachment_name())
	spine_sprite.get_skeleton().set_skin(hair)

CustomSkinProject.zip

The code works fine in my godot build. I don't know if this issue is a random bug...

Doesn't crash for me either.

works now


Fix Build Process

As webpack doesn't support node >14 out of the box, a few changes to webpack configurations is necessary.
Furthermore, this extension doesn't compile using vsce package, as dist/web/extension.js isn't built during the execution of vscode:prepublish.
Changes made in this PR will make sure that webpack is using for the most recent node version and add the package-web script to vscode:prepublish in order to make sure, this extension can be compiled simply by invoking vsce package.

Good catch! That's true, I'll go edit this file in a sec.

You're most welcome 😄


Allow recovery of time_taken for jobs on private hubs

What is the expected behavior?
When we run a vqe/qaoa algorithm on a real quantum device assigned to a private hub, we cannot check the time_taken of the jobs on qiskit. The result object can be viewed once and since the results are pulled at the end of each iteration of vqe/qaoa, so we can no longer access to this information. Is it possible to add the time_taken like metadata in the job(job.time_taken) and/or also the global time_taken for these jobs?

See #1243

Is this resolved? @AzizNgoueya  can you close the issue if not needed anymore?


FR: Google/MLKit using SPM

[READ] Guidelines
For large or ambiguous requests, such as significant breaking changes or use
cases that could be addressed by multiple different features, consider instead
starting a
Pitch
discussion for ideas that you'd like to discuss with the Firebase community to
flush out.
When filing a feature request please make sure the issue title starts with "FR:".
A good feature request ideally

is either immediately obvious (i.e. "Add Sign in with Apple support"), or
starts with a use case that is not achievable with the existing Firebase API and
includes an API proposal that would make the use case possible. The proposed API
change does not need to be very specific.

Once you've read this section, please delete it and fill out the rest of the template.
Feature proposal

Firebase Component: _____ (Auth, Core, Database, Firestore, Messaging, Storage, etc)

I believe the FirebaseML/TextRecognition will be now deprecated in favor of GoogleML/TextRecognation - now i am migrating from cocoapods to SPM but i cant see some repo to add it in SPM? any idea? Thanks

Hi @koolfreak, this seems to be a dupe of googlesamples/mlkit#180.

Sorry, MLKit does not provide support for SPM. Please follow up in the MLKit channels. I'm going to close as out of scope for Firebase.


ASIM Authentication Event schema parser with its sample and test data for VMware Carbon Black Cloud

Change(s):

Added ASIM Authentication Event schema parser for VMware Carbon Black Cloud based on API Data

Reason for Change(s):

Initial version ASIM Authentication Event Parser

Version Updated:

Initial version

Testing Completed:

Yes

Checked that the validations are passing and have addressed any issues that are present:

Yes

Hi @jayeshprajapaticrest,
Thank you for raising Pull Request with us! We will review it and get back to you by shortly.

Hi @jayeshprajapaticrest,
There is an error with the sample data and kql validation below. Please resolve it. Please check on branch conflicts as well. Thanks

@v-atulyadav validations are fixed

Hi @jayeshprajapaticrest, could you please provide some updates on @vakohl's comments and also please look into branch conflicts. Thanks

Hi @jayeshprajapaticrest, could you please provide some updates on @vakohl's comments and also please look into branch conflicts. Thanks

@v-atulyadav Conflicts resolved and We will look at the comment by this weekend.

Noted @jayeshprajapaticrest. Thanks

Hi @jayeshprajapaticrest,
To follow up appropriately, we would appreciate some indication of the timeframe for these changes. Thanks

Hi @jayeshprajapaticrest,
We're waiting for an update on this. Thanks

Hi @jayeshprajapaticrest, We're waiting for an update on this. Thanks

@v-atulyadav We have made the suggested changes

Noted @niralishah-crest. Thanks

@vakohl We have made the suggested changes.

@vakohl
We have updated unifying parser file with the filters as suggested by you. We have updated "targetusername_has(String Type)" with the "targetusername_has_any(Dynamic Type)" in unifying parser file. Also used the updated filter in the products developed by us. But the old products has "targetusername_has" filter name and because of that getting validation error as below.
Errors: The name 'targetusername_has' does not refer to any known column

@vakohl We have updated unifying parser file with the filters as suggested by you. We have updated "targetusername_has(String Type)" with the "targetusername_has_any(Dynamic Type)" in unifying parser file. Also used the updated filter in the products developed by us. But the old products has "targetusername_has" filter name and because of that getting validation error as below. Errors: The name 'targetusername_has' does not refer to any known column

@jayeshprajapaticrest Please skip updating union for now.

Hi @jayeshprajapaticrest,
Please find the comments from @vakohl above and also check for errors in KQL validation. Thanks

Hi @jayeshprajapaticrest,
We're waiting for an update on this. Thanks

@vakohl We have updated unifying parser file with the filters as suggested by you. We have updated "targetusername_has(String Type)" with the "targetusername_has_any(Dynamic Type)" in unifying parser file. Also used the updated filter in the products developed by us. But the old products has "targetusername_has" filter name and because of that getting validation error as below. Errors: The name 'targetusername_has' does not refer to any known column

@jayeshprajapaticrest Please skip updating union for now.

If we skip, still we can get the error as we have used "targetusername_has_any" of type dynamic. But previous version has "targetusername_has" of type string.

Hi @jayeshprajapaticrest, please check comments above from @vakohl. Thanks

Hi @jayeshprajapaticrest,
Please work on above comment.
Thanks

Hi @jayeshprajapaticrest, could you please provide some updates on @vakohl's comments. Thanks

Hi @jayeshprajapaticrest,
We're waiting for an update on this. Thanks

@v-atulyadav
We have started working on this PR suggested changes. Will update this by next week.
Thanks

Noted @jayeshprajapaticrest. Thanks

@jayeshprajapaticrest @niralishah-crest we are getting KQL validation error due to new Auth parameters. Can you remove the new changes in imauthentication union parser and only keep the old parameters to avoid the error for now?

@jayeshprajapaticrest @niralishah-crest we are getting KQL validation error due to new Auth parameters. Can you remove the new changes in imauthentication union parser and only keep the old parameters to avoid the error for now?

@jayeshprajapaticrest @niralishah-crest I resolved remaining comments. Can you please fix the validation error?


Fix crashing bugs with JSON serialization

:sparkles: What kind of change does this PR introduce? (Bug fix, feature, docs update...)
Bug fixes
:arrow_heading_down: What is the current behavior?
JSON error thrown during jsonEncode(placemark) if placemark.position.timestamp == null.
ArgumentError thrown during Placemark.fromMap(placemark_map) where placemark_map was created using jsonEncode(placemark).
:new: What is the new behavior (if this is a feature change)?
No errors in the above cases. Proper deserialization of Placemark from map whether or not position is supplied.
:boom: Does this PR introduce a breaking change?
No.
:bug: Recommendations for testing
Using a Placemark without a timestamp, e.g. by using Android 10 in an emulator, call Placemark.fromMap(jsonEncode(placemark))
:memo: Links to relevant issues/docs
n/a
:thinking: Checklist before submitting

[X] All projects build
[X] Follows style guide lines (code style guide)
[-] Relevant documentation was updated
[X] Rebased onto current develop

@bangfalse thanks for contributing and helping out to improve the Geolocator plugin.


Critical vulnerability

From 0.8 release changelog: https://conduit.rs/changelog/
"This release is focused on patching security vulnerabilities. Most notably, there is a CRITICAL vulnerability, which requires an attacker to have an account on your server. Administrators which have untrusted users on their server (e.g. public homeservers) are advised to update immediately or take their homeserver off the internet ASAP."
More info in the changelog.
@ericgaspar  I think this package should be disabled until updated to 0.8.

fixed

I just tried to update and the checksum don't match:
Error: Failed to rollback sources : YunoHost was able to download the asset 'main' (https://gitlab.com/api/v4/projects/famedly%2Fconduit/jobs/artifacts/master/raw/x86_64-unknown-linux-musl?job=artifacts) for conduit, but the asset doesn't match the expected checksum. This could mean that some temporary network failure happened on your server, OR the asset was somehow changed by the upstream maintainer (or a malicious actor?) and YunoHost packagers need to investigate and perhaps update the app manifest to take this change into account.
    Expected sha256 checksum: eafa400feefee2a2117d56a09c891d0c39cbec30520a2422056d7d2dcd00de04
    Downloaded sha256 checksum: ba6825d7108bba124f4dbb39d579a34816d34d635547e898b6e9813ffb04b045
    Downloaded file size: 58M

I just tried to update and the checksum don't match:
Error: Failed to rollback sources : YunoHost was able to download the asset 'main' (https://gitlab.com/api/v4/projects/famedly%2Fconduit/jobs/artifacts/master/raw/x86_64-unknown-linux-musl?job=artifacts) for conduit, but the asset doesn't match the expected checksum. This could mean that some temporary network failure happened on your server, OR the asset was somehow changed by the upstream maintainer (or a malicious actor?) and YunoHost packagers need to investigate and perhaps update the app manifest to take this change into account.
    Expected sha256 checksum: eafa400feefee2a2117d56a09c891d0c39cbec30520a2422056d7d2dcd00de04
    Downloaded sha256 checksum: ba6825d7108bba124f4dbb39d579a34816d34d635547e898b6e9813ffb04b045
    Downloaded file size: 58M

https://github.com/YunoHost-Apps/conduit_ynh/pull/37

I could update, thanks!


updated docs

Status
Ready/In Progress/In Hold (Reason for hold)
Related Issues
fixes: link to the issue
Description
A few sentences describing the overall goals of the pull request's commits.
Screenshots
Paste here any images that will help the reviewer

@michal-dagan Doc review completed.


Messages disappear within federated conversations

When messaging within a conversation with a non-local peer, sometimes images or text messages will no longer be within the senders view. The messages will sometimes show within preview on the main topics page, but will not be present within the conversation body. My non-local peer also had the same issue with a conversation hosted on my server, but I had the full conversation. I haven't checked to see if this occurs within users on the same server, but i'd wager it doesn't.

Could you give me a bit more detail about the issue?

is this happening only with sealed topics or unsealed topics?
is this happening on mobile or browser, or both? will the same message be missing from both?
does this happen to all messages within a topic or just a random individual message?
does restarting the app cause the message to reappear?

Thanks for reporting this, this is obviously a serious issue that I need to resolve. There was a bug recently in the mobile app on some devices where unsealed topic messages would not show up, but that was resolved ~1month ago.

Thank you so much for reporting this!!!! This was a serious issue.
I see the problem and will fix it tonight. It will however take around a week for the apps to be deployed through the app stores.

Pierre,
This is in the mobile app. It looks like the messages are in the mobile app. Admittedly, i am using a slightly older version and need to update. I'm only really messaging one other remote user. I'll update and attempt to replicate this. Also, restarting the app does not cause the message to re-appear.
Sent with Proton Mail secure email.
------- Original Message -------
On Tuesday, August 15th, 2023 at 11:14 PM, Pierre Balzack @.***> wrote:

Could you give me a bit more detail about the issue?

is this happening only with sealed topics or unsealed topics?
is this happening on mobile or browser, or both? will the same message be missing from both?
does this happen to all messages within a topic or just a random individual message?
does restarting the app cause the message to reappear?

Thanks for reporting this, this is obviously a serious issue that I need to resolve. There was a bug recently in the mobile app on some devices where unsealed topic messages would not show up, but that was resolved ~1month ago.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Yes, thank you. I was able to reproduce the issue and fix it for any new messages coming in,
The iOS app has been updated, the fdroid app will be updated in the next few days.
The messages before the fix will still appear missing, but can be recovered by scrolling to the top of the thread and back down.

The fdroid app has now also been updated. If you get a chance, can you see if messages continue to disappear?

I'm upgrading my server later today, and am using the app store version, but I will test.
Sent with Proton Mail secure email.
------- Original Message -------
On Monday, August 21st, 2023 at 1:11 PM, Pierre Balzack @.***> wrote:

The fdroid app has now also been updated. If you get a chance, can you see if messages continue to disappear?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

The app store version was updated as well. Thanks!

I believe this bug has been fixed....thanks again for reporting it.

I can confirm this is resolved.
Sent with Proton Mail secure email.
------- Original Message -------
On Thursday, September 21st, 2023 at 2:15 PM, Pierre Balzack @.***> wrote:

I believe this bug has been fixed....thanks again for reporting it.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


feat(factories): use children in shorthands as render props

⏩ Migration
We decided to go with soft migration, existing API with render callback will be deprecated and will create warnings.
Case 1: wrapping slot
Used when you need to wrap component slot with Popup or Tooltip, for example.
Before
  <Button
    content={render =>
      render({ content: 'Foo', tabIndex: 1 }, (Component, props) => (
        <Popup trigger={<Component {...props} />} />
      ))
    }
  />

After
  <Button
    content={{
      content: 'Foo',
      tabIndex: 1,
      children: (Component, props) => <Popup trigger={<Component {...props} />} />,
    }}
  />

Case 2: wrapping item
Used when you need to wrap the whole item with Popup or Tooltip, for example.
Before
const items = [
  render =>
    render({ content: 'Foo' }, (Component, props) => <Popup trigger={<Component {...props} />} />),
  { content: 'Bar' },
]

<Menu items={items} />

After
const items = [
  { content: 'Foo', children: (Component, props) => <Popup trigger={<Component {...props} />} /> },
  { content: 'Bar' },
]

const MenuExample = () => <Menu items={items} />

Case 3: delayed execution
Is used in async scenarios. We deprecated this use case, see Motivation part. There is only one way to migrate is to lift up state, it works even now.
CodeSandbox with Before & After: https://codesandbox.io/s/stardust-ui-example-23icy
Before
  <Avatar
    image="https://stardust-ui.github.io/react/public/images/avatar/small/matt.jpg"
    status={render => (
      <QueryMock>
        {status => {
          if (status) {
            return render({
              color: "green",
              icon: "stardust-checkmark",
              title: "Available"
            });
          }

          return render({
            color: "grey",
            icon: "sync",
            title: "Loading"
          });
        }}
      </QueryMock>
    )}
  />

After
<QueryMock>
    {status => (
      <Avatar
        image="https://stardust-ui.github.io/react/public/images/avatar/small/matt.jpg"
        status={
          status
            ? {
                color: "green",
                icon: "stardust-checkmark",
                title: "Available"
              }
            : {
                color: "grey",
                icon: "sync",
                title: "Loading"
              }
        }
      />
    )}
  </QueryMock>

⌚ Motivation
Existing API with render callback is very powerful and in the same time is over-complicated: it's hard to explain to people how it works and it's hard to use for frequent use cases.
<Menu
  items={[
    render => // callback 1
      render(    // callback 2
        {
          key: 'editorials',
          content: 'Editorials',
        },
        (Component, props) => <Popup content="Foo" trigger={<Component {...props} />} />,
      ),
  ]}
/>

Other cons

it allows developers to do really strange things with passing render down into React tree:

<Menu
  items={[
    render => <ItemRenderer render={render} />} />
  ]}
/>

the resolution of kind prop is broken:

<Menu
  items={[
    render =>
      render(
        {
          key: 'editorials',
          kind: 'divider',
          content: 'Editorials',
        },
        (Component, props) => <Component /> // renders MenuItem 😭
      ),
  ]}
/>

⭐ Solution
React has well known render props pattern and I suggest to use instead as more friendly option.
I propose to have only one type of usage, via children prop:

it allows to deprecate render callback, otherwise there will be not obvious collision if we will decide to go with deprecation
single option is better than multiple

<Menu
  items={[
    {
      key: 'events',
      content: 'Upcoming Events',
      children: (Component, props) => (
        <Popup content="Popup" trigger={<Component {...props} />} />
      ),
    },
  ]}
/>

It still allows to pass shorthand props.

this looks awesome! Migration would be a bit tricky for the consumers though, let'see how we can handle that.

passing the render down the tree, even though strange, was used for a reason - if the shorthand props are resolved asynchronously. Do you see a good solution in this case, or should the recommendation only be to move the state up and resolve everything before rendering?

Do you see a good solution in this case, or should the recommendation only be to move the state up and resolve everything before rendering?

Lift up state, with hooks it will be easier. It also will solve issues like re-positioning requirement.

Warnings

:warning:
There are no updates provided to CHANGELOG. Ensure there are no publicly visible changes introduced by this PR.

  Generated by :no_entry_sign: dangerJS

Fails

:no_entry_sign:
All of your entries in CHANGELOG.md should be in the **Unreleased** section!

  Generated by :no_entry_sign: dangerJS


Very verbose HTTP error messages

When a HTTP error happens on the HTTP error message, the error string that comes back from the message contains the whole HTML error, This means the error messages are long enough to leave a nasty surprise (as I just discovered) :

The line that produces it is: https://github.com/cloudflare/cloudflare-go/blob/2c441b766adb2201bf54f31a43d3c2b016140d81/cloudflare.go#L106
What should we do, Clip the content (still, I don't know what useful info there is in there if the status is not something we expect) or just not post the content at all?

It's a bit of a difficult situation. We basically have two choices:

We can do what we do now, which is to conclude that something went wrong (HTTP status 504), and since we got some content back in the response, we might as well include that in the error in order to provide as much context as possible.
We can check if the status code either is unknown or on a pre-defined list, and the make up our own error message saying something along the lines of "An unknown error occurred, HTTP status 504 received", which isn't necessarily very helpful to the user.

A potential third option could be to go with open 1, but then limit the size of the body in the response to a certain number of bytes/characters, but I can't quite figure out of that's better or worse than the above suggestions.

Surely there should be no reason for a user to get a error message like that in general (provided api.cloudflare.com is online), As I see in that code we already look at the some error messages, We could catch things like 522,523,524,504,500 and return a error object "Provider fault" or something like that, For other error messages I would agree, it may be good to provide context, but there is no point bombing HTML page in someones error log

Fixed via #84.


XHR timeout disabled is required for file uploads.

A timeout (e.g. set globally to work around certain Google Chrome bugs) would otherwise break file uploads lasting longer than the set value.

Thanks for your contribution.
However if a timeout is set globally, this usually means there is a reason why requests should time out after the set time. And if file uploads are to be handled differently, I think it's better to explicitly set this in the fileupload initialization, than to set it globally, which might lead to surprises.

Well, normally someone might set the timeout and just have the response time in mind but for timeout the request time counts as well, in this case the length of the whole upload. In my case it was unexpected and I see no reason would ever want to have a timeout on an upload request.

there is a reason why requests should time out after the set time
Yes, like I wrote in the commit description there are certain Chrome bugs: http://stackoverflow.com/q/21063909

That is a valid argument. I've reconsidered and the surprise of not following the global timeout setting is a lesser concern, so I'll merge it. Thanks for your patience!

Great, thank you. Also worth mentioning in the wiki (which BTW I can't edit in this repo).

Done. Wiki editing is disabled as it was too much of a hassle to revert spam changes.


Add tunein.com and iheartradio.de support (fixes conflicts in #191)

Deciding that moving forward is our best option, I went ahead and fixed the manifest that was causing a conflict in #191.  ;)

Add iloveradio.de to README


Setting up WordPress with Docker

Proposed title of article
WordPress setup with Docker
Introduction paragraph (2-3 paragraphs):
WordPress is an open source content management written in PHP. WordPress comes with MSQL and MariaDB and together, they enable ease in creating dynamic websites. Besides, WordPress provides various plugins that facilitate drag and drop for website building.
In this tutorial, we will discus how to setup WordPress development environment using Docker. We will create a Docker compose file with a few services to run so our entire WordPress application will run on Docker container and not on our machine. We will use WordPress image, MySQL, and Phpmyadmin by setting up a single file that includes all of them before we setup wordpress.
Key takeaways:

Docker Compose
Using WordPress. MySQL & Phpmyadmin in a Docker container
Running WordPress using Docker

References:
Please list links to any published content/research that you intend to use to support/guide this article.
Templates to use as guides

How To Guide Template
Software Review Template
Tutorial Template

seems like a helpful topic - lets please be sure it add value beyond what is in the official docs and that it does not overlap with any existing EngEd articles or incoming topic suggestions (if you haven't already) to avoid any potential article closure. - approved
@mia-roberts

@hectorkambow  @mia-roberts I had already covered a similar topic of WordPress with Docker
https://www.section.io/engineering-education/docker-wordpress-containerizing-wordpress-with-docker-compose/

Thank you @Rose-stack, I did not see that before. Closing this issue.
cc @hectorkambow


[Bug]: Outgoing QoS upgrades not affecting storage of offline messages

Environment

VerneMQ Version: 1.13.0
OS: Linux/Docker
Cluster size/standalone: Standalone

Current Behavior
I run VerneMQ with the following command:
docker run -it --rm \
 -e DOCKER_VERNEMQ_ACCEPT_EULA=yes \
 -e DOCKER_VERNEMQ_ALLOW_ANONYMOUS=on \
 -e DOCKER_VERNEMQ_UPGRADE_OUTGOING_QOS=on \
 -p 1883:1883 -p 8888:8888 vernemq/vernemq:1.13.0

I create a persistent offline session with
mosquitto_sub -t 'test1' -q 1 -i c1 -c -d

Then I terminate the client and send two messages:
mosquitto_pub -t "test1" -m "test.q0" -q 0
mosquitto_pub -t "test1" -m "test.q1" -q 1

Then I start the client again:
mosquitto_sub -t 'test1' -q 1 -i c1 -c -d
Client c1 sending CONNECT
Client c1 received CONNACK (0)
Client c1 sending SUBSCRIBE (Mid: 1, Topic: test1, QoS: 1, Options: 0x00)
Client c1 received PUBLISH (d0, q1, r0, m1, 'test1', ... (7 bytes))
Client c1 sending PUBACK (m1, rc0)
test.q1
Client c1 received SUBACK
Subscribed (mid: 1): 1

Expected behaviour
Since QoS is upgraded from 0 to 1, I expect both messages to be handled as offline messages and sent to the client after it re-connects.
Configuration, logs, error output, etc.
Nothing of relevance

Code of Conduct

[X] I agree to follow the VerneMQ's Code of Conduct

@micw thanks, something smells wrong here.
I think we fail to add a message id and do not add the "QoS-0-message-which-is-now-a-Qos>0-message" to the waiting acks and replay queue in the FSM statemachines.
I agree the behaviour you expect is what the option promises. So, should be somehow fixed and aligned, even if it's a non-spec option. ("We have left MQTT jurisdiction").
This is somewhat low-priority for me but feel free to propose a fix, if it's urgent for your use case.

👉 Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
👉 Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.

The upgrade is done too late (the decision  to store on disk or not has already been made). The upgrade should be moved to the earliest possible moment (maybe in vmq_queue, and not in mqtt_fsm)

@mths1 Thanks for the PR! @micw can you give it a try? https://github.com/vernemq/vernemq/pull/2221

👉 Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
👉 Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.

Test plan:

publish without client connected and without any sessions

mosquitto_pub -t "test1" -m "test.q0" -q 0
mosquitto_pub -t "test1" -m "test.q1" -q 1

subscribe with a client, qos=1, clear-session=false

mosquitto_sub -t 'test1' -q 1 -i c1 -c -d

Expected result: no messages are received - PASS

publish with client connected

mosquitto_pub -t "test1" -m "test.q0" -q 0
mosquitto_pub -t "test1" -m "test.q1" -q 1

Expected result: both messages are received by the connected client. Both have qos 1 - PASS

disconnect the client, publish with client disconnected and existing offline session

mosquitto_pub -t "test1" -m "test.q0" -q 0
mosquitto_pub -t "test1" -m "test.q1" -q 1

subscribe with the same client id again, qos=1, clear-session=false

mosquitto_sub -t 'test1' -q 1 -i c1 -c -d

Expected result: both offline messages are received by the client. Both have qos 1 - PASS
Works for me.

@micw thanks for verifying! cc @mths1

👉 Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
👉 Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.


Maybe we increase the grouping function of the client management page.

Maybe we increase the grouping function of the client management page.
Each client occupies a large part of the area. When there are many people, it will be very crowded. You can make each of them in a specific group, and you can also fold the configuration file information in the group. , expand it when you want to view it.
This will make managing the client a lot easier.

Hi @tiny-andr, I have added a few improvements to the client configuration page. You can now collapse/expand each client (which will be remembered), apply a filter to narrow down the total list, and see a count. I didn't go as far as adding grouping yet, but I thought this would be a good start. In case you still use WS4W, feel free to grab the latest version and let me know what you think.

Hi @tiny-andr, I have added a few improvements to the client configuration page in 2.0.7. You can now collapse/expand each client (which will be remembered), apply a filter to narrow down the total list, and see a count. I didn't go as far as adding grouping yet, but I thought this would be a good start. In case you still use WS4W, feel free to grab the latest version and let me know what you think.

I would say this new feature is simply awesome!
I've been using wg4win. (I found this amazing app on 2.0.2, I'm still using 2.0.6, I also made a how-to video for this app, I'll be upgrading to 2.0.9! )

I'm glad to hear about your positive experience! I would be interested in seeing the video if you care to share. 😊
If you are happy with the new client configuration UI in 2.0.7+, please feel free to close this issue. Thanks!


Create documentation for deployment

We need to create a new page in https://docs.devqaly.com explaining how to deploy Devqaly.
Currently we do not have any support for other deployments other than just copy the repository and set it up manualy.
Later down the road we plan to add support for Docker.

This issue was transfered to https://github.com/devqaly/devqaly/issues/104


Change 100 lighthouse score circle to accurate representation

The template boasts 100 performance on lighthouse, but in reality the performance is around 60/100 if you use the real lighthouse - the one google will use to evaluate your website on the search engine results page. It even fails the core web vitals assessment.
https://pagespeed.web.dev/report?url=https%3A%2F%2Fprecedent.dev%2F

LGTM on Desktop:

Odd that Mobile is performing so poorly, will look into it. Closing this issue for now!

mobile is 75 👍


Website not working

The website is not working properly.

Can you describe please?

I am stuck at this in firefox. Checked in internet explorer, it is working just fine.
But, the transliteration never works for me.

Yes, we are finding some really weird problems happening. We are trying to fix it inshallah


Nux Generate is putting default data on dynamic routes and lagging the load

I'm loading data from an API and generating dynamic routes for each id getted from API, all is working like expected but all the generated pages is builded with some default data. Example, if i have an area with {{data.name}}, this area will be filled with some name during the generate build, and when i load the page, it will show first the default text and a second after the page shows the right text. It is not a static behavior, cause the page is getting the right text async for some reason, and until the real text is not getted, the page shows some arbitrary text. It is a bug or a feature?
my code is:
// nuxt.config.js
generate: {
    routes: function () {
      return axios.get('http://rest.bandsintown.com/artists/u2/events?app_id=apptest')
        .then(res => {
          return res.data.map(item => {
            return {
              route: '/posts/' + item.id,
              payload: item
            }
          })
        })
    }
 }

// Dynamic route
<template>

        {{data.id}} - {{data.venue.name}}

</template>

Video showing the behavior

Image (Red is the default text and Blue is the right text that i need the page load), i dont know why the Red text exists inside the page, that is the problem that i'm trying to explain here.

Hi, thanks for using Nuxt.
It's a bug, we are working on it and should be fixed in the next release.

#896

Thanks


Rename the armeabi folders in the SDK .AAR files to armeabi-v7a to target the correct ABI

Some of the SDK's .AAR files contain armeabi folders with native libraries, while the SDK documentation states: "The Public Preview App SDK supports armeabi-v7a processors only" (link)
In Xamarin Android, these armeabi folders cause the SfB App SDK to fail loading in apps that target armeabi-v7a only (i.e. because the app also uses other native libraries that only support armeabi-v7a and that do use the correct folder names).
As a workaround, I unpack the AAR's, rename the armeabi folders to armeabi-v7a, and repack them.
For other people experiencing this problem: here is the Mac Terminal script that I use to partially automate this rename:
find . -type f -name *.aar -execdir unzip {} -d tmp/{} \;
find . -type d -name armeabi -execdir mv {} {}-v7a \;

echo manually:cd tmp; md new; for each renamed aar: jar cvf new/SkypeForBusinessNative.aar -C SkypeForBusinessNative.aar .

(Ps I use a Mac for creating Xamarin bindings for the SfB App SDK's for both Android and iOS)

@VincentH-Net "Failed to resolve" errors are related to this ?


Vulnerability roundup 85: gradle-5.6.4: 1 advisory [5.9]

search, files

[ ] CVE-2019-16370 CVSSv3=5.9 (nixos-20.03, nixos-unstable)

Scanned versions: nixos-20.03: a84b797b28e; nixos-unstable: 22c98819ccd. May contain false positives.

20.03 is frozen and EOL.
20.09 at 6.6
master at 6.7
Closing.


[Android] Fix race condition in ConnectionStateStreamHanderl (#468)

Add extra null check and synchronized block in async callback

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

After this commit, the crash no longer happens for me.
I was able to reproduce the crash about 80% of the time before.

Thanks for creating the issue and fixing it! Looks good!


Pre-request hook for request mangling

See Issue #106 for details.

@j16sdiz I like this approach. Two comments

Can you please add tests for it?
Seems like Travis complained about the test, can you check?

Thx!.

seems ok, could even be useful for some other things

@j16sdiz could you add a test for this? maybe even the use case you're giving it

I have added a test case.

@marcosnils this seems ok, any comments?

@sschepens @j16sdiz :+1: merging.

After merging I just think about something:
Why not providing some way of hooking middleware functions that will be called before and after each request?. That way goreq can be extended with different middlewares to do different things such as authentication / logging / etc.
I feel like we're missing something if we just give the ability to call a before function and not an after one/

@marcosnils  Actually, I had considered adding an interface for more hooks, but that kind of interface is hard to change without breaking backward compatibility. Without a full usecase for other hooks, I just implemented what I need.


B2BUA?

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@tong3jie you would use this framework to build a B2BUA


fix(*): prevent queues from growing without bounds

Summary
This commit implements an upper limit on the number of batches that may be waiting on a queue for processing.  Once the limit has been reached, the oldest batch is dropped from the queue and an error message is logged.  The maximum number of batches that can be waiting on a queue is configured through the max_queued_batches parameter of the queue, which defaults to 100 and can be globally overriden with the max_queued_batches parameter in kong.conf
A more complete rewrite of the queuing system is in the works but will not make it into 3.2.
KAG-303
This reverts commit 218cc0a81500986b0b94e6b4e350302326097018 and fffb4e8626ba9ec99194cd3d9f9cd15e19c72c61
Checklist

[X] The Pull Request has tests
[X] There's an entry in the CHANGELOG
[ ] There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

The backport to release/2.8.x failed:
The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-release/2.8.x release/2.8.x
# Navigate to the new working tree
cd .worktrees/backport-release/2.8.x
# Create a new branch
git switch --create backport-10247-to-release/2.8.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 94a31c6471f5a52e22968e88f522135213233324
# Push it to GitHub
git push --set-upstream origin backport-10247-to-release/2.8.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release/2.8.x

Then, create a pull request where the base branch is release/2.8.x and the compare/head branch is backport-10247-to-release/2.8.x.

The backport to release/3.0.x failed:
The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-release/3.0.x release/3.0.x
# Navigate to the new working tree
cd .worktrees/backport-release/3.0.x
# Create a new branch
git switch --create backport-10247-to-release/3.0.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 94a31c6471f5a52e22968e88f522135213233324
# Push it to GitHub
git push --set-upstream origin backport-10247-to-release/3.0.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release/3.0.x

Then, create a pull request where the base branch is release/3.0.x and the compare/head branch is backport-10247-to-release/3.0.x.

The backport to release/3.1.x failed:
The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-release/3.1.x release/3.1.x
# Navigate to the new working tree
cd .worktrees/backport-release/3.1.x
# Create a new branch
git switch --create backport-10247-to-release/3.1.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 94a31c6471f5a52e22968e88f522135213233324
# Push it to GitHub
git push --set-upstream origin backport-10247-to-release/3.1.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release/3.1.x

Then, create a pull request where the base branch is release/3.1.x and the compare/head branch is backport-10247-to-release/3.1.x.

@hanshuebner I might be missing some context but what is driving the inclusion of this feature again? What's the implication of this change for batch queue rewrite later? Can we remove this new config option safely in the future?

@dndx We've decided to include this band-aid fix because an important customer demands an immediate solution (FTI-4756).  We will be able to deprecate the global parameter and convert it to the plugin specific parameter - if set - when we move on to the new implementation.


simplex-lt fold

a0*x0 + a1*x1 + ... < 0 is equivalent to -x0-x1- ... < 0 if xi >= 0 and ai < 0.

this is not universally faster, similar speed overall


Docs delete

@sierra-moxon    Please review
Note: Mac systems cannot distinguish files that are the same name except for case. So some artifacts in docs like:
~/docs/Allele.html
~/docs/allele.html
Cannot be considered different files on a Mac (pointed out by @oblodgett )
Olin helped me clean this up and make the commit.

In the unix world Allele.html and allele.html are two different files. However in the mac world they are the same file. If someone on a unix / windows machine commits these, then what happens on the mac via git checkout / close / etc is the first file gets written to disk and then the second file overwrites the first file because "they are the same file" so it looks like the first file was modified however its now the second file. And what can be even more strange is the mac will show you two "different" files on the filesystem. The same physical file with "two pointers". Long story short... avoid this if possible.

@oblodgett - indeed.  in fact, no one except github-actions user should be regenerating docs (we'll get there).


Restructure repository packages into pkg subdirs

This restructures the repository to reduce the clutter in the root directory of the repository. Resolves #128

This won't be a breaking change to package-analysis as it's pinned but it's probably worth following it up.

Will do this today :+1:


Applied downstream PR and fixed some issues

Scan submitted to Checkmarx

Checkmarx scan completed
Full Scan Details
Checkmarx Scan Summary

Severity
Count

High
0

Medium
0

Low
1

Informational
0

Violation Summary

Severity
Count

Details

Lines
Severity
Category
File
Link


Update CI pipeline to use devcontainer Docker image for all jobs

This PR updates the CircleCI workflow so that all jobs in the workflow run inside the same container. This will remove problems where the dependencies are updated and checks run locally but not in CI.
New Features

Updates the CircleCI workflow to use the Docker image that is created in the build-image step of the workflow.

Linked to
Closes #20

Codecov Report

Merging #25 (9b7f781) into main (bb892c7) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff            @@
##              main       #25   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines            5         5
=========================================
  Hits             5         5

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


The new Colorspace implementation doesn't quite support RGBA, and that breaks jpg and png rendering

Both our JPG and PNG decoders set surface format as RGBA.  This breaks some validation apps (they use cocos2d), where the colors of the PNG and JPG images are off.

@shahmeeresmail I have a potential fix, but that breaks in other circumstances.  Will submit a PR and tag you, would you be able to take a look?

Also UIImage is constructed directly to hold the backing instead of a CGImage.  If the CGImageRef is then passed to other CG methods, we will create another backing (inside the backing) and be all kinds of broken.  TBD: #848

Yes, I can take a look at the PR.
On another note, I have been unable to repro the issue with WOCCATALOG nor with any of the other samples.


Potential issue with spearman R bootstrapping

We observed the following test failure when integrating another PR:
======================================================================
FAIL: test_sample_level_spearmanr_bootstrap (integration_tests.meta_eval_wmt_da_test.MetaEvalNLGCITest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/runner/work/ExplainaBoard/ExplainaBoard/integration_tests/meta_eval_wmt_da_test.py", line 191, in test_sample_level_spearmanr_bootstrap
    self.assertAlmostEqual(ci[0], 0.6488, 2)
AssertionError: 0.7325904563487001 != 0.6488 within 2 places (0.08379045634870008 difference)

----------------------------------------------------------------------

We are not sure whether this is an issue with the test or the underlying code, but as a temporary measure we reduced the sensitivity of the test. We should go back and check to make sure whether this is just due to bootstrapping variance or whether it's due to a bug in the test itself.

The cause of randomness may be that we didn't fix the random seed.
https://github.com/neulab/ExplainaBoard/blob/9ba998c125587bb5a9b421706b1ca50028af220b/explainaboard/metrics/metric.py#L571
I think a possible fix is:

Provide a way to fix the seed from outside
Implement test case with almost-equal assertion for several seeds

NumPy provides SeedSequence functionality which allows us to hierarchically initialize the random seeds over the whole library. I think it would be better that every class that calculates something have SeedSequence argument in __init__.

That seems reasonable to me.

I'm seeing this failures with a high probability. It's time consuming to re-run integration tests just to make PR green. Is someone already working on the fix?

We have a temporary fix of making the test more lenient that is mixed in with this PR: https://github.com/neulab/ExplainaBoard/pull/532
It might be worth pulling out just that fix and making it a separate PR.

@neubig I think we should create a separate PR to fix this flaky test as soon as possible, given that the PR is still in review.

I agree. I'm not able to do it now, but welcome anyone else who can do it

@neubig I'll create a PR to cherry-pick the change in the test in #532. I will add comments to #532, too.

Plan to apply the change:

Implement seed argument in Metric.__init__, which is defaulting to None. If seed is None, it is initialized randomly.
Implement Metric.get_seed to return the seed that the object holds.
In inherited classes, Implement randomizer with initializing a spawned seed from the seed returned by get_seed.

Assigning to me as per the offline discussion with @odashi.


How do I connect this service remotely?

Do you want to request a feature or report a bug?
Feature
What did you expect to see?
Documentation/How-to for remotely installing and accessing this service

Did you try the Getting Started guide? Did you have issues following that?

Closing this off due to inactivity. Please let me know if you have any additional questions


ISSUE-117 Add list datasets by processing level to podaac_utils

This PR

rearranges the functions in podaac/podaac_utils.py such that they are in alphabetical order
adds two new functions, namely list_level4_dataset_ids and list_level4_dataset_short_names which aid in using OCW for Level4-specific applications such as Apache OCW.

Coverage increased (+0.1%) to 96.27% when pulling 991bb8f966531ff265af0be4f05f8a4be40d132d on ISSUE-117 into b562e0bb9259695f4cc30e27d1e656ff74296254 on master.


[BUG] Upgrade Longhorn Rancher catalog app - Wait helm template failed. panic: interface conversion:

Describe the bug
Errors upgrading Longhorn catalog app from 1.0.2 to 1.1.0
To Reproduce
Steps to reproduce the behavior:

Go to cluster, go to project, go to apps, see indicator that Longhorn upgrade is available
Click on upgrade available
ensure all values are correct (we are air-gapped, so i used the provided save-images/load-images scripts)
See error

Expected behavior
Longhorn is upgraded to v1.1.0
Error
Wait helm template failed. panic: interface conversion: interface {} is string, not map[string]interface {} goroutine 1 [running]: k8s.io/helm/pkg/strvals.(*parser).key(0xc000544f20, 0xc000579a70, 0xc00067d438, 0x8) /go/src/k8s.io/helm/pkg/strvals/parser.go:211 +0xfde k8s.io/helm/pkg/strvals.(*parser).key(0xc000544f20, 0xc000579860, 0xc00067d650, 0x5) /go/src/k8s.io/helm/pkg/strvals/parser.go:215 +0x1ad k8s.io/helm/pkg/strvals.(*parser).key(0xc000544f20, 0xc0005797d0, 0x0, 0x0) /go/src/k8s.io/helm/pkg/strvals/parser.go:215 +0x1ad k8s.io/helm/pkg/strvals.(*parser).parse(0xc000544f20, 0xc0005797d0, 0xe00) /go/src/k8s.io/helm/pkg/strvals/parser.go:133 +0x38 k8s.io/helm/pkg/strvals.ParseInto(0x7fffdc2900f2, 0xee9, 0xc0005797d0, 0xc000000180, 0x200000003) /go/src/k8s.io/helm/pkg/strvals/parser.go:85 +0xbf main.vals(0x0, 0x0, 0x0, 0xc000328bb0, 0x1, 0x1, 0x2e176f8, 0x0, 0x0, 0x2e176f8, ...) /go/src/k8s.io/helm/cmd/helm/install.go:420 +0x29d main.(*templateCmd).run(0xc0000ac360, 0xc00031af00, 0xc0000f7110, 0x1, 0x7, 0x0, 0x0) /go/src/k8s.io/helm/cmd/helm/template.go:139 +0x1dc k8s.io/helm/vendor/github.com/spf13/cobra.(*Command).execute(0xc00031af00, 0xc0000f70a0, 0x7, 0x7, 0xc00031af00, 0xc0000f70a0) /go/src/k8s.io/helm/vendor/github.com/spf13/cobra/command.go:826 +0x465 k8s.io/helm/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0xc0000bc500, 0x8, 0x8, 0xc0000bc500) /go/src/k8s.io/helm/vendor/github.com/spf13/cobra/command.go:914 +0x2fc k8s.io/helm/vendor/github.com/spf13/cobra.(*Command).Execute(...) /go/src/k8s.io/helm/vendor/github.com/spf13/cobra/command.go:864 main.main() /go/src/k8s.io/helm/cmd/helm/helm.go:270 +0x7a : exit status 2
Environment:

Longhorn version: v1.0.2
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: RKE v1.2.3
Node config

OS type and version: Ubuntu 18.04.5 LTS
CPU per node: 4
Memory per node: 8
Disk type(e.g. SSD/NVMe): SSD
Network bandwidth and latency between the nodes: 1Gb

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): VMware ESXi 6.7

Additional context
Add any other context about the problem here.
gz#14149

@pulberg just to verify did you run the load/save images against the updated images.txt file for the longhorn 1.1 release?
Since we added a new share-manager image.
Interestingly the above looks like a helm template failure.

Yes, here is the list of images -
bat longhorn-images.txt
───────┬──────────────────────────────────────────────────
       │ File: longhorn-images.txt
───────┼──────────────────────────────────────────────────
   1   │ longhornio/longhorn-engine:v1.1.0
   2   │ longhornio/longhorn-instance-manager:v1_20201216
   3   │ longhornio/longhorn-share-manager:v1_20201204
   4   │ longhornio/longhorn-manager:v1.1.0
   5   │ longhornio/longhorn-ui:v1.1.0
   6   │ longhornio/csi-attacher:v2.2.1-lh1
   7   │ longhornio/csi-provisioner:v1.6.0-lh1
   8   │ longhornio/csi-resizer:v0.5.1-lh1
   9   │ longhornio/csi-snapshotter:v2.1.1-lh1
  10   │ longhornio/csi-node-driver-registrar:v1.2.0-lh1

The Longhorn images LGTM.
I just google the error you provide. It seems that something is wrong with the config value of the Longhorn Helm options. Can you click Edit as YAML on the Longhorn upgrade page then paste the contents (remember to delete the sensitive data) here?
BTW, what's your Rancher version?

Wait helm template failed. 2020/12/31 17:51:03 Warning: Merging destination map for chart 'longhorn'. Overwriting table item 'ui', with non table value: longhornio/longhorn-ui 2020/12/31 17:51:03 Warning: Merging destination map for chart 'longhorn'. Overwriting table item 'engine', with non table value: longhornio/longhorn-engine 2020/12/31 17:51:03 Warning: Merging destination map for chart 'longhorn'. Overwriting table item 'instanceManager', with non table value: longhornio/longhorn-instance-manager 2020/12/31 17:51:03 Warning: Merging destination map for chart 'longhorn'. Overwriting table item 'manager', with non table value: longhornio/longhorn-manager Error: render error in "longhorn/templates/uninstall-job.yaml": template: longhorn/templates/uninstall-job.yaml:20:56: executing "longhorn/templates/uninstall-job.yaml" at <.Values.image.longhorn.manager.repository>: can't evaluate field repository in type interface {} : exit status 1

It seems that something is wrong with your Helm rendering. More accurately, according to the error message, the value types seem to be messed up. e.g.The error at <.Values.image.longhorn.manager.repository>: can't evaluate field repository in type interface {} : exit status 1 is weird. According to the YAML you provide, the value should be "longhornio/longhorn-manager"  rather than an invalid type interface {}.
I cannot reproduce this error with the config you provide (except for the air-gapped setting). Have you applied other operations before the upgrade?

It seems that something is wrong with your Helm rendering. More accurately, according to the error message, the value types seem to be messed up. e.g.The error at <.Values.image.longhorn.manager.repository>: can't evaluate field repository in type interface {} : exit status 1 is weird. According to the YAML you provide, the value should be "longhornio/longhorn-manager"  rather than an invalid type interface {}.
I cannot reproduce this error with the config you provide (except for the air-gapped setting). Have you applied other operations before the upgrade?

Nothing else was/has been done, I'm simply trying to upgrade the current v1.0.2 install.
The only things I modify on the upgrade page are -

Pick v1.1.0 from the "template version" dropdown.
Enter my private registry secret name.
Update the "static storageclass name" to what mine is called.
Click upgrade.
View multiple errors.

Nothing else was/has been done, I'm simply trying to upgrade the current v1.0.2 install.
The only things I modify on the upgrade page are -

Pick v1.1.0 from the "template version" dropdown.
Enter my private registry secret name.
Update the "static storageclass name" to what mine is called.
Click upgrade.
View multiple errors.

All right. Can you try the following to see if it's a Rancher + Helm issue?

Download this chart directory: https://github.com/longhorn/longhorn/tree/master/chart
Update the value files, or directly use --set when running the command in step3
Run the helm command to see if the rendering works fine. e.g.

cd <The Chart Directory>
helm template --dry-run --debug longhorn ./ --namespace longhorn-system

If it works fine, then there may be something wrong with Rancher + Helm. If NO, there may be something wrong with the values or Helm itself.

All right. Can you try the following to see if it's a Rancher + Helm issue?

Download this chart directory: https://github.com/longhorn/longhorn/tree/master/chart
Update the value files, or directly use --set when running the command in step3
Run the helm command to see if the rendering works fine. e.g.

cd <The Chart Directory>
helm template --dry-run --debug longhorn ./ --namespace longhorn-system

If it works fine, then there may be something wrong with Rancher + Helm. If NO, there may be something wrong with the values or Helm itself.

OK. I can reproduce this issue now. Here is the Reproducing step:

Deploy Longhorn via Rancher UI - Cluster Manager

Set version to 1.0.2
Select Default Image: False
Select Customize Default Settings: True and ChangeDefault Longhorn Static StorageClass Name: longhorn

Wait for deployment success then upgrade to v1.1.0. The error reported above will be shown.

Set version to 1.1.0 then not change any other existing parameters.

OK. I can reproduce this issue now. Here is the Reproducing step:

Deploy Longhorn via Rancher UI - Cluster Manager

Set version to 1.0.2
Select Default Image: False
Select Customize Default Settings: True and ChangeDefault Longhorn Static StorageClass Name: longhorn

Wait for deployment success then upgrade to v1.1.0. The error reported above will be shown.

Set version to 1.1.0 then not change any other existing parameters.

This seems to be more towards a rancher UI issue.
Observed that the payload passed from rancher UI include both old and new answers key values. This confused helm in rancher and caused panic.

A quick workaround could be to pass the changes as the YAML file this would pass in the changes as valuesYaml instead of answers.

Select 1.1.0 in Template Version.
Click Edit as YAML on the Longhorn upgrade page
Click Upgrade.

This seems to be more towards a rancher UI issue.
Observed that the payload passed from rancher UI include both old and new answers key values. This confused helm in rancher and caused panic.

A quick workaround could be to pass the changes as the YAML file this would pass in the changes as valuesYaml instead of answers.

Select 1.1.0 in Template Version.
Click Edit as YAML on the Longhorn upgrade page
Click Upgrade.

Thanks @c3y1huang . I saw you already filed a Rancher issue. Let's wait for the response to the issue before proceeding.
Move the issue to Icebox.

Thanks @c3y1huang . I saw you already filed a Rancher issue. Let's wait for the response to the issue before proceeding.
Move the issue to Icebox.

This can be fixed at Longhorn side, closing.

@innobead Please explain how to fix this on the Longhorn side as you stated.


first rough version of lyrics module

Let me know what you think?

I queried the API for you used to call me on my cellphone and didn't get the expected result.

@swapagarwal hmm yeah, i don't think the api is up to date. Also there aren't many good apis out there so I'm gonna close this for now.

@williamshoops96 Have you tried MusixMatch?