search

samccone / twinkie

A polymer(1)&&(2) template parser + interface printer
Apache License 2.0
5 stars 5 forks source link

Internal error! in isPolymerElementType #31

Open bro314 opened 2 years ago

bro314 commented 2 years ago

Gerrit team is upgrading our tools/libraries, and we are now getting an internal error from twinkie, see below.

Upgrade change is: https://gerrit-review.googlesource.com/c/gerrit/+/330565 Bazel: Bump rules_nodejs version to 5.1.0

We will probably just disable twinkie for now. Not sure whether it is worth running the Polymer checker, because we will be migrating to Lit over the next few months.

brohlfs-macbookpro2:gerrit brohlfs$ bazel build --subcommands polygerrit-ui/app:polylint_test
INFO: Invocation ID: 3c67f03d-cc11-4dc3-90cc-25de0b85453e
INFO: Options provided by the client:
  Inherited 'common' options: --isatty=1 --terminal_columns=134
INFO: Reading rc options for 'build' from /Users/brohlfs/gerrit/.bazelrc:
  'build' options: --workspace_status_command=python3 ./tools/workspace_status.py --repository_cache=~/.gerritcodereview/bazel-cache/repository --action_env=PATH --disk_cache=~/.gerritcodereview/bazel-cache/cas --java_language_version=11 --java_runtime_version=remotejdk_11 --tool_java_language_version=11 --tool_java_runtime_version=remotejdk_11 --incompatible_strict_action_env --announce_rc
INFO: Analyzed target //polygerrit-ui/app:polylint_test (535 packages loaded, 26094 targets configured).
INFO: Found 1 target...
SUBCOMMAND: # //polygerrit-ui/app:template_test_npm_bin [action 'Executing genrule //polygerrit-ui/app:template_test_npm_bin', configuration: a3d6a018cb0955280bb130f6ad8c775c458ac5d6a9336fcc7f7ff3cb91a09cfb, execution platform: @local_config_platform//:host]
(cd /private/var/tmp/_bazel_brohlfs/1afd3a60e459d78e0c48831b04b071c0/execroot/gerrit && \
  exec env - \
    PATH=/Users/brohlfs/Library/Caches/bazelisk/downloads/bazelbuild/bazel-5.0.0-darwin-arm64/bin:/usr/local/git/current/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin \
  /bin/bash -c 'source external/bazel_tools/tools/genrule/genrule-setup.sh; bazel-out/host/bin/tools/node_tools/twinkie-bin.sh --tsconfig polygerrit-ui/app/tsconfig_bazel.json --out-dir bazel-out/darwin_arm64-fastbuild/bin/polygerrit-ui/app/template_test_out  --files bazel-out/darwin_arm64-fastbuild/bin/polygerrit-ui/app/template_test.params --out-ts-config bazel-out/darwin_arm64-fastbuild/bin/polygerrit-ui/app/tsconfig_template_test.json')
# Configuration: a3d6a018cb0955280bb130f6ad8c775c458ac5d6a9336fcc7f7ff3cb91a09cfb
# Execution platform: @local_config_platform//:host
ERROR: /Users/brohlfs/gerrit/polygerrit-ui/app/BUILD:136:45: Executing genrule //polygerrit-ui/app:template_test_npm_bin failed: (Exit 1): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Internal error!
Error: Internal error!
    at isPolymerElementType (polymer_classes_parser.ts:344:13)
    at extendsPolymerElement (polymer_classes_parser.ts:327:9)
    at isPolymerElement (polymer_classes_parser.ts:232:10)
    at Array.filter (<anonymous>)
    at Object.getPolymerElements (polymer_classes_parser.ts:277:6)
    at main (index.ts:246:27)
    at Object.<anonymous> (index.ts:304:1)
    at Module._compile (node:internal/modules/cjs/loader:1101:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
Target //polygerrit-ui/app:polylint_test failed to build
Use --verbose_failures to see the command lines of failed build steps.
ERROR: /Users/brohlfs/gerrit/polygerrit-ui/app/BUILD:157:8 Middleman _middlemen/polygerrit-ui_Sapp_Spolylint_Utest-runfiles failed: (Exit 1): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
INFO: Elapsed time: 33.688s, Critical Path: 1.65s
INFO: 9 processes: 9 internal.
FAILED: Build did NOT complete successfully
bro314 commented 2 years ago

With the latest version of 330565: Bazel: Bump rules_nodejs version to 5.1.0 | https://gerrit-review.googlesource.com/c/gerrit/+/330565 this seems to be fixed. Feel free to just close the issue.