Skip to content

Is it possible to update? Is it sustainable as the repo grows? #2

@vonpupp

Description

@vonpupp

Hello,

I noticed that this repo is 7m old. Probably it is problematic to update the repo (or it will be at some point).

I forked the repo and I am running the action right now. I am not sure if that will update my repo or it is bound to yours (I am not very familiar with actions) but the point being is that the action failed half way through when cloning the repo:

remote: Compressing objects:  99% (32202/32527)        
remote: Compressing objects: 100% (32527/32527)        
remote: Compressing objects: 100% (32527/32527), done.        
Receiving objects:   0% (1/34832)
Receiving objects:   0% (39/34832), 70.12 MiB | 70.12 MiB/s
Receiving objects:   0% (53/34832), 156.67 MiB | 78.37 MiB/s
...
Receiving objects:   7% (2679/34832), 18.38 GiB | 63.78 MiB/s
Receiving objects:   7% (2694/34832), 18.42 GiB | 62.88 MiB/s
Receiving objects:   7% (2708/34832), 18.47 GiB | 53.10 MiB/s

failed after 2h 7m 57s .

Probably that is why this repo is no longer updated? If so, what would be the command that I could use to update it on my notebook? I have seen a docker-compose reference on the action file, but I don't see any docker-compose file.

Thanks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions