ligi
Thanks for the detailed report!
Thanks for the suggestion - unfortunately I will have to wait for IPFS to implement throttling upstream and exposes an API/Command for this. I don't think it is a good...
I added pinning - but unfortunately this is also one of the commands that stall like described in #4
why would you want this?
can you be a bit more specific?
Thanks for the suggestion - will read a bit into dweb:
@splix thanks for the answer! > It should certainly work for some test network and similar, but I don't think it's a good idea for others. The difficulty will 0...
this is a really strange issue. Interestingly it works after some point. Could now reproduce: - update to 1.3.50 - gradlew lint fails - gradlew build success - afterwards also...
here the full stacktrace - perhaps this helps: ``` * Exception is: org.gradle.api.ProjectConfigurationException: A problem occurred configuring project ':app'. at org.gradle.configuration.project.LifecycleProjectEvaluator.wrapException(LifecycleProjectEvaluator.java:80) at org.gradle.configuration.project.LifecycleProjectEvaluator.addConfigurationFailure(LifecycleProjectEvaluator.java:73) at org.gradle.configuration.project.LifecycleProjectEvaluator.access$600(LifecycleProjectEvaluator.java:53) at org.gradle.configuration.project.LifecycleProjectEvaluator$NotifyAfterEvaluate.run(LifecycleProjectEvaluator.java:199) at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:402) at...