227 |             *result = CNaN;
      |     ^
parser.rl:229:1: note: here
  229 |             rb_enc_raise(EXC_ENCODING eParserError, "%u: unexpected token at '%s'", __LINE__, p - 2);
      | ^
parser.c:630:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  630 |  if ( ++p == pe )
      |     ^
parser.c:632:1: note: here
  632 | case 2:
      | ^~~~
parser.c:637:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  637 |  if ( ++p == pe )
      |     ^
parser.c:639:1: note: here
  639 | case 3:
      | ^~~~
parser.c:644:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  644 |  if ( ++p == pe )
      |     ^
parser.c:646:1: note: here
  646 | case 4:
      | ^~~~
parser.c:651:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  651 |  if ( ++p == pe )
      |     ^
parser.c:653:1: note: here
  653 | case 5:
      | ^~~~
parser.c:658:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  658 |  if ( ++p == pe )
      |     ^
parser.c:660:1: note: here
  660 | case 6:
      | ^~~~
parser.c:665:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  665 |  if ( ++p == pe )
      |     ^
parser.c:667:1: note: here
  667 | case 7:
      | ^~~~
parser.c:672:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  672 |  if ( ++p == pe )
      |     ^
parser.c:674:1: note: here
  674 | case 8:
      | ^~~~
parser.c:679:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  679 |  if ( ++p == pe )
      |     ^
parser.c:681:1: note: here
  681 | case 9:
      | ^~~~
parser.c:686:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  686 |  if ( ++p == pe )
      |     ^
parser.c:688:1: note: here
  688 | case 10:
      | ^~~~
parser.c:693:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  693 |  if ( ++p == pe )
      |     ^
parser.c:695:1: note: here
  695 | case 11:
      | ^~~~
parser.c:700:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  700 |  if ( ++p == pe )
      |     ^
parser.c:702:1: note: here
  702 | case 12:
      | ^~~~
parser.c:707:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  707 |  if ( ++p == pe )
      |     ^
parser.c:709:1: note: here
  709 | case 13:
      | ^~~~
parser.c:714:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  714 |  if ( ++p == pe )
      |     ^
parser.c:716:1: note: here
  716 | case 14:
      | ^~~~
parser.c:721:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  721 |  if ( ++p == pe )
      |     ^
parser.c:723:1: note: here
  723 | case 15:
      | ^~~~
parser.c:728:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  728 |  if ( ++p == pe )
      |     ^
parser.c:730:1: note: here
  730 | case 16:
      | ^~~~
parser.c:735:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  735 |  if ( ++p == pe )
      |     ^
parser.c:737:1: note: here
  737 | case 17:
      | ^~~~
parser.c:742:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  742 |  if ( ++p == pe )
      |     ^
parser.c:744:1: note: here
  744 | case 18:
      | ^~~~
parser.c:749:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  749 |  if ( ++p == pe )
      |     ^
parser.c:751:1: note: here
  751 | case 19:
      | ^~~~
parser.c:756:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  756 |  if ( ++p == pe )
      |     ^
parser.c:758:1: note: here
  758 | case 20:
      | ^~~~
parser.c: In function ‘JSON_parse_string’:
parser.c:1447:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1447 |  if ( ++p == pe )
      |     ^
parser.c:1449:1: note: here
 1449 | case 2:
      | ^~~~
parser.c:1479:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1479 |  if ( ++p == pe )
      |     ^
parser.c:1481:1: note: here
 1481 | case 3:
      | ^~~~
parser.c:1488:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1488 |  if ( ++p == pe )
      |     ^
parser.c:1490:1: note: here
 1490 | case 4:
      | ^~~~
parser.c:1501:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1501 |  if ( ++p == pe )
      |     ^
parser.c:1503:1: note: here
 1503 | case 5:
      | ^~~~
parser.c:1514:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1514 |  if ( ++p == pe )
      |     ^
parser.c:1516:1: note: here
 1516 | case 6:
      | ^~~~
parser.c:1527:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1527 |  if ( ++p == pe )
      |     ^
parser.c:1529:1: note: here
 1529 | case 7:
      | ^~~~
parser.c: In function ‘JSON_parse_array’:
parser.c:1106:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1106 |  if ( ++p == pe )
      |     ^
parser.c:1108:1: note: here
 1108 | case 2:
      | ^~~~
parser.rl:394:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  394 |
      |     ^
parser.rl:396:1: note: here
  396 |
      | ^
parser.c:1163:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1163 |  if ( ++p == pe )
      |     ^
parser.c:1165:1: note: here
 1165 | case 4:
      | ^~~~
parser.c:1187:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1187 |  if ( ++p == pe )
      |     ^
parser.c:1189:1: note: here
 1189 | case 5:
      | ^~~~
parser.c:1196:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1196 |  if ( ++p == pe )
      |     ^
parser.c:1198:1: note: here
 1198 | case 6:
      | ^~~~
parser.c:1203:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1203 |  if ( ++p == pe )
      |     ^
parser.c:1205:1: note: here
 1205 | case 7:
      | ^~~~
parser.c:1212:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1212 |  if ( ++p == pe )
      |     ^
parser.c:1214:1: note: here
 1214 | case 8:
      | ^~~~
parser.c:1219:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1219 |  if ( ++p == pe )
      |     ^
parser.c:1221:1: note: here
 1221 | case 9:
      | ^~~~
parser.c:1228:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1228 |  if ( ++p == pe )
      |     ^
parser.c:1230:1: note: here
 1230 | case 10:
      | ^~~~
parser.c:1235:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1235 |  if ( ++p == pe )
      |     ^
parser.c:1237:1: note: here
 1237 | case 11:
      | ^~~~
parser.c:1244:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1244 |  if ( ++p == pe )
      |     ^
parser.c:1246:1: note: here
 1246 | case 12:
      | ^~~~
parser.c:1261:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1261 |  if ( ++p == pe )
      |     ^
parser.c:1263:1: note: here
 1263 | case 13:
      | ^~~~
parser.c:1270:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1270 |  if ( ++p == pe )
      |     ^
parser.c:1272:1: note: here
 1272 | case 14:
      | ^~~~
parser.c:1277:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1277 |  if ( ++p == pe )
      |     ^
parser.c:1279:1: note: here
 1279 | case 15:
      | ^~~~
parser.c:1286:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1286 |  if ( ++p == pe )
      |     ^
parser.c:1288:1: note: here
 1288 | case 16:
      | ^~~~
parser.c: In function ‘JSON_parse_object’:
parser.c:156:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  156 |  if ( ++p == pe )
      |     ^
parser.c:158:1: note: here
  158 | case 2:
      | ^~~~
parser.rl:162:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  162 |
      |     ^
parser.rl:164:1: note: here
  164 |     next_pair   = ignore* value_separator pair;
      | ^
parser.c:194:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  194 |  if ( ++p == pe )
      |     ^
parser.c:196:1: note: here
  196 | case 4:
      | ^~~~
parser.c:203:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  203 |  if ( ++p == pe )
      |     ^
parser.c:205:1: note: here
  205 | case 5:
      | ^~~~
parser.c:210:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  210 |  if ( ++p == pe )
      |     ^
parser.c:212:1: note: here
  212 | case 6:
      | ^~~~
parser.c:219:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  219 |  if ( ++p == pe )
      |     ^
parser.c:221:1: note: here
  221 | case 7:
      | ^~~~
parser.c:226:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  226 |  if ( ++p == pe )
      |     ^
parser.c:228:1: note: here
  228 | case 8:
      | ^~~~
parser.rl:154:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  154 |         char *np;
      |     ^
parser.rl:156:1: note: here
  156 |         np = JSON_parse_string(json, fpc, pe, &last_name);
      | ^
parser.c:282:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  282 |  if ( ++p == pe )
      |     ^
parser.c:284:1: note: here
  284 | case 10:
      | ^~~~
parser.c:295:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  295 |  if ( ++p == pe )
      |     ^
parser.c:297:1: note: here
  297 | case 11:
      | ^~~~
parser.c:304:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  304 |  if ( ++p == pe )
      |     ^
parser.c:306:1: note: here
  306 | case 12:
      | ^~~~
parser.c:311:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  311 |  if ( ++p == pe )
      |     ^
parser.c:313:1: note: here
  313 | case 13:
      | ^~~~
parser.c:320:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  320 |  if ( ++p == pe )
      |     ^
parser.c:322:1: note: here
  322 | case 14:
      | ^~~~
parser.c:327:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  327 |  if ( ++p == pe )
      |     ^
parser.c:329:1: note: here
  329 | case 15:
      | ^~~~
parser.c:336:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  336 |  if ( ++p == pe )
      |     ^
parser.c:338:1: note: here
  338 | case 16:
      | ^~~~
parser.c:343:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  343 |  if ( ++p == pe )
      |     ^
parser.c:345:1: note: here
  345 | case 17:
      | ^~~~
parser.c:352:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  352 |  if ( ++p == pe )
      |     ^
parser.c:354:1: note: here
  354 | case 18:
      | ^~~~
parser.c:369:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  369 |  if ( ++p == pe )
      |     ^
parser.c:371:1: note: here
  371 | case 19:
      | ^~~~
parser.c:378:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  378 |  if ( ++p == pe )
      |     ^
parser.c:380:1: note: here
  380 | case 20:
      | ^~~~
parser.c:385:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  385 |  if ( ++p == pe )
      |     ^
parser.c:387:1: note: here
  387 | case 21:
      | ^~~~
parser.c:394:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  394 |  if ( ++p == pe )
      |     ^
parser.c:396:1: note: here
  396 | case 22:
      | ^~~~
parser.c:401:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  401 |  if ( ++p == pe )
      |     ^
parser.c:403:1: note: here
  403 | case 23:
      | ^~~~
parser.c:410:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  410 |  if ( ++p == pe )
      |     ^
parser.c:412:1: note: here
  412 | case 24:
      | ^~~~
parser.c:417:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  417 |  if ( ++p == pe )
      |     ^
parser.c:419:1: note: here
  419 | case 25:
      | ^~~~
parser.c:426:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  426 |  if ( ++p == pe )
      |     ^
parser.c:428:1: note: here
  428 | case 26:
      | ^~~~
parser.c: In function ‘JSON_parse_float’:
parser.c:939:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  939 |  if ( ++p == pe )
      |     ^
parser.c:941:1: note: here
  941 | case 2:
      | ^~~~
parser.c:948:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  948 |  if ( ++p == pe )
      |     ^
parser.c:950:1: note: here
  950 | case 3:
      | ^~~~
parser.c:958:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  958 |  if ( ++p == pe )
      |     ^
parser.c:960:1: note: here
  960 | case 4:
      | ^~~~
parser.c:965:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  965 |  if ( ++p == pe )
      |     ^
parser.c:967:1: note: here
  967 | case 8:
      | ^~~~
parser.c:989:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  989 |  if ( ++p == pe )
      |     ^
parser.c:991:1: note: here
  991 | case 5:
      | ^~~~
parser.c:1000:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1000 |  if ( ++p == pe )
      |     ^
parser.c:1002:1: note: here
 1002 | case 6:
      | ^~~~
parser.c:1007:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1007 |  if ( ++p == pe )
      |     ^
parser.c:1009:1: note: here
 1009 | case 10:
      | ^~~~
parser.c:1021:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1021 |  if ( ++p == pe )
      |     ^
parser.c:1023:1: note: here
 1023 | case 7:
      | ^~~~
parser.c: In function ‘JSON_parse_integer’:
parser.c:840:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  840 |  if ( ++p == pe )
      |     ^
parser.c:842:1: note: here
  842 | case 2:
      | ^~~~
parser.c:849:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  849 |  if ( ++p == pe )
      |     ^
parser.c:851:1: note: here
  851 | case 3:
      | ^~~~
parser.c:866:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  866 |  if ( ++p == pe )
      |     ^
parser.c:868:1: note: here
  868 | case 5:
      | ^~~~
parser.c: In function ‘cParser_parse_strict’:
parser.c:1786:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1786 |  if ( ++p == pe )
      |     ^
parser.c:1788:1: note: here
 1788 | case 1:
      | ^~~~
parser.c:1803:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1803 |  if ( ++p == pe )
      |     ^
parser.c:1805:1: note: here
 1805 | case 2:
      | ^~~~
parser.c:1812:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1812 |  if ( ++p == pe )
      |     ^
parser.c:1814:1: note: here
 1814 | case 3:
      | ^~~~
parser.c:1819:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1819 |  if ( ++p == pe )
      |     ^
parser.c:1821:1: note: here
 1821 | case 4:
      | ^~~~
parser.c:1828:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1828 |  if ( ++p == pe )
      |     ^
parser.c:1830:1: note: here
 1830 | case 5:
      | ^~~~
parser.rl:749:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  749 |         char *np;
      |     ^
parser.rl:751:1: note: here
  751 |         np = JSON_parse_array(json, fpc, pe, &result);
      | ^
parser.c:1866:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1866 |  if ( ++p == pe )
      |     ^
parser.c:1868:1: note: here
 1868 | case 6:
      | ^~~~
parser.c:1875:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1875 |  if ( ++p == pe )
      |     ^
parser.c:1877:1: note: here
 1877 | case 7:
      | ^~~~
parser.c:1882:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1882 |  if ( ++p == pe )
      |     ^
parser.c:1884:1: note: here
 1884 | case 8:
      | ^~~~
parser.c:1891:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1891 |  if ( ++p == pe )
      |     ^
parser.c:1893:1: note: here
 1893 | case 9:
      | ^~~~
linking shared-object json/ext/generator.so
make[2]: Leaving directory '/tmp/ruby-build.20200518193720.118097.NYVlMg/ruby-2.2.10/ext/json/generator'
make[2]: Entering directory '/tmp/ruby-build.20200518193720.118097.NYVlMg/ruby-2.2.10'
make[2]: warning: -j4 forced in submake: resetting jobserver mode.
compiling complex.c
linking shared-object mathn/complex.so
make[2]: Leaving directory '/tmp/ruby-build.20200518193720.118097.NYVlMg/ruby-2.2.10/ext/mathn/complex'
make[2]: Entering directory '/tmp/ruby-build.20200518193720.118097.NYVlMg/ruby-2.2.10'
make[2]: warning: -j4 forced in submake: resetting jobserver mode.
compiling rational.c
linking shared-object mathn/rational.so
make[2]: Leaving directory '/tmp/ruby-build.20200518193720.118097.NYVlMg/ruby-2.2.10/ext/mathn/rational'
make[2]: Entering directory '/tmp/ruby-build.20200518193720.118097.NYVlMg/ruby-2.2.10'
make[2]: warning: -j4 forced in submake: resetting jobserver mode.
installing default nkf libraries
compiling nkf.c
linking shared-object json/ext/parser.so
In file included from nkf.c:62:
nkf-utf8/nkf.c: In function ‘module_connection’:
nkf-utf8/nkf.c:5709:5: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
 5709 |     if (nkf_enc_unicode_p(output_encoding))
      |     ^~
nkf-utf8/nkf.c:5712:2: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’
 5712 |  if (x0201_f == NKF_UNSPECIFIED) {
      |  ^~
make[2]: Leaving directory '/tmp/ruby-build.20200518193720.118097.NYVlMg/ruby-2.2.10/ext/json/parser'
make[2]: Entering directory '/tmp/ruby-build.20200518193720.118097.NYVlMg/ruby-2.2.10'
make[2]: warning: -j4 forced in submake: resetting jobserver mode.
compiling objspace_dump.c
compiling objspace.c
compiling object_tracing.c
nkf-utf8/nkf.c: In function ‘options’:
nkf-utf8/nkf.c:6806:22: warning: this statement may fall through [-Wimplicit-fallthrough=]
 6806 |      fold_preserve_f = TRUE;
nkf-utf8/nkf.c:6807:2: note: here
 6807 |  case 'f':   /* folding -f60 or -f */
      |  ^~~~
In file included from nkf.c:62:
nkf-utf8/nkf.c: In function ‘set_input_encoding’:
nkf-utf8/nkf.c:1238:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1238 |  if (x0201_f == NKF_UNSPECIFIED) x0201_f = FALSE; /* -x specified implicitly */
      |     ^
nkf-utf8/nkf.c:1239:5: note: here
 1239 |     case CP50220:
      |     ^~~~
In file included from objspace.c:15:
../../internal.h:84:30: warning: this use of "defined" may not be portable [-Wexpansion-to-defined]
   84 | #if GCC_VERSION_SINCE(4, 6, 0) || __has_extension(c_static_assert)
      |                              ^
../../internal.h:84:30: warning: this use of "defined" may not be portable [-Wexpansion-to-defined]
In file included from objspace_dump.c:15:
../../internal.h:84:30: warning: this use of "defined" may not be portable [-Wexpansion-to-defined]
   84 | #if GCC_VERSION_SINCE(4, 6, 0) || __has_extension(c_static_assert)
      |                              ^
../../internal.h:84:30: warning: this use of "defined" may not be portable [-Wexpansion-to-defined]
In file included from object_tracing.c:16:
../../internal.h:84:30: warning: this use of "defined" may not be portable [-Wexpansion-to-defined]
   84 | #if GCC_VERSION_SINCE(4, 6, 0) || __has_extension(c_static_assert)
      |                              ^
../../internal.h:84:30: warning: this use of "defined" may not be portable [-Wexpansion-to-defined]
objspace.c: In function ‘total_i’:
objspace.c:64:6: warning: this statement may fall through [-Wimplicit-fallthrough=]
   64 |   if (FL_TEST(v, FL_SINGLETON))
      |      ^
objspace.c:66:8: note: here
   66 |        default:
      |        ^~~~~~~
  CC       src/x86/ffi64.lo
linking shared-object date_core.so
make[2]: Leaving directory '/tmp/ruby-build.20200518193720.118097.NYVlMg/ruby-2.2.10/ext/date'
make[2]: Entering directory '/tmp/ruby-build.20200518193720.118097.NYVlMg/ruby-2.2.10'
make[2]: warning: -j4 forced in submake: resetting jobserver mode.
compiling ossl_config.c
compiling ossl_x509req.c
compiling ossl_pkey_dh.c
compiling ossl_x509ext.c
In file included from ossl.h:58,
                 from ossl_config.c:11:
/usr/include/openssl/asn1_mac.h:10:2: error: #error "This file is obsolete; please update your software."
   10 | #error "This file is obsolete; please update your software."
      |  ^~~~~
linking shared-object objspace.so
In file included from ossl.h:58,
                 from ossl_x509ext.c:11:
/usr/include/openssl/asn1_mac.h:10:2: error: #error "This file is obsolete; please update your software."
   10 | #error "This file is obsolete; please update your software."
      |  ^~~~~
In file included from ossl.h:220,
                 from ossl_config.c:11:
openssl_missing.h:79:35: error: macro "EVP_MD_CTX_create" passed 1 arguments, but takes just 0
   79 | EVP_MD_CTX *EVP_MD_CTX_create(void);
      |                                   ^
In file included from /usr/include/openssl/x509.h:18,
                 from /usr/include/openssl/x509v3.h:14,
                 from ossl.h:59,
                 from ossl_config.c:11:
/usr/include/openssl/evp.h:541: note: macro "EVP_MD_CTX_create" defined here
  541 | # define EVP_MD_CTX_create()     EVP_MD_CTX_new()
      |
openssl_missing.h:83:6: error: expected declaration specifiers or ‘...’ before ‘(’ token
   83 | void EVP_MD_CTX_init(EVP_MD_CTX *ctx);
      |      ^~~~~~~~~~~~~~~
openssl_missing.h:91:6: error: expected declaration specifiers or ‘...’ before ‘(’ token
   91 | void EVP_MD_CTX_destroy(EVP_MD_CTX *ctx);
      |      ^~~~~~~~~~~~~~~~~~
In file included from ossl.h:234,
                 from ossl_config.c:11:
ossl_pkey.h:44:5: warning: this use of "defined" may not be portable [-Wexpansion-to-defined]
   44 | #if HAVE_BN_GENCB
      |     ^~~~~~~~~~~~~
ossl_pkey.h:44:5: warning: this use of "defined" may not be portable [-Wexpansion-to-defined]
ossl_pkey.h:44:5: warning: this use of "defined" may not be portable [-Wexpansion-to-defined]
make[2]: *** [Makefile:293: ossl_config.o] Error 1
make[2]: *** Waiting for unfinished jobs....
In file included from ossl.h:58,
                 from ossl_x509req.c:11:
/usr/include/openssl/asn1_mac.h:10:2: error: #error "This file is obsolete; please update your software."
   10 | #error "This file is obsolete; please update your software."
      |  ^~~~~
make[2]: Leaving directory '/tmp/ruby-build.20200518193720.118097.NYVlMg/ruby-2.2.10/ext/objspace'
In file included from ossl.h:58,
                 from ossl_pkey_dh.c:13:
/usr/include/openssl/asn1_mac.h:10:2: error: #error "This file is obsolete; please update your software."
   10 | #error "This file is obsolete; please update your software."
      |  ^~~~~
make[2]: Entering directory '/tmp/ruby-build.20200518193720.118097.NYVlMg/ruby-2.2.10'
make[2]: warning: -j4 forced in submake: resetting jobserver mode.
compiling pathname.c
installing default pathname libraries
In file included from ossl.h:220,
                 from ossl_x509ext.c:11:
openssl_missing.h:79:35: error: macro "EVP_MD_CTX_create" passed 1 arguments, but takes just 0
   79 | EVP_MD_CTX *EVP_MD_CTX_create(void);
      |                                   ^
In file included from /usr/include/openssl/x509.h:18,
                 from /usr/include/openssl/x509v3.h:14,
                 from ossl.h:59,
                 from ossl_x509ext.c:11:
/usr/include/openssl/evp.h:541: note: macro "EVP_MD_CTX_create" defined here
  541 | # define EVP_MD_CTX_create()     EVP_MD_CTX_new()
      |
openssl_missing.h:83:6: error: expected declaration specifiers or ‘...’ before ‘(’ token
   83 | void EVP_MD_CTX_init(EVP_MD_CTX *ctx);
      |      ^~~~~~~~~~~~~~~
openssl_missing.h:91:6: error: expected declaration specifiers or ‘...’ before ‘(’ token
   91 | void EVP_MD_CTX_destroy(EVP_MD_CTX *ctx);
      |      ^~~~~~~~~~~~~~~~~~
In file included from ossl.h:234,
                 from ossl_x509ext.c:11:
ossl_pkey.h:44:5: warning: this use of "defined" may not be portable [-Wexpansion-to-defined]
   44 | #if HAVE_BN_GENCB
      |     ^~~~~~~~~~~~~
ossl_pkey.h:44:5: warning: this use of "defined" may not be portable [-Wexpansion-to-defined]
ossl_pkey.h:44:5: warning: this use of "defined" may not be portable [-Wexpansion-to-defined]
ossl_x509ext.c: In function ‘ossl_x509ext_set_value’:
ossl_x509ext.c:365:9: warning: implicit declaration of function ‘M_ASN1_OCTET_STRING_set’; did you mean ‘ASN1_OCTET_STRING_set’? [-Wimplicit-function-declaration]
  365 |     if(!M_ASN1_OCTET_STRING_set(asn1s, s, RSTRING_LENINT(data))){
      |         ^~~~~~~~~~~~~~~~~~~~~~~
      |         ASN1_OCTET_STRING_set
In file included from ossl.h:220,
                 from ossl_x509req.c:11:
openssl_missing.h:79:35: error: macro "EVP_MD_CTX_create" passed 1 arguments, but takes just 0
   79 | EVP_MD_CTX *EVP_MD_CTX_create(void);
      |                                   ^
In file included from /usr/include/openssl/x509.h:18,
                 from /usr/include/openssl/x509v3.h:14,
                 from ossl.h:59,
                 from ossl_x509req.c:11:
/usr/include/openssl/evp.h:541: note: macro "EVP_MD_CTX_create" defined here
  541 | # define EVP_MD_CTX_create()     EVP_MD_CTX_new()
      |
openssl_missing.h:83:6: error: expected declaration specifiers or ‘...’ before ‘(’ token
   83 | void EVP_MD_CTX_init(EVP_MD_CTX *ctx);
      |      ^~~~~~~~~~~~~~~
openssl_missing.h:91:6: error: expected declaration specifiers or ‘...’ before ‘(’ token
   91 | void EVP_MD_CTX_destroy(EVP_MD_CTX *ctx);
      |      ^~~~~~~~~~~~~~~~~~
In file included from ossl.h:234,
                 from ossl_x509req.c:11:
ossl_pkey.h:44:5: warning: this use of "defined" may not be portable [-Wexpansion-to-defined]
   44 | #if HAVE_BN_GENCB
      |     ^~~~~~~~~~~~~
ossl_pkey.h:44:5: warning: this use of "defined" may not be portable [-Wexpansion-to-defined]
ossl_pkey.h:44:5: warning: this use of "defined" may not be portable [-Wexpansion-to-defined]
In file included from ossl.h:220,
                 from ossl_pkey_dh.c:13:
openssl_missing.h:79:35: error: macro "EVP_MD_CTX_create" passed 1 arguments, but takes just 0
   79 | EVP_MD_CTX *EVP_MD_CTX_create(void);
      |                                   ^
In file included from /usr/include/openssl/x509.h:18,
                 from /usr/include/openssl/x509v3.h:14,
                 from ossl.h:59,
                 from ossl_pkey_dh.c:13:
/usr/include/openssl/evp.h:541: note: macro "EVP_MD_CTX_create" defined here
  541 | # define EVP_MD_CTX_create()     EVP_MD_CTX_new()
      |
openssl_missing.h:83:6: error: expected declaration specifiers or ‘...’ before ‘(’ token
   83 | void EVP_MD_CTX_init(EVP_MD_CTX *ctx);
      |      ^~~~~~~~~~~~~~~
openssl_missing.h:91:6: error: expected declaration specifiers or ‘...’ before ‘(’ token
   91 | void EVP_MD_CTX_destroy(EVP_MD_CTX *ctx);
      |      ^~~~~~~~~~~~~~~~~~
In file included from ossl.h:234,
                 from ossl_pkey_dh.c:13:
ossl_pkey.h:44:5: warning: this use of "defined" may not be portable [-Wexpansion-to-defined]
   44 | #if HAVE_BN_GENCB
      |     ^~~~~~~~~~~~~
ossl_pkey.h:44:5: warning: this use of "defined" may not be portable [-Wexpansion-to-defined]
ossl_pkey.h:44:5: warning: this use of "defined" may not be portable [-Wexpansion-to-defined]
ossl_x509ext.c: In function ‘ossl_x509ext_get_value’:
ossl_x509ext.c:422:2: warning: implicit declaration of function ‘M_ASN1_OCTET_STRING_print’; did you mean ‘ASN1_OCTET_STRING_set’? [-Wimplicit-function-declaration]
  422 |  M_ASN1_OCTET_STRING_print(out, ext->value);
      |  ^~~~~~~~~~~~~~~~~~~~~~~~~
      |  ASN1_OCTET_STRING_set
ossl_pkey_dh.c: In function ‘ossl_dh_new’:
ossl_x509ext.c:422:36: error: dereferencing pointer to incomplete type ‘X509_EXTENSION’ {aka ‘struct X509_extension_st’}
  422 |  M_ASN1_OCTET_STRING_print(out, ext->value);
      |                                    ^~
ossl_pkey_dh.c:69:24: error: dereferencing pointer to incomplete type ‘EVP_PKEY’ {aka ‘struct evp_pkey_st’}
   69 |  if (EVP_PKEY_type(pkey->type) != EVP_PKEY_DH) {
      |                        ^~
ossl_pkey_dh.c: At top level:
ossl_pkey_dh.c:84:48: warning: this use of "defined" may not be portable [-Wexpansion-to-defined]
   84 | #if defined(HAVE_DH_GENERATE_PARAMETERS_EX) && HAVE_BN_GENCB
      |                                                ^~~~~~~~~~~~~
ossl_pkey_dh.c:84:48: warning: this use of "defined" may not be portable [-Wexpansion-to-defined]
ossl_pkey_dh.c:84:48: warning: this use of "defined" may not be portable [-Wexpansion-to-defined]
ossl_pkey_dh.c: In function ‘dh_generate’:
ossl_pkey_dh.c:105:48: warning: this use of "defined" may not be portable [-Wexpansion-to-defined]
  105 | #if defined(HAVE_DH_GENERATE_PARAMETERS_EX) && HAVE_BN_GENCB
      |                                                ^~~~~~~~~~~~~
ossl_pkey_dh.c:105:48: warning: this use of "defined" may not be portable [-Wexpansion-to-defined]
ossl_pkey_dh.c:105:48: warning: this use of "defined" may not be portable [-Wexpansion-to-defined]
ossl_pkey_dh.c:106:14: error: storage size of ‘cb’ isn’t known
  106 |     BN_GENCB cb;
      |              ^~
ossl_pkey_dh.c:106:14: warning: unused variable ‘cb’ [-Wunused-variable]
ossl_x509req.c: In function ‘ossl_x509req_get_signature_algorithm’:
ossl_x509req.c:311:34: error: dereferencing pointer to incomplete type ‘X509_REQ’ {aka ‘struct X509_req_st’}
  311 |     if (!i2a_ASN1_OBJECT(out, req->sig_alg->algorithm)) {
      |                                  ^~
ossl_pkey_dh.c: In function ‘ossl_dh_compute_key’:
ossl_pkey_dh.c:508:12: error: dereferencing pointer to incomplete type ‘DH’ {aka ‘struct dh_st’}
  508 |     if (!dh->p)
      |            ^~
ossl_pkey_dh.c: In function ‘ossl_dh_is_private’:
ossl_pkey_dh.c:277:1: warning: control reaches end of non-void function [-Wreturn-type]
  277 | }
      | ^
ossl_pkey_dh.c: In function ‘ossl_dh_is_public’:
ossl_pkey_dh.c:260:1: warning: control reaches end of non-void function [-Wreturn-type]
  260 | }
      | ^
make[2]: *** [Makefile:293: ossl_pkey_dh.o] Error 1
make[2]: *** [Makefile:293: ossl_x509ext.o] Error 1
make[2]: *** [Makefile:293: ossl_x509req.o] Error 1
make[2]: Leaving directory '/tmp/ruby-build.20200518193720.118097.NYVlMg/ruby-2.2.10/ext/openssl'
make[1]: *** [exts.mk:205: ext/openssl/all] Error 2
make[1]: *** Waiting for unfinished jobs....
  CPPAS    src/x86/unix64.lo
  CC       src/x86/ffi.lo
  CPPAS    src/x86/sysv.lo
  CCLD     libffi_convenience.la
ar: `u' modifier ignored since `D' is the default (see `U')
  CCLD     libffi.la
linking shared-object pathname.so
make[2]: Leaving directory '/tmp/ruby-build.20200518193720.118097.NYVlMg/ruby-2.2.10/ext/pathname'
ar: `u' modifier ignored since `D' is the default (see `U')
make[5]: Leaving directory '/tmp/ruby-build.20200518193720.118097.NYVlMg/ruby-2.2.10/ext/fiddle/libffi-3.2.1'
make[4]: Leaving directory '/tmp/ruby-build.20200518193720.118097.NYVlMg/ruby-2.2.10/ext/fiddle/libffi-3.2.1'
make[3]: Leaving directory '/tmp/ruby-build.20200518193720.118097.NYVlMg/ruby-2.2.10/ext/fiddle/libffi-3.2.1'
linking shared-object fiddle.so
make[2]: Leaving directory '/tmp/ruby-build.20200518193720.118097.NYVlMg/ruby-2.2.10/ext/fiddle'
linking shared-object nkf.so
make[2]: Leaving directory '/tmp/ruby-build.20200518193720.118097.NYVlMg/ruby-2.2.10/ext/nkf'
make[1]: Leaving directory '/tmp/ruby-build.20200518193720.118097.NYVlMg/ruby-2.2.10'
make: *** [uncommon.mk:189: build-ext] Error 2


CIP-0060 | Update to v2

@rphair I'm having those in the original discussions from last year look over this as well so there's no hurry to merge this. The suggested changes came from Jimmy Londo at SickCity. I want him to look over it as well to make sure I've captured exactly what he wanted to do with it.

I meet with Jimmy on Thursday to discuss the changes. So... no merging for now.

@rphair Changes have been discussed and finalized with stakeholders. This can be merged whenever.

Hi, thanks for tagging and sorry for the late response.
Would like to drop a few thoughts on all of this.
Firstly, the document is quite hard to read, because you're nesting many of the fields into various objects without revealing it in the overview table.
It might make sense to label a field "release.release_type" if it's nested in that structure. Then it also shows that it might make sense to just call it "release.type" and "release.title" instead, saving some space.
On contributors / people metadata:
For "Artists" there is an object, which is great, because it can easily be extended with socials / DIDs etc. to make the artist uniquely identifiable. But for other contributors involved (mix / mastering engineers, producers, visual artists etc.) there's only a string - why not use something like a contributor-object for all so they can also add own social handles, links etc. if they want? For players / recommendation algos etc. there's no way to uniquely identify them otherwise once there's two contributors with the same name.
Secondly, some of them appear in the new "release" object, while others, or only the artists (?), appear in the song objects. Along with "copyright", "genres" and other song-related fields, the artists should also be mentionable in the "release" object and vice versa. Some songs of an album may have been produced by different producers. And this would also remove loads of duplication seen in the "Multiple" example.
On release types:
I think it'd make a lot of sense to stick with the industry standards: Single / EP, Album / LP, Compilation, Mixtape etc. and not reinvent the wheel with a "Multiple" release type. The release types make it possible to easily distinguish between "appearances" of artists on compilations / collections and an artist's own albums and other release types. I think it's a basic feature we're used to in modern music streaming services and players should be able to categorize releases accordingly.
On the "song" object nested inside the file object:
This structure seems a bit bloated to me. I would suggest adding a "files[*].type = song" (consistent with the release.type) and then just adding song-related attributes directly to the file object.
Also, the "files[].song.song_title" is identical with the "file[].name" in all examples, so I think "song_title" can simply be removed.
On genres:
I think the limit is too narrow for many use cases. While you may just want to display the basic top-level genres (rock, pop, hiphop etc.) in your initial product's UI, under the hood for recommendation systems additional genres can be very useful. Also the examples imo demonstrate that there's a need for more granular genres (you may not have a "Guitar Live Looping" section in your app, but if an algo comes across this again it may find a great recommendation). Why limit this at all, when you can decide to just ignore them for your particular product?
Hope there's some value in this; maybe also just for the next v3 iteration.
Best regards,
Sean

@AndrewWestberg looks like this is ready for last check, but also our feeling at the meeting is that there could be documentation improvements that would make it more readable as suggested like @sean118 ... so we wanted to give you more time to respond to those suggestions & otherwise this seems ready to merge.

Let's go ahead and merge for now. We can address the @sean118 comments in v3.

@KtorZ @SebastienGllmt @Ryun1 somehow the Last Check tag didn't get this on the agenda for yesterday's meeting.  Can we review & merge it here, at least before the next sort-of-biweekly update with the CIP number assignments & table updates?

@AndrewWestberg confirmed for Last Check at meeting today: https://hackmd.io/@cip-editors/67


display imap login and select error message

require 'mailman'

imap_config = {
  server: 'imap.gmail.com',
  port: '993',
  ssl: true,
  username<EMAIL_ADDRESS>  password: '123456' #wrong password
}
Mailman.config.imap = imap_config

Mailman::Application.run do
  to imap_config[:username] do
  end
end

before
I, [2016-10-26T12:59:10.031439 #14167]  INFO -- : Mailman v0.8.0 started
I, [2016-10-26T12:59:10.031536 #14167]  INFO -- : IMAP receiver enabled (vkill.net@gmail.com@imap.gmail.com).
I, [2016-10-26T12:59:10.032185 #14167]  INFO -- : Polling enabled. Checking every 60 seconds.
/usr/local/rvm/rubies/ruby-2.3.1/lib/ruby/2.3.0/net/imap.rb:1198:in `get_tagged_response': Unknown command g192mb193849556ita (Net::IMAP::BadResponseError)

after
I, [2016-10-26T12:56:42.725073 #13915]  INFO -- : Mailman v0.8.0 started
I, [2016-10-26T12:56:42.725178 #13915]  INFO -- : IMAP receiver enabled (vkill.net@gmail.com@imap.gmail.com).
I, [2016-10-26T12:56:42.725751 #13915]  INFO -- : Polling enabled. Checking every 60 seconds.
/usr/local/rvm/rubies/ruby-2.3.1/lib/ruby/2.3.0/net/imap.rb:1196:in `get_tagged_response':  Invalid credentials (Failure) (Net::IMAP::NoResponseError)

Hi @Mic92 I updated the example code the result, we can see the real errors when we provide a wrong password.
But the travis-ci was wrong, I read the errors, all messages are gem install wrong, do you know why?

Hi @Mic92 I updated the example code the result, we can see the real errors when we provide a wrong password.
But the travis-ci was wrong, I read the errors, all messages are gem install wrong, do you know why?


[WIP] Self versioning updater

Fixes #40
However looks conflicted with #208 😮

@kachick Oops
No worries, I'll just close mine since yours is more complete with tests etc.

WARN: Config Warning
{
  "configError": {
    "validationError": "Cannot find preset's package (github>kachick/renovate-config-asdf:self)",
    "message": "config-validation",
    "stack": "Error: config-validation\n    at fetchPreset (/home/ubuntu/renovateapp/node_modules/renovate/dist/config/presets/index.js:293:23)\n    at runMicrotasks (<anonymous>)\n    at processTicksAndRejections (node:internal/process/task_queues:96:5)\n    at async Object.resolveConfigPresets (/home/ubuntu/renovateapp/node_modules/renovate/dist/config/presets/index.js:238:39)\n    at async mergeRenovateConfig (/home/ubuntu/renovateapp/node_modules/renovate/dist/workers/repository/init/merge.js:206:61)\n    at async getRepoConfig (/home/ubuntu/renovateapp/node_modules/renovate/dist/workers/repository/init/config.js:15:14)\n    at async initRepo (/home/ubuntu/renovateapp/node_modules/renovate/dist/workers/repository/init/index.js:33:14)\n    at async Object.renovateRepository (/home/ubuntu/renovateapp/node_modules/renovate/dist/workers/repository/index.js:40:18)\n    at async renovateRepository (/home/ubuntu/renovateapp/app/worker/index.js:264:26)\n    at async /home/ubuntu/renovateapp/app/worker/index.js:458:5"
  },
  "res": "created"
}

🤔
https://github.com/kachick/deploy-yard-to-pages/issues/13

https://github.com/kachick/renovate-config-asdf/commit/f8f4236e5d57eb5f37da08057f52b673f057ebbf fixed 🎉  https://github.com/kachick/deploy-yard-to-pages/pull/14


[Winds of Magic] Ygethmor’s Flaming Blizzard Bug

Ygethmor’s Flaming Blizzard has literally no effect. It has no damage, only descriptionFrom: Goliath#5940foundry: 10.291wfrp4e: 6.5.3wfrp4e-altdorf: 2.0.2wfrp4e-archives1: 2.4.1wfrp4e-core: 3.1.1wfrp4e-dotr: 3.0.1wfrp4e-eis: 3.1.3wfrp4e-middenheim: 2.4.2wfrp4e-rnhd: 3.0.5wfrp4e-starter-set: 3.1.2wfrp4e-up-in-arms: 3.0.4wfrp4e-wom: 3.0.2Active Modules: foundryvtt-simple-calendar, fvtt-keikaku, give-item, nations-of-mankind-wfrp4e, ogre-kingdom-wfrp4e, token-action-hud, wfrp4e-character-details, wfrp4e-gm-toolkit, wfrp4e-laws-pet-shoppe, wfrp4e-unofficial-grimoire, wfrp4e-vampires

Damage is in the effect when applied from chat


Add support for uploading app files + databases

This PR adds support for a mw app upload and a mw database mysql import command. Both of these are useful for offering a quick way to publish a development environment onto a server (most prominently, for using ddev push).
⚠ It needs to be stressed that this is a development tool, and not a suitable substitute for a production-ready deployment solution.

Look good


[AREA]: Create work orders

Contact details
<EMAIL_ADDRESS>Organization type
Microsoft employee
End-to-end business process
Service to cash
Specify the business process area name for the article.
Create work orders
Enter any additional comments or information you want us to know about this business process area.
In technical review
Specify the date you expect the article to be completed and ready for review.
7/31/2023
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Merged into Create and manage service work


ValueError: The truth value of a Series is ambiguous. Use a.empty, a.bool(), a.item(), a.any() or a.all().

When using a pandas DataFrame, I keep getting this error, no matter what DataFrame I use:
Traceback (most recent call last):
  File "clean_input_file.py", line 177, in <module>
    main()
  File "clean_input_file.py", line 172, in main
    plot_res(data_FSW)
  File "clean_input_file.py", line 149, in plot_res
    title={'label': 'Vote Percentage in 2016 US Presidential Election', 'loc': 'left'}
  File "C:\Users\Pez Amaury\AppData\Local\Programs\Python\Python36-32\lib\site-packages\matplotlib\pyplot.py", line 548, in figure
    **kwargs)
  File "C:\Users\Pez Amaury\AppData\Local\Programs\Python\Python36-32\lib\site-packages\matplotlib\backend_bases.py", line 160, in new_figure_manager
    fig = fig_cls(*args, **kwargs)
  File "C:\Users\Pez Amaury\AppData\Local\Programs\Python\Python36-32\lib\site-packages\pywaffle\waffle.py", line 158, in __init__
    if (not self.fig_args['values'] or not self.fig_args['rows']) and not self.plots:
  File "C:\Users\Pez Amaury\AppData\Local\Programs\Python\Python36-32\lib\site-packages\pandas\core\generic.py", line 1573, in __nonzero__
    .format(self.__class__.__name__))
ValueError: The truth value of a Series is ambiguous. Use a.empty, a.bool(), a.item(), a.any() or a.all().

I understand this is due to using operators or/and in waffle.py, so changing them to np.logical_and and np.logical_or would probably solve the problem.

I have figured out what causes this issue and I will fix it soon.
At current stage, if you want to avoid this error with current version, you can either use parameter "plots" with "111" as the position for the single plot, or convert the pandas series into list or dict.

Fixed. Please upgrade to the latest version 0.0.9.

Thank you :)


Book a lawyer App backend .

In this repository, @richardoppiyo  and @helio3197 created an API only backend application to serve endpoints to our Book a lawyer  application. In this milestone we worked on the following:

Initialised the project wit rails and Postgres and the database
Added the required gems and Installed  dependencies
Created database and intiliazed their relationships
Set up controllers and they respective actions
Added models and their respective associations
Worked on harmonising the controllers and models
Set up the authentication workflow
Added authorizations
Configured AWS for the project
Deployed the project to Heroku.

This is the initial state of the Kanban board:

This is the Final state of the Kansan board:

Finally,
Link to the front end repository

Thanks for the suggestions, we are not adding tests, because we are only two members in this group, and we didn't have the necessary time to implement them, I hope that can be understandable, thank you.


Data class

This issue can be closed when there is a bare-bones class and basic demo script for the information produced by the creation modules and ingested by the estimation and/or evaluation modules.  Discussion of how to implement this should happen in comments on this issue.

I have a few initial thoughts to start the discussion of how this would interact with other parts of the pipeline.  I imagine that a Creator class instance would output two instances of an Information class (or whatever it's called), one with "public" information for an Estimator class instance to ingest and one with "private" information that may be ingested by an Evaluator class instance, so all three main pipeline classes need to know how to talk to it.  Presumably we'd want the class to either itself be pickleable or for it to be instantiated by reading in its serialized contents in whatever manner is most straightforward.  I do think it's preferable to make that process more demanding for the Creator than the Estimator so we can minimize the activation energy for wrapping photo-z PDF codes as Estimator subclasses.

This is being taken care of with a yaml structure (in the branch for #3) where paths to files of TXPipe-compatible formats are provided separately for the shared experimental conditions and for each specific algorithm, leaving the formatting consistency of flexible inputs beyond catalogs of photometry up to whoever writes the subclass for a given Estimator.  It will be easier to define formats for more complex yaml fields for the shared experimental conditions when we can explore concrete options associated with any given Estimator subclass.


Add documentation for undocumented methods in Levenshtein module

Adds documentation for Levensthein.find (both variants).

@straight-shoota Thanks for the suggestions. I updated the PR.

I'd actually like to remove Levenshtein from the std, or at least rewrite the current API. It was mostly written for the compiler. Same thing that happened with the Markdown module.

@asterite It still doesn't hurt to document it.

I'd merge this but...

The base branch restricts merging to authorized users

🤔

@bcardiff thanks, fixed.

Dziękuję @katafrakt


feat: Implement insert condition for merge strategy.

Description

This PR introduces insert condition for the merge strategy in the incremental run.
Resolves #466

Models used to test
{{ config(
        table_type='iceberg',
        materialized='incremental',
        incremental_strategy='merge',
        unique_key=['id'],
        insert_condition='src.status != 0'
    )
}}

{% if is_incremental() %}

select * from (
    values
    (1, -1)
    , (2, 0)
    , (3, 1)
) as t (id, status)

{% else %}

select * from (
    values
    (0, 1)
) as t (id, status)

{% endif %}

Checklist

[x] You followed contributing section
[x] You kept your Pull Request small and focused on a single feature or bug fix.
[x] You added unit testing when necessary
[x] You added functional testing when necessary
[ ] Update documentation (PR)

@nicor88 thanks!

Nice job 💯
@svdimchenko do you want to have another look?

sure, now we have full pack of conditions for merge strategy, thanks to @talhasenSC 💪


Webinterface very slow

Since today the web-ui is super slow for me :( Everything was working fine but without any (knowingly) changes that I made.
It works fine when I restart my rasberry for about a minute or so (didn't do time-tracking). After that, jumping from one page to another (f.e. file-setup to home) will load forever.
Also I just uploaded some files into a folder and it will not show in "Home". It will show that there is my folder with the subfolder. Also that there are 30 files in there. But it will not show the content when clicking on it?!?
Any idea on how to debug the problems?

Hi @georgbachmann
that doesn't sound good. And it sounds, well, as you say: unexpected.

are you running "classic" or "plus spotify"?
which version are you running?
can you ssh into the RPi and type top in the terminal to see what applicatoin squats the CPU power?

Hey @MiczFlor
I am using classic and just did a git pull today... so latest master version
I did a top earlier, but didn't see anything significant. the gpio-buttons.py was using the most cpu with about 2-3%
Could it have something todo with the files I uploaded earlier? That it is processing something? But then the cpu would spike... hm...

Hm. Let's see if somebody else jumps into this thread with a similar issue.
Usually the RPi gets slow if

the power supply is not powerful enough (needs 2.5A and over)
the RAM is full and the RPi starts swapping to the SD card
the RPi gets too hot

Hm... mine has 2.1W (it's an iPad charger)
About the RAM... there is nothing but the phoniebox on the pi... So I guess that should not be the issue?
And at least it does not feel too hot... is there a way to check that more precisely? :)

I have similar problems sometimes. I attributed it to Wi-Fi problems because for me there are no performance issues with the ui when the pi is in a room with good Wi-Fi reception.

I'm having the same issue to the point where my phoniebox times out before it ever shows me the UI, I've put this down to having a large MPD database, the existing cards I have programmed for RFID work but I can't add any more. Connecting to MPD via another app on my laptop works fine though.
Top comes back with the following
16585 www-data  20   0  123812  12656   5636 D    4.6  1.3   0:40.65 php-fpm7.0
16185 www-data  20   0  128024  16348   5828 D    3.0  1.6   0:55.99 php-fpm7.0
466    root             20   0  227088  50324  15288 S   2.6  5.1   25:15.25 mpd
Memory shows
KiB Mem :   994108 total,   462460 free,   172620 used,   359028 buff/cache
KiB Swap:   102396 total,   102396 free,        0 used.   729056 avail Mem
I'm wondering if it's a PHP issue (only guessing), as I have one network share added to my Phoniebox library that has hundreds of folders in it, up until adding this the UI worked perfectly with locally created folders.

Hi @georgbachmann @helloiamgary @m-rl-n
I had a look at this issue again. Using top I identified that the gpio-buttons.py (which I had switched on, but am not using - I have no buttons) took 75% CPU on my RPi 1.
In the web UI under settings I switched it off and got the feeling that the webUI loads much faster. It's a feeling only :) So I wanted to share this with you and have this tested by you - and share with me if you feel the same

@MiczFlor I'm seeing the same issue with the gpio buttons daemon on my Pi1. Disabiling the service helps.
Two questions though

The service is automatically started on boot. how can I disable the service permanently?
Is there a fix for the high CPU for buttons? Are buttons not recommended for the Pi1?

Thanks!

Closing as this is very outdated now.


Gradle 8.5 and 8.6 APIs

Hi @lacasseio!
Wondering if API for 8.5 and 8.6 could be released? :)

Done, it should be available now.

awesome! thank you!


Clean up deprecated items

IPv6
Out of date Multus portions
koko / kokonet

Should we change "build-install multus" to "just install multus by daemonset?"


Pretrained Model

Hello, thank you for the work.
What ImageNet weights are you specifically using for pre-training? For W18_S2 I tried a few different weights from the HRNet repo but they did not match.
Thank you!

Hi, we use HRNet-W18-C-Small-v2 in https://github.com/HRNet/HRNet-Image-Classification

Thank you!


Norm constraints don't act properly on non 'Dense' layers

The way the UnitNorm and MaxNorm constraints work is currently somewhat different, and problematic on certain layer types. For example if one wanted unit-norm convolutional filters weights, these layers would do something, but it wouldn't be quite right since they compute norms over hard-coded dimensions. I'm not sure what the best general solution is to this problem so I wanted to open it up for feedback. The two main options I can think of are:

standardize weight matrices so that the norms one would aggregate over would all be in the same place so the constraints are applied properly during updates, but have them reshaped them to proper form for computing the layer output.

have the constraints.get function call in each layer also take an argument that determines which dimension(s) are aggregated over to compute the norm (which is obviously ignored if it's not needed i.e. NonNeg).

Thinking this through while writing it, I'm pretty sure 2 is the best option. What so you all think?

Wouldn't the right dimension always be the last one, though? Except in the case of convolution kernels.
Do constraints make sense on convolution kernels? I don't think I have ever seen that in the literature.

It's a problem for the maxout layer as well where you'd like to constrain the norm of the feature weights. And it does make sense to constrain the norm of convolution kernels for the same reason it does fully connected layers, and was actually used in the original Dropout paper "Dropout: A Simple Way to Prevent Neural Networks from Overfitting" in their analysis of Street View House Numbers: "Max-norm regularization was used for weights in both convolutional and fully connected layers."
Also, it is not the last dimension you want to sum over if you want to constrain the weight vector of the incoming weights to each hidden unit and so the UnitNorm constraint is wrong, while the MaxNorm constraint works correctly for dense layers, but not maxout or convolutional layers. You can see how the UnitNorm constraint fails here:
# weight matrix example with 10 hidden units
W = np.random.randn(784,10)
# constrain like UnitNorm
W /= np.sqrt(np.sum(W**2, axis=-1, keepdims=True))
# check norm of weight vector to first hidden unit
np.sqrt(np.sum(W[:,0]**2))

Ok, I see. We should definitely have the constraint functions accept an argument to configure the norm axis. Then each layer can customize its call to the constraint function with the proper axis.


Problem with accessing SSD from FPGA

Hello,
I have an U.2 SmartSSD CSD (userguide).
Is there a way to access the SSD (read/write) from the FPGA kernel? I am aware of P2P buffers, but as far as I know, in order to copy data from SSD to P2P buffer in FPGA DDR memory, host needs to initiate the transfer. But in my use case, I need to communicate with SSD from the FPGA kernel, without any involvement of the host CPU.
Any help would be appreciated.

Hi @omidrostamabadi ,
can you please post such query to Xilinx Forum?
https://support.xilinx.com/s/topic/0TO2E000000YKYAWA4/vitis-acceleration-acceleration?language=en_US

The examples under /host/p2p_simple, /host/p2p_bandwidthand /host/p2p_overlap_bandwidth utilize the P2P connection between the FPGA and SSD and the source code includes the required API. The tests also need to run with root access


 Tested with Firefox, Edge, Safari and no issue seen.
What is the expected behavior?
The opening of dialog should be as smooth on Chrome as other browsers
What is the current behavior?
Laggy Mat-Dialog opening animation
What are the steps to reproduce?
Stackblitz: https://stackblitz.com/edit/angular6-fast-dialog
Stackoverflow topic: https://stackoverflow.com/questions/50329776/angular-6-mat-dialog-slow-opening-with-chrome
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular CLI 6.0.1 / Angular Material 6.0.1
Is there anything else we should know?

Noticed this as well, for me it seems to get the slower the higher my browser window is. But then again, that makes sense I guess, more content to paint.

The animation performance is very very slow, specially when you have an infinite scrolling list without virtual scrolling. When you have a lot of items rendered, it starts getting slower and slower. I just wanted to change to an opacity animation or just completely remove it.

Hi guys, I Have The same issue here. This bug broken UI performance.

Same issue here, especially open a dialog in a complicated page

I am getting this only on Chrome Mobile when the keyboard opens immediately because of the embedded input field in the dialog.

also getting the same issue in chrome. are there any plans to fix this in the near future? or good workarounds?

Still an issue with 6.1.0-rc.3
When opening dialog for the first time on Chrome, the animation is really sloppy. After the first time it becomes smooth.
This is not an issue in the latest Firefox

Is there any update this issue? Its quite obvious mat dialog is slower in chrome for the first time load.

It seems to be better after adding this in my case:
.mat-dialog-container {
	will-change: transform;
}

The problem is still present at the moment, and I hope it will be fixed soon. Like @abductedMind said, we will keep using it for the moment because it is usable, but it would be very nice if this could be fixed ASAP. All the other animations we are doing on our side are fluids and smooth, but the one on the Material Dialog is not, which make it pretty annoying. Please, I'm happy to use material but these kind of things are crucial, specially for a UI framework.

@schankam do you use Material version 6 or 7? I have seen reports about Material 7 animations being much better.
We are still on Material 6 currently.

So some updates here: I've updated to Material 7 and the modal animation is now fast and smooth !
@rvalimaki Thanks for your comment, it helped :)

Closing the issue since people are reporting that it's fixed. We also have an option now to disable the animation.

@crisbeto What's the option?

I still find it pretty slow.

The problem is when you are using two animations at once - opening sidenav and backdrop transition. Quick fix is to put transition-delay on backdrops transition like 0.3s

To me, the problem is not fixed. I noticed this sloppy behaviour with mat-tab-group
Here the blitzstack comming from https://material.angular.io/components/tabs/overview
https://stackblitz.com/angular/yrjaxnymmqk?file=app%2Ftab-group-animations-example.ts
Try to compare the slow animation in Chrome VS Firefox.
Firefox >>> Chrome here.


The URL is dead

the URL in the readme file that links to https://lab.github.com/githubtraining/devops-with-github-actions gives a 404 error. can you fix this?

https://docs.github.com/en/actions/quickstart


QueueToken should be Send

It is quite annoying to be unable to create objects in one thread attached to a queue living in another thread. It is something I was doing using a previous version, and it's blocking me now.
If I understand correctly, doing that would require giving the QueueToken of the remote queue to Proxy::attach. Which is impossible since QueueToken is not Send. I feel like it has been done that way so that the filter given to Main::assign doesn't need to be Send. But it's quite annoying. I feel trapped in my threads.
Instead of making QueueToken Send, to preserve the good property of Main::assign another idea would be to add a RemoteQueueToken with RemoteAttached and RemoteMain for which the filter in assign needs to be Send.

it's not Send, because it's not thread safe to do so. You should manage objects only on a thread you've created them. In a multi thread context you may create event queue on a thread you want, that's how everyone is doing so.

Could you explain why it is not thread safe?

that's how everyone is doing so

Well I'm not doing it so. I can't, because in my context I have no guaranties about in which thread some particular code is being executed that needs to create an object (a shared memory pool here). So I am blocked. And it feels like a limitation to me because I don't see why it is not thread safe to assign an object to a remote queue upon creation.

And it feels like a limitation to me because I don't see why it is not thread safe to assign an object to a remote queue upon creation.

The answer is pretty straightforward actually : it is not threadsafe because libwayland-client.so does not do any synchronisation around its event queue, hence doing anything with an event queue on an other thread than the one hosting is racy and could corrupt the internal state of the queue. That includes assigning a new object to this queue.
This cannot be made threadsafe in the crate's API without dropping support for using the system-provided libwayland, which would in turn make it impossible to support OpenGL.

I see... Ah yes I suppose mesa is using libwayland-client.so to implement EGL. Well too bad.

Note  that there is a potential way forward regarding this, but it is a long shot : https://github.com/Smithay/wayland-rs/issues/317


Question about evaluation performance

I downloaded and used your pretrained model, but I couldn't get the reported result.
Q1. Can I ask which part am I missed??
Total images: 2754
Valid images: 2754,  Total instances: 15573,  Average: 5.65/image
Inference time: 86.035171  Average: 0.031240/image
Umeyama time: 104.452625  Average: 0.037928/image
Total time: 323.474025
mAP:
3D IoU at 25: 81.9
3D IoU at 50: 71.0
3D IoU at 75: 43.1
5 degree, 2cm: 11.4
5 degree, 5cm: 12.0
10 degree, 2cm: 33.5
10 degree, 5cm: 37.8
Acc:
3D IoU at 25: 90.3
3D IoU at 50: 82.9
3D IoU at 75: 57.5
5 degree, 2cm: 23.3
5 degree, 5cm: 24.5
10 degree, 2cm: 45.5
10 degree, 5cm: 50.2

I have run the evaluation several times. With the released model, similar results should be expected.
Did you follows the instructions in README when you prepare the dataset?

Yeah, I followed your instructions.
(shape_data.py) There are some issues in this part. https://github.com/mentian/object-deformnet/issues/3#issuecomment-672858239
and (pose_data.py) I found some real_test background value was 0 , instead of 255 value. So I change 0 value to 255.

kind of busy, will respond to you in the next couple days.

I used pretrained model to evaluate real-test dataset and got results similar to yours.
mAP:
3D IoU at 25: 79.3
3D IoU at 50: 68.4
3D IoU at 75: 40.4
5 degree, 2cm: 11.5
5 degree, 5cm: 12.1
10 degree, 2cm: 33.5
10 degree, 5cm: 37.8
Acc:
3D IoU at 25: 89.8
3D IoU at 50: 82.4
3D IoU at 75: 56.8
5 degree, 2cm: 23.4
5 degree, 5cm: 24.5
10 degree, 2cm: 45.5
10 degree, 5cm: 50.1

Could you confirm that you specify the correct mode path in evaluate.py? To evaluate on the real_test dataset, you need to set the value for both --data and --model.
I actually run evaluation on real test dataset with the pre-trained model for CAMERA, and get similar result as you provided. I guess this might be the reason.
Please let me know if this does not solve your problem.

Thanks, the problem was solved !!
Total images: 2754
Valid images: 2754,  Total instances: 15573,  Average: 5.65/image
Inference time: 113.280357  Average: 0.041133/image
Umeyama time: 177.431597  Average: 0.064427/image
Total time: 462.305699
Evaluating ...
mAP:
3D IoU at 25: 83.4
3D IoU at 50: 77.4
3D IoU at 75: 53.5
5 degree, 2cm: 19.5
5 degree, 5cm: 21.6
10 degree, 2cm: 43.5
10 degree, 5cm: 54.0
Acc:
3D IoU at 25: 91.5
3D IoU at 50: 87.7
3D IoU at 75: 69.4
5 degree, 2cm: 31.6
5 degree, 5cm: 34.3
10 degree, 2cm: 55.0
10 degree, 5cm: 63.1

谢谢，问题解决了！！
Total images: 2754
Valid images: 2754,  Total instances: 15573,  Average: 5.65/image
Inference time: 113.280357  Average: 0.041133/image
Umeyama time: 177.431597  Average: 0.064427/image
Total time: 462.305699
Evaluating ...
mAP:
3D IoU at 25: 83.4
3D IoU at 50: 77.4
3D IoU at 75: 53.5
5 degree, 2cm: 19.5
5 degree, 5cm: 21.6
10 degree, 2cm: 43.5
10 degree, 5cm: 54.0
Acc:
3D IoU at 25: 91.5
3D IoU at 50: 87.7
3D IoU at 75: 69.4
5 degree, 2cm: 31.6
5 degree, 5cm: 34.3
10 degree, 2cm: 55.0
10 degree, 5cm: 63.1

Hello, I have set the data to real_ test and model are also set to real/model_50.pth, but the result is still consistent with your first attempt. May I ask how you resolved it at that time？

Thanks, the problem was solved !!
Total images: 2754
Valid images: 2754,  Total instances: 15573,  Average: 5.65/image
Inference time: 113.280357  Average: 0.041133/image
Umeyama time: 177.431597  Average: 0.064427/image
Total time: 462.305699
Evaluating ...
mAP:
3D IoU at 25: 83.4
3D IoU at 50: 77.4
3D IoU at 75: 53.5
5 degree, 2cm: 19.5
5 degree, 5cm: 21.6
10 degree, 2cm: 43.5
10 degree, 5cm: 54.0
Acc:
3D IoU at 25: 91.5
3D IoU at 50: 87.7
3D IoU at 75: 69.4
5 degree, 2cm: 31.6
5 degree, 5cm: 34.3
10 degree, 2cm: 55.0
10 degree, 5cm: 63.1

Hello, I have set the data to real_ test and model are also set to real/model_50.pth, but the result is still consistent with your first attempt. May I ask how you resolved it at that time？


Customize Audience on SAML2.0 Token

We have a SAP-HANA system which supports only 1 SpID identifier, this configured SpID must match the Audience in the SAML 2.0 Token to support SSO , AAD automatically populate this xml node (AudienceRestrictions->Audience) with spn:[Guid] which is different for each AAD registration, we have multiple applications registered in AAD and we are interested for all users to SSO to Hana using their respective tokens.
Is there a way/it is supported currently to statically include an additional audience on the token?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 195c79a3-ccc5-8c6a-233e-95e344a9b4df
Version Independent ID: 401c7557-5817-bbd3-5bd8-8c97ef5a28cc
Content: Customize Azure AD tenant app claims (PowerShell) - Microsoft identity platform
Content Source: articles/active-directory/develop/active-directory-claims-mapping.md
Service: active-directory
Sub-service: develop
GitHub Login: @rwike77
Microsoft Alias: ryanwi

@jesussalasp Thank you for your feedback . We will investigate and update the thread.

@jesussalasp I would like to request you to check the SAP Hana SSO integration Tutorial . I will find out about the other query if we can include multiple audiences in the token and let you know.

Hello @shashishailaj we tried that option and did not work, the database disallow the user authentication because the audience do not match with the configuration on the DB.

Have a look here: https://docs.microsoft.com/en-us/answers/questions/23675/oauth-obo-flow-azure-ad.html?sort=oldest
tl;dr: Change the Application ID URI (int the App Registration > Expose an API) to api://your-name or https://your-name, and potentially reimport the metadata into SAP:

@shashishailaj any update on this?

@jesussalasp My apologies for the delay on this.  At a time there can be only one audience , there cant be multiple audience in one token. Because Audience denotes the end entity who would be able to consume the token to provide access to the requestor . This is by design at this point . There may be other ways to design this but I am not sure on them.  I would suggest you to send us an email to azcommunity[at]microsoft[dot]com with a subject line "ATTN:Shashi" referencing this issue if you would like to have a discussion with support team further on this and we will help facilitate the same if needed. But I am sure of one thing that our STS (azure AD security token service) will always grant a token with a single audience not more than one audience. We will now close this issue.
Thank you.

@shashishailaj I sent the email as you suggested, will wait for you. thanks!


About - View with Legal information

[ ] Link to Imprint
[ ] Link to PrivacyPolicy
[ ] App Icon
[ ] App Name

Imprint & PrivacyPolicy should be stored locally in static HTML Files and called via WebView:
https://docs.microsoft.com/en-us/xamarin/xamarin-forms/user-interface/webview?tabs=macos


Mongo Express return 404 page not found

Hello everyone :)
First of all, congratulations on a great job :)
Unfortunately I have noticed that I have some problems with mongo express in the browser.
Every time I try to access I get the error 404 page not found.
I turn over to you my docker.compose:
#ddev-generated
# Remove the line above if you don't want this file to be overwritten when you run
# ddev get ddev/ddev-mongo
#
# This file comes from https://github.com/ddev/ddev-mongo
#
services:
  mongo:
    container_name: ddev-${DDEV_SITENAME}-mongo
    image: mongo:5-focal
    volumes:
      - type: "volume"
        source: mongo
        target: "/data/db"
        volume:
          nocopy: true
      - ".:/mnt/ddev_config"
    restart: "no"
    expose:
      - "27017"
    labels:
      com.ddev.site-name: ${DDEV_SITENAME}
      com.ddev.approot: $DDEV_APPROOT
    environment:
      - MONGO_INITDB_ROOT_USERNAME=
      - MONGO_INITDB_ROOT_PASSWORD=
      - MONGO_INITDB_DATABASE=db
    healthcheck:
      test: [ "CMD-SHELL", "mongo --eval 'db.runCommand(\"ping\").ok' localhost:27017/test --quiet" ]
      timeout: 60s

  mongo_test: # Nome del servizio per il database di test
    container_name: ddev-${DDEV_SITENAME}-mongo-test
    image: mongo:5-focal
    volumes:
      - type: "volume"
        source: mongo_test # Nome del volume per il database di test
        target: "/data/db"
        volume:
          nocopy: true
    restart: "no"
    expose:
      - "27018" # Porta diversa per il database di test
    labels:
      com.ddev.site-name: ${DDEV_SITENAME}
      com.ddev.approot: $DDEV_APPROOT
    environment:
      - MONGO_INITDB_ROOT_USERNAME= # Nome utente per il database di test
      - MONGO_INITDB_ROOT_PASSWORD= # Password per il database di test
      - MONGO_INITDB_DATABASE=db_test # Nome del database di test

  mongo-express:
    container_name: ddev-${DDEV_SITENAME}-mongo-express
    image: mongo-express:latest
    restart: "no"
    labels:
      com.ddev.site-name: ${DDEV_SITENAME}
      com.ddev.approot: ${DDEV_APPROOT}
      com.ddev.platform: ddev
    expose:
      - "8081"
    environment:
      VIRTUAL_HOST: $DDEV_HOSTNAME
      ME_CONFIG_BASICAUTH_USERNAME: ''
      ME_CONFIG_BASICAUTH_PASSWORD: ''
      ME_CONFIG_MONGODB_ENABLE_ADMIN: false
      ME_CONFIG_MONGODB_AUTH_USERNAME: ''
      ME_CONFIG_MONGODB_AUTH_PASSWORD: ''
      ME_CONFIG_MONGODB_AUTH_DATABASE: 'db'
      HTTP_EXPOSE: "9091:8081"
    depends_on:
      - mongo
    entrypoint: [ sh, -c, "sleep 5s && tini -- /docker-entrypoint.sh mongo-express" ]

volumes:
  mongo:
  mongo_test:

The only thing I added was a second database for testing and removed local authentication.
For any further information please ask me :)

It seems like you're saying you changed the docker-compose.mongo.yaml, or you wouldn't have provided it here?

Please don't change the docker-compose.mongo.yaml, instead add a docker-compose.mongo_extra.yaml with your changes.
Please don't ask for support on something you've changed. Please demonstrate the problem with plain-vanilla add-on first, thanks!

Hmm, I have the same problem, although I did not change a thing in the configuration. Any ideas?

Hi @detrax,
Check the fix in:

#18

Hi @detrax,
Check the fix in:
* [Bump mongo-express, update config, do not expand php version, fixes #16 #18](https://github.com/ddev/ddev-mongo/pull/18)

Hi @detrax , I've released a 1.2.0 version with the mentioned fix. Please take a look. Thanks.

I just set up ddev in my folder and called "ddev get ddev/ddev-mongo"

Don't forget to do a ddev restart (and then a ddev describe will give you the mongo express url).

Happy to continue the conversation here or elsewhere, but closing for now due to lack of response.


Refresh and enable the 'ComBinder' code in PowerShell

The support for dynamic and ComBinder was added by https://github.com/dotnet/runtime/pull/33060 and shipped in .NET 5 preview.2.
We should refresh the code under src\System.Management.Automation\engine\ComInterop with the code from dotnet/runtime and enable ComBnder code path in our binders.
ComBinder will significantly speed up COM interop in PowerShell. See the reference issue: https://github.com/dotnet/runtime/issues/36944

Added a Config file to the onedrive link
.\Fortigate2Excel.ps1" .\PerfTest_20200526_0942.conf
to run the command


--latex-engine → --pdf-engine

https://pandoc.org/releases.html#behavior-changes-1

Sorry my mind blocked me after installing .NET 5 & VS Code on Ubuntu 20.04.  I copied and pasted the code in the README w/o taking the behavioral changes in the linked pandoc release notes into consideration.  Closes #6 by updating the relevant part in the README with such change.


select all in code editor does not actually select all, just what is visible

super weird unsure if us or codemirror via cmd+a

actually this works in the browser app, will verify it works in the desktop app after release

we this is still not working in tauri but fine in the ui

this might be fixed with electron port


Fix texture caching.

Related forum issue: https://forum.babylonjs.com/t/got-wrong-mapping-in-equirectangularcubetexture/31329
Related playground: https://playground.babylonjs.com/#NIWPUI#1

Should we do it for all cube textures, passing isCube in ???
GG for the fix by the way :-)

Thanks! I'll add to the other cube textures :D


T-Ray Scanners Not Working as Intended

Description
I have not played in a while, but I noticed that T-Ray scanners don't seem to work in the player's bag or belt slots anymore. However, if this is an intended change, there are some bugs associated with it, namely;

Switching T-Ray scanner into belt from hand while on causes the area seen during handheld to remain visible no matter the distance of the player until they turn the T-Ray off or switch it back into hand.
Spamming between hand and belt allows for T-Ray to work while on belt.

Reproduction
For the first bug:

Get T-Ray and turn it on while in hand
Switch it to belt or bag
Walk Away
Underneath the tile remains visible from the initial T-Ray start

For the second bug:

Turn T-Ray on in hand
Spam it between belt and hand
It will eventually allow you to use it while in the belt slot

Screenshots

Additional context
The first screenshot details the first bug.
The second screenshot shows it working while I walk in my belt slot. I don't know how to record video but it shows the next "under-tile" loading in with the disposal bend showing up first.

Ok, I've noticed that the info the admin told me was incorrect, T-Ray should still be working as long as it is on/on your character. However, I have had some bugs in which the issues I highlight above still happen with the T-Ray not updating the tiles while moving outside of the hands of the player.


Add test

Related to #1818

Looks fine, but one comment.

Coverage decreased (-1.9%) to 72.26% when pulling 53977db8ce3c75f3069c24f3eb0069421433760d on i1818 into b18c23241c0634b632cdac8f8fcf6e1bc8cead9d on master.


panoply.rb: depends_on_java

Thank you for the contribution. It needed some fixes, so they were made in a11199dda5977ccc6c63753c99b32c1f08f69bdf. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.


Add ability to sort a data table by clicking a table heading

Adds the ability to sort columns by clicking the table header. Accepts an onClick in the model, which will make the column clickable. Then, you can pass props.sortColumn and props.sortDirection into the <Table /> to get the up/down icon to display.

Thank you @tuckerconnelly I have been keeping this unmerges because the Table is already deprecated in favour of a more flexible version. We are keeping the 1.x in the master branch so if you think it's worthy feel free to open a PR there. Dev holds now the 2.0 beta with some rewritten components


keep the message channel callback active

fix for issue AGCORDOVA-125
How to test:

remove the currently installed push plugin:

$ cordova plugin rm aerogear-cordova-push

install my branch:

$ cordova plugin add https://github.com/edewit/aerogear-pushplugin-cordova#AGCORDOVA-125

Invoke the register method multiple times and see that the success callback is called for all of them.

Tested by Alex


Injective and Isomorphic type classes?

I had some older code for this. Is this useful or not?
See

https://hackage.haskell.org/package/type-iso-<IP_ADDRESS>/candidate/docs/Data-Types-Injective.html
https://hackage.haskell.org/package/type-iso-<IP_ADDRESS>/candidate/docs/Data-Types-Isomorphic.html

Yes I do believe this is useful. E.g. you may make a combined ParserPrettyPrinter out of combinators resulting in something with a type param made up of products and coproducts, and then you need to go from that type to the type your interested in working with (via Iso).


Unable to use inputs in "insert link" modal

Description
When the insert link modal is presented I am unable to enter text into the inputs in the insert link modal. When I click on them the cursor does not select them and does not blink like I'm able to type. When I type after clicking nothing happens.

Windows, macOS
Firefox, Chrome

How to reproduce?

click insert link
click on any text input in the modal
try to use the inputs

Can you provide me a demo page with the bug?
I can't reproduce :/
Feel free to reopen if you have a working (I mean... a buggy :D) demo :)


Let :delete have form params

This small change is the difference between passing and failing per the gist linked on #365.

Merged, thanks @DanBurton! (and look all all those approvals ;) )


The property 'OnRemove' cannot be found on this object

Hello, I'm using Azure Cloud Shell and I'm encountering this error when running a PowerShell script.  My script manages VMs.  Any ideas?
InvalidOperation: /usr/local/share/powershell/Modules/Microsoft.PowerShell.UnixCompleters/0.1.1/OnStart.ps1:12
Line |
  12 |      $m.OnRemove = {
     |      ~~~~~~~~~~~~~~~
     | The property 'OnRemove' cannot be found on this object. Verify that the property exists and can be set.

I'll post a script when I get a chance to sanitize it.

Environment data
PSVersion                      7.0.3
PSEdition                      Core
GitCommitId                    7.0.3
OS                             Linux 4.15.0-1095-azure #105~16.04.1-Ubuntu SMP Sun Sep 6 00:30:35 UTC 2020
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Hmmm, that's strange. I've never seen that reported before. Does the module import properly otherwise?

It does:
ModuleType Version    PreRelease Name                                ExportedCommands
---------- -------    ---------- ----                                ----------------
Binary     0.1.1                 Microsoft.PowerShell.UnixCompleters {Import-UnixCompleters, Remove-UnixCompleters, Set-UnixCompleter}```

The unfortunate (or fortunate?) is that I'm no longer seeing the error.

Thank you for your response.  I'll repost if it occurs again.

Glenn

@rjmholt Is there an async at the module load time?

@rjmholt Is there an async at the module load time?

I don't believe there's any async or task usage in the module at all


GenerationReplacement and unit tests

PR for #24
The client can now specify how the generation of solutions for the next iteration is calculated, having in regards the current generation and the newly created one.
By default, the generation for the next iteration is the new one, but this could be refined, to create a better generation, taking in accound more attributes of the solutions found in both of them.

Coverage decreased (-0.8%) to 86.416% when pulling d2ae36c9f33730987815e8073408394ae8e101c7 on 24 into c538d4c238b04e69c767897df3d05e4414b52cd5 on master.

@rultor merge

@rultor merge

@amihaiemil OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@amihaiemil Done! FYI, the full log is here (took me 1min)


Tryna test issue section on GitHubY #1

          > Tryna test issue section on [GitHub**Y**](github.com/loneroust) #1

yigit yilmaz

as you said
Originally posted by @loneroust in https://github.com/loneroust/skills-introduction-to-github/issues/2#issuecomment-1630830163
Test reference functionality

test done


Add preview for files and history provider

How are you getting the file icons here in the photo?

How are you getting the file icons here in the photo?

:h g:clap_enable_icon, ensure you have installed the nerdfont https://www.nerdfonts.com/.

Is there any other requirement? I have the setting on and I use nerdfonts in many places in my config. I am not seeing the icons when I do :Clap files

Do you have installed the rust binary maple? files icon support is only avaliable when maple exists.

Disregard, as soon as I added the installed binary it worked


Keeps crashing

Whenever I use route finder, it crashes right at the very end and gives this code:
SBOX_FATAL_MEMORY_EXCEEDED
I have a decent system, 16 gigs of ram and a 5600X, and checked task manager and was only getting about 4-5 gigs of memory usage and 60% cpu.
I've closed all other programs.
Is there something I'm doing wrong?

That is weird, I have never seen this. Some questions to help troubleshoot:

What browser (Chrome, Firefox, etc.) are you using? Could you try with another one and see if you have the same issue?
What job area have you loaded?
Could you share the parameters you are setting for your route searches?


Use anchors when doing 'match'es

Poked by reading https://www.elastic.co/blog/do-you-grok-grok
And thanks for the great work!

Nice catch! Thanks ;)


Don't remove xml version

After running avdo *.xml
All my files lost their first line
<?xml version="1.0" encoding="utf-8"?>

I'll disable this by default.

Why was removing enabled by default?
In the readme example the avgo tool explicitly added the header from the file that did not have it.

Thanks for pointing that out. I've updated the README.

Fixed in v0.1.0-alpha.8.
You can run npm install -g avdo to get the updated version.


SlackHandler: do not send username and icon

Is there a way to use SlackHandler without sending username and icon? We have our bot configured in Slack administration and it is used by more services, so we want to remove duplicated username and icon definitions.

#846 should take care of this I believe.

Nice, thanks!

And btw I'm looking for slack users to give the new handlers in that PR a go, so if you have time and can try that branch and give feedback that'd be cool :)

Okay, I will do it later today :)


BUG: pip download scipy requires openblas

Describe your issue.
For my usage I need to use pip download on a machine and then pip install on the target machine with no access to internet.
I can't run pip download on scipy as it requires openblas which is not installed on my machine, is it expected.
Reproducing Code Example
Run pip download scipy on a machine without openblas

Error message
python3 -m pip download scipy
Collecting scipy
  Using cached scipy-1.10.0.tar.gz (42.4 MB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Installing backend dependencies ... done
    Preparing wheel metadata ... error
    ERROR: Command errored out with exit status 1:
     command: /tmp/Python-3.8.5-install/bin/python3 /tmp/Python-3.8.5-install/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py prepare_metadata_for_build_wheel /tmp/tmpkq7kaw0a
         cwd: /tmp/pip-download-wlya4wbi/scipy
    Complete output (75 lines):
    The Meson build system
    Version: 1.0.0
    Source dir: /tmp/pip-download-wlya4wbi/scipy
    Build dir: /tmp/pip-download-wlya4wbi/scipy/.mesonpy-ip8_p61a/build
    Build type: native build
    Project name: SciPy
    Project version: 1.10.0
    C compiler for the host machine: cc (gcc 8.4.1 "cc (GCC) 8.4.1 20200928 (Red Hat 8.4.1-1)")
    C linker for the host machine: cc ld.bfd 2.30-93
    C++ compiler for the host machine: c++ (gcc 8.4.1 "c++ (GCC) 8.4.1 20200928 (Red Hat 8.4.1-1)")
    C++ linker for the host machine: c++ ld.bfd 2.30-93
    Host machine cpu family: ppc64
    Host machine cpu: ppc64le
    Compiler for C supports arguments -Wno-unused-but-set-variable: YES
    Compiler for C supports arguments -Wno-unused-function: YES
    Compiler for C supports arguments -Wno-conversion: YES
    Compiler for C supports arguments -Wno-misleading-indentation: YES
    Compiler for C supports arguments -Wno-incompatible-pointer-types: YES
    Library m found: YES
    Fortran compiler for the host machine: gfortran (gcc 8.4.1 "GNU Fortran (GCC) 8.4.1 20200928 (Red Hat 8.4.1-1)")
    Fortran linker for the host machine: gfortran ld.bfd 2.30-93
    Compiler for Fortran supports arguments -Wno-conversion: YES
    Checking if "-Wl,--version-script" : links: YES
    Program cython found: YES (/tmp/pip-build-env-sgbnggps/overlay/bin/cython)
    Program python found: YES (/tmp/Python-3.8.5-install/bin/python3)
    Found pkg-config: /usr/bin/pkg-config (1.4.2)
    Program pythran found: YES (/tmp/pip-build-env-sgbnggps/overlay/bin/pythran)
    Run-time dependency threads found: YES
    Library npymath found: YES
    Library npyrandom found: YES
    Found CMake: /data_local/sw/spack/0.17.0/opt/spack/linux-rhel7-power8le/gcc-4.8.5/cmake-3.21.4-t2lf7jyc3qc3wkhc7mf4ska7akugi3ko/bin/cmake (3.21.4)
    Run-time dependency openblas found: NO (tried pkgconfig and cmake)
    Run-time dependency openblas found: NO (tried pkgconfig and cmake)

    ../../scipy/meson.build:134:0: ERROR: Dependency "OpenBLAS" not found, tried pkgconfig and cmake

    A full log can be found at /tmp/pip-download-wlya4wbi/scipy/.mesonpy-ip8_p61a/build/meson-logs/meson-log.txt
    + meson setup --prefix=/tmp/Python-3.8.5-install /tmp/pip-download-wlya4wbi/scipy /tmp/pip-download-wlya4wbi/scipy/.mesonpy-ip8_p61a/build --native-file=/tmp/pip-download-wlya4wbi/scipy/.mesonpy-native-file.ini -Ddebug=false -Doptimization=2
    Traceback (most recent call last):
      File "/tmp/Python-3.8.5-install/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py", line 126, in prepare_metadata_for_build_wheel
        hook = backend.prepare_metadata_for_build_wheel
    AttributeError: module 'mesonpy' has no attribute 'prepare_metadata_for_build_wheel'

    During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
      File "/tmp/Python-3.8.5-install/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py", line 280, in <module>
        main()
      File "/tmp/Python-3.8.5-install/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py", line 263, in main
        json_out['return_val'] = hook(**hook_input['kwargs'])
      File "/tmp/Python-3.8.5-install/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py", line 130, in prepare_metadata_for_build_wheel
        return _get_wheel_metadata_from_wheel(backend, metadata_directory,
      File "/tmp/Python-3.8.5-install/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py", line 159, in _get_wheel_metadata_from_wheel
        whl_basename = backend.build_wheel(metadata_directory, config_settings)
      File "/tmp/pip-build-env-sgbnggps/overlay/lib/python3.8/site-packages/mesonpy/__init__.py", line 1060, in build_wheel
        with _project(config_settings) as project:
      File "/tmp/Python-3.8.5-install/lib/python3.8/contextlib.py", line 113, in __enter__
        return next(self.gen)
      File "/tmp/pip-build-env-sgbnggps/overlay/lib/python3.8/site-packages/mesonpy/__init__.py", line 975, in _project
        with Project.with_temp_working_dir(
      File "/tmp/Python-3.8.5-install/lib/python3.8/contextlib.py", line 113, in __enter__
        return next(self.gen)
      File "/tmp/pip-build-env-sgbnggps/overlay/lib/python3.8/site-packages/mesonpy/__init__.py", line 750, in with_temp_working_dir
        yield cls(source_dir, tmpdir, build_dir, meson_args)
      File "/tmp/pip-build-env-sgbnggps/overlay/lib/python3.8/site-packages/mesonpy/__init__.py", line 632, in __init__
        self._configure(reconfigure=bool(build_dir) and not native_file_mismatch)
      File "/tmp/pip-build-env-sgbnggps/overlay/lib/python3.8/site-packages/mesonpy/__init__.py", line 680, in _configure
        self._meson('setup', *setup_args)
      File "/tmp/pip-build-env-sgbnggps/overlay/lib/python3.8/site-packages/mesonpy/__init__.py", line 657, in _meson
        return self._proc('meson', *args)
      File "/tmp/pip-build-env-sgbnggps/overlay/lib/python3.8/site-packages/mesonpy/__init__.py", line 652, in _proc
        subprocess.check_call(list(args), env=self._env)
      File "/tmp/Python-3.8.5-install/lib/python3.8/subprocess.py", line 364, in check_call
        raise CalledProcessError(retcode, cmd)
    subprocess.CalledProcessError: Command '['meson', 'setup', '--prefix=/tmp/Python-3.8.5-install', '/tmp/pip-download-wlya4wbi/scipy', '/tmp/pip-download-wlya4wbi/scipy/.mesonpy-ip8_p61a/build', '--native-file=/tmp/pip-download-wlya4wbi/scipy/.mesonpy-native-file.ini', '-Ddebug=false', '-Doptimization=2']' returned non-zero exit status 1.
    ----------------------------------------
ERROR: Command errored out with exit status 1: /tmp/Python-3.8.5-install/bin/python3 /tmp/Python-3.8.5-install/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py prepare_metadata_for_build_wheel /tmp/tmpkq7kaw0a Check the logs for full command output.

SciPy/NumPy/Python version information
Any/Any/3.8.5

If you need an offline install two options are either use the wheels if compatible wheel exists or you build scipy yourself.  See https://docs.scipy.org/doc/scipy/dev/contributor/building.html and relevant parts

I'm guessing you're on a cluster. Besides following @ilayn instructions, it seems like you have spack installed. Could you try installing scipy with spack, is the python you're using provided by spack?

The answers here seem sufficient. gh-17743 updates the build instructions. Things should work once OpenBLAS is installed. Or use Spack to install SciPy (package is named py-scipy in Spack) indeed.
I'll close this, since there is no bug and nothing more to fix on our side. Please feel free to ask follow up questions of course @XL64.


BUG | Support Dynamic deployment_circuit_breaker for CODE_DEPLOY

what

The deployment_circuit_breaker option is now a dynamic block with a conditional for the deployment_controller_type value

why

This PR fixes an issue when using CODE_DEPLOY deployment_circuit_breaker option.
Previously, the deployment_circuit_breaker was always included as part of the module. However, the AWS DeploymentCircuitBreaker documentation states":

The deployment circuit breaker can only be used for services using the rolling update (ECS) deployment type that aren't behind a Classic Load Balancer.

Consequently, when using CODE_DEPLOY for deployment_circuit_breaker with this module, the state is consistently out of sync with the remote, which attempts to sync with the remote on every update.

references

AWS DeploymentCircuitBreaker documentation: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DeploymentCircuitBreaker.html

/test all

Any updates on this? Would love to get back to 0 updates on apply soon. 😁
Let me know if you need any changes.

@lgants thanks for bumping and for your contribution! Released as https://github.com/cloudposse/terraform-aws-ecs-alb-service-task/releases/tag/0.65.0

Awesome! Thanks @joe-niland both for merging and for all you do to support cloudposse's top-notch open-source code


More Numpy Funpy

Given points x and y in N dimensions,

return a set of M+2 points so that each point is equidistant on the line representing the shortest path between x and y.

so, for example, in 2 dimensions and given x = (0,0), y = (3,3), M=2, return [(0,0),(1,1),(2,2),(3,3)].
also in 2 dimensions and given x=(0,0), y=(4,2),M=1, return [(0,0),(2,1),(4,2)]

see issue 'more more numpy funpy' for part II

first attempt
punk_y_img = example_images[8]
punk_x_coords = [  7.350558  , -13.799404  ,  -2.4654112 ,  -6.299609  ]
punk_y_coords = [-10.365253  , -11.024603  ,  16.105639  ,   3.2864196 ]

M=20
x = punk_x_coords
y = punk_y_coords
x = zip(np.linspace(x[0],y[0],M),
        np.linspace(x[1],y[1],M),
        np.linspace(x[2],y[2],M),
        np.linspace(x[3],y[3],M),
       )
z_s = np.array(list(x))
#z_s = np.array([[  7.350558  , -13.799404  ,  -2.4654112 ,  -6.299609  ]])
reconst_images = decoder.predict(z_s)
#plt.imshow(reconst_images[8])

fig = plt.figure(figsize=(15, 3))
fig.subplots_adjust(hspace=0.4, wspace=0.4)
for i in range(20):
    img = reconst_images[i]#.squeeze()
    ax = fig.add_subplot(2, n_to_show, i+1)
    ax.axis('off')
    ax.imshow(img)

a random walk between the latent space of two punks.

easier one


Update LICENSE

Hello @laganverma , Thanks for your contribution, but adding more links is more relevant than just editing those texts.
Please consider looking for good interesting links instead :)


fix: gracefully handle unsettable keys during automocking (fix #1671)

Sometimes while automocking we will encounter a property that, for some unknown reason, throws an error when you try to define it. Unfortunately I can't figure out why it errors, so instead I have opted to quietly skip these unsettable properties. If that becomes a problem in the future this can be revisited, but I don't forsee it being an issue since these keys are mostly deeply internal prototype stuff that 99.999% of people don't even know exists, let alone want to mock. Plus, if you really need to have this behavior you can always use __mocks__ or just shim it inline yourself.
Fixes #1671

It feels like we are going into a trap 🤔

deeply internal prototype stuff that 99.999% of people don't even know exists

If we don't copy internal stuff, how can public stuff access it?

If we don't copy internal stuff, how can public stuff access it?

It doesn't need to. The output of the automocking process is an entirely new object with all methods stubbed out. Not spied on, completely overwritten. Therefore the internal implementation of these top-level APIs are irrelevant, since they won't be used anyway, and thus the deeper layers are also irrelevant since they won't actually be used by anything.
I'm sure there will be at least one person at some point who will actually need some of those items mocked, but as I said they can always just make their own mock via the __mocks__ folder and set it up however they need.

It seems that the macos and windows tests timed out, but I don't know why and I can't reproduce it locally. Any ideas?


build failed

hello I was compiling on windows and got this error
thread 'main' panicked at C:\Users\me.cargo\git\checkouts\ctru-rs-1206856f7a5d76bc\4a15ec9\ctru-sys\build.rs:180:10:
called Result::unwrap() on an Err value: Os { code: 3, kind: NotFound, message: "The system cannot find the path specified." }
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish..

Do you have the devkitARM toolchain installed with all the tools? It is possible the path is either wrong or the compiler is actually missing.
Check whether DEVKITARM and DEVKITPRO are variables defined in your environment and whether the path they specify actually contains the needed tools.


Camera permission is asked every time I open the access camera

Thanks for great plugin, I having issue while accessing camera from webview. I have this code in my application to access camera
 return Webview(
                controller,
                permissionRequested: (url, permissionKind, isUserInitiated) =>
                    _onPermissionRequested(
                  url: url,
                  kind: permissionKind,
                  isUserInitiated: isUserInitiated,
                  context: context,
                  isPermissionGranted: isPermissionGranted,
                ),
              );

This code work fine but every time I run this code it is asking for camera permission even if grant the permission.

So it keeps asking per request? I haven’t found any documentation on how long a permission, once granted, is considered valid. Can’t you just cache the user’s decision?

@jnschulze  I tried to cache but It didn't work, when I allow the permission request  for first time and try to open camera it is not opening unless I ask the permission again.

@CodingWithTashi Have you found a solution?

This issue can be fixed within the application it self. In my case, I have fixed it within my packages. If you are interested only with permission, do check this out this PR


Jacoco Aggregation Plugin ExternalSystemException during project configuration

Unable to configure outgoing variant for ArtifactTypeDefinition.BINARY_DATA_TYPE for instrumented android test in the android module. Receiving an exception during sync: stacktrace.txt
Expected Behavior
More descriptive error if the script is wrong. More documentation on integrating custom outgoing variants.
Current Behavior
Unable to pass fileTree for an outgoing variant for ArtifactTypeDefinition.BINARY_DATA_TYPE.
Context

I am trying to set up JaCoCo Report Aggregation Plugin in a project with JVM and Android modules. By providing the missing outgoing variants for Android modules.
Setup with only android unit tests works fine, the problem is attaching android instrumented test execution data. Android instrumented test generates not a single execution data file but separate execution for each test stored under the directory (coverageDirectory).
Steps to Reproduce

I attach an empty project with a single module, which has scripts to configure outgoing variants.
Child module configuration is in /gradle/testCoverage.module.gradle. For root project in /gradle/testCoverage.project.gradle
After opening the project not able to sync. Neither execute :testCodeCoverageReport task.
Tried gradle 7.6 and 8.0.2.
MyApplication7.6.zip
MyApplication8.0.2.zip
Your Environment
Operating system: macOS Ventura 13.2.1
AGP: 7.4.2
Gradle: 7.6 / 8.0.2
Build scan URL: https://scans.gradle.com/s/z5qatslw3dalw (when trying to execute :testCodeCoverageReport task)

Sorry that you're having trouble with Gradle!
Your issue appears to be a question about how to use Gradle. Your question might be answered in Gradle documentation or on our community Slack or forums. Find links to these resources on help.gradle.org.
This might be an issue with the Android Gradle Plugin which is developed by Google and cannot be addressed in the Gradle Build Tool project.
===
Please, ask Android community about integrating jacoco instrumented android tests.