undefined reference to `__imp__cprintf' during build x86_64-w64-mingw32 on Windows

I am trying to build OpenBlas so I can use blas_sgemm() on Windows 10 using x86_64-w64-mingw32. Unfortunately, I keep running across this error, when running the make command. I did not specify any extra arguments.
ar -ru ../../../libopenblas_skylakexp-r0.3.24.a lapacke_cgb_nancheck.o lapacke_cgb_trans.o lapacke_cge_nancheck.o lapacke_cge_trans.o lapacke_cgg_nancheck.o lapacke_cgg_trans.o lapacke_cgt_nancheck.o lapacke_chb_nancheck.o lapacke_chb_trans.o lapacke_che_nancheck.o lapacke_che_trans.o lapacke_chp_nancheck.o lapacke_chp_trans.o lapacke_chs_nancheck.o lapacke_chs_trans.o lapacke_c_nancheck.o lapacke_cpb_nancheck.o lapacke_cpb_trans.o lapacke_cpf_nancheck.o lapacke_cpf_trans.o lapacke_cpo_nancheck.o lapacke_cpo_trans.o lapacke_cpp_nancheck.o lapacke_cpp_trans.o lapacke_cpt_nancheck.o lapacke_csp_nancheck.o lapacke_csp_trans.o lapacke_cst_nancheck.o lapacke_csy_nancheck.o lapacke_csy_trans.o lapacke_ctb_nancheck.o lapacke_ctb_trans.o lapacke_ctf_nancheck.o lapacke_ctf_trans.o lapacke_ctp_nancheck.o lapacke_ctp_trans.o lapacke_ctr_nancheck.o lapacke_ctr_trans.o lapacke_ctz_nancheck.o lapacke_ctz_trans.o lapacke_dgb_nancheck.o lapacke_dgb_trans.o lapacke_dge_nancheck.o lapacke_dge_trans.o lapacke_dgg_nancheck.o lapacke_dgg_trans.o lapacke_dgt_nancheck.o lapacke_dhs_nancheck.o lapacke_dhs_trans.o lapacke_d_nancheck.o lapacke_dpb_nancheck.o lapacke_dpb_trans.o lapacke_dpf_nancheck.o lapacke_dpf_trans.o lapacke_dpo_nancheck.o lapacke_dpo_trans.o lapacke_dpp_nancheck.o lapacke_dpp_trans.o lapacke_dpt_nancheck.o lapacke_dsb_nancheck.o lapacke_dsb_trans.o lapacke_dsp_nancheck.o lapacke_dsp_trans.o lapacke_dst_nancheck.o lapacke_dsy_nancheck.o lapacke_dsy_trans.o lapacke_dtb_nancheck.o lapacke_dtb_trans.o lapacke_dtf_nancheck.o lapacke_dtf_trans.o lapacke_dtp_nancheck.o lapacke_dtp_trans.o lapacke_dtr_nancheck.o lapacke_dtr_trans.o lapacke_dtz_nancheck.o lapacke_dtz_trans.o lapacke_lsame.o lapacke_sgb_nancheck.o lapacke_sgb_trans.o lapacke_sge_nancheck.o lapacke_sge_trans.o lapacke_sgg_nancheck.o lapacke_sgg_trans.o lapacke_sgt_nancheck.o lapacke_shs_nancheck.o lapacke_shs_trans.o lapacke_s_nancheck.o lapacke_spb_nancheck.o lapacke_spb_trans.o lapacke_spf_nancheck.o lapacke_spf_trans.o lapacke_spo_nancheck.o lapacke_spo_trans.o lapacke_spp_nancheck.o lapacke_spp_trans.o lapacke_spt_nancheck.o lapacke_ssb_nancheck.o lapacke_ssb_trans.o lapacke_ssp_nancheck.o lapacke_ssp_trans.o lapacke_sst_nancheck.o lapacke_ssy_nancheck.o lapacke_ssy_trans.o lapacke_stb_nancheck.o lapacke_stb_trans.o lapacke_stf_nancheck.o lapacke_stf_trans.o lapacke_stp_nancheck.o lapacke_stp_trans.o lapacke_str_nancheck.o lapacke_str_trans.o lapacke_stz_nancheck.o lapacke_stz_trans.o lapacke_xerbla.o lapacke_zgb_nancheck.o lapacke_zgb_trans.o lapacke_zge_nancheck.o lapacke_zge_trans.o lapacke_zgg_nancheck.o lapacke_zgg_trans.o lapacke_zgt_nancheck.o lapacke_zhb_nancheck.o lapacke_zhb_trans.o lapacke_zhe_nancheck.o lapacke_zhe_trans.o lapacke_zhp_nancheck.o lapacke_zhp_trans.o lapacke_zhs_nancheck.o lapacke_zhs_trans.o lapacke_z_nancheck.o lapacke_zpb_nancheck.o lapacke_zpb_trans.o lapacke_zpf_nancheck.o lapacke_zpf_trans.o lapacke_zpo_nancheck.o lapacke_zpo_trans.o lapacke_zpp_nancheck.o lapacke_zpp_trans.o lapacke_zpt_nancheck.o lapacke_zsp_nancheck.o lapacke_zsp_trans.o lapacke_zst_nancheck.o lapacke_zsy_nancheck.o lapacke_zsy_trans.o lapacke_ztb_nancheck.o lapacke_ztb_trans.o lapacke_ztf_nancheck.o lapacke_ztf_trans.o lapacke_ztp_nancheck.o lapacke_ztp_trans.o lapacke_ztr_nancheck.o lapacke_ztr_trans.o lapacke_ztz_nancheck.o lapacke_ztz_trans.o lapacke_make_complex_float.o lapacke_make_complex_double.o
ranlib ../../../libopenblas_skylakexp-r0.3.24.a
make[3]: Leaving directory 'D:/Users/superkogito/Desktop/workspace/OpenBLAS-0.3.24/lapack-netlib/LAPACKE/utils'
make[2]: Leaving directory 'D:/Users/superkogito/Desktop/workspace/OpenBLAS-0.3.24/lapack-netlib/LAPACKE'
make[1]: Leaving directory 'D:/Users/superkogito/Desktop/workspace/OpenBLAS-0.3.24/lapack-netlib'
make[1]: Entering directory 'D:/Users/superkogito/Desktop/workspace/OpenBLAS-0.3.24/exports'
make[1]: warning: -j8 forced in makefile: resetting jobserver mode.
./gensymbol win2k    x86_64 dummy 0 0 0 0 0 0 "" "" 1 0 1 1 1 1 > libopenblas.def
cc -O2 -DSMALL_MATRIX_OPT -DMS_ABI -DMAX_STACK_ALLOC=2048 -Wall -m64 -DF_INTERFACE_GFORT -DSMP_SERVER -DNO_WARMUP -DMAX_CPU_NUMBER=8 -DMAX_PARALLEL_NUMBER=1 -DBUILD_SINGLE=1 -DBUILD_DOUBLE=1 -DBUILD_COMPLEX=1 -DBUILD_COMPLEX16=1 -DVERSION=\"0.3.24\" -msse3 -mssse3 -msse4.1 -mavx -mavx2 -march=skylake-avx512 -fno-asynchronous-unwind-tables -mavx2 -UASMNAME -UASMFNAME -UNAME -UCNAME -UCHAR_NAME -UCHAR_CNAME -DASMNAME=dllinit -DASMFNAME=dllinit_ -DNAME=dllinit_ -DCNAME=dllinit -DCHAR_NAME=\"dllinit_\" -DCHAR_CNAME=\"dllinit\" -DNO_AFFINITY -I.. -c -o dllinit.obj -s dllinit.c
ranlib ../libopenblas_skylakexp-r0.3.24.a
cc -O2 -DSMALL_MATRIX_OPT -DMS_ABI -DMAX_STACK_ALLOC=2048 -Wall -m64 -DF_INTERFACE_GFORT -DSMP_SERVER -DNO_WARMUP -DMAX_CPU_NUMBER=8 -DMAX_PARALLEL_NUMBER=1 -DBUILD_SINGLE=1 -DBUILD_DOUBLE=1 -DBUILD_COMPLEX=1 -DBUILD_COMPLEX16=1 -DVERSION=\"0.3.24\" -msse3 -mssse3 -msse4.1 -mavx -mavx2 -march=skylake-avx512 -fno-asynchronous-unwind-tables -mavx2 -UASMNAME -UASMFNAME -UNAME -UCNAME -UCHAR_NAME -UCHAR_CNAME -DASMNAME= -DASMFNAME=_ -DNAME=_ -DCNAME= -DCHAR_NAME=\"_\" -DCHAR_CNAME=\"\" -DNO_AFFINITY -I..  libopenblas.def dllinit.obj \
-shared -o ../libopenblas.dll -Wl,--out-implib,../libopenblas.dll.a \
-Wl,--whole-archive ../libopenblas_skylakexp-r0.3.24.a -Wl,--no-whole-archive -Lc:/programdata/chocolatey/lib/mingw/tools/install/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/12.2.0 -Lc:/programdata/chocolatey/lib/mingw/tools/install/mingw64/bin/../lib/gcc -Lc:/programdata/chocolatey/lib/mingw/tools/install/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/12.2.0/../../../../x86_64-w64-mingw32/lib/../lib -Lc:/programdata/chocolatey/lib/mingw/tools/install/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/12.2.0/../../../../lib -Lc:/programdata/chocolatey/lib/mingw/tools/install/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/12.2.0/../../../../x86_64-w64-mingw32/lib -Lc:/programdata/chocolatey/lib/mingw/tools/install/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/12.2.0/../../..  -lgfortran -lmoldname -lmingwex -lmsvcrt -lquadmath -lm -lmoldname -lmingwex -lmsvcrt -lpthread -lmoldname -lmingwex -lmsvcrt  -defaultlib:advapi32 -lgfortran -defaultlib:advapi32 -lgfortran
C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.1.0/../../../../x86_64-w64-mingw32/bin/ld.exe: ../libopenblas_skylakexp-r0.3.24.a(memory.obj):memory.c:(.text+0x6c2): undefined reference to `__imp__cprintf'
C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.1.0/../../../../x86_64-w64-mingw32/bin/ld.exe: ../libopenblas_skylakexp-r0.3.24.a(memory.obj):memory.c:(.text+0x7f7): undefined reference to `__imp__cprintf'
C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.1.0/../../../../x86_64-w64-mingw32/bin/ld.exe: ../libopenblas_skylakexp-r0.3.24.a(xerbla.obj):xerbla.c:(.text+0x13): undefined reference to `__imp__cprintf'
collect2.exe: error: ld returned 1 exit status
make[1]: *** [Makefile:124: ../libopenblas.dll] Error 1
make[1]: Leaving directory 'D:/Users/superkogito/Desktop/workspace/OpenBLAS-0.3.24/exports'
make: *** [Makefile:146: shared] Error 2

I already tried make clean and installing the mingw dependencies as mentioned here, but no luck:

https://github.com/OpenMathLib/OpenBLAS/issues/658
https://github.com/OpenMathLib/OpenBLAS/issues/1306

My GCC version is:
gcc --version
gcc.exe (MinGW-W64 x86_64-ucrt-posix-seh, built by Brecht Sanders) 12.2.0

Any help on how to solve this is appreciated.
Thank you.

did you install the gcc-fortran part(s) of mingw as well ?

Yes as discussed https://github.com/OpenMathLib/OpenBLAS/issues/1306, unless I am missing something.

gfortran dev package looks to be a different version ?

I updated the MinGW installation manager catalogue but no updated/newer version is available. I will remove the dev version and try to build again, although I don't think this should affect my installation since as mentioned https://github.com/OpenMathLib/OpenBLAS/issues/1306

It should skip all fortran components (LAPACK) in absence of compiler and hopefully wrongly set compiler too.

And I already tried the build without the fortran installation and it also failed.
I should mention that I am running this on my work pc which includes some corporate firewall and proxy, can these possibly affect the build process?

Corporate network profile might be on a network share or under aggressive virus control.
Try c:/users/public as stable local filesystem.
Or setting MAKE_NB_JOBS=2 to avoid microbe races on shares

Can you please elaborate on this. I am not sure I understand it

Try c:/users/public as stable local filesystem.

errno 1 is permission denied which means that your admin is better positioned to help. It can be your profile syncing to a file server or antivirus nagging you with background scan.  You can have mingw cross-compiler in linux if you cannot get normal filesystem on windows.

I get the feeling that all the discussion around the fortran part of mingw in earlier issues were either misunderstandings or symptoms of an incomplete or broken installation of the cross-compiler in general. _cprintf is specifically declared to override the generic printf (in drivers/other/memory.c and drivers/other/xerbla.c) when compiling with mingw like this
https://github.com/martin-frbg/OpenBLAS/blob/425bcc1f8bc36571221e9babf8aea0b66ad03fba/driver/others/xerbla.c#L43-L47
#if defined(OS_WINDOWS) && (defined(__MINGW32__) || defined(__MINGW64__))
#include <conio.h>
#undef  printf
#define printf	_cprintf
#endif

and this code fragment appears to be unchanged from the original GotoBLAS of >15 years ago. My (older) mingw-gcc on Linux which I use to cross-build the Windows packages appears to provide the implementations in its libmsvcrt , so maybe this is a question of setting up the library paths for linking ?

Suspect that the ucrt in your gcc version string may be the key here - perhaps it would be worth a try to remove the above five lines from both files.

flawless build with "MinGW-W64 x86_64-ucrt-mcf-seh, built by Brecht Sanders) 13.2.0", builds with "your" MinGW-W64 x86_64-ucrt-posix-seh, built by Brecht Sanders) 12.2.0 are currently timing out in the Azure cloud before they reach the link step

Built fine with MinGW-W64-x86_64-ucrt-posix-seh as well (once I reduced the build size to fit into Azure's time constraint).
So it is looking like an installation problem on your end again - all I did was download the single prebuilt archive from Brecht Sanders' site, unpack it somewhere and prepend its installation directory to the windows PATH variable.
    mkdir winlib
      cd winlib
      curl -L -o mingw64.zip https://github.com/brechtsanders/winlibs_mingw/releases/download/12.2.0-16.0.0-10.0.0-ucrt-r5/winlibs-x86_64-posix-seh-gcc-12.2.0-mingw-w64ucrt-10.0.0-r5.zip
      dir
      tar -xf mingw64.zip
      set PATH=%cd%\mingw64\bin;%PATH%

And I notice now that all the MinGW packages shown in your screenshot appear to be much older versions (4.8.2, 6.3.0) than the 12.2.0 from gcc -v (or even 13.1.0 - from the path names in your first make output ?) in your first post. Either you showed output from multiple computers, or your system has multiple (and probably conflicting?) mingw/gcc versions installed, only some of which show up in MinGW's installation manager. As Brecht Sanders' packages are "simply unpack and use", they will probably not show up anywhere in either MinGW's or Windows' installed software list. Make sure that you have the one you want to use first in your PATH

And @brada4 I'm fairly sure the "error 1" reported by mingw32-make is simply the Unix-style exit code "failure" (of the preceding MinGW ld call) and not something from any Windows component. (I'm not even aware of there being a unique definition of this code across all Windows components, where did you get the "permission denied" from ?)

I think this could be related to my setup, I have a very weird hybrid setup at this point and I am not even sure where to start. I tried to build within CLion but I got a different errors. However, finally I managed to install a compatible OpenBLAS from here https://packages.msys2.org/package/mingw-w64-x86_64-openblas?repo=mingw64
This was a much simpler install and worked like a charm. It is not built from source but it works enough for my use case.
Since my problem cannot be reproduced and seems more of a my setup issue. I suggest closing this for now. If I needed help again, I will open a new one.
Thank you so much for your efforts and help over the last couple of days, you made this debugging feel less overwhelming. ❤

And at least I know now that OpenBLAS compiles with the ucrt variant of mingw-gcc as well

Would it be useful to add a runner to the existing GitHub-CI to build OpenBLAS for that environment of MSYS2?

Thought about that, but it did not strike me as that different from the existing builds in the end.

Given that projects start to switch to UCRT for binaries that they distribute for Windows, and the fact that mingw-w64 switched their default CRT to UCRT, we could also replace the MINGW64 runners with UCRT64 ones.
The main (only?) difference is that that environment uses binaries that link to the UCRT instead of the MSVCRT:
https://www.msys2.org/docs/environments/

Yes, guess it would make sense to replace the MINW64 ones with UCRT64, given that old-style MSVCRT builds are also covered by Azure and Appveyor. (The alternative would seem to be to consolidate all these in runners, if the performance is consistently better - but Appveyor is only used for really ancient gcc builds anyway, not sure if these would fit in with the gh job matrix)

(The alternative would seem to be to consolidate all these in runners, if the performance is consistently better - but Appveyor is only used for really ancient gcc builds anyway, not sure if these would fit in with the gh job matrix)

MSYS2 follows a rolling release model. That means that the compilers are always quite recent versions. I don't know if there is a way to install older versions of the compilers using MSYS2. (I'd guess there isn't.)
(If that is what you meant...)


Hot reload should be even less verbose

This should be collapsed into one line when you hit "r":
Syncing files to device...                           96ms
Performing hot reload...                             1793ms
Reloaded 260 of 439 libraries.

We have learnt from usability studies that the more verbose our logging, the less people read it, and this leads to them to missing things like "press r to hot reload" entirely.

What should the single line look like?
Hot reload: Syncing files to device (96ms) -> performing hot reload (1793ms) -> reloaded 260 of 439 libraries.

Something like:
Reloading app...                             1793ms

Syncing files (96ms), reloading 260 of 439 libraries (1793ms)

CC @johnmccutchan

I don't think we need to separate the measures of the sync and reload steps, so suggest:
When the reload starts:
Hot reloading app...                              1793ms

When the reload completes:
Hot reloading app... (17 of 460 libraries)        1793ms

I like @mit-mit's suggestion.


Terraform Provider seems to ignore user-data

Description
I am trying to inject commands for cloud-init via ‘user-data’ into a cubeserver.
I have used the commands as heredoc and as base64 encoded string.
Unfortunately, the content is not executed in either case.
It is independent of the image used (I have tried debian:11, debian:12 and ubuntu:24.04).
If you run the script via the data centre, it works perfectly.
Here is the configuration (the script is just an example without much sense):
resource "ionoscloud_cube_server" "server" {
  datacenter_id     = ionoscloud_datacenter.dc.id
  name              = "Server"
  availability_zone = "AUTO"
  template_uuid     = data.ionoscloud_template.template.id
  image_name        = data.ionoscloud_image.image.id
  ssh_key_path      = [ "/root/.ssh/id_ionos_ecdsa.pub" ]
  volume {
    name            = "Vol-Server"
    disk_type       = "DAS"
    user_data       = "IyEvYmluL2Jhc2gKZWNobyAiSGVsbG8gd29ybGQhIiA+L3Vzci9sb2NhbC9zcmMvbW90ZApjaG1vZCA2NDQgL3Vzci9sb2NhbC9zcmMvbW90ZAo="
  }
  nic {
    lan             = ionoscloud_lan.wan.id
    name            = "Nic WAN"
    dhcp            = true
    ips             = [ "${var.public-ip}" ]
    firewall_active = false
  }
}

Expected behavior
a file, e.g. in /usr/local/src
Environment
Terraform version:
Terraform v1.9.7
on linux_amd64

Provider version:
6.5.7

OS:
debian 11.11

Configuration Files
see above
How to Reproduce
sh> terraform apply
Error and Debug Output

vm created in data centre:

  sh> cat cloud-init.log | grep user-data
  2024-10-07 11:35:30,676 - util.py[DEBUG]: Reading from /var/lib/cloud/seed/nocloud/user-data (quiet=False)
  2024-10-07 11:35:30,676 - util.py[DEBUG]: Read 147 bytes from /var/lib/cloud/seed/nocloud/user-data
  2024-10-07 11:35:31,294 - util.py[DEBUG]: Writing to /var/lib/cloud/instances/nocloud/user-data.txt - wb: [600] 147 bytes
  2024-10-07 11:35:31,296 - util.py[DEBUG]: Writing to /var/lib/cloud/instances/nocloud/user-data.txt.i - wb: [600] 453 bytes

vm created with terraform:

  sh> cat cloud-init.log | grep user-data
  2024-10-07 10:48:50,801 - util.py[DEBUG]: Reading from /var/lib/cloud/seed/nocloud/user-data (quiet=False)
  2024-10-07 10:48:50,801 - util.py[DEBUG]: Read 0 bytes from /var/lib/cloud/seed/nocloud/user-data
  2024-10-07 10:48:51,356 - util.py[DEBUG]: Writing to /var/lib/cloud/instances/nocloud/user-data.txt - wb: [600] 0 bytes
  2024-10-07 10:48:51,358 - util.py[DEBUG]: Writing to /var/lib/cloud/instances/nocloud/user-data.txt.i - wb: [600] 308 bytes

We will fix this. Meanwhile, if you need this urgently, you can create a ionoscloud_server with

resource "ionoscloud_server" "server" {
  datacenter_id     = ionoscloud_datacenter.dc.id
  name              = "Server"
  type                = "CUBE"
  availability_zone = "AUTO"
  template_uuid     = data.ionoscloud_template.template.id
  image_name        = data.ionoscloud_image.image.id
  ssh_key_path      = [ "/root/.ssh/id_ionos_ecdsa.pub" ]
  volume {
    name            = "Vol-Server"
    disk_type       = "DAS"
    user_data       = "IyEvYmluL2Jhc2gKZWNobyAiSGVsbG8gd29ybGQhIiA+L3Vzci9sb2NhbC9zcmMvbW90ZApjaG1vZCA2NDQgL3Vzci9sb2NhbC9zcmMvbW90ZAo="
  }
  nic {
    lan             = ionoscloud_lan.wan.id
    name            = "Nic WAN"
    dhcp            = true
    ips             = [ "${var.public-ip}" ]
    firewall_active = false
  }
}

Perfect. That's the solution. Many thanks for the quick help!

Fixed.


scss support

Any chance of getting the bower-installed font-mfizz to generate a scss directory/files beside less?

Hi Kevin,
The project primarily relies on the fontcustom project to help build the
font & css.  I haven't taken a look in awhile to see if fontcustom can
output other formats such as scss.  Another user mentioned an alternative
to fontcustom using gulp.  I'm open to PRs!
-Joe
On Tue, May 17, 2016 at 8:20 PM, Kevin Funk<EMAIL_ADDRESS>wrote:

Any chance of getting the bower-installed font-mfizz to generate a scss
directory/files beside less?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/fizzed/font-mfizz/issues/42

It looks like fontcustom does easily support scss, so I'll look into it and see if I can make a PR.
In the meantime, can you explain to me how the .less file is generated? I don't see any config to tell fontcustom to do that, nor do I see it in the repo. However, it sure showed up when i bower installed.


Find/replace with multiple root folders does not exclude ignored files

When doing a find/replace with a single folder open, the files ignored via .gitignore are excluded from the search results. (as expected)
However, when multiple root folders are in use, the previous exclusion doesn't apply and it will search every file for all the root folders. (not respecting the .gitignore anymore)
I'm not sure if this is related directly to #5728 or not, as I didn't see this issue mentioned there.

Hi @dominicbarnes, it was already reported in atom/find-and-replace#508, please subscribe there to follow the work on this issue.


Please add support for staging channels

Loading backups with stage channels causes error
Job Failed: Invalid Form Body
user_limit[NUMBER_TYPE_MAX]: int value should be less than or equal to 99.
ID: loadChannel::guild.channels.create::Собрание
DiscordAPIError[50035]: Invalid Form Body
user_limit[NUMBER_TYPE_MAX]: int value should be less than or equal to 99.
    at handleErrors (C:\Users\V3land\Documents\backup_test\node_modules\@discordjs\rest\dist\index.js:722:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async SequentialHandler.runRequest (C:\Users\V3land\Documents\backup_test\node_modules\@discordjs\rest\dist\index.js:1120:23)
    at async SequentialHandler.queueRequest (C:\Users\V3land\Documents\backup_test\node_modules\@discordjs\rest\dist\index.js:953:14)
    at async _REST.request (C:\Users\V3land\Documents\backup_test\node_modules\@discordjs\rest\dist\index.js:1266:22)
    at async GuildChannelManager.create (C:\Users\V3land\Documents\backup_test\node_modules\discord.js\src\managers\GuildChannelManager.js:171:18) {
  requestBody: {
    files: undefined,
    json: {
      name: 'Собрание',
      topic: undefined,
      type: 2,
    }
  },
  rawError: {
    message: 'Invalid Form Body',
    code: 50035,
    errors: { user_limit: [Object] }
  },
  code: 50035,
  status: 400,
  method: 'POST',
  url: 'https://discord.com/api/v10/guilds/1195297326730842182/channels'
}

In backup file there is a
userLimit: 10000 value, which I think is default for stage channels

Hey @TuskarMA, Would you mind sharing the stage channel backup data? The channel type in the stack trace appears to be a normal voice channel, If you can provide some backup data to check with that would be helpful in resolving this issue.

Hey @TuskarMA, thanks for opening this issue. I just added support for Stage channels and released it in v0.7.0. Feel free to open another issue if you have any more problems!


DataFrame API Na(), Read(), JsonFile() and Map()

Add DataFrame.Na(), DataFrameNaFunctions and samples & unit tests
Add SqlContext.Read(), DataFrameReader and samples & unit tests
SqlContext.JsonFile(path, schema) and samples
Column.Cast()
DataFrame.Map() and samples & unit tests
Minor changes to some samples.

The root cause for the failed travis build has already been figured out. After the fix is checked in, will trigger this travis build again.

LGTM

Current coverage is 44.91%

Merging #175 into master will increase coverage by +0.19% as of 3c32f21

@@            master    #175   diff @@
======================================
  Files           41      45     +4
  Stmts         3931    4157   +226
  Branches       365     380    +15
  Methods          0       0
======================================
+ Hit           1758    1867   +109
- Partial        113     120     +7
- Missed        2060    2170   +110

Review entire Coverage Diff as of 3c32f21

Powered by Codecov. Updated on successful CI builds.


Bumpversion

Fixes #14
bozo bump-version major
bozo bump-version minor
bozo bump-version patch
bumping any part sets the less significant parts to 0. major changes minor of 3 to 0 for example.
Bumping is only possible if the git index is empty (no pending files). This is so the version bump can be added to the index and committed as part of the bozo command

I think I'd be happy for this to have the command name bump rather than bump-version. I can't see it conflicting mentally with any other command. Perhaps could be an alias so you can use both.


Bump gemspec

Regenerates the gemspec. Should fix #139.

can you rebase/merge-master this?

@ryanking rebased


analytics ping when the service calls time out

When a service call (compilation or analysis) times out, we should ping GA to that effect (re: #65).

@devoncarew I think this is done?

yup, closing


[Foundation] Address slice regions that incorrectly fetched from the wrong offset of the backing buffers

Slicing of data incorrectly skipped using the start offset of slice regions in a few APIs; this brings it on par with the expected slice behavior.
Addresses the following issues:
https://bugs.swift.org/browse/SR-4462
https://bugs.swift.org/browse/SR-4473
rdar://problem/31361522

@swift-ci  test

@swift-ci test

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - fb84c7bedce3c81e40fbc6cba48869cde43239cd
Test requested by - @phausler

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - fb84c7bedce3c81e40fbc6cba48869cde43239cd
Test requested by - @phausler

updated to include unit tests that were missing from previous changes

@swift-ci test and merge

@swift-ci please test and merge

@phausler I only see a change in TestData.swift. Is this supposed to be a functionality change, and did that get dropped from the PR?

the functionality was merged previously in another commit

@swift-ci test and merge


Moving least square operator problem...

For the simple test program below, I get an error in MPI_Waitall.  If I switch to the nearest neighbor operator, everything works as expected.
--------------------------------------------------------------------------
[mtb20:88890] *** An error occurred in MPI_Waitall
[mtb20:88890] *** reported by process [343932929,1]
[mtb20:88890] *** on communicator MPI COMMUNICATOR 3 DUP FROM 0
[mtb20:88890] *** MPI_ERR_TRUNCATE: message truncated
[mtb20:88890] *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort,
[mtb20:88890] ***    and potentially your MPI job)
[mtb20:88885] 1 more process has sent help message help-mpi-btl-base.txt / btl:no-nics
[mtb20:88885] Set MCA parameter "orte_base_help_aggregate" to 0 to see all help / error messages

#include <stdlib.h>
#include <string.h>

#include <cstdlib>
#include <Kokkos_Core.hpp>
#include <DTK_NearestNeighborOperator.hpp>
#include <DTK_MovingLeastSquaresOperator.hpp>

using Space=Kokkos::HostSpace;

int main(int argc, char* argv[]) {

  MPI_Comm transfer_comm;

  MPI_Init(&argc, &argv);
  Kokkos::ScopeGuard s(argc,argv);
  int nc = 27;

  MPI_Comm_dup(MPI_COMM_WORLD, &transfer_comm);
  if (transfer_comm == MPI_COMM_NULL) return 1;
  int this_rank;
  MPI_Comm_rank(transfer_comm,&this_rank);

  Kokkos::View<double*,Space> temp0;
  Kokkos::View<double*,Space> temp1;
  Kokkos::View<double**,Kokkos::LayoutRight,Space> coord0;
  Kokkos::View<double**,Kokkos::LayoutRight,Space> coord1;

  if (this_rank==0) {
    temp0 = Kokkos::View<double*,Space>("temp0",nc);
    coord0 = Kokkos::View<double**,Kokkos::LayoutRight,Space>("coord0",nc,3);
    //coord1 = Kokkos::View<double**,Kokkos::LayoutRight,Space>("coord0",0,3);
    for (int i = 0; i < nc; ++i) temp0(i) = 1.0;
    int cnum = 0;
    for (int i = 0; i < 3; ++i){
      for (int j = 0; j < 3; ++j) {
        for (int k = 0; k < 3; ++k) {
          coord0(cnum,0)=i*.1;
          coord0(cnum,1)=j*.1;
          coord0(cnum,2)=k*.1;
          cnum++;
        }
      }
    }
  }

 if (this_rank==1) {
    temp1 = Kokkos::View<double*,Space>("temp0",nc);
    coord1 = Kokkos::View<double**,Kokkos::LayoutRight,Space>("coord1",nc,3);

    //coord0 = Kokkos::View<double**,Kokkos::LayoutRight,Space>("coord0",0,3);
    int cnum = 0;
    for (int i = 0; i < 3; ++i){
      for (int j = 0; j < 3; ++j) {
        for (int k = 0; k < 3; ++k) {
          coord1(cnum,0)=i*.1;
          coord1(cnum,1)=j*.1;
          coord1(cnum,2)=k*.1;
          cnum++;
        }
      }
    }
  }

  //DataTransferKit::NearestNeighborOperator<Kokkos::HostSpace::device_type> myop(transfer_comm, coord0, coord1);
  DataTransferKit::MovingLeastSquaresOperator<Kokkos::HostSpace::device_type> myop(transfer_comm,coord0,coord1);

  myop.apply(temp0,temp1);

  if (this_rank==1) {
    printf("temp1(0) = %f\n", temp1(0));
  }

  MPI_Comm_free(&transfer_comm);
  MPI_Finalize();
  return 0;
}

Can you try an MPI barrier on transfer_comm right before you free that communicator at the end of main? I want to make sure there's not some kind of barrier missing here.

Can you try an MPI barrier on transfer_comm right before you free that communicator at the end of main? I want to make sure there's not some kind of barrier missing here.

OK maybe that's not it. I'll cross reference this with out unit tests.

@Rombur @masterleinad Matt's problem has sources only on rank 0 and targets only on rank 1. I don't think we have a good test for this one. Matt's test is pretty simple and should be easy to add to the unit tests.

At Stuart's suggestion, if I uncomment the intialization of coord0 and coord1 to 0 length views, things seem to work fine.  Note that the nearest neighbor operator worked fine without  having to initialize these to 0 length.

@Rombur @masterleinad Should we support uninitialized views and assume them to be size 0?

This would have failed with DBC in place (and I think that should be enabled in Debug mode by default).
In general, I would consider any use of uninitialized Kokkos::View objects a user error.

This would have failed with DBC in place (and I think that should be enabled in Debug mode by default).
In general, I would consider any use of uninitialized Kokkos::View objects a user error.

Would you please post a reference to the assertion that you expect would fail?

Would you please post a reference to the assertion that you expect would fail?

https://github.com/ORNL-CEES/DataTransferKit/blob/d7a54fbfa64a6960467ce0bf556956f25c35fe58/packages/Meshfree/src/DTK_MovingLeastSquaresOperator_def.hpp#L38-L41

DataTransferKit is going to be archived.


KendoUI SASS deprecation warning

Laravel Mix Version: 6.0.49
Node Version (node -v): v16.17.0
NPM Version (npm -v): 8.15.0
OS: Ubuntu WSL

Description:
Dart sass warning:
I'm migrating to laravel mix from 5 to 6 with also sass from 1.32.13 to 1.55.0 . I'm using kendoui component and I've many deprecation warning that confuse me in development.
In kendoui community is proposed to hide the warning with the options
 sassOptions: {
          quietDeps: true
}

I've tried many combination to hide this but without success. How can update this options?
Using something like that looks promising but look like I brake the compilation of the template.
mix.webpackConfig({
  rules: [
    {
       test: /\.vue$/,
       use: [
          loader: 'vue-loader', options: { sassOptions: { quietDeps: true } }
       ]
    }
  ]
})

The problem
WARNING in ./resources/js/components/navbar/xxxx.vue?vue&type=style&index=0&id=373334aa&lang=scss&scoped=true (./node_modules/css-loader/dist/cjs.js??clonedRuleSet-12.use[1]!./node_modules/vue-loader/dist/stylePostLoader.js!./node_modules/postcss-loader/dist/cjs.js??clonedRuleSet-12.use[2]!./node_modules/sass-loader/dist/cjs.js??clonedRuleSet-12.use[3]!./node_modules/vue-loader/dist/index.js??ruleSet[0].use[0]!./resources/js/components/navbar/xxxx.vue?vue&type=style&index=0&id=373334aa&lang=scss&scoped=true)
Module Warning (from ./node_modules/sass-loader/dist/cjs.js):
Deprecation Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.

Steps To Reproduce:
Add kendoui element in laravel9 projects

@paraflu why not just fix the Sass division?

Is from kendoui package...

I think the y need to fix that because current sass doesn’t support slash for division anymore.


Revert "Revert "feat: adventure leaderboard""

Reverts OtterClam/otto-app#330

merged in https://github.com/OtterClam/otto-app/pull/332


AmbiguousRuleException: Rules calculate_proportion and compute_coverage are ambiguous for the file results/bed/28  /test/reads/28_1.fastq.gz.proportion.bed.

RDscan end with this error with our data, and dry run give probably the results
Dry run
/mnt/f/RD/RDscan/workflow/rules/novel_discovery.smk:52: SyntaxWarning: invalid escape sequence '\w'
input:
Building DAG of jobs...
Nothing to be done (all requested files are present and up to date).
Our data
AmbiguousRuleException:
Rules calculate_proportion and compute_coverage are ambiguous for the file results/bed/28  /test/reads/28_1.fastq.gz.proportion.bed.
Consider starting rule output with a unique prefix, constrain your wildcards, or use the ruleorder directive.
Wildcards:
calculate_proportion: sample=28  /test/reads/28_1.fastq.gz
compute_coverage: sample=28  /test/reads/28_1.fastq.gz.proportion
Expected input files:
calculate_proportion: results/mosdepth_bed/28  /test/reads/28_1.fastq.gz.regions.bed.gz
compute_coverage: results/mapped/28  /test/reads/28_1.fastq.gz.proportion.bam resources/IS6110.bed
Expected output files:
calculate_proportion: results/bed/28  /test/reads/28_1.fastq.gz.proportion.bed
compute_coverage: results/bed/28  /test/reads/28_1.fastq.gz.proportion.bed

Can you provide your samples sheet?

Dear Dmitry Bespiatykh,
Please find attached the sample sheet
Regards
Dr. Prasad Thomas
Scientist
In-charge National Salmonella Center (Veterinary) and Anaerobe Laboratory
Division of Bacteriology and Mycology
ICAR-Indian Veterinary Research Institute
Izatnagar, Bareilly- 243122
India
Telephone (O)  +91 0581/2312497
(M) +91<PHONE_NUMBER>
On Fri, 9 Feb 2024 at 13:45, Dmitry Bespiatykh @.***>
wrote:

Can you provide your samples sheet?
—
Reply to this email directly, view it on GitHub
https://github.com/dbespiatykh/RDscan/issues/4#issuecomment-1935498648,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BGA7V4L4XQNYOGN4N2QNPSDYSXLJPAVCNFSM6AAAAABDA6O7RKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZVGQ4TQNRUHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

I do not see any attached files. Can you add it via Attach files directly in this GitHub issue thread?

please find the attached, I missed
Run_accession	R1	R2
28  /test/reads/28_1.fastq.gz	/test/reads/28_2.fastq.gz
samples.txt

In the provided file, in the second line, you have two spaces instead of a tab character between 28 and /test/reads/28_1.fastq.gz. Also make sure that the provided path for files exist, in the current state it leads to the root directory, maybe you want to add . before / if files located in the RDscan/test/reads directory. I have attached the
samples.txt file which works on my computer; in my case, files are located in the RDscan/test/reads.

Thanks for the suggestion went further, but again ended up in another error with my files
The error doesnt happen with test fastq files
localrule compute_coverage:
input: results/mapped/28.proportion.bam, resources/IS6110.bed
output: results/bed/28.proportion.bed
log: logs/bedtools/28.proportion.coverage.log
jobid: 1
reason: Missing output files: results/bed/28.proportion.bed
wildcards: sample=28.proportion
resources: tmpdir=/tmp
Waiting at most 5 seconds for missing files.
regards

If you send me your FASTQ files, I can look further into it.

Dear Dmitry Bespiatykh,
I hope you can access the files through the email, through Github, the file
size was an issue
regards
28_1.fastq.gz
https://drive.google.com/file/d/1JP2jFlo1T-phHGFcN3zPiSSGu15XtwXd/view?usp=drive_web
28_2.fastq.gz
https://drive.google.com/file/d/1DY27buU9emHeby70KrDhSjuYiqwHRwop/view?usp=drive_web
Dr. Prasad Thomas
Scientist
In-charge National Salmonella Center (Veterinary) and Anaerobe Laboratory
Division of Bacteriology and Mycology
ICAR-Indian Veterinary Research Institute
Izatnagar, Bareilly- 243122
India
Telephone (O)  +91 0581/2312497
(M) +91<PHONE_NUMBER>
On Fri, 9 Feb 2024 at 16:26, Dmitry Bespiatykh @.***>
wrote:

If you send me your FASTQ files, I can look further into it.
—
Reply to this email directly, view it on GitHub
https://github.com/dbespiatykh/RDscan/issues/4#issuecomment-1935710183,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BGA7V4JOWHCLTX47E2KUTKDYSX6HPAVCNFSM6AAAAABDA6O7RKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZVG4YTAMJYGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

I ran RDscan using your reads and couldn't reproduce your error, everything worked correctly on Linux and macOS. I did make minor changes to the pipeline to fix SyntaxWarning, so you can try to use the latest version.
I also attached the result files for your reads:
RD_known.xlsx
RD_known.bin.txt
RD_known.txt
RD_putative.txt
If the new version still throws an error, send me all log files

Hi, still a different kind of issue,
Same results also in dry run
tried also with also an new to RDscan2 in enviroment.yml file
Log file attatched
2024-02-10T130809.240069.snakemake.log
Building DAG of jobs...
WorkflowError:
InputFunctionException (rule bwa_mem, line 2, /mnt/f/RD/RDscan-1.0.4/workflow/rules/mapping.smk):
Error:
KeyError: '28.proportion'
Wildcards:
sample=28.proportion
Traceback:
File "/mnt/f/RD/RDscan-1.0.4/workflow/rules/common.smk", line 19, in get_fastq
File "/mnt/e/Miniconda3/envs/RDscan2/lib/python3.12/site-packages/pandas/core/indexing.py", line 1192, in getitem
File "/mnt/e/Miniconda3/envs/RDscan2/lib/python3.12/site-packages/pandas/core/indexing.py", line 1432, in _getitem_axis
File "/mnt/e/Miniconda3/envs/RDscan2/lib/python3.12/site-packages/pandas/core/indexing.py", line 1382, in _get_label
File "/mnt/e/Miniconda3/envs/RDscan2/lib/python3.12/site-packages/pandas/core/generic.py", line 4295, in xs
File "/mnt/e/Miniconda3/envs/RDscan2/lib/python3.12/site-packages/pandas/core/indexes/base.py", line 3809, in get_loc (rule bwa_mem, line 2, /mnt/f/RD/RDscan-1.0.4/workflow/rules/mapping.smk)
MissingInputException: Missing input files for rule bwa_mem:
output: results/mapped/28.bam, results/mapped/28.bam.bai
wildcards: sample=28
affected files:
/test/reads/28_1.fastq.gz
/test/reads/28_2.fastq.gz

The error indicates that the files are not accessible at the specified file path, try using the absolute path (in terminal go to the location of 28_*.fastq.gz, type pwd and use that path). Also try ls /test/reads/ does it print 28_1.fastq.gz and 28_2.fastq.gz?

Resolved,
As suggested was not having access to files with faulty path
Thanking again for prompt respone and help


RG353V Display Timings still offer 120Hz?

Describe the Issue (If applicable)
Estimated Screen Refresh Rate in Retroarch suggests the display is running timings at 60Hz, and behavior with black frame insertion seems to confirm this. Emulation station lists the panel version as 1, so as I understand it, it should be running at 120Hz. There used to be a setting to use the stock Anbernic timings, but that option has since been removed due to "no longer being necessary," as the new DTBs are apparently able to support both v1 and v2 screens. Does this mean that v1s are meant to run at 120Hz, or are both screens now just locked to 60Hz? If it is the latter, being able to use 120Hz timings does not feel like a feature that is "no longer necessary."
What device are you using?
RG353V
What version of ArkOS are you on?
v2.0 (01/27/2024)
I also manually updated to this release's DTBs.

The screen was never 120Hz.  It was something like 124HZ which many complained caused jerky movement.  That was fixed by some other community members and done away with.  If you'd like to try the original hold refresh, you'd have to build the dtb without the changes.  So this commit here:  https://github.com/christianhaitian/RG353VKernel/commit/54605c6b0226f2d3fecbf188aec17c72d30a5b59


Use UTC for end time, bump dependencies

Closes: https://github.com/byu-oit/github-action-start-standard-change/issues/29
Closes: #18

Looking at the results in staging, we only mostly fixed this:

Looks like we still have a timezone mismatch with the work-start value that we get as an output from github-action-start-standard-change.

I'd rather transmit the time in UTC over the wire, so I'll fix it over in that repo.


module build failed v3.1.6

When upgrading from 3.1.5 to 3.1.6, I get this error:
Error: Module build failed (from ./node_modules/favicons-webpack-plugin/lib/fa  vicons.js):
3:11:45 PM:   TypeError: (config.html[platform] || []).map is not a function

I have the same problem, even on version 3.1.5 (freshly installed). I reckon this must be something to do with dependency APIs having changed.

Have you seen this https://github.com/itgalaxy/favicons/issues/268? Hopefully there will soon be a fix! Meanwhile, I've done what was suggested, ie. $ npm install itgalaxy/favicons#v5.4.0, and this works.

Indeed the fix in itgalaxy/favicons should be available today. I'll see tomorrow if I need to release a new version of gatsby-favicon-plugin.

Has the issue been resolved yet? I am getting the same error here

It seems that we're waiting for this PR https://github.com/itgalaxy/favicons/pull/271 to be merged. As soon as it is done, it should work again.

Thank you for the update!

Looks like that has been merged now @julien1619 👍

Yes, you're right @spences10 ! Normally, you just have to update the npm packages to make it work again. As soon as someone else here can confirm that the bug is now gone, I'll close this issue.

Oh, so, we just need to update gatsby-plugin-favicon?
Has there been a release? I'm on mobile now but can try kick off another netlify build and confirm that way if needed.

@spences10 The itgalaxy/favicons is only pinned by your package-lock.json, so running npm update should do the trick.

Running npm update didn't work for me. I uninstalled, then installed the plugin

@janetrimmer Do you have the version of favicons as specified in your package-lock.json before, after npm update and after reinstall?

Yeah, didn't work for me either :'(

For some reason, I initially had problems running npm update. (Permissions issue). When I finally got it running, it didn't alter the version of favicons in package-lock.json.
Before uninstalling  gatsby-plugin-favicon, the version of favicons in package-lock.json was 5.4.0. After installing the plugin again, the version became 5.4.1 and gatsby now works for me!

Okay I've just read the npm doc again and npm update will only check top level dependencies. npm --depth 4 update should update it correctly.

I upgraded my package as well, I'm using Yarn

I can confirm that removing and reinstalling gatsby-plugin-favicon (using yarn) solves the issue. Didn't try yarn upgrade.


test(bindings/C): add valgrind test into C bindings test

The memory management in C binding is a tough thing. Since many other bindings depend on this, we'd better make it right.
Note: Valgrind is only available on linux machine.

Wouldn't ASan be a more viable cross-platform alternative?


[Bug]: DevHome & WindowsTerminal not updating

The problem
Does not find any updates:
PS C:\Program Files\Winget-AutoUpdate> .\Winget-Upgrade.ps1
#################################################################
11/25/2024 - CHECK FOR APP UPDATES (User context)
#################################################################
14:25:41 - Notification Level: SuccessOnly. Notification Language: English
14:25:41 - Checking internet connection...
14:25:41 - Connected !
14:25:41 - WAU uses Black List config
14:25:41 - -> Successsfully loaded default excluded apps list.
14:25:41 - Checking application updates on Winget Repository...
14:25:42 - No new update.
14:25:42 - End of process!
Running winget directly does:
PS C:\Program Files\Winget-AutoUpdate> winget upgrade
Name             Id                        Version      Available    Source
Dev Home         Microsoft.DevHome         0.1800.640.0 0.1901.687.0 winget
Windows Terminal Microsoft.WindowsTerminal 1.21.2911.0  1.21.3231.0  winget
2 upgrades available.
What version of WAU has the issue?
2.1.0
What version of Windows are you using (ex. Windows 11 22H2)?
Win11 23H2
What version of winget are you using?
<IP_ADDRESS>
Log information
no log folder

Additional information
No response

It's working now after I setup the listpath


Set default VirtualBox disk size to 200GB

As commented in this pull request to Docker Toolbox: https://github.com/docker/toolbox/pull/203 the default disk size for a Docker Machine in VirtualBox is set to 20GB, it could be useful to set that default to 200GB.
I edited the code based on this comment: https://github.com/docker/toolbox/pull/203#issuecomment-144593368 by @SydOps, who nailed down where that default was set.
I submit this pull request as asked by @mchiang0610 and @nathanleclaire in other comments in that PR (https://github.com/docker/toolbox/pull/203#issuecomment-150402370).
If that other PR seems to work for Docker Toolbox users and don't rise any additional issues and if you see fit, you may consider merging this PR to update the default Docker-Machine VirtualBox disk size to 200GB.

NOT LGTM until we see how setting the Toolbox default goes

^ yes @nathanleclaire let's see the results from separated Toolbox test first.

@tiangolo
Seems there are more defaultDiskSize setting in this repository.
https://github.com/docker/machine/search?utf8=✓&q=defaultdisksize&type=Code
if we change it for VirtualBox, we should change the rest vm as well.

OK, thanks @SydOps, I see there are several of those variables with the same default size, but some have very low values: "google", "exoscale" and "softlayer", I don't know the internals of any of those other drivers and which problems could arise.
Also, if any of those other drivers actually allocate the physical disk size from the beginning, that would probably be a problem. As VirtualBox has a dynamic disk size limited by the creation disk size but that allocates only about 200MB initially, I see how it could work and wouldn't be a problem, but for the others I'm not sure.
I would prefer to ask @nathanleclaire what we should do. I know this isn't even approved, but I would like to know if I should update this PR including any of those other drivers' default disk size and which of them.

As I said before, NOT LGTM until we see the results from the ToolBox.  This is a really big setting to be playing around with, and if we make something dangerous the default in Machine, we're in a LOT of trouble.  Let's wait a few months and see.


also run node.js 6 CI in worker pool

What kind of change does this PR introduce?
CI

Summary

Does this PR introduce a breaking change?
no

Other information

@niieani This seem to work and is faster. What was the reason to not do that?

@sokra There are more random errors on node 6 when using parallel tests because of resource limit on Travis/Appveyor.

Ah I see let me test that

Any plan to fix that in jest or do you want to wait until node.js is dead?

No idea what was the issue. It just hangs. No idea how to debug it either...
Maybe a bug in jest, maybe in node.

Oddly, all passed now. Maybe I was running into that in combination with something else? Maybe when there were actual errors it was hanging? I don't remember exactly, just know it was hard to debug.

Ironically node.js 10 is hanging and node.js 6 worked fine...

😕

(copied from slack)
Just spoke with @SimenB from the jest team, he suggested adding the --forceExit as a workaround. For debugging it, he also mentioned as worth trying to add https://github.com/mafintosh/why-is-node-running and see what might be causing the process to be hanging after the tests end.

node.js 8 is also hanging here: https://ci.appveyor.com/project/sokra/webpack/build/1.0.7520/job/p6bqee96aelymyhv

It seem to be a general jest problem not bound to node.js version

For this PR I'm going to merge it since the problem is independent of it.

@sokra it was hanging on that Node 8 one you cited because of an internal error though:
(node:1060) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'spies' of undefined
(node:1060) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)

This is why I added the asyncSuite.disabled = true, but I'll have to investigate and fix in jest if possible.


Better log parsing in LSVMBUS test

Validate the test result better with the lsvmbus log. Make sure of the test result with lsvmbus log.
The ask is to copy the lsvmbus.log file.
Script is https://github.com/LIS/LISAv2/blob/master/Testscripts/Linux/LSVMBUS.sh

Created a new feature request to handle new requirement for collecting logs in https://github.com/LIS/LISAv2/issues/524


dark theme more grey

in latest version you add more black colors to dark theme. i prefer more grey like were before. For daylight its better to use grey colors. Night mode already has black colors, why you change it for dark theme. Is it possible to get those grey colors before latest update?
Maybe give additional option. Thx in advance.

I actually like it the way it is, but maybe there could be configuration. Chrome, especially mobile, does not allow for a lot of customization, so it would be lot of work to add it in.

#101


About /dist build folder

Yes, "ng serve" will start webpack-dev-server to run application, i also tried to run "ng build" for my angular 4 application to generate the /dist folder for build purpose, but in my app folder i don't see any /dist folder.
Is there any other way ?

Please use npm run build command.. Also,if it is not an issue with the component, please do not raise an issue here. Please send a mail for any consulting purposes.

Can we use gulp for angular 4 project instead of "ng serve"..?

Yes. Build tools are developers discretion.

is there any way to find sample projects of Angular 4 using gulp

I can do that. But would charge a consulting fee. If interested you can
contact me at<EMAIL_ADDRESS>or +91-9902384179
On Fri, Nov 17, 2017 at 10:25 PM, policz<EMAIL_ADDRESS>wrote:

is there any way to find sample projects of Angular 4 using gulp
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/CuppaLabs/angular2-multiselect-dropdown/issues/93#issuecomment-345300203,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADxjoHfPXByy1SL2FvgzJzSQ6fk19ls2ks5s3bqSgaJpZM4QiKIs
.

--
Thanks & Regards
Pradeep Kumar Terli
Bangalore, India
https://cuppalabs.github.io


Buildkite: don't cache stack logs

Overview
The stack build/test logs from old builds were cluttering up the buildkite artifacts list.
Comments
Tested with using ghci in the .buildkite directory then inspecting archive contents.
λ> :l rebuild.hs
[1 of 1] Compiling Main             ( rebuild.hs, interpreted )
Ok, one module loaded.
Collecting type info for 1 module(s) ...
λ> cd ".."
λ> saveStackWork (CICacheConfig "/tmp/cache" "/home/rodney/.stack" ["master"])
Saving cache /tmp/cache/master/stack-work.tar.lz4 ... wrote 2.135 GB.
λ>

bors r+


Possible data gap for 2024-03-14T10:00:00Z in BOAV

Describe the issue
A time 2024-03-14T10:00:00Z data is missing from "Acceptance volumes by settlement date (BOAV)" and "Acceptance volumes by settlement period (BOAV)" report, settlementPeriod=21
Steps to Reproduce
Steps to reproduce the behavior:

Go to
https://bmrs.elexon.co.uk/api-documentation/endpoint/balancing/settlement/acceptance/volumes/all/{bidOffer}/{settlementDate}
Fields: "settlementDate" = "2024-03-14", "bidOffer" = "bid" (or "bidOffer" = "offer", data is missing for both values)
Click Execute
In data returned look for 2024-03-14T10:00:00Z. Data is missing for 2024-03-14T10:00:00Z settlementPeriod 21

Expected behaviour
I expect there should be at least one record for either bid or offer for 2024-03-14T10:00:00Z settlementPeriod 21
HTTP requests/responses
https://data.elexon.co.uk/bmrs/api/v1/balancing/settlement/acceptance/volumes/all/bid/2024-03-14
https://data.elexon.co.uk/bmrs/api/v1/balancing/settlement/acceptance/volumes/all/offer/2024-03-14
https://data.elexon.co.uk/bmrs/api/v1/balancing/settlement/acceptance/volumes/all/bid/2024-03-14/21
https://data.elexon.co.uk/bmrs/api/v1/balancing/settlement/acceptance/volumes/all/offer/2024-03-14/21
Additional context
I think this is related to https://github.com/elexon-data/insights-issues/issues/36 and https://github.com/elexon-data/insights-issues/issues/37
Checks
Please answer the following questions for yourself before submitting an issue.

[x] I checked the documentation and found no answer
[x] I checked to make sure that this issue has not already been filed
[x] I'm reporting the issue to the correct repository
[x] I'm reporting a problem and not a feature request
[x] I have added the correct labels
[x] I have added screenshots or other relevant evidence (if applicable)

At present this is a genuine gap in data which is being investigated.


Speech partial veneer

Supercedes #2421.

Coverage decreased (-0.1%) to 99.89% when pulling ac55bc1eec465f3ced88e6281b630c324af5c4e4 on lukesneeringer:speech-partial-veneer into 4b5158e64fd80df221bce1d736e530c7e5edec25 on GoogleCloudPlatform:master.


Foreman doesn't start -   terminated by SIGTERM

I just want to start the foreman but I get this:
foreman start
16:46:30 cacapi.1  | started with pid 14149
16:46:30 cmsapi.1  | started with pid 14151
16:46:30 elapi.1   | started with pid 14153
16:46:30 es.1      | started with pid 14155
16:46:30 casc.1    | started with pid 14157
16:46:30 cdnmgmt.1 | started with pid 14159
16:46:30 cdnmgmt.1 | /home/vagrant/.rvm/gems/ruby-1.9.2-p180/gems/foreman-0.61.0/bin/foreman-runner: line 41: /home/vagrant/cdn-management/bin/thin: No such file or directory
16:46:30 cdnmgmt.1 | exited with code 1
16:46:30 system    | sending SIGTERM to all processes
SIGTERM received
16:46:30 cacapi.1  | terminated by SIGTERM
16:46:30 cmsapi.1  | terminated by SIGTERM
16:46:30 elapi.1   | terminated by SIGTERM
16:46:30 es.1      | terminated by SIGTERM
16:46:30 casc.1    | terminated by SIGTERM
Anyone has already experienced this? Thanks.

When I start foreman start i got following
15:01:02 console.1  | started with pid 13446
15:01:02 solr.1     | started with pid 13448
15:01:02 nginx.1    | started with pid 13451
15:01:02 frontend.1 | started with pid 13455
15:01:02 sidekiq.1  | started with pid 13458
15:01:02 nginx.1    | nginx: [emerg] open() "/run/nginx.pid" failed (13: Permission denied)
15:01:02 nginx.1    | exited with code 1
15:01:02 system     | sending SIGTERM to all processes
15:01:02 solr.1     | terminated by SIGTERM
15:01:02 console.1  | terminated by SIGTERM
15:01:02 frontend.1 | terminated by SIGTERM
15:01:02 sidekiq.1  | terminated by SIGTERM
nr-ubuntu@nrubuntu-desktop:~/Desktop/CoreCommerce$ sudo touch /run/nginx.pid nr-ubuntu@nrubuntu-desktop:~/Desktop/CoreCommerce$ sudo chmod -R 777 /run/nginx.pid
nr-ubuntu@nrubuntu-desktop:~/Desktop/CoreCommerce$ foreman start
15:02:55 console.1  | started with pid 13567
15:02:55 solr.1     | started with pid 13569
15:02:55 nginx.1    | started with pid 13572
15:02:55 frontend.1 | started with pid 13576
15:02:55 sidekiq.1  | started with pid 13578
15:02:57 console.1  | [13570] Puma starting in cluster mode...
15:02:57 console.1  | [13570] * Version 2.15.3 (ruby 2.1.2-p95), codename: Autumn Arbor Airbrush
15:02:57 console.1  | [13570] * Min threads: 0, max threads: 16
15:02:57 console.1  | [13570] * Environment: development
15:02:57 console.1  | [13570] * Process workers: 4
15:02:57 console.1  | [13570] * Phased restart available
15:02:57 console.1  | [13570] * Listening on tcp://<IP_ADDRESS>:3000
15:02:57 console.1  | /home/nr-ubuntu/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/puma-2.15.3/lib/puma/binder.rb:234:in initialize': Address already in use - bind(2) for "<IP_ADDRESS>" port 3000 (Errno::EADDRINUSE) 15:02:57 console.1  | 	from /home/nr-ubuntu/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/puma-2.15.3/lib/puma/binder.rb:234:in new'
15:02:57 console.1  | 	from /home/nr-ubuntu/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/puma-2.15.3/lib/puma/binder.rb:234:in add_tcp_listener' 15:02:57 console.1  | 	from /home/nr-ubuntu/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/puma-2.15.3/lib/puma/binder.rb:98:in block in parse'
15:02:57 console.1  | 	from /home/nr-ubuntu/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/puma-2.15.3/lib/puma/binder.rb:84:in each' 15:02:57 console.1  | 	from /home/nr-ubuntu/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/puma-2.15.3/lib/puma/binder.rb:84:in parse'
15:02:57 console.1  | 	from /home/nr-ubuntu/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/puma-2.15.3/lib/puma/cluster.rb:328:in run' 15:02:57 console.1  | 	from /home/nr-ubuntu/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/puma-2.15.3/lib/puma/cli.rb:215:in run'
15:02:57 console.1  | 	from /home/nr-ubuntu/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/puma-2.15.3/bin/puma:10:in <top (required)>' 15:02:57 console.1  | 	from /home/nr-ubuntu/.rbenv/versions/2.1.2/bin/puma:23:in load'
15:02:57 console.1  | 	from /home/nr-ubuntu/.rbenv/versions/2.1.2/bin/puma:23:in `'
15:02:57 console.1  | exited with code 1
15:02:57 system     | sending SIGTERM to all processes
15:02:57 solr.1     | terminated by SIGTERM
15:02:57 nginx.1    | terminated by SIGTERM
15:02:57 frontend.1 | terminated by SIGTERM
15:02:57 sidekiq.1  | terminated by SIGTERM
Anybody Please help me??

how can you solved that?
i have the same errror


Make the firmware documentation more explicit

I would like to make the doc>firmware.rst document [EDIT: currently at the stage of pull request from @leonhma] more complete and accessible. Can
someone review it and see whether my initial steps are correct?
As a beginner in electronics, I have been struggling to interprete the firmware instructions, but a research project I’m doing requires this filament sensor so I'll have to make it work, on a printer too!

REQUIREMENTS

Arduino > V1.8.8
TinyWireS LIbary from https://github.com/nadavmatalon/TinyWireS Download the .ZIP of this library and upload in Tool>Include Library>Add .ZIP library
ATtiny85 Board for Arduino from https://github.com/damellis/attiny Load this in Board Manager, more info in https://www.youtube.com/watch?v=AmpHIHM41Hw&ab_channel=Adio_ -
ISP Programmer like Arduino over ISP -->
https://www.arduino.cc/en/Tutorial/BuiltInExamples/ArduinoISP Set the Arduino Uno as an Arduino As ISP following same video as above. Upload the example sketch ArduinoISP onto the board, this board is now an ISP programmer and you may need a different board as host.

Load the code, wire the ISP program to the ISP port on the sensor and
program it.

This sentence was very obscure to me, so here's how I interpreted and detailed it.
How to flash firmware onto the sensor

Wire the ISP programmer to the ISP port on the sensor.
I think this is different from the host_to_sensor_arduino.PNG wiring drawing because the ISP port is not occupied. So I tried to find the equivalent functions of each pin  on the ISP port and on the Uno ISP programmer.

Type
Pin #   on ISP  port (Sensor)
Arduino Pin (ISP programmer)

MISO
1
12

VCC
2
5V

SCK
3
13

SDA
4
11

RESET
5
10

GND
6
GND

In Tools, Set processor to Attiny85, Clock to Internal 16MHz (current doc says 1MHz but the sensor .ino files all say 16MHz), Programmer to Arduino as ISP
Tools > Burn Bootloader
Open driver.ino and Sketch>Upload with Programmer

Current status
At the moment, with this method, three issues arise:
ISSUE 1. In the doc Firmware, the LED is said to flash twice. For me, it flashed only once.
ISSUE 2. With the driver.ino flashed onto the sensor, when I approach a magnet, no matter what the magnet polarity is, the LED is triggered. I wonder if anyone has the same issue. In the video https://www.youtube.com/watch?v=RYgdLPe_T0c&t=14s&ab_channel=ThomasSanladerer (5:19), the sensor should not be triggered with one of the two magnet faces (and that's the direction you should use to stick on the lever). I have a N45 magnet instead of the N35, but I also have the same problem with a much smaller N45 magnet which should have a smaller force.
ISSUE 3.  With the current state of the documentation, I don't understand when the 5 different firmwares should be used. Could someone clarify the difference between all these firmware in the description and state exactly on which occasion they should be used?
TLDR;
a noob tries to clarify the documentation on the firmware. Can you review up to this stage, and clarify what firmware should be on host and sensor at every step?
PS: I realize this might belongs more to a forum than to GitHub but since I'm not aware of one, please forgive me for posting it here. I hope that maybe my remarks and questions could help to make this project more accessible to others as well.

This is a good a venue as any for comments and feedback. I'll take a moment later on today to review this and I'll try and help you out. Other contributors might beat me to it.

Doesn't look wrong to me. I can't test it though, my parts are still stuck in China 😬. As you saw, I made a pr (ran firmware.md through a converter and added it to the online docs). I don't really know how detailed this is. @CCMCAGP  you can use the MD document in the firmware folder as reference.

Thank you for your answers. I realized what is wrong: at this point it is not driver.ino but calibration.ino that should be loaded onto the sensor. Even better to follow along with the firmware.rst doc, these two files are actually not useful as far as I know. To start calibration, you should upload Host_ee_prog.ino onto the Host and Infidel_release_ee onto the sensor. Then you start seeing the next steps according to firmware.rst.
When I'm through with the calibration I will post a more thorough summary!

Looks good to me. Feel free to open a PR to my repo and then it can be merged back into this one.


Add graph example

This deploys graph + vector against a single Aerospike cluster.

I think until we have an actual example app here I am just going to keep this in a branch and close this PR.


Add version flag in blobfuse driver

Is your feature request related to a problem?/Why is this needed

Describe the solution you'd like in detail

could refer to https://github.com/kubernetes-sigs/azuredisk-csi-driver/pull/70
This feature is a must for v0.1.0-alpha release
Describe alternatives you've considered

Additional context

hi @ashishranjan738 could you work on this? Thanks.

Sure

hi @ashishranjan738 do you have time to work on this? I would like to cut a release when this issue resolved, thanks.

Yeah i can raise today


some UI / editing features that already exist in pull requests should also be available in issues

In "Pull Requests" you can use a feature-rich interface directly inside VSCode to view pull requests, write follow up comments etc.
In Issues I only get a small popup window and a link to leave VSCode.
I would really like to be able to edit existing issues within VScode, as well as view and reply to follow up comments.
The "Pull Requests" part of the plugin is considerably more extensive than the "Issues" part.
For Issues there is no comparable functionality as for Pull Requests yet.
There was a feature request for this, #3433, which was a repeat of an already closed #3428 where the requester provided additional information, and #4023, which was marked as a duplicate of #3433.
All of these have been closed, without even mentioning that there is no intention of giving issues as much love as pull requests.

#3433 was never closed

Duplicate of https://github.com/microsoft/vscode-pull-request-github/issues/3433


Release (signed) Mozilla extension

The extension seems to build properly and can be used in Firefox without problems, but Mozilla requires extensions to be signed, otherwise there's no way to install them (the xpinstall.signatures.required=false override only works on the Developer edition).
Are there any plans to release it officially and sign it? I know there's an old .xpi in the releases, but lots of bugfixes have been submitted since.
The process seems relatively simple: https://developer.mozilla.org/en-US/Add-ons/Distribution

Just made a fork with just a few changes: https://github.com/aisk/hn-special/tree/fit-firefox
(Just changed the application id to avoid conflict, and flattened the zip file layout).
And released on FireFox addon store: https://addons.mozilla.org/zh-CN/firefox/addon/my-hn-special/ for people who want use it right now, and for a basic provement than hn-special can used under firefox now.
Feel free to contact me if hn-special's mantainer want to remove it on firefox store. @gabrielecirulli

Thank you for making the changes @aisk. The problem you'll find if you try to move the extension from Experimental to Signed is that they have been blocking our release because of our usage of innerHTML, as documented in #88. However, I would be happy to accept your changes in a PR to this project.

@PxlBuzzard got it, thanks!

I know this is old, but I wanted to update here and say that v1.4.11 and the latest v1.5.0 are officially signed and available under the Releases tab.


[BUG] Windows install UnicodeDecodeError

pip install mkdocs-static-i18n
in Windows10，output follow errors:
Traceback (most recent call last):
  File "setup.py", line 20, in <module>
    long_description=read("README.md"),
  File "setup.py", line 11, in read
    return (Path(__file__).resolve().parent / fname).read_text()
  File "C:\Program Files\Python38\lib\pathlib.py", line 1233, in read_text
    return f.read()
UnicodeDecodeError: 'gbk' codec can't decode byte 0x80 in position 2335: illegal multibyte sequence

Just add encoding to read_text(), like this:
return (Path(__file__).resolve().parent / fname).read_text(encoding='utf-8')

Thanks for your report @luolingchun
cc @cacrespo did you ever encounter this?

Thanks @luolingchun this is part of version 0.14

Consider spreading :heart: and :star: the project if you like it mate!

Hi @ultrabug!!
I just installed it in a virtual environment and had no problem...
Although now that I see: it is version 0.14 and it should be fixed 😆


generate more comments

Fix #92. Parse more comments, and emit more comments (and with slightly better formatting).
@danrubel

LGTM


equalToJson with ignoreArrayOrder only ignores some reordering.

Using equalToJson with ignoreArrayOrder set to true only seems to ignore some reordering.
  @Test
    public void equalToJsonIgnoreArrayOrder()
        throws Exception
    {
        String a1 = "[1, 2, 3, 4]";
        String a2 = "[4, 3, 2, 1]";
        String a3 = "[3, 2, 4, 1]";

        StringValuePattern pattern = equalToJson(a1, true, false);
        MatchResult result = pattern.match(a2);

        assertTrue("Should match array with elements in reverse order",
                   result.isExactMatch());

        result = pattern.match(a3);
        assertTrue("Should match array with elements in \"random\" order",
                   result.isExactMatch());
    }

This test fails for me using wiremock 2.6.0 on a mac with java 1.8.0_121.

https://github.com/tomakehurst/wiremock/pull/519 seems to fix the issue. Any plan on accepting that pull request?

https://github.com/tomakehurst/wiremock/pull/519 fails on the following test though:
assertFalse(WireMock.equalToJson("[1, 2, 3, 4]",
                                                            true,
                                                            false)
                                     .match("[1, 3, 2, 4, 5, 6]")
                                     .isExactMatch());

I need to find some time to spend on this. I can see the problem, but I'm dubious about that PR because it works around the problem rather than fixing it at source.
Thanks for the additional test case, that's useful to have.

Closing this issue. Conversation to continue on #519.


Introduce external repository token

Potential alternative to https://github.com/github/codeql-action/pull/273 to demonstrate an idea.
Introduces GitHubApiExternalRepoDetails and GitHubApiCombinedDetails (names very open to changing) to get us type safety on the different types of api token.
Merge / deployment checklist

[x] Confirm this change is backwards compatible with existing workflows.
[x] Confirm the readme has been updated if necessary.

Closes #273.

I forgot to include a couple of bits of https://github.com/github/codeql-action/pull/273 like the changes to the readme and to init/action.yml. I think I've got it all now and this should work but I'm going to give it a manual test before merging. @chrisgavin, could you have another quick look and see if you spot anything else I've missed?

I forgot to include a couple of bits of https://github.com/github/codeql-action/pull/273 like the changes to the readme and to init/action.yml. I think I've got it all now and this should work but I'm going to give it a manual test before merging. @chrisgavin, could you have another quick look and see if you spot anything else I've missed?

I've tested this out locally with a private repository that could only be downloaded by passing the external repository token. It all seems good.

I've tested this out locally with a private repository that could only be downloaded by passing the external repository token. It all seems good.


Integrate Apache Airflow with CWL

Prove that Apache Airflow can run worklfows written according to CWL definition.
Goal: execute our CWL workflows on a cluster with Apache Airflow. Apache Airflow shoud replace run-workflow.py script in this repository.
To begin with, start by defining a a simple CWL workflow of, say, 3 steps and execute it with Apache Airflow (has 3 steps in Airflow as well)
flowchart LR
  a(print 'a')
  b(print 'b')
  c(print 'c')
  a --> b --> c

It is of high priority to integrate with FZJ and WP5.

@r-sarma @MrGweep would you like to contribute?


fix(appengine/queue): lease api call waits for lease timer.

The timer thread was not started as a daemon, making a call
to lease with n seconds would take that same amount of time
to respond.

lgtm, just waiting for the tests to finish.


get users active in last 90 days

see OpenCollective/OpenCollective#212
@asood123 here's what I'm getting at.  I was having trouble with the test environment, so unfortunately I am going to have to abandon this for now.

merging this since seb reviewed it once already.


Auto-deploy handbook to GitHub pages

Purpose
Auto-deploy handbook to GitHub pages when travis runs for the develop branch
Summary of Changes

make rootURL configurable via environment variable
make MIRAGE_ENABLED environment variable apply to all build environments except test
use assetsPrefix for handbook assetsUrlPath
enable lazy loading for handbook engine
configure Travis to build and deploy the handbook to GitHub pages as a separate build stage that is only run for the develop branch

Side Effects / Testing Notes
Example build with deploy: https://travis-ci.org/jamescdavis/ember-osf-web/builds/397410596
(when this build ran, was configured to deploy for deploy_github_pages branch, since changed to develop)
Deployed to: https://jamescdavis.github.io/ember-osf-web/handbook
Example build on branch that shouldn't deploy: https://travis-ci.org/jamescdavis/ember-osf-web/builds/397429550
(When this build ran, was configured to deploy for develop branch. Note the lack of Deploy handbook stage.)
Ticket
n/a
Reviewer Checklist

[ ] meets requirements
[ ] easy to understand
[ ] DRY
[ ] testable and includes test(s)
[ ] changes described in CHANGELOG.md

Coverage increased (+0.01%) to 59.525% when pulling f29fe936f07ce15ae782137857ff3238453ee0fb on jamescdavis:deploy_github_pages into dad19241bbe47e5a6c346c30f047a0e27d9483fc on CenterForOpenScience:develop.

Pull request against develop with no deploy stage: https://travis-ci.org/jamescdavis/ember-osf-web/builds/397612177
Merge to develop with deploy: https://travis-ci.org/jamescdavis/ember-osf-web/builds/397614191


Unable to mint.

Everything is great until you try to mint.  It just says Error  under the button in red.

sadness! sorry to hear. can you elaborate a bit more on your setup? was this on your local build with a deployed contract? or on one of our sample sites? can you share what error was on the console?

I think I ran into a similar issue. Some more info below in case it helps.
Minting from https://nonfungiblecoinbaes.vercel.app/mint with Coinbase Wallet v2.21.1 was failing in the following request:
curl 'https://eth-rinkeby.alchemyapi.io/v2' \
  -H 'authority: eth-rinkeby.alchemyapi.io' \
  -H 'accept: */*' \
  -H 'accept-language: en-GB,en-US;q=0.9,en;q=0.8' \
  -H 'content-type: application/json' \
  -H 'origin: https://nonfungiblecoinbaes.vercel.app' \
  -H 'referer: https://nonfungiblecoinbaes.vercel.app/' \
  --data-raw '{"method":"eth_blockNumber","params":[],"jsonrpc":"2.0","id":5}' \

Response returned:
{"message":"Not Found","logref":null,"path":null,"_links":{"self":{"href":"/v2","templated":false,"profile":null,"deprecation":null,"title":null,"hreflang":null,"type":null,"name":null}},"_embedded":{"errors":[{"message":"Page Not Found","logref":null,"path":null,"_links":{},"_embedded":{}}]}}

The weird part was that the Rinkeby RPC settings was https://rinkeby-infura.wallet.coinbase.com (by default).
Re-connecting the wallet fixed the issue as the eth_blockNumber request started to go to infura again.

@lakai if you can share the error in your console when the client side show "Error" that would be helpful for me to debug the issue. thanks!
@gmertk thanks for the detailed info. did you configure your frontend with your own infura RPC URL? i believe https://rinkeby-infura.wallet.coinbase.com is the default endpoint that Coinbase Wallet uses on their side. in any case, i'm glad the issue was resolved. let me know if it happens again.


Track down pmap tests and demo model

pmaps test are located here: https://github.com/google/jax/blob/main/tests/pmap_test.py /cc @okkwon

@phoenix-meadowlark Is there any update on this issue?

In Flax there are examples for using jax.pmap to train a transformer on WMT en-de and ResNet50 on Imagenet. Some of the other examples also support training using jax.pmap.
Most PAX models can be configured to train using their PmapPartitioner by setting ICI_MESH_SHAPE = None (with the exception of some pipelined configurations that prohibit this). The only OSS model that already uses jax.pmap and trains on non-synthetic data is BertAdamL4H128.

I have a draft PR to help @phoenix-meadowlark to run multiple JAX clients using MPI or environmental variables. If there is a model after partitioning, I can try and help make it run.

I am trying to run NVIDIA1_3BPmap I got from Phoenix. It compiles fine, but it got a segfault, and looking for a way to reproduce it with offline tools.

Filed an issue for the problem above: https://github.com/openxla/openxla-pjrt-plugin/issues/132

The PJRT_Buffer_Delete issue got fixed. So I was able to run. @phoenix-meadowlark can you provide a configuration for two GPUs?

You can use NVIDIA1_3BPmap – it will scale to use as many GPUs/devices as JAX makes available.

Okay, I was able to run multiple clients with MPI, but it needs a tweak in paxml. Here is the diff.
diff --git a/paxml/setup_jax.py b/paxml/setup_jax.py
index dd3e9b4..19f0985 100644
--- a/paxml/setup_jax.py
+++ b/paxml/setup_jax.py
@@ -65,9 +65,10 @@ def setup_jax(globally_use_hardware_rng: bool,

   if should_initialize_jax_distributed:
     if jax_distributed_options:
-      jax.distributed.initialize(jax_distributed_options.coordinator_address,
-                                 jax_distributed_options.num_processes,
-                                 jax_distributed_options.process_id)
+      jax.distributed.initialize()
+#      jax.distributed.initialize(jax_distributed_options.coordinator_address,
+#                                 jax_distributed_options.num_processes,
+#                                 jax_distributed_options.process_id)
     else:
       jax.distributed.initialize()

diff --git a/paxml/tasks/lm/params/nvidia.py b/paxml/tasks/lm/params/nvidia.py
index 4f5018a..db80276 100644
--- a/paxml/tasks/lm/params/nvidia.py
+++ b/paxml/tasks/lm/params/nvidia.py
@@ -268,6 +268,13 @@ class NVIDIA8_3B(NVIDIA1_3B):
   MODEL_DIMS = 4096
   HIDDEN_DIMS = 4 * 4096

<EMAIL_ADDRESS>+class NVIDIA1_3BPmap(NVIDIA1_3B):
+  DCN_MESH_SHAPE = None
+  ICI_MESH_SHAPE = None
+  PERCORE_BATCH_SIZE = 2
+  FPROP_DTYPE = jnp.float32
+

 @experiment_registry.register
 class NVIDIA10B(NVIDIA1_3B):

The thing is when we use MPI, we just need to call jax.distributed.initialize() without any arguments.
Here is the command:
JAX_PLATFORMS=iree_cuda mpirun -np 2 python main.py --exp=tasks.lm.params.nvidia.NVIDIA1_3BPmap --job_log_dir=log_NVIDIA1_3BPmap --mode=eval --multiprocess_gpu

But there is one big question about the IR; I still see mhlo.num_replicas=1 and mhlo.num_partitions=1.

I got a workaround from @trevor-m for the random number generator.
diff --git a/praxis/py_utils.py b/praxis/py_utils.py
index 7766878..90354d2 100644
--- a/praxis/py_utils.py
+++ b/praxis/py_utils.py
@@ -457,7 +457,7 @@ def get_global_input_shape_dtype(x: jnp.ndarray) -> jax.ShapeDtypeStruct:

 def set_globally_use_rbg_prng_key() -> None:
   """Must call this before any JAX computation to set RBG PRNGKey globally."""
-  jax.config.update('jax_default_prng_impl', 'rbg')
+  jax.config.update('jax_default_prng_impl', 'threefry2x32')

 def total_num_vars(variables) -> int:


Add telemetry

cfn-lint version: (cfn-lint --version) N/A
Description of issue. Right now, the only mechanism we have for gathering feedback is GitHub issues.
Feature request: Add telemetry to the linter, similar to how the SAM CLI does it:

it seems to be opt-out
it collects usage data and error reports

Some other data sources besides direct feedback or telemetry:
https://pypistats.org/packages/cfn-lint
https://pepy.tech/project/cfn-lint
https://github.com/aws-cloudformation/cfn-python-lint/network/dependents
https://github.com/aws-cloudformation/cfn-python-lint/graphs/traffic
https://github.com/search?q=filename:.cfnlintrc&type=Code
https://github.com/search?l=YAML&q=Metadata+cfn-lint+config&type=Code
https://github.com/search?q=cfn-lint+--ignore-checks&type=Code
Same code searches internally as well


default-schema-tab not working on multipart/form-data

HelIo!
Thank you again for adding multipart/form-data support. It has been really useful for our team!
I just realized this morning that the default view for form-data was set to example.
I wanted to change it to model so I set default-schema-tab to model but the default tab stays the same.
Is there a way to get model as the default tab?

Thank you very much for this quick update!!


Fix a few problems related to '@' and 'JR'

Fixes https://github.com/rednex/rgbds/issues/259
This also removes 2 conflicts from the parser of rgbasm.
Regarding the warnings of rgbasm when the code has lists of values and there is one or more empty elements, it will only be shown once per list.

Lovely! This is going to make disassembly a whole lot more comfortable! ⭐


Consume is repeated indefinetely when raised OperationCancelledException

Is this a bug report?
Yes
Can you also reproduce the problem with the latest version?
Yes
Environment

Operating system: Windows 10 Enterprise
Visual Studio version: 2017, v15.9.8
Dotnet version: NetCore SDK 2.2.104

Steps to Reproduce

Bus configured with RabbitMQ transport
Retry policy on 'ReceiveEndpoint' set to Immediate(1)
Publish one event
Consumer throws TaskCancellationException or OperationCancelledException

Expected Behavior
The system calls consumer trying to consume message, then retry policy reiterate it exactly one time (UseMessageRetry(r => r.Immediate(1)))
Actual Behavior
The system calls consumer trying to consume message without end.
The same scenario with 'InMemory' transport works as we expected.
Reproducible Demo
    public class Program
    {
        static void Main(string[] args)
        {
            var bus = Bus.Factory.CreateUsingRabbitMq(cfg =>
            {
                cfg.Host(new Uri("rabbitmq://localhost/"), h =>
                {
                    h.Username("guest");
                    h.Password("guest");
                });

                cfg.ReceiveEndpoint("input-queue", e =>
                {
                    e.UseMessageRetry(r => r.Immediate(1));

                    e.Consumer<MyConsumer>();
                });
            });
            bus.Start();

            bus.Publish(new SimpleEvent { Id = 123 });

            Console.ReadLine();
        }
    }
    public class MyConsumer : IConsumer<SimpleEvent>
    {
        public Task Consume(ConsumeContext<SimpleEvent> context)
        {
            var attempt = context.GetRetryAttempt();
            throw new TaskCanceledException("task cancelled");
        }
    }
    public class SimpleEvent
    {
        public int Id { get; set; }
    }

I think that's how it's going to be, given how that exception is part of flow control for the TPL. Since your consumer may actually be cancelled by the transport, which would signal the CancellationToken, and that exception is used by a majority of the pipeline to give up and return to the caller.

Thank you for quick response.
What do you recommend to avoid infinite loop in case, that we actually faced, when consumer calls
http api that is not accessible due to some network issue. I know, easy answer is to solve network issue,
but still it could sometimes happen.
What I missed in above 'Reproducible Demo' is that our abstraction over http client wraps exceptions.
    public class Program
    {
        static void Main(string[] args)
        {
            var bus = Bus.Factory.CreateUsingRabbitMq(cfg =>
            {
                cfg.Host(new Uri("rabbitmq://localhost/"), h =>
                {
                    h.Username("guest");
                    h.Password("guest");
                });

                cfg.ReceiveEndpoint("input-queue", e =>
                {
                    e.UseMessageRetry(r =>
                    {
                        r.Immediate(1);
                    });

                    e.Consumer<MyConsumer>();
                });
            });
            bus.Start();

            bus.Publish(new SimpleEvent { Id = 123 });

            Console.ReadLine();
        }
    }
    public class MyConsumer : IConsumer<SimpleEvent>
    {
        public Task Consume(ConsumeContext<SimpleEvent> context)
        {
            var attempt = context.GetRetryAttempt();
            throw new MyException("my exception", new TaskCanceledException("task cancelled"));
        }
    }
    public class SimpleEvent
    {
        public int Id { get; set; }
    }
    public class MyException : ApplicationException
    {
        public MyException(string message, Exception inner)
            : base(message, inner)
        {
        }
    }

I'm having the same issue with Retry.Exponential.
@phatboyg Is it possible to distinguish exceptions caused by transport/pipeline from exception caused by handler logic?
I tried to wrap it in the handler but it does not help.

I used this code to reproduce issue https://gist.github.com/shatl/5c20aa981d6e6a3cd6c1de6f55cfc52f
Debugger stops at MassTransit.Pipeline.Filters.HandlerMessageFilter.IFilter<ConsumeContext<TMessage>>.Send(ConsumeContext<TMessage> context, IPipe<ConsumeContext<TMessage>> next)
with stack trace

 MassTransit.dll!MassTransit.Pipeline.Filters.HandlerMessageFilter<mtfailure.TestMessage>.GreenPipes.IFilter<MassTransit.ConsumeContext<mtfailure.TestMessage>>.Send(MassTransit.ConsumeContext<mtfailure.TestMessage> context, GreenPipes.IPipe<MassTransit.ConsumeContext<mtfailure.TestMessage>> next) Line 71	C#
 	[Resuming Async Method]
 	System.Private.CoreLib.dll!System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) Line 167	C#
 	System.Private.CoreLib.dll!System.Runtime.CompilerServices.AsyncTaskMethodBuilder<System.Threading.Tasks.VoidTaskResult>.AsyncStateMachineBox<MassTransit.Pipeline.Filters.HandlerMessageFilter<mtfailure.TestMessage>.<GreenPipes-IFilter<MassTransit-ConsumeContext<TMessage>>-Send>d__5>.MoveNext() Line 559	C#
 	System.Private.CoreLib.dll!System.Runtime.CompilerServices.YieldAwaitable.YieldAwaiter.OutputCorrelationEtwEvent.AnonymousMethod__6_0(System.Action innerContinuation, System.Threading.Tasks.Task continuationIdTask) Line 182	C#
 	System.Private.CoreLib.dll!System.Threading.ThreadPoolWorkQueue.Dispatch() Line 588	C#

Execution log (reverse order)
| 11:01:05.816 | Processing 00010000-4100-0250-6851-08d6fefdbc81, message 1 |
| 11:01:05.464 | Processing 00010000-4100-0250-6851-08d6fefdbc81, message 1 |
| 11:01:05.298 | R-RETRY rabbitmq://rmq:5671/test/retry-test-commands 00010000-4100-0250-6851-08d6fefdbc81 test |
| 11:01:05.064 | Processing 00010000-4100-0250-6851-08d6fefdbc81, message 1 |
| 11:01:04.999 | SEND rabbitmq://rmq:5671/test/MassTransit:Fault--mtfailure:TestMessage-- 00010000-4100-0250-8493-08d6fefe1b20 MassTransit.Fault<mtfailure.TestMessage> |
| 11:01:04.978 | R-FAULT rabbitmq://rmq:5671/test/retry-test-commands 00010000-4100-0250-9a1c-08d6fefe1718 mtfailure.TestMessage MassTransit.MessageHandler<mtfailure.TestMessage>(00:00:00.0466748) test |
| 11:01:04.886 | Processing 00010000-4100-0250-9a1c-08d6fefe1718, message 1 |
| 11:01:03.781 | Processing 00010000-4100-0250-9a1c-08d6fefe1718, message 1 |
| 11:01:02.841 | Processing 00010000-4100-0250-9a1c-08d6fefe1718, message 1 |
| 11:01:02.342 | Processing 00010000-4100-0250-9a1c-08d6fefe1718, message 1 |
| 11:01:02.221 | SEND rabbitmq://rmq:5671/test/MassTransit:Fault--mtfailure:TestMessage-- 00010000-4100-0250-6784-08d6fefe1974 MassTransit.Fault<mtfailure.TestMessage> |
| 11:01:02.088 | Bind exchange to exchange (source: MassTransit:Fault--mtfailure:TestMessage--, destination: MassTransit:Fault) |
| 11:01:02.055 | Declare exchange (name: MassTransit:Fault, type: fanout, durable) |
| 11:01:02.055 | Declare exchange (name: MassTransit:Fault--mtfailure:TestMessage--, type: fanout, durable) |
| 11:01:01.981 | Creating model: username@rmq:5671/test |
| 11:01:01.912 | Processing 00010000-4100-0250-9a1c-08d6fefe1718, message 1 |
| 11:01:01.733 | R-RETRY rabbitmq://rmq:5671/test/retry-test-commands 00010000-4100-0250-9a1c-08d6fefe1718 test |
| 11:01:01.579 | Processing 00010000-4100-0250-9a1c-08d6fefe1718, message 1 |
| 11:01:01.500 | R-FAULT rabbitmq://rmq:5671/test/retry-test-commands 00010000-4100-0250-6851-08d6fefdbc81 mtfailure.TestMessage MassTransit.MessageHandler<mtfailure.TestMessage>(00:00:00.0487345) test |
| 11:01:01.396 | Processing 00010000-4100-0250-6851-08d6fefdbc81, message 1 |
| 11:01:00.307 | Processing 00010000-4100-0250-6851-08d6fefdbc81, message 1 |
| 11:00:59.372 | Processing 00010000-4100-0250-6851-08d6fefdbc81, message 1 |
| 11:00:58.880 | Processing 00010000-4100-0250-6851-08d6fefdbc81, message 1 |
| 11:00:58.529 | Processing 00010000-4100-0250-6851-08d6fefdbc81, message 1 |
| 11:00:58.354 | SEND rabbitmq://rmq:5671/test/retry-test-commands 00010000-4100-0250-9a1c-08d6fefe1718 mtfailure.TestMessage |
| 11:00:58.251 | R-RETRY rabbitmq://rmq:5671/test/retry-test-commands 00010000-4100-0250-6851-08d6fefdbc81 test |
| 11:00:53.460 | Declare exchange (name: retry-test-commands, type: fanout, durable) |
| 11:00:53.406 | Processing 00010000-4100-0250-6851-08d6fefdbc81, message 1 |
| 11:00:53.365 | Creating model: username@rmq:5671/test |
| 11:00:48.849 | ConsumerOk: rabbitmq://rmq:5671/test/CHTECVKWLT_dotnet_bus_yyyoyynbyybfbhtwbdmx79oonr?durable=false&autodelete=true - amq.ctag-xIgCBzdQSSq5VJmE5VIExw |
| 11:00:48.843 | ConsumerOk: rabbitmq://rmq:5671/test/retry-test-commands - amq.ctag-eJXmvyqDmjx2te3QVNhVlw |
| 11:00:48.805 | Setting Prefetch Count: 16 |
| 11:00:48.761 | Setting Prefetch Count: 16 |
| 11:00:48.729 | Bind exchange to queue (source: retry-test-commands, destination: retry-test-commands) |
| 11:00:48.714 | Declare queue (name: retry-test-commands, durable) |
| 11:00:48.707 | Bind exchange to queue (source: WS_dotnet_bus_yyyoyynbyybfbhtwbdmx79oonr, destination: WS_dotnet_bus_yyyoyynbyybfbhtwbdmx79oonr) |
| 11:00:48.695 | Bind exchange to exchange (source: mtfailure:TestMessage, destination: retry-test-commands) |
| 11:00:48.680 | Declare queue (name: WS_dotnet_bus_yyyoyynbyybfbhtwbdmx79oonr, x-expires: 60000) |
| 11:00:48.580 | Declare exchange (name: mtfailure:TestMessage, type: fanout, durable) |
| 11:00:48.580 | Declare exchange (name: retry-test-commands, type: fanout, durable) |
| 11:00:48.580 | Declare exchange (name: WS_dotnet_bus_yyyoyynbyybfbhtwbdmx79oonr, type: fanout, auto-delete) |
| 11:00:48.479 | Connected: username@rmq:5671/test (address: amqp://rmq:5671, local: 49264) |
| 11:00:47.691 | Connecting: username@rmq:5671/test |
| 11:00:47.587 | Starting bus hosts... |

This was addressed in v6.


sniffer cleanup

@puerco
New PR against, main stream your comments ;).
Basic cleanup of the sniffer logic
Attaching @puerco Comment

OK, the way the format detection works right now has two main goals:
Avoid reading the whole SBOM into memory
It assumes the SBOM format can generally be found at the top of the file so it tries to optimize for less I/O by catching it early.
The proposed patch breaks # 2 above. For example, if I point the sniffer it to the Kubernetes SBOM which is SPDX, it will read the whole 18 MB needlessly and read it again with the SPDX parser to find the format.
Do you want to rework the patch to maybe unify the reads and open the PR against main? There are some more comments about string conversion, etc but let's go through them in a PR to protobom/main

The proposed patch breaks # 2 above. For example, if I point the sniffer it to the Kubernetes SBOM which is SPDX, it will read the whole 18 MB needlessly and read it again with the SPDX parser to find the format.

Can you elaborate ? (i loop over all sniffer for each fragment block).

I'll take a review today or tomorrow. Thanks, @houdini91!

Hmm, @houdini91, would you be willing to show some basic stats on running this version of the sniffer versus the version currently in main?
It seems both you and @puerco agree on a key criteria by which to choose a sniffer:

The idea of this library is to detect the SBOM format efficiently, that is with the least I/O possible on the SBOM file

But I can't tell just by looking at the code which version of the code is more efficient. If you selected at least two SBOMs (preferably several MBs), ran both, and then showed the timing stats for both, that would probably help resolve which sniffer approach is superior, at least on the efficiency metric.
How does that sound?

Thoughts from @veramine, @wey-chiang and others welcome!

I'm not too worried about conversion throughput/speed/clock time  I would be in favor of a multiple-pass approach to improve accuracy.  I haven't looked at this code yet, but in general speed is not a factor for which to optimize.  Accuracy is far far more important.  Even if conversion takes multiple seconds, that would be ok for our particular use case.

Accuracy is far far more important.

Question: are the approaches equally accurate? I currently don't know of evidence in any direction.

Even if conversion takes multiple seconds, that would be ok for our particular use case.

I think for Chainguard's that this might not be the case. @puerco? My sense is that keeping the conversion very snappy is a technical priority for us.

I did not mean to modify the code flow, accurate or efficient. if i did it was a bug and hopefully i fixed it in the latest commit.
I also agree with @puerco approuch of iterating fragments of files between different sniffers, i only trying to clean up the responsibility of the sniffers to different formats so we have a clear view and interfaces both for our sake and library users.
@puerco @jspeed-meyers Take a peek see if it answers your concerns

Ahh, okay, @houdini91. I clearly mis-understood. Apologies!
I'lll defer to @puerco. Puerco, LMK if my review could be helpful.

Ah now I see where the misunderstanding is:

i only trying to clean up the responsibility of the sniffers to different formats so we have a clear view and interfaces both

The problem with the approach right now is that is has to do one pass for each format. What we want is to detect the SBOM format in less than one read. Is we break the sniffers one per format, it will become more and more inefficient as the number of formats*encodings grow.

@puerco not sure I follow, if we want only one read then we need to probably exact the chunk size (line by line is not bug enough, also lines can be kinda logs of you don't indent .. )
Also do you mean my code in this PR breaks your original code efficiency? Can you try and point me to where you think it breaks.
In the code I try to check cdx and spdx on each line read from file and if one of the sniffers find there respective formats the code sould break.

The problem with the approach right now is that is has to do one pass for each format.

@houdini91, are you saying the approach in this PR does NOT do one pass for each format? I suspect this is where the mismatch in understanding may lie.
If I'm correct, @houdini91, you're saying that this code checks line by line and on each line it checks for evidence of the document being SPDX or CycloneDX. The code therefore does not do a full ingestion of the document and check for SPDX and, if the document is not SPDX, then do another full ingestion of the document and check for CycloneDX. @houdini91, have I correctly represented the current functionality in this PR?
Another question to @houdini91: Why make this change at all? Is is better than the current approach in some way? Sorry, I think I've gotten a little lost.
@houdini91 and @puerco, we could also find a time to meet and discuss this in real time. Long GitHub issues can become confusing :(

I synched with Mikey today about this PR and we're going to go ahead and split the detection into different objects working on data bits (as opposed to going through the full SBOMs data) as this PR is doing. After merging we'll optimize how we're cycling to lower the buffering cycles.
@houdini91 : It seems that the patch is failing to detect the CycloneDX example. As mentioned in the review comments above, I think we can simplify the implementation by dropping the state struct and keeping a persistent format. As these are internal details we can handle that a follow-up.

What's the status with this PR? Is further discussion needed? Some prototyping? Something else?

I think the pr is ready to be merged on the technical side after review of @puerco , aside of test not passing ofc.
I did not debug the test issue deeply but hopefully i can resolve the issue end of next week (I am on vacation until then) so the pr can be merged.

@jspeed-meyers @puerco @manifestori
I fixed the test,
I still have some linter issuer but it comes form a unrelated document , anyone can help me resolve this, so we can merge this

@houdini91:
I see this error:
Error: G601: Implicit memory aliasing in for loop. (gosec)

I would recommend running gosec locally to get more information, including the exact file and line that causes this error. That information should then lead you to a fix.

thanks,

pkg/writer/serializer_cdx.go:184:20: G601: Implicit memory aliasing in for loop. (gosec)
Dependencies: &e.To,

Its odd because it is not something i have changed in this PR @manifestori

@jspeed-meyers PR Is ready to me merged ..

Nice, @houdini91!
Let's get @puerco or @manifestori to take a look. But LGTM!

Ok, got it, i summarise in a issue so we can merge and continue this effort in another PR.
https://github.com/bom-squad/protobom/issues/74

@puerco I opened a new issue so we can track the pending issues from this PR.. (take a peek see if I missing something).
Imho they are not really blockers to merge this one which has been hanging for a while.

OK, sounds good let's merge it as is and we can follow it up in subsequent PRs. Thanks Mikey! :+1:


Wrap words on press some char like ( ' )

Currently if I select a text and press ' the current text selected is replaced by ' char.
I want press ' and wrapper the text selected by this char, like < , [, (, "

This one is worth reopening.

Could you point out where this convention comes from? I've never encountered (or at least noticed) it in the wild.

Hm this seems to work as expected when I use it. Ie write hello select hello then press ' and the text becomes 'hello'.

Seems to work for me as well in all cases except <. Might be something trivial to add if the others currently work.

@rundis it's not working for me.
version 0.8.1

Have you turned on the autoclose brackets plugin (https://codemirror.net/demo/closebrackets.html)
ie do you have the following in your user.behaviors ?
[:editor :lt.objs.editor/autoclose-brackets]

@rundis I have it but commented. Thanks for the reminder!