Some fixes

patches 1 and 2 merged.

Hi, Bruce:
Please correct me if I am wrong, but my understanding was the containers should be tracked firstly then we can do the files movements on top of the subvolumes created by 'overc-ctl track', or else all the modifications in container directories (/opt/container/cube-gw, etc.) would be removed if we do tracking later as it is after your change.
Because the current implementation of 'overc-ctl track' is as follows:
1 Check if /opt/container exists, if not, create it.
2 Check if /opt/container/${container_name} exists, if it exists, delete it. (This is mandatory since btrfs needs it to be non-existence, otherwise, btrfs would create a subvolume into that directory)
3 Check if /opt/container is being mounted on a btrfs device, if so, create a subvolume at /opt/container/${container_name}, if not, create a normal directory.
//Ming Liu

That's the issue. There is a lot of data movement that happens when some container types are added, and the tracking should be something that is enabled when the final container is in place, since errors can happen at many places in the process.
Also tracking is something that will be enabled via 'cube-cfg' on an existing container, or something that can be later disabled. This is required to deal with space issues or to have steps in the process that are not tracked.
I'm seeing [error] messages thrown to the screen during the add process due to tracking having issues with btrfs and different subvol issues.
I understand the flow you are talking about above, but to allow us to work with many different types of filesystems and flows that I'm mentioning above, it needs to be something more like:

install a container to /opt/container/
optionally test to ensure it works
track it (i.e. create a snapshot)

So whatever is in  when it is 'tracked', we take a snapshot then. Yes, there may be additional data movement, since you will probably have to move 'foo' to another location to create btrfs, or whatever other type of snapshot we are doing, and then create the FS layout and then put the container data back.
Also, it is something to consider that we store snapshots in a parallel data structure to the containers, i.e. /opt/container-snapshots/. But we may run into space issues, etc.


Dropwizard version of command latency recorder

Feature Request
Describe the solution you'd like
An analogue of the micrometer solution.

Attaching PR for discussion

Anyway, let me know, and I'll polish off the tests for the dropwizard lettuce.


RHMAP-4875 Update fh-mbaas-api version with fh.db changes for shared mongo in mbaas

Reviewed, merging


GradebookNG can't add items in 11.x branch.

Tried creating a GB-NG item  on the 11.x branch and it wouldn't let me.

Thanks @willkara.  It looks like the location of jquery-ui.js changed locations and GradebookNG is still referring to the old location.
We'll review all the assets we use and make sure they're up to date.

Delving deeper, it seems that this issue is isolated to the 11.x branch and ok on master.  More specifically, the 11.x branch has an older version of GradebookNG (2 months older!) which doesn't contain the patch which fixes this exact issue: caa82ebf7375457426e973c768544f6bb281064c.
@steveswinsburg, is there anything we can do push through a later version of GradebookNG to the 11.x branch?

Yeah we are going to ask the branch managers to pull the latest mods into 11.x on a weekly or so basis.  Cheers.


Protocol "https" not supported or disabled in libcurl

after runnig the following code :
python3 setup.py develop --user
this error appears :
CMake Error at libmypaint-stamp/download-libmypaint.cmake:159 (message):
  Each download failed!

    error: downloading 'https://github.com/mypaint/libmypaint/releases/download/v1.3.0/libmypaint-1.3.0.tar.xz' failed
         status_code: 1
         status_string: "Unsupported protocol"
         log:
         --- LOG BEGIN ---
         Protocol "https" not supported or disabled in libcurl

  Closing connection -1

         --- LOG END ---

I'm using ubuntu 18 and this is curl version :
curl 7.65.3 (x86_64-pc-linux-gnu) libcurl/7.65.3 OpenSSL/1.1.1
Release-Date: 2019-07-19
Protocols: dict file ftp ftps gopher http https imap imaps pop3 pop3s rtsp smb smbs smtp smtps telnet tftp
Features: AsynchDNS HTTPS-proxy IPv6 Largefile NTLM NTLM_WB SSL TLS-SRP UnixSockets

It doesn't seem like a problem specific to this project. Not sure what causes it but I would suggest downloading the archive manually (https://github.com/mypaint/libmypaint/releases/download/v1.3.0/libmypaint-1.3.0.tar.xz) and patching CMakeLists.txt to use local file URL (see https://github.com/deepmind/spiral/blob/master/CMakeLists.txt#L26)

I added a link to a pre-build Docker image to README. Please use this if my suggestion above didn't help.


The built-in Disqus now requires visitors to load unsafe scripts on https in order to comment.

The built-in Disqus now requires visitors to load unsafe scripts on https in order to comment. This didn't use to be necessary. If users don't do this step, they don't even see the Disqus comment box at the bottom of my page. It appears Disqus is not https compatible?

I had the same problem and was able to fix it by modifying -
project_dir/_includes/JB/comments_providers/disqus  line 10
from  dsq.src = 'http://' + disqus_shortname + '.disqus.com/embed.js';
to  dsq.src = 'https://' + disqus_shortname + '.disqus.com/embed.js';
I don't know if this is the "right" way but it did work for me.
Scott D.

@Duroktar are you using Social Engine? Where did you find this file? I can't find anything with project_dir

@Duroktar I found it...thank you!

Just noticing this now, sorry. Glad I was able to help someone :)


TypeScript: extends or implements not colored correctly when both are used at the same time

When extends and implements are used at the same time, the second one gets highlighted incorrectly with the color assigned to class names. In the above example implements should be blue instead of green.

Filed the issue with the correct repository:
https://github.com/Microsoft/TypeScript-TmLanguage/issues/31


raidboss: P6s initial timeline

I built this based on a log from quisquous. This has received no live testing, and I haven't taken the time to match everything 1-1 with the video I was handed alongside, but it passed test_timeline against every encounter in that log.
Given that my group hasn't started on this yet, I don't know what timeline elements are superfluous. Unholy Darkness and Dark Dome in particular are probably in need of some cleanup. I also didn't distinguish any potential 100% split or shared Synergy busters.

I think landing something here is better than nothing.  I'm going to leave the comments here as suggestions for follow-ups, and will merge this for now.


[FEAT] trailing_slash argument to ini()

E.g. url = BuildURL('example.com', trailing_slash=True) so one can set it from the beginning:)

The trailing_slash attribute is automatically updated every time the path is modified.
For example, if you do url /= "path/", trailing_slash will be set to True, and if you then do url /= "again", trailing_slash will be set to False, to reflect the latest path.
When instantiating BuildURL, it'll also use the given base URL to determine trailing_slash, so if you do url = BuildURL("https://example.com/"), trailing_slash will be set to True.
I've added an option to force the trailing slash, called force_trailing_slash, and this option isn't updated automatically. It can be set when instantiating, like url = BuildURL("https://example.com", force_trailing_slash=True), can be set directly with url.force_trailing_slash = True, or can be manipulated inline with url.set_force_trailing_slash() (that also returns a reference to self for chaining purposes, like requested in #12).


TH breaking syntax highlight

This appears to break the syntax highlighting,
disambiguate <- lift $ examineSplice [||b||]

https://github.com/neovimhaskell/haskell-vim/blob/f35d02204b4813d1dbe8b0e98cc39701a4b8e15e/syntax/haskell.vim#L116
This looks like it should support this syntax though.


Sea Level Rise Data

This partition also includes 20191223_dimensions_Sea_Level_Rise_Inundation

Hi @JasonZhangzy1757,  I looked into the commit history. Still not sure what happened. Some of the other files included in this PR seemed to be rather old -- for example, it was using a much older copy of test.py and .gitignore.
I took the master branch then added your new partition, plus my update on the unit tests.  That was merged already in PR #52 -- so this PR should be deleted.

Also, it's probably a really good idea at this point to go through and run
git checkout master
git pull

on your repo, or delete and clone a new copy?

I just realized I made such a silly mistake. I shouldn't upload the file directly to my branch instead of keeping my git updated and using git push. That's probably why all the other files are old. Thank you so much and sorry for the trouble!

No worries, great to troubleshoot that!


how to build kuberhealthy from code?

how to build kuberhealthy from code?
I searched with google, but I cannot find it.
Could some one help me?
Thanks in advance

maybe you can  pull the kuberhealthy images to run the container by docker, is this what you want do get?

maybe you can pull the kuberhealthy images to run the container by docker, is this what you want do get?

I am new to kuberhealthy,I want to build the kuberhealthy into some binaries, is there some guide here?

From https://github.com/kuberhealthy/kuberhealthy/blob/master/cmd/kuberhealthy/Makefile
cd ./cmd/kuberhealthy
go build
./kuberhealthy -h


Shaping functions: make '.' subject implicit

In the common case of shaping the entire record as in shape(., <sometype..>), allow the . argument to be omitted, following the pattern introduced with is().

(Maybe I should do this for cut and pick too?)


Renamed of the Firehose service gRPC ids and packages

This will require a coordinate update for NEAR when Firehose service ids will change there, graph-node with this version will need to be deployed.
I suggest we merge this branch than quickly coordinate between us for the deployment of NEAR Mainnet, downtime will be minimal.

A backward compatibility layer has been pushed in the backed for this, so both version can co-exists. It was actually already been deployed to production on NEAR by mistake which caused a downtime, had to code the backward compatibility layer to fix the down time.
When the CI finished, I'll merge this.


Fixes the extension check required for OIT

Based on the discussion in this WebKit thread, this PR adds a check for EXT_float_blend  when enabling OIT. It also removes the restriction on OIT for iOS devices added as a workaround in https://github.com/CesiumGS/cesium/pull/10337.

Before
After

Tested on an iPhone XR running iOS 15.5 using WebGL via Metal.

Thanks for the pull request @sanjeetsuhag!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.

@sanjeetsuhag I think you have one eslint error to clean up.
@lilleyse Could you confirm the fix?


result problem

I use the your training code to train. The training set only uses got10k. The test results are as follows
my   result:AO=0.612，SR0.5=0.735,SR0.75=0.461
your result:AO=0.595,SR0.5=0.695,SR0.75=0.479
Looks like performance is very good
But when I tested vot18 with this model, the result was very poor,The test results are as follows
my   result:ACC=0.549,ROB=0.300,EAO=0.310
your result:ACC=0.587,ROB=0.183,EAO=0.426
Do you have this problem
It is worth noting that the code for training is  "sh  tools/train_test-googlenet.sh" . When training is interrupted, I run "python ./main/train.py --config experiments/siamfcpp/train/siamfcpp_googlenet-trn.yaml --resume-from-file=... " to continue training

The model with EAO=0.426 is trained with multi-datasets like coco+youtubebb+lasot+got10k. We will release the multi-datasets training code in a few weeks, please keep tuned.

Can't support multi dataset training yet. I see  "names: ["GOT10kDataset",]  in the configuration file, but an error will be reported when I use  ["GOT10kDataset","LaSOTDataset"].

You are right. The training with multi-datasets is under testing yet, the original code is written with the internal framework. So the reproduce will take some time.

ce will take some t

Hi, can u provide the specific time of releasing the training code to reproduce the VOT18 and OTB100?

I can not guarantee one certain time but we will release it in this month hopefully.

@songdejia Training code is done and it is under final test (to make sure it works well after PyTorch version change) before being merged into Master branch. If you are urgent, you can check out the "dev-fulldata_hpo" branch in my fork.

@songdejia Training code is done and it is under final test (to make sure it works well after PyTorch version change) before being merged into Master branch. If you are urgent, you can check out the "dev-fulldata_hpo" branch in my fork.

Thanks. Can u provide a readme file to describe how to use full data

and in  fact you don't use youtube-BB dataset , you  use TrackingNet. there is  no  ytb_bb.py script in your program

@lzx1413
We will release the multi-datasets training code in a few weeks, please keep tuned?  Did you have finished?  Thank  you !


Fix authors profile syntax.

@FREDERICO23 Adding a missing comma here to fix broken syntax in your frontmatter.

Thank you


debug_fd deprication warning message

This is more of an annoyance then a problem.
After starting the react-script this message gets displayed:
> react-scripts start

Starting the development server...

(node:13088) DeprecationWarning: `DEBUG_FD` is deprecated. Override `debug.log` if you want to use a different log function (https://git.io/vMUyr)
Compiled successfully!

The app is running at:

  http://localhost:3000/

Note that the development build is not optimized.
To create a production build, use npm run build.

The issue in question is the DEBUG_FD. Like I've mentioned already, this is simply an annoyance at this point and I'd like to resolve it if possible.
Is there a way of solving this from my end?
Node version 6.9.4
Npm version 4.1.1
Environment Windows 10

Can you find which package calls the function?

In the code there is no call for it.
In the node_modules these modules I've found using it:

express
compression
finalhandler
send
eslint-module-utils
serve-index
ajv
debug

Do you have this problem with a clean project? So far I'm unable to reproduce it with Node 6.9.4.

This was likely caused by WebStorm's use of that variable. The deprecation warning was rolled back for some cases so I'm assuming this got fixed. https://github.com/visionmedia/debug/issues/410

Hi @gaearon
Sorry for the late response.
I can confirm that with the version 0.9.0 the problem is gone.


wrong inputs passed to run:

Using the snakemake version 6.15.1 I encounter what appears to be a rather peculiar bug:
In certain situation when checkpoint is referenced twice, the first occurrence passes incorrect input values to a run rule. Curiously, correct values are passed to a shell rule. A small reproducible test case is given below.
The bug can be reproduced by running
rm -rf xxx && mkdir -p xxx && echo -e "1\n2\n3" > xxx/input.txt
snakemake -j1 -s test-bug.txt -d xxx/ -p --nocolor

After this, the content of these two new files should be same, but is not (the first is incorrect):
$ cat xxx/list.txt
jobs.txt

$ cat xxx/list2.txt
dir/1/ccc.txt
dir/2/ccc.txt
dir/3/ccc.txt

See the small test pipeline here test-bug.txt
Here note I want to use run because the input array is expected to be very big for my data and the shell line length limit would be exceeded.

@johanneskoester I looked in the code but it's too modular and complex, couldn't identify where the run vs shell inputs get filled. I found out that update_checkpoint_outputs() in snakemake/dag.py gets called more times with run than with shell, but couldn't make anything of that.
Somewhat encouraging is that the -p option sees in both cases the correct input dependency
rule many_to_one:
    input: dir/1/bbb.txt, dir/2/bbb.txt, dir/3/bbb.txt
    output: list.txt

although run ends up using jobs.txt instead of dir/1/bbb.txt, dir/2/bbb.txt, dir/3/bbb.txt.
Since both see the input correctly and shell is even able to execute it correctly, this should not be an unsurmountable design problem?

Hi again,
I'm getting the problem in the shell directive (6.15.5).

#855, #1021, and a number of other issues seem to be reporting the same problem.
This bug seems to have existed for a long time, but still no fixes?
The checkpoint feature is surely one very critical feature for a lot of workflows. Once I found the feature, I changed a lot of the code to utilise it. It seemed like it was working great while developing, but I'm experiencing this problem near the completion of my pipeline, which makes it really inconvenient :/.
I'd advise others who read this to use the checkpoint feature sparingly until the bug is fixed.

Hey @pd3,
I ran your minimal example with both 6.15.1 and 7.1.1.
As you said, the output of xxx/list.txt only contains jobs.txt when the pipeline ran with 6.15.1. But the seems okay in 7.1.1, with the below content.
dir/1/bbb.txt
dir/2/bbb.txt
dir/3/bbb.txt

This is what you expected right?
From going over the changelog between 6.15.1 and 7.1.1, I can't find which change might've fixed your problem but it looks to be fixed.
I'm not sure whether the update would've fixed my problem, but I've changed the quite code a bit so not sure whether I'd be able to reproduce.

@youngchanpark Indeed, the new version fixed the problem!


Eng/dqm

There are 2 input data sources in the demos:

karate club  - from networkx lib, so it is not stored in any file
brain graph data - stored in demo/network_community_detection/brain_networks_data.

If you find the demo dir too messy, we can:

delete the demo/network_community_detection dir, then the community_detection_brain.ipynb would probably be to delete as well as it relies on the data and functions from this dir

and

keep only community_detection_karate_club.ipynb as a community detection demo


@DIR does nto behave as "expected" in IJulia

Hi there, i have a notebook in a folder A of my computer.
When I start Julia I automatically set my working directory to the desktop.
I fire up IJulia and launch the notebook. In there I type:
joinpath(@__DIR__)

which returns "C:\\Users\\datse\\Desktop", i.e. it does not return the directory of the file containing the macro call. Or maybe it does "technically" given how IJulia works under the hood, but this is not my typicall usage of @__DIR__.
How can I obtain the source directory of the notebook inside the notebook?

This might(?) not be possible.
Jupyter is designed to have two separate parts: the frontend (e.g., Jupyter Notebook, Nteract, QT Console, Jupyter Lab, etc.) and the kernel (IPython, IJulia, IRKernel).
The kernel part doesn't have very much knowledge of all of what's going on in the frontend, it's basically just a process that responds to code execution requests. In particular, it doesn't know what notebook file the code requests are coming from (all that IJulia sees is a request to execute println("foobar") and nothing more).
When you start IJulia, the working directory is set by default to be the directory of the notebook, so removing the part where it automatically sets the working directory to the desktop should fix that issue. If you do that in startup.jl, you can just add a check like this:
if !haskey(ENV, "JPY_PARENT_PID")
    cd(...)
end

Not possible in general: https://github.com/ipython/ipython/issues/10123

For what it is worth, @travigd solution was good enough for me :)


LocalAI use only 100% CPU (one Core) for Rebuild and Could not release VRAM when not use model

Is your feature request related to a problem? Please describe.

It could be Problem. I used docker desktop and when rebuild Local AI, LocalAI use only one cpu 100% while my computer has  40 VCPU. It takes long time to finish rebuilding, almost 8 hours.
When loading model for using, If I want release vram to load other model, I have to restart server.
Describe the solution you'd like

Solution could me:

Local AI should user more CPU to finish rebuilding earlier.
Command looks like curl .... to release model and vram.

Describe alternatives you've considered

Parameter to use more CPU
Command to release Model and Vram
Additional context

Thank you for a wonderful solution right now.

BUILD_PARALLELISM

Thank you for your reply. However, i could not search out this parameter "BUILD_PARALLELISM " Could you please show the syntax of this config? BUILD_PARALLELISM=true or BUILD_PARALLELISM=30??

You can see the code here:
https://github.com/mudler/LocalAI/blob/1c708d21de87371bb17c27e2615aa352e9ac5790/entrypoint.sh#L18
It's the number of threads you want to use when building/rebuilding. You need to pass it as an environment variables when creating the container.
For instance if your computer has 40 CPU cores and you want to use all of them during the rebuild it would look like this: BUILD_PALALLELISM=40

Thank you for your help.

You can see the code here:
https://github.com/mudler/LocalAI/blob/1c708d21de87371bb17c27e2615aa352e9ac5790/entrypoint.sh#L18
It's the number of threads you want to use when building/rebuilding. You need to pass it as an environment variables when creating the container.
For instance if your computer has 40 CPU cores and you want to use all of them during the rebuild it would look like this: BUILD_PALALLELISM=40

Hi,
I tried this option but still the same. only one CPU used by localai

I tried this option but still the same. only one CPU used by localai

I experienced the same -- I went ahead and edited BUILD_PARALLELISM=20into the .env file, then double checked that that was in fact the right instance of the file, and this cleared up the problem.
(This wasn't the first instance I've observed here where some of my attempts to set environment vars from outside the container aren't  making it all the way inside. I haven't done much to root-cause that since it's easy enough to work around.)

I tried this option but still the same. only one CPU used by localai

I experienced the same -- I went ahead and edited BUILD_PARALLELISM=20into the .env file, then double checked that that was in fact the right instance of the file, and this cleared up the problem.
(This wasn't the first instance I've observed here where some of my attempts to set environment vars from outside the container aren't making it all the way inside. I haven't done much to root-cause that since it's easy enough to work around.)

Thanks reedtaylor. Mistyping letter R by L lead to not-working config. Now, it's working well.


RayCastMesh should be type-registered for use in Scene

I have a scene that I want to serialize/deserialize, containing meshes that I'd like marked with RayCastMesh. However this doesn't seem to be possible unless RayCastMesh is registered with the type system. Would it be possible to add this? RayCastSource is probably another good candidate too.

This is blocked on https://github.com/bevyengine/bevy/issues/5144.

Looks like
bevy::reflect::impl_reflect_value!(RaycastMesh<T: Reflect + Clone>);
bevy::reflect::impl_from_reflect_value!(RaycastMesh<T: Reflect + Clone>);

should do the trick, but I want to see if I can minimize breakage for people that don't need reflection.

@djeedai can you please give #67 a try and let me know if this works?

#67 depends on Bevy 0.9, it will take at very least a week before all crates I need upgraded.

This has been implemented and released.


travis ci build failing on no-colors test

no-colors by default will output in color is the failing test
you can see the output in the build: https://travis-ci.org/nathanboktae/mocha-phantomjs/builds/159069819
I think the issue is with the regex being used for matching, may have to do with the unicode character matching. I haven't investigated further yet, just wanted to let you know the travis ci build's failing at the moment

a little late but thanks @nathanboktae for fixing this issue! 😄

Thank you for reporting it !


Fix geod_inverse argument order

Fixes #105

Ah, I just ran into this error I think.  Thanks for the PR!
Testing the patch reveals the correct behaviour.


Add mmol support

To use mmol go into Xdrip/settings/glucose units and change your units to your desired value. changing the value in xdrip will change the value on the watch

👍


How to Watch particular record in Horizon ?

Uncaught TypeError: messages.find(...).fetch(...).watch is not a function

messages.find({name:'liveit'}).fetch().watch().subscribe(function (sl) {             this.setState({                 live:sl.text             })         }.bind(this))

Just take out fetch, you want .find().watch()
On Tue, Sep 27, 2016, 09:25 Vignesh Warar<EMAIL_ADDRESS>wrote:

Uncaught TypeError: messages.find(...).fetch(...).watch is not a function
messages.find({name:'liveit'}).fetch().watch().subscribe(function (sl) {
this.setState({
live:sl.text
})
}.bind(this))
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/rethinkdb/horizon/issues/842, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAFVhC_GKYsW4U4E8F2hSfJVnqerZbTks5quUN5gaJpZM4KH3_a
.


[release-v1.6] SRVKS-981 Multiarch test images

multiarch-build github action

Remove unwanted github actions from upstream. This will be done automatically when creating release branches.

Change ko base image

Allow specifying TEST_IMAGE_TAG and KO_FLAGS for test image build

Cover both cases test image dir without yaml and without Go file

/lgtm


Tunnel names are case sensitive but remoteAuthorities are not

Currently, the tunnel name is case sensitive, and you can have two tunnels that differ only by casing.
This is problematic as the tunnel name is used in the remote authority vscode-remote://tunnel+tunnelName/..
URI-authorities are case insensitive. vscode-remote://tunnel+foo/ is equal to vscode-remote://tunnel+FOO/.
We would have to encode the tunnel name in the authority, or we define that tunnel names are also case insensitive.
I suggest we do the latter.

This doesn't yet seem to work for already persisted servers.
The persisted settings are {"name":"AESCHLI-SURFACE","id":"dgm3ggl2","cluster":"uks1"}
After loading, the name should be lowercased, so that
https://github.com/microsoft/vscode/blob/efe37734ebbb492f02ae686cf605ec5b6343776a/cli/src/tunnels/dev_tunnels.rs#L388
will update the server name

I wonder if we should still store the name in the original casing so we can use it for labels

How does this work? On machine A I ran code-insiders tunnel and it gave me the name vibrant-weaver. On machine B I ran code-insiders tunnel rename VIBRANT-weaver and that succeeded

But when I go to https://insiders.vscode.dev/tunnel/VIBRANT-weaver/ it connects to machine A, is that expected?

Step 2 fails for me. I need to use the exact casing, otherwise it says the tunnel isn't found. After I use the exact casing, it says I have an auth mismatch.
I start the tunnel foo-bar using the dedicated Insiders CLI on Windows in a Windows Terminal tab. I can connect to it just fine from Edge using any casing. Then, I create a new Windows Terminal tab and rename the tunnel to bar-FOO while it's still running. Then, I try opening a URL such as insiders.vscode.dev/tunnel/BAR-FOO or  insiders.vscode.dev/tunnel/bar-FOO and get the error above.

Testing on Version: 1.78.0-insider
Commit: 657bb89984f37b810b250955570593cde0cd62eb
Date: 2023-05-02T11:22:37.024Z
Electron: 22.4.8
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.14.0-1048-oem
Sandboxed: Yes
I see the same, exact csing is needed when connecting with the browser

open VS Code desktop
open the setting, set "remote.tunnels.access.hostNameOverride": "KapitalT"
start the remote tunnel access using the Accounts menu: Turn on Remote Server Access
from the popup, click in the vscode.insiders.dev link
browser opens correcly
in the browser URL change the casing and reopen:
https://insiders.vscode.dev/tunnel/KAPITALT/home/aeschli/workspaces/vscode-distro

Error dialog:
An unexpected error occurred that requires a reload of this page.
The workbench failed to connect to the server (Error: Could not find a tunnel named KAPITALT. Please make sure you are logged into the correct account. You can reloading, logging in, then running 'Connect to Remote Server'.)

I can't get past GitHub auth on insiders.vscode.dev when opening a tunnel link. Letting someone else verify this issue in case it's a misconfiguration on my end.


Endpoint DLP log (device activity log) schema is missing

The following page does not have Dynamics 365 schema information, even though we can get Endpoint DLP logs (device activity log) using Office 365 Management Activity API.
https://docs.microsoft.com/en-us/office/office-365-management-api/office-365-management-activity-api-schema
https://github.com/MicrosoftDocs/office-365-management-api/blob/live/office-365-management-api/office-365-management-activity-api-schema.md
For example, we can get an Endpoint DLP log (device activity log) like below (some values are masked):
 {
    "SourceLocationType": 1,
    "Platform": 1,
    "Application": "EXCEL.EXE",
    "FileExtension": "xlsx",
    "DeviceName": "device01.corp.contoso.com",
    "MDATPDeviceId": "1e82df73acf2c509bc12b4d7bcc4a394be6aa67c",
    "FileSize": 0,
    "FileType": "Microsoft Excel",
    "Hidden": false,
    "ObjectId": "C:\\Users\\User01\\Desktop\\~$test.xlsx",
    "UserId"<EMAIL_ADDRESS>    "ClientIP": "x.x.x.x",
    "Id": "a70cb637-7b6e-4002-8170-eb66ce46f28b",
    "RecordType": 63,
    "CreationTime": "2021-03-04T14:06:26",
    "Operation": "FileDeleted",
    "OrganizationId": "70c32610-3071-4013-8607-d338463e92e4",
    "UserType": 0,
    "UserKey"<EMAIL_ADDRESS>    "Workload": "Endpoint",
    "Version": 1,
    "Scope": 1
  }

@rykoma Please create a PR with your proposed changes! Thanks, linda

@lindalu-MSFT Sorry for the late reply. But I cannot create a PR, because I don't know the correct schema information. Could you collaborate with the right person in engineering group and update the documentation, please?
JFYI. I submitted a similar issue last year, and the documentation was fixed without creating a PR.
https://github.com/MicrosoftDocs/office-365-management-api/issues/134


iterating over game-drives-plays-players vs. game.players

Thank's for this great package!
It may not be an issue but just me not understanding.
I want to get all fumbles recovered by defense duging a game (defense_frec stat).
game = nflgame.games(2016, week=1, away='MIN')[0]
print game
MIN (25) at TEN (16)
There was actually 2 fumbles recovered by the Vikings in this game.
trying:
for dd in game.drives:
    for pp in dd.plays:
        for pl in pp.players:
            if 'defense_frec' in pl.stats:
                print pl, pl.team, pl.stats

D.Hunter MIN OrderedDict([('defense_tds', 1), ('defense_frec_tds', 1), ('defense_frec_yds', 24),    ('defense_frec', 1)])
A.Sendejo MIN OrderedDict([('defense_frec_yds', 2), ('defense_frec', 1)])

I get the expected result.
But if I iterate over game.players directly,
for pp in game.players:
    if 'defense_frec' in pl.stats:
                print pl, pl.team, pl.stats

then, I get nothing (I actually get some stats but the ones I'm expecting aren't there). What am I missing?

You're not doing anything wrong per-say, just a misunderstanding about what type of statistic a defense_frec is.
While it does appear as a stat type within a play (your first code block demonstrates this), when you ran for pp in game.players you had nflgame do some aggregating of all of the plays and spit out a different set of stats recorded in the game.   Whereas defense_frec is a valid stat type in a play, the aggregated collection of those recovered fumbles is captured under fumbles_trcv  (I honestly don't know how it determined which stats are used nor how those play stats get mapped to their aggregate counterparts.).
import nflgame

games = nflgame.games(year=2016, week=1, kind='REG', away='MIN')
for game in games:
    for pp in game.players:
        # if 'fumbles_trcv' in pp.stats:  # Maybe everyone that fumbles has `fumbles_trcv` initialized to 0?
        if pp.stats.get('fumbles_trcv', 0):
                    print pp, pp.team, pp.stats

A.Sendejo MIN OrderedDict([(u'fumbles_trcv', 1), (u'fumbles_tot', 0), (u'fumbles_rcv', 0), (u'fumbles_yds', 2), (u'fumbles_lost', 0), (u'defense_ffum', 0), (u'defense_tkl', 4), (u'defense_int', 0), (u'defense_ast', 0), (u'defense_sk', 0)])
D.Hunter MIN OrderedDict([(u'fumbles_trcv', 1), (u'fumbles_tot', 0), (u'fumbles_rcv', 0), (u'fumbles_yds', 24), (u'fumbles_lost', 0), (u'defense_ffum', 0), (u'defense_tkl', 3), (u'defense_int', 0), (u'defense_ast', 0), (u'defense_sk', 1)])

But - and I hope you've made it this far! - you don't need to go through the cumbersome game > drive > play > player hierarchy to access play statistics.  Forget all that.  If you want all of the plays where a fumble was recovered, then you can do something much simpler:
import nflgame

games = nflgame.games(year=2016, week=1, kind='REG', away='MIN')
plays = nflgame.combine_plays(games)
for play in plays.filter(defense_frec=True):
    print play

    for player in play.players:
        print '\t', player, player.stats
    print '-'*79

(TEN, TEN 25, Q4, 1 and 10) (11:11) (Shotgun) M.Mariota FUMBLES (Aborted) at TEN 22, RECOVERED by MIN-D.Hunter at TEN 24. D.Hunter for 24 yards, TOUCHDOWN.
    M.Mariota OrderedDict([('rushing_att', 1), ('rushing_yds', 0), ('fumbles_rec_yds', -1), ('fumbles_tot', 1), ('fumbles_notforced', 1), ('fumbles_lost', 1)])
    D.Hunter OrderedDict([('defense_tds', 1), ('defense_frec_tds', 1), ('defense_frec_yds', 24), ('defense_frec', 1)])
-------------------------------------------------------------------------------
(TEN, TEN 42, Q4, 2 and 8) (9:48) (Shotgun) D.Murray up the middle to TEN 43 for 1 yard (L.Joseph). FUMBLES (L.Joseph), RECOVERED by MIN-A.Sendejo at TEN 48. A.Sendejo to TEN 46 for 2 yards (T.Lewan).
    A.Sendejo OrderedDict([('defense_frec_yds', 2), ('defense_frec', 1)])
    T.Lewan OrderedDict([('defense_tkl', 1)])
    D.Murray OrderedDict([('rushing_att', 1), ('rushing_yds', 1), ('fumbles_tot', 1), ('fumbles_forced', 1), ('fumbles_lost', 1)])
    L.Joseph OrderedDict([('defense_tkl', 1), ('defense_ffum', 1)])
-------------------------------------------------------------------------------

Thanks for the answer!
In order to wrap my head around this, I took a look at the json file for this game. It seems that there are two types of statistics in there. One set is for each of the players in a team and seems to correspond to the players' aggregate stats for the whole game. The fumbles_trcv comes from this set of stats.
The other set of stat is at the level of each play and have a statId which seems to be mapped to python attributes through the statmap.py. The statId for the players who recovered fumbles in their respective plays is 59, which is mapped to defense_frec in statId.py.
So game.players iterates over the first set of stats, explaining with fumbles_trcv is found in there but not defense_frec. On the other hand, play.players returns the second set of stats, which contains defense_frec. Hope it makes sense?

Yeah, that does make sense.  I was mistaking the aggregated data as something nflgame was assembling.  In reality, it is already in the JSON and nflgame is just pulling it out.


Undefined Method

getting following errors:
undefined method `app_secret=' for Facebook::Messenger::Configuration:Module (NoMethodError)
the following after commenting out app_secret
uninitialized constant Welcome (NameError)

Those features haven't been released yet. You can use master branch:
gem "facebook-messenger", github: "hyperoslo/facebook-mesenger", branch: "master"

Or check the README for the latest version here:
https://github.com/hyperoslo/facebook-messenger/tree/7f3c6701deb730b379eb25a0c53110cfc56ab15b
@jgorset there is no release tag for 0.4.1 and 0.4.2.

I pushed tags for 0.4.1, 0.4.2 and released a new version 0.5.0. Thanks guys!

https://github.com/hyperoslo/facebook-messenger/blob/master/CHANGELOG.md#050---2016-05-26


Adding support for ex-core structures

What is the change?
Added initial support for ex-core structures in ARMI.

Blueprints can now easily define ex-core structures on their own grids.
The old SpentFuelPool logic was rolled into the new ExcoreStructure class.
The old AssemblyList class was removed.
Reporting tools were updated to match.
Docs were updated to match.

The ARMI Reactor class used to have two children that were also attributes: r.core and r.sfp.  Now it has two children that are also attributes: r.core and r.excore.  And r.excore is currently a dictionary where keys map to an arbitrary set of ex-core objects:

r.excore["sfp"]
r.excore["ivs"]
r.excore["evst1"]
r.excore["evst2"]
r.excore["primary_coolant_pump_3"]

Why is the change being made?
Thus far, ARMI has really only provided a data object model for the Reactor core (and also a default spent fuel pool). The large teams that model and analyze nuclear reactors will also want to model ex-core structures for fuel handling and mechanical analysis reasons.

Checklist

[x] This PR has only one purpose or idea.
[x] Tests have been added/updated to verify any new/changed code.

[x] The code style follows good practices.
[x] The commit message(s) follow good practices.

[x] The release notes have been updated if necessary.
[x] The documentation is still up-to-date in the doc folder.
[x] The dependencies are still up-to-date in pyproject.toml.

Out of curiosity, why is excore it's own object/dictionary? Why not just allow apps to register the excore structures they want directly to reactor? So like r.core, r.sfp, r.evst etc?

Out of curiosity, why is excore it's own object/dictionary? Why not just allow apps to register the excore structures they want directly to reactor? So like r.core, r.sfp, r.evst etc?

This feels very natural and something that could make a user's life easier. r.evst vs r.excore["evst"] is fewer characters.
But to support the level of dynamism needed for r.evst to resolve when that attribute is not defined on the class would likely require some new logic in Reactor.__getattr__ to be able to dynamically resolve new children. But this also means you can't do children like "primary pump 3" which may also be more natural

 Prototype
In [1]: class R:
   ...:     def __init__(self):
   ...:         self.core = None
   ...:         self.__excore = {}
   ...:     def add(self, name, obj):
   ...:         self.__excore[name] = obj
   ...:     def __getattr__(self, name):
   ...:         try:
   ...:             return self.__excore[name]
   ...:         except KeyError as ke:
   ...:             raise AttributeError(name) from ke
   ...:

In [2]: r = R()

In [3]: r.core = "hello"

In [4]: r.core
Out[4]: 'hello'

In [5]: r.add("evst", [])

In [6]: r.evst
Out[6]: []

In [7]: r.sfp
---------------------------------------------------------------------------
KeyError                                  Traceback (most recent call last)
Cell In[1], line 9, in R.__getattr__(self, name)
      8 try:
----> 9     return self.__excore[name]
     10 except KeyError as ke:

KeyError: 'sfp'

The above exception was the direct cause of the following exception:

AttributeError                            Traceback (most recent call last)
Cell In[7], line 1
----> 1 r.sfp

Cell In[1], line 11, in R.__getattr__(self, name)
      9     return self.__excore[name]
     10 except KeyError as ke:
---> 11     raise AttributeError(name) from ke

AttributeError: sfp

Food for thought.

Out of curiosity, why is excore it's own object/dictionary? Why not just allow apps to register the excore structures they want directly to reactor? So like r.core, r.sfp, r.evst etc?

Well, that's possible. But we are going to have dozens or hundreds of excore structures, and they area all just r.whatever, and there's no organization left.
It's certainly a thought I had early on, but I don't know.
I think if we were to do THAT, I would still prefer: r.excore.sfp, r.excore.ivs, r.excore.evst3.  At least that way, it's clear what these things are.
hmm

I think I was going along the lines of more general would be more flexible. If you have a crazy reactor setup with two cores, then you would be forced into modeling one core as the core and one as excore.core2. Or similarly, if someone wanted to run analysis on the spent fuel pool like it was a reactor to verify things, then they could... Seems like it's on the plugins to know what container to look at and run analysis on.

Sure, we could do something more like this:
class Recctor:
    # ...

    def __getattr__(self, key):
        try:
            return self.__dict__[key]
        except KeyError:
            if key in self.excore:
                return self.excore[key]
            else:
                raise

    def __setattr__(self, key, value):
        try:
            self.__dict__[key] = value
        except KeyError:
            if key in self.excore:
                self.excore[key] = value
            else:
                raise

This allows r.sfp and r.evst1, if that's just super important to everyone.
Though I still think r.excore.sfp and r.excore.evst is more clear.

Want to clarify that I am not likely going to be an immediate user nor stakeholder of this feature so take my suggestion w/ a grain of salt. Not a requirement

@drewj-tp @jakehader @alexhjames
I guess encapsulation is my goal here:
r.core - core physical object
r.excore - ex-core physical object
r.o - operator
r.id - number
r.p - parameter collection
r.cached - tooling
r.spatialGrid - tooling
r.factory - method
r.add - method
r.isFuel - method
r.backUp - method

I mean, I can make r.sfp a thing, and r.ivs, but it will mean a metric TON of error checking to make sure people don't name their excore structures id or p or o or cached or factory, because that would break the Reactor class.
And I'll have to check that no one tries to over-write the method r.factory() by doing r.factory = ExcoreStructure().
Or, in code you could set r.ivs = ExcoreStructure() , but I need to make sure you don't do r.o = ExcoreStructure().
There would just be so much error checking where I need to list every single time anyone adds or touches any method or attribute on a Reactor object. I would have to keep a full list of all attributes and methods in Reactor and it's parents Composite and ArmiObject.

There is at least one place in our benchmarks that will need to be migrated due to this change. We used to allow r.sfp, but now it is r.excore["sfp"].

@john-science Test this downstream before merging.


software bug：use v0.4.2-rc2 release packages to install k8 on  kylin os,  the socat is needed

/kind bug

Solved in #413


[flutter_tools] remove assertion for deprecation .packages

.packages is deprecated and not used by the tool. Unblocks the pub roll.

This can't affect the internal roll. Landing manually to unblock the engine roll.


Requested streaming from 0/286E000, which is before the start of the timeline 0/286E018

Saw into this error in CI:
https://github.com/neondatabase/neon/actions/runs/3134904311/jobs/5090092139
I believe this is the same issue as was discussed here:
https://github.com/neondatabase/neon/pull/2143#issuecomment-1199969052
Opening a new issue to track that more explicitly.

Fixed by https://github.com/neondatabase/neon/pull/2529, closing


Implement NSMutableOrderedSet

Very handy implementation of a “mutable, ordered collection of distinct objects.”
Unclear if this is being implemented (see https://github.com/Microsoft/WinObjC/pull/482).
For my purposes, performance is not critical.

I am implementing most of the functions, expect to see a review out soon.
RJ

@RG-J, thank you!

@RG-J how is this coming along?

@rajsesh-msft  I'll push my changes soon, just pulled it up to the latest code and setting up VS2017.


WFCORE-706 non exploded deployments incorrectly marked as exploded

Core - Full Integration Build 1005 is now running using a merge of bbba7d4625d4476f7972de6f269d231768645065

Linux Build 1859 is now running using a merge of bbba7d4625d4476f7972de6f269d231768645065

Windows Build 1409 is now running using a merge of bbba7d4625d4476f7972de6f269d231768645065

Windows Build 1409 outcome was SUCCESS using a merge of bbba7d4625d4476f7972de6f269d231768645065
Summary: Tests passed: 3109, ignored: 69 Build time: 0:21:16

Linux Build 1859 outcome was SUCCESS using a merge of bbba7d4625d4476f7972de6f269d231768645065
Summary: Tests passed: 3109, ignored: 69 Build time: 0:23:50

Core - Full Integration Build 1005 outcome was SUCCESS using a merge of bbba7d4625d4476f7972de6f269d231768645065
Summary: Tests passed: 2863, ignored: 374 Build time: 0:50:38


Terraform checkov detection: CKV_AZURE_110: "Ensure that key vault enables purge protection"

Check: CKV_AZURE_110: "Ensure that key vault enables purge protection"
FAILED for resource: module.init.azurerm_key_vault.init
https://www.checkov.io/5.Policy Index/terraform.html

Previously included in skip_check


Wheel not spinning on mobile browser

Use dummy values to try : http://echoes.stargazer.co.in/events/encryption.php

Android, IPhone, Windows? What browser on mobile, the crappy Android "browser" or Chrome, Firefox, some other mobile browser? More details are required.


Performance comparison (react-native-unity vs native unity build)

Hello,
I would like to understand wether there is a performance hit, when running a unity scene using the react-native-unity wrapper, compared with having a unity scene and directly deploy from Unity to the iOS/Andorid device.
Hopefully, in the next few weeks I'll do a comparison in this very regard, but I wanted to check if someone can share their experiences, how the unity integration using react-native-untiy performs.
It would be nice to have a Unity scene with known performance when being deployed directly from unity to e.g. an iOS Device and then have the same scene running using react-native-unity wrapper and see if the performance matches.

@exotexot did you ever come to a conclusion?

@rcorrie Back then I ran the test that I described in my first post, and I can share the results here.
I did some tests though were react-native-unity was performing worse. Could have been due to thermal throttling or whatever. But the videos show that they CAN run very similar!
https://github.com/azesmway/react-native-unity/assets/10153413/e634e693-4f7f-40e2-8785-c20595eee401
https://github.com/azesmway/react-native-unity/assets/10153413/54181d6c-9db7-47fd-b291-a50b394dfb04


Github pushing

I am using code interpreter to push my samp.py file into github using the crew agent but the code interpreter is not able to execute my code for github pushing and successfully do the task, is there a way I could directly do this usecase with githubsearchtool() ?

Hi @Varuni-13
No the GitHubSearchTool is a RAG tool for GitHub only


My old Copay wallet was gone!!

When I tried to log in, I created a new account and all my old data was gone.  It is very regrettable, please tell me the reason for this case and the countermeasure.

@sakura129
we have developed our own hardware for cracking all versions of bitcoin wallet password with superfast speed
and if you still has problem I can help you run it. you can find my contact details on my profile
or you can send me message in telegram: @johnjames333 or gmail<EMAIL_ADDRESS>


Bug url_escape::encode_fragment

The following code
url_escape::encode_fragment("http://example.org?a=1");
returns
"http://example.org?a=1"
It does not encode it as a fragment. It in fact does nothing.
The correct result should be http%3A%2F%2Fexample.org%3Fa%3D1

According to the spec, the fragment percent-encode set is the C0 control percent-encode set and U+0020 SPACE, U+0022 ("), U+003C (<), U+003E (>), and U+0060 (`).
If you want to encode :, /, ? and =, you should use the encode_component function or the encode_userinfo function.


Feature request: Timestamp

Would be awesome to be able to toggle timestamp option

@G12c4 thank you for feedback, i added this feature with this pr : https://github.com/AliYmn/python-colorful-print/pull/4


intermediate_solutions_program results mismatch with docs

According to this intermediate_solitions_program the intermediary solution should be printed. But when I run exactly the same code on my machine the number of solutions is one, while in this reference there are seven optimal solutions. What`s wrong?

Looks like the solver improved and doesn't need those intermediate solutions anymore in this case.
You can see that by hinting wrong values and creating more intermediate solutions:
model.AddHint(z, 0)
model.AddHint(y, 0)

So, not really a issue.

@stradivari96 thanx for instance reply!

Yes, now we branch directly in the direction of the objective.
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
Le mar. 27 août 2019 à 14:59, Xiang Chen<EMAIL_ADDRESS>a
écrit :

Looks like the solver improved and doesn't need those intermediate
solutions anymore in this case.
You can see that by hinting wrong values and creating more intermediate
solutions:
model.AddHint(z, 0)
model.AddHint(y, 0)
So, not really a issue.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1523?email_source=notifications&email_token=ACUPL3M44Q335UMRL4B6J6TQGUQKVA5CNFSM4IQEBUBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5HUPLY#issuecomment-525289391,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACUPL3MLN4QSTCS4Q3IOAKLQGUQKVANCNFSM4IQEBUBA
.

@stradivari96 what will happen if I call another cp_model solver, with seperate constraints and logic, from intermediary callback method?

It should works. But is would be fairly expensive.
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
Le mar. 27 août 2019 à 15:05, Shohruh<EMAIL_ADDRESS>a écrit :

@stradivari96 https://github.com/stradivari96 what will happen if I
call another cp_model solver, with seperate constraints and logic, from
intermediary callback method?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1523?email_source=notifications&email_token=ACUPL3PUOVXXGKIC4QRXWGLQGUQ77A5CNFSM4IQEBUBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5HVAXA#issuecomment-525291612,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACUPL3OLQZ5O7NWMZYDPIOTQGUQ77ANCNFSM4IQEBUBA
.

@stradivari96 @lperron even after AddHint(...) it returned few solutions - 2 or 3 max. Could you explain,why it is so, ?

The real question is, why do you need those intermediate suboptimal solutions?

Because the problem  is so trivial it will converge towards the optimal
very fast.
BTW, the best possible solver only returns one solution.
Le mar. 27 août 2019 à 17:40, Xiang Chen<EMAIL_ADDRESS>a
écrit :

The real question is, why do you need those intermediate suboptimal
solutions?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1523?email_source=notifications&email_token=ACUPL3IPAFCRNCLJ63GJJ7DQGVDIDA5CNFSM4IQEBUBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5IFWJQ#issuecomment-525359910,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACUPL3NEHT5WE4NFP54PPVTQGVDIDANCNFSM4IQEBUBA
.

@stradivari96 for my case I am using two level solver(), as ortools is not imperative. So, one solver calls another solver within callback. I know this is really heavy but this approach is suitable for my case. That is why suboptimal solutions are rather helpful for my case, as the most optimal solution of the upper solver can not optimal for the inner one.

By the way, which ortools version is supporting what I need?

I do not understand. Any version should work. You should use the latest.
Le mar. 27 août 2019 à 17:51, Shohruh<EMAIL_ADDRESS>a écrit :

By the way, which ortools version is supporting what I need?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1523?email_source=notifications&email_token=ACUPL3LG6HDW6Z4JLS7TP6DQGVEQ5A5CNFSM4IQEBUBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5IG2SA#issuecomment-525364552,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACUPL3O5ZQGF7L25Q5MOE6LQGVEQ5ANCNFSM4IQEBUBA
.


An unexpected error 127, while running sudo make openlane

Description
touch venv/created
make[1]: Entering directory '/home/eeuser/openlane/docker'
make[1]: /venv/bin/python3: No such file or directory
make[1]: /venv/bin/python3: No such file or directory
make[1]: /venv/bin/python3: No such file or directory
make[1]: /venv/bin/python3: No such file or directory
make[1]: /venv/bin/python3: No such file or directory
make[1]: /venv/bin/python3: No such file or directory
make[1]: /venv/bin/python3: No such file or directory
make[1]: /venv/bin/python3: No such file or directory
/venv/bin/python3 ./utils.py pull-if-doesnt-exist --repository efabless/openlane-tools --os centos-7 --architecture  run-base
make[1]: /venv/bin/python3: No such file or directory
make[1]: *** [Makefile:60: pull-run-base] Error 127
make[1]: Leaving directory '/home/eeuser/openlane/docker'
make: *** [Makefile:91: openlane] Error 2
Expected Behavior
I need to install openlane successfully without error report in my terminal
Environment report
Kernel: Linux v5.15.0-58-generic
Distribution: ubuntu 22.04
Python: v3.10.6 (OK)
Container Engine: docker v20.10.12 (OK)
OpenLane Git Version: f9b5781f5ef0bbdf39ab1c2bbd78be8db11b27f2
pip: INSTALLED
pip:venv: INSTALLED
---
PDK Version Verification Status: FAILED
/home/eeuser/openlane/pdks/sky130A not found.
Traceback (most recent call last):
  File "/home/eeuser/openlane/dependencies/verify_versions.py", line 72, in verify_versions
    raise Exception(f"{pdk_dir} not found.")
Exception: /home/eeuser/openlane/pdks/sky130A not found.

Failed to verify sky130A.
---
Git Log (Last 3 Commits)

f9b5781 2022-07-01T16:04:31+02:00 Fix a bug with `-overwrite` (#1171) - Anton Blanchard -  (HEAD -> master, origin/master, origin/HEAD)
abb9d59 2022-07-01T13:46:02+02:00 Reimplement support for multiple power domains (#1175) - Marwan Abbas -  ()
83b6145 2022-06-26T18:19:11+02:00 Fix #1163 (#1164) - Mohamed Gaber -  ()

Reproduction material
...
Relevant log output
...

@JeffreyHJF
Seems trying with older release. Please follow instruction from here and try with latest OpenLane release https://github.com/The-OpenROAD-Project/OpenLane#installation-the-short-version

Why are you using sudo ?

Don't use sudo.
You are using a release from July of 2022.

Step 25 (routing) failed with error:
I got this error while running make proj
Can someone help?

@Prabha1010
Please create new issue with complete log file and reproducible test case generated the run directory.


'esnext.array' doesn't enable access to Array.prototype.flat()

TypeScript Version:  3.1.0-dev.201xxxxx

Search Terms: esnext, esnext.array, Array.prototype.flat()
Code
// greeter.ts

function greeter(persons: string[]) {
    return "Hello, " + persons.flat().join();
}

var user: string[] = ["Jane User"];

document.body.innerHTML = greeter(user);

// tsconfig.json
{
  "files": [
    "greeter.ts"
  ],
  "compilerOptions": {
    "target": "esnext",
    "lib": [
      "es2017",
      "esnext.array",
      "dom"
    ]
  }
}

Expected behavior:
Should compile successfully. According to MDN, it's an experimental API supported by multiple browsers already.
Actual behavior:
Compilation error:

greeter.ts:2:32 - error TS2339: Property 'flat' does not exist on type 'string[]'.

2 return "Hello, " + persons.flat().join(); ~~~~

Playground Link

.flat is specified in lib.esnext.array.d.ts:
https://github.com/Microsoft/TypeScript/blob/ef7997cb73ce46081cbfebc0edd2a0295ba30c33/lib/lib.esnext.array.d.ts#L152-L222
It feels like something else is going on.  It won't work in the playground because it doesn't support changing things like the libs and target.

Your tsconfig.json doesn't contain any files or include properties.  How are you compiling greeter.ts?  At the moment, the config file would not apply to the greeter.ts in something like Visual Studio code.

@kitsonk , yes, I've made sure flat() is there in lib.esnext.array.d.ts before creating this.
I compiled it with tsc greeter.ts hoping that tsc would pick up tsconfig.json. I've just tried again with files section added (see updated initial post) and the error is the same.

@AbakumovAlexandr try tsc -p . instead...

@kitsonk just tried tsc -p tsconfig.json with the same error. Does it work for you?

$ tsc --version
Version 3.0.1
$ tsc -p .

No errors output, greeter.js that is emitted:
function greeter(persons) {
    return "Hello, " + persons.flat().join();
}
var user = ["Jane User"];
document.body.innerHTML = greeter(user);

I even with typescript@next:
$ tsc --version
Version 3.1.0-dev.20180810
$ tsc -p .

Again, no errors... 🤷♂

@AbakumovAlexandr what's the output of tsc -v ?

@kitsonk I think I've figured out the source of the issue thanks to the feedback from your side!
I've switched local TypeScript versions only, while my global stays 2.9.2. So it's always compliled with TS 2.9.2. But in 2.9.2, flat() was called flatten(). That's why it couldn't find it.
Unfortunately, tsc doesn't prints its version to the console leaving a room for confusion. If you, guys, feel like you'd like to implement it, let me know and I'll create a different issue for that.

@RyanCavanaugh see my above comment, please.

It does print to the console with --version and most compilers are implicitly silent.

@Favna I've tried loading the lib configs in your order as well, but that does not work for me.

@ernie-h I've got 2 more ideas then

What is your NodeJS version (node -v)? I know for a fact that on runkit.com array.prototype.flat is not available in Node 10 LTS, but it is when setting it to Node 11 Current. So if you have lower, consider upgrading. If you use Linux or MacOS you could consider using NVM so you can switch back easily if that's not the resolution.

Note that I personally use Node 11.

Here is an exact copy of my tsconfig, maybe you need to configure other settings, such as the moduleResolution to node

{
	"compilerOptions": {
		"outDir": "dist/",
		"rootDir": "./src",
		"forceConsistentCasingInFileNames": true,
		"esModuleInterop": true,
		"lib": ["esnext.array", "es2018", "dom"],
		"target": "es6",
		"module": "commonjs",
		"moduleResolution": "node",
		"newLine": "lf",
		"noFallthroughCasesInSwitch": true,
		"noImplicitAny": true,
		"noImplicitReturns": true,
		"noImplicitThis": true,
		"noUnusedLocals": true,
		"removeComments": true,
		"resolveJsonModule": true
	},
	"include": ["src/**/*.ts"],
	"exclude": ["node_modules", "dist", "src/**/*.js"]
}

Updating to Node 11 also resolved this issue for me. The ordering of items in lib does not seem to have an effect, nor does moduleResolution.

Ye Node 11 is the reason why it works as it has the feature internally (and also the fact that the newer V8 engine it has supports it). I think on that note this issue can pretty much be closed. Maybe the feature will eventually be backported to LTS (V10 at time of writing) but that is far outside the scope of this issue.

I'm having a similar problem, it looks like TS is not transpiling the .flat() method to previous versions of node, like it would do for async/await for example.
Node: v10.16.0
Typescript: v3.5.2
{
  "compilerOptions": {
    "incremental": true,
    "target": "es2018",
    "module": "commonjs",
    "lib": ["esnext"],
    "strict": true,
    "moduleResolution": "node",
    "esModuleInterop": true,
    "experimentalDecorators": true,
    "emitDecoratorMetadata": true
  }
}

const flatArr = [[1], [2]].flat().join(',');
console.log(flatArr);

To compile, I'm running the command npx tsc -p .
The output is:
"use strict";
const flatArr = [[1], [2]].flat().join(',');
console.log(flatArr);

The output is wrong because in the target (es2018), Array.prototype.flat does not exists.

TypeScript has never downleveled method calls to built-in APIs

Thank you for your reply Ryan.
I find this a bit confusing, how does TS decide what to transpile and what not to?
Like decorators, async/await yes, but built in APIs no? Is it documented anywhere?

TypeScript transpiles language syntax, not functionality.  async/await is language syntax, Array.prototype.flat() is functionality.  Items described in a type library (lib) are not transpiled.
Even with syntax there are certain caveats, like --downlevelIteration is behind a flag, because it requires that other functionality needs to be polyfilled in environments where it is targeted, which TypeScript won't provide.

How can I get this error to go away since I'm fine with not supporting IE and don't want TS to bloat my bundle with any polyfills? (I'm assuming that's what lib does even though it's not exactly clear from the docs)

don't want TS to bloat my bundle with any polyfills

TypeScript never generates polyfills, so you don't need to do anything

don't want TS to bloat my bundle with any polyfills

TypeScript never generates polyfills, so you don't need to do anything

Ohhhh I see, good to know 👌


chore: remove dependency on vs/common

The one use of AsyncIterableSource can be easily replaced with a readable stream.
Had to remove the DOM types fromt the tsconfig.json as the @types/node definition of ReadableStream breaks a bit when the DOM types for ReadableStream are also present.
Verified this still works using the chat-sample (and tested the stream still streams)

I ended up using another utility, so I updated this after merging


PyPI version broken

The version PyPI is broken. Could you please make a release of the current master on PyPI

hi
this is known, we have made a mistake when uploading the current prod version to pypi, we expect to solve this in the next release of udocker
due to some pypi feature, when a version is uploaded, even if we delete it, it does not allow the same version anymore, and that is why we could not have fixed it

Do you have an ETA for when you will make a new release?

Since the current release is broken, I think you should make it ASAP because packages that depend on udocker cannot make releases also until you do. This is a very annoying situation

hi @SpheMakh , apologies for the delay
please check and try now
pip install udocker
you will get version 1.1.3-post1, but is exactly the same released version (1.1.3), we just fix the setup.py and upload to pypi


Configuration of the plugin is no problem, But it doesn't work properly.

NOTE: GitHub issues are reserved for bug reports only.
For anything else, please join the conversation
in Kong Nation https://discuss.konghq.com/c/kubernetes.

Summary
SUMMARY_GOES_HERE
Kong Ingress controller version
kong-docker-kubernetes-ingress-controller.bintray.io/kong-ingress-controller:0.3.0

Kong or Kong Enterprise version
Kubernetes version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.5", GitCommit:"32ac1c9073b132b8ba18aa830f46b77dcceb0723", GitTreeState:"clean", BuildDate:"2018-06-21T11:46:00Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.6", GitCommit:"b1d75deca493a24a2f87eb1efde1a569e52fc8d9", GitTreeState:"clean", BuildDate:"2018-12-16T04:30:10Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}

Environment

Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):

NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

Kernel (e.g. uname -a):

Linux test1.eyingchina.com 3.10.0-957.5.1.el7.x86_64 #1 SMP Fri Feb 1 14:54:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Install tools:
helm
Others:

What happened
After I refer to this  document the plugin does not work properly.
But the configuration of the plugin is no problem.The response header does not have X-RateLimit-Limit-*

@vincent927 Can you share logs of the Ingress Controller?

@vincent927 Can you share logs of the Ingress Controller?

Thanks!
It seems to be my problem, I am directly accessing through ingress, and changing to kong-proxy access will not be a problem.
But I still have a question, how is kong-proxy exposed? If I have multiple domain names that need to be proxyed

But I still have a question, how is kong-proxy exposed? If I have multiple domain names that need to be proxyed

Assuming you're running in a cloud environment, you will need to expose it as a LoadBalancer service and then for each domains you're proxying, update the DNS to point to the LoadBalancer's IP (A records) or DNS name(CNAME record).

@hbagdi Tks a lot!  I got it .


Allow Google Cloud Run Deployment by adding adapter-node to adapter-auto

Describe the problem
I would like SvelteKit applications to deploy successfully to Google Cloud Run with zero configuration using adapter-auto. Currently, it requires switching to the adapter-node package.
Describe the proposed solution
I would like to include@sveltejs/adapter-node in the list of adapters in order to support deployment to Google Cloud Run and other Node environments. I proposing to add Node last (code example here) since it might be present in other environments.
// Add Node last since it might be present in other environments
{
  name: 'Node',
  test: () => process.env.NODE_ENV,
  module: '@sveltejs/adapter-node',
  version: '5'
}

Alternatives considered

We could create our own custom adapter for Google Cloud Run, but the only official default environment variables could catch other K Native environments that are not Cloud Run. This would also present additional maintenance when adapter-node already works out of the box.{
  name: 'Google Cloud Run',
  test: () => !!process.env.K_SERVICE,
  module: 'svelte-adapter-cloud-run',
  version: '1'
}

Importance
would make my life easier
Additional Information
I'm happy to make a Pull Request (I have this one drafted), but since I am new to the world of SvelteKit adapters and there may already be a good reason for not including this, I wanted to create the issue for discussion first. I'm sure I am missing something. Let me know if this could work or if this could be modified in some way that would be acceptable.

Thanks for reaching out! I'm not really familiar with Google Cloud Run, but from the blog I found it seems it also requires the user to create a Dockerfile to deploy SvelteKit? If that's the case, the auto adapter isn't a great fit for it since the auto adapter should only be for environments that are zero-config (see also: https://github.com/sveltejs/kit/pull/8984).
If the deployment can be zero-config, then maybe the auto adapter could work. However, we'd want an environment variable that is unique to Cloud Run, since NODE_ENV could be present in other environments. We wouldn't want the auto adapter to start trying to use the node adapter unexpectedly in environments that aren't Cloud Run.

Thanks for responding @geoffrich!
I helped Karl write the Dockerfile for that blog. So I can also confirm that it wouldn't be needed 😄
Right now, node build which is the last part of that Dockerfile, isn't included in the list of start commands that Buildpacks attempts, but I think the Buildpacks team would be willing to add something specific for SvelteKit (like it did with node .output/server/index.mjs for Nuxt.js).
I think the bigger issue is likely finding an environment variable specific to Cloud Run. The current list of environment variables are all related to K Native, but that might include non-Cloud Run environments as well.
Let me check with the team to see if we can come up with an environment variable that would work.
Thanks again for taking a look.

@geoffrich - In the process of working with the Buildpacks team, they brought up the idea that rather than targeting a "Cloud Run specific" environment variable, instead they could add a specific environment variable for SvelteKit's node adapter?
What are your thoughts on something like this?
{
  name: 'Node',
  test: () => process.env.USE_SVELTEKIT_NODE_ADAPTER,
  module: '@sveltejs/adapter-node',
  version: '5'
}

Or it could be used to provide a general-purpose environment variable for any adapter?
{
  name: 'Node',
  test: () => process.env.SVELTEKIT_ADAPTER === '@sveltejs/adapter-node',
  module: '@sveltejs/adapter-node',
  version: '5'
},
{
  name: 'Static',
  test: () => process.env.SVELTEKIT_ADAPTER === '@sveltejs/adapter-static',
  module: '@sveltejs/adapter-static',
  version: '3'
}

This way, it wouldn't be necessary to add a specific configuration object for every host that supports node or static hosting?

Hmm, those suggested environment variables feel too generic to me. They seem like they could encourage other platforms to set them as well, and then you couldn't easily bump the specified adapter version since we wouldn't know what deployment platforms would be affected.
At the very least, I think the environment variable should include something to indicate it's coming from cloud run, e.g. CLOUD_RUN_USE_SVELTEKIT_NODE_ADAPTER.
I'll raise this issue internally to see if any other maintainers have an opinion.

That makes sense. It should definitely be a conversation between maintainers. My thought process was that "since adapter-node isn't specific to Cloud Run, there's no reason other providers couldn't use it?" But that makes sense from the standpoint of knowing whether or not it's safe to update.

I raised this issue in the maintainers channel and we're still leaning towards an environment variable name that indicates it's Cloud-Run-specific to keep things organized and minimize unforeseen consequences.
The proposed process.env.SVELTEKIT_ADAPTER pattern is interesting, but I think that would need a lot more investigation and thought to make sure it's a pattern we feel good about, since we couldn't easily iterate on it once the environment variables are being used. So I think it's best to go with the established platform-specific env var pattern for now.

Thank you so much for following up. That makes sense. I'll work with the Google Cloud Buildpacks team to determine a reliable environment variable and make a pull request.

@geoffrich - I worked with the Buildpacks team who made these changes to their repository, which should pave the way for zero-config SvelteKit deployments. I created this Pull Request, which should be the last piece in the puzzle. I think it meets the "Cloud Run specific" goals that the SvelteKit team was looking to accomplish. Let me know if there's anything else I should do before this pull request is ready to merge.
Thanks again for all your help!


tools/lesspipe: Allow generic shell

Its better to allow generic shell for compatible with other distro

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


error trying to withdraw bETH

hi - discord is on lockdown. we can't send messages through telegram. so I'm going to try here -
I am trying to withdraw my collateral bETH but keep having "transaction failed" notices.
The transaction requested has failed due to the following reason:
: Generic error: Price is too old: execute wasm contract failed
tx hash: EA3198...838BEE

Same here

I did this yesterday and it worked and got my bETH out and back to Ethereum and convert to webETH  wormhole then cobert to stETH on lido
they might have stopped the Anchor eth Oracle because someone was manipulating it last night - look at this masssive bETH price spike over night (12 hours ago) it peaked to 303k per bETH also massive volume - locked bETH on anchor went from $33million to $6Million
https://coinhall.org/charts/terra/terra1c0afrdc5253tkp5wt7rxhuj42xwyf2lcre0s7c

+1, please fix asap. Anchor team holding our assets hostages, much for decentralisation.

app.anchorprotocol.com is now down????!!! will it ever work? my ETH is stuck there, wht am I supposed to do? anyone has any success contacting the devs? I'm tried discord (currently shut down), tried Telegram (can't send messages in there), and tagged them on Twitter with my issue but no luck so far...what are we supposed to do?


update node integration guide with Fastify code example

What kind of changes does this PR include?

New or updated content

Description
Adding astrojs/node + Fastify minimal code example to the docs, with the same functionality as express example has.

Ready for review 🙏

Thanks for this example!
This is actually an auto-generated file - would you mind opening a PR in the Node adapter package README?
One other thing - we should introduce with a capitalized sentence:

Or, with Fastify:

@Jutanium oh, I did not see the NOTE in the beggining of the file 🤦 I have raised an MR in node/README:  https://github.com/withastro/astro/pull/6120 PTAL.


Removed enabled tags in two plugins

Not really sure if this is the fix for the issue as this is my first contribution. Removed enabled flags for two plugins.

Not quite. You're almost there though! You see, if you load the theme, you can try to enable these two plugins by setting GEOMETRY_PROMPT_PLUGINS=(virtualenv docker_machine) in your ~/.zshrc file, before loading geometry.
If you do try to it like that, however you will notice they won't be enabled. This is because you still need to set PROMPT_DOCKER_MACHINE_ENABLED and PROMPT_VIRTUALENV_ENABLED to true.
What we want here is not having to do that at all. We want to active the behaviour just by setting GEOMETRY_PROMPT_PLUGINS=(virtualenv docker_machine). Those variables don't seem to actually needed at all!

Okay, so if I just remove the true values or do I also remove the false values ? Thank you

You can just delete the variables and remove any reference to them. The setup functions don't even need to return anything, they can just be empty: geometry_prompt_virtualenv_setup() {}

That's it! Just one final request: in order to keep the code clean and consistent throughout the codebase, can you put the empty setup functions in a single line? geometry_prompt_virtualenv_setup() {}

Perfect! Squashing and merging it. Congrats on your first contribution! 🎉 🎉 🎉

Thank you !

Late to the party. Congrats @keelan542 for your first open source contribution! The first of many more I hope!


Unable to arm custom after latest update

Hello,
After updating everything this morning, I have below the error message after calling following service:
service: alarmo.arm
data:
  mode: custom
  entity_id: alarm_control_panel.xxx

2021-11-29 08:41:29 ERROR (MainThread) [homeassistant.helpers.script.websocket_api_script] websocket_api script: Error executing script. Unexpected error for call_service at pos 1: 'armed_custom'
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 371, in _async_step
    await getattr(self, handler)()
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 571, in _async_call_service_step
    await service_task
  File "/usr/src/homeassistant/homeassistant/core.py", line 1495, in async_call
    task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1530, in _execute_service
    await handler.job.target(service_call)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 685, in handle_service
    await service.entity_service_call(
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 667, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 863, in async_request_call
    await coro
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 704, in _handle_entity_call
    await result
  File "/config/custom_components/alarmo/alarm_control_panel.py", line 351, in async_service_arm_handler
    await self.async_handle_arm_request(
  File "/config/custom_components/alarmo/alarm_control_panel.py", line 366, in async_handle_arm_request
    not (const.MODES_TO_SUPPORTED_FEATURES[arm_mode] & self.supported_features) or
KeyError: 'armed_custom'
2021-11-29 08:41:29 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [547083385056] Error handling message: Unknown error
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 26, in _handle_async_response
    await func(hass, connection, msg)
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 523, in handle_execute_script
    await script_obj.async_run(msg.get("variables"), context=context)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1243, in async_run
    await asyncio.shield(run.async_run())
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 353, in async_run
    await self._async_step(log_exceptions=False)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 371, in _async_step
    await getattr(self, handler)()
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 571, in _async_call_service_step
    await service_task
  File "/usr/src/homeassistant/homeassistant/core.py", line 1495, in async_call
    task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1530, in _execute_service
    await handler.job.target(service_call)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 685, in handle_service
    await service.entity_service_call(
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 667, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 863, in async_request_call
    await coro
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 704, in _handle_entity_call
    await result
  File "/config/custom_components/alarmo/alarm_control_panel.py", line 351, in async_service_arm_handler
    await self.async_handle_arm_request(
  File "/config/custom_components/alarmo/alarm_control_panel.py", line 366, in async_handle_arm_request
    not (const.MODES_TO_SUPPORTED_FEATURES[arm_mode] & self.supported_features) or
KeyError: 'armed_custom'

I don't think I see something related to this on the breaking changes list. Can you please help ?
Thanks !

Woops, my bad. This was unintentional.
You could use armed_custom_bypass as mode, it would work the same.
I will have to make some change to allow custom as input again.

Ok thanks !
This is working with armed_custom_bypass
Note that this is also breaking automations GUI when calling the service, we have to force yaml mode since drop-down only allows this:

Question: are other modes impacted too ?

The fix is on its way https://github.com/nielsfaber/alarmo/commit/62a6672ac9ec8d7c2e00259ab89df1be6a8c0bb6
I will update you once I released the change.

Question: are other modes impacted too ?

No, only input 'custom' is not processed correctly.

Can you update alarmo to v1.8.1? This should solve the problem.
Please close the issue if it works OK now.