-
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Abstract "task" API: spell incantation, kind and caster #14
Labels
Milestone
Comments
svengreb
added a commit
that referenced
this issue
Nov 17, 2020
The "wand" API is inspired by the fantasy novel "Harry Potter" [1] and uses an abstract view to define interfaces. The main motivation to create a matching naming to the overall "magic" topic and the actual target project Mage [2]. This might be too abstract for some, but is kept understandable insofar as it should allow everyone to use the "task" API and to derive their own tasks from it. - <I> `cast.Caster` - A `interface` type that casts a `spell.Incantation` using a command for a specific `spell.Kind`: - `Cast(spell.Incantation) error` - casts a spell incantation. - `Handles() spell.Kind` - returns the spell kind that can be casted. - `Validate() error` - validates the caster command. - <I> `cast.BinaryCaster` - A `interface` type that composes `cast.Caster` to run commands using a binary executable: - `GetExec() string` - returns the path to the binary executable of the command. - <I> `spell.Incantation` - A `interface` type that is the abstract representation of parameters for a command or action: - `Formula() []string` - returns all parameters of a spell. - `Kind() Kind` - returns the Kind of a spell. - `Options() interface{}` - return the options of a spell. - <I> `cast.Binary` - A `interface` type that composes `cast.Caster` for commands which are using a binary executable: - `Env() map[string]string` - returns additional environment variables. - <I> `cast.GoCode` - A `interface` type that composes `cast.Caster` for actions that can be casted without a `cast.Caster`: - `Cast() (interface{}, error)` - casts itself - <I> `cast.GoModule` - A `interface` type that composes `cast.Binary` for commands that are compiled from a [Go module][3]: - `GoModuleID() *project.GoModuleID` - returns the identifier of a Go module. - <T> `spell.Kind` - A `struct` type that defines the kind of a spell. The API components can be roughly translated to their purpose: - `cast.Caster` -> a executable command It validates the command and defines which `spell.Kind` can be handled by this caster. It could be executed without parameters (`spell.Incantation`), but in most cases needs at least one parameter. - `cast.BinaryCaster` -> a composed `cast.Caster` to run commands using a binary executable. It ensures that the executable file exists and stores information like the path. It could also be executed without parameters (`spell.Incantation`), but would not have any effect im many cases. - `spell.Incantation` -> the parameters of a executable command It assemble all parameters based on the given options and ensures the they are correctly formatted for the execution in a shell environment. Except for special incantations like `spell.GoCode` a incantation cannot be used alone but must be passed to a `cast.Caster` that is able to handle the `spell.Kind` of this incantation. - `spell.Binary` -> a composed `spell.Incantation` to run commands that are using binary executable. It can inject or override environment variables in the shell environment in which the the command will be run. - `spell.GoCode` -> a composed `spell.Incantation` for pure Go code instead of a (binary) executable command. It can “cast itself“, e.g. to simply delete a directory using packages like `os` from the Go standard library. It has been designed this way to also allow such tasks to be handled by the incantation API. - `spell.GoModule` -> a composed `spell.Binary` to run binary commands managed by a [Go module][3], in other words executables installed in `GOBIN` or received via `go get`. It requires the module identifier (`path@version`) in order to download and run the executable. [1]: https://en.wikipedia.org/wiki/Harry_Potter [2]: https://magefile.org [3]: https://golang.org/ref/mod GH-14
svengreb
added a commit
that referenced
this issue
Nov 17, 2020
The "wand" API is inspired by the fantasy novel "Harry Potter" [1] and uses an abstract view to define interfaces. The main motivation to create a matching naming to the overall "magic" topic and the actual target project Mage [2]. This might be too abstract for some, but is kept understandable insofar as it should allow everyone to use the "task" API and to derive their own tasks from it. - <I> `cast.Caster` - A `interface` type that casts a `spell.Incantation` using a command for a specific `spell.Kind`: - `Cast(spell.Incantation) error` - casts a spell incantation. - `Handles() spell.Kind` - returns the spell kind that can be casted. - `Validate() error` - validates the caster command. - <I> `cast.BinaryCaster` - A `interface` type that composes `cast.Caster` to run commands using a binary executable: - `GetExec() string` - returns the path to the binary executable of the command. - <I> `spell.Incantation` - A `interface` type that is the abstract representation of parameters for a command or action: - `Formula() []string` - returns all parameters of a spell. - `Kind() Kind` - returns the Kind of a spell. - `Options() interface{}` - return the options of a spell. - <I> `cast.Binary` - A `interface` type that composes `cast.Caster` for commands which are using a binary executable: - `Env() map[string]string` - returns additional environment variables. - <I> `cast.GoCode` - A `interface` type that composes `cast.Caster` for actions that can be casted without a `cast.Caster`: - `Cast() (interface{}, error)` - casts itself - <I> `cast.GoModule` - A `interface` type that composes `cast.Binary` for commands that are compiled from a [Go module][3]: - `GoModuleID() *project.GoModuleID` - returns the identifier of a Go module. - <T> `spell.Kind` - A `struct` type that defines the kind of a spell. The API components can be roughly translated to their purpose: - `cast.Caster` -> a executable command It validates the command and defines which `spell.Kind` can be handled by this caster. It could be executed without parameters (`spell.Incantation`), but in most cases needs at least one parameter. - `cast.BinaryCaster` -> a composed `cast.Caster` to run commands using a binary executable. It ensures that the executable file exists and stores information like the path. It could also be executed without parameters (`spell.Incantation`), but would not have any effect im many cases. - `spell.Incantation` -> the parameters of a executable command It assemble all parameters based on the given options and ensures the they are correctly formatted for the execution in a shell environment. Except for special incantations like `spell.GoCode` a incantation cannot be used alone but must be passed to a `cast.Caster` that is able to handle the `spell.Kind` of this incantation. - `spell.Binary` -> a composed `spell.Incantation` to run commands that are using binary executable. It can inject or override environment variables in the shell environment in which the the command will be run. - `spell.GoCode` -> a composed `spell.Incantation` for pure Go code instead of a (binary) executable command. It can “cast itself“, e.g. to simply delete a directory using packages like `os` from the Go standard library. It has been designed this way to also allow such tasks to be handled by the incantation API. - `spell.GoModule` -> a composed `spell.Binary` to run binary commands managed by a [Go module][3], in other words executables installed in `GOBIN` or received via `go get`. It requires the module identifier (`path@version`) in order to download and run the executable. [1]: https://en.wikipedia.org/wiki/Harry_Potter [2]: https://magefile.org [3]: https://golang.org/ref/mod Resolves GH-14
Closed
svengreb
added a commit
that referenced
this issue
Nov 21, 2020
To use the Go toolchain, also known as the `go` command [1], a new caster [2], introduced in GH-14 [3], has been implemented. To unify the handling of errors in the cast [5] package, a new `ErrCast` [4] struct type has also been implemented. The `Validate` function [6] of the new caster returns an error of type `*cast.ErrCast` when the `go` binary executable does not exists at the configured path or when it is also not available in the executable search paths of the current environment. [1]: https://golang.org/cmd/go [2]: https://pkg.go.dev/github.com/svengreb/wand/pkg/cast#Caster [3]: #14 [4]: https://pkg.go.dev/github.com/svengreb/wand/pkg/cast#ErrCast [5]: https://pkg.go.dev/github.com/svengreb/wand/pkg/cast [6]: https://pkg.go.dev/github.com/svengreb/wand/pkg/cast#Validate GH-20
svengreb
added a commit
that referenced
this issue
Nov 21, 2020
To use the Go toolchain, also known as the `go` command [1], a new caster [2], introduced in GH-14 [3], has been implemented. To unify the handling of errors in the cast [5] package, a new `ErrCast` [4] struct type has also been implemented. The `Validate` function [6] of the new caster returns an error of type `*cast.ErrCast` when the `go` binary executable does not exists at the configured path or when it is also not available in the executable search paths of the current environment. [1]: https://golang.org/cmd/go [2]: https://pkg.go.dev/github.com/svengreb/wand/pkg/cast#Caster [3]: #14 [4]: https://pkg.go.dev/github.com/svengreb/wand/pkg/cast#ErrCast [5]: https://pkg.go.dev/github.com/svengreb/wand/pkg/cast [6]: https://pkg.go.dev/github.com/svengreb/wand/pkg/cast#Validate GH-20
svengreb
added a commit
that referenced
this issue
Nov 21, 2020
To use the Go toolchain, also known as the `go` command [1], a new caster [2], introduced in GH-14 [3], has been implemented. To unify the handling of errors in the cast [5] package, a new `ErrCast` [4] struct type has also been implemented. The `Validate` function [6] of the new caster returns an error of type `*cast.ErrCast` when the `go` binary executable does not exists at the configured path or when it is also not available in the executable search paths of the current environment. [1]: https://golang.org/cmd/go [2]: https://pkg.go.dev/github.com/svengreb/wand/pkg/cast#Caster [3]: #14 [4]: https://pkg.go.dev/github.com/svengreb/wand/pkg/cast#ErrCast [5]: https://pkg.go.dev/github.com/svengreb/wand/pkg/cast [6]: https://pkg.go.dev/github.com/svengreb/wand/pkg/cast#Validate GH-20
svengreb
added a commit
that referenced
this issue
Nov 21, 2020
To use the Go toolchain, also known as the `go` command [1], a new caster [2], introduced in GH-14 [3], has been implemented. To unify the handling of errors in the cast [5] package, a new `ErrCast` [4] struct type has also been implemented. The `Validate` function [6] of the new caster returns an error of type `*cast.ErrCast` when the `go` binary executable does not exists at the configured path or when it is also not available in the executable search paths of the current environment. [1]: https://golang.org/cmd/go [2]: https://pkg.go.dev/github.com/svengreb/wand/pkg/cast#Caster [3]: #14 [4]: https://pkg.go.dev/github.com/svengreb/wand/pkg/cast#ErrCast [5]: https://pkg.go.dev/github.com/svengreb/wand/pkg/cast [6]: https://pkg.go.dev/github.com/svengreb/wand/pkg/cast#Validate Closes GH-20
svengreb
added a commit
that referenced
this issue
Dec 7, 2020
With GH-14 [1] the "abstract" wand API was introduced with a naming scheme is inspired by the fantasy novel "Harry Potter" [2] that was used to to define interfaces. The main motivation was to create a matching naming to the overall "magic" topic and the actual target project Mage [3], but in retrospect this is way too abstract and confusing. The goal of this commit is to... - rewrite the API to make it way easier to use. - use a "normal" naming scheme. - improve all documentations to be more user-scoped and provide guides and examples. >>> New API Concept The basic mindset of the API remains partially the same, but it is designed around the concept of tasks and the ways to run them. >>>> Command Runner `task.Runner` [4] is a new base interface that runs a command with parameters in a specific environment. It can be compared to the current `cast.Caster` [5] interface, but provides a cleaner method set accepting the new `task.Task` [6] interface. - <M> `Handles() task.Kind` - returns the supported task kind [7]. - <M> `Run(task.Task) error` - runs a command. - <M> `Validate() error` - validates the runner. The new `task.RunnerExec` [8] interface is a specialized `task.Runner` and serves as an abstract representation for a command or action, in most cases a (binary) [executable][9] of external commands or Go module `main` packages, that provides corresponding information like the path to the executable. It can be compared to the previous `BinaryCaster` [10] interface, but also comes with a cleaner method set and a more appropriate name. - <M> `FilePath() string` - returns the path to the (binary) command executable. >>>> Tasks `task.Task` [6] is the new interface that is scoped for Mage "target" [11] usage. It can be compared to the previous `spell.Incantation` [12] interface, but provides a smaller method set without `Formula() []string`. - <M> `Kind() task.Kind` - returns the task kind [7]. - <M> `Options() task.Options` - returns the task options [13]. The new `task.Exec` [14] interface is a specialized `task.Task` and serves as an abstract task for an executable command. It can be compared to the previous `Binary` [15] interface, but also comes with the new `BuildParams() []string` method that enables a more flexible usage by exposing the parameters for command runner like `task.RunnerExec` and also allows to compose with other tasks. See the Wikipedia page about the "anatomy of a shell CLI" [16] for more details about parameters. - <M> `BuildParams() []string` - builds the parameters for a command runner where parameters can consist of options, flags and arguments. - <M> `Env() map[string]string` - returns the task specific environment. The new `task.GoModule` [17] interface is a specialized `task.Exec` for a executable Go module command. It can be compared to the previous `spell.GoModule` [18] interface and the method set has not changed except a renaming of the `GoModuleID() *project.GoModuleID` to the more appropriate name `ID() *project.GoModuleID`. See the official "Go module reference documentation" [19] for more details about Go modules. - <M> `ID() *project.GoModuleID` - returns the identifier of a Go module. >>> New API Naming Scheme The following listing shows the new name concept and how the previous API components can be mapped to the upcoming changes: 1. Runner - A component that runs a command with parameters in a specific environment, in most cases a (binary) executable [9] of external commands or Go module `main` packages. The previous API component that can be compared to runners is `cast.Caster` [5] and its specialized interfaces. 2. Tasks - A component that is scoped for Mage "target" [11] usage in order to run a action. The previous API component that can be compared to tasks is`spell.Incantation` [12] and its specialized interfaces. >>> API Usage Even though the API has been changed quite heavily, the basic usage has almost not changed. -> A `task.Task` can only be run through a `task.Runner`! Before a `spell.Incantation` was passed to a `cast.Caster` in order to run it, in most cases a (binary) executable of a command that uses the `Formula() []string` method of `spell.Incantation` to pass the result a parameters. The new API works the same: A `task.Task` is passed to a `task.Runner` that calls the `BuildParams() []string` method when the runner is specialized for (binary) executable of commands. >>> Improved Documentations Before the documentation was mainly scoped on the technical details, but lacked more user-friendly sections about topics like the way how to implement own API components, how to compose the "elder" reference implementation [20] or usage examples for single or monorepo [21] project layouts. >>>> User Guide Most of the current sections have been rewritten or removed entirely while new sections now provide more user-friendly guides about how to... - use or compose the "elder" reference implementation [20]. - build own tasks and runners using the new API. - structure repositories independent of the layout, single or "monorepo". >>>> Usage Examples Some examples have been added, that are linked and documented in the user guides described above, to show how to... - use or compose the "elder" reference implementation [20]. - build own tasks and runners using the new API. - structure repositories independent of the layout, single or "monorepo". [1]: #14 [2]: https://en.wikipedia.org/wiki/Harry_Potter [3]: https://magefile.org [4]: https://pkg.go.dev/github.com/svengreb/wand/pkg/task#Runner [5]: https://pkg.go.dev/github.com/svengreb/wand/pkg/cast#Caster [6]: https://pkg.go.dev/github.com/svengreb/wand/pkg/task#Task [7]: https://pkg.go.dev/github.com/svengreb/wand/pkg/task#Kind [8]: https://pkg.go.dev/github.com/svengreb/wand/pkg/task#RunnerExec [9]: https://en.wikipedia.org/wiki/Executable [10]: https://pkg.go.dev/github.com/svengreb/wand/pkg/cast#BinaryCaster [11]: https://magefile.org/targets [12]: https://pkg.go.dev/github.com/svengreb/wand/pkg/spell#Incantation [13]: https://pkg.go.dev/github.com/svengreb/wand/pkg/task#Options [14]: https://pkg.go.dev/github.com/svengreb/wand/pkg/task#Exec [15]: https://pkg.go.dev/github.com/svengreb/wand/pkg/spell#Binary [16]: https://en.wikipedia.org/wiki/Command-line_interface#Anatomy_of_a_shell_CLI [17]: https://pkg.go.dev/github.com/svengreb/wand/pkg/task#GoModule [18]: https://pkg.go.dev/github.com/svengreb/wand/pkg/spell#GoModule [19]: https://golang.org/ref/mod [20]: https://pkg.go.dev/github.com/svengreb/wand/pkg/elder [21]: https://trunkbaseddevelopment.com/monorepos GH-49
svengreb
added a commit
that referenced
this issue
Dec 7, 2020
With GH-14 [1] the "abstract" wand API was introduced with a naming scheme is inspired by the fantasy novel "Harry Potter" [2] that was used to to define interfaces. The main motivation was to create a matching naming to the overall "magic" topic and the actual target project Mage [3], but in retrospect this is way too abstract and confusing. The goal of this commit is to... - rewrite the API to make it way easier to use. - use a "normal" naming scheme. - improve all documentations to be more user-scoped and provide guides and examples. >>> New API Concept The basic mindset of the API remains partially the same, but it is designed around the concept of tasks and the ways to run them. >>>> Command Runner `task.Runner` [4] is a new base interface that runs a command with parameters in a specific environment. It can be compared to the current `cast.Caster` [5] interface, but provides a cleaner method set accepting the new `task.Task` [6] interface. - <M> `Handles() task.Kind` - returns the supported task kind [7]. - <M> `Run(task.Task) error` - runs a command. - <M> `Validate() error` - validates the runner. The new `task.RunnerExec` [8] interface is a specialized `task.Runner` and serves as an abstract representation for a command or action, in most cases a (binary) [executable][9] of external commands or Go module `main` packages, that provides corresponding information like the path to the executable. It can be compared to the previous `BinaryCaster` [10] interface, but also comes with a cleaner method set and a more appropriate name. - <M> `FilePath() string` - returns the path to the (binary) command executable. >>>> Tasks `task.Task` [6] is the new interface that is scoped for Mage "target" [11] usage. It can be compared to the previous `spell.Incantation` [12] interface, but provides a smaller method set without `Formula() []string`. - <M> `Kind() task.Kind` - returns the task kind [7]. - <M> `Options() task.Options` - returns the task options [13]. The new `task.Exec` [14] interface is a specialized `task.Task` and serves as an abstract task for an executable command. It can be compared to the previous `Binary` [15] interface, but also comes with the new `BuildParams() []string` method that enables a more flexible usage by exposing the parameters for command runner like `task.RunnerExec` and also allows to compose with other tasks. See the Wikipedia page about the "anatomy of a shell CLI" [16] for more details about parameters. - <M> `BuildParams() []string` - builds the parameters for a command runner where parameters can consist of options, flags and arguments. - <M> `Env() map[string]string` - returns the task specific environment. The new `task.GoModule` [17] interface is a specialized `task.Exec` for a executable Go module command. It can be compared to the previous `spell.GoModule` [18] interface and the method set has not changed except a renaming of the `GoModuleID() *project.GoModuleID` to the more appropriate name `ID() *project.GoModuleID`. See the official "Go module reference documentation" [19] for more details about Go modules. - <M> `ID() *project.GoModuleID` - returns the identifier of a Go module. >>> New API Naming Scheme The following listing shows the new name concept and how the previous API components can be mapped to the upcoming changes: 1. Runner - A component that runs a command with parameters in a specific environment, in most cases a (binary) executable [9] of external commands or Go module `main` packages. The previous API component that can be compared to runners is `cast.Caster` [5] and its specialized interfaces. 2. Tasks - A component that is scoped for Mage "target" [11] usage in order to run a action. The previous API component that can be compared to tasks is`spell.Incantation` [12] and its specialized interfaces. >>> API Usage Even though the API has been changed quite heavily, the basic usage has almost not changed. -> A `task.Task` can only be run through a `task.Runner`! Before a `spell.Incantation` was passed to a `cast.Caster` in order to run it, in most cases a (binary) executable of a command that uses the `Formula() []string` method of `spell.Incantation` to pass the result a parameters. The new API works the same: A `task.Task` is passed to a `task.Runner` that calls the `BuildParams() []string` method when the runner is specialized for (binary) executable of commands. >>> Improved Documentations Before the documentation was mainly scoped on the technical details, but lacked more user-friendly sections about topics like the way how to implement own API components, how to compose the "elder" reference implementation [20] or usage examples for single or monorepo [21] project layouts. >>>> User Guide Most of the current sections have been rewritten or removed entirely while new sections now provide more user-friendly guides about how to... - use or compose the "elder" reference implementation [20]. - build own tasks and runners using the new API. - structure repositories independent of the layout, single or "monorepo". >>>> Usage Examples Some examples have been added, that are linked and documented in the user guides described above, to show how to... - use or compose the "elder" reference implementation [20]. - build own tasks and runners using the new API. - structure repositories independent of the layout, single or "monorepo". [1]: #14 [2]: https://en.wikipedia.org/wiki/Harry_Potter [3]: https://magefile.org [4]: https://pkg.go.dev/github.com/svengreb/wand/pkg/task#Runner [5]: https://pkg.go.dev/github.com/svengreb/wand/pkg/cast#Caster [6]: https://pkg.go.dev/github.com/svengreb/wand/pkg/task#Task [7]: https://pkg.go.dev/github.com/svengreb/wand/pkg/task#Kind [8]: https://pkg.go.dev/github.com/svengreb/wand/pkg/task#RunnerExec [9]: https://en.wikipedia.org/wiki/Executable [10]: https://pkg.go.dev/github.com/svengreb/wand/pkg/cast#BinaryCaster [11]: https://magefile.org/targets [12]: https://pkg.go.dev/github.com/svengreb/wand/pkg/spell#Incantation [13]: https://pkg.go.dev/github.com/svengreb/wand/pkg/task#Options [14]: https://pkg.go.dev/github.com/svengreb/wand/pkg/task#Exec [15]: https://pkg.go.dev/github.com/svengreb/wand/pkg/spell#Binary [16]: https://en.wikipedia.org/wiki/Command-line_interface#Anatomy_of_a_shell_CLI [17]: https://pkg.go.dev/github.com/svengreb/wand/pkg/task#GoModule [18]: https://pkg.go.dev/github.com/svengreb/wand/pkg/spell#GoModule [19]: https://golang.org/ref/mod [20]: https://pkg.go.dev/github.com/svengreb/wand/pkg/elder [21]: https://trunkbaseddevelopment.com/monorepos Closes GH-49
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The wand API is inspired by the fantasy novel “Harry Potter“ and uses an abstract view to define interfaces. The main motivation to create a matching naming to the overall “magic“ topic and the actual target project Mage. This might be too abstract for some, but is kept understandable insofar as it should allow everyone to use the "task" API and to derive their own tasks from it.
cast.Caster
— Ainterface
type that casts aspell.Incantation
using a command for a specificspell.Kind
:Cast(spell.Incantation) error
— casts a spell incantation.Handles() spell.Kind
— returns the spell kind that can be casted.Validate() error
— validates the caster command.cast.BinaryCaster
— Ainterface
type that composescast.Caster
to run commands using a binary executable:GetExec() string
— returns the path to the binary executable of the command.spell.Incantation
— Ainterface
type that is the abstract representation of parameters for a command or action:Formula() []string
— returns all parameters of a spell.Kind() Kind
— returns the Kind of a spell.Options() interface{}
— return the options of a spell.cast.Binary
— Ainterface
type that composescast.Caster
for commands which are using a binary executable:Env() map[string]string
— returns additional environment variables.cast.GoCode
— Ainterface
type that composescast.Caster
for actions that can be casted without acast.Caster
:Cast() (interface{}, error)
— casts itself.cast.GoModule
— Ainterface
type that composescast.Binary
for commands that are compiled from a Go module:GoModuleID() *project.GoModuleID
— returns the identifier of a Go module.spell.Kind
— Astruct
type that defines the kind of a spell.The API components can be roughly translated to their purpose:
cast.Caster
→ a executable commandIt validates the command and defines which
spell.Kind
can be handled by this caster. It could be executed without parameters (spell.Incantation
), but in most cases needs at least one parameter.cast.BinaryCaster
→ a composedcast.Caster
to run commands using a binary executable.It ensures that the executable file exists and stores information like the path. It could also be executed without parameters (
spell.Incantation
), but would not have any effect im many cases.spell.Incantation
→ the parameters of a executable commandIt assemble all parameters based on the given options and ensures the they are correctly formatted for the execution in a shell environment. Except for special incantations like
spell.GoCode
a incantation cannot be used alone but must be passed to acast.Caster
that is able to handle thespell.Kind
of this incantation.spell.Binary
→ a composedspell.Incantation
to run commands that are using binary executable.It can inject or override environment variables in the shell environment in which the the command will be run.
spell.GoCode
→ a composedspell.Incantation
for pure Go code instead of a (binary) executable command.It can “cast itself“, e.g. to simply delete a directory using packages like
os
from the Go standard library. It has been designed this way to also allow such tasks to be handled by the incantation API.spell.GoModule
→ a composedspell.Binary
to run binary commands managed by a Go module, in other words executables installed inGOBIN
or received viago get
.It requires the module identifier (
path@version
) in order to download and run the executable.The text was updated successfully, but these errors were encountered: