ERROR: null exception in GenericResourcesImpl.getById #16

ondrejmichlicekips · 2019-02-04T16:16:27Z

Build worked correctly till 31st of January 2019. Then without any modification it started to throw following error:

Started by user admin
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
[Pipeline] stage
[Pipeline] { (Test Deploy)
[Pipeline] node
Running on Jenkins in C:\Program Files (x86)\Jenkins\workspace\Test_project\AKS_Test
[Pipeline] {
[Pipeline] acsDeploy
Starting Azure Container Service / Kubernetes Service Deployment
Delete Kubernetes management config file C:\Program Files (x86)\Jenkins\workspace\Test_project\AKS_Test\kubeconfig-4637128700832550368
ERROR: ERROR: null
java.lang.NullPointerException
	at com.microsoft.azure.management.resources.implementation.GenericResourcesImpl.getById(GenericResourcesImpl.java:92)
	at com.microsoft.azure.management.resources.implementation.GenericResourcesImpl.getById(GenericResourcesImpl.java:28)
	at com.microsoft.jenkins.acs.commands.AKSDeploymentCommand$AKSDeployWorker.prepareKubeconfig(AKSDeploymentCommand.java:62)
	at com.microsoft.jenkins.acs.commands.KubernetesDeploymentCommandBase$KubernetesDeployWorker.call(KubernetesDeploymentCommandBase.java:170)
	at com.microsoft.jenkins.acs.commands.KubernetesDeploymentCommandBase$KubernetesDeployWorker.call(KubernetesDeploymentCommandBase.java:133)
	at hudson.FilePath.act(FilePath.java:1165)
	at com.microsoft.jenkins.acs.commands.KubernetesDeploymentCommandBase.doExecute(KubernetesDeploymentCommandBase.java:79)
	at com.microsoft.jenkins.acs.commands.AKSDeploymentCommand.execute(AKSDeploymentCommand.java:37)
	at com.microsoft.jenkins.acs.commands.AKSDeploymentCommand.execute(AKSDeploymentCommand.java:25)
...
ERROR: Azure Container Service / Kubernetes Service deployment ended with HasError
Finished: FAILURE

By the code inspection it looks like problem with Azure/AKS API.

acsDeploy 0.2.3
Jenkins 2.150.2

The text was updated successfully, but these errors were encountered:

kristianhald · 2019-02-05T10:03:40Z

We are having the same problem with out AKS setup. ACI is working without problems.
Ours started failing yesterday morning and our AKS is running in Azure WestEurope.

We are using 'Azure Container Agents Plugin' version 0.4.1 and Jenkins is 2.163.
We have not made any changes to our setup prior to the failure.

I believe AKS API might have been updated.
Written a ticket to Microsoft yesterday to determine if this is the case.

jcme · 2019-02-05T11:40:54Z

We're experiencing the same issue as well, currently unable to complete any deployments

Azure Container Service Plugin version 0.2.3
Jenkins version 2.150.2

[Pipeline] { (Deploy)
[Pipeline] acsDeploy
Starting Azure Container Service / Kubernetes Service Deployment
ERROR: ERROR: null
java.lang.NullPointerException
	at com.microsoft.azure.management.resources.implementation.GenericResourcesImpl.getById(GenericResourcesImpl.java:92)
	at com.microsoft.azure.management.resources.implementation.GenericResourcesImpl.getById(GenericResourcesImpl.java:28)
	at com.microsoft.jenkins.acs.commands.AKSDeploymentCommand$AKSDeployWorker.prepareKubeconfig(AKSDeploymentCommand.java:62)
	at com.microsoft.jenkins.acs.commands.KubernetesDeploymentCommandBase$KubernetesDeployWorker.call(KubernetesDeploymentCommandBase.java:170)
	at com.microsoft.jenkins.acs.commands.KubernetesDeploymentCommandBase$KubernetesDeployWorker.call(KubernetesDeploymentCommandBase.java:133)
	at hudson.remoting.UserRequest.perform(UserRequest.java:212)
	at hudson.remoting.UserRequest.perform(UserRequest.java:54)
	at hudson.remoting.Request$2.run(Request.java:369)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1135)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.lang.Thread.run(Thread.java:844)
	Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to jenkins-linux-node-nodejs
		at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)
		at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)
		at hudson.remoting.Channel.call(Channel.java:955)
		at hudson.FilePath.act(FilePath.java:1162)
		at com.microsoft.jenkins.acs.commands.KubernetesDeploymentCommandBase.doExecute(KubernetesDeploymentCommandBase.java:79)
		at com.microsoft.jenkins.acs.commands.AKSDeploymentCommand.execute(AKSDeploymentCommand.java:37)
		at com.microsoft.jenkins.acs.commands.AKSDeploymentCommand.execute(AKSDeploymentCommand.java:25)
		at com.microsoft.jenkins.azurecommons.command.CommandService.runCommand(CommandService.java:88)
		at com.microsoft.jenkins.azurecommons.command.CommandService.execute(CommandService.java:96)
		at com.microsoft.jenkins.azurecommons.command.CommandService.executeCommands(CommandService.java:75)
		at com.microsoft.jenkins.azurecommons.command.BaseCommandContext.executeCommands(BaseCommandContext.java:77)
		at com.microsoft.jenkins.acs.ACSDeploymentBuilder.perform(ACSDeploymentBuilder.java:56)
		at com.microsoft.jenkins.acs.ACSDeploymentContext$ExecutionImpl.run(ACSDeploymentContext.java:141)
		at com.microsoft.jenkins.acs.ACSDeploymentContext$ExecutionImpl.run(ACSDeploymentContext.java:125)
		at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
		at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
		at java.util.concurrent.FutureTask.run(FutureTask.java:266)
		at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
		at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
		at java.lang.Thread.run(Thread.java:748)
[Pipeline] }
[Pipeline] // stage```

kristianhald · 2019-02-05T11:50:22Z

I can see that I wrote in a wrong project, as we are not using the ACS plugin, but the ACA.
It seems they are having something that looks like the same issue:
jenkinsci/azure-container-agents-plugin#34

BartSaelen · 2019-02-05T14:46:49Z

We are experiencing the same problem, since last friday.

ERROR: ERROR: null
java.lang.NullPointerException
	at com.microsoft.azure.management.resources.implementation.GenericResourcesImpl.getById(GenericResourcesImpl.java:92)
	at com.microsoft.azure.management.resources.implementation.GenericResourcesImpl.getById(GenericResourcesImpl.java:28)
	at com.microsoft.jenkins.acs.commands.AKSDeploymentCommand$AKSDeployWorker.prepareKubeconfig(AKSDeploymentCommand.java:62)
	at com.microsoft.jenkins.acs.commands.KubernetesDeploymentCommandBase$KubernetesDeployWorker.call(KubernetesDeploymentCommandBase.java:170)
	at com.microsoft.jenkins.acs.commands.KubernetesDeploymentCommandBase$KubernetesDeployWorker.call(KubernetesDeploymentCommandBase.java:133)
	at hudson.FilePath.act(FilePath.java:1165)
	at com.microsoft.jenkins.acs.commands.KubernetesDeploymentCommandBase.doExecute(KubernetesDeploymentCommandBase.java:79)
	at com.microsoft.jenkins.acs.commands.AKSDeploymentCommand.execute(AKSDeploymentCommand.java:37)
	at com.microsoft.jenkins.acs.commands.AKSDeploymentCommand.execute(AKSDeploymentCommand.java:25)
	at com.microsoft.jenkins.azurecommons.command.CommandService.runCommand(CommandService.java:88)
	at com.microsoft.jenkins.azurecommons.command.CommandService.execute(CommandService.java:96)
	at com.microsoft.jenkins.azurecommons.command.CommandService.executeCommands(CommandService.java:75)
	at com.microsoft.jenkins.azurecommons.command.BaseCommandContext.executeCommands(BaseCommandContext.java:77)
	at com.microsoft.jenkins.acs.ACSDeploymentBuilder.perform(ACSDeploymentBuilder.java:56)
	at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
	at hudson.model.Build$BuildExecution.build(Build.java:206)
	at hudson.model.Build$BuildExecution.doRun(Build.java:163)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
	at hudson.model.Run.execute(Run.java:1810)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:97)
	at hudson.model.Executor.run(Executor.java:429)
ERROR: Azure Container Service / Kubernetes Service deployment ended with HasError
Finished: FAILURE

Jenkins ver. 2.150.2
Azure Container Service Plugin ver. 0.2.3

tomaszszlek · 2019-02-05T17:58:16Z

I am facing the same issue, in K8s logs I can see the following :

Operation name
Get Managed Cluster AccessProfile by List Credential

Could not find role name: clusterAdmin in subscription: xxxx, resourceGroup: MyResourceGroup, managed cluster resource: k8s.

weinong · 2019-02-05T23:20:08Z

the accessProfile resource is not versioned as managed cluster resource.. the proper way is to use the POST command instead. Rest API reference: https://docs.microsoft.com/en-us/rest/api/aks/managedclusters/listclusteradmincredentials

widgetpl · 2019-02-06T14:52:03Z

so Jenkins plugin uses Azure libs for Java and it reference to this
GenericResourcesImpl.java
ResourcesInner.java

        @Headers({ "Content-Type: application/json; charset=utf-8", "x-ms-logging-context: com.microsoft.azure.management.resources.Resources getById" })
        @GET("{resourceId}")
        Observable<Response<ResponseBody>> getById(@Path(value = "resourceId", encoded = true) String resourceId, @Query("api-version") String apiVersion, @Header("accept-language") String acceptLanguage, @Header("User-Agent") String userAgent);

so GET is used but still the question is what has changed as this used to work

yangl900 · 2019-02-06T23:23:20Z

AKS published a new API version (2018-08-01-preview), and it seems the Jenkins plugin dynamically discovers and uses the latest API version. This caused the problem because the GET /accessProfiles API is intend to be deprecated in newer versions. A hotfix is on the way to mitigate the issue..

weinong · 2019-02-07T21:29:54Z

@widgetpl the proper API is to use List{Admin|ClusterUser}Credentials like https://github.com/Azure/azure-libraries-for-java/blob/b4caebe92d042fddb59277945c76a69c4b224a52/azure-mgmt-containerservice/src/main/java/com/microsoft/azure/management/containerservice/implementation/ManagedClustersInner.java#L555

ps-rfriesen · 2019-02-08T09:18:59Z

@yangl900 Hi,
as we are eagerly waiting for that fix, to get our deployment pipeline running again, could you please indicate where the information the a hotfix is on the way is coming from. I couldn't find any information regarding that except for the comment here.

Thanks in advance

amitnanaware · 2019-02-12T09:52:13Z

AKS published a new API version (2018-08-01-preview), and it seems the Jenkins plugin dynamically discovers and uses the latest API version. This caused the problem because the GET /accessProfiles API is intend to be deprecated in newer versions. A hotfix is on the way to mitigate the issue..

We are also facing same issue since last few days? When we can expect fix on this?

kristianhald · 2019-02-12T10:06:47Z

@amitnanaware Still having the error?

I believe this error is the same, that we have had with the Azure Container Agents plugin. Azure deployed a hotfix to AKS to mitigate this error.

https://github.com/Azure/AKS/releases/tag/2019-02-07

jcme · 2019-02-12T10:13:18Z

Seems to have resolved the issue for us. Thanks all!

amitnanaware · 2019-02-12T11:28:28Z

@amitnanaware Still having the error?

I believe this error is the same, that we have had with the Azure Container Agents plugin. Azure deployed a hotfix to AKS to mitigate this error.

https://github.com/Azure/AKS/releases/tag/2019-02-07

The issue is resolved thanks!

amenon90 · 2019-04-04T08:45:56Z

I think this has resurfaced. My deployments were working fine, and today I started getting this:

Starting Azure Container Service / Kubernetes Service Deployment
Delete Kubernetes management config file /home/deploy/workspace/project/kubeconfig-6074144939093463942
ERROR: ERROR: null
java.lang.NullPointerException
	at com.microsoft.azure.management.resources.implementation.GenericResourcesImpl.getById(GenericResourcesImpl.java:92)
	at com.microsoft.azure.management.resources.implementation.GenericResourcesImpl.getById(GenericResourcesImpl.java:28)
	at com.microsoft.jenkins.acs.commands.AKSDeploymentCommand$AKSDeployWorker.prepareKubeconfig(AKSDeploymentCommand.java:62)
	at com.microsoft.jenkins.acs.commands.KubernetesDeploymentCommandBase$KubernetesDeployWorker.call(KubernetesDeploymentCommandBase.java:170)
	at com.microsoft.jenkins.acs.commands.KubernetesDeploymentCommandBase$KubernetesDeployWorker.call(KubernetesDeploymentCommandBase.java:133)
	at hudson.remoting.UserRequest.perform(UserRequest.java:212)
	at hudson.remoting.UserRequest.perform(UserRequest.java:54)
	at hudson.remoting.Request$2.run(Request.java:369)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
	Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to dotnetffb800
		at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)
		at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)
		at hudson.remoting.Channel.call(Channel.java:955)
		at hudson.FilePath.act(FilePath.java:1160)
		at com.microsoft.jenkins.acs.commands.KubernetesDeploymentCommandBase.doExecute(KubernetesDeploymentCommandBase.java:79)
		at com.microsoft.jenkins.acs.commands.AKSDeploymentCommand.execute(AKSDeploymentCommand.java:37)
		at com.microsoft.jenkins.acs.commands.AKSDeploymentCommand.execute(AKSDeploymentCommand.java:25)
		at com.microsoft.jenkins.azurecommons.command.CommandService.runCommand(CommandService.java:88)
		at com.microsoft.jenkins.azurecommons.command.CommandService.execute(CommandService.java:96)
		at com.microsoft.jenkins.azurecommons.command.CommandService.executeCommands(CommandService.java:75)
		at com.microsoft.jenkins.azurecommons.command.BaseCommandContext.executeCommands(BaseCommandContext.java:77)
		at com.microsoft.jenkins.acs.ACSDeploymentBuilder.perform(ACSDeploymentBuilder.java:56)
		at com.microsoft.jenkins.acs.ACSDeploymentContext$ExecutionImpl.run(ACSDeploymentContext.java:141)
		at com.microsoft.jenkins.acs.ACSDeploymentContext$ExecutionImpl.run(ACSDeploymentContext.java:125)
		at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50)
		at hudson.security.ACL.impersonate(ACL.java:290)
		at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47)
		at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
		... 4 more

jcme · 2019-04-04T08:58:41Z

Yes, seems to be broken for us again as well:

Starting Azure Container Service / Kubernetes Service Deployment

ERROR: ERROR: null

java.lang.NullPointerException

	at com.microsoft.azure.management.resources.implementation.GenericResourcesImpl.getById(GenericResourcesImpl.java:92)

	at com.microsoft.azure.management.resources.implementation.GenericResourcesImpl.getById(GenericResourcesImpl.java:28)

	at com.microsoft.jenkins.acs.commands.AKSDeploymentCommand$AKSDeployWorker.prepareKubeconfig(AKSDeploymentCommand.java:62)

	at com.microsoft.jenkins.acs.commands.KubernetesDeploymentCommandBase$KubernetesDeployWorker.call(KubernetesDeploymentCommandBase.java:170)

	at com.microsoft.jenkins.acs.commands.KubernetesDeploymentCommandBase$KubernetesDeployWorker.call(KubernetesDeploymentCommandBase.java:133)

	at hudson.remoting.UserRequest.perform(UserRequest.java:212)

	at hudson.remoting.UserRequest.perform(UserRequest.java:54)

	at hudson.remoting.Request$2.run(Request.java:369)

	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)

	at java.util.concurrent.FutureTask.run(FutureTask.java:264)

	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1135)

	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)

	at java.lang.Thread.run(Thread.java:844)

	Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to jenkins-linux-node-nodejs

		at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)

		at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)

		at hudson.remoting.Channel.call(Channel.java:955)

		at hudson.FilePath.act(FilePath.java:1162)

		at com.microsoft.jenkins.acs.commands.KubernetesDeploymentCommandBase.doExecute(KubernetesDeploymentCommandBase.java:79)

		at com.microsoft.jenkins.acs.commands.AKSDeploymentCommand.execute(AKSDeploymentCommand.java:37)

		at com.microsoft.jenkins.acs.commands.AKSDeploymentCommand.execute(AKSDeploymentCommand.java:25)

		at com.microsoft.jenkins.azurecommons.command.CommandService.runCommand(CommandService.java:88)

		at com.microsoft.jenkins.azurecommons.command.CommandService.execute(CommandService.java:96)

		at com.microsoft.jenkins.azurecommons.command.CommandService.executeCommands(CommandService.java:75)

		at com.microsoft.jenkins.azurecommons.command.BaseCommandContext.executeCommands(BaseCommandContext.java:77)

		at com.microsoft.jenkins.acs.ACSDeploymentBuilder.perform(ACSDeploymentBuilder.java:56)

		at com.microsoft.jenkins.acs.ACSDeploymentContext$ExecutionImpl.run(ACSDeploymentContext.java:141)

		at com.microsoft.jenkins.acs.ACSDeploymentContext$ExecutionImpl.run(ACSDeploymentContext.java:125)

		at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)

		at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

		at java.util.concurrent.FutureTask.run(FutureTask.java:266)

		at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

		at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

		at java.lang.Thread.run(Thread.java:748)

ondrejmichlicekips · 2019-04-04T09:03:45Z

Confirm, that issue is back. Probably new API rollout :(

szymon-wlodarczyk · 2019-04-04T11:47:36Z

Same for me

ghost · 2019-04-04T12:15:47Z

Same problems here since this morning Amsterdam time

sureshselvam01 · 2019-04-04T12:55:04Z

Same issue here too. When could we expect the fix

szymon-wlodarczyk · 2019-04-08T07:34:26Z

Hello, issue is still occurring, when we can expect fix for this ?

gavinfish · 2019-04-09T05:59:22Z

I am working on fixing this issue. A PR is on the way.

szymon-wlodarczyk · 2019-04-09T07:49:41Z

when new plugin version will be released with this fix ?

gavinfish · 2019-04-09T07:56:48Z

I am now working on the release process, the new version will be 0.2.4 thanks.

amenon90 · 2019-04-09T12:18:27Z

0.2.4 works. Thank you very much @gavinfish

szymon-wlodarczyk · 2019-04-09T12:20:09Z

I can confirm that as well. Cheers.

torumakabe mentioned this issue Feb 7, 2019

Connect to null failed: null jenkinsci/azure-container-agents-plugin#34

Closed

gavinfish mentioned this issue Apr 9, 2019

Use AKS api instead of generic one #17

Merged

gavinfish closed this as completed in #17 Apr 9, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

ERROR: null exception in GenericResourcesImpl.getById #16

ERROR: null exception in GenericResourcesImpl.getById #16

ondrejmichlicekips commented Feb 4, 2019

kristianhald commented Feb 5, 2019

jcme commented Feb 5, 2019 •

edited

Loading

kristianhald commented Feb 5, 2019

BartSaelen commented Feb 5, 2019

tomaszszlek commented Feb 5, 2019

weinong commented Feb 5, 2019

widgetpl commented Feb 6, 2019

yangl900 commented Feb 6, 2019

weinong commented Feb 7, 2019

ps-rfriesen commented Feb 8, 2019

amitnanaware commented Feb 12, 2019

kristianhald commented Feb 12, 2019

jcme commented Feb 12, 2019

amitnanaware commented Feb 12, 2019

amenon90 commented Apr 4, 2019

jcme commented Apr 4, 2019

ondrejmichlicekips commented Apr 4, 2019

szymon-wlodarczyk commented Apr 4, 2019

ghost commented Apr 4, 2019

sureshselvam01 commented Apr 4, 2019

szymon-wlodarczyk commented Apr 8, 2019

gavinfish commented Apr 9, 2019

szymon-wlodarczyk commented Apr 9, 2019

gavinfish commented Apr 9, 2019

amenon90 commented Apr 9, 2019

szymon-wlodarczyk commented Apr 9, 2019

ERROR: null exception in GenericResourcesImpl.getById #16

ERROR: null exception in GenericResourcesImpl.getById #16

Comments

ondrejmichlicekips commented Feb 4, 2019

Build worked correctly till 31st of January 2019. Then without any modification it started to throw following error:

kristianhald commented Feb 5, 2019

jcme commented Feb 5, 2019 • edited Loading

kristianhald commented Feb 5, 2019

BartSaelen commented Feb 5, 2019

tomaszszlek commented Feb 5, 2019

weinong commented Feb 5, 2019

widgetpl commented Feb 6, 2019

yangl900 commented Feb 6, 2019

weinong commented Feb 7, 2019

ps-rfriesen commented Feb 8, 2019

amitnanaware commented Feb 12, 2019

kristianhald commented Feb 12, 2019

jcme commented Feb 12, 2019

amitnanaware commented Feb 12, 2019

amenon90 commented Apr 4, 2019

jcme commented Apr 4, 2019

ondrejmichlicekips commented Apr 4, 2019

szymon-wlodarczyk commented Apr 4, 2019

ghost commented Apr 4, 2019

sureshselvam01 commented Apr 4, 2019

szymon-wlodarczyk commented Apr 8, 2019

gavinfish commented Apr 9, 2019

szymon-wlodarczyk commented Apr 9, 2019

gavinfish commented Apr 9, 2019

amenon90 commented Apr 9, 2019

szymon-wlodarczyk commented Apr 9, 2019

jcme commented Feb 5, 2019 •

edited

Loading