You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Under common circumstances, the SDK emits builds containing duplicate imports. While this may or may not cause problems for core-warm modules, it does cause fatal errors during warming when running under the component adapter. (The Component spec says "All import names are required to be unique…", so validation gets grumpy.)
Under TinyGo, all is well. This happens only in standard Go.
We can trigger it simply by importing fmt:
package main
import (
"fmt"
)
funcmain() {
fmt.Println("Boo.")
}
This simple Hello World yields a duplicate import of fd_write:
Under common circumstances, the SDK emits builds containing duplicate imports. While this may or may not cause problems for core-warm modules, it does cause fatal errors during warming when running under the component adapter. (The Component spec says "All import names are required to be unique…", so validation gets grumpy.)
Under TinyGo, all is well. This happens only in standard Go.
We can trigger it simply by importing
fmt
:This simple Hello World yields a duplicate import of
fd_write
:For comparison, compiling an empty
main()
(and thus nofmt
import) emits only 1fd_write
:fd_write
is not unique in this respect, though it is the most common. Several other duplicates occur in the wild as well.The text was updated successfully, but these errors were encountered: