Kris

After doing this: ```smalltalk #( 'https://github.com/SeasideSt/Seaside-Legacy30' 'https://github.com/pharo-project/pharo-zeroconf.git' 'https://github.com/pharo-project/pharo.git' 'https://github.com/pharo-project/pharo-launcher.git' 'https://github.com/pharo-project/pharo-vm.git' 'https://github.com/pharo-project/pharo-site.git' 'https://github.com/pharo-project/pharo-changelogs.git' 'https://github.com/pharo-project/pharo-core.git' ) do: [ :url | Transcript show: url; cr. [ IceRepositoryCreator new url: url; location: FileLocator temp...

I suspect the problem has to do with the following point in the [changes listed for libgit2 v1.0.1](https://github.com/libgit2/libgit2/releases/tag/v1.0.1): > * A bug where the smart HTTP transport could not read...

The description of the change in libgit2 I referred to says “fetching from servers like Gerrit, that sent large data packets, would error.” I assume GitHub just didn’t send large...

@estebanlm, about: > 3. libgit2 library may have become incorrect for the context […] See [my comment from August 1st](https://github.com/pharo-project/pharo/issues/11481#issuecomment-1201163105): my ‘test.c’ reproduces the error with libgit2 v1.0.0, but not...

@estebanlm OK no problem, I couldn’t quite tell from your comment whether you had read that so just wanted to make sure. I assume that what changed is that GitHub...

This: > It seems like the semaphore is not being signalled correctly. Makes me wonder whether this OSSubprocess issue is somehow related: https://github.com/pharo-contributions/OSSubprocess/issues/73 As I wrote in that issue, the...

I’m not sure either whether the issues are truly related other than that they both involve a Semaphore. Though if I understand correctly, the problem in this issue is that...

Here's a screenshot of another example I was testing (screenshot was made using [v3.3.1](https://github.com/swagger-api/swagger-ui/tree/v3.3.1)). The structure of the schema object for the “containingFolder” attribute for “Folder” is similar to the...

> "type": "null" is not valid in OpenAPI, because there's no null type - that's one of the differences from JSON Schema. OpenAPI uses the nullable attribute instead. @hkosova, I...

> @Rinzwind can't think of a different way to express it. Thanks for the feedback. I’ve posted an [issue for it at the OpenAPI Specification repository](https://github.com/OAI/OpenAPI-Specification/issues/1368).