asoltesz
asoltesz
@Ilogeek Yes, dynamic_edit is a great productivity booster makes one enthusiastic. (thanks for the plugin BTW) I would love to contribute, although I have nonexistent Ruby/Rails skills and limited in...
@markusneg Yes, I mean that plugin and it doesn't show up in mine either. This is not a surprise, because I suspect the redmine_wysiwyg_editor plugin probably attaches to some extension...
I second the enhancement. Most of the time a theme will strictly belong to one site since it is much easier for authors to just copy a theme and quickly...
I second this feature request because non-volumesnapshot-based, offline filesystem backups are obviously still needed. Implementing my hybrid volumesnapshot / restic feature request ( #1099 ) could somehow alleviate the need...
Any idea when this will be investigated / fixed? Seems like a serious issue for an rc6 version state.
@hossainemruz I have tried with the version you recommended. There are no error messages now in the operator log: ~~~ I0601 20:26:08.225724 1 jobs.go:69] Sync/Add/Update for Job stash-backup-default-1591043160 I0601 20:26:08.225751...
I believe this belonged to the first execution today: ~~~ kubectl describe backupsession default-1591042691 Name: default-1591042691 Namespace: pgadmin Labels: app.kubernetes.io/component=stash-backup app.kubernetes.io/managed-by=stash.appscode.com stash.appscode.com/invoker-name=default stash.appscode.com/invoker-type=BackupConfiguration Annotations: API Version: stash.appscode.com/v1beta1 Kind: BackupSession Metadata:...
Here they are: ~~~ kc logs stash-vs-pvc-pgadmin-1591044603-xtp97 I0601 20:50:04.574623 1 log.go:181] FLAG: --alsologtostderr="false" I0601 20:50:04.574772 1 log.go:181] FLAG: --backupsession="default-1591044603" I0601 20:50:04.574781 1 log.go:181] FLAG: --bypass-validating-webhook-xray="false" I0601 20:50:04.574789 1 log.go:181] FLAG:...
Not easily. I would have to migrate my stuff up to Kubernetes 1.17 because that API is only available from there. Unfortunately Kubernetes 1.16+ has removed a lot of older...
> It won't be easy for us to support both API versions. There are some breaking changes. We would rather go with the v1beta1 api. I perfectly understand the issue,...