Resolving Hex dependencies... Resolution completed in 0.18s Unchanged: ash 3.24.3 ash_form_builder 0.2.3 ash_phoenix 2.3.21 buckets 1.1.0 castore 1.0.18 circular_buffer 1.0.0 crux 0.1.2 decimal 2.3.0 ecto 3.13.5 elixir_make 0.9.0 ets 0.9.0 finch 0.21.0 hpax 1.0.3 interactive_cmd 0.1.3 iterex 0.1.2 jason 1.4.4 jose 1.11.12 libgraph 0.16.0 mime 2.0.7 mint 1.7.1 nerves 1.13.2 nerves_discovery 0.1.2 nerves_logging 0.2.4 nerves_runtime 0.13.12 nerves_system_bbb 2.29.3 nerves_system_br 1.33.5 nerves_system_grisp2 0.17.3 nerves_system_mangopi_mq_pro 0.15.3 nerves_system_osd32mp1 0.24.3 nerves_system_qemu_aarch64 0.3.3 nerves_system_rpi 2.0.2 nerves_system_rpi0 2.0.2 nerves_system_rpi0_2 2.0.2 nerves_system_rpi2 2.0.2 nerves_system_rpi3 2.0.2 nerves_system_rpi4 2.0.2 nerves_system_rpi5 2.0.2 nerves_system_x86_64 1.33.3 nerves_toolchain_aarch64_nerves_linux_gnu 13.2.0 nerves_toolchain_armv6_nerves_linux_gnueabihf 13.2.0 nerves_toolchain_armv7_nerves_linux_gnueabihf 13.2.0 nerves_toolchain_ctng 1.10.0 nerves_toolchain_riscv64_nerves_linux_gnu 13.2.0 nerves_toolchain_x86_64_nerves_linux_musl 13.2.0 nerves_uevent 0.1.3 nimble_options 1.1.1 nimble_pool 1.1.0 phoenix 1.8.5 phoenix_html 4.3.0 phoenix_live_view 1.1.28 phoenix_pubsub 2.2.0 phoenix_template 1.0.4 plug 1.19.1 plug_crypto 2.1.1 property_table 0.3.3 reactor 1.0.1 req 0.5.17 req_s3 0.2.3 ring_logger 0.11.5 shoehorn 0.9.3 spark 2.6.1 splode 0.3.1 stream_data 1.3.0 tablet 0.3.2 telemetry 1.4.1 toolshed 0.4.2 uboot_env 1.0.2 websock 0.5.3 websock_adapter 0.5.9 yamerl 0.10.0 yaml_elixir 2.12.1 ymlr 5.1.5 All dependencies have been fetched ==> stream_data Compiling 3 files (.ex) Generated stream_data app ==> ymlr Compiling 3 files (.ex) Generated ymlr app ==> mime Compiling 1 file (.ex) Generated mime app ==> circular_buffer Compiling 1 file (.ex) Generated circular_buffer app ==> nimble_options Compiling 3 files (.ex) Generated nimble_options app ==> plug_crypto Compiling 5 files (.ex) Generated plug_crypto app ==> hpax Compiling 4 files (.ex) Generated hpax app ==> nerves_compatibility_test ===> Analyzing applications... ===> Compiling yamerl ==> jose Compiling 113 files (.erl) Compiling 8 files (.ex) Generated jose app ==> ets Compiling 7 files (.ex) Generated ets app ==> tablet Compiling 2 files (.ex) Generated tablet app ==> iterex Compiling 48 files (.ex) Generated iterex app ==> elixir_make Compiling 8 files (.ex) Generated elixir_make app ==> nerves_logging CC kmsg_tailer.o LD kmsg_tailer Not crosscompiling. To test locally, the port binary needs extra permissions. Set SUDO=sudo to set permissions. The default is to skip this step. SUDO_ASKPASS=/usr/bin/ssh-askpass SUDO=true Compiling 5 files (.ex) Generated nerves_logging app ==> castore Compiling 1 file (.ex) Generated castore app ==> mint Compiling 1 file (.erl) Compiling 20 files (.ex) Generated mint app ==> nerves_discovery Compiling 5 files (.ex) Generated nerves_discovery app ==> ring_logger Compiling 7 files (.ex) Generated ring_logger app ==> decimal Compiling 4 files (.ex) Generated decimal app ==> jason Compiling 10 files (.ex) Generated jason app ==> spark Compiling 45 files (.ex) Generated spark app ==> shoehorn Compiling 8 files (.ex) Generated shoehorn app ==> yaml_elixir Compiling 6 files (.ex) Generated yaml_elixir app ==> interactive_cmd Compiling 1 file (.ex) Generated interactive_cmd app ==> nerves HOST_CC port.o HOST_LD port Compiling 52 files (.ex) Generated nerves app ==> libgraph Compiling 15 files (.ex) Generated libgraph app ==> nerves_compatibility_test ===> Analyzing applications... ===> Compiling telemetry ==> ecto Compiling 56 files (.ex) Generated ecto app ==> phoenix_html Compiling 6 files (.ex) Generated phoenix_html app ==> phoenix_template Compiling 4 files (.ex) Generated phoenix_template app ==> phoenix_pubsub Compiling 12 files (.ex) Generated phoenix_pubsub app ==> splode Compiling 5 files (.ex) Generated splode app ==> reactor Compiling 113 files (.ex) Generated reactor app ==> plug Compiling 1 file (.erl) Compiling 42 files (.ex) Generated plug app ==> uboot_env Compiling 5 files (.ex) Generated uboot_env app ==> crux Compiling 19 files (.ex) Generated crux app ==> ash Compiling 569 files (.ex) Generated ash app ==> nimble_pool Compiling 2 files (.ex) Generated nimble_pool app ==> finch Compiling 14 files (.ex) Generated finch app ==> req Compiling 19 files (.ex) Generated req app ==> req_s3 Compiling 2 files (.ex) Generated req_s3 app ==> property_table Compiling 8 files (.ex) Generated property_table app ==> nerves_uevent CC uevent.o LD uevent Not crosscompiling. To test locally, the port binary needs extra permissions. Set SUDO=sudo to set permissions. The default is to skip this step. SUDO_ASKPASS=/usr/bin/ssh-askpass SUDO=true Compiling 3 files (.ex) Generated nerves_uevent app ==> nerves_runtime Compiling 14 files (.ex) Generated nerves_runtime app ==> toolshed Compiling 5 files (.ex) Generated toolshed app ==> websock Compiling 1 file (.ex) Generated websock app ==> websock_adapter Compiling 4 files (.ex) Generated websock_adapter app ==> phoenix Compiling 74 files (.ex) Generated phoenix app ==> phoenix_live_view Compiling 49 files (.ex) Generated phoenix_live_view app ==> ash_phoenix Compiling 35 files (.ex) Generated ash_phoenix app ==> buckets Compiling 19 files (.ex) Generated buckets app ==> ash_form_builder Compiling 19 files (.ex) warning: undefined module attribute @field, please remove access to @field or explicitly set it before access │ 284 │ input_type = html_input_type(@field.type) │ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ │ └─ lib/ash_form_builder/themes/glassmorphism.ex:284: AshFormBuilder.Themes.Glassmorphism (module) warning: you are accessing the variable "input_type" inside a LiveView template. Using variables in HEEx templates are discouraged as they disable change tracking. You are only allowed to access variables defined by Elixir control-flow structures, such as if/case/for, or those defined by the special attributes :let/:if/:for. If you are shadowing a variable defined outside of the template using a control-flow structure, you must choose a unique variable name within the template. Instead of: def add(assigns) do result = assigns.a + assigns.b ~H"the result is: {result}" end You must do: def add(assigns) do assigns = assign(assigns, :result, assigns.a + assigns.b) ~H"the result is: {@result}" end lib/ash_form_builder/themes/glassmorphism.ex:288: AshFormBuilder.Themes.Glassmorphism.field_input/1 warning: you are accessing the variable "input_type" inside a LiveView template. Using variables in HEEx templates are discouraged as they disable change tracking. You are only allowed to access variables defined by Elixir control-flow structures, such as if/case/for, or those defined by the special attributes :let/:if/:for. If you are shadowing a variable defined outside of the template using a control-flow structure, you must choose a unique variable name within the template. Instead of: def add(assigns) do result = assigns.a + assigns.b ~H"the result is: {result}" end You must do: def add(assigns) do assigns = assign(assigns, :result, assigns.a + assigns.b) ~H"the result is: {@result}" end lib/ash_form_builder/themes/glassmorphism.ex:304: AshFormBuilder.Themes.Glassmorphism.field_input/1 warning: you are accessing the variable "error_messages" inside a LiveView template. Using variables in HEEx templates are discouraged as they disable change tracking. You are only allowed to access variables defined by Elixir control-flow structures, such as if/case/for, or those defined by the special attributes :let/:if/:for. If you are shadowing a variable defined outside of the template using a control-flow structure, you must choose a unique variable name within the template. Instead of: def add(assigns) do result = assigns.a + assigns.b ~H"the result is: {result}" end You must do: def add(assigns) do assigns = assign(assigns, :result, assigns.a + assigns.b) ~H"the result is: {@result}" end lib/ash_form_builder/themes/glassmorphism.ex:473: AshFormBuilder.Themes.Glassmorphism.field_errors/1 warning: you are accessing the variable "error_messages" inside a LiveView template. Using variables in HEEx templates are discouraged as they disable change tracking. You are only allowed to access variables defined by Elixir control-flow structures, such as if/case/for, or those defined by the special attributes :let/:if/:for. If you are shadowing a variable defined outside of the template using a control-flow structure, you must choose a unique variable name within the template. Instead of: def add(assigns) do result = assigns.a + assigns.b ~H"the result is: {result}" end You must do: def add(assigns) do assigns = assign(assigns, :result, assigns.a + assigns.b) ~H"the result is: {@result}" end lib/ash_form_builder/themes/glassmorphism.ex:474: AshFormBuilder.Themes.Glassmorphism.field_errors/1 warning: you are accessing the variable "error_messages" inside a LiveView template. Using variables in HEEx templates are discouraged as they disable change tracking. You are only allowed to access variables defined by Elixir control-flow structures, such as if/case/for, or those defined by the special attributes :let/:if/:for. If you are shadowing a variable defined outside of the template using a control-flow structure, you must choose a unique variable name within the template. Instead of: def add(assigns) do result = assigns.a + assigns.b ~H"the result is: {result}" end You must do: def add(assigns) do assigns = assign(assigns, :result, assigns.a + assigns.b) ~H"the result is: {@result}" end lib/ash_form_builder/themes/glassmorphism.ex:473: AshFormBuilder.Themes.Glassmorphism.field_errors/1 warning: you are accessing the variable "error_messages" inside a LiveView template. Using variables in HEEx templates are discouraged as they disable change tracking. You are only allowed to access variables defined by Elixir control-flow structures, such as if/case/for, or those defined by the special attributes :let/:if/:for. If you are shadowing a variable defined outside of the template using a control-flow structure, you must choose a unique variable name within the template. Instead of: def add(assigns) do result = assigns.a + assigns.b ~H"the result is: {result}" end You must do: def add(assigns) do assigns = assign(assigns, :result, assigns.a + assigns.b) ~H"the result is: {@result}" end lib/ash_form_builder/themes/glassmorphism.ex:474: AshFormBuilder.Themes.Glassmorphism.field_errors/1 warning: undefined module attribute @field, please remove access to @field or explicitly set it before access │ 282 │ input_type = html_input_type(@field.type) │ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ │ └─ lib/ash_form_builder/themes/shadcn.ex:282: AshFormBuilder.Themes.Shadcn (module) warning: you are accessing the variable "input_type" inside a LiveView template. Using variables in HEEx templates are discouraged as they disable change tracking. You are only allowed to access variables defined by Elixir control-flow structures, such as if/case/for, or those defined by the special attributes :let/:if/:for. If you are shadowing a variable defined outside of the template using a control-flow structure, you must choose a unique variable name within the template. Instead of: def add(assigns) do result = assigns.a + assigns.b ~H"the result is: {result}" end You must do: def add(assigns) do assigns = assign(assigns, :result, assigns.a + assigns.b) ~H"the result is: {@result}" end lib/ash_form_builder/themes/shadcn.ex:286: AshFormBuilder.Themes.Shadcn.field_input/1 warning: you are accessing the variable "input_type" inside a LiveView template. Using variables in HEEx templates are discouraged as they disable change tracking. You are only allowed to access variables defined by Elixir control-flow structures, such as if/case/for, or those defined by the special attributes :let/:if/:for. If you are shadowing a variable defined outside of the template using a control-flow structure, you must choose a unique variable name within the template. Instead of: def add(assigns) do result = assigns.a + assigns.b ~H"the result is: {result}" end You must do: def add(assigns) do assigns = assign(assigns, :result, assigns.a + assigns.b) ~H"the result is: {@result}" end lib/ash_form_builder/themes/shadcn.ex:303: AshFormBuilder.Themes.Shadcn.field_input/1 warning: you are accessing the variable "error_messages" inside a LiveView template. Using variables in HEEx templates are discouraged as they disable change tracking. You are only allowed to access variables defined by Elixir control-flow structures, such as if/case/for, or those defined by the special attributes :let/:if/:for. If you are shadowing a variable defined outside of the template using a control-flow structure, you must choose a unique variable name within the template. Instead of: def add(assigns) do result = assigns.a + assigns.b ~H"the result is: {result}" end You must do: def add(assigns) do assigns = assign(assigns, :result, assigns.a + assigns.b) ~H"the result is: {@result}" end lib/ash_form_builder/themes/shadcn.ex:466: AshFormBuilder.Themes.Shadcn.field_errors/1 warning: you are accessing the variable "error_messages" inside a LiveView template. Using variables in HEEx templates are discouraged as they disable change tracking. You are only allowed to access variables defined by Elixir control-flow structures, such as if/case/for, or those defined by the special attributes :let/:if/:for. If you are shadowing a variable defined outside of the template using a control-flow structure, you must choose a unique variable name within the template. Instead of: def add(assigns) do result = assigns.a + assigns.b ~H"the result is: {result}" end You must do: def add(assigns) do assigns = assign(assigns, :result, assigns.a + assigns.b) ~H"the result is: {@result}" end lib/ash_form_builder/themes/shadcn.ex:467: AshFormBuilder.Themes.Shadcn.field_errors/1 warning: you are accessing the variable "error_messages" inside a LiveView template. Using variables in HEEx templates are discouraged as they disable change tracking. You are only allowed to access variables defined by Elixir control-flow structures, such as if/case/for, or those defined by the special attributes :let/:if/:for. If you are shadowing a variable defined outside of the template using a control-flow structure, you must choose a unique variable name within the template. Instead of: def add(assigns) do result = assigns.a + assigns.b ~H"the result is: {result}" end You must do: def add(assigns) do assigns = assign(assigns, :result, assigns.a + assigns.b) ~H"the result is: {@result}" end lib/ash_form_builder/themes/shadcn.ex:466: AshFormBuilder.Themes.Shadcn.field_errors/1 warning: you are accessing the variable "error_messages" inside a LiveView template. Using variables in HEEx templates are discouraged as they disable change tracking. You are only allowed to access variables defined by Elixir control-flow structures, such as if/case/for, or those defined by the special attributes :let/:if/:for. If you are shadowing a variable defined outside of the template using a control-flow structure, you must choose a unique variable name within the template. Instead of: def add(assigns) do result = assigns.a + assigns.b ~H"the result is: {result}" end You must do: def add(assigns) do assigns = assign(assigns, :result, assigns.a + assigns.b) ~H"the result is: {@result}" end lib/ash_form_builder/themes/shadcn.ex:467: AshFormBuilder.Themes.Shadcn.field_errors/1 warning: nil.type/0 is undefined (module nil is not available or is yet to be defined) │ 282 │ input_type = html_input_type(@field.type) │ ~ │ └─ lib/ash_form_builder/themes/shadcn.ex:282:41: AshFormBuilder.Themes.Shadcn."field_input (overridable 1)"/1 warning: nil.type/0 is undefined (module nil is not available or is yet to be defined) │ 284 │ input_type = html_input_type(@field.type) │ ~ │ └─ lib/ash_form_builder/themes/glassmorphism.ex:284:41: AshFormBuilder.Themes.Glassmorphism."field_input (overridable 1)"/1 Generated ash_form_builder app ==> nerves_compatibility_test Nerves environment MIX_TARGET: host MIX_ENV: prod Checking for prebuilt Nerves artifacts... Compiling 2 files (.ex) Generated nerves_compatibility_test app