history changes

There's no LA in the index.html file - please add it (as a  block)

Closing pull request because the commits were squashed. A new pull request will be pushed.


3D classification tutorial Early stopping

Describe the bug
The training for the tutorial 3D classification terminates after 5 epochs. Pytorch ignite EarlyStopping handler is used to stop training. This occurs for both the files for training_dict and training_array.
  logs
./3d_classification/ignite/densenet_training_dict.py
MONAI version: 0.8.1
Numpy version: 1.22.3
Pytorch version: 1.11.0+cu102
MONAI flags: HAS_EXT = False, USE_COMPILED = False
MONAI rev id: 71ff399a3ea07aef667b23653620a290364095b1
Optional dependencies:
Pytorch Ignite version: 0.4.8
Nibabel version: 3.2.2
scikit-image version: 0.19.2
Pillow version: 9.1.0
Tensorboard version: 2.8.0
gdown version: 4.4.0
TorchVision version: 0.12.0+cu102
tqdm version: 4.64.0
lmdb version: 1.3.0
psutil version: 5.9.0
pandas version: 1.4.2
einops version: 0.4.1
transformers version: 4.18.0
mlflow version: 1.25.1
For details about installing the optional dependencies, please visit:
https://docs.monai.io/en/latest/installation.html#installing-the-recommended-dependencies
torch.Size([2, 1, 96, 96, 96]) tensor([0, 0])
INFO:ignite.engine.engine.Engine:Engine run starting with max_epochs=30.
INFO:trainer:Epoch: 1/30, Iter: 1/5 -- Loss: 0.8398
INFO:trainer:Epoch: 1/30, Iter: 2/5 -- Loss: 0.7421
INFO:trainer:Epoch: 1/30, Iter: 3/5 -- Loss: 0.6903
INFO:trainer:Epoch: 1/30, Iter: 4/5 -- Loss: 0.6971
INFO:trainer:Epoch: 1/30, Iter: 5/5 -- Loss: 0.8217
INFO:ignite.engine.engine.Engine:Engine run starting with max_epochs=1.
INFO:evaluator:Epoch[1] Metrics -- AUC: 0.7500
INFO:ignite.engine.engine.Engine:Epoch[1] Complete. Time taken: 00:00:05
INFO:ignite.engine.engine.Engine:Engine run complete. Time taken: 00:00:05
INFO:ignite.engine.engine.Engine:Epoch[1] Complete. Time taken: 00:00:23
INFO:trainer:Epoch: 2/30, Iter: 1/5 -- Loss: 0.7278
INFO:trainer:Epoch: 2/30, Iter: 2/5 -- Loss: 0.8066
INFO:trainer:Epoch: 2/30, Iter: 3/5 -- Loss: 0.7281
INFO:trainer:Epoch: 2/30, Iter: 4/5 -- Loss: 0.7249
INFO:trainer:Epoch: 2/30, Iter: 5/5 -- Loss: 0.6370
INFO:ignite.engine.engine.Engine:Engine run starting with max_epochs=1.
INFO:evaluator:Epoch[2] Metrics -- AUC: 0.7500
INFO:ignite.engine.engine.Engine:Epoch[1] Complete. Time taken: 00:00:05
INFO:ignite.engine.engine.Engine:Engine run complete. Time taken: 00:00:06
INFO:ignite.engine.engine.Engine:Epoch[2] Complete. Time taken: 00:00:22
INFO:trainer:Epoch: 3/30, Iter: 1/5 -- Loss: 0.7986
INFO:trainer:Epoch: 3/30, Iter: 2/5 -- Loss: 0.7600
INFO:trainer:Epoch: 3/30, Iter: 3/5 -- Loss: 0.5949
INFO:trainer:Epoch: 3/30, Iter: 4/5 -- Loss: 0.7725
INFO:trainer:Epoch: 3/30, Iter: 5/5 -- Loss: 0.6432
INFO:ignite.engine.engine.Engine:Engine run starting with max_epochs=1.
INFO:evaluator:Epoch[3] Metrics -- AUC: 0.7083
INFO:ignite.engine.engine.Engine:Epoch[1] Complete. Time taken: 00:00:05
INFO:ignite.engine.engine.Engine:Engine run complete. Time taken: 00:00:06
INFO:ignite.engine.engine.Engine:Epoch[3] Complete. Time taken: 00:00:23
INFO:trainer:Epoch: 4/30, Iter: 1/5 -- Loss: 0.7858
INFO:trainer:Epoch: 4/30, Iter: 2/5 -- Loss: 0.7818
INFO:trainer:Epoch: 4/30, Iter: 3/5 -- Loss: 0.6025
INFO:trainer:Epoch: 4/30, Iter: 4/5 -- Loss: 0.5577
INFO:trainer:Epoch: 4/30, Iter: 5/5 -- Loss: 0.7618
INFO:ignite.engine.engine.Engine:Engine run starting with max_epochs=1.
INFO:evaluator:Epoch[4] Metrics -- AUC: 0.6667
INFO:ignite.engine.engine.Engine:Epoch[1] Complete. Time taken: 00:00:06
INFO:ignite.engine.engine.Engine:Engine run complete. Time taken: 00:00:06
INFO:ignite.engine.engine.Engine:Epoch[4] Complete. Time taken: 00:00:23
INFO:trainer:Epoch: 5/30, Iter: 1/5 -- Loss: 0.7667
INFO:trainer:Epoch: 5/30, Iter: 2/5 -- Loss: 0.7293
INFO:trainer:Epoch: 5/30, Iter: 3/5 -- Loss: 0.5294
INFO:trainer:Epoch: 5/30, Iter: 4/5 -- Loss: 0.7414
INFO:trainer:Epoch: 5/30, Iter: 5/5 -- Loss: 0.5467
INFO:ignite.engine.engine.Engine:Engine run starting with max_epochs=1.
INFO:evaluator:Epoch[5] Metrics -- AUC: 0.7500
2022-04-21 00:17:29,358 ignite.handlers.early_stopping.EarlyStopping INFO: EarlyStopping: Stop training
INFO:ignite.engine.engine.Engine:Terminate signaled. Engine will stop after current iteration is finished.
INFO:ignite.engine.engine.Engine:Epoch[1] Complete. Time taken: 00:00:05
INFO:ignite.engine.engine.Engine:Engine run complete. Time taken: 00:00:06
INFO:ignite.engine.engine.Engine:Epoch[5] Complete. Time taken: 00:00:22
INFO:ignite.engine.engine.Engine:Engine run complete. Time taken: 00:01:53
State:
iteration: 25
epoch: 5
epoch_length: 5
max_epochs: 30
output: 0.5467474460601807
batch: <class 'dict'>
metrics: <class 'dict'>
dataloader: <class 'torch.utils.data.dataloader.DataLoader'>
seed: <class 'NoneType'>
times: <class 'dict'>
examples 3d classification ignite: model file not generated
Running ./3d_classification/ignite/densenet_evaluation_dict.py
MONAI version: 0.8.1
Numpy version: 1.22.3
Pytorch version: 1.11.0+cu102
MONAI flags: HAS_EXT = False, USE_COMPILED = False
MONAI rev id: 71ff399a3ea07aef667b23653620a290364095b1
Optional dependencies:
Pytorch Ignite version: 0.4.8
Nibabel version: 3.2.2
scikit-image version: 0.19.2
Pillow version: 9.1.0
Tensorboard version: 2.8.0
gdown version: 4.4.0
TorchVision version: 0.12.0+cu102
tqdm version: 4.64.0
lmdb version: 1.3.0
psutil version: 5.9.0
pandas version: 1.4.2
einops version: 0.4.1
transformers version: 4.18.0
mlflow version: 1.25.1
For details about installing the optional dependencies, please visit:
https://docs.monai.io/en/latest/installation.html#installing-the-recommended-dependencies
INFO:ignite.engine.engine.Engine:Engine run starting with max_epochs=1.
INFO:ignite.engine.engine.Engine:Restored all variables from ./runs_dict/net_checkpoint_20.pt
INFO:evaluator:Epoch[1] Metrics -- Accuracy: 0.4000
INFO:ignite.engine.engine.Engine:Epoch[1] Complete. Time taken: 00:00:05
INFO:ignite.engine.engine.Engine:Engine run complete. Time taken: 00:00:06
State:
iteration: 5
epoch: 1
epoch_length: 5
max_epochs: 1
output: <class 'tuple'>
batch: <class 'dict'>
metrics: <class 'dict'>
dataloader: <class 'torch.utils.data.dataloader.DataLoader'>
seed: <class 'NoneType'>
times: <class 'dict'>

Environment (please complete the following information):

Python version: 3.8.10
MONAI version:0.8.1

Hi @addcue ,
I think this is expected behavior to show the usage of EarlyStopping handler.
Or maybe I misunderstood your question?
Thanks.

Hi,
is there a tutorial for using the classification in its entirely without the early stopping?

Hi @addcue ,
If you don't want to apply the Early-Stop, maybe you can remove these 2 lines and run again:
https://github.com/Project-MONAI/tutorials/blob/master/3d_classification/ignite/densenet_training_dict.py#L151-L152
Thanks.

Thanks! That helped fix it for the training_dict file, but in the training_array walkthrough the model is not improving. The AUC is stuck at 0.6. Do you know why that’s happening?
From: Nic Ma @.>
Reply-To: Project-MONAI/tutorials @.>
Date: Thursday, April 21, 2022 at 9:48 AM
To: Project-MONAI/tutorials @.>
Cc: "Qiu, Edwin" @.>, Mention @.***>
Subject: Re: [Project-MONAI/tutorials] 3D classification tutorial Early stopping (Issue #666)
Hi @addcuehttps://github.com/addcue ,
If you don't want to apply the Early-Stop, maybe you can remove these 2 lines and run again:
https://github.com/Project-MONAI/tutorials/blob/master/3d_classification/ignite/densenet_training_dict.py#L151-L152
Thanks.
—
Reply to this email directly, view it on GitHubhttps://github.com/Project-MONAI/tutorials/issues/666#issuecomment-1105232681, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AI4FXCC5IVAF432CUQSKG6DVGFMAZANCNFSM5T57RAJA.
You are receiving this because you were mentioned.Message ID: @.***>

Hi @addcue ,
These examples only try to show the functionality, not real-world training, you can see that we only used few images of the dataset.
Thanks.


Warn command markdown.extension.onBackspaceKey not found.

VSCode Version: Code 1.18.1 (929bacba01ef658b873545e26034d1a8067445e9, 2017-11-16T18:23:26.125Z)
OS Version: Darwin x64 17.2.0
Extensions:

Extension
Author (truncated)
Version

format-php
Kas
1.1.2

html-css-class-completion
Zig
1.14.0

html-snippets
abu
0.1.0

color-info
bie
0.5.0

path-intellisense
chr
1.4.2

gitlens
eam
6.3.0

php-debug
fel
1.12.1

php-intellisense
fel
2.0.4

php-pack
fel
1.0.1

auto-close-tag
for
0.5.5

auto-rename-tag
for
0.0.15

php-cs-fixer
jun
0.1.51

mssql
ms-
1.2.1

php-docblocker
nei
1.3.2

vscode-todo-highlight
way
0.5.11

markdown-all-in-one
yzh
0.11.2

vscode-open-in-github
ziy
1.3.0

(1 theme extensions excluded)

Steps to Reproduce:
When I open a markdown file with HTML code inside, like
lorem ipsum
 and want to delete the tags using keyboard (
 for example), I have this message:
Warn command markdown.extension.onBackspaceKey not found.
The error appears for tab key too:
Warn command markdown.extension.onTabKey not found.
Reproduces without extensions: No. I suspect Markdown All in One.

Please file this issue against your markdown extension


[BUG]: Learn How to Interact with On-Chain Programs - establishConnection - async or not

Issue/Experience
There's inconsistency of whether establishConnection function should be asynchronous or not. While defined in the step 9, the problem can reveal itself as far as step 57.
Step 9 - Mentions exporting async function from hello-world.js.
Step 10 (and further) - Seed of the hello-world.js has synchronous function.
Step 11 - Last test uses await when calling establishConnection.
Step 12 - Mentions adding const connection = establishConnection() to the main.js file.
Step 13 (and further) - Seed of the main.js file, has const connection = establishConnection().
Step 57 - Running node src/client/main.js results in error. I'm right now not entirely sure, but I recall this didn't stop all step tests from passing.
file:///workspace/solana-curriculum/learn-how-to-interact-with-on-chain-programs/src/client/hello-world.js:70
    const account = await connection.getAccountInfo(programId)
                                     ^

TypeError: connection.getAccountInfo is not a function
    at checkProgram (file:///workspace/solana-curriculum/learn-how-to-interact-with-on-chain-programs/src/client/hello-world.js:70:38)
    at main (file:///workspace/solana-curriculum/learn-how-to-interact-with-on-chain-programs/src/client/main.js:9:11)
    at async file:///workspace/solana-curriculum/learn-how-to-interact-with-on-chain-programs/src/client/main.js:13:1

Output of running node tooling/camper-info.js from the workspace root
🔵 INFO:   Project:  learn-how-to-interact-with-on-chain-programs
🔵 INFO:   Lesson Number:  1
🔵 INFO:   Curriculum Version:  0.1.2
🔵 INFO:   freeCodeCamp - Courses<EMAIL_ADDRESS>🔵 INFO:   Commit:  5526f1a chore(deps): update dependency @types/node to v18.11.13
🔵 INFO:   OS Info:
Architecture: x64
Platform: linux
Release: 5.15.0-56-generic
Type: Linux

Thank you for opening this, and providing detailed steps.
establishConnection should NOT be async. So, I guess the error on step 57 is from you declaring it as async, and connection being a Promise<Connection> which does not have .getAccountInfo?

establishConnection should NOT be async. So, I guess the error on step 57 is from you declaring it as async, and connection being a Promise<Connection> which does not have .getAccountInfo?

I had similar assumption regarding problem on the step 57.


Please provide the code for the obfuscated lambda python code

It's hard to unobfuscate an indentation based language. I want to see what does it do exactly and maybe change it to suit my needs if necessary. Thanks

It‘s not „obfuscated“, it‘s minimized. You can find a link to the original source repo at https://github.com/tobilg/serverless-aws-static-websites/blob/master/resources/custom-acm-certificate-lambda.yml#L5
I‘ll not provide a separate Version in this repo, sorry.


docker部署控制台报错  登陆进去没有任何反应

console.min.js:1 WebSocket connection to 'ws://<IP_ADDRESS>:10010/console/sshws/Lo6JpqA87KrIt1CO8WF0CjGInZYnZ64RmfkK+u5XTQSjF4s=?cols=136&rows=16' failed: Error during WebSocket handshake: Unexpected response code: 403

请添加服务器白名单发自我的华为手机-------- 原始邮件 --------主题：[shibingli/webconsole] docker部署控制台报错 登陆进去没有任何反应 (#45)发件人：yangzhenwei-java 收件人：shibingli/webconsole 抄送：Subscribed console.min.js:1 WebSocket connection to 'ws://<IP_ADDRESS>:10010/console/sshws/Lo6JpqA87KrIt1CO8WF0CjGInZYnZ64RmfkK+u5XTQSjF4s=?cols=136&rows=16' failed: Error during WebSocket handshake: Unexpected response code: 403
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/shibingli/webconsole","title":"shibingli/webconsole","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/shibingli/webconsole"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"docker部署控制台报错  登陆进去没有任何反应 (#45)"}],"action":{"name":"View Issue","url":"https://github.com/shibingli/webconsole/issues/45"}}}


desktopManagerHandlesLidAndPower should be set per session not global

The state of services.xserver.displayManager.desktopManagerHandlesLidAndPower be set per session and not globally as my "none + xmonad" session wants to be true and my kde5 session wants it to be false.
While @Profpatsch 's commit 44c12dc0ff131653f35fc63e97257bf089082c21 moves the act setting downstream, this now creates a problem if the variable is set to different values as it is still of global scope. In the above example I needed to disable it globally to remove the conflict (or rather, I let kde5.enable set it globally for me).

I suppose you've missed #9642 – we don't have the option anymore, for related reasons.

Also see my comment https://github.com/NixOS/nixpkgs/pull/9642#issuecomment-138590745

@vcunat I did, thanks for pointing it out!
@Profpatsch ACK.


Tutorial or code example please

Hi @Mefodei
Could you please create some examples or write some tutorials, readme to getting started with this tool?
Thank you so much! Addressable Tech is the replacement of the Assets Bundle in the future, definitely.

Hello. I'm currently working on that :)
пн, 17 мая 2021 г. в 06:26, takaaptech @.***>:

Hi @Mefodei https://github.com/Mefodei
Could you please create some examples or write some tutorials, readme to
getting started with this tool?
Thank you so much! AddressableTools is the replacement of Assets Bundle in
the future, definitely.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/UniGameTeam/UniGame.AddressableTools/issues/3, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABY4TDU634FA5IN54FO6PPDTOCEFLANCNFSM447SRB2A
.

--
Best Regards
Sergey Mikhaylov
Tel: +7 (931) 963-99-56
CTO
email: @.***
linkedin: https://www.linkedin.com/in/mefodei
github: https://github.com/Mefodei

Thank you! Have a nice day!


✨  Input file and output file in run command

Fix #14

I can't test this feature because of #15

J'arrive bien à logger les erreurs, mais j'ai pas le prefix devant.

Good enough for tonight! We'll improve/refactor later. :) thx


Try different olfactory threshold with the DNS data and Model 7

Following #62
We can make a test with a more fine subdivision of the thresholds to be tested to analyze the performances.
Instead of testing every 1e-1, 1e-2, ... 1e-9,
we can try: 0.1, 0.09, 0.08,... 0.01, 0.009, 0.008, ... 0.001

Implemented October 2nd
Convergence:

Steps Taken:

Notes:
We can see that the 9x9, 7x7 model is very good at higher thresholds (Smaller amount of cues) compared to the 5x5, 5x5 model.
But at lower thresholds, this is inverted, the 5x5, 5x5 model is better than the 9x9, 7x7 model.


Entering Middle names

Marriage entries:
If the a Middle Name has been entered incorrectly using the backspace to delete the entire entry moves the curser to the 'Spouse' field.  It should remain in the now empty 'Middle Name' field

ok, this behavior has been fixed in 1.0.7


Update 3Box.js documentation on npm

It's not current. For example still has getActivity().

This will be fixed when we release 1.0.0. Npm looks at the most recent published version that is not publised to the next tag, i.e. beta.


Fix retain cycle

Noticed a retain cycle when using RxViewModel.

Actually, still seeing the issue (though I'm pretty sure the change I made in this PR should still eliminate one retain cycle.)
Documenting the issue here: https://github.com/RxSwiftCommunity/RxViewModel/issues/31

😱 good catch @sprynmr
CirceCI has been off for quite some time (need to fix this).
I'll go ahead and merge this (giving that its true that this should take at least 1 retain cycle)
Thanks for the PR.
BTW. I'm following Ash Furrow's idea and I'm offering access to the repo, etc to anyone that submits a PR and gets merged; let me know if that's something you would be interested in 😄

Hey sure. At some point I think it would make sense to move to a protocol first approach for this, similar to the open PR https://github.com/RxSwiftCommunity/RxViewModel/pull/25. Not sure exactly what that would look like (maybe that PR is dead on), but something I was going to look at at some point here.

Yes; definitely the protocol approach was always on my mind but at the time of the creation of this library i lacked enough knowledge to make it happen as I wanted it to be.
I need to check #25 deeply because it could be the solution or might too close to only need very few tweaks 😄
I'll send you an invite to the org right now BTW


nixos/gonic: init

Description of changes
Adds a module for gonic using a generic settings style interface, including a basic module test. Based mainly on the navidrome module. Closes #181965.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[x] (Module addition) Added a release notes entry if adding a new NixOS module
[x] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1603

I've noticed that scrobbling is broken so I marked it as a draft for now.

Scrobbling was fixed by adding /etc/resolv.conf to the list of read-only binds.

@SuperSandro2000 could I kindly ask you for another review? Thanks!

Rebased to the current master

Rebased to current master


Add files via upload

add kyonggi univ

@jouiyeon I am sorry, the domain kyonggi.ac.kr is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


FIX duplicated nodes on Symbols

@tiagoaguiar31 Closing this as it's fixed by https://github.com/virtualidentityag/biotope-sketcher/pull/7/commits/ab4ae9eda4c528045ede657f8099e433d1b46c65


wrong deserialize of the datetimeoffset

coming from here
Describe the bug
i have a model like this
class MyModel{
    public DateTimeOffset? plannedStartDate {get;set;}
}

and an action like this
[HttpPost]
public IActionResult Get(MyModel activityUpdate){
}

and i'm sending request from angular as a json
    {
       "plannedStartDate": "2019-03-04T16:00:00.000Z"
    }

which contains a valid date

but what i'm getting in the api is wrong

if i inspet the variable in the immediate windows i can see that the offset couldnt' parse correctly

i tried to change the mvc options to
service.AddMvc()
 .AddJsonOptions(opt=>
    opt.SerializerSettings.DateParseHandling=DateParseHandling.DateTimeOffset);

i also played with these options
DateFormatHandling = DateFormatHandling.MicrosoftDateFormat,
DateTimeZoneHandling = DateTimeZoneHandling.Local

and
DateFormatHandling = DateFormatHandling.IsoDateFormat,
DateTimeZoneHandling = DateTimeZoneHandling.Local,
DateParseHandling = DateParseHandling.DateTimeOffset

which didn't help, i dont' think it's about deserialize options.
our staging server is using linux and we don't have this problem, but our production use IIS on windows server and have this problem. i am not sure if it's related on the OS. but if i try it on my local development(which is windows 10) aslo i'm facing the same bug.
To Reproduce
Steps to reproduce the behavior:

Using this version of ASP.NET Core '2.2'
use windows machine (this bug doesn't happen in linux)

Expected behavior
something like this shouldn't need to have custom modelbinder or custom serilizer implementation. i checked a lot of solutions in SO, but most ask to create a new serilizer or modelBinder which doesn't make sense. when the input is valid and model ask for datetimeoffset why the offset is truncated?
Additional context
Include the output of dotnet --info
.NET Core SDK (reflecting any global.json):
 Version:   2.2.104
 Commit:    73f036d4ac

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.17763
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\2.2.104\

Host (useful for support):
  Version: 2.2.2
  Commit:  a4fd7b2c84

.NET Core SDKs installed:
  2.1.503 [C:\Program Files\dotnet\sdk]
  2.1.504 [C:\Program Files\dotnet\sdk]
  2.2.101 [C:\Program Files\dotnet\sdk]
  2.2.102 [C:\Program Files\dotnet\sdk]
  2.2.104 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.2.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.2.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.2.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.2.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.2.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.2.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.8 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.2.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.2.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.2.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

I'm not sure I follow your description.

Do you think that you should have, after deserialization, a date with a timezone for Singapore?
But you're sending a value with a specific Timezone UTC (Z) and you're deserializing a DateTimeOffset which honors this timezone.  The offset is not truncated, it specified via 'Z' to be UTC. If you don't like that you can either send the correct Timezone or change your model to use DateTime and change the knobs to do local TimeZone Handling (as you've already tried). But as https://www.newtonsoft.com/json/help/html/DatesInJSON.htm specified, those knobs don't work with DateTimeOffset.

yes, you are right, it was a bug in my side, thanks for explanaing.


Gives empty list when passing withProperties: true on iOS

Without withProperties: true, it returns 2000+ contacts for me with just displayName but when I pass withProperties: true then I get an empty list. I am trying this on iOS 17, iPhone 15 PRO

Even when withProperties is set to true, I am not getting phone numbers on iOS.


The integration tests have been run in openSUSE Leap 42.1
Docker 1.11.2 has been installed from
$ cat /etc/zypp/repos.d/containers.repo
[containers]
enabled=1
autorefresh=0
baseurl=http://download.opensuse.org/repositories/Virtualization:/containers/openSUSE_Leap_42.1
type=rpm-md
gpgcheck=0
keeppackages=1

Steps to reproduce the issue:
I'm trying to port the Docker integration tests to openSUSE in order to have a testsuite that can be verify the proper behavior of the Docker daemon in this environment. So far, I have successfully ported from the top Dockerfile all the steps required for creating the required testing environment. All the integration tests run fine except for the TestRunUnshareProc test.
This test runs the command:
sudo docker run --rm --privileged --security-opt seccomp=unconfined --security-opt apparmor=docker-default --name test debian:jessie unshare -p -m -f -r mount -t proc none /proc

and it expects to fail with a permission denied kind of error. I guess it is related to the apparmor configuration:
> cat /etc/apparmor.d/docker

@{PROC}=/proc/

profile docker-default flags=(attach_disconnected,mediate_deleted) {
  network,
  capability,
  file,
  umount,

  deny @{PROC}/* w,   # deny write for all files directly in /proc (not in a subdir)
  # deny write to files not in /proc/<number>/** or /proc/sys/**
  deny @{PROC}/{[^1-9],[^1-9][^0-9],[^1-9s][^0-9y][^0-9s],[^1-9][^0-9][^0-9][^0-9]*}/** w,
  deny @{PROC}/sys/[^k]** w,  # deny /proc/sys except /proc/sys/k* (effectively /proc/sys/kernel)
  deny @{PROC}/sys/kernel/{?,??,[^s][^h][^m]**} w,  # deny everything except shm* in /proc/sys/kernel/
  deny @{PROC}/sysrq-trigger rwklx,
  deny @{PROC}/mem rwklx,
  deny @{PROC}/kmem rwklx,
  deny @{PROC}/kcore rwklx,

  deny mount,

  deny /sys/[^f]*/** wklx,
  deny /sys/f[^s]*/** wklx,
  deny /sys/fs/[^c]*/** wklx,
  deny /sys/fs/c[^g]*/** wklx,
  deny /sys/fs/cg[^r]*/** wklx,
  deny /sys/firmware/efi/efivars/** rwklx,
  deny /sys/kernel/security/** rwklx,

  # suppress ptrace denials when using 'docker ps' or using 'ps' inside a container
  ptrace (trace,read) peer=docker-default,
}

so any tip on this would be appreciated....
Describe the results you received:
START: /home/abuild/rpmbuild/BUILD/docker-1.11.2/integration-cli/docker_cli_run_test.go:3007: DockerSuite.TestRunUnshareProc
/home/abuild/rpmbuild/BUILD/docker-1.11.2/integration-cli/docker_cli_run_test.go:3056:
    ...open /home/abuild/rpmbuild/BUILD/docker-1.11.2/integration-cli/docker_cli_run_test.go: no such file or directory
... Error: privileged unshare with apparmor should have failed with 'mount: cannot mount none' or 'permission denied', got: , <nil>

Describe the results you expected:
PASS: /home/abuild/rpmbuild/BUILD/docker-1.11.2/integration-cli/docker_cli_run_test.go:3007: DockerSuite.TestRunUnshareProc

Additional information you deem important (e.g. issue happens only occasionally):

ping @cyphar any ideas?

@inercia is on the same team as me :wink:, we've been looking into this issue for a while (we're working on running the integration tests as part of our release setup).

This is likely caused by SUSE offering only incomplete AppArmor support. I.e. AppArmor expects mount masks to be enabled, i.e. it expects that /sys/kernel/security/apparmor/features/mount/mask is present but it is not.

Then I think I will modify this test in order to skip it when /sys/kernel/security/apparmor/features/mount/mask does not exist... I will submit a PR when it's ready

@inercia Curious if you ever got to sending us that pr?

ping @inercia ^^

ping @inercia @cyphar is this still an issue?


Downloading Genshin Impact fails with error

I am on pre-release channel.
Version: 1.70.4 Preview
GIF
https://iili.io/H4z1BEu.gif
Error log
System.UriFormatException: Invalid URI: The URI is empty.
   at System.Uri.CreateThis(String, Boolean, UriKind, UriCreationOptions& )
   at System.Uri..ctor(String uriString)
   at Hi3Helper.Http.Http.GetContentLengthAsync(String Input, CancellationToken token) in E:\myGit\Collapse\Hi3Helper.Http\Class\Session\SessionManager.cs:line 352
   at Hi3Helper.Http.Http.TryGetContentLengthAsync(String URL, CancellationToken Token) in E:\myGit\Collapse\Hi3Helper.Http\Class\Session\SessionManager.cs:line 336
   at CollapseLauncher.InstallManager.Base.InstallManagerBase`1.TryGetPackageRemoteSize(GameInstallPackage asset, CancellationToken token) in E:\myGit\Collapse\CollapseLauncher\Classes\InstallManagement\BaseClass\InstallManagerBase.cs:line 795
   at CollapseLauncher.InstallManager.Base.InstallManagerBase`1.GetPackagesRemoteSize(List`1 packageList, CancellationToken token) in E:\myGit\Collapse\CollapseLauncher\Classes\InstallManagement\BaseClass\InstallManagerBase.cs:line 788
   at CollapseLauncher.InstallManager.Base.InstallManagerBase`1.StartPackageDownload(Boolean skipDialog) in E:\myGit\Collapse\CollapseLauncher\Classes\InstallManagement\BaseClass\InstallManagerBase.cs:line 127
   at CollapseLauncher.Pages.HomePage.InstallGameDialog(Object sender, RoutedEventArgs e) in E:\myGit\Collapse\CollapseLauncher\XAMLs\MainApp\Pages\HomePage.xaml.cs:line 487

Duplicate of #148
An update is recently pushed to pre and stable regarding this bug, please update and try again

Hi @seriaati,
As bagus already said above, please update your launcher to the latest version and since the issue should've been fixed now, we are going to close this issue in 24 hours.
Please let us know if you have any issues.


date_trunc on bigquery

Describe the bug
Macro date_trunc on bigquery use a convertion to timestamp, so result is in a timestamp format and not keep original format.
date_trunc function exist on biguqery : https://cloud.google.com/bigquery/docs/reference/standard-sql/date_functions?hl=fr#date_trunc
Steps to reproduce
Use date_trunc on biquery with a source column in date format (not a timestamp), result of trunc is in timestamp format.
Expected results
Keep source format
Actual results
Result of trunc is in timestamp format, not in source format
System information
The contents of your packages.yml file:
Which database are you using dbt with?

[ ] postgres
[ ] redshift
[X] bigquery
[ ] snowflake
[ ] other (specify: ____________)

Are you interested in contributing the fix?
I am able to fix this.
But I don't know why a more complex method has been added specifically for BigQuery.
We rarely do complicated things for fun.

it's not a dbt-utils issue, but a dbt-core issue.


[QUERY] Does Azure.ResourceManager.CosmosDB support Cosmos DB Emulator?

Library name and version
Azure.ResourceManager.CosmosDB
Query/Question
Does Azure.ResourceManager.CosmosDB support Cosmos DB Emulator?
For example, do the control plane operation like CreateDatabase, CreateCollection using this client's API.
Environment
Windows
Dotnet 6

HI @blankor1.  Thank you for reaching out and for your inquiry.  The Azure SDK management packages are intended to work with the official Azure ARM endpoints.  Unfortunately, we cannot answer what the emulator may or may not support.   In order to get an authoritative answer to your question, you'd need to ask the owners of the Cosmos emulator if they officially support the ARM API.
As the emulator is not open source, there is no GitHub repository for me to transfer your inquiry to.  Your best path forward for would be to open an Azure support request or inquire on the Microsoft Q&A site.
I'm going to close this out; if I've misunderstood what you're describing, please let us know in a comment and we'd be happy to assist as we're able.


feat: implement EthBlockNumber and validate against Lotus

Summary of changes

Changes introduced in this pull request:

Implement EthBlockNumber and test against Lotus

Reference issue to close (if applicable)

Closes associated task in #3640
Other information and links

Change checklist

[ ] I have performed a self-review of my own code,
[ ] I have made corresponding changes to the documentation,
[ ] I have added tests that prove my fix is effective or that my feature works (if possible),
[ ] I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

After latest changes:


add Infarm

Our software team is remote; other departments may be partially/fully remote.

@lisaq Thank you 👏


GEODE-3720: Bounce DUnit VMs to give the test a clean environment

Bounce the VMs once at the beginning of the test so they start clean.
Rules in the test ensure the VMs are cleaned up after each test method.
Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[x] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[x] Is your initial contribution a single, squashed commit?

[x] Does gradlew build run cleanly?

[x] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

Do we need to bounce both before and after? Could we just bounce before? Do you know why after is not enough?

Original intent of the rule was to have tests cleanup after themselves. However, the use of the rule is not universal, so there are tests 1) don't adequately cleanup (leading to flaky test failures like ConnectCommandWithSSLTest), and 2) need clean VMs to avoid their own flaky failures.
If all DUnit tests used the rule, then presumably we would not need to bounce VMs before.


Correct MACRO GDP reporting & update docs

This PR:

Corrects the reporting of GDP which includes the deduction of trade_costs coming from MESSAGE.

Updates MESSAGEix based total_cost parameter in iteration with MACRO including the trade balance.

Extends the documentation of the capital constraint section in MACRO to explain the reasoning behind the changes.

PR #422 can be closed after merging this.

[x] Continuous integration checks all ✅
[x] Add or expand tests; coverage checks both ✅
[x] Add, expand, or update documentation.
[ ] Update release notes.

Hi @GamzeUnlu95 - I understand there are still some requirements left for this to be merged. Would you say it is available to try to use on a trial basis?

Hi folks, I wanted to report back after having tried to use this PR in some of my ongoing work.
Observed issue: Running a mitigation scenario with a calibrated scenario causes MESSAGE LP infeasibility within MESSAGE-MACRO iteration.
Suggestion: Before merging this, run a test case on the current ENGAGE set up where MACRO is recalibrated with these changes and confirm that mitigation cases can still converge.
More specifics:
It's hard for me to pin point exactly why this PR causes my failure, but I am combining a number of updates - I start from the new R15 model, apply 1-year time steps for early periods, and calibrate using this MACRO branch. I did not observe any issues while creating baselines or non-mitigation scenarios.

MESSAGE LP infeasibility within MESSAGE-MACRO iteration

Can you please upload a snippet from the GAMS .lst file to indicate which variables are infeasible?

That file has already been overwritten. I can try later to reproduce - can you tell me what to grep for?

But this is a good opportunity to plug our need for better tooling when dealing with infeasibilities. It would be great to have some first (or even second) class support to say, dump out why a model was infeasible at the end of a run that is persistable.

can you tell me what to grep for?

https://github.com/iiasa/message_ix/issues/418#issuecomment-720388779 for example

I have pulled these changes onto the latest main branch, updated the macro-calibration xlsx but then encountered errors.
**** Exec Error at line 544: log: FUNC SINGULAR: x = 0
**** Exec Error at line 544: overflow in * operation (mulop)

Has anyone encountered such issues? Was this PR already tested with the calibration? I have added the macro_run.lst file as a .txt file if this helps with debugging.
MACRO_run.txt

I have pulled these changes onto the latest main branch, updated the macro-calibration xlsx but then encountered errors.
**** Exec Error at line 544: log: FUNC SINGULAR: x = 0
**** Exec Error at line 544: overflow in * operation (mulop)

Has anyone encountered such issues? Was this PR already tested with the calibration? I have added the macro_run.lst file as a .txt file if this helps with debugging. MACRO_run.txt

Thanks for adding the .lst file. I attempted to test this PR with calibration a couple of months ago and at that time there was an issue with the macro-calibration xlsx in the main branch and I could not complete it. I need to find and allocate time soon to test this PR again and finalize it.

I tested this PR with the ENGAGE setup by using the model ENGAGE_SSP2_v4.1.7_T4.5_r3.1_test. I did not experience any issues with the calibration of the baseline. I ran the mitigation case with 600 budget and was able to get a solution for EN_NPi2020_600. However, in Step 3 of EN_NPi2020_400, in the third iteration, there is an execution error division by eps as in this MESSAGE-MACRO_run.log and MESSAGE-MACRO_run_lst file. Not sure if this is directly related to the changes that are made in this PR. The line indicated in the error message is the following:
price_diff_rel(iteration,node_macro,sector,year)$( price_init(node_macro,sector,year) ) =
5455      price_diff_abs(iteration,node_macro,sector,year) / price_init(node_macro,sector,year)

At today's message meeting, this PR was suggested to me as a possible fix for #752. As far as I can tell, this PR does not enable usage of user-defined units. However, I rebased this onto current main so if you want to run any tests again to see if this can be merged, this might be a good time, @GamzeUnlu95, @OFR-IIASA, @gidden.

This PR may even predate the PR template, but it is missing one item that appears there: "Update release notes". I've added this to the PR description above.
These notes are especially important when the behaviour and outputs of the core GAMS code change, as in this PR. Users must have an opportunity to notice and understand how their model outputs may be affected by a new release.

As discussed in yesterday's weekly meeting, we hold off on merging these changes because we don't trust our current test suite to adequately verify that the changes won't break anything. As @gidden suggested (please correct me if I misunderstood), we should set up a testing workflow that runs a full emission baseline and a peak budget scenario. Since these runs might take a while, we would ideally keep them optional and either run them as part of nightly tests or enable them on PRs that affect the GAMS code. This would allow us to trust the changes here.
@Jihoon noted that the line currently causing the test failure reported by @GamzeUnlu95 had caused issues before, so was removed locally in his installation without any noticeable negative consequences. No one else in the room knew what this line might be good for, so in a separate PR, we could try to remove it -- and test that with the new test cases proposed above.

Thanks @glatterf42. My suggestion is to follow @khaeru's example here and combine this with @OFR-IIASA's ENGAGE process script here.
I would suggest to run

a baseline scenario
a full century budget scenario
a peak-budget scenario

And compare a few key metrics on the output excel (e.g., co2 emissions, kyoto emissions, gdp, primary energy, final energy).

My suggestion is to follow @khaeru's example here and combine this with @OFR-IIASA's ENGAGE process script here.

While I generally agree with this idea directionally and the basic observation underlying it, to implement these ideas would involve, conservatively, at least 2 person-weeks of work. Either we accept that this PR sits until someone is assigned/freed-up to spend that time, or we find a simpler, manual check (and someone to do it) that can assure that this PR will not change [expected behaviour].
In order to avoid derailing this particular PR with that broader discussion, I'll open a new issue.


Code isolation: Plugins with no shared types vs AppDomain

I'm using plugins successfully in my app. Everything works great. Currently the host and the single plugin are being built at the same time. One would not expect any conflict given that all the shared dependencies are the same version. I want to separate the host from the plugin with regard to building.  The shared dependencies (numerous) will now be different. The host would be updated much less frequently then the plugins. So now my question: I had previously been using AppDomains for isolation and of course never experienced any dependency clash. If I do not share any types (no unification) can I expect the same level of isolation with DotNetCorePlugins?
Thanks for you efforts.
Jim

Yes, you should see the same kind of isolation. DotNetCorePlugins relies on the AssemblyLoadContext feature of .NET Core, which is the spiritual successor of AppDomains. The ability to load multiple versions of the same assembly into one .NET process is about where the similarities end, though. AssemblyLoadContext doesn't offer other features of AppDomains, like remote code execution.

Great! That's what I thought. Thanks for the quick reply.

Happy to help!


Add All Quiet to Alertmanager Webhook Receiver

Please add All Quiet to the list of webhook receivers.

:+1: Thanks!


Support more commit types

See https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#type
build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
docs: Documentation only changes
feat: A new feature
fix: A bug fix
perf: A code change that improves performance
refactor: A code change that neither fixes a bug nor adds a feature
style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
test: Adding missing tests or correcting existing tests

I should have slept more ⏲


FirebaseMessaging.onMessage.listen trigger five times

firebase_core: ^1.3.0
firebase_messaging: ^10.0.2
FirebaseMessaging.onMessage.listen((RemoteMessage event) {
print("message recieved");
print(event.notification.body);
});
Print:
flutter: message recieved
flutter:please check notification
flutter: message recieved
flutter:please check notification
flutter: message recieved
flutter:please check notification
flutter: message recieved
flutter:please check notification
flutter: message recieved
flutter:please check notification

Hi @adnankhan74444
Where are you listening to onMessage? Are you sure you aren't just listening to it multiple times?
Thank you

I've same problem


Need Example Project

Hello, I already read through the documentation, but I still can't understand how to use this. Is there anyone who would provide any example project for this?
Thanks

Sorry, we currently can not provide an example application|source at the moment, but i can assure you, that this library works at its best.
You have to use your brain a bit and figure out on your own. But in my opinion the documentation is quite enough for the most basic actions.
Please close this issue, as this is a personal matter, and not targeting any bugs nor recommending features or tweaks.

Just try it with creating a fresh React Native project, it works like charm and pretty easy to implement. What I previously to do is combine it with this repository https://github.com/rusel1989/react-native-bluetooth-serial and it gets a little bit tricky. I'll just reopen this issue with other title as current title would be misleading. Anyway thank you for your suggestion @HunWalk

Yeah, because the lib itself already using the bluetooth module to establish connection between devices, sooo expect some weird stuff going on. Could you provide some logs or description or steps to reproduce the problem or an actual description about the stuff that goes on when you link this lib with the BluetoothSerial one? If you want to extend the bluetooth capabilities of this lib..you may have to create your own native module(not from scratch, just fork this and add your stuff) to be able to add some customizations.


Update README.md

Small text improvements
Signed-off-by: André Franciosi<EMAIL_ADDRESS>

Will do it again with Signed-off-by.


Samples: Fix behavior when specified non-intel device

Add:
Fixes: 4e3c14a ("samples: add support for render node specifying")
To commit message. Question: did you verify that samples work with -device parameter?

Done.
Yes, i double-checked this, but in first commit I missed this behavior due to big log...


Feature Request: Ability to control sign priority

In NeoVim, one can control the 'priority' of signs in the sign column. (See :help sign-priority). It would be nice if I could control the priority of the signs marks.nvim places in its configuration. For example, I use gitsigns.nvim also, and I consider git changes to be more important than marks.nvim signs (sorry!). It would be nice to be able to 'demote' the signs from this plugin.
Even better (if this is not just creeping configuration) would be to control letter signs and built-in marks separately. The former I place myself, so they are arguably 'important'. The latter are by-products of editing, and I would argue should be very low priority.

Yes, this is on the todo list. My priority is first fixing #10 , but after that it should be relatively simply to add an option controlling this.


[NPM] Fixing netpol translation issues with extended cyclonus

Reason for Change:

This PR fixes two issues:

If a rule has multiple ip CIDR blocks, we will not use the same name and consider them to be individual ipsets. Introduced a peerindex to help with this.

  egress:
  - ports:
    - port: 80
      protocol: TCP
    to:
    - ipBlock:
        cidr: <IP_ADDRESS>/24
    - ipBlock:
        cidr: <IP_ADDRESS>/24
        except:
        - <IP_ADDRESS>/28

If a rule has a pod selector and ip cidr block, we should consider them as OR  and not as AND

  - from:
    - namespaceSelector: {}
    - ipBlock:
        cidr: <IP_ADDRESS>/24

Issue Fixed:

Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests

Notes:

/azp run


Fix/daef 196 sidebar UX updates

This PR introduces a fix which prevents sidebar auto-hiding feature and always show submenus on wallets page load.

reviewing this one now …


No module named 'pympler'

Hi,
I tried to run the demo in the README file but got an exception.
The command and output are:
python main.py --llm_name gemma-2b-it --max_gpu_memory '{"0": "24GB"}' --eval_device "cuda:0" --max_new_tokens 256
Traceback (most recent call last):
File "/root/autodl-tmp/AIOS/main.py", line 21, in
from src.agents.agent_factory import AgentFactory
File "/root/autodl-tmp/AIOS/src/agents/agent_factory.py", line 14, in
from pympler import asizeof
ModuleNotFoundError: No module named 'pympler'
Does it mean the file pympler.py is not included in the released code now?

Ok. I resolved this question now but met another one.
pleaseTraceback (most recent call last):
File "/root/miniconda3/lib/python3.10/site-packages/urllib3/connection.py", line 174, in _new_conn
conn = connection.create_connection(
File "/root/miniconda3/lib/python3.10/site-packages/urllib3/util/connection.py", line 95, in create_connection
raise err
File "/root/miniconda3/lib/python3.10/site-packages/urllib3/util/connection.py", line 85, in create_connection
sock.connect(sa)
TimeoutError: timed out
Does it mean I cannot connect to Hugging Face? If so, how to address this.

Pympler dependencies have been added into the requirements.txt. And about the error of connecting to huggingface, I am not sure whether you apply for the access to use the specific model in the huggingface model card.

Thanks for the clarification. I checked that my server cannot ping huggingface.
I wonder is there any screenshot to show the execution result of AIOS?


Feature/no intersection edge cases

alls tests for spoken edge-cases are green, except diffing where source contains clip.
meaning we would create a hole in the source, which cannot be represented by the datastructure.
| ------------------- |
|  -----------------  |
|  |                 |   |
|  |                 |   |
|  -----------------  |
| -------------------- |

we have to discuss how to handle this.
for now an error is thrown.

before merge we have to adapt the test for diffing holes (which fail because an error is thrown)


The "ResolveNativeReferences" task failed unexpectedly

I am interested in using this nuget in my project but I am getting the following compile error after installing the nuget: "The "ResolveNativeReferences" task failed unexpectedly".
Nuget version:

Drastic.IQKeyboardManager 1.0.0

As you can see in the .csproj image, the only difference from your sample project is that I have more platforms in the TargetFrameworks tag and the nuget is installed with the condition:  Condition="'$(TargetFramework)' == 'net7 .0-ios'" to avoid problems with other platforms, can you think of what might be happening? I leave an example project on GitHub:
https://github.com/nacompllo/IQKeyboardManagerIssue/tree/master/IQKeyboardManagerIssue

I believe you're hitting this issue, https://github.com/xamarin/xamarin-macios/issues/16001, specifically https://github.com/xamarin/xamarin-macios/issues/16001#issuecomment-1398175706. I'm packaging this as an xcframework and the SDK/Platform on Windows is not able to extract it.
I could change it to just reference the framework, but then I would need to bundle both device and simulator frameworks and I'm not sure how to do that, nor do I really feel like it. I rather the original issue be fixed by the SDK/Platform team rather than me hack around it. Sorry!


[Enhancement]: Avoider Game

Is your enhancement request related to a problem? Please describe.➕
Game enhancement

Avoider Game styling and functioning improvement.
Attractive UI/UX for the users to give best experience.

Describe the solution you'd like
Solution steps

Increase the size of the board.
Adding styling and hover effect with best user experience.

Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @Avdhesh-Varshney !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/assign

Hey @Avdhesh-Varshney ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


Super Test Graph + Test Infrastructure

Due to the combinatorial explosion of the ways nodes can be rendered, it would be nice to create the following:

a super graph that contains an enumeration of all of the possible combinations of sbgn classes

For example:  complex, complex w/ clonemarker, complex w/ state var, complex with unit of info, complex with multimer, complex w/ clonemarker and state var, complex w/ clonemarker and unit of info, etc.

more bells and whistles in the demo app so that it doesnt take as long to test these changes.

ideally, and probably the most sustainable way would be to create test infrastructure that can automate testing properties for svg.  I am not sure you can automate visual testing.  e.g does this graph look better after these changes?

Mostly done.  Didn't get all of the combinations but have a solid base to start.


support for markdown-it-emoji & markdown-it-mark

It would be great to see following extensions in stackedit
https://github.com/markdown-it/markdown-it-emoji
https://github.com/markdown-it/markdown-it-mark

Fixed in v5.11.


[bug] switch: attachInternals is undefined in Safari

In Safari, switch fails to render because this.attachInternals is undefined.
Steps to reproduce

Open https://patternflyelements.org/components/switch/ in Safari
View the console

The demo page, https://patternflyelements.org/components/switch/demo/, works fine because it imports element-internals-polyfill.
I think we'll need to add some guidance about including this polyfill when switch is used.

It looks like we'll need to include element-internals-polyfill prior to pfe.min.js being added to the page.

yes, we need to polyfill for now. luckily, webkit has already implemented element internals, so the polyfill period will not be very long


StackStorm v3.2dev pre-release Testing

We're ready to prepare the StackStorm v3.2 release and starting pre-release testing.
This will be the first StackStorm release under the Linux Foundation with new Open Source Governance and Maintainers team. We now rely on our Community more than ever and invite everyone to help with the pre-release testing and development/contribution.
Release Process Preparation
@armab and @punkrokk will freeze the master for the major repositories in StackStorm org, follow the StackStorm Release Process which is now available to public, accompanied by the Useful Info for Release managers. Communication is happening in #releasemgmt and #development Slack channels.
The first step is pre-release manual user-acceptance testing for v3.2dev.
Why Manual testing?
StackStorm is very serious about testing and has a lot of it: Unit tests, Integration, Deployment/Integrity checks, Smoke tests and eventually end-2-end tests when automation spins up new AWS instance for each OS/flavor we support, installs real st2 like user would and runs set of st2tests (for each st2 PR, nightly, periodically, during release).

See st2ci and st2cd for more examples and workflows about how StackStorm automation is used to test StackStorm (dogfooding).

That's a perfect way to verify what we already know and codify expectations about how StackStorm should function.
However it's not enough.
There are always new unknowns to discover, edge cases to experience and tests to add. Hence, manual (Exploratory Testing](https://en.wikipedia.org/wiki/Exploratory_testing) is an exercise where entire team gathers together and starts trying (or breaking) new features before the new release. Because we're all different, perceive software differently and try different things we might find new bugs, improper design, oversights, edge cases and more.
This is how StackStorm previously managed to land less major/critical bugs into production.
TL;DR
Install StackStorm v3.2dev staging packages, try random things in random environments (different OS) and report any regressions found comparing to v3.1:
curl -sSL https://stackstorm.com/packages/install.sh | bash -s -- --user=st2admin --password=Ch@ngeMe --unstable

Extra points for PR hotfixes and adding new or missing test cases.
Major changes
Important changes which are highly encouraged to try and test.

New CentOS8/RHEL8 support with Python 3.6 and MongoDB 4.0:
https://docs.stackstorm.com/latest/install/rhel8.html
New st2 pack install with dependencies:
https://docs.stackstorm.com/latest/packs.html#pack-dependencies
New Orquestra re-run:
https://docs.stackstorm.com/latest/orquesta/operations.html#re-running-workflow-execution
https://docs.stackstorm.com/latest/orquesta/operations.html#re-running-workflow-execution-from-task-s
New Orquestra task retry in workflow definition:
https://docs.stackstorm.com/latest/orquesta/languages/orquesta.html#task-retry-model
New Orquestra continue, noop, fail keywords in workflow definition:
https://docs.stackstorm.com/latest/orquesta/languages/orquesta.html#engine-commands
ChatOps functionality with Slack, Microsoft Teams, Cisco Spark (Webex) and Mattermost might be affected due to refactoring, fixes and major updates.
Test v3.1 -> v3.2 upgrade. Upgrade Notes:
https://docs.stackstorm.com/latest/upgrade_notes.html#st2-v3-2
Run st2-self-check
https://docs.stackstorm.com/latest/troubleshooting/self_verification.html

Full Changelog
Changes which are recommended to ack, explore, check and try in a random way.
st2
Added

Add support for blacklisting / whitelisting hosts to the HTTP runner by adding new
url_hosts_blacklist and url_hosts_whitelist runner attribute. (new feature)
stackstorm/st2#4757
Add user parameter to re_run method of st2client. stackstorm/st2#4785
Install pack dependencies automatically. stackstorm/st2#4769
Add support for immutable_parameters on Action Aliases. This feature allows default
parameters to be supplied to the action on every execution of the alias. stackstorm/st2#4786
Add get_entrypoint() method to ActionResourceManager attribute of st2client.
stackstorm/st2#4791
Add support for orquesta task retry. (new feature)
Add config option scheduler.execution_scheduling_timeout_threshold_min to better control the cleanup of scheduled actions that were orphaned. stackstorm/st2#4886

Changed

Install pack with the latest tag version if it exists when branch is not specialized.
(improvement) stackstorm/st2#4743

Implement "continue" engine command to orquesta workflow. (improvement) stackstorm/st2#4740

Update various internal dependencies to latest stable versions (apscheduler, eventlet,
kombu, amqp, pyyaml, mongoengine, python-gnupg, paramiko, tooz, webob, bcrypt).
Latest version of mongoengine should show some performance improvements (5-20%) when
writing very large executions (executions with large results) to the database. stackstorm/st2#4767

Improved development instructions in requirements.txt and dist_utils.py comment headers
(improvement) stackstorm/st2#4774

Add new actionrunner.stream_output_buffer_size config option and default it to -1
(previously default value was 0). This should result in a better performance and smaller
CPU utilization for Python runner actions which produce a lot of output.
(improvement)
Reported and contributed by Joshua Meyer (@jdmeyer3) stackstorm/st2#4803

Add new action_runner.pip_opts st2.conf config option which allows user to specify a list
of command line option which are passed to pip install command when installing pack
dependencies into a pack specific virtual environment. stackstorm/st2#4792

Refactor how orquesta handles individual item result for with items task. Before the fix,
when there are a lot of items and/or result size for each item is huge, there is a negative
performance impact on write to the database when recording the conductor state. (improvement)

Remove automatic rendering of workflow output when updating task state for orquesta workflows.
This caused workflow output to render incorrectly in certain use case. The render_workflow_output
function must be called separately. (improvement)

Update various internal dependencies to latest stable versions (cryptography, jinja2, requests,
apscheduler, eventlet, amqp, kombu, semver, six) stackstorm/st2#4819 (improvement)

Improve MongoDB connection timeout related code. Connection and server selection timeout is now
set to 3 seconds. Previously a default value of 30 seconds was used which means that for many
connection related errors, our code would first wait for this timeout to be reached (30 seconds)
before returning error to the end user. stackstorm/st2#4834

Upgrade pymongo to the latest stable version (3.10.0.). stackstorm/st2#4835 (improvement)

Updated Paramiko to v2.7.1 to support new PEM ECDSA key formats stackstorm/st2#4901 (improvement)

Remove .scrutinizer.yml config file. No longer used.

Convert escaped dict and dynamic fields in workflow db models to normal dict and dynamic fields.
(performnce improvement)

Add support for PEP 508 <https://www.python.org/dev/peps/pep-0508/stackstorm/st2#environment-markers>_
environment markers in generated requirements.txt files. (improvement) stackstorm/st2#4895

Use pip-compile from pip-tools instead of pip-conflict-checker (improvement) stackstorm/st2#4896

Refactor how inbound criteria for join task in orquesta workflow is evaluated to count by
task completion instead of task transition. (improvement)

The workflow engine orquesta is updated to v1.1.0 for the st2 v3.2 release. The version upgrade
contains various new features and bug fixes. Please review the release notes for the full list of
changes at https://github.com/StackStorm/orquesta/releases/tag/v1.1.0 and the st2 upgrade notes
for potential impact. (improvement)

Fixed

Fix the action query when filtering tags. The old implementation returned actions which have the
provided name as action name and not as tag name. (bug fix) stackstorm/st2#4828
Reported by @AngryDeveloper and contributed by Marcel Weinberg (@winem)

Fix the passing of arrays to shell scripts where the arrays where not detected as such by the
st2 action_db utility. This caused arrays to be passed as Python lists serialized into a string.
Reported by @kingsleyadam stackstorm/st2#4804 and contributed by Marcel Weinberg (@winem) stackstorm/st2#4861

Fix ssh zombies when using ProxyCommand from ssh config stackstorm/st2#4881 [Eric Edgar]

Fix rbac with execution view where the rbac is unable to verify the pack or uid of the execution
because it was not returned from the action execution db. This would result in an internal server
error when trying to view the results of a single execution.
Contributed by Joshua Meyer (@jdmeyer3) stackstorm/st2#4758

Fixed logging middleware to output a content_length of 0 instead of Infinity
when the type of data being returned is not supported. Previously, when the value was
set to Infinity this would result in invalid JSON being output into structured
logs. (bug fix) stackstorm/st2#4722
Contributed by Nick Maludy (@nmaludy Encore Technologies)

Fix the workflow execution cancelation to proceed even if the workflow execution is not found or
completed. (bug fix) stackstorm/st2#4735

Added better error handling to contrib/linux/actions/dig.py to inform if dig is not installed.
Contributed by JP Bourget (@punkrokk Syncurity) stackstorm/st2#4732

Update dist_utils module which is bundled with st2client and other Python packages so it
doesn't depend on internal pip API and so it works with latest pip version. (bug fix) stackstorm/st2#4750

Fix dependency conflicts in pack CI runs: downgrade requests dependency back to 0.21.0, update
internal dependencies and test expectations (amqp, pyyaml, prance, six) (bugfix) stackstorm/st2#4774

Fix secrets masking in action parameters section defined inside the rule when using
GET /v1/rules and GET /v1/rules/<ref> API endpoint. (bug fix) stackstorm/st2#4788 stackstorm/st2#4807
Contributed by @Nicodemos305 and @jeansfelix

Fix a bug with authentication API endpoint (POST /auth/v1/tokens) returning internal
server error when running under gunicorn and whenauth.api_url config option was not set.
(bug fix) stackstorm/st2#4809
Reported by @guzzijones

Fixed st2 execution get and st2 run not printing the action.ref for non-workflow
actions. (bug fix) stackstorm/st2#4739
Contributed by Nick Maludy (@nmaludy Encore Technologies)

Update st2 execution get command to always include context.user, start_timestamp and
end_timestamp attributes. (improvement) stackstorm/st2#4739

Fixed core.sendmail base64 encoding of longer subject lines (bug fix) stackstorm/st2#4795
Contributed by @stevemuskiewicz and @guzzijones

Update all the various rule criteria comparison operators which also work with strings (equals,
icontains, nequals, etc.) to work correctly on Python 3 deployments if one of the operators is
of a type bytes and the other is of a type unicode / string. (bug fix) stackstorm/st2#4831

Fix SSL connection support for MongoDB and RabbitMQ which wouldn't work under Python 3 and would
result in cryptic "maximum recursion depth exceeded while calling a Python object" error on
connection failure.
NOTE: This issue only affected installations using Python 3. (bug fix) stackstorm/st2#4832 stackstorm/st2#4834
Reported by @alexku7.

Fix the amqp connection setup for WorkflowExecutionHandler to pass SSL params. (bug fix) stackstorm/st2#4845
Contributed by Tatsuma Matsuki (@mtatsuma)

Fix dependency conflicts by updating requests (2.23.0) and gitpython (2.1.15). stackstorm/st2#4869

Fix orquesta syntax error for with items task where action is misindented or missing. (bug fix)
PR StackStorm/orquesta#195.

Fix orquesta yaql/jinja vars extraction to ignore methods of base ctx() dict. (bug fix)
PR StackStorm/orquesta#196. Fixes stackstorm/st2#4866.

Fix parsing of array of dicts in YAQL functions. Fix regression in YAQL/Jinja conversion
functions as a result of the change. (bug fix) PR StackStorm/orquesta#191.
Contributed by Hiroyasu Ohyama (@userlocalhost)

Removed

Removed Ubuntu 14.04 from test matrix stackstorm/st2#4897

Full list of changes: https://github.com/StackStorm/st2/blob/master/CHANGELOG.rst
orquesta
Added

Add feature to retry task execution on given condition with delay in between retries and
max number of retries. (new feature)
Contributed by Hiroyasu Ohyama (@userlocalhost) and Nick Maludy (@nmaludy)
Add support to rerun completed workflow (failed or succeeded) from given task(s). (new feature)

Changed

Replace "noop" with "continue" when "do" is not specified. The new "continue" command
will not alter the previous task state and will continue to conduct the workflow
execution. StackStorm/st2#4740 (improvement)
Refactor conductor to not store each item result in task state. If there are a lot of items
and/or result size is huge per item, then there will be a performance impact on database
write operations when recording the conductor state. (improvement)
Use ujson to deepcopy dict(s) for faster performance. (improvement)
Refactor how inbound criteria for join task is evaluated to count by task completion
instead of task transition. (improvement)

Fixed

Fix conducting of cycle with a fork. Fixes StackStorm/orquesta#169 (bug fix)
Fix request_workflow_status to ignore certain status change errors such as pausing a workflow
that is already pausing and canceling a workflow that is already canceling. (bug fix)
Remove rendering of workflow output automatically when updating task state. This caused
workflow output to render incorrectly in certain use case. The render_workflow_output function
must be called separately. (bug fix)
When inspecting custom YAQL/Jinja function to see if there is a context arg, use getargspec
for py2 and getfullargspec for py3. (bug fix)
Check syntax on with items task to ensure action is indented correctly. Fixes StackStorm/orquesta#184 (bug fix)
Fix variable inspection where ctx().get() method calls are identified as errors.
Fixes StackStorm/st2#4866 (bug fix)
Fix a problem of TypeError orccuring when a list (or dict) value that contains unhashable typed
value (list or dict) is passed in some YAQL operators (e.g. distinct()). Fixes StackStorm/orquesta#176 (bug fix)
Contributed by Hiroyasu Ohyama (@userlocalhost)

Fore more info see https://github.com/StackStorm/orquesta/blob/master/CHANGELOG.rst
st2chatops

Massive refactoring for hubot-stackstorm st2chatops relies on. Random ChatOps bugs could be fixed as well as regressions appear.
Update to latest fixed Microsoft Teams Hubot Adapter StackStorm/st2chatops#141 StackStorm/st2chatops#148
Update to latest fixed Cisco Spark (Webex) Hubot Adapter StackStorm/hubot-stackstorm#198 StackStorm/hubot-stackstorm#200 StackStorm/st2chatops#148
Fix for Mattermost Adapter StackStorm/hubot-stackstorm#192

st2web

No changes.

Warning!
st2web UI needs a contributor/maintainer! Critical security vulnerabilities due to outdated dependencies, as well as tech debt, issues and number of unreviewed PRs is all high.

This could be huge. With almost 1 year since v3.1 st2 release codebase accumulated so many new features, changes and fixes.
Please report findings here and bugs/regressions in respective repositories.
Depending on severity and importance bugs might be fixed before the release or postponed to the next release if they're very minor and not a release blocker.

@StackStorm/maintainers Even if you didn't find any bugs, please report back in this discussion which OS/environment you've used and which features/items you've tried or verified. This will help to get an overall idea about OS/distro testing distribution.
I may assign OS/flavors to different team members as we did before.

Very brief test done on centos8. Installed using single line install which went fine.
Simple chatops configured with slack for the aws ec2 get alias (note: stackstorm_aws 1.2.3 pack used, as 1.3.1 had issues - which I'll report separately - but not to do with stackstorm version).
Simple orquesta workflow moved over successfully from stackstorm 3.1 install, which used the aws_boto3 and slack packs.
I did fall foul to the change where it installs the latest tagged pack rather than latest version of the code, on page: https://docs.stackstorm.com/latest/packs.html it states that it installs the latest commit of a pack rather than the tagged, but looking at the change log then that seems to be a known change.
Docs state "By default, the latest commit to a pack repository will be installed, but you can specify a particular version, branch, tag, or even a commit hash. Just use =:" yet, it seems to install last tag. If this is by design as per "Install pack with the latest tag version if it exists when branch is not specialized. (improvement) #4743" - then does documentation need updating?

@amanda11 Awesome, thank you very much for testing and feedback!
Yes indeed, in 3.2dev the behavior of pack install has changed which now installs latest "tag/version" instead of latest commit from master.
That's a good catch! :+1:
@amanda11 Documentation indeed needs updating. How about submitting a small PR to fix that?
https://github.com/StackStorm/st2docs/blob/master/docs/source/packs.rst

@armab I'll submit a PR for the doc change. thanks.

@armab I'll submit a PR for the doc change. thanks.

https://github.com/StackStorm/st2docs/pull/973 raised. I also verified the behaviour when you had a local repo that it was working, and what it picked up if you used file:/// towards a local git repo. That seems to still use the latest commit when using a file:/// to a local repo - so I left that section stating latest commit. So I literally just changed one word in the docs in the end.

FYI for someone testing 3.1 -> 3.2 upgrade scenarios here is how to install 3.1dev from unstable packages first:
curl -sSL https://stackstorm.com/packages/install.sh | bash -s -- \
  --unstable --version=3.1dev \
  --user=st2admin --password=Ch@ngeMe

Then follow the packages upgrade procedure https://docs.stackstorm.com/latest/install/upgrades.html#general-upgrade-procedure to get v3.1dev->v3.2dev upgraded.

Installation with the following instructions fails on EL6 and EL7:
curl -sSL https://stackstorm.com/packages/install.sh | bash -s --   --unstable --version=3.1dev   --user=st2admin --password=Ch@ngeMe

repoquery -y flag which was added before is non-existent for EL6.
Update: -y is non-existent for EL7 as well.
Reported as https://github.com/StackStorm/st2-packages/issues/641

Further positive feedback on testing. Loving the immutable parameters on the aliases. Needed them for some aliases I needed for AWS reporting using the aws_boto3 pack. Integrated those successfully with st2chatops using 3.2dev on Centos8.

Another 2 minor issues/enhancements were spot:

MongoDB 3.4 reached its EOL used by the EL6/EL7/U16 platforms https://github.com/StackStorm/stackstorm-ha/issues/97
nginx warning about deprecated 'ssl on' st2 nginx config we use: https://github.com/StackStorm/st2/pull/4917

Both are not release blockers and will be planned for the next st2 v3.3.

Probably not an issue - but a problem I encountered. If I already have a config for a pack under /opt/stackstorm/configs, and then try and use st2 pack config then I get an error due to failing to have write permission to that file. It works if I delete the old config file, as it then creates a new file with the owner of st2. But I am guessing that if people have manually configured files they may not have created them with the owner as st2.

I had a play with the retry feature in the Orquesta workflow and I was surprised that I didn't have to up the version in the workflow yaml to state it was using version 1.1.0. I have the version as 1.0 and it works fine (documentation example uses version 1.0).
So although new functionality it is still the same version of the workflow DSL?

I have a Orquesta workflow with:
action A - with retry count of 2 (no when clause on the retry - so default to failed)
action B - slack post message
The when transition on A goes to B if A fails.
I was expecting to only goto B once. But I'm seeing that B is being called for all 3 failures. Whereas I expected that it would only do the fail transition once.

After running the st2-self-check I was left with lots and lots of chatops_test aliases. Could the packs that get installed get removed at the end?

@amanda11 For the orquesta with retry, that sounds unexpected to me too.
From the description, could be somewhat related to https://github.com/StackStorm/orquesta/issues/138#issuecomment-615338189
Can you please create a new issue in https://github.com/StackStorm/orquesta/ with example workflow for @m4dcoder to reproduce easily, describing what's expected and what went wrong?

I had a play with the retry feature in the Orquesta workflow and I was surprised that I didn't have to up the version in the workflow yaml to state it was using version 1.1.0. I have the version as 1.0 and it works fine (documentation example uses version 1.0).
So although new functionality it is still the same version of the workflow DSL?

The version in WF DSL is a placeholder currently and the engine don't support multiple DSL versions.  The new features are additive.  In the future as we make major changes such as schema change or deprecation, we will definitely need to figure out how to separate support of different DSL versions.

Here's the fix for the task retry reported above. PR @ https://github.com/StackStorm/orquesta/pull/200. Good catch @amanda11, keep them coming. @armab Once PR is merged, I'm thinking of republishing the v1.1.0 release for orquesta. What do you think?

Hi,
here is the summary of my tests from tonight:
successfully tested:

installation and basic st2 commands on CentOS8
installation and basic st2 commands on Ubuntu 18.04 (all tests mentioned below were made on this system)
tested the automatic installation of dependencies (#4769)

install local pack with dependencies
install local pack with dependency to another local pack with dependencies to github & st2 exchange
install several packs with the same dependencies
install pack with dependencies to local and remote packs
install a pack (pack1) with a dependency to pack2 which has a dependency to pack1 (to see if this creates some kind of infinite loop or deadlock)

test the new continue command (#4740) and the retry feature in Orquesta workflows
compare the performance of with item tasks on st2 3.1 vs. 3.2 (https://github.com/StackStorm/orquesta/pull/195)
test a bunch of actions from the aws_boto3 pack and verify that existing workflows still work
tested inquiries with properties of all available types
tested the pack API

only the tests with the tags filter failed (see #4918)

I hope this helps. Will continue testing in the next days. Let me know if you want anything special tested. Otherwise I will just keep going through the release notes and test the mentioned changes.

Hi,
here is the summary of my tests from tonight:

installation and basic st2 commands on CentOS8
installation and basic st2 commands on Ubuntu 18.04 (all tests mentioned below were made on this system)
tested the automatic installation of dependencies (#4769)

install local pack with dependencies
install local pack with dependency to another local pack with dependencies to github & st2 exchange
install several packs with the same dependencies
install pack with dependencies to local and remote packs
install a pack (pack1) with a dependency to pack2 which has a dependency to pack1 (to see if this creates some kind of infinite loop or deadlock)

test the new continue command (#4740) and the retry feature in Orquesta workflows
compare the performance of with item tasks on st2 3.1 vs. 3.2 (https://github.com/StackStorm/orquesta/pull/195)
test a bunch of actions from the aws_boto3 pack and verify that existing workflows still work
tested inquiries with properties of all available types
tested the pack API

only the tests with the tags filter failed (see #4918)

I hope this helps. Will continue testing in the next days. Let me know if you want anything special tested. Otherwise I will just keep going through the release notes and test the mentioned changes.

Whilst testing re-run from task functionality I raised: https://github.com/StackStorm/st2docs/issues/975 on the documentation. Haven't submitted PR as didn't know if was a known list of new features to be upcoming past 3.2 that should be in there instead.

@m4dcoder For the Orquesta bugfix I think it's best to publish new v1.1.1 patch to include in st2.
Also replied in https://github.com/StackStorm/orquesta/pull/200#discussion_r414570864

Current 3.2dev pre-release testing status:

Community is doing a pretty good job in testing the features and reported/fixed already good amount of bugs. Thank you all for the tremendous help!
New hotfixes based on reported bugs https://github.com/StackStorm/st2/pull/4919 https://github.com/StackStorm/orquesta/pull/200 https://github.com/StackStorm/st2/pull/4917 are included into 3.2dev and latest packages were re-generated
Feel free to continue 2nd cycle of 3.2dev testing based on new fixed packages
If everything goes well, we'll kick off the release automation early next week with @punkrokk  to get st2 v3.2 into staging-stable

Documentation issue raised on upgrade docs when running on python 3: https://github.com/StackStorm/st2docs/issues/977. Wasn't sure if just needed a small note, or if there was extra steps required for mistral when going from 3.1->3.2.

Next stage of release automation process & testing, following the https://github.com/StackStorm/discussions/wiki/Release-Process#process-for-major-release (now open) is that we got staging-stable packages out in https://packagecloud.io/stackstorm/staging-stable repository.
At this stage we can just quickly check the packages like integrity/smoke tests to make sure this version is not different to what we tested last week and has no surprises:
curl -sSL https://stackstorm.com/packages/install.sh | bash -s -- --user=st2admin --password=st2admin --staging

These packages are now candidate for the final stable promotion.
If no major issues found, we'll continue the release automation tomorrow, 28 Apr, US morning.

FYI for someone wondering the pipeline is the following:
staging-unstable -> unstable -> staging-stable -> stable.
See https://github.com/StackStorm/discussions/wiki/Useful-info-for-Release-Managers#packagecloud-repositories for more info about each repository.

Probably a bit late to the party but I just ran all the tests from my previous comment on the staging packages again - successfully.

Thanks everyone!
Especially @amanda11 and @winem for spending extra effort catching and fixing bugs!
We now have StackStorm v3.2.0 stable out: https://stackstorm.com/2020/04/30/stackstorm-v3-2-0-released/


SPA aren't autoloaded anymore

Can't find locations registered for myjobs, alerta, packagemanager.. etc

fixed in ae16f3f9b68e3808afda2526c1fdbcd3e2b8aad2

verified


Dnscrypt-proxy - 1.9.4-3 vs 1.9.5-1

I've noticed that when upgrading to the latest release ( I think from yesterday or today ) , dnscrypt stops working after reboot, if you use any of the options that come commented in the base package. I was using this options:
config dnscrypt-proxy ns1
        option address '<IP_ADDRESS>'
        option port '5353'
        option resolver 'cisco-familyshield'
        option resolvers_list '/usr/share/dnscrypt-proxy/dnscrypt-resolvers.csv'
        # ephemeral keys option requires extra CPU cycles and can cause huge system load
        # option ephemeral_keys '0'
        # more details at https://github.com/jedisct1/dnscrypt-proxy#public-key-client-authentication
        # option client_key '/path/to/client_key'
-->        option syslog '1'
-->        option syslog_prefix 'dnscrypt-proxy'
-->        option query_log_file '/mnt/sda1/dnslogs/dnsqueries.log'
        # enable cache may speed up dnscrypt-proxy, see https://github.com/jedisct1/dnscrypt-proxy/wiki/Go-faster
-->        option local_cache '1'
        # disable IPv6 may also speed up dnscrypt-proxy, see https://github.com/jedisct1/dnscrypt-proxy/wiki/Go-faster
-->        option block_ipv6 '1'
        # Blacklists allow you to block domains, ip, ... see https://github.com/jedisct1/dnscrypt-proxy/wiki/Filtering
-->        list blacklist 'domains:/usr/share/dnscrypt-proxy/dnscrypt-blacklist-domains.txt' 'logfile:/mnt/sda1/dnslogs/dnscrypt-blocked.log'

Some of the lines preceded with a --> are the ones that are creating chaos.
I tried several combinations, and for example , running the latest version ( 1.9.5-1 ) , I was able to enable option syslog '1' and option syslog_prefix, but not the others.
Running a dnscrypt-proxy restart logs in the system log something like "plugins are not implemented", and the router is left with no capability to resolve DNS Addresses ( therefore, the whole network goes down )
I was also unable to make the option to save the blocked queries into the log file... it does save the queries, but not the blocked ones

Operating system? Architecture? Package source?

I've never seen a configuration file that looks like that. It's certainly not something the normal dnscrypt-proxy package can load.
There have been no new releases for the past few days either. So I'm not sure what you have installed.
"plugins are not implemented" means that support for plugins was disabled when the package was compiled. Plugins have been enabled by default for a long time, so they have been explicitly disabled.
Which means that logging, filtering, IPv6 filtering, etc. cannot work. They are all plugins.

I'm running on a router using LEDE. Source are:
src/gz reboot_core https://davidc502sis.dynamic-dns.net/snapshots/r4114/targets/mvebu/generic/packages
src/gz reboot_base https://davidc502sis.dynamic-dns.net/snapshots/r4114/packages/arm_cortex-a9_vfpv3/base
src/gz reboot_luci https://davidc502sis.dynamic-dns.net/snapshots/r4114/packages/arm_cortex-a9_vfpv3/luci
src/gz reboot_packages https://davidc502sis.dynamic-dns.net/snapshots/r4114/packages/arm_cortex-a9_vfpv3/packages
src/gz reboot_routing https://davidc502sis.dynamic-dns.net/snapshots/r4114/packages/arm_cortex-a9_vfpv3/routing

Since this is completely different from a vanilla installation of dnscrypt-proxy, you should probably report this to the LEDE maintainers.
I'm not familiar with LEDE, but perhaps the plugins are in a different package?
Alternatively you can use dnscrypt-proxy installer but this requires the ability to write files to /lib and I don't know if this is the case on LEDE.

Frank, thanks! I did report this to the LEDE maintaner already.
On Thu, May 18, 2017 at 11:57 AM, Frank Denis<EMAIL_ADDRESS>wrote:

Since this is completely different from a vanilla installation of
dnscrypt-proxy, you should probably report this to the LEDE maintainers.
I'm not familiar with LEDE, but perhaps the plugins are in a different
package?
Alternatively you can use dnscrypt-proxy installer
https://github.com/jedisct1/dnscrypt-proxy-installer but this requires
the ability to write files to /lib and I don't know if this is the case
on LEDE.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jedisct1/dnscrypt-proxy/issues/661#issuecomment-302448900,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKXxmu2c5FJzO7cT7d1y41CZxLkS8yKzks5r7GpjgaJpZM4NevRw
.


bug: Security Vulnerabilities created with no Severity

Describe the bug
The Security Vulnerabilities that are created in the GitHub Security Tab, do not have vulnerabilities assigned to it
Expected behavior
Vulnerability Levels should ideally be set as Critical, High, Medium, Low, Info.
This is actually the output of the scan, but vulnerabilities aren't created using them
Using the latest Github Actions
System Info

tfsec version: 1.28.0
terraform version: ?
OS: ?

Additional context

How did you upload the result to Github?
Now the efforts of developers are focused on the development and support of Trivy. You can upload the results of the Trivy scan to Github using trivy-action.
/cc @simar7


jobquery filtering by RAM does not work

Adding a value to the RAM field leads to an error.  Also, "RAM" is ambiguous, it should be resident or virtual.
Probably the jobquery page needs a lot of testing.

It's "min-mem-peak" not "min-peak-mem", cpu filtering has the same issue.

Also, sonalyze needs to move into the new world where it's possible to filter by resident memory, and it needs to make it clear that "mem" is virtual.

Filtering by CPU also does not work because of unit problems - it deals in "cores" and I write "20", the search deals in percent of cores and gives me anything using more than 20% of one core.


What is different in this one than the original "hack_interview" ?

Can you please mention in the readme whats different than the original project ?

Why? And what exactly should I write in the differences? That other libraries are used, there is a possibility to choose a model for generating answers, the UI is different. Event handling is also different in general. And about all the other differences too?
It seems to me that this is unnecessary information for the user of the application for the readme file.


fix(client): Ensure types renamed by the bundler do not leak to thrid-party packages

Removes automatic forced export of all types in client's runtime and
replaced that with controlled exports from a specific place.
Custom eslint rules ensure that all neccessary types can be used by tsc
without inlining. Details you can see in types/exported/README.md
file.
Fix prisma/team-orm#358
/integration

Note: After the re-run of the ecosystem-tests, they are all passing.


sys.stdout not flushed on exit

🌍 Environment

Your operating system and version: MacOS 10.15.7
Your python version: Python 3.9.1
How did you install python (e.g. apt or pyenv)? Did you use a virtualenv?:  Yes, reproduces after fixing compilation errors.

💥 Reproducing
Clone https://github.com/arxanas/pyo3-bug and run PYTHONPATH=. cargo run in the root directory.
main.rs:
use pyo3::prelude::*;

fn main() -> PyResult<()> {
    Python::with_gil(|py| {
        let testing = PyModule::import(py, "testing")?;
        testing.call0("foo")?;
        Ok(())
    })
}

testing.py:
import sys

def foo():
    sys.stdout.write("Hello, world!")
    # Uncomment to fix issue:
    # sys.stdout.flush()

Note that the issue doesn't reproduce if the output ends with a newline character. Presumably that automatically flushes stdout.
This is probably due to #1355. I understand that running finalizers might break some C code, but perhaps a special case can be made for flushing stdout/stderr? It's an idempotent operation, and it might take a long time for someone to debug the issue otherwise.
If you don't want to change this behavior, then a note in the documentation somewhere would be helpful.

Hi @arxanas we added the finalizers to flush stdout and then removed them in #1355 as you note because of the C code and also async issues. In the end we decided there's too many issues with finalizers to run them ourselves. So I think this is a documentation issue.
You may want to consider running with PYTHONUNBUFFERED=1 if you've got stdout being printed from both Rust and Python, so that ordering remains consistent. This will also avoid the need to call flush manually at program exit 😃
Alternatively you could add unsafe { pyo3::ffi::Py_Finalize() } at the end of your main function if it doesn't cause you problems.


[Draft] Payment review

This PR is about the last big stone of the back-end: payment API.
For now, /payement/pay makes the request to helloasso but the post processing isn't implemented yet.
There is also some CORS issues to solve
TODO

[ ] /payment/refund

[x] handling callbacks

[x] cleaning code

[ ] hardening

[ ] documentation

[ ] testing

For the refund, only admins can achieve this action. This action can only be performed in the djando admin panel, with an action on a transaction. In the front, maybe a form that sends  an email to email address. This will reduce the risk to be misused

So today I added:

The entire hooks/callbacks system
Admin interface stuff for various classes we used
Updates to the tournament classes and their fields
An entire pipeline to pay for a tournament registration through the payment API

From what I got from our last conversation, all that's left here is:

Tournament Opening and closing dates from #31

[ ] Products should have an available and expiry date
[ ] Tickets should use the date from the tournament when created
[ ] Changing dates in a tournament should change it on the products
[ ] Ideally, add an issue to have the reverse also be true

[ ] Cashprizes from #49

The only thing missing as a django action to allow admin to refund/cancel user participation in a tournament

Before merge this big piece of features, the only thing missing is to allow player to join a team. The idea is to use team password. The captain can generate it (generated randomly otherwise) and then an url with this password as a query param is given to the captain and they can invite their player as so

Before merging this big piece of features, the only thing missing is to allow player to join a team. The idea is to use team password. The captain can generate it (generated randomly otherwise) and then an url with this password as a query param is given to the captain and they can invite their player with it.

This is more linked with tournament code, as its pertains to the flow of joining teams, but not the flow of paying for a ticket or refunding it, provided that everything else works.

Bigger issue so far: we seemingly completely misunderstood the point of return/back/error URLs, and we should not be using them for deciding the fate of a transaction. This has to be fixed before merge. I'm digging into the helloasso API documentation to try and figure that out

Despite a few mistakes, the code looks alright, we will need to deploy to preprod to test the full pipeline for real though

There's also the big problem with that fundamental misunderstanding we had with the notification channel from HelloAsso, but I intend to try and solve that at some point before/during out meeting tonight

In the meantime, aside from pushing huge modifications linked to the notification channel (those are on another laptop, sadly), I can address the nitpicking points mentioned above :+1:

Alright last step is handling all of the refund API non-availability nonsense 🥲

Rebased.
Abandon all hope, ye who reads this PR


Refactor tests and moved fixture to conftest

Fixes #88
That will make the code readable and maintainable, mainly for future work
Changes you made

Moved fixture to one file "conftest.py"
Made sure that the tests works
Refactor test_check_is_employee, test_check_is_manager to be shorter

@kobihk How can we move on with that PR?

@AvivLiberman Please fix the conflicts and the parameterized as we talked
Thanks!!

@AvivLiberman Please fix the conflicts and the parameterized as we talked Thanks!!

@kobihk Added the changes


RNAseq Variant Calling Pipeline

I have an RNAseq Variant Calling Pipeline in snakemake form, adapted from the one made by Jeffrey for BL. I can modify it to fit lcr-modules guidelines.

Write access granted. Please develop on a branch named after your module (e.g. rnaseq-variant-calling) and then submit a PR. I'll have more detailed contribution guidelines before the end of the week.

This module is in PR #184


Exception while passing own moshiAdapters to NetworkingRouterConfig

I need to pass my own JsonAdapter that implements the MoshiAdapterFactory interface to the NetworkingRouterConfig() then it throws an exception as soon as it get used.
UserJsonAdapter.kt:
class UserJsonAdapter: MoshiAdapterFactory {
    private lateinit var borsh: Borsh

    override fun create(borsh: Borsh): Object {
        this.borsh = borsh
        return Object()
    }

    @FromJson
    fun fromJson(rawData: Any): Buffer<User> = Buffer.create(borsh = borsh, rawData = rawData, clazz = User::class.java)
}

Solana initialization:
Solana(
           router = OkHttpNetworkingRouter(
                endpoint = RPCEndpoint.mainnetBetaSolana,
                httpClient = get(),
                config = NetworkingRouterConfig(rules = listOf(UserRule()), moshiAdapters = listOf(UserJsonAdapter()))
            )
        )

Exception:
    java.lang.IllegalArgumentException: Expected at least one @ToJson or @FromJson method on java.lang.Object         at com.squareup.moshi.AdapterMethodsFactory.get(AdapterMethodsFactory.java:153)         at com.squareup.moshi.Moshi$Builder.add(Moshi.java:223)         at com.solana.networking.OkHttpNetworkingRouter$moshi$2.invoke(NetworkingRouter.kt:68)         at com.solana.networking.OkHttpNetworkingRouter$moshi$2.invoke(NetworkingRouter.kt:60)

This is now rewritten. I think it was not wheel documented. Check https://github.com/metaplex-foundation/SolanaKT/pull/107


feat: educate user about the password

What I try to educate user about the password:

I guess expert users always know what is blockchain, and I never have to teach them. So the target groups of users I aim to educate is those new-to-blockchain user coming from keypom, etc.
I have to educate them that the password is not a tools that allow them to recover their account. They still need to backup their seed phrase.
I have to educate them that the password should not be safe in the browser password manager, doing so totally defeats the purpose of this password encryption because what the password encryption actually do is to prevent physical hacker (your guest in house / office).
I have to also educate them that the password is not a correct way to protect data if they are not using it in a private PC environment. They should immediately clear all browser history as this is the safest way to protect their data.

Known and unsolved issues:

User will just tick that 3 checkbox and press Next, without reading any of the text, I knew that, but I don't have any better solution yet.

I just changed the warning messages slightly. The message about using a public PC is pretty much a general warning for using wallets anywhere- not too specific to the password encryption itself, so I removed it.


Question: XLIFF file: Lifecycle Services

I have tried the Lifecycle Services from Microsoft to translate my xlf files that are generated from Visual Studio Code.
I used the following guide: https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/lifecycle-services/use-translation-service#xliff-tm
However I can't seem to upload a valid file. I tried both Microsoft Dynamics 365 for Finance and Operations and Dynamics Nav 2017 (2018 not available in drop down).
Is this service not available yet for our developments? Will it be available in the future?

LCS now supports the XLIFF format for NAV translations:
https://blogs.msdn.microsoft.com/lcs/2018/01/30/lcs-january-2018-release-2-release-notes/


Torque CDN URL composition doesn't work for shared tables

Extracted from #9017, as a partial fix was deployed at #8991.
The last tests of #8991 integrating all fixes revealed a last issue in staging: Torque still generates the wrong CDN request. Example. It requests a url based on the table owner instead of the visualization owner.
It's probably because of these lines. The backend patch that works without CDN can't be applied here.
PS: this only happens with named maps.
cc @javisantana

We'll add a layer.options['visualization_user_name'] attribute to the v2 vizjson to be used by Torque.

That's already working right?

No, it's not. Backend side was ready (CartoDB/cartodb/pull/9136), but Torque side was still missing.

I've made @CartoDB/cartodb.js#1435 PR to fix this issue.

With that fix it will be done @donflopez?

I hope @xavijam! I need to try it with a real cdn.

staging!