Error: Building package boost-build:x64-windows failed with: BUILD_FAILED

I'm trying to install the dependencies for cpprestsdk but vcpkg is giving errors when installing boost. Also in the bootstrap-x64-windows-err.log it says "'cl' is not recognized as an internal or external command....". But I'm running this in Visual studio 2017 command prompt and cl is a recognized command. Have also tried it in Powershell with the same result. I have also tried it with an installed version of CMake, then uninstalled CMake and no difference.
C:\Users\aprole\vcpkg>vcpkg install --triplet x64-windows boost-system zlib openssl boost-date-time boost-regex websocketpp
The following packages will be built and installed:

boost-algorithm[core]:x64-windows
boost-array[core]:x64-windows
boost-asio[core]:x64-windows
boost-atomic[core]:x64-windows
boost-bind[core]:x64-windows
boost-build[core]:x64-windows
boost-chrono[core]:x64-windows
boost-concept-check[core]:x64-windows
boost-container[core]:x64-windows
boost-container-hash[core]:x64-windows
boost-context[core]:x64-windows
boost-conversion[core]:x64-windows
boost-coroutine[core]:x64-windows
boost-date-time[core]:x64-windows
boost-exception[core]:x64-windows
boost-function[core]:x64-windows
boost-function-types[core]:x64-windows
boost-functional[core]:x64-windows
boost-fusion[core]:x64-windows
boost-intrusive[core]:x64-windows
boost-io[core]:x64-windows
boost-iterator[core]:x64-windows
boost-lambda[core]:x64-windows
boost-lexical-cast[core]:x64-windows
boost-math[core]:x64-windows
boost-modular-build-helper[core]:x64-windows
boost-mpl[core]:x64-windows
boost-numeric-conversion[core]:x64-windows
boost-optional[core]:x64-windows
boost-pool[core]:x64-windows
boost-range[core]:x64-windows
boost-ratio[core]:x64-windows
boost-rational[core]:x64-windows
boost-regex[core]:x64-windows
boost-smart-ptr[core]:x64-windows
boost-system[core]:x64-windows
boost-thread[core]:x64-windows
boost-throw-exception[core]:x64-windows
boost-tokenizer[core]:x64-windows
boost-tuple[core]:x64-windows
boost-type-index[core]:x64-windows
boost-type-traits[core]:x64-windows
boost-typeof[core]:x64-windows
boost-unordered[core]:x64-windows
boost-utility[core]:x64-windows
openssl[core]:x64-windows
openssl-windows[core]:x64-windows
websocketpp[core]:x64-windows
zlib[core]:x64-windows
Additional packages (*) will be modified to complete this operation.
Starting package 1/49: boost-build:x64-windows
Building package boost-build[core]:x64-windows...
-- Using cached C:/Users/aprole/vcpkg/downloads/boostorg-build-boost-1.69.0.tar.gz
-- Using source at C:/Users/aprole/vcpkg/buildtrees/boost-build/src/ost-1.69.0-1d1e4d577d
-- Using cached C:/Users/aprole/vcpkg/downloads/boost_LICENSE_1_0.txt
-- Using cached C:/Users/aprole/vcpkg/downloads/boost-1.69.0-boostcpp.jam
-- Installing: C:/Users/aprole/vcpkg/packages/boost-build_x64-windows/share/boost-build/copyright
-- Installing: C:/Users/aprole/vcpkg/packages/boost-build_x64-windows/tools/boost-build/boostcpp.jam
-- Bootstrapping...
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:56 (message):
Command failed: C:/Users/aprole/vcpkg/packages/boost-build_x64-windows/tools/boost-build/bootstrap.bat;msvc
Working Directory: C:/Users/aprole/vcpkg/packages/boost-build_x64-windows/tools/boost-build
See logs for more information:
C:\Users\aprole\vcpkg\buildtrees\boost-build\bootstrap-x64-windows-out.log
C:\Users\aprole\vcpkg\buildtrees\boost-build\bootstrap-x64-windows-err.log

Call Stack (most recent call first):
ports/boost-build/portfile.cmake:53 (vcpkg_execute_required_process)
scripts/ports.cmake:71 (include)
Error: Building package boost-build:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: boost-build:x64-windows
Vcpkg version: 2018.11.23-nohash
Additionally, attach any relevant sections from the log files above.
bootstrap-x64-windows-err.log
bootstrap-x64-windows-out.log
bootstrap.log

vcpkg env --triplet x64-windows --debug

Just ran again with the --debug flag
C:\Users\aprole\vcpkg>vcpkg install --triplet x64-windows --debug boost-system zlib openssl boost-date-time boost-regex websocketpp
[DEBUG] Using vcpkg-root: C:\Users\aprole\vcpkg
The following packages will be built and installed:

boost-algorithm[core]:x64-windows
boost-array[core]:x64-windows
boost-asio[core]:x64-windows
boost-atomic[core]:x64-windows
boost-bind[core]:x64-windows
boost-build[core]:x64-windows
boost-chrono[core]:x64-windows
boost-concept-check[core]:x64-windows
boost-container[core]:x64-windows
boost-container-hash[core]:x64-windows
boost-context[core]:x64-windows
boost-conversion[core]:x64-windows
boost-coroutine[core]:x64-windows
boost-date-time[core]:x64-windows
boost-exception[core]:x64-windows
boost-function[core]:x64-windows
boost-function-types[core]:x64-windows
boost-functional[core]:x64-windows
boost-fusion[core]:x64-windows
boost-intrusive[core]:x64-windows
boost-io[core]:x64-windows
boost-iterator[core]:x64-windows
boost-lambda[core]:x64-windows
boost-lexical-cast[core]:x64-windows
boost-math[core]:x64-windows
boost-modular-build-helper[core]:x64-windows
boost-mpl[core]:x64-windows
boost-numeric-conversion[core]:x64-windows
boost-optional[core]:x64-windows
boost-pool[core]:x64-windows
boost-range[core]:x64-windows
boost-ratio[core]:x64-windows
boost-rational[core]:x64-windows
boost-regex[core]:x64-windows
boost-smart-ptr[core]:x64-windows
boost-system[core]:x64-windows
boost-thread[core]:x64-windows
boost-throw-exception[core]:x64-windows
boost-tokenizer[core]:x64-windows
boost-tuple[core]:x64-windows
boost-type-index[core]:x64-windows
boost-type-traits[core]:x64-windows
boost-typeof[core]:x64-windows
boost-unordered[core]:x64-windows
boost-utility[core]:x64-windows
openssl[core]:x64-windows
openssl-windows[core]:x64-windows
websocketpp[core]:x64-windows
zlib[core]:x64-windows
Additional packages (*) will be modified to complete this operation.
Starting package 1/49: boost-build:x64-windows
Building package boost-build[core]:x64-windows...
[DEBUG] _wpopen(""C:\Users\aprole\vcpkg\downloads\tools\cmake-3.12.4-windows\cmake-3.12.4-win32-x86\bin\cmake.exe" --version 2>&1")
[DEBUG] _pclose() returned 0 after    25903 us
[DEBUG] _wpopen(""C:\Users\aprole\vcpkg\downloads\tools\cmake-3.12.4-windows\cmake-3.12.4-win32-x86\bin\cmake.exe" "-DCMAKE_TRIPLET_FILE=C:/Users/aprole/vcpkg/triplets/x64-windows.cmake" -P "C:/Users/aprole/vcpkg/scripts/get_triplet_environment.cmake" 2>&1")
[DEBUG] _pclose() returned 0 after    23750 us
[DEBUG] Found path: C:\Program Files\Git\cmd\git.exe
[DEBUG] _wpopen(""C:\Users\aprole\vcpkg\downloads\tools\git-2.20.0-windows\cmd\git.exe" --version 2>&1")
[DEBUG] _pclose() returned 0 after    34059 us
[DEBUG] _wpopen(""C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe" -all -prerelease -legacy -products * -format xml 2>&1")
[DEBUG] _pclose() returned 0 after    76451 us
[DEBUG] CreateProcessW(cmd.exe /c ""C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Auxiliary\Build\vcvarsall.bat" -vcvars_ver=14.1 amd64   2>&1 <NUL & "C:\Users\aprole\vcpkg\downloads\tools\cmake-3.12.4-windows\cmake-3.12.4-win32-x86\bin\cmake.exe" "-DCMD=BUILD" "-DPORT=boost-build" "-DCURRENT_PORT_DIR=C:/Users/aprole/vcpkg/ports/boost-build" "-DTARGET_TRIPLET=x64-windows" "-DVCPKG_PLATFORM_TOOLSET=v141" "-DVCPKG_USE_HEAD_VERSION=0" "-DDOWNLOADS=C:/Users/aprole/vcpkg/downloads" "-D_VCPKG_NO_DOWNLOADS=0" "-D_VCPKG_DOWNLOAD_TOOL=BUILT_IN" "-DGIT=C:/Users/aprole/vcpkg/downloads/tools/git-2.20.0-windows/cmd/git.exe" "-DFEATURES=core" "-DALL_FEATURES=" -P "C:/Users/aprole/vcpkg/scripts/ports.cmake"")
[ERROR:vcvarsall.bat] Invalid argument found : -vcvars_ver=14.1
[ERROR:~nx0] Error in script usage. The correct usage is:
Syntax:
vcvarsall.bat [arch]
or
vcvarsall.bat [arch] [version]
or
vcvarsall.bat [arch] [platform_type] [version]
where :
[arch]: x86 | amd64 | x86_amd64 | x86_arm | x86_arm64 | amd64_x86 | amd64_arm | amd64_arm64
[platform_type]: {empty} | store | uwp
[version] : full Windows 10 SDK number (e.g. 10.0.10240.0) or "8.1" to use the Windows 8.1 SDK.

The store parameter sets environment variables to support Universal Windows Platform application
development and is an alias for 'uwp'.
For example:
vcvarsall.bat x86_amd64
vcvarsall.bat x86_amd64 10.0.10240.0
vcvarsall.bat x86_arm uwp 10.0.10240.0
vcvarsall.bat x86_arm onecore 10.0.10240.0
vcvarsall.bat x64 8.1
vcvarsall.bat x64 store 8.1
Please make sure either Visual Studio or C++ Build SKU is installed.
-- Using cached C:/Users/aprole/vcpkg/downloads/boostorg-build-boost-1.69.0.tar.gz
-- Using source at C:/Users/aprole/vcpkg/buildtrees/boost-build/src/ost-1.69.0-1d1e4d577d
-- Using cached C:/Users/aprole/vcpkg/downloads/boost_LICENSE_1_0.txt
-- Using cached C:/Users/aprole/vcpkg/downloads/boost-1.69.0-boostcpp.jam
-- Installing: C:/Users/aprole/vcpkg/packages/boost-build_x64-windows/share/boost-build/copyright
-- Installing: C:/Users/aprole/vcpkg/packages/boost-build_x64-windows/tools/boost-build/boostcpp.jam
-- Bootstrapping...
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:56 (message):
Command failed: C:/Users/aprole/vcpkg/packages/boost-build_x64-windows/tools/boost-build/bootstrap.bat;msvc
Working Directory: C:/Users/aprole/vcpkg/packages/boost-build_x64-windows/tools/boost-build
See logs for more information:
C:\Users\aprole\vcpkg\buildtrees\boost-build\bootstrap-x64-windows-out.log
C:\Users\aprole\vcpkg\buildtrees\boost-build\bootstrap-x64-windows-err.log
Call Stack (most recent call first):
ports/boost-build/portfile.cmake:53 (vcpkg_execute_required_process)
scripts/ports.cmake:71 (include)
[DEBUG] CreateProcessW() returned 1 after 3106215 us
Error: Building package boost-build:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: boost-build:x64-windows
Vcpkg version: 2018.11.23-nohash
Additionally, attach any relevant sections from the log files above.
[DEBUG] ..\src\vcpkg\install.cpp(405)
[DEBUG] Exiting after 3384592 us (3382187 us)

donwload vs 2015 => https://stackoverflow.com/questions/44290672/how-to-download-visual-studio-community-edition-2015-not-2017


Remove arrow changeset pin (fixes #2027)

Romain's arrow fix (https://issues.apache.org/jira/browse/ARROW-5361) has been merged, so this can be removed.

Thanks @nealrichardson! We can definitely merge, let me know... but looks like maybe we introduce a different issue in the arrow repo? I have not spotted this one before...
------------------------- ANTICONF ERROR ---------------------------
Configuration failed because arrow parquet was not found. Try installing:
 * brew: apache-arrow (Mac OSX)
If arrow parquet is already installed, check that 'pkg-config' is in your
PATH and PKG_CONFIG_PATH contains a arrow parquet.pc file. If pkg-config
is unavailable you can set INCLUDE_DIR and LIB_DIR manually via:
R CMD INSTALL --configure-vars='INCLUDE_DIR=... LIB_DIR=...'

I wonder why the Mac OSX anticonf is triggering.

It's not macOS; that error message appears only gives macOS help though. The actual problem is farther up. Arrow C++ is failing to build: https://travis-ci.org/rstudio/sparklyr/jobs/540843901#L2015
This is the same issue I fixed for Arrow on Friday. Because your Travis builds are pinned to dist: trusty, you have an old version of Boost (1.54), which is no longer sufficient to build Arrow.
To fix, we/you could either bump up to Xenial (the Travis default as of last month anyway) and follow the fix I did in https://github.com/apache/arrow/pull/4443/files, or try to find a way to install newer Boost on trusty (I'd guess there's a PPA for that), or I hear there is a vendored Boost lib in Arrow we could build with instead (though I haven't looked into what that entails). (See also https://issues.apache.org/jira/browse/ARROW-5474, the resolution of which I would expect to give advice on what to do.)

Oh that's great, that's for pointing out the issue, should be easy to update Travis, I can take a look.


Imports are broken

#52 fixed imports for ext.commands although this needs to be fixed throughout the entire aliased library

discord.tasks are un-importable because nextcord.tasks does not exist

discord.tasks are un-importable because nextcord.tasks does not exist

not a bug. Import is discord.ext.tasks

discord.tasks are un-importable because nextcord.tasks does not exist

not a bug. Import is discord.ext.tasks

I also can't import discord.ext.tasks because I get a ModuleNotFoundError: No module named 'nextcord.tasks'

Yep, the init file should say nextcord.ext.tasks

Is this fixed from the new pull?

Again

Yeah haven't seen anyone have issues with the alias anymore.


Test module + Several minor changes (toolbar, window size, table sort)

Problem
A test module was necessary to ensure the good behaviour of the application
Solution
In the tests folder, the file test_taskstab.py contains all the functions necessary to perform a group test on the table. The file utils_tests.py contains several useful functions.
A toolbar was also added
The behaviour of the size of the window was also changed
The table can now be sorted

Outdated branch, PR closed


Integrate pip-tools for dependency management

pip dependency resolver was taking extremely long due to complex version resolution prior to this change (>6 hours on CI). This commit introduces version pinning with pip-tools. A wrapper script to update the pinned versions when dependencies are added, or when upgrades are needed, is provided.

@nmanovic Do you have link on CI-workflow that takes >6 hours?

@kirill-sizov , I have copied the message from a pull request of Nico G. and his PR. I don't have the link.


Beautify on Save not working with the latest version of Brackets

I just installed Brackets Release 1.1 build 1.1.0-15558 (release ea908cae5). Beautify on Save doesn't seem to be working. Selecting the option manually works fine, but not on save. Is this a  Beautify issue or a Brackets one?

I've got a suggested fix for this in the following pull request.
#130
function onSave(event, doc) {
        var currentTimestamp = Date.now();

        if ((currentTimestamp - localStorage.getItem(COMMAND_TIMESTAMP)) > 1000) {
            format(true);
            localStorage.setItem(COMMAND_TIMESTAMP, currentTimestamp);
            CommandManager.execute(Commands.FILE_SAVE, {
                doc: doc
            });
        }
}

I've got a suggested fix for this in the following pull request.
#130
function onSave(event, doc) {
        var currentTimestamp = Date.now();

        if ((currentTimestamp - localStorage.getItem(COMMAND_TIMESTAMP)) > 1000) {
            format(true);
            localStorage.setItem(COMMAND_TIMESTAMP, currentTimestamp);
            CommandManager.execute(Commands.FILE_SAVE, {
                doc: doc
            });
        }
}

Hey guys thanks for the help on this.  I've updated the registry with the commit.  Thanks @egosapien, @castlefields and @NexZhu  for the code


configure script crashing in virtuealenv due to issues with site.getsitepackages()

In the current master, the line https://github.com/tensorflow/tensorflow/blob/master/util/python/python_config.sh#L63
causes a crash stating

AttributeError: module 'site' has no attribute 'getsitepackages'

if running confgure inside virtualenv Python environment.
The underlying issue is that virtualenv uses an older site package that doesn't have getsitepackages. It is still an open bug in virtualenv after 4 years (!): https://github.com/pypa/virtualenv/issues/355.
For reference, I am using Python 3, virtualenv and virtualenvwrapper on Ubuntu 16.04 with CUDA 8.0. The v0.10.0rc0 release works for me, but this recent fix in python_config.sh breaks virtualenv usage.

I'm facing the same issue

@danmane, you merged this change I believe, but it was originally authored by @itsmeolivia. Could @itsmeolivia look at fixing this so it can work with the older site interface so that virtualenv doesn't break. Thanks!

I ran it and it doesn't crash because of the AttributeError.  It crashes because it expects user input for the python library path and defaults to providing nothing if the python library path cannot be found nor provided by the user.  Right now it is working as intended but the installation can always be made a little smoother.
Here's a quick workaround to find your path manually while I change the script a lil more:
In your virtualenv run:
$ python
>>> from distutils.sysconfig import get_python_lib
>>> print(get_python_lib())
Copy that output and when you run ./configure paste it into the line that says
Please input the desired Python library path to use.  Default is []

looks that the issue is still there. I'm using virtualenv 15.0.1 and the latest tensorflow code (ae62a692ddb53253462c1f79702fbc45baeb4ae3) on ubuntu 16.04 x64.
$virtualenv -p python3 ~/pyenv/tfbuild
$source ~/pyenv/tfbuild/bin/activate
(tfbuild) yguo18@yguo18-skl-u1604:/work/ml/tensorflow_work/tensorflow$ ./configure
WARNING: ignoring http_proxy in environment.
WARNING: --batch mode is deprecated. Please instead explicitly shut down your Bazel server using the command "bazel shutdown".
You have bazel 0.15.0 installed.
Please specify the location of python. [Default is /home/yguo18/pyenv/tfbuild/bin/python]:
Traceback (most recent call last):
File "", line 1, in
AttributeError: module 'site' has no attribute 'getsitepackages'
Found possible Python library paths:
/home/yguo18/pyenv/tfbuild/lib/python3.6/site-packages
Please input the desired Python library path to use.  Default is [/home/yguo18/pyenv/tfbuild/lib/python3.6/site-packages]
/home/yguo18/pyenv/tfbuild/lib/python3.6/site-packages
Do you wish to build TensorFlow with jemalloc as malloc support? [Y/n]: n
No jemalloc as malloc support will be enabled for TensorFlow.
...


Fix layout enum to match specification

Description

layout::column_major is renamed to layout::col_major to match the specification
The values of the enum are swapped to match with close-source layout enum

Fixes https://github.com/oneapi-src/oneMKL/issues/400
Checklist
All Submissions

[x] Do all unit tests pass locally? Attach a log. I have triggered an internal CI (see email)
[x] Have you formatted the code using clang-format?

Other than the file include/oneapi/mkl/types.hpp the diff was generated by replacing layout::column_major to layout::col_major.


Add support for the REST API

Support for querying graph data recently landed in the development builds of CheckMK.
This Pull Request will add support for using it, as the Web API will soon be dropped.
The current plan is to support both the REST and Web API at the same time, until it is no longer necessary.
In order to do this, a lot of recatoring needs to be done, so this might take a while.

Still TODO: Filters can be added multiple times

save & test in datasource menu does not work
probably needs rebasing on main to include #83
remove selected div to get button and form element on the same line:
after adding a filter, the filter dropdown should show the "Add Filter" placeholder
value of template dropdown is cleared
following usecase is not working (having multiple sites, not sure if this is relevant):

choose host
choose service cpu utilization
template dropdown shows multiple cpu utilization elements, should only show a single one
(hint: it works if a site filter is added, but i think this should not be mandatory)

removing a filter element clears filters after this element:

add filter site "local"
add filter host "localhost"
add filter service "APT Updates"
remove filter host
-> service filter will no longer contain "APT Updates"

really like that the Negate checkbox!


Pass dbt model path to dagster

Description

This should pass the path of the dbt model to Dagster to materialize assets.
Motivation and Context

How Has This Been Tested?

Ran Dagit locally and all seemed to be working
Types of changes

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

Checklist:

[ ] My code follows the code style of this project. (Did you install and run the pre-commit hooks?)
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

:+1:


SSO Authentication Remote Jupyter

Applies To

[X] Notebooks (.ipynb files)
[ ] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
I'm trying to use SSO of Azure Active Directory to login into Snowflake. The problem happens when I'm using VSCode to remote a VM in an azure ML environment.
When I run the command to login the notebook is not showing me a placeholder where to put the URL

In case I run directly in a jupyter notebook in the VM it works as expected

Any idea what could I try to fix it?
VS Code Version
1.74.0
Jupyter Extension Version
v2022.11.1003412109
Jupyter logs
No response
Coding Language and Runtime Version
No response
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
Remote

Please could you enable logging as follows:

Open settings & go into Jupyter->Logging
Change the value to verbose
Reload VS Code,
Attempt to repro the issue & then copy the output from the Jupyter output panel.

Could you also copy the output from the console window, you can get to that using the command Toggle Developer Tools

Closing this issue as its been over 4 weeks, since the information was requested.
We'll be happy to reopen the issue when the requested information has been provided.

I have encountered the same issue and here is my workaround:

Run the connect code, your browser will open a page to sign in to the SSO, and then jump to a page that has URL starts with "localhost:xxxxx'. （this is the URL you copied into the input box in jupyter)
Go back to vscode, there is a port forwarding page next to terminal window.  Manually setup port forwarding to be the same as the one you see on SSO page.
One port forwarding is ready, go to your browser and refresh the page.
Go back to vscode, your connection to SF should be ready in a few second.

I guess there might be an issue with auto port forwarding.

I change the log level of Jupyter to Verbose but it still starts with debug in the output window, here is the jupyter output from console window:
debug 17:22:37.220: VSCodeNotebookController::handleExecution, Class name = Kv (started execution) debug 17:22:37.222: Execute Cell 2 /mnt/**********.ipynb debug 17:22:37.222: start the kernel, options.disableUI=false for /mnt/**********.ipynb debug 17:22:37.222: Start Jupyter Session in kernel.ts with disableUI = false debug 17:22:37.224: Start cell 2 execution @<PHONE_NUMBER>224
and here is the developer tool output
log.ts:392  INFO [LocalProcess0][resolveAuthority(ssh-remote,1)][1ms] obtaining proxy... log.ts:392  INFO [LocalProcess0][resolveAuthority(ssh-remote,1)][1ms] invoking... log.ts:392  INFO [LocalProcess0][resolveAuthority(ssh-remote,1)][1045ms] waiting... log.ts:392  INFO [LocalProcess0][resolveAuthority(ssh-remote,1)][2003ms] waiting... log.ts:404   ERR [Extension Host] (node:15960) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead. (Use Code --trace-deprecation ...to show where the warning was created) console.ts:137 [Extension Host] (node:15960) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead. (UseCode --trace-deprecation ...to show where the warning was created) log.ts:392  INFO [LocalProcess0][resolveAuthority(ssh-remote,1)][2968ms] returned <IP_ADDRESS>:61777 log.ts:392  INFO resolveAuthority(ssh-remote) returned '<IP_ADDRESS>:61777' after 2970 ms log.ts:392  INFO Creating a socket (renderer-Management-56b86923-42d4-4405-b134-a4baf9186736)... log.ts:392  INFO Creating a socket (renderer-ExtensionHost-ec0d22e8-1dea-4aa6-9db3-b70fe41a820e)... log.ts:392  INFO Creating a socket (renderer-Management-56b86923-42d4-4405-b134-a4baf9186736) was successful after 168 ms. log.ts:392  INFO Creating a socket (renderer-ExtensionHost-ec0d22e8-1dea-4aa6-9db3-b70fe41a820e) was successful after 337 ms. log.ts:404   ERR Could not find pty on pty host: CodeExpectedError: Could not find pty on pty host     at S.L (/mnt/******/.vscode-server/bin/ee2b180…/out/vs/platform/terminal/node/ptyHostMain.js:27:6849)     at S.updateIcon (/mnt/******/.vscode-server/bin/ee2b180…/out/vs/platform/terminal/node/ptyHostMain.js:27:2680)     at Object.call (/mnt/******/.vscode-server/bin/ee2b180…/out/vs/platform/terminal/node/ptyHostMain.js:17:5043)     at l.s (/mnt/******/.vscode-server/bin/ee2b180…/out/vs/platform/terminal/node/ptyHostMain.js:15:5412)     at l.q (/mnt/******/.vscode-server/bin/ee2b180…/out/vs/platform/terminal/node/ptyHostMain.js:15:4915)     at /mnt/******/.vscode-server/bin/ee2b180…/out/vs/platform/terminal/node/ptyHostMain.js:15:4326     at n.invoke (/mnt/******/.vscode-server/bin/ee2b180…/out/vs/platform/terminal/node/ptyHostMain.js:11:145)     at E.deliver (/mnt/******/.vscode-server/bin/ee2b180…/out/vs/platform/terminal/node/ptyHostMain.js:11:2070)     at c.fire (/mnt/******/.vscode-server/bin/ee2b180…/out/vs/platform/terminal/node/ptyHostMain.js:11:1708)     at process.T (/mnt/******/.vscode-server/bin/ee2b180…/out/vs/platform/terminal/node/ptyHostMain.js:9:20949)     at process.emit (node:events:526:28)     at emit (node:internal/child_process:938:14)     at processTicksAndRejections (node:internal/process/task_queues:84:21) log.ts:404   ERR Could not find pty on pty host: CodeExpectedError: Could not find pty on pty host     at S.L (/mnt/******/.vscode-server/bin/ee2b180…/out/vs/platform/terminal/node/ptyHostMain.js:27:6849)     at S.updateTitle (/mnt/******/.vscode-server/bin/ee2b180…/out/vs/platform/terminal/node/ptyHostMain.js:27:2630)     at Object.call (/mnt/******/.vscode-server/bin/ee2b180…/out/vs/platform/terminal/node/ptyHostMain.js:17:5043)     at l.s (/mnt/******/.vscode-server/bin/ee2b180…/out/vs/platform/terminal/node/ptyHostMain.js:15:5412)     at l.q (/mnt/******/.vscode-server/bin/ee2b180…/out/vs/platform/terminal/node/ptyHostMain.js:15:4915)     at /mnt/******/.vscode-server/bin/ee2b180…/out/vs/platform/terminal/node/ptyHostMain.js:15:4326     at n.invoke (/mnt/******/.vscode-server/bin/ee2b180…/out/vs/platform/terminal/node/ptyHostMain.js:11:145)     at E.deliver (/mnt/******/.vscode-server/bin/ee2b180…/out/vs/platform/terminal/node/ptyHostMain.js:11:2070)     at c.fire (/mnt/******/.vscode-server/bin/ee2b180…/out/vs/platform/terminal/node/ptyHostMain.js:11:1708)     at process.T (/mnt/******/.vscode-server/bin/ee2b180…/out/vs/platform/terminal/node/ptyHostMain.js:9:20949)     at process.emit (node:events:526:28)     at emit (node:internal/child_process:938:14)     at processTicksAndRejections (node:internal/process/task_queues:84:21) log.ts:392  INFO [perf] Render performance baseline is 98ms console.ts:137 [Extension Host] Starting WebSocket: RAW/api/kernels/55858091-a0fb-43a8-8714-175cd70658c3 log.ts:404   ERR read ECONNRESET: Error: read ECONNRESET 	at TCP.onStreamRead (node:internal/stream_base_commons:217:20) 3 log.ts:398  WARN Settings pattern "application.*" doesn't match any settings DevTools failed to load source map: Could not load content for https://vscode-remote+ssh-002dremote-002b7b2……ons/ms-toolsai.jupyter-renderers-1.0.15/out/client_renderer/preload.js.map: Connection error: net::ERR_NAME_NOT_RESOLVED DevTools failed to load source map: Could not load content for https://vscode-remote+ssh-002dremote-002b7b2……0692131/out/webviews/webview-side/ipywidgetsKernel/ipywidgetsKernel.js.map: Connection error: net::ERR_NAME_NOT_RESOLVED DevTools failed to load source map: Could not load content for https://vscode-remote+ssh-002dremote-002b7b2……i.jupyter-renderers-1.0.15/out/client_renderer/builtinRendererHooks.js.map: Connection error: net::ERR_NAME_NOT_RESOLVED DevTools failed to load source map: Could not load content for https://vscode-remote+ssh-002dremote-002b7b2……-2023.2.1200692131/out/webviews/webview-side/ipywidgetsKernel/dummy.js.map: Connection error: net::ERR_NAME_NOT_RESOLVED
sensitive information was replaced with *
At this point, jupyter notebook is running and waiting for a response, I had to manually setup port forwarding, and then the code would execute with no error
here is the jupyter output
 debug 17:22:37.220: VSCodeNotebookController::handleExecution, Class name = Kv (started execution) debug 17:22:37.222: Execute Cell 2 /mnt/**********.ipynb debug 17:22:37.222: start the kernel, options.disableUI=false for /mnt/**********.ipynb debug 17:22:37.222: Start Jupyter Session in kernel.ts with disableUI = false debug 17:22:37.224: Start cell 2 execution @<PHONE_NUMBER>224 debug 17:25:11.697: End cell 2 execution @<PHONE_NUMBER>696, started @<PHONE_NUMBER>224, elapsed time = 154.472s debug 17:25:11.697: Cell 2 executed with state Success debug 17:25:11.697: VSCodeNotebookController::handleExecution, Class name = Kv, completed in 154477ms, has a falsy return value

Thank you for your help
Please can you share all of the logs (not just a section)
If the file and folder names are sensitive please could you open a different folder and just mask the user name (leaving rest of the past)
The paths are important, as I will need to map them in the logs and figure out which one is which

Had to attach a file, otherwise some log would be translated into format
Jupyter Log.txt
developertoollog.txt

Looks like you are using an old version of vscode and Jupiter extension
Please could you update them and try again
And send the logs once again

There is no new version of vscode that I can find.
The Jupyter version is v2023.2.1200692131, which is also the latest version I can found, unless I switch to pre-release channel.

Oops, sorry was looking at the wrong logs

I have encountered the same issue and here is my workaround:
Run the connect code, your browser will open a page to sign in to the SSO, and then jump to a page that has URL starts with "localhost:xxxxx'. （this is the URL you copied into the input box in jupyter)
Go back to vscode, there is a port forwarding page next to terminal window. Manually setup port forwarding to be the same as the one you see on SSO page.
Once port forwarding is ready, go back to your browser and refresh the SSO page.

@54iceblock sorry it took me a while to get back to this issue, i've re-read this issue and checked the logs
I do not think this is an issue in the extension, instead this is just a configuration (environment setup) issue
I agree this is not the best experience, however you will need to first setup the port forwarding for things to work.
Hence whatyou have described as the work around, is the right solution.
Closing as this is the expected behaviour.
Hope that makes sense, if I have misunderstood something, please do feel free to reply back here

I think the behavior difference between web hosted jupyter and vscode hoster jupyter is that, on web, it will show a box to paste the URL to jupyter to continue the process but not in vscode. Would it be possible to show the box like the one on shown in the 2nd pic of original post?

I have encountered the same issue and here is my workaround:

Run the connect code, your browser will open a page to sign in to the SSO, and then jump to a page that has URL starts with "localhost:xxxxx'. （this is the URL you copied into the input box in jupyter)
Go back to vscode, there is a port forwarding page next to terminal window.  Manually setup port forwarding to be the same as the one you see on SSO page.
Once port forwarding is ready, go back to your browser and refresh the SSO page.
Go back to vscode, your connection should be ready in a few second.

I guess there might be an issue with auto port forwarding. @DonJayamanne, would you mind to re-open this issue and I can try pull the log you needed.

Hi @54iceblock I didn't manage to get the Port Forwarding page next to the terminal while using an Azure ML VM. By any chance did you use this type of VM?

I have encountered the same issue and here is my workaround:

Run the connect code, your browser will open a page to sign in to the SSO, and then jump to a page that has URL starts with "localhost:xxxxx'. （this is the URL you copied into the input box in jupyter)
Go back to vscode, there is a port forwarding page next to terminal window.  Manually setup port forwarding to be the same as the one you see on SSO page.
Once port forwarding is ready, go back to your browser and refresh the SSO page.
Go back to vscode, your connection should be ready in a few second.

I guess there might be an issue with auto port forwarding. @DonJayamanne, would you mind to re-open this issue and I can try pull the log you needed.

Hi @54iceblock I didn't manage to get the Port Forwarding page next to the terminal while using an Azure ML VM. By any chance did you use this type of VM?

Nope, I'm using cortex lab.

Could you try right click on "OUTPUT" and see if "port" is not checked
Hit F1 and then type 'port', see if you have option "forward a port" available

I think port is associated with the remote extension, you might want to play with the extension a bit if none of the solution above works.

I have encountered the same issue and here is my workaround:

Run the connect code, your browser will open a page to sign in to the SSO, and then jump to a page that has URL starts with "localhost:xxxxx'. （this is the URL you copied into the input box in jupyter)
Go back to vscode, there is a port forwarding page next to terminal window.  Manually setup port forwarding to be the same as the one you see on SSO page.
Once port forwarding is ready, go back to your browser and refresh the SSO page.
Go back to vscode, your connection should be ready in a few second.

I guess there might be an issue with auto port forwarding. @DonJayamanne, would you mind to re-open this issue and I can try pull the log you needed.

Hi @54iceblock I didn't manage to get the Port Forwarding page next to the terminal while using an Azure ML VM. By any chance did you use this type of VM?

Nope, I'm using cortex lab.

Could you try right click on "OUTPUT" and see if "port" is not checked
Hit F1 and then type 'port', see if you have option "forward a port" available

I think port is associated with the remote extension, you might want to play with the extension a bit if none of the solution above works.

Thanks for your answer, unfortunately, none of the options 1 and 2 worked. Looks like it's a problem with the Azure Machine Learning - Remote extension which is not letting me forward the ports.

you can also try paste the URL direct in the terminal, at least it works for me.

you can also try paste the URL direct in the terminal, at least it works for me.

When I run the cell to establish the connection, the terminal is not showing anything related to an input

I know, but can you try paste it?  that works for me with python directly or via jupyter when sshed into remote cortex machine using remote-ssh extension.

I tried it but unfortunately didn't work.

@mrcmoresi Is this still an issue?

Hi @DonJayamanne
unfortunately yes, I kept trying different things and nothing worked out.

Closing this issue for now, as its now possible for extension authors to create custom extensions that contribute Jupyter servers with custom authentication
I.e. one can create an extension that merely provides the jUpyter server URI and the auth information (allowing 3rd party extension to be responsiblel for auth)
https://code.visualstudio.com/updates/v1_83#_finalized-jupyter-server-provider-api-for-extension-authors


Remove Delete Lists/Items from Drawers

Since checkboxes are removed, there's no way for the user to select items/lists and that button will never be enabled.

Commit: https://github.com/johneastman/todo/commit/6b04a615171d9ba4f7502c395bc9e692cda13e77


Component - QR

Design: https://www.figma.com/file/eOUqz887O5EKZwIJhJQ13U/SubWallet-UI-Base?node-id=306%3A5400&t=tpBNXokKY0HhEGG6-0
Test URL: https://ui-preview.subwallet.app/?path=/story/basic-components-qrcode--default&globals=backgrounds.value:!hex(1A1A1A)

Please check:

[ ] QR with icon can not scan (Example: Scan with value = an address)

[ ] Remove "bordered" control if not use them


Add Localizable.strings Korean

Added Localizable.strings Korean

Thank you! This PR will be reviewed and merged before the release of the next minor version of Reveil.

Thanks a lot.


Version 1.8.6

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

Project coverage is 78.07%. Comparing base (e81633a) to head (f2c3645).
Report is 17 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##               main     #435   +/-   ##
=========================================
  Coverage     78.07%   78.07%
  Complexity      347      347
=========================================
  Files            28       28
  Lines          1195     1195
=========================================
  Hits            933      933
  Misses          262      262

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[Info] Pages in /info/ to use the same styling and components as Library

But in a different index/type.
Also, add /info/ to the CDN to enable Crosswalk

Here is an example page:  https://stage.lifesciences.danaher.com/us/en/info/what-is-luminescence.html

Fixed with #483, #484 & #486


(localsend_app:324511): Gtk-WARNING **: 09:17:50.997: Could not load a pixbuf from /org/gtk/libgtk/icons/16x16/status/window-minimize-symbolic.symbolic.png.

Describe the bug

To reproduce
manjaro linux run LocalSend-1.8.0.AppImage
Expected behavior
not run
Screenshots
No response
Desktop (please complete the following information)
No response
Smartphone (please complete the following information)
No response
Additional context
No response

Looks like the issue brought up in #212
Workarounds have been detailed there!


pull request for e2e test at 12/06/2016 16:56:02

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


x11docker runs on raspi4 (aarch64)

I have installed docker and x11docker on a raspi 4 (8GB) running ubuntu 20.04. On this system I can run a xfce4 desktop in from a docker image which I have built with buildx for the aarch64 architecture (andewufrank/xfce-session-deb10) based on debian.
This is proof of concept of the idea to have portable desktop GUI to move between different types of hardware. I will now study the existing examples to build a working desktop; specific questions may arise...
Thank you for the clever design of x11docker, which is easily portable across linux installations!

@andrewufrank, note that x11docker is architecture agnostic. It works on any architecture, as long as the host can execute the binaries in the images. See #274. In dbhi/docker several multi-arch images are provided, which you can use as a reference.

I thought the idea to make x11docker architecture agnostic very impressive. I constructed an armv6 version of xfce to test on a old raspberry (1) (from andrewufrank/xfce). It did not work and I attach the --debug file for you. Perhaps the error is small, but it may be a fundamental limitation of the VERY small device. Could you point me to the dockerfile for the lcde image you mentioned in the readme file. I could imagine a trivial dockerfile, but then I observed that your dockerfile for xfce was not just calling the metapackage for the xfce desktop but installed each package separately. Why is this necessary?
Next test is for armv7 (on an cubietruck).
I consulted the dbhi/docker and might be interested in octave use. for dbhi i had to check a paper by wappler and fetzer to have an idea what is meant. is this what you do for a living? interesting!

@andrewufrank, note that I am not the/a maintainer of this project. @mviereck is. I just help him test x11docker and runx on some platforms (mostly Windows), when I have time.

It did not work and I attach the --debug file for you.

I think you forgot to attach it!

Could you point me to the dockerfile for the lcde image you mentioned in the readme file. I could imagine a trivial dockerfile, but then I observed that your dockerfile for xfce was not just calling the metapackage for the xfce desktop but installed each package separately. Why is this necessary?

I believe the dockerfile you are asking about is the following: https://github.com/mviereck/dockerfile-x11docker-lxde. @mviereck keeps each dockerfile in a different repository: https://github.com/mviereck?tab=repositories&type=source

I consulted the dbhi/docker and might be interested in octave use.

That should work as-is. Try x11docker [ARGS] aptman/dbhi:bionic-octave octave. You can optionally specify the arch of the container: aptman/dbhi:bionic-octave-arm, aptman/dbhi:bionic-octave-arm64 or aptman/dbhi:bionic-octave-amd64.

for dbhi i had to check a paper by wappler and fetzer to have an idea what is meant. is this what you do for a living? interesting!

I am not aware of the paper you mention. AFAIK, those docker images are used in dbhi.github.io, which is a framework/methodology to "compile" hardware designs, (V)HDL sources, into executable binaries/shared libs, and then use Dynamic Binary Modification to hook those in replacement of functions in existing unmodified applications. See FPGA2020_poster.pdf. Hence, dbhi/qus and dbhi/docker seem to be helper sub-projects. Nonetheless, I am neither a maintainer. I just use the multiarch images on RPi, because they provide GHDL, VUnit, numpy, Flask, Gtkwave and Octave.

I think of adding a check in x11docker for host and image architecture to avoid a failure like in #274 and to print a warning in case there is an architecture mismatch.
I just checked here, uname -m prints x86_64, docker inspect --format '{{.Architecture}}' x11docker/xfce prints amd64.
So the output is not equal but means the same. Could you please show me the output for other architectures, too?
Are there multi-arch images that could run on multiple platforms (not just different docker tags)?

I think of adding a check in x11docker for host and image architecture to avoid a failure like in #274 and to print a warning in case there is an architecture mismatch.

That might not be easy to check. On the one hand, QEMU is installed and enabled in Docker Desktop by default. Hence, Windows/MacOS users can execute arm32v7 or arm64v8 images on their amd64 hosts, without any setup. However, GNU/Linux users need to setup binfmt explicitly. That's one of the reasons for dbhi/qus to exist. On the other hand, Docker Desktop supports a subset of architectures only. For example, a year ago arm32v6 was not supported/enabled, ony arm32v7: linuxkit/linuxkit#3401. That's the second reason for dbhi/qus to exist. Overall, dbhi/qus provides a consistent approach to configure QEMU/Docker on any host OS (GNU/Linux, Windows or MacOS). BTW, dbhi/qus is known to work with podman and/or buildx too.
Hence, the check should be a warning only. Even if the architectures don't match, some will work by default. Moreover, almost any (foreign) container should work if docker run --rm --privileged aptman/qus -s -- -p is executed first (once only, until restart).
x11docker could try to check which binfmt interpreters are registered (see register.sh). But, is it worth adding that complexity to x11docker?

I just checked here, uname -m prints x86_64, docker inspect --format '{{.Architecture}}' x11docker/xfce prints amd64.
So the output is not equal but means the same. Could you please show me the output for other architectures, too?

There are mismatches between uname, Docker and QEMU (even between Debian and Fedora packages). See the hardcoded equivalencies in https://github.com/dbhi/qus/blob/main/run.sh#L364-L389 and https://github.com/dbhi/qus/blob/main/run.sh#L66-L116.

Are there multi-arch images that could run on multiple platforms (not just different docker tags)?

Yes. All the images in dbhi/docker have different tags for each platform, but then a "manifest" tag exists to unify all of them. So, aptman/dbhi:bionic-octave-arm, aptman/dbhi:bionic-octave-arm64 and aptman/dbhi:bionic-octave-amd64 are IMAGES, but aptman/dbhi:bionic-octave is a MANIFEST. See https://hub.docker.com/r/aptman/dbhi/tags?page=1&name=bionic-octave.
As a result, if the user executes aptman/dbhi:bionic-octave, the manifest is read and the image that matches the host architecture is used. However, the user might want to explicitly execute a foreign container. For example, using the ARM64 container on an AMD64 Windows host. In that case, the user needs to specify the full tag (*-arm64), otherwise *-amd64 is downloaded and used by default.

the debug file I mentioned and forgot to attach:
raspi2.txt

Line 274 says

docker ERROR: dockerrc(): Did not receive PID of PID1 in container.
Maybe the container immediately stopped forunknown reasons.

Probably means your container isn't running & that it quit unexpectedly. My first guess would be an Architecture Mismatch but that's suspect since you built w/ buildx. Can you run the container like below on your target system and tell us the output?
docker run andrewufrank/xfce file /usr/local/bin/start

on the cubietruck i have for uname -m armv7l, on the raspi i get (from memory, it is not connected just now) armv6l.
for the command you asked to run I am not certain if it is with file or not. here both cases
docker run andrewufrank/xfce file /usr/local/bin/start
docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "exec: \"file\": executable file not found in $PATH": unknown.
ERRO[0003] error waiting for container: context canceled

root@cubietruck:/home/frank# docker run andrewufrank/xfce  /usr/local/bin/start
docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "exec: \"/usr/local/bin/start\": stat /usr/local/bin/start: no such file or directory": unknown.
ERRO[0002] error waiting for container: context canceled

the images should be available for all architectures:
b576e2e2dcab linux/amd64  204.85 MB
3de45eeab021 linux/arm/v6 192.03 MB
5ac0856ce08a linux/arm/v7 187.76 MB
b7a8f087c0aa linux/arm64 198.06 MB
and i would assume that the correct image is selected automatically. unfortunately I cannot see in the debug log the ID of the image, only the container, which I will verify a bit later.

@andrewufrank, can you try the official images first? I.e. arm32v7/ubuntu and/or arm32v6/ubuntu.

I could imagine a trivial dockerfile, but then I observed that your dockerfile for xfce was not just calling the metapackage for the xfce desktop but installed each package separately. Why is this necessary?

I can't remember the exact reasons for this image yet. In general, I try to build small images. Meta packages can have more dependencies than intended, some even include xorg.
A very small image is x11docker/fvwm.

That might not be easy to check. On the one hand, QEMU is installed and enabled in Docker Desktop by default. Hence, Windows/MacOS users can execute arm32v7 or arm64v8 images on their amd64 hosts, without any setup. However, GNU/Linux users need to setup binfmt explicitly. That's one of the reasons for dbhi/qus to exist. On the other hand, Docker Desktop supports a subset of architectures only. For example, a year ago arm32v6 was not supported/enabled, ony arm32v7: linuxkit/linuxkit#3401. That's the second reason for dbhi/qus to exist. Overall, dbhi/qus provides a consistent approach to configure QEMU/Docker on any host OS (GNU/Linux, Windows or MacOS). BTW, dbhi/qus is known to work with podman and/or buildx too.

Thank you for this insight! I wasn't aware of this.

There are mismatches between uname, Docker and QEMU (even between Debian and Fedora packages). See the hardcoded equivalencies in https://github.com/dbhi/qus/blob/main/run.sh#L364-L389 and https://github.com/dbhi/qus/blob/main/run.sh#L66-L116.

Thank you, maybe I'll use this for a check in x11docker. It would have taken a long time to collect all those multiple code names.

In fact, docker run --rm --privileged aptman/qus -s -- -p is not limited to using foreign containers. After executing that command, any foreign binary can be used on the host as long as it is statically built, or foreign dependencies exist. Precisely, using foreign containers avoids installing cross-platform toolchains.

Interesting. So this container adds (with --privileged) some QEMU features to the host kernel.
This is technically impressive, but something I would never recommend or do myself. It adds complexity, therefore security and stability risks. I recommend to just use images matching the host architecture. If they don't exist, build them yourself. I might be biased, but I believe not everything that is possible should be done.

I thought the idea to make x11docker architecture agnostic very impressive. I constructed an armv6 version of xfce to test on a old raspberry (1) (from andrewufrank/xfce). It did not work and I attach the --debug file for you.

The debug output looks like an architecture mismatch, though I am not sure.
I've made a commit that show host and image architecture in the --debug output.

@andrewufrank Sorry I didn't test it & assumed it worked.
I've tested the following on the x11docker/lxde image & confirm it works. Update the Docker tag w/ whatever you need & run this on whichever system you are having issues deploying the docker image to (The Rasp Pi 1 If I followed correctly)
docker run andrewufrank/xfce /bin/bash -c "apt-get update 1>/dev/null 2>&1 && apt-get install -y file 1>/dev/null 2>&1 && file /usr/bin/lxsession"

We are trying to get info of the executing binary inside the image you built.

Interesting. So this container adds (with --privileged) some QEMU features to the host kernel.

Yes. Technically, it uses a shell script to register binfmt interpreters based on the magic strings from QEMU, and point them to QEMU user static binaries. binfmt is a kernel feature. See https://dbhi.github.io/qus/#context-docker-and-qemu:

Fortunately, the Linux kernel has a capability named binfmt_misc which allows arbitrary executable file formats to be transparently recognized and passed to certain applications . This is configured either by directly sending special sequences to the register file in a special purpose file system interface (usually mounted under part of /proc), or using a wrapper (like Debian-based distributions) or systemd’s systemd-binfmt.service.
Moreover, in version 4.8 of the kernel a new flag was added to the binfmt handlers . It allows to open the emulation binary when it is registered, so in future it is cloned from the open file. This is specially useful because it allows to work with foreign architecture containers without contaminating the container image.

Nonetheless, using the permanent (-p) flag is optional. In https://dbhi.github.io/qus/#tests 15+ different setups are summarized. As you see, half of them do not use -p, but then users need to somehow add qemu-user-* binaries to the containers. In fact, that was the mainstream approach, until -p was added to v4.8 of the kernel.
Overall, aptman/qus is just a handy packaging (container) for qemu-user-static packages from Debian, plus a couple of shell scripts.

This is technically impressive, but something I would never recommend or do myself. It adds complexity, therefore security and stability risks. I recommend to just use images matching the host architecture. If they don't exist, build them yourself. I might be biased, but I believe not everything that is possible should be done.

It is mostly meant for CI and for development purposes. On the one hand, using this approach allows to build, test and publish multi-arch images/manifests using regular amd64 only CI services (such as GitHub Actions or Travis CI). On the other hand, it allows developing and testing applications for embedded devices (say SBCs or SoCs with FPGA) from amd64 workstations. I believe this is the motivation for the partnership between Docker and ARM, and why QEMU is included in Docker Desktop by default.
For example, binaries built and tested in arm32v7/ubuntu containers can be deployed to PYNQ boards (https://github.com/Xilinx/PYNQ/releases). Such embedded devices are typically slower than workstations, specially for cpu-bound tasks. Hence, even if QEMU introduces a x3-10 execution penalty, development can be faster. Furthermore, using a container is "cleaner" than installing all cross-compilation dependencies on the host. Last, but not least, some of those boards cost >2000€. Hence, the number of devices in the lab (or at home) might be limited.
Summarizing, dbhi/qus is mostly targeted at users that would use QEMU in any case. Nontheless, some users have reported use cases which I would have not though about. E.g., running Steam on a RPi.

on the cubietruck (an armv7 architecture) I installed a headless debian butcher and added the packages the wiki recommends (i.e.
xpra xserver-xephyr xinit xauth xclip x11-xserver-utils xdpyinfo and then x11-utils which seems to include xdpyinfo). The xfce desktop starts (with a recommendation to use --xorg) but I had no mouse package. Any idea what I should install? otherwise I add a desktop - what is a good choice?

@pahansen95 I ran ubuntu (the architecture is selected automatically) with
x11docker --desktop ubuntu in the raspi desktop.
The result was a large grey window (not the full screen), but nothing showed except for the cross, which moves with the mouse.
I attach the debug log.
I have the impression from the logs that the raspi 1 is very slow and does not produce expected responses fast enough; then x11docker and docker give up? Is this possible?
raspi5.txt

@pahansen95 - I ran your command docker run andrewufrank/xfce /bin/bash -c "apt-get update 1>/dev/null 2>&1 && apt-get install -y file 1>/dev/null 2>&1 && file /usr/bin/lxsession" in an ssh terminal and have absolutely no output and cannot see a file generated. I do not understand the command. If there should be a file you would like to see (/usr/bin/lxsession), please tell me.
Thank you for the interest!

That sounds like expected results running x11docker --desktop ubuntu. The X Server was started on the host but since the vanilla ubuntu image isn't configured with a desktop environment you are left with a grey screen & the debug log again saying it couldn't get the Pid of the container's PID1.
So let's backtrack

the issue that you need help as I understand is the andrewufrank/xfce image you built seems to be exiting unexpectedly (according to the debug logs).
You're running it on a Raspberry Pi 1.

So to troubleshoot you should first try & confirm your container is quitting unexpectedly. If you can confirm that then you should figure out why it's quitting.
So the command I provided (I've removed suppression of stdout & stderr when updating via apt-get)
docker run andrewufrank/xfce /bin/bash -c "apt-get update && apt-get install -y file && file /usr/bin/lxsession"

is meant to be run on the Raspberry Pi 1 & should print to stdout details about the /usr/bin/lxsession binary OR it might dump some sort of message about being unable to execute (in which case means the binary is built for the wrong architecture).
The last part of the command which is passed to the docker container is the important bit. file /usr/bin/lxsession.
Here is what the file command does.
/usr/bin/lxsession is the binary that is ultimately run by your container assuming it's the just the x11docker/xfce Dockerfile built for armv6. If not then we will probably need to see your Dockerfile.

@pahansen95 - Thank you for your explanation, now I see what you intended.
I run the code you gave (once in a terminal, once in a console); it does not produce any output at all.
I also run the ubuntu image and got the error message (x11): no screen found (EE)  . The images are all for the armv7 architecture and the original RPi 1 uses armv6l (which is what uname -m says).
I have the impression that the early single board computers (I tested also an cubietruck, which is 'armv7' but failed when installing docker) made too many trade-offs and optimizations  and are too "special" to run docker and x11docker; they are also too slow for desktop interaction. Thus I give up on x11docker for the RPi 1 and concentrate on the RPi 4, which seemed initially to work.
Thank you for your help! I learned quite a bit and may need your support for more powerful boards.

are too "special" to run docker and x11docker

You could run a check if docker itself works at all on RPi 1.
For example:
docker run -ti alpine sh

This should give you an interactive shell in a container.

I have the impression from the logs that the raspi 1 is very slow and does not produce expected responses fast enough; then x11docker and docker give up? Is this possible?
raspi5.txt

Your raspi5.txt does not contain --debug output.
(In general, I prefer logs in www.pastebin.com, would be nixe to store them there)

on the cubietruck (an armv7 architecture) I installed a headless debian butcher and added the packages the wiki recommends [...] The xfce desktop starts (with a recommendation to use --xorg) but I had no mouse package.

Do you get a mouse cursor now?
IIRC Raspian is based on debian and adds some Raspberry specific packages. Maybe Debian on its own is not enough and misses something to detect the mouse.

It is mostly meant for CI and for development purposes. On the one hand, using this approach allows to build, test and publish multi-arch images/manifests using regular amd64 only CI services (such as GitHub Actions or Travis CI). On the other hand, it allows developing and testing applications for embedded devices (say SBCs or SoCs with FPGA) from amd64 workstations. I believe this is the motivation for the partnership between Docker and ARM, and why QEMU is included in Docker Desktop by default.

For example, binaries built and tested in arm32v7/ubuntu containers can be deployed to PYNQ boards (https://github.com/Xilinx/PYNQ/releases). Such embedded devices are typically slower than workstations, specially for cpu-bound tasks. Hence, even if QEMU introduces a x3-10 execution penalty, development can be faster. Furthermore, using a container is "cleaner" than installing all cross-compilation dependencies on the host. Last, but not least, some of those boards cost >2000€. Hence, the number of devices in the lab (or at home) might be limited.

Thank you, that is comprehensive.

x11docker now prints host and image architecture in the PID1 error message.
Example:
x11docker ERROR: dockerrc(): Did not receive PID of PID1 in container.
  Maybe the container immediately stopped for unknown reasons.
  Just in case, check if host and image architecture are compatible:
  Host architecture: amd64 (x86_64), image architecture: amd64.

Thanks @andrewufrank , I've used the check from your link to https://github.com/dbhi/qus/blob/main/run.sh#L364-L389 to provide a hopefully useful output.

Thank you for adding this check - I will try it out next time I connect the Raspi 1 (space on my workbench is limited, now the RPi4 is on).
I like your approach and appreciate all the clever ideas which went into x11docker!

I've created a wiki page for multiarch setups with QEMU, mostly copypasted from @umarcor 's posts.
Could you please have a look? Proposals are appreciated.
https://github.com/mviereck/x11docker/wiki/Multiarch-setups-with-QEMU

i have replied - favorably - in an email.

I did not receive an email yet. Can't we just discuss here?

a short writeup on the use of buildx approach to multi-arch images

That sounds like a good idea.
Overall, I'd like to keep the wiki article rather short. The point is that I am not experienced myself in these approaches and could not answer questions about this myself.
I think of a short overview, even shorter than now, that just gives a core explanation and points where to look further.

I will attempt to draft something. how and where can I send it to you?

I will attempt to draft something. how and where can I send it to you?

Thanks! You could just post it here.

here it is! comments welcome! it needs fixing the link to the multi-arch wiki page and the title.

title: Multiarchitecture with Docker
abstract:Buildx allows the construction of Docker images for multiple hardware architectures. The produced images can be deployed to different hardware (PC, Raspberry, Odroid etc.) and run there identically.
keywords: Docker
date: 2020-08-12
My dream is to have one program run on different hardware exactly the same; with docker, buildx and x11docker we are approaching this goal very quickly. The idea is to construct programs, program suits and even desktop environments which can be installed on different hardware to produce the same user experience.
A major limitations in the past were differences in the CPU used in different hardware: a Raspberry uses a CPU with a different set of instructions than a PC (see wiki multi-archictecture) and QEMU allows the emulation of an instruction set of one hardware on a different hardware; this permits execution of programs for a Raspi on a PC.
buildx takes a different path in producing comparable Docker images for different hardware, mostly using existing compiled versions of a program for different hardware architectures and freezing the installation steps.
An ordiary Docker image is build on a host hardware putting together compiled programs for the architecture of the host; a Dockerfile list the instructions a programmer would use to construct the program - from the OS used, adding program packages   and describin the setup (e.g. access to disks, use of ports). The result is an image which can be downloaded on another host of the same architecture and run there using the local kernel.
With buildx the same Dockerfile can be used to produce in parallel images which can execute on different hardware architecture. buildx requires an installation of QEMU and some experimental features of Docker build; on newer hardware it is easy to install. The result is a set of comparable Docker images, which run on different hardware and produce identical effects.
For example, it is possible to construct an xfce desktop, including firefox and Visual Studio Code, which runs identically on a PC and a Raspberry 4 (i.e. on hardware with an amd64 and an aarch architecture). The commands to be issued in a console are
x11docker --home=$HOME/secondhome --desktop --hostnet --share $HOME/Download -- --tmpfs /dev/shm --  andrewufrank/xfce-plusvc:deb10.1.x1.1.e1.vc1aarch

respectively
x11docker --home=$HOME/secondhome --desktop --hostnet --share $HOME/Download -- --tmpfs /dev/shm --  andrewufrank/xfce-plusvc:deb10.1.x1.1.e1.vc1.

The Dockerfile is found on github. It should be possible to have one Dockerfile and one encantation for both architectures, but I have not yet figured out how.
x11docker selects automatically the docker image appropriate for the host hardware architecture and the images run code which is alrady compiled for this hardware with native speed (not emulated as with QEMU); for example, Visual Studio Code runs on a Raspberry 4 with acceptable speed - for example the rendering of an Markdown file is done on the fly.

I've created a wiki page for multiarch setups with QEMU, mostly copypasted from @umarcor 's posts.
Could you please have a look? Proposals are appreciated.
https://github.com/mviereck/x11docker/wiki/Multiarch-setups-with-QEMU

LGTM! Maybe I'm missing an explicit reference to the fact that Docker Desktop includes QEMU (installed and enabled) by default. I.e., some reference from https://dbhi.github.io/qus/#linuxkitbinfmt-dockerbinfmt. So, users of Docker Desktop + x11docker on Windows can execute aarch64 containers (for say RPi), without using any additional tool.

I think of a short overview, even shorter than now, that just gives a core explanation and points where to look further.

I think that the last paragraph (the one specific about arm32v7 and ZYNQ) can be removed.

Thank you for your proposals! I am working on the wiki article yet.
I've already shortened the QEMU part a bit and try to give a short introduction to buildx based on you post. You wrote a lot, sorry, maybe I wasn't clear that I want to keep it short.

Maybe I'm missing an explicit reference to the fact that Docker Desktop includes QEMU (installed and enabled) by default.

Maybe I should re-add this. I've already dropped this part.

@andrewufrank, AFAIU, the difference between build and buildx is only related to the manifests. With build, you use a command to build each of the images, and then a last command to generate/update the manifest based on those images. Conversely, with buildx a single command will internally execute each of the images and also update the manifest.
However, with regard to the ability for executing foreign architectures, buildx is exactly the same. That is, dbhi/qus can be used BEFORE running buildx, as an alternative to installing QEMU on the host through a package manager. See https://docs.docker.com/buildx/working-with-buildx/#build-multi-platform-images. In https://github.com/dbhi/qus/issues/2#issuecomment-596101886, you will find several examples that combine dbhi/qus and buildx in CI.
As commented above (and copied in the wiki), the purpose of dbhi/qus is NOT executing containers (only). The main usage of dbhi/qus is to avoid installing a full QEMU package through apt, dnf... It allows registering the foreign archs you need, and no more. Any regular install would setup all the foreign architectures by default.

I think the wiki article is ok now: https://github.com/mviereck/x11docker/wiki/Multiarch-setups-with-QEMU
I've reordered a bit to divide more clearly between QEMU, dbhi/qus and buildx. I hope, everything is technically correct.
Thank you @all for your contributions!

Yet I found that installing qemu-user-static on Debian host is enough to run arm images on amd64.
I did no further setup and removed all other QEMU packages from host.
The package installs:
qemu-aarch64_be-static    qemu-mips64el-static      qemu-riscv32-static
qemu-aarch64-static       qemu-mips64-static        qemu-riscv64-static
qemu-alpha-static         qemu-mipsel-static        qemu-s390x-static
qemu-armeb-static         qemu-mipsn32el-static     qemu-sh4eb-static
qemu-arm-static           qemu-mipsn32-static       qemu-sh4-static
qemu-cris-static          qemu-mips-static          qemu-sparc32plus-static
qemu-debootstrap          qemu-nios2-static         qemu-sparc64-static
qemu-hppa-static          qemu-or1k-static          qemu-sparc-static
qemu-i386-static          qemu-ppc64abi32-static    qemu-tilegx-static
qemu-m68k-static          qemu-ppc64le-static       qemu-x86_64-static
qemu-microblazeel-static  qemu-ppc64-static         qemu-xtensaeb-static
qemu-microblaze-static    qemu-ppc-static           qemu-xtensa-static

I am confused.
Does Docker detect the binaries and uses them automatically? (Docker version 19.03.12, build 48a66213fe)
So no setup at all is needed than just installing this package. I even don't need to execute the binaries myself.
$ uname -m
x86_64
$ docker run --rm  -ti arm32v7/debian:stretch-slim
root@0757b1d279fb:/# uname -m
armv7l

So no setup at all is needed than just installing this package. I even don't need to execute the binaries myself.

When you install pacakge qemu-user-static, it does not only install all those (static) binaries, but it also executes qemu-setup-binfmt.sh, in order to have all of them registered automatically. In Debian or systems with systemd, it also configures them to work after restart. But, depending on the system, interpreters might not be registered automatically, or might not work automatically after restart.
So, there are two points to understand here:

Docker does not detect the binaries, the kernel does. Whichever user level application that wants to execute a binary (docker is a user level application) asks the kernel to do so. Then, the kernel checks the magic string and decides which interpreter to use for it. For instance, python3 is another possible interpreter (for executable python scripts). I am not an expert, but I would say that the permissions of the application are dependent on the user level context, not on the interpreter. Hence, from a security point of view, using qemu-user-static is not more insecure than executing the same binary natively on the target host. In any case, the attack surface is increased because of QEMU's codebase.

dbhi/qus does use Debian's qemu-user-static package (it downloads them, extracts the content and puts it in images) and QEMU's qemu-setup-binfmt.sh (a modified version is added to aptman/qus images). The difference is that dbhi/qus can install and register a single interpreter (or a few of them) only. Furthermore, exactly the same command can be used on any GNU/Linux, Windows and/or MacOS terminal. That is, installing "system packages" requires different commands on Debian, Fedora, Arch, Alpine, etc. However running aptman/qus is possible on any of them.

@umarcor Thank you for the clarification!
It seems on Debian the magic strings for automatic detection by the kernel are stored in /usr/share/binfmts.
I've added some notes about the standard installation and shortened the article overall.


autotest: Handle test runs atomically

An example of this is changing test scripts after enqueuing test runs.

Closed by #3398.


Add fetchMultiple to compliment rpc getMultiple

Notes

Added fetchMultiple to AccountClient to handle fetching multiple program accounts at once.

Discussion

Also created (but didn't commit) test in the tests/misc project, but it requires depending on local built ts. Not sure how ts tests are being handled, please advise.
getMultipleAccountsInfo is now in solana web3, but only (stable) as of 1.24.1. Currently anchor is using 1.17.0. Advise upgrading this reference and reworking utils/rpc to use it.  I could do this and #364 at the same time. Already did that one.

LInt appears to still be failing.

Lint appears to still be failing.

apologies. amended.


Use GitHub Action to fetch translations from Transifex daily

Everyday around 00:00 UTC (+/- some offset), this action will fetch translations from Transifex and commit them if there are any changes.
This action will also be triggered by:

Updates to Python files
Updates to this file.
Manually from actions page.

The following must be set up as secrets in the repository:

SOME_STRING: Anything. Changing this invalidates pip cache.
TRANSIFEX_API_TOKEN: Self-explanatory.

Awesome! Very happy about this -- I'll merge it in then kick off a manual run to test.

Glad to help!


fix combination/product bug

it's broken when the input has 3 sets.
This bug affects for, so it breaks if more than 3 vars are defined.
previous behavior:
(combination/product [1 11] [2 22] [3 33])
;=>
[[1 2] 3]
[[1 2] 33]
[[1 22] 3]
[[1 22] 33]
[[11 2] 3]
[[11 2] 33]
[[11 22] 3]
[[11 22] 33]

BTW, I can't yarn repl after yarn install
$ yarn repl

><EMAIL_ADDRESS>repl /Users/miyamonz/go/src/github.com/miyamonz/glisp
> node ./repl/index.js

Error: ENOENT: no such file or directory, open '/Users/baku/Sites/glisp/repl/lib/core.glisp'

so I only tested on a browser manually.
https://glisp.app/commit:9bce3f6/?code_url=https://gist.githubusercontent.com/miyamonz/5310b09eb276e170f03be606b96a329e/raw/72f7541b25a2a35abf24e31989fab726e72c296d/sketch_sep-11-2020_22-31-24.glisp.glisp
and I couldn't find out how to run tests and where to write my test.
According to test.js, maybe the test setting is only for your PC currently. isn't it?

Thank you for your PR...! I just merged and it seems to work fine;)
As for yarn repl, you need to run yarn repl:build at first to set up the local REPL environment running on Node.js. I'll write about it on the documentation soon!


Making  public get unsigne dtx for UnsignedTransactionImpl

👋  I am updating the playground with a SimulatedBlockchainContext.
having this function as public would let me delete a lot of code.

On this occasion, I would like to ask if this method and the other getters could be added to the UnsignedTransaction interface. I always wondered why it is empty and need to access some of the information in my clients (for me it is getBoxesToSpend().


new functions: str_unique() & word()

Let me know when you're ready for me to take a look at this one and I'll merge

Will do. At the moment I'm just adding functions periodically.

Awesome! Thank you for you help


#1630 Fix assertion for Map<String, Set>

Relates to #1630
I added a test that reproduces the issue and added a fix that achieves the expected behavior.
@marcingrzejszczak in the ticket you say it should work with sets,
but a set is an unordered collection, but arrays in JSON are ordered.
Do we check the order of elements in JSON?  If not, just accept my PR :)
If yes, I'm hesitating that we can treat sets as lists. Maybe we have to check contains for sets, but not equals.
I can work on it, but I need this to be clarified.
Also
SingleTestGeneratorSpec fails in the main branch as well, so it's not related to my changes.

@dehasi Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@dehasi Thank you for signing the Contributor License Agreement!


Simple dump functions are not defined (Composer installation)

Hi, I've installed sage with Composer in a pre-existing project, the setup is PHP 8.1 with some Symfony components (so dd is taken).
I tested it by using the sage() and saged() functions and it works very well (backtrace dump works too).
However, it seems that their shorthand versions - s() and sd() respectively - are actually returning simple dumps, while explicitly calling the simple dump functions  - i.e., ssage() and ssaged() - raises a fatal error because they seem to be undefined.
As far as I understand, the library injects functions in the global namespace, so it shouldn't be necessary to explicitly require the class and/or individual functions with use statements, correct?
This is a sample output of calling saged('testing'):

while this is the output of sd('testing'):

Is this the expected behaviour?

First of all, thank you for trying this tiny tool and for reporting the issue! I really appreciate it!
The readme is currently describing changes ahead of the latest release (available through "php-sage/sage": "dev-main"), but I am actually already confident enough of the stability.
I went ahead and created a new release, if you'd run composer update you should be getting the latest version with shorthands working as advertised :)
Happy coding, let me know if anything annoys you about Sage, I'd appreciate it :))


How to create a read more button for a post? I mean how to only show a part of posts and click "read more" to read all?

when run jekyll serve show error：
Liquid Exception: Included file '_includes/JB/setup' not found in _posts/2012-04-01-python_1.md/#excerpt
jekyll 2.1.1 | Error:  Included file '_includes/JB/setup' not found

Hi, @sunxianchao
I don't use Jekyll Bootstrap in this theme and don't know how to reproduce your bug.
I also checked your repository and blog, it seems the problem have already fixed.  Let me know if there is anything I can do to help.
Please delete the author picture in your blog. This picture is copyright reserved.

Hi, @truongduyng
Freshman21 theme doesn't support "read more" mode. However, you can fix this problem by create post.summary, please see this article.

wow, greate theme and article!. Thank you very much.

Hi, @truongduyng
Thanks for you reply. I upload the readmore version to my repository, you can copy this version by using
git clone --branch readmore https://github.com/yulijia/freshman21.git


White bg on Junodownload

Could someone please let me know how to darken the background on junodownload.com via dev mode?

This should be enough
        {
            "url": "junodownload.com",
            "removebg": "body"
        },

No theme is required for Dynamic Theme mode.


fix(utils) Monkeypatch to serializeFunction

Resolves #5001 and cases where functions are serialized with a prefix of function function

Types of changes

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

Description

This is a naive attempt at resolving #5001
I am not certain how to resolve the root issue with the function parsing code; the current code in serialize.js strikes me as requiring specific knowledge of how it was built. @galvez Perhaps you have ideas for a better fix?
Otherwise, I'm hopeful that this PR is helpful!
Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[x] All new and existing tests are passing.

Codecov Report

Merging #5754 into dev will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##             dev   #5754   +/-   ##
=====================================
  Coverage   95.6%   95.6%
=====================================
  Files         82      82
  Lines       2662    2662
  Branches     683     683
=====================================
  Hits        2545    2545
  Misses        98      98
  Partials      19      19

Impacted Files
Coverage Δ

packages/utils/src/serialize.js
92.85% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

@aaronransley just please check this against 2.7.1 as I have a suspicion this may have been solved already. cc @pi0

@galvez Still occurring on 2.7.1

@aaronransley k, cool, let's get this in then
@pi0 I'll take a stab at rewriting serializeFunction using acorn to prevent further problems.


carton init should check locally installed swift wasm version before installing from github

Hi,
My swift wasm is locally installed by adding its path to .bashrc, so when I run:
swift --version
SwiftWasm Swift version 5.9.1 (swift-5.9.1-RELEASE)
Target: x86_64-unknown-linux-gnu

which swift
/home/cc/Downloads/swift-wasm-5.9.1/usr/bin/swift

But when I run carton init --template tokamak I got this:
Creating new project with template tokamak in TokamakApp
- checking Swift compiler path: /home/cc/.carton/sdk/wasm-5.9.1-RELEASE/usr/bin/swift
- checking Swift compiler path: /home/cc/.swiftenv/versions/wasm-5.9.1-RELEASE/usr/bin/swift
Fetching release assets from https://api.github.com/repos/swiftwasm/swift/releases/tags/swift-wasm-5.9.1-RELEASE
Response contained body, parsing it now...
Response succesfully parsed, choosing from this number of assets: 7
Local installation of Swift version wasm-5.9.1-RELEASE not found
Swift toolchain/SDK download URL: https://github.com/swiftwasm/swift/releases/download/swift-wasm-5.9.1-RELEASE/swift-wasm-5.9.1-RELEASE-ubuntu22.04_x86_64.tar.gz

it seems that carton is looking for swift either at ~/.carton/sdk/wasm-5.9.1-RELEASE/usr/bin/swift or ~/.swiftenv/versions/wasm-5.9.1-RELEASE/usr/bin/swift. If not found, it tries to install it from github.
I think this is not ideal for the case when swift is actually already installed.

Unfortunately there is no good way to detect if a given swift executable is built from a specific revision of SwiftWasm, so we conservatively check only known installation layouts.

Is it possible to run some command like swift --version or which swift to find the installed swiftwasm?


Update address hrp

Description
Updating hrp address.
Related issue(s)
#388
Checklist

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)
[x] My code follows the code style of this project.
[x] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[ ] CHANGELOG is updated.

@yenkhoon Thanks


PostgreSQL Store for Sessions, Subscriptions and Messages.

Are there any plans to support PostgreSQL as a store for sessions, subscriptions and offline messages?

His testark,
while there are currently no clear plans for this, we've been discussing some sort of full consistency modes for VerneMQ lately. This would imply making the backend database replacable or switchable, and would be the first step in any case (PostgreSQL or other).
Let's see.
Great to see you back here btw :)

@ioolkos have there been any developments regarding this?

hi @testark! Unfortunately not. Our priorities have been elsewhere lately. I think the best chance of getting a feature like this at the moment would be if someone contributes it - it doesn't have a very high priority on our roadmap at the moment. That is, of course, subject to change ;)


Collections and Data Structures

Addressed comments and fixed <> formatting

@cartermp  Fixed. Ready to merge?

Not quite sure I like the affinity between HashSet<T> and performing mathematical functions.  What was the rationale for this article when it was written for MSDN?

@cartermp  Not sure who originally wrote this nor what their rationale was. Should I just remove this from the table?

@stevehoag I think we can keep in the table.  The key benefit to a HashSet<T> for me has always been storing unique elements with similar performance characteristics of a Dictionary<K, V>.  Capturing that somehow (e.g., "Efficient storage and access of unique elements") seems like an appropriate value proposition.

@cartermp Good call - changed it to "Manage efficient storage and access of unique elements "

LGTM.


Can Ason be designed to be inheritable and then used to support other serialization formats?

Such as JSON. ASON interface may require a visitor pattern.

If a generic parameter supports serialization of various basic types, and the specific serialization format operation is provided by the generic parameter, then I think ason can provide serialization functions for different formats

There is already a custom serialization method n each class you can implement.
__asonSerialize(): StaticArray<u8>{}
__asonDeserialize(buffer: StaticArray<u8>): void {}

If you would like to inject your own serialization method inside ASON, it's already possible at compile time.

I mean to replace all encoding modes, for example, JSON encoding can be implemented based on ASON

The answer here is no. I suppose it might be possible to assemble things across rust or other languages using the reflection semantics I'm designing. However, as is, the algorithm is heavily coupled to the assemblyscript runtime.


MacOS Ventura, Python 3.10 - pip install -r requirements fails

ERROR: Could not find a version that satisfies the requirement scipy==1.7.1
How can I install on Ventura?

similar issue with numpy 1.21.3


Resolve "Add Kernel Logger"

Closes #357

As of right now the Logger constructor is not getting called at all and I'm at a complete loss as to why that would be. I've tried moving it into the global namespace, calling the constructor manually, printing inside it, and just about anything else. No indication that it's getting initialized. When I moved it to the global namespace, the constructor appeared in the .ctors section according to Ghidra, but m_logLevel was still 0 (lTrace) despite the code showing it should be set to 3 (lInfo).

Global constructor issue was resolved (at least in part) in #373. However, even though things like the primes task are now working properly, the static Logger instance is still not being constructed properly. The log level is being ignored.

@micahswitzer raises the point that having something to replace all of the __func__ arguments would be nice. I propose that once we create the standard library directory, we can add a SourceLocation class that mimics the functionality of std::source_location


Camouflage any RFTools block (elevator), horizontal screen placement

A way to camouflage RFtools blocks, most specifically the Elevator.
Allow screens to be placed flat on top/bottom of blocks.

Doing that in general is not very easy. I could do it for some specific blocks though like the elevator.

yes that would be nice but slightly complicated atm. It is on my todo however

Could just use the same method you use to paint blocks from the shield.

Yes but that's possible because those shield blocks are made for that. All other blocks are not and that's not very easy

Bringing this suggestion back if its ever becomes possible, that would be amazing for the elevator blocks especially, and perhaps add a door control that would only open the doors if the elevator is at the current floor, I think I can manage to do a system for this right now if the elevator block output a redstone signal when its at a floor, I have to fiddle out a bit with this right now.

The elevator does output a redstone signal when it is at a floor. That's what the red arrow is for at the back

Good, will have to find a way to get the door system now that I know I can count on a redstone signal. I found a nice sliding door from Malisis doors that should fit nicely. What is the maximum size of the elevator, can I do a 4x4 or its 3x3 limited platform size.

The elevator does output a redstone signal when it is at a floor. That's what the red arrow is for at the back

Wish I'd known that a few days ago.  I just set up a system using a Sensor to detect the elevator platform being present. :man_facepalming: (Works well, and I can even hide it behind a wall on most floors due to the sensor's 3-block mode.  Though it doesn't work on some floors due to layout, and this would let me fix that.)
I'm using a Shield for the door, although currently in 1.10 this doesn't support using another block texture yet, which would be nice.


[BUG] Failed to install additional selinux policy by semodule

Describe the bug

libsemanage.semanage_commit_sandbox: Error while renaming /var/lib/selinux/targeted/active to /var/lib/selinux/targeted/previous. (Invalid cross-device link).
/usr/sbin/semodule:  Failed!

To Reproduce
Steps to reproduce the behavior:

install an rpm package that includes selinux policies, refer to https://docs.harvesterhci.io/v1.1/troubleshooting/os#how-can-i-install-packages-why-are-some-paths-read-only

Expected behavior

install additional selinux policy successfully
Support bundle

Environment

Harvester ISO version:
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630):

Additional context
Add any other context about the problem here.
workaround:
mv /var/lib/selinux/targeted/active /var/lib/selinux/targeted/previous
cp --link --recursive /var/lib/selinux/targeted/previous /var/lib/selinux/targeted/active

Let's reopen this if this is still a valid issue.


Spelling Correction in Service Section

#16 Corrected the Bootstrap Spelling

This issue is assigned to someone else. Please do not make pull requests before you are assigned.


No option to change hires manager email address

stuck on<EMAIL_ADDRESS>

This value should be set correctly if a site is created from the /admin page, and is updated when a the hires manager radial buttons are updated in the sites settings page.
As a global admin page is now present, initial seed data should be removed

effectively fixed with #10


[Soft fork] Modify validation control flow for Bitswap block propagation

Included in this, need to support partial breadcrumbs in the frontier (or another intermediate data structure in front of the frontier that tracks partial blocks).

Some discussion (copying here from a DM thread):
George:
So, I am considering the following design: I think of introducing a header frontier (HF). This will be just the same as full frontier, only with headers instead of breadcrumbs.
The invariant will be for each transition will be in one of the following states:

Part of full frontier (FF)
Part of catchup tree
Part of header frontier
Not known to the node
Each transition in HF has parent: a) a root transition b) a transition in HF c) a transition in FF. A transition is added to HF when it's received on the gossip and condition above applies. If condition above doesn't hold, a catch-up is triggered.
For each transition in HF we request associated bitswap block tree to be retrieved. Each transition in HF has a timeout assigned. After the timeout the transition is removed from HF and is scheduled for catch-up.
———————————
Justification for such design is the following:

I don't want to implement a new catch-up procedure right now and want to leave super-catchup intact
I want to rely on super-catchup even in case the Bitswap fails
I want to abstain from using super-catchup in "average case"

Follow-up on this: I think it's a good idea to have gossip messages of 3-4 headers, representing a chain of a block and a few of its immediate ancestors
This will cover all the short forks that regularly happen on the network
This way I think we will almost never require catchup, bar the catchup on node's start
Nathan:
I finally had some time today to think through this some. After working through the problem in my head some, I believe I'm largely aligned with the strategy of introducing a new HeaderFrontier, though there are some complexities of this approach I am still thinking through. I'm diagramming and writing my thoughts up on this, will share with you this week. I'm thinking we can simplify some of the transition handler subsystem while we add this without having to dig into the guts of the frontier or the catchup subsystem.
Also sent as direct message
One thing I'm struggling to come to grips with is how this will continue to add complexity in the management of all these different frontier views we have (catchup tree, full frontier, and now header frontier). The catchup tree and header frontier both need to be pruned based on root transitions to the full frontier. We also need to decide on exact invariants on when a transition is stored in the catchup tree vs the header frontier, and those 2 need to interact (catchup tree needs to know if we acquired a block body for a dependency over bitswap, and header frontier needs to know when catchup jobs succeed and fail).
My current thought is that, while a larger change, we should consider folding the catchup tree and the header frontier into the same data structure. This would simplify the model a lot, I think, but would require more extensive updates to the catchup mechanism. It's probably possible to expose this data structure directly to catchup the same way that catchup works off of the catchup tree today, but it might make sense to rethink having a separate state machine for catchup altogether. All-in-all, I counted 9 types of notifications that need to be sent between these subsystems and data structures under this approach, which is a lot. Each of these notifications needs thought put into how they will fit into the concurrency model.
The ideal model in my head is to have a singular state machine running for all "in-flight" transitions. All the pending transitions would be stored in the same data structure, with states such as WaitForParentValidation, WaitForBitswap, WaitForCatchup, BodyAvailable and BodyValidated. We could thus simplify the catchup mechanism to not operate off of a state machine model, but instead to be a simple worker pool that just downloads batches of blocks from other peers based on jobs we dispatch to it. The obvious downside of this is that it creates more work upfront, but I think it puts us in a better world and makes it less likely we introduce new bugs.


*: make it clear that proxy only supports v2 api now

@heyitsanthony @gyuho

LGTM. Thanks.

lgtm


DaVinci-003 deprecated, what is the new one?

I am using this model: "model: Model.textDavinci3". I received an email from OpenAI telling me that I need to update it.

I couldn´t find any other model to be replaced. What is the new one to be used in a "CompleteText" call?
Thanks.

@htsnet you can using gpt-3.5-turbo-instruct

@redevrx Thank you!


add a use case for responding to events

This sample project was not completed yet, as the whole benefits of DDD can be further explained by adding another use case for responding to events of changes happening to domain objects.

Done!


New Website Logo: Clever Cloud

Organization name: Clever Cloud
Homepage url: https://www.clever-cloud.com/
Logo url: http://dev.unhandledexpression.com/clever-svg.svg
How you are using Rust: we host Rust web apps (currently in beta), and a part of our infrastructure (around git and app management) is developed in Rust
Url describing Rust usage: https://www.clever-cloud.com/doc/rust/rust/
Organization contact: Geoffroy Couprie<EMAIL_ADDRESS>

Sorry about taking so long with the PR! I was out of town.

I was out of town too ;)


Remove OperationsHealth.json spec files and corresponding example files

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[x] Other, please clarify

Remove the private spec file: OperationsHealth.json with the request from the feature owner.

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[x] No refresh required for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.

[x] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

This is the request from the SQL feature owner. They want to let Operations Health API as private based on business justification. I will attend the Azure Breaking Change Review meeting on Dec 6th.

@zhenglaizhang can you help to merge it? the breaking change review board has signed off. Thanks!

@ericshape @zhenglaizhang FYI, removing the swagger files from the repo without updating the mapping.json file will cause the CI job to fail. Please see https://dev.azure.com/ceapex/Engineering/_workitems/edit/528992 for details.

@ericshape @zhenglaizhang FYI, removing the swagger files from the repo without updating the mapping.json file will cause the CI job to fail. Please see https://dev.azure.com/ceapex/Engineering/_workitems/edit/528992 for details.

Hi @kexugit sorry to block the CI. do you know how we can modify the mapping file? I can create a PR to fix it.

@ericshape @zhenglaizhang FYI, removing the swagger files from the repo without updating the mapping.json file will cause the CI job to fail. Please see https://dev.azure.com/ceapex/Engineering/_workitems/edit/528992 for details.

Hi @kexugit sorry to block the CI. do you know how we can modify the mapping file? I can create a PR to fix it.

it seems docs side already fix the issue @kexugit please correct me if I am wrong.
This is seems another reason why we need enable auto rest api doc version update.