[Bug]: 复现puma_gpt2_benchmark时报错No module named 'jax.extend.linear_util'

Issue Type
Build/Install
Modules Involved
SPU runtime
Have you reproduced the bug with SPU HEAD?
Yes
Have you searched existing issues?
Yes
SPU Version
from latest source code
OS Platform and Distribution
Linux Ubuntu 22.04
Python Version
3.10
Compiler Version
GCC 11.4.0
Current Behavior?
 Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:batch_dot_simplification'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:batchnorm_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:bitcast_dtypes_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:call_inliner'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:cholesky_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:conditional_simplifier'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:conditional_to_select'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:convolution_4d_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:convolution_group_converter'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:dot_decomposer'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:eigh_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:float_normalization'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:gather_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:gather_simplifier'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:hlo_constant_folding'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:hlo_cse'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:hlo_dce'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:hlo_pass_pipeline'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:map_inliner'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:operand_upcaster'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:qr_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:real_imag_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:reshape_mover'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:result_caster'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:scatter_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:slice_sinker'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:sort_simplifier'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:triangular_solve_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:while_loop_constant_sinking'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:while_loop_simplifier'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:zero_sized_hlo_elimination'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service/gpu:dot_dimension_sorter'. Continuing because --nocheck_visibility is active
INFO: Analyzed target //examples/python/utils:nodectl (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
Target //examples/python/utils:nodectl up-to-date:
  bazel-bin/examples/python/utils/nodectl
INFO: Elapsed time: 1.468s, Critical Path: 0.01s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
INFO: Running command line: bazel-bin/examples/python/utils/nodectl --config /home/admin/dev/spu/examples/python/ml/puma_bert_benchmarks/3pc.json up
Traceback (most recent call last):
  File "/root/.cache/bazel/_bazel_root/c7c2256833a99c4ceaf0534f480b1c44/execroot/spulib/bazel-out/k8-opt/bin/examples/python/utils/nodectl.runfiles/spulib/examples/python/utils/nodectl.py", line 20, in <module>
    import spu.utils.distributed as ppd
  File "/root/.cache/bazel/_bazel_root/c7c2256833a99c4ceaf0534f480b1c44/execroot/spulib/bazel-out/k8-opt/bin/examples/python/utils/nodectl.runfiles/spulib/spu/utils/distributed.py", line 46, in <module>
    import jax.extend.linear_util as lu
ModuleNotFoundError: No module named 'jax.extend.linear_util'
(base) root@9022304ba02a:/home/admin/dev/spu# bazel run -c opt //examples/python/utils:nodectl -- --config `pwd`/examples/python/ml/puma_gpt2_benchmarks/3pc.json up
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:algebraic_simplifier'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:batch_dot_simplification'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:batchnorm_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:bitcast_dtypes_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:call_inliner'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:cholesky_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:conditional_simplifier'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:conditional_to_select'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:convolution_4d_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:convolution_group_converter'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:dot_decomposer'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:eigh_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:float_normalization'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:gather_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:gather_simplifier'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:hlo_constant_folding'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:hlo_cse'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:hlo_dce'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:hlo_pass_pipeline'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:map_inliner'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:operand_upcaster'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:qr_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:real_imag_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:reshape_mover'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:result_caster'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:scatter_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:slice_sinker'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:sort_simplifier'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:triangular_solve_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:while_loop_constant_sinking'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:while_loop_simplifier'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:zero_sized_hlo_elimination'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service/gpu:dot_dimension_sorter'. Continuing because --nocheck_visibility is active
INFO: Analyzed target //examples/python/utils:nodectl (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
Target //examples/python/utils:nodectl up-to-date:
  bazel-bin/examples/python/utils/nodectl
INFO: Elapsed time: 0.653s, Critical Path: 0.00s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
INFO: Running command line: bazel-bin/examples/python/utils/nodectl --config /home/admin/dev/spu/examples/python/ml/puma_gpt2_benchmarks/3pc.json up
Traceback (most recent call last):
  File "/root/.cache/bazel/_bazel_root/c7c2256833a99c4ceaf0534f480b1c44/execroot/spulib/bazel-out/k8-opt/bin/examples/python/utils/nodectl.runfiles/spulib/examples/python/utils/nodectl.py", line 20, in <module>
    import spu.utils.distributed as ppd
  File "/root/.cache/bazel/_bazel_root/c7c2256833a99c4ceaf0534f480b1c44/execroot/spulib/bazel-out/k8-opt/bin/examples/python/utils/nodectl.runfiles/spulib/spu/utils/distributed.py", line 46, in <module>
    import jax.extend.linear_util as lu
ModuleNotFoundError: No module named 'jax.extend.linear_util'
(base) root@9022304ba02a:/home/admin/dev/spu# bazel run -c opt //examples/python/utils:nodectl -- --config `pwd`/examples/python/ml/puma_gpt2_benchmarks/3pc.json up
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:algebraic_simplifier'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:batch_dot_simplification'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:batchnorm_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:bitcast_dtypes_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:call_inliner'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:cholesky_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:conditional_simplifier'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:conditional_to_select'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:convolution_4d_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:convolution_group_converter'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:dot_decomposer'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:eigh_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:float_normalization'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:gather_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:gather_simplifier'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:hlo_constant_folding'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:hlo_cse'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:hlo_dce'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:hlo_pass_pipeline'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:map_inliner'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:operand_upcaster'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:qr_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:real_imag_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:reshape_mover'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:result_caster'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:scatter_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:slice_sinker'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:sort_simplifier'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:triangular_solve_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:while_loop_constant_sinking'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:while_loop_simplifier'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:zero_sized_hlo_elimination'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service/gpu:dot_dimension_sorter'. Continuing because --nocheck_visibility is active
INFO: Analyzed target //examples/python/utils:nodectl (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
Target //examples/python/utils:nodectl up-to-date:
  bazel-bin/examples/python/utils/nodectl
INFO: Elapsed time: 0.824s, Critical Path: 0.00s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
INFO: Running command line: bazel-bin/examples/python/utils/nodectl --config /home/admin/dev/spu/examples/python/ml/puma_gpt2_benchmarks/3pc.json up
Traceback (most recent call last):
  File "/root/.cache/bazel/_bazel_root/c7c2256833a99c4ceaf0534f480b1c44/execroot/spulib/bazel-out/k8-opt/bin/examples/python/utils/nodectl.runfiles/spulib/examples/python/utils/nodectl.py", line 20, in <module>
    import spu.utils.distributed as ppd
  File "/root/.cache/bazel/_bazel_root/c7c2256833a99c4ceaf0534f480b1c44/execroot/spulib/bazel-out/k8-opt/bin/examples/python/utils/nodectl.runfiles/spulib/spu/utils/distributed.py", line 46, in <module>
    import jax.extend.linear_util as lu
ModuleNotFoundError: No module named 'jax.extend.linear_util'
(base) root@9022304ba02a:/home/admin/dev/spu# bazel run -c opt //examples/python/utils:nodectl -- --config `pwd`/examples/python/ml/puma_gpt2_benchmarks/3pc.json up
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:algebraic_simplifier'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:batch_dot_simplification'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:batchnorm_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:bitcast_dtypes_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:call_inliner'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:cholesky_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:conditional_simplifier'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:conditional_to_select'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:convolution_4d_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:convolution_group_converter'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:dot_decomposer'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:eigh_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:float_normalization'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:gather_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:gather_simplifier'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:hlo_constant_folding'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:hlo_cse'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:hlo_dce'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:hlo_pass_pipeline'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:map_inliner'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:operand_upcaster'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:qr_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:real_imag_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:reshape_mover'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:result_caster'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:scatter_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:slice_sinker'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:sort_simplifier'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:triangular_solve_expander'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:while_loop_constant_sinking'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:while_loop_simplifier'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service:zero_sized_hlo_elimination'. Continuing because --nocheck_visibility is active
WARNING: /home/admin/dev/spu/libspu/compiler/front_end/BUILD.bazel:17:15: in cc_library rule //libspu/compiler/front_end:hlo_importer: Target '//libspu/compiler/front_end:hlo_importer' violates visibility of target '@xla//xla/service/gpu:dot_dimension_sorter'. Continuing because --nocheck_visibility is active
INFO: Analyzed target //examples/python/utils:nodectl (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
Target //examples/python/utils:nodectl up-to-date:
  bazel-bin/examples/python/utils/nodectl
INFO: Elapsed time: 0.745s, Critical Path: 0.00s
INFO: 1 process: 1 internal.

@Ye-D  yeah,i use git clone https://github.com/AntCPLab/puma_benchmarks.git，
Here are my steps：
https://github.com/secretflow/spu/issues/583#issuecomment-1975863212

The bugs are related to the Array shape conversion of JAX, not related to SPU. Please check the dimensions of outputs.logits and related variables. And I will try to re-build this bugs asap and fix it.

@Ye-D  OK, thank you. In addition, I would like to ask if PUMA-benchmark reproduction supports GPU. If not, when I choose puma_gpt2_benchmark for reproduction, how much RAM do I need at least?

it does not support GPU now. You need >= 64GB RAM for each ABY3 node.

@Ye-D  Could you tell me the version of each imported package in Python when puma can be successfully reproduced?

@Ye-D ok, thank you
@anakinxc 请问自己通过编译安装spu包之后，像puma_bert_benchmarks.py需要import spu，是不是也需要参考https://github.com/secretflow/spu/issues/401#issuecomment-1809718108 的操作

@Ye-D ok, thank you @anakinxc 请问自己通过编译安装spu包之后，像puma_bert_benchmarks.py需要import spu，是不是也需要参考#401 (comment) 的操作

是的，不要在 spu 目录下 import spu

@anakinxc 好的，谢谢
@Ye-D Since the error seems to be related to the model, and the batch_num (= 100) here is a constant, is it possible that the failure of reshape is caused by the update of the FlaxGPT2LMHeadModel of huggingface?

@Ye-D
Hi, I found that the reshape operation error here is because the default size of the gpt2 vacab_size imported in the code is 50257, which makes it impossible to divide by the  batch_num 100 set in the code, so I don't think it is due to jax.
Have you changed the vacab_size of the imported gpt2 model before running puma_gpt2_benchmarks, or is the size at that time not 50257?

@pguihc
Probably, we do not need the reshape operation. Hope it helps you.

@pguihc We do not need modify the source code about softmax in modeling_flax_gpt2.py, and our hijack method can catch the softmax function. You can verify it by profiling the costs with that: 1) if you do not hijack softmax, we see about 12 calls of div; 2) when you enable the softmax hijack, you can see the div is replaced by recipe. Hope this helps you.

@Ye-D Hi, thank you very much for your reply. I would like to ask if this result is normal: I modified the flax_gpt2.py by hijacking the gelu and softmax functions. Then I ran the modified code and compared it with flax_gpt2.py, and found that they generated a token in about the same time.

Please check the profiling time and communication costs. If you run the code in localhost, then you might get similar running time.

@Ye-D This is part of my code and log. But the profile time in the log of both functions is about the same. Could you tell me what to do to know the impact of hijacking gelu and softmax on token generation time?
def run_on_spu():
    # encode context the generation is conditioned on
    inputs_ids = tokenizer.encode(
        "I enjoy walking with my cute dog, but I'm not sure if I'll ever be able to walk with my dog. I'm not sure if I'll ever be able to walk with my dog.\n\nI'm not sure if I'll ever be able to walk with my dog. I'm not sure if I'll ever be able to walk with my dog.\n\nI'm not", return_tensors='jax'
    )
    input_ids = ppd.device("P1")(lambda x: x)(inputs_ids)
    params = ppd.device("P2")(lambda x: x)(pretrained_model.params)
    outputs_ids = ppd.device("SPU")(text_generation,)(input_ids, params)
    outputs_ids = ppd.get(outputs_ids)
    return outputs_ids

def run_on_puma():
    # encode context the generation is conditioned on
    input_ids = tokenizer.encode(
        "I enjoy walking with my cute dog, but I'm not sure if I'll ever be able to walk with my dog. I'm not sure if I'll ever be able to walk with my dog.\n\nI'm not sure if I'll ever be able to walk with my dog.

@Ye-D Hi, Thank you very much for your reply.
Do you mean that the current spu has optimized the internal related calculation function, so that the time comparison of token generation after only hijacking softmax and gelu is not obvious?

the difference of communication is obvious, so you should do the
experiments with a WAN setting.

Best wishes,
Ye Dong
https://ye-d.github.io/
pguihc @.***> 于2024年3月26日周二 19:06写道：

@Ye-D https://github.com/Ye-D Hi, Thank you very much for your reply.
Do you mean that the current spu has optimized the internal related
calculation function, so that the time comparison of token generation after
only hijacking softmax and gelu is not obvious?
—
Reply to this email directly, view it on GitHub
https://github.com/secretflow/spu/issues/583#issuecomment-2020133574,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFU7RG2QMRF3EZXMTI3DHK3Y2FJCLAVCNFSM6AAAAABEDF7FKKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRQGEZTGNJXGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Basically, it would be difficult to see the cost of a specific function since it has been broken down into smaller operations.
But your latest puma's run seems weired. It should not contain f_div

@Ye-D This is my test code.
test_spu

Add copts optimization to the SPU device environment.
please check if you have modified the activation function of Bert and GPT2 as we did in our readme file.

@fionser @Ye-D
in puma_gpt2.py：copts.enable_optimize_denominator_with_broadcast = True
in both docker containers, modeling_flax_gpt2.py:

But there's still f_div in the log
What does it mean to have f _ div in the log?

please follow this: https://github.com/AntCPLab/puma_benchmarks/blob/835db68d578038f5f79ce0c8fd2822c7e1599930/puma_gpt2_benchmarks/puma_gpt2_benchmarks.py#L163C22-L163C102

@fionser @Ye-D in puma_gpt2.py：copts.enable_optimize_denominator_with_broadcast = True in both docker containers, modeling_flax_gpt2.py:  But there's still f_div in the log What does it mean to have f _ div in the log?

In your old log, no f_div is called. It correctly called f_reciprocal.
But in the latter log, f_div pops out.

@Ye-D @fionser Thank you for your patient reply.


[AVM Module Issue]: Capability to apply log_analytics_solutions as a child item to the workspace

Check for previous/existing GitHub issues

[X] I have checked for previous/existing GitHub issues

Issue Type?
Feature Request
(Optional) Module Version
0.1.5
(Optional) Correlation Id
No response
Description
In order to enable features like sentinel etc we should be able to apply log analytics solutions to the workspace. Discussion to have, should this be with this module or a seperate child module. Opening this issue to see if @cshea-msft is willing to be the owner

@ChrisSidebotham - could add it as a sub-module to the LAW module? Since log analytics solution isn't a standalone resource.

To be discussed with core TF Team this week...
In bicep version we have a separate resource module as the Resource Provider is not the same as the resource provider for the Log analytics workspace. Therefore the module requires 2 inputs:

Name
LAW Id

Sub modules are allowed for parent child resources. See the virtual network module.
References must be passed by resource id.

@ChrisSidebotham @matt-FFFFFF @mbilalamjad  - To confirm I'll create the Log Analytics Solution as a Sub-Module for the Log Analytics Workspace Resource Module.

Is it definitely a child resource?

Log Analytics Solution is dependent on LAW, it Requires a workspace ID to deploy the Solution so I would think Yes. IMO

I think in this case it makes sense to use a submodule. You can't deploy solutions anywhere else after all.

log analytics solution sub module will added to the next version release.

I just wanted to know if this is still on the roadmap, because there are already a lot of version releases since this was closed 😄. I am currently creating a new service/solution and trying to build it out of 100% AVM Pattern/Resources modules. Sentinel is part of this solution, and I also need to deploy Solutions to the LWA.

Hey @c-baumgartner  - the submodule was released. I apologize for any miscommunication. It is under module folder. I had to make it a sub-module.
https://github.com/Azure/terraform-azurerm-avm-res-operationalinsights-workspace/tree/main/modules/log_analytics_solution and here is an example i created. https://github.com/Azure/terraform-azurerm-avm-res-operationalinsights-workspace/tree/main/examples/deploy_security_insights
Hope this helps. if any issues please open an issue and link this issue.

Thank you for the quick response @cshea-msft - I did not see that one because there was no PR linked to this issue and I could not find any trace on the AVM side nor in the documentation for the "parent"-module.
Are there some thoughts on how this will be documented / communicated for similar cases? I also had to check on how to pull a submodule directly from the registry :-)
Just in case someone struggles with that here is a module call:
module "log_analytics_solution" {
  source  = "Azure/avm-res-operationalinsights-workspace/azurerm//modules/log_analytics_solution"
  version = "0.4.1"
  ...

Thank you for the quick response @cshea-msft - I did not see that one because there was no PR linked to this issue and I could not find any trace on the AVM side nor in the documentation for the "parent"-module.
And I did not pay close attention in the registry that there is a submodule :-D

Yes, that is my fault, I didn't communicate well.


Empty lines spacer

Everything is working good, but as i see i'm not able to keep empty line on parse method.
Empty lines works like a spacer to improve the readability.
Example:
const yaml = require("yaml");
const ymlFile = fs.readFileSync("./file.yml", "utf-8");  // << file with empty lines before every node
let parsedYml = yaml.parse(ymlFile);

// ...editing parsedYml's props here...

fs.writeFileSync("./file.yml", yaml.stringify(parsedYml));

...the new file.yml here will not have any space before every node, making it unreadable for me.
A good solution should be to add a new prop on option parameter for stringify method, example: "space(s)Before" (boolean, o number...).

If you're intending to read, modify, and then re-stringify a YAML file while keeping its general structure, you should use the YAML Document API instead of the parse/stringify API. In addition to keeping empty lines, this will keep comments and other structural features at least close to how they were in the original. The document also provides a number of accessor methods that should make it relatively easy to access and modify values within your structure.
But you're also right that having an automatic spacer might also be nice for YAML.stringify() and new YAML.Document. The API for that option will need some thought, though, as it'll probably need to be controllable at least according to the depth of the document structure.

If you're intending to read, modify, and then re-stringify a YAML file while keeping its general structure, you should use the YAML Document API instead of the parse/stringify API.

ok...got it!
here is the full working example code:
const yaml = require("yaml");
const ymlFile = fs.readFileSync("./file.yml", "utf-8");
let parsedYml = yaml.parseDocument(ymlFile);

// ...editing parsedYml's props here...
parsedYml.setIn(["prop1", "nestedProp"], "asd");
parsedYml.set("prop2", "lol");

fs.writeFileSync("./file.yml", parsedYml.toString());

...here is the full list of methods to navigate/manipulate the parsed document.

Closing this as answered/stale. I'd kept it open to account for the "automatic spacer" idea, but that's best raised as a separate issue or PR.


How to get data from IPN message

Can somebody just help to point me on right way, i will make pull request...
Thanks!

I got them all without modification or original code...
       ipn = PaypalAdaptive::IpnNotification.new
          ipn.send_back(request.raw_post)
           txn_id = params['txn_id']

           #other variables that you want to access...


(PDB-3294) Update to i18n 0.7.1

Test FAILed

Test FAILed

Test PASSed

CLA signed by all contributors.


Lens UI missing raw span and trace ids

Lens UI has lost the ability to show raw spanId, traceId, and parentSpanId in the recent UI overhaul. Reproduced in zipkin 2.19.1.
See #2507 and #1300 for when this was added the last two times

Thank you for your feedback!
I agree with you!


Publishing the TFLite models (without metadata) on TF Hub

@margaretmz @khanhlvg
As per our discussion here we decided to go with fixed-shaped TFLite models (520x520). Also, the models are not metadata populated yet which also came as one of the decisions in the aforementioned thread. With better model binding support in the coming days, we can release v2 of these models. WDYT?
All the models are temporarily hosted on a GCS bucket. I have included the links here.
I have also included a fresh notebook to demo the conversion and Python inference process.
Let me know what y'all think about the TF Hub publication step from here.

Thanks Sayak! If we decided to go with fixed shape model for now, could you populate the metadata to those model? It will allow Margaret to integrate the model using Android Studio using the ML Model Binding plugin without writing a lot of boilerplate code.

Let me know what y'all think about the TF Hub publication step from here.

Let's publish v1 int8 and dynamic range model with metadata and fixed shape to TF Hub first as the fp16 model doesn't run on GPU delegate anyway.

@khanhlvg as per this discussion I did not populate the metadata in these models. @margaretmz tried the metadata populated models as well but the results came to be spurious. Margaret and I had a few doubts regarding the metadata parameters. Margaret, would you like to chime in here?

the fp16 model doesn't run on GPU delegate anyway.

Ahh, I didn't know it. Is there anything we could do about it?

@khanhlvg as per this discussion I did not populate the metadata in these models. @margaretmz tried the metadata populated models as well but the results came to be spurious. Margaret and I had a few doubts regarding the metadata parameters. Margaret, would you like to chime in here?

My understanding is Margaret's issue with the metadata came from the fact that she tried the dynamic shape model with ML Model Binding and got a weird error. It is because ML Model Binding doesn't support dynamic shape model yet.

the fp16 model doesn't run on GPU delegate anyway.
Ahh, I didn't know it. Is there anything we could do about it?

Unfortunately no. It comes from a limitation of the TF Lite GPU delegate. We need the TF Lite GPU team to work on it.

Okay. I will populate the metadata with what we discussed here.

@khanhlvg another point on the float16 model. Could we include it in the v1 release which might make the release more complete?

@khanhlvg @margaretmz
Models have been populated with metadata. Download links available here. Here's the Colab Notebook.

Thanks Sayak!

@khanhlvg another point on the float16 model. Could we include it in the v1 release which might make the release more complete?

The fp16 models is larger and slower than the int8/dynamic range quantized models on CPU so I think there's no use of it. However I don't have a strong opinion on whether to publish it or not so I'll let you decide :)

For completion, I would keep it in the release. Would you advise to include a note on the current incompatibility of the models with TFLite GPU delegate?

For completion, I would keep it in the release. Would you advise to include a note on the current incompatibility of the models with TFLite GPU delegate?

Sure. You can just say that the CartoonGAN model is currently not compatible with TF Lite GPU delegate.

Fair enough!

@sayakpaul please make the following updates:

image size should be 512x512 per discussion here.
edit the title of this issue and README to be (with metadata) if your models indeed contain metadata.
I tried the 3 models what you listed most recently. The FP16 one was crashing on Android not sure why but it wasn't crashing before. The other 2 were black - I figured out it's due to incorrect metadata. Please fix it according to this issue I opened here.

The FP16 one was crashing on Android not sure why but it wasn't crashing before.

It crashes if you use GPU delegate. Maybe you didn't try with GPU delegate before?

@margaretmz feedback addressed as per https://github.com/margaretmz/CartoonGAN-e2e-tflite-tutorial/issues/7.
Not sure about the FP16 model crashing on Android, though.

It crashes if you use GPU delegate. Maybe you didn't try with GPU delegate before?
I created a new app, imported the FP16 model with metadata. It still crashes and I can't seem to find the error log.
@khanhlvg could you take a look at the FP16 model in Android?

Thanks for the update, @margaretmz. Once we are clear on the models I will go ahead and create a PR on TF Hub. We could accompany our tutorial with these TF Hub models. WDYT?

I created a new app, imported the FP16 model with metadata and didn't check the "GPU delegate option". It still crashes and I can't seem to find the error in Logcat.

I suspect that the model use too much memory so Android OS killed the process. This is what it look like when I run the model from an Android app.

This is the result from the benchmark app.
Peak memory footprint (MB): init=0.988281 overall=618.25
The model runs fine with the benchmark app because the app doesn't have a rich UI so it consume less memory. The dynamic range and int8 quantized model also consume about 4 times less memory.
I tried reducing the model input shape to 384 * 384 and it runs fine from an Android app.
@sayakpaul If you publish the fp16 model to TF Hub, can you reduce its input shape?

@khanhlvg sure thing. We can also make a note about this on TF Hub and in our upcoming tutorial as well.
WDYT?
Cc: @margaretmz

sure thing. We can also make a note about this on TF Hub and in our upcoming tutorial as well.

SGTM!
@margaretmz Thanks for spotting the issue. :)

Exported float16 model with reduced input shape and populated with metadata.
This section has been updated too.
Cc: @khanhlvg @margaretmz

@khanhlvg it was indeed a memory issue! This explains why original 224x224 worked fine but then stopped working after updating to 512x512.
Even with the reduced size of 384x384, the app died on an older budget phone with 3GB memory; however, it works fine on my Pixel 4 (6GB RAM). My thoughts:

For showing a small image on a a phone (especially side by side with the original image), I'm thinking 224x224 image resolution maybe sufficient. We can give it a try for the FP16 one.
For the sake of a sample app, being able to running only on newer high-end phone is OK. We could also specify that under the "Requirements" section under Android instructions on project GitHub repo.

If the int8 and the DR models run on an older budget phone I think we can drop the FP16 model for now. It won't anyway run on the GPU. WDYT?

If the int8 and the DR models run on an older budget phone I think we can drop the FP16 model for now. It won't anyway run on the GPU. WDYT?

My answer is 'yes' and 'no':

For the purpose of publishing tflite models on TF Hub, we should choose the best ones for wide developer adoption on most devices. Plus it won't even run on GPU. So yes drop it from the release candidates for now.
For the purpose of an  E2E TFLite tutorial with a sample app, including the FP16 variant is a  great demo of quantization trade-offs, and a good story to tell in the tutorial. So I'd like to keep it in the sample app.

Sounds good @margaretmz. Your points make sense. Here's what I propose:

We include 224x224 fp16 model in both the TF Hub bundle and the tutorial. We make a note about the limitations of the fp16 model.

WDYT?
Upon this decision, I will:

Create a 224x224 fp16 model and will populate that with metadata.
Update the download links so that it's easier for you to navigate.
Create a PR on Hub.

Sounds like a good plan. Thanks @sayakpaul!

@margaretmz models updated here.

Excellent! Here is what the 224x224 FP16 model looks like:

By the way, a few minor corrections:

update the title of this issue remove ("without metadata
on the main README - should be 224x244, not 384x384

Thanks @margaretmz. Updates have been made.

PR has been created: https://github.com/tensorflow/hub/pull/654.


fix: do not export g_logging_fail_func

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (25a349f) 59.17% compared to head (f21b853) 59.40%.
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1042      +/-   ##
==========================================
+ Coverage   59.17%   59.40%   +0.23%
==========================================
  Files          19       19
  Lines        2557     2643      +86
  Branches      916      965      +49
==========================================
+ Hits         1513     1570      +57
- Misses        695      721      +26
- Partials      349      352       +3

Files
Coverage Δ

src/logging.cc
67.16% <ø> (-0.06%)
:arrow_down:


Provide a "Cancel Boost" command for ZAPPI

The Myenergy integration offers a "Start Boost" service and a "Stop Boost" service directed at a ZAPPI.  "Start Boost" works correctly and commences a boost with a defined number of kWh target.  "Stop Boost" when issued, momentarily pauses the boost, but the ZAPPI then continues the boost until the target number of kWh have been delivered.  The boost can only be cancelled by using the panel on the ZAPPI itself.  It is useful to be able to start and stop boosts in order to take advantage of favourable tariffs.
The "Stop Boost" command when directed at an EDDI does cancel the boost properly.
If possible a "Cancel Boost" service for the ZAPPI which has the result of a complete cancellation of the boost, as can be done from the ZAPPI panel, would be very useful.

This assumes there is an API link between the so-called boost and the Zappi and clearly there is not. There seems to be a widespread misconception/ presumption that all functions are available when in fact few are.

Octopus Energy, using the Intelligent Octopus Go tariff, manages to start and stop charging on the ZAPPI at will.  Also, the Octopus Energy integration in Home Assistant (courtesy of Bottlecap Dave) offers services "Turn on Intelligent Bump Charge" and "Turn off Intelligent Bump Charge" both of which work.  So there does seem to be a method of programatically controlling the ZAPPI.

So you need to find the API controls and propose a code change with a working example. This is how GitHub works. This is a community integration that relies on the community to solve the problem…

AFAIK Octopus controls the EV not the Zappi and the only function they implement is to switch the Zappi between FAST and ECO+.

The zappi can be controlled by Octopus. I believe the do it by sending a batch of scheduled boosts to the zappi, a start time and a length. Personally, I think this is better than the car integrations as, to the best of my knowledge they are a start and a stop command, so there is a greater risk of temporary connectivity loss (between Octopus and car) resulting in a charge continuing longer than it should.


[MAT-1759] Using VSAC API Key instead of username/password

Submitter:

[x] This pull request describes why these changes were made.
[x] Internal ticket for this PR: MAT-1759
[ ] Internal ticket links to this PR
[x] Code diff has been done and been reviewed
[x] Tests are included and test edge cases
[x] Tests have been run locally and pass

Reviewer 1:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Reviewer 2:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Codecov Report

Merging #113 into bonnie-on-fhir will not change coverage.
The diff coverage is 100.00%.

@@               Coverage Diff               @@
##           bonnie-on-fhir     #113   +/-   ##
===============================================
  Coverage           90.32%   90.32%
===============================================
  Files                  13       13
  Lines                 579      579
===============================================
  Hits                  523      523
  Misses                 56       56

Impacted Files
Coverage Δ

lib/util/vsac_api.rb
96.79% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b0a0cd6...64d7f1f. Read the comment docs.


Problem with sequence as parameters

Expected: No Error
Code:
def blank func(whole x[], whole y[][]){
    yeet#
}
sheesh(){
    yeet#
}

Error Message:
Line 1, Token 14: Unexpected "[" [[], expected -> [',', ')']

recently ko lang nakita inadd mo two d param HHAAHAHAH


Poblem with updating notifications in the iOS app ntfy 1.3

:lady_beetle: Describe the bug
I'm having trouble receiving notification updates in my app. I'm able to send and receive messages from my ntfy app on my iphone, but I have to keep refreshing the topic for the messages to be updated. I've cleared all the permissions for the app on iOS and I still can't receive the messages.
:computer: Components impacted
Own ntfy server, Iphone 15 iOS 17.3.1, app version 1.3 (4)
:crystal_ball: Additional context
The problem does not occur when I use my second Android smartphone. I don't have to keep refreshing the topic to receive or send messages and I don't have a problem receiving messages on the smartphone's notification screen.

To get notifications working on iOS, you need to:

make sure upstream-base-url is set to "https://ntfy.sh"
make sure base-url is set to your full domain, including "https://" and without a trailing slash (e.g., https://ntfy.domain.com)
make sure the default server URL in the iOS app is set to your full domain, I including "https://" and without a trailing slash (it has to exactly match the base-url)

To get notifications working on iOS, you need to:

make sure upstream-base-url is set to "https://ntfy.sh"
make sure base-url is set to your full domain, including "https://" and without a trailing slash (e.g., https://ntfy.domain.com)
make sure the default server URL in the iOS app is set to your full domain, I including "https://" and without a trailing slash (it has to exactly match the base-url)

Thank you very much! I ended up getting excited when installing and didn't even see this part of the docs. It worked now wunter8.

To get notifications working on iOS, you need to:
. . .
3. make sure the default server URL in the iOS app is set to your full domain, I including "https://" and without a trailing slash (it has to exactly match the `base-url`)

Will things still work if a device subscribes to a topic on a custom domain while the default server URL is still set to https://ntfy.sh?

@adebisi-fa I think that will work fine as long as you set the server for that topic to "your full domain, including "https://" and without a trailing slash (it has to exactly match the base-url)"


WASM build fails (mac)

I tried to follow the instructions to build for web, but they fail on my 2019 macbook pro.
I've attached the errors I got, and I can confirm the wasm build works when I remove rltk from my dependencies in Cargo.toml
I also noticed a couple of things in the WASM tutorial that seem to be targeted towards windows users (like using \ instead of / for paths) so I was wondering if the wasm stuff was only tested on windows.
Thanks for making this tutorial btw!
error[E0432]: unresolved import `platform::Signal`
  --> /Users/ldd/.cargo/registry/src/github.com-1ecc6299db9ec823/ctrlc-3.1.9/src/lib.rs:52:9
   |
52 | pub use platform::Signal;
   |         ^^^^^^^^^^^^^^^^ no `Signal` in `platform`

error[E0412]: cannot find type `Error` in module `platform`
  --> /Users/ldd/.cargo/registry/src/github.com-1ecc6299db9ec823/ctrlc-3.1.9/src/error.rs:25:21
   |
25 | impl From<platform::Error> for Error {
   |                     ^^^^^ not found in `platform`
   |
help: consider importing one of these items
   |
1  | use core::fmt::Error;
   |
1  | use crate::Error;
   |
1  | use crate::error::fmt::Error;
   |
1  | use std::error::Error;
   |
     and 2 other candidates

error[E0412]: cannot find type `Error` in module `platform`
  --> /Users/ldd/.cargo/registry/src/github.com-1ecc6299db9ec823/ctrlc-3.1.9/src/error.rs:26:26
   |
26 |     fn from(e: platform::Error) -> Error {
   |                          ^^^^^ not found in `platform`
   |
help: consider importing one of these items
   |
1  | use core::fmt::Error;
   |
1  | use crate::Error;
   |
1  | use crate::error::fmt::Error;
   |
1  | use std::error::Error;
   |
     and 2 other candidates

error[E0412]: cannot find type `Signal` in module `platform`
  --> /Users/ldd/.cargo/registry/src/github.com-1ecc6299db9ec823/ctrlc-3.1.9/src/signal.rs:22:21
   |
22 |     Other(platform::Signal),
   |                     ^^^^^^ not found in `platform`

error[E0425]: cannot find function `init_os_handler` in module `platform`
  --> /Users/ldd/.cargo/registry/src/github.com-1ecc6299db9ec823/ctrlc-3.1.9/src/lib.rs:97:25
   |
97 |         match platform::init_os_handler() {
   |                         ^^^^^^^^^^^^^^^ not found in `platform`

error[E0425]: cannot find function `block_ctrl_c` in module `platform`
   --> /Users/ldd/.cargo/registry/src/github.com-1ecc6299db9ec823/ctrlc-3.1.9/src/lib.rs:110:27
    |
110 |                 platform::block_ctrl_c().expect("Critical system error while waiting for Ctrl-C");
    |                           ^^^^^^^^^^^^ not found in `platform`

error: aborting due to 6 previous errors

Some errors have detailed explanations: E0412, E0425, E0432.
For more information about an error, try `rustc --explain E0412`.
error: could not compile `ctrlc`
    ```

Exact same issue here on windows 10

Workaround found on Discord:
[dependencies]
rltk = { git = "https://github.com/amethyst/bracket-lib" }


Limited number of slides

Everytime I try to add more than 55 slides I get an error, there's a way to prevent this error and continue to adding slides?

Hi, not sure why it's happening, there shouldn't be a limitation to the number of slides. Does it matter if the slides contain elements or not?

Nope, if I create a 56th slide with no elements in it there is still an error when I try to save it.
I tried to switch browser, I usually use Firefox and I tried with Chrome but the error persist.

I'm sorry for the giant delay in the response, I had to dedicate a lot of time into other things lately... I'm wondering if, for some, reason, the server sets a hard limit to 55 values to insert. Do you have access to the SQL logs?


bug(mat-select): mat-select multiple crashes Chrome

Is this a regression?

[X] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
We have an Angular 14 project and a user reported that Chrome would crash for them consistently with the 'sad tab' and error code 11 when they opened certain mat-select inputs. The affected inputs were all multiples, just like this issue.
They are running Chrome Version 124.0.6367.62 on an Apple Silicon Mac, but we have reproduced the issue on Chrome Version 124.0.6367.62 on Windows ARM also.
This issue only seems to affect Chrome, but with no obvious pattern. After a crash, the web inspector reveals nothing unusual, nor is there any console output. I was able to capture chrome debug logs during one such crash, but it did not reveal anything interesting.
I realise that this report isn't particularly useful since I can't reliably reproduce the error, but I suspect this may be happening more widely than is realised since it's unlikely to get picked up by automated error monitoring.
Reproduction
We have not been able to consistently reproduce the issue. Having made no code changes, the issue is manifesting intermittently.
Expected Behavior
Opening a mat-select multiple should not crash Chrome.
Actual Behavior
Chrome crashes when opening mat-select multiple
Environment

Angular: 14.2.9
CDK/Material: 14.2.7
Browser(s): Chrome Version 124.0.6367.62
Operating System (e.g. Windows, macOS, Ubuntu): Windows and macOS, possibly more

We've also been experiencing this and can replicate consistently.

Happens with multiple selection disabled
Only happens when inside a mat-form-field, and only when clicked

Setting floatLabel to always or never does not have an effect

No console errors, nor anything other useful indication as to what could be causing it (apart from STATUS_STACK_OVERFLOW message on Windows).
@angular/core: 16.2.11
@angular/material: 16.2.10
Witnessed on

macOS: Chrome v124.0.6367.62 (Error code 11)
Windows: Chrome v124.0.6367.61 (Error code: STATUS_STACK_OVERFLOW)

https://github.com/angular/components/assets/1168092/00c1ccad-6b53-4dc1-9e4e-f88d2cdef513

Hello, thank you for providing as much detail as possible. Unfortunately, if this is a Chrome issue, then there's nothing that Angular components can do about this.
Have you filed an issue on Chromium?
Best Regards,
Zach

Hey guys, I was able to reproduce this in the component library I work on (which has the same implementation with aria/role as this for our custom dropdown). The 2 way relationship below:

parent

child

is enough to demo in chrome if you inspect the child or mouse over in Elements devtools. So you can patch by breaking the aria-labelledby if you need to.
Cheers!

@zarend are you aware of that it may be just a result of endless circles done by the library, stack overflow, memory overconsumption or something? And that is not chromium fault then.

I can confirm what @hook said.  If I open the devtools and remove the aria-owns and aria-labelledby attributes from the mat-select and label, it shows the options and does not crash Chrome.
Chrome: 124.0.6367.61
Angular: ^15.2.9
Material: ^15.2.9

As @justinpjames mentioned I've found just removing the aria-owns attribute alone on the mat-label stops it from crashing.

Thanks for sharing that @justinpjames, I've been able to create a directive to apply on the mat-label of the affected inputs which fixes the crash at the expense of accessibility:
import { Directive, ElementRef, AfterViewInit } from '@angular/core';

@Directive({
  selector: '[appRemoveAriaOwns]'
})
export class RemoveAriaOwnsDirective implements AfterViewInit {
  constructor(private el: ElementRef) {}

  ngAfterViewInit() {
    this.el.nativeElement.parentElement.removeAttribute('aria-owns');
  }
}

Hello, thank you for providing as much detail as possible. Unfortunately, if this is a Chrome issue, then there's nothing that Angular components can do about this.
Have you filed an issue on Chromium?
Best Regards, Zach

Open issue on Chromium here, appreciate this isn't an Angular issue as such, but having a thread to discuss workarounds and troubleshoot is helpful since it seems to be triggered by the HTML Angular produces/

Hello, thank you for providing as much detail as possible. Unfortunately, if this is a Chrome issue, then there's nothing that Angular components can do about this.
Have you filed an issue on Chromium?
Best Regards, Zach

Open issue on Chromium here, appreciate this isn't an Angular issue as such, but having a thread to discuss workarounds and troubleshoot is helpful since it seems to be triggered by the HTML Angular produces.

If you are affected, please indicate this in the Chromium bug tracker, it helps the Chrome team to prioritize! (Top right +1 button).

Also, if you have mat-select with a placeholder but no mat-label for the mat-elect it will crash Chrome.  Luckily, you can use the current workaround if you add a mat-label with the directive above to the mat-select form-field and it will fix the issue.

As a side note, we also have this issue; the above workaround works. But the issue was only seen in MacOS running on intel CPU, our M2 Macs worked as expected.

Updating Chrome worked in my case.

I'm seeing this same issue a couple of different ways.
In both Chrome and Edge, it'll throw this error when trying to use the browser's scrollbar to scroll a mat-select. Using the mouse's wheel works fine.
In both Chrome and Edge, if mat-select has "multiple" defined, it'll crash when clicking the drop-down arrow. If I remove "multiple" it doesn't crash when clicking the drop-down arrow, but does still crash when using the scrollbar.
I don't have the "aria-owns" attribute anywhere in our project.
`

Sampling Equipment
<mat-select #samplingEquipment id="sampling-equipment-dropdown" formControlName="SamplingEquipment" multiple>
<mat-option *ngFor="let samplingEquipment of samplingEquipments" [value]="samplingEquipment.Computed">
{{samplingEquipment.Computed}}

<ng-container *ngIf="seedSamplingForm.controls.SamplingEquipment.value != seedSamplingForm.controls.PreviousSamplingEquipment.value
&& seedSamplingForm.controls.PreviousSamplingEquipment.value != null && seedSamplingForm.controls.PreviousSamplingEquipment.value != ''">

Sampling Equipment - Previous Value

`

The same problem happens in angular version 14.3.0.
Chrome version 124.0.6367.61 (official version) 64-bit
Workaround to deal with the error!
export class AppComponent implements OnInit {
  public ngOnInit(): void {
    document.addEventListener('DOMNodeInserted', function () {
      const elements = document.querySelectorAll('[aria-owns]');

      elements.forEach(element => {
        element.removeAttribute('aria-owns');
      });
    });
  }
}

Hello everyone, here is a solution that might work for some of us. Nothing more than what the amazing @ErikZA suggested earlier, just packaged as a chrome extension. Feel free to install it to your chrome until they send a hotfix
Go to chrome://extensions
Turn on developer mode
Load unpacked

https://github.com/gtzinos/chrome-hot-fix

Hi, for info, it's working when we remove aria-owns on element, but that is just not the multiple element. On Angular 15, any select could fail.
Some works for a raison i ignore:
FAIL :
<mat-form-field>
    <mat-label>Favorite food</mat-label>
    <mat-select disableOptionCentering="true" placeholder="Select placeholder">
      <mat-option *ngFor="let item of selectItems" [value]="item.value">
        {{ item.viewValue }}
      </mat-option>
    </mat-select>
    <mat-hint align="start">Hint message</mat-hint>
  </mat-form-field>

WORKS:

Select credit card

**** **** **** **** 1234
Exp. 02/25

It's impacts Edge also, so on chromium in general. Only switching to firefox is the correct solution for all users right now.

Hi Everyone, I am having the same issues. I am trying to understand the prompts that's given as resolution. I am not a techy person, so trying to understand where to enter /change these prompts. I went to Command prompt and it isn't working. Please provide the steps.
Thank you!

Hey guys, I was able to reproduce this in the component library I work on (which has the same implementation with aria/role as this for our custom dropdown). The 2 way relationship below:

parent

child

is enough to demo in chrome if you inspect the child or mouse over in Elements devtools. So you can patch by breaking the aria-labelledby if you need to.
Cheers!

So it looks like its not entirely angular. I too was able to reproduce it using a simple non angular page as explained above

Hi,
Some of our live users are also facing the same issue while using Chrome - 124.0.6367.61 and edge as well on a specific page which has dynamic drop down. We are not using angular. Upon inspecting the page we observed aria-owns tag is being added.  Dev team is unable to replicate this issue and is happening only to specific users.Will upgrading to latest chrome version resolves this issue? or is there any fix in particular?

this works for me. Just put this script tag code in your index.html and all good.

this works for me. Just put this script tag code in your index.html and all good.

Just rolled out this change. Works beautifully well. Thank you so much!!

Hi,
Thanks for the suggestion. Aria- owns attribute is removed successfully. But the code doesn't work for removing aria-labelledby tag.
Please help.

Hello!!,
This error has been critical for my organization for the last few days.
The directive workaround wasn't an option for me.
A few minutes ago, I created a hot Fix in my platform, replacing the "aria-own" directly in the js file created by angular.
Example:
sed -i 's/aria-owns/failaria-owns/g' main.8153e40XXXXXXX.js
Simple and clean :)
Good luck, angular lovers :)

This is now fixed at https://issuetracker.google.com/issues/335553723

This is now fixed at https://issuetracker.google.com/issues/335553723

That is true!!! 👍 ; I'm following the original issues too. But I suppose the fix requires a browser update or release. I can't wait for that. This type of issue will be with us for a long time because we don't have control over the versions of all the browsers our users use.

Here a workaround with mutation observer to be applied to the component consuming the mat-select:
const ariaOwnsRemover$ = new MutationObserver((mutationsList) => {
  for (const mutation of mutationsList) {
    if (mutation.type === 'attributes' && mutation.attributeName === 'aria-owns') {
      (mutation.target as Element).removeAttribute('aria-owns');
    }
  }
  });

and then in your component:
  ngOnInit() {
    ariaOwnsRemover$.observe(nativeElement, { attributes: true, subtree: true });
...

Thanks for sharing that @justinpjames, I've been able to create a directive to apply on the mat-label of the affected inputs which fixes the crash at the expense of accessibility:
import { Directive, ElementRef, AfterViewInit } from '@angular/core';

@Directive({
  selector: '[appRemoveAriaOwns]'
})
export class RemoveAriaOwnsDirective implements AfterViewInit {
  constructor(private el: ElementRef) {}

  ngAfterViewInit() {
    this.el.nativeElement.parentElement.removeAttribute('aria-owns');
  }
}

this fixed my issue

We also the exact same issue with mat multi select option when mat-label is provided.
I used solution provided by @HappyTepid . It is working for us.
Thanks.

Are there any other Angular Material components affected by the issue besides mat-select?

Since the underlying Chromium issue's been fixed and we have a wealth of workarounds for those who've yet to upgrade, I'm going to close this issue.

Please reopen it


DevTools version mismatched in flutter --version output and live DevTools instance

The DevTools version displayed in DevTools is not the same that is displayed from flutter --version (more details here).
@christopherfujino is there a chance that the version.json file is not getting updated? We grab the devtools version here: https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/cache.dart#L390 for use in the flutter --version output. Originally added in this PR.
This is reproducible on stable. Run flutter/bin/dart devtools, then look at the DevTools version in the bottom left when you open DevTools. Observe that this version is different from the one that is displayed when you run flutter --version.

Hi @kenzieschmoll, Thanks for filing the issue. I see dev tools version mismatch only on the master channel. Please check the below output. Labeling this issue as a regression.
stable
mahesh@Maheshs-MacBook-Air-M1 test_app % which dart
/Users/mahesh/Documents/flutter/bin/dart
mahesh@Maheshs-MacBook-Air-M1 test_app % dart devtools
Serving DevTools at http://<IP_ADDRESS>:9101.

Hit ctrl-c to terminate the server.

mahesh@Maheshs-MacBook-Air-M1 test_app % which flutter
/Users/mahesh/Documents/flutter/bin/flutter
mahesh@Maheshs-MacBook-Air-M1 test_app % flutter --version
Flutter 2.10.3 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 7e9793dee1 (2 weeks ago) • 2022-03-02 11:23:12 -0600
Engine • revision bd539267b4
Tools • Dart 2.16.1 • DevTools 2.9.2

master
mahesh@Maheshs-MacBook-Air-M1 test_app % /Users/mahesh/Documents/flutter_master/bin/dart devtools
Serving DevTools at http://<IP_ADDRESS>:9101.

          Hit ctrl-c to terminate the server.

mahesh@Maheshs-MacBook-Air-M1 test_app % which flutterm
flutterm: aliased to ~/Documents/flutter_master/bin/flutter
mahesh@Maheshs-MacBook-Air-M1 test_app % flutterm --version
Flutter 2.13.0-0.0.pre.103 • channel master • https://github.com/flutter/flutter.git
Framework • revision 509ddfda5c (28 hours ago) • 2022-03-15 21:10:18 -0700
Engine • revision dc22c4c7fe
Tools • Dart 2.17.0 (build 2.17.0-202.0.dev) • DevTools 2.11.4

In the stable output above, the DevTools UI shows 2.9.2+1 but in the flutter --version output it's missing the +1 - I believe that's the issue here.
Although the master one I can reproduce too - I think it may be caching issue since clearing application data in Chrome (or using a different port) shows 2.11.4 for me. @kenzieschmoll maybe https://github.com/flutter/devtools/issues/1674 - service worker related?

Thanks Elliott. However, I think there are still two separate issues here:

The devtools version from flutter --version is behind what we see in DevTools once launched (the original bug report and the example from stable above).
The devtools version from flutter --version is ahead of what we see in DevTools once launched (the example from master above). This is the browser caching issue that @elliette is looking into.

But it seems we still have an undiagnosed cause for 1).

Thanks Elliott. However, I think there are still two separate issues here:

The devtools version from flutter --version is behind what we see in DevTools once launched (the original bug report and the example from stable above).
The devtools version from flutter --version is ahead of what we see in DevTools once launched (the example from master above). This is the browser caching issue that @elliette is looking into.

But it seems we still have an undiagnosed cause for 1).

Thanks for clarifying, I'll take a look at #1

In the stable output above, the DevTools UI shows 2.9.2+1 but in the flutter --version output it's missing the +1 - I believe that's the issue here.

Removing the regression label since this is reproducible on 2.10 too

Thanks Elliott. However, I think there are still two separate issues here:

The devtools version from flutter --version is behind what we see in DevTools once launched (the original bug report and the example from stable above).
The devtools version from flutter --version is ahead of what we see in DevTools once launched (the example from master above). This is the browser caching issue that @elliette is looking into.

But it seems we still have an undiagnosed cause for 1).

Opened https://github.com/flutter/devtools/issues/3896 to track the work for #2

Regarding investigating 1)
I can confirm on latest stable I'm seeing:
Flutter 2.10.3 • channel stable • git@github.com:flutter/flutter.git
Framework • revision 7e9793dee1 (2 weeks ago) • 2022-03-02 11:23:12 -0600
Engine • revision bd539267b4
Tools • Dart 2.16.1 • DevTools 2.9.2

But from dart devtools I see 2.9.2+1.
In the cache file that we're reading, I see 2.9.2. Let me check what the package on the website says...

This is coming from the Dart SDK official release bundle:
https://storage.googleapis.com/dart-archive/channels/stable/release/2.16.1/sdk/dartsdk-macos-x64-release.zip
$ cat dart-sdk/bin/resources/devtools/version.json {"app_name":"devtools_app","version":"2.9.2","build_number":"1","package_name":"devtools_app"}
I'm guessing this is an issue with whatever is generating this file?

@kenzieschmoll it sounds like issue 2) is being tracked in https://github.com/flutter/devtools/issues/3896, and I believe that 1) is the result of dart-sdk/bin/resources/devtools/version.json being wrong (https://github.com/flutter/flutter/issues/100247#issuecomment-1072834538). I'm assigning this to you to follow up on how to fix that file.
Let me know if there's any action items in the Flutter tool for me.

Haven't seen this in over a year, and the suspicion was that the wrong version was generated during this particular DevTools build, so closing as obsolete.


Migrate to codecov.io

Fix: #233
Signed-off-by: Juncheng Zhu<EMAIL_ADDRESS>

Need access to get the badge for README.md
REF: https://docs.codecov.com/docs/status-badges

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@064752f). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Current head f1b3e8e differs from pull request most recent head 23aa1fe. Consider uploading reports for the commit 23aa1fe to get more accurate results

@@           Coverage Diff           @@
##             main     #247   +/-   ##
=======================================
  Coverage        ?   70.57%
=======================================
  Files           ?       35
  Lines           ?     3055
  Branches        ?        0
=======================================
  Hits            ?     2156
  Misses          ?      669
  Partials        ?      230

Help us with your feedback. Take ten seconds to tell us how you rate us.


Difference vs ora - double printing on exit

Thanks for the great work to help make the ecosystem more efficient!
I would like to replace our usage of ora with nanospinner in https://github.com/nrwl/nx - our overall tracking issue is here: https://github.com/es-tooling/ecosystem-cleanup/issues/117
I went through our usage and fortunately we don't require the multiple spinners support. Things are nearly ready to go but I found one blocking bug, here is a repro:
https://stackblitz.com/edit/stackblitz-starters-dmnx9n?file=package.json&view=editor

Run node ora.js
Run node nanospinner.js

You will see that ora does not print again after the error message is printed as expected, but nanospinner does.

@JamesHenry I'll take a look soon

@JamesHenry fix relese 1.2.2

Ah cool thank you @usmanyunusov, I also wanted to make you aware of the discussion happening here: https://github.com/tinylibs/picospinner/pull/5


Fix sporadic Elasticsearch test failures

Hopefully resolves #426 and #438

Have you considered instead using https://www.testcontainers.org/modules/elasticsearch/ ?

No, but I totally agree with going in that direction.
I thought this was going to be an easy "fix" using Spock's @Retry annotation until I discovered that @Retry only applies to the tests themselves, and not to the setup, which is where these bind exceptions occur.

Your approach is certainly more applicable: the majority of tests which start some server can be solved that way. But it needs at least some documentation. Currently it leaves bad taste in my mouth: "Something is broken here, don't know what exactly, let us just retry".
Another solution, which requires more effort, is to run Elastic in Testcontainer. And probably to run only 1 container for all Elastic related tests, if that is possible. Will speed things up as well.
I am OK with this PR as a short term solution to flakiness, but I think we can do better in a long run.

👍 good point, added doc to withRetryOnBindException()


Updated to support different model

currently not working for my Pro X Superlight,  So I just added the ID for it

Sorry, but the ID you added is the ID of the receiver, we can't merge this because a different device might use the same receiver, so same ID, causing a collision.
This needs to be supported at the kernel level, I believe there's a PR for that but is stalled, would need to look into it.
That said, you can use this .device locally to use your device with libratbad.
See #1118


Added parameters in config file to set the key and value columns name

Added parameters in config file to set the key and value columns name. This parameters are used in migration when is created the table, and used in DatabaseSettingStore to persist and query the data using the setted column names.

The properties should be named keyColumn and valueColumn.
Make sure to use tabs for indentation to be consistent with the rest of the code - I know it's not the community standard but it is what it is.

If you push your changes to your forked repository's master branch, the pull request will update automatically.

Thanks!


_sg_gl_reset_state_cache assert failure on GLES2

I'm trying to run sokol on RaspberryPI which is OpenGL-ES2. and at the initialization I get assert failure in here.
By checking the documentation, I guess the error is legit because no VAO is binded.

Hmm, glDisableVertexAttribArray() isn't a VAO function though.
I seem to remember that the Raspi2's GL implementation doesn't support 16 vertex attributes, instead the number must be queried with glGetIntegerv(GL_MAX_VERTEX_ATTRIBS, &max_vertex_attrs) when the GL backend is setup, and the min(max_vertex_attrs, SG_MAX_VERTEX_ATTRIBUTES) must be used in loop like the one that generates the error.
I'm surprised I didn't think of that. I'll close this ticket and write a new one to fix this specific problem.


Alt-F4 don't close main PowerToys Settings window

Microsoft PowerToys version
"0.51.1"
Running as admin

[X] Yes

Area(s) with issue?
General, Settings
Steps to reproduce
Minor issue but still. I'm using my keyboard a lot, so closing tabs with ctrl+F4 and windows/apps with alt+F4 is just in the fingers. But no, not for PowerToys Settings windows.
Steps

Open PowerToys Settings, e.g. by clicking the tray icon (and waiting for way too long, wondering "did I misfire?"
Press alt+F4
Profit...

PowerToysReport_2022-01-13-11-36-10.zip
.
✔ Expected Behavior
Window closing.
❌ Actual Behavior
Nothing happens.
Other Software
No response

Sorry, forgot to search!
https://github.com/microsoft/PowerToys/issues/7243


feat: add [rich text editor] to/in [form inputs]

🙋 Feature Request

it can be use for  reciving  advanced  scenario such cod for  fifrent language  ading  external url and embeding  pictures and formating text for blogs and son
🤔 Expected Behavior

somthing like CKEditor
😯 Current Behavior

💁 Possible Solution

🔦 Context

💻 Examples

Hi,
This has been discussed before. We will not be adding such a component to the library anytime soon.


[Event Hubs] Update system property types

Summary
The focus of these changes is to update the type of several existing values in the EventData.SystemProperties collection have been changed  so that they are properly represented as .NET string types.  Previously,
the underlying AMQP types were unintentionally returned, forcing callers to call ToString() to read the value.  This is a behavioral breaking change that will impacts only those callers  who were explicitly casting system property values to AmqpAddress or  AmqpMessageId before calling ToString.
The affected system properties are:

MessageId
CorelationId
To
ReplyTo

/azp run net - eventhub - tests

API change check
API changes are not detected in this pull request.