405 errors, and others..

So I can confirm on 2012r2 WMF 5.0 doesn't work and errors around the Invoke CimMethod.  (don't have the errors to hand any more! but they were pretty terminal)
5.1 gets further, but it appears that it doesn't install or enable WebDAV - (doesn't seem to throw errors)  which then gave me 405 method not allowed errors..
I'm now having issues with it configuring the source repo's
VERBOSE: [servername]:                            [[PackageManagementSource]SourceGallery] Repository details, Name
 = 'PSPrivateGallery', Location = 'http://servername:8080/api/v2/'; IsTrusted = 'True'; IsRegistered = 'True'.
The PSGallery repository has pre-defined locations. The 'Location, NewLocation or SourceLocation' parameter is not
allowed, try again after removing the 'Location, NewLocation or SourceLocation' parameter.
    + CategoryInfo          : InvalidArgument: (https://www.powershellgallery.com:) [], CimException
    + FullyQualifiedErrorId : ParameterIsNotAllowedWithPSGallery,Add-PackageSource,Microsoft.PowerShell.PackageManagem
   ent.Cmdlets.RegisterPackageSource
    + PSComputerName        : localhost

VERBOSE: [servername]: LCM:  [ End    Set      ]  [[PackageManagementSource]SourceGallery]  in 1.5780 seconds.
PowerShell DSC resource MSFT_PackageManagementSource  failed to execute Set-TargetResource functionality with error
message: Failed to register the package source PSGallery. Message:System.Exception: The PSGallery repository has
pre-defined locations. The 'Location, NewLocation or SourceLocation' parameter is not allowed, try again after
removing the 'Location, NewLocation or SourceLocation' parameter.
    + CategoryInfo          : InvalidOperation: (:) [], CimException
    + FullyQualifiedErrorId : ProviderOperationExecutionFailure
    + PSComputerName        : localhost

Trying to re-run the install gives me a unable to insert duplicate row into the database around the user setup.
VERBOSE: [servername]:                            [[PSGalleryUser]PrivateGalleryUser] User 'GalleryUser' does not
exist in database 'PSGallery'
VERBOSE: [servername]:                            [[PSGalleryUser]PrivateGalleryUser] Adding user 'GalleryUser' to
database 'PSGallery'
VERBOSE: [servername]:                            [[PSGalleryUser]PrivateGalleryUser] 'Users' table in the database
 'PSGallery' on '(LocalDb)\PSGallery' instance is not populated. Populating the table...
Exception calling "ExecuteNonQuery" with "0" argument(s): "Cannot insert duplicate key row in object 'dbo.Users' with
unique index 'IX_UsersByUsername'. The duplicate key value is (GalleryUser).
The statement has been terminated."
    + CategoryInfo          : NotSpecified: (:) [], CimException
    + FullyQualifiedErrorId : SqlException,Set-TableData
    + PSComputerName        : localhost

VERBOSE: [servername]: LCM:  [ End    Set      ]  [[PSGalleryUser]PrivateGalleryUser]  in 0.6410 seconds.
The PowerShell DSC resource '[PSGalleryUser]PrivateGalleryUser' with SourceInfo
'C:\PSPrivateGallery\Configuration\PSPrivateGalleryPublish.ps1::35::9::PSGalleryUser' threw one or more
non-terminating errors while running the Set functionality. These errors are logged to the ETW channel called
Microsoft-Windows-DSC/Operational. Refer to this channel for more details.
    + CategoryInfo          : InvalidOperation: (:) [], CimException
    + FullyQualifiedErrorId : NonTerminatingErrorFromProvider
    + PSComputerName        : localhost

VERBOSE: [servername]: LCM:  [ End    Set      ]
The SendConfigurationApply function did not succeed.
    + CategoryInfo          : NotSpecified: (root/Microsoft/...gurationManager:String) [], CimException
    + FullyQualifiedErrorId : MI RESULT 1
    + PSComputerName        : localhost

VERBOSE: Operation 'Invoke CimMethod' complete.
VERBOSE: Time taken for configuration job to complete is 47.214 seconds

Just to add I have swapped back to windows 2012 r2 with GUI, after failing to get this working on 2016TP5 Core edition.

And then once I try and publish a module I get:
PS C:\temp> Publish-Module -Path .\MyModuleName -Repository PSPrivateGallery -NuGetApiKey c34d0782-b5ad-4b45-9165-a168b7f0436f
WARNING: This module 'C:\Users\!davidw\AppData\Local\Temp\225150623\MyModuleName\MyModuleName.psd1' has exported functions.
 As a best practice, include exported functions in the module manifest file(.psd1). You can run Update-ModuleManifest -FunctionsToExport to update
the manifest with ExportedFunctions field.
Publish-PSArtifactUtility : Failed to publish module 'MyModuleName': 'Cannot prompt for input in non-interactive mode.
'.
At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\<IP_ADDRESS>\PSModule.psm1:1079 char:17
+                 Publish-PSArtifactUtility -PSModuleInfo $moduleInfo `
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : FailedToPublishTheModule,Publish-PSArtifactUtility

PS C:\temp>

I have ensured I have nuget downloaded:
Invoke-WebRequest -Uri "http://go.microsoft.com/fwlink/?LinkID=690216&clcid=0x409" -OutFile "C:\ProgramData\Microsoft\Windows\PowerShell\PowerShellGet\NuGet.exe"
If I try an incorrect API key, I get the same error..
Is there a way I can test this with NUGET?

HELP!!!

Are you using PowerShell v5.0 or 5.1 on 2012R2? I think it's broken on 5.0 based on my previous tests.

rebuilt the box as 2012 r2 with gui and WMF 5.1 - Tried 5.0 and that failed badly..
Rebuilt again after and did 5.1

And that's the setup you're getting the API key errors for?

Yeah.  Don't suppose you documented the steps you used for a working
install or any prerequisites you installed prior
On 27 Sep 2016 19:30, "Michael T Lombardi"<EMAIL_ADDRESS>wrote:

And that's the setup you're getting the API key errors for?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/PowerShell/PSPrivateGallery/issues/21#issuecomment-249954865,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANNq_mC140IilNWOi2UiJ9wfonjTviBDks5quWCpgaJpZM4J7kWK
.

I did, actually, here - you can check the source repo for the configs/etc.

Fresh build and slightly tweaked script to install results in the above:
[cmdletbinding()]
param (
    [string]$AdminPass',
    [string]$UserPass',
    [string]$ApiKey = (New-Guid | Select-Object -ExpandProperty Guid),
    [string]$EmailAddress =<EMAIL_ADDRESS>    [string]$PrivateGalleryName = 'PSPrivateGallery'
)

dir -path "c:\pspg" -recurse |unblock-file

copy-item -path "c:\pspg\Modules\*" -Destination "$env:ProgramFiles\WindowsPowerShell\Modules" -recurse -force

Push-Location $PSScriptRoot
New-Object System.Management.Automation.PSCredential ('GalleryAdmin',(ConvertTo-SecureString $AdminPass -AsPlainText -Force)) | Export-Clixml -Path .\GalleryAdminCredFile.clixml
New-Object System.Management.Automation.PSCredential ('GalleryUser',(ConvertTo-SecureString $UserPass -AsPlainText -Force)) | Export-Clixml -Path .\GalleryUserCredFile.clixml

# Update the environment variables with those specified at build time.
$UpdatedGalleryEnvironment = Get-Content .\PSPrivateGalleryEnvironment.psd1 | ForEach-Object {
    $_.Replace('PSPrivateGallery',$PrivateGalleryName)
}
$UpdatedGalleryEnvironment | Out-File .\PSPrivateGalleryEnvironment.psd1

$UpdatedGalleryPublishEnvironment = Get-Content .\PSPrivateGalleryPublishEnvironment.psd1 | ForEach-Object {
    $Processing = $_.Replace('PSPrivateGallery',$PrivateGalleryName)
    $Processing = $Processing.Replace('First.Last@Domain.com',$EmailAddress)
    $Processing.Replace('ApiKeyGuid',$ApiKey)
}
$UpdatedGalleryPublishEnvironment | Out-File .\PSPrivateGalleryPublishEnvironment.psd1

& .\PSPrivateGallery.ps1
& .\PSprivateGalleryPublish.ps1
Pop-Location

Hi All.
The latest Master has all of the above issues fixed. I have verified on WS2012R2+WMF5.1 and Server 2016 Preview.
And @michaeltlombardi - excellent how-to on deploying PSPrivateGallery to Azure.
https://michaeltlombardi.github.io/PSPrivateGalleryWalkthrough/
-Raghu

Glad to see this repo getting more love! :)
Started off writing a blog, ended up writing a walkthrough on our experience.

Look forward to trying this again :)

not resolved for me:

also if I try and publish with it in the above state I get:

Last time I tracked this down to WebDAV not being installed..

@davidwallis3101 The first error is from PackageManagementProviderResource
I believe v1.0.3 of this resource has the fix. May I know the version of this DSC resource on your machine?

default build after installing wmf 5.1..
PS C:\WINDOWS\system32> Get-DscResource -Module PackageManagementProviderResource
WARNING: There are no modules present in the system with the given module specification.
PS C:\WINDOWS\system32>

after running:
$zipFile = 'c:\PSPrivateGallery-master.zip'
If (Test-Path $zipFile){ Remove-Item $zipFile }
Invoke-WebRequest -Uri "https://github.com/PowerShell/PSPrivateGallery/archive/master.zip" -OutFile $zipFile

Unblock-File $zipFile
Expand-Archive –Path $zipFile –DestinationPath "C:\" –Force

Rename-Item –Path "C:\PSPrivateGallery-master" –NewName "C:\PSPrivateGallery"

Copy-Item -path "C:\PSPrivateGallery\Modules\*" -Destination "$env:ProgramFiles\WindowsPowerShell\Modules" -recurse -force

I get the following
PS C:\WINDOWS\system32> Get-DscResource -Module PackageManagementProviderResource

ImplementedAs   Name                      ModuleName                     Version    Properties
-------------   ----                      ----------                     -------    ----------
PowerShell      NugetPackage              PackageManagementProviderRe... 1.0.3      {DestinationPath, Name, DependsO.
PowerShell      PackageManagement         PackageManagementProviderRe... 1.0.3      {Name, AdditionalParameters, Dep.
PowerShell      PackageManagementSource   PackageManagementProviderRe... 1.0.3      {Name, ProviderName, SourceUri, .
PowerShell      PSModule                  PackageManagementProviderRe... 1.0.3      {Name, DependsOn, Ensure, Instal.

PS C:\WINDOWS\system32>

so lets try an install by running:
Cd "C:\PSPrivateGallery\Configuration"

New-Object System.Management.Automation.PSCredential ('GalleryAdmin',(ConvertTo-SecureString "APassword" -AsPlainText -Force)) | Export-Clixml -Path .\GalleryAdminCredFile.clixml
New-Object System.Management.Automation.PSCredential ('GalleryUser',(ConvertTo-SecureString "APassword" -AsPlainText -Force)) | Export-Clixml -Path .\GalleryUserCredFile.clixml

.\PSPrivateGallery.ps1

.\PSPrivateGalleryPublish.ps1

get the following errors:
`VERBOSE: Perform operation 'Invoke CimMethod' with following parameters, ''methodName' =
SendConfigurationApply,'className' = MSFT_DSCLocalConfigurationManager,'namespaceName' =
root/Microsoft/Windows/DesiredStateConfiguration'.
VERBOSE: An LCM method call arrived from computer SERVER with user sid
S-1-5-21-196282956-19940018-89367796-25974.
VERBOSE: [SERVER]: LCM:  [ Start  Set      ]
VERBOSE: [SERVER]: LCM:  [ Start  Resource ]  [[PackageManagementSource]SourceGallery]
VERBOSE: [SERVER]: LCM:  [ Start  Test     ]  [[PackageManagementSource]SourceGallery]
VERBOSE: [SERVER]:                            [[PackageManagementSource]SourceGallery] Begin invoking
Get-packageSource PSGallery
VERBOSE: [SERVER]:                            [[PackageManagementSource]SourceGallery] Repository details, Name
= 'PSGallery', Location = 'https://www.powershellgallery.com/api/v2/'; IsTrusted = 'False'; IsRegistered = 'True'.
VERBOSE: [SERVER]:                            [[PackageManagementSource]SourceGallery] Repository details, Name
= 'PSGallery', Location = 'https://www.powershellgallery.com/api/v2/'; IsTrusted = 'False'; IsRegistered = 'True'.
VERBOSE: [SERVER]:                            [[PackageManagementSource]SourceGallery] Package source
'PSGallery' not found
VERBOSE: [SERVER]:                            [[PackageManagementSource]SourceGallery] Resource PSGallery is
not in the desired state. Required Ensure is Present and actual Ensure is Absent
VERBOSE: [SERVER]: LCM:  [ End    Test     ]  [[PackageManagementSource]SourceGallery]  in 10.4530 seconds.
VERBOSE: [SERVER]: LCM:  [ Start  Set      ]  [[PackageManagementSource]SourceGallery]
WARNING: [SERVER]:                            [[PackageManagementSource]SourceGallery] Begin registering
'PSGallery' to source location 'https://www.powershellgallery.com' with 'Trusted' policy"
VERBOSE: [SERVER]:                            [[PackageManagementSource]SourceGallery] Begin invoking
Register-Packagesource PSGallery
VERBOSE: [SERVER]:                            [[PackageManagementSource]SourceGallery] Repository details, Name
= 'PSGallery', Location = 'https://www.powershellgallery.com/api/v2/'; IsTrusted = 'False'; IsRegistered = 'True'.
VERBOSE: [SERVER]:                            [[PackageManagementSource]SourceGallery] Successfully
unregistered the repository 'PSGallery'.
VERBOSE: [SERVER]:                            [[PackageManagementSource]SourceGallery] Repository details, Name
= 'PSGallery', Location = 'https://www.powershellgallery.com/api/v2/'; IsTrusted = 'True'; IsRegistered = 'True'.
VERBOSE: [SERVER]:                            [[PackageManagementSource]SourceGallery] Successfully registered
the package source PSGallery
VERBOSE: [SERVER]: LCM:  [ End    Set      ]  [[PackageManagementSource]SourceGallery]  in 2.2340 seconds.
VERBOSE: [SERVER]: LCM:  [ End    Resource ]  [[PackageManagementSource]SourceGallery]
VERBOSE: [SERVER]: LCM:  [ Start  Resource ]  [[PackageManagementSource]PrivateGallery]
VERBOSE: [SERVER]: LCM:  [ Start  Test     ]  [[PackageManagementSource]PrivateGallery]
VERBOSE: [SERVER]:                            [[PackageManagementSource]PrivateGallery] Begin invoking
Get-packageSource PSPrivateGallery
VERBOSE: [SERVER]:                            [[PackageManagementSource]PrivateGallery] Package source
'PSPrivateGallery' not found
VERBOSE: [SERVER]:                            [[PackageManagementSource]PrivateGallery] Resource
PSPrivateGallery is not in the desired state. Required Ensure is Present and actual Ensure is Absent
VERBOSE: [SERVER]: LCM:  [ End    Test     ]  [[PackageManagementSource]PrivateGallery]  in 0.7650 seconds.
VERBOSE: [SERVER]: LCM:  [ Start  Set      ]  [[PackageManagementSource]PrivateGallery]
WARNING: [SERVER]:                            [[PackageManagementSource]PrivateGallery] Begin registering
'PSPrivateGallery' to source location 'http://localhost:8080' with 'Trusted' policy"
VERBOSE: [SERVER]:                            [[PackageManagementSource]PrivateGallery] Begin invoking
Register-Packagesource PSPrivateGallery
VERBOSE: [SERVER]:                            [[PackageManagementSource]PrivateGallery] Repository details,
Name = 'PSGallery', Location = 'https://www.powershellgallery.com/api/v2/'; IsTrusted = 'True'; IsRegistered = 'True'.
The specified Uri 'http://localhost:8080' for parameter 'Location' is an invalid Web Uri. Please ensure that it meets
the Web Uri requirements.
+ CategoryInfo          : InvalidArgument: (http://localhost:8080:) [], CimException
+ FullyQualifiedErrorId : InvalidWebUri,Add-PackageSource,Microsoft.PowerShell.PackageManagement.Cmdlets.RegisterP
ackageSource
+ PSComputerName        : localhost
VERBOSE: [SERVER]: LCM:  [ End    Set      ]  [[PackageManagementSource]PrivateGallery]  in 31.8600 seconds.
PowerShell DSC resource MSFT_PackageManagementSource  failed to execute Set-TargetResource functionality with error
message: Failed to register the package source PSPrivateGallery. Message:System.Exception: The specified Uri
'http://localhost:8080' for parameter 'Location' is an invalid Web Uri. Please ensure that it meets the Web Uri
requirements.
+ CategoryInfo          : InvalidOperation: (:) [], CimException
+ FullyQualifiedErrorId : ProviderOperationExecutionFailure
+ PSComputerName        : localhost
VERBOSE: [SERVER]: LCM:  [ Start  Resource ]  [[PSGalleryUser]PrivateGalleryUser]
VERBOSE: [SERVER]: LCM:  [ Start  Test     ]  [[PSGalleryUser]PrivateGalleryUser]
VERBOSE: [SERVER]:                            [[PSGalleryUser]PrivateGalleryUser] Get UserSettings for user
'GalleryUser'
VERBOSE: [SERVER]:                            [[PSGalleryUser]PrivateGalleryUser] User 'GalleryUser' does not
exist in database 'PSGallery'
VERBOSE: [SERVER]:                            [[PSGalleryUser]PrivateGalleryUser] User information does not
exist in database 'PSGallery' and Ensure is set to 'Present'
VERBOSE: [SERVER]: LCM:  [ End    Test     ]  [[PSGalleryUser]PrivateGalleryUser]  in 0.7190 seconds.
VERBOSE: [SERVER]: LCM:  [ Start  Set      ]  [[PSGalleryUser]PrivateGalleryUser]
VERBOSE: [SERVER]:                            [[PSGalleryUser]PrivateGalleryUser] Get UserSettings for user
'GalleryUser'
VERBOSE: [SERVER]:                            [[PSGalleryUser]PrivateGalleryUser] User 'GalleryUser' does not
exist in database 'PSGallery'
VERBOSE: [SERVER]:                            [[PSGalleryUser]PrivateGalleryUser] Adding user 'GalleryUser' to
database 'PSGallery'
VERBOSE: [SERVER]:                            [[PSGalleryUser]PrivateGalleryUser] 'Users' table in the database
'PSGallery' on '(LocalDB)\PSGallery' instance is not populated. Populating the table...
VERBOSE: [SERVER]:                            [[PSGalleryUser]PrivateGalleryUser] Setting connection string
VERBOSE: [SERVER]:                            [[PSGalleryUser]PrivateGalleryUser] The 'Users' table in the
database 'PSGallery' on '(LocalDB)\PSGallery' instance has been populated.
VERBOSE: [SERVER]:                            [[PSGalleryUser]PrivateGalleryUser] Setting connection string
VERBOSE: [SERVER]:                            [[PSGalleryUser]PrivateGalleryUser] 'Credentials' table in the
database 'PSGallery' on '(LocalDB)\PSGallery' instance is not populated. Populating the table...
VERBOSE: [SERVER]:                            [[PSGalleryUser]PrivateGalleryUser] Setting connection string
VERBOSE: [SERVER]:                            [[PSGalleryUser]PrivateGalleryUser] The 'Credentials' table in
the database 'PSGallery' on '(LocalDB)\PSGallery' instance has been populated.
VERBOSE: [SERVER]: LCM:  [ End    Set      ]  [[PSGalleryUser]PrivateGalleryUser]  in 0.3280 seconds.
VERBOSE: [SERVER]: LCM:  [ End    Resource ]  [[PSGalleryUser]PrivateGalleryUser]
VERBOSE: [SERVER]: LCM:  [ End    Set      ]
The SendConfigurationApply function did not succeed.
+ CategoryInfo          : NotSpecified: (root/Microsoft/...gurationManager:String) [], CimException
+ FullyQualifiedErrorId : MI RESULT 1
+ PSComputerName        : localhost
VERBOSE: Operation 'Invoke CimMethod' complete.
VERBOSE: Time taken for configuration job to complete is 48.255 seconds
PS C:\PSPrivateGallery\Configuration>`

fixed it and created a pull request.

@davidwallis3101 I will close this issue as resolved.
Please let me know otherwise


Handshake failed.  Error in the certificate.

task diagnostics output:
task 2.5.1
   Platform: Linux

Compiler
    Version: 6.3.0 20170415
       Caps: +stdc +stdc_hosted +LP64 +c8 +i32 +l64 +vp64 +time_t64
 Compliance: C++11

Build Features
      CMake: 3.7.2
    libuuid: libuuid + uuid_unparse_lower
  libgnutls: 3.5.6
 Build type: None

Configuration
       File: /home/nhxjhhh/.taskrc (found), 1979 bytes, mode 100664
       Data: /home/nhxjhhh/.task (found), dir, mode 40755
    Locking: Enabled
         GC: Enabled
     Server: www.freecinc.com:53589
         CA: /home/nhxjhhh/.task/freecinc_1155befe.ca.pem, readable, 3755 bytes
      Trust: strict
Certificate: /home/nhxjhhh/.task/freecinc_1155befe.cert.pem, readable, 3741 bytes
        Key: /home/nhxjhhh/.task/freecinc_1155befe.key.pem, readable, 25367 bytes
    Ciphers: NORMAL
      Creds: FreeCinc/freecinc_1155befe/************************************

Hooks
     System: Enabled
   Location: /home/nhxjhhh/.task/hooks
             (-none-)

Tests
      $TERM: screen-256color (245x72)
       Dups: Scanned 11 tasks for duplicate UUIDs:
             No duplicates found
 Broken ref: Scanned 11 tasks for broken references:
             No broken references found

I follow the instructions from the website to the letter; also, the diagnostic output above doesn't show any errors, all three .pem files are readable, Server and Creds are populated.
I have done this a handful of times on various systems (android, linux, windows) and I get the exact same error each time.
Huge fan of taskwarrior; would like to sync across my devices.
Before I go bang my head into a wall, I figured I would ask for help.  What am I doing wrong?
I have this on a Digital Ocean droplet currently with port 53589 open.

I don't use taskwarrior anymore. You may be able to find help in #taskwarrior on freenode.

Thanks.
I'm curious: what do you use nowadays for task tracking?
And: does that mean the freecinc service is defunct now?

You piqued my curiosity. I just installed taskwarrior 2.5.1 on my machine via apt-get, followed the instructions on freecinc.com to set up new keys, added one task, and performed inital sync. Like I said, "works for me", but people still write in occasionally to say it's not working for them.
And there's still a bot running in the amazon cloud that syncs with freecinc every minute (See source code at https://github.com/jackdesert/freecinc/blob/master/tools/restart_unless_sync.go ). If that sync fails twice in a row, it sends me an email and asks freecinc to restart the taskd service.
And when it goes down for any length of time, I get emails from real people. Which leads me to believe it's still up and running. But if someone wants to help out I'm ready to pass the reigns.

Fwiw, I've been seeing the same issue for the past 24 hours. I'll probably take it as an opportunity to finally setup my own server to host though.

Thanks for the insight into an alternative organizational work flow.
And thanks for verifying everything on the remote end; now I know for sure that I need to investigate my end.  Maybe I have ufw issues.
Thanks again!


[PDI-17831] .csv read from CSV Input step is locked in Carte's JVM

@pentaho/tatooine @pentaho-lmartins
There was much duplicate code on the unit tests, so I pushed some to the base class.
There're 13 unit test classes, someone should look into them as it seems that there're tests that are duplicated... sometime... :-)

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

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

Changed files
  engine/src/main/java/org/pentaho/di/trans/steps/csvinput/CsvInput.java
  engine/src/test/java/org/pentaho/di/trans/steps/csvinput/CsvInputDoubleLineEndTest.java
  engine/src/test/java/org/pentaho/di/trans/steps/csvinput/CsvInputEnclosureTest.java
  engine/src/test/java/org/pentaho/di/trans/steps/csvinput/CsvInputMultiCharDelimiterTest.java
  engine/src/test/java/org/pentaho/di/trans/steps/csvinput/CsvInputRowNumberTest.java
  engine/src/test/java/org/pentaho/di/trans/steps/csvinput/CsvInputTest.java
  engine/src/test/java/org/pentaho/di/trans/steps/csvinput/CsvInputUnicodeTest.java
  engine/src/test/java/org/pentaho/di/trans/steps/csvinput/CsvInputUnitTestBase.java
  engine/src/test/java/org/pentaho/di/trans/steps/csvinput/CsvProcessRowInParallelTest.java
  engine/src/test/java/org/pentaho/di/trans/steps/csvinput/PDI_15270_Test.java

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

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

:warning: Coverage Changes (click to expand)
org.pentaho.di.trans.steps.checksum.CheckSumMeta

Instruction Change: -0.2% :small_red_triangle_down:

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

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

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

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

org.pentaho.di.trans.steps.csvinput.CsvInput

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

org.pentaho.di.trans.steps.csvinput.EmptyPatternMatcher

Complexity Change: -100% :small_red_triangle_down:
Instruction Change: -100% :small_red_triangle_down:
Line Change: -100% :small_red_triangle_down:
Method Change: -100% :small_red_triangle_down:

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

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

org.pentaho.di.trans.steps.ivwloader.IngresVectorwiseLoader

Branch Change: -0.7% :small_red_triangle_down:
Complexity Change: -1.1% :small_red_triangle_down:
Instruction Change: -0.5% :small_red_triangle_down:
Line Change: -0.9% :small_red_triangle_down:

org.pentaho.di.trans.steps.ivwloader.IngresVectorwiseLoader.FifoOpener

Branch Change: -16.7% :small_red_triangle_down:
Complexity Change: -12.5% :small_red_triangle_down:
Instruction Change: -7.1% :small_red_triangle_down:
Line Change: -10.5% :small_red_triangle_down:
Method Change: -20% :small_red_triangle_down:

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

Branch Change: -2.2% :small_red_triangle_down:
Complexity Change: -2.6% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:
Line Change: -0.4% :small_red_triangle_down:

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

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

org.pentaho.di.trans.steps.tableoutput.TableOutputMeta

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


(PUP-10106) Don't require domain proxy exceptions to start with dot

Previously, the no_proxy setting only supported domain exceptions using a
wildcard (*.example.com) or a dotted-domain (.example.com). However, curl and
ruby accept a dotted-domain and a domain suffix (example.com, ample.com), but
not wildcards.
This could lead to strange behavior if puppet executed ruby or curl during an
exec resource, and the no_proxy environment variable was specified as a domain
suffix -- puppet would still use the proxy, while ruby & curl would not.
This commit allows puppet to accept no_proxy environment variables or puppet
settings containing domain suffixes, while retaining support for wildcards and
dotted domains. As a result, it's no longer possible to force puppet to not use
a proxy for a specific host, but not any domains that happen to match that
hostname.

CLA signed by all contributors.

About docs, I did find https://puppet.com/docs/pe/2019.2/configuring_proxies.html#proxying-agent-traffic. It still looks correct given these changes, as it defers to the configuration reference for details, and that will be updated by this PR.

jenkins please test this

I know acceptance tests aren't impacted by this change, I'm just using this PR to remind me how pr testing works and where pr testing lives :-D


IP Address

The IP addresses that show up in the log appear to be the server address.  Is there configuration for this?


Baas smoke tests

Codecov Report

Merging #424 into master will increase coverage by 0.18%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #424      +/-   ##
==========================================
+ Coverage   81.94%   82.13%   +0.18%
==========================================
  Files          81       81
  Lines        2703     2703
  Branches       79       79
==========================================
+ Hits         2215     2220       +5
+ Misses        488      483       -5

Impacted Files
Coverage Δ

...aker/baas/state/InteractionsServiceDiscovery.scala
88.46% <0%> (-3.85%)
:arrow_down:

...e/akka/actor/process_index/ProcessIndexProto.scala
99.48% <0%> (+3.06%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7785587...febe103. Read the comment docs.


React to a recenter request by the headset

Still working on this but adding the logic into our start_xr script so we also react on a recenter request.
At this point in time this results in the player being positioned on the XROrigin point. That may be the right solution in some scenarios but not all. So will need to play a bit more with this.

nice this rounds things up, indeed recenter on xrorigin might fit for the current Version, since malcolm is working on the character centric solution, i dont see why the above shouldnt be merged prior. It would in essence complement the current version before the big breaking changes jump.

The thing that is still missing is that this jumps the player back to the origin point, both when this is desired, and when it is not.
So needs a little bit more experimentation to get this right.

nice this rounds things up, indeed recenter on xrorigin might fit for the current Version, since malcolm is working on the character centric solution, i dont see why the above shouldnt be merged prior. It would in essence complement the current version before the big breaking changes jump.

The thing that is still missing is that this jumps the player back to the origin point, both when this is desired, and when it is not. So needs a little bit more experimentation to get this right.

indeed, right..  i got a somewhat special case to test the above.
a hide system which sets the current origin to a new one. I wonder how well this will work when using the recenter and changing from seated to standing and back


Also skip vendor directory.

This change makes nakedret also skip the vendor directory. In general this sort of static analysis is run on the project itself, not on its dependencies, so I didn't think it warranted being an option, but I can do that instead if you'd rather.

Ah, good point! Nah, I don't think there's really a use case to have it as an option. Thank you! Merged :smile:


publish fails with 'your local code is different than the code tagged on Github'

Elm: 0.19.0
OS: ArchLinux (on virtualbox)
Steps taken:

elm bump
git add -A  && git commit -m "version bump"
git tag 2.0.1
git push origin master --tags
elm publish

Fails with "LOCAL CHANGES" error: "Your local code is different than the code tagged on Github"
There are no local changes and the current, tagged, local commit is the same as the commit tagged on Github.
It recommends "If you are sure everything is in order, you can run git checkout 2.0.1 and publish your code from there".  But that results in the same error.
NB. this is the first 0.19 release of the library if that makes a difference.

What is the output of the following command?
$ git diff-index 2.0.1 --

Closing for now, it could be something specific to my machine, will reopen if needed. Thanks again for your help.


Add C++ to the try page

@Carreau @ellisonbg do you feel like pressing the green button?

Just because it's you.


Still maintained?

Hi, I think this is a really helpful plugin.
Is it still maintained?
The last commit was from 1 year ago...
Thank you

I would be at least insterested in a fix for (or help to myself fix) https://github.com/dboissier/jenkins-control-plugin/issues/167
Because this really makes it unusable for me, because I often need to work on multiple projects in parallel.

Within a week I'll try to prepare some hints for you to help you fix it. Please prepare development environment for the plugin during that time.

Thank you very much.
Is there documentation what's needed to develop this plugin? I have not done IntelliJ plugin development before.

Jetbrains has quite good documentation here: https://www.jetbrains.com/help/idea/plugin-development-guidelines.html
Please take note of any difficulties you'll have during setting up project, it can be used to overcome them or put relevant information in Readme.

Thank you. I've cloned, imported into IntelliJ and gradle build is working fine, however Run/Debug the plugin seems not so easy.
First followed the description of https://stackoverflow.com/questions/18278440/how-to-import-and-run-existing-plugins-from-intellij-community-edition-repo
how to get the run config enabled.
But after that there is no guidance on how to do it:
http://www.jetbrains.org/intellij/sdk/docs/basics/getting_started/running_and_debugging_a_plugin.html
When I press run or debug ("main" module) I end up with a new IntelliJ window, not having the plugin installed/enabled. Not sure what I need to do there.
I could maybe continue with blindly fixing the code with your help (or change, deploy, validate cycles) however there should be a better way, isn't it?

it is possible to add an additional maintainer or contributer with merge rights?
So this project will be active.
@dboissier Can you grant access

Hey guys,
Excellent 😀😀
Available to help to fix bugs and improve it 👍

Good to know. Thanks for help.
You can look for an issue and solve it.
Currently i work on multibranch feature and 2020.1 support

@MCMicS I look at the project.
Multibranch doesn't work for 2019.2 version. Only for latest 2019.3 version ?
Which one need to be solved asap ? Possible to discuss on discord, gitter (already available or not) ?

Gitter is available.
Not sure if 2018 should supported. Currently only 2019+ is developed.
May be we do an 2018 version if needed


Migration import changes

Fix migration zip imported NPE
Disable typeDef processor, import audits writes (specific to import, not ES audits)
Migration import: Enable listeners
Conditionally disable entity notification
Conditionally disable entity audits
Conditionally disable stats listener
Fixed __index issue
Support setting username with property while migration

Test once on yatin.atlan.dev or beta before merging


Add warnings for env_file entries not copied

As 'env_file' entries are not taken in account,
we warn the user to copy that and fix it's
compose file.
- What I did
Add a warning for each env_file entry on each service
- How I did it
By checking the env_file block for each service entry in docker app init
- How to verify it
Create a docker-compose.yml file with:
version: '3.7'
services:
  front:
    image: "nginx"
    env_file:
     - "myenv.env1"
     - "myenv.env2"

Run:
docker app init --compose-file docker-compose.yml myapp

- Description for the changelog
Add warnings for env_file entries not copied
- A picture of a cute animal (not mandatory but encouraged)

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "add-env_file-warning" git@github.com:ulyssessouza/app.git somewhere
$ cd somewhere
$ git rebase -i HEAD~842354452128
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.


services/horizon: Update txsub queue to account for new CAP-21 preconditions

Fixes #4283

I have replaced the heap with a sorted slice.
I could keep a linked list (or a second slice) sorted by the minSeq instead of iterating the full slice every time but I don't think it's worth it.

And, after @tamirms 's suggestion, I replaced it by an unsorted slice which we sort as needed on the fly.


Format option to drop zero remainder

It would be nice if there was a format option to drop a zero remainder, i.e.
30 > ($0,0.00?) > $30
30.54 > ($0,0.00?) > $30.54

'$0,0[.]00' already does this ;)


no feedback on tldr --update progress

Downloading https://tldr.sh/assets/tldr.zip takes 4 minutes and the tool provides no feedback about it.

The archive is ca. 12 MB, even with really slow internet this shouldn't take more than 30 seconds. The library we use to make the requests does not provide any progress indication, as far as I can tell. So I am going to close here, as it would be a lot of work for little value to most users.
Does a second update also take this long? In case you just have a slow Internet connection, I am working to download a part of the archive that matches the configured languages, so this might speed up the download


OKE module datasources fails to get latest_images

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version and Provider Version
Terraform v0.14.2

provider registry.terraform.io/hashicorp/helm v1.3.2
provider registry.terraform.io/hashicorp/kubernetes v1.13.3
provider registry.terraform.io/hashicorp/local v2.0.0
provider registry.terraform.io/hashicorp/null v3.0.0
provider registry.terraform.io/hashicorp/oci v4.5.0
provider registry.terraform.io/hashicorp/template v2.2.0

Affected Resource(s)
modules/oke/modules/oke/datasources.tf line 9, in data "oci_core_images" "latest_images"
Terraform Configuration Files
variable "tenancy_ocid" {}
variable "user_ocid" {}
variable "fingerprint" {}
variable "private_key_path" {}
variable "parent_compartment_ocid" {}
variable "region" {}

variable "ssh_private_key_path" {}
variable "ssh_public_key_path" {}

terraform {
  required_providers {
    oci = {
      source  = "hashicorp/oci"
      version = "~> 4.5.0"
    }
  }
}

provider "oci" {
  tenancy_ocid         = var.tenancy_ocid
  user_ocid            = var.user_ocid
  fingerprint          = var.fingerprint
  private_key_path     = var.private_key_path
  region               = var.region
}

resource "oci_identity_compartment" "compartment" {
  name           = "testcompartment"
  description    = "Test Compartment"
  compartment_id = var.parent_compartment_ocid
}

module "oke" {
  # Settings for configuring this remote module
  source                  = "oracle-terraform-modules/oke/oci"
  version                 = "2.3.3"

  # Identity and access
  api_fingerprint         = var.fingerprint
  api_private_key_path    = var.private_key_path
  compartment_id          = oci_identity_compartment.compartment.id
  tenancy_id              = var.tenancy_ocid
  user_id                 = var.user_ocid

  # SSH Keys
  ssh_private_key_path    = var.ssh_private_key_path
  ssh_public_key_path     = var.ssh_public_key_path

  # General OCI
  label_prefix            = "test"
  region                  = var.region

  # OCI Networking
  vcn_cidr                = "<IP_ADDRESS>/16"
  vcn_dns_label           = "test"
  vcn_name                = "test-vcn"

  # Bastion Host
  bastion_access                = "ANYWHERE"
  bastion_image_id              = "Autonomous"
  bastion_enabled               = false
  bastion_notification_enabled  = true
  bastion_notification_endpoint =<EMAIL_ADDRESS>  bastion_notification_protocol = "EMAIL"
  bastion_notification_topic    = "bastion"
  bastion_package_upgrade       = true
  bastion_shape                 = "VM.Standard.E2.1"
  bastion_timezone              = "America/Los_Angeles"

  # Admin Host
  operator_enabled               = false
  operator_image_id              = "Oracle"
  operator_instance_principal    = true
  operator_notification_enabled  = false
  operator_notification_endpoint =<EMAIL_ADDRESS>  operator_notification_protocol = "EMAIL"
  operator_notification_topic    = "operator"
  operator_package_upgrade       = true
  operator_shape                 = "VM.Standard.E2.1" #var.operator_shape
  operator_timezone              = "America/Los_Angeles" #var.operator_timezone

  # Availability Domains
domain
  availability_domains = {
    bastion  = 1
    operator = 1
  }

  # Tagging
  tags = {
    # vcn, bastion and operator tags are required. Add more tags in each as desired
    vcn = {
      environment = "dev"
    }
    bastion = {
      environment = "dev"
      role        = "bastion"
    }
    operator = {
      environment = "dev"
      role        = "operator"
    }
  }

  # OKE
  admission_controller_options = {
    PodSecurityPolicy = true
  }
  allow_node_port_access  = false
  allow_worker_ssh_access = true
  cluster_name            = "k8s1"
  check_node_active       = "one"
  dashboard_enabled       = false
  kubernetes_version      = "v1.18.10"
  node_pools = {
    np1 = {
      shape               = "VM.Standard.E3.Flex",
      ocpus               = 1,
      memory              = 32,
      node_pool_size      = 1,
      boot_volume_size    = 50
    }
  }
  node_pool_image_id      = "ocid1.image.oc1.iad.aaaaaaaapulaxjedwo2y3koeli6zq6evql6rropyxpni3wu44i2rbffgxgza"
  worker_mode             = "private"

  # OKE Load Balancers
balancers
  lb_subnet_type          = "public"
  preferred_lb_subnets    = "public"
//  public_lb_ports         = [443, 8883]
  waf_enabled             = false

  # OCIR
//  secret_id               = "" # TODO Add this to vault!!
//  email_address           =<EMAIL_ADDRESS>//  tenancy_name            = "mytenancy"
//  username                = "myuser"

  # Calico
  calico_version = "3.12"
  calico_enabled = false

  # Kubernetes Metrics Server
  metricserver_enabled = false

  # KMS Integration
  use_encryption = false
  existing_key_id = ""

  # Service Account
  create_service_account               = false
  service_account_name                 = "myaccountname"
  service_account_namespace            = "myaccountnamespace"
  service_account_cluster_role_binding = "cicd"
}

Debug Output
https://gist.github.com/rbair23/5e0d7e9c8c6a5dee035ea8c34f05d1f9
Expected Behavior
Clean run of Terraform Plan / Apply
Actual Behavior
Fails with error
Steps to Reproduce

terraform plan

I thought maybe there was an incompatible change on the OCI terraform module, so I tried a few different versions including 3.88.0 and 4.5.0 and 4.6.0, but they all fail the same way.

If I comment out node_pools, then it works.

It looks like this may already be fixed on the main branch:
data "oci_core_images" "latest_images" {
  for_each                 = var.node_pools.node_pools
  compartment_id           = var.compartment_id
  operating_system         = var.node_pools.node_pool_os
  operating_system_version = var.node_pools.node_pool_os_version
  shape                    = lookup(each.value,"shape","VM.Standard.E3.Flex")
  sort_by                  = "TIMECREATED"
}

@rbair23 The terraform.tfvars format is not correct for the version you are using .It has to be of the format  node_pools = {
np1 = ["VM.Standard.E2.2", 1]
np2 = ["VM.Standard2.8", 2]
np3 = ["VM.Standard.E2.2", 1]
np4 = ["VM.Standard.E2.2", 4]
}. The one you are using is the latest one . node_pools = {
np1 = {
shape               = "VM.Standard.E3.Flex",
ocpus               = 1,
memory              = 32,
node_pool_size      = 1,
boot_volume_size    = 50
}
}

Closing this issue. Please reopen if the problem is not fixed after changing the terraform.tfvars


FPS Starter Project can't connect to a deployment because can't find a port in a logfile on MacOS

Description
FPS Starter Project can't connect to a deployment because it can't find a port in a logfile on MacOS.
I found in the code that the log file is being searched like this:
case RuntimePlatform.OSXPlayer:
                    // On MacOS it always goes in the Unity folder regardless of what companyName and productName are set to.
                    logPath = Path.Combine(Environment.GetFolderPath(Environment.SpecialFolder.UserProfile), "Library", "Logs", "Unity", "Player.log");
                    break;

Which is:

/Users/username/Library/Logs/Unity/Player.log

However Launcher opens a completely different directory if you click on a "Open Log File" button:

/Users/username/Library/Logs/Improbable/FPS Starter Project/Player.log"

Expected behaviour

GDK should use the same directory for a log file as SpatialOS Launcher to find a correct port.
Current behaviour
GDK uses wrong directory for a log file and couldn't find a port.
Possible solution
I couldn't find a launcher code, is it open source?
Steps to reproduce
Follow https://docs.improbable.io/unity/alpha/projects/fps/get-started/get-started on macOS Mojave
Environment
I was trying to start with FPS Starter Project on macOS.
Unity 2019.2.6f1
macOS Mojave 10.14.6 (18G87

Hey @v1ctor thanks for the report!
As the comment in the source may suggest, this was abnormal when we originally wrote this feature. Its possible in the meantime Unity has fixed up the directory to align with the other platforms. I'll raise a bug internally to check it out! 😄
Did this prevent you from connecting to the deployment?
As that is unexpected behaviour, this port is just used for debugging purposes not for connecting to the SpatialOS deployment. It should log the error, but that's all:
#if !UNITY_EDITOR && DEVELOPMENT_BUILD && !UNITY_ANDROID && !UNITY_IPHONE
            try
            {
                var port = GetPlayerConnectionPort();
                Worker.SendLogMessage(LogLevel.Info, $"Unity PlayerConnection port: {port}.", Worker.WorkerId, null);
            }
            catch (Exception e)
            {
                logger.HandleLog(LogType.Exception, new LogEvent("Could not find the Unity PlayerConnection port.").WithException(e));
            }
#endif

Did this prevent you from connecting to the deployment?

Yes I couldn't connect to the deployment.
I'm getting this exception:
Exception: Could n

ot find PlayerConnection port in logfile
at Improbable.Gdk.Core.WorkerConnector.ExtractPlayerConnectionPort (System.String fileContents) [0x0005d] in /Users/bool/gamedev/examples/gdk-for-unity-fps-starter-project/workers/unity/Library/PackageCache/io.improbable.gdk.core@0.3.1/Worker/WorkerConnector.cs:324
at Improbable.Gdk.Core.WorkerConnector.GetPlayerConnectionPort () [0x00125] in /Users/bool/gamedev/examples/gdk-for-unity-fps-starter-project/workers/unity/Library/PackageCache/io.improbable.gdk.core@0.3.1/Worker/WorkerConnector.cs:300
at Improbable.Gdk.Core.WorkerConnector+d__9.MoveNext () [0x002f1] in /Users/bool/gamedev/examples/gdk-for-unity-fps-starter-project/workers/unity/Library/PackageCache/io.improbable.gdk.core@0.3.1/Worker/WorkerConnector.cs:138
UnityEngine.DebugLogHandler:Internal_LogException(Exception, Object)
UnityEngine.DebugLogHandler:LogException(Exception, Object)
UnityEngine.Logger:LogException(Exception, Object)
Improbable.Gdk.Core.ForwardingDispatcher:HandleLog(LogType, LogEvent) (at /Users/bool/gamedev/examples/gdk-for-unity-fps-starter-project/workers/unity/Library/PackageCache/io.improbable.gdk.core@0.3.1/Logging/ForwardingDispatcher.cs:76)
Improbable.Gdk.Core.d__9:MoveNext() (at /Users/bool/gamedev/examples/gdk-for-unity-fps-starter-project/workers/unity/Library/PackageCache/io.improbable.gdk.core@0.3.1/Worker/WorkerConnector.cs:143)
System.Runtime.CompilerServices.MoveNextRunner:InvokeMoveNext(Object)
System.Threading.ExecutionContext:RunInternal(ExecutionContext, ContextCallback, Object, Boolean)
System.Threading.ExecutionContext:Run(ExecutionContext, ContextCallback, Object, Boolean)
System.Runtime.CompilerServices.MoveNextRunner:Run()
System.Threading.Tasks.AwaitTaskContinuation:InvokeAction(Object)
System.Threading.Tasks.AwaitTaskContinuation:RunCallback(ContextCallback, Object, Task&)
System.Threading.Tasks.SynchronizationContextAwaitTaskContinuation:Run(Task, Boolean)
System.Threading.Tasks.Task:FinishContinuations()
System.Threading.Tasks.Task:FinishStageThree()
System.Threading.Tasks.Task1:TrySetResult(WorkerInWorld) System.Runtime.CompilerServices.AsyncTaskMethodBuilder1:SetResult(WorkerInWorld)
Improbable.Gdk.Core.d__12:MoveNext() (at /Users/bool/gamedev/examples/gdk-for-unity-fps-starter-project/workers/unity/Library/PackageCache/io.improbable.gdk.core@0.3.1/Worker/WorkerConnector.cs:203)
System.Runtime.CompilerServices.MoveNextRunner:InvokeMoveNext(Object)
System.Threading.ExecutionContext:RunInternal(ExecutionContext, ContextCallback, Object, Boolean)
System.Threading.ExecutionContext:Run(ExecutionContext, ContextCallback, Object, Boolean)
System.Runtime.CompilerServices.MoveNextRunner:Run()
System.Threading.Tasks.AwaitTaskContinuation:InvokeAction(Object)
System.Threading.Tasks.AwaitTaskContinuation:RunCallback(ContextCallback, Object, Task&)
System.Threading.Tasks.SynchronizationContextAwaitTaskContinuation:Run(Task, Boolean)
System.Threading.Tasks.Task:FinishContinuations()
System.Threading.Tasks.Task:FinishStageThree()
System.Threading.Tasks.Task1:TrySetResult(WorkerInWorld) System.Runtime.CompilerServices.AsyncTaskMethodBuilder1:SetResult(WorkerInWorld)
Improbable.Gdk.Core.d__10:MoveNext() (at /Users/bool/gamedev/examples/gdk-for-unity-fps-starter-project/workers/unity/Library/PackageCache/io.improbable.gdk.core@0.3.1/Worker/WorkerInWorld.cs:65)
System.Runtime.CompilerServices.MoveNextRunner:InvokeMoveNext(Object)
System.Threading.ExecutionContext:RunInternal(ExecutionContext, ContextCallback, Object, Boolean)
System.Threading.ExecutionContext:Run(ExecutionContext, ContextCallback, Object, Boolean)
System.Runtime.CompilerServices.MoveNextRunner:Run()
System.Threading.Tasks.AwaitTaskContinuation:InvokeAction(Object)
System.Threading.Tasks.AwaitTaskContinuation:RunCallback(ContextCallback, Object, Task&)
System.Threading.Tasks.SynchronizationContextAwaitTaskContinuation:Run(Task, Boolean)
System.Threading.Tasks.Task:FinishContinuations()
System.Threading.Tasks.Task:FinishStageThree()
System.Threading.Tasks.Task1:TrySetResult(IConnectionHandler) System.Runtime.CompilerServices.AsyncTaskMethodBuilder1:SetResult(IConnectionHandler)
Improbable.Gdk.Core.d__11:MoveNext() (at /Users/bool/gamedev/examples/gdk-for-unity-fps-starter-project/workers/unity/Library/PackageCache/io.improbable.gdk.core@0.3.1/Worker/ConnectionHandlers/SpatialOSConnectionHandlerBuilder.cs:90)
System.Runtime.CompilerServices.MoveNextRunner:InvokeMoveNext(Object)
System.Threading.ExecutionContext:RunInternal(ExecutionContext, ContextCallback, Object, Boolean)
System.Threading.ExecutionContext:Run(ExecutionContext, ContextCallback, Object, Boolean)
System.Runtime.CompilerServices.MoveNextRunner:Run()
System.Threading.Tasks.<>c:<.cctor>b__7_0(Object)
UnityEngine.WorkRequest:Invoke() (at /Users/builduser/buildslave/unity/build/Runtime/Export/Scripting/UnitySynchronizationContext.cs:114)
UnityEngine.UnitySynchronizationContext:Exec() (at /Users/builduser/buildslave/unity/build/Runtime/Export/Scripting/UnitySynchronizationContext.cs:74)
UnityEngine.UnitySynchronizationContext:ExecuteTasks() (at /Users/builduser/buildslave/unity/build/Runtime/Export/Scripting/UnitySynchronizationContext.cs:94)
(Filename<EMAIL_ADDRESS>Line: 324)

However in the same file above there is a line which mach a regex:

PlayerConnection initialized network socket : <IP_ADDRESS> 55333

Right, but the exception is caught and logged (what you see in the snippet you posted above), so I'm unsure why (or if) that would cause the connection failure.
Do you see any other errors in the output logs?

@jamiebrynes7 Oh, I think you're right, I've confused the cause.
Here is logs when launcher cannot connect to the deployment:

[UnityClient] Unable to create player after 1 attempt.
'WorkerType': 'UnityClient'
UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
UnityEngine.DebugLogHandler:LogFormat(LogType, Object, String, Object[])
UnityEngine.Logger:Log(LogType, Object, Object)
Improbable.Gdk.Core.ForwardingDispatcher:HandleLog(LogType, LogEvent) (at /Users/bool/gamedev/examples/gdk-for-unity-fps-starter-project/workers/unity/Library/PackageCache/io.improbable.gdk.core@0.3.1/Logging/ForwardingDispatcher.cs:80)
Improbable.Gdk.PlayerLifecycle.SendCreatePlayerRequestSystem:RetryCreatePlayerRequest() (at /Users/bool/gamedev/examples/gdk-for-unity-fps-starter-project/workers/unity/Library/PackageCache/io.improbable.gdk.playerlifecycle@0.3.1/Systems/PlayerCreation/SendCreatePlayerRequestSystem.cs:164)
Improbable.Gdk.PlayerLifecycle.SendCreatePlayerRequestSystem:HandlePlayerCreation() (at /Users/bool/gamedev/examples/gdk-for-unity-fps-starter-project/workers/unity/Library/PackageCache/io.improbable.gdk.playerlifecycle@0.3.1/Systems/PlayerCreation/SendCreatePlayerRequestSystem.cs:206)
Improbable.Gdk.PlayerLifecycle.SendCreatePlayerRequestSystem:OnUpdate() (at /Users/bool/gamedev/examples/gdk-for-unity-fps-starter-project/workers/unity/Library/PackageCache/io.improbable.gdk.playerlifecycle@0.3.1/Systems/PlayerCreation/SendCreatePlayerRequestSystem.cs:224)
Unity.Entities.ComponentSystem:InternalUpdate() (at /Users/bool/gamedev/examples/gdk-for-unity-fps-starter-project/workers/unity/Library/PackageCache/com.unity.entities@0.1.1-preview/Unity.Entities/ComponentSystem.cs:800)
Unity.Entities.ComponentSystemBase:Update() (at /Users/bool/gamedev/examples/gdk-for-unity-fps-starter-project/workers/unity/Library/PackageCache/com.unity.entities@0.1.1-preview/Unity.Entities/ComponentSystem.cs:284)
Unity.Entities.ComponentSystemGroup:OnUpdate() (at /Users/bool/gamedev/examples/gdk-for-unity-fps-starter-project/workers/unity/Library/PackageCache/com.unity.entities@0.1.1-preview/Unity.Entities/ComponentSystemGroup.cs:602)
Unity.Entities.ComponentSystem:InternalUpdate() (at /Users/bool/gamedev/examples/gdk-for-unity-fps-starter-project/workers/unity/Library/PackageCache/com.unity.entities@0.1.1-preview/Unity.Entities/ComponentSystem.cs:800)
Unity.Entities.ComponentSystemBase:Update() (at /Users/bool/gamedev/examples/gdk-for-unity-fps-starter-project/workers/unity/Library/PackageCache/com.unity.entities@0.1.1-preview/Unity.Entities/ComponentSystem.cs:284)
Unity.Entities.ComponentSystemGroup:OnUpdate() (at /Users/bool/gamedev/examples/gdk-for-unity-fps-starter-project/workers/unity/Library/PackageCache/com.unity.entities@0.1.1-preview/Unity.Entities/ComponentSystemGroup.cs:602)
Unity.Entities.ComponentSystem:InternalUpdate() (at /Users/bool/gamedev/examples/gdk-for-unity-fps-starter-project/workers/unity/Library/PackageCache/com.unity.entities@0.1.1-preview/Unity.Entities/ComponentSystem.cs:800)
Unity.Entities.ComponentSystemBase:Update() (at /Users/bool/gamedev/examples/gdk-for-unity-fps-starter-project/workers/unity/Library/PackageCache/com.unity.entities@0.1.1-preview/Unity.Entities/ComponentSystem.cs:284)
Unity.Entities.DummyDelegateWrapper:TriggerUpdate() (at /Users/bool/gamedev/examples/gdk-for-unity-fps-starter-project/workers/unity/Library/PackageCache/com.unity.entities@0.1.1-preview/Unity.Entities/ScriptBehaviourUpdateOrder.cs:144)
(Filename<EMAIL_ADDRESS>Line: 80)

Okay, that's more like it 😅. So the client-worker connected successfully, but the CreatePlayer request to the UnityGameLogic worker failed for one reason or another. That means that either:

There is no UnityGameLogic worker to handle the create player request
The UnityGameLogic worker failed to create the player for your client

Could you check the deployment logs to check for:

The UnityGameLogic worker connecting successfully to the deployment
Any error logs relating to the UnityGameLogic worker failing to create the player.

TBH I don't see a UnityGameLogic worker anywhere, where I can find it?

You should see a message in the Logs for your deployment similar to:
Handling connection request for worker of type UnityGameLogic trying to log in: UnityGameLogic0

and then:
The worker UnityGameLogic0 connected to SpatialOS successfully.

If it connected successfully

Ok, I found the the number of live workers is 0 for all workers. I'll try to restart deployment now to see if it helps.
It strange I didn't see anything related to workers in the Get Started docs.

The Get Started docs gloss over it a bit to get you into game ASAP. You can see the worker configuration in the load balancing section of the launch configuration (for example - https://github.com/spatialos/gdk-for-unity-fps-starter-project/blob/master/cloud_launch_large.json#L16).
Provided you have built the workers (especially the UnityGameLogic@Linux worker), it should work out of the box. You can sanity check this by looking at the zips in the ${SPATIAL_PROJECT_ROOT}/build/assembly/workers directory

I think that I found the problem:

Could not download<EMAIL_ADDRESS>for Worker(UnityGameLogic). The Runtime will be unable to start workers of this type.: rpc error: code = NotFound desc = failed to get<EMAIL_ADDRESS>for assembly(beta_may_nuts_261_1126_1142), project(beta_may_nuts_261): failed to get<EMAIL_ADDRESS>for assembly(beta_may_nuts_261_1126_1142), project(beta_may_nuts_261)
error
failed to get<EMAIL_ADDRESS>for assembly(beta_may_nuts_261_1126_1142), project(beta_may_nuts_261)

And of course there is no such an artifact in the assembly. However, it's not clear how to cross compile for Linux on macOS, or how to configure deployment to use mac from the docs.

Thank for your help @jamiebrynes7 !

I don't know if you'd like to do anything with the port error though. Do you want me to create another issue?

I believe it will work now.

Awesome! 🎉 Let me know if you run into any more problems!

I don't know if you'd like to do anything with the port error though. Do you want me to create another issue?

We've made an internal bug ticket for this, lets leave this issue open to track it publicly. 😄

This was fixed in #1232 and released in v0.3.2!


Channels

Allow image params to use an arbitrary amount of channels, then ensure that image_shape uses that correctly.

I am going to give this a try. If there are some critical places to begin or some remarks to share It would be perfect

@BadrYoubiIdrissi thank so much for your willingness! I imagine extending the parameterization itself (start at lucid.optvis.params.images) will be pretty straightforward, I'm more concerned about e.g. lucid.optvis.objectives operating on such a parameterization. LMK if you run into a situation where there's no clearly correct answer, or I can help with anything else!

@ludwigschubert The decorrelation matrix seems to be infered from Imagenet, should the code provide a way for the user to specify a decorrelation matrix if the number of channels is different from 3?


[FIX] Skin changer request

@danielkrupinski if you could, can you work on making it to where skins from the skin changer don't show when you switch to a bot? (knife & gloves too)

Also different knife and glove settings for each team

Also different knife and glove settings for each team

@danielkrupinski ^^^

@danielkrupinski if you could, can you work on making it to where skins from the skin changer don't show when you switch to a bot? (knife & gloves too)

That's how the game is designed.


Studio hangs trying to render line-geometry-transform: skewX(90);

I have no idea what line-geometry-transform: skewX(90); will actually look like, I was just plugging in different values to see what it does. I had to remove the line in the .mss file so Studio could work again.

@cleversprocket - thanks a ton for the report. That should definitely not hang. I've replicated the problem locally and will be fixing shortly.

@springmeyer @cleversprocket - this is fixed in mapnik-core :
https://github.com/mapnik/mapnik/commit/6d6cb15b4547539152c488fb7bfe7f9506c48d9a


kube-dns goes into CrashLoopBackOff

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
Rancher 2.x on AWS.
Set up a Custom rancher cluster, by selecting Amazon as the cloud provider.
Result:
kubectl get po -n kube-system -o wide|grep kube-dns
kube-dns-6db5b57f97-wxzls                 1/3     CrashLoopBackOff   25         28m
Other details that may be helpful:
The only error i can find in the logs is in sidecar logs:
W0430 07:00:45.832893       1 server.go:64] Error getting metrics from dnsmasq: read udp <IP_ADDRESS>:54210-><IP_ADDRESS>:53: read: connection refused
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI):
v2.1.7
Installation option (single install/HA):
single install
AWS with three EC2 nodes. Selecting custom type cluster and cloud provider as Amazon.
We have followed the pre-reqs required for this kind of setup - AWS role and labels.

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported):
Machine type (cloud/VM/metal) and specifications (CPU/memory):
Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.0", GitCommit:"641856db18352033a0d96dbc99153fa3b27298e5", GitTreeState:"clean", BuildDate:"2019-03-25T15:53:57Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.4", GitCommit:"c27b913fddd1a6c480c229191a087698aa92f0b1", GitTreeState:"clean", BuildDate:"2019-02-28T13:30:26Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}

Docker version (use docker version):

18.09.3

There are troubleshooting docs that can be used to retrieve the root cause here: https://rancher.com/docs/rancher/v2.x/en/troubleshooting/
Also, please supply what AMI you are using.

Hi Superseb,
We are using a Centos 7 AMI that we have customized.
Here is the output from the troubleshooting:
$ kubectl create -f ds-overlaytest.yml
daemonset.apps/overlaytest created
$ kubectl rollout status ds/overlaytest -w
daemon set "overlaytest" successfully rolled out
$ echo "=> Start network overlay test"; kubectl get pods -l name=overlaytest -o jsonpath='{range<EMAIL_ADDRESS><EMAIL_ADDRESS>| while read spod shost; do kubectl ge
t pods -l name=overlaytest -o jsonpath='{range<EMAIL_ADDRESS><EMAIL_ADDRESS>| while read tip thost; do kubectl --request-timeout='10s' exec $spod -- /bin/sh -c "ping -c2 $tip > /dev/null 2>&1"; RC=$?; if [
$RC -ne 0 ]; then echo $shost cannot reach $thost; fi; done; done; echo "=> End network overlay test"
=> Start network overlay test
=> End network overlay test
$ kubectl -n kube-system get pods -l k8s-app=kube-dns
NAME                        READY   STATUS             RESTARTS   AGE
kube-dns-6db5b57f97-kf4h7   1/3     CrashLoopBackOff   37         47m
kube-dns-9c6c5558b-zdzcn    1/3     CrashLoopBackOff   38         48m
$ kubectl -n kube-system get svc -l k8s-app=kube-dns
NAME       TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)         AGE
kube-dns   ClusterIP   <IP_ADDRESS>           53/UDP,53/TCP   18d
$ kubectl run -it --rm --restart=Never busybox --image=busybox:1.28 -- nslookup kubernetes.default
If you don't see a command prompt, try pressing enter.
Address 1: <IP_ADDRESS>
nslookup: can't resolve 'kubernetes.default'
pod "busybox" deleted
pod default/busybox terminated (Error)
$ kubectl run -it --rm --restart=Never busybox --image=busybox:1.28 -- nslookup www.google.com
If you don't see a command prompt, try pressing enter.
Address 1: <IP_ADDRESS>
nslookup: can't resolve 'www.google.com'
pod "busybox" deleted
pod default/busybox terminated (Error)
$ kubectl create -f ds-dnstest.yml
daemonset.apps/dnstest created
$ kubectl rollout status ds/dnstest -w
daemon set "dnstest" successfully rolled out
$ export DOMAIN=www.google.com; echo "=> Start DNS resolve test"; kubectl get pods -l name=dnstest --no-headers -o custom-columns=NAME:.metadata.name,HOSTIP:.status.hostIP | while read pod host; do
kubectl exec $pod -- /bin/sh -c "nslookup $DOMAIN > /dev/null 2>&1"; RC=$?; if [ $RC -ne 0 ]; then echo $host cannot resolve $DOMAIN; fi; done; echo "=> End DNS resolve test"
=> Start DNS resolve test
command terminated with exit code 1
<IP_ADDRESS> cannot resolve www.google.com
command terminated with exit code 1
<IP_ADDRESS> cannot resolve www.google.com
command terminated with exit code 1
<IP_ADDRESS> cannot resolve www.google.com
=> End DNS resolve test
$ kubectl delete ds/dnstest
daemonset.extensions "dnstest" deleted
$ kubectl -n kube-system get pods -l k8s-app=kube-dns --no-headers -o custom-columns=NAME:.metadata.name,HOSTIP:.status.hostIP | while read pod host; do echo "Pod ${pod} on host ${host}"; kubectl -
n kube-system exec $pod -c kubedns cat /etc/resolv.conf; done
Pod kube-dns-6db5b57f97-kf4h7 on host <IP_ADDRESS>
error: unable to upgrade connection: container not found ("kubedns")
Pod kube-dns-9c6c5558b-zdzcn on host <IP_ADDRESS>
error: unable to upgrade connection: container not found ("kubedns")
$ kubectl -n kube-system get configmap kube-dns -o go-template='{{range $key, $value := .data}}{{ $key }}{{":"}}{{ $value }}{{"\n"}}{{end}}'
Error from server (NotFound): configmaps "kube-dns" not found
Regards,

Sorry missed the CrashLoopBackOff state. Can you share output of kubectl -n kube-system describe pods -l k8s-app=kube-dns?

Here is the requested output:
$ kubectl -n kube-system describe pods -l k8s-app=kube-dns
Name:               kube-dns-6db5b57f97-kf4h7
Namespace:          kube-system
Priority:           0
PriorityClassName:
Node:               ip-10-100-138-42.ap-southeast-2.compute.internal/<IP_ADDRESS>
Start Time:         Wed, 01 May 2019 15:31:10 +1000
Labels:             k8s-app=kube-dns
pod-template-hash=6db5b57f97
Annotations:        cattle.io/timestamp: 2019-04-30T05:42:51Z
cni.projectcalico.org/podIP: <IP_ADDRESS>/32
field.cattle.io/ports:
[[{"containerPort":10053,"dnsName":"kube-dns-","name":"dns-local","protocol":"UDP","sourcePort":0},{"containerPort":10053,"dnsName":"kube-...
scheduler.alpha.kubernetes.io/critical-pod:
Status:             Running
IP:                 <IP_ADDRESS>
Controlled By:      ReplicaSet/kube-dns-6db5b57f97
Containers:
kubedns:
Container ID:  docker://eb97b3797a171982f64c8cb84b7785c322857b7bdc1195c603d552c1a8036e32
Image:         rancher/k8s-dns-kube-dns-amd64:1.15.0
Image ID:      docker-pullable://rancher/k8s-dns-kube-dns-amd64@sha256:e7f673b2c5ccd047c48b4eecd5452b2db1b9454daf07b23068ad239f98afaa29
Ports:         10053/UDP, 10053/TCP, 10055/TCP
Host Ports:    0/UDP, 0/TCP, 0/TCP
Args:
--domain=cluster.local.
--dns-port=10053
--config-dir=/kube-dns-config
--v=2
State:          Running
Started:      Thu, 02 May 2019 09:24:29 +1000
Last State:     Terminated
Reason:       Error
Exit Code:    137
Started:      Thu, 02 May 2019 09:16:59 +1000
Finished:     Thu, 02 May 2019 09:19:18 +1000
Ready:          False
Restart Count:  78
Limits:
memory:  170Mi
Requests:
cpu:      100m
memory:   70Mi
Liveness:   http-get http://:10054/healthcheck/kubedns delay=60s timeout=5s period=10s #success=1 #failure=5
Readiness:  http-get http://:8081/readiness delay=3s timeout=5s period=10s #success=1 #failure=3
Environment:
PROMETHEUS_PORT:  10055
Mounts:
/kube-dns-config from kube-dns-config (rw)
/var/run/secrets/kubernetes.io/serviceaccount from kube-dns-token-vmhxf (ro)
dnsmasq:
Container ID:  docker://5bd8e14d87c78699333f0d27d9ae8c7e783787eb1ba3b9a5e871b267b393b4b3
Image:         rancher/k8s-dns-dnsmasq-nanny-amd64:1.15.0
Image ID:      docker-pullable://rancher/k8s-dns-dnsmasq-nanny-amd64@sha256:ed10a8d06cde253474a7e9cfa65bbdf5f8f0c6a377f66c033e623ff63e9d5edf
Ports:         53/UDP, 53/TCP
Host Ports:    0/UDP, 0/TCP
Args:
-v=2
-logtostderr
-configDir=/etc/k8s/dns/dnsmasq-nanny
-restartDnsmasq=true
--
-k
--cache-size=1000
--log-facility=-
--server=/cluster.local/<IP_ADDRESS>#10053
--server=/in-addr.arpa/<IP_ADDRESS>#10053
--server=/ip6.arpa/<IP_ADDRESS>#10053
State:          Running
Started:      Thu, 02 May 2019 09:24:59 +1000
Last State:     Terminated
Reason:       Error
Exit Code:    137
Started:      Thu, 02 May 2019 09:17:30 +1000
Finished:     Thu, 02 May 2019 09:19:50 +1000
Ready:          True
Restart Count:  78
Requests:
cpu:        150m
memory:     20Mi
Liveness:     http-get http://:10054/healthcheck/dnsmasq delay=60s timeout=5s period=10s #success=1 #failure=5
Environment:
Mounts:
/etc/k8s/dns/dnsmasq-nanny from kube-dns-config (rw)
/var/run/secrets/kubernetes.io/serviceaccount from kube-dns-token-vmhxf (ro)
sidecar:
Container ID:  docker://d112131ebfede8bdb1b2a407fd7705c87b09da161b192ca1204d19ce28724e13
Image:         rancher/k8s-dns-sidecar-amd64:1.15.0
Image ID:      docker-pullable://rancher/k8s-dns-sidecar-amd64@sha256:fbaf5cf6218942898cb171a34dca9a1dd9e5dcf15c8f18ff2d391dddfe9482f5
Port:          10054/TCP
Host Port:     0/TCP
Args:
--v=2
--logtostderr
--probe=kubedns,<IP_ADDRESS>:10053,kubernetes.default.svc.cluster.local,5,A
--probe=dnsmasq,<IP_ADDRESS>:53,kubernetes.default.svc.cluster.local,5,A
State:          Waiting
Reason:       CrashLoopBackOff
Last State:     Terminated
Reason:       Error
Exit Code:    2
Started:      Thu, 02 May 2019 09:20:09 +1000
Finished:     Thu, 02 May 2019 09:21:59 +1000
Ready:          False
Restart Count:  82
Requests:
cpu:        10m
memory:     20Mi
Liveness:     http-get http://:10054/metrics delay=60s timeout=5s period=10s #success=1 #failure=5
Environment:
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-dns-token-vmhxf (ro)
Conditions:
Type              Status
Initialized       True
Ready             False
ContainersReady   False
PodScheduled      True
Volumes:
kube-dns-config:
Type:      ConfigMap (a volume populated by a ConfigMap)
Name:      kube-dns
Optional:  true
kube-dns-token-vmhxf:
Type:        Secret (a volume populated by a Secret)
SecretName:  kube-dns-token-vmhxf
Optional:    false
QoS Class:       Burstable
Node-Selectors:
Tolerations:     CriticalAddonsOnly
node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type     Reason     Age                    From                                                       Message

Normal   Killing    38m (x12 over 80m)     kubelet, ip-10-100-138-42.ap-southeast-2.compute.internal  Killing container with id docker://sidecar:Container failed liveness probe.. Container will be killed and recreated.

I have resolved this issue. The problem was with the proxy settings I added to the Kube cluster.
As the cluster is using <IP_ADDRESS>/16 and <IP_ADDRESS>/16 for internal communication, I needed to add those to No_PROXY list. After that the kube_dns service started working as expected.
Thanks for your help!!


SKVFS 2014.9 Implementation

Coverage decreased (-0.4%) to 99.634% when pulling 2ad99df9a8cc409354432f2fe25d09c95d3d77e6 on SKVFS_2014.9_Implementation into 19a88196080efeb4502b5215ac094cd5ea1df9ee on master.

Coverage remained the same at 100.0% when pulling b62dec5afc45042aa7ac1ebf821a5cd7f54320ad on SKVFS_2014.9_Implementation into 19a88196080efeb4502b5215ac094cd5ea1df9ee on master.

LGTM

LGTM


mingwX64 support

Any plans to add support for mingwX64?

Yeah, there is MacOS so why not Windows...

Support it in what sense?

Still got same error with org.jetbrains.compose.foundation:foundation:1.5.10
Any plan to support mingwX64?

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


inViewport returns true for element starting at window.innerHeight

Maybe it's just a matter of definition, but an element starting exactly at the invisible first pixel under viewport is considered "inViewport". Why?
http://plnkr.co/edit/rurMeic3TAIEXQ8OHJLz?p=preview
Considering that position counting starts at 0, an element having top=viewportH() isn't really in the viewport IMO.

Hmm reasonable logic. The current logic is inclusive of both endpoints.


"See the Wiki for information on adding line breaks."

The Jamf schema says "See the Wiki for information on adding line breaks." for mainContentText - but there's absolutely nothing in the wiki about line breaks(unless I can't find it?)
Edit: 1.1.6 fixes line breaks. \n works

@AndersBNielsen Please see the following:
https://github.com/macadmins/nudge/wiki/updateElements#maincontenttext---type-string-default-value-


Foundation: correct directory iteration on Windows

The path that was being constructed would elide the penultimate arc in the path as the base URL was not marked as a directory.  As such, it was assumed to be a file URL, and making a URL relative to it would truncate the previously last arc.  Append the path component instead and explicitly indicate if it is a directory component when building the URL as we already have the information on hand.
This repairs the directory traversal on Windows.  The bug was identified by the DocC test suite on Windows.

@swift-ci please test Windows platform

@swift-ci please test Linux platform

@swift-ci please test Linux platform

@swift-ci please test Linux platform

@swift-ci please test

@swift-ci please test Windows platform


Wed 3 Oct 11:33 pm #31 -  Python version compatablity >=3.9

#31 @mrutunjay-kinagi thanks for working on this !!!


Simple ocdev installation/update/uninstallation

Goal
The goal of this epic is to provide a simple installation flow for ocdev as well as update and uninstallation.
While the installation might not be difficult, we should make it really simple so the users could (ideally) install ocdev with a single instruction line.
Description
Getting Started
We need to think about the getting started experience of the end-user with ocdev and try to provide the best first experience. This implies a certain requirements on how the user can install ocdev as well as a flow in the documentation to help the user to quickly ramp up.
The installation of  ocdev is requiring some pre-requisites that we need to document.
Once those pre-requisites are installed, we should be looking at how we can simplify the installation of ocdev. For example, on MacOS, we could be using homebrew packages, on Linux we could install from a single command line wget -qO- https://github.com/redhat-developer/ocdev/master/blob/install-ocdev.sh | sh . This should be properly documented too.
After having proceed of the installation, we should guide the user to verify that ocdev has been properly installed.
Now that ocdev is ready, we should provide a default basic set of first commands, something like:

oc login
ocdev application create first-app
ocdev component create nodejs
ocdev ocdev component create --git https://github.com/openshift/nodejs-ex
ocdev component push

Staying up to date
How do we handle the updates of ocdev ? Could we be looking at different solutions so that ocdev keep itself automatically up to date?
To start, we can just put a warning to notify the user that there is a new version of ocdev available, and point to the installation/upgrade documentation.
Troubleshooting
What happens when the developer is hitting some issues? Can we provide different DEBUG information when interacting with the OpenShift API?
Uninstallation
We need to provide a way for the developer to properly uninstall ocdev.
If ocdev was installed with homebrew, we can have an uninstall command.
We should provide proper set of instructions to delete on Linux and Windows too.
Documentation
We should be providing documentation for installing ocdev to cover:

Pre-requisities
Download and Installing: MacOS, Windows, Linux
Verify your installation
Getting started
Update ocdevcli
Troubleshooting
Uninstallation

Sub Tasks

[x] Create Homebrew package - https://github.com/redhat-developer/ocdev/issues/69
[x] show warning when user is running older ocdev version -  https://github.com/redhat-developer/ocdev/issues/71
[x] Create installation bash script #74
[x] add proper documentation #75
[ ]
[ ]
[ ]

@slemeur Other than homebrew what else do we want? As in for other platforms?

You mentioned https://chocolatey.org/ for Windows. That could be nice.

@slemeur Can we close this? I believe we have all the relevant docs now.

Hey @slemeur I'm going to close this for now to cut-down on our issues and I believe this is fully covered :+1: Let us know if it's not! (specifically uninstall documents, I'm not too sure what you mean other than removing just the binary)


Change the perl6 command line to raku

The problem
Since 2019.11, raku is available as an alias, and can be used like that.
Suggestions
Look for occurrences in tooling and documentation and change it.

Hi sir, I am quite interested in contributing for raku and can solve this issue  but am not able to find out the website code in this repository. Where should I find it out @JJ

Hi, @veb7vmehra , thanks a lot for your interest. The website is generated from the /docs directory in this repo, using the Documentable utility, as specified in the README.md. In principle you needn't worry abou that: just check for "perl6" in examples using
`git grep perl6`

and where you find it (in examples), change it to raku. As you probably know, you should work in a fork of this repository, and when you're done, create a pull request and make a reference to this issue (saying simply #3105 in the commit, or closes #3105 if you think it's all that needs to be done).
Thanks a lot again and gold luck. We'll be around here (and in the #raku and #raku-dev IRC channels) just in case you need help.

@JJ Thanks for your help, Will make a pull request by tomorrow. Please also tell me how can I contribute more for Raku

Thanks! You can check any of the repositories in the perl6/ organization,
which are community-maintained sites and modules, as well as the Rakudo
organization, which includes the interpreter. Any contribution to any
module will be probably appreciated too.

I did change the command line command In #3272.
As done by hand, I listed other perl6 appearance left

Editor

ft=perl6
atom-language-perl6
```perl6

Site

doc.perl6.org
github.com/perl6
perl6maven
perl6advent
https://raw.githubusercontent.com/perl6

Modules

Perl::ToPerl6
Perl6::Metamodel
PERL6LIB
PERL6_EXCEPTIONS_HANDLER
~/.perl6/
lang = 'perl6'   <- compiler language ('Raku' apparently)

Did another pass just now, added some comments where I felt we needed to keep the perl6 but it looked out of place, left any external URLs, updated a few incidental references.


[FEATURE] Extracting information from original image using Cellpose masks

Hello! I am working with some NanoString datasets outside their AtoMx SIP. I have used Cellpose GUI to run some segmentations which I like, but I am unable to extract any information from the resulting masks, viz. pixel co-ordinates of the cells, transcript locations etc.
I would also like to extract information (such as staining intensities) from the original image using Cellpose generated masks. Any help is appreciated. Thanks!

we are not going to support this in cellpose, but scipy.ndimage has nice functions for this, e.g.: https://docs.scipy.org/doc/scipy/reference/generated/scipy.ndimage.mean.html#scipy.ndimage.mean
you can use the mean to compute the staining intensity per cell, e.g. with a given img with your stain, you can use the cellpose masks as follows
from scipy.ndimage import mean
intensities = mean(img, masks)


[BUG] loadConfig never uses cache

Describe the bug
I have an issue where a change to the way I set my tailwind.config file started making timeouts when linting. Loading the actual application is fine.
The change was to determine which local packages my app depends on in order to add it to the content that tailwind has to look into.
When debugging I came to a finding that the tailwind.config file was being loaded more times than should be necessary. One time per file it seems.
It seems to me that, when loading tailwind config, the cache is never used. In this line, 2 different instances of dates are compared. These are always different.
To Reproduce
Place a console.log inside each if statement
      if (stats === null) {
        loadedConfig = {};
         console.log("1")
      } else if (lastModifiedDate !== stats.mtime.getTime()) {
        lastModifiedDate = stats.mtime.getTime();
        loadedConfig = requireUncached(resolvedPath);
         console.log("2")
      } else {
        loadedConfig = null;
         console.log("3")
      }

only 2 will appear
Expected behavior
A clear and concise description of what you expected to happen.
I expect  2 to appear once followed by many instances of 3. This means that the last modified date has not changed.
Screenshots
N/A
Environment (please complete the following information):

OS: Debian 11
Softwares + version used:

yarn 4
node 18
eslint-plugin-tailwindcss 3.17.0

Additional context
N/A
eslint config file or live demo
https://github.com/francoismassart/eslint-plugin-tailwindcss/pull/344

@francoismassart this should be a trivial fix. The PR now compares unix times. I'll write tests if necessary.

Hi @rpereira-anchor,
Thank you for your contribution, I'm working on a new beta version which fixes this issue:
https://github.com/francoismassart/eslint-plugin-tailwindcss/blob/fix/config-and-css-expiration/lib/util/customConfig.js#L47
And it also avoid re-parsing unchanged CSS files...
You can already test it out via
npm i<EMAIL_ADDRESS>

Should be fixed in latest release (3.17.4)

@francoismassart I have a deadline soon, I'll report back on the fix. Thank you very much!

@francoismassart it works!


feat(circuits): export web prover, add tests

Pull request checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[x] Build (yarn build) was run locally and any changes were pushed
[x] Lint (yarn lint --check) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Closes #425
What is the new behavior?

Does this introduce a breaking change?

[ ] Yes
[x] No

Other information

I made a copy of the current keys at https://keys.unirep.io/2.0.0-beta-3/. For all future versions we'll use the exact version number in the path.


Add donation flow diagram

related to #295
@CarlosQ96  @mateodaza
I would appreciate if both of you review this diagram

I would add the totalDonations update to the diagram indicating after updating the priceUSD the whole projects total donations is recalculated.
Aside from that I think it's great documentation!

Good point
can you update it on this PR?
(You just click on the documentation, it would open it on mermaidjs editor, then change it and replace markdown link here)

Yes I'll do it today and update the PR.

Added! We can Merge!

Added! We can Merge!

Thanks man


[navigation] fix bug in Get.until/GetDelegate.backUntil

Right now, backUntil tests if there is at most one route before popping. However, it should test if there is more than one route.
Pre-launch Checklist

[ ] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making or feature I am adding, or @jonataslaw said the PR is test-exempt.
[x] All existing and new tests are passing.

fixes #2932

I must have been sleepy when I wrote this to not have seen this hahaha
Thank you very much for your contribution!
LGTM.