Issues with processing climate data

Hi Lilian,
First of all, thanks a lot for all these tools. They are really exhaustive, I'm sure I'll be able to find a lot of useful stuff for my project. I'm particularly interested in the daily climate processing, temperature scaling and initialization of snow/ice fractions.
I've been following the how_to_daily_input_daily_output.ipynb notebook in order to try a few things. I'm encountering a couple of issues when trying to process daily climate data for a gdir. When I do (bear in mind that the source code here is in Julia, but all the libraries called are in Python), I get the following error:
MBsandbox = pyimport("MBsandbox.mbmod_daily_oneflowline")

PARAMS["hydro_month_nh"]=1
climate="W5E5"
MBsandbox.process_w5e5_data(gdir, climate_type=climate, temporal_resol="daily")

OSError(-101, 'NetCDF: HDF error')
  File "/Users/Bolib001/Python/oggm/oggm/utils/_workflow.py", line 490, in _entity_task
    out = task_func(gdir, **kwargs)
  File "/Users/Bolib001/Python/massbalance-sandbox/MBsandbox/mbmod_daily_oneflowline.py", line 435, in process_w5e5_data
    with xr.open_dataset(path_tmp) as ds:
  File "/Users/Bolib001/miniconda3/envs/oggm_env/lib/python3.9/site-packages/xarray/backends/api.py", line 497, in open_dataset
    backend_ds = backend.open_dataset(
  File "/Users/Bolib001/miniconda3/envs/oggm_env/lib/python3.9/site-packages/xarray/backends/netCDF4_.py", line 551, in open_dataset
    store = NetCDF4DataStore.open(
  File "/Users/Bolib001/miniconda3/envs/oggm_env/lib/python3.9/site-packages/xarray/backends/netCDF4_.py", line 380, in open
    return cls(manager, group=group, mode=mode, lock=lock, autoclose=autoclose)
  File "/Users/Bolib001/miniconda3/envs/oggm_env/lib/python3.9/site-packages/xarray/backends/netCDF4_.py", line 328, in __init__
    self.format = self.ds.data_model
  File "/Users/Bolib001/miniconda3/envs/oggm_env/lib/python3.9/site-packages/xarray/backends/netCDF4_.py", line 389, in ds
    return self._acquire()
  File "/Users/Bolib001/miniconda3/envs/oggm_env/lib/python3.9/site-packages/xarray/backends/netCDF4_.py", line 383, in _acquire
    with self._manager.acquire_context(needs_lock) as root:
  File "/Users/Bolib001/miniconda3/envs/oggm_env/lib/python3.9/contextlib.py", line 119, in __enter__
    return next(self.gen)
  File "/Users/Bolib001/miniconda3/envs/oggm_env/lib/python3.9/site-packages/xarray/backends/file_manager.py", line 187, in acquire_context
    file, cached = self._acquire_with_cache_info(needs_lock)
  File "/Users/Bolib001/miniconda3/envs/oggm_env/lib/python3.9/site-packages/xarray/backends/file_manager.py", line 205, in _acquire_with_cache_info
    file = self._opener(*self._args, **kwargs)
  File "src/netCDF4/_netCDF4.pyx", line 2307, in netCDF4._netCDF4.Dataset.__init__
  File "src/netCDF4/_netCDF4.pyx", line 1925, in netCDF4._netCDF4._ensure_nc_success
PyError ($(Expr(:escape, :(ccall(#= /Users/Bolib001/.julia/packages/PyCall/BD546/src/pyfncall.jl:43 =# @pysym(:PyObject_Call), PyPtr, (PyPtr, PyPtr, PyPtr), o, pyargsptr, kw))))) <class 'OSError'>
OSError(-101, 'NetCDF: HDF error')

After looking around a little bit, this seems to be quite a common bug, which can be due to different things: either corrupted .nc files or problems with the order of installation of the h5py and netCDF4 libraries. I have tried multiple things with no success so far. I was just wondering if you have already encountered this problem and if you know of any easy fix :)
I also tested MBsandbox.process_era5_daily_data(gdir) as suggested in the notebook, but when it just seems to run forever (I stop it after several minutes running). Is it OK to use this function or am I missing something?
Thanks a lot again!

Hi Jordi,
It is possible that MBsandbox.process_era5_daily_data(gdir) and also MBsandbox.process_w5e5_data take some time to run because when running them for the first time, they first have to download the new (daily) data. So, depending on your internet connection, this can take some time. (e.g. in case of ERA5_daily it is 662MB, note that there only temperature is daily, and for precipitation the monthly estimates are used while for W5E5 e.g., both prcp and temp are daily ... in case of W5E5 it is 2*280MB). So, for testing daily MB, you should rather use W5E5, also because my preprocessed data goes until end of 2019  for W5E5 (and for ERA5 only goes till end of 2018).
You can also check manually inside of the folders whether the data has been correctly downloaded. In my case it is under:  /home/lilianschuster/OGGM/download_cache/cluster.klima.uni-bremen.de/~lschuster/w5e5v2.0/flattened/daily  (e.g. try to open it with xarray).  If the download did not work, you could also manually download the files under this link here and drop them in the right folder. If it still does not work to open it with xarray and you can normally open stuff with xarray, then we know at least a bit better where the problem is.
I hope that helps a bit. This is all work in process, so if you encounter other problems, don't hesitate to ask further. Specifically the sfc type distinction model using a snow ageing bucket system is still not well documented.

Thanks for the quick reply! Now I'm getting a little bit more of information. The current situation is the following one:
When I run it using MBsandbox.process_w5e5_data(gdir, climate_type=climate, temporal_resol="daily") I get:
2021-09-30 17:46:00: oggm.cfg: PARAMS['hydro_month_nh'] changed from `10` to `1`.
2021-09-30 17:46:00: MBsandbox.mbmod_daily_oneflowline: (RGI60-11.01450) process_w5e5_data
2021-09-30 17:46:00: oggm.utils: No known hash for cluster.klima.uni-bremen.de/~lschuster/w5e5v2.0/flattened/daily/w5e5v2.0_tas_global_daily_flat_glaciers_1979_2019.nc
2021-09-30 17:46:00: oggm.utils: No known hash for cluster.klima.uni-bremen.de/~lschuster/w5e5v2.0/flattened/daily/w5e5v2.0_pr_global_daily_flat_glaciers_1979_2019.nc
2021-09-30 17:46:00: oggm.utils: No known hash for cluster.klima.uni-bremen.de/~lschuster/w5e5v2.0/flattened/daily/w5e5v2.0_glacier_invariant_flat.nc
2021-09-30 17:46:00: MBsandbox.mbmod_daily_oneflowline: OSError occurred during task process_w5e5_data on RGI60-11.01450: [Errno -101] NetCDF: HDF error: b'/Users/Bolib001/OGGM/download_cache/cluster.klima.uni-bremen.de/~lschuster/w5e5v2.0/flattened/daily/w5e5v2.0_tas_global_daily_flat_glaciers_1979_2019.nc'

Opening the file directly with xarray with xr.open_dataset("/Users/Bolib001/OGGM/download_cache/cluster.klima.uni-bremen.de/~lschuster/w5e5v2.0/flattened/daily/w5e5v2.0_tas_global_daily_flat_glaciers_1979_2019.nc") produces exactly the same error as above.
However, manually downloading the file from the server you sent me and opening with xarray works with no issues. To me, it looks like the issue comes from the automatically downloaded file from process_w5e5_data. FYI, I didn't have any issues when downloading the "classic" monthly CRU data from OGGM.

Hi Jordi,
Thanks for reporting back.  I also just tested to delete the files and do process_w5e5_data: for me, it downloads the files normally and I can work with them afterwards. If this works for you, you can just go the manual way: via manually putting the files in the right folder, then when you do process_w5e5_data, oggm won't download the files again and you can then hopefully work with the climate files. But I will ask Fabien next week how to solve this. Probably this has something to do that I do not have any hash for that ... or, as you get an OSError, it might also be a problem from the path description, do you use linux, I have only tested it in linux systems?

What can happen is that the files are only partly downloaded if the user breaks the process while running, which could lead to the HDF errors reported here.
These files are probably not yet in the "verified" list (where we check for hashes) - probably we should add them soon

OK, so I manually placed the files in the default folder and it solved the issue. The automatically downloaded files might be somehow corrupted.
Thanks a lot for the help! Shall I keep the issue open?


migrate protos

As referenced in #381 this will reference protos in the dapr/dapr repo rather than being copied.
Merging this will close #381
Signed-off-by: mikeee<EMAIL_ADDRESS>

@mikeee can you fix the PR? we want to migrate the protos from dapr/dapr for the upcoming 1.12 release

Sure, sorry it's been on my to-do. I'll rework it today

@yaron2 ready for your eyes

Thanks!


skip save dialog on quit if buffer is shared

Currently, when a modified buffer is closed, the user is asked if the buffer should be saved. This happens even if the same file is opened in another buffer. With this PR, the save dialog is skipped in this case. I personally like to open a file in a second buffers when I made modifications that affect two locations. Then this issue pops up.

Thanks for addressing this, this issue has been occasionally annoying me as well.


Package swiftmailer/swiftmailer is abandoned, you should avoid using it. Use symfony/mailer instead.

i got this error while installing this extension
Package swiftmailer/swiftmailer is abandoned, you should avoid using it. Use symfony/mailer instead.
[master_0]:public_html$ composer require fof/cookie-consent
Using version ^1.0 for fof/cookie-consent
./composer.json has been updated
Running composer update fof/cookie-consent
Loading composer repositories with package information
Updating dependencies
Lock file operations: 1 install, 0 updates, 0 removals
  - Locking fof/cookie-consent (1.0.2)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 1 install, 0 updates, 0 removals
  - Downloading fof/cookie-consent (1.0.2)
  - Installing fof/cookie-consent (1.0.2): Extracting archive
Package swiftmailer/swiftmailer is abandoned, you should avoid using it. Use symfony/mailer instead.
Generating autoload files
102 packages you are using are looking for funding.
Use the `composer fund` command to find out more!

This output is expected, everything went well and the extension should be available in the admin panel.
The swiftmailer/swiftmailer warning is caused by Flarum itself and will be present in all Composer outputs for all extensions. It has to be fixed in the upstream Laravel package first, then Flarum will be able to use that new version and get rid of the message. It might take a few more Flarum releases until it disappears.
If there's any issue with the extension itself let us know and we'll take a look!


Load caffe without caffe dependency?

Just like https://github.com/szagoruyko/loadcaffe in torch7, there is no need to install caffe. Can mxnet do this? Currently, I just find caffe converter in mxnet, but need caffe installed.

I took a look at this:
https://github.com/szagoruyko/torch-caffe-binding
https://github.com/szagoruyko/loadcaffe
They looks like good reference. Maybe people working on caffe bindings can use this.
@jermainewang

I think it can be done by compile the official caffe protobuf caffe.proto to get the caffe_pb2.py file, which can do the parsing. https://github.com/kitofans/caffe-theano-conversion is also a good reference.

closed by #620


"Product Design" page text cut-off

I'm look at the Product Design page, and I'm seeing two small errors:

Small typo in the "Value Proposition" section

product: what needs to be build to help our users reach their goals?

The article stops abruptly mid-sentence, see below

Fixed, thanks @emmyscode! There will likely be more -- wish VSCode had a Google docs type of grammar/language checker.


[quick fix] Add help for updated expected output files #188_110

Motivation

Added help message for all tests but the prover
The provers test logic is a bit more custom
And I think it already has a message

Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
CI/CD tests are covered.

/canary

:sunny: Canary successful

/land


0.1.7版本装不上~·

压缩包解压后提示  不存在~

Which platform are you using? I tested the zip file for Windows and did not reproduce same situation.

[BingGPT-0.1.7-win32-x64-Setup.exe]
[BingGPT-0.1.7-win32-x64.zip]
Thank you. I tried the two methods before, but just now I downloaded and extracted it again, and found that it worked.
Thank you very much for your response!


fix(udf): ensure always_retry_on_network_error does so for all tonic errors (#15458)

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
closes https://github.com/risingwavelabs/risingwave/issues/15494
cherry pick #15458

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

Can't update the branch, since there's a release prefix. Pushing a new one.


How do I get Electrum to run?

Discussed in https://github.com/raspiblitz/raspiblitz/discussions/4355

Originally posted by Nerfzooka January  7, 2024
Before I show you a wall of debug text, take a look at what AI thinks a PCB centerpiece looks like:

Allright!  The old rpi node was running slow so I decided to give it a new sd card.  My wallets are set to connect to my node but they can't sync up.  The wallets say "no connection", the node says Electrum : Not running.
I tried to add a "sudo journalctl -u electrs" output but it wouldn't fit in the discussion window.
Here's a debug output:
*************************************************************** * RASPIBLITZ DEBUG LOGS  *************************************************************** blitzversion: 1.10.0 chainnetwork: bitcoin / main  20:09:27 up 1 day,  2:38,  1 user,  load average: 0.99, 1.20, 1.19  *** FAILED SERVICES *** list any servcies with problems: sudo systemctl list-units --failed   UNIT             LOAD   ACTIVE SUB    DESCRIPTION ● bitcoind.service loaded failed failed Bitcoin daemon on mainnet  LOAD   = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB    = The low-level unit activation state, values depend on unit type. 1 loaded units listed.  *** SETUPPHASE / BOOTSTRAP *** see logs: cat /home/admin/raspiblitz.log setupPhase--> done state--> ready  *** BACKGROUNDSERVICE *** to monitor Background service call: sudo journalctl -f -u background  *** BLOCKCHAIN (MAINNET) SYSTEMD STATUS *** ● bitcoind.service - Bitcoin daemon on mainnet      Loaded: loaded (/etc/systemd/system/bitcoind.service; enabled; vendor preset: enabled)      Active: failed (Result: exit-code) since Sun 2024-01-07 17:21:00 GMT; 2h 48min ago     Process: 3536647 ExecStartPre=/home/admin/config.scripts/bitcoin.check.sh prestart mainnet (code=exited, status=0/SUCCESS)     Process: 3536666 ExecStart=/usr/local/bin/bitcoind -daemonwait -conf=/mnt/hdd/bitcoin/bitcoin.conf -datadir=/mnt/hdd/bitcoin (code=exited, status=1/FAILURE)         CPU: 222ms  Jan 07 17:21:00 raspberrypi systemd[1]: bitcoind.service: Failed with result 'exit-code'. Jan 07 17:21:00 raspberrypi systemd[1]: Failed to start Bitcoin daemon on mainnet.  *** LAST BLOCKCHAIN (MAINNET) ERROR LOGS *** sudo journalctl -u bitcoind -b --no-pager -n20 -- Journal begins at Thu 2023-09-21 22:59:15 BST, ends at Sun 2024-01-07 20:09:27 GMT. -- Jan 07 17:20:59 raspberrypi systemd[1]: bitcoind.service: Control process exited, code=exited, status=1/FAILURE Jan 07 17:20:59 raspberrypi systemd[1]: bitcoind.service: Failed with result 'exit-code'. Jan 07 17:20:59 raspberrypi systemd[1]: Failed to start Bitcoin daemon on mainnet. Jan 07 17:20:59 raspberrypi systemd[1]: bitcoind.service: Scheduled restart job, restart counter is at 6. Jan 07 17:20:59 raspberrypi systemd[1]: Stopped Bitcoin daemon on mainnet. Jan 07 17:20:59 raspberrypi systemd[1]: Starting Bitcoin daemon on mainnet... Jan 07 17:20:59 raspberrypi bitcoin.check.sh[3536651]: /bin/chgrp: changing group of '/mnt/hdd/bitcoin': Read-only file system Jan 07 17:20:59 raspberrypi bitcoin.check.sh[3536654]: sed: couldn't open temporary file /mnt/hdd/bitcoin/sedenDphp: Read-only file system Jan 07 17:20:59 raspberrypi bitcoin.check.sh[3536655]: sed: couldn't open temporary file /mnt/hdd/bitcoin/sedvl0I4r: Read-only file system Jan 07 17:20:59 raspberrypi bitcoin.check.sh[3536658]: sed: couldn't open temporary file /mnt/hdd/bitcoin/sedbRPC6E: Read-only file system Jan 07 17:20:59 raspberrypi bitcoind[3536666]: Error: Settings file could not be written: Jan 07 17:20:59 raspberrypi bitcoind[3536666]: - Error: Unable to open settings file /mnt/hdd/bitcoin/settings.json.tmp for writing Jan 07 17:20:59 raspberrypi systemd[1]: bitcoind.service: Control process exited, code=exited, status=1/FAILURE Jan 07 17:20:59 raspberrypi systemd[1]: bitcoind.service: Failed with result 'exit-code'. Jan 07 17:20:59 raspberrypi systemd[1]: Failed to start Bitcoin daemon on mainnet. Jan 07 17:21:00 raspberrypi systemd[1]: bitcoind.service: Scheduled restart job, restart counter is at 7. Jan 07 17:21:00 raspberrypi systemd[1]: Stopped Bitcoin daemon on mainnet. Jan 07 17:21:00 raspberrypi systemd[1]: bitcoind.service: Start request repeated too quickly. Jan 07 17:21:00 raspberrypi systemd[1]: bitcoind.service: Failed with result 'exit-code'. Jan 07 17:21:00 raspberrypi systemd[1]: Failed to start Bitcoin daemon on mainnet.  *** LAST BLOCKCHAIN (MAINNET) INFO LOGS *** sudo tail -n 50 /mnt/hdd/bitcoin/debug.log 2024-01-07T16:08:47Z UpdateTip: new best=00000000000000000001c846ebb61f86e426b3eb89d700ffbe09330bb1b41582 height=824761 version=0x20600000 log2_work=94.651530 tx=948948620 date='2024-01-07T16:08:20Z' progress=1.000000 cache=307.1MiB(2150145txo) 2024-01-07T16:08:59Z Saw new header hash=00000000000000000000cd95c5aef11bfda45ab92b646eadbfe385cd4c08de1b height=824762 2024-01-07T16:08:59Z [net] Saw new cmpctblock header hash=00000000000000000000cd95c5aef11bfda45ab92b646eadbfe385cd4c08de1b peer=455 2024-01-07T16:09:01Z UpdateTip: new best=00000000000000000000cd95c5aef11bfda45ab92b646eadbfe385cd4c08de1b height=824762 version=0x3fff0000 log2_work=94.651544 tx=948951996 date='2024-01-07T16:08:49Z' progress=1.000000 cache=307.7MiB(2154869txo) 2024-01-07T16:10:09Z Saw new header hash=000000000000000000015f9a06caa0ee6cffc3fe8b654d9e2b4df6210bdab9a8 height=824763 2024-01-07T16:10:09Z [net] Saw new cmpctblock header hash=000000000000000000015f9a06caa0ee6cffc3fe8b654d9e2b4df6210bdab9a8 peer=455 2024-01-07T16:10:11Z UpdateTip: new best=000000000000000000015f9a06caa0ee6cffc3fe8b654d9e2b4df6210bdab9a8 height=824763 version=0x29a2e000 log2_work=94.651559 tx=948954811 date='2024-01-07T16:09:59Z' progress=1.000000 cache=308.3MiB(2158665txo) 2024-01-07T16:12:32Z New outbound peer connected: version: 70016, blocks=824763, peer=1766 (block-relay-only) 2024-01-07T16:20:18Z Saw new header hash=00000000000000000002124c17bbf75b5807bdf092cfbde335243bb8f2bb39a2 height=824764 2024-01-07T16:20:21Z UpdateTip: new best=00000000000000000002124c17bbf75b5807bdf092cfbde335243bb8f2bb39a2 height=824764 version=0x32868000 log2_work=94.651573 tx=948958511 date='2024-01-07T16:19:59Z' progress=1.000000 cache=309.5MiB(2167516txo) 2024-01-07T16:43:56Z New outbound peer connected: version: 70016, blocks=824764, peer=1801 (block-relay-only) 2024-01-07T16:45:41Z Saw new header hash=00000000000000000003860b9bb6e7705e01ff312e8483dc53fe24249464c6b7 height=824765 2024-01-07T16:45:41Z [net] Saw new cmpctblock header hash=00000000000000000003860b9bb6e7705e01ff312e8483dc53fe24249464c6b7 peer=455 2024-01-07T16:45:43Z UpdateTip: new best=00000000000000000003860b9bb6e7705e01ff312e8483dc53fe24249464c6b7 height=824765 version=0x225c8000 log2_work=94.651588 tx=948961739 date='2024-01-07T16:45:26Z' progress=1.000000 cache=311.6MiB(2182927txo) 2024-01-07T16:45:51Z New outbound peer connected: version: 70016, blocks=824765, peer=1804 (block-relay-only) 2024-01-07T16:46:18Z Saw new header hash=0000000000000000000267a992e2ccb9f30bf5f3e50a85e19f20cc635250f631 height=824766 2024-01-07T16:46:19Z New outbound peer connected: version: 70016, blocks=824765, peer=1806 (outbound-full-relay) 2024-01-07T16:46:20Z UpdateTip: new best=0000000000000000000267a992e2ccb9f30bf5f3e50a85e19f20cc635250f631 height=824766 version=0x2f036000 log2_work=94.651602 tx=948964846 date='2024-01-07T16:46:03Z' progress=1.000000 cache=312.1MiB(2186516txo) 2024-01-07T16:46:24Z New outbound peer connected: version: 70016, blocks=824766, peer=1807 (block-relay-only) 2024-01-07T16:48:51Z Socks5() connect to ***.onion:8333 failed: host unreachable 2024-01-07T16:51:00Z New outbound peer connected: version: 70016, blocks=824766, peer=1819 (outbound-full-relay) 2024-01-07T16:53:06Z Socks5() connect to ***.onion:8333 failed: general failure 2024-01-07T16:54:49Z New outbound peer connected: version: 70016, blocks=824766, peer=1824 (block-relay-only) 2024-01-07T16:59:19Z New outbound peer connected:
Thanks for looking, any ideas as to what's wrong?

Here, the "sudo journalctl -u electrs" output boiled down, it's this message repeated about 780 times :
-- Boot 634e0ec47bcf4153b2e7fbcdd1d8140b --
Jan 14 16:43:40 raspberrypi systemd[1]: Started Electrs.
Jan 14 16:43:41 raspberrypi electrs[30991]: Starting electrs 0.10.0 on aarch64 linux with Config { network: Bitcoin, db_path: "/mnt/hdd/app-storage/electrs/db/bitcoin", daemon_dir: "/home/electrs/.bitcoin", daemon_auth: UserPass("raspibolt", ""), daemon_rpc_addr: <IP_ADDRESS>:8332, daemon_p2p_addr: <IP_ADDRESS>:8333, electrum_rpc_addr: <IP_ADDRESS>:50001, monitoring_addr: <IP_ADDRESS>:4224, wait_duration: 10s, jsonrpc_timeout: 15s, index_batch_size: 10, index_lookup_limit: None, reindex_last_blocks: 0, auto_reindex: true, ignore_mempool: false, sync_once: false, skip_block_download_wait: false, disable_electrum_rpc: false, server_banner: "Welcome to electrs v0.10.0 - the Electrum Rust Server on your RaspiBlitz", signet_magic: f9beb4d9, args: [] }
Jan 14 16:44:08 raspberrypi electrs[30991]: Error: electrs failed
Jan 14 16:44:08 raspberrypi electrs[30991]: Caused by:
Jan 14 16:44:08 raspberrypi electrs[30991]: 0: bitcoind RPC polling failed
Jan 14 16:44:08 raspberrypi electrs[30991]: 1: daemon not available
Jan 14 16:44:08 raspberrypi electrs[30991]: 2: JSON-RPC error: transport error: Couldn't connect to host: Resource temporarily unavailable (os error 11)
Jan 14 16:44:08 raspberrypi systemd[1]: electrs.service: Main process exited, code=exited, status=1/FAILURE
Jan 14 16:44:08 raspberrypi systemd[1]: electrs.service: Failed with result 'exit-code'.
Jan 14 16:44:08 raspberrypi systemd[1]: electrs.service: Consumed 10.939s CPU time.
Jan 14 16:45:09 raspberrypi systemd[1]: electrs.service: Scheduled restart job, restart counter is at 1.
Jan 14 16:45:09 raspberrypi systemd[1]: Stopped Electrs.
Jan 14 16:45:09 raspberrypi systemd[1]: electrs.service: Consumed 10.939s CPU time.
Jan 14 16:45:09 raspberrypi systemd[1]: Started Electrs.
Jan 14 16:45:09 raspberrypi electrs[33467]: Starting electrs 0.10.0 on aarch64 linux with Config { network: Bitcoin, db_path: "/mnt/hdd/app-storage/electrs/db/bitcoin", daemon_dir: "/home/electrs/.bitcoin", daemon_auth: UserPass("raspibolt", ""), daemon_rpc_addr: <IP_ADDRESS>:8332, daemon_p2p_addr: <IP_ADDRESS>:8333, electrum_rpc_addr: <IP_ADDRESS>:50001, monitoring_addr: <IP_ADDRESS>:4224, wait_duration: 10s, jsonrpc_timeout: 15s, index_batch_size: 10, index_lookup_limit: None, reindex_last_blocks: 0, auto_reindex: true, ignore_mempool: false, sync_once: false, skip_block_download_wait: false, disable_electrum_rpc: false, server_banner: "Welcome to electrs v0.10.0 - the Electrum Rust Server on your RaspiBlitz", signet_magic: f9beb4d9, args: [] }
Jan 14 16:45:35 raspberrypi electrs[33467]: Error: electrs failed
Jan 14 16:45:35 raspberrypi electrs[33467]: Caused by:
Jan 14 16:45:35 raspberrypi electrs[33467]: 0: bitcoind RPC polling failed
Jan 14 16:45:35 raspberrypi electrs[33467]: 1: daemon not available
Jan 14 16:45:35 raspberrypi electrs[33467]: 2: JSON-RPC error: transport error: Couldn't connect to host: Resource temporarily unavailable (os error 11)
Jan 14 16:45:35 raspberrypi systemd[1]: electrs.service: Main process exited, code=exited, status=1/FAILURE
Jan 14 16:45:35 raspberrypi systemd[1]: electrs.service: Failed with result 'exit-code'.
Jan 14 16:45:35 raspberrypi systemd[1]: electrs.service: Consumed 9.434s CPU time.
Jan 14 16:46:35 raspberrypi systemd[1]: electrs.service: Scheduled restart job, restart counter is at 2.
Jan 14 16:46:35 raspberrypi systemd[1]: Stopped Electrs.
Jan 14 16:46:35 raspberrypi systemd[1]: electrs.service: Consumed 9.434s CPU time.
Jan 14 16:46:35 raspberrypi systemd[1]: Started Electrs.
Jan 14 16:46:35 raspberrypi electrs[34901]: Starting electrs 0.10.0 on aarch64 linux with Config { network: Bitcoin, db_path: "/mnt/hdd/app-storage/electrs/db/bitcoin", daemon_dir: "/home/electrs/.bitcoin", daemon_auth: UserPass("raspibolt", ""), daemon_rpc_addr: <IP_ADDRESS>:8332, daemon_p2p_addr: <IP_ADDRESS>:8333, electrum_rpc_addr: <IP_ADDRESS>:50001, monitoring_addr: <IP_ADDRESS>:4224, wait_duration: 10s, jsonrpc_timeout: 15s, index_batch_size: 10, index_lookup_limit: None, reindex_last_blocks: 0, auto_reindex: true, ignore_mempool: false, sync_once: false, skip_block_download_wait: false, disable_electrum_rpc: false, server_banner: "Welcome to electrs v0.10.0 - the Electrum Rust Server on your RaspiBlitz", signet_magic: f9beb4d9, args: [] }
Jan 14 16:47:02 raspberrypi electrs[34901]: Error: electrs failed
Jan 14 16:47:02 raspberrypi electrs[34901]: Caused by:
Jan 14 16:47:02 raspberrypi electrs[34901]: 0: bitcoind RPC polling failed
Jan 14 16:47:02 raspberrypi electrs[34901]: 1: daemon not available
Jan 14 16:47:02 raspberrypi electrs[34901]: 2: JSON-RPC error: transport error: Couldn't connect to host: Resource temporarily unavailable (os error 11)
Jan 14 16:47:02 raspberrypi systemd[1]: electrs.service: Main process exited, code=exited, status=1/FAILURE
Jan 14 16:47:02 raspberrypi systemd[1]: electrs.service: Failed with result 'exit-code'.
Jan 14 16:47:02 raspberrypi systemd[1]: electrs.service: Consumed 10.537s CPU time.
Jan 14 16:48:02 raspberrypi systemd[1]: electrs.service: Scheduled restart job, restart counter is at 3.
Jan 14 16:48:02 raspberrypi systemd[1]: Stopped Electrs.
Jan 14 16:48:02 raspberrypi systemd[1]: electrs.service: Consumed 10.537s CPU time.

So electrs seems to have problems calling bitcoind .. the bitcoin debug logs were hard to read so I pumped it thru ChatGPT and it says:
The log you provided gives some important insights into why bitcoind, the Bitcoin daemon, is not running on your Raspberry Pi. The key points to note are:

Read-Only File System Errors:

chgrp: changing group of '/mnt/hdd/bitcoin': Read-only file system
sed: couldn't open temporary file /mnt/hdd/bitcoin/sed...: Read-only file system

These lines suggest that the file system where the Bitcoin data is stored (/mnt/hdd/bitcoin) has become read-only. This is often a protective measure taken by the operating system when it detects some kind of file system corruption or I/O error, typically with the physical storage device (like an SD card or HDD/SSD).

Bitcoin Daemon Unable to Write Settings File:

Error: Settings file could not be written:
Error: Unable to open settings file /mnt/hdd/bitcoin/settings.json.tmp for writing

This indicates that bitcoind is trying to write to the settings file but is unable to do so because of the read-only status of the file system.

Repeated Failure and Restart Attempts:
The log shows that the bitcoind service has repeatedly tried and failed to start, indicated by the multiple entries of Failed to start Bitcoin daemon on mainnet.

Other Blockchain Logs Appear Normal:
The logs related to blockchain updates and peer connections (UpdateTip: new best=..., Saw new header hash=..., New outbound peer connected:...) appear normal up to a certain point. This suggests that bitcoind was functioning correctly until it encountered the read-only file system issue.

Given these points, the primary issue seems to be with the file system or the storage device where your Bitcoin data is located. To address this, you can try the following steps:

Check and Repair the File System: Use tools like fsck (for Linux file systems) to check and repair any errors on the file system. This should be done with caution and ideally after taking a backup, if possible.

Check the Health of the Storage Device: If you're using an SD card or an HDD/SSD, check its health. SD cards, in particular, have a limited lifespan and can become unreliable over time.

Ensure Adequate Power Supply: Insufficient power supply to Raspberry Pi and connected storage devices can cause file system corruption. Make sure your power supply is adequate and stable.

Backup and Restore: If you have a backup of your Bitcoin data, you might need to restore it after fixing the file system or replacing the storage device.

Consult Raspberry Pi and Bitcoin Community Forums: If the problem persists, consider seeking advice from Raspberry Pi and Bitcoin community forums where you might find others who have faced similar issues.

Remember that dealing with file system issues and potential data corruption should be approached with caution, especially when it involves valuable data like a Bitcoin blockchain.


Mastertherm nenacteno po aktualizaci ha core update 6.12.2023

System Health details
viz predmet
Checklist

[X] I have given details of my install including what type of system airsource/ watersource or groundsource
[X] I have provided logs showing any errors.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of currently previous issues..

Describe the issue
po posledni aktualizacu pise mastertherm integrace, ze nebyla nactena.
Reproduction steps

...
nelze
Logs
nelze

Diagnostics dump, if available
nelze

Should be resolved in 1.1.8


Upgrade CF-deployer to 1.3.1

Local build with the tests run successfully.
Resolves spring-cloud/spring-cloud-dataflow-server-cloudfoundry#393

Was already applied. Closing.


Show number of rows processed on Validation Results page

Provide confidence that the whole file was processed especially when you use the "Validate Again" button and the CSV behind the URL may have changed in size.
Important to know if processing completed or a large file size resulted in only part of the file being processed. Especially given the warning on the /About page

this is a small fix that is currently stalled due to below

[  ]  resolve CSVlint .env to run locally without problems noted in #281
with planned additions of
[  ] write tests for stress test fixtures (multiples of 1000 rows and 1MB and 10MB file size)


MemoryError using slurm in mmdet

I ran my code using slurm. And the erroy is as floow:
Traceback (most recent call last):  File "<string>", line 1, in <module>  File "/mnt/lustre/share/platform/env/miniconda3/lib/python3.7/multiprocessing/spawn.py", line 105, in spawn_main    exitcode = _main(fd)  File "/mnt/lustre/share/platform/env/miniconda3/lib/python3.7/multiprocessing/spawn.py", line 115, in _main    self = reduction.pickle.load(from_parent) MemoryErrorTraceback (most recent call last):   File "<string>", line 1, in <module>  File "/mnt/lustre/share/platform/env/miniconda3/lib/python3.7/multiprocessing/spawn.py", line 105, in spawn_main     exitcode = _main(fd)  File "/mnt/lustre/share/platform/env/miniconda3/lib/python3.7/multiprocessing/spawn.py", line 115, in _main     self = reduction.pickle.load(from_parent)MemoryError
the dataset is large(about 450G), I have the following guesses:

The maximum amount of memory that can be allocated exceeds the limit that slrum can allocate.
As shown in the error,

mp.set_start_method ('spawn')

was called during distributed training, which resulted in some errors that I couldn't solve.
What is the possible cause. And how do I troubleshoot them? thanks a lot!

This seems to be the bug/limit of the machine, I think I met this problem before when the annotations or proposals files are large, you could change another machine/cluster or try to reduce the loading overload at the beginning.


Localize Health Summary PDF

Localize Health Summary PDF
:recycle: Current situation & Problem
The Health Summary didn't really contain any localization and also the dynamic texts for the symptom score summary weren't dynamic.
:gear: Release Notes
Add a bullet point list summary of the feature and possible migration guides if this is a breaking change so this section can be added to the release notes.
Include code snippets that provide examples of the feature implemented or links to the documentation if it appends or changes the public interface.
:books: Documentation
Please ensure that you properly document any additions in conformance to Spezi Documentation Guide.
You can use this section to describe your solution, but we encourage contributors to document your reasoning and changes using in-line documentation.
:white_check_mark: Testing
Please ensure that the PR meets the testing requirements set by CodeCov and that new functionality is appropriately tested.
This section describes important information about the tests and why some elements might not be testable.
Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines:

[x] I agree to follow the Code of Conduct and Contributing Guidelines.

Open Questions:

In which order should the symptom scores be displayed? Newest on top or at the bottom? The current version has newest on top, but then the oldest one is bold, which doesn't really make sense.


.toHaveProperty() does not distinguish between any and never

Playground link
.toHaveProperty() does not distinguish between any and never. See the link above.
It sound like never should not have any properties. Might be I missed something.

@mrazauskas Technically both keyof never and keyof any resolve to string | number | symbol. Not sure if it would be the best idea to stray away from TypeScript's intended behavior but you're right. Semantically it doesn't make sense. It seems like keyof never should be never. Not sure what the best approach here would be to be honest.


Support for Span/Div

Currently we default to a div for any unknown directive, there are times especially as we are starting to build custom directives that we need more flexibility on spans/divs with custom styles. This should probably be the default fallback for directives/roles respectively.

These are now released in the theme side, still no directives for these at the moment.

Div is supported through #1140.

We have also added better support in html parsing, which means that html styles are now applied:
## Complex Tables with Style

creates:

I am going to close this, and we can reopen with further requests.

@rowanc1 This works great, thank you!


InvalidTokenException serialized as XML instead of JSON

When testing failure scenarios for token the InvalidTokenException is being sent back as XML instead of JSON. I get the following:
<InvalidTokenException><error>invalid_token</error><error_description>Cannot convert access token to JSON</error_description></InvalidTokenException>
when I expect JSON.  Is there some config option I'm missing here?

any resolution of config option for JSON serialization?

setting header attribute "Accept" : "application/json" solved the problem. Is there any better way to implement this as default behavior. I tried to override WebMvcConfiguration to set content negotiation strategy as FixedContentNegotiationStrategy with default content type as "application/json", which didn't work.

@kshitij-kasliwal Did you get any workaround on this ?


Reset Purchased Items

hi how can i reset purchsed items? I just want to test it but i get always "PurchasedSuccessfully"

You can use consumePurchase


GH1311: Add support for Inno Setup

Fixes #1311
This is a minimal implementation, I haven't implemented mappings for all command-line switches yet.

A large part of the code is copied and adapted from the NSIS-related code, since NSIS and Inno Setup work in very similar ways.
I was also wondering: is there any mechanism in Cake to locate tools in their default installation directory? The default installation path for InnoSetup is C:\Program Files (x86)\Inno Setup 5, is there a way to automatically look for iscc.exe in that folder?

@thomaslevesque, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, DNFBOT;

@thomaslevesque Yes there is. Take a look at the MSBuild tool for example: https://github.com/cake-build/cake/blob/develop/src/Cake.Common/Tools/MSBuild/MSBuildRunner.cs#L254

@thomaslevesque Ping us when you're ready with this PR and someone will review it. Thanks!

@thomaslevesque Yes there is. Take a look at the MSBuild tool for example: https://github.com/cake-build/cake/blob/develop/src/Cake.Common/Tools/MSBuild/MSBuildRunner.cs#L254

Ah, thanks! I'll implement it then.

All done, I think; ready to review!

@thomaslevesque if you can fix up the suggestions from @patriksvensson we can get this merged in, ready for the next release.  Thanks!

@patriksvensson I made fixup commits to address your comments; I'll squash them after you review them.

@thomaslevesque If you squash your commits we can merge this. 👍

Squashing just the fixup commits didn't work too well, I was getting weird conflicts. Eventually I just squashed everything to a single commit.

Thanks for your contribution! Awesome work! 👍

Thanks for the merge!


Add stack links

close: https://github.com/appcelerator/amp/issues/597
Adds a get method to the stack api that returns the stack information from etcd.
Adds a link command to the cli that uses the api
Adds a link section to the ui that uses the api

Lets stick with amp stack urls . . . even if we latter change it I don't see any issue leaving urls as an alias


Errors while loading the saved state

I am new to both game dev and github.
Dunno if this is the right place for this.
But i need help.
Can't seem to find ink and java integration anywhere on the web but here.
I followed the instructions as given in the README.md file of this repo.
I got a sample .ink file from the inkle repo.
The game runs properly.
Saves too, using the code
 String saveState = story.getState().toJson();

but
when i try to load the saved file with code
  story.getState().loadJson("save.json");

It throws the error saying Ink version number not found.
I do not understand what is going on.
This is my entire code. I know it is all over and place and messy. But please help me.

import com.bladecoder.ink.runtime.*;
import java.io.BufferedReader;
import java.io.File;
import java.io.FileWriter;
import java.io.IOException;
import java.io.InputStream;
import java.io.InputStreamReader;
import java.util.Scanner;

public class InkTest {

    public static void main(String[] args) throws Exception {

        InkTest it = new InkTest();
        it.loadJSON();
    }

    public void loadJSON() throws IOException, Exception {
        File file = new File("save.json");
        System.out.print(System.getProperty("user.dir"));
        FileWriter f = new FileWriter(file);
        Scanner in = new Scanner(System.in);
        String saveState = " ";

        StringBuilder sb;
        String filename = "intercept.json";
        InputStream is = ClassLoader.getSystemResourceAsStream(filename);
        InputStreamReader isr = new InputStreamReader(is, "UTF-8");
        try (BufferedReader br = new BufferedReader(isr)) {
            sb = new StringBuilder();
            String line = br.readLine();

            while (line != null) {
                sb.append(line);
                sb.append("\n");
                line = br.readLine();
            }

        }

        String json = sb.toString().replace('\uFEFF', ' ');
        Story story = new Story(json);

        if (file.exists() && !file.isDirectory()) {
            sb = new StringBuilder();
            is = ClassLoader.getSystemResourceAsStream("save.json");
            isr = new InputStreamReader(is, "UTF-8");
            try (BufferedReader br = new BufferedReader(isr)) {
                String line = br.readLine();
                sb.append(line);
            }
            saveState=sb.toString();
            story.getState().loadJson(saveState);
        }

        while (story.canContinue()) {
            String line = story.Continue();
            System.out.print(line);
            if (story.getCurrentChoices().size() > 0) {
                System.out.println("\n");
                for (int i = 0; i < story.getCurrentChoices().size(); ++i) {
                    Choice choice = story.getCurrentChoices().get(i);
                    System.out.println("\tChoice " + (i) + ". " + choice.getText());
                }

                int n = in.nextInt();
                if (n > 35) {
                    break;
                }
                story.chooseChoiceIndex(n);
            }
            saveState = story.getState().toJson();
            f.write(saveState);
        }
    }

}

I think that you are reading only the first line of the saved game, you need to put a while loop...


Full page modal: not opening properly in iTwinUI storybook

Describe the bug (actual behavior)
When clicking "Full page modal" and going to "Canvas". Modal slides up and disappears from screen:
https://user-images.githubusercontent.com/122555873/213699629-04af2b07-88b8-440e-89ff-88aadb0eca9c.mp4
When switching to "Docs" the animation is a bit jumpy and slides in from top of the screen instead of bottom:
https://user-images.githubusercontent.com/122555873/213699620-21457c09-7d47-4182-852c-a62ccbfd92f4.mp4
Browser: Chrome Version 109.0.5414.75 (Official Build) (64-bit)
Laptop: HP ZBook 15 (system information will follow)
Expected behavior
Note that the full page modal is working correctly in the CSS iTwinUI library for me:
https://user-images.githubusercontent.com/122555873/213700695-ea489165-b751-4f79-8e2d-704c2568c2b5.mp4
Steps to reproduce

Open: https://itwin.github.io/iTwinUI/react/?path=/story/core-modal--full-page-modal
Make sure the switch in top left is on "Canvas"
Click on button to open full page modal

Additional information
--

This is interesting. The animation is a bit jumpy for me but I cannot reproduce it going out of screen completely.

I just noticed that when the bug happened, my Google Chrome was still on version: Version 108.0.5359.126 (Official Build) (64-bit)
Now it's updated to: Version 109.0.5414.75 (Official Build) (64-bit) and now the modal doesn't slide out of the screen anymore!

I can't seem to reproduce this bug either.
Laptop: HP ZBook 15
Chrome version: Version 111.0.5563.65 (Official Build) (64-bit)
Gif:

Tested in: regular mode, incognito mode, all different canvas background settings, dark and light mode

@Chrissy-L This issue has been resolved in v2.8.0.


Container Registry support?

hello
does this role currently allow gitea Docker "Container Registry" as recently submitted in this PR?
https://docs.gitea.io/en-us/packages/container/
https://github.com/go-gitea/gitea/pull/16510

looks like the docs are ahead of the releases
v1.17 possibly?
https://discourse.gitea.io/t/github-packages-equivalent/2901/2

Container regestry support in gitea sounds like a cool feature.
By just looking at the pull request and the container regestry doc I'm not quite sure what it takes in gitea to use this. The way I currently interpret this config file, it seems that you just have to set a config value to true or false for container regestry support once version 1.17 of gitea is released.
See https://github.com/KN4CK3R/gitea/blob/16f8940b37a224592e46c5fa9d60b2ed6d4a5496/custom/conf/app.example.ini#L2248-L2250
If this is the case, then this is currently already supported with the ansible role here. Since you can configure variables that are not defined by the *_extra_config parameter.
A possible configuration could look like this:
gitea_extra_config:  |
  [packages]
  ENABLED = true

As soon as there is a gitea version with container support, we can also include the most important variables in ansible. But I would wait until the actual release.

yes, the fact Gitea added the documentation for the feature makes me optimistic it will be released sooner than later

BTW,  Package Registry support is nativ built in in gitea and enabled by default.
Since https://github.com/roles-ansible/ansible_role_gitea/releases/tag/v3.0.0 there are some variables available to modify or disable it.


Feature/readme

Description

Related Issue

Motivation and Context

Screenshots (if appropriate)
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation Update (if none of the other choices apply)

Checklist

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.

Codecov Report

Merging #1349 (65811dc) into main (abf95a9) will increase coverage by 0.24%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1349      +/-   ##
==========================================
+ Coverage   45.47%   45.72%   +0.24%
==========================================
  Files         140      140
  Lines       11967    11975       +8
==========================================
+ Hits         5442     5475      +33
+ Misses       5904     5876      -28
- Partials      621      624       +3

Flag
Coverage Δ

Object-compatibility-e2etests
?

e2etests
?

unittests
45.72% <ø> (+0.24%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

cdn/supervisor/progress/progress.go
90.62% <0.00%> (-6.25%)
:arrow_down:

...ent/daemon/peer/peertask_piecetask_synchronizer.go
48.91% <0.00%> (+1.29%)
:arrow_up:

client/daemon/storage/local_storage.go
30.33% <0.00%> (+2.25%)
:arrow_up:

client/daemon/peer/peertask_piecetask_poller.go
47.10% <0.00%> (+16.66%)
:arrow_up:


Corrupt bitstream when bitrate is set too high

Tested with a 720p clip setting --bitrate 24000 (i.e. 24 Mbps).
I have been able to reproduce this with several different clips, and it seems (under investigation) that even setting a lower bitrate has a chance of generating a corrupt bitstream (presumably from spikes), though it is not as consistent.
command line:
cargo run --release -- 720.y4m --tile-rows 2 --tile-cols 2 -s 4 -l 120 --min-quantizer 20 --quantizer 170 --bitrate 24000 -o 720.ivf

mpv/ffmpeg output:
[ffmpeg/video] libaom-av1: Failed to decode frame: Bitstream not supported by this decoder
[ffmpeg/video] libaom-av1:   Additional information: Buffer -1 does not contain a decoded frame
[ffmpeg/video] libaom-av1: Failed to decode frame: Corrupt frame detected
[ffmpeg/video] libaom-av1:   Additional information: Reference frame containing this frame's initial frame context is unavailable.
[ffmpeg/video] libaom-av1: Failed to decode frame: Bitstream not supported by this decoder
[ffmpeg/video] libaom-av1:   Additional information: Buffer -1 does not contain a decoded frame
[ffmpeg/demuxer] ivf: Could not find codec parameters for stream 0 (Video: av1 (libaom-av1) (Main) (AV01 / 0x31305641), none, 1280x720): unspecified pixel format
[ffmpeg/demuxer] Consider increasing the value for the 'analyzeduration' and 'probesize' options
 (+) Video --vid=1 (av1 1280x720 25.000fps)
mpv: /build/aom-BDGUmS/aom-1.0.0.errata1/av1/decoder/decodemv.c:314: set_segment_id: Assertion `segment_id >= 0 && segment_id < MAX_SEGMENTS' failed.

 The lower the bitrate, the longer it tends to take for corruption to occur, presumably because the quantizer is usually higher.

This sounds very similar to https://github.com/xiph/rav1e/issues/1649 which should be fixed by https://github.com/xiph/rav1e/pull/1694

You're right, I'll pull that branch and see if it solves it.

That branch alone does not solve the issue, instead for the clip I am testing playback just freezes at the point where it was previously corrupted. The encoder behavior from what I saw seems to be that dozens of frames are encoded "at once" (the frame counter jumps to the end from several dozens behind).

I updated my original comment with the input command line. Clearly min-quantizer is also relevant as even with @tdaede's branch the corruption only seems to occur when the quantizer is set very low. Changing the minimum to 40 with the same bitrate seems to fix it for the clip I tested.

Interesting. The latest version of my patch has an assert for the qidx = 0 case, so if you don't see it asserting then it's probably a different issue (or I screwed up).

Sample: sample.tar.gz
Will be corrupted after a few frames when encoded with the command line above.

First bad commit: 6f86711f197f2e54c8a1101054d4afda43ad1532

This sounds very similar to #1649 which should be fixed by #1694

Indeed, it looks to me coming from the same origin of #1649 in its nature.

With @tdaede's branch and large LRU disabled, first bad commit is cc7c5f39aa7291ebe55cf039536ed2959bae22d6.

Note that, if speed 4 is used as reported, this issue should not be related because quant_rdo is only enabled at speed 0 and 1 since https://github.com/xiph/rav1e/pull/1709, which is committed on Sep 27, 45d7358c1953c05693f6a52f2487f384540fce80
So, as @rzumer stated, min-quantizer or others are related.

Fixed by tdaede#1 (#1694).

Oh...
" /// When disabled, the segment ID is chosen heuristically.
pub quantizer_rdo: bool,"
I missed whole this. So, seg_id still works even if quantizer_rdo is disabled.
Based on block importance?


This option is no longer available

This option is no longer available for my tenant, has it changed recently?

Dokumentinformasjon
⚠ Ikke rediger denne delen. Den kreves for koblingen docs.microsoft.com ➟ GitHub-problem.

ID: b602a91d-7aa4-705b-004a-780108514ea4
Version Independent ID: 5742fdc9-307a-99aa-ca6b-58a792ad906f
Content: Office 365 control plane in Azure Virtual WAN
Content Source: articles/virtual-wan/virtual-wan-office365-overview.md
Service: virtual-wan
GitHub Login: @cherylmc
Microsoft Alias: cherylmc

@msandbu , I will check this out with my subscription and update you.

@msandbu do you need further assistance with this?

@msandbu Since we have not heard back from you we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

This is stil not available in the portal as an option, is the feature deprecated?


Llama 2 Support

Since it’s public https://ai.meta.com/llama/
Do you have any plan to support it too?

#51 see this PR.
I was able to test with llama2 weights published here https://huggingface.co/TheBloke/llama-2-7B-Guanaco-QLoRA-GGML
This requires the current version of llama.cpp and also need to rebuild llamasharp to match a breaking change in llama.cpp

0.4.2 is out now and should support all llama2 models. I've tested llama-2-13b-chat.ggmlv3.q6_K.bin with it and it works fine.


feat: SVG support implemented. reduced bundled size to only ~130KB.

cleanup: unnecessary png files & bash scripts.
example: windows platform added.

Nice work, so this is a gain of about 700 kb ?

Thanks, when do we expect a new version gets released?

Have you put any thought on using another svg renderer ? EG: https://pub.dev/packages/jovial_svg  seems to have better performances

I've been recently researching (in-house research) Fontello, SVG Icons converted to TTF Font, which is very efficient. Font with Icon Widget with IconData is very robust.
Here is an example of such a font: https://fonts.google.com/noto/specimen/Noto+Color+Emoji?coloronly=true
I'll let you know if those country flags also can be converted into a TTF Font.

Another example of converting SVG to TTF & Dart files is here: https://github.com/pedrolemoz/unicons-flutter
And also I've been successful in converting our in-house app's SVG icons to TTF and using them in that app.

I tried those, but they do not support color fonts, I've searched a little on the JS ecosystem to find out any package that will help us generate color fonts, but it seems it is not feasible yet. https://github.com/nfroidure/svgicons2svgfont/issues/163


Create Special Ops Insignia relic

Problems:
1 - The cards created aren't exhausting neither are Ethereal.
2 - Description has four lines.
3 - Needs a counter.

Only thing left is a huge description.

And done.


Crashes with no info

Crashing Bug (?)
Whenever I boot up the northstar launcher, it just crashes, the crash screen also doesn't say anything, it just says "Northstar has crashed! A crash log and dump can be found in R2Northstar/logs", if it helps to know, I started getting this crash after my initial (and failed) attempt at installing a pilot mod, I've also noticed that I'm supposedly missing a file in 64x retail in bin, yet verifying the game seems to not add it back... Also the normal game runs fine,
Steps to reproduce
Add some clear steps on how to reproduce this problem

(I'm not sure if this contributed to it but install a pilot mod that changes a pilot's model ?)
Activate the Northstar Launcher.
Crash.

Specifications

Northstar version: 1.40
Platform: Steam

Log :
nslog2022-02-07 20-22-16.txt

Check if you followed all installation steps correctly, if that doesn't help use our ticket bot on the discord channel


The package hapi does not satisfy its siblings' peerDependencies requirements!

Hi i just tried using the generator and came across some this issue:
<EMAIL_ADDRESS>node_modules/hoek
npm ERR! peerinvalid The package hapi does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants hapi@>= 8.x.x
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants hapi@>= 8

npm ERR! System Darwin 14.0.0
npm ERR! command "node" "/usr/local/bin/npm" "install"
npm ERR! cwd /Users/marc/Sites/hapiyo
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.14
npm ERR! code EPEERINVALID
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/marc/Sites/hapiyo/npm-debug.log
npm ERR! not ok code 0

I am unfortunately not yet a node / npm specialist in order to figure this out easily myself.

Got the same issue:
$ yo hapi-composer
 _-----_
|       |    .--------------------------.
|--(o)--|    |   Hello, and welcome to  |

---------´   |     the hapi composer    |     ( _´U_ )    |    generator. Let's be   |
/A\    |     awesome together!    |
|  ~  |     '--------------------------'
'..'_
´    |° ´ Y
? Project Name: hapi-playground
? Description: The best project ever.
? Homepage:
? License: MIT
? GitHub username:
? Author's Name:
? Author's Email:
? Author's Homepage:
? Which modules would you like to include? jscs (JavaScript Code Style checker), release (Bump npm versions with Gulp)
? Which hapi plugins would you like to include? lout (API documentation generator), hapi-auth-basic (Basic authentication plugin), tv (Interactive debug console), poop (Plugin for handling uncaught exceptions), good (Server and process monitoring plugin)
? Would you like to include a hapi plugin boilerplate? No
? Which other npm dependencies would you like to include? joi (Object schema validation), boom (HTTP-friendly error objects)
I'm all done. Running npm install for you to install the required dependencies. If this fails, try running the command yourself.
create .jshintrc
create .gitignore
create .travis.yml
create .editorconfig
create .jscs.json
create README.md
create gulpfile.js
create package.json
create lib/index.js
create lib/config.json
create test/hapi-playground_test.js
npm WARN package.json<EMAIL_ADDRESS>Bug string field must be url, email, or {email,url}
npm WARN package.json<EMAIL_ADDRESS>Normalized value of bugs field is an empty object. Deleted.
npm WARN package.json<EMAIL_ADDRESS>homepage field must start with a protocol.

<EMAIL_ADDRESS>install /Users/pk/Documents/dev/hapi-playground/hapi-playground/node_modules/gulp/node_modules/v8flags
node fetch.js

<EMAIL_ADDRESS>install /Users/pk/Documents/dev/hapi-playground/hapi-playground/node_modules/poop/node_modules/heapdump
node-gyp rebuild

CXX(target) Release/obj.target/addon/src/heapdump.o
SOLINK_MODULE(target) Release/addon.node
SOLINK_MODULE(target) Release/addon.node: Finished

<EMAIL_ADDRESS>install /Users/pk/Documents/dev/hapi-playground/hapi-playground/node_modules/tv/node_modules/ws
(node-gyp rebuild 2> builderror.log) || (exit 0)

CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
SOLINK_MODULE(target) Release/bufferutil.node
SOLINK_MODULE(target) Release/bufferutil.node: Finished
CXX(target) Release/obj.target/validation/src/validation.o
SOLINK_MODULE(target) Release/validation.node
SOLINK_MODULE(target) Release/validation.node: Finished
npm ERR! peerinvalid The package hapi does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants hapi@>= 8.x.x
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants hapi@>= 8
npm ERR! System Darwin 13.4.0
npm ERR! command "/Users/pk/.nvm/v0.10.32/bin/node" "/Users/pk/.nvm/v0.10.32/bin/npm" "install"
npm ERR! cwd /Users/pk/Documents/dev/hapi-playground/hapi-playground
npm ERR! node -v v0.10.32
npm ERR! npm -v 1.4.28
npm ERR! code EPEERINVALID
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/pk/Documents/dev/hapi-playground/hapi-playground/npm-debug.log
npm ERR! not ok code 0

Same, here's stack:
npm ERR! Darwin 13.4.0
npm ERR! argv "node" "/usr/local/bin/npm" "install" "lout"
npm ERR! node v0.10.33
npm ERR! npm  v2.1.11
npm ERR! code EPEERINVALID
npm ERR! peerinvalid The package hapi does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants hapi@>= 8

Same:
npm ERR! Darwin 14.1.0
npm ERR! argv "node" "/usr/local/bin/npm" "i" "buffer64" "--save"
npm ERR! node v0.10.33
npm ERR! npm  v2.6.0
npm ERR! code EPEERINVALID
npm ERR! peerinvalid The package hapi does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>

bump hapi version to 8.x.x
and replace default index.js with:
var config = require('./config.json');

var Glue = require('glue');

var manifest = {
  connections: [{
    host: config.host,
    port: config.port
  }],
  plugins: config.plugins
};

if (!module.parent) {
  Glue.compose(manifest, function (err, pack) {
    if (err) {
      console.log('Failed composing');
    } else {
      pack.start(function() {
        console.log("Servers is listening on port " + config.port);
      });
    }
  });
}

module.exports = manifest;

Submitted pull-request https://github.com/wakayama-io/generator-hapi-composer/pull/5
All of you that mentioned this bug really should take a couple minutes to look at how pull-requests work on GitHub. It's incredibly easy to contribute to a project and be part of a solution rather than just another "me too" in an issues conversation.
All I had to do for this pull request was:
-search this project for "hapi" to see where the reference to "6." was,
-fork this project so I had a copy I could modify
-edit the fix (right on GitHub even)
-save the file, commit directly to my forked master branch (not sure this is best practice)
-Goto "Pull Reqests" for my project and hit new. In the pull request I mentioned the link to this issue (hence the "rainabba referenced" posts above).
-come back here and link to the pull request just to make things that much easier
BAM! I've officially "contributed" even though I feel like a newb still. Of course, it's taken me a couple years with GitHub to realize how easy this can be :)


Pachdash does not display joins in network

What happened?:
Investigating Pachyderm Dashboard after defining a pipeline, noticed connections were missing, sorry for tall image.

What you expected to happen?:
1_preprocess to have a connection to 0_staging (joins from a list of acceptable data levels to process from input)
"input":{
	"cross":[{"join":[
	{"pfs":{
		"repo":"0_staging",
		"name":"staging",
		"glob":"/(*).csv",
		"join_on":"$1"
	}},{"pfs":{
		"name":"validLvL",
		"repo":"input",
		"glob":"/validLvL/(*)",
		"join_on":"$1"
	}}]},{"pfs":{
		"name":"dv",
		"repo":"input",
		"glob":"/diff_var/"
	}}
	]
}

1_B to have connection with 1_preprocess (joins valid data from 1_preprocess with the same type as of rejected data coming out of 1_preprocess, to perform lookalike matching on)
"input":{
	"cross":[{"join":[
		{"pfs":{
		"repo":"1_preprocess",
		"name":"preprocess_R",
		"glob":"/reject/(*)/*",
		"join_on":"$1"
		}},
		{"pfs":{
		"repo":"1_preprocess",
		"name":"preprocess",
		"glob":"/universe/(*)/*",
		"join_on":"$1"
		}}
	]},
	{"pfs":{
	"repo":"0_staging",
	"name":"staging",
	"glob":"/",
	"lazy":true
	}}
	]}

3_best_of to have connections with 2_models and 1-E_compile (joins directory of models coming out of 2 with data from 1-E)
"input":{
	"cross":[
		{"join":[
			{"pfs":{
				"repo":"1-E_Compile",
				"name":"preprocess",
				"glob":"/universe/*/(*)",
				"join_on":"$1"
			}},
			{"pfs":{
				"repo":"2_models",
				"glob":"/(*)",
				"join_on":"$1"
			}}
		]},
		{"pfs":{
			"repo":"input",
			"glob":"/trainCodes/"
		}}
		]
}

MS Paint alteration

How to reproduce it (as minimally and precisely as possible)?:
join any two inputs, http://localhost:30080/, see no connection
Anything else we need to know?:
further experimentation shows problem persists with join at base: "input":{"join":[]}, so problem not endemic of performing cross on join, which all above were.
Environment?:

Kubernetes version (use kubectl version):
v1.14.7
Pachyderm CLI and pachd server version (use pachctl version):
1.9.8
Cloud provider (e.g. aws, azure, gke) or local deployment (e.g. minikube vs dockerized k8s):
K8 from Docker Desktop for windows pro
OS (e.g. from /etc/os-release):
Win 10 Pro
Others:

Hi, @CelebrateVC, I'm going to move this issue to the dash repo.


Show Tokens in Dev Mode even when Styles or Variables are Applied

Is your feature request related to a problem? Please describe.
We currently only display applied tokens in Dev mode but users also have styles & variables attached to their tokens.
Describe the solution you'd like
Would it be also be possible to display tokens when a user applies style or variable only but that are attached to their corresponding tokens?

Looking forward to this feature release. Thanks

@robin-deriv In case a style or variable is applied, in the dev mode we can already see that information. In case a style or variable that is linked to a token is applied, would you like to see the token name under the Tokens Studio section? Just for my curiosity, in your workflow would the developers pick up the token name and not the variable or style name that is applied?

@esthercheran If we select styles from figma properties menu, we can not able to see the token name in Dev Mode. However, our tokens and figma styles naming are fully same and we transfer those styles from TS plugin. So both are same but still if our designer choose style from figma they are unable to see in dev mode. It would be great, if they see assigned token in dev mode in this case.
But, Later I realize, still devlopers can see assigned tokens using token studio inspect section. Currently our develoeprs working using inspect instead of dev mode. So it will be a additional feature.

Thank you for explaining the use case @robin-deriv !
We can explore to add the token name in Dev mode, in case a style or variable linked to a token is applied on a layer.

This request has been moved to our new feedback tool. Go check out https://tokensstudio.featurebase.app/ to create a free account. You can upvote and comment on existing posts, make a new request, and subscribe to be notified when requests move into our roadmap.

Added to Featurebase Roadmap : 👨💻 Enhance data in Dev Mode


Fixed bug!

Fixed typo that I made

:white_check_mark: Build ServiceBusExplorer 4.2.0-commandLineBugFix.51.build.634 completed (commit https://github.com/paolosalvatori/ServiceBusExplorer/commit/431021df0e by @rajrao)

Thanks @rajrao


[Translation] Deploy test resources failing in nightly runs

Translation nightly test runs are failing with:

Error message
DEBUG: 14:06:03 - [ConfigManager] Got nothing from [EnableDataCollection], Module = [], Cmdlet = []. Returning default value [True].
VERBOSE: Running registered exit actions
VERBOSE: Logging out of service principal ''
VERBOSE: Performing the operation "New-TestResources.ps1" on target "".
Write-Error: /mnt/vss/_work/1/s/eng/common/TestResources/New-TestResources.ps1:721
Line |
721 |          $deployment = Retry {
|                        ~~~~~~~
| Exception calling "Invoke" with "0" argument(s): "The running
| command stopped because the preference variable
| "ErrorActionPreference" or common parameter is set to Stop:
| 14:06:03 - Error: Code=InvalidTemplateDeployment; Message=The
| template deployment 't6cdb147895974349' is not valid according
| to the validation procedure. The tracking id is
| 'b4e5cc33-2014-445d-ae85-1fc360bb9aa0'. See inner errors for
| details. "
##[error]PowerShell exited with code '1'.

For more details check here:

https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1647003&view=results

@jsquire for notification.

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Storage:0.2181608,Service Bus:0.09830933,Azure.Identity:0.059021104'
Label prediction was below confidence level 0.6 for Model:CategoryLabels: 'Client:0.55122274,Mgmt:0.4436611,Service:0.004167984'

//fyi: @pallavit


LordSachse

https://github.com/git/git-scm.com/issues/1690#issue-1236314784

content://media/external_primary/downloads/18670


1.19.2 Near Instant Crash on Startup

I have a few other optimization mods installed, I'm attempting to figure out what combonation of them will make a light modded server run best on a 2012 12-core Mac Pro. I got a warning on my client that memory usage would be very high unless I installed FerriteCore, however when I did this, I was gifted this crash: https://pastebin.com/sCFAPRK3
That's the crash log from the server, the client one looks identical. It's just the server one I had on hand on this machine since this is the machine the server is running on, and I decided for some reason to open Github on THAT.

Remove Radium.

^That, see https://github.com/malte0811/FerriteCore/issues/96#issuecomment-1278544397.


vulnerable jars

Hi Team,
I am using Apache Tika 1.5 and it has some vulnerabilities in apache pdfbox. But we are not using pdfbox in the application. Is it still vulnerable if we are not using apache pdfbox? or application is still vulnerable?

That is always a million dollar question - transitive dependencies.  In some cases you would not be vulnerable - in other cases you might. Very few of the SCA tools do anything in this space (especially the free ones).  My suggestion is to try and keep everything as up-to-date as possible all the time.  I frequently suggest folks use tools like @dependabot[bot] (see https://dependabot.com/).

It isn't vulnerable if you are sure that you'll never process PDF files. Nevertheless I recommend you update TIKA. 1.5 sounds old, the project is at 1.21 now. By keeping old versions you're denying yourself the joy of all the good things that the developers have created since then.

If your code is on github - checkout dependabot. This makes upgrading/patching just part of your normal lifecycle by continually getting PRs when new versions of a dependency come out. What is great about doing this is you can stay ahead of discovered vulnerabilities and if an emergency/zero day event - patching/upgrading is already part of the lifecycle and you can respond quicker. Both because you are likely using a very recent version (patches are only sometimes backported) and because patching is already part of the standard development sprints.


Fix updateBinary operator parameter

There is an issue in updateBinary where attempting to update operator without updating left or right results in a silent no-op.
Please verify that:

[ ] There is an associated issue in the Backlog milestone (required)
[x] Code is up-to-date with the master branch
[x] You've successfully run gulp runtests locally
[ ] There are new or updated unit tests validating the change

I ran into this bug while writing a transform hook which decomposes foo += 1 into foo = foo + 1 (as part of a larger process where such a rewrite would be useful).
As far as I can tell there is not currently any test coverage that hits this function or those in the same mutation family, so there's no tests to update without building out more test infrastructure.

Thanks, I've updated the PR.

Thanks @laverdet!


wip fix

widen RecipesBase compat

Coverage increased (+3.7%) to 81.081% when pulling b271b81962bd9bc6b6de49920de29b3f75d30510 on mkborregaard:newphylo into 933c3cb3def6e7b11d91bb6b21e6e305295bc25e on richardreeve:master.

Diversity should work, at least with this, once you tag a 0.4.2 release of Phylo.jl with my fix, I believe?

Okay, thanks. I'm just waiting for the tests to complete on master for Phylo and then I'll register it.


wrote pedersen commitments and underlying concepts

Have made these changes along with the changes you mentioned in Discord 👍


Adding Home Assistant Addon

solves #1
I kept it simple.
For now the Addon needs a Token as i wanted it to stay as close as possible to the main tool.
Adding over Addon Store, the configuration in the UI is possible.
I set an default of 60 seconds, which seems ridiculous high, but my raspi4 needed often more than 30secs and i don't wanted to get it killed all the time (i have many addons however)
Builds before i used sibbl docker repo again
Note: I'm unable to build a build armv7. The Github action fails, it works however on my machine.. May someone with more github action experience here?

Awesome work, thank you very much!
I've been on vacation in the last 2 weeks and will take a closer look and test it locally next weekend.
Maybe I can also spot some solution regarding the armv7 compatibility - let's see.


Please update the document as mentioned below.

This is regarding the noop IO scheduler for SLES12 VMs. I tried enabling it on SLES12 SP4 VM, but it did not work.
Moreover the sed command mentioned here to update the /etc/default/grub changes the 2nd line “GRUB_CMDLINE_LINUX” also
with “GRUB_CMDLINE_LINUX_DEFAULT”. Which causes serial console not to work.
Finally I found that we have to disable the scsi block mq (scsi_mod.use_blk_mq) to make noop enabled.
So, I reverted the configuration file /etc/default/grub from the backup, changed it as follows and rebooted the VM.
sed -i 's/scsi_mod.use_blk_mq=1/scsi_mod.use_blk_mq=0 elevator=noop/g' /etc/default/grub
sed -i 's/quiet splash elevator=noop/quiet splash/g' /etc/default/grub
Once rebooted, I can see the noop scheduler enabled and it is as default.
suse-node2:~ # cat /sys/block/sda/queue/scheduler
[noop] deadline cfq
suse-node2:~ #
Can you please update the document accordingly.

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

ID: f7792d5a-de76-c48a-0c8d-46b3e918a503
Version Independent ID: 23b37b12-4a16-d108-2705-2d96ceb484c8
Content: Optimize your Linux VM on Azure
Content Source: articles/virtual-machines/linux/optimization.md
Service: virtual-machines-linux
Sub-service: disks
GitHub Login: @RicksterCDN
Microsoft Alias: rclaus

@amkarmak Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

@RicksterCDN Please validate and update the doc as required

Hi Jakaruna, thank you for the reply. Just to update the sed commands will be as follows...
sed -i 's/scsi_mod.use_blk_mq=1/scsi_mod.use_blk_mq=0 elevator=noop/g' /etc/default/grub
sed -i 's/GRUB_CMDLINE_LINUX=""/GRUB_CMDLINE_LINUX="quiet splash"/g' /etc/default/grub
So, the complete steps will be as ...

Disable scsi block mq (scsi_mod.use_blk_mq) and enable noop scheduler in /etc/default/grub configuration file with the below command.

sed -i 's/scsi_mod.use_blk_mq=1/scsi_mod.use_blk_mq=0 elevator=noop/g' /etc/default/grub
sed -i 's/GRUB_CMDLINE_LINUX=""/GRUB_CMDLINE_LINUX="quiet splash"/g' /etc/default/grub

Once done, rebuild the kernel with below command..

grub2-mkconfig -o /boot/grub2/grub.cfg

Once done, reboot the VM. VM will come up with the noop scheduler enabled.

Example:-
sles-12-sp4-noop-test:~ # cat /sys/block/sda/queue/scheduler
[noop] deadline cfq
sles-12-sp4-noop-test:~ #

Hi Jakaruna,
Thank you for the reply. Just to update the sed commands will be as follows...
sed -i 's/scsi_mod.use_blk_mq=1/scsi_mod.use_blk_mq=0 elevator=noop/g' /etc/default/grub
sed -i 's/GRUB_CMDLINE_LINUX=""/GRUB_CMDLINE_LINUX="quiet splash"/g' /etc/default/grub
So, the complete steps will be as ...

Disable scsi block mq (scsi_mod.use_blk_mq) and enable noop scheduler in /etc/default/grub configuration file with the below command.

sed -i 's/scsi_mod.use_blk_mq=1/scsi_mod.use_blk_mq=0 elevator=noop/g' /etc/default/grub
sed -i 's/GRUB_CMDLINE_LINUX=""/GRUB_CMDLINE_LINUX="quiet splash"/g' /etc/default/grub

Once done, rebuild the kernel with below command..

grub2-mkconfig -o /boot/grub2/grub.cfg

Once done, reboot the VM. VM will come up with the noop scheduler enabled.

Example:-
sles-12-sp4-noop-test:~ # cat /sys/block/sda/queue/scheduler
[noop] deadline cfq
sles-12-sp4-noop-test:~ #
Regards,
Amit
Amit Karmakar
Microsoft Azure Linux Support
Support Escalation Engineer
Working Hours:
Working Days:
Email:
Manager:
11:30 – 20:30 IST
Tuesday - Saturday
amkarmak<EMAIL_ADDRESS>Sabir | Sabir.Chandwale<EMAIL_ADDRESS>If you have any questions about a case, please contact azbackup<EMAIL_ADDRESS>Service Dashboardhttp://www.microsoft.com/windowsazure/support/status/servicedashboard.aspx | Create a Casehttp://www.microsoft.com/windowsazure/support/
From: jakaruna-MSFT<EMAIL_ADDRESS>Sent: Friday, August 23, 2019 2:51 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Amit Karmakar<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Please update the document as mentioned below. (#37674)
@RicksterCDNhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FRicksterCDN&data=02|01|Amit.Karmakar%40microsoft.com|91120b69f9564b04ebfe08d727ab3564|72f988bf86f141af91ab2d7cd011db47|1|0|637021488594087164&sdata=mi2Iz1e%2BESeRhhX%2FptWTFnDtoGKdEWH6By6tJeZQ63M%3D&reserved=0 Please validate and update the doc as required
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F37674%3Femail_source%3Dnotifications%26email_token%3DAM7JCX7NMORJKHQDOH335U3QF6TXTA5CNFSM4IO4MIK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD47UXRQ%23issuecomment-524241862&data=02|01|Amit.Karmakar%40microsoft.com|91120b69f9564b04ebfe08d727ab3564|72f988bf86f141af91ab2d7cd011db47|1|0|637021488594087164&sdata=DDD1L51jLO8YXPovcXM7XSNr1S9VhAgzqTFxjPROzgY%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAM7JCX33MAK3EZD46T5ZF3DQF6TXTANCNFSM4IO4MIKQ&data=02|01|Amit.Karmakar%40microsoft.com|91120b69f9564b04ebfe08d727ab3564|72f988bf86f141af91ab2d7cd011db47|1|0|637021488594097158&sdata=tX3qCrN6HfiMbbqHOT3MPj6Zn7FgVrhRpRVcyJCloyk%3D&reserved=0.

Hi Rick / Jagadeesh,
Is there any update on this please. I can see the document is still having the old values/steps.
Link:- https://docs.microsoft.com/en-us/azure/virtual-machines/linux/optimization
Regards,
Amit
Amit Karmakar
Microsoft Azure Linux Support
Support Escalation Engineer
Working Hours:
Working Days:
Email:
Manager:
11:30 - 20:30 IST
Tuesday - Saturday
amkarmak<EMAIL_ADDRESS>Sabir | Sabir.Chandwale<EMAIL_ADDRESS>If you have any questions about a case, please contact azbackup<EMAIL_ADDRESS>Service Dashboardhttp://www.microsoft.com/windowsazure/support/status/servicedashboard.aspx | Create a Casehttp://www.microsoft.com/windowsazure/support/
From: Amit Karmakar<EMAIL_ADDRESS>Sent: Saturday, August 24, 2019 5:54 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Rick Claus<EMAIL_ADDRESS>Cc: Mention<EMAIL_ADDRESS>Amit Karmakar<EMAIL_ADDRESS>Subject: RE: [MicrosoftDocs/azure-docs] Please update the document as mentioned below. (#37674)
Hi Jakaruna,
Thank you for the reply. Just to update the sed commands will be as follows...
sed -i 's/scsi_mod.use_blk_mq=1/scsi_mod.use_blk_mq=0 elevator=noop/g' /etc/default/grub
sed -i 's/GRUB_CMDLINE_LINUX=""/GRUB_CMDLINE_LINUX="quiet splash"/g' /etc/default/grub
So, the complete steps will be as ...

Disable scsi block mq (scsi_mod.use_blk_mq) and enable noop scheduler in /etc/default/grub configuration file with the below command.

sed -i 's/scsi_mod.use_blk_mq=1/scsi_mod.use_blk_mq=0 elevator=noop/g' /etc/default/grub
sed -i 's/GRUB_CMDLINE_LINUX=""/GRUB_CMDLINE_LINUX="quiet splash"/g' /etc/default/grub

Once done, rebuild the kernel with below command..

grub2-mkconfig -o /boot/grub2/grub.cfg

Once done, reboot the VM. VM will come up with the noop scheduler enabled.

Example:-
sles-12-sp4-noop-test:~ # cat /sys/block/sda/queue/scheduler
[noop] deadline cfq
sles-12-sp4-noop-test:~ #
Regards,
Amit
Amit Karmakar
Microsoft Azure Linux Support
Support Escalation Engineer
Working Hours:
Working Days:
Email:
Manager:
11:30 - 20:30 IST
Tuesday - Saturday
amkarmak<EMAIL_ADDRESS>Sabir | Sabir.Chandwale<EMAIL_ADDRESS>If you have any questions about a case, please contact azbackup<EMAIL_ADDRESS>Service Dashboardhttps://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.microsoft.com%2Fwindowsazure%2Fsupport%2Fstatus%2Fservicedashboard.aspx&data=02|01|Amit.Karmakar%40microsoft.com|cc5b3e54c0794636f09908d7288de038|72f988bf86f141af91ab2d7cd011db47|1|0|637022462183041764&sdata=1KCme7fstDOxBQo21rc17qZlcBuxb5PZMPt1nWHahrA%3D&reserved=0 | Create a Casehttps://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.microsoft.com%2Fwindowsazure%2Fsupport%2F&data=02|01|Amit.Karmakar%40microsoft.com|cc5b3e54c0794636f09908d7288de038|72f988bf86f141af91ab2d7cd011db47|1|0|637022462183051760&sdata=5VHur9NXHL%2Bf6HigMeSD%2BYn1S2fs4vXykZBJuShZoxY%3D&reserved=0
From: jakaruna-MSFT <notifications<EMAIL_ADDRESS>Sent: Friday, August 23, 2019 2:51 PM
To: MicrosoftDocs/azure-docs <azure-docs<EMAIL_ADDRESS>Cc: Amit Karmakar <Amit.Karmakar<EMAIL_ADDRESS>Mention <mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Please update the document as mentioned below. (#37674)
@RicksterCDNhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FRicksterCDN&data=02|01|Amit.Karmakar%40microsoft.com|cc5b3e54c0794636f09908d7288de038|72f988bf86f141af91ab2d7cd011db47|1|0|637022462183051760&sdata=qcTvwubtcksVnM%2BXw%2BKx0UvZWwSjsnKKKw5wSiR11a0%3D&reserved=0 Please validate and update the doc as required

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F37674%3Femail_source%3Dnotifications%26email_token%3DAM7JCX7NMORJKHQDOH335U3QF6TXTA5CNFSM4IO4MIK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD47UXRQ%23issuecomment-524241862&data=02|01|Amit.Karmakar%40microsoft.com|cc5b3e54c0794636f09908d7288de038|72f988bf86f141af91ab2d7cd011db47|1|0|637022462183061752&sdata=Oi6Y76V3SCJzfL0lPbp6IaUxl4OXm1Ww0Pm1yK4SFRw%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAM7JCX33MAK3EZD46T5ZF3DQF6TXTANCNFSM4IO4MIKQ&data=02|01|Amit.Karmakar%40microsoft.com|cc5b3e54c0794636f09908d7288de038|72f988bf86f141af91ab2d7cd011db47|1|0|637022462183061752&sdata=R3uD72rmO%2F2pP6Q6u8ePKTCEXmU6GC6dH%2FXrf9NECps%3D&reserved=0.

@RicksterCDN Please look at the above comments  and provide your views

I wouldn't recommend disabling blk_mq as that was added to improve performance, particularly in NVME disks.
Since switching to blk_mq for many VM images in Azure (including RHEL and SLES) the 'noop' setting no longer applies, but you can set the scheduler to 'none' instead.

#reassign: @MicahMcKittrick-MSFT

Closing based on the doc appears correct. If I am mistaken please let me know and we can reopen and continue.


Fixing content tree state in info message

EVE shouldn't report state Delivered if we get an error while loading the content tree in CAS.

LGTM.
Since this will not apply to application instances, volumes, and content-trees can you verify that the UI shows all three of them correctly?

Content-tree and application instance state are showing correctly now but the run state of the volume instance is still incorrect. I am looking at it.


changed non existing funtion createLOrder to createOrder for the Yobi…

…t exchange.
Also removed unnecessary spaces and added last line newline

Thank you!


Create shapeArea exercise in preferred languages

Already done in languages:

You can choose another language to do this exercise.
Only the first script per language for this exercise will be accepted.

Please comment the new language for this exercise referencing the # for your PR.

Created the PR #46 using Haskell as preferred language.


Simplify the way ansible get the pod name in openshift

The way Ansible collect_config role is getting the pod name is not optimal and can introduce bugs.
We should use instead this command:
oc get pod |grep glance-external-api | cut -f 1 -d' '

Done by the last PR: https://github.com/openstack-k8s-operators/os-diff/pull/37


Added macOS support

added macOS project
added #if/#else/#endif for the difference between iOS and macOS

@petroladkin Is this at a point where it is testable? I may not have a chance to look at it soon but very much would like having macOS support and happy to test and contribute!

@jakerockland the last pull request compiled for macOS but doesn't correctly work in some use cases. Now I testing SwiftyBluetooth in our App (commercial and not open source) on macOS and added small features and fixed one bug/crash. In some days I will create a new pull request with fixes.

Your pull request is turning into far more than a macOS support branch, be careful how you split up your work otherwise it will be much harder to review and integrate the branch.

So, I see at least 3 separate things you are doing right now:

Mac support
Running bluetooth tasks on a background queue
Cosmetic API changes

I don't have the time to review, test and integrate a branch that implements that many things at once.
Break them apart into apart into their own separate branch otherwise I won't bother.

I close this pull request because I will create separated branches for pulls:

mac support
support custom work queue
cosmetic API changes
In my main branch, I will want to apply from separated branches for supporting all features in our project over CocoaPods

Excellent, thank you for your interested in the library.


PR #10906 breaks when using gVisor

Description
PR #10906 unconditionally adds pipe ownership options to runtimes, but these only work with runc as the option format is extensible and other runtimes like gVisor use a different one. This is also a breaking change for people using the 2.0 branch.
Steps to reproduce the issue

Use Kubernetes 1.31, gVisor 20241119 and containerd 2.0 with the cherry-pick of the referenced PR.
Use the following configuration snippet in containerd:

        [plugins."io.containerd.cri.v1.runtime".containerd.runtimes.runsc]
          runtime_type = "io.containerd.runsc.v1"
          privileged_without_host_devices = false
          privileged_without_host_devices_all_devices_allowed = false

          [plugins."io.containerd.cri.v1.runtime".containerd.runtimes.runsc.options]
            ConfigPath = "/containerd/conf/runsc.toml"
            TypeUrl = "io.containerd.runsc.v1.options"

Use the following K8s runtimeclass:

apiVersion: node.k8s.io/v1
kind: RuntimeClass
metadata:
  name: gvisor
handler: runsc

Start a pod with that runtimeclass

Describe the results you received and expected
Error: failed to create containerd task: failed to create shim task: unsupported option type "containerd.runc.v1.Options"

This works with the 2.0 tag only.
What version of containerd are you using?
2.0 tag with that PR cherry-picked
Any other relevant information
runc 1.2.2, fairly default CRI config, Linux 6.6 LTS, K8s 1.31.3 all integrated into https://github.com/monogon-dev/monogon.
Show configuration if it is related to CRI plugin.
No response

/cc @fuweid

PR https://github.com/containerd/containerd/pull/10906 unconditionally adds pipe ownership options to runtimes,

That PR #10906 adds pipe ownership options to runtimes only if container needs to run in user namespace. It's not unconditional.
Please check out the following code in release 2.0.
https://github.com/containerd/containerd/blob/961cac9aa08e444fc0ddf04ecb4cfda9da6b4cc0/internal/cri/server/container_start_linux.go#L34-L40
However, when kubelet enables UserNamespaceSupport feature gate, kubelet always uses non-empty UsernsOptions.
This is my local environment.

➜  containerd git:(release/2.0) kubectl get node -o wide
NAME     STATUS   ROLES           AGE   VERSION   INTERNAL-IP   EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION     CONTAINER-RUNTIME
devbox   Ready    control-plane   11h   v1.31.0   <IP_ADDRESS>      <none>        Ubuntu 22.04.5 LTS   6.5.0-1025-azure   containerd://2.0.0-25-g961cac9aa

➜  containerd git:(release/2.0) containerd-shim-runsc-v1 -v
containerd-shim-runsc-v1:
  Version:  1.6.36+unknown
  Revision:
  Go version: go1.23.2 X:nocoverageredesign

➜  containerd git:(release/2.0) runsc --version
runsc version release-20241118.0
spec: 1.1.0-rc.1

➜  containerd git:(release/2.0) sudo crictl info | grep runsc
      "name": "runsc"
        "runsc": {
          "runtimeType": "io.containerd.runsc.v1",
            "ConfigPath": "/etc/containerd/runsc.toml",
            "TypeUrl": "io.containerd.runsc.v1.options"

➜  containerd git:(release/2.0) cat /etc/containerd/runsc.toml
log_path = "/var/log/runsc/%ID%/shim.log"
log_level = "debug"
[runsc_config]
  debug = "true"
  debug-log = "/var/log/runsc/%ID%/gvisor.%COMMAND%.log"

This is that pod spec I try to create.
➜  containerd git:(release/2.0) cat /tmp/pods.yaml
apiVersion: node.k8s.io/v1
kind: RuntimeClass
metadata:
  name: gvisor
handler: runsc
---
apiVersion: v1
kind: Pod
metadata:
  name: nginx-gvisor
spec:
  runtimeClassName: gvisor
  containers:
  - name: nginx
    image: nginx:1.14.2
    ports:
    - containerPort: 80
    -
➜  containerd git:(release/2.0) kubectl get pods -o wide
No resources found in default namespace.

➜  containerd git:(release/2.0) kubectl apply -f /tmp/pods.yaml
runtimeclass.node.k8s.io/gvisor unchanged
pod/nginx-gvisor created

➜  containerd git:(release/2.0) kubectl get pods -o wide
NAME           READY   STATUS    RESTARTS   AGE   IP           NODE     NOMINATED NODE   READINESS GATES
nginx-gvisor   1/1     Running   0          3s    <IP_ADDRESS>   devbox   <none>           <none>

When I try to enable UserNamespaceSupport feature gate in kubelet, it will be like
➜  containerd git:(release/2.0) kubectl apply -f /tmp/pods.yaml
runtimeclass.node.k8s.io/gvisor unchanged
pod/nginx-gvisor created

➜  containerd git:(release/2.0) kubectl get pods -o wide
NAME           READY   STATUS              RESTARTS   AGE   IP       NODE     NOMINATED NODE   READINESS GATES
nginx-gvisor   0/1     RunContainerError   0          3s    <none>   devbox   <none>           <none>

➜  containerd git:(release/2.0) kubectl get events | grep runc.v1
4s          Warning   Failed                    pod/nginx-gvisor   Error: failed to create containerd task: failed to create shim task: type with url containerd.runc.v1.Options: not found

I can file pull request to add check if UsernsOptions is not nil and it's for node level userns. Or the user namespace IO ownership only works for builtin shimv2.

However, I don't think it's breaking change. After shimv2 introduced since v1.2, both containerd client SDK and CRI are using those options named by runc. The name might be confusing but it's API and abstract level. If gVisor shim doesn't need the option, just don't read it.


Vector thruster rework and added 'Use Vector length as Mul' option

Basically a performance overhaul and added ability to use vector length as mul

Everything seems working fine. I'll be sure to fix anything if it pops up.


Sanity check size and alignment

#2, at least for the Sized case.

This looks good! :+1: It successfully catches #17 without #18.


Add Changeset information to the printed report

for more visibility on why things are reported... TBD

Some initial proof of concept work: https://github.com/grodowski/undercover/tree/changeset-info

Another idea: it might be really beneficial to highlight added lines (based on Changelog) on top of the coverage data in a given Undercover::Result


unmaskAsNumber causing jquery serialize to fail

using this options:
{
  alias: 'numeric',
  groupSeparator: '.',
  radixPoint: ',',
  autoGroup: true,
  digits: 2,
  digitsOptional: false,
  placeholder: '0',
  unmaskAsNumber: true,
  autoUnmask: true,
  removeMaskOnSubmit: true
}

calling jquery.serialize will throws exception saying that replace is not a function.
this is because jquery serialize assume that the fields value is string and tries to escape new line characters if any.
https://jsfiddle.net/mtsunu/8Ldejeeq/
the other issue is when setting unmaskAsNumber: false.
notice i'm using comma as radixPoint.
when i input 12.000,24 the serialized value is 12000,24 (i'm guessing the unmask value will be wrong too, haven't tried it though)
what is the correct options for that situation?

@mtsunu ,
Maybe the unmaskAsNumber should return a numeric parsable string.

won't it be better to fix the custom radixPoint issue?
with the option named "unmaskAsNumber", it would make sense if we expect it to return a number rather than numeric string..

The custom radixPoint issue is not really An issue as some backends want it that way to parse it correctly depending the culture settings. You can always extend the current implementatie.

@mtsunu ,
An example
https://jsfiddle.net/8Ldejeeq/1/

Thanks for the code.
I think you're right, I really need to fix my backend culture settings.
But what if I can't change my backend culture settings? Is that make sense?
So, have you decide what to do with unmaskAsNumber?

@mtsunu ,
unmaskedadnumber stays as is, also the unmasking.
When the culture setting of the backend are fixed, you can use the extension above.  But I cannot think a reason why you could not change the culture settings on the backend.

Okay.
Maybe you should put a warning on the documentation.
Thanks for the help!


Port commits from proposal-temporal 2023-04-16

Big batch of migrated commits!  I think this is about 40% of the remaining commits, although the huge ones like the string slot changes are still ahead.
Thanks again @12wrigja for the great tools to make this easier.

Yes, I think that every observable commit that doesn't also change the expected failures file is probably a sign off a possible test gap.
Maybe it's possible in some cases that the tests were deterred? @ptomato may know.
I'll open an issue in the proposal repo to investigate this further.

Here are the ones where that seems to be the case:

c8912b05703fe6de698f29deee2cb99549d98c1f
d1e939f1e9f5cf86020ec7e95505208dd8c2ec11
0613780d960baa09d3520772fc9492612b1d448f
d28c3f8f9bf138958f97921c6a56a115c89396b9
92334c7dbe5224ddb9b38557f8253dda9c2abfd9
0f7691206e40665a3b5f427922d76f6faf3b5562
544f5391b446567b01e6f3267322685c09745900
bd112438110296af1a0d91309c5ca30782ab22a8
11cd552d9c5daaacd9a2a73ddc54bcb19c4e8ab7

All except the last one in the list have to do with observable order of operations. My guess is that each of those individual commits were necessary but not sufficient to make one of the test262 order-of-operations.js tests pass, so that's why no tests were removed from the expected failures list in each of those commits.
If you can identify the normative PR in the proposal-temporal repo that corresponds to a commit in this repo, I have been fairly consistently linking the test262 PRs that correspond to them (and if I forgot, there's likely a commit in the PR labeled "Update test262" so you can see which test262 commit it points to)

@justingrant I wonder if something that might be useful would be a "test262 results" comparsion system built into the rebase tool where we could gather up the expected-failures lists from both versions and compare them to see whether there are tests that should have been re-enabled (or disabled) but didn't for some reason? It would probably mean having to maintain another expected-failures-like list of test cases we know should be different from upstream "for reasons", but might make rebasing easier overall?

I wonder if something that might be useful would be a "test262 results" comparison system built into the rebase tool where we could gather up the expected-failures lists from both versions and compare them to see whether there are tests that should have been re-enabled (or disabled) but didn't for some reason? It would probably mean having to maintain another expected-failures-like list of test cases we know should be different from upstream "for reasons", but might make rebasing easier overall?

The upstream repo has essentially no expected failures, except weird cases like V8 bugs and for those this repo should fail too.
Also, the tests are somewhat out of sync because upstream the Test262 commit is usually the last one in the PR, but here I've been removing tests from the expected failures file for each commit that needs them.
So I'm not sure how what you describe will be helpful. But maybe I'm missing something?
FWIW, dealing with Test262 using the test runner option you built has been a huge help. I just run every Test262 with that option set. So Test262 is essentially a non-issue for the porting workflow... adds zero extra work for me, because my workflow is this:

Open two terminal tabs, and set up the alias in Tab 1 and start the rebase there. Note that I don't run tests using --exec=./test.sh because that wastes time given that I don't commit until all tests are passing. Below is what I do for each step.
Resolve merge conflicts in editor
Make ecmascript.mjs => ecmascript.ts changes in the editor. This is, by far, the most time consuming (and error-prone) part. If we could turn these changes into merge conflicts, then that would be a massive time savings!
Tab 2: Run npm run prune && npm test && npm run test262 -- --update-expected-failure-files
Tab 1: While tests are running, do git add in terminal tab 2 for all changed files (and the expected failure file if needed). If tests fail then I can git rm to fix the problems.
Tab 2: If tests pass, then git rm /polyfill/lib/ecmascript.mjs
Tab 1: trt continue, GOTO 1

After doing this 50+ times I'm getting pretty fast at it. If we can fix the ecmascript thing to be merge conflicts then I could probably 2x+ my pace.