windows: Dozens of tests fail when the version number of fluentd has .rc suffix

Describe the bug
When the version number of fluentd has .rc suffix, dozens of tests in test/command/test_fluentd.rb always fail on Windows.
e.g.) https://github.com/fluent/fluentd/runs/3336022194
It reproduces also on my local environment.
To Reproduce

Add .rc suffix to Fluent::VERSION in lib/fluent/version.rb
bundle exec rake test TEST=test/command/test_fluentd.rb on Windows

Expected behavior
All tests passes
Your Environment
- Fluentd version: 1.14.0.rc
- TD Agent version:
- Operating system: Windows
- Kernel version:

Your Configuration
N/A
Your Error Log
https://github.com/fluent/fluentd/runs/3336022194

2021-08-16T02:22:00.7725312Z Failure: test: by top level <match> section with warning for missing log levels (and warnings for each log event records)(TestFluentdCommand::configured to route log events to plugins):
2021-08-16T02:22:00.8069106Z   execution timeout.
2021-08-16T02:22:00.8383915Z   <"2021-08-16 02:21:55 +0000 [info]: parsing config file is succeeded path=\"D:/a/fluentd/fluentd/test/tmp/command/fluentd/logevent_2.conf\"\r\n" +
2021-08-16T02:22:01.1053865Z   "2021-08-16 02:21:55 +0000 [info]: gem 'fluentd' version '1.14.0.rc'\r\n" +
2021-08-16T02:22:01.2913634Z   "2021-08-16 02:21:55 +0000 [warn]: [dummy] both of Plugin @id and path for <storage> are not specified. Using on-memory store.\r\n" +
2021-08-16T02:22:01.3402954Z   "2021-08-16 02:21:55 +0000 [warn]: [dummy] both of Plugin @id and path for <storage> are not specified. Using on-memory store.\r\n" +
2021-08-16T02:22:01.4706086Z   "2021-08-16 02:21:55 +0000 [warn]: define <match fluent.warn>, <match fluent.error>, <match fluent.fatal> to capture fluentd logs in top level is deprecated. Use <label @FLUENT_LOG> instead\r\n" +
2021-08-16T02:22:01.5743224Z   "2021-08-16 02:21:55 +0000 [warn]: match for some tags of log events are not defined in top level (to be ignored) tags=[\"fluent.trace\", \"fluent.debug\", \"fluent.info\"]\r\n" +
2021-08-16T02:22:01.6202979Z   "2021-08-16 02:21:55 +0000 [info]: using configuration file: <ROOT>\r\n" +
2021-08-16T02:22:01.7429834Z   "  <source>\r\n" +
2021-08-16T02:22:02.0123936Z   "    @type dummy\r\n" +
2021-08-16T02:22:02.3719457Z   "    @id dummy\r\n" +
2021-08-16T02:22:02.4995266Z   "    tag \"dummy\"\r\n" +
2021-08-16T02:22:02.8993303Z   "    dummy {\"message\":\"yay!\"}\r\n" +
2021-08-16T02:22:02.9732556Z   "  </source>\r\n" +
2021-08-16T02:22:03.0746214Z   "  <match dummy>\r\n" +
2021-08-16T02:22:03.3538733Z   "    @type null\r\n" +
2021-08-16T02:22:03.4174346Z   "    @id blackhole\r\n" +
2021-08-16T02:22:04.0182926Z   "  </match>\r\n" +
2021-08-16T02:22:04.0183988Z   "  <match fluent.warn fluent.error fluent.fatal>\r\n" +
2021-08-16T02:22:04.0542068Z   "    @type stdout\r\n" +
2021-08-16T02:22:04.1207617Z   "  </match>\r\n" +
2021-08-16T02:22:04.1627752Z   "</ROOT>\r\n" +
2021-08-16T02:22:04.3784094Z   "2021-08-16 02:21:55 +0000 [info]: starting fluentd-1.14.0.rc pid=604 ruby=\"2.7.4\"\r\n" +
2021-08-16T02:22:04.3807757Z   "2021-08-16 02:21:55 +0000 [info]: spawn command to main:  cmdline=[\"C:/hostedtoolcache/windows/Ruby/2.7.4/x64/bin/ruby.exe\", \"-rC:/hostedtoolcache/windows/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/bundler-2.2.25/lib/bundler/setup\", \"-Eascii-8bit:ascii-8bit\", \"D:/a/fluentd/fluentd/bin/fluentd\", \"-c\", \"D:/a/fluentd/fluentd/test/tmp/command/fluentd/logevent_2.conf\", \"--under-supervisor\"]\r\n">
2021-08-16T02:22:04.5437875Z   was expected to include:
2021-08-16T02:22:04.6348665Z   <["fluentd worker is now running",
2021-08-16T02:22:04.7210498Z    "[warn]: #0 match for some tags of log events are not defined in top level (to be ignored) tags=[\"fluent.trace\", \"fluent.debug\", \"fluent.info\"]",
2021-08-16T02:22:05.0798422Z    "define <match fluent.warn>, <match fluent.error>, <match fluent.fatal> to capture fluentd logs in top level is deprecated. Use <label @FLUENT_LOG> instead",
2021-08-16T02:22:05.1550809Z    "[warn]: #0 no patterns matched tag=\"fluent.info\""]>
2021-08-16T02:22:05.3207606Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:162:in `assert_log_matches'
2021-08-16T02:22:05.5156963Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:362:in `block (2 levels) in <class:TestFluentdCommand>'
2021-08-16T02:22:05.6627210Z      359: </match>
2021-08-16T02:22:05.7548090Z      360: CONF
2021-08-16T02:22:05.9694436Z      361:       conf_path = create_conf_file('logevent_2.conf', conf)
2021-08-16T02:22:06.0954106Z   => 362:       assert_log_matches(
2021-08-16T02:22:06.1912729Z      363:         create_cmdline(conf_path),
2021-08-16T02:22:06.4589703Z      364:         "fluentd worker is now running",
2021-08-16T02:22:06.6613544Z      365:         '[warn]: #0 match for some tags of log events are not defined in top level (to be ignored) tags=["fluent.trace", "fluent.debug", "fluent.info"]',
2021-08-16T02:22:06.9152109Z ===============================================================================
2021-08-16T02:22:06.9813450Z : (10.696810)
2021-08-16T02:22:07.7950549Z   configured to run 2 workers:
2021-08-16T02:22:08.8120864Z     test: -E option is set to RUBYOPT[-E]:		.: (7.817403)
2021-08-16T02:22:18.7573852Z     test: -E option is set to RUBYOPT[-encoding]:	.: (10.019407)
2021-08-16T02:22:28.8464088Z     test: -E option is set to RUBYOPT[-external-encoding]:	.: (10.556173)
2021-08-16T02:22:40.7781413Z     test: -E option is set to RUBYOPT[-internal-encoding]:	.: (11.857187)
2021-08-16T02:22:52.7928125Z     test: failed to start workers when configured plugins as children of MultiOutput do not support multi worker configuration:	F
2021-08-16T02:22:53.0649098Z ===============================================================================
2021-08-16T02:22:53.0689997Z Failure: test: failed to start workers when configured plugins as children of MultiOutput do not support multi worker configuration(TestFluentdCommand::configured to run 2 workers):
2021-08-16T02:22:53.0741625Z   fluentd failed to start, without specified regular expressions:
2021-08-16T02:22:53.0748024Z   2021-08-16 02:22:50 +0000 [info]: parsing config file is succeeded path="D:/a/fluentd/fluentd/test/tmp/command/fluentd/workers_invalid3.conf"
2021-08-16T02:22:53.0752733Z   2021-08-16 02:22:50 +0000 [info]: gem 'fluentd' version '1.14.0.rc'
2021-08-16T02:22:53.0756080Z   2021-08-16 02:22:50 +0000 [warn]: [single] both of Plugin @id and path for <storage> are not specified. Using on-memory store.
2021-08-16T02:22:53.0759985Z   2021-08-16 02:22:50 +0000 [warn]: [single] both of Plugin @id and path for <storage> are not specified. Using on-memory store.
2021-08-16T02:22:53.0764530Z   2021-08-16 02:22:50 +0000 [info]: using configuration file: <ROOT>
2021-08-16T02:22:53.0767401Z     <system>
2021-08-16T02:22:53.0769517Z       workers 2
2021-08-16T02:22:53.0798585Z     </system>
2021-08-16T02:22:53.0966995Z     <source>
2021-08-16T02:22:53.1889995Z       @type dummy
2021-08-16T02:22:53.2452303Z       tag "dummy"
2021-08-16T02:22:53.3451130Z       @id single
2021-08-16T02:22:53.5496862Z       @label @dummydata
2021-08-16T02:22:53.7676375Z     </source>
2021-08-16T02:22:54.1763100Z     <label @dummydata>
2021-08-16T02:22:54.2271021Z       <match dummy>
2021-08-16T02:22:54.2619205Z         @type copy
2021-08-16T02:22:54.3273101Z         <store>
2021-08-16T02:22:54.4023367Z           @type "single"
2021-08-16T02:22:54.5952692Z         </store>
2021-08-16T02:22:55.5776566Z         <store>
2021-08-16T02:22:55.6829341Z           @type "single"
2021-08-16T02:22:55.8082018Z         </store>
2021-08-16T02:22:55.9243307Z       </match>
2021-08-16T02:22:56.0552917Z     </label>
2021-08-16T02:22:56.0800650Z   </ROOT>
2021-08-16T02:22:56.2464781Z   2021-08-16 02:22:50 +0000 [info]: starting fluentd-1.14.0.rc pid=4876 ruby="2.7.4"
2021-08-16T02:22:56.4339805Z   2021-08-16 02:22:50 +0000 [info]: spawn command to main:  cmdline=["C:/hostedtoolcache/windows/Ruby/2.7.4/x64/bin/ruby.exe", "-rC:/hostedtoolcache/windows/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/bundler-2.2.25/lib/bundler/setup", "-Eascii-8bit:ascii-8bit", "D:/a/fluentd/fluentd/bin/fluentd", "-c", "D:/a/fluentd/fluentd/test/tmp/command/fluentd/workers_invalid3.conf", "-p", "D:/a/fluentd/fluentd/test/tmp/command/fluentd/plugin", "--under-supervisor"]
2021-08-16T02:22:59.2253547Z   .
2021-08-16T02:22:59.2253967Z   <false> is not true.
2021-08-16T02:22:59.2254683Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:209:in `assert_fluentd_fails_to_start'
2021-08-16T02:22:59.2255773Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:723:in `block (2 levels) in <class:TestFluentdCommand>'
2021-08-16T02:22:59.2256555Z ===============================================================================
2021-08-16T02:22:59.2256953Z : (12.067584)
2021-08-16T02:23:04.0276415Z     test: failed to start workers when configured plugins do not support multi worker configuration:	F
2021-08-16T02:23:04.0538154Z ===============================================================================
2021-08-16T02:23:04.1096396Z Failure: test: failed to start workers when configured plugins do not support multi worker configuration(TestFluentdCommand::configured to run 2 workers):
2021-08-16T02:23:04.1618854Z   fluentd failed to start, without specified regular expressions:
2021-08-16T02:23:04.2886684Z   .
2021-08-16T02:23:04.3989903Z   <false> is not true.
2021-08-16T02:23:05.2367927Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:209:in `assert_fluentd_fails_to_start'
2021-08-16T02:23:05.5769205Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:648:in `block (2 levels) in <class:TestFluentdCommand>'
2021-08-16T02:23:05.5782741Z ===============================================================================
2021-08-16T02:23:05.6145558Z : (11.228944)
2021-08-16T02:23:18.6365568Z     test: failed to start workers when file buffer is configured in non-workers way:	F
2021-08-16T02:23:18.7132815Z ===============================================================================
2021-08-16T02:23:19.0085815Z Failure: test: failed to start workers when file buffer is configured in non-workers way(TestFluentdCommand::configured to run 2 workers):
2021-08-16T02:23:19.4060141Z   fluentd failed to start, without specified regular expressions:
2021-08-16T02:23:19.6620722Z   .
2021-08-16T02:23:20.1310485Z   <false> is not true.
2021-08-16T02:23:20.1906545Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:209:in `assert_fluentd_fails_to_start'
2021-08-16T02:23:20.2790691Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:677:in `block (2 levels) in <class:TestFluentdCommand>'
2021-08-16T02:23:20.4294521Z ===============================================================================
2021-08-16T02:23:20.4819127Z : (14.484754)
2021-08-16T02:23:20.6734469Z     test: invalid values are set to RUBYOPT:		O
2021-08-16T02:23:20.8671391Z ===============================================================================
2021-08-16T02:23:21.1275655Z Omission: hard to run correctly because RUBYOPT=-r/path/to/bundler/setup is required on Windows while this test set invalid RUBYOPT [test: invalid values are set to RUBYOPT(TestFluentdCommand::configured to run 2 workers)]
2021-08-16T02:23:21.4548451Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:899:in `block (2 levels) in <class:TestFluentdCommand>'
2021-08-16T02:23:21.7318183Z ===============================================================================
2021-08-16T02:23:22.3256466Z : (0.584737)
2021-08-16T02:23:33.7095973Z     test: multiple values are set to RUBYOPT:		F
2021-08-16T02:23:33.8465234Z ===============================================================================
2021-08-16T02:23:33.9445267Z Failure: test: multiple values are set to RUBYOPT(TestFluentdCommand::configured to run 2 workers):
2021-08-16T02:23:34.1869558Z   execution timeout.
2021-08-16T02:23:34.4401193Z   <"WARN: Unresolved or ambiguous specs during Gem::Specification.reset:\r\n" +
2021-08-16T02:23:34.7219799Z   "      power_assert (>= 0)\r\n" +
2021-08-16T02:23:35.6356416Z   "      Available/installed versions of this gem:\r\n" +
2021-08-16T02:23:35.9590813Z   "      - 2.0.0\r\n" +
2021-08-16T02:23:35.9637165Z   "      - 1.1.7\r\n" +
2021-08-16T02:23:35.9925702Z   "WARN: Clearing out unresolved specs. Try 'gem cleanup <gem>'\r\n" +
2021-08-16T02:23:36.0112490Z   "Please report a bug if this causes problems.\r\n" +
2021-08-16T02:23:36.0189965Z   "2021-08-16 02:23:31 +0000 [info]: parsing config file is succeeded path=\"D:/a/fluentd/fluentd/test/tmp/command/fluentd/rubyopt_test.conf\"\r\n" +
2021-08-16T02:23:36.2224951Z   "2021-08-16 02:23:31 +0000 [info]: gem 'fluentd' version '1.14.0.rc'\r\n" +
2021-08-16T02:23:36.2890645Z   "2021-08-16 02:23:32 +0000 [warn]: both of Plugin @id and path for <storage> are not specified. Using on-memory store.\r\n" +
2021-08-16T02:23:36.5179783Z   "2021-08-16 02:23:32 +0000 [warn]: both of Plugin @id and path for <storage> are not specified. Using on-memory store.\r\n" +
2021-08-16T02:23:36.6147738Z   "2021-08-16 02:23:32 +0000 [warn]: define <match fluent.**> to capture fluentd logs in top level is deprecated. Use <label @FLUENT_LOG> instead\r\n" +
2021-08-16T02:23:36.8862350Z   "2021-08-16 02:23:32 +0000 [info]: using configuration file: <ROOT>\r\n" +
2021-08-16T02:23:37.6325281Z   "  <source>\r\n" +
2021-08-16T02:23:37.8298861Z   "    @type dummy\r\n" +
2021-08-16T02:23:37.8341789Z   "    tag \"dummy\"\r\n" +
2021-08-16T02:23:38.1186407Z   "  </source>\r\n" +
2021-08-16T02:23:38.1263510Z   "  <match>\r\n" +
2021-08-16T02:23:38.1688665Z   "    @type null\r\n" +
2021-08-16T02:23:38.3059081Z   "  </match>\r\n" +
2021-08-16T02:23:38.3818396Z   "</ROOT>\r\n" +
2021-08-16T02:23:38.5771404Z   "2021-08-16 02:23:32 +0000 [info]: starting fluentd-1.14.0.rc pid=1472 ruby=\"2.7.4\"\r\n" +
2021-08-16T02:23:38.7029952Z   "2021-08-16 02:23:32 +0000 [info]: spawn command to main:  cmdline=[\"C:/hostedtoolcache/windows/Ruby/2.7.4/x64/bin/ruby.exe\", \"-rC:/hostedtoolcache/windows/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/bundler-2.2.25/lib/bundler/setup\", \"-rtest-unit\", \"-rbundler/setup\", \"-Eascii-8bit:ascii-8bit\", \"D:/a/fluentd/fluentd/bin/fluentd\", \"-c\", \"D:/a/fluentd/fluentd/test/tmp/command/fluentd/rubyopt_test.conf\", \"--under-supervisor\"]\r\n">
2021-08-16T02:23:38.9679439Z   was expected to include:
2021-08-16T02:23:39.3369940Z   <["#0 fluentd worker is now running worker=0"]>
2021-08-16T02:23:39.5606607Z   and not include:
2021-08-16T02:23:39.7756617Z   <["(LoadError)"]>
2021-08-16T02:23:39.9785689Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:162:in `assert_log_matches'
2021-08-16T02:23:40.4611695Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:846:in `block (2 levels) in <class:TestFluentdCommand>'
2021-08-16T02:23:40.6070069Z      843: </match>
2021-08-16T02:23:40.6303509Z      844: CONF
2021-08-16T02:23:40.6688084Z      845:       conf_path = create_conf_file('rubyopt_test.conf', conf)
2021-08-16T02:23:40.8164699Z   => 846:       assert_log_matches(
2021-08-16T02:23:41.1199502Z      847:         create_cmdline(conf_path),
2021-08-16T02:23:41.1636979Z      848:         '#0 fluentd worker is now running worker=0',
2021-08-16T02:23:41.3316423Z      849:         patterns_not_match: ['(LoadError)'],
2021-08-16T02:23:41.4757717Z ===============================================================================
2021-08-16T02:23:41.4801845Z : (14.450838)
2021-08-16T02:23:46.9277843Z     test: ruby path contains spaces:			F
2021-08-16T02:23:47.2323484Z ===============================================================================
2021-08-16T02:23:47.2332867Z Failure: test: ruby path contains spaces(TestFluentdCommand::configured to run 2 workers):
2021-08-16T02:23:47.3043632Z   execution timeout.
2021-08-16T02:23:48.1249871Z   <"\r\n" +
2021-08-16T02:23:48.3711526Z   "D:\\a\\fluentd\\fluentd\\test\\tmp\\command\\fluentd>C:/hostedtoolcache/windows/Ruby/2.7.4/x64/bin/ruby.exe D:/a/fluentd/fluentd/bin/fluentd -c D:/a/fluentd/fluentd/test/tmp/command/fluentd/space_mixed_ruby_path_test.conf \r\n">
2021-08-16T02:23:48.7677097Z   was expected to include:
2021-08-16T02:23:49.2523139Z   <["spawn command to main:", "-Eascii-8bit:ascii-8bit"]>
2021-08-16T02:23:49.6254567Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:162:in `assert_log_matches'
2021-08-16T02:23:49.8413971Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:944:in `block (2 levels) in <class:TestFluentdCommand>'
2021-08-16T02:23:50.4400780Z      941:       cmd_path = File.expand_path(File.dirname(__FILE__) + "../../../bin/fluentd")
2021-08-16T02:23:50.4478844Z      942:       conf_path = create_conf_file('space_mixed_ruby_path_test.conf', conf)
2021-08-16T02:23:50.6443760Z      943:       args = ["bundle", "exec", tmp_ruby_path, cmd_path, "-c", conf_path]
2021-08-16T02:23:50.7164544Z   => 944:       assert_log_matches(
2021-08-16T02:23:51.0726198Z      945:         args,
2021-08-16T02:23:51.5554374Z      946:         'spawn command to main:',
2021-08-16T02:23:51.8612618Z      947:         '-Eascii-8bit:ascii-8bit'
2021-08-16T02:23:52.0884333Z ===============================================================================
2021-08-16T02:23:52.6060125Z : (13.103954)
2021-08-16T02:24:01.9370197Z     test: success to start a worker with worker specific configuration:	F
2021-08-16T02:24:02.1783146Z ===============================================================================
2021-08-16T02:24:02.2500696Z Failure: test: success to start a worker with worker specific configuration(TestFluentdCommand::configured to run 2 workers):
2021-08-16T02:24:02.3276189Z   execution timeout.
2021-08-16T02:24:02.4546912Z   <"">
2021-08-16T02:24:02.5124178Z   was expected to include:
2021-08-16T02:24:02.6210625Z   <["#0 fluentd worker is now running worker=0",
2021-08-16T02:24:03.0395561Z    "#1 fluentd worker is now running worker=1",
2021-08-16T02:24:04.0241319Z    /(?!#\d) adding source type="dummy"/,
2021-08-16T02:24:04.4118933Z    "#1 adding source type=\"dummy\""]>
2021-08-16T02:24:04.6414637Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:162:in `assert_log_matches'
2021-08-16T02:24:04.8468223Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:783:in `block (2 levels) in <class:TestFluentdCommand>'
2021-08-16T02:24:05.0481617Z ===============================================================================
2021-08-16T02:24:05.1020789Z : (14.942786)
2021-08-16T02:24:15.3538334Z     test: success to start a worker2 with worker specific configuration:F
2021-08-16T02:24:15.3684357Z ===============================================================================
2021-08-16T02:24:15.3704109Z Failure: test: success to start a worker2 with worker specific configuration(TestFluentdCommand::configured to run 2 workers):
2021-08-16T02:24:15.4661466Z   execution timeout.
2021-08-16T02:24:16.0897384Z   <"">
2021-08-16T02:24:16.9776086Z   was expected to include:
2021-08-16T02:24:16.9822102Z   <["spawn command to main"]>
2021-08-16T02:24:17.1086852Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:162:in `assert_log_matches'
2021-08-16T02:24:17.1983563Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:741:in `block (2 levels) in <class:TestFluentdCommand>'
2021-08-16T02:24:17.2010800Z      738:       FileUtils.rm_rf(@root_path) rescue nil
2021-08-16T02:24:17.3715420Z      739:
2021-08-16T02:24:17.4016003Z      740:       assert_path_not_exist(@root_path)
2021-08-16T02:24:17.4020036Z   => 741:       assert_log_matches(create_cmdline(conf_path), 'spawn command to main') # any message is ok
2021-08-16T02:24:17.4025591Z      742:       assert_path_exist(@root_path)
2021-08-16T02:24:17.4058365Z      743:       if Fluent.windows?
2021-08-16T02:24:17.6335030Z      744:         # In Windows, dir permission is always 755.
2021-08-16T02:24:17.8704556Z ===============================================================================
2021-08-16T02:24:17.8773964Z : (13.790245)
2021-08-16T02:24:31.3250386Z     test: success to start the number of workers specified by command line option:	F
2021-08-16T02:24:31.3252569Z ===============================================================================
2021-08-16T02:24:31.5713151Z Failure: test: success to start the number of workers specified by command line option(TestFluentdCommand::configured to run 2 workers):
2021-08-16T02:24:31.7077170Z   execution timeout.
2021-08-16T02:24:31.7799582Z   <"">
2021-08-16T02:24:31.9277869Z   was expected to include:
2021-08-16T02:24:32.1105624Z   <["#0 fluentd worker is now running worker=0",
2021-08-16T02:24:32.1479931Z    "#1 fluentd worker is now running worker=1"]>
2021-08-16T02:24:32.4280644Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:162:in `assert_log_matches'
2021-08-16T02:24:32.6272543Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:612:in `block (2 levels) in <class:TestFluentdCommand>'
2021-08-16T02:24:32.6306614Z ===============================================================================
2021-08-16T02:24:32.6695398Z : (15.344046)
2021-08-16T02:24:45.4996752Z     test: success to start the number of workers specified in configuration:	F
2021-08-16T02:24:45.5054007Z ===============================================================================
2021-08-16T02:24:45.6518271Z Failure: test: success to start the number of workers specified in configuration(TestFluentdCommand::configured to run 2 workers):
2021-08-16T02:24:45.8571191Z   execution timeout.
2021-08-16T02:24:46.1356411Z   <"">
2021-08-16T02:24:46.2367075Z   was expected to include:
2021-08-16T02:24:46.2848454Z   <["#0 fluentd worker is now running worker=0",
2021-08-16T02:24:46.3504077Z    "#1 fluentd worker is now running worker=1"]>
2021-08-16T02:24:46.4495123Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:162:in `assert_log_matches'
2021-08-16T02:24:46.5012613Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:585:in `block (2 levels) in <class:TestFluentdCommand>'
2021-08-16T02:24:46.5499772Z ===============================================================================
2021-08-16T02:24:46.5614476Z : (14.177524)
2021-08-16T02:24:58.8523595Z     test: success to start workers when configured plugins as a children of MultiOutput only for specific worker do not support multi worker configuration:	F
2021-08-16T02:24:58.9439844Z ===============================================================================
2021-08-16T02:24:59.1885626Z Failure: test: success to start workers when configured plugins as a children of MultiOutput only for specific worker do not support multi worker configuration(TestFluentdCommand::configured to run 2 workers):
2021-08-16T02:24:59.3642361Z   execution timeout.
2021-08-16T02:24:59.4354961Z   <"">
2021-08-16T02:24:59.6046382Z   was expected to include:
2021-08-16T02:24:59.6587548Z   <["#0 fluentd worker is now running worker=0",
2021-08-16T02:24:59.8110369Z    "#1 fluentd worker is now running worker=1",
2021-08-16T02:24:59.8587354Z    "#1 adding match pattern=\"dummy\" type=\"copy\""]>
2021-08-16T02:24:59.8693538Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:162:in `assert_log_matches'
2021-08-16T02:25:00.0290262Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:1023:in `block (2 levels) in <class:TestFluentdCommand>'
2021-08-16T02:25:00.1131064Z ===============================================================================
2021-08-16T02:25:00.1493629Z : (13.787508)
2021-08-16T02:25:13.0834411Z     test: success to start workers when configured plugins only for specific worker do not support multi worker configuration:	F
2021-08-16T02:25:13.1687749Z ===============================================================================
2021-08-16T02:25:13.1698168Z Failure: test: success to start workers when configured plugins only for specific worker do not support multi worker configuration(TestFluentdCommand::configured to run 2 workers):
2021-08-16T02:25:13.4974277Z   execution timeout.
2021-08-16T02:25:13.6705011Z   <"">
2021-08-16T02:25:13.7590145Z   was expected to include:
2021-08-16T02:25:13.8468111Z   <["#0 fluentd worker is now running worker=0",
2021-08-16T02:25:13.8629245Z    "#1 fluentd worker is now running worker=1",
2021-08-16T02:25:14.2473093Z    "#1 adding source type=\"single\""]>
2021-08-16T02:25:14.6427443Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:162:in `assert_log_matches'
2021-08-16T02:25:15.5998748Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:827:in `block (2 levels) in <class:TestFluentdCommand>'
2021-08-16T02:25:15.6741678Z ===============================================================================
2021-08-16T02:25:16.0076019Z : (14.322403)
2021-08-16T02:25:27.0558074Z     test: success to start workers when file buffer is configured in non-workers way only for specific worker:	F
2021-08-16T02:25:27.0872141Z ===============================================================================
2021-08-16T02:25:27.2211695Z Failure: test: success to start workers when file buffer is configured in non-workers way only for specific worker(TestFluentdCommand::configured to run 2 workers):
2021-08-16T02:25:27.6457006Z   execution timeout.
2021-08-16T02:25:27.7695524Z   <"">
2021-08-16T02:25:28.1293144Z   was expected to include:
2021-08-16T02:25:28.7327779Z   <["#0 fluentd worker is now running worker=0",
2021-08-16T02:25:29.0931909Z    "#1 fluentd worker is now running worker=1",
2021-08-16T02:25:29.1746847Z    "#1 adding match pattern=\"dummy\" type=\"null\""]>
2021-08-16T02:25:29.4746711Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:162:in `assert_log_matches'
2021-08-16T02:25:29.5004702Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:976:in `block (2 levels) in <class:TestFluentdCommand>'
2021-08-16T02:25:29.6543701Z ===============================================================================
2021-08-16T02:25:30.1404321Z : (13.619544)
2021-08-16T02:25:42.7194648Z     test: without RUBYOPT:				.: (15.288406)
2021-08-16T02:25:42.7665429Z   configured to suppress configuration dump:
2021-08-16T02:25:58.2687250Z     test: configured as false by system config, but overridden as true by command line option:	F
2021-08-16T02:25:58.4195381Z ===============================================================================
2021-08-16T02:25:58.5099976Z Failure: test: configured as false by system config, but overridden as true by command line option(TestFluentdCommand::configured to suppress configuration dump):
2021-08-16T02:25:58.5495466Z   execution timeout.
2021-08-16T02:25:58.5866234Z   <"">
2021-08-16T02:25:58.6367102Z   was expected to include:
2021-08-16T02:25:58.9443851Z   <["fluentd worker is now running"]>
2021-08-16T02:25:59.0224025Z   and not include:
2021-08-16T02:25:59.3498832Z   <["tag dummy"]>
2021-08-16T02:25:59.4007387Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:162:in `assert_log_matches'
2021-08-16T02:25:59.5130988Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:450:in `block (2 levels) in <class:TestFluentdCommand>'
2021-08-16T02:25:59.8369691Z      447: </system>
2021-08-16T02:26:00.6629942Z      448: SYSTEM
2021-08-16T02:26:00.8086738Z      449:       conf_path = create_conf_file('suppress_conf_dump_3.conf', conf)
2021-08-16T02:26:00.9968360Z   => 450:       assert_log_matches(create_cmdline(conf_path, '--suppress-config-dump'), "fluentd worker is now running", patterns_not_match: ["tag dummy"])
2021-08-16T02:26:01.4693678Z      451:     end
2021-08-16T02:26:01.4718429Z      452:   end
2021-08-16T02:26:01.4725331Z      453:
2021-08-16T02:26:01.4729889Z ===============================================================================
2021-08-16T02:26:01.4732465Z : (15.895562)
2021-08-16T02:26:12.1605131Z     test: configured by command line option:		F
2021-08-16T02:26:12.1695702Z ===============================================================================
2021-08-16T02:26:12.3698798Z Failure: test: configured by command line option(TestFluentdCommand::configured to suppress configuration dump):
2021-08-16T02:26:12.5022881Z   execution timeout.
2021-08-16T02:26:12.6265949Z   <"">
2021-08-16T02:26:12.7954730Z   was expected to include:
2021-08-16T02:26:12.8945818Z   <["fluentd worker is now running"]>
2021-08-16T02:26:13.5118631Z   and not include:
2021-08-16T02:26:13.8405861Z   <["tag dummy"]>
2021-08-16T02:26:13.8461721Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:162:in `assert_log_matches'
2021-08-16T02:26:13.8521453Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:440:in `block (2 levels) in <class:TestFluentdCommand>'
2021-08-16T02:26:15.0746243Z      437:
2021-08-16T02:26:15.4683384Z      438:     test 'configured by command line option' do
2021-08-16T02:26:16.0205697Z      439:       conf_path = create_conf_file('suppress_conf_dump_2.conf', @basic_conf)
2021-08-16T02:26:16.0686530Z   => 440:       assert_log_matches(create_cmdline(conf_path, '--suppress-config-dump'), "fluentd worker is now running", patterns_not_match: ["tag dummy"])
2021-08-16T02:26:16.4662320Z      441:     end
2021-08-16T02:26:16.5536995Z      442:
2021-08-16T02:26:16.5548150Z      443:     test 'configured as false by system config, but overridden as true by command line option' do
2021-08-16T02:26:16.8972171Z ===============================================================================
2021-08-16T02:26:16.9974488Z : (14.332296)
2021-08-16T02:26:31.2795786Z     test: configured by system config:			F
2021-08-16T02:26:31.2800855Z ===============================================================================
2021-08-16T02:26:31.2810299Z Failure: test: configured by system config(TestFluentdCommand::configured to suppress configuration dump):
2021-08-16T02:26:31.2811392Z   execution timeout.
2021-08-16T02:26:31.2811788Z   <"">
2021-08-16T02:26:31.2812242Z   was expected to include:
2021-08-16T02:26:31.2812760Z   <["fluentd worker is now running"]>
2021-08-16T02:26:31.2813242Z   and not include:
2021-08-16T02:26:31.2813621Z   <["tag dummy"]>
2021-08-16T02:26:31.2814259Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:162:in `assert_log_matches'
2021-08-16T02:26:31.2815326Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:435:in `block (2 levels) in <class:TestFluentdCommand>'
2021-08-16T02:26:31.2816072Z      432: </system>
2021-08-16T02:26:31.2816460Z      433: SYSTEM
2021-08-16T02:26:31.2817015Z      434:       conf_path = create_conf_file('suppress_conf_dump_1.conf', conf)
2021-08-16T02:26:31.2818153Z   => 435:       assert_log_matches(create_cmdline(conf_path), "fluentd worker is now running", patterns_not_match: ["tag dummy"])
2021-08-16T02:26:31.2818860Z      436:     end
2021-08-16T02:26:31.2819210Z      437:
2021-08-16T02:26:31.2819690Z      438:     test 'configured by command line option' do
2021-08-16T02:26:31.2820350Z ===============================================================================
2021-08-16T02:26:31.2820726Z : (14.913324)
2021-08-16T02:26:31.2821142Z   sahred socket options:
2021-08-16T02:26:42.7051293Z     test: disable shared socket by command line option:	F
2021-08-16T02:26:42.7059421Z ===============================================================================
2021-08-16T02:26:42.8191558Z Failure: test: disable shared socket by command line option(TestFluentdCommand::sahred socket options):
2021-08-16T02:26:43.2637478Z   execution timeout.
2021-08-16T02:26:43.8465588Z   <"">
2021-08-16T02:26:44.3460160Z   was expected to include:
2021-08-16T02:26:44.3953281Z   <["shared socket for multiple workers is disabled"]>
2021-08-16T02:26:44.7079595Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:162:in `assert_log_matches'
2021-08-16T02:26:44.8821940Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:1090:in `block (2 levels) in <class:TestFluentdCommand>'
2021-08-16T02:26:44.8974555Z      1087:       conf = ""
2021-08-16T02:26:45.0064839Z      1088:       conf_path = create_conf_file('empty.conf', conf)
2021-08-16T02:26:45.0455493Z      1089:       assert File.exist?(conf_path)
2021-08-16T02:26:45.0970456Z   => 1090:       assert_log_matches(create_cmdline(conf_path, "--disable-shared-socket"),
2021-08-16T02:26:45.1977601Z      1091:                          "shared socket for multiple workers is disabled",)
2021-08-16T02:26:45.2253282Z      1092:     end
2021-08-16T02:26:46.0857719Z      1093:
2021-08-16T02:26:46.3867219Z ===============================================================================
2021-08-16T02:26:46.5359555Z : (15.400659)
2021-08-16T02:26:58.0150434Z     test: disable shared socket by system config:	F
2021-08-16T02:26:58.2589507Z ===============================================================================
2021-08-16T02:26:58.3721373Z Failure: test: disable shared socket by system config(TestFluentdCommand::sahred socket options):
2021-08-16T02:26:58.9129714Z   execution timeout.
2021-08-16T02:26:59.2994590Z   <"">
2021-08-16T02:26:59.2996373Z   was expected to include:
2021-08-16T02:26:59.3015854Z   <["shared socket for multiple workers is disabled"]>
2021-08-16T02:26:59.4700100Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:162:in `assert_log_matches'
2021-08-16T02:26:59.6152804Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:1102:in `block (2 levels) in <class:TestFluentdCommand>'
2021-08-16T02:26:59.7149011Z      1099: CONF
2021-08-16T02:26:59.8527498Z      1100:       conf_path = create_conf_file('empty.conf', conf)
2021-08-16T02:26:59.9072040Z      1101:       assert File.exist?(conf_path)
2021-08-16T02:27:00.1555976Z   => 1102:       assert_log_matches(create_cmdline(conf_path, "--disable-shared-socket"),
2021-08-16T02:27:00.2077093Z      1103:                          "shared socket for multiple workers is disabled",)
2021-08-16T02:27:00.2334196Z      1104:     end
2021-08-16T02:27:00.5294421Z      1105:   end
2021-08-16T02:27:00.5324747Z ===============================================================================
2021-08-16T02:27:00.9208047Z : (15.607050)
2021-08-16T02:27:12.5576076Z     test: enable shared socket by default:		F
2021-08-16T02:27:12.5662729Z ===============================================================================
2021-08-16T02:27:12.6076279Z Failure: test: enable shared socket by default(TestFluentdCommand::sahred socket options):
2021-08-16T02:27:13.0482056Z   execution timeout.
2021-08-16T02:27:13.3152910Z   <"">
2021-08-16T02:27:13.3212057Z   was expected to include:
2021-08-16T02:27:13.9235463Z   <[]>
2021-08-16T02:27:14.4026044Z   and not include:
2021-08-16T02:27:14.8247974Z   <["shared socket for multiple workers is disabled"]>
2021-08-16T02:27:14.8761622Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:162:in `assert_log_matches'
2021-08-16T02:27:14.9600544Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:1082:in `block (2 levels) in <class:TestFluentdCommand>'
2021-08-16T02:27:15.0350548Z      1079:       conf = ""
2021-08-16T02:27:15.1404399Z      1080:       conf_path = create_conf_file('empty.conf', conf)
2021-08-16T02:27:15.1604756Z      1081:       assert File.exist?(conf_path)
2021-08-16T02:27:15.3499530Z   => 1082:       assert_log_matches(create_cmdline(conf_path),
2021-08-16T02:27:15.4365244Z      1083:                          patterns_not_match: ["shared socket for multiple workers is disabled"])
2021-08-16T02:27:15.4667975Z      1084:     end
2021-08-16T02:27:15.5563050Z      1085:
2021-08-16T02:27:15.7573782Z ===============================================================================
2021-08-16T02:27:15.7845088Z : (14.274697)
2021-08-16T02:27:16.0156269Z   with --conf-encoding:
2021-08-16T02:27:28.6179356Z     test: failed to run by invalid encoding:		F
2021-08-16T02:27:28.6634746Z ===============================================================================
2021-08-16T02:27:28.7731368Z Failure: test: failed to run by invalid encoding(TestFluentdCommand::with --conf-encoding):
2021-08-16T02:27:28.8301285Z   fluentd failed to start, without specified regular expressions:
2021-08-16T02:27:33.0447444Z   .
2021-08-16T02:27:33.0447981Z   <false> is not true.
2021-08-16T02:27:33.0448706Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:209:in `assert_fluentd_fails_to_start'
2021-08-16T02:27:33.0449823Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:266:in `block (2 levels) in <class:TestFluentdCommand>'
2021-08-16T02:27:33.0450698Z      263: </match>
2021-08-16T02:27:33.0451119Z      264: CONF
2021-08-16T02:27:33.0451693Z      265:       conf_path = create_conf_file('shift_jis.conf', conf, 'shift_jis')
2021-08-16T02:27:33.0452656Z   => 266:       assert_fluentd_fails_to_start(create_cmdline(conf_path), "invalid byte sequence in UTF-8")
2021-08-16T02:27:33.0453369Z      267:     end
2021-08-16T02:27:33.0597891Z      268:   end
2021-08-16T02:27:33.0598328Z      269:
2021-08-16T02:27:33.0598734Z ===============================================================================
2021-08-16T02:27:33.0599206Z : (16.121889)
2021-08-16T02:27:44.2538558Z     test: runs successfully:				F
2021-08-16T02:27:44.3103220Z ===============================================================================
2021-08-16T02:27:44.5139021Z Failure: test: runs successfully(TestFluentdCommand::with --conf-encoding):
2021-08-16T02:27:44.6283411Z   execution timeout.
2021-08-16T02:27:44.6457167Z   <"">
2021-08-16T02:27:44.7003648Z   was expected to include:
2021-08-16T02:27:44.7955695Z   <["fluentd worker is now running", "worker=0"]>
2021-08-16T02:27:44.8407270Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:162:in `assert_log_matches'
2021-08-16T02:27:44.8992362Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:250:in `block (2 levels) in <class:TestFluentdCommand>'
2021-08-16T02:27:45.0777744Z      247: </match>
2021-08-16T02:27:46.0719264Z      248: CONF
2021-08-16T02:27:46.1806210Z      249:       conf_path = create_conf_file('shift_jis.conf', conf, 'shift_jis')
2021-08-16T02:27:46.2352181Z   => 250:       assert_log_matches(create_cmdline(conf_path, '--conf-encoding', 'shift_jis'), "fluentd worker is now running", 'worker=0')
2021-08-16T02:27:46.2856202Z      251:     end
2021-08-16T02:27:46.4096396Z      252:
2021-08-16T02:27:46.4716436Z      253:     test 'failed to run by invalid encoding' do
2021-08-16T02:27:46.6811994Z ===============================================================================
2021-08-16T02:27:47.5210181Z : (15.189270)
2021-08-16T02:27:47.7633465Z   with system configuration about root directory:
2021-08-16T02:27:56.6326681Z     test: creates the specified root directory if missing:	F
2021-08-16T02:27:56.6614760Z ===============================================================================
2021-08-16T02:27:56.9911398Z Failure: test: creates the specified root directory if missing(TestFluentdCommand::with system configuration about root directory):
2021-08-16T02:27:57.1895568Z   execution timeout.
2021-08-16T02:27:57.3101727Z   <"">
2021-08-16T02:27:57.3582956Z   was expected to include:
2021-08-16T02:27:57.6079959Z   <["fluentd worker is now running", "worker=0"]>
2021-08-16T02:27:57.6596183Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:162:in `assert_log_matches'
2021-08-16T02:27:58.0070568Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:306:in `block (2 levels) in <class:TestFluentdCommand>'
2021-08-16T02:27:58.0570201Z      303:       conf_path = create_conf_file('missing_root_dir.conf', @conf)
2021-08-16T02:27:58.1891711Z      304:       assert_false Dir.exist?(@root_path)
2021-08-16T02:27:58.2619887Z      305:
2021-08-16T02:27:58.4482602Z   => 306:       assert_log_matches(create_cmdline(conf_path), "fluentd worker is now running", 'worker=0')
2021-08-16T02:27:59.1227528Z      307:       assert Dir.exist?(@root_path)
2021-08-16T02:27:59.2532846Z      308:     end
2021-08-16T02:27:59.5566272Z      309:
2021-08-16T02:27:59.7389943Z ===============================================================================
2021-08-16T02:28:00.2386818Z : (12.960674)
2021-08-16T02:28:12.1309573Z     test: fails to launch fluentd if specified root path is invalid path for directory:	F
2021-08-16T02:28:12.1790276Z ===============================================================================
2021-08-16T02:28:12.7154999Z Failure: test: fails to launch fluentd if specified root path is invalid path for directory(TestFluentdCommand::with system configuration about root directory):
2021-08-16T02:28:12.7260587Z   fluentd failed to start, without specified regular expressions:
2021-08-16T02:28:12.8749566Z   .
2021-08-16T02:28:12.9307716Z   <false> is not true.
2021-08-16T02:28:13.0479604Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:209:in `assert_fluentd_fails_to_start'
2021-08-16T02:28:13.1122169Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:316:in `block (2 levels) in <class:TestFluentdCommand>'
2021-08-16T02:28:13.2357938Z      313:       end
2021-08-16T02:28:14.1482013Z      314:       conf_path = create_conf_file('existing_root_dir.conf', @conf)
2021-08-16T02:28:14.2057834Z      315:
2021-08-16T02:28:14.2087580Z   => 316:       assert_fluentd_fails_to_start(
2021-08-16T02:28:14.2597368Z      317:         create_cmdline(conf_path),
2021-08-16T02:28:14.3598317Z      318:         "non directory entry exists:#{@root_path}",
2021-08-16T02:28:14.7483134Z      319:       )
2021-08-16T02:28:15.2010614Z ===============================================================================
2021-08-16T02:28:15.5465130Z : (15.485838)
2021-08-16T02:28:26.9916075Z     test: use the specified existing directory as root:	F
2021-08-16T02:28:27.0602758Z ===============================================================================
2021-08-16T02:28:27.0645790Z Failure: test: use the specified existing directory as root(TestFluentdCommand::with system configuration about root directory):
2021-08-16T02:28:27.0648457Z   execution timeout.
2021-08-16T02:28:27.0650706Z   <"">
2021-08-16T02:28:27.0651843Z   was expected to include:
2021-08-16T02:28:27.0654393Z   <["fluentd worker is now running", "worker=0"]>
2021-08-16T02:28:27.0657050Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:162:in `assert_log_matches'
2021-08-16T02:28:27.0659501Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:299:in `block (2 levels) in <class:TestFluentdCommand>'
2021-08-16T02:28:27.0662106Z      296:       conf_path = create_conf_file('existing_root_dir.conf', @conf)
2021-08-16T02:28:27.0663541Z      297:       assert Dir.exist?(@root_path)
2021-08-16T02:28:27.0664939Z      298:
2021-08-16T02:28:27.0666503Z   => 299:       assert_log_matches(create_cmdline(conf_path), "fluentd worker is now running", 'worker=0')
2021-08-16T02:28:27.0668733Z      300:     end
2021-08-16T02:28:27.0671758Z      301:
2021-08-16T02:28:27.0673836Z      302:     test 'creates the specified root directory if missing' do
2021-08-16T02:28:27.0676188Z ===============================================================================
2021-08-16T02:28:27.0677357Z : (14.417933)
2021-08-16T02:28:27.0679001Z   with valid configuration:
2021-08-16T02:28:40.4620055Z     test: runs successfully:				F
2021-08-16T02:28:40.4890651Z ===============================================================================
2021-08-16T02:28:40.6099879Z Failure: test: runs successfully(TestFluentdCommand::with valid configuration):
2021-08-16T02:28:40.7373970Z   execution timeout.
2021-08-16T02:28:41.0656445Z   <"">
2021-08-16T02:28:41.1286000Z   was expected to include:
2021-08-16T02:28:41.6306989Z   <["fluentd worker is now running", "worker=0"]>
2021-08-16T02:28:41.6902133Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:162:in `assert_log_matches'
2021-08-16T02:28:41.7091293Z D:/a/fluentd/fluentd/test/command/test_fluentd.rb:232:in `block (2 levels) in <class:TestFluentdCommand>'
2021-08-16T02:28:41.8029961Z ===============================================================================
2021-08-16T02:28:42.9853614Z : (13.734773)
2021-08-16T02:28:43.0381391Z TestFluentdCtl:
2021-08-16T02:28:43.0958911Z   test_commands[shutdown]:				.: (0.075510)
2021-08-16T02:28:43.2697143Z   test_commands[restart]:				.: (0.014718)
2021-08-16T02:28:43.6279570Z   test_commands[flush]:					.: (0.007112)
2021-08-16T02:28:43.6863828Z   test_commands[reload]:				.: (0.051405)
2021-08-16T02:28:43.7492588Z   test_commands_with_winsvcname[shutdown]:		The specified service does not exist as an installed service. - OpenService: The specified service does not exist as an installed service.

Additional context
No response

Hmm, each tests are succeeded when I run them individually.
e.g.)
>bundle exec rake test TEST=test/command/test_fluentd.rb TESTOPTS="--name=\"test: success to start a worker2 with worker specific configuration\""
test_file_util.rb for non-root user env. Disable this test on root environment
C:/Ruby27-x64/bin/ruby.exe -w -I"lib;test" -Eascii-8bit:ascii-8bit C:/Users/aho/Projects/fluentd/vendor/bundle/ruby/2.7.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb "test/command/test_fluentd.rb" --name="test: success to start a worker2 with worker specific configuration"
C:/Users/aho/Projects/fluentd/lib/fluent/config/literal_parser.rb:194: warning: assigned but unused variable - e
C:/Users/aho/Projects/fluentd/vendor/bundle/ruby/2.7.0/gems/serverengine-2.2.4-x64-mingw32/lib/serverengine/socket_manager_win.rb:140: warning: assigned but unused variable - type
C:/Users/aho/Projects/fluentd/lib/fluent/plugin_helper.rb:46: warning: method redefined; discarding old inherited
C:/Users/aho/Projects/fluentd/lib/fluent/plugin_helper.rb:46: warning: previous definition of inherited was here
C:/Users/aho/Projects/fluentd/lib/fluent/plugin/parser_syslog.rb:487: warning: assigned but unused variable - e
Loaded suite C:/Users/aho/Projects/fluentd/vendor/bundle/ruby/2.7.0/gems/rake-13.0.6/lib/rake/rake_test_loader
Started
.
Finished in 2.4104524 seconds.
--------------------------------------------------------------------------------------------------------------------------------------------------------------
1 tests, 4 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
100% passed
--------------------------------------------------------------------------------------------------------------------------------------------------------------
0.41 tests/s, 1.66 assertions/s


Add predict_one to preditor.

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Please tag this pr with at least one of these labels to make our release process faster: BREAKING, new feature, bug fix, other change, dev setup

I think this makes sense to have

In general, there are two kinds of predictors, those who can predict one item, and those who predict batches. Currently we have lumped everything together.
What we could do is to introduce BatchPredictor and OnePredictor (or something along those lines) and then derive from either of these.
But maybe we start with this for now and think about generalising later?


Preprints - Save the children/documentation explainations

Purpose
A complicated fix for a seemingly easy problem! ember-preprints subjects on the discover page were showing a caret even if there were no children there to load - the request for more children wasn't being made until the carat was clicked, so there was no way to know weather or not to load the carrot or not.
This change adds children as another foreign field, which is set in the update_taxonomies script, so that ember-preprints can know how many children there are before making the request, thus weather or not to show the carrot in advance
h/t to @sloria for much help
Also at request of @brianjgeiger add message to preprint related API routes that the API routes are in flux!
Changes

add child count to the taxonomies serializer  (added here in attributes instead of in extra for simplicity when reading from ember for speed sake)
add child_count property to Subjects
add children as foreign field to Subjects cause why not be proper
use update_taxonomies script to also set the children
update preprints realted views with caveat message

Side effects
Must run update_taxonomies again to make sure all children are saved, orelse all children counts will be 0
An ember-osf PR will rely on this to get accurate carrts or not
Ticket
https://trello.com/c/GETV8yQ1/111-preprints-discover-the-caret-does-no-action

Closing in favor of #6238 ♨


closes #543

Codecov Report

Merging #546 into master will decrease coverage by 0.03%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master     #546      +/-   ##
==========================================
- Coverage   91.22%   91.19%   -0.04%
==========================================
  Files          37       37
  Lines        2371     2374       +3
  Branches      213      213
==========================================
+ Hits         2163     2165       +2
- Misses        158      159       +1
  Partials       50       50

Impacted Files
Coverage Δ

...hBoundControllerAbstraction/proxy/faucet/parser.py
65.25% <66.66%> (+0.03%)
:arrow_up:

Continue to review full report at Codecov.

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


Documentation - Import/export csv UG and markdown DG updates

Purpose
This PR updates the content on the components which I worked on.
WIP as I am still updating DG
Current live version can be viewed here

Codecov Report

Merging #251 (398dd6c) into master (d38a548) will increase coverage by 0.31%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #251      +/-   ##
============================================
+ Coverage     72.36%   72.68%   +0.31%
- Complexity     1205     1235      +30
============================================
  Files           156      159       +3
  Lines          3666     3774     +108
  Branches        440      445       +5
============================================
+ Hits           2653     2743      +90
- Misses          938      952      +14
- Partials         75       79       +4

Impacted Files
Coverage Δ

...va/seedu/contax/model/appointment/Appointment.java
97.91% <0.00%> (-2.09%)
:arrow_down:

...a/seedu/contax/storage/JsonAdaptedAppointment.java
98.18% <0.00%> (-1.82%)
:arrow_down:

src/main/java/seedu/contax/ui/TextStyleHelper.java
91.07% <0.00%> (-0.31%)
:arrow_down:

...rc/main/java/seedu/contax/model/person/Person.java
100.00% <0.00%> (ø)

...java/seedu/contax/logic/commands/ChainCommand.java
100.00% <0.00%> (ø)

...ava/seedu/contax/logic/parser/ImportCsvParser.java
100.00% <0.00%> (ø)

...a/seedu/contax/logic/parser/AddressBookParser.java
100.00% <0.00%> (ø)

.../seedu/contax/logic/commands/ImportCsvCommand.java
100.00% <0.00%> (ø)

...ax/ui/appointment/cardfactory/AppointmentCard.java
0.00% <0.00%> (ø)

...edu/contax/logic/commands/EditPriorityCommand.java
100.00% <0.00%> (ø)

... and 5 more

Continue to review full report at Codecov.

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


[7.x] Add withBearerToken() helper method

This PR adds a small helper method for tests using Authorization Bearer tokens as part of request headers. It was inspired by the existing $request->bearerToken() method on the Illuminate\Http\Request class, which is also really useful.
I feel this allows requests inside tests to read a little nicer, as well as helps against typos when writing "Authorization" and "Bearer" over and over, and instead IDEs can autocomplete the method.
$response = $this->withHeader('Authorization', 'Bearer test_token')->postJson('/some-endpoint');

$response = $this->withBearerToken('test_token')->postJson('/some-endpoint');

There are no breaking changes, and I've added a small test to verify everything works as expected.
Happy to make changes if there's any feedback!

I just noticed that the Illuminate\Http\Client\PendingRequest class uses withToken() which is even better/shorter and allows overriding the default "Bearer" type.
I'll push an update to make this method more dynamic shortly!

Please also rebase this PR against the latest 7.x codebase. :)

Whoops, I think I did something wrong while rebasing! Apologies if this sent out a bunch of notifications 🤦♂
@GrahamCampbell Sorry about this, what's the best way to fix this? Should I create a new PR and ensure my branch is on latest 7.x?

It can be easier just copy the your commits hash sequentially (since it's not many), reset hard the branch to the latest upstream commit, cherry pick your commits and then a push force.

Thanks @lcdss, I ended up doing something similar -- looks ok now (I think)

The PR is now ready for review!
The method changed slightly since my original message, so here's an updated snippet to demonstrate its usefulness:
$response = $this->withHeader('Authorization', 'Bearer test_token')->postJson('/some-endpoint');

$response = $this->withToken('test_token')->postJson('/some-endpoint');

Much shorter and more readable I think — hope you agree 😊
Let me know if there's any feedback!


remove SignupQueued screen

Doesn't seem necessary anymore. Has some stuff that will need to get changed w/ new XRPC rework, easier to just rm this screen.

Leaving this in.


Modify swapchain.rs to use undeprecated functions

The swapchain.rs file uses the get_capabilities() function, which is deprecated.
Instead, the new capabilities() function should be used.
However, because get_capabilities always unwraps and returns Ok() , and capabilities returns CapabiltiesError, there might be some modification needed to the Swapchain::new_inner function.

One possible solution that doesn't change the API or contain any sort of externally visible change is to use the new function and panic! on error:
let capabilities = match surface.capabilities(device.physical_device()) {
            Ok(caps) => caps,
            Err(err) => match err {
                CapabilitiesError::OomError(oom_err) => return Err(oom_err),
                CapabilitiesError::SurfaceLost => panic!("Surface lost while creating swapchain")
            }
        };

Needs to modify the error returned when creating a swapchain.


Add more detail to key based verification example

It would be helpful to have more explanation on:

downloading cosign separately from this repo
possibly, how to use the example with some other signed container of choice (including setting up PAT for ghcr or similar)
how to fill out the values for the rekor pub key and fulcio cert and/or set their locations

I would also specify how to get cosign working to be able to run the cosign commands, using the installation docs and that you have to run cosign initialize to populate the certificates referred to in the example.

The -key flag for cosign should also be updated apparently:
WARNING: the -key flag is deprecated and will be removed in a future release. Please use the --key flag instead.


Who is maintaining this gem?

Twitter is gradually migrating its API to v2, but is this gem still maintained?
Is there an alternative gem?

I would like to know this as well.

https://github.com/sferik/twitter/issues/952


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add kubernetes secrets

Examples taken from https://github.com/gitleaks/gitleaks/pull/1462. Could be tweaked to be more varied or realistic.
This fixes #3.
It attempts to implement a structure based on discussions in #4. Let me know your thoughts.

These are looking great!
Could I have you tweak the paths a bit to line up with the final format we landed on?
tool-or-service/validity/single-test-case(\.extension)?

where single test-case can be a folder or file depending on if you need to build out a folder structure for the path based matching to work.
For example:
k8s/invalid/secret-after-insufficient-length.yml

(I'm really excited to finally start getting this repo cleaned up and make it more useful for folks)

Done.


Relying on eval?

https://github.com/ljharb/get-intrinsic/blob/1c8305b5365827c9b6fc785434aac0e1328ff2f5/index.js#L12
Hi, I was just wondering why eval is being used here instead of just hard-coding the values? Is this done in order to avoid, say, throwing uncatchable parser/syntax errors that would otherwise occur in older ECMA environments? If that is the reason, I think it would at least be useful to maybe have another version of this package (whether internal, or external via a separate package) that would always be able to query all intrinsics in any modern environment (say esnext) regardless of whether eval is allowed or not.
I think it would also be nice if there were a way to access all of these intrinsics at once, say in a collection or array, or even a plain object/hash whose keys could be iterated over.
Instead of doing it all from scratch, I've been trying to find a package that would be able to take in any unknown value where:
((typeof value === "object" || typeof value === "function") && value !== null)

and then test it in order to see if it is a is a builtin/intrinsic object (e.g. Math), or builtin/intrinsic Function (e.g. Date). It is this issue that led me here to this package. I suppose most or many of these values simply exist on the global object (in which case one could perhaps simply test against every value in globalThis), but that doesn't seem to be the case for all of them...
Finally, I was just wondering what the benefit is of querying these builtins/intrinsics by their language spec name/syntax? Is it just done that way to have a one-to-one mapping in regards to how they are listed in the spec? I'm honestly just curious to know if there's something additional that I might be missing here, that's all.
Sorry for being a bit of a noob, and thank you beforehand for hearing out my concerns and any information you can provide regarding these questions!

Yes, it's impossible to hardcode the values, because the only non-eval way to get to them is syntax that would break the entire program in older browsers.
What use case do you have for iterating over all intrinsics? Why does it matter if a value is an intrinsic or not, if you don't know which one it is?
It's indeed done that way to have a one-to-one mapping; the purpose of this package is to be used in polyfills/shims which also match the spec.

What use case do you have for iterating over all intrinsics? Why does it matter if a value is an intrinsic or not, if you don't know which one it is?

I'm working on an experimental package (that would be used in development I suppose) that takes an unknown value at runtime and recursively expands and prints out its typescript type/shape, especially for any plain objects or plain arrays it finds while walking them. I think this could be useful in typing random objects say JSON responses from a web server instead of doing the entire thing by hand (perhaps it would cut the time in half, although some manual editing is still gonna be involved). I want to to be somewhat compatible with values such as intrinsics if one is found or come across for any reason (so that way my module won't try to walk Math for instance and will instead simply emit Math for its type). Perhaps there's already some code in the typescript repo that already does something similar, but part of this package is simply learning experience for me as well (maybe it will be my first npm pkg).
Here is what I've currently got that determines if an object is a plain/default object that should be expanded/walked or not:
function isRegularObject(value: unknown) {
    return (
        typeof value === "object" &&
        value !== null && (
        Object.getPrototypeOf(value) === null ||
        value.constructor === {}.constructor
        )
    );
}

and I've got this for plain/default arrays:
function isDefaultArray(value: unknown) {
    return typeof value === "object" &&
        value !== null && Object.getPrototypeOf(value) === Object.getPrototypeOf([]);
}

but the former fn returns true for Math etc. and so will start walking Math which I don't want.

It's indeed done that way to have a one-to-one mapping; the purpose of this package is to be used in polyfills/shims which also match the spec.

Ah I see, thank you for that!

What use case do you have for iterating over all intrinsics? Why does it matter if a value is an intrinsic or not, if you don't know which one it is?

Oh boy I'm sorry, I'm not sure I even answered your question! That's a good question.
Well, if the unknown value matches an intrinsic, then I was figuring that maybe a type could be emitted by doing something like:
`${value.name}Constructor`

or
`typeof ${value.name}`

for functions, and then
`${value.constructor.name}`

for objects, although it is something I am still investigating and I am not sure that is going to work in every case. I also just realized my isRegularObject() fn would think that prototype-less objects are regular objects (and from there type HasNullProto = { key: string } would actually have the Object.prototype as its prototype I believe), which wouldn't be entirely correct.

a) you can never rely on .constructor being present or correct
b) most intrinsics aren't constructors at all
Runtime comparison to intrinsics would happen after type information has already been deleted - at type-time, you can't rely on runtime values.

I understand. It seems like alot of different algorithms in the spec itself do rely on "constructor" being correct however via Get(obj, "constructor"). I'm having a hard time though finding where in the spec it actually details how and when this property is set initially, and I only just now found out that it comes from and exists on an object's prototype.
But basically this module I'm mucking about with is only intended to be used for assistance with manually creating type definition files at design time. It is not intended to be an end all solution either. For example, say you want to emit a type for a parsed JSON server response object of unknown type/shape that comes in response to sending a request to an API endpoint of someone else's website/server. This object typically has the same set of keys (repeated requests return similar or same JSON structure/type) whose values are typically of a certain type. Well one way might be to just JSON.stringify() it then edit the values manually by hand (true becomes boolean, "hello" becomes string, unquote the keys,  etc.) but I'd like a module to do that part for me among other things. I may have widened the scope of what I am trying to accomplish a bit too much in trying to tackle the typing of non-JSON objects/values at runtime however.

At design time you don't have any runtime values tho, so i'm not sure how you could use what you're asking about.
It's a very very hard problem to try to infer and then emit a type for a runtime value, at runtime, and i don't think this library would help much.

I'm sorry I'm probably not explaining it too well. This is what my inspiration was: There's a simple npm pkg here for interacting with the Robinhood API. It has a .d.ts file which defines itself and its methods. The methods simply send a request to Robinhood's servers and then return the response body as a parsed JSON object. I wanted to add types (to their .d.ts) for them for their methods so that anyone who depends on their module can have a fairly good idea what the methods are returning instead of just any (the methods are actually just using the request npm pkg which itself uses callbacks to "return" the server response). Now, I thought something like the module I'm working on might make things slightly easier and faster in accomplishing generating/authoring those types or shapes of the server responses. The manual way to do this, I gather, is to just enter the REPL and console.log the JSON server responses received from calling each relevant method of robinhood npm pkg, then copy/paste/edit that into their .d.ts file. The edit part simply means converting that text to a valid ts type/shape by hand.
My module would enable the same workflow, but more or less automate the edit part if it was required() and used in the REPL as well during this process. It would accept a JSON value (or what I really wanted was any js value lol, so that my module would become more universal in its potential use-cases) and output a string that is the ts type definition that can be copy & pasted into a .d.ts file from there. But I agree that it wouldn't be adding a ton of value and that the whole process is still a manual one. So basically I started working on this module of mine and then thought to myself, how do I make this compatible with other potential situations people might encounter when trying to author ts type definitions (that aren't simply limited to JSON values)? But really all of these use-cases might be quite rare perhaps.
Thank you for the advice and knowledge you've shared with me here however, as well as answering my questions about this repo. I really appreciate it!

I think it has to always be manual - because you can't programmatically know what possible types something will have. You might make 100 requests and get an integer, and make a 101st and get a string. You can only document the types of a thing if you authored it, or if you inspect the code/docs and match them.

I think it has to always be manual - because you can't programmatically know what possible types something will have. You might make 100 requests and get an integer, and make a 101st and get a string. You can only document the types of a thing if you authored it, or if you inspect the code/docs and match them.

I think I get it. So in essence it is more important for a type definition to be guaranteed correct than to exist at all?
For the sake of argument, lets assume that in my example here the thing we're trying to type is guaranteed to be a plain {...} JSON (or JSON-derived) object (not a JSON string, array, etc.), and there's truly no other way to author type definitions for this object. One thing that then make things kinda interesting is the ability to mark properties as optional while including an index signature... in that case such a type becomes almost like a hint, and in such circumstances the question then becomes: is such a type, or its existence, truly semantically incorrect? Or, perhaps it is correct but simply a bad practice? Maybe there's already a golden rule or best practice for this case, trying to author such a type, that I am not aware of. You know what would be cool is a repo dedicated to best practices for js and ts (for noobs and semi-noobs) if there isn't already, with explanations for why each example is a best practice. I know we already have tools like ESLint and friends, but some best practices go beyond mere code (such as in this case) (and I apologize if such a repo already exists, or if I'm stating the blatantly obvious here).
At the end of the day, I understand that this particular pkg robinhood isn't like most, cannot replied upon, and is merely provided for convenience, and so maybe then making the module that I was going to make is a waste of time as it is for a use-case far too rare. Plus, I can see how it could be bad to encourage authoring types in such a manner, and perhaps merely publishing such a pkg could encourage such a thing. I don't know.

Yes, an incorrect type definition is far far worse than none at all.

+1


White line above title bar

Type
Incorrect behavior
Operating System
None
OS Version
Windows 10
Bug description
Randomly occurred about 3-4 weeks ago on startup, hasn't gone away since. It seems the runelite overaly is not matching up with the jagex launchers native top bar?
Screenshots or videos

RuneLite version
Runelite Version: 1.10.22
Launcher Version: 2.6.13
Logs
No response

I got a grey bar at the bottom since one of the updates...

We don't know why this happens, and it doesn't happen to very many people (or to us). If you can figure out any system settings which affects it we would be interested in knowing what it is.

I got a grey bar at the bottom since one of the updates... I can manually fix it by minimizing/maximizing every time though.

This is a separate issue, fixed in https://github.com/runelite/runelite/pull/17529

I was having the same issue on windows 11 i went into runelite properties and had run this program in compatibility mode for windows 8 selected, i turned it off and restarted and the line went away


update doc reference.md with redundant digit and alphanumeric

We got feedback from folks trying to translate our docs, questioning about he use of digit, since the sentence already contains alphanumeric
https://github.com/openwhisk/openwhisk/blob/master/docs/reference.md#entity-names
So it will go from:

The first character must be an alphanumeric character, a digit, or an underscore.
The subsequent characters can be alphanumeric, digits, spaces, or any of the following: _, @, ., -.
The new bullets would look like this:
The first character must be an alphanumeric character, or an underscore.
The subsequent characters can be alphanumeric, spaces, or any of the following: _, @, ., -

I checked the doc, I see no references to digit.


[master] Quick start YAML

Adding Edge Stack quick start YAML file

@khussey sounds good, I could put it in /docs/latest/... if needed instead but was trying to avoid using that super long URL in the new quick start


LeoStick

Should the LeoStick be compatible with this project?

The LeoStick has an ATmega32u4, so yes it should work.


Define basic transliterator interface

Part of #1

High-level directory structure comment. Given that we are going to start with a single repo which will contain both tests, python library and potentially other libraries I was thinking about separating libraries by directories:

tests
python
(potentially) csharp

The tests directory will contain only json files without any python code. To keep it language-agnostic.


⚠ Bofrost.com has degraded performance

In 7b97bef, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 647 ms

Resolved: Bofrost.com performance has improved in 1c39876 after 6 minutes.


Install prereleases to jail

Jail is a super cool feature for testing out new packages in an isolated environment.  I'd really like to be able to install prerelease packages there for testing, is there already a way to do this?  If not, could it be added?

Almost there. Dephell support it, I've just forgot enable --pre key for jail :) We need to add builders.build_resolver(parser) in jail_install.py

Do you want to contribute it as well?


Allow partial reconstruct of historical states

#5749
Documentation

[X] I thought about documentation and added the doc-change-required label to this PR if updates are required.

Changelog

[X] I thought about adding a changelog entry, and added one if I deemed necessary.

Looking good, just a couple of small things.


Support for rendering of mathematical formulas

Better support the rendering of mathematical formulas.

@krschacht I really don't know if this is a good way of doing this... what do you think? One test is already failing which already says a lot. Feels very hacky.

It's a good idea to add support for this! But hmm, that's tricky. The failing tests are simply because of removing html_escape() on the text that comes back. I tried adding it back and the tests pass, but then the math equation is not displayed properly—I just see a bunch of HTML.
The reason I had to add this html_escape was because sometimes the LLM will reply with actual HTML when it's explaining something to you. If this HTML is rendered by the browser rather than being escaped and displayed to the user, sometimes the text doesn't make sense. For example, you might ask "how do I make a table in HTML" and the LLM is trying to show you the HTML but the browser is rendering the HTML instead of displaying it. In addition, the LLM could return HTML that would cause the overall page layout to break. Somehow we'll have to differentiate between math and other html that the LLM may return.
Also, it's not impossible to use a JS library to do final rendering on the front-end, but I've been trying to avoid it. Parts of the page refresh a lot during streaming and I ran into some odd issues with render cycles. This is what led me to do serverside converting from markdown into HTML, using Redcarpet.
The easiest would be if Redcarpet supported some markup for math. I'm not very familiar with the options for math markup, but I did a little bit of digging and it seems like Redcarpet does not. However, in their forums they recommended a different ruby markdown parser: Kramdown. Maybe the best route to go would be to switch from Redcarpet to Kramdown and then lean into their support for math? e.g. https://kramdown.gettalong.org/documentation.html

Dear @ceicke,
I'm trying to your PR, but it's only display math after refresh page, New message isn't display with MathJax. I try using other event as turbo:load but it also only display for previous message, latest message isn't display while F5 too.

Dear @ceicke,
I found latest message alway update by Connection.rb inside ApplicationCable
module ApplicationCable
  class Connection < ActionCable::Connection::Base
    def connect
      ActiveSupport::Notifications.subscribe "transmit_subscription_confirmation.action_cable" do |*args|
        # Sometimes the conversation page loads and it doesn't get the message to appear, even though
        # the logs show it was broadcasted. This is because there is a small race condition where right
        # in between when find() of the message and the client establishing the turbo stream connection,
        # the broadcast happens.
        #
        # The fix is to re-broadcast the last message to the client after the connection is established.
        #
        # FIXME: See if there is any conclusion on this Rails Issue: https://github.com/rails/rails/issues/52420
        event = ActiveSupport::Notifications::Event.new(*args)

        if event.payload[:channel_class] == "Turbo::StreamsChannel"
          identifier = JSON.parse(event.payload[:identifier])
          signed_stream_name = identifier["signed_stream_name"]
          stream_name = Base64.urlsafe_decode64(Turbo.signed_stream_verifier.verify(signed_stream_name))
          class_name, id = stream_name.split("/").last(2)
          conversation = class_name.classify.constantize.find(id)
          message = conversation.latest_message_for_version

          GetNextAIMessageJob.broadcast_updated_message(message)
        end
      end
    end
  end
end

I disabled this code, everything is OK.
@krschacht could you tell me how to call javascript after load final message? Here is code inside application.
document.addEventListener('turbo:load', (event) => {
  console.log('Document: load', event.detail.url)

  if (typeof MathJax !== 'undefined') {
    MathJax.typeset();
  }
})

Now, I'm hacky by
document.addEventListener('turbo:before-stream-render', (event) => {
  console.log(`Document: stream render (${event.target.getAttribute('action')} event)`, event.target)
  setTimeout(() => {
    console.log('Document: stream render done')
    if (typeof MathJax !== 'undefined') {
      MathJax.typeset();
    }
  }, 1000)
})

I think it's not good, but now I can't find other solution. if you have, please let me know


Live Share activating all extensions with an onTaskType

Since very recently, Live Share has started to activate random extensions when starting a session. This is very annoying as you get random extensions complaining about the current folder not using the language they're for and such.

Hi @nomyTx - can you provide more details such as: OS, Live Share extension version, what are the other extensions that are activating? Also, are you able to reproduce the issue consistently? If so, please share the steps to reproduce.

OS: Windows
Live Share version: v1.0.5834
To reproduce just start a session while having extensions like the Go extension and the Rust Analyzer extension. They will all start.

Any updates on this?

@nomyTx: thanks for filing this issue and including the repro steps! We were able to repro. It occurs due to Live Share calling: vscode.tasks.fetchTasks().
When this is called it activates all extensions that use onTaskType activation events. Another user filed a VS code issue on this:  https://github.com/microsoft/vscode/issues/152844
We've scoped down our usage of this API to only fetchTasks() when searching for tasks that can be run from Live Share. We no longer call this on Share or Join unless the host has the Allow Guest Task Control setting enabled. Note: this setting isn't enabled by default
This fix will be included in our next Live Share release. Stay tuned! We'll let you know when it is available in the marketplace.

Thank you for the fix, I will be waiting for it to be released

@nomyTx: the Live Share release (1.0.5857) with this fix is now in the VS Marketplace.


(PUP-4903) Add applications to node catalog and add an environment compiler

These patches do three things:

recognize applications as a new kind of known resource type
make sure that components mapped to a node wind up in that node's catalog
add an environment compiler

Rebased on top of latest (PUP-5045) branch, nothing else changed

Added a new test spec/unit/appmgmt_spec.rb and added some tests around applications to spec/unit/resource/type_collection_spec.rb

Rebased on top of latest (PUP-5045) PR

Rebased on top of latest (PUP-5045) PR

Made the changes and repushed


fix dev dependency: prettier#master => prettier#main

Prettier have update their report from master branch to main

btw do we still need to use git dependency? I bet they released a new version since that change

btw do we still need to use git dependency? I bet they released a new version since that change


Scale points to wrong TaskIt version

Scales wrongly points to taskit dev-0.2.1. That version did exist but there was no BaselineOfTaskItShell in there. The baseline exists in dev-0.3.

A new release of taskit was done for this purpose:
https://github.com/sbragagnolo/taskit/releases/tag/v0.3


[Snyk] Security upgrade alpine from 3.14.0 to 3.19

Snyk has created this PR to fix 4 vulnerabilities in the dockerfile dependencies of this project.
Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Snyk changed the following file(s):

Dockerfile

We recommend upgrading to alpine:3.19, as this image has only 0 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Out-of-bounds Read SNYK-ALPINE314-APKTOOLS-1533752
  714

Buffer Overflow SNYK-ALPINE314-OPENSSL-1569445
  714

Buffer Overflow SNYK-ALPINE314-OPENSSL-1569445
  714

Out-of-bounds Write SNYK-ALPINE314-ZLIB-2976174
  714

Use After Free SNYK-ALPINE314-OPENSSL-3314637
  614

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Use After Free

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Allow @prop and @property without type

This PR is related to #186. I found out it was easy to make doctrine support this use case so I went ahead and made the changes.

Hi @tmcw and @tibdex , it would be great to have this MR in....is there anything I can do to help out? @tmcw 's comment seems to make sense, I can submit a separate PR with those changes if that would help.

Hey @tmcw, I pushed a new commit refactoring the code as you suggested.
I can rebase on top of Doctrine's master branch, squash, and fix the commit message if you want to.

I'm closing this because there hasn't been any activity on it for a long time.
I checked the "allow edits from maintainers" box so feel free to reopen and merge if you want to.


specify tsconfig.json path

Is it possible to specify the path of tsconfig.json if tsconfig.json is not in the root of the project?

Duplicate of #12463
We detect tsconfig.json files in subdirectories as well (but they have to be named tsconfig.json)


Netlify ignore script is not working

Netlify ignore script assumes that nx exists at that point in the build step. It does not so it throws an error and all apps are build on every PR, we should fix this or look into building a plugin that will work for our apps

Closing as @bglownia, @edd and I looked at this and we believe we have a usable netlify config for now


Add topLevelCommentId field to comments.

This allows childComments to know what the top most parent comment is by adding a topLevelCommentId to each childComment.

Awesome, thanks!

Great - thanks SachaG. You're fast! :)

Taking another look at this, I don't think we can keep that migration. There's three nested forEach loops in there, and I'm not sure if that's a good idea for sites like Crater that already have a lot of comments…
Maybe we just need to leave current data alone and assume the topLevelCommentId property might not always exist?

Yeah, I mean, if people don't need this for old comments threads, then it shouldn't be a big deal to not have a migration. I was't sure how to do the migration any simpler.

Yeah I don't know how you could do it simpler either. It's more about doing it with https://github.com/percolatestudio/meteor-migrations or some similar system that can account for how long it'll take. Telescope's current migrations system is pretty bare-bones, so it can mess up with the deploy process.


 I feel this is rather clear.

 Since then I've found out that virtualenv now also provides a fish activation script, and I've settled for a different solution, so I don't care anymore.
Here is it in case anyone else is interested:
	#~/.config/fish/config.fish

    # python virtualenv auto load when changing directory.
    # to create a new virtualenv inside the project directory use: virtualenv .virtualenv
    function auto_virtualenv --on-variable PWD
        if test -d ".venv"
            if not set -q VIRTUAL_ENV
                set --export --global venv_root $PWD
                source .venv/bin/activate.fish
            end
        else
            if set -q VIRTUAL_ENV
                if set -q venv_root
                    if not string match --entire --quiet $venv_root $PWD
                        set --erase venv_root
                        deactivate
                    end
                end
            end
        end
    end

    # in case the shell is started in a directory which contains a virtualenv
    auto_virtualenv

I thought this repo was stupid because I was red pilled by @kennethreitz
Though, after some heavier investigation I realised that this was in fact a great repo. Thanks for including your script I will be sure to use it my dear friend. @franciscolourenco may I ask what you think of this repo? If it is not too personal a question.

@izaakf I dismissed this plugin as a viable choice once I found two unresolved issues previously closed due to inactivity:

https://github.com/sentriz/fish-pipenv/issues/20#issuecomment-463627715
https://github.com/sentriz/fish-pipenv/issues/19#issuecomment-463627616

Regarding Pipenv in general, I gave it a try as well as I did with Poetry. It seems that the community hasn't settled for wither, both projects still seem to have some rough edges, and I didn't need any package management functionality for the time being, so I stuck with vanilla virtualenv once I found out it supported fish now.

I understand your dismissal of this plugin due to those open issues. It is a shame they were never resolved and closed due to staleness. If I had the cycles I most certainly would've sought to resolve them myself. If I find the cycles to work on those tasks do you think you would return to use this project @franciscolourenco?

I see, I'm still an avid user of Poetry myself. Despite the lack of community there is still something magical, and whimsical about it. I have been trying to advocate for use of Poetry within crypto and NFT communities as I think they could be easily persuaded to use such a technology. It has been with little success thus far but I feel that with upcoming global events that those in the crypto could still be encouraged to use Poetry.


Board Review: Azure Communication Services (SPOOL) Mobile UI Chat Composite  [iOS & Android] [Public Preview]

Team: Mobile UI team
Contoso developers can use the chat composite to allow their users to create chat thread, send, and receive messages all these capabilities under the mobile platforms (Android & iOS)
iOS: https://apiview.dev/Assemblies/Review/94effc0dc5834079836603972a352a27
Android: https://apiview.dev/Assemblies/Review/33a75b55f6434f99a5e8f42cb65c1a39

Scheduled for Dec 15th from 2:05PM - 4PM PST.


UI Improvements Contributor Profiles and Listing

This is a collection of multiple minor UI issues.
The contributor profiles UI has evolved in a somewhat unstructured way. The currently UI has some problems and potential for improvements:
1) Master data vs. communication channel preferences
It’s unclear which fields are merely a way to store additional information about a contributor vs. which fields are used to send messages to contributors. For example, an editor reported they wanted to simply store an email address in a contributor’s profile as additional information. They did not expect that this would cause the contributor to receive all messages via email.
We should probably separate the fields that store communication channel information and those that store master data that isn’t used for anything else. We should also add help texts where appropriate to set clear expectations.
2) Filter contributor listing by active/inactive contributors
Currently, the listings page for contributors lists all contributors, wether they are active or inactive. This is confusing, as the listings don’t indicate which contributors are active/inactive (i.e. you have to visit the contributor profile to see the status). Also, the total number of contributors includes inactive contributors, which might give you a false impression of the community size.

https://github.com/tactilenews/100eyes/pull/464#issuecomment-719975476
3) Use more subtle styles for tag pills
Tag pills currently have solid, very colorful backgrounds. This can make the contributor listings a little overwhelming/hard to scan. Also, foreground/background contrasts are bad for some colors. We could style tags a little less prominent, while keeping colored tags, something in this direction:

Please just show the active communication-channel field (only "Threema" or "Telegram")!
good solution ( Probably we can show a "User remaining on your plan) )
Tag color should be consistent, so "Entwickler" is always green.


Legend: improve support for labels with line breaks

Issue: If you make a chart with a line break in the label, the legend renders it as an unknown character
ScottPlot Version:  5.0.25
ScottPlot.Plot myPlot = new();

List<PieSlice> slices = new()
{
	new PieSlice() { Value = 5, FillColor = Colors.Red, Label = "Red has long\ntitle here" },
	new PieSlice() { Value = 2, FillColor = Colors.Orange, Label = "Orange" },
	new PieSlice() { Value = 8, FillColor = Colors.Gold, Label = "Yellow" },
	new PieSlice() { Value = 4, FillColor = Colors.Green, Label = "Green" },
	new PieSlice() { Value = 8, FillColor = Colors.Blue, Label = "Blue" },
};

var pie = myPlot.Add.Pie(slices);
pie.ExplodeFraction = .1;

myPlot.ShowLegend();

myPlot.SavePng("demo.png", 400, 300);

I looked into it, and oof, the legend items are manually rendered text and don't leverage the Label class with all its new string measurement features and multiline support. I'll start working on this now and wow, it'll be a big PR! 😅

Interestingly, I found a flag which indicates this may have been hacked-in before.
I'm not going to even test if it works since it's getting refactored away, but it's there 🤷
formsPlot1.Plot.Legend.AllowMultiline = true;

I gave it a shot, it doesn't work.

Merging #3689 now 🚀 It's one of the biggest PRs I've worked on in a while 😅


Commentlines endpoint build

Sprint 3 push:

Added number-of-comment-lines endpoint with the comment.py file

Sprint 3 merge

Added number-of-comment-lines endpoint


Change metadata.name in catalog-info.yaml to match accelerator name

The name in the catalog-info.yaml file should match the accelerator name so someone using the defaults to generate a project could use this file to register the component with the Backstage catalog.
metadata:
  name: sample-app

This applies to weatherforecast-csharp and weatherforecast-steeltoe samples.

Will also require associated updates to accelerator.yaml

There is no need to update weatherforecast-csharp and weatherforecast-steeltoe cause this dummy name (sampl-app) will always be replaced during an accelerator execution.
But there are 2 other accelerators where there is no name replacement at all: appsso-starter-java and spring-smtp-gateway. We'll update these 2 in the scope of this task.


[SPARK-44788][PYTHON][DOCS][FOLLOW-UP] Add from_xml and schema_of_xml into PySpark documentation

What changes were proposed in this pull request?
This PR adds from_xml and schema_of_xml into PySpark documentation
Why are the changes needed?
For users to know how to use them.
Does this PR introduce any user-facing change?
Yes, It adds both from_xml and schema_of_xml into Python documentation
How was this patch tested?
Manually tested.
Was this patch authored or co-authored using generative AI tooling?
No.

LGTM

@HyukjinKwon I just found that there was a Xml Functions group

Oops thanks for doing this.


Unexpected long cue export time (~4 sec)

What version of CUE are you using (cue version)?

$ cue version

cue version v0.0.0-20230628071453-b6a32da097fc

go version go1.20.6
      -buildmode exe
       -compiler gc
     CGO_ENABLED 1
          GOARCH amd64
            GOOS linux
         GOAMD64 v1
             vcs git
    vcs.revision b6a32da097fce5f9c960ad0a02da51efb18de2fd
        vcs.time 2023-06-28T07:14:53Z
    vcs.modified false

Does this issue reproduce with the latest stable release?
Yes. Also checked on:

v0.5.0
https://github.com/cue-lang/cue/commit/db28ec6e85290adbb04e5115bd13923fde6a7446 (current master)
https://github.com/cue-lang/cue/commit/f681271a38ec9e13d3a4c7ed2641267f0aabaa75 https://cuelang.org/play/
https://github.com/cue-lang/cue/pull/2503 (looks like this is not duplicate of #2500 issue)

What did you do?
cue export for single file:
package issue

#Cloud: {
	availability_zones: [...string]
}

#Cluster: {
	cloud:              #Cloud
	availability_zones: [...string] | *cloud.availability_zones
}

#sampleCloud: #Cloud & {
	availability_zones: [...string] | *["1a", "1b", "1c", "2a", "2b", "2c"]
}

#Context: {
	cluster: #Cluster
}

#AppContext: #Context & {
	cluster: #Cluster & {
		cloud: #sampleCloud
	}
}

#Config: {
	#context: #Context

	name:    string
	context: #context
}

#AppConfig: #Config & {
	#context: #AppContext
	name:     "foo"
}

#ViewName: {
	#domain: #Config
	name:    #domain.name
}

#View2: {
	#domain: #Config

	let domain = #domain
	view2_a: #ViewName & {
		#domain: domain
	}
	view2_b: #ViewName & {
		#domain: domain
	}
}

#View1: {
	#domain: #Config

	let domain = #domain
	view1_a: #View2 & {
		#domain: domain
	}
	view1_b: #View2 & {
		#domain: domain
	}
}

#View: {
	#domain: #Config

	let domain = #domain
	view_a: #View1 & {
		#domain: domain
	}
	view_b: #View1 & {
		#domain: domain
	}
}

#View & {
	#domain: #AppConfig
}

What did you expect to see?
I expect milliseconds export time and result like:
{
    "view_a": {
        "view1_a": {
            "view2_a": {
                "name": "foo"
            },
            "view2_b": {
                "name": "foo"
            }
        },
        "view1_b": {
            "view2_a": {
                "name": "foo"
            },
            "view2_b": {
                "name": "foo"
            }
        }
    },
    "view_b": {
        "view1_a": {
            "view2_a": {
                "name": "foo"
            },
            "view2_b": {
                "name": "foo"
            }
        },
        "view1_b": {
            "view2_a": {
                "name": "foo"
            },
            "view2_b": {
                "name": "foo"
            }
        }
    }
}

What did you see instead?
time CUE_STATS_FILE=- cue export .
{
    "view_a": {
        "view1_a": {
            "view2_a": {
                "name": "foo"
            },
            "view2_b": {
                "name": "foo"
            }
        },
        "view1_b": {
            "view2_a": {
                "name": "foo"
            },
            "view2_b": {
                "name": "foo"
            }
        }
    },
    "view_b": {
        "view1_a": {
            "view2_a": {
                "name": "foo"
            },
            "view2_b": {
                "name": "foo"
            }
        },
        "view1_b": {
            "view2_a": {
                "name": "foo"
            },
            "view2_b": {
                "name": "foo"
            }
        }
    }
}
{
    "CUE": {
        "Unifications": 136090,
        "Disjuncts": 166346,
        "Conjuncts": 12253269,
        "Freed": 166338,
        "Reused": 166311,
        "Allocs": 27,
        "Retained": 8
    },
    "Go": {
        "AllocBytes":<PHONE_NUMBER>,
        "AllocObjects": 22867934
    }
}
CUE_STATS_FILE=- cue export ./issue  8,69s user 0,12s system 197% cpu 4,470 total

Since you opened a new issue to do your research in https://github.com/cue-lang/cue/pull/2503, I'll link to my response at https://github.com/cue-lang/cue/issues/2500#issuecomment-1646616946, which feels applicable here as well :)

In this case, it seems that the problem is solved by closing the list like:
 #sampleCloud: #Cloud & {
-	availability_zones: [...string] | *["1a", "1b", "1c", "2a", "2b", "2c"]
+ 	availability_zones: [...string] | *close(["1a", "1b", "1c", "2a", "2b", "2c"])
 }

I could not check whether the new evaluator fixed this performance issue as it is currently failing on this input; I've filed https://github.com/cue-lang/cue/issues/3641 to track this as it clearly appears like a bug.


Cannot install vega plugin package

Hi,
I have installed backstage. When I followed your doc to install vega plugin, I was in the backstage directory and executed the first bash: yarn workspace app add @avaliasystems/backstage-plugin-vega. It showed this error:
[root@localhost appbackstage]# yarn workspace app add @avaliasystems/backstage-plugin-vega --verbose
yarn workspace v1.22.19
yarn add v1.22.19
verbose 0.189855464 Checking for configuration file "/root/appbackstage/packages/app/.npmrc".
verbose 0.190173132 Checking for configuration file "/usr/local/share/.npmrc".
verbose 0.190702654 Checking for configuration file "/root/.nvm/versions/node/v16.18.1/etc/npmrc".
verbose 0.190908152 Checking for configuration file "/root/.npmrc".
verbose 0.191548648 Checking for configuration file "/root/appbackstage/packages/app/.npmrc".
verbose 0.191933195 Checking for configuration file "/root/appbackstage/packages/.npmrc".
verbose 0.192399486 Checking for configuration file "/root/appbackstage/.npmrc".
verbose 0.192672514 Found configuration file "/root/appbackstage/.npmrc".
verbose 0.193194066 Checking for configuration file "/root/.npmrc".
verbose 0.194587177 Checking for configuration file "/root/appbackstage/packages/app/.yarnrc".
verbose 0.194774353 Checking for configuration file "/usr/local/share/.yarnrc".
verbose 0.195022049 Found configuration file "/usr/local/share/.yarnrc".
verbose 0.195528463 Checking for configuration file "/root/.nvm/versions/node/v16.18.1/etc/yarnrc".
verbose 0.195779353 Checking for configuration file "/root/.yarnrc".
verbose 0.19589324 Checking for configuration file "/root/appbackstage/packages/app/.yarnrc".
verbose 0.196009231 Checking for configuration file "/root/appbackstage/packages/.yarnrc".
verbose 0.196228655 Checking for configuration file "/root/appbackstage/.yarnrc".
verbose 0.196330333 Checking for configuration file "/root/.yarnrc".
verbose 0.207661667 current time: 2022-12-15T09:32:13.063Z
[1/4] Resolving packages...
verbose 0.341706931 Performing "GET" request to "https://registry.npmjs.org/backstage-plugin-vega".
verbose 1.303352429 Request "https://registry.npmjs.org/backstage-plugin-vega" finished with status code 404.
verbose 1.312872626 Error: Couldn't find package<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>on the "npm" registry.
    at MessageError.ExtendableBuiltin (/root/.nvm/versions/node/v16.18.1/lib/node_modules/yarn/lib/cli.js:721:66)
    at new MessageError (/root/.nvm/versions/node/v16.18.1/lib/node_modules/yarn/lib/cli.js:750:123)
    at PackageRequest.<anonymous> (/root/.nvm/versions/node/v16.18.1/lib/node_modules/yarn/lib/cli.js:36590:17)
    at Generator.throw (<anonymous>)
    at step (/root/.nvm/versions/node/v16.18.1/lib/node_modules/yarn/lib/cli.js:310:30)
    at /root/.nvm/versions/node/v16.18.1/lib/node_modules/yarn/lib/cli.js:323:13
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
error Couldn't find package<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>on the "npm" registry.
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

I believe that it cannot find the plugin on the https://registry.npmjs.org. Any help on fixing this issues?
Thx in advanced!

Hi @liemmtnet,
Strange, I just checked and I don't see the problem on my side. Here is the URL of the package: ..
What is weird in your log is that the @avaliasystems prefix is missing in the GET request.

Is it working now?

its still not working,
im having a problem in step 3.
I can't specify the absolute path where I add , import its
can you show me the absolute path where i add import like the guide below

Thx in advanced !

This repo contains a Backstage app, which you can run. In the Home Page, we have included a widget. This way, you have an example that you should be able to use.
Hava a look. Please have a look at this source file
Here is the import section:
import { VegaWidget, VegaLibrary } from '@avaliasystems/backstage-plugin-vega';


Python 3 support

Any timeline for this?

We're not actively working on it as we don't use py3 but we'd gladly accept patches. Shouldn't be too hard as pymongo is already OK.

Wow! Thanks to @Liwink and @monnierj for the Pull Requests! Impressed to have 2 of them in just a couple days :-)
One seems to be using six, the other not. Let's discuss here which approach is the best for the project?

Fixed by #18 :-)