Weird checkpointing behaviour

Context: followed guide to completion. Deployed subnet t01020 with bottom-up and top-down periods of 30 blocks (default). No deployment issues.
Immediately after deployment, we get (notice checkpoint send fails):
[2023-04-20T22:42:35Z INFO  ipc_agent::manager::checkpoint] Config changed, reloading checkpointing subsystem
[2023-04-20T22:42:35Z INFO  ipc_agent::manager::bottomup] Starting bottom-up checkpoint manager for (child, parent) subnet pair (/root/t01020, /root)
[2023-04-20T22:42:35Z INFO  ipc_agent::manager::topdown] Starting top-down checkpoint manager for (child, parent) subnet pair (/root/t01020, /root)
[2023-04-20T22:43:49Z INFO  ipc_agent::manager::lotus] joined subnet: /root/t01020
[2023-04-20T22:44:19Z INFO  ipc_agent::manager::lotus] joined subnet: /root/t01020
[2023-04-20T22:44:19Z INFO  ipc_agent::manager::lotus] joined subnet: /root/t01020
[2023-04-20T22:45:45Z INFO  ipc_agent::manager::topdown] Submitting topdown checkpoint for account t1zn6zwtlx5tvqwplsuwtz6hjaewkokgq373i4bqq
[2023-04-20T22:45:45Z ERROR ipc_agent::manager::topdown] error submitting top-down checkpoint for epoch 28743 in subnet: SubnetID { parent: "/root", actor: Address { payload: ID(1020) } }
[2023-04-20T22:45:45Z WARN  ipc_agent::manager::topdown] error submitting top-down checkpoint, waiting to next iteration: Err(json_rpc error: {"code":1,"message":"GasEstimateMessageGas error: gas estimation failed: CallWithGas failed: call raw get actor: resolution lookup failed (t1zn6zwtlx5tvqwplsuwtz6hjaewkokgq373i4bqq): resolve address t1zn6zwtlx5tvqwplsuwtz6hjaewkokgq373i4bqq: actor not found"})
[2023-04-20T22:45:55Z INFO  ipc_agent::manager::topdown] Submitting topdown checkpoint for account t1xqaib6dlictungc6zwbmk2gyz4qc7ksydyxltdq
[2023-04-20T22:45:55Z INFO  ipc_agent::manager::bottomup] Submitting checkpoint bottom-up for account t1zn6zwtlx5tvqwplsuwtz6hjaewkokgq373i4bqq and epoch 30 from child /root/t01020
[2023-04-20T22:45:55Z INFO  ipc_agent::manager::bottomup] checkpoint at epoch 30 contains 0 number of cross messages
[2023-04-20T22:45:55Z INFO  ipc_agent::manager::topdown] waiting for top-down checkpoint for epoch 28743 to be committed
[2023-04-20T22:45:55Z INFO  ipc_agent::manager::bottomup] waiting bottom-up for checkpoint for epoch 30 to be committed
[2023-04-20T22:45:57Z INFO  ipc_agent::manager::topdown] successfully published top-down checkpoint submission for epoch 28743
[2023-04-20T22:45:57Z INFO  ipc_agent::manager::topdown] Submitting topdown checkpoint for account t1xqaib6dlictungc6zwbmk2gyz4qc7ksydyxltdq
[2023-04-20T22:45:57Z INFO  ipc_agent::manager::topdown] waiting for top-down checkpoint for epoch 28743 to be committed
[2023-04-20T22:45:59Z INFO  ipc_agent::manager::topdown] successfully published top-down checkpoint submission for epoch 28743
[2023-04-20T22:45:59Z INFO  ipc_agent::manager::topdown] Submitting topdown checkpoint for account t1xqaib6dlictungc6zwbmk2gyz4qc7ksydyxltdq
[2023-04-20T22:45:59Z ERROR ipc_agent::manager::topdown] error submitting top-down checkpoint for epoch 28743 in subnet: SubnetID { parent: "/root", actor: Address { payload: ID(1020) } }
[2023-04-20T22:45:59Z WARN  ipc_agent::manager::topdown] error submitting top-down checkpoint, waiting to next iteration: Err(json_rpc error: {"code":1,"message":"GasEstimateMessageGas error: message execution failed: exit 22, reason: message failed with backtrace:\n00: f064 (method<PHONE_NUMBER>) -- already submitted (22)\n (RetCode=22)"})
[2023-04-20T22:46:04Z INFO  ipc_agent::manager::bottomup] successfully published bottom-up checkpoint submission for epoch 30
[2023-04-20T22:46:04Z INFO  ipc_agent::manager::bottomup] Submitting checkpoint bottom-up for account t1zn6zwtlx5tvqwplsuwtz6hjaewkokgq373i4bqq and epoch 30 from child /root/t01020
[2023-04-20T22:46:04Z INFO  ipc_agent::manager::bottomup] checkpoint at epoch 30 contains 0 number of cross messages
[2023-04-20T22:46:04Z ERROR ipc_agent::manager::bottomup] error submitting bottom-up checkpoint for epoch 30 in subnet: SubnetID { parent: "/root", actor: Address { payload: ID(1020) } }
[2023-04-20T22:46:04Z WARN  ipc_agent::manager::bottomup] error submitting bottom-up checkpoint, waiting to next iteration: Err(json_rpc error: {"code":1,"message":"GasEstimateMessageGas error: message execution failed: exit 20, reason: message failed with backtrace:\n00: f01020 (method<PHONE_NUMBER>) -- already submitted (20)\n (RetCode=20)"})

Now it's 1000 block periods later. The subnet validator logs look pretty normal, but not anything else.
Agent:
[2023-04-20T23:12:01Z INFO  ipc_agent::manager::topdown] Submitting topdown checkpoint for account t1zn6zwtlx5tvqwplsuwtz6hjaewkokgq373i4bqq
[2023-04-20T23:12:01Z ERROR ipc_agent::manager::topdown] error submitting top-down checkpoint for epoch 29073 in subnet: SubnetID { parent: "/root", actor: Address { payload: ID(1020) } }
[2023-04-20T23:12:01Z WARN  ipc_agent::manager::topdown] error submitting top-down checkpoint, waiting to next iteration: Err(json_rpc error: {"code":1,"message":"GasEstimateMessageGas error: message execution failed: exit 22, reason: message failed with backtrace:\n00: f064 (method<PHONE_NUMBER>) -- already submitted (22)\n (RetCode=22)"})
[2023-04-20T23:12:11Z INFO  ipc_agent::manager::topdown] Submitting topdown checkpoint for account t1xqaib6dlictungc6zwbmk2gyz4qc7ksydyxltdq
[2023-04-20T23:12:11Z ERROR ipc_agent::manager::topdown] error submitting top-down checkpoint for epoch 29073 in subnet: SubnetID { parent: "/root", actor: Address { payload: ID(1020) } }
[2023-04-20T23:12:11Z WARN  ipc_agent::manager::topdown] error submitting top-down checkpoint, waiting to next iteration: Err(json_rpc error: {"code":1,"message":"GasEstimateMessageGas error: message execution failed: exit 22, reason: message failed with backtrace:\n00: f064 (method<PHONE_NUMBER>) -- already submitted (22)\n (RetCode=22)"})
[2023-04-20T23:12:20Z INFO  ipc_agent::manager::bottomup] successfully published bottom-up checkpoint submission for epoch 210
[2023-04-20T23:12:20Z INFO  ipc_agent::manager::bottomup] Submitting checkpoint bottom-up for account t1yihlouxw3sxwbk2sqcnde3hekh6qwbhmlc2cjwy and epoch 210 from child /root/t01020
[2023-04-20T23:12:20Z INFO  ipc_agent::manager::bottomup] checkpoint at epoch 210 contains 0 number of cross messages
[2023-04-20T23:12:20Z ERROR ipc_agent::manager::bottomup] error submitting bottom-up checkpoint for epoch 210 in subnet: SubnetID { parent: "/root", actor: Address { payload: ID(1020) } }
[2023-04-20T23:12:20Z WARN  ipc_agent::manager::bottomup] error submitting bottom-up checkpoint, waiting to next iteration: Err(json_rpc error: {"code":1,"message":"GasEstimateMessageGas error: message execution failed: exit 20, reason: message failed with backtrace:\n00: f01020 (method<PHONE_NUMBER>) -- already submitted (20)\n (RetCode=20)"})

(note that it's trying and failing to submit checkpoint for epoch 210)
Checkpoints are in fact getting in, but lagging way behind:
ubuntu@ip-172-26-28-130:~/ipc$ ./ipc-agent/bin/ipc-agent checkpoint list-bottomup --from-epoch 1 --to-epoch 28000 --subnet /root/t01020
[2023-04-20T23:13:53Z INFO  ipc_agent::cli::commands::checkpoint::list_checkpoints] epoch 30 - prev_check="bafy2bzacedkoa623kvi5gfis2yks7xxjl73vg7xwbojz4tpq63dd5jpfz757i", cross_msgs={"cross_msgs":[],"fee":[]}, child_checks=[]
[2023-04-20T23:13:53Z INFO  ipc_agent::cli::commands::checkpoint::list_checkpoints] epoch 60 - prev_check="bafy2bzacebxuxxjwfmdwhpnwvqo3tvcijtnmilfgik2r25ptvqtzsknpzxwlc", cross_msgs={"cross_msgs":[],"fee":[]}, child_checks=[]
[2023-04-20T23:13:53Z INFO  ipc_agent::cli::commands::checkpoint::list_checkpoints] epoch 90 - prev_check="bafy2bzacedl77x7rsvcnhrkiynyrqggkdcypjekoosvrmgooz5c32ey5mdyhg", cross_msgs={"cross_msgs":[],"fee":[]}, child_checks=[]
[2023-04-20T23:13:53Z INFO  ipc_agent::cli::commands::checkpoint::list_checkpoints] epoch 120 - prev_check="bafy2bzaceae6g5akfzqcye3mrziihefqkaoskbkiyu7seotn4eeciibkofjas", cross_msgs={"cross_msgs":[],"fee":[]}, child_checks=[]
[2023-04-20T23:13:53Z INFO  ipc_agent::cli::commands::checkpoint::list_checkpoints] epoch 150 - prev_check="bafy2bzaceaf4pyuqfluwj2xopcm774ug5gjrqw52ictsbqis4bkb7uts6mcdg", cross_msgs={"cross_msgs":[],"fee":[]}, child_checks=[]
[2023-04-20T23:13:53Z INFO  ipc_agent::cli::commands::checkpoint::list_checkpoints] epoch 180 - prev_check="bafy2bzaceals7ybcw5cisibz3bwxzzoa3tjauxkfmruhk5vjbx6ytjcmatgh6", cross_msgs={"cross_msgs":[],"fee":[]}, child_checks=[]

Because, at this time, this is where the subnet miner is:
2023-04-20T23:15:08.622Z        INFO    mir-consensus   mir/state_manager.go:536        Snapshot for epoch 1756 started {"validator": "t1zn6zwtlx5tvqwplsuwtz6hjaewkokgq373i4bqq"}
2023-04-20T23:15:08.622Z        INFO    mir-consensus   mir/state_manager.go:544        Snapshot started: epoch - 1756, height - 5268   {"validator": "t1zn6zwtlx5tvqwplsuwtz6hjaewkokgq373i4bqq"}
2023-04-20T23:15:08.622Z        INFO    mir-consensus   mir/state_manager.go:559        waiting for latest block (5268) before checkpoint to be synced to assemble the snapshot {"validator": "t1zn6zwtlx5tvqwplsuwtz6hjaewkokgq373i4bqq"}
2023-04-20T23:15:08.622Z        INFO    mir-consensus   mir/state_manager.go:769        waitForHeight 5268 started      {"validator": "t1zn6zwtlx5tvqwplsuwtz6hjaewkokgq373i4bqq"}
2023-04-20T23:15:08.622Z        INFO    mir-consensus   mir/state_manager.go:775        waitForHeight 5268 finished     {"validator": "t1zn6zwtlx5tvqwplsuwtz6hjaewkokgq373i4bqq"}
2023-04-20T23:15:08.623Z        INFO    mir-consensus   mir/state_manager.go:572        Getting Cid for block height 5268 and cid bafy2bzacealbuwsudfl52oaxioppjw3loiffhrx2rmaekcakeonoyaj5fcada to include in snapshot        {"validator": "t1zn6zwtlx5tvqwplsuwtz6hjaewkokgq373i4bqq"}
2023-04-20T23:15:08.624Z        INFO    mir-consensus   mir/state_manager.go:572        Getting Cid for block height 5267 and cid bafy2bzacecndmni6abthskuyxnsmlgduis2yxn77tlw2kzisubdkmeupn3cgo to include in snapshot        {"validator": "t1zn6zwtlx5tvqwplsuwtz6hjaewkokgq373i4bqq"}
2023-04-20T23:15:08.624Z        INFO    mir-consensus   mir/state_manager.go:572        Getting Cid for block height 5266 and cid bafy2bzacebmbzclgjlsrocxhj5d55ilijgntdlhy2ux3vkgpzzoco32augdyw to include in snapshot        {"validator": "t1zn6zwtlx5tvqwplsuwtz6hjaewkokgq373i4bqq"}
2023-04-20T23:15:08.624Z        INFO    mir-consensus   mir/state_manager.go:580        Snapshot finished: epoch - 1756, height - 5268  {"validator": "t1zn6zwtlx5tvqwplsuwtz6hjaewkokgq373i4bqq"}
2023-04-20T23:15:08.624Z        INFO    mir-consensus   mir/state_manager.go:581        Snapshot for epoch 1756 finished        {"validator": "t1zn6zwtlx5tvqwplsuwtz6hjaewkokgq373i4bqq"}
2023-04-20T23:15:08.632Z        INFO    mir-consensus   mir/state_manager.go:591        Checkpoint for epoch 1756 started       {"validator": "t1zn6zwtlx5tvqwplsuwtz6hjaewkokgq373i4bqq"}
2023-04-20T23:15:08.632Z        INFO    mir-consensus   mir/state_manager.go:599        Mir generated new checkpoint for height: 5269   {"validator": "t1zn6zwtlx5tvqwplsuwtz6hjaewkokgq373i4bqq"}
2023-04-20T23:15:08.632Z        INFO    mir-consensus   mir/state_manager.go:614        deliverCheckpoint for height 5269 started       {"validator": "t1zn6zwtlx5tvqwplsuwtz6hjaewkokgq373i4bqq"}
2023-04-20T23:15:08.641Z        INFO    mir-consensus   mir/state_manager.go:667        deliverCheckpoint for height 5269 finished      {"validator": "t1zn6zwtlx5tvqwplsuwtz6hjaewkokgq373i4bqq"}
2023-04-20T23:15:08.641Z        INFO    mir-consensus   mir/state_manager.go:608        Checkpoint for epoch 1756 finished      {"validator": "t1zn6zwtlx5tvqwplsuwtz6hjaewkokgq373i4bqq"}

And the root eudico shows:
2023-04-20T23:16:51.039Z        WARN    rpc     go-jsonrpc@v0.2.3/handler.go:406        error in RPC call to 'Filecoin.MpoolPushMessage': GasEstimateMessageGas error:
    github.com/filecoin-project/lotus/node/impl/full.(*MpoolAPI).MpoolPushMessage
        /home/ubuntu/ipc/lotus/node/impl/full/mpool.go:196
  - message execution failed: exit 20, reason: message failed with backtrace:
    00: f01020 (method<PHONE_NUMBER>) -- already submitted (20)
     (RetCode=20):
    github.com/filecoin-project/lotus/node/impl/full.gasEstimateGasLimit
        /home/ubuntu/ipc/lotus/node/impl/full/gas.go:327
2023-04-20T23:17:05.873Z        WARN    sub     sub/incoming.go:102     received block with large delay from miner      {"block": "bafy2bzacebumm3wemlw5qc3p3j4fv7n36hpfb4dfphbzvshcisjqjckgtc7f4", "delay":<PHONE_NUMBER>, "miner": "t00"}

That was bottom-up. Top-down seem to be getting through (and so do funds), even if a little delayed? At height 29315, a query shows:
ubuntu@ip-172-26-28-130:~/ipc$ ./ipc-agent/bin/ipc-agent checkpoint last-topdown --subnet /root/t01020
[2023-04-20T23:18:52Z INFO  ipc_agent::cli::commands::checkpoint::topdown_executed] Last top-down checkpoint executed in epoch: 29153
ubuntu@ip-172-26-28-130:~/ipc$ ./ipc-agent/bin/ipc-agent checkpoint last-topdown --subnet /root/t01020
[2023-04-20T23:19:38Z INFO  ipc_agent::cli::commands::checkpoint::topdown_executed] Last top-down checkpoint executed in epoch: 29163

But that isn't the weird part. That would be topdown checkpoints being committed every 10 seconds, despite the actor having been deployed with 30s period.
I feel like I tried things one too many times and might be making stupid mistakes, but I don't know what that would be in this case. it really did all seem to go well.

This is related with: https://github.com/consensus-shipyard/ipc-actors/issues/97
And is the expected behavior after introducing this horrible patch. It will  be fixed soon.

Fixed in #185, #182, #184


Add optional argument in pre_processing_wine.py

Please run code below to get preprocessed data.
# Get preprocessed data with splitting
python src/pre_processing_wine.py --in_file_1="data/raw/winequality-red.csv" --in_file_2="data/raw/winequality-white.csv" --out_dir="data/processed/"

# Get preprocessed data without splitting
python src/pre_processing_wine.py --in_file_1="data/raw/winequality-red.csv" --in_file_2="data/raw/winequality-white.csv" --out_dir="data/processed/" --split="n"

Code run well. But I think the usage of option split = 'n' is flipped in the documentation from. i.e. split = 'n' equal not splitting instead of split. Suggest fix as follow.
[--split=<split>]            Condsider wheater splict data or not. if --splict ='n', code will split data

to
[--split=<split>]            Condsider whether to split data or not. if --splict ='n', code will NOT split data`

If you are ok and fix the .py, I will proceed to merge this.
Thank you.

@athy9193 I fixed .py file. Ready to merge. 👍


IsNumber function returns false for floats

IsNumber function currently returns false if you pass it a non-integer value. Basically, it checks if a number is an integer.

This function should either return true for all numbers or be renamed to isInteger.
From MDN docs: The JavaScript Number type is a double-precision 64-bit binary format IEEE 754.

https://github.com/rayepps/radash/blob/b1e2a8b16de764d2c860e01332130002b2e1ce3a/src/typed.ts#L21-L25

Great catch @jovanamatk 👍 I'd like to have an isInt, isFloat as well as an isNumber function that unions the more int/float check.
This is pretty bad... I'll make a change and fix tonight.


Removing playSound's default value

This at least gets us the old behavior in the toolbox (Power Up is selected by default) and the completions from Monaco are no longer broken (you get an empty string; not ideal but whatever)
Any other fix will require changes to PXT. Just to break down why this is an issue:
playSound() takes a string argument but uses a shadow block called sound() for the default value in blocks
sound() takes an enum argument and returns a string
In PXT when you give a default value for an argument then that value is sent to the shadow block in the toolbox and also the completion snippets in Monaco. Usually that works because the shadow block doesn't do anything to the value (shim=TD_ID) and so the same default argument for the shadow block also works for the parameter. Because the sound() shadow block actually does something to the argument it is passed (turns a number into a string) our strategy breaks down here.
We need a new authoring syntax for specifying default values on the shadow and for the actual API.

Could you please file a bug for the need of the new authoring syntax, linking this issue. (For tracking purposes).


Don't Merge! PR real time test for webhook case

Docs Build status updates of commit a1fc4c3:
:clock10: Pending: waiting for processors (17 builds ahead of you)
:warning: Docs Build is busy, currently there are 17 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit a1fc4c3:
:clock10: Full build: the average full build time is 7 min(s) 49 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit a1fc4c3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/testing.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Updated Cookies + Privacy Policy for slow.trade Mainnet

Content Stuff

added privacy policy + cleanup + links to sections
a. opted for brevity & ease via PDF link

Travis automatic deployment:
https://pr391--dxreact.review.gnosisdev.com

Travis automatic deployment:
https://pr391--dxreact.review.gnosisdev.com


Text change in the Capability Level diagram(s): change from "Phase" to "Level"

Description of the change:
Text change in Capability Diagram: change from using "Phase" to "Level".
Motivation for the change:
Synced up with the terminology being used for "Capability Level".

FYI @dmesser , this is the diagram changed you are looking for.


arg_parse.c: Keep print sequences as command gives

Hi again, @danny-burrows!
I've implemented the feature that supports multiple-file conversion at #1,
but I discovered that the results of conversions were printed in reverse order.
To fix this problem, I add a singly linked list with caching a last node, and apply it to the arg_parse() function.
(Of course, this affects other relative files.)
There are a few(?) changes for this PR. Please check this out.
Thanks to read.

Hi there, thanks for your contribution! Apologies for the delay in responding to this. I believe this functionality has been implemented on main, as such I'm gonna go ahead and close this but please do feel free to open an issue if there is anything remaining you'd like to see added in!


result [FEATURE]

Is your feature request related to a problem? Please describe.
on displaying result, there should be the use of adjectives according to score. like excellent, very good, good, needs improvement, etc.
Describe the solution you'd like]
it could be done using conditionals in js

Can I please work on this


[Docs] Converting PyTorch to Relax

Hello,
I am currently working on converting a PyTorch model using TVM Relax.
I have some question regarding how iteration in PyTorch dynamo handled within TVM Relax.
There is no examples and document about it.
I think Relax IR given like LLVM IR.
Thank you!

Here is the doc about importing pytorch model into Relax.
https://tvm.apache.org/docs/how_to/tutorials/e2e_opt_model.html

Thank you for relay!
I will read document carefully.


Feedback about ASP.NET Core 2.2 preview web application template

Is this a Bug or Feature request?:
Feature request
Description of the problem:
I’ve tried the preview of ASP.NET Core 2.2 and created a new web application. I do like that it based on Bootstrap 4. But I find that the template is be too simple. I would like to see some sample pages where the most common scenarios are covered on a basic level. For instance:

A page showing how to create an object, with post and validation. Using a real database is maybe too complicated but storing stuff in a static list will show the concept.
A page where to search for objects, with a get request.
A page using ajax against an API, maybe using TypeScript.
A page with some common BootStrap controls and responsive design.
A page describing how to change the top menu.
A page showing how to work with localization.
A page showing how LibMan works. Or at least having a LibMan-file in the project and reference to some documentation.

I’m not asking for a complete tutorial. But I do think it would be useful for beginners (and developers like me that never learn :-) to have a better starting point in the template. It could be a bit overwhelming to learn web development, a good template could make that easier.
I know that a lot of developers wants the template to be as simple as possible. But I think it’s better that experienced developers learn how to delete pages than that beginners need to write pages from scratch :-) If most sample code is isolated to one folder it doesn’t need to be that bad.

Thanks for your feedback, @pekspro.
@danroth27, I'll leave this to you to process.

@pekspro Thanks for this feedback! It's a tricky balance to figure out how much sample code to include in the project templates so that beginners have an easy way to get started, but more experienced devs don't get frustrated with having to delete a bunch of code every time they create a project. Over the years we've heard consistent feedback the customers want a simpler template with less noise, so that's the direction we decided to go with for this release. But, we do understand that not everyone feels this way and hearing your opinion helps us get a more complete picture of what developers want.
For many of the scenarios you listed above, it sounds like you are looking for sample apps to help you learn different aspects of the framework. For samples I would recommend looking at the various tutorials and topics in the docs.

No problem, I just wanted to share my thoughts :-) Thanks for a quick reply!


[DDW-1083] Build Daedalus with Nix flakes

This PR uses the new nix3 CLI, and flakes.
Todos

[ ] Hydra errors – https://hydra.iohk.io/jobset/Cardano/daedalus-pr-3008#tabs-errorserror: access to URI 'https://api.github.com/repos/divnix/std/tarball/3be03536b3a6767b5542fa14339fc34f5ea22ee7'
    is forbidden in restricted mode

[ ] Windows signing (nix run script)
[ ] verify that release scripts / proposal-ui still work in a test release (@michalrus needs to get access to the release machines first)
[ ] follow-up PRs – a lot more changes/clean-up needed

Screenshots
n/a
Testing Checklist

TODO: Slack QA thread
[ ] Test

Review Checklist
Basics

[x] PR assigned to the PR author(s)
[ ] input-output-hk/daedalus-dev and input-output-hk/daedalus-qa assigned as PR reviewers
[ ] If there are UI changes, Alexander Rukin assigned as an additional reviewer
[ ] All visual regression testing has been reviewed (assign run Chromatic label to PR to trigger the run)
[ ] PR has appropriate labels (release-vNext, feature/bug/chore, WIP)
[ ] PR link is added to a Jira ticket, ticket moved to In Review
[ ] PR is updated to the most recent version of the target branch (and there are no conflicts)
[ ] PR has a good description that summarizes all changes
[ ] PR contains screenshots (in case of UI changes)
[ ] CHANGELOG entry has been added to the top of the appropriate section (Features, Fixes, Chores) and is linked to the correct PR on GitHub
[ ] There are no missing translations (running yarn manage:translations produces no changes)
[ ] Text changes are proofread and approved (Jane Wild / Amy Reeve)
[ ] Japanese text changes are proofread and approved (Junko Oda)
[ ] Storybook works and no stories are broken (yarn storybook)
[ ] In case of dependency changes yarn.lock file is updated

Code Quality

[ ] Important parts of the code are properly commented and documented
[ ] Code is properly typed with typescript types
[ ] React components are split-up enough to avoid unnecessary re-renderings
[ ] Any code that only works in main process is neatly separated from components

Testing

[ ] New feature/change is covered by acceptance tests
[ ] New feature/change is manually tested and approved by QA team
[ ] All existing acceptance tests are still up-to-date
[ ] New feature/change is covered by Daedalus Testing scenario
[ ] All existing Daedalus Testing scenarios are still up-to-date

After Review

[ ] Update Slack QA thread by marking it with a green checkmark

Quick favor: merge develop branch into this branch so that I can build 5.1 with the flake?

@quinn-dougherty okay, I’ll try to squeeze in resolving those conflicts today =)

/cc @tgunnoe

@quinn-dougherty there you go, just pushed the merge :octocat:


Try to fix cloning of repo's where a branch got created, instantly de…

Thanks a lot for the pull request you are going to do!
Please verify that you validate these points:

[ ] indentation is made with 4 spaces
[ ] your pull request contains only changes intended (no refactoring, line return added, ... that could make code review harder. Make another one if you think it is needed...)
[ ] run and verify that existing tests pass and add some new units tests, if needed.
[ ] update the documentation, if needed.
[ ] update the release notes file
…leted and then recreated

(works on my machine)

This PR worked for my project. Thanks

Hi @elangelo, thanks for the contribution! Can you describe the problem you're solving and the approach you took here? Please remove whitespace-only changes, they make it harder to review. There's a merge conflict with master, can you rebase on master or merge in master and fix the conflict?

Hi,
Glad someone is finally looking at this issue. I've tried to rebase my changes on master but the conflict is exactly where i started changing code so i'm unsure how to proceed. (TfsHelper.Commons.c : private void GetRootChangesetForBranch). The code that is there now is also completely different from what was there when i first branched the repo so i'm not sure which cases this change fixes...
The problem that i was trying to solve is where git-tfs would be confused on how to find the first changeset of a certain branch. Our developers have a habit (???) of creating a branch, deleting it almost instantly and then recreating the branch again (with exactly the same name) a bit later. This confuses git-tfs because it will just pick the changeset where the branch was created first instead of taking the 'second' creation changeset.
I wrote this code quite a while back, but as i remember git-tfs searches from the last changeset to the first changeset of that branch. All i did was look for the first changeset that is a ChangeType.Branch instead of keep on searching till i get to the first changeset of the branch. (which is a fluke as it was deleted shortly after).
T

Is someone still working on integrating this patch??


Section for non-technical readers

To make D3 more approachable to a larger number of users—from informed developers to curious passersby and new and interested visitors—I have added a new section to the README. The section is entitled What to Use D3 for and When to Use It. As the name suggests, the new section, a brief paragraph, explains in plain and straightforward language what D3 is used for and when one should consider using it in a project.
Other repositories may begin to use this new informative and catchy section soon, as my colleagues contact open-source technologies in an effort to make them more accessible to the tens of thousands of new users learning to code and thousands joining GitHub every day.
Thank you!

I appreciate the suggestion, but I think this longer material is better suited to the publicly-editable wiki rather than the README. Thanks.


[Bug] KBM - A key is pressed even if it is released

Platform

Device: Desktop
OS: Windows
Browser: Edge
Browser Version: 109
Better xCloud Version: 3.0.3

Describe the bug
Sometimes it happens that a key is pressed even if you release it. After this, the key is released after quite a long time (5-10 seconds), and sometimes it is not released at all.
The only thing that helps is minimizing the browser (or just clicking on another window) and going back.
It's not about Internet speed/latency. Changing to a lower resolution (1080p -> 720) did not help.
I don't have the Xbox xCloud Keyboard and Mouse extension.
Screenshots/Videos
Video (trying to scroll the steering wheel to the left, but due to the fact that D (I'm using the WASD preset) is pressed, it scrolls only to the center)

I have the same problem, I already tried changing browsers and it still didn't solve it.

Any chance you're using/enabling different input method (to type languages other than English) while playing?

it hapens to me almost instantly

Estou tendo o mesmo problema, rotineiramente...

Same here.
Chrome with the 3.0.3 version.

Any chance you're using/enabling different input method (to type languages other than English) while playing?
Does it happend with <IP_ADDRESS>?

Please answer my question

Try to switch to English keyboard and try again

Alguma chance de você estar usando/habilitando método de entrada diferente (para digitar idiomas diferentes do inglês) durante a reprodução?
Isso acontece com o <IP_ADDRESS>?

Yes, I use the Brazilian input to type, I'm Brazilian, but what I found strange was the fact that no one here in Brazil reported this problem.

Alguma chance de você estar usando/habilitando método de entrada diferente (para digitar idiomas diferentes do inglês) durante a reprodução?
Isso acontece com o <IP_ADDRESS>?

Sim, eu uso a entrada brasileira para digitar, sou brasileiro, mas o que achei estranho foi o fato de que ninguém aqui no Brasil relatou esse problema.

I reported it but the adm closed it because it had already reported the bug...
But is it just changing the keyboard to English?

I have the same problem after I updated to better xcloud 3.0.3

Alguma chance de você estar usando/habilitando método de entrada diferente (para digitar idiomas diferentes do inglês) durante a reprodução?
Isso acontece com o <IP_ADDRESS>?

Sim, eu uso a entrada brasileira para digitar, sou brasileiro, mas o que achei estranho foi o fato de que ninguém aqui no Brasil relatou esse problema.

I'm also Brazilian and I'm going through the problem

Any chance you're using/enabling different input method (to type languages other than English) while playing?
Does it happend with <IP_ADDRESS>?

Yes, but after enabling another input method the problem still exists.
On version <IP_ADDRESS> I don’t see this problem, but I see another one. If I hold A+D and then release one key, I have to wait about a second until the second key is pressed again.

Try this version: https://github.com/redphx/better-xcloud/raw/main/better-xcloud.user.js

Try this version: https://github.com/redphx/better-xcloud/raw/main/better-xcloud.user.js This version also increase the responsiveness of the emulated sticks

Bro, I tested this version and it worked as far as I played, for about 20 minutes without any problems described, I only tested it on a server and so far I haven't had any problems.

Bro, I tested this version and it worked as far as I played, for about 20 minutes without any problems described, I only tested it on a server and so far I haven't had any problems.

Thanks for testing. It should work with all servers and games.

Try this version: https://github.com/redphx/better-xcloud/raw/main/better-xcloud.user.js This version also increase the responsiveness of the emulated sticks

I tested this too and there were no problems. The sticks actually respond faster, which is nice. Thank you.

Bro, I tested this version and it worked as far as I played, for about 20 minutes without any problems described, I only tested it on a server and so far I haven't had any problems.

Thanks for testing. It should work with all servers and games.

I tested it here and it's working fine, thanks

Fixed in 3.0.4

Try this version: https://github.com/redphx/better-xcloud/raw/main/better-xcloud.user.js This version also increase the responsiveness of the emulated sticks

It works!, thank you very much

Fixed in 3.0.4

What I can say is that I felt that in version 3.0.3 in the shooters the right stick was more fluid, now it moves more square

Fixed in 3.0.4

What I can say is that I felt that in version 3.0.3 in the shooters the right stick was more fluid, now it moves more square

I didn't change the behaviour of the mouse movement


Align Brainwave types

Updates the brainwave type definitions to match the actual API spec as documented in https://docs.neurosity.co/docs/api/brainwaves.
Changes:

Adds channelNames and notchFrequency to BrainwaveInfo interface
Updates Epoch, PSD, and PowerByBand interfaces to use the complete BrainwaveInfo type

update to:
export interface Epoch {
  data: AmplitudeByChannel;
  info: BrainwaveInfo;
}

export interface PSD {
  psd: PSDByChannel;
  freqs: number[];
  info: BrainwaveInfo;
}

export interface PowerByBand {
  gamma: number[];
  beta: number[];
  alpha: number[];
  theta: number[];
  delta: number[];
  info: BrainwaveInfo;
}

Also rawUnfiltered is not in the types


Printing the error stack on errors

Often faced issues with migration.js having errors and the tool not pointing out the exact error. One can just add a DEBUG=true when running mm to see the error stack.

Added a parameter to the exit method
Added a flag: process.env.DEBUG
Printed the Error.stack on exit via console.error
Docs added for DEBUG flag

added a check for existence of err and err.stack

Thanks.
Can you please update it another time?
exit = (msg, err) ->
    if msg
        console.error "Error: " + msg,
        if debug and err?.stack
            console.error err.stack
        process.exit 1
    process.exit 0

done :) !

Oops, I'm sorry, there shouldn't be a trailing comma after the msg

  console.error("Error: " + msg);
      if (debug && (err != null ? err.stack : void 0)) {
        console.error(err.stack);
      }

turns out to be something like this

It should be like that, but it isn't atm, check the diff. Please remove the
comma and will be good to merge
On Чт, 17 марта 2016 г. at 15:27 Mohammad Umair Khan <
<EMAIL_ADDRESS>wrote:

console.error("Error: " + msg);
if (debug && (err != null ? err.stack : void 0)) {
console.error(err.stack);
}
turns out to be something like this
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/emirotin/mongodb-migrations/pull/15#issuecomment-197855705

Should be good to go now.

:+1:


It is really difficult to inspect mutations

When I'm inspecting a mutation I want to easily check the mutation data.
Right now, the mutation information is listed at the end of the inspect panel, the user needs to scroll all the way down(Through state & getters) to see it, this is an issue if your state and getters are big.
Solutions:

Move the mutation information to the top.
Create like tabs, or app bar with direct access buttons to the state, getters, a mutation information
Collapse state tree

Potentially fixed by #477


Some names of Environment lead to parser error

Hello,
why is it that some variable names raise an UnexpectedCharacters error when using them to create a new Quadrupole object? Here is a minimal working example:

import xtrack as xt

env = xt.Environment()

env['l_quad'] = 0.2  # [m]

for it in range(5):
    env.set(f'quad{it+1}_k1', it)   # this name works
    env.new(f'Q{it+1}', xt.Quadrupole, length='l_quad', k1=f'quad{it+1}_k1')

    env.set(f'k1_Q{it+1}', it)  # raises UnexpectedCharacters
    env.new(f'newQ{it+1}', xt.Quadrupole, length='l_quad', k1=f'k1_Q{it+1}')

Thanks for your help!

Hello, at the moment indeed we don't support capital letters (historical reasons).
This limitation will be removed soon


packet inject problem

When I use the function of Generator, the problem appears:
2017-08-17 10:21:18.192770 I | http: panic serving <IP_ADDRESS>:14376: runtime error: invalid memory address or nil pointer dereference
goroutine 389 [running]:
net/http.(*conn).serve.func1(0xc42258e820)
/usr/local/go/src/net/http/server.go:1721 +0xd0
panic(0x11f6420, 0x1dec710)
/usr/local/go/src/runtime/panic.go:489 +0x2cf
github.com/skydive-project/skydive/packet_injector.(*PacketInjectorClient).InjectPacket(0xc420138350, 0xc422695f20, 0x24, 0xc42258ee60, 0xc42258ee60, 0x0, 0x0, 0xe4000000013237c0)
/root/work/src/github.com/skydive-project/skydive/packet_injector/client.go:50 +0x130
github.com/skydive-project/skydive/api.(*PacketInjectorAPI).injectPacket(0xc42095b6c0, 0x1e15e00, 0xc4218e5dc0, 0xc421e56d80)
/root/work/src/github.com/skydive-project/skydive/api/packet_injector.go:174 +0x18d
github.com/skydive-project/skydive/api.(*PacketInjectorAPI).(github.com/skydive-project/skydive/api.injectPacket)-fm(0x1e15e00, 0xc4218e5dc0, 0xc421e56d80)
/root/work/src/github.com/skydive-project/skydive/api/packet_injector.go:212 +0x48
github.com/skydive-project/skydive/http.(*NoAuthenticationBackend).Wrap.func1(0x1e15e00, 0xc4218e5dc0, 0xc420081800)
/root/work/src/github.com/skydive-project/skydive/http/noauth.go:44 +0xf8
net/http.HandlerFunc.ServeHTTP(0xc42095b800, 0x1e15e00, 0xc4218e5dc0, 0xc420081800)
/usr/local/go/src/net/http/server.go:1942 +0x44
github.com/skydive-project/skydive/vendor/github.com/gorilla/mux.(*Router).ServeHTTP(0xc4213cbe00, 0x1e15e00, 0xc4218e5dc0, 0xc420081800)
/root/work/src/github.com/skydive-project/skydive/vendor/github.com/gorilla/mux/mux.go:100 +0x255
net/http.serverHandler.ServeHTTP(0xc421429540, 0x1e15e00, 0xc4218e5dc0, 0xc420081800)
/usr/local/go/src/net/http/server.go:2568 +0x92
net/http.(*conn).serve(0xc42258e820, 0x1e17180, 0xc4218fa0c0)
/usr/local/go/src/net/http/server.go:1825 +0x612
created by net/http.(*Server).Serve
/usr/local/go/src/net/http/server.go:2668 +0x2ce

metadatas(id: 2dc3c058-c50e-40e8-614c-ac79b5be9ef3)
Driver : openvswitch
EncapType : ether
FDB :
Flags : 2
MAC : 33:33:00:00:00:01
State : 128
Type : 0
Flags : 2
MAC : 01:00:5e:00:00:01
State : 128
Type : 0
Flags : 2
MAC : 33:33:ff:7b:50:09
State : 128
Type : 0
IPV6 :

fe80::3c48:79ff:fe7b:5009/64
IfIndex : 13
MAC : f0:2f:a7:2d:17:98
MTU : 1500
Name : external_api
OfPort : 2
State : UP
TID : 7d9c8c73-20fb-508e-6da9-e7186e6ba26d
Type : internal
UUID : e31c19c2-bb25-468d-9839-16b857096e3c

Driver : tun
EncapType : ether
FDB :
Flags : 0
MAC : fa:16:3e:01:13:b0
State : 2
Type : 0
Flags : 0
MAC : fe:16:3e:01:13:b0
State : 128
Type : 0
Flags : 0
MAC : fe:16:3e:01:13:b0
State : 128
Type : 0
Flags : 2
MAC : 33:33:00:00:00:01
State : 128
Type : 0
Flags : 2
MAC : 01:00:5e:00:00:01
State : 128
Type : 0
Flags : 2
MAC : 33:33:ff:01:13:b0
State : 128
Type : 0
IPV6 :

fe80::fc16:3eff:fe01:13b0/64
IfIndex : 107
MAC : fe:16:3e:01:13:b0
MTU : 9000
Name : tap4d17820b-d1
Speed : 10
State : UP
TID : 789d55f4-6005-5acb-772d-3925ecda8848
Type : tun

analyzer's config:
# Skydive config file

# host_id is used to reference the agent by default set to hostname
# host_id:

# WebSocket Ping/Pong timeout in second
ws_pong_timeout: 5
# maximum number of topology aggregated messages before sending
# ws_bulk_maxmsgs: 100
# duration in seconds before flushing topology aggregated messages
# ws_bulk_maxdelay: 2

openstack:
#  auth_url: http://xxx.xxx.xxx.xxx:5000/v2.0
# auth_url:http://<IP_ADDRESS>/dashboard/auth/login/
# username: admin
#  password: 79da84d0ab01481f
#  tenant_name: admin
#  region_name: RegionOne
  # The endpoint_type value must be 'public', 'internal' or 'admin'
#  endpoint_type: public
  # When using Keystone V3, domain_name needs to be specified
  # domain_name: MyDomain

analyzer:
  # address and port for the analyzer API, Format: addr:port.
  # Default addr is <IP_ADDRESS>
  listen: <IP_ADDRESS>:8082
  # File path to X509 Certificate and Private Key to enable TLS communication
  # Must be different than the agent
  # X509_cert: /etc/ssl/certs/analyzer.domain.com.crt
  # X509_key:  /etc/ssl/certs/analyzer.domain.com.key

  # Flow storage engine
  storage:
      # Available: elasticsearch, orientdb
      backend: elasticsearch
      # maximum number of flows aggregated between two data store inserts
      bulk_insert: 100
      # deadline of each bulk insert in second
      bulk_insert_deadline: 5
  topology:
    # Define static interfaces and links updating Skydive topology
    # Can be useful to define external resources like : TOR, Router, etc.
    #
    # A description language similar to the dot language is used to define
    # interfaces and links. An arrow (->) is used to define a link between
    # two interfaces (parent -> child).
    # Square brackets after the arrow is used to define additional metadata
    # of the link (->[key=value,..]). Each interface described will be
    # created in the topology excepted interfaces with the local prefix.
    # In that specific case the interface of the local host will be used.
    # Attributes of interfaces are declared using square brackets ([]).
    # The following example creates a TOR1 node linked to a TOR1_PORT1 which is
    # linked to the local interface eth0.
    fabric:
       - TOR1[Name=tor1] -> [color=red] TOR1_PORT1[Name=port1, MTU=1500]
       - TOR1_PORT1 -> *[Type=host]/eth0
  # update rate of links in seconds
  bandwidth_update_rate: 5
  # interface metrics - 'netlink'
  # captured flows TxBytes + RxByte - 'flows' (need to turn on capture)
  bandwidth_source: netlink
  # 'absolute' - thresholds in Kbit
  # 'relative' - thresholds in % relative to link speed reported by netlink
  bandwidth_threshold: absolute
  bandwidth_absolute_active: 1
  bandwidth_absolute_warning: 10
  bandwidth_absolute_alert: 100
  bandwidth_relative_active: 0.1
  bandwidth_relative_warning: 0.4
  bandwidth_relative_alert: 0.8

# list of analyzers used by analyzers and agents
analyzers:
  - <IP_ADDRESS>:8082

agent:
  # address and port for the agent API, Format: addr:port.
  # Default addr is <IP_ADDRESS>
  listen: :8081
  # File path to X509 Certificate and Private Key to enable TLS communication
  # Must be different than the analyzer and unique per agent (recommended)
  # X509_cert: /etc/ssl/certs/agent.domain.com.crt
  # X509_key:  /etc/ssl/certs/agent.domain.com.key
  # Server name field specified in TLS communications.
  # Not required, but can be used to allow virtual hosting
  # X509_servername: domain.com
  #
  topology:
    # Probes used to capture topology informations like interfaces,
    # bridges, namespaces, etc...
    # Available: ovsdb, docker, neutron, opencontrail
    probes:
      - ovsdb
      # - docker
      # - neutron
      # - opencontrail
    netlink:
      # delay in seconds between two metric updates
      # metrics_update: 30
  flow:
    # Period in second to get capture stats from the probe. Note this
    # currently only works for the pcap probe
    # stats_update: 1
  metadata:
    info: This is compute node

sflow:
  # Default listening address is <IP_ADDRESS>
    bind_address: <IP_ADDRESS>

  # Port min/max used when starting a sflow probe, a agent will be started
  # with a port from this range
    port_min: 6345
    port_max: 6355

ovs:
  # ovsdb connection, Format supported :
  # * addr:port
  # * tcp://addr:port
  # * unix:///var/run/openvswitch/db.sock
  # If you use the tcp connection you need to authorize connexion to ovsdb agent
  # at least locally
  # % sudo ovs-appctl -t ovsdb-server ovsdb-server/add-remote ptcp:6400:<IP_ADDRESS>
  # ovsdb: unix:///var/run/openvswitch/db.sock
  oflow:
    # Enable the parsing of openflow rules (disabled by default)
    enable: false
    # The probe can connect to remote bridge over TLS (ssl url).
    # The default value is empty for those options.
    # Path to the private key file (TLS connection)
    # key: /etc/ssl/private/agent.key
    # Path to the certificate associated to the key (TLS connection)
    # cert: /etc/ssl/certs/agent.crt
    # Path to certificate authority validating bridge connections (TLS connection)
    # ca: /etc/ssl/certs/ca.crt
    address:
      # Map translating bridge names into URL for remote connection
      # - bridge: ssl:xxx.yyy.zzz.ttt:port
docker:
  # url: unix:///var/run/docker.sock

netns:
  # allow to specify where the netns probe is watching network namespace
  # run_path: /var/run/netns

opencontrail:
  # Host address of the OpenContrail vrouter agent
  # host: localhost
  # TCP port of the OpenContrail vrouter agent
  # port: 8086
  # UDP dest port for MPLS traffic
  # mpls_udp_port: 51234

storage:
  elasticsearch:
    host: <IP_ADDRESS>:9200
    maxconns: 10
    retry: 60
     bulk_maxdocs: 100
    bulk_maxdelay: 5

  # OrientDB connection informations
  # orientdb:
  #  addr: http://<IP_ADDRESS>:2480
  #  database: Skydive
  #  username: root
  #  password: hello

graph:
  # graph backend memory, elasticsearch, orientdb
  backend: elasticsearch

logging:
  level: INFO
  backends:
    - stderr
  # - file
  # - syslog
  # - json
  # configuration of the 'file' backend
  # file:
  #   path: /var/log/skydive.log
  # configuration encoder could be for all backends or for specific one
  # encoder: json

auth:
  # specify the type of authentication mechanism: noauth, basic, keystone (default: noauth)
  # type: basic
  # basic:
    # file: /etc/skydive/htpasswd
  # The 'analyzer_username' and 'analyzer_password' parameters are
  # used by the agent to authenticate against the analyzer
  analyzer_username: admin
  analyzer_password: password

etcd:
  # when 'embedded' is set to true, the analyzer will start an embedded etcd server
  embedded: true
  listen: <IP_ADDRESS>:2379

  # both the analyzers and the agents make use of etcd
  servers:
    - http://<IP_ADDRESS>:2379

  client_timeout: 5

flow:
  # Wihout any new packets, a flow expires after flow.expire
  # seconds
  expire: 600
  # Seconds between flow updates (metrics, enhancements,...)
  update: 60
  # Protocol to use to send flows to the analyzer: websocket or udp
  # protocol: udp

when i run
skydive client inject-packet --type icmp6 --count 1 --dstIP fe80::fc16:3eff:fe01:13b0/64 --dstMAC fe:16:3e:01:13:b0 --srcIP fe80::3c48:79ff:fe7b:5009/64 --srcMAC f0:2f:a7:2d:17:98
it shows:
2017-08-17T15:45:05.459+0800	ERROR	client/packet_injector.go:86 glob..func14	AECA1083-3CC4-E611-B614-F02FA741EF52: Post http://<IP_ADDRESS>:8082/api/injectpacket: EOF

1st/  you need to set the analyzer ip in the configuration file, like :
analyzers:
  - <IP_ADDRESS>:8082

2nd/ if you want to use an external etcd server, you should set embedded to false
etcd:
  embedded: false

as you using the analyzer etcd server, you should
etcd:
embedded: true
listen: <IP_ADDRESS>:2379

analyzer's config file:
# Skydive config file

# host_id is used to reference the agent by default set to hostname
# host_id:

# WebSocket Ping/Pong timeout in second
ws_pong_timeout: 5
# maximum number of topology aggregated messages before sending
# ws_bulk_maxmsgs: 100
# duration in seconds before flushing topology aggregated messages
# ws_bulk_maxdelay: 2

openstack:
#  auth_url: http://xxx.xxx.xxx.xxx:5000/v2.0
# auth_url:http://<IP_ADDRESS>/dashboard/auth/login/
# username: admin
#  password: 79da84d0ab01481f
#  tenant_name: admin
#  region_name: RegionOne
  # The endpoint_type value must be 'public', 'internal' or 'admin'
#  endpoint_type: public
  # When using Keystone V3, domain_name needs to be specified
  # domain_name: MyDomain

analyzer:
  # address and port for the analyzer API, Format: addr:port.
  # Default addr is <IP_ADDRESS>
  listen: <IP_ADDRESS>:8082
  # File path to X509 Certificate and Private Key to enable TLS communication
  # Must be different than the agent
  # X509_cert: /etc/ssl/certs/analyzer.domain.com.crt
  # X509_key:  /etc/ssl/certs/analyzer.domain.com.key

  # Flow storage engine
 # storage:
      # Available: elasticsearch, orientdb
     # backend: elasticsearch
      # maximum number of flows aggregated between two data store inserts
     # bulk_insert: 100
      # deadline of each bulk insert in second
     # bulk_insert_deadline: 5
  topology:
    # Define static interfaces and links updating Skydive topology
    # Can be useful to define external resources like : TOR, Router, etc.
    #
    # A description language similar to the dot language is used to define
    # interfaces and links. An arrow (->) is used to define a link between
    # two interfaces (parent -> child).
    # Square brackets after the arrow is used to define additional metadata
    # of the link (->[key=value,..]). Each interface described will be
    # created in the topology excepted interfaces with the local prefix.
    # In that specific case the interface of the local host will be used.
    # Attributes of interfaces are declared using square brackets ([]).
    # The following example creates a TOR1 node linked to a TOR1_PORT1 which is
    # linked to the local interface eth0.
    fabric:
       - TOR1[Name=tor1] -> [color=red] TOR1_PORT1[Name=port1, MTU=1500]
       - TOR1_PORT1 -> *[Type=host]/eth0
  # update rate of links in seconds
  bandwidth_update_rate: 5
  # interface metrics - 'netlink'
  # captured flows TxBytes + RxByte - 'flows' (need to turn on capture)
  bandwidth_source: netlink
  # 'absolute' - thresholds in Kbit
  # 'relative' - thresholds in % relative to link speed reported by netlink
  bandwidth_threshold: absolute
  bandwidth_absolute_active: 1
  bandwidth_absolute_warning: 10
  bandwidth_absolute_alert: 100
  bandwidth_relative_active: 0.1
  bandwidth_relative_warning: 0.4
  bandwidth_relative_alert: 0.8

# list of analyzers used by analyzers and agents
analyzers:
  - <IP_ADDRESS>:8082

agent:
  # address and port for the agent API, Format: addr:port.
  # Default addr is <IP_ADDRESS>
  listen: :8081
  # File path to X509 Certificate and Private Key to enable TLS communication
  # Must be different than the analyzer and unique per agent (recommended)
  # X509_cert: /etc/ssl/certs/agent.domain.com.crt
  # X509_key:  /etc/ssl/certs/agent.domain.com.key
  # Server name field specified in TLS communications.
  # Not required, but can be used to allow virtual hosting
  # X509_servername: domain.com
  #
  topology:
    # Probes used to capture topology informations like interfaces,
    # bridges, namespaces, etc...
    # Available: ovsdb, docker, neutron, opencontrail
    probes:
      - ovsdb
      - netlink
      - netns
      # - docker
      # - neutron
      # - opencontrail
    netlink:
      # delay in seconds between two metric updates
      # metrics_update: 30
  flow:
    # Period in second to get capture stats from the probe. Note this
    # currently only works for the pcap probe
    # stats_update: 1
      - gopacket
      - pcapsocket
  metadata:
    info: This is compute node

sflow:
  # Default listening address is <IP_ADDRESS>
    bind_address: <IP_ADDRESS>

  # Port min/max used when starting a sflow probe, a agent will be started
  # with a port from this range
    port_min: 6345
    port_max: 6355

ovs:
  # ovsdb connection, Format supported :
  # * addr:port
  # * tcp://addr:port
  # * unix:///var/run/openvswitch/db.sock
  # If you use the tcp connection you need to authorize connexion to ovsdb agent
  # at least locally
  # % sudo ovs-appctl -t ovsdb-server ovsdb-server/add-remote ptcp:6400:<IP_ADDRESS>
  # ovsdb: unix:///var/run/openvswitch/db.sock
  oflow:
    # Enable the parsing of openflow rules (disabled by default)
    enable: false
    # The probe can connect to remote bridge over TLS (ssl url).
    # The default value is empty for those options.
    # Path to the private key file (TLS connection)
    # key: /etc/ssl/private/agent.key
    # Path to the certificate associated to the key (TLS connection)
    # cert: /etc/ssl/certs/agent.crt
    # Path to certificate authority validating bridge connections (TLS connection)
    # ca: /etc/ssl/certs/ca.crt
    address:
      # Map translating bridge names into URL for remote connection
      # - bridge: ssl:xxx.yyy.zzz.ttt:port
docker:
  # url: unix:///var/run/docker.sock

netns:
  # allow to specify where the netns probe is watching network namespace
  # run_path: /var/run/netns

opencontrail:
  # Host address of the OpenContrail vrouter agent
  # host: localhost
  # TCP port of the OpenContrail vrouter agent
  # port: 8086
  # UDP dest port for MPLS traffic
  # mpls_udp_port: 51234

storage:
  elasticsearch:
    host: <IP_ADDRESS>:9200
    maxconns: 10
    retry: 60
    bulk_maxdocs: 100
    bulk_maxdelay: 5

  # OrientDB connection informations
  # orientdb:
  #  addr: http://<IP_ADDRESS>:2480
  #  database: Skydive
  #  username: root
  #  password: hello

graph:
  # graph backend memory, elasticsearch, orientdb
  backend: elasticsearch

logging:
  level: INFO
  backends:
    - stderr
  # - file
  # - syslog
  # - json
  # configuration of the 'file' backend
  # file:
  #   path: /var/log/skydive.log
  # configuration encoder could be for all backends or for specific one
  # encoder: json

auth:
  # specify the type of authentication mechanism: noauth, basic, keystone (default: noauth)
  # type: basic
  # basic:
    # file: /etc/skydive/htpasswd
  # The 'analyzer_username' and 'analyzer_password' parameters are
  # used by the agent to authenticate against the analyzer
  analyzer_username: admin
  analyzer_password: password

etcd:
  # when 'embedded' is set to true, the analyzer will start an embedded etcd server
  embedded: true
  listen: <IP_ADDRESS>:2379

  # both the analyzers and the agents make use of etcd
  servers:
    - http://<IP_ADDRESS>:2379

  client_timeout: 10

flow:
  # Wihout any new packets, a flow expires after flow.expire
  # seconds
  expire: 600
  # Seconds between flow updates (metrics, enhancements,...)
  update: 60
  # Protocol to use to send flows to the analyzer: websocket or udp
  # protocol: udp

agent' config file:
# Skydive config file

# host_id is used to reference the agent by default set to hostname
# host_id:

# WebSocket Ping/Pong timeout in second
ws_pong_timeout: 5
# maximum number of topology aggregated messages before sending
# ws_bulk_maxmsgs: 100
# duration in seconds before flushing topology aggregated messages
# ws_bulk_maxdelay: 2

openstack:
#  auth_url: http://xxx.xxx.xxx.xxx:5000/v2.0
#  auth_url : http://<IP_ADDRESS>/dashboard/auth/login/
#  username: admin
#  password: 79da84d0ab01481f
#  tenant_name: admin
#  region_name: RegionOne
  # The endpoint_type value must be 'public', 'internal' or 'admin'
# endpoint_type: public
  # When using Keystone V3, domain_name needs to be specified
  # domain_name: MyDomain

analyzer:
  # address and port for the analyzer API, Format: addr:port.
  # Default addr is <IP_ADDRESS>
  listen: :8082
  # File path to X509 Certificate and Private Key to enable TLS communication
  # Must be different than the agent
  # X509_cert: /etc/ssl/certs/analyzer.domain.com.crt
  # X509_key:  /etc/ssl/certs/analyzer.domain.com.key

  # Flow storage engine
  storage:
      # Available: elasticsearch, orientdb
      backend: elasticsearch
      # maximum number of flows aggregated between two data store inserts
      bulk_insert: 100
      # deadline of each bulk insert in second
      bulk_insert_deadline: 5
  topology:
    # Define static interfaces and links updating Skydive topology
    # Can be useful to define external resources like : TOR, Router, etc.
    #
    # A description language similar to the dot language is used to define
    # interfaces and links. An arrow (->) is used to define a link between
    # two interfaces (parent -> child).
    # Square brackets after the arrow is used to define additional metadata
    # of the link (->[key=value,..]). Each interface described will be
    # created in the topology excepted interfaces with the local prefix.
    # In that specific case the interface of the local host will be used.
    # Attributes of interfaces are declared using square brackets ([]).
    # The following example creates a TOR1 node linked to a TOR1_PORT1 which is
    # linked to the local interface eth0.
    fabric:
       - TOR1[Name=tor1] -> [color=red] TOR1_PORT1[Name=port1, MTU=1500]
       - TOR1_PORT1 -> *[Type=host]/eth0
  # update rate of links in seconds
  bandwidth_update_rate: 5
  # interface metrics - 'netlink'
  # captured flows TxBytes + RxByte - 'flows' (need to turn on capture)
  bandwidth_source: netlink
  # 'absolute' - thresholds in Kbit
  # 'relative' - thresholds in % relative to link speed reported by netlink
  bandwidth_threshold: absolute
  bandwidth_absolute_active: 1
  bandwidth_absolute_warning: 10
  bandwidth_absolute_alert: 100
  bandwidth_relative_active: 0.1
  bandwidth_relative_warning: 0.4
  bandwidth_relative_alert: 0.8

# list of analyzers used by analyzers and agents
analyzers:
  - <IP_ADDRESS>:8082

agent:
  # address and port for the agent API, Format: addr:port.
  # Default addr is <IP_ADDRESS>
  listen: <IP_ADDRESS>:8081
  # File path to X509 Certificate and Private Key to enable TLS communication
  # Must be different than the analyzer and unique per agent (recommended)
  # X509_cert: /etc/ssl/certs/agent.domain.com.crt
  # X509_key:  /etc/ssl/certs/agent.domain.com.key
  # Server name field specified in TLS communications.
  # Not required, but can be used to allow virtual hosting
  # X509_servername: domain.com
  #
  topology:
    # Probes used to capture topology informations like interfaces,
    # bridges, namespaces, etc...
    # Available: ovsdb, docker, neutron, opencontrail
    probes:
      - ovsdb
      # - docker
      # - neutron
      # - opencontrail
    netlink:
      # delay in seconds between two metric updates
      # metrics_update: 30
  flow:
    # Period in second to get capture stats from the probe. Note this
    # currently only works for the pcap probe
    # stats_update: 1
  metadata:
    info: This is compute node

sflow:
  # Default listening address is <IP_ADDRESS>
  bind_address: <IP_ADDRESS>

  # Port min/max used when starting a sflow probe, a agent will be started
  # with a port from this range
  port_min: 6345
  port_max: 6355

ovs:
  # ovsdb connection, Format supported :
  # * addr:port
  # * tcp://addr:port
  # * unix:///var/run/openvswitch/db.sock
  # If you use the tcp connection you need to authorize connexion to ovsdb agent
  # at least locally
  # % sudo ovs-appctl -t ovsdb-server ovsdb-server/add-remote ptcp:6400:<IP_ADDRESS>
  # ovsdb: unix:///var/run/openvswitch/db.sock
  oflow:
    # Enable the parsing of openflow rules (disabled by default)
    enable: false
    # The probe can connect to remote bridge over TLS (ssl url).
    # The default value is empty for those options.
    # Path to the private key file (TLS connection)
    # key: /etc/ssl/private/agent.key
    # Path to the certificate associated to the key (TLS connection)
    # cert: /etc/ssl/certs/agent.crt
    # Path to certificate authority validating bridge connections (TLS connection)
    # ca: /etc/ssl/certs/ca.crt
    address:
      # Map translating bridge names into URL for remote connection
      # - bridge: ssl:xxx.yyy.zzz.ttt:port
docker:
  # url: unix:///var/run/docker.sock

netns:
  # allow to specify where the netns probe is watching network namespace
  # run_path: /var/run/netns

opencontrail:
  # Host address of the OpenContrail vrouter agent
  # host: localhost
  # TCP port of the OpenContrail vrouter agent
  # port: 8086
  # UDP dest port for MPLS traffic
  # mpls_udp_port: 51234

storage:
  elasticsearch:
    host: <IP_ADDRESS>:9200
    maxconns: 10
    retry: 60
    bulk_maxdocs: 100
    bulk_maxdelay: 5

  # OrientDB connection informations
  # orientdb:
  #  addr: http://<IP_ADDRESS>:2480
  #  database: Skydive
  #  username: root
  #  password: hello

graph:
  # graph backend memory, elasticsearch, orientdb
  backend: memory

logging:
  level: INFO
  backends:
    - stderr
  # - file
  # - syslog
  # - json
  # configuration of the 'file' backend
  # file:
  #   path: /var/log/skydive.log
  # configuration encoder could be for all backends or for specific one
  # encoder: json

auth:
  # specify the type of authentication mechanism: noauth, basic, keystone (default: noauth)
  # type: basic
  # basic:
    # file: /etc/skydive/htpasswd
  # The 'analyzer_username' and 'analyzer_password' parameters are
  # used by the agent to authenticate against the analyzer
  analyzer_username: admin
  analyzer_password: password

etcd:
  # when 'embedded' is set to true, the analyzer will start an embedded etcd server
   embedded: true

   listen: <IP_ADDRESS>:2379

  # both the analyzers and the agents make use of etcd
   servers:
     - http://<IP_ADDRESS>:2379

   client_timeout: 5

flow:
  # Wihout any new packets, a flow expires after flow.expire
  # seconds
  expire: 600
  # Seconds between flow updates (metrics, enhancements,...)
  update: 60
  # Protocol to use to send flows to the analyzer: websocket or udp
 #  protocol: udp

source node is mandatory param. added a proper check and error message.
https://github.com/skydive-project/skydive/pull/395


Display a License tab

Like GitHub does. It shows a tab with the project license, so it's immediate to see what it is

I don't understand what you want to request, please explain it properly.

Maybe he speak about this:

Ah, that makes more sense.

But for a self-hosted server, I seems there is no requirement.

we are no forced to do something like github who scan repo to determine licence. maybe juste a selectbox field on repo settings page is enough ?

This is something we can integrate at some point, so I moved it to a future milestone

Using something like go-license[1] it'd be fairly simple to implement, just remember to cache the result until the license-file changes (just add another column in the repo-table)
[1] https://github.com/ryanuber/go-license

Yeah could add a new field on repo model and update it at each push / merge event if file LICENSE or LICENSE.* is updated

@0xbaadf00d preferably only update when LICENSE* have been updated ;)

@bkcsoft that may not be always he case... some projects use COPYING for instance

LICENSE files my also not necessarily contain a single license, but a list of licenses for various components

@bamboleeeero-bamboleeeero

some projects use COPYING for instance

How does GitHub handle this?

but a list of licenses for various components

Same here. How does others handle that?
As I see it, it's a new feature, do the smallest amount of work first then extend on that in a later version :)

Github handles this through the gem licensee.

some projects use COPYING for instance

Github scans the root of a project, and matches the files in that directory against a series of regular expressions with scores. High enough and it's treated as a file that likely contains the license text.

but a list of licenses for various components

The first license that Licensee detects and knows about is used. A better solution is being discussed at https://github.com/benbalter/licensee/issues/57

I can agree to @bamboleeeero-bamboleeeero - the filename is not always LICENSE. E.g. LICENSE.txt, LICENSE.md, COPYING are often used too

activity!

ref. https://github.com/src-d/go-license-detector

@lunny Any plans to implement this? The library looks promising.

Library moved to https://github.com/go-enry/go-license-detector

I would love to see this suggestion implemented. Even if it is a self-hosted version, I offered access to several people on it and it would be useful to have a license tab.

I would love to see this suggestion implemented. Even if it is a self-hosted version, I offered access to several people on it and it would be useful to have a license tab.

May I suggest to also support the more flexible REUSE standard when implementing this important feature?
License detection would become really easy, especially if multiple licenses are in use. All you have to do is fetching the file names from the LICENSES directory. For instance, check this.
The files names (without .txt) indicate the unique SPDX license identifiers, and save everyone from interpreting the often diverging text in files like LICENSE or COPYING.

google did start developing a licence detector: https://github.com/google/licensecheck

Would be very helpful indeed to have a license tab


✨ Gitlab: Contributors check

What kind of change does this PR introduce?
Adds GitLab support for the Contributors check
What is the new behavior (if this is a feature change)?**
Contributors in GitLab are now detected by Scorecard. This check is still slow because of the number of API calls per contributor (1 search + 1 lookup  = 2 api calls / contributor)

[x] Tests for the changes have been added (for bug fixes/features)

GitLab support for Contributors check

@naveensrinivasan I believe those will be covered by E2E tests that can only run on main.


fix CI failure and warnings running on JRuby 9.2

Travis was configured to use the --client flag, which is deprecated.
For some reason, the script to resolve the rake path was not working, but found a simpler way.


Show a maximum of 10 modules in the stats output by default

Do you want to request a feature or report a bug?
feature
What is the current behavior?
many modules are shown, node_modules are excluded by default
big code bases result in many output lines
If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?
only the first 10 modules (meassured by distance to entry point) should be shown by default
If this is a feature request, what is motivation or use case for changing the behavior?
less output

Could this be a configurable option in our webpack config?

Sure, everything is configurable...


update make-config to add autoscaler info per env

Part of this ticket
Prod environments are likely to have different autoscaling requirements. This PR, therefore, updates the make-config command to allow adding separate scaling info via the bootstrap.yml file.

Updates environment schema based on copilot autoscaler docs
adds a to_yaml filter to web manifest jinja template
bumps package
updates make-config test with new prod example

Looks good, though can we update the migration-tools/build-copilot-config.py app to include the count in the bootstrap configs it generates even if it just defaults to 1.
I wonder if the cloudfoundry client supports getting scaling info from app instances?

I think we already have a default now:
count: # See https://aws.github.io/copilot-cli/docs/manifest/lb-web-service/#count
  range: 2-10
  cooldown:
    in: 120s
    out: 60s
  cpu_percentage: 50

(At least that's what the make-config command produced for me when I ran it most recently. I think that's preferable to setting the same thing for each environment)
I could create a separate ticket to investigate finding values from cloudfoundry and adding to the bootstrap file?

Looks good, though can we update the migration-tools/build-copilot-config.py app to include the count in the bootstrap configs it generates even if it just defaults to 1.
I wonder if the cloudfoundry client supports getting scaling info from app instances?

I think we already have a default now:
count: # See https://aws.github.io/copilot-cli/docs/manifest/lb-web-service/#count
  range: 2-10
  cooldown:
    in: 120s
    out: 60s
  cpu_percentage: 50

(At least that's what the make-config command produced for me when I ran it most recently. I think that's preferable to setting the same thing for each environment)
I could create a separate ticket to investigate finding values from cloudfoundry and adding to the bootstrap file?

The make-config file relies on the bootstrap.yml file if I am not mistaken, so we most definitely need to at least pull in these values for the production environment from the Cloud Foundry client, if possible.

Looks good, though can we update the migration-tools/build-copilot-config.py app to include the count in the bootstrap configs it generates even if it just defaults to 1.
I wonder if the cloudfoundry client supports getting scaling info from app instances?

I think we already have a default now:
count: # See https://aws.github.io/copilot-cli/docs/manifest/lb-web-service/#count
  range: 2-10
  cooldown:
    in: 120s
    out: 60s
  cpu_percentage: 50

(At least that's what the make-config command produced for me when I ran it most recently. I think that's preferable to setting the same thing for each environment)
I could create a separate ticket to investigate finding values from cloudfoundry and adding to the bootstrap file?

The make-config file relies on the bootstrap.yml file if I am not mistaken, so we most definitely need to at least pull in these values for the production environment from the Cloud Foundry client, if possible.

I was thinking that people will have to at least cast their eye over bootstrap.yml before running that command and so could add any custom autoscaler config at that point, using the default already generated by make-config, as a fallback. Agree that ideally we'd pull in from cloudfoundry, but don't think it's a blocker.

Looks good, though can we update the migration-tools/build-copilot-config.py app to include the count in the bootstrap configs it generates even if it just defaults to 1.
I wonder if the cloudfoundry client supports getting scaling info from app instances?

I can get the below by running cf app APP_NAME:

So I think it should be possible to get similar using the python client too.


Mongoid support

Hello,
I needed basic mongoid support on this gem, I can confirm this works using DelayedJob, I don't have time to test the rest though.
Have a nice day

As the direction is to support only ActiveJob, I think this can be closed - follow discussion on #173


change colors

Hi - I've been trying to change colors - I want to use #1c2c2c or #212121 as background color but no matter what i do nothing changes. All my programs and terminals are either ¤1c1c1c or #212121 so for the consistent look 'i 'd like this to follow the same colors.  Any idea how I can achieve this?
edit:
Also want to thank you for this- I've used nighttab for over a year now - but this is just amazing so if I can change it so it fits with my other colors this will be my new go to.
edit 2
I tried to change sidebar bg color to 1c1c1c but after the restart, it showed the same color - no change
including a pic so you see what
i  mean
https://imgur.com/a/Nu3Oo43

Have you tried firefox color yet? That was my primary means of changing color schemes and it should work, at least for everything except sidebar.
In case it isn't able to change sidebar color, adding this CSS to TST should work:
:root, #background{
    background:  #212121;
}

Have you tried firefox color yet? That was my primary means of changing color schemes and it should work, at least for everything except sidebar.
In case it isn't able to change sidebar color, adding this CSS to TST should work:
:root, #background{
    background:  #212121;
}

Yeah ff color wors fine but rhe sidebar wouldnt change. Will try rhe solution you posted when i get home. Thx in advance

Yeah ff color wors fine but rhe sidebar wouldnt change. Will try rhe solution you posted when i get home. Thx in advance

Worked perfectly - thank you

Worked perfectly - thank you


Vectorized a bunch of the discrete rngs

Submission Checklist

[x] Run unit tests: ./runTests.py test/unit
[x] Run cpplint: make cpplint
[x] Declare copyright holder and open-source license: see below

Summary:
Vectorized a bunch of the discrete random number generators
As far as vectorizing all the rngs goes, this skips all the distributions that don't have vectorized pmfs/pdfs or don't have rngs. There are a few distributions where only the interface is being tested in the vectorized tests (no distributions). This includes von_mises, pareto type 2, and exp_mod_normal.
Intended Effect:
Same as above
How to Verify:
./runTests.py test/unit/math/prim/mat/prob
./runTests.py test/unit/math/prim/scal/prob

Side Effects:
Hopefully none!
Documentation:
In the doxygen
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company): University of California, Santa Barbara
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses:

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

@bbbales2, this is great.  Can't wait for it to be merged.  When it is, I'll expose these on the Stan side.

I had a look at the multivariate stuff. The only three distributions that actually had vectorized lpdfs were multi_normal, multi_normal_cholesky, and multi_student_t, so I just manually built tests for those.
Had to add a few new metaprograms to make this work: StdVectorBuilder, contains_std_vector, and is_std_vector. The difference from VectorBuilder, contains_vector, and is_vector is that the only thing StdVectorBuilder respects as a vectorized type are actual std::vectors. Dunno if there is a better way of doing this.
I also added some rudimentary distribution tests to von_mises, pareto type 2, and exp_mod_normal (which didn't previously have tests).
At this point this pull req. should have all the stuff for https://github.com/stan-dev/math/issues/45 . Any missing tests/vectorizations are a bug.

This is fantastic.  Let me know when it's ready to review.

Great.  I'm going to wait until the Jenkins issues get ironed out.  We just rebooted the server.  So I'll try retesting.
Jenkins, retest this, please.

@mitzimorris has kindly agreed to review this pull req.
Here's the User's Guide to the pull:
The bulk of this is implementation and testing of vectorized integer rngs, but there are also a few multivariate distributions and updates to the continuous ones.
A prototypical continuous univariate rng is the normal distribution
Implementation: https://github.com/stan-dev/math/blob/develop/stan/math/prim/scal/prob/normal_rng.hpp
Tests: https://github.com/bbbales2/math/blob/0c9ef5559181a7598bd199f50446c48778824e9e/test/unit/math/prim/mat/prob/normal_test.cpp
A prototypical discrete univariate rng is the poisson distribution
Implementation: https://github.com/bbbales2/math/blob/0c9ef5559181a7598bd199f50446c48778824e9e/stan/math/prim/scal/prob/poisson_rng.hpp
Tests: https://github.com/bbbales2/math/blob/0c9ef5559181a7598bd199f50446c48778824e9e/test/unit/math/prim/mat/prob/poisson_test.cpp
A prototypical multivariate distribution is multi_normal_cholesky:
Implementation: https://github.com/bbbales2/math/blob/0c9ef5559181a7598bd199f50446c48778824e9e/stan/math/prim/mat/prob/multi_normal_cholesky_rng.hpp
Tests: https://github.com/bbbales2/math/blob/0c9ef5559181a7598bd199f50446c48778824e9e/test/unit/math/prim/mat/prob/multi_normal_cholesky_test.cpp
Implementation of the different _rng interfaces is simplified through the use of:
scalar_seq_view, vector_seq_view, VectorBuilder, and StdVectorBuilder. StdVectorBuilder is new to this pull req. and is used by the multivariate rngs to construct the correct output (https://github.com/bbbales2/math/blob/0c9ef5559181a7598bd199f50446c48778824e9e/stan/math/prim/scal/meta/StdVectorBuilder.hpp). There are two additional metaprograms, contains_std_vector and is_std_vector which are new. They're modeled after contains_vector and is_vector.
Testing for the univariate rngs works by building test rigs and then feeding them to two of three types of test functions which all live in https://github.com/bbbales2/math/blob/0c9ef5559181a7598bd199f50446c48778824e9e/test/unit/math/prim/mat/prob/vector_rng_test_helper.hpp:
check_dist_throws_* - which tests the interface works and the code throws errors in the expected places
check_quantiles_* - which tests that continuous rngs are sampling from the expected distributions
check_counts_* - which tests that discrete rngs are sampling from the expeced dists.
Each rng makes a test rig that inherits from either https://github.com/bbbales2/math/blob/0c9ef5559181a7598bd199f50446c48778824e9e/test/unit/math/prim/mat/prob/VectorRealRNGTestRig.hpp (for reals) or https://github.com/bbbales2/math/blob/0c9ef5559181a7598bd199f50446c48778824e9e/test/unit/math/prim/mat/prob/VectorIntRNGTestRig.hpp forints. They inherit from https://github.com/bbbales2/math/blob/0c9ef5559181a7598bd199f50446c48778824e9e/test/unit/math/prim/mat/prob/VectorRNGTestRig.hpp.

Following up to @mitzimorris
I hunted down the finicky quantile (https://github.com/stan-dev/math/pull/622#issuecomment-334510950). I think it's just that, and so I reported a bug to Boost https://svn.boost.org/trac10/ticket/13620.

Phew lol, finally got this to pass, after updating a comment. @mitzimorris want to merge?

merged!

Awesome.  I'd like to get to the Stan side of this by the end of this week.  Thanks to you both.

Cool! Just pm'ed you on Discourse to ask if you were still up for it haha. Thanks for looking at this!


Is osx (yosemite) able to change device name?

Docs seem to say you can, but have to
sudo BLENO_DEVICE_NAME="Battery" node examples/battery-service/main.js

But that doesn't appear to work for me.

@jacobrosenthal that's in the Linux only section right? Do you see it elsewhere?
https://github.com/sandeepmistry/bleno#running-on-linux

True enough
On Tue, Sep 29, 2015 at 2:19 AM, Sandeep Mistry<EMAIL_ADDRESS>wrote:

@jacobrosenthal https://github.com/jacobrosenthal that's in the Linux
only section right? Do you see it elsewhere?
https://github.com/sandeepmistry/bleno#running-on-linux
—
Reply to this email directly or view it on GitHub
https://github.com/sandeepmistry/bleno/issues/132#issuecomment-143909153
.

You might be able to change it non-programmatically via: OS X Settings -> Sharing -> Computer Name


Add version: ByteDance.Feishu version 32

Pull request has been created with WinGet Automation 🪟📦🤖
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installer Verification Analysis Context Information:
Error occurred while downloading installer from https://sf3-cn.feishucdn.com/obj/ee-appcenter/47273f95/Feishu-win32_ia32-7.9.7-signed.exe. 0x8A15002E.
Error information:
Http Response: OK
Http Reason Phrase: OK

(Automated response - build 575.)

URL:
Status Code: 200
(Automated message - build 575)

/AzurePipelines run


Tab out of editing in the last column causes error without row markers

When editing a cell in the last column of our grid, we get this error:
Uncaught TypeError: Cannot read properties of undefined (reading 'width')
    at minXScrollToCol (data-editor.js?590d:617)
    at eval (data-editor.js?590d:652)
    at eval (data-editor.js?590d:674)
    at eval (data-grid-overlay-editor.js?4992:121)
    at HTMLUnknownElement.callCallback (react-dom.development.js?61bb:3945)
    at Object.invokeGuardedCallbackDev (react-dom.development.js?61bb:3994)
    at invokeGuardedCallback (react-dom.development.js?61bb:4056)
    at invokeGuardedCallbackAndCatchFirstError (react-dom.development.js?61bb:4070)
    at executeDispatch (react-dom.development.js?61bb:8243)
    at processDispatchQueueItemsInOrder (react-dom.development.js?61bb:8275)

Here's a reproduction CodeSandbox. It looks like it only happens when scrolled down at least one row.

Fixed in a branch, should be fixed in the next point release.


cmd/controller: secure using CORS and auth

Auth is provided via a secure cookie that the user is granted upon
successful auth in the PWD world.
Fixes #43

https://github.com/play-with-go/play-with-go/pull/71 was approved which is stacked on top of this PR. So per offline chat, taking this as approved by proxy. Will merge on green build.


remove pyplot example in favour of a pgfplotsx one or something as it seems to break docs

pyplot currently commented in #222 problem disappears so it seems it's indeed the cause.


keycloak-client throws exception from 1.16.1 and up

Hi,
when upgrading to 1.16.1 or higher, instantiating a client results in the following error:
Execution error (NoClassDefFoundError) at keycloak.deployment/keycloak-client (deployment.clj:71).
clojure/tools/logging/impl/LoggerFactory

The code is taken straight from the documentation and works until, including, 1.16.0.
(def kc-client
  (-> (client-conf {:auth-server-url auth-url
                    :realm realm
                    :client-id "admin-cli"})
      (keycloak-client backend-admin-id backend-admin-secret)))

Yes, I changed recently the way the thin jar is built by adding Keycloak-Clojure's AOT classes along clj files without any other dependencies classes.
How do you declare the keycloak-clojure's dependency? with tools.deps? leiningen?

Hi, thanks for the prompt answer.
We use deps.edn with the following declaration: keycloak-clojure/keycloak-clojure {:mvn/version "1.16.4"}
Do you need any extra infos?

Thank you that's enough informations, I'll setup a sample project to reproduce and isolate the error. Maybe I messed up the jar building...

Hi Alexander,
I've released a new 1.16.5 version that should fix the issue. I've messed up the Jar building process with AOT while trying to optimise some loading stuff (long story short: just don't, see https://clojureverse.org/t/deploying-aot-compiled-libraries/2545).

Hi Jérémie,
thanks for your swift work. Everything works as expected again. 👍


Is it possible to have two lines with different horizontal axis values?

I would like to create a line chart with two lines. But the horizontal axis values for each line need to be different. One is a temperature (so could be 0 to 40 degrees), the other one is a chance of rain (so could be 0% to 100%). Is this possible?
Hopefully the question makes sense.

Hey @roly151
If I understand correctly I think easiest way to do this is just to build 2 charts and add them in a Stack.
Currently library is not supporting different X or Y coordinates for different data on same chart.

Thanks - I did consider that. I'll give it a go.


How to get messages/warning/errors in MAVSDK?

Hi,
Is there a way in MAVSDK that can help us in getting the message/warnings/errors about the drone as we get in the QGroundControl/Mission planner?
For Example:
Critical Navigation Failure
Arming Denied
Failsafe enabled
etc.
Some messages can be seen on the attached images of QGC.

Try subscribing to status texts: http://mavsdk-python-docs.s3-website.eu-central-1.amazonaws.com/plugins/telemetry.html?highlight=statustext#mavsdk.telemetry.Telemetry.status_text

Try subscribing to status texts: http://mavsdk-python-docs.s3-website.eu-central-1.amazonaws.com/plugins/telemetry.html?highlight=statustext#mavsdk.telemetry.Telemetry.status_text

This is what I was looking for. It worked.
Thank you.


Issues with Two same instance of login screen in same browser window

Core Library
MSAL.js v2 (@azure/msal-browser)
Core Library Version
2.33.0
Wrapper Library
MSAL Angular (@azure/msal-angular)
Wrapper Library Version
2.5.3
Public or Confidential Client?
Public
Description
We have implemented custom policies with azure adb2c and calling that through a client using MSAL Angular (Latest Version).
Curently using Localstorage to save MSAL Cache and tokens.
The issue we and most of our Customer are facing is they need to do MFA Twice.
We first thought it's an intermittent issue and occur for users logging into system after X no. of days and due to refresh token expiry the system invalidates the login and makes MFA request twice.
But recently we relesed a specific pattern when this issue occurs.
Whenever we start our application due to MSAL Guards it automatically redirect to a long b2c url defined in the cofiguration.
https://.b2clogin.com/.onmicrosoft.com/b2c_1a_mfa_phone_or_email/oauth2/v2.0/authorize?client_id=01c7**&scope=openid%20profile%20offline_access&redirect_uri=http%3A%2F%2Flocalhost%3A4200%2F&client-request-id=f5c7d413-257f-48ac-999c-6e1a213840b3&response_mode=fragment&response_type=code&x-client-SKU=msal.js.browser&x-client-VER=2.33.0&client_info=1&code_challenge=JUGPQlehE-bQxph7q4YnAzEJzs&code_challenge_method=S256&nonce=6b2a8c0f-22d0-483f-9065-6662910&state=eyJpZCI6IjhiZGQwMGI0LTBmMDEtNGQ0Zi05NTg2LTdlMTZlYjBkYTNiNCIsIm1ldGEiOnsiaW50ZXJhY3Rpb25UeXBl
If I open a new tab and hit the base url (localhost in this example) it again redirects to the b2c url but with new values in parameters like state , nounce and code challenge as well as request id.
Now if I switch to the old tab and hit login in the first place it erases the password , If I hit it again it asks me for MFA and redirects back to MFA screen again. After verifying MFA again it lets me inside the system.
Same thing works on newly open login page.
I want to get rid of thsi MFA loop (occuring Twice in my case but users have reported it more as well)
Any help to resolve this is Appreciated.
Thanks in Advance!
Error Message
No Error Mesaage in console
Msal Logs
No response
MSAL Configuration
auth: {
      clientId: clientID,
      authority:authorityURL,
      navigateToLoginRequestUrl:true,
      redirectUri: http://localhost:4200/,
      postLogoutRedirectUri:http://localhost:4200/,
      knownAuthorities: **.b2clogin.com
    },
    cache: {
      cacheLocation: BrowserCacheLocation.LocalStorage,
      storeAuthStateInCookie: isIE // set to true for IE 11
    },
    system: {
      loggerOptions: {
        loggerCallback,
        logLevel: LogLevel.Info,
        piiLoggingEnabled: false
      }
    }

Relevant Code Snippets
NA

Reproduction Steps

Open Two Tabs of Angular App
Try to login with the 1st Tab you used to open the application
Password field goes blank in first attempt
Try to input password again and hit enter
You will be presented with MFA twice

Expected Behavior
User should be able to login in first attempt irrescpective of which tab he choosed
Identity Provider
Azure B2C Custom Policy
Browsers Affected (Select all that apply)
Chrome, Edge
Regression
No response
Source
Internal (Microsoft)

Reproduced the same issue on provided amgular sample :
https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/samples/msal-angular-v2-samples

This looks like a question for the B2C service team please follow the support instructions documented here and they should be able to provide further assistance.


feat(curriculum): add equation solver project to SCWP

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

Reminders:

Add intro.
Flesh out pages.
Verify project order.

Based on the feedback received, I modified the prototype . Here are the main changes:

replaced abstract properties degree and type with class attributes
added __init_subclass__ method (not sure about the implementation)
modified coefficients attribute to keep the same order of args
removed self.coefficients[<n>] references, (coefficients are now unpacked to improve readability)
moved the creation of the strings to print outside the solve and analyze methods.

I'll start to implement these changes here as soon as I get a positive feedback. @ilenia-magoni @zairahira @gikf


Directory option for autofs

In case of multiple auto.* files, it is helpful to keep all files in a directory. I have forked this module to add option for directory in case of mount_files option.
I also need to pass some 'options' in case of mount_files.
My forked version is here
https://github.com/oxford-physics/puppet-autofs
If it is useful for other people then I can send a pull request
Thanks
Kashif

The options part I definitely want, but the directory part I'm not so sure. Your current implementation is out of sync with mount, and all distros except ArchLinux seems to default to /etc folder (ArchLinux use /etc/autofs, also for auto.master).
Implementing this I would probably expose it as an option to init.pp as well - and default to a distro specific folder (/etc/autofs on ArchLinux, /etc on everything else) in params. Then use the same default value within the mountfile define.
The current implementation doesn't account for ArchLinux having implemented the /etc/autofs directory, so a directory option should get added to consider this fact anyhow

Hi
I agree that directory part may not be useful for everyone and it will  clutter the code. It is in our setup because of some historical reason. You  can close this issue.


Failed to create image if the disk has the same name with a vm

Environment summary
Ubuntu 16.04LTS
Install Method (e.g. pip, interactive script, apt-get, Docker, MSI, edge build) / CLI version (az --version) / OS version / Shell Type (e.g. bash, cmd.exe, Bash on Windows)
pip install azure-cli

I want to create an image use Azure-CLI from a given disk, but a vm in the same group has the same name with disk. Then Azure-CLI will failed to create image from disk but from vm.
details:
My resource group myrg has the following resources:

/disks/testvm001
/virtualmachine/testvm001
/disks/disk001

I now want to create an image with osDisk is /disks/testvm001, and dataDisks contains /disks/disk001.
So I use the following command:
az image create --source /subscriptions/XXXX/resourceGroups/myrg/providers/Microsoft.Compute/disks/testvm001 --data-disk-sources disk001--os-type Linux -g myrg -n testimage001

However, when it executes these lines: vm/_validators.py#992
It only checks whether there is a vm with such name, then creates image from this vm, but not from disk as I want.
BTW, it finally failed since this code thinks I define a vm as source and also define the data-disk.

Thanks for reporting this.


[Q] Release Schedule

Quick question: Do you have a set release schedule? I'm just wondering when we can expect a new stable release. There are some changes in the current master that I'd very much like to get to our production environment.

There is no release date yet.
I want to add a couple of feature, fix all remaining bugs and test again.

I released the version 1.0.12 today.

:+1:  :+1:

:+1:


export <Link /> from theme docs

fixes https://github.com/shuding/nextra/issues/1693

Thanks @B2o5T 👏 really appreciate this!


Provide support of additional tags in all the aws resources specifically on eks nodes

Changes  done in the module - Provide additional tags support in all the resources in the terraform-aws-eks module.
Made changes in the main.tf of calling module and add the two cost related tags in the additional_aws_tags .
Made changes in the main.tf of modules managed_node_group in launch_template resource to support additional tags in eks nodes.

Functionality has been tested.


[FEATURE] Document enviroment variables set by npx and npm exec

What / Why
npx sets many enviroment variables.
It can be seen by running command:
meld <(npx -c 'env | sort') <(env | sort) <(npm exec -c 'env | sort')

How
Current Behavior
There is no documentation on this.
Expected Behavior
It should be documented.
Who

n/a

References

n/a

The things we export that users can rely on are documented here https://docs.npmjs.com/cli/v7/using-npm/scripts#environment
Some other things are set, but not documented because they are not something we want to support and may be changed.
If there are things exported that you feel belong on the list in the existing docs, please specify them explicitly so we can discuss if it is an actual oversight, or if it is intended to be undocumented.

Some other things are set, but not documented because they are not something we want to support and may be changed.

Understandable, closing issue.