text:
SternalBoard not shown (IllegalArgumentException)

I get the following error, when a user connects to the server. I didn't found any other logs, that enclose the error.
The Board isn't shown.
However while booting the server or reloading the SternalBoard config, no error occurs.
The Placeholder Api is also the newest Version.
Caused by: java.lang.IllegalArgumentException: Attempt to get net.minecraft.server.level.PlayerInteractManager field "net.minecraft.server.level.EntityPlayer.e" with illegal data type conversion to int
	at jdk.internal.reflect.FieldAccessorImpl.newGetIllegalArgumentException(Unknown Source) ~[?:?]
	at jdk.internal.reflect.FieldAccessorImpl.newGetIntIllegalArgumentException(Unknown Source) ~[?:?]
	at jdk.internal.reflect.MethodHandleObjectFieldAccessorImpl.getInt(Unknown Source) ~[?:?]
	at java.lang.reflect.Field.getInt(Unknown Source) ~[?:?]
	at com.extendedclip.papi.expansion.player.PlayerUtil$1.apply(PlayerUtil.java:66) ~[?:?]
	at com.extendedclip.papi.expansion.player.PlayerUtil$1.apply(PlayerUtil.java:50) ~[?:?]
	at com.extendedclip.papi.expansion.player.PlayerUtil.getPing(PlayerUtil.java:122) ~[?:?]
	at com.extendedclip.papi.expansion.player.PlayerExpansion.retrievePing(PlayerExpansion.java:481) ~[?:?]
	at com.extendedclip.papi.expansion.player.PlayerExpansion.onRequest(PlayerExpansion.java:403) ~[?:?]
	at me.clip.placeholderapi.replacer.CharsReplacer.apply(CharsReplacer.java:119) ~[PlaceholderAPI-2.11.3.jar:?]
	at me.clip.placeholderapi.PlaceholderAPI.setPlaceholders(PlaceholderAPI.java:71) ~[PlaceholderAPI-2.11.3.jar:?]
	at me.clip.placeholderapi.PlaceholderAPI.setPlaceholders(PlaceholderAPI.java:99) ~[PlaceholderAPI-2.11.3.jar:?]
	at com.xism4.sternalboard.utils.TextUtils.processPlaceholders(TextUtils.java:63) ~[SternalBoard-2.2.0.jar:?]
	at com.xism4.sternalboard.Scoreboards.lambda$updateFromSection$0(Scoreboards.java:28) ~[SternalBoard-2.2.0.jar:?]
	at java.util.ArrayList.replaceAllRange(Unknown Source) ~[?:?]
	at java.util.ArrayList.replaceAll(Unknown Source) ~[?:?]
	at com.xism4.sternalboard.Scoreboards.updateFromSection(Scoreboards.java:28) ~[SternalBoard-2.2.0.jar:?]
	at com.xism4.sternalboard.managers.ScoreboardManager.setScoreboard(ScoreboardManager.java:80) ~[SternalBoard-2.2.0.jar:?]
	at com.xism4.sternalboard.managers.ScoreboardManager.toggle(ScoreboardManager.java:110) ~[SternalBoard-2.2.0.jar:?]
	at com.xism4.sternalboard.commands.SternalCommand.toggleSubcommand(SternalCommand.java:81) ~[SternalBoard-2.2.0.jar:?]
	at com.xism4.sternalboard.commands.SternalCommand.onCommand(SternalCommand.java:42) ~[SternalBoard-2.2.0.jar:?]
	at org.bukkit.command.PluginCommand.execute(PluginCommand.java:45) ~[paper-api-1.20.1-R0.1-SNAPSHOT.jar:?]
	... 23 more
```

It was an error with the PlaceholderAPI Cache, my bad.

repo: ShieldCommunity/SternalBoard


text:
move codegen to separate library

depends on https://github.com/ShiftLeftSecurity/product/issues/4176

depends on https://github.com/ShiftLeftSecurity/overflowdb-codegen/pull/2

source: gharchive/pull-request

repo: ShiftLeftSecurity/codepropertygraph

license_type: permissive

license_source: github-api


text:
当差异行的下一行多一个空行时，对比失败

大佬，你好，红框中的行，没有高亮显示差异word

另外想问下，vue2.6支持v-code-diff的最大版本是多少，好像直接安装最新的会报错

你好，2.6的情况我看下，理论上一直是兼容的

实测最新版（1.13.1）可以兼容 vue2.6

好的，非常感谢。我的第一个问题，有思路么

好的，非常感谢。我的第一个问题，有思路么

可以把文本贴给我看下么

server {
        listen 443 ssl;
        listen  80;
        server_name     logan-gateway.dev.local;
        access_log  /data/nginxlogs/log-gat.access.log log_access;
        error_log   /data/nginxlogs/log-gateway.error.log debug;

        ssl_certificate /etc/nginx/ssl/nginx-selfsigned.crt;
        ssl_certificate_key /etc/nginx/ssl/nginx-selfsigned.key;
        ssl_session_timeout 5m;
        ssl_protocols TLSv1 TLSv1.1 TLSv1.2;

server {
        listen 443 ssl;
        listen  80;
        server_name     logan-gateway.test.aeroht.com;
        access_log  /data/nginxlogs/log-gateway.test.com.access.log log_access;
        error_log   /data/nginxlogs/log-gateway.test.com.error.log debug;

        ssl_certificate /etc/nginx/ssl/test.com.pem;
        ssl_certificate_key /etc/nginx/ssl/test.com.key;

        ssl_session_timeout 5m;
        ssl_protocols TLSv1 TLSv1.1 TLSv1.2;

您好，这是文本

@jedi201321 您好，默认是参考 github 的设计，当一块代码块新增和删除行数不等时，只显示行级差异。如果希望强行比较，可以把 forceInlineComparison prop 设为 true

@Shimada666 好的，明白了  感谢感谢

source: gharchive/issue

license: MIT


text:
Error on IOS platform

I tried to build this project on IOS platform, but app got frozen after launching.
"Execution of the command buffer was aborted due to an error during execution. Ignored (for causing prior/excessive GPU errors) (IOAF code 4)"
I got this error, have you ever try it on IOS?

Sorry for the late reply, I do not have any IOS devices and cannot test on them, though I would think it's a problem of compute shader which is not a function available in all devices (like IOS).

repo: Shinao/Unity-GPU-Boids


text:
Documentation

Validate documentation for all extensions:

Rates:

[x] preinstall
[x] postinstall
[x] extensions.yaml
[x] generate readme

Track Label:

[ ] preinstall
[ ] postinstall
[ ] extensions.yaml
[ ] generate readme

Validate Address:

[ ] preinstall
[ ] postinstall
[ ] extensions.yaml
[ ] generate readme

@forksofpower how close is this to being done?

authors: andyhite forksofpower

repo: ShipEngine/firebase-extensions


text:
🛑 ShippersEdge Rates API is down

In c73d6e2, ShippersEdge Rates API (https://api.shippersedge.com/v2/rates/shipment/365186086) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ShippersEdge Rates API is back up in 3512bad.

repo: ShippersEdge/upptime


text:
Slide

layout: slide
title: "Welcome to our second slide!"
Your text 😄
Use the left arrow to go back!

Hi

repo: Shivraj-Dhaytadak/github-slideshow


text:
Memory issues

-Memory not freed after downsizing
-Frame buffer not freed on app close
-OS has to reclaim all resources on throw

Fix implemented in latest unstable (not yet committed).

repo: Shmizmin/Vulkan-Renderer


text:
[Bug]: "shopify theme dev" errors on ARM-based macs (Ventura)

Please confirm that you have:

[X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[X] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
Theme
Expected behavior
It should have ran the command with no errors and allowed me to preview a theme
Actual behavior
Spat out a very long stack trace about Ruby / gems. I believe that the culprit is a line which says:
/opt/homebrew/Cellar/ruby/3.2.0/lib/libruby.3.2.dylib, building for macOS-x86_64 but attempting to link with file built for macOS-arm64 Undefined symbols for architecture x86_64:
This makes me believe that the issue here is that the shopify cli is trying to do something with ruby which isn't working on ARM architectures, just x86 architectures.
Stack trace
/opt/homebrew/Cellar/shopify-cli/3.39.0/libexec/lib/node_modules/@shopify/cli/node_modules/yoga-layout-prebuilt/yoga-layout/build/Release/nbind.js:53
        throw ex;
        ^

ExternalError: Command failed with exit code 5: /opt/homebrew/opt/ruby/bin/bundle install
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

current directory:
/Users/isaacmattern/Library/Caches/shopify-cli-nodejs/vendor/ruby-cli/2.34.0/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c
/opt/homebrew/opt/ruby/bin/ruby -I
/opt/homebrew/Cellar/ruby/3.2.0/lib/ruby/3.2.0 extconf.rb
checking for ffi.h... no
checking for ffi.h in
/usr/local/include,/usr/include/ffi,/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/ffi,/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/ffi...
yes
checking for ffi_prep_closure_loc() in -lffi... yes
checking for ffi_prep_cif_var()... yes
checking for ffi_raw_call()... yes
checking for ffi_prep_raw_closure()... yes
checking for whether -pthread is accepted as LDFLAGS... yes
creating extconf.h
creating Makefile

current directory:
/Users/isaacmattern/Library/Caches/shopify-cli-nodejs/vendor/ruby-cli/2.34.0/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c
make DESTDIR\= sitearchdir\=./.gem.20230131-63128-tv6ap
sitelibdir\=./.gem.20230131-63128-tv6ap clean

current directory:
/Users/isaacmattern/Library/Caches/shopify-cli-nodejs/vendor/ruby-cli/2.34.0/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c
make DESTDIR\= sitearchdir\=./.gem.20230131-63128-tv6ap
sitelibdir\=./.gem.20230131-63128-tv6ap
compiling AbstractMemory.c
compiling ArrayType.c
compiling Buffer.c
compiling Call.c
compiling ClosurePool.c
compiling DynamicLibrary.c
compiling Function.c
compiling FunctionInfo.c
compiling LastError.c
compiling LongDouble.c
compiling MappedType.c
compiling MemoryPointer.c
compiling MethodHandle.c
compiling Platform.c
compiling Pointer.c
compiling Struct.c
compiling StructByValue.c
compiling StructLayout.c
compiling Thread.c
compiling Type.c
compiling Types.c
compiling Variadic.c
compiling ffi.c
linking shared-object ffi_c.bundle
ld: warning: ignoring file
/opt/homebrew/Cellar/ruby/3.2.0/lib/libruby.3.2.dylib, building for macOS-x86_64
but attempting to link with file built for macOS-arm64
Undefined symbols for architecture x86_64:
  "_rb_ary_detransient", referenced from:
      _memory_put_array_of_int8 in AbstractMemory.o
      _memory_put_array_of_uint8 in AbstractMemory.o
      _memory_put_array_of_int16 in AbstractMemory.o
      _memory_put_array_of_uint16 in AbstractMemory.o
      _memory_put_array_of_int32 in AbstractMemory.o
      _memory_put_array_of_uint32 in AbstractMemory.o
      _memory_put_array_of_int64 in AbstractMemory.o
      ...
  "_rb_ary_dup", referenced from:
      _fntype_param_types in FunctionInfo.o
      _struct_layout_fields in StructLayout.o
      _struct_layout_members in StructLayout.o
      _struct_layout_to_a in StructLayout.o
  "_rb_ary_entry", referenced from:
      _invoke_callback in Function.o
      _fntype_initialize in FunctionInfo.o
      _struct_layout_initialize in StructLayout.o
      _variadic_initialize in Variadic.o
      _variadic_invoke in Variadic.o
  "_rb_ary_new", referenced from:
      _struct_initialize in Struct.o
  "_rb_ary_new_capa", referenced from:
      _memory_get_array_of_int8 in AbstractMemory.o
      _memory_get_array_of_uint8 in AbstractMemory.o
      _memory_get_array_of_int16 in AbstractMemory.o
      _memory_get_array_of_uint16 in AbstractMemory.o
      _memory_get_array_of_int32 in AbstractMemory.o
      _memory_get_array_of_uint32 in AbstractMemory.o
      _memory_get_array_of_int64 in AbstractMemory.o
      ...
  "_rb_ary_new_from_values", referenced from:
      _struct_initialize in Struct.o
  "_rb_ary_push", referenced from:
      _memory_get_array_of_int8 in AbstractMemory.o
      _memory_get_array_of_uint8 in AbstractMemory.o
      _memory_get_array_of_int16 in AbstractMemory.o
      _memory_get_array_of_uint16 in AbstractMemory.o
      _memory_get_array_of_int32 in AbstractMemory.o
      _memory_get_array_of_uint32 in AbstractMemory.o
      _memory_get_array_of_int64 in AbstractMemory.o
      ...
  "_rb_block_given_p", referenced from:
      _buffer_initialize in Buffer.o
      _rbffi_SetupCallParams in Call.o
      _function_initialize in Function.o
      _memptr_initialize in MemoryPointer.o
  "_rb_block_proc", referenced from:
      _rbffi_SetupCallParams in Call.o
      _function_initialize in Function.o
  "_rb_cFalseClass", referenced from:
      _rbffi_Function_ForProc in Function.o
      _rbffi_Type_Init in Type.o
  "_rb_cFloat", referenced from:
      _rbffi_Function_ForProc in Function.o
      _rbffi_Type_Init in Type.o
  "_rb_cInteger", referenced from:
      _rbffi_Function_ForProc in Function.o
      _rbffi_Type_Init in Type.o
  "_rb_cModule", referenced from:
      _function_attach in Function.o
  "_rb_cNilClass", referenced from:
      _rbffi_Type_Init in Type.o
  "_rb_cObject", referenced from:
      _rbffi_AbstractMemory_Init in AbstractMemory.o
      _rbffi_DynamicLibrary_Init in DynamicLibrary.o
      _rbffi_longdouble_new in LongDouble.o
      _bigdecimal_load in LongDouble.o
      _rbffi_num2longdouble in LongDouble.o
      _rbffi_Struct_Init in Struct.o
      _rbffi_StructLayout_Init in StructLayout.o
      ...
  "_rb_cProc", referenced from:
      _function_init in Function.o
      _invoke_callback in Function.o
      _function_field_put in StructLayout.o
  "_rb_cString", referenced from:
      _array_field_put in StructLayout.o
  "_rb_cSymbol", referenced from:
      _rbffi_Function_ForProc in Function.o
      _rbffi_Type_Init in Type.o
  "_rb_cTrueClass", referenced from:
      _rbffi_Function_ForProc in Function.o
      _rbffi_Type_Init in Type.o
  "_rb_call_super", referenced from:
      _inline_array_to_s in Struct.o
  "_rb_class2name", referenced from:
      _struct_set_layout in Struct.o
      _struct_class_layout in Struct.o
  "_rb_class_new_instance", referenced from:
      _function_initialize in Function.o
      _memptr_s_from_string in MemoryPointer.o
      _rbffi_Pointer_Init in Pointer.o
      _inline_array_aref in Struct.o
      _array_field_get in StructLayout.o
      _rbffi_NativeValue_ToRuby in Types.o
  "_rb_const_defined", referenced from:
      _rbffi_num2longdouble in LongDouble.o
  "_rb_const_get", referenced from:
      _bigdecimal_load in LongDouble.o
      _rbffi_num2longdouble in LongDouble.o
      _rbffi_Type_Init in Type.o
      _variadic_invoke in Variadic.o
  "_rb_const_set", referenced from:
      _rbffi_Type_Init in Type.o
  "_rb_cv_set", referenced from:
      _function_attach in Function.o
  "_rb_data_object_zalloc", referenced from:
      _memory_allocate in AbstractMemory.o
      _array_type_s_allocate in ArrayType.o
      _buffer_allocate in Buffer.o
      _buffer_alloc_inout in Buffer.o
      _buffer_order in Buffer.o
      _slice in Buffer.o
      _library_allocate in DynamicLibrary.o
      ...
  "_rb_debug_rstring_null_ptr", referenced from:
      _memory_put_string in AbstractMemory.o
      _memory_put_bytes in AbstractMemory.o
      _RSTRING_PTR in FunctionInfo.o
      _rbffi_num2longdouble in LongDouble.o
      _ptr_free.cold.1 in Pointer.o
      _RSTRING_PTR in Variadic.o
  "_rb_define_alias", referenced from:
      _rbffi_AbstractMemory_Init in AbstractMemory.o
      _rbffi_Buffer_Init in Buffer.o
      _rbffi_Pointer_Init in Pointer.o
      _rbffi_Struct_Init in Struct.o
  "_rb_define_alloc_func", referenced from:
      _rbffi_AbstractMemory_Init in AbstractMemory.o
      _rbffi_ArrayType_Init in ArrayType.o
      _rbffi_Buffer_Init in Buffer.o
      _rbffi_DynamicLibrary_Init in DynamicLibrary.o
      _rbffi_Function_Init in Function.o
      _rbffi_FunctionInfo_Init in FunctionInfo.o
      _rbffi_MappedType_Init in MappedType.o
      ...
  "_rb_define_attr", referenced from:
      _rbffi_DynamicLibrary_Init in DynamicLibrary.o
  "_rb_define_class_under", referenced from:
      _rbffi_AbstractMemory_Init in AbstractMemory.o
      _rbffi_ArrayType_Init in ArrayType.o
      _rbffi_Buffer_Init in Buffer.o
      _rbffi_DynamicLibrary_Init in DynamicLibrary.o
      _rbffi_Function_Init in Function.o
      _rbffi_FunctionInfo_Init in FunctionInfo.o
      _rbffi_MappedType_Init in MappedType.o
      ...
  "_rb_define_const", referenced from:
      _rbffi_ArrayType_Init in ArrayType.o
      _rbffi_DynamicLibrary_Init in DynamicLibrary.o
      _rbffi_FunctionInfo_Init in FunctionInfo.o
      _rbffi_Platform_Init in Platform.o
      _rbffi_Pointer_Init in Pointer.o
      _rbffi_StructByValue_Init in StructByValue.o
      _rbffi_Type_Init in Type.o
      ...
  "_rb_define_method", referenced from:
      _rbffi_AbstractMemory_Init in AbstractMemory.o
      _rbffi_ArrayType_Init in ArrayType.o
      _rbffi_Buffer_Init in Buffer.o
      _rbffi_DynamicLibrary_Init in DynamicLibrary.o
      _rbffi_Function_Init in Function.o
      _function_attach in Function.o
      _rbffi_FunctionInfo_Init in FunctionInfo.o
      ...
  "_rb_define_module", referenced from:
      _Init_ffi_c in ffi.o
  "_rb_define_module_function", referenced from:
      _rbffi_LastError_Init in LastError.o
  "_rb_define_module_under", referenced from:
      _rbffi_LastError_Init in LastError.o
      _rbffi_Platform_Init in Platform.o
      _rbffi_Type_Init in Type.o
  "_rb_define_private_method", referenced from:
      _rbffi_Struct_Init in Struct.o
  "_rb_define_singleton_method", referenced from:
      _rbffi_Buffer_Init in Buffer.o
      _rbffi_DynamicLibrary_Init in DynamicLibrary.o
      _function_attach in Function.o
      _rbffi_MemoryPointer_Init in MemoryPointer.o
  "_rb_eArgError", referenced from:
      _rbffi_AbstractMemory_Cast in AbstractMemory.o
      _memory_put_array_of_int8 in AbstractMemory.o
      _memory_get_array_of_int8 in AbstractMemory.o
      _memory_put_array_of_uint8 in AbstractMemory.o
      _memory_get_array_of_uint8 in AbstractMemory.o
      _memory_put_array_of_int16 in AbstractMemory.o
      _memory_get_array_of_int16 in AbstractMemory.o
      ...
  "_rb_eException", referenced from:
      _rbffi_CallFunction in Call.o
      _callback_invoke in Function.o
      _callback_with_gvl in Function.o
      _async_cb_call in Function.o
      _variadic_invoke in Variadic.o
  "_rb_eFatal", referenced from:
      _rbffi_MethodHandle_Init in MethodHandle.o
  "_rb_eIndexError", referenced from:
      _memory_get_int8 in AbstractMemory.o
      _memory_put_uint8 in AbstractMemory.o
      _memory_get_uint8 in AbstractMemory.o
      _memory_read_int8 in AbstractMemory.o
      _memory_write_uint8 in AbstractMemory.o
      _memory_read_uint8 in AbstractMemory.o
      _memory_put_array_of_int8 in AbstractMemory.o
      ...
  "_rb_eLoadError", referenced from:
      _library_initialize in DynamicLibrary.o
  "_rb_eNoMemError", referenced from:
      _function_init in Function.o
      _rbffi_MethodHandle_Alloc in MethodHandle.o
  "_rb_eNoMethodError", referenced from:
      _mapped_initialize in MappedType.o
  "_rb_eNotImpError", referenced from:
      _array_field_put in StructLayout.o
  "_rb_eRangeError", referenced from:
      _memory_put_bytes in AbstractMemory.o
  "_rb_eRuntimeError", referenced from:
      _rbffi_AbstractMemory_Error in AbstractMemory.o
      _rbffi_AbstractMemory_Init in AbstractMemory.o
      _rbffi_Closure_Alloc in ClosurePool.o
      _symbol_initialize_copy in DynamicLibrary.o
      _function_initialize_copy in Function.o
      _function_attach in Function.o
      _function_release in Function.o
      ...
  "_rb_eTypeError", referenced from:
      _rbffi_SetupCallParams in Call.o
      _function_init in Function.o
      _fntype_initialize in FunctionInfo.o
      _mapped_initialize in MappedType.o
      _ptr_initialize in Pointer.o
      _struct_set_pointer in Struct.o
      _struct_set_layout in Struct.o
      ...
  "_rb_ensure", referenced from:
      _buffer_initialize in Buffer.o
      _memptr_initialize in MemoryPointer.o
  "_rb_error_arity", referenced from:
      _memory_get_string in AbstractMemory.o
      _memory_put_bytes in AbstractMemory.o
      _memory_get_array_of_string in AbstractMemory.o
      _buffer_initialize in Buffer.o
      _buffer_order in Buffer.o
      _function_initialize in Function.o
      _fntype_initialize in FunctionInfo.o
      ...
  "_rb_exc_new_str", referenced from:
      _memory_get in AbstractMemory.o
      _memory_put in AbstractMemory.o
  "_rb_exc_raise", referenced from:
      _memory_get in AbstractMemory.o
      _memory_put in AbstractMemory.o
      _rbffi_CallFunction in Call.o
      _variadic_invoke in Variadic.o
  "_rb_fix2int", referenced from:
      _memory_put_array_of_int8 in AbstractMemory.o
      _memory_put_array_of_int16 in AbstractMemory.o
      _memory_put_array_of_int32 in AbstractMemory.o
      _memory_get_array_of_string in AbstractMemory.o
      _memory_copy_from in AbstractMemory.o
      _memory_op_put_int8 in AbstractMemory.o
      _memory_op_put_int16 in AbstractMemory.o
      ...
  "_rb_float_new", referenced from:
      _memory_get_float32 in AbstractMemory.o
      _memory_read_float32 in AbstractMemory.o
      _memory_get_array_of_float32 in AbstractMemory.o
      _memory_get_float64 in AbstractMemory.o
      _memory_read_float64 in AbstractMemory.o
      _memory_get_array_of_float64 in AbstractMemory.o
      _memory_op_get_float32 in AbstractMemory.o
      ...
  "_rb_funcall", referenced from:
      _rbffi_SetupCallParams in Call.o
      _function_init in Function.o
      _async_cb_event in Function.o
      _rbffi_longdouble_new in LongDouble.o
      _rbffi_num2longdouble in LongDouble.o
      _memptr_s_from_string in MemoryPointer.o
      _ptr_free.cold.1 in Pointer.o
      ...
  "_rb_funcallv", referenced from:
      _memory_aref in AbstractMemory.o
      _get_pointer_value in AbstractMemory.o
      _rbffi_SetupCallParams in Call.o
      _getPointer in Call.o
      _invoke_callback in Function.o
      _fntype_initialize in FunctionInfo.o
      _mapped_initialize in MappedType.o
      ...
  "_rb_gc_mark", referenced from:
      _array_type_mark in ArrayType.o
      _buffer_mark in Buffer.o
      _symbol_mark in DynamicLibrary.o
      _function_mark in Function.o
      _fntype_mark in FunctionInfo.o
      _mapped_mark in MappedType.o
      _ptr_mark in Pointer.o
      ...
  "_rb_gc_mark_locations", referenced from:
      _fntype_mark in FunctionInfo.o
      _struct_mark in Struct.o
  "_rb_gc_writebarrier_unprotect", referenced from:
      _memory_put_array_of_int8 in AbstractMemory.o
      _memory_put_array_of_uint8 in AbstractMemory.o
      _memory_put_array_of_int16 in AbstractMemory.o
      _memory_put_array_of_uint16 in AbstractMemory.o
      _memory_put_array_of_int32 in AbstractMemory.o
      _memory_put_array_of_uint32 in AbstractMemory.o
      _memory_put_array_of_int64 in AbstractMemory.o
      ...
  "_rb_global_variable", referenced from:
      _rbffi_AbstractMemory_Init in AbstractMemory.o
      _rbffi_ArrayType_Init in ArrayType.o
      _rbffi_Buffer_Init in Buffer.o
      _rbffi_DynamicLibrary_Init in DynamicLibrary.o
      _rbffi_Function_Init in Function.o
      _rbffi_FunctionInfo_Init in FunctionInfo.o
      _rbffi_MappedType_Init in MappedType.o
      ...
  "_rb_hash_aref", referenced from:
      _rbffi_Function_ForProc in Function.o
      _fntype_initialize in FunctionInfo.o
      _struct_aref in Struct.o
      _struct_aset in Struct.o
      _struct_field in Struct.o
      _struct_layout_aref in StructLayout.o
      _variadic_initialize in Variadic.o
      ...
  "_rb_hash_aset", referenced from:
      _rbffi_Function_ForProc in Function.o
      _struct_layout_initialize in StructLayout.o
  "_rb_hash_lookup", referenced from:
      _rbffi_type_size in Type.o
      _rbffi_Type_Lookup in Type.o
  "_rb_hash_new", referenced from:
      _rbffi_Function_ForProc in Function.o
      _struct_layout_initialize in StructLayout.o
      _rbffi_Type_Init in Type.o
  "_rb_id2sym", referenced from:
      _buffer_order in Buffer.o
      _fntype_initialize in FunctionInfo.o
      _ptr_order in Pointer.o
      _variadic_initialize in Variadic.o
  "_rb_include_module", referenced from:
      _rbffi_Struct_Init in Struct.o
  "_rb_int2big", referenced from:
      _memory_get_long in AbstractMemory.o
      _memory_read_long in AbstractMemory.o
      _memory_get_array_of_long in AbstractMemory.o
      _memory_size in AbstractMemory.o
      _memory_op_get_long in AbstractMemory.o
      _invoke_callback in Function.o
      _memptr_s_from_string in MemoryPointer.o
      ...
  "_rb_intern2", referenced from:
      _rbffi_AbstractMemory_Init in AbstractMemory.o
      _buffer_order in Buffer.o
      _rbffi_Call_Init in Call.o
      _function_init in Function.o
      _rbffi_Function_Init in Function.o
      _async_cb_event in Function.o
      _fntype_initialize in FunctionInfo.o
      ...
  "_rb_iv_get", referenced from:
      _variadic_invoke in Variadic.o
  "_rb_iv_set", referenced from:
      _library_initialize in DynamicLibrary.o
      _variadic_initialize in Variadic.o
  "_rb_ivar_defined", referenced from:
      _rbffi_Function_ForProc in Function.o
      _struct_class_layout in Struct.o
  "_rb_ivar_get", referenced from:
      _rbffi_Function_ForProc in Function.o
      _struct_class_layout in Struct.o
      _sbv_initialize in StructByValue.o
  "_rb_ivar_set", referenced from:
      _rbffi_Function_ForProc in Function.o
      _struct_set_pointer in Struct.o
      _struct_set_layout in Struct.o
  "_rb_ll2inum", referenced from:
      _memory_get_int64 in AbstractMemory.o
      _memory_read_int64 in AbstractMemory.o
      _memory_get_array_of_int64 in AbstractMemory.o
      _memory_op_get_int64 in AbstractMemory.o
      _invoke_callback in Function.o
      _rbffi_NativeValue_ToRuby in Types.o
  "_rb_mEnumerable", referenced from:
      _rbffi_Struct_Init in Struct.o
  "_rb_mKernel", referenced from:
      _rbffi_longdouble_new in LongDouble.o
  "_rb_num2dbl", referenced from:
      _memory_put_float32 in AbstractMemory.o
      _memory_write_float32 in AbstractMemory.o
      _memory_put_array_of_float32 in AbstractMemory.o
      _memory_put_float64 in AbstractMemory.o
      _memory_write_float64 in AbstractMemory.o
      _memory_put_array_of_float64 in AbstractMemory.o
      _memory_op_put_float32 in AbstractMemory.o
      ...
  "_rb_num2int", referenced from:
      _memory_put_array_of_int8 in AbstractMemory.o
      _memory_put_array_of_int16 in AbstractMemory.o
      _memory_put_array_of_int32 in AbstractMemory.o
      _memory_get_array_of_string in AbstractMemory.o
      _memory_copy_from in AbstractMemory.o
      _memory_op_put_int8 in AbstractMemory.o
      _memory_op_put_int16 in AbstractMemory.o
      ...
  "_rb_num2ll", referenced from:
      _memory_put_array_of_int64 in AbstractMemory.o
      _memory_op_put_int64 in AbstractMemory.o
      _rbffi_SetupCallParams in Call.o
      _invoke_callback in Function.o
      _ptr_initialize in Pointer.o
  "_rb_num2long", referenced from:
      _memory_put_int8 in AbstractMemory.o
      _memory_get_int8 in AbstractMemory.o
      _memory_put_uint8 in AbstractMemory.o
      _memory_get_uint8 in AbstractMemory.o
      _memory_put_array_of_int8 in AbstractMemory.o
      _memory_get_array_of_int8 in AbstractMemory.o
      _memory_put_array_of_uint8 in AbstractMemory.o
      ...
  "_rb_num2uint", referenced from:
      _memory_put_uint8 in AbstractMemory.o
      _memory_write_uint8 in AbstractMemory.o
      _memory_put_array_of_uint8 in AbstractMemory.o
      _memory_put_uint16 in AbstractMemory.o
      _memory_write_uint16 in AbstractMemory.o
      _memory_put_array_of_uint16 in AbstractMemory.o
      _memory_put_uint32 in AbstractMemory.o
      ...
  "_rb_num2ull", referenced from:
      _memory_put_array_of_uint64 in AbstractMemory.o
      _memory_op_put_uint64 in AbstractMemory.o
      _get_pointer_value in AbstractMemory.o
      _rbffi_SetupCallParams in Call.o
      _invoke_callback in Function.o
  "_rb_num2ulong", referenced from:
      _memory_put_array_of_ulong in AbstractMemory.o
      _memory_aref in AbstractMemory.o
      _memory_op_put_ulong in AbstractMemory.o
      _rbffi_SetupCallParams in Call.o
      _invoke_callback in Function.o
  "_rb_obj_classname", referenced from:
      _function_init in Function.o
      _ptr_inspect in Pointer.o
      _struct_set_pointer in Struct.o
      _struct_set_layout in Struct.o
      _inline_array_aref in Struct.o
      _inline_array_aset in Struct.o
      _struct_field_initialize in StructLayout.o
      ...
  "_rb_obj_dup", referenced from:
      _struct_order in Struct.o
  "_rb_obj_is_instance_of", referenced from:
      _sbv_initialize in StructByValue.o
      _array_field_put in StructLayout.o
  "_rb_obj_is_kind_of", referenced from:
      _rbffi_AbstractMemory_Cast in AbstractMemory.o
      _memory_put_array_of_int8 in AbstractMemory.o
      _memory_get_array_of_int8 in AbstractMemory.o
      _memory_put_array_of_uint8 in AbstractMemory.o
      _memory_get_array_of_uint8 in AbstractMemory.o
      _memory_put_array_of_int16 in AbstractMemory.o
      _memory_get_array_of_int16 in AbstractMemory.o
      ...
  "_rb_raise", referenced from:
      _rbffi_AbstractMemory_Cast in AbstractMemory.o
      _rbffi_AbstractMemory_Error in AbstractMemory.o
      _memory_get_int8 in AbstractMemory.o
      _memory_put_uint8 in AbstractMemory.o
      _memory_get_uint8 in AbstractMemory.o
      _memory_read_int8 in AbstractMemory.o
      _memory_write_uint8 in AbstractMemory.o
      ...
  "_rb_require", referenced from:
      _bigdecimal_load in LongDouble.o
  "_rb_rescue", referenced from:
      _rbffi_longdouble_new in LongDouble.o
  "_rb_rescue2", referenced from:
      _rbffi_CallFunction in Call.o
      _callback_invoke in Function.o
      _callback_with_gvl in Function.o
      _async_cb_call in Function.o
      _variadic_invoke in Variadic.o
  "_rb_respond_to", referenced from:
      _get_pointer_value in AbstractMemory.o
      _getPointer in Call.o
      _function_init in Function.o
      _invoke_callback in Function.o
      _mapped_initialize in MappedType.o
      _struct_field_initialize in StructLayout.o
      _function_field_put in StructLayout.o
      ...
  "_rb_singleton_class", referenced from:
      _rbffi_Buffer_Init in Buffer.o
      _rbffi_Struct_Init in Struct.o
  "_rb_sprintf", referenced from:
      _memory_get in AbstractMemory.o
      _memory_put in AbstractMemory.o
  "_rb_str_intern", referenced from:
      _struct_field_initialize in StructLayout.o
  "_rb_str_new", referenced from:
      _memory_get_string in AbstractMemory.o
      _memory_get_bytes in AbstractMemory.o
      _rbffi_longdouble_new in LongDouble.o
  "_rb_str_new_cstr", referenced from:
      _memory_get_array_of_string in AbstractMemory.o
      _memory_op_get_strptr in AbstractMemory.o
      _buffer_inspect in Buffer.o
      _library_dlerror in DynamicLibrary.o
      _symbol_inspect in DynamicLibrary.o
      _invoke_callback in Function.o
      _ptr_inspect in Pointer.o
      ...
  "_rb_str_new_static", referenced from:
      _library_initialize in DynamicLibrary.o
      _function_init in Function.o
      _async_cb_event in Function.o
      _rbffi_num2longdouble in LongDouble.o
  "_rb_str_to_str", referenced from:
      _ptr_free.cold.1 in Pointer.o
  "_rb_string_value", referenced from:
      _memptr_s_from_string in MemoryPointer.o
  "_rb_string_value_cstr", referenced from:
      _rbffi_SetupCallParams in Call.o
      _library_initialize in DynamicLibrary.o
      _library_dlsym in DynamicLibrary.o
      _symbol_inspect in DynamicLibrary.o
      _function_attach in Function.o
      _struct_field in Struct.o
  "_rb_string_value_ptr", referenced from:
      _getPointer in Call.o
  "_rb_sym2id", referenced from:
      _buffer_order in Buffer.o
      _ptr_order in Pointer.o
  "_rb_thread_call_with_gvl", referenced from:
      _callback_invoke in Function.o
  "_rb_thread_call_without_gvl", referenced from:
      _rbffi_do_blocking_call in Call.o
      _async_cb_event in Function.o
  "_rb_thread_create", referenced from:
      _function_init in Function.o
      _async_cb_event in Function.o
  "_rb_uint2big", referenced from:
      _memory_get_ulong in AbstractMemory.o
      _memory_read_ulong in AbstractMemory.o
      _memory_get_array_of_ulong in AbstractMemory.o
      _memory_aref in AbstractMemory.o
      _memory_op_get_ulong in AbstractMemory.o
      _invoke_callback in Function.o
      _rbffi_NativeValue_ToRuby in Types.o
      ...
  "_rb_ull2inum", referenced from:
      _memory_get_uint64 in AbstractMemory.o
      _memory_read_uint64 in AbstractMemory.o
      _memory_get_array_of_uint64 in AbstractMemory.o
      _memory_op_get_uint64 in AbstractMemory.o
      _invoke_callback in Function.o
      _ptr_address in Pointer.o
      _rbffi_NativeValue_ToRuby in Types.o
      ...
  "_rb_undef_method", referenced from:
      _rbffi_DynamicLibrary_Init in DynamicLibrary.o
      _rbffi_Type_Init in Type.o
  "_rb_unexpected_type", referenced from:
      _rbffi_AbstractMemory_Cast in AbstractMemory.o
      _memory_put_int8 in AbstractMemory.o
      _memory_get_int8 in AbstractMemory.o
      _memory_put_uint8 in AbstractMemory.o
      _memory_get_uint8 in AbstractMemory.o
      _memory_write_int8 in AbstractMemory.o
      _memory_read_int8 in AbstractMemory.o
      ...
  "_rb_warn", referenced from:
      _function_init in Function.o
      _ptr_free.cold.1 in Pointer.o
  "_rb_yield", referenced from:
      _buffer_initialize in Buffer.o
      _memptr_initialize in MemoryPointer.o
      _inline_array_each in Struct.o
  "_ruby_malloc_size_overflow", referenced from:
      _memory_write_bytes in AbstractMemory.o
      _rbffi_CallFunction in Call.o
      _invoke_callback in Function.o
      _variadic_invoke in Variadic.o
  "_ruby_native_thread_p", referenced from:
      _callback_invoke in Function.o
  "_ruby_snprintf", referenced from:
      _buffer_inspect in Buffer.o
      _rbffi_Closure_Alloc in ClosurePool.o
      _library_dlerror in DynamicLibrary.o
      _library_initialize in DynamicLibrary.o
      _symbol_inspect in DynamicLibrary.o
      _function_attach in Function.o
      _callback_prep in Function.o
      ...
  "_ruby_thread_has_gvl_p", referenced from:
      _callback_invoke in Function.o
  "_ruby_xcalloc", referenced from:
      _array_type_s_allocate in ArrayType.o
      _array_type_initialize in ArrayType.o
      _rbffi_ClosurePool_New in ClosurePool.o
      _fntype_initialize in FunctionInfo.o
      _rbffi_save_errno in LastError.o
      _get_last_error in LastError.o
      _rbffi_MethodHandle_Alloc in MethodHandle.o
      ...
  "_ruby_xfree", referenced from:
      _array_type_free in ArrayType.o
      _buffer_initialize_copy in Buffer.o
      _buffer_release in Buffer.o
      _buffer_free in Buffer.o
      _cleanup_closure_pool in ClosurePool.o
      _rbffi_ClosurePool_Free in ClosurePool.o
      _rbffi_Closure_Free in ClosurePool.o
      ...
  "_ruby_xmalloc", referenced from:
      _buffer_initialize in Buffer.o
      _buffer_initialize_copy in Buffer.o
      _rbffi_MemoryPointer_NewInstance in MemoryPointer.o
      _memptr_initialize in MemoryPointer.o
      _ptr_initialize_copy in Pointer.o
  "_ruby_xmalloc2", referenced from:
      _struct_initialize_copy in Struct.o
      _struct_aset in Struct.o
  "_ruby_xrealloc2", referenced from:
      _fntype_initialize in FunctionInfo.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [ffi_c.bundle] Error 1

make failed, exit code 2

Gem files will remain installed in
/Users/isaacmattern/Library/Caches/shopify-cli-nodejs/vendor/ruby-cli/2.34.0/ruby/3.2.0/gems/ffi-1.15.5
for inspection.
Results logged to
/Users/isaacmattern/Library/Caches/shopify-cli-nodejs/vendor/ruby-cli/2.34.0/ruby/3.2.0/extensions/arm64-darwin-22/3.2.0/ffi-1.15.5/gem_make.out

/opt/homebrew/Cellar/ruby/3.2.0/lib/ruby/3.2.0/rubygems/ext/builder.rb:102:in
`run'
/opt/homebrew/Cellar/ruby/3.2.0/lib/ruby/3.2.0/rubygems/ext/builder.rb:51:in
`block in make'
/opt/homebrew/Cellar/ruby/3.2.0/lib/ruby/3.2.0/rubygems/ext/builder.rb:43:in
`each'
/opt/homebrew/Cellar/ruby/3.2.0/lib/ruby/3.2.0/rubygems/ext/builder.rb:43:in
`make'
/opt/homebrew/Cellar/ruby/3.2.0/lib/ruby/3.2.0/rubygems/ext/ext_conf_builder.rb:42:in
`build'
/opt/homebrew/Cellar/ruby/3.2.0/lib/ruby/3.2.0/rubygems/ext/builder.rb:171:in
`build_extension'
/opt/homebrew/Cellar/ruby/3.2.0/lib/ruby/3.2.0/rubygems/ext/builder.rb:205:in
`block in build_extensions'
/opt/homebrew/Cellar/ruby/3.2.0/lib/ruby/3.2.0/rubygems/ext/builder.rb:202:in
`each'
/opt/homebrew/Cellar/ruby/3.2.0/lib/ruby/3.2.0/rubygems/ext/builder.rb:202:in
`build_extensions'
/opt/homebrew/Cellar/ruby/3.2.0/lib/ruby/3.2.0/rubygems/installer.rb:843:in
`build_extensions'
/opt/homebrew/Cellar/ruby/3.2.0/lib/ruby/3.2.0/bundler/rubygems_gem_installer.rb:72:in
`build_extensions'
/opt/homebrew/Cellar/ruby/3.2.0/lib/ruby/3.2.0/bundler/rubygems_gem_installer.rb:28:in
`install'
/opt/homebrew/Cellar/ruby/3.2.0/lib/ruby/3.2.0/bundler/source/rubygems.rb:200:in
`install'
/opt/homebrew/Cellar/ruby/3.2.0/lib/ruby/3.2.0/bundler/installer/gem_installer.rb:54:in
`install'
/opt/homebrew/Cellar/ruby/3.2.0/lib/ruby/3.2.0/bundler/installer/gem_installer.rb:16:in
`install_from_spec'
/opt/homebrew/Cellar/ruby/3.2.0/lib/ruby/3.2.0/bundler/installer/parallel_installer.rb:155:in
`do_install'
/opt/homebrew/Cellar/ruby/3.2.0/lib/ruby/3.2.0/bundler/installer/parallel_installer.rb:146:in
`block in worker_pool'
/opt/homebrew/Cellar/ruby/3.2.0/lib/ruby/3.2.0/bundler/worker.rb:62:in
`apply_func'
/opt/homebrew/Cellar/ruby/3.2.0/lib/ruby/3.2.0/bundler/worker.rb:57:in `block
in process_queue'
  /opt/homebrew/Cellar/ruby/3.2.0/lib/ruby/3.2.0/bundler/worker.rb:54:in `loop'
/opt/homebrew/Cellar/ruby/3.2.0/lib/ruby/3.2.0/bundler/worker.rb:54:in
`process_queue'
/opt/homebrew/Cellar/ruby/3.2.0/lib/ruby/3.2.0/bundler/worker.rb:90:in `block
(2 levels) in create_threads'

An error occurred while installing ffi (1.15.5), and Bundler cannot continue.

In Gemfile:
  shopify-cli was resolved to 2.34.0, which depends on
    listen was resolved to 3.7.1, which depends on
      rb-inotify was resolved to 0.10.1, which depends on
        ffi
Fetching gem metadata from https://rubygems.org/.............
Resolving dependencies...
Using concurrent-ruby 1.2.0
Using bundler 2.4.2
Using liquid 5.4.0
Using rb-fsevent 0.11.2
Using racc 1.6.2
Using ast 2.4.2
Using bugsnag 6.25.1
Using nokogiri 1.14.1 (arm64-darwin)
Using parser 3.2.0.0
Using theme-check 1.14.0
Installing ffi 1.15.5 with native extensions
    at makeError (file:///opt/homebrew/Cellar/shopify-cli/3.39.0/libexec/lib/node_modules/@shopify/theme/node_modules/execa/lib/error.js:59:11)
    at handlePromise (file:///opt/homebrew/Cellar/shopify-cli/3.39.0/libexec/lib/node_modules/@shopify/theme/node_modules/execa/index.js:119:26)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async exec (file:///opt/homebrew/Cellar/shopify-cli/3.39.0/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/dist/public/node/system.js:54:9)
    at async bundleInstallShopifyCLI (file:///opt/homebrew/Cellar/shopify-cli/3.39.0/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/dist/public/node/ruby.js:218:5)
    at async installCLIDependencies (file:///opt/homebrew/Cellar/shopify-cli/3.39.0/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/dist/public/node/ruby.js:125:9)
    at async execCLI2 (file:///opt/homebrew/Cellar/shopify-cli/3.39.0/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/dist/public/node/ruby.js:24:5) {
  tryMessage: null,
  type: 0,
  nextSteps: undefined,
  command: '/opt/homebrew/opt/ruby/bin/bundle',
  args: [ 'install' ]
}

Node.js v19.5.0

Reproduction steps

Install homebrew
Install yarn
Install ruby
Install shopify-cli: I did so using the following commands:
arch -arm64 brew tap shopify/shopify
arch -arm64 brew install shopify-cli
Run "shopify theme dev [your store]"

Operating System
Mac OS Ventura
Shopify CLI version (check your project's package.json if you're not sure)
3.39.0
Shell
zsh
Node version (run node -v if you're not sure)
19.5.0
What language and version are you using in your application?
3.2.0

Sorry - I'm actually running MacOS Ventura (13.1)

Looks like the real problem was that the brew file doesn't specify a Ruby version.

That's indeed a problem. The version was removed from the formula some months ago to support Ruby 3.1 (instead of 3.0), so in theory 3.1 should work.
I will leave this issue open, in case other users have the same problem.

@houseofpsalm – In your case, it’s a Node.js issue → https://github.com/nodejs/node/issues/47096
Looks like you need to install Node.js 19.8.1 (instead of 19.8.0)

Having the same issue - I tried to clean up Ruby + Shopify CLI and redo the whole thing clean and still having this issue with shopify theme check and shopify theme dev, shopify theme info works
~ shopify theme check

── external error ───────────────────

Error coming from `/opt/homebrew/opt/ruby/bin/bundle install`

Command failed with exit code 5: /opt/homebrew/opt/ruby/bin/bundle install
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

.....

Undefined symbols for architecture x86_64:
  "_ffi_call", referenced from:
      _ffi_raw_call in raw_api.o
      _ffi_java_raw_call in java_raw_api.o
  "_ffi_closure_trampoline_table_page", referenced from:
      _ffi_trampoline_table_alloc in closures.o
  "_ffi_prep_cif_machdep", referenced from:
      _ffi_prep_cif_core in prep_cif.o
  "_ffi_prep_cif_machdep_var", referenced from:
      _ffi_prep_cif_core in prep_cif.o
  "_ffi_prep_closure_loc", referenced from:
      _ffi_prep_closure in prep_cif.o
      _ffi_prep_raw_closure_loc in raw_api.o
      _ffi_prep_java_raw_closure_loc in java_raw_api.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[3]: *** [libffi.la] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all] Error 2
make: ***
["/Users/user/Library/Caches/shopify-gems-nodejs/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi-arm64-darwin22"/.libs/libffi_convenience.a]
Error 2

make failed, exit code 2

Could we reopen the case? I have the exact theme behavior on my machine.
Mac Book Pro: M1 Max 16-inch, 2021
macOS: 13.0.1 (22A400)
Excerpt:
`An error occurred while installing nokogiri (1.14.5), and Bundler cannot
continue.
In Gemfile:
theme-check was resolved to 1.15.0, which depends on
nokogiri
Fetching gem metadata from https://rubygems.org/..........
Resolving dependencies...
Installing nokogiri 1.14.5 with native extensions`

authors: Henry31 Poitrin egantz isaacmattern

repo: Shopify/cli


text:
[Bug]: Shopify theme dev ruby error

Please confirm that you have:

[X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[X] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
Theme
Expected behavior
Development server should start and output urls for localhost
Actual behavior
I get 'Unexpected error occured' message in a terminal
Stack trace
`Error
    at execCLI2 (file:///home/<username>/.nvm/versions/node/v18.14.2/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/dist/public/node/ruby.js:55:15)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)`

Reproduction steps

cd to theme directory
run 'shopify theme dev'

If it's important, I am using rvm for installing ruby v3.0.0. It all worked recently and I don't know what is the reason that it stopped.
Operating System
wsl2 with Ubuntu 20.04 running on Windows 10
Shopify CLI version (check your project's package.json if you're not sure)
3.44.1
Shell
wsl2 - Ubuntu 20.04
Node version (run node -v if you're not sure)
v18.14.2
What language and version are you using in your application?
No response

Today I got this error too. https://jmp.sh/Y9Eja8KU

authors: bmandl ulziibat-n


text:
[BUG] Updating to 1.4.3 breaks production build with Vite rollup error

Describe the bug
I updated to @shopify/hydrogen 1.4.3 from 1.4.2., and I'm getting the following error on production builds via Github Actions:
$ shopify hydrogen build --target node
[STARTED] Building node code
vite v2.9.15 building SSR bundle for production...
transforming...
✓ 38 modules transformed.
[vite]: Rollup failed to resolve import "/app/dist/client/index.html?raw" from "node_modules/@shopify/hydrogen/dist/esnext/platforms/virtual.js".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
[FAILED] [vite]: Rollup failed to resolve import "/app/dist/client/index.html?raw" from "node_modules/@shopify/hydrogen/dist/esnext/platforms/virtual.js".
[FAILED] This is most likely unintended because it can break your application at runtime.
[FAILED] If you do want to externalize this module explicitly add it to
[FAILED] `build.rollupOptions.external`

━━━━━━ Error ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    [vite]: Rollup failed to resolve import "/app/dist/client/index.html?raw" from "node_modules/@shopify/hydrogen/dist/esnext/platforms/virtual.js".
    This is most likely unintended because it can break your application at runtime.
    If you do want to externalize this module explicitly add it to
    `build.rollupOptions.external`

To Reproduce

Create a production build, in my case, via Github Actions using ubuntu-latest as the build container.

Additional context
Add any other context about the problem here. eg.

Hydrogen version: 1.4.3
Docker image: ubuntu-latest

The only thing that changes from 1.4.2 to 1.4.3 is some implementation details of the Cart component so this might not be related to the version.
Can you try using Node 18 and making sure node_modules is not cached?
Also, can you check if /app/dist/client/index.html file exists after this error? It should be created during the build but before throwing this error.

I am having a similar issue. It was happening with @shopify/hydrogen 1.2.0, so I upgraded to 1.4.3, which did not change anything. I have no issues building locally, but the deploy with oxygen and github actions fails every time.

@diemonster Thanks for the tip, but sadly that doesn't seem to be the issue for me...
@frandiox Ive updated to use Node 18, nothing is being cached and my .../dist/client/index.html exists although it does not have the script tag with the entry-client module like my project's index.html does... Any other ideas?
For completeness, I'm attaching my errors along with my GitHub workflow file.
🛠 Building the application...
yarn run v1.22.19
$ shopify hydrogen build
[STARTED] Building worker code
vite v2.9.15 building SSR bundle for production...
transforming...
✓ 2 modules transformed.
[vite]: Rollup failed to resolve import "/home/runner/work/pax-shopify-hydrogen/pax-shopify-hydrogen/dist/client/index.html?raw" from "node_modules/@shopify/hydrogen/dist/esnext/platforms/virtual.js".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
[FAILED] [vite]: Rollup failed to resolve import "/home/runner/work/pax-shopify-hydrogen/pax-shopify-hydrogen/dist/client/index.html?raw" from "node_modules/@shopify/hydrogen/dist/esnext/platforms/virtual.js".
[FAILED] This is most likely unintended because it can break your application at runtime.
[FAILED] If you do want to externalize this module explicitly add it to
[FAILED] `build.rollupOptions.external`

━━━━━━ Error ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    [vite]: Rollup failed to resolve import "/home/runner/work/pax-shopify-hydrogen/pax-shopify-hydrogen/dist/client/index.html?raw" from "node_modules/@shopify/hydrogen/dist/esnext/platforms/virtual.js".

Workflow:
name: Oxygen Deployment

on:
  workflow_dispatch:
  push:

jobs:
  deploy:
    name: Deploy to Oxygen
    timeout-minutes: 30
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2

      - name: Setup node.js
        uses: actions/setup-node@v3
        with:
          node-version: '18'
          check-latest: true

      - name: Install dependencies
        id: 'install-dependencies'
        run: yarn

      - name: Build and Publish to Oxygen
        id: deploy
        uses: shopify/oxygenctl-action@v4
        with:
          path: ./
          oxygen_deployment_token: ${{ secrets.OXYGEN_DEPLOYMENT_TOKEN_65651 }}
          build_command: 'HYDROGEN_ASSET_BASE_URL=$OXYGEN_ASSET_BASE_URL yarn build'

      - name: Create GitHub Deployment
        uses: shopify/github-deployment-action@v1
        if: always()
        with:
          token: ${{ github.token }}
          environment: 'preview'
          preview_url: ${{ steps.deploy.outputs.url }}
          description: ${{ github.event.head_commit.message }}

my .../dist/client/index.html exists although it does not have the script tag with the entry-client module like my project's index.html does

That's fine, the entry-client script tag is only for development. This index.html should contain different script tags generated during the client build.

I am having a similar issue. It was happening with @shopify/hydrogen 1.2.0, so I upgraded to 1.4.3, which did not change anything. I have no issues building locally, but the deploy with oxygen and github actions fails every time.

There's some kind of mismatch between the local and the CI environment but not sure what it could be apart from what I already mentioned. You are not changing the build output path in your yarn build or in vite.config.js, right?
In any case, if you can't find what's different between the two environments, you can try this workaround. Create a new <root>/worker-entry.ts file where you manually specify the path to your files:
import handleRequest from './src/App.server'; // Path to your App.server
import indexTemplate from './dist/client/index.html?raw'; // Path to your built index.html

declare global {
  // eslint-disable-next-line no-var
  var globalThis: {
    Oxygen: {env: any};
    [key: string]: any;
  };
}

export default {
  async fetch(
    request: Request,
    env: unknown,
    context: {waitUntil: (promise: Promise<any>) => void}
  ) {
    if (!globalThis.Oxygen) {
      globalThis.Oxygen = {env};
    }

    try {
      return (await handleRequest(request, {
        indexTemplate,
        cache: await caches.open('oxygen'),
        context,
        buyerIpHeader: 'oxygen-buyer-ip',
      })) as Response;
    } catch (error: any) {
      return new Response(error.message || error.toString(), {status: 500});
    }
  },
};

Then, change the build command to shopify hydrogen build --entry worker-entry.
Since you are manually resolving the path to your files, you should not see the index.html not found issue (as long the paths in this file are correct).

EvalError: Code generation from strings disallowed for this context

Yeah that doesn't sound like anything familiar in Hydrogen 🤔
Closing this issue since the main problem seems to be solved 👍

authors: diemonster frandiox tylerscave

repo: Shopify/hydrogen


text:
Demo store neue: article page

Description
Article WIP

https://github.com/Shopify/hydrogen-v2-demo-store/issues/26 / https://github.com/Shopify/hydrogen-v2-demo-store/issues/27

Before submitting the PR, please make sure you do the following:

[ ] Read the Contributing Guidelines
[ ] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123)
[ ] Update docs in this repository according to your change
[ ] Run yarn changeset add if this PR cause a version bump based on Keep a Changelog and adheres to Semantic Versioning

Closing in favour of https://github.com/Shopify/hydrogen/pull/1437


text:
Removes the risk of sending decrypted EJSON secrets to output.

NB: This addresses a security issue with application secrets
What are you trying to accomplish with this PR?
Presently, if a 'kubectl apply' fails when updating EJSON secrets, it's
possible that the decrypted secrets payload can be output as part of the
error message.
This should be avoided since it can expose all secrets of your application.
For e.g, GKE had an incident on February 26th which caused
intermittent errors when calling kubectl. We happened to see a failure
at the step when secrets are updated. Because kubectl  apply failed, the
exception was bubbled up and logged to output.
How is this accomplished?
This change takes a simple approach by not including the error message in
commands where it is possible to display the payload. The 'Kubectl' class
does not log messages if the sensitive flag is set to true, however the
EjsonSecretProvisioner class raises EjsonSecretError which is logged
further up the stack.
What could go wrong?
The error that is displayed is generic and will not show specific error information
returned from kubectl. This might be problematic.
We would like some feedback on this PR specifically whether this is the best approach.
Either way, this addresses a significant security risk that should be looked at ASAP.
Pinging @dturn on the advice of a colleague who formerly worked at Shopify.

@KnVerey Since #424 is done, would it be possible to merge that first? Its had significant effort put into several rounds of review already and is blocking #411

@benlangfeld I feel your pain. Unfortunately, I think it's important that we release security issues quickly. And as @KnVerey pointed out in a different pr, there are versioning reasons why it makes sense to cut a release without 424

authors: benlangfeld dturn stantona

repo: Shopify/kubernetes-deploy

license: mit

license_source: bigquery


text:
Clean graphql config utilities test output

Description
Tests for graphql-config-utilities outputs warnings when testing resolveProjectName. This PR disables them because they are expected.
Fixes (issue #)

Type of change

[X] graphql-config-utilities Patch: Bug (non-breaking change which fixes an issue)
[ ]  Minor: New feature (non-breaking change which adds functionality)
[ ]  Major: Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

[x] I have added a changelog entry, prefixed by the type of change noted above (Documentation fix and Test update does not need a changelog as we do not publish new version)

Do we need an afterEach to restore the original implementation?

authors: BPScott vsumner

repo: Shopify/quilt


text:
Ruby LSP Rails failed to initialize server

Hello,
Since today, I can't start the Ruby LSP server. Here's the output from the logs:
2024-11-06 17:20:09.075 [info] (platform) The Gemfile's dependencies are satisfied

2024-11-06 17:20:10.791 [info] (platform) Initializing Ruby LSP v0.21.3...
2024-11-06 17:20:10.796 [info] (platform) Auto detected formatter: rubocop
2024-11-06 17:20:10.796 [info] (platform) Auto detected linters: rubocop
2024-11-06 17:20:10.796 [info] (platform) Detected test library: rspec
2024-11-06 17:20:10.796 [info] (platform) Finished initializing Ruby LSP!
2024-11-06 17:20:10.955 [info] (platform) Activating Ruby LSP Rails add-on v0.3.23
2024-11-06 17:20:10.956 [info] (platform) Ruby LSP Rails booting server
2024-11-06 17:20:15.521 [info] (platform) [Error - 5:20:15 PM] Ruby LSP Rails failed to initialize server: /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/ruby-lsp-rails-0.3.23/lib/ruby_lsp/ruby_lsp_rails/runner_client.rb:295:in `block in read_response': RubyLsp::Rails::RunnerClient::EmptyMessageError (RubyLsp::Rails::RunnerClient::EmptyMessageError)
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/ruby-lsp-rails-0.3.23/lib/ruby_lsp/ruby_lsp_rails/runner_client.rb:292:in `synchronize'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/ruby-lsp-rails-0.3.23/lib/ruby_lsp/ruby_lsp_rails/runner_client.rb:292:in `read_response'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/sorbet-runtime-0.5.11637/lib/types/private/methods/_methods.rb:279:in `bind_call'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/sorbet-runtime-0.5.11637/lib/types/private/methods/_methods.rb:279:in `block in _on_method_added'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/ruby-lsp-rails-0.3.23/lib/ruby_lsp/ruby_lsp_rails/runner_client.rb:90:in `initialize'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/sorbet-runtime-0.5.11637/lib/types/private/methods/_methods.rb:279:in `bind_call'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/sorbet-runtime-0.5.11637/lib/types/private/methods/_methods.rb:279:in `block in _on_method_added'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/ruby-lsp-rails-0.3.23/lib/ruby_lsp/ruby_lsp_rails/runner_client.rb:16:in `new'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/ruby-lsp-rails-0.3.23/lib/ruby_lsp/ruby_lsp_rails/runner_client.rb:16:in `create_client'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/sorbet-runtime-0.5.11637/lib/types/private/methods/_methods.rb:279:in `bind_call'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/sorbet-runtime-0.5.11637/lib/types/private/methods/_methods.rb:279:in `block in _on_method_added'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/ruby-lsp-rails-0.3.23/lib/ruby_lsp/ruby_lsp_rails/addon.rb:41:in `block (3 levels) in initialize'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/ruby-lsp-rails-0.3.23/lib/ruby_lsp/ruby_lsp_rails/addon.rb:41:in `synchronize'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/ruby-lsp-rails-0.3.23/lib/ruby_lsp/ruby_lsp_rails/addon.rb:41:in `block (2 levels) in initialize'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/ruby-lsp-rails-0.3.23/lib/ruby_lsp/ruby_lsp_rails/addon.rb:39:in `synchronize'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/ruby-lsp-rails-0.3.23/lib/ruby_lsp/ruby_lsp_rails/addon.rb:39:in `block in initialize'

Server dependent features will not be available

Below is the Ruby LSP debug information. Could you point me to how I can troubleshoot this problem? Thank you. :)
Ruby LSP Information
VS Code Version
1.95.1
Ruby LSP Extension Version
0.8.13
Ruby LSP Server Version
0.21.3
Ruby LSP Addons

Ruby LSP Rails

Ruby Version
3.2.4
Ruby Version Manager
rbenv
Installed Extensions

Click to expand

copilot (1.243.0)
copilot-chat (0.22.1)
elixir-ls (0.24.2)
gitlens (15.6.3)
go (0.42.1)
makefile-tools (0.11.13)
prettier-sql-vscode (1.6.0)
rainbow-csv (3.12.0)
ruby-extensions-pack (0.1.12)
ruby-lsp (0.8.13)
sorbet-vscode-extension (0.3.37)
terraform (2.33.0)
vscode-fileutils (3.10.3)
vscode-graphql (0.12.1)
vscode-json-validate (1.5.0)
vscode-yaml (1.15.0)

Ruby LSP Settings

Click to expand
Workspace
{}

User
{
  "enableExperimentalFeatures": false,
  "enabledFeatures": {
    "codeActions": true,
    "diagnostics": true,
    "documentHighlights": true,
    "documentLink": true,
    "documentSymbols": true,
    "foldingRanges": true,
    "formatting": true,
    "hover": true,
    "inlayHint": true,
    "onTypeFormatting": true,
    "selectionRanges": true,
    "semanticHighlighting": true,
    "completion": true,
    "codeLens": true,
    "definition": true,
    "workspaceSymbol": true,
    "signatureHelp": true,
    "typeHierarchy": true
  },
  "featuresConfiguration": {},
  "addonSettings": {},
  "rubyVersionManager": {
    "identifier": "auto"
  },
  "customRubyCommand": "",
  "formatter": "auto",
  "linters": null,
  "bundleGemfile": "",
  "testTimeout": 30,
  "branch": "",
  "pullDiagnosticsOn": "both",
  "useBundlerCompose": false,
  "bypassTypechecker": false,
  "rubyExecutablePath": "/Users/alexanderpopov/.rbenv/shims/ruby",
  "indexing": {},
  "erbSupport": true,
  "useLauncher": false,
  "featureFlags": {}
}

Thank you for the report! Can you please try the just released v0.3.24? I believe this is the same as #512.

Hey @vinistock, thank you for the quick reply! Unfortunately, this didn't solve the issue for me:
2024-11-07 13:28:21.469 [info] (platform) Initializing Ruby LSP v0.21.3...
2024-11-07 13:28:21.475 [info] (platform) Auto detected formatter: rubocop
2024-11-07 13:28:21.475 [info] (platform) Auto detected linters: rubocop
2024-11-07 13:28:21.475 [info] (platform) Detected test library: rspec
2024-11-07 13:28:21.475 [info] (platform) Finished initializing Ruby LSP!
2024-11-07 13:28:21.597 [info] (platform) Activating Ruby LSP Rails add-on v0.3.25
2024-11-07 13:28:21.599 [info] (platform) Ruby LSP Rails booting server
2024-11-07 13:28:26.341 [info] (platform) [Error - 1:28:26 PM] Ruby LSP Rails failed to initialize server: /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/ruby-lsp-rails-0.3.25/lib/ruby_lsp/ruby_lsp_rails/runner_client.rb:296:in `block in read_response': RubyLsp::Rails::RunnerClient::EmptyMessageError (RubyLsp::Rails::RunnerClient::EmptyMessageError)
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/ruby-lsp-rails-0.3.25/lib/ruby_lsp/ruby_lsp_rails/runner_client.rb:293:in `synchronize'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/ruby-lsp-rails-0.3.25/lib/ruby_lsp/ruby_lsp_rails/runner_client.rb:293:in `read_response'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/sorbet-runtime-0.5.11641/lib/types/private/methods/_methods.rb:279:in `bind_call'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/sorbet-runtime-0.5.11641/lib/types/private/methods/_methods.rb:279:in `block in _on_method_added'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/ruby-lsp-rails-0.3.25/lib/ruby_lsp/ruby_lsp_rails/runner_client.rb:91:in `initialize'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/sorbet-runtime-0.5.11641/lib/types/private/methods/_methods.rb:279:in `bind_call'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/sorbet-runtime-0.5.11641/lib/types/private/methods/_methods.rb:279:in `block in _on_method_added'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/ruby-lsp-rails-0.3.25/lib/ruby_lsp/ruby_lsp_rails/runner_client.rb:16:in `new'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/ruby-lsp-rails-0.3.25/lib/ruby_lsp/ruby_lsp_rails/runner_client.rb:16:in `create_client'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/sorbet-runtime-0.5.11641/lib/types/private/methods/_methods.rb:279:in `bind_call'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/sorbet-runtime-0.5.11641/lib/types/private/methods/_methods.rb:279:in `block in _on_method_added'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/ruby-lsp-rails-0.3.25/lib/ruby_lsp/ruby_lsp_rails/addon.rb:41:in `block (3 levels) in initialize'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/ruby-lsp-rails-0.3.25/lib/ruby_lsp/ruby_lsp_rails/addon.rb:41:in `synchronize'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/ruby-lsp-rails-0.3.25/lib/ruby_lsp/ruby_lsp_rails/addon.rb:41:in `block (2 levels) in initialize'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/ruby-lsp-rails-0.3.25/lib/ruby_lsp/ruby_lsp_rails/addon.rb:39:in `synchronize'
	from /home/alexander/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/ruby-lsp-rails-0.3.25/lib/ruby_lsp/ruby_lsp_rails/addon.rb:39:in `block in initialize'

Server dependent features will not be available

I tried your patch. This problem persists. On my end, I have Mongoid 8.1.6.

Do you see any errors if running this on the command line:
bundle exec rails runner PATH_TO_INSTALLATION/ruby-lsp-rails/lib/ruby_lsp/ruby_lsp_rails/server.rb start

(get the path using bundle show ruby-lsp-rails)

This works well:
# logs for other initializers from the Rails app
Content-Length: 73

{"result":{"message":"ok","root":"/Users/erickg/repos/skvk/application"}}

I bootstraped a 7.2.2 Rails with sqlite3. ruby-lsp-rails commit b5235c3b937300cccaf734809d75f896355039e5.

Logs from VS Code Ruby LSP
2024-11-08 13:06:00.722 [info] (testapp) Found rbenv executable at /opt/homebrew/bin
2024-11-08 13:06:00.724 [info] (testapp) Running command: `/opt/homebrew/bin/rbenv exec ruby -W0 -rjson -e 'STDERR.print("RUBY_LSP_ACTIVATION_SEPARATOR" + { env: ENV.to_h, yjit: !!defined?(RubyVM::YJIT), version: RUBY_VERSION, gemPath: Gem.path }.to_json + "RUBY_LSP_ACTIVATION_SEPARATOR")'` in /Users/erickg/repos/skvk/testapp using shell: /opt/homebrew/bin/zsh
2024-11-08 13:06:00.772 [info] (testapp) [Error - 13:06:00] Server process exited with code 0.
2024-11-08 13:06:01.241 [info] (testapp) Ruby LSP> Skipping custom bundle setup since /Users/erickg/repos/skvk/testapp/.ruby-lsp/Gemfile.lock already exists and is up to date

2024-11-08 13:06:01.283 [info] (testapp) Ruby LSP> Running bundle install for the custom bundle. This may take a while...
Ruby LSP> Command: (bundle _2.4.19_ check || bundle _2.4.19_ install) 1>&2

2024-11-08 13:06:01.455 [info] (testapp) The Gemfile's dependencies are satisfied

2024-11-08 13:06:02.452 [info] (testapp) Initializing Ruby LSP v0.21.3...
2024-11-08 13:06:02.457 [info] (testapp) Auto detected formatter: rubocop
2024-11-08 13:06:02.458 [info] (testapp) Auto detected linters: rubocop
2024-11-08 13:06:02.458 [info] (testapp) Detected test library: rails
2024-11-08 13:06:02.458 [info] (testapp) Finished initializing Ruby LSP!
2024-11-08 13:06:02.470 [info] (testapp) Activating Ruby LSP Rails add-on v0.3.25
2024-11-08 13:06:02.475 [info] (testapp) Ruby LSP Rails booting server
2024-11-08 13:06:03.580 [info] (testapp) Finished booting Ruby LSP Rails server
2024-11-08 13:06:40.219 [info] (testapp) Found rbenv executable at /opt/homebrew/bin
2024-11-08 13:06:40.219 [info] (testapp) Running command: `/opt/homebrew/bin/rbenv exec ruby -W0 -rjson -e 'STDERR.print("RUBY_LSP_ACTIVATION_SEPARATOR" + { env: ENV.to_h, yjit: !!defined?(RubyVM::YJIT), version: RUBY_VERSION, gemPath: Gem.path }.to_json + "RUBY_LSP_ACTIVATION_SEPARATOR")'` in /Users/erickg/repos/skvk/testapp using shell: /opt/homebrew/bin/zsh
2024-11-08 13:06:40.525 [info] (testapp) Shutting down Ruby LSP...
2024-11-08 13:06:40.526 [info] (testapp) Ruby LSP Rails shutting down server
2024-11-08 13:06:41.047 [info] (testapp) [Error - 13:06:41] Server process exited with code 0.
2024-11-08 13:06:41.250 [info] (testapp) Ruby LSP> Skipping custom bundle setup since /Users/erickg/repos/skvk/testapp/.ruby-lsp/Gemfile.lock already exists and is up to date

2024-11-08 13:06:41.324 [info] (testapp) Ruby LSP> Running bundle install for the custom bundle. This may take a while...
Ruby LSP> Command: (bundle _2.4.19_ check || bundle _2.4.19_ install) 1>&2

2024-11-08 13:06:41.495 [info] (testapp) The Gemfile's dependencies are satisfied

2024-11-08 13:06:42.504 [info] (testapp) DEBUGGER: Debugger can attach via UNIX domain socket (/var/folders/bh/3stpknyx3vvc0kj_8k2l4htm0000gn/T/rdbg-501/rdbg-55875)

2024-11-08 13:06:42.509 [info] (testapp) Initializing Ruby LSP v0.21.3...
2024-11-08 13:06:42.512 [info] (testapp) Auto detected formatter: rubocop
2024-11-08 13:06:42.512 [info] (testapp) Auto detected linters: rubocop
2024-11-08 13:06:42.512 [info] (testapp) Detected test library: rails
2024-11-08 13:06:42.512 [info] (testapp) Finished initializing Ruby LSP!
2024-11-08 13:06:42.526 [info] (testapp) Activating Ruby LSP Rails add-on v0.3.25
2024-11-08 13:06:42.531 [info] (testapp) Ruby LSP Rails booting server
2024-11-08 13:06:43.490 [info] (testapp) Finished booting Ruby LSP Rails server

Everything looks fine. Then I did bundle show ruby-lsp-rails.
/Users/erickg/.local/share/mise/installs/ruby/3.2.4/lib/ruby/gems/3.2.0/bundler/gems/ruby-lsp-rails-b5235c3b9373

Running bundle exec rails runner lib/ruby_lsp/ruby_lsp_rails/server.rb start
Same message:
Content-Length: 69

{"result":{"message":"ok","root":"/Users/erickg/repos/skvk/testapp"}}

Both repo has a direnv setup:
use rbenv

layout ruby

PATH_add bin

This is a bit bizzare. So I suspected my environment. I have both mise and rbenv. I use rbenv in Ruby LSP but not in an interactive shell. My direnv uses rbenv. So I disabled mise and applied the same check again. Now that Ruby LSP Rails runs well.
Now the problem should be which "bundle" Ruby LSP picks up. When mise is available, mise overwrites the 'direnv' bundle. I know this will cause undefined behavior. I will fix that integration.
The nuance to RubyLSP is though where RubyLSP loads the environment in this case.

That app doesn't seem to start:
repro-ruby-lsp-rails main % bin/rails c
/Users/andyw8/.gem/ruby/3.3.4/gems/bundler-2.4.19/lib/bundler/rubygems_integration.rb:280:in `block (2 levels) in replace_gem': Error loading the 'sqlite3' Active Record adapter. Missing a gem it depends on? sqlite3 is not part of the bundle. Add it to your Gemfile. (LoadError)
        from /Users/andyw8/.gem/ruby/3.3.4/gems/activerecord-7.2.2/lib/active_record/connection_adapters/sqlite3_adapter.rb:14:in `<top (required)>'

I can boot it if comment out the active_record Railtie and the mentions in development.rb. Continuing to investigate...

Yep, it's 22.

Meanwhile I don't have the problem, running on 0.3.26:
2024-11-09 07:17:59.034 [info] (platform) Initializing Ruby LSP v0.21.3...
2024-11-09 07:17:59.041 [info] (platform) Auto detected formatter: rubocop
2024-11-09 07:17:59.041 [info] (platform) Auto detected linters: rubocop
2024-11-09 07:17:59.041 [info] (platform) Detected test library: rspec
2024-11-09 07:17:59.041 [info] (platform) Finished initializing Ruby LSP!
2024-11-09 07:17:59.178 [info] (platform) Activating Ruby LSP Rails add-on v0.3.26
2024-11-09 07:17:59.179 [info] (platform) Ruby LSP Rails booting server
2024-11-09 07:18:04.835 [info] (platform) Finished booting Ruby LSP Rails server
2024-11-09 07:18:04.836 [info] (platform) [dry-types] Dry::Types::Type#safe is deprecated and will be removed in the next major version

2024-11-09 07:18:04.836 [info] (platform) Please use Dry::Types::Type#lax instead.

2024-11-09 07:18:04.836 [info] (platform) /home/alexander/Toptal/platform/config/application.rb:12:in `<main>'

2024-11-09 07:18:04.836 [info] (platform) your 131072x1 screen size is bogus. expect trouble

Great, we can close the issue. Thanks for helping.

Closing as the problem is no longer reproducible in 0.3.26. Thank you, @erickguan, for helping! 🙇 🙏

authors: AlexVPopov andyw8 erickguan vinistock

repo: Shopify/ruby-lsp-rails


text:
Bugfix: Allow TLS connections to work over socks proxy.

It seems that the code was either proxy or tls but in my case I need tls over the socks proxy so Ive created this PR to fix this issue.
Note there seems to be an issue with the tls test where the server name was never set so Ive fixed that too.

@probot-shopify
CLA — Contributor License Agreement (CLA) status  Signed :)

@github-actions CI / Go 1.13.x with Kafka 2.4.0 on Ubuntu (pull_request)
+ bin/zookeeper-server-stop.sh
No zookeeper server to stop
##[error]Process completed with exit code 1.

hmmm seems like an intermittant problem exists ;)

Note there seems to be an issue with the tls test where the server name was never set so Ive fixed that too.

@KevinJCross did you add the code for this?

repo: Shopify/sarama


text:
Utils::sanitizeShopDomain is not utilizing the custom $myShopifyDomain parameter

Issue summary
I am not sure if this is a bug or a feature request since it appears the code is in place to handle what we need but it is not used. We are using the Craft CMS Shopify plugin which uses this library to make API requests to Shopify stores. We are running into an issue where a shop with a custom domain results in an error.
Expected behavior
I'm not sure exactly how allowing custom domains should be implemented but I would like the ability to have the domain I supplied for the store to be passed into that second parameter or allowed in some other way.
Actual behavior
We see the following error when using our custom shop domain:

Cannot assign null to property Shopify\Auth\Session::$shop of type string
in /var/www/html/vendor/shopify/shopify-api/src/Auth/Session.php (line 33)

I noticed the Utils::sanitizeShopDomain($shop) call is not utilizing the second parameter that allows for sanitizing a custom domain.

We have run into the same issue using a custom Shopify domain.

@benjaminkohl We have run into the same issue using a custom Shopify domain. When adding the custom domain as the Hostname we get that same error and cannot access the backend.

I believe we resolved this one by setting the domain to the default [store].myshopiy.com domain. Apparently that is what needs to be used for API requests.

authors: a-am benjaminkohl

repo: Shopify/shopify-api-php


text:
changeItem using GET method

While trying to update a cart item with the changeItem function requests are being sent as GET rather than POST.

This is fixed in the latest release (1.0.0) of theme-cart!

authors: NikolaDonchev t-kelly

repo: Shopify/theme-scripts


text:
Apple M1 build crashes when trying to build dependency of themekit

Was running into this issue trying to setup my dev environment on a new mac mini. Not sure if its something on my end or something that needs to be updated.
[6/15] ⠠ gifsicle
[9/15] ⠠ pngquant-bin
[7/15] ⠠ mozjpeg
[4/15] ⠠ @shopify/themekit
error /Users/andrewamistad/Sites/dry-farm-wines/node_modules/@shopify/themekit: Command failed.
Exit code: 1
Command: node ./lib/cli.js install
Arguments:
Directory: /Users/andrewamistad/Sites/dry-farm-wines/node_modules/@shopify/themekit
Output:
-/Users/andrewamistad/Sites/dry-farm-wines/node_modules/@shopify/themekit/lib/install.js:46
        throw runErr;
        ^

Error: The `/Users/andrewamistad/Sites/dry-farm-wines/node_modules/@shopify/themekit/bin/theme` binary doesn't seem to work correctly
    at BinWrapper.<anonymous> (/Users/andrewamistad/Sites/dry-farm-wines/node_modules/bin-wrapper/index.js:156:7)
    at ChildProcess.<anonymous> (/Users/andrewamistad/Sites/dry-farm-wines/node_modules/bin-check/index.js:26:4)```

@aamistad Do you have your Terminal set to 'Open in Rosetta'?

@andyw8 yes terminal is set to open using Rosetta. I've also attempted reinstalling themekit, brew and reinstalled command line tools

Please open this on the https://github.com/Shopify/node-themekit repo as it looks like an installation issue with the node library. We have seen success with others using themekit directly on M1

authors: aamistad andyw8 tanema

repo: Shopify/themekit


text:
A note about how to use in the dev console

Was using Twine and couldn't remember this trick - after I had someone remind me I thought I would add to the readme since this easy to forget line is invaluable.
@patrickdonovan @DrewMartin @pushrax

Yeah this should totally be in there.

repo: Shopify/twine


text:
Invalid runtimepath is detected in Windows

Setting RTP with the following snippet:
  let &runtimepath = join([
        \ expand('$XDG_CONFIG_HOME/vim'),
        \ expand('$VIM/vimfiles'),
        \ expand('$VIMRUNTIME'),
        \ expand('$VIM/vimfiles/after'),
        \ expand('$XDG_CONFIG_HOME/vim/after')], ',')

echo expand('$VIMRUNTIME') outputs C:/Program Files/Vim/vim74
echo $VIMRUNTIME outputs C:\Program Files\Vim\vim74
The error is being triggered for this code:
let n = index(rtps, $VIMRUNTIME)

Because $VIMRUNTIME doesn't actually match any value in rtps, due to the difference between \ and /, plugin fails, despite technically valid runtimepath.
Temporary workaround is to add the following to vimrc before neobundle is called:
let $VIMRUNTIME=expand('$VIMRUNTIME')

@ClaudiaJ I think expand() does not convert backslash.
Have you set shellslash option?
I think it is your configuration problem.  I don't recommend to set path manually.

Whoops, you are right.
I mostly copied your dotfiles. I preferred shellslash on, but commenting that out makes the problem go away.

authors: ClaudiaJ Shougo


text:
Investigate why we can load gltf from polyhaven, but fbx have a problem with bump_normals

For both gltf and fbx, the files does not contain tangent/bitangent and they are computed by Assimp.
The issue looks a bit like an handedness problem, but It is strange it is only the case with one format.
Tangents

FBX
glTF

Bitangents

FBX
glTF

Well, as we can see above both formats lead to the same tangent/bitangent.
Turns out it was not an issue of handedness, but how I converted the exr normal map to png. Downloading the png directly from polyhaven fixed it.

repo: ShredEagle/snacman


text:
Kth Smallest Element in a Sorted Matrix in java #123

Kth Smallest Element in a Sorted Matrix in java #123

can u add hacktoberfest label to it.


text:
modify @last with no @ combine after replaced for eg. /invite @last

I encountered an issue when trying to set up a chat command to invite a friend to a party using the command /invite @last. It turns out the program adds '@' in front of the name, causing it to fail as it cannot find the player's name. I made adjustments to ensure it handles this case.
The '@last' command, used for whispering, also still works as intended.

This was fixed recently in #395
It will be released in the stable version soon, in the meantime the beta has this fix.

These will work after:

authors: domialex edwardmelody

repo: Sidekick-Poe/Sidekick


text:
feature: turn on security by default

I also moved the two security plugins to the SignalK git.
Please publish those and/or give me permission to publish @signalk npm's (if possible)
Changes on the plugin side include generating the secret key at startup if non specified and prompting the user to create an admin username and password the first time the site is hit.

We'll do this after the new UI is in...

repo: SignalK/signalk-server-node


text:
Add linting support

Adds linting support and integrates release pipeline.

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

Chrome Web Store
GitHub release

Your semantic-release bot :package::rocket:

repo: Silthus/chrome-enterprise-tab-rotate


text:
Report dimer RMSD using itables

Description
This PR is a possible alternative to #52 that uses itables for interactive dimer energy reporting.

Status

[X] Ready to go

https://panel.holoviz.org/reference/widgets/Tabulator.html could also be an option:

Woow this is awesome much better than a static output lets take either over #52! Maybe we could include some way to search for dimers as well or maybe even smarts patterns similar to mols2grid?

Maybe we could include some way to search for dimers as well or maybe even smarts patterns similar to mols2grid?

I think that would be awesome but would probably also need something a bit more custom! Given how useful mols2grid is though mols2table would probably be worth it!

authors: SimonBoothroyd jthorton

repo: SimonBoothroyd/descent


text:
Fix function comments based on best practices from Effective Go

Every exported function in a program should have a doc comment. The first sentence should be a summary that starts with the name being declared.
From effective go.
I generated this with CodeLingo and I'm keen to get some feedback, but this is automated so feel free to close it and just say opt out to opt out of future CodeLingo outreach PRs.

These changes look pretty solid except the capitalisation of "Will" on this one, which I've noted an am fixing.
Let me know what you think! :smile:

repo: SimonWaldherr/golang-examples


text:
Saving behaviour

Love the picker and its simplicity!
Would like the ability to save on change though.
Currently the picker crashes if setColor is called within the onChange event. And there is no way to trigger an event when the picker is closed/hidden, which makes it tricky to achieve the behaviour with the current setup.

Thanks :) Really appreciate it!
Seems more like a bug, should IMO possible, I will take a look and try to fix it!

Looking for the same functionality. I would like to ommit the save button. So exactly like you write, at every mouse move I would like to set the value of an input field. This already works by updating the input field within the onChange handler, but as you said, updating the Pickr.setColor causes an infinite loop. I tried compare against Pickr.lastColor but this doesn't seem to work either.

@jaschaio That's an internal method and not save to use it in this way. This method saves the current color and would result in a horrible performance if you would call it in onChange. Moreover it has nothing to do with color-setting, as the name suggests :)

@jaschaio Ahh, yeah... that makes sense.
Fantastic idea, Will be added :)

Okay, I've added it in 2ec9036d5aff4a7186de306e4825d9ac38b6d4d9. Simply add comparison: false to your pickr config-object and the button (and preview) get's immediately updated when you select a color :)

Brilliant! Seems to work. :) Looking forward to have it via npm in 0.1.9.
Is there a way to hide the 'save' button, or should it just be done via CSS?

Ouch damn, Seems like I missed a component option as I added the save button 😬
I will add this option later today! Will be components.options.save which you can toggle :)

So, finally :D Now the save-button can be hide with (00564e81ae58fdf1310952c88f04afad9d131c76):
components: {
    output: {
        save: false
    }
}

Yeah, output as container name is a little bit wrong in this context. It's from the beginning where only output and color modes exists, maybe I will change it in the next major release. Anyway, I think I'll publish 0.1.9 tomorrow or in a few days :)

🎉

@Simonwep  how to hide pickr after clicking save button

authors: Jaybagz Simonwep jaschaio okydk

repo: Simonwep/pickr


text:
Cycle the Riccati solver

This PR aims at adding a function to efficiently cycle the three different kind of linear solvers so as to avoid full reallocation at each MPC control cycle. Discussions are open to decide what is the best way to achieve it.

I'm thinking - maybe we should have a test, reproducing some minimal example? And maybe checking for memory allocations when we expect none.

Didn't see a test was added yet!

The cycling of the parallel solver does not work yet. Test case only involves serial solver for now. The linear solver dedicated to parallel computation needs to be redesign.

authors: ManifoldFR edantec

repo: Simple-Robotics/aligator


text:
mobile: move edit profile to last menu item below search

can you assign this issue to  me ?

can you assign this issue to me ?

Hi @anjali29singh! Thanks for being willing to contribute; that's cool since we're just started :D We've got these issues covered since we're actively developing the platform internally but do star the repo and check in a couple of months!

Done!


text:
Wrong image for Gradient background

Background 2 should be used for Gradient background in README

@AkdM

That's right, my bad!
Thanks for pointing that out 👍

authors: AkdM Sadmansamee jendaz

repo: SimpleBoilerplates/SwiftUI-Cheat-Sheet


text:
Firestore is not a function

Describe the issue / bug.
Hi there,
I am using this vue-cli template to create a new VueJs+Electron project powered by Firestore.
However, when I define the configuration of my VueJs client to connect with my Firestore database, I receive a firebaseApp.firestore is not a function.
I first asked the question at  https://github.com/firebase/firebase-js-sdk/issues/464
How can I reproduce this problem?
You may clone https://github.com/mlapeyre3/firestore-issue-464 to reproduce the issue. Just run yarn then yarn run dev.
My configuration is
import firebase from 'firebase';
import 'firebase/firestore';

const firebaseApp = firebase.initializeApp({
  apiKey: '...',
  authDomain: '...',
  databaseURL: '...',
  projectId: '...',
  storageBucket: '...',
  messagingSenderId: '...',
});

const auth = firebaseApp.auth();
const db = firebaseApp.firestore();

export { db, auth };

However this should not be the source of my issue as, when using an other vue-cli template (webpack instead of simulatedgreg/electron-vue as described in this tutorial) it works perfectly.
If visual, provide a screenshot.

Tell me about your development environment.

Node version: 8.9.0
Yarn version: 1.3.2
vue-cli version: 2.8.2
Operating System: Windows Version	10.0.16299 Build 16299

I've honestly see so many issues with the firebase sdk with webpack. Firebase just really insists you import via a <script> tag. There are a few other issues that may both checking. I'm going to close this as it isn't a direct issue with the boilerplate.

I am also facing similar problem.

Thanks @mlapeyre3 for your 'ugly' solution though, atleast its working!

import firebase from 'firebase'
require('firebase/firestore')

console.log(typeof firebase.firestore)
// "function"

This solved it for me. firebase/firestore has side effects, so I had to require, rather than import it.

@mlapeyre3 I think I've got it. Was from a post related to importing codemirror with electron-webpack. https://github.com/electron-userland/electron-webpack/issues/81
This worked for me.
// package.json
{
  ...
  "electronWebpack": {
    "whiteListedModules": [
      "firebase"
    ]
  },
  ...
}

Btw, this worked for me:
I used this:
import firebase from '@firebase/app';
import '@firebase/firestore'

Rather than this:
import firebase from 'firebase';
import 'firebase/firestore';

I fixed it by importing multiple libraries: firebase and firebase/firestore. That's because the firebase core library does not include the firestore library innately. So the full code to fix it is:

import * as firebase from 'firebase';
import 'firebase/firestore';

repo: SimulatedGREG/electron-vue


text:
Allow * to be used for input (like it can be used for output)

Hello.
The star does not seem to match all input devices:
input * {
    accel_profile flat
    natural_scroll enabled
}

However when using the actual identifiers, the configurations apply:
input "1133:49242:Logitech_USB_Optical" {
    accel_profile flat
}

input "1452:594:Apple_Inc._Apple_Internal_Keyboard_\/_Trac" {
    accel_profile flat
    natural_scroll enabled
}

input "1452:594:bcm" {
    accel_profile flat
    natural_scroll enabled
}

It is quite clear the star configuration does not work as natural scrolling does not apply.
I suggest an improvement to input to allow the use of * to match all inputs (similar to how it matches all output names).
Thanks

Well, maybe input and output could use fnmatch to allow pattern matching?

Better would be a way to target classes of devices like you can with the libinput Xorg configs.

Yes it would be nice to target all input for flat accel, but only all touchpads for natural scrolling.

Yes it would be nice to target all input for flat accel, but only all touchpads for natural scrolling.

authors: harrisonrodgers ldmldmldm nloewen progandy

repo: SirCmpwn/sway


text:
Getting rid of hydration errors for nextjs pages in ExpEditor

This adds a workaround for Experience Editor to make it work better with nextjs apps and avoid hydration errors that started occurring after next and react version upgrades.
Description / Motivation
React will add specific markup for empty placeholders in Experience Editor on first page load. This way it won't be "confused" by this markup when Experience Editor client side scripts add it.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

@ambrauer it shouldn't be. Placeholders appear to behave slightly different on Pages and hydration error does not occur when I tested (at least on XM Cloud deployment).

repo: Sitecore/jss


text:
Doesn't work when included in nested component

When I include beautiful-chat in a nested component the beautiful-chat isn't displayed.
Example:
Main Vue
<template>
  <a />
</template>

A Source
<template>
  <beautiful-chat.... />
</template>

Hello, do you have errors in the browser console?

Same issue here. But it was my first try. See browser console attached.

authors: Sitronik jonasesser robertperez-upc


text:
Test missing CI workers

Some as #30 but instead of disabling workers for missing architectures, leave the tasks hanging (forever).

(the documentation commit also needs to be updated if we go this approach)

repo: Sjors/bitcoin


text:
Shortcut base branch detection if only one possible branch

Topic: bb
Reviewers: brian-k

Reviews in this chain:
└https://github.com/Skydio/revup/pull/57 Remove exceptions for no commits/topics found
　└https://github.com/Skydio/revup/pull/58 Make populate_topics repeatable
　　└https://github.com/Skydio/revup/pull/59 Shortcut base branch detection if only one possible branch

#
head
base
diff
date
summary

0
4f4c1b4e
c28550ee
diff
Sep 21 2:39 PM
1 file changed, 6 insertions(+)

repo: Skydio/revup


text:
🛑 SkyWT is down

In 3860e0a, SkyWT (https://skywt.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SkyWT is back up in cf181dd.


text:
Improve skeleton abstraction

With Autobone skeleton now repeats twice. Originally, HumanSkeleton class and it's ancestors were meant to be as an abstract skeleton, but they iclude too much logic that depend on the server and can't be freely used by other systems. Need to make one skeleton class that doesn't rely on any outside system and can resolve skeleton with a lot of different settings, inputs and outputs.

Implemented in #95 by @ButterscotchVanilla 👍

repo: SlimeVR/SlimeVR-Server


text:
RUG re-design 2014

Design PSD: https://dl.dropboxusercontent.com/u/88844/rug_design.psd

[x] Added SASS support to jekyll via jekyll-sass
[x] Extracted GA code to partial
[x] Removed old css code
[x] Started ignoring .sass-cache folder in .gitignore
[x] Added HTML5 metadata
[x] Make SASS work with GH pages (noted by @mrfoto)
[x] Implemented header design
[x] Implemented "big-what" section
[x] Implemented footer design
[x] Implemented single-page desing
[x] Implemented front-page design
[ ] Opacity to first page post has to be added behind posts with images
[x] Stickers page has to be added
[x] Past meetup recap button has to lead (somewhere)?
[ ] Background for single post has to be white?
[ ] Incresse size of videos in single posts

@mrfoto @zigomir This branch was updated. Can someone please finish the remaining tree tasks? :beer:  ;)

hello it's me
i can help you out with site responsiveness if you're okay with that

Of course we are :+1:
--
Miha Rekar
http://mr.si/
On Sat, Mar 14, 2015 at 10:11 AM, Matic Jurglič notifications@github.com
wrote:

hello it's me
i can help you out with site responsiveness if you're okay with that
Reply to this email directly or view it on GitHub:
https://github.com/SloveniaRUG/SloveniaRUG.github.io/pull/6#issuecomment-80191761

Hey dude!
I'll talk to you on monday.

Oto

On Sat, 14 Mar 2015 10:12 Miha Rekar notifications@github.com wrote:

Of course we are :+1:
--
Miha Rekar
http://mr.si/
On Sat, Mar 14, 2015 at 10:11 AM, Matic Jurglič notifications@github.com
wrote:

hello it's me
i can help you out with site responsiveness if you're okay with that
Reply to this email directly or view it on GitHub:

https://github.com/SloveniaRUG/SloveniaRUG.github.io/pull/6#issuecomment-80191761
—
Reply to this email directly or view it on GitHub
https://github.com/SloveniaRUG/SloveniaRUG.github.io/pull/6#issuecomment-80192894
.

A bi blo možno dobit boljšo kvaliteto tega ozadja?

Tale ni niti blizu 1x quality, kaj šele 2x. :smile:

@otobrglez ma kontakt od dizajnerja - mu boš pisu?

@mrfoto Ja, bom vprašal, ker rekonstruirat to sigurno vzame več časa kot napisat en mail. :smile:

@mfilej Tukaj je RUG folder na DB, ki ga je dal designer.

@SloveniaRUG/owners a lahko prosim zmergamo branch "responsive", da ne bo potem kaj divergiralo...

Sweet, hvala!
p.s. prozorna ozadja so :pig: :pig: :pig: Mi je koncno uspelo, ampak nisem znal drugače, kot dat vsem postom fiksno višino:

@mfilej Pušaj commite, da pogledam če je kak drug way.

@mfilej Prosim če tudi mrđaš @matixmatix ov branch.

@otobrglez Bom priparvil pull request. Kateri je @matixmatixov branch?
Aja, še to: kako je pa s fonti? Imamo kje tiste, ki jih je dizajner določil, ali gremo kar s klasiko (mogoče celo boljš, da ne nalaga se še tisto)?

@mfilej glej #8 font naj ostane ta ki je sedaj.

Ok merged. To bo rebase party, haha. :tada:

Ok ni blo hudega, ampak mogoce responsive branch ni bil ready?

@matixmatix Mogoce ves kaj bi blo narobe al revertam?

ayyy pozabu pushat asset fajle :crying_cat_face:

@matixmatix Ok ni problema, dej še en PR. :)

@mfilej done

@matixmatix Dela, hvala. :+1:

Zakaj removat atom.xml? Če že, potem je treba RSS namest tega http://joelglovier.com/writing/rss-for-jekyll/

We use Slackin on http://srug-invite.herokuapp.com/

@mrfoto Si naredil slack.rug.si?

Ja

Rebased and ready to merge unless anyone has any final fixes? cc @SloveniaRUG/owners
TODOs moved to #15. If you have more in mind just add there.

Meni zgleda vse ok. :100:

authors: matixmatix mfilej mrfoto otobrglez


text:
On what websites are you guys using this

Hey, Im just wondering on what websites this is used, So I just can get some inspiration (I wont steal :P)
:palm_tree: <-- smoke weed every day

Uhhh what?

ok, Im now working on a tf2 casino-website


text:
🛑 My blog(CDN) is down

In 5253b4c, My blog(CDN) (https://sbrave.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: My blog(CDN) is back up in 1a94483.

repo: SmartBrave/uptime


text:
🛑 MPC Homepage is down

In 5f4727c, MPC Homepage (https://www.minorplanetcenter.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MPC Homepage is back up in 4fb95a9 after 4 minutes.

repo: Smithsonian/upptime


text:
🛑 MPC Homepage is down

In 166e799, MPC Homepage (https://www.minorplanetcenter.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MPC Homepage is back up in 01714cb after 1 minute.


text:
Visibility of IDs on client

Describe the feature
Allow visibility of IDs within modals such as the call and incident modals and anywhere that the ID is not present in the URL.
This helps developers link data and makes troubleshooting a little easier for custom API calls.
This should probably be an optional feature but also would be nice if it only showed for administrators or for people with a permission key.
This is similar to the change that shows IDs for departments/divisions which has saved me an awful lot of time. It isn't required for citizen pages as the ID is present in the URL when browsing those.
Additional Context
Example modals:

With this I’ll introduce a developer mode, this will also affect the ids shown in the values tables ;)

authors: Dev-CasperTheGhost jxckUK


text:
[BUG] Wrong css style in dropdown navbar

What version of Node.js are you using?
does not matter
What version of npm are you using?
does not matter
What operating system are you using?
does not matter
What version of SnailyCAD are you currently using?
v1.0.0-beta.91
Describe the Bug
On different css pages, the styles of the navbar dropdown menu are different. Adds an unnecessary border to the item
Example 1

Example 2

Expected Behavior
--
To Reproduce
No response

This is expected behaviour.

This is expected behaviour.

Is it ok to have different styles? Right?

Yeah, it’s something for keyboard navigation


text:
ss brokes some minified js code

Have some problems that ss brokes some minified js code
jquerymin for example
input
#{ template core() }
L="[\\x20\\t\\r\\n\\f]"
#{/}

output
L="[\x20\t\r\n\f]"

Maybe I need some filter or renderMode?
was trying raw
But got another error :))
ReferenceError: document is not defined

Got another

< style
    += jqueryui.styles()

Лол, чувак, что ты пытаешься сделать?

cdata should help
#{ template core() }
#{cdata}
L="[\\x20\\t\\r\\n\\f]"
#{/cdata}
#{/}

But why not just attach JS and CSS as an external file?
- script js file = foo.js
- link css href = foo.css

Лол, чувак, что ты пытаешься сделать?
Блин. Прям автоматика какая-то - на гите на англ создавать ищью и обсуждать :)
Я делаю конструктор.
На вход он принимает набор конфигов и отдает структуру файлов и папок.
Есть несколько модов, которые отличаются тем, что тот же набор конфигов на выходе по разному группируются по папкам и файлам.
Тот же jquery.min может быть как отдельным файлом, так и в составе какого-то файла.
Поэтому я для него сделал шаблон. Но ошибки..
#{ template core() } - расширенный режим чуток помог, что мне не нужно следить за отступами, как в jade-like, но как оказалось он режет символы.
#{cdata} - на простом примере L="[\\x20\\t\\r\\n\\f]" работает как надо. Да. Но на реальном большом файле https://code.jquery.com/jquery-1.12.2.min.js скрипт падает
SyntaxError: Octal literals are not allowed in strict mode.
   at exports.runInThisContext (vm.js:53:16)
   at Module._compile (module.js:414:25)
   at Object.Module._extensions..js (module.js:442:10)
   at Module.load (module.js:356:32)
   at Function.Module._load (module.js:311:12)
   at Module.require (module.js:366:17)
   at require (module.js:385:17)
   at Object.exports.compileFile (.\dev\node_modules\snakeskin\snakeskin.js:181:10)

По сути мне нужно такой темплеит, который вот как введено - так и отдает. Я могу что угодно написать. Ему неважно. Для темплеита это будет raw текст, который просто надо отдать as is и пока с этим проблемы :(

Вообще, у SS есть слак. Можно писать там, это быстрее будет, наверное)
https://snakeskin.slack.com/
Во-вторых... Ты уверен, что тебе вебпак не подойдёт больше?
В-третьих, когда мне нужно было инлайнить файлы прямо текстом в шаблон (инлайнил метрику и аналитику) -- как я понимаю, это примерно то, что тебе нужно, я написал для этих целей фильтр, могу подарить его код)
snakeskin.importFilters({
	insertFileContent: (() => {
		const data = {};
		return (filepath) => {
			filepath = path.resolve(filepath);
			if (data[filepath] && process.env.NODE_ENV === 'production') {
				return data[filepath];
			}

			let content = '';

			try {
				content = fs.readFileSync(filepath);
			} catch (err) {
				log.error('File read failed', err);
			}

			data[path] = content;
			return content;
		};
	})()
});

Ну, правда, тебе его там подгонять придётся, наверное, но вряд ли сильно.

Создал в слаке канал consulting, можно писать туда)
https://snakeskin.slack.com/messages/consulting/

Я просто не понимаю, зачем вообще может пригодится создавать шаблон в который текстом вставлять минифицированный жиквери и отдавать его текстом :)
Но вообще для таких задач, используется cdata, он как раз полностью игнорируется парсером и вставляется как есть, т.е. внутри cdata мы уже не можем использовать другие директивы SS.

#{cdata} - на простом примере L="[\x20\t\r\n\f]" работает как надо. Да. Но на реальном большом файле https://code.jquery.com/jquery-1.12.2.min.js скрипт падает

Внимание на ошибку: падает не SS, а JS парсер, который уже после выполняет файл, т.е. скорее всего проблема именно в самом коде жиквери, а не СС.
Вообще если очень нужно, чтобы шаблон таки отдавал RAW файл, то почему бы просто не грузить его с диска?
- import fs from 'fs'
- template foo()
  += fs.readFileSync('myFile.js')

Как вариант.

#{ template core() } - расширенный режим чуток помог, что мне не нужно следить за отступами, как в jade-like, но как оказалось он режет символы.

Он не режет символы, просто СС управляет текстом, а о природе этого текст он ничего не знает. Ты скормил ему кусок JS-а и хочешь чтобы СС знал что это JS и т.д. но для SS это простой plain text, где \\n парсится как \(экранирующий слеш)\(простой слеш)n(просто символ).

Внимание на ошибку: падает не SS, а JS парсер, который уже после выполняет файл, т.е. скорее всего проблема именно в самом коде жиквери, а не СС.

Этот момент надо пояснить, думаю: SS генерит JS, соответственно, если ты вставляешь в вывод немного JS, то при парсинге он и будет воспринят как JS -- как результат, это всё может упасть. Директива output оборачивает всё в кавычки)

Создал в слаке канал consulting, можно писать туда)
не пускает туда. Можете меня туда пригласить? yazonnile@gmail.com

Исправлено. Спасибо @yazonnile

authors: kobezzza trikadin yazonnile

repo: SnakeskinTpl/Snakeskin